[Kernel-packages] [Bug 2045584] Re: Firefox/brave browser causes GPU reset
Please have a look at the picture of the crash.
** Attachment added: "Screen when GPU crashes"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045584/+attachment/5739602/+files/IMG_20231202_165801.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045584
Title:
Firefox/brave browser causes GPU reset
Status in linux package in Ubuntu:
New
Bug description:
I am using UBUNTU 23.10 with Vega 64 using the latest amdgpu drivers.
This started when I upgraded to 23.10. Was not happening in 22.04 or
23.04.
In Wayland, it always crashes the gnome session and I have to hardware
power off the system. It also sometimes makes a weird pixelated image
on the screen, kind of like static with both firefox and brave
broswers.
In xorg session only firefox seems to crash the session but weirdly it
just "logs me out" to the welcome screen. Brave works fine.
I thought it was a mem issue but I have run memtest twice now with all
tests passing for the whole night. I have also run prime95
successfully on both windows and ubuntu now for 5-6 hours as well just
to stress the system for both CPU and mem and no issues there.
Its fairly reproducible so please let me know how I can help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-13-generic 6.5.0-13.13
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: awaahm 6528 F wireplumber
/dev/snd/controlC2: awaahm 6528 F wireplumber
/dev/snd/controlC0: awaahm 6528 F wireplumber
/dev/snd/seq:awaahm 6512 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 4 20:05:05 2023
InstallationDate: Installed on 2021-03-30 (979 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-13-generic
root=UUID=0392d1e9-f9ce-4e11-a853-626267f141ac ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-13-generic N/A
linux-backports-modules-6.5.0-13-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-10 (24 days ago)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8702
dmi.board.asset.tag: Default string
dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr8702:bd08/10/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2023-07-26T18:11:44.877297
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045584] Re: Firefox/brave browser causes GPU reset
Sometimes the screen crashes as above and I didnt know what to do, but
now when I switch to tty3 I am able to see the console again and it
seems to be working, Then if I want and try to go back to the GUI TTY by
pressing the ctrl+2 and typing in the password, I am unable to login and
gnome-shell keeps logging me out.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045584
Title:
Firefox/brave browser causes GPU reset
Status in linux package in Ubuntu:
New
Bug description:
I am using UBUNTU 23.10 with Vega 64 using the latest amdgpu drivers.
This started when I upgraded to 23.10. Was not happening in 22.04 or
23.04.
In Wayland, it always crashes the gnome session and I have to hardware
power off the system. It also sometimes makes a weird pixelated image
on the screen, kind of like static with both firefox and brave
broswers.
In xorg session only firefox seems to crash the session but weirdly it
just "logs me out" to the welcome screen. Brave works fine.
I thought it was a mem issue but I have run memtest twice now with all
tests passing for the whole night. I have also run prime95
successfully on both windows and ubuntu now for 5-6 hours as well just
to stress the system for both CPU and mem and no issues there.
Its fairly reproducible so please let me know how I can help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-13-generic 6.5.0-13.13
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: awaahm 6528 F wireplumber
/dev/snd/controlC2: awaahm 6528 F wireplumber
/dev/snd/controlC0: awaahm 6528 F wireplumber
/dev/snd/seq:awaahm 6512 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 4 20:05:05 2023
InstallationDate: Installed on 2021-03-30 (979 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-13-generic
root=UUID=0392d1e9-f9ce-4e11-a853-626267f141ac ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-13-generic N/A
linux-backports-modules-6.5.0-13-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-10 (24 days ago)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8702
dmi.board.asset.tag: Default string
dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr8702:bd08/10/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2023-07-26T18:11:44.877297
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045584] Re: Firefox/brave browser causes GPU reset
This is a big issue as its a crash and I was wondering how to get it
prioritized as no one seems to be looking at it. I am new to this so I
just wanted to understand how to get some attention.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045584
Title:
Firefox/brave browser causes GPU reset and Gnome-shell crash
Status in linux package in Ubuntu:
New
Bug description:
I am using UBUNTU 23.10 with Vega 64 using the latest amdgpu drivers.
This started when I upgraded to 23.10. Was not happening in 22.04 or
23.04.
In Wayland, it always crashes the gnome session and I have to hardware
power off the system. It also sometimes makes a weird pixelated image
on the screen, kind of like static with both firefox and brave
broswers.
In xorg session only firefox seems to crash the session but weirdly it
just "logs me out" to the welcome screen. Brave works fine.
I thought it was a mem issue but I have run memtest twice now with all
tests passing for the whole night. I have also run prime95
successfully on both windows and ubuntu now for 5-6 hours as well just
to stress the system for both CPU and mem and no issues there.
Its fairly reproducible so please let me know how I can help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-13-generic 6.5.0-13.13
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: awaahm 6528 F wireplumber
/dev/snd/controlC2: awaahm 6528 F wireplumber
/dev/snd/controlC0: awaahm 6528 F wireplumber
/dev/snd/seq:awaahm 6512 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 4 20:05:05 2023
InstallationDate: Installed on 2021-03-30 (979 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-13-generic
root=UUID=0392d1e9-f9ce-4e11-a853-626267f141ac ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-13-generic N/A
linux-backports-modules-6.5.0-13-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-10 (24 days ago)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8702
dmi.board.asset.tag: Default string
dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr8702:bd08/10/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2023-07-26T18:11:44.877297
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045584] Re: Firefox/brave browser causes GPU reset and Gnome-shell crash
** Summary changed:
- Firefox/brave browser causes GPU reset
+ Firefox/brave browser causes GPU reset and Gnome-shell crash
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045584
Title:
Firefox/brave browser causes GPU reset and Gnome-shell crash
Status in linux package in Ubuntu:
New
Bug description:
I am using UBUNTU 23.10 with Vega 64 using the latest amdgpu drivers.
This started when I upgraded to 23.10. Was not happening in 22.04 or
23.04.
In Wayland, it always crashes the gnome session and I have to hardware
power off the system. It also sometimes makes a weird pixelated image
on the screen, kind of like static with both firefox and brave
broswers.
In xorg session only firefox seems to crash the session but weirdly it
just "logs me out" to the welcome screen. Brave works fine.
I thought it was a mem issue but I have run memtest twice now with all
tests passing for the whole night. I have also run prime95
successfully on both windows and ubuntu now for 5-6 hours as well just
to stress the system for both CPU and mem and no issues there.
Its fairly reproducible so please let me know how I can help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-13-generic 6.5.0-13.13
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: awaahm 6528 F wireplumber
/dev/snd/controlC2: awaahm 6528 F wireplumber
/dev/snd/controlC0: awaahm 6528 F wireplumber
/dev/snd/seq:awaahm 6512 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 4 20:05:05 2023
InstallationDate: Installed on 2021-03-30 (979 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-13-generic
root=UUID=0392d1e9-f9ce-4e11-a853-626267f141ac ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-13-generic N/A
linux-backports-modules-6.5.0-13-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-10 (24 days ago)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8702
dmi.board.asset.tag: Default string
dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr8702:bd08/10/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2023-07-26T18:11:44.877297
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045584] Re: [amdgpu] Firefox/brave browser causes GPU reset and Gnome-shell crash
Small update. Issue is resolved by removing ROCm drivers on the latest
version of Ubuntu 23.10. It seems that ROCm was the issue. I do not know
how and where I should report this or does it need to be verified by
someone else.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045584
Title:
[amdgpu] Firefox/brave browser causes GPU reset and Gnome-shell crash
Status in linux package in Ubuntu:
New
Bug description:
I am using UBUNTU 23.10 with Vega 64 using the latest amdgpu drivers.
This started when I upgraded to 23.10. Was not happening in 22.04 or
23.04.
In Wayland, it always crashes the gnome session and I have to hardware
power off the system. It also sometimes makes a weird pixelated image
on the screen, kind of like static with both firefox and brave
broswers.
In xorg session only firefox seems to crash the session but weirdly it
just "logs me out" to the welcome screen. Brave works fine.
I thought it was a mem issue but I have run memtest twice now with all
tests passing for the whole night. I have also run prime95
successfully on both windows and ubuntu now for 5-6 hours as well just
to stress the system for both CPU and mem and no issues there.
Its fairly reproducible so please let me know how I can help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-13-generic 6.5.0-13.13
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: awaahm 6528 F wireplumber
/dev/snd/controlC2: awaahm 6528 F wireplumber
/dev/snd/controlC0: awaahm 6528 F wireplumber
/dev/snd/seq:awaahm 6512 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 4 20:05:05 2023
InstallationDate: Installed on 2021-03-30 (979 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-13-generic
root=UUID=0392d1e9-f9ce-4e11-a853-626267f141ac ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-13-generic N/A
linux-backports-modules-6.5.0-13-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-10 (24 days ago)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8702
dmi.board.asset.tag: Default string
dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr8702:bd08/10/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2023-07-26T18:11:44.877297
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045584] [NEW] Firefox/brave browser causes GPU reset
Public bug reported:
I am using UBUNTU 23.10 with Vega 64 using the latest amdgpu drivers.
This started when I upgraded to 23.10. Was not happening in 22.04 or
23.04.
In Wayland, it always crashes the gnome session and I have to hardware
power off the system. It also sometimes makes a weird pixelated image on
the screen, kind of like static with both firefox and brave broswers.
In xorg session only firefox seems to crash the session but weirdly it
just "logs me out" to the welcome screen. Brave works fine.
I thought it was a mem issue but I have run memtest twice now with all
tests passing for the whole night. I have also run prime95 successfully
on both windows and ubuntu now for 5-6 hours as well just to stress the
system for both CPU and mem and no issues there.
Its fairly reproducible so please let me know how I can help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-13-generic 6.5.0-13.13
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: awaahm 6528 F wireplumber
/dev/snd/controlC2: awaahm 6528 F wireplumber
/dev/snd/controlC0: awaahm 6528 F wireplumber
/dev/snd/seq:awaahm 6512 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 4 20:05:05 2023
InstallationDate: Installed on 2021-03-30 (979 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-13-generic
root=UUID=0392d1e9-f9ce-4e11-a853-626267f141ac ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-13-generic N/A
linux-backports-modules-6.5.0-13-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-10 (24 days ago)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8702
dmi.board.asset.tag: Default string
dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr8702:bd08/10/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2023-07-26T18:11:44.877297
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045584
Title:
Firefox/brave browser causes GPU reset
Status in linux package in Ubuntu:
New
Bug description:
I am using UBUNTU 23.10 with Vega 64 using the latest amdgpu drivers.
This started when I upgraded to 23.10. Was not happening in 22.04 or
23.04.
In Wayland, it always crashes the gnome session and I have to hardware
power off the system. It also sometimes makes a weird pixelated image
on the screen, kind of like static with both firefox and brave
broswers.
In xorg session only firefox seems to crash the session but weirdly it
just "logs me out" to the welcome screen. Brave works fine.
I thought it was a mem issue but I have run memtest twice now with all
tests passing for the whole night. I have also run prime95
successfully on both windows and ubuntu now for 5-6 hours as well just
to stress the system for both CPU and mem and no issues there.
Its fairly reproducible so please let me know how I can help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-13-generic 6.5.0-13.13
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: awaahm 6528 F wireplumber
/dev/snd/controlC2: awaahm 6528 F wireplumber
/dev/snd/controlC0: awaahm 6528 F wireplumber
/dev/snd/seq:awaahm 6512 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec
[Kernel-packages] [Bug 2045584] Re: Firefox/brave browser causes GPU reset
Can be easily replicated by having vega64 gpu:
- create ubuntu live cd with 23.10.1
- login computer using livecd and select to test ubuntu
- open firefox
- run a few tests using speedtest.net
- open a few other sites and wait a few mins until you are logged out.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045584
Title:
Firefox/brave browser causes GPU reset
Status in linux package in Ubuntu:
New
Bug description:
I am using UBUNTU 23.10 with Vega 64 using the latest amdgpu drivers.
This started when I upgraded to 23.10. Was not happening in 22.04 or
23.04.
In Wayland, it always crashes the gnome session and I have to hardware
power off the system. It also sometimes makes a weird pixelated image
on the screen, kind of like static with both firefox and brave
broswers.
In xorg session only firefox seems to crash the session but weirdly it
just "logs me out" to the welcome screen. Brave works fine.
I thought it was a mem issue but I have run memtest twice now with all
tests passing for the whole night. I have also run prime95
successfully on both windows and ubuntu now for 5-6 hours as well just
to stress the system for both CPU and mem and no issues there.
Its fairly reproducible so please let me know how I can help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-13-generic 6.5.0-13.13
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: awaahm 6528 F wireplumber
/dev/snd/controlC2: awaahm 6528 F wireplumber
/dev/snd/controlC0: awaahm 6528 F wireplumber
/dev/snd/seq:awaahm 6512 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 4 20:05:05 2023
InstallationDate: Installed on 2021-03-30 (979 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-13-generic
root=UUID=0392d1e9-f9ce-4e11-a853-626267f141ac ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-13-generic N/A
linux-backports-modules-6.5.0-13-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-10 (24 days ago)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8702
dmi.board.asset.tag: Default string
dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr8702:bd08/10/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2023-07-26T18:11:44.877297
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983625] [NEW] 5.15.0-1013-oracle: Unable to boot large memory SEV guest without setting swiotlb parameter.
Public bug reported: When launching a SEV Ubuntu22.04 guest with e.g. memory > 16876M, Ubuntu kernel 5.15.0-1013-oracle panics unless swiotlb=262144 is specified on guest kernel parameters. It seems that the kernel tries to adjust swiotlb buffer size but can not do that and crashes. With a memory size such as 8G, the guest boots fine. HOST INFO Host type : OCI Bare-Metal Server Server/Machine: ORACLE SERVER E2-2c CPU model : AMD EPYC 7742 64-Core Processor Architecture : x86_64 Hostname : atanveer-amd-sme OS: Oracle Linux Server release 7.9 Kernel: 5.4.17-2136.309.4.el7uek.x86_64 #2 SMP Tue Jun 28 17:35:13 PDT 2022 Hypervisor: QEMU emulator version 4.2.1 (qemu-4.2.1-18.oci.el7) OVMF/AAVMF: OVMF-1.6.3-1.el7.noarch Qemu command to launch SEV guest: /bin/qemu-system-x86_64 -name OL22.04-uefi \ -machine q35 \ -enable-kvm \ -cpu host,+host-phys-bits \ -m 16877M \ -smp 8,maxcpus=240 \ -D ./22.04-uefi.log \ -nodefaults \ -monitor stdio \ -vnc 0.0.0.0:0,to=999 \ -vga std \ -drive file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly \ -drive file=OVMF_VARS.pure-efi.fd.ol22.04,index=1,if=pflash,format=raw \ -device virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true \ -drive file=Ubuntu-22.04-2022.06.16-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk \ -device ide-hd,drive=local_disk0,id=local_disk1,bootindex=0 \ -qmp tcp:127.0.0.1:3334,server,nowait \ -serial telnet:127.0.0.1:,server,nowait \ -device virtio-rng-pci,disable-legacy=on,iommu_platform=true \ -object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1 \ -machine memory-encryption=sev0 Console log: [0.005025] software IO TLB: SWIOTLB bounce buffer size adjusted to 1011MB [0.033881] kvm-guest: KVM setup pv remote TLB flush [0.054931] software IO TLB: Cannot allocate buffer [0.248933] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.249582] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.317440] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.317440] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [0.424952] iommu: DMA domain TLB invalidation policy: lazy mode [0.570923] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.571669] software IO TLB: No low mem . . . . [1.233515] ata1: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010100 irq 28 [1.234985] ata2: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010180 irq 28 [1.236464] ata3: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010200 irq 28 [1.237863] ata4: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010280 irq 28 [1.239257] ata5: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010300 irq 28 [1.240659] ata6: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010380 irq 28 [1.555165] ata5: SATA link down (SStatus 0 SControl 300) [1.556661] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [1.558232] ata2: SATA link down (SStatus 0 SControl 300) [1.559728] ata4: SATA link down (SStatus 0 SControl 300) [1.560996] ata3: SATA link down (SStatus 0 SControl 300) [1.562134] ata1: SATA link down (SStatus 0 SControl 300) [1.563566] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [6.911450] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [6.912906] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [ 12.288045] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 12.289904] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [ 17.663548] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 242.883993] INFO: task kworker/u480:0:9 blocked for more than 120 seconds. [ 242.885619] Not tainted 5.15.0-1013-oracle #17-Ubuntu [ 242.886743] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.888198] task:kworker/u480:0 state:D stack:0 pid:9 ppid: 2 flags:0x4000 [ 242.889703] Workqueue: events_unbound async_run_entry_fn [ 242.890882] Call Trace: [ 242.891727] Full console log is attached. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "detailed console log" https://bugs.launchpad.net/bugs/1983625/+attachment/5607058/+files/5.15_sev_crash.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983625 Title: 5.15.0-1013-oracle: Unable to boot large memory SEV guest without setting swiotlb parameter. Status in linux package in Ubuntu: New Bug description: When launching a SEV Ubuntu22.04 guest with e.g. memory > 16876M, Ubuntu kernel 5.15.0-1013-oracle panics unless swiotlb=262144 is specified on guest kernel parameters. It seems that the kernel tries to adjust swiotlb buffer size but can not do that and crashes. W
[Kernel-packages] [Bug 1983625] Re: 5.15.0-1013-oracle: Unable to boot large memory SEV guest without setting swiotlb parameter.
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983625 Title: 5.15.0-1013-oracle: Unable to boot large memory SEV guest without setting swiotlb parameter. Status in linux package in Ubuntu: Confirmed Bug description: When launching a SEV Ubuntu22.04 guest with e.g. memory > 16876M, Ubuntu kernel 5.15.0-1013-oracle panics unless swiotlb=262144 is specified on guest kernel parameters. It seems that the kernel tries to adjust swiotlb buffer size but can not do that and crashes. With a memory size such as 8G, the guest boots fine. HOST INFO Host type : OCI Bare-Metal Server Server/Machine: ORACLE SERVER E2-2c CPU model : AMD EPYC 7742 64-Core Processor Architecture : x86_64 Hostname : atanveer-amd-sme OS: Oracle Linux Server release 7.9 Kernel: 5.4.17-2136.309.4.el7uek.x86_64 #2 SMP Tue Jun 28 17:35:13 PDT 2022 Hypervisor: QEMU emulator version 4.2.1 (qemu-4.2.1-18.oci.el7) OVMF/AAVMF: OVMF-1.6.3-1.el7.noarch Qemu command to launch SEV guest: /bin/qemu-system-x86_64 -name OL22.04-uefi \ -machine q35 \ -enable-kvm \ -cpu host,+host-phys-bits \ -m 16877M \ -smp 8,maxcpus=240 \ -D ./22.04-uefi.log \ -nodefaults \ -monitor stdio \ -vnc 0.0.0.0:0,to=999 \ -vga std \ -drive file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly \ -drive file=OVMF_VARS.pure-efi.fd.ol22.04,index=1,if=pflash,format=raw \ -device virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true \ -drive file=Ubuntu-22.04-2022.06.16-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk \ -device ide-hd,drive=local_disk0,id=local_disk1,bootindex=0 \ -qmp tcp:127.0.0.1:3334,server,nowait \ -serial telnet:127.0.0.1:,server,nowait \ -device virtio-rng-pci,disable-legacy=on,iommu_platform=true \ -object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1 \ -machine memory-encryption=sev0 Console log: [0.005025] software IO TLB: SWIOTLB bounce buffer size adjusted to 1011MB [0.033881] kvm-guest: KVM setup pv remote TLB flush [0.054931] software IO TLB: Cannot allocate buffer [0.248933] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.249582] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.317440] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.317440] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [0.424952] iommu: DMA domain TLB invalidation policy: lazy mode [0.570923] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.571669] software IO TLB: No low mem . . . . [1.233515] ata1: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010100 irq 28 [1.234985] ata2: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010180 irq 28 [1.236464] ata3: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010200 irq 28 [1.237863] ata4: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010280 irq 28 [1.239257] ata5: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010300 irq 28 [1.240659] ata6: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010380 irq 28 [1.555165] ata5: SATA link down (SStatus 0 SControl 300) [1.556661] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [1.558232] ata2: SATA link down (SStatus 0 SControl 300) [1.559728] ata4: SATA link down (SStatus 0 SControl 300) [1.560996] ata3: SATA link down (SStatus 0 SControl 300) [1.562134] ata1: SATA link down (SStatus 0 SControl 300) [1.563566] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [6.911450] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [6.912906] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [ 12.288045] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 12.289904] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [ 17.663548] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 242.883993] INFO: task kworker/u480:0:9 blocked for more than 120 seconds. [ 242.885619] Not tainted 5.15.0-1013-oracle #17-Ubuntu [ 242.886743] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.888198] task:kworker/u480:0 state:D stack:0 pid:9 ppid: 2 flags:0x4000 [ 242.889703] Workqueue: events_unbound async_run_entry_fn [ 242.890882] Call Trace: [ 242.891727] Full console log is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kerne
[Kernel-packages] [Bug 1983625] Re: 5.15.0-1013-oracle: Unable to boot large memory SEV guest without setting swiotlb parameter.
Can not run apport-collect logs since the SEV guest instance fails to boot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983625 Title: 5.15.0-1013-oracle: Unable to boot large memory SEV guest without setting swiotlb parameter. Status in linux package in Ubuntu: Confirmed Bug description: When launching a SEV Ubuntu22.04 guest with e.g. memory > 16876M, Ubuntu kernel 5.15.0-1013-oracle panics unless swiotlb=262144 is specified on guest kernel parameters. It seems that the kernel tries to adjust swiotlb buffer size but can not do that and crashes. With a memory size such as 8G, the guest boots fine. HOST INFO Host type : OCI Bare-Metal Server Server/Machine: ORACLE SERVER E2-2c CPU model : AMD EPYC 7742 64-Core Processor Architecture : x86_64 Hostname : atanveer-amd-sme OS: Oracle Linux Server release 7.9 Kernel: 5.4.17-2136.309.4.el7uek.x86_64 #2 SMP Tue Jun 28 17:35:13 PDT 2022 Hypervisor: QEMU emulator version 4.2.1 (qemu-4.2.1-18.oci.el7) OVMF/AAVMF: OVMF-1.6.3-1.el7.noarch Qemu command to launch SEV guest: /bin/qemu-system-x86_64 -name OL22.04-uefi \ -machine q35 \ -enable-kvm \ -cpu host,+host-phys-bits \ -m 16877M \ -smp 8,maxcpus=240 \ -D ./22.04-uefi.log \ -nodefaults \ -monitor stdio \ -vnc 0.0.0.0:0,to=999 \ -vga std \ -drive file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly \ -drive file=OVMF_VARS.pure-efi.fd.ol22.04,index=1,if=pflash,format=raw \ -device virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true \ -drive file=Ubuntu-22.04-2022.06.16-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk \ -device ide-hd,drive=local_disk0,id=local_disk1,bootindex=0 \ -qmp tcp:127.0.0.1:3334,server,nowait \ -serial telnet:127.0.0.1:,server,nowait \ -device virtio-rng-pci,disable-legacy=on,iommu_platform=true \ -object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1 \ -machine memory-encryption=sev0 Console log: [0.005025] software IO TLB: SWIOTLB bounce buffer size adjusted to 1011MB [0.033881] kvm-guest: KVM setup pv remote TLB flush [0.054931] software IO TLB: Cannot allocate buffer [0.248933] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.249582] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.317440] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.317440] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [0.424952] iommu: DMA domain TLB invalidation policy: lazy mode [0.570923] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.571669] software IO TLB: No low mem . . . . [1.233515] ata1: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010100 irq 28 [1.234985] ata2: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010180 irq 28 [1.236464] ata3: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010200 irq 28 [1.237863] ata4: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010280 irq 28 [1.239257] ata5: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010300 irq 28 [1.240659] ata6: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010380 irq 28 [1.555165] ata5: SATA link down (SStatus 0 SControl 300) [1.556661] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [1.558232] ata2: SATA link down (SStatus 0 SControl 300) [1.559728] ata4: SATA link down (SStatus 0 SControl 300) [1.560996] ata3: SATA link down (SStatus 0 SControl 300) [1.562134] ata1: SATA link down (SStatus 0 SControl 300) [1.563566] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [6.911450] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [6.912906] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [ 12.288045] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 12.289904] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [ 17.663548] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 242.883993] INFO: task kworker/u480:0:9 blocked for more than 120 seconds. [ 242.885619] Not tainted 5.15.0-1013-oracle #17-Ubuntu [ 242.886743] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.888198] task:kworker/u480:0 state:D stack:0 pid:9 ppid: 2 flags:0x4000 [ 242.889703] Workqueue: events_unbound async_run_entry_fn [ 242.890882] Call Trace: [ 242.891727] Full console log is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net
