[Bug 106869] Re: e1000 locks up under load in Feisty.
*This is an automated response* This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New". ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- e1000 locks up under load in Feisty. https://bugs.launchpad.net/bugs/106869 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 106869] Re: e1000 locks up under load in Feisty.
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test: 1) If you are comfortable installing packages on your own, the linux- image-2.6.27-* package is currently available for you to install and test. --or-- 2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD. Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback. ** Tags added: cft-2.6.27 -- e1000 locks up under load in Feisty. https://bugs.launchpad.net/bugs/106869 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 106869] Re: e1000 locks up under load in Feisty.
** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: Kernel Bugs (kernel-bugs) => (unassigned) -- e1000 locks up under load in Feisty. https://bugs.launchpad.net/bugs/106869 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 106869] Re: e1000 locks up under load in Feisty.
Bug may already be fixed in later versions of kernel but need to confirm. See comments above. ** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: (unassigned) => Lavrock (linuxkernels) ** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: Lavrock (linuxkernels) => Tahir Rauf (linux-kernel-worm) ** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: Tahir Rauf (linux-kernel-worm) => Kernel Bugs (kernel-bugs) -- e1000 locks up under load in Feisty. https://bugs.launchpad.net/bugs/106869 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 106869] Re: e1000 locks up under load in Feisty.
You guys still running Feisty? Still seeing the problem on whichever version you are running? ** Changed in: linux-source-2.6.20 (Ubuntu) Status: New => Confirmed -- e1000 locks up under load in Feisty. https://bugs.launchpad.net/bugs/106869 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 106869] Re: e1000 locks up under load in Feisty.
7.10 64-bit does not exhibit this behaviour. 32-bit Linux does, but 64-bit doesn't (on my machine). -- e1000 locks up under load in Feisty. https://bugs.launchpad.net/bugs/106869 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 106869] Re: e1000 locks up under load in Feisty.
Having the same problem with a dell workstation purchased in april of this year. its core 2 duo E6600 system. -- e1000 locks up under load in Feisty. https://bugs.launchpad.net/bugs/106869 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106869] Re: e1000 locks up under load in Feisty.
I have a stronger idea of where this bug lurks now. I upgraded another e1000 equipped machine, and it exhibited similar symptoms. Affected: SMP Linux 2.6.20-15, 2.6.20-16 (Ubuntu) SMP Linux 2.6.20.7 (kernel.org) SMP Linux 2.6.22.1 (kernel.org) Unaffected: SMP Linux 2.6.17-11 (Ubuntu) UMP Linux02.6.22.1 (kernel.org) Hardware affected: AMD X2 3600+, 3800+, 4200+, etc (1.9-2.5Ghz range I can test) with both cores enabled and kernel >= 2.6.20-15 + e1000 (included the latest driver from http://sourceforge.net/projects/e1000 , which was 7.6.5). Hardware unaffected The exact same hardware with the dual-core mode disabled in the BIOS. I can easily sling around bits anywhere from 300Mbps to 600Mbps with jumbo frames, rock solid. So... what's broken in SMP mode? What broke between 2.6.17-11 and 2.6.20-15? I don't feel like wading through kernel diffs alone. -- e1000 locks up under load in Feisty. https://bugs.launchpad.net/bugs/106869 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106869] Re: e1000 locks up under load in Feisty.
I've tried a few things. I did a blacklist ipv6, which seems to make it harder to trigger the condition with MythTV traffic (I was able to successfully watch a number of shows without the client locking up), but this didn't stop the case where any NFS transfers to my Slackware server locked up the client. On a lark, I swapped the network card from the new e1000 to an old e100 card I had in a drawer. It locks up identically under NFS load: [ 341.152000] NETDEV WATCHDOG: eth0: transmit timed out [ 341.172000] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex [ 346.168000] NETDEV WATCHDOG: eth0: transmit timed out [ 346.188000] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex I suspect a deeper bug in the kernel, perhaps relating to interrupts, or the networking parts common to both code paths (where the skbs are transmitted). -- e1000 locks up under load in Feisty. https://bugs.launchpad.net/bugs/106869 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106869] Re: e1000 locks up under load in Feisty.
Here is a transcription of the lockup from the perspective of MythTV! 2007-04-27 00:11:47.138 Using runtime prefix = /usr 2007-04-27 00:11:47.144 DPMS is active. 2007-04-27 00:11:47.497 New DB connection, total: 1 2007-04-27 00:11:47.572 Connected to database 'mythconverg' at host: apollo 2007-04-27 00:11:47.600 Total desktop dim: 1920x1200, with 1 screen[s]. 2007-04-27 00:11:47.630 Using screen 0, 1920x1200 at 0,0 2007-04-27 00:11:47.652 Current Schema Version: 1160 2007-04-27 00:11:47.652 mythfrontend version: 0.20.20060828-3 www.mythtv.org 2007-04-27 00:11:47.652 Enabled verbose msgs: important general 2007-04-27 00:11:49.193 Total desktop dim: 1920x1200, with 1 screen[s]. 2007-04-27 00:11:49.196 Using screen 0, 1920x1200 at 0,0 2007-04-27 00:11:49.200 Switching to square mode (Titivillus) 2007-04-27 00:11:49.289 Using the Qt painter mythtv: could not connect to socket mythtv: No such file or directory lirc_init failed for mythtv, see preceding messages 2007-04-27 00:11:51.025 Joystick disabled. 2007-04-27 00:11:51.198 Loading from: /usr/share/mythtv/themes/default/base.xml 2007-04-27 00:11:52.080 Registering Internal as a media playback plugin. 2007-04-27 00:12:29.375 XMLParse::LoadTheme using /usr/share/mythtv/themes/Titivillus/ui.xml 2007-04-27 00:12:32.205 Connecting to backend server: 192.168.0.3:6543 (try 1 of 5) 2007-04-27 00:12:32.207 Using protocol version 31 2007-04-27 00:12:43.744 New DB connection, total: 2 2007-04-27 00:12:43.826 Connected to database 'mythconverg' at host: apollo 2007-04-27 00:12:43.902 TV: Attempting to change from None to WatchingPreRecorded 2007-04-27 00:12:44.013 DPMS Deactivated 0: start_time: 0.036 duration: 165.324 1: start_time: 0.026 duration: 165.307 stream: start_time: 0.289 duration: 1837.046 bitrate=4896 kb/s 2007-04-27 00:12:44.440 AFD: Opened codec 0x8523800, id(MPEG2VIDEO) type(Video) 2007-04-27 00:12:44.481 AFD: Opened codec 0x8461790, id(MP2) type(Audio) 2007-04-27 00:12:44.505 Opening OSS audio device '/dev/dsp'. 2007-04-27 00:12:44.749 VideoOutputXv: XvMCTex: Init failed 2007-04-27 00:12:44.761 VideoOutputXv: XVideo Adaptor Name: 'NV17 Video Texture' X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 140 Minor opcode: 14 Resource id: 0x290 2007-04-27 00:12:47.695 TV: Changing from None to WatchingPreRecorded 2007-04-27 00:12:47.696 New DB connection, total: 3 2007-04-27 00:12:47.716 Realtime priority would require SUID as root. 2007-04-27 00:12:47.741 Connected to database 'mythconverg' at host: apollo 2007-04-27 00:12:47.835 Video timing method: USleep with busy wait 2007-04-27 00:12:49.758 AO: Using time stretch 1.5 2007-04-27 00:20:17.793 NVP: prebuffering pause 2007-04-27 00:20:18.180 RingBuf(myth://192.168.0.3:6543/1032_2007042622.mpg): Waited 1.0 seconds for data to become available... 2007-04-27 00:20:18.712 NVP: Prebuffer wait timed out 10 times. 2007-04-27 00:20:19.204 RingBuf(myth://192.168.0.3:6543/1032_2007042622.mpg): Waited 2.0 seconds for data to become available... 2007-04-27 00:20:19.632 NVP: Prebuffer wait timed out 10 times. 2007-04-27 00:20:20.552 NVP: Prebuffer wait timed out 10 times. 2007-04-27 00:20:21.252 RingBuf(myth://192.168.0.3:6543/1032_2007042622.mpg): Waited 4.0 seconds for data to become available... 2007-04-27 00:20:21.472 NVP: Prebuffer wait timed out 10 times. 2007-04-27 00:20:22.392 NVP: Prebuffer wait timed out 10 times. 2007-04-27 00:20:23.312 NVP: Prebuffer wait timed out 10 times. 2007-04-27 00:20:24.232 NVP: Prebuffer wait timed out 10 times. 2007-04-27 00:20:25.152 NVP: Prebuffer wait timed out 10 times. 2007-04-27 00:20:25.348 RingBuf(myth://192.168.0.3:6543/1032_2007042622.mpg): Waited 8.0 seconds for data to become available... 2007-04-27 00:20:26.073 NVP: Prebuffer wait timed out 10 times. 2007-04-27 00:20:26.993 NVP: Prebuffer wait timed out 10 times. 2007-04-27 00:20:27.917 NVP: Prebuffer wait timed out 10 times. 2007-04-27 00:20:28.837 NVP: Prebuffer wait timed out 10 times. 2007-04-27 00:20:29.757 NVP: Prebuffer wait timed out 10 times. 2007-04-27 00:20:30.677 NVP: Prebuffer wait timed out 10 times. 2007-04-27 00:20:31.494 MythSocket(a4b01630:18): readStringList: Error, timeout (quick). 2007-04-27 00:20:31.494 RemoteFile::Read(): No response from control socket. 2007-04-27 00:20:31.494 RingBuf(myth://192.168.0.3:6543/1032_2007042622.mpg) Error: RingBuffer::safe_read(RemoteFile* ...): read failed The network is down... naturally. This was after 9 days of uptime (where I didn't use NFS or anything beyond simple email/web browsing, which rarely triggers the bug). I clicked logout. 20 minutes later, I manually killed X. It seems that the Kubuntu desktop gets fairly broken when network goes away, and there are some NFS mounts setup. -- e1000 locks up under load in Feisty. https://bugs.launchpad.net/bugs/106869 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs maili
[Bug 106869] Re: e1000 locks up under load in Feisty.
More interesting bits: lots of network traffic can cause the system to just be wonky, without actually killing the link. Here is a summary of my experiences - Transfering big files over NFS will cause the NIC to no longer work. - Streaming video (Mythfrontend) will experience problems where the keyboard appears to get modifier keys (shift, etc) stuck on, and the finally cause the NIC to no longer work after a few more minutes. - Minor traffic (~20k/s of torrents) will cause the modifier keys to appear stuck on periodically. It seems that bidirectional traffic makes it worse than uni-directional, and that higher rates of transfer lead to more rapid failures. -- e1000 locks up under load in Feisty. https://bugs.launchpad.net/bugs/106869 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
