linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
	"Bernhard M. Wiedemann" <bernhardout@lsmod.de>
Cc: wireless <linux-wireless@vger.kernel.org>,
	Ivo van Drn <IvDoorn@gmail.com>,
	Gertjan van Wingerde <gwingerde@gmail.com>,
	Helmut Schaa <helmut.schaa@googlemail.com>,
	"users@rt2x00.serialmonkey.com" <users@rt2x00.serialmonkey.com>
Subject: Re: Bug in rt2800pci on an RT3090
Date: Sat, 24 Sep 2011 18:30:07 +0200	[thread overview]
Message-ID: <20110924163007.GA10001@redhat.com> (raw)
In-Reply-To: <4E7CEE67.2070906@lwfinger.net>

On Fri, Sep 23, 2011 at 03:39:03PM -0500, Larry Finger wrote:
> A bug was sent to me concerning a scheduling-while-atomic-BUG. This
> happened shortly after KDE suspended an eeepc1015PE netbook during
> system update over WLAN. Suspend&resume normally worked allright.
> The OP is Berhard Wiedemann in the Cc list. Inquiries for more info
> go to him.

It looks like we forgot to unlock spinlock somewhere or we do not
use _irqsave version of spinlock where needed, but provided calltrace
is not naught to find the bug.

I suggest compile kernel with CONFIG_LOCKDEP, try to reproduce and see
if we do get some more messages.

Stanislaw

  reply	other threads:[~2011-09-24 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-23 20:39 Bug in rt2800pci on an RT3090 Larry Finger
2011-09-24 16:30 ` Stanislaw Gruszka [this message]
2011-09-24 18:53   ` Bernhard M. Wiedemann
2011-09-26  7:55     ` Stanislaw Gruszka
2011-09-26  8:20 ` Helmut Schaa

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=20110924163007.GA10001@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=IvDoorn@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=bernhardout@lsmod.de \
    --cc=gwingerde@gmail.com \
    --cc=helmut.schaa@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=users@rt2x00.serialmonkey.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 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).