mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Sadasivan Shaiju <sshaiju@mvista.com>
Cc: Catalin.Marinas@arm.com, linux-kernel@vger.kernel.org,
	shaiju_sada@yahoo.com
Subject: Re: PATCH -RCU locking on last_VFP_context[cpu] in vfp_notifier [2.6.32]
Date: Tue, 12 Aug 2014 10:26:38 +0100	[thread overview]
Message-ID: <20140812092638.GG30401@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <dfaec2915a403865125b1e06c35386f9@mail.gmail.com>

On Mon, Aug 11, 2014 at 06:12:35PM -0700, Sadasivan Shaiju wrote:
> Hi  Russell,
> 
> Thanks  for  looking  into  the  issue.
> 
> This  issue  came  up  when  I  was  doing  econa (ARM)  board bringup
> for Montavista (cavium) .
> Following  was  the  bug  description .
> 
>   Using cge60-econa-cns3420-2.6.32_110928_1104937 the kernel failed to
> boot with
> the following error:
> 
> Internal error: Oops: 817 [#1] from cpu 1 PREEMPT SMP
> last sysfs file: /sys/devices/virtual/bdi/0:19/uevent
> Modules linked in: hmac ctr deflate
> CPU: 1    Tainted: G        W   (2.6.32.46.cge #1)
> PC is at vfp_notifier+0x48/0xbc
> LR is at vfp_notifier+0x44/0xbc
> pc : []    lr : []    psr: 60000013
> sp : aeee1d30  ip : aeee1d50  fp : aeee1d4c
> r10: af8d6460  r9 : ffffffff  r8 : af88c000
> r7 : a05ba584  r6 : af88c000  r5 : 00000001  r4 : 40000000
> r3 : 00000000  r2 : 00000000  r1 : 40000000  r0 : aeee0230
> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
> Control: 00c5787d  Table: 2eeec00a  DAC: 00000017
> Process grep (pid: 1710, stack limit = 0xaeee0270)
> Stack:  from cpu 1 (0xaeee1d30 to 0xaeee2000)
> 
> 
> During  the  bring up  I  used  to  intract  with   Catalin Marinas(
> Catalin.Marinas@arm.com)from  ARM  .  He  is  copied on the email .
> Catalin  has  pointed   out  the  following  patch  to  me ,  which
> solved  my problem .  I  just  want  to make  sure  the patch  goes to
> mainline kernel.

All you've done is re-quoted the same information you supplied in your
initial email with nothing new.  Therefore, you are wasting my time,
and I really can't be bothered with time wasters.

Since you seem to be totally incapable of analysing the problem
correctly, and I know very little about RT kernels, there's nothing
I can do here.  Sorry.

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

      reply	other threads:[~2014-08-12  9:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 22:24 Sadasivan Shaiju
2014-08-11 22:49 ` Russell King - ARM Linux
2014-08-12  1:12   ` Sadasivan Shaiju
2014-08-12  9:26     ` Russell King - ARM Linux [this message]

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=20140812092638.GG30401@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=Catalin.Marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaiju_sada@yahoo.com \
    --cc=sshaiju@mvista.com \
    /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

all inboxes | Powered by JetHome®