[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8cc36c16-4aa0-9c47-ab2f-c75c1e22772f@citrix.com>
Date: Tue, 14 Mar 2023 11:41:08 +0000
From: Andrew Cooper <Andrew.Cooper3@...rix.com>
To: Juergen Gross <jgross@...e.com>,
Joost Roeleveld <joost@...arean.org>,
Christoph Hellwig <hch@...radead.org>
Cc: jejb@...ux.ibm.com, Sreekanth Reddy <sreekanth.reddy@...adcom.com>,
Bart Van Assche <bvanassche@....org>,
Salvatore Bonaccorso <carnil@...ian.org>,
sathya.prakash@...adcom.com, suganath-prabu.subramani@...adcom.com,
"Martin K. Petersen" <martin.petersen@...cle.com>,
MPT-FusionLinux.pdl@...adcom.com, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org,
adi@...egisch.at
Subject: Re: Report in downstream Debian: mpt3sas broken with xen dom0 with
update to 5.10.149 in 5.10.y.
On 14/03/2023 11:23 am, Juergen Gross wrote:
> On 14.03.23 12:17, Joost Roeleveld wrote:
>>> On Mon, Oct 24, 2022 at 05:28:05PM +0000, Andrew Cooper wrote:
>>>> I don't know exactly how this translates to Linux internals, but most
>>>> devices are fine and it's routinely the mpt2/3sas drivers which
>>>> encounter problems. It would be lovely if we could get to the
>>>> bottom of
>>>> this for once and for all.
>>>
>>> So to summarize my two mails: I think te use of dma_get_required_mask
>>> in mpt3sas is wrong, and the dma_get_required_mask return value from
>>> xen-swiotlb is also wrong. Fixing either one should fix this problem,
>>> and I think we should fix both.
>>
>> Hi all,
>>
>> Is there anything that can be done to get this fixed in xen and the
>> kernel somehow?
>> I keep having to manually patch the mpt3sas driver to prevent it from
>> being able to switch to 32bit mode each time I upgrade the kernel.
>
> Just use 5.10.173.
Its still broken even in 6.1
We've just stumbled over this yet again in XenServer.
~Andrew
Powered by blists - more mailing lists