From: Martin Michlmayr <tbm@cyrius.com>
To: linux-mips@linux-mips.org
Subject: Non-fatal oops on SGI IP22 when doing: md5sum /dev/mem
Date: Tue, 28 Feb 2006 11:41:37 +0000 [thread overview]
Message-ID: <20060228114137.GA3087@deprecation.cyrius.com> (raw)
I get the following non-fatal oops on SGI IP22 (2.6.16-rc5) when
running "md5sum /dev/mem". I know it's not very smart to run this
command but nevertheless we shouldn't oops. FWIW, i386 reports
"md5sum: /dev/mem: Bad address".
sgi:/# md5sum /dev/mem
Segmentation fault
MC Bus Error
GIO error 0x400:<TIME > @ 0x00090000
Data bus error, epc == ffffffff881b0cf0, ra == ffffffff881c9ab4
Oops[#8]:
Cpu 0
$ 0 : 0000000000000000 0000000000000004 ffffffff80090000 0000000000000000
$ 4 : 00000000100023a8 ffffffff80090000 0000000000001000 ffffffff8a6dfe88
$ 8 : 0000000000000040 0000000000000000 0000000000000000 0000000000008000
$12 : 0000000000000008 0000000000008000 0000000000001000 ffffffffb0000000
$16 : 0000000000000000 00000000100033a8 ffffffff80000000 ffffffff8a6dfe88
$20 : 0000000000008000 ffffffffffffffff 000000007fcf29a8 00000000100022e8
$24 : 0000000000000000 0000000000090000
$28 : ffffffff8a6dc000 ffffffff8a6dfe30 0000000000008000 ffffffff881c9ab4
Hi : 0000000000000000
Lo : 0000000000000000
epc : ffffffff881b0cf0 both_aligned+0x10/0x64 Not tainted
ra : ffffffff881c9ab4 read_mem+0xec/0x138
Status: 3004cce3 KX SX UX KERNEL EXL IE
Cause : 1000401c
PrId : 00000460
Modules linked in: md5 ipv6
Process md5sum (pid: 1211, threadinfo=ffffffff8a6dc000, task=ffffffff8c0e0128)
Stack : ffffffff8c1c5aa0 0000000000000000 00000000100023a8 ffffffff880902bc
fffffffffffffff7 00000000100023a8 ffffffff8c1c5aa0 00000000100022e8
ffffffffffffffff ffffffff88091014 0000000000000000 0000000000090000
0000000000000000 0000000000008000 000000007fcf2998 ffffffff8801de8c
0000000000000000 0000000000000004 0000000000000fa3 0000000000008000
0000000000000003 00000000100023a8 0000000000008000 0000000000000000
0000000000000000 ffffffffb0000000 0000000000000000 ffffffffffffff0f
0000000000000000 0000000000000000 0000000000000000 ffffffffff000000
0000000000000000 0000000000000000 0000000000000000 ffffffffb0000000
0000000000000000 0000000000000000 000000006f857da9 ffffffffa9c7a710
...
Call Trace:
[<ffffffff880902bc>] vfs_read+0xfc/0x1b8
[<ffffffff88091014>] sys_read+0x4c/0x90
[<ffffffff8801de8c>] handle_sys+0x12c/0x148
Code: 11000017 30d8003f 00000000 <dca80000> dca90008 dcaa0010 dcab0018 64c6ffc0 dcac0020
--
Martin Michlmayr
http://www.cyrius.com/
next reply other threads:[~2006-02-28 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 11:41 Martin Michlmayr [this message]
2006-02-28 11:42 ` Non-fatal oops on SGI IP22 when doing: md5sum /dev/core Martin Michlmayr
2006-03-01 2:04 ` Non-fatal oops on SGI IP22 when doing: md5sum /dev/mem Martin Michlmayr
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=20060228114137.GA3087@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=linux-mips@linux-mips.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.