Re: agpgart problem on 2.4.0-ac1

From: Manfred (manfred@colorfullife.com)
Date: Fri Jan 05 2001 - 06:32:52 EST

Next message: Stephen C. Tweedie: "Re: [Ext2-devel] Re: [RFC] ext2_new_block() behaviour"
Previous message: Arjan van de Ven: "Re: IEEE1394 2.4.0 (final) compile problems"
Maybe in reply to: Narancs 1: "agpgart problem on 2.4.0-ac1"
Next in thread: Alan Cox: "Re: agpgart problem on 2.4.0-ac1"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> EIP: 0010:[<00000000>]
> Call Trace: [<c8829bb0>] [<c8827000>] [<c8827068>] [<c8829d50>]
> [<c882aa00>] [<c8827000>] [<c01156cd>]
> [<c8820000>] [<c8827060>] [<c0108d5f>]
>
> Code: Bad EIP value.

Could you parse your oops through ksymoops?

Probably someone called an uninitialized function pointer, or there was
a stack overrun.

--
	Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Next message: Stephen C. Tweedie: "Re: [Ext2-devel] Re: [RFC] ext2_new_block() behaviour"
Previous message: Arjan van de Ven: "Re: IEEE1394 2.4.0 (final) compile problems"
Maybe in reply to: Narancs 1: "agpgart problem on 2.4.0-ac1"
Next in thread: Alan Cox: "Re: agpgart problem on 2.4.0-ac1"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Jan 07 2001 - 21:00:21 EST