Thanks for testing and confirming against the latest Jaunty released.
Please run the following command from a Terminal
(Applications->Accessories->Terminal).  It will automatically gather and
attach updated debug information to this report.

apport-collect -p linux-image-2.6.28-11-generic 338047

If the issue remains in Jaunty, if you could also test the latest
upstream kernel available that would be great.  It will allow additional
upstream developers to examine this issue.  Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds .  Once you've tested the
upstream kernel, please remove the 'needs-upstream-testing' tag.  This
can be done by clicking on the yellow pencil icon next to the tag
located at the bottom of the bug description and deleting the 'needs-
upstream-testing' text.  Please let us know your results.

Thanks in advance.

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
soft lockup - CPU#0 stuck for 11s! [clurgmgrd:4587]
https://bugs.launchpad.net/bugs/338047
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is a direct subscriber.

Status in “linux” package in Ubuntu: Incomplete
Status in “redhat-cluster” package in Ubuntu: Triaged

Bug description:
Hardware:
System - 2 HP servers
Ubuntu version - Hardy 8.04.2

Step to reproduce:
1. Configure the hostname
2. Configure the static IP address
3. Install redhat-cluster-suite software
4. Create the cluster.conf file[1].

5. Reboot both server. When the server boot up, the error message will appear 
repeatedly even after reboot:
soft lockup - CPU#0 stuck for 11s! [clurgmgrd:4587]
soft lockup - CPU#0 stuck for 11s! [clurgmgrd:4587]
soft lockup - CPU#0 stuck for 11s! [clurgmgrd:4587]
soft lockup - CPU#0 stuck for 11s! [clurgmgrd:4587]
soft lockup - CPU#0 stuck for 11s! [clurgmgrd:4587]

*see soft_lockup.png


[1] Here is the cluster.conf file that I created.
Here is the cluster.conf file:
<?xml version="1.0" ?>
<cluster alias="ubuntu" config_version="2" name="ubuntu">
        <fence_daemon post_fail_delay="0" post_join_delay="3"/>
        <clusternodes>
                <clusternode name="node0.ubuntu.local" nodeid="1" votes="1">
                        <fence>
                                <method name="1">
                                        <device name="m_fencing" 
nodename="node0.ubuntu.local"/>
                                </method>
                        </fence>
                </clusternode>
                <clusternode name="node1.ubuntu.local" nodeid="2" votes="1">
                        <fence>
                                <method name="1">
                                        <device name="m_fencing" 
nodename="node1.ubuntu.local"/>
                                </method>
                        </fence>
                </clusternode>
        </clusternodes>
        <cman expected_votes="1" two_node="1"/>
        <fencedevices>
                <fencedevice agent="fence_manual" name="m_fencing"/>
        </fencedevices>
        <rm>
                <failoverdomains/>
                <resources/>
        </rm>
</cluster>

_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help   : https://help.launchpad.net/ListHelp

Reply via email to