[Bug 427111] New: YaST2 network freezes when PCI WLAN card when RTL8185 present
https://bugzilla.novell.com/show_bug.cgi?id=427111 Summary: YaST2 network freezes when PCI WLAN card when RTL8185 present Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: andreas.schallenberg@eurobild.com QAContact: jsrain@novell.com Found By: Community User I set up a PC (32 bit system, P III) with openSUSE 11.0 and installed patches via ethernet. Then I added a PCI WLAN card and tried to set it up... but I can't. YaST2 network setup reliably freezes, since I installed that card. It is a Longshine LCS-8031G3 with a RTL8185 chipset. lspci reports: 02:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller (rev 20) A web search reveals that some linux systems with other distros also freeze or stutter when trying to connect to a network using a card with that chipset. Examples: http://ubuntuforums.org/archive/index.php/t-210958.html https://bugs.launchpad.net/ubuntu/+bug/152527 http://www.dslreports.com/forum/r19693840-Re-Home-Network-Need-HELP-setting-... Updating the kernel to a fresh version (2.6.27rc3) from: http://download.opensuse.org/repositories/Kernel:/Vanilla/openSUSE_11.0 ..but that didn't change anything. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=427111
User andreas.schallenberg@eurobild.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c1
--- Comment #1 from Andreas Schallenberg
https://bugzilla.novell.com/show_bug.cgi?id=427111
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=427111
User andreas.schallenberg@eurobild.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c2
Andreas Schallenberg
https://bugzilla.novell.com/show_bug.cgi?id=427111
User zoz@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c3
Christian Zoz
https://bugzilla.novell.com/show_bug.cgi?id=427111
User andreas.schallenberg@eurobild.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c4
Andreas Schallenberg
https://bugzilla.novell.com/show_bug.cgi?id=427111
User zoz@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c5
Christian Zoz
Here are some additional test results:
* The system freezes during boot on both cards, but late in the boot process. This happens, if network devices are controlled by network manager.
Andreas, could you please disable network at boottime completely and start NM manually to verify, that NM is really triggering the problem? Can you run 'cat /proc/kmsg' in another terminal to see if there were some kernel messages before the system freezes? Tambet, what else can he do to debug the issue with NM?
Controlling devices the traditional way (ifup etc) allows the system to boot.
Did you use the device the same way (same kind of connection/configuration)?
(The following tests are made using the Longshine card)
* lsmod reports the following modules after boot: rtl8180, mac80211, eeprom_93cx6 (calling "lsmod | grep rtl") * hwinfo does not make the system freeze * Calling network setup in yast freezes with "Treiberinformationen laden" (trans.: loading driver information), second item. The first item (network device detection) received a check mark.
Michal, how can that be debugged? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=427111
Christian Zoz
https://bugzilla.novell.com/show_bug.cgi?id=427111
User andreas.schallenberg@eurobild.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c6
Andreas Schallenberg
Controlling devices the traditional way (ifup etc) allows the system to boot. Did you use the device the same way (same kind of connection/configuration)?
I was not able to set up a configuration the traditional way. With NetworkManager disabled, the system boots into runlevel 5. As soon as I try to call YaST network setup, the system freezes. To clarify: To enable/disable NetworkManager using YaST, I remove the PCI card from the PC and re-insert it afterwards. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=427111
User zoz@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c7
Christian Zoz
https://bugzilla.novell.com/show_bug.cgi?id=427111
User helmut.schaa@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c8
Helmut Schaa
There were no messages on /proc/kmsg.
You could try to capture the kernel messages using netconsole over the ethernet interface. Have a look at [1] for more information. [1] http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=427111
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=427111
User andreas.schallenberg@eurobild.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c9
Andreas Schallenberg
Andreas, could you please verify if the freeze also happens if you start NetworkManager without having a frontend running (just kill KNetworkManager or nm-applet before starting NM)?
Here is what I did: I used Yast2/network to disable networkmanager start. Reboot, inserted PCI card. Closed KNetworkmanager. Verified, that no network-manager process remains: "ps -Aef | grep -i netw" gives me one dhcpd process only (eth0 is configured and has an IP address via DHCP). Then I start "NetworkManager" as root from a shell. It takes around 2 seconds, then the system is frozen. Netconsole: I was not able to set this up. On the receiving machine (IP 192.168.178.21), I called "netcat -l -p 6666 -u" as root. On the sending machine (the freezing one, IP 192.168.178.33) I entered "modprobe netconsole 6666@192.168.178.33/eth0,6666@192.168.178.21/" I found in a blog that "ifconfig eth0 promisc ; ifconfig eth0 -promisc" should send some messages. But there were none. Even observing "eth0" using wireshark did not list any packages to 192.168.178.21. The firewall was shut down. Obviously I am doing something wrong here. IP 33 is connected via ethernet to a wlan router (the only ethernet port) and IP 21 uses wlan. Therefore I omitted the MAC address setting in the netconsole start, they wouldn't see each other's MAC address anyway. Asking for advice on IRC didn't help either. So if you really require the netconsole messages, it would be nice if there were some ability to chat at IRC at get some advice. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=427111
User helmut.schaa@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c10
Helmut Schaa
Then I start "NetworkManager" as root from a shell. It takes around 2 seconds, then the system is frozen.
Ok, looks to me like the driver oopses either when NM sets the interface up, starts a scan or does any initialization. Could you please try if one of the following commands results in the system freeze too? - ifconfig wlan0 up - iwconfig wlan0 - iwlist wlan0 scan
So if you really require the netconsole messages, it would be nice if there were some ability to chat at IRC at get some advice.
Good, I'll first try to reproduce the issue using a rtl8180. I hope to have access to this card next week. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=427111
User andreas.schallenberg@eurobild.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c11
--- Comment #11 from Andreas Schallenberg
Ok, looks to me like the driver oopses either when NM sets the interface up, starts a scan or does any initialization. Could you please try if one of the following commands results in the system freeze too? - ifconfig wlan0 up - iwconfig wlan0 - iwlist wlan0 scan
I'll provide this info in some hours.
So if you really require the netconsole messages, it would be nice if there were some ability to chat at IRC at get some advice.
Good, I'll first try to reproduce the issue using a rtl8180. I hope to have access to this card next week.
I test with two cards having an rtl8185 chip. I could easily send you one. I just need an address. I also have access to a laptop with a 8180 chip on a PCMCIA card. The card works ok, so I'd expect that you propably won't be able to reproduce it with a 8180 card. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=427111
User andreas.schallenberg@eurobild.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c12
Andreas Schallenberg
(...) Could you please try if one of the following commands results in the system freeze too? - ifconfig wlan0 up
This makes the system freeze.
- iwconfig wlan0 - iwlist wlan0 scan
These don't. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=427111
User helmut.schaa@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c13
--- Comment #13 from Helmut Schaa
(...) Could you please try if one of the following commands results in the system freeze too? - ifconfig wlan0 up
This makes the system freeze.
Thanks. That's a good starting point. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=427111
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=427111
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=427111
Christian Zoz
https://bugzilla.novell.com/show_bug.cgi?id=427111
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=427111
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=427111
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c14
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=427111
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c15
--- Comment #15 from Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=427111
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c16
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=427111
User andreas.schallenberg@eurobild.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c17
--- Comment #17 from Andreas Schallenberg
https://bugzilla.novell.com/show_bug.cgi?id=427111
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c18
Helmut Schaa
Guess what, I am writing this entry on that PC, connected to the internet over WLAN. It worked.
Just for information, which channel are you using (because it seems to me as only connections on channel 1, sometimes 2 and 3, are possible)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=427111
User andreas.schallenberg@eurobild.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c19
Andreas Schallenberg
... Just for information, which channel are you using (because it seems to me as only connections on channel 1, sometimes 2 and 3, are possible)?
My local network is on 2.452 GHz (Channel 9). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=427111
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c20
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=427111
User andreas.schallenberg@eurobild.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c21
Andreas Schallenberg
Andreas, does the connection work reliable?
Yes. The signal strength is pretty weak but it works reliable.
How much attempts do you need to establish the connection?
One. I use the network manager to connect. It is pretty weird, that on one system it does not work at all, another one (your current one) has channel restrictions etc. and a third one (my current one) works without problems. My blind guess is that the kernel module is somewhat picky when it comes to interrupts or similar which are different, depending on the Chipset, BIOS, etc. What board/chipset do you use? If it helps, I could do experiments with a fourth PC, having a ASUS board with NForce-2 chipset. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=427111
User bill@oldmillfarm.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c22
Prexy Prexy
https://bugzilla.novell.com/show_bug.cgi?id=427111
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=427111#c23
Helmut Schaa
participants (1)
-
bugzilla_noreply@novell.com