From owner-freebsd-stable Mon Nov 5 6:12: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 196D037B417; Mon, 5 Nov 2001 06:11:57 -0800 (PST) Received: from simoeon.sentex.net (pyroxene.sentex.ca [199.212.134.18]) by smtp1.sentex.ca (8.11.6/8.11.6) with ESMTP id fA5EBuI44803; Mon, 5 Nov 2001 09:11:56 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.1.0.14.0.20011105085938.067aea40@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 05 Nov 2001 09:05:09 -0500 To: "Stephan van Beerschoten" , From: Mike Tancsa Subject: Re: fxp0: DYNAMIC STANDBY MODE ?? In-Reply-To: <24623.199.228.142.5.1004968755.squirrel@webmail.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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: port 0xc400-0xc43f mem 0xd5101000-0xd5101fff irq 11 at device 8.0 on pci1 fxp1: Ethernet address 00:01:80:05:d2:67 inphy1: 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