linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: FP register corruption in Exynos 4210 (Cortex-A9)
Date: Mon, 22 Dec 2014 23:50:24 +0000	[thread overview]
Message-ID: <20141222235024.GP11285@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <5498AC4A.1050701@gmail.com>

On Mon, Dec 22, 2014 at 08:42:02PM -0300, Lanchon wrote:
> 
> On 12/22/2014 08:29 PM, Russell King - ARM Linux wrote:
> >On Mon, Dec 22, 2014 at 07:46:27PM -0300, Lanchon wrote:
> >>however under some circumstances the kernel did the wrong thing: it didn't
> >>reload the registers even though it was needed, probably because the
> >>hardware had been powered down and had lost state without the tracking code
> >>getting word of it. just disabling the optimization made the kernel solid.
> >Right, so mainline kernel's don't exhibit the behaviour...
> >
> >>a couple of days later the root cause seems to have been identified and
> >>fixed. i describe the whole thing here:
> >>http://forum.xda-developers.com/galaxy-s2/development-derivatives/kernel-fpbug-stable-4-x-kernel-galaxy-t2978088
> >... because it's a local issue with cpuidle not calling the appropriate
> >CPU PM functions, and that means there's no patches that we need to deal
> >with for mainline kernels, right?
> >
> 
> that's what i think, yes. i only got back here on the list to thank you and
> let you know what was wrong since you helped me a couple of months ago.

Please let us know if anything changes, thanks.

And have a Merry Christmas.

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2014-12-22 23:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 21:48 FP register corruption in Exynos 4210 (Cortex-A9) Lanchon
2014-10-07 22:15 ` Russell King - ARM Linux
2014-10-08  7:58   ` Lanchon
2014-10-08  8:19   ` Lanchon
2014-10-08  8:27     ` Russell King - ARM Linux
2014-10-08  8:35     ` Russell King - ARM Linux
2014-10-08  8:53       ` Ard Biesheuvel
2014-10-08  9:22         ` Ard Biesheuvel
2014-10-08  9:55           ` Russell King - ARM Linux
2014-10-08 10:32             ` Ard Biesheuvel
2014-10-09 22:36           ` Lanchon
2014-10-09 22:20         ` Lanchon
2014-10-09 22:32           ` Russell King - ARM Linux
2014-10-10  9:45             ` Arnd Bergmann
2014-10-10 10:01               ` Russell King - ARM Linux
2014-12-22 22:46                 ` Lanchon
2014-12-22 23:29                   ` Russell King - ARM Linux
2014-12-22 23:42                     ` Lanchon
2014-12-22 23:50                       ` Russell King - ARM Linux [this message]
2014-12-23  8:45                   ` Ard Biesheuvel

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=20141222235024.GP11285@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).