Bug 131229

Summary:	Network interface configuation (e100) locks after some time
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	olaf thormählen <cleaner>
Component:	Kernel	Assignee:	Karsten Keil <karsten.keil>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	i586
OS:	Other
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description olaf thormählen 2005-10-28 09:18:32 UTC

Noticed on a Toshiba Latop Portege M100.

lspci lists the device as "Ethernet controller: Intel Corporation 82801DB PRO/100 VE (MOB) Ethernet Controller (rev 83)". The module is e100.

Symptoms:

After running some time (10min to 30min) the interface locks up configurationwise. Any "ifconfig eth0" will lock up. kill -9 (or any other signal) on the ifconfig process will have no effect. Shutting down the system will lock when reaching the point to unconfigure NW-interfaces. The interface is configured with DHCP, it stays accessible, just the configuration locks up.

Comment 1 Hubert Mantel 2005-10-28 13:05:11 UTC

Which interrupt is being used by the NIC? Is it shared with some other device? Does the problem also happen when you boot in "failsafe" mode?

Comment 2 olaf thormählen 2005-10-28 15:05:12 UTC

irq 11 along with just about everything else (eth0, USB -ehci and uhci-, 1394, ICH4, yenta, ipw2200).

apparently the problem ceases in safe mode. I waited 60 minutes now, but ifconfig still works...

Comment 3 Hubert Mantel 2005-10-28 15:27:36 UTC

Ok, some progress. "Failsafe mode" means several parameters are passed to the kernel. Could you please try to find out which one of them makes the difference? You can do a binary search, so it should not take more than two or three iterations.

Comment 4 Olaf Kirch 2005-11-15 10:30:11 UTC

If ifconfig locks up this may really mean there may have been a kernel
oops.

Please run hwinfo and attach the output to this bug report.
Please also check your system log (/var/log/messages*) for Oops messages.

Comment 5 Karsten Keil 2006-01-24 00:58:46 UTC

No feedback close it for now.