Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Dec 2000 11:03:36 -0800 (PST)
From:      John Baldwin <jhb@FreeBSD.ORG>
To:        Matthew Jacob <mjacob@feral.com>
Cc:        alpha@FreeBSD.ORG
Subject:   RE: mutex/ithread jitters?
Message-ID:  <XFMail.001214110336.jhb@FreeBSD.org>
In-Reply-To: <Pine.LNX.4.21.0012141032090.28426-100000@zeppo.feral.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On 14-Dec-00 Matthew Jacob wrote:
> 
> Since I (and maybe only I :-)) have gotten a 4100 up and running, I've been
> experiencing the following two behaviours:
> 
> Periodic messages like:
> 
> (da1:isp0:0:3:0): isp0: watchdog timeout (cf, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (21, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (9, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (65, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (c8, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (6e, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (1a, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (2, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (ee, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (cb, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (d4, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (d6, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (c8, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (89, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (56, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (19, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (ec, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (91, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (e0, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (50, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (77, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (5b, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (5, 0)
> (da1:isp0:0:3:0): isp0: watchdog timeout (c3, 0)
> 
> 
> and
> 
> 'freezes' while rlogin'd in.
> 
> 
> Has anyone else seen anything like this? The former, which really shouldn't
> happen at all at all (and doesn't under 4.2 in the same framework) indicates
> a
> completely lost interrupt. The latter I'm not sure about, but it could be the
> same.

Sounds like lost interrupts.  Possibly the interrupt isn't being enabled
properly after the ithread finishes running the handler.

> -matt

-- 

John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.001214110336.jhb>