Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gou Zhuang <gouzhuang@bigfoot.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Gou Zhuang <gouzhuang@bigfoot.com>, alsa-devel@lists.sourceforge.net
Subject: Re: Oops on resume, X crashes
Date: Mon, 27 Oct 2003 09:03:59 +0800	[thread overview]
Message-ID: <3F9C6EFF.9030909@bigfoot.com> (raw)
In-Reply-To: <s5hoew77xmd.wl@alsa2.suse.de>

Takashi Iwai wrote:
> At Fri, 24 Oct 2003 13:45:53 +0800,
> Gou Zhuang wrote:
> 
>>I applied the patch, the oops went away :) But I still get a lot of
>>"ALSA pcm_oss.c:552: snd_pcm_oss_prepare: SNDRV_PCM_IOCTL_PREPARE failed".
>>
>>And the artsd crashed after resume with the following errmsg:
>>
>>Sound Server fatal error:
>>AudioSubSystem::handleIO: write failed
>>len = 16, can_write = 24, errno = 4 (interrupted system call)
>>
>>Do you have any clue on this?
> 
> 
> how about the attached patch?  (in replacement with the previous one.)
> 
> 
> Takashi

Yes, this patch fixed it.

Thanks,
Gouzhuang



-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/

  reply	other threads:[~2003-10-27  1:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-20  7:48 Oops on resume, X crashes Gou Zhuang
2003-10-20 14:48 ` Takashi Iwai
     [not found]   ` <3F94F094.80109@Sun.COM>
2003-10-21 11:29     ` Takashi Iwai
2003-10-23  9:12       ` Gou Zhuang
2003-10-23 18:01         ` Takashi Iwai
2003-10-24  5:45           ` Gou Zhuang
2003-10-24 10:12             ` Takashi Iwai
2003-10-27  1:03               ` Gou Zhuang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-20  6:42 Gou Zhuang

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=3F9C6EFF.9030909@bigfoot.com \
    --to=gouzhuang@bigfoot.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tiwai@suse.de \
    /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