lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 24 May 2007 10:32:49 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	linux-kernel@...r.kernel.org, stable@...nel.org
Cc:	mjw99@...ac.uk,
	"bugme-daemon@...nel-bugs.osdl.org" 
	<bugme-daemon@...zilla.kernel.org>, Andi Kleen <ak@...e.de>
Subject: Re: [Bugme-new] [Bug 8533] New: Panic on boot with early exception
 rip ffffffff8150a240 error 0 cr2 2260

On Thu, 24 May 2007 08:23:04 -0700
bugme-daemon@...zilla.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@...e.de
>          Submitter: mjw99@...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?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