[e1000_netpoll] BUG: sleeping function called from invalid context at kernel/irq/manage.c:110

Greetings, This BUG message can be found in recent kernels as well as v4.4 and linux-stable. It happens when running modprobe netconsole netconsole=@/,$port@$server/ [ 39.937534] 22 Jul 13:30:40 ntpdate[440]: step time server 192.168.1.1 offset -673.833841 sec [ 39.943285]

[e1000_netpoll] BUG: sleeping function called from invalid context at kernel/irq/manage.c:110

Greetings, This BUG message can be found in recent kernels as well as v4.4 and linux-stable. It happens when running modprobe netconsole netconsole=@/,$port@$server/ [ 39.937534] 22 Jul 13:30:40 ntpdate[440]: step time server 192.168.1.1 offset -673.833841 sec [ 39.943285]

Re: [PATCH 2/5] mm: add per-zone lru list stat

Hi Minchan, We find duplicate /proc/vmstat lines showing up in linux-next, which look related to this patch. --- a/mm/vmstat.c +++ b/mm/vmstat.c @@ -921,6 +921,11 @@ int fragmentation_index(struct zone *zone, unsigned int order) const char * const vmstat_text[] = { /* enum

Re: [PATCH 2/5] mm: add per-zone lru list stat

Hi Minchan, We find duplicate /proc/vmstat lines showing up in linux-next, which look related to this patch. --- a/mm/vmstat.c +++ b/mm/vmstat.c @@ -921,6 +921,11 @@ int fragmentation_index(struct zone *zone, unsigned int order) const char * const vmstat_text[] = { /* enum

Re: [kbuild-all] arch/xtensa/include/asm/initialize_mmu.h:55: Error: invalid register 'atomctl' for 'wsr' instruction

Hi Max, On Fri, Jul 22, 2016 at 06:32:28PM +0800, kbuild test robot wrote: Hi, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 47ef4ad2684d380dd6d596140fb79395115c3950 commit:

Re: [kbuild-all] arch/xtensa/include/asm/initialize_mmu.h:55: Error: invalid register 'atomctl' for 'wsr' instruction

Hi Max, On Fri, Jul 22, 2016 at 06:32:28PM +0800, kbuild test robot wrote: Hi, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 47ef4ad2684d380dd6d596140fb79395115c3950 commit:

Re: linux-next: build failure after merge of the pm tree

On Fri, Jul 22, 2016 at 02:08:35PM +0200, Rafael J. Wysocki wrote: On Thursday, July 21, 2016 07:26:28 PM Steve Muckle wrote: On Fri, Jul 22, 2016 at 11:56:20AM +1000, Stephen Rothwell wrote: > Hi Rafael, > > After merging the pm tree, today's linux-next build (arm > multi_v7_defconfig) failed

Re: linux-next: build failure after merge of the pm tree

On Fri, Jul 22, 2016 at 02:08:35PM +0200, Rafael J. Wysocki wrote: On Thursday, July 21, 2016 07:26:28 PM Steve Muckle wrote: On Fri, Jul 22, 2016 at 11:56:20AM +1000, Stephen Rothwell wrote: > Hi Rafael, > > After merging the pm tree, today's linux-next build (arm > multi_v7_defconfig) failed

[gcc-4.4] Re: arch/x86/events/intel/uncore_snbep.o: warning: objtool: snbep_uncore_msr_enable_event()+0x2e: function has unreachable instruction

On Thu, Jul 21, 2016 at 11:06:06AM +0800, Liang, Kan wrote: Hi Fengguang, I located the unreachable instruction which is ud2. This instruction will raise invalid opcode exception. So I think normally it should not be reached. Also ud2 should be generated by compiler, not our codes. It's

[gcc-4.4] Re: arch/x86/events/intel/uncore_snbep.o: warning: objtool: snbep_uncore_msr_enable_event()+0x2e: function has unreachable instruction

On Thu, Jul 21, 2016 at 11:06:06AM +0800, Liang, Kan wrote: Hi Fengguang, I located the unreachable instruction which is ud2. This instruction will raise invalid opcode exception. So I think normally it should not be reached. Also ud2 should be generated by compiler, not our codes. It's

Re: [lkp] [PATCH v2 2/9] hwmon: (core) New hwmon registration API

Hi, [auto build test ERROR on hwmon/hwmon-next] [also build test ERROR on v4.7-rc7 next-20160719] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [lkp] [PATCH v2 2/9] hwmon: (core) New hwmon registration API

Hi, [auto build test ERROR on hwmon/hwmon-next] [also build test ERROR on v4.7-rc7 next-20160719] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [lkp] [PATCH v3 1/3] spi: spidev: create spidev device for all spi slaves.

Hi, [auto build test WARNING on v4.7-rc7] [cannot apply to next-20160719] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Michal-Suchanek/Spidev-usability-patchset-update/20160720-055513

Re: [lkp] [PATCH v3 1/3] spi: spidev: create spidev device for all spi slaves.

Hi, [auto build test WARNING on v4.7-rc7] [cannot apply to next-20160719] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Michal-Suchanek/Spidev-usability-patchset-update/20160720-055513

Re: [lkp] [PART2 PATCH v4 05/11] iommu/amd: Detect and initialize guest vAPIC log

Hi, [auto build test WARNING on iommu/next] [also build test WARNING on v4.7-rc7 next-20160719] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [lkp] [PART2 PATCH v4 05/11] iommu/amd: Detect and initialize guest vAPIC log

Hi, [auto build test WARNING on iommu/next] [also build test WARNING on v4.7-rc7 next-20160719] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [kbuild-all] [PATCH v17 net-next 1/1] hv_sock: introduce Hyper-V Sockets

On Tue, Jul 19, 2016 at 07:52:53PM -0700, David Miller wrote: From: Dexuan Cui Date: Wed, 20 Jul 2016 01:48:18 + From: kbuild test robot [mailto:l...@intel.com] Sent: Wednesday, July 20, 2016 1:10 Hi, [auto build test WARNING on net-next/master] url:

Re: [kbuild-all] [PATCH v17 net-next 1/1] hv_sock: introduce Hyper-V Sockets

On Tue, Jul 19, 2016 at 07:52:53PM -0700, David Miller wrote: From: Dexuan Cui Date: Wed, 20 Jul 2016 01:48:18 + From: kbuild test robot [mailto:l...@intel.com] Sent: Wednesday, July 20, 2016 1:10 Hi, [auto build test WARNING on net-next/master] url:

Re: [kbuild-all] [PATCH v17 net-next 1/1] hv_sock: introduce Hyper-V Sockets

Yes, sorry for the noises! >> net/hv_sock/af_hvsock.o: warning: objtool: hvsock_on_channel_cb()+0x1d: function has unreachable instruction These warnings are all false alarms. Thanks, -- Dexuan ___ kbuild-all mailing list kbuild-...@lists.01.org

Re: [kbuild-all] [PATCH v17 net-next 1/1] hv_sock: introduce Hyper-V Sockets

Yes, sorry for the noises! >> net/hv_sock/af_hvsock.o: warning: objtool: hvsock_on_channel_cb()+0x1d: function has unreachable instruction These warnings are all false alarms. Thanks, -- Dexuan ___ kbuild-all mailing list kbuild-...@lists.01.org

Re: [kbuild-all] security/yama/yama_lsm.o: warning: objtool: report_access()+0x210: function has unreachable instruction

Hi Jann, Sorry please ignore this one -- it looks like false warning from old gcc 4.4 and 4.6 -- we just enabled old compiler tests triggered 10k these warnings.. Thanks, Fengguang On Tue, Jul 19, 2016 at 10:20:05PM +0800, kbuild test robot wrote: tree:

Re: [kbuild-all] security/yama/yama_lsm.o: warning: objtool: report_access()+0x210: function has unreachable instruction

Hi Jann, Sorry please ignore this one -- it looks like false warning from old gcc 4.4 and 4.6 -- we just enabled old compiler tests triggered 10k these warnings.. Thanks, Fengguang On Tue, Jul 19, 2016 at 10:20:05PM +0800, kbuild test robot wrote: tree:

Re: [kbuild-all] drivers/virtio/virtio_balloon.o: warning: objtool: release_pages_balloon()+0x98: function has unreachable instruction

Hi Cornelia, Michael, Sorry please ignore this one -- it looks like false warning from old gcc 4.4 and 4.6 -- we just enabled old compiler tests triggered thousands of these warnings.. Thanks, Fengguang On Wed, Jul 20, 2016 at 01:33:15AM +0800, kbuild test robot wrote: tree:

Re: [kbuild-all] drivers/virtio/virtio_balloon.o: warning: objtool: release_pages_balloon()+0x98: function has unreachable instruction

Hi Cornelia, Michael, Sorry please ignore this one -- it looks like false warning from old gcc 4.4 and 4.6 -- we just enabled old compiler tests triggered thousands of these warnings.. Thanks, Fengguang On Wed, Jul 20, 2016 at 01:33:15AM +0800, kbuild test robot wrote: tree:

Re: scripts/sign-file.c:23:30: fatal error: openssl/opensslv.h: No such file or directory

On Tue, Jul 19, 2016 at 05:09:03PM +0100, David Howells wrote: kbuild test robot wrote: >> scripts/sign-file.c:23:30: fatal error: openssl/opensslv.h: No such file or directory Missing openssl devel packages in your build environment? Oops, will fix it, thank you!

Re: scripts/sign-file.c:23:30: fatal error: openssl/opensslv.h: No such file or directory

On Tue, Jul 19, 2016 at 05:09:03PM +0100, David Howells wrote: kbuild test robot wrote: >> scripts/sign-file.c:23:30: fatal error: openssl/opensslv.h: No such file or directory Missing openssl devel packages in your build environment? Oops, will fix it, thank you! Regards, Fengguang

Re: running "make dtbs" for test builds

On Mon, Jul 18, 2016 at 02:52:32PM +0200, Arnd Bergmann wrote: On Monday, July 18, 2016 8:41:22 PM CEST Fengguang Wu wrote: Hi Arnd, On Mon, Jul 18, 2016 at 02:01:17PM +0200, Arnd Bergmann wrote: >Hi Fengguang, > >I've recently run into a number of cases in which I pulled

Re: running "make dtbs" for test builds

On Mon, Jul 18, 2016 at 02:52:32PM +0200, Arnd Bergmann wrote: On Monday, July 18, 2016 8:41:22 PM CEST Fengguang Wu wrote: Hi Arnd, On Mon, Jul 18, 2016 at 02:01:17PM +0200, Arnd Bergmann wrote: >Hi Fengguang, > >I've recently run into a number of cases in which I pulled

Re: running "make dtbs" for test builds

Hi Arnd, On Mon, Jul 18, 2016 at 02:01:17PM +0200, Arnd Bergmann wrote: Hi Fengguang, I've recently run into a number of cases in which I pulled a branch that was building fine with "make vmlinux", but that failed for "make dtbs", and I wonder if this is something that could be checked by the

Re: running "make dtbs" for test builds

Hi Arnd, On Mon, Jul 18, 2016 at 02:01:17PM +0200, Arnd Bergmann wrote: Hi Fengguang, I've recently run into a number of cases in which I pulled a branch that was building fine with "make vmlinux", but that failed for "make dtbs", and I wonder if this is something that could be checked by the

Re: running "make dtbs" for test builds

Hi Arnd, On Mon, Jul 18, 2016 at 02:01:17PM +0200, Arnd Bergmann wrote: Hi Fengguang, I've recently run into a number of cases in which I pulled a branch that was building fine with "make vmlinux", but that failed for "make dtbs", and I wonder if this is something that could be checked by the

Re: running "make dtbs" for test builds

Hi Arnd, On Mon, Jul 18, 2016 at 02:01:17PM +0200, Arnd Bergmann wrote: Hi Fengguang, I've recently run into a number of cases in which I pulled a branch that was building fine with "make vmlinux", but that failed for "make dtbs", and I wonder if this is something that could be checked by the

Re: [PATCH v2 0/5] firmware: add SmPL grammar to avoid issues

On Thu, Jul 14, 2016 at 05:08:12AM +0200, Luis R. Rodriguez wrote: On Thu, Jul 14, 2016 at 10:23:36AM +0800, Fengguang Wu wrote: On Thu, Jul 14, 2016 at 04:15:01AM +0200, Luis R. Rodriguez wrote: >On Thu, Jul 14, 2016 at 07:52:07AM +0800, Fengguang Wu wrote: >>Hi Luis, >> >>

Re: [PATCH v2 0/5] firmware: add SmPL grammar to avoid issues

On Thu, Jul 14, 2016 at 05:08:12AM +0200, Luis R. Rodriguez wrote: On Thu, Jul 14, 2016 at 10:23:36AM +0800, Fengguang Wu wrote: On Thu, Jul 14, 2016 at 04:15:01AM +0200, Luis R. Rodriguez wrote: >On Thu, Jul 14, 2016 at 07:52:07AM +0800, Fengguang Wu wrote: >>Hi Luis, >> >>

Re: [PATCH v2 0/5] firmware: add SmPL grammar to avoid issues

On Thu, Jul 14, 2016 at 04:15:01AM +0200, Luis R. Rodriguez wrote: On Thu, Jul 14, 2016 at 07:52:07AM +0800, Fengguang Wu wrote: Hi Luis, On Thu, Jul 07, 2016 at 02:56:44AM +0200, Luis R. Rodriguez wrote: >On Thu, Jun 16, 2016 at 03:54:16PM -0700, Luis R. Rodriguez wrote: >>The fir

Re: [PATCH v2 0/5] firmware: add SmPL grammar to avoid issues

On Thu, Jul 14, 2016 at 04:15:01AM +0200, Luis R. Rodriguez wrote: On Thu, Jul 14, 2016 at 07:52:07AM +0800, Fengguang Wu wrote: Hi Luis, On Thu, Jul 07, 2016 at 02:56:44AM +0200, Luis R. Rodriguez wrote: >On Thu, Jun 16, 2016 at 03:54:16PM -0700, Luis R. Rodriguez wrote: >>The fir

Re: [PATCH v2 0/5] firmware: add SmPL grammar to avoid issues

Hi Luis, On Thu, Jul 07, 2016 at 02:56:44AM +0200, Luis R. Rodriguez wrote: On Thu, Jun 16, 2016 at 03:54:16PM -0700, Luis R. Rodriguez wrote: The firmware API has had some issues a while ago, some of this is not well documented, and its still hard to grasp. This documents some of these

Re: [PATCH v2 0/5] firmware: add SmPL grammar to avoid issues

Hi Luis, On Thu, Jul 07, 2016 at 02:56:44AM +0200, Luis R. Rodriguez wrote: On Thu, Jun 16, 2016 at 03:54:16PM -0700, Luis R. Rodriguez wrote: The firmware API has had some issues a while ago, some of this is not well documented, and its still hard to grasp. This documents some of these

Re: [PATCH net-next 3/3] bpf: avoid stack copy and use skb ctx for event output

Hi Daniel, On Wed, Jul 13, 2016 at 01:45:47AM +0200, Daniel Borkmann wrote: On 07/13/2016 01:25 AM, kbuild test robot wrote: Hi, [auto build test WARNING on net-next/master] url: https://github.com/0day-ci/linux/commits/Daniel-Borkmann/BPF-event-output-helper-improvements/20160713-065944

Re: [PATCH net-next 3/3] bpf: avoid stack copy and use skb ctx for event output

Hi Daniel, On Wed, Jul 13, 2016 at 01:45:47AM +0200, Daniel Borkmann wrote: On 07/13/2016 01:25 AM, kbuild test robot wrote: Hi, [auto build test WARNING on net-next/master] url: https://github.com/0day-ci/linux/commits/Daniel-Borkmann/BPF-event-output-helper-improvements/20160713-065944

[PATCH] chardev: add missing line break in pr_warn

RNEL|__GFP_COMP|__GFP_NOTRACK) Reported-by: Philip Li <philip...@intel.com> Signed-off-by: Fengguang Wu <fengguang...@intel.com> --- fs/char_dev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/char_dev.c b/fs/char_dev.c index 687471d..6edd825 100644 --

[PATCH] chardev: add missing line break in pr_warn

RNEL|__GFP_COMP|__GFP_NOTRACK) Reported-by: Philip Li Signed-off-by: Fengguang Wu --- fs/char_dev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/char_dev.c b/fs/char_dev.c index 687471d..6edd825 100644 --- a/fs/char_dev.c +++ b/fs/char_dev.c @@ -92,7 +92,7 @@ __register_chrdev

Re: [kbuild-all] [PATCH 3/7] security, overlayfs: Provide security hook for copy up of xattrs for overlay file

On Mon, Jul 11, 2016 at 09:40:04AM -0400, Vivek Goyal wrote: On Sat, Jul 09, 2016 at 01:41:38AM +0800, kbuild test robot wrote: Hi, [auto build test ERROR on next-20160708] [also build test ERROR on v4.7-rc6] [cannot apply to pcmoore-selinux/next security/next v4.7-rc6 v4.7-rc5 v4.7-rc4] [if

Re: [kbuild-all] [PATCH 3/7] security, overlayfs: Provide security hook for copy up of xattrs for overlay file

On Mon, Jul 11, 2016 at 09:40:04AM -0400, Vivek Goyal wrote: On Sat, Jul 09, 2016 at 01:41:38AM +0800, kbuild test robot wrote: Hi, [auto build test ERROR on next-20160708] [also build test ERROR on v4.7-rc6] [cannot apply to pcmoore-selinux/next security/next v4.7-rc6 v4.7-rc5 v4.7-rc4] [if

Re: ERROR: "bad_dma_ops" [sound/core/snd-pcm.ko] undefined!

> > config: m32r-allmodconfig (attached as .config) > > compiler: m32r-linux-gcc (GCC) 4.9.0 > > You are using 4.9.0 ? If you want you can get 5.3.0 from: > http://chat.vectorindia.net/crosstool/x86_64/5.3.0/m32r-linux.tar.xz Glad to know that! Philip will help pull the new version. Thanks,

Re: ERROR: "bad_dma_ops" [sound/core/snd-pcm.ko] undefined!

> > config: m32r-allmodconfig (attached as .config) > > compiler: m32r-linux-gcc (GCC) 4.9.0 > > You are using 4.9.0 ? If you want you can get 5.3.0 from: > http://chat.vectorindia.net/crosstool/x86_64/5.3.0/m32r-linux.tar.xz Glad to know that! Philip will help pull the new version. Thanks,

Re: Stable -rc git trees and email headers

On Mon, Jun 20, 2016 at 11:52:14AM +0200, Jiri Slaby wrote: > On 06/20/2016, 11:39 AM, Fengguang Wu wrote: > >> git://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux-stable.git > > > > It looks already in the testing pipeline. :) > > Oh, and it's there for

Re: Stable -rc git trees and email headers

On Mon, Jun 20, 2016 at 11:52:14AM +0200, Jiri Slaby wrote: > On 06/20/2016, 11:39 AM, Fengguang Wu wrote: > >> git://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux-stable.git > > > > It looks already in the testing pipeline. :) > > Oh, and it's there for

Re: Stable -rc git trees and email headers

Hi Jiri, On Mon, Jun 20, 2016 at 10:39:37AM +0200, Jiri Slaby wrote: > On 06/18/2016, 07:22 AM, Fengguang Wu wrote: > > Hi Greg, > > > > On Fri, Jun 17, 2016 at 08:16:20PM -0700, Greg KH wrote: > >> Hi, > >> > >> I've finally gotte

Re: Stable -rc git trees and email headers

Hi Jiri, On Mon, Jun 20, 2016 at 10:39:37AM +0200, Jiri Slaby wrote: > On 06/18/2016, 07:22 AM, Fengguang Wu wrote: > > Hi Greg, > > > > On Fri, Jun 17, 2016 at 08:16:20PM -0700, Greg KH wrote: > >> Hi, > >> > >> I've finally gotte

Re: Stable -rc git trees and email headers

Hi Greg, On Fri, Jun 17, 2016 at 08:16:20PM -0700, Greg KH wrote: > Hi, > > I've finally gotten off my butt and made my quilt trees of patches into > a "semi-proper" git tree to make it easier for people to test them. > > I'm now pushing the patches I accept into the stable queues into the git

Re: Stable -rc git trees and email headers

Hi Greg, On Fri, Jun 17, 2016 at 08:16:20PM -0700, Greg KH wrote: > Hi, > > I've finally gotten off my butt and made my quilt trees of patches into > a "semi-proper" git tree to make it easier for people to test them. > > I'm now pushing the patches I accept into the stable queues into the git

Re: [Revert "ppdev] 1701f68040: genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000080 (goldfish_pdev_bus)

Hi Alan, On Tue, May 31, 2016 at 11:11:55AM +0100, Alan wrote: > On Sun, 29 May 2016 23:28:41 +0800 > kernel test robot wrote: > > > Greetings, > > > > 0day kernel testing robot got the below dmesg and the first bad > > commit is > > > >

Re: [Revert "ppdev] 1701f68040: genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000080 (goldfish_pdev_bus)

Hi Alan, On Tue, May 31, 2016 at 11:11:55AM +0100, Alan wrote: > On Sun, 29 May 2016 23:28:41 +0800 > kernel test robot wrote: > > > Greetings, > > > > 0day kernel testing robot got the below dmesg and the first bad > > commit is > > > >

Re: [Revert "ppdev] 1701f68040: genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000080 (goldfish_pdev_bus)

On Sun, May 29, 2016 at 09:25:28AM -0700, Linus Torvalds wrote: > On Sun, May 29, 2016 at 8:28 AM, kernel test robot > wrote: > > > > 0day kernel testing robot got the below dmesg and the first bad commit is > > This bisection seems unlikely. > > I *think* what is going

Re: [Revert "ppdev] 1701f68040: genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000080 (goldfish_pdev_bus)

On Sun, May 29, 2016 at 09:25:28AM -0700, Linus Torvalds wrote: > On Sun, May 29, 2016 at 8:28 AM, kernel test robot > wrote: > > > > 0day kernel testing robot got the below dmesg and the first bad commit is > > This bisection seems unlikely. > > I *think* what is going on is that the previous

Re: [i2c: dev] d6760b14d4: BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff8800091b4c49

On Sat, May 28, 2016 at 09:32:17AM +0200, Wolfram Sang wrote: > > > There will be simple boot tests quickly after the compile tests. > > However boot tests typically need more time to be detected, bisected > > and especially manual checked. We are yet to automate more boot error > > reports. > >

Re: [i2c: dev] d6760b14d4: BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff8800091b4c49

On Sat, May 28, 2016 at 09:32:17AM +0200, Wolfram Sang wrote: > > > There will be simple boot tests quickly after the compile tests. > > However boot tests typically need more time to be detected, bisected > > and especially manual checked. We are yet to automate more boot error > > reports. > >

Re: [i2c: dev] d6760b14d4: BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff8800091b4c49

On Sat, May 28, 2016 at 09:12:34AM +0200, Wolfram Sang wrote: > > 0day kernel testing robot got the below dmesg and the first bad commit is > > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > > So, I got a success message from buildbot "[wsa:i2c/for-next] >

Re: [i2c: dev] d6760b14d4: BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff8800091b4c49

On Sat, May 28, 2016 at 09:12:34AM +0200, Wolfram Sang wrote: > > 0day kernel testing robot got the below dmesg and the first bad commit is > > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > > So, I got a success message from buildbot "[wsa:i2c/for-next] >

Re: [x86/cpufeature] 7b5e74e637: BUG: unable to handle kernel paging request at 6b636170

Hi Dave, You are right -- this is a bad bisect. > > [1.914984] random: trinity urandom read with 25 bits of entropy > available > > [8.542178] random: nonblocking pool is initialized > > [ 11.939833] sock: process `trinity-main' is using obsolete setsockopt > SO_BSDCOMPAT > > [

Re: [x86/cpufeature] 7b5e74e637: BUG: unable to handle kernel paging request at 6b636170

Hi Dave, You are right -- this is a bad bisect. > > [1.914984] random: trinity urandom read with 25 bits of entropy > available > > [8.542178] random: nonblocking pool is initialized > > [ 11.939833] sock: process `trinity-main' is using obsolete setsockopt > SO_BSDCOMPAT > > [

Re: [RFC][PATCH 00/31] implement atomic_fetch_$op

On Fri, Apr 22, 2016 at 09:35:06PM +0300, Kalle Valo wrote: > Fengguang Wu <fengguang...@intel.com> writes: > > >> OK, weirdness. I received the "BUILD SUCCESS" email without any arm64 > >> builds listed, but I just received a build bot email telling me

Re: [RFC][PATCH 00/31] implement atomic_fetch_$op

On Fri, Apr 22, 2016 at 09:35:06PM +0300, Kalle Valo wrote: > Fengguang Wu writes: > > >> OK, weirdness. I received the "BUILD SUCCESS" email without any arm64 > >> builds listed, but I just received a build bot email telling me the > >> arm64 build was

Re: [RFC][PATCH 00/31] implement atomic_fetch_$op

On Fri, Apr 22, 2016 at 04:23:03PM +0200, Peter Zijlstra wrote: > On Fri, Apr 22, 2016 at 08:56:56PM +0800, Fengguang Wu wrote: > > I'll add arm64-defconfig to P1 list to improve its coverage. > > Thanks; any more architectures missing from P1? Good question! Just double checke

Re: [RFC][PATCH 00/31] implement atomic_fetch_$op

On Fri, Apr 22, 2016 at 04:23:03PM +0200, Peter Zijlstra wrote: > On Fri, Apr 22, 2016 at 08:56:56PM +0800, Fengguang Wu wrote: > > I'll add arm64-defconfig to P1 list to improve its coverage. > > Thanks; any more architectures missing from P1? Good question! Just double checke

Re: [RFC][PATCH 00/31] implement atomic_fetch_$op

On Fri, Apr 22, 2016 at 11:44:55AM +0200, Peter Zijlstra wrote: > On Fri, Apr 22, 2016 at 11:04:13AM +0200, Peter Zijlstra wrote: > > The one that I did not do was ARMv8.1-LSE and I was hoping Will would help > > out > > with that. Also, it looks like the 0-day built bot does not do arm64 builds,

Re: [RFC][PATCH 00/31] implement atomic_fetch_$op

On Fri, Apr 22, 2016 at 11:44:55AM +0200, Peter Zijlstra wrote: > On Fri, Apr 22, 2016 at 11:04:13AM +0200, Peter Zijlstra wrote: > > The one that I did not do was ARMv8.1-LSE and I was hoping Will would help > > out > > with that. Also, it looks like the 0-day built bot does not do arm64 builds,

Re: [kbuild-all] mipsel-linux-gnu-gcc: error: unrecognized command line option '-mcompact-branches=optimal'

Hi Ralf, On Wed, Apr 20, 2016 at 03:30:21PM +0200, Ralf Baechle wrote: > On Wed, Apr 20, 2016 at 01:44:28PM +0800, kbuild test robot wrote: > > > FYI, the error/warning still remains. > > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > master > > head:

Re: [kbuild-all] mipsel-linux-gnu-gcc: error: unrecognized command line option '-mcompact-branches=optimal'

Hi Ralf, On Wed, Apr 20, 2016 at 03:30:21PM +0200, Ralf Baechle wrote: > On Wed, Apr 20, 2016 at 01:44:28PM +0800, kbuild test robot wrote: > > > FYI, the error/warning still remains. > > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > master > > head:

Re: [PATCH] bpf: avoid warning for wrong pointer cast

Hi Alexei, On Sat, Apr 16, 2016 at 05:47:42PM -0700, Alexei Starovoitov wrote: > On Sat, Apr 16, 2016 at 10:29:33PM +0200, Arnd Bergmann wrote: > > Two new functions in bpf contain a cast from a 'u64' to a > > pointer. This works on 64-bit architectures but causes a warning > > on all 32-bit

Re: [PATCH] bpf: avoid warning for wrong pointer cast

Hi Alexei, On Sat, Apr 16, 2016 at 05:47:42PM -0700, Alexei Starovoitov wrote: > On Sat, Apr 16, 2016 at 10:29:33PM +0200, Arnd Bergmann wrote: > > Two new functions in bpf contain a cast from a 'u64' to a > > pointer. This works on 64-bit architectures but causes a warning > > on all 32-bit

Re: [kbuild-all] arch/xtensa/include/asm/processor.h:227: Error: unknown opcode or format name 'wer'

Sorry Filippov! Philip, how about giving more priority to this issue? Thanks, Fengguang On Mon, Apr 18, 2016 at 06:52:57PM +0300, Max Filippov wrote: > Hi Fengguang, > > On Mon, Apr 18, 2016 at 6:29 PM, kbuild test robot > wrote: > > FYI, the error/warning still

Re: [kbuild-all] arch/xtensa/include/asm/processor.h:227: Error: unknown opcode or format name 'wer'

Sorry Filippov! Philip, how about giving more priority to this issue? Thanks, Fengguang On Mon, Apr 18, 2016 at 06:52:57PM +0300, Max Filippov wrote: > Hi Fengguang, > > On Mon, Apr 18, 2016 at 6:29 PM, kbuild test robot > wrote: > > FYI, the error/warning still remains. > > > > tree:

Re: [kbuild-all] arch/xtensa/include/asm/initialize_mmu.h:55: Error: invalid register 'atomctl' for 'wsr' instruction

Hi Max, Thank you for the info! CC Philip for following this issue. Thanks, Fengguang On Sun, Mar 20, 2016 at 02:54:54PM +0300, Max Filippov wrote: > Hi Fengguang, > > On Sun, Mar 20, 2016 at 8:34 AM, kbuild test robot > wrote: > > Hi Max, > > > > FYI, the

Re: [kbuild-all] arch/xtensa/include/asm/initialize_mmu.h:55: Error: invalid register 'atomctl' for 'wsr' instruction

Hi Max, Thank you for the info! CC Philip for following this issue. Thanks, Fengguang On Sun, Mar 20, 2016 at 02:54:54PM +0300, Max Filippov wrote: > Hi Fengguang, > > On Sun, Mar 20, 2016 at 8:34 AM, kbuild test robot > wrote: > > Hi Max, > > > > FYI, the error/warning still remains. > >

[PATCH] microblaze/PCI: export isa_io_base to fix link errors

. ERROR: "isa_io_base" [drivers/scsi/qla2xxx/qla2xxx.ko] undefined! ERROR: "isa_io_base" [drivers/scsi/ppa.ko] undefined! Signed-off-by: Fengguang Wu <fengguang...@intel.com> --- arch/microblaze/pci/pci-common.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/a

[PATCH] microblaze/PCI: export isa_io_base to fix link errors

. ERROR: "isa_io_base" [drivers/scsi/qla2xxx/qla2xxx.ko] undefined! ERROR: "isa_io_base" [drivers/scsi/ppa.ko] undefined! Signed-off-by: Fengguang Wu --- arch/microblaze/pci/pci-common.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/microblaze/pci/pci-common.c b/

Re: [kbuild-all] kernel/irq/irqdesc.c:206:2: error: array index in initializer exceeds array bounds

Hi Thomas, On Mon, Mar 14, 2016 at 08:53:55AM +0100, Thomas Gleixner wrote: > Fenguang, > > On Mon, 14 Mar 2016, kbuild test robot wrote: > > > Hi Thomas, > > > > FYI, the error/warning still remains. > > > make.cross ARCH=m68k > > >arch/m68k/include/asm/irq.h:25:17: error:

Re: [kbuild-all] kernel/irq/irqdesc.c:206:2: error: array index in initializer exceeds array bounds

Hi Thomas, On Mon, Mar 14, 2016 at 08:53:55AM +0100, Thomas Gleixner wrote: > Fenguang, > > On Mon, 14 Mar 2016, kbuild test robot wrote: > > > Hi Thomas, > > > > FYI, the error/warning still remains. > > > make.cross ARCH=m68k > > >arch/m68k/include/asm/irq.h:25:17: error:

[xtensa] arch/xtensa/include/asm/processor.h:14:26: fatal error: variant/core.h: No such file or directory

Hi Chris, FYI, xtensa has an error that happen in the below 2 configs: xtensa-audio_kc705_defconfig (attached as .config) xtensa-smp_lx200_defconfig It's too old to be bisect friendly. It'd be great if can be fixed. In file included from

[xtensa] arch/xtensa/include/asm/processor.h:14:26: fatal error: variant/core.h: No such file or directory

Hi Chris, FYI, xtensa has an error that happen in the below 2 configs: xtensa-audio_kc705_defconfig (attached as .config) xtensa-smp_lx200_defconfig It's too old to be bisect friendly. It'd be great if can be fixed. In file included from

[mips] ERROR: "isa_io_base" [drivers/video/fbdev/sm712fb.ko] undefined!

Hi Michal, microblaze allmodconfig triggers lots of below errors in build tests, shall we EXPORT_SYMBOL(isa_io_base)? ERROR: "isa_io_base" [sound/pci/vx222/snd-vx222.ko] undefined! ERROR: "isa_io_base" [sound/pci/trident/snd-trident.ko] undefined! ERROR: "isa_io_base"

[mips] ERROR: "isa_io_base" [drivers/video/fbdev/sm712fb.ko] undefined!

Hi Michal, microblaze allmodconfig triggers lots of below errors in build tests, shall we EXPORT_SYMBOL(isa_io_base)? ERROR: "isa_io_base" [sound/pci/vx222/snd-vx222.ko] undefined! ERROR: "isa_io_base" [sound/pci/trident/snd-trident.ko] undefined! ERROR: "isa_io_base"

Re: [kbuild-all] arch/mips/vdso/elf.S:1:0: error: '-march=r3900' requires '-mfp32'

Hi Alex, This error has been there for some time. Shall I stop reporting it by adding this error to blacklist? Thanks, Fengguang On Sun, Mar 13, 2016 at 05:08:45PM +0800, kbuild test robot wrote: > Hi Alex, > > FYI, the error/warning still remains. > > tree:

Re: [kbuild-all] arch/mips/vdso/elf.S:1:0: error: '-march=r3900' requires '-mfp32'

Hi Alex, This error has been there for some time. Shall I stop reporting it by adding this error to blacklist? Thanks, Fengguang On Sun, Mar 13, 2016 at 05:08:45PM +0800, kbuild test robot wrote: > Hi Alex, > > FYI, the error/warning still remains. > > tree:

Re: [kbuild-all] drivers/vhost/vhost.c:718:3: error: call to '__compiletime_assert_718' declared with attribute error: BUILD_BUG_ON failed: __alignof__ *vq->avail > VRING_AVAIL_ALIGN_SIZE

Hi Michael, Sorry for the delay! I blacklisted it just now. Fengguang On Sun, Mar 13, 2016 at 04:57:26PM +0200, Michael S. Tsirkin wrote: > On Thu, Mar 10, 2016 at 08:49:24AM +0800, Fengguang Wu wrote: > > Hi Michael, > > > > On Sun, Mar 06, 2016 at 10:37:07AM +0200, Mic

Re: [kbuild-all] drivers/vhost/vhost.c:718:3: error: call to '__compiletime_assert_718' declared with attribute error: BUILD_BUG_ON failed: __alignof__ *vq->avail > VRING_AVAIL_ALIGN_SIZE

Hi Michael, Sorry for the delay! I blacklisted it just now. Fengguang On Sun, Mar 13, 2016 at 04:57:26PM +0200, Michael S. Tsirkin wrote: > On Thu, Mar 10, 2016 at 08:49:24AM +0800, Fengguang Wu wrote: > > Hi Michael, > > > > On Sun, Mar 06, 2016 at 10:37:07AM +0200, Mic

Re: [kbuild-all] drivers/vhost/vhost.c:718:3: error: call to '__compiletime_assert_718' declared with attribute error: BUILD_BUG_ON failed: __alignof__ *vq->avail > VRING_AVAIL_ALIGN_SIZE

Hi Michael, On Sun, Mar 06, 2016 at 10:37:07AM +0200, Michael S. Tsirkin wrote: > I keep seeing these errors. Any openrisc/gcc/kbuild people > interested in looking into this? Sorry, currently the buildbot is running old gcc 4.5.1 cross compiler for openrisc:

Re: [kbuild-all] drivers/vhost/vhost.c:718:3: error: call to '__compiletime_assert_718' declared with attribute error: BUILD_BUG_ON failed: __alignof__ *vq->avail > VRING_AVAIL_ALIGN_SIZE

Hi Michael, On Sun, Mar 06, 2016 at 10:37:07AM +0200, Michael S. Tsirkin wrote: > I keep seeing these errors. Any openrisc/gcc/kbuild people > interested in looking into this? Sorry, currently the buildbot is running old gcc 4.5.1 cross compiler for openrisc:

Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

On Tue, Mar 01, 2016 at 02:15:27PM +1100, Michael Ellerman wrote: > On Tue, 2016-03-01 at 10:48 +0800, Fengguang Wu wrote: > > On Tue, Mar 01, 2016 at 10:06:19AM +0800, Fengguang Wu wrote: > > > Hi Geert, > > > > > > > > make.cross ARCH=xtensa

Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

On Tue, Mar 01, 2016 at 02:15:27PM +1100, Michael Ellerman wrote: > On Tue, 2016-03-01 at 10:48 +0800, Fengguang Wu wrote: > > On Tue, Mar 01, 2016 at 10:06:19AM +0800, Fengguang Wu wrote: > > > Hi Geert, > > > > > > > > make.cross ARCH=xtensa

Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

On Tue, Mar 01, 2016 at 10:06:19AM +0800, Fengguang Wu wrote: > Hi Geert, > > > > make.cross ARCH=xtensa > > > > > > All errors (new ones prefixed by >>): > > > > > >>> Invalid CPU Type - valid names are: alpha, arm, x86, ia6

Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

On Tue, Mar 01, 2016 at 10:06:19AM +0800, Fengguang Wu wrote: > Hi Geert, > > > > make.cross ARCH=xtensa > > > > > > All errors (new ones prefixed by >>): > > > > > >>> Invalid CPU Type - valid names are: alpha, arm, x86, ia6

Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

On Sun, Feb 28, 2016 at 10:24:42AM +0100, Thomas Gleixner wrote: > On Sun, 28 Feb 2016, kbuild test robot wrote: > > > Hi Thomas, > > > > FYI, the error/warning still remains. > > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > master > > head:

Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

On Sun, Feb 28, 2016 at 10:24:42AM +0100, Thomas Gleixner wrote: > On Sun, 28 Feb 2016, kbuild test robot wrote: > > > Hi Thomas, > > > > FYI, the error/warning still remains. > > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > master > > head:

Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

Hi Geert, > > make.cross ARCH=xtensa > > > > All errors (new ones prefixed by >>): > > > >>> Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, > >>> microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, > >>> blackfin, avr32, nds32, or1k > >Usage:

Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

Hi Geert, > > make.cross ARCH=xtensa > > > > All errors (new ones prefixed by >>): > > > >>> Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, > >>> microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, > >>> blackfin, avr32, nds32, or1k > >Usage:

Re: [RFC/PATCH 1/1] format-patch: add an option to record base tree info

On Tue, Feb 23, 2016 at 10:30:04PM -0800, Junio C Hamano wrote: > Fengguang Wu <fengguang...@intel.com> writes: > > > The necessary lines for the robot are > > > > base commit: > > base patch-id: > > or > > base tree-id: &

Re: [RFC/PATCH 1/1] format-patch: add an option to record base tree info

On Tue, Feb 23, 2016 at 10:30:04PM -0800, Junio C Hamano wrote: > Fengguang Wu writes: > > > The necessary lines for the robot are > > > > base commit: > > base patch-id: > > or > > base tree-id: > > base patch-id:

<    3   4   5   6   7   8   9   10   11   12   >