Launchpad has imported 16 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=501109.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2009-05-16T14:11:17+00:00 Olivier wrote: Created attachment 344269 sosreport of the system Description of problem: Ther system experiences hard hang when using WIFI with the rtl8180 kernel module. The system ends in such a state that sysrq is inefficient (sysrq-t, sysrq-m, sysrq-c do nothing) and quite often require a complete electrical unplug for several seconds to be able to reboot. Console logs or /var/log/message show no oops or kernel backtrace. Blacklisting the module rtl8180 or removing the Belkin WIFI G PCI card cures the problem but does not help with WIFI connectivity ^_~ Version-Release number of selected component (if applicable): kernel-PAE-2.6.29.3-140.fc11.i686 (But occurs on older kernel as well, including F10) How reproducible: 100% reproducible Steps to Reproduce: 1. Install the Belkin Wireless G dektop PCI card Based on the Realtek 818x 2. Boot the system Actual results: System will hang either at login or at logout Expected results: System remains stable and functional Additional info: The WIFI connection uses hidden ESSID and WPA/WPA2 security. The problem occurs either when NetworkManager connects to the network or when it terminates (logging out from the user session leads to a 100% hang). Same happens if NetworkManager exits or needs to reconnect. The same hardware works perfectly under Windows with Belkin's provided driver though. I am attaching the sosreport of the system, unfortunately I am unable to debug this issue much further and I could not come up with a usable workaround for the issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/2 ------------------------------------------------------------------------ On 2009-06-09T15:55:39+00:00 Bug wrote: This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/4 ------------------------------------------------------------------------ On 2009-12-29T21:50:55+00:00 Skippy wrote: I can confirm this bug for Fedora 12 with the following wifi card : Zyxel G-302 v3. For some other reason I cannot achieve a proper install right now so I can confirm only with the live CD, but symptoms are exactly the same as above : boot ok, user session ok, if I click on the NetworkManager icon I can select the network, then connect to it, enter my WEP key, and then the system will freeze (while asking for the keyring password, secondarily). If I don't try to connect, everything works fine but the system won't shutdown (didn't try to logout). Similar issues happen with Ubuntu, cf https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/11 ------------------------------------------------------------------------ On 2010-03-16T18:14:38+00:00 Sylvain wrote: I too confirm this kernel hang with a TRENDdet TEW-423PI (C1.0R) on a up to date Fedora 12 the only message when manually activating the connection was some "invalid parameter" message when using the GUI Otherwise when on startup or command line nothing is showing but only the endless hang BTW this is a blocker on the rescue mode if the interface is checked on as managed by the NetworkManager My workaround has been to let this card disabled :( obviously that was not my goal Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/18 ------------------------------------------------------------------------ On 2010-04-27T14:21:20+00:00 Bug wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/19 ------------------------------------------------------------------------ On 2010-04-30T17:39:56+00:00 John wrote: Created attachment 410552 rtl8180: fix tx status reporting Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/20 ------------------------------------------------------------------------ On 2010-04-30T17:42:19+00:00 John wrote: http://koji.fedoraproject.org/koji/taskinfo?taskID=2149629 I don't get any such hang on F-12 w/ my cardbus rtl8185 device. However, I did get rather poor performance. Are you still seeing this hang with the test kernels above? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/21 ------------------------------------------------------------------------ On 2010-05-24T02:39:21+00:00 Steven wrote: I just installed f12 on my wife's computer (she finally got frustrated enough with Windows to let me do it), and it hit this bug. I have the following card: ZyXEL ZyAIR G-302 >From lspci -vv 02:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller (rev 20) Subsystem: ZyXEL Communication Corporation Device 340d Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (8000ns min, 16000ns max), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at 2000 [size=256] Region 1: Memory at e8100000 (32-bit, non-prefetchable) [size=512] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: rtl8180 Kernel modules: rtl8180 Seems to be a race condition. It gets past setting up the wlan0 every other boot or so. Once it is up and running, everything is fine. I tried suspend and resume once, and that locked up on resume too (even though this is a desktop, it should still support s2r). I'm currently doing a "yum update", I'll report again with the results of the latest kernel. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/22 ------------------------------------------------------------------------ On 2010-05-24T13:07:37+00:00 Steven wrote: After doing a "yum update" and updating all packages since the fresh f12 install (which included the kernel package), I have yet to hit this bug. I've rebooted 4 times and suspend and resumed twice. So far, so good. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/23 ------------------------------------------------------------------------ On 2010-05-24T13:59:08+00:00 Steven wrote: Spoke too soon. Seems the race condition is smaller. While showing my wife how to use her box, it locked up on suspend and resume while (I think) initializing the network. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/24 ------------------------------------------------------------------------ On 2010-05-24T16:57:45+00:00 John wrote: Steven, and logs available? Perhaps you could capture a trace using netconsole (over a wired port)? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/25 ------------------------------------------------------------------------ On 2010-05-26T00:41:39+00:00 Steven wrote: John, investigating this further, the lockup seemed to have nothing to do with the network card. It looks like a drm/i915 bug. But it takes out the network too, although I don't know why. It looks like I'm hitting this bug: https://bugzilla.redhat.com/show_bug.cgi?id=573177 As far as I can tell from the logs when it locks up now. It does not seem to be related to the wifi nic, but to the video. I don't understand why I lose my wireless on the X lockup. I'm fine on serial. I'll try again with a wired connection, but as far as I'm concerned, it looks like this BZ is done. I would like a working system before I conclude that though ;-) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/26 ------------------------------------------------------------------------ On 2010-05-27T19:05:20+00:00 Steven wrote: Interesting, after pulling the pci wireless card, I can not make X lockup. I wonder if it is related. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/27 ------------------------------------------------------------------------ On 2010-05-27T20:59:55+00:00 Steven wrote: Nevermind, I was able to finally reproduce the hang without the wireless card. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/28 ------------------------------------------------------------------------ On 2010-06-09T17:46:23+00:00 John wrote: I can't recreate any problems -- this driver works reasonably well for me. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/29 ------------------------------------------------------------------------ On 2010-06-22T23:10:32+00:00 Sylvain wrote: (In reply to comment #14) > I can't recreate any problems -- this driver works reasonably well for me. It just means the card you own works fine with it.... Btw do you own a realtek branded one ? Thanks in advance Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/comments/30 ** Changed in: fedora Status: Confirmed => Invalid ** Changed in: fedora Importance: Unknown => High ** Bug watch added: Red Hat Bugzilla #573177 https://bugzilla.redhat.com/show_bug.cgi?id=573177 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/368679 Title: wifi module rtl8180 freezes the system Status in linux package in Ubuntu: Won't Fix Status in Debian: New Status in Fedora: Invalid Bug description: On computers with some rtl818x chip based wifi cards, when module rtl8180 is modprobed this causes a complete freeze of the system. This issue is severe for two reasons: * computers with such wifi cards aren't able to connect to their network via wifi through a native linux driver; * because rtl8180 is modprobed at startup, when a new user tries Ubuntu on such computer, the liveCD will show a black screen without any error message, and then the user will blame Ubuntu. Although there are already some similar bug reports, they are all too specific to another hardware so the aim of this report is to centralize any information about actual system freezes caused by rtl8180 modprobes. In addition, this bug has been initially described in previous bug #152527. Affected Ubuntu releases: Intrepid, Jaunty, Karmic Affected wifi cards : * MSI PC54G3 III (chipset RTL8185L) * Zyxel G-302 V3 Workarounds: * ndiswrapper: * works on Intrepid but not on Jaunty * manual install of Realtek's supported driver: * at least it seems it prevents the system from freezing * still in testing: some can connect to the network, some not ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 LsUsb: Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0ac8:303b Z-Star Microelectronics Corp. ZC0303 WebCam Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub NonfreeKernelModules: nvidia Package: linux-image-2.6.27-14-generic 2.6.27-14.33 ProcCmdLine: root=UUID=94814e6a-5868-4218-85ea-ff6550520509 ro quiet splash ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.27-14.33-generic SourcePackage: linux UnreportableReason: Ceci n'est pas un authentique paquet Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/368679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
