[SOLVED]Wifi failure overnight

Gelatinous · 2017-05-03 15:52:05

Hi all,

I'm not sure if this is the correct forum to post this under. If it isn't can a mod kindly move it to the appropriate section.

I woke up this morning and discovered that my laptop (Acer Aspire 5920G) had lost it's internet connection.

uname -a

Linux bunsen-box 3.16.0-4-686-pae #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) i686 GNU/Linux

I am running an install from the Deuterium iso if that matters.

I checked /var/log/syslog.1 in vim and found the following:

(This is just an excerpt from syslog.1)

1137 May  2 23:25:51 bunsen-box wpa_supplicant[1000]: wlan0: Trying to associate with 10:86:8c:5a:07:96 (SSID='Hide Yo Kids Hide Yo WiFi-2.4' freq=2437 MHz)
1138 May  2 23:25:51 bunsen-box NetworkManager[462]: <info> (wlan0): supplicant interface state: scanning -> authenticating
1139 May  2 23:25:51 bunsen-box kernel: [352267.668036] wlan0: associate with 10:86:8c:5a:07:96 (try 1/3)
1140 May  2 23:25:51 bunsen-box NetworkManager[462]: <info> (wlan0): supplicant interface state: authenticating -> associating
1141 May  2 23:25:51 bunsen-box kernel: [352267.678299] wlan0: RX AssocResp from 10:86:8c:5a:07:96 (capab=0x431 status=0 aid=1)
1142 May  2 23:25:51 bunsen-box wpa_supplicant[1000]: wlan0: Associated with 10:86:8c:5a:07:96
1143 May  2 23:25:51 bunsen-box kernel: [352267.684655] wlan0: associated
1144 May  2 23:25:51 bunsen-box kernel: [352267.684722] cfg80211: Calling CRDA for country: US
1145 May  2 23:25:51 bunsen-box wpa_supplicant[1000]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
1146 May  2 23:25:51 bunsen-box NetworkManager[462]: <info> (wlan0): supplicant interface state: associating -> associated
1147 May  2 23:25:51 bunsen-box kernel: [352267.689355] cfg80211: Regulatory domain changed to country: US
1148 May  2 23:25:51 bunsen-box kernel: [352267.689360] cfg80211:  DFS Master region: FCC
1149 May  2 23:25:51 bunsen-box kernel: [352267.689364] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
1150 May  2 23:25:51 bunsen-box kernel: [352267.689368] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
1151 May  2 23:25:51 bunsen-box kernel: [352267.689373] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (N/A)
1152 May  2 23:25:51 bunsen-box kernel: [352267.689378] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s)
1153 May  2 23:25:51 bunsen-box kernel: [352267.689382] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s)
1154 May  2 23:25:51 bunsen-box kernel: [352267.689386] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
1155 May  2 23:25:51 bunsen-box kernel: [352267.689390] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
1156 May  2 23:25:52 bunsen-box NetworkManager[462]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
1157 May  2 23:25:52 bunsen-box wpa_supplicant[1000]: wlan0: WPA: Key negotiation completed with 10:86:8c:5a:07:96 [PTK=CCMP GTK=TKIP]
1158 May  2 23:25:52 bunsen-box wpa_supplicant[1000]: wlan0: CTRL-EVENT-CONNECTED - Connection to 10:86:8c:5a:07:96 completed [id=0 id_str=]
1159 May  2 23:25:52 bunsen-box NetworkManager[462]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
1160 May  2 23:33:39 bunsen-box kernel: [352736.038004] iwl3945 0000:06:00.0: HARDWARE GONE?? INTA == 0xffffffff
1161 May  2 23:33:40 bunsen-box kernel: [352736.528084] iwl3945 0000:06:00.0: Error sending C_TX_PWR_TBL: time out after 500ms.
1162 May  2 23:33:40 bunsen-box kernel: [352736.528097] iwl3945 0000:06:00.0: Error setting Tx power (-110).
1163 May  2 23:33:40 bunsen-box kernel: [352737.084071] iwl3945 0000:06:00.0: Error sending C_RXON: time out after 500ms.
1164 May  2 23:33:40 bunsen-box kernel: [352737.084084] iwl3945 0000:06:00.0: Error clearing ASSOC_MSK on current configuration (-110).
1165 May  2 23:33:41 bunsen-box kernel: [352737.880035] iwl3945 0000:06:00.0: Error sending C_RXON: time out after 500ms.
1166 May  2 23:33:41 bunsen-box kernel: [352737.880043] iwl3945 0000:06:00.0: Error clearing ASSOC_MSK on current configuration (-110).
1167 May  2 23:33:41 bunsen-box kernel: [352738.168065] iwl3945 0000:06:00.0: Queue 4 stuck for 2140 ms.
1168 May  2 23:33:41 bunsen-box kernel: [352738.168076] iwl3945 0000:06:00.0: On demand firmware reload
1169 May  2 23:33:42 bunsen-box kernel: [352738.436087] iwl3945 0000:06:00.0: Error sending C_RXON: time out after 500ms.
1170 May  2 23:33:42 bunsen-box kernel: [352738.436099] iwl3945 0000:06:00.0: Error clearing ASSOC_MSK on current configuration (-110).
1171 May  2 23:33:42 bunsen-box kernel: [352738.436434] ieee80211 phy0: Hardware restart was requested
1172 May  2 23:33:42 bunsen-box kernel: [352738.440125] ------------[ cut here ]------------
1173 May  2 23:33:42 bunsen-box kernel: [352738.440125] WARNING: CPU: 0 PID: 1344 at /build/linux-2IfvRo/linux-3.16.39/drivers/net/wireless/iwlegacy/common.c:     116 _il_grab_nic_access+0xa0/0xb0 [iwlegacy]()
1174 May  2 23:33:42 bunsen-box kernel: [352738.440125] Timeout waiting for ucode processor access (CSR_GP_CNTRL 0xffffffff)
1175 May  2 23:33:42 bunsen-box kernel: [352738.440125] Modules linked in: hid_microsoft usbhid hid isofs udf ctr ccm cpufreq_powersave cpufreq_stats cpufreq_     conservative cpufreq_userspace nouveau uvcvideo iTCO_wdt iTCO_vendor_support r852 videobuf2_vmalloc acer_wmi sparse_keymap sm_common arc4 coretemp videob     uf2_memops videobuf2_core mxm_wmi r592 pcspkr iwl3945 nand v4l2_common joydev evdev ttm iwlegacy nand_ecc memstick videodev drm_kms_helper serio_raw nand     _bch bch nand_ids media drm mtd i2c_i801 mac80211 lpc_ich i2c_algo_bit mfd_core i2c_core cfg80211 wmi battery rfkill snd_hda_codec_realtek snd_hda_codec_     generic snd_hda_intel snd_hda_controller shpchp snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore video ac button acpi_cpufreq processor fuse autof     s4 ext4 crc16 mbcache jbd2 crc32c_generic btrfs xor raid6_pq sg sd_mod crc_t10dif crct10dif_generic crct10dif_common sr_mod cdrom ata_generic psmouse ata     _piix libata firewire_ohci scsi_mod sdhci_pci sdhci mmc_core firewire_core crc_itu_t tg3 ptp pps_core libphy thermal thermal_sys ehci_pci uhci_hcd ehci_h     cd usbcore usb_common
1176 May  2 23:33:42 bunsen-box kernel: [352738.440125] CPU: 0 PID: 1344 Comm: kworker/0:0 Not tainted 3.16.0-4-686-pae #1 Debian 3.16.39-1+deb8u2
1177 May  2 23:33:42 bunsen-box kernel: [352738.440125] Hardware name: Acer, inc. Aspire 5920G    /Chapala         , BIOS v1.3808 01/29/2008
1178 May  2 23:33:42 bunsen-box kernel: [352738.440125] Workqueue: events ieee80211_restart_work [mac80211]
1179 May  2 23:33:42 bunsen-box kernel: [352738.440125]  00000000 e6827d30 c147db97 e6827d40 f8383f5c c1057b34 f838402c e6827d5c
1180 May  2 23:33:42 bunsen-box kernel: [352738.440125]  00000540 f8383f5c 00000074 f837c7f0 f837c7f0 00000009 00000000 f7320e40
1181 May  2 23:33:42 bunsen-box kernel: [352738.440125]  00000082 e6827d48 c1057b83 00000009 e6827d40 f838402c e6827d5c e6827d68
1182 May  2 23:33:42 bunsen-box kernel: [352738.440125] Call Trace:
1183 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<c147db97>] ? dump_stack+0x55/0x6e
1184 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<c1057b34>] ? warn_slowpath_common+0x84/0xa0
1185 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<f837c7f0>] ? _il_grab_nic_access+0xa0/0xb0 [iwlegacy]
1186 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<f837c7f0>] ? _il_grab_nic_access+0xa0/0xb0 [iwlegacy]
1187 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<c1057b83>] ? warn_slowpath_fmt+0x33/0x40
1188 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<f837c7f0>] ? _il_grab_nic_access+0xa0/0xb0 [iwlegacy]
1189 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<f837c93c>] ? il_wr_prph+0x2c/0x80 [iwlegacy]
1190 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<f837deb1>] ? il_apm_init+0x161/0x1d0 [iwlegacy]
1191 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<f8369ef5>] ? il3945_apm_init+0x15/0x130 [iwl3945]
1192 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<f836ac12>] ? il3945_hw_nic_init+0x32/0x540 [iwl3945]
1193 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<f8366c02>] ? __il3945_up+0xb2/0x280 [iwl3945]
1194 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<f8367fe7>] ? il3945_mac_start+0x277/0x610 [iwl3945]
1195 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<c106d377>] ? __queue_work+0xf7/0x2d0
1196 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<f84bf09f>] ? __ieee80211_scan_completed+0x10f/0x350 [mac80211]
1197 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<f84e128e>] ? ieee80211_reconfig+0x21e/0x1600 [mac80211]
1198 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<f84c03df>] ? ieee80211_scan_cancel+0xcf/0x1b0 [mac80211]
1199 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<c1063231>] ? del_timer_sync+0x41/0x50
1200 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<f84b71cf>] ? ieee80211_restart_work+0x5f/0xa0 [mac80211]
1201 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<c106eea9>] ? process_one_work+0x109/0x370
1202 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<c106d18d>] ? pwq_activate_delayed_work+0x2d/0x80
1203 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<c106f6fd>] ? worker_thread+0xed/0x490
1204 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<c109176f>] ? __wake_up_locked+0x1f/0x30
1205 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<c106f610>] ? create_and_start_worker+0x50/0x50
1206 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<c107493b>] ? kthread+0x9b/0xb0
1207 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<c1482a41>] ? ret_from_kernel_thread+0x21/0x30
1208 May  2 23:33:42 bunsen-box kernel: [352738.440125]  [<c10748a0>] ? kthread_create_on_node+0x110/0x110
1209 May  2 23:33:42 bunsen-box kernel: [352738.440125] ---[ end trace 58a39c84382e47e6 ]---
1210 May  2 23:33:43 bunsen-box kernel: [352739.373843] iwl3945 0000:06:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xffffffff, s/b      0xf802020
1211 May  2 23:33:43 bunsen-box kernel: [352739.373854] iwl3945 0000:06:00.0: Unable to set up bootstrap uCode: -5
1212 May  2 23:33:43 bunsen-box kernel: [352739.501846] iwl3945 0000:06:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xffffffff, s/b      0xf802020
1213 May  2 23:33:43 bunsen-box kernel: [352739.501854] iwl3945 0000:06:00.0: Unable to set up bootstrap uCode: -5
1214 May  2 23:33:43 bunsen-box kernel: [352739.629751] iwl3945 0000:06:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xffffffff, s/b      0xf802020
1215 May  2 23:33:43 bunsen-box kernel: [352739.629758] iwl3945 0000:06:00.0: Unable to set up bootstrap uCode: -5
1216 May  2 23:33:43 bunsen-box kernel: [352739.757687] iwl3945 0000:06:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xffffffff, s/b      0xf802020
1217 May  2 23:33:43 bunsen-box kernel: [352739.757694] iwl3945 0000:06:00.0: Unable to set up bootstrap uCode: -5
1218 May  2 23:33:43 bunsen-box kernel: [352739.885726] iwl3945 0000:06:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xffffffff, s/b      0xf802020
1219 May  2 23:33:43 bunsen-box kernel: [352739.885734] iwl3945 0000:06:00.0: Unable to set up bootstrap uCode: -5
1220 May  2 23:33:43 bunsen-box kernel: [352739.885991] iwl3945 0000:06:00.0: Unable to initialize device after 5 attempts.

My only recourse was a reboot as my linux network knowledge is limited. I'm not sure if it's related or not, but on the laptop I find that slowly over time the wifi will slow to a crawl and sites with https:// will stop loading until I disconnect and reconnect.

Please let me know what information you would like as I'm not sure what I should be posting for debugging.

Thanks,

Chris

Last edited by Gelatinous (2017-05-28 22:47:49)

Horizon_Brave · 2017-05-03 17:04:24

Did you do any changes updates before it stopped working?

On a terminal, what is the output of:

lspci -knn | grep -iA3 'net'

Is this an internal built in networking wireless card? or an external one you're using?

Head_on_a_Stick · 2017-05-03 17:08:01

Do these problems still occur if you load up the BunsenLabs ISO image and select the "live session"?

I think your card may be dying

Gelatinous · 2017-05-03 17:41:32

Horizon_Brave wrote:

Did you do any changes updates before it stopped working?
On a terminal, what is the output of:
lspci -knn | grep -iA3 'net'
Is this an internal built in networking wireless card? or an external one you're using?

It's an internal wireless card, Intel. I don't recall doing any updates in the last week or so and it's been a problem (the slowing until https:// stops) since first install. It wasn't an issue with Windows 7 when I had that installed though. It's only had the total loss of network that comes back with a reboot once before.

