public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Paul Blazejowski <diffie@gmail.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Diffie <diffie@blazebox.homeip.net>,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Linux 2.6.10-rc2
Date: Mon, 15 Nov 2004 16:16:31 -0500	[thread overview]
Message-ID: <1100553392.4369.1.camel@krustophenia.net> (raw)
In-Reply-To: <9dda349204111512234f30c60d@mail.gmail.com>

Please report ALSA issues to alsa-devel@lists.sourceforge.net.  I have
added them to the cc:.

Lee

On Mon, 2004-11-15 at 15:23 -0500, Paul Blazejowski wrote:
> Starting up ut2004 or doom3 games produces ALSA segfaults, dmesg prints:
> 
> scheduling while atomic: ut2004-bin/0x00000001/8390
>  [<c0331508>] schedule+0x508/0x510
>  [<c03319a3>] schedule_timeout+0x63/0xc0
>  [<c0122c90>] process_timeout+0x0/0x10
>  [<c012306f>] msleep+0x2f/0x40
>  [<f8b9e02f>] snd_intel8x0_setup_pcm_out+0xbf/0x150 [snd_intel8x0]
>  [<f8b9e14c>] snd_intel8x0_pcm_prepare+0x8c/0xb0 [snd_intel8x0]
>  [<f8bfda84>] snd_pcm_do_prepare+0x14/0x40 [snd_pcm]
>  [<f8bfcdd8>] snd_pcm_action_single+0x38/0x80 [snd_pcm]
>  [<f8bfcfd0>] snd_pcm_action_nonatomic+0x80/0x90 [snd_pcm]
>  [<f8bfdb37>] snd_pcm_prepare+0x57/0x80 [snd_pcm]
>  [<f8c001b2>] snd_pcm_playback_ioctl1+0x52/0x310 [snd_pcm]
>  [<f8d25ae9>] snd_pcm_oss_poll+0x49/0x1a0 [snd_pcm_oss]
>  [<c016901a>] poll_freewait+0x3a/0x50
>  [<f8c00828>] snd_pcm_kernel_playback_ioctl+0x38/0x50 [snd_pcm]
>  [<f8d23026>] snd_pcm_oss_prepare+0x26/0x60 [snd_pcm_oss]
>  [<f8d2309d>] snd_pcm_oss_make_ready+0x3d/0x60 [snd_pcm_oss]
>  [<f8d2358d>] snd_pcm_oss_write1+0x3d/0x210 [snd_pcm_oss]
>  [<f8d259d0>] snd_pcm_oss_write+0x40/0x60 [snd_pcm_oss]
>  [<f8d25990>] snd_pcm_oss_write+0x0/0x60 [snd_pcm_oss]
>  [<c01563e8>] vfs_write+0xb8/0x130
>  [<c0156531>] sys_write+0x51/0x80
>  [<c010317b>] syscall_call+0x7/0xb
> 
> .config attached
> 
> Regards,
> 
> Paul B.
-- 
Lee Revell <rlrevell@joe-job.com>


  reply	other threads:[~2004-11-16  1:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15 20:23 Linux 2.6.10-rc2 Paul Blazejowski
2004-11-15 21:16 ` Lee Revell [this message]
2004-11-16  9:46   ` [Alsa-devel] " Takashi Iwai
2004-11-18 16:19     ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2004-11-15  2:49 Linus Torvalds
2004-11-15 10:26 ` Russell King
2004-11-15 11:24   ` Ben Dooks
2004-11-15 11:55 ` Nick Piggin
2004-11-15 20:20   ` Andrew Morton
2004-11-16 16:25 ` Guido Guenther
2004-11-17 15:54 ` Andrew Walrond
2004-11-18 17:26 ` Vladimir B. Savkin
2004-11-18 17:59   ` Linus Torvalds
2004-11-18 18:01     ` Matthew Wilcox
2004-11-19  8:43       ` Vladimir B. Savkin

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=1100553392.4369.1.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=diffie@blazebox.homeip.net \
    --cc=diffie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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