From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 187231] kernel panic during hpsa MSI plus tg3 MSI
Date: Mon, 07 Nov 2016 16:16:05 +0000 [thread overview]
Message-ID: <bug-187231-11613-401cl4AVVt@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-187231-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=187231
--- Comment #3 from Don <don.brace@microsemi.com> ---
(In reply to Patrick Schaaf from comment #2)
> Thanks Don for the reaction!
>
> Right now, on the box that had that panic and the worst resetting/reset
> issues (see the other bug I linked), I'm back to 3.14.79, and want to stay
> there for another 24 to 36 hours, to see that this issue was not present
> with that kernel series.
>
> What would your patch help with? Specifically the panic potential in case a
> logical device reset is ongoing? Or should it affect / remedy the mysterious
> (to me) "resetting logical" events in the first place?
>
> I'm willing to test patches on that box starting Thursday, but I'd like to
> understand a bit better what we are dealing with here.
The specific issue that this patch addresses is that during a reset,
complete_scsi_command returns without having called scsi_done which causes the
OS to offline the disk (after two more occurrences). But this code path is not
often followed so the issue does not happen with all resets.
There are some other recent patches that should also be tested that have been
recently applied.
>From git format-patch:
0457-scsi-hpsa-Check-for-null-device-pointers.patch
* This checks for a NULL device that can happen if the OS
off-lines the disk because of the afore mentioned reset issue.
0460-scsi-hpsa-Check-for-null-devices-in-ioaccel-submissi.patch
0462-scsi-hpsa-correct-call-to-hpsa_do_reset.patch
* Fine tunes resets into LOGICAL/Physical resets.
A patch I still have pending on linux-scsi
0464-hpsa-add-generate-controller-NMI-on-lockup.patch
* This patch just adds more granularity on lock-up detection.
It would be nice to know why the reset is happening in the first place.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-11-07 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 13:53 [Bug 187231] New: kernel panic during hpsa MSI plus tg3 MSI bugzilla-daemon
2016-11-07 15:25 ` [Bug 187231] " bugzilla-daemon
2016-11-07 15:45 ` bugzilla-daemon
2016-11-07 16:16 ` bugzilla-daemon [this message]
2016-11-08 16:01 ` bugzilla-daemon
2016-11-11 9:54 ` bugzilla-daemon
2016-11-16 6:17 ` 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-187231-11613-401cl4AVVt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).