linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@redhat.com>
To: Daniel Mack <zonque@gmail.com>
Cc: Bruno Wolff III <bruno@wolff.to>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: Logitech USB headset not working in 3.6-rc3
Date: Sat, 25 Aug 2012 08:17:58 -0400	[thread overview]
Message-ID: <20120825121758.GF20043@zod.bos.redhat.com> (raw)
In-Reply-To: <5038C186.7000107@gmail.com>

On Sat, Aug 25, 2012 at 02:13:58PM +0200, Daniel Mack wrote:
> On 25.08.2012 14:07, Bruno Wolff III wrote:
> > On Sat, Aug 25, 2012 at 14:02:51 +0200,
> >    Daniel Mack <zonque@gmail.com> wrote:
> >>
> >> Can you revert commit e9ba389c5 ("ALSA: usb-audio: Fix
> >> scheduling-while-atomic bug in PCM capture stream") and see if that
> > 
> > I can try that, but it takes a long time to build a new kernel on my 
> > old hardware.
> > 
> >> helps? If not, can you summarize again which kernels still work for you
> >> and which don't?
> > 
> > The latest kernel that works is 3.6.0-0.rc2.git1.2.fc18. The earliest that 
> > doesn't work is 3.6.0-0.rc2.git2.1.fc18.
> > 
> 
> The report you sent doesn't look like it could be caused by e9ba389c5.
> It fixes a kernel Ooops. But as it is the only relevant patch in that
> area, it would be interesting if reverting it fixes anything.

Yep, agreed.  If this revert kernel doesn't work, we're likely down to a
git bisect, Bruno.

> Btw - thanks a lot for testing -rc kernels, much appreciated!

Indeed!

josh

  reply	other threads:[~2012-08-25 12:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 19:08 Logitech USB headset not working in 3.6-rc3 Josh Boyer
2012-08-24 21:30 ` Daniel Mack
2012-08-24 22:30   ` Josh Boyer
2012-08-24 22:30 ` Daniel Mack
2012-08-25 11:17   ` Bruno Wolff III
2012-08-25 11:54     ` Bruno Wolff III
2012-08-25 12:02       ` Daniel Mack
2012-08-25 12:07         ` Bruno Wolff III
2012-08-25 12:13           ` Josh Boyer
2012-08-25 12:16             ` Bruno Wolff III
2012-08-26 12:46               ` Kernel module build workflow (Re: Logitech USB headset not working in 3.6-rc3) Takashi Iwai
     [not found]                 ` <CAFz=ag47OU1GbS-a8GUug4bJ04JA6kn_uBUZ0LiBjzUCJ0fN_w@mail.gmail.com>
2012-08-27 18:46                   ` [alsa-devel] " Takashi Iwai
2012-08-25 15:00             ` Logitech USB headset not working in 3.6-rc3 Bruno Wolff III
2012-08-25 12:13           ` Daniel Mack
2012-08-25 12:17             ` Josh Boyer [this message]
2012-08-25 13:45               ` Takashi Iwai
2012-08-29 11:26               ` Daniel Mack
2012-08-29 13:29                 ` Takashi Iwai
2012-08-29 13:32                   ` Daniel Mack
2012-08-29 14:14                     ` Takashi Iwai
2012-08-29 14:25                       ` Daniel Mack
2012-08-29 15:01                         ` Takashi Iwai
2012-08-29 17:07                     ` Josh Boyer
2012-08-29 17:22                       ` Josh Boyer
2012-08-29 18:50                         ` Bruno Wolff III
2012-08-30 14:10                     ` Takashi Iwai
2012-08-30 15:03                       ` Bruno Wolff III

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=20120825121758.GF20043@zod.bos.redhat.com \
    --to=jwboyer@redhat.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bruno@wolff.to \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.de \
    --cc=zonque@gmail.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;
as well as URLs for NNTP newsgroup(s).