Lkft-triage

lkft-triage@lists.linaro.org

31 participants
34106 discussions

Re: next: kernel BUG at drivers/virtio/virtio.c:122!

by Michael S. Tsirkin

On Tue, Dec 20, 2022 at 06:27:59PM +0800, Xuan Zhuo wrote: > On Tue, 20 Dec 2022 14:51:54 +0530, Naresh Kamboju <naresh.kamboju(a)linaro.org> wrote: > > The qemu-x86_64 and qemu-arm64 boot failed with Linux next-20221220 tag. > > It is always reproducible with gcc-11/ gcc-12 and clang tool chains. > > > > Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> > > > > <6>[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x000f0510] > > <5>[ 0.000000] Linux version 6.1.0-next-20221220 (tuxmake@tuxmake) > > (Debian clang version 16.0.0 > > (++20221218072110+9c1b82599dac-1~exp1~20221218072217.501), Debian LLD > > 16.0.0) #1 SMP PREEMPT @1671498176 > > <5>[ 0.000000] random: crng init done > > <6>[ 0.000000] Machine model: linux,dummy-virt > > .... > > <6>[ 3.571098] loop: module loaded > > <6>[ 3.573410] virtio_blk virtio0: 1/0/0 default/read/poll queues > > <5>[ 3.578816] virtio_blk virtio0: [vda] 2816420 512-byte logical > > blocks (1.44 GB/1.34 GiB) > > <4>[ 3.581234] ------------[ cut here ]------------ > > <2>[ 3.581595] kernel BUG at drivers/virtio/virtio.c:122! > > <0>[ 3.582906] Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP > > <4>[ 3.583672] Modules linked in: > > <4>[ 3.584905] CPU: 0 PID: 1 Comm: swapper/0 Not tainted > > 6.1.0-next-20221220 #1 > > <4>[ 3.585801] Hardware name: linux,dummy-virt (DT) > > <4>[ 3.586591] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT > > -SSBS BTYPE=--) > > <4>[ 3.587349] pc : virtio_check_driver_offered_feature+0x60/0x6c > > <4>[ 3.588613] lr : virtblk_probe+0x7cc/0x8f0 > > <4>[ 3.588915] sp : ffff80000802b840 > > <4>[ 3.589314] x29: ffff80000802b850 x28: 0000000000000000 x27: > > 0000000000000001 > > <4>[ 3.590509] x26: 0000000000000001 x25: 0000000000000200 x24: > > ffff0000c1699b00 > > <4>[ 3.590832] x23: 00000000000000fe x22: ffff0000c0313c30 x21: > > ffff0000c0313c00 > > <4>[ 3.591568] x20: ffff0000c02f4080 x19: 0000000000000000 x18: > > ffffffffffffffff > > <4>[ 3.592056] x17: 00000000ffffffea x16: 00000000fffffffe x15: > > 0000000000000004 > > <4>[ 3.592632] x14: 0000000000000fff x13: ffff800008028000 x12: > > ffff80000802c000 > > <4>[ 3.593157] x11: 000000000000000f x10: 000000000000000f x9 : > > ffffae66eee314d8 > > <4>[ 3.594048] x8 : 0000000000000000 x7 : 3631383837352e33 x6 : > > 202020205b3e353c > > <4>[ 3.594429] x5 : 0000000000000001 x4 : 0000000000000000 x3 : > > ffff80000802b780 > > <4>[ 3.594956] x2 : ffff80000802b6f8 x1 : 0000000000000011 x0 : > > ffff0000c02f4080 > > <4>[ 3.595811] Call trace: > > <4>[ 3.596120] virtio_check_driver_offered_feature+0x60/0x6c > > <4>[ 3.596632] virtio_dev_probe+0x274/0x320 > > <4>[ 3.597064] really_probe+0x178/0x418 > > <4>[ 3.597547] __driver_probe_device+0x120/0x188 > > <4>[ 3.597820] driver_probe_device+0x48/0x22c > > <4>[ 3.598189] __driver_attach+0xf8/0x250 > > <4>[ 3.598656] bus_for_each_dev+0x8c/0xd8 > > <4>[ 3.599151] driver_attach+0x30/0x3c > > <4>[ 3.599321] bus_add_driver+0x11c/0x22c > > <4>[ 3.599684] driver_register+0x84/0x120 > > <4>[ 3.600175] register_virtio_driver+0x38/0x48 > > <4>[ 3.600575] virtio_blk_init+0x6c/0xb4 > > <4>[ 3.600759] do_one_initcall+0xe0/0x2f8 > > <4>[ 3.601197] do_initcall_level+0xa8/0x150 > > <4>[ 3.601703] do_initcalls+0x60/0xa0 > > <4>[ 3.601892] do_basic_setup+0x28/0x34 > > <4>[ 3.602229] kernel_init_freeable+0x100/0x178 > > <4>[ 3.602706] kernel_init+0x2c/0x1b4 > > <4>[ 3.603162] ret_from_fork+0x10/0x20 > > <0>[ 3.604398] Code: 540000a0 91001129 f1000508 54ffff61 (d4210000) > > <4>[ 3.606108] ---[ end trace 0000000000000000 ]--- > > <6>[ 3.606714] note: swapper/0[1] exited with preempt_count 1 > > <0>[ 3.608155] Kernel panic - not syncing: Attempted to kill init! > > exitcode=0x0000000b > > <2>[ 3.609173] SMP: stopping secondary CPUs > > <0>[ 3.610506] Kernel Offset: 0x2e66e4800000 from 0xffff800008000000 > > <0>[ 3.610970] PHYS_OFFSET: 0x40000000 > > <0>[ 3.611428] CPU features: 0x00000,003a612f,cd22773f > > <0>[ 3.612277] Memory Limit: none > > <0>[ 3.613192] ---[ end Kernel panic - not syncing: Attempted to > > kill init! exitcode=0x0000000b ]--- > > > > Ref Links, > > https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221220/te… > > https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221220/te… > > https://storage.tuxsuite.com/public/linaro/lkft/builds/2J9l3qxSBmPWVa1S2uWn… > > > > > I think there is a bug, VIRTIO_BLK_F_ZONED depends the CONFIG_BLK_DEV_ZONE, but > checking its code in virtblk_probe does not depend on this config. > > This option in your config file is indeed not opened. > > > static int virtblk_probe(struct virtio_device *vdev){ > ..... > virtblk_update_capacity(vblk, false); > virtio_device_ready(vdev); > > if (virtio_has_feature(vdev, VIRTIO_BLK_F_ZONED)) { > err = virtblk_probe_zoned_device(vdev, vblk, q); > if (err) > goto out_cleanup_disk; > } > > dev_info(&vdev->dev, "blk config size: %zu\n", > sizeof(struct virtio_blk_config)); > > .... > > static unsigned int features[] = { > VIRTIO_BLK_F_SEG_MAX, VIRTIO_BLK_F_SIZE_MAX, VIRTIO_BLK_F_GEOMETRY, > VIRTIO_BLK_F_RO, VIRTIO_BLK_F_BLK_SIZE, > VIRTIO_BLK_F_FLUSH, VIRTIO_BLK_F_TOPOLOGY, VIRTIO_BLK_F_CONFIG_WCE, > VIRTIO_BLK_F_MQ, VIRTIO_BLK_F_DISCARD, VIRTIO_BLK_F_WRITE_ZEROES, > VIRTIO_BLK_F_SECURE_ERASE, VIRTIO_BLK_F_LIFETIME, > #ifdef CONFIG_BLK_DEV_ZONED > VIRTIO_BLK_F_ZONED, > #endif /* CONFIG_BLK_DEV_ZONED */ > } > > > Thanks. Oh you are right, I wanted to test it so of course I enabled it. Testing this fixup now: commit f9503d0fd839b59e0f48b00c20635437c41420ed Author: Michael S. Tsirkin <mst(a)redhat.com> Date: Tue Dec 20 05:53:41 2022 -0500 fixup! virtio-blk: add support for zoned block devices diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c index ff49052e26f7..d8cdaeb51d1c 100644 --- a/drivers/block/virtio_blk.c +++ b/drivers/block/virtio_blk.c @@ -775,6 +775,10 @@ static int virtblk_probe_zoned_device(struct virtio_device *vdev, return ret; } +static inline bool virtblk_has_zoned_feature(struct virtio_device *vdev) +{ + return virtio_has_feature(vdev, VIRTIO_BLK_F_ZONED); +} #else /* @@ -790,6 +794,11 @@ static inline int virtblk_probe_zoned_device(struct virtio_device *vdev, { return -EOPNOTSUPP; } + +static inline bool virtblk_has_zoned_feature(struct virtio_device *vdev) +{ + return false; +} #endif /* CONFIG_BLK_DEV_ZONED */ /* return id (s/n) string for *disk to *id_str @@ -1576,11 +1585,11 @@ static int virtblk_probe(struct virtio_device *vdev) else q->limits.discard_granularity = blk_size; } virtblk_update_capacity(vblk, false); virtio_device_ready(vdev); - if (virtio_has_feature(vdev, VIRTIO_BLK_F_ZONED)) { + if (virtblk_has_zoned_feature(vdev)) { err = virtblk_probe_zoned_device(vdev, vblk, q); if (err) goto out_cleanup_disk; -- MST

