From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 219507] nouveau: GeForce GT 710: irq 166 handler nvkm_intr+0x0/0x1b3 [nouveau] enabled interrupts
Date: Mon, 10 Mar 2025 19:42:43 +0000 [thread overview]
Message-ID: <bug-219507-2300-0JCg1mF8Vn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219507-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219507
Joe Breuer (linux-kernel@jmbreuer.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |linux-kernel@jmbreuer.net
--- Comment #6 from Joe Breuer (linux-kernel@jmbreuer.net) ---
I get a very similar thing with kernel 6.13.5, and an (OK, it's ancient) nVidia
GeForce 8600 GT (G84):
irq 25 handler nvkm_intr+0x0/0x210 enabled interrupts
WARNING: CPU: 1 PID: 1355 at kernel/irq/handle.c:161 __handle_irq_event_percpu
(kernel/irq/handle.c:161 (discriminator 1))
...
I also have some other diagnostics from nouveau in dmesg - 5 copies of this,
about 12 seconds before the kernel WARNING:
nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter-qt[1199]] get
0000216004 put 0000216088 ib_get 00000007 ib_put 00000008 state 800081a4 (err:
INVALID_CMD) push 00406040
I'll try the workaround suggested above; and take any findings on to the linked
freedesktop issue.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2025-03-10 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 10:53 [Bug 219507] New: nouveau: GeForce GT 710: irq 166 handler nvkm_intr+0x0/0x1b3 [nouveau] enabled interrupts bugzilla-daemon
2024-11-18 11:43 ` [Bug 219507] " bugzilla-daemon
2024-11-18 13:37 ` bugzilla-daemon
2024-11-18 16:45 ` bugzilla-daemon
2024-11-18 16:55 ` bugzilla-daemon
2024-11-18 23:52 ` bugzilla-daemon
2025-03-10 19:42 ` bugzilla-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-219507-2300-0JCg1mF8Vn@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.