All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Kuhne <stefan.kuhne@gmx.net>
To: xen-devel@lists.xensource.com
Subject: Re: [pv_ops] e1000e: "Detected Tx Unit Hang"
Date: Fri, 21 May 2010 00:58:18 +0200	[thread overview]
Message-ID: <4BF5BE8A.9060509@access.denied> (raw)
In-Reply-To: <4BF5B547.60700@goop.org>


[-- Attachment #1.1: Type: text/plain, Size: 2971 bytes --]

Am 21.05.2010 00:18, schrieb Jeremy Fitzhardinge:

Hello Jeremy,

> e1000e works fine for me.  However, I did have problems with my Ibex
> Peak-based system and the integrated ethernet devices; they would drop
> off the PCIe bus (lspci -vx would show all 0xff for the config space),
> which turned out to be some problem with ALPM (PCIe active link power
> management).  Could this be what you're seeing?
> 
my "lspci -vx" output:

02:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet
Controller (Copper)
        Subsystem: FIRST INTERNATIONAL Computer Inc Unknown device 4720
        Flags: bus master, fast devsel, latency 0, IRQ 409
        Memory at d0000000 (32-bit, non-prefetchable) [size=128K]
        I/O ports at 2000 [size=32]
        Capabilities: [c8] Power Management version 2
        Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable+
        Capabilities: [e0] Express Endpoint IRQ 0
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number c6-a9-09-ff-ff-0b-14-00
00: 86 80 8c 10 07 05 10 00 00 00 00 02 10 00 00 00
10: 00 00 00 d0 00 00 00 00 01 20 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 09 15 20 47
30: 00 00 00 00 c8 00 00 00 00 00 00 00 0b 01 00 00

and the complete dmesg output:
[ 9620.997466] 0000:02:00.0: peth0: Detected Tx Unit Hang:
[ 9620.997469]   TDH                  <fc>
[ 9620.997471]   TDT                  <1f>
[ 9620.997473]   next_to_use          <1f>
[ 9620.997475]   next_to_clean        <fc>
[ 9620.997477] buffer_info[next_to_clean]:
[ 9620.997479]   time_stamp           <8e2ec3>
[ 9620.997481]   next_to_watch        <fc>
[ 9620.997483]   jiffies              <8e3a25>
[ 9620.997485]   next_to_watch.status <0>
[ 9622.997490] 0000:02:00.0: peth0: Detected Tx Unit Hang:
[ 9622.997496]   TDH                  <fc>
[ 9622.997500]   TDT                  <1f>
[ 9622.997503]   next_to_use          <1f>
[ 9622.997507]   next_to_clean        <fc>
[ 9622.997511] buffer_info[next_to_clean]:
[ 9622.997515]   time_stamp           <8e2ec3>
[ 9622.997519]   next_to_watch        <fc>
[ 9622.997522]   jiffies              <8e41f5>
[ 9622.997526]   next_to_watch.status <0>
[ 9624.997536] 0000:02:00.0: peth0: Detected Tx Unit Hang:
[ 9624.997541]   TDH                  <fc>
[ 9624.997545]   TDT                  <1f>
[ 9624.997549]   next_to_use          <1f>
[ 9624.997553]   next_to_clean        <fc>
[ 9624.997557] buffer_info[next_to_clean]:
[ 9624.997561]   time_stamp           <8e2ec3>
[ 9624.997565]   next_to_watch        <fc>
[ 9624.997568]   jiffies              <8e49c5>
[ 9624.997572]   next_to_watch.status <0>
[ 9626.065848] eth0: port 1(peth0) entering disabled state
[ 9629.910292] e1000e: peth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: None
[ 9629.910854] eth0: port 1(peth0) entering forwarding state

Regards,
Stefan Kuhne


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 552 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-05-20 22:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20 21:45 [pv_ops] e1000e: "Detected Tx Unit Hang" Stefan Kuhne
2010-05-20 22:18 ` Jeremy Fitzhardinge
2010-05-20 22:58   ` Stefan Kuhne [this message]
2010-05-20 23:01     ` Jeremy Fitzhardinge
2010-05-20 23:21       ` AW: " Heiko Wundram
2010-05-23  0:16         ` Stefan Kuhne
2010-05-20 23:22       ` Stefan Kuhne
2010-05-22 15:32 ` Thomas Goirand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BF5BE8A.9060509@access.denied \
    --to=stefan.kuhne@gmx.net \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.