From: Alex Riesen <alexander.riesen@synopsys.COM>
To: Paul Fulghum <paulkf@microgate.com>
Cc: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>,
LKML <linux-kernel@vger.kernel.org>,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: 2.5.69+bk: "sleeping function called from illegal context" on card release while shutting down
Date: Tue, 13 May 2003 19:21:14 +0200 [thread overview]
Message-ID: <20030513172114.GH32559@Synopsys.COM> (raw)
In-Reply-To: <1052839860.2255.19.camel@diemos>
Paul Fulghum, Tue, May 13, 2003 17:31:01 +0200:
> > > Just tried to eject the card while the system was shutting down.
> > Don't know if this is fixed by latest Russell patches, but vanilla and
> > -bk snapshots do *not* contain the latest PCMCIA/CardBus code. Is it
> > possible for you to try 2.5.69-mm4?
>
> Russell's patches do not address this.
still i'm going to give them a spin a bit later.
> Individual PCMCIA drivers need to be updated to call
> thier release function directly when processing a
> CARD_RELEASE message instead of from a timer procedure.
>
> Similar to this patch for synclink_cs.c:
...
> - mod_timer(&link->release, jiffies + HZ/20);
> + mgslpc_release((u_long)link);
Tried that. This time the trace looks different:
Debug: sleeping function called from illegal context at include/asm/semaphore.h:119
Call Trace:
[<c0118bc8>] __might_sleep+0x58/0x70
[<c6a31eb6>] +0x82/0x58c [pcmcia_core]
[<c6a2d193>] undo_irq+0x23/0x90 [pcmcia_core]
[<c6a31eb6>] +0x82/0x58c [pcmcia_core]
[<c6a302f8>] pcmcia_release_irq+0xb8/0xe0 [pcmcia_core]
[<c6a25e00>] pcnet_release+0x0/0x80 [pcnet_cs]
[<c6a312d5>] CardServices+0x155/0x260 [pcmcia_core]
[<c6a312c9>] CardServices+0x149/0x260 [pcmcia_core]
[<c6a25e56>] pcnet_release+0x56/0x80 [pcnet_cs]
[<c01224a4>] run_timer_softirq+0xc4/0x1a0
[<c010a8b3>] handle_IRQ_event+0x33/0xf0
[<c011e889>] do_softirq+0xa9/0xb0
[<c010abb5>] do_IRQ+0x125/0x150
[<c01093a8>] common_interrupt+0x18/0x20
[<c013cfb6>] zap_pte_range+0xd6/0x1d0
[<c013d0f3>] zap_pmd_range+0x43/0x70
[<c013d153>] unmap_page_range+0x33/0x60
[<c013d271>] unmap_vmas+0xf1/0x260
[<c01412d5>] exit_mmap+0x65/0x180
[<c0119196>] mmput+0x56/0xb0
[<c01556ce>] exec_mmap+0xce/0x150
[<c01557e8>] flush_old_exec+0x18/0x830
[<c01555ea>] kernel_read+0x3a/0x50
[<c0170483>] load_elf_binary+0x283/0xba0
[<c01316fd>] generic_file_aio_read+0x3d/0x50
[<c0134379>] buffered_rmqueue+0xc9/0x160
[<c0170200>] load_elf_binary+0x0/0xba0
[<c015639b>] search_binary_handler+0xcb/0x2d0
[<c01566f9>] do_execve+0x159/0x1a0
[<c0157d28>] getname+0x78/0xc0
[<c0107a46>] sys_execve+0x36/0x70
[<c0109187>] syscall_call+0x7/0xb
next prev parent reply other threads:[~2003-05-13 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 13:57 2.5.69+bk: "sleeping function called from illegal context" on card release while shutting down Alex Riesen
2003-05-13 14:58 ` Felipe Alfaro Solana
2003-05-13 15:31 ` Paul Fulghum
2003-05-13 16:08 ` Russell King
2003-05-13 17:21 ` Alex Riesen [this message]
2003-05-13 17:28 ` Paul Fulghum
2003-05-13 17:33 ` Alex Riesen
2003-05-13 21:52 ` Felipe Alfaro Solana
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 18:46 Alex Riesen
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=20030513172114.GH32559@Synopsys.COM \
--to=alexander.riesen@synopsys.com \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.com \
--cc=rmk@arm.linux.org.uk \
/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