On 2/11/06, Ed Wandasiewicz <[EMAIL PROTECTED]> wrote: > I have the following dmesg with a ural device attached to a macppc, > following current, as of 8 Feb 2006. > > Any suggestions? > Ed. > wd0(wdc1:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 2 > cd0(wdc1:0:1): using PIO mode 4, DMA mode 2, Ultra-DMA mode 2 > "Apple UniNorth Firewire" rev 0x81 at pci2 dev 14 function 0 not configured > gem0 at pci2 dev 15 function 0 "Apple Uni-N2 GMAC" rev 0x80: irq 41, address > 00:11:24:8b:aa:18 > bmtphy0 at gem0 phy 0: BCM5221 100baseTX PHY, rev. 4 > ural0 at uhub5 port 2 > ural0: ASUS 802.11g WLAN Drive, rev 2.00/0.01, addr 2 > ural0: MAC/BBP RT2570 (rev 0x03), RF RT2526, address 00:11:d8:dc:2b:3c > ueagle0 at uhub3 port 1 > ueagle0: U.S. Robotics USR9000 SureConnect ADSL, rev 1.00/40.0b, addr 2 > ueagle0: address: 00:c0:49:b7:37:4a > bootpath: '/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/bsd' > boot device: wd0. > root on wd0a > 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
