From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757702Ab1GAWF3 (ORCPT ); Fri, 1 Jul 2011 18:05:29 -0400 Received: from mailservice.tudelft.nl ([130.161.131.5]:51603 "EHLO mailservice.tudelft.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756652Ab1GAWF2 (ORCPT ); Fri, 1 Jul 2011 18:05:28 -0400 X-Spam-Flag: NO X-Spam-Score: -21.89 Message-ID: <4E0E44A4.4000201@tudelft.nl> Date: Sat, 02 Jul 2011 00:05:24 +0200 From: =?ISO-8859-1?Q?=C9ric_Piel?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18) Gecko/20110621 Mandriva/3.1.11-1 (2011.0) Thunderbird/3.1.11 MIME-Version: 1.0 To: Sarah Sharp , Alan Stern CC: Greg KH , LKML , "Rafael J. Wysocki" Subject: Re: Regression 3.0-rc5+ : khubd blocked References: <20110701200800.GB17865@xanatos> In-Reply-To: <20110701200800.GB17865@xanatos> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Op 01-07-11 22:08, Sarah Sharp schreef: > On Fri, Jul 01, 2011 at 01:19:23PM -0400, Alan Stern wrote: >> On Fri, 1 Jul 2011, [ISO-8859-1] ?ric Piel wrote: >> >>> Sorry, but from a quick look, it seems to not fix the bug. >>> >>> I'll try further on Monday. >> >> Do you get a similar message from the task watchdog? The patch should >> have caused usb_set_interface() to return early, without trying to >> acquire the mutex that caused the problem before. > > I've been able to reproduce this bug with linus/master. When I apply > your patch (or at least change the code to match your patch, since I > don't have those top-level directories), I can successfully unplug and > replug in a hub with a keyboard and mouse attached to it, with no hangs. > So I'm not sure why it isn't working for Éric. Hi, I've found out it was not the patched kernel that I was tested (but just linus/master), due to a mistake in selecting the right kernel in grub. So that'd explain why I was still seeing the bug ;-) Thanks everyone for reacting to this bug so quickly! Éric