On Fri, Nov 15, 2002 at 11:45:16AM -0500, Robert Watson <[EMAIL PROTECTED]> wrote:
> Does this apply generally to all P4's, or just a subset? If all, it may > be we want to add a P4-workaround to GENERIC so that P4's work better ouf > of the box. If it's a select few, I wonder if there's some way to test > for the problem early in the boot... > > One of the recurring themes here has (a) been P4 processors, and (b) been > a fear that because of timing changes introduced by the DISABLE_FOO flags, > the real bug is still there, but less visible in the tests people are > running. Certainly doesn't happen on my P3-500 SMP system. I've finished two buildworlds without any problems. As everyone seems to think that it happens only on P4's, I'm not going to try it on old P2-400. That's all I can provide, happens reliably (for months now) on my P4 and doesn't happen with P3. 5.0-RELEASE definitely needs a fix. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
