Messages in this thread | | | From | "Rafael J. Wysocki" <> | Date | Fri, 5 Jul 2019 11:59:47 +0200 | Subject | Re: linux-next boot error: WARNING in corrupted |
| |
On Fri, Jul 5, 2019 at 11:37 AM Dmitry Vyukov <dvyukov@google.com> wrote: > > On Fri, Jul 5, 2019 at 11:23 AM Rafael J. Wysocki <rjw@rjwysocki.net> wrote: > > > > On Thursday, July 4, 2019 7:27:04 PM CEST syzbot wrote: > > > Hello, > > > > > > syzbot found the following crash on: > > > > > > HEAD commit: 16c474c9 Add linux-next specific files for 20190704 > > > git tree: linux-next > > > console output: https://syzkaller.appspot.com/x/log.txt?x=17f8b463a00000 > > > kernel config: https://syzkaller.appspot.com/x/.config?x=983f02aae1ef31b6 > > > dashboard link: https://syzkaller.appspot.com/bug?extid=de771ae9390dffed7266 > > > compiler: gcc (GCC) 9.0.0 20181231 (experimental) > > > > > > Unfortunately, I don't have any reproducer for this crash yet. > > > > > > IMPORTANT: if you fix the bug, please add the following tag to the commit: > > > Reported-by: syzbot+de771ae9390dffed7266@syzkaller.appspotmail.com > > > > ... > > > ------------[ cut here ]------------ > > > __dev_pm_qos_remove_request() called for unknown object > > > WARNING: CPU: 1 PID: 1 at drivers/base/power/qos.c:486 > > > __dev_pm_qos_remove_request+0x3d3/0x4d0 drivers/base/power/qos.c:486 > > > > Viresh, any chance to look at this? > > > > I'm a bit concerned about the freq QoS series at this point, may defer pushing it. > > FWIW here is full WARNING since I am hitting it locally too:
So can you try to revert commits between
0b07ee944701 PM / QOS: Pass request type to dev_pm_qos_{add|remove}_notifier()
and
95c7e46c0f80 cpufreq: Add QoS requests for userspace constraints
inclusive from linux-next (they should revert cleanly) and see if that makes the issue go away?
| |