From: Manfred Gruber <m.gruber@tirol.com>
To: linux-kernel@vger.kernel.org
Cc: jan.altenberg@linutronix.de, tglx@linutronix.de, mingo@elte.hu
Subject: preempt_rt bug or warn on arm v4t
Date: Fri, 20 Apr 2007 13:06:08 +0200 [thread overview]
Message-ID: <200704201306.08066.m.gruber@tirol.com> (raw)
Hi !
I am using 2.6.21-rc7 with Preempt_rt Patch 2.6.20-rc6-rt0 on ep93xx.
This oops does not trigger in preempt_rt patch is applied.
On startup i get following oops when preemption is none.
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
BUG: at kernel/sched.c:4285 __schedule()
[<c006d404>] (dump_stack+0x0/0x14) from [<c02eeea4>] (__schedule+0x844/0x8e0)
[<c02ee660>] (__schedule+0x0/0x8e0) from [<c02ef038>] (schedule+0xd0/0x118)
[<c02eef68>] (schedule+0x0/0x118) from [<c02ef3e0>]
(wait_for_completion+0x94/0xf0)
r4 = C042DE88
[<c02ef34c>] (wait_for_completion+0x0/0xf0) from [<c0099c14>]
(keventd_create_kthread+0x3c/0x74)
r7 = 00000000 r6 = 00000002 r5 = C042DED4 r4 = C042DF18
[<c0099bd8>] (keventd_create_kthread+0x0/0x74) from [<c0099ccc>]
(kthread_create+0x80/0xc8)
r6 = C001C320 r5 = C042DED4 r4 = 00000000
[<c0099c4c>] (kthread_create+0x0/0xc8) from [<c009ad48>]
(posix_cpu_thread_call+0x40/0xb8)
r3 = 00000000 r2 = C0352BD0
r5 = 00000000 r4 = 00000000
[<c009ad08>] (posix_cpu_thread_call+0x0/0xb8) from [<c000dd10>]
(posix_cpu_thread_init+0x24/0x40)
r5 = 00000000 r4 = C03A7F74
[<c000dcec>] (posix_cpu_thread_init+0x0/0x40) from [<c00088b0>]
(init+0x38/0x30c)
r4 = 00000000
[<c0008878>] (init+0x0/0x30c) from [<c0087b90>] (do_exit+0x0/0x80c)
NET: Registered protocol family 16
ep93xx: PLL1 running at 400 MHz, PLL2 at 192 MHz
ep93xx: FCLK 200 MHz, HCLK 100 MHz, PCLK 50 MHz
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
If I enable full preemp_rt i get a warn:
irq event stamp: 0
hardirqs last enabled at (0): [<00000000>] __init_begin+0x3fff8000/0x30
hardirqs last disabled at (0): [<c00850f4>] copy_process+0x344/0x124c
softirqs last enabled at (0): [<c00850f4>] copy_process+0x344/0x124c
softirqs last disabled at (0): [<00000000>] __init_begin+0x3fff8000/0x30
BUG: at kernel/sched.c:4288 __schedule()
[<c006e71c>] (dump_stack+0x0/0x28) from [<c0308b64>] (__schedule+0xa04/0xab4)
[<c0308160>] (__schedule+0x0/0xab4) from [<c0308e28>] (schedule+0xdc/0x128)
[<c0308d4c>] (schedule+0x0/0x128) from [<c009d760>] (kthread+0xcc/0x12c)
r4 = C0B72000
[<c009d694>] (kthread+0x0/0x12c) from [<c008a508>] (do_exit+0x0/0x814)
r7 = 00000000 r6 = 00000000 r5 = 00000000 r4 = 00000000
---------------------------
| preempt count: 00000000 ]
| 0-level deep critical section nesting:
Does someone has an idea what is wrong ?
The configs can be found here:
https://dev.contec.at/dev/micro/micro9/LINUX/trunk/kernel/linux-2.6-config/
My quilt queue can be found here:
https://dev.contec.at/dev/micro/micro9/LINUX/trunk/kernel/linux-2.6/patches/
thanks regards
manfred
next reply other threads:[~2007-04-20 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 11:06 Manfred Gruber [this message]
2007-04-20 13:01 ` preempt_rt bug or warn on arm v4t Jan Altenberg
2007-04-20 13:26 ` Manfred Gruber
2007-04-25 15:02 ` Manfred Gruber
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=200704201306.08066.m.gruber@tirol.com \
--to=m.gruber@tirol.com \
--cc=jan.altenberg@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox