From owner-freebsd-current Sat Jan 23 19:09:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27719 for freebsd-current-outgoing; Sat, 23 Jan 1999 19:09:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27714 for ; Sat, 23 Jan 1999 19:09:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id TAA57441; Sat, 23 Jan 1999 19:08:49 -0800 (PST) (envelope-from dillon) Date: Sat, 23 Jan 1999 19:08:49 -0800 (PST) From: Matthew Dillon Message-Id: <199901240308.TAA57441@apollo.backplane.com> To: Peter Wemm Cc: N , current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 References: <199901240213.KAA01206@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On my system I can understand it, it's a 2xP5 with a shared L2 cache on a :Neptune chipset - something that isn't known for speed. Once you get two :processors hammering the system bus, *plus* mix in an EISA scsi :controller, I could well imagine the memory bus getting thrashed. When we started throwing together Duel-P-II machines, we basically had to throw away our DEC chipset cards... I think that the DEC chip cards, at least the older ones, have serious PCI spec bugs that cause them to operate incorrectly on duel-cpu machines when more then one cpu is populated. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message