Red Hat Bugzilla – Bug 205958
my machine freeze from time to time
Last modified: 2007-11-30 17:11:42 EST
Description of problem:
from time to time our server is stuck for about an hour
Version-Release number of selected component (if applicable):
fedora core 5
Steps to Reproduce:
1. launch a "big" program like matlab
2. wait a bit
3. the machine is stuck for about an hour and the date of the machine has lost
afer about one hour it came back to life
here is the message on console and in /var/log/messages
Sep 8 22:15:59 helios kernel: BUG: write-lock lockup on CPU#6, MATLAB/23423,
c073da00 (Not tainted)
Sep 8 22:15:59 helios kernel: <c04ea9f6> _raw_write_lock+0xe2/0x100
Sep 8 22:15:59 helios kernel: <c042e343> __dequeue_signal+0x14a/0x155
Sep 8 22:15:59 helios kernel: <c042fc5b> get_signal_to_deliver+0x3a9/0x3d1
Sep 8 22:15:59 helios kernel: <c041f2e7> default_wake_function+0x0/0xc
Sep 8 22:15:59 helios kernel: <c0403ece> work_notifysig+0x13/0x19
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
the problem is solved