From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 209275] Graphics freeze after WARNING: CPU: 2 PID: 156207 at fs/ext4/inode.c:3599 ext4_set_page_dirty+0x3e/0x50
Date: Thu, 24 Sep 2020 00:18:10 +0000 [thread overview]
Message-ID: <bug-209275-13602-tAeXlteGn2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209275-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209275
--- Comment #5 from Monthero Ronald (rhmcruiser@gmail.com) ---
(In reply to Dennis Wagelaar from comment #3)
> The core dumps for gnome-shell stop after disabling shell extensions. These
> core dumps can be reliably triggered for both gnome-shell with extensions
> and firefox by putting the system into S3 sleep and waking it back up
> (something I do multiple times per day).
>
> I upgraded to kernel 5.8.9-101.fc31.x86_64 this morning. I'll report back
> whether this issue persists or not.
Hi Dennis,
Yes its quite indicative that the gnome-shell hang (graphics and input) and
repeated core dumps of gnome-shell were triggering this behavior.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-09-24 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 7:24 [Bug 209275] New: Graphics freeze after WARNING: CPU: 2 PID: 156207 at fs/ext4/inode.c:3599 ext4_set_page_dirty+0x3e/0x50 bugzilla-daemon
2020-09-15 8:15 ` [Bug 209275] " bugzilla-daemon
2020-09-17 14:42 ` bugzilla-daemon
2020-09-18 8:50 ` bugzilla-daemon
2020-09-23 19:00 ` bugzilla-daemon
2020-09-24 0:18 ` bugzilla-daemon [this message]
2020-09-24 0:22 ` 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-209275-13602-tAeXlteGn2@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.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.