[TRACKING] Hard freezing on Fedora 36 with the new 12th gen system

Framework Laptop 13 Linux
285

I don’t know if this will add something useful to the discussion here but hopefully all small details count.

I just experienced another freeze in the gnome settings in debian sid with a 12th gen frame.work laptop.

keyboard and mouse seemed to be non-responsive, the sound (music) was still going and I could hear my fan running at maximum.

I was able to ssh into the laptop from another computer. from there I could see in dmesg a line mentioning “GPU HANG” like mentioned in #24. the process gnome-shell was running at 100% cpu and when I straced it I could see the following line coming out repeatedly very fast:

ioctl(12, DRM_IOCTL_SYNCOBJ_WAIT, 0x7fff22383b40) = 0

Then I used kill -9 on the gnome-shell process and got brought back to gdm on the laptop so I could start using it again.

286

@Fred_Welland Hmm, I’ve been on my 12th gen all day, and here is what I have. Flawless performance.

1 Like
287

Finally had some sort of error, but unless this repeats itself, I don’t think it’s worth noting. Connected to AC power, wifi showed connected and then fell down.

If this error repeats, I’ll note it to the Fedora devs.

iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
iwlwifi 0000:00:14.3: Transport status: 0x0000004A, valid: 6
iwlwifi 0000:00:14.3: Loaded firmware version: 72.daa05125.0 so-a0-hr-b0-72.ucode
iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL    
iwlwifi 0000:00:14.3: 0x00808210 | trm_hw_status0
iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
iwlwifi 0000:00:14.3: 0x004D8C8A | branchlink2
iwlwifi 0000:00:14.3: 0x004D769A | interruptlink1
iwlwifi 0000:00:14.3: 0x004D769A | interruptlink2
iwlwifi 0000:00:14.3: 0x00015114 | data1
iwlwifi 0000:00:14.3: 0x00000010 | data2
iwlwifi 0000:00:14.3: 0x00000000 | data3
iwlwifi 0000:00:14.3: 0x8AC18C68 | beacon time
iwlwifi 0000:00:14.3: 0x5801462D | tsf low
iwlwifi 0000:00:14.3: 0x000000E8 | tsf hi
iwlwifi 0000:00:14.3: 0x00000000 | time gp1
iwlwifi 0000:00:14.3: 0xA61A69AA | time gp2
iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
iwlwifi 0000:00:14.3: 0x00000048 | uCode version major
iwlwifi 0000:00:14.3: 0xDAA05125 | uCode version minor
iwlwifi 0000:00:14.3: 0x00000370 | hw version
iwlwifi 0000:00:14.3: 0x00489002 | board version
iwlwifi 0000:00:14.3: 0x802AFC03 | hcmd
iwlwifi 0000:00:14.3: 0x24020000 | isr0
iwlwifi 0000:00:14.3: 0x01000000 | isr1
iwlwifi 0000:00:14.3: 0x48F00002 | isr2
iwlwifi 0000:00:14.3: 0x00C3080C | isr3
iwlwifi 0000:00:14.3: 0x00000000 | isr4
iwlwifi 0000:00:14.3: 0x058F001C | last cmd Id
iwlwifi 0000:00:14.3: 0x00015114 | wait_event
iwlwifi 0000:00:14.3: 0x00000080 | l2p_control
iwlwifi 0000:00:14.3: 0x00010034 | l2p_duration
iwlwifi 0000:00:14.3: 0x0000003F | l2p_mhvalid
iwlwifi 0000:00:14.3: 0x00CE18B8 | l2p_addr_match
iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
iwlwifi 0000:00:14.3: 0x00000000 | timestamp
iwlwifi 0000:00:14.3: 0x0000284C | flow_handler
iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
iwlwifi 0000:00:14.3: Transport status: 0x0000004A, valid: 7
iwlwifi 0000:00:14.3: 0x20003463 | ADVANCED_SYSASSERT
iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
iwlwifi 0000:00:14.3: 0x8045E934 | umac branchlink2
iwlwifi 0000:00:14.3: 0x804694E2 | umac interruptlink1
iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
iwlwifi 0000:00:14.3: 0x5801461F | umac data1
iwlwifi 0000:00:14.3: 0xA61A699B | umac data2
iwlwifi 0000:00:14.3: 0xB2BF92AD | umac data3
iwlwifi 0000:00:14.3: 0x00000048 | umac major
iwlwifi 0000:00:14.3: 0xDAA05125 | umac minor
iwlwifi 0000:00:14.3: 0xA61A69A4 | frame pointer
iwlwifi 0000:00:14.3: 0xC0885DA8 | stack pointer
iwlwifi 0000:00:14.3: 0x008C010D | last host cmd
iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
iwlwifi 0000:00:14.3: IML/ROM dump:
iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state
iwlwifi 0000:00:14.3: 0x00004FE3 | IML/ROM data1
iwlwifi 0000:00:14.3: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0
iwlwifi 0000:00:14.3: Fseq Registers:
iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE
iwlwifi 0000:00:14.3: 0x80350002 | FSEQ_TOP_INIT_VERSION
iwlwifi 0000:00:14.3: 0x00150000 | FSEQ_CNVIO_INIT_VERSION
iwlwifi 0000:00:14.3: 0x0000A482 | FSEQ_OTP_VERSION
iwlwifi 0000:00:14.3: 0x00000003 | FSEQ_TOP_CONTENT_VERSION
iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
iwlwifi 0000:00:14.3: 0x00080400 | FSEQ_CNVI_ID
iwlwifi 0000:00:14.3: 0x01300504 | FSEQ_CNVR_ID
iwlwifi 0000:00:14.3: 0x00080400 | CNVI_AUX_MISC_CHIP
iwlwifi 0000:00:14.3: 0x01300504 | CNVR_AUX_MISC_CHIP
iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
288

