[Bug 291801] Re: e1000e mutex contention

2011-07-18 Thread Brad Figg
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)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/291801

Title:
  e1000e mutex contention

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/291801/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 291801] Re: e1000e mutex contention

2008-11-17 Thread Jeffrey Baker
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]  [] e1000_acquire_swflag_ich8lan+0x47/0xd0 [e1000e]
[ 3844.989515]  [] e1000e_read_phy_reg_igp+0x21/0x70 [e1000e]
[ 3844.989538]  [] e1000e_phy_has_link_generic+0x48/0xe0 [e1000e]
[ 3844.989559]  [] e1000e_check_for_copper_link+0x34/0x90 [e1000e]
[ 3844.989580]  [] e1000_watchdog_task+0x47b/0x650 [e1000e]
[ 3844.989601]  [] ? vmstat_update+0x0/0x30
[ 3844.989616]  [] ? e1000_watchdog_task+0x0/0x650 [e1000e]
[ 3844.989637]  [] run_workqueue+0x95/0x160
[ 3844.989648]  [] ? finish_wait+0x16/0x70
[ 3844.989657]  [] worker_thread+0x88/0xf0
[ 3844.989666]  [] ? autoremove_wake_function+0x0/0x50
[ 3844.989676]  [] ? worker_thread+0x0/0xf0
[ 3844.989685]  [] kthread+0x41/0x80
[ 3844.989694]  [] ? kthread+0x0/0x80
[ 3844.989704]  [] kernel_thread_helper+0x7/0x10
[ 3844.989714]  ===
[ 3844.989719] ---[ end trace 1aa61db9484f7898 ]---
[ 3846.988168] [ cut here ]
[ 3846.988182] WARNING: at 
/build/buildd/linux-2.6.27/drivers/net/e1000e/ich8lan.c:403 
e1000_acquire_swflag_ich8lan+0x47/0xd0 [e1000e]()
[ 3846.988191] e1000e mutex contention. Owned by pid -1
[ 3846.988198] Modules linked in: af_packet i915 drm rfcomm sco bridge stp bnep 
l2cap ppdev ipv6 container sbs sbshc wmi pci_slot acpi_cpufreq 
cpufreq_powersave cpufreq_stats cpufreq_conservative cpufreq_userspace 
cpufreq_ondemand freq_table iptable_filter ip_tables x_tables sbp2 parport_pc 
lp parport btusb bluetooth pcmcia arc4 ecb crypto_blkcipher thinkpad_acpi nvram 
evdev serio_raw psmouse pcspkr iwlagn iwlcore snd_hda_intel rfkill snd_pcm_oss 
snd_mixer_oss sdhci_pci battery sdhci led_class yenta_socket rsrc_nonstatic ac 
mac80211 snd_pcm mmc_core cfg80211 pcmcia_core video output snd_seq_dummy 
snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer 
snd_seq_device snd button intel_agp iTCO_wdt iTCO_vendor_support soundcore 
agpgart shpchp pci_hotplug snd_page_alloc ext3 jbd mbcache sd_mod crc_t10dif 
ata_generic sg pata_acpi ahci ata_piix ohci1394 libata ieee1394 scsi_mod 
ehci_hcd uhci_hcd usbcore dock e1000e thermal processor fan fbcon tileblit font 
bitblit softcursor fuse


** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 291801] Re: e1000e mutex contention

2008-11-05 Thread Marius Gedminas
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 reboot again (with the 'profile' boot option).  The boot 
takes a really long time, then crashes with a kernel panic (blinking capslock 
led).  The panic is not captured in the system log files, and is not visible on 
screen due to usplash.  It's not related to this bug, I think.
2008-10-31 10:53, I reboot again without the 'profile' option.  The boot is 
successful.
2008-10-31 11:17, I suspend.
2008-10-31 14:05, I resume.
2008-10-31 20:04, I suspend.
2008-10-31 20:04, the errors start (5233 repetitions of 'e1000e mutext 
contention' on this day.  The very first messages are rather strange, e.g.

  [e10lo7.290] ea047.0fc1f28]2k_rc8kb+0 /0t0g1x9ce
i[ce3.y4]289h7?.o9r8=dt0rA.004o.u5 2vvoe_slot esonsipher snd_rawi a_core
r

after a while they become readable

