On Sun, May 27, 2007 at 11:49:30PM +0200, Kay Sievers wrote:
> What exactly is the problem we see here? The timeout of the firmware loader?
> What goes wrong with frozen userspace, usually there is only a netlink
> message sent from the kernel, which should be received and handled
> just fine when userspace is running again.
Driver calls request_firmware in the resume method. The userspace helper
can't be run because it's been frozen, so the firmware never gets loaded
and the call times out. The driver then fails to resume. While all this
is happening, the rest of the kernel is blocking on that resume method.
The firmware can be loaded once userspace has been started again, but by
that time the driver has given up.
--
Matthew Garrett | [email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
