On Sat, Oct 06, 2012 at 02:08:50PM +0200, Pavel Machek wrote: > On Fri 2012-10-05 10:37:00, Stanislaw Gruszka wrote: > > On Wed, Oct 03, 2012 at 11:07:13AM -0700, David Rientjes wrote: > > > On Wed, 3 Oct 2012, Stanislaw Gruszka wrote: > > > > > > > So, can this problem be solved like on below patch, or I should rather > > > > split firmware loading into chunks similar like was already iwlwifi did? > > > > Hmm, I looked at iwl3945 code and looks loading firmware in chunks is > > nothing that can be easily done. 3945 bootstrap code expect that runtime > > ucode will be placed in physically continue memory, and there are no > > separate instructions for copy and for execute, just one to perform both > > those actions. Maybe loading firmware in chunks can be done using > > undocumented features of the device, but I'm eager to do this. > > Just allocate memory during boot? On driver I can reserve memory during module load, but also this isn't something I prefer to do. > > Pavel, do you still can reproduce this problem on released 3.6 ? > > It happened again yesterday on 3.6.0-rc6+. I don't think mm changed > between -rc6 and final... Could you check __GFP_REPEAT oneline patch posted previously ? And if that fail again, provide full dmesg (on your previous messages there is vmap() failure, which I do not understand, where it come from) ? Thanks Stanislaw -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
