Re: Suspend to RAM failes

[coypu%SDF.ORG@localhost]

On Tue, Nov 29, 2016 at 04:10:49PM +0100, Carsten Kunze wrote:
> acpi0: entering state S3
> Flushing disk caches: 8 done
> sd0(umass0:0:0:0): generic HBA error
> sd0: cache synchronization failed
> fatal page fault in supervisor mode
> trap type 6 code 10 rip 0 cs 8 rflags 10282 cr2 0 ilevel 5 rsp fffffe810e66ce68
> curlwp 0xfffffe822e531440 pid 0.6 lowest kstack 0xfffffe810e6692c0
> panic: trap
> cpu0: Begin traceback...
> vpanic() at netbsd:vpanic+0x140
> snprintf() at netbsd:snprintf
> trap() at netbsd:trap+0xc4b
> --- trap (number 6) ---
> ?() at 0
> ehci_softintr() at netbsd:ehci_softintr+0x19c
> usb_soft_intr() at netbsd:usb_soft_intr+0x1f
> softint_dispatch() at netbsd:softint_dispatch+0xd3
> DDB lost frame for netbsd:Xsoftintr+0x4f, trying 0xfffffe810e66cff0
> Xsoftintr() at netbsd:Xsoftintr+0x4f
> --- interrupt ---
> /home: replaying log to disk

I've seen this too, it was with USB wifi. I think it was attempting to use
USB-attached devices before the rest of the USB system is ready.
I have PR kern/51341 open for my issue.

... as a really horrible and otherwise transparent hack, you could probably
detach USB before & reattach (drvctl -r) after.

I'm not sure whether this is the right fix (if done within the kernel), but
it sounds somewhat correct...