All of lore.kernel.org
 help / color / mirror / Atom feed
From: dk-arm-linux@gmx.de (Dieter Kiermaier)
To: linux-arm-kernel@lists.infradead.org
Subject: kirkwood openrd: random kernel crashes with git kernel
Date: Thu, 1 Oct 2009 10:42:09 +0200	[thread overview]
Message-ID: <200910011042.09185.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <20091001101925.50a592fd@marrow.netinsight.se>

Am Donnerstag 01 Oktober 2009 10:19:25 schrieb Simon Kagstrom:
> 
> On Thu, 1 Oct 2009 10:12:16 +0200
> Sascha Silbe <sascha-ml-devel-openrd-google@silbe.org> wrote:
> 
> > On Thu, Oct 01, 2009 at 09:04:18AM +0200, Dieter Kiermaier wrote:
> > 
> > > WARNING: at arch/arm/kernel/process.c:171 cpu_idle+0x74/0xbc()
> > > Modules linked in:
> > > [<c002a748>] (unwind_backtrace+0x0/0xd8) from [<c003931c>] 
> > > (warn_slowpath_common+0x4c/0x68)
> > > [<c003931c>] (warn_slowpath_common+0x4c/0x68) from [<c0026844>] 
> > > (cpu_idle+0x74/0xbc)
> > > [<c0026844>] (cpu_idle+0x74/0xbc) from [<c0008b2c>] 
> > > (start_kernel+0x22c/0x27c)
> > > [<c0008b2c>] (start_kernel+0x22c/0x27c) from [<00008034>] (0x8034)
> > Try the patch from [1], it works for me (uptime 5 days now without the 
> > message above).
> > Disclaimer: I know next to nothing about Linux internals, so can't judge 
> > the quality of the patch. Use at your own risk.
> > 
> > [1] http://patchwork.kernel.org/patch/40871/
> 
> Nice!
> 
> I should add that I've seen this error even without openocd connected,
> so this seems to be a real error. Anyway, I guess this will sooner or
> later be applied (in some form) upstream, so openrd should benefit
> "automatically" from it.
> 
> However, with OpenOCD there are other type of crashes which look very
> random, so I believe those will stay even with this.
> 

Many thanks to all off you for your valuable comments!

As far as I've seen on my system there are two different things in conjunction with openOCD:

1. The above adressed issue in cpu_idle path
2. Another different thing which causes slightly random crashes.

So [1.] could be solved by the above mentioned patch - I will try this out.

[2.] ??? I will try to find some information at the openocd list archive...

Dieter


> // Simon
> 
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups "OpenRD" group.
> To post to this group, send email to openrd at googlegroups.com
> To unsubscribe from this group, send email to openrd+unsubscribe at googlegroups.com
> For more options, visit this group at http://groups.google.com/group/openrd?hl=en
> -~----------~----~----~----~------~----~------~--~---
> 

  reply	other threads:[~2009-10-01  8:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01  7:04 kirkwood openrd: random kernel crashes with git kernel Dieter Kiermaier
2009-10-01  7:04 ` Simon Kagstrom
2009-10-01  8:07   ` Dieter Kiermaier
2009-10-01  8:08     ` Simon Kagstrom
2009-10-01 16:15   ` Nicolas Pitre
2009-10-01  8:12 ` Sascha Silbe
2009-10-01  8:19   ` Simon Kagstrom
2009-10-01  8:42     ` Dieter Kiermaier [this message]
2009-10-01 16:19     ` Nicolas Pitre
2009-10-02  6:40       ` Simon Kagstrom
2009-10-02  6:53         ` Dieter Kiermaier
2009-10-03  2:50         ` Nicolas Pitre
2009-10-01  8:17 ` Russell King - ARM Linux

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=200910011042.09185.dk-arm-linux@gmx.de \
    --to=dk-arm-linux@gmx.de \
    --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 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.