From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-wireless@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: rc2-next-20170929: wireless down, won't come up
Date: Mon, 16 Oct 2017 12:51:55 +0200 [thread overview]
Message-ID: <20171016105154.GB3752@redhat.com> (raw)
In-Reply-To: <20171016102745.GA22525@amd>
Hi
Site note: Intel folks do not support iwlegacy, I removed them from CC.
On Mon, Oct 16, 2017 at 12:27:45PM +0200, Pavel Machek wrote:
> > In -next... after few days of usage with suspend and resume cycles,
> > wifi failed on thinkpad x60. I have not seen this in years...
<snip>
> > Any ideas?
We do not have any recent iwlegacy changes except cosmetic
ones, so this problem most likely is mac80211, pci or other
subsystem issue
> Suspend+resume fixed the problem.
It is not reproducible? If so, I think it will not be
easy to identify the issue.
Thanks
Stanislaw
next prev parent reply other threads:[~2017-10-16 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 9:18 rc2-next-20170929: wireless down, won't come up Pavel Machek
2017-10-16 10:27 ` Pavel Machek
2017-10-16 10:51 ` Stanislaw Gruszka [this message]
2017-10-16 12:24 ` Pavel Machek
2017-10-16 12:34 ` Stanislaw Gruszka
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=20171016105154.GB3752@redhat.com \
--to=sgruszka@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.