Date: Mon, 21 Jul 2008 10:22:03 -0700 From: Marcel Moolenaar <xcllnt@mac.com> To: Hiroki Sato <hrs@FreeBSD.org> Cc: freebsd-ia64@FreeBSD.org Subject: Re: panic on HP rx1600 Message-ID: <98D324EF-328F-4C23-97FE-83B16EC28B04@mac.com> In-Reply-To: <20080721.014513.25214113.hrs@allbsd.org> References: <20080720.210503.01730835.hrs@allbsd.org> <CB80C6F8-02CF-4E4F-82A1-2E0E0DFD910D@mac.com> <20080721.003831.44053407.hrs@allbsd.org> <20080721.014513.25214113.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 20, 2008, at 9:45 AM, Hiroki Sato wrote: > Hiroki Sato <hrs@freebsd.org> wrote > in <20080721.003831.44053407.hrs@allbsd.org>: > > hr> Marcel Moolenaar <xcllnt@mac.com> wrote > hr> in <CB80C6F8-02CF-4E4F-82A1-2E0E0DFD910D@mac.com>: > hr> > hr> xc> If you don't have INVARIANTS, could you add it to your kernel > hr> xc> configuration. I've seen kernel panics without INVARIANTS > hr> xc> after GCC 4 was imported. Also, if you're using ULE, then > hr> xc> please switch to 4BSD. > hr> > hr> Okay, thanks. I will do and report what is changed. The > kernel was > hr> the same configuration as GENERIC. > > I confirmed that adding INVARIANTS prevents it from triggering a > panic. Hmm, do you know exactly which part of the tree is the cause, > or should we narrow down this issue? I haven't had the time to go to the bottom of this. This is not to say that I think we should narrow it down. Looking at the context (unlocking, turnstiles), it could be related to atomic operations and I already fixed a GCC bug in that respect: src/sys/ia64/include/atomic.h, rev 1.14 It would be extreme luck if that would also fix the panic, but we might as well try.... Hmmm, I'd better MFC it... -- Marcel Moolenaar xcllnt@mac.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?98D324EF-328F-4C23-97FE-83B16EC28B04>