Random freezes

kcaps

Sun Mar 15, 2020 10:39:09 am

While using the laptop (zorin 15) occasionally the desktop freezes completely, requiring a hard reboot. Sometimes it happens once a week and other times 4 times in an hour. Is there any known issue that causes this? I have not been able to find anything useful, only a post about ubuntu, and their fix wasn't relevant, they said to delete a certain file but it did not exist for me anyway..
There is also this post: https://askubuntu.com/questions/761706/ ... g-randomly which suggests editing my grub file, but my system does not currently take any changes from there. I am thinking of perhaps clean reinstalling the whole OS.

Aravisian

Sun Mar 15, 2020 11:31:16 am

kcaps wrote: which suggests editing my grub file, but my system does not currently take any changes from there.

Can you explain this statement? Because your system absolutely should be taking changes from the grub file.

kcaps wrote:I am thinking of perhaps clean reinstalling the whole OS.

I often suggest to people that they Do Not Fear the Reinstall. (It is much easier on Linux!) Having been through a great many of them (94% of them caused by my own faults), I have learned to appreciate them and to back up regularly (Something I was actually doing when I got bored waiting on a file to compress and checked the forum).

That being said:
What version Kernel are you currently running?
Are your updates set to the Main Server?
Are you running Zorin 15 or Zorin 15.2?
If 15, when was your last update...
What chipset and what graphics card are you currently using on that machine?

kcaps

Sun Mar 15, 2020 5:01:17 pm

Aravisian wrote:Can you explain this statement? Because your system absolutely should be taking changes from the grub file.

I explained it a few months back in this post. The last post in the thread is the resolution. SInce then I haven't monkeyed around with grub at all.
viewtopic.php?f=5&t=15238&p=68566#p68566

Aravisian wrote:
I often suggest to people that they Do Not Fear the Reinstall. (It is much easier on Linux!) Having been through a great many of them (94% of them caused by my own faults), I have learned to appreciate them and to back up regularly (Something I was actually doing when I got bored waiting on a file to compress and checked the forum).

I don't mind wiping, I can backup my ~ and installed packages. I'm just lazy so if there's no point there's no point.

Aravisian wrote:
That being said:
What version Kernel are you currently running?
Are your updates set to the Main Server?
Are you running Zorin 15 or Zorin 15.2?
If 15, when was your last update...
What chipset and what graphics card are you currently using on that machine?

Code:: uname -a : Linux zenbook-zorin 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Don't know how too check other than:

Code:: sudo apt update: Hit:1 http://ppa.launchpad.net/zorinos/apps/ubuntu bionic InRelease Hit:2 http://il.archive.ubuntu.com/ubuntu bionic InRelease Get:3 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Get:4 http://il.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Hit:5 http://ppa.launchpad.net/zorinos/drivers/ubuntu bionic InRelease Get:6 https://packages.microsoft.com/repos/ms-teams stable InRelease [17.5 kB] Hit:7 http://ppa.launchpad.net/zorinos/patches/ubuntu bionic InRelease Hit:8 https://packages.zorinos.com/stable bionic InRelease Get:9 http://il.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:10 https://packages.microsoft.com/repos/ms-teams stable/main amd64 Packages [5,169 B] Get:11 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 DEP-11 Metadata [2,464 B] Hit:12 https://packages.zorinos.com/patches bionic InRelease Get:13 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 Metadata [42.1 kB] Hit:14 http://ppa.launchpad.net/zorinos/stable/ubuntu bionic InRelease Get:15 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11 Metadata [307 kB] Get:16 http://security.ubuntu.com/ubuntu bionic-security/universe DEP-11 48x48 Icons [16.4 kB] Get:17 http://security.ubuntu.com/ubuntu bionic-security/universe DEP-11 64x64 Icons [111 kB] Hit:18 https://packages.zorinos.com/apps bionic InRelease Get:19 http://security.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 Metadata [38.5 kB] Hit:20 https://packages.zorinos.com/drivers bionic InRelease Get:21 http://security.ubuntu.com/ubuntu bionic-security/main DEP-11 48x48 Icons [17.6 kB] Get:22 http://security.ubuntu.com/ubuntu bionic-security/main DEP-11 64x64 Icons [41.5 kB] Hit:23 https://packages.zorinos.com/premium bionic InRelease Get:24 http://il.archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 48x48 Icons [73.8 kB] Get:25 http://il.archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 64x64 Icons [140 kB] Get:26 http://il.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 DEP-11 Metadata [265 kB] Get:27 http://il.archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 48x48 Icons [203 kB] Get:28 http://il.archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 64x64 Icons [470 kB] Get:29 http://il.archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 DEP-11 Metadata [2,468 B] Get:30 http://il.archive.ubuntu.com/ubuntu bionic-backports/universe amd64 DEP-11 Metadata [7,980 B]

