From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: arm kernel oops in highmem.c with 4.2
Date: Wed, 5 Aug 2015 11:07:01 +0100 [thread overview]
Message-ID: <20150805100701.GV7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CALeDE9Ox3=sh3AXQ0NUG6BBfU5i5YrMY=LDpcTHQWqz2=60F2g@mail.gmail.com>
On Wed, Aug 05, 2015 at 11:01:01AM +0100, Peter Robinson wrote:
> Hi All,
>
> On Fedora 23 with recent 4.2 kernels we're seeing a crash (below) in
> highmem.c on a fairly regular occurrence across a number of different
> SoCs, I've seen it with at least AllWinner A20, i.MX6Q, Tegra2 and 124
> with both a LPAE and non LPAE kernel, seen it happen when doing a
> number of different things but regenerating a initrd, applying updates
> (dnf/yum) and starting X are all pretty good triggers.
I've yet to see any problems with mainline 4.2-rc5 kernels on any of my
iMX6 platforms, which includes initramfs regeneration, apt-get updates
and X.
> [71751.658105] ------------[ cut here ]------------
> [71751.658153] kernel BUG at arch/arm/mm/highmem.c:114!
Well, in mainline kernels, the BUG is on line 113, not line 114. So at
least this file is modified from mainline kernels. Maybe the problem is
caused by patches applied to Fedora kernels?
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-08-05 10:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 10:01 arm kernel oops in highmem.c with 4.2 Peter Robinson
2015-08-05 10:07 ` Russell King - ARM Linux [this message]
2015-08-05 10:13 ` Peter Robinson
2015-08-05 11:27 ` Russell King - ARM Linux
2015-08-11 17:48 ` Mark Salter
2015-08-11 18:10 ` Russell King - ARM Linux
2015-08-11 19:41 ` Nicolas Pitre
2015-08-11 19:56 ` Russell King - ARM Linux
2015-08-11 20:20 ` Nicolas Pitre
2015-08-11 21:17 ` Mark Salter
2015-08-12 2:18 ` Nicolas Pitre
2015-08-12 13:33 ` Mark Salter
2015-08-12 15:50 ` Nicolas Pitre
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=20150805100701.GV7557@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).