On Friday 28 January 2005 16:38, you wrote: > On Fri, 28 Jan 2005 [EMAIL PROTECTED] wrote: > > Hello, > > > > I've got some trouble with my external ISDN modem (AVM Fritz!CARD > > USBv2.0) since I changed from kernel 2.4.20 (SuSE 8.2) to 2.6.8 (SuSE > > 9.2). The modem is running perfectly for a couple of seconds and then the > > message > > > > kernel: hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling... > > > > appears in the logs and everything breaks. Meanwhile I managed to fix the > > driver fcusb2 so that it not causing a kernel oops any more, but I dont > > think that the origin of my problem comes from this driver. > > You could try upgrading to 2.6.10 or even 2.6.11-rc2 to see if the problem > has already been fixed.
Ok, I will try that first. > > Regarding the obscure kernel message above, I found that it is sent by > > drivers/usb/core/hub.c (module usbcore) when USB_PORT_STAT_ENABLE is set > > in portstatus. > > No, it is sent when USB_PORT_STAT_C_ENABLE is set and USB_PORT_STAT_ENABLE > is _not_ set (among other requirements). You are right, I didn't remember all details when I wrote the mail. > > I tried to follow the way of this status signal back to its > > roots, but ended soon in ith URB stuff in drivers/usb/core/message.c, > > which I don't understand. > > Don't worry about following it back; it comes more or less directly from > the hub (the root hub in your case). > > > My questions: > > - Does anybody know the origin of this portstatus flag? (my guess: the > > origin is a hcd module and the status is transmittet to usbcore by a URB > > message) > > That's right. The HCD gets the status from the USB controller hardware. Ok, I will have a closer look on the HCD code and compare it with kernel 2.4, since there is still no problem as long as I use the old kernel. When the status really comes directly from the hub *hardware*, then it must have been ignored or overlooked in kernel 2.4, or the initialization of the hub is different, or the problem is caused by unappropriate hardware access, ... (I'm afraid this will turn out to be difficult, but I will try it :-) > > - This should be an easy one, but I couldn't find the answer: How do I > > find out which hcd driver is actually used for my modem? > > Look in the system log. There will be messages for each HCD and each > USB device as they are initialized, listing the bus number along with > other information. Just match up the entries by bus number (it's the part > before the '-' in the device name; for example 2-0:1.0 indicates bus 2). > > > - Where do I find a short introduction to URBs? > > There are a lot of references available on <http://www.linux-usb.org>. > > Alan Stern Thank you very much, your answer helps me to skip the URB stuff and jump directly into the driver code. And sorry for the last two questions. Reinhard Caspary ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