I'll pop it open and check connections as well, I'd hate for it to be something silly like that even though it failed just sitting idle overnight.

06:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4222] (rev 02)
	Subsystem: Intel Corporation PRO/Wireless 3945ABG Network Connection [8086:1000]
	Kernel driver in use: iwl3945
08:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express [14e4:1693] (rev 02)
	Subsystem: Acer Incorporated [ALI] Aspire 5920G [1025:0121]
	Kernel driver in use: tg3
0a:09.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 05)

Head_on_a_Stick wrote:

Do these problems still occur if you load up the BunsenLabs ISO image and select the "live session"?
I think your card may be dying hmm

I haven't tried the live session for any length of time. I can give it a go though.

Gelatinous · 2017-05-03 22:21:48

Well,

The wifi failed again so I am now posting from the live image. I have a terminal running with sudo tail -f /var/log/syslog so that I can monitor for the failure. I'm going to leave the machine running to see what happens.

I was doing some research and it looks like I'm not the only person it has happened to with regards to the Intel module stopping functioning in Linux.

https://lists.gt.net/linux/kernel/1472187

That persons issue was with their laptop dieing while in suspend, their WiFi module failed to restart. Towards the end of the mailing list they're talking about kernel version 3.2-rc7 that supposedly fixes an issue with a bridge not being enabled? and so I was wondering if trying a different kernel would be an option for me. That is assuming it fails under the live image as well? Or would it be an option either way.

