On Mon, Oct 21, 2019 at 10:48 AM Karol Herbst wrote:
>
> fyi: I decided to go for a different workaround to fix the runpm
> issues observed with nvidia gpus with nouveau in the "pci: prevent
> putting nvidia GPUs into lower device states on certain intel bridges"
> thread
OK, I've seen that.
>
fyi: I decided to go for a different workaround to fix the runpm
issues observed with nvidia gpus with nouveau in the "pci: prevent
putting nvidia GPUs into lower device states on certain intel bridges"
thread
that's on the pci and pm mailing list. Maybe it makes sense to wait
for that to land
On Mon, Oct 21, 2019 at 4:14 AM Alex Hung wrote:
>
> We have done some tests on three of Intel + nVidia configuration
> systems with OEM _OSI strings removed - while some bugs are still
> observed, ex. one out of three has suspend/resume issues, no system
> crashes were observed - the biggest
We have done some tests on three of Intel + nVidia configuration
systems with OEM _OSI strings removed - while some bugs are still
observed, ex. one out of three has suspend/resume issues, no system
crashes were observed - the biggest issue that worries us.
The positive results give us confident
On Thu, Sep 5, 2019 at 5:26 PM Rafael J. Wysocki wrote:
>
> On Thursday, September 5, 2019 5:51:23 PM CEST Karol Herbst wrote:
> > is there any update on the testing with my patches? On the hardware I
> > had access to those patches helped, but I can't know if it also helped
> > on the hardware
On Thu, Sep 5, 2019 at 11:51 AM Karol Herbst wrote:
>
> is there any update on the testing with my patches? On the hardware I
> had access to those patches helped, but I can't know if it also helped
> on the hardware for which those workarounds where actually added.
>
> On Mon, Aug 19, 2019 at
On Thursday, September 5, 2019 5:51:23 PM CEST Karol Herbst wrote:
> is there any update on the testing with my patches? On the hardware I
> had access to those patches helped, but I can't know if it also helped
> on the hardware for which those workarounds where actually added.
Alex Hung and
is there any update on the testing with my patches? On the hardware I
had access to those patches helped, but I can't know if it also helped
on the hardware for which those workarounds where actually added.
On Mon, Aug 19, 2019 at 11:52 AM Rafael J. Wysocki wrote:
>
> On Thursday, August 15,
On Thursday, August 15, 2019 12:47:35 AM CEST Dave Airlie wrote:
> On Thu, 15 Aug 2019 at 07:31, Karol Herbst wrote:
> >
> > This reverts commit 28586a51eea666d5531bcaef2f68e4abbd87242c.
> >
> > The original commit message didn't even make sense. AMD _does_ support it
> > and
> > it works with
: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to
> enable dGPU direct output"
>
>
> [EXTERNAL EMAIL]
>
> On Thu, 15 Aug 2019 16:37:05 +0200,
> Alex Deucher wrote:
> >
> > On Thu, Aug 15, 2019 at 10:25 AM Karo
TCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to
> enable dGPU direct output"
>
>
> [EXTERNAL EMAIL]
>
> On Thu, Aug 15, 2019 at 4:20 PM wrote:
> >
> > > > There are definitely going to be regressions on machines in the field
> > > >
Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to
> enable dGPU direct output"
>
> On Thu, 15 Aug 2019 at 07:31, Karol Herbst wrote:
> >
> > This reverts commit 28586a51eea666d5531bcaef2f68e4abbd87242c.
> >
> > The
> > There are definitely going to be regressions on machines in the field with
> > the
> > in tree drivers by reverting this. I think we should have an answer for
> > all of
> those
> > before this revert is accepted.
> >
> > Regarding systems with Intel+NVIDIA, we'll have to work with partners
14, 2019 5:48 PM
> > > > > > To: Karol Herbst
> > > > > > Cc: LKML; Linux ACPI; dri-devel; nouveau; Rafael J . Wysocki; Alex
> > > > > > Hung;
> Ben
> > > > > > Skeggs; Dave Airlie
> > > > > >
> > Linux ACPI Mailing List; Alex Hung; Ben Skeggs; David Airlie
> > Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string
> > to
> > enable dGPU direct output"
> >
> >
> > [EXTERNAL EMAIL]
> >
> > On Thu, 15 Aug
> > Linux ACPI Mailing List; Alex Hung; Ben Skeggs; David Airlie
> > Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string
> > to
> > enable dGPU direct output"
> >
> >
> > [EXTERNAL EMAIL]
> >
> > On Thu,
On Thu, Aug 15, 2019 at 10:37 AM Alex Deucher wrote:
>
> On Thu, Aug 15, 2019 at 10:25 AM Karol Herbst wrote:
> >
> > On Thu, Aug 15, 2019 at 4:20 PM wrote:
> > >
> > > > > There are definitely going to be regressions on machines in the field
> > > > > with the
> > > > > in tree drivers by
On Thu, 15 Aug 2019 16:37:05 +0200,
Alex Deucher wrote:
>
> On Thu, Aug 15, 2019 at 10:25 AM Karol Herbst wrote:
> >
> > On Thu, Aug 15, 2019 at 4:20 PM wrote:
> > >
> > > > > There are definitely going to be regressions on machines in the field
> > > > > with the
> > > > > in tree drivers by
el.org> On
> > > > > > > Behalf Of Dave Airlie
> > > > > > > Sent: Wednesday, August 14, 2019 5:48 PM
> > > > > > > To: Karol Herbst
> > > > > > > Cc: LKML; Linux ACPI; dri-devel; nouveau; Rafael J . Wysocki;
>
On Thu, Aug 15, 2019 at 10:25 AM Karol Herbst wrote:
>
> On Thu, Aug 15, 2019 at 4:20 PM wrote:
> >
> > > > There are definitely going to be regressions on machines in the field
> > > > with the
> > > > in tree drivers by reverting this. I think we should have an answer
> > > > for all of
> >
t; > Wysocki; Alex Hung; Ben Skeggs; David Airlie
> > Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string
> > to
> > enable dGPU direct output"
> >
> >
> > [EXTERNAL EMAIL]
> >
> > On Thu, Aug 15, 2019 a
el.org> On
> > > > > > > Behalf Of Dave Airlie
> > > > > > > Sent: Wednesday, August 14, 2019 5:48 PM
> > > > > > > To: Karol Herbst
> > > > > > > Cc: LKML; Linux ACPI; dri-devel; nouveau; Rafael J . Wysocki;
>
On Thu, Aug 15, 2019 at 4:20 PM wrote:
>
> > > There are definitely going to be regressions on machines in the field
> > > with the
> > > in tree drivers by reverting this. I think we should have an answer for
> > > all of
> > those
> > > before this revert is accepted.
> > >
> > > Regarding
gt; > > Cc: LKML; Linux ACPI; dri-devel; nouveau; Rafael J . Wysocki; Alex
> > > > > Hung; Ben
> > > > > Skeggs; Dave Airlie
> > > > > Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI
> >
rnel.org
> > > > On
> > > > Behalf Of Dave Airlie
> > > > Sent: Wednesday, August 14, 2019 5:48 PM
> > > > To: Karol Herbst
> > > > Cc: LKML; Linux ACPI; dri-devel; nouveau; Rafael J . Wysocki; Alex
> > > > Hung; Ben
> > >
, August 14, 2019 5:48 PM
> > > To: Karol Herbst
> > > Cc: LKML; Linux ACPI; dri-devel; nouveau; Rafael J . Wysocki; Alex Hung;
> > > Ben
> > > Skeggs; Dave Airlie
> > > Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI
>
On Thu, Aug 15, 2019 at 12:47 AM Dave Airlie wrote:
>
> On Thu, 15 Aug 2019 at 07:31, Karol Herbst wrote:
> >
> > This reverts commit 28586a51eea666d5531bcaef2f68e4abbd87242c.
> >
> > The original commit message didn't even make sense. AMD _does_ support it
> > and
> > it works with Nouveau as
eau; Rafael J . Wysocki; Alex Hung; Ben
> > Skeggs; Dave Airlie
> > Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string
> > to
> > enable dGPU direct output"
> >
> > On Thu, 15 Aug 2019 at 07:31, Karol Herbst wrote:
> > >
On Thu, 15 Aug 2019 at 07:31, Karol Herbst wrote:
>
> This reverts commit 28586a51eea666d5531bcaef2f68e4abbd87242c.
>
> The original commit message didn't even make sense. AMD _does_ support it and
> it works with Nouveau as well.
>
> Also what was the issue being solved here? No references to
29 matches
Mail list logo
