On Thu, Oct 27, 2022 at 1:17 PM <Sagar.Biradar@xxxxxxxxxxxxx> wrote: > > Hi James and Konstantin, > > *Limiting the audience to avoid spamming* > > Sorry for delayed response as I was on vacation. > This one got missed somehow as someone else was looking into this and is no longer with the company. > > I will look into this, meanwhile I wanted to check if you (or someone else you know) had a chance to test this thoroughly with the latest kernel? > I will get back to you with some more questions or the confirmation in a day or two max. Did this ever get looked at? As this exact patch was merged into the vendor aacraid a while ago I'm not sure why it wouldn't be good to merge to mainline as well. Vendor aacraid release with this patch merged: https://download.adaptec.com/raid/aac/linux/aacraid-linux-src-1.2.1-60001.tgz > > > Thanks for your patience. > Sagar > > > -----Original Message----- > From: James Hilliard <james.hilliard1@xxxxxxxxx> > Sent: Thursday, October 27, 2022 1:40 AM > To: Martin K. Petersen <martin.petersen@xxxxxxxxxx> > Cc: Konstantin Khorenko <khorenko@xxxxxxxxxxxxx>; Christian Großegger <christian@xxxxxxxxxxxxxx>; linux-scsi@xxxxxxxxxxxxxxx; Adaptec OEM Raid Solutions <aacraid@xxxxxxxxxxxxx>; Sagar Biradar - C34249 <Sagar.Biradar@xxxxxxxxxxxxx>; Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>; Don Brace - C33706 <Don.Brace@xxxxxxxxxxxxx> > Subject: Re: [PATCH v3 0/1] aacraid: Host adapter Adaptec 6405 constantly resets under high io load > > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe > > On Wed, Oct 19, 2022 at 2:03 PM Konstantin Khorenko <khorenko@xxxxxxxxxxxxx> wrote: > > > > On 10.10.2022 14:31, James Hilliard wrote: > > > On Tue, Feb 22, 2022 at 10:41 PM Martin K. Petersen > > > <martin.petersen@xxxxxxxxxx> wrote: > > >> > > >> > > >> Christian, > > >> > > >>> The faulty patch (Commit: 395e5df79a9588abf) from 2017 should be > > >>> repaired with Konstantin Khorenko (1): > > >>> > > >>> scsi: aacraid: resurrect correct arc ctrl checks for Series-6 > > >> > > >> It would be great to get this patch resubmitted by Konstantin and > > >> acked by Microchip. > > Can we merge this as is since microchip does not appear to be maintaining this driver any more or responding? > > > > > > > Does the patch need to be rebased? > > > > James, i have just checked - the old patch (v3) applies cleanly onto latest master branch. > > > > > Based on this it looks like someone at microchip may have already reviewed: > > > v3 changes: > > > * introduced another wrapper to check for devices except for Series 6 > > > controllers upon request from Sagar Biradar (Microchip) > > > > Well, back in the year 2019 i've created a bug in RedHat bugzilla > > https://bugzilla.redhat.com/show_bug.cgi?id=1724077 > > (the bug is private, this is default for Redhat bugs) > > > > In this bug Sagar Biradar (with the email @microchip.com) suggested me > > to rework the patch - i've done that and sent the v3. > > > > And nothing happened after that, but in a ~year (2020-06-19) the bug > > was closed with the resolution NOTABUG and a comment that S6 users will find the patch useful. > > > > i suppose S6 is so old that RedHat just does not have customers using > > it and Microchip company itself is also not that interested in handling so old hardware issues. > > > > Sorry, i was unable to get a final ack from Microchip, i've written > > direct emails to the addresses which is found in the internet, tried > > to connect via linkedin, no luck. > > > > -- > > Konstantin Khorenko
