From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Dave Jones <davej@redhat.com>
Cc: mpm@selenic.com, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Debug: sleeping function called from invalid context
Date: Mon, 18 Aug 2003 17:15:02 -0700 [thread overview]
Message-ID: <20030818171502.65d40693.rddunlap@osdl.org> (raw)
In-Reply-To: <20030819001316.GF22433@redhat.com>
On Tue, 19 Aug 2003 01:13:16 +0100 Dave Jones <davej@redhat.com> wrote:
| On Mon, Aug 18, 2003 at 02:07:29PM -0700, Randy.Dunlap wrote:
| > | > | > Debug: sleeping function called from invalid context at include/asm/uaccess.h:473
| > | > | > Call Trace:
| > | > | > [<c0120d94>] __might_sleep+0x54/0x5b
| > | > | > [<c010d001>] save_v86_state+0x71/0x1f0
| > | > | > [<c010dbd5>] handle_vm86_fault+0xc5/0xa90
| > | > | > [<c019cab8>] ext3_file_write+0x28/0xc0
| > | > | > [<c011cd96>] __change_page_attr+0x26/0x220
| > | > | > [<c010b310>] do_general_protection+0x0/0x90
| > | > | > [<c010a69d>] error_code+0x2d/0x40
| > | > | > [<c0109657>] syscall_call+0x7/0xb
| > | > |
| >
| > I had another occurrence of this yesterday. It doesn't seem to be
| > an error condition AFAICT.
|
| How spooky. now I got one too, (minus the noise).
|
| Call Trace:
| [<c0120022>] __might_sleep+0x5b/0x5f
| [<c010cf8a>] save_v86_state+0x6a/0x1f3
| [<c010dad2>] handle_vm86_fault+0xa7/0x897
| [<c010b2ed>] do_general_protection+0x0/0x93
| [<c010a651>] error_code+0x2d/0x38
| [<c0109623>] syscall_call+0x7/0xb
|
| By the looks of the logs, it happened as I restarted X, as theres
| a bunch of mtrr messages right after this..
I don't recall mtrr messages, but it is happening just after I start
X and the window manager with me also.
--
~Randy
"Everything is relative."
next prev parent reply other threads:[~2003-08-19 0:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 17:18 Debug: sleeping function called from invalid context Randy.Dunlap
2003-08-15 17:32 ` Dave Jones
2003-08-15 17:42 ` Randy.Dunlap
2003-08-15 19:30 ` Randy.Dunlap
2003-08-16 7:06 ` Matt Mackall
2003-08-18 21:07 ` Randy.Dunlap
2003-08-18 21:26 ` Matt Mackall
2003-08-19 0:13 ` Dave Jones
2003-08-19 0:15 ` Randy.Dunlap [this message]
2003-08-19 1:02 ` Zwane Mwaikambo
2003-08-19 0:15 ` Andrew Morton
2003-08-19 1:27 ` Matt Mackall
2003-08-19 3:24 ` Randy.Dunlap
2003-08-19 3:35 ` Andrew Morton
2003-08-19 3:39 ` Randy.Dunlap
2003-08-19 4:26 ` Matt Mackall
2003-08-19 4:29 ` Andrew Morton
2003-08-19 4:14 ` Matt Mackall
2003-08-19 5:14 ` Matt Mackall
2003-08-19 1:01 ` Matt Mackall
2003-08-19 1:04 ` Dave Jones
2003-08-19 1:09 ` Matt Mackall
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=20030818171502.65d40693.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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).