From: Jean-Paul CHAPUT <jpc@asim.lip6.fr>
To: linux-kernel@vger.kernel.org
Cc: Jean-Paul CHAPUT <jpc@asim.lip6.fr>
Subject: Tulip driver advertising bug.
Date: Sun, 3 Jun 2001 19:04:05 +0200 [thread overview]
Message-ID: <20010603190405.A4884@melon.lip6.fr> (raw)
Hello Mr Kernel,
I've found a bug in the tulip driver in the advertising step.
As you can see at the end of this kernel message log, the driver
switch to advertise 0001 (which is buggy) instead of 01e1 (the
correct value for my card). 0001 means that the MII transceiver
have no capabilities (neither 10baseT, 100baseT, AUI or anything
else), so the switch shut down the link!
I've found where this bug occurs in the kernel sources :
drivers/net/tulip/tulip_core.c at line 1360
the function tulip_parse_eeprom() overwrite the value of
tp->to_advertise to 0x0001. This is strange (at least for me) because
tp->to_advertise has just been previously set to the correct value.
The kernel message :
Linux Tulip driver version 0.9.14 (February 20, 2001)
PCI: Found IRQ 11 for device 00:09.0
eth0: Digital DS21140 Tulip rev 32 at 0xe800, 00:00:C0:EF:EE:E9, IRQ 11.
eth0: EEPROM default media type Autosense.
eth0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
eth0: MII transceiver #3 config 3100 status 7809 advertising 01e1.
eth0: Advertising 0001 on PHY 3, previously advertising 01e1.
eth0: Advertising 0001 (to advertise is 0001).
My system is a standart RedHat 7.1 distribution.
Thanks a lot for Linux.
--
J e a n - P a u l C h a p u t
|
|-- e-mail : Jean-Paul.Chaput@lip6.fr
`-- Tel : (33) 01.44.27.52.53
06.66.25.35.55
U P M C Universite Pierre & Marie Curie
L I P 6 Laboratoire d'Informatique de Paris VI
A S I M Architecture des Systemes Integres et Micro-electronique
reply other threads:[~2001-06-03 17:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010603190405.A4884@melon.lip6.fr \
--to=jpc@asim.lip6.fr \
--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