Ubuntu 21.04 crashes frequently

Framework Laptop 13
1

Just got my Batch 4 Framework, super impressed with the hardware so far.

Unfortunately I am getting constant crashes/random restarts while using Ubuntu.

Configuration:

Framework DIY Edition
Processor: Intel i7-1165G7 (12M Cache, up to 4.70 GHz)
Memory: GSkill 32GBx2 DDR4
(Serial Number: 00826543, Asset Tag: 9876543210, Part Number: F4-3200C22-32GRS)

Here’s the output of journalctl -b -2 -e

Oct 23 19:14:17 typon-Laptop kernel: check: Corrupted low memory at 00000000eefc7d0f (1b50 phys) = 400000000000
Oct 23 19:14:17 typon-Laptop kernel: check: Corrupted low memory at 00000000e98ec54e (1b58 phys) = 400000000000
Oct 23 19:14:17 typon-Laptop kernel: check: Corrupted low memory at 00000000e5e6bf91 (1bd0 phys) = 20000000000
Oct 23 19:14:17 typon-Laptop kernel: check: Corrupted low memory at 000000005ff7522a (1be0 phys) = 800000000000
Oct 23 19:14:17 typon-Laptop kernel: check: Corrupted low memory at 0000000096de9800 (1be8 phys) = a00000000000
Oct 23 19:14:17 typon-Laptop kernel: ------------[ cut here ]------------
Oct 23 19:14:17 typon-Laptop kernel: Memory corruption detected in low memory
Oct 23 19:14:17 typon-Laptop kernel: WARNING: CPU: 1 PID: 5243 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0
Oct 23 19:14:17 typon-Laptop kernel: Modules linked in: apple_mfi_fastcharge rfcomm ccm cmac algif_hash algif_skcipher af_alg snd_hda_codec_hdmi snd_hda_codec_realtek snd_h>
Oct 23 19:14:17 typon-Laptop kernel:  snd videobuf2_common kfifo_buf btrtl hid_sensor_iio_common intel_cstate btbcm drm_kms_helper industrialio btintel videodev cec rc_core>
Oct 23 19:14:17 typon-Laptop kernel:  pinctrl_tigerlake
Oct 23 19:14:17 typon-Laptop kernel: CPU: 1 PID: 5243 Comm: kworker/1:0 Not tainted 5.11.0-38-generic #42-Ubuntu
Oct 23 19:14:17 typon-Laptop kernel: Hardware name: Framework Laptop/FRANBMCP06, BIOS 03.02 07/01/2021
Oct 23 19:14:17 typon-Laptop kernel: Workqueue: events check_corruption
Oct 23 19:14:17 typon-Laptop kernel: RIP: 0010:check_for_bios_corruption+0xb1/0xc0
Oct 23 19:14:17 typon-Laptop kernel: Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d 5e f5 e8 01 00 75 ed 48 c7 c7 28 fe 9a 94 c6 05 4e f5 e8 01 01 e8 8f 0a b6 00 <0f>
Oct 23 19:14:17 typon-Laptop kernel: RSP: 0018:ffffbbb382b27e40 EFLAGS: 00010286
Oct 23 19:14:17 typon-Laptop kernel: RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffff9814afa58ac8
Oct 23 19:14:17 typon-Laptop kernel: RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffff9814afa58ac0
Oct 23 19:14:17 typon-Laptop kernel: RBP: ffffbbb382b27e60 R08: 0000000000000000 R09: ffffbbb382b27c20
Oct 23 19:14:17 typon-Laptop kernel: R10: ffffbbb382b27c18 R11: ffffffff951535e8 R12: ffff980440010000
Oct 23 19:14:17 typon-Laptop kernel: R13: ffff980440010000 R14: 0000000080000000 R15: ffff9814afa6bd00
Oct 23 19:14:17 typon-Laptop kernel: FS:  0000000000000000(0000) GS:ffff9814afa40000(0000) knlGS:0000000000000000
Oct 23 19:14:17 typon-Laptop kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 23 19:14:17 typon-Laptop kernel: CR2: 00007f774fd57000 CR3: 0000000247a10005 CR4: 0000000000770ee0
Oct 23 19:14:17 typon-Laptop kernel: PKRU: 55555554
Oct 23 19:14:17 typon-Laptop kernel: Call Trace:
Oct 23 19:14:17 typon-Laptop kernel:  check_corruption+0xe/0x40
Oct 23 19:14:17 typon-Laptop kernel:  process_one_work+0x220/0x3c0
Oct 23 19:14:17 typon-Laptop kernel:  worker_thread+0x50/0x370
Oct 23 19:14:17 typon-Laptop kernel:  kthread+0x11f/0x140
Oct 23 19:14:17 typon-Laptop kernel:  ? process_one_work+0x3c0/0x3c0
Oct 23 19:14:17 typon-Laptop kernel:  ? set_kthread_struct+0x50/0x50
Oct 23 19:14:17 typon-Laptop kernel:  ret_from_fork+0x1f/0x30
Oct 23 19:14:17 typon-Laptop kernel: ---[ end trace b69ac849bf56b1fe ]---
Oct 23 19:14:19 typon-Laptop wpa_supplicant[615]: wlp170s0: CTRL-EVENT-BEACON-LOSS
Oct 23 19:14:19 typon-Laptop wpa_supplicant[615]: wlp170s0: CTRL-EVENT-BEACON-LOSS
Oct 23 19:14:26 typon-Laptop wpa_supplicant[615]: wlp170s0: CTRL-EVENT-BEACON-LOSS
Oct 23 19:14:27 typon-Laptop wpa_supplicant[615]: wlp170s0: CTRL-EVENT-BEACON-LOSS
Oct 23 19:14:27 typon-Laptop systemd[1]: Condition check resulted in Daily apt upgrade and clean activities being skipped.
Oct 23 19:14:27 typon-Laptop wpa_supplicant[615]: wlp170s0: CTRL-EVENT-BEACON-LOSS
Oct 23 19:14:27 typon-Laptop wpa_supplicant[615]: wlp170s0: CTRL-EVENT-BEACON-LOSS
Oct 23 19:14:29 typon-Laptop kernel: usb 3-6: USB disconnect, device number 9
Oct 23 19:14:40 typon-Laptop wpa_supplicant[615]: wlp170s0: CTRL-EVENT-BEACON-LOSS
Oct 23 19:14:44 typon-Laptop systemd[1462]: Reached target Bluetooth.
Oct 23 19:14:44 typon-Laptop bluetoothd[575]: profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info

