public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Adrian Bunk <bunk@stusta.de>,
	sfrench@samba.org, linux-cifs-client@lists.samba.org,
	samba-technical@lists.samba.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc: CIFS reproducibly freezes the computer
Date: Tue, 14 Feb 2006 13:33:21 -0500	[thread overview]
Message-ID: <1139942002.11659.133.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.61.0602141911470.32490@yvahk01.tjqt.qr>

On Tue, 2006-02-14 at 19:12 +0100, Jan Engelhardt wrote:
> >"Complete freeze" is:
> >[..]
> >  is played in an endless loop by the sound chip
> 
> Sounds like a portion of code disabled interrupts?

Anything that locks the machine while sound is playing will cause the
last period of audio to repeat in an endless loop, because the DMA
engine keeps running but the soundcard isn't getting new data.  It's not
specific to interrupt disabling.

Isn't it fortunate that network cards don't work this way? ;-)

Lee


  reply	other threads:[~2006-02-14 18:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-14 13:50 2.6.16-rc: CIFS reproducibly freezes the computer Adrian Bunk
2006-02-14 15:00 ` Marc Koschewski
2006-02-14 15:59 ` Christian
2006-02-14 16:40   ` Marc Koschewski
2006-02-14 18:47     ` Ross Vandegrift
2006-02-15 13:35       ` Marc Koschewski
2006-02-15 16:47         ` Ross Vandegrift
2006-02-16 12:11         ` Adrian Bunk
2006-02-16 13:32           ` Marc Koschewski
2006-02-27  6:29       ` Adrian Bunk
2006-02-28  3:02         ` Ross Vandegrift
2006-02-14 18:12 ` Jan Engelhardt
2006-02-14 18:33   ` Lee Revell [this message]
     [not found] ` <OFD6EC212C.9D3CD1CC-ON87257115.0057751D-86257115.0057E155@us.ibm.com>
2006-02-16 12:07   ` [linux-cifs-client] " Adrian Bunk

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=1139942002.11659.133.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=bunk@stusta.de \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox