Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 878829 - sys-kernel/gentoo-kernel-bin-6.0.6: does not shutdown
Summary: sys-kernel/gentoo-kernel-bin-6.0.6: does not shutdown
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Distribution Kernel Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-30 14:44 UTC by Vasco Gervasi
Modified: 2022-11-04 18:44 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vasco Gervasi 2022-10-30 14:44:59 UTC 
Hi,
I have just updated gentoo-kernel-bin to 6.0.6 and I am not able to shutdown my laptop anymore.
If I type `sudo poweroff` my laptop gets stuck on systemd logs.
I have noticed that in `dmesg` I see:

```
[    4.831050] RIP: 0010:nvif_object_mthd+0x139/0x1f0 [nouveau]
[    4.831074] Code: 48 8d 7c 24 20 66 89 04 24 c6 44 24 18 00 e8 8e ca d1 da 41 8d 55 20 49 8b 46 08 83 fa 17 76 6e 49 39 c6 74 38 4c 89 74 24 10 <48> 8b 78 20 c6 44 24 06 ff 48 8b 40 38 31 c9 48 89 e6 48 8b 40 28
[    4.831075] RSP: 0018:ffffaf05c07df650 EFLAGS: 00010282
[    4.831076] RAX: 0000000000000000 RBX: ffff8bca44abc000 RCX: 0000000000000000
[    4.831077] RDX: 0000000000000028 RSI: ffffaf05c07df718 RDI: ffffaf05c07df678
[    4.831078] RBP: ffff8bca44abc4f8 R08: 0000000000000000 R09: 0000000000000008
[    4.831079] R10: ffff8bca4a012de0 R11: ffffaf05c0f41000 R12: ffffaf05c07df710
[    4.831079] R13: 0000000000000008 R14: ffff8bca44abc4f8 R15: 0000000000000000
[    4.831080] FS:  00007f7bd3f1f800(0000) GS:ffff8bcdae680000(0000) knlGS:0000000000000000
[    4.831081] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    4.831082] CR2: 0000000000000020 CR3: 0000000100c94005 CR4: 00000000001706e0
[    4.831083] Call Trace:
[    4.831085]  <TASK>
[    4.831086]  ? nvkm_vmm_new_+0x1f5/0x3c0 [nouveau]
[    4.831119]  ? nv04_vmm_new_+0x19/0x40 [nouveau]
[    4.831149]  nvif_conn_hpd_status+0x32/0xf0 [nouveau]
[    4.831171]  nouveau_dp_detect+0x2de/0x400 [nouveau]
[    4.831203]  find_encoder+0x146/0x810 [nouveau]
[    4.831235]  ? nvkm_ioctl+0xd2/0x180 [nouveau]
[    4.831259]  drm_helper_probe_detect+0x7e/0x250 [drm_kms_helper]
[    4.831263]  drm_helper_probe_single_connector_modes+0x44a/0x520 [drm_kms_helper]
[    4.831267]  drm_client_modeset_probe+0x200/0x13e0
[    4.831271]  ? __pm_runtime_suspend+0x6f/0x100
[    4.831273]  ? nouveau_drm_ioctl+0x813/0x17f0 [nouveau]
[    4.831306]  ? x86_pmu_hw_config+0x1c0/0x220
[    4.831309]  drm_fb_helper_check_var+0x3b6/0x8c0 [drm_kms_helper]
[    4.831313]  ? drm_client_init+0x11a/0x170
[    4.831315]  nouveau_fbcon_init+0x14a/0x1c0 [nouveau]
[    4.831345]  nouveau_drm_ioctl+0x1082/0x17f0 [nouveau]
[    4.831378]  ? pci_bus_read_config_word+0x36/0x60
[    4.831381]  nouveau_drm_ioctl+0x172b/0x17f0 [nouveau]
[    4.831413]  ? __pm_runtime_resume+0x58/0x80
[    4.831416]  local_pci_probe+0x42/0x80
[    4.831418]  ? pci_match_device+0xdb/0x130
[    4.831419]  pci_device_probe+0xb4/0x1f0
[    4.831421]  ? sysfs_do_create_link_sd+0x6d/0xe0
[    4.831425]  really_probe+0xde/0x390
[    4.831427]  ? pm_runtime_barrier+0x50/0x90
[    4.831429]  __driver_probe_device+0x78/0x180
[    4.831430]  driver_probe_device+0x1e/0x90
[    4.831432]  __driver_attach+0x9d/0x1f0
[    4.831433]  ? __device_attach_driver+0x110/0x110
[    4.831434]  ? __device_attach_driver+0x110/0x110
[    4.831436]  bus_for_each_dev+0x61/0x90
[    4.831439]  bus_add_driver+0x1a9/0x200
[    4.831441]  driver_register+0x8f/0xf0
[    4.831442]  ? 0xffffffffc1291000
[    4.831443]  do_one_initcall+0x41/0x210
[    4.831445]  ? kmem_cache_alloc_trace+0x16e/0x2e0
[    4.831448]  do_init_module+0x4c/0x1e0
[    4.831452]  __do_sys_finit_module+0x9f/0x100
[    4.831455]  do_syscall_64+0x59/0xc0
[    4.831459]  ? ksys_mmap_pgoff+0xe8/0x1f0
[    4.831462]  ? syscall_exit_to_user_mode+0x17/0x40
[    4.831464]  ? do_syscall_64+0x69/0xc0
[    4.831465]  ? syscall_exit_to_user_mode+0x17/0x40
[    4.831466]  ? do_syscall_64+0x69/0xc0
[    4.831468]  ? irqtime_account_irq+0x3c/0xb0
[    4.831470]  ? __irq_exit_rcu+0x4b/0xe0
[    4.831473]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
[    4.831475] RIP: 0033:0x7f7bd432b7e9
```

If I boot and use the version 5.19.17 it works as expected.

My laptop is a Thinkpad W541 with a NVIDIA GK106GLM [Quadro K2100M] 

Thanks


Reproducible: Always

Steps to Reproduce:
1. emerge -a =gentoo-kernel-bin-6.0.6
2.
3.
Actual Results:  
Not able to shutdown

Expected Results:  
Able to shutdown
Comment 1 Vasco Gervasi 2022-11-04 10:36:11 UTC 
The issue persists with 6.0.7.
Comment 2 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2022-11-04 10:39:12 UTC 
I don't think this is specific to sys-kernel/gentoo-kernel.  @kernel, could you take this?
Comment 3 Alice Ferrazzi Gentoo Infrastructure gentoo-dev 2022-11-04 17:16:55 UTC 
@vasco could you please send the bug upstream? please write here the bug link after, so that we can keep track of it.

https://bugs.freedesktop.org Component: Driver/nouveau
Comment 4 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2022-11-04 17:22:10 UTC 
Also, can you post full dmesg or at least some more lins before that RIP?
Comment 5 Vasco Gervasi 2022-11-04 18:37:44 UTC 
Seems that it is already been reported https://gitlab.freedesktop.org/drm/nouveau/-/issues/188