search for: martitz

Hi Thomas, On Mon, Oct 01, 2018 at 04:25:06PM +0200, Thomas Martitz wrote: > Am 01.10.18 um 06:57 schrieb Daniel Drake: > > On Sun, Sep 30, 2018 at 5:07 AM Thomas Martitz <kugel at rockbox.org> wrote: > > > The latest iteration does not work on my HP system. The GPU fails to > > > power up just like the unpatched kernel. > >...

On Sun, Sep 30, 2018 at 5:07 AM Thomas Martitz <kugel at rockbox.org> wrote: > The latest iteration does not work on my HP system. The GPU fails to > power up just like the unpatched kernel. That's weird, I would not expect a behaviour change in the latest patch. pci_restore_config_dword() has some debug messages, could you ple...

Am 31. Dezember 2015 03:54:43 MEZ, schrieb Karol Herbst <nouveau at karolherbst.de>: >> Thomas Martitz <kugel at rockbox.org> hat am 30. Dezember 2015 um 23:53 >> geschrieben: >> >> Am 25.12.2015 um 18:43 schrieb Pierre Moreau: >> > Hello, >> > >> > Maybe my e-mail client is messing with me, but I couldn't find any >dmesg >> > outpu...

Am 02.10.18 um 22:03 schrieb Bjorn Helgaas: > Hi Thomas, > > On Mon, Oct 01, 2018 at 04:25:06PM +0200, Thomas Martitz wrote: >> Am 01.10.18 um 06:57 schrieb Daniel Drake: >>> On Sun, Sep 30, 2018 at 5:07 AM Thomas Martitz <kugel at rockbox.org> wrote: >>>> The latest iteration does not work on my HP system. The GPU fails to >>>> power up just like the unpatched kernel....

Am 25.12.2015 um 18:43 schrieb Pierre Moreau: > Hello, > > Maybe my e-mail client is messing with me, but I couldn't find any dmesg output > attached to your e-mail. Could you please try to attach it again? > > By the way, since you have a Kepler, you should try booting with > "nouveau.War00C800_0=1". That workaround is enabled by default in 4.4-rc5 > (IIRC),

...ot;r8169: don't use MSI-X on RTL8106e"). It also fixes the same issue on RTL6186evl/8111evl on an Aimfor-tech laptop that we had not yet patched. I suspect it will also fix the issue that was worked around in commit 7c53a722459c ("r8169: don't use MSI-X on RTL8168g"). Thomas Martitz reports that this change also solves an issue where the AMD Radeon Polaris 10 GPU on the HP Zbook 14u G5 is unresponsive after S3 suspend/resume. Link: https://bugzilla.kernel.org/show_bug.cgi?id=201069 Signed-off-by: Daniel Drake <drake at endlessm.com> --- drivers/pci/pci.c | 25 +++++++++...

...It also fixes the same issue on RTL6186evl/8111evl on an > > Aimfor-tech laptop that we had not yet patched. I suspect it will also > > fix the issue that was worked around in commit 7c53a722459c ("r8169: > > don't use MSI-X on RTL8168g"). > > > > Thomas Martitz reports that this change also solves an issue where > > the AMD Radeon Polaris 10 GPU on the HP Zbook 14u G5 is unresponsive > > after S3 suspend/resume. > > > > Link: https://bugzilla.kernel.org/show_bug.cgi?id=201069 > > Signed-off-by: Daniel Drake <drake at endl...

