From owner-freebsd-hardware@FreeBSD.ORG Sun Nov 30 15:24:43 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E5E81065677; Sun, 30 Nov 2008 15:24:43 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout2.freenet.de (mout2.freenet.de [IPv6:2001:748:100:40::2:4]) by mx1.freebsd.org (Postfix) with ESMTP id 001F58FC16; Sun, 30 Nov 2008 15:24:42 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.12] (helo=2.mx.freenet.de) by mout2.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #65) id 1L6oA4-0000Ob-50; Sun, 30 Nov 2008 16:24:40 +0100 Received: from mafd5.m.pppool.de ([89.49.175.213]:10239 helo=ernst.jennejohn.org) by 2.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #68) id 1L6oA3-0000yI-Rf; Sun, 30 Nov 2008 16:24:40 +0100 Date: Sun, 30 Nov 2008 16:24:37 +0100 From: Gary Jennejohn To: Andriy Gapon Message-ID: <20081130162437.1bae4371@ernst.jennejohn.org> In-Reply-To: <492FF203.5060405@icyb.net.ua> References: <492FF203.5060405@icyb.net.ua> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: dd if=/dev/mem can hang a machine? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Nov 2008 15:24:43 -0000 On Fri, 28 Nov 2008 15:28:35 +0200 Andriy Gapon wrote: > > I have a new machine with DG33TL mainboard (ICH9/G33). > In a course of some hacking I ran dd if=/dev/mem ... to scan all memory, > this caused the machine to hang. > I tried to reproduce and this is 100% reproducible. > > I am not used to such behavior. In older days I could scan all the > memory without any issues. > > Could this be related to some modern form of memory-mapped IO? Or to > Intel Management Engine (that seems t bite into DRAM)? > Or something else? > > Just wondering. > That's what I would assume. With some hardware just reading a register can be harmful. --- Gary Jennejohn