[eepro100] PRO/100+ Fell Asleep, Never Woke Up!

Alvin Oga aoga@Mail.Linux-Consulting.com
Tue, 19 Sep 2000 13:57:04 -0700 (PDT)


hi basil...

try checking the motherboard bios "power saving" settings...
	- turn those power thingies off...

the new intel d815eeaal mb also tries to conserve power and shutdowns
completely after 20 minutes of idle....no way to wake it up except
a reset button.....

oh well
alvin

On Tue, 19 Sep 2000, Basil Hussain wrote:

> Hi all,
> 
> I have an Intel PRO/100+ Management Adapter PCI card (make that two, now)
> that I was using happily in a server (PIII-600, 128Mb) under RedHat Linux
> 6.0 (using the out-of-the-box drivers). It was working just fine, up until a
> few days ago. I'm trying to discover whether the config isn't right, or if
> the machine it's in is now broken.
> 
> Here's what's happened:
> 
> * The situation arises that I need to press the machine into production use.
> Decide to wipe it clean by doing a re-install of RedHat. I configure the
> machine and install software, etc.
> 
> * I start to copy some data onto it via FTP. This is where the trouble
> starts. I experience problems exactly similar to what this guy below
> reported on the list back in April. However, I didn't have time to look into
> it, as some other task came up. I shut the machine down for the weekend.
> 
> > I don't know what he did, but I have had cases where I _have_ to do an
> > outward ping before eepro100 starts doing anything.
> > Pinging it from outside does not wake it up.
> 
> * I return to the office, power on, and all of a sudden the network
> connection is dead. Pinging in or out results in nothing. I suspect I may
> have made a config goof, so I wipe the machine clean again, but still the
> same.
> 
> So this is where I'm at now. I can't figure what the hell is going on.
> Here's what I've checked, but to no avail:
> 
> * Network cable - used another known-working lead.
> * Switch - changed to another port. Even changed to a different hub.
> * Network card - put in another brand new PRO/100+.
> * PCI slot - moved the card to another PCI slot.
> 
> So, I know it's not the card, cable or switch. Could be the motherboard,
> though... Not sure. Hopefully someone here can help me make a decision. I
> enclose below output from ifconfig, eepro100-diag, mii-diag, /proc/pci and
> /proc/interrupts.
> 
> Regards,
> 
> ------------------------------------------------
> Basil Hussain (basil.hussain@specialreserve.net)
> 
> 
> ifconfig:
> ---------
> 
> eth0      Link encap:Ethernet  HWaddr 00:D0:B7:21:EC:82
>           inet addr:212.125.93.118  Bcast:212.125.93.127
> Mask:255.255.255.224
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:385 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:107 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           Interrupt:10 Base address:0xec00
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:3924  Metric:1
>           RX packets:150 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:150 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
> 
> eepro100-diag:
> --------------
> 
> eepro100-diag.c:v2.02 7/19/2000 Donald Becker (becker@scyld.com)
>  http://www.scyld.com/diag/index.html
> Index #1: Found a Intel i82557 (or i82558) EtherExpressPro100B adapter at
> 0xec00.
> i82557 chip registers at 0xec00:
>   00000050 0fdb68f0 00000000 00080002 18250021 00000600
>   No interrupt sources are pending.
>    The transmit unit state is 'Suspended'.
>    The receive unit state is 'Ready'.
>   This status is normal for an activated but idle interface.
> Intel EtherExpress Pro 10/100 EEPROM contents:
>   Station address 00:D0:B7:21:EC:82.
>   Board assembly 721383-008, Physical connectors present: RJ45
>   Primary interface chip i82555 PHY #1.
>  MII PHY #1 transceiver registers:
>   3000 782d 02a8 0154 05e1 0021 0000 0000
>   0000 0000 0000 0000 0000 0000 0000 0000
>   0400 0000 0001 0000 0000 0000 0000 0000
>   0000 0000 0000 0000 0000 0000 0000 0000.
>  MII PHY #1 transceiver registers:
>    3000 782d 02a8 0154 05e1 0021 0000 0000
>    0000 0000 0000 0000 0000 0000 0000 0000
>    0400 0000 0001 0000 0000 0000 0000 0000
>    0000 0000 0000 0000 0000 0000 0000 0000.
>  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 00:aa:00:--:--:--, model 21 rev. 4.
>    No specific information is known about this transceiver type.
>  I'm advertising 05e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD
> 10baseT
>    Advertising no additional info pages.
>    IEEE 802.3 CSMA/CD protocol.
>  Link partner capability is 0021: 10baseT.
>    Negotiation did not complete.
> 
> mii-diag:
> ---------
> 
> Basic registers of MII PHY #1:  3000 782d 02a8 0154 05e1 0021 0000 0000.
>  Basic mode control register 0x3000: Auto-negotiation enabled.
>  You have link beat, and everything is working OK.
>  Your link partner is generating 10baseT link beat  (no autonegotiation).
> 
> /proc/pci:
> ----------
> 
> PCI devices found:
>   Bus  0, device   0, function  0:
>     Host bridge: VIA Technologies Unknown device (rev 68).
>       Vendor id=1106. Device id=691.
>       Medium devsel.  Master Capable.  No bursts.
>       Prefetchable 32 bit memory at 0xe0000000 [0xe0000008].
>   Bus  0, device   1, function  0:
>     PCI bridge: VIA Technologies VT 82C598 Apollo MVP3 AGP (rev 0).
>       Medium devsel.  Master Capable.  No bursts.  Min Gnt=12.
>   Bus  0, device   7, function  0:
>     ISA bridge: VIA Technologies Unknown device (rev 27).
>       Vendor id=1106. Device id=686.
>       Medium devsel.  Master Capable.  No bursts.
>   Bus  0, device   7, function  1:
>     IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
>       Medium devsel.  Fast back-to-back capable.  Master Capable.
> Latency=64.
>       I/O at 0xe000 [0xe001].
>   Bus  0, device  14, function  0:
>     Ethernet controller: Intel 82557 (rev 8).
>       Medium devsel.  Fast back-to-back capable.  IRQ 10.  Master Capable.
> Latency=64.  Min Gnt=8.Max Lat=56.
>       Non-prefetchable 32 bit memory at 0xe9100000 [0xe9100000].
>       I/O at 0xec00 [0xec01].
>       Non-prefetchable 32 bit memory at 0xe9000000 [0xe9000000].
>   Bus  1, device   0, function  0:
>     VGA compatible controller: ATI Mach64 GB (rev 92).
>       Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master Capable.
> Latency=64.  Min Gnt=8.
>       Non-prefetchable 32 bit memory at 0xe4000000 [0xe4000000].
>       I/O at 0xd000 [0xd001].
>       Non-prefetchable 32 bit memory at 0xe6000000 [0xe6000000].
> 
> /proc/interrupts:
> -----------------
> 
>            CPU0
>   0:     362235          XT-PIC  timer
>   1:       2168          XT-PIC  keyboard
>   2:          0          XT-PIC  cascade
>   8:          2          XT-PIC  rtc
>  10:        497          XT-PIC  Intel EtherExpress Pro 10/100 Ethernet
>  13:          1          XT-PIC  fpu
>  14:      56715          XT-PIC  ide0
>  15:          5          XT-PIC  ide1
> NMI:          0
> 
> 
> 
> _______________________________________________
> eepro100 mailing list
> eepro100@scyld.com
> http://www.scyld.com/mailman/listinfo/eepro100
>