Date: Sun, 15 Apr 2001 23:19:50 -0700 From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: "Forrest" <praxis@techpraxis.com>, "FreeBSD Questions" <freebsd-questions@FreeBSD.ORG> Subject: RE: Please help: -- sis0 : watchdog timeout? Message-ID: <004701c0c63d$3defbc00$1401a8c0@tedm.placo.com> In-Reply-To: <B6FD67B5.756E%praxis@techpraxis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Forrest >Sent: Saturday, April 14, 2001 2:35 AM >To: FreeBSD Questions >Subject: Re: Please help: -- sis0 : watchdog timeout? > > >On 4/12/01 1:54 AM, "Ted Mittelstaedt" <tedm@toybox.placo.com> is said to >have spake: > >> You don't say what model/type of switch you have which hinders >> troubleshooting. > >It is a Fore Systems ES-2810. However, this behaviour occurs no matter what >kind of port I plug the CAT5 cable into. The Switch doesn't hinder >troubleshooting (not sure why you said that?) > I said that on the off chance that the switch was a 10BaseT one and that you hadn't tested at all on a 100baseT port. >> But, first I'd try using ifconfig to lock both >> interfaces into 10BaseT half-duplex and see if the problem goes >> away or not. >I tried this, using the media options in ifconfig...timeout still occurs >when ports are both "active" and "10-base T UTP." > Oops - I meant both posts as in "the port on the sis0 and the port on the Switch." In short, try going into the Fore Systems management interface and try all of the port speeds - first try locking it into 10baseT half Duplex, then lock the FreeBSD system into 10BaseT half Duplex, then try full duplex on both the BSD box and the Fore box, then 100baseT half, then 100BaseT full. Obviouly the xl0 port has nothing to do with this problem, so don't mess with it. >I am still looking for help on this; Ted, thanks for your reply. >Again, I really appreciate any help anyone can render with this >problem. The >motherboard has the standard SiS 9000 ethernet chip on it, that is the LAN >controller for this on-board LAN port, so it makes sense that it uses the >'sis' driver. When I look online for clues as to how to >troubleshoot and fix >"watchdog timeout" errors on *BSDs and Linux, it looks like several things >can be the cause. I am pretty sure it is a hardware problem with >FreeBSD, if >someone could help me track it down I would be most grateful... > Fortunately, Ethernet cards are cheap, assuming you have the slot for it. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >Cheers >Forrest H. >> >> Ted Mittelstaedt tedm@toybox.placo.com >> Author of: The FreeBSD Corporate Networker's Guide >> Book website: http://www.freebsd-corp-net-guide.com >> >> >>> -----Original Message----- >>> From: owner-freebsd-questions@FreeBSD.ORG >>> [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Forrest >>> Sent: Thursday, April 12, 2001 1:00 AM >>> To: FreeBSD Questions >>> Subject: Please help: -- sis0 : watchdog timeout? >>> >>> >>> A Call for help from the excellence of this list: >>> >>> My FreeBSD box is giving me TROUBLE.... If someone could detect what is >>> wrong, and if it is a bug, please tell me how to submit it to the kernel >>> people... >>> >>> I have two ethernet interfaces, a 3Com 905C-TX that is flawless >so far, it >>> uses the "xl" driver, and an onboard LAN port that was autodetected at >>> FreeBSD install and assigned the "sis" driver. >>> >>> Description of problem: seconds after pluggin' my second ethernet >>> interface >>> into my switch, (also occurs plugged into a Netgear 10BT hub), no matter >>> what cat-5 cable I use(I switched out cables furiously), I get >this message >>> on the console: >>> >>> Mymachine /kernel: sis0: watchdog timeout >>> Then ping yields: >>> Ping: sendto: Host is down >>> (repeats until Ctrl-C) >>> >>> Description of freebsd system: >>> FreeBSD 4.3-BETA, running kernel compiled from sources. >>> >>> Description of hardware: >>> Processor: Athlon 600 MHz >>> Motherboard: ECS K7ASA w/ AGP slot, two PCI Bus Master UDMA >ports, 2 ATAPI >>> ea. >>> RAM: 256 MB PC 100 SDRAM, 3.3V unbuffered DIMMS. >>> ---> Embedded Network interface: >>> >>> Here is the results of /sbin/dmesg: >>> >>> Timecounter "i8254" frequency 1193182 Hz >>> Timecounter "TSC" frequency 598839452 Hz >>> CPU: AMD Athlon(tm) Processor (598.84-MHz 686-class CPU) >>> Origin = "AuthenticAMD" Id = 0x621 Stepping = 1 >>> >>> Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE, >>> MCA,CMOV, >>> PAT,PSE36,MMX,FXSR> >>> AMD Features=0xc0400000<AMIE,DSP,3DNow!> >>> real memory = 134217728 (131072K bytes) >>> config> di sn0 >>> config> di lnc0 >>> config> di ie0 >>> config> di fe0 >>> config> di cs0 >>> config> q >>> avail memory = 126726144 (123756K bytes) >>> Preloaded elf kernel "kernel" at 0xc03d5000. >>> Preloaded userconfig_script "/boot/kernel.conf" at 0xc03d509c. >>> Pentium Pro MTRR support enabled >>> md0: Malloc disk >>> npx0: <math processor> on motherboard >>> npx0: INT 16 interface >>> pcib0: <AMD-751 host to PCI bridge> on motherboard >>> pci0: <PCI bus> on pcib0 >>> pcib1: <AMD-751 PCI-PCI (AGP) bridge> at device 1.0 on pci0 >>> pci1: <PCI bus> on pcib1 >>> pci1: <ATI Mach64-GB graphics accelerator> at 5.0 irq 11 >>> isab0: <PCI to ISA bridge (vendor=1022 device=7408)> at device >7.0 on pci0 >>> isa0: <ISA bus> on isab0 >>> atapci0: <AMD 756 ATA66 controller> port 0xf000-0xf00f at device >>> 7.1 on pci0 >>> ata0: at 0x1f0 irq 14 on atapci0 >>> ata1: at 0x170 irq 15 on atapci0 >>> chip1: <PCI to Other bridge (vendor=1022 device=740b)> at device >>> 7.3 on pci0 >>> ohci0: <AMD-756 USB Controller> mem 0xefffe000-0xefffefff irq 9 >at device >>> 7.4 on pci0 >>> usb0: OHCI version 1.0, legacy support >>> usb0: SMM does not respond, resetting >>> usb0: <AMD-756 USB Controller> on ohci0 >>> usb0: USB revision 1.0 >>> uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >>> uhub0: 4 ports with 4 removable, self powered >>> xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xd400-0xd47f mem >>> 0xefffdf80-0xefffdfff irq 5 at device 10.0 on pci0 >>> xl0: Ethernet address: 00:01:02:87:04:af >>> miibus0: <MII bus> on xl0 >>> xlphy0: <3c905C 10/100 internal PHY> on miibus0 >>> xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >>> pci0: <unknown card> (vendor=0x14f1, dev=0x1036) at 11.0 irq 9 >>> ahc0: <Adaptec 2910/15/20/30C SCSI adapter> port 0xdc00-0xdcff mem >>> 0xeffff000-0xefffffff irq 10 at device 12.0 on pci0 >>> ahc0: Host Adapter Bios disabled. Using default SCSI device parameters >>> aic7850: Single Channel A, SCSI Id=7, 3/255 SCBs >>> sis0: <SiS 900 10/100BaseTX> port 0xcc00-0xccff mem >0xefffc000-0xefffcfff >>> irq 9 >>> at device 14.0 on pci0 >>> sis0: Ethernet address: 00:d0:09:53:6f:82 >>> miibus1: <MII bus> on sis0 >>> ukphy0: <Generic IEEE 802.3u media interface> on miibus1 >>> ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >>> pci0: <unknown card> (vendor=0x13f6, dev=0x0111) at 15.0 irq 10 >>> fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq >2 on isa0 >>> fdc0: FIFO enabled, 8 bytes threshold >>> fd0: <1440-KB 3.5" drive> on fdc0 drive 0 >>> atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 >>> atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 >>> kbd0 at atkbd0 >>> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem >0xa0000-0xbffff on isa0 >>> sc0: <System console> at flags 0x100 on isa0 >>> sc0: VGA <16 virtual consoles, flags=0x300> >>> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 >>> sio0: type 16550A >>> sio1 at port 0x2f8-0x2ff irq 3 on isa0 >>> sio1: type 16550A >>> ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 >>> ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode >>> plip0: <PLIP network interface> on ppbus0 >>> lpt0: <Printer> on ppbus0 >>> lpt0: Interrupt-driven port >>> ppi0: <Parallel I/O> on ppbus0 >>> IP Filter: v3.4.16 initialized. Default = pass all, Logging = enabled >>> ad0: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata0-master UDMA66 >>> acd0: CDROM <TOSHIBA CD-ROM XM-6102B> at ata1-master using PIO3 >>> Waiting 5 seconds for SCSI devices to settle >>> Mounting root from ufs:/dev/ad0s2a >>> xl0: promiscuous mode enabled >>> sis0: watchdog timeout >>> sis0: watchdog timeout >>> >>> and the result of ifconfig: >>> xl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 >>> inet <<ipaddress>> netmask 0xffffff00 broadcast 64.221.116.255 >>> inet6 fe80::201:2ff:fe87:4af%xl0 prefixlen 64 scopeid 0x1 >>> ether 00:01:02:87:04:af >>> media: autoselect (10baseT/UTP) status: active >>> supported media: autoselect 100baseTX <full-duplex> 100baseTX >>> 10baseT/UTP <full-duplex> 10baseT/UTP 100baseTX <hw-loopback> >>> sis0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 >>> inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 >>> inet6 fe80::2d0:9ff:fe53:6f82%sis0 prefixlen 64 scopeid 0x2 >>> ether 00:d0:09:53:6f:82 >>> media: autoselect (100baseTX <full-duplex>) status: active >>> supported media: autoselect 100baseTX <full-duplex> 100baseTX >>> 10baseT/UTP <full-duplex> 10baseT/UTP none >>> lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500 >>> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 >>> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 >>> inet6 ::1 prefixlen 128 >>> inet 127.0.0.1 netmask 0xff000000 >>> ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 >>> faith0: flags=8000<MULTICAST> mtu 1500 >>> gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 >>> gif1: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 >>> gif2: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 >>> gif3: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 >>> >>> Any other details that help in troubleshooting can be provided >on request. >>> Thank you, >>> Forrest H. >>> >>> >>> To Unsubscribe: send mail to majordomo@FreeBSD.org >>> with "unsubscribe freebsd-questions" in the body of the message >>> >> >> > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004701c0c63d$3defbc00$1401a8c0>