From: Willy Tarreau <w@1wt.eu>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mason <slash.tmp@free.fr>, stable@vger.kernel.org
Subject: Re: Status of v4.9
Date: Mon, 16 Jan 2017 18:42:30 +0100 [thread overview]
Message-ID: <20170116174230.GA6162@1wt.eu> (raw)
In-Reply-To: <20170116155524.GB18675@kroah.com>
On Mon, Jan 16, 2017 at 04:55:24PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Jan 16, 2017 at 03:39:44PM +0100, Willy Tarreau wrote:
> > On Mon, Jan 16, 2017 at 03:29:24PM +0100, Greg Kroah-Hartman wrote:
> > > Has anyone run any benchmarks yet even? Have you?
> >
> > At least FWIW I've upgraded my laptop to it two weeks ago in the hope
> > to spot any issue, and my build farm is not running on it as well. No
> > perf nor stability issues to report yet, but it's early ;-)
>
> Ah, that's good to hear, thanks for letting me know.
Hmmm that was before I tried to use WiFi :-)
------------
iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
wlan0: authenticate with c0:56:27:eb:e7:b2
wlan0: send auth to c0:56:27:eb:e7:b2 (try 1/3)
wlan0: authenticated
wlan0: waiting for beacon from c0:56:27:eb:e7:b2
wlan0: associate with c0:56:27:eb:e7:b2 (try 1/3)
wlan0: RX AssocResp from c0:56:27:eb:e7:b2 (capab=0x431 status=0 aid=4)
wlan0: associated
wlan0: deauthenticated from c0:56:27:eb:e7:b2 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
wlan0: authenticate with c0:56:27:eb:e7:b2
wlan0: send auth to c0:56:27:eb:e7:b2 (try 1/3)
wlan0: authenticated
wlan0: associate with c0:56:27:eb:e7:b2 (try 1/3)
wlan0: RX AssocResp from c0:56:27:eb:e7:b2 (capab=0x431 status=0 aid=4)
wlan0: associated
wlan0: deauthenticated from c0:56:27:eb:e7:b2 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
wlan0: authenticate with c0:56:27:eb:e7:b2
wlan0: send auth to c0:56:27:eb:e7:b2 (try 1/3)
wlan0: authenticated
wlan0: associate with c0:56:27:eb:e7:b2 (try 1/3)
wlan0: RX AssocResp from c0:56:27:eb:e7:b2 (capab=0x431 status=0 aid=4)
wlan0: associated
wlan0: deauthenticated from c0:56:27:eb:e7:b2 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
wlan0: authenticate with c0:56:27:eb:e7:b2
wlan0: send auth to c0:56:27:eb:e7:b2 (try 1/3)
wlan0: authenticated
wlan0: associate with c0:56:27:eb:e7:b2 (try 1/3)
wlan0: RX AssocResp from c0:56:27:eb:e7:b2 (capab=0x431 status=0 aid=4)
wlan0: associated
wlan0: deauthenticated from c0:56:27:eb:e7:b2 (Reason: 9=STA_REQ_ASSOC_WITHOUT_AUTH)
------------
I'll try to bisect, it was rock-solid in 4.4.38 (strange for WiFi I know)
and doesn't work at all in 4.9.1-4.9.4.
Willy
next prev parent reply other threads:[~2017-01-16 17:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 8:39 Status of v4.9 Mason
2017-01-16 10:34 ` Greg Kroah-Hartman
2017-01-16 12:35 ` Mason
2017-01-16 13:02 ` Greg Kroah-Hartman
2017-01-16 14:11 ` Mason
2017-01-16 14:29 ` Greg Kroah-Hartman
2017-01-16 14:39 ` Willy Tarreau
2017-01-16 15:55 ` Greg Kroah-Hartman
2017-01-16 17:42 ` Willy Tarreau [this message]
2017-01-16 18:34 ` Willy Tarreau
2017-01-17 7:15 ` Greg Kroah-Hartman
2017-01-17 7:28 ` Willy Tarreau
2017-01-17 7:45 ` Christoph Biedl
2017-06-05 21:41 ` Christoph Biedl
2017-01-17 9:15 ` Mason
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=20170116174230.GA6162@1wt.eu \
--to=w@1wt.eu \
--cc=gregkh@linuxfoundation.org \
--cc=slash.tmp@free.fr \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).