After a fresh install of Karmic, I experienced fairly frequent random crashes which required hard resets. At first I thought the crashes might graphics driver related but was able to rule this out when the system crashed with no applications open at all.
I then noticed the prevalence of syslog entries such as:
{{{
Feb 25 21:18:13 truffles wpa_supplicant[1164]: CTRL-EVENT-SCAN-RESULTS
Feb 25 21:20:13 truffles wpa_supplicant[1164]: CTRL-EVENT-SCAN-RESULTS
}}}
just before crashes occurred. This was *before* finding this bug report.
After finding this bug report, I tried turning wireless networking off and using a network cable, and had a couple of days working without any network connection at all. In both cases I had no further crashes. Turning wireless networking back on coincides with crashes reoccurring.
I have experienced what I believe is the same problem on a MacBook Pro 2,1 with Karmic.
{{{
description: Wireless interface
product: AR5008 Wireless Network Adapter
vendor: Atheros Communications Inc.
physical id: 0
logical name: wlan0
version: 01
serial: 00:17:f2:eb:b5:1b
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration : broadcast=yes driver=ath9k ip=192.168.0.21 latency=0 multicast=yes wireless=IEEE 802.11abgn
resources: irq:17 memory: 98100000- 9810ffff
*-network
bus info: pci@0000:03:00.0
}}}
After a fresh install of Karmic, I experienced fairly frequent random crashes which required hard resets. At first I thought the crashes might graphics driver related but was able to rule this out when the system crashed with no applications open at all.
I then noticed the prevalence of syslog entries such as:
{{{ 1164]: CTRL-EVENT- SCAN-RESULTS 1164]: CTRL-EVENT- SCAN-RESULTS
Feb 25 21:18:13 truffles wpa_supplicant[
Feb 25 21:20:13 truffles wpa_supplicant[
}}}
just before crashes occurred. This was *before* finding this bug report.
After finding this bug report, I tried turning wireless networking off and using a network cable, and had a couple of days working without any network connection at all. In both cases I had no further crashes. Turning wireless networking back on coincides with crashes reoccurring.