From: Jiri Slaby <jirislaby@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Shlomi Fish <shlomif@iglu.org.il>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
perex@suse.cz
Subject: Re: [Alsa-devel] Re: Two OOPSes in ALSA with kernel-2.6.17-rc1
Date: Mon, 10 Apr 2006 19:16:17 +0159 [thread overview]
Message-ID: <443A92F8.6020704@gmail.com> (raw)
In-Reply-To: <s5hd5fp4aqv.wl%tiwai@suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Takashi Iwai napsal(a):
> At Mon, 10 Apr 2006 17:57:48 +0159,
> Jiri Slaby wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Shlomi Fish napsal(a):
>>> Hi all!
>>>
>>> (Please CC me on the replies)
>>>
>>> I recently received these two OOPSes with kernel-2.6.17-rc1. They happened
>>> while mpg123 was playing a WAV file and I invoked KDE (along with artsd).
>>>
>>> My soundcard is snd_intel8x0.
>>>
>>> Let me know if you need any other information.
>> Try to turn sound debug on and retest.
>> It seems like struct snd_pcm_runtime *runtime is NULL.
>
> In which function?
Sorry, I cut it away:
http://lkml.org/lkml/2006/4/10/130
regards,
- --
Jiri Slaby www.fi.muni.cz/~xslaby
\_.-^-._ jirislaby@gmail.com _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFEOpL4MsxVwznUen4RAhZGAJoC1vnWGKCuRy5AETmc/37i6rMhOwCfYVrr
PxufLfOVmdORm2vb91dRiKw=
=LYPV
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-04-10 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 15:23 Two OOPSes in ALSA with kernel-2.6.17-rc1 Shlomi Fish
2006-04-10 15:58 ` Jiri Slaby
2006-04-10 17:10 ` [Alsa-devel] " Takashi Iwai
2006-04-10 17:17 ` Jiri Slaby [this message]
2006-04-10 17:35 ` Takashi Iwai
2006-04-10 17:35 ` [Alsa-devel] " Takashi Iwai
2006-04-10 17:17 ` Jiri Slaby
2006-04-10 17:10 ` Takashi Iwai
2006-04-10 15:58 ` Jiri Slaby
2006-04-10 17:12 ` Tomasz Torcz
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=443A92F8.6020704@gmail.com \
--to=jirislaby@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=shlomif@iglu.org.il \
--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 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.