* Re: oops ACPI in Linux-2.6.6-bk1
[not found] <A6974D8E5F98D511BB910002A50A6647615FB4FE@hdsmsx403.hd.intel.com>
@ 2004-05-14 5:19 ` Len Brown
2004-05-14 14:57 ` Pat LaVarre
0 siblings, 1 reply; 5+ messages in thread
From: Len Brown @ 2004-05-14 5:19 UTC (permalink / raw)
To: Pat LaVarre; +Cc: kernelnewbies, linux-kernel
On Thu, 2004-05-13 at 11:02, Pat LaVarre wrote:
> > ACPI: Subsystem revision 20040326 ...
> > [<c01eef72>] acpi_ev_save_method_info+0x44/0x75 ...
> > Unable to handle kernel NULL pointer dereferencec01e1194 ...
> > Kernel panic: Aiee, killing interrupt handler! ...
> > Unable <o ha1dleUn kernel NULL pointer dereferenceer
> dereferenceOoops: ...
> > Unable to handle kernel NULL pointer dereference at virtual address
> ...
>
> Theory confirmed:
>
> Deleting CONFIG_ACPI=y etc. via `make xconfig` fixes this.
what theory?
There were no ACPI changes between 2.6.6 and 2.6.6-bk1.
Does 2.6.6 work for you?
-Len
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: oops ACPI in Linux-2.6.6-bk1
2004-05-14 5:19 ` oops ACPI in Linux-2.6.6-bk1 Len Brown
@ 2004-05-14 14:57 ` Pat LaVarre
2004-06-09 17:48 ` Pat LaVarre
0 siblings, 1 reply; 5+ messages in thread
From: Pat LaVarre @ 2004-05-14 14:57 UTC (permalink / raw)
To: len.brown; +Cc: kernelnewbies, linux-kernel
> There were no ACPI changes between 2.6.6 and 2.6.6-bk1.
The change my newbie eye sees here is that the effect of CONFIG_ACPI=y
changes from imperceptible in 2.6.6 to kernel won't boot in 2.6.6-bk1.
> Does 2.6.6 work for you?
2.6.6 works for me, yes, as did 2.6.5, 2.6.4, etc. ...
$ grep 'CONFIG_ACPI=' .config
CONFIG_ACPI=y
$ grep 'ACPI.*=y$' .config | grep -v '^#' | wc -l
16
$
The motherboard labels in front of me include:
"INTEL DESKTOP BOARD"
"D865GBF/D865PERC".
> > > ACPI: Subsystem revision 20040326 ...
> > > [<c01eef72>] acpi_ev_save_method_info+0x44/0x75 ...
> > > Unable to handle kernel NULL pointer dereferencec01e1194 ...
> > > Kernel panic: Aiee, killing interrupt handler! ...
> > > Unable <o ha1dleUn kernel NULL pointer dereferenceer
> > dereferenceOoops: ...
> > > Unable to handle kernel NULL pointer dereference at virtual address
> > ...
> >
> > Theory confirmed:
> >
> > Deleting CONFIG_ACPI=y etc. via `make xconfig` fixes this.
>
> what theory?
Thanks for making the time to say I was unclear.
In launching a thread titled "oops ACPI" I was guessing that lossy dmesg
spew appearing immediately past "ACPI: Subsystem revision 20040326" was
caused by me living too close to `make defconfig`. I then revisited
`make xconfig`, asked to turn off ACPI, and suddenly life got better.
I'm working from local copies of the kernel.org files:
$ ls -l *2.6.6*
-rw-rw-r-- 1 pat pat 34896138 May 10 11:14 linux-2.6.6.tar.bz2
-rw------- 1 pat pat 1072216 May 12 08:47 patch-2.6.6-bk1.bz2
$
I can fsck the containing volume, but I haven't yet otherwise learned
how to crc-check their integrity.
Pat LaVarre
^ permalink raw reply [flat|nested] 5+ messages in thread
* oops ACPI in Linux-2.6.6-bk1
@ 2004-05-12 15:28 Pat LaVarre
2004-05-13 15:02 ` Pat LaVarre
0 siblings, 1 reply; 5+ messages in thread
From: Pat LaVarre @ 2004-05-12 15:28 UTC (permalink / raw)
To: kernelnewbies; +Cc: linux-kernel
Linux-2.6.6-bk1 boot chokes here. Transcribed by hand, with conscious
omissions shown as ... ellipses:
// Trial 5:
schedule+0x608/0x60d
[<c01eef72>] acpi_ev_save_method_info+0x44/0x75
[<c01e94a2>] acpi_os_allocate+0xe/0x11
[<c01f7f59>] acpi_ns_get_next_node+x15/0x4e
... preempt_schedule...
... setup_irq...
... acpi_irq...
... acpi_irq...
... request_irq...
... acpi_os_install_interrupt_handler...
... acpi_irq...
... acpi_irq...
... acpi_ev_install_sci_handler...
... acpi_ev_sci_xrupt_handler...
... acpi_ev_handler_initialize...
... acpi_enable_subsystem...
... acpi_bus_init...
... acpi_init...
... do_initcalls...
... init_workqueues...
[<c0100363>] init+0x62/0x193
[<c0100301>] init+0x0/0x193
[<c01042a9>] kernel_thread_helper+0x5/0xb
// Trial 4:
ACPI: Subsystem revision 20040326
Unable to handle kernel NULL pointer dereferencec01e1194
*pde = 00000000
// Trial 3:
ACPI: Subsystem revision 20040326
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
// Trial 2:
ACPI: Subsystem revision 20040326
Unable <o ha1dleUn kernel NULL pointer dereferenceer dereferenceOoops:
49a0 [#1]
// Trial 1:
ACPI: Subsystem revision 20040326
Unable to handle kernel NULL pointer dereference at virtual address
00000038
printing eip:
c0118857
*pde = 00000000
Unable to handle kernel NULL pointer dereference at virtual address
00000034
printing eip:
C0107137
*pde = 00000000
// Often before the ACPI line I see:
...
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
// This is my first experience of any -bk release,
// risked for the sake of the new code of drivers/scsi/libata*
Enjoy, Pat LaVarre
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: oops ACPI in Linux-2.6.6-bk1
2004-05-12 15:28 Pat LaVarre
@ 2004-05-13 15:02 ` Pat LaVarre
0 siblings, 0 replies; 5+ messages in thread
From: Pat LaVarre @ 2004-05-13 15:02 UTC (permalink / raw)
To: kernelnewbies; +Cc: linux-kernel
> ACPI: Subsystem revision 20040326 ...
> [<c01eef72>] acpi_ev_save_method_info+0x44/0x75 ...
> Unable to handle kernel NULL pointer dereferencec01e1194 ...
> Kernel panic: Aiee, killing interrupt handler! ...
> Unable <o ha1dleUn kernel NULL pointer dereferenceer dereferenceOoops: ...
> Unable to handle kernel NULL pointer dereference at virtual address ...
Theory confirmed:
Deleting CONFIG_ACPI=y etc. via `make xconfig` fixes this.
Pat LaVarre
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-06-09 17:48 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <A6974D8E5F98D511BB910002A50A6647615FB4FE@hdsmsx403.hd.intel.com>
2004-05-14 5:19 ` oops ACPI in Linux-2.6.6-bk1 Len Brown
2004-05-14 14:57 ` Pat LaVarre
2004-06-09 17:48 ` Pat LaVarre
2004-05-12 15:28 Pat LaVarre
2004-05-13 15:02 ` Pat LaVarre
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox