Re: Kodak USB flash reader causes freezes, panics

2005-04-27 Thread Brooks Davis
On Wed, Apr 27, 2005 at 07:42:35PM -0400, Tim Howe wrote:
> Brooks Davis <[EMAIL PROTECTED]> writes:
> 
> >> > > Reproducibly, if I begin copying data to a [...] CF card [...] it
> >> > > works for a while, then freezes the system.
> [...]
> > Sounds like you should file a PR about the issue.  Are you sure the file
> > system in question is OK?  There were some msdosfs corruption bugs fixed
> > recently.
> 
> Taking your suggestion I zeroed out the CF card, then used fdisk and
> newfs_msdos to get it in working order again.  I've been testing it
> over the past week and have had no problems since.
> 
> Thanks for the pointer.  Is it accepted for a corrupt filesystem to
> freeze the system, though?

No, but that's what broken code often does. :(

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4


pgputg1brEq2q.pgp
Description: PGP signature


Re: Kodak USB flash reader causes freezes, panics

2005-04-27 Thread Tim Howe
Brooks Davis <[EMAIL PROTECTED]> writes:

>> > > Reproducibly, if I begin copying data to a [...] CF card [...] it
>> > > works for a while, then freezes the system.
[...]
> Sounds like you should file a PR about the issue.  Are you sure the file
> system in question is OK?  There were some msdosfs corruption bugs fixed
> recently.

Taking your suggestion I zeroed out the CF card, then used fdisk and
newfs_msdos to get it in working order again.  I've been testing it
over the past week and have had no problems since.

Thanks for the pointer.  Is it accepted for a corrupt filesystem to
freeze the system, though?

>> [1042] ~ # true > /dev/da0   
[...]
>
> I'd highly recommend running the command in the other direction so you
> try to read rather than write.  It shouldn't matter, but that makes me
> nervous (not that I think it has anything to do with your problem.)

I tried that, and doing a read and waiting a few seconds.  Opening for
write, as above, worked immediately.

-- 
Tim Howe
Software Engineer
Celebrity Resorts
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Kodak USB flash reader causes freezes, panics

2005-04-12 Thread Brooks Davis
On Mon, Apr 11, 2005 at 10:14:14PM -0400, Tim Howe wrote:
> Brooks Davis <[EMAIL PROTECTED]> writes:
> 
> > On Mon, Apr 11, 2005 at 05:24:15PM -0400, Tim Howe wrote:
> >
> > > Reproducibly, if I begin copying data to a [...] CF card [...] it
> > > works for a while, then freezes the system.
> >
> > It is quite likely that 5.4 fixed your problem.
> 
> Unfortunately not.  I was able, having mounted the filesystem with no
> synchronization options, to copy 171MiB of data onto it and unmount.
> However when I re-mounted it with the same options and tried to copy
> 71MiB more, it again froze midway through.

Sounds like you should file a PR about the issue.  Are you sure the file
system in question is OK?  There were some msdosfs corruption bugs fixed
recently.

> Everything else (X11, sound, printing, input) seems to be working
> perfectly with 5.4, but I did notice something new and strange with
> regard to umass.  I still have to run "true > /dev/da0" to get the slice
> to show up, but now I get the following:
> 
> [1042] ~ # true > /dev/da0   
> [1043] ~ # camcontrol rescan 0   
> Re-scan of bus 0 was successful
> [1044] ~ # ls -l /dev/da0*   
> crw-r-  1 root  operator4,  21 Apr 11 21:45 /dev/da0
> crw-r-  1 root  operator4,  28 Apr 11 21:45 /dev/da0s1
> crw-r-  1 root  operator4,  29 Apr 11 21:45 /dev/da0s1s1
> [1045] ~ # mount_msdosfs /dev/da0s1 /mnt/cf 
> [1046] ~ # umount /mnt/cf 
> [1047] ~ # mount_msdosfs /dev/da0s1s1 /mnt/cf
> [1048] ~ # umount /mnt/cf

I'd highly recommend running the command in the other direction so you
try to read rather than write.  It shouldn't matter, but that makes me
nervous (not that I think it has anything to do with your problem.)  It
would appear that your da0s1 has data at the front that looks like an
MBR and GEOM is attaching to it.  I'm not sure what the best solution to
that problem is.  Probably a reformat.

