Description of problem: With latest update of Fedora 12, the system has become unstable. NetworkManager is altogether disabled and the system freezes. I had to do hard reboot after few seconds. The NetworkManager package is NetworkManager-1:0.7.996-6.git20091021.fc12 The kernel is 2.6.31.9-174.fc12.i686.PAE. The crash manager notifies of the kernel crash and dmesg shows an error: "[drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own" Version-Release number of selected component (if applicable): NetworkManager-1:0.7.996-6.git20091021.fc12 Kernel 2.6.31.9-174.fc12.i686.PAE How reproducible: No specific procedure, just restart the system after an update from 03 Jan 2010. Actual results: NetworkManager is disabled and system freezes. Expected results: NetworkManager should be enabled and system should not freeze. Additional info:
The system freeze appears to be DRM/graphics related and not NetworkManager related actually. When you say "network manager is disabled", what specifically do you mean? Is the 'Networking enabled' checkbox in the nm-applet right-click menu unchecked? Or something else? If you can, can you grab the kernel log messages with a command like this typed into a terminal: dmesg > /tmp/kernel.log and then attach that file to this bug report?
(In reply to comment #1) > The system freeze appears to be DRM/graphics related and not NetworkManager > related actually. > Yep, sorry for that. I stumbled across two problem at the same time, the Networkmanager issue and the drm error. Someone has already logged a bug related to drm in bugzilla. > When you say "network manager is disabled", what specifically do you mean? Is > the 'Networking enabled' checkbox in the nm-applet right-click menu unchecked? > Or something else? > The "Networking enabled" checkbox gets automatically disabled after update. And there is no notification that the checkbox has been disabled. > If you can, can you grab the kernel log messages with a command like this typed > into a terminal: > > dmesg > /tmp/kernel.log > > and then attach that file to this bug report? As the bug is already in the database, I will avoid duplicating it here. Thanks and regards, ~Ajit
*** This bug has been marked as a duplicate of bug 589108 ***