From: Benny Sjostrand <gorm@cucumelo.org>
To: Arthur Peters <amp@singingwizard.org>
Cc: Alsa dev list <alsa-devel@lists.sourceforge.net>
Subject: Re: ALSA + jack + xrun = kernel crash
Date: Sat, 17 May 2003 22:57:56 +0200 [thread overview]
Message-ID: <3EC6A254.4010303@cucumelo.org> (raw)
In-Reply-To: 1053136440.1197.213.camel@newbie.localnet.local
>
>
>Hello, I am experiencing a reletivly hard crash (SysRq works but SysRq-B
>prints a message saying it will reboot then doesn't). The crash happens
>when jackd xruns. I've been reproducing it using "jackd -d alsa" (other
>options don't make a difference) then "ladccad". Once the system crashs
>the only way to get any responce is with SysRq. Keys don't echo to the
>console and I can't switch VTs.
>
>Generally there is no error message or oops that I can see, even when
>debug=full is enable in ALSA. Early on I saw a message from jackd to the
>tune of "error write 512 somethings to device", but I have not been able
>to reproduce it. I am willing to run any tests that might help. I use
>journaling filesystems ;-)
>
>My hardware is:
>Dual PIII 1Ghz with 512M RAM on a Tyan MB.
>SoundBlaster Live! Value
>ATI Radeon 8500 (using the closed-source ATI drivers; version 2.9.8)
>
>My software is:
>ALSA drivers 0.9.3a or current CVS
>Linux 2.4.20 (vanilla or gentoo patched)
>Jack 0.71.2
>Current Gentoo with testing packages enabled (~x86)
>
>
Just want to tell that I'm experiencing almost the same problem (I got a
Dual PIII 1Gz 256Mb
and two cs46xx soundcards)
After updating ALSA CVS today, jack is no longer able to start, it just
locks up my machine, and
sometimes even the SysRQ hack dont react. (I've been several hours today
fighting with this problem .....)
What I was able to find out from the SysRQ is that the EIP all the times
seems
to be somewhere at: c0153804 <.text.lock.inode+135/211>, or
sync_unlocked_inodes(...)
which dont make any sense to me. (?????????????)
One more interesting point is that if I start the jackd without the "-R"
flag jack starts for a while,
sometimes I'm able to even stop/kill it. But after that no program is
able to start or run correctly,
which feels like that something is seriously corrupted in the kernel.
Now, for first time in my life I've downgraded ALSA to a previous CVS
version, which seems
to work with JACK :(
/Benny
-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful,
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
next prev parent reply other threads:[~2003-05-17 20:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 1:54 ALSA + jack + xrun = kernel crash Arthur Peters
2003-05-17 12:27 ` Paul Davis
2003-05-17 12:47 ` Jaroslav Kysela
2003-05-17 20:48 ` Arthur Peters
2003-05-19 16:10 ` Takashi Iwai
2003-05-19 16:38 ` Paul Davis
2003-05-19 19:16 ` Benny Sjostrand
2003-05-20 8:46 ` Takashi Iwai
2003-05-21 0:32 ` Pieter Palmers
2003-05-21 10:33 ` Takashi Iwai
2003-05-21 11:35 ` Jaroslav Kysela
2003-05-21 11:49 ` Takashi Iwai
2003-05-21 12:54 ` Jaroslav Kysela
[not found] ` <3ECBCF5B.2020807@esat.kuleuven.ac.be>
2003-05-21 23:08 ` Pieter Palmers
2003-05-21 23:50 ` Tarragon Allen
2003-05-22 1:20 ` Paul Davis
2003-05-17 20:57 ` Benny Sjostrand [this message]
2003-05-17 21:38 ` Jaroslav Kysela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EC6A254.4010303@cucumelo.org \
--to=gorm@cucumelo.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=amp@singingwizard.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.