Re: [AGPGART] intel_agp: use table for device probe

[Dave Jones <davej@redhat.com>]

On Sun, Jun 17, 2007 at 09:59:01PM +0200, Carlo Wood wrote:
 > On Sun, Jun 17, 2007 at 03:07:14PM -0400, Dave Jones wrote:
 > > Sometimes things fall through the cracks..
 > > I haven't heard any similar problems, which makes it somewhat odd.
 > 
 > Ok. Well, the lockup is all to real here :p
 > 
 > I suspect a memory corruption going on, as under certain circumstances
 > there is printed more after the "agpgart: Detected an Intel 965G
 > Chipset." -- that is, the kernel *sometimes* doesn't hang silently,
 > but either reboots by itself (hard reset) or prints something
 > that looks like a total crash to me. Often, this is prefixed by
 > the name of running process. I am sorry, I never wrote any of that
 > down. Only the last time, it then went like:
 > 
 > agpgart: Detected an Intel 965G Chipset.
 > modprobe: Corrupt page table at address 20
 > PGD 178c6c067 PUD 201000c0049c04f BAD

That's pretty bad corruption indeed.  What I'm puzzling over though
is why other 965G users aren't seeing the same thing.
My own 965G seems to be fine, though that's using Intel graphics
instead of nvidia.

(Just to rule it out, I'm assuming at this stage in boot that the
 nvidia driver module has never been loaded?)

And if you never load the agpgart modules, you never see lockups?

Right now, I'm at a loss to explain this.

	Dave

-- 
http://www.codemonkey.org.uk