* Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
From: Uwe Kleine-König @ 2016-02-15 9:14 UTC (permalink / raw)
To: Russell King - ARM Linux
Cc: linux-arm-kernel, Greg Kroah-Hartman, linux-next, linux-kernel,
Guenter Roeck
In-Reply-To: <20160215085818.GC10826@n2100.arm.linux.org.uk>
Hello Russell,
On Mon, Feb 15, 2016 at 08:58:18AM +0000, Russell King - ARM Linux wrote:
> On Mon, Feb 15, 2016 at 09:17:50AM +0100, Uwe Kleine-König wrote:
> > On Sun, Feb 14, 2016 at 08:07:55PM +0000, Russell King - ARM Linux wrote:
> > > On Sun, Feb 14, 2016 at 08:55:01PM +0100, Uwe Kleine-König wrote:
> > > > So the unexpected abnormality here is that even though this device is
> > > > instantiated by dt, the driver doesn't provide any compatibles.
> > > > Either my expectation is wrong, then 67d02a1bbb33455 should be reverted
> > >
> > > Your expectation is wrong. AMBA primecell devices have hardware IDs
> > > and are matched to their drivers by those IDs. Just like PCI.
> >
> > pci devices don't appear in dt, do they? I don't see the connection
> > between amba devices and platform devices, see my other mail in this
> > thread for some more details.
>
> They both have hardware IDs, and they are both matched via those hardware
> IDs.
I changed platform_match which is about matching by dt compatible, acpi
and/or device name. I don't see how this can affect an amba device given
they match to a driver by a hardware id.
> Your change has introduced a regression and is therefore wrong.
I'd like to understand though why and how my commit is wrong to be able
to fix it instead of getting it reverted.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
^ permalink raw reply
* next-20160215 build: 3 failures 14 warnings (next-20160215)
From: Build bot for Mark Brown @ 2016-02-15 9:13 UTC (permalink / raw)
To: kernel-build-reports, linaro-kernel, linux-next
Tree/Branch: next-20160215
Git describe: next-20160215
Commit: 2625f908fc Add linux-next specific files for 20160215
Build Time: 74 min 43 sec
Passed: 6 / 9 ( 66.67 %)
Failed: 3 / 9 ( 33.33 %)
Errors: 11
Warnings: 14
Section Mismatches: 1
Failed defconfigs:
arm64-allmodconfig
arm64-defconfig
Errors:
arm64-allmodconfig
ERROR: "msi_create_irq_domain" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "irq_chip_mask_parent" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "free_msi_entry" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "msi_domain_alloc_irqs" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "of_msi_get_domain" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "irq_chip_eoi_parent" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "msi_domain_set_affinity" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "msi_get_domain_info" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "msi_domain_free_irqs" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "alloc_msi_entry" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "irq_chip_unmask_parent" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
-------------------------------------------------------------------------------
defconfigs with issues (other than build errors):
6 warnings 2 mismatches : arm64-allmodconfig
4 warnings 0 mismatches : arm-multi_v7_defconfig
7 warnings 0 mismatches : arm-allmodconfig
6 warnings 0 mismatches : arm64-defconfig
-------------------------------------------------------------------------------
Errors summary: 11
1 ERROR: "of_msi_get_domain" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
1 ERROR: "msi_get_domain_info" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
1 ERROR: "msi_domain_set_affinity" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
1 ERROR: "msi_domain_free_irqs" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
1 ERROR: "msi_domain_alloc_irqs" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
1 ERROR: "msi_create_irq_domain" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
1 ERROR: "irq_chip_unmask_parent" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
1 ERROR: "irq_chip_mask_parent" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
1 ERROR: "irq_chip_eoi_parent" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
1 ERROR: "free_msi_entry" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
1 ERROR: "alloc_msi_entry" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
Warnings Summary: 14
4 ../include/linux/kern_levels.h:4:18: warning: field width specifier '*' expects argument of type 'int', but argument 2 has type 'long unsigned int' [-Wformat=]
2 ../net/ipv4/igmp.c:1665:14: warning: unused variable 'net' [-Wunused-variable]
2 ../net/ipv4/igmp.c:1646:14: warning: unused variable 'net' [-Wunused-variable]
2 ../net/ipv4/igmp.c:1319:14: warning: unused variable 'net' [-Wunused-variable]
2 ../net/ipv4/igmp.c:1227:14: warning: unused variable 'net' [-Wunused-variable]
2 ../include/linux/kernel.h:754:17: warning: comparison of distinct pointer types lacks a cast
2 ../drivers/spi/spi.c:2279:9: warning: format '%i' expects argument of type 'int', but argument 4 has type 'size_t {aka long unsigned int}' [-Wformat=]
1 ../lib/lz4/lz4hc_compress.c:514:1: warning: the frame size of 1472 bytes is larger than 1024 bytes [-Wframe-larger-than=]
1 ../include/asm-generic/div64.h:224:22: warning: passing argument 1 of '__div64_32' from incompatible pointer type [-Wincompatible-pointer-types]
1 ../include/asm-generic/div64.h:220:25: warning: right shift count >= width of type [-Wshift-count-overflow]
1 ../include/asm-generic/div64.h:207:28: warning: comparison of distinct pointer types lacks a cast
1 ../drivers/ntb/test/ntb_perf.c:214:14: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
1 ../drivers/ntb/test/ntb_perf.c:213:10: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
1 ../drivers/mtd/chips/cfi_cmdset_0020.c:651:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
Section Mismatch Summary: 1
2 WARNING: drivers/staging/fsl-mc/bus/mc-bus-driver.o(.init.text+0x198): Section mismatch in reference from the function init_module() to the function .exit.text:fsl_mc_allocator_driver_exit()
===============================================================================
Detailed per-defconfig build reports below:
-------------------------------------------------------------------------------
arm64-allmodconfig : FAIL, 11 errors, 6 warnings, 2 section mismatches
Errors:
ERROR: "msi_create_irq_domain" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "irq_chip_mask_parent" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "free_msi_entry" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "msi_domain_alloc_irqs" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "of_msi_get_domain" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "irq_chip_eoi_parent" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "msi_domain_set_affinity" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "msi_get_domain_info" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "msi_domain_free_irqs" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "alloc_msi_entry" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
ERROR: "irq_chip_unmask_parent" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
Warnings:
../include/linux/kern_levels.h:4:18: warning: field width specifier '*' expects argument of type 'int', but argument 2 has type 'long unsigned int' [-Wformat=]
../include/linux/kern_levels.h:4:18: warning: field width specifier '*' expects argument of type 'int', but argument 2 has type 'long unsigned int' [-Wformat=]
../include/linux/kern_levels.h:4:18: warning: field width specifier '*' expects argument of type 'int', but argument 2 has type 'long unsigned int' [-Wformat=]
../include/linux/kern_levels.h:4:18: warning: field width specifier '*' expects argument of type 'int', but argument 2 has type 'long unsigned int' [-Wformat=]
../drivers/spi/spi.c:2279:9: warning: format '%i' expects argument of type 'int', but argument 4 has type 'size_t {aka long unsigned int}' [-Wformat=]
../include/linux/kernel.h:754:17: warning: comparison of distinct pointer types lacks a cast
Section Mismatches:
WARNING: drivers/staging/fsl-mc/bus/mc-bus-driver.o(.init.text+0x198): Section mismatch in reference from the function init_module() to the function .exit.text:fsl_mc_allocator_driver_exit()
WARNING: drivers/staging/fsl-mc/bus/mc-bus-driver.o(.init.text+0x198): Section mismatch in reference from the function init_module() to the function .exit.text:fsl_mc_allocator_driver_exit()
-------------------------------------------------------------------------------
arm-multi_v7_defconfig : PASS, 0 errors, 4 warnings, 0 section mismatches
Warnings:
../net/ipv4/igmp.c:1227:14: warning: unused variable 'net' [-Wunused-variable]
../net/ipv4/igmp.c:1319:14: warning: unused variable 'net' [-Wunused-variable]
../net/ipv4/igmp.c:1646:14: warning: unused variable 'net' [-Wunused-variable]
../net/ipv4/igmp.c:1665:14: warning: unused variable 'net' [-Wunused-variable]
-------------------------------------------------------------------------------
arm-allmodconfig : PASS, 0 errors, 7 warnings, 0 section mismatches
Warnings:
../lib/lz4/lz4hc_compress.c:514:1: warning: the frame size of 1472 bytes is larger than 1024 bytes [-Wframe-larger-than=]
../include/asm-generic/div64.h:207:28: warning: comparison of distinct pointer types lacks a cast
../include/asm-generic/div64.h:220:25: warning: right shift count >= width of type [-Wshift-count-overflow]
../include/asm-generic/div64.h:224:22: warning: passing argument 1 of '__div64_32' from incompatible pointer type [-Wincompatible-pointer-types]
../drivers/mtd/chips/cfi_cmdset_0020.c:651:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
../drivers/ntb/test/ntb_perf.c:213:10: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
../drivers/ntb/test/ntb_perf.c:214:14: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
-------------------------------------------------------------------------------
arm64-defconfig : FAIL, 0 errors, 6 warnings, 0 section mismatches
Warnings:
../net/ipv4/igmp.c:1227:14: warning: unused variable 'net' [-Wunused-variable]
../net/ipv4/igmp.c:1319:14: warning: unused variable 'net' [-Wunused-variable]
../net/ipv4/igmp.c:1646:14: warning: unused variable 'net' [-Wunused-variable]
../net/ipv4/igmp.c:1665:14: warning: unused variable 'net' [-Wunused-variable]
../drivers/spi/spi.c:2279:9: warning: format '%i' expects argument of type 'int', but argument 4 has type 'size_t {aka long unsigned int}' [-Wformat=]
../include/linux/kernel.h:754:17: warning: comparison of distinct pointer types lacks a cast
-------------------------------------------------------------------------------
Passed with no errors, warnings or mismatches:
x86_64-allnoconfig
arm64-allnoconfig
arm-allnoconfig
arm-multi_v5_defconfig
x86_64-defconfig
^ permalink raw reply
* Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
From: Russell King - ARM Linux @ 2016-02-15 8:58 UTC (permalink / raw)
To: Uwe Kleine-König
Cc: linux-arm-kernel, Greg Kroah-Hartman, linux-next, linux-kernel,
Guenter Roeck
In-Reply-To: <20160215081750.GD12289@pengutronix.de>
On Mon, Feb 15, 2016 at 09:17:50AM +0100, Uwe Kleine-König wrote:
> Hello Russell,
>
> On Sun, Feb 14, 2016 at 08:07:55PM +0000, Russell King - ARM Linux wrote:
> > On Sun, Feb 14, 2016 at 08:55:01PM +0100, Uwe Kleine-König wrote:
> > > So the unexpected abnormality here is that even though this device is
> > > instantiated by dt, the driver doesn't provide any compatibles.
> > > Either my expectation is wrong, then 67d02a1bbb33455 should be reverted
> >
> > Your expectation is wrong. AMBA primecell devices have hardware IDs
> > and are matched to their drivers by those IDs. Just like PCI.
>
> pci devices don't appear in dt, do they? I don't see the connection
> between amba devices and platform devices, see my other mail in this
> thread for some more details.
They both have hardware IDs, and they are both matched via those hardware
IDs.
Your change has introduced a regression and is therefore wrong.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
^ permalink raw reply
* Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
From: Uwe Kleine-König @ 2016-02-15 8:17 UTC (permalink / raw)
To: Russell King - ARM Linux
Cc: linux-arm-kernel, Greg Kroah-Hartman, linux-next, linux-kernel,
Guenter Roeck
In-Reply-To: <20160214200755.GB10826@n2100.arm.linux.org.uk>
Hello Russell,
On Sun, Feb 14, 2016 at 08:07:55PM +0000, Russell King - ARM Linux wrote:
> On Sun, Feb 14, 2016 at 08:55:01PM +0100, Uwe Kleine-König wrote:
> > So the unexpected abnormality here is that even though this device is
> > instantiated by dt, the driver doesn't provide any compatibles.
> > Either my expectation is wrong, then 67d02a1bbb33455 should be reverted
>
> Your expectation is wrong. AMBA primecell devices have hardware IDs
> and are matched to their drivers by those IDs. Just like PCI.
pci devices don't appear in dt, do they? I don't see the connection
between amba devices and platform devices, see my other mail in this
thread for some more details.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
^ permalink raw reply
* Re: linux-next: build warning after merge of the net-next tree
From: Nikolay Borisov @ 2016-02-15 8:01 UTC (permalink / raw)
To: Stephen Rothwell, David Miller, netdev; +Cc: linux-next, linux-kernel
In-Reply-To: <20160215130941.4ce2ae28@canb.auug.org.au>
On 02/15/2016 04:09 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> net/ipv4/igmp.c: In function 'igmp_group_added':
> net/ipv4/igmp.c:1227:14: warning: unused variable 'net' [-Wunused-variable]
> struct net *net = dev_net(in_dev->dev);
> ^
> net/ipv4/igmp.c: In function 'ip_mc_inc_group':
> net/ipv4/igmp.c:1319:14: warning: unused variable 'net' [-Wunused-variable]
> struct net *net = dev_net(in_dev->dev);
> ^
> net/ipv4/igmp.c: In function 'ip_mc_init_dev':
> net/ipv4/igmp.c:1646:14: warning: unused variable 'net' [-Wunused-variable]
> struct net *net = dev_net(in_dev->dev);
> ^
> net/ipv4/igmp.c: In function 'ip_mc_up':
> net/ipv4/igmp.c:1665:14: warning: unused variable 'net' [-Wunused-variable]
> struct net *net = dev_net(in_dev->dev);
> ^
>
> Introduced by commits
>
> 87a8a2ae65b7 ("igmp: Namespaceify igmp_llm_reports sysctl knob")
> 165094afcee7 ("igmp: Namespacify igmp_qrv sysctl knob")
>
> CONFIG_IP_MULTICAST is not set for this build.
Right, I have forgotten to add the ifdef guards for the respective
variables, will squeeze a patch in the next series on namespaceifying
various sysctls.
Thanks for testing!
^ permalink raw reply
* Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
From: Uwe Kleine-König @ 2016-02-15 7:48 UTC (permalink / raw)
To: Guenter Roeck
Cc: Greg Kroah-Hartman, linux-kernel, linux-next, linux-arm-kernel,
Russell King, Grant Likely, Arnd Bergmann, Rob Herring
In-Reply-To: <56C0ECDA.1000203@roeck-us.net>
Hello Guenter,
On Sun, Feb 14, 2016 at 01:08:42PM -0800, Guenter Roeck wrote:
> On 02/14/2016 11:55 AM, Uwe Kleine-König wrote:
> >[adding lakml and rmk to Cc]
[adding some more people to Cc]
> >On Sun, Feb 14, 2016 at 08:50:10AM -0800, Guenter Roeck wrote:
> >>Your patch 'driver-core: platform: probe of-devices only using list of
> >>compatibles' causes the following qemu tests to crash in -next.
For the new readers, that is 67d02a1bbb334558e9380409a3cd426b36d4578b.
The original idea of this commit was to not bind a device created from
device tree when its name matches the driver name but none of the
driver's compatibles which might yield some surprises.
> >>arm:vexpress-a9:vexpress_defconfig:vexpress-v2p-ca9
> >>arm:vexpress-a15:vexpress_defconfig:vexpress-v2p-ca15-tc1
> >>arm:vexpress-a9:multi_v7_defconfig:vexpress-v2p-ca9
> >>arm:vexpress-a15:multi_v7_defconfig:vexpress-v2p-ca15-tc1
> >>
> >>Crash log:
> >>
> >>VFS: Cannot open root device "mmcblk0" or unknown-block(0,0): error -6
> >>Please append a correct "root=" boot option; here are the available partitions:
> >>1f00 131072 mtdblock0 (driver?)
> >>1f01 32768 mtdblock1 (driver?)
> >>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> >>
> >>ie the mmc driver no longer instantiates. Reverting the patch fixes the problem.
> >
> >The driver is drivers/mmc/host/mmci.c, right? and the relevant device
> >tree snippet is:
> >
> > mmci@05000 {
> > compatible = "arm,pl180", "arm,primecell";
> > ...
> > };
> >
>
> Yes, I think so, or one of the many other similar mmc entries.
So the driver in question is an amba_driver and it fails to bind because
static int platform_match(struct device *dev, struct device_driver *drv)
was changed. This is the platform bus type's match function. Why is this
called for amba devices (that I would expect to use amba_bustype and so
amba_match)?
The driver isn't matched by of_driver_match_device, so the
following code must yield 1 for the mmci device:
/* Then try ACPI style match */
if (acpi_driver_match_device(dev, drv))
return 1;
/* Then try to match against the id table */
if (pdrv->id_table)
return platform_match_id(pdrv->id_table, pdev) != NULL;
/* fall-back to driver name match */
return (strcmp(pdev->name, drv->name) == 0);
acpi seems unlikely, and the other two match by the device's name which
feels wrong. And I also wonder, what drv is here, because platform_match
assumes it is a platform_driver, not an amba_driver.
> >? So the unexpected abnormality here is that even though this device is
> >instantiated by dt, the driver doesn't provide any compatibles.
> >Either my expectation is wrong, then 67d02a1bbb33455 should be reverted
> >(or handle this case in a different way), or the mmci driver should
> >declare compatibles (but then it needs to be a platform driver and not
> >an amba driver?).
>
> No idea what the correct solution would be. I do see
>
> if (of_device_is_compatible(bus, "arm,primecell")) {
> /*
> * Don't return an error here to keep compatibility with older
> * device tree files.
> */
> of_amba_device_create(bus, bus_id, platform_data, parent);
> return 0;
> }
So there is a new (and better?) way to instantiate amba devices?
> in drivers/of/platform.c, which suggests some special handling for amba
> devices. No idea if and how that is related, but I do have some concern
> that fixing the problem for mmc alone might not fix it for all the other
> devices instantiated with "arm,primecell". After all, my boot tests are
> really rudimentary (it boots, therefore it works).
I don't see the right thing to do either. Maybe someone else can shed
some light on this issue?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
^ permalink raw reply
* Re: linux-next: arm64 no longer boots with initramfs in qemu tests
From: Ard Biesheuvel @ 2016-02-15 7:13 UTC (permalink / raw)
To: Guenter Roeck
Cc: linux-next, Catalin Marinas, Mark Rutland,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
In-Reply-To: <20160214221242.GA23489@roeck-us.net>
On 14 February 2016 at 23:12, Guenter Roeck <linux@roeck-us.net> wrote:
> Hi,
>
> my qemu tests for arm64 fail to boot in linux-next, starting with next-20160209.
> Primary error is
>
> VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
> Please append a correct "root=" boot option; here are the available partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
>
> but that doesn't mean much since I try to boot an initramfs.
>
> A bisect attempt points to 'arm64: move kernel image to base of vmalloc area',
> but that doesn't really help since some of the bisect attempts fail to build
> with linker errors. Just for reference, a bisect log is attached.
>
> Comparing console logs between 4.5-rc3 and next-20160212, one key difference is
> that the kernel now displays
>
> Moving initrd from [88000000-889ae7ff] to [5d251000-5dbff7ff]
>
> which was not the case before. Turns out RAM ends at 60000000, so the address
> appears to be a bit odd (4.5-rc3 shows initramfs at a lower address).
> My qemu test runs with 512MB RAM. If I increase the RAM size to 2G,
> the "Moving" message is no longer displayed. However, I still get the same
> error.
>
> Qemu command line:
>
> qemu-system-aarch64 -machine virt -cpu cortex-a57 -machine type=virt \
> -nographic -smp 1 -m 512 -kernel arch/arm64/boot/Image \
> -initrd rootfs.arm64.cpio -append "console=ttyAMA0"
>
> Configuration is defconfig. Initramfs can be copied from
> https://github.com/groeck/linux-build-test/blob/master/rootfs/arm64/rootfs.arm64.cpio
>
> Please let me know if there is anything I can do to help tracking down
> the problem.
>
Hi Guenter,
Thanks for the detailed analysis. This looks like the same issue I fixed here:
http://thread.gmane.org/gmane.linux.ports.arm.kernel/477645
Regards,
Ard.
^ permalink raw reply
* linux-next: Tree for Feb 15
From: Stephen Rothwell @ 2016-02-15 5:40 UTC (permalink / raw)
To: linux-next; +Cc: linux-kernel
Hi all,
Changes since 20160212:
The aio tree still had a build failure so I used the version from
next-20160111.
The akpm-current tree gained conflict against the mips tree.
Non-merge commits (relative to Linus' tree): 4580
3966 files changed, 164257 insertions(+), 72564 deletions(-)
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" and checkout or reset to the new
master.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log
files in the Next directory. Between each merge, the tree was built
with a ppc64_defconfig for powerpc and an allmodconfig (with
CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a
native build of tools/perf. After the final fixups (if any), I do an
x86_64 modules_install followed by builds for x86_64 allnoconfig,
powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig
(this fails its final link) and pseries_le_defconfig and i386, sparc
and sparc64 defconfig.
Below is a summary of the state of the merge.
I am currently merging 239 trees (counting Linus' and 36 trees of patches
pending for Linus' tree).
Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .
Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.
Thanks to Randy Dunlap for doing many randconfig builds. And to Paul
Gortmaker for triage and bug fixes.
--
Cheers,
Stephen Rothwell
$ git checkout master
$ git reset --hard stable
Merging origin/master (18558cae0272 Linux 4.5-rc4)
Merging fixes/master (36f90b0a2ddd Linux 4.5-rc2)
Merging kbuild-current/rc-fixes (3d1450d54a4f Makefile: Force gzip and xz on module install)
Merging arc-current/for-curr (74bf8efb5fa6 Linux 4.4-rc7)
Merging arm-current/fixes (e972c37459c8 ARM: 8519/1: ICST: try other dividends than 1)
Merging m68k-current/for-linus (daf670bc9d36 m68k/defconfig: Update defconfigs for v4.5-rc1)
Merging metag-fixes/fixes (0164a711c97b metag: Fix ioremap_wc/ioremap_cached build errors)
Merging mips-fixes/mips-fixes (1795cd9b3a91 Linux 3.16-rc5)
Merging powerpc-fixes/fixes (0fe53e8d335b powerpc/powernv: Fix stale PE primary bus)
Merging powerpc-merge-mpe/fixes (bc0195aad0da Linux 4.2-rc2)
Merging sparc/master (ca0bb0798022 Add sun4v_wdt watchdog driver)
Merging net/master (db92ea5d4df0 dscc4: Undefined signed int shift)
Merging ipsec/master (a8a572a6b5f2 xfrm: dst_entries_init() per-net dst_ops)
Merging ipvs/master (cb27e4f99b5d ipvs: allow rescheduling after RST)
Merging wireless-drivers/master (fb724ed5c617 wlcore: Fix regression in wlcore_set_partition())
Merging mac80211/master (212c5a5e6ba6 mac80211: minstrel: Change expected throughput unit back to Kbps)
Merging sound-current/for-linus (07d86ca93db7 ALSA: usb-audio: avoid freeing umidi object twice)
Merging pci-current/for-linus (0cf1337e0b83 PCI: rcar: Add device tree support for r8a7793)
Merging driver-core.current/driver-core-linus (18558cae0272 Linux 4.5-rc4)
Merging tty.current/tty-linus (18558cae0272 Linux 4.5-rc4)
Merging usb.current/usb-linus (18558cae0272 Linux 4.5-rc4)
Merging usb-gadget-fixes/fixes (6a4290cc28be usb: dwc3: gadget: set the OTG flag in dwc3 gadget driver.)
Merging usb-serial-fixes/usb-linus (4152b387da81 USB: option: fix Cinterion AHxx enumeration)
Merging usb-chipidea-fixes/ci-for-usb-stable (6f51bc340d2a usb: chipidea: imx: fix a possible NULL dereference)
Merging staging.current/staging-linus (388f7b1d6e8c Linux 4.5-rc3)
Merging char-misc.current/char-misc-linus (18558cae0272 Linux 4.5-rc4)
Merging input-current/for-linus (ff84dabe3c6e Input: colibri-vf50-ts - add missing #include <linux/of.h>)
Merging crypto-current/master (8a3978ad55fb crypto: marvell/cesa - fix test in mv_cesa_dev_dma_init())
Merging ide/master (e04a2bd6d8c9 drivers/ide: make ide-scan-pci.c driver explicitly non-modular)
Merging devicetree-current/devicetree/merge (f76502aa9140 of/dynamic: Fix test for PPC_PSERIES)
Merging rr-fixes/fixes (8244062ef1e5 modules: fix longstanding /proc/kallsyms vs module insertion race.)
Merging vfio-fixes/for-linus (16ab8a5cbea4 vfio/noiommu: Don't use iommu_present() to track fake groups)
Merging kselftest-fixes/fixes (92e963f50fc7 Linux 4.5-rc1)
Merging backlight-fixes/for-backlight-fixes (68feaca0b13e backlight: pwm: Handle EPROBE_DEFER while requesting the PWM)
Merging ftrace-fixes/for-next-urgent (6224beb12e19 tracing: Have branch tracer use recursive field of task struct)
Merging mfd-fixes/for-mfd-fixes (1b52e50f2a40 mfd: max77843: Fix max77843_chg_init() return on error)
Merging drm-intel-fixes/for-linux-next-fixes (ed3f9fd1e865 drm/i915: fix error path in intel_setup_gmbus())
Merging asm-generic/master (040b323b5012 ARM: asm/div64.h: adjust to generic codde)
Merging arc/for-next (37eda9df5bd8 ARC: mm: Introduce explicit super page size support)
Merging arm/for-next (9bf9dc709377 Merge branches 'component', 'fixes', 'misc' and 'tauros2' into for-next)
Merging arm-perf/for-next/perf (92e963f50fc7 Linux 4.5-rc1)
Merging arm-soc/for-next (ce4785b58783 ARM: SoC: document merges)
Merging at91/at91-next (8129febb508f ARM: dts: at91: at91sam9n12ek: fix panel compatible string)
Merging bcm2835/for-next (b2776bf7149b Linux 3.18)
Merging bcm2835-dt/bcm2835-dt-next (5ec6f2cd8ec4 ARM: bcm2835: Add the Raspberry Pi power domain driver to the DT.)
Merging bcm2835-soc/bcm2835-soc-next (92e963f50fc7 Linux 4.5-rc1)
Merging bcm2835-drivers/bcm2835-drivers-next (92e963f50fc7 Linux 4.5-rc1)
Merging bcm2835-defconfig/bcm2835-defconfig-next (92e963f50fc7 Linux 4.5-rc1)
Merging berlin/berlin/for-next (9a7e06833249 Merge branch 'berlin/fixes' into berlin/for-next)
Merging cortex-m/for-next (f719a0d6a854 ARM: efm32: switch to vendor,device compatible strings)
Merging imx-mxs/for-next (9519c91560f3 Merge branch 'imx/defconfig' into for-next)
Merging keystone/next (8fdbbde4a16c Merge branch 'for_4.6/keystone_dts' into next)
Merging mvebu/for-next (94bd511801b6 Merge branch 'mvebu/defconfig' into mvebu/for-next)
Merging omap/for-next (28151408222a Merge branch 'omap-for-v4.6/dt' into for-next)
Merging omap-pending/for-next (30aa18d3bea5 MAINTAINERS: add maintainer for OMAP hwmod data)
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/omap_hwmod_7xx_data.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/omap_hwmod_43xx_data.c
Merging qcom/for-next (305d0c411114 ARM: qcom: Drop ARCH_MSM* configs)
CONFLICT (content): Merge conflict in MAINTAINERS
Merging renesas/next (74eb2716fe71 Merge branches 'heads/arm64-dt-for-v4.6', 'heads/defconfig-for-v4.6', 'heads/dt-for-v4.6' and 'heads/soc-for-v4.6' into next)
Merging rockchip/for-next (b24b8204ad7d Merge branch 'v4.6-armsoc/dts64' into for-next)
Merging rpi/for-rpi-next (bc0195aad0da Linux 4.2-rc2)
Merging samsung/for-next (92e963f50fc7 Linux 4.5-rc1)
Merging samsung-krzk/for-next (e47aab925a76 Merge branch 'for-v4.6/non-critical-fixes' into for-next)
Merging sunxi/sunxi/for-next (06902a8895d5 Merge branches 'sunxi/clocks-for-4.6', 'sunxi/core-for-4.6', 'sunxi/drivers-for-4.6' and 'sunxi/dt-for-4.6' into sunxi/for-next)
Merging tegra/for-next (46e98126e5a7 Merge branch for-4.6/arm64 into for-next)
Merging arm64/for-next/core (f4d92287583b arm64: Fix build with CONFIG_DEBUG_PAGEALLOC=n)
Merging blackfin/for-linus (d91e14b3b9e1 eth: bf609 eth clock: add pclk clock for stmmac driver probe)
Merging c6x/for-linux-next (ca3060d39ae7 c6x: Use generic clkdev.h header)
Merging cris/for-next (f9f3f864b5e8 cris: Fix section mismatches in architecture startup code)
Merging h8300/h8300-next (11943fdd17d2 h8300: dts: Rename the serial port clock to fck)
Merging hexagon/linux-next (02cc2ccfe771 Revert "Hexagon: fix signal.c compile error")
Merging ia64/next (7e26e9ff0a93 pstore: Fix return type of pstore_is_mounted())
Merging m68k/for-next (a9c9d9aca4e7 zorro: Use kobj_to_dev())
Merging m68knommu/for-next (9d4c9e5064d7 m68knommu: fix FEC platform device registration when driver is modular)
Merging metag/for-next (c8b6ad8b3f87 metag: ftrace: remove the misleading comment for ftrace_dyn_arch_init)
Merging microblaze/next (c937adb7ec91 microblaze: Wire up userfaultfd, membarrier, mlock2 syscalls)
Merging mips/mips-for-linux-next (950823465ff6 Merge branch '4.5-fixes' into mips-for-linux-next)
Merging nios2/for-next (8e3d7c834ba0 nios2: fix cache coherency)
Merging parisc-hd/for-next (afd2ff9b7e1b Linux 4.4)
Merging powerpc/next (388f7b1d6e8c Linux 4.5-rc3)
Merging powerpc-mpe/next (bc0195aad0da Linux 4.2-rc2)
Merging fsl/next (44451d4d8f0e MAINTAINERS: Update Scott Wood's e-mail address)
Merging mpc5xxx/next (39e69f55f857 powerpc: Introduce the use of the managed version of kzalloc)
Merging s390/features (232f5dd78586 s390/oprofile: fix address range for asynchronous stack)
Merging sparc-next/master (9f935675d41a Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input)
Merging tile/master (f1c3418ed4e6 tile kgdb: fix bug in copy to gdb regs, and optimize memset)
Merging uml/linux-next (288b31a382d2 um: use %lx format specifiers for unsigned longs)
Merging unicore32/unicore32 (d670878e2c9a unicore32: Remove ARCH_HAS_CPUFREQ config option)
Merging xtensa/for_next (bb2f3486041a Merge tag 'xtensa-for-next-20160111' of git://github.com/jcmvbkbc/linux-xtensa)
Merging btrfs/next (988f1f576d4f Merge branch 'for-chris-4.5' of git://git.kernel.org/pub/scm/linux/kernel/git/fdmanana/linux into for-linus-4.5)
Merging btrfs-kdave/for-next (9e61250d83bf Merge branch 'for-next-4.6-20160212' into for-next-20160212)
Merging ceph/master (bbadd4529b09 libceph: MOSDOpReply v7 encoding)
Merging cifs/for-next (4b550af51985 cifs: fix erroneous return value)
Merging configfs/for-next (1609bac8af31 configfs: add myself as co-maintainer, updated git tree)
Merging ecryptfs/next (933c32fe0e42 ecryptfs: drop null test before destroy functions)
Merging ext3/for_next (5a9530e498ed ocfs2: Implement get_next_id())
Merging ext4/dev (b7bcb1cf0d3b ext4: remove unused parameter "newblock" in convert_initialized_extent())
Merging f2fs/dev (9fa02d4ea5ec f2fs: avoid garbage lenghs in dentries)
Merging fscache/fscache (b00c2ae2ed3c FS-Cache: Don't override netfs's primary_index if registering failed)
Merging fuse/for-next (0b5da8db145b fuse: add support for SEEK_HOLE and SEEK_DATA in lseek)
Merging gfs2/for-next (00bf5636b147 GFS2: Prevent delete work from occurring on glocks used for create)
Merging jfs/jfs-next (26456955719b jfs: clean up jfs_rename and fix out of order unlock)
Merging nfs/linux-next (50ab8ec74a15 nfs: fix nfs_size_to_loff_t)
Merging nfsd/nfsd-next (ee2bf98bbe90 NFSv4: fix getacl ERANGE for some ACL buffer sizes)
Merging orangefs/for-next (da335c69c759 orangefs: use S_ISREG(mode) and friends instead of mode & S_IFREG.)
Applying: orangfs: update for follow_link to get_link change
Merging overlayfs/overlayfs-next (84889d493356 ovl: check dentry positiveness in ovl_cleanup_whiteouts())
Merging squashfs/master (62421645bb70 Squashfs: Add LZ4 compression configuration option)
Merging v9fs/for-next (a333e4bf2556 fs/9p: use fscache mutex rather than spinlock)
Merging ubifs/linux-next (4fdd1d51ad5d ubifs: Use XATTR_*_PREFIX_LEN)
Merging xfs/for-next (63a1962bea7d Merge branch 'xfs-buf-macro-cleanup-4.6' into for-next)
Merging file-locks/linux-next (5af9c2e19da6 Merge branch 'akpm' (patches from Andrew))
Merging vfs/for-next (6f3925248b75 Merge branches 'work.iov_iter', 'work.copy_file_range', 'work.xattr' and 'work.symlinks' into for-next)
Merging pci/next (a314966fad61 Merge branches 'pci/host-designware', 'pci/host-imx6', 'pci/host-layerscape' and 'pci/host-rcar' into next)
Merging hid/for-next (bc1db4af59b2 Merge branches 'for-4.6/sony' and 'for-4.6/upstream' into for-next)
Merging i2c/i2c/for-next (61c18aeb05c3 i2c: uniphier: add COMPILE_TEST option)
Merging jdelvare-hwmon/master (f02de116250d Documentation/hwmon: Update links in max34440)
Merging dmi/master (c3db05ecf8ac firmware: dmi_scan: Save SMBIOS Type 9 System Slots)
Merging hwmon-staging/hwmon-next (972d7d17b6bb hwmon: Add LTC2990 sensor driver)
Merging v4l-dvb/master (0d8f3357897d Merge branch 'v4l_for_linus' into to_next)
Merging kbuild/for-next (f6f756ddd65f Merge branch 'kbuild/kbuild' into kbuild/for-next)
Merging kconfig/for-next (c0ddc8c745b7 localmodconfig: Use Kbuild files too)
Merging libata/for-next (a2127e400edd libata: support AHCI on OCTEON platform)
Merging pm/linux-next (e2222c52f8e7 Merge branch 'pm-cpufreq-governor' into linux-next)
Merging idle/next (31ade3b83e18 Linux 4.4-rc3)
Merging apm/for-next (53675abbd1e5 x86, apm: Remove unused variable)
Merging thermal/next (98d94507e10c Merge branches 'thermal-intel', 'thermal-suspend-fix' and 'thermal-soc' into next)
Merging thermal-soc/next (a53b8394ec3c thermal: cpu_cooling: fix out of bounds access in time_in_idle)
Merging ieee1394/for-next (100ceb66d5c4 firewire: ohci: fix JMicron JMB38x IT context discovery)
Merging dlm/next (a6b1533e9a57 dlm: make posix locks interruptible)
Merging swiotlb/linux-next (386744425e35 swiotlb: Make linux/swiotlb.h standalone includible)
Merging slave-dma/next (8e2a101d7199 Merge branch 'topic/sh' into next)
Merging net-next/master (667f00630ebe Merge branch 'local-checksum-offload')
CONFLICT (content): Merge conflict in drivers/net/vxlan.c
Merging ipsec-next/master (cb866e3298cd xfrm: Increment statistic counter on inner mode error)
Merging ipvs-next/master (72c1ef52626b netfilter: ipvs/SIP: handle ip_vs_fill_iph_skb_off failure)
Merging wireless-drivers-next/master (11e70824e75f mwifiex: firmware dump support for w8997 chipset)
Merging bluetooth/master (9a6a1c77e1fc Bluetooth: Use managed version of led_trigger_register in LED trigger)
Merging mac80211-next/master (94106d26c380 mac80211: fix VHT MU-MIMO frame processing)
CONFLICT (content): Merge conflict in net/mac80211/debugfs.c
Merging rdma/for-next (34356f64ac0d IB/mlx5: Unify CQ create flags check)
Merging mtd/master (38714fbd299f MAINTAINERS: update Han's email)
Merging l2-mtd/master (3b5394a3ccff mtd: spi-nor: remove micron_quad_enable())
Merging crypto/master (f75516a81548 crypto: keys - Revert "convert public key to akcipher api")
Merging drm/drm-next (5443ce86fa37 drm: virtio-gpu: set atomic flag)
Merging drm-panel/drm/panel/for-next (abf08d5efee4 dt-bindings: Move panel bindings to correct location)
Merging drm-intel/for-linux-next (59bbf84d8958 drm/i915: Update DRIVER_DATE to 20160214)
Merging drm-tegra/drm/tegra/for-next (d50bbe33efb5 gpu: host1x: Use a signed return type for do_relocs())
Merging drm-misc/topic/drm-misc (4d32c0d82380 drm/i915: Set aux.dev to the drm_connector device, instead of drm_device.)
Merging drm-exynos/exynos-drm/for-next (25364a9e54fb Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid)
Merging drm-msm/msm-next (2abd1c88345e drm/msm/mdp: fix a problematic usage of WARN_ON())
Merging hdlcd/for-upstream/hdlcd (8bb912e606b7 arm64: Juno: Add HDLCD support to the Juno boards.)
Merging drm-vc4/drm-vc4-next (5645e785cea2 drm/vc4: fix an error code)
Merging sound/for-next (cbaaee80e151 Merge branch 'topic/core-fixes' into for-next)
Merging sound-asoc/for-next (965e35728446 Merge remote-tracking branches 'asoc/topic/ssm4567' and 'asoc/topic/wm8974' into asoc-next)
Merging modules/modules-next (b37a05c083c8 Merge branch 'akpm' (patches from Andrew))
Merging input/next (1261d013daea Input: Allow compile test of Goodix and Colibri VF50 if !GPIOLIB)
Merging block/for-next (ab3d8b3ecf77 Merge branch 'for-4.6/core' into for-next)
Merging device-mapper/for-next (aa8c484be790 dm thin metadata: remove needless newline from subtree_dec() DMERR message)
Merging pcmcia/master (e8e68fd86d22 pcmcia: do not break rsrc_nonstatic when handling anonymous cards)
Merging mmc/mmc-next (11bc9381b277 mmc: sdhci-s3c: use mmc_of_parse and remove the card_tasklet)
Merging mmc-uh/next (fa0ec6cfd1e2 Merge branch 'fixes' into next)
Merging kgdb/kgdb-next (2d289f14f00a kdb: Fix handling of kallsyms_symbol_next() return value)
Merging md/for-next (fc2561ec0afc md-cluster: delete useless code)
Merging mfd/for-mfd-next (103d8a7bb8a2 mfd: tps65090: Set regmap config reg counts properly)
Merging backlight/for-backlight-next (60d613d6aef4 backlight: pwm_bl: Free PWM requested by legacy API on error path)
Merging battery/master (265b60497a57 power: bq27xxx_battery: Fix bq27541 AveragePower register address)
Merging omap_dss2/for-next (caf05780f6ed Merge omapdss split between omapdrm and omapfb)
Merging regulator/for-next (a67f79c2fedf Merge remote-tracking branches 'regulator/topic/max77802', 'regulator/topic/maxim', 'regulator/topic/mt6397' and 'regulator/topic/qcom-saw' into regulator-next)
Merging security/next (388f7b1d6e8c Linux 4.5-rc3)
Merging integrity/next (70ded691640f ima: use "ima_hooks" enum as function argument)
Merging selinux/next (9090a2d5e3e6 selinux: use absolute path to include directory)
Merging lblnet/next (b2776bf7149b Linux 3.18)
Merging watchdog/master (388f7b1d6e8c Linux 4.5-rc3)
Merging iommu/next (fd6b6b40c17e Merge branches 'iommu/fixes' and 'arm/rockchip' into next)
Merging dwmw2-iommu/master (fda3bec12d09 iommu/vt-d: Fix 64-bit accesses to 32-bit DMAR_GSTS_REG)
Merging vfio/next (d4f50ee2f5b4 vfio/iommu_type1: make use of info.flags)
Merging jc_docs/docs-next (5645a717c6ee Documentation: HOWTO: remove obsolete info about regression postings)
Merging trivial/for-next (e9bf1d57f0a0 drivers/rtc: broken link fix)
Applying: kernel/memremap.c: add new arg to dev_WARN
Merging audit/next (fd97646b0595 audit: Fix typo in comment)
Merging devicetree/devicetree/next (48a9b733e644 of/irq: Rename "intc_desc" to "of_intc_desc" to fix OF on sh)
Merging dt-rh/for-next (6338b8a12d0a Merge branches 'dt/linus' and 'dt/next' into for-next)
Merging mailbox/mailbox-for-next (bfbcfa770b1c mailbox: constify mbox_chan_ops structure)
Merging spi/for-next (b34cedc7cf77 Merge remote-tracking branch 'spi/topic/ti-qspi' into spi-next)
Merging tip/auto-latest (61c66a442223 Merge branch 'x86/mm')
Merging clockevents/clockevents/next (1ddca16cc5b3 clocksource/drivers/h8300: Use ioread / iowrite)
CONFLICT (content): Merge conflict in drivers/clocksource/h8300_timer16.c
Merging edac/linux_next (12f0721c5a70 sb_edac: correctly fetch DIMM width on Ivy Bridge and Haswell)
Merging edac-amd/for-next (7cc5a5d3cd4c ARM: socfpga: Enable OCRAM ECC on startup)
Merging irqchip/irqchip/for-next (f290917dc209 Merge branch 'irqchip/sunxi' into irqchip/for-next)
Merging tiny/tiny/next (f114040e3ea6 Linux 3.18-rc1)
Merging ftrace/for-next (7fd13615992a tracing/dma-buf/fence: Fix timeline str value on fence_annotate_wait_on)
Merging rcu/rcu/next (0dd1befbc663 rcu: Remove expedited GP funnel-lock bypass)
Merging kvm/linux-next (bce87cce88c7 KVM: x86: consolidate different ways to test for in-kernel LAPIC)
Merging kvm-arm/next (1f4fa0c0e5bf arm/arm64: KVM: Handle out-of-RAM cache maintenance as a NOP)
CONFLICT (content): Merge conflict in arch/arm/kvm/arm.c
Merging kvm-ppc/kvm-ppc-next (c63517c2e381 KVM: PPC: Book3S: correct width in XER handling)
Merging kvm-ppc-paulus/kvm-ppc-next (b4d7f161feb3 KVM: PPC: Fix ONE_REG AltiVec support)
Merging kvms390/next (1763f8d09d52 KVM: s390: bail out early on fatal signal in dirty logging)
Merging xen-tip/linux-next (a4cdb556cae0 xen/gntdev: add ioctl for grant copy)
Merging percpu/for-next (18fc93fd6412 percpu: remove PERCPU_ENOUGH_ROOM which is stale definition)
Merging workqueues/for-next (d6e022f1d207 workqueue: handle NUMA_NO_NODE for unbound pool_workqueue lookup)
Merging drivers-x86/for-next (b0c141b8f86b dell-led: use dell_smbios_send_request() for performing SMBIOS calls)
Merging chrome-platform/for-next (ebaf31c46cce platform/chrome: Fix i2c-designware adapter name)
Merging regmap/for-next (02ce716f8000 Merge remote-tracking branches 'regmap/topic/doc' and 'regmap/topic/irq' into regmap-next)
Merging hsi/for-next (87d99063be01 HSI: ssi-protocol: Use handshake logic from n950)
Merging leds/for-next (ee2e1c2d18a4 leds: leds-gpio: Fix return value check in create_gpio_led())
Merging ipmi/for-next (7f8df84ecba8 ipmi_si: Avoid a wrong long timeout on transaction done)
Merging driver-core/driver-core-next (c21b04f9890c Merge 4.5-rc4 into driver-core-next)
Merging tty/tty-next (249f3c4fe4fd Merge 4.5-rc4 into tty-next)
Merging usb/usb-next (172ad9af55d2 Merge 4.5-rc4 into usb-next)
Merging usb-gadget/next (36f90b0a2ddd Linux 4.5-rc2)
Merging usb-serial/usb-next (92e963f50fc7 Linux 4.5-rc1)
Merging usb-chipidea-next/ci-for-usb-next (6b8bc9c6fb26 usb: chipidea: udc: remove unused value assignment)
Merging staging/staging-next (d9750a2f9eea Merge tag 'iio-for-4.6b' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next)
CONFLICT (modify/delete): drivers/staging/dgap/dgap.c deleted in staging/staging-next and modified in HEAD. Version HEAD of drivers/staging/dgap/dgap.c left in tree.
$ git rm -f drivers/staging/dgap/dgap.c
Merging char-misc/char-misc-next (1b79dff672ca Merge 4.5-rc4 into char-misc-next)
Merging extcon/extcon-next (0331966df0a2 arm: boot: beaglex15: pass correct interrupt)
Merging cgroup/for-next (223ffb29f972 cgroup: provide cgroup_nov1= to disable controllers in v1 mounts)
Merging scsi/for-next (cef98052b16c Merge branch 'fixes' into for-next)
Merging target-updates/for-next (fab683eb12e7 scsi: qla2xxxx: avoid type mismatch in comparison)
Merging target-merge/for-next-merge (bc0195aad0da Linux 4.2-rc2)
Merging pinctrl/for-next (b4f51b6f4513 Merge branch 'devel' into for-next)
Merging vhost/linux-next (481eaec37e91 tools/virtio: add ringtest utilities)
Merging remoteproc/for-next (7a6271a80cae remoteproc/wkup_m3: Use MODULE_DEVICE_TABLE to export alias)
Merging rpmsg/for-next (b1b9891441fa rpmsg: use less buffers when vrings are small)
Merging gpio/for-next (8d68bb842800 Merge branch 'devel' into for-next)
Merging dma-mapping/dma-mapping-next (d770e558e219 Linux 4.2-rc1)
Merging pwm/for-next (ff01c944cfa9 pwm: Mark all devices as "might sleep")
Merging dma-buf/for-next (168309855a7d Linux 4.4-rc8)
Merging userns/for-next (f2ca379642d7 namei: permit linking with CAP_FOWNER in userns)
Merging ktest/for-next (b953c0d234bc Linux 4.1)
Merging clk/clk-next (7208d1d9c568 clk: qcom: mmcc8974: Use gdscs .parent and remove genpd calls)
Merging random/dev (7185ad2672a7 crypto: memzero_explicit - make sure to clear out sensitive data)
Merging aio/master (fb2e69217129 aio: Fix compile error due to unexpected use of cmpxchg())
$ git reset --hard HEAD^
Merging next-20160111 version of aio
Merging llvmlinux/for-next (25d4aee23af2 arm: LLVMLinux: Use global stack register variable for percpu)
Merging kselftest/next (92e963f50fc7 Linux 4.5-rc1)
Merging y2038/y2038 (477b8541b31f qla2xxx: Remove use of 'struct timeval')
Merging luto-misc/next (afd2ff9b7e1b Linux 4.4)
Merging borntraeger/linux-next (36f90b0a2ddd Linux 4.5-rc2)
Merging livepatching/for-next (03f726f415f5 Merge branch 'for-4.5/upstream-fixes' into for-next)
Merging coresight/next (37fe87dbde16 coresight: implementing 'cpu_id()' API)
Merging rtc/rtc-next (9d4be765c76d drivers: rtc: allow compilation of sun6i RTC for all sunxi SoCs)
Merging hwspinlock/for-next (bd5717a4632c hwspinlock: qcom: Correct msb in regmap_field)
Merging nvdimm/libnvdimm-for-next (36f90b0a2ddd Linux 4.5-rc2)
Merging akpm-current/current (b424a3e227e8 ipc/msg.c: use freezable blocking call)
CONFLICT (content): Merge conflict in fs/ocfs2/aops.c
CONFLICT (content): Merge conflict in arch/mips/Kconfig
$ git checkout -b akpm remotes/origin/akpm/master
Applying: drivers/net/wireless/intel/iwlwifi/dvm/calib.c: simplfy min() expression
Merging akpm/master (ebfe43f349a7 drivers/net/wireless/intel/iwlwifi/dvm/calib.c: simplfy min() expression)
^ permalink raw reply
* linux-next: manual merge of the akpm-current tree with the mips tree
From: Stephen Rothwell @ 2016-02-15 5:03 UTC (permalink / raw)
To: Andrew Morton, Ralf Baechle
Cc: linux-next, linux-kernel, Petr Mladek, David Daney
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/mips/Kconfig
between commit:
d96927dfa449 ("MIPS: Select CONFIG_HANDLE_DOMAIN_IRQ and make it work.")
from the mips tree and commit:
29afe44a7fbe ("printk/nmi: generic solution for safe printk in NMI")
from the akpm-current tree.
I fixed it up (see below) and can carry the fix as necessary (no action
is required).
--
Cheers,
Stephen Rothwell
diff --cc arch/mips/Kconfig
index e4df64c411b7,56f57816613e..000000000000
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@@ -62,7 -62,7 +62,8 @@@ config MIP
select HAVE_IRQ_TIME_ACCOUNTING
select GENERIC_TIME_VSYSCALL
select ARCH_CLOCKSOURCE_DATA
+ select HANDLE_DOMAIN_IRQ
+ select HAVE_NMI
menu "Machine selection"
^ permalink raw reply
* linux-next: build warning after merge of the net-next tree
From: Stephen Rothwell @ 2016-02-15 2:09 UTC (permalink / raw)
To: David Miller, netdev; +Cc: linux-next, linux-kernel, Nikolay Borisov
Hi all,
After merging the net-next tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
net/ipv4/igmp.c: In function 'igmp_group_added':
net/ipv4/igmp.c:1227:14: warning: unused variable 'net' [-Wunused-variable]
struct net *net = dev_net(in_dev->dev);
^
net/ipv4/igmp.c: In function 'ip_mc_inc_group':
net/ipv4/igmp.c:1319:14: warning: unused variable 'net' [-Wunused-variable]
struct net *net = dev_net(in_dev->dev);
^
net/ipv4/igmp.c: In function 'ip_mc_init_dev':
net/ipv4/igmp.c:1646:14: warning: unused variable 'net' [-Wunused-variable]
struct net *net = dev_net(in_dev->dev);
^
net/ipv4/igmp.c: In function 'ip_mc_up':
net/ipv4/igmp.c:1665:14: warning: unused variable 'net' [-Wunused-variable]
struct net *net = dev_net(in_dev->dev);
^
Introduced by commits
87a8a2ae65b7 ("igmp: Namespaceify igmp_llm_reports sysctl knob")
165094afcee7 ("igmp: Namespacify igmp_qrv sysctl knob")
CONFIG_IP_MULTICAST is not set for this build.
--
Cheers,
Stephen Rothwell
^ permalink raw reply
* Re: next: sparc64 crashes due to 'blk-mq: dynamic h/w context count'
From: Jens Axboe @ 2016-02-14 22:35 UTC (permalink / raw)
To: Guenter Roeck, Ming Lei
Cc: Keith Busch, Linux Kernel Mailing List, Jens Axboe, linux-block,
linux-next@vger.kernel.org
In-Reply-To: <56C0DDD2.50802@roeck-us.net>
On 02/14/2016 01:04 PM, Guenter Roeck wrote:
> On 02/14/2016 07:14 AM, Ming Lei wrote:
>> On Sun, Feb 14, 2016 at 9:17 PM, Guenter Roeck <linux@roeck-us.net>
>> wrote:
>>> Hi,
>>>
>>> my runtime tests of linux-next crash for sparc64 due to commit
>>> 'blk-mq: dynamic
>>> h/w context count'. Reverting the patch fixes the problem. Bisect log is
>>> attached below. Full crash log is available at
>>> http://kerneltests.org/builders,
>>> in the table with qemu test results.
>>
>> Guenter, could you test patch in the following link to see if it can
>> be fixed?
>>
>> http://marc.info/?l=linux-kernel&m=145526562410555&w=2
>>
>
> Yes, that fixes the problem.
Ming, I've added it to 4.6/core, thanks.
--
Jens Axboe
^ permalink raw reply
* linux-next: arm64 no longer boots with initramfs in qemu tests
From: Guenter Roeck @ 2016-02-14 22:12 UTC (permalink / raw)
To: linux-next
Cc: Ard Biesheuvel, Catalin Marinas, Mark Rutland, linux-arm-kernel,
linux-kernel
Hi,
my qemu tests for arm64 fail to boot in linux-next, starting with next-20160209.
Primary error is
VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
but that doesn't mean much since I try to boot an initramfs.
A bisect attempt points to 'arm64: move kernel image to base of vmalloc area',
but that doesn't really help since some of the bisect attempts fail to build
with linker errors. Just for reference, a bisect log is attached.
Comparing console logs between 4.5-rc3 and next-20160212, one key difference is
that the kernel now displays
Moving initrd from [88000000-889ae7ff] to [5d251000-5dbff7ff]
which was not the case before. Turns out RAM ends at 60000000, so the address
appears to be a bit odd (4.5-rc3 shows initramfs at a lower address).
My qemu test runs with 512MB RAM. If I increase the RAM size to 2G,
the "Moving" message is no longer displayed. However, I still get the same
error.
Qemu command line:
qemu-system-aarch64 -machine virt -cpu cortex-a57 -machine type=virt \
-nographic -smp 1 -m 512 -kernel arch/arm64/boot/Image \
-initrd rootfs.arm64.cpio -append "console=ttyAMA0"
Configuration is defconfig. Initramfs can be copied from
https://github.com/groeck/linux-build-test/blob/master/rootfs/arm64/rootfs.arm64.cpio
Please let me know if there is anything I can do to help tracking down
the problem.
Guenter
---
bisect log:
# bad: [64d9a3617b3b8bc0734ba97caeb433b7019c6187] Add linux-next specific files for 20160212
# good: [388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95] Linux 4.5-rc3
git bisect start 'next-20160212' 'v4.5-rc3'
# bad: [597dc9d36e8bc04941b61b26ac7aa3f8a33aba53] Merge remote-tracking branch 'sound-asoc/for-next'
git bisect bad 597dc9d36e8bc04941b61b26ac7aa3f8a33aba53
# bad: [50d4eb6f1f993ca4a3da8c0aa6b807bcf0bd502a] Merge remote-tracking branch 'hid/for-next'
git bisect bad 50d4eb6f1f993ca4a3da8c0aa6b807bcf0bd502a
# good: [b80f982a1a4a6e091235e31906fc0c1cc8c76307] Merge remote-tracking branch 'samsung-krzk/for-next'
git bisect good b80f982a1a4a6e091235e31906fc0c1cc8c76307
# bad: [5278da7e981882dbf23d8dcd5a7ce4d92ff24ba9] Merge remote-tracking branch 'nfsd/nfsd-next'
git bisect bad 5278da7e981882dbf23d8dcd5a7ce4d92ff24ba9
# bad: [d4cf2a954fb2a40acb1c91a55ccaca987fb367ea] Merge remote-tracking branch 'microblaze/next'
git bisect bad d4cf2a954fb2a40acb1c91a55ccaca987fb367ea
# good: [1bdf65407f5d226fbaf1798ffee76e5d12a6ed8e] Merge remote-tracking branch 'tegra/for-next'
git bisect good 1bdf65407f5d226fbaf1798ffee76e5d12a6ed8e
# bad: [f59ba4eb5629fc1a7afe596ab1e84720b893472b] arm64: move back to generic memblock_enforce_memory_limit()
git bisect bad f59ba4eb5629fc1a7afe596ab1e84720b893472b
# good: [a9262c0ff6c56e45e3abb901d7166b4fe2f4d285] arm64: mm: add functions to walk tables in fixmap
git bisect good a9262c0ff6c56e45e3abb901d7166b4fe2f4d285
# good: [80a5c2655c25f4f8e92bf12207d2f90f771585ac] arm64: add support for ioremap() block mappings
git bisect good 80a5c2655c25f4f8e92bf12207d2f90f771585ac
# good: [e7f7cf4021c3b711f5eec19727aa88bf7532db51] arm64: decouple early fixmap init from linear mapping
git bisect good e7f7cf4021c3b711f5eec19727aa88bf7532db51
# bad: [752af28bd7117bd877caafce1600edf69c5bd7e4] arm64: move kernel image to base of vmalloc area
git bisect bad 752af28bd7117bd877caafce1600edf69c5bd7e4
# good: [6a26b548a2c42652229d15b7b8361382f4182dfc] arm64: kvm: deal with kernel symbols outside of linear mapping
git bisect good 6a26b548a2c42652229d15b7b8361382f4182dfc
# first bad commit: [752af28bd7117bd877caafce1600edf69c5bd7e4] arm64: move kernel image to base of vmalloc area
^ permalink raw reply
* Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
From: Guenter Roeck @ 2016-02-14 21:08 UTC (permalink / raw)
To: Uwe Kleine-König
Cc: Greg Kroah-Hartman, linux-kernel, linux-next, linux-arm-kernel,
Russell King
In-Reply-To: <20160214195501.GA12289@pengutronix.de>
On 02/14/2016 11:55 AM, Uwe Kleine-König wrote:
> [adding lakml and rmk to Cc]
>
> Hello Guenter,
>
> On Sun, Feb 14, 2016 at 08:50:10AM -0800, Guenter Roeck wrote:
>> Uwe,
>>
>> Your patch 'driver-core: platform: probe of-devices only using list of
>> compatibles' causes the following qemu tests to crash in -next.
>>
>> arm:vexpress-a9:vexpress_defconfig:vexpress-v2p-ca9
>> arm:vexpress-a15:vexpress_defconfig:vexpress-v2p-ca15-tc1
>> arm:vexpress-a9:multi_v7_defconfig:vexpress-v2p-ca9
>> arm:vexpress-a15:multi_v7_defconfig:vexpress-v2p-ca15-tc1
>>
>> Crash log:
>>
>> VFS: Cannot open root device "mmcblk0" or unknown-block(0,0): error -6
>> Please append a correct "root=" boot option; here are the available partitions:
>> 1f00 131072 mtdblock0 (driver?)
>> 1f01 32768 mtdblock1 (driver?)
>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
>>
>> ie the mmc driver no longer instantiates. Reverting the patch fixes the problem.
>
> The driver is drivers/mmc/host/mmci.c, right? and the relevant device
> tree snippet is:
>
> mmci@05000 {
> compatible = "arm,pl180", "arm,primecell";
> ...
> };
>
Yes, I think so, or one of the many other similar mmc entries.
> ? So the unexpected abnormality here is that even though this device is
> instantiated by dt, the driver doesn't provide any compatibles.
> Either my expectation is wrong, then 67d02a1bbb33455 should be reverted
> (or handle this case in a different way), or the mmci driver should
> declare compatibles (but then it needs to be a platform driver and not
> an amba driver?).
>
No idea what the correct solution would be. I do see
if (of_device_is_compatible(bus, "arm,primecell")) {
/*
* Don't return an error here to keep compatibility with older
* device tree files.
*/
of_amba_device_create(bus, bus_id, platform_data, parent);
return 0;
}
in drivers/of/platform.c, which suggests some special handling for amba
devices. No idea if and how that is related, but I do have some concern
that fixing the problem for mmc alone might not fix it for all the other
devices instantiated with "arm,primecell". After all, my boot tests are
really rudimentary (it boots, therefore it works).
Thanks,
Guenter
^ permalink raw reply
* Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
From: Russell King - ARM Linux @ 2016-02-14 20:07 UTC (permalink / raw)
To: Uwe Kleine-König
Cc: Guenter Roeck, Greg Kroah-Hartman, linux-kernel, linux-next,
linux-arm-kernel
In-Reply-To: <20160214195501.GA12289@pengutronix.de>
On Sun, Feb 14, 2016 at 08:55:01PM +0100, Uwe Kleine-König wrote:
> So the unexpected abnormality here is that even though this device is
> instantiated by dt, the driver doesn't provide any compatibles.
> Either my expectation is wrong, then 67d02a1bbb33455 should be reverted
Your expectation is wrong. AMBA primecell devices have hardware IDs
and are matched to their drivers by those IDs. Just like PCI.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
^ permalink raw reply
* Re: next: sparc64 crashes due to 'blk-mq: dynamic h/w context count'
From: Guenter Roeck @ 2016-02-14 20:04 UTC (permalink / raw)
To: Ming Lei
Cc: Keith Busch, Linux Kernel Mailing List, Jens Axboe, linux-block,
linux-next@vger.kernel.org
In-Reply-To: <CACVXFVMx5o8csfpXKHuKJc65pvb95WOjqA_NuW1-6GUB-GOZyg@mail.gmail.com>
On 02/14/2016 07:14 AM, Ming Lei wrote:
> On Sun, Feb 14, 2016 at 9:17 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>> Hi,
>>
>> my runtime tests of linux-next crash for sparc64 due to commit 'blk-mq: dynamic
>> h/w context count'. Reverting the patch fixes the problem. Bisect log is
>> attached below. Full crash log is available at http://kerneltests.org/builders,
>> in the table with qemu test results.
>
> Guenter, could you test patch in the following link to see if it can be fixed?
>
> http://marc.info/?l=linux-kernel&m=145526562410555&w=2
>
Yes, that fixes the problem.
Thanks,
Guenter
^ permalink raw reply
* Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
From: Uwe Kleine-König @ 2016-02-14 19:55 UTC (permalink / raw)
To: Guenter Roeck
Cc: Greg Kroah-Hartman, linux-kernel, linux-next, linux-arm-kernel,
Russell King
In-Reply-To: <20160214165010.GA3189@roeck-us.net>
[adding lakml and rmk to Cc]
Hello Guenter,
On Sun, Feb 14, 2016 at 08:50:10AM -0800, Guenter Roeck wrote:
> Uwe,
>
> Your patch 'driver-core: platform: probe of-devices only using list of
> compatibles' causes the following qemu tests to crash in -next.
>
> arm:vexpress-a9:vexpress_defconfig:vexpress-v2p-ca9
> arm:vexpress-a15:vexpress_defconfig:vexpress-v2p-ca15-tc1
> arm:vexpress-a9:multi_v7_defconfig:vexpress-v2p-ca9
> arm:vexpress-a15:multi_v7_defconfig:vexpress-v2p-ca15-tc1
>
> Crash log:
>
> VFS: Cannot open root device "mmcblk0" or unknown-block(0,0): error -6
> Please append a correct "root=" boot option; here are the available partitions:
> 1f00 131072 mtdblock0 (driver?)
> 1f01 32768 mtdblock1 (driver?)
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
>
> ie the mmc driver no longer instantiates. Reverting the patch fixes the problem.
The driver is drivers/mmc/host/mmci.c, right? and the relevant device
tree snippet is:
mmci@05000 {
compatible = "arm,pl180", "arm,primecell";
...
};
? So the unexpected abnormality here is that even though this device is
instantiated by dt, the driver doesn't provide any compatibles.
Either my expectation is wrong, then 67d02a1bbb33455 should be reverted
(or handle this case in a different way), or the mmci driver should
declare compatibles (but then it needs to be a platform driver and not
an amba driver?).
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
^ permalink raw reply
* arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
From: Guenter Roeck @ 2016-02-14 16:50 UTC (permalink / raw)
To: Uwe Kleine-König; +Cc: Greg Kroah-Hartman, linux-kernel, linux-next
Uwe,
Your patch 'driver-core: platform: probe of-devices only using list of
compatibles' causes the following qemu tests to crash in -next.
arm:vexpress-a9:vexpress_defconfig:vexpress-v2p-ca9
arm:vexpress-a15:vexpress_defconfig:vexpress-v2p-ca15-tc1
arm:vexpress-a9:multi_v7_defconfig:vexpress-v2p-ca9
arm:vexpress-a15:multi_v7_defconfig:vexpress-v2p-ca15-tc1
Crash log:
VFS: Cannot open root device "mmcblk0" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
1f00 131072 mtdblock0 (driver?)
1f01 32768 mtdblock1 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
ie the mmc driver no longer instantiates. Reverting the patch fixes the problem.
Bisect log is attached.
Guenter
---
# bad: [64d9a3617b3b8bc0734ba97caeb433b7019c6187] Add linux-next specific files for 20160212
# good: [388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95] Linux 4.5-rc3
git bisect start 'HEAD' 'v4.5-rc3'
# good: [597dc9d36e8bc04941b61b26ac7aa3f8a33aba53] Merge remote-tracking branch 'sound-asoc/for-next'
git bisect good 597dc9d36e8bc04941b61b26ac7aa3f8a33aba53
# bad: [91fe8ea815243ec595753ccf7e14126b6f87f2bf] Merge remote-tracking branch 'usb-chipidea-next/ci-for-usb-next'
git bisect bad 91fe8ea815243ec595753ccf7e14126b6f87f2bf
# good: [1d6796e67f265e835bcb1a19d27ba0433dbd75e4] Merge remote-tracking branch 'tip/auto-latest'
git bisect good 1d6796e67f265e835bcb1a19d27ba0433dbd75e4
# bad: [858163465b53ab87c3939cae9e6fd0ecbeb60bfa] Merge remote-tracking branch 'driver-core/driver-core-next'
git bisect bad 858163465b53ab87c3939cae9e6fd0ecbeb60bfa
# good: [5acd4c7ca23549bf4e480a92efb7d87d988be432] Merge remote-tracking branch 'kvm-arm/next'
git bisect good 5acd4c7ca23549bf4e480a92efb7d87d988be432
# good: [d28003ab55e09323bf1a026e804165c6d371ae6b] Merge remote-tracking branch 'drivers-x86/for-next'
git bisect good d28003ab55e09323bf1a026e804165c6d371ae6b
# good: [f28a8693f4b1eb8b4035167825f2bcd44bd95546] Merge remote-tracking branch 'hsi/for-next'
git bisect good f28a8693f4b1eb8b4035167825f2bcd44bd95546
# good: [d3a7387f8aae81ba0f3687518a9ad7a14bfb165d] Merge remote-tracking branch 'ipmi/for-next'
git bisect good d3a7387f8aae81ba0f3687518a9ad7a14bfb165d
# good: [75f3e8e47f381074801d0034874d20c638d9e3d9] firmware: introduce sysfs driver for QEMU's fw_cfg device
git bisect good 75f3e8e47f381074801d0034874d20c638d9e3d9
# good: [9e5b3d6f7f946a3fb4d83ac2ab6d2bfefcdafffb] drivers: dma-coherent: simplify dma_init_coherent_memory return value
git bisect good 9e5b3d6f7f946a3fb4d83ac2ab6d2bfefcdafffb
# good: [cf68d85529f7dccc24412887d46e364f4b422a5d] driver-core: platform: fix typo in documentation for multi-driver helper
git bisect good cf68d85529f7dccc24412887d46e364f4b422a5d
# bad: [67d02a1bbb334558e9380409a3cd426b36d4578b] driver-core: platform: probe of-devices only using list of compatibles
git bisect bad 67d02a1bbb334558e9380409a3cd426b36d4578b
# first bad commit: [67d02a1bbb334558e9380409a3cd426b36d4578b] driver-core: platform: probe of-devices only using list of compatibles
^ permalink raw reply
* Re: next: sparc64 crashes due to 'blk-mq: dynamic h/w context count'
From: Ming Lei @ 2016-02-14 15:14 UTC (permalink / raw)
To: Guenter Roeck
Cc: Keith Busch, Linux Kernel Mailing List, Jens Axboe, linux-block,
linux-next@vger.kernel.org
In-Reply-To: <20160214131704.GA19659@roeck-us.net>
On Sun, Feb 14, 2016 at 9:17 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> Hi,
>
> my runtime tests of linux-next crash for sparc64 due to commit 'blk-mq: dynamic
> h/w context count'. Reverting the patch fixes the problem. Bisect log is
> attached below. Full crash log is available at http://kerneltests.org/builders,
> in the table with qemu test results.
Guenter, could you test patch in the following link to see if it can be fixed?
http://marc.info/?l=linux-kernel&m=145526562410555&w=2
Thanks,
>
> Guenter
>
> ---
> crash log:
>
> [ 2.470860] Unable to handle kernel paging request at virtual address ffffffffffffe000
> [ 2.471099] tsk->{mm,active_mm}->context = 0000000000000000
> [ 2.471263] tsk->{mm,active_mm}->pgd = fffff80000402000
> [ 2.471416] \|/ ____ \|/
> [ 2.471416] "@'/ .. \`@"
> [ 2.471416] /_| \__/ |_\
> [ 2.471416] \__U_/
> [ 2.471848] bioset(350): Oops [#1]
> [ 2.472072] CPU: 0 PID: 350 Comm: bioset Not tainted 4.5.0-rc3-next-20160212 #1
> [ 2.472418] task: fffff8001f2369e0 ti: fffff8001f354000 task.ti: fffff8001f354000
> [ 2.472641] TSTATE: 0000008080e01603 TPC: 0000000000470d70 TNPC: 0000000000470d74 Y: 00000016 Not tainted
> [ 2.472933] TPC: <rescuer_thread+0x70/0x2c0>
> [ 2.473062] g0: fffff8001f2369e0 g1: 0000000000000000 g2: 0000000004208060 g3: 0000000000000000
> [ 2.473304] g4: fffff8001f2369e0 g5: 0000000000000000 g6: fffff8001f354000 g7: 0000000004000000
> [ 2.473546] o0: 0000000000000000 o1: ffffffffffffffec o2: 0000000000000008 o3: 0000000000015ab9
> [ 2.473788] o4: 0000000000a11800 o5: 0000000000000000 sp: fffff8001f3574e1 ret_pc: 0000000000470d4c
> [ 2.474039] RPC: <rescuer_thread+0x4c/0x2c0>
> [ 2.474176] l0: fffff8001f213800 l1: fffff8001f213870 l2: 0000000000a16000 l3: 0000000000000000
> [ 2.474426] l4: 0000000000000001 l5: 0000000000a66000 l6: 0000000000000001 l7: 000000000096c990
> [ 2.474671] i0: fffff8001f3328d0 i1: 0000000000000000 i2: 0000000000abab10 i3: 0000000000000082
> [ 2.474915] i4: 0000000000a25e58 i5: fffff8001f3328a0 i6: fffff8001f3575a1 i7: 0000000000475b48
> [ 2.475171] I7: <kthread+0xa8/0xe0>
> [ 2.475292] Call Trace:
> [ 2.475400] [0000000000475b48] kthread+0xa8/0xe0
> [ 2.475547] [0000000000405fa4] ret_from_fork+0x1c/0x2c
> [ 2.475729] [0000000000000000] (null)
> [ 2.475879] Disabling lock debugging due to kernel taint
> [ 2.476063] Caller[0000000000475b48]: kthread+0xa8/0xe0
> [ 2.476228] Caller[0000000000405fa4]: ret_from_fork+0x1c/0x2c
> [ 2.476392] Caller[0000000000000000]: (null)
> [ 2.476545] Instruction DUMP: 02600070 01000000 f25c2070 <f45e7f80> b6067f80 c0710000 c25e6008 c45e4000 c270a008
> [ 2.477010] Unable to handle kernel paging request at virtual address ffffffffffffe000
> [ 2.477233] tsk->{mm,active_mm}->context = 0000000000000000
> [ 2.477388] tsk->{mm,active_mm}->pgd = fffff80000402000
> [ 2.477533] \|/ ____ \|/
> [ 2.477533] "@'/ .. \`@"
> [ 2.477533] /_| \__/ |_\
> [ 2.477533] \__U_/
> [ 2.477941] bioset(350): Oops [#2]
> [ 2.478085] CPU: 0 PID: 350 Comm: bioset Tainted: G D 4.5.0-rc3-next-20160212 #1
> [ 2.478333] task: fffff8001f2369e0 ti: fffff8001f354000 task.ti: fffff8001f354000
> [ 2.478550] TSTATE: 0000000011e01603 TPC: 0000000000476148 TNPC: 00000000004717b0 Y: 00000190 Tainted: G D
> [ 2.478854] TPC: <kthread_data+0x8/0x20>
> [ 2.478969] g0: fffff8001f357790 g1: 0000000000000000 g2: 000000000420806c g3: 0000000000000004
> [ 2.479207] g4: fffff8001f2369e0 g5: 0000000000000000 g6: fffff8001f354000 g7: ffffffffffd23940
> [ 2.479449] o0: fffff8001f2369e0 o1: fffff8001f2369e0 o2: 0000000000a11800 o3: 00000000000166b9
> [ 2.479687] o4: 0000000000a11800 o5: 0000000000a11a18 sp: fffff8001f356e71 ret_pc: 00000000004717a8
> [ 2.479937] RPC: <wq_worker_sleeping+0x8/0xc0>
> [ 2.480064] l0: 000000000000007b l1: 0000000000abceb0 l2: 0000000000000080 l3: 0000000000000005
> [ 2.480305] l4: 0000000000002290 l5: 0000000000afac00 l6: 0000000000000000 l7: 0000000000000000
> [ 2.480554] i0: 0000000000000000 i1: 0000000000000000 i2: 0000000000000001 i3: 000000000000015e
> [ 2.480795] i4: 000000000000000e i5: 000000000000000e i6: fffff8001f356f21 i7: 00000000008b7e4c
> [ 2.481039] I7: <switch_to_pc+0xa0/0x394>
> [ 2.481154] Call Trace:
> [ 2.481231] [00000000008b7e4c] switch_to_pc+0xa0/0x394
> [ 2.481380] [00000000008b825c] schedule+0x1c/0xa0
> [ 2.481519] [000000000045e218] do_exit+0x578/0x9a0
> [ 2.481659] [0000000000427b78] die_if_kernel+0x198/0x320
> [ 2.481813] [00000000008bb848] unhandled_fault+0x8c/0xa4
> [ 2.481968] [00000000008bbe68] do_sparc64_fault+0x608/0x720
> [ 2.482128] [0000000000407ac4] sparc64_realfault_common+0x10/0x20
> [ 2.482316] [0000000000470d70] rescuer_thread+0x70/0x2c0
> [ 2.482477] [0000000000475b48] kthread+0xa8/0xe0
> [ 2.482613] [0000000000405fa4] ret_from_fork+0x1c/0x2c
> [ 2.482759] [0000000000000000] (null)
> [ 2.482897] Caller[00000000008b7e4c]: switch_to_pc+0xa0/0x394
> [ 2.483064] Caller[00000000008b825c]: schedule+0x1c/0xa0
> [ 2.483218] Caller[000000000045e218]: do_exit+0x578/0x9a0
> [ 2.483374] Caller[0000000000427b78]: die_if_kernel+0x198/0x320
> [ 2.483544] Caller[00000000008bb848]: unhandled_fault+0x8c/0xa4
> [ 2.483714] Caller[00000000008bbe68]: do_sparc64_fault+0x608/0x720
> [ 2.483891] Caller[0000000000407ac4]: sparc64_realfault_common+0x10/0x20
> [ 2.484081] Caller[0000000000470d4c]: rescuer_thread+0x4c/0x2c0
> [ 2.484251] Caller[0000000000475b48]: kthread+0xa8/0xe0
> [ 2.484402] Caller[0000000000405fa4]: ret_from_fork+0x1c/0x2c
> [ 2.484565] Caller[0000000000000000]: (null)
>
> ---
> bisect log:
>
> # bad: [64d9a3617b3b8bc0734ba97caeb433b7019c6187] Add linux-next specific files for 20160212
> # good: [527e9316f8ec44bd53d90fb9f611fa7ffff52bb9] Linux 4.4-rc4
> git bisect start 'HEAD' 'v4.4-rc4'
> # good: [12768c1e2c83b05ea1658470045789a14b6edf4c] Merge tag 'linux-kselftest-4.5-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> git bisect good 12768c1e2c83b05ea1658470045789a14b6edf4c
> # good: [fbb8c963573926bceb5c59e2a7d74e5ce7669e78] staging: sm750fb, fix typos
> git bisect good fbb8c963573926bceb5c59e2a7d74e5ce7669e78
> # good: [5973e9b7adaf8719bbaf6d124102dc4d6b87aaf4] Merge remote-tracking branch 'drm-panel/drm/panel/for-next'
> git bisect good 5973e9b7adaf8719bbaf6d124102dc4d6b87aaf4
> # bad: [dfe494eecfeddbc0b88acc9e618e7942105d4885] Merge remote-tracking branch 'tty/tty-next'
> git bisect bad dfe494eecfeddbc0b88acc9e618e7942105d4885
> # bad: [c461e79ad7bad110246651b5381542b9cd3cacdb] Merge remote-tracking branch 'spi/for-next'
> git bisect bad c461e79ad7bad110246651b5381542b9cd3cacdb
> # good: [597dc9d36e8bc04941b61b26ac7aa3f8a33aba53] Merge remote-tracking branch 'sound-asoc/for-next'
> git bisect good 597dc9d36e8bc04941b61b26ac7aa3f8a33aba53
> # bad: [84d5092d655bc9532c5fc88e7b2308090889187d] Merge remote-tracking branch 'kgdb/kgdb-next'
> git bisect bad 84d5092d655bc9532c5fc88e7b2308090889187d
> # good: [48513b689dbd263a60211b06addd5dfcab2fee71] dt/bindings: mmc: Add bindings for PIC32 SDHCI host controller
> git bisect good 48513b689dbd263a60211b06addd5dfcab2fee71
> # bad: [36942f9b4e473650cc648d4e287e959f8050e053] Merge remote-tracking branch 'block/for-next'
> git bisect bad 36942f9b4e473650cc648d4e287e959f8050e053
> # bad: [9f46f4ba39e45de3623c8b38b15dceed220a8e62] Merge branch 'for-4.6/drivers' into for-next
> git bisect bad 9f46f4ba39e45de3623c8b38b15dceed220a8e62
> # bad: [cde0dbe0c98f1d95646b59561e413dad8500fae9] Merge branch 'for-4.6/core' into for-next
> git bisect bad cde0dbe0c98f1d95646b59561e413dad8500fae9
> # good: [a257ae3e482e1cbd5fc573efeef5a73bffe09757] cfq-iosched: Allow sync noidle workloads to preempt each other
> git bisect good a257ae3e482e1cbd5fc573efeef5a73bffe09757
> # good: [f42cf119bcf8c8c9a2748a3c587aa76bc5af7405] Merge branch 'for-4.6/core' into for-next
> git bisect good f42cf119bcf8c8c9a2748a3c587aa76bc5af7405
> # bad: [868f2f0b72068a097508b6e8870a8950fd8eb7ef] blk-mq: dynamic h/w context count
> git bisect bad 868f2f0b72068a097508b6e8870a8950fd8eb7ef
> # first bad commit: [868f2f0b72068a097508b6e8870a8950fd8eb7ef] blk-mq: dynamic h/w context count
> --
> To unsubscribe from this list: send the line "unsubscribe linux-block" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Ming Lei
^ permalink raw reply
* next: sparc64 crashes due to 'blk-mq: dynamic h/w context count'
From: Guenter Roeck @ 2016-02-14 13:17 UTC (permalink / raw)
To: Keith Busch; +Cc: linux-kernel, Jens Axboe, linux-block, linux-next
Hi,
my runtime tests of linux-next crash for sparc64 due to commit 'blk-mq: dynamic
h/w context count'. Reverting the patch fixes the problem. Bisect log is
attached below. Full crash log is available at http://kerneltests.org/builders,
in the table with qemu test results.
Guenter
---
crash log:
[ 2.470860] Unable to handle kernel paging request at virtual address ffffffffffffe000
[ 2.471099] tsk->{mm,active_mm}->context = 0000000000000000
[ 2.471263] tsk->{mm,active_mm}->pgd = fffff80000402000
[ 2.471416] \|/ ____ \|/
[ 2.471416] "@'/ .. \`@"
[ 2.471416] /_| \__/ |_\
[ 2.471416] \__U_/
[ 2.471848] bioset(350): Oops [#1]
[ 2.472072] CPU: 0 PID: 350 Comm: bioset Not tainted 4.5.0-rc3-next-20160212 #1
[ 2.472418] task: fffff8001f2369e0 ti: fffff8001f354000 task.ti: fffff8001f354000
[ 2.472641] TSTATE: 0000008080e01603 TPC: 0000000000470d70 TNPC: 0000000000470d74 Y: 00000016 Not tainted
[ 2.472933] TPC: <rescuer_thread+0x70/0x2c0>
[ 2.473062] g0: fffff8001f2369e0 g1: 0000000000000000 g2: 0000000004208060 g3: 0000000000000000
[ 2.473304] g4: fffff8001f2369e0 g5: 0000000000000000 g6: fffff8001f354000 g7: 0000000004000000
[ 2.473546] o0: 0000000000000000 o1: ffffffffffffffec o2: 0000000000000008 o3: 0000000000015ab9
[ 2.473788] o4: 0000000000a11800 o5: 0000000000000000 sp: fffff8001f3574e1 ret_pc: 0000000000470d4c
[ 2.474039] RPC: <rescuer_thread+0x4c/0x2c0>
[ 2.474176] l0: fffff8001f213800 l1: fffff8001f213870 l2: 0000000000a16000 l3: 0000000000000000
[ 2.474426] l4: 0000000000000001 l5: 0000000000a66000 l6: 0000000000000001 l7: 000000000096c990
[ 2.474671] i0: fffff8001f3328d0 i1: 0000000000000000 i2: 0000000000abab10 i3: 0000000000000082
[ 2.474915] i4: 0000000000a25e58 i5: fffff8001f3328a0 i6: fffff8001f3575a1 i7: 0000000000475b48
[ 2.475171] I7: <kthread+0xa8/0xe0>
[ 2.475292] Call Trace:
[ 2.475400] [0000000000475b48] kthread+0xa8/0xe0
[ 2.475547] [0000000000405fa4] ret_from_fork+0x1c/0x2c
[ 2.475729] [0000000000000000] (null)
[ 2.475879] Disabling lock debugging due to kernel taint
[ 2.476063] Caller[0000000000475b48]: kthread+0xa8/0xe0
[ 2.476228] Caller[0000000000405fa4]: ret_from_fork+0x1c/0x2c
[ 2.476392] Caller[0000000000000000]: (null)
[ 2.476545] Instruction DUMP: 02600070 01000000 f25c2070 <f45e7f80> b6067f80 c0710000 c25e6008 c45e4000 c270a008
[ 2.477010] Unable to handle kernel paging request at virtual address ffffffffffffe000
[ 2.477233] tsk->{mm,active_mm}->context = 0000000000000000
[ 2.477388] tsk->{mm,active_mm}->pgd = fffff80000402000
[ 2.477533] \|/ ____ \|/
[ 2.477533] "@'/ .. \`@"
[ 2.477533] /_| \__/ |_\
[ 2.477533] \__U_/
[ 2.477941] bioset(350): Oops [#2]
[ 2.478085] CPU: 0 PID: 350 Comm: bioset Tainted: G D 4.5.0-rc3-next-20160212 #1
[ 2.478333] task: fffff8001f2369e0 ti: fffff8001f354000 task.ti: fffff8001f354000
[ 2.478550] TSTATE: 0000000011e01603 TPC: 0000000000476148 TNPC: 00000000004717b0 Y: 00000190 Tainted: G D
[ 2.478854] TPC: <kthread_data+0x8/0x20>
[ 2.478969] g0: fffff8001f357790 g1: 0000000000000000 g2: 000000000420806c g3: 0000000000000004
[ 2.479207] g4: fffff8001f2369e0 g5: 0000000000000000 g6: fffff8001f354000 g7: ffffffffffd23940
[ 2.479449] o0: fffff8001f2369e0 o1: fffff8001f2369e0 o2: 0000000000a11800 o3: 00000000000166b9
[ 2.479687] o4: 0000000000a11800 o5: 0000000000a11a18 sp: fffff8001f356e71 ret_pc: 00000000004717a8
[ 2.479937] RPC: <wq_worker_sleeping+0x8/0xc0>
[ 2.480064] l0: 000000000000007b l1: 0000000000abceb0 l2: 0000000000000080 l3: 0000000000000005
[ 2.480305] l4: 0000000000002290 l5: 0000000000afac00 l6: 0000000000000000 l7: 0000000000000000
[ 2.480554] i0: 0000000000000000 i1: 0000000000000000 i2: 0000000000000001 i3: 000000000000015e
[ 2.480795] i4: 000000000000000e i5: 000000000000000e i6: fffff8001f356f21 i7: 00000000008b7e4c
[ 2.481039] I7: <switch_to_pc+0xa0/0x394>
[ 2.481154] Call Trace:
[ 2.481231] [00000000008b7e4c] switch_to_pc+0xa0/0x394
[ 2.481380] [00000000008b825c] schedule+0x1c/0xa0
[ 2.481519] [000000000045e218] do_exit+0x578/0x9a0
[ 2.481659] [0000000000427b78] die_if_kernel+0x198/0x320
[ 2.481813] [00000000008bb848] unhandled_fault+0x8c/0xa4
[ 2.481968] [00000000008bbe68] do_sparc64_fault+0x608/0x720
[ 2.482128] [0000000000407ac4] sparc64_realfault_common+0x10/0x20
[ 2.482316] [0000000000470d70] rescuer_thread+0x70/0x2c0
[ 2.482477] [0000000000475b48] kthread+0xa8/0xe0
[ 2.482613] [0000000000405fa4] ret_from_fork+0x1c/0x2c
[ 2.482759] [0000000000000000] (null)
[ 2.482897] Caller[00000000008b7e4c]: switch_to_pc+0xa0/0x394
[ 2.483064] Caller[00000000008b825c]: schedule+0x1c/0xa0
[ 2.483218] Caller[000000000045e218]: do_exit+0x578/0x9a0
[ 2.483374] Caller[0000000000427b78]: die_if_kernel+0x198/0x320
[ 2.483544] Caller[00000000008bb848]: unhandled_fault+0x8c/0xa4
[ 2.483714] Caller[00000000008bbe68]: do_sparc64_fault+0x608/0x720
[ 2.483891] Caller[0000000000407ac4]: sparc64_realfault_common+0x10/0x20
[ 2.484081] Caller[0000000000470d4c]: rescuer_thread+0x4c/0x2c0
[ 2.484251] Caller[0000000000475b48]: kthread+0xa8/0xe0
[ 2.484402] Caller[0000000000405fa4]: ret_from_fork+0x1c/0x2c
[ 2.484565] Caller[0000000000000000]: (null)
---
bisect log:
# bad: [64d9a3617b3b8bc0734ba97caeb433b7019c6187] Add linux-next specific files for 20160212
# good: [527e9316f8ec44bd53d90fb9f611fa7ffff52bb9] Linux 4.4-rc4
git bisect start 'HEAD' 'v4.4-rc4'
# good: [12768c1e2c83b05ea1658470045789a14b6edf4c] Merge tag 'linux-kselftest-4.5-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
git bisect good 12768c1e2c83b05ea1658470045789a14b6edf4c
# good: [fbb8c963573926bceb5c59e2a7d74e5ce7669e78] staging: sm750fb, fix typos
git bisect good fbb8c963573926bceb5c59e2a7d74e5ce7669e78
# good: [5973e9b7adaf8719bbaf6d124102dc4d6b87aaf4] Merge remote-tracking branch 'drm-panel/drm/panel/for-next'
git bisect good 5973e9b7adaf8719bbaf6d124102dc4d6b87aaf4
# bad: [dfe494eecfeddbc0b88acc9e618e7942105d4885] Merge remote-tracking branch 'tty/tty-next'
git bisect bad dfe494eecfeddbc0b88acc9e618e7942105d4885
# bad: [c461e79ad7bad110246651b5381542b9cd3cacdb] Merge remote-tracking branch 'spi/for-next'
git bisect bad c461e79ad7bad110246651b5381542b9cd3cacdb
# good: [597dc9d36e8bc04941b61b26ac7aa3f8a33aba53] Merge remote-tracking branch 'sound-asoc/for-next'
git bisect good 597dc9d36e8bc04941b61b26ac7aa3f8a33aba53
# bad: [84d5092d655bc9532c5fc88e7b2308090889187d] Merge remote-tracking branch 'kgdb/kgdb-next'
git bisect bad 84d5092d655bc9532c5fc88e7b2308090889187d
# good: [48513b689dbd263a60211b06addd5dfcab2fee71] dt/bindings: mmc: Add bindings for PIC32 SDHCI host controller
git bisect good 48513b689dbd263a60211b06addd5dfcab2fee71
# bad: [36942f9b4e473650cc648d4e287e959f8050e053] Merge remote-tracking branch 'block/for-next'
git bisect bad 36942f9b4e473650cc648d4e287e959f8050e053
# bad: [9f46f4ba39e45de3623c8b38b15dceed220a8e62] Merge branch 'for-4.6/drivers' into for-next
git bisect bad 9f46f4ba39e45de3623c8b38b15dceed220a8e62
# bad: [cde0dbe0c98f1d95646b59561e413dad8500fae9] Merge branch 'for-4.6/core' into for-next
git bisect bad cde0dbe0c98f1d95646b59561e413dad8500fae9
# good: [a257ae3e482e1cbd5fc573efeef5a73bffe09757] cfq-iosched: Allow sync noidle workloads to preempt each other
git bisect good a257ae3e482e1cbd5fc573efeef5a73bffe09757
# good: [f42cf119bcf8c8c9a2748a3c587aa76bc5af7405] Merge branch 'for-4.6/core' into for-next
git bisect good f42cf119bcf8c8c9a2748a3c587aa76bc5af7405
# bad: [868f2f0b72068a097508b6e8870a8950fd8eb7ef] blk-mq: dynamic h/w context count
git bisect bad 868f2f0b72068a097508b6e8870a8950fd8eb7ef
# first bad commit: [868f2f0b72068a097508b6e8870a8950fd8eb7ef] blk-mq: dynamic h/w context count
^ permalink raw reply
* Re: linux-next: Tree for Feb 12
From: Sudip Mukherjee @ 2016-02-13 18:55 UTC (permalink / raw)
To: Borislav Petkov, Andy Lutomirski
Cc: Guenter Roeck, Stephen Rothwell, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, Andy Lutomirski, Ingo Molnar
In-Reply-To: <20160213155028.GA17704@pd.tnic>
On Saturday 13 February 2016 09:20 PM, Borislav Petkov wrote:
> On Sat, Feb 13, 2016 at 06:57:24AM -0800, Andy Lutomirski wrote:
>> I think Borislav's patch should fix this.
>
> Yeah, guys, can you give it a try:
>
> https://lkml.kernel.org/r/20160210145116.GF23914@pd.tnic
Its late night in our time so I could only test with i386 defconfig and
it builds fine with gcc-4.6.3
regards
sudip
^ permalink raw reply
* Re: linux-next: Tree for Feb 12
From: Borislav Petkov @ 2016-02-13 15:50 UTC (permalink / raw)
To: Andy Lutomirski
Cc: Guenter Roeck, Sudip Mukherjee, Stephen Rothwell,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Lutomirski, Ingo Molnar
In-Reply-To: <CALCETrUWRJR5=4sXsg=KYX6mYRrXkvXSOgccX+PVQa7dHXQYxw@mail.gmail.com>
On Sat, Feb 13, 2016 at 06:57:24AM -0800, Andy Lutomirski wrote:
> I think Borislav's patch should fix this.
Yeah, guys, can you give it a try:
https://lkml.kernel.org/r/20160210145116.GF23914@pd.tnic
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
^ permalink raw reply
* Re: linux-next: Tree for Feb 12
From: Andy Lutomirski @ 2016-02-13 14:57 UTC (permalink / raw)
To: Guenter Roeck
Cc: Sudip Mukherjee, Stephen Rothwell, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, Andy Lutomirski, Ingo Molnar
In-Reply-To: <20160213074935.GA27448@roeck-us.net>
On Fri, Feb 12, 2016 at 11:49 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> On Fri, Feb 12, 2016 at 11:32:42AM +0530, Sudip Mukherjee wrote:
>> On Fri, Feb 12, 2016 at 04:20:35PM +1100, Stephen Rothwell wrote:
>> > Hi all,
>> >
>> > Changes since 20160211:
>>
>> since last few days with gcc-4.6.3, x86_64 and i386 defconfig and
>> allmodconfig builds are failing with the error:
>> "arch/x86/include/asm/tlbflush.h:26:18: error: memory input 0 is not
>> directly addressable"
>>
>> But with gcc-4.8.2 and later it builds fine. Should I try to bisect and
>> find the problem or its not worth for gcc-4.6.3 ?
>>
> Bisect log attached. Looks like older versions of gcc (or at least 4.6.3)
> don't like the newly introduced __invpcid().
>
> Guenter
>
> ---
> # bad: [64d9a3617b3b8bc0734ba97caeb433b7019c6187] Add linux-next specific files for 20160212
> # good: [388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95] Linux 4.5-rc3
> git bisect start 'HEAD' 'v4.5-rc3'
> # good: [597dc9d36e8bc04941b61b26ac7aa3f8a33aba53] Merge remote-tracking branch 'sound-asoc/for-next'
> git bisect good 597dc9d36e8bc04941b61b26ac7aa3f8a33aba53
> # bad: [91fe8ea815243ec595753ccf7e14126b6f87f2bf] Merge remote-tracking branch 'usb-chipidea-next/ci-for-usb-next'
> git bisect bad 91fe8ea815243ec595753ccf7e14126b6f87f2bf
> # bad: [1d6796e67f265e835bcb1a19d27ba0433dbd75e4] Merge remote-tracking branch 'tip/auto-latest'
> git bisect bad 1d6796e67f265e835bcb1a19d27ba0433dbd75e4
> # good: [4abecd5aab4960c786530db5ce4ca332ceba2b73] Merge branch 'x86/microcode'
> git bisect good 4abecd5aab4960c786530db5ce4ca332ceba2b73
> # good: [84d5092d655bc9532c5fc88e7b2308090889187d] Merge remote-tracking branch 'kgdb/kgdb-next'
> git bisect good 84d5092d655bc9532c5fc88e7b2308090889187d
> # good: [e4e0cfcfc9fd3885ff7dadfb5a4b553495d011e4] Merge remote-tracking branch 'iommu/next'
> git bisect good e4e0cfcfc9fd3885ff7dadfb5a4b553495d011e4
> # good: [e908e75fc3833b413837aca4667db96c372c843e] Merge remote-tracking branch 'spi/topic/ti-qspi' into spi-next
> git bisect good e908e75fc3833b413837aca4667db96c372c843e
> # good: [88e2211191dabe9ae2a953d5a4326d3e4b7f2901] Merge remote-tracking branch 'trivial/for-next'
> git bisect good 88e2211191dabe9ae2a953d5a4326d3e4b7f2901
> # good: [d12a72b844a49d4162f24cefdab30bed3f86730e] x86/mm: Add a 'noinvpcid' boot option to turn off INVPCID
> git bisect good d12a72b844a49d4162f24cefdab30bed3f86730e
> # good: [a135746b7d4386c17290e0344440101d037e86f8] Merge remote-tracking branch 'dt-rh/for-next'
> git bisect good a135746b7d4386c17290e0344440101d037e86f8
> # bad: [ce1143aa60273220a9f89012f2aaaed04f97e9a2] x86/dmi: Switch dmi_remap() from ioremap() [uncached] to ioremap_cache()
> git bisect bad ce1143aa60273220a9f89012f2aaaed04f97e9a2
> # bad: [d8bced79af1db6734f66b42064cc773cada2ce99] x86/mm: If INVPCID is available, use it to flush global mappings
> git bisect bad d8bced79af1db6734f66b42064cc773cada2ce99
> # first bad commit: [d8bced79af1db6734f66b42064cc773cada2ce99] x86/mm: If INVPCID is available, use it to flush global mappings
I think Borislav's patch should fix this.
--Andy
--
Andy Lutomirski
AMA Capital Management, LLC
^ permalink raw reply
* Re: linux-next: Tree for Feb 12
From: Guenter Roeck @ 2016-02-13 7:49 UTC (permalink / raw)
To: Sudip Mukherjee
Cc: Stephen Rothwell, linux-next, linux-kernel, Andy Lutomirski,
Ingo Molnar
In-Reply-To: <20160212060241.GA1390@sudip-pc>
On Fri, Feb 12, 2016 at 11:32:42AM +0530, Sudip Mukherjee wrote:
> On Fri, Feb 12, 2016 at 04:20:35PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20160211:
>
> since last few days with gcc-4.6.3, x86_64 and i386 defconfig and
> allmodconfig builds are failing with the error:
> "arch/x86/include/asm/tlbflush.h:26:18: error: memory input 0 is not
> directly addressable"
>
> But with gcc-4.8.2 and later it builds fine. Should I try to bisect and
> find the problem or its not worth for gcc-4.6.3 ?
>
Bisect log attached. Looks like older versions of gcc (or at least 4.6.3)
don't like the newly introduced __invpcid().
Guenter
---
# bad: [64d9a3617b3b8bc0734ba97caeb433b7019c6187] Add linux-next specific files for 20160212
# good: [388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95] Linux 4.5-rc3
git bisect start 'HEAD' 'v4.5-rc3'
# good: [597dc9d36e8bc04941b61b26ac7aa3f8a33aba53] Merge remote-tracking branch 'sound-asoc/for-next'
git bisect good 597dc9d36e8bc04941b61b26ac7aa3f8a33aba53
# bad: [91fe8ea815243ec595753ccf7e14126b6f87f2bf] Merge remote-tracking branch 'usb-chipidea-next/ci-for-usb-next'
git bisect bad 91fe8ea815243ec595753ccf7e14126b6f87f2bf
# bad: [1d6796e67f265e835bcb1a19d27ba0433dbd75e4] Merge remote-tracking branch 'tip/auto-latest'
git bisect bad 1d6796e67f265e835bcb1a19d27ba0433dbd75e4
# good: [4abecd5aab4960c786530db5ce4ca332ceba2b73] Merge branch 'x86/microcode'
git bisect good 4abecd5aab4960c786530db5ce4ca332ceba2b73
# good: [84d5092d655bc9532c5fc88e7b2308090889187d] Merge remote-tracking branch 'kgdb/kgdb-next'
git bisect good 84d5092d655bc9532c5fc88e7b2308090889187d
# good: [e4e0cfcfc9fd3885ff7dadfb5a4b553495d011e4] Merge remote-tracking branch 'iommu/next'
git bisect good e4e0cfcfc9fd3885ff7dadfb5a4b553495d011e4
# good: [e908e75fc3833b413837aca4667db96c372c843e] Merge remote-tracking branch 'spi/topic/ti-qspi' into spi-next
git bisect good e908e75fc3833b413837aca4667db96c372c843e
# good: [88e2211191dabe9ae2a953d5a4326d3e4b7f2901] Merge remote-tracking branch 'trivial/for-next'
git bisect good 88e2211191dabe9ae2a953d5a4326d3e4b7f2901
# good: [d12a72b844a49d4162f24cefdab30bed3f86730e] x86/mm: Add a 'noinvpcid' boot option to turn off INVPCID
git bisect good d12a72b844a49d4162f24cefdab30bed3f86730e
# good: [a135746b7d4386c17290e0344440101d037e86f8] Merge remote-tracking branch 'dt-rh/for-next'
git bisect good a135746b7d4386c17290e0344440101d037e86f8
# bad: [ce1143aa60273220a9f89012f2aaaed04f97e9a2] x86/dmi: Switch dmi_remap() from ioremap() [uncached] to ioremap_cache()
git bisect bad ce1143aa60273220a9f89012f2aaaed04f97e9a2
# bad: [d8bced79af1db6734f66b42064cc773cada2ce99] x86/mm: If INVPCID is available, use it to flush global mappings
git bisect bad d8bced79af1db6734f66b42064cc773cada2ce99
# first bad commit: [d8bced79af1db6734f66b42064cc773cada2ce99] x86/mm: If INVPCID is available, use it to flush global mappings
^ permalink raw reply
* Re: next-20160208 perf build error "tests/bp_signal.c:106:47: error: declaration of ‘signal’ shadows a global declaration [-Werror=shadow]"
From: Arnaldo Carvalho de Melo @ 2016-02-12 21:40 UTC (permalink / raw)
To: Vinson Lee; +Cc: linux-next, Peter Zijlstra, Ingo Molnar, Wang Nan, Jiri Olsa
In-Reply-To: <20160211222121.GK32168@kernel.org>
Em Thu, Feb 11, 2016 at 07:21:21PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Mon, Feb 08, 2016 at 10:28:53AM -0800, Vinson Lee escreveu:
> > I hit this perf build error with next-20160208 with GCC 4.6.
> I try to test on a rhel6 vm from time to time, need to do it using
> docker or something, thanks for the report, but can you please send a
> proper patch, with a:
>
> Fixes: 6a7d550e8b2e ("perf test: Check environment before start real BPF test")
>
> Line, signed-off, etc?
Do it next time please, I did this time, when testing other changes on
my rhel6.7 vm, its in my perf/core branch,
Thanks,
- arnaldo
^ permalink raw reply
* Re: linux-next: Tree for Feb 12
From: Sudip Mukherjee @ 2016-02-12 14:27 UTC (permalink / raw)
To: Kees Cook, Ard Biesheuvel, Russell King
Cc: linux-next-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA, Stephen Rothwell,
kernel-testers-u79uwXL29TY76Z2rM5mHXA
In-Reply-To: <20160212162035.1e0260cd-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
On Fri, Feb 12, 2016 at 04:20:35PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160211:
arm lpc18xx_defconfig build fails with the error:
./arch/arm/kernel/vmlinux.lds:702: undefined symbol `SECTION_SHIFT'
referenced in expression
bisect leads to:
64ac2e74f0b2 ("ARM: 8502/1: mm: mark section-aligned portion of rodata NX")
reverting that patch fixed the build.
build log at:
https://travis-ci.org/sudipm-mukherjee/parport/jobs/108716281
regards
sudip
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox