[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKgT0UcWHgeRXuMDsOCXacwv6OL9T8FBCbqCYR1wu1iQkCmhmQ@mail.gmail.com>
Date: Wed, 3 Feb 2016 07:27:20 -0800
From: Alexander Duyck <alexander.duyck@...il.com>
To: "Kirill A. Shutemov" <kirill@...temov.name>
Cc: "Martin K. Petersen" <martin.petersen@...cle.com>,
Alexander Duyck <aduyck@...antis.com>, jbottomley@...n.com,
Hannes Reinecke <hare@...e.de>, linux-scsi@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Shane M. Seymour" <shane.seymour@....com>, jthumshirn@...e.de
Subject: Re: [PATCH 0/2] scsi: Fix endless loop of ATA hard resets due to VPD reads
On Tue, Feb 2, 2016 at 10:48 PM, Kirill A. Shutemov
<kirill@...temov.name> wrote:
> On Tue, Feb 02, 2016 at 09:45:48PM -0500, Martin K. Petersen wrote:
>> >>>>> "Kirill" == Kirill A Shutemov <kirill@...temov.name> writes:
>>
>> Kirill> I have the same problem.
>>
>> Kirill> Shouldn't we put quirk for that?
>>
>> I was hoping that Hannes' patch would do the trick so we could avoid
>> blacklisting:
>>
>> https://patchwork.kernel.org/patch/8079011/
>
> It didn't help me.
My patch didn't resolve the Marvell issue, it just resolved other
cases that could also lead to the same problem.
I added a line to my kernel parameters to blacklist the Marvell
console. I wasn't sure if blacklisting would have been acceptable.
That is why I called out that I still had to add that line to my
kernel in the cover letter for my patch set.
- Alex
Powered by blists - more mailing lists