Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752692Ab2HUFfC (ORCPT ); Tue, 21 Aug 2012 01:35:02 -0400 Received: from mail-ey0-f174.google.com ([209.85.215.174]:50972 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752143Ab2HUFe7 (ORCPT ); Tue, 21 Aug 2012 01:34:59 -0400 MIME-Version: 1.0 Date: Tue, 21 Aug 2012 13:34:57 +0800 Message-ID: Subject: udev 182: response timeout for request_firmware in module_probe path From: Ming Lei To: Kay Sievers Cc: Linux Kernel Mailing List , Greg Kroah-Hartman , Johannes Berg , Larry Finger , Linus Torvalds Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 739 Lines: 22 Hi Kay, I found that udev 182 doesn't response for the request_firmware in module_probe path until 30sec later after the 'ADD' event of firmware device, but no such problem in udev175, sounds like a regression of udev? I find there was a related discussion in [1], so CC guys who discussed before. Just grep under kernel root dir, there are about 360 request_firmware callers, and looks most of them are called in .probe path. [1], https://lkml.org/lkml/2012/2/19/57 Thanks, -- Ming Lei -- 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/