Red Hat Bugzilla – Bug 430063
system hung with htb QoS
Last modified: 2008-02-15 06:01:31 EST
I've setup QoS on my ftp server to limit outgoing traffic. Apparently the server
stops responding (no output no keyboard) in an unpredictable manner. Sometimes it
takes an hour, sometimes up to 4 days for the system to hung.
I have included an attachment with my QoS startup script, dmesg output,
lspci -vvv, iptables that interact with QoS.
I'm also receiving this quite often:
Jan 15 12:23:17 ftp kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Jan 15 12:23:17 ftp kernel: Tx Queue <0>
Jan 15 12:23:17 ftp kernel: TDH <2a>
Jan 15 12:23:17 ftp kernel: TDT <17>
Jan 15 12:23:17 ftp kernel: next_to_use <17>
Jan 15 12:23:17 ftp kernel: next_to_clean <2a>
Jan 15 12:23:17 ftp kernel: buffer_info[next_to_clean]
Jan 15 12:23:17 ftp kernel: time_stamp <5798144>
Jan 15 12:23:17 ftp kernel: next_to_watch <2d>
Jan 15 12:23:17 ftp kernel: jiffies <57988ef>
Jan 15 12:23:17 ftp kernel: next_to_watch.status <0>
Jan 15 12:23:19 ftp kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Today for the first time (after applying options to e1000 driver in
modprobe.conf) I got a kernel panic:
BUG: unable to handle kernel paging request at virtual address a0379120
EIP: 0060: [<c05db2dc>] Not Tainted VLI
EIP is at ip_rcv+0x286/0x4ba
Kernel panic - not syncing: Fatal exception in interrupt
This is what I wrote on paper cause there wasn't logged anywhere.
Usually it hungs without a kernel panic.
System in Fedoca Core 8 up2date
2x Intel(R) Xeon(TM) CPU 3.20GHz
Without the QoS loaded system never hungs. It must be related to this. However
the e1000 error I'm receiving must have to do with the e1000 driver. I've seen
this bug in the past that's why I tried to apply the options in modprobe.conf
any help will be appreciated
thanx in advance
Created attachment 292781 [details]
dmesg, lspci, QoS, iptables, modprobe.conf
I was looking for this problem on the Internet and this kernel message was
mentioned with network card, router etc. This could be capabilities problem of
network card or the driver, because they mentioned problems after changing value
The type of network card could help me.
The card is an Intel Corporation 82546GB Gigabit Ethernet Controller.
By the way this bug was fixed by disabling TSO
/usr/sbin/ethtool -K eth0 tso off
I'm closing bug as notabug,because that's not iproute's problem.