From mboxrd@z Thu Jan 1 00:00:00 1970 From: jamal Subject: Re: BUG: 2.4.21-pre5 changes network scan order Date: Sun, 16 Mar 2003 23:43:10 -0500 (EST) Sender: netdev-bounce@oss.sgi.com Message-ID: <20030316233446.T9241@shell.cyberus.ca> References: <200303170425.h2H4PO8j006362@marajade.sandelman.ottawa.on.ca> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: netdev@oss.sgi.com, Marcelo Tosatti Return-path: To: Michael Richardson In-Reply-To: <200303170425.h2H4PO8j006362@marajade.sandelman.ottawa.on.ca> Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org This is definetly unacceptable behavior. Did driverfs sneak into 2.4 ? cheers, jamal On Sun, 16 Mar 2003, Michael Richardson wrote: > ------- Blind-Carbon-Copy > > To: netdev@oss.sgi.com > Subject: BUG: 2.4.21-pre5 changes network scan order > Mime-Version: 1.0 (generated by tm-edit 1.8) > Content-Type: text/plain; charset=US-ASCII > Date: Sun, 16 Mar 2003 20:25:24 -0800 > From: Michael Richardson > > - -----BEGIN PGP SIGNED MESSAGE----- > > > We installed 2.4.21-pre5 on a system that had 2.4.20 on it before. > A) The network scan order changes. It used to be: > eth0 = Intel (on motherboard) > eth1 = DP8381x > eth2 = DS21140 > > which WAS the PCI BIOS order. > > 2.4.21-pre5 does NOT get it in the PCI bios order. > > B) Since we all agree that it is unacceptable to make a change like this in > the production stream, I expect that this is a bug. > > > dhs-[~] root 31 #lspci > 00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 0) > 00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) > 00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) > 00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) > 00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) > 00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02) > 00:0d.0 Ethernet controller: Intel Corp. 82559ER (rev 09) > 00:11.0 Ethernet controller: National Semiconductor Corporation DP83815 (MacPhyr > 00:13.0 Ethernet controller: Digital Equipment Corporation DECchip 21140 [Faste) > 01:00.0 VGA compatible controller: S3 Inc. 86c368 [Trio 3D/2X] (rev 02) > > > > tulip0: EEPROM default media type Autosense. > tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. > tulip0: MII transceiver #0 config 1000 status 7809 advertising 01e1. > divert: allocating divert_blk for eth0 > eth0: Digital DS21140 Tulip rev 34 at 0xec00, 00:40:05:A3:52:E6, IRQ 10. > eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html > eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin and others > PCI: Found IRQ 9 for device 00:0d.0 > divert: allocating divert_blk for eth1 > eth1: Intel Corp. 82559ER, 00:60:EF:11:4E:5A, IRQ 9. > Receiver lock-up bug exists -- enabling work-around. > Board assembly 645520-034, Physical connectors present: RJ45 > Primary interface chip DP83840 PHY #1. > DP83840 specific setup, setting register 23 to 0422. > General self-test: passed. > Serial sub-system self-test: passed. > Internal registers self-test: passed. > ROM checksum self-test: passed (0xdbd8681d). > Receiver lock-up workaround activated. > natsemi dp8381x driver, version 1.07+LK1.0.17, Sep 27, 2002 > originally by Donald Becker > http://www.scyld.com/network/natsemi.html > 2.4.x kernel port by Jeff Garzik, Tjeerd Mulder > PCI: Found IRQ 9 for device 00:11.0 > divert: allocating divert_blk for eth2 > eth2: NatSemi DP8381[56] at 0xe080f000, 00:a0:cc:a1:fd:84, IRQ 9. > - -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.7 (GNU/Linux) > Comment: Finger me for keys > > iQCVAwUBPnVOI4qHRg3pndX9AQEY5QP/Uu0jvlmLSdH94lyn3yln0Psszc3HjTw/ > oc3CiuuIFTlZ7brJ/IuBuGjCrgS31+oaOUMq+xgqQDlXL+Pj9Xw3Q8llphjyWTKz > M15s2If2fTAVTYDuKa9WMGBT8HfmSDrE+V/2UulsG1PivUyztID8VVmqeDECctL0 > nivCqDooFV4= > =mUBg > - -----END PGP SIGNATURE----- > > ------- End of Blind-Carbon-Copy >