From: Borislav Petkov <bp@alien8.de>
To: "Lasse Kärkkäinen" <ljkarkk2@cc.hut.fi>
Cc: linux-kernel@vger.kernel.org, USB list <linux-usb@vger.kernel.org>
Subject: Re: CPU soft lockup in usb-audio
Date: Thu, 24 Jan 2013 17:16:29 +0100 [thread overview]
Message-ID: <20130124161629.GD13471@pd.tnic> (raw)
In-Reply-To: <510159D2.7000001@cc.hut.fi>
On Thu, Jan 24, 2013 at 05:57:06PM +0200, Lasse Kärkkäinen wrote:
> I've spent months hunting for this random crash bug until today when
> I finally found a way to reliably reproduce it (run a software that
> I develop under valgrind). Log received over netconsole:
>
> http://pastie.org/5848168
>
> Is this a known issue or do you need more information to debug it?
Hmm, this happens while running memcheck-<something>.
A couple of things:
* can you try the same way of reproduction without the proprietary
nvidia module loaded?
* can you try latest kernel, 3.8-rc4 or 3.7-stable?
* let's also add linux-usb to CC.
HTH.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2013-01-24 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 15:57 CPU soft lockup in usb-audio Lasse Kärkkäinen
2013-01-24 16:16 ` Borislav Petkov [this message]
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=20130124161629.GD13471@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ljkarkk2@cc.hut.fi \
/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.