[Bug 314961] Re: Kernel Panic with iwl3945 ucode
*** This bug is a duplicate of bug 336001 *** https://bugs.launchpad.net/bugs/336001 ** This bug has been marked a duplicate of bug 336001 NetworkManager causes system freeze, lock up, kernel panic -- Kernel Panic with iwl3945 ucode https://bugs.launchpad.net/bugs/314961 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314961] Re: Kernel Panic with iwl3945 ucode
Can you reproduce the lock-up described in bug #345710 "modprobe -r iwl3945 causes total system freeze" ? -- Kernel Panic with iwl3945 ucode https://bugs.launchpad.net/bugs/314961 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314961] Re: Kernel Panic with iwl3945 ucode
I am using the same card and have the same problems. In Intrepid, I switched from NetworkManager+WEP+kernel 2.6.27-11 to Wicd+WPA2Enterprise+kernel 2.6.27-13 (I read that it could solve the problem). Although I got far less kernel panics than with the first combination (I even thought it was solved), I still got kernel panics. Also, I recently switched from Intrepid to Fedora 10 to see if it could solve the issue (also seemed to be working for some people), and I got a kernel panic in 2.6.27.19-170.2.35.fc10.i686, NetworkManager 0.7.0.99+WPA2Enterprise (far less frequent than in the original scenario with Intrepid+NM+WEP too). The fact that I also got the kernel panic with Wicd makes me think that NetworkManager is not the problem, or at least, the only problem. -- Kernel Panic with iwl3945 ucode https://bugs.launchpad.net/bugs/314961 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314961] Re: Kernel Panic with iwl3945 ucode
Same here.laptop is completely useless on my works wpa/2 enterprise Wireless lan. Shortly after the connection with the wap...the system locks completely requiring a hard reboot / power cycle. System xbuntu 10 x64 / 2.6.27-11-generic #1 SMP Feb 17 14:27:22 Unknown kernel: [ 15.543769] iwl3945: Copyright(c) 2003-2008 Intel Corporation Feb 17 14:27:22 Unknown kernel: [ 15.591557] iwl3945 :10:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Feb 17 14:27:22 Unknown kernel: [ 15.591590] iwl3945: Detected Intel Wireless WiFi Link 3945ABG Feb 17 14:27:22 Unknown kernel: [ 15.672395] iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels Feb 17 14:27:22 Unknown kernel: [ 15.862931] iwl3945 :10:00.0: PCI INT A disabled Feb 17 14:27:34 Unknown kernel: [ 33.931525] iwl3945 :10:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Feb 17 14:27:34 Unknown kernel: [ 33.931951] firmware: requesting iwlwifi-3945-1.ucode Feb 17 14:27:34 Unknown kernel: [ 34.066183] Registered led device: iwl-phy0:radio Feb 17 14:27:34 Unknown kernel: [ 34.066620] Registered led device: iwl-phy0:assoc Feb 17 14:27:34 Unknown kernel: [ 34.066970] Registered led device: iwl-phy0:RX Feb 17 14:27:34 Unknown kernel: [ 34.067304] Registered led device: iwl-phy0:TX Feb 17 14:33:41 Unknown kernel: [ 15.931892] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks Feb 17 14:33:41 Unknown kernel: [ 15.931896] iwl3945: Copyright(c) 2003-2008 Intel Corporation Feb 17 14:33:41 Unknown kernel: [ 15.958509] iwl3945 :10:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Feb 17 14:33:41 Unknown kernel: [ 15.958551] iwl3945: Detected Intel Wireless WiFi Link 3945ABG Feb 17 14:33:41 Unknown kernel: [ 16.021157] iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels Feb 17 14:33:41 Unknown kernel: [ 16.438913] iwl3945 :10:00.0: PCI INT A disabled Feb 17 14:33:54 Unknown kernel: [ 34.078723] iwl3945 :10:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Feb 17 14:33:54 Unknown kernel: [ 34.079149] firmware: requesting iwlwifi-3945-1.ucode Feb 17 14:33:54 Unknown kernel: [ 34.222180] Registered led device: iwl-phy0:radio Feb 17 14:33:54 Unknown kernel: [ 34.04] Registered led device: iwl-phy0:assoc Feb 17 14:33:54 Unknown kernel: [ 34.58] Registered led device: iwl-phy0:RX Feb 17 14:33:54 Unknown kernel: [ 34.79] Registered led device: iwl-phy0:TX Feb 17 14:34:11 Unknown kernel: [ 51.344634] iwl3945: Radio Frequency Kill Switch is On: Feb 17 14:34:15 Unknown kernel: [ 54.578049] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC Feb 17 14:34:15 Unknown kernel: [ 54.627793] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC Feb 17 14:34:15 Unknown kernel: [ 54.687426] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC Feb 17 14:34:15 Unknown kernel: [ 54.850643] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC Feb 17 14:34:15 Unknown kernel: [ 54.867017] iwl3945 :10:00.0: PCI INT A disabled -- Kernel Panic with iwl3945 ucode https://bugs.launchpad.net/bugs/314961 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314961] Re: Kernel Panic with iwl3945 ucode
** Changed in: linux (Ubuntu) Importance: Undecided => High Status: Incomplete => Triaged -- Kernel Panic with iwl3945 ucode https://bugs.launchpad.net/bugs/314961 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314961] Re: Kernel Panic with iwl3945 ucode
The log above is for kernel panic before GDM. I encountered another scenario, able to log into Desktop but no wireless networking at all (even with modprobe iwl3945 again), with the log below is [ 31.297854] iwl3945 :05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 31.298050] iwl3945 :05:00.0: restoring config space at offset 0x1 (was 0x12, writing 0x16) [ 31.300896] firmware: requesting iwlwifi-3945-2.ucode [ 32.733311] iwl3945 :05:00.0: loaded firmware version 15.28.2.8 [ 34.737043] iwl3945 :05:00.0: Wait for START_ALIVE timeout after 2000ms. [ 34.737137] iwl3945 :05:00.0: PCI INT A disabled [ 34.751024] iwl3945 :05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 34.751211] iwl3945 :05:00.0: restoring config space at offset 0x1 (was 0x12, writing 0x16) [ 34.939266] NET: Registered protocol family 10 [ 36.757053] iwl3945 :05:00.0: Wait for START_ALIVE timeout after 2000ms. [ 36.757156] iwl3945 :05:00.0: PCI INT A disabled -- Kernel Panic with iwl3945 ucode https://bugs.launchpad.net/bugs/314961 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314961] Re: Kernel Panic with iwl3945 ucode
Jan 22 16:58:00 Ephemeral-Dream acpid: client connected from 5475[111:122] Jan 22 16:58:01 Ephemeral-Dream NetworkManager: starting... Jan 22 16:58:01 Ephemeral-Dream NetworkManager: Found radio killswitch /org/freedesktop/Hal/devices/iwl_wlan_switch Jan 22 16:58:01 Ephemeral-Dream NetworkManager: eth0: driver is 'e1000e'. Jan 22 16:58:01 Ephemeral-Dream NetworkManager: Found new Ethernet device 'eth0'. Jan 22 16:58:01 Ephemeral-Dream NetworkManager: (eth0): exported as /org/freedesktop/Hal/devices/net_00_0e_7b_55_01_98 Jan 22 16:58:01 Ephemeral-Dream NetworkManager: wlan0: driver is 'iwl3945'. Jan 22 16:58:01 Ephemeral-Dream NetworkManager: wlan0: driver supports SSID scans (scan_capa 0x01). Jan 22 16:58:01 Ephemeral-Dream NetworkManager: Found new 802.11 WiFi device 'wlan0'. Jan 22 16:58:01 Ephemeral-Dream NetworkManager: (wlan0): exported as /org/freedesktop/Hal/devices/net_00_13_02_cb_cc_07 Jan 22 16:58:01 Ephemeral-Dream NetworkManager: Trying to start the supplicant... Jan 22 16:58:01 Ephemeral-Dream NetworkManager: Trying to start the system settings daemon... Jan 22 16:58:01 Ephemeral-Dream nm-system-settings:SCPlugin-Ifupdown: init! Jan 22 16:58:01 Ephemeral-Dream nm-system-settings:SCPlugin-Ifupdown: update_system_hostname Jan 22 16:58:01 Ephemeral-Dream nm-system-settings:SCPluginIfupdown: management mode: unmanaged Jan 22 16:58:01 Ephemeral-Dream nm-system-settings:SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/net_00_0e_7b_55_01_98, iface: eth0): not well known Jan 22 16:58:01 Ephemeral-Dream nm-system-settings:SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/net_00_13_02_cb_cc_07, iface: wlan0): not well known Jan 22 16:58:01 Ephemeral-Dream nm-system-settings:SCPlugin-Ifupdown: end _init. Jan 22 16:58:01 Ephemeral-Dream nm-system-settings: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. Jan 22 16:58:01 Ephemeral-Dream nm-system-settings: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Jan 22 16:58:01 Ephemeral-Dream nm-system-settings:SCPlugin-Ifupdown: (141525280) ... get_connections. Jan 22 16:58:01 Ephemeral-Dream nm-system-settings:SCPlugin-Ifupdown: (141525280) ... get_connections (managed=false): return empty list. Jan 22 16:58:01 Ephemeral-Dream NetworkManager: (wlan0): supplicant manager is now in state 1 (from 0). Jan 22 16:58:01 Ephemeral-Dream nm-system-settings:Ifupdown: get unmanaged devices count: 0 Jan 22 16:58:02 Ephemeral-Dream acpid: client connected from 5580[0:0] Jan 22 16:58:04 Ephemeral-Dream acpid: client connected from 5580[0:0] Jan 22 16:58:05 Ephemeral-Dream NetworkManager: (eth0): device state change: 1 -> 2 Jan 22 16:58:05 Ephemeral-Dream NetworkManager: (eth0): bringing up device. Jan 22 16:58:05 Ephemeral-Dream NetworkManager: (eth0): preparing device. Jan 22 16:58:05 Ephemeral-Dream NetworkManager: (eth0): deactivating device (reason: 2). Jan 22 16:58:05 Ephemeral-Dream NetworkManager: Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Jan 22 16:58:05 Ephemeral-Dream NetworkManager: Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Jan 22 16:58:05 Ephemeral-Dream nm-system-settings: Adding default connection 'Auto eth0' for /org/freedesktop/Hal/devices/net_00_0e_7b_55_01_98 Jan 22 16:58:05 Ephemeral-Dream NetworkManager: (wlan0): device state change: 1 -> 2 Jan 22 16:58:05 Ephemeral-Dream NetworkManager: (wlan0): bringing up device. Jan 22 16:58:05 Ephemeral-Dream kernel: [ 28.965330] iwl3945 :05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 Jan 22 16:58:05 Ephemeral-Dream kernel: [ 28.965527] iwl3945 :05:00.0: restoring config space at offset 0x1 (was 0x12, writing 0x16) Jan 22 16:58:05 Ephemeral-Dream kernel: [ 28.968406] firmware: requesting iwlwifi-3945-2.ucode Jan 22 16:58:05 Ephemeral-Dream ntpd[5621]: ntpd 4.2@1.1520-o Tue Jan 6 15:54:48 UTC 2009 (1) Jan 22 16:58:05 Ephemeral-Dream kernel: [ 29.446859] iwl3945 :05:00.0: loaded firmware version 15.28.2.8 Jan 22 16:58:05 Ephemeral-Dream ntpd[5624]: precision = 11.000 usec Jan 22 16:58:08 Ephemeral-Dream kernel: [ 32.753639] iwl3945 :05:00.0: Wait for START_ALIVE timeout after 2000ms. Jan 22 16:58:08 Ephemeral-Dream kernel: [ 32.753727] iwl3945 :05:00.0: PCI INT A disabled Jan 22 16:58:08 Ephemeral-Dream kernel: [ 32.754098] NET: Registered protocol family 10 Jan 22 16:58:08 Ephemeral-Dream kernel: [ 32.755360] lo: Disabled Privacy Extensions Jan 22 16:58:08 Ephemeral-Dream kernel: [ 32.756678] ADDRCONF(NETDEV_UP): eth0: link is not ready Jan 22 16:58:09 Ephemeral-Dream ntpd[5624]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Jan 22 16:58:09 Ephemeral-Dream ntp
[Bug 314961] Re: Kernel Panic with iwl3945 ucode
Hi, I think the problem is lying with the Network-Manager and not the kernel itself. I tried both LiveCDs (Intrepid and Jaunty), the live session boot fine because Network-Manager (NM) has no network to connect to yet (fresh) in contrast to my NM which contains my home/school's network configurations. I will not have kernel panic when I remove all the configurations or have no network to connect with. I took a step further to do some more testing with NM behaviour (both with orignal intrepid and latest compat-wireless stack with iwlwifi-3945-2.ucode) * First boot to a connectable network, NM connected to a network before GDM -> panic * Second boot (after forced restart) to a connectable network, NM only connected to a network after GDM -> NO panic * Boot to a non-connectable network, NM can't connect -> NO panic Lots of If-up/down, unmanaged device in the daemon log though... I will try to grab a proper log, cos the problem occur like 1 per day per Network access point (due to 2nd boot scenario above). Is there any way to debug this network manager problem? Many thanks for your kind help! Regards, -- Kernel Panic with iwl3945 ucode https://bugs.launchpad.net/bugs/314961 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314961] Re: Kernel Panic with iwl3945 ucode
Hi idyllic, Care to do one more test. Can you test the latest pre-release of Jaunty 9.04 (currently Alpha3). You should be able to test via a LiveCD. Please let us know your results. http://cdimage.ubuntu.com/releases/jaunty/ . Thanks. -- Kernel Panic with iwl3945 ucode https://bugs.launchpad.net/bugs/314961 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314961] Re: Kernel Panic with iwl3945 ucode
Hi, I booted with "-quite no splash" and everything seems OK till the GDM login. When the panic occurred, the screen is blank as opposed to normal GDM greeting. Since it is blank screen, I think it is of no use to take a screenshot. The only indication is the BLINKING/FLICKERING of CAPSLOCK button. REISUB doesn't help me to reboot, only a hard reset using the power button. I have tried the linux-backports-modules-intrepid earlier, but it couldn't solve the problem. Thanks -- Kernel Panic with iwl3945 ucode https://bugs.launchpad.net/bugs/314961 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314961] Re: Kernel Panic with iwl3945 ucode
Hi idyllic, Would you be able to capture the kernel panic you are seeing and attach it to this report? Even if you have to take a digital photo of your screen that would be fine. You may also want to try installing the linux-backports-modules-intrepid package to see if it helps. It contains an updated compat-wireless stack. Please let us know your results. Thanks. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- Kernel Panic with iwl3945 ucode https://bugs.launchpad.net/bugs/314961 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314961] Re: Kernel Panic with iwl3945 ucode
** Changed in: linux (Ubuntu) Sourcepackagename: None => linux -- Kernel Panic with iwl3945 ucode https://bugs.launchpad.net/bugs/314961 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314961] Re: Kernel Panic with iwl3945 ucode
** Attachment added: "lspci -vvnn" http://launchpadlibrarian.net/21000326/lspci_vvnn.log -- Kernel Panic with iwl3945 ucode https://bugs.launchpad.net/bugs/314961 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
