From: Anisse Astier <anisse@astier.eu>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: rtl8192ce : freeze after connecting to network with FW Power Save on
Date: Thu, 24 May 2012 19:10:37 +0200 [thread overview]
Message-ID: <20120524191037.19e10917@destiny.ordissimo> (raw)
In-Reply-To: <4FB3D348.2010700@lwfinger.net>
(sorry for the delay, I got caught up in other things, and forgot to send
answer email)
On Wed, 16 May 2012 11:18:16 -0500, Larry Finger <Larry.Finger@lwfinger.net> wrote :
> On 05/16/2012 05:41 AM, Anisse Astier wrote:
> > I enabled the following options:
> > CONFIG_LOCKDEP_SUPPORT=y
> > CONFIG_LOCKDEP=y
> > CONFIG_DEBUG_LOCKDEP=y
> > CONFIG_DEBUG_SPINLOCK=y
> > CONFIG_DEBUG_MUTEXES=y
> > But it didn't detect any lockup yet, and machine still hangs. I'll try
> > CONFIG_PROVE_LOCKING.
> >
> > Enabling CONFIG_DEBUG_INFO seems to make the problem go away...
>
> That may explain why I never see the problem. I do not think I have ever
> generated a kernel with that parameter disabled, and my distro's kernels have it
> enabled. Does anything new get logged (dmesg output) when that parameter is enabled?
>
There's no zero difference in dmesg output. Have you tried with
debug_info disabled?
Unfortunately, I've lost access to this hardware, so I won't be able to
do more test for quite some time.
next prev parent reply other threads:[~2012-05-24 17:10 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
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 [this message]
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=20120524191037.19e10917@destiny.ordissimo \
--to=anisse@astier.eu \
--cc=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).