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: Fri, 24 Oct 2003 13:45:53 +0800 [thread overview]
Message-ID: <3F98BC91.3090606@bigfoot.com> (raw)
In-Reply-To: <s5hptgn96lc.wl@alsa2.suse.de>
Takashi Iwai wrote:
> At Thu, 23 Oct 2003 17:12:08 +0800,
> Gou Zhuang wrote:
>
>>I turned on OSS_DEBUG in pcm_oss.c. I did not start X this time, I only started artsd from
>>console to reproduce the oops. Below is the messages after resume, my comments are marked
>>with <<<---------
>>
>>-------------------------
>>MYDEBUG intel8x0.c:2141: Entering intel8x0_suspend()
>>MYDEBUG intel8x0.c:2149: Call snd_pcm_suspend_all() on Intel 82801CA-ICH3
>>MYDEBUG intel8x0.c:2149: Call snd_pcm_suspend_all() on Intel 82801CA-ICH3 - MIC ADC
>>MYDEBUG intel8x0.c:2152: Call snd_power_change_state(card, SNDRV_CTL_POWER_D3hot)
>>MYDEBUG intel8x0.c:2154: Return from snd_power_change_state()
>>pcm_oss: ioctl = 0x8010500c
>>pcm_oss: space: bytes = 7168, fragments = 7, fragstotal = 7, fragsize = 1024
>>pcm_oss: write: recovering from SUSPEND
>>ALSA pcm_oss.c:552: snd_pcm_oss_prepare: SNDRV_PCM_IOCTL_PREPARE failed
>>pcm_oss: write 1024 bytes (wrote -11 bytes) <<<----------- IT SEEMS THE WRITE FAILED!
>
>
> that's ok, because it's opened with non-block mode.
>
>
>>MYDEBUG intel8x0.c:2162: Entering intel8x0_resume()
>>MYDEBUG intel8x0.c:2167: Call pci_enable_device(chip->pci)
>>PCI: Found IRQ 11 for device 00:1f.5
>>PCI: Sharing IRQ 11 with 00:1f.6
>>MYDEBUG intel8x0.c:2169: Call pci_set_master(chip->pci)
>>PCI: Setting latency timer of device 00:1f.5 to 64
>>MYDEBUG intel8x0.c:2067: Entering snd_intel8x0_chip_init()
>>MYDEBUG ../../alsa-kernel/pci/ac97/ac97_codec.c:2148: Entering snd_ac97_resume()
>>MYDEBUG ../../alsa-kernel/pci/ac97/ac97_codec.c:2148: Entering snd_ac97_resume()
>>MYDEBUG intel8x0.c:2177: Call snd_power_change_state(card, SNDRV_CTL_POWER_D0)
>
>
> ok, i think i found a bug.
> please try the attached patch.
>
>
> Takashi
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?
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/
next prev parent reply other threads:[~2003-10-24 5:45 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 [this message]
2003-10-24 10:12 ` Takashi Iwai
2003-10-27 1:03 ` Gou Zhuang
-- 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=3F98BC91.3090606@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