In message: <E1I37RI-0000Z5-6B_at_clue.co.za> Ian FREISLICH <ianf_at_clue.co.za> writes: : "M. Warner Losh" wrote: : > In message: <E1I2ic4-0000bu-Fo_at_clue.co.za> : > Ian FREISLICH <ianf_at_clue.co.za> writes: : > : Ian FREISLICH wrote: : > : > I also fixed the onboard wireless mouse controller which previously : > : : > : s/I/It/ : > : : > : > worked for about 10 minutes before a usb bus error broke the : > : > connection. : > : : > : Seems I spoke too soon. After running fine for about an hour the : > : wireless mouse died with the following error: : > : : > : Jun 25 09:00:53 apple kernel: usb3: host controller process error : > : Jun 25 09:00:53 apple kernel: usb3: host controller halted : > : : > : Is there any debugging knob I can turn to get more data about what : > : went wrong? : > : > I don't know. You can try configuring USBDEBUG in your kernel, then : > setting hw.ums.debug=1, but that tends to generate a lot of traffic in : > an hour. : : Hmm. Not much more to go on: : : usb3: host controller process error : usb3: host controller halted : usb3 regs: cmd=0080, sts=0030, intr=000f, frnum=05f7, flbase=01bba7dc, sof=0040, portsc1=0095, portsc2=01a5 : intrs=33921 : QH(0xc4e02f80) at 01ba8f80: hlink=01ba8fa2 elink=00000001 You might try hw.usb.debug=1 (or some higher value). WarnerReceived on Tue Jun 26 2007 - 12:32:13 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:13 UTC