Messages in this thread | | | Date | Tue, 19 Aug 2003 01:13:16 +0100 | From | Dave Jones <> | Subject | Re: Debug: sleeping function called from invalid context |
| |
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..
Dave
-- Dave Jones http://www.codemonkey.org.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |