Return-path: Received: from mail-pa0-f42.google.com ([209.85.220.42]:40991 "EHLO mail-pa0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754487AbaJNDl3 (ORCPT ); Mon, 13 Oct 2014 23:41:29 -0400 Received: by mail-pa0-f42.google.com with SMTP id bj1so7102454pad.1 for ; Mon, 13 Oct 2014 20:41:29 -0700 (PDT) Message-ID: <543C9B66.6050705@lwfinger.net> (sfid-20141014_054139_010643_17037434) Date: Mon, 13 Oct 2014 22:41:26 -0500 From: Larry Finger MIME-Version: 1.0 To: "S. Gilles" , Chaoming Li CC: linux-wireless@vger.kernel.org Subject: Re: PROBLEM: Boot failure with bad RIP value References: <20141013234509.GD22088@number18> In-Reply-To: <20141013234509.GD22088@number18> Content-Type: text/plain; charset=windows-1252; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 10/13/2014 06:45 PM, S. Gilles wrote: > (Sending this to the right people this time, hopefully.) > > I have been getting a consistent boot failure with 3.17, which I have > bisected to > > 38506ecefab911785d5e1aa5889f6eeb462e0954 is the first bad commit > commit 38506ecefab911785d5e1aa5889f6eeb462e0954 > Author: Larry Finger > Date: Mon Sep 22 09:39:19 2014 -0500 > > rtlwifi: rtl_pci: Start modification for new drivers > > Future patches will move the drivers for RTL8192EE and RTL8821AE > from staging to the regular wireless tree. Here, the necessary features > are added to the PCI driver. Other files are touched due to changes > in the various data structs. > > Signed-off-by: Larry Finger > Signed-off-by: John W. Linville > > The end of the trace (hand-retyped, so there may be errors that > escaped me): > > R10: ffffffff825f2d80 R11: 0000000000000000 R12: ffff8800b4f107c0 > R13: ffff8800b4f124b8 R14: 0000000000001000 R15: ffff8800b4c7a000 > FS: 000007fc66c938700(0000) GS:ffff88013e200000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 0000000000000000 CR3: 00000000b5438000 CR4: 00000000000407f0 > Stack: > ffffffffa01e20d6 ffff8800b4f12420 ffff8800b4f107c0 ffff880137d7fcd0 > ffffffffa01c97b5 ffff8800b4f107c0 ffff8800b4c7a8d0 0000000000000000 > ffff880137d7fd30 ffffffff81577304 0000000000000000 ffff8800b4c7a8c0 > Call Trace: > [] ? rtl_pci_start+0x2b/0x15f [rtl_pci] > [] rtl_op_start+0x45/0x64 [rtlwifi] > [] ieee80211_do_open+0x152/0xb4b > [] ? mutex_unlock+0x9/0xb > [] ieee80211_open+0x4d/0x57 > [] __dev_open+0x8b/0xcb > [] __dev_change_flags+0xa4/0x13a > [] dev_change_flags+0x20/0x53 > [] devinet_ioctl+0x269/0x568 > [] inet_ioctl+0x81/0x9e > [] sock_do_ioctl+0x20/0x3d > [] sock_ioctl+0x20e/0x21a > [] do_vfs_ioctl+0x39e/0x467 > [] ? sysret_check+0x1b/0x56 > [] ? trace_hardirqs_on_caller+0x16e/0x18a > [] SyS_ioctl+0x38/0x5f > [] system_call_fastpath+0x16/0x1b > Code: Bad RIP value. > RIP [< (null)>] (null) > RSP > CR2: 0000000000000000 > ---[ end trace 7307d2524c1e640b ]--- > > This is extremely easy to test (boot) and seems 100% reproducible. > > I have submitted Bug 86211 - Boot failure: Bad RIP value for rtl8192ce > for this issue. I am traveling and it may be a few days before I am able to make a suitable test. In the meantime, please post the appropriate stanza for the Realtek device from the output of lspci -nn There are several different devices that use driver rtl8192ce, and I need to know which one you have so that I can duplicate the problem. Larry