Re: Encrypted Swap Problem with 12.0-CURRENT r324427

[Thomas Laus]

On 10/10/17 17:25, Conrad Meyer wrote:
> Thomas,
> 
> Please try r32.  Based on your panic message, "panic: freeing
> invalid range," it may be the same general swap issue which r32
> aimed to address.
>
Building and installing 12.0-CURRENT r324508 fixed my problem.  I was
able to reboot successfully 10 times in a row.  I was also able to
successfully go from single user to multi-user without any issues.

Thanks

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"

Re: Encrypted Swap Problem with 12.0-CURRENT r324427

[Conrad Meyer]

Thomas,

Please try r32.  Based on your panic message, "panic: freeing
invalid range," it may be the same general swap issue which r32
aimed to address.

Best,
Conrad

On Tue, Oct 10, 2017 at 2:20 PM, Thomas Laus  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 =
> 0x7fffea48, rbp 0x7fffea60 ---
>
> 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"

Re: Encrypted Swap Problem with 12.0-CURRENT r324427

[Thomas Laus]

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 =
0x7fffea48, rbp 0x7fffea60 ---

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"

Re: Encrypted Swap Problem with 12.0-CURRENT r324427

[Allan Jude]

On 10/10/2017 16:15, Thomas Laus wrote:
> I have been having some boot issues after upgrading to r324427 this
> week.  It gets to the step of accessing my Geli encrypted swap partition
> and then drops to the ddb> prompt.  Sometimes it works but mostly it
> does not.  Booting with r323984 is flawless.  Has anything been changed
> between these 2 revisions that would affect me?  Booting in single
> usermode works fine on r324427 but immediately goes to the ddb> prompt
> when terminating with a 'ctrl-d' to go into multi-user mode.
> 
> Is there anything that I might have missed in the UPDATING instruction
> that might cause this.  I don't have any errors on this partition that
> gpart status finds.
> 
> Tom
> 
> 

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.

-- 
Allan Jude
___
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"