Bug 245107

Summary:	Reloading e1000 module causes hibernate to fail
Product:	[Fedora] Fedora	Reporter:	Bryan O'Sullivan <bos>
Component:	kernel	Assignee:	Dave Jones <davej>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	high
Version:	7	CC:	chris.brown, pfrields
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-01-09 15:00:08 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 Bryan O'Sullivan 2007-06-21 05:42:46 UTC

I'm using a Thinkpad X60.

The workaround for bug 236956 (failure to detect carrier) is to rmmod and
modprobe the e1000 driver.  If I do this, the next time I try to suspend to disk
(aka "hibernate"), all network-related userspace programs (NetworkManager, etc)
go into an unkillable state, suspend fails because these processes can't be
frozen, and any further attempt to load or unload kernel modules hangs.

Will be happy to provide more info.

Comment 1 Chuck Ebbert 2007-06-21 19:58:38 UTC

Can you get output from alt-sysrq-t when it hangs?

(or just do "echo "t" >/proc/sysrq-trigger)

Comment 2 Christopher Brown 2007-09-17 11:41:56 UTC

Hello,

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?

If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.

Cheers
Chris

Comment 3 Christopher Brown 2008-01-09 15:00:08 UTC

As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.