Date: Mon, 05 Nov 2001 09:05:09 -0500 From: Mike Tancsa <mike@sentex.net> To: "Stephan van Beerschoten" <stephanb@xs4all.nl>, <stable@freebsd.org> Subject: Re: fxp0: DYNAMIC STANDBY MODE ?? Message-ID: <5.1.0.14.0.20011105085938.067aea40@marble.sentex.ca> In-Reply-To: <24623.199.228.142.5.1004968755.squirrel@webmail.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
What kind of motherboard chipset do you have ? Certain Intel 815 boards
have a version of the fxp built into the motherboard that has a bug that
needs to be worked around. The message below is the code doing so. The bug
manifested itself mostly in 10baseT mode and not 100baseTX. What does/did
the dmesg show for the phy type ?
for example,
fxp1: <Intel Pro/100 Ethernet> port 0xc400-0xc43f mem 0xd5101000-0xd5101fff
irq 11 at device 8.0 on pci1
fxp1: Ethernet address 00:01:80:05:d2:67
inphy1: <i82562ET 10/100 media interface> on miibus1
inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
---Mike
At 02:59 PM 11/5/01 +0100, Stephan van Beerschoten wrote:
>I hope someome can relate to this, I haven't found anything about this
>subject I'm going to discuss now.
>
>Yesterday I rebooted one of my remote systems with the up-to-date cvsup
>level of that day. The reboot went fine. This was a hardware-maintenance
>reboot too to check that everything is still working.
>Like I said, the reboot was succesful. This morning I replaced my kernel
>with a kernel that has IPFilter in stead of IPFW. This reboot went
>flawlessly too. After this reboot I decided to check up some system boot
>messages. Just to be on the safe side and then I saw the following:
>
>/kernel: fxp0: *** DISABLING DYNAMIC STANDBY MODE IN EEPROM ***
>/kernel: fxp0: New EEPROM ID: 0x40a0
>/kernel: fxp0: EEPROM checksum @0x3f: 0x17e3 -> 0x17e5
>/kernel: fxp0: *** PLEASE REBOOT THE SYSTYM NOW FOR CURRECT OPERATION ***
>
>So, because I rebooted the machine twice the last 2 days anyway, I decided
>to reboot the machine. It has to be noted that no configuration and no
>kernel changes were made during the upcoming reboot and the reboot I had
>this morning.
>
>Fact of the matter is that I am waiting for 20 minutes now for my machine
>to come back online and I don't think it will happen.
>
>In any case I would like to know what this kernel message was about and
>what exactly changed.
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.0.14.0.20011105085938.067aea40>