All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Cook <tom.k.cook@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: Tracers+cyclictest causing kernel oops
Date: Fri, 31 May 2013 10:31:01 +0100	[thread overview]
Message-ID: <CAFSh4Uw-tAC0QugLQzFow4uRyZKw=7Gu=XC37ZYrsAuPAOrjpw@mail.gmail.com> (raw)
In-Reply-To: <51A86C1A.2040100@linutronix.de>

On Fri, May 31, 2013 at 10:23 AM, Sebastian Andrzej Siewior
<bigeasy@linutronix.de> wrote:
[snip]
> I just tried the same thing on my AM33xx and nothing bad happned here.
> One thing still: you might want to use "-n" for nanosleep.
>
> Could you try [0] to check if you are not using more memory than
> available? If the OOM-killer kills the program, then it is okay, if the
> data-abort exception comes or the kernel crashes in a strange way then
> it is HW.
>
> The tracer do not use any special interrupts on purpose.
> Now that I saw rasperry-pi let me ask this: do you have any
> non-mainline patches on-top? And if it is the case, could you try to
> get rid of them?

It is the linux-3.6.y branch of raspberrypi/linux on github with RT
patches added.  Nothing else custom.

> Also you can try the same test without the RT patches?

Okay.  Hopefully the flurry of spring weddings will break up enough to
give me a chance to try this over the weekend.

Tom

  reply	other threads:[~2013-05-31  9:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26  8:04 Tracers+cyclictest causing kernel oops Tom Cook
2013-04-29  7:16 ` Tom Cook
2013-05-03 16:05   ` Sebastian Andrzej Siewior
2013-05-12  5:14     ` Tom Cook
     [not found]     ` <CAFSh4UwD5yyJrtKwUaOX-uiUuzVf7YaDbM4vbZ1EFZBf6F1JHg@mail.gmail.com>
2013-05-21 11:16       ` Sebastian Andrzej Siewior
2013-05-21 15:20         ` Tom Cook
2013-05-27  8:02           ` Uwe Kleine-König
2013-05-27 21:23             ` Tom Cook
2013-05-28  6:53               ` Uwe Kleine-König
2013-06-21 11:01                 ` Tom Cook
2013-05-31  9:23           ` Sebastian Andrzej Siewior
2013-05-31  9:31             ` Tom Cook [this message]
2013-06-21 11:21             ` Tom Cook
2013-06-21 14:17               ` Tom Cook
2013-06-21 14:58                 ` Tom Cook
2013-06-21 15:00               ` Sebastian Andrzej Siewior

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='CAFSh4Uw-tAC0QugLQzFow4uRyZKw=7Gu=XC37ZYrsAuPAOrjpw@mail.gmail.com' \
    --to=tom.k.cook@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.