Thomas, Please try r324444. Based on your panic message, "panic: freeing invalid range," it may be the same general swap issue which r324444 aimed to address.
Best, Conrad On Tue, Oct 10, 2017 at 2:20 PM, Thomas Laus <lau...@acm.org> wrote: > Allan Jude [allanj...@freebsd.org] wrote: >> >> Before the ddb> prompt there should be a message explaining what has >> gone wrong to make it drops into the debugger. If it has scrolled off >> the top of the screen, press scroll-lock and then you can use the arrow >> keys to navigate back up into the buffer. >> > The first message is from GEOM_ELI: Device ada0p2.eli created > GEOM_ELI: Encryption AES-XTS 128 > GEOM_ELI: Crypto: software > panic: freeing invalid range. > > Next follows the stack trace > > then: > > --- syscall (85, FreeBSD ELF64, sys_swapon), rip = 0x800a88aea, rsp = > 0x7fffffffea48, rbp 0x7fffffffea60 --- > > stopped at kdb_enter+0x3b:mmovq $0,kdb_why > > I can't save all of this to a file to attach, but this is just an > overview of the panic. > > I get this everytime when going from single user to multi-user and > about 3 out of 5 times with a normal boot. My other release has been > flawless 100 percent of the time. > > Tom > > -- > Public Keys: > PGP KeyID = 0x5F22FDC1 > GnuPG KeyID = 0x620836CF > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
