On 3/12/19 8:19 PM, Juergen Gross wrote:
> On 12/03/2019 17:41, Hans van Kranenburg wrote:
>> On 3/12/19 5:04 PM, Juergen Gross wrote:
>>> On 11/03/2019 20:50, Hans van Kranenburg wrote:
On 3/11/19 7:34 AM, Juergen Gross wrote:
>
> I'm not sure. Patch 3 of this series is basically
On 12/03/2019 17:41, Hans van Kranenburg wrote:
> On 3/12/19 5:04 PM, Juergen Gross wrote:
>> On 11/03/2019 20:50, Hans van Kranenburg wrote:
>>> On 3/11/19 7:34 AM, Juergen Gross wrote:
I'm not sure. Patch 3 of this series is basically already there (see
commit
On 3/12/19 5:04 PM, Juergen Gross wrote:
> On 11/03/2019 20:50, Hans van Kranenburg wrote:
>> On 3/11/19 7:34 AM, Juergen Gross wrote:
>>>
>>> I'm not sure. Patch 3 of this series is basically already there (see
>>> commit c6d4381220a0087ce19dbf6984d92c451bd6b364). So maybe all we need
>>> is
On 11/03/2019 20:50, Hans van Kranenburg wrote:
> On 3/11/19 7:34 AM, Juergen Gross wrote:
>>
>> I'm not sure. Patch 3 of this series is basically already there (see
>> commit c6d4381220a0087ce19dbf6984d92c451bd6b364). So maybe all we need
>> is patch 4, which should really be easy to do?
>>
>>
On 3/11/19 7:34 AM, Juergen Gross wrote:
>
> I'm not sure. Patch 3 of this series is basically already there (see
> commit c6d4381220a0087ce19dbf6984d92c451bd6b364). So maybe all we need
> is patch 4, which should really be easy to do?
>
> Hans, could you give it a try? You'd need to use a 4.20
On 3/11/19 2:34 AM, Juergen Gross wrote:
>
> I'm not sure. Patch 3 of this series is basically already there (see
> commit c6d4381220a0087ce19dbf6984d92c451bd6b364). So maybe all we need
> is patch 4, which should really be easy to do?
FWIW to me this also seems to be the only missing part.
On 10/03/2019 23:03, Andrew Cooper wrote:
> On 10/03/2019 21:35, Hans van Kranenburg wrote:
>> found -1 4.19.20-1
>> thanks
>>
>> Hi,
>>
>> Reviving a thing from Jan 2017 here. I don't have this thread in my
>> mailbox, so no inline quotes.
>>
>> I just installed some HP z820 workstation and
On 10/03/2019 23:12, Hans van Kranenburg wrote:
> On 3/10/19 11:03 PM, Andrew Cooper wrote:
>> On 10/03/2019 21:35, Hans van Kranenburg wrote:
>>> [...]
>>>
>>> Using dom0_mem=2GiB,max:4GiB instead of dom0_mem=2GiB,max:2GiB (which I
>>> started with) makes the errors go away, so workaround
On 10/03/2019 23:03, Andrew Cooper wrote:
> On 10/03/2019 21:35, Hans van Kranenburg wrote:
>> found -1 4.19.20-1
>> thanks
>>
>> Hi,
>>
>> Reviving a thing from Jan 2017 here. I don't have this thread in my
>> mailbox, so no inline quotes.
>>
>> I just installed some HP z820 workstation and
On 3/10/19 11:03 PM, Andrew Cooper wrote:
> On 10/03/2019 21:35, Hans van Kranenburg wrote:
>>
>> [...]
>>
>> Using dom0_mem=2GiB,max:4GiB instead of dom0_mem=2GiB,max:2GiB (which I
>> started with) makes the errors go away, so workaround confirmed.
It's actually dom0_mem=2G,max:4G, I typed
On 10/03/2019 21:35, Hans van Kranenburg wrote:
> found -1 4.19.20-1
> thanks
>
> Hi,
>
> Reviving a thing from Jan 2017 here. I don't have this thread in my
> mailbox, so no inline quotes.
>
> I just installed some HP z820 workstation and rebooted it into Xen
> 4.11.1+26-g87f51bf366-3 with linux
found -1 4.19.20-1
thanks
Hi,
Reviving a thing from Jan 2017 here. I don't have this thread in my
mailbox, so no inline quotes.
I just installed some HP z820 workstation and rebooted it into Xen
4.11.1+26-g87f51bf366-3 with linux 4.19.20-1 as dom0 kernel.
During boot I'm greeted by a long list
On Mon, 2017-01-16 at 11:47 +, Ian Jackson wrote:
> Andy Smith writes ("Re: Bug#850425: Debian bug #850425 - mpt3sas "swiotlb
> buffer is full" problem only under Xen"):
> > On Mon, Jan 09, 2017 at 06:01:14PM +, Ian Jackson wrote:
> > > Patche
Andrew Cooper writes ("Re: Bug#850425: Debian bug #850425 - mpt3sas "swiotlb
buffer is full" problem only under Xen"):
> On 16/01/17 13:00, Ian Jackson wrote:
> > FYI David Vrabel doesn't work for Citrix any more but I'm hoping if
> > there are questions Andrew
On 16/01/17 13:00, Ian Jackson wrote:
> Andy Smith writes ("Re: Bug#850425: Debian bug #850425 - mpt3sas "swiotlb
> buffer is full" problem only under Xen"):
>> On Mon, Jan 16, 2017 at 11:47:54AM +, Ian Jackson wrote:
>>> Right. Well, you need t
Andy Smith writes ("Re: Bug#850425: Debian bug #850425 - mpt3sas "swiotlb
buffer is full" problem only under Xen"):
> On Mon, Jan 16, 2017 at 11:47:54AM +, Ian Jackson wrote:
> > Right. Well, you need to post to linux-kernel saying "this patch
> > fi
Hi Ian,
On Mon, Jan 16, 2017 at 11:47:54AM +, Ian Jackson wrote:
> Right. Well, you need to post to linux-kernel saying "this patch
> fixes such-and-such". You should:
[…]
I see. This is not something I've done before, but I'd be willing to
give it a go.
But, I am not the author of these
Andy Smith writes ("Re: Bug#850425: Debian bug #850425 - mpt3sas "swiotlb
buffer is full" problem only under Xen"):
> On Mon, Jan 09, 2017 at 06:01:14PM +, Ian Jackson wrote:
> > Patches only make it into Linux upstream stable releases if someone
> > push
Hi Ian,
On Mon, Jan 09, 2017 at 06:01:14PM +, Ian Jackson wrote:
> Patches only make it into Linux upstream stable releases if someone
> pushes to get them in.
Do you have any advice how I could push to get this to happen?
Obviously I need this in order for Xen to be usable on my hardware
On Mon, 2017-01-09 at 18:01 +, Ian Jackson wrote:
> Andy Smith writes ("Debian bug #850425 - mpt3sas "swiotlb buffer is
> full" problem only under Xen"):
> > I'm trying to get two Xen patches applied in Debian as I need it
> > for
> > Xen to
Andy Smith writes ("Debian bug #850425 - mpt3sas "swiotlb buffer is full"
problem only under Xen"):
> I'm trying to get two Xen patches applied in Debian as I need it for
> Xen to work on my hardware. The bug report is here:
>
> https://bugs.debian.org/cgi-
21 matches
Mail list logo
