Bug#567985: [linux-source-2.6.32] kerneloops on boot if LBDAF not used
- To: Ben Hutchings <firstname.lastname@example.org>
- Cc: email@example.com
- Subject: Bug#567985: [linux-source-2.6.32] kerneloops on boot if LBDAF not used
- From: "Brent S. Elmer Ph.D." <firstname.lastname@example.org>
- Date: Tue, 02 Feb 2010 10:45:33 -0500
- Message-id: <1265125533.6126.2.camel@belmer>
- Reply-to: "Brent S. Elmer Ph.D." <email@example.com>, firstname.lastname@example.org
- In-reply-to: <1265060618.3479.6.camel@localhost>
- References: <1265044198.21192.72.camel@belmer> <1265060618.3479.6.camel@localhost>
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
On Mon, 2010-02-01 at 21:43 +0000, 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.