The following in done on an Thinkpad X60s. First i have to load the sierra manually. If i do this right after a clean reboot, i get a /dev/ttyUSB0 device that gives me access to my umts modem. After a suspend to ram and resume /dev/ttyUSB0 is missing. Even reloading usbserial and sierra kernel modules does not fix this situation. Only a clean reboot brings it back. UMTS does only work with regular kernels. I can not get it to work with kernel-PAE at all. Version-Release number of selected component (if applicable): All F11 kernel modules currently : 2.6.29.6-213.fc11.i586 How reproducible: - Install F11 - update, # modprobe sierra, # ls /dev/ttyUSB0 - suspend resume # ls /dev/ttyUSB0 Expected results: umts device to survice suspend and resume. This worked on Fedora8 :-)
I found a work around to rebooting my fedora evertime i want to start umts after a suspend to ram. I just need to flip the wireless kill switch to kill wireless for a few seconds. When i switch it back to allow wireless, the umts devices are created again.
Flipping the switch though is not allways enough to bring the devices back. Running this script usually helps : #!/bin/bash rmmod sierra rmmod usbserial sleep 1 modprobe sierra
I've seen the same exact problem on an IBM/lenovo x300. Suspend/Resume of the sierra driver worked perfectly in Fedora 10, but once I switched to FC11, /dev/ttyUSB0 disappears after resume. Confirmed that cycling the rf-kill switch works in bringing the device back (at least the first time I tried it).
Also here with a Thinkpad X61s and internal UMTS modem. I don't have to manually modprobe sierra in on boot, but after resume the device is gone.
i can confirm this on a thinkpad x60s running 2.6.29.6-217.2.16.fc11.i586, cycling the wireless kill switch brings /dev/ttyUSB0 back for me as well. one more symptom is that NetworkManager (nm-applet actually) seems to lose the "Mobile Broadband" device from its context menu list after suspend/resume (probably because /dev/ttyUSB0 is gone?). The device entry does not come back after cycling the kill switch. I can only see it again after rebooting.
Changed to kernel: 2.6.29.5-191.fc11.i586 Still have the same issue. But a bit different if i try reloading the module. I don't get /dev/ttyUSB0 back after resume. If i unload + reload the sierra module i'll get ttyUSB3 to ttyUSB5 instead. Only if i unload sierra before sleep i'll get ttyUSB0 back.
Can you attach the dmesg output and /var/log/pm-suspend.log after suspend/resume? It is better to update to the newest kernel in fedora.
I tried the latest kernel in F11. kernel-2.6.30.8-64.fc11.i586. Loading sierra showed no ttyUSB* devices at all.
Same for me. The latest FC11 kernel (kernel-2.6.30.8-64.fc11.x86_64) was worse. 1) ttyUSB* doesn't show up at all 2) the wifi did not return after reboot.
I've been having issues with wwan in 2.6.30.8-64 over in bug #527463 - the later comments here sound like the same thing (but potentially different from the earlier post-suspend issues?). Curiously if I boot back into 2.6.29 and get wwan back, it persists for "a while" back in 2.6.30 - can you reproduce this behaviour?
issue still exists in latest rawhide kernel: 2.6.31.5-96.fc12.i686.PAE unloading and loading the sierra module still fixes the problem.
ok, just checked f11 latest kernel : kernel-2.6.30.9-90.fc11.i586 and kernel-PAE-2.6.30.9-90.fc11.i686 -> i have no /dev/ttyUSB* in those kernels at all, even after flipping the switch and reloading the sierra module At the moment i'm using : 2.6.29.5-191.fc11.i686.PAE this works quite well, as i sometimes need only flip the kill wireless switch back and forth to see the umts device in NetworkManager. But most of the time i still need to reload the sierra module. Stragely enough i need to do this twice... Regarding comment #7 i'll attach the files right away.
Created attachment 367341 [details] /var/log/pm-suspend.log Don't know if that will help. This was with 2.6.29.5-191.fc11.i686.PAE.
Created attachment 367342 [details] dmesg after suspend this looks interesting, done with 2.6.29.5-191.fc11.i686.PAE
Very interesting. Lutz, is there a chance for you to upgrade to F12? It would make my negotiations with upstream easier.
Here's the removal of low_latency thing that causes a flip buffer push to go directly into the line discipline: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=2400a2bfbd0e912193fe3b077f492d4980141813 It went in after 2.6.29. I bet Lutz's problem would go away if we just dropped it from sierra.
I'll upgrade to F12 as soon as i get the chance. This will probably be somewhere between Xmas and New Year :-) ... Cheers Lutz
problem still exists in F12.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.