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

Date:	Mon, 23 Jun 2014 17:39:25 +0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	Viresh Kumar <viresh.kumar@...aro.org>
Cc:	Jet Chen <jet.chen@...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()

Hi Viresh,

On Mon, Jun 23, 2014 at 02:02:25PM +0530, Viresh Kumar wrote:
> 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.

Yeah our build error reports are mostly private emails. However we do
CC LKML for runtime regressions - because there is no easy way for us
to tell whether the reported regression has reached more people.

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

Sorry if it hurts. :)

> Anyway, will look at what broke. Thanks.

Thank you!

Cheers,
Fengguang
--
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/