public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zan Lynx <zlynx@acm.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.24-rc4-mm1 and excessive block IO errors
Date: Fri, 07 Dec 2007 20:44:45 +0000	[thread overview]
Message-ID: <1197060285.15428.20.camel@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 4532 bytes --]

I am not sure if this problem has been addressed already.  I read some
about the fast-fail issues and this may be related?

On nearly all my USB block devices, I have been getting zillions of I/O
errors.  But they aren't real, they don't appear with 2.6.23 kernels.

I can often read and write data to the device, but these IO errors cause
error aborts in user space applications in many cases, making it a
chancy thing to run backup software, for example.

Here is a bit of dmesg from plugging in a perfectly good USB-2 flash
drive.

hub 3-0:1.0: state 7 ports 6 chg 0000 evt 0004
ehci_hcd 0000:00:02.2: GetStatus port 2 status 001803 POWER sig=j CSC CONNECT
hub 3-0:1.0: port 2, status 0501, change 0001, 480 Mb/s
hub 3-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x501
ehci_hcd 0000:00:02.2: port 2 high speed
ehci_hcd 0000:00:02.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 3-2: new high speed USB device using ehci_hcd and address 9
ehci_hcd 0000:00:02.2: port 2 high speed
ehci_hcd 0000:00:02.2: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
usb 3-2: default language 0x0409
usb 3-2: uevent
usb 3-2: usb_probe_device
usb 3-2: configuration #1 chosen from 1 choice
usb 3-2: adding 3-2:1.0 (config #1, interface 0)
usb 3-2:1.0: uevent
libusual 3-2:1.0: usb_probe_interface
libusual 3-2:1.0: usb_probe_interface - got id
usb-storage 3-2:1.0: usb_probe_interface
usb-storage 3-2:1.0: usb_probe_interface - got id
scsi4 : SCSI emulation for USB Mass Storage devices
drivers/usb/core/inode.c: creating file '009'
usb 3-2: New USB device found, idVendor=05dc, idProduct=a400
usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-2: Product: JUMPDRIVE
usb 3-2: Manufacturer: LEXAR MEDIA
usb 3-2: SerialNumber: 0A4EEC05201219080904
usb-storage: device found at 9
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 4:0:0:0: Direct-Access     LEXAR    JUMPDRIVE        1000 PQ: 0 ANSI: 0 CCS
sd 4:0:0:0: [sdg] 2026592 512-byte hardware sectors (1038 MB)
sd 4:0:0:0: [sdg] Write Protect is off
sd 4:0:0:0: [sdg] Mode Sense: 43 00 00 00
sd 4:0:0:0: [sdg] Assuming drive cache: write through
sd 4:0:0:0: [sdg] 2026592 512-byte hardware sectors (1038 MB)
sd 4:0:0:0: [sdg] Write Protect is off
sd 4:0:0:0: [sdg] Mode Sense: 43 00 00 00
sd 4:0:0:0: [sdg] Assuming drive cache: write through
 sdg: sdg1
sd 4:0:0:0: [sdg] Attached SCSI removable disk
sd 4:0:0:0: Attached scsi generic sg7 type 0
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 3984
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 162
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 290
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 418
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 546
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 674
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 802
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 930
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 1058
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 1186
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 1314
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 1442
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 1570
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 1698
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 1826
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 1954
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 528288
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 528672
sd 4:0:0:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdg, sector 546392

-- 
Zan Lynx <zlynx@acm.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2007-12-07 20:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07 20:44 Zan Lynx [this message]
2007-12-07 23:05 ` 2.6.24-rc4-mm1 and excessive block IO errors Andrew Morton
2007-12-07 23:33   ` Alexey Dobriyan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1197060285.15428.20.camel@localhost \
    --to=zlynx@acm.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox