Message-Id: <email address hidden>
Date: Wed, 04 Aug 2004 11:23:51 -0400
From: Andres Salomon <email address hidden>
To: Chris Jones <email address hidden>, <email address hidden>
Subject: Re: Bug#263420: kernel-image-2.6.7-1-686-smp: oppses while starting, during ACPI?
On Wed, 04 Aug 2004 10:46:00 +0100, Chris Jones wrote:
> Package: kernel-image-2.6.7-1-686-smp
> Version: 2.6.7-2
> Severity: critical
> Justification: breaks the whole system
>=20
> On booting the 2.6.7 smp kernel i recive errors after the line
>=20
> ACPI Revision 20040326
>=20
> This errors vary, this is an example
>=20
> ACPI Revision 20040326
> unable to handle NULL pointer dereferance <1> unable to handle kernel
> NULL pointer at virtual address 00000001
> printing eip
> 726566675
Is there a backtrace?
>=20
> I have also recived oopses, random asci strings (but no error) followed
> by hang, and messages about garbage stacks
>=20
> The non smp verson of this package boots, i include the output of dmesg
> for this kenel
Not all that interested in the non-oopsing kernel boot log; can you send
the boot log of the oopsing kernel? Also, you can try passing
acpi=3Doff to the kernel to keep it from oopsing. Alternatively, if it's
just the pci apci stuff that's causing problems (i've had problems w/ thi=
s
code), try pci=3Dnoacpi.
Message-Id: <email address hidden> image-2. 6.7-1-686- smp: oppses while starting, during ACPI?
Date: Wed, 04 Aug 2004 11:23:51 -0400
From: Andres Salomon <email address hidden>
To: Chris Jones <email address hidden>, <email address hidden>
Subject: Re: Bug#263420: kernel-
On Wed, 04 Aug 2004 10:46:00 +0100, Chris Jones wrote:
> Package: kernel- image-2. 6.7-1-686- smp
> Version: 2.6.7-2
> Severity: critical
> Justification: breaks the whole system
>=20
> On booting the 2.6.7 smp kernel i recive errors after the line
>=20
> ACPI Revision 20040326
>=20
> This errors vary, this is an example
>=20
> ACPI Revision 20040326
> unable to handle NULL pointer dereferance <1> unable to handle kernel
> NULL pointer at virtual address 00000001
> printing eip
> 726566675
Is there a backtrace?
>=20
> I have also recived oopses, random asci strings (but no error) followed
> by hang, and messages about garbage stacks
>=20
> The non smp verson of this package boots, i include the output of dmesg
> for this kenel
Not all that interested in the non-oopsing kernel boot log; can you send
the boot log of the oopsing kernel? Also, you can try passing
acpi=3Doff to the kernel to keep it from oopsing. Alternatively, if it's
just the pci apci stuff that's causing problems (i've had problems w/ thi=
s
code), try pci=3Dnoacpi.