Rosegarden 4.1 + emu10k1 (+ AMD64?) => System Deadlock

Message

datenwolf · Post by **datenwolf** » Thu Nov 16, 2006 12:28 am

I recently dicovered a weird bug, which exact location I'm unable to pin down. After a system update (emerge -uD system; emerge -uD world) starting Rosegarden causes my system to deadlock. I mean really deadlock nothing can reawake it, even the Magic-SysReq seems unable to work (though I'm using a USB keybord and only the USB subsystem might have died). The system also doesn't respond to pings or similair stuff. Only pressing the reset button helps.

I'm pretty sure, that it is related to the combination Rosegarden + emu10k1 It deadloacks with both the in kernel tree drivers and the separate alsa-driver drivers. Unloading the emu10k1 modules and using the snd_dummy, snd_seq_dummy drivers and then starting Rosegarden works flawlessly.

All parts of the system have been compiled with gcc-3.4.6-vanilla

Any other music composing / audio editing related software works fine though, among others these are jackd, ardour, museseq and hydrogen. To enable realtime access for jack I also got the realtime-lsm module loaded.

The system is a AMD64 X2 4400+, 2GiB RAM on an ASUS P8N-Deluxe, nVidia GF7800GT (x11-drivers/nvidia-drivers). The Kernel is gentoo-sources-2.6.17-r8. The last message to be seen from Rosegarden just before the lockup is, that is about finishing the emu10k1 sequencer initialisation. The minor version of Rosegarden doesn't matter, it happens with all 4.1.x versions of it. jackd is version 0.101.1-r1.

Please could other people with a similair system check if they can (not) reproduce this bug.

bugg_tb · Post by **bugg_tb** » Thu Nov 16, 2006 6:53 pm

Well I haven't tried it with other sound cards or dummies but mine locks before the splash screen has disappeared and I can't do a thing with it.

Emu10k1,
2.6.17-r8 gentoo kernel
P4
gcc-4.1.1

xHemi · Post by **xHemi** » Sat Dec 30, 2006 7:21 pm

Same issue here(unresolved), cannot load rosegarden without total system deadlock. Not using jack.

Using:

Code: Select all

snd_emu10k1

media-sound/rosegarden-4.1.0-r2
sys-devel/gcc-4.1.1

System uname: 2.6.17-gentoo-r8 i686 Intel(R) Pentium(R) 4 CPU 2.53GHz
Gentoo Base System version 1.12.5

CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=pentium4 -O2 -pipe -mfpmath=sse -msse"

Enverex · Post by **Enverex** » Sat Dec 30, 2006 7:30 pm

Audigy 1 here (emu10k1) on AMD64 with RoseGarden 4.1 and it works fine for me, makes a change, hah.

xHemi · Post by **xHemi** » Sat Dec 30, 2006 7:36 pm

Enverex wrote:Audigy 1 here (emu10k1) on AMD64 with RoseGarden 4.1 and it works fine for me, makes a change, hah.

Good to know but you didn't state if you used emu10k1 drivers from alsa-drivers or kernel supplied, and if so what kernel you are running. But I'm assuming identical setup..
Anyway I'm going to try to run on top of jack instead to see if it helps.

xHemi · Post by **xHemi** » Sat Dec 30, 2006 8:10 pm

looks like I spoke to soon..
installing (USE=jack emerge rosegarden) and running on top of jackd didn't resolve my issues. It did help me fire up the application but when I set jackd to actually use my card, configuration I missed yesterday, it froze once again.

Code: Select all

cat /proc/interrupts
           CPU0
  0:     165746    IO-APIC-edge  timer
  1:        293    IO-APIC-edge  i8042
  7:          0    IO-APIC-edge  parport0
  8:          2    IO-APIC-edge  rtc
 14:      21090    IO-APIC-edge  ide0
 15:        101    IO-APIC-edge  ide1
 16:     122269   IO-APIC-level  nvidia
 17:       4807   IO-APIC-level  eth0
 18:          2   IO-APIC-level  EMU10K1, uhci_hcd:usb2, ehci_hcd:usb5
 19:          0   IO-APIC-level  CMI8738-MC6, ohci_hcd:usb3
 20:       4495   IO-APIC-level  uhci_hcd:usb1
 22:         33   IO-APIC-level  acpi, ohci_hcd:usb4
NMI:          0
LOC:     165722
ERR:          0
MIS:          0

