Re: [ata crash] Re: Linux 2.6.25-rc1

2008-02-20 Thread Ingo Molnar
* Tejun Heo <[EMAIL PROTECTED]> wrote: > Tejun Heo wrote: > > Ingo Molnar wrote: > >> On a second attempt to boot the same bzImage, another ATA related > >> weirdness showed up: > >> > >> [8.226144] Calling initcall 0xc09f3d8e: isapnp_init+0x0/0xf() > >> [8.232017] Bad IO access at port

Re: [ata crash] Re: Linux 2.6.25-rc1

2008-02-20 Thread Tejun Heo
Tejun Heo wrote: > Ingo Molnar wrote: >> On a second attempt to boot the same bzImage, another ATA related >> weirdness showed up: >> >> [8.226144] Calling initcall 0xc09f3d8e: isapnp_init+0x0/0xf() >> [8.232017] Bad IO access at port 0x0 (outb(val,port)) >> [8.232799] [

Re: [ata crash] Re: Linux 2.6.25-rc1

2008-02-20 Thread Tejun Heo
Tejun Heo wrote: Ingo Molnar wrote: On a second attempt to boot the same bzImage, another ATA related weirdness showed up: [8.226144] Calling initcall 0xc09f3d8e: isapnp_init+0x0/0xf() [8.232017] Bad IO access at port 0x0 (outb(val,port)) [8.232799] [ cut here

Re: [ata crash] Re: Linux 2.6.25-rc1

2008-02-20 Thread Ingo Molnar
* Tejun Heo [EMAIL PROTECTED] wrote: Tejun Heo wrote: Ingo Molnar wrote: On a second attempt to boot the same bzImage, another ATA related weirdness showed up: [8.226144] Calling initcall 0xc09f3d8e: isapnp_init+0x0/0xf() [8.232017] Bad IO access at port 0x0

Re: [ata crash] Re: Linux 2.6.25-rc1

2008-02-13 Thread Tejun Heo
Ingo Molnar wrote: > On a second attempt to boot the same bzImage, another ATA related > weirdness showed up: > > [8.226144] Calling initcall 0xc09f3d8e: isapnp_init+0x0/0xf() > [8.232017] Bad IO access at port 0x0 (outb(val,port)) > [8.232799] [ cut here ] >

Re: [ata crash] Re: Linux 2.6.25-rc1

2008-02-13 Thread Ingo Molnar
* Arjan van de Ven <[EMAIL PROTECTED]> wrote: > btw this one was featured in the weekly bug top 10.. it's a rather > popular thing to happen. i didnt get very far with bisection. .23 definitely did not crash and booted up fine - but it produced the "Bad IO ..." messages - so my automated

Re: [ata crash] Re: Linux 2.6.25-rc1

2008-02-13 Thread Ingo Molnar
* Arjan van de Ven [EMAIL PROTECTED] wrote: btw this one was featured in the weekly bug top 10.. it's a rather popular thing to happen. i didnt get very far with bisection. .23 definitely did not crash and booted up fine - but it produced the Bad IO ... messages - so my automated bisector

Re: [ata crash] Re: Linux 2.6.25-rc1

2008-02-13 Thread Tejun Heo
Ingo Molnar wrote: On a second attempt to boot the same bzImage, another ATA related weirdness showed up: [8.226144] Calling initcall 0xc09f3d8e: isapnp_init+0x0/0xf() [8.232017] Bad IO access at port 0x0 (outb(val,port)) [8.232799] [ cut here ] [

Re: [ata crash] Re: Linux 2.6.25-rc1

2008-02-12 Thread Arjan van de Ven
On Tue, 12 Feb 2008 09:18:16 +0100 Ingo Molnar <[EMAIL PROTECTED]> wrote: > > hm, ata_port_wait_eh() started crashing on a testsystem (8-way box): > > [ 39.324116] Calling initcall 0xc09f41eb: legacy_init+0x0/0x888() > [ 39.331868] BUG: unable to handle kernel NULL pointer dereference > at

Re: [ata crash] Re: Linux 2.6.25-rc1

2008-02-12 Thread Arjan van de Ven
On Tue, 12 Feb 2008 09:18:16 +0100 Ingo Molnar [EMAIL PROTECTED] wrote: hm, ata_port_wait_eh() started crashing on a testsystem (8-way box): [ 39.324116] Calling initcall 0xc09f41eb: legacy_init+0x0/0x888() [ 39.331868] BUG: unable to handle kernel NULL pointer dereference at 00e4