linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Anisse Astier <anisse@astier.eu>
Cc: linux-wireless@vger.kernel.org
Subject: Re: rtl8192ce : freeze after connecting to network with FW Power Save on
Date: Tue, 15 May 2012 09:51:23 -0500	[thread overview]
Message-ID: <4FB26D6B.2030005@lwfinger.net> (raw)
In-Reply-To: <20120515152951.7cc4f84b@destiny.ordissimo>

On 05/15/2012 08:29 AM, Anisse Astier wrote:
> Hi,
>
> With the rtl8192ce driver, I get freezes a few seconds after connecting
> to a network. (see PCI id below) Machine is unusable after hang. I'm
> using the linville/wireless-next git tree.
>
> I've been playing with the different options, and noticed that setting
> fwlps=0 fixes the issue.
>
> I've tried to get more messages with netconsole, but once the lockup
> happens I'm unable to get any debug message (regardless of the log level
> of the driver).
>
> Regards,
>
> Anisse
>
>
> 06:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)
> 	Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:8212]
> 	Flags: bus master, fast devsel, latency 0, IRQ 17
> 	I/O ports at 3000 [size=256]
> 	Memory at f0200000 (64-bit, non-prefetchable) [size=16K]
> 	Capabilities: [40] Power Management version 3
> 	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
> 	Capabilities: [70] Express Endpoint, MSI 00
> 	Capabilities: [100] Advanced Error Reporting
> 	Capabilities: [140] Virtual Channel
> 	Capabilities: [160] Device Serial Number 01-91-81-fe-ff-4c-e0-00
> 	Kernel driver in use: rtl8192ce

I have been doing long-term tests with that same card for about one week with no 
dropouts and no freezes. I am running wireless-testing, not wireless-next; 
however, I have all the rtlwifi and friends patches applied. I think it is safe 
to say that I cannot duplicate your results, and that we need to explore the 
rest of your system to see what is different.

Is your system 32- or 64-bit? How many cores in your CPU? Have you tried 
connecting to more than one AP? What is the make and model of the AP that needs 
to have power save turned off? What is the mode of operation?

I am using a 64-bit system with a dual-core CPU. My main AP is a Netgear 
WNDR3300 running standard firmware and is encrypted using WPA2-TKIP (AES). The 
mode is 802.11n at up to 270 Mbps; however, I have also tested using a Linksys 
WRT54GL running openWRT Kamakaze firmware. That one is 802.11g at up to 54 Mbps.

Larry

  reply	other threads:[~2012-05-15 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 13:29 rtl8192ce : freeze after connecting to network with FW Power Save on Anisse Astier
2012-05-15 14:51 ` Larry Finger [this message]
2012-05-15 15:04   ` Anisse Astier
2012-05-15 16:45     ` Larry Finger
2012-05-16 10:41       ` Anisse Astier
2012-05-16 16:18         ` Larry Finger
2012-05-24 17:10           ` Anisse Astier
2012-08-29 15:06             ` Anisse Astier

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=4FB26D6B.2030005@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=anisse@astier.eu \
    --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).