Re: EHCI: mtools stuck in state 'physrd' or panic

2005-06-26 Thread Stefan Walter
Hi, Ian Dowse, 26.06.05, 18:42h CEST: > OpenBSD have a workaround for problems with VIA EHCI controllers > that can cause the hanging symptoms you describe. Below is a patch > that implements their change in FreeBSD's driver. Could you try it > to see if it helps? I just tried, but unfortunately

Re: EHCI: mtools stuck in state 'physrd' or panic

2005-06-26 Thread Ian Dowse
In message <[EMAIL PROTECTED]>, Stefan Walter write s: >FYI: I have just sent a PR for this problem. > >http://www.freebsd.org/cgi/query-pr.cgi?pr=82660 OpenBSD have a workaround for problems with VIA EHCI controllers that can cause the hanging symptoms you describe. Below is a patch that implemen

Re: EHCI: mtools stuck in state 'physrd' or panic

2005-06-26 Thread Stefan Walter
FYI: I have just sent a PR for this problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=82660 Stefan -- No reading beyond this point pgpnIhmnGEEx6.pgp Description: PGP signature

Re: EHCI: mtools stuck in state 'physrd' or panic

2005-06-24 Thread Stefan Walter
Mike Tancsa in gmane.os.freebsd.stable: > If you reformat the USB stick with UFS2, does IO still hang the box ? I haven't tried that, but instead tried to just dump the whole USB stick to a file with "dd if=/dev/da2 of=stickimage bs=1024". The dd process also hung in state "physrd" eventually, an

Re: EHCI: mtools stuck in state 'physrd' or panic

2005-06-24 Thread Mike Tancsa
At 08:50 AM 24/06/2005, Stefan Walter wrote: I can also list the content of the FAT filesystem with mtools' mdir command. When trying to copy a file from the stick to a local filesystem, however, mcopy is almost immediately stuck in state "physrd" (according to top(1)) after copying a varying num

EHCI: mtools stuck in state 'physrd' or panic

2005-06-24 Thread Stefan Walter
Hi, I just updated to this morning's RELENG_5 and thought I'd give USB 2.0 a try to speed up data exchange with my USB sticks. The controller is correctly identified, it seems: ehci0: mem 0xdbfdf700-0xdbfdf7ff irq 3 at device 16.3 on pci0 When plugging in a USB stick, it is correctly identifie