3 years, 5 months

Re: next: kernel BUG at drivers/virtio/virtio.c:122!

by Michael S. Tsirkin

On Tue, Dec 20, 2022 at 04:12:05PM +0530, Naresh Kamboju wrote: > On Tue, 20 Dec 2022 at 16:04, Xuan Zhuo <xuanzhuo(a)linux.alibaba.com> wrote: > > > > On Tue, 20 Dec 2022 14:51:54 +0530, Naresh Kamboju <naresh.kamboju(a)linaro.org> wrote: > > > The qemu-x86_64 and qemu-arm64 boot failed with Linux next-20221220 tag. > > > It is always reproducible with gcc-11/ gcc-12 and clang tool chains. > > > > > > Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> > > > > > > <6>[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x000f0510] > > > <5>[ 0.000000] Linux version 6.1.0-next-20221220 (tuxmake@tuxmake) > > > (Debian clang version 16.0.0 > > > (++20221218072110+9c1b82599dac-1~exp1~20221218072217.501), Debian LLD > > > 16.0.0) #1 SMP PREEMPT @1671498176 > > > <5>[ 0.000000] random: crng init done > > > <6>[ 0.000000] Machine model: linux,dummy-virt > > > .... > > > <6>[ 3.571098] loop: module loaded > > > <6>[ 3.573410] virtio_blk virtio0: 1/0/0 default/read/poll queues > > > <5>[ 3.578816] virtio_blk virtio0: [vda] 2816420 512-byte logical > > > blocks (1.44 GB/1.34 GiB) > > > <4>[ 3.581234] ------------[ cut here ]------------ > > > <2>[ 3.581595] kernel BUG at drivers/virtio/virtio.c:122! > > > <0>[ 3.582906] Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP > > > <4>[ 3.583672] Modules linked in: > > > <4>[ 3.584905] CPU: 0 PID: 1 Comm: swapper/0 Not tainted > > > 6.1.0-next-20221220 #1 > > > <4>[ 3.585801] Hardware name: linux,dummy-virt (DT) > > > <4>[ 3.586591] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT > > > -SSBS BTYPE=--) > > > <4>[ 3.587349] pc : virtio_check_driver_offered_feature+0x60/0x6c > > > <4>[ 3.588613] lr : virtblk_probe+0x7cc/0x8f0 > > > <4>[ 3.588915] sp : ffff80000802b840 > > > <4>[ 3.589314] x29: ffff80000802b850 x28: 0000000000000000 x27: > > > 0000000000000001 > > > <4>[ 3.590509] x26: 0000000000000001 x25: 0000000000000200 x24: > > > ffff0000c1699b00 > > > <4>[ 3.590832] x23: 00000000000000fe x22: ffff0000c0313c30 x21: > > > ffff0000c0313c00 > > > <4>[ 3.591568] x20: ffff0000c02f4080 x19: 0000000000000000 x18: > > > ffffffffffffffff > > > <4>[ 3.592056] x17: 00000000ffffffea x16: 00000000fffffffe x15: > > > 0000000000000004 > > > <4>[ 3.592632] x14: 0000000000000fff x13: ffff800008028000 x12: > > > ffff80000802c000 > > > <4>[ 3.593157] x11: 000000000000000f x10: 000000000000000f x9 : > > > ffffae66eee314d8 > > > <4>[ 3.594048] x8 : 0000000000000000 x7 : 3631383837352e33 x6 : > > > 202020205b3e353c > > > <4>[ 3.594429] x5 : 0000000000000001 x4 : 0000000000000000 x3 : > > > ffff80000802b780 > > > <4>[ 3.594956] x2 : ffff80000802b6f8 x1 : 0000000000000011 x0 : > > > ffff0000c02f4080 > > > <4>[ 3.595811] Call trace: > > > <4>[ 3.596120] virtio_check_driver_offered_feature+0x60/0x6c > > > <4>[ 3.596632] virtio_dev_probe+0x274/0x320 > > > <4>[ 3.597064] really_probe+0x178/0x418 > > > <4>[ 3.597547] __driver_probe_device+0x120/0x188 > > > <4>[ 3.597820] driver_probe_device+0x48/0x22c > > > <4>[ 3.598189] __driver_attach+0xf8/0x250 > > > <4>[ 3.598656] bus_for_each_dev+0x8c/0xd8 > > > <4>[ 3.599151] driver_attach+0x30/0x3c > > > <4>[ 3.599321] bus_add_driver+0x11c/0x22c > > > <4>[ 3.599684] driver_register+0x84/0x120 > > > <4>[ 3.600175] register_virtio_driver+0x38/0x48 > > > <4>[ 3.600575] virtio_blk_init+0x6c/0xb4 > > > <4>[ 3.600759] do_one_initcall+0xe0/0x2f8 > > > <4>[ 3.601197] do_initcall_level+0xa8/0x150 > > > <4>[ 3.601703] do_initcalls+0x60/0xa0 > > > <4>[ 3.601892] do_basic_setup+0x28/0x34 > > > <4>[ 3.602229] kernel_init_freeable+0x100/0x178 > > > <4>[ 3.602706] kernel_init+0x2c/0x1b4 > > > <4>[ 3.603162] ret_from_fork+0x10/0x20 > > > <0>[ 3.604398] Code: 540000a0 91001129 f1000508 54ffff61 (d4210000) > > > <4>[ 3.606108] ---[ end trace 0000000000000000 ]--- > > > <6>[ 3.606714] note: swapper/0[1] exited with preempt_count 1 > > > <0>[ 3.608155] Kernel panic - not syncing: Attempted to kill init! > > > exitcode=0x0000000b > > > <2>[ 3.609173] SMP: stopping secondary CPUs > > > <0>[ 3.610506] Kernel Offset: 0x2e66e4800000 from 0xffff800008000000 > > > <0>[ 3.610970] PHYS_OFFSET: 0x40000000 > > > <0>[ 3.611428] CPU features: 0x00000,003a612f,cd22773f > > > <0>[ 3.612277] Memory Limit: none > > > <0>[ 3.613192] ---[ end Kernel panic - not syncing: Attempted to > > > kill init! exitcode=0x0000000b ]--- > > > > > > Ref Links, > > > https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221220/te… > > > https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221220/te… > > > https://storage.tuxsuite.com/public/linaro/lkft/builds/2J9l3qxSBmPWVa1S2uWn… > > > > > > > > > I think there is a bug, VIRTIO_BLK_F_ZONED depends the CONFIG_BLK_DEV_ZONE, but > > checking its code in virtblk_probe does not depend on this config. > > I see this in my config, > # CONFIG_BLK_DEV_ZONED is not set > > > > > This option in your config file is indeed not opened. > > > > static int virtblk_probe(struct virtio_device *vdev){ > > ..... > > virtblk_update_capacity(vblk, false); > > virtio_device_ready(vdev); > > > > if (virtio_has_feature(vdev, VIRTIO_BLK_F_ZONED)) { > > err = virtblk_probe_zoned_device(vdev, vblk, q); > > if (err) > > goto out_cleanup_disk; > > } > > > > dev_info(&vdev->dev, "blk config size: %zu\n", > > sizeof(struct virtio_blk_config)); > > > > .... > > > > static unsigned int features[] = { > > VIRTIO_BLK_F_SEG_MAX, VIRTIO_BLK_F_SIZE_MAX, VIRTIO_BLK_F_GEOMETRY, > > VIRTIO_BLK_F_RO, VIRTIO_BLK_F_BLK_SIZE, > > VIRTIO_BLK_F_FLUSH, VIRTIO_BLK_F_TOPOLOGY, VIRTIO_BLK_F_CONFIG_WCE, > > VIRTIO_BLK_F_MQ, VIRTIO_BLK_F_DISCARD, VIRTIO_BLK_F_WRITE_ZEROES, > > VIRTIO_BLK_F_SECURE_ERASE, VIRTIO_BLK_F_LIFETIME, > > #ifdef CONFIG_BLK_DEV_ZONED > > VIRTIO_BLK_F_ZONED, > > #endif /* CONFIG_BLK_DEV_ZONED */ > > } > > I have attached config files to this email. > > > > > Thanks. > > > > > > > > > > -- > > > Linaro LKFT > > > https://lkft.linaro.org Thanks a lot! -- MST

