From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Johannes Löthberg" <johannes@kyriasis.com>,
linux-wireless@vger.kernel.org
Subject: Re: rtl8192ce kernel panics since 3.17(?)
Date: Thu, 12 Feb 2015 10:38:32 -0600 [thread overview]
Message-ID: <54DCD708.3070402@lwfinger.net> (raw)
In-Reply-To: <20150212121057.GA1804@leeloo.kyriasis.com>
On 02/12/2015 06:10 AM, Johannes Löthberg wrote:
> Since sometime around version 3.16 or 3.17 I've been getting a lot of occasional
> kernel panics related to my wifi driver. My laptop has a Realtek RTL8188CE
> wireless card and uses the rtl8192ce driver.
>
> I have pictures of what I think is two identical kernel panics, a couple of days
> apart:
>
> https://lh4.googleusercontent.com/yjwOnrDmioCwuC8FqIXlKMiBTOXddLyJkWTiInJoX2o=w421-h569-no
>
> https://lh3.googleusercontent.com/-xM-1wSsVu4c/VKxDnlkgBbI/AAAAAAAAIng/HxtqgHgglHY/w421-h569-no/IMG_20150106_212020.jpg
>
>
> It only seems to happen when I have several days of uptime on my laptop and just
> use sleep all the time instead of shutting it down.
>
> Also I have a picture of a kernel panic that is different from the previous ones:
>
> https://lh3.googleusercontent.com/-Hj06Csglpa0/VKrI1al6QbI/AAAAAAAAImk/VzhmN-dfSB0/w657-h486-no/IMG_20150105_182236.jpg
>
>
> Not sure how to debug it really, but figured that sending in a report would be
> worth a shot.
>
What kernel were you running when you made the photos? Use the command 'uname
-r'. When I get that information, I can then use the dump trace to determine the
locations of the oops.
Larry
next prev parent reply other threads:[~2015-02-12 16:38 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 [this message]
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
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=54DCD708.3070402@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=johannes@kyriasis.com \
--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).