On 2/11/06, Ed Wandasiewicz <[EMAIL PROTECTED]> wrote: > On Sat, Feb 11, 2006 at 01:54:21PM -0500, Nick Guenther wrote: > > On 2/11/06, Ed Wandasiewicz <[EMAIL PROTECTED]> wrote: > > > rootdev=0x0 rrootdev=0xb00 rawdev=0xb02 > > > ohci3: 1 scheduling overruns > > > ohci3: 2 scheduling overruns > > > ohci3: 1 scheduling overruns > > > ohci3: 1 scheduling overruns > > > > > > > I notice the 'uhub'. Is this an external hub or an internal one? Also, > > does the device work a) flawlessly b) somewhat (drops packets etc) c) > > not at all? I'm guessing it's just that the processor (or something?) > > can't keep up with all the data from the uhub and thus the queue gets > > "overrun". I can't really say any more though, grep the ohci and uhub > > source code for "scheduling overruns" perhaps. > > > > -Kousu > > Internal hub, inside a mac mini. ural device works 99% of the time. I do get > occasional dmesg of scrolling "usbd_dump_queue" messages, but happens > quite rarely. > > Ed.
Well then I wouldn't worry about it, the driver just can't keep up and drops some packets. I don't know where to look in the source to alter the rate but I imagine it could be done. Perhaps post a bug report and include as much information as you can on the hardware and maybe it'll help improve the driver. -Kousu
