From owner-freebsd-stable@FreeBSD.ORG Sat Mar 15 19:44:47 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 770AFA5A for ; Sat, 15 Mar 2014 19:44:47 +0000 (UTC) Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4F402DB6 for ; Sat, 15 Mar 2014 19:44:47 +0000 (UTC) Received: by mail-pb0-f44.google.com with SMTP id rp16so4054729pbb.3 for ; Sat, 15 Mar 2014 12:44:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=icA53xqiv1KfWvLdnokEB339sh9ggUUTaNYosh+/RR0=; b=UjwoEaPqZeIBofZj88LzIYEU5vXeTMwlqsqtOka+gyHuxcTbSzZm5gFmCofraRfL5G CFsXA4+4fZk0RvO4vxYKgvXn4bCs3IxA9YZsMKXsPhcXTNfDy2i4Z4eTZNZs7RkGzXcS ncuJnoLOouNFF88+NqwWEoM3oEy135m14LJ6gkr4pGeZ/E2ghBEKhUen+56MtxR+8tFn iHxBYY2NHIG3GcTywkDCWtEz8pSa62ZHRsd6/gxv1bSDWLCNoKpNiPv8gcGiBoPOPgdJ xwHFZRz684y7omthjvvXs/g+FWFlVrU7Ex9k6mo3OhbiZaqPHW1LwBhh3bUQ8QI2JUjP xtvA== MIME-Version: 1.0 X-Received: by 10.68.237.133 with SMTP id vc5mr16479399pbc.92.1394912686892; Sat, 15 Mar 2014 12:44:46 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.66.0.164 with HTTP; Sat, 15 Mar 2014 12:44:46 -0700 (PDT) Date: Sat, 15 Mar 2014 12:44:46 -0700 X-Google-Sender-Auth: y-r8N7263JQCHjg2GkNkDt6JPW8 Message-ID: Subject: Clock issues and crash on resume on 10-Stable r263062M From: Kevin Oberman To: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Mar 2014 19:44:47 -0000 I am seeing clock related issues when resuming from a suspended state on my laptop running r263062M. I've seen two failures, but both appear to be dealing with updating the system time after resuming. FreeBSD rogue.local 10.0-STABLE FreeBSD 10.0-STABLE #0 r263062M: Tue Mar 11 22:14:07 PDT 2014 root@rogue.local:/usr/obj/usr/src/sys/VT amd64 1. The time does not update after resume. The time on the system simply starts counting again from the time of the suspend. 'ntpq -p' shows no sync to any clock and a rather large offset to them once there has been poll of that server. It is possible that, if I waited long enough, that NTP would correct the time, but with polling at 1024 seconds and several polls needed for the time to try to reset, I simply forced the time to within a second and went on. 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=) at pcpu.h:219 219 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) 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=) at /usr/src/sys/kern/kern_shutdown.c:759 #3 0xffffffff80c97022 in trap_fatal (frame=, eva=) 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 #9 0xffffffff8088929b in intr_event_execute_handlers ( p=, ie=0xfffff800027b0900) at /usr/src/sys/kern/kern_intr.c:1263 #10 0xffffffff808896e6 in ithread_loop (arg=0xfffff8000292ac60) at /usr/src/sys/kern/kern_intr.c:1276 #11 0xffffffff80886f4a in fork_exit ( callout=0xffffffff80889650 , arg=0xfffff8000292ac60, frame=0xfffffe00f1354ac0) at /usr/src/sys/kern/kern_fork.c:995 #12 0xffffffff80c7e27e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:606 #13 0x0000000000000000 in ?? () Current language: auto; currently minimal One of these failures has occurred on over half of the resume operations I have tried since about March 3rd, though I have had only one crash, earlier today. N.B. I failed to remove VESA from my kernel on March 3, so was unable to resume until I added VT and removed VESA on March 11. Resume worked fine with my kernel at r261581. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com