Total hard lockup when running rosegarden

Message

Higgaion · Post by **Higgaion** » Sun Feb 05, 2006 9:46 pm

I mean were talking an absolutely unresponsive lockup.

I tried ssh from another gentoo machine on my lan and no dice. totaly dead. This has happened to me twice recently, and i noticed that i was running rosegarden both times. The first time i played with rosegarden for a while and went to bed. the next morning the machine was totaly jammed. This time i just opened rosegarden and when i hit the open file button BOOM. dead.
My only lead is a similar death earlier in my gentoo experience with SEQ24. the program compiled and opened just fine, but then when i pushed play... same story, hardlock. this happened like three times and i says to myself... "must be something in the kernel" (basically because i figured it would take something deeply important to the os to cause such a vile crash ) I had this configuration under alsa sound:

Code: Select all

───────────────────────────────────────────────────────────────────┐ │
  │ │            <M> Advanced Linux Sound Architecture                    │ │
  │ │            <M>   Sequencer support                                  │ │
  │ │            < >     Sequencer dummy client                           │ │
  │ │            <M>   OSS Mixer API                                      │ │
  │ │            <M>   OSS PCM (digital audio) API                        │ │
  │ │            [ ]   OSS Sequencer API                                  │ │
  │ │            <M>   RTC Timer support                                  │ │
  │ │            [*]     Use RTC as default sequencer timer               │ │

i unchecked this box:

Code: Select all

  │ │            []     Use RTC as default sequencer timer               │ │

on a whim ( mainly because RTC sounds demanding ? ), recompiled, and SEQ24 has worked pretty well since. so this is the kernel that is now giving me so much troubble. all versions of all relevant packages are the latest from portage, except i've got alsa-lib1.0.11_rc3, and alsa-headers1.0.11_rc3 as recomended by the alsa-users list to get two descreet stereo inputs in jack from my emu10k1. so those are masked packages. other than that it's all been deemed stable. my kernel is 2.6.14-gentoo-r5

Code: Select all

# cat /etc/portage/package.keywords
x11-base/x11-drm ~x86
media-sound/ardour
x11-misc/smeg
media-libs/dssi
media-libs/liblo
media-libs/fluidsynth-dssi
media-sound/seq24
media-sound/alsa-headers ~x86
media-libs/alsa-lib ~x86

please help. i could live without rosegarden, i suppose, if that is really the problem, but i want to know why my system is unstable.

Higgaion · Post by **Higgaion** » Tue Feb 07, 2006 3:06 am

*bump*

Higgaion · Post by **Higgaion** » Wed Feb 08, 2006 1:03 am

maybe it has something to do with running rosegarden under Gnome? has anyome else had problems there?

norb · Post by **norb** » Sat Feb 25, 2006 6:28 pm

Hi,

Not a very useful reply but I thought i'd let you know you are not alone. I just had the same problem. After booting up into Gnome and running Rosegarden the machine locks up at the 'Clean studio data...' (or similar) stage of the splash screen.
In the past I've managed to get Rosegarden running quite happily so I suspect something having gone wrong after an update (of it or some other package). It's quite surprising that it can lock the machine up, I didn't realise that really happened anymore - perhaps it's a kernel/module thing in that case?
Sorry this is a bit vague, if I get anywhere with working it out I'll post back.

Cheers,
-Nige

Higgaion · Post by **Higgaion** » Sun Feb 26, 2006 1:16 am

Nige, have you tried the latest muse in portage? it's pretty stable. no score view, though...

norb · Post by **norb** » Fri Apr 28, 2006 1:53 pm

Argh, this is driving me mad!

I still haven't managed to get it working. However, I might have tracked the problem down a little closer to the source (MIDI Input).
I spotted that Rosegarden works when started as root. MIDI output works fine but no MIDI input.
The Manage MIDI Devices dialog shows the following:

Play devices:
General MIDI Device 16:0 MPU-401 MIDI 0-0 (duplex)
MIDI output system device No connection

Record devices:
MIDI hardware input device 16:0 MPU-401 MIDI 0-0 (duplex)
MIDI input system device No connection

Neither of the record devices have the check box indicating 'current' checked.
As soon as I click on the 'Current' check box for the 'MIDI hardware input device' the machine locks up totally.
Museseq seems to have the same problem.

Are there any lightweight packages which would help to diagnose the problem further? Preferrably something that runs from the command line.

I have a C-Media CM8738 sound card.

If anyone knows anything about this I'd greatly appreciate the help.

Cheers,
-Nige

Higgaion · Post by **Higgaion** » Fri Apr 28, 2006 4:17 pm

Well if you just want to do some midi diagnosics, try amidi.
i believe it's in the alsa-utils package. amidi -l will list your midi ins and outs.

norb · Post by **norb** » Sat Apr 29, 2006 12:29 am

