From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH 3.14-rt] sas-ata/isci: dont't disable interrupts in qc_issue handler
Date: Wed, 18 Feb 2015 10:33:34 -0500 [thread overview]
Message-ID: <54E4B0CE.1020508@windriver.com> (raw)
In-Reply-To: <20150218113803.GG28763@linutronix.de>
On 15-02-18 06:38 AM, Sebastian Andrzej Siewior wrote:
> * Paul Gortmaker | 2015-02-14 11:01:16 [-0500]:
>
>> On 3.14-rt we see the following trace on Canoe Pass for
>> SCSI_ISCI "Intel(R) C600 Series Chipset SAS Controller"
>> when the sas qc_issue handler is run:
>
> So I have finally something that is using isci I would have assumed that
> I would be affected by this. But somehow it does not pop up…
Funny you should mention that, as I too had the same thought, since
I also did not see it on my machine with the same hardware, but I did
see it on the machine I was loaned to diagnose the issue. I assumed
that the loaner machine had flaky media that was calling error handler
code that my machine would never run.
P.
--
>
> Applied.
>
> And we are down to
> | $ git grep -c 'local_irq_save\W' drivers/scsi/ | wc -l
> | 14
>
> I hope the others are just old things nobody is using…
>
> Sebastian
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-02-18 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 16:01 [PATCH 3.14-rt] sas-ata/isci: dont't disable interrupts in qc_issue handler Paul Gortmaker
2015-02-18 11:38 ` Sebastian Andrzej Siewior
2015-02-18 15:33 ` Paul Gortmaker [this message]
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=54E4B0CE.1020508@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@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.