From: syzbot <syzbot+d130c4a0890561cfac5b@syzkaller.appspotmail.com>
To: Rex.Zhu@amd.com, airlied@linux.ie, alexander.deucher@amd.com,
amd-gfx@lists.freedesktop.org, b.zolnierkie@samsung.com,
christian.koenig@amd.com, daniel.vetter@ffwll.ch,
david1.zhou@amd.com, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
maarten.lankhorst@linux.intel.com, rex.zhu@amd.com,
sam@ravnborg.org, syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task hung in fb_release
Date: Mon, 23 Dec 2019 10:31:01 +0000 [thread overview]
Message-ID: <0000000000002074ef059a5c86e2@google.com> (raw)
In-Reply-To: <00000000000082b80f059a56da1f@google.com>
In-Reply-To: <00000000000082b80f059a56da1f@google.com>
syzbot has bisected this bug to:
commit e3933f26b657c341055443103bad331f4537b113
Author: Rex Zhu <Rex.Zhu@amd.com>
Date: Tue Jan 16 10:35:15 2018 +0000
drm/amd/pp: Add edit/commit/show OD clock/voltage support in sysfs
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x\x12b5a799e00000
start commit: c6017471 Merge tag 'xfs-5.5-fixes-2' of git://git.kernel.o..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x\x11b5a799e00000
console output: https://syzkaller.appspot.com/x/log.txt?x\x16b5a799e00000
kernel config: https://syzkaller.appspot.com/x/.config?x\x7f6119e2e3675a73
dashboard link: https://syzkaller.appspot.com/bug?extidÑ30c4a0890561cfac5b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x\x169b1925e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x\x12b9623ee00000
Reported-by: syzbot+d130c4a0890561cfac5b@syzkaller.appspotmail.com
Fixes: e3933f26b657 ("drm/amd/pp: Add edit/commit/show OD clock/voltage
support in sysfs")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-12-23 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 3:45 INFO: task hung in fb_release syzbot
2019-12-23 10:31 ` syzbot [this message]
2020-01-07 15:47 ` Daniel Vetter
2020-01-07 16:01 ` Dmitry Vyukov
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=0000000000002074ef059a5c86e2@google.com \
--to=syzbot+d130c4a0890561cfac5b@syzkaller.appspotmail.com \
--cc=Rex.Zhu@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=b.zolnierkie@samsung.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=david1.zhou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=sam@ravnborg.org \
--cc=syzkaller-bugs@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).