All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 210203] New: linux boot sometimes hang around scsi_try_target_reset for a system with SSD/SATA 1.92T *10
Date: Sun, 15 Nov 2020 06:42:06 +0000	[thread overview]
Message-ID: <bug-210203-11613@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=210203

            Bug ID: 210203
           Summary: linux boot sometimes hang around scsi_try_target_reset
                    for a system with SSD/SATA 1.92T *10
           Product: IO/Storage
           Version: 2.5
    Kernel Version: 5.4.76 and other 5.4.x
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: SCSI
          Assignee: linux-scsi@vger.kernel.org
          Reporter: wangyugui@e16-tech.com
        Regression: No

Created attachment 293673
  --> https://bugzilla.kernel.org/attachment.cgi?id=293673&action=edit
sysrq-l-t-1.log

linux boot sometimes hang around scsi_try_target_reset for a system with
SSD/SATA 1.92T *10

console output:
        A start job is running for dev-disk-by\x2dlabel-OS_T604.device
                *** always waiting here

Failed to login, so only gathered SysRq info(saved in sysrq-l-t-1.log,
sysrq-l-t-2.log).
- sysrq l command
- sysrq t command

From SysRq info, it seem a problem around scsi_try_target_reset();

[  744.388123] scsi_eh_9       S    0   604      2 0x80004000
[  744.388124] Call Trace:
[  744.388125]  __schedule+0x285/0x6e0
[  744.388126]  ? scsi_try_target_reset+0x90/0x90
[  744.388127]  schedule+0x2f/0xa0
[  744.388128]  scsi_error_handler+0x1c4/0x500
[  744.388129]  ? scsi_eh_get_sense+0x220/0x220
[  744.388130]  kthread+0x112/0x130
[  744.388131]  ? kthread_park+0x80/0x80
[  744.388132]  ret_from_fork+0x1f/0x40


Frequency: about 10%
   only happened in a server with btrfs RAID0 & 10 SSD.
   yet not happened in another two server with the same kernel

OS: centos 7.8/7.9
kernel version:
        5.4.76, 5.4.74, 5.4.73, and others 5.4.x

# lsscsi
[14:0:0:0]   disk    ATA      MK1920GFDKU      HPG0  /dev/sda
[14:0:1:0]   disk    ATA      MK1920GFDKU      HPG0  /dev/sdb
[14:0:2:0]   disk    ATA      MK1920GFDKU      HPG0  /dev/sdc
[14:0:3:0]   disk    ATA      MK1920GFDKU      HPG0  /dev/sdd
[14:0:4:0]   disk    ATA      MK1920GFDKU      HPG0  /dev/sde
[14:0:6:0]   disk    ATA      SAMSUNG MZ7KM1T9 003Q  /dev/sdf
[14:0:7:0]   disk    ATA      SAMSUNG MZ7KM1T9 003Q  /dev/sdg
[14:0:8:0]   disk    ATA      SAMSUNG MZ7KM1T9 003Q  /dev/sdh
[14:0:9:0]   disk    ATA      SAMSUNG MZ7KM1T9 003Q  /dev/sdi
[14:0:10:0]  disk    ATA      SAMSUNG MZ7KM1T9 003Q  /dev/sdj

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2020-11-15  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-15  6:42 bugzilla-daemon [this message]
2020-11-15  6:43 ` [Bug 210203] linux boot sometimes hang around scsi_try_target_reset for a system with SSD/SATA 1.92T *10 bugzilla-daemon
2020-11-15  8:22 ` bugzilla-daemon
2020-11-17 14:58 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-210203-11613@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.