Kernel panic while trying to install 3.1rc2

[Rosario Contarino]

Dear all,

I tried first the alpha live and it worked fine, then downloaded and booted with the 3.1rc2 but unfortunately, as soon as I try to install it, no matter which troubleshooting option I take, it will end up with a kernel panic.

The PC is an old Dell Dimension 5150 with a Pentium D 2.8Ghz and 4GB of RAM and a firewire PCI card.

Any ideas?

Thanks in advance
Rosario

[JPL]

I'm having a similar problem. Have just downloaded the ISO again and will have another try later.

In the meantime, have you enabled legacy mode in the boot options in the BIOS?

[Rosario Contarino]

Not sure which legacy mode you are referring to.

There is one option on the A05 Bios available on the motherboard of the Dimension 5150 which allows the BIOS to show only 256MB of available memory to "old" OSs.

I tried  it and, again, kernel panic

Consider that the live USB boots and runs normally so I would say it may have something to do with the installation process, maybe something with the HDD controllers?

Hope some moderator will give us a hint.

--
You received this message because you are subscribed to a topic in the Google Groups "qubes-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qubes-users/BJER3lm2niA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/46ca7d3d-af3e-43f8-8014-a569244b4b81%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

R.D. Contarino <rdcon...@gmail.com>
skype: rdarioc

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, Jan 27, 2016 at 09:35:39AM +0100, Rosario Contarino wrote:
> On 27 January 2016 at 08:57, JPL <atep...@gmail.com> wrote:
> > On Wednesday, January 27, 2016 at 6:41:13 AM UTC, Rosario Contarino wrote:
> >>
> >> Dear all,
> >>
> >> I tried first the alpha live and it worked fine, then downloaded and
> >> booted with the 3.1rc2 but unfortunately, as soon as I try to install it,
> >> no matter which troubleshooting option I take, it will end up with a kernel
> >> panic.
> >>
> >> The PC is an old Dell Dimension 5150 with a Pentium D 2.8Ghz and 4GB of
> >> RAM and a firewire PCI card.
> >>
> >> Any ideas?
> >>
> >> Thanks in advance
> >> Rosario
> >>
> >
> > I'm having a similar problem. Have just downloaded the ISO again and will
> > have another try later.
> >
> > In the meantime, have you enabled legacy mode in the boot options in the
> > BIOS?
>

> Not sure which legacy mode you are referring to.
>
> There is one option on the A05 Bios available on the motherboard of the
> Dimension 5150 which allows the BIOS to show only 256MB of available memory
> to "old" OSs.
>
> I tried it and, again, kernel panic
>
> Consider that the live USB boots and runs normally so I would say it may
> have something to do with the installation process, maybe something with
> the HDD controllers?

What exactly "kernel panic" message you've got?

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWrpAxAAoJENuP0xzK19csDfkH/2JUkhcG1WcOsxD8riKgXl1L
dpPfK0yerl3RdVYDArhoo/UXliKEs0WgY1u2r7//VSbc/hDhkigbWDr5HzijWjlX
/munB12/7KRvpG5oTQ4dd934PWNRa8msm2q0M3kAUT8sgDqHoGNdLYys+X9Z5Q2u
BnM2Cs55CaSu8nJSHb/YraWOIRmwAfNh7suFMv4ZmbkDtkVcUyO7cak/9aq3B6hf
53KwJCyqipnoNE0qWPNkDqsSm4pleOey4uXXk6UkHc9F2s4g5vo63iTw1/UpdKsc
5eKLnF+8nYTWAUpm6rgbrU9qOIHGC3KoVHM3WOOEjPXI8qpetVoDxs62mNoXA8Q=
=8ETc
-----END PGP SIGNATURE-----

[R. D. Contarino]

Hard to say. It all happens in a fraction of a second before the machine reboots.

Nonetheless I'll give it another try and I'll let you know if I'm able to get more details.

Do you know if any of those console logs before the final kernel error are stored somewhere in the flash used to install the os?

---
R.D. Contarino

[Rosario Contarino]

So,

I select the option: "Test this media & install qubes"

Screen is cleared, then:

xen.gz ... ok

vmlinux ... ok

initrd.img ... ok

then about 30 lines of console messages that end with (not the exact format)

