Re: panic on boot

From: Tim Kientzle <tim_at_kientzle.com>
Date: Thu, 4 Sep 2014 20:25:17 -0700
On Sep 3, 2014, at 7:08 AM, Tim Kientzle <tim_at_kientzle.com> wrote:

> 
> On Sep 3, 2014, at 6:51 AM, Tim Kientzle <tim_at_kientzle.com> wrote:
> 
>> 
>> On Sep 2, 2014, at 1:13 PM, Garrett Cooper <yaneurabeya_at_gmail.com> wrote:
>> 
>>> On Tue, Sep 2, 2014 at 9:47 AM, AN <andy_at_neu.net> wrote:
>>>> FreeBSD FBSD11 11.0-CURRENT FreeBSD 11.0-CURRENT #47 r269949: Wed Aug 13
>>>> 14:18:28 EDT 2014     root_at_FBSD11:/usr/obj/usr/src/sys/MYKERNEL  amd64
>>>> 
>>>> 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?
>>> 
>>>  Could you please provide the traceback?
>> 
>> I’m also seeing panics at boot on BBB (armv6) with a kernel built from r270779.  Old kernel from r270339 still works.
> 
> Here’s what I’m seeing at boot on BBB with r270779:
> 
> … 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=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
> 	options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
> 	inet6 ::1 prefixlen 128 
> 	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 
> 	inet 127.0.0.1 netmask 0xff000000 
> 	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
> cpsw0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> 	options=8000b<RXCSUM,TXCSUM,VLAN_MTU,LINKSTATE>
> 	ether 7c:66:9d:6c:e1:4d
> 	media: Ethernet autoselect (none)
> 	status: no carrier
> 	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> Starting devd.
> panic: Undefined instruction in kernel.
> 
> 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 = 0xc054d7a8  lr = 0xc0231ab8 (db_stack_trace+0xf4)
>         sp = 0xde69d2f8  fp = 0xde69d310
>        r10 = 0xc0939838
> db_stack_trace() at db_stack_trace+0xf4
>         pc = 0xc0231ab8  lr = 0xc0231428 (db_command+0x270)
>         sp = 0xde69d318  fp = 0xde69d3b8
>         r4 = 0x00000000  r5 = 0x00000000
>         r6 = 0x00000000
> db_command() at db_command+0x270
>         pc = 0xc0231428  lr = 0xc023118c (db_command_loop+0x60)
>         sp = 0xde69d3c0  fp = 0xde69d3d0
>         r4 = 0xc059585e  r5 = 0xc05b04e3
>         r6 = 0xc0939824  r7 = 0xc064fa38
>         r8 = 0xc06958e4  r9 = 0xc06958e0
> db_trap() at db_trap+0xd8
>         pc = 0xc0233b54  lr = 0xc039e894 (kdb_trap+0xbc)
>         sp = 0xde69d500  fp = 0xde69d520
>         r4 = 0x00000000  r5 = 0x00000001
>         r6 = 0xc0695908  r7 = 0xc064fa38
> kdb_trap() at kdb_trap+0xbc
>         pc = 0xc039e894  lr = 0xc0563c80 (undefinedinstruction+0x298)
>         sp = 0xde69d528  fp = 0xde69d598
>         r4 = 0x00000000  r5 = 0x00000000
>         r6 = 0xc0563938  r7 = 0xe7ffffff
>         r8 = 0xc2b15c80  r9 = 0xc039e164
>        r10 = 0xde69d5a0
> undefinedinstruction() at undefinedinstruction+0x298
>         pc = 0xc0563c80  lr = 0xc054f490 (exception_exit)
>         sp = 0xde69d5a0  fp = 0xde69d5f8
>         r4 = 0xc05b0538  r5 = 0xde69d634
>         r6 = 0xc05dc349  r7 = 0xc0687e28
>         r8 = 0xc2b15c80  r9 = 0xc093b1dc
>        r10 = 0xc0687c90
> exception_exit() at exception_exit
>         pc = 0xc054f490  lr = 0xc039e158 (kdb_enter+0x40)
>         sp = 0xde69d5f0  fp = 0xde69d5f8
>         r0 = 0xc06958f4  r1 = 0x00000000
>         r2 = 0xc05b3eac  r3 = 0x000000aa
>         r4 = 0xc05b0538  r5 = 0xde69d634
>         r6 = 0xc05dc349  r7 = 0xc0687e28
>         r8 = 0xc2b15c80  r9 = 0xc093b1dc
>        r10 = 0xc0687c90 r12 = 0x00000000
> $a() at $a
>         pc = 0xc039e168  lr = 0xc03675a0 (vpanic+0xb4)
>         sp = 0xde69d600  fp = 0xde69d620
>         r4 = 0x00000100
> vpanic() at vpanic+0xb4
>         pc = 0xc03675a0  lr = 0xc0367604 (kproc_shutdown)
>         sp = 0xde69d628  fp = 0xde69d62c
>         r4 = 0x00000000  r5 = 0x00000000
>         r6 = 0xc0563938  r7 = 0xe28fc600
>         r8 = 0xc2b15c80  r9 = 0xc2eb1bd8
>        r10 = 0xde69d6b8
> kproc_shutdown() at kproc_shutdown
>         pc = 0xc0367604  lr = 0xc0939610 (gdb_uh)
>         sp = 0xde69d634  fp = 0xde69d6b0
>         r4 = 0xc0367604  r5 = 0xde69d634
> Unknown entry: 0
> gdb_uh() at gdb_uh
>         pc = 0xc0939610  lr = 0xc0939610 (gdb_uh)
>         sp = 0xde69d634  fp = 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
Received on Fri Sep 05 2014 - 01:30:48 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:51 UTC