From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754490Ab2A0A1m (ORCPT ); Thu, 26 Jan 2012 19:27:42 -0500 Received: from mail-pz0-f46.google.com ([209.85.210.46]:37362 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751835Ab2A0A1l (ORCPT ); Thu, 26 Jan 2012 19:27:41 -0500 Date: Thu, 26 Jan 2012 16:27:39 -0800 (PST) Message-ID: <87hazi56rw.wl%kuninori.morimoto.gx@renesas.com> From: Kuninori Morimoto To: balbi@ti.com Cc: Yves-Alexis Perez , Greg KH , linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org Subject: Re: [3.2+] BUG: scheduling while atomic: swapper/0/0/0x10000100 In-Reply-To: <20120126164512.GD8665@legolas.emea.dhcp.ti.com> References: <1327587732.2296.25.camel@scapa> <20120126161539.GA2098@kroah.com> <20120126163130.GB8665@legolas.emea.dhcp.ti.com> <1327595767.2062.7.camel@scapa> <20120126164512.GD8665@legolas.emea.dhcp.ti.com> User-Agent: Wanderlust/2.14.0 Emacs/23.3 Mule/6.0 MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi All > > > Specially when you consider the fact that > > > it's very recently that we dropped the ARCH dependency with commit > > > d242c110c43b55aaf3ebb3ceac1eeab0d452a177 > > > > > > > Kuninori, any thoughts about this? Should I revert this from the > > > > tree? > > > > > > I don't think so, I think this was a bad bisection. > > > > > Maybe (especially since the first bad commit is a merge commit, so I'm > > not completely sure I did correctly the second bisect). But I'm puzzled > > why reverting the commit on top of 3.2.1 fixes that. And now that Felipe > > mentions it, USB Gadget is not even compiled, so I'm completely lost. > > Hehehe :-) That's fun... Maybe it's some other instability and it just > didn't kick when you reverted that commit. It could be that the problem > is somewhere completely different and you just didn't fully debug it yet > :-) I was very much surprised at this issue. As Felipe explained, renesas_usbhs was for SuperH system. x86 can not use it, but, if your PC has "renesas_usbhs.ko" as kernel module, and loaded it somehow... Best regards --- Kuninori Morimoto