From owner-freebsd-alpha Thu Dec 14 11: 4:37 2000 From owner-freebsd-alpha@FreeBSD.ORG Thu Dec 14 11:04:34 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 6E62737B400 for ; Thu, 14 Dec 2000 11:04:34 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBEJ4OE80187; Thu, 14 Dec 2000 11:04:24 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.0) id eBEJ3a040023; Thu, 14 Dec 2000 11:03:36 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 14 Dec 2000 11:03:36 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Matthew Jacob Subject: RE: mutex/ithread jitters? Cc: alpha@FreeBSD.ORG Sender: jhb@foo.osd.bsdi.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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 -- 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