Few tests - incomplete - pstore logs, Kernel panic - not syncing: EXT4-fs (device sda2): panic forced after error, _raw_spin_lock_nested
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11976/shard-iclb4/pstore24-1660052211_Panic_1.txt
<6>[ 615.742232] sd 2:0:0:0: [sda] tag#25 CDB: opcode=0x2a 2a 00 17 f0 08 a8 00 00 08 00
<3>[ 615.742243] Buffer I/O error on dev sda2, logical block 50069525, lost async page write
<2>[ 615.742257] EXT4-fs error (device sda2): ext4_journal_check_start:83: comm igt_runner: Detected aborted journal
<4>[ 615.742316] EXT4-fs warning (device sda2): ext4_end_bio:347: I/O error 10 writing to inode 12714000 starting block 51092746)
<3>[ 615.742329] Buffer I/O error on device sda2, logical block 50961418
<2>[ 615.742352] EXT4-fs error (device sda2) in ext4_reserve_inode_write:5756: Journal has aborted
<4>[ 615.742366] EXT4-fs warning (device sda2): ext4_end_bio:347: I/O error 10 writing to inode 12714000 starting block 51092749)
<3>[ 615.742385] Buffer I/O error on device sda2, logical block 50961421
<6>[ 615.742482] ata3: EH complete
<2>[ 615.742623] EXT4-fs error (device sda2) in ext4_writepages:2829: Journal has aborted
<6>[ 615.744588] ata3.00: detaching (SCSI 2:0:0:0)
<3>[ 615.745139] EXT4-fs (sda2): I/O error while writing superblock
<0>[ 615.745161] Kernel panic - not syncing: EXT4-fs (device sda2): panic forced after error
<4>[ 615.745302] ------------[ cut here ]------------
<4>[ 615.745339]
<4>[ 615.745341] ======================================================
<4>[ 615.745342] WARNING: possible circular locking dependency detected
<4>[ 615.745343] 5.19.0-CI_DRM_11976-g33740045ce83+ #1 Not tainted
<4>[ 615.745345] ------------------------------------------------------
<4>[ 615.745346] kworker/u16:3/284 is trying to acquire lock:
<4>[ 615.745348] ffffffff82734dd8 ((console_sem).lock){-.-.}-{2:2}, at: down_trylock+0xa/0x30
<4>[ 615.745380]
<4>[ 615.745380] but task is already holding lock:
<4>[ 615.745380] ffff88849fbbb658 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x1b/0x30
<4>[ 615.745389]
<4>[ 615.745389] which lock already depends on the new lock.
<4>[ 615.745389]
<4>[ 615.745390]
<4>[ 615.745390] the existing dependency chain (in reverse order) is:
<4>[ 615.745390]
<4>[ 615.745390] -> #2 (&rq->__lock){-.-.}-{2:2}:
<4>[ 615.745394] _raw_spin_lock_nested+0x2d/0x40
<4>[ 615.745399] raw_spin_rq_lock_nested+0x1b/0x30
<4>[ 615.745403] task_fork_fair+0x43/0x170
<4>[ 615.745406] sched_cgroup_fork+0xec/0x130
<4>[ 615.745409] copy_process+0x1293/0x1ca0
<4>[ 615.745413] kernel_clone+0x98/0x730
<4>[ 615.745416] user_mode_thread+0x56/0x80
<4>[ 615.745419] rest_init+0x1d/0x190
<4>[ 615.745423] arch_call_rest_init+0x5/0xa
<4>[ 615.745429] start_kernel+0x684/0x6af
<4>[ 615.745433] secondary_startup_64_no_verify+0xce/0xdb
<4>[ 615.745437]
<4>[ 615.745437] -> #1 (&p->pi_lock){-.-.}-{2:2}:
<4>[ 615.745440] _raw_spin_lock_irqsave+0x33/0x50
<4>[ 615.745443] try_to_wake_up+0x6b/0x830
<4>[ 615.745445] up+0x3b/0x50
<4>[ 615.745470] __up_console_sem+0x5c/0x70
<4>[ 615.745473] console_unlock+0x1bc/0x1d0
<4>[ 615.745475] vprintk_emit+0x251/0x380
<4>[ 615.745476] devkmsg_emit.constprop.33+0x52/0x6d
<4>[ 615.745478] devkmsg_write.cold.45+0x1c/0x46
<4>[ 615.745479] do_iter_readv_writev+0x130/0x190
<4>[ 615.745480] do_iter_write+0x6c/0x1a0
<4>[ 615.745482] vfs_writev+0x97/0x290
<4>[ 615.745483] do_writev+0x63/0x110
<4>[ 615.745484] do_syscall_64+0x37/0x90
<4>[ 615.745485] entry_SYSCALL_64_after_hwframe+0x63/0xcd
<4>[ 615.745487]