Bug 143261

Summary:	YaST network card configuration causes lots of kernel messages/crash
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Stefan Nordhausen <nordhaus>
Component:	YaST2	Assignee:	Joachim Gleissner <joachim.gleissner>
Status:	VERIFIED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None	CC:	behlert
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2logs output of "hwinfo --wlan" output of "lsmod" output of "tail -n 200 /var/log/messages"

Description Stefan Nordhausen 2006-01-14 11:57:55 UTC

When I start YaST and go to Network Devices->Network Card, dmesg shows lots of messages like this:

CCMP: received packet without ExtIV flag from 00:90:4b:83:27:d0
printk: 179 messages suppressed.
CCMP: received packet without ExtIV flag from 00:90:4b:83:27:d0
printk: 399 messages suppressed.
CCMP: received packet without ExtIV flag from 00:90:4b:83:27:d0
printk: 164 messages suppressed.

I noticed this because one time it even locked the machine completely (no CTRL+ALT+DEL or CTRL+ALT+BACKSPACE). The lockup occured after clicking on the icon in YaST while the module was loading. When it crashed the loading procedure had only produced one line of output.

The messages are triggered by starting the YaST module and don't go away when I leave it. However, "ifdown eth1" stops them. Eth1 is my WLAN card that gets listed as "Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)" by lspci, it is plugged into an Acer Travelmate 800. I'm using Suse's own kernel and all available patches have been applied.

Comment 1 Stefan Nordhausen 2006-01-14 11:58:55 UTC

Created attachment 63352 [details]
y2logs

Comment 2 Michael Gross 2006-01-16 13:52:10 UTC

Hi Stefan,

please attach about 200 lines of your syslog, the output of `hwinfo --wlan' as well as the output of `lsmod' once the trouble-causing module was loaded. What exactly did you do/configure to provoke this problem?

Comment 3 Stefan Nordhausen 2006-01-17 20:36:00 UTC

It locked the machine another time while trying to create the requested files. Even Capslock didn't work. It happened while the progress bar still showed 0% and said it was detecting devices.

After that it didn't crash, but I found that I loose connectivity when running the YaST module. I can restore that, too, by "ifdown eth1; ifup eth1". That is probably the reason why I didn't detect that last time.

I do not know exactly what caused this problem, I just stumbled over it when I started the YaST module. I had not used it for quite a long time (my network is working fine, no need for changes) so I do not know if it was caused by an update/config change/whatever.

Comment 4 Stefan Nordhausen 2006-01-17 20:36:57 UTC

Created attachment 63680 [details]
output of "hwinfo --wlan"

Comment 5 Stefan Nordhausen 2006-01-17 20:37:44 UTC

Created attachment 63681 [details]
output of "lsmod"

Comment 6 Stefan Nordhausen 2006-01-17 20:38:27 UTC

Created attachment 63682 [details]
output of "tail -n 200 /var/log/messages"

Comment 7 Martin Lasarsch 2006-01-18 11:30:47 UTC

please also attach /var/log/YaST/y2log

assigned to maintainer, put jg into cc:, maybe he knows more about that error.

Comment 8 Stefan Nordhausen 2006-02-02 22:38:23 UTC

y2log already attached, see comment #1

Comment 9 Martin Vidner 2006-02-03 09:21:09 UTC

Sorry for the delay. Yast loads the driver modules on startup. So I think it is a driver problem.

Comment 10 Joachim Gleissner 2006-03-10 16:25:40 UTC

Yes, it's most probably a driver problem.

Comment 11 Stefan Behlert 2007-01-19 12:42:22 UTC

Is this bug still present in 10.2?

Comment 12 Joachim Gleissner 2007-01-19 13:04:28 UTC

I don't know, I did not encounter it. Stefan, in case you're running a later SUSE version now, do you still see this bug?

Comment 13 Stefan Behlert 2007-02-16 11:42:58 UTC

Please reopen when you see this again. Thanks.