* ATA Write Error and Time-out Notification in User Space
@ 2005-12-20 21:55 John Treubig
2005-12-20 22:50 ` Alan Cox
0 siblings, 1 reply; 12+ messages in thread
From: John Treubig @ 2005-12-20 21:55 UTC (permalink / raw)
To: linux-kernel, linux-scsi, linux-ide
[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]
Where would I look in the LibATA/SCSI chain to permit Write Error and
Time-out notification to be passed back to user space without hanging the
system?
BACKGROUND: We've implemented a disk drive testing system under 2.6 using
LibATA to access the ATA devices. During testing, we attach additional
"test" drives to the system and perform reads and writes to these drives.
The system drive is not part of the test environment. During testing we
expect to see errors reported (read, write and time-out) from the "test"
drives. When a SCSI disks report errors, the SCSI handlers perform as
expected, reporting the error and recovering. When ATA drives report
errors, only read errors recover and we are able to capture the error.
Write and time-out errors hang the system.
Hardware tested:
Promise Ultra133 TX2 (PDC20269 chip; pata_pdc2027x driver)
Kernel versions tested:
2.6.11
2.6.14 rc2
2.6.15 rc5
RECREATING THE PROBLEM: In our situation, we see the write and time-out
failures when we screen drives beyond their commercial temperature limits
for military applications using a custom application to read and write to
the "test" drives. Rather than having to have a drive in a special
temperature environment, the easiest way to simulate the failures is to
unplug power to a test drive while it is under test. The resulting errors
and time-outs will hang the system. Under this scenario, any type of read
or write to the "test" drive will fail the same as with our application.
I've attached copies of the system messages and startup-log to give further
details into the hangs.
---
Best wishes,
John Treubig
VT Miltope
Senior Test Engineer
(334) 613-6495
[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 15639 bytes --]
write back
[ 115.889416] ata_scsi_dump_cdb: CDB (2:0,0,0) 00 00 00 00 00 00 00 00 24
[ 115.916707] ata_scsiop_noop: ENTER
[ 115.943552] ata_scsi_dump_cdb: CDB (2:0,0,0) 25 00 00 00 00 00 00 00 00
[ 115.970878] ata_scsiop_read_cap: ENTER
[ 115.997800] SCSI device sdc: 78138047 512-byte hdwr sectors (40007 MB)
[ 116.025414] ata_scsi_dump_cdb: CDB (2:0,0,0) 5a 00 08 00 00 00 00 00 08
[ 116.053090] ata_scsiop_mode_sense: ENTER
[ 116.080352] ata_scsi_dump_cdb: CDB (2:0,0,0) 5a 00 08 00 00 00 00 00 24
[ 116.108002] ata_scsiop_mode_sense: ENTER
[ 116.135220] SCSI device sdc: drive cache: write back
[ 116.162352] sdc:<3>ata_scsi_dump_cdb: CDB (2:0,0,0) 28 00 00 00 00 00 00
00 08
[ 116.189890] ata_scsi_translate: ENTER
[ 116.217022] scsi_10_lba_len: ten-byte command
[ 116.244166] ata_sg_setup: ENTER, ata2
[ 116.271090] ata_sg_setup: 1 sg elements mapped
[ 116.297906] ata_fill_sg: PRD[0] = (0xFD0A000, 0x1000)
[ 116.324556] ata_dev_select: ENTER, ata2: device 0, wait 1
[ 116.351065] ata_tf_load_mmio: feat 0x0 nsect 0x8 lba 0x0 0x0 0x0
[ 116.377858] ata_tf_load_mmio: device 0xE0
[ 116.404290] ata_exec_command_mmio: ata2: cmd 0xC8
[ 116.431008] ata_scsi_translate: EXIT
[ 116.835832] ata_host_intr: ata2: host_stat 0x4
[ 116.862205] ata_host_intr: ata2: protocol 4 (dev_stat 0x50)
[ 116.888452] ata_sg_clean: unmapping 1 sg elements
[ 116.914752] ata_qc_complete: EXIT
[ 116.940787] unknown partition table
[ 116.966767] sd 4:0:0:0: Attached scsi disk sdc
[ 116.994509] sr0: scsi-1 drive
[ 117.020498] Uniform CD-ROM driver Revision: 3.20
[ 117.046702] sr 2:0:0:0: Attached scsi CD-ROM sr0
[ 117.046756] sd 0:0:6:0: Attached scsi generic sg0 type 0
[ 117.073246] sr 2:0:0:0: Attached scsi generic sg1 type 5
[ 117.099473] sd 3:0:0:0: Attached scsi generic sg2 type 0
[ 117.125325] sd 4:0:0:0: Attached scsi generic sg3 type 0
[ 117.150525] Fusion MPT base driver 3.03.04
[ 117.175476] Copyright (c) 1999-2005 LSI Logic Corporation
[ 117.200672] Fusion MPT SPI Host driver 3.03.04
[ 117.225785] Fusion MPT FC Host driver 3.03.04
[ 117.250437] Fusion MPT SAS Host driver 3.03.04
[ 117.274695] Fusion MPT misc device (ioctl) driver 3.03.04
[ 117.298994] mptctl: Registered with Fusion MPT base driver
[ 117.323331] mptctl: /dev/mptctl @ (major,minor=10,220)
[ 117.348061] ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
[ 117.372545] ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [APCL] -> GSI 22
(level, high) -> IRQ 20
[ 117.397705] PCI: Setting latency timer of device 0000:00:02.2 to 64
[ 117.397709] ehci_hcd 0000:00:02.2: EHCI Host Controller
[ 117.422670] ehci_hcd 0000:00:02.2: debug port 1
[ 117.447214] PCI: cache line size of 64 is not supported by device
0000:00:02.2
[ 117.447282] ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus
number 1
[ 117.472256] ehci_hcd 0000:00:02.2: irq 20, io mem 0xe0005000
[ 117.496766] ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10
Dec 2004
[ 117.521393] hub 1-0:1.0: USB hub found
[ 117.545622] hub 1-0:1.0: 6 ports detected
[ 117.670136] ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI)
Driver (PCI)
[ 117.670519] ACPI: PCI Interrupt Link [APCF] enabled at IRQ 21
[ 117.694783] ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 21
(level, high) -> IRQ 21
[ 117.719857] PCI: Setting latency timer of device 0000:00:02.0 to 64
[ 117.719861] ohci_hcd 0000:00:02.0: OHCI Host Controller
[ 117.744608] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus
number 2
[ 117.769437] ohci_hcd 0000:00:02.0: irq 21, io mem 0xe0003000
[ 117.846898] hub 2-0:1.0: USB hub found
[ 117.871420] hub 2-0:1.0: 3 ports detected
[ 117.996976] ACPI: PCI Interrupt Link [APCG] enabled at IRQ 20
[ 118.021855] ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCG] -> GSI 20
(level, high) -> IRQ 22
[ 118.047521] PCI: Setting latency timer of device 0000:00:02.1 to 64
[ 118.047524] ohci_hcd 0000:00:02.1: OHCI Host Controller
[ 118.072995] ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus
number 3
[ 118.098933] ohci_hcd 0000:00:02.1: irq 22, io mem 0xe0004000
[ 118.177418] hub 3-0:1.0: USB hub found
[ 118.203101] hub 3-0:1.0: 3 ports detected
[ 118.329153] USB Universal Host Controller Interface driver v2.3
[ 118.355385] usbcore: registered new driver usblp
[ 118.381437] drivers/usb/class/usblp.c: v0.13: USB Printer Device Class
driver
[ 118.408307] Initializing USB Mass Storage driver...
[ 118.435370] usbcore: registered new driver usb-storage
[ 118.462560] USB Mass Storage support registered.
[ 118.489815] usbcore: registered new driver usbhid
[ 118.517024] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[ 118.544622] mice: PS/2 mouse device common for all mice
[ 118.573058] NET: Registered protocol family 2
[ 118.609747] IP route cache hash table entries: 4096 (order: 2, 16384
bytes)
[ 118.639384] TCP established hash table entries: 16384 (order: 4, 65536
bytes)
[ 118.669324] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
[ 118.699306] TCP: Hash tables configured (established 16384 bind 16384)
[ 118.729249] TCP reno registered
[ 118.759060] ip_conntrack version 2.4 (2047 buckets, 16376 max) - 212
bytes per conntrack
[ 118.798121] input: AT Translated Set 2 keyboard as /class/input/input0
[ 118.845373] ip_tables: (C) 2000-2002 Netfilter core team
[ 118.918268] ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>.
http://snowman.net/projects/ipt_recent/
[ 118.951157] arp_tables: (C) 2002 David S. Miller
[ 118.992131] TCP bic registered
[ 119.024260] NET: Registered protocol family 1
[ 119.056060] NET: Registered protocol family 17
[ 119.087602] Using IPI Shortcut mode
[ 119.341785] input: ImPS/2 Generic Wheel Mouse as /class/input/input1
[ 119.543784] VFS: Mounted root (ext2 filesystem) readonly.
[ 119.575808] Freeing unused kernel memory: 216k freed
[ 124.822183] Adding 1188800k swap on /dev/hda3. Priority:-1 extents:1
across:1188800k
[ 125.145728] radDIO: module license 'unspecified' taints kernel.
[ 125.152977] RAD-DIO driver for NuDAQ PCI-7224 V1.0
[ 125.152982] Developed for Miltope Corp. by Radical Systems, Inc.
[ 125.152984] http://www.radicalsystems.com
[ 125.152986] Copyright (c) 2004, Radical Systems, Inc.
[ 125.152988] All rights reserved.
[ 125.159787] Probing...
[ 125.159808] ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [APC3] -> GSI 18
(level, high) -> IRQ 19
[ 125.159819] Found Device:
[ 125.159821] Name: 0000:01:06.0
[ 125.159823] InitFlag: 0x7248
[ 125.159824] BusNo: 0x1
[ 125.159826] DevFunc: 0x30
[ 125.159827] LCRBase: 0x7000
[ 125.159829] BaseAddr: 0x7400
[ 125.159830] IRQ No: 0x5
[ 125.218473] sata_promise 0000:01:0a.0: version 1.03
[ 125.218503] ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC3] -> GSI 18
(level, high) -> IRQ 19
[ 125.228953] ata_device_add: ENTER
[ 125.228955] ata_host_add: ENTER
[ 125.228996] ata_port_start: prd alloc, virt cf01a000, dma f01a000
[ 125.229001] ata5: SATA max UDMA/133 cmd 0xD086A200 ctl 0xD086A238 bmdma
0x0 irq 19
[ 125.229006] ata_host_add: ENTER
[ 125.229023] ata_port_start: prd alloc, virt cf195000, dma f195000
[ 125.229027] ata6: SATA max UDMA/133 cmd 0xD086A280 ctl 0xD086A2B8 bmdma
0x0 irq 19
[ 125.229032] ata_host_add: ENTER
[ 125.229049] ata_port_start: prd alloc, virt cf025000, dma f025000
[ 125.229053] ata7: SATA max UDMA/133 cmd 0xD086A300 ctl 0xD086A338 bmdma
0x0 irq 19
[ 125.229058] ata_host_add: ENTER
[ 125.229076] ata_port_start: prd alloc, virt cf21d000, dma f21d000
[ 125.229080] ata8: SATA max UDMA/133 cmd 0xD086A380 ctl 0xD086A3B8 bmdma
0x0 irq 19
[ 125.229087] ata_device_add: probe begin
[ 125.229089] ata_device_add: ata5: probe begin
[ 125.429660] ata5: no device found (phy stat 00000000)
[ 125.429663] ata_device_add: ata5: probe end
[ 125.429666] scsi7 : sata_promise
[ 125.436545] ata_device_add: ata6: probe begin
[ 125.637365] ata_bus_reset: ENTER, host 6, port 1
[ 125.637377] ata_bus_softreset: ata6: bus reset via SRST
[ 125.893001] ata_dev_classify: found ATA device by sig
[ 125.893022] ata_bus_reset: EXIT
[ 125.893024] ata_dev_identify: ENTER, host 6, dev 0
[ 125.893027] ata_dev_select: ENTER, ata6: device 0, wait 1
[ 125.893054] ata_dev_identify: do ATA identify
[ 125.893057] pdc_qc_prep: ENTER
[ 125.893059] ata_dev_select: ENTER, ata6: device 0, wait 1
[ 125.893110] ata_exec_command_mmio: ata6: cmd 0xEC
[ 125.895981] ata_pio_sector: data read
[ 125.896332] ata_qc_complete: EXIT
[ 125.896346] ata6: dev 0 cfg 49:2f00 82:346b 83:5b01 84:4003 85:3469
86:1801 87:4003 88:407f
[ 125.896350] ata_dump_id: 49==0x2f00 53==0x0007 63==0x0007 64==0x0003
75==0x0000
[ 125.896353] ata_dump_id: 80==0x007e 81==0x001b 82==0x346b 83==0x5b01
84==0x4003
[ 125.896356] ata_dump_id: 88==0x407f 93==0x604f
[ 125.896360] ata6: dev 0 ATA-6, max UDMA/133, 234441648 sectors: LBA
[ 125.896364] ata_dev_identify: EXIT, drv_stat = 0x50
[ 125.896366] ata6(0): applying bridge limits
[ 125.896369] ata_dev_identify: ENTER/EXIT (host 6, dev 1) -- nodev
[ 125.896373] ata_host_set_pio: base 0x8 xfer_mode 0xc mask 0x1f x 4
[ 125.896378] ata_dev_set_xfermode: set features - xfer mode
[ 125.896380] pdc_qc_prep: ENTER
[ 125.896383] pdc_packet_start: ENTER, ap cf6ca284
[ 125.896514] pdc_interrupt: ENTER
[ 125.896517] pdc_interrupt: port 0
[ 125.896519] pdc_interrupt: port 1
[ 125.896533] ata_qc_complete: EXIT
[ 125.896535] pdc_interrupt: port 2
[ 125.896536] pdc_interrupt: port 3
[ 125.896538] pdc_interrupt: EXIT
[ 125.896540] ata_dev_set_xfermode: EXIT
[ 125.896543] ata_dev_set_mode: idx=5 xfer_shift=0, xfer_mode=0x45,
base=0x40, offset=5
[ 125.896546] ata6: dev 0 configured for UDMA/100
[ 125.896548] ata_device_add: ata6: probe end
[ 125.896550] scsi8 : sata_promise
[ 125.903442] ata_device_add: ata7: probe begin
[ 126.103668] ata7: no device found (phy stat 00000000)
[ 126.103671] ata_device_add: ata7: probe end
[ 126.103674] scsi9 : sata_promise
[ 126.110431] ata_device_add: ata8: probe begin
[ 126.310364] ata8: no device found (phy stat 00000000)
[ 126.310367] ata_device_add: ata8: probe end
[ 126.310370] scsi10 : sata_promise
[ 126.317094] ata_device_add: probe begin
[ 126.317175] ata_scsi_dump_cdb: CDB (6:0,0,0) 12 00 00 00 24 00 00 00 00
[ 126.317179] ata_scsiop_inq_std: ENTER
[ 126.317216] ata_scsi_dump_cdb: CDB (6:0,0,0) 12 00 00 00 60 00 00 00 00
[ 126.317219] ata_scsiop_inq_std: ENTER
[ 126.317233] Vendor: ATA Model: ST3120023AS Rev: 3.01
[ 126.317241] Type: Direct-Access ANSI SCSI
revision: 05
[ 126.324097] ata_scsi_dump_cdb: CDB (6:0,0,0) 00 00 00 00 00 00 00 00 00
[ 126.324103] ata_scsiop_noop: ENTER
[ 126.324133] ata_scsi_dump_cdb: CDB (6:0,0,0) 25 00 00 00 00 00 00 00 00
[ 126.324136] ata_scsiop_read_cap: ENTER
[ 126.324146] SCSI device sdd: 234441648 512-byte hdwr sectors (120034 MB)
[ 126.324154] ata_scsi_dump_cdb: CDB (6:0,0,0) 5a 00 08 00 00 00 00 00 08
[ 126.324157] ata_scsiop_mode_sense: ENTER
[ 126.324168] ata_scsi_dump_cdb: CDB (6:0,0,0) 5a 00 08 00 00 00 00 00 24
[ 126.324171] ata_scsiop_mode_sense: ENTER
[ 126.324176] SCSI device sdd: drive cache: write back
[ 126.330966] ata_scsi_dump_cdb: CDB (6:0,0,0) 00 00 00 00 00 00 00 00 24
[ 126.330972] ata_scsiop_noop: ENTER
[ 126.331003] ata_scsi_dump_cdb: CDB (6:0,0,0) 25 00 00 00 00 00 00 00 00
[ 126.331006] ata_scsiop_read_cap: ENTER
[ 126.331016] SCSI device sdd: 234441648 512-byte hdwr sectors (120034 MB)
[ 126.331023] ata_scsi_dump_cdb: CDB (6:0,0,0) 5a 00 08 00 00 00 00 00 08
[ 126.331026] ata_scsiop_mode_sense: ENTER
[ 126.331037] ata_scsi_dump_cdb: CDB (6:0,0,0) 5a 00 08 00 00 00 00 00 24
[ 126.331040] ata_scsiop_mode_sense: ENTER
[ 126.331045] SCSI device sdd: drive cache: write back
[ 126.331048] sdd:<3>ata_scsi_dump_cdb: CDB (6:0,0,0) 28 00 00 00 00 00 00
00 08
[ 126.331079] ata_scsi_translate: ENTER
[ 126.331083] scsi_10_lba_len: ten-byte command
[ 126.331087] ata_sg_setup: ENTER, ata6
[ 126.331090] ata_sg_setup: 1 sg elements mapped
[ 126.331093] pdc_qc_prep: ENTER
[ 126.331096] ata_fill_sg: PRD[0] = (0xF74E000, 0x1000)
[ 126.331099] pdc_packet_start: ENTER, ap cf6ca284
[ 126.331104] ata_scsi_translate: EXIT
[ 126.352866] pdc_interrupt: ENTER
[ 126.352870] pdc_interrupt: port 0
[ 126.352872] pdc_interrupt: port 1
[ 126.352888] ata_sg_clean: unmapping 1 sg elements
[ 126.352890] ata_qc_complete: EXIT
[ 126.352892] pdc_interrupt: port 2
[ 126.352894] pdc_interrupt: port 3
[ 126.352895] pdc_interrupt: EXIT
[ 126.352906] unknown partition table
[ 126.352939] sd 8:0:0:0: Attached scsi disk sdd
[ 126.366494] sd 8:0:0:0: Attached scsi generic sg4 type 0
[ 126.366520] ata_device_add: EXIT, returning 4
[ 126.830077] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.830291] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.830583] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.830829] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.880736] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.880757] ata_scsi_dump_cdb: CDB (1:0,0,0) 12 01 80 00 60 00 00 00 24
[ 126.880780] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.880788] ata_scsi_dump_cdb: CDB (1:0,0,0) 12 00 00 00 60 00 00 00 24
[ 126.880791] ata_scsiop_inq_std: ENTER
[ 126.880826] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.880834] ata_scsi_dump_cdb: CDB (1:0,0,0) 12 01 83 00 60 00 00 00 24
[ 126.880857] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.880864] ata_scsi_dump_cdb: CDB (1:0,0,0) 12 01 80 00 60 00 00 00 24
[ 126.914346] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.914367] ata_scsi_dump_cdb: CDB (2:0,0,0) 12 01 80 00 60 00 00 00 24
[ 126.914391] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.914398] ata_scsi_dump_cdb: CDB (2:0,0,0) 12 00 00 00 60 00 00 00 24
[ 126.914401] ata_scsiop_inq_std: ENTER
[ 126.914435] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.914443] ata_scsi_dump_cdb: CDB (2:0,0,0) 12 01 83 00 60 00 00 00 24
[ 126.914486] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.914493] ata_scsi_dump_cdb: CDB (2:0,0,0) 12 01 80 00 60 00 00 00 24
[ 126.947093] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.947114] ata_scsi_dump_cdb: CDB (6:0,0,0) 12 01 80 00 60 00 00 00 24
[ 126.947137] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.947145] ata_scsi_dump_cdb: CDB (6:0,0,0) 12 00 00 00 60 00 00 00 24
[ 126.947148] ata_scsiop_inq_std: ENTER
[ 126.947182] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.947189] ata_scsi_dump_cdb: CDB (6:0,0,0) 12 01 83 00 60 00 00 00 24
[ 126.947213] program scsi_unique_id is using a deprecated SCSI ioctl,
please convert it to SG_IO
[ 126.947221] ata_scsi_dump_cdb: CDB (6:0,0,0) 12 01 80 00 60 00 00 00 24
[ 127.560220] kjournald starting. Commit interval 5 seconds
[ 127.560297] EXT3 FS on hda1, internal journal
[ 127.560303] EXT3-fs: mounted filesystem with ordered data mode.
[ 139.382882] r8169: eth0: link up
[-- Attachment #3: messages1.gz --]
[-- Type: application/x-gzip, Size: 12140 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ATA Write Error and Time-out Notification in User Space
2005-12-20 21:55 ATA Write Error and Time-out Notification in User Space John Treubig
@ 2005-12-20 22:50 ` Alan Cox
2005-12-21 0:31 ` Drew Winstel
0 siblings, 1 reply; 12+ messages in thread
From: Alan Cox @ 2005-12-20 22:50 UTC (permalink / raw)
To: John Treubig; +Cc: linux-kernel, linux-scsi, linux-ide
On Maw, 2005-12-20 at 15:55 -0600, John Treubig wrote:
> Where would I look in the LibATA/SCSI chain to permit Write Error and
> Time-out notification to be passed back to user space without hanging the
> system?
Some background first:
The 2.6 block layer can generally handle passing errors back up. It has
a load of problems with EOF on media that is variable size but block
that need fixing but the fundamental errors get back to the block layer.
Unfortunately although they get back to the block request the full error
is not propogated further up the stack. Thats actually tricky for the
general file system case as I/O as asynchronous to the actual file
system accesses and we may even hit errors on pages we didn't actually
need.
One result of that is that on write errors we generally mark a volume
offline and processes accessing it get stuck.
> drives. When a SCSI disks report errors, the SCSI handlers perform as
> expected, reporting the error and recovering. When ATA drives report
> errors, only read errors recover and we are able to capture the error.
> Write and time-out errors hang the system.
The problem with the file system layer at this point is it isn't clear
how you get the device back. What you should see is a sequence of
retries and then the volume going offline.
I don't know how complete your log is but it doesn't end with the
expected 'giving up' and volume offlining. Is that because the final
messages don't hit the log or are they just not seen ? The promise
devices have some "interesting" behaviour when you reset the chip.
There is a second problem with PATA too. If the drive decides to keel
over asserting IORDY its game over. The bus transactions will hang and
the CPU get stuck. That would _not_ be my first suspicion however.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ATA Write Error and Time-out Notification in User Space
2005-12-20 22:50 ` Alan Cox
@ 2005-12-21 0:31 ` Drew Winstel
2005-12-22 1:09 ` Alan Cox
0 siblings, 1 reply; 12+ messages in thread
From: Drew Winstel @ 2005-12-21 0:31 UTC (permalink / raw)
To: linux-ide; +Cc: Alan Cox, John Treubig, linux-kernel, linux-scsi
Hi Alan,
On Tuesday, December 20, 2005 16:50, Alan Cox wrote:
> On Maw, 2005-12-20 at 15:55 -0600, John Treubig wrote:
> > Where would I look in the LibATA/SCSI chain to permit Write Error and
> > Time-out notification to be passed back to user space without hanging the
> > system?
>
> Some background first:
>
> The 2.6 block layer can generally handle passing errors back up. It has
> a load of problems with EOF on media that is variable size but block
> that need fixing but the fundamental errors get back to the block layer.
>
> Unfortunately although they get back to the block request the full error
> is not propogated further up the stack. Thats actually tricky for the
> general file system case as I/O as asynchronous to the actual file
> system accesses and we may even hit errors on pages we didn't actually
> need.
>
> One result of that is that on write errors we generally mark a volume
> offline and processes accessing it get stuck.
>
With the application that John is using (namely, it delivers reads and writes
directly to the drive via various SG ioctls), the file system is not an
issue, hence wanting the errors to be returned to userspace.
I presume this means that John would have to look at the block level error
handling as opposed to the SCSI level?
<snip>
Drew
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ATA Write Error and Time-out Notification in User Space
2005-12-21 0:31 ` Drew Winstel
@ 2005-12-22 1:09 ` Alan Cox
0 siblings, 0 replies; 12+ messages in thread
From: Alan Cox @ 2005-12-22 1:09 UTC (permalink / raw)
To: Drew Winstel; +Cc: linux-ide, John Treubig, linux-kernel, linux-scsi
On Maw, 2005-12-20 at 18:31 -0600, Drew Winstel wrote:
> With the application that John is using (namely, it delivers reads and writes
> directly to the drive via various SG ioctls), the file system is not an
> issue, hence wanting the errors to be returned to userspace.
>
> I presume this means that John would have to look at the block level error
> handling as opposed to the SCSI level?
If you are using the sg ioctls then the commands are dispatched and the
results come through the request queues but not the block layer above.
In that case you really shouldn't be seeing a hang.
Alan
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ATA Write Error and Time-out Notification in User Space
@ 2006-01-03 18:29 John Treubig
2006-01-03 18:58 ` Alan Cox
0 siblings, 1 reply; 12+ messages in thread
From: John Treubig @ 2006-01-03 18:29 UTC (permalink / raw)
To: alan, raw; +Cc: linux-ide, linux-kernel, linux-scsi
[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]
Alan,
Happy new year and many thanks for your help. I took the information from
the prior submissions and wanted to see if the Promise sub-system was my
failure point. I put a drive on the Secondary IDE bus hanging off the
motherboard Nvidia NForce 2 controller, began an access and pulled the plug.
Sure enough the failures occured and were passed back to user level, but
the system did not hang. I've repeated this a number of times. I moved the
same drive to the Promise Controller and the hang occurs. Thus it seems we
have proved the Promise sub-system is my problem.
You suggested the something like IORDY hanging was not likely the problem.
Given the data, what would you suspect? I've included the message logs for
the NForce for comparison.
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Drew Winstel <raw@dslr.net>
CC: linux-ide@vger.kernel.org, John Treubig
<jtreubig@hotmail.com>,linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: ATA Write Error and Time-out Notification in User Space
Date: Thu, 22 Dec 2005 01:09:16 +0000
On Maw, 2005-12-20 at 18:31 -0600, Drew Winstel wrote:
> With the application that John is using (namely, it delivers reads and
writes
> directly to the drive via various SG ioctls), the file system is not an
> issue, hence wanting the errors to be returned to userspace.
>
> I presume this means that John would have to look at the block level
error
> handling as opposed to the SCSI level?
If you are using the sg ioctls then the commands are dispatched and the
results come through the request queues but not the block layer above.
In that case you really shouldn't be seeing a hang.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: failure.txt --]
[-- Type: text/plain, Size: 14965 bytes --]
Jan 3 10:35:43 localhost kernel: [ 1326.485012] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 00 00 00 60 00 44 ce 00
Jan 3 10:35:43 localhost kernel: [ 1326.485018] ata_scsiop_inq_std: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.485248] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 01 00 00 fc 00 44 ce 58
Jan 3 10:35:43 localhost kernel: [ 1326.485358] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 01 80 00 fc 00 44 ce 58
Jan 3 10:35:43 localhost kernel: [ 1326.485403] ata_scsi_dump_cdb: CDB
(1:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 3 10:35:43 localhost kernel: [ 1326.485407] ata_scsiop_read_cap: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.485477] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 00 00 00 60 00 a3 cf 00
Jan 3 10:35:43 localhost kernel: [ 1326.485481] ata_scsiop_inq_std: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.485519] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 01 00 00 fc 00 a3 cf 58
Jan 3 10:35:43 localhost kernel: [ 1326.485589] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 01 80 00 fc 00 a3 cf 58
Jan 3 10:35:43 localhost kernel: [ 1326.485632] ata_scsi_dump_cdb: CDB
(6:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 3 10:35:43 localhost kernel: [ 1326.485635] ata_scsiop_read_cap: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.504714] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 00 00 00 60 00 27 cd 00
Jan 3 10:35:43 localhost kernel: [ 1326.504721] ata_scsiop_inq_std: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.504939] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 01 00 00 fc 00 27 cd 58
Jan 3 10:35:43 localhost kernel: [ 1326.505048] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 01 80 00 fc 00 27 cd 58
Jan 3 10:35:43 localhost kernel: [ 1326.505093] ata_scsi_dump_cdb: CDB
(1:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 3 10:35:43 localhost kernel: [ 1326.505097] ata_scsiop_read_cap: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.505168] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 00 00 00 60 00 92 cf 00
Jan 3 10:35:43 localhost kernel: [ 1326.505172] ata_scsiop_inq_std: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.505226] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 01 00 00 fc 00 92 cf 58
Jan 3 10:35:43 localhost kernel: [ 1326.505297] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 01 80 00 fc 00 92 cf 58
Jan 3 10:35:43 localhost kernel: [ 1326.505340] ata_scsi_dump_cdb: CDB
(6:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 3 10:35:43 localhost kernel: [ 1326.505343] ata_scsiop_read_cap: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.524300] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 00 00 00 60 00 e5 cd 00
Jan 3 10:35:43 localhost kernel: [ 1326.524307] ata_scsiop_inq_std: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.524523] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 01 00 00 fc 00 e5 cd 58
Jan 3 10:35:43 localhost kernel: [ 1326.524633] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 01 80 00 fc 00 e5 cd 58
Jan 3 10:35:43 localhost kernel: [ 1326.524678] ata_scsi_dump_cdb: CDB
(1:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 3 10:35:43 localhost kernel: [ 1326.524682] ata_scsiop_read_cap: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.524750] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 00 00 00 60 00 44 ce 00
Jan 3 10:35:43 localhost kernel: [ 1326.524754] ata_scsiop_inq_std: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.524793] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 01 00 00 fc 00 44 ce 58
Jan 3 10:35:43 localhost kernel: [ 1326.524864] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 01 80 00 fc 00 44 ce 58
Jan 3 10:35:43 localhost kernel: [ 1326.524907] ata_scsi_dump_cdb: CDB
(6:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 3 10:35:43 localhost kernel: [ 1326.524910] ata_scsiop_read_cap: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.543782] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 00 00 00 60 00 f9 cd 00
Jan 3 10:35:43 localhost kernel: [ 1326.543789] ata_scsiop_inq_std: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.544003] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 01 00 00 fc 00 f9 cd 58
Jan 3 10:35:43 localhost kernel: [ 1326.544113] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 01 80 00 fc 00 f9 cd 58
Jan 3 10:35:43 localhost kernel: [ 1326.544176] ata_scsi_dump_cdb: CDB
(1:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 3 10:35:43 localhost kernel: [ 1326.544180] ata_scsiop_read_cap: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.544251] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 00 00 00 60 00 2a cf 00
Jan 3 10:35:43 localhost kernel: [ 1326.544254] ata_scsiop_inq_std: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.544292] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 01 00 00 fc 00 2a cf 58
Jan 3 10:35:43 localhost kernel: [ 1326.544361] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 01 80 00 fc 00 2a cf 58
Jan 3 10:35:43 localhost kernel: [ 1326.544404] ata_scsi_dump_cdb: CDB
(6:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 3 10:35:43 localhost kernel: [ 1326.544407] ata_scsiop_read_cap: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.563356] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 00 00 00 60 00 9c cf 00
Jan 3 10:35:43 localhost kernel: [ 1326.563363] ata_scsiop_inq_std: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.563581] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 01 00 00 fc 00 9c cf 58
Jan 3 10:35:43 localhost kernel: [ 1326.563690] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 01 80 00 fc 00 9c cf 58
Jan 3 10:35:43 localhost kernel: [ 1326.563736] ata_scsi_dump_cdb: CDB
(1:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 3 10:35:43 localhost kernel: [ 1326.563739] ata_scsiop_read_cap: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.563809] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 00 00 00 60 00 45 ce 00
Jan 3 10:35:43 localhost kernel: [ 1326.563813] ata_scsiop_inq_std: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.563850] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 01 00 00 fc 00 45 ce 58
Jan 3 10:35:43 localhost kernel: [ 1326.563922] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 01 80 00 fc 00 45 ce 58
Jan 3 10:35:43 localhost kernel: [ 1326.563965] ata_scsi_dump_cdb: CDB
(6:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 3 10:35:43 localhost kernel: [ 1326.563968] ata_scsiop_read_cap: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.582915] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 00 00 00 60 00 9e c9 00
Jan 3 10:35:43 localhost kernel: [ 1326.582922] ata_scsiop_inq_std: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.583152] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 01 00 00 fc 00 9e c9 58
Jan 3 10:35:43 localhost kernel: [ 1326.583264] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 01 80 00 fc 00 9e c9 58
Jan 3 10:35:43 localhost kernel: [ 1326.583309] ata_scsi_dump_cdb: CDB
(1:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 3 10:35:43 localhost kernel: [ 1326.583313] ata_scsiop_read_cap: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.583383] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 00 00 00 60 00 67 cd 00
Jan 3 10:35:43 localhost kernel: [ 1326.583387] ata_scsiop_inq_std: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.583424] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 01 00 00 fc 00 67 cd 58
Jan 3 10:35:43 localhost kernel: [ 1326.583494] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 01 80 00 fc 00 67 cd 58
Jan 3 10:35:43 localhost kernel: [ 1326.583537] ata_scsi_dump_cdb: CDB
(6:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 3 10:35:43 localhost kernel: [ 1326.583540] ata_scsiop_read_cap: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.602537] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 00 00 00 60 00 b1 c4 00
Jan 3 10:35:43 localhost kernel: [ 1326.602544] ata_scsiop_inq_std: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.602760] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 01 00 00 fc 00 b1 c4 58
Jan 3 10:35:43 localhost kernel: [ 1326.602869] ata_scsi_dump_cdb: CDB
(1:0,0,0) 12 01 80 00 fc 00 b1 c4 58
Jan 3 10:35:43 localhost kernel: [ 1326.602914] ata_scsi_dump_cdb: CDB
(1:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 3 10:35:43 localhost kernel: [ 1326.602918] ata_scsiop_read_cap: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.602987] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 00 00 00 60 00 48 ce 00
Jan 3 10:35:43 localhost kernel: [ 1326.602991] ata_scsiop_inq_std: ENTER
Jan 3 10:35:43 localhost kernel: [ 1326.603028] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 01 00 00 fc 00 48 ce 58
Jan 3 10:35:43 localhost kernel: [ 1326.603114] ata_scsi_dump_cdb: CDB
(6:0,0,0) 12 01 80 00 fc 00 48 ce 58
Jan 3 10:35:43 localhost kernel: [ 1326.603157] ata_scsi_dump_cdb: CDB
(6:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 3 10:35:43 localhost kernel: [ 1326.603161] ata_scsiop_read_cap: ENTER
Jan 3 10:35:44 localhost kernel: [ 1327.700597] raddio: raddio_open() -
file->f_mode=15
Jan 3 10:36:21 localhost kernel: [ 1364.170793] hdc: dma_timer_expiry: dma
status == 0x61
Jan 3 10:36:31 localhost kernel: [ 1374.156104] hdc: DMA timeout error
Jan 3 10:36:31 localhost kernel: [ 1374.156114] hdc: dma timeout error:
status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError
Index Error }
Jan 3 10:36:31 localhost kernel: [ 1374.156121] hdc: dma timeout error:
error=0x7f { DriveStatusError UncorrectableError SectorIdNotFound
TrackZeroNotFound AddrMarkNotFound }, LBAsect=260013951, sector=58557208
Jan 3 10:36:31 localhost kernel: [ 1374.156132] ide: failed opcode was:
unknown
Jan 3 10:36:31 localhost kernel: [ 1374.158087] hdc: DMA disabled
Jan 3 10:36:31 localhost kernel: [ 1374.206030] ide1: reset: master: error
(0x0a?)
Jan 3 10:37:01 localhost kernel: [ 1404.161969] hdc: lost interrupt
Jan 3 10:37:01 localhost kernel: [ 1404.161976] hdc: set_geometry_intr:
status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError
Index Error }
Jan 3 10:37:01 localhost kernel: [ 1404.161984] hdc: set_geometry_intr:
error=0x7f { DriveStatusError UncorrectableError SectorIdNotFound
TrackZeroNotFound AddrMarkNotFound }, LBAsect=260013951, sector=58557208
Jan 3 10:37:01 localhost kernel: [ 1404.161994] ide: failed opcode was:
unknown
Jan 3 10:37:01 localhost kernel: [ 1404.211892] ide1: reset: master: error
(0x0e?)
Jan 3 10:37:01 localhost kernel: [ 1404.211905] end_request: I/O error, dev
hdc, sector 58557208
Jan 3 10:37:01 localhost kernel: [ 1404.295241] end_request: I/O error, dev
hdc, sector 11436648
Jan 3 10:37:01 localhost kernel: [ 1404.295598] end_request: I/O error, dev
hdc, sector 35034528
Jan 3 10:37:01 localhost kernel: [ 1404.295851] end_request: I/O error, dev
hdc, sector 71396488
Jan 3 10:37:01 localhost kernel: [ 1404.296074] end_request: I/O error, dev
hdc, sector 35035064
Jan 3 10:37:01 localhost kernel: [ 1404.296288] end_request: I/O error, dev
hdc, sector 29730312
Jan 3 10:37:01 localhost kernel: [ 1404.296507] end_request: I/O error, dev
hdc, sector 18232768
Jan 3 10:37:01 localhost kernel: [ 1404.297303] end_request: I/O error, dev
hdc, sector 50093576
Jan 3 10:37:01 localhost kernel: [ 1404.297496] end_request: I/O error, dev
hdc, sector 13031360
Jan 3 10:37:01 localhost kernel: [ 1404.297718] end_request: I/O error, dev
hdc, sector 4525024
Jan 3 10:37:01 localhost kernel: [ 1404.298029] end_request: I/O error, dev
hdc, sector 68605856
Jan 3 10:37:01 localhost kernel: [ 1404.298248] end_request: I/O error, dev
hdc, sector 20995192
Jan 3 10:37:01 localhost kernel: [ 1404.298445] end_request: I/O error, dev
hdc, sector 41058880
Jan 3 10:37:01 localhost kernel: [ 1404.298632] end_request: I/O error, dev
hdc, sector 73172512
Jan 3 10:37:01 localhost kernel: [ 1404.298837] end_request: I/O error, dev
hdc, sector 48503288
Jan 3 10:37:01 localhost kernel: [ 1404.299022] end_request: I/O error, dev
hdc, sector 46497312
Jan 3 10:37:01 localhost kernel: [ 1404.299167] end_request: I/O error, dev
hdc, sector 60576872
Jan 3 10:37:01 localhost kernel: [ 1404.299308] end_request: I/O error, dev
hdc, sector 9632736
Jan 3 10:37:01 localhost kernel: [ 1404.299449] end_request: I/O error, dev
hdc, sector 40871200
Jan 3 10:37:01 localhost kernel: [ 1404.299627] end_request: I/O error, dev
hdc, sector 68270824
Jan 3 10:37:01 localhost kernel: [ 1404.299800] end_request: I/O error, dev
hdc, sector 22557072
Jan 3 10:37:01 localhost kernel: [ 1404.299805] Buffer I/O error on device
hdc, logical block 2819634
Jan 3 10:37:01 localhost kernel: [ 1404.299807] lost page write due to I/O
error on hdc
Jan 3 10:37:01 localhost kernel: [ 1404.299952] end_request: I/O error, dev
hdc, sector 58118752
Jan 3 10:37:01 localhost kernel: [ 1404.300100] end_request: I/O error, dev
hdc, sector 74922088
Jan 3 10:37:01 localhost kernel: [ 1404.300240] end_request: I/O error, dev
hdc, sector 38151592
Jan 3 10:37:01 localhost kernel: [ 1404.300380] end_request: I/O error, dev
hdc, sector 76381056
Jan 3 10:37:01 localhost kernel: [ 1404.300520] end_request: I/O error, dev
hdc, sector 62933696
Jan 3 10:37:01 localhost kernel: [ 1404.300660] end_request: I/O error, dev
hdc, sector 42973464
Jan 3 10:37:01 localhost kernel: [ 1404.300810] end_request: I/O error, dev
hdc, sector 37614272
Jan 3 10:37:01 localhost kernel: [ 1404.300950] end_request: I/O error, dev
hdc, sector 14795552
Jan 3 10:37:01 localhost kernel: [ 1404.301137] end_request: I/O error, dev
hdc, sector 73067064
Jan 3 10:37:01 localhost kernel: [ 1404.301141] Buffer I/O error on device
hdc, logical block 9133383
Jan 3 10:37:01 localhost kernel: [ 1404.301143] lost page write due to I/O
error on hdc
Jan 3 10:37:01 localhost kernel: [ 1404.301292] end_request: I/O error, dev
hdc, sector 68217912
Jan 3 10:37:01 localhost kernel: [ 1404.301442] end_request: I/O error, dev
hdc, sector 73352768
Jan 3 10:37:01 localhost kernel: [ 1404.301446] Buffer I/O error on device
hdc, logical block 9169096
Jan 3 10:37:01 localhost kernel: [ 1404.301448] lost page write due to I/O
error on hdc
Jan 3 10:37:01 localhost kernel: [ 1404.301590] end_request: I/O error, dev
hdc, sector 46747304
Jan 3 10:37:01 localhost kernel: [ 1404.301730] end_request: I/O error, dev
hdc, sector 65496040
Jan 3 10:37:01 localhost kernel: [ 1404.301881] end_request: I/O error, dev
hdc, sector 66611208
Jan 3 10:37:01 localhost kernel: [ 1404.302021] end_request: I/O error, dev
hdc, sector 3644328
Jan 3 10:37:01 localhost kernel: [ 1404.302167] end_request: I/O error, dev
hdc, sector 17088312
Jan 3 10:37:01 localhost kernel: [ 1404.302316] end_request: I/O error, dev
hdc, sector 47087584
Jan 3 10:37:01 localhost kernel: [ 1404.302320] Buffer I/O error on device
hdc, logical block 5885948
Jan 3 10:37:01 localhost kernel: [ 1404.302322] lost page write due to I/O
error on hdc
Jan 3 10:37:01 localhost kernel: [ 1404.302474] end_request: I/O error, dev
hdc, sector 15981504
Jan 3 10:37:01 localhost kernel: [ 1404.302478] Buffer I/O error on device
hdc, logical block 1997688
Jan 3 10:37:01 localhost kernel: [ 1404.302480] lost page write due to I/O
error on hdc
Jan 3 10:37:01 localhost kernel: [ 1404.302653] end_request: I/O error, dev
hdc, sector 70501312
Jan 3 10:37:01 localhost kernel: [ 1404.303509] end_request: I/O error, dev
hdc, sector 0
Jan 3 10:37:01 localhost kernel: [ 1404.303512] Buffer I/O error on device
hdc, logical block 0
Jan 3 10:56:42 localhost /sbin/hotplug: no runnable /etc/hotplug/vc.agent
is installed
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: ATA Write Error and Time-out Notification in User Space
2006-01-03 18:29 John Treubig
@ 2006-01-03 18:58 ` Alan Cox
2006-01-03 19:27 ` John Treubig
2006-01-04 12:37 ` Erik Slagter
0 siblings, 2 replies; 12+ messages in thread
From: Alan Cox @ 2006-01-03 18:58 UTC (permalink / raw)
To: John Treubig; +Cc: raw, linux-ide, linux-kernel, linux-scsi
On Maw, 2006-01-03 at 12:29 -0600, John Treubig wrote:
> failure point. I put a drive on the Secondary IDE bus hanging off the
> motherboard Nvidia NForce 2 controller, began an access and pulled the plug.
> Sure enough the failures occured and were passed back to user level, but
> the system did not hang. I've repeated this a number of times. I moved the
> same drive to the Promise Controller and the hang occurs. Thus it seems we
> have proved the Promise sub-system is my problem.
Bingo. Yes I know why this is occuring now.
There is a known old bug with error handling in some cases on promise
chips. The core kernel code tries to clean up any remaining data after
an error (to handle chip prefetch/postwrite FIFOs) if DRQ_STAT is
asserted. Its a nice trick, saves on resets and slow recovery but isn't
compatible with some promise controllers.
The -mm tree has a partial but incomplete fix to this implemented, the
base kernel does not have this fixed.
Its been known for some time so perhaps the ide maintainers have patches
waiting for 2.6.16 now its opened ?
Alan
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ATA Write Error and Time-out Notification in User Space
2006-01-03 18:58 ` Alan Cox
@ 2006-01-03 19:27 ` John Treubig
2006-01-03 21:48 ` Alan Cox
2006-01-04 12:37 ` Erik Slagter
1 sibling, 1 reply; 12+ messages in thread
From: John Treubig @ 2006-01-03 19:27 UTC (permalink / raw)
To: alan; +Cc: raw, linux-ide, linux-kernel, linux-scsi
I receive this as great news, only I don't know where the -mm tree is
located to see if I can get the patch or fix! Can you give me a few
pointers?!
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: John Treubig <jtreubig@hotmail.com>
CC: raw@dslr.net, linux-ide@vger.kernel.org,linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: ATA Write Error and Time-out Notification in User Space
Date: Tue, 03 Jan 2006 18:58:42 +0000
On Maw, 2006-01-03 at 12:29 -0600, John Treubig wrote:
> failure point. I put a drive on the Secondary IDE bus hanging off the
> motherboard Nvidia NForce 2 controller, began an access and pulled the
plug.
> Sure enough the failures occured and were passed back to user level,
but
> the system did not hang. I've repeated this a number of times. I moved
the
> same drive to the Promise Controller and the hang occurs. Thus it seems
we
> have proved the Promise sub-system is my problem.
Bingo. Yes I know why this is occuring now.
There is a known old bug with error handling in some cases on promise
chips. The core kernel code tries to clean up any remaining data after
an error (to handle chip prefetch/postwrite FIFOs) if DRQ_STAT is
asserted. Its a nice trick, saves on resets and slow recovery but isn't
compatible with some promise controllers.
The -mm tree has a partial but incomplete fix to this implemented, the
base kernel does not have this fixed.
Its been known for some time so perhaps the ide maintainers have patches
waiting for 2.6.16 now its opened ?
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ATA Write Error and Time-out Notification in User Space
2006-01-03 19:27 ` John Treubig
@ 2006-01-03 21:48 ` Alan Cox
0 siblings, 0 replies; 12+ messages in thread
From: Alan Cox @ 2006-01-03 21:48 UTC (permalink / raw)
To: John Treubig; +Cc: raw, linux-ide, linux-kernel, linux-scsi
On Maw, 2006-01-03 at 13:27 -0600, John Treubig wrote:
> I receive this as great news, only I don't know where the -mm tree is
> located to see if I can get the patch or fix! Can you give me a few
> pointers?!
The -mm patches live on kernel.org in pub/linux/kernel/people/akpm/
The patch you want is the one to drivers/ide/ide-io.c although be aware
it will make non PCI ATA controllers crash on errors if applied. The
"right" fix for this is probably to have a hwif->flush_data() function
that defaults to try_to_flush_leftover_data() so that the knowledge
involved is not hacked into the ide core but kept in the driver.
Alan
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ATA Write Error and Time-out Notification in User Space
2006-01-03 18:58 ` Alan Cox
2006-01-03 19:27 ` John Treubig
@ 2006-01-04 12:37 ` Erik Slagter
2006-01-04 12:45 ` Alan Cox
1 sibling, 1 reply; 12+ messages in thread
From: Erik Slagter @ 2006-01-04 12:37 UTC (permalink / raw)
To: Alan Cox; +Cc: linux-ide
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
On Tue, 2006-01-03 at 18:58 +0000, Alan Cox wrote:
> There is a known old bug with error handling in some cases on promise
> chips. The core kernel code tries to clean up any remaining data after
> an error (to handle chip prefetch/postwrite FIFOs) if DRQ_STAT is
> asserted. Its a nice trick, saves on resets and slow recovery but isn't
> compatible with some promise controllers.
>
> The -mm tree has a partial but incomplete fix to this implemented, the
> base kernel does not have this fixed.
>
> Its been known for some time so perhaps the ide maintainers have patches
> waiting for 2.6.16 now its opened ?
Is this patch supposed to fix this problem:
Promise SATAII150 TX2plus using libata_promise, when it misses one
single interrupt (or maybe it's not even missed but only delayed), it
goes crazy, kernel log is full with disk failures, and the disk is
kicked out of the md(1) array grmbl.
This happens when amd76x_pm is used, even with the irq watcher in the
utter most conservative setting.
Any clue otherwise?
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2771 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ATA Write Error and Time-out Notification in User Space
2006-01-04 12:37 ` Erik Slagter
@ 2006-01-04 12:45 ` Alan Cox
2006-01-04 12:48 ` Erik Slagter
0 siblings, 1 reply; 12+ messages in thread
From: Alan Cox @ 2006-01-04 12:45 UTC (permalink / raw)
To: Erik Slagter; +Cc: linux-ide
On Mer, 2006-01-04 at 13:37 +0100, Erik Slagter wrote:
> > Its been known for some time so perhaps the ide maintainers have patches
> > waiting for 2.6.16 now its opened ?
>
> Is this patch supposed to fix this problem:
Nope - it fixes a problem with the old IDE layer.
> Promise SATAII150 TX2plus using libata_promise, when it misses one
> single interrupt (or maybe it's not even missed but only delayed), it
> goes crazy, kernel log is full with disk failures, and the disk is
> kicked out of the md(1) array grmbl.
>
> This happens when amd76x_pm is used, even with the irq watcher in the
> utter most conservative setting.
Does it happen with it not being used ?
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ATA Write Error and Time-out Notification in User Space
2006-01-04 12:45 ` Alan Cox
@ 2006-01-04 12:48 ` Erik Slagter
0 siblings, 0 replies; 12+ messages in thread
From: Erik Slagter @ 2006-01-04 12:48 UTC (permalink / raw)
To: Alan Cox; +Cc: linux-ide
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
On Wed, 2006-01-04 at 12:45 +0000, Alan Cox wrote:
> On Mer, 2006-01-04 at 13:37 +0100, Erik Slagter wrote:
> > > Its been known for some time so perhaps the ide maintainers have patches
> > > waiting for 2.6.16 now its opened ?
> >
> > Is this patch supposed to fix this problem:
>
> Nope - it fixes a problem with the old IDE layer.
Ow, sorry, I probably didn't read your msg carefully.
> > Promise SATAII150 TX2plus using libata_promise, when it misses one
> > single interrupt (or maybe it's not even missed but only delayed), it
> > goes crazy, kernel log is full with disk failures, and the disk is
> > kicked out of the md(1) array grmbl.
> >
> > This happens when amd76x_pm is used, even with the irq watcher in the
> > utter most conservative setting.
>
> Does it happen with it not being used ?
No, I bought a new (decent) power supply recently, and since then I did
not have a single problem with the card. Until I start using amd76x_pm.
I have it setup so that whenever a single interrupt is caught
(monitoring interval: 1ms) any transition to C2 is suspended for about a
second.
But I realise this is not officially supported stuff, it's just nice if
it would work, it saves about 70 watts on power (confirmed by own
measurements) and a lot of heat.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2771 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ATA Write Error and Time-out Notification in User Space
@ 2006-01-05 20:27 John Treubig
0 siblings, 0 replies; 12+ messages in thread
From: John Treubig @ 2006-01-05 20:27 UTC (permalink / raw)
To: alan; +Cc: raw, linux-ide, linux-kernel, linux-scsi
[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]
I applied the patch to the mm and yes, we have no more hangs! The bad news
is the application gets no notification that there has been any error in the
drive subsystem. I have only had one instance that I got a notification
back, but this was due to me adding a BUG_ON statement prior to the PRINTKs.
Here's the details of what occurs: With the application running, and I
unplug the drive, my app still tries to read and write because it has gotten
no error from the SG calls. Is there a way that we can notify the kernel
that this device is dead and cause all future accesses to result in an
error?
I have had great difficulty getting the PRINTKs to output anything for this
specific error, yet I've been able to get other PRINTKs in the IDE-IO.C to
output. I have attached the messages that do result.
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: John Treubig <jtreubig@hotmail.com>
CC: raw@dslr.net, linux-ide@vger.kernel.org,linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: ATA Write Error and Time-out Notification in User Space
Date: Tue, 03 Jan 2006 21:48:04 +0000
On Maw, 2006-01-03 at 13:27 -0600, John Treubig wrote:
> I receive this as great news, only I don't know where the -mm tree is
> located to see if I can get the patch or fix! Can you give me a few
> pointers?!
The -mm patches live on kernel.org in pub/linux/kernel/people/akpm/
The patch you want is the one to drivers/ide/ide-io.c although be aware
it will make non PCI ATA controllers crash on errors if applied. The
"right" fix for this is probably to have a hwif->flush_data() function
that defaults to try_to_flush_leftover_data() so that the knowledge
involved is not hacked into the ide core but kept in the driver.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: junk1.txt --]
[-- Type: text/plain, Size: 9064 bytes --]
Jan 5 08:28:26 localhost kernel: [ 204.399120] ata_scsi_translate: EXIT
Jan 5 08:28:26 localhost kernel: [ 204.408979] ata_host_intr: ata2:
host_stat 0x4
Jan 5 08:28:26 localhost kernel: [ 204.408987] ata_host_intr: ata2:
protocol 4 (dev_stat 0x50)
Jan 5 08:28:26 localhost kernel: [ 204.408991] ata_sg_clean: unmapping 1
sg elements
Jan 5 08:28:26 localhost kernel: [ 204.408993] ata_qc_complete: EXIT
Jan 5 08:28:26 localhost kernel: [ 204.409010] ata_scsi_dump_cdb: CDB
(2:0,0,0) 28 00 01 ca 9f 15 00 00 08
Jan 5 08:28:26 localhost kernel: [ 204.409013] ata_scsi_translate: ENTER
Jan 5 08:28:26 localhost kernel: [ 204.409015] scsi_10_lba_len: ten-byte
command
Jan 5 08:28:26 localhost kernel: [ 204.409017] ata_sg_setup_one: mapped
buffer of 4096 bytes for read
Jan 5 08:28:26 localhost kernel: [ 204.409020] ata_fill_sg: PRD[0] =
(0xD048000, 0x1000)
Jan 5 08:28:26 localhost kernel: [ 204.409022] ata_dev_select: ENTER,
ata2: device 0, wait 1
Jan 5 08:28:26 localhost kernel: [ 204.409050] ata_tf_load_mmio: feat 0x0
nsect 0x8 lba 0x15 0x9F 0xCA
Jan 5 08:28:26 localhost kernel: [ 204.409052] ata_tf_load_mmio: device
0xE1
Jan 5 08:28:26 localhost kernel: [ 204.409067] ata_exec_command_mmio:
ata2: cmd 0xC8
Jan 5 08:28:26 localhost kernel: [ 204.409072] ata_scsi_translate: EXIT
Jan 5 08:28:26 localhost kernel: [ 204.409146] ata_host_intr: ata2:
host_stat 0x4
Jan 5 08:28:26 localhost kernel: [ 204.409154] ata_host_intr: ata2:
protocol 4 (dev_stat 0x50)
Jan 5 08:28:26 localhost kernel: [ 204.409158] ata_sg_clean: unmapping 1
sg elements
Jan 5 08:28:26 localhost kernel: [ 204.409160] ata_qc_complete: EXIT
Jan 5 08:28:26 localhost kernel: [ 204.409211] ata_scsi_dump_cdb: CDB
(2:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 5 08:28:26 localhost kernel: [ 204.409214] ata_scsiop_read_cap: ENTER
Jan 5 08:28:26 localhost kernel: [ 204.409244] ata_scsi_dump_cdb: CDB
(2:0,0,0) 2a 00 00 d9 65 fb 00 00 08
Jan 5 08:28:26 localhost kernel: [ 204.409246] ata_scsi_translate: ENTER
Jan 5 08:28:26 localhost kernel: [ 204.409248] scsi_10_lba_len: ten-byte
command
Jan 5 08:28:26 localhost kernel: [ 204.409251] ata_sg_setup_one: mapped
buffer of 4096 bytes for write
Jan 5 08:28:26 localhost kernel: [ 204.409253] ata_fill_sg: PRD[0] =
(0xD048000, 0x1000)
Jan 5 08:28:26 localhost kernel: [ 204.409256] ata_dev_select: ENTER,
ata2: device 0, wait 1
Jan 5 08:28:26 localhost kernel: [ 204.409283] ata_tf_load_mmio: feat 0x0
nsect 0x8 lba 0xFB 0x65 0xD9
Jan 5 08:28:26 localhost kernel: [ 204.409285] ata_tf_load_mmio: device
0xE0
Jan 5 08:28:26 localhost kernel: [ 204.409300] ata_exec_command_mmio:
ata2: cmd 0xCA
Jan 5 08:28:26 localhost kernel: [ 204.409305] ata_scsi_translate: EXIT
Jan 5 08:28:26 localhost kernel: [ 204.462137] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:26 localhost kernel: [ 205.135110] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:26 localhost kernel: [ 205.211290] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:40 localhost kernel: [ 218.368667] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:40 localhost kernel: [ 218.449054] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:40 localhost kernel: [ 218.691283] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:40 localhost kernel: [ 218.946905] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:40 localhost kernel: [ 218.948318] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:40 localhost kernel: [ 219.194021] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:40 localhost kernel: [ 219.214175] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:41 localhost kernel: [ 219.696113] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:41 localhost kernel: [ 219.697451] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:41 localhost kernel: [ 219.742827] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:41 localhost kernel: [ 219.937038] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:41 localhost kernel: [ 219.985139] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:42 localhost kernel: [ 220.445205] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:42 localhost kernel: [ 220.797927] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:42 localhost kernel: [ 220.816866] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:42 localhost kernel: [ 220.907329] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:42 localhost kernel: [ 221.089499] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:42 localhost kernel: [ 221.090284] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:42 localhost kernel: [ 221.238775] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:43 localhost kernel: [ 221.267263] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:43 localhost kernel: [ 221.536527] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:43 localhost kernel: [ 221.611554] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:43 localhost kernel: [ 221.938468] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:44 localhost kernel: [ 222.373794] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:44 localhost kernel: [ 222.374695] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:44 localhost kernel: [ 223.162135] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:44 localhost kernel: [ 223.163329] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:44 localhost kernel: [ 223.164521] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:45 localhost kernel: [ 223.813787] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:45 localhost kernel: [ 224.140885] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:46 localhost kernel: [ 224.353850] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:46 localhost kernel: [ 224.379358] ata_scsi_error: ENTER
Jan 5 08:28:46 localhost kernel: [ 224.379361] ata_eng_timeout: ENTER
Jan 5 08:28:46 localhost kernel: [ 224.379363] ata_qc_timeout: ENTER
Jan 5 08:28:46 localhost kernel: [ 224.379374] ata2: command 0xca timeout,
stat 0x7f host_stat 0x1
Jan 5 08:28:46 localhost kernel: [ 224.379377] ata_sg_clean: unmapping 1
sg elements
Jan 5 08:28:46 localhost kernel: [ 224.379391] ata2: translated ATA
stat/err 0x7f/7f to SCSI SK/ASC/ASCQ 0x4/00/00
Jan 5 08:28:46 localhost kernel: [ 224.379394] ata2: status=0x7f {
DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error }
Jan 5 08:28:46 localhost kernel: [ 224.379399] ata2: error=0x7f {
DriveStatusError UncorrectableError SectorIdNotFound TrackZeroNotFound
AddrMarkNotFound }
Jan 5 08:28:46 localhost kernel: [ 224.379411] ata_qc_complete: EXIT
Jan 5 08:28:46 localhost kernel: [ 224.379413] ata_qc_timeout: EXIT
Jan 5 08:28:46 localhost kernel: [ 224.379414] ata_eng_timeout: EXIT
Jan 5 08:28:46 localhost kernel: [ 224.379416] ata_scsi_error: EXIT
Jan 5 08:28:46 localhost kernel: [ 224.400243] ata_scsi_dump_cdb: CDB
(2:0,0,0) 25 00 00 00 00 00 00 00 00
Jan 5 08:28:46 localhost kernel: [ 224.400249] ata_scsiop_read_cap: ENTER
Jan 5 08:28:46 localhost kernel: [ 224.400423] ata_scsi_dump_cdb: CDB
(2:0,0,0) 2a 00 03 af fd 18 00 00 08
Jan 5 08:28:46 localhost kernel: [ 224.400426] ata_scsi_translate: ENTER
Jan 5 08:28:46 localhost kernel: [ 224.400430] scsi_10_lba_len: ten-byte
command
Jan 5 08:28:46 localhost kernel: [ 224.400435] ata_sg_setup_one: mapped
buffer of 4096 bytes for write
Jan 5 08:28:46 localhost kernel: [ 224.400438] ata_fill_sg: PRD[0] =
(0xD048000, 0x1000)
Jan 5 08:28:46 localhost kernel: [ 224.400441] ata_dev_select: ENTER,
ata2: device 0, wait 1
Jan 5 08:28:46 localhost kernel: [ 224.410486] ATA: abnormal status 0x7F
on port 0xD08195DF
Jan 5 08:28:46 localhost kernel: [ 224.410504] ata_tf_load_mmio: feat 0x0
nsect 0x8 lba 0x18 0xFD 0xAF
Jan 5 08:28:46 localhost kernel: [ 224.410506] ata_tf_load_mmio: device
0xE3
Jan 5 08:28:46 localhost kernel: [ 224.410522] ata_exec_command_mmio:
ata2: cmd 0xCA
Jan 5 08:28:46 localhost kernel: [ 224.410527] ata_scsi_translate: EXIT
Jan 5 08:28:46 localhost kernel: [ 224.658874] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:46 localhost kernel: [ 224.753952] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:46 localhost kernel: [ 224.874626] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:46 localhost kernel: [ 225.186896] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:47 localhost kernel: [ 226.040653] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:47 localhost kernel: [ 226.191764] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:48 localhost kernel: [ 226.348601] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:48 localhost kernel: [ 226.415600] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:48 localhost kernel: [ 226.878584] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:48 localhost kernel: [ 226.909086] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:48 localhost kernel: [ 226.933143] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:49 localhost kernel: [ 227.240286] ata_host_intr: ata2:
host_stat 0x1
Jan 5 08:28:49 localhost kernel: [ 227.458131] ata_host_intr: ata2:
host_stat 0x1
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2006-01-05 20:27 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-12-20 21:55 ATA Write Error and Time-out Notification in User Space John Treubig
2005-12-20 22:50 ` Alan Cox
2005-12-21 0:31 ` Drew Winstel
2005-12-22 1:09 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2006-01-03 18:29 John Treubig
2006-01-03 18:58 ` Alan Cox
2006-01-03 19:27 ` John Treubig
2006-01-03 21:48 ` Alan Cox
2006-01-04 12:37 ` Erik Slagter
2006-01-04 12:45 ` Alan Cox
2006-01-04 12:48 ` Erik Slagter
2006-01-05 20:27 John Treubig
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).