From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org,
Matheos Worku <matheos.worku@sun.com>,
jesper@krogh.cc
Subject: Re: [Bugme-new] [Bug 10801] New: niu Sun Neptune 10G fiber card - "transmit timed out".
Date: Mon, 26 May 2008 12:52:02 -0700 [thread overview]
Message-ID: <20080526125202.3d7cd1fc.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-10801-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Mon, 26 May 2008 12:42:18 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=10801
>
> Summary: niu Sun Neptune 10G fiber card - "transmit timed out".
> Product: Drivers
> Version: 2.5
> KernelVersion: 2.6.25.2
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Network
> AssignedTo: jgarzik@pobox.com
> ReportedBy: jesper@krogh.cc
>
>
> Latest working kernel version: ?
> Earliest failing kernel version: 2.6.24 (perhaps earlier)
> Distribution: Ubuntu Hardy
> Hardware Environment: Sun Fire X4600 M2
> Software Environment:
> Problem Description:
> The driver locks up the kernel and only a hard reboot can bring the system bag.
> only message in the log is:
> May 26 10:51:14 hest kernel: [1477079.785404] NETDEV WATCHDOG: eth4: transmit
> timed out
> .. many times pr. second.
>
> Steps to reproduce:
> It seems to be reproducible by sending a lot of traffic (small packages)
> through the card. But I've also hit it under normal production (an NFS server).
>
> Discussion:
> http://thread.gmane.org/gmane.linux.kernel/677545
>
next parent reply other threads:[~2008-05-26 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10801-10286@http.bugzilla.kernel.org/>
2008-05-26 19:52 ` Andrew Morton [this message]
2008-05-26 22:16 ` [Bugme-new] [Bug 10801] New: niu Sun Neptune 10G fiber card - "transmit timed out" David Miller
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=20080526125202.3d7cd1fc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jesper@krogh.cc \
--cc=matheos.worku@sun.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).