On Mon, Jul 22, 2013 at 12:47 AM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > On Sun, Jul 21, 2013 at 11:22:24PM +0200, Francis Moreau wrote: >> >> I'm attaching a backport of your patch for 3.4. It was almost trivial, >> but I'm not sure about the modifications I did in >> firmware_free_data(), specially the condition to test if the firmware >> has been loaded by the kernel itself. I will test it tomorrow to check >> if I'm really affected by the udev bug, but whatever the result I >> think it's still an interesting issue to address. > > Did you test this out and verify that it works properly for the > offending devices? I just finished to test the patch and it fix the hung I had during boot, and now I can see: [ 2.216169] isci 0000:0e:00.0: OEM SAS parameters (version: 1.3) loaded (firmware) instead of something like "failed to load firmware, using default values". So yes it now works properly, the only thing I'm not sure is about the code I needed to adapt for 3.4 in firmware_free_data(). I'm still not sure if the udev fix should be preferred over this patch. Thanks -- Francis -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html