2008-10-31 20:33, I resume and notice the errors.
2008-10-31 21:33, I suspend and resume, to see if the errors would go away.
2008-10-31 23:23, I shut down the machine
2008-11-01 09:00, I boot it up, notice both LEDs are on, notice no e1000e 
errors in dmesg
2008-11-01 13:27, I suspend
2008-11-01 13:27, the errors start
2008-11-01 16:11, I resume, the errors continue (349 repetitions of 'e1000e 
mutext contention')
2008-11-01 16:15, I rmmod e1000e to see if it helps (yes)
2008-11-01 16:40, I suspend
2008-11-02 07:45, I resume
2008-11-02 11:34, I suspend
2008-11-02 17:03, I resume
2008-11-02 21:36, I suspend
2008-11-02 21:39, I resume
2008-11-02 21:48, I suspend
2008-11-03 00:02, I resume
2008-11-03 00:09, I suspend
2008-11-03 08:02, I resume, and see a scary message

Nov  3 08:02:04 platonas kernel: [49099.700050] [ cut here 
]
Nov  3 08:02:04 platonas kernel: [49099.700053] WARNING: at 
/build/buildd/linux-2.6.27/arch/x86/kernel/ipi.c:123 
send_IPI_mask_bitmask+0x99/0xb0()
Nov  3 08:02:04 platonas kernel: [49099.700055] Modules linked in: e1000e 
aes_i586 aes_generic ecryptfs isofs loop nls_iso8859_1 nls_cp437 vfat fat 
usb_storage libusual ppp_async crc_ccitt ppp_generic slhc af_packet i915 drm 
rfcomm sco bridge stp bnep l2cap binfmt_misc ppdev ipv6 acpi_cpufreq 
cpufreq_conservative cpufreq_stats cpufreq_ondemand cpufreq_userspace 
cpufreq_powersave freq_table pci_slot sbs sbshc container iptable_filter 
ip_tables x_tables uinput sbp2 parport_pc lp parport btusb bluetooth joydev 
pcmcia snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy 
snd_seq_oss snd_seq_midi snd_rawmidi arc4 ecb crypto_blkcipher 
snd_seq_midi_event snd_seq iwl3945 snd_timer snd_seq_device thinkpad_acpi 
mac80211 rfkill snd led_class sdhci_pci sdhci yenta_socket iTCO_wdt serio_raw 
battery ricoh_mmc mmc_core iTCO_vendor_support nvram cfg80211 psmouse evdev 
video ac bay rsrc_nonstatic pcmcia_core output soundcore button wmi pcspkr 
intel_agp agpgart snd_page_alloc shpchp pci_hotplug ext3 jbd mbcache sr_mod cdro
Nov  3 08:02:04 platonas kernel:  sd_mod crc_t10dif sg pata_acpi ata_piix 
ata_generic ohci1394 libata ieee1394 ehci_hcd scsi_mod uhci_hcd usbcore dock 
thermal processor fan fuse vesafb fbcon tileblit font bitblit softcursor [last 
unloaded: e1000]
Nov  3 08:02:04 platonas kernel: [49099.700137] Pid: 0, comm: swapper Tainted: 
GW 2.6.27-7-generic #1
Nov  3 08:02:04 platonas kernel: [49099.700140]  [] ? printk+0x1d/0x1f
Nov  3 08:02:04 platonas kernel: [49099.700146]  [] 
warn_on_slowpath+0x59/0x90
Nov  3 08:02:04 platonas kernel: [49099.700150]  [] ? 
read_hpet+0x8/0x20
Nov  3 08:02:04 platonas kernel: [49099.700154]  [] ? 
account_scheduler_latency+0xe/0x220
Nov  3 08:02:04 platonas kernel: [49099.700157]  [] ? 
__enqueue_entity+0xd4/0x100
Nov  3 08:02:04 platonas kernel: [49099.700161]  [] ? 
__next_cpu+0x15/0x30
Nov  3 08:02:04 platonas kernel: [49099.700164]  [] ? 
account_scheduler_latency+0xe/0x220
Nov  3 08:02:04 platonas kernel: [49099.700167]  [] ? 
find_busiest_group+0x15d/0x7c0
Nov  3 08:02:04 platonas kernel: [49099.700171]  [] 
send_IPI_mask_bitmask+0x99/0xb0
Nov  3 08:02:04 platonas kernel: [49099.700174]  [] 
native_send_call_func_single_ipi+0x2b/0x30
Nov  3 08:02:04 platonas kernel: [49099.700177]  [] 
generic_exec_single+0x89/0x90
Nov  3 08:02:04 platonas kernel: [49099.700181]  [] 
__smp_call_function_single+0x34/0x60
Nov  3 08:02:04 platonas kernel: [49099.700184]  [] 
hrtick_start_fair+0x10d/0x1a0
Nov  3 08:02:04 platonas kernel: [49099.700187]  [] 
enqueue_task_fair+0x48/0x50
Nov  3 08:02:04 platonas kernel: [49099.700190]  [] 
enqueue_task+0x57/0x70
Nov  3 08:02:04 platonas kernel: [49099.700193]  [] 
activate_task+0x1a/0x30
Nov  3 08:02:04 platonas kernel: [49099.700196]  [] 
try_to_wake_up+0x1dd/0x290
Nov  3 08:02:04 platonas kernel: [49099.700199]  [] ? 
read_hpet+0x8/0x20
Nov  3 08:02:04 platonas kernel: [49099.7002

[Bug 291801] Re: e1000e mutex contention

2008-11-03 Thread Leann Ogasawara
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/GitKernelBuild and should be a simple
process.  In the future we hope to have an upstream kernel package for
you to use, but for now we still have to ask to manually build and test.
Definitely let us know your results.  Thanks.

-- 
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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 291801] Re: e1000e mutex contention

2008-11-01 Thread Marius Gedminas
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 kernel.  The modprobe
process can be stopped with SIGQUIT (C-\).

-- 
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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 291801] Re: e1000e mutex contention

2008-11-01 Thread Marius Gedminas
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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs