Bug 219507 - nouveau: GeForce GT 710: irq 166 handler nvkm_intr+0x0/0x1b3 [nouveau] enabled interrupts
Summary: nouveau: GeForce GT 710: irq 166 handler nvkm_intr+0x0/0x1b3 [nouveau] enable...
Status: RESOLVED ANSWERED
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: Intel Linux
: P3 high
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-11-18 10:53 UTC by Paul Osmialowski
Modified: 2024-11-18 23:52 UTC (History)
0 users

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Paul Osmialowski 2024-11-18 10:53:26 UTC
Maybe it's not immediately bad (no observable problems yet), but any warnings in interrupts are always bad and make the system not trustworthy.

After inserting popular MSI graphics card (GeForce GT 710 based) newly purchased on Amazon, I'm seeing this in dmesg:

[    9.451569] Loading firmware: regulatory.db
[    9.452199] Loading firmware: regulatory.db.p7s
[   10.616519] ------------[ cut here ]------------
[   10.616522] irq 166 handler nvkm_intr+0x0/0x1b3 [nouveau] enabled interrupts
[   10.616581] WARNING: CPU: 7 PID: 0 at kernel/irq/handle.c:161 __handle_irq_event_percpu+0xe6/0x13a
[   10.616586] Modules linked in: cfg80211 8021q uvcvideo uvc videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev snd_usb_audio snd_usbmidi_lib snd_rawmidi pl2303 cp210x snd_seq_device xpad mc input_leds usbserial ff_memless joydev snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio nouveau snd_hda_intel snd_intel_dspcfg x86_pkg_temp_thermal led_class snd_hda_codec drm_exec gpu_sched snd_hda_core drm_ttm_helper kvm_intel ttm snd_hwdep snd_pcm i2c_algo_bit kvm irqbypass drm_display_helper i2c_i801 snd_timer pcspkr drm_kms_helper snd i2c_smbus fan video button vboxnetadp(O) vboxnetflt(O) vboxdrv(O) coretemp drm i2c_core backlight fuse dm_mod nfnetlink efivarfs ip_tables x_tables usbhid xhci_pci xhci_hcd ahci libahci usbcore libata usb_common
[   10.616615] CPU: 7 PID: 0 Comm: swapper/7 Tainted: G           O       6.6.58-gentoo-r1-x86_64 #1
[   10.616617] Hardware name: HP HP Pavilion Desktop TP01-3xxx/89B5, BIOS F.24 01/04/2024
[   10.616617] RIP: 0010:__handle_irq_event_percpu+0xe6/0x13a
[   10.616619] Code: 00 9c 58 0f ba e0 09 73 24 80 3d 2f 37 ad 01 00 75 1a 48 8b 13 89 ee 48 c7 c7 7d a4 24 ad c6 05 1a 37 ad 01 01 e8 a0 e5 f9 ff <0f> 0b fa 41 83 fd 02 75 2f 48 83 7b 20 00 75 1d f0 48 0f ba 6b 40
[   10.616620] RSP: 0018:ffffbd05004b8f48 EFLAGS: 00010282
[   10.616621] RAX: 0000000000000000 RBX: ffff97fa40c6db00 RCX: 0000000000000027
[   10.616622] RDX: 0000000000000000 RSI: ffffffffad25313f RDI: 00000000ffffffff
[   10.616623] RBP: 00000000000000a6 R08: 0000000000000000 R09: 0000000000000000
[   10.616624] R10: 0000000000000041 R11: 0000000000000000 R12: ffff97fa4799ca00
[   10.616624] R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000000
[   10.616625] FS:  0000000000000000(0000) GS:ffff98019f7c0000(0000) knlGS:0000000000000000
[   10.616626] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   10.616626] CR2: 00007f9bc80e1488 CR3: 00000002a5a42000 CR4: 0000000000750ee0
[   10.616627] PKRU: 55555554
[   10.616628] Call Trace:
[   10.616629]  <IRQ>
[   10.616631]  ? __warn+0x99/0x11a
[   10.616634]  ? report_bug+0xdb/0x155
[   10.616636]  ? __handle_irq_event_percpu+0xe6/0x13a
[   10.616638]  ? handle_bug+0x3c/0x63
[   10.616639]  ? exc_invalid_op+0x13/0x60
[   10.616640]  ? asm_exc_invalid_op+0x16/0x20
[   10.616644]  ? __handle_irq_event_percpu+0xe6/0x13a
[   10.616645]  ? __handle_irq_event_percpu+0xe6/0x13a
[   10.616647]  handle_irq_event_percpu+0xf/0x32
[   10.616648]  handle_irq_event+0x34/0x53
[   10.616650]  handle_edge_irq+0xb0/0xcf
[   10.616652]  __common_interrupt+0x40/0xac
[   10.616655]  common_interrupt+0xa5/0xd0
[   10.616656]  </IRQ>
[   10.616657]  <TASK>
[   10.616657]  asm_common_interrupt+0x22/0x40
[   10.616659] RIP: 0010:finish_task_switch.isra.0+0x148/0x21a
[   10.616662] Code: e6 13 00 41 80 a6 0c 04 00 00 fb 31 c9 4c 89 e7 89 4b 34 e8 5c d3 ff ff 4c 89 e7 e8 bc 03 96 00 fb 65 48 8b 04 25 80 b6 02 00 <66> 90 4d 85 ed 75 2b eb 7a 4c 8b a0 c0 02 00 00 4d 85 e4 74 ed 65
[   10.616663] RSP: 0018:ffffbd05001bfe78 EFLAGS: 00000282
[   10.616664] RAX: ffff97fa40848000 RBX: ffff97fa42a63e00 RCX: 0000000000000000
[   10.616665] RDX: 0000000000000002 RSI: ffffffffad25313f RDI: 00000000ffffffff
[   10.616665] RBP: ffffbd05001bfea8 R08: 0000000000000000 R09: 000073746e657665
[   10.616666] R10: 8080808080808080 R11: fefefefefefefeff R12: ffff98019f7ebec0
[   10.616666] R13: 0000000000000000 R14: ffff97fa40848000 R15: ffff97fa40848580
[   10.616668]  ? finish_task_switch.isra.0+0x13e/0x21a
[   10.616670]  __schedule+0x5e8/0x622
[   10.616672]  schedule_idle+0x27/0x34
[   10.616673]  cpu_startup_entry+0x2a/0x2c
[   10.616676]  start_secondary+0xf0/0xf0
[   10.616677]  secondary_startup_64_no_verify+0x166/0x16b
[   10.616679]  </TASK>
[   10.616680] ---[ end trace 0000000000000000 ]---
[   11.088891] tun: Universal TUN/TAP device driver, 1.6

It's Gentoo Linux with Plasma and SDDM. I've tried two distribution (genkernel) kernels: linux-6.6.52-gentoo and linux-6.6.58-gentoo-r1, both with the same warning in dmesg.
Comment 1 Paul Osmialowski 2024-11-18 11:43:18 UTC
I've just made an accidental discovery: this does not happen when I'm using HDMI output only. And that's a huge degradation, as I'm so got used to work with two-monitor setup like this:

$ xrandr
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
DVI-D-1 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 521mm x 293mm
   1920x1080     60.00*+
   1680x1050     59.88  
   1280x1024     75.02    60.02  
   1440x900      59.90  
   1280x960      60.00  
   1280x800      59.91  
   1152x864      75.00  
   1280x720      60.00  
   1024x768      75.03    70.07    60.00  
   832x624       74.55  
   800x600       72.19    75.00    60.32    56.25  
   640x480       75.00    66.67    59.94  
   720x400       70.08  
HDMI-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
   1920x1080     60.00*+  74.97    50.00    59.94  
   1920x1080i    60.00    50.00    59.94  
   1680x1050     59.88  
   1600x900      60.00  
   1280x1024     75.02    60.02  
   1280x800      59.91  
   1152x864      75.00  
   1280x720      60.00    50.00    59.94  
   1024x768      75.03    60.00  
   832x624       74.55  
   800x600       75.00    60.32  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       75.00    60.00    59.94  
   720x400       70.08  
VGA-1 disconnected (normal left inverted right x axis y axis)
Comment 2 Artem S. Tashkinov 2024-11-18 13:37:37 UTC
Please check 6.12 and if it's still affected repost here:

https://gitlab.freedesktop.org/drm/nouveau/-/issues/
Comment 3 Paul Osmialowski 2024-11-18 16:45:17 UTC
Ah yes yes, I've unmasked 6.12.0-gentoo and it happens there too.
Comment 4 Paul Osmialowski 2024-11-18 16:55:22 UTC
As suggested, I've opened freedesktop issue: https://gitlab.freedesktop.org/drm/nouveau/-/issues/394
Comment 5 Paul Osmialowski 2024-11-18 23:52:49 UTC
I came across this page: https://bugs.mageia.org/show_bug.cgi?id=31695 and tried the workaround presented on it, I've created /etc/X11/xorg.conf as such:

Section "Device"
    Identifier "device1"
    Driver "nouveau"
    Option "DPMS"
    Option "NoAccel" "true"
EndSection


And the problem is gone.

Of course, this is only workaround, not a solution.

Note You need to log in before you can comment on or make changes to this bug.