Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #92312 > unrolled thread
| Started by | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| First post | 2026-05-05 22:30 +0200 |
| Last post | 2026-07-07 21:50 +0200 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#1135780: nouveau: driver caused graphical session to become unresponsive Salvatore Bonaccorso <carnil@debian.org> - 2026-05-05 22:30 +0200
Processed: Re: Bug#1135780: nouveau: driver caused graphical session to become unresponsive "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-05-05 22:30 +0200
Bug#1135780: nouveau: driver caused graphical session to become unresponsive Salvatore Bonaccorso <carnil@debian.org> - 2026-07-07 21:50 +0200
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2026-05-05 22:30 +0200 |
| Subject | Bug#1135780: nouveau: driver caused graphical session to become unresponsive |
| Message-ID | <MRuyZ-2R16-7@gated-at.bofh.it> |
Control: tags -1 + moreinfo Hi On Wed, May 06, 2026 at 06:19:23AM +1000, Anand Kumria wrote: > Package: src:linux > Version: 6.19.14-1 > Severity: normal > > Dear Maintainer, > > While in an ordinary graphical session, it suddenly became unresponsive. > > After rebooting, the following messages were in the kernel log. > > > -- Package-specific info: > ** Kernel log: boot messages should be attached > May 05 08:00:50 pushan kernel: INFO: task kworker/u32:3:305137 blocked for > more than 120 seconds. > May 05 08:00:50 pushan kernel: Not tainted 6.19.14+deb14-amd64 #1 > Debian 6.19.14-1 > May 05 08:00:50 pushan kernel: "echo 0 > > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > May 05 08:00:50 pushan kernel: task:kworker/u32:3 state:D stack:0 > pid:305137 tgid:305137 ppid:2 task_flags:0x4208060 flags:0x00080000 > May 05 08:00:50 pushan kernel: Workqueue: events_unbound > nv50_disp_atomic_commit_work [nouveau] > May 05 08:00:50 pushan kernel: Call Trace: > May 05 08:00:50 pushan kernel: <TASK> > May 05 08:00:50 pushan kernel: __schedule+0x48a/0xfc0 > May 05 08:00:50 pushan kernel: schedule+0x27/0xd0 > May 05 08:00:50 pushan kernel: schedule_timeout+0xbd/0x100 > May 05 08:00:50 pushan kernel: dma_fence_default_wait+0x1a8/0x280 > May 05 08:00:50 pushan kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10 > May 05 08:00:50 pushan kernel: dma_fence_wait_timeout+0xa2/0x150 > May 05 08:00:50 pushan kernel: > drm_atomic_helper_wait_for_fences+0x133/0x1f0 [drm_kms_helper] > May 05 08:00:50 pushan kernel: nv50_disp_atomic_commit_tail+0x88/0x790 > [nouveau] > May 05 08:00:50 pushan kernel: process_one_work+0x192/0x350 > May 05 08:00:50 pushan kernel: worker_thread+0x196/0x300 > May 05 08:00:50 pushan kernel: ? __pfx_worker_thread+0x10/0x10 > May 05 08:00:50 pushan kernel: kthread+0xfc/0x240 > May 05 08:00:50 pushan kernel: ? __pfx_kthread+0x10/0x10 > May 05 08:00:50 pushan kernel: ? __pfx_kthread+0x10/0x10 > May 05 08:00:50 pushan kernel: ret_from_fork+0x24d/0x290 > May 05 08:00:50 pushan kernel: ? __pfx_kthread+0x10/0x10 > May 05 08:00:50 pushan kernel: ret_from_fork_asm+0x1a/0x30 > May 05 08:00:50 pushan kernel: </TASK> > May 05 08:00:50 pushan kernel: INFO: task kworker/u33:0:306101 blocked for > more than 120 seconds. > May 05 08:00:50 pushan kernel: Not tainted 6.19.14+deb14-amd64 #1 > Debian 6.19.14-1 > May 05 08:00:50 pushan kernel: "echo 0 > > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > May 05 08:00:50 pushan kernel: task:kworker/u33:0 state:D stack:0 > pid:306101 tgid:306101 ppid:2 task_flags:0x4208060 flags:0x00080000 > May 05 08:00:50 pushan kernel: Workqueue: ttm ttm_bo_delayed_delete [ttm] > May 05 08:00:50 pushan kernel: Call Trace: > May 05 08:00:50 pushan kernel: <TASK> > May 05 08:00:50 pushan kernel: __schedule+0x48a/0xfc0 > May 05 08:00:50 pushan kernel: schedule+0x27/0xd0 > May 05 08:00:50 pushan kernel: schedule_timeout+0xbd/0x100 > May 05 08:00:50 pushan kernel: dma_fence_default_wait+0x1a8/0x280 > May 05 08:00:50 pushan kernel: ? __pfx_dma_fence_default_wait_cb+0x10/0x10 > May 05 08:00:50 pushan kernel: dma_fence_wait_timeout+0xa2/0x150 > May 05 08:00:50 pushan kernel: dma_resv_wait_timeout+0xce/0x1d0 > May 05 08:00:50 pushan kernel: ttm_bo_delayed_delete+0x32/0x90 [ttm] > May 05 08:00:50 pushan kernel: process_one_work+0x192/0x350 > May 05 08:00:50 pushan kernel: worker_thread+0x196/0x300 > May 05 08:00:50 pushan kernel: ? __pfx_worker_thread+0x10/0x10 > May 05 08:00:50 pushan kernel: kthread+0xfc/0x240 > May 05 08:00:50 pushan kernel: ? __pfx_kthread+0x10/0x10 > May 05 08:00:50 pushan kernel: ? __pfx_kthread+0x10/0x10 > May 05 08:00:50 pushan kernel: ret_from_fork+0x24d/0x290 > May 05 08:00:50 pushan kernel: ? __pfx_kthread+0x10/0x10 > May 05 08:00:50 pushan kernel: ret_from_fork_asm+0x1a/0x30 > May 05 08:00:50 pushan kernel: </TASK> As 6.19.y is end of life now, can you please update to the 7.0.3-1 kernel in unstable and report back if you can reproduce the issue? Regards, Salvatore
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2026-05-05 22:30 +0200 |
| Subject | Processed: Re: Bug#1135780: nouveau: driver caused graphical session to become unresponsive |
| Message-ID | <MRuyZ-2R16-11@gated-at.bofh.it> |
| In reply to | #92312 |
Processing control commands: > tags -1 + moreinfo Bug #1135780 [src:linux] nouveau: driver caused graphical session to become unresponsive Added tag(s) moreinfo. -- 1135780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1135780 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2026-07-07 21:50 +0200 |
| Message-ID | <NejXP-3mrW-3@gated-at.bofh.it> |
| In reply to | #92312 |
Hi Anand, On Tue, Jun 30, 2026 at 01:40:14PM +1000, Anand Kumria wrote: > Hi, > > The same lock-up has occurred with a new kernel version: > > Jun 07 14:31:39 pushan kernel: Linux version 7.0.9+deb14-amd64 ( > debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc-15 (Debian 15.2.0-17)> > ... > Jun 29 14:19:47 pushan kernel: BUG: kernel NULL pointer dereference, > address: 0000000000000040 > Jun 29 14:19:48 pushan kernel: #PF: supervisor read access in kernel mode > Jun 29 14:19:48 pushan kernel: #PF: error_code(0x0000) - not-present page > Jun 29 14:19:48 pushan kernel: PGD 0 P4D 0 > Jun 29 14:19:48 pushan kernel: Oops: Oops: 0000 [#1] SMP PTI > Jun 29 14:19:48 pushan kernel: CPU: 6 UID: 1000 PID: 1532627 Comm: chrome > Not tainted 7.0.9+deb14-amd64 #1 PREEMPT(lazy) Debian 7.0.9-1 > Jun 29 14:19:48 pushan kernel: Hardware name: Acer Veriton S680G > /Veriton M680G, BIOS P01-A4 05/27/2010 > Jun 29 14:19:48 pushan kernel: RIP: 0010:nouveau_fence_sync+0x12c/0x1b0 > [nouveau] > Jun 29 14:19:48 pushan kernel: Code: 74 08 48 3d 20 dd d2 c0 75 aa e8 bf 47 > b1 c6 49 8b 76 50 48 85 f6 74 97 48 8b 85 f0 00 00 00 48 8b 96 f0 00 00 00 > 48 8b 40 40 <48> 39 42 40 0f 85 7b ff ff ff 48 39 f5 74 17 49 8b 47 30 48 8> > Jun 29 14:19:48 pushan kernel: RSP: 0018:ffffcf83a06cf540 EFLAGS: 00010286 > Jun 29 14:19:48 pushan kernel: RAX: ffff8a62909f4000 RBX: ffffcf83a06cf558 > RCX: ffff8a635f0050c0 > Jun 29 14:19:48 pushan kernel: RDX: 0000000000000000 RSI: ffff8a62d6520c00 > RDI: ffffcf83a06cf558 > Jun 29 14:19:48 pushan kernel: RBP: ffff8a6304899400 R08: 0000000000000000 > R09: 0000820000000000 > Jun 29 14:19:48 pushan kernel: R10: ffff8a62909f41c0 R11: 00007e0000000000 > R12: 0000000000000000 > Jun 29 14:19:48 pushan kernel: R13: 0000000000000000 R14: ffff8a65acbc5d20 > R15: ffff8a6280f94500 > Jun 29 14:19:48 pushan kernel: FS: 00007f92404ce700(0000) > GS:ffff8a6625efc000(0000) knlGS:0000000000000000 > Jun 29 14:19:48 pushan kernel: CS: 0010 DS: 0000 ES: 0000 CR0: > 0000000080050033 > Jun 29 14:19:48 pushan kernel: CR2: 0000000000000040 CR3: 0000000385f52000 > CR4: 00000000000026f0 > Jun 29 14:19:48 pushan kernel: Call Trace: > Jun 29 14:19:48 pushan kernel: <TASK> > Jun 29 14:19:48 pushan kernel: nouveau_bo_move+0x1de/0x8d0 [nouveau] > Jun 29 14:19:48 pushan kernel: ? ttm_pool_alloc+0x7d/0xb0 [ttm] > Jun 29 14:19:48 pushan kernel: ? ttm_tt_populate+0xa1/0x140 [ttm] > Jun 29 14:19:48 pushan kernel: ttm_bo_handle_move_mem+0xd0/0x1a0 [ttm] > Jun 29 14:19:48 pushan kernel: ttm_bo_evict+0x115/0x170 [ttm] > Jun 29 14:19:48 pushan kernel: ? __ttm_bo_lru_cursor_next+0xff/0x300 [ttm] > Jun 29 14:19:48 pushan kernel: ttm_bo_evict_cb+0x77/0xd0 [ttm] > Jun 29 14:19:48 pushan kernel: ttm_lru_walk_for_evict+0xad/0x1d0 [ttm] > Jun 29 14:19:48 pushan kernel: ttm_bo_alloc_resource+0x186/0x4c0 [ttm] > Jun 29 14:19:48 pushan kernel: ttm_bo_validate+0x9e/0x180 [ttm] > Jun 29 14:19:48 pushan kernel: ttm_bo_init_reserved+0x16d/0x1f0 [ttm] > Jun 29 14:19:48 pushan kernel: nouveau_bo_init+0x95/0x110 [nouveau] > Jun 29 14:19:48 pushan kernel: ? __pfx_nouveau_bo_del_ttm+0x10/0x10 > [nouveau] > Jun 29 14:19:48 pushan kernel: nouveau_gem_new+0x163/0x200 [nouveau] > Jun 29 14:19:48 pushan kernel: nouveau_gem_ioctl_new+0x8c/0x170 [nouveau] > Jun 29 14:19:48 pushan kernel: ? __pfx_nouveau_gem_ioctl_new+0x10/0x10 > [nouveau] > Jun 29 14:19:48 pushan kernel: drm_ioctl_kernel+0xae/0x100 [drm] > Jun 29 14:19:48 pushan kernel: drm_ioctl+0x2a8/0x550 [drm] > Jun 29 14:19:48 pushan kernel: ? __pfx_nouveau_gem_ioctl_new+0x10/0x10 > [nouveau] > Jun 29 14:19:48 pushan kernel: nouveau_drm_ioctl+0x58/0xc0 [nouveau] > Jun 29 14:19:48 pushan kernel: __x64_sys_ioctl+0x97/0xe0 > Jun 29 14:19:48 pushan kernel: do_syscall_64+0xcd/0x15f0 > Jun 29 14:19:48 pushan kernel: ? __alloc_frozen_pages_noprof+0x17e/0x340 > Jun 29 14:19:48 pushan kernel: ? mod_memcg_lruvec_state+0xe7/0x2e0 > Jun 29 14:19:48 pushan kernel: ? lruvec_stat_mod_folio+0x85/0xd0 > Jun 29 14:19:48 pushan kernel: ? __folio_mod_stat+0x2d/0x90 > Jun 29 14:19:48 pushan kernel: ? set_ptes.isra.0+0x36/0x80 > Jun 29 14:19:48 pushan kernel: ? do_anonymous_page+0x103/0x900 > Jun 29 14:19:48 pushan kernel: ? __pte_offset_map+0x1b/0x100 > Jun 29 14:19:48 pushan kernel: ? __handle_mm_fault+0xb12/0xf50 > Jun 29 14:19:48 pushan kernel: ? __free_frozen_pages+0x242/0x7c0 > Jun 29 14:19:48 pushan kernel: ? count_memcg_events+0xeb/0x220 > Jun 29 14:19:48 pushan kernel: ? handle_mm_fault+0x1d6/0x2d0 > Jun 29 14:19:48 pushan kernel: ? do_user_addr_fault+0x2b4/0x7b0 > Jun 29 14:19:48 pushan kernel: ? irqentry_exit+0x6e/0x570 > Jun 29 14:19:48 pushan kernel: ? exc_page_fault+0x82/0x1d0 > Jun 29 14:19:48 pushan kernel: ? __irq_exit_rcu+0x3d/0xe0 > Jun 29 14:19:48 pushan kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e > Jun 29 14:19:48 pushan kernel: RIP: 0033:0x7f92416d7d3b > Jun 29 14:19:48 pushan kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 > c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 > 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 0> > Jun 29 14:19:48 pushan kernel: RSP: 002b:00007ffc0acf89f0 EFLAGS: 00000246 > ORIG_RAX: 0000000000000010 > Jun 29 14:19:48 pushan kernel: RAX: ffffffffffffffda RBX: 0000379c00221320 > RCX: 00007f92416d7d3b > Jun 29 14:19:48 pushan kernel: RDX: 00007ffc0acf8aa0 RSI: 00000000c0306480 > RDI: 0000000000000013 > Jun 29 14:19:48 pushan kernel: RBP: 00007ffc0acf8aa0 R08: 00005600f4303bc8 > R09: 0000379c03e07dc0 > Jun 29 14:19:48 pushan kernel: R10: 0000379c03e07e8c R11: 0000000000000246 > R12: 00000000c0306480 > Jun 29 14:19:48 pushan kernel: R13: 0000000000000013 R14: 0000379c00088600 > R15: 0000000000001000 > Jun 29 14:19:48 pushan kernel: </TASK> > Jun 29 14:19:48 pushan kernel: Modules linked in: nft_fib_ipv6 nft_ct > nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_fib_ipv4 nft_fib nf_tables > wireguard libcurve25519 libchacha20poly1305 libchacha libpoly1305 > ip6_udp_tunnel u> > Jun 29 14:19:48 pushan kernel: drm_exec i2c_algo_bit drm_display_helper > cec rc_core drm_client_lib drm_kms_helper sd_mod hid_generic usbhid uas > usb_storage hid ahci libahci ata_generic iTCO_wdt drm libata intel_pmc_bxt > ehci_p> > Jun 29 14:19:48 pushan kernel: CR2: 0000000000000040 > Jun 29 14:19:48 pushan kernel: ---[ end trace 0000000000000000 ]--- > Jun 29 14:19:48 pushan kernel: RIP: 0010:nouveau_fence_sync+0x12c/0x1b0 > [nouveau] > Jun 29 14:19:48 pushan kernel: Code: 74 08 48 3d 20 dd d2 c0 75 aa e8 bf 47 > b1 c6 49 8b 76 50 48 85 f6 74 97 48 8b 85 f0 00 00 00 48 8b 96 f0 00 00 00 > 48 8b 40 40 <48> 39 42 40 0f 85 7b ff ff ff 48 39 f5 74 17 49 8b 47 30 48 8> > Jun 29 14:19:48 pushan kernel: RSP: 0018:ffffcf83a06cf540 EFLAGS: 00010286 > Jun 29 14:19:48 pushan kernel: RAX: ffff8a62909f4000 RBX: ffffcf83a06cf558 > RCX: ffff8a635f0050c0 > Jun 29 14:19:48 pushan kernel: RDX: 0000000000000000 RSI: ffff8a62d6520c00 > RDI: ffffcf83a06cf558 > Jun 29 14:19:48 pushan kernel: RBP: ffff8a6304899400 R08: 0000000000000000 > R09: 0000820000000000 > Jun 29 14:19:48 pushan kernel: R10: ffff8a62909f41c0 R11: 00007e0000000000 > R12: 0000000000000000 > Jun 29 14:19:48 pushan kernel: R13: 0000000000000000 R14: ffff8a65acbc5d20 > R15: ffff8a6280f94500 > Jun 29 14:19:48 pushan kernel: FS: 00007f92404ce700(0000) > GS:ffff8a6625efc000(0000) knlGS:0000000000000000 > Jun 29 14:19:48 pushan kernel: CS: 0010 DS: 0000 ES: 0000 CR0: > 0000000080050033 > Jun 29 14:19:48 pushan kernel: CR2: 0000000000000040 CR3: 0000000385f52000 > CR4: 00000000000026f0 > Jun 29 14:19:52 pushan kernel: audit: type=1400 > audit(1782706792.259:350272): apparmor="DENIED" operation="ptrace" > class="ptrace" profile="/usr/bin/papers//sanitized_helper" pid=368943 > comm="FSBroker855023" requested_mask="rea> > Jun 29 14:20:05 pushan kernel: BUG: unable to handle page fault for > address: ffffcf83a06cf7a8 > Jun 29 14:20:05 pushan kernel: #PF: supervisor read access in kernel mode > Jun 29 14:20:05 pushan kernel: #PF: error_code(0x0000) - not-present page > Jun 29 14:20:05 pushan kernel: PGD 100000067 P4D 100000067 PUD 100259067 > PMD 3d15b1067 PTE 0 It is not entirely clear we hit the same issue here, but we defintively need more information in form of a full trace. So I ask you once more again to please boot with the newest kernel in meanwhile available, which is 7.1.3-1. In case you hit the issue still, then we need a full trace. If it does not get reorded into log in time, then we might need to attach a netconsole, cf. https://docs.kernel.org/networking/netconsole.html#netconsole Regards, Salvatore
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web