Re: Re: Reliable unreliability with D-Link DWL-122 USB
| Newsgroups | gmane.linux.linux-wlan.user |
|---|---|
| Message-ID | <20050601085929.BYHJ26865.aamta09-winn.ispmail.ntl.com@smtp.ntlworld.com> |
> > From: Dave Jenkins <[email protected]> > > --- [email protected] wrote: > > However, its not all bad news. The main culprit > seems > > to be hald, which in versions before 0.5.0 is > regularly > > reading /proc/bus/usb/devices and thus making the > lockup > > highly likely. As far as I can see from the hal > source > > code, a major change in 0.5.0 might remove this > behaviour - > > it will do the lookup only the once rather than > frequently. > > Thanks for the info. The behaviour that I get is one > lockup shortly after booting up in the morning, > usually after accessing two or three image-heavy web > pages. I rarely get further lockups during the day > after that. I'm not sure if that fits with the culprit > being hal regularly reading /proc/bus/usb/devices. > Okay I should clarify. Hal < 0.5.0 isn't regularly reading based on a timer, but does read /proc/bus/usb/devices for EACH usb device it encounters (both when it first starts, and on subsequent hotplug events). This means that it reads several times over when it first starts. Further, it appears to me that the read doesn't immediately cause the card to lock up. Instead it seems that the read can cause the card to lock sometime in the future - perhaps minutes later (maybe when the load gets heavy?). > > Unfortunately I don't have the time or the wits to > try > > and upgrade my system to test this theory. > > I'll be upgrading from Fedora Core 3 to 4 when it > comes out shortly and it appears FC4 may use hal 0.5.2 > . I'll report back after the upgrade. > > Thanks again, > > Dave ----------------------------------------- Email provided by http://www.ntlhome.com/