Return-Path: MIME-version: 1.0 Content-type: text/plain; charset=UTF-8; format=flowed Message-id: <52129AC3.5020402@samsung.com> Date: Mon, 19 Aug 2013 16:22:59 -0600 From: Shuah Khan Reply-to: shuah.kh@samsung.com To: Stefan Lippers-Hollmann Cc: Greg Kroah-Hartman , linux-kernel@vger.kernel.org, stable@vger.kernel.org, Shuah Khan , shuahkhan@gmail.com Subject: Re: [ 00/34] 3.4.59-stable review References: <20130818203259.653403173@linuxfoundation.org> <52125DA9.3090601@samsung.com> <20130819193538.GB24897@kroah.com> <201308192214.54917.s.L-H@gmx.de> In-reply-to: <201308192214.54917.s.L-H@gmx.de> Content-transfer-encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On 08/19/2013 02:14 PM, Stefan Lippers-Hollmann wrote: > Hi > > On Monday 19 August 2013, Greg Kroah-Hartman wrote: >> On Mon, Aug 19, 2013 at 12:02:17PM -0600, Shuah Khan wrote: >>> On 08/18/2013 02:34 PM, Greg Kroah-Hartman wrote: > […] >>> and the following traces in dmesg: >>> [ 124.802169] init: udevtrigger post-stop process (353) terminated >>> with status 1 >>> [ 243.439212] INFO: task crda:723 blocked for more than 120 seconds. >> >> What is "crda"? >> >> Any luck with bisection? It should go fast as the majority of patches >> here are non-x86. > > crda is a userspace helper, invoked by udev events, which sets -and > intersects as needed- the regulatory domain settings for (modern, > cfg80211 based) wlan hardware based on the device's EEPROM regdom hint, > local configuration (country code) and eventual IEEE 802.11d hints > (country IEs) beaconed by access points nearby. It hooks into udev with > these udev rules (Debian/ 1.1.2-1): > > $ grep -v -e ^$ -e ^\# /lib/udev/rules.d/60-crda.rules > SUBSYSTEM=="ieee80211", ACTION=="add", RUN+="/lib/crda/setregdomain" > > $ grep -v -e ^$ -e ^\# /lib/udev/rules.d/85-regulatory.rules > KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/sbin/crda" > > Full source is at [2], it should be installed on pretty much every > distro/ system released with wlan support for the last >>3 years. > > There are two iwl4965 patches in this series, which might be among the > first ones to check - /if/ you actually have that hardware, the second > one (iwl4965: reset firmware after rfkill off) might also indirectly > have an effect on blutetooth (via rfkill). > > Regards > Stefan Lippers-Hollmann > > [1] http://wireless.kernel.org/en/developers/Regulatory/CRDA > [2] https://github.com/mcgrof/crda > Greg, git bisect shows the following patch as the problem: [ 26/34] genetlink: fix family dump race -- Shuah -- Shuah Khan Senior Linux Kernel Developer - Open Source Group Samsung Research America(Silicon Valley) shuah.kh@samsung.com | (970) 672-0658