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:	Tue, 19 Jun 2007 19:44:07 -0400
From:	Dave Jones <davej@...hat.com>
To:	Carlo Wood <carlo@...noe.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, eric@...olt.net,
	zhenyu.z.wang@...el.com, lethal@...ux-sh.org, y-goto@...fujitsu.com
Subject: Re: 2.6.22-rc5 regression

On Wed, Jun 20, 2007 at 01:37:16AM +0200, Carlo Wood wrote:

 > Personally I am convinced that the real problem is with
 > 8888985144db8f4cb7e56154b31bdf233d3550bf
 > 
 >     [AGPGART] intel_agp: fix device probe
 >     
 >     This patch trys to fix device probe in two cases. First we should
 >     correctly detect device if integrated graphics device is not enabled
 >     or exists, like an add-in card is plugged. Second on some type of intel
 >     GMCH, it might have multiple graphic chip models, like 945GME case, so
 >     we should be sure the detect works through the whole table.
 >     
 >     Signed-off-by: Wang Zhenyu <zhenyu.z.wang@...el.com>
 >     Signed-off-by: Dave Jones <davej@...hat.com>
 > 
 > 
 > The result of this patch is that the kernel starts to print
 > "agpgart: Detected an Intel 965G Chipset." again with the usual
 > disastrous results. Now, that doesn't mean that this patch is
 > wrong - but it explains why the problem returns after this patch.

Right, without this patch, probing was broken, so we never matched
an agp driver to the chipset.  The question remains though, why
the initialisation of the chip is so broken.

	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