I noticed that Pid: x, comm: indexer Not tainted 2.6.27-y-server appeared in
all my log files. indexer is part of mnogosearch which I use to search through
pdf files. I had built version 3.3.7 on a 2.6.27-9-generic kernel a while ago.
I downloaded the new version of mnogosearch, rebuilt it and
@Andy after almost a week of no-crashes, my computer froze last night.
Attached is the extract from kernel log. As you asked, I looked for any
'Panic' lines before the crash but there aren't any.. even for the
earlier reported crashes.
In this crash, the first bug reported is BUG: unable to
We believe that the original bug here is definatly fixed by the change
to the lockless pagecache carried in the -14.18 kernel which is now in
Intrepid -updates. Closing this one Fix Released for Intrepid. If you
do not have the original soft lockup style error then please file a
new bug.
**
** Changed in: linux (Ubuntu Intrepid)
Importance: Undecided = High
--
RAID array causing BUG: soft lockup errors/system freeze
https://bugs.launchpad.net/bugs/312163
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@tom -- that appears to be a different symptom. Cirtainly from the one
originally reported on this bug, and the one the patch to which I was
referring was supposed to fix. Lets get a separate bug filed for that
one please. We can dup it to this one should it prove later to be the
same.
--
** Also affects: linux (Ubuntu Intrepid)
Importance: Undecided
Status: New
--
RAID array causing BUG: soft lockup errors/system freeze
https://bugs.launchpad.net/bugs/312163
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Now that karmic is open the primary task applies there. The fix
relating to this issue is already there so closing Fix Released. We
continue to monitor Intrepid expecting that the fix is there, in -14 and
later.
** Changed in: linux (Ubuntu Intrepid)
Status: New = Incomplete
** Changed
As far as I can tell this issue is fixed in Jaunty. I have been really
hammering the system for several weeks and have not seen the original
problem.
I believe some of issues posted here lately are not related to the
original bug. The stack traces look different.
--
RAID array causing BUG:
Is there anything I can do to help solve this problem?
--
RAID array causing BUG: soft lockup errors/system freeze
https://bugs.launchpad.net/bugs/312163
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
@andy: Not so much luck on my side.
System was running for less than a day before it crashed again. I've attached a
new log file. Looks very similar.
** Attachment added: xfs_oops_2.txt
http://launchpadlibrarian.net/26240729/xfs_oops_2.txt
--
RAID array causing BUG: soft lockup
I've been having similar problems for quite some time
(http://oss.sgi.com/archives/xfs/2009-03/msg00062.html). Lockups affecting
random parts of the system. Most of the time, it wouldn't even reboot and I had
to pull the plug. I'm running intrepid 2.6.27-11-server x86_64 on an Intel
Core2 Duo
@Deepak -- sorry missread your version number, jaunty has no -proposed
and the main kernels have the fix to this bug. Looking at your log
fragment it looks like a different trace. Could you file that one as a
new bug. When you do could you check back before the first occurance of
the bug in
@tom -- we would expect that to be gone with -14 kernels, if you could
report back if your testing is successful that would be helpful.
--
RAID array causing BUG: soft lockup errors/system freeze
https://bugs.launchpad.net/bugs/312163
You received this bug notification because you are a member
We have deployed 2.6.27-14 on the KVM host. As a caveat we had to add
rootdelay=200 to the kernel options as the FC attached storage didn't
configure quickly enough for the root fs to be found.
This machine is hosting 14 VMs so it's I/O load can be very heavy at
times.
My potentially related
It is possible that I am facing this issue too. I am running Jaunty
(kernel 2.6.28-11-generic). I have a mdadm based raid too.
Here's the dump from /var/log/kern.log that I also posted in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/367389/comments/2
@Deepak -- could you try the kernel in proposed as the -11 kernels do
not contain the fix, but the -14 should. Please report back here.
--
RAID array causing BUG: soft lockup errors/system freeze
https://bugs.launchpad.net/bugs/312163
You received this bug notification because you are a member
@Andy: I added the jaunty-proposed repo (as in
https://wiki.ubuntu.com/Testing/EnableProposed) but didn't get any new
kernel. I tried both with and without pinning the repos as suggested in
'selective upgrading from -proposed' but still no new kernel.
Meanwhile, I am attaching some more kernel
I'm testing linux-image-2.6.27-14-server on amd64 KVM this weekend.
/etc/apt/sources.list contains:
deb http://archive.ubuntu.com/ubuntu/ intrepid-proposed main
/etc/apt/preferences contains:
Package: *
Pin: release a=intrepid-security
Pin-Priority: 990
Package: *
Pin: release
It seems that the upstream fix mentioned above has made it into the
Intrepid kernel and is currently in the kernels in Intrepid -proposed.
If those who are affected by this could test the kernels from -proposed
and report back that would be helpful. Please see
Are the following bugs about the same issue?
They all are about soft lockup using xfs on Intrepid:
268215
289158
312163
348218
Thanks.
--
RAID array causing BUG: soft lockup errors/system freeze
https://bugs.launchpad.net/bugs/312163
You received this bug notification because you are a member
I spent the last few days testing on Jaunty and it seems to be fixed
there. Kernel is 2.6.28-11.42 x86_64.
I will have more confidence after a few weeks of testing but I think it
looks good so far.
--
RAID array causing BUG: soft lockup errors/system freeze
Chris, it would be great if you could let us know your results if you're
either able to test the patch or a newer 2.6.28 based Jaunty kernel.
Thanks in advance.
--
RAID array causing BUG: soft lockup errors/system freeze
https://bugs.launchpad.net/bugs/312163
You received this bug notification
** Package changed: mdadm (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Tags added: regression-release
--
RAID array causing BUG: soft lockup errors/system freeze
I've downgraded to the 2.6.24-16-generic kernel (hardy) and the problem
seems to have been resolved. This issue seems to be an issue with the
later kernels.
--
RAID array causing BUG: soft lockup errors/system freeze
https://bugs.launchpad.net/bugs/312163
You received this bug notification
The patch that I mentioned above is in the 2.6.28-11 kernel used in
Jaunty so it might work also. I'm not sure when I will get a chance to
test it though.
--
RAID array causing BUG: soft lockup errors/system freeze
https://bugs.launchpad.net/bugs/312163
You received this bug notification
I've been having the same problem today after adding 2x1TB drives to my Ubuntu
x64 system - configured as stripe using mdadm.
Random lockups when copying to and reading from raid. Occurs with xfs, reiser
and ext3.
Will post logs next week.
--
RAID array causing BUG: soft lockup errors/system
We're still seeing occasional machine check events but nothing logged in
/var/log/mcelog
Feb 25 00:10:46 dev kernel: [110217.794081] Machine check events logged
Feb 25 01:13:16 dev kernel: [113958.998576] Machine check events logged
and no further soft lockups.
--
RAID array causing BUG: soft
I have been running for over a month now on the older Hardy kernel
(2.6.24-23-generic x86_64) and have not seen this issue at all. So it
appears it's almost definitely something broken in the newer kernels.
At this point it's unclear if it is an Ubuntu or Linux kernel problem.
With that said, I
Hi,
I'm seeing a similar problem on my system with frequent soft lockup
messages and machine check events logged.
Distributor ID: Ubuntu
Description:Ubuntu 8.10
Release:8.10
Codename: intrepid
Errors with linux-image-2.6.27-11-server (64-bit). It's not clear if
there are
I've been seeing the same problem from doing an iozone test on an mdraid
5 array. This keeps appearing in my dmesg:
[553927.303743] BUG: soft lockup - CPU#3 stuck for 61s! [iozone:24558]
[553927.303755] Modules linked in: wmi video output sbs sbshc pci_slot battery
ac bonding iptable_filter
I'm still testing but I have been using the kernel from 8.04 Hardy
2.6.24-23-generic and problem has not appeared for several days now.
I'm still running Intrepid but with the older kernel.
If this is true then this bug must have been introduced somewhere
between 2.6.24 and 2.6.27 (and as I
I built the current Jaunty kernel (2.6.28-4-generic) and tried that but
it has the same problem.
It seems the error happens much more often when using XFS but I'm not
sure if it's related to XFS or not. I have found that doing very long
running large SqLite operations is the best way to recreate
I've been seeing this same problem.
I have two arrays one raid0 other raid5 both with xfs on them. If I
copy 10GB files between the two theres a 50% chance it'll pause and end
with cpu soft lockup messages.
Unsure if this is related:
After more testing I have modified the original description because
originally I was thinking it just affected XFS but now I don't think
that is the case. I just got another crash when using Ext3 so now I'm
not sure where the problem might be. It still looks like it probably
has something to do
34 matches
Mail list logo
