From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 203317] WARNING: CPU: 2 PID: 925 at fs/ext4/inode.c:3897 ext4_set_page_dirty+0x39/0x50
Date: Mon, 09 Sep 2019 09:36:46 +0000 [thread overview]
Message-ID: <bug-203317-13602-5jA3VonOWB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203317-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203317
--- Comment #11 from howaboutsynergy (howaboutsynergy@pm.me) ---
(In reply to Jani Nikula from comment #10)
> Where?
To: intel-gfx@lists.freedesktop.org
> If you think this is about i915, and want i915 developers to look, please file bugs at [1], or send email to intel-gfx@lists.freedesktop.org where the likely first response is to ask you to file bugs at [1].
The only reason I think it's about i915 is because of:
1. "i915" in the stacktrace in Comment 1
2. it only happens on my Intel(i915) computer, not on Amd/Radeon laptop(I
simply cannot reproduce the freeze on the AMD one)
> Generally the only action the i915 developers do at bugzilla.kernel.org is to close, and ask bugs to be filed at [1]. You get the picture. ;)
> [1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
Good info, thanks! I'll file a bug there then. Sorry for the noise.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-09-09 9:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 7:58 [Bug 203317] New: WARNING: CPU: 2 PID: 925 at fs/ext4/inode.c:3897 ext4_set_page_dirty+0x39/0x50 bugzilla-daemon
2019-07-08 13:50 ` [Bug 203317] " bugzilla-daemon
2019-07-08 14:16 ` bugzilla-daemon
2019-07-20 16:53 ` bugzilla-daemon
2019-08-14 0:13 ` bugzilla-daemon
2019-08-14 16:36 ` bugzilla-daemon
2019-09-09 0:01 ` bugzilla-daemon
2019-09-09 8:09 ` bugzilla-daemon
2019-09-09 8:19 ` bugzilla-daemon
2019-09-09 8:39 ` bugzilla-daemon
2019-09-09 9:25 ` bugzilla-daemon
2019-09-09 9:36 ` bugzilla-daemon [this message]
2019-09-09 9:50 ` bugzilla-daemon
2019-09-09 10:32 ` 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-203317-13602-5jA3VonOWB@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.