[ardour-dev] ardour bug?
forums at machinehasnoagenda.com
Tue Jun 7 00:04:48 PDT 2005
hmmmmm, not sure what to make of this,
i'd entered "dmesg" into a terminal to get a bit of info, and copped
this at the bottom:
ardour:4370 userspace BUG: scheduling in user-atomic context!
[<c034fe38>] schedule+0xb8/0x130 (8)
[<c0350bf5>] rwsem_down_read_failed+0x95/0x160 (36)
[<c0133ffc>] .text.lock.futex+0x5f/0xe3 (48)
[<c034fdb3>] schedule+0x33/0x130 (40)
[<c0122c57>] del_singleshot_timer_sync+0x17/0x70 (12)
[<c0114fc0>] default_wake_function+0x0/0x30 (28)
[<c0114fc0>] default_wake_function+0x0/0x30 (32)
[<c017434f>] do_poll+0x5f/0xd0 (20)
[<c0133e14>] do_futex+0x74/0xd0 (20)
[<c0133ee9>] sys_futex+0x79/0x110 (36)
[<c0102ccb>] sysenter_past_esp+0x54/0x75 (60)
i can't remember anything happening in ardour, as it had been at least a
few hours since using it and this message ... actually - there *was* a
crash, after performing some editing (really can't remember what) ...
if it shows up in dmesg, is it more likely to be a kernel bug? i'm using
2.6.12RC6 with latest rt_preempt patch.
More information about the Ardour-Dev