From owner-freebsd-amd64@FreeBSD.ORG Wed Jul 27 17:27:31 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5FCD16A41F for ; Wed, 27 Jul 2005 17:27:31 +0000 (GMT) (envelope-from gmulder@infotechfl.com) Received: from pigeon.infotechfl.com (mailrelay.infotechfl.com [209.251.147.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F84A43D88 for ; Wed, 27 Jul 2005 17:27:30 +0000 (GMT) (envelope-from gmulder@infotechfl.com) Received: from [172.20.0.75] (gmulder.infotechfl.com [172.20.0.75]) by pigeon.infotechfl.com (8.11.6/8.11.6) with ESMTP id j6RHRT327949; Wed, 27 Jul 2005 13:27:30 -0400 Message-ID: <42E7C454.8080404@infotechfl.com> Date: Wed, 27 Jul 2005 13:28:52 -0400 From: Gary Mu1der User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <200507270814.j6R8E2Mc006780@peedub.jennejohn.org> In-Reply-To: <200507270814.j6R8E2Mc006780@peedub.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Tyan S2885 Thunder K8W lockups X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2005 17:27:31 -0000 Gary Jennejohn wrote: > NAKATA Maho writes: > >>How to lockup: >># dd if=/dev/mem of=/dev/null bs=1024k >>about 50 seconds later it lockups. 100% reproducible. >>* Both Optimal/Failsafe setting in BIOS >>* Both MTRR Mapping Continuous/Disabled >>* set hw.physmem="4G" doesn't help >> >>workaround: >>on board GbE (bge0) and SATA disabled. >> >>any hints or comments? >> > > > I could be wrong, but it seems to me that you might be accessing HW > address space with resulting undesirable side effects since you're > trying to read the entire range which /dev/mem maps. I can confirm I tried the same thing and got the same result with similar hardware. It was also pointed out to me that reading indiscriminately from /dev/mem may screw up memory mapped I/O and likely cause a crash. Gary