public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Malte Schröder" <MalteSch@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 3c59x on 2.6.0-test3->test6 slow
Date: Tue, 7 Oct 2003 06:31:30 +0200	[thread overview]
Message-ID: <200310070631.30972.MalteSch@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0310062016340.19396@montezuma.fsmlabs.com>

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

mii-tool does not work for me either. I thought mine was outdated or something 
like that ;)
Oh, kernel is -test6-mm4.

# mii-tool -V
mii-tool.c 1.9 2000/04/28 00:56:08 (David Hinds)

# mii-tool eth0
SIOCGMIIPHY on 'eth0' failed: Operation not supported

On Tuesday 07 October 2003 02:18, Zwane Mwaikambo wrote:
> On Tue, 7 Oct 2003, Domen Puncer wrote:
> > On Tuesday 07 of October 2003 00:43, Zwane Mwaikambo wrote:
> > > On Tue, 7 Oct 2003, Domen Puncer wrote:
> > > > > Ok, could you send your .config too, i use the 3c59x driver and
> > > > > haven't noticed this in 2.6.0-test5-mm4. My card is;
> > > >
> > > > .config at the end of mail
> > >
> > > Sorry i forgot to ask for a dmesg too (from a kernel exhibiting the
> > > problem)
> >
> > 0000:00:0a.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xd400. Vers LK1.1.19
> > eth0: no IPv6 routers present
> > eth0: Setting full-duplex based on MII #24 link partner capability of
> > 0141.
>
> What is your link peer?
>
> > Might be relevant... the last line is lagged a couple of seconds, and
> > network works fine before i see that line in dmesg.
>
> I'm also curious as to why mii-tool doesn't work, can you attach an strace
> mii-tool eth0?
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
---------------------------------------
Malte Schröder
MalteSch@gmx.de
ICQ# 68121508
---------------------------------------


[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-10-07  4:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06 13:29 3c59x on 2.6.0-test3->test6 slow Domen Puncer
2003-10-06 21:23 ` Zwane Mwaikambo
2003-10-06 22:33   ` Domen Puncer
2003-10-06 22:43     ` Zwane Mwaikambo
2003-10-06 23:44       ` Domen Puncer
2003-10-07  0:18         ` Zwane Mwaikambo
2003-10-07  4:31           ` Malte Schröder [this message]
2003-10-07 11:05             ` Malte Schröder
2003-10-07 12:58               ` Profiling disk usage on selected branches of a file system Stephen Satchell
2003-10-07  7:49           ` 3c59x on 2.6.0-test3->test6 slow Domen Puncer
2003-10-07 23:43             ` Zwane Mwaikambo
2003-10-08 15:05               ` Domen Puncer
2003-10-09  1:53                 ` Zwane Mwaikambo
2003-10-09  8:49                   ` Domen Puncer
2003-10-09 23:10                     ` Zwane Mwaikambo
2003-10-09 23:55                       ` Domen Puncer
2003-10-13  0:22                         ` Domen Puncer
2003-10-13  0:37                           ` Andrew Morton
2003-10-13  2:28                             ` Domen Puncer
2003-10-13  3:03                               ` Andrew Morton

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=200310070631.30972.MalteSch@gmx.de \
    --to=maltesch@gmx.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