kernel panic ... not syncing ... attempted to kill init! exitcode 0x000009

Any idea?

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, Feb 01, 2016 at 07:31:42AM +0100, Rosario Contarino wrote:
> So,
>
> I select the option: "Test this media & install qubes"
>
> Screen is cleared, then:
>
> xen.gz ... ok
> vmlinux ... ok
> initrd.img ... ok
>
> then about 30 lines of console messages that end with (not the exact format)
> kernel panic ... not syncing ... attempted to kill init! exitcode 0x000009
>
> Any idea?

Only how to get more details:

In bootloader edit that entry (press "e"), then go to line with
"vmlinuz" and remove "rhgb quiet" from the end. Then you should get more
details why "init" was killed. You can try to capture the message with
some camera.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWrzq9AAoJENuP0xzK19csZ9EH/2xdFqhjItAKK044SDgZipTI
AWGL4MT2BRdu5PKpat6Ya7RHkzDQEwttvbI2piVA9qUkJ+EKue1+kOhFyhM4afXE
3WHYTZZpKQmG6qTfKOwN1XmIzDb57rf/mmN8WD11jnPTMaOCJdczEMCdGbft21wY
liKN5F5qv6gw1bwL82w3p57wL495D1lSm7Uj7j57W93zLCDyVKYtMe9vH7mKoFhv
pHV8kklWPNwuFQm6Dtj+/jMt/ExYunCyRhzVCsad3ABGpdauTLJ36kThlcXSF8QP
tNLXteDXXwO0pgiQ+YJZUiwvdJC9dSM6ok77BnDHXARBxlD9sXgTvsJtL4Nfhcc=
=5jA7
-----END PGP SIGNATURE-----

[Rosario Contarino]

attached you will find the best screenshot I could take.

please let me know if it is readable.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, Feb 01, 2016 at 12:52:55PM +0100, Rosario Contarino wrote:
> On 1 February 2016 at 12:00, Marek Marczykowski-Górecki <
> marm...@invisiblethingslab.com> wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > On Mon, Feb 01, 2016 at 07:31:42AM +0100, Rosario Contarino wrote:
> > > So,
> > >
> > > I select the option: "Test this media & install qubes"
> > >
> > > Screen is cleared, then:
> > >
> > > xen.gz ... ok
> > > vmlinux ... ok
> > > initrd.img ... ok
> > >
> > > then about 30 lines of console messages that end with (not the exact
> > format)
> > > kernel panic ... not syncing ... attempted to kill init! exitcode
> > 0x000009
> > >
> > > Any idea?
> >
> > Only how to get more details:
> >
> > In bootloader edit that entry (press "e"), then go to line with
> > "vmlinuz" and remove "rhgb quiet" from the end. Then you should get more
> > details why "init" was killed. You can try to capture the message with
> > some camera.
>
> attached you will find the best screenshot I could take.
>
> please let me know if it is readable.

Yes, it is perfectly readable. But the most important message is above
this one... Did you get anything from there? Even a single word...

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWr0nnAAoJENuP0xzK19cs3T0H/3StB3JNFwY1xbfwjCJUDXZS
UumUuiAACc0cJ01Be1DG2Ed95CDUkaAXNgleoTyc20lxqx8FjMKW6tRnTn7Mek22
bTnUB+zqeL5VjlCEaDBRM5V8d+MS9lgBhNcB8vFN52Yg3okhGE8aMfrVVMBU5rSW
WFL2vjtVBOjnp4iWf72FXK/1nTT6051cguYZtZc7y2uDSz7+T++aRb7eQxuGqlnH
fXhcbeArSY3yPgeu0/Hg69ViDz6P9oGNO1jDegm2Kxuvw7JEnSKqTnx7i7bDW9YK
Ubd7pN+fZ3dWaU6vfQX7yUtPM1+Dn+R7uRNdFrx0IINdGQqYdukNms/B2chwwUo=
=Oum7
-----END PGP SIGNATURE-----

[Rosario Contarino]

Prior the frame I sent you there are other four frames which you will find in attach with a name coherent with their timing (from 1 to 4). You already have the fifth frame.

Unfortunately those are barely readable because of the high persistence of the lcd and the relatively low quality of my camera (only 60fps).

