Comment # 32
on bug 106671
from Alan W. Irwin
I had another lockup today after ~3 days of uptime. Please see the most recent attachment for the relevant log files and dmesg output corresponding to this lockup. These logs contain NMI messages and references to the e1000e kernel module so, although I am no expert, this lockup appears to be e1000e related. That kernel module is running the following Intel networking expansion card: 09:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection That card is used to connect (via crossover cable) this Ryzen 7 box with an external X-terminal box. Since this is the second lockup recently attributed to the e1000e module and other recent lockups I have encountered with no error messages or ascii null error messages in the system logs could also be due to this kernel module, the current stability test I just started was to turn off the X terminal completely (to eliminate use of the 82574L other than its initial detection). The second user of the present system that previously accessed it with the X-terminal is now accessing locally it with "startx -- :1" while I am accessing it locally with "startx". So the two users are sharing one monitor, keyboard, and mouse and switching between their two xfce desktops and associated local X servers using the appropriate ctrl-alt-FN keyboard shortcuts. So although this is a painful way to run our two desktops it obviously is a more stringent test and also a much cleaner test (without the e1000e troubles confusing graphics stack issues) of how stable the Debian Buster graphics stack is for my Ryzen 7 1700 system with 64GB, (idle) Intel 82574L networking card, and (extremely busy since it is switched between two X servers several times per day) AMD RX 550. In sum, my hope is that all the other package upgrades and installations (e.g., of the firmware packages) I have done have completely stabilized the Debian Buster graphics stack for my Ryzen 7 system with RX 550 so that I will get an uptime (with this painful but useful experiment with two local X servers) of at least several months which would allow me to close this bug report as fixed. @Michel Dänzer: Meanwhile, where is the best upstream place to report the repeated lockups with the e1000e? I have already created a Debian Buster bug report at <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911496> concerning the e1000e lockups, but I would like to repeat that for the relevant kernel bug tracker in case there is no Debian response to that bug report.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
