Date: Sun, 19 Jul 2015 11:33:07 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: "Herbert J. Skuhra" <herbert@oslo.ath.cx> Cc: svn-src-stable@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, svn-src-stable-10@FreeBSD.org Subject: Re: svn commit: r284998 - in stable/10: cddl/contrib/opensolaris/cmd/lockstat sys/kern sys/sys Message-ID: <55AB60C3.7000900@FreeBSD.org> In-Reply-To: <20150719051246.GB93016@oslo.ath.cx> References: <201507011015.t61AFoNo028793@svn.freebsd.org> <20150719050332.GA93016@oslo.ath.cx> <20150719051246.GB93016@oslo.ath.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19/07/2015 08:12, Herbert J. Skuhra wrote: > On Sun, Jul 19, 2015 at 07:03:32AM +0200, Herbert J. Skuhra wrote: >> On Wed, Jul 01, 2015 at 10:15:50AM +0000, Andriy Gapon wrote: >>> Author: avg >>> Date: Wed Jul 1 10:15:49 2015 >>> New Revision: 284998 >>> URL: https://svnweb.freebsd.org/changeset/base/284998 >>> >>> Log: >>> MFC r284297: several lockstat improvements >>> >>> Modified: >>> stable/10/cddl/contrib/opensolaris/cmd/lockstat/lockstat.c >>> stable/10/sys/kern/kern_mutex.c >>> stable/10/sys/kern/kern_rwlock.c >>> stable/10/sys/kern/kern_sx.c >>> stable/10/sys/sys/lockstat.h >>> Directory Properties: >>> stable/10/ (props changed) >> >> Yesterday I tried to upgrade my Soekris Net6501-70 from 10.2-PRERELEASE >> (r284583) to 10.2-BETA2 (r285646). All kernels after this commit fail to >> boot: >> >> SMP: AP CPU #1 Launched! >> >> Fatal double fault: >> eip = 0xc08b2e0f >> esp = 0xe0febfec >> ebp = 0xe0fec008 >> cpuid = 1; apic id = 01 >> panic: double fault >> cpuid = 1 >> KDB: stack backtrace: >> #0 0xc065ed62 at kdb_backtrace+0x52 >> #1 0xc06204eb at vpanic+0x11b >> #2 0xc06203cb at panic+0x1b >> #3 0xc08a5bbb at dblfault_handler+0xab >> Uptime: 2s >> Automatic reboot in 15 seconds - press a key on the console to abort >> Rebooting... >> cpu_reset: Restarting BSP >> timeout stopping cpus >> cpu_reset_proxy: Stopped CPU 1 >> >> I am running i386 on my Soekris. > > Sorry. There is already a PR for this issue: 201642! > Yes, the fix should be coming to stable/10 and stable/9 soon. Sorry about the problem. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55AB60C3.7000900>