[ardour-dev] Keep crashing with Ardour2

Mr Machine forums at machinehasnoagenda.com
Tue Mar 28 05:02:16 PST 2006


this is making me lose my mind ...

for the past couple of days, recording in ardour has been next to
impossible:

i've got a song with about 10 tracks, no effects, and a length
approaching four minutes. i'm trying to record the final vocal track,
but each time i stop recording, ardour crashes and loses what i've
done :(

i got a bit of help from the irc channel on how to use gdb with ardour,
but of course it won't crash when i run my debug-build of ardour (i
thought it might pop out a core file, but no). running ardour from the
command line, the most it will tell me is: user defined signal 2.

i thought it might have been the fact that i have recently been using
the nightly cvs tarballs of ardour2, but falling back to ardour-alpha2
provides no joy, either (i made sure i deleted my ./.ardour folder
before reverting, too).

then i remembered that i'd updated my kernel to 2.6.16-rt7 recently, so
i checked dmesg after a crash, and i'm thinking this might be the
culprit:

hdc: DMA timeout retry
hdc: timeout waiting for DMA
hdc: irq timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hdc: ATAPI reset complete
ardour:9320 userspace BUG: scheduling in user-atomic context!
 [<c0372d78>] schedule+0x108/0x130 (8)
 [<c0372dae>] io_schedule+0xe/0x20 (36)
 [<c016503b>] sync_buffer+0x3b/0x50 (8)
 [<c0373335>] __wait_on_bit+0x45/0x70 (12)
 [<c0165000>] sync_buffer+0x0/0x50 (8)
 [<c0165000>] sync_buffer+0x0/0x50 (12)
 [<c03733dd>] out_of_line_wait_on_bit+0x7d/0x90 (8)
 [<c012ead0>] wake_bit_function+0x0/0x60 (24)
 [<c01dc2d7>] ext3_find_entry+0x187/0x650 (24)
 [<c01722b0>] vfs_permission+0x20/0x30 (32)
 [<c01e7844>] start_this_handle+0x3a4/0x470 (76)
 [<c01738dd>] link_path_walk+0x7d/0x130 (44)
 [<c01e7a19>] journal_start+0x109/0x140 (28)
 [<c01dcf6c>] ext3_unlink+0xbc/0x1a0 (44)
 [<c0171930>] may_delete+0x40/0x170 (20)
 [<c0171afc>] vfs_unlink+0x9c/0xa0 (28)
 [<c0174395>] do_unlinkat+0xe5/0x140 (24)
 [<c0163832>] sys_write+0x72/0x80 (56)
 [<c0102eff>] sysenter_past_esp+0x54/0x75 (40)
ardour:9463 userspace BUG: scheduling in user-atomic context!
 [<c0372d78>] schedule+0x108/0x130 (8)
 [<c0372dae>] io_schedule+0xe/0x20 (36)
 [<c016503b>] sync_buffer+0x3b/0x50 (8)
 [<c0373335>] __wait_on_bit+0x45/0x70 (12)
 [<c0165000>] sync_buffer+0x0/0x50 (8)
 [<c0165000>] sync_buffer+0x0/0x50 (12)
 [<c03733dd>] out_of_line_wait_on_bit+0x7d/0x90 (8)
 [<c012ead0>] wake_bit_function+0x0/0x60 (24)
 [<c01dc2d7>] ext3_find_entry+0x187/0x650 (24)
 [<c01722b0>] vfs_permission+0x20/0x30 (32)
 [<c01e7844>] start_this_handle+0x3a4/0x470 (76)
 [<c01738dd>] link_path_walk+0x7d/0x130 (44)
 [<c01e7a19>] journal_start+0x109/0x140 (28)
 [<c01dcf6c>] ext3_unlink+0xbc/0x1a0 (44)
 [<c0171930>] may_delete+0x40/0x170 (20)
 [<c0171afc>] vfs_unlink+0x9c/0xa0 (28)
 [<c0174395>] do_unlinkat+0xe5/0x140 (24)
 [<c0163832>] sys_write+0x72/0x80 (56)
 [<c0102eff>] sysenter_past_esp+0x54/0x75 (40)
