From: Takashi Iwai <tiwai@suse.de>
To: Martin van Es <martin@mrvanes.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.17.1 bug/oops in snd_usb_audio subsystem
Date: Fri, 14 Jul 2006 20:31:38 +0200 [thread overview]
Message-ID: <s5hsll43unp.wl%tiwai@suse.de> (raw)
In-Reply-To: <200607141328.40680.martin@mrvanes.com>
At Fri, 14 Jul 2006 13:28:40 +0200,
Martin van Es wrote:
>
> On Friday 14 July 2006 12:54, Alexey Dobriyan wrote:
> > On Fri, Jul 14, 2006 at 11:54:36AM +0200, Martin van Es wrote:
> > > I already sent this mail to perex@suse.cz a couple of days ago since I
> > > thought that was the closest match in the MAINTAINERS list for this oops.
> > > Since I didn't receive any reply
> >
> > Your kernel is tainted. Please complain to kqemu developers. Don't waste
> > Jaroslav's time.
>
> Thank you Alexey for pointing out I reported this oops while running a tainted
> kernel (kqemu was indeed tainting it). I interpreted the reply as a request
> for reproducing the oops on a untainted version of the Kernel of which I'll
> post the dmesg output below.
>
> Hope this helps.
> Is there anything else I can do to contribute?
Try to compile with CONFIG_SND_DEBUG=y. Also, you can try to build
modules from alsa-driver-1.0.12rc1 whether the bug still exists in the
latest version.
The problem is on OSS emulation, so check other OSS apps whether the
similar problem happens.
Takashi
next prev parent reply other threads:[~2006-07-14 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 9:54 Kernel 2.6.17.1 bug/oops in snd_usb_audio subsystem Martin van Es
2006-07-14 10:54 ` Alexey Dobriyan
2006-07-14 11:28 ` Martin van Es
2006-07-14 18:31 ` Takashi Iwai [this message]
2006-07-14 19:45 ` Martin van Es
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=s5hsll43unp.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@mrvanes.com \
/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