3 years, 5 months

next: kernel BUG at drivers/virtio/virtio.c:122!

by Naresh Kamboju

The qemu-x86_64 and qemu-arm64 boot failed with Linux next-20221220 tag. It is always reproducible with gcc-11/ gcc-12 and clang tool chains. Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> <6>[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x000f0510] <5>[ 0.000000] Linux version 6.1.0-next-20221220 (tuxmake@tuxmake) (Debian clang version 16.0.0 (++20221218072110+9c1b82599dac-1~exp1~20221218072217.501), Debian LLD 16.0.0) #1 SMP PREEMPT @1671498176 <5>[ 0.000000] random: crng init done <6>[ 0.000000] Machine model: linux,dummy-virt .... <6>[ 3.571098] loop: module loaded <6>[ 3.573410] virtio_blk virtio0: 1/0/0 default/read/poll queues <5>[ 3.578816] virtio_blk virtio0: [vda] 2816420 512-byte logical blocks (1.44 GB/1.34 GiB) <4>[ 3.581234] ------------[ cut here ]------------ <2>[ 3.581595] kernel BUG at drivers/virtio/virtio.c:122! <0>[ 3.582906] Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP <4>[ 3.583672] Modules linked in: <4>[ 3.584905] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.1.0-next-20221220 #1 <4>[ 3.585801] Hardware name: linux,dummy-virt (DT) <4>[ 3.586591] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) <4>[ 3.587349] pc : virtio_check_driver_offered_feature+0x60/0x6c <4>[ 3.588613] lr : virtblk_probe+0x7cc/0x8f0 <4>[ 3.588915] sp : ffff80000802b840 <4>[ 3.589314] x29: ffff80000802b850 x28: 0000000000000000 x27: 0000000000000001 <4>[ 3.590509] x26: 0000000000000001 x25: 0000000000000200 x24: ffff0000c1699b00 <4>[ 3.590832] x23: 00000000000000fe x22: ffff0000c0313c30 x21: ffff0000c0313c00 <4>[ 3.591568] x20: ffff0000c02f4080 x19: 0000000000000000 x18: ffffffffffffffff <4>[ 3.592056] x17: 00000000ffffffea x16: 00000000fffffffe x15: 0000000000000004 <4>[ 3.592632] x14: 0000000000000fff x13: ffff800008028000 x12: ffff80000802c000 <4>[ 3.593157] x11: 000000000000000f x10: 000000000000000f x9 : ffffae66eee314d8 <4>[ 3.594048] x8 : 0000000000000000 x7 : 3631383837352e33 x6 : 202020205b3e353c <4>[ 3.594429] x5 : 0000000000000001 x4 : 0000000000000000 x3 : ffff80000802b780 <4>[ 3.594956] x2 : ffff80000802b6f8 x1 : 0000000000000011 x0 : ffff0000c02f4080 <4>[ 3.595811] Call trace: <4>[ 3.596120] virtio_check_driver_offered_feature+0x60/0x6c <4>[ 3.596632] virtio_dev_probe+0x274/0x320 <4>[ 3.597064] really_probe+0x178/0x418 <4>[ 3.597547] __driver_probe_device+0x120/0x188 <4>[ 3.597820] driver_probe_device+0x48/0x22c <4>[ 3.598189] __driver_attach+0xf8/0x250 <4>[ 3.598656] bus_for_each_dev+0x8c/0xd8 <4>[ 3.599151] driver_attach+0x30/0x3c <4>[ 3.599321] bus_add_driver+0x11c/0x22c <4>[ 3.599684] driver_register+0x84/0x120 <4>[ 3.600175] register_virtio_driver+0x38/0x48 <4>[ 3.600575] virtio_blk_init+0x6c/0xb4 <4>[ 3.600759] do_one_initcall+0xe0/0x2f8 <4>[ 3.601197] do_initcall_level+0xa8/0x150 <4>[ 3.601703] do_initcalls+0x60/0xa0 <4>[ 3.601892] do_basic_setup+0x28/0x34 <4>[ 3.602229] kernel_init_freeable+0x100/0x178 <4>[ 3.602706] kernel_init+0x2c/0x1b4 <4>[ 3.603162] ret_from_fork+0x10/0x20 <0>[ 3.604398] Code: 540000a0 91001129 f1000508 54ffff61 (d4210000) <4>[ 3.606108] ---[ end trace 0000000000000000 ]--- <6>[ 3.606714] note: swapper/0[1] exited with preempt_count 1 <0>[ 3.608155] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b <2>[ 3.609173] SMP: stopping secondary CPUs <0>[ 3.610506] Kernel Offset: 0x2e66e4800000 from 0xffff800008000000 <0>[ 3.610970] PHYS_OFFSET: 0x40000000 <0>[ 3.611428] CPU features: 0x00000,003a612f,cd22773f <0>[ 3.612277] Memory Limit: none <0>[ 3.613192] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]--- Ref Links, https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221220/te… https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221220/te… https://storage.tuxsuite.com/public/linaro/lkft/builds/2J9l3qxSBmPWVa1S2uWn… -- Linaro LKFT https://lkft.linaro.org