Thanks @Gabriel_Filion, different distro and likely different with a number of libraries as well since it’s Debian (not sure which version). But I would agree that GNOME has seen some issues that will likely see solutions in the updates.

289

Also worth noting and likely why I’ve had a great experience - Fedora Freezes and Flickering on newer Kernels - #40 by nadb

This is Fedora 37 and matches my config.

290

Another item to look at when testing is extensions. Turn them all off first and then slowly add. A lot of these troubles are just reminiscent of other issues I have seen elsewhere and quite often they are tied to dash-to-panel, desktop icon related extension, system tray type extensions, anything moving the dash elsewhere or adding old functionality is more likely to create, contirbute, or enhance graphics related issues.

2 Likes
291

Completely agree, it’s been on my growing list as well. Because as you point out, create, contribute to, or enhance graphics related issues.

100% agree.

1 Like
292

@Matt_Hartley you should try using chrome or something chromium based on your framework laptop.

I don’t think I’ve had a hard freeze while using only firefox. But switching to chrome will trigger one. I also noticed some weird things related to plugging in power.

293

Hi @Kelby_Faessler, no freezing on mine. Other users. :slight_smile:

Thanks for the insights you’ve noted, appreciated!

294

No such issues with Chromium or Vivaldi, with Firefox running with Discord Video going.

Additional Info: I am using a dock with two external hdmi monitors at 1920x1080. Intel i7-1260p, 64GB RAM, P41 SK Hynix NVME. Experiencing no issues at this time on battery or on AC. Fedora 37 (updated daily for now), Wayland, Gnome. Have not had a hard freeze in two weeks now.

295

This looks like Screen freeze because gnome-shell waits DRM_IOCTL_SYNCOBJ_WAIT forever in Wayland mode when resource is tight (#6851) · Issues · drm / intel · GitLab , which seems to be one possible cause of the freezes, but there are freezes unrelated to this.

296

Thanks @real_or_random it does seem similar. I’ll keep an eye on that.

297

Currently trying to run with minimal extensions and without the i915 kernel option. So far ran for a good couple hours with Chrome, Discord w/ video and screen share, and more without any issue. Perhaps my two graphical extensions have some connection to the freezes I’ve been experiencing. :thinking:

1 Like
298

Out of curiosity which extensions did you turn off?

299

I don’t use any extensions and I still get freezes

300

Initially all but eventually turned all back on except “Gnome 4x UI Improvements” and “Blur my Shell”. My finding are unfortunately inconclusive and out of convenience I re-enabled the i915 fix.

1 Like
301

And re-enabling the i915 fix provides you with a workaround until this issue is resolved? (Tracking this issue actively, so asking obvious questions).

302

mine threw it’s toys out of the pram earlier. 2 different youtube videos were crashing firefox every 5-10mins (using hw acceleration).
switched to safe mode (software render/hw accel off) and it was stable over 25-30min video.
switched back to normal firefox (hw accel on) and so far no problems even with the same first 2 videos.
only thing different is starting firefox via cmdline vs the launcher menu.

very frustrating i cant reproduce since it was so prominent 60-90mins ago.

as a reminder on my system; i’m on F37 KDE, fully patched with the 3.06beta bios. no changes like psr/i915 tweaks; out of box config in that respect.

it’s also taken me a long time to experience any further issues since my last reply - weeks since since i last had issues and I’ve considered things are fixed for me. bit suspicous i’ve done both OS updates and bios updates today, but could jus tbe coincidence.

303

@vhx Appreciate the detail here. And are you using a dock with external displays? I am trying to find the common thread here as mine Framework 11th and 12th connected directly from expansion cards over HDMI have not given me any issues with a fully up to date Fedora 37 GNOME.

304

yes to a dock with 1x external screen using the docks HDMI connection.
specifically the Anker 341 https://www.amazon.co.uk/gp/product/B07ZVKTP53/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1.
display is a Gigabyte FI27Q.

in a way, i wish the crashing would be more frequent. it’d be a lot easier to test with&without a dock. i’ll try to remember to disconnect the dock if it happens again and test purely with the laptop.

I’d like to clarify my issue in my last reply: the laptop remains running - no hard freeze or system crash. Just Firefox freezing for 1-2secs and then disappears. restart Firefox and it does the usual "firefox unexpectedly closed, do you wish to restore your tabs). Literally nothing in dmesg, journalctl or abnormal system behaviour to even hint at where the issue could coming from.
Firefox is triggering an abrt report. nothing obvious sticks out as the cause and they dont seem to like being sucessfully reported due to low quality info

1 Like