Created attachment 25086 [details] dmesg of kernel 2.6.31 Hi, A few hours after starting a server I have these error messages in the e1000 driver. I have these messages for kernel versions 2.6.31 and 2.6.32. Regards. For kernel 2.6.31, boot at 09:47 : Feb 15 10:39:49 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Feb 15 10:39:49 hastur kernel: Tx Queue <0> Feb 15 10:39:49 hastur kernel: TDH <74> Feb 15 10:39:49 hastur kernel: TDT <ce> Feb 15 10:39:49 hastur kernel: next_to_use <ce> Feb 15 10:39:49 hastur kernel: next_to_clean <6c> Feb 15 10:39:49 hastur kernel: buffer_info[next_to_clean] Feb 15 10:39:49 hastur kernel: time_stamp <acd13> Feb 15 10:39:49 hastur kernel: next_to_watch <75> Feb 15 10:39:49 hastur kernel: jiffies <ace9a> Feb 15 10:39:49 hastur kernel: next_to_watch.status <0> Feb 15 10:39:51 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Feb 15 10:39:51 hastur kernel: Tx Queue <0> Feb 15 10:39:51 hastur kernel: TDH <74> Feb 15 10:39:51 hastur kernel: TDT <ce> Feb 15 10:39:51 hastur kernel: next_to_use <ce> Feb 15 10:39:51 hastur kernel: next_to_clean <6c> Feb 15 10:39:51 hastur kernel: buffer_info[next_to_clean] Feb 15 10:39:51 hastur kernel: time_stamp <acd13> Feb 15 10:39:51 hastur kernel: next_to_watch <75> Feb 15 10:39:51 hastur kernel: jiffies <ad08e> Feb 15 10:39:51 hastur kernel: next_to_watch.status <0> Feb 15 10:39:53 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Feb 15 10:39:53 hastur kernel: Tx Queue <0> Feb 15 10:39:53 hastur kernel: TDH <74> Feb 15 10:39:53 hastur kernel: TDT <ce> Feb 15 10:39:53 hastur kernel: next_to_use <ce> Feb 15 10:39:53 hastur kernel: next_to_clean <6c> Feb 15 10:39:53 hastur kernel: buffer_info[next_to_clean] Feb 15 10:39:53 hastur kernel: time_stamp <acd13> Feb 15 10:39:53 hastur kernel: next_to_watch <75> Feb 15 10:39:53 hastur kernel: jiffies <ad282> Feb 15 10:39:53 hastur kernel: next_to_watch.status <0> Feb 15 10:39:54 hastur kernel: ------------[ cut here ]------------ Feb 15 10:39:54 hastur kernel: WARNING: at net/sched/sch_generic.c:246 dev_watchdog+0xcf/0x152() Feb 15 10:39:54 hastur kernel: Hardware name: To Be Filled By O.E.M. Feb 15 10:39:54 hastur kernel: NETDEV WATCHDOG: eth0 (e1000): transmit queue 0 timed out Feb 15 10:39:54 hastur kernel: Modules linked in: Feb 15 10:39:54 hastur kernel: Pid: 0, comm: swapper Not tainted 2.6.31 #1 Feb 15 10:39:54 hastur kernel: Call Trace: Feb 15 10:39:54 hastur kernel: [<c101a987>] ? warn_slowpath_common+0x5e/0x8a Feb 15 10:39:54 hastur kernel: [<c101a9e5>] ? warn_slowpath_fmt+0x26/0x2a Feb 15 10:39:54 hastur kernel: [<c11dae4f>] ? dev_watchdog+0xcf/0x152 Feb 15 10:39:54 hastur kernel: [<c10171db>] ? __wake_up_common+0x2d/0x52 Feb 15 10:39:54 hastur kernel: [<c11dad80>] ? dev_watchdog+0x0/0x152 Feb 15 10:39:54 hastur kernel: [<c1020ddf>] ? run_timer_softirq+0x101/0x145 Feb 15 10:39:54 hastur kernel: [<c101e072>] ? __do_softirq+0x5d/0xc7 Feb 15 10:39:54 hastur kernel: [<c101e015>] ? __do_softirq+0x0/0xc7 Feb 15 10:39:54 hastur kernel: <IRQ> [<c101de66>] ? irq_exit+0x25/0x4e Feb 15 10:39:54 hastur kernel: [<c100eb32>] ? smp_apic_timer_interrupt+0x60/0x68 Feb 15 10:39:54 hastur kernel: [<c1002d8a>] ? apic_timer_interrupt+0x2a/0x30 Feb 15 10:39:54 hastur kernel: [<c1007141>] ? default_idle+0x25/0x38 Feb 15 10:39:54 hastur kernel: [<c1001ac6>] ? cpu_idle+0x23/0x3d Feb 15 10:39:54 hastur kernel: [<c13615c3>] ? start_kernel+0x211/0x214 Feb 15 10:39:54 hastur kernel: ---[ end trace 3269f164dd9f2bed ]--- Feb 15 10:39:57 hastur kernel: e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Feb 15 10:39:58 hastur kernel: e1000: eth0 NIC Link is Down Feb 15 10:40:00 hastur kernel: e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX For kernel 2.6.32, boot at 19:57 : Feb 15 22:10:46 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Feb 15 22:10:46 hastur kernel: Tx Queue <0> Feb 15 22:10:46 hastur kernel: TDH <7b> Feb 15 22:10:46 hastur kernel: TDT <8c> Feb 15 22:10:46 hastur kernel: next_to_use <8c> Feb 15 22:10:46 hastur kernel: next_to_clean <73> Feb 15 22:10:46 hastur kernel: buffer_info[next_to_clean] Feb 15 22:10:46 hastur kernel: time_stamp <1d8441> Feb 15 22:10:46 hastur kernel: next_to_watch <7c> Feb 15 22:10:46 hastur kernel: jiffies <1d859e> Feb 15 22:10:46 hastur kernel: next_to_watch.status <0> Feb 15 22:10:48 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Feb 15 22:10:48 hastur kernel: Tx Queue <0> Feb 15 22:10:48 hastur kernel: TDH <7b> Feb 15 22:10:48 hastur kernel: TDT <8c> Feb 15 22:10:48 hastur kernel: next_to_use <8c> Feb 15 22:10:48 hastur kernel: next_to_clean <73> Feb 15 22:10:48 hastur kernel: buffer_info[next_to_clean] Feb 15 22:10:48 hastur kernel: time_stamp <1d8441> Feb 15 22:10:48 hastur kernel: next_to_watch <7c> Feb 15 22:10:48 hastur kernel: jiffies <1d8792> Feb 15 22:10:48 hastur kernel: next_to_watch.status <0> Feb 15 22:10:50 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Feb 15 22:10:50 hastur kernel: Tx Queue <0> Feb 15 22:10:50 hastur kernel: TDH <7b> Feb 15 22:10:50 hastur kernel: TDT <8c> Feb 15 22:10:50 hastur kernel: next_to_use <8c> Feb 15 22:10:50 hastur kernel: next_to_clean <73> Feb 15 22:10:50 hastur kernel: buffer_info[next_to_clean] Feb 15 22:10:50 hastur kernel: time_stamp <1d8441> Feb 15 22:10:50 hastur kernel: next_to_watch <7c> Feb 15 22:10:50 hastur kernel: jiffies <1d8986> Feb 15 22:10:50 hastur kernel: next_to_watch.status <0> Feb 15 22:10:52 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Feb 15 22:10:52 hastur kernel: Tx Queue <0> Feb 15 22:10:52 hastur kernel: TDH <7b> Feb 15 22:10:52 hastur kernel: TDT <8c> Feb 15 22:10:52 hastur kernel: next_to_use <8c> Feb 15 22:10:52 hastur kernel: next_to_clean <73> Feb 15 22:10:52 hastur kernel: buffer_info[next_to_clean] Feb 15 22:10:52 hastur kernel: time_stamp <1d8441> Feb 15 22:10:52 hastur kernel: next_to_watch <7c> Feb 15 22:10:52 hastur kernel: jiffies <1d8b7a> Feb 15 22:10:52 hastur kernel: next_to_watch.status <0> Feb 15 22:10:54 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Feb 15 22:10:54 hastur kernel: Tx Queue <0> Feb 15 22:10:54 hastur kernel: TDH <7b> Feb 15 22:10:54 hastur kernel: TDT <8c> Feb 15 22:10:54 hastur kernel: next_to_use <8c> Feb 15 22:10:54 hastur kernel: next_to_clean <73> Feb 15 22:10:54 hastur kernel: buffer_info[next_to_clean] Feb 15 22:10:54 hastur kernel: time_stamp <1d8441> Feb 15 22:10:54 hastur kernel: next_to_watch <7c> Feb 15 22:10:54 hastur kernel: jiffies <1d8d6e> Feb 15 22:10:54 hastur kernel: next_to_watch.status <0> Feb 15 22:10:55 hastur kernel: ------------[ cut here ]------------ Feb 15 22:10:55 hastur kernel: WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0xcf/0x152() Feb 15 22:10:55 hastur kernel: Hardware name: To Be Filled By O.E.M. Feb 15 22:10:55 hastur kernel: NETDEV WATCHDOG: eth0 (e1000): transmit queue 0 timed out Feb 15 22:10:55 hastur kernel: Modules linked in: Feb 15 22:10:55 hastur kernel: Pid: 0, comm: swapper Not tainted 2.6.32 #1 Feb 15 22:10:55 hastur kernel: Call Trace: Feb 15 22:10:55 hastur kernel: [<c101b013>] ? warn_slowpath_common+0x5e/0x8a Feb 15 22:10:55 hastur kernel: [<c101b071>] ? warn_slowpath_fmt+0x26/0x2a Feb 15 22:10:55 hastur kernel: [<c11dd1d1>] ? dev_watchdog+0xcf/0x152 Feb 15 22:10:55 hastur kernel: [<c10177f5>] ? __wake_up_common+0x2d/0x52 Feb 15 22:10:55 hastur kernel: [<c1025cf6>] ? delayed_work_timer_fn+0x0/0xe Feb 15 22:10:55 hastur kernel: [<c1017829>] ? __wake_up+0xf/0x15 Feb 15 22:10:55 hastur kernel: [<c1025cf0>] ? __queue_work+0x43/0x49 Feb 15 22:10:55 hastur kernel: [<c11dd102>] ? dev_watchdog+0x0/0x152 Feb 15 22:10:55 hastur kernel: [<c1021731>] ? run_timer_softirq+0x101/0x145 Feb 15 22:10:55 hastur kernel: [<c101e8b3>] ? __do_softirq+0x5d/0xc6 Feb 15 22:10:55 hastur kernel: [<c101e856>] ? __do_softirq+0x0/0xc6 Feb 15 22:10:55 hastur kernel: <IRQ> [<c101e69d>] ? irq_exit+0x25/0x53 Feb 15 22:10:55 hastur kernel: [<c100eba9>] ? smp_apic_timer_interrupt+0x60/0x68 Feb 15 22:10:55 hastur kernel: [<c1002e0a>] ? apic_timer_interrupt+0x2a/0x30 Feb 15 22:10:55 hastur kernel: [<c1007119>] ? default_idle+0x25/0x38 Feb 15 22:10:55 hastur kernel: [<c1001ad4>] ? cpu_idle+0x23/0x3f Feb 15 22:10:55 hastur kernel: [<c13685ef>] ? start_kernel+0x211/0x214 Feb 15 22:10:55 hastur kernel: ---[ end trace 2a3d8f7abc7b6ece ]--- Feb 15 22:10:58 hastur kernel: e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Created attachment 25087 [details] dmesg of kernel 2.6.32
please include lspci -vvv ethtool -e kernel .config
Created attachment 25184 [details] lspci -vvv output
Created attachment 25185 [details] ethtool -e output
Created attachment 25186 [details] config file for kernel 2.6.31
Created attachment 25187 [details] config file for kernel 2.6.32
Hi, I have the same problem with the kernel 2.6.33. Regards. Feb 25 22:18:32 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Feb 25 22:18:32 hastur kernel: Tx Queue <0> Feb 25 22:18:32 hastur kernel: TDH <a9> Feb 25 22:18:32 hastur kernel: TDT <dc> Feb 25 22:18:32 hastur kernel: next_to_use <dc> Feb 25 22:18:32 hastur kernel: next_to_clean <a1> Feb 25 22:18:32 hastur kernel: buffer_info[next_to_clean] Feb 25 22:18:32 hastur kernel: time_stamp <80825e> Feb 25 22:18:32 hastur kernel: next_to_watch <ac> Feb 25 22:18:32 hastur kernel: jiffies <808464> Feb 25 22:18:32 hastur kernel: next_to_watch.status <0> Feb 25 22:18:34 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Feb 25 22:18:34 hastur kernel: Tx Queue <0> Feb 25 22:18:34 hastur kernel: TDH <a9> Feb 25 22:18:34 hastur kernel: TDT <dc> Feb 25 22:18:34 hastur kernel: next_to_use <dc> Feb 25 22:18:34 hastur kernel: next_to_clean <a1> Feb 25 22:18:34 hastur kernel: buffer_info[next_to_clean] Feb 25 22:18:34 hastur kernel: time_stamp <80825e> Feb 25 22:18:34 hastur kernel: next_to_watch <ac> Feb 25 22:18:34 hastur kernel: jiffies <808658> Feb 25 22:18:34 hastur kernel: next_to_watch.status <0> Feb 25 22:18:36 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Feb 25 22:18:36 hastur kernel: Tx Queue <0> Feb 25 22:18:36 hastur kernel: TDH <a9> Feb 25 22:18:36 hastur kernel: TDT <dc> Feb 25 22:18:36 hastur kernel: next_to_use <dc> Feb 25 22:18:36 hastur kernel: next_to_clean <a1> Feb 25 22:18:36 hastur kernel: buffer_info[next_to_clean] Feb 25 22:18:36 hastur kernel: time_stamp <80825e> Feb 25 22:18:36 hastur kernel: next_to_watch <ac> Feb 25 22:18:36 hastur kernel: jiffies <80884c> Feb 25 22:18:36 hastur kernel: next_to_watch.status <0> Feb 25 22:18:38 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Feb 25 22:18:38 hastur kernel: Tx Queue <0> Feb 25 22:18:38 hastur kernel: TDH <a9> Feb 25 22:18:38 hastur kernel: TDT <dc> Feb 25 22:18:38 hastur kernel: next_to_use <dc> Feb 25 22:18:38 hastur kernel: next_to_clean <a1> Feb 25 22:18:38 hastur kernel: buffer_info[next_to_clean] Feb 25 22:18:38 hastur kernel: time_stamp <80825e> Feb 25 22:18:38 hastur kernel: next_to_watch <ac> Feb 25 22:18:38 hastur kernel: jiffies <808a40> Feb 25 22:18:38 hastur kernel: next_to_watch.status <0> Feb 25 22:18:39 hastur kernel: ------------[ cut here ]------------ Feb 25 22:18:39 hastur kernel: WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0xcf/0x14f() Feb 25 22:18:39 hastur kernel: Hardware name: To Be Filled By O.E.M. Feb 25 22:18:39 hastur kernel: NETDEV WATCHDOG: eth0 (e1000): transmit queue 0 timed out Feb 25 22:18:39 hastur kernel: Modules linked in: Feb 25 22:18:39 hastur kernel: Pid: 0, comm: swapper Not tainted 2.6.33 #1 Feb 25 22:18:39 hastur kernel: Call Trace: Feb 25 22:18:39 hastur kernel: [<c101cd89>] ? warn_slowpath_common+0x5e/0x8a Feb 25 22:18:39 hastur kernel: [<c101cde7>] ? warn_slowpath_fmt+0x26/0x2a Feb 25 22:18:39 hastur kernel: [<c11e6d96>] ? dev_watchdog+0xcf/0x14f Feb 25 22:18:39 hastur kernel: [<c11e0030>] ? __dst_free+0x72/0x85 Feb 25 22:18:39 hastur kernel: [<c11d3306>] ? sk_reset_timer+0xc/0x18 Feb 25 22:18:39 hastur kernel: [<c12034d3>] ? tcp_retransmit_timer+0x444/0x4b6 Feb 25 22:18:39 hastur kernel: [<c1203867>] ? tcp_write_timer+0x0/0x161 Feb 25 22:18:39 hastur kernel: [<c11e6cc7>] ? dev_watchdog+0x0/0x14f Feb 25 22:18:39 hastur kernel: [<c1023bdd>] ? run_timer_softirq+0x101/0x145 Feb 25 22:18:39 hastur kernel: [<c1020784>] ? __do_softirq+0x5d/0xc5 Feb 25 22:18:39 hastur kernel: [<c1020727>] ? __do_softirq+0x0/0xc5 Feb 25 22:18:39 hastur kernel: <IRQ> [<c102057a>] ? irq_exit+0x25/0x53 Feb 25 22:18:39 hastur kernel: [<c101074b>] ? smp_apic_timer_interrupt+0x60/0x68 Feb 25 22:18:39 hastur kernel: [<c123a422>] ? apic_timer_interrupt+0x2a/0x30 Feb 25 22:18:39 hastur kernel: [<c10071a8>] ? default_idle+0x25/0x38 Feb 25 22:18:39 hastur kernel: [<c1001976>] ? cpu_idle+0x23/0x3d Feb 25 22:18:39 hastur kernel: [<c137a5fb>] ? start_kernel+0x21d/0x220 Feb 25 22:18:39 hastur kernel: ---[ end trace 4faff233e7319c91 ]--- Feb 25 22:18:42 hastur kernel: e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Created attachment 25243 [details] config file for kernel 2.6.33
Created attachment 25244 [details] dmesg for kernel 2.6.33
What kind of traffic are you doing at the time of failure, and I guess it is easily reproducible right? Would you be able to run some debug code for me?
It's a web server in production with many small and medium web sites, no high trafic. Error messages appearing several minutes after boot, but it's random. I can use some debug code, if it does not go down the server. :o)
Hi sorry for the delay, is the issue still occurring? I guess if you wanted to you could try 2.6.34, not for any particular fix, but just because it is the newest. I see you have an ICH5 (82865) and do you have 3GB or 4GB of ram? Please attach output of dmidecode.
Hi, Yes, I still had a trace on Friday 21. In the coming weeks I will test the kernel 2.6.34, but as the server is in production I can not reboot it regularly. :o) This server has 3 GB of ram. I post the output of dmidecode. Regards.
Created attachment 26549 [details] dmidecode output
Hi, On 23 June, I updated the server to the kernel 2.6.34. I will post the dmesg and config file. Since I had two times the error messages : Jun 24 23:15:59 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Jun 24 23:15:59 hastur kernel: Tx Queue <0> Jun 24 23:15:59 hastur kernel: TDH <a8> Jun 24 23:15:59 hastur kernel: TDT <b7> Jun 24 23:15:59 hastur kernel: next_to_use <b7> Jun 24 23:15:59 hastur kernel: next_to_clean <a0> Jun 24 23:15:59 hastur kernel: buffer_info[next_to_clean] Jun 24 23:15:59 hastur kernel: time_stamp <17d51e7> Jun 24 23:15:59 hastur kernel: next_to_watch <a9> Jun 24 23:15:59 hastur kernel: jiffies <17d541e> Jun 24 23:15:59 hastur kernel: next_to_watch.status <0> Jun 24 23:16:01 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Jun 24 23:16:01 hastur kernel: Tx Queue <0> Jun 24 23:16:01 hastur kernel: TDH <a8> Jun 24 23:16:01 hastur kernel: TDT <b7> Jun 24 23:16:01 hastur kernel: next_to_use <b7> Jun 24 23:16:01 hastur kernel: next_to_clean <a0> Jun 24 23:16:01 hastur kernel: buffer_info[next_to_clean] Jun 24 23:16:01 hastur kernel: time_stamp <17d51e7> Jun 24 23:16:01 hastur kernel: next_to_watch <a9> Jun 24 23:16:01 hastur kernel: jiffies <17d5612> Jun 24 23:16:01 hastur kernel: next_to_watch.status <0> Jun 24 23:16:03 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Jun 24 23:16:03 hastur kernel: Tx Queue <0> Jun 24 23:16:03 hastur kernel: TDH <a8> Jun 24 23:16:03 hastur kernel: TDT <b7> Jun 24 23:16:03 hastur kernel: next_to_use <b7> Jun 24 23:16:03 hastur kernel: next_to_clean <a0> Jun 24 23:16:03 hastur kernel: buffer_info[next_to_clean] Jun 24 23:16:03 hastur kernel: time_stamp <17d51e7> Jun 24 23:16:03 hastur kernel: next_to_watch <a9> Jun 24 23:16:03 hastur kernel: jiffies <17d5806> Jun 24 23:16:03 hastur kernel: next_to_watch.status <0> Jun 24 23:16:05 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Jun 24 23:16:05 hastur kernel: Tx Queue <0> Jun 24 23:16:05 hastur kernel: TDH <a8> Jun 24 23:16:05 hastur kernel: TDT <b7> Jun 24 23:16:05 hastur kernel: next_to_use <b7> Jun 24 23:16:05 hastur kernel: next_to_clean <a0> Jun 24 23:16:05 hastur kernel: buffer_info[next_to_clean] Jun 24 23:16:05 hastur kernel: time_stamp <17d51e7> Jun 24 23:16:05 hastur kernel: next_to_watch <a9> Jun 24 23:16:05 hastur kernel: jiffies <17d59fa> Jun 24 23:16:05 hastur kernel: next_to_watch.status <0> Jun 24 23:16:07 hastur kernel: ------------[ cut here ]------------ Jun 24 23:16:07 hastur kernel: WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0xcf/0x14f() Jun 24 23:16:07 hastur kernel: Hardware name: To Be Filled By O.E.M. Jun 24 23:16:07 hastur kernel: NETDEV WATCHDOG: eth0 (e1000): transmit queue 0 timed out Jun 24 23:16:07 hastur kernel: Modules linked in: Jun 24 23:16:07 hastur kernel: Pid: 0, comm: swapper Not tainted 2.6.34 #1 Jun 24 23:16:07 hastur kernel: Call Trace: Jun 24 23:16:07 hastur kernel: [<c101d5d7>] ? warn_slowpath_common+0x5e/0x8a Jun 24 23:16:07 hastur kernel: [<c101d635>] ? warn_slowpath_fmt+0x26/0x2a Jun 24 23:16:07 hastur kernel: [<c11ec1ca>] ? dev_watchdog+0xcf/0x14f Jun 24 23:16:07 hastur kernel: [<c1010030>] ? native_apic_wait_icr_idle+0x0/0x1b Jun 24 23:16:07 hastur kernel: [<c11d7b86>] ? sk_reset_timer+0xc/0x18 Jun 24 23:16:07 hastur kernel: [<c1208cd8>] ? tcp_retransmit_timer+0x4bf/0x531 Jun 24 23:16:07 hastur kernel: [<c1209072>] ? tcp_write_timer+0x0/0x162 Jun 24 23:16:07 hastur kernel: [<c11ec0fb>] ? dev_watchdog+0x0/0x14f Jun 24 23:16:07 hastur kernel: [<c10248dd>] ? run_timer_softirq+0x101/0x145 Jun 24 23:16:07 hastur kernel: [<c10212a8>] ? __do_softirq+0x5d/0xc5 Jun 24 23:16:07 hastur kernel: [<c102124b>] ? __do_softirq+0x0/0xc5 Jun 24 23:16:07 hastur kernel: <IRQ> [<c102109e>] ? irq_exit+0x25/0x53 Jun 24 23:16:07 hastur kernel: [<c1010a65>] ? smp_apic_timer_interrupt+0x5f/0x67 Jun 24 23:16:07 hastur kernel: [<c12401fa>] ? apic_timer_interrupt+0x2a/0x30 Jun 24 23:16:07 hastur kernel: [<c1006e3c>] ? default_idle+0x25/0x38 Jun 24 23:16:07 hastur kernel: [<c10018dc>] ? cpu_idle+0x23/0x3f Jun 24 23:16:07 hastur kernel: [<c138263a>] ? start_kernel+0x22c/0x22f Jun 24 23:16:07 hastur kernel: ---[ end trace 693624fee1e86793 ]--- Jun 24 23:16:10 hastur kernel: e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX And : Jun 26 08:54:44 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Jun 26 08:54:44 hastur kernel: Tx Queue <0> Jun 26 08:54:44 hastur kernel: TDH <f7> Jun 26 08:54:44 hastur kernel: TDT <1f> Jun 26 08:54:44 hastur kernel: next_to_use <1f> Jun 26 08:54:44 hastur kernel: next_to_clean <f3> Jun 26 08:54:44 hastur kernel: buffer_info[next_to_clean] Jun 26 08:54:44 hastur kernel: time_stamp <34b5f60> Jun 26 08:54:44 hastur kernel: next_to_watch <f8> Jun 26 08:54:44 hastur kernel: jiffies <34b6240> Jun 26 08:54:44 hastur kernel: next_to_watch.status <0> Jun 26 08:54:46 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Jun 26 08:54:46 hastur kernel: Tx Queue <0> Jun 26 08:54:46 hastur kernel: TDH <f7> Jun 26 08:54:46 hastur kernel: TDT <1f> Jun 26 08:54:46 hastur kernel: next_to_use <1f> Jun 26 08:54:46 hastur kernel: next_to_clean <f3> Jun 26 08:54:46 hastur kernel: buffer_info[next_to_clean] Jun 26 08:54:46 hastur kernel: time_stamp <34b5f60> Jun 26 08:54:46 hastur kernel: next_to_watch <f8> Jun 26 08:54:46 hastur kernel: jiffies <34b6434> Jun 26 08:54:46 hastur kernel: next_to_watch.status <0> Jun 26 08:54:48 hastur kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Jun 26 08:54:48 hastur kernel: Tx Queue <0> Jun 26 08:54:48 hastur kernel: TDH <f7> Jun 26 08:54:48 hastur kernel: TDT <1f> Jun 26 08:54:48 hastur kernel: next_to_use <1f> Jun 26 08:54:48 hastur kernel: next_to_clean <f3> Jun 26 08:54:48 hastur kernel: buffer_info[next_to_clean] Jun 26 08:54:48 hastur kernel: time_stamp <34b5f60> Jun 26 08:54:48 hastur kernel: next_to_watch <f8> Jun 26 08:54:48 hastur kernel: jiffies <34b6628> Jun 26 08:54:48 hastur kernel: next_to_watch.status <0> Jun 26 08:54:53 hastur kernel: e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Regards.
Created attachment 26960 [details] config file for kernel 2.6.34
Created attachment 26961 [details] dmesg of kernel 2.6.34
Hi, I've also the same problem since about one year and just opened a bug here. Now with some other search patterns I've found this, so mine is a clone *sorry* I've found a patch which fixed the problem for me: see bugreport #16471 https://bugzilla.kernel.org/show_bug.cgi?id=16471 regards Patrick
Hi, In my case, the server has 3GB of RAM, not 4 GB. Regards.
*** This bug has been marked as a duplicate of bug 16471 ***