Bug#567985: [linux-source-2.6.32] kerneloops on boot if LBDAF not used

2010-02-02 Thread Brent S. Elmer Ph.D.
I submitted upstream as bug 15209.  I don't know how to get the oops
message as kerneloops is having problems which I submitted as Debian bug
567555.

Brent
On Mon, 2010-02-01 at 21:43 +, Ben Hutchings wrote:
 On Mon, 2010-02-01 at 12:09 -0500, Brent S. Elmer Ph.D. wrote:
  Package: linux-source-2.6.32
  Version: 2.6.32-5
  Severity: important
  
  --- Please enter the report below this line. ---
  I get a kerneloops on 2.6.32 kernels unless CONFIG_LBDAF is yes.  This is 
  on a Lenovo W500 thinkpad that only has a 150G 
  hard drive so there shouldn't be any need for LBDAF.  The kerneloops is 
  very early in the boot process.  I always build my 
  own kernels.  I copied the 2.6.30 kernel config for my current kernel to 
  the 2.6.32 source directory and did a make oldconfig.
  The resulting 2.6.32 kernel gave the kerneloops.  After a long process of 
  narrowing down what was causing the problem. 
  I found that LBDAF had to be used for the kernel to boot.
 
 Please report this upstream at http://bugzilla.kernel.org, including
 your full config and the oops message.  Let us know the bug number so we
 can track it.
 
 Ben.
 





-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#567985: [linux-source-2.6.32] kerneloops on boot if LBDAF not used

2010-02-01 Thread Brent S. Elmer Ph.D.
Package: linux-source-2.6.32
Version: 2.6.32-5
Severity: important

--- Please enter the report below this line. ---
I get a kerneloops on 2.6.32 kernels unless CONFIG_LBDAF is yes.  This is on a 
Lenovo W500 thinkpad that only has a 150G 
hard drive so there shouldn't be any need for LBDAF.  The kerneloops is very 
early in the boot process.  I always build my 
own kernels.  I copied the 2.6.30 kernel config for my current kernel to the 
2.6.32 source directory and did a make oldconfig.
The resulting 2.6.32 kernel gave the kerneloops.  After a long process of 
narrowing down what was causing the problem. 
I found that LBDAF had to be used for the kernel to boot.

--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.32.100131

Debian Release: squeeze/sid
  500 testing www.debian-multimedia.org 
  500 testing security.debian.org 
  500 testing debian.linux.ibm.com 
  500 jaunty  ppa.launchpad.net 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
binutils| 2.20-5
bzip2   | 1.0.5-4


Recommends  (Version) | Installed
=-+-===
libc6-dev | 2.10.2-2
 OR libc-dev  | 
gcc   | 4:4.3.4-1
make  | 3.81-7


Suggests(Version) | Installed
=-+-===
libncurses-dev| 
 OR ncurses-dev   | 
kernel-package| 12.032
libqt3-mt-dev | 3:3.3.8b-6









-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#567985: [linux-source-2.6.32] kerneloops on boot if LBDAF not used

2010-02-01 Thread Ben Hutchings
On Mon, 2010-02-01 at 12:09 -0500, Brent S. Elmer Ph.D. wrote:
 Package: linux-source-2.6.32
 Version: 2.6.32-5
 Severity: important
 
 --- Please enter the report below this line. ---
 I get a kerneloops on 2.6.32 kernels unless CONFIG_LBDAF is yes.  This is on 
 a Lenovo W500 thinkpad that only has a 150G 
 hard drive so there shouldn't be any need for LBDAF.  The kerneloops is very 
 early in the boot process.  I always build my 
 own kernels.  I copied the 2.6.30 kernel config for my current kernel to the 
 2.6.32 source directory and did a make oldconfig.
 The resulting 2.6.32 kernel gave the kerneloops.  After a long process of 
 narrowing down what was causing the problem. 
 I found that LBDAF had to be used for the kernel to boot.

Please report this upstream at http://bugzilla.kernel.org, including
your full config and the oops message.  Let us know the bug number so we
can track it.

Ben.

-- 
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein


signature.asc
Description: This is a digitally signed message part