Hello! I would say it fits in here, because the problem first appears with Linux 3.18 and the bug is about supporting Linux 3.18+. Fixing a bug that we know of as we go also sounds like a good idea. Also just my opinion.
Sounds like a good plan to wait for any reaction by the maintainer. Greetings, Bruno On 2015-04-29 16:36, Eduard Bloch wrote: > Hallo, > * Bruno Bierbaumer [Wed, Apr 29 2015, 02:49:23PM]: >> Yes, there are many reports about this lockup. > > Maybe, but as said, it was not strictly in the scope of this bugreport. > It deserves a new bug report with important severity, IMHO. > >> Original one is here: >> https://bugs.gentoo.org/show_bug.cgi?id=523326#c24 >> >> I don't think it 3.18 specific and Gentoo and Arch are definitely also >> applying the patch to broadcom-sta for all kernel versions. > > Ok, sounds plausible. I would wait a couple of days, maybe $maintainer > will react and do something about it. Please remind me next weekend if > nothing happened in the meantime. > >> For me I could always reproduce the lock up by: >> - Starting a heavy download >> - Disconnecting the WiFi through NetworkManager or going to suspend > > Interesting... maybe my laptop is just too slow and this issue is > triggered by concurency problems? > > Anyhow, the report above sounds convincing enough. > > Regards, > Eduard. > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
