All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Tim Hockin <thockin@hockin.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Natsemi DP83815 driver spaming
Date: Wed, 02 May 2007 07:54:32 +0200	[thread overview]
Message-ID: <46382798.2090709@interia.pl> (raw)
In-Reply-To: <b3ece790705011543gdca3a9ei905d3499b6c18dc8@mail.gmail.com>

>> > >  * 2) check for sudden death of the NIC:
>> > >  *    It seems that a reference set for this chip went out with
>> incorrect info,
>> > >  *    and there exist boards that aren't quite right.  An
>> unexpected voltage
>> > >  *    drop can cause the PHY to get itself in a weird state
>> (basically reset).
>> > >  *    NOTE: this only seems to affect revC chips.
>>
>> > Code commented out and NIC is working OK. Strange.
>> > eth0: DSPCFG accepted after 0 usec.
>> > eth0: link up.
>> > eth0: Setting full-duplex based on negotiated link capability.
>> > dspcfg = 0x00000000  np->dspcfg = 0x00005060
>>
>> Oh, that's entertaining.  I have to confess that I've never seen an that
>> triggered the workaround before - adding the maintainer, Tim Hockin, who
>> may be able to shed some light on the expected behaviour here?
> 
> It's been quite a while since I dealt with this issue, so I am going
> on faulty memory.  A particular reference design for this chip had bad
> resistor values, or something similar.  That caused the chip to get
> very very confused and need a reset.
Can You send me documentation? I can't find anything in datasheet. 
I will replace bad resitors with correct ones.
> So the driver is finding your chip to be hosed over and over again.
> dspcfg = 0x000000 is bad.  I'd be very surprised if you don't get
> other wierdness - bad performance or noise or who knows what.
No. It is much better. Much less packets need to be retransmitted.  
I was blaming w3cache.tkdami.net earlier.
> You could take out the error message and just let the driver do it's
> thing, or you can try to run with that logic removed.  But I'd measure
> both and see what they do.  Specifically - look  for packet errors.
With code commented out I have 1 error / 30000 transmitted packets from 
DP83815C. I have 1 error / 100000 transmitted packets to DP83815C. Maybe 
it works at all because I have short cable, only 10m long.
I don't remember any errors with plain 2.6.21.1.
> Tim
Rafał


----------------------------------------------------------------------
NIE KUPUJ!!!
...zanim nie porownasz cen >> http://link.interia.pl/f1a5e




  parent reply	other threads:[~2007-05-02  5:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 20:58 Natsemi DP83815 driver spaming Rafał Bilski
2007-05-01  3:55 ` Andrew Morton
2007-05-01  7:17   ` Rafał Bilski
2007-05-01  8:23     ` Rafał Bilski
2007-05-01  8:35       ` Andrew Morton
2007-05-01 10:40         ` Rafał Bilski
2007-05-01  8:46   ` Mark Brown
2007-05-01 10:25     ` Rafał Bilski
2007-05-01 18:08       ` Mark Brown
2007-05-01 19:10         ` Rafał Bilski
2007-05-01 19:52         ` Rafał Bilski
2007-05-01 21:27           ` Mark Brown
     [not found]             ` <b3ece790705011543gdca3a9ei905d3499b6c18dc8@mail.gmail.com>
2007-05-02  5:54               ` Rafał Bilski [this message]
     [not found]                 ` <b3ece790705012303x1e5a2d03xddf6c14aec5a99d8@mail.gmail.com>
2007-05-02  6:34                   ` Rafał Bilski
2007-05-02  6:51                     ` Tim Hockin
2007-05-02  8:22                       ` Mark Brown
     [not found]                         ` <b3ece790705020744p2e73bb5fo2c0acad947a5de15@mail.gmail.com>
2007-05-02 20:05                           ` Rafał Bilski
2007-05-02 20:48                             ` Tim Hockin
2007-05-02 21:41                             ` Mark Brown
2007-05-03  6:33                               ` Rafał Bilski

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=46382798.2090709@interia.pl \
    --to=rafalbilski@interia.pl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=thockin@hockin.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.