public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Dolgov <solkaa@gmail.com>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: usb-storage, error reading the last 8 sectors, regression in 2.6.25-rc7
Date: Sun, 30 Mar 2008 11:49:27 +0400	[thread overview]
Message-ID: <20080330074927.GA8178@slk.laptop> (raw)

Hi!

If I boot Asus Eee PC with 8 Gb Transcend SDHC card inserted into the
internal card reader, 2.6.25-rc7 prints the following:

   [    9.914968] scsi 2:0:0:0: Direct-Access     USB2.0   CardReader SD0   0100 PQ: 0 ANSI: 0
   [   10.248951] sd 2:0:0:0: [sdb] 15660032 512-byte hardware sectors (8018 MB)
   [   10.249695] sd 2:0:0:0: [sdb] Write Protect is off
   [   10.249928] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
   [   10.249935] sd 2:0:0:0: [sdb] Assuming drive cache: write through
   [   10.256632] sd 2:0:0:0: [sdb] 15660032 512-byte hardware sectors (8018 MB)
   [   10.257440] sd 2:0:0:0: [sdb] Write Protect is off
   [   10.257546] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
   [   10.257552] sd 2:0:0:0: [sdb] Assuming drive cache: write through
   [   10.257657]  sdb: sdb1 sdb2 sdb3
   [   10.259560] sd 2:0:0:0: [sdb] Attached SCSI removable disk
   [   10.260489] usb-storage: device scan complete
   [   10.380590] sd 2:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
   [   10.380590] sd 2:0:0:0: [sdb] Sense Key : 0x4 [current] 
   [   10.380590] sd 2:0:0:0: [sdb] ASC=0x11 ASCQ=0x0
   [   10.380590] end_request: I/O error, dev sdb, sector 15660024

As a result, no sdb device is created by udev.

If the card is inserted after the boot, it sometimes works fine (I've
tested with "dd if=/dev/sdb of=/dev/null bs=512 skip=15660000"), and
sometimes fails in the same way (the same I/O error message, dd
hangs).

2.6.24.4 is fine (no problems at boot, always can dd read the whole
card, all 15660032 sectors of it).

The other SD card I've got, 2 Gb, also works ok even with 2.6.25-rc7.

-- 
Sergey

             reply	other threads:[~2008-03-30  7:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-30  7:49 Sergey Dolgov [this message]
2008-03-30 18:59 ` usb-storage, error reading the last 8 sectors, regression in 2.6.25-rc7 Alan Stern
2008-03-30 22:32   ` Sergey Dolgov
2008-04-01  1:18     ` Sergey Dolgov
2008-04-01  1:58       ` Alan Stern
2008-04-01  7:38         ` Oliver Neukum
2008-04-01 14:28           ` Alan Stern
2008-04-01 14:34             ` Matthew Dharm
2008-04-01 14:42               ` Alan Stern
2008-04-01 15:26                 ` Boaz Harrosh
2008-04-01 15:53                 ` Matthew Dharm
2008-04-01 16:31                   ` Boaz Harrosh
2008-04-01 20:24                     ` Hans de Goede
2008-04-01 21:01                       ` Alan Stern
2008-04-02  7:01                         ` Hans de Goede
2008-04-02 14:15                           ` Alan Stern
2008-04-01 16:48                   ` Sergey Dolgov
  -- strict thread matches above, loose matches on Subject: below --
2008-04-03 22:49 2.6.25-rc8-git2: Reported regressions from 2.6.24 Rafael J. Wysocki
2008-04-03 23:22 ` usb-storage, error reading the last 8 sectors, regression in 2.6.25-rc7 Rafael J. Wysocki

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=20080330074927.GA8178@slk.laptop \
    --to=solkaa@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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