linux-kernel - Re: Logitech USB headset not working in 3.6-rc3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 25 Aug 2012 15:45:05 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Josh Boyer <jwboyer@...hat.com>
Cc:	Daniel Mack <zonque@...il.com>, Bruno Wolff III <bruno@...ff.to>,
	Jaroslav Kysela <perex@...ex.cz>, alsa-devel@...a-project.org,
	linux-kernel@...r.kernel.org
Subject: Re: Logitech USB headset not working in 3.6-rc3

At Sat, 25 Aug 2012 08:17:58 -0400,
Josh Boyer wrote:
> 
> 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@...il.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.

Yes, please.  I'm currently traveling for KS and Plumbers, so I cannot
debug it deeply, unfortunately.

If the culprit were really my patch, I still don't figure out why it
breaks.  In that case, it must be really a subtle timing issue...


thanks,

Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/