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
