Re: Intel Wireless fatal error
Hi, Justin Parrott wrote: bros, if you have something that works, consider sticking with it... maybe, instead, is time to track down an error and fix a bug which existed before but just got worse? Waiting for Martin's debug patches... Riccardo
Re: Intel Wireless fatal error
bros, if you have something that works, consider sticking with it... On Tue, May 7, 2024 at 3:34 AM Riccardo Mottola wrote: > Hi, > > I upgraded my trusty Thinkpad to T30 to 10.0 and now most rough edges > have been sorted out. > > Yesterday I connected it via WiFi, connected remotely to it, then went > to bed. Today I see the connection dropped and a green message on the > console. > Ifconfig says network down. > > > dmesg | grep iwi0 > [ 1.005536] iwi0 at pci2 dev 2 function 0: Intel PRO/Wireless LAN > 2200BG Mini-PCI Adapter (rev. 0x05) > [ 1.005536] iwi0: interrupting at irq 11 > [ 1.005536] iwi0: 802.11 address 00:16:6f:0c:0f:59 > [ 3574.054462] iwi0: autoconfiguration error: fatal error > > what autoconfiguration failed after it was running for a while? if those > are directly seconds it would be after 1h. > > This issue happened on 9.3 too, sometimes - but I never checked > console/dmesg and related things. > > Riccardo > -- Identity is Fleeting // Speak the Truth you Know in your Heart
Re: Intel Wireless fatal error
Hi, Martin Husemann wrote: > The message is bogus, it has nothing to do with autoconfiguration. Misleading.. I was wondering what autoconfiguration had to be done after everything was connected. > > "Fatal error" is a bit in the interrupt cause register of the intel > chipset. The driver can not do anything about it and resets the device > (simmilar to a "ifconfig iwi0 down). This is not a good error handling > strategy, as you have noticed - and it is also done very wrong in the > iwi_softintr handler. Not very good and it explains aslo why, if done quickly enough, ifconfig up restores network connectivity and even open connection. Clearly, if time passes, dhcp lease might expire, connections drop, etc. > The driver should clear the interrupt, schedule a reset and ignore all > other activity untill the reset has happened. Of course the reset should > include bringing up the device to full working state again. I wonder which interrupt here happens that requires a rest - these disconnects happen also with a quite idle system. I had no X11 running and just network up and telnet in sometimes. > > However, this is obviously not easy to test and debug, as you will have to > be in a setup where this happens often enough (like your's). Let's try I wonder if 10 increased the frequency of drops or today is an unlucky day! > If you have patience and would be able to help with this: compile your > kernel with "options IWI_DEBUG" and see if that enables enough login to > give us a hint about the cause. If that is not enough you would need to > raise iwi_debug to more than the default level of 4, but that would > spam your log with every received packet. I will! The system should be fast enough. I just found that syssrc.tgz doesn't provide builds.h and one needs whole src.tgz to get it.. a little stupid. And also share. Building now will report back once done / rebooted. > Please file a PR and lets collect data there. Done. kern/58232 Riccardo
Re: Intel Wireless fatal error
El mar, 7 may 2024 a las 11:13, Martin Husemann () escribió: > > On Tue, May 07, 2024 at 08:16:18AM +, Riccardo Mottola wrote: > > [ 3574.054462] iwi0: autoconfiguration error: fatal error > > The message is bogus, it has nothing to do with autoconfiguration. > > "Fatal error" is a bit in the interrupt cause register of the intel > chipset. The driver can not do anything about it and resets the device > (simmilar to a "ifconfig iwi0 down). This is not a good error handling > strategy, as you have noticed - and it is also done very wrong in the > iwi_softintr handler. > > The driver should clear the interrupt, schedule a reset and ignore all > other activity untill the reset has happened. Of course the reset should > include bringing up the device to full working state again. > > However, this is obviously not easy to test and debug, as you will have to > be in a setup where this happens often enough (like your's). > If you have patience and would be able to help with this: compile your > kernel with "options IWI_DEBUG" and see if that enables enough login to > give us a hint about the cause. If that is not enough you would need to > raise iwi_debug to more than the default level of 4, but that would > spam your log with every received packet. > > Please file a PR and lets collect data there. > > Martin I remember such messages in my old Compal Electronics laptop i386 machine with iwi0 several months before NetBSD 10 release, at the very early moments after installing. I did not dig into that cause I ended using the more trusty ethernet, but it was very frustrating. If you think I can help with that I can compile the kernel with IWI_DEBUG as said before. It is a computer that I do not use regulary so plenty of space to do experiments. Regards. Ramiro.
Re: Intel Wireless fatal error
On Tue, May 07, 2024 at 08:16:18AM +, Riccardo Mottola wrote: > [ 3574.054462] iwi0: autoconfiguration error: fatal error The message is bogus, it has nothing to do with autoconfiguration. "Fatal error" is a bit in the interrupt cause register of the intel chipset. The driver can not do anything about it and resets the device (simmilar to a "ifconfig iwi0 down). This is not a good error handling strategy, as you have noticed - and it is also done very wrong in the iwi_softintr handler. The driver should clear the interrupt, schedule a reset and ignore all other activity untill the reset has happened. Of course the reset should include bringing up the device to full working state again. However, this is obviously not easy to test and debug, as you will have to be in a setup where this happens often enough (like your's). If you have patience and would be able to help with this: compile your kernel with "options IWI_DEBUG" and see if that enables enough login to give us a hint about the cause. If that is not enough you would need to raise iwi_debug to more than the default level of 4, but that would spam your log with every received packet. Please file a PR and lets collect data there. Martin
Re: Intel Wireless fatal error
Hi, Riccardo Mottola wrote: > dmesg | grep iwi0 > [ 1.005536] iwi0 at pci2 dev 2 function 0: Intel PRO/Wireless LAN > 2200BG Mini-PCI Adapter (rev. 0x05) > [ 1.005536] iwi0: interrupting at irq 11 > [ 1.005536] iwi0: 802.11 address 00:16:6f:0c:0f:59 > [ 3574.054462] iwi0: autoconfiguration error: fatal error > > what autoconfiguration failed after it was running for a while? if those > are directly seconds it would be after 1h. just a little after writing this mail, the network disconnected again. So it lasted like 30 minutes at most :( Again another fatal error. [ 1.005536] iwi0 at pci2 dev 2 function 0: Intel PRO/Wireless LAN 2200BG Mini-PCI Adapter (rev. 0x05) [ 1.005536] iwi0: interrupting at irq 11 [ 1.005536] iwi0: 802.11 address 00:16:6f:0c:0f:59 [ 3574.054462] iwi0: autoconfiguration error: fatal error [ 31534.294058] iwi0: autoconfiguration error: fatal error This connection is stable, the router is literally 2 meters away in the same room, actually a small repeating access point that delivers WEB instead of WPA. For easy connection purposes so wpa_config is not needed while hacking+ Ifconfig shows that the ssid and key were still fine. Just as I write this.. it disconnected again ! Even if all parameters according to ifconfig look fine, including IP, reissuing dhcpcd is not enough! But "ifconfig iwi0 up" after a couple of attempts. [ 3574.054462] iwi0: autoconfiguration error: fatal error [ 31534.294058] iwi0: autoconfiguration error: fatal error [ 32554.279739] iwi0: autoconfiguration error: fatal error [ 33274.150790] iwi0: autoconfiguration error: fatal error Riccardo
Intel Wireless fatal error
Hi, I upgraded my trusty Thinkpad to T30 to 10.0 and now most rough edges have been sorted out. Yesterday I connected it via WiFi, connected remotely to it, then went to bed. Today I see the connection dropped and a green message on the console. Ifconfig says network down. dmesg | grep iwi0 [ 1.005536] iwi0 at pci2 dev 2 function 0: Intel PRO/Wireless LAN 2200BG Mini-PCI Adapter (rev. 0x05) [ 1.005536] iwi0: interrupting at irq 11 [ 1.005536] iwi0: 802.11 address 00:16:6f:0c:0f:59 [ 3574.054462] iwi0: autoconfiguration error: fatal error what autoconfiguration failed after it was running for a while? if those are directly seconds it would be after 1h. This issue happened on 9.3 too, sometimes - but I never checked console/dmesg and related things. Riccardo
