All of lore.kernel.org
 help / color / mirror / Atom feed
From: Parag Warudkar <kernel-stuff@comcast.net>
To: ALSA devel <alsa-devel@alsa-project.org>
Cc: Takashi Iwai <tiwai@suse.de>, linux-kernel@vger.kernel.org
Subject: ALSA CVS - pcm_oss.c:1872: BUG?
Date: Fri, 14 Apr 2006 17:48:15 -0400	[thread overview]
Message-ID: <200604141748.15367.kernel-stuff@comcast.net> (raw)

I get the below BUG in dmesg once or twice a day. Running snd_hda_intel on 
2.6.16 along with yesterday's ALSA CVS. 

Parag

[17197574.124000]  [<f89d8ad3>] snd_pcm_oss_get_active_substream+0x5d/0x7e 
[snd_pcm_oss]
[17197574.124000]  [<f89d9011>] snd_pcm_oss_ioctl+0x346/0x9c9 [snd_pcm_oss]
[17197574.128000]  [<7815ca79>] do_ioctl+0x21/0x5f
[17197574.128000]  [<7815cd07>] vfs_ioctl+0x250/0x263
[17197574.128000]  [<7815cd60>] sys_ioctl+0x46/0x62
[17197574.128000]  [<78102797>] sysenter_past_esp+0x54/0x75
[17197574.128000] ALSA /root/alsa/alsa-driver/acore/oss/pcm_oss.c:1872: BUG? 
(substream != ((void *)0))
[17197574.128000]  [<f89d8376>] snd_pcm_oss_release+0x37/0xda [snd_pcm_oss]
[17197574.128000]  [<7814df15>] __fput+0x86/0x14a
[17197574.128000]  [<7814baaa>] filp_close+0x4e/0x57
[17197574.128000]  [<7814c4a7>] sys_close+0x6b/0x80
[17197574.128000]  [<78102797>] sysenter_past_esp+0x54/0x75


             reply	other threads:[~2006-04-14 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14 21:48 Parag Warudkar [this message]
2006-04-18 10:05 ` [Alsa-devel] ALSA CVS - pcm_oss.c:1872: BUG? Takashi Iwai
2006-04-18 19:08   ` up do date repository ? Giuliano Pochini
2006-04-18 19:11     ` Takashi Iwai
2006-04-19  8:43       ` Giuliano Pochini
2006-04-19 10:24         ` Takashi Iwai
2006-04-18 10:05 ` ALSA CVS - pcm_oss.c:1872: BUG? Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2006-04-14 21:48 Parag Warudkar

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=200604141748.15367.kernel-stuff@comcast.net \
    --to=kernel-stuff@comcast.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.