From owner-freebsd-alpha Sun Sep 24 14: 5:17 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id AEC4337B42C for ; Sun, 24 Sep 2000 14:05:13 -0700 (PDT) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id OAA95724; Sun, 24 Sep 2000 14:07:37 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id OAA53607; Sun, 24 Sep 2000 14:06:56 -0700 (PDT) (envelope-from john) Message-Id: <200009242106.OAA53607@john.baldwin.cx> 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: Sun, 24 Sep 2000 14:06:56 -0700 (PDT) From: John Baldwin To: Doug Rabson Subject: RE: Ithreads kernel weirdness Cc: alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 24-Sep-00 Doug Rabson wrote: > On Fri, 22 Sep 2000, John Baldwin wrote: > >> >> On 20-Sep-00 John Baldwin wrote: >> > I suppose many of you are wondering why there haven't been any >> > recent commits of ithreads for the alpha as promised. The reason >> > is that I can't get a plain kernel to boot. My test kernel with >> >> ... >> >> Ok, status update: I know have an almost fully MI softinterrupt >> thread which works fine on UP and SMP i386. It also seems to work >> fine with a normal kernel with interrupt threads on the alpha. I >> have one last bug to track down (we are grabbing shed_lock with >> interrupts disabled at some point late in the sysinit right before >> init forks, probably the first time we grab the sched_lock). >> Currently my running kernel is hacking around it by always assuming >> the saved ipl in a spin mutex is ALPHA_PSL_IPL_0. :-P >> >> Once I track this last bug down I'll update the alpha.ithreads.patch >> so you all can test it and help fine other bugs. We also are still >> in need of some low-level PCI interrupt enable/disable code for two >> of the PCI chipsets. > > Does this fix the hang you were seeing before? I'm hoping its the same > problem which was hanging the the rawhide when I was trying to get the > ithreads changes to dxlpx to work. Yes. Actually, it looks like the kproc's (syncer, for example) are starting off with a saved PSR that has an IPL != 0 in them. I'm going to be looking at this some more today. -- 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