Re: [Bugme-new] [Bug 8533] New: Panic on boot with early exception rip ffffffff8150a240 error 0 cr2 2260

Re: [Bugme-new] [Bug 8533] New: Panic on boot with early exception rip ffffffff8150a240 error 0 cr2 2260

[Andrew Morton]

On Thu, 24 May 2007 08:23:04 -0700
bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=8533
> 
>            Summary: Panic on boot with early exception rip ffffffff8150a240
>                     error 0 cr2 2260
>     Kernel Version: 2.6.21.2
>             Status: NEW
>           Severity: high
>              Owner: ak@suse.de
>          Submitter: mjw99@ic.ac.uk
> 
> 
> Most recent kernel where this bug did *NOT* occur:
> 2.6.18.3 (I've not tried anything between that and 2.6.21.2)
> 
> Distribution:
> [root@f02 ~]# more /etc/redhat-release
> Red Hat Enterprise Linux AS release 4 (Nahant Update 2)
> (but using a kernel.org kernel, not a redhat one)
> 
> Hardware Environment:
> 8CPU Dual Core Opteron; http://www.iwill.net/product_2.asp?p_id=90&sp=Y
> 
> Software Environment:
> Red Hat Enterprise Linux AS release 4 (Nahant Update 2)
> 
> Problem Description:
> Kernel Panics on boot with the following error message sequence:
> 
> Decompressing Linux...done.
> Booting the kernel.
> 
> 
> 
> Kernel alive
> kernel direct mapping tables up to 840000000 @ 8000-2a000
> PANIC: early exception rip ffffffff8150a240 error 0 cr2 2260
> 
> 
> 
> Steps to reproduce:
> 
> 1) Boot the kernel with flags
> kernel /vmlinuz-2.6.21.2 ro root=LABEL=/ selinux=0 console=ttyS0,57600 console=tty0
> 
> 2) Observe the above problem
> 

erk, -stable just went unstable.

hm, it occurred sometime between 2.6.18.3 and 2.6.21.2.  That's a huge
leap.  I don't suppose you'd have the time and inclination to run a
git-bisect search?

Re: [Bugme-new] [Bug 8533] New: Panic on boot with early exception rip ffffffff8150a240 error 0 cr2 2260

[Andi Kleen]

> > 
> > Kernel alive
> > kernel direct mapping tables up to 840000000 @ 8000-2a000
> > PANIC: early exception rip ffffffff8150a240 error 0 cr2 2260
> > 
> > 
> > 
> > Steps to reproduce:
> > 
> > 1) Boot the kernel with flags
> > kernel /vmlinuz-2.6.21.2 ro root=LABEL=/ selinux=0 console=ttyS0,57600 console=tty0
> > 
> > 2) Observe the above problem
> > 
> 
> erk, -stable just went unstable.

Multiple reports? Sometimes things seem to get "miscompiled" for random
reasons, so for really weird crashes I would suggest a make clean and try
again. 

> hm, it occurred sometime between 2.6.18.3 and 2.6.21.2.  That's a huge
> leap.  I don't suppose you'd have the time and inclination to run a
> git-bisect search?

And looking up ffffffff8150a240 in the System.map

-Andi