LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 02-23-2020, 12:45 PM   #1
Pigi_102
Member
 
Registered: Aug 2008
Posts: 109

Rep: Reputation: 10
qemu-system-arm panic on X86_64


Hi all,
I'm trying to follow the indication on
https://docs.slackware.com/howtos:ha...cross-compiler, because I would like to try to finish the google-go-lang build as described in another thread.

I've followed everything and on the first try I had an error that had been easily addressed. It was a problem with the vlan keyword on the NETTYPE.

After this I've issued the installer_launch script but after the tipical kernel messages it starts complaining with:
Code:
[  170.107314] Run /init as init process
/etc/rc.d/rc.modules-arm: line 67:   108 Segmentation fault      $MP $mod > /dev/null 2>&1
/etc/rc.d/rc.modules-arm: line 67:   109 Segmentation fault      $MP $mod > /dev/null 2>&1
/etc/rc.d/rc.modules-arm: line 67:   110 Segmentation fault      $MP $mod > /dev/null 2>&1
and does this for many lines.
At the end f this errors I get a prompt, but whichever command I issue I get a kernel panic and the only thing I have to do is kill the qemu-system-arm ( from antoher windows ):
Code:
[  934.152688] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[  934.154074] CPU: 0 PID: 1 Comm: init Not tainted 5.4.18-armv7 #2
[  934.154891] Hardware name: ARM-Versatile Express
[  934.156754] [<c030f480>] (unwind_backtrace) from [<c030a8e4>] (show_stack+0x10/0x14)
[  934.158127] [<c030a8e4>] (show_stack) from [<c09edd48>] (dump_stack+0xb8/0xdc)
[  934.159417] [<c09edd48>] (dump_stack) from [<c033e708>] (panic+0xe8/0x2fc)
[  934.160774] [<c033e708>] (panic) from [<c0341a58>] (do_exit+0x1a0/0x9b0)
[  934.161711] [<c0341a58>] (do_exit) from [<c0342db8>] (do_group_exit+0x58/0xb8)
[  934.162788] [<c0342db8>] (do_group_exit) from [<c034d144>] (get_signal+0x194/0x61c)
[  934.164075] [<c034d144>] (get_signal) from [<c030a1f0>] (do_work_pending+0xc4/0x34c)
[  934.165259] [<c030a1f0>] (do_work_pending) from [<c0301064>] (slow_work_pending+0xc/0x20)
[  934.166401] Exception stack(0xee095fb0 to 0xee095ff8)
[  934.167369] 5fa0:                                     b6ef3fd0 00000000 00000019 bec6dc81
[  934.168653] 5fc0: b6f99e00 b6fb9950 00000001 00000002 00000000 00000000 b6fbc000 001017c8
[  934.169881] 5fe0: 00101308 bec6dc88 00000001 00000000 60010030 ffffffff
[  934.171634] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
Is there someone that has addressed this problem ?

Thx

Pigi
 
Old 02-23-2020, 03:29 PM   #2
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 640

Rep: Reputation: 375Reputation: 375Reputation: 375Reputation: 375
Quote:
Originally Posted by Pigi_102 View Post
I'm trying to follow the indication on https://docs.slackware.com/howtos:ha...cross-compiler, because I would like to try to finish the google-go-lang build as described in another thread.

Is there someone that has addressed this problem ?
Hi, could you post a description on which hardware you're using, and operating systems involved, and why you're cross-compiling? I need some grasp of your setup, what you're trying to achieve, and how you're trying to achieve it. Thanks in advance.
 
Old 02-23-2020, 04:13 PM   #3
Pigi_102
Member
 
Registered: Aug 2008
Posts: 109

Original Poster
Rep: Reputation: 10
Yes, Exaga, noi problem !

My setup is:
Hw MacbookPro 2011
Intel(R) Core(TM) i5-2415M CPU @ 2.30GHz ( 4 core )
8Gb Ram

O.s. Slackware-current upgraded on Feb 6.
Kernel 5.4.13 #1 SMP x86_64

My need is to have an environment to cross-compile those packages that I cannot directly compile on my Raspberry PI ( 3+ ).

My idea is to have a "VM" using qemu with the same setup of my Pi ( slackware-current ) but with a bit more of resources to achieve those compilations.

In this way I can get the packages ready to be installed on Pi.

Let me know if you need more infos.


Pigi
 
Old 02-27-2020, 04:18 AM   #4
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 1,048

