From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
dwalker@mvista.com, david singleton <dsingleton@mvista.com>
Subject: Re: 2.6.14-rc4-rt1
Date: Fri, 14 Oct 2005 11:35:39 -0700 [thread overview]
Message-ID: <1129314939.4652.4.camel@cmn3.stanford.edu> (raw)
In-Reply-To: <1129312907.19449.13.camel@cmn3.stanford.edu>
On Fri, 2005-10-14 at 11:01 -0700, Fernando Lopez-Lezcano wrote:
> On Fri, 2005-10-14 at 08:15 +0200, Ingo Molnar wrote:
> > * Ingo Molnar <mingo@elte.hu> wrote:
> >
> > > could you try:
> > >
> > > strace -o log sleep 10
> > >
> > > and wait for a failure, and send us the log? Is it perhaps nanosleep
> > > unexpectedly returning with -EAGAIN or -512? There's a transient
> > > nanosleep failure that happens on really fast boxes, which we havent
> > > gotten to the bottom yet. That problem is very sporadic, but maybe
> > > your box is just too fast and triggers it more likely :-)
> >
> > is nanosleep returning -ERESTART_RESTARTBLOCK (-516) perhaps?
>
> Yes, that is probably correct, I saw a few of these:
> sleep: cannot read realtime clock: Unknown error 516
>
> I'm building rt5 and will report later.
Sorry, still getting the same behavior from rt5 (including 516 errors).
I'm getting something out of rt5's debugging code, some examples follow:
crond/4144[CPU#1]: BUG in check_ktimer_signal at kernel/ktimers.c:1117
[<c0128277>] __WARN_ON+0x67/0x90 (8)
[<c01416e7>] check_ktimer_signal+0x127/0x130 (48)
[<c01417a1>] ktimer_nanosleep+0xb1/0xf0 (52)
[<c014181b>] ktimer_nanosleep_mono+0x3b/0x50 (60)
[<c0374f60>] nanosleep_restart_mono+0x0/0x30 (8)
[<c01415b0>] process_ktimer+0x0/0x10 (60)
[<c01418cc>] sys_nanosleep+0x4c/0x50 (36)
[<c0103481>] syscall_call+0x7/0xb (16)
expires: 1736/464432941
expired: 1721/862640520
at: 657
interval: 0/0
now: 1721/862641188
rem: 14/601792421
overrun: 0
getoffset: 00000000
crond/4144[CPU#1]: BUG in check_ktimer_signal at kernel/ktimers.c:1117
[<c0128277>] __WARN_ON+0x67/0x90 (8)
[<c01416e7>] check_ktimer_signal+0x127/0x130 (48)
[<c01417a1>] ktimer_nanosleep+0xb1/0xf0 (52)
[<c014181b>] ktimer_nanosleep_mono+0x3b/0x50 (60)
[<c0374f60>] nanosleep_restart_mono+0x0/0x30 (8)
[<c01415b0>] process_ktimer+0x0/0x10 (60)
[<c01418cc>] sys_nanosleep+0x4c/0x50 (36)
[<c0103481>] syscall_call+0x7/0xb (16)
expires: 6116/908892557
expired: 1721/862993769
at: 657
interval: 0/0
now: 1721/862994253
rem: 4395/45898788
overrun: 0
getoffset: 00000000
gpm/4136[CPU#1]: BUG in check_ktimer_signal at kernel/ktimers.c:1117
[<c0128277>] __WARN_ON+0x67/0x90 (8)
[<c01416e7>] check_ktimer_signal+0x127/0x130 (48)
[<c01417a1>] ktimer_nanosleep+0xb1/0xf0 (52)
[<c014181b>] ktimer_nanosleep_mono+0x3b/0x50 (60)
[<c0374f60>] nanosleep_restart_mono+0x0/0x30 (8)
[<c01415b0>] process_ktimer+0x0/0x10 (60)
[<c01418cc>] sys_nanosleep+0x4c/0x50 (36)
[<c0103481>] syscall_call+0x7/0xb (16)
expires: 1730/917836219
expired: 1721/862633260
at: 657
interval: 0/0
now: 1721/862633539
rem: 9/55202959
overrun: 0
getoffset: 00000000
sleep/5299[CPU#1]: BUG in check_ktimer_signal at kernel/ktimers.c:1117
[<c0128277>] __WARN_ON+0x67/0x90 (8)
[<c01416e7>] check_ktimer_signal+0x127/0x130 (48)
[<c01417a1>] ktimer_nanosleep+0xb1/0xf0 (52)
[<c014181b>] ktimer_nanosleep_mono+0x3b/0x50 (60)
[<c0374f60>] nanosleep_restart_mono+0x0/0x30 (8)
[<c01415b0>] process_ktimer+0x0/0x10 (60)
[<c01418cc>] sys_nanosleep+0x4c/0x50 (36)
[<c0103481>] syscall_call+0x7/0xb (16)
expires: 1739/273286972
expired: 1739/272964651
at: 657
interval: 0/0
now: 1739/272965670
rem: 0/322321
overrun: 0
getoffset: 00000000
hald-addon-stor/4229[CPU#1]: BUG in check_ktimer_signal at
kernel/ktimers.c:1117 [<c0128277>] __WARN_ON+0x67/0x90 (8)
[<c01416e7>] check_ktimer_signal+0x127/0x130 (48)
[<c01417a1>] ktimer_nanosleep+0xb1/0xf0 (52)
[<c014181b>] ktimer_nanosleep_mono+0x3b/0x50 (60)
[<c0374f60>] nanosleep_restart_mono+0x0/0x30 (8)
[<c01415b0>] process_ktimer+0x0/0x10 (60)
[<c01418cc>] sys_nanosleep+0x4c/0x50 (36)
[<c0103481>] syscall_call+0x7/0xb (16)
expires: 1751/956279550
expired: 1751/955896702
at: 657
interval: 0/0
now: 1751/955897242
rem: 0/382848
overrun: 0
getoffset: 00000000
sleep/5321[CPU#1]: BUG in check_ktimer_signal at kernel/ktimers.c:1117
[<c0128277>] __WARN_ON+0x67/0x90 (8)
[<c01416e7>] check_ktimer_signal+0x127/0x130 (48)
[<c01417a1>] ktimer_nanosleep+0xb1/0xf0 (52)
[<c014181b>] ktimer_nanosleep_mono+0x3b/0x50 (60)
[<c0374f60>] nanosleep_restart_mono+0x0/0x30 (8)
[<c01415b0>] process_ktimer+0x0/0x10 (60)
[<c01418cc>] sys_nanosleep+0x4c/0x50 (36)
[<c0103481>] syscall_call+0x7/0xb (16)
expires: 1753/316840062
expired: 1753/316460409
at: 657
interval: 0/0
now: 1753/316461329
rem: 0/379653
overrun: 0
getoffset: 00000000
hald-addon-stor/4229[CPU#1]: BUG in check_ktimer_signal at
kernel/ktimers.c:1117 [<c0128277>] __WARN_ON+0x67/0x90 (8)
[<c01416e7>] check_ktimer_signal+0x127/0x130 (48)
[<c01417a1>] ktimer_nanosleep+0xb1/0xf0 (52)
[<c014181b>] ktimer_nanosleep_mono+0x3b/0x50 (60)
[<c0374f60>] nanosleep_restart_mono+0x0/0x30 (8)
[<c01415b0>] process_ktimer+0x0/0x10 (60)
[<c01418cc>] sys_nanosleep+0x4c/0x50 (36)
[<c0103481>] syscall_call+0x7/0xb (16)
-- Fernando
next prev parent reply other threads:[~2005-10-14 18:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 11:14 2.6.14-rc4-rt1 Ingo Molnar
2005-10-11 16:03 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-11 20:55 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-11 21:08 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-11 21:13 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-11 21:21 ` 2.6.14-rc4-rt1 Lee Revell
2005-10-11 22:23 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 16:37 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 17:48 ` 2.6.14-rc4-rt1 Lee Revell
2005-10-12 18:00 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 18:25 ` 2.6.14-rc4-rt1 Lee Revell
2005-10-12 18:38 ` 2.6.14-rc4-rt1 Lee Revell
2005-10-12 19:11 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 19:41 ` 2.6.14-rc4-rt1 Mark Knecht
2005-10-12 19:45 ` 2.6.14-rc4-rt1 Lee Revell
2005-10-12 19:52 ` 2.6.14-rc4-rt1 Lee Revell
2005-10-12 6:14 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-12 6:16 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-12 6:33 ` 2.6.14-rc4-rt1 Steven Rostedt
2005-10-12 22:08 ` 2.6.14-rc4-rt1 George Anzinger
2005-10-12 23:41 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-12 23:52 ` 2.6.14-rc4-rt1 George Anzinger
2005-10-14 4:04 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-12 7:10 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-13 22:29 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-14 2:28 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-14 4:56 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14 6:15 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14 8:53 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14 18:01 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-14 18:35 ` Fernando Lopez-Lezcano [this message]
2005-10-14 19:05 ` 2.6.14-rc4-rt1 Fernando Lopez-Lezcano
2005-10-14 3:56 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-12 16:42 ` 2.6.14-rc4-rt1 Badari Pulavarty
2005-10-14 6:22 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14 9:57 ` 2.6.14-rc4-rt1 Andi Kleen
2005-10-14 13:12 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-14 19:24 ` 2.6.14-rc4-rt1 Badari Pulavarty
2005-10-14 6:22 ` 2.6.14-rc4-rt1 Ingo Molnar
2005-10-13 21:14 ` 1.6ms jitter in rtc_wakeup (Re: 2.6.14-rc4-rt1) Esben Nielsen
2005-10-14 3:45 ` Ingo Molnar
2005-10-14 21:32 ` Esben Nielsen
2005-10-19 7:52 ` Esben Nielsen
2005-10-19 16:04 ` Petr Vandrovec
2005-10-19 18:07 ` ktimer hiccup in rt11 David Singleton
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=1129314939.4652.4.camel@cmn3.stanford.edu \
--to=nando@ccrma.stanford.edu \
--cc=dsingleton@mvista.com \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--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
all inboxes | Powered by JetHome®