From: Stefan Roese <sr@denx.de>
To: Felix Radensky <felix@embedded-sol.com>
Cc: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>, netdev@vger.kernel.org
Subject: Re: e1000e "Detected Tx Unit Hang"
Date: Mon, 14 Jul 2008 09:47:46 +0200 [thread overview]
Message-ID: <200807140947.46733.sr@denx.de> (raw)
In-Reply-To: <487AFE97.8090107@embedded-sol.com>
Felix,
On Monday 14 July 2008, Felix Radensky wrote:
> I'm CC-ing Stefan, who ported Linux to this platform.
>
> Applying the patch you suggested did not help. I'm still getting TX unit
> hangs. I don't see any netdev watchdog messages. When the hang occurs
> I cannot get the prompt, so I cannot run ethtool.
>
> The following command works always
>
> dd if=/dev/zero of=/mnt/test bs=512 count=2
>
> and the following causes Tx unit hang
>
> dd if=/dev/zero of=/mnt/test bs=512 count=3
>
> Stefan, are you aware of any PCIe related problems on Canyonlands ?
> AMCC have compatibility chart on their site, which indicates that this
> particular card (Intel PRO/1000 T Desktop Adapter) Iwas tested with
> linux-2.6.25 kernel.
What Linux kernel version did you use? From kernel.org or from the
linux-2.6-denx repository? Please send the complete bootup log including
U-Boot startup log.
Thanks.
Best regards,
Stefan
next prev parent reply other threads:[~2008-07-14 7:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 11:31 e1000e "Detected Tx Unit Hang" Felix Radensky
2008-07-10 21:13 ` Brandeburg, Jesse
2008-07-10 22:25 ` Felix Radensky
2008-07-14 7:21 ` Felix Radensky
2008-07-14 7:47 ` Stefan Roese [this message]
2008-07-14 8:16 ` Felix Radensky
2008-07-18 14:55 ` Stefan Roese
2008-07-18 15:36 ` Felix Radensky
2008-07-18 15:44 ` Stefan Roese
2008-07-18 16:03 ` Felix Radensky
2008-07-18 18:29 ` Stefan Roese
-- strict thread matches above, loose matches on Subject: below --
2008-06-26 0:52 Herbert Xu
2008-06-26 7:13 ` Brandeburg, Jesse
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=200807140947.46733.sr@denx.de \
--to=sr@denx.de \
--cc=felix@embedded-sol.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).