All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 207855] New: arcconf host reset causes kernel panic -> driver crash?
Date: Fri, 22 May 2020 08:49:36 +0000	[thread overview]
Message-ID: <bug-207855-11613@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 207855
           Summary: arcconf host reset causes kernel panic -> driver
                    crash?
           Product: IO/Storage
           Version: 2.5
    Kernel Version: 5.6.13
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: SCSI
          Assignee: linux-scsi@vger.kernel.org
          Reporter: janpieter.sollie@edpnet.be
        Regression: No

Created attachment 289227
  --> https://bugzilla.kernel.org/attachment.cgi?id=289227&action=edit
last dmesg captured

When performing a arcconf operation (assign hot-spare) on a adaptec 72405 SAS
controller, the program crashes with the error "segmentation fault", but
apparently, the driver is not too happy with it either: it becomes
unresponsive, and makes it impossible to access scsi devices on the SAS
controller.
Additional tricks to perform a PCI level reset ultimately lead to a kernel
panic:
linuxserver# echo 1 > /sys/bus/pci/devices/0000\:04\:00.0/reset
(wait a minute)
linuxserver# echo 1 > /sys/bus/pci/rescan
(wait a minute)
linuxserver# umount /data/* (where all SAS devices are mounted)
(hangs indefinitely) 
linuxserver# echo auto > /sys/bus/pci/devices/0000\:04\:00.0/power/control
linuxserver# echo "0000:04:00.0" > /sys/bus/pci/drivers/aacraid/unbind
--PANIC--

I haven't been able to C/P the panic output yet, working on a kexec kernel or
crash dump.
The root directory is NOT one of the SAS devices, it is on a generic SATA
controller

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

             reply	other threads:[~2020-05-22  8:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22  8:49 bugzilla-daemon [this message]
2020-05-22  9:19 ` [Bug 207855] arcconf host reset causes kernel panic -> driver crash? bugzilla-daemon
2020-05-22  9:40 ` bugzilla-daemon
2020-05-23 16:29 ` bugzilla-daemon
2020-05-23 17:53 ` bugzilla-daemon
2020-05-23 18:38 ` bugzilla-daemon
2020-05-23 19:09 ` bugzilla-daemon
2020-06-06  9:01 ` bugzilla-daemon
2020-07-13 11:46 ` bugzilla-daemon
2020-07-13 11:47 ` bugzilla-daemon
2020-07-13 19:10 ` bugzilla-daemon
2020-07-15  8:45 ` bugzilla-daemon
2020-07-15  8:50 ` bugzilla-daemon
2020-07-19  6:36 ` bugzilla-daemon
2020-11-07 17:11 ` 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-207855-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.