Re: * watchdog timeout (Was: dc0: watchdog timeout)
Warner Losh wrote: In message [EMAIL PROTECTED] [EMAIL PROTECTED] writes: : Probably not related at all, but on -current I am seeing: : xe0: watchdog timeout; resetting card : It happens just once, at boot time or after I insert the PC Card (Compaq : whatever). After that, everything works ok. Generally watchdog timeouts from pccard devices mean that your irqs are fubar'd. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message Mmm... I don't know, the PC card gets IRQ 3, which would be used by the IR COM2, which is disabled in the BIOS. In fact, I only get one such message, after that the xe0 is working great. Maybe it just takes too long to init? -- Loose bits sink chips. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: * watchdog timeout (Was: dc0: watchdog timeout)
In message [EMAIL PROTECTED] [EMAIL PROTECTED] writes: : Mmm... I don't know, the PC card gets IRQ 3, which would be used by the IR : COM2, which is disabled in the BIOS. In fact, I only get one such message, : after that the xe0 is working great. Maybe it just takes too long to init? If it works fine and at top speed after the init, then the watchdog is happening just a tad fast. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: * watchdog timeout (Was: dc0: watchdog timeout)
That's just what I figured out. I'm compiling a kernel with XE_DEBUG and will try increasing the if_timeout, let's see if this helps. I should be able to do this in a rather short time. Warner Losh wrote: In message [EMAIL PROTECTED] [EMAIL PROTECTED] writes: : Mmm... I don't know, the PC card gets IRQ 3, which would be used by the IR : COM2, which is disabled in the BIOS. In fact, I only get one such message, : after that the xe0 is working great. Maybe it just takes too long to init? If it works fine and at top speed after the init, then the watchdog is happening just a tad fast. -- Speak softly and carry a cellular phone. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: * watchdog timeout (Was: dc0: watchdog timeout)
In message [EMAIL PROTECTED] [EMAIL PROTECTED] writes: : Probably not related at all, but on -current I am seeing: : xe0: watchdog timeout; resetting card : It happens just once, at boot time or after I insert the PC Card (Compaq : whatever). After that, everything works ok. Generally watchdog timeouts from pccard devices mean that your irqs are fubar'd. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
* watchdog timeout (Was: dc0: watchdog timeout)
Probably not related at all, but on -current I am seeing: xe0: watchdog timeout; resetting card It happens just once, at boot time or after I insert the PC Card (Compaq whatever). After that, everything works ok. Andrew Gallatin wrote: 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 -- The computer revolution is over. The computers won. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: * watchdog timeout (Was: dc0: watchdog timeout)
At 18:24 30-10-00 +0100, you wrote: Probably not related at all, but on -current I am seeing: xe0: watchdog timeout; resetting card It happens just once, at boot time or after I insert the PC Card (Compaq whatever). After that, everything works ok. This is normal. It's bringing up the card when it's still not up. I agree this should be done earlier. I've been in that code before. I'll see if I can whip up a patch. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
