> > > - either fix the driver
> > > or
> > > - disable the watchdog entirely.
> >
> > In principle you are soooo right. Just that it sometimes is HARD to fix
> > such long delays...
>
> That's why I said "disable the watchdog".
> But since the whole _point_ of watchdogging is to find places like this,
> when you paper over _these_ symptoms, you end up killing the whole idea.
>
> Which is why I'd suggest making it a more conscious decision: just turn
> off watchdog support. And if somebody needs watchdog support with a broken
> driver, maybe, just _maybe_, he'll find the energy to fix the frigging
> thing.
We had the same situation a while back (2.2.x, early 2.4.x era) with systems
that had (have, they still exist) a 1 second WD tied to the hard RESET line.
1 second with interrupts off == reboot. Let me tell you, we found a LOT of
places where there were problems. Network drivers, routing stuff, SCSI,
etc. We fixed some, and hacked around some in this same manner.
Now, if I have a chance to port Cobalt crap to 2.6, we'll see how many of
our changes were merged, in concept or in code.
Tim
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 07 2003 - 22:00:30 EST