Return-path: Received: from resqmta-po-08v.sys.comcast.net ([96.114.154.167]:59558 "EHLO resqmta-po-08v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752064AbcEWRh5 (ORCPT ); Mon, 23 May 2016 13:37:57 -0400 Reply-To: james@nurealm.net Subject: Re: "kernel: BUG: scheduling while atomic:" errors with linux kernel 4.6 References: <20160519225612.GB12028@localhost> <573F2FB3.6090206@lwfinger.net> To: Larry Finger , Bob Copeland Cc: hostap@lists.infradead.org, linux-wireless@vger.kernel.org From: James Feeney Message-ID: (sfid-20160523_193804_273697_AE1F055F) Date: Mon, 23 May 2016 11:29:46 -0600 MIME-Version: 1.0 In-Reply-To: <573F2FB3.6090206@lwfinger.net> Content-Type: text/plain; charset=utf-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 05/20/2016 09:39 AM, Larry Finger wrote: > @James: Please run the command "dmesg | grep rtl_rfreg_delay". Do any of the > resulting lines show a value other than "+0x38" for the offset? If that is the > only one, the attached patch should fix the problem. Sorry about the delayed response. $ dmesg | grep rtl_rfreg_delay [ 15.936262] [] rtl_rfreg_delay+0x38/0x50 [rtlwifi] [ 348.735402] [] rtl_rfreg_delay+0x38/0x50 [rtlwifi] So that looks like a no, just the "+0x38" for the offset. Thanks James