This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
I actually have hundreds of these in my log on a ThinkPad X61.
[ 3844.989440] Pid: 8106, comm: events/1 Tainted: GW 2.6.27-7-generic #1
[ 3844.989448] [] warn_slowpath+0x65/0x90
[ 3844.989465] [] ? __do_softirq+0xf6/0x120
[ 3844.989478] [] ? mutex_trylock+0x9/0x30
[ 3844.989491] [] e10
Even with the original kernel the problem happened only twice and then
never again.
Let me make a timeline before I get confused (feel free to skip it):
2008-10-31 10:14, I install linux-image-2.6.27-7-generic to 2.6.27-7.15.
2008-10-31 10:28, I reboot into the new kernel
2008-10-31 10:51, I rebo
Hi Marius,
Would you be willing to confirm if this issue exists with the upstream
e1000e driver as well? If so, this is likely something we'll want to
try notifying upstream about. You will have to compile the upstream
kernel, but this is documented at
https://wiki.ubuntu.com/KernelTeam/GitKerne
Suspending the laptop (a Thinkpad T61) is what triggers this spew of
e1000e errors. The laptop sleeps fine, but the errors appear just
before suspend and continue after resume.
rmmod e1000e stops the error flood, but a subsequent modprobe e1000e
hangs burning 100% of one CPU core inside the kerne
Actually, both Ethernet LEDs are on all the time after reboot, and so
far the errors in dmesg haven't recurred.
--
e1000e mutex contention
https://bugs.launchpad.net/bugs/291801
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
