|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] agpgart and i830M Chipset problem
Hi,
here's a bit from dmesg:
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 150M
agpgart: Detected an Intel(R) 830M Chipset.
invalid operand: 0000
CPU: 0
EIP: 0819:[<c022d22c>] Not tainted
EFLAGS: 00213207
eax: c04f6000 ebx: c04f6ca0 ecx: 01000000 edx: 00000328
esi: 00000000 edi: 00000000 ebp: 00000001 esp: ca871e88
ds: 0821 es: 0821 ss: 0821
Process modprobe.moduti (pid: 292, stackpage=ca871000)<1>
Stack: 00000001 c0406540 c01233fb ca364000 c11c154c 00000000 00000000 00000001
c022d52e c11c154c 00000073 ca871eb8 00000000 c11c154c 00000000 00000000
00000000 cc46ffe5 c11c154c 00000001 00000073 00000063 cc473e96 ca871f14
Call Trace: [<c01233fb>] [<c022d52e>] [<cc46ffe5>]
[<cc473e96>] [<cc474000>] [<cc474ec0>] [<c010a030>] [<cc46e060>]
[<c022481f>]
this happens with 2.4.27-based xen0, with non-xen enabled 2.4.27 everything
is fine.
Should I expect problems on other agpgart modules ( for example, are
radeons known to work? ).
--
Dariush Pietrzak,
Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] agpgart and i830M Chipset problem,
xen <=
|
|
|
|
|