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: Tue, 17 Jan 2017 08:28:38 +0100 [thread overview]
Message-ID: <20170117072838.GC6868@1wt.eu> (raw)
In-Reply-To: <20170117071531.GA7996@kroah.com>
On Tue, Jan 17, 2017 at 08:15:31AM +0100, Greg Kroah-Hartman wrote:
> On Mon, Jan 16, 2017 at 07:34:03PM +0100, Willy Tarreau wrote:
> > On Mon, Jan 16, 2017 at 06:42:30PM +0100, Willy Tarreau wrote:
> > > 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.
> >
> > OK please disregard this, I should have shut up, it suddenly stopped
> > working in 4.4 as well, so it's just working as one could expect a wire
> > made of thin air to work. There's no regression here, I'll have to try
> > to debug this later if I need it.
>
> Is this a hardware issue? What wireless driver/chip is it?
Probably just an AP issue only, that's why I really don't care. I've just
verified that it works fine at home. I use it once every few months, if
it doesn't work anymore with my previous kernel I consider that it's not
a kernel regression :-) It just happens that I discovered the issue for
the first time in 4.9 so I believed it was a regression. If it had been
broken since 4.4, many daily users would have reported it ;-)
The driver is iwlwifi BTW.
Cheers,
Willy
next prev parent reply other threads:[~2017-01-17 7:28 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
2017-01-16 18:34 ` Willy Tarreau
2017-01-17 7:15 ` Greg Kroah-Hartman
2017-01-17 7:28 ` Willy Tarreau [this message]
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=20170117072838.GC6868@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 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.