From owner-freebsd-hackers Sun Jun 1 22:44:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA28490 for hackers-outgoing; Sun, 1 Jun 1997 22:44:33 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA28485 for ; Sun, 1 Jun 1997 22:44:29 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id WAA29447; Sun, 1 Jun 1997 22:46:00 -0700 (PDT) Message-Id: <199706020546.WAA29447@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Michael Smith cc: hackers@FreeBSD.ORG Subject: Re: weird scheduler crash (2.2) In-reply-to: Your message of "Mon, 02 Jun 1997 14:34:54 +0930." <199706020504.OAA18291@genesis.atrad.adelaide.edu.au> From: David Greenman Reply-To: dg@root.com Date: Sun, 01 Jun 1997 22:46:00 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >calltrap() at calltrap+0x15 >--- trap 0xc, eip = 0xf0117408, esp = 0xefbffe84, ebp = 0xefbffe88 --- >_unsleep(f0d0cc00) at _unsleep+0x48 >_selwakeup(f0214348) at _selwakeup+0x76 >_mdsiointr(0,10,f020f9dc,118,ffffffff) at _mdsiointr+0x184 >_Xfastintr10(f020f9dc,118,f011cb84,b,f01f5748) at _Xfastintr10+0x17 >_select(f0d0cc00,efbfff94,efbfff84) at _select+0x2e2 >_syscall(27,27,4,4,efbf77d4) at _syscall+0x127 >_Xsyscall() at _Xsyscall+0x35 >--- syscall 0x5d, eip = 0x7c945, esp = 0xefbf7568, ebp = efbf77d4 --- > >have. It looks like the driver (mdsio) took an interrupt during a >select syscall which in turn resulted in the driver trying to wake the >selecting process up again. What is mdsio? It looks like it is configured as a "fast" interrupt handler, but is breaking the rules by calling the wakeup code. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project