Bug 203915 - ipw2100: Fatal interrupt. Scheduling firmware restart.
Summary: ipw2100: Fatal interrupt. Scheduling firmware restart.
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-17 14:02 UTC by Alexey Kuznetsov
Modified: 2019-09-02 21:27 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.15.0-51-generic
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg, first errors, wifi keep working. (302.02 KB, text/plain)
2019-06-17 14:02 UTC, Alexey Kuznetsov
Details
dmesg (ipw2100: wlp1s4: Failed to start the firmware) (364.04 KB, text/plain)
2019-06-17 14:52 UTC, Alexey Kuznetsov
Details
syslog (2.99 MB, text/plain)
2019-06-17 14:53 UTC, Alexey Kuznetsov
Details
syslog from boot to crash due to ipw2100 (579.73 KB, text/plain)
2019-09-02 21:27 UTC, Gianni
Details

Description Alexey Kuznetsov 2019-06-17 14:02:45 UTC
Created attachment 283303 [details]
dmesg, first errors, wifi keep working.

Hello! My notebook M3N has "01:04.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)" which lose wifi connection one a day and I have to restart the machine.

Seems like this bug was reported back then https://bugzilla.kernel.org/show_bug.cgi?id=15613, but closed due to lack of respond.

So, I did add "echo 32 > /proc/net/ipw2100/debug_level" and ready to post the data.

dmesg getting flooded and cut, so I will add first log from beginning, then later today I will dmesg when wifi get broken.
Comment 1 Alexey Kuznetsov 2019-06-17 14:52:21 UTC
Created attachment 283305 [details]
dmesg (ipw2100: wlp1s4: Failed to start the firmware)

dmesg with "ipw2100: wlp1s4: Failed to start the firmware", got it few minutes after reboot, very lucky. Message means - wifi no longer works, has to reboot machine. I will add syslog
Comment 2 Alexey Kuznetsov 2019-06-17 14:53:27 UTC
Created attachment 283307 [details]
syslog

iwlist scan:

lo        Interface doesn't support scanning.

enp1s8    Interface doesn't support scanning.

wlp1s4    No scan results
Comment 3 Alexey Kuznetsov 2019-06-17 14:56:23 UTC
Ubuntu related bug: https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776
Comment 4 WhoAmEye 2019-06-17 20:23:59 UTC
Maybe you should loop in linuxwifi@intel.com
Comment 5 Emmanuel Grumbach 2019-06-25 12:25:46 UTC
realistically, this won't be fixed.
We don't support this driver, and even less the firmware of this 13 year old device.

You can try to contact its maintainer though.
Comment 6 Alexey Kuznetsov 2019-06-25 12:40:49 UTC
If you do not want support device, it would be fair to release firmware source code for this device. I did not know Intel blocking fixing old hardware issues, forcing people to buy new hardware.
Comment 7 Gianni 2019-09-02 21:24:56 UTC
I am on xubuntu 18.04.3 LTS and I am experiencing the same issue.
kernel: 4.4.190
device: Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)

In my case the wifi card seems to freeze my pc after a random amount of time, and it seems to do so during high workloads (such as downloading a large file), but not always.
In my case I activated the debug option via putting ipw2100.debug=32 kernel parameter at boot time (I compiled the kernel with support for this option), since this path "/proc/net/ipw2100/debug_level" would not work on ubuntu (at least in my experience).

I am appending a syslog that goes from pc boot to the relevant crash.

I am available to provide more info as needed.

It's unfortunate that a card that shows itself to be capable to connecting me to the web seems to have such a  detrimental bug that basically renders the card completely unreliable.
Comment 8 Gianni 2019-09-02 21:27:05 UTC
Created attachment 284771 [details]
syslog from boot to crash due to ipw2100

extract from my syslog that shows a complete log of one session that goes from pc boot to the pc crashing due to the wifi card (crashes are only there when the wifi card is activated)

Note You need to log in before you can comment on or make changes to this bug.