All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pete Barnard" <petebarnard@tiscali.co.uk>
To: tomasz motylewski <T.Motylewski@bfad.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Broken pipe mystery
Date: Thu, 13 Feb 2003 20:56:33 -0000	[thread overview]
Message-ID: <000001c2d3a2$a450b2f0$0100a8c0@Pblaptop> (raw)
In-Reply-To: Pine.LNX.4.21.0302081212550.32024-100000@mailserver.intern.bfad.de

:
>
> Does it always crash after the same time?

No. It didin't crash after the same time.  The problem is fixed now thanks
to Josh Green's tip.   (I wrote a function that caught the EPIPE error and
then did a snd_pcm_prepare). I left it for 2 nights with a system("date") in
the catch function and got an EPIPE once on one night and not at all on the
second night - so even though it is fixed I'm still slightly curious as to
why I got this problem/feature at all.

Regards,

Pete


>
> What sampling frequency do you use (kHz) ?
>
> Best regards,
> --
> Tomek
>



-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en

  parent reply	other threads:[~2003-02-13 20:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08 10:21 Broken pipe mystery Pete Barnard
2003-02-08 11:13 ` tomasz motylewski
2003-02-08 13:56   ` Pete Barnard
2003-02-10  7:47     ` tomasz motylewski
2003-02-13 20:56   ` Pete Barnard [this message]
2003-02-13 23:36     ` Josh Green
2003-02-09  7:36 ` Josh Green

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='000001c2d3a2$a450b2f0$0100a8c0@Pblaptop' \
    --to=petebarnard@tiscali.co.uk \
    --cc=T.Motylewski@bfad.de \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.