All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000705]: RME96 Driver crashes
Date: Mon, 13 Dec 2004 19:28:27 +0100	[thread overview]
Message-ID: <0cde21842fd208be47690604352c8876@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=705> 
======================================================================
Reported By:                FishB8
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   705
Category:                   PCI - RME 96
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
Distribution:               Gentoo
Kernel Version:             2.6.9
======================================================================
Date Submitted:             12-03-2004 23:43 CET
Last Modified:              12-13-2004 19:28 CET
======================================================================
Summary:                    RME96 Driver crashes
Description: 
Something has changed in the RME96 driver between 1.0.6 and 1.0.7 causeing
it to crash. Whenever an audio program uses ALSA and stops playing the
driver hangs. When trying to start JACK, it never gets started but the CPU
hits 100%. It's impossible to kill any of the programs because any program
dealing with processes hangs as well. The system will not totally shut
down and has to be reset. Kernel 2.6.8 works just fine.
======================================================================

----------------------------------------------------------------------
 FishB8 - 12-12-04 23:35 
----------------------------------------------------------------------
In case it makes any difference, my configure options for jack are:

./configure --prefix=/usr --enable-posix-shm --enable-mmx --enable-sse
--enable-timestamps --enable-preemption-check --enable-capabilities
--disable-oldtrans --disable-portaudio --disable-oss

(currently using 0.99.28)

CFLAGS/CXXFLAGS are:

-O3 -march=athlon-xp -mfpmath=sse -mmmx -msse -m3dnow -funroll-loops
-fprefetch-loop-arrays -fomit-frame-pointer -pipe


alsalib is 1.0.7

----------------------------------------------------------------------
 martin - 12-13-04 19:28 
----------------------------------------------------------------------
still no progress. jackd aborts on different machines always (more or less
cleanly) with my rme32: 

#jackd -R -d alsa -P hw:x,0:

jackd 0.99.30
JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:0,0|-|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
nperiods = 16 for playback
Noise-shaped dithering at 16 bits
too many consecutive interrupt delays ... engine pausing
cycle execution failure, exiting
DRIVER NT: could not run driver cycle
delay of 298841.000 usecs exceeds estimated spare time of 20897.000;
restart ...
delay of 298841.000 usecs exceeds estimated spare time of 20897.000;
restart ...
delay of 298841.000 usecs exceeds estimated spare time of 20897.000;
restart ...
delay of 298841.000 usecs exceeds estimated spare time of 20897.000;
restart ...
delay of 298841.000 usecs exceeds estimated spare time of 20897.000;
restart ...
delay of 298841.000 usecs exceeds estimated spare time of 20897.000;
restart ...
delay of 298841.000 usecs exceeds estimated spare time of 20897.000;
restart ...
delay of 298841.000 usecs exceeds estimated spare time of 20897.000;
restart ...
delay of 298841.000 usecs exceeds estimated spare time of 20897.000;
restart ...
delay of 298841.000 usecs exceeds estimated spare time of 20897.000;
restart ...
delay of 298841.000 usecs exceeds estimated spare time of 20897.000;
restart ...
jack main caught signal 12
received signal 2 during shutdown (ignored)
jackd watchdog: timeout - killing jackd
Killed

Well, OTOH my via82xx runs fine with the same command on the same
machine.

Hmm, I don't see the core of the problem. It's so dark ... I'm a little
bit lost.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
12-03-04 23:43 FishB8         New Issue                                    
12-03-04 23:43 FishB8         File Added: config                           
12-03-04 23:43 FishB8         Distribution              => Gentoo          
12-03-04 23:43 FishB8         Kernel Version            => 2.6.9           
12-04-04 12:30 martin         Note Added: 0002715                          
12-04-04 17:56 FishB8         Note Added: 0002717                          
12-04-04 19:21 FishB8         Note Added: 0002718                          
12-04-04 20:18 eradicator     Issue Monitored: eradicator                    
12-07-04 18:44 tiwai          Note Added: 0002758                          
12-07-04 23:06 FishB8         Note Added: 0002768                          
12-08-04 12:08 tiwai          Note Added: 0002776                          
12-09-04 00:22 FishB8         Note Added: 0002796                          
12-09-04 11:22 tiwai          Note Added: 0002798                          
12-12-04 20:04 martin         Note Added: 0002819                          
12-12-04 23:35 FishB8         Note Added: 0002820                          
12-13-04 19:28 martin         Note Added: 0002822                          
======================================================================




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

             reply	other threads:[~2004-12-13 18:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-13 18:28 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-14 18:31 [ALSA - driver 0000705]: RME96 Driver crashes bugtrack
2005-01-12 14:05 bugtrack
2005-01-12 11:53 bugtrack
2005-01-12  1:46 bugtrack
2004-12-16 17:27 bugtrack
2004-12-15 19:06 bugtrack
2004-12-15  5:09 bugtrack
2004-12-12 22:35 bugtrack
2004-12-12 19:04 bugtrack
2004-12-09 10:22 bugtrack
2004-12-08 23:22 bugtrack
2004-12-08 11:08 bugtrack
2004-12-07 22:06 bugtrack
2004-12-07 17:44 bugtrack
2004-12-04 18:21 bugtrack
2004-12-04 16:56 bugtrack
2004-12-04 11:30 bugtrack
2004-12-03 22:43 bugtrack

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=0cde21842fd208be47690604352c8876@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.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.