From: "Pierre-Loup A. Griffais" <pgriffais@valvesoftware.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <edumazet@google.com>, lkml <linux-kernel@vger.kernel.org>,
<torvalds@linux-foundation.org>
Subject: Re: Steam is broken on new kernels
Date: Fri, 21 Jun 2019 14:43:54 -0700 [thread overview]
Message-ID: <6033e333-137b-9016-bfdc-62ed747835ef@valvesoftware.com> (raw)
In-Reply-To: <20190621214139.GA31034@kroah.com>
On 6/21/19 2:41 PM, Greg Kroah-Hartman wrote:
> On Fri, Jun 21, 2019 at 02:27:41PM -0700, Pierre-Loup A. Griffais wrote:
>> This seems to have broken us:
>>
>> https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.1.11
>>
>> Here's some affected users:
>>
>> https://github.com/ValveSoftware/steam-for-linux/issues/6326
>>
>> https://www.reddit.com/r/linux_gaming/comments/c37lmh/psa_steam_does_not_connect_on_kernels_newer_than/
>>
>> https://www.phoronix.com/scan.php?page=news_item&px=Steam-Networking-Kernel-Woes
>>
>> I don't really understand that distributions that claim to be desktop
>> products would have fast-tracked a server-oriented fix to all their users
>> without testing one of the primary desktop usecases, but that's another
>> thing to figure out later.
>>
>
> What specific commit caused the breakage?
Unclear as of yet, we're starting that process on our end just now. Not
sure if a user has already performed a bisect and shared his findings in
one of the links below, but we'll be scouring these and doing our own
testing as next steps.
>
next prev parent reply other threads:[~2019-06-21 21:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 21:27 Pierre-Loup A. Griffais
2019-06-21 21:41 ` Greg Kroah-Hartman
2019-06-21 21:43 ` Pierre-Loup A. Griffais [this message]
2019-06-21 22:19 ` Linus Torvalds
[not found] ` <CANn89iL5+x3n9H9v4O6y39W=jvQs=uuXbzOvN5mBbcj0t+wdeg@mail.gmail.com>
2019-06-21 23:04 ` Pierre-Loup A. Griffais
2019-06-21 23:42 ` Josh Hunt
2019-06-21 23:54 ` Linus Torvalds
2019-06-22 0:19 ` Eric Dumazet
2019-06-22 1:01 ` Pierre-Loup A. Griffais
2019-06-22 5:28 ` Linus Torvalds
2019-06-22 6:35 ` Greg Kroah-Hartman
2019-06-22 7:37 ` Greg Kroah-Hartman
2019-06-26 2:02 ` Guenter Roeck
2019-06-26 2:29 ` Greg Kroah-Hartman
2019-06-26 3:43 ` Guenter Roeck
2019-06-26 4:20 ` Eric Dumazet
2019-06-26 5:17 ` Greg Kroah-Hartman
2019-06-26 6:38 ` Eric Dumazet
2019-06-26 8:23 ` Greg Kroah-Hartman
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=6033e333-137b-9016-bfdc-62ed747835ef@valvesoftware.com \
--to=pgriffais@valvesoftware.com \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®