| 2017-03-09 06:25:42 |
Maciej Dziardziel |
bug |
|
|
added bug |
| 2017-03-09 06:25:42 |
Maciej Dziardziel |
attachment added |
|
kernel config, lspci, dmesg messages and other info I could get https://bugs.launchpad.net/bugs/1671360/+attachment/4834330/+files/report.tgz |
|
| 2017-03-09 06:31:27 |
Brad Figg |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2017-03-09 19:05:40 |
Maciej Dziardziel |
tags |
|
apport-collected zesty |
|
| 2017-03-09 19:05:44 |
Maciej Dziardziel |
description |
I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard,
and it has a load of problems, starting with not being able to boot normally.
During normal boot, on 16.10 as well as 17.04 beta:
system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07"
messages displayed.
Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings
1. add "acpi=off" to boot params
That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode.
2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option.
That gets me even further - system sees all cores now. Still only recovery mode though,
but its enough to get info for this bug report.
Some observed problems:
1. dmesg reports *a lot* of messages like this all the time:
[ 163.362068] ->handle_irq(): ffffffff87a7e090,
[ 163.362081] bad_chained_irq+0x0/0x40
[ 163.362089] ->handle_irq(): ffffffff87a7e090,
[ 163.362090] amd_gpio_irq_handler+0x0/0x200
[ 163.362090] ->irq_data.chip(): ffffffff88587e20,
[ 163.362090] ioapic_ir_chip+0x0/0x120
[ 163.362090] ->action(): ffffffff884601c0
[ 163.362091] IRQ_NOPROBE set
[ 163.362099] ->handle_irq(): ffffffff87a7e090,
[ 163.362099] amd_gpio_irq_handler+0x0/0x200
[ 163.362100] ->irq_data.chip(): ffffffff88587e20,
[ 163.362100] ioapic_ir_chip+0x0/0x120
[ 163.362101] ->action(): ffffffff884601c0
I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those.
2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs?
3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040.
Phoronix tested ryzen using different motherboard, and it worked better (though not well),
so I suspect it is an issue with motherboard. |
I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard,
and it has a load of problems, starting with not being able to boot normally.
During normal boot, on 16.10 as well as 17.04 beta:
system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07"
messages displayed.
Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings
1. add "acpi=off" to boot params
That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode.
2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option.
That gets me even further - system sees all cores now. Still only recovery mode though,
but its enough to get info for this bug report.
Some observed problems:
1. dmesg reports *a lot* of messages like this all the time:
[ 163.362068] ->handle_irq(): ffffffff87a7e090,
[ 163.362081] bad_chained_irq+0x0/0x40
[ 163.362089] ->handle_irq(): ffffffff87a7e090,
[ 163.362090] amd_gpio_irq_handler+0x0/0x200
[ 163.362090] ->irq_data.chip(): ffffffff88587e20,
[ 163.362090] ioapic_ir_chip+0x0/0x120
[ 163.362090] ->action(): ffffffff884601c0
[ 163.362091] IRQ_NOPROBE set
[ 163.362099] ->handle_irq(): ffffffff87a7e090,
[ 163.362099] amd_gpio_irq_handler+0x0/0x200
[ 163.362100] ->irq_data.chip(): ffffffff88587e20,
[ 163.362100] ioapic_ir_chip+0x0/0x120
[ 163.362101] ->action(): ffffffff884601c0
I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those.
2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs?
3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040.
Phoronix tested ryzen using different motherboard, and it worked better (though not well),
so I suspect it is an issue with motherboard.
---
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2015-08-06 (581 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
Package: linux (not installed)
ProcEnviron:
LANGUAGE=en_US:en
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Tags: zesty
Uname: Linux 4.11.0-rc1-custom x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
UserGroups:
_MarkForUpload: True |
|
| 2017-03-09 19:05:46 |
Maciej Dziardziel |
attachment added |
|
JournalErrors.txt https://bugs.launchpad.net/bugs/1671360/+attachment/4834867/+files/JournalErrors.txt |
|
| 2017-03-09 19:06:15 |
Maciej Dziardziel |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2017-03-09 19:19:49 |
Eric Hartmann |
bug |
|
|
added subscriber Eric Hartmann |
| 2017-03-09 19:46:48 |
Joseph Salisbury |
linux (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-03-09 19:47:06 |
Joseph Salisbury |
linux (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2017-03-09 21:39:20 |
Maciej Dziardziel |
tags |
apport-collected zesty |
apport-collected kernel-bug-exists-upstream zesty |
|
| 2017-03-09 21:39:55 |
Maciej Dziardziel |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2017-03-12 09:37:02 |
Cosmin Mutu |
bug |
|
|
added subscriber Cosmin Mutu |
| 2017-03-12 10:04:09 |
Cosmin Mutu |
attachment added |
|
Screenshot from 2017-03-12 10-01-42.png https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+attachment/4836279/+files/Screenshot%20from%202017-03-12%2010-01-42.png |
|
| 2017-03-13 08:58:42 |
Huang YangWen |
attachment added |
|
Screenshot from 2017-03-13 16-53-20.png https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+attachment/4836844/+files/Screenshot%20from%202017-03-13%2016-53-20.png |
|
| 2017-03-14 08:23:40 |
Eric Hartmann |
attachment added |
|
devices.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+attachment/4837491/+files/devices.txt |
|
| 2017-03-14 08:24:05 |
Eric Hartmann |
attachment added |
|
lspci.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+attachment/4837492/+files/lspci.txt |
|
| 2017-03-21 11:29:35 |
Marc Singer |
bug |
|
|
added subscriber Marc Singer |
| 2017-04-02 13:14:23 |
MoKraD |
bug |
|
|
added subscriber MoKraD |
| 2017-04-02 14:03:29 |
Roland Kaiser |
bug |
|
|
added subscriber Roland Kaiser |
| 2017-04-06 15:06:19 |
Roland Kaiser |
attachment added |
|
gb_pinctrl_amd.tar.gz https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+attachment/4856311/+files/gb_pinctrl_amd.tar.gz |
|
| 2017-04-06 19:08:36 |
Roland Kaiser |
attachment added |
|
mem_0xfed81500.bin https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+attachment/4856581/+files/mem_0xfed81500.bin |
|
| 2017-04-08 04:10:33 |
Roland Kaiser |
summary |
System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3 |
System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) |
|
| 2017-04-08 04:14:21 |
Roland Kaiser |
tags |
apport-collected kernel-bug-exists-upstream zesty |
apport-collected kernel-bug-exists-upstream xenial yakkety zesty |
|
| 2017-04-08 04:21:04 |
Roland Kaiser |
tags |
apport-collected kernel-bug-exists-upstream xenial yakkety zesty |
apport-collected kernel-bug-exists-upstream regression-release xenial yakkety zesty |
|
| 2017-04-11 01:38:00 |
Leonardo Varuzza |
bug |
|
|
added subscriber Leonardo Varuzza |
| 2017-04-11 17:42:20 |
Robert C Jennings |
bug |
|
|
added subscriber Robert C Jennings |
| 2017-04-12 02:55:27 |
AAY |
bug |
|
|
added subscriber AAY |
| 2017-04-12 17:38:38 |
DIONYSIS KAPATSORIS |
bug |
|
|
added subscriber DIONYSIS KAPATSORIS |
| 2017-04-14 17:33:38 |
ATIpro |
bug |
|
|
added subscriber ATIpro |
| 2017-04-17 03:22:53 |
Kai-Heng Feng |
bug |
|
|
added subscriber AMD Team |
| 2017-04-17 18:47:48 |
Joseph Salisbury |
linux (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2017-04-17 18:48:03 |
Joseph Salisbury |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2017-04-17 22:33:24 |
keithy |
bug |
|
|
added subscriber keithy |
| 2017-04-18 04:59:01 |
GiaBao Phu Truong |
bug |
|
|
added subscriber GiaBao Phu Truong |
| 2017-04-18 18:14:46 |
Joseph Salisbury |
tags |
apport-collected kernel-bug-exists-upstream regression-release xenial yakkety zesty |
apport-collected kernel-bug-exists-upstream kernel-da-key regression-release xenial yakkety zesty |
|
| 2017-04-22 03:15:55 |
Chris Reid |
bug |
|
|
added subscriber Chris Reid |
| 2017-04-24 02:43:26 |
Kevin Norman |
bug |
|
|
added subscriber Kevin Norman |
| 2017-04-24 15:53:25 |
Robert C Jennings |
removed subscriber Robert C Jennings |
|
|
|
| 2017-04-25 11:15:43 |
Woody |
bug |
|
|
added subscriber Woody |
| 2017-04-25 17:15:17 |
Navdeep Singh |
bug |
|
|
added subscriber Navdeep Singh |
| 2017-04-26 14:26:01 |
Roland Kaiser |
tags |
apport-collected kernel-bug-exists-upstream kernel-da-key regression-release xenial yakkety zesty |
apport-collected bitesize kernel-bug-exists-upstream kernel-da-key kernel-oops regression-release xenial yakkety zesty |
|
| 2017-04-28 23:30:56 |
Paulo J. S. Silva |
bug |
|
|
added subscriber Paulo J. S. Silva |
| 2017-05-03 12:57:18 |
belgianguy |
bug |
|
|
added subscriber belgianguy |
| 2017-05-05 17:55:40 |
Ondrej Masek |
bug |
|
|
added subscriber Ondrej Masek |
| 2017-05-08 08:24:24 |
Michael Neufing |
bug |
|
|
added subscriber Michael Neufing |
| 2017-05-09 09:22:29 |
Kai-Heng Feng |
bug watch added |
|
http://bugzilla.kernel.org/194825 |
|
| 2017-05-09 09:22:29 |
Kai-Heng Feng |
bug task added |
|
linux |
|
| 2017-05-19 18:32:39 |
Linus Luotsinen |
bug |
|
|
added subscriber Linus Luotsinen |
| 2017-05-19 23:51:14 |
Hein |
bug |
|
|
added subscriber Hein |
| 2017-05-21 11:55:25 |
Peter Newman |
bug |
|
|
added subscriber Peter Newman |
| 2017-05-21 20:16:26 |
David Pottage |
bug |
|
|
added subscriber David Pottage |
| 2017-06-01 05:25:18 |
Kai-Heng Feng |
description |
I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard,
and it has a load of problems, starting with not being able to boot normally.
During normal boot, on 16.10 as well as 17.04 beta:
system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07"
messages displayed.
Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings
1. add "acpi=off" to boot params
That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode.
2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option.
That gets me even further - system sees all cores now. Still only recovery mode though,
but its enough to get info for this bug report.
Some observed problems:
1. dmesg reports *a lot* of messages like this all the time:
[ 163.362068] ->handle_irq(): ffffffff87a7e090,
[ 163.362081] bad_chained_irq+0x0/0x40
[ 163.362089] ->handle_irq(): ffffffff87a7e090,
[ 163.362090] amd_gpio_irq_handler+0x0/0x200
[ 163.362090] ->irq_data.chip(): ffffffff88587e20,
[ 163.362090] ioapic_ir_chip+0x0/0x120
[ 163.362090] ->action(): ffffffff884601c0
[ 163.362091] IRQ_NOPROBE set
[ 163.362099] ->handle_irq(): ffffffff87a7e090,
[ 163.362099] amd_gpio_irq_handler+0x0/0x200
[ 163.362100] ->irq_data.chip(): ffffffff88587e20,
[ 163.362100] ioapic_ir_chip+0x0/0x120
[ 163.362101] ->action(): ffffffff884601c0
I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those.
2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs?
3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040.
Phoronix tested ryzen using different motherboard, and it worked better (though not well),
so I suspect it is an issue with motherboard.
---
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2015-08-06 (581 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
Package: linux (not installed)
ProcEnviron:
LANGUAGE=en_US:en
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Tags: zesty
Uname: Linux 4.11.0-rc1-custom x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
UserGroups:
_MarkForUpload: True |
[Impact]
Gigabyte AM4 boards users cannot boot Ubuntu successfully.
Commit linux-gpio/fixes babdc22b0ccf4ef5a3075ce6e4afc26b7a279faf "pinctrl/amd: Use regular interrupt instead of chained" can fix the issue.
[Test Case]
All Gigabyte AM4 boards can reproduce the issue.
With the patch, the issue is resolved, per comment #170.
[Regression Potential]
Regression Potential is low. It limits to rather new AMD platform which has pinctrl-amd.
As the commit log says, use chained interrupt is not a good idea. Use regular interrupt is the correct way.
I also test the patch on an AMD laptop, where its touchpad depends on pinctrl-amd. No regression found.
Original bug report:
I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard,
and it has a load of problems, starting with not being able to boot normally.
During normal boot, on 16.10 as well as 17.04 beta:
system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07"
messages displayed.
Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings
1. add "acpi=off" to boot params
That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode.
2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option.
That gets me even further - system sees all cores now. Still only recovery mode though,
but its enough to get info for this bug report.
Some observed problems:
1. dmesg reports *a lot* of messages like this all the time:
[ 163.362068] ->handle_irq(): ffffffff87a7e090,
[ 163.362081] bad_chained_irq+0x0/0x40
[ 163.362089] ->handle_irq(): ffffffff87a7e090,
[ 163.362090] amd_gpio_irq_handler+0x0/0x200
[ 163.362090] ->irq_data.chip(): ffffffff88587e20,
[ 163.362090] ioapic_ir_chip+0x0/0x120
[ 163.362090] ->action(): ffffffff884601c0
[ 163.362091] IRQ_NOPROBE set
[ 163.362099] ->handle_irq(): ffffffff87a7e090,
[ 163.362099] amd_gpio_irq_handler+0x0/0x200
[ 163.362100] ->irq_data.chip(): ffffffff88587e20,
[ 163.362100] ioapic_ir_chip+0x0/0x120
[ 163.362101] ->action(): ffffffff884601c0
I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those.
2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs?
3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040.
Phoronix tested ryzen using different motherboard, and it worked better (though not well),
so I suspect it is an issue with motherboard.
---
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2015-08-06 (581 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
Package: linux (not installed)
ProcEnviron:
LANGUAGE=en_US:en
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Tags: zesty
Uname: Linux 4.11.0-rc1-custom x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
UserGroups:
_MarkForUpload: True |
|
| 2017-06-01 05:25:28 |
Kai-Heng Feng |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-06-01 05:25:28 |
Kai-Heng Feng |
nominated for series |
|
Ubuntu Artful |
|
| 2017-06-01 20:30:53 |
Seth Forshee |
bug task added |
|
linux (Ubuntu Artful) |
|
| 2017-06-01 20:31:03 |
Seth Forshee |
bug task added |
|
linux (Ubuntu Zesty) |
|
| 2017-06-01 20:31:40 |
Seth Forshee |
linux (Ubuntu Artful): assignee |
|
Kai-Heng Feng (kaihengfeng) |
|
| 2017-06-01 20:31:52 |
Seth Forshee |
linux (Ubuntu Zesty): assignee |
|
Kai-Heng Feng (kaihengfeng) |
|
| 2017-06-01 20:31:59 |
Seth Forshee |
linux (Ubuntu Artful): status |
Confirmed |
Fix Committed |
|
| 2017-06-02 13:45:48 |
Richard |
bug |
|
|
added subscriber Richard |
| 2017-06-03 21:38:48 |
Launchpad Janitor |
linux (Ubuntu Zesty): status |
New |
Confirmed |
|
| 2017-06-03 21:40:04 |
Erik Nijland |
bug |
|
|
added subscriber Erik Nijland |
| 2017-06-06 15:34:51 |
Kleber Sacilotto de Souza |
linux (Ubuntu Zesty): status |
Confirmed |
Fix Committed |
|
| 2017-06-07 17:58:16 |
windblow |
linux (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2017-06-09 09:11:46 |
Stefan Bader |
linux (Ubuntu Zesty): status |
Fix Released |
Fix Committed |
|
| 2017-06-14 07:54:03 |
Hein |
removed subscriber Hein |
|
|
|
| 2017-06-14 09:15:51 |
Kleber Sacilotto de Souza |
tags |
apport-collected bitesize kernel-bug-exists-upstream kernel-da-key kernel-oops regression-release xenial yakkety zesty |
apport-collected bitesize kernel-bug-exists-upstream kernel-da-key kernel-oops regression-release verification-needed-zesty xenial yakkety zesty |
|
| 2017-06-14 14:58:21 |
Kleber Sacilotto de Souza |
tags |
apport-collected bitesize kernel-bug-exists-upstream kernel-da-key kernel-oops regression-release verification-needed-zesty xenial yakkety zesty |
apport-collected bitesize kernel-bug-exists-upstream kernel-da-key kernel-oops regression-release verification-done-zesty xenial yakkety zesty |
|
| 2017-06-25 00:44:27 |
Tekkla |
bug |
|
|
added subscriber Tekkla |
| 2017-06-29 07:17:58 |
Launchpad Janitor |
linux (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2017-06-29 07:17:58 |
Launchpad Janitor |
cve linked |
|
2017-1000364 |
|
| 2017-06-29 07:17:58 |
Launchpad Janitor |
cve linked |
|
2017-100363 |
|
| 2017-06-29 07:17:58 |
Launchpad Janitor |
cve linked |
|
2017-8890 |
|
| 2017-06-29 07:17:58 |
Launchpad Janitor |
cve linked |
|
2017-9074 |
|
| 2017-06-29 07:17:58 |
Launchpad Janitor |
cve linked |
|
2017-9075 |
|
| 2017-06-29 07:17:58 |
Launchpad Janitor |
cve linked |
|
2017-9076 |
|
| 2017-06-29 07:17:58 |
Launchpad Janitor |
cve linked |
|
2017-9077 |
|
| 2017-06-29 07:17:58 |
Launchpad Janitor |
cve linked |
|
2017-9242 |
|
| 2017-06-29 07:17:57 |
Launchpad Janitor |
linux (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2017-06-30 17:19:06 |
Launchpad Janitor |
linux (Ubuntu Artful): status |
Fix Committed |
Fix Released |
|
| 2017-07-31 15:59:04 |
Václav Haisman |
bug |
|
|
added subscriber Václav Haisman |
| 2018-09-02 11:20:40 |
Jaap de Haan |
bug |
|
|
added subscriber Jaap de Haan |
| 2020-09-27 23:59:38 |
Bug Watch Updater |
linux: status |
Unknown |
Confirmed |
|
| 2020-09-27 23:59:38 |
Bug Watch Updater |
linux: importance |
Unknown |
Medium |
|
| 2022-05-19 14:19:31 |
Mario Limonciello |
removed subscriber AMD |
|
|
|
| 2022-05-22 04:38:29 |
Bug Watch Updater |
linux: status |
Confirmed |
Fix Released |
|
| 2022-05-22 04:38:34 |
Bug Watch Updater |
bug watch added |
|
https://bugzilla.proxmox.com/show_bug.cgi?id=1366 |
|
| 2022-05-22 04:38:34 |
Bug Watch Updater |
bug watch added |
|
https://bugzilla.kernel.org/show_bug.cgi?id=194945 |
|
