Bug 115366

Summary:	Laptop hangs on starting yast lan
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Will Stephenson <wstephenson>
Component:	Kernel	Assignee:	Hubert Mantel <mantel>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	aj
Version:	Beta 4 Plus
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:	115132
Bug Blocks:

Description Will Stephenson 2005-09-06 08:51:38 UTC

Since upgrading from beta3 with beta4 kernel to beta4plus, my hp centrino 
laptop  
1. fails to get an IP address with DHCP at bootup  
2. locks up hard at 100% cpu when running ´yast lan´ to see what the problem 
is. 
 
At the moment its network config is inconsistent, I changed from a fixed 
ip/default route environment to DHCP here, and changed IP address to DHCP but 
left the static default route in place. 
 
Looking at /var/log/messages and /var/log/warn there are no logs from before 
the hang.  On bootup there is a kernel message - general protection fault: 
0000 [#1], after loading the slamr modem module, and there are numerous 
warnings from ACPI about devices not being power mananageable, including the 
8139cp ethernet interface.

Comment 1 Dr. Werner Fink 2005-09-06 10:45:50 UTC

Q: Do you use a ipw2200 wireless ethernet card? See bug 113634.
Beside this the slamr module should not chrash the kernel,
maybe this module should be blacklisted.

Comment 2 Andreas Jaeger 2005-09-06 11:28:01 UTC

Marian?

Comment 3 Michael Gross 2005-09-06 11:48:06 UTC

Reducing this to `critical'. Problems with specific notebooks are encountered
only by few persons.

Comment 4 Will Stephenson 2005-09-06 11:54:52 UTC

It's ipw2100.  Both network interfaces have worked without a problem since 
suse 9.1.

Comment 5 Thomas Renninger 2005-09-06 16:32:35 UTC

Does your processor support C3?
cat /proc/acpi/processor/*/power

If yes try to load the processor module with option max_cstate=2.
(options processor max_cstate=2  in /etc/modprobe.conf)

(Or try to not load processor module at all by not starting powersaved service -
chkconfig powersaved off).

I heard about DMA transfer issues that freeze machines with IPW drivers and C3
processor sleep state triggering -> symptom is normally total freeze, but maybe
it's that..., just an idea...

Comment 6 Joachim Gleissner 2005-09-06 17:15:15 UTC

Could you try whether the ipw2100 module attachted to bug 115252 fixes this?

Comment 7 Marian Jancar 2005-09-07 09:36:23 UTC

The fault in slamr was caused by recent change to pci_match_device() and is
fixed allready (see bug #115132).

Comment 8 Hubert Mantel 2005-09-07 14:08:43 UTC

Could this one be related to eg. #115372 ? At least several people reported
strange segmentation faults at various places during booting.

Comment 9 Andreas Jaeger 2005-09-08 13:10:24 UTC

Will, could you check this with RC1, please?

Comment 10 Will Stephenson 2005-09-08 16:00:52 UTC

No hang with RC1, and beta4plus worked with the replacement ipw2100 module, 
although I do not have WPA. 

*** This bug has been marked as a duplicate of 115252 ***