Date: Sun, 10 Dec 2000 20:06:05 +0100 From: Cliff Sarginson <cliff@raggedclown.net> To: Mark Huizer <freebsd@dohd.org>, freebsd-current@freebsd.org Subject: Re: fxp driver not reset after Windows reboot? Message-ID: <00121020060504.01067@buffy> In-Reply-To: <20001210130814.A47149@dohd.cx> References: <20001210130814.A47149@dohd.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello I have the self same problem with my nics' Realtek 8139's. But on my '98 machine it is dual bootable with Linux. If I don't power cycle the PC between using windows and Linux my nic's are unusable, gaining a MAC address of FFFF........ as I see yours does. I have found no solution for it (even swearing doesnt help) but since it so similar to your problem and with both Linux and FreeBSD .... we have been Gate'd again Cliff On Sunday 10 December 2000 13:08, Mark Huizer wrote: > Hello, > > On my VAIO laptop, I have trouble rebooting directly from Windows to > FreeBSD (luckily enough I don't run Windows that often :-) > I tried to look at the driver code, but it looks to me like it is doing > resets when attaching the fxp driver, but somehow, Windows has left it > in the state where it isn't recognized properly. > > Below I have dmesg output, stripped to the fxp0 part. Does anyone have > an idea what the problem might be, or where to try to debug this? > I have added some comments to the dmesg output, /* here */, to add the > programs running there > > Mark > > FreeBSD 5.0-CURRENT #0: Wed Dec 6 09:34:39 CET 2000 > root@pooh.local.dohd.org:/usr/src2/sys/compile/vaio > Preloaded elf kernel "kernel" at 0xc042b000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc042b09c. > Preloaded elf module "if_fxp.ko" at 0xc042b0ec. > fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0xfcc0-0xfcff mem > 0xfed00000-0xfedfffff,0xfecff000-0xfecfffff irq 9 at device 11.0 on pci0 > fxp0: Ethernet address ff:ff:ff:ff:ff:ff, 10Mbps > BRIDGE 990810, have 7 interfaces > -- index 1 type 6 phy 0 addrl 6 addr ff.ff.ff.ff.ff.ff > /* dhclient leads to the below */ > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: DMA timeout > fxp0: SCB timeout > fxp0: DMA timeout > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: warning: unsupported PHY, type = 63, addr = 255 > /* IPv6 router sollicitation below */ > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: DMA timeout > fxp0: SCB timeout > fxp0: DMA timeout > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: warning: unsupported PHY, type = 63, addr = 255 > /* various stuff like apache etc below */ > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: DMA timeout > fxp0: SCB timeout > fxp0: DMA timeout > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: warning: unsupported PHY, type = 63, addr = 255 > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: device timeout > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: DMA timeout > fxp0: SCB timeout > fxp0: DMA timeout > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: warning: unsupported PHY, type = 63, addr = 255 > fxp0: SCB timeout > fxp0: SCB timeout > fxp0: device timeout > fxp0: SCB timeout > /* etc etc */ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00121020060504.01067>