From: Jens Axboe <axboe@suse.de>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Jon Smirl <jonsmirl@gmail.com>,
jeffrey.t.kirsher@intel.com,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] e1000 C style badness
Date: Thu, 19 Jan 2006 09:02:00 +0100 [thread overview]
Message-ID: <20060119080200.GA4349@suse.de> (raw)
In-Reply-To: <4807377b0601181110y72e1e4f2w8337c559713f2da4@mail.gmail.com>
On Wed, Jan 18 2006, Jesse Brandeburg wrote:
> On 1/18/06, Jens Axboe <axboe@suse.de> wrote:
> > On Wed, Jan 18 2006, Jeff Garzik wrote:
> > > We'll get it fixed ASAP, even if it means reverting all those patches.
> >
> > Thanks, it is rather critical. At least it didn't get included in -rc1,
> > that would have been a disaster :-)
>
> just FYI, I have a patch for the e1000 breakage which will be out as
> soon as I can generate it.
Newest -git works for me. Well sort of, I get a lot of these:
e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Tx Queue <0>
TDH <72>
TDT <e5>
next_to_use <e5>
next_to_clean <6f>
buffer_info[next_to_clean]
time_stamp <10000160a>
next_to_watch <72>
jiffies <100001e09>
next_to_watch.status <0>
e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Tx Queue <0>
TDH <72>
TDT <e5>
next_to_use <e5>
next_to_clean <6f>
buffer_info[next_to_clean]
time_stamp <10000160a>
next_to_watch <72>
jiffies <1000025da>
next_to_watch.status <0>
e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Tx Queue <0>
TDH <72>
TDT <e5>
next_to_use <e5>
next_to_clean <6f>
buffer_info[next_to_clean]
time_stamp <10000160a>
next_to_watch <72>
jiffies <10000357b>
next_to_watch.status <0>
NETDEV WATCHDOG: eth0: transmit timed out
e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
--
Jens Axboe
next prev parent reply other threads:[~2006-01-19 8:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 8:07 [PATCH] e1000 C style badness Jens Axboe
2006-01-18 8:37 ` Jens Axboe
2006-01-18 17:53 ` Jon Smirl
2006-01-18 18:13 ` Jeff Garzik
2006-01-18 18:20 ` Jens Axboe
2006-01-18 19:10 ` Jesse Brandeburg
2006-01-19 8:02 ` Jens Axboe [this message]
2006-01-21 6:52 ` Jesse Brandeburg
2006-01-21 11:42 ` Jens Axboe
[not found] <5wgyi-18w-7@gated-at.bofh.it>
2006-01-18 8:56 ` Patrizio Bassi
2006-01-18 9:00 ` Jens Axboe
2006-01-18 9:02 ` Nick Piggin
2006-01-18 11:30 ` Patrizio Bassi
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=20060119080200.GA4349@suse.de \
--to=axboe@suse.de \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@gmail.com \
--cc=jgarzik@pobox.com \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 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.