From: Dave Jones <davej@redhat.com>
To: Wakko Warner <wakko@animx.eu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Illegal instruction with gl
Date: Sat, 24 Jan 2004 15:42:49 +0000 [thread overview]
Message-ID: <20040124154249.GA2499@redhat.com> (raw)
In-Reply-To: <20040124103919.A7924@animx.eu.org>
On Sat, Jan 24, 2004 at 10:39:19AM -0500, Wakko Warner wrote:
> Just to add to the below, I disabled acpi, highmem, smp, and preempt. Same
> problem. I also tried 2.4.24 kernel, same results.
>
> I modified agpgart on 2.4.24 to use generic intel init which didn't change
> anything.
>
> This is the first system with an intel E7505 I've used so I don't know if
> it's a board problem or a kernel problem. Or if it's with the matrox g400.
>
> Here's the kernel messages for agp/drm from 2.6.1 (everything enabled that I
> disabled):
> agpgart: Detected an Intel E7505 Chipset.
> agpgart: Maximum main memory to use for agp memory: 941M
> agpgart: AGP aperture is 32M @ 0xf8000000
> [drm] Initialized mga 3.1.0 20021029 on minor 0
> agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
> agpgart: Device is in legacy mode, falling back to 2.x
> agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
> agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
>
> I placed some files in:
> http:// veg.animx.eu.org/e7505/
> with some extra information (config, full dmesg, lspci -v)
I see no evidence that this is an agpgart problem. When that does something
wrong, you usually end up with either a system lockup, or massive memory
corruption. Apps segfaulting would suggest to me that you have a problem with
your X GL libraries.
You may have more luck asking the folks at dri-devel@lists.sf.net about it.
Dave
next prev parent reply other threads:[~2004-01-24 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 23:15 Illegal instruction with gl Wakko Warner
2004-01-24 15:39 ` Wakko Warner
2004-01-24 15:42 ` Dave Jones [this message]
2004-01-24 16:12 ` Wakko Warner
2004-01-24 23:32 ` [SOLVED] " Wakko Warner
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=20040124154249.GA2499@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wakko@animx.eu.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