linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: linux-wireless@vger.kernel.org
Subject: Re: rtl8192ce kernel panics since 3.17(?)
Date: Thu, 12 Feb 2015 16:51:12 -0600	[thread overview]
Message-ID: <54DD2E60.50509@lwfinger.net> (raw)
In-Reply-To: <20150212215457.GA23894@leeloo.kyriasis.com>

On 02/12/2015 03:54 PM, Johannes Löthberg wrote:
> On 12/02, Larry Finger wrote:
>> OK, that makes more sense than your original report of problems starting with
>> 3.16 or 3.17. That bug was fixed in 3.18.4.
>>
>
> Well, I'm rather sure that I had some panics in 3.17 due to it, but I have no
> photographic evidence anymore alas. And d'oh, should have tried a newer kernel
> before sending it in, was meaning to report it for a while but never ended up
> to, sorry.
>
> Any idea about the third kernel panic photo?

Trying to trace it back on my kernel leads to a nonsense location. If it happens 
again, capture the trace as you did, then find the location in one of the rtl* 
routines that crashed. In the picture you sent, that is 
"_rtl_pci_interrupt+0x3d0" and that is in rtl_pci. To find the code section that 
crashed, start in the kernel source directory and do the following:

gdb drivers/net/wireless/rtlwifi/rtl_pci.ko
l *_rtl_pci_interrupt+0x3d0
quit

Adjust the driver and location to match the new crash. Send me the output of the 
"l" command.

Larry



      reply	other threads:[~2015-02-12 22:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12 12:10 rtl8192ce kernel panics since 3.17(?) Johannes Löthberg
2015-02-12 16:38 ` Larry Finger
2015-02-12 17:27   ` Johannes Löthberg
2015-02-12 18:55     ` Larry Finger
2015-02-12 21:54       ` Johannes Löthberg
2015-02-12 22:51         ` Larry Finger [this message]

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=54DD2E60.50509@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.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 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).