On Monday 21 September 2009 12:56:48 Pekka Enberg wrote: > On Mon, 2009-09-21 at 12:46 +0200, Bartlomiej Zolnierkiewicz wrote: > > > > I don't know why people don't see it but for me it has a memory management > > > > regression and reliability issue written all over it. > > > > > > Possibly but drivers that reload their firmware as a response to an > > > error condition is relatively new and loading network drivers while the > > > system is already up and running a long time does not strike me as > > > typical system behaviour. > > > > Loading drivers after boot is a typical desktop/laptop behavior, please > > think about hotplug (the hardware in question is an USB dongle). > > Yeah, I wonder what broke things. Did the wireless stack change in > 2.6.31-rc1 too? IIRC Mel ruled out page allocator changes as a suspect. The thing is that the mm behavior change has been narrowed down already over a month ago to -mm merge in 2.6.31-rc1 (as has been noted in my initial reports), I first though that that it was -next breakage but it turned out that it came the other way around (because -mm is not even pulled into -next currently -- great way to set an example for other kernel maintainers BTW). I understand that behavior change may be justified and technically correct in itself. I also completely agree that high order allocations in certain drivers need fixing anyway. However there is something wrong with the big picture and the way changes are happening. I'm not saying that I'm surprised though, especially given the recent decline in the quality assurance and the paradigm shift that I'm seeing (some influential top level people talking that -rc1 is fine for testing new code now or the "new kernel new hardware" thing). Sorry but I have no more time currently to narrow down the issue some more (guess what, there are other kernel bugs standing in the way to bisect it and I would have to provide some reliable way to reproduce it first) so I see no more point in wasting people's time on this. I can certainly get by with allocation failure here and there. Not a big deal for me personally.. -- 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
