From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Internal error: Oops: 17 [#1] ARM
Date: Wed, 22 Jan 2014 16:41:00 +0000 [thread overview]
Message-ID: <20140122164100.GE15937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CACUGKYPXficVuqDgy6_Tnh9b-VOXDNK=+nqb6U5O6NpcZOGGpQ@mail.gmail.com>
On Wed, Jan 22, 2014 at 08:23:36AM -0800, John Tobias wrote:
> Hello all,
>
> I am using 3.13-rc1 kernel on iMX6SL processor. My filesystem is in
> eMMC running SDR50.
> Is anyone here encountered these problem and if there's any existing
> patch that I can get?.
How reproducable is this? I notice you're using 3.13-rc1 too, it could
be the bug has already been fixed in a later kernel version. -rc1
kernels are really the "fresh after lots of new feature merging" kernels
which should always be expected to be rather buggy.
Linux kernel "release candidates" are not "we think this is going to be
a final kernel, please test it" but -rc1 marks the end of the new
feature merging and the beginning of the stablisation phase.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-22 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 16:23 Internal error: Oops: 17 [#1] ARM John Tobias
2014-01-22 16:41 ` Russell King - ARM Linux [this message]
2014-01-22 17:56 ` John Tobias
2014-01-22 23:49 ` John Tobias
2014-01-23 2:28 ` Fabio Estevam
2014-01-23 3:25 ` John Tobias
2014-01-23 3:01 ` walimis
2014-01-23 3:28 ` John Tobias
2014-01-23 3:46 ` walimis
2014-01-23 4:13 ` John Tobias
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=20140122164100.GE15937@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).