Michal 'hramrach' Suchanek wrote:

> On Sat, Jul 19, 2003 at 12:59:27PM +0200, Lennart Augustsson wrote:
>> Can you get into the debugger when it happens?
>> 
>>    -- Lennart
> The first time I encountered this I got an uvm fault and was dropped to
> the debugger. However, the command that was supposed to give a stack trace
> caused one more (iirc the same) fault and sync did not finish, no coredump
> after reboot.

FWIW, if I remove my flash reader before unmounting it on all of
the NetBSD hosts I use it on, that host completely locks up. No
coredump, no debugger, no remote login, it doesn't even respond to
a ping at that point. It has been this way since this reader was
first enabled (last fall - post 1.6 -current).

I also have to wait until sd0 has completed the identification
sequence (last line below) before I try to mount it (I usually use
amd to mount it) or I have to reboot the host if I ever want to
mount it again.

Jul 20 17:39:01 tiamat /netbsd: umass0 at uhub2 port 1 configuration 1 interface 0
Jul 20 17:39:01 tiamat /netbsd:
Jul 20 17:39:01 tiamat /netbsd: umass0: PQI Travel Flash, rev 1.10/2.05, addr 2
Jul 20 17:39:01 tiamat /netbsd: umass0: using SCSI over Bulk-Only
Jul 20 17:39:01 tiamat /netbsd: scsibus0 at umass0: 2 targets, 1 lun per target
Jul 20 17:39:01 tiamat /netbsd: scsibus0: waiting 2 seconds for devices to settle...
Jul 20 17:39:03 tiamat /netbsd: sd0 at scsibus0 target 1 lun 0: <General, Flash Disk Drive, 2.05> disk removable
Jul 20 17:39:03 tiamat /netbsd: sd0: 8000 KB, 7 cyl, 64 head, 32 sec, 512 bytes/sect x 16000 sectors