Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp4564516imm; Tue, 11 Sep 2018 14:03:49 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZkFTgU10PB/En82JwFAFi4/Z5x8yz+3ML+LD78AdZEE1fOHeCjOrIBZKG8V5/ivri257/m X-Received: by 2002:a62:1544:: with SMTP id 65-v6mr31289613pfv.178.1536699829438; Tue, 11 Sep 2018 14:03:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536699829; cv=none; d=google.com; s=arc-20160816; b=WEqAPXhb/EMEQo+FPVPROYHn8i99hqGcFF9y1KfkoM2XOzweG9J3NrYn1XhMuZJP0X J8Xy7Z62wclJwWkCGWSDdnZ06XTofCQEC/svax8w+WgLiPIIEOdFpVK3tNih/gT668Hq 5g/nXoCmaR8S0XZK4n4azzj0JaYQLOr4s5ynGncjw+Frz6FVrSSN3e/zH7cBl/7GpH3Z iZSVG540ngyAOnE3Hld39dDRmWshk5zfVSNZmRHFyEou70iiiEJ9yS42raXYaeQ3kwju XQ9FirOYowpfzNGrkPrQLFItzrQd2W5zXcNE00pT/HrZ7LzBNGgdPMtd4sgXQZsET0gg XC/w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:to:from:subject:message-id; bh=xoKOEOQ0KYQ24epj6NCbEQAYLzZ2cUQrkP6b3fyfzP8=; b=je8j3U7QENnVwuSAZdPfZdTD1CVgNzvNSJb3VyweLsfwl0CAkr7H8RdxMcmNO/eK/+ 8i7/05GrSk8RZ868ojisHAmRdBSMUESB4v8oVqYlJj52+GHV8Gybnlu648FjHHtOTRj4 1mZdi2/vfCrFnqFkONNOYbIrZifqTmstGKvp2SgWVqzTTzB+jkFfWf8unbKjydC4xWFu WaxKfq8IQaCHbMrSD1fV1ZO4s1pidrjJpG8Wc9GqjlezDcB6gBISOZrOmdamgiGYDS+T J26i2q8N8Khz5qHekHW7mN9MUvmrUR5o2yuhNkegrjt19vaYMImcWIKMYDiTRElxCebe 1vdA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d13-v6si22387349plj.286.2018.09.11.14.03.34; Tue, 11 Sep 2018 14:03:49 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727833AbeILCDS (ORCPT + 99 others); Tue, 11 Sep 2018 22:03:18 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:48138 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727645AbeILCDS (ORCPT ); Tue, 11 Sep 2018 22:03:18 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from ) id 1fzpnV-0005L8-Vv; Tue, 11 Sep 2018 23:02:10 +0200 Message-ID: <1536699720.3224.152.camel@sipsolutions.net> Subject: Re: 4.19-rc[23] iwlwifi: BUG in swiotlb From: Johannes Berg To: Randy Dunlap , LKML , linux-wireless , linuxwifi@intel.com Date: Tue, 11 Sep 2018 23:02:00 +0200 In-Reply-To: <8bea4cfc-4b16-7c7c-3e9a-5b6684b47345@infradead.org> References: <0c5e53e5-2afa-8d38-0b48-272c670c4bc5@infradead.org> <1536651177.3224.106.camel@sipsolutions.net> <8bea4cfc-4b16-7c7c-3e9a-5b6684b47345@infradead.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.6 (3.26.6-1.fc27) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.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