Re: 3.9.0 dmesg reports that my NIC is hanging

From: John
Date: Tue May 07 2013 - 17:07:34 EST






----- Original Message -----
> From: Bjorn Helgaas <bhelgaas@xxxxxxxxxx>
> To: John <da_audiophile@xxxxxxxxx>
> Cc: lkml <linux-kernel@xxxxxxxxxxxxxxx>; Jeff Kirsher <jeffrey.t.kirsher@xxxxxxxxx>; "e1000-devel@xxxxxxxxxxxxxxxxxxxxx" <e1000-devel@xxxxxxxxxxxxxxxxxxxxx>
> 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@xxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/