From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andrey Melnikov <temnota.am@gmail.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
arekm@maven.pl, linux-scsi@vger.kernel.org,
Raghava Aditya Renukunta <RaghavaAditya.Renukunta@microsemi.com>
Subject: Re: aacraid: kernel: AAC: Host adapter dead -1 (bisected)
Date: Fri, 10 Feb 2017 11:47:07 +0100 [thread overview]
Message-ID: <20170210104707.GA19359@kroah.com> (raw)
In-Reply-To: <CA+PODjqqvA91Eo1OPr35t9AXmK=SzteCiKjXsb+9xGcB2DyhGA@mail.gmail.com>
On Fri, Feb 10, 2017 at 01:45:06PM +0300, Andrey Melnikov wrote:
> Cc: linux-scsi@vger.kernel.org
>
> 2017-02-10 13:24 GMT+03:00 Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
> > On Fri, Feb 10, 2017 at 02:25:26AM +0300, Andrey Jr. Melnikov wrote:
> >> In article <201701151205.37563.a.miskiewicz@gmail.com> you wrote:
> >> > Newsgroups: gmane.linux.kernel
> >>
> >>
> >> > Hi.
> >>
> >> > There is a bug with handling of adaptec raid cards (in my case it is Adaptec
> >> > 3405) where kernel logs hundreds of "AAC: Host adapter dead -1" messages.
> >>
> >> > Bug was reported previously on lkml but there was no progres in solving it.
> >>
> >> > There is also bugzilla entry:
> >> > https://bugzilla.kernel.org/show_bug.cgi?id=151661
> >>
> >> > I've bisected that to commit bellow and indeed, reverting it from kernel 4.9.3
> >> > makes messages go away.
> >>
> >>
> >> Don't try to switch Adaptec 3405/3805 RAID cards to MSI-X interrupt mode.
> >> Fix https://bugzilla.kernel.org/show_bug.cgi?id=151661
> >>
> >> Signed-off-by: Andrey Jr. Melnikov <temnota.am@gmail.com>
> >>
> >> ---
> >>
> >> diff --git a/drivers/scsi/aacraid/aacraid.h b/drivers/scsi/aacraid/aacraid.h
> >> index 969c312de1be..2ad8403dea40 100644
> >> --- a/drivers/scsi/aacraid/aacraid.h
> >> +++ b/drivers/scsi/aacraid/aacraid.h
> >
> > <snip>
> >
> > Why are you sending this to me and not the scsi developers who can
> > actually do something with this patch?
>
> Bug in bugzilla open half year ago, microsemi maintainer slowly read
> his fine docs about his hardware, broken driver fills our log with
> useless messages every 10 seconds.
> So, make decision - apply this patch to stable 4.9.x/4.4.x tree or
> revert commit 78cbccd3bd683c295a44af8050797dc4a41376ff from it.
I don't understand, that's not how the stable kernels work, please read
Documentation/stable_kernel_rules.txt for how the process works. Please
get a patch accepted into Linus's tree and then we will be glad to apply
it to the stable kernel trees.
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-10 10:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 23:25 aacraid: kernel: AAC: Host adapter dead -1 (bisected) Andrey Jr. Melnikov
2017-02-10 10:24 ` Greg Kroah-Hartman
2017-02-10 10:45 ` Andrey Melnikov
2017-02-10 10:47 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-15 11:05 Arkadiusz Miskiewicz
[not found] ` <423FD6710FB8FB4F8728F93591889F9A4143D2BB@avsrvexchmbx2.microsemi.net>
2017-01-17 18:31 ` Arkadiusz Miskiewicz
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=20170210104707.GA19359@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=RaghavaAditya.Renukunta@microsemi.com \
--cc=arekm@maven.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=temnota.am@gmail.com \
/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