Re: 2.4.4 Kernel - ASUS CUV4X-DLS Question
All, I unfortunately don't have the time this evening to produce actual kernel messages, but I did want to throw out that I have an ASUS CUV4X-DLS board too, with two PIII/1GHz processors in it, and I cannot get it to boot an SMP kernel at all. In addition to the built-in devices, the following cards are also present: * Netgear FA310TX (rev. D, I believe - lspci reports it as a Lite-On LNE100TX rev 21) * Promise PDC20267 Ultra100 controller * Creative SB Live! Value * Matrox G200 AGP When it gets to the point of activating the second processor, kernel 2.4.3-ac13 starts spewing: probable hardware bug: clock timer configuration lost - probably a VIA686a motherboard. probable hardware bug: restoring chip configuration. continuously. Older kernels simply hang at this point. I'll try to get the actual messages leading up to this tomorrow. Also, if there's any other information I can collect from my system that could help, feel free to ask. I'll also build 2.4.4-ac6 on it tomorrow and try booting it SMP. Here's the output of lspci -vv: 00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4) Subsystem: Asustek Computer, Inc.: Unknown device 8038 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset- FastB2B- Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) Subsystem: Asustek Computer, Inc.: Unknown device 8038 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] [size=256K] 00:0b.0 Unknown mass storage controller: Promise Technology, Inc. 20267 (rev 02) Subsystem: Promise Technology, Inc.: Unknown device 4d33 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- [disabled] [size=64K] Capabilities: [58] Power Management version 1 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:0c.0 Multimedia audio controller: Creative Labs SB Live! EMU1 (rev 08) Subsystem: Creative Labs CT4832 SBLive! Value Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Starting kswapd v1.8 Winbond Super-IO detection, now testing ports 3F0,370,250,4E,2E ... SMSC Super-IO detection, now testing Ports 2F0, 370 ... 0x378: FIFO is 16 bytes 0x378: writeIntrThreshold is 8 0x378: readIntrThreshold is 8 0x378: PWord is 8 bits 0x378: Interrupts are ISA-Pulses 0x378: ECP port cfgA=0x10 cfgB=0x00 0x378: ECP settings irq= dma= parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,COMPAT,ECP] parport0: cpp_daisy: aa5500ff(38) parport0: assign_addrs: aa5500ff(38) parport0: cpp_daisy: aa5500ff(38) parport0: assign_addrs: aa5500ff(38) parport_pc: Via 686A parallel port: io=0x378 Detected PS/2 Mouse Port. pty: 256 Unix98 ptys configured lp0: using parport0 (polling). block: queued sectors max/low 169506kB/56502kB, 512 slots per queue Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 21 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:04.1 ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:DMA PDC20267: IDE controller on PCI bus 00 dev 58 PCI: Found IRQ 10 for device 00:0b.0 PCI: The same IRQ used for device 00:07.0 PDC20267: chipset revision 2 PDC20267: not 100% native mode: will probe irqs later PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mo
Problems with Tulip driver in 2.2 and 2.4
Any time I disconnect and then reconnect the ethernet cable from my Netgear
FA310TX cards, the card appears to not notice and doesn't reestablish the
link. Under 2.2.17pre4, the link light comes on, but until I do ifconfig
ethX down; ifconfig ethX up, the kernel ignores any traffic on that
interface (tcpdump on both an affected machine and a nonaffected machine
show the kernel ignoring all incoming traffic, and not sending any traffic
out.) Under 2.4.0-test9-pre7, however, when I reconnect the ethernet
cable, the link light does _not_ come on, and nothing short of a reboot
will bring it back up.
I'm currently stuck at 2.2.17pre4 because I need André Hedrick's IDE patch,
which won't apply (except manually) to later 2.2 kernels, and my attempts
to apply the patch manually have ended in kernels that fail during boot.
In this system, eth0 is connected to a 10/100 Asanté FriendlyNet 8-port
switch, and eth1 is connected to an RCA model DCM205 "digital|BROADBAND"
cablemodem.
Bootup messages from 2.4.0-test9-pre7:
Linux Tulip driver version 0.9.10 (September 6, 2000)
eth0: Lite-On 82c168 PNIC rev 33 at 0xe000, 00:A0:CC:3C:A8:D4, IRQ 11.
eth0: MII transceiver #1 config 1000 status 782d advertising 01e1.
eth1: Lite-On 82c168 PNIC rev 33 at 0xee00, 00:A0:CC:3C:A8:DB, IRQ 10.
eth1: MII transceiver #1 config 1000 status 782d advertising 01e1.
lspci -vv output:
00:0f.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 21)
Subsystem: Netgear FA310TX
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- http://www.scyld.com/diag/index.html
Index #1: Found a Lite-On 82c168 PNIC adapter at 0xe000.
Port selection is MII, half-duplex.
Transmit started, Receive started, half-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
The transmit threshold is 128.
MII PHY found at address 1, status 0x782d.
MII PHY #1 transceiver registers:
3000 782d 7810 0001 45e1 0001
4000 38c8 0010 0002
0001 .
Basic mode control register 0x3000: Auto-negotiation enabled.
Basic mode status register 0x782d ... 782d.
Link status: established.
Capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
Able to perform Auto-negotiation, negotiation complete.
Vendor ID is 1e:04:00:--:--:--, model 0 rev. 0.
Vendor/Part: Level One LXT970.
I'm advertising 0001:
Advertising no additional info pages.
IEEE 802.3 CSMA/CD protocol.
Link partner capability is 45e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD
10baseT.
Negotiation completed.
Index #2: Found a Lite-On 82c168 PNIC adapter at 0xee00.
Port selection is MII, half-duplex.
Transmit started, Receive started, half-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
The transmit threshold is 128.
MII PHY found at address 1, status 0x782d.
MII PHY #1 transceiver registers:
3000 782d 7810 0001 41e1 0001
4000 38c8 0010 0002
0001 .
Basic mode control register 0x3000: Auto-negotiation enabled.
Basic mode status register 0x782d ... 782d.
Link status: established.
Capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
Able to perform Auto-negotiation, negotiation complete.
Vendor ID is 1e:04:00:--:--:--, model 0 rev. 0.
Vendor/Part: Level One LXT970.
I'm advertising 0001:
Advertising no additional info pages.
IEEE 802.3 CSMA/CD protocol.
Link partner capability is 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
Negotiation completed.
When unhappy, the basic mode status register contains the value 0x7809, the
link status is "not established", and negotiation is listed as not
complete. Attempts to kick the card back into operation with -r, -R, -A,
or -F achieve nothing.
Bootup messages from 2.2.17pre4:
tulip.c:v0.91g-ppc 7/16/99 [EMAIL PROTECTED]
eth0: Lite-On 82c168 PNIC rev 33 at 0xe000, 00:A0:CC:3C:A8:D4, IRQ 11.
eth0: MII transceiver #1 config 1000 status 782d advertising 01e1.
eth1: Lite-On 82c168 PNIC rev 33 at 0xee00, 00:A0:CC:3C:A8:DB, IRQ 10.
eth1: MII transceiver #1 config 1000 status 782d advertising 01e1.
< a few seconds later >
eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: Setting full-duplex based on MII#1 link partner capability of 41e1.
lspci -vv output, in 2.2.17pre4:
Identical with that from 2.4.0-test9-pre7, except the [size=XXX] information
isn't printed.
tulip-diag output, when happy, from 2.2.17pre4:
tulip-diag.c:v2.04 9/26/2000 Donald Becker ([EMAIL PROTECTED])
http://www.scyld.com/diag/index.html
Index #1: Found a Lite-On 82c168 PNIC adapter at 0xe000.
Port selection is MII, full-duplex.
Transmit started, Receive st
Re: Problems with Tulip driver in 2.2 and 2.4
On Sun, 15 Oct 2000, David Rees wrote: > I've seen similar behavior on the same cards, but it only seems to affect > 100Mbps operation, plugging it into a 10Mbps hub instead of our 3Com > 100Mbps switch will also get things working as does running ifup/ifdown on > the interface. eth0 on my machine is a 100 Mbps interface. eth1 is connected to a cablemodem that only does 10 Mbps. It's the cablemodem interface that gives me the most grief, as whenever it resets and resynchs to the network, it drops the ethernet link. Jeff, I'll give your suggestion a try tomorrow. If I can work out what magic makes it work, I'll try merging it into 2.4 and let you know. -- Jeffrey Sean Connell __ | SHOUTip Team Leader, net.com [EMAIL PROTECTED] \/ | PGP key: http://www.canuck.gen.nz/~ankh/pgpkey.html + - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
