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

**URL:** <https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675>\
**Category:** Linux\
**Created:** [July 27, 2022, 9:50pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675 "2022-07-27T21:50:43Z")\
**Posts on this page:** 20\
**Page:** 24

<div class="post-metadata">

**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\
**Post date:** [April 13, 2023, 5:43pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/467 "2023-04-13T17:43:33Z")

</div>

Please keep updating. Thus far, so good! 🙂

---

<div class="post-metadata">

**Author:** ![Fraoch](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/fraoch/32/6364_2.png) [@Fraoch](https://community.frame.work/u/Fraoch)\
**Post date:** [April 19, 2023, 1:07pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/468 "2023-04-19T13:07:38Z")

</div>

A post was merged into an existing topic: [[SOLVED] Ubuntu 22.04.2 with Kernel 5.19 =\> fan noise issues at low load](https://community.frame.work/t/solved-ubuntu-22-04-2-with-kernel-5-19-fan-noise-issues-at-low-load/27646/16)

---

<div class="post-metadata">

**Author:** ![Mathieson\_Sterling](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mathieson_sterling/32/15105_2.png) [@Mathieson\_Sterling](https://community.frame.work/u/Mathieson_Sterling)\
**Post date:** [April 21, 2023, 7:09pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/469 "2023-04-21T19:09:24Z")

</div>

1. Pop! OS 22.04
2. #202303130630~1681329778~22.04~d824cd4 SMP PREEMPT\_DYNAMIC Wed A
3. nope, stock
4. WD\_BLACK™ SN850X NVMe
5. Web browsing (Brave) or using Obsidian.

---

<div class="post-metadata">

**Author:** ![vhx](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@vhx](https://community.frame.work/u/vhx)\
**Post date:** [May 2, 2023, 4:49pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/470 "2023-05-02T16:49:16Z")

</div>

been using F38 KDE with removed psr=0 since it went final last week; so far all good. Plenty of media playback from various sources without issue.

---

<div class="post-metadata">

**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\
**Post date:** [May 2, 2023, 5:13pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/471 "2023-05-02T17:13:54Z")

</div>

> [@vhx](#):
>
> been using F38 KDE with removed psr=0 since it went final last week; so far all good. Plenty of media playback from various sources without issue.

Across the board, seems like 38 has been stellar. I’m very happy with it.

---

<div class="post-metadata">

**Author:** ![snoopdouglas](https://avatars.discourse-cdn.com/v4/letter/s/df788c/32.png) [@snoopdouglas](https://community.frame.work/u/snoopdouglas)\
**Post date:** [May 31, 2023, 7:20pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/472 "2023-05-31T19:20:51Z")

</div>

Hi, I’ve just experienced some occasional freezes and jitters on F38 (kernel `6.2.15-300.fc38.x86_64`) with my 12th gen Framework - so it doesn’t appear to have gone away just yet.

`psr=0` does seem to have eliminated them so far, though.

---

<div class="post-metadata">

**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\
**Post date:** [May 31, 2023, 10:01pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/473 "2023-05-31T22:01:17Z")

</div>

> [@snoopdouglas](#):
>
> `psr=0` does seem to have eliminated them so far, though.

Bringing in @Loell_Framework to this conversation.

@snoopdouglas You indicated that the kernel parameter psr=0 seems to be helping. Is this 11th or 12th gen Framework 13?

---

<div class="post-metadata">

**Author:** ![Loell\_Framework](https://avatars.discourse-cdn.com/v4/letter/l/9f8e36/32.png) [@Loell\_Framework](https://community.frame.work/u/Loell_Framework)\
**Post date:** [May 31, 2023, 10:26pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/474 "2023-05-31T22:26:58Z")

</div>

hi @snoopdouglas ,

will try and check this on a 11th and 12th gen with F38 and see how psr=0 parameter goes.

---

<div class="post-metadata">

**Author:** ![snoopdouglas](https://avatars.discourse-cdn.com/v4/letter/s/df788c/32.png) [@snoopdouglas](https://community.frame.work/u/snoopdouglas)\
**Post date:** [May 31, 2023, 10:50pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/475 "2023-05-31T22:50:16Z")

</div>

@Loell_Framework - 12th gen as I said in my previous post. I had an 11th gen mainboard before, and should note that I only started experiencing jitters/freezes after the upgrade. dmesg output is consistent with the bug reports on the [DRI issue](https://gitlab.freedesktop.org/drm/intel/-/issues/6916).

(Edited as Loell is handling this - Matt)

---

<div class="post-metadata">

**Author:** ![snoopdouglas](https://avatars.discourse-cdn.com/v4/letter/s/df788c/32.png) [@snoopdouglas](https://community.frame.work/u/snoopdouglas)\
**Post date:** [June 2, 2023, 9:24am UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/476 "2023-06-02T09:24:20Z")

</div>

@Loell_Framework Kernel `6.3.4-201.fc38.x86_64` has just been released; I’m now using that without `psr=0` and the symptoms _appear_ to have disappeared, having used it for ~24h. Will update if they reappear.

---

<div class="post-metadata">

**Author:** ![Fred\_Welland](https://avatars.discourse-cdn.com/v4/letter/f/b2d939/32.png) [@Fred\_Welland](https://community.frame.work/u/Fred_Welland)\
**Post date:** [June 2, 2023, 10:55am UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/477 "2023-06-02T10:55:03Z")

</div>

Long term update: I maybe I had some freeze issues related to psr=0 and maybe even intel\_idle settings; but things turned out different for me.

Not a framework laptop, but one with 12th Gen Intel(R) Core™ i7-1260P, but very similar symptoms as noted in this thread. Laptop started with fedora 37 and jumped ship to fedora 38 – terrible freezing and outright total crashes for months!

I am currently 100% fixed, with nearly 2 weeks of absolutely no problems and NO kernel boot parameters. Using all features of laptop – thunderbolt/usb-c hub with PDS, bluetooth, driving 2 monitors, USB A keyboard, USB A wireless mouse, usb ethernet and/or wifi, webcam too. Everything is just working.

FWIW current kernel: 6.2.15-300.fc38.x86\_64.

What was the problem? Well I am certain there was some kernel driver issues related to the 12th Gen intel stuff, early on. I feel those were probably addressed a while back, probably with advent of Fedora 38. After a particular knarly crash and spying some log artifacts that said something about ‘memory’, I ran a memory test (memtest86+) several times – all were very very negative. A pair of new DIMMs later and many positive memtest86+ runs, everything has been great!

YMMV – but this thread has been a valuable resource for me during this effort.

---

<div class="post-metadata">

**Author:** ![Loell\_Framework](https://avatars.discourse-cdn.com/v4/letter/l/9f8e36/32.png) [@Loell\_Framework](https://community.frame.work/u/Loell_Framework)\
**Post date:** [June 2, 2023, 9:11pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/478 "2023-06-02T21:11:02Z")

</div>

Thank you for sharing a valuable insight @Fred_Welland , especially taking note on kernel 6.2.15-300.fc38.x86\_64. 😊

---

<div class="post-metadata">

**Author:** ![Jason\_Axelson](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/jason_axelson/32/11342_2.png) [@Jason\_Axelson](https://community.frame.work/u/Jason_Axelson)\
**Post date:** [June 17, 2023, 6:12pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/479 "2023-06-17T18:12:45Z")

</div>

> [@Fred\_Welland](#):
>
> What was the problem? Well I am certain there was some kernel driver issues related to the 12th Gen intel stuff, early on. I feel those were probably addressed a while back, probably with advent of Fedora 38. After a particular knarly crash and spying some log artifacts that said something about ‘memory’, I ran a memory test (memtest86+) several times – all were very very negative. A pair of new DIMMs later and many positive memtest86+ runs, everything has been great!

Out of curiosity how long did you run each of those memtest86+ runs? I’ve been suffering from what seems like the symptoms in this thread (12th gen + Linux Mint) to the point that my Framework laptop is unusable (~50% crash rate within 5 minutes, ~90% within 30 minutes). But for me a memtest run overnight did not detect a memory issue.

After ~3 weeks of not using my laptop at all (due to the freezing) I just upgraded all the packages and I’m now running kernel 6.2.16-060216-generic x86\_64. Hopefully the crash will be gone now

---

<div class="post-metadata">

**Author:** ![Fred\_Welland](https://avatars.discourse-cdn.com/v4/letter/f/b2d939/32.png) [@Fred\_Welland](https://community.frame.work/u/Fred_Welland)\
**Post date:** [June 17, 2023, 7:27pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/480 "2023-06-17T19:27:58Z")

</div>

The negatve tests were pretty quick to go negative. I’d say within 1 or 2 minutes of starting the memtest86+ basic run I would start getting failures. That pattern was repeatable; I probably did 6 runs all negative before concluding I had a bad dim or dims. Each run, when I let it complete was maybe like 10 mins before completion with summary report.

The economics were such that  
I replaced the 2x8 pair with 2x16 pair.

Those (positive ) runs did seem to take longer but didnt seem like 2x the 16gb runs (perhaps error reporting slowed things down??) ; so maybe like 15 mins or so.

I probably did 6 or 8 of those success runs; beforeconcluding the mem issue was whipped.

I then just dove into full on testing with f38. I have had no crashes since (and few days before; I delayed my posting to ensure my issue was addressed) that time.

HtH

Note i never did any of more advanced test runs offered by mt86+. Also maybe 4 weeks prior i did run a user space memchecker that i googled up. That ran clean. There is some www noise about effectiveness of that tool. I actualy dont recall the name.

---

<div class="post-metadata">

**Author:** ![Jason\_Axelson](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/jason_axelson/32/11342_2.png) [@Jason\_Axelson](https://community.frame.work/u/Jason_Axelson)\
**Post date:** [June 19, 2023, 5:02am UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/481 "2023-06-19T05:02:54Z")

</div>

Thanks for the additional information! Unfortunately I’m still getting crashes, I’ll try running memtest again, although my suspicion is that something else is causing the issue for me.

---

<div class="post-metadata">

**Author:** ![xidiot](https://avatars.discourse-cdn.com/v4/letter/x/e9bcb4/32.png) [@xidiot](https://community.frame.work/u/xidiot)\
**Post date:** [July 19, 2023, 1:04pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/482 "2023-07-19T13:04:38Z")

</div>

@Jason_Axelson, for me I think I’ve isolated the issue to a USB-C multiport HUB 49140, which I use for my 2nd monitor and to charge the laptop itself:  
Manufacturer: LENOVO  
Product Name: 21E30086BM  
Version: ThinkPad E14 Gen

Architecture: x86\_64  
CPU op-mode(s): 32-bit, 64-bit  
Address sizes: 39 bits physical, 48 bits virtual  
Byte Order: Little Endian  
CPU(s): 12  
On-line CPU(s) list: 0-11  
Vendor ID: GenuineIntel  
Model name: 12th Gen Intel(R) Core™ i5-1235U  
CPU family: 6  
Model: 154

---

<div class="post-metadata">

**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\
**Post date:** [July 19, 2023, 4:22pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/483 "2023-07-19T16:22:38Z")

</div>

Appreciate everyone’s updates here.

---

<div class="post-metadata">

**Author:** ![amDude](https://avatars.discourse-cdn.com/v4/letter/a/bbe5ce/32.png) [@amDude](https://community.frame.work/u/amDude)\
**Post date:** [July 26, 2023, 2:23am UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/484 "2023-07-26T02:23:30Z")

</div>

For me this freezing bug with the black screen only happens if GPU-Hardware-Acceleration is activated. I use an AMD RX 6700 XT with current mesa-git on Manjaro.

This bug also happens in the complete Kernel 6.x Series if Hardware-Acceleration is activated, but it doesn’t happen in Kernel 5.15.x. So Kernel 5.15.x is working fine.

I hope this somehow helps.

---

<div class="post-metadata">

**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\
**Post date:** [July 26, 2023, 5:30pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/485 "2023-07-26T17:30:43Z")

</div>

> [@amDude](#):
>
> Kernel 5.15.x. So Kernel 5.15.x is working fine.

That is some legacy LTS kernel action there - assuming Ubuntu?

---

<div class="post-metadata">

**Author:** ![amDude](https://avatars.discourse-cdn.com/v4/letter/a/bbe5ce/32.png) [@amDude](https://community.frame.work/u/amDude)\
**Post date:** [July 26, 2023, 7:27pm UTC](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675/486 "2023-07-26T19:27:38Z")

</div>

I am sorry, i just can say i use 5.15.x with Manjaro Cinnamon Edition and it don’t cause the freezing bug like in the 6.x. Kernel line.

[Previous page](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675.md?page=23)

[Next page](https://community.frame.work/t/tracking-hard-freezing-on-fedora-36-with-the-new-12th-gen-system/20675.md?page=25)
