Comment 72 for bug 263059

Revision history for this message
DSHR (s-heuer) wrote :

I blacklisted iwl3945 and added a modprobe iwl3945 in /etc/rc.local
I had no freezes since then and this is my dmesg output:

[ 681.433407] Bluetooth: RFCOMM TTY layer initialized
[ 681.433420] Bluetooth: RFCOMM ver 1.10
[ 681.452827] Bridge firewalling registered
[ 681.454271] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
[ 681.516090] Bluetooth: SCO (Voice Link) ver 0.6
[ 681.516101] Bluetooth: SCO socket layer initialized
[ 685.223193] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driv
er for Linux, 1.2.26ks
[ 685.223201] iwl3945: Copyright(c) 2003-2008 Intel Corporation
[ 685.224860] iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 685.224883] iwl3945 0000:03:00.0: setting latency timer to 64
[ 685.224914] iwl3945: Detected Intel Wireless WiFi Link 3945ABG
[ 685.286373] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
[ 685.287998] phy0: Selected rate control algorithm 'iwl-3945-rs'
[ 685.378425] iwl3945 0000:03:00.0: PCI INT A disabled
[ 685.809758] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 686.088367] [drm] Initialized drm 1.1.0 20060810
[ 686.133056] pci 0000:00:02.0: power state changed by ACPI to D0
[ 686.133081] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 686.133091] pci 0000:00:02.0: setting latency timer to 64
[ 686.138910] [drm] Initialized i915 1.6.0 20060119 on minor 0
[ 689.392622] iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 689.392789] iwl3945 0000:03:00.0: restoring config space at offset 0x1 (was 0x100102, writing 0x100106)
[ 689.396877] firmware: requesting iwlwifi-3945-1.ucode
[ 689.542012] Registered led device: iwl-phy0:radio
[ 689.542104] Registered led device: iwl-phy0:assoc
[ 689.542140] Registered led device: iwl-phy0:RX
[ 689.542176] Registered led device: iwl-phy0:TX
[ 689.549639] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 689.685114] NET: Registered protocol family 17
[ 763.680856] CPU0 attaching NULL sched-domain.

Not a solution - but a workaround for me ...