Arch Linux

cemi

Member

Registered: 2020-09-05

Posts: 19

Frequent nouveau Timeout: Can't Turn off dGPU Using acpi_call Script.

While looking for errors after following this guide I discovered nouveau timeouts every few minutes, sometimes seconds.

Gnome + GDM 3.36.5 (Wayland)

02:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] 
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)

 kernel: nouveau 0000:02:00.0: Enabling HDA controller
 kernel: nouveau 0000:02:00.0: timeout
 kernel: WARNING: CPU: 0 PID: 7558 at drivers/gpu/drm/nouveau/nvkm/subdev/pmu/base.c:107 nvkm_pmu_reset+0x1aa/0x1c0 [nouveau]
 kernel: RIP: 0010:nvkm_pmu_reset+0x1aa/0x1c0 [nouveau]
 kernel:  nvkm_pmu_init+0x16/0x40 [nouveau]
 kernel:  nvkm_subdev_init+0x92/0xd0 [nouveau]
 kernel:  nvkm_device_init+0x10b/0x190 [nouveau]
 kernel:  nvkm_udevice_init+0x44/0x60 [nouveau]
 kernel:  nvkm_object_init+0x3e/0x100 [nouveau]
 kernel:  nvkm_object_init+0x6f/0x100 [nouveau]
 kernel:  nvkm_object_init+0x6f/0x100 [nouveau]
 kernel:  nouveau_do_resume+0x29/0xd0 [nouveau]
 kernel:  nouveau_pmops_runtime_resume+0x77/0x160 [nouveau]

vga_switcheroo tells me it's "on demand".

$ cat /sys/kernel/debug/vgaswitcheroo/switch

0:IGD:+:Pwr:0000:00:02.0
1:DIS: :DynOff:0000:02:00.0

The script "fails" to match any entry.

Tried the acpi_call method since I don't plan on switching graphics, which bbswitch does.

Not sure if they're related, still:

gdm-password][3781]: gkr-pam: unable to locate daemon control file
pulseaudio[3638]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.

Last edited by cemi (2020-09-07 07:23:43)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,365

Re: Frequent nouveau Timeout: Can't Turn off dGPU Using acpi_call Script.

bbswitch does not switch graphics and does the right thing, use bbswitch (... and blacklist nouveau).

Last edited by V1del (2020-09-07 07:26:36)

cemi

Member

Registered: 2020-09-05

Posts: 19

Re: Frequent nouveau Timeout: Can't Turn off dGPU Using acpi_call Script.

bbswitch does not switch graphics and does the right thing, use bbswitch (... and blacklist nouveau).

I thought bbswitch was for switching between cards, instead it's for switching off dGPU's.

Hey you're a mod, is there any additional information I should include (regarding nouveau) to better my odds?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,365

Re: Frequent nouveau Timeout: Can't Turn off dGPU Using acpi_call Script.

bbswitch was primarily developed for bumblebee to have a way to properly disable and enable the dgpu on an as needed basis (and afaik it was developed precisely because the acpi_call method by itself was unreliable). You can configure it to automatically poweroff the dgpu without doing much else, see: https://wiki.archlinux.org/index.php/Bu … g_bbswitch

As for nouveau, it is generally not the most stable driver, if you really just want to disable the nvidia card you can use bbswitch (for bbswitch or acpi_call to do that the card shouldn't yet be occupied by a driver, which is why you need to blacklist nouveau regardless)

cemi

Member

Registered: 2020-09-05

Posts: 19

Re: Frequent nouveau Timeout: Can't Turn off dGPU Using acpi_call Script.

bbswitch was primarily developed for bumblebee to have a way to properly disable and enable the dgpu on an as needed basis (and afaik it was developed precisely because the acpi_call method by itself was unreliable). You can configure it to automatically poweroff the dgpu without doing much else, see: https://wiki.archlinux.org/index.php/Bu … g_bbswitch

As for nouveau, it is generally not the most stable driver, if you really just want to disable the nvidia card you can use bbswitch (for bbswitch or acpi_call to do that the card shouldn't yet be occupied by a driver, which is why you need to blacklist nouveau regardless)

Sorry about my late response, I accidentally trashed my sessions and had a little difficulty recovering.

Why does the wiki instruct users to load bbswitch and its options by introducing "/etc/modprobe.d/bbswitch.conf", instead of adding bbswitch to "/etc/mkinitcpio.conf"  and passing options as kernel parameters? Are there any upsides or downsides to either method?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,365

Re: Frequent nouveau Timeout: Can't Turn off dGPU Using acpi_call Script.

That basically comes down to personal preferences at the point were this becomes relevant. Having it in mkinitcpio ensures that this happens as soon as possible, having it in modprobe leads to the same effect just logically later (after the kernel has booted and mounted and read configs from your root filesystem) For the purposes of relevance in this case it's unlikely to matter, you might be more space contraint on the place where you have put the initramfs (e.g. if you use a small ESP on an UEFI system) but the bbswitch module is so small this is unlikely to factor in.