From owner-freebsd-alpha Wed Jun 13 12:55: 8 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 289E237B407; Wed, 13 Jun 2001 12:55:06 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f5DJsS142230; Wed, 13 Jun 2001 12:54:28 -0700 (PDT) (envelope-from jhb@FreeBSD.org) 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: <15143.49115.393545.131197@grasshopper.cs.duke.edu> Date: Wed, 13 Jun 2001 12:54:33 -0700 (PDT) From: John Baldwin To: Andrew Gallatin Subject: Re: More followup... Cc: wilko@FreeBSD.org, freebsd-alpha@FreeBSD.org, mjacob@feral.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 13-Jun-01 Andrew Gallatin wrote: > > This is different than Wilko's panic. At least with my kernel, it > maps to this: It would be helpful to know what the actual trap is. Sticking a 'printtrap' in at the top of trap to output the trap details would be very helpful. > (gdb) l * hardclock+0x308 > 0xfffffc000043a608 is in hardclock (../../kern/kern_clock.c:215). > 210 * Process callouts at a very low cpu priority, so we don't > keep the > 211 * relatively high clock interrupt priority any longer than > necessary. > 212 */ > 213 mtx_lock_spin(&callout_lock); > 214 ticks++; > 215 if (TAILQ_FIRST(&callwheel[ticks & callwheelmask]) != NULL) { > 216 need_softclock = 1; > 217 } else if (softticks + 1 == ticks) > 218 ++softticks; > 219 mtx_unlock_spin(&callout_lock); > > > This is well past Wilko's tlaser panic & looks like it could be a sign > of the general pmap corruption brought on by the vm_mtx fiasco.... > I'll have to push a machine here hard today an see where it blows up > for me. I don't think it's general pmap corruption, but I could be wrong. Almost everything is back under Giant that wasn't before. My current vm.patch moves pagedaemon and vmdaemon back under Giant, so the only thing that possibly should move back under Giant is the stuff in trap() that was under Giant before. I'll look at this in a bit. The thing is that if we still have these problems when all of vm is under Giant, then it's not a vm_mtx problem. :( -- 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