So it seems, in my case, to be a IRQ collision. I'm guessing EMU10K1 doesn't like to share

Enverex · Post by **Enverex** » Sat Dec 30, 2006 8:14 pm

xHemi wrote:
Enverex wrote:Audigy 1 here (emu10k1) on AMD64 with RoseGarden 4.1 and it works fine for me, makes a change, hah.
Good to know but you didn't state if you used emu10k1 drivers from alsa-drivers or kernel supplied, and if so what kernel you are running. But I'm assuming identical setup..
Anyway I'm going to try to run on top of jack instead to see if it helps.

Sorry, kernel is Gentoo-2.6.19-r2 and I believe I swapped audio drivers at one point so I've tried both in kernel and ALSA ebuild.

charles_elwood · Post by **charles_elwood** » Mon Jan 01, 2007 4:47 pm

There is a slight 'issue' with the rosegarden numbering.

Rosegarden-2.x Original unmaintiend application
Rosegarden 4.x.x Complete rewrite of rosegarden-2 using Qt
Rodegarden-1.2.x == rosegarden-4.1.2.x
Rosegaredn-1.4 == Latest version, major feature relase, massive improvements in stability.

GWilliam · Post by **GWilliam** » Mon Mar 26, 2007 6:20 am

#NULL

GWilliam · Post by **GWilliam** » Mon Mar 26, 2007 6:27 am

#NULL

Matrix7 · Post by **Matrix7** » Thu Mar 29, 2007 7:15 pm

Try compiling Rosegarden without arts support.

USE="-arts" emerge rosegarden.

I find that Rosegarden won't play using arts, but with alsa it's fine.

gimpel · Post by **gimpel** » Thu Mar 29, 2007 8:46 pm

GWilliam wrote:Perhaps this might shed some light on the problem?

http://sourceforge.net/mailarchive/mess ... d=17776961

Uhm...

Would you like to receive every morning Italian news directly in your mailbox, ABSOLUTELY FREE ?...

rofl...

Rosegarden hardlocks too here, and hardlocks on a lot of other systems. Envy24 chip here and I know of hardlocks on Other Systems with Envy24 too. Last version I tried is 1.4, currently compiling 1.5.1 - let's see.

Good to see it's not Envy24 related

Start from a terminal, here it's around the time when it tries to initialize the MIDI device stuff.

gimpel · Post by **gimpel** » Fri Mar 30, 2007 7:32 am

Heh, rosegarden 1.5.1 still hardlocks. x86 here btw.

Well, forget about that crap, use museseq

GWilliam · Post by **GWilliam** » Mon Jul 30, 2007 4:06 am

#NULL

alfton · Post by **alfton** » Mon Nov 05, 2007 12:50 pm

ah good to see more people with the same problem.

Rosegarden works fine without activating the Xf-i sound card. But when i activate it Rosegarden totaly lock my system down
I try to start "rosegardensequencer" in console to se messages, and it look like to me that is when it loading the stuff.

i think it is when i inisiating device thing are crashing for it

it come to Creating device 3 in playmode for connetion 17:3 creative x-fi port 3 [df00]
default device name for this device is midi synth 4
connecting my port 7 to 16:0 on intitialisation.

Well sorry for my bad english, but is someone have anny clue on what may be wrong, i would be werry happy.

GWilliam · Post by **GWilliam** » Tue Jan 08, 2008 4:44 am

#NULL

alfton · Post by **alfton** » Fri Jan 11, 2008 11:42 am

I'm afread this deadlock is driver related, it's not rosegardens foult. So we just have to be pationts, and hope creative, or some else come with bethere more stable driver.

GWilliam · Post by **GWilliam** » Sun Nov 29, 2009 3:46 am

#NULL

Clad in Sky · Post by **Clad in Sky** » Sun Nov 29, 2009 9:33 am

What's this, necrothreading?

Anyway, for me rosegarden works well. I've got version 1.7 running on Gnome.
These are my useflags:
media-sound/rosegarden-1.7.3 USE="alsa -debug -dssi -jack -lirc"
So, just alsa.
I assume you have alsasound up and running and all other sound works.

Could you run rosegarden from a terminal - this might give some info where it all goes wahoonie-shaped.

GWilliam · Post by **GWilliam** » Sun Dec 13, 2009 1:55 am

#NULL

GWilliam · Post by **GWilliam** » Tue Jun 01, 2010 2:56 am

#NULL