Rep: Reputation: 852Reputation: 852Reputation: 852Reputation: 852Reputation: 852Reputation: 852Reputation: 852
Quote:
Originally Posted by Pigi_102 View Post
Hi all,
I'm trying to follow the indication on
https://docs.slackware.com/howtos:ha...cross-compiler, because I would like to try to finish the google-go-lang build as described in another thread.

I've followed everything and on the first try I had an error that had been easily addressed. It was a problem with the vlan keyword on the NETTYPE.
I'll have a look at that. Did you follow the installation documents on docs.slackware.com? Is that where you took the script from?


Quote:
After this I've issued the installer_launch script but after the tipical kernel messages it starts complaining with:
Code:
[  170.107314] Run /init as init process
/etc/rc.d/rc.modules-arm: line 67:   108 Segmentation fault      $MP $mod > /dev/null 2>&1
/etc/rc.d/rc.modules-arm: line 67:   109 Segmentation fault      $MP $mod > /dev/null 2>&1
/etc/rc.d/rc.modules-arm: line 67:   110 Segmentation fault      $MP $mod > /dev/null 2>&1
I'll have a look at this when I have time in the next weeks. It worked fine when I tested Linux 5.4 recently.
 
Old 02-27-2020, 08:26 AM   #5
Pigi_102
Member
 
Registered: Aug 2008
Posts: 109

Original Poster
Rep: Reputation: 10
Quote:
Originally Posted by drmozes View Post
I'll have a look at that. Did you follow the installation documents on docs.slackware.com? Is that where you took the script from?
Yes, exactly from there.
Feel free not to be in a hurry. At the moment I have been able to "build" golang directly on Pi, so it' not urgent ( also it it will be easer to work on faster environment )
Thanks for your time.

Pigi
 
Old 03-02-2020, 10:52 AM   #6
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 1,048

Rep: Reputation: 852Reputation: 852Reputation: 852Reputation: 852Reputation: 852Reputation: 852Reputation: 852
It works fine here with qemu 4.1.0 on Slackware64-14.2. It seems that the qemu network settings need some work though, because just removing the 'vlan' parameters don't bring up eth0.
If anyone knows how to fix that, let me know: I've looked at the docs just now and it's not as obvious as I'd have hoped.
 
Old 03-06-2020, 07:13 AM   #7
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 1,048

Rep: Reputation: 852Reputation: 852Reputation: 852Reputation: 852Reputation: 852Reputation: 852Reputation: 852
Quote:
Originally Posted by drmozes View Post
It works fine here with qemu 4.1.0 on Slackware64-14.2. It seems that the qemu network settings need some work though, because just removing the 'vlan' parameters don't bring up eth0.
If anyone knows how to fix that, let me know: I've looked at the docs just now and it's not as obvious as I'd have hoped.
I've popped a note at the head of the document, in case anyone wants to submit a diff to the helper scripts.
 
Old 09-30-2020, 03:56 PM   #8
mralk3
Senior Member
 
Registered: May 2015
Distribution: Slackware, OpenBSD
Posts: 1,558

Rep: Reputation: 882Reputation: 882Reputation: 882Reputation: 882Reputation: 882Reputation: 882Reputation: 882
The docs have been updated and a clean qemu vm booted with arm-current on a Slackware64-14.2 host. The Slackwarearm-current qemu guest changelog is dated Sun Sep 20 08:08:08 UTC 2020.

@Pigi_102: If you are trying to boot an aarch64 or arm64 kernel with Slackwarearm, this has not been tested. Slackware ARM is based on x86. Also, I test in qemu with the stock 14.2 kernel (4.4.227 at this time). The stable release is the host target and the qemu guest targets arm-current.

Please mark this thread as solved if none of this applies any longer.

EDIT:

The installer boots and installs, it just takes a long long time.

I booted the resulting install with the disk_launch script.

Last edited by mralk3; 09-30-2020 at 08:09 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
kernel panic on init linux for arm using qemu jbaramidze Linux - Software 1 02-25-2014 01:39 PM
help with kernel panic in qemu (arm) larry7 Linux - Embedded & Single-board computer 0 07-30-2012 07:13 AM
LXer: Set up qemu-kvm-1.0+noroms as spice enabled qemu server vs qemu-kvm-spice on Ubuntu Precise LXer Syndicated Linux News 0 05-26-2012 07:41 AM
buildroot images not working with qemu-system-arm ramitwadhwa Linux - Embedded & Single-board computer 0 10-19-2010 10:14 AM
ipm timed out error on Red Hat 2.6.9-67.0.22.ELsmp #1 SMP x86_64 x86_64 x86_64 GNU/L bellnarm Linux - Newbie 0 07-07-2009 04:36 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 09:08 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration