Your message dated Wed, 10 Jul 2013 20:09:39 +0200
with message-id <20130710180939.GC6890@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #518182,
regarding linux-2.6: Error with e1000 e1000_clean_tx_irq: Detected Tx Unit Hang
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
518182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 23
Severity: normal
I have a problem with the e1000 driver. The network card is not working
correctly.
It looks like the problem shows only up with more then 4GB Memory. I have the
same behavier with
an etch system under xen. On that system the card is working if I truncate
memory to 4GB
Here are some information:
dmesg:
[ 2869.960646] e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
[ 2869.960649] Tx Queue <0>
[ 2869.960651] TDH <6>
[ 2869.960652] TDT <6>
[ 2869.960654] next_to_use <6>
[ 2869.960655] next_to_clean <0>
[ 2869.960656] buffer_info[next_to_clean]
[ 2869.960658] time_stamp <10009c3ec>
[ 2869.960659] next_to_watch <0>
[ 2869.960660] jiffies <10009c9ae>
[ 2869.960662] next_to_watch.status <0>
[ 2871.959195] e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
[ 2871.959198] Tx Queue <0>
[ 2871.959200] TDH <6>
[ 2871.959201] TDT <6>
[ 2871.959202] next_to_use <6>
[ 2871.959204] next_to_clean <0>
[ 2871.959205] buffer_info[next_to_clean]
[ 2871.959206] time_stamp <10009c3ec>
[ 2871.959208] next_to_watch <0>
[ 2871.959209] jiffies <10009cba2>
[ 2871.959211] next_to_watch.status <0>
ethtool -i eth0
driver: e1000
version: 7.3.20-k2-NAPI
firmware-version: N/A
bus-info: 0000:01:09.0
ethtool -e eth0
Offset Values
------ ------
0x0000 00 0e 0c a8 a2 09 10 02 ff ff 00 10 ff ff ff ff
0x0010 02 c8 01 35 0b 64 76 13 86 80 7c 10 86 80 84 b2
0x0020 dd 20 55 55 00 00 90 2f 00 32 12 00 20 1e 12 00
0x0030 20 1e 12 00 20 1e 12 00 20 1e 09 00 00 02 00 00
0x0040 0c 00 a6 93 0b 28 00 00 00 04 ff ff ff ff ff ff
0x0050 ff ff ff ff ff ff ff ff ff ff ff ff ff ff 02 06
0x0060 00 01 00 40 16 12 07 40 ff ff ff ff ff ff ff ff
0x0070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff 15 05
01:09.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet
Controller (rev 05)
Subsystem: Intel Corporation PRO/1000 GT Desktop Adapter
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (63750ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fddc0000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at fdda0000 (32-bit, non-prefetchable) [size=128K]
Region 2: I/O ports at bc00 [size=64]
Expansion ROM at fde00000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [e4] PCI-X non-bridge device
Command: DPERE- ERO+ RBC=512 OST=1
Status: Dev=00:00.0 64bit- 133MHz- SCD- USC- DC=simple
DMMRBC=2048 DMOST=1 DMCRS=8 RSCEM- 266MHz- 533MHz-
Kernel driver in use: e1000
Kernel modules: e1000
Regards Matthias
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.
We don't have the ressources to reproduce the complete backlog of all older
kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with
Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by
sending
a mail to cont...@bugs.debian.org with the following three commands included in
the
mail:
reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks
Cheers,
Moritz
--- End Message ---
