I've upgraded from 3.2.9 to 3.3.1 and I face a kernel panic after the messages: "Decompressing Linux...Parsing ELF...done." and "Booting the kernel".
The error message is "PANIC : early exception 06 rip 10 : ffffffff81456a10 error 0 cr 2 0"
I'm running a laptop DELL XPS L501X.
In attach, you can find the output of lspci and lsusb.
Created attachment 72859 [details]
Created attachment 72860 [details]
I'm running archlinux. You can find the way the kernel is built here:
What other info should I put or action should I take to find where the problem could be ?
Ok, sorry for this report done too early. Seems it's already known in the distro and followed-up:
Mmmm, finally the bug mentionned above is not the problem (at least the workaroung mentionned don't work) -> reopening.
So, my original question remains: what other info should I put or action should I take to find where the problem could be ?
I'm seeing this too. Same hardware, running on Fedora 16 and Fedora 17 Alpha/Beta. Worked for me up to 3.2.10; the update to 3.3 then hit this bug.
It is something to do with the wifi driver: disabling wifi in the BIOS allows the machine to boot (but a laptop without wifi isn't much use).
Simply turning the wifi off with the soft key combo before the GRUB screen doesn't help. I'd hoped that I could get round it by turning it off with the key combo, and then turning it back on after booting, but the panic still happens. And if I turn it off in the BIOS, I can't then turn it back on with the key combo after booting.
Same problem on Dell XPS15/L501X. Had to disable BOTH the wifi and ethernet nic in bios. Disabling just wifi didn't work.
Exactly the same problem here, on the exact same hardware.
Assigned To: email@example.com
Why is this assigned to IA-64? The Dell XPS is an AMD 64-bit capable intel (i7 - i5 - i3) architecture.
So it should be x86-64 or i386 (IA 64 is itanium, i7 is not itanium).
I observed the bug with 64 bit kernel, did anyone use a 32 bit kernel?
@firstname.lastname@example.org: Indeed it's not Itanium but x86_64. Unfortunately I don't have authority to change the assignee.
@valere: Dare I suggest opening a new bug with the right architecture? The current assignee has not yet seen fit to comment or to reassign, and this won't get looked at otherwise.
If you do open a new bug, please post the link here so that we can copy our comments across and join in the game.
@j.heather: new bug entry created: https://bugzilla.kernel.org/show_bug.cgi?id=43098
Marking this one as duplicate
*** This bug has been marked as a duplicate of bug 43098 ***