Date: Fri, 17 Jul 2015 03:46:24 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 201642] panic: recent lockstat work resulting in boot time double fault on STABLE/HEAD Message-ID: <bug-201642-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201642 Bug ID: 201642 Summary: panic: recent lockstat work resulting in boot time double fault on STABLE/HEAD Product: Base System Version: 10.2-BETA1 Hardware: i386 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: jason.unovitch@gmail.com Ever since the recent lockstat improvements, my Soekris 6501 running i386 has been having a repeatable kernel panic at boot up. I normally running CURRENT, however after tracking the issue down I verified this is happening on 10.2-BETA1 as well as CURRENT. The panic I am seeing looks along the lines of this below and is repeatable on a revision with the lockstat work. The only way I have been able to boot on an impacted revision is by using safe boot via the boot loader menu. SMP: AP CPU #1 Launched! Timecounter "TSC" frequency 1600033960 Hz quality 1000 Fatal double fault: eip = 0xc1099873 esp = 0xe1fb8000 ebp = 0xe1fb8000 cpuid = 1; apic id = 01 panic: double fault cpuid = 1 KDB: stack backtrace: #0 0xc0b7a602 at kdb_backtrace+0x52 #1 0xc0b3b79b at vpanic+0x11b #2 0xc0b3b67b at panic+0x1b #3 0xc108736b at dblfault_handler+0xab Uptime: 11s Automatic reboot in 15 seconds - press a key on the console to abort Summary of tested revisions: stable/10 -- good -- r284994 stable/10 -- bad -- r284998, r285365 head -- good -- r284296, r284256, r284233, r284194 head -- bad -- r284297, r284309, r285143-r285155 (approx, this was when I initially ran into issue) The common ground has been the several lockstat improvement commit in r284297. https://svnweb.freebsd.org/base?view=revision&revision=284297 -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-201642-8>