Public bug reported:
Since upgrading from kernel 6.17.0-29-generic to 6.17.0-35-generic, the machine
completely freezes (no input, blank/frozen display, requires a hard power-off)
when a GPU-accelerated application — in practice Chromium-based browsers (Google
Chrome, Brave) — is launched. The kernel log shows nouveau FIFO faults
(PAGE_NOT_PRESENT on the PGRAPH engine) followed by SCHED_ERROR
[CTXSW_TIMEOUT] and kernel WARNING/Call Trace inside the nouveau FIFO code.
The previous kernel (6.17.0-29-generic) does not exhibit this on the same
hardware and userspace.
System information
- Hardware: Hewlett-Packard HP Z440 Workstation
- GPU: NVIDIA Corporation GF119 [NVS 310] [10de:107d] (rev a1) (Fermi)
- GPU driver in use: nouveau (kernel modules: nvidiafb, nouveau)
- OS: Ubuntu 24.04.4 LTS (noble)
- Affected kernel: 6.17.0-35.35~24.04.1-generic (6.17.13), from
noble-updates/main
- Last known-good kernel: 6.17.0-29.29~24.04.1-generic (6.17.13)
Steps to reproduce
1. Boot kernel 6.17.0-35-generic into the default GNOME session.
2. Launch Google Chrome or Brave (default settings, GPU acceleration enabled).
3. Within seconds the entire machine freezes; only a hard power-off recovers it.
Expected result
The browser opens and renders normally (as it does on 6.17.0-29-generic). A
malfunction in GPU command submission should at most reset the GPU channel or
terminate the offending process — it should not hang the whole machine.
Actual result
The machine freezes completely and must be power-cycled.
Regression data
Kernel package install dates (from /var/log/dpkg.log):
2026-05-20 09:38:02 linux-image-6.17.0-29-generic (last good)
2026-06-04 15:45:12 linux-image-6.17.0-35-generic (first bad)
Count of nouveau fault signatures (SCHED_ERROR / PAGE_NOT_PRESENT / "fifo:
fault")
per boot, with the kernel that boot ran. Collected via journalctl per-boot:
Date Kernel nouveau faults in boot
2026-05-21 6.17.0-29 0
2026-05-22 6.17.0-29 0
2026-05-25 6.17.0-29 0
2026-05-26 6.17.0-29 0
2026-05-26 6.17.0-29 0
2026-06-01 6.17.0-29 0
2026-06-02 6.17.0-29 0
2026-06-03 6.17.0-29 0
2026-06-04 6.17.0-29 2 <- 6.17.0-35 installed 15:45 this day
2026-06-05 6.17.0-35 21
2026-06-05 6.17.0-35 26
2026-06-08 6.17.0-35 14
2026-06-08 6.17.0-35 18
2026-06-08 6.17.0-35 15
2026-06-09 6.17.0-35 12
2026-06-09 6.17.0-35 16
2026-06-10 6.17.0-35 10
2026-06-10 6.17.0-35 8
Note: faults appear only in boots where a GPU-accelerated browser session was
started; boots on 6.17.0-35 where no such session ran show 0 faults. No boot on
6.17.0-29 produced any fault across roughly two weeks of normal use.
Log excerpts
Fault sequence on 6.17.0-35 (browser named as the channel owner):
kernel: Linux version 6.17.0-35-generic ... (Ubuntu
6.17.0-35.35~24.04.1-generic 6.17.13)
kernel: nouveau 0000:02:00.0: drm: failed to create ce channel, -22
kernel: nouveau 0000:02:00.0: Direct firmware load for nouveau/nvd9_fuc084
failed with error -2
kernel: nouveau 0000:02:00.0: Direct firmware load for nouveau/nvd9_fuc084d
failed with error -2
kernel: nouveau 0000:02:00.0: msvld: unable to load firmware data
kernel: nouveau 0000:02:00.0: msvld: init failed, -19
kernel: nouveau 0000:02:00.0: fifo: fault 00 [READ] at 0000000000000000
engine 00 [PGRAPH] client 05 [HUB/CTXCTL] reason 02 [PAGE_NOT_PRESENT] on
channel 6 [003fa92000 brave[3732]]
kernel: nouveau 0000:02:00.0: fifo:000000:0006:[brave[3732]] rc scheduled
kernel: nouveau 0000:02:00.0: fifo:000000: rc scheduled
Kernel WARNING / Call Trace on 6.17.0-35 (FIFO context-switch timeout):
kernel: nouveau 0000:02:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
kernel: nouveau 0000:02:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
kernel: WARNING: CPU: 10 PID: 79 at
drivers/gpu/drm/nouveau/nvkm/engine/fifo/nv50.c:228 nv50_runl_wait+0xe2/0xf0
[nouveau]
kernel: RIP: 0010:nv50_runl_wait+0xe2/0xf0 [nouveau]
kernel: nouveau 0000:02:00.0: fifo: SCHED_ERROR 0d []
kernel: WARNING: CPU: 3 PID: 5048 at
drivers/gpu/drm/nouveau/nvkm/engine/fifo/runl.c:251
nvkm_runl_preempt_wait+0xf3/0x110 [nouveau]
kernel: RIP: 0010:nvkm_runl_preempt_wait+0xf3/0x110 [nouveau]
kernel: Call Trace:
kernel: nvkm_client_ioctl+0xe/0x20 [nouveau]
kernel: nvif_object_dtor+0x7a/0xb0 [nouveau]
kernel: nouveau_channel_del+0x8b/0xf0 [nouveau]
kernel: nouveau_abi16_chan_fini.isra.0+0x143/0x1d0 [nouveau]
kernel: nouveau_abi16_ioctl_channel_free+0x50/0xa0 [nouveau]
Same hardware and userspace on 6.17.0-29 (no faults that boot):
kernel: Linux version 6.17.0-29-generic ... (Ubuntu
6.17.0-29.29~24.04.1-generic 6.17.13)
nouveau fault signatures in boot: 0
Workaround found
Disabling GPU/hardware acceleration in the browser (e.g. launching with
--disable-gpu, or turning off "Use hardware acceleration when available")
prevents the freeze on 6.17.0-35. Booting 6.17.0-29 also avoids it with GPU
acceleration left enabled.
Environment notes (facts, for completeness)
- Both Chrome and Brave update frequently; the most recent on this system were
Chrome 149.0.7827.53 (2026-06-10) and Brave 1.91.171 (2026-06-10). The browser
versions present during the fault-free 6.17.0-29 period were therefore earlier
than those during the 6.17.0-35 period.
- The two kernels share the same upstream base string (6.17.13); the difference
is the Ubuntu packaging revision (-29 vs -35).
---
Reporter's analysis
The data above is intended to stand on its own. The following is my
reading of it:
- The onset of the freezes is tightly correlated in time with the 6.17.0-29 ->
6.17.0-35 kernel change (installed 2026-06-04; faults begin the first boot
after, 2026-06-05). The hardware did not change.
- Because a userspace application should not be able to hard-hang the kernel,
and the previous kernel handled the same class of workload without faults, the
defect appears to live in the nouveau FIFO handling in 6.17.0-35 rather than
in
the browser. The browser is the trigger; the GPU acceleration workload is what
exercises the faulting path.
- The accompanying messages ("failed to create ce channel, -22"; nvd9 firmware
load failures; msvld init failure) may or may not be related to the hang; I
cannot say whether they are pre-existing/benign on this card or contributory.
- A bisection window of 6.17.0-29 (good) to 6.17.0-35 (bad) is available on this
machine if it would help isolate the change.
I have filed this information with the help of AI as I wanted to be as
descriptive as possible. Please let me know if this is not acceptable
and will revert this bug.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.17.0-35-generic 6.17.0-35.35~24.04.1
ProcVersionSignature: Ubuntu 6.17.0-35.35~24.04.1-generic 6.17.13
Uname: Linux 6.17.0-35-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 10 10:37:32 2026
InstallationDate: Installed on 2025-07-01 (344 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
MachineType: Hewlett-Packard HP Z440 Workstation
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-35-generic
root=UUID=dff0a4d6-2ae4-4be3-8e78-2babaabf9552 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.17.0-35-generic N/A
linux-backports-modules-6.17.0-35-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.27
RfKill:
SourcePackage: linux-hwe-6.17
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2015
dmi.bios.release: 1.62
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M60 v01.62
dmi.board.name: 212B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: unknown
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrM60v01.62:bd07/22/2015:br1.62:svnHewlett-Packard:pnHPZ440Workstation:pvr:rvnHewlett-Packard:rn212B:rvrunknown:cvnHewlett-Packard:ct6:cvr:skuF5W13AV:
dmi.product.family: 103C_53335X G=D
dmi.product.name: HP Z440 Workstation
dmi.product.sku: F5W13AV
dmi.sys.vendor: Hewlett-Packard
** Affects: linux-hwe-6.17 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble wayland-session
** Description changed:
Since upgrading from kernel 6.17.0-29-generic to 6.17.0-35-generic, the
machine
completely freezes (no input, blank/frozen display, requires a hard power-off)
when a GPU-accelerated application — in practice Chromium-based browsers
(Google
Chrome, Brave) — is launched. The kernel log shows nouveau FIFO faults
(PAGE_NOT_PRESENT on the PGRAPH engine) followed by SCHED_ERROR
[CTXSW_TIMEOUT] and kernel WARNING/Call Trace inside the nouveau FIFO code.
The previous kernel (6.17.0-29-generic) does not exhibit this on the same
hardware and userspace.
- ## System information
+ System information
- Hardware: Hewlett-Packard HP Z440 Workstation
- GPU: NVIDIA Corporation GF119 [NVS 310] [10de:107d] (rev a1) (Fermi)
- GPU driver in use: nouveau (kernel modules: nvidiafb, nouveau)
- OS: Ubuntu 24.04.4 LTS (noble)
- Affected kernel: 6.17.0-35.35~24.04.1-generic (6.17.13), from
noble-updates/main
- Last known-good kernel: 6.17.0-29.29~24.04.1-generic (6.17.13)
- ## Steps to reproduce
+ Steps to reproduce
1. Boot kernel 6.17.0-35-generic into the default GNOME session.
2. Launch Google Chrome or Brave (default settings, GPU acceleration enabled).
3. Within seconds the entire machine freezes; only a hard power-off recovers
it.
- ## Expected result
+ Expected result
The browser opens and renders normally (as it does on 6.17.0-29-generic). A
malfunction in GPU command submission should at most reset the GPU channel or
terminate the offending process — it should not hang the whole machine.
- ## Actual result
+ Actual result
The machine freezes completely and must be power-cycled.
- ## Regression data
+ Regression data
Kernel package install dates (from /var/log/dpkg.log):
- 2026-05-20 09:38:02 linux-image-6.17.0-29-generic (last good)
- 2026-06-04 15:45:12 linux-image-6.17.0-35-generic (first bad)
+ 2026-05-20 09:38:02 linux-image-6.17.0-29-generic (last good)
+ 2026-06-04 15:45:12 linux-image-6.17.0-35-generic (first bad)
Count of nouveau fault signatures (SCHED_ERROR / PAGE_NOT_PRESENT / "fifo:
fault")
per boot, with the kernel that boot ran. Collected via journalctl per-boot:
- Date Kernel nouveau faults in boot
- 2026-05-21 6.17.0-29 0
- 2026-05-22 6.17.0-29 0
- 2026-05-25 6.17.0-29 0
- 2026-05-26 6.17.0-29 0
- 2026-05-26 6.17.0-29 0
- 2026-06-01 6.17.0-29 0
- 2026-06-02 6.17.0-29 0
- 2026-06-03 6.17.0-29 0
- 2026-06-04 6.17.0-29 2 <- 6.17.0-35 installed 15:45 this day
- 2026-06-05 6.17.0-35 21
- 2026-06-05 6.17.0-35 26
- 2026-06-08 6.17.0-35 14
- 2026-06-08 6.17.0-35 18
- 2026-06-08 6.17.0-35 15
- 2026-06-09 6.17.0-35 12
- 2026-06-09 6.17.0-35 16
- 2026-06-10 6.17.0-35 10
- 2026-06-10 6.17.0-35 8
+ Date Kernel nouveau faults in boot
+ 2026-05-21 6.17.0-29 0
+ 2026-05-22 6.17.0-29 0
+ 2026-05-25 6.17.0-29 0
+ 2026-05-26 6.17.0-29 0
+ 2026-05-26 6.17.0-29 0
+ 2026-06-01 6.17.0-29 0
+ 2026-06-02 6.17.0-29 0
+ 2026-06-03 6.17.0-29 0
+ 2026-06-04 6.17.0-29 2 <- 6.17.0-35 installed 15:45 this day
+ 2026-06-05 6.17.0-35 21
+ 2026-06-05 6.17.0-35 26
+ 2026-06-08 6.17.0-35 14
+ 2026-06-08 6.17.0-35 18
+ 2026-06-08 6.17.0-35 15
+ 2026-06-09 6.17.0-35 12
+ 2026-06-09 6.17.0-35 16
+ 2026-06-10 6.17.0-35 10
+ 2026-06-10 6.17.0-35 8
Note: faults appear only in boots where a GPU-accelerated browser session was
started; boots on 6.17.0-35 where no such session ran show 0 faults. No boot
on
6.17.0-29 produced any fault across roughly two weeks of normal use.
- ## Log excerpts
+ Log excerpts
Fault sequence on 6.17.0-35 (browser named as the channel owner):
- kernel: Linux version 6.17.0-35-generic ... (Ubuntu
6.17.0-35.35~24.04.1-generic 6.17.13)
- kernel: nouveau 0000:02:00.0: drm: failed to create ce channel, -22
- kernel: nouveau 0000:02:00.0: Direct firmware load for
nouveau/nvd9_fuc084 failed with error -2
- kernel: nouveau 0000:02:00.0: Direct firmware load for
nouveau/nvd9_fuc084d failed with error -2
- kernel: nouveau 0000:02:00.0: msvld: unable to load firmware data
- kernel: nouveau 0000:02:00.0: msvld: init failed, -19
- kernel: nouveau 0000:02:00.0: fifo: fault 00 [READ] at 0000000000000000
engine 00 [PGRAPH] client 05 [HUB/CTXCTL] reason 02 [PAGE_NOT_PRESENT] on
channel 6 [003fa92000 brave[3732]]
- kernel: nouveau 0000:02:00.0: fifo:000000:0006:[brave[3732]] rc scheduled
- kernel: nouveau 0000:02:00.0: fifo:000000: rc scheduled
+ kernel: Linux version 6.17.0-35-generic ... (Ubuntu
6.17.0-35.35~24.04.1-generic 6.17.13)
+ kernel: nouveau 0000:02:00.0: drm: failed to create ce channel, -22
+ kernel: nouveau 0000:02:00.0: Direct firmware load for
nouveau/nvd9_fuc084 failed with error -2
+ kernel: nouveau 0000:02:00.0: Direct firmware load for
nouveau/nvd9_fuc084d failed with error -2
+ kernel: nouveau 0000:02:00.0: msvld: unable to load firmware data
+ kernel: nouveau 0000:02:00.0: msvld: init failed, -19
+ kernel: nouveau 0000:02:00.0: fifo: fault 00 [READ] at 0000000000000000
engine 00 [PGRAPH] client 05 [HUB/CTXCTL] reason 02 [PAGE_NOT_PRESENT] on
channel 6 [003fa92000 brave[3732]]
+ kernel: nouveau 0000:02:00.0: fifo:000000:0006:[brave[3732]] rc scheduled
+ kernel: nouveau 0000:02:00.0: fifo:000000: rc scheduled
Kernel WARNING / Call Trace on 6.17.0-35 (FIFO context-switch timeout):
- kernel: nouveau 0000:02:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
- kernel: nouveau 0000:02:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
- kernel: WARNING: CPU: 10 PID: 79 at
drivers/gpu/drm/nouveau/nvkm/engine/fifo/nv50.c:228 nv50_runl_wait+0xe2/0xf0
[nouveau]
- kernel: RIP: 0010:nv50_runl_wait+0xe2/0xf0 [nouveau]
- kernel: nouveau 0000:02:00.0: fifo: SCHED_ERROR 0d []
- kernel: WARNING: CPU: 3 PID: 5048 at
drivers/gpu/drm/nouveau/nvkm/engine/fifo/runl.c:251
nvkm_runl_preempt_wait+0xf3/0x110 [nouveau]
- kernel: RIP: 0010:nvkm_runl_preempt_wait+0xf3/0x110 [nouveau]
- kernel: Call Trace:
- kernel: nvkm_client_ioctl+0xe/0x20 [nouveau]
- kernel: nvif_object_dtor+0x7a/0xb0 [nouveau]
- kernel: nouveau_channel_del+0x8b/0xf0 [nouveau]
- kernel: nouveau_abi16_chan_fini.isra.0+0x143/0x1d0 [nouveau]
- kernel: nouveau_abi16_ioctl_channel_free+0x50/0xa0 [nouveau]
+ kernel: nouveau 0000:02:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
+ kernel: nouveau 0000:02:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
+ kernel: WARNING: CPU: 10 PID: 79 at
drivers/gpu/drm/nouveau/nvkm/engine/fifo/nv50.c:228 nv50_runl_wait+0xe2/0xf0
[nouveau]
+ kernel: RIP: 0010:nv50_runl_wait+0xe2/0xf0 [nouveau]
+ kernel: nouveau 0000:02:00.0: fifo: SCHED_ERROR 0d []
+ kernel: WARNING: CPU: 3 PID: 5048 at
drivers/gpu/drm/nouveau/nvkm/engine/fifo/runl.c:251
nvkm_runl_preempt_wait+0xf3/0x110 [nouveau]
+ kernel: RIP: 0010:nvkm_runl_preempt_wait+0xf3/0x110 [nouveau]
+ kernel: Call Trace:
+ kernel: nvkm_client_ioctl+0xe/0x20 [nouveau]
+ kernel: nvif_object_dtor+0x7a/0xb0 [nouveau]
+ kernel: nouveau_channel_del+0x8b/0xf0 [nouveau]
+ kernel: nouveau_abi16_chan_fini.isra.0+0x143/0x1d0 [nouveau]
+ kernel: nouveau_abi16_ioctl_channel_free+0x50/0xa0 [nouveau]
Same hardware and userspace on 6.17.0-29 (no faults that boot):
- kernel: Linux version 6.17.0-29-generic ... (Ubuntu
6.17.0-29.29~24.04.1-generic 6.17.13)
- nouveau fault signatures in boot: 0
+ kernel: Linux version 6.17.0-29-generic ... (Ubuntu
6.17.0-29.29~24.04.1-generic 6.17.13)
+ nouveau fault signatures in boot: 0
- ## Workaround found
+ Workaround found
Disabling GPU/hardware acceleration in the browser (e.g. launching with
--disable-gpu, or turning off "Use hardware acceleration when available")
prevents the freeze on 6.17.0-35. Booting 6.17.0-29 also avoids it with GPU
acceleration left enabled.
- ## Environment notes (facts, for completeness)
+ Environment notes (facts, for completeness)
- Both Chrome and Brave update frequently; the most recent on this system were
- Chrome 149.0.7827.53 (2026-06-10) and Brave 1.91.171 (2026-06-10). The
browser
- versions present during the fault-free 6.17.0-29 period were therefore
earlier
- than those during the 6.17.0-35 period.
+ Chrome 149.0.7827.53 (2026-06-10) and Brave 1.91.171 (2026-06-10). The
browser
+ versions present during the fault-free 6.17.0-29 period were therefore
earlier
+ than those during the 6.17.0-35 period.
- The two kernels share the same upstream base string (6.17.13); the
difference
- is the Ubuntu packaging revision (-29 vs -35).
+ is the Ubuntu packaging revision (-29 vs -35).
---
- ## Reporter's analysis (interpretation, not measured fact)
+ Reporter's analysis
The data above is intended to stand on its own. The following is my
reading of it:
- The onset of the freezes is tightly correlated in time with the 6.17.0-29 ->
- 6.17.0-35 kernel change (installed 2026-06-04; faults begin the first boot
- after, 2026-06-05). The hardware did not change.
+ 6.17.0-35 kernel change (installed 2026-06-04; faults begin the first boot
+ after, 2026-06-05). The hardware did not change.
- Because a userspace application should not be able to hard-hang the kernel,
- and the previous kernel handled the same class of workload without faults,
the
- defect appears to live in the nouveau FIFO handling in 6.17.0-35 rather
than in
- the browser. The browser is the trigger; the GPU acceleration workload is
what
- exercises the faulting path.
+ and the previous kernel handled the same class of workload without faults,
the
+ defect appears to live in the nouveau FIFO handling in 6.17.0-35 rather
than in
+ the browser. The browser is the trigger; the GPU acceleration workload is
what
+ exercises the faulting path.
- The accompanying messages ("failed to create ce channel, -22"; nvd9 firmware
- load failures; msvld init failure) may or may not be related to the hang; I
- cannot say whether they are pre-existing/benign on this card or
contributory.
+ load failures; msvld init failure) may or may not be related to the hang; I
+ cannot say whether they are pre-existing/benign on this card or
contributory.
- A bisection window of 6.17.0-29 (good) to 6.17.0-35 (bad) is available on
this
- machine if it would help isolate the change.
+ machine if it would help isolate the change.
I have filed this information with the help of AI as I wanted to be as
descriptive as possible. Please let me know if this is not acceptable
and will revert this bug.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.17.0-35-generic 6.17.0-35.35~24.04.1
ProcVersionSignature: Ubuntu 6.17.0-35.35~24.04.1-generic 6.17.13
Uname: Linux 6.17.0-35-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 10 10:37:32 2026
InstallationDate: Installed on 2025-07-01 (344 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64
(20250215)
MachineType: Hewlett-Packard HP Z440 Workstation
ProcEnviron:
- LANG=en_US.UTF-8
- PATH=(custom, no user)
- SHELL=/bin/bash
- TERM=xterm-256color
- XDG_RUNTIME_DIR=<set>
+ LANG=en_US.UTF-8
+ PATH=(custom, no user)
+ SHELL=/bin/bash
+ TERM=xterm-256color
+ XDG_RUNTIME_DIR=<set>
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-35-generic
root=UUID=dff0a4d6-2ae4-4be3-8e78-2babaabf9552 ro quiet splash vt.handoff=7
RelatedPackageVersions:
- linux-restricted-modules-6.17.0-35-generic N/A
- linux-backports-modules-6.17.0-35-generic N/A
- linux-firmware 20240318.git3b128b60-0ubuntu2.27
+ linux-restricted-modules-6.17.0-35-generic N/A
+ linux-backports-modules-6.17.0-35-generic N/A
+ linux-firmware 20240318.git3b128b60-0ubuntu2.27
RfKill:
-
+
SourcePackage: linux-hwe-6.17
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2015
dmi.bios.release: 1.62
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M60 v01.62
dmi.board.name: 212B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: unknown
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrM60v01.62:bd07/22/2015:br1.62:svnHewlett-Packard:pnHPZ440Workstation:pvr:rvnHewlett-Packard:rn212B:rvrunknown:cvnHewlett-Packard:ct6:cvr:skuF5W13AV:
dmi.product.family: 103C_53335X G=D
dmi.product.name: HP Z440 Workstation
dmi.product.sku: F5W13AV
dmi.sys.vendor: Hewlett-Packard
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2156334
Title:
nouveau: hard freeze on GF119 [NVS 310] when launching GPU-accelerated
browser, regression in 6.17.0-35-generic (good: 6.17.0-29)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.17/+bug/2156334/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
