Re: usb umass regression

On Wed, 2004-10-06 at 16:54, Brian Fundakowski Feldman wrote:
> On Wed, Oct 06, 2004 at 01:41:29PM -0700, Sean McNeil wrote:
> > My system now locks up again when I attempt to write to my pendrive
> > without going into the debugger or any output to console at all:
> > 
> > Oct  6 13:24:32 server kernel: da0 at umass-sim0 bus 0 target 0 lun 0
> > Oct  6 13:24:32 server kernel: da0: <Memorex USB2 Thumbdrive 2.00>
> > Removable Direct Access SCSI-2 device
> > Oct  6 13:24:32 server kernel: da0: 1.000MB/s transfers
> > Oct  6 13:24:32 server kernel: da0: 125MB (256000 512 byte sectors: 64H
> > 32S/T 125C)
> > 
> > mount -t msdos /dev/da0s1 /mnt
> > 
> > I used tar:
> > 
> > cd /mnt
> > (cd /; tar cf - var/named/etc) | tar xvf -
> 
> Have you tried SW_WATCHDOG?  E.g. add that option to the kernel, and these
> to /etc/rc.conf:
> watchdogd_enable="YES"
> watchdogd_flags="-s 1 -t 60"

Added this and it made no difference at all.  Locked up completely. 
This is with a latest cvsup:

CPU: AMD Athlon(tm) 64 Processor 3000+ (2000.08-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0xfc0  Stepping = 0
 
Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
  AMD Features=0xe0500800<SYSCALL,NX,MMX+,LM,3DNow+,3DNow>

uhci0: <VIA 83C572 USB controller> port 0xbc00-0xbc1f irq 21 at device
16.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <VIA 83C572 USB controller> port 0xc000-0xc01f irq 21 at device
16.1 on pci0
uhci1: [GIANT-LOCKED]
usb1: <VIA 83C572 USB controller> on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
ugen0: American Power Conversion Back-UPS RS 1000 FW:7.g3 .D USB FW:g3,
rev 1.10/1.06, addr 2
ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.10, addr 3, iclass
3/1
ums0: 3 buttons and Z dir.
uhci2: <VIA 83C572 USB controller> port 0xc400-0xc41f irq 21 at device
16.2 on pci0
uhci2: [GIANT-LOCKED]
usb2: <VIA 83C572 USB controller> on uhci2
usb2: USB revision 1.0
uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3: <VIA 83C572 USB controller> port 0xc800-0xc81f irq 21 at device
16.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <VIA 83C572 USB controller> on uhci3
usb3: USB revision 1.0
uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ucom0: Prolific Technology Inc. USB-Serial Controller, rev 1.10/3.00,
addr 2

Then I plug in...

umass0: USB Mass storage, rev 2.00/2.00, addr 2
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <Memorex USB2 Thumbdrive 2.00> Removable Direct Access SCSI-2
device
da0: 1.000MB/s transfers
da0: 125MB (256000 512 byte sectors: 64H 32S/T 125C)

mount it, write to it, then hard lockup with no debug or anything.  I
just added a firewire card, though.  Could my system now be sending
debug out that way?  I haven't looked into setting up fw debugging yet
but that is why I bought the card.

I have in my kernel config:

options         KDB                     # Enable kernel debugger
support.
options         DDB                     # Support DDB.
options         GDB                     # Support remote GDB.

Sean