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:22:54 +0000 [thread overview]
Message-ID: <bug-209275-13602-taaRqSpDGK@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 #6 from Monthero Ronald (rhmcruiser@gmail.com) ---
(In reply to Dennis Wagelaar from comment #4)
> This bug no longer occurs under kernel 5.8.9-101.fc31.x86_64 - closing.
Ah good to know issue is resolved with upgrade to newer kernel. (Probbaly the
issue was within the gnome-shell where the above stack was indicating a use
after free sort of condition in the gnome userspace code causing core dumps.
ep 15 08:23:46 styx gnome-shell[67420]: #9 55a8b19fc420 i
resource:///org/gnome/gjs/modules/overrides/Gio.js:169 (7fba6c0d3e50 @ 39)
Sep 15 08:23:46 styx gnome-shell[67420]: == Stack trace for context
0x55a8ac63e3a0 ==
Sep 15 08:23:46 styx gnome-shell[67420]: #0 55a8b19fc6d8 i
/usr/share/gnome-shell/extensions/gamemode@christian.kellner.me/extension.js:231
(7fba10824820 @ 287)
Sep 15 08:23:46 styx gnome-shell[67420]: #1 7ffe62146c90 b self-hosted:977
(7fba45130a60 @ 413)
Sep 15 08:23:46 styx gnome-shell[67420]: #2 7ffe62146d70 b
resource:///org/gnome/gjs/modules/signals.js:135 (7fba6c0c6040 @ 376)
Sep 15 08:23:46 styx journal[67420]: Object St.Icon (0x55a8ad298110), has been
already deallocated — impossible to access it. This might be caused by the
object having been destroyed from C code using something such as destroy(),
dispose(), or remove() vfuncs.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2020-09-24 0:22 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
2020-09-24 0:22 ` 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-209275-13602-taaRqSpDGK@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.