Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to enable dGPU direct output"

2019-10-20 Thread Alex Hung
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 to ack the removal of the OEM
_OSI strings. While our tests were not able to cover all possible I+N
systems, we are sure we can fix issues along the way. If there aren't
systems that cannot be fixed without these OEM _OSI strings, these
strings should probably enable with DMI quirks (possible future
patches) so they won't affect others.

Acked-by: Alex Hung 




On Thu, Sep 5, 2019 at 10:26 AM 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 for which those workarounds where actually added.
>
> Alex Hung and Mario need to answer this question I think.
>
> > On Mon, Aug 19, 2019 at 11:52 AM Rafael J. Wysocki  
> > wrote:
> > >
> > > 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 Nouveau as well.
> > > > >
> > > > > Also what was the issue being solved here? No references to any bugs 
> > > > > and not
> > > > > even explaining any issue at all isn't the way we do things.
> > > > >
> > > > > And even if it means a muxed design, then the fix is to make it work 
> > > > > inside the
> > > > > driver, not adding some hacky workaround through ACPI tricks.
> > > > >
> > > > > And what out of tree drivers do or do not support we don't care one 
> > > > > bit anyway.
> > > > >
> > > >
> > > > I think the reverts should be merged via Rafael's tree as the original
> > > > patches went in via there, and we should get them in asap.
> > > >
> > > > Acked-by: Dave Airlie 
> > >
> > > The _OSI strings are to be dropped when all of the needed support is 
> > > there in
> > > drivers, so they should go away along with the requisite driver changes.
> > >
> >
> > that goes beside the point. firmware level workarounds for GPU driver
> > issues were pushed without consulting with upstream GPU developers.
> > That's something which shouldn't have happened in the first place. And
> > yes, I am personally annoyed by the fact, that people know about
> > issues, but instead of contacting the proper persons and working on a
> > proper fix, we end up with stupid firmware level workarounds. I can't
> > see why we ever would have wanted such workarounds in the first place.
> >
> > And I would be much happier if the next time something like that comes
> > up, that the drm mailing list will be contacted as well or somebody
> > involved.
> >
> > We could have also just disable the feature inside the driver (and
> > probably we should have done that a long time ago, so that is
> > essentially our fault, but still)
> >
> > > I'm all for dropping then when that's the case, so please feel free to 
> > > add ACKs
> > > from me to the patches in question at that point.
> > >
> > > Cheers,
> > > Rafael
> > >
> > >
> > >
> >
>
>
>
>


-- 
Cheers,
Alex Hung
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

[Nouveau] [Bug 112070] H/W Acceleration sufficiently buggy on Debian to hard lock machine GeForce 7600 GO

2019-10-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=112070

--- Comment #10 from Ilia Mirkin  ---
(In reply to Doobz from comment #9)
> Does nouveau need any firmware for my card? I thought it didn't, but looking
> here it appears it might.
> https://nouveau.freedesktop.org/wiki/VideoAcceleration/

It would need it for hypothetical VP1 support. However there is no software
support for the VP1 decoding engine, and according to all reports, it didn't
make anything actually faster (on Windows). The MPEG decoding engine should
work fine (via XvMC ... IIRC VDPAU didn't quite work, and XvMC is a better
match anyways).

This is all for accelerated video decoding, which is not in play for the videos
you're talking about.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2019-10-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #117 from Lukas Wunner  ---
Created attachment 145778
  --> https://bugs.freedesktop.org/attachment.cgi?id=145778=edit
Debug patch to log invocations of pm_runtime_forbid()

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2019-10-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #116 from Lukas Wunner  ---
@Przemysław Kopa:

The fix was applied by Takashi Iwai on Thursday Oct 17 with commit
94989e318b2f, it was merged to Linus' tree on Friday Oct 18 and will thus be
part of v5.4-rc4 due out later today. It should appear in v5.3-stable within 1
or 2 weeks. You may want to double-check that the issue is gone with this fix.

There's one problem remaining, you shouldn't have to manually echo "auto" to
the HDA's control file because we call pm_runtime_allow() on the HDA device in
drivers/pci/quirks.c:quirk_gpu_hda() -> pci_create_device_link(). Something
must be calling pm_runtime_forbid() afterwards, perhaps this is triggered from
user space on Arch Linux. I'm attaching a little debug patch which logs a
stacktrace to dmesg whenever pm_runtime_allow() / _forbid() is called for a
device. Feel free to attach dmesg output with this patch applied and I'll be
happy to take a look at it.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau