Received-SPF: pass (google.com: domain of linux-kernel+bounces-70197-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Message-ID: <f8a92dd7-8509-428d-8982-4ba94063081c@infradead.org>
Date: Sat, 17 Feb 2024 20:34:45 -0800
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Linux FS6712X-EB92 5.13.x - page allocation failure followed by a
 controller reset and the drive drops out of the array
Content-Language: en-US
To: Justin Piszcz <jpiszcz@lucidpixels.com>,
 LKML <linux-kernel@vger.kernel.org>
References: <CAO9zADyveGGBNKsD-JFoOeGZ3om3wMhkqvPc2mvxp-yBzk5mrg@mail.gmail.com>
From: Randy Dunlap <rdunlap@infradead.org>
In-Reply-To: <CAO9zADyveGGBNKsD-JFoOeGZ3om3wMhkqvPc2mvxp-yBzk5mrg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi Justin,

On 2/15/24 15:46, Justin Piszcz wrote:
> Hello,
> 
> I am using an Asus FlashStor FS6712X-EB92, and was curious why this
> issue keeps happening?  Is this a known issue in 5.13.x?  The last
> time this happened, I had removed the drive, ran a bunch of
> diagnostics on it and used it in another system and it was okay, no
> errors were found.  This is the second instance where there is a page
> allocation failure and a drive drops out of the array.
> 

I can't answer your question. I suggest that you ask it on the
linux-raid@vger.kernel.org  mailing list.

Also, I have one question:

in this log fragment:

[1698614.263935] SLUB: Unable to allocate memory on node -1,
gfp=0x800(GFP_NOWAIT)
[1698614.271680]   cache: skbuff_head_cache, object size: 224, buffer
size: 256, default order: 0, min order: 0
[1698614.281979]   node 0: slabs: 32, objs: 512, free: 64
[1933116.236646] nvme nvme9: I/O 119 QID 2 timeout, aborting
[1933116.242365] nvme nvme9: I/O 120 QID 2 timeout, aborting
[1933141.324640] nvme nvme9: I/O 1 QID 0 timeout, reset controller
[1933146.444701] nvme nvme9: I/O 119 QID 2 timeout, reset controller
[1933215.826997] nvme nvme9: Device not ready; aborting reset, CSTS=0x1

there are roughly 4 days between the 1698614 log entry and the
1933116 log entry. Is that (logging) accurate? Did it miss anything?
It just seems odd to me.


thanks.
-- 
#Randy