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 09:04:18 +0200	[thread overview]
Message-ID: <200910010904.18923.dk-arm-linux@gmx.de> (raw)

Hi all,

hm - it seems to be suspect but I've got random kernel crashes with latest openrd git kernel from:

http://repo.or.cz/w/linux-2.6/linux-2.6-openrd.git
(BTW: are there any news on bringing the openrd kernel to mainline?)

It looks like there is something wrong in cpu_idle()???
kernel: Linux version 2.6.31-rc9-ge2e09ec (dieter at dk1-linux) (gcc version 4.2.0 20070413 (prerelease)) #10 PREEMPT Thu Oct 1 08:46:47 CEST 2009

Once I got a backtrace like:
------------[ cut here ]------------
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)
---[ end trace fb05d74310f1e273 ]---

Many other times the system freezes and I see in the debugger:

: System
cpsr: 0xffffffff pc: 0xffffffe9
MMU: disabled, D-Cache: disabled, I-Cache: disabled
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
target state: halted
target halted in Thumb state due to debug-request, current mode: Abort
cpsr: 0x00000037 pc: 0xc046a74a
MMU: disabled, D-Cache: disabled, I-Cache: disabled

I've written yesterday in a email to openrd google group "openrd kernel questions" that I've got problems with enabled EHCI but it looks like
that wasn't the reason because today morning I got the crashes without enabled EHCI!

Have somenone else observed this earlier and how can I go on to track the bug down?

Many thanks,
Dieter

             reply	other threads:[~2009-10-01  7:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01  7:04 Dieter Kiermaier [this message]
2009-10-01  7:04 ` kirkwood openrd: random kernel crashes with git kernel 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
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=200910010904.18923.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.