OK Stefan, thank you so much. I've seen that the file if_iwm.c has declared the variable iwm_debug which prints more information depending on the level you set on that variable. If you want, I can set that variable to 20 for a full report about what's going on ...
On the other hand, The other day, when I sent the output of my dmesg here,I forgot to tell you that my computer is an MSI GE70 2QE Apache PRO. Greetings Have a nice day 2016-08-08 1:19 GMT+02:00 Stefan Sperling <[email protected]>: > On Tue, Aug 02, 2016 at 07:42:16PM +0200, Guillermo Bernaldo de Quiros > Maraver wrote: > > Hi, goord afternoon. > > > > I have a similar problem. Sometimes I get the message "iwm0: fatal > firmware > > error" and then, I have to restart the network interface doing sh > > /etc/netstart. But most of the time, I have internet access. > > I've just committed a workaround for this. Meaning the driver will > now try to restart the interface automatically when this happens. > > It would be nice to understand the underlying cause but the information > I have so far leads nowhere. A small bit of good news is that I've seen > this happen on one of my own machines. Not in an environment where I can > actually debug the issue but good enough to test my workaround. > > > Now, I've > > added the option IWM_DEBUG in the kernel, I rebuilt the kernel and I'm > > getting a lot of messages like: "sending command 0x4e qid 9, idx 215" > (once > > per second at least) and sometimes I get: "RX BA Session stopped in fw" > You > > have all the information in the attachment. Maybe this can help you a > > little bit more :) > > These messages are printed when everything works as expected. >
