Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 18 Mar 2014 15:27:17 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        freebsd-stable@freebsd.org
Cc:        Kevin Oberman <rkoberman@gmail.com>, ray@freebsd.org
Subject:   Re: Clock issues and crash on resume on 10-Stable r263062M
Message-ID:  <201403181527.17100.jhb@freebsd.org>
In-Reply-To: <CAN6yY1seOSacdXY3RKOgEdY_v%2BzD=vqMAfnsXH96Ft8w%2BOoJew@mail.gmail.com>
References:  <CAN6yY1seOSacdXY3RKOgEdY_v%2BzD=vqMAfnsXH96Ft8w%2BOoJew@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, March 15, 2014 3:44:46 pm Kevin Oberman wrote:
> 2. The time does not update after resume. After about 2 seconds, ehe system
> crashes.
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address   = 0x30
> fault code              = supervisor read data, page not present
> instruction pointer     = 0x20:0xffffffff808c9ef3
> stack pointer           = 0x28:0xfffffe00f13548e0
> frame pointer           = 0x28:0xfffffe00f13549b0
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 12 (swi4: clock)
> trap number             = 12
> panic: page fault
> cpuid = 0
> KDB: stack backtrace:
> #0 0xffffffff808ed460 at kdb_backtrace+0x60
> #1 0xffffffff808b4e35 at panic+0x155
> #2 0xffffffff80c97022 at trap_fatal+0x3a2
> #3 0xffffffff80c972f9 at trap_pfault+0x2c9
> #4 0xffffffff80c96a8b at trap+0x5bb
> #5 0xffffffff80c7dd42 at calltrap+0x8
> #6 0xffffffff808ca304 at softclock+0x94
> #7 0xffffffff8088929b at intr_event_execute_handlers+0xab
> #8 0xffffffff808896e6 at ithread_loop+0x96
> #9 0xffffffff80886f4a at fork_exit+0x9a
> #10 0xffffffff80c7e27e at fork_trampoline+0xe
> [...]
> #0  doadump (textdump=<value optimized out>) at pcpu.h:219
> 219     pcpu.h: No such file or directory.
>         in pcpu.h
> (kgdb) #0  doadump (textdump=<value optimized out>) at pcpu.h:219
> #1  0xffffffff808b4ab0 in kern_reboot (howto=260)
>     at /usr/src/sys/kern/kern_shutdown.c:452
> #2  0xffffffff808b4e74 in panic (fmt=<value optimized out>)
>     at /usr/src/sys/kern/kern_shutdown.c:759
> #3  0xffffffff80c97022 in trap_fatal (frame=<value optimized out>,
>     eva=<value optimized out>) at /usr/src/sys/amd64/amd64/trap.c:875
> #4  0xffffffff80c972f9 in trap_pfault (frame=0xfffffe00f1354830, usermode=0)
>     at /usr/src/sys/amd64/amd64/trap.c:692
> #5  0xffffffff80c96a8b in trap (frame=0xfffffe00f1354830)
>     at /usr/src/sys/amd64/amd64/trap.c:456
> #6  0xffffffff80c7dd42 in calltrap ()
>     at /usr/src/sys/amd64/amd64/exception.S:232
> #7  0xffffffff808c9ef3 in softclock_call_cc (c=0xffffffff813834b8,
>     cc=0xffffffff81527680, direct=0) at /usr/src/sys/kern/kern_timeout.c:701
> #8  0xffffffff808ca304 in softclock (arg=0xffffffff81527680)
>     at /usr/src/sys/kern/kern_timeout.c:810

This is actually a crash in newcons.  Try setting kern.vt.suspendswitch to 0
as a workaround.

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201403181527.17100.jhb>