3 years, 5 months

Daily cts/vts report for lkft - 2022-Dec-20

by lava＠validation.linaro.org

Total jobs: 39 Total errors: 20 (51.28%) LAVA errors: 0 (0.00%) Test errors: 4 (10.26%) Job errors: 0 (0.00%) Infra errors: 16 (41.03%) Canceled jobs: 0 (0.00%) Device type: hi6220-hikey-r2 Total jobs: 1 Total errors: 1 (100.00%) Error type: Test Error count: 1 (100.00%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 585 seconds' Count: 1 (100.00%) IDs: hikey-6220-r2-14: 5979537 Device type: dragonboard-845c Total jobs: 38 Total errors: 19 (50.00%) Error type: Infrastructure Error count: 16 (42.11%) Error: Connection closed Count: 16 (42.11%) IDs: db845c-03: 5967040 5967045 5967050 5967057 5967058 5967074 5967083 5967092 5967107 db845c-04: 5963914 5966941 5967025 5967031 5967091 5978709 5978710 Error type: Test Error count: 3 (7.89%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 281 seconds' Count: 1 (2.63%) IDs: db845c-03: 5967069 Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 587 seconds' Count: 1 (2.63%) IDs: db845c-04: 5964670 Error: No match for error type 'Test', message 'tradefed - adb device lost[b6b742b9]' Count: 1 (2.63%) IDs: db845c-01: 5962752

3 years, 5 months

Linux-stable-rc/ queue_5.10

by Naresh Kamboju

The MIPS tinyconfig with clang nightly build failed, Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> Build warnings / errors, make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build LLVM=1 LLVM_IAS=0 ARCH=mips CROSS_COMPILE=mips-linux-gnu- HOSTCC=clang CC=clang tinyconfig /tmp/calibrate-9ea8cf.s: Assembler messages: /tmp/calibrate-9ea8cf.s:134: Error: .module is not permitted after generating code /tmp/calibrate-9ea8cf.s:168: Error: .module is not permitted after generating code /tmp/calibrate-9ea8cf.s:192: Error: .module is not permitted after generating code /tmp/calibrate-9ea8cf.s:216: Error: .module is not permitted after generating code clang: error: assembler command failed with exit code 1 (use -v to see invocation) make[2]: *** [/builds/linux/scripts/Makefile.build:286: init/calibrate.o] Error 1 Build link, https://storage.tuxsuite.com/public/linaro/lkft/builds/2J8KYpCyqe9C5esb4CrL… Steps to reproduce: ------------------ # To install tuxmake on your system globally: # sudo pip3 install -U tuxmake # # See https://docs.tuxmake.org/ for complete documentation. # Original tuxmake command with fragments listed below. # tuxmake --runtime podman --target-arch mips --toolchain clang-nightly --kconfig tinyconfig LLVM=1 LLVM_IAS=0 tuxmake --runtime podman --target-arch mips --toolchain clang-nightly --kconfig https://storage.tuxsuite.com/public/linaro/lkft/builds/2J8KYpCyqe9C5esb4CrL… LLVM=1 LLVM_IAS=0 -- Linaro LKFT https://lkft.linaro.org

3 years, 5 months

[REGRESSION] lkft ltp for 938dfa1

by lkft＠linaro.org

## Build * kernel: 6.0.13 * git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc * git branch: linux-6.0.y * git commit: 843cf4765c1b76102b7e24388adb478b2ec0c3fd * git describe: 938dfa1 * test details: https://qa-reports.linaro.org/lkft/ltp/build/938dfa1 ## Test Regressions (compared to a1ec817) * qemu_i386, log-parser-test - check-kernel-exception - check-kernel-warning ## Metric Regressions (compared to a1ec817) No metric regressions found. Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> ## Test Fixes (compared to a1ec817) * qemu_i386, log-parser-test - check-kernel-exception - check-kernel-warning ## Metric Fixes (compared to a1ec817) No metric fixes found. ## Test result summary total: 10131, pass: 8719, fail: 108, skip: 1304, xfail: 0 ## Build Summary ## Test suites summary * log-parser-boot * log-parser-test * ltp-cap_bounds * ltp-commands * ltp-containers * ltp-controllers * ltp-cpuhotplug * ltp-crypto * ltp-cve * ltp-dio * ltp-fcntl-locktests * ltp-filecaps * ltp-fs * ltp-fs_bind * ltp-fs_perms_simple * ltp-fsx * ltp-hugetlb * ltp-io * ltp-ipc * ltp-math * ltp-mm * ltp-nptl * ltp-pty * ltp-sched * ltp-securebits * ltp-syscalls * ltp-tracing -- Linaro LKFT https://lkft.linaro.org

3 years, 5 months

Daily cts/vts report for lkft - 2022-Dec-19

by lava＠validation.linaro.org

Total jobs: 55 Total errors: 37 (67.27%) LAVA errors: 0 (0.00%) Test errors: 1 (1.82%) Job errors: 13 (23.64%) Infra errors: 23 (41.82%) Canceled jobs: 0 (0.00%) Device type: hi6220-hikey-r2 Total jobs: 2 Total errors: 1 (50.00%) Error type: Test Error count: 1 (50.00%) Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 17987 seconds' Count: 1 (50.00%) IDs: hikey-6220-r2-12: 5966964 Device type: dragonboard-845c Total jobs: 53 Total errors: 36 (67.92%) Error type: Infrastructure Error count: 23 (43.40%) Error: Connection closed Count: 23 (43.40%) IDs: db845c-03: 5962711 5962712 5962713 5962714 5962715 5962716 5962718 5962725 5962728 5962729 5962731 5962735 5962736 5962737 5962738 5962742 5962744 5962747 5962748 5962749 5962750 db845c-05: 5962720 db845c-07: 5962705 Error type: Job Error count: 13 (24.53%) Error: No match for error type 'Job', message 'login-action timed out after 874 seconds' Count: 1 (1.89%) IDs: db845c-03: 5962740 Error: No match for error type 'Job', message 'login-action timed out after 873 seconds' Count: 2 (3.77%) IDs: db845c-03: 5962732 5962734 Error: wait for prompt timed out Count: 7 (13.21%) IDs: db845c-01: 5962724 db845c-03: 5962708 5962719 5962722 5962723 5962730 5962733 Error: No match for error type 'Job', message 'login-action timed out after 869 seconds' Count: 2 (3.77%) IDs: db845c-03: 5962717 5962727 Error: No match for error type 'Job', message 'login-action timed out after 870 seconds' Count: 1 (1.89%) IDs: db845c-03: 5962721

3 years, 5 months

[REGRESSION] lkft ltp for a1ec817

by lkft＠linaro.org

## Build * kernel: 6.0.13 * git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc * git branch: linux-6.0.y * git commit: 843cf4765c1b76102b7e24388adb478b2ec0c3fd * git describe: a1ec817 * test details: https://qa-reports.linaro.org/lkft/ltp/build/a1ec817 ## Test Regressions (compared to 9547e6a) * qemu_i386, log-parser-test - check-kernel-exception - check-kernel-warning * qemu_i386, ltp-syscalls - ustat01 - ustat02 - vfork01 ## Metric Regressions (compared to 9547e6a) No metric regressions found. Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> ## Test Fixes (compared to 9547e6a) * bcm2711-rpi-4-b, ltp-syscalls - inotify11 * qemu_arm64, log-parser-test - check-kernel-exception - check-kernel-warning * qemu_arm64, ltp-controllers - cpuacct_100_100 * qemu_i386, log-parser-test - check-kernel-exception - check-kernel-warning ## Metric Fixes (compared to 9547e6a) No metric fixes found. ## Test result summary total: 12149, pass: 10319, fail: 135, skip: 1695, xfail: 0 ## Build Summary ## Test suites summary * log-parser-boot * log-parser-test * ltp-cap_bounds * ltp-commands * ltp-containers * ltp-controllers * ltp-cpuhotplug * ltp-crypto * ltp-cve * ltp-dio * ltp-fcntl-locktests * ltp-filecaps * ltp-fs * ltp-fs_bind * ltp-fs_perms_simple * ltp-fsx * ltp-hugetlb * ltp-io * ltp-ipc * ltp-math * ltp-mm * ltp-nptl * ltp-pty * ltp-sched * ltp-securebits * ltp-syscalls * ltp-tracing -- Linaro LKFT https://lkft.linaro.org

3 years, 5 months

[REGRESSION] lkft ltp for 40a9f2d

by lkft＠linaro.org

## Build * kernel: 6.0.13 * git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc * git branch: linux-6.0.y * git commit: 843cf4765c1b76102b7e24388adb478b2ec0c3fd * git describe: 40a9f2d * test details: https://qa-reports.linaro.org/lkft/ltp/build/40a9f2d ## Test Regressions (compared to 9547e6a) * qemu_arm, ltp-syscalls - epoll_pwait01 - prot_hsymlinks * qemu_i386, log-parser-test - check-kernel-exception - check-kernel-warning ## Metric Regressions (compared to 9547e6a) No metric regressions found. Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org> ## Test Fixes (compared to 9547e6a) * bcm2711-rpi-4-b, ltp-syscalls - inotify11 * qemu_arm64, log-parser-test - check-kernel-exception - check-kernel-warning * qemu_i386, log-parser-test - check-kernel-exception - check-kernel-warning ## Metric Fixes (compared to 9547e6a) No metric fixes found. ## Test result summary total: 12148, pass: 10318, fail: 135, skip: 1695, xfail: 0 ## Build Summary ## Test suites summary * log-parser-boot * log-parser-test * ltp-cap_bounds * ltp-commands * ltp-containers * ltp-controllers * ltp-cpuhotplug * ltp-crypto * ltp-cve * ltp-dio * ltp-fcntl-locktests * ltp-filecaps * ltp-fs * ltp-fs_bind * ltp-fs_perms_simple * ltp-fsx * ltp-hugetlb * ltp-io * ltp-ipc * ltp-math * ltp-mm * ltp-nptl * ltp-pty * ltp-sched * ltp-securebits * ltp-syscalls * ltp-tracing -- Linaro LKFT https://lkft.linaro.org

3 years, 5 months

Daily cts/vts report for lkft - 2022-Dec-18

by lava＠validation.linaro.org

Total jobs: 39 Total errors: 9 (23.08%) LAVA errors: 0 (0.00%) Test errors: 1 (2.56%) Job errors: 2 (5.13%) Infra errors: 6 (15.38%) Canceled jobs: 0 (0.00%) Device type: dragonboard-845c Total jobs: 38 Total errors: 9 (23.68%) Error type: Job Error count: 2 (5.26%) Error: No match for error type 'Job', message 'login-action timed out after 868 seconds' Count: 1 (2.63%) IDs: db845c-03: 5966235 Error: wait for prompt timed out Count: 1 (2.63%) IDs: db845c-03: 5965997 Error type: Infrastructure Error count: 6 (15.79%) Error: Connection closed Count: 6 (15.79%) IDs: db845c-03: 5962649 5965990 5966025 5966206 db845c-04: 5962683 db845c-05: 5962647 Error type: Test Error count: 1 (2.63%) Error: No match for error type 'Test', message 'tradefed - adb device lost[b6b742b9]' Count: 1 (2.63%) IDs: db845c-01: 5966039 Device type: hi6220-hikey-r2 Total jobs: 1 Total errors: 0 (0.00%)

3 years, 5 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

Lkft-triage