Description of problem: I installed kernel-3.2.1-3.fc16.i686 via the software update.When I rebooted using the new kernel it comes to the login screen and just hangs. After some times, it shows lot of information with Kernel Panic written in last.Older kernel ( kernel-3.2.1-3.fc16.i686 ) is working fine. Version-Release number of selected component (if applicable): kernel-3.2.1-3.fc16.i686 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: I am using Dell Inspiron Mini 1012 ( CPU : 1.6 GHz Intel Atom , 1 GB DDR2 RAM ) with triple-booting Ubuntu 11.10 ,Fedora 16 and Windows Xp Home Edition. The grub menu is via Ubuntu 11.10, so I ran update-grub using Ubuntu before rebooting into new Fedora kernel.
(In reply to comment #0) > Description of problem: > > I installed kernel-3.2.1-3.fc16.i686 via the software update.When I rebooted > using the new kernel it comes to the login screen and just hangs. After some > times, it shows lot of information with Kernel Panic written in last.Older > kernel ( kernel-3.2.1-3.fc16.i686 ) is working fine. I'm slightly confused. You said kernel-3.2.1-3.fc16.i686 is panicing, but then say it is working fine. I'm guessing you meant to list a different kernel version for the "Older kernel"? Do you have a stack trace to look at?
(In reply to comment #1) > (In reply to comment #0) > > Description of problem: > > > > I installed kernel-3.2.1-3.fc16.i686 via the software update.When I rebooted > > using the new kernel it comes to the login screen and just hangs. After some > > times, it shows lot of information with Kernel Panic written in last.Older > > kernel ( kernel-3.2.1-3.fc16.i686 ) is working fine. > > I'm slightly confused. You said kernel-3.2.1-3.fc16.i686 is panicing, but then > say it is working fine. I'm guessing you meant to list a different kernel > version for the "Older kernel"? > > Do you have a stack trace to look at? Oh.. sorry. I meant to say that the older kernel ( kernel-3.1.9-1.fc16.i686 ) is working fine and kernel-3.2.1-3.fc16.i686 is getting panic. Yes.. I do see a stack trace when it says Kenel Panic but I don't know how to save it or find it in logs...
(In reply to comment #2) > Oh.. sorry. I meant to say that the older kernel ( kernel-3.1.9-1.fc16.i686 ) > is working fine and kernel-3.2.1-3.fc16.i686 is getting panic. > > Yes.. I do see a stack trace when it says Kenel Panic but I don't know how to > save it or find it in logs... If you can see it, can you take a digital picture and attach it?
Created attachment 557312 [details] Image showing the Kernel Panic Image showing the Kernel Panic
The image there shows the last oops that happened and the D taint flag is already set. Can you try setting pause_on_oops=30 on the kernel command line to see if you can capture the first oops? Also, you might get better debugging output if you install kernel-debug and boot that.
Created attachment 557325 [details] Image showing the Kernel Panic while booting kernel-debug-3.2.1-3.fc16.i686
Created attachment 557326 [details] Image showing the Kernel Panic while booting kernel-3.2.1-3.fc16.i686 1st Pause During this boot pause_on_oops=30 was also set.
Created attachment 557329 [details] Image showing the Kernel Panic while booting kernel-3.2.1-3.fc16.i686 2nd and last pause During this boot pause_on_oops=30 was also set.
Exact same problem on my Atom based MSI Wind U100. Consistent kernel panic within seconds after successful boot and display of Gnome Shell (auto-login enabled).
Just wanted to say that I'm also having this problem on my Acer Aspire 5730Z after getting 3.2.1-3.fc16.i686, I get to the login screen but everything just freezes and crashes to command line but I can't Ctrl-C or switch to another tty or something like that so now I'm stuck on 3.1.9-1.fc16.i686. Space weather bug? :D
Unfortunately, I still can't see the beginning of the panic in the pictures provided. If anyone else with this problem has a serial console that can be used to capture the full trace that would be helpful. Other tricks include passing 'vga=791 pause_on_oops=30' on the kernel command line and removing 'rhgb quiet'. You might also try installing kernel-debug and booting that instead, as it has many debugging options turned on.
I just wanted to mention that I am also experiencing this exception here on Fedora (3.2.1-3.fc16.i686) 30 seconds after the login screen here. Fedora (3.1.9-1.fc16.i686) works fine just like Manish Raj describes. In common with those that have reported the problem I am also sitting on a laptop, in this case a HP Probook 4520s. http://i.imgur.com/y7MpY.jpg http://i.imgur.com/40Ht1.jpg Best Regards, Bastian
(In reply to comment #11) > Unfortunately, I still can't see the beginning of the panic in the pictures > provided. If anyone else with this problem has a serial console that can be > used to capture the full trace that would be helpful. Other tricks include > passing 'vga=791 pause_on_oops=30' on the kernel command line and removing > 'rhgb quiet'. > > You might also try installing kernel-debug and booting that instead, as it has > many debugging options turned on. Well.... when I tried passing " vga=791 pause_on_oops=30 " to boot option of kernel-debug-3.2.1-3.fc16.i686 ... it just booted perfectly ( I writing all these directly from this boot) ..... may be vga=791 did the trick..
(In reply to comment #13) > (In reply to comment #11) > > Unfortunately, I still can't see the beginning of the panic in the pictures > > provided. If anyone else with this problem has a serial console that can be > > used to capture the full trace that would be helpful. Other tricks include > > passing 'vga=791 pause_on_oops=30' on the kernel command line and removing > > 'rhgb quiet'. > > > > You might also try installing kernel-debug and booting that instead, as it has > > many debugging options turned on. > > Well.... when I tried passing " vga=791 pause_on_oops=30 " to boot option of > kernel-debug-3.2.1-3.fc16.i686 ... it just booted perfectly ( I writing all > these directly from this boot) ..... may be vga=791 did the trick.. If you drop the vga= part, does it still panic?
With a little bit help from #fedora I managed to record the exception with vga=791, rghb n' quiet removed and pause_on_oops=30. I hope you can make any use of the video: http://rvzt.net/Temp/exception.mkv (118MB) Best Regards, Bastian Hougaard
(In reply to comment #14) > If you drop the vga= part, does it still panic? No.. it doesn't . So, I tried to recreate the situation ( kernel panic ) and recover back from it . I found that When I boot into ubuntu it re-sync my system clock. If I then try to boot into Fedora kernel-3.2.1-3.fc16.i686 , it just refuses. When I checked my system clock via BIOS setting it was wrong.So I manually adjusted it. But that doesn't stopped the kernel panic. So, I went to my third boot-installtion of my system i.e. Windows Xp Home Edition and synced the clock using it. This time I was successfully boot into kernel-3.2.1-3.fc16.i686 without addtion of any extra option to kernel command line.
Now its getting totally intermittent i.e. sometimes I am able to successfully boot into kernel-3.2.1-3.fc16.i686 and sometimes it crashes. I am getting confused and annoyed by this....
I can figure that the video I uploaded previously wasn't very readable due to the poor quality. So I have now merged a picture of the whole kernel log: http://i.imgur.com/ISl73.jpg I hope I am to any help. Best Regards, Bastian Hougaard
Same problem on a Dell Latitude 2100 netbook (Atom CPU). Kernel panic, either during boot or shortly thereafter. I tries the following (one by one, no combinations), and none works vga=791 pause_on_oops=30, tpm_tis.interrupts=0 Both kernel and kernel-PAE behave exactly the same.
Just tried kernel-PAE-3.2.2-1.f16 from Koji, and the problem seems to be gone: machine is running for about 1 hour now.
(In reply to comment #20) > Just tried kernel-PAE-3.2.2-1.f16 from Koji, and the problem seems to be gone: > machine is running for about 1 hour now. Great to know. If the others could try that kernel, it would be appreciated. I'll be submitting an update for it later this morning in any case.
(In reply to comment #21) > > Great to know. If the others could try that kernel, it would be appreciated. > > I'll be submitting an update for it later this morning in any case. I can confirm that Koji's kernel-PAE-3.2.2-1.f16 doesn't have the issue. Thank you for the tip, Bert!
(In reply to comment #21) > (In reply to comment #20) > > Just tried kernel-PAE-3.2.2-1.f16 from Koji, and the problem seems to be gone: > > machine is running for about 1 hour now. > > Great to know. If the others could try that kernel, it would be appreciated. > > I'll be submitting an update for it later this morning in any case. Still no luck with kernel-3.2.1-3.fc16.i686 . It is sometimes booting without panic and sometimes it panics. So, I have decided to remove the kernel till the time an updated one is released. and yes... I tested Koji's kernel-3.2.2-1.fc16.i686 and it is working perfectly.. but will wait for a final release to use it fully on my system.
The problem disappeared with new kernel-3.2.2-1.fc16.i686
This problem exists in kernel-3.3.0-0.rc1.git4.1.fc17 as well (latest from koji).
The problem seems to have disappeared in new kernel ( kernel-3.2.2-1.fc16.i686 ). Its working absolutely fine. But, whatever the problem was is needed to be found out as it can re-appear in future releases if went un-diagnosed.
(In reply to comment #26) > The problem seems to have disappeared in new kernel ( kernel-3.2.2-1.fc16.i686 > ). Its working absolutely fine. > > But, whatever the problem was is needed to be found out as it can re-appear in > future releases if went un-diagnosed. You all likely got a different failure symptom with the ums-realtek error that was fixed with a different bug number. (In reply to comment #25) > This problem exists in kernel-3.3.0-0.rc1.git4.1.fc17 as well (latest from > koji). I'll include the patch we added to 3.2.2-1.fc16 in rawhide later today.
(In reply to comment #27) > (In reply to comment #25) > > This problem exists in kernel-3.3.0-0.rc1.git4.1.fc17 as well (latest from > > koji). > > I'll include the patch we added to 3.2.2-1.fc16 in rawhide later today. Tomorrow's rawhide build will have the fix I spoke of. I'm going to close this bug out as a duplicate of 784345. If any of you are still seeing this issue after the next f16 kernel update, please open a new bug with the relevant details. *** This bug has been marked as a duplicate of bug 784345 ***