From: Laura Abbott <labbott@redhat.com>
To: simon@mungewell.org, "Kim, Milo" <milo.kim@ti.com>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Kernel Oops: btusb: 4.2rc1 System lockup with BT dongle insert - log attached
Date: Fri, 17 Jul 2015 10:23:28 -0700 [thread overview]
Message-ID: <55A93A10.3060201@redhat.com> (raw)
In-Reply-To: <d51df2e1e321efc18d74f3cc33bd4106.squirrel@mungewell.org>
On 07/17/2015 08:14 AM, simon@mungewell.org wrote:
>
>>> 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.
>>>
>>
>> The 'CONFIG_FW_LOADER_USER_HELPER_FALLBACK' enables to load firmware
>> data manually by accessing /sys/class/firmware/<name>/data. It runs in
>> case the firmware file is missing.
>> This user helper fallback will be enabled if one of LP55xx driver is
>> included in your dot config. Please see my patch below.
>>
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/leds?id=b67893206fc0a0e8af87130e67f3d8ae553fc87c
>>
>> However, I'm not sure why this affects your system lockup. Can I have
>> more details?
>
> Hi Milo,
> I'm not suggesting that your patch is the cause, just that it is an
> 'enabler' and and explains why the problem (system lockup when I plug USB
> Bluetooth dongle in) appears now.
>
> A full Oops log is further back in this thread:
> http://www.spinics.net/lists/linux-bluetooth/msg63090.html
>
>
>>> Will try building 4.1 with this option to see if it fails.
>
> A very quick test as I was leaving the house this morning shows that 4.1
> with 'CONFIG_FW_LOADER_USER_HELPER_FALLBACK' does not show the problem.
>
> So at least we know the 'real' problem is a recent change to the code.
> Simon
>
I think this was reported and fixed
https://lkml.org/lkml/2015/7/8/858
https://lkml.org/lkml/2015/7/8/1199
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6f957724b94cb19f5c1c97efd01dd4df8ced323c
Thanks,
Laura
next prev parent reply other threads:[~2015-07-17 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a48f30f621c508955ba989117690fe73.squirrel@mungewell.org>
[not found] ` <dcf4c0f809904c54f453fe781e30adfe.squirrel@mungewell.org>
2015-07-17 5:14 ` Kernel Oops: btusb: 4.2rc1 System lockup with BT dongle insert - log attached simon
2015-07-17 6:14 ` simon
2015-07-17 7:09 ` Kim, Milo
2015-07-17 15:14 ` simon
2015-07-17 17:23 ` Laura Abbott [this message]
2015-07-17 17:40 ` simon
2015-07-20 1:48 ` simon
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=55A93A10.3060201@redhat.com \
--to=labbott@redhat.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=milo.kim@ti.com \
--cc=simon@mungewell.org \
/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