Date: Sun, 19 Sep 2010 20:38:35 -0700 From: Randall Stewart <rrs@lakerest.net> To: Lawrence Stewart <lstewart@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, avg@freebsd.org Subject: Re: Crash during boot of current (rev 212885) Message-ID: <29093DA9-BB4D-49B5-A20E-EDEDF6B5BAEC@lakerest.net> In-Reply-To: <4C96C772.4030006@freebsd.org> References: <EBB29842-99B9-4912-9E86-B5965F9C4201@lakerest.net> <4C96C772.4030006@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Lawrence: I am currently doing a binary search.. I know that 212660 shows the break. I am just about to try 212560 ;-) If that works I will update to 212646 and see if it works.. ;-) R On Sep 19, 2010, at 7:31 PM, Lawrence Stewart wrote: > Hiya Randall! > > On 09/20/10 08:56, Randall Stewart wrote: >> Hey all: >> >> I am now seeing a crash when I boot my Intel (in 64 bit more)... >> >> Its very early in the boot process.. and thus no crash dump ;-0 >> >> Its in >> >> netisr_start_swi() >> >> When it initializes netisr_mtx with a mtx_init() it crashes saying >> that netisr_mtx is unaligned... (the address ddb shows for >> netisr_mtx ends >> with c ... so it definitely is unaligned... >> >> Looking at the netisr_workstream structure (where netisr_mtx is) it >> appears to be in theory aligned right (follows 2 pointers)... so >> did something change the DP_CPU Define stuff to cause us to get >> unaligned >> access? >> >> Just curious... If I don't hear from anyone I will start backing >> things >> out 1 >> rev at a time until I find what did it I guess ;-) > > My guess would be r212647. Try backing that rev out and if it fixes > things, hopefully Andriy will have some thoughts on how to fix the > problem. Apologies if my guess is a red herring. > > Cheers, > Lawrence > ------------------------------ Randall Stewart 803-317-4952 (cell)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?29093DA9-BB4D-49B5-A20E-EDEDF6B5BAEC>