Let me know if those frames give you more clue on why the installation process fails.

Thanks

[vladimi...@gmail.com]

Hi...that is exactly my problem too. I just write here to get by email the possible solution. Regards.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, Feb 01, 2016 at 02:37:12PM +0100, Rosario Contarino wrote:
> Prior the frame I sent you there are other four frames which you will find
> in attach with a name coherent with their timing (from 1 to 4). You already
> have the fifth frame.
>
> Unfortunately those are barely readable because of the high persistence of
> the lcd and the relatively low quality of my camera (only 60fps).
>
> Let me know if those frames give you more clue on why the installation
> process fails.

I guess frame3.jpg contains the message I need, but can't read it...

iQEcBAEBCAAGBQJWtLB5AAoJENuP0xzK19cs+6YIAI3P7yKU73dYggM++QR9Irpn
BcuXEyxzTG78QPzxZxu7KqrKFyk9veZhXDKn1LtKNHYv1kNcv/yg49lAcseDUINX
2f2SzuxWJwY6d508JlmUxZdNcTAgtlOE1SzDEr1uV2zeFoK2xk9Dhy5xde2oK21M
cpYkWyuybh2Jlb6g7AbqnArldlsr/1iryIYR57JWdBkPhRbkNqxPom1bRsc/pR9L
cqyODzecTZ77uErxAMP/HwDULND0AJVxK+zf8xXh/caCI+1pHWu4USAQgbX+TsRo
qBx5aJHX/ctr8CLndxhyR/IL92igirUr/gz+samD5tCkdRYmzIsNCuQwGqQ4/8g=
=EmQP
-----END PGP SIGNATURE-----

[R. D. Contarino]

Any way to shrink the logs in page four or five so that the log in page three gets visible?

---
R.D. Contarino

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Fri, Feb 05, 2016 at 05:46:16PM +0100, R. D. Contarino wrote:
> On February 5, 2016, 15:23, Marek Marczykowski-Górecki wrote:
>> On Mon, Feb 01, 2016 at 02:37:12PM +0100, Rosario Contarino wrote:
>>> Prior the frame I sent you there are other four frames which you will find
>>> in attach with a name coherent with their timing (from 1 to 4). You already
>>> have the fifth frame.
>>>
>>> Unfortunately those are barely readable because of the high persistence of
>>> the lcd and the relatively low quality of my camera (only 60fps).
>>>
>>> Let me know if those frames give you more clue on why the installation
>>> process fails.
>>
>> I guess frame3.jpg contains the message I need, but can't read it...
>

> Any way to shrink the logs in page four or five so that the log in page three gets visible?

I don't know any method to do that. Eric, do you know how to prevent (if
possible) printing stack trace etc on kernel panic and leave it only a
single line. Or not even that? Or maybe some other clever idea how to
debug this?

Context if you haven't seen those photos - there is kernel panic at boot
("Attempted to kill init!", signal 9), but anything that init has
written to the terminal is already outside of the screen (thanks to
stack trace and CPU state).

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWtOO3AAoJENuP0xzK19csf/4IAIxUnI4bdpLCbOERGr9YFdUl
c2WBjsRr0wZGeXyDDgza6/SOI6W0/xt8x6m9y7ozvLTGL22ngMYFk6TOL/Qec//C
GdaFqkbno1tuoCXvb+3Ocj3m0SOD6rSjmWIzzfhjWT1QXuD3GSF42h5JDUHA5R56
+HT6/3I0uR4TXx4lC1Kc6DENsvCSlUtkDe1UhxDcRw9rvI5LZ6EES9ktT/rQAaWZ
/l7i+OYASaUuRG4YQIxJoKDBKtpreUuvD2uCwvHx7NTEGL07ere1PZyWZgG3Q9Ts
gYkKAY+GpEzvnW1VYtPOD4i5iURXRuxOc3WoB3ttUAlTsdUL+aSrjKJV7tkqEqQ=
=CrHY
-----END PGP SIGNATURE-----

[Rosario Contarino]

Could any of those two option work?

* * *

Console Messages

Kernel Oops messages general contain a fair amount of information, ranging from register and process state dump and a stack dump too. Unfortunately the stack dump can be more than 25 lines and can scroll off the top of the 25 line Virtual Console. Hence to capture more of a Oops, try the following:

