This is a reissue of an earlier report, and I've since done some more digging.
Up to kernel 2.4.20-pre2 there was no problem, agpgart et al ran fine etc,
but from 2.4.20-pre4 onwards when Xwindows starts to load these modules
I am instantly thrown back to a booting machine.
The same kernels on a VIA MVP3 chipset box with a Matrox G200 are fine.
I have ascertained that any attempt to use agpgart triggers it.
Rather than clutter up the list with lots of log files, I've made a web page at
http://www.users.bigpond.com/allan.d/bug/Matrox.html
with all the info I could gather.
Any suggestions of how to improve the error messages around the failure point
are welcome. Nothing is written into dmesg at the time of failure.
On Thu, 12 Sep 2002, Allan Duncan wrote:
> This is a reissue of an earlier report, and I've since done some more digging.
>
> Up to kernel 2.4.20-pre2 there was no problem, agpgart et al ran fine etc,
> but from 2.4.20-pre4 onwards when Xwindows starts to load these modules
> I am instantly thrown back to a booting machine.
> The same kernels on a VIA MVP3 chipset box with a Matrox G200 are fine.
>
> I have ascertained that any attempt to use agpgart triggers it.
>
> Rather than clutter up the list with lots of log files, I've made a web page at
> http://www.users.bigpond.com/allan.d/bug/Matrox.html
> with all the info I could gather.
>
> Any suggestions of how to improve the error messages around the failure point
> are welcome. Nothing is written into dmesg at the time of failure.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Might be good to check with a previous bug report I posted if there are
any similarities. My problem is that the kernel panics when opengl is used
when I have some highmem available.
On Thu, Sep 12, 2002 at 11:56:20AM +1000, Allan Duncan wrote:
> This is a reissue of an earlier report, and I've since done some more digging.
>
> Up to kernel 2.4.20-pre2 there was no problem, agpgart et al ran fine etc,
> but from 2.4.20-pre4 onwards when Xwindows starts to load these modules
> I am instantly thrown back to a booting machine.
> The same kernels on a VIA MVP3 chipset box with a Matrox G200 are fine.
>
> I have ascertained that any attempt to use agpgart triggers it.
>
I've seen the same thing with 2.4.20-pre5-ac1, and I'm just building
pre5-aa2 to see if there's any difference. This is with an AMD 751
system (an Asus K7M), an original Radeon, and the DRI CVS code. I
couldn't get any log messages out of it, though.
Simon
--
PGP public key Id 0x144A991C, or ftp://bg77.anu.edu.au/pub/himi/himi.asc
(crappy) Homepage: http://bg77.anu.edu.au
doe #237 (see http://www.lemuria.org/DeCSS)
My DeCSS mirror: ftp://bg77.anu.edu.au/pub/mirrors/css/
Allan Duncan <[email protected]> writes:
>
> Any suggestions of how to improve the error messages around the failure point
> are welcome. Nothing is written into dmesg at the time of failure.
You're booting with mem=nopentium right ? It should go away when you turn
that off. I'm working on a fix. You can safely turn it off for now, the
old problems that it worked around are fixed.
-Andi
On Thu, Sep 12, 2002 at 11:50:19AM +0200, Andi Kleen wrote:
> Allan Duncan <[email protected]> writes:
> >
> > Any suggestions of how to improve the error messages around the failure point
> > are welcome. Nothing is written into dmesg at the time of failure.
>
> You're booting with mem=nopentium right ? It should go away when you turn
> that off. I'm working on a fix. You can safely turn it off for now, the
> old problems that it worked around are fixed.
>
The problem goes away without mem=nopentium - I've just booted into
2.4.20-pre5aa2 and fired up X.
Simon
--
PGP public key Id 0x144A991C, or ftp://bg77.anu.edu.au/pub/himi/himi.asc
(crappy) Homepage: http://bg77.anu.edu.au
doe #237 (see http://www.lemuria.org/DeCSS)
My DeCSS mirror: ftp://bg77.anu.edu.au/pub/mirrors/css/