Thanks,

Chris

EDIT: Forgot to say that I pulled the bottom off the laptop and reseated the card. It looks like a PCI-e connector and two screws to hold the card in place. As far as I know it has never been removed prior to my doing so today.

Last edited by Gelatinous (2017-05-03 22:23:18)

ohnonot · 2017-05-04 05:10:50

- you should remeber whether you did an update/upgrade or not. afaik, bl does not automate that for you. it is VERY important to know for this issue, otherwise how can it be software related if a) it worked before and b) works on live.

- i think you should also monitor

dmesg -w

Head_on_a_Stick · 2017-05-04 06:31:35

Gelatinous wrote:

Towards the end of the mailing list they're talking about kernel version 3.2-rc7 that supposedly fixes an issue with a bridge not being enabled? and so I was wondering if trying a different kernel would be an option for me.

BunsenLabs ships with kernel 3.16 so already has the fix discussed in that thread (16>2).

You could try the backported kernel but that is (much) more likely to have regressions than the stock kernel:

https://forums.bunsenlabs.org/viewtopic.php?id=1257

Horizon_Brave · 2017-05-04 16:25:30

Gelantinous: You probably don't have it still in it's 'down' state, but next time this happens, and you loose connectivity, post the output of :

journalctl

Do this while the network is experienceing the issue, and grep for something like NetworkManager, or just network maybe.

Likewise, *before* the disconnect happens set up your pc to run from the command line:

nmcli monitor

Maybe your card is reaching out, and trying to connect (roam) to other access points that present stronger signals

Gelatinous · 2017-05-04 23:37:38

ohnonot wrote:

- you should remeber whether you did an update/upgrade or not. afaik, bl does not automate that for you. it is VERY important to know for this issue, otherwise how can it be software related if a) it worked before and b) works on live.

Since I didn't really have any idea what or when I had last updated, I backed up my info that I wanted to save (I don't use the laptop for much) and reinstalled.

Since then it has been fine, at least so far. There are a couple applications that use the network that I have not yet reinstalled just to see. Those applications are MessengerForDesktop and yakyak.

I did the reinstall this morning after letting the live session run overnight with no wifi failures.

I've seen some disconnects, ieee80211 phy0: wlan0: No probe response from AP <address removed> after 500ms, disconnecting.

so I added a line to /etc/modprobe.d/mac80211.conf

options mac80211 probe_wait_ms=1000

I've only just rebooted since making the changes to the conf file so we'll see if I see any more disconnect messages, but I haven't seen any failures.

I'm still monitoring

/var/log/syslog

and

dmesg -w

and will now add

nmcli monitor

to the mix.

chris@bunsen-box:~$ journalctl
No journal files were found.

but it has been working fine since the reinstall. I will try this again if it fails again.

just tried nmcli monitor.... monitor wasn't recognized

ohnonot · 2017-05-05 06:15:19

Gelatinous wrote:

so I added a line to /etc/modprobe.d/mac80211.conf
options mac80211 probe_wait_ms=1000

nifty.
where'd you get that from? is it kosher?

about journalctl: on debian jessie it has to be explicitely enabled iirc. guides on these very forums.

Head_on_a_Stick · 2017-05-05 06:30:20

Edit the Storage line in /etc/systemd/journald.conf to enable persistent logging, for more on this read

man journald.conf

Gelatinous · 2017-05-05 14:53:56

ohnonot wrote:

Gelatinous wrote:
so I added a line to /etc/modprobe.d/mac80211.conf
options mac80211 probe_wait_ms=1000
nifty.
where'd you get that from? is it kosher?

about journalctl: on debian jessie it has to be explicitely enabled iirc. guides on these very forums.

I have no idea if it's kosher or not, but I got it from here:

https://ubuntuforums.org/archive/index. … 41623.html

search for the user "chili555" and a post dated "May 8th, 2013, 11:26 PM"

I'll look into enabling journaling here shortly.

While the WiFi didn't fail, it did slow down to a crawl and I was forced to reconnect to the access point. I found that it still gave a no response from access point in 1000ms, disconnecting message in dmesg, but at a much much lower rate than before. I'm going to try 1500ms and see if that makes it any better.

damo · 2017-05-05 15:14:26

This may be a silly question, but is the problem with the router? Have you tried wifi in other locations?

Gelatinous · 2017-05-05 15:39:01

damo wrote:

This may be a silly question, but is the problem with the router? Have you tried wifi in other locations?

I don't think it's an issue with the router, my Windows 8.1 PC, Windows 10 laptop, my wife's Mac, her android phone and my Blackberry all stay connected with fast transfer speeds. It's only this the laptops I have that are running Linux that have the disconnect issue. Both laptops are running BL, one is plain hydrogen (Toshiba Celeron M), the other (Acer 5920G) is running the Deuterium point release.

That being said, I have not tried it in other locations. I'm in a Starbucks on their Google WiFi right now, but it auto disconnects every so often, even with my Windows 10 Laptop.

Horizon_Brave · 2017-05-05 17:45:13

hmm again this could be an issue with your card trying to join another network that's nearby? Look around at the nm (network-manager) suite of commands. And yea definitely enable journald's journaling features. You just need to edit one of the files.

Gelatinous · 2017-05-05 17:51:39

Horizon_Brave wrote:

hmm again this could be an issue with your card trying to join another network that's nearby? Look around at the nm (network-manager) suite of commands. And yea definitely enable journald's journaling features. You just need to edit one of the files.

Thanks! I'll read up on nm and nmcli to see what I can see. I've just enabled persistent storage in journald.conf as well.

Head_on_a_Stick · 2017-05-05 20:26:53

Try disabling 802.11n

https://wiki.archlinux.org/index.php/Wi … n#iwlegacy

Gelatinous · 2017-05-07 16:59:40

Head_on_a_Stick wrote:

Try disabling 802.11n
https://wiki.archlinux.org/index.php/Wi … n#iwlegacy

I've disabled 802.11n per those instructions. It's doing much better now. It does still slow to a crawl, but much less frequently. I was going through my dmesg -w and spotted this this morning.

[ 7314.541575] iwl3945 0000:06:00.0: Microcode SW error detected. Restarting 0x82000008.
[ 7314.541600] iwl3945 0000:06:00.0: Loaded firmware version: 15.32.2.9
[ 7314.541643] iwl3945 0000:06:00.0: Start IWL Error Log Dump:
[ 7314.541650] iwl3945 0000:06:00.0: Status: 0x000202E4, count: 1
[ 7314.541657] iwl3945 0000:06:00.0: Desc       Time       asrtPC  blink2 ilink1  nmiPC   Line
[ 7314.541889] iwl3945 0000:06:00.0: SYSASSERT     (0x5) 0000201036 0x008B6 0x00274 0x0031C 0x04EA4 116

[ 7314.541911] iwl3945 0000:06:00.0: Error Reply type 0x00000005 cmd C_TX (0x1C) seq 0x00E0 ser 0x00740000
[ 7315.044269] iwl3945 0000:06:00.0: Error sending C_RATE_SCALE: time out after 500ms.
[ 7315.044281] iwl3945 0000:06:00.0: Error setting HW rate table: FFFFFF92
[ 7315.046048] iwl3945 0000:06:00.0: Can't stop Rx DMA.
[ 7315.046290] ieee80211 phy0: Hardware restart was requested

and even with the probe timeout set to 1500ms it still disconnects. I'm going to be looking into the nm monitoring options to see if it's trying to hop to another access point, but I've only ever connected to my home one with this machine, or the starbucks google wifi, but that one is nowhere even close to my apartment.

Gelatinous · 2017-05-28 22:46:50

I think this can be closed now. I made the following changes:

I created two files, iwl3945.conf and mac80211.conf in the /etc/modprobe.d directory. Inside these files I have the following:

/etc/modprobe.d/iwl3945.conf

chris@bunsen-box:/etc/modprobe.d$ cat iwl3945.conf 
#attempting to fix frequent disconnects in WiFi
#information from here: https://tuxmal.blogspot.com/2014/09/wifi-intel-e-kernel-31x-ovvero-no-probe.html
#use Google Translate as site is not in English.

#ieee80211 phy0: wlan0: No probe response from AP 10:86:8c:5a:07:96 after 500ms, disconnecting.
#
#disable hardware scanning?
options iwl3945 disable_hw_scan=0

/etc/modprobe.d/mac80211.conf

chris@bunsen-box:/etc/modprobe.d$ cat mac80211.conf 
#attempting to fix frequent disconnects in WiFi
#information from here: https://tuxmal.blogspot.com/2014/09/wifi-intel-e-kernel-31x-ovvero-no-probe.html
#use Google Translate as site is not in English.

#ieee80211 phy0: wlan0: No probe response from AP 10:86:8c:5a:07:96 after 500ms, disconnecting.
#
#increase the number of retries and the time between retries before disconnecting.
options mac80211 max_probe_tries=20 probe_wait_ms=1000

I haven't had any disconnects or slowdowns since. I do still see some reauthing in dmesg and disconnecting for reason 6 (CLASS2_FRAME_FROM_NONAUTH_STA), whatever that means.

I'll keep monitoring it for now and open a new topic should it start failing again.

Thanks everyone,

Gelatinous (Chris)

Sector11 · 2017-05-29 00:56:16

We don't close threads that are 'positive' in nature, [Solved] or not.

Someone, someday might need this and your fix might not work. However glad you are happy.

#1 2017-05-03 15:52:05

[SOLVED]Wifi failure overnight

#2 2017-05-03 17:04:24

Re: [SOLVED]Wifi failure overnight

#3 2017-05-03 17:08:01

Re: [SOLVED]Wifi failure overnight

#4 2017-05-03 17:41:32

Re: [SOLVED]Wifi failure overnight

#5 2017-05-03 22:21:48

Re: [SOLVED]Wifi failure overnight

#6 2017-05-04 05:10:50

Re: [SOLVED]Wifi failure overnight

#7 2017-05-04 06:31:35

Re: [SOLVED]Wifi failure overnight

#8 2017-05-04 16:25:30

Re: [SOLVED]Wifi failure overnight

#9 2017-05-04 23:37:38

Re: [SOLVED]Wifi failure overnight

#10 2017-05-05 06:15:19

Re: [SOLVED]Wifi failure overnight

#11 2017-05-05 06:30:20

Re: [SOLVED]Wifi failure overnight

#12 2017-05-05 14:53:56

Re: [SOLVED]Wifi failure overnight

#13 2017-05-05 15:14:26

Re: [SOLVED]Wifi failure overnight

#14 2017-05-05 15:39:01

Re: [SOLVED]Wifi failure overnight

#15 2017-05-05 17:45:13

Re: [SOLVED]Wifi failure overnight

#16 2017-05-05 17:51:39

Re: [SOLVED]Wifi failure overnight

#17 2017-05-05 20:26:53

Re: [SOLVED]Wifi failure overnight

#18 2017-05-07 16:59:40

Re: [SOLVED]Wifi failure overnight

#19 2017-05-28 22:46:50

Re: [SOLVED]Wifi failure overnight

#20 2017-05-29 00:56:16

Re: [SOLVED]Wifi failure overnight

Board footer