[PlanetCCRMA] wierd hanging of jack, or some other process using fc3 edge kernel

Shayne O'Connor forums@machinehasnoagenda.com
Mon Apr 4 16:26:01 2005


On Mon, 2005-04-04 at 12:57 -0700, Fernando Lopez-Lezcano wrote:
> On Mon, 2005-04-04 at 04:56, Shayne O'Connor wrote:
> > this is pretty vague, but i've been getting sporadic hanging of - i
> > think - the jack daemon with the latest CCRMA edge kernel for fedora
> > core 3.
> > 
> > what happens is this. either:
> > 
> > * i start jack with qjackctl, and then have a session with ardour,
> > hydrogen, and maybe some VST effects. sometimes, after closing hydrogen
> > and ardour, i'll press the "stop" button on qjactctl - but it will just
> > hang at that inbetween "stopping" state, never actually stopping
> > completely until i reboot.
> > 
> > * or, i go to start jack, which will fire up - but with no input/output
> > channels, and ardour complaining that the current song was recorded at
> > 48000khz, not 0hz (yes - that's the sample rate that qjackctl shows!).
> > if i then stop jack, it will stop, but will not start again until i
> > reboot. i guess there is some interesting messages when it shuts down,
> > too - when it tries to umount /home, it is busy, along
> > with /var/lib/jack/tmp. 
> > 
> > when i run gnome-system-monitor to try and kill jack, it doesn't show
> > jackd at all, but rather some blank processes that apparently aren't
> > using any resources, but are sure preventing my system from functioning
> > correctly.
> > 
> > here's a screenshot of the processes window:
> > 
> > http://www.machinehasnoagenda.com/images/unknown_process.gif
> >
> > this isn't happening *all* the time, but enough to move me to action :)
> 
> Have you looked at /var/log/messages or the output of dmesg? I smells
> like something is causing a kernel oops, and after that happens all bets
> are off in terms of how usable the system remains. 


i've dug through the system logs, but didn't find any explicity mentions
of a "kernel oops" (i've been wondering - what the heck *is* a "kernel
oops"?), but i've decided to include some of the errors and warnings i
did find in there. most of these probly have nothing at all to do with
the problem i describe, but i'll list them in what i think is their
order of relevance (if, indeed, they have any - if they don't, i'll post
some more pertinent ones as soon as it happens again):


Kernel Startup Log:

(ok, i have a spurios interrupt ... but apparently, these are nothing to
worry about?)

PCI: Using ACPI for IRQ routing
** PCI interrupts are no longer routed automatically.  If this
** causes a device to stop working, it is probably because the
** driver failed to call pci_enable_device().  As a temporary
** workaround, the "pci=routeirq" argument restores the old
** behavior.  If this argument makes the device work again,
** please email the output of "lspci" to bjorn.helgaas@hp.com
** so I can fix the driver.
spurious 8259A interrupt: IRQ7.
TC classifier action (bugs to netdev@oss.sgi.com cc hadi@cyberus.ca)



System Log:

Apr  4 21:30:35 localhost gdm(pam_unix)[3768]: session opened for user
mrmachine by (uid=0)
Apr  4 21:30:46 localhost gconfd (mrmachine-3987): starting (version
2.8.1), pid 3987 user 'mrmachine'
Apr  4 21:30:46 localhost gconfd (mrmachine-3987): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
configuration source at position 0
Apr  4 21:30:46 localhost gconfd (mrmachine-3987): Resolved address
"xml:readwrite:/home/mrmachine/.gconf" to a writable configuration
source at position 1
Apr  4 21:30:46 localhost gconfd (mrmachine-3987): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
configuration source at position 2
Apr  5 00:10:13 localhost gconfd (root-6581): starting (version 2.8.1),
pid 6581 user 'root'
Apr  5 00:10:13 localhost gconfd (root-6581): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
configuration source at position 0
Apr  5 00:10:13 localhost gconfd (root-6581): Resolved address
"xml:readwrite:/root/.gconf" to a writable configuration source at
position 1
Apr  5 00:10:13 localhost gconfd (root-6581): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
configuration source at position 2
Apr  5 00:11:11 localhost cups: cupsd -HUP succeeded
Apr  5 00:12:56 localhost cups: cupsd -HUP succeeded
iso-8859-1Apr  5 00:40:19 localhost bonobo-activation-server
(mrmachine-3989): Duff env. var 'ØÈâ·8'
iso-8859-1Apr  5 00:40:46 localhost bonobo-activation-server
(mrmachine-3989): Duff env. var 'ØÈâ·8'
iso-8859-1Apr  5 00:40:46 localhost bonobo-activation-server
(mrmachine-3989): Duff env. var 'ÿ7*'
iso-8859-1Apr  5 00:40:46 localhost bonobo-activation-server
(mrmachine-3989): Duff env. var '°n*è'
Apr  5 00:40:46 localhost bonobo-activation-server (mrmachine-3989):
Duff env. var ''
Apr  5 08:31:20 localhost shutdown: shutting down for system reboot
Apr  5 08:31:20 localhost init: Switching to runlevel: 6
Apr  5 08:31:20 localhost gconfd (mrmachine-3987): Received signal 15,
shutting down cleanly
Apr  5 08:31:20 localhost gconfd (mrmachine-3987): Exiting
Apr  5 08:31:21 localhost gdm(pam_unix)[3768]: session closed for user
mrmachine



Security Log:

(looking back through the system log, this one has kept popping up since
i installed FC3 - but's probly to do with my DNS server being at that
address)

Apr  5 08:32:33 localhost sshd[3087]: Server listening on :: port 22.
Apr  5 08:32:33 localhost sshd[3087]: error: Bind to port 22 on 0.0.0.0
failed: Address already in use.
Apr  5 08:45:32 localhost userhelper[4308]: pam_timestamp: `/' owner
GID != 0
Apr  5 08:45:35 localhost userhelper[4308]: pam_timestamp: `/' owner
GID != 0



Xorg log:

(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) Module ABI versions:
	X.Org ANSI C Emulation: 0.2
	X.Org Video Driver: 0.7
	X.Org XInput driver : 0.4
	X.Org Server Extension : 0.2
	X.Org Font Renderer : 0.4

.....

(WW) (1400x1050,Monitor0) mode clock 122MHz exceeds DDC maximum 110MHz
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "700x525" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "700x525" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "700x525" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (bad mode
clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (width too large for
virtual size)
(WW) NVIDIA(0): Not using mode "700x525" (height 1050 is larger than
(WW) NVIDIA(0):      EDID-specified maximum 1024)
(WW) NVIDIA(0): Not using mode "1152x768":
(WW) NVIDIA(0):   horizontal sync start (1178) not a multiple of 8
(WW) NVIDIA(0): Not using mode "576x384":
(WW) NVIDIA(0):   horizontal sync start (589) not a multiple of 8
(WW) NVIDIA(0): Not using mode "360x200":
(WW) NVIDIA(0):   horizontal sync start (378) not a multiple of 8
(**) NVIDIA(0): Validated modes for display device CRT-0:
(**) NVIDIA(0):      Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0
Hz
(**) NVIDIA(0):      Default mode "1280x960": 108.0 MHz, 60.0 kHz, 60.0
Hz
(**) NVIDIA(0):      Default mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0
Hz



Mail Log:

(probly nothing here, but just for the sake of completeness - but this
one occurs all the time, too, and is the annoying spam thing from
evolution ... )

Apr  5 08:42:27 localhost spamc[4276]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#1 of 3): Connection refused
Apr  5 08:42:28 localhost spamc[4276]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#2 of 3): Connection refused
Apr  5 08:42:29 localhost spamc[4276]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#3 of 3): Connection refused
Apr  5 08:42:30 localhost spamc[4276]: connection attempt to spamd
aborted after 3 retries
Apr  5 08:42:31 localhost spamd[4279]: spamd starting 
Apr  5 08:42:32 localhost spamd[4281]: server started on port 7830/tcp
(running version 3.0.2)