Re: [LKP] [lkp-robot] [confidence: ] 7757d607c6 [ 56.996267] BUG: Bad page map in process trinity-c2 pte:0d755065 pmd:0d55b067

2018-07-30 Thread Ye Xiaolong
Hi, On 07/27, Joerg Roedel wrote: >Hey, > >thanks for the report! It did a lot of testing and the issue is fixed >now with this patch: > > > https://lore.kernel.org/lkml/1532533683-5988-4-git-send-email-j...@8bytes.org/ > >I did 2150 runs of your reproducer with the reproducer attached to

Re: [PATCH v4 2/5] rtc: isl1208: add support for isl1219 with tamper detection

2018-07-11 Thread Ye Xiaolong
Hi, Denis The patch was applied in correct sequence as you can see in the github link. I think the question here is rtc-isl1208 can be built as a built-in module, but it would fail if it was built as a ko. Thanks, Xiaolong On 07/10, Denis OSTERLAND wrote: >Hi, > >seems 2/5 was applied before

Re: [lkp-robot] [x86/entry/64/compat] 8bb2610bc4: kernel_selftests.x86.test_syscall_vdso_32.fail

2018-07-04 Thread Ye Xiaolong
On 07/04, Linus Torvalds wrote: >On Tue, Jul 3, 2018 at 11:58 PM kernel test robot >wrote: >> >> FYI, we noticed the following commit (built with gcc-7): >> >> commit: 8bb2610bc4967f19672444a7b0407367f1540028 ("x86/entry/64/compat: >> Preserve r8-r11 in int $0x80") >> [...] >> caused below

Re: [lkp-robot] [fs] 3deb642f0d: will-it-scale.per_process_ops -8.8% regression

2018-06-27 Thread Ye Xiaolong
On 06/27, Christoph Hellwig wrote: >On Tue, Jun 26, 2018 at 02:03:38PM +0800, Ye Xiaolong wrote: >> Hi, >> >> On 06/22, Christoph Hellwig wrote: >> >Hi Xiaolong, >> > >> >can you retest this workload on the following branch: >> > >>

Re: [lkp-robot] [fs] 3deb642f0d: will-it-scale.per_process_ops -8.8% regression

2018-06-26 Thread Ye Xiaolong
Hi, On 06/22, Christoph Hellwig wrote: >Hi Xiaolong, > >can you retest this workload on the following branch: > >git://git.infradead.org/users/hch/vfs.git remove-get-poll-head > >Gitweb: > > > http://git.infradead.org/users/hch/vfs.git/shortlog/refs/heads/remove-get-poll-head Here is the

Re: [lkp-robot] [xfs] b027d4c97b: fio.latency_2ms% +7.1% regression

