Re: dc0: watchdog timeout
To follow up on this, after switching from a dc0 to an fxp0 I finally managed to wedge my -current UP1000 with heavy CPU & NFS activity (starting up the linux mozilla). It is now speweing 'fxp0: device timeout' to the console (and inconveniently ignoring breaks on the serial console). So it appears that it is not dc specific (though it does seem to happen much more fequently 21143's) I guess its either alpha or SMPng specific.. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dc0: watchdog timeout
Motomichi Matsuzaki writes: > > At Mon, 23 Oct 2000 22:46:26 -0400 (EDT), > Andrew Gallatin <[EMAIL PROTECTED]> wrote: > > Anybody else seeing 'dc0: watchdog timeout' since SMPng integration? > > Yes I have. > > I have this several times before SMPng integration at a high load > situation. But, since the integration, it occurs frequently. I just switched out my tulip for an Intel EtherExpress Pro100B. I've had the machine sitting in a while 1 loop, rebuilding a debug kernel (which frequently triggered the dc0 watchdog reset). No problems after 3 hours, so I'm considering it "safe" It must be either a driver issue or something to do with tulips being sensative to not being serviced in a reasonable amount of time.. Cheers, Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dc0: watchdog timeout
At Mon, 23 Oct 2000 22:46:26 -0400 (EDT), Andrew Gallatin <[EMAIL PROTECTED]> wrote: > Anybody else seeing 'dc0: watchdog timeout' since SMPng integration? Yes I have. I have this several times before SMPng integration at a high load situation. But, since the integration, it occurs frequently. > links. I don't have tulip cards in any PCs, so it is hard for me to > tell if this is an alpha issue or an if_dc driver issue.. FreeBSD 5.0-CURRENT #15: Sat Sep 23 07:12:39 JST 2000 CPU: Pentium II/Pentium II Xeon/Celeron (451.03-MHz 686-class CPU) FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 > dc0: port 0x10100-0x1017f mem 0x41353100-0x4135317f irq >10 at device 9.0 on pci0 > dc0: interrupting at ISA irq 10 > dc0: Ethernet address: 00:00:f8:07:b6:45 > miibus0: on dc0 > dcphy0: on miibus0 > dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: port 0xd400-0xd4ff mem 0xe780-0xe78000ff irq 16 at device 15.0 on pci0 dc0: Ethernet address: 00:90:cc:a2:fa:82 miibus0: on dc0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto -- Motomichi Matsuzaki <[EMAIL PROTECTED]> Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
