All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Randy Dunlap <rdunlap@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	linuxwifi@intel.com
Subject: Re: 4.19-rc[23] iwlwifi: BUG in swiotlb
Date: Tue, 11 Sep 2018 23:02:00 +0200	[thread overview]
Message-ID: <1536699720.3224.152.camel@sipsolutions.net> (raw)
In-Reply-To: <8bea4cfc-4b16-7c7c-3e9a-5b6684b47345@infradead.org>

On Tue, 2018-09-11 at 13:57 -0700, Randy Dunlap wrote:

> I can't be sure.  I've been having problems booting this laptop for a few
> weeks now but haven't tracked it down yet.

Ok.

> The wireless NIC is Condor Peak:
> 
> 04:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak]

Wow, that's old. I should have one somewhere, but we haven't worked on
this NIC in many years. We've touched the driver, of course, but the
configuration for this wouldn't have changed.

> sigh.  I can reproduce it without the patch:
> 
> > https://p.sipsolutions.net/aa0dccd7a60fe176.txt
> 
> but with that patch, it just hangs after about 25 seconds of booting
> (slow hard drive, not SSD).
> 
> I'll try some other ways.

Hmm. That makes me think you have some corruption going on, rather than
something really being set to 0, because otherwise you should've seen
the warning at least?

johannes

  reply	other threads:[~2018-09-12  2:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11  2:17 4.19-rc[23] iwlwifi: BUG in swiotlb Randy Dunlap
2018-09-11  7:32 ` Johannes Berg
2018-09-11 20:57   ` Randy Dunlap
2018-09-11 21:02     ` Johannes Berg [this message]
2018-09-16  9:34   ` Pavel Machek
2018-09-16  9:41     ` Pavel Machek
2018-09-16  9:55       ` Pavel Machek
2018-09-16  9:59         ` [PATCH] fix iwlwifi on old cards in v4.19 was " Pavel Machek
2018-09-16 10:12           ` [linuxwifi] " Grumbach, Emmanuel
2018-09-16 10:14             ` Grumbach, Emmanuel
2018-09-16 11:06               ` Pavel Machek
2018-10-07  0:44             ` Randy Dunlap
2018-10-07  0:56               ` Randy Dunlap
2018-09-16 22:27           ` Randy Dunlap

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=1536699720.3224.152.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxwifi@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 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.