2018-06-05 Thread Ye Xiaolong
On 06/06, Dave Chinner wrote: >On Tue, Jun 05, 2018 at 03:16:57PM +0800, kernel test robot wrote: >> >> Greeting, >> >> FYI, we noticed a +7.1%% regression of fio.latency_2ms% due to commit: >> >> >> commit: b027d4c97b9675c2ad75dec94be4e46dceb3ec74 ("xfs: don't retry >> xfs_buf_find on

Re: [PATCH v4 0/1] Add livepatch kselftests

2018-05-10 Thread Ye Xiaolong
Hi, Joe Sorry for the late response. On 04/26, Joe Lawrence wrote: >>On 04/25/2018 02:28 PM, Joe Lawrence wrote: > >> [ ... snip ... ] >> >> base-commit: 0adb32858b0bddf4ada5f364a84ed60b196dbcda >> prerequisite-patch-id: 5ed747c1a89a5dc4bba08186e21f927d7f3bf049 >> prerequisite-patch-id:

Re: [lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage

2018-04-09 Thread Ye Xiaolong
On 04/09, Steven Rostedt wrote: >On Tue, 10 Apr 2018 09:23:40 +0800 >Ye Xiaolong <xiaolong...@intel.com> wrote: > >> Hi, Steven >> >> On 04/09, Steven Rostedt wrote: >> >On Mon, 9 Apr 2018 13:32:52 +0800 >> >kernel test robot <xiao

Re: [lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage

2018-04-09 Thread Ye Xiaolong
Hi, Steven On 04/09, Steven Rostedt wrote: >On Mon, 9 Apr 2018 13:32:52 +0800 >kernel test robot wrote: > >> FYI, we noticed the following commit (built with gcc-7): >> >> commit: 2580d6b795e25879c825a0891cf67390f665b11f ("init, tracing: Have >> printk come through the

Re: [lkp-robot] [sched/fair] d519329f72: unixbench.score -9.9% regression

2018-04-04 Thread Ye Xiaolong
On 04/03, Patrick Bellasi wrote: >Hi Xiaolong, > >On 02-Apr 11:20, kernel test robot wrote: >> >> Greeting, >> >> FYI, we noticed a -9.9% regression of unixbench.score due to commit: > >thanks for the report, I'll try to reproduce it locally to better >understand what's going on. Thanks for

Re: [lkp-robot] [iversion] c0cef30e4f: aim7.jobs-per-min -18.0% regression

2018-02-26 Thread Ye Xiaolong
On 02/25, Jeff Layton wrote: >On Sun, 2018-02-25 at 23:05 +0800, kernel test robot wrote: >> Greeting, >> >> FYI, we noticed a -18.0% regression of aim7.jobs-per-min due to commit: >> >> >> commit: c0cef30e4ff0dc025f4a1660b8f0ba43ed58426e ("iversion: make >> inode_cmp_iversion{+raw} return

Re: [lkp-robot] [mm, mlock, vmscan] 9c4e6b1a70: stress-ng.hdd.ops_per_sec -7.9% regression

2018-02-25 Thread Ye Xiaolong
Hi, Shakeel On 02/25, Shakeel Butt wrote: >On Sun, Feb 25, 2018 at 6:44 AM, kernel test robot > wrote: >> >> Greeting, >> >> FYI, we noticed a -7.9% regression of stress-ng.hdd.ops_per_sec due to >> commit: >> >> >> commit: 9c4e6b1a7027f102990c0395296015a812525f4d ("mm,

Re: [lkp-robot] [torture] b151f93a71: INFO:rcu_preempt_detected_stalls_on_CPUs/tasks

2017-11-27 Thread Ye Xiaolong
On 11/27, Paul E. McKenney wrote: >On Sun, Nov 26, 2017 at 04:42:03PM +0800, kernel test robot wrote: >> >> FYI, we noticed the following commit (built with gcc-6): >> >> commit: b151f93a71fc9fecb560e823a92402d882516483 ("torture: Eliminate >> torture_runnable") >>

Re: [lkp-robot] [fw_cfg] 05b5d5161b: WARNING:at_drivers/firmware/qemu_fw_cfg.c:#fw_cfg_dma_transfer

2017-11-16 Thread Ye Xiaolong
On 11/16, Michael S. Tsirkin wrote: >On Thu, Nov 16, 2017 at 08:58:13AM +0800, kernel test robot wrote: >> >> FYI, we noticed the following commit (built with gcc-6): >> >> commit: 05b5d5161b9e6c72e1d06f36614edbdbfe192cc7 ("fw_cfg: do DMA read >> operation") >>

Re: [lkp-robot] [printk] 7f7c60e066: BUG:KASAN:slab-out-of-bounds

2017-10-30 Thread Ye Xiaolong
On 10/30, Kees Cook wrote: >On Wed, Oct 25, 2017 at 9:22 AM, kernel test robot > wrote: >> >> FYI, we noticed the following commit (built with gcc-4.9): >> >> commit: 7f7c60e0663645e757e520245606fde9c6e326bb ("printk: hash addresses >> printed with %p") >> url: >>

Re: [lkp-robot] [x86/mm] c4c3c3c2d0: will-it-scale.per_process_ops -61.0% regression

2017-10-17 Thread Ye Xiaolong
On 10/17, Borislav Petkov wrote: >On Tue, Oct 17, 2017 at 06:57:43AM +0200, Markus Trippelsdorf wrote: >> On 2017.10.16 at 18:06 -0700, Andy Lutomirski wrote: >> > On Mon, Oct 16, 2017 at 3:15 AM, Borislav Petkov wrote: >> > > On Mon, Oct 16, 2017 at 10:39:17AM +0800, kernel test

Re: [lkp-robot] [x86/mm] c4c3c3c2d0: will-it-scale.per_process_ops -61.0% regression

2017-10-17 Thread Ye Xiaolong
Hi, Andy On 10/16, Andy Lutomirski wrote: >On Mon, Oct 16, 2017 at 3:15 AM, Borislav Petkov wrote: >> On Mon, Oct 16, 2017 at 10:39:17AM +0800, kernel test robot wrote: >>> >>> Greeting, >>> >>> FYI, we noticed a -61.0% regression of will-it-scale.per_process_ops due to >>>

Re: [lkp-robot] [fs] 91f9943e1c: aim7.jobs-per-min -26.6% regression

2017-10-16 Thread Ye Xiaolong
On 10/16, Christoph Hellwig wrote: >The only change for the non-nowait case is that we now do a trylock before >locking i_rwsem. In the past that was the more optimal pattern. Can you >test the patch below if that's not the case anymore? We have a few more >instances like that which might also

Re: [lkp-robot] [blk] 47e0fb461f: BUG:unable_to_handle_kernel

2017-10-12 Thread Ye Xiaolong
On 10/09, Tejun Heo wrote: >Hello, > >On Sat, Sep 30, 2017 at 01:21:13PM -0700, Linus Torvalds wrote: >> Tejun, any ideas? The original report is at >> >>https://lkml.org/lkml/2017/9/20/939 >> >> in case you don't see it in your inbox from lkml. > >So, in the full log, there is an earlier

Re: [lkp-robot] [blk] 47e0fb461f: BUG:unable_to_handle_kernel

2017-10-09 Thread Ye Xiaolong
On 09/30, Linus Torvalds wrote: >On Thu, Sep 21, 2017 at 12:02 AM, NeilBrown wrote: >> >> I think it is crashing in >> static inline bool ata_is_host_link(const struct ata_link *link) >> { >> return link == >ap->link || link == link->ap->slave_link; >> } > >Yes. The code

Re: [PATCH] x86/asm: Fix inline asm call constraints for GCC 4.4

2017-09-29 Thread Ye Xiaolong
h implies >debugging. > >( Sometimes we refer to 'debugging a bug' as the reporter adding printks on > request and printing out key state that helps understand the bug. It does > not > necessarily imply root-causing the bug. ) > >Also note that I added a "Reported-and-Bisected-by:" tag for the ktest robot, >to >further credit the fact that in addition to reporting a kernel crash, a >specific >commit was bisected to as well. > >I'll wait for another round of ktest robot testing to make sure the crash is >indeed fixed. The panic is gone with the fix patch for 4 times test. Tested-by: Ye Xiaolong <xiaolong...@intel.com> Thanks, Xiaolong > >Thanks, > > Ingo

Re: [lkp-robot] [irda] 66d98e78e4: BUG:unable_to_handle_kernel

2017-08-30 Thread Ye Xiaolong
On 08/30, Greg Kroah-Hartman wrote: >On Wed, Aug 30, 2017 at 02:04:11PM +0800, kernel test robot wrote: >> FYI, we noticed the following commit: >> >> commit: 66d98e78e44ccb969cb3196995759d200e64b49b ("irda: move net/irda/ to >> drivers/staging/irda/net/") >> url: >>

Re: [PATCH] ARM: sun8i: a83t: Add device tree for Sinovoip Bananapi BPI-M3

2017-08-24 Thread Ye Xiaolong
On 08/20, icen...@aosc.io wrote: >在 2017-08-20 08:59,kbuild test robot 写道: >>Hi Chen-Yu, >> >>[auto build test ERROR on robh/for-next] >>[also build test ERROR on v4.13-rc5 next-20170817] >>[if your patch is applied to the wrong git tree, please drop us a note >>to help improve the system] > >In

Re: [lkp-robot] [mm] 7674270022: will-it-scale.per_process_ops -19.3% regression

2017-08-08 Thread Ye Xiaolong
On 08/08, Minchan Kim wrote: >On Mon, Aug 07, 2017 at 10:51:00PM -0700, Nadav Amit wrote: >> Nadav Amit wrote: >> >> > Minchan Kim wrote: >> > >> >> Hi, >> >> >> >> On Tue, Aug 08, 2017 at 09:19:23AM +0800, kernel test robot wrote: >> >>> Greeting, >>

Re: [lkp-robot] [mm] 7674270022: will-it-scale.per_process_ops -19.3% regression

2017-08-08 Thread Ye Xiaolong
On 08/08, Minchan Kim wrote: >On Mon, Aug 07, 2017 at 10:51:00PM -0700, Nadav Amit wrote: >> Nadav Amit wrote: >> >> > Minchan Kim wrote: >> > >> >> Hi, >> >> >> >> On Tue, Aug 08, 2017 at 09:19:23AM +0800, kernel test robot wrote: >> >>> Greeting, >>

Re: [lkp-robot] [include/linux/string.h] 6974f0c455: kernel_BUG_at_lib/string.c

2017-07-20 Thread Ye Xiaolong
Hi, On 07/19, Linus Torvalds wrote: >Hmm. I wonder why the kernel test robot ends up having that annoying >line doubling for the dmesg. > Hmm, this line doubling issue should be caused by we set both 'earlyprintk=ttyS0,115200' and 'console=ttyS0,115200' in cmdline, after I remove any of it, this

Re: [x86/time] 03fa63cc96: ACPI_Error:Table[DMAR]is_not_invalidated_during_early_boot_stage(#/tbxface -#)

2017-07-06 Thread Ye Xiaolong
On 07/07, Dou Liyang wrote: >Hi xiaolong, > >Really thanks for your testing. > >At 07/07/2017 09:54 AM, Ye Xiaolong wrote: >>On 07/06, Thomas Gleixner wrote: >>>On Thu, 6 Jul 2017, kernel test robot wrote: >>> >>>>commit: 03fa63cc96ab

Re: [x86/time] 03fa63cc96: ACPI_Error:Table[DMAR]is_not_invalidated_during_early_boot_stage(#/tbxface -#)

2017-07-06 Thread Ye Xiaolong
On 07/06, Thomas Gleixner wrote: >On Thu, 6 Jul 2017, kernel test robot wrote: > >> commit: 03fa63cc96ab35592e0a7d522b8edbc1e6b02d22 ("x86/time: Initialize >> interrupt mode behind timer init") > >> ++++ >> || 43436935b7 | 03fa63cc96 | >>

Re: [lkp-robot] [scsi] 5c279bd9e4: blogbench.read_score -10.0% regression

2017-07-05 Thread Ye Xiaolong
Hi, Ming Lei On 07/06, Ming Lei wrote: >Hi Xiaolong, > >On Mon, Jul 3, 2017 at 10:57 AM, kernel test robot > wrote: >> >> Greeting, >> >> FYI, we noticed a -10.0% regression of blogbench.read_score due to commit: > >Looks like related with mq scheduler, could you test the

Re: [lkp-robot] [ALSA] fcc88d91cd: WARNING:at_sound/hda/hdac_i915.c:#snd_hdac_i915_init[snd_hda_core]

2017-07-05 Thread Ye Xiaolong
On 07/03, Takashi Iwai wrote: >On Mon, 03 Jul 2017 04:41:02 +0200, >kernel test robot wrote: >> >> >> FYI, we noticed the following commit: >> >> commit: fcc88d91cd36d1343a0ccc09444b21f6b0dad2d8 ("ALSA: hda - Bind with >> i915 component before codec binding") >>

Re: [kbuild-all] [PATCH] include/linux/vfio.h: Guard powerpc-specific functions with CONFIG_VFIO_SPAPR_EEH

2017-06-13 Thread Ye Xiaolong
On 06/08, Alexey Kardashevskiy wrote: >On 08/06/17 15:35, Alexey Kardashevskiy wrote: >> Hi, >> >> How did you manage to have CONFIG_EEH=y and CONFIG_VFIO_SPAPR_EEH=n? "make >> oldconfig" fixes this to CONFIG_VFIO_SPAPR_EEH=y. > > >Also, the attached config has "CONFIG_VFIO_SPAPR_EEH=m" and

Re: [posix] 91d57bae08: WARNING:at_kernel/time/hrtimer.c:#hrtimer_forward

2017-06-12 Thread Ye Xiaolong
On 06/12, Thomas Gleixner wrote: >On Fri, 9 Jun 2017, kernel test robot wrote: >> >> FYI, we noticed the following commit: >> >> commit: 91d57bae08689199c8acc77a8b3b41150cafab1c ("posix-timers: Make use of >> forward/remaining callbacks") >>

Re: [lkp-robot] [mm, memcg] b4536f0c82: kobject(#):tried_to_init_an_initialized_object,something_is_seriously_wrong

2017-06-12 Thread Ye Xiaolong
On 06/12, Michal Hocko wrote: >On Mon 12-06-17 14:59:45, kernel test robot wrote: >> >> FYI, we noticed the following commit: >> >> commit: b4536f0c829c8586544c94735c343f9b5070bd01 ("mm, memcg: fix the active >> list aging for lowmem requests when memcg is enabled") >>

Re: [LKP] [lkp-robot] [EDAC, sb_edac] e2f747b1f4: kmsg.EDAC_sbridge:Failed_to_register_device_with_error

2017-06-11 Thread Ye Xiaolong
On 06/12, Ye Xiaolong wrote: >On 06/10, Zhuo, Qiuxu wrote: >>> From: Borislav Petkov [mailto:b...@alien8.de] >>> >>> Xiaolong, >>> >>> can you please run Qiuxu's patch to verify it fixes your issue? >> >> >>Hi Boris, >>

Re: [lkp-robot] [EDAC, sb_edac] e2f747b1f4: kmsg.EDAC_sbridge:Failed_to_register_device_with_error

2017-06-11 Thread Ye Xiaolong
On 06/10, Zhuo, Qiuxu wrote: >> From: Borislav Petkov [mailto:b...@alien8.de] >> >> Xiaolong, >> >> can you please run Qiuxu's patch to verify it fixes your issue? > > >Hi Boris, >I manually verified the fix patch on the Broadwell-DE server on which the > bug was found by Xiaolong: >the

Re: [lkp-robot] [KEYS] 501901ac94: ltp.add_key02.fail

2017-06-09 Thread Ye Xiaolong
On 06/09, David Howells wrote: >kernel test robot wrote: > >> user :notice: [ 82.772613] add_key02.c:65: FAIL: add_key() failed >> unexpectedly, expected EINVAL: EFAULT > >The LTP test needs updating. Eric has a patch for that. Got it, thanks for the information.

Re: [kbuild-all] [PATCH v4 3/9] arm: dts: mt7623: add mt7623-mt6323.dtsi file

2017-05-31 Thread Ye Xiaolong
Hi, Matthias On 05/29, Matthias Brugger wrote: > > >On 28/05/17 13:31, kbuild test robot wrote: >>Hi John, >> >>[auto build test ERROR on robh/for-next] >>[also build test ERROR on v4.12-rc2 next-20170526] >>[if your patch is applied to the wrong git tree, please drop us a note to >>help improve

Re: [kbuild-all] [PATCH v4 2/3] hwmon: (adt7475) temperature smoothing

2017-05-17 Thread Ye Xiaolong
On 05/16, Guenter Roeck wrote: 0day bot applied your patchset on top of commit 6eaaea1 ("hwmon: (pmbus) Add client driver for IR35221"), is it wrong or you have some prerequisite patches? >> >>Thanks for the info, seems we need to improve the kbuild bot by pulling the >>latest tree

Re: [kbuild-all] [PATCH v4 2/3] hwmon: (adt7475) temperature smoothing

2017-05-16 Thread Ye Xiaolong
On 05/17, Chris Packham wrote: >On 17/05/17 15:09, Ye Xiaolong wrote: >> On 05/16, Chris Packham wrote: >>> On 16/05/17 20:23, kbuild test robot wrote: >>>> Hi Chris, >>>> >>>> [auto build test ERROR on hwmon/hwmon-next] >>>> [als

Re: [kbuild-all] [PATCH v4 2/3] hwmon: (adt7475) temperature smoothing

2017-05-16 Thread Ye Xiaolong
On 05/16, Chris Packham wrote: >On 16/05/17 20:23, kbuild test robot wrote: >> Hi Chris, >> >> [auto build test ERROR on hwmon/hwmon-next] >> [also build test ERROR on v4.12-rc1 next-20170516] >> [if your patch is applied to the wrong git tree, please drop us a note to >> help improve the system]

Re: [lkp-robot] [asm] c1aad8dcc4: BUG:kernel_hang_in_boot_stage

2017-05-15 Thread Ye Xiaolong
On 05/16, Al Viro wrote: >On Tue, May 16, 2017 at 09:19:57AM +0800, kernel test robot wrote: >> >> FYI, we noticed the following commit: >> >> commit: c1aad8dcc49382399f48541dc47b6e30b0ef1b62 ("asm-generic: zero in >> __get_user(), not __get_user_fn()") >>

Re: [lkp-robot] [rcuperf] 87c458e630: WARNING:at_arch/x86/kernel/smp.c:#native_smp_send_reschedule

2017-05-03 Thread Ye Xiaolong
On 05/03, Paul E. McKenney wrote: >On Thu, May 04, 2017 at 10:59:26AM +0800, kernel test robot wrote: >> >> FYI, we noticed the following commit: >> >> commit: 87c458e6304c6a1b37bf856e88c70fc37f08851f ("rcuperf: Set more >> user-friendly defaults") >>

Re: [lkp-robot] [perf] 924726b2b5: double_fault:#[##]

2017-04-27 Thread Ye Xiaolong
On 04/27, Sebastian Andrzej Siewior wrote: >On 2017-04-27 10:58:36 [+0800], kernel test robot wrote: >> >> FYI, we noticed the following commit: >> >> commit: 924726b2b5e5000dfb8eb6032651baed1b1bdc6c ("perf: Cure hotplug lock >> ordering issues") >>

Re: [kbuild-all] [PATCH v3] axon_ram: add dax_operations support

2017-04-26 Thread Ye Xiaolong
On 04/19, Dan Williams wrote: >On Wed, Apr 19, 2017 at 8:01 PM, kbuild test robot wrote: >> Hi Dan, >> >> [auto build test ERROR on powerpc/next] >> [also build test ERROR on v4.11-rc7 next-20170419] >> [if your patch is applied to the wrong git tree, please drop us a note to >>

Re: [lkp-robot] [debugfs] f3e7155d08: BUG:unable_to_handle_kernel

2017-04-24 Thread Ye Xiaolong
On 04/23, Nicolai Stange wrote: >Hi Xiaolong, > >I'm encountering some difficulties running the reproducer, see below. >Any help is very welcome! > Thanks for watching the report and trying the reproducer. > >On Tue, Apr 18 2017, kernel test robot wrote: > >> [ 45.772683] BUG: unable to handle

Re: [kbuild-all] [PATCH V2 16/16] block, bfq: split bfq-iosched.c into multiple source files

2017-04-12 Thread Ye Xiaolong
On 04/11, Paolo Valente wrote: > >> Il giorno 02 apr 2017, alle ore 12:02, kbuild test robot ha >> scritto: >> >> Hi Paolo, >> >> [auto build test ERROR on block/for-next] >> [also build test ERROR on v4.11-rc4 next-20170331] >> [if your patch is applied to the wrong git tree,

Re: [printk] fbc14616f4: BUG:kernel_reboot-without-warning_in_test_stage

2017-04-05 Thread Ye Xiaolong
On 03/31, Ye Xiaolong wrote: >On 03/31, Sergey Senozhatsky wrote: >>On (03/31/17 11:35), Sergey Senozhatsky wrote: >>[..] >>> > [ 21.009531] VFS: Warning: trinity-c2 using old stat() call. Recompile >>> > your binary. >>> > [ 21.148

Re: [printk] fbc14616f4: BUG:kernel_reboot-without-warning_in_test_stage

2017-03-31 Thread Ye Xiaolong
On 03/31, Sergey Senozhatsky wrote: >On (03/31/17 11:35), Sergey Senozhatsky wrote: >[..] >> > [ 21.009531] VFS: Warning: trinity-c2 using old stat() call. Recompile >> > your binary. >> > [ 21.148898] VFS: Warning: trinity-c0 using old stat() call. Recompile >> > your binary. >> > [

Re: [kbuild-all] [PATCH 1/2] usb: phy: Introduce one extcon device into usb phy

2017-03-22 Thread Ye Xiaolong
On 03/20, Baolin Wang wrote: >Hi, > > >On 19 March 2017 at 19:42, kbuild test robot wrote: >> Hi Baolin, >> >> [auto build test ERROR on balbi-usb/next] >> [also build test ERROR on v4.11-rc2 next-20170310] >> [if your patch is applied to the wrong git tree, please drop us a note

Re: [x86] 45fc8757d1: BUG:unable_to_handle_kernel

2017-03-19 Thread Ye Xiaolong
On 03/17, Thomas Garnier wrote: >I tried multiple things to repro this crash without success: > - Used the config on my existing qemu setup (boot fine) > - Add most of the command-line (boot fine) > - Try to run the script on a dedicated machine and it seems it is >really tailored for your setup.

Re: [lkp-robot] [mm] bae58218d8: WARNING:at_mm/page_alloc.c:#drain_all_pages

2017-03-16 Thread Ye Xiaolong
//git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master > >Could you test with >http://lkml.kernel.org/r/20170315164021.28532-1-mho...@kernel.org >applied? This warning is gone with above patch applied for 10 time boot. Tested-by: Xiaolong Ye <xiaolong...@intel.com> Thanks, Xiaolong >-- >Michal Hocko >SUSE Labs

Re: [lkp-robot] [f2fs] 4ac912427c: -33.7% aim7.jobs-per-min regression

2017-03-16 Thread Ye Xiaolong
On 03/15, Jaegeuk Kim wrote: >On 03/14, Ye Xiaolong wrote: >> On 03/14, Chao Yu wrote: >> >On 2017/3/14 3:22, Jaegeuk Kim wrote: >> >> On 03/13, Thorsten Leemhuis wrote: >> >>> @Chao Yu/@Jaegeuk Kim: I'm considering to add this to the regressions >

Re: [lkp-robot] [f2fs] 4ac912427c: -33.7% aim7.jobs-per-min regression

2017-03-15 Thread Ye Xiaolong
On 03/15, Jaegeuk Kim wrote: >On 03/14, Ye Xiaolong wrote: >> On 03/14, Chao Yu wrote: >> >On 2017/3/14 3:22, Jaegeuk Kim wrote: >> >> On 03/13, Thorsten Leemhuis wrote: >> >>> @Chao Yu/@Jaegeuk Kim: I'm considering to add this to the regressions >

Re: [lkp-robot] [f2fs] 4ac912427c: -33.7% aim7.jobs-per-min regression

2017-03-14 Thread Ye Xiaolong
ches in Jaegeuk's tree could help to recover the performance >as well > > f2fs: skip scanning free nid bitmap of full NAT blocks > f2fs: combine nat_bits and free_nid_bitmap cache These 2 patches do help recover the performance back. Details as below. Tested-by: Xiaolong Ye

Re: [lkp-robot] [f2fs] 4ac912427c: -33.7% aim7.jobs-per-min regression

2017-03-13 Thread Ye Xiaolong
On 03/14, Chao Yu wrote: >On 2017/3/14 3:22, Jaegeuk Kim wrote: >> On 03/13, Thorsten Leemhuis wrote: >>> @Chao Yu/@Jaegeuk Kim: I'm considering to add this to the regressions >>> report for 4.11; or is there a reason why it shouldn't be considered a >>> regression? Ciao, Thorsten >> >> Hi, >>

Re: [lkp-robot] [x86] ed3ce2a917: BUG:unable_to_handle_kernel

2017-03-09 Thread Ye Xiaolong
On 03/09, Borislav Petkov wrote: >On Thu, Mar 09, 2017 at 10:13:10AM +0800, Ye Xiaolong wrote: >> >Anyway, the diff is below, please try that ontop of tip's x86/asm branch >> >which already has the clear_page patch: >> > >> >http://git.kernel.org/cgit/linu

Re: [kbuild-all] [media] omap3isp: Correctly set IO_OUT_SEL and VP_CLK_POL for CCP2 mode

2017-03-09 Thread Ye Xiaolong
On 03/03, Pavel Machek wrote: >Hi! > >> [auto build test ERROR on linuxtv-media/master] >> [also build test ERROR on v4.10 next-20170303] >> [if your patch is applied to the wrong git tree, please drop us a note to >> help improve the system] >> > >Yes, the patch is against Sakari's ccp2 branch.

Re: [kbuild-all] [PATCH 6/6] sysctl: Add global tunable mt_page_copy

2017-03-09 Thread Ye Xiaolong
On 03/08, Anshuman Khandual wrote: >On 02/17/2017 09:00 PM, kbuild test robot wrote: >> Hi Zi, >> >> [auto build test ERROR on linus/master] >> [also build test ERROR on v4.10-rc8 next-20170217] >> [if your patch is applied to the wrong git tree, please drop us a note to >> help improve the

Re: [lkp-robot] [x86] ed3ce2a917: BUG:unable_to_handle_kernel

2017-03-08 Thread Ye Xiaolong
On 03/02, Borislav Petkov wrote: >Hi, > >On Thu, Mar 02, 2017 at 09:09:34AM +0800, kernel test robot wrote: >> >> FYI, we noticed the following commit: >> >> commit: ed3ce2a9172457ef7dbaa9f964e63dfde2bdcb5f ("x86: Optimize >> clear_page()") >> url: >>

Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-27 Thread Ye Xiaolong
On 02/28, Ye Xiaolong wrote: >On 02/27, Peter Chen wrote: >>On Sun, Feb 26, 2017 at 06:19:59PM +0800, Fengguang Wu wrote: >>> [Sorry, resend to correct Felipe's email address] >>> >>> Greetings, >>> >>> This debug patch possibly discloses

Re: [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-27 Thread Ye Xiaolong
On 02/27, Peter Chen wrote: >On Sun, Feb 26, 2017 at 06:19:59PM +0800, Fengguang Wu wrote: >> [Sorry, resend to correct Felipe's email address] >> >> Greetings, >> >> This debug patch possibly discloses some USB/I2C bugs. Since the USB >> warning shows up earlier in dmesg, it might also be the

Re: [lkp-robot] [x86/mm/ptdump] 243b72aae2: WARNING:at_arch/x86/mm/dump_pagetables.c:#note_page

2017-02-27 Thread Ye Xiaolong
On 02/28, Masami Hiramatsu wrote: >On Mon, 27 Feb 2017 16:01:34 +0300 >Andrey Ryabinin wrote: > >> On 02/27/2017 04:03 AM, kernel test robot wrote: >> > >> > FYI, we noticed the following commit: >> > >> > commit: 243b72aae28ca1032284028323bb81c9235b15c9

Re: [lkp-robot] [platform/x86] a869ab5dab: BUG:unable_to_handle_kernel

2017-02-26 Thread Ye Xiaolong
On 02/27, Jonathan Woithe wrote: >On Mon, Feb 27, 2017 at 09:04:14AM +0800, kernel test robot wrote: >> FYI, we noticed the following commit: >> >> commit: a869ab5dabf6ec5327a3b2bb366eccf80b207d76 ("platform/x86: >> fujitsu-laptop: only register backlight device if FUJ02B1 is present") >>

Re: [lkp-robot] [mm, vmscan] 5e56dfbd83: fsmark.files_per_sec -11.1% regression

2017-02-22 Thread Ye Xiaolong
Hi, Michal On 02/07, Michal Hocko wrote: [snip] >Could you retest with a single NUMA node? I am not familiar with the >benchmark enough to judge it was set up properly for a NUMA machine. I've retested the commit with a single NUMA node via "numactl -m 0 fs_mark xxx", and it did help recover the

Re: [PATCH v2 0/4] Revert works for the mapping of cpuid <-> nodeid

2017-02-20 Thread Ye Xiaolong
On 02/21, Ye Xiaolong wrote: >On 02/20, Dou Liyang wrote: >>Currently, We make the mapping of "cpuid <-> nodeid" fixed at the booting >>time. >>It keeps consistent with the WorkQueue and avoids some bugs which may be >>caused >>by the dy

Re: [LKP] [hrtimer] 336a9cde10 WARNING: CPU: 1 PID: 1 at kernel/time/hrtimer.c:1090 hrtimer_init

2017-02-20 Thread Ye Xiaolong
On 02/21, Ye Xiaolong wrote: >Hi, fengguang >On 02/20, Thomas Gleixner wrote: >>On Tue, 21 Feb 2017, Fengguang Wu wrote: >> >>> Hi Marc, >>> >>> FYI here is another bisect result. The attached reproduce-* script can >>> be used to reproduce

Re: [hrtimer] 336a9cde10 WARNING: CPU: 1 PID: 1 at kernel/time/hrtimer.c:1090 hrtimer_init

2017-02-20 Thread Ye Xiaolong
Hi, fengguang On 02/20, Thomas Gleixner wrote: >On Tue, 21 Feb 2017, Fengguang Wu wrote: > >> Hi Marc, >> >> FYI here is another bisect result. The attached reproduce-* script can >> be used to reproduce the bug. > >Again. This is a problem in the calling code The WARN_ON merily shows the

Re: [lkp-robot] [tcp] e70ac17165: WARNING:at_kernel/softirq.c:#__local_bh_enable_ip

2017-02-20 Thread Ye Xiaolong
On 02/20, Eric Dumazet wrote: >On Sun, Feb 19, 2017 at 6:11 PM, kernel test robot > wrote: >> >> FYI, we noticed the following commit: >> >> commit: e70ac171658679ecf6bea4bbd9e9325cd6079d2b ("tcp: tcp_probe: use >> spin_lock_bh()") >>

Re: [PATCH v2 0/4] Revert works for the mapping of cpuid <-> nodeid

2017-02-20 Thread Ye Xiaolong
On 02/20, Dou Liyang wrote: >Currently, We make the mapping of "cpuid <-> nodeid" fixed at the booting time. >It keeps consistent with the WorkQueue and avoids some bugs which may be caused >by the dynamic assignment. >As we know, It is implemented by the patches as follows: 2532fc318d,

Re: [lkp] [x86/acpi] dc6db24d24: BUG: unable to handle kernel paging request at 0000116007090008

2017-02-12 Thread Ye Xiaolong
Hi, liyang On 02/13, Dou Liyang wrote: >Hi, Xiaolong > >At 02/13/2017 09:37 AM, Ye Xiaolong wrote: >>On 11/21, Dou Liyang wrote: >>>Hi, Xiaolong, >>> >>>At 11/21/2016 09:31 AM, Ye Xiaolong wrote: >>>>On 11/18, Dou Liyang wrote: >>>>

Re: [lkp-robot] [mm, vmscan] 5e56dfbd83: fsmark.files_per_sec -11.1% regression

2017-02-06 Thread Ye Xiaolong
On 02/06, Michal Hocko wrote: >On Sat 04-02-17 16:16:04, Ye Xiaolong wrote: >> On 01/26, Michal Hocko wrote: >> >On Wed 25-01-17 12:27:06, Ye Xiaolong wrote: >> >> On 01/24, Michal Hocko wrote: >[...] >> >> >perf profiles before and after t

Re: [lkp-robot] [mm/memblock] cc4a913fa5: WARNING:at_mm/memblock.c:#__next_mem_pfn_range

2017-02-05 Thread Ye Xiaolong
On 02/05, Wei Yang wrote: >On Fri, Feb 03, 2017 at 09:44:49AM +0800, kernel test robot wrote: >> >>FYI, we noticed the following commit: >> >>commit: cc4a913fa513cdac8777c2714e6388465691faf8 ("mm/memblock: switch to use >>NUMA_NO_NODE instead of MAX_NUMNODES in for_each_mem_pfn_range()") >>url:

Re: [lkp-robot] [mm, vmscan] 5e56dfbd83: fsmark.files_per_sec -11.1% regression

2017-02-04 Thread Ye Xiaolong
On 01/26, Michal Hocko wrote: >On Wed 25-01-17 12:27:06, Ye Xiaolong wrote: >> On 01/24, Michal Hocko wrote: >> >On Mon 23-01-17 09:26:44, kernel test robot wrote: >> >> >> >> Greeting, >> >> >> >> FYI, we

Re: [sched/clock] 9881b024b7: WARNING:at_kernel/sched/clock.c:#set_sched_clock_stable

2017-02-03 Thread Ye Xiaolong
On 01/26, Peter Zijlstra wrote: >On Thu, Jan 26, 2017 at 05:14:06AM +0800, kernel test robot wrote: >> >> FYI, we noticed the following commit: >> >> commit: 9881b024b7d7671f6a014091bc96506b89081802 ("sched/clock: Delay >> switching sched_clock to stable") >>

Re: [kbuild-all] [PATCH 1/3] pinctrl: intel: Add support for hardware debouncer

2017-02-02 Thread Ye Xiaolong
On 01/27, Mika Westerberg wrote: >On Fri, Jan 27, 2017 at 07:51:03PM +0800, kbuild test robot wrote: >> Hi Mika, >> >> [auto build test ERROR on pinctrl/for-next] >> [also build test ERROR on v4.10-rc5 next-20170125] >> [if your patch is applied to the wrong git tree, please drop us a note to >>

Re: [lkp-robot] [mm, vmscan] 5e56dfbd83: fsmark.files_per_sec -11.1% regression

2017-01-24 Thread Ye Xiaolong
On 01/24, Michal Hocko wrote: >On Mon 23-01-17 09:26:44, kernel test robot wrote: >> >> Greeting, >> >> FYI, we noticed a -11.1% regression of fsmark.files_per_sec due to commit: >> >> >> commit: 5e56dfbd837421b7fa3c6c06018c6701e2704917 ("mm, vmscan: consider >> eligible zones in

Re: [lkp-robot] e5a305ac4a: WARNING:at_lib/list_debug.c:#__list_del_entry_valid

2017-01-18 Thread Ye Xiaolong
On 01/18, Andrew Morton wrote: >On Wed, 18 Jan 2017 09:23:04 +0800 kernel test robot >wrote: > >> >> FYI, we noticed the following commit: >> >> commit: e5a305ac4a5233e039586c97f4ea643a4c7dc484 ("Reimplement IDR and IDA >> using the radix tree") >>

Re: [lkp-robot] e5a305ac4a: WARNING:at_lib/list_debug.c:#__list_del_entry_valid

2017-01-18 Thread Ye Xiaolong
On 01/18, Matthew Wilcox wrote: >From: lkp-robot-requ...@eclists.intel.com >[mailto:lkp-robot-requ...@eclists.intel.com] On Behalf Of kernel test robot >> FYI, we noticed the following commit: >> >> commit: e5a305ac4a5233e039586c97f4ea643a4c7dc484 ("Reimplement IDR >> and IDA using the radix

Re: [lkp-developer] [ACPICA] 174cc7187e: kmsg.ACPI_Error:Mutex[ACPI_MTX_Tables]already_acquired_by_this_thread[#](#/utmutex-#)

2017-01-11 Thread Ye Xiaolong
s Linux version 4.9.0-rc5-00017-g174cc71 which means commit 174cc7187e is the head commit to be built. Thanks, Xiaolong > >Thanks and best regards >Lv > >> From: lkp-developer-requ...@eclists.intel.com >> [mailto:lkp-developer-requ...@eclists.intel.com] On >> Beha

Re: [lkp-developer] [sched/core] 6b94780e45: unixbench.score -4.5% regression

2017-01-02 Thread Ye Xiaolong
On 01/02, Vincent Guittot wrote: >Hi Xiaolong, > >Le Monday 19 Dec 2016 à 08:14:53 (+0800), kernel test robot a écrit : >> >> Greeting, >> >> FYI, we noticed a -4.5% regression of unixbench.score due to commit: > >I have been able to restore performance on my platform with the patch below. >Could

Re: [kbuild-all] [PATCH 4/4] thermal/intel_powerclamp: stop sched tick in forced idle

2016-11-29 Thread Ye Xiaolong
On 11/28, Jacob Pan wrote: >On Tue, 29 Nov 2016 07:21:14 +0800 >kbuild test robot wrote: > >> Hi Jacob, >> >> [auto build test ERROR on soc-thermal/next] >> [also build test ERROR on v4.9-rc7 next-20161128] >> [if your patch is applied to the wrong git tree, please drop us a >>

Re: [lkp] [mm] e7c1db75fe: BUG:sleeping_function_called_from_invalid_context_at_mm/page_alloc.c

2016-11-29 Thread Ye Xiaolong
On 11/29, Paul E. McKenney wrote: >On Tue, Nov 29, 2016 at 05:21:19PM +, Sudeep Holla wrote: >> On Sun, Nov 27, 2016 at 6:16 PM, kernel test robot >> wrote: >> > >> > FYI, we noticed the following commit: >> > >> > commit e7c1db75fed821a961ce1ca2b602b08e75de0cd8 ("mm:

Re: [lkp] [mm] e7c1db75fe: BUG:sleeping_function_called_from_invalid_context_at_mm/page_alloc.c

2016-11-29 Thread Ye Xiaolong
On 11/29, Paul E. McKenney wrote: >On Tue, Nov 29, 2016 at 05:21:19PM +, Sudeep Holla wrote: >> On Sun, Nov 27, 2016 at 6:16 PM, kernel test robot >> wrote: >> > >> > FYI, we noticed the following commit: >> > >> > commit e7c1db75fed821a961ce1ca2b602b08e75de0cd8 ("mm:

Re: [lkp] [rcu] a7410f28ce: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 0-... } 25089 jiffies s: 9 root: 0x1/.

2016-11-28 Thread Ye Xiaolong
On 11/28, Sebastian Andrzej Siewior wrote: >On 2016-11-09 14:25:39 [+0800], kernel test robot wrote: >> >> FYI, we noticed the following commit: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master >> commit a7410f28ceb566bda840b4afc278747c63383fb6 ("rcu: update: Make

Re: [LKP] [net] 34fad54c25: kernel BUG at include/linux/skbuff.h:1935!

2016-11-23 Thread Ye Xiaolong
On 11/22, Linus Torvalds wrote: >On Tue, Nov 22, 2016 at 10:44 PM, Fengguang Wu wrote: >> >> On Tue, Nov 22, 2016 at 02:04:42PM -0800, Linus Torvalds wrote: >> >>> I also noticed that the kernel test robot had screwed up the >>> participants list for some reason, and had

Re: [kbuild-all] [Patch v6.1] x86/kvm: Add AVX512_4VNNIW and AVX512_4FMAPS support

2016-11-20 Thread Ye Xiaolong
On 11/15, He Chen wrote: >On Tue, Nov 15, 2016 at 04:24:39AM +0800, kbuild test robot wrote: >> Hi He, >> >> [auto build test ERROR on kvm/linux-next] >> [also build test ERROR on v4.9-rc5] >> [cannot apply to next-20161114] >> [if your patch is applied to the wrong git tree, please drop us a

Re: [net] 34fad54c25: kernel BUG at include/linux/skbuff.h:1935!

2016-11-15 Thread Ye Xiaolong
On 11/16, Duyck, Alexander H wrote: >On Wed, 2016-11-16 at 05:20 +0800, kernel test robot wrote: >From what I can tell it looks like the size of the frame is 0x160 hex, >or 352.  For whatever reason we are only pulling 8 bytes into the >header which is giving us an skb->len of 352 (0x160), and a

Re: [lkp] [net] af1fee9821: BUG:spinlock_trylock_failure_on_UP_on_CPU

2016-11-07 Thread Ye Xiaolong
On 11/07, Allan W. Nielsen wrote: >Hi, > >I tried to get this "lkp" up and running, but I had some troubles gettting >these scripts to work. Hi, Allan Could you tell us what troubles you have met when trying the "lkp qemu" tool, it would be better if you could paste some log so we can help to

Re: [lkp] [x86/platform/UV] 71854cb812: will-it-scale.per_thread_ops -2.3% regression

2016-10-26 Thread Ye Xiaolong
On 10/25, Thomas Gleixner wrote: >On Tue, 25 Oct 2016, kernel test robot wrote: >> FYI, we noticed a -2.3% regression of will-it-scale.per_thread_ops due to >> commit: >> >> commit 71854cb812ec23bfe5f63d52217e6b9e6cb901f5 ("x86/platform/UV: Fix >> support for EFI_OLD_MEMMAP after BIOS callback

Re: [lkp] [x86/acpi] dc6db24d24: BUG: unable to handle kernel paging request at 0000116007090008

2016-10-20 Thread Ye Xiaolong
On 10/20, Dou Liyang wrote: >Hi xiaolong, > >Thank you very much for report. > >I was just investigating the related problem in another patches. > > >At 10/20/2016 09:16 AM, kernel test robot wrote: >> >>FYI, we noticed the following commit: >>

Re: [LKP] [x86] 811565123a: BUG: kernel hang in early-boot stage, last printk: Probing EDD (edd=off to disable)... ok

2016-10-16 Thread Ye Xiaolong
On 10/14, Andi Kleen wrote: >On Fri, Oct 14, 2016 at 12:56:00PM +0800, Ye Xiaolong wrote: >> On 10/14, Ye Xiaolong wrote: >> >On 10/13, Andi Kleen wrote: >> >>Andi Kleen <a...@firstfloor.org> writes: >> >> >> >>Any comments on this? &

Re: [LKP] [x86] 811565123a: BUG: kernel hang in early-boot stage, last printk: Probing EDD (edd=off to disable)... ok

2016-10-13 Thread Ye Xiaolong
On 10/14, Ye Xiaolong wrote: >On 10/13, Andi Kleen wrote: >>Andi Kleen <a...@firstfloor.org> writes: >> >>Any comments on this? >> >>I still cannot reproduce the failure unfortunately. >> > >Btw, you can try below commands to reproduc

Re: [x86] 811565123a: BUG: kernel hang in early-boot stage, last printk: Probing EDD (edd=off to disable)... ok

2016-10-13 Thread Ye Xiaolong
On 10/13, Andi Kleen wrote: >Andi Kleen writes: > >Any comments on this? > >I still cannot reproduce the failure unfortunately. > Btw, you can try below commands to reproduce the error on your local host, they will download the necessary images and run QEMU: git

Re: [x86] 811565123a: BUG: kernel hang in early-boot stage, last printk: Probing EDD (edd=off to disable)... ok

2016-10-13 Thread Ye Xiaolong
On 10/13, Andi Kleen wrote: >Andi Kleen writes: > >Any comments on this? > >I still cannot reproduce the failure unfortunately. oh, sorry, missed you mail before, I'll try the tests you mentioned and provide results later. Thanks, Xiaolong > > >> Could you do two tests for

Re: [mm] c4344e8035: WARNING: CPU: 0 PID: 101 at mm/memory.c:303 __tlb_remove_page_size+0x25/0x99

2016-10-12 Thread Ye Xiaolong
--- a/mm/memory.c >+++ b/mm/memory.c >@@ -526,7 +526,11 @@ void free_pgd_range(struct mmu_gather *tlb, > end -= PMD_SIZE; > if (addr > end - 1) > return; >- >+ /* >+ * We add page table cache pages with PAGE_SIZE, >+ * (see pte_free_tlb()), flush the

Re: [lkp] [ipc/sem.c] 0882cba0a0: aim9.shared_memory.ops_per_sec -8.8% regression

2016-10-10 Thread Ye Xiaolong
On 10/09, Manfred Spraul wrote: >Hi, > >On 10/09/2016 09:05 AM, kernel test robot wrote: >>FYI, we noticed a -8.8% regression of aim9.shared_memory.ops_per_sec due to >>commit: >> >>commit 0882cba0a03bca73acd8fab8fb50db04691908e9 ("ipc/sem.c: fix >>complex_count vs. simple op race")

Re: [lkp] [staging] d4f56b47a8: divide error: 0000 [#1] PREEMPT SMP KASAN

2016-09-30 Thread Ye Xiaolong
e_initcall+0x9a/0x12c >> [ 16.814588] [] kernel_init_freeable+0x1b0/0x246 >> [ 16.815180] [] kernel_init+0xc/0x108 >> [ 16.815679] [] ret_from_fork+0x1f/0x40 >> [ 16.816197] [] ? rest_init+0x13c/0x13c >> [ 16.816724] Code: 85 c0 89 c3 74 12 48 c7 c7 64

Re: [lkp] [staging] d4f56b47a8: divide error: 0000 [#1] PREEMPT SMP KASAN

2016-09-29 Thread Ye Xiaolong
On 09/30, Viresh Kumar wrote: >On Fri, Sep 30, 2016 at 7:29 AM, kernel test robot > wrote: >> >> >> FYI, we noticed the following commit: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master >> commit d4f56b47a8fac90b15adfae80a42a2735d6b3213

[LKP] Tips to append base tree info by git-format-patch

2016-09-23 Thread Ye Xiaolong
Hi, Here's a tip for people who've been bothered by messages sent by kbuild bot like below: [auto build test ERROR on net/master] [also build test ERROR on v4.8-rc3 next-20160825] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] It means that

Re: [lkp] [sched/core] 3d26b7622f: BUG: unable to handle kernel NULL pointer dereference at 00000001

2016-09-08 Thread Ye Xiaolong
Hi, cheng hao, On 09/09, chengchao wrote: >Hi, xiaolong > > where can I find the commit 3d26b7622f3bab689696900ffd33c6dd7849d7c2? This is the commit by 0Day bot for your original email patch sent on Sep 05 where both CONFIG_PREEMPT_NONE and CONFIG_PREEMPT_VOLUNTARY will turn the logic on.

  1   2   >