Re: Re: Reliable unreliability with D-Link DWL-122 USB

Well the hotplug (coldplug) usb.rc script itself
also reads /proc and/or /sys, so potentially that could
be a problem as well!

On my system, the motherboard usb hubs start exploring
the usb bus once uhci gets loaded - which I think is
during the hotplug (coldplug) pci.rc sequence. This finds
my prism card, and launches a true hotplug event that
loads the driver ... which in turn launches a true hotplug
event to add the new 'net' interface ... which in turn
starts initialising the card to bring it up.

Now all this happens BEFORE hotplug (coldplug) gets round
to doing its own scan of the usb bus (which it does in usb.rc by looking in /sys - or on older systems /proc/bus/usb/devices), which means that this also can
be a culprit - since my card is by then already in action.

Two things to try:

- enabling hotplug debug messages (there is probably
a script of config file with a DEBUG variable that can
be set to yes) - this will log hotplug events and
their activity. From this you can see the order in which
things happen (like my description above).

- Turn off usb.rc coldplug simply by disabling the
execute permissions on the file


Karl


> 
> From: Dave Jenkins <[email protected]>
> Date: 2005/06/01 Wed PM 12:28:42 BST
> To: [email protected]
> Subject: Re: [lwlan-user] Reliable unreliability with D-Link DWL-122 USB
> 
> --- Holger Wansing <[email protected]> wrote:
> > Why don't you try to disable hal for some days to
> > see, _if_ _hal_ _is_ the problem?
> 
> Thanks, I assumed without checking that hal is
> something I need. I have tried disabling it and
> rebooting a couple of times. Result: exactly the same
> as before. I.e. network hangs shortly after boot,
> after accessing a couple of web pages. I have verified
> that hal is not running.
> 
> So perhaps something else is reading
> /proc/bus/usb/devices - udev, maybe?
> 
> Dave


-----------------------------------------
Email provided by http://www.ntlhome.com/