Greg KH wrote:
Sure, here's the logs for when I boot 2.6.17 with your patch:
[--snip--]
[4294672.044000] ata_piix 0000:00:1f.2: version 1.05
[4294672.044000] ata_piix 0000:00:1f.2: MAP [ P0 P2 XX XX ]
[4294672.048000] ata_piix 0000:00:1f.2: invalid MAP value 0
[4294672.052000] ata_pci_init_one: ENTER
[4294672.055000] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 18
[4294672.059000] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[4294672.059000] ata_device_add: ENTER
[4294672.063000] ata_host_add: ENTER
[4294672.067000] ata_port_start: prd alloc, virt f7e55000, dma 37e55000
[4294672.070000] ata1: SATA max UDMA/133 cmd 0x1498 ctl 0x140E bmdma 0x1480 irq 18
[4294672.074000] ata_host_add: ENTER
[4294672.078000] ata_port_start: prd alloc, virt f7cfb000, dma 37cfb000
[4294672.081000] ata2: SATA max UDMA/133 cmd 0x1490 ctl 0x140A bmdma 0x1488 irq 18
[4294672.085000] ata_device_add: probe begin
[4294672.089000] ata_device_add: ata1: bus probe begin
[4294672.093000] piix_sata_probe: ata1: ENTER, pcs=0x11 base=0
[4294672.198000] piix_sata_probe: ata1: LEAVE, pcs=0x11 present_mask=0x1
[4294672.201000] ata_std_softreset: ENTER ata1
[4294672.205000] ata_std_softreset: about to softreset, devmask=3
[4294672.209000] ata_bus_softreset: ata1: bus reset via SRST
[4294672.364000] ata_dev_classify: found ATAPI device by sig
[4294672.367000] ata_dev_classify: found ATAPI device by sig
[4294672.371000] ata_std_softreset: EXIT, classes[0]=3 [1]=3
[4294672.375000] ata_std_postreset: ENTER
[4294672.378000] ata_std_postreset: EXIT
[4294672.382000] ata_dev_read_id: ENTER, host 1, dev 0
[4294672.537000] ata_exec_command_pio: ata1: cmd 0xA1
[4294672.543000] ata_pio_sector: data read
[4294672.546000] ata_dev_configure: ENTER, host 1, dev 0
[4294672.550000] ata1: dev 0 cfg 49:0f00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:0407
[4294672.550000] ata_dump_id: 49==0x0f00 53==0x0006 63==0x0007 64==0x0003 75==0x0000
[4294672.553000] ata_dump_id: 80==0x0078 81==0x0000 82==0x0000 83==0x0000 84==0x0000
[4294672.557000] ata_dump_id: 88==0x0407 93==0x4000
[4294672.560000] ata1: dev 0 ATAPI, max UDMA/33
[4294672.563000] ata1(0): applying bridge limits
[4294672.566000] ata_dev_configure: EXIT, drv_stat = 0x50
[4294672.569000] ata_dev_read_id: ENTER, host 1, dev 1
[4294672.723000] ata_exec_command_pio: ata1: cmd 0xA1
[4294672.726000] ata1: PIO error
[4294672.729000] ata1: dev 1 failed to IDENTIFY (I/O error)
Ah.. I see. IRQ-driven PIO times out while polling PIO detects it right
away.
Thanks. I'll push the fix to Jeff.
--
tejun
-
: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
