From: Andrew Morton <akpm@linux-foundation.org>
To: "Ni@m" <niam.niam@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: NIKON D50 problem
Date: Mon, 2 Jul 2007 15:59:12 -0700 [thread overview]
Message-ID: <20070702155912.fe1e6834.akpm@linux-foundation.org> (raw)
In-Reply-To: <a9e22dff0707021217r239ebcf0g8154a6e985b078f3@mail.gmail.com>
On Mon, 2 Jul 2007 22:17:20 +0300
"Ni@m" <niam.niam@gmail.com> wrote:
> Hi! Recently I've found out that my camera NIKON D50 can't mount any more.
> uname -a: "Linux niam 2.6.22-rc6-cfs-v18 #6 Mon Jul 2 20:19:25 EEST
> 2007 i686 Intel(R) Celeron(R) M processor 1.50GHz GenuineIntel
> GNU/Linux"
>
> dmesg:
> scsi 2:0:0:0: Direct-Access NIKON D50 1.00 PQ: 0 ANSI: 2
> sd 2:0:0:0: [sdb] 1984001 512-byte hardware sectors (1016 MB)
> sd 2:0:0:0: [sdb] Write Protect is off
> sd 2:0:0:0: [sdb] Mode Sense: 0f 00 00 00
> sd 2:0:0:0: [sdb] Assuming drive cache: write through
> sd 2:0:0:0: [sdb] 1984001 512-byte hardware sectors (1016 MB)
> sd 2:0:0:0: [sdb] Write Protect is off
> sd 2:0:0:0: [sdb] Mode Sense: 0f 00 00 00
> sd 2:0:0:0: [sdb] Assuming drive cache: write through
> sdb: sdb1
> sd 2:0:0:0: [sdb] Attached SCSI removable disk
> sd 2:0:0:0: Attached scsi generic sg2 type 0
> usb-storage: device scan complete
> end_request: I/O error, dev sdb, sector 1984000
> Buffer I/O error on device sdb, logical block 1984000
> end_request: I/O error, dev sdb, sector 1984000
> Buffer I/O error on device sdb, logical block 1984000
> end_request: I/O error, dev sdb, sector 1983992
> Buffer I/O error on device sdb, logical block 1983992
> end_request: I/O error, dev sdb, sector 1983993
> Buffer I/O error on device sdb, logical block 1983993
> Buffer I/O error on device sdb, logical block 1983994
> Buffer I/O error on device sdb, logical block 1983995
> Buffer I/O error on device sdb, logical block 1983996
> Buffer I/O error on device sdb, logical block 1983997
> Buffer I/O error on device sdb, logical block 1983998
> Buffer I/O error on device sdb, logical block 1983999
> end_request: I/O error, dev sdb, sector 1983992
> ...................
>
> Some time ago(I really can't remember version of the kernel)
> everything was Ok. I'll try to find out the workable version of the
> kernel ... but I've already tried 2.6.20 - the same =(.
> I'm not sure, but It's possible that I've had ATA subsystem but not
> libata ... I haven't tested this case yet.
>
> PS. I can see photos on my camera ... flash card is Ok. I have this
> problem even if I changed the flash card in this camera.
It's more likely a usb-storage or scsi layer problem.
The device reports as having 1984001 sectors and the kernel is reporting IO
errors around the very end of the device. Presumably an IO is straddling
end-of-device and we're not handling that correctly.
next prev parent reply other threads:[~2007-07-02 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 19:17 NIKON D50 problem Ni@m
2007-07-02 22:59 ` Andrew Morton [this message]
2007-07-03 6:02 ` [linux-usb-devel] " Oliver Neukum
2007-07-03 21:01 ` Alan Stern
2007-07-03 6:44 ` Oliver Neukum
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=20070702155912.fe1e6834.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=niam.niam@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.