Re: sk0: watchdog timeout
Ferdinand Haselbacher (jr.) wrote: On Tue, Nov 29, 2005 at 07:22:17PM -0500, Nicolas Blais wrote: That's great. But as I said, there's nothing I can configure on my switch's side. Anyway, you and I aren't the only ones with the same problem, under the same circonstances. My forcing of the TX/RX mode does speed up recovery, but doesn't fix the actual issue. The driver has a bug somewhere. Although I'm not talented enough in driver programming, but someone with skills could probably fix this. Maybe the driver has a bug somewhere, but i also think that this marvell chips have some design flaws, iam using one on my A8V and it 's giving me problems in WinXp (although i didn't use it for a while), Linux (seems to work better now in 2.6.14-mm1, but still connection losses) and freebsd too. I can confirm that I got pretty much the same thing happening in Windows XP Professional SP2. There was a driver update for the Marvel Yukon NIC in Windows XP sometime ago which made it even worse and made the whole machine crash under heavy load (and my Windows XP is generally rock solid). I will be installing Gentoo soon and if it's still happening there with that skge (not sure if that's what it was called) driver, then I guess it's got to be something with the hardware. It's a bit of a shame that my other on-board nvidia NIC (nforce 4 chipset) doesn't really work well with the nve driver either. Two on-board NICs and I still need to go out and buy a 'real' one ;( ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0: watchdog timeout
On Tue, Nov 29, 2005 at 07:22:17PM -0500, Nicolas Blais wrote: That's great. But as I said, there's nothing I can configure on my switch's side. Anyway, you and I aren't the only ones with the same problem, under the same circonstances. My forcing of the TX/RX mode does speed up recovery, but doesn't fix the actual issue. The driver has a bug somewhere. Although I'm not talented enough in driver programming, but someone with skills could probably fix this. Maybe the driver has a bug somewhere, but i also think that this marvell chips have some design flaws, iam using one on my A8V and it 's giving me problems in WinXp (although i didn't use it for a while), Linux (seems to work better now in 2.6.14-mm1, but still connection losses) and freebsd too. Nicolas. -- FreeBSD 7.0-CURRENT #2: Sat Nov 26 10:55:30 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CLK01A PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc so far -- pgppzPHlpubmC.pgp Description: PGP signature
Re: sk0: watchdog timeout
Bernhard Fischer wrote: If you change hardware settings, you should also maintain the same settings on both ends of the wire, i.e. at the computer *and* the ethernet switch. [SNIP] I just forced it to use 100baseTX / full-duplex which I think was used before I forced it as well. That's exactly what I ment. If you force your sk0 to 100-full do the same with your switch. If you set sk0 to auto-config -- do it with your switch. That's great. But as I said, there's nothing I can configure on my switch's side. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0: watchdog timeout
That's great. But as I said, there's nothing I can configure on my switch's side. Anyway, you and I aren't the only ones with the same problem, under the same circonstances. My forcing of the TX/RX mode does speed up recovery, but doesn't fix the actual issue. The driver has a bug somewhere. Although I'm not talented enough in driver programming, but someone with skills could probably fix this. Nicolas. -- FreeBSD 7.0-CURRENT #2: Sat Nov 26 10:55:30 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CLK01A PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc pgpz5869zM71t.pgp Description: PGP signature
Re: sk0: watchdog timeout
Hans Nieser wrote: Nicolas Blais wrote: I have an sk0 too on one of my computer's onboard A8V-DX which will timeout once in a while too. I found a way to reduce down time by modifying my rc.conf to force 'full-duplex 100Mbps'. Now, even when it goes into a watchdog timeout, I quickly get back my link within that second. This is what my rc.conf line looks like: ifconfig_sk0=inet 192.168.1.100 media 100baseTX mediaopt full-duplex netmask 255.255.255.0 Thanks! Will give this a try It appears the above hasn't helped me, it still goes down after copying about 10-15GB of data and I still have to bring the interface down and up again to regain connectivity. Thanks for the tip though, it was worth a try ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0: watchdog timeout
ifconfig_sk0=inet 192.168.1.100 media 100baseTX mediaopt full-duplex netmask 255.255.255.0 It appears the above hasn't helped me, it still goes down after copying about 10-15GB of data and I still have to bring the interface down and up again to regain connectivity. Thanks for the tip though, it was worth a try If you change hardware settings, you should also maintain the same settings on both ends of the wire, i.e. at the computer *and* the ethernet switch. Regards, bh pgpUMZMbOQegg.pgp Description: PGP signature
Re: sk0: watchdog timeout
Bernhard Fischer wrote: ifconfig_sk0=inet 192.168.1.100 media 100baseTX mediaopt full-duplex netmask 255.255.255.0 It appears the above hasn't helped me, it still goes down after copying about 10-15GB of data and I still have to bring the interface down and up again to regain connectivity. Thanks for the tip though, it was worth a try If you change hardware settings, you should also maintain the same settings on both ends of the wire, i.e. at the computer *and* the ethernet switch. Hmm, I'm not sure what you mean. There isn't much (in fact, nothing at all) I can configure on my switch's end as it's a cheap 8-port 10/100mbit switch (A UNEX NexSwitch SD080s). I just forced it to use 100baseTX / full-duplex which I think was used before I forced it as well. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0: watchdog timeout
If you change hardware settings, you should also maintain the same settings on both ends of the wire, i.e. at the computer *and* the ethernet switch. [SNIP] I just forced it to use 100baseTX / full-duplex which I think was used before I forced it as well. That's exactly what I ment. If you force your sk0 to 100-full do the same with your switch. If you set sk0 to auto-config -- do it with your switch. Watch your interface-counters: netstat -I sk0 -b -d -t If the hardware (cards, cabeling, plugs, ...) is ok, there shouldn't be any errors for days or even weeks! Regards, bh pgpYjJkaOjpYe.pgp Description: PGP signature
Re: sk0: watchdog timeout
Bernhard Fischer wrote: If you change hardware settings, you should also maintain the same settings on both ends of the wire, i.e. at the computer *and* the ethernet switch. [SNIP] I just forced it to use 100baseTX / full-duplex which I think was used before I forced it as well. That's exactly what I ment. If you force your sk0 to 100-full do the same with your switch. If you set sk0 to auto-config -- do it with your switch. Watch your interface-counters: netstat -I sk0 -b -d -t If the hardware (cards, cabeling, plugs, ...) is ok, there shouldn't be any errors for days or even weeks! Regards, bh Hi Bernhard, thanks for your message. I suppose we all know something about networking, but this is hardware/driver related problem ( with the highest probability ). I used my server in two different environments - at home and now at serverhouse. No difference. Still getting (from time to time ): sk0: watchdog timeout sk0: link state changed to DOWN sk0: watchdog timeout sk0: link state changed to UP sk0: watchdog timeout sk0: link state changed to DOWN sk0: watchdog timeout sk0: link state changed to UP sk0: watchdog timeout sk0: link state changed to DOWN messages. But server still running. I am out of ideas how can we solve our problem and I am about to buy new network card, because this stressfull situation is not good. ;-) Vladimir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0: watchdog timeout
--- Vladimir Dvorak [EMAIL PROTECTED] wrote: Bernhard Fischer wrote: If you change hardware settings, you should also maintain the same settings on both ends of the wire, i.e. at the computer *and* the ethernet switch. [SNIP] I just forced it to use 100baseTX / full-duplex which I think was used before I forced it as well. That's exactly what I ment. If you force your sk0 to 100-full do the same with your switch. If you set sk0 to auto-config -- do it with your switch. Watch your interface-counters: netstat -I sk0 -b -d -t If the hardware (cards, cabeling, plugs, ...) is ok, there shouldn't be any errors for days or even weeks! Regards, bh Hi Bernhard, thanks for your message. I suppose we all know something about networking, but this is hardware/driver related problem ( with the highest probability ). I used my server in two different environments - at home and now at serverhouse. No difference. Still getting (from time to time ): sk0: watchdog timeout sk0: link state changed to DOWN sk0: watchdog timeout sk0: link state changed to UP sk0: watchdog timeout sk0: link state changed to DOWN sk0: watchdog timeout sk0: link state changed to UP sk0: watchdog timeout sk0: link state changed to DOWN messages. But server still running. I am out of ideas how can we solve our problem and I am about to buy new network card, because this stressfull situation is not good. ;-) Vladimir There are generally 2 cases in which you'll get a watchdog timeout message on a network card driver. 1) Your machine is in livelock (ie overrun) 2) There is a problem with the interrupts Clearly you should know if 1) was occurring. With 2), it could be a driver or hardware problem or both. DT __ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0: watchdog timeout
Danial Thom wrote: --- Vladimir Dvorak [EMAIL PROTECTED] wrote: Bernhard Fischer wrote: If you change hardware settings, you should also maintain the same settings on both ends of the wire, i.e. at the computer *and* the ethernet switch. [SNIP] I just forced it to use 100baseTX / full-duplex which I think was used before I forced it as well. That's exactly what I ment. If you force your sk0 to 100-full do the same with your switch. If you set sk0 to auto-config -- do it with your switch. Watch your interface-counters: netstat -I sk0 -b -d -t If the hardware (cards, cabeling, plugs, ...) is ok, there shouldn't be any errors for days or even weeks! Regards, bh Hi Bernhard, thanks for your message. I suppose we all know something about networking, but this is hardware/driver related problem ( with the highest probability ). I used my server in two different environments - at home and now at serverhouse. No difference. Still getting (from time to time ): sk0: watchdog timeout sk0: link state changed to DOWN sk0: watchdog timeout sk0: link state changed to UP sk0: watchdog timeout sk0: link state changed to DOWN sk0: watchdog timeout sk0: link state changed to UP sk0: watchdog timeout sk0: link state changed to DOWN messages. But server still running. I am out of ideas how can we solve our problem and I am about to buy new network card, because this stressfull situation is not good. ;-) Vladimir There are generally 2 cases in which you'll get a watchdog timeout message on a network card driver. 1) Your machine is in livelock (ie overrun) 2) There is a problem with the interrupts Clearly you should know if 1) was occurring. With 2), it could be a driver or hardware problem or both. DT Hi, thanks for reply. The first case ( overrun ) is impossible, the server has (for now) very low traffic ( load is 0.00 almost all the time ). The second case is right answer. ;-) I suspect driver related problem. Before FreeBSD 6.0, there were Linux Debian and I didn`t mentioned any problem. I had there for several days FreeBSD 5.4 and watchdogs appear too. Vladimir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0: watchdog timeout
Hans Nieser wrote: Nicolas Blais wrote: On November 26, 2005 09:15 am, Hans Nieser wrote: A long, long time ago Vladimir Dvorak wrote: Hello, I have a problem with network card. From time to time kernel says sk0: watchdog timeout I just ran into the same issue. I have an ASUS A8N-SLI Deluxe in my desktop machine which runs FreeBSD 6.0+Xorg+Gnome. It has two on-board NICs, the nvidia one and a Marvel one. The nvidia was one big disaster and was giving me device timeouts so I never bothered with that one again. I have an sk0 too on one of my computer's onboard A8V-DX which will timeout once in a while too. I found a way to reduce down time by modifying my rc.conf to force 'full-duplex 100Mbps'. Now, even when it goes into a watchdog timeout, I quickly get back my link within that second. This is what my rc.conf line looks like: ifconfig_sk0=inet 192.168.1.100 media 100baseTX mediaopt full-duplex netmask 255.255.255.0 I found some other solution here: http://sources.zabbadoz.net/freebsd/if_sk.html There is recommended to use correct on-chip RAM size: 6. use correct on-chip RAM size; committed to HEAD http://lists.freebsd.org/pipermail/cvs-src/2004-November/035293.html Can some of you know how ? Thank you. Vladimir Dvorak ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0: watchdog timeout
Vladimir Dvorak wrote: I found some other solution here: http://sources.zabbadoz.net/freebsd/if_sk.html There is recommended to use correct on-chip RAM size: 6. use correct on-chip RAM size; committed to HEAD http://lists.freebsd.org/pipermail/cvs-src/2004-November/035293.html Can some of you know how ? I don't think that patch could solve anything in my case as it's pretty old and already included in FreeBSD 6.0, I think. Many thanks for that link though, it's got loads of info. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0: watchdog timeout
A long, long time ago Vladimir Dvorak wrote: Hello, I have a problem with network card. From time to time kernel says sk0: watchdog timeout I just ran into the same issue. I have an ASUS A8N-SLI Deluxe in my desktop machine which runs FreeBSD 6.0+Xorg+Gnome. It has two on-board NICs, the nvidia one and a Marvel one. The nvidia was one big disaster and was giving me device timeouts so I never bothered with that one again. - skc0: Marvell Gigabit Ethernet port 0xac00-0xacff mem 0xd4008000-0xd400bfff irq 17 at device 12.0 on pci5 skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) sk0: Marvell Semiconductor, Inc. Yukon on skc0 sk0: Ethernet address: 00:11:d8:99:3b:b0 miibus0: MII bus on sk0 e1000phy0: Marvell 88E1000 Gigabit PHY on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto - nve0: NVIDIA nForce MCP9 Networking Adapter port 0xb000-0xb007 mem 0xd500-0xd5000fff irq 22 at device 10.0 on pci0 nve0: Ethernet address 00:11:d8:99:39:be miibus1: MII bus on nve0 ukphy0: Generic IEEE 802.3u media interface on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nve0: Ethernet address: 00:11:d8:99:39:be nve0: [GIANT-LOCKED] - [EMAIL PROTECTED]:12:0: class=0x02 card=0x811a1043 chip=0x432011ab rev=0x13 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = '88E8001/8003/8010 Gigabit Ethernet Controller with Integrated PHY (copper)' class= network subclass = ethernet - [EMAIL PROTECTED]:10:0: class=0x068000 card=0x81411043 chip=0x005710de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 Ethernet Controller' class= bridge - Until now the Marvell one had worked flawlessly for me, until today, when I was moving 80GB of data to my server. It keeps crapping out with sk0: watchdog timeout and appears to take the whole desktop down with it, apps become unresponsive and Nautilus basically freezes. Bringing the interface down and up restores connectivity, unfortunately Nautilus won't continue copying files (despite it offering a Retry button, it just kept spewing errors) so having to manually figure out what was and wasn't copied over every 20GB or so is quickly becoming a pain in the behind. Looks like some PRs were filed on this issue but I guess they haven't been able to fix it (yet? - say yes please). It may also be worth noting that this NIC also lost connectivity in Windows XP from time to time forcing me to disable/enable it, so maybe the NIC itself is just garbage. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0: watchdog timeout
On November 26, 2005 09:15 am, Hans Nieser wrote: A long, long time ago Vladimir Dvorak wrote: Hello, I have a problem with network card. From time to time kernel says sk0: watchdog timeout I just ran into the same issue. I have an ASUS A8N-SLI Deluxe in my desktop machine which runs FreeBSD 6.0+Xorg+Gnome. It has two on-board NICs, the nvidia one and a Marvel one. The nvidia was one big disaster and was giving me device timeouts so I never bothered with that one again. I have an sk0 too on one of my computer's onboard A8V-DX which will timeout once in a while too. I found a way to reduce down time by modifying my rc.conf to force 'full-duplex 100Mbps'. Now, even when it goes into a watchdog timeout, I quickly get back my link within that second. This is what my rc.conf line looks like: ifconfig_sk0=inet 192.168.1.100 media 100baseTX mediaopt full-duplex netmask 255.255.255.0 Nicolas. -- FreeBSD 7.0-CURRENT #1: Sat Nov 19 12:36:29 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CLK01A PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc pgp1m2Euu5vqy.pgp Description: PGP signature
Re: sk0: watchdog timeout
Nicolas Blais wrote: On November 26, 2005 09:15 am, Hans Nieser wrote: A long, long time ago Vladimir Dvorak wrote: Hello, I have a problem with network card. From time to time kernel says sk0: watchdog timeout I just ran into the same issue. I have an ASUS A8N-SLI Deluxe in my desktop machine which runs FreeBSD 6.0+Xorg+Gnome. It has two on-board NICs, the nvidia one and a Marvel one. The nvidia was one big disaster and was giving me device timeouts so I never bothered with that one again. I have an sk0 too on one of my computer's onboard A8V-DX which will timeout once in a while too. I found a way to reduce down time by modifying my rc.conf to force 'full-duplex 100Mbps'. Now, even when it goes into a watchdog timeout, I quickly get back my link within that second. This is what my rc.conf line looks like: ifconfig_sk0=inet 192.168.1.100 media 100baseTX mediaopt full-duplex netmask 255.255.255.0 Thanks! Will give this a try ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0: watchdog timeout
Nicolas Blais wrote: On November 3, 2005 06:37 pm, martinko wrote: Vladimir Dvorak wrote: Hello, I have a problem with network card. From time to time kernel says sk0: watchdog timeout It has (probably) random behavior. I use FreeBSD 5.4-RELEASE-p8, motherboard is ASUS A8V Deluxe (AMD64, Athlon64XP 3200+) and internal network card from pciconf -v -l [EMAIL PROTECTED]:10:0: class=0x02 card=0x811a1043 chip=0x432011ab rev=0x13 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = '88E8001 Gigabit 32-bit Ethernet Controller with Integrated PHY' class= network subclass = ethernet This machine should be sent to serverhouse and I am not sure, if it is ready. :-( Can anyone tell me what is the solution ? To buy another netcard ? Thank you, Vladimir Dvorak ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] the same chip here and i see the messages from time to time too. not sure what's the problem or if there is any at all. so far card has been working alright, or at least i haven't noticed any issues. m. Same here too: sk0: watchdog timeout sk0: watchdog timeout sk0: watchdog timeout with occasional : sk0: discard frame w/o leading ethernet header (len 10 pkt len 10) sk0: discard frame w/o leading ethernet header (len 11 pkt len 11) Network is running fine, though sometimes accessing the internet takes 2-3 seconds (as if the DNS was not responding) but then is fine. Yes, the same feeling. This error is independend on load. I downloaded tens of GB and nothing happend, but usually after boot this error occures ( I do not know if it is really error). Tonight I tested small pings on this machine from several stations in network, no watchdog timeout message. Once I mentioned 1-2 seconds networking break, when I 'dmesg' immediatelly after that, the watchdog was there. Im not sure if I can put it as production server :-(. But I will try. ;-) Vladimir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0: watchdog timeout
Vladimir Dvorak wrote: Hello, I have a problem with network card. From time to time kernel says sk0: watchdog timeout It has (probably) random behavior. I use FreeBSD 5.4-RELEASE-p8, motherboard is ASUS A8V Deluxe (AMD64, Athlon64XP 3200+) and internal network card from pciconf -v -l [EMAIL PROTECTED]:10:0: class=0x02 card=0x811a1043 chip=0x432011ab rev=0x13 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = '88E8001 Gigabit 32-bit Ethernet Controller with Integrated PHY' class= network I have the same motherboard and ethernet chipset, and don't have these problems, so *maybe* there's some hardware problem with yours, or maybe I just don't load the ethernet as much. However, I have had numerous ethernet chips over the years which produced these errors every now and again, and I have always safely ignored them. Run some stress tests before you ship the machine, but if you get decent(*) performance then I'd just ship it without being concerned. --Alex (*) Decent, is of course not likely to be Gigabit! Try the nttcp port for measuring the performance you get; ftp performance will likely be limited by disk-read; and ssh is just rubbish on fast networks unless you install ssh-hpn port which fixes some problems and also adds the ability to not encrypt the data transfer (just the authentication) which is useful on closed-ish networks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0: watchdog timeout
Vladimir Dvorak wrote: Hello, I have a problem with network card. From time to time kernel says sk0: watchdog timeout It has (probably) random behavior. I use FreeBSD 5.4-RELEASE-p8, motherboard is ASUS A8V Deluxe (AMD64, Athlon64XP 3200+) and internal network card from pciconf -v -l [EMAIL PROTECTED]:10:0: class=0x02 card=0x811a1043 chip=0x432011ab rev=0x13 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = '88E8001 Gigabit 32-bit Ethernet Controller with Integrated PHY' class= network subclass = ethernet This machine should be sent to serverhouse and I am not sure, if it is ready. :-( Can anyone tell me what is the solution ? To buy another netcard ? Thank you, Vladimir Dvorak ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] the same chip here and i see the messages from time to time too. not sure what's the problem or if there is any at all. so far card has been working alright, or at least i haven't noticed any issues. m. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sk0: watchdog timeout
On November 3, 2005 06:37 pm, martinko wrote: Vladimir Dvorak wrote: Hello, I have a problem with network card. From time to time kernel says sk0: watchdog timeout It has (probably) random behavior. I use FreeBSD 5.4-RELEASE-p8, motherboard is ASUS A8V Deluxe (AMD64, Athlon64XP 3200+) and internal network card from pciconf -v -l [EMAIL PROTECTED]:10:0: class=0x02 card=0x811a1043 chip=0x432011ab rev=0x13 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = '88E8001 Gigabit 32-bit Ethernet Controller with Integrated PHY' class= network subclass = ethernet This machine should be sent to serverhouse and I am not sure, if it is ready. :-( Can anyone tell me what is the solution ? To buy another netcard ? Thank you, Vladimir Dvorak ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] the same chip here and i see the messages from time to time too. not sure what's the problem or if there is any at all. so far card has been working alright, or at least i haven't noticed any issues. m. Same here too: sk0: watchdog timeout sk0: watchdog timeout sk0: watchdog timeout with occasional : sk0: discard frame w/o leading ethernet header (len 10 pkt len 10) sk0: discard frame w/o leading ethernet header (len 11 pkt len 11) Network is running fine, though sometimes accessing the internet takes 2-3 seconds (as if the DNS was not responding) but then is fine. -- FreeBSD 7.0-CURRENT #0: Sat Oct 29 11:32:52 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CLK01A PGP? : http://www.clkroot.net/security/nb_root.asc pgpo1i6QGXkzr.pgp Description: PGP signature
