Bug 9281 - hald forgets about wifi device after suspend/resume
Summary: hald forgets about wifi device after suspend/resume
Status: RESOLVED NOTOURBUG
Alias: None
Product: hal
Classification: Unclassified
Component: hald (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: David Zeuthen (not reading bugmail)
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-07 16:51 UTC by Jeff Laughlin
Modified: 2007-04-19 00:24 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
verbose hald syslog output from execution through syspend/resume cycle (322.60 KB, text/plain)
2006-12-07 16:52 UTC, Jeff Laughlin
Details
lshal output before sleep (Thinkpad T41p) (97.49 KB, text/plain)
2007-01-06 06:52 UTC, Tim Niemueller
Details
lshal output after sleep (Thinkpad T41p) (96.73 KB, text/plain)
2007-01-06 06:54 UTC, Tim Niemueller
Details

Description Jeff Laughlin 2006-12-07 16:51:26 UTC
Fedora Core 6
hal-0.5.8.1-5.fc6
madwifi-0.1823.20061128-6 (latest snapshot, also tried latest stable release)

I boot up, everything is fine. lshal shows my ath0 wifi device. I
suspend/resume, now lshal does NOT show my ath0 wifi device. I restart hald and
now lshal DOES show my ath0 wifi device.

ath0 is listed in /sys/class/net the whole time and I can manipulate the ath0
device with iwconfig/iwlist/ifconfig.

I also submitted this as a bug on the fedora bugzilla
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=218833
Comment 1 Jeff Laughlin 2006-12-07 16:52:26 UTC
Created attachment 8008 [details]
verbose hald syslog output from execution through syspend/resume cycle
Comment 2 Danny Kukawka 2006-12-13 09:42:20 UTC
please provide lshal before suspend and after resume.
Comment 3 Tim Niemueller 2007-01-06 06:52:13 UTC
Created attachment 8312 [details]
lshal output before sleep (Thinkpad T41p)
Comment 4 Tim Niemueller 2007-01-06 06:54:14 UTC
Created attachment 8313 [details]
lshal output after sleep (Thinkpad T41p)

This time the device was actually detected but could not connect. I had to do
"rmmod ath_pci; modprobe ath_pci". Afterwards the ath0 device does no longer
appear in hal output, wifi0 does.
Comment 5 Danny Kukawka 2007-02-09 10:27:46 UTC
Since the log indicates that only the remove event for ath0 get recieved by hal (for wifi0 we get a remove and a add event). IMO this looks for me like a kernel/udev problem and not a HAL problem. 

please start as root user 'udevmonitor --env > /tmp/ath_test_udev',  then suspend the machine and resume. Attach the file /tmp/ath_test_udev to the bug.
Comment 6 Danny Kukawka 2007-04-19 00:24:01 UTC
no news since 2 months close bug


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.