Hello Ben, Thank you for uploading the fixed version. The following is mostly for you information. (I.e. I do not expect you to do any additional investigation. Neither am I going to spend more time on this.)
On 20 April 2014 22:34, Dmitry Semyonov wrote: > On 20 April 2014 18:05, Ben Hutchings wrote: >> On Sun, 2014-04-20 at 11:41 +0400, Dmitry Semyonov wrote: > >>> Thanks! It fixes the crash but wlan0 has to be brought down, and up >>> again to make it work after initial bring up attempt: >> [...] >> >> I assume this is a regression, i.e. this problem did not exist in >> 3.2.54-2? > > This is correct. The interesting thing is that I do not see the regression in 3.2.57-3, although it uses the same rtl8192ce patch as I was testing with. So, I wonder if I missed some important step, or 3.2.57-3 contains a bit more changes than just the patch? (Note that I also removed 3.10 kernel-related packages from the system before installing 3.2.57-3, but this hardly could cause such change in behavior.) > I have double-checked 3.2.54-2: > > $ sudo ifup wlan0=h > > [ 93.537605] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin > [ 93.881450] ADDRCONF(NETDEV_UP): wlan0: link is not ready > [ 94.750415] wlan0: direct probe to b8:a3:86:aa:93:66 (try 1/3) > [ 94.752161] wlan0: direct probe responded And there are no "direct probe" messages in 3.2.57-3 log that were failing in 3.2.57-2 + rtl8192ce patch. P.S. Found one case with "direct probe" failures magically solved on a different hardware after rebooting to Windows - https://bbs.archlinux.org/viewtopic.php?pid=1044780#p1044780. -- ...Bye..Dmitry. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
