From owner-freebsd-alpha Thu Mar 15 12:34:55 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BC7EE37B719; Thu, 15 Mar 2001 12:34:52 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA19075; Thu, 15 Mar 2001 12:34:55 -0800 Date: Thu, 15 Mar 2001 12:34:51 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.org Subject: Re: Deadlocks, whee! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > On 15-Mar-01 Matthew Jacob wrote: > > btw- it's been true for quite some time that ithreads seem to get dropped and > > not addressed- at least I think that this might be what would explain isp > > timeouts during makeworlds. > > Hmmmmmmmm. When an interrupt comes in we always mark it as needing to be > serviced before we grab the scheduler lock, and in the main ithread loop > we always check that flag after getting the scheduler lock before we > switch out. That _should_ mean that interrupts shouldn't be lost. Indeed! > > > When you deadlock'd your alpha, did you go and brew a cup of tea? What's your > > quantum for determining deadlock? > > No interrupts. I.e. ctrl-alt-esc doesn't work, pings are dropped, etc. I > think it locked up durng an overnight buildworld and I reset it the next day. Hmm... The FreeBSD portion of what I do got swapped out to the /dev/drum, but it's due back in early next week. I'll see where we are then. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message