Re: ❌ FAIL: Test report for kernel 5.17.2 (stable-queue, eabfed45)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Apr 13, 2022 at 2:51 PM Veronika Kabatova <vkabatov@xxxxxxxxxx> wrote:
>
> On Wed, Apr 13, 2022 at 8:24 AM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> >
> > On Wed, Apr 13, 2022 at 06:03:14AM -0000, CKI Project wrote:
> > >
> > >
> > > Check out this report and any autotriaged failures in our web dashboard:
> > >     https://datawarehouse.cki-project.org/kcidb/checkouts/38921
> > >
> > > Hello,
> > >
> > > We ran automated tests on a recent commit from this kernel tree:
> > >
> > >        Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > >             Commit: eabfed45bc7c - io_uring: drop the old style inflight file tracking
> >
> > It's alive!
> >
> > > The results of these automated tests are provided below.
> > >
> > >     Overall result: FAILED (see details below)
> > >              Merge: OK
> > >            Compile: OK
> > >              Tests: FAILED
> > >     Targeted tests: NO
> >
> > But things are failing.
> >
> > Is this the CKI tool's issue, or is it the patches in the stable queue's
> > issue?
> >
> > Given that CKI has been dead for so long, I'll guess it's a CKI issue
> > unless you all say otherwise.
> >
>
> Hi,
>
> yes, we finally got the builds fixed and are able to run the testing,
> and immediately hit the following Fedora bug:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2074083
>
> We're looking into what exactly went wrong, the initial suspect is
> that the bug caused aborted test runs which confused the
> reporting system. Sorry about that, and thank you for reaching
> out about the problem!
>
> The listed failures are actual failures (both test and kernel bugs),
> but not specific to the stable tree. They were already reported to
> the relevant places. If you wish, you can look into the details in the
> provided DataWarehouse link.

Actually, we hit a panic that we don't know if it has been reported
yet. More logs at [1].

[  346.728135] CPU: 12 PID: 158 Comm: kworker/12:1H Tainted: G
 I       5.17.2 #1
[  346.770889] Hardware name: HP ProLiant SL390s G7/, BIOS P69 07/02/2013
[  346.805535] Workqueue: kblockd blk_mq_run_work_fn
[  346.827834] RIP: 0010:__bfq_deactivate_entity+0x168/0x240
[  346.855601] Code: 48 2b 41 28 48 85 c0 7e 05 49 89 5c 24 18 49 8b
44 24 08 4d 8d 74 24 08 48 85 c0 0f 84 d3 00 00 00 48 8b 7b 28 eb 03
48 89 c8 <48> 8b 48 28 48 8d 70 10 48 8d 50 08 48 29 f9 48 85 c9 48 0f
4f d6
[  346.947892] RSP: 0018:ffffac0943f6bbe0 EFLAGS: 00010086
[  346.973661] RAX: 9fa41f2000000000 RBX: ffff9ae8c9164748 RCX: 9fa41f2000000000
[  347.009384] RDX: ffff9aeaed07c0a8 RSI: ffff9aeaed07c0a8 RDI: 0000000ae2080ce1
[  347.044680] RBP: ffff9ae8c91646c0 R08: ffff9aeadd031960 R09: 0000004f9bf8c41b
[  347.080125] R10: 0000000000000001 R11: 0000000000000000 R12: ffff9aeadd031960
[  347.116032] R13: 0000000000000001 R14: ffff9aeadd031968 R15: ffff9ae8cb750748
[  347.150977] FS:  0000000000000000(0000) GS:ffff9aeacbb80000(0000)
knlGS:0000000000000000
[  347.198911] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  347.228754] CR2: 00007fb1e2c6ae14 CR3: 0000000340810005 CR4: 00000000000206e0
[  347.268138] Call Trace:
[  347.281292]  <TASK>
[  347.292058]  bfq_deactivate_entity+0x50/0xc0
[  347.313894]  bfq_del_bfqq_busy+0x91/0x190
[  347.335376]  bfq_remove_request+0x124/0x340
[  347.357453]  ? bfq_may_expire_for_budg_timeout+0xa5/0x1c0
[  347.385031]  ? _raw_spin_unlock_irqrestore+0x25/0x40
[  347.411908]  ? bfq_bfqq_served+0x132/0x1a0
[  347.433312]  bfq_dispatch_request+0x44d/0x12e0
[  347.454390]  ? sbitmap_get+0x90/0x1a0
[  347.472494]  blk_mq_do_dispatch_sched+0x109/0x370
[  347.496896]  ? finish_task_switch.isra.0+0xc1/0x2f0
[  347.520044]  ? __switch_to+0x77/0x430
[  347.537777]  __blk_mq_sched_dispatch_requests+0xd8/0x120
[  347.567004]  blk_mq_sched_dispatch_requests+0x30/0x60
[  347.592476]  __blk_mq_run_hw_queue+0x34/0x90
[  347.614232]  process_one_work+0x1c7/0x380
[  347.635369]  worker_thread+0x4d/0x380
[  347.652939]  ? _raw_spin_lock_irqsave+0x25/0x50
[  347.674477]  ? process_one_work+0x380/0x380
[  347.697082]  kthread+0xe9/0x110
[  347.712042]  ? kthread_complete_and_exit+0x20/0x20
[  347.735250]  ret_from_fork+0x22/0x30
[  347.753503]  </TASK>


[1] https://datawarehouse.cki-project.org/kcidb/tests/3193432

Thanks,
Bruno

> We're working on transforming the email reports to include the
> known issue detection that is currently provided in the dashboard,
> it should be in place in the (hopefully) near future. That should
> also stabilize the emails.
>
> Veronika
>
> > thanks,
> >
> > greg k-h
> >
>




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux