Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756831AbbGQGOK (ORCPT ); Fri, 17 Jul 2015 02:14:10 -0400 Received: from host171.canaca.com ([67.55.55.225]:57737 "EHLO host171.canaca.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756641AbbGQGOI (ORCPT ); Fri, 17 Jul 2015 02:14:08 -0400 Message-ID: <913a160c809900ee52e7c83350b4162f.squirrel@mungewell.org> In-Reply-To: <8297c42b69d89cb9326b938a9adaa997.squirrel@mungewell.org> References: <8297c42b69d89cb9326b938a9adaa997.squirrel@mungewell.org> Date: Fri, 17 Jul 2015 02:14:06 -0400 Subject: Re: Kernel Oops: btusb: 4.2rc1 System lockup with BT dongle insert - log attached From: simon@mungewell.org To: linux-bluetooth@vger.kernel.org Cc: linux-kernel@vger.kernel.org, "Milo Kim" User-Agent: SquirrelMail/1.4.22 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Priority: 3 (Normal) Importance: Normal X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host171.canaca.com X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - mungewell.org X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2317 Lines: 68 > It looks like the firmware 'opt_flags' must be different, so this may be a > contributing factor. Plot thickens.... kernel config has changed since I built 4.1.0rc7, but I don't recall doing it or starting a fresh. /boot/config-4.1.0-rc7+ -- CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="" CONFIG_FW_LOADER_USER_HELPER=y # CONFIG_FW_LOADER_USER_HELPER_FALLBACK is not set CONFIG_WANT_DEV_COREDUMP=y CONFIG_ALLOW_DEV_COREDUMP=y CONFIG_DEV_COREDUMP=y -- /boot/config-4.2.0-rc1+ -- CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="" CONFIG_FW_LOADER_USER_HELPER=y CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y <------------!!! CONFIG_WANT_DEV_COREDUMP=y CONFIG_ALLOW_DEV_COREDUMP=y CONFIG_DEV_COREDUMP=y -- Has a kconfig forced a change?.... Grrr -- $ git blame ./drivers/leds/Kconfig -- c93d08fa7 (Milo(Woogyom) Kim 2013-02-05 18:01:23 +0900 228) config LEDS_LP55XX_COMMON 33b3a561f (Kim, Milo 2013-07-09 02:11:37 -0700 229) tristate "Common Driver for TI/National LP5521/5523/55231/5562/8501" 33b3a561f (Kim, Milo 2013-07-09 02:11:37 -0700 230) depends on LEDS_LP5521 || LEDS_LP5523 || LEDS_LP5562 || LEDS_LP8501 10c06d178 (Milo(Woogyom) Kim 2013-02-05 19:17:20 +0900 231) select FW_LOADER b67893206 (Milo Kim 2015-06-28 17:39:14 -0700 232) select FW_LOADER_USER_HELPER_FALLBACK <-----!!!! c93d08fa7 (Milo(Woogyom) Kim 2013-02-05 18:01:23 +0900 233) help 33b3a561f (Kim, Milo 2013-07-09 02:11:37 -0700 234) This option supports common operations for LP5521/5523/55231/5562/8501 c93d08fa7 (Milo(Woogyom) Kim 2013-02-05 18:01:23 +0900 235) devices. -- So in summary this problem is showing up now as the 'User Helper Fallback' is now forced on, obviously the underlying problem needs to be fixed - but I don't know when it crept in. Will try building 4.1 with this option to see if it fails. Simon -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/