From: Kyle <kyle@actarg.com>
To: linux-kernel@vger.kernel.org
Subject: [Fwd: Re: SDDR-31, or possible kernel bug]
Date: Mon, 24 Dec 2001 15:48:16 -0700 [thread overview]
Message-ID: <3C27B0B0.4060500@actarg.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 196 bytes --]
I have a flash card which, when read, locks up linux hard. Here's the
particulars so far. Is there anything I can do to help out kernel bug
checking before I try to reformat this flash card?
[-- Attachment #2: Re: SDDR-31, or possible kernel bug --]
[-- Type: message/rfc822, Size: 7135 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 5328 bytes --]
I suggest you contact linux-kernel@vger.kernel.org and see what they say.
Matt
On Mon, Dec 24, 2001 at 09:45:51AM -0700, Kyle wrote:
> Matthew Dharm wrote:
>
> >Yes, I'm still supporting it.
> >
> >Can you recompile your kernel with USB Mass Storage Verbose debugging
> >turned on?
> >
> Hmmm, I have an interesting new development. I had previously been doing:
>
> mount -t vfat /dev/sda1 /mnt/flash
>
> The device appeared to mount fine, but as soon as I would do:
>
> find /mnt/flash
>
> the system will *hard* lock. I just put the problem flash in a PCMCIA
> adapter and stuck it in my laptop. It is recognized nicely on /dev/hde.
> I do:
>
> mount -t vfat /dev/hde1 /mnt/flash
>
> which works ok, but when I do:
>
> find /mnt/flash
>
> the system hard locks just as before (but without usb being involved at
> all)...
>
> I looked in syslog and found:
>
> Dec 24 10:07:08 nb0 kernel: hde: hde1
> Dec 24 10:07:08 nb0 kernel: FAT: bogus logical sector size 20487
> Dec 24 10:07:08 nb0 kernel: VFS: Can't find a valid FAT filesystem on
> dev 21:00.
> Dec 24 10:07:08 nb0 kernel: hde: hde1
>
> I repeated the test and still got the hard lock, but the error messages
> about the FAT being messed up are not there. So I looked back in
> earlier logs of when I had been trying to mount the usb flash reader and
> sure enough: Even though later crashes had yielded no syslog messages,
> there were earlier ones that did. Here's a section of syslog:
>
> Dec 21 19:29:49 nb0 syslogd 1.4.1: restart.
> Dec 21 19:34:44 nb0 su(pam_unix)[1239]: session opened for user root by
> kyle(uid=1000)
> Dec 21 19:42:46 nb0 apmd[699]: Battery: -0.055762 (0:18) 4294967295
> days, 4294967291:4294967244 (100% unknown)
> Dec 21 20:06:37 nb0 modprobe: modprobe: Can't locate module char-major-97
> Dec 21 20:06:37 nb0 last message repeated 3 times
> Dec 21 20:07:02 nb0 modprobe: modprobe: Can't locate module freedos
> Dec 21 20:07:09 nb0 modprobe: modprobe: Can't locate module freefat
> Dec 21 20:07:24 nb0 kernel: Attached scsi removable disk sda at scsi0,
> channel 0, id 0, lun 0
> Dec 21 20:07:24 nb0 kernel: usb-uhci.c: interrupt, status 3, frame# 228
> Dec 21 20:07:24 nb0 kernel: usb-uhci.c: interrupt, status 3, frame# 242
> Dec 21 20:07:24 nb0 kernel: usb-uhci.c: interrupt, status 3, frame# 256
> Dec 21 20:07:24 nb0 kernel: sda : READ CAPACITY failed.
> Dec 21 20:07:24 nb0 kernel: sda : status = 1, message = 00, host = 0,
> driver = 08
> Dec 21 20:07:24 nb0 kernel: Current sd00:00: sense key Not Ready
> Dec 21 20:07:24 nb0 kernel: Additional sense indicates Medium not present
> Dec 21 20:07:24 nb0 kernel: sda : block size assumed to be 512 bytes,
> disk size 1GB.
> Dec 21 20:07:24 nb0 kernel: sda: I/O error: dev 08:00, sector 0
> Dec 21 20:07:24 nb0 kernel: unable to read partition table
> Dec 21 20:07:24 nb0 kernel: Device not ready. Make sure there is a disc
> in the drive.
> Dec 21 20:07:24 nb0 kernel: usb-uhci.c: interrupt, status 3, frame# 292
> Dec 21 20:07:24 nb0 kernel: usb-uhci.c: interrupt, status 3, frame# 306
> Dec 21 20:07:24 nb0 kernel: usb-uhci.c: interrupt, status 3, frame# 320
> Dec 21 20:07:24 nb0 kernel: sda : READ CAPACITY failed.
> Dec 21 20:07:24 nb0 kernel: sda : status = 1, message = 00, host = 0,
> driver = 08
> Dec 21 20:07:24 nb0 kernel: Current sd00:00: sense key Not Ready
> Dec 21 20:07:24 nb0 kernel: Additional sense indicates Medium not present
> Dec 21 20:07:24 nb0 kernel: sda : block size assumed to be 512 bytes,
> disk size 1GB.
> Dec 21 20:07:24 nb0 kernel: sda: I/O error: dev 08:00, sector 0
> Dec 21 20:07:24 nb0 kernel: unable to read partition table
> Dec 21 20:07:46 nb0 kernel: SCSI device sda: 125185 512-byte hdwr
> sectors (64 MB)
> Dec 21 20:07:46 nb0 kernel: sda: Write Protect is off
> Dec 21 20:07:46 nb0 kernel: sda: sda1
> Dec 21 20:12:21 nb0 syslogd 1.4.1: restart.
>
> I don't understand why later attempts don't log to syslog, but it
> appears to me that there is data corruption of some kind in this
> particular flash card. Every test that's failed had this card involved
> and other cards have not (yet) failed.
>
> I'm not sure if I should try reformatting the flash card or if we would
> lose a valuable chance to find a potential kernel problem. Is the
> kernel expected to survive if I mount a corrupt filesystem?
>
> I realize this sounds like the problem is not in your driver, but do you
> have any suggestions?
>
> >
> >
> >On Fri, Dec 21, 2001 at 07:58:17PM -0700, Kyle wrote:
> >
> >> Are you still supporting the usb-storage code?
> >>
> >>I have some of the SDDR-31 flash readers I'm using under Linux. They
> >>seem to work most of the time but when I get a flash card with lots of
> >>pictures on it, I hard lock the machine when I try to browse the newly
> >>mounted filesystem.
> >>
> >>I'm running redhat 7.2 (2.4.9 stock kernel).
> >>
> >>Any ideas where to start looking?
> >>
> >
>
>
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
I think the problem is there's a nut loose on your keyboard.
-- Greg to Customer
User Friendly, 1/5/1999
[-- Attachment #2.1.2: Type: application/pgp-signature, Size: 232 bytes --]
reply other threads:[~2001-12-24 22:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3C27B0B0.4060500@actarg.com \
--to=kyle@actarg.com \
--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 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.