* linux-next: qemu boot failure after merge of the tip tree
@ 2021-02-01 9:09 Stephen Rothwell
2021-02-01 13:04 ` Valentin Schneider
0 siblings, 1 reply; 6+ messages in thread
From: Stephen Rothwell @ 2021-02-01 9:09 UTC (permalink / raw)
To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
Cc: Valentin Schneider, Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1.1: Type: text/plain, Size: 3140 bytes --]
Hi all,
After merging the tip tree, today's linux-next qemu boot test (powerpc
pseries_le_defconfig) failed like this:
[ 0.005355][ T1] smp: Brought up 1 node, 1 CPU
[ 0.005415][ T1] numa: Node 0 CPUs: 0
[ 0.005496][ T1] BUG: Unable to handle kernel instruction fetch (NULL pointer?)
[ 0.005559][ T1] Faulting instruction address: 0x00000000
[ 0.005613][ T1] Oops: Kernel access of bad area, sig: 11 [#1]
[ 0.005665][ T1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries
[ 0.005719][ T1] Modules linked in:
[ 0.005754][ T1] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.11.0-rc6 #2
[ 0.005808][ T1] NIP: 0000000000000000 LR: c0000000001a22ac CTR: 0000000000000001
[ 0.005870][ T1] REGS: c0000000063a3860 TRAP: 0480 Not tainted (5.11.0-rc6)
[ 0.005933][ T1] MSR: 8000000002009033 <SF,VEC,EE,ME,IR,DR,RI,LE> CR: 24002242 XER: 20000000
[ 0.006014][ T1] CFAR: c0000000001a22a8 IRQMASK: 0
[ 0.006014][ T1] GPR00: c0000000001a21ac c0000000063a3b00 c000000001439400 0000000000000000
[ 0.006014][ T1] GPR04: 0000000000000000 00000000000000c4 0000000000000001 c000000001509400
[ 0.006014][ T1] GPR08: 0000000000000000 c0000000011f5af0 000000007eaa0000 0000000000000001
[ 0.006014][ T1] GPR12: 0000000000000001 c000000001610000 c000000006350f18 0000000000000001
[ 0.006014][ T1] GPR16: c000000001507bb0 0000000000000000 c0000000012106b0 c00000000146dce0
[ 0.006014][ T1] GPR20: c000000006054a90 0000000000000001 0000000000000000 00000000ffff8ad0
[ 0.006014][ T1] GPR24: 00000000ffff8ad0 c000000006054a00 0000000000000000 c000000006055000
[ 0.006014][ T1] GPR28: 0000000000000000 c000000006350f00 c000000006350f00 c000000001472380
[ 0.006590][ T1] NIP [0000000000000000] 0x0
[ 0.006633][ T1] LR [c0000000001a22ac] build_sched_domains+0x47c/0x1500
[ 0.006687][ T1] Call Trace:
[ 0.006719][ T1] [c0000000063a3b00] [c0000000001a21ac] build_sched_domains+0x37c/0x1500 (unreliable)
[ 0.006794][ T1] [c0000000063a3c40] [c0000000001a42d0] sched_init_domains+0xe0/0x120
[ 0.006858][ T1] [c0000000063a3c90] [c000000001075f38] sched_init_smp+0x50/0xc4
[ 0.006922][ T1] [c0000000063a3cc0] [c0000000010545a4] kernel_init_freeable+0x1d4/0x398
[ 0.006987][ T1] [c0000000063a3da0] [c000000000013144] kernel_init+0x2c/0x168
[ 0.007051][ T1] [c0000000063a3e10] [c00000000000dff0] ret_from_kernel_thread+0x5c/0x6c
[ 0.007116][ T1] Instruction dump:
[ 0.007150][ T1] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
[ 0.007226][ T1] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
[ 0.007310][ T1] ---[ end trace e117133fa9cbc962 ]---
(full boot log attached)
Presumably caused by commit
620a6dc40754 ("sched/topology: Make sched_init_numa() use a set for the deduplicating sort")
I note a similar report from the kernel test robot on LKML.
I have reverted that commit for today (which fixed the boot failure).
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: bootlog.txt --]
[-- Type: text/plain, Size: 11376 bytes --]
spawn qemu-system-ppc64 -M pseries -m 2G -vga none -nographic -enable-kvm -kernel /home/sfr/next/powerpc_pseries_le_defconfig/vmlinux -initrd ./ppc64le-rootfs.cpio.gz
KVM: Failed to create TCE64 table for liobn 0x71000002
KVM: Failed to create TCE64 table for liobn 0x71000003
KVM: Failed to create TCE64 table for liobn 0x80000000
SLOF^[[0m^[[?25l **********************************************************************
^[[1mQEMU Starting
^[[0m Build Date = Dec 29 2020 12:07:03
FW Version = release 20200717
Press "s" to enter Open Firmware.
^[[0m^[[?25hC0000C0100C0120C0140C0200C0240C0260C02E0C0300C0320C0340C0360C0370C0380C0371C0373C0374C03F0C0400C0480C04C0C04D0C0500Populating /vdevice methods
Populating /vdevice/vty@71000000
Populating /vdevice/nvram@71000001
Populating /vdevice/l-lan@71000002
Populating /vdevice/v-scsi@71000003
SCSI: Looking for devices
8200000000000000 CD-ROM : "QEMU QEMU CD-ROM 2.5+"
C05A0Populating /pci@800000020000000
C0600C06C0C0700C0800C0880No NVRAM common partition, re-initializing...
C0890C08A0C08A8C08B0Scanning USB
C08C0C08D0Using default console: /vdevice/vty@71000000
C08E0C08E8Detected RAM kernel at 400000 (160a5a8 bytes)
C08FF
Welcome to Open Firmware
Copyright (c) 2004, 2017 IBM Corporation All rights reserved.
This program and the accompanying materials are made available
under the terms of the BSD License available at
http://www.opensource.org/licenses/bsd-license.php
Booting from memory...
OF stdout device is: /vdevice/vty@71000000
Preparing to boot Linux version 5.11.0-rc6 (sfr@ash) (gcc (Debian 10.2.1-3) 10.2.1 20201224, GNU ld (GNU Binutils for Debian) 2.35.1) #2 SMP Mon Feb 1 19:12:28 AEDT 2021
Detected machine type: 0000000000000101
command line:
Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... done
memory layout at init:
memory_limit : 0000000000000000 (16 MB aligned)
alloc_bottom : 0000000001bf0000
alloc_top : 0000000030000000
alloc_top_hi : 0000000080000000
rmo_top : 0000000030000000
ram_top : 0000000080000000
instantiating rtas at 0x000000002fff0000... done
prom_hold_cpus: skipped
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x0000000001c00000 -> 0x0000000001c00a77
Device tree struct 0x0000000001c10000 -> 0x0000000001c20000
Quiescing Open Firmware ...
Booting Linux via __start() @ 0x0000000000400000 ...
[ 0.000000][ T0] hash-mmu: Page sizes from device-tree:
[ 0.000000][ T0] hash-mmu: base_shift=12: shift=12, sllp=0x0000, avpnm=0x00000000, tlbiel=1, penc=0
[ 0.000000][ T0] hash-mmu: base_shift=16: shift=16, sllp=0x0110, avpnm=0x00000000, tlbiel=1, penc=1
[ 0.000000][ T0] Using 1TB segments
[ 0.000000][ T0] hash-mmu: Initializing hash mmu with SLB
[ 0.000000][ T0] Linux version 5.11.0-rc6 (sfr@ash) (gcc (Debian 10.2.1-3) 10.2.1 20201224, GNU ld (GNU Binutils for Debian) 2.35.1) #2 SMP Mon Feb 1 19:12:28 AEDT 2021
[ 0.000000][ T0] Found initrd at 0xc000000001a20000:0xc000000001bed70b
[ 0.000000][ T0] Using pSeries machine description
[ 0.000000][ T0] printk: bootconsole [udbg0] enabled
[ 0.000000][ T0] Partition configured for 1 cpus.
[ 0.000000][ T0] CPU maps initialized for 1 thread per core
[ 0.000000][ T0] -----------------------------------------------------
[ 0.000000][ T0] phys_mem_size = 0x80000000
[ 0.000000][ T0] dcache_bsize = 0x80
[ 0.000000][ T0] icache_bsize = 0x80
[ 0.000000][ T0] cpu_features = 0x000002eb8f4d9187
[ 0.000000][ T0] possible = 0x000ffbfbcf5fb187
[ 0.000000][ T0] always = 0x0000000380008181
[ 0.000000][ T0] cpu_user_features = 0xdc0065c2 0xae000000
[ 0.000000][ T0] mmu_features = 0x78006001
[ 0.000000][ T0] firmware_features = 0x00000085455a445f
[ 0.000000][ T0] vmalloc start = 0xc008000000000000
[ 0.000000][ T0] IO start = 0xc00a000000000000
[ 0.000000][ T0] vmemmap start = 0xc00c000000000000
[ 0.000000][ T0] hash-mmu: ppc64_pft_size = 0x18
[ 0.000000][ T0] hash-mmu: htab_hash_mask = 0x1ffff
[ 0.000000][ T0] -----------------------------------------------------
[ 0.000000][ T0] numa: NODE_DATA [mem 0x7ffe7080-0x7ffebfff]
[ 0.000000][ T0] rfi-flush: fallback displacement flush available
[ 0.000000][ T0] rfi-flush: ori type flush available
[ 0.000000][ T0] rfi-flush: mttrig type flush available
[ 0.000000][ T0] count-cache-flush: hardware flush enabled.
[ 0.000000][ T0] link-stack-flush: software flush enabled.
[ 0.000000][ T0] stf-barrier: hwsync barrier available
[ 0.000000][ T0] PCI host bridge /pci@800000020000000 ranges:
[ 0.000000][ T0] IO 0x0000200000000000..0x000020000000ffff -> 0x0000000000000000
[ 0.000000][ T0] MEM 0x0000200080000000..0x00002000ffffffff -> 0x0000000080000000
[ 0.000000][ T0] MEM 0x0000210000000000..0x000021ffffffffff -> 0x0000210000000000
[ 0.000000][ T0] PCI: OF: PROBE_ONLY disabled
[ 0.000000][ T0] PPC64 nvram contains 65536 bytes
[ 0.000000][ T0] PV qspinlock hash table entries: 4096 (order: 0, 65536 bytes, linear)
[ 0.000000][ T0] barrier-nospec: using ORI speculation barrier
[ 0.000000][ T0] Zone ranges:
[ 0.000000][ T0] Normal [mem 0x0000000000000000-0x000000007fffffff]
[ 0.000000][ T0] Movable zone start for each node
[ 0.000000][ T0] Early memory node ranges
[ 0.000000][ T0] node 0: [mem 0x0000000000000000-0x000000007fffffff]
[ 0.000000][ T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000007fffffff]
[ 0.000000][ T0] percpu: Embedded 10 pages/cpu s604440 r0 d50920 u1048576
[ 0.000000][ T0] Built 1 zonelists, mobility grouping on. Total pages: 32736
[ 0.000000][ T0] Policy zone: Normal
[ 0.000000][ T0] Kernel command line:
[ 0.000000][ T0] Dentry cache hash table entries: 262144 (order: 5, 2097152 bytes, linear)
[ 0.000000][ T0] Inode-cache hash table entries: 131072 (order: 4, 1048576 bytes, linear)
[ 0.000000][ T0] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000][ T0] Memory: 1999872K/2097152K available (13824K kernel code, 2688K rwdata, 2816K rodata, 1728K init, 1449K bss, 97280K reserved, 0K cma-reserved)
[ 0.000000][ T0] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000][ T0] ftrace: allocating 32011 entries in 12 pages
[ 0.000000][ T0] ftrace: allocated 12 pages with 2 groups
[ 0.000000][ T0] rcu: Hierarchical RCU implementation.
[ 0.000000][ T0] rcu: RCU event tracing is enabled.
[ 0.000000][ T0] rcu: RCU restricting CPUs from NR_CPUS=2048 to nr_cpu_ids=1.
[ 0.000000][ T0] Rude variant of Tasks RCU enabled.
[ 0.000000][ T0] Tracing variant of Tasks RCU enabled.
[ 0.000000][ T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000][ T0] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[ 0.000000][ T0] NR_IRQS: 512, nr_irqs: 512, preallocated irqs: 16
[ 0.000000][ T0] random: get_random_u64 called from start_kernel+0x4ec/0x728 with crng_init=0
[ 0.000001][ T0] clocksource: timebase: mask: 0xffffffffffffffff max_cycles: 0x761537d007, max_idle_ns: 440795202126 ns
[ 0.001234][ T0] clocksource: timebase mult[1f40000] shift[24] registered
[ 0.002066][ T0] Console: colour dummy device 80x25
[ 0.002643][ T0] printk: console [hvc0] enabled
[ 0.002643][ T0] printk: console [hvc0] enabled
[ 0.003220][ T0] printk: bootconsole [udbg0] disabled
[ 0.003220][ T0] printk: bootconsole [udbg0] disabled
[ 0.003912][ T0] pid_max: default: 32768 minimum: 301
[ 0.003989][ T0] Mount-cache hash table entries: 8192 (order: 0, 65536 bytes, linear)
[ 0.004061][ T0] Mountpoint-cache hash table entries: 8192 (order: 0, 65536 bytes, linear)
[ 0.004655][ T1] POWER8 performance monitor hardware support registered
[ 0.004712][ T1] power8-pmu: PMAO restore workaround active.
[ 0.004778][ T1] rcu: Hierarchical SRCU implementation.
[ 0.005308][ T1] smp: Bringing up secondary CPUs ...
[ 0.005355][ T1] smp: Brought up 1 node, 1 CPU
[ 0.005415][ T1] numa: Node 0 CPUs: 0
[ 0.005496][ T1] BUG: Unable to handle kernel instruction fetch (NULL pointer?)
[ 0.005559][ T1] Faulting instruction address: 0x00000000
[ 0.005613][ T1] Oops: Kernel access of bad area, sig: 11 [#1]
[ 0.005665][ T1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries
[ 0.005719][ T1] Modules linked in:
[ 0.005754][ T1] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.11.0-rc6 #2
[ 0.005808][ T1] NIP: 0000000000000000 LR: c0000000001a22ac CTR: 0000000000000001
[ 0.005870][ T1] REGS: c0000000063a3860 TRAP: 0480 Not tainted (5.11.0-rc6)
[ 0.005933][ T1] MSR: 8000000002009033 <SF,VEC,EE,ME,IR,DR,RI,LE> CR: 24002242 XER: 20000000
[ 0.006014][ T1] CFAR: c0000000001a22a8 IRQMASK: 0
[ 0.006014][ T1] GPR00: c0000000001a21ac c0000000063a3b00 c000000001439400 0000000000000000
[ 0.006014][ T1] GPR04: 0000000000000000 00000000000000c4 0000000000000001 c000000001509400
[ 0.006014][ T1] GPR08: 0000000000000000 c0000000011f5af0 000000007eaa0000 0000000000000001
[ 0.006014][ T1] GPR12: 0000000000000001 c000000001610000 c000000006350f18 0000000000000001
[ 0.006014][ T1] GPR16: c000000001507bb0 0000000000000000 c0000000012106b0 c00000000146dce0
[ 0.006014][ T1] GPR20: c000000006054a90 0000000000000001 0000000000000000 00000000ffff8ad0
[ 0.006014][ T1] GPR24: 00000000ffff8ad0 c000000006054a00 0000000000000000 c000000006055000
[ 0.006014][ T1] GPR28: 0000000000000000 c000000006350f00 c000000006350f00 c000000001472380
[ 0.006590][ T1] NIP [0000000000000000] 0x0
[ 0.006633][ T1] LR [c0000000001a22ac] build_sched_domains+0x47c/0x1500
[ 0.006687][ T1] Call Trace:
[ 0.006719][ T1] [c0000000063a3b00] [c0000000001a21ac] build_sched_domains+0x37c/0x1500 (unreliable)
[ 0.006794][ T1] [c0000000063a3c40] [c0000000001a42d0] sched_init_domains+0xe0/0x120
[ 0.006858][ T1] [c0000000063a3c90] [c000000001075f38] sched_init_smp+0x50/0xc4
[ 0.006922][ T1] [c0000000063a3cc0] [c0000000010545a4] kernel_init_freeable+0x1d4/0x398
[ 0.006987][ T1] [c0000000063a3da0] [c000000000013144] kernel_init+0x2c/0x168
[ 0.007051][ T1] [c0000000063a3e10] [c00000000000dff0] ret_from_kernel_thread+0x5c/0x6c
[ 0.007116][ T1] Instruction dump:
[ 0.007150][ T1] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
[ 0.007226][ T1] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
[ 0.007310][ T1] ---[ end trace e117133fa9cbc962 ]---
[ 0.007354][ T1]
[ 1.007387][ T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
qemu-system-ppc64: OS terminated: OS panic: Attempted to kill init! exitcode=0x0000000b
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: linux-next: qemu boot failure after merge of the tip tree
2021-02-01 9:09 linux-next: qemu boot failure after merge of the tip tree Stephen Rothwell
@ 2021-02-01 13:04 ` Valentin Schneider
2021-02-01 14:40 ` Peter Zijlstra
0 siblings, 1 reply; 6+ messages in thread
From: Valentin Schneider @ 2021-02-01 13:04 UTC (permalink / raw)
To: Stephen Rothwell, Thomas Gleixner, Ingo Molnar, H. Peter Anvin,
Peter Zijlstra
Cc: Linux Kernel Mailing List, Linux Next Mailing List
On 01/02/21 20:09, Stephen Rothwell wrote:
> Hi all,
>
Hi Stephen,
> After merging the tip tree, today's linux-next qemu boot test (powerpc
> pseries_le_defconfig) failed like this:
In case you haven't seen it, Dietmar did the dirty work and fixed my fail
at
http://lore.kernel.org/r/6000e39e-7d28-c360-9cd6-8798fd22a9bf@arm.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: linux-next: qemu boot failure after merge of the tip tree
2021-02-01 13:04 ` Valentin Schneider
@ 2021-02-01 14:40 ` Peter Zijlstra
2021-02-10 4:53 ` Stephen Rothwell
0 siblings, 1 reply; 6+ messages in thread
From: Peter Zijlstra @ 2021-02-01 14:40 UTC (permalink / raw)
To: Valentin Schneider
Cc: Stephen Rothwell, Thomas Gleixner, Ingo Molnar, H. Peter Anvin,
Linux Kernel Mailing List, Linux Next Mailing List
On Mon, Feb 01, 2021 at 01:04:30PM +0000, Valentin Schneider wrote:
> On 01/02/21 20:09, Stephen Rothwell wrote:
> > Hi all,
> >
>
> Hi Stephen,
>
> > After merging the tip tree, today's linux-next qemu boot test (powerpc
> > pseries_le_defconfig) failed like this:
>
> In case you haven't seen it, Dietmar did the dirty work and fixed my fail
> at
>
> http://lore.kernel.org/r/6000e39e-7d28-c360-9cd6-8798fd22a9bf@arm.com
Right, picked that up, I'll try and push it before the next next ;-)
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: linux-next: qemu boot failure after merge of the tip tree
2021-02-01 14:40 ` Peter Zijlstra
@ 2021-02-10 4:53 ` Stephen Rothwell
2021-02-15 9:56 ` Ingo Molnar
0 siblings, 1 reply; 6+ messages in thread
From: Stephen Rothwell @ 2021-02-10 4:53 UTC (permalink / raw)
To: Peter Zijlstra
Cc: Valentin Schneider, Thomas Gleixner, Ingo Molnar, H. Peter Anvin,
Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
Hi Peter,
On Mon, 1 Feb 2021 15:40:12 +0100 Peter Zijlstra <peterz@infradead.org> wrote:
>
> On Mon, Feb 01, 2021 at 01:04:30PM +0000, Valentin Schneider wrote:
> > On 01/02/21 20:09, Stephen Rothwell wrote:
> > > Hi all,
> > >
> >
> > Hi Stephen,
> >
> > > After merging the tip tree, today's linux-next qemu boot test (powerpc
> > > pseries_le_defconfig) failed like this:
> >
> > In case you haven't seen it, Dietmar did the dirty work and fixed my fail
> > at
> >
> > http://lore.kernel.org/r/6000e39e-7d28-c360-9cd6-8798fd22a9bf@arm.com
>
> Right, picked that up, I'll try and push it before the next next ;-)
This fix has not reached the tip auto-latest branch yet and so is not
in linux-next.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: linux-next: qemu boot failure after merge of the tip tree
2021-02-10 4:53 ` Stephen Rothwell
@ 2021-02-15 9:56 ` Ingo Molnar
2021-02-15 9:59 ` Stephen Rothwell
0 siblings, 1 reply; 6+ messages in thread
From: Ingo Molnar @ 2021-02-15 9:56 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Peter Zijlstra, Valentin Schneider, Thomas Gleixner, Ingo Molnar,
H. Peter Anvin, Linux Kernel Mailing List,
Linux Next Mailing List
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Peter,
>
> On Mon, 1 Feb 2021 15:40:12 +0100 Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > On Mon, Feb 01, 2021 at 01:04:30PM +0000, Valentin Schneider wrote:
> > > On 01/02/21 20:09, Stephen Rothwell wrote:
> > > > Hi all,
> > > >
> > >
> > > Hi Stephen,
> > >
> > > > After merging the tip tree, today's linux-next qemu boot test (powerpc
> > > > pseries_le_defconfig) failed like this:
> > >
> > > In case you haven't seen it, Dietmar did the dirty work and fixed my fail
> > > at
> > >
> > > http://lore.kernel.org/r/6000e39e-7d28-c360-9cd6-8798fd22a9bf@arm.com
> >
> > Right, picked that up, I'll try and push it before the next next ;-)
>
> This fix has not reached the tip auto-latest branch yet and so is not in
> linux-next.
This fix should be there now as:
e972d92d52a1: ("sched/topology: Fix sched_domain_topology_level alloc in sched_init_numa()")
Thanks,
Ingo
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: linux-next: qemu boot failure after merge of the tip tree
2021-02-15 9:56 ` Ingo Molnar
@ 2021-02-15 9:59 ` Stephen Rothwell
0 siblings, 0 replies; 6+ messages in thread
From: Stephen Rothwell @ 2021-02-15 9:59 UTC (permalink / raw)
To: Ingo Molnar
Cc: Peter Zijlstra, Valentin Schneider, Thomas Gleixner, Ingo Molnar,
H. Peter Anvin, Linux Kernel Mailing List,
Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
Hi Ingo,
On Mon, 15 Feb 2021 10:56:51 +0100 Ingo Molnar <mingo@kernel.org> wrote:
>
> * Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > This fix has not reached the tip auto-latest branch yet and so is not in
> > linux-next.
>
> This fix should be there now as:
>
> e972d92d52a1: ("sched/topology: Fix sched_domain_topology_level alloc in sched_init_numa()")
Yeah, thanks. It appears that my email and the patch turning up
overlapped. So it is all good now.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2021-02-15 10:01 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-01 9:09 linux-next: qemu boot failure after merge of the tip tree Stephen Rothwell
2021-02-01 13:04 ` Valentin Schneider
2021-02-01 14:40 ` Peter Zijlstra
2021-02-10 4:53 ` Stephen Rothwell
2021-02-15 9:56 ` Ingo Molnar
2021-02-15 9:59 ` Stephen Rothwell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).