On Tue, Jul 16, 2013 at 11:27 AM, Stanislaw Gruszka <sgruszka@xxxxxxxxxx> wrote: >> I seem only to be able to trigger it with disable_hw_scan=0, I need >> further testing with disable_hw_scan=1 (I use disable_hw_scan=0 >> because it prevents me from getting disconnected from eduroam Cisco >> APs -- haven't tested disable_hw_scan=0 since the VOIP-friendly SW >> scanning patch, however). >> >> Do you want the log anyway? (modprobe iwl3945 debug=0x47ffffff >> disable_hw_scan=0 and runtime PCI powersave also enabled -- I don't >> know if it matters). > > As this is not causing troubles with default disable_hw_scan option, > I'll post that patch. My mistake, I can trigger error conditions _independently_ of disable_hw_scan option being enabled or disabled, as long as powersave is enabled. I'll send you a private email with the logs. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html