| 2022-07-27 17:55:26 |
Ip Soon |
bug |
|
|
added bug |
| 2022-07-27 17:56:28 |
Ip Soon |
summary |
Random crashes without any meaningful error logs related to CPU virtualization but a way to replicate the crashes |
Random crashes related to CPU virtualization - have a sure way to replicate the crashes |
|
| 2022-07-27 17:57:58 |
Ip Soon |
description |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes leave little information to pinpoint the exact process that caused the problem.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
The syslogs doesn't show any meaningful info for the crashes.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
has all of the info gathered in the painful experiences.
Once the SVM mode on the motherboard is turned off, I no longer experience the same crashes, and glmark2 can finish without any issues.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions. |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes leave little information to pinpoint the exact process that caused the problem.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
The syslogs doesn't show any meaningful info for the crashes.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
has all of the info gathered in the painful experiences.
Once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 can finish without any issues.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions. |
|
| 2022-07-27 18:00:15 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2022-07-27 19:35:47 |
Ip Soon |
description |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes leave little information to pinpoint the exact process that caused the problem.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
The syslogs doesn't show any meaningful info for the crashes.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
has all of the info gathered in the painful experiences.
Once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 can finish without any issues.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions. |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
BIOS version: F14 then F15c, both exhibited the same behaviors. F15c seems to be a little more resilient to the crashes, meaning the execution of glmark2 lasts a little longer before crashes.
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes leave little information to pinpoint the exact process that caused the problem.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
The syslogs doesn't show any meaningful info for the crashes.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
has all of the info gathered in the painful experiences.
Once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 can finish without any issues.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions. |
|
| 2022-07-27 19:50:26 |
Ip Soon |
tags |
|
apport-collected una |
|
| 2022-07-27 19:50:27 |
Ip Soon |
description |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
BIOS version: F14 then F15c, both exhibited the same behaviors. F15c seems to be a little more resilient to the crashes, meaning the execution of glmark2 lasts a little longer before crashes.
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes leave little information to pinpoint the exact process that caused the problem.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
The syslogs doesn't show any meaningful info for the crashes.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
has all of the info gathered in the painful experiences.
Once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 can finish without any issues.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions. |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
BIOS version: F14 then F15c, both exhibited the same behaviors. F15c seems to be a little more resilient to the crashes, meaning the execution of glmark2 lasts a little longer before crashes.
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes leave little information to pinpoint the exact process that caused the problem.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
The syslogs doesn't show any meaningful info for the crashes.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
has all of the info gathered in the painful experiences.
Once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 can finish without any issues.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: tssoon 1444 F.... pulseaudio
/dev/snd/controlC2: tssoon 1444 F.... pulseaudio
/dev/snd/controlC0: tssoon 1444 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 20.3
InstallationDate: Installed on 2022-03-02 (146 days ago)
InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
IwConfig:
lo no wireless extensions.
enp3s0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. B550M DS3H
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=7ec49d59-8fa2-4222-87f1-815e8c1d27e1 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
RelatedPackageVersions:
linux-restricted-modules-5.15.0-43-generic N/A
linux-backports-modules-5.15.0-43-generic N/A
linux-firmware 1.187.32
RfKill:
Tags: una
Uname: Linux 5.15.0-43-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/11/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F15c
dmi.board.asset.tag: Default string
dmi.board.name: B550M DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF15c:bd05/11/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B550 MB
dmi.product.name: B550M DS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
mtime.conffile..etc.apport.crashdb.conf: 2022-06-28T21:57:12.636387 |
|
| 2022-07-27 19:50:28 |
Ip Soon |
attachment added |
|
AlsaInfo.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605601/+files/AlsaInfo.txt |
|
| 2022-07-27 19:50:29 |
Ip Soon |
attachment added |
|
CRDA.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605602/+files/CRDA.txt |
|
| 2022-07-27 19:50:31 |
Ip Soon |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605603/+files/CurrentDmesg.txt |
|
| 2022-07-27 19:50:33 |
Ip Soon |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605604/+files/Lspci.txt |
|
| 2022-07-27 19:50:34 |
Ip Soon |
attachment added |
|
Lspci-vt.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605605/+files/Lspci-vt.txt |
|
| 2022-07-27 19:50:36 |
Ip Soon |
attachment added |
|
Lsusb.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605606/+files/Lsusb.txt |
|
| 2022-07-27 19:50:37 |
Ip Soon |
attachment added |
|
Lsusb-t.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605607/+files/Lsusb-t.txt |
|
| 2022-07-27 19:50:39 |
Ip Soon |
attachment added |
|
Lsusb-v.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605608/+files/Lsusb-v.txt |
|
| 2022-07-27 19:50:41 |
Ip Soon |
attachment added |
|
ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605609/+files/ProcCpuinfo.txt |
|
| 2022-07-27 19:50:42 |
Ip Soon |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605610/+files/ProcCpuinfoMinimal.txt |
|
| 2022-07-27 19:50:43 |
Ip Soon |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605611/+files/ProcEnviron.txt |
|
| 2022-07-27 19:50:44 |
Ip Soon |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605612/+files/ProcInterrupts.txt |
|
| 2022-07-27 19:50:46 |
Ip Soon |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605613/+files/ProcModules.txt |
|
| 2022-07-27 19:50:47 |
Ip Soon |
attachment added |
|
PulseList.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605614/+files/PulseList.txt |
|
| 2022-07-27 19:50:49 |
Ip Soon |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605615/+files/UdevDb.txt |
|
| 2022-07-27 19:50:52 |
Ip Soon |
attachment added |
|
WifiSyslog.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605616/+files/WifiSyslog.txt |
|
| 2022-07-27 19:50:54 |
Ip Soon |
attachment added |
|
acpidump.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605617/+files/acpidump.txt |
|
| 2022-07-27 19:50:56 |
Ip Soon |
attachment added |
|
modified.conffile..etc.apport.crashdb.conf.txt https://bugs.launchpad.net/bugs/1982965/+attachment/5605618/+files/modified.conffile..etc.apport.crashdb.conf.txt |
|
| 2022-07-27 19:52:42 |
Ip Soon |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2022-07-27 19:52:50 |
Ip Soon |
description |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
BIOS version: F14 then F15c, both exhibited the same behaviors. F15c seems to be a little more resilient to the crashes, meaning the execution of glmark2 lasts a little longer before crashes.
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes leave little information to pinpoint the exact process that caused the problem.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
The syslogs doesn't show any meaningful info for the crashes.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
has all of the info gathered in the painful experiences.
Once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 can finish without any issues.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: tssoon 1444 F.... pulseaudio
/dev/snd/controlC2: tssoon 1444 F.... pulseaudio
/dev/snd/controlC0: tssoon 1444 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 20.3
InstallationDate: Installed on 2022-03-02 (146 days ago)
InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
IwConfig:
lo no wireless extensions.
enp3s0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. B550M DS3H
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=7ec49d59-8fa2-4222-87f1-815e8c1d27e1 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
RelatedPackageVersions:
linux-restricted-modules-5.15.0-43-generic N/A
linux-backports-modules-5.15.0-43-generic N/A
linux-firmware 1.187.32
RfKill:
Tags: una
Uname: Linux 5.15.0-43-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/11/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F15c
dmi.board.asset.tag: Default string
dmi.board.name: B550M DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF15c:bd05/11/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B550 MB
dmi.product.name: B550M DS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
mtime.conffile..etc.apport.crashdb.conf: 2022-06-28T21:57:12.636387 |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
BIOS version: F14 then F15c, both exhibited the same behaviors. F15c seems to be a little more resilient to the crashes, meaning the execution of glmark2 lasts a little longer before crashes.
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes means, I just received black screen, no keyboard or mouse response. Had to power cycle the computer to resume operations. Tried to store the syslog for each boot ended in crash.
At beginning, I tried to sync the file system at rebooting the computer, but the computer boots up without syncing the file system as well.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
To me the syslogs doesn't show any meaningful info for the crashes. The following link gives some of the syslog gathered in the painful experiences especially those crashes shortly after reboot.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
The Key Finding:
Once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 can finish without any issues. All versions of kernel 5.11 to 5.15 work stably as expected.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions. |
|
| 2022-07-27 20:03:17 |
Ip Soon |
description |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
BIOS version: F14 then F15c, both exhibited the same behaviors. F15c seems to be a little more resilient to the crashes, meaning the execution of glmark2 lasts a little longer before crashes.
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes means, I just received black screen, no keyboard or mouse response. Had to power cycle the computer to resume operations. Tried to store the syslog for each boot ended in crash.
At beginning, I tried to sync the file system at rebooting the computer, but the computer boots up without syncing the file system as well.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
To me the syslogs doesn't show any meaningful info for the crashes. The following link gives some of the syslog gathered in the painful experiences especially those crashes shortly after reboot.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
The Key Finding:
Once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 can finish without any issues. All versions of kernel 5.11 to 5.15 work stably as expected.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions. |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
BIOS version: F14 then F15c, both exhibited the same behaviors. F15c seems to be a little more resilient to the crashes, meaning the execution of glmark2 lasts a little longer before crashes.
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes means, I just received black screen, no keyboard or mouse response. Had to power cycle the computer to resume operations. Tried to store the syslog for each boot ended in crash. Also after reboot tried to look into /var/crash to see any files written, typically, it's empty.
At beginning, I tried to sync the file system at rebooting the computer, but the computer boots up without syncing the file system as well.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
To me the syslogs doesn't show any meaningful info for the crashes. The following link gives some of the syslog gathered in the painful experiences especially those crashes shortly after reboot.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
The Key Finding:
Once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 can finish without any issues. All versions of kernel 5.11 to 5.15 work stably as expected.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions. |
|
| 2022-07-27 20:05:25 |
Ip Soon |
description |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
BIOS version: F14 then F15c, both exhibited the same behaviors. F15c seems to be a little more resilient to the crashes, meaning the execution of glmark2 lasts a little longer before crashes.
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes means, I just received black screen, no keyboard or mouse response. Had to power cycle the computer to resume operations. Tried to store the syslog for each boot ended in crash. Also after reboot tried to look into /var/crash to see any files written, typically, it's empty.
At beginning, I tried to sync the file system at rebooting the computer, but the computer boots up without syncing the file system as well.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
To me the syslogs doesn't show any meaningful info for the crashes. The following link gives some of the syslog gathered in the painful experiences especially those crashes shortly after reboot.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
The Key Finding:
Once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 can finish without any issues. All versions of kernel 5.11 to 5.15 work stably as expected.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions. |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
BIOS version: F14 then F15c, both exhibited the same behaviors. F15c seems to be a little more resilient to the crashes, meaning the execution of glmark2 lasts a little longer before crashes.
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes means, lost of desktop screen and received only a black screen, no keyboard or mouse response. Had to power cycle the computer to resume operations. Tried to store the syslog for each boot ended in crash.
At beginning, I tried to sync the file system at rebooting the computer, but the computer boots up without syncing the file system as well.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
To me the syslogs doesn't show any meaningful info for the crashes. The following link gives some of the syslog gathered in the painful experiences especially those crashes shortly after reboot.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
The Key Finding:
Once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 can finish without any issues. All versions of kernel 5.11 to 5.15 work stably as expected.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions. |
|
| 2022-07-27 20:44:37 |
Ip Soon |
description |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
BIOS version: F14 then F15c, both exhibited the same behaviors. F15c seems to be a little more resilient to the crashes, meaning the execution of glmark2 lasts a little longer before crashes.
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes means, lost of desktop screen and received only a black screen, no keyboard or mouse response. Had to power cycle the computer to resume operations. Tried to store the syslog for each boot ended in crash.
At beginning, I tried to sync the file system at rebooting the computer, but the computer boots up without syncing the file system as well.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
To me the syslogs doesn't show any meaningful info for the crashes. The following link gives some of the syslog gathered in the painful experiences especially those crashes shortly after reboot.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
The Key Finding:
Once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 can finish without any issues. All versions of kernel 5.11 to 5.15 work stably as expected.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions. |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
BIOS version: F14 then F15c, both exhibited the same behaviors. F15c seems to be a little more resilient to the crashes, meaning the execution of glmark2 lasts a little longer before crashes.
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes means, lost of desktop screen and received only a black screen, no keyboard or mouse response. Had to power cycle the computer to resume operations. Tried to store the syslog for each boot ended in crash.
At beginning, I tried to sync the file system at rebooting the computer, but the computer boots up without syncing the file system as well.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
To me the syslogs doesn't show any meaningful info for the crashes. The following link gives some of the syslog gathered in the painful experiences especially those crashes shortly after reboot.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
The Key Finding is once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 can finish without any issues. All versions of kernel 5.11 to 5.15 work stably as expected.
The real question to me is how the CPU virtualization is supported in the kernel and why turning on the CPU virtualization can promote the crashes. Perhaps the BIOS might be involved for a satisfactory solution to this observed problem, however, what I can offer is just a sure way to replicate the crashes for others to investigate this issue further.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions. |
|
| 2022-07-27 20:55:43 |
Ip Soon |
description |
Description: Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
BIOS version: F14 then F15c, both exhibited the same behaviors. F15c seems to be a little more resilient to the crashes, meaning the execution of glmark2 lasts a little longer before crashes.
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15
Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard CPU virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes means, lost of desktop screen and received only a black screen, no keyboard or mouse response. Had to power cycle the computer to resume operations. Tried to store the syslog for each boot ended in crash.
At beginning, I tried to sync the file system at rebooting the computer, but the computer boots up without syncing the file system as well.
After almost three months of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped. The packaged kernel 5.4 doesn't have proper drivers for both the graphics and network interfaces.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done.
To me the syslogs doesn't show any meaningful info for the crashes. The following link gives some of the syslog gathered in the painful experiences especially those crashes shortly after reboot.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
The Key Finding is once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 can finish without any issues. All versions of kernel 5.11 to 5.15 work stably as expected.
The real question to me is how the CPU virtualization is supported in the kernel and why turning on the CPU virtualization can promote the crashes. Perhaps the BIOS might be involved for a satisfactory solution to this observed problem, however, what I can offer is just a sure way to replicate the crashes for others to investigate this issue further.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions. |
Problem description: Linux suffers random crashes especially during video intensive operations.
Hardware configurations:
CPU: AMD Ryzen 7 5700G with Radeon Graphics
Motherboard: Gigabyte B550M D3H
BIOS version: F14 then F15c, both exhibited the same behaviors. F15c seems to be a little more resilient to the crashes, meaning the execution of glmark2 lasts a little longer before crashes.
OS: Linux Mint 20.3 / with a number of Ubuntu kernels from 5.11, 5.13, and 5.15. Due to the CPU and motherboard, have to use non-packaged kernels for both graphics and network interface to work.
Key findings:
Once the CPU virtualization is turned-on, system starts to crash randomly. For Gigabyte motherboard, Hardware virtualization is called SVM mode. All crashes occurred under CPU SVM mode is enabled.
Crashes means, sudden lost of desktop screen during operations and received only a black screen. No keyboard or mouse response. Had to power cycle the computer to resume operations. Tried to store the syslog for each boot ended in crash.
At beginning, I tried to sync the file system at rebooting the computer, but the computer boots up without syncing the file system as well.
During at least three months of this kind of bad experiences, tried to upgrade kernel from 5.11 to 5.15, none of them helped.
Methods of replicating the crashes:
1. Turn on the SVM mode in BIOS.
2. Execute glmark2 to benchmark the graphic card performance.
3. System crashes before the benchmark test is done every time.
To me the syslogs doesn't show any meaningful info for the crashes. The following link gives some of the syslog gathered in the painful experiences especially those crashes shortly after reboot.
https://drive.google.com/drive/folders/1cYbQPdfPSC_6A879xBWRs1jIY7R5ylMU?usp=sharing
The most important Finding is once the SVM mode on the motherboard is turned off (disabled), I no longer experience the same kind of random crashes, and glmark2 benchmark can finish without any issues. All versions of kernel 5.11 to 5.15 work stably as expected.
The real question to me is how the CPU virtualization is supported in the kernel and why turning on the CPU virtualization can promote the crashes. Perhaps the BIOS might be involved for a satisfactory solution to this observed problem, however, what I can offer is just a sure way to replicate the crashes for others to investigate this issue further.
That's all I can report here. If you need any further information. Please feel free to let me know.
Thanks for your attentions. |
|
