diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/108/other/877 | 121 | ||||
| -rw-r--r-- | results/classifier/108/other/877498 | 77 |
2 files changed, 198 insertions, 0 deletions
diff --git a/results/classifier/108/other/877 b/results/classifier/108/other/877 new file mode 100644 index 00000000..e275f1c6 --- /dev/null +++ b/results/classifier/108/other/877 @@ -0,0 +1,121 @@ +graphic: 0.915 +permissions: 0.893 +semantic: 0.872 +PID: 0.857 +performance: 0.845 +debug: 0.842 +other: 0.825 +device: 0.812 +boot: 0.806 +files: 0.802 +socket: 0.726 +network: 0.722 +vnc: 0.712 +KVM: 0.686 + +qemu-system-x86_64: Linux kernel warning when CONFIG_NUMA_EMU is enabled +Description of problem: +When Linux kernel is run on qemu 6.2, it prints a warning when `NUMA_EMU` is used. When the same kernel is run on qemu 6.1.1 (`54e1f5be86dd11744e45da8be6afad01d01d59e7`) or earlier, no such warning is printed. + +``` +[ 0.341924] smpboot: CPU0: Intel QEMU Virtual CPU version 2.5+ (family: 0xf, model: 0x6b, stepping: 0x1) +[ 0.342371] Performance Events: unsupported Netburst CPU model 107 no PMU driver, software events only. +[ 0.343302] rcu: Hierarchical SRCU implementation. +[ 0.344470] smp: Bringing up secondary CPUs ... +[ 0.345349] x86: Booting SMP configuration: +[ 0.345945] .... node #1, CPUs: #1 +[ 0.014099] ------------[ cut here ]------------ +[ 0.014099] sched: CPU #1's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. +[ 0.014099] WARNING: CPU: 1 PID: 0 at arch/x86/kernel/smpboot.c:423 topology_sane.isra.0+0x62/0x70 +[ 0.014099] Modules linked in: +[ 0.014099] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.16.9 #6 +[ 0.014099] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 +[ 0.014099] RIP: 0010:topology_sane.isra.0+0x62/0x70 +[ 0.014099] Code: 80 3d e1 72 a1 01 00 75 f6 48 83 ec 08 4c 89 da 44 89 d6 48 c7 c7 c0 cd f4 8b 88 44 24 07 c6 05 c3 72 a1 01 01 e8 3c 16 b7 00 <0f> 0b 0f b6 44 24 07 48 83 c4 08 c3 66 90 48 8b 0d 21 95 a3 01 0f +[ 0.014099] RSP: 0000:ffffa8c3006a3ed8 EFLAGS: 00010086 +[ 0.014099] RAX: 0000000000000000 RBX: ffffa335fdc15480 RCX: 0000000000000000 +[ 0.014099] RDX: 0000000000000002 RSI: 00000000ffffffea RDI: 00000000ffffffff +[ 0.014099] RBP: ffffa3353dc15480 R08: ffffffff8c335ac8 R09: 00000000ffffdfff +[ 0.014099] R10: ffffffff8c255ae0 R11: ffffffff8c255ae0 R12: 0000000000000001 +[ 0.014099] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000001 +[ 0.014099] FS: 0000000000000000(0000) GS:ffffa335fdc00000(0000) knlGS:0000000000000000 +[ 0.014099] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 +[ 0.014099] CR2: 0000000000000000 CR3: 0000000112a0c000 CR4: 00000000000006e0 +[ 0.014099] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 +[ 0.014099] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 +[ 0.014099] Call Trace: +[ 0.014099] <TASK> +[ 0.014099] set_cpu_sibling_map+0x16a/0x560 +[ 0.014099] start_secondary+0x42/0xf0 +[ 0.014099] secondary_startup_64_no_verify+0xc2/0xcb +[ 0.014099] </TASK> +[ 0.014099] Kernel panic - not syncing: panic_on_warn set ... +[ 0.014099] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.16.9 #6 +[ 0.014099] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 +[ 0.014099] Call Trace: +[ 0.014099] <TASK> +[ 0.014099] dump_stack_lvl+0x34/0x44 +[ 0.014099] panic+0xef/0x2a6 +[ 0.014099] ? topology_sane.isra.0+0x62/0x70 +[ 0.014099] __warn.cold+0x26/0x30 +[ 0.014099] ? topology_sane.isra.0+0x62/0x70 +[ 0.014099] report_bug+0x9a/0xc0 +[ 0.014099] handle_bug+0x3c/0x60 +[ 0.014099] exc_invalid_op+0x14/0x70 +[ 0.014099] asm_exc_invalid_op+0x12/0x20 +[ 0.014099] RIP: 0010:topology_sane.isra.0+0x62/0x70 +[ 0.014099] Code: 80 3d e1 72 a1 01 00 75 f6 48 83 ec 08 4c 89 da 44 89 d6 48 c7 c7 c0 cd f4 8b 88 44 24 07 c6 05 c3 72 a1 01 01 e8 3c 16 b7 00 <0f> 0b 0f b6 44 24 07 48 83 c4 08 c3 66 90 48 8b 0d 21 95 a3 01 0f +[ 0.014099] RSP: 0000:ffffa8c3006a3ed8 EFLAGS: 00010086 +[ 0.014099] RAX: 0000000000000000 RBX: ffffa335fdc15480 RCX: 0000000000000000 +[ 0.014099] RDX: 0000000000000002 RSI: 00000000ffffffea RDI: 00000000ffffffff +[ 0.014099] RBP: ffffa3353dc15480 R08: ffffffff8c335ac8 R09: 00000000ffffdfff +[ 0.014099] R10: ffffffff8c255ae0 R11: ffffffff8c255ae0 R12: 0000000000000001 +[ 0.014099] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000001 +[ 0.014099] ? topology_sane.isra.0+0x62/0x70 +[ 0.014099] set_cpu_sibling_map+0x16a/0x560 +[ 0.014099] start_secondary+0x42/0xf0 +[ 0.014099] secondary_startup_64_no_verify+0xc2/0xcb +[ 0.014099] </TASK> +[ 0.014099] ---[ end Kernel panic - not syncing: panic_on_warn set ... ]--- +``` +Steps to reproduce: +1. Check out the Linux kernel: +``` +git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git +cd linux-stable +git checkout v5.16.9 +``` +2. Generate the configuration file: +``` +make defconfig +./scripts/config -e NUMA_EMU -e CMDLINE_BOOL --set-str CMDLINE "numa=fake=2 panic_on_warn=1" -d CONFIG_CMDLINE_OVERRIDE +``` +3. Build the kernel +``` +make -j32 +``` +4. Run qemu and wait for a couple of seconds: +``` +./qemu-system-x86_64 -m 4G -smp 2 -kernel ~/linux-stable/arch/x86/boot/bzImage -append "console=ttyS0 root=/dev/sda earlyprintk=serial" -enable-kvm -nographic -snapshot +``` +Additional information: +With explicit NUMA configuration, it boots fine: +``` +./qemu-system-x86_64 -m 4G -smp 2 -object memory-backend-ram,size=8G,id=m0 -numa node,cpus=0-1,nodeid=0,memdev=m0 -kernel ~/linux-stable/arch/x86/boot/bzImage -append "console=ttyS0 root=/dev/sda earlyprintk=serial" -enable-kvm -nographic -snapshot +``` + +On the host machine: +``` +$ numactl -H +available: 2 nodes (0-1) +node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 +node 0 size: 95259 MB +node 0 free: 1767 MB +node 1 cpus: 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 +node 1 size: 96757 MB +node 1 free: 2407 MB +node distances: +node 0 1 + 0: 10 21 + 1: 21 10 +``` diff --git a/results/classifier/108/other/877498 b/results/classifier/108/other/877498 new file mode 100644 index 00000000..ac8da58f --- /dev/null +++ b/results/classifier/108/other/877498 @@ -0,0 +1,77 @@ +device: 0.867 +vnc: 0.837 +PID: 0.730 +other: 0.705 +KVM: 0.675 +graphic: 0.673 +boot: 0.635 +performance: 0.602 +debug: 0.585 +permissions: 0.573 +socket: 0.553 +files: 0.535 +semantic: 0.527 +network: 0.477 + +qemu does not pass sector size from physical devices to virtual devices + +When passing a physical disk (i.e. a multipathed fcal volume in my case) with a 4k sector size as raw image to qemu (-drive file=/dev/mapper/hartebeest-sys,if=none,id=drive-virtio-disk0,boot=on,format=raw), the resulting virtual device has a sector size of 512b, rendering the partition table unusable! + +QEMU 0.12 is pretty much outdated ... can you still reproduce this issue with the latest version of QEMU, or can we close this bug nowadays? + +Hi, + +I can’t verify it for the logical block size right away, but +this bug still present for the physical block size in qemu-kvm 1:2.1+dfsg-1. + +I will try to verify this bug with testing soon + +> On 20. Mar 2017, at 23:57, Thomas Huth <email address hidden> wrote: +> +> QEMU 0.12 is pretty much outdated ... can you still reproduce this issue +> with the latest version of QEMU, or can we close this bug nowadays? +> +> ** Changed in: qemu +> Status: New => Incomplete +> +> -- +> You received this bug notification because you are subscribed to the bug +> report. +> https://bugs.launchpad.net/bugs/877498 +> +> Title: +> qemu does not pass sector size from physical devices to virtual +> devices +> +> Status in QEMU: +> Incomplete +> +> Bug description: +> When passing a physical disk (i.e. a multipathed fcal volume in my +> case) with a 4k sector size as raw image to qemu (-drive +> file=/dev/mapper/hartebeest-sys,if=none,id=drive-virtio- +> disk0,boot=on,format=raw), the resulting virtual device has a sector +> size of 512b, rendering the partition table unusable. +> +> Versions used: QEMU 0.12.5 (qemu-kvm-0.12.5) from debian unstable +> +> To manage notifications about this bug go to: +> https://bugs.launchpad.net/qemu/+bug/877498/+subscriptions +> + +AVE! + Philipp S. Tiesel / phils… +-- + {phils}--->---(<email address hidden>)--->---(http://phils.in-panik.de)----, + wenn w eine aube ist dn man au dran dre en | + o Schr an muss hc h (Kurt Schwitters) | +:wq! <----(phone: +49-179-6737439)---<---(jabber: <email address hidden>)----' + + + +QEMU 2.1 is also not supported anymore. Please test with the latest upstream QEMU version (2.8 ... or the latest 2.9 release candidate) - or otherwise report the bug in the bug tracker of your distribution instead. + +[Expired for QEMU because there has been no activity for 60 days.] + +Recent QEMU is able to do read-modify-write operations when using 512 byte logical sectors in the VM and 4K logical sectors in the host. + |