All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000952]: System freeze at end of MIDI playback
Date: Wed, 28 Jun 2006 00:03:59 +0200	[thread overview]
Message-ID: <e01efe2bcb78004dd609a4cf433ebda4@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=952> 
======================================================================
Reported By:                skunk
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   952
Category:                   PCI - emu10k1
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     new
Distribution:               Debian testing
Kernel Version:             2.6.8-2-k7
======================================================================
Date Submitted:             03-01-2005 06:28 CET
Last Modified:              06-28-2006 00:03 CEST
======================================================================
Summary:                    System freeze at end of MIDI playback
Description: 
Hardware: Sound Blaster Live! Value
Software: sfxload (for patch loading) and drvmidi (playback)

I often play a list of MIDI files. On a number of occasions---either at
the end of a MIDI song, or when I hit STOP---the computer has frozen hard.
The recurrence is rare enough to make this more an annoyance than a
showstopper, but then, I haven't been too keen on ferreting out this bug.

I am reporting this against ALSA from the 2.6.8 kernel, as that is what
I'm using now (Debian official package) but the same problem arose with
alsa-driver 1.0.8 (as compiled by me) on 2.4.29.

I could probably rig up something to start/stop MIDI playback repeatedly,
with a debug-compiled driver, but is there any way to get useful debugging
output when the bug takes the whole system down?
======================================================================

----------------------------------------------------------------------
 phorn - 06-27-06 23:43 
----------------------------------------------------------------------
I am also getting this bug pretty often (kernels 2.6.15 through 2.6.17.1).

I get no useful indication when using SMP.  The only way to tell is that
"pmidi" frezes in the "running" state, and half of the I/O devices
(keyboard, ethernet and sometimes harddrive) stop working.

I decided to disable SMP and then I got a nice kernel message which I
attached as kernel_spinlock-2.6.17.1-nosmp.txt

----------------------------------------------------------------------
 rlrevell - 06-28-06 00:03 
----------------------------------------------------------------------
Can you verify the bug is still present in the latest Hg sources?

Issue History
Date Modified  Username       Field                    Change              
======================================================================
03-01-05 06:28 skunk          New Issue                                    
03-01-05 06:28 skunk          Distribution              => Debian testing  
03-01-05 06:28 skunk          Kernel Version            => 2.6.8-2-k7      
09-19-05 10:10 jdthood        Note Added: 0006287                          
09-19-05 10:19 skunk          Note Added: 0006290                          
04-23-06 07:57 skunk          Note Added: 0009441                          
06-07-06 18:09 pen            Note Added: 0010085                          
06-07-06 18:09 pen            Issue Monitored: pen                         
06-07-06 18:23 rlrevell       Note Added: 0010086                          
06-07-06 19:45 pen            Note Added: 0010087                          
06-07-06 19:50 rlrevell       Note Added: 0010088                          
06-08-06 09:28 skunk          Note Added: 0010109                          
06-27-06 23:35 phorn          File Added: kernel_spinlock-2.6.17.1-nosmp.txt    
               
06-27-06 23:43 phorn          Note Added: 0010602                          
06-28-06 00:03 rlrevell       Note Added: 0010603                          
======================================================================



Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

             reply	other threads:[~2006-06-27 22:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27 22:03 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-06 13:37 [ALSA - driver 0000952]: System freeze at end of MIDI playback bugtrack
2006-07-06  8:14 bugtrack
2006-07-06  7:30 bugtrack
2006-07-05 11:20 bugtrack
2006-07-05  7:32 bugtrack
2006-07-05  3:34 bugtrack
2006-07-04 17:32 bugtrack
2006-07-04 15:56 bugtrack
2006-07-04 15:53 bugtrack
2006-07-04 15:46 bugtrack
2006-07-04 15:07 bugtrack
2006-07-04  5:20 bugtrack
2006-07-04  2:58 bugtrack
2006-07-04  1:23 bugtrack
2006-07-03 18:24 bugtrack
2006-07-03 16:05 bugtrack
2006-07-03  0:57 bugtrack
2006-07-02 13:37 bugtrack
2006-06-28  1:50 bugtrack
2006-06-27 21:43 bugtrack
2006-06-08  7:28 bugtrack
2006-06-07 17:50 bugtrack
2006-06-07 17:45 bugtrack
2006-06-07 16:23 bugtrack
2006-06-07 16:09 bugtrack
2006-04-23  5:57 bugtrack
2005-09-19  8:19 bugtrack
2005-09-19  8:10 bugtrack
2005-03-01  5:28 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=e01efe2bcb78004dd609a4cf433ebda4@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.