[+cc LKML, Dave, Luming] On Fri, Sep 07, 2018 at 05:05:15PM +0200, Peter Wu wrote: > On Fri, Sep 07, 2018 at 01:36:14PM +0800, Daniel Drake wrote: > <..> > > Thomas Martitz reports that this workaround also solves an issue where > > the AMD Radeon Polaris 10 GPU on the HP Zbook 14u G5 is unresponsive > > after S3 suspend/resume. > > Where was this claimed? It is not stated in the linked bug: > (https://bugs.freedesktop.org/show_bug.cgi?id=105760...

...ot;r8169: don't use MSI-X on RTL8106e"). It also fixes the same issue on RTL6186evl/8111evl on an Aimfor-tech laptop that we had not yet patched. I suspect it will also fix the issue that was worked around in commit 7c53a722459c ("r8169: don't use MSI-X on RTL8168g"). Thomas Martitz reports that this change also solves an issue where the AMD Radeon Polaris 10 GPU on the HP Zbook 14u G5 is unresponsive after S3 suspend/resume. Link: https://bugzilla.kernel.org/show_bug.cgi?id=201069 Signed-off-by: Daniel Drake <drake at endlessm.com> --- Notes: Replaces patch:...

...ot;r8169: don't use MSI-X on RTL8106e"). It also fixes the same issue on RTL6186evl/8111evl on an Aimfor-tech laptop that we had not yet patched. I suspect it will also fix the issue that was worked around in commit 7c53a722459c ("r8169: don't use MSI-X on RTL8168g"). Thomas Martitz reports that this workaround also solves an issue where the AMD Radeon Polaris 10 GPU on the HP Zbook 14u G5 is unresponsive after S3 suspend/resume. >From our testing, the affected Intel PCI bridges are: Intel Skylake PCIe Controller (x16) [8086:1901] (rev 05) Intel Skylake PCIe Controller (x1...

...please try to attach it again? By the way, since you have a Kepler, you should try booting with "nouveau.War00C800_0=1". That workaround is enabled by default in 4.4-rc5 (IIRC), but that might not be the case on Karol's branch. Best regards, Pierre On 08:18 AM - Dec 25 2015, Thomas Martitz wrote: > Hello, > > following up on myself, it was suggested on IRC that I better attach a dmesg > output. Here's the output of a clean boot & echo 0f > /sys/.../pstate cycle. > > I can't spot a message that relates to the reclock action, and there's only >...

> Thomas Martitz <kugel at rockbox.org> hat am 30. Dezember 2015 um 23:53 > geschrieben: > > Am 25.12.2015 um 18:43 schrieb Pierre Moreau: > > Hello, > > > > Maybe my e-mail client is messing with me, but I couldn't find any dmesg > > output > > attached to your e-m...

On Fri, Sep 07, 2018 at 01:36:14PM +0800, Daniel Drake wrote: <..> > Thomas Martitz reports that this workaround also solves an issue where > the AMD Radeon Polaris 10 GPU on the HP Zbook 14u G5 is unresponsive > after S3 suspend/resume. Where was this claimed? It is not stated in the linked bug: (https://bugs.freedesktop.org/show_bug.cgi?id=105760 > On resume, reprogra...

Am 01.10.18 um 06:57 schrieb Daniel Drake: > On Sun, Sep 30, 2018 at 5:07 AM Thomas Martitz <kugel at rockbox.org> wrote: >> The latest iteration does not work on my HP system. The GPU fails to >> power up just like the unpatched kernel. > > That's weird, I would not expect a behaviour change in the latest > patch. pci_restore_config_dword() has some debug...

...on > RTL8106e"). It also fixes the same issue on RTL6186evl/8111evl on an > Aimfor-tech laptop that we had not yet patched. I suspect it will also > fix the issue that was worked around in commit 7c53a722459c ("r8169: > don't use MSI-X on RTL8168g"). > > Thomas Martitz reports that this change also solves an issue where > the AMD Radeon Polaris 10 GPU on the HP Zbook 14u G5 is unresponsive > after S3 suspend/resume. > > Link: https://bugzilla.kernel.org/show_bug.cgi?id=201069 > Signed-off-by: Daniel Drake <drake at endlessm.com> Still Revie...

...on > RTL8106e"). It also fixes the same issue on RTL6186evl/8111evl on an > Aimfor-tech laptop that we had not yet patched. I suspect it will also > fix the issue that was worked around in commit 7c53a722459c ("r8169: > don't use MSI-X on RTL8168g"). > > Thomas Martitz reports that this change also solves an issue where > the AMD Radeon Polaris 10 GPU on the HP Zbook 14u G5 is unresponsive > after S3 suspend/resume. > > Link: https://bugzilla.kernel.org/show_bug.cgi?id=201069 > Signed-off-by: Daniel Drake <drake at endlessm.com> Applied wit...

...on > RTL8106e"). It also fixes the same issue on RTL6186evl/8111evl on an > Aimfor-tech laptop that we had not yet patched. I suspect it will also > fix the issue that was worked around in commit 7c53a722459c ("r8169: > don't use MSI-X on RTL8168g"). > > Thomas Martitz reports that this change also solves an issue where > the AMD Radeon Polaris 10 GPU on the HP Zbook 14u G5 is unresponsive > after S3 suspend/resume. > > Link: https://bugzilla.kernel.org/show_bug.cgi?id=201069 > Signed-off-by: Daniel Drake <drake at endlessm.com> > --- >...

...the same issue on RTL6186evl/8111evl on an >>> Aimfor-tech laptop that we had not yet patched. I suspect it will also >>> fix the issue that was worked around in commit 7c53a722459c ("r8169: >>> don't use MSI-X on RTL8168g"). >>> >>> Thomas Martitz reports that this change also solves an issue where >>> the AMD Radeon Polaris 10 GPU on the HP Zbook 14u G5 is unresponsive >>> after S3 suspend/resume. >>> >>> Link: https://bugzilla.kernel.org/show_bug.cgi?id=201069 >>> Signed-off-by: Daniel Drake &lt...

this series solves different issues we encounter on kepler cards while reclocking: 1. core clock doesn't change at all and produces a volting error (patch 1) this can happen when the voltage table has only 0ed values in the header so we have to parse the entries itself, which contain the right voltages 2. kepler won't clock to highest cstates (patch 2) this happens, because there are

Am 25.12.2015 um 18:43 schrieb Pierre Moreau: > Hello, > > Maybe my e-mail client is messing with me, but I couldn't find any dmesg output > attached to your e-mail. Could you please try to attach it again? > > By the way, since you have a Kepler, you should try booting with > "nouveau.War00C800_0=1". That workaround is enabled by default in 4.4-rc5 > (IIRC),