Re: [alsa-devel] linux-next: Tree for Oct 17 (soundwire)
On 10/17/19 10:22 AM, Randy Dunlap wrote: On 10/16/19 9:26 PM, Stephen Rothwell wrote: Hi all, Changes since 20191016: on x86_64: # CONFIG_BLOCK is not set CC [M] drivers/soundwire/intel_init.o In file included from ../drivers/soundwire/intel_init.c:12:0: ../include/linux/iomap.h: In function ‘iomap_sector’: ../include/linux/iomap.h:76:48: error: ‘SECTOR_SHIFT’ undeclared (first use in this function); did you mean ‘SECTIONS_SHIFT’? return (iomap->addr + pos - iomap->offset) >> SECTOR_SHIFT; ^~~~ SECTIONS_SHIFT Yes, looks like by fixing cross-compilation issues I added new ones. We can either add an explicit dependency on CONFIG_BLOCK or remove the use of ioread32() and use readl() instead. I didn't write the initial code and I have no idea what the intent behind using ioread32 was.
Re: linux-next: Tree for Oct 17 (soundwire)
On 10/16/19 9:26 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20191016: > on x86_64: # CONFIG_BLOCK is not set CC [M] drivers/soundwire/intel_init.o In file included from ../drivers/soundwire/intel_init.c:12:0: ../include/linux/iomap.h: In function ‘iomap_sector’: ../include/linux/iomap.h:76:48: error: ‘SECTOR_SHIFT’ undeclared (first use in this function); did you mean ‘SECTIONS_SHIFT’? return (iomap->addr + pos - iomap->offset) >> SECTOR_SHIFT; ^~~~ SECTIONS_SHIFT -- ~Randy
linux-next: Tree for Oct 17
Hi all, Changes since 20191016: Non-merge commits (relative to Linus' tree): 4283 4317 files changed, 145570 insertions(+), 67942 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, an allmodconfig 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 and pseries_le_defconfig and i386, sparc and sparc64 defconfig. And finally, a simple boot test of the powerpc pseries_le_defconfig kernel in qemu (with and without kvm enabled). Below is a summary of the state of the merge. I am currently merging 315 trees (counting Linus' and 78 trees of bug fix patches pending for the current merge release). 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 (bc88f85c6c09 kthread: make __kthread_queue_delayed_work static) Merging fixes/master (54ecb8f7028c Linux 5.4-rc1) Merging kbuild-current/fixes (991b78fbd223 scripts: setlocalversion: fix a bashism) Merging arc-current/for-curr (41277ba7eb4e ARC: mm: tlb flush optim: elide redundant uTLB invalidates for MMUv3) Merging arm-current/fixes (4c0742f65b4e ARM: 8914/1: NOMMU: Fix exc_ret for XIP) Merging arm-soc-fixes/arm/fixes (dd163ca3fb49 Merge tag 'mvebu-fixes-5.4-1' of git://git.infradead.org/linux-mvebu into arm/fixes) Merging arm64-fixes/for-next/fixes (597399d0cb91 arm64: tags: Preserve tags for addresses translated via TTBR1) Merging m68k-current/for-linus (0f1979b402df m68k: Remove ioremap_fullcache()) Merging powerpc-fixes/fixes (2272905a4580 spufs: fix a crash in spufs_create_root()) Merging s390-fixes/fixes (062795fcdcb2 s390/uaccess: avoid (false positive) compiler warnings) Merging sparc/master (038029c03e21 sparc: remove unneeded uapi/asm/statfs.h) Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2) Merging net/master (2ca4f6ca4562 rxrpc: use rcu protection while reading sk->sk_user_data) Merging bpf/master (9e8acd9c44a0 bpf: lwtunnel: Fix reroute supplying invalid dst) Merging ipsec/master (68ce6688a5ba net: sched: taprio: Fix potential integer overflow in taprio_set_picos_per_byte) Merging netfilter/master (503c9addef61 ptp: fix typo of "mechanism" in Kconfig help text) Merging ipvs/master (503c9addef61 ptp: fix typo of "mechanism" in Kconfig help text) Merging wireless-drivers/master (d79749f7716d ath10k: fix latency issue for QCA988x) Merging mac80211/master (82ad862115c2 Merge branch 'smc-fixes') Merging rdma-fixes/for-rc (0417791536ae RDMA/mlx5: Add missing synchronize_srcu() for MW cases) Merging sound-current/for-linus (130bce3afbbb ALSA: hdac: clear link output stream mapping) Merging sound-asoc-fixes/for-linus (a4ff7dff4e65 Merge branch 'asoc-5.4' into asoc-linus) Merging regmap-fixes/for-linus (da0c9ea146cb Linux 5.4-rc2) Merging regulator-fixes/for-linus (68a2d13c4d54 Merge branch 'regulator-5.4' into regulator-linus) Merging spi-fixes/for-linus (09ee9e1664ba Merge branch 'spi-5.4' into spi-linus) Merging pci-current/for-linus (54ecb8f7028c Linux 5.4-rc1) Merging driver-core.current/driver-core-linus (82af5b660967 sysfs: Fixes __BIN_ATTR_WO() macro) Merging tty.current/tty-linus (f50b6805dbb9 8250-men-mcb: fix error checking when get_num_ports returns -ENODEV) Merging usb.current/usb-linus (7a7591979748 USB: usblp: fix use-after-free on disconnect) Merging usb-gadget-fixes/fixes (4a56a478a525 usb: gadget: mass_storage: Fix races between fsg_disable and fsg_set_alt) Merging usb-serial-fixes/usb-linus (bc25770f00d3 USB: serial: ti_usb_3410_5052: clean up serial data access) Merging usb-chipidea-fixes/ci-for-usb-stable (16009db47c51 usb: chipidea: udc: workaround for endpoint conflict issue) Merging phy/fixes (68eeb39a53d5 phy: qcom-usb-hs: Fix extcon double register after power cycle) Merging sta
Re: linux-next: Tree for Oct 17 (x86; jump labels ?; x86 macros?; ; )
On 10/16/18 11:06 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20181016: > Some randconfigs have a problem on x86 (1 of 10 on i386, 1 of 10 on x86_64 for my overnight randconfig builds). (thousands of lines of errors on each $arch) I don't know that the config combination that causes this is. The failing x86_64 randconfig is attached. CC arch/x86/crypto/glue_helper.o In file included from ../include/linux/export.h:45:0, from ../include/linux/linkage.h:7, from ../include/linux/kernel.h:7, from ../include/linux/list.h:9, from ../include/linux/module.h:9, from ../arch/x86/crypto/glue_helper.c:28: ../arch/x86/include/asm/qspinlock.h: In function ‘queued_fetch_set_pending_acquire’: ../arch/x86/include/asm/rmwcc.h:23:17: error: jump into statement expression : clobbers : cc_label);\ ^ ../include/linux/compiler.h:58:42: note: in definition of macro ‘__trace_if’ if (__builtin_constant_p(!!(cond)) ? !!(cond) : \ ^ ../arch/x86/include/asm/qspinlock.h:18:2: note: in expansion of macro ‘if’ if (GEN_BINARY_RMWcc(LOCK_PREFIX "btsl", lock->val.counter, c, ^ ../arch/x86/include/asm/rmwcc.h:21:2: note: in expansion of macro ‘asm_volatile_goto’ asm_volatile_goto (fullop "; j" #cc " %l[cc_label]" \ ^ ../arch/x86/include/asm/rmwcc.h:54:2: note: in expansion of macro ‘__GEN_RMWcc’ __GEN_RMWcc(op " %[val], " arg0, var, cc, \ ^ ../arch/x86/include/asm/rmwcc.h:58:2: note: in expansion of macro ‘GEN_BINARY_RMWcc_6’ GEN_BINARY_RMWcc_6(op, var, cc, vcon, val, "%[var]") ^ ../arch/x86/include/asm/rmwcc.h:9:30: note: in expansion of macro ‘GEN_BINARY_RMWcc_5’ #define __RMWcc_CONCAT(a, b) a ## b ^ ../arch/x86/include/asm/rmwcc.h:10:28: note: in expansion of macro ‘__RMWcc_CONCAT’ #define RMWcc_CONCAT(a, b) __RMWcc_CONCAT(a, b) ^ ../arch/x86/include/asm/rmwcc.h:60:32: note: in expansion of macro ‘RMWcc_CONCAT’ #define GEN_BINARY_RMWcc(X...) RMWcc_CONCAT(GEN_BINARY_RMWcc_, RMWcc_ARGS(X))(X) ^ ../arch/x86/include/asm/qspinlock.h:18:6: note: in expansion of macro ‘GEN_BINARY_RMWcc’ if (GEN_BINARY_RMWcc(LOCK_PREFIX "btsl", lock->val.counter, c, ^ ../arch/x86/include/asm/rmwcc.h:25:1: note: label ‘cc_label’ defined here cc_label: c = true; \ ^ ../include/linux/compiler.h:58:30: note: in definition of macro ‘__trace_if’ if (__builtin_constant_p(!!(cond)) ? !!(cond) : \ ^ ../arch/x86/include/asm/qspinlock.h:18:2: note: in expansion of macro ‘if’ if (GEN_BINARY_RMWcc(LOCK_PREFIX "btsl", lock->val.counter, c, ^ ../arch/x86/include/asm/rmwcc.h:54:2: note: in expansion of macro ‘__GEN_RMWcc’ __GEN_RMWcc(op " %[val], " arg0, var, cc, \ ^ ../arch/x86/include/asm/rmwcc.h:58:2: note: in expansion of macro ‘GEN_BINARY_RMWcc_6’ GEN_BINARY_RMWcc_6(op, var, cc, vcon, val, "%[var]") ^ ../arch/x86/include/asm/rmwcc.h:9:30: note: in expansion of macro ‘GEN_BINARY_RMWcc_5’ #define __RMWcc_CONCAT(a, b) a ## b ^ ../arch/x86/include/asm/rmwcc.h:10:28: note: in expansion of macro ‘__RMWcc_CONCAT’ #define RMWcc_CONCAT(a, b) __RMWcc_CONCAT(a, b) ^ ../arch/x86/include/asm/rmwcc.h:60:32: note: in expansion of macro ‘RMWcc_CONCAT’ #define GEN_BINARY_RMWcc(X...) RMWcc_CONCAT(GEN_BINARY_RMWcc_, RMWcc_ARGS(X))(X) ^ ../arch/x86/include/asm/qspinlock.h:18:6: note: in expansion of macro ‘GEN_BINARY_RMWcc’ if (GEN_BINARY_RMWcc(LOCK_PREFIX "btsl", lock->val.counter, c, ^ ../arch/x86/include/asm/rmwcc.h:25:1: error: duplicate label ‘cc_label’ cc_label: c = true; \ ^ ../include/linux/compiler.h:58:42: note: in definition of macro ‘__trace_if’ if (__builtin_constant_p(!!(cond)) ? !!(cond) : \ ^ ../arch/x86/include/asm/qspinlock.h:18:2: note: in expansion of macro ‘if’ if (GEN_BINARY_RMWcc(LOCK_PREFIX "btsl", lock->val.counter, c, ^ ../arch/x86/include/asm/rmwcc.h:54:2: note: in expansion of macro ‘__GEN_RMWcc’ __GEN_RMWcc(op " %[val], " arg0, var, cc, \ ^ ../arch/x86/include/asm/rmwcc.h:58:2: note: in expansion of macro ‘GEN_BINARY_RMWcc_6’ GEN_BINARY_RMWcc_6(op, var, cc, vcon, val, "%[var]") ^ ../arch/x86/include/asm/rmwcc.h:9:30: note: in expansion of macro ‘GEN_BINARY_RMWcc_5’ #define __RMWcc_CONCAT(a, b) a ## b ^ ../arch/x86/include/asm/rmwcc.h:10:28: note: in expansion of macro ‘__RMWcc_CONCAT’ #define RMWcc_CONCAT(a, b) __RMWcc_CONCAT(a, b) ^ ../arch/x86/include/asm/rmwcc.h:60:32: note: in expansion of macro ‘RMWcc_CONCAT’ #define GEN_BINARY_RMWcc(X...) RMWcc_CONCAT(GEN_BINARY_RMWcc_, RMWcc_ARGS(X))(X) ^ ../arch/x86/include/asm/qspinlock.h:18:6: no
linux-next: Tree for Oct 17
Hi all, Changes since 20181016: The net-next tree gained a conflict against the net tree. The netfilter-next tree lost its build failure. The char-misc tree gained a conflict against the drm tree. Non-merge commits (relative to Linus' tree): 10826 9851 files changed, 513320 insertions(+), 221735 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, an allmodconfig 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 and pseries_le_defconfig and i386, sparc and sparc64 defconfig. And finally, a simple boot test of the powerpc pseries_le_defconfig kernel in qemu (with and without kvm enabled). Below is a summary of the state of the merge. I am currently merging 291 trees (counting Linus' and 66 trees of bug fix patches pending for the current merge release). 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 (b955a910d7fd Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc) Merging fixes/master (eb81bfb224ce Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input) Merging kbuild-current/fixes (5318321d367c samples: disable CONFIG_SAMPLES for UML) Merging arc-current/for-curr (56d02dd9e794 ARC: IOC: panic if kernel was started with previously enabled IOC) Merging arm-current/fixes (3a58ac65e2d7 ARM: 8799/1: mm: fix pci_ioremap_io() offset check) Merging arm64-fixes/for-next/fixes (ca2b497253ad arm64: perf: Reject stand-alone CHAIN events for PMUv3) Merging m68k-current/for-linus (0986b16ab49b m68k/mac: Use correct PMU response format) Merging powerpc-fixes/fixes (ac1788cc7da4 powerpc/numa: Skip onlining a offline node in kdump path) Merging sparc/master (b955a910d7fd Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc) Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2) Merging net/master (0ac1077e3a54 sctp: get pr_assoc and pr_stream all status with SCTP_PR_SCTP_ALL instead) Merging bpf/master (bd8be2cf8b69 Merge branch 'nfp-fix-pedit-set-action-offloads') Merging ipsec/master (9d200fd1 xfrm: policy: use hlist rcu variants on insert) Merging netfilter/master (cb20f2d2c050 netfilter: xt_nat: fix DNAT target for shifted portmap ranges) Merging ipvs/master (feb9f55c33e5 netfilter: nft_dynset: allow dynamic updates of non-anonymous set) Merging wireless-drivers/master (3baafeffa48a iwlwifi: 1000: set the TFD queue size) Merging mac80211/master (8d0be26c781a mac80211_hwsim: fix module init error paths for netlink) Merging rdma-fixes/for-rc (dd9a40349570 IB/mlx5: Unmap DMA addr from HCA before IOMMU) Merging sound-current/for-linus (709ae62e8e6d ALSA: hda/realtek - Cannot adjust speaker's volume on Dell XPS 27 7760) Merging sound-asoc-fixes/for-linus (212e5fa13415 Merge branch 'asoc-4.19' into asoc-linus) Merging regmap-fixes/for-linus (7876320f8880 Linux 4.19-rc4) Merging regulator-fixes/for-linus (35a7f35ad1b1 Linux 4.19-rc8) Merging spi-fixes/for-linus (6e21bb549bb4 Merge branch 'spi-4.19' into spi-linus) Merging pci-current/for-linus (2edab4df98d9 PCI: Expand the "PF" acronym in Kconfig help text) Merging driver-core.current/driver-core-linus (7876320f8880 Linux 4.19-rc4) Merging tty.current/tty-linus (202dc3cc10b4 serial: sh-sci: Fix receive on SCIFA/SCIFB variants with DMA) Merging usb.current/usb-linus (665c365a77fb USB: fix the usbfs flag sanitization for control transfers) Merging usb-gadget-fixes/fixes (d9707490077b usb: dwc2: Fix call location of dwc2_check_core_endianness) Merging usb-serial-fixes/usb-linus (0238df646e62 Linux 4.19-rc7) Merging usb-chipidea-fixes/ci-for-usb-stable (a930d8bd94d8 usb: chipidea: Always build ULPI code) Merging phy/fixes (5b394b2ddf03 Linux 4.19-rc1) Merging s
linux-next: Tree for Oct 17
Hi all, Changes since 20161016: The akpm-current tree still had its build failures for which I applied 2 patches. Non-merge commits (relative to Linus' tree): 770 999 files changed, 29247 insertions(+), 16481 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 243 trees (counting Linus' and 34 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 (1001354ca341 Linux 4.9-rc1) Merging fixes/master (30066ce675d3 Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6) Merging kbuild-current/rc-fixes (d3e2773c4ede builddeb: Skip gcc-plugins when not configured) Merging arc-current/for-curr (8df0cc75f530 ARC: [build] Support gz, lzma compressed uImage) Merging arm-current/fixes (fb833b1fbb68 ARM: fix delays) Merging m68k-current/for-linus (6736e65effc3 m68k: Migrate exception table users off module.h and onto extable.h) Merging metag-fixes/fixes (35d04077ad96 metag: Only define atomic_dec_if_positive conditionally) Merging powerpc-fixes/fixes (b79331a5eb9f powerpc/powernv/pci: Fix m64 checks for SR-IOV and window alignment) Merging sparc/master (4c1fad64eff4 Merge tag 'for-f2fs-4.9' of git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs) Merging net/master (fb5c6cfaec12 vmxnet3: avoid assumption about invalid dma_pa in vmxnet3_set_mc()) CONFLICT (content): Merge conflict in drivers/net/ethernet/qlogic/Kconfig Applying: qed*: merge fix for CONFIG_INFINIBAND_QEDR Kconfig move Merging ipsec/master (7f92083eb58f vti6: flush x-netns xfrm cache when vti interface is removed) Merging netfilter/master (6d3a4c404648 strparser: Propagate correct error code in strp_recv()) Merging ipvs/master (ea43f860d984 Merge branch 'ethoc-fixes') Merging wireless-drivers/master (1ea2643961b0 ath6kl: add Dell OEM SDIO I/O for the Venue 8 Pro) Merging mac80211/master (1d4de2e222b4 mac80211: fix CMD_FRAME for AP_VLAN) Merging sound-current/for-linus (fdd8218d7d1b ALSA: line6: fix a crash in line6_hwdep_write()) Merging pci-current/for-linus (035ee288ae7a PCI: Fix bridge_d3 update on device removal) Merging driver-core.current/driver-core-linus (b66484cd7470 Merge branch 'akpm' (patches from Andrew)) Merging tty.current/tty-linus (b66484cd7470 Merge branch 'akpm' (patches from Andrew)) Merging usb.current/usb-linus (b66484cd7470 Merge branch 'akpm' (patches from Andrew)) Merging usb-gadget-fixes/fixes (d8a4100ddc75 usb: gadget: udc: atmel: fix endpoint name) Merging usb-serial-fixes/usb-linus (f190fd92458d USB: serial: simple: add support for another Infineon flashloader) Merging usb-chipidea-fixes/ci-for-usb-stable (6b7f456e67a1 usb: chipidea: host: fix NULL ptr dereference during shutdown) Merging staging.current/staging-linus (1001354ca341 Linux 4.9-rc1) Merging char-misc.current/char-misc-linus (b66484cd7470 Merge branch 'akpm' (patches from Andrew)) Merging input-current/for-linus (1134ca268e73 Merge branch 'next' into for-linus) Merging crypto-current/master (c3afafa47898 Merge git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6) Merging ide/master (797cee982eef Merge branch 'stable-4.8' of git://git.infradead.org/users/pcmoore/audit) Merging rr-fixes/fixes (8244062ef1e5 modules: fix longstanding /proc/kallsyms vs module insertion race.) Merging vfio-fixes/for-linus (c8952a707556 vfio/pci: Fix NULL pointer oops in error interrupt setup hand
linux-next: Tree for Oct 17
Hi all, Please do not add any material intended for v3.19 to your linux-next included trees until after v3.18-rc1 has been released. Changes since 20141016: The thermal tree still had its build failure for which I reverted a commit. The kvm-arm tree gained a conflict against Linus' tree. The akpm-current tree lost its build failure. Non-merge commits (relative to Linus' tree): 1129 1098 files changed, 32868 insertions(+), 16497 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 for x86_64 and a multi_v7_defconfig for arm. After the final fixups (if any), it is also built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and allyesconfig (this fails its final link) and i386, sparc, sparc64 and arm defconfig. Below is a summary of the state of the merge. I am currently merging 225 trees (counting Linus' and 32 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 Rothwells...@canb.auug.org.au $ git checkout master $ git reset --hard stable Merging origin/master (0429fbc0bdc2 Merge branch 'for-3.18-consistent-ops' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu) Merging fixes/master (b94d525e58dc Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net) Merging kbuild-current/rc-fixes (7d1311b93e58 Linux 3.17-rc1) Merging arc-current/for-curr (2ce7598c9a45 Linux 3.17-rc4) Merging arm-current/fixes (ad684dce87fa ARM: 8179/1: kprobes-test: Fix compile error "bad immediate value for offset") Merging m68k-current/for-linus (24cae7934cf1 m68k: Reformat arch/m68k/mm/hwtest.c) Merging metag-fixes/fixes (ffe6902b66aa asm-generic: remove _STK_LIM_MAX) Merging mips-fixes/mips-fixes (1795cd9b3a91 Linux 3.16-rc5) Merging powerpc-merge/merge (396a34340cdf powerpc: Fix endianness of flash_block_list in rtas_flash) Merging powerpc-merge-mpe/for-linus (aeba3731b150 powerpc/pci: Fix IO space breakage after of_pci_range_to_resource() change) Merging sparc/master (f4da3628dc7c sparc64: Fix FPU register corruption with AES crypto offload.) Merging net/master (2c6ba4b15b5e netlink: fix description of portid) Merging ipsec/master (b8c203b2d2fc xfrm: Generate queueing routes only from route lookup functions) Merging sound-current/for-linus (c8b00fd2f4c5 ALSA: hda_intel: Add Device IDs for Intel Sunrise Point PCH) Merging pci-current/for-linus (8c33e57e6fb3 Merge branch 'remove-weak-function-declarations' into for-linus) Merging wireless/master (f8adaf0ae978 brcmfmac: Fix off by one bug in brcmf_count_20mhz_channels()) Merging driver-core.current/driver-core-linus (5e40d331bd72 Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security) Merging tty.current/tty-linus (9e82bf014195 Linux 3.17-rc5) Merging usb.current/usb-linus (0f33be009b89 Linux 3.17-rc6) Merging usb-gadget-fixes/fixes (0b93a4c838fa usb: dwc3: fix TRB completion when multiple TRBs are started) Merging usb-serial-fixes/usb-linus (dee80ad12d2b USB: cp210x: add support for Seluxit USB dongle) Merging staging.current/staging-linus (80213c03c415 Merge tag 'pci-v3.18-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci) Merging char-misc.current/char-misc-linus (9e82bf014195 Linux 3.17-rc5) Merging input-current/for-linus (4dfb15cd5aaa Input: xpad - add Thrustmaster as Xbox 360 controller vendor) Merging md-current/for-linus (d47648fcf061 raid5: avoid finding "discard" stripe) Merging crypto-current/master (be34c4ef693f crypto: sha - Handle unaligned input data in generic sha256 and sha512.) Merging ide/master (7546e52b5e3d Drivers: ide: Remove typedef atiixp_ide_timing) Merging dwmw2/master (5950f0803ca9 pcmcia: remove RPX board stuff) Merging devicetree-current/devicetree/merge (e66c98c7a0ea of: Fix NULL dereference in selftest removal code) Merging rr-fixes/fixes (f49819560f53 virtio-rng: skip reading when we start to remove the device) Merging
Re: linux-next: Tree for Oct 17 (pinctrl-single.c)
On 10/18/13 17:39, Tony Lindgren wrote: > * Tony Lindgren [131018 16:49]: >> * Randy Dunlap [131018 16:41]: >>> On 10/18/13 16:39, Tony Lindgren wrote: Looks like we need a little bit of arch specific handling with the generic IRQ. Fix the issue with an ifdef the same way as other drivers do. ARM needs things set to IRQF_VALID, which also then sets noprobe. Others seem to use just irq_set_noprobe(). Otherwise we can get: drivers/pinctrl/pinctrl-single.c: In function 'pcs_irqdomain_map': drivers/pinctrl/pinctrl-single.c:1750:2: error: implicit declaration of function 'set_irq_flags' [-Werror=implicit-function-declaration] >>> >>> Did you address this error? I don't see a fix for it... >> >> Yes set_irq_flags() is defined for ARM archs in >> arch/arm/include/asm/hw_irq.h which is included from >> include/linux/irq.h as . So the ifdef >> below takes care of that too. >> +#ifdef CONFIG_ARM + set_irq_flags(irq, IRQF_VALID); +#else + irq_set_noprobe(irq); +#endif > > OK I've sent the pull request and Olof has now pulled the fix > into arm-soc next/dt branch. Thanks. Acked-by: Randy Dunlap -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 17 (pinctrl-single.c)
* Tony Lindgren [131018 16:49]: > * Randy Dunlap [131018 16:41]: > > On 10/18/13 16:39, Tony Lindgren wrote: > > > > > > Looks like we need a little bit of arch specific handling > > > with the generic IRQ. Fix the issue with an ifdef the > > > same way as other drivers do. > > > > > > ARM needs things set to IRQF_VALID, which also then sets > > > noprobe. Others seem to use just irq_set_noprobe(). > > > > > > Otherwise we can get: > > > > > > drivers/pinctrl/pinctrl-single.c: In function 'pcs_irqdomain_map': > > > drivers/pinctrl/pinctrl-single.c:1750:2: error: implicit declaration of > > > function 'set_irq_flags' [-Werror=implicit-function-declaration] > > > > Did you address this error? I don't see a fix for it... > > Yes set_irq_flags() is defined for ARM archs in > arch/arm/include/asm/hw_irq.h which is included from > include/linux/irq.h as . So the ifdef > below takes care of that too. > > > > +#ifdef CONFIG_ARM > > > + set_irq_flags(irq, IRQF_VALID); > > > +#else > > > + irq_set_noprobe(irq); > > > +#endif OK I've sent the pull request and Olof has now pulled the fix into arm-soc next/dt branch. Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 17 (pinctrl-single.c)
* Randy Dunlap [131018 16:41]: > On 10/18/13 16:39, Tony Lindgren wrote: > > > > Looks like we need a little bit of arch specific handling > > with the generic IRQ. Fix the issue with an ifdef the > > same way as other drivers do. > > > > ARM needs things set to IRQF_VALID, which also then sets > > noprobe. Others seem to use just irq_set_noprobe(). > > > > Otherwise we can get: > > > > drivers/pinctrl/pinctrl-single.c: In function 'pcs_irqdomain_map': > > drivers/pinctrl/pinctrl-single.c:1750:2: error: implicit declaration of > > function 'set_irq_flags' [-Werror=implicit-function-declaration] > > Did you address this error? I don't see a fix for it... Yes set_irq_flags() is defined for ARM archs in arch/arm/include/asm/hw_irq.h which is included from include/linux/irq.h as . So the ifdef below takes care of that too. > > +#ifdef CONFIG_ARM > > + set_irq_flags(irq, IRQF_VALID); > > +#else > > + irq_set_noprobe(irq); > > +#endif Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 17 (pinctrl-single.c)
On 10/18/13 16:39, Tony Lindgren wrote: > * Linus Walleij [131018 12:43]: >> On Fri, Oct 18, 2013 at 8:08 PM, Randy Dunlap wrote: >>> On 10/17/13 17:38, Mark Brown wrote: Hi all, I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131017 tag is also provided for convenience. One new conflict today but otherwise uneventful. x86_64 allmodconfigs build after each merge but no other build tests were done. >>> >>> on i386: >>> >>> drivers/pinctrl/pinctrl-single.c: In function 'pcs_irqdomain_map': >>> drivers/pinctrl/pinctrl-single.c:1750:2: error: implicit declaration of >>> function 'set_irq_flags' [-Werror=implicit-function-declaration] >>> drivers/pinctrl/pinctrl-single.c:1750:21: error: 'IRQF_VALID' undeclared >>> (first use in this function) >>> drivers/pinctrl/pinctrl-single.c:1750:34: error: 'IRQF_PROBE' undeclared >>> (first use in this function) >> >> H this looks like Tony's baby and the offending patch is >> not in the pinctrl tree, I bet he'll have a fix for it in no time. > > Ouch sorry about that. I'll send a pull request for the > following fix ASAP. Build tested with Randy's randconfig. > > Regards, > > Tony > > 8< > From: Tony Lindgren > Date: Fri, 18 Oct 2013 16:20:05 -0700 > Subject: [PATCH] pinctrl: single: Fix build when not built on ARM > > Looks like we need a little bit of arch specific handling > with the generic IRQ. Fix the issue with an ifdef the > same way as other drivers do. > > ARM needs things set to IRQF_VALID, which also then sets > noprobe. Others seem to use just irq_set_noprobe(). > > Otherwise we can get: > > drivers/pinctrl/pinctrl-single.c: In function 'pcs_irqdomain_map': > drivers/pinctrl/pinctrl-single.c:1750:2: error: implicit declaration of > function 'set_irq_flags' [-Werror=implicit-function-declaration] Did you address this error? I don't see a fix for it... Thanks. > drivers/pinctrl/pinctrl-single.c:1750:21: error: 'IRQF_VALID' undeclared > (first use in this function) > drivers/pinctrl/pinctrl-single.c:1750:34: error: 'IRQF_PROBE' undeclared > (first use in this function) > > Reported-by: Randy Dunlap > Signed-off-by: Tony Lindgren > > --- a/drivers/pinctrl/pinctrl-single.c > +++ b/drivers/pinctrl/pinctrl-single.c > @@ -1743,7 +1743,12 @@ static int pcs_irqdomain_map(struct irq_domain *d, > unsigned int irq, > irq_set_chip_data(irq, pcs_soc); > irq_set_chip_and_handler(irq, &pcs->chip, >handle_level_irq); > - set_irq_flags(irq, IRQF_VALID | IRQF_PROBE); > + > +#ifdef CONFIG_ARM > + set_irq_flags(irq, IRQF_VALID); > +#else > + irq_set_noprobe(irq); > +#endif > > return 0; > } > -- -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 17 (pinctrl-single.c)
* Linus Walleij [131018 12:43]: > On Fri, Oct 18, 2013 at 8:08 PM, Randy Dunlap wrote: > > On 10/17/13 17:38, Mark Brown wrote: > >> Hi all, > >> > >> I've uploaded today's linux-next tree to the master branch of the > >> repository below: > >> > >> git://gitorious.org/thierryreding/linux-next.git > >> > >> A next-20131017 tag is also provided for convenience. > >> > >> One new conflict today but otherwise uneventful. x86_64 allmodconfigs > >> build after each merge but no other build tests were done. > > > > on i386: > > > > drivers/pinctrl/pinctrl-single.c: In function 'pcs_irqdomain_map': > > drivers/pinctrl/pinctrl-single.c:1750:2: error: implicit declaration of > > function 'set_irq_flags' [-Werror=implicit-function-declaration] > > drivers/pinctrl/pinctrl-single.c:1750:21: error: 'IRQF_VALID' undeclared > > (first use in this function) > > drivers/pinctrl/pinctrl-single.c:1750:34: error: 'IRQF_PROBE' undeclared > > (first use in this function) > > H this looks like Tony's baby and the offending patch is > not in the pinctrl tree, I bet he'll have a fix for it in no time. Ouch sorry about that. I'll send a pull request for the following fix ASAP. Build tested with Randy's randconfig. Regards, Tony 8< From: Tony Lindgren Date: Fri, 18 Oct 2013 16:20:05 -0700 Subject: [PATCH] pinctrl: single: Fix build when not built on ARM Looks like we need a little bit of arch specific handling with the generic IRQ. Fix the issue with an ifdef the same way as other drivers do. ARM needs things set to IRQF_VALID, which also then sets noprobe. Others seem to use just irq_set_noprobe(). Otherwise we can get: drivers/pinctrl/pinctrl-single.c: In function 'pcs_irqdomain_map': drivers/pinctrl/pinctrl-single.c:1750:2: error: implicit declaration of function 'set_irq_flags' [-Werror=implicit-function-declaration] drivers/pinctrl/pinctrl-single.c:1750:21: error: 'IRQF_VALID' undeclared (first use in this function) drivers/pinctrl/pinctrl-single.c:1750:34: error: 'IRQF_PROBE' undeclared (first use in this function) Reported-by: Randy Dunlap Signed-off-by: Tony Lindgren --- a/drivers/pinctrl/pinctrl-single.c +++ b/drivers/pinctrl/pinctrl-single.c @@ -1743,7 +1743,12 @@ static int pcs_irqdomain_map(struct irq_domain *d, unsigned int irq, irq_set_chip_data(irq, pcs_soc); irq_set_chip_and_handler(irq, &pcs->chip, handle_level_irq); - set_irq_flags(irq, IRQF_VALID | IRQF_PROBE); + +#ifdef CONFIG_ARM + set_irq_flags(irq, IRQF_VALID); +#else + irq_set_noprobe(irq); +#endif return 0; } -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 17 (pinctrl-single.c)
On Fri, Oct 18, 2013 at 8:08 PM, Randy Dunlap wrote: > On 10/17/13 17:38, Mark Brown wrote: >> Hi all, >> >> I've uploaded today's linux-next tree to the master branch of the >> repository below: >> >> git://gitorious.org/thierryreding/linux-next.git >> >> A next-20131017 tag is also provided for convenience. >> >> One new conflict today but otherwise uneventful. x86_64 allmodconfigs >> build after each merge but no other build tests were done. > > on i386: > > drivers/pinctrl/pinctrl-single.c: In function 'pcs_irqdomain_map': > drivers/pinctrl/pinctrl-single.c:1750:2: error: implicit declaration of > function 'set_irq_flags' [-Werror=implicit-function-declaration] > drivers/pinctrl/pinctrl-single.c:1750:21: error: 'IRQF_VALID' undeclared > (first use in this function) > drivers/pinctrl/pinctrl-single.c:1750:34: error: 'IRQF_PROBE' undeclared > (first use in this function) H this looks like Tony's baby and the offending patch is not in the pinctrl tree, I bet he'll have a fix for it in no time. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 17
On Fri, Oct 18, 2013 at 9:22 AM, Kevin Hilman wrote: > On Fri, Oct 18, 2013 at 1:22 AM, Thierry Reding > wrote: >> On Fri, Oct 18, 2013 at 12:45:26AM -0700, Olof Johansson wrote: >>> On Fri, Oct 18, 2013 at 01:38:47AM +0100, Mark Brown wrote: >>> > Hi all, >>> > >>> > I've uploaded today's linux-next tree to the master branch of the >>> > repository below: >>> > >>> > git://gitorious.org/thierryreding/linux-next.git > >>> > A next-20131017 tag is also provided for convenience. >>> > >>> > One new conflict today but otherwise uneventful. x86_64 allmodconfigs >>> > build after each merge but no other build tests were done. >>> >>> Hi, >>> >>> I'm seeing a fairly large fallout on boot testing. See >>> http://lists.linaro.org/pipermail/kernel-build-reports/2013-October/000719.html >>> for full list (I need to start providing longer backlogs for failures, the >>> top >>> of the oopses is lost in the email). >>> >>> For example, on dove (SolidRun Cubox) I see: >>> >>> [0.707248] Unable to handle kernel NULL pointer dereference at virtual >>> address 0054 >>> [0.715297] pgd = c0004000 >>> [0.717984] [0054] *pgd= >>> [0.721548] Internal error: Oops: 5 [#1] ARM >>> [0.725794] Modules linked in: >>> [0.728841] CPU: 0 PID: 1 Comm: swapper Not tainted >>> 3.12.0-rc5-next-20131017 #1 >>> [0.736114] task: ef035c00 ti: ef036000 task.ti: ef036000 >>> [0.741497] PC is at kfree+0x54/0xc4 >>> [0.745063] LR is at ata_host_register+0x3c/0x290 >>> [0.749741] pc : []lr : []psr: 4193 >>> [0.749741] sp : ef037da8 ip : 0034 fp : >>> [0.761159] r10: r9 : ef061810 r8 : c0519fc8 >>> [0.766353] r7 : c0519fc8 r6 : a113 r5 : r4 : ef1c9dd0 >>> [0.772850] r3 : c0fc8fe0 r2 : c07c9000 r1 : 4000 r0 : >>> [0.779349] Flags: nZcv IRQs off FIQs on Mode SVC_32 ISA ARM >>> Segment kernel >>> [0.786708] Control: 10c5387d Table: 4019 DAC: 0015 >>> [0.792428] Process swapper (pid: 1, stack limit = 0xef036248) >>> [0.798234] Stack: (0xef037da8 to 0xef038000) >>> [0.957218] [] (kfree+0x54/0xc4) from [] >>> (ata_host_register+0x3c/0x290) >>> [0.965542] [] (ata_host_register+0x3c/0x290) from >>> [] (ata_host_activate+0xdc/0x118) >>> [0.974992] [] (ata_host_activate+0xdc/0x118) from >>> [] (mv_platform_probe+0x2dc/0x36c) >>> [0.984527] [] (mv_platform_probe+0x2dc/0x36c) from >>> [] (platform_drv_probe+0x18/0x48) >>> [0.994051] [] (platform_drv_probe+0x18/0x48) from >>> [] (really_probe+0x74/0x1fc) >>> [1.003062] [] (really_probe+0x74/0x1fc) from [] >>> (__driver_attach+0x98/0x9c) >>> [1.011804] [] (__driver_attach+0x98/0x9c) from [] >>> (bus_for_each_dev+0x60/0x94) >>> [1.020808] [] (bus_for_each_dev+0x60/0x94) from [] >>> (bus_add_driver+0x148/0x1f0) >>> [1.029898] [] (bus_add_driver+0x148/0x1f0) from [] >>> (driver_register+0x78/0xf8) >>> [1.038911] [] (driver_register+0x78/0xf8) from [] >>> (mv_init+0x30/0x50) >>> [1.047144] [] (mv_init+0x30/0x50) from [] >>> (do_one_initcall+0x100/0x14c) >>> [1.07] [] (do_one_initcall+0x100/0x14c) from [] >>> (kernel_init_freeable+0x120/0x1c0) >>> [1.065259] [] (kernel_init_freeable+0x120/0x1c0) from >>> [] (kernel_init+0x8/0x158) >>> [1.074441] [] (kernel_init+0x8/0x158) from [] >>> (ret_from_fork+0x14/0x3c) >>> [1.082841] Code: e0823283 e3110902 1593301c e593001c (e5904054) >>> >>> >>> I bisected it down to commit 55acc602faae7c10e53acdca0c70f4936c2539c6, which >>> is really weird. That is: >>> >>> commit 55acc602faae7c10e53acdca0c70f4936c2539c6 >>> Merge: e32face ba6857b >>> Author: Mark Brown >>> AuthorDate: Thu Oct 17 23:55:55 2013 +0100 >>> Commit: Mark Brown >>> CommitDate: Thu Oct 17 23:55:55 2013 +0100 >>> >>> Merge remote-tracking branch 'driver-core/driver-core-next' >>> >>> Conflicts: >>> include/linux/netdevice.h >>> >>> >>> But there isn't anything controversial in the merge commit. >>> >>> I tried checking out either side of that merge, and they both boot >>> fine. I redid the merge myself, and I get no delta compared to your >>> merge and I still get the same failure. >>> >>> I've got more failures than dove, I'll try bisecting a few of the others >>> in the morning (it's late here), hopefully they will help indicate what's >>> actually going wrong. I'm guessing something just happens to move around >>> enough to expose a different problem once the two branches are merged. >> >> Looking at that oops it seems like host is actually NULL when kfree() is >> called in ata_host_register(). That seems to only happen when freeing up >> any of the unused ports, which is strange in itself because Cubox seems >> to only register a single one. Also if host is indeed NULL, then things >> should go haywire much sooner. >> >> Looks like you won't easily find out what's going on here unless you get >> into it somewhat deeper and per
Re: linux-next: Tree for Oct 17
On Fri, Oct 18, 2013 at 9:22 AM, Kevin Hilman wrote: > On Fri, Oct 18, 2013 at 1:22 AM, Thierry Reding > wrote: >> On Fri, Oct 18, 2013 at 12:45:26AM -0700, Olof Johansson wrote: >>> On Fri, Oct 18, 2013 at 01:38:47AM +0100, Mark Brown wrote: >>> > Hi all, >>> > >>> > I've uploaded today's linux-next tree to the master branch of the >>> > repository below: >>> > >>> > git://gitorious.org/thierryreding/linux-next.git > >>> > A next-20131017 tag is also provided for convenience. >>> > >>> > One new conflict today but otherwise uneventful. x86_64 allmodconfigs >>> > build after each merge but no other build tests were done. >>> >>> Hi, >>> >>> I'm seeing a fairly large fallout on boot testing. See >>> http://lists.linaro.org/pipermail/kernel-build-reports/2013-October/000719.html >>> for full list (I need to start providing longer backlogs for failures, the >>> top >>> of the oopses is lost in the email). >>> >>> For example, on dove (SolidRun Cubox) I see: >>> >>> [0.707248] Unable to handle kernel NULL pointer dereference at virtual >>> address 0054 >>> [0.715297] pgd = c0004000 >>> [0.717984] [0054] *pgd= >>> [0.721548] Internal error: Oops: 5 [#1] ARM >>> [0.725794] Modules linked in: >>> [0.728841] CPU: 0 PID: 1 Comm: swapper Not tainted >>> 3.12.0-rc5-next-20131017 #1 >>> [0.736114] task: ef035c00 ti: ef036000 task.ti: ef036000 >>> [0.741497] PC is at kfree+0x54/0xc4 >>> [0.745063] LR is at ata_host_register+0x3c/0x290 >>> [0.749741] pc : []lr : []psr: 4193 >>> [0.749741] sp : ef037da8 ip : 0034 fp : >>> [0.761159] r10: r9 : ef061810 r8 : c0519fc8 >>> [0.766353] r7 : c0519fc8 r6 : a113 r5 : r4 : ef1c9dd0 >>> [0.772850] r3 : c0fc8fe0 r2 : c07c9000 r1 : 4000 r0 : >>> [0.779349] Flags: nZcv IRQs off FIQs on Mode SVC_32 ISA ARM >>> Segment kernel >>> [0.786708] Control: 10c5387d Table: 4019 DAC: 0015 >>> [0.792428] Process swapper (pid: 1, stack limit = 0xef036248) >>> [0.798234] Stack: (0xef037da8 to 0xef038000) >>> [0.957218] [] (kfree+0x54/0xc4) from [] >>> (ata_host_register+0x3c/0x290) >>> [0.965542] [] (ata_host_register+0x3c/0x290) from >>> [] (ata_host_activate+0xdc/0x118) >>> [0.974992] [] (ata_host_activate+0xdc/0x118) from >>> [] (mv_platform_probe+0x2dc/0x36c) >>> [0.984527] [] (mv_platform_probe+0x2dc/0x36c) from >>> [] (platform_drv_probe+0x18/0x48) >>> [0.994051] [] (platform_drv_probe+0x18/0x48) from >>> [] (really_probe+0x74/0x1fc) >>> [1.003062] [] (really_probe+0x74/0x1fc) from [] >>> (__driver_attach+0x98/0x9c) >>> [1.011804] [] (__driver_attach+0x98/0x9c) from [] >>> (bus_for_each_dev+0x60/0x94) >>> [1.020808] [] (bus_for_each_dev+0x60/0x94) from [] >>> (bus_add_driver+0x148/0x1f0) >>> [1.029898] [] (bus_add_driver+0x148/0x1f0) from [] >>> (driver_register+0x78/0xf8) >>> [1.038911] [] (driver_register+0x78/0xf8) from [] >>> (mv_init+0x30/0x50) >>> [1.047144] [] (mv_init+0x30/0x50) from [] >>> (do_one_initcall+0x100/0x14c) >>> [1.07] [] (do_one_initcall+0x100/0x14c) from [] >>> (kernel_init_freeable+0x120/0x1c0) >>> [1.065259] [] (kernel_init_freeable+0x120/0x1c0) from >>> [] (kernel_init+0x8/0x158) >>> [1.074441] [] (kernel_init+0x8/0x158) from [] >>> (ret_from_fork+0x14/0x3c) >>> [1.082841] Code: e0823283 e3110902 1593301c e593001c (e5904054) >>> >>> >>> I bisected it down to commit 55acc602faae7c10e53acdca0c70f4936c2539c6, which >>> is really weird. That is: >>> >>> commit 55acc602faae7c10e53acdca0c70f4936c2539c6 >>> Merge: e32face ba6857b >>> Author: Mark Brown >>> AuthorDate: Thu Oct 17 23:55:55 2013 +0100 >>> Commit: Mark Brown >>> CommitDate: Thu Oct 17 23:55:55 2013 +0100 >>> >>> Merge remote-tracking branch 'driver-core/driver-core-next' >>> >>> Conflicts: >>> include/linux/netdevice.h >>> >>> >>> But there isn't anything controversial in the merge commit. >>> >>> I tried checking out either side of that merge, and they both boot >>> fine. I redid the merge myself, and I get no delta compared to your >>> merge and I still get the same failure. >>> >>> I've got more failures than dove, I'll try bisecting a few of the others >>> in the morning (it's late here), hopefully they will help indicate what's >>> actually going wrong. I'm guessing something just happens to move around >>> enough to expose a different problem once the two branches are merged. >> >> Looking at that oops it seems like host is actually NULL when kfree() is >> called in ata_host_register(). That seems to only happen when freeing up >> any of the unused ports, which is strange in itself because Cubox seems >> to only register a single one. Also if host is indeed NULL, then things >> should go haywire much sooner. >> >> Looks like you won't easily find out what's going on here unless you get >> into it somewhat deeper and per
Re: linux-next: Tree for Oct 17
On Fri, Oct 18, 2013 at 1:22 AM, Thierry Reding wrote: > On Fri, Oct 18, 2013 at 12:45:26AM -0700, Olof Johansson wrote: >> On Fri, Oct 18, 2013 at 01:38:47AM +0100, Mark Brown wrote: >> > Hi all, >> > >> > I've uploaded today's linux-next tree to the master branch of the >> > repository below: >> > >> > git://gitorious.org/thierryreding/linux-next.git > >> > A next-20131017 tag is also provided for convenience. >> > >> > One new conflict today but otherwise uneventful. x86_64 allmodconfigs >> > build after each merge but no other build tests were done. >> >> Hi, >> >> I'm seeing a fairly large fallout on boot testing. See >> http://lists.linaro.org/pipermail/kernel-build-reports/2013-October/000719.html >> for full list (I need to start providing longer backlogs for failures, the >> top >> of the oopses is lost in the email). >> >> For example, on dove (SolidRun Cubox) I see: >> >> [0.707248] Unable to handle kernel NULL pointer dereference at virtual >> address 0054 >> [0.715297] pgd = c0004000 >> [0.717984] [0054] *pgd= >> [0.721548] Internal error: Oops: 5 [#1] ARM >> [0.725794] Modules linked in: >> [0.728841] CPU: 0 PID: 1 Comm: swapper Not tainted >> 3.12.0-rc5-next-20131017 #1 >> [0.736114] task: ef035c00 ti: ef036000 task.ti: ef036000 >> [0.741497] PC is at kfree+0x54/0xc4 >> [0.745063] LR is at ata_host_register+0x3c/0x290 >> [0.749741] pc : []lr : []psr: 4193 >> [0.749741] sp : ef037da8 ip : 0034 fp : >> [0.761159] r10: r9 : ef061810 r8 : c0519fc8 >> [0.766353] r7 : c0519fc8 r6 : a113 r5 : r4 : ef1c9dd0 >> [0.772850] r3 : c0fc8fe0 r2 : c07c9000 r1 : 4000 r0 : >> [0.779349] Flags: nZcv IRQs off FIQs on Mode SVC_32 ISA ARM Segment >> kernel >> [0.786708] Control: 10c5387d Table: 4019 DAC: 0015 >> [0.792428] Process swapper (pid: 1, stack limit = 0xef036248) >> [0.798234] Stack: (0xef037da8 to 0xef038000) >> [0.957218] [] (kfree+0x54/0xc4) from [] >> (ata_host_register+0x3c/0x290) >> [0.965542] [] (ata_host_register+0x3c/0x290) from [] >> (ata_host_activate+0xdc/0x118) >> [0.974992] [] (ata_host_activate+0xdc/0x118) from [] >> (mv_platform_probe+0x2dc/0x36c) >> [0.984527] [] (mv_platform_probe+0x2dc/0x36c) from >> [] (platform_drv_probe+0x18/0x48) >> [0.994051] [] (platform_drv_probe+0x18/0x48) from [] >> (really_probe+0x74/0x1fc) >> [1.003062] [] (really_probe+0x74/0x1fc) from [] >> (__driver_attach+0x98/0x9c) >> [1.011804] [] (__driver_attach+0x98/0x9c) from [] >> (bus_for_each_dev+0x60/0x94) >> [1.020808] [] (bus_for_each_dev+0x60/0x94) from [] >> (bus_add_driver+0x148/0x1f0) >> [1.029898] [] (bus_add_driver+0x148/0x1f0) from [] >> (driver_register+0x78/0xf8) >> [1.038911] [] (driver_register+0x78/0xf8) from [] >> (mv_init+0x30/0x50) >> [1.047144] [] (mv_init+0x30/0x50) from [] >> (do_one_initcall+0x100/0x14c) >> [1.07] [] (do_one_initcall+0x100/0x14c) from [] >> (kernel_init_freeable+0x120/0x1c0) >> [1.065259] [] (kernel_init_freeable+0x120/0x1c0) from >> [] (kernel_init+0x8/0x158) >> [1.074441] [] (kernel_init+0x8/0x158) from [] >> (ret_from_fork+0x14/0x3c) >> [1.082841] Code: e0823283 e3110902 1593301c e593001c (e5904054) >> >> >> I bisected it down to commit 55acc602faae7c10e53acdca0c70f4936c2539c6, which >> is really weird. That is: >> >> commit 55acc602faae7c10e53acdca0c70f4936c2539c6 >> Merge: e32face ba6857b >> Author: Mark Brown >> AuthorDate: Thu Oct 17 23:55:55 2013 +0100 >> Commit: Mark Brown >> CommitDate: Thu Oct 17 23:55:55 2013 +0100 >> >> Merge remote-tracking branch 'driver-core/driver-core-next' >> >> Conflicts: >> include/linux/netdevice.h >> >> >> But there isn't anything controversial in the merge commit. >> >> I tried checking out either side of that merge, and they both boot >> fine. I redid the merge myself, and I get no delta compared to your >> merge and I still get the same failure. >> >> I've got more failures than dove, I'll try bisecting a few of the others >> in the morning (it's late here), hopefully they will help indicate what's >> actually going wrong. I'm guessing something just happens to move around >> enough to expose a different problem once the two branches are merged. > > Looking at that oops it seems like host is actually NULL when kfree() is > called in ata_host_register(). That seems to only happen when freeing up > any of the unused ports, which is strange in itself because Cubox seems > to only register a single one. Also if host is indeed NULL, then things > should go haywire much sooner. > > Looks like you won't easily find out what's going on here unless you get > into it somewhat deeper and perhaps trace what exactly fails and why the > NULL pointer is even there in the first place. For me, bisect has fingered the patch below[1]. Reverting that gets i.MX6 w
Re: linux-next: Tree for Oct 17
On 10/18/2013 12:45 AM, Olof Johansson wrote: On Fri, Oct 18, 2013 at 01:38:47AM +0100, Mark Brown wrote: Hi all, I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git > A next-20131017 tag is also provided for convenience. One new conflict today but otherwise uneventful. x86_64 allmodconfigs build after each merge but no other build tests were done. Hi, I'm seeing a fairly large fallout on boot testing. See http://lists.linaro.org/pipermail/kernel-build-reports/2013-October/000719.html for full list (I need to start providing longer backlogs for failures, the top of the oopses is lost in the email). For example, on dove (SolidRun Cubox) I see: [0.707248] Unable to handle kernel NULL pointer dereference at virtual address 0054 [0.715297] pgd = c0004000 [0.717984] [0054] *pgd= [0.721548] Internal error: Oops: 5 [#1] ARM [0.725794] Modules linked in: [0.728841] CPU: 0 PID: 1 Comm: swapper Not tainted 3.12.0-rc5-next-20131017 #1 [0.736114] task: ef035c00 ti: ef036000 task.ti: ef036000 [0.741497] PC is at kfree+0x54/0xc4 [0.745063] LR is at ata_host_register+0x3c/0x290 [0.749741] pc : []lr : []psr: 4193 [0.749741] sp : ef037da8 ip : 0034 fp : [0.761159] r10: r9 : ef061810 r8 : c0519fc8 [0.766353] r7 : c0519fc8 r6 : a113 r5 : r4 : ef1c9dd0 [0.772850] r3 : c0fc8fe0 r2 : c07c9000 r1 : 4000 r0 : [0.779349] Flags: nZcv IRQs off FIQs on Mode SVC_32 ISA ARM Segment kernel [0.786708] Control: 10c5387d Table: 4019 DAC: 0015 [0.792428] Process swapper (pid: 1, stack limit = 0xef036248) [0.798234] Stack: (0xef037da8 to 0xef038000) [0.957218] [] (kfree+0x54/0xc4) from [] (ata_host_register+0x3c/0x290) [0.965542] [] (ata_host_register+0x3c/0x290) from [] (ata_host_activate+0xdc/0x118) [0.974992] [] (ata_host_activate+0xdc/0x118) from [] (mv_platform_probe+0x2dc/0x36c) [0.984527] [] (mv_platform_probe+0x2dc/0x36c) from [] (platform_drv_probe+0x18/0x48) [0.994051] [] (platform_drv_probe+0x18/0x48) from [] (really_probe+0x74/0x1fc) [1.003062] [] (really_probe+0x74/0x1fc) from [] (__driver_attach+0x98/0x9c) [1.011804] [] (__driver_attach+0x98/0x9c) from [] (bus_for_each_dev+0x60/0x94) [1.020808] [] (bus_for_each_dev+0x60/0x94) from [] (bus_add_driver+0x148/0x1f0) [1.029898] [] (bus_add_driver+0x148/0x1f0) from [] (driver_register+0x78/0xf8) [1.038911] [] (driver_register+0x78/0xf8) from [] (mv_init+0x30/0x50) [1.047144] [] (mv_init+0x30/0x50) from [] (do_one_initcall+0x100/0x14c) [1.07] [] (do_one_initcall+0x100/0x14c) from [] (kernel_init_freeable+0x120/0x1c0) [1.065259] [] (kernel_init_freeable+0x120/0x1c0) from [] (kernel_init+0x8/0x158) [1.074441] [] (kernel_init+0x8/0x158) from [] (ret_from_fork+0x14/0x3c) [1.082841] Code: e0823283 e3110902 1593301c e593001c (e5904054) My 'sh' qemu run fails with: BUG: unable to handle kernel paging request at 6e81 PC: [<8c1f10ce>] ata_finalize_port_ops+0x4e/0xc0 pgd = 8c401150 [6e81] *pgd= Oops: [#1] Modules linked in: CPU: 0 PID: 1 Comm: swapper Not tainted 3.12.0-rc5-next-20131017-06210-gdaa01b0 #1 task: 8fc27be0 ti: 8fc28000 task.ti: 8fc28000 PC is at ata_finalize_port_ops+0x4e/0xc0 PR is at ata_host_start+0x48/0x1c0 PC : 8c1f10ce SP : 8fc29e0c SR : 40008001 TEA : 6e81 R0 : R1 : 8fc83018 R2 : 6e81 R3 : R4 : 8fc83000 R5 : 00bc R6 : 6e69 R7 : 8fc830f0 R8 : 8fd47cac R9 : 8fd47cac R10 : R11 : 8c207d80 R12 : 8c1f1080 R13 : R14 : 0064 MACH: MACL: 0001 GBR : PR : 8c1f21e8 Call trace: [<8c1f807e>] ata_host_activate+0x1e/0x120 [<8c207d80>] ata_sff_interrupt+0x0/0x240 [<8c209ed6>] pata_platform_probe+0x76/0x120 [<8c209ed6>] pata_platform_probe+0x76/0x120 [<8c1cf440>] platform_get_resource+0x0/0x60 [<8c1cfeda>] platform_drv_probe+0x1a/0x60 [<8c012800>] arch_local_save_flags+0x0/0x20 [<8c1ce1ee>] driver_probe_device+0x6e/0x260 [<8c012820>] arch_local_irq_restore+0x0/0x40 [<8c1cc4c0>] klist_devices_put+0x0/0x20 [<8c1ce466>] __driver_attach+0x86/0xa0 [<8c2fa800>] mutex_lock+0x0/0x60 [<8c1cc8c8>] bus_for_each_dev+0x48/0x80 [<8c1cc620>] next_device+0x0/0x20 [<8c1ce3e0>] __driver_attach+0x0/0xa0 [<8c1cd862>] bus_add_driver+0xc2/0x220 [<8c1ce90c>] driver_register+0x4c/0x120 [<8c3eeccc>] pata_platform_driver_init+0x0/0x14 [<8c011244>] do_one_initcall+0x1c4/0x280 [<8c3eeccc>] pata_platform_driver_init+0x0/0x14 [<8c059160>] register_irq_proc+0x0/0xa0 [<8c10b6f0>] proc_create_data+0x50/0xe0 [<8c03f2b8>] parse_args+0x218/0x3a0 [<8c03f000>] parameq+0x0/0xa0 [<8c012820>] arch_local_irq_restore+0x0/0x40 [<8c3e0a06>] kernel_init_freeable+0xce/0x1c8 [<8c011080>] do_one_initcall+0x0/0x280 [<8c3e0158>] repair_env_string+0
Re: linux-next: Tree for Oct 17
On Fri, Oct 18, 2013 at 12:45:26AM -0700, Olof Johansson wrote: > On Fri, Oct 18, 2013 at 01:38:47AM +0100, Mark Brown wrote: > > Hi all, > > > > I've uploaded today's linux-next tree to the master branch of the > > repository below: > > > > git://gitorious.org/thierryreding/linux-next.git > > > A next-20131017 tag is also provided for convenience. > > > > One new conflict today but otherwise uneventful. x86_64 allmodconfigs > > build after each merge but no other build tests were done. > > Hi, > > I'm seeing a fairly large fallout on boot testing. See > http://lists.linaro.org/pipermail/kernel-build-reports/2013-October/000719.html > for full list (I need to start providing longer backlogs for failures, the top > of the oopses is lost in the email). > > For example, on dove (SolidRun Cubox) I see: > > [0.707248] Unable to handle kernel NULL pointer dereference at virtual > address 0054 > [0.715297] pgd = c0004000 > [0.717984] [0054] *pgd= > [0.721548] Internal error: Oops: 5 [#1] ARM > [0.725794] Modules linked in: > [0.728841] CPU: 0 PID: 1 Comm: swapper Not tainted > 3.12.0-rc5-next-20131017 #1 > [0.736114] task: ef035c00 ti: ef036000 task.ti: ef036000 > [0.741497] PC is at kfree+0x54/0xc4 > [0.745063] LR is at ata_host_register+0x3c/0x290 > [0.749741] pc : []lr : []psr: 4193 > [0.749741] sp : ef037da8 ip : 0034 fp : > [0.761159] r10: r9 : ef061810 r8 : c0519fc8 > [0.766353] r7 : c0519fc8 r6 : a113 r5 : r4 : ef1c9dd0 > [0.772850] r3 : c0fc8fe0 r2 : c07c9000 r1 : 4000 r0 : > [0.779349] Flags: nZcv IRQs off FIQs on Mode SVC_32 ISA ARM Segment > kernel > [0.786708] Control: 10c5387d Table: 4019 DAC: 0015 > [0.792428] Process swapper (pid: 1, stack limit = 0xef036248) > [0.798234] Stack: (0xef037da8 to 0xef038000) > [0.957218] [] (kfree+0x54/0xc4) from [] > (ata_host_register+0x3c/0x290) > [0.965542] [] (ata_host_register+0x3c/0x290) from [] > (ata_host_activate+0xdc/0x118) > [0.974992] [] (ata_host_activate+0xdc/0x118) from [] > (mv_platform_probe+0x2dc/0x36c) > [0.984527] [] (mv_platform_probe+0x2dc/0x36c) from [] > (platform_drv_probe+0x18/0x48) > [0.994051] [] (platform_drv_probe+0x18/0x48) from [] > (really_probe+0x74/0x1fc) > [1.003062] [] (really_probe+0x74/0x1fc) from [] > (__driver_attach+0x98/0x9c) > [1.011804] [] (__driver_attach+0x98/0x9c) from [] > (bus_for_each_dev+0x60/0x94) > [1.020808] [] (bus_for_each_dev+0x60/0x94) from [] > (bus_add_driver+0x148/0x1f0) > [1.029898] [] (bus_add_driver+0x148/0x1f0) from [] > (driver_register+0x78/0xf8) > [1.038911] [] (driver_register+0x78/0xf8) from [] > (mv_init+0x30/0x50) > [1.047144] [] (mv_init+0x30/0x50) from [] > (do_one_initcall+0x100/0x14c) > [1.07] [] (do_one_initcall+0x100/0x14c) from [] > (kernel_init_freeable+0x120/0x1c0) > [1.065259] [] (kernel_init_freeable+0x120/0x1c0) from > [] (kernel_init+0x8/0x158) > [1.074441] [] (kernel_init+0x8/0x158) from [] > (ret_from_fork+0x14/0x3c) > [1.082841] Code: e0823283 e3110902 1593301c e593001c (e5904054) > > > I bisected it down to commit 55acc602faae7c10e53acdca0c70f4936c2539c6, which > is really weird. That is: > > commit 55acc602faae7c10e53acdca0c70f4936c2539c6 > Merge: e32face ba6857b > Author: Mark Brown > AuthorDate: Thu Oct 17 23:55:55 2013 +0100 > Commit: Mark Brown > CommitDate: Thu Oct 17 23:55:55 2013 +0100 > > Merge remote-tracking branch 'driver-core/driver-core-next' > > Conflicts: > include/linux/netdevice.h > > > But there isn't anything controversial in the merge commit. > > I tried checking out either side of that merge, and they both boot > fine. I redid the merge myself, and I get no delta compared to your > merge and I still get the same failure. > > I've got more failures than dove, I'll try bisecting a few of the others > in the morning (it's late here), hopefully they will help indicate what's > actually going wrong. I'm guessing something just happens to move around > enough to expose a different problem once the two branches are merged. Looking at that oops it seems like host is actually NULL when kfree() is called in ata_host_register(). That seems to only happen when freeing up any of the unused ports, which is strange in itself because Cubox seems to only register a single one. Also if host is indeed NULL, then things should go haywire much sooner. Looks like you won't easily find out what's going on here unless you get into it somewhat deeper and perhaps trace what exactly fails and why the NULL pointer is even there in the first place. Thierry pgpEClK8cEolS.pgp Description: PGP signature
Re: linux-next: Tree for Oct 17
On Fri, Oct 18, 2013 at 01:38:47AM +0100, Mark Brown wrote: > Hi all, > > I've uploaded today's linux-next tree to the master branch of the > repository below: > > git://gitorious.org/thierryreding/linux-next.git > > A next-20131017 tag is also provided for convenience. > > One new conflict today but otherwise uneventful. x86_64 allmodconfigs > build after each merge but no other build tests were done. Hi, I'm seeing a fairly large fallout on boot testing. See http://lists.linaro.org/pipermail/kernel-build-reports/2013-October/000719.html for full list (I need to start providing longer backlogs for failures, the top of the oopses is lost in the email). For example, on dove (SolidRun Cubox) I see: [0.707248] Unable to handle kernel NULL pointer dereference at virtual address 0054 [0.715297] pgd = c0004000 [0.717984] [0054] *pgd= [0.721548] Internal error: Oops: 5 [#1] ARM [0.725794] Modules linked in: [0.728841] CPU: 0 PID: 1 Comm: swapper Not tainted 3.12.0-rc5-next-20131017 #1 [0.736114] task: ef035c00 ti: ef036000 task.ti: ef036000 [0.741497] PC is at kfree+0x54/0xc4 [0.745063] LR is at ata_host_register+0x3c/0x290 [0.749741] pc : []lr : []psr: 4193 [0.749741] sp : ef037da8 ip : 0034 fp : [0.761159] r10: r9 : ef061810 r8 : c0519fc8 [0.766353] r7 : c0519fc8 r6 : a113 r5 : r4 : ef1c9dd0 [0.772850] r3 : c0fc8fe0 r2 : c07c9000 r1 : 4000 r0 : [0.779349] Flags: nZcv IRQs off FIQs on Mode SVC_32 ISA ARM Segment kernel [0.786708] Control: 10c5387d Table: 4019 DAC: 0015 [0.792428] Process swapper (pid: 1, stack limit = 0xef036248) [0.798234] Stack: (0xef037da8 to 0xef038000) [0.957218] [] (kfree+0x54/0xc4) from [] (ata_host_register+0x3c/0x290) [0.965542] [] (ata_host_register+0x3c/0x290) from [] (ata_host_activate+0xdc/0x118) [0.974992] [] (ata_host_activate+0xdc/0x118) from [] (mv_platform_probe+0x2dc/0x36c) [0.984527] [] (mv_platform_probe+0x2dc/0x36c) from [] (platform_drv_probe+0x18/0x48) [0.994051] [] (platform_drv_probe+0x18/0x48) from [] (really_probe+0x74/0x1fc) [1.003062] [] (really_probe+0x74/0x1fc) from [] (__driver_attach+0x98/0x9c) [1.011804] [] (__driver_attach+0x98/0x9c) from [] (bus_for_each_dev+0x60/0x94) [1.020808] [] (bus_for_each_dev+0x60/0x94) from [] (bus_add_driver+0x148/0x1f0) [1.029898] [] (bus_add_driver+0x148/0x1f0) from [] (driver_register+0x78/0xf8) [1.038911] [] (driver_register+0x78/0xf8) from [] (mv_init+0x30/0x50) [1.047144] [] (mv_init+0x30/0x50) from [] (do_one_initcall+0x100/0x14c) [1.07] [] (do_one_initcall+0x100/0x14c) from [] (kernel_init_freeable+0x120/0x1c0) [1.065259] [] (kernel_init_freeable+0x120/0x1c0) from [] (kernel_init+0x8/0x158) [1.074441] [] (kernel_init+0x8/0x158) from [] (ret_from_fork+0x14/0x3c) [1.082841] Code: e0823283 e3110902 1593301c e593001c (e5904054) I bisected it down to commit 55acc602faae7c10e53acdca0c70f4936c2539c6, which is really weird. That is: commit 55acc602faae7c10e53acdca0c70f4936c2539c6 Merge: e32face ba6857b Author: Mark Brown AuthorDate: Thu Oct 17 23:55:55 2013 +0100 Commit: Mark Brown CommitDate: Thu Oct 17 23:55:55 2013 +0100 Merge remote-tracking branch 'driver-core/driver-core-next' Conflicts: include/linux/netdevice.h But there isn't anything controversial in the merge commit. I tried checking out either side of that merge, and they both boot fine. I redid the merge myself, and I get no delta compared to your merge and I still get the same failure. I've got more failures than dove, I'll try bisecting a few of the others in the morning (it's late here), hopefully they will help indicate what's actually going wrong. I'm guessing something just happens to move around enough to expose a different problem once the two branches are merged. -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
linux-next: Tree for Oct 17
Hi all, I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131017 tag is also provided for convenience. One new conflict today but otherwise uneventful. x86_64 allmodconfigs build after each merge but no other build tests were done. signature.asc Description: Digital signature
linux-next: Tree for Oct 17
Hi all, Changes since 201201016: Undropped Tree: cortex The l2-mtd tree still had its build failure so I used the version from next-20121011. The security tree gained conflicts against Linus' tree. The cortex tree lost its conflicts. The signal tree still had its build failure for which I applied a suggested patch. 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" as mentioned in the FAQ on the wiki (see below). 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 for x86_64. After the final fixups (if any), it is also built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and allyesconfig (minus CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc, sparc64 and arm defconfig. These builds also have CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and CONFIG_DEBUG_INFO disabled when necessary. Below is a summary of the state of the merge. We are up to 204 trees (counting Linus' and 26 trees of patches pending for Linus' tree), more are welcome (even if they are currently empty). Thanks to those who have contributed, and to those who haven't, please do. 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. There is a wiki covering stuff to do with linux-next at http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel. -- Cheers, Stephen Rothwells...@canb.auug.org.au $ git checkout master $ git reset --hard stable Merging origin/master (dd8e8c4 thermal, cpufreq: Fix build when CPU_FREQ_TABLE isn't configured) Merging fixes/master (12250d8 Merge branch 'i2c-embedded/for-next' of git://git.pengutronix.de/git/wsa/linux) Merging kbuild-current/rc-fixes (b1e0d8b kbuild: Fix gcc -x syntax) Merging arm-current/fixes (3d6ee36 Merge branch 'late-for-linus' of git://git.linaro.org/people/rmk/linux-arm) Merging m68k-current/for-linus (92f79db m68k: Remove empty #ifdef/#else/#endif block) Merging powerpc-merge/merge (fd3bc66 Merge tag 'disintegrate-powerpc-20121009' into merge) Merging sparc/master (e793d8c sparc64: Fix bit twiddling in sparc_pmu_enable_event().) Merging net/master (9f0d3c2 ipv6: addrconf: fix /proc/net/if_inet6) Merging sound-current/for-linus (1f04661 ALSA: hda - Stop LPIB delay counting on broken hardware) Merging pci-current/for-linus (0ff9514 PCI: Don't print anything while decoding is disabled) Merging wireless/master (bf11315 net/wireless: ipw2200: Fix panic occurring in ipw_handle_promiscuous_tx()) Merging driver-core.current/driver-core-linus (ddffeb8 Linux 3.7-rc1) Merging tty.current/tty-linus (3e5bde8 serial/8250_hp300: Missing 8250 register interface conversion bits) Merging usb.current/usb-linus (db5c8b5 USB: fix port probing and removal in garmin_gps) Merging staging.current/staging-linus (ddffeb8 Linux 3.7-rc1) Merging char-misc.current/char-misc-linus (ddffeb8 Linux 3.7-rc1) Merging input-current/for-linus (0cc8d6a Merge branch 'next' into for-linus) Merging md-current/for-linus (72f36d5 md: refine reporting of resync/reshape delays.) Merging audit-current/for-linus (c158a35 audit: no leading space in audit_log_d_path prefix) Merging crypto-current/master (c9f97a2 crypto: x86/glue_helper - fix storing of new IV in CBC encryption) Merging ide/master (9974e43 ide: fix generic_ide_suspend/resume Oops) Merging dwmw2/master (244dc4e Merge git://git.infradead.org/users/dwmw2/random-2.6) Merging sh-current/sh-fixes-for-linus (4403310 SH: Convert out[bwl] macros to inline functions) Merging irqdomain-current/irqdomain/merge (15e06bf irqdomain: Fix debugfs formatting) Merging devicetree-current/devicetree/merge (4e8383b of: release node fix for of_parse_phandle_with_args) Merging spi-current/spi/merge (d1c185b of/spi: Fix SPI module loading by using proper "spi:" modalias prefixes.) Merging gpio-current/gpio/merge (96b7064 gpio/tca6424: merge I2C transactions, remove cast) Merging asm-generic/master (c37d615 Merge branch 'disintegrate-asm-generic' of git://git.infradead.org/users/dhowells/linux-headers into asm-generic) Merging arm/for-next (3d6ee36 Merge branch 'late-for-linus' of git://git.linaro.org/people/rmk/linux-arm) Merging arm-perf/for-next/perf (5d6
