From: Larry Finger <Larry.Finger@lwfinger.net>
To: Jamie Kitson <jamie@kitten-x.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: BUG: Soft lockup CPU#0 stuck for 22s! [wpa_supplicant:756]
Date: Tue, 04 Oct 2011 14:03:34 -0500 [thread overview]
Message-ID: <4E8B5886.3010103@lwfinger.net> (raw)
In-Reply-To: <CA+z-pWFvBfvqY9_km8t3Xbmt=2Pw7eJo8T+SyFp=Lv=d1+ZOPw@mail.gmail.com>
On 10/04/2011 01:03 PM, Jamie Kitson wrote:
> Hi,
>
> I get the following error when cold booting, it doesn't seem to happen
> after a restart:
>
> http://www.flickr.com/photos/jamiekitson/6211329161/
>
> I have just moved my installation to a new machine with a:
>
> 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE
> 802.11b/g/n WiFi Adapter (rev 01)
> Subsystem: Realtek Semiconductor Co., Ltd. Device 8195
> Kernel driver in use: rtl8192ce
> Kernel modules: rtl8192ce
>
> Linux jamie-laptop 3.0-ARCH #1 SMP PREEMPT Tue Aug 30 08:53:25 CEST
> 2011 x86_64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel
> GNU/Linux
>
> I am reporting it here as I assume it's a rtl8192ce bug, but if not I
> can report it to the wpa_supplicant guys.
The bug is not necessarily caused by rtl8192ce. I have never seen this problem
on my system. I would also expect a stack dump. Anyone know what is needed to
get one here?
I do have some further questions.
Which variant of the RTL8188CE do you have? Use 'lspci -nn' to tell.
Does ARCH have an updated kernel later than 3.0?
What version of wpa-supplicant?
Are you using NetworkManager? If so, what version? Is your desktop KDE, Gnome,
or something else? If NM, what applet and version?
If not NM, how do you connect?
Larry
next prev parent reply other threads:[~2011-10-04 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 18:03 BUG: Soft lockup CPU#0 stuck for 22s! [wpa_supplicant:756] Jamie Kitson
2011-10-04 19:03 ` Larry Finger [this message]
2011-10-04 20:59 ` Jamie Kitson
2011-10-05 2:55 ` 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=4E8B5886.3010103@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=jamie@kitten-x.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).