Running 15, updated yesterday but usually update daily or at least multiple times per week.
Intel core 17 8th gen, intel UHD 620 gpu, that's pretty much all I know about the hardware.

Aravisian

Mon Mar 16, 2020 3:38:28 am

kcaps wrote:
Aravisian wrote:Can you explain this statement? Because your system absolutely should be taking changes from the grub file.

I explained it a few months back in this post. The last post in the thread is the resolution. SInce then I haven't monkeyed around with grub at all.
viewtopic.php?f=5&t=15238&p=68566#p68566

Ok, I do not see anything there that might suggest that your system does not accept changes in Grub. The opposite, actually.

kcaps wrote:I don't mind wiping, I can backup my ~ and installed packages. I'm just lazy so if there's no point there's no point.

-chuckle- I hear you on this one...

kcaps wrote:

Code:

uname -a : Linux zenbook-zorin 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Ok, so Intel integrated graphics and you are running the latest Kernel for Zorin.
You may try rolling back your kernel. Azorin gave a quick guide here:
viewtopic.php?f=5&t=15294&p=70441#p70441

Could be worth a shot.

Aside from that, the grub alteration you referenced in your previous post relates to intel chipsets and graphics.

kcaps

Mon Mar 16, 2020 10:04:57 am

Aravisian wrote:Ok, I do not see anything there that might suggest that your system does not accept changes in Grub. The opposite, actually.

I can't use the standard grub "GRUB_CMDLINE_LINUX_DEFAULT=" (Which does include the suggested fix anyway, which means it either doesnt help in my case or the system is not actually taking the grub values other than recordfail timeout) because grub doesn't enter that part of the code. Instead it gets a recordfail, so I set the timeout to 1. How do I set the cmdline even through recordfail?

Aravisian wrote:You may try rolling back your kernel. Azorin gave a quick guide here:
viewtopic.php?f=5&t=15294&p=70441#p70441

Could be worth a shot.

This has been happening since the beginning, I doubt an older version would help.. I think that clean installing 15.2 would be a better chance of success, no?

Aravisian wrote:Aside from that, the grub alteration you referenced in your previous post relates to intel chipsets and graphics.

I'm sorry, I don't know what you mean.

Aravisian

Mon Mar 16, 2020 10:35:53 am

kcaps wrote:
Aravisian wrote:Ok, I do not see anything there that might suggest that your system does not accept changes in Grub. The opposite, actually.

I can't use the standard grub "GRUB_CMDLINE_LINUX_DEFAULT=" (Which does include the suggested fix anyway, which means it either doesnt help in my case or the system is not actually taking the grub values other than recordfail timeout) because grub doesn't enter that part of the code. Instead it gets a recordfail, so I set the timeout to 1. How do I set the cmdline even through recordfail?

Ah, ok. I am following you, now.
Your computer does use grub, but is Not Responsive to that particular fix. Recordfail: If you are using a system with only one installed O.S. (not dual boot), LVM (Logical Volume Management) and UEFI (Ubinified extensible interface-all three conditions), then this can happen.
The purpose of it is basically an override, because without it, you would be unable to get Advanced Grub to appear if you needed it. It is actually a forced script that interferes with grub.
So, before going much further: Are you in fact using UEFI, LVM and have only one O.S. installed?

