From: David Daney <ddaney@avtrex.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@linux-mips.org
Subject: Re: 2.6.24-rc2 crash in kmap_coherent
Date: Tue, 11 Dec 2007 14:49:21 -0800 [thread overview]
Message-ID: <475F13F1.2050109@avtrex.com> (raw)
In-Reply-To: <20071211221327.GB2150@paradigm.rfc822.org>
Florian Lohoff wrote:
> Hi,
> i just discovered that my native gcc build on one of my Indys stopped. I
> found this in the dmesg ;)
>
> Its a 2.6.24-rc2 on an R5k Indy 64M:
>
> Kernel bug detected[#1]:
> Cpu 0
> $ 0 : 0000000000000000 ffffffff9000cce0 0000000000000001 ffffffff80000000
> $ 4 : ffffffff8921f910 000000007fda0f05 000000007fda0f05 ffffffff8b8ea000
> $ 8 : ffffffff89b4ef05 000000000000000e ffffffff8921f910 0000000000000f05
> $12 : 0000000000000000 ffffffff80000008 ffffffff88090010 00000000004038b4
> $16 : ffffffff8921f910 000000007fda0f05 ffffffff8b8ea000 000000000000000e
> $20 : ffffffff8bdfb920 0000000000000000 ffffffff8bd88cc0 ffffffff8893fd58
> $24 : 0000000000000006 ffffffff8801df00
> $28 : ffffffff8893c000 ffffffff8893fd20 ffffffff88430000 ffffffff8801c010
> Hi : 000000000001d1ea
> Lo : 0000000000009b4e
> epc : ffffffff8801bcf0 kmap_coherent+0x10/0x130 Not tainted
> ra : ffffffff8801c010 copy_from_user_page+0x40/0xb0
> Status: 9000cce3 KX SX UX KERNEL EXL IE
> Cause : 00000034
> PrId : 00002321 (R5000)
> Modules linked in: dm_snapshot dm_mirror dm_mod ipv6
> Process cat (pid: 14553, threadinfo=ffffffff8893c000, task=ffffffff88a52660)
> Stack : 000000000000000e 000000007fda0f05 ffffffff8b8ea000 0000000000000000
> ffffffff88079d10 ffffffff88079cc4 ffffffff8bfbd528 ffffffff8921f910
> ffffffff8bdfb980 ffffffff8b8ea000 ffffffff8bdfb920 0000000000000000
> ffffffff8b8ea000 000000000000000e ffffffff8bd88cc0 ffffffff8893fe78
> 0000000000447000 000000000052c7d8 0000000000000000 ffffffff880d9014
> ffffffff8bd88cc0 ffffffff8b8ea000 fffffffffffffff4 ffffffff8b863248
> 0000000000000400 ffffffff8893fe78 0000000000447000 ffffffff880db188
> ffffffff8be6f6e0 0000000000000400 0000000000447000 ffffffff8893fe78
> 0000000000447000 0000000000000003 0000000000000016 ffffffff8808fbdc
> ffffffff8be6f6e0 0000000000000400 0000000000447000 fffffffffffffff7
> ...
> Call Trace:
> [<ffffffff8801bcf0>] kmap_coherent+0x10/0x130
> [<ffffffff8801c010>] copy_from_user_page+0x40/0xb0
> [<ffffffff88079d10>] access_process_vm+0x168/0x1d8
> [<ffffffff880d9014>] proc_pid_cmdline+0xac/0x140
> [<ffffffff880db188>] proc_info_read+0x108/0x150
> [<ffffffff8808fbdc>] vfs_read+0xec/0x178
> [<ffffffff88090060>] sys_read+0x50/0x98
> [<ffffffff88019718>] handle_sys+0x118/0x134
>
>
> Code: 0002127a 00021000 30420001 <00028036> 8f820024 3c038843 24420001 af820024 dc62f390
>
FWIW I get something very similar reading /proc/1/cmdline on
2.6.23-1/ip32 w/ R5000 and there have been other similar postings here
recently.
Maybe one day I will look into it, but it probably will not be real soon...
David Daney
next prev parent reply other threads:[~2007-12-11 22:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 22:13 2.6.24-rc2 crash in kmap_coherent Florian Lohoff
2007-12-11 22:49 ` David Daney [this message]
2007-12-12 6:40 ` David Daney
2007-12-12 12:06 ` Ralf Baechle
2007-12-12 15:32 ` Ralf Baechle
2007-12-12 17:11 ` Giuseppe Sacco
2007-12-12 17:25 ` Giuseppe Sacco
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=475F13F1.2050109@avtrex.com \
--to=ddaney@avtrex.com \
--cc=flo@rfc822.org \
--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