Bug 212353

Summary:	T60p networking issues: hang on boot in loopback interface
Product:	Red Hat Enterprise Linux 5	Reporter:	Richard Li <richardl>
Component:	kernel	Assignee:	Andy Gospodarek <agospoda>
Status:	CLOSED NOTABUG	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.0	CC:	linville, peterm, zcerza
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-10-31 17:39:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Richard Li 2006-10-26 14:45:24 UTC

Description of problem:

- On boot, T60p will sometimes hang while bringing up the loopback interface
- If boot is successfully completed, ipw3945 wireless does not function (does
not show any access points)

Version-Release number of selected component (if applicable):

2732 kernel (regular, non-xen)

How reproducible:

loopback interface: frequently
non-working wireless: always

Additional info:

When the network does come up, it says "ipw3945 device eth1 does not seem to be
present delaying initialization"

the ipw3945d daemon is running

lsmod shows the ipw3945

Comment 2 Richard Li 2006-10-26 15:33:52 UTC

I can boot successfully with the Xen kernel (2732) although ipw3945 still does
not work. (Oddly enough, I was able to get it working at one point a few days
ago, but then I did a yum update from a tree yesterday and now things are horked.)

Comment 3 Zack Cerza 2006-10-26 16:54:15 UTC

The wireless problem was a false alarm; Richard left his RF kill switch on. :)

Comment 4 Richard Li 2006-10-26 18:08:58 UTC

Change to NEEDINFO since Zack and I are no longer able to reproduce this problem.

Comment 5 Andy Gospodarek 2006-10-31 17:01:13 UTC

So can we close this one then?