kcaps wrote:This has been happening since the beginning, I doubt an older version would help..

In that case, my suggestion would probably not help. I am not sure which kernel you had loaded at the beginning (it may have been kernel 5.0 whereas the above suggestion would roll back to 4.15.0-74... I think). However, the comments just above this line suggests there may be something else going on here.

kcaps wrote:I think that clean installing 15.2 would be a better chance of success, no?

Honestly... It is what I would do if it was me. It has a good chance of success and it MAY even afford creating the install a little differently allowing to solve the original problem from reappearing. For example, installing, not using LVM.
Given that you said you were willing but would prefer not to... I was shooting for ideas that may help prevent it.

kcaps wrote:I'm sorry, I don't know what you mean.

I was mentioning that the above mentioned grub-fix relates to your hardware. However, you have clarified that you cannot enter that fix above.

kcaps

Tue Mar 17, 2020 8:17:13 am

Aravisian wrote:
kcaps wrote:
Aravisian wrote:Ok, I do not see anything there that might suggest that your system does not accept changes in Grub. The opposite, actually.

I can't use the standard grub "GRUB_CMDLINE_LINUX_DEFAULT=" (Which does include the suggested fix anyway, which means it either doesnt help in my case or the system is not actually taking the grub values other than recordfail timeout) because grub doesn't enter that part of the code. Instead it gets a recordfail, so I set the timeout to 1. How do I set the cmdline even through recordfail?

Ah, ok. I am following you, now.
Your computer does use grub, but is Not Responsive to that particular fix. Recordfail: If you are using a system with only one installed O.S. (not dual boot), LVM (Logical Volume Management) and UEFI (Ubinified extensible interface-all three conditions), then this can happen.
The purpose of it is basically an override, because without it, you would be unable to get Advanced Grub to appear if you needed it. It is actually a forced script that interferes with grub.
So, before going much further: Are you in fact using UEFI, LVM and have only one O.S. installed?
kcaps wrote:This has been happening since the beginning, I doubt an older version would help..

In that case, my suggestion would probably not help. I am not sure which kernel you had loaded at the beginning (it may have been kernel 5.0 whereas the above suggestion would roll back to 4.15.0-74... I think). However, the comments just above this line suggests there may be something else going on here.
kcaps wrote:I think that clean installing 15.2 would be a better chance of success, no?

Honestly... It is what I would do if it was me. It has a good chance of success and it MAY even afford creating the install a little differently allowing to solve the original problem from reappearing. For example, installing, not using LVM.
Given that you said you were willing but would prefer not to... I was shooting for ideas that may help prevent it.
kcaps wrote:I'm sorry, I don't know what you mean.

I was mentioning that the above mentioned grub-fix relates to your hardware. However, you have clarified that you cannot enter that fix above.

Yeah, as I wrote in the other thread, one OS, LVM, UEFI.
I guess there's nothing for it. I'll clean install the new 15.2 without lvm.

kcaps

Mon Mar 23, 2020 2:16:47 pm

Aravisian wrote:

I have clean installed Zorin core 15.2, and the issue persists, even with the suggested "cstate" fix in grub.
What can I try now?

Aravisian

Tue Mar 24, 2020 1:10:13 am

Let's hit the searches and hope one of us gets lucky... I cannot make any more recommendations since I'm as confused as you are. But maybe we can find someone who has solved it with enough web-crawling.

kcaps

Tue Mar 24, 2020 9:08:39 am

Aravisian wrote:Let's hit the searches and hope one of us gets lucky... I cannot make any more recommendations since I'm as confused as you are. But maybe we can find someone who has solved it with enough web-crawling.

https://bugs.launchpad.net/ubuntu/+sour ... ug/1798961

I've applied #42, Guess I'll wait and see what happens next.

Aravisian

Tue Mar 24, 2020 9:50:45 am

kcaps wrote:
Aravisian wrote:Let's hit the searches and hope one of us gets lucky... I cannot make any more recommendations since I'm as confused as you are. But maybe we can find someone who has solved it with enough web-crawling.

