Hardy 64bit on DELL Server random blackouts / hangs

Bug #607167 reported by Daniel Paufler
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

We have 3 database-servers running hardy on DELL PowerEdge R710.

After upgrading from 32bit to 64bit, we experience blackouts / hangs about once a day for 2-5 minutes. With 32bit hardy, we never had any problems. Our logs dont show anything suspicious. currently running kernel is 2.6.24-28-server #1 SMP x86_64 GNU/Linux

For a good explaination what happens see forum threads:
http://ubuntuforums.org/showthread.php?t=1343083
http://ubuntuforums.org/showthread.php?t=1403658

Revision history for this message
Daniel Paufler (d-paufler-ergomedia) wrote :
Revision history for this message
Daniel Paufler (d-paufler-ergomedia) wrote :
Revision history for this message
Daniel Paufler (d-paufler-ergomedia) wrote :
tags: added: kj-triage
Revision history for this message
Juergen Neumann (j-neumann) wrote :

URGENT! We updated all our Hardy 64 bit servers to recent linux-image 2.6.24.-28.71. The problem still persist. All Hardy 64 bit servers on DELL hardware have a blackout once or twice a day. We wrote a monitoring script to check it. Ping and ssh will still work, but mysql and samba will blackout for several minutes.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Daniel Paufler, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 607167

Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

tags: added: needs-upstream-testing
removed: kernel linux
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.