chvt 1
setfont /usr/share/consolefonts/Uni1-VGA8.psf.gz

Of course, one may still have a stack dump that scrolls the top of the Oops message off the console, so one trick is to rebuild the kernel with the stack dump removed, just to capture the initial Oops information. To do this, modify dump_stack in arch/x86/kernel/dumpstack_*.c and comment out the call to show_trace()

Slowing down kernel messages on boot

One may find a machine hangs during the kernel boot process and one would like to be able to see all the kernel messages but unfortunately they scroll off the console too quickly. One can slow down kernel console messages at boot time using by building the kernel with the following option enabled:

CONFIG_BOOT_PRINTK_DELAY=y

And boot the machine with the following kernel boot parameter:

boot_delay=N

where N = msecs delay between each console message.

* * *

(from https://wiki.ubuntu.com/Kernel/KernelDebuggingTricks)

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sat, Feb 06, 2016 at 11:47:46AM +0100, Rosario Contarino wrote:
> Could any of those two option work?
>
> * * *

> *Console Messages*
>
> *Kernel Oops messages general contain a fair amount of information, ranging

> from register and process state dump and a stack dump too. Unfortunately
> the stack dump can be more than 25 lines and can scroll off the top of the
> 25 line Virtual Console. Hence to capture more of a Oops, try the

> following: *
>
> *chvt 1
> setfont /usr/share/consolefonts/Uni1-VGA8.psf.gz*
>
> *Of course, one may still have a stack dump that scrolls the top of the

> Oops message off the console, so one trick is to rebuild the kernel with
> the stack dump removed, just to capture the initial Oops information. To do
> this, modify dump_stack in arch/x86/kernel/dumpstack_*.c and comment out

> the call to show_trace() *
>
> *Slowing down kernel messages on boot*
>
> *One may find a machine hangs during the kernel boot process and one would

> like to be able to see all the kernel messages but unfortunately they
> scroll off the console too quickly. One can slow down kernel console
> messages at boot time using by building the kernel with the following

> option enabled: *
>
> *CONFIG_BOOT_PRINTK_DELAY=y*
>
> *And boot the machine with the following kernel boot parameter: *
>
> *boot_delay=N*
>
> *where N = msecs delay between each console message. *
>
> * * *
> (from https://wiki.ubuntu.com/Kernel/KernelDebuggingTricks)

Yes, this is excellent idea! I totally forgot about boot_delay
parameter.

Try value like boot_delay=10, then capture messages using camera again
(adjust value if necessary).

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWte3iAAoJENuP0xzK19csM1kH/iKQ5Gmpqz2bL1weFjVgthdV
2MB1QSdft7gN9OhsCR4NedB0Y9Cdzz9uPuRyMaFedLzdZfm1L0FRbsCikDV4Ir7e
JLwMp3LYXFGeLi0db3TrDZbFpc7MpLdKxeHMKmlbsYgE0zb/Abn2SkC1k4x885cm
hbfA3og/zudJ0dfJ4YnSUaGejx9rjqpPyReE/ct/iEZQFvknz95ikD2ez/Psb6oi
p85Tc2R8w7oA+SdBUksMNg2lf4i9Ds11dgPcSn76WkUiTSkPob24qRlg20DZWw8J
H8BznGeJvK6gEcirVCcxDafbu2vxqCElyyeD27FjQSB2dAri6KEzPoCaSQLbP4k=
=KbjO
-----END PGP SIGNATURE-----

[unpar...@gmail.com]

I've got the same problem. Its a dell 11 3120 chromebook.

I get the same problem on the latest install usb and live alpha.

Have you got the info you need or do you want me to do it

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

> I've got the same problem. Its a dell 11 3120 chromebook.
>
> I get the same problem on the latest install usb and live alpha.
>
> Have you got the info you need or do you want me to do it

No, I haven't. Please try above boot_delay=10 trick.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJW+CDeAAoJENuP0xzK19csmH0H/jRFtbqR57eVGUDgqfdAb9pH
oIpCP9gpHbXILvizwP6yG5lyCxs0kRMET/4EwozIoFSklHSGve4zQU3Wy6HmrOOc
GnNOMZ8vI+vEK0qD81ebLlGWAU4vQUnH2QkyAZtzBv4kPBkze/D1uO0iNDi2zJHJ
mNcZjr0mHevTFUqpPi8rb8IMAPtxFpjQI90GuMYCIP0l3eZrh/9xf4zXcPyEPKZa
jvbpUafBCoaxpD9Mu6FJ8uEKxnHEERs1/dPRloZj+8uASRZLnIUHBZfeNYzMlRiT
FfuhASOcPDWFY5V1c4PgWoL9Md+tH4z7w0O28Fx5VykAoEVHnm0+QX/gXKXVfZE=
=46y5
-----END PGP SIGNATURE-----

[unpar...@gmail.com]

Sorry I don't know how to rebuild the kernel to get that boot delay thing working. If you guide me though what I need to do then I can have another go.

Here are some pictures for fun.

[url=http://postimg.org/image/hndak28s5/][img]http://s10.postimg.org/hndak28s5/1459123071466.jpg[/img][/url]

[url=http://postimg.org/image/g4hwf327p/][img]http://s10.postimg.org/g4hwf327p/1459123074177.jpg[/img][/url]

[url=http://postimg.org/image/nyii0ha0l/][img]http://s10.postimg.org/nyii0ha0l/1459123076377.jpg[/img][/url]

[url=http://postimg.org/image/9o8xozto5/][img]http://s10.postimg.org/9o8xozto5/1459124063605.jpg[/img][/url]

[unpar...@gmail.com]

Here is a better link http://postimg.org/gallery/imizp8di/

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

> > Sorry I don't know how to rebuild the kernel to get that boot delay thing working. If you guide me though what I need to do then I can have another go.

You don't need to rebuild anything, just add boot_delay=10 to kernel
command line. In grub you can press "e" to edit the entry, add the
option to the line with "vmlinuz", then press ctrl+x to boot it.

> > Here are some pictures for fun.
> >
> > [url=http://postimg.org/image/hndak28s5/][img]http://s10.postimg.org/hndak28s5/1459123071466.jpg[/img][/url]
> >
> > [url=http://postimg.org/image/g4hwf327p/][img]http://s10.postimg.org/g4hwf327p/1459123074177.jpg[/img][/url]
> >
> > [url=http://postimg.org/image/nyii0ha0l/][img]http://s10.postimg.org/nyii0ha0l/1459123076377.jpg[/img][/url]
> >
> > [url=http://postimg.org/image/9o8xozto5/][img]http://s10.postimg.org/9o8xozto5/1459124063605.jpg[/img][/url]
>
> Here is a better link http://postimg.org/gallery/imizp8di/

The problem is somewhere in __startup_pirq function(at least that's what
is on the screenshot). Which looks somehow different than the original
issue. Anyway top of that message would be useful.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJW+IFmAAoJENuP0xzK19csD/YH/1KYhzg4lbhi7tUlMNzUZQkW
RnOd7n2yKgI1xUwgbIWA72407NxTdVXXRfT+uCa9208/M4RMZdkCIUPjKrFYms3y
Td8i3Kc9laNUNf4XtBosktg+2eTf6DekDZOHHOPnPxYwjY7QL6XYhRfV1muE+bO9
2JHBTCXNTP2gcUdPAgqNibgpTSpkbQgbN4bR4xpn1UUTx4D8KFvrMxwMdZLlR311
rx2gFt0IyHQJUIgNedQM/4Hq8Vd972KEksXs+Oup5PwBwzUhvQmdX1C/uuxeOw3M
xtlSizyQRcmBo3M+iDhin+gLrWDm2xdyq+gsK2Yy3oNY0iXDglB/LftaELfxFUo=
=s+8P
-----END PGP SIGNATURE-----

[schow...@gmail.com]

>
> You don't need to rebuild anything, just add boot_delay=10 to kernel
> command line. In grub you can press "e" to edit the entry, add the
> option to the line with "vmlinuz", then press ctrl+x to boot it.
>

It looks as though this thread went nowhere. I'm having the same problem as the original poster above. I've tried creating an install USB with both Windows and Linux - same result.

I'm happy to try editing the edit kernel command line, but am hoping someone has solved this before I proceed. Please let me know if this problem wasn't solved.

Thanks,
Mike