From: Matt Mackall <mpm@selenic.com>
To: Stig Brautaset <stig@brautaset.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test3: Debug: sleeping function called from invalid context at include/asm/uaccess.h:473
Date: Sun, 10 Aug 2003 15:48:28 -0500 [thread overview]
Message-ID: <20030810204828.GA31810@waste.org> (raw)
In-Reply-To: <20030810161951.GA1009@brautaset.org>
On Sun, Aug 10, 2003 at 05:19:51PM +0100, Stig Brautaset wrote:
> Hi, I just got this message on a 2.6.0-test3 kernel:
>
> Debug: sleeping function called from invalid context at include/asm/uaccess.h:473
> Call Trace:
> [<c0117c01>] __might_sleep+0x61/0x80
> [<c010ba18>] save_v86_state+0x68/0x210
> [<c01362f5>] generic_file_aio_write+0x85/0xb0
> [<c010c547>] handle_vm86_fault+0xb7/0xa10
> [<c0181a2f>] ext3_file_write+0x3f/0xd0
> [<c010a330>] do_general_protection+0x0/0xa0
> [<c0109625>] error_code+0x2d/0x38
> [<c010947b>] syscall_call+0x7/0xb
>
> I'm unsure what other information is needed, if any.
> I'm not on list, so CC me on replies please.
This looks like the vm86 fault I described earlier. For some reason
vm86 mode writes part of its state out to userspace in its fault
handler and I can't find anything that guarantees that won't double
fault. Anyone?
It might be useful to know what video driver you're using and whether
or not you use Wine, Dosemu, or anything similar. Being able to
reproduce it easily would be handy too.
--
Matt Mackall : http://www.selenic.com : of or relating to the moon
next prev parent reply other threads:[~2003-08-10 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-10 16:19 Stig Brautaset
2003-08-10 20:48 ` Matt Mackall [this message]
2003-08-10 21:45 ` Stig Brautaset
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=20030810204828.GA31810@waste.org \
--to=mpm@selenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stig@brautaset.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®