netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Krogh <jesper@krogh.cc>
To: Matheos Worku <Matheos.Worku@Sun.COM>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: niu driver - Transmit timed out - 2.6.29
Date: Sat, 28 Mar 2009 08:25:41 +0100	[thread overview]
Message-ID: <49CDD0F5.1060802@krogh.cc> (raw)
In-Reply-To: <49CDC136.60709@sun.com>

Matheos Worku wrote:
> Jesper Krogh wrote:
>> Matheos Worku wrote:
>>>> This is probably the interesting part:
>>>> Mar 26 13:25:49 hest kernel: [25335.587191] niu 0000:84:00.0: niu: 
>>>> eth4: bits (40000000) of register RXDMA_CFIG1 would not clear, 
>>>> val[c0000000]
>>> Jesper,
>>>
>>> One of the RX  ring DMAs  is failing to reset. I guess whatever is 
>>> hanging the TX side is affecting the RX side as well. Can you do 
>>> lspci on the function  and its siblings?
>>
>> Like this(please guide me if that wasn't the correct lspci output):
> 
> Jesper,
> 
> I was wondering if you can get the register dump just after the NIC hangs.
> 
> lspci -vvv -xxx -s 84:0

I will try to do that, but it involves more or less "putting a known bad 
driver" in production. And wait X days. (where X usually is less than 7 
and more than 2). So if there is more debugging code that would be 
helpful to have in the driver/kernel then it would be preferrable to get 
it in at the same time, in order to reduce the amount of trial-and-error 
cycles.

-- 
Jesper


      reply	other threads:[~2009-03-28  7:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 12:44 niu driver - Transmit timed out - 2.6.29 Jesper Krogh
2009-03-27 19:31 ` Jesper Krogh
2009-03-28  0:42   ` Matheos Worku
2009-03-28  6:05     ` Jesper Krogh
2009-03-28  6:18       ` Matheos Worku
2009-03-28  7:25         ` Jesper Krogh [this message]

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=49CDD0F5.1060802@krogh.cc \
    --to=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).