[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4be6759d-091f-428c-a514-fec465cf053e@roeck-us.net>
Date: Thu, 8 Jan 2026 08:18:49 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: 王志 <23009200614@....xidian.edu.cn>
Cc: 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 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.
Guenter
Powered by blists - more mailing lists