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]
Date:	Sun, 17 Jun 2007 16:49:04 -0400
From:	Dave Jones <davej@...hat.com>
To:	Carlo Wood <carlo@...noe.com>, linux-kernel@...r.kernel.org,
	eric@...olt.net, zhenyu.z.wang@...el.com
Subject: Re: [AGPGART] intel_agp: use table for device probe

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
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