public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: jc@eclis•ch (Jean-Christian de Rivaz)
To: linux-arm-kernel@lists•infradead.org
Subject: Unhandled fault or spinlock lockup suspected ?
Date: Tue, 29 Sep 2015 19:50:08 +0200	[thread overview]
Message-ID: <560ACF50.8030205@eclis.ch> (raw)
In-Reply-To: <20150929162246.GK21513@n2100.arm.linux.org.uk>

Le 29. 09. 15 18:22, Russell King - ARM Linux a ?crit :
> On Tue, Sep 29, 2015 at 06:02:33PM +0200, Jean-Christian de Rivaz wrote:
>> I tried the last git linux master on a embedded system that worked with a
>> 3.19.0 kernel before. I solved most of the problems caused by the kernel
>> upgrade, but every 15 to 20 minutes I get this type of kernel report:
> Yes, it's because of the user access changes.  The uaccess_with_memcpy()
> code got broken, and despite trying to fix it, it seems that it's still
> broken.  I'll try again to fix it in the next few days.
>
> In any case, unless you have a Marvell platform, you should have this
> disabled - it provides a performance boost for Marvell platforms, but
> degrades performance everywhere else.  Please ensure that you disable
> CONFIG_UACCESS_WITH_MEMCPY.
>

Hi Russell, many thanks for your fast help. Work well when 
CONFIG_UACCESS_WITH_MEMCPY is disabled.

Jean-Christian

  reply	other threads:[~2015-09-29 17:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29 16:02 Unhandled fault or spinlock lockup suspected ? Jean-Christian de Rivaz
2015-09-29 16:22 ` Russell King - ARM Linux
2015-09-29 17:50   ` Jean-Christian de Rivaz [this message]
2015-09-29 18:01     ` Fabio Estevam

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=560ACF50.8030205@eclis.ch \
    --to=jc@eclis$(echo .)ch \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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