https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263632

--- Comment #14 from Jonathan Vasquez <j...@xyinn.org> ---
Some more updates. So I was able to fix my computer just generally crashing on
X11 (with any DE, although I normally use i3 or KDE) by adding the following to
my /usr/local/etc/X!1/xorg.conf.d/10-video.conf:

```
Section "Device"
        Identifier  "Card0"
        Driver      "modesetting"
        BusID       "PCI:0:2:0"
        Option      "AccelMethod"       "SNA"
EndSection
```

Once I added that, I re-tested the resume behavior since as I said earlier,
there are probably multiple bugs here (some in the graphics layer, and some in
the wireless layer).

During my first three tests, I did 'acpiconf -s 3', waited about 30 seconds, 2
minutes, and 5 minutes respectively. None of these crashed. However, the
wireless driver stopped working on the first resume. The good news is that I
was able to get more data out of 'dmesg' regarding iwlwifi (attached is
'dump3').

During the third resume, I tried a 'service netif restart wlan0' to see if it
would crash (given what we know about the old state), and yup, it crashed
immediately. On a fresh reboot, I tried again my 'acpiconf -s 3' tests, and the
system started to have non-deterministic behavior as follows:

1. The system resumed fine, didn't crash, but wifi wasn't working. Restarting
the wifi driver actually yielded a working connection.

2. The system resumed, and crashed about 10 seconds later, this was a hard
crash and the system actually spat out A LOT of output very quickly, ending
with an error in the graphics driver (drm-510-kmod, attached as
graphics-1.jpg). I was expecting a crash dump to be properly saved since I have
the dumpdev properly set now (and even using a 32 GB physical swap :O), but
when the system started up it didn't dump anything. No cores were found.

3. The system resumed, and immediately decides to shutdown (as if the power
signal was pressed).

Should I open another bug report specifically targeting the graphics portion of
this since it does seem we are running into two separate bugs (given this is
primarily for the wireless crash on resume)?

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to