Re: How to crash a 4.99.69 with nothing but an USB stick...

[David Hopper <dhop%nwlink.com@localhost>]

This got me too.  I had just bought a Dynex 2-port USB 2.0 PCI card  
and 320GB USB drive to do some network backups on my 4.99.69 x86 box.   
The drive was formatted FFS, mounted with softdep.  I successfully  
copied some 40 GB of data over SFTP, then the system wedged hard.   
Upon rebooting, the drive's magic number was gone, and could not be  
recovered from any of the backup sectors.

uhci0 at pci1 dev 10 function 0: VIA Technologies VT83C572 USB  
Controller (rev. 0x62)
uhci0: interrupting at ioapic0 pin 21
usb0 at uhci0: USB revision 1.0
uhci1 at pci1 dev 10 function 1: VIA Technologies VT83C572 USB  
Controller (rev. 0x62)
uhci1: interrupting at ioapic0 pin 22
usb1 at uhci1: USB revision 1.0
ehci0 at pci1 dev 10 function 2: VIA Technologies VT8237 EHCI USB  
Controller (rev. 0x65)
ehci0: interrupting at ioapic0 pin 16
ehci0: dropped intr workaround enabled
ehci0: EHCI version 1.0
ehci0: companion controllers, 2 ports each: uhci0 uhci1
usb2 at ehci0: USB revision 2.0
[...]
uhub0 at usb0: VIA Technologies UHCI root hub, class 9/0, rev  
1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhub1 at usb1: VIA Technologies UHCI root hub, class 9/0, rev  
1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhub2 at usb2: VIA Technologies EHCI root hub, class 9/0, rev  
2.00/1.00, addr 1
uhub2: 4 ports with 4 removable, self powered
[...]
umass0 at uhub2 port 1 configuration 1 interface 0
umass0: SimpleDrive PS SimpleTech, rev 2.00/1.00, addr 2
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, 1 lun per target
sd0 at scsibus0 target 0 lun 0: <WDC WD32, 00BEVT-22ZCT0, 11.0> disk  
fixed
sd0: fabricating a geometry
sd0: 298 GB, 305245 cyl, 64 head, 32 sec, 512 bytes/sect x 625142448  
sectors

--Dave


On Jul 23, 2008, at 1:55 PM, Jared D. McNeill wrote:

> Martin S. Weber wrote:
> > On Wed, Jul 23, 2008 at 03:08:54PM -0400, Jared D. McNeill wrote:
> > > (...)
> > > "Me too". Not right away, but eventually it happens. I'm not sure  
> > > that it's msdosfs specific, and every time I've triggered it I  
> > > seem to be using X at the time so I have yet to catch the panic  
> > > message.
> > Uh yes, I forgot. Freeze might be panic in X. I was running X at  
> > the time, too.
>
> Just after I wrote my last email I had another one, laptop had been  
> up for >2 days, plugged in my Blackberry to charge it, and it froze  
> or panic'd again. Didn't even have to mount it.
>
> Output from a normal attachment of it:
>
> uberry0 at uhub1 port 1
> uberry0: Research In Motion RIM Mass Storage Device, rev 1.10/1.06,  
> addr 2
> uberry0: at uhub1 port 1 (addr 2) disconnected
> uberry0: detached
> umass0 at uhub1 port 1 configuration 1 interface 1
> umass0: Research In Motion RIM Composite Device, rev 1.10/1.06, addr 2
> umass0: using SCSI over Bulk-Only
> scsibus0 at umass0: 2 targets, 1 lun per target
> sd0 at scsibus0 target 0 lun 0: <RIM, BlackBerry SD, 0001> disk  
> removable
> sd0: drive offline
>
> Cheers,
> Jared