Blackbird version to install

[Leandro Lupori]

You could try to boot in single user mode and run "fsck -y" twice, to make
sure the panic isn't being caused by a corrupted FS.

- Leandro

On Sat, Sep 7, 2019 at 10:41 PM Curtis Hamilton <clhamilto at gmail.com> wrote:

> Finally got my blackbird working and installed 13-CURRENT.  However,
> after a couple reboots I'm now getting the below panic:
>
> panic: ffs_valloc: dup alloc
> cpuid = 14
> time = 1567918670
> KDB: stack backtrace:
> 0xe00000008b7e5a20: at .kdb_backtrace+0x5c
> 0xe00000008b7e5b50: at .vpanic+0x1b4
> 0xe00000008b7e5c10: at .panic+0x38
> 0xe00000008b7e5ca0: at .ffs_valloc+0x650
> 0xe00000008b7e5da0: at .ufs_readdir+0xe60
> 0xe00000008b7e5fc0: at .ufs_readdir+0x1768
> 0xe00000008b7e6050: at .VOP_CREATE_APV+0x148
> 0xe00000008b7e60e0: at .vn_open_cred+0x240
> 0xe00000008b7e62b0: at .vn_open+0x24
> 0xe00000008b7e6330: at .kern_openat+0x27c
> 0xe00000008b7e6520: at .sys_openat+0x58
> 0xe00000008b7e65b0: at .trap+0x65c
> 0xe00000008b7e6770: at .powerpc_interrupt+0x290
> 0xe00000008b7e6810: user SC trap by 0x810221858: srr1=0x900000000000f032
> r1=0x3fffffffffffd9c0 cr=0x44000024 xer=0x20040000 ctr=0x810221850
> r2=0x8102f3a50
> KDB: enter: panic
> [ thread pid 172 tid 100182 ]
> Stopped at .kdb_enter+0x60:        ld      r2, r1, 0x28
> db>
>
> I'm getting this panic with and without a monitor attached. Any ideas?
>
> -Curtis
> On 08/25/19 08:02, Mark Linimon wrote:
> > Here's what I'm running on mine: blackbird1% uname -a FreeBSD
> > blackbird1.lonesome.com 13.0-CURRENT FreeBSD 13.0-CURRENT r349478
> > GENERIC powerpc blackbird1% uptime 12:01PM up 42 days, 7:28, 6 users,
> > load averages: 0.23, 0.16, 0.14 Are you perhaps being caught in this
> > trap?
> > https://wiki.freebsd.org/powerpc/Raptor/Blackbird#Tips_and_Tricks mcl
>
> _______________________________________________
> freebsd-ppc at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe at freebsd.org"
>