On Mon, Feb 20, 2017 at 11:03:52AM +0800, Fengguang Wu wrote:
> We actually already test LKML patch in that way (Xiaolong maintains
> this feature). Nevertheless if developers specify "base-commit:" it
> could help eliminate the guessing works by the dumb robot. We'll
> appreciate if the "base-comm
Hi Borislav,
On Sun, Feb 19, 2017 at 02:50:19PM +0100, Borislav Petkov wrote:
On Sun, Feb 19, 2017 at 09:06:51AM +0800, Fengguang Wu wrote:
Yes if we add it as a line below the branch URL, it could be a time saver.
Right.
Since it's hard to teach ALL people about the rule, it'd be best if w
On Sun, Feb 19, 2017 at 09:06:51AM +0800, Fengguang Wu wrote:
> Yes if we add it as a line below the branch URL, it could be a time saver.
Right.
> Since it's hard to teach ALL people about the rule, it'd be best if we
> can work w/o any rules -- unless you want to be accurate&helpful or to
> cus
On Sun, Feb 19, 2017 at 01:10:47AM +0100, Borislav Petkov wrote:
Hey Fengguang,
On Sun, Feb 19, 2017 at 07:29:50AM +0800, Fengguang Wu wrote:
Good point! I noticed it too while sending out the report. It'll be
showed as this in future:
https://github.com/0day-ci/linux/commits/Borislav-
Hey Fengguang,
On Sun, Feb 19, 2017 at 07:29:50AM +0800, Fengguang Wu wrote:
> Good point! I noticed it too while sending out the report. It'll be
> showed as this in future:
>
>
> https://github.com/0day-ci/linux/commits/Borislav-Petkov/x86-Optimize-clear_page/20170210-053052
How about
Hi Borislav,
On Sat, Feb 18, 2017 at 03:48:00PM +0100, Borislav Petkov wrote:
Guys,
please fix the 0day bot reporting. See below for more info.
On Sat, Feb 18, 2017 at 01:01:53PM +0800, Fengguang Wu wrote:
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
Guys,
please fix the 0day bot reporting. See below for more info.
On Sat, Feb 18, 2017 at 01:01:53PM +0800, Fengguang Wu wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://github.com/0day-ci/linux
> Borislav-Petkov/x86-Optimize-clear_p
anges on commit
> >
> > 445d95d7c384741d133251a9adac935866591c92 ("sched: Remove
> > update_rq_runnable_avg")
> >
> > [ 67.303839] BUG: unable to handle kernel NULL pointer dereference at
> > 0040
> > [ 67.304014] IP: [] print_cfs_rq+0x4a3/0xa96
>
> Well that one&
On Sat, 11 Oct 2014 13:15:30 +0800
Fengguang Wu wrote:
> FYI, we noticed the below changes on commit
>
> 445d95d7c384741d133251a9adac935866591c92 ("sched: Remove
> update_rq_runnable_avg")
>
> [ 67.303839] BUG: unable to handle kernel NULL pointer derefe
| 0 | 5 |
+--+++
repeat count: 267
2014-10-10 18:20:23 ./case-anon-wx-rand-mt
2014-10-10 18:20:23 ./usemem --runtime 300 -t 4 --prealloc --random 514360832
[ 67.303839] BUG: unable to handle kernel NU
on Sat, 15 Jun 2013 11:08:47 +0300, Ming Lei
wrote:
On Sat, Jun 15, 2013 at 2:30 PM, Guenter Roeck
wrote:
On Sat, Jun 15, 2013 at 10:32:14AM +0800, Ming Lei wrote:
On Sat, Jun 15, 2013 at 1:07 AM, nirinA raseliarison
wrote:
> patch applied and no longer have the bug message when i
> reb
On Sat, Jun 15, 2013 at 2:30 PM, Guenter Roeck wrote:
> On Sat, Jun 15, 2013 at 10:32:14AM +0800, Ming Lei wrote:
>> On Sat, Jun 15, 2013 at 1:07 AM, nirinA raseliarison
>> wrote:
>>
>> > patch applied and no longer have the bug message when i
>> > reboot and wake up the ethernet controller.
>>
>
On Sat, Jun 15, 2013 at 10:32:14AM +0800, Ming Lei wrote:
> On Sat, Jun 15, 2013 at 1:07 AM, nirinA raseliarison
> wrote:
>
> > patch applied and no longer have the bug message when i
> > reboot and wake up the ethernet controller.
>
> I am wondering if Guenter's patch can fix the race really, b
On Sat, Jun 15, 2013 at 1:07 AM, nirinA raseliarison
wrote:
> patch applied and no longer have the bug message when i
> reboot and wake up the ethernet controller.
I am wondering if Guenter's patch can fix the race really, but I'd like to
see Guenter's explanation on his patch.
The race should
0 EAT 2013
x86_64
Intel(R) Celeron(R) CPU G1610 @ 2.60GHz GenuineIntel GNU/Linux
thanks,
-8<--8<---
[ 57.877560] BUG: unable to handle kernel NULL pointer dereference at
0040
[ 57
ll considers me to be a spammer and doesn't let me send any
e-mail to you ]
Guenter
------
From 9feae0b1b33721573c41fbf2323db2a12c34c725 Mon Sep 17 00:00:00 2001
From: Guenter Roeck
Date: Fri, 14 Jun 2013 08:39:06 -0700
Subject: [PATCH] firmware: Fix race condition in firmware
.1 (GCC) ) #1
>> SMP Fri Jun 14 09:14:50 EAT 2013
>>
>> uname -a
>> Linux supernova 3.9.6.20130614 #1 SMP Fri Jun 14 09:14:50 EAT 2013 x86_64
>> Intel(R) Celeron(R) CPU G1610 @ 2.60GHz GenuineIntel GNU/Linux
>>
>> thanks,
>> -
.882888] RSP
> > [ 57.884019] CR2: 00000040
> > [ 57.885166] ---[ end trace 6705f6d4ce6b6a12 ]---
> >
Please try the following patch.
[ Bjorn, sorry I dropped you from the recipient list, but unfortunately
Google still considers me to be a spammer and doesn't l
13 x86_64
> Intel(R) Celeron(R) CPU G1610 @ 2.60GHz GenuineIntel GNU/Linux
>
> thanks,
> -8<------------------8<---------------
>
> [ 57.877560] BUG: unable to handle kernel NULL pointer dereference at
> 0040
>
e to handle kernel NULL pointer dereference at
0040
[ 57.877603] IP: [] fw_load_abort.isra.5+0x4/0x20
[ 57.877634] PGD 21330a067 PUD 211a3a067 PMD 0
[ 57.877660] Oops: 0002 [#1] SMP
[ 57.877681] Modules linked in: fuse coretemp kvm_intel kvm evdev r8169
microcode mii
[ 57.87
add dgrp to the build
>
> Kconfig and Makefile changes to add dgrp to the build system.
>
> Signed-off-by: Bill Pemberton
> Signed-off-by: Greg Kroah-Hartman
>
> [7.904899] i2c-core: driver [isl29018] registered
> [7.906424] i2c-core: driver [tsl2583] registered
21 matches
Mail list logo
