Re: Panic after update: stable/12-n233561-42cb78bdd49 - n233682-a436245ccf1

On 29/08/2021 06:54, David Wolfskill wrote:
> The core.txt.0 file claims that the backtrace is:
> 
> panic: vm_fault: fault on nofault entry, addr: 0xfffffe10384e2000
> cpuid = 7
> time = 1630206013
> KDB: stack backtrace:
> #0 0xffffffff80bebfc5 at kdb_backtrace+0x65
> #1 0xffffffff80ba017b at vpanic+0x17b
> #2 0xffffffff80b9fff3 at panic+0x43
> #3 0xffffffff80f5be62 at vm_fault+0x24f2
> #4 0xffffffff80f59850 at vm_fault_trap+0x60
> #5 0xffffffff8104fb4c at trap_pfault+0x19c
> #6 0xffffffff8104f046 at trap+0x286
> #7 0xffffffff81026eb8 at calltrap+0x8
> Uptime: 2m18s

As far as I can tell, the stack trace shows only what was called _after_ the 
trap / fault.  So, the interesting part is missing.

-- 
Andriy Gapon