Help needed: what is making the wireless card on my Raspberry Pi crash

Here’s the syslog from my Raspberry Pi this morning:


Jan 8 06:25:15 raspberrypi /USR/SBIN/CRON[10042]: (CRON) info (No MTA installed, discarding output)
Jan 8 06:25:30 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 8 06:25:30 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 8 06:25:31 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 373 seconds.
Jan 8 06:31:43 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 8 06:31:43 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 8 06:31:43 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 405 seconds.
Jan 8 06:38:28 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 8 06:38:28 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 8 06:38:28 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 376 seconds.
Jan 8 06:44:44 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 8 06:44:44 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 8 06:44:44 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 415 seconds.
Jan 8 06:49:58 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c IEEE 802.11: authentication OK (open system)
Jan 8 06:49:58 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c MLME: MLME-AUTHENTICATE.indication(7c:61:93:ff:98:0c, OPEN_SYSTEM)
Jan 8 06:49:58 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c MLME: MLME-DELETEKEYS.request(7c:61:93:ff:98:0c)
Jan 8 06:49:58 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c IEEE 802.11: authenticated
Jan 8 06:49:58 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c IEEE 802.11: association OK (aid 1)
Jan 8 06:49:58 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c IEEE 802.11: associated (aid 1)
Jan 8 06:49:58 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c MLME: MLME-ASSOCIATE.indication(7c:61:93:ff:98:0c)
Jan 8 06:49:58 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c MLME: MLME-DELETEKEYS.request(7c:61:93:ff:98:0c)
Jan 8 06:51:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 06:51:39 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 8 06:51:39 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 8 06:51:40 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 373 seconds.
Jan 8 06:52:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 06:53:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 06:54:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 06:55:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 06:56:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 06:57:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 06:57:53 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 8 06:57:53 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 8 06:57:54 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 350 seconds.
Jan 8 06:58:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 06:59:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:00:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:01:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:02:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:03:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:03:44 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 8 07:03:44 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 8 07:03:44 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 419 seconds.
Jan 8 07:04:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:05:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:06:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:07:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:08:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:09:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:10:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:10:43 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 8 07:10:43 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 8 07:10:43 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 368 seconds.
Jan 8 07:11:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:12:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:13:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:14:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:15:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:16:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:16:51 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 8 07:16:51 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 8 07:16:52 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 385 seconds.
Jan 8 07:17:01 raspberrypi /USR/SBIN/CRON[10417]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 8 07:17:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:18:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:19:11 raspberrypi NetworkManager[2774]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 8 07:18:04 raspberrypi kernel: imklog 5.8.11, log source = /proc/kmsg started.

(The last line is the first output of the rebooted machine – when, at about 7.19am I got up and found it wasn’t working – not sure why the clock goes backwards but it does.)

And here is yesterday’s log at the same time…


Jan 7 06:25:14 raspberrypi /USR/SBIN/CRON[8350]: (CRON) info (No MTA installed, discarding output)
Jan 7 06:26:05 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 7 06:26:05 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 7 06:26:07 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 399 seconds.
Jan 7 06:32:46 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 7 06:32:46 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 7 06:32:47 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 361 seconds.
Jan 7 06:38:48 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 7 06:38:48 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 7 06:38:49 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 420 seconds.
Jan 7 06:41:27 raspberrypi kernel: [63555.391671] usb 1-1.3.1: reset high-speed USB device number 6 using dwc_otg
Jan 7 06:45:50 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 7 06:45:50 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 7 06:45:50 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 354 seconds.
Jan 7 06:49:59 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c IEEE 802.11: authentication OK (open system)
Jan 7 06:49:59 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c MLME: MLME-AUTHENTICATE.indication(7c:61:93:ff:98:0c, OPEN_SYSTEM)
Jan 7 06:49:59 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c MLME: MLME-DELETEKEYS.request(7c:61:93:ff:98:0c)
Jan 7 06:49:59 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c IEEE 802.11: authenticated
Jan 7 06:49:59 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c IEEE 802.11: association OK (aid 1)
Jan 7 06:49:59 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c IEEE 802.11: associated (aid 1)
Jan 7 06:49:59 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c MLME: MLME-ASSOCIATE.indication(7c:61:93:ff:98:0c)
Jan 7 06:49:59 raspberrypi hostapd: wlan0: STA 7c:61:93:ff:98:0c MLME: MLME-DELETEKEYS.request(7c:61:93:ff:98:0c)
Jan 7 06:51:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 06:51:45 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 7 06:51:45 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 7 06:51:45 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 359 seconds.
Jan 7 06:52:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 06:53:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 06:54:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 06:55:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 06:56:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 06:57:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 06:57:45 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 7 06:57:45 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 7 06:57:45 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 369 seconds.
Jan 7 06:58:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 06:59:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:00:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:01:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:02:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:03:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:03:54 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 7 07:03:54 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 7 07:03:54 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 366 seconds.
Jan 7 07:04:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:05:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:06:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:07:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:08:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:09:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:10:00 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 7 07:10:00 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 7 07:10:00 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 397 seconds.
Jan 7 07:10:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:11:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:12:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:13:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:14:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:15:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:16:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:16:37 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 7 07:16:37 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 7 07:16:38 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 435 seconds.
Jan 7 07:17:01 raspberrypi /USR/SBIN/CRON[8725]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 7 07:17:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:18:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:19:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:20:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:21:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:22:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:23:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Jan 7 07:23:53 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 7 07:23:53 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 7 07:23:54 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 389 seconds.
Jan 7 07:24:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:25:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:26:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:27:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:28:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:29:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:30:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:30:23 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 7 07:30:23 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 7 07:30:23 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 382 seconds.
Jan 7 07:31:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:32:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:33:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:34:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:35:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:36:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:36:45 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 7 07:36:45 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 7 07:36:46 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 375 seconds.
Jan 7 07:37:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:38:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:39:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:40:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:41:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:42:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:43:02 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 7 07:43:02 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 7 07:43:02 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 439 seconds.
Jan 7 07:43:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:44:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:45:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:46:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:47:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:48:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:49:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:50:21 raspberrypi dhclient: DHCPREQUEST on br0 to 192.168.62.1 port 67
Jan 7 07:50:21 raspberrypi dhclient: DHCPACK from 192.168.62.1
Jan 7 07:50:22 raspberrypi dhclient: bound to 192.168.62.104 -- renewal in 418 seconds.
Jan 7 07:50:23 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:51:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:52:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:53:22 raspberrypi NetworkManager[2763]: <warn> Could not get scan request result: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jan 7 07:17:55 raspberrypi kernel: imklog 5.8.11, log source = /proc/kmsg started.

As you can see, I didn’t reboot it yesterday until a bit later (I was puzzled as to why I could still ping the bridge but not log in to the box – but this morning I had seen it al before.)

As the logs up to time 6.49am show no sign of a problem I am guessing this is a cron related issue.

But I can see nothing in the various cron.daily scripts that should hit the wireless card.

Any ideas as to what this is about?