Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 1 Apr 2005 22:01:04 -0800
From:      Astrodog <astrodog@gmail.com>
To:        freebsd-amd64@freebsd.org
Subject:   Re: Tyan k8sr lockups
Message-ID:  <2fd864e05040122013d8fd812@mail.gmail.com>
In-Reply-To: <20050401201907.U95587@carver.gumbysoft.com>
References:  <f0111a98c01333b3c306c81d10294de4@khera.org> <Pine.SOC.4.61.0503300229560.3181@tea.blinkenlights.nl> <424C215E.5080201@infotechfl.com> <424C4EED.5070601@infotechfl.com> <424D58F7.1010005@infotechfl.com> <424DA4B3.3070703@infotechfl.com> <20050401201907.U95587@carver.gumbysoft.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 1, 2005 8:26 PM, Doug White <dwhite@gumbysoft.com> wrote:
> On Fri, 1 Apr 2005, Gary Mu1der wrote:
> 
> > I have isolated the crash to the following dd command:
> >
> >       dd if=/dev/mem of=/dev/null bs=1024k skip=4040 count=1
> 
> Reading from random places in /dev/mem will cause unpredicatable behavior.
> Memory at that offset is in PCI memory-mapped device space, and reading
> from there may disrupt the PCI bridge, enable or disable interrupts, or
> worse.
> 
> --

I think the basic idea here is that dd'ing from /dev/mem may or may
not work, on any given hardware, and is certainly not reccomended. If
you want to test this "Safely", do an mdconfig, and dd onto, or from
the md device.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2fd864e05040122013d8fd812>