From: "Anton D. Kachalov" <mouse@mayc.ru>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reading /dev/mem by dd
Date: Thu, 12 Nov 2009 18:46:31 +0300 [thread overview]
Message-ID: <4AFC2DD7.5090407@mayc.ru> (raw)
In-Reply-To: <20091111162052.GD2448@hack>
Américo Wang wrote:
> On Wed, Nov 11, 2009 at 05:36:51PM +0300, 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?
>>
>
>
> What is the full backtrace? And which version of kernel are you
> running?
>
>
Ubuntu 2.6.28-16-server and 2.6.31-11-server.
Nov 10 17:59:10 localhost kernel: [ 243.749254] BUG: soft lockup -
CPU#11 stuck for 61s! [dd:4325]
Nov 10 17:59:10 localhost kernel: [ 243.749256] Modules linked in:
ip_queue ipt_LOG xt_limit ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4
xt_state xt_tcpudp x
t_multiport xt_NOTRACK nf_conntrack iptable_raw video output
iptable_filter ip_tables x_tables dummy parport_pc lp parport igb dca
snd_pcm serio_raw snd_timer snd soundcore snd_page_alloc iTCO_wdt
iTCO_vendor_support shpchp pcspkr raid10 raid456 raid6_pq async_xor
async_memcpy async_tx xor raid1 raid0 multipath linear fbcon tileblit
font bitblit softcursor
Nov 10 17:59:10 localhost kernel: [ 243.749282] CPU 11:
Nov 10 17:59:10 localhost kernel: [ 243.749284] Modules linked in:
ip_queue ipt_LOG xt_limit ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4
xt_state xt_tcpudp xt_multiport xt_NOTRACK nf_conntrack iptable_raw
video output iptable_filter ip_tables x_tables dummy parport_pc lp
parport igb dca snd_pcm serio_raw snd_timer snd soundcore snd_page_alloc
iTCO_wdt iTCO_vendor_support shpchp pcspkr raid10 raid456 raid6_pq
async_xor async_memcpy async_tx xor raid1 raid0 multipath linear fbcon
tileblit font bitblit softcursor
Nov 10 17:59:10 localhost kernel: [ 243.749305] Pid: 4325, comm: dd Not
tainted 2.6.31-11-server #36ya3 X8DTU
Nov 10 17:59:10 localhost kernel: [ 243.749307] RIP:
0010:[<ffffffff81061fd5>] [<ffffffff81061fd5>] r_next+0x5/0x30
Nov 10 17:59:10 localhost kernel: [ 243.749316] RSP:
0018:ffff88012b55fe48 EFLAGS: 00000206
Nov 10 17:59:10 localhost kernel: [ 243.749317] RAX: ffff8800280211e0
RBX: ffff88012b55fe88 RCX: 0000000000000118
Nov 10 17:59:10 localhost kernel: [ 243.749319] RDX: ffff88012b55fe60
RSI: ffff8800280211e0 RDI: 0000000000000000
Nov 10 17:59:10 localhost kernel: [ 243.749320] RBP: ffffffff81012aee
R08: 000000000000000e R09: ffffffff81795be0
Nov 10 17:59:10 localhost kernel: [ 243.749322] R10: 8000000000000563
R11: 8000000000000573 R12: ffffffff81516179
Nov 10 17:59:10 localhost kernel: [ 243.749323] R13: ffff88012b55fdf8
R14: ffffffff81078449 R15: ffff88012b55fda8
Nov 10 17:59:10 localhost kernel: [ 243.749325] FS:
00007fb8fe3646e0(0000) GS:ffff880028161000(0000) knlGS:0000000000000000
Nov 10 17:59:10 localhost kernel: [ 243.749327] CS: 0010 DS: 0000 ES:
0000 CR0: 000000008005003b
Nov 10 17:59:10 localhost kernel: [ 243.749328] CR2: 00007fb8de930000
CR3: 000000012b4fd000 CR4: 00000000000006a0
Nov 10 17:59:10 localhost kernel: [ 243.749330] DR0: 0000000000000000
DR1: 0000000000000000 DR2: 0000000000000000
Nov 10 17:59:10 localhost kernel: [ 243.749331] DR3: 0000000000000000
DR6: 00000000ffff0ff0 DR7: 0000000000000400
Nov 10 17:59:10 localhost kernel: [ 243.749333] Call Trace:
Nov 10 17:59:10 localhost kernel: [ 243.749337] [<ffffffff8106294a>] ?
iomem_is_exclusive+0x8a/0xb0
Nov 10 17:59:10 localhost kernel: [ 243.749342] [<ffffffff81037cbc>] ?
devmem_is_allowed+0x2c/0x50
Nov 10 17:59:10 localhost kernel: [ 243.749346] [<ffffffff812e2828>] ?
read_mem+0xa8/0x180
Nov 10 17:59:10 localhost kernel: [ 243.749350] [<ffffffff81117314>] ?
vfs_read+0xc4/0x190
Nov 10 17:59:10 localhost kernel: [ 243.749352] [<ffffffff81117530>] ?
sys_read+0x50/0x90
Nov 10 17:59:10 localhost kernel: [ 243.749356] [<ffffffff81011f42>] ?
system_call_fastpath+0x16/0x1b
Same problem with soft lockup I have on this platform under heavy system
load but I can't get backtrace for it...
next prev parent reply other threads:[~2009-11-12 15:46 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 [this message]
2009-11-11 21:09 ` Robert Hancock
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=4AFC2DD7.5090407@mayc.ru \
--to=mouse@mayc.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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