From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 218617] New: Linux Kernel Bug Report: "Scheduling while atomic" Kernel Panic and System Freeze on NVIDIA RTX 2000 Ada Generation Laptop GPU
Date: Wed, 20 Mar 2024 18:44:28 +0000 [thread overview]
Message-ID: <bug-218617-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218617
Bug ID: 218617
Summary: Linux Kernel Bug Report: "Scheduling while atomic"
Kernel Panic and System Freeze on NVIDIA RTX 2000 Ada
Generation Laptop GPU
Product: Drivers
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: blocking
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: sarah.salzstein@gmail.com
Regression: No
Created attachment 306013
--> https://bugzilla.kernel.org/attachment.cgi?id=306013&action=edit
Relevant dmesg output
Dear Linux Kernel Development Team,
I am writing to report a critical issue I have been encountering with the Linux
kernel, specifically related to my NVIDIA RTX 2000 Ada Generation Laptop GPU,
installed in a Lenovo ThinkPad P1 Gen 6. The problem manifests as a "scheduling
while atomic" kernel bug, followed by a complete system freeze.
Description of the Problem:
Randomly during system operation, the kernel gives the error message
"scheduling while atomic". This error occurs seemingly at random intervals and
under varying system loads. Subsequently, at some point, the system becomes
unresponsive and necessitates a hard reboot to regain functionality.
Steps to Reproduce:
- The error occurs randomly during system operation.
- The system becomes unresponsive, leading to a complete freeze.
System Information:
- GPU: NVIDIA Corporation AD107GLM [RTX 2000 Ada Generation Laptop GPU] (rev
a1)
Linux Distribution: Gentoo Linux
- Kernel Version: 6.8.1 (Also affects kernel versions 6.7.x, 6.6.x, and 6.1.x)
Additional Information:
The issue persists across multiple kernel versions, indicating it is not
specific to a particular kernel release.
I have examined the system logs and have identified the occurrence of the
"scheduling while atomic" error as the primary issue leading to the kernel
panic and subsequent system freeze.
No specific system activity or workload triggers the error; it happens
seemingly at random.
I have ensured that the GPU drivers are up to date and have attempted to
reinstall them without resolving the issue, but no matter which NVIDIA driver
version I install, the bug consistently persists.
Attached Logs:
Attached the relevant portion of the dmesg output showing the BUG.
This issue severely affects the usability and stability of my system, and I
kindly request your assistance in resolving it promptly. If there are any
additional diagnostic steps or information required from my end, please let me
know, and I will gladly provide it.
Thank you for your attention to this matter.
Sincerely,
Sarah S.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2024-03-20 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 18:44 bugzilla-daemon [this message]
2024-03-20 20:24 ` [Bug 218617] Linux Kernel Bug Report: "Scheduling while atomic" Kernel Panic and System Freeze on NVIDIA RTX 2000 Ada Generation Laptop GPU bugzilla-daemon
2024-03-20 20:28 ` bugzilla-daemon
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-218617-2300@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.