From: Dirk Behme <dirk.behme@googlemail.com>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: 2.6.19 rc6 rt3 on embedded ARM system
Date: Sun, 19 Nov 2006 20:27:02 +0100 [thread overview]
Message-ID: <4560B006.2070305@gmail.com> (raw)
In-Reply-To: <20061119181539.GQ18636@pengutronix.de>
Robert Schwebel wrote:
> On Sun, Nov 19, 2006 at 06:36:03PM +0100, Dirk Behme wrote:
>
>>playing with patch-2.6.19-rc6-rt3 on an embedded TI OMAP
>>based ARM926 system I encountered two issues.
>>
>>First, I got the system booting and even playing MP3 via NFS
>>using madplay on ALSA works :)
>>
>>But after madplay stops, I got an Oops:
>>
>>kernel BUG at kernel/rtmutex.c:672!
>>Unable to handle kernel NULL pointer dereference at virtual
>>address 00000000
>>pgd = c0004000
>>[00000000] *pgd=00000000
>>Internal error: Oops: 817 [#1]
>>PC is at __bug+0x44/0x58
>>LR is at rt_up+0x4c/0x6c
>>...
>>Any ideas what's wrong here?
>
> You snipped the stack trace here, which could offer some information
> about the call path. Could you post it?
Thought for whoever coded this explicit bug statement info
above would be sufficient ;)
Ah! Thanks for directing me to the details. Looks like I
missed one spinlock -> raw_spinlock conversion...
> arm-v4t-linux-gnueabi/gcc-4.2-20061031-glibc-2.5
> arm-v4t-linux-gnueabi/gcc-4.1.1-glibc-2.5
...
>>I use a gcc 4.1.0 toolchain built with crosstool with glibc-2.3.2:
>
> I assume glibc-2.3.2 is too old.
Yeah, thanks. A toolchain with glibc 2.3.6 seem to make the
job. Maybe this is worth a hint in wiki?
Cheers
Dirk
next prev parent reply other threads:[~2006-11-19 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 17:36 2.6.19 rc6 rt3 on embedded ARM system Dirk Behme
2006-11-19 18:15 ` Robert Schwebel
2006-11-19 19:27 ` Dirk Behme [this message]
2006-11-19 21:31 ` Robert Schwebel
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=4560B006.2070305@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=r.schwebel@pengutronix.de \
/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.