Bug 583010 - kernel-PAE-2.6.33.2-41 doesn't boot
Summary: kernel-PAE-2.6.33.2-41 doesn't boot
Keywords:
Status: CLOSED DUPLICATE of bug 583117
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: All
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-16 12:40 UTC by Fabian A. Scherschel
Modified: 2010-04-26 19:54 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-26 15:10:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Fabian A. Scherschel 2010-04-16 12:40:37 UTC
Description of problem:

kernel-PAE-2.6.33.2-41 doesn't boot on my system. SMOLT: http://www.smolts.org/client/show/pub_f3370e37-9d8a-4165-9ea3-dae4fa2972f7

Version-Release number of selected component (if applicable):

PAE 2.6.33.2-41

How reproducible:

100% - every boot


Steps to Reproduce:
1. Boot the machine with this kernel.
  
Actual results:
Machine hangs with a core dump immediately after GRUB.


Expected results:
Machine should boot.

Comment 1 Jason Montleon 2010-04-18 16:32:43 UTC
I experience the same with 2.6.33.2-41.fc13.x86_64

2.6.33.1-24.fc13.x86_64 and earlier work fine.

Comment 2 Chuck Ebbert 2010-04-19 22:21:23 UTC
(In reply to comment #2)
> Actual results:
> Machine hangs with a core dump immediately after GRUB.

That could be any of dozens of different problems. What does the "core dump" say?

Comment 3 Fabian A. Scherschel 2010-04-19 22:41:42 UTC
I can't copy and paste it because the machine hangs at the point. I could screenshot the few lines that show up (can't scroll) if that helps...

Comment 4 Fabian A. Scherschel 2010-04-19 22:42:46 UTC
Sorry, by "screenshot" I mean take a photo off the screen. ;)

Comment 5 Tommy He 2010-04-20 18:57:14 UTC
Confirmed this bug on my Asus F9DC with PAE kernel

http://www.smolts.org/client/show/pub_0b8133aa-815e-4c11-9e5f-f5ca20f88bb6

My friend running generic i686 kernel on Intel MacBook also has this problem.

Here is the photo of the error message.

http://goo.gl/iJGh

Two lines out of capture are:

async/0 used greatest stack depth 5696 bytes left
isapnp: No Plug & Play device found

The workaround is unplugging the battery and using AC power instead. Leaving the battery in the slot and using AC power will still trigger this error.

However, it is unacceptable for laptop users.

Comment 6 Jason 2010-04-20 19:19:53 UTC
removing the battery also allowed me to boot my system

Comment 7 jeff.mueller 2010-04-21 06:06:04 UTC
I'll add a "me too" on this... but I'm running 32-bit (i686) and not PAE kernel.  I'm not sure if it's appropriate to add this here or if I should open a new bug.  

While I didn't compare my trace/dump data to the photo attached by Tommy, the symptoms and circumvention are the same.  System is Thinkpad G41 (yup, it's old!) and, in case it matters, the battery was previously flagged as bad (<50% capacity).

Booting from 2.6.33.2-41.fc13.i686 fails with battery, works with battery removed.
Booting from 2.6.33.1-24.fc13.i686 (and earlier) works with or without battery.

Comment 8 Tommy He 2010-04-21 07:45:25 UTC
(In reply to comment #7)
> I'll add a "me too" on this... but I'm running 32-bit (i686) and not PAE
> kernel.  I'm not sure if it's appropriate to add this here or if I should open
> a new bug.  
> 
> While I didn't compare my trace/dump data to the photo attached by Tommy, the
> symptoms and circumvention are the same.  System is Thinkpad G41 (yup, it's
> old!) and, in case it matters, the battery was previously flagged as bad (<50%
> capacity).
> 
> Booting from 2.6.33.2-41.fc13.i686 fails with battery, works with battery
> removed.
> Booting from 2.6.33.1-24.fc13.i686 (and earlier) works with or without battery.    

Should I say that I am glad more people are aware of this bug ? :-P

I tested it on both i686 generic and PAE kernels, they share the same problem.
Not sure about x86_64 kernel though.

There seems to be a new kernel in updates-testing today. Let's see what it can do.

Comment 9 Tommy He 2010-04-21 08:32:36 UTC
Booting with 2.6.33.2-57 seems to be fine. Fixed by upstream ?

Comment 10 jeff.mueller 2010-04-21 15:42:18 UTC
Confirmed... booted fine with 2.6.33.2-57.fc13.i686 with battery installed.

Comment 11 Fabian A. Scherschel 2010-04-22 20:59:21 UTC
Yes, it's fixed. :)

Comment 12 Tommy He 2010-04-25 23:06:03 UTC
Great, now the fixed kernel 2.6.33.2-57.fc13.i686 disappears from the repository.

Comment 13 Carl G. 2010-04-26 02:17:57 UTC
(In reply to comment #12)
> Great, now the fixed kernel 2.6.33.2-57.fc13.i686 disappears from the
> repository.    

Care to explain ?
---

Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 14 Tommy He 2010-04-26 08:23:52 UTC
Before yesterday, the latest kernel available in the repository is 2.6.33.2-57, which fixed the problem reported here.

But on yesterday afternoon, the latest kernel available in the repository downgraded to 2.6.33.2-41, which caused this problem. It leaves the poor guy like me who just reinstalled the system suffers the problem again. :-(

Comment 15 Carl G. 2010-04-26 15:10:22 UTC
(In reply to comment #14)
> Before yesterday, the latest kernel available in the repository is 2.6.33.2-57,
> which fixed the problem reported here.
> 
> But on yesterday afternoon, the latest kernel available in the repository
> downgraded to 2.6.33.2-41, which caused this problem. It leaves the poor guy
> like me who just reinstalled the system suffers the problem again. :-(    

Tom, could you try to see if you _could_ get the update from another mirror ? The update as been pushed to stable :

bodhi - 2010-04-25 13:56:30
This update has been pushed to stable
---

Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

*** This bug has been marked as a duplicate of bug 583117 ***

Comment 16 Tommy He 2010-04-26 19:54:59 UTC
I(In reply to comment #15)
> (In reply to comment #14)
> > Before yesterday, the latest kernel available in the repository is 2.6.33.2-57,
> > which fixed the problem reported here.
> > 
> > But on yesterday afternoon, the latest kernel available in the repository
> > downgraded to 2.6.33.2-41, which caused this problem. It leaves the poor guy
> > like me who just reinstalled the system suffers the problem again. :-(    
> 
> Tom, could you try to see if you _could_ get the update from another mirror ?
> The update as been pushed to stable :
> 
> bodhi - 2010-04-25 13:56:30
> This update has been pushed to stable
> ---
> 
> Fedora Bugzappers volunteer triage team
> https://fedoraproject.org/wiki/BugZappers
> 
> *** This bug has been marked as a duplicate of bug 583117 ***    

It might take some for the mirror in UK to synchronize the packages. I will see what happens tomorrow.


Note You need to log in before you can comment on or make changes to this bug.