Re: linux-next: Tree for Nov 5
On Tue, 10 Nov 2020 at 14:54, Marco Elver wrote: > > On Tue, 10 Nov 2020 at 10:36, Dmitry Vyukov wrote: > [...] > > > > On Tue, Nov 10, 2020 at 8:50 AM Anders Roxell > > > > wrote: > [...] > > > > > When building an arm64 allmodconfig and booting up that in qemu I see > > > > > > > > > > [10011.092394][ T28] task:kworker/0:2 state:D stack:26896 pid: > > > > > 1840 ppid: 2 flags:0x0428 > > > > > [10022.368093][ T28] Workqueue: events toggle_allocation_gate > > > > > [10024.827549][ T28] Call trace: > > > > > [10027.152494][ T28] __switch_to+0x1cc/0x1e0 > > > > > [10031.378073][ T28] __schedule+0x730/0x800 > > > > > [10032.164468][ T28] schedule+0xd8/0x160 > > > > > [10033.886807][ T28] toggle_allocation_gate+0x16c/0x220 > > > > > [10038.477987][ T28] process_one_work+0x5c0/0x980 > > > > > [10039.900075][ T28] worker_thread+0x428/0x720 > > > > > [10042.782911][ T28] kthread+0x23c/0x260 > > > > > [10043.171725][ T28] ret_from_fork+0x10/0x18 > > > > > [10046.227741][ T28] INFO: lockdep is turned off. > > > > > [10047.732220][ T28] Kernel panic - not syncing: hung_task: blocked > > > > > tasks > > > > > [10047.741785][ T28] CPU: 0 PID: 28 Comm: khungtaskd Tainted: G > > > > > W 5.10.0-rc2-next-20201105-6-g7af110e4d8ed #1 > > > > > [10047.755348][ T28] Hardware name: linux,dummy-virt (DT) > > > > > [10047.763476][ T28] Call trace: > > > > > [10047.769802][ T28] dump_backtrace+0x0/0x420 > > > > > [10047.777104][ T28] show_stack+0x38/0xa0 > > > > > [10047.784177][ T28] dump_stack+0x1d4/0x278 > > > > > [10047.791362][ T28] panic+0x304/0x5d8 > > > > > [10047.798202][ T28] check_hung_uninterruptible_tasks+0x5e4/0x640 > > > > > [10047.807056][ T28] watchdog+0x138/0x160 > > > > > [10047.814140][ T28] kthread+0x23c/0x260 > > > > > [10047.821130][ T28] ret_from_fork+0x10/0x18 > > > > > [10047.829181][ T28] Kernel Offset: disabled > > > > > [10047.836274][ T28] CPU features: 0x0240002,20002004 > > > > > [10047.844070][ T28] Memory Limit: none > > > > > [10047.853599][ T28] ---[ end Kernel panic - not syncing: hung_task: > > > > > blocked tasks ]--- > > > > > > > > > > if I build with KFENCE=n it boots up eventually, here's my .config > > > > > file [2]. > > > > > > > > > > Any idea what may happen? > > > > > > > > > > it happens on next-20201109 also, but it takes longer until we get the > > > > > "Call trace:". > > > > > > > > > > Cheers, > > > > > Anders > > > > > [1] http://ix.io/2Ddv > > > > > [2] > > > > > https://people.linaro.org/~anders.roxell/allmodconfig-next-20201105.config > [...] > > > oh I missed to say that this is the full boot log with the kernel > > > panic http://ix.io/2Ddv > > > > Thanks! > > The last messages before the hang are: > > > > [ 1367.791522][T1] Running tests on all trace events: > > [ 1367.815307][T1] Testing all events: > > > > I can imagine tracing somehow interferes with kfence. > > The reason is simply that that config on qemu is so slow (enabling > lockdep helped), and the test that is running doesn't result in > allocations for an extended time. Because of that our wait_event() > just stalls, as there are no allocations coming in. My guess is that > this scenario is unique to early boot, where we are not yet running > user space, paired with running a selftest that results in no > allocations for some time. > > Try and give that a spin: > https://lkml.kernel.org/r/20201110135320.3309507-1-el...@google.com Thank you Marco. I'll give it a spin and reply to that thread if it works or not. Cheers, Anders
Re: linux-next: Tree for Nov 5
On Tue, 10 Nov 2020 at 10:36, Dmitry Vyukov wrote: [...] > > > On Tue, Nov 10, 2020 at 8:50 AM Anders Roxell > > > wrote: [...] > > > > When building an arm64 allmodconfig and booting up that in qemu I see > > > > > > > > [10011.092394][ T28] task:kworker/0:2 state:D stack:26896 pid: > > > > 1840 ppid: 2 flags:0x0428 > > > > [10022.368093][ T28] Workqueue: events toggle_allocation_gate > > > > [10024.827549][ T28] Call trace: > > > > [10027.152494][ T28] __switch_to+0x1cc/0x1e0 > > > > [10031.378073][ T28] __schedule+0x730/0x800 > > > > [10032.164468][ T28] schedule+0xd8/0x160 > > > > [10033.886807][ T28] toggle_allocation_gate+0x16c/0x220 > > > > [10038.477987][ T28] process_one_work+0x5c0/0x980 > > > > [10039.900075][ T28] worker_thread+0x428/0x720 > > > > [10042.782911][ T28] kthread+0x23c/0x260 > > > > [10043.171725][ T28] ret_from_fork+0x10/0x18 > > > > [10046.227741][ T28] INFO: lockdep is turned off. > > > > [10047.732220][ T28] Kernel panic - not syncing: hung_task: blocked > > > > tasks > > > > [10047.741785][ T28] CPU: 0 PID: 28 Comm: khungtaskd Tainted: G > > > > W 5.10.0-rc2-next-20201105-6-g7af110e4d8ed #1 > > > > [10047.755348][ T28] Hardware name: linux,dummy-virt (DT) > > > > [10047.763476][ T28] Call trace: > > > > [10047.769802][ T28] dump_backtrace+0x0/0x420 > > > > [10047.777104][ T28] show_stack+0x38/0xa0 > > > > [10047.784177][ T28] dump_stack+0x1d4/0x278 > > > > [10047.791362][ T28] panic+0x304/0x5d8 > > > > [10047.798202][ T28] check_hung_uninterruptible_tasks+0x5e4/0x640 > > > > [10047.807056][ T28] watchdog+0x138/0x160 > > > > [10047.814140][ T28] kthread+0x23c/0x260 > > > > [10047.821130][ T28] ret_from_fork+0x10/0x18 > > > > [10047.829181][ T28] Kernel Offset: disabled > > > > [10047.836274][ T28] CPU features: 0x0240002,20002004 > > > > [10047.844070][ T28] Memory Limit: none > > > > [10047.853599][ T28] ---[ end Kernel panic - not syncing: hung_task: > > > > blocked tasks ]--- > > > > > > > > if I build with KFENCE=n it boots up eventually, here's my .config file > > > > [2]. > > > > > > > > Any idea what may happen? > > > > > > > > it happens on next-20201109 also, but it takes longer until we get the > > > > "Call trace:". > > > > > > > > Cheers, > > > > Anders > > > > [1] http://ix.io/2Ddv > > > > [2] > > > > https://people.linaro.org/~anders.roxell/allmodconfig-next-20201105.config [...] > > oh I missed to say that this is the full boot log with the kernel > > panic http://ix.io/2Ddv > > Thanks! > The last messages before the hang are: > > [ 1367.791522][T1] Running tests on all trace events: > [ 1367.815307][T1] Testing all events: > > I can imagine tracing somehow interferes with kfence. The reason is simply that that config on qemu is so slow (enabling lockdep helped), and the test that is running doesn't result in allocations for an extended time. Because of that our wait_event() just stalls, as there are no allocations coming in. My guess is that this scenario is unique to early boot, where we are not yet running user space, paired with running a selftest that results in no allocations for some time. Try and give that a spin: https://lkml.kernel.org/r/20201110135320.3309507-1-el...@google.com Thanks, -- Marco
Re: linux-next: Tree for Nov 5
On Tue, Nov 10, 2020 at 10:25 AM Anders Roxell wrote: > > On Tue, 10 Nov 2020 at 10:17, Dmitry Vyukov wrote: > > > > On Tue, Nov 10, 2020 at 8:50 AM Anders Roxell > > wrote: > > > > > > On Thu, 5 Nov 2020 at 07:06, Stephen Rothwell > > > wrote: > > > > > > > > Hi all, > > > > > > > > Changes since 20201104: > > > > > > When building an arm64 allmodconfig and booting up that in qemu I see > > > > > > [10011.092394][ T28] task:kworker/0:2 state:D stack:26896 pid: > > > 1840 ppid: 2 flags:0x0428 > > > [10022.368093][ T28] Workqueue: events toggle_allocation_gate > > > [10024.827549][ T28] Call trace: > > > [10027.152494][ T28] __switch_to+0x1cc/0x1e0 > > > [10031.378073][ T28] __schedule+0x730/0x800 > > > [10032.164468][ T28] schedule+0xd8/0x160 > > > [10033.886807][ T28] toggle_allocation_gate+0x16c/0x220 > > > [10038.477987][ T28] process_one_work+0x5c0/0x980 > > > [10039.900075][ T28] worker_thread+0x428/0x720 > > > [10042.782911][ T28] kthread+0x23c/0x260 > > > [10043.171725][ T28] ret_from_fork+0x10/0x18 > > > [10046.227741][ T28] INFO: lockdep is turned off. > > > [10047.732220][ T28] Kernel panic - not syncing: hung_task: blocked > > > tasks > > > [10047.741785][ T28] CPU: 0 PID: 28 Comm: khungtaskd Tainted: G > > > W 5.10.0-rc2-next-20201105-6-g7af110e4d8ed #1 > > > [10047.755348][ T28] Hardware name: linux,dummy-virt (DT) > > > [10047.763476][ T28] Call trace: > > > [10047.769802][ T28] dump_backtrace+0x0/0x420 > > > [10047.777104][ T28] show_stack+0x38/0xa0 > > > [10047.784177][ T28] dump_stack+0x1d4/0x278 > > > [10047.791362][ T28] panic+0x304/0x5d8 > > > [10047.798202][ T28] check_hung_uninterruptible_tasks+0x5e4/0x640 > > > [10047.807056][ T28] watchdog+0x138/0x160 > > > [10047.814140][ T28] kthread+0x23c/0x260 > > > [10047.821130][ T28] ret_from_fork+0x10/0x18 > > > [10047.829181][ T28] Kernel Offset: disabled > > > [10047.836274][ T28] CPU features: 0x0240002,20002004 > > > [10047.844070][ T28] Memory Limit: none > > > [10047.853599][ T28] ---[ end Kernel panic - not syncing: hung_task: > > > blocked tasks ]--- > > > > > > if I build with KFENCE=n it boots up eventually, here's my .config file > > > [2]. > > > > > > Any idea what may happen? > > > > > > it happens on next-20201109 also, but it takes longer until we get the > > > "Call trace:". > > > > > > Cheers, > > > Anders > > > [1] http://ix.io/2Ddv > > > [2] > > > https://people.linaro.org/~anders.roxell/allmodconfig-next-20201105.config > > > > Hi Anders, > > Hi Dmitry, > > > > > Does it happen during boot or afterwards? > > During boot, since it runs a lot of boot selftests. > > > 10047 are seconds after boot, right? > > No > > > So this is like 3 hours after boot, no? > > This is a boot log where I actually get to the boot prompt. > https://people.linaro.org/~anders.roxell/output-next-20201109-nokfence.log > > > Also, is there anything useful before that part of the log? > > oh I missed to say that this is the full boot log with the kernel > panic http://ix.io/2Ddv Thanks! The last messages before the hang are: [ 1367.791522][T1] Running tests on all trace events: [ 1367.815307][T1] Testing all events: I can imagine tracing somehow interferes with kfence. Alex, Marco, please take a look. Maybe you will be able to reproduce it by enabling these boot tests.
Re: linux-next: Tree for Nov 5
On Tue, 10 Nov 2020 at 10:17, Dmitry Vyukov wrote: > > On Tue, Nov 10, 2020 at 8:50 AM Anders Roxell > wrote: > > > > On Thu, 5 Nov 2020 at 07:06, Stephen Rothwell wrote: > > > > > > Hi all, > > > > > > Changes since 20201104: > > > > When building an arm64 allmodconfig and booting up that in qemu I see > > > > [10011.092394][ T28] task:kworker/0:2 state:D stack:26896 pid: > > 1840 ppid: 2 flags:0x0428 > > [10022.368093][ T28] Workqueue: events toggle_allocation_gate > > [10024.827549][ T28] Call trace: > > [10027.152494][ T28] __switch_to+0x1cc/0x1e0 > > [10031.378073][ T28] __schedule+0x730/0x800 > > [10032.164468][ T28] schedule+0xd8/0x160 > > [10033.886807][ T28] toggle_allocation_gate+0x16c/0x220 > > [10038.477987][ T28] process_one_work+0x5c0/0x980 > > [10039.900075][ T28] worker_thread+0x428/0x720 > > [10042.782911][ T28] kthread+0x23c/0x260 > > [10043.171725][ T28] ret_from_fork+0x10/0x18 > > [10046.227741][ T28] INFO: lockdep is turned off. > > [10047.732220][ T28] Kernel panic - not syncing: hung_task: blocked tasks > > [10047.741785][ T28] CPU: 0 PID: 28 Comm: khungtaskd Tainted: G > > W 5.10.0-rc2-next-20201105-6-g7af110e4d8ed #1 > > [10047.755348][ T28] Hardware name: linux,dummy-virt (DT) > > [10047.763476][ T28] Call trace: > > [10047.769802][ T28] dump_backtrace+0x0/0x420 > > [10047.777104][ T28] show_stack+0x38/0xa0 > > [10047.784177][ T28] dump_stack+0x1d4/0x278 > > [10047.791362][ T28] panic+0x304/0x5d8 > > [10047.798202][ T28] check_hung_uninterruptible_tasks+0x5e4/0x640 > > [10047.807056][ T28] watchdog+0x138/0x160 > > [10047.814140][ T28] kthread+0x23c/0x260 > > [10047.821130][ T28] ret_from_fork+0x10/0x18 > > [10047.829181][ T28] Kernel Offset: disabled > > [10047.836274][ T28] CPU features: 0x0240002,20002004 > > [10047.844070][ T28] Memory Limit: none > > [10047.853599][ T28] ---[ end Kernel panic - not syncing: hung_task: > > blocked tasks ]--- > > > > if I build with KFENCE=n it boots up eventually, here's my .config file [2]. > > > > Any idea what may happen? > > > > it happens on next-20201109 also, but it takes longer until we get the > > "Call trace:". > > > > Cheers, > > Anders > > [1] http://ix.io/2Ddv > > [2] > > https://people.linaro.org/~anders.roxell/allmodconfig-next-20201105.config > > Hi Anders, Hi Dmitry, > > Does it happen during boot or afterwards? During boot, since it runs a lot of boot selftests. > 10047 are seconds after boot, right? No > So this is like 3 hours after boot, no? This is a boot log where I actually get to the boot prompt. https://people.linaro.org/~anders.roxell/output-next-20201109-nokfence.log > Also, is there anything useful before that part of the log? oh I missed to say that this is the full boot log with the kernel panic http://ix.io/2Ddv Cheers, Anders
Re: linux-next: Tree for Nov 5
On Tue, Nov 10, 2020 at 8:50 AM Anders Roxell wrote: > > On Thu, 5 Nov 2020 at 07:06, Stephen Rothwell wrote: > > > > Hi all, > > > > Changes since 20201104: > > When building an arm64 allmodconfig and booting up that in qemu I see > > [10011.092394][ T28] task:kworker/0:2 state:D stack:26896 pid: > 1840 ppid: 2 flags:0x0428 > [10022.368093][ T28] Workqueue: events toggle_allocation_gate > [10024.827549][ T28] Call trace: > [10027.152494][ T28] __switch_to+0x1cc/0x1e0 > [10031.378073][ T28] __schedule+0x730/0x800 > [10032.164468][ T28] schedule+0xd8/0x160 > [10033.886807][ T28] toggle_allocation_gate+0x16c/0x220 > [10038.477987][ T28] process_one_work+0x5c0/0x980 > [10039.900075][ T28] worker_thread+0x428/0x720 > [10042.782911][ T28] kthread+0x23c/0x260 > [10043.171725][ T28] ret_from_fork+0x10/0x18 > [10046.227741][ T28] INFO: lockdep is turned off. > [10047.732220][ T28] Kernel panic - not syncing: hung_task: blocked tasks > [10047.741785][ T28] CPU: 0 PID: 28 Comm: khungtaskd Tainted: G > W 5.10.0-rc2-next-20201105-6-g7af110e4d8ed #1 > [10047.755348][ T28] Hardware name: linux,dummy-virt (DT) > [10047.763476][ T28] Call trace: > [10047.769802][ T28] dump_backtrace+0x0/0x420 > [10047.777104][ T28] show_stack+0x38/0xa0 > [10047.784177][ T28] dump_stack+0x1d4/0x278 > [10047.791362][ T28] panic+0x304/0x5d8 > [10047.798202][ T28] check_hung_uninterruptible_tasks+0x5e4/0x640 > [10047.807056][ T28] watchdog+0x138/0x160 > [10047.814140][ T28] kthread+0x23c/0x260 > [10047.821130][ T28] ret_from_fork+0x10/0x18 > [10047.829181][ T28] Kernel Offset: disabled > [10047.836274][ T28] CPU features: 0x0240002,20002004 > [10047.844070][ T28] Memory Limit: none > [10047.853599][ T28] ---[ end Kernel panic - not syncing: hung_task: > blocked tasks ]--- > > if I build with KFENCE=n it boots up eventually, here's my .config file [2]. > > Any idea what may happen? > > it happens on next-20201109 also, but it takes longer until we get the > "Call trace:". > > Cheers, > Anders > [1] http://ix.io/2Ddv > [2] https://people.linaro.org/~anders.roxell/allmodconfig-next-20201105.config Hi Anders, Does it happen during boot or afterwards? 10047 are seconds after boot, right? So this is like 3 hours after boot, no? Also, is there anything useful before that part of the log? It seems that at least the bug type header is stripped.
Re: linux-next: Tree for Nov 5
On Thu, 5 Nov 2020 at 07:06, Stephen Rothwell wrote: > > Hi all, > > Changes since 20201104: When building an arm64 allmodconfig and booting up that in qemu I see [10011.092394][ T28] task:kworker/0:2 state:D stack:26896 pid: 1840 ppid: 2 flags:0x0428 [10022.368093][ T28] Workqueue: events toggle_allocation_gate [10024.827549][ T28] Call trace: [10027.152494][ T28] __switch_to+0x1cc/0x1e0 [10031.378073][ T28] __schedule+0x730/0x800 [10032.164468][ T28] schedule+0xd8/0x160 [10033.886807][ T28] toggle_allocation_gate+0x16c/0x220 [10038.477987][ T28] process_one_work+0x5c0/0x980 [10039.900075][ T28] worker_thread+0x428/0x720 [10042.782911][ T28] kthread+0x23c/0x260 [10043.171725][ T28] ret_from_fork+0x10/0x18 [10046.227741][ T28] INFO: lockdep is turned off. [10047.732220][ T28] Kernel panic - not syncing: hung_task: blocked tasks [10047.741785][ T28] CPU: 0 PID: 28 Comm: khungtaskd Tainted: G W 5.10.0-rc2-next-20201105-6-g7af110e4d8ed #1 [10047.755348][ T28] Hardware name: linux,dummy-virt (DT) [10047.763476][ T28] Call trace: [10047.769802][ T28] dump_backtrace+0x0/0x420 [10047.777104][ T28] show_stack+0x38/0xa0 [10047.784177][ T28] dump_stack+0x1d4/0x278 [10047.791362][ T28] panic+0x304/0x5d8 [10047.798202][ T28] check_hung_uninterruptible_tasks+0x5e4/0x640 [10047.807056][ T28] watchdog+0x138/0x160 [10047.814140][ T28] kthread+0x23c/0x260 [10047.821130][ T28] ret_from_fork+0x10/0x18 [10047.829181][ T28] Kernel Offset: disabled [10047.836274][ T28] CPU features: 0x0240002,20002004 [10047.844070][ T28] Memory Limit: none [10047.853599][ T28] ---[ end Kernel panic - not syncing: hung_task: blocked tasks ]--- if I build with KFENCE=n it boots up eventually, here's my .config file [2]. Any idea what may happen? it happens on next-20201109 also, but it takes longer until we get the "Call trace:". Cheers, Anders [1] http://ix.io/2Ddv [2] https://people.linaro.org/~anders.roxell/allmodconfig-next-20201105.config
Re: linux-next: Tree for Nov 5 [drivers/net/ethernet/stmicro/stmmac/dwmac-thead.ko]
On 11/4/20 10:06 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20201104: > > The drm-intel-fixes tree lost its build failure. > > The drm-msm tree gained conflicts against the drm and drm-misc trees. > > The mfd tree gained a build failure so I used the version from > next-20201104. > > The pinctrl tree lost its build failure. > > The akpm-current tree gained a build failure for which I reverted > a commit. > > Non-merge commits (relative to Linus' tree): 3085 > 3498 files changed, 376683 insertions(+), 40297 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 htmldocs. 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 327 trees (counting Linus' and 85 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. > on x86_64: CONFIG_STMMAC_ETH=m # CONFIG_STMMAC_PLATFORM is not set CONFIG_DWMAC_INTEL=m CONFIG_STMMAC_PCI=m dwmac-thead.c is always built but it seems to expect (require) that stmmac_platform.c is also always built, but the latter has a Kconfig option that can be (is) disabled, resulting in build errors: ERROR: modpost: "stmmac_pltfr_pm_ops" [drivers/net/ethernet/stmicro/stmmac/dwmac-thead.ko] undefined! ERROR: modpost: "stmmac_pltfr_remove" [drivers/net/ethernet/stmicro/stmmac/dwmac-thead.ko] undefined! ERROR: modpost: "stmmac_remove_config_dt" [drivers/net/ethernet/stmicro/stmmac/dwmac-thead.ko] undefined! ERROR: modpost: "stmmac_probe_config_dt" [drivers/net/ethernet/stmicro/stmmac/dwmac-thead.ko] undefined! ERROR: modpost: "stmmac_get_platform_resources" [drivers/net/ethernet/stmicro/stmmac/dwmac-thead.ko] undefined! -- ~Randy Reported-by: Randy Dunlap
Re: linux-next: Tree for Nov 5 [drivers/auxdisplay/hd44780_common.ko]
On 11/4/20 10:06 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20201104: > on i386: ERROR: modpost: "charlcd_backlight" [drivers/auxdisplay/hd44780_common.ko] undefined! Full randconfig file is attached. -- ~Randy Reported-by: Randy Dunlap # # Automatically generated file; DO NOT EDIT. # Linux/i386 5.10.0-rc2 Kernel Configuration # CONFIG_CC_VERSION_TEXT="gcc (SUSE Linux) 7.5.0" CONFIG_CC_IS_GCC=y CONFIG_GCC_VERSION=70500 CONFIG_LD_VERSION=23200 CONFIG_CLANG_VERSION=0 CONFIG_CC_HAS_ASM_GOTO=y CONFIG_CC_HAS_ASM_INLINE=y CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_TABLE_SORT=y CONFIG_THREAD_INFO_IN_TASK=y # # General setup # CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_COMPILE_TEST=y CONFIG_LOCALVERSION="" CONFIG_BUILD_SALT="" CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_HAVE_KERNEL_LZ4=y CONFIG_HAVE_KERNEL_ZSTD=y # CONFIG_KERNEL_GZIP is not set # CONFIG_KERNEL_BZIP2 is not set CONFIG_KERNEL_LZMA=y # CONFIG_KERNEL_XZ is not set # CONFIG_KERNEL_LZO is not set # CONFIG_KERNEL_LZ4 is not set # CONFIG_KERNEL_ZSTD is not set CONFIG_DEFAULT_INIT="" CONFIG_DEFAULT_HOSTNAME="(none)" CONFIG_SYSVIPC=y CONFIG_WATCH_QUEUE=y # CONFIG_CROSS_MEMORY_ATTACH is not set # CONFIG_USELIB is not set CONFIG_HAVE_ARCH_AUDITSYSCALL=y # # IRQ subsystem # CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_IRQ_SHOW=y CONFIG_HARDIRQS_SW_RESEND=y CONFIG_GENERIC_IRQ_CHIP=y CONFIG_IRQ_DOMAIN=y CONFIG_IRQ_SIM=y CONFIG_IRQ_DOMAIN_HIERARCHY=y CONFIG_IRQ_FASTEOI_HIERARCHY_HANDLERS=y CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=y CONFIG_GENERIC_IRQ_RESERVATION_MODE=y CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y # CONFIG_GENERIC_IRQ_DEBUGFS is not set # end of IRQ subsystem CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_ARCH_CLOCKSOURCE_INIT=y CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_HAVE_POSIX_CPU_TIMERS_TASK_WORK=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ_COMMON=y # CONFIG_HZ_PERIODIC is not set CONFIG_NO_HZ_IDLE=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y # end of Timers subsystem # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_PREEMPTION=y # # CPU/Task time and stats accounting # CONFIG_TICK_CPU_ACCOUNTING=y # CONFIG_IRQ_TIME_ACCOUNTING is not set CONFIG_PSI=y # CONFIG_PSI_DEFAULT_DISABLED is not set # end of CPU/Task time and stats accounting CONFIG_CPU_ISOLATION=y # # RCU Subsystem # CONFIG_TREE_RCU=y CONFIG_PREEMPT_RCU=y # CONFIG_RCU_EXPERT is not set CONFIG_SRCU=y CONFIG_TREE_SRCU=y CONFIG_TASKS_RCU_GENERIC=y CONFIG_TASKS_RCU=y CONFIG_TASKS_RUDE_RCU=y CONFIG_TASKS_TRACE_RCU=y CONFIG_RCU_STALL_COMMON=y CONFIG_RCU_NEED_SEGCBLIST=y # end of RCU Subsystem CONFIG_IKCONFIG=y CONFIG_IKHEADERS=m CONFIG_LOG_BUF_SHIFT=17 CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y # # Scheduler features # # end of Scheduler features CONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=y CONFIG_CGROUPS=y # CONFIG_MEMCG is not set # CONFIG_CGROUP_SCHED is not set CONFIG_CGROUP_PIDS=y # CONFIG_CGROUP_RDMA is not set # CONFIG_CGROUP_FREEZER is not set # CONFIG_CGROUP_HUGETLB is not set CONFIG_CGROUP_DEVICE=y # CONFIG_CGROUP_CPUACCT is not set # CONFIG_CGROUP_PERF is not set CONFIG_CGROUP_DEBUG=y CONFIG_CHECKPOINT_RESTORE=y # CONFIG_SCHED_AUTOGROUP is not set # CONFIG_SYSFS_DEPRECATED is not set # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set # CONFIG_BOOT_CONFIG is not set CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_HAVE_UID16=y CONFIG_SYSCTL_EXCEPTION_TRACE=y CONFIG_HAVE_PCSPKR_PLATFORM=y CONFIG_EXPERT=y # CONFIG_MULTIUSER is not set # CONFIG_SGETMASK_SYSCALL is not set CONFIG_SYSFS_SYSCALL=y CONFIG_FHANDLE=y # CONFIG_POSIX_TIMERS is not set CONFIG_PRINTK=y CONFIG_PRINTK_NMI=y # CONFIG_BUG is not set CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_FUTEX_PI=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y # CONFIG_TIMERFD is not set # CONFIG_EVENTFD is not set CONFIG_SHMEM=y # CONFIG_AIO is not set # CONFIG_IO_URING is not set CONFIG_ADVISE_SYSCALLS=y CONFIG_MEMBARRIER=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_BASE_RELATIVE=y # CONFIG_BPF_SYSCALL is not set # CONFIG_USERFAULTFD is not set CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y CONFIG_RSEQ=y CONFIG_DEBUG_RSEQ=y # CONFIG_EMBEDDED is not set CONFIG_HAVE_PERF_EVENTS=y CONFIG_PERF_USE_VMALLOC=y CONFIG_PC104=y # # Kernel Performance Events And Counters # CONFIG_PERF_EVENTS=y CONFIG_DEBUG_PERF_USE_VMALLOC=y # end of Kernel Performance Events And Counters # CONFIG_VM_EVENT_COUNTERS is not set CONFIG_COMPAT_BRK=y # CONFIG_SLAB is not set # CONFIG_SLUB is not set CONFIG_SLOB=y CONFIG_SLAB_MERGE_DEFAULT=y CONFIG_SHUFFLE_PAGE_ALLOCATOR=y CONFIG_SYSTEM_DATA_VERIFICATION=y # CONFIG_PROFILING is not set
Re: linux-next: Tree for Nov 5 (net/ipv6/af_inet6)
On 11/4/18 9:51 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20181102: > > Non-merge commits (relative to Linus' tree): 418 on i386 or x86_64: ld: net/ipv6/af_inet6.o: in function `inet6_init': af_inet6.c:(.init.text+0x285): undefined reference to `ipv6_anycast_init' ld: af_inet6.c:(.init.text+0x376): undefined reference to `ipv6_anycast_cleanup' Full randconfig file is attached (for i386). -- ~Randy # # Automatically generated file; DO NOT EDIT. # Linux/i386 4.20.0-rc1 Kernel Configuration # # # Compiler: gcc (SUSE Linux) 4.8.5 # CONFIG_CC_IS_GCC=y CONFIG_GCC_VERSION=40805 CONFIG_CLANG_VERSION=0 CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_EXTABLE_SORT=y CONFIG_THREAD_INFO_IN_TASK=y # # General setup # CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_COMPILE_TEST=y CONFIG_LOCALVERSION="" CONFIG_BUILD_SALT="" CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_HAVE_KERNEL_LZ4=y # CONFIG_KERNEL_GZIP is not set CONFIG_KERNEL_BZIP2=y # CONFIG_KERNEL_LZMA is not set # CONFIG_KERNEL_XZ is not set # CONFIG_KERNEL_LZO is not set # CONFIG_KERNEL_LZ4 is not set CONFIG_DEFAULT_HOSTNAME="(none)" # CONFIG_SWAP is not set CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y # CONFIG_CROSS_MEMORY_ATTACH is not set # CONFIG_USELIB is not set # CONFIG_AUDIT is not set CONFIG_HAVE_ARCH_AUDITSYSCALL=y # # IRQ subsystem # CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_IRQ_CHIP=y CONFIG_IRQ_DOMAIN=y CONFIG_IRQ_SIM=y CONFIG_IRQ_DOMAIN_HIERARCHY=y CONFIG_GENERIC_MSI_IRQ=y CONFIG_GENERIC_MSI_IRQ_DOMAIN=y CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=y CONFIG_GENERIC_IRQ_RESERVATION_MODE=y CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y CONFIG_GENERIC_IRQ_DEBUGFS=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_ARCH_CLOCKSOURCE_DATA=y CONFIG_ARCH_CLOCKSOURCE_INIT=y CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y CONFIG_GENERIC_CMOS_UPDATE=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ_COMMON=y # CONFIG_HZ_PERIODIC is not set CONFIG_NO_HZ_IDLE=y CONFIG_NO_HZ=y # CONFIG_HIGH_RES_TIMERS is not set # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_PREEMPT_COUNT=y # # CPU/Task time and stats accounting # CONFIG_TICK_CPU_ACCOUNTING=y CONFIG_IRQ_TIME_ACCOUNTING=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y # CONFIG_TASK_IO_ACCOUNTING is not set # CONFIG_PSI is not set CONFIG_CPU_ISOLATION=y # # RCU Subsystem # CONFIG_TINY_RCU=y # CONFIG_RCU_EXPERT is not set CONFIG_SRCU=y CONFIG_TINY_SRCU=y CONFIG_TASKS_RCU=y # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=17 CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=y CONFIG_CGROUPS=y CONFIG_PAGE_COUNTER=y CONFIG_MEMCG=y CONFIG_BLK_CGROUP=y # CONFIG_DEBUG_BLK_CGROUP is not set CONFIG_CGROUP_WRITEBACK=y CONFIG_CGROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y CONFIG_CFS_BANDWIDTH=y # CONFIG_RT_GROUP_SCHED is not set # CONFIG_CGROUP_PIDS is not set CONFIG_CGROUP_RDMA=y CONFIG_CGROUP_FREEZER=y CONFIG_CGROUP_DEVICE=y # CONFIG_CGROUP_CPUACCT is not set CONFIG_CGROUP_PERF=y CONFIG_CGROUP_BPF=y # CONFIG_CGROUP_DEBUG is not set CONFIG_SOCK_CGROUP_DATA=y # CONFIG_NAMESPACES is not set CONFIG_CHECKPOINT_RESTORE=y # CONFIG_SCHED_AUTOGROUP is not set CONFIG_SYSFS_DEPRECATED=y CONFIG_SYSFS_DEPRECATED_V2=y # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set # CONFIG_CC_OPTIMIZE_FOR_DEBUGGING is not set CONFIG_HAVE_UID16=y CONFIG_SYSCTL_EXCEPTION_TRACE=y CONFIG_HAVE_PCSPKR_PLATFORM=y CONFIG_BPF=y CONFIG_EXPERT=y # CONFIG_UID16 is not set CONFIG_MULTIUSER=y CONFIG_SGETMASK_SYSCALL=y # CONFIG_SYSFS_SYSCALL is not set CONFIG_FHANDLE=y # CONFIG_POSIX_TIMERS is not set CONFIG_PRINTK=y CONFIG_PRINTK_NMI=y # CONFIG_BUG is not set CONFIG_PCSPKR_PLATFORM=y # CONFIG_BASE_FULL is not set CONFIG_FUTEX=y CONFIG_FUTEX_PI=y # CONFIG_EPOLL is not set # CONFIG_SIGNALFD is not set # CONFIG_TIMERFD is not set CONFIG_EVENTFD=y # CONFIG_SHMEM is not set # CONFIG_AIO is not set # CONFIG_ADVISE_SYSCALLS is not set CONFIG_MEMBARRIER=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_BASE_RELATIVE=y CONFIG_BPF_SYSCALL=y CONFIG_USERFAULTFD=y CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y CONFIG_RSEQ=y # CONFIG_DEBUG_RSEQ is not set # CONFIG_EMBEDDED is not set CONFIG_HAVE_PERF_EVENTS=y CONFIG_PERF_USE_VMALLOC=y CONFIG_PC104=y # # Kernel Performance Events And Counters # CONFIG_PERF_EVENTS=y CONFIG_DEBUG_PERF_USE_VMALLOC=y CONFIG_VM_EVENT_COUNTERS=y # CONFIG_COMPAT_BRK is not set # CONFIG_SLAB is not set # CONFIG_SLUB is not set CONFIG_SLOB=y CONFIG_SLAB_MERGE_DEFAULT=y CONFIG_SYSTEM_DATA_VERIFICATION=y CONFIG_PROFILING=y CONFIG_TRACEPOINTS=y
Re: linux-next: Tree for Nov 5 (net/ipv6/af_inet6)
On 11/4/18 9:51 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20181102: > > Non-merge commits (relative to Linus' tree): 418 on i386 or x86_64: ld: net/ipv6/af_inet6.o: in function `inet6_init': af_inet6.c:(.init.text+0x285): undefined reference to `ipv6_anycast_init' ld: af_inet6.c:(.init.text+0x376): undefined reference to `ipv6_anycast_cleanup' Full randconfig file is attached (for i386). -- ~Randy # # Automatically generated file; DO NOT EDIT. # Linux/i386 4.20.0-rc1 Kernel Configuration # # # Compiler: gcc (SUSE Linux) 4.8.5 # CONFIG_CC_IS_GCC=y CONFIG_GCC_VERSION=40805 CONFIG_CLANG_VERSION=0 CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_EXTABLE_SORT=y CONFIG_THREAD_INFO_IN_TASK=y # # General setup # CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_COMPILE_TEST=y CONFIG_LOCALVERSION="" CONFIG_BUILD_SALT="" CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_HAVE_KERNEL_LZ4=y # CONFIG_KERNEL_GZIP is not set CONFIG_KERNEL_BZIP2=y # CONFIG_KERNEL_LZMA is not set # CONFIG_KERNEL_XZ is not set # CONFIG_KERNEL_LZO is not set # CONFIG_KERNEL_LZ4 is not set CONFIG_DEFAULT_HOSTNAME="(none)" # CONFIG_SWAP is not set CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y # CONFIG_CROSS_MEMORY_ATTACH is not set # CONFIG_USELIB is not set # CONFIG_AUDIT is not set CONFIG_HAVE_ARCH_AUDITSYSCALL=y # # IRQ subsystem # CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_IRQ_CHIP=y CONFIG_IRQ_DOMAIN=y CONFIG_IRQ_SIM=y CONFIG_IRQ_DOMAIN_HIERARCHY=y CONFIG_GENERIC_MSI_IRQ=y CONFIG_GENERIC_MSI_IRQ_DOMAIN=y CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=y CONFIG_GENERIC_IRQ_RESERVATION_MODE=y CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y CONFIG_GENERIC_IRQ_DEBUGFS=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_ARCH_CLOCKSOURCE_DATA=y CONFIG_ARCH_CLOCKSOURCE_INIT=y CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y CONFIG_GENERIC_CMOS_UPDATE=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ_COMMON=y # CONFIG_HZ_PERIODIC is not set CONFIG_NO_HZ_IDLE=y CONFIG_NO_HZ=y # CONFIG_HIGH_RES_TIMERS is not set # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_PREEMPT_COUNT=y # # CPU/Task time and stats accounting # CONFIG_TICK_CPU_ACCOUNTING=y CONFIG_IRQ_TIME_ACCOUNTING=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y # CONFIG_TASK_IO_ACCOUNTING is not set # CONFIG_PSI is not set CONFIG_CPU_ISOLATION=y # # RCU Subsystem # CONFIG_TINY_RCU=y # CONFIG_RCU_EXPERT is not set CONFIG_SRCU=y CONFIG_TINY_SRCU=y CONFIG_TASKS_RCU=y # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=17 CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=y CONFIG_CGROUPS=y CONFIG_PAGE_COUNTER=y CONFIG_MEMCG=y CONFIG_BLK_CGROUP=y # CONFIG_DEBUG_BLK_CGROUP is not set CONFIG_CGROUP_WRITEBACK=y CONFIG_CGROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y CONFIG_CFS_BANDWIDTH=y # CONFIG_RT_GROUP_SCHED is not set # CONFIG_CGROUP_PIDS is not set CONFIG_CGROUP_RDMA=y CONFIG_CGROUP_FREEZER=y CONFIG_CGROUP_DEVICE=y # CONFIG_CGROUP_CPUACCT is not set CONFIG_CGROUP_PERF=y CONFIG_CGROUP_BPF=y # CONFIG_CGROUP_DEBUG is not set CONFIG_SOCK_CGROUP_DATA=y # CONFIG_NAMESPACES is not set CONFIG_CHECKPOINT_RESTORE=y # CONFIG_SCHED_AUTOGROUP is not set CONFIG_SYSFS_DEPRECATED=y CONFIG_SYSFS_DEPRECATED_V2=y # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set # CONFIG_CC_OPTIMIZE_FOR_DEBUGGING is not set CONFIG_HAVE_UID16=y CONFIG_SYSCTL_EXCEPTION_TRACE=y CONFIG_HAVE_PCSPKR_PLATFORM=y CONFIG_BPF=y CONFIG_EXPERT=y # CONFIG_UID16 is not set CONFIG_MULTIUSER=y CONFIG_SGETMASK_SYSCALL=y # CONFIG_SYSFS_SYSCALL is not set CONFIG_FHANDLE=y # CONFIG_POSIX_TIMERS is not set CONFIG_PRINTK=y CONFIG_PRINTK_NMI=y # CONFIG_BUG is not set CONFIG_PCSPKR_PLATFORM=y # CONFIG_BASE_FULL is not set CONFIG_FUTEX=y CONFIG_FUTEX_PI=y # CONFIG_EPOLL is not set # CONFIG_SIGNALFD is not set # CONFIG_TIMERFD is not set CONFIG_EVENTFD=y # CONFIG_SHMEM is not set # CONFIG_AIO is not set # CONFIG_ADVISE_SYSCALLS is not set CONFIG_MEMBARRIER=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_BASE_RELATIVE=y CONFIG_BPF_SYSCALL=y CONFIG_USERFAULTFD=y CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y CONFIG_RSEQ=y # CONFIG_DEBUG_RSEQ is not set # CONFIG_EMBEDDED is not set CONFIG_HAVE_PERF_EVENTS=y CONFIG_PERF_USE_VMALLOC=y CONFIG_PC104=y # # Kernel Performance Events And Counters # CONFIG_PERF_EVENTS=y CONFIG_DEBUG_PERF_USE_VMALLOC=y CONFIG_VM_EVENT_COUNTERS=y # CONFIG_COMPAT_BRK is not set # CONFIG_SLAB is not set # CONFIG_SLUB is not set CONFIG_SLOB=y CONFIG_SLAB_MERGE_DEFAULT=y CONFIG_SYSTEM_DATA_VERIFICATION=y CONFIG_PROFILING=y CONFIG_TRACEPOINTS=y
Re: linux-next: Tree for Nov 5
On Wed, Nov 05, 2014 at 05:53:30PM +1100, Stephen Rothwell wrote: > Hi all, > > Due to a move of office, there will not be a linux-next release on > Friday (and maybe Monday). > > Changes since 20141104: > > The f2fs tree gained a build failure so I used the version from > next-20141104. > > The mfd tree lost its build failure. > > The iommu tree gained a build failure so I used the version from > next-20141104. > > The usb tree gained a conflict against the usb.current tree. > > The staging tree gained conflicts against the v4l-dvb tree. > > The scsi tree still had its its build failure, so I applied a supplied > patch. > > The akpm tree lost a patch that turned up elsewhere. > > Non-merge commits (relative to Linus' tree): 3680 > 3064 files changed, 103787 insertions(+), 114924 deletions(-) > Build results: total: 133 pass: 117 fail: 16 Failed builds: arm:omap2plus_defconfig arm:axm55xx_defconfig arm64:defconfig avr32:defconfig m68k:allmodconfig microblaze:mmu_defconfig microblaze:nommu_defconfig mips:allmodconfig mips:nlm_xlp_defconfig powerpc:mpc85xx_defconfig powerpc:mpc85xx_smp_defconfig powerpc:mpc85xx_defconfig powerpc:mpc85xx_smp_defconfig s390:defconfig tile:tilegx_defconfig Qemu test results: total: 30 pass: 28 fail: 2 Failed tests: arm64:arm64_smp_defconfig arm64:arm64_nosmp_defconfig Browsing through the failures, they all seem to be due to the missing declaration of 'audit_file'. A patch for that problem is pending with https://lkml.org/lkml/2014/11/4/528. Guenter -- 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 Nov 5
On Wed, Nov 05, 2014 at 05:53:30PM +1100, Stephen Rothwell wrote: Hi all, Due to a move of office, there will not be a linux-next release on Friday (and maybe Monday). Changes since 20141104: The f2fs tree gained a build failure so I used the version from next-20141104. The mfd tree lost its build failure. The iommu tree gained a build failure so I used the version from next-20141104. The usb tree gained a conflict against the usb.current tree. The staging tree gained conflicts against the v4l-dvb tree. The scsi tree still had its its build failure, so I applied a supplied patch. The akpm tree lost a patch that turned up elsewhere. Non-merge commits (relative to Linus' tree): 3680 3064 files changed, 103787 insertions(+), 114924 deletions(-) Build results: total: 133 pass: 117 fail: 16 Failed builds: arm:omap2plus_defconfig arm:axm55xx_defconfig arm64:defconfig avr32:defconfig m68k:allmodconfig microblaze:mmu_defconfig microblaze:nommu_defconfig mips:allmodconfig mips:nlm_xlp_defconfig powerpc:mpc85xx_defconfig powerpc:mpc85xx_smp_defconfig powerpc:mpc85xx_defconfig powerpc:mpc85xx_smp_defconfig s390:defconfig tile:tilegx_defconfig Qemu test results: total: 30 pass: 28 fail: 2 Failed tests: arm64:arm64_smp_defconfig arm64:arm64_nosmp_defconfig Browsing through the failures, they all seem to be due to the missing declaration of 'audit_file'. A patch for that problem is pending with https://lkml.org/lkml/2014/11/4/528. Guenter -- 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 Nov 5 (tty/serial/xilinx_uartps)
On 11/04/13 23:16, Stephen Rothwell wrote: > Hi all, > > Changes since 20131104: on i386: drivers/tty/serial/xilinx_uartps.c: In function 'xuartps_isr': drivers/tty/serial/xilinx_uartps.c:247:13: error: 'struct uart_port' has no member named 'sysrq' -- ~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 Nov 5 (tty/serial/xilinx_uartps)
On 11/04/13 23:16, Stephen Rothwell wrote: Hi all, Changes since 20131104: on i386: drivers/tty/serial/xilinx_uartps.c: In function 'xuartps_isr': drivers/tty/serial/xilinx_uartps.c:247:13: error: 'struct uart_port' has no member named 'sysrq' -- ~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/
