linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Tomasz Nowicki <tn@semihalf.com>,
	Christoffer Dall <christoffer.dall@linaro.org>,
	Sasha Levin <alexander.levin@verizon.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes.berg@intel.com>
Subject: Re: [linux-stable] 4fc2942b6e kernel BUG at kernel/time/hrtimer.c:109!
Date: Fri, 17 Feb 2017 20:49:33 +0800	[thread overview]
Message-ID: <20170217124933.bfvyhc4tkzkbwhz5@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <0f58a1d0-a2e6-9430-7883-68e986ccb4c0@arm.com>

On Fri, Feb 17, 2017 at 10:09:06AM +0000, Marc Zyngier wrote:
>On 17/02/17 09:28, Thomas Gleixner wrote:
>> On Fri, 17 Feb 2017, kernel test robot wrote:
>>
>>> Hi Marc,
>>>
>>> We find this oops in linux-4.4.y. The gcc-6 compiled mainline kernel is fine.
>
>The last bit is worrying, as mainline has the exact same bug. Has it
>been tested the same way?

Nope, mainline is not tested the same way because gcc-4.6 cannot build
a mainline kernel due to gcc-plugin related build errors.

Thanks,
Fengguang

      parent reply	other threads:[~2017-02-17 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17  5:26 [linux-stable] 4fc2942b6e kernel BUG at kernel/time/hrtimer.c:109! kernel test robot
2017-02-17  9:28 ` Thomas Gleixner
2017-02-17 10:09   ` Marc Zyngier
2017-02-17 10:16     ` Thomas Gleixner
2017-02-17 10:31       ` Marc Zyngier
2017-02-17 12:49     ` Fengguang Wu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170217124933.bfvyhc4tkzkbwhz5@wfg-t540p.sh.intel.com \
    --to=fengguang.wu@intel.com \
    --cc=alexander.levin@verizon.com \
    --cc=christoffer.dall@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes.berg@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=tglx@linutronix.de \
    --cc=tn@semihalf.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).