From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 95101] scsi/mpt2sas: setpci reset results in kernel oops
Date: Thu, 19 Mar 2015 21:46:04 +0000 [thread overview]
Message-ID: <bug-95101-11613-GkCRa2fRHA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-95101-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=95101
Joe Lawrence <joe.lawrence@stratus.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |joe.lawrence@stratus.com
--- Comment #1 from Joe Lawrence <joe.lawrence@stratus.com> ---
>From the /var/log/messages attachment:
Mar 16 01:13:10 RHEL63 kernel: mpt2sas1: _base_fault_reset_work: Running
mpt2sas_dead_ioc thread success !!!!
...
Mar 16 01:13:20 RHEL63 kernel: mpt2sas1: _scsih_ir_shutdown: timeout
Mar 16 01:13:20 RHEL63 kernel: mpt2sas1: removing handle(0x0024),
wwid(0x0c4e8a1c03a9b742)
indicates that _scsih_remove was called when the driver's watchdog detected
that the device was misbehaving. Driver device removal invokes:
mpt2sas_base_detach
mpt2sas_base_free_resources
iounmap(ioc->chip)
setting the stage for the crash:
Mar 16 01:13:37 RHEL63 kernel: BUG: unable to handle kernel paging request at
ffffc900171e0000
Mar 16 01:13:37 RHEL63 kernel: IP: [<ffffffffa00502e0>]
mpt2sas_base_get_iocstate+0x10/0x30 [mpt2sas]
...
Mar 16 01:13:37 RHEL63 kernel: RAX: ffffc900171e0000 RBX: ffff88105a0aa788 RCX:
0000000000004fdc
where mpt2sas_base_get_iocstate was probably calling
readl(&ioc->chip->Doorbell)
So it would seem that the mpt2sas ioctl code (step 5, I think) isn't
synchronized against device removal.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-03-19 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-95101-11613@https.bugzilla.kernel.org/>
2015-03-19 17:33 ` [Bug 95101] scsi/mpt2sas: setpci reset results in kernel oops bugzilla-daemon
2015-03-19 21:46 ` bugzilla-daemon [this message]
2015-04-02 5: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-95101-11613-GkCRa2fRHA@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.