Re[2]: FreeBSD 7.1-RC1 rl0 watchdog timeout with custom kernel
Any mistake? The rl driver supports some really terrible hardware, so I'm far from convinced that your custom kernel is causing the problems. Perhaps you could check by switching back to a GENERIC kernel for a while. It works well with GENERIC when I'm simply serfing the net or fetching ports. How can I test my network adapter under heavy load? connect to other computer and transfer files, one direction or both ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 7.1-RC1 rl0 watchdog timeout with custom kernel
Hello, all! I have Asus X51RL laptop with FreeBSD 7.1-RC1 installed. There were no troubles with GENERIC kernel, but when I've compiled custom kernel, rl ethernet driver tells to the console a lot of errors: rl0: link state changed to UP rl0: watchdog timeout rl0: watchdog timeout Any mistake? uname -a: FreeBSD asusbook.local 7.1-RC1 FreeBSD 7.1-RC1 #0: Mon Dec 15 08:40:11 MSK 2008 r...@asusbook.local:/usr/obj/usr/src/sys/GENERIC i386 pciconf -lv: r...@pci0:8:7:0:class=0x02 card=0x10451043 chip=0x813910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter' class = network subclass = ethernet dmesg from custom kernel (ASUSBOOK): Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-RC1 #2: Sun Dec 14 20:13:33 MSK 2008 r...@asusbook.local:/usr/obj/usr/src/sys/ASUSBOOK Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 550 @ 2.00GHz (1995.14-MHz 686-class CPU) Origin = GenuineIntel Id = 0x10661 Stepping = 1 Features=0xafebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE Features2=0xe31dSSE3,DTES64,MON,DS_CPL,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x2000LM AMD Features2=0x1LAHF real memory = 2012905472 (1919 MB) avail memory = 1964134400 (1873 MB) kbd1 at kbdmux0 ath_hal: 0.10.5.6 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417) acpi0: A.M.I OEMXSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 77f0 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_ec0: Embedded Controller: GPE 0x11 port 0x62,0x66 on acpi0 acpi_asus0: Unsupported Asus laptop: X51RL pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci_link3: BIOS IRQ 10 for 0.19.INTD is invalid pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0x7800-0x78ff mem 0x9000-0x9fff,0xf88f-0xf88f irq 5 at device 5.0 on pci1 pcib2: ACPI PCI-PCI bridge at device 4.0 on pci0 pci2: ACPI PCI bus on pcib2 ath0: Atheros 5424/2424 mem 0xf89f-0xf89f irq 11 at device 0.0 on pci2 ath0: [ITHREAD] ath0: WARNING: using obsoleted if_watchdog interface ath0: Ethernet address: 00:15:af:9e:d1:34 ath0: mac 14.2 phy 7.0 radio 10.2 pcib3: ACPI PCI-PCI bridge at device 5.0 on pci0 pci3: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge at device 6.0 on pci0 pci6: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge at device 7.0 on pci0 pci7: ACPI PCI bus on pcib5 atapci0: ATI IXP600 SATA300 controller port 0xe800-0xe807,0xe400-0xe403,0xe000-0xe007,0xdc00-0xdc03,0xd800-0xd80f mem 0xfebffc00-0xfebf irq 3 at device 18.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected ata2: ATA channel 0 on atapci0 ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 ata3: [ITHREAD] ata4: ATA channel 2 on atapci0 ata4: [ITHREAD] ata5: ATA channel 3 on atapci0 ata5: [ITHREAD] ohci0: OHCI (generic) USB controller mem 0xfebfe000-0xfebfefff irq 11 at device 19.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: OHCI (generic) USB controller mem 0xfebfd000-0xfebfdfff irq 5 at device 19.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: OHCI (generic) USB controller on ohci1 usb1: USB revision 1.0 uhub1: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 uhub1: 2 ports with 2 removable, self powered ohci2: OHCI (generic) USB controller mem 0xfebfc000-0xfebfcfff irq 4 at device 19.2 on pci0 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb2: OHCI version 1.0, legacy support usb2: OHCI (generic) USB controller on ohci2 usb2: USB revision 1.0 uhub2: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb2 uhub2: 2 ports with 2 removable, self powered ohci3: OHCI (generic) USB controller mem 0xfebfb000-0xfebfbfff irq 5 at device 19.3 on pci0 ohci3: [GIANT-LOCKED] ohci3: [ITHREAD] usb3: OHCI version 1.0, legacy support usb3: OHCI (generic) USB controller on ohci3 usb3: USB revision 1.0 uhub3: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb3 uhub3: 2 ports with 2 removable, self powered ohci4: OHCI (generic) USB controller mem 0xfebfa000-0xfebfafff irq 4 at device 19.4 on pci0 ohci4: [GIANT-LOCKED] ohci4: [ITHREAD
Re: FreeBSD 7.1-RC1 rl0 watchdog timeout with custom kernel
On Mon, Dec 15, 2008 at 10:31:16AM +0300, Gennady Kudryashoff wrote: Hello, all! I have Asus X51RL laptop with FreeBSD 7.1-RC1 installed. There were no troubles with GENERIC kernel, but when I've compiled custom kernel, rl ethernet driver tells to the console a lot of errors: rl0: link state changed to UP rl0: watchdog timeout rl0: watchdog timeout Any mistake? Have you looked at the manual page for this driver? (try running 'man rl' in a (x-)terminal). I quote: rl%d: watchdog timeout The device has stopped responding to the network, or there is a problem with the network connection (cable). I recently dumped an rl based card because it didn't work properly (upload speed sucked). Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpgUxb2EOX9s.pgp Description: PGP signature
Re: FreeBSD 7.1-RC1 rl0 watchdog timeout with custom kernel
Gennady Kudryashoff glothlor...@mail.ru writes: Hello, all! I have Asus X51RL laptop with FreeBSD 7.1-RC1 installed. There were no troubles with GENERIC kernel, but when I've compiled custom kernel, rl ethernet driver tells to the console a lot of errors: rl0: link state changed to UP rl0: watchdog timeout rl0: watchdog timeout Any mistake? The rl driver supports some really terrible hardware, so I'm far from convinced that your custom kernel is causing the problems. Perhaps you could check by switching back to a GENERIC kernel for a while. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re[2]: FreeBSD 7.1-RC1 rl0 watchdog timeout with custom kernel
From Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org: rl0: link state changed to UP rl0: watchdog timeout rl0: watchdog timeout Any mistake? The rl driver supports some really terrible hardware, so I'm far from convinced that your custom kernel is causing the problems. Perhaps you could check by switching back to a GENERIC kernel for a while. It works well with GENERIC when I'm simply serfing the net or fetching ports. How can I test my network adapter under heavy load? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
kernel: rl0: watchdog timeout
Since I upgraded to version 6, my server has frozen under heavy network traffic three times. It ran happily for months on various versions of 5. Same hardware, same configuration. There was never anything in /var/log/messages until this last time. This time I found: kernel: rl0: watchdog timeout I don't know what it's trying to tell me, and I don't know if it's a cause or an effect. This is 6.0-STABLE as of late Sunday night. i386. rl0 is my WAN-side interface. vr0 is my internal interface. This machine runs DNS, email, web, NFS host, and several other services. It uses pf with altq. I don't think the system is panicking. It doesn't reboot. It may be freezing. It becomes unresponsive on both network interfaces. When the incident occurs, there's always a lot of simple TCP/IP traffic that's just passing through the box (not NFS, email, web, or anything the box provides on its own) and my first response is to hit the reset button to get it going again. What should I look for? The handbook says to check cables, and they seem fine. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel: rl0: watchdog timeout
On Wed, 23 Nov 2005, Luke Dean wrote: Since I upgraded to version 6, my server has frozen under heavy network traffic three times. It ran happily for months on various versions of 5. Same hardware, same configuration. There was never anything in /var/log/messages until this last time. This time I found: kernel: rl0: watchdog timeout I don't know what it's trying to tell me, and I don't know if it's a cause or an effect. This is 6.0-STABLE as of late Sunday night. i386. rl0 is my WAN-side interface. vr0 is my internal interface. This machine runs DNS, email, web, NFS host, and several other services. It uses pf with altq. I have seen this once about two years ago. It went away, after I changed the NIC (realtek aren't high quality anyway). Regards, Uli. I don't think the system is panicking. It doesn't reboot. It may be freezing. It becomes unresponsive on both network interfaces. When the incident occurs, there's always a lot of simple TCP/IP traffic that's just passing through the box (not NFS, email, web, or anything the box provides on its own) and my first response is to hit the reset button to get it going again. What should I look for? The handbook says to check cables, and they seem fine. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] * * Peter Ulrich Kruppa - Wuppertal - Germany * * ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rl0: watchdog timeout
On Friday 17 December 2004 09:35, Nico Meijer wrote: I don't (and won't, unless forced) use Intel NICs, so I cannot speak of them. I've had the very unpleasant experience of having had to deal with a fierce network boost on a RealTek 8139 (don't ask...) in a linux box. It meant the nic (and thus the machine) was unavailable for 15 minutes. Other machines (which were not mine) which experienced the boost, were humming along nicely. So thanks, I'll pay $50 extra for the nic. Is there anything more than high reliability in Intel/3COM NICs? Do they produce less interrupts? I've heard rumors that they do some packet processing themselves thus offloading CPU. Is that true? If so, where can I check that in kernel source? -- ...python is just now at 2.4? perl is 3.4 better! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rl0: watchdog timeout
Hi Dmitry, Are we straying OT yet? I guess so, you've been warned. We have tons of them working on servers, routers and desktops because they are cheap (some beers are more expensive). You are comparing cheap nics with beer? I'll take that beer, thanks! ;-) I like the analogy, btw. Cheap beer s*cks most of the time and gives you headaches, whereas quality beers (I happen to particularly like Duvel, Grimbergen, Alfa) supply richer taste and gives you less or no headache (drink the yeast). In summary: good quality beers amount to a better user experience. Same goes with nics, imho. There is no real difference between Realtek and Intel NICs when they work (even for most servers). I don't (and won't, unless forced) use Intel NICs, so I cannot speak of them. I've had the very unpleasant experience of having had to deal with a fierce network boost on a RealTek 8139 (don't ask...) in a linux box. It meant the nic (and thus the machine) was unavailable for 15 minutes. Other machines (which were not mine) which experienced the boost, were humming along nicely. So thanks, I'll pay $50 extra for the nic. Decent nics give me no headaches. Replacing cheaper ones (this includes onboard vr) with decent nics, makes me sleep well at night. Just my experience... Nico ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rl0: watchdog timeout
On Thursday 16 December 2004 04:36, Mike Jeays wrote: I have no first hand experience with this particular problem, but it's almost common knowledge RealTek nics are great because they are cheap, not because they are of good quality. The phrase piece of crap has been uttered more than once in relation to these nics. I have three of them, and have had no trouble at all so far, in a low-activity home network. I wouldn't buy them for servers at work, though. We have tons of them working on servers, routers and desktops because they are cheap (some beers are more expensive). There is no real difference between Realtek and Intel NICs when they work (even for most servers). I've seen only 3 or 4 broken rl's in last four years. If your rl0 gets broken, just replace it and forget about it. -- ...python is just now at 2.4? perl is 3.4 better! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
rl0: watchdog timeout
Good day! I know, this question is famous, but i can't handle it myself. The problem is: After some time my realtek card becomes unresponsible. It happens because of buffer overflow. I tried ping -f xxx. 15 seconds later, the kernel says that rl0: watchdog timeout. I can't send files more then 100MB via network. This problem is because of my PC configuration - Motherboard GB K8N, chipset nforce 3. Unfortunately, even FreeBSD 5.3 can't handle it (but it's better then 5.2.1). Maybe someone has already met this problem? Thank you! Good luck. P.S. Sorry for my english. :) P.P.S. I tried 4 realtek cards in different slots and one 3com. :( ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rl0: watchdog timeout
Hi Andrew, Warning: no definitive answer ahead. After some time my realtek card becomes unresponsible. It happens because of buffer overflow. I tried ping -f xxx. 15 seconds later, the kernel says that rl0: watchdog timeout. I can't send files more then 100MB via network. This problem is because of my PC configuration - Motherboard GB K8N, chipset nforce 3. Unfortunately, even FreeBSD 5.3 can't handle it (but it's better then 5.2.1). Maybe someone has already met this problem? Thank you! I have no first hand experience with this particular problem, but it's almost common knowledge RealTek nics are great because they are cheap, not because they are of good quality. The phrase piece of crap has been uttered more than once in relation to these nics. Can you get your hands on any gigabit nics? (I've been using sk based chips with OpenBSD lately and they've been performing great under all circumstances so far.) P.S. Sorry for my english. :) Don't be, it's fine. Bye... Nico ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rl0: watchdog timeout
I have no first hand experience with this particular problem, but it's almost common knowledge RealTek nics are great because they are cheap, not because they are of good quality. The phrase piece of crap has been uttered more than once in relation to these nics. I have three of them, and have had no trouble at all so far, in a low-activity home network. I wouldn't buy them for servers at work, though. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rl0: watchdog timeout
On Wed, 15 Dec 2004 22:08:24 +0300, Andrew [EMAIL PROTECTED] wrote: Good day! I know, this question is famous, but i can't handle it myself. The problem is: After some time my realtek card becomes unresponsible. It happens because of buffer overflow. I tried ping -f xxx. 15 seconds later, the kernel says that rl0: watchdog timeout. I can't send files more then 100MB via network. This problem is because of my PC configuration - Motherboard GB K8N, chipset nforce 3. Unfortunately, even FreeBSD 5.3 can't handle it (but it's better then 5.2.1). Maybe someone has already met this problem? Looking around Google a bit, it looks like many people have been able to get the timeouts to go away by disabling PnP OS in the BIOS. Do you have that set to Yes? If so, try disabling it, and see if it helps any. -- Joshua Lokken Open Source Advocate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