Cool, thanks. That led me to thinking about how I could simplify the problem by removing Rosegarden (etc).
The Alsa Wiki has info about MIDI and mentions aconnect.
Basically, I followed their examples and installed vkeybd (virtual midi keyboard) and fluidsynth (virtual synth).

Initally, aconnect shows the following as input and output MIDI ports:

Code: Select all

nige@sully ~ $ aconnect -i -o
client 0: 'System' [type=kernel]
    0 'Timer           '
    1 'Announce        '
client 14: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
client 16: 'MPU-401 MIDI 0-0' [type=kernel]
    0 'MPU-401 MIDI 0-0'

After starting vkeybd and fluidsynth:

Code: Select all

nige@sully ~ $ aconnect -i -o
client 0: 'System' [type=kernel]
    0 'Timer           '
    1 'Announce        '
client 14: 'Midi Through' [type=kernel]

    0 'Midi Through Port-0'
client 16: 'MPU-401 MIDI 0-0' [type=kernel]
    0 'MPU-401 MIDI 0-0'
client 128: 'Virtual Keyboard' [type=user]
    0 'Virtual Keyboard'
client 129: 'FLUID Synth (7495)' [type=user]
    0 'Synth input port (7495:0)'

Hooking together the keyboard and fluidsynth works (after loading a soundfont into fluidsynth). Playing notes on the virtual keyboard makes audio from the sound card:

Code: Select all

nige@sully ~ $ aconnect 128:0 129:0

Disconnect fluidsynth and vkeybd and connect vkeybd to the MIDI port (with a hardware synth attached). Playing notes on the virtual keyboard makes noises from the external synth:

Code: Select all

nige@sully ~ $ aconnect -d 128:0 129:0
nige@sully ~ $ aconnect 128:0 16:0

Trying to connect the MIDI port (with external keyboard attached) to fluidsynth causes the system lock up:

Code: Select all

nige@sully ~ $ aconnect 16:0 129:0

An even simpler way to get the system to lock up is to use aseqdump, this can be done straight after boot up without having to start X or anything:

Code: Select all

nige@sully ~ $ aseqdump -p 16:0

I presume that the system locking up means it's a kernel thing (in either a module or the main kernel).
Does anyone know of a way to get more information out from the kernel before it locks up to help pinpoint the problem?

Cheers,
-Nige

Higgaion · Post by **Higgaion** » Sat Apr 29, 2006 9:10 pm

I had some problems with seq24, midi in, and my RTC options in the kernel. I believe the culprit was the "use RTC as default timer" option.
so if you've got that checked, try recompiling without it. if that doesn't help, or even if it does, join the linux-audio-user mailing list! that's where a swell group of LA enthusiasts will argue about your problems and maybe even solve them

gimpel · Post by **gimpel** » Sat Apr 29, 2006 10:55 pm

wow.. i'm not allone.. rosegarden locks up my box too while starting up - no matter if i use alsa or jackd. and i never have been able to trace it as the kernel doesn't even react on sysrq+t/s/u/b whatever..

all hail MusE

norb · Post by **norb** » Wed Jun 28, 2006 2:50 pm

Hi all,

I just thought I'd give an update on my situation in case it helps others in the future.
I posted to Linux-Audio-User (http://www.music.columbia.edu/pipermail ... 35274.html)
and finally Alsa-Devel (http://sourceforge.net/mailarchive/mess ... d=17776961) where Takashi Iwai replied with a patch to fix my problem.
I believe he will fix the problem in future versions of the driver.

Hope this helps,
-Nige

GWilliam · Post by **GWilliam** » Mon Mar 30, 2009 6:55 am

#NULL

GWilliam · Post by **GWilliam** » Sun Apr 12, 2009 8:10 pm

#NULL

Clad in Sky · Post by **Clad in Sky** » Mon Apr 13, 2009 6:56 am

Nothing really, but I thought I'd just report that for me rosegarden works well in Gnome.
I don't use midi in, though. I'm mainly interested in the score view and printing function.
Midi Out works, however using timidity.

Hope this helps a bit.

GWilliam · Post by **GWilliam** » Mon Apr 13, 2009 9:40 pm

#NULL

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

#NULL

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

Uh...sorry.

Onboard sound using the snd_hda_intel driver.

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

#NULL

GWilliam · Post by **GWilliam** » Tue Dec 29, 2009 11:23 pm

#NULL

GWilliam · Post by **GWilliam** » Fri May 14, 2010 1:32 am

#NULL

GWilliam · Post by **GWilliam** » Sun Jun 20, 2010 6:26 am

#NULL

gimpel · Post by **gimpel** » Mon Jun 21, 2010 9:03 am

Seems it's taking them years to understand that this is a rosegarden bug, not ALSA (at least no other application exhibits that behaviour)

http://www.mail-archive.com/rosegarden- ... 14769.html

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

#NULL