From: Kumar Gala <galak@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Michael Buesch <mbuesch@freenet.de>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: PowerPC: Sleeping function called from invalid context at emulate_instruction()
Date: Wed, 22 Feb 2006 22:22:17 -0600 [thread overview]
Message-ID: <7A04DCF5-C5CF-46E2-A133-A7743BD83B17@kernel.crashing.org> (raw)
In-Reply-To: <200602222129.31700.mbuesch@freenet.de>
On Feb 22, 2006, at 2:29 PM, Michael Buesch wrote:
> Hi,
>
> On a powerPC 32bit, I got the following debugging assertion failure:
>
> [ 733.209827] Debug: sleeping function called from invalid context
> at arch/powerpc/kernel/traps.c:697
> [ 733.210682] in_atomic():0, irqs_disabled():1
> [ 733.211347] Call Trace:
> [ 733.211969] [D6023EB0] [C0007F84] show_stack+0x58/0x174
> (unreliable)
> [ 733.212765] [D6023EE0] [C0022C34] __might_sleep+0xbc/0xd0
> [ 733.213523] [D6023EF0] [C000D158] program_check_exception
> +0x1d8/0x4fc
> [ 733.214309] [D6023F40] [C000E744] ret_from_except_full+0x0/0x4c
> [ 733.215076] --- Exception: 700 at 0x102a7100
> [ 733.215785] LR = 0xdb9ef04
>
> It is caused by the line
> if (get_user(instword, (u32 __user *)(regs->nip)))
> in arch/powerpc/kernel/traps.c:emulate_instruction()
>
> I am not sure, if this is an indication for a bug, or just false
> alarm.
> In case of false alarm, the debugging message should be made quiet
> somehow, though.
Paul,
Last time this was brought up we left it wondering why you had made
program_check_exception() run with interrupts disabled. Any further
ideas on that one?
- kumar
next prev parent reply other threads:[~2006-02-23 4:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 20:29 PowerPC: Sleeping function called from invalid context at emulate_instruction() Michael Buesch
2006-02-23 4:22 ` Kumar Gala [this message]
2006-02-23 22:57 ` Paul Mackerras
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=7A04DCF5-C5CF-46E2-A133-A7743BD83B17@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mbuesch@freenet.de \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).