From: Ingo Molnar <mingo@elte.hu>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rc3-rt10 build problem (now rt12)
Date: Sun, 9 Oct 2005 06:33:41 +0200 [thread overview]
Message-ID: <20051009043341.GA30878@elte.hu> (raw)
In-Reply-To: <1128824015.5104.6.camel@cmn3.stanford.edu>
* Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU> wrote:
> This appears to be triggered from Freqtweak (a Jack application):
> Oct 8 18:48:00 cmn3 kernel: freqtweak:4705 userspace BUG: scheduling in
> user-atomic context!
> Oct 8 18:48:00 cmn3 kernel: [<c037c05b>] schedule+0xeb/0x100 (8)
> Oct 8 18:48:00 cmn3 kernel: [<c037d745>] rwsem_down_read_failed
> +0xa5/0x1c0 (28)
> Oct 8 18:48:00 cmn3 kernel: [<c01467ee>] .text.lock.futex+0xa9/0x2db
> (52)
> Oct 8 18:48:00 cmn3 kernel: [<c0130c46>] try_to_del_timer_sync
> +0x46/0x50 (32)
> Oct 8 18:48:00 cmn3 kernel: [<c0130c71>] del_timer_sync+0x21/0x30 (16)
> Oct 8 18:48:00 cmn3 kernel: [<c0121330>] default_wake_function
> +0x0/0x20 (32)
> Oct 8 18:48:00 cmn3 kernel: [<c0151b5c>] audit_syscall_exit+0x4c/0x400
> (12)
> Oct 8 18:48:00 cmn3 kernel: [<c0146589>] do_futex+0x69/0xf0 (24)
> Oct 8 18:48:00 cmn3 kernel: [<c0146674>] sys_futex+0x64/0x120 (24)
> Oct 8 18:48:00 cmn3 kernel: [<c0103471>] syscall_call+0x7/0xb (60)
could you enable CONFIG_DEBUG_PREEMPT and send me the same assert (which
will hopefully include a critical section list too).
Ingo
next prev parent reply other threads:[~2005-10-09 4:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 17:17 2.6.14-rc3-rt10 build problem Fernando Lopez-Lezcano
2005-10-07 11:41 ` Ingo Molnar
2005-10-07 19:55 ` 2.6.14-rc3-rt10 build problem (now rt12) Fernando Lopez-Lezcano
2005-10-07 21:16 ` Ingo Molnar
2005-10-07 22:56 ` Fernando Lopez-Lezcano
2005-10-07 23:11 ` Ingo Molnar
2005-10-09 2:13 ` Fernando Lopez-Lezcano
2005-10-09 4:33 ` Ingo Molnar [this message]
2005-10-09 18:38 ` Fernando Lopez-Lezcano
2005-10-11 0:50 ` 2.6.14-rc3-rt10 build problem (now rt13) Fernando Lopez-Lezcano
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=20051009043341.GA30878@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=nando@ccrma.Stanford.EDU \
/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.