public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: "Anton D. Kachalov" <mouse@mayc.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reading /dev/mem by dd
Date: Wed, 11 Nov 2009 15:09:54 -0600	[thread overview]
Message-ID: <4AFB2822.30906@gmail.com> (raw)
In-Reply-To: <4AFACC03.7080209@mayc.ru>

On 11/11/2009 08:36 AM, Anton D. Kachalov wrote:
> Hello everyone!
>
> I've found strange behavior of reading /dev/mem:
>
> for i in 0 1 2; do
> echo $i
> dd if=/dev/mem of=/dev/null skip=$((6+$i)) bs=$((0x20000000)) count=1
> done
>
> On some systems with Supermicro X8DTU I've got several messages during
> first 512Mb starting from 0xc000_0000:
>
> "BUG: soft lockup - CPU#xx stuck for 61s!"
>
> On other systems with the sameboard I've stuck without any errors at
> last 10Mb before 0x1_0000_0000. Local APIC access?
>
> On E5440 (Dell PowerEdge 1950) I've just got several:
> APIC error on CPU3: 00(80)
> APIC error on CPU3: 80(80)
> ...
> APIC error on CPU3: 80(80)
> That looks like wrong register access.

I don't think that we prevent any access to device registers in /dev/mem 
- if you read something that has side effects and something breaks, well 
I guess you get to keep both pieces :-) There's a reason it's root-only..

  parent reply	other threads:[~2009-11-11 21:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 14:36 Reading /dev/mem by dd Anton D. Kachalov
2009-11-11 16:20 ` Américo Wang
2009-11-12 15:46   ` Anton D. Kachalov
2009-11-11 21:09 ` Robert Hancock [this message]
2009-11-12  2:12   ` Henrique de Moraes Holschuh
2009-11-12 11:09     ` Alan Cox
2009-11-12 16:06       ` Henrique de Moraes Holschuh
2009-11-12 17:52         ` Alan Cox
2009-11-12 16:44     ` Andi Kleen
2009-11-12 17:37       ` Henrique de Moraes Holschuh
2009-11-12 17:49         ` Alan Cox
2009-11-12 17:57           ` Henrique de Moraes Holschuh
2009-11-12 18:13             ` Alan Cox
2009-11-12 20:02               ` Henrique de Moraes Holschuh
2009-11-12 20:06                 ` Alan Cox
2009-11-12 21:07         ` Krzysztof Halasa
2009-11-12 21:29           ` Cyrill Gorcunov
  -- strict thread matches above, loose matches on Subject: below --
2010-02-16  8:35 Nameer Yarkon
2010-02-16  8:41 ` Andi Kleen
2010-02-16  9:03   ` Nameer Yarkon
2010-02-16 12:31 ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AFB2822.30906@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mouse@mayc.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox