Created attachment 142459 [details]
dmesg output with debug
Symptoms: Display freezes for several seconds; The mouse pointer is still movable, but nothing responds to click anymore; The display manager crashes and either goes into fallback mode (Cinnamon) or takes me back to the login screen (MATE).
Reproduce: This issue seems most reproducible when watching a YouTube video in Firefox. Though it has happened in many other scenarios as well.
-- system architecture: x86_64
-- kernel version: 4.15.0-39-generic
-- Linux distribution: Linux Mint 19, both Cinnamon and MATE versions
-- Machine or mother board model:
System: Host: tokyo Kernel: 4.15.0-39-generic x86_64 bits: 64 gcc: 7.3.0
Desktop: MATE 1.20.1 (Gtk 3.22.30-1ubuntu1) dm: lightdm Distro: Linux Mint 19 Tara
Machine: Device: desktop System: Compulab product: fitlet2 serial: N/A
Mobo: Compulab model: fitlet2 v: 1.1 serial: N/A
UEFI: American Megatrends v: FLT2.MBM2.0.46.01.00 date: 09/26/2018
Chassis: type: 3 serial: N/A
Battery hidpp__2: charge: N/A condition: NA/NA Wh volts: NA
model: Logitech Wireless Mouse M310/M310t serial: <filter>status: Discharging
hidpp__3: charge: N/A condition: NA/NA Wh volts: NA
model: Logitech K520 serial: <filter>status: Discharging
CPU: Quad core Intel Celeron J3455 (-MCP-) arch: N/A cache: 1024 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11980
clock speeds: min/max: 800/2300 MHz 1: 1776 MHz 2: 1666 MHz 3: 1560 MHz
4: 1710 MHz
Graphics: Card: Intel Device 5a85 bus-ID: 00:02.0 chip-ID: 8086:5a85
Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting (unloaded: fbdev,vesa)
OpenGL: renderer: Mesa DRI Intel HD Graphics 500 (Broxton 2x6)
version: 4.5 Mesa 18.0.5 (compat-v: 3.0) Direct Render: Yes
Audio: Card Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster
driver: snd_hda_intel bus-ID: 00:0e.0 chip-ID: 8086:5a98
Sound: Advanced Linux Sound Architecture v: k4.15.0-39-generic
Network: Card-1: Intel Wireless 8260 driver: iwlwifi bus-ID: 01:00.0 chip-ID: 8086:24f3
IF: wlp1s0 state: down mac: <filter>
Card-2: Intel I211 Gigabit Network Connection
driver: igb v: 5.4.0-k port: e000 bus-ID: 02:00.0 chip-ID: 8086:1539
IF: enp2s0 state: down mac: <filter>
Card-3: Intel I211 Gigabit Network Connection
driver: igb v: 5.4.0-k port: d000 bus-ID: 03:00.0 chip-ID: 8086:1539
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 63.4GB (14.6% used)
ID-1: /dev/sda model: M2SCF size: 63.4GB serial: <filter>
Partition: ID-1: / size: 58G used: 8.7G (16%) fs: ext4 dev: /dev/sda2
RAID: System: supported: N/A
No RAID devices: /proc/mdstat, md_mod kernel module present
Unused Devices: none
Sensors: System Temperatures: cpu: 37.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 180 Uptime: 15 min Memory: 482.9/3767.5MB
Init: systemd v: 237 runlevel: 5 Gcc sys: 7.3.0
Client: Shell (bash 4.4.191 running in mate-terminal) inxi: 2.3.56
-- Display connector: HDMI
-- dmesg with debug information: SEE ATTACHED
-- GPU crash dump: SEE ATTACHED
Created attachment 142460 [details]
batch buffer output
Also reported in Linux Mint forums:
The ring registers are more than a little peculiar, could you recapture the error on a more recent kernel?
Sure thing. Installed 4.19.2 and recaptured both logs, attached.
Created attachment 142469 [details]
dmesg w/ 4.19.2
Created attachment 142470 [details]
batch buffer w/ 4.19.2
If there's any signs that this is actually a hardware issue I would appreciate knowing that so I can get this back to the manufacturer while it's still under warranty. Thanks!
Since the hang happened on flush, I assume this is an Xorg bug. Setting the product as Xorg.
The STATE_BASE_ADDRESS looks inconsistent, suggesting a relocation screw up.
Brian, do you still have this issue with latest drmtip?
If problem exists with latest drm-tip, set kernel parameters drm.debug=0x1e log_buf_len=4M and reboot.
Try to reproduce the issue and attach the dmesg log.
Due to lack of activity in this bug report I had to RMA the system. Couldn't wait any longer. So I no longer have the system to test with.
Since the setup is no longer available to reproduce the issue with drmtip, Closing this bug.