From: John <da_audiophile@yahoo.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>
Subject: Re: 3.9.0 dmesg reports that my NIC is hanging
Date: Tue, 7 May 2013 14:07:29 -0700 (PDT) [thread overview]
Message-ID: <1367960849.23964.YahooMailNeo@web140002.mail.bf1.yahoo.com> (raw)
In-Reply-To: <CAErSpo4C3-WH6_GOnmz1TgKsD3SyNGQYeU8Cj0=_+c+9K2yS+A@mail.gmail.com>
----- Original Message -----
> From: Bjorn Helgaas <bhelgaas@google.com>
> To: John <da_audiophile@yahoo.com>
> Cc: lkml <linux-kernel@vger.kernel.org>; Jeff Kirsher <jeffrey.t.kirsher@intel.com>; "e1000-devel@lists.sourceforge.net" <e1000-devel@lists.sourceforge.net>
> Sent: Monday, May 6, 2013 1:29 PM
> Subject: Re: 3.9.0 dmesg reports that my NIC is hanging
>
> [+cc Jeff, e1000-devel (from MAINTAINERS)]
>
> On Sat, May 4, 2013 at 1:56 PM, John <da_audiophile@yahoo.com> wrote:
>> After upgrading to the official Arch Linux 3.9-2 kernel package, dmesg
> reports that my NIC is hanging:
>>
>> [ 5.955720] e1000e 0000:00:19.0 eno1: changing MTU from 1500 to 4000
>> [ 8.464507] e1000e 0000:00:19.0 eno1: Detected Hardware Unit Hang:
>> TDH <0>
>> TDT <2>
>> next_to_use <2>
>> next_to_clean <0>
>> buffer_info[next_to_clean]:
>> time_stamp <fffea787>
>> next_to_watch <0>
>> jiffies <fffeaa30>
>> next_to_watch.status <0>
>> MAC Status <40080080>
>> PHY Status <7949>
>> PHY 1000BASE-T Status <0>
>> PHY Extended Status <3000>
>> PCI Status <10>
>>
>> Not too sure what else to post. I am not subscribed to lkml so please cc
> my email in your reply.
>>
>>
>> Link to complete dmesg: http://pastebin.com/zRBajGrY
>> Seems similar to: bugzilla.redhat.com/show_bug.cgi?id=785806
>
> It sounds like this is a regression, so it might be useful to know
> what the newest working kernel was, and maybe a dmesg log from it as
> well, though I don't see any obvious clues in the 3.9.0-2-ARCH dmesg
> you collected.
>
> Bjorn
Thank you for the reply, Bjorn. 3.8.11-1-ARCH works just fine for me. Here is the dmesg from 3.8.11-1-ARCH per your request: http://pastebin.com/cUHwrQfq
next prev parent reply other threads:[~2013-05-07 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 20:56 John
2013-05-06 17:29 ` Bjorn Helgaas
2013-05-07 21:07 ` John [this message]
2013-08-22 17:44 ` Bjorn Helgaas
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=1367960849.23964.YahooMailNeo@web140002.mail.bf1.yahoo.com \
--to=da_audiophile@yahoo.com \
--cc=bhelgaas@google.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®