On Wed, Aug 07, 2024 at 12:26:26PM +0200, Jürgen Groß wrote:
> On 07.08.24 12:23, Marek Marczykowski-Górecki wrote:
> > On Tue, Aug 06, 2024 at 05:24:22PM +0200, Jürgen Groß wrote:
> > > On 06.08.24 17:21, Marek Marczykowski-Górecki wrote:
> > > > On Tue, Aug 06, 2024 at 04:12:32PM +0200, Jürgen Gr
On 07.08.24 12:23, Marek Marczykowski-Górecki wrote:
On Tue, Aug 06, 2024 at 05:24:22PM +0200, Jürgen Groß wrote:
On 06.08.24 17:21, Marek Marczykowski-Górecki wrote:
On Tue, Aug 06, 2024 at 04:12:32PM +0200, Jürgen Groß wrote:
Marek,
On 17.06.24 16:03, Marek Marczykowski-Górecki wrote:
On M
On Tue, Aug 06, 2024 at 05:24:22PM +0200, Jürgen Groß wrote:
> On 06.08.24 17:21, Marek Marczykowski-Górecki wrote:
> > On Tue, Aug 06, 2024 at 04:12:32PM +0200, Jürgen Groß wrote:
> > > Marek,
> > >
> > > On 17.06.24 16:03, Marek Marczykowski-Górecki wrote:
> > > > On Mon, Jun 17, 2024 at 01:22:3
On 06.08.2024 17:24, Jürgen Groß wrote:
> On 06.08.24 17:21, Marek Marczykowski-Górecki wrote:
>> On Tue, Aug 06, 2024 at 04:12:32PM +0200, Jürgen Groß wrote:
>>> If possible it would be nice to verify suspend to disk still working, as
>>> the kernel will need to access the ACPI NVS area in this ca
On 06.08.24 17:21, Marek Marczykowski-Górecki wrote:
On Tue, Aug 06, 2024 at 04:12:32PM +0200, Jürgen Groß wrote:
Marek,
On 17.06.24 16:03, Marek Marczykowski-Górecki wrote:
On Mon, Jun 17, 2024 at 01:22:37PM +0200, Jan Beulich wrote:
Hello,
while it feels like we had a similar situation bef
On Tue, Aug 06, 2024 at 04:12:32PM +0200, Jürgen Groß wrote:
> Marek,
>
> On 17.06.24 16:03, Marek Marczykowski-Górecki wrote:
> > On Mon, Jun 17, 2024 at 01:22:37PM +0200, Jan Beulich wrote:
> > > Hello,
> > >
> > > while it feels like we had a similar situation before, I can't seem to be
> > >
Marek,
On 17.06.24 16:03, Marek Marczykowski-Górecki wrote:
On Mon, Jun 17, 2024 at 01:22:37PM +0200, Jan Beulich wrote:
Hello,
while it feels like we had a similar situation before, I can't seem to be
able to find traces thereof, or associated (Linux) commits.
Is it some AMD Threadripper sy
On 17.06.24 16:25, Jan Beulich wrote:
On 17.06.2024 16:03, Marek Marczykowski-Górecki wrote:
On Mon, Jun 17, 2024 at 01:22:37PM +0200, Jan Beulich wrote:
Hello,
while it feels like we had a similar situation before, I can't seem to be
able to find traces thereof, or associated (Linux) commits.
On 17.06.2024 16:03, Marek Marczykowski-Górecki wrote:
> On Mon, Jun 17, 2024 at 01:22:37PM +0200, Jan Beulich wrote:
>> Hello,
>>
>> while it feels like we had a similar situation before, I can't seem to be
>> able to find traces thereof, or associated (Linux) commits.
>
> Is it some AMD Threadri
On Mon, Jun 17, 2024 at 01:22:37PM +0200, Jan Beulich wrote:
> Hello,
>
> while it feels like we had a similar situation before, I can't seem to be
> able to find traces thereof, or associated (Linux) commits.
Is it some AMD Threadripper system by a chance? Previous thread on this
issue:
https://
Hello,
while it feels like we had a similar situation before, I can't seem to be
able to find traces thereof, or associated (Linux) commits.
With
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x400
...
(XEN) Dom0 alloc.: 00044000->00044800 (619175 pages to be
a
11 matches
Mail list logo
