From: Jouni Malinen <jkmaline@cc.hut.fi>
To: joshk@triplehelix.org
Cc: linux-kernel@vger.kernel.org, Jean Tourrilhes <jt@hpl.hp.com>
Subject: Re: 2.5 kernel + hostap_cs + X11 = scheduling while atomic
Date: Wed, 5 Feb 2003 21:28:49 -0800 [thread overview]
Message-ID: <20030206052849.GA1540@jm.kir.nu> (raw)
In-Reply-To: <20030205073637.GA10725@saltbox.argot.org>
On Tue, Feb 04, 2003 at 11:36:37PM -0800, Joshua Kwan wrote:
> However, a combination of running said kernel, hostap_cs, and X11 produces
> this nasty infinite string of errors:
>
> bad: scheduling while atomic!
> Call Trace:
> [<d2948a30>] hfa384x_get_rid+0x36/0x2d6b7606 [hostap_cs]
That will sleep, so it better not be called while in interrupt context
or apparently also, while atomic with preemptive kernels(?).
> [<d29388b5>] hostap_get_wireless_stats+0xa6/0x2d6c77f1 [hostap]
That's the dev->get_wireless_stats handler. I have assumed that it is
allowed to sleep there, but apparently that is not the case with Linux
2.5.x (at least with CONFIG_PREEMPT). I added a workaround for this into
Host AP CVS, but you will not get signal quality statistics in that
case. I'll do a proper fix if that function is indeed not allowed to
sleep (e.g., by collecting the statistics before and just copying the
values here).
Jean, do you have a comment on this? This happens, e.g., when executing
'cat /proc/net/wireless':
> [<c0168f45>] seq_printf+0x45/0x56
> [<c02bd9b6>] wireless_seq_show+0xd6/0xf7
> [<c0141dd5>] do_mmap_pgoff+0x40e/0x6dc
> [<c0168a56>] seq_read+0x1c9/0x2ee
> [<c014d20f>] vfs_read+0xbc/0x127
> [<c014d496>] sys_read+0x3e/0x55
> [<c01093cb>] syscall_call+0x7/0xb
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2003-02-06 5:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 7:36 Joshua Kwan
2003-02-06 5:28 ` Jouni Malinen [this message]
2003-02-06 17:27 ` Jean Tourrilhes
2003-02-07 0:07 ` David Gibson
2003-02-07 0:36 ` Jean Tourrilhes
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=20030206052849.GA1540@jm.kir.nu \
--to=jkmaline@cc.hut.fi \
--cc=joshk@triplehelix.org \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®