Tejun Heo wrote:
quoted text
> 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 ]------------
>> [    8.232799] WARNING: at lib/iomap.c:44 bad_io_access+0x2f/0x34()
>> [    8.232799] Pid: 1, comm: swapper Not tainted 2.6.25-rc1 #5
>> [    8.232799]  [<c011fd63>] warn_on_slowpath+0x3c/0x4c
>> [    8.232799]  [<c0358e9d>] ? serial8250_console_write+0x0/0x14e
>> [    8.232799]  [<c01200a5>] ? __call_console_drivers+0x56/0x63
>> [    8.232799]  [<c06b7acf>] ? _spin_unlock_irqrestore+0x15/0x21
>> [    8.232799]  [<c0120556>] ? release_console_sem+0x1c1/0x1c9
>> [    8.232799]  [<c015c400>] ? print_trailer+0x6e/0xfc
>> [    8.232799]  [<c015c77f>] ? check_object+0x10b/0x181
>> [    8.232799]  [<c01209a0>] ? printk+0x15/0x17
>> [    8.232799]  [<c02cc2ce>] bad_io_access+0x2f/0x34
>> [    8.232799]  [<c02cc48a>] iowrite8+0x31/0x34
>> [    8.232799]  [<c04a1c8d>] ata_bmdma_freeze+0x1d/0x30
>> [    8.232799]  [<c04a2063>] __ata_port_freeze+0x2c/0x33
>> [    8.232799]  [<c04a224f>] ata_eh_freeze_port+0x21/0x2f
>> [    8.232799]  [<c0497fa9>] ata_host_start+0xe1/0x132
> 
> Does the following patch fix the above problem?  pata_isapnp is the
> only one which can have NULL ctl_addr and libata SFF layer wasn't
> ready for that.

Ping.

-- 
tejun
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/