From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: make virt_to_idmap() return unsigned long
Date: Mon, 1 Feb 2016 17:31:37 +0000 [thread overview]
Message-ID: <20160201173137.GV10826@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <56AF917F.9030505@oracle.com>
On Mon, Feb 01, 2016 at 09:10:23AM -0800, santosh shilimkar wrote:
> Based on the log, I think the patch seems to work fine since the boot
> reached upto rootfs. The crash seems to be coming from mostky NetCP
> related compents.
I read the boot log slightly differently - I'm assuming that the
boot log is from the kernel which _will_ be kexec'd from, so we
don't yet know whether the patches work or not.
I looked at the oops, and it's in tasklet_action, but for some
reason the unwinder is unable to unwind and provide a backtrace,
so it's not very debuggable.
However, this is a useful backtrace for me in a different way:
to provide to people who want to deprecate the frame-pointer
based backtracing to prove why the unwinder based solution still
isn't up to the job.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-02-01 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 18:21 [PATCH 1/2] ARM: make virt_to_idmap() return unsigned long Russell King
2016-01-27 4:27 ` santosh.shilimkar at oracle.com
2016-02-01 15:20 ` Russell King - ARM Linux
2016-02-01 17:01 ` Vitaly Andrianov
2016-02-01 17:10 ` santosh shilimkar
2016-02-01 17:31 ` Russell King - ARM Linux [this message]
2016-02-01 17:55 ` santosh.shilimkar at oracle.com
2016-02-03 0:09 ` santosh shilimkar
2016-02-03 14:14 ` Grygorii Strashko
2016-02-03 15:43 ` Vitaly Andrianov
2016-02-03 19:59 ` Russell King - ARM Linux
2016-02-04 11:53 ` Grygorii Strashko
2016-02-08 17:10 ` Russell King - ARM Linux
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=20160201173137.GV10826@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).