linux-kernel - Re: [clockevents] WARNING: CPU: 0 PID: 0 at kernel/time/tick-oneshot.c:32 tick_stop

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKohpomtHuXP0Q9QnWvJj1d2O=AewMR+nVNE3N_KFJkMpcCHYA@mail.gmail.com>
Date:	Mon, 23 Jun 2014 14:02:25 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Jet Chen <jet.chen@...el.com>
Cc:	Fengguang Wu <fengguang.wu@...el.com>, LKP <lkp@...org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [clockevents] WARNING: CPU: 0 PID: 0 at kernel/time/tick-oneshot.c:32
 tick_stop_event()

On 23 June 2014 13:50, Jet Chen <jet.chen@...el.com> wrote:
> Hi Viresh,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> git://git.linaro.org/people/vireshk/linux tick/ONESHOT-STOPPED

Hi Jet/Fengguang,

Why did your scripts Cc'd LKML for this report? It never used to
happen for my trees Atleast.

These patches haven't been posted to LKML yet and sending
reports there for these wouldn't be good for their fate :)

Anyway, will look at what broke. Thanks.

--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/