On Mon, Aug 14, 2017 at 12:05:59AM +0100, Laurence Tratt wrote: > The following panic happened immediately after a resume (the second since > the machine was switched on) on the Aug 11th snapshot: > > uvm_fault(0xffffffff81b3ff8, 0x200000003, 0, 1) -> e > kernel: page fault trap, code=0 > Stopped at acpitz_setfan+0x8c: movq 0(%rax), %rsi > > https://imagebin.ca/v/3Wmq884ayBSf > > This happened before the keyboard was reattached, so I couldn't get any > further information from the panic.
It turns out that this happens repeatedly on this machine. The precise offset in the message changes but it's always of the form: kernel: page fault trap, code=0 Stopped at acpitz_setfan+0x94: movq 0(%rbx),%rsi AFAICT it never happens after the first resume, but only on a subsequent resume (sometimes the second, sometimes the third etc.). One thing that does occur to me is that this machine is fanless: the fans are turned off in the BIOS. Maybe a null pointer is leaking in somewhere because of that? Laurie
