All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lyude Paul <lyude@redhat.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Karol Herbst <kherbst@redhat.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	Linux PCI <linux-pci@vger.kernel.org>,
	Ben Skeggs <bskeggs@redhat.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	nouveau <nouveau@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Patrick Volkerding <volkerdi@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	Sasha Levin <sashal@kernel.org>
Subject: Re: nouveau regression with 5.7 caused by "PCI/PM: Assume ports without DLL Link Active train links in 100 ms"
Date: Tue, 21 Jul 2020 11:01:55 -0400	[thread overview]
Message-ID: <f951fba07ca7fa2fdfd590cd5023d1b31f515fa2.camel@redhat.com> (raw)
In-Reply-To: <20200721122247.GI5180@lahna.fi.intel.com>

Sure thing. Also, feel free to let me know if you'd like access to one of the
systems we saw breaking with this patch - I'm fairly sure I've got one of them
locally at my apartment and don't mind setting up AMT/KVM/SSH

On Tue, 2020-07-21 at 15:22 +0300, Mika Westerberg wrote:
> Hi,
> 
> [Sorry for the delay, I was on vacation]
> 
> On Fri, Jul 17, 2020 at 01:32:10PM +0200, Karol Herbst wrote:
> > Filed at https://bugzilla.kernel.org/show_bug.cgi?id=208597
> 
> Thanks for reporting.
> 
> I'll check your logs and try to figure if there is something we can do
> to make both nouveau and TBT working at the same time.
> 
> > oddly enough I wasn't able to reproduce it on my XPS 9560, will ping
> > once something breaks.
-- 
Cheers,
	Lyude Paul (she/her)
	Software Engineer at Red Hat


WARNING: multiple messages have this Message-ID (diff)
From: Lyude Paul <lyude@redhat.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Karol Herbst <kherbst@redhat.com>
Cc: Sasha Levin <sashal@kernel.org>,
	Patrick Volkerding <volkerdi@gmail.com>,
	Linux PCI <linux-pci@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	Bjorn Helgaas <helgaas@kernel.org>,
	Ben Skeggs <bskeggs@redhat.com>,
	nouveau <nouveau@lists.freedesktop.org>,
	Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: nouveau regression with 5.7 caused by "PCI/PM: Assume ports without DLL Link Active train links in 100 ms"
Date: Tue, 21 Jul 2020 11:01:55 -0400	[thread overview]
Message-ID: <f951fba07ca7fa2fdfd590cd5023d1b31f515fa2.camel@redhat.com> (raw)
In-Reply-To: <20200721122247.GI5180@lahna.fi.intel.com>

Sure thing. Also, feel free to let me know if you'd like access to one of the
systems we saw breaking with this patch - I'm fairly sure I've got one of them
locally at my apartment and don't mind setting up AMT/KVM/SSH

On Tue, 2020-07-21 at 15:22 +0300, Mika Westerberg wrote:
> Hi,
> 
> [Sorry for the delay, I was on vacation]
> 
> On Fri, Jul 17, 2020 at 01:32:10PM +0200, Karol Herbst wrote:
> > Filed at https://bugzilla.kernel.org/show_bug.cgi?id=208597
> 
> Thanks for reporting.
> 
> I'll check your logs and try to figure if there is something we can do
> to make both nouveau and TBT working at the same time.
> 
> > oddly enough I wasn't able to reproduce it on my XPS 9560, will ping
> > once something breaks.
-- 
Cheers,
	Lyude Paul (she/her)
	Software Engineer at Red Hat

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-07-21 15:02 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07 19:30 nouveau regression with 5.7 caused by "PCI/PM: Assume ports without DLL Link Active train links in 100 ms" Karol Herbst
2020-07-16 22:10 ` Karol Herbst
2020-07-16 22:10   ` Karol Herbst
2020-07-16 23:54   ` Bjorn Helgaas
2020-07-16 23:54     ` Bjorn Helgaas
2020-07-17  0:43     ` Karol Herbst
2020-07-17  0:43       ` Karol Herbst
2020-07-17  0:43       ` Karol Herbst
2020-07-17 11:32       ` Karol Herbst
2020-07-17 11:32         ` Karol Herbst
2020-07-21 12:22         ` Mika Westerberg
2020-07-21 12:22           ` Mika Westerberg
2020-07-21 15:01           ` Lyude Paul [this message]
2020-07-21 15:01             ` Lyude Paul
2020-07-21 15:27             ` Mika Westerberg
2020-07-21 15:27               ` Mika Westerberg
2020-07-21 16:00               ` Lyude Paul
2020-07-21 16:00                 ` Lyude Paul
2020-07-21 18:24                 ` Lyude Paul
2020-07-21 18:24                   ` Lyude Paul
2020-07-21 18:24                   ` Lyude Paul
2020-07-22  9:23                   ` Mika Westerberg
2020-07-22  9:23                     ` Mika Westerberg
2020-07-21 18:37               ` Patrick Volkerding
2020-07-21 18:37                 ` Patrick Volkerding
2020-07-22  9:25                 ` Mika Westerberg
2020-07-22  9:25                   ` Mika Westerberg
2020-07-22  9:25                   ` Mika Westerberg
2020-07-23 20:30                   ` Karol Herbst
2020-07-23 20:30                     ` Karol Herbst
2020-07-24  9:57                     ` Mika Westerberg
2020-07-24  9:57                       ` Mika Westerberg
2020-07-24 14:35                       ` Bjorn Helgaas
2020-07-24 14:35                         ` Bjorn Helgaas
2020-07-17 14:43       ` Sasha Levin
2020-07-17 14:43         ` Sasha Levin
2020-07-17 22:59         ` Bjorn Helgaas
2020-07-17 22:59           ` Bjorn Helgaas
2020-07-17 19:04     ` Lyude Paul
2020-07-17 19:04       ` Lyude Paul
2020-07-17 19:04       ` Lyude Paul
2020-07-17 19:52       ` Lukas Wunner
2020-07-17 19:52         ` Lukas Wunner
2020-07-21 13:08         ` Mika Westerberg
2020-07-21 13:08           ` Mika Westerberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f951fba07ca7fa2fdfd590cd5023d1b31f515fa2.camel@redhat.com \
    --to=lyude@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=helgaas@kernel.org \
    --cc=kai.heng.feng@canonical.com \
    --cc=kherbst@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=nouveau@lists.freedesktop.org \
    --cc=sashal@kernel.org \
    --cc=volkerdi@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.