linux-kernel - Re: [AGPGART] intel_agp: use table for device probe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4676C3F5.5070501@redhat.com>
Date:	Mon, 18 Jun 2007 13:42:13 -0400
From:	Chuck Ebbert <cebbert@...hat.com>
To:	Carlo Wood <carlo@...noe.com>, Dave Airlie <airlied@...il.com>,
	Dave Jones <davej@...hat.com>, linux-kernel@...r.kernel.org,
	eric@...olt.net
Subject: Re: [AGPGART] intel_agp: use table for device probe

On 06/17/2007 10:37 PM, Wang Zhenyu wrote:
> On 2007.06.18 03:56:36 +0000, Carlo Wood wrote:
>> On Mon, Jun 18, 2007 at 10:57:38AM +1000, Dave Airlie wrote:
>>>> Right now, I'm at a loss to explain the corruption, so it's
>>>> difficult to suggest what to try.
>>> The thing is here, this is PCIE, so if there is a GPU plugged into the
>>> PCIE 16x slot in theory the main onboard graphics should disable, AGP
>>> code is used to control the GART for the onboard chip, in this case a
>>> plugged in card will  not use AGP, I wonder have Intel tested with a
>>> pcie card in place...
> 
> Agree. We seem to always enable AGP even IGD is disabled or not exists,
> other card should not depend on this module ever.
> 
>> That is Chinese for me :/.
>> Do you want me to try something?
> 
> Carlo, I've just built latest kernel git tree on a Dell 965G box and
> have a NV card plugged-in. It boots fine.
> 
> Linux agpgart interface v0.102 (c) Dave Jones
> agpgart: Detected an Intel 965G Chipset.
> agpgart: AGP aperture is 256M @ 0x0
> 
> I don't know why it hangs your machine when loading this module, it should
> just not bother anything. But from your last "modprobe: ..." line, it seems
> there's really badness somewhere, do you have serial console to see more
> in the message?

There are also these bug reports:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229913
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242101
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/