linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pete Clements <clem@clem.clem-digital.net>
To: klassert@mathematik.tu-chemnitz.de (Steffen Klassert)
Cc: clem@clem.clem-digital.net (Pete Clements),
	linux-kernel@vger.kernel.org (linux-kernel),
	akpm@osdl.org (Andrew Morton)
Subject: Re: Correction: 2.6.16-git12 killed networking -- 3c900 card
Date: Tue, 28 Mar 2006 11:44:54 -0500 (EST)	[thread overview]
Message-ID: <200603281644.k2SGish7001726@clem.clem-digital.net> (raw)
In-Reply-To: <20060328141443.GB8455@gareth.mathematik.tu-chemnitz.de>

[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]

Quoting Steffen Klassert
  > > 
  > > FYI:
  > >   Single 3c900 card, UP i386
  > >   Lost networking with .16-git12, message
  > >   ADDRCONF(NETDEV_UP): eth0: link is not ready
  > 
  > This could be due to the recent driver update.
  > I can not reproduce this with a 3c900B-Combo,
  > so I need some more information to track it down.

Data attached. Note:
 1) Using coax 10base2.
 2) Driver is compiled in, not a module. If you need I'll
    recompile with debug set.
  > 
  > >   Had several of these with git11
  > >   NETDEV WATCHDOG: eth0: transmit timed out
  > 
  > Is this for sure that these messages occured first time with git11?
  > There were no changes in the 3c59x driver between git10 and git11.

 Only occurrance in git11, 4 hits during a local net ftp. Low network 
 load system.

  > 
  > > 
  > >   No problems observed git1-git10
  > > 
  > 
  > If you are willing to provide me with some information
  > you can send the following:
  > 
  > 1. output of lspci -vvv (just the ethernet controller related part)
  > 
  > 2. your Kernel configuration
  > 
  > 3. modprobe the driver with debug=4 and send
  > the 3c59x related lines of your logs for both, git11 and git12.
  > (From driver startup about 15 seconds should be sufficiant for now)
  > 
  > 4. the output of "vortex-diag -aem" and "mii-diag".
  > You can find these tools at http://www.scyld.com/ethercard_diag.html
  > 
  > 
  > Steffen
  > -

-- 
Pete Clements 

[-- Attachment #2: gzip compressed data, from Unix --]
[-- Type: application/octet-stream, Size: 5299 bytes --]

  reply	other threads:[~2006-03-28 16:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27  2:12 Correction: 2.6.16-git12 killed networking -- 3c900 card Pete Clements
2006-03-28 14:14 ` Steffen Klassert
2006-03-28 16:44   ` Pete Clements [this message]
2006-03-29 11:47     ` Steffen Klassert
2006-03-29 14:27       ` Pete Clements
2006-03-29  1:12   ` Pete Clements
2006-03-29  2:50   ` Pete Clements
2006-03-29  6:43     ` Andrew Morton
2006-03-29  9:14       ` Steffen Klassert
2006-03-29 14:39       ` Pete Clements
2006-03-29  6:49     ` Andrew Morton
2006-03-29 14:49       ` Pete Clements
2006-03-29 19:29         ` Andrew Morton
2006-03-30  0:53           ` Pete Clements
2006-03-30  1:10             ` Andrew Morton
2006-03-30  1:19               ` Pete Clements
2006-03-30  4:51               ` Pete Clements
2006-03-30  5:09                 ` Andrew Morton
2006-03-30 13:46                   ` Pete Clements
2006-03-30 14:29                     ` Steffen Klassert
2006-03-30 16:02                       ` Pete Clements
2006-03-29  7:01     ` Andrew Morton
2006-03-29 15:15       ` Pete Clements
2006-03-29  1:07 ` Pete Clements

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=200603281644.k2SGish7001726@clem.clem-digital.net \
    --to=clem@clem.clem-digital.net \
    --cc=akpm@osdl.org \
    --cc=klassert@mathematik.tu-chemnitz.de \
    --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;
as well as URLs for NNTP newsgroup(s).