From: Larry Finger <Larry.Finger@lwfinger.net>
To: "S. Gilles" <sgilles@terpmail.umd.edu>,
Chaoming Li <chaoming_li@realsil.com.cn>
Cc: linux-wireless@vger.kernel.org
Subject: Re: PROBLEM: Boot failure with bad RIP value
Date: Mon, 13 Oct 2014 22:41:26 -0500 [thread overview]
Message-ID: <543C9B66.6050705@lwfinger.net> (raw)
In-Reply-To: <20141013234509.GD22088@number18>
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 <Larry.Finger@lwfinger.net>
> 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 <Larry.Finger@lwfinger.net>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
>
> 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:
> [<ffffffffa01e20d6>] ? rtl_pci_start+0x2b/0x15f [rtl_pci]
> [<ffffffffa01c97b5>] rtl_op_start+0x45/0x64 [rtlwifi]
> [<ffffffff81577304>] ieee80211_do_open+0x152/0xb4b
> [<ffffffff815b52bc>] ? mutex_unlock+0x9/0xb
> [<ffffffff81577d4a>] ieee80211_open+0x4d/0x57
> [<ffffffff8147df7f>] __dev_open+0x8b/0xcb
> [<ffffffff8147e1e1>] __dev_change_flags+0xa4/0x13a
> [<ffffffff8147e297>] dev_change_flags+0x20/0x53
> [<ffffffff814d0204>] devinet_ioctl+0x269/0x568
> [<ffffffff814d19b4>] inet_ioctl+0x81/0x9e
> [<ffffffff814654e6>] sock_do_ioctl+0x20/0x3d
> [<ffffffff81465a56>] sock_ioctl+0x20e/0x21a
> [<ffffffff81136242>] do_vfs_ioctl+0x39e/0x467
> [<ffffffff815b7277>] ? sysret_check+0x1b/0x56
> [<ffffffff810965fe>] ? trace_hardirqs_on_caller+0x16e/0x18a
> [<ffffffff81136343>] SyS_ioctl+0x38/0x5f
> [<ffffffff815b7252>] system_call_fastpath+0x16/0x1b
> Code: Bad RIP value.
> RIP [< (null)>] (null)
> RSP <ffff880137d7fc90>
> 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
next prev parent reply other threads:[~2014-10-14 3:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 23:45 PROBLEM: Boot failure with bad RIP value S. Gilles
2014-10-14 3:41 ` Larry Finger [this message]
2014-10-14 4:13 ` S. Gilles
2014-10-21 22:35 ` S. Gilles
2014-10-31 13:56 ` S. Gilles
2014-10-31 15:07 ` Larry Finger
2014-11-01 3:41 ` S. Gilles
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=543C9B66.6050705@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=linux-wireless@vger.kernel.org \
--cc=sgilles@terpmail.umd.edu \
/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).