Bug 5753 - Kernel hangs on boot after "Started LSB: Network Monitoring daemon [ OK ]"
Summary: Kernel hangs on boot after "Started LSB: Network Monitoring daemon [ OK ]"
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-05 08:29 CEST by Andrew
Modified: 2013-02-26 08:35 CET (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Andrew 2012-05-05 08:29:48 CEST
Description of problem:

When booting Mageia, kernel hangs after displaying "Started LSB: Network Monitoring daemon        [  OK  ]"

Problem began occuring after reboot. Actions performed during last successfully boot were changing control of wireless network from drakx-net to NetworkManager (was bug testing for Empathy as some of its functions prefer NetworkManager) and changing hostname through drakx-net. Rebooted system, kernel hangs.

Version-Release number of selected component (if applicable):

kernel-desktop-3.3.4-1.mga2

How reproducible:

Automatically during boot. Please advise...

Steps to Reproduce (1st occurance):
1. Right-click on NetApplet
2. Click "Configure Networks" (? Don't remember exact wording)
3. Select "wlan:0"
4. Enable / disable "Allow interface to be controlled by Network Manager"
5. Changed hostname
6. Logout - Screen turned black with no response
7. Reboot

Steps to Reproduce (Subsequent occurance):
1. Boot system
Andrew 2012-05-07 06:10:48 CEST

Summary: Kernel hangs on boot => Kernel hangs on boot after "Started LSB: Network Monitoring daemon [ OK ]"

Comment 1 Andrew 2012-05-07 06:19:11 CEST
I let the computer sit overnight, just in case it was waiting on timeouts - still no success.

Failsafe preset in GRUB is able to get me to a terminal screen. Is there anything I can do from there that will help? Still awaiting advice.
Comment 2 Manuel Hiebel 2012-05-08 19:46:21 CEST
can you have more info with removing 'splash quiet' in the grub ?
Comment 3 Andrew 2012-05-12 04:45:52 CEST
Already did that. That's how I was able to tell what point it hangs. Any advice or should I just reinstall?
Comment 4 Andrew 2012-05-13 23:08:55 CEST
I've been unable to perform ANY testing on this machine for over a week from the time I reported this as I cannot boot cauldron beyond the point described.

It's been over a week since I reported this with no advice or progress and I need to be able to resume testing. I will give up on this bug and reinstall cauldron if no further advice is received by the next day as I cannot afford to have my system unusable any longer.
Comment 5 Manuel Hiebel 2012-05-14 17:09:06 CEST
yes do that...
Comment 6 Ken Johnson 2012-05-25 12:09:20 CEST
Will there be any further work on this?  I had to reinstall 1.  My Aspire 7560-sb600 displays LSB errors several time during boot and finally hangs waiting for Plymouth to exit.

CC: (none) => johnsonken1

Comment 7 Marja Van Waes 2012-05-26 13:07:36 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 8 Ken Johnson 2012-05-27 01:29:34 CEST
It is.  LSB errors occur several times during boot and system finally hangs waiting for Plymouth to exit.
Sander Lepik 2012-05-27 09:34:46 CEST

Keywords: NEEDINFO => (none)
CC: (none) => sander.lepik

Hans Micheelsen 2013-02-05 15:33:05 CET

CC: (none) => micheelsen

Comment 9 Sander Lepik 2013-02-13 08:54:36 CET
Andrew, is this bug still present in cauldron?
Sander Lepik 2013-02-13 08:55:07 CET

Component: Release (media or process) => RPM Packages

Comment 10 Andrew 2013-02-26 08:31:13 CET
No. :-) Bug seems to be fixed. Unable to reproduce.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 11 Andrew 2013-02-26 08:35:28 CET
@Ken Johnson: Is your issue related NetApplet / Drakx-Net & NetworkManager (which was the original cause of this bug)? If not, please file your report as a new bug instead of adding your unrelated issue to this one.

Closing as Fixed.

Note You need to log in before you can comment on or make changes to this bug.