From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: kbugs@pelvoux.nildram.co.uk
Subject: [Bug 1339] New: sleeping function called from invalid context
Date: Fri, 10 Oct 2003 08:10:16 -0700 [thread overview]
Message-ID: <200010000.1065798616@[10.10.2.4]> (raw)
Summary: sleeping function called from invalid context
Kernel Version: 2.6.0-test6
Status: NEW
Severity: normal
Owner: akpm@digeo.com
Submitter: kbugs@pelvoux.nildram.co.uk
Distribution: Debian Sarge
Hardware Environment:
Gateway PC, Intel Pentium III (Katmai) 450Mhz, Intel 440BX Chipset, 640Mb RAM
Software Environment:
Gnu C 3.3.2
Gnu make 3.80
util-linux 2.12
mount 2.12
e2fsprogs 1.35-WIP
nfs-utils 1.0.5
Linux C Library 2.3.2
Dynamic linker (ldd) 2.3.2
Procps 3.1.12
Net-tools 1.60
Console-tools 0.2.3
Sh-utils 5.0
Modules Loaded nfsd exportfs lockd sunrpc reiserfs 8250 serial_core
eepro100 mii rtc
Problem Description:
The following message appeared on the system log:
Debug: sleeping function called from invalid context at include/asm/uaccess.h:473
in_atomic():0, irqs_disabled():1
Call Trace:
[<c011bd58>] __might_sleep+0x88/0x90
[<c010c55f>] save_v86_state+0x6f/0x1f0
[<c010d017>] handle_vm86_fault+0xb7/0xa10
[<c0141e21>] do_no_page+0x191/0x2f0
[<c0140fc6>] zeromap_pte_range+0x36/0x70
[<c010b070>] do_general_protection+0x0/0xa0
[<c010a399>] error_code+0x2d/0x38
[<c010a1ef>] syscall_call+0x7/0xb
Steps to reproduce:
I don't have a method to reproduce - this just appeared in the log.
next reply other threads:[~2003-10-10 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 15:10 Martin J. Bligh [this message]
2003-10-11 5:35 ` Matt Mackall
[not found] <200010000.1065798616@[10.10.2.4].suse.lists.linux.kernel>
2003-10-10 15:33 ` Andi Kleen
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='200010000.1065798616@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=kbugs@pelvoux.nildram.co.uk \
--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 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®