From: David Daney <ddaney@avtrex.com>
To: Noah Meyerhans <frodo@morgul.net>
Cc: linux-mips@linux-mips.org
Subject: Re: memory related kernel bug on cobalt raq2
Date: Mon, 14 Jan 2008 09:22:42 -0800 [thread overview]
Message-ID: <478B9A62.7000401@avtrex.com> (raw)
In-Reply-To: <20080114153114.GN3899@morgul.net>
Noah Meyerhans wrote:
> Hi all. I know this has come up in the past, but in case it's helpful, I
> figured I'd report that the kernel bug previously reported at (at least)
> http://www.linux-mips.org/archives/linux-mips/2007-10/msg00093.html is still
> present in current git kernels (more recently observed in
> 2.6.24-rc7-raq2-gaeb7040e-dirty). Here's the kernel output:
>
> Kernel bug detected[#1]:
> Cpu 0
> $ 0 : 00000000 b000ec00 00000001 00000004
> $ 4 : 81107760 7fb60f09 0000000e 83fb6000
> $ 8 : 00000f09 7fb60f09 800f5fe8 00000000
> $12 : 00000000 00000000 83ea6cc0 004038b4
> $16 : 81107760 0000000e 83fb6000 7fb60f09
> $20 : 803c0000 8fdf2cc0 00000000 86015e28
> $24 : 00000006 8008d480
> $28 : 86014000 86015de0 86015e2c 8008b2cc
> Hi : 00000000
> Lo : 00000000
> epc : 8008af9c kmap_coherent+0xc/0xe0 Not tainted
> ra : 8008b2cc copy_from_user_page+0xb0/0xe4
> Status: b000ec03 KERNEL EXL IE
> Cause : 00800034
> PrId : 000028a0 (Nevada)
> Process cat (pid: 5739, threadinfo=86014000, task=804b9178)
> Stack : 8fdf2cc0 7fb60f09 83fb6000 0000000e 0000000e 7fb60f09 83fb6000 00000000
> 0000000e 800e0484 8fc75178 804b9178 000800d0 00000000 883bbf09 0000000e
> 86015e2c 86015e28 8fe0dbfc 81107760 8fdf2cf4 00000000 8fdf2cc0 00000000
> 0000000e 83fb6000 00000400 8fc75178 00001000 0052c7c8 00000000 80133f5c
> 8fc75178 8fa26704 83fb6000 86015f18 00000000 0052c7c8 8fc75178 83fb6000
> ...
> Call Trace:
> [<8008af9c>] kmap_coherent+0xc/0xe0
> [<8008b2cc>] copy_from_user_page+0xb0/0xe4
> [<800e0484>] access_process_vm+0x178/0x21c
> [<80133f5c>] proc_pid_cmdline+0xa4/0x14c
> [<80136300>] proc_info_read+0x104/0x144
> [<800f5a7c>] vfs_read+0xc0/0x160
> [<800f603c>] sys_read+0x54/0xa0
> [<80088cac>] stack_done+0x20/0x3c
>
Yes, this would seem to be the same problem as:
http://www.linux-mips.org/cgi-bin/mesg.cgi?a=linux-mips&i=20071211221327.GB2150%40paradigm.rfc822.org
There is a similar problem in 2.6.23.
David Daney
next prev parent reply other threads:[~2008-01-14 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 15:31 memory related kernel bug on cobalt raq2 Noah Meyerhans
2008-01-14 17:22 ` David Daney [this message]
2008-01-15 6:32 ` Yoichi Yuasa
2008-01-15 15:26 ` Noah Meyerhans
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=478B9A62.7000401@avtrex.com \
--to=ddaney@avtrex.com \
--cc=frodo@morgul.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox