linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: phandel@cise.ufl.edu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: DMASOUND->rev6  (2.4.3)(attn: Xine, MOL, PowerComputing, ibook, Tumbler)
Date: Sat, 07 Apr 2001 11:56:06 +0100	[thread overview]
Message-ID: <20010407105610.94080DBA03@atlas.valhalla.net> (raw)


>>  - fix bug where TX stops when dbdma status comes up "DEAD"
>>    so far only reported on PowerComputing clones ... but.
>>    (PowerComputing clones - NOT TESTED - please let me know what happens).
>
> Nope, I can still kill sound by merely moving the mouse.  Here is the new
> line from the console:
>
> Apr  7 03:31:13 like kernel: dmasound_pmac: tx-irq: xfer died - patching
> it up...
>
> ...but sound is dead, along with the player app, just as before.

damn... so much for the dbdma manual... :-(

what do you _have_ to do to re-start the sound?
kill & re-start the app?
close & re-open /dev/dsp?
un-load & re-load the module?
- or reboot?

can you make sure it's not the app that's stopping?
(or is this equally the case with _any_ app?)

If you have a big-ish file (although it doesn't sound like you need very
big) then my stest program would do to test it... it's *very* simple and
therefore should eliminate lots of other possibilities ;-)

ciao,
Iain.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-04-07 10:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-07 10:56 Iain Sandoe [this message]
2001-04-07 20:56 ` DMASOUND->rev6 (2.4.3)(attn: Xine, MOL, PowerComputing, ibook, Tumbler) phandel
  -- strict thread matches above, loose matches on Subject: below --
2001-04-09  0:21 Iain Sandoe
2001-04-08 14:47 Iain Sandoe
2001-04-08 20:30 ` Michael Schmitz
2001-04-07 11:56 Iain Sandoe
2001-04-06  6:51 Iain Sandoe
2001-04-06  0:19 Henry Worth
2001-04-05 11:33 Iain Sandoe
2001-04-05 11:09 Iain Sandoe
2001-04-07 10:39 ` phandel

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=20010407105610.94080DBA03@atlas.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=phandel@cise.ufl.edu \
    /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;
as well as URLs for NNTP newsgroup(s).