From: Akifumi Chikazawa <chikazawa.akifu@jp.fujitsu.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel crash on P4080DS
Date: Tue, 17 Apr 2012 22:06:23 -0700 (PDT) [thread overview]
Message-ID: <33705797.post@talk.nabble.com> (raw)
In-Reply-To: <33544993.post@talk.nabble.com>
Continue investing, I found a mistake in my last report.
These sentences are not true.
> This was due to BUG_ON. so I checked the condition.
> But it is not true (it means pte_val(*pt) is 0).
I guess that the cause of BUG_ON are as follows. There are two cases.
Could you advise me what would cause the kernel panic?
Board :P2020RDB,P4080DS
Linux kernel:2.6.36.2
Case 1
When ioremap is executed, a part of data of vmap_area that consists of tree
structure had been deleted,
and then, process to find a empty area in ioremap tried to assign an address
already being used.
As the result of that, BUG_ON in mmap_page was executed and caused kernel
panic.
Case2
When ioremap is executed, va_end in vmap_area structure can be 0. va_start
is the correct value at that time.
and process to find an empty area in ioremap did not caluculate accurately.
then it led to an incorrect address.
As the result of that, BUG_ON in mmap_page was executed and caused kernel
panic.
During execution of the immediately preceding ioremap, va_end is not 0.
and I attached Test program for P2020RDB.
http://old.nabble.com/file/p33705797/sample_driver.tar.gz
sample_driver.tar.gz
--
View this message in context: http://old.nabble.com/kernel-crash-on-P4080DS-tp33544993p33705797.html
Sent from the linux-kernel mailing list archive at Nabble.com.
prev parent reply other threads:[~2012-04-18 5:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 13:22 kernel crash on P4080DS Akifumi Chikazawa
2012-04-18 5:06 ` Akifumi Chikazawa [this message]
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=33705797.post@talk.nabble.com \
--to=chikazawa.akifu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.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