On Tue, Mar 12, 2024 at 05:07:12PM -0400, Jason Andryuk wrote:
> On 2024-03-10 10:06, Marek Marczykowski-Górecki wrote:
> > On Fri, Jan 19, 2024 at 02:40:06PM +0100, Marek Marczykowski-Górecki wrote:
> > > On Thu, Jan 18, 2024 at 01:23:56AM -0500, Patrick Plenefisch wrote:
> > > > On Wed, Jan 17,
On 2024-03-10 10:06, Marek Marczykowski-Górecki wrote:
On Fri, Jan 19, 2024 at 02:40:06PM +0100, Marek Marczykowski-Górecki wrote:
On Thu, Jan 18, 2024 at 01:23:56AM -0500, Patrick Plenefisch wrote:
On Wed, Jan 17, 2024 at 3:46 AM Jan Beulich wrote:
On 17.01.2024 07:12, Patrick Plenefisch
On Fri, Jan 19, 2024 at 02:40:06PM +0100, Marek Marczykowski-Górecki wrote:
> On Thu, Jan 18, 2024 at 01:23:56AM -0500, Patrick Plenefisch wrote:
> > On Wed, Jan 17, 2024 at 3:46 AM Jan Beulich wrote:
> > > On 17.01.2024 07:12, Patrick Plenefisch wrote:
> > > > As someone who hasn't built a
On Wed, Jan 24, 2024 at 3:23 AM Roger Pau Monné
wrote:
> > >
> > >>
> > >> > I had been working with ASRock support ever since I got my brand
> > >> > new motherboard because I couldn't see the BIOS/UEFI screens. I
> could
> > >> boot
> > >> > up, and once native linux took control amdgpu got
On Tue, Jan 23, 2024 at 08:27:18PM -0500, Patrick Plenefisch wrote:
> On Sat, Jan 20, 2024 at 8:33 PM Patrick Plenefisch
> wrote:
>
> >
> >
> > On Fri, Jan 19, 2024 at 6:06 AM Roger Pau Monné
> > wrote:
> >
> >> On Fri, Jan 19, 2024 at 02:44:35AM -0500, Patrick Plenefisch wrote:
> >> > On Thu,
On Sat, Jan 20, 2024 at 8:33 PM Patrick Plenefisch
wrote:
>
>
> On Fri, Jan 19, 2024 at 6:06 AM Roger Pau Monné
> wrote:
>
>> On Fri, Jan 19, 2024 at 02:44:35AM -0500, Patrick Plenefisch wrote:
>> > On Thu, Jan 18, 2024 at 7:41 AM Roger Pau Monné
>> > wrote:
>> >
>> > >
>> > > From that
On Fri, Jan 19, 2024 at 6:06 AM Roger Pau Monné
wrote:
> On Fri, Jan 19, 2024 at 02:44:35AM -0500, Patrick Plenefisch wrote:
> > On Thu, Jan 18, 2024 at 7:41 AM Roger Pau Monné
> > wrote:
> >
> > >
> > > From that environment (PVH dom0) can you see if you can dump the
> > > contents of the VFCT
On Fri, Jan 19, 2024 at 4:54 AM Huang Rui wrote:
> Thanks Roger to involve us. The VFCT table is to expose video BIOS image by
> AMD GPUs. You can see details here:
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/amd/include/atombios.h
>
> Did you
: ACPI VFCT table too short on PVH dom0 (was: Re: E820 memory
> allocation issue on Threadripper platforms)
>
> On Fri, Jan 19, 2024 at 03:44:35PM +0800, Patrick Plenefisch wrote:
> >On Thu, Jan 18, 2024 at 7:41 AM Roger Pau Monné
> ><[1]roger@citrix.com> wrote:
>
On Fri, Jan 19, 2024 at 02:50:38PM +0100, Jan Beulich wrote:
> On 19.01.2024 14:40, Marek Marczykowski-Górecki wrote:
> > On Thu, Jan 18, 2024 at 01:23:56AM -0500, Patrick Plenefisch wrote:
> >> On Wed, Jan 17, 2024 at 3:46 AM Jan Beulich wrote:
> >>> On 17.01.2024 07:12, Patrick Plenefisch
On 19.01.2024 14:40, Marek Marczykowski-Górecki wrote:
> On Thu, Jan 18, 2024 at 01:23:56AM -0500, Patrick Plenefisch wrote:
>> On Wed, Jan 17, 2024 at 3:46 AM Jan Beulich wrote:
>>> On 17.01.2024 07:12, Patrick Plenefisch wrote:
As someone who hasn't built a kernel in over a decade, should
On Thu, Jan 18, 2024 at 01:23:56AM -0500, Patrick Plenefisch wrote:
> On Wed, Jan 17, 2024 at 3:46 AM Jan Beulich wrote:
> > On 17.01.2024 07:12, Patrick Plenefisch wrote:
> > > As someone who hasn't built a kernel in over a decade, should I figure
> > out
> > > how to do a kernel build with
On Fri, Jan 19, 2024 at 02:44:35AM -0500, Patrick Plenefisch wrote:
> On Thu, Jan 18, 2024 at 7:41 AM Roger Pau Monné
> wrote:
>
> >
> > From that environment (PVH dom0) can you see if you can dump the
> > contents of the VFCT table? I don't have a system with that table, so
> > not sure if
On Fri, Jan 19, 2024 at 03:44:35PM +0800, Patrick Plenefisch wrote:
>On Thu, Jan 18, 2024 at 7:41 AM Roger Pau Monné
><[1]roger@citrix.com> wrote:
>
> From that environment (PVH dom0) can you see if you can dump the
> contents of the VFCT table? I don't have a system with
On Thu, Jan 18, 2024 at 4:46 AM Roger Pau Monné
wrote:
> >
> > Luckily linux logs are mercifully short. Append this to
> > xen-4.18p_grub_linuxoffset_pvh.log:
> >
> > [0.778770] i2c_designware AMDI0010:00: Unknown Synopsys component
> type:
> > 0x
> > [0.914664] amd_gpio
On Thu, Jan 18, 2024 at 10:46:26AM +0100, Roger Pau Monné wrote:
> On Thu, Jan 18, 2024 at 03:34:13AM -0500, Patrick Plenefisch wrote:
> > On Thu, Jan 18, 2024 at 3:27 AM Roger Pau Monné
> > wrote:
> >
> > > On Thu, Jan 18, 2024 at 01:23:56AM -0500, Patrick Plenefisch wrote:
> > > > On Wed, Jan
On Thu, Jan 18, 2024 at 03:34:13AM -0500, Patrick Plenefisch wrote:
> On Thu, Jan 18, 2024 at 3:27 AM Roger Pau Monné
> wrote:
>
> > On Thu, Jan 18, 2024 at 01:23:56AM -0500, Patrick Plenefisch wrote:
> > > On Wed, Jan 17, 2024 at 3:46 AM Jan Beulich wrote:
> > >
> > > > On 17.01.2024 07:12,
On 18.01.2024 07:23, Patrick Plenefisch wrote:
> On Wed, Jan 17, 2024 at 3:46 AM Jan Beulich wrote:
>> On 17.01.2024 07:12, Patrick Plenefisch wrote:
>>> I'm currently talking to the vendor's support team and testing a beta
>> BIOS
>>> for unrelated reasons, is there something specific I should
On Thu, Jan 18, 2024 at 3:27 AM Roger Pau Monné
wrote:
> On Thu, Jan 18, 2024 at 01:23:56AM -0500, Patrick Plenefisch wrote:
> > On Wed, Jan 17, 2024 at 3:46 AM Jan Beulich wrote:
> >
> > > On 17.01.2024 07:12, Patrick Plenefisch wrote:
> > > > On Tue, Jan 16, 2024 at 4:33 AM Jan Beulich
>
On Thu, Jan 18, 2024 at 01:23:56AM -0500, Patrick Plenefisch wrote:
> On Wed, Jan 17, 2024 at 3:46 AM Jan Beulich wrote:
>
> > On 17.01.2024 07:12, Patrick Plenefisch wrote:
> > > On Tue, Jan 16, 2024 at 4:33 AM Jan Beulich wrote:
> > >
> > >> On 16.01.2024 01:22, Patrick Plenefisch wrote:
>
On 17.01.2024 13:59, Roger Pau Monné wrote:
> On Wed, Jan 17, 2024 at 01:06:53PM +0100, Marek Marczykowski-Górecki wrote:
>> On Tue, Jan 16, 2024 at 10:33:26AM +0100, Jan Beulich wrote:
>>> ... as per
>>>
>>> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x4a0
>>>
>>> there's an
On Wed, Jan 17, 2024 at 01:06:53PM +0100, Marek Marczykowski-Górecki wrote:
> On Tue, Jan 16, 2024 at 10:33:26AM +0100, Jan Beulich wrote:
> > ... as per
> >
> > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x4a0
> >
> > there's an overlap with not exactly a hole, but with an
> >
On Wed, Jan 17, 2024 at 11:40:20AM +0100, Jan Beulich wrote:
> On 17.01.2024 11:13, Roger Pau Monné wrote:
> > On Wed, Jan 17, 2024 at 09:46:27AM +0100, Jan Beulich wrote:
> >> Whereas I assume the native kernel can deal with that as long as
> >> it's built with CONFIG_RELOCATABLE=y. I don't think
On Tue, Jan 16, 2024 at 10:33:26AM +0100, Jan Beulich wrote:
> ... as per
>
> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x4a0
>
> there's an overlap with not exactly a hole, but with an
> EfiACPIMemoryNVS region:
>
> (XEN) 00010-003159fff type=2
On 17.01.2024 11:13, Roger Pau Monné wrote:
> On Wed, Jan 17, 2024 at 09:46:27AM +0100, Jan Beulich wrote:
>> Whereas I assume the native kernel can deal with that as long as
>> it's built with CONFIG_RELOCATABLE=y. I don't think we want to
>> get into the business of interpreting the kernel's
On Wed, Jan 17, 2024 at 09:46:27AM +0100, Jan Beulich wrote:
> On 17.01.2024 07:12, Patrick Plenefisch wrote:
> > On Tue, Jan 16, 2024 at 4:33 AM Jan Beulich wrote:
> >> On 16.01.2024 01:22, Patrick Plenefisch wrote:
> >> It remains to be seen in how far it is reasonably possible to work
> >>
On Wed, Jan 17, 2024 at 01:12:30AM -0500, Patrick Plenefisch wrote:
> On Tue, Jan 16, 2024 at 4:33 AM Jan Beulich wrote:
>
> > On 16.01.2024 01:22, Patrick Plenefisch wrote:
> > It remains to be seen in how far it is reasonably possible to work
> > around this in the kernel. While (sadly) still
On 17.01.2024 07:12, Patrick Plenefisch wrote:
> On Tue, Jan 16, 2024 at 4:33 AM Jan Beulich wrote:
>
>> On 16.01.2024 01:22, Patrick Plenefisch wrote:
>>> I managed to set up serial access and saved the output with the requested
>>> flags as the attached logs
>>
>> Thanks. While you didn't ...
On Tue, Jan 16, 2024 at 4:33 AM Jan Beulich wrote:
> On 16.01.2024 01:22, Patrick Plenefisch wrote:
> > I managed to set up serial access and saved the output with the requested
> > flags as the attached logs
>
> Thanks. While you didn't ...
>
>
> ... fiddle with the Linux message, ...
>
I
On 16.01.2024 01:22, Patrick Plenefisch wrote:
> I managed to set up serial access and saved the output with the requested
> flags as the attached logs
Thanks. While you didn't ...
> On Thu, Jan 11, 2024 at 5:13 AM Juergen Gross wrote:
>> On 11.01.24 09:37, Jan Beulich wrote:
>>> On 11.01.2024
I managed to set up serial access and saved the output with the requested
flags as the attached logs
Patrick
On Thu, Jan 11, 2024 at 5:13 AM Juergen Gross wrote:
> On 11.01.24 09:37, Jan Beulich wrote:
> > On 11.01.2024 03:29, Patrick Plenefisch wrote:
> >> Hi,
> >>
> >> I ran into a memory
On 11.01.24 09:37, Jan Beulich wrote:
On 11.01.2024 03:29, Patrick Plenefisch wrote:
Hi,
I ran into a memory allocation issue, I think. It is the same as
https://github.com/QubesOS/qubes-issues/issues/8791 and I saw at the end it
was recommended (by marmarek) that the issue reporter forward
On 11/1/24 10:37, Jan Beulich wrote:
On 11.01.2024 03:29, Patrick Plenefisch wrote:
Hi,
I ran into a memory allocation issue, I think. It is the same as
https://github.com/QubesOS/qubes-issues/issues/8791 and I saw at the end it
was recommended (by marmarek) that the issue reporter forward
On 11.01.2024 03:29, Patrick Plenefisch wrote:
> Hi,
>
> I ran into a memory allocation issue, I think. It is the same as
> https://github.com/QubesOS/qubes-issues/issues/8791 and I saw at the end it
> was recommended (by marmarek) that the issue reporter forward the issue to
> this list. I
34 matches
Mail list logo
