From owner-freebsd-current@FreeBSD.ORG Fri Sep 5 03:30:48 2014 Return-Path: Delivered-To: freebsd-current@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 E8F321D1 for ; Fri, 5 Sep 2014 03:30:47 +0000 (UTC) Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B9F2D1EF4 for ; Fri, 5 Sep 2014 03:30:47 +0000 (UTC) Received: by mail-pa0-f46.google.com with SMTP id eu11so21302931pac.5 for ; Thu, 04 Sep 2014 20:30:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=0VL/Z9kqxQWD0QOgswGJh1I69ABEh4bK9GwHYsdaeyo=; b=PyTFASVnEkeRKiT6PwgUNyrqse+juLCqB4M54koCBS33FOHnCftCADzthThV3qArRk uquWwxRFsSjgnVMeUzwQ0f4770fnfqVYrnpbw3I6Lz+IpzQVTVlkjrKQ+w1ujiVaph5S gvXW58wh7/f9Jaf3ATjZj3mRX01a38xhwVUXvzlDLZNcKbSneSps+b11usmZh+lR20YZ vJ+qy9D8l4sdoyIoiUDCIAx8Ten5uzPRJ8Dos+XWHtcDrGjvvTMBbV0azWLjFWSeAyMt KuSwVa9a3mfp/Im+RaqIWO2nBYwZPwoZct53R4HVMSTCMMP0IM4hC1Jj4/Ht9PwaDC6P /ewA== X-Gm-Message-State: ALoCoQlnXHBnMVX6iK/Kz9/ZIviQTiF+fDc/gcNa4acxVCHpjZwDCsl6CSQvtKmpVwkvv/bXUK0C X-Received: by 10.70.129.204 with SMTP id ny12mr10416211pdb.114.1409887526176; Thu, 04 Sep 2014 20:25:26 -0700 (PDT) Received: from [192.168.1.100] (c-24-6-220-224.hsd1.ca.comcast.net. [24.6.220.224]) by mx.google.com with ESMTPSA id mn1sm512296pbc.4.2014.09.04.20.25.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 04 Sep 2014 20:25:25 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: panic on boot From: Tim Kientzle In-Reply-To: Date: Thu, 4 Sep 2014 20:25:17 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Garrett Cooper X-Mailer: Apple Mail (2.1878.6) Cc: AN , FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2014 03:30:48 -0000 On Sep 3, 2014, at 7:08 AM, Tim Kientzle wrote: >=20 > On Sep 3, 2014, at 6:51 AM, Tim Kientzle wrote: >=20 >>=20 >> On Sep 2, 2014, at 1:13 PM, Garrett Cooper = wrote: >>=20 >>> On Tue, Sep 2, 2014 at 9:47 AM, AN wrote: >>>> FreeBSD FBSD11 11.0-CURRENT FreeBSD 11.0-CURRENT #47 r269949: Wed = Aug 13 >>>> 14:18:28 EDT 2014 root@FBSD11:/usr/obj/usr/src/sys/MYKERNEL = amd64 >>>>=20 >>>> Trying to rebuild the system at r270973 >>>> I get a kernel panic on boot. I am able to boot into kernel.old at = r269949 >>>> and the system is functional. Is anyone else seeing a panic on = boot at a >>>> recent svn update? >>>=20 >>> Could you please provide the traceback? >>=20 >> I=92m also seeing panics at boot on BBB (armv6) with a kernel built = from r270779. Old kernel from r270339 still works. >=20 > Here=92s what I=92m seeing at boot on BBB with r270779: >=20 > =85 usual kernel boot messages ... > Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... > warning: no time-of-day clock registered, system time will not be set = accurately > Setting hostuuid: aeaa664b-1739-11e4-8e30-7c669d6ce14d. > Setting hostid: 0x0318d0fa. > No suitable dump device was found. > Entropy harvesting: interrupts ethernet point_to_point swi. > Starting file system checks: > /dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/mmcsd0s2a: clean, 1982743 free (62311 frags, 240054 blocks, 1.6% = fragmentation) > Mounting local file systems:. > /etc/rc: WARNING: $swapfile is obsolete. Ignored. > Writing entropy file:. > Setting hostname: bb-blue. > cpsw0: link state changed to DOWN > Starting Network: lo0 cpsw0. > lo0: flags=3D8049 metric 0 mtu 16384 > options=3D600003 > inet6 ::1 prefixlen 128=20 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2=20 > inet 127.0.0.1 netmask 0xff000000=20 > nd6 options=3D21 > cpsw0: flags=3D8843 metric 0 = mtu 1500 > options=3D8000b > ether 7c:66:9d:6c:e1:4d > media: Ethernet autoselect (none) > status: no carrier > nd6 options=3D29 > Starting devd. > panic: Undefined instruction in kernel. >=20 > KDB: enter: panic > [ thread pid 284 tid 100069 ] > Stopped at $d: ldrb r15, [r15, r15, ror r15]! > db> bt > Tracing pid 284 tid 100069 td 0xc2b15c80 > db_trace_self() at db_trace_self > pc =3D 0xc054d7a8 lr =3D 0xc0231ab8 (db_stack_trace+0xf4) > sp =3D 0xde69d2f8 fp =3D 0xde69d310 > r10 =3D 0xc0939838 > db_stack_trace() at db_stack_trace+0xf4 > pc =3D 0xc0231ab8 lr =3D 0xc0231428 (db_command+0x270) > sp =3D 0xde69d318 fp =3D 0xde69d3b8 > r4 =3D 0x00000000 r5 =3D 0x00000000 > r6 =3D 0x00000000 > db_command() at db_command+0x270 > pc =3D 0xc0231428 lr =3D 0xc023118c (db_command_loop+0x60) > sp =3D 0xde69d3c0 fp =3D 0xde69d3d0 > r4 =3D 0xc059585e r5 =3D 0xc05b04e3 > r6 =3D 0xc0939824 r7 =3D 0xc064fa38 > r8 =3D 0xc06958e4 r9 =3D 0xc06958e0 > db_trap() at db_trap+0xd8 > pc =3D 0xc0233b54 lr =3D 0xc039e894 (kdb_trap+0xbc) > sp =3D 0xde69d500 fp =3D 0xde69d520 > r4 =3D 0x00000000 r5 =3D 0x00000001 > r6 =3D 0xc0695908 r7 =3D 0xc064fa38 > kdb_trap() at kdb_trap+0xbc > pc =3D 0xc039e894 lr =3D 0xc0563c80 = (undefinedinstruction+0x298) > sp =3D 0xde69d528 fp =3D 0xde69d598 > r4 =3D 0x00000000 r5 =3D 0x00000000 > r6 =3D 0xc0563938 r7 =3D 0xe7ffffff > r8 =3D 0xc2b15c80 r9 =3D 0xc039e164 > r10 =3D 0xde69d5a0 > undefinedinstruction() at undefinedinstruction+0x298 > pc =3D 0xc0563c80 lr =3D 0xc054f490 (exception_exit) > sp =3D 0xde69d5a0 fp =3D 0xde69d5f8 > r4 =3D 0xc05b0538 r5 =3D 0xde69d634 > r6 =3D 0xc05dc349 r7 =3D 0xc0687e28 > r8 =3D 0xc2b15c80 r9 =3D 0xc093b1dc > r10 =3D 0xc0687c90 > exception_exit() at exception_exit > pc =3D 0xc054f490 lr =3D 0xc039e158 (kdb_enter+0x40) > sp =3D 0xde69d5f0 fp =3D 0xde69d5f8 > r0 =3D 0xc06958f4 r1 =3D 0x00000000 > r2 =3D 0xc05b3eac r3 =3D 0x000000aa > r4 =3D 0xc05b0538 r5 =3D 0xde69d634 > r6 =3D 0xc05dc349 r7 =3D 0xc0687e28 > r8 =3D 0xc2b15c80 r9 =3D 0xc093b1dc > r10 =3D 0xc0687c90 r12 =3D 0x00000000 > $a() at $a > pc =3D 0xc039e168 lr =3D 0xc03675a0 (vpanic+0xb4) > sp =3D 0xde69d600 fp =3D 0xde69d620 > r4 =3D 0x00000100 > vpanic() at vpanic+0xb4 > pc =3D 0xc03675a0 lr =3D 0xc0367604 (kproc_shutdown) > sp =3D 0xde69d628 fp =3D 0xde69d62c > r4 =3D 0x00000000 r5 =3D 0x00000000 > r6 =3D 0xc0563938 r7 =3D 0xe28fc600 > r8 =3D 0xc2b15c80 r9 =3D 0xc2eb1bd8 > r10 =3D 0xde69d6b8 > kproc_shutdown() at kproc_shutdown > pc =3D 0xc0367604 lr =3D 0xc0939610 (gdb_uh) > sp =3D 0xde69d634 fp =3D 0xde69d6b0 > r4 =3D 0xc0367604 r5 =3D 0xde69d634 > Unknown entry: 0 > gdb_uh() at gdb_uh > pc =3D 0xc0939610 lr =3D 0xc0939610 (gdb_uh) > sp =3D 0xde69d634 fp =3D 0xde69d6b0 > Unable to unwind into user mode I just noticed another of my BBB systems is successfully running = r270695, so it seems something broke the Beaglebone kernel between = 270695 and 270779. Tim