ardour:9513 userspace BUG: scheduling in user-atomic context!
 [<c0372d78>] schedule+0x108/0x130 (8)
 [<c0372dae>] io_schedule+0xe/0x20 (36)
 [<c016503b>] sync_buffer+0x3b/0x50 (8)
 [<c0373335>] __wait_on_bit+0x45/0x70 (12)
 [<c0165000>] sync_buffer+0x0/0x50 (8)
 [<c0165000>] sync_buffer+0x0/0x50 (12)
 [<c03733dd>] out_of_line_wait_on_bit+0x7d/0x90 (8)
 [<c012ead0>] wake_bit_function+0x0/0x60 (24)
 [<c0167efd>] __bread+0x8d/0xc0 (24)
 [<c01d6926>] ext3_free_branches+0x96/0x250 (20)
 [<c01d903a>] ext3_truncate+0x97a/0xa20 (60)
 [<c011556c>] __wake_up+0x3c/0x70 (20)
 [<c01e7a19>] journal_start+0x109/0x140 (64)
 [<c01d5da4>] start_transaction+0x24/0x60 (44)
 [<c01d91d6>] ext3_delete_inode+0xf6/0x130 (24)
 [<c01d90e0>] ext3_delete_inode+0x0/0x130 (16)
 [<c017e869>] generic_delete_inode+0x69/0x110 (8)
 [<c01743c0>] do_unlinkat+0x110/0x140 (24)
 [<c0163832>] sys_write+0x72/0x80 (56)
 [<c0102eff>] sysenter_past_esp+0x54/0x75 (40)
ardour:14353 userspace BUG: scheduling in user-atomic context!
 [<c0372d78>] schedule+0x108/0x130 (8)
 [<c0372dae>] io_schedule+0xe/0x20 (36)
 [<c016503b>] sync_buffer+0x3b/0x50 (8)
 [<c0373335>] __wait_on_bit+0x45/0x70 (12)
 [<c0165000>] sync_buffer+0x0/0x50 (8)
 [<c0165000>] sync_buffer+0x0/0x50 (12)
 [<c03733dd>] out_of_line_wait_on_bit+0x7d/0x90 (8)
 [<c012ead0>] wake_bit_function+0x0/0x60 (24)
 [<c01dc2d7>] ext3_find_entry+0x187/0x650 (24)
 [<c01722b0>] vfs_permission+0x20/0x30 (32)
 [<c01e7844>] start_this_handle+0x3a4/0x470 (76)
 [<c01738dd>] link_path_walk+0x7d/0x130 (44)
 [<c01e7a19>] journal_start+0x109/0x140 (28)
 [<c01dcf6c>] ext3_unlink+0xbc/0x1a0 (44)
 [<c0171930>] may_delete+0x40/0x170 (20)
 [<c0171afc>] vfs_unlink+0x9c/0xa0 (28)
 [<c0174395>] do_unlinkat+0xe5/0x140 (24)
 [<c0163832>] sys_write+0x72/0x80 (56)
 [<c0102eff>] sysenter_past_esp+0x54/0x75 (40)
ardour:14431 userspace BUG: scheduling in user-atomic context!
 [<c0372d78>] schedule+0x108/0x130 (8)
 [<c0372dae>] io_schedule+0xe/0x20 (36)
 [<c016503b>] sync_buffer+0x3b/0x50 (8)
 [<c0373335>] __wait_on_bit+0x45/0x70 (12)
 [<c0165000>] sync_buffer+0x0/0x50 (8)
 [<c0165000>] sync_buffer+0x0/0x50 (12)
 [<c03733dd>] out_of_line_wait_on_bit+0x7d/0x90 (8)
 [<c012ead0>] wake_bit_function+0x0/0x60 (24)
 [<c01dc2d7>] ext3_find_entry+0x187/0x650 (24)
 [<c01722b0>] vfs_permission+0x20/0x30 (32)
 [<c01e7844>] start_this_handle+0x3a4/0x470 (76)
 [<c01738dd>] link_path_walk+0x7d/0x130 (44)
 [<c01e7a19>] journal_start+0x109/0x140 (28)
 [<c01dcf6c>] ext3_unlink+0xbc/0x1a0 (44)
 [<c0171930>] may_delete+0x40/0x170 (20)
 [<c0171afc>] vfs_unlink+0x9c/0xa0 (28)
 [<c0174395>] do_unlinkat+0xe5/0x140 (24)
 [<c0163832>] sys_write+0x72/0x80 (56)
 [<c0102eff>] sysenter_past_esp+0x54/0x75 (40)


i'm not that familiar with this type of message, but i assume it is
entirely related to a kernel bug, and nothing to do with ardour?

i'm not quite sure where to go with this, so sorry if this is the wrong
place, but this track i'm working on is for a demo comp that closes on
friday (i know, i know - pretty stupid to use software that is only in
alpha stage for something important, but me just can't use ardour1 after
experiencing the - previous - brilliance of ardour2) ... help please!

shayne





More information about the Ardour-Dev mailing list