From: Frederic Weisbecker <fweisbec@gmail.com>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Poking ieee80211_default_rc_algo causes kernel lockups
Date: Sun, 15 Feb 2009 20:41:48 +0100 [thread overview]
Message-ID: <20090215194147.GB5790@nowhere> (raw)
In-Reply-To: <883216.75749.qm@web110607.mail.gq1.yahoo.com>
On Sun, Feb 15, 2009 at 11:24:41AM -0800, Sitsofe Wheeler wrote:
> > Could you please enable the CONFIG_DETECT_SOFTLOCKUP option in your kernel?
>
> > It's on Kernel Hacking > Detect Soft Lockups.
> > With some chances you will have a relevant stacktrace of the lockup, in case
> > I couldn't reproduce it.
>
> I'll try (the kernel I'm currently using is jam packed with with debug options) but I'm unconvinced it will unfreeze enough for anything useful...
No need to actually, I guess we found it...
next prev parent reply other threads:[~2009-02-15 19:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 16:09 Poking ieee80211_default_rc_algo causes kernel lockups Sitsofe Wheeler
2009-02-15 17:02 ` Frederic Weisbecker
2009-02-15 19:24 ` Sitsofe Wheeler
2009-02-15 19:41 ` Frederic Weisbecker [this message]
2009-02-15 21:02 ` Sitsofe Wheeler
2009-02-16 1:40 ` Frederic Weisbecker
2009-02-16 2:37 ` Frederic Weisbecker
2009-02-15 19:35 ` Frederic Weisbecker
2009-02-16 10:10 ` Rusty Russell
2009-02-16 17:59 ` Frederic Weisbecker
2009-02-16 23:37 ` Rusty Russell
2009-02-20 10:27 ` What made this bug report better? (was Re: Poking ieee80211_default_rc_algo causes kernel lockups) Sitsofe Wheeler
2009-02-20 11:31 ` Ingo Molnar
2009-02-24 3:13 ` Rusty Russell
2009-02-24 8:16 ` What made this bug report better? Sitsofe Wheeler
2009-02-24 17:58 ` Frederic Weisbecker
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=20090215194147.GB5790@nowhere \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sitsofe@yahoo.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.