Hi So if 3.9 works and current kernel does not, the best way to address the issue would be identify change that broke. Ideally if bisecton could be performed, but this can be hard taking that the problem is not easy reproducible. Further difficultly comes from a fact that OpenWRT has custom patches. So I suggest some kind of manual semi-bisection on OpenWRT repository with long testing, to find out first or close to first OpenWRT change that start to broke things. Cheers Stanislaw On Wed, Jan 24, 2018 at 09:18:23AM +0100, Enrico Mioso wrote: > Hello! > I can confirm - there is no firmware being uploaded to the device, or at least: if it's there, it's not uploaded from an external file. > root@smalltalk:~# ls -Fa -1 /lib/firmware/ > ./ > ../ > regulatory.db > root@smalltalk:~# > > Anything I might do? I can also give an ssh session to the device in case. > > Enrico > > On Tue, 23 Jan 2018, Stanislaw Gruszka wrote: > > >Date: Tue, 23 Jan 2018 14:22:35 > >From: Stanislaw Gruszka <sgruszka@xxxxxxxxxx> > >To: Enrico Mioso <mrkiko.rs@xxxxxxxxx> > >Cc: Tom Psyborg <pozega.tomislav@xxxxxxxxx>, > > linux-wireless <linux-wireless@xxxxxxxxxxxxxxx>, > > Johannes Berg <johannes.berg@xxxxxxxxx>, > > Daniel Golle <daniel@xxxxxxxxxxxxxx>, Arnd Bergmann <arnd@xxxxxxxx>, > > John Crispin <john@xxxxxxxxxxx>, Felix Fietkau <nbd@xxxxxxxx> > >Subject: Re: ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping > > frame due to full tx queue...? > > > >On Mon, Jan 22, 2018 at 06:45:57AM +0100, Enrico Mioso wrote: > >>Crash happening here also in the WL-330n3G device; unfortunately, no messages to report. > >>Regarding your hypothesis regardingthe firmware not being able to communicate a problem regarding it's inability to send frames: around when OpenWRT had 3.9.9 kernel, this device worked for weeks no stop with no issues I think. > >>And I don't think this is only a coicnidence. So I suspect, but it's only an impression, also because I know ... very very little about this, that at some point things worked. > > > >I think FW was upgraded since 3.9 kernel as well. But this > >could be also problem how driver program the device registers, > >not only FW problem. > > > >Regards > >Stanislaw > >