-- Brooks

--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4


pgp8wZIaFCZxM.pgp
Description: PGP signature


Re: Kodak USB flash reader causes freezes, panics

2005-04-11 Thread Tim Howe
Brooks Davis <[EMAIL PROTECTED]> writes:

> On Mon, Apr 11, 2005 at 05:24:15PM -0400, Tim Howe wrote:
>
> > Reproducibly, if I begin copying data to a [...] CF card [...] it
> > works for a while, then freezes the system.
>
> It is quite likely that 5.4 fixed your problem.

Unfortunately not.  I was able, having mounted the filesystem with no
synchronization options, to copy 171MiB of data onto it and unmount.
However when I re-mounted it with the same options and tried to copy
71MiB more, it again froze midway through.

Everything else (X11, sound, printing, input) seems to be working
perfectly with 5.4, but I did notice something new and strange with
regard to umass.  I still have to run "true > /dev/da0" to get the slice
to show up, but now I get the following:

[1042] ~ # true > /dev/da0   
[1043] ~ # camcontrol rescan 0   
Re-scan of bus 0 was successful
[1044] ~ # ls -l /dev/da0*   
crw-r-  1 root  operator4,  21 Apr 11 21:45 /dev/da0
crw-r-  1 root  operator4,  28 Apr 11 21:45 /dev/da0s1
crw-r-  1 root  operator4,  29 Apr 11 21:45 /dev/da0s1s1
[1045] ~ # mount_msdosfs /dev/da0s1 /mnt/cf 
[1046] ~ # umount /mnt/cf 
[1047] ~ # mount_msdosfs /dev/da0s1s1 /mnt/cf
[1048] ~ # umount /mnt/cf

Thoughts?

FreeBSD beaker.data-secure.net 5.4-RC2 FreeBSD 5.4-RC2 #2: Mon Apr 11 20:31:53 
EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Kodak USB flash reader causes freezes, panics

2005-04-11 Thread Brooks Davis
On Mon, Apr 11, 2005 at 05:24:15PM -0400, Tim Howe wrote:
> I'm not sure if this should go here or to -bugs, but the other
> USB-related reports put me in good company, I'm hoping...
> 
> I'm having a problem with a Kodak USB flash reader.  "camcontrol
> inquiry" gives me:
> 
>   pass0:  Removable Direct Access SCSI-0 device 
>   pass0: Serial Number 
>   pass0: 1.000MB/s transfers 
> 
> The device has printed on it:
> 
>   Kodak Multi-Card Reader   CE2A012
> KP P/N 7E3771
> ITEM# 20209416
> P/N 680-070-563
> 
> Reproducibly, if I begin copying data to a Lexar 256MB CF card (P/N
> 2250, Rev. A), it works for a while, then freezes the system.  The first
> time this happened it was when trying to unmount the filesystem.  The
> second time was in the midst of copying data.  Both times the system was
> completely frozen; not even the keyboard LEDs toggled.  Strangely, I
> could connect on the SSH and FTP ports, but received no welcome banner.
> 
> The third time I modified the script I was using to copy my files to
> sync and sleep after each file.  This time the system seemed to freeze,
> then lurch through handling several interrupts (mouse pointer moved and
> a menu popped up from right-clicking), then froze again.  Initially
> connecting to the SSH port brought up the banner after a very long
> delay, but an attempt to reproduce this was unsuccessful, and I was
> unable to actually SSH in.
> 
> Mounting the filesystem synchronously doesn't seem to help.  The first
> time it worked, but then when I unmounted and remounted it and copied
> some more files it froze midway through.
> 
> I'm running FreeBSD 5.3:
> 
> FreeBSD beaker.data-secure.net 5.3-RELEASE-p8 FreeBSD 5.3-RELEASE-p8 #1: Mon 
> Apr 11 15:20:08 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  
> i386
> 
> I will be fairly busy for the next few days but later this week I should
> be able to try out patches or set up a machine running a more
> cutting-edge source tree, if necessary.  I've got FreeBSD 5.4-RC2
> building today, actually; is it likely that this will solve my problem?

It is quite likely that 5.4 fixed your problem.  Not certain, of course,
but many problems have been fixed recently.

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4


pgpEl9k3d1gNq.pgp
Description: PGP signature