[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANp29Y5OvPgU7y6OftDtk=jhraJDJyDb3=DEBcOk9T9B99kcVg@mail.gmail.com>
Date: Fri, 9 Jan 2026 08:34:27 +0100
From: Aleksandr Nogikh <nogikh@...gle.com>
To: Guenter Roeck <linux@...ck-us.net>
Cc: 王志 <23009200614@....xidian.edu.cn>,
linux-watchdog@...r.kernel.org, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] Kernel panic in pcipcwd_get_status due to simulated overheat
On Thu, Jan 8, 2026 at 5:18 PM Guenter Roeck <linux@...ck-us.net> wrote:
>
> On Thu, Jan 08, 2026 at 10:50:35AM +0800, 王志 wrote:
> > syzbot has found the following issue on:
> >
> > HEAD commit: 6.18.0 (custom build)
> > git tree: linux-stable
> > console output: (see below)
> > kernel config: (attached)
> >
> > ---
> >
> > pcwd_pci: Card timer not enabled
> > pcwd_pci: Unexpected close, not stopping watchdog!
> > pcwd_pci: Card timer not enabled
> > pcwd_pci: Unexpected close, not stopping watchdog!
> > pcwd_pci: Card timer not enabled
> > Kernel panic - not syncing: pcwd_pci: Temperature overheat trip!
>
> You mean syzbot now complains that a driver is doing exactly what
> it is supposed to be doing ? Really ?
>
> It is not surprising that more and more people consider syzbot reports
> to be just noise.
Please note that it was not a report from syzbot itself.
>
> Guenter
>
Powered by blists - more mailing lists