https://bugs.launchpad.net/ubuntu/+sour ... ug/1798961

I've applied #42, Guess I'll wait and see what happens next.

Nice find- please update results when you feel confident that you have them.

kcaps

Tue Mar 24, 2020 11:35:32 am

kcaps wrote:
Aravisian wrote:Let's hit the searches and hope one of us gets lucky... I cannot make any more recommendations since I'm as confused as you are. But maybe we can find someone who has solved it with enough web-crawling.

https://bugs.launchpad.net/ubuntu/+sour ... ug/1798961

I've applied #42, Guess I'll wait and see what happens next.

No dice. Crashed.
I tried confusing the system by unplugging it from power, folding and opening the screen, plugging it back in, then plugging in a USB drive, as the crashes often happen after these events.
Immediately after that I run : journalctl -b -1 -k
Output:

Code:: Mar 24 13:16:16 zenbook-zorin kernel: usb 1-1: USB disconnect, device number 2 Mar 24 13:16:16 zenbook-zorin kernel: usb 1-1.4: USB disconnect, device number 4 Mar 24 13:16:17 zenbook-zorin kernel: BUG: kernel NULL pointer dereference, address: 0000000000000080 Mar 24 13:16:17 zenbook-zorin kernel: #PF: supervisor read access in kernel mode Mar 24 13:16:17 zenbook-zorin kernel: #PF: error_code(0x0000) - not-present page Mar 24 13:16:17 zenbook-zorin kernel: PGD 800000036e08c067 P4D 800000036e08c067 PUD 0 Mar 24 13:16:17 zenbook-zorin kernel: Oops: 0000 [#1] SMP PTI Mar 24 13:16:17 zenbook-zorin kernel: CPU: 0 PID: 15735 Comm: kworker/0:1 Tainted: G OE 5.3.0-42-generic #34~18.04.1-Ubuntu Mar 24 13:16:17 zenbook-zorin kernel: Hardware name: ASUSTeK COMPUTER INC. UX370UAR/UX370UAR, BIOS UX370UAR.308 06/28/2018 Mar 24 13:16:17 zenbook-zorin kernel: Workqueue: events ucsi_connector_change [typec_ucsi] Mar 24 13:16:17 zenbook-zorin kernel: RIP: 0010:ucsi_displayport_remove_partner+0xe/0x20 [typec_ucsi] Mar 24 13:16:17 zenbook-zorin kernel: Code: c3 8b 53 28 48 8b 7b f8 48 c7 c6 6e f5 64 c0 e8 1f d9 48 f9 eb c8 66 0f 1f 44 00 00 0f 1f 44 00 00 55 48 85 ff 48 89 e5 74 0f <48> 8b 47 78 48 c7 Mar 24 13:16:17 zenbook-zorin kernel: RSP: 0018:ffffa864c462fde8 EFLAGS: 00010202 Mar 24 13:16:17 zenbook-zorin kernel: RAX: 0000000000000008 RBX: ffff9834fe865170 RCX: 0000000001286aee Mar 24 13:16:17 zenbook-zorin kernel: RDX: 0000000001286aed RSI: 0000000000000001 RDI: 0000000000000008 Mar 24 13:16:17 zenbook-zorin kernel: RBP: ffffa864c462fde8 R08: 0000000000000000 R09: ffffa864c462fc90 Mar 24 13:16:17 zenbook-zorin kernel: R10: ffffa864c462f918 R11: 0000000000000000 R12: 0000000000000000 Mar 24 13:16:17 zenbook-zorin kernel: R13: ffff9834fe865170 R14: 0000000000000001 R15: ffff9834fe865030 Mar 24 13:16:17 zenbook-zorin kernel: FS: 0000000000000000(0000) GS:ffff98350ea00000(0000) knlGS:0000000000000000 Mar 24 13:16:17 zenbook-zorin kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 24 13:16:17 zenbook-zorin kernel: CR2: 0000000000000080 CR3: 00000004454de001 CR4: 00000000003606f0 Mar 24 13:16:17 zenbook-zorin kernel: Call Trace: Mar 24 13:16:17 zenbook-zorin kernel: ucsi_unregister_altmodes+0x83/0x90 [typec_ucsi] Mar 24 13:16:17 zenbook-zorin kernel: ucsi_unregister_partner.part.12+0x17/0x30 [typec_ucsi] Mar 24 13:16:17 zenbook-zorin kernel: ucsi_connector_change+0x208/0x390 [typec_ucsi] Mar 24 13:16:17 zenbook-zorin kernel: ? kfree+0x1f7/0x210 Mar 24 13:16:17 zenbook-zorin kernel: process_one_work+0x1fd/0x3f0 Mar 24 13:16:17 zenbook-zorin kernel: worker_thread+0x34/0x410 Mar 24 13:16:17 zenbook-zorin kernel: kthread+0x121/0x140 Mar 24 13:16:17 zenbook-zorin kernel: ? process_one_work+0x3f0/0x3f0 Mar 24 13:16:17 zenbook-zorin kernel: ? kthread_park+0xb0/0xb0 Mar 24 13:16:17 zenbook-zorin kernel: ret_from_fork+0x35/0x40 Mar 24 13:16:17 zenbook-zorin kernel: Modules linked in: xt_tcpudp rfcomm ip6table_filter ip6_tables pci_stub iptable_filter vboxpci(OE) bpfilter vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) cc Mar 24 13:16:17 zenbook-zorin kernel: videobuf2_v4l2 serio_raw asus_wmi snd_seq_device sparse_keymap wmi_bmof videobuf2_common snd_timer bluetooth iwlwifi hid_sensor_accel_3d cdc_ether usbn Mar 24 13:16:17 zenbook-zorin kernel: pinctrl_intel Mar 24 13:16:17 zenbook-zorin kernel: CR2: 0000000000000080 Mar 24 13:16:17 zenbook-zorin kernel: ---[ end trace 3543a540a9de8181 ]--- Mar 24 13:16:17 zenbook-zorin kernel: RIP: 0010:ucsi_displayport_remove_partner+0xe/0x20 [typec_ucsi] Mar 24 13:16:17 zenbook-zorin kernel: Code: c3 8b 53 28 48 8b 7b f8 48 c7 c6 6e f5 64 c0 e8 1f d9 48 f9 eb c8 66 0f 1f 44 00 00 0f 1f 44 00 00 55 48 85 ff 48 89 e5 74 0f <48> 8b 47 78 48 c7 Mar 24 13:16:17 zenbook-zorin kernel: RSP: 0018:ffffa864c462fde8 EFLAGS: 00010202 Mar 24 13:16:17 zenbook-zorin kernel: RAX: 0000000000000008 RBX: ffff9834fe865170 RCX: 0000000001286aee Mar 24 13:16:17 zenbook-zorin kernel: RDX: 0000000001286aed RSI: 0000000000000001 RDI: 0000000000000008 Mar 24 13:16:17 zenbook-zorin kernel: RBP: ffffa864c462fde8 R08: 0000000000000000 R09: ffffa864c462fc90 Mar 24 13:16:17 zenbook-zorin kernel: R10: ffffa864c462f918 R11: 0000000000000000 R12: 0000000000000000 Mar 24 13:16:17 zenbook-zorin kernel: R13: ffff9834fe865170 R14: 0000000000000001 R15: ffff9834fe865030 Mar 24 13:16:17 zenbook-zorin kernel: FS: 0000000000000000(0000) GS:ffff98350ea00000(0000) knlGS:0000000000000000 Mar 24 13:16:17 zenbook-zorin kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 24 13:16:17 zenbook-zorin kernel: CR2: 0000000000000080 CR3: 00000004454de001 CR4: 00000000003606f0 Mar 24 13:16:19 zenbook-zorin kernel: usb 1-1: new high-speed USB device number 9 using xhci_hcd Mar 24 13:16:19 zenbook-zorin kernel: usb 1-1: New USB device found, idVendor=1a40, idProduct=0801, bcdDevice= 1.00 Mar 24 13:16:19 zenbook-zorin kernel: usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 Mar 24 13:16:19 zenbook-zorin kernel: usb 1-1: Product: USB 2.0 Hub Mar 24 13:16:19 zenbook-zorin kernel: hub 1-1:1.0: USB hub found Mar 24 13:16:19 zenbook-zorin kernel: hub 1-1:1.0: 4 ports detected Mar 24 13:16:19 zenbook-zorin kernel: usb 1-1.4: new high-speed USB device number 10 using xhci_hcd Mar 24 13:16:19 zenbook-zorin kernel: usb 1-1.4: New USB device found, idVendor=0bda, idProduct=8152, bcdDevice=20.00 Mar 24 13:16:19 zenbook-zorin kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 24 13:16:19 zenbook-zorin kernel: usb 1-1.4: Product: USB 10/100 LAN Mar 24 13:16:19 zenbook-zorin kernel: usb 1-1.4: Manufacturer: Realtek Mar 24 13:16:19 zenbook-zorin kernel: usb 1-1.4: SerialNumber: 00E04C360052 Mar 24 13:16:19 zenbook-zorin kernel: usb 1-1.4: reset high-speed USB device number 10 using xhci_hcd Mar 24 13:16:19 zenbook-zorin kernel: r8152 1-1.4:1.0 eth0: v1.09.10 Mar 24 13:16:19 zenbook-zorin kernel: r8152 1-1.4:1.0 enx00e04c360052: renamed from eth0 Mar 24 13:16:22 zenbook-zorin kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enx00e04c360052: link becomes ready Mar 24 13:16:22 zenbook-zorin kernel: r8152 1-1.4:1.0 enx00e04c360052: carrier on Mar 24 13:16:25 zenbook-zorin kernel: usb 1-1.3: new high-speed USB device number 11 using xhci_hcd Mar 24 13:16:25 zenbook-zorin kernel: usb 1-1.3: New USB device found, idVendor=ffee, idProduct=0100, bcdDevice= 1.00 Mar 24 13:16:25 zenbook-zorin kernel: usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Mar 24 13:16:25 zenbook-zorin kernel: usb-storage 1-1.3:1.0: USB Mass Storage device detected Mar 24 13:16:25 zenbook-zorin kernel: scsi host0: usb-storage 1-1.3:1.0 Mar 24 13:16:25 zenbook-zorin kernel: usbcore: registered new interface driver usb-storage Mar 24 13:16:25 zenbook-zorin kernel: usbcore: registered new interface driver uas Mar 24 13:16:26 zenbook-zorin kernel: scsi 0:0:0:0: Direct-Access FNK TECH USB CARD READER 2.33 PQ: 0 ANSI: 2 Mar 24 13:16:26 zenbook-zorin kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Mar 24 13:16:26 zenbook-zorin kernel: sd 0:0:0:0: [sda] 60367872 512-byte logical blocks: (30.9 GB/28.8 GiB) Mar 24 13:16:26 zenbook-zorin kernel: sd 0:0:0:0: [sda] Write Protect is off Mar 24 13:16:26 zenbook-zorin kernel: sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 Mar 24 13:16:26 zenbook-zorin kernel: sd 0:0:0:0: [sda] No Caching mode page found Mar 24 13:16:26 zenbook-zorin kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Mar 24 13:16:26 zenbook-zorin kernel: sda: sda1 Mar 24 13:16:26 zenbook-zorin kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk Mar 24 13:16:26 zenbook-zorin kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Aravisian

Tue Mar 24, 2020 12:01:26 pm

Looking over your report, then searching this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1785972

Maybe can find some relevant information, there. The steps to reproduce are similar to yours.

I have found similar reports going back to 2012, as well.
https://bbs.archlinux.org/viewtopic.php?id=249563
This thread suggests:
"pass "amdgpu.dc=0" to the kernel to likely sidestep the issue."
https://www.kernel.org/doc/html/latest/ ... pu-dc.html
I could be wrong, But I believe that this means in Grub:

Code:: GRUB_CMDLINE_LINUX=amdgpu.dc=0

May be worth a shot.

This is a static archive of the old Zorin Forum.