From owner-freebsd-stable@FreeBSD.ORG Wed Mar 19 04:07:59 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6653D7C3; Wed, 19 Mar 2014 04:07:59 +0000 (UTC) Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 03754A85; Wed, 19 Mar 2014 04:07:58 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id m20so8966029qcx.24 for ; Tue, 18 Mar 2014 21:07:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=/TLX1z8K63MIVocCHKEi96MlIPA/wjxyM7svYhom1sM=; b=riAgqZWfIUP7HpkSTmVFtUIx/xkgTM7UvXro21e+07P3Pq8sDsVlp/l2gfEANX8MVv SODllMcTj7ePzcKqq7uDXbYuKND2bWOUH876aWhtMkLKpRweDVmBtwhS9vfyiES58KfL /CIuJBltLS30L1XwRwhkxQGFDfLE6fK+GcSN6/KFAl8SNG5QgdA1Sy3VoHLnrLTH37ac 66ktm8Hg8v23LQd4PC4z7KUvuQnBLqSnpCBevw7dL5//PIqEe190FaKoeoazAsGo9aOG ehXt9BHvOTZbb3YVmnybRpdLqzlf1lS1K9Awz1mW5Eugqcr8It9+V8RcckDSfLXRKn8M Jv0w== MIME-Version: 1.0 X-Received: by 10.224.131.193 with SMTP id y1mr24258qas.86.1395202077388; Tue, 18 Mar 2014 21:07:57 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.8.137 with HTTP; Tue, 18 Mar 2014 21:07:57 -0700 (PDT) In-Reply-To: <20140318234623.61a99182.ray@ddteam.net> References: <201403181527.17100.jhb@freebsd.org> <20140318234623.61a99182.ray@ddteam.net> Date: Tue, 18 Mar 2014 21:07:57 -0700 X-Google-Sender-Auth: SPMNNni3lOYI1SRv8In1jP-9Q3M Message-ID: Subject: Re: Clock issues and crash on resume on 10-Stable r263062M From: Adrian Chadd To: Aleksandr Rybalko Content-Type: text/plain; charset=ISO-8859-1 Cc: Kevin Oberman , Aleksandr Rybalko , FreeBSD-STABLE Mailing List , John Baldwin 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: Wed, 19 Mar 2014 04:07:59 -0000 Well, changing the default is cool, but there's still some odd bug there that could do with chasing down. :) -a On 18 March 2014 14:46, Aleksandr Rybalko wrote: > On Tue, 18 Mar 2014 14:38:31 -0700 > Kevin Oberman wrote: > >> On Tue, Mar 18, 2014 at 12:27 PM, John Baldwin >> wrote: >> >> > 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=) 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 >> > >> > This is actually a crash in newcons. Try setting >> > kern.vt.suspendswitch to 0 >> > as a workaround. >> > >> > -- >> > John Baldwin >> > >> >> Ack! I had forgotten seeing the thread on this just a while back, >> before vt was committed to 10. >> >> Thanks so much! >> -- >> R. Kevin Oberman, Network Engineer, Retired >> E-mail: rkoberman@gmail.com > > Looks like I have to invert default for it :) > > Sorry for making such problems. > > WBW > -- > Aleksandr Rybalko > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"