From: Pavel Machek <pavel@ucw.cz>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>, rdunlap@infradead.org
Cc: Johannes Berg <johannes.berg@intel.com>,
"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
luciano.coelho@intel.com, linuxwifi@intel.com,
linux-wireless@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: v4.19-rc3 on thinkpad x220: kernel BUG at kernel/dma/swiotlb.c:521 when enabling radios
Date: Sun, 16 Sep 2018 10:22:28 +0200 [thread overview]
Message-ID: <20180916082227.GA4602@amd> (raw)
In-Reply-To: <CAF7Mx6o1PV2xcgLp94=9OP1ZaxoxjebPE1_t93hQ65UkDLgKWQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
Hi!
> > > I was running X220 with wireless disabled for long long time. Now I
> > > needed to enable it, and got...
> >
> > Tried with next-0913, and machine crashed with capslock LED blinking
> > when I toggled the switch...
> >
> > Any ideas?
>
> Replying using my phone. There has been such a report from Randy Dunlap on
> September 11 with subject "4.19-rc[23] iwlwifi: BUG in swiotlb".
>
> Did not quite follow that, just recall seeing it fly by. Maybe it helps.
Thanks for pointer.
Hi, Randy! We have same problem.
I switched back to v4.18, and it seems to be ok.
I'd prefer not to hear the b-word. Any other ideas?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-09-16 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 6:47 v4.19-rc3 on thinkpad x220: kernel BUG at kernel/dma/swiotlb.c:521 when enabling radios Pavel Machek
2018-09-16 6:57 ` Pavel Machek
[not found] ` <CAF7Mx6o1PV2xcgLp94=9OP1ZaxoxjebPE1_t93hQ65UkDLgKWQ@mail.gmail.com>
2018-09-16 8:22 ` Pavel Machek [this message]
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=20180916082227.GA4602@amd \
--to=pavel@ucw.cz \
--cc=arend.vanspriel@broadcom.com \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luciano.coelho@intel.com \
--cc=rdunlap@infradead.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).