From: James Bourne <jbourne@hardrock.org>
To: Benjamin Reed <breed@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: [BUG REPORT 2.6.0] cisco airo_cs scheduling while atomic
Date: Fri, 18 Jul 2003 07:03:59 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0307180656090.19070-100000@cafe.hardrock.org> (raw)
The Cisco Airo card driver calls schedule while atomic in the function
issuecommand in drivers/net/wireless/airo.c line 2388.
Jul 17 15:27:10 localhost kernel: bad: scheduling while atomic!
Jul 17 15:27:10 localhost kernel: Call Trace:
Jul 17 15:27:10 localhost kernel: [<c0119754>] schedule+0x3c4/0x3d0
Jul 17 15:27:10 localhost kernel: [<d18cbb51>] sendcommand+0xa1/0xe0 [airo]
Jul 17 15:27:10 localhost kernel: [<d18cba80>] issuecommand+0x60/0x90 [airo]
Jul 17 15:27:10 localhost kernel: [<d18cc001>] PC4500_accessrid+0x41/0x80 [airo]
Jul 17 15:27:10 localhost kernel: [<d18cc0a3>] PC4500_readrid+0x63/0x130 [airo]
Jul 17 15:27:10 localhost kernel: [<d18c95d9>] readStatsRid+0x29/0x50 [airo]
Jul 17 15:27:10 localhost kernel: [<d18c9c0a>] airo_get_stats+0x2a/0xe0 [airo]
Jul 17 15:27:10 localhost kernel: [<c013e194>] check_poison_obj+0x54/0x1d0
Jul 17 15:27:10 localhost kernel: [<c013e194>] check_poison_obj+0x54/0x1d0
Jul 17 15:27:10 localhost kernel: [<c013fa94>] kmem_cache_alloc+0x114/0x160
Jul 17 15:27:10 localhost kernel: [<c01848ce>] proc_alloc_inode+0x1e/0x80
Jul 17 15:27:10 localhost kernel: [<c01848fd>] proc_alloc_inode+0x4d/0x80
Jul 17 15:27:10 localhost kernel: [<c016def7>] alloc_inode+0xd7/0x190
Jul 17 15:27:10 localhost kernel: [<c0184887>] proc_read_inode+0x17/0x40
Jul 17 15:27:10 localhost kernel: [<c016f941>] wake_up_inode+0x11/0x30
Jul 17 15:27:10 localhost kernel: [<c01f070a>] vsnprintf+0x21a/0x440
Jul 17 15:27:10 localhost kernel: [<c0173bd5>] seq_printf+0x45/0x60
Jul 17 15:27:10 localhost kernel: [<c02846eb>] dev_seq_printf_stats+0xeb/0x100
Jul 17 15:27:10 localhost kernel: [<c0284726>] dev_seq_show+0x26/0x80
Jul 17 15:27:10 localhost kernel: [<c0173689>] seq_read+0x1c9/0x300
Jul 17 15:27:10 localhost kernel: [<c0154bd3>] vfs_read+0xd3/0x140
Jul 17 15:27:10 localhost kernel: [<c0154e7f>] sys_read+0x3f/0x60
Jul 17 15:27:10 localhost kernel: [<c01094fb>] syscall_call+0x7/0xb
Regards
James Bourne
--
James Bourne | Email: jbourne@hardrock.org
Unix Systems Administrator | WWW: http://www.hardrock.org
Custom Unix Programming | Linux: The choice of a GNU generation
----------------------------------------------------------------------
"All you need's an occasional kick in the philosophy." Frank Herbert
next reply other threads:[~2003-07-18 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 13:03 James Bourne [this message]
2003-07-18 21:04 ` [BUG REPORT 2.6.0] cisco airo_cs scheduling while atomic Andrew Morton
2003-07-19 2:46 ` James Bourne
2003-07-19 3:00 ` Andrew Morton
2003-07-19 4:36 ` Tom Sightler
2003-07-19 12:17 Daniel Ritz
2003-07-19 12:58 Sven Dowideit
2003-07-21 17:15 ` Georg Nikodym
2003-07-21 19:52 ` Tom Sightler
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=Pine.LNX.4.44.0307180656090.19070-100000@cafe.hardrock.org \
--to=jbourne@hardrock.org \
--cc=breed@users.sourceforge.net \
--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 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.