From: "Diego Calleja García" <aradorlinux@yahoo.es>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test4-mm4
Date: Mon, 1 Sep 2003 03:11:12 +0200 [thread overview]
Message-ID: <20030901031112.17a98baf.aradorlinux@yahoo.es> (raw)
In-Reply-To: <20030830161536.7e7be6d3.akpm@osdl.org>
El Sat, 30 Aug 2003 16:15:36 -0700 Andrew Morton <akpm@osdl.org> escribió:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test4/2.6.0-test4-mm4/
I've been getting this warnings randomly since a few kernels. (sadly, i don't
know when they started)
Sep 1 02:39:33 estel modprobe: FATAL: Module apm not found.
Sep 1 02:39:34 estel kernel: Debug: sleeping function called from invalid context at include/asm/uaccess.h:512
Sep 1 02:39:34 estel kernel: Call Trace:
Sep 1 02:39:34 estel kernel: [__might_sleep+97/128] __might_sleep+0x61/0x80
Sep 1 02:39:34 estel kernel: [save_v86_state+110/544] save_v86_state+0x6e/0x220
Sep 1 02:39:34 estel kernel: [handle_vm86_fault+183/2576] handle_vm86_fault+0xb7/0xa10
Sep 1 02:39:34 estel kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20
Sep 1 02:39:34 estel kernel: [__copy_from_user_ll+68/112] __copy_from_user_ll+0x44/0x70
Sep 1 02:39:34 estel kernel: [do_general_protection+0/160] do_general_protection+0x0/0xa0
Sep 1 02:39:34 estel kernel: [error_code+47/56] error_code+0x2f/0x38
Sep 1 02:39:34 estel kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Sep 1 02:39:34 estel kernel: [inet_fill_ifaddr+123/672] inet_fill_ifaddr+0x7b/0x2a0
Sep 1 02:39:34 estel kernel:
[...]
Sep 1 02:39:53 estel modprobe: FATAL: Module apm not found.
Sep 1 02:39:53 estel kernel: Debug: sleeping function called from invalid context at include/asm/uaccess.h:512
Sep 1 02:39:53 estel kernel: Call Trace:
Sep 1 02:39:53 estel kernel: [__might_sleep+97/128] __might_sleep+0x61/0x80
Sep 1 02:39:53 estel kernel: [save_v86_state+110/544] save_v86_state+0x6e/0x220
Sep 1 02:39:53 estel kernel: [handle_vm86_fault+183/2576] handle_vm86_fault+0xb7/0xa10
Sep 1 02:39:53 estel kernel: [kernel_text_address+59/80] kernel_text_address+0x3b/0x50
Sep 1 02:39:53 estel kernel: [do_general_protection+0/160] do_general_protection+0x0/0xa0
Sep 1 02:39:53 estel kernel: [error_code+47/56] error_code+0x2f/0x38
Sep 1 02:39:53 estel kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Sep 1 02:39:53 estel kernel: [inet_fill_ifaddr+123/672] inet_fill_ifaddr+0x7b/0x2a0
Sep 1 02:39:53 estel kernel:
I though they happened randonmly. But I realisedI've a
"modprobe: FATAL: Module apm not found."
just before them. I'll try to track down the responsible userspace app causing
this behaviour (and do a better bug report).
next prev parent reply other threads:[~2003-09-01 1:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-30 23:15 2.6.0-test4-mm4 Andrew Morton
2003-08-31 14:41 ` 2.6.0-test4-mm4 Thomas Molina
2003-08-31 15:44 ` 2.6.0-test4-mm4 Zwane Mwaikambo
2003-09-01 1:11 ` Diego Calleja García [this message]
2003-09-02 17:27 ` 2.6.0-test4-mm4 Diego Calleja García
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=20030901031112.17a98baf.aradorlinux@yahoo.es \
--to=aradorlinux@yahoo.es \
--cc=akpm@osdl.org \
--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®