Looks like a memory corruption issue?

1 Like
2

Mmm. The memory you have looks like it doesn’t rely on XMP, so that’s good. Not sure what’s happening, I’m afraid. I went with one of the officially recommened ram cards. I guess you should just double-check that it’s seated correctly.

3

Try testing the laptop with only one of the ram sticks installed, then test it with the other. If it crashes with only one of the sticks but not the other, then it looks like you have a bad ram stick

3 Likes
4

Get https://www.memtest86.com/ on a USB drive and let it run to confirm that it’s not a bad memory module.

1 Like
5

yeah I would first run memtest just to be sure it wasn’t some conflict with your install (not that a stock 21.04 should have any problems that significant)

6

I second the memtest86 post from @hspak above. It may take a few hours to fully run, but it will save you a lot of hassle in the long term. My DIY edition order came with 2x 16GB modules from Crucial, but one of them failed memtest and had to be returned.

Also, my experience getting a replacement was a little bizarre. Framework asked me to contact Crucial directly for returns, and the first reply I got from Crucial told me to ignore memtest and trying running with the bad module anyway. I replied asking for more information on what about the memtest results I sent them indicated it was a false positive, and the next reply I got ignored my question and just gave me an RMA number and shipping address, and I was able to get a replacement (and the replacement tested fine).

2 Likes
7

Thanks for the suggestions. I will try memtest and get back to you guys.

8

I use xubuntu 21.04 and whatever is the latest non-rc mainline-ppa kernel and never see a crash.

I’m using 2x32g ram supplied by Framework.

So, just to supply a data point that it’s probably nothing inherently incompatible in ubuntu 21.04

9

Reporting back…

I ran 4 passes of memtest for 8 hours total…found 0 errors.

Looks like the memory isn’t corrupt…

10

So the hardware is probably ok, and the OS is compatible. Whatever it is, you have to figure it out. It’s either some other piece of hardware besides ram & cpu that is tickled in normal operation but not in memtest86, an overheating issue, or some other piece of software. I’ve been running 21.04 and now 21.10 this whole time without a single crash ever. You’ll have to do things like run with all usb-c devices unplugged, remove the wifi card (us a usb etherne or usb wifi for a while), run a live distro of some other distro for a while, stuff like that.

Or: Kernel Crash Dump | Ubuntu