iwl3945 crashes randomly

This change was made by a bot.

tristezo2k, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

I have the same network controller and

I have been having trouble with wifi stopping working intermittently after updating to 16.04 requiring a reboot so I surmise this is the correct issue.

I am currently on 16.10 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 05:28:27 UTC 2016 but the issue still remains.

There were no problems with 15.10, this issue started only after 16.04.

drwt, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

I've been having the same issue for a number of months now, not fixed on the upgrade to 16.10. It's now happening multiple times a day, meaning the laptop needs to be connected via ethernet for it to be reliable. Anything I can do? Just report it to the Ubuntu repository kernel like drwt?

mxyzptlk, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

mxyzptlk, I did some bisection in the following bug if its of any help:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629603

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Problem still exists. I have the same Wi fi.
Sometime just turned off and everything. Interface Restarting does not help.
Проблема осталась. У меня такая же вай фай.
Переодически просто отключается и всё. Перезапуск интерфейсов не помогает.

Same here with kernel 4.4.49 on Slackware. (Custom build)

The "solution" in my case is: modprobe -r iwl3945 > wifi button off (I have a physical button) > standby (suspend to ram) > power on the computer > wifi switch on > modprobe iwl3945

Someone who has the time and energy should probably take this upstream.

I believe here are the correct contact info: https://wireless.wiki.kernel.org/en/users/drivers/iwlegacy#support

I have send email to the above page.

I have response from "intel-driver-man" and I think he is right. I indeed manually enabled powersaving via powertop.

I quote:
"This could be caused by power save, which is disable by default
in the driver but some programs/distribution seems to enable
it without user knowlage. First check:

$ iw dev wlan0 get power_save

and if PS is enabled, disable by:

$ iw dev wlan0 set power_save off

and check if problem still happen.

@drwt about your remark:
> I looked at all kernel versions that had changes committed to iwlwifi and tested between them.
>
> I now have determined that I do not have this issue in the kernel version 4.4.4.
>
> I do have the issue in 4.4.6 and that is the next kernel version that has changes to iwlwifi so I guess that is the first bad version."

This does not make sense as 3945 device is handled by
iwl3495 (iwlegacy) driver, not by iwlwifi.

I have the issue with wifi power save off so it cant be that.

try those commands.

iwconfig wlan0 retry 30
iwconfig wlan0 frag 2346
iwconfig wlan0 rts 2347

No help from those commands.

I have an HP6710b that was working until around 6 June. Since then the firmware for the 3945 does not appear to have been loading and wifi is completely dead.
16.04, up to date.

Another laptop, HP nc6320, also has 3945 and 16.04, yet wifi is ok.#

john@john-HP-Compaq-6710b-GR680ET-ABU:~$ dmesg | grep firmware
[ 2.908019] tg3 0000:18:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update
[ 2.968042] tg3 0000:18:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update
[ 3.028026] tg3 0000:18:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update
john@john-HP-Compaq-6710b-GR680ET-ABU:~$ dmesg | grep iwl
[ 29.009428] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:s
[ 29.009432] iwl3945: Copyright(c) 2003-2011 Intel Corporation
[ 29.009500] iwl3945 0000:10:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 29.072355] iwl3945 0000:10:00.0: Tunable channels: 13 802.11bg, 23 802.11a channels
[ 29.072360] iwl3945 0000:10:00.0: Detected Intel Wireless WiFi Link 3945ABG
[ 29.082108] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs'
[ 30.207394] iwl3945 0000:10:00.0 wlp16s0: renamed from wlan0
john@john-HP-Compaq-6710b-GR680ET-ABU:~$ lspci -nnk | grep -iA2 net
10:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4222] (rev 02)
        Subsystem: Hewlett-Packard Company PRO/Wireless 3945ABG [Golan] Network Connection [103c:135c]
        Kernel driver in use: iwl3945
        Kernel modules: iwl3945
18:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express [14e4:1693] (rev 02)
        Subsystem: Hewlett-Packard Company 6710b [103c:30c0]
        Kernel driver in use: tg3
john@john-HP-Compaq-6710b-GR680ET-ABU:~$

After much fruitless experiment I loaded an SL7.3 KDE live disk. The dmesg | grep firmware response had only one line of 'vpd r/w failed' (which seems to have been around for a long time) followed by a successful load of the iwl3945 firmware. But still no wifi connection - until, on editing the config security, I was asked to grant access to the Kwallet.

Once I had done that, it all started working. So it isn't the hardware problem that I had feared; but I'm not clear how to translate it to kubuntu.

This is clearly not directly related to the bug definition, but I'm not getting wifi with a dongle that used to work. Here's dmesg on plugging it in. I'm in the UK.

  642.752097] usb 2-5: new high-speed USB device number 4 using ehci-pci
[ 642.932296] usb 2-5: New USB device found, idVendor=0846, idProduct=9001
[ 642.932311] usb 2-5: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[ 642.932319] usb 2-5: Product: USB2.0 WLAN
[ 642.932325] usb 2-5: Manufacturer: ATHER
[ 642.932331] usb 2-5: SerialNumber: 12345
[ 644.932085] usb 2-5: reset high-speed USB device number 4 using ehci-pci
[ 645.101053] usbcore: registered new interface driver carl9170
[ 645.113059] usb 2-5: driver API: 1.9.7 2012-12-15 [1-1]
[ 645.113066] usb 2-5: firmware API: 1.9.6 2012-07-07
[ 645.458207] ath: EEPROM regdomain: 0x0
[ 645.458215] ath: EEPROM indicates default country code should be used
[ 645.458219] ath: doing EEPROM country->regdmn map search
[ 645.458225] ath: country maps to regdmn code: 0x3a
[ 645.458230] ath: Country alpha2 being used: US
[ 645.458234] ath: Regpair used: 0x3a
[ 645.461764] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[ 645.468290] usb 2-5: Atheros AR9170 is registered as 'phy1'
[ 645.646656] carl9170 2-5:1.0 wlx0026f298b969: renamed from wlan0
[ 645.933258] cfg80211: Regulatory domain changed to country: US
[ 645.933263] cfg80211: DFS Master region: FCC
[ 645.933265] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 645.933268] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
[ 645.933271] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 1700 mBm), (N/A)
[ 645.933275] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s)
[ 645.933277] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s)
[ 645.933279] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
[ 645.933282] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
[ 647.067292] IPv6: ADDRCONF(NETDEV_UP): wlx0026f298b969: link is not ready

This laptop, similar age, connects fine - although I haven't tried leaving it running for long.

john@john-HP-Compaq-nc6320-RH367ET-ABU:~$ lspci -nnk | grep -iA2 net
02:0e.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5788 Gigabit Ethernet [14e4:169c] (rev 03)
        Subsystem: Hewlett-Packard Company NetXtreme BCM5788 Gigabit Ethernet [103c:30aa]
        Kernel driver in use: tg3
        Kernel modules: tg3
08:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4222] (rev 02)
        Subsystem: Hewlett-Packard Company PRO/Wireless 3945ABG [Golan] Network Connection [103c:135c]
        Kernel driver in use: iwl3945
        Kernel modules: iwl3945
john@john-HP-Compaq-nc6320-RH367ET-ABU:~$

A second HP 6710b has wifi that still works. I have not tried an update.

matthew@matthew-HP-Compaq-6710b-GB898ET-ABU:~$ uname -rsvp
Linux 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64

I installed the 16.04 HWE option on the problematic HP 6710b, but it has had no effect on the wifi.
It did cause a black-screen problem and drm_wait messages, worked around by disabling SVIDEO in grub.

$ uname -rsvp
Linux 4.8.0-58-generic #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64

$ dmesg | grep firm
[ 3.764045] tg3 0000:18:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update

but I have found nothing that looks hopeful.

The change of wording from 'vpd r/w' to 'VPD access' follows kernel patch 8385431.
I found an HP advisory about the tg3 driver for Proliant servers and a specific el6 kernel, but it doesn't seem applicable here.

so still no iwl3945 firmware load. I've tried

sudo modprobe -v iwl3945 fw_restart=1, with no apparent effect.

The VPD error message is addressed in this document from HP

http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=mmr_kc-0131686

which has links to kernel patches from SUSE that are related to the one in comment #25

It isn't clear to me how much of this is already in the 'buntu kernels, or what effect the "VPD" problem has on the loading of the iwl3945 firmware and my wifi access.

Hello,
I am adding some experience and a new dump.
Trying to get more data, I build my own kernel from ubuntu sources, leaving JUST iwl3945, and enabling debugging.
I still have the issue.
However, I notice the ... crash? happens more often if I am far/low signal. While I am near the AP, the occurrence is quite low.
I now read there is a suggestion to turn off power save, and I will do for further tests.
In case it is relevant, here is my .config: https://pastebin.com/kJMrQSqr

Here is my info:
seba@D630:~$ uname -a
Linux D630 4.10.17-seba-02-dirty #2 SMP PREEMPT Thu Aug 10 23:58:20 ART 2017 x86_64 x86_64 x86_64 GNU/Linux
seba@D630:~$ dmesg|grep iwl
[ 2.120918] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:ds
[ 2.120920] iwl3945: Copyright(c) 2003-2011 Intel Corporation
[ 2.120980] iwl3945 0000:0c:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 2.893534] iwl3945 0000:0c:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
[ 2.893536] iwl3945 0000:0c:00.0: Detected Intel Wireless WiFi Link 3945ABG
[ 2.961072] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs'
[ 3.177796] iwl3945 0000:0c:00.0 wlp12s0: renamed from wlan0
[ 4.729980] iwl3945 0000:0c:00.0: loaded firmware version 15.32.2.9
[ 3558.511047] iwl3945 0000:0c:00.0: Queue 4 stuck for 2016 ms.
[ 3558.511059] iwl3945 0000:0c:00.0: On demand firmware reload
...
[ 2772.703212] wlp12s0: detected beacon loss from AP (missed 7 beacons) - probing
[ 2849.436436] wlp12s0: cancelling AP probe due to a received beacon
[ 2969.412241] wlp12s0: cancelling AP probe due to a received beacon
[ 3089.426654] wlp12s0: cancelling AP probe due to a received beacon
[ 3209.436499] wlp12s0: cancelling AP probe due to a received beacon
[ 3329.444913] wlp12s0: cancelling AP probe due to a received beacon
[ 3449.418406] wlp12s0: cancelling AP probe due to a received beacon
[ 3558.511047] iwl3945 0000:0c:00.0: Queue 4 stuck for 2016 ms.
[ 3558.511059] iwl3945 0000:0c:00.0: On demand firmware reload
[ 3558.517453] ieee80211 phy0: Hardware restart was requested
[ 3558.566281] iwl3945 0000:0c:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020
[ 3558.566286] iwl3945 0000:0c:00.0: Unable to set up bootstrap uCode: -5
[ 3558.613179] iwl3945 0000:0c:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020
[ 3558.613185] iwl3945 0000:0c:00.0: Unable to set up bootstrap uCode: -5
[ 3558.660085] iwl3945 0000:0c:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020
[ 3558.660091] iwl3945 0000:0c:00.0: Unable to set up bootstrap uCode: -5
[ 3558.706972] iwl3945 0000:0c:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020
[ 3558.706978] iwl3945 0000:0c:00.0: Unable to set up bootstrap uCode: -5
[ 3558.753710] iwl3945 0000:0c:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020
[ 3558.753736] iwl3945 0000:0c:00.0: Unable to set up bootstrap uCode: -5
[ 3558.790577] iwl3945 0000:0c:00.0: Unable to initialize device after 5 attempts.
[ 3...

It looks like it is indeed a power management issue. Last threee days I made and manually run this script when I login;
seba@D630:~$ cat $HOME/bin/iwl_power_save.sh
sudo iw dev wlp12s0 get power_save
sudo iw dev wlp12s0 set power_save off
sudo iw dev wlp12s0 get power_save

and I haven't had any issue.
Everytime I boot power management is on and I switch it off.
I will report in a week. Maybe I will also switch back to the HWE kernel to make sure this is reproducible with the ubuntu kernel.

I have tried this script, modified to use wlp16s0. It reports 'Power save: off' on both entry and exit and has no apparent effect. Still no firmware load, and ifconfig -a shows no inet address.

I had the same problem. I disabled power-save like korgman (korgie) wrote.
look, if power-save is enabled...
-> $ iw dev wlan0 get power_save
if yes, do this...
-> $ iw dev wlan0 set power_save off

Buf if there will be a new kernel (I guess), you have to repeat this.

(my laptop ist a x60 lenovo with kernel 4.4.0-97-generic i686 running on Ubuntu 16.04.3 LTS)

I'd like to add a few things:
- When signal is lower this happens more often.
- Disabling power management didn't help.
- The issue does not happen with a 751U-2HnD (three weeks testing), but
with a cheap tp-link is more probable.

On Fri, Oct 13, 2017 at 4:04 PM, Erp Folger <email address hidden>
wrote:

> I had the same problem. I disabled power-save like korgman (korgie) wrote.
> look, if power-save is enabled...
> -> $ iw dev wlan0 get power_save
> if yes, do this...
> -> $ iw dev wlan0 set power_save off
>
> Buf if there will be a new kernel (I guess), you have to repeat this.
>
> (my laptop ist a x60 lenovo with kernel 4.4.0-97-generic i686 running on
> Ubuntu 16.04.3 LTS)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1627828
>
> Title:
> iwl3945 crashes randomly
>
> Status in linux package in Ubuntu:
> Confirmed
>

--
i prefer to wear my pants backwards, because it is more thrilling to me,
intellectually ( @billwurtz )

My problem with iwl3945, (no wifi and no report of firmware load, comments #19 and on) seems to have been resolved. I don't know what caused it initially, but after removing *all* apparently-broadcom-related packages wifi works on two hp6710b laptops running fully updated xenial with the HWE stack.

https://askubuntu.com/questions/1000415/wifi-works-from-live-dvd-but-firmware-does-not-load-from-fully-updated-kubuntu-x/1001085#1001085

Hello,

This is just to say problem has been solved for me with the

sudo iw dev wlp12s0 set power_save off

command.

My laptop is a Dell Latitude D620, running Ubuntu 18.04 with mainline 4.19.77-041977-generic kernel