What motherboards are you using with the OHCI controller?
John-Mark Gurney (jmg@) and I kicked this around at bsdcon but couldn't
reproduce it. If its a common board or chipset we can probably get it and
work on the issue. The zeroed block showed up in 8KB boundaries in the
instance we saw, whic
-- Your message was: (from "Wesley Morgan")
On Fri, 26 Sep 2003, Brian Fundakowski Feldman wrote:
> I can get fdisk to read the MBR, but when I try mdir, I get this trace back
> (of course, no crash dump because those haven't worked for me in a year):
> trap 0xc
> memcpy()
> ohci_softintr()
> us
On Fri, 26 Sep 2003, Brian Fundakowski Feldman wrote:
> I can get fdisk to read the MBR, but when I try mdir, I get this trace back
> (of course, no crash dump because those haven't worked for me in a year):
> trap 0xc
> memcpy()
> ohci_softintr()
> usb_schedsoftintr()
> ohci_intr1()
> ohci_intr()
On Friday 26 September 2003 09:18, Brian Fundakowski Feldman wrote:
> ohci_intr()
> ithread_loop()
>
> Anyone have any clued? I'll include my dmesg, of course.
Yes, the same bad thing with umass on my sony vaio pcg-v505bx laptop.
This is the only reason I have to keep slackware linux within to
I can get fdisk to read the MBR, but when I try mdir, I get this trace back
(of course, no crash dump because those haven't worked for me in a year):
trap 0xc
memcpy()
ohci_softintr()
usb_schedsoftintr()
ohci_intr1()
ohci_intr()
ithread_loop()
Anyone have any clued? I'll include my dmesg, of cou
