linux-kernel - RE: ILK regression: hangs on reboot to Watchdog line, bisected

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B54378AE4@hasmsx108.ger.corp.intel.com>
Date:   Mon, 9 Jan 2017 20:15:27 +0000
From:   "Winkler, Tomas" <tomas.winkler@...el.com>
To:     "Sarvela, Tomi P" <tomi.p.sarvela@...el.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:     "intel-gfx-ci@...ists.intel.com" <intel-gfx-ci@...ists.intel.com>
Subject: RE: ILK regression: hangs on reboot to Watchdog line, bisected



> -----Original Message-----
> From: Sarvela, Tomi P
> Sent: Monday, January 09, 2017 20:11
> To: Winkler, Tomas <tomas.winkler@...el.com>; linux-kernel@...r.kernel.org
> Cc: intel-gfx-ci@...ists.intel.com
> Subject: ILK regression: hangs on reboot to Watchdog line, bisected
> 
> Hello there,
> 
> Our Iron Lake testhosts stopped rebooting at Christmas time. When
> commanding reboot, the last line showing is
> [   21.360606] watchdog: watchdog0: watchdog did not stop!
> (usually after that comes reboot: Restarting system)
> 
> This affects the following hardware:
> HP Elite 8100 Small Form Factor (ILK 650) HP Elitebook 8440p (ILK m540) IBM
> ThinkCentre A85 (ILK 650)
> 
> Older "Cantiga" hardware isn't affected and reboots as it should, as does
> Pineview and Sandy Bridge.
> 
> Bisecting shows that the first bad commit is
> ----
> commit 7279b238badec09efd0545293e64c21feee97f73
> Author: Alexander Usyskin <alexander.usyskin@...el.com>
> Date:   Thu Nov 10 18:38:57 2016 +0200
> 
>     mei: send OS type to the FW
> ----
> 
> If there's something I can do to track this bug down, the hosts are usually
> available for testing.

A fix is here https://lkml.org/lkml/2017/1/9/414
Bugzilla entry https://bugzilla.kernel.org/show_bug.cgi?id=192051
Thanks
Tomas