Hello from 2020 !
I have a debian 8 VM running a 3.16.51-3 kernel which also encountered
this bug a few times in the past days. The host is an ESXi 6.5.
Commenting in here because of search results. I don't know if anyone
else still experiences this ? (seen it on centos bug reports too :
https://b
I'm very desperated.
Ubuntu is very bad and the support haven't solved this problem since
July 2008!!!
For three mounth nothing was happened and today the issue was presented for
three time!!!
How Semmelb said, bug reappers in Ubuntu Server 10.04 LTS.
I also put an attachment to show this long-
BUG reapers in Ubuntu Server 10.04.1 LTS
Using Kernel 2.6.32-24 server running on an Asus P5K-E mainboard
Man this is annoying!
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because yo
There was no update to this from the OR after suggesting 10.04 LTS
should be ok. So I assume this is now in use and works. As I don't see
anybody requiring a fix in Hardy (no report back on the test kernel
either) I assume the immediate need is gone there. It would take some
amount of debugging/ver
Sim, this patch was part of 2.6.26, so beside all other things that have
gone into 10.04 (which is based on 2.6.32) this is part of it as well.
As all the comments from various sources indicate this problem was not
seen after 2.6.26, so 10.04 should be fine.
The patches test kernels would be for p
Dear Stefan,
thanks for your support!
Can you tell me if there is thi this patch in new Ubuntu 10.04 LTS
kernel?
In this way I can try to upgrade my servers to new version.
The crash is very occasional (about 3/6 months) and for this test with
pached kernel we have to wait long time.
Tell me wh
First it is not really clear why -18 works and -19 does not. Looking over the
patches in between, none of them immediately would looks as like it could be
the cause for that. And actually I wonder whether all comments really are about
the same problem or just the same symptom.
Anyway, as the ker
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags removed: kernel-candidate
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubunt
** Tags added: kernel-candidate kernel-reviewed
** Tags removed: kernel-needs-review
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Ubuntu
Bugs, which is a dir
THIS NIGHT A NEW CRASH AFTER SEVERAL MONTHS WITH MANY HOURS DOWN.
ALSO HEARTBEAT ISN'T ABLE TO SWITH TO SECOND SERVER BECAUSE THIS ISSUE NOT
RELEASE ALL RESOURCES!
I'VE ANOTHER DISTRO WITH SOME "YEARS" UP WITHOUT ANY PROBLEM.
THIS IS RIDICULOUS... UBUNTU SERVER IS RIDICULOUS!
IS IT UBUNTU SERVER A
THIS NIGHT A NEW CRASH AFTER SEVERAL MONTHS WITH MANY HOURS DOWN.
ALSO HEARTBEAT ISN'T ABLE TO SWITH TO SECOND SERVER BECAUSE THIS ISSUE NOT
RELEASE ALL RESOURCES!
I'VE ANOTHER DISTRO WITH SOME "YEARS" UP WITHOUT ANY PROBLEM.
THIS IS RIDICULOUS... UBUNTU SERVER IS RIDICULOUS!
IS IT UBUNTU SERVER A
THIS NIGHT A NEW CRASH AFTER SEVERAL MONTHS WITH MANY HOURS DOWN.
ALSO HEARTBEAT ISN'T ABLE TO SWITH TO SECOND SERVER BECAUSE THIS ISSUE NOT
RELEASE ALL RESOURCES!
I'VE ANOTHER DISTRO WITH SOME "YEARS" UP WITHOUT ANY PROBLEM.
THIS IS RIDICULOUS... UBUNTU SERVER IS RIDICULOUS!
IS IT UBUNTU SERVER A
On Tue, Jun 08, 2010 at 04:07:40PM -, Jeremy Foshee wrote:
> The Ubuntu Kernel Team is focused on providing the most stable kernel
> possible for a release schedule of 6 months.
Is there a document online, beyond this bug, that discusses where the
kernel team's support goals differ from the di
Clearly several of you are under a misconception as to the role of the
Ubuntu Kernel Team. I will attempt to clarify.
The Ubuntu Kernel Team is focused on providing the most stable kernel
possible for a release schedule of 6 months. This means that they are
committed to pulling in the patches from
...me to!
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
It's very sad that this bug is not being fixed by Ubuntu developers. I'm
very disappointed.
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Ubuntu
Bugs, which i
got the same problem on my Ubuntu 8.04 64 bit (home-)server. Is there a
solution yet? Should i try a update too 10.04 (use the server alone so i
ciuld risk the downtime)?
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You
Well, I've added the noapic boot option and now I am not able to
reproduce the error ...
That's an step forward ...
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a membe
Dear Ubuntu Users,
I'm hitting the same error/bug you are. My setup is the following :
- SunFire X4450 with 4 Intel Xeon 6-Core :
(Intel(R) Xeon(R) CPU E7450 @ 2.40GHz)
- Ubuntu 8.04 LTS :
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 8.04.4 LTS
Release:
We're hitting a similar problem; hard to say whether it's related to bug
#556919 or bug #540378 but we get
CPU#1 stuck for 66s
type stuff too. This is in a Lucid server host & guest, with lucid-
propsed enabled.
AfC
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond
I just started seeing this bug on an NFS server (nfs-kernel-server
1:1.1.2-2ubuntu2.2) on 8.04LTS (2.6.24-27-server #1 SMP Fri Mar 12
01:23:09 UTC 2010 x86_64 GNU/Linux / Ubuntu 2.6.24-27.68-server) with
four NFS exports from two iSCSI initiated volumes (open-iscsi
2.0.865-1ubuntu3.3). This NFS se
Another crash after 14h!
Here a screenshot.
http://img195.imageshack.us/img195/1930/screenshotjr.jpg
No comment!
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member
After 5 months, 2 crash in 1 day!
LTS???... Ridiculous!
PS: At boot ubuntu show:
[..] intel_rng: FWH not detected
[..] iTCO_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware
Is this the cause?
However it is difficult to diagnose ...
Regards
--
Server 8.04 LTS: soft lockup - C
After 5 months, 2 crash in 1 day!
LTS???... Ridiculous!
PS: At boot ubuntu show:
[..] intel_rng: FWH not detected
[..] iTCO_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware
Is this the cause?
However it is difficult to diagnose ...
Regards
** Changed in: linux (Ubuntu)
I neglected to mention that I would be very interested in whether you
encounter this issue in one of the more current releases of Karmic or
Lucid. Do you think you could run a LiveCD to verify this issue in one
of these releases?
Thanks in advance,
-JFo
--
Server 8.04 LTS: soft lockup - CPU#1
Charles,
The main difficulty is the total of 10,000 bugs that need attention. I'd
really appreciate dmesg logs and any other log file that is relevant to the
issue. Have you had the opportunity to test this versus the latest Hardy
release that just came out a few weeks ago?
I'd be very int
try clocksource=tsc at boot time...
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubu
Just curious... This is a high priority bug that affects many servers...
I thought this distribution had Long Term Support. This bug has been
sitting here for OVER A YEAR!!! Doesn't anyone care???
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.laun
Additionally, this is Ubuntu 8.04.3 LTS running on a hyperthreaded P4.
Disabling hyperthreading has no effect. I am reving it to Ubuntu
2.6.24-24.61-server, but not very hopeful...
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/2
I am encountering soft lockups related the bond module. I suspect they
are related however this situation is a bit different.
This server is dedicated, no virtualization, host or guest, here.
cat /proc/version_signature
Ubuntu 2.6.24-24.60-server
This unit runs bonding on 2 x Intel e1000 interfa
Here is the change log entry from the link I posted above:
Date: Mon Aug 17 14:34:59 2009 -0700
clockevent: Prevent dead lock on clockevents_lock
Currently clockevents_notify() is called with interrupts enabled at
some places and interrupts disabled at some other places.
Following up on my previous post. I have downgraded the kernel back to
2.6.18-2 on 20 of our guests. These machines have been running for over
a week with no incident. We have been able to reproduce this issue on
2.6.26-2 very consistently. We also attempted to upgrade to 2.6.30 but
we experien
Hi all,
I also confirm what Sim says: the issue isn't solved.
I also tell you to change the state in a Debian section, because that Simon
Boggis says that this bug is solved but isn't true!!!
@Chris Brown:You have reason, this issue isn't closed/solved and I don't
understand why Simon Boggis (an
Hello everybody,
such as Chris Braun says at his last sentence of his post, Sim and Simon Boggis
isn't the same person.
Infact I'm Sim and I don't know who is the other person who pretends to be me!!!
However, the issue seems to be solved but unfortunatelly tonight it was
resubmitted the same pr
I am seeing the same symptom as Sim. Seems to have popped up after
upgrading from Debian 4 (2.6.18-6-686-BIGMEM) to Debian 5
(2.6.26-2-686-BIGMEM). I have a bout 25 VMs running ESX 4 and 3.5 that
are all running debian kernel 2.6.26-2. They are all 2 CPU VMs runnning
on 2, 4, and 8 way systems.
On Thu, Aug 13, 2009 at 11:32:20PM -, Leann Ogasawara wrote:
> I'm marking this Fix Released against the actively developed kernel
> based on the feedback from Sim, the original bug reporter:
>
> https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/245779/comments/53
But since I am seein
I'm marking this Fix Released against the actively developed kernel
based on the feedback from Sim, the original bug reporter:
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/245779/comments/53
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
Server 8.04 LTS:
Perhaps related to this kernel bug with a patch against 2.6.27-rc5:
http://bugzilla.kernel.org/show_bug.cgi?id=10753
** Bug watch added: Linux Kernel Bug Tracker #10753
http://bugzilla.kernel.org/show_bug.cgi?id=10753
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond
At one point I was able to track down a kernel.org post about the root of
the problem, but I can't remember exactly what it was. But I recall it was
due to a mistake on the part of one of the kernel devs.
-W
On Wed, Jul 22, 2009 at 2:36 PM, Ryan Lovett
wrote:
> On Wed, Jul 22, 2009 at 06:23:0
On Wed, Jul 22, 2009 at 06:23:01PM -, Warren V wrote:
> Upgrade your kernel to 2.6.28. CentOS is now on 2.6.28-128, I noted the
> problem went away around 2.6.28-92.
>
> Ubuntu is stuck with whatever is currently out.
Do you know which patch addressed the issue? If so, the Ubuntu kernel devs
Upgrade your kernel to 2.6.28. CentOS is now on 2.6.28-128, I noted the
problem went away around 2.6.28-92.
Ubuntu is stuck with whatever is currently out.
On Wed, Jul 22, 2009 at 12:55 PM, Ryan Lovett
wrote:
> We are seeing this problem with 2.6.24-24-server. We were running with
> -23 recent
We are seeing this problem with 2.6.24-24-server. We were running with
-23 recently but had this problem and upgraded after reading this
report. Additionally, the CPU load on the machine is around 190 though
summing the individual processes in top doesn't approach that total.
kswapd is near the top
Leann Ogasawara wrote:
> Sim, since you are the original bug reporter, care to comment if this is
> now resolved for you as well? Thanks.
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
I have not had a recurrence on any of my equipment (of the order of 25
servers),
Sim, since you are the original bug reporter, care to comment if this is
now resolved for you as well? Thanks.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/
I had this problem with kernel release 2.6.24.19-server on 4 cloned Ubuntu
8.04.2 on Vmware ESX 3.5.
The problem happened randomly twice a day or even more on all cloned servers.
After doing dist-upgrade to 2.6.24.24-server the problem disappeared.
Kind regards
--
Ludovico
--
Server 8.04 LTS:
Are there any changes with this error
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing li
1 Year and we have always the same problem!
For 4 month I haven't had any problem.
In this week two server (see my first post) have crashed with the same results,
without touching anything!
This is very very very ridiculous!
This big problem is appared with kernel 2.6.24-19-server
No comment!
Sorry, I'm using using the latest Ubuntu 8.04 kernel: 2.6.24-23-server
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber
using 2.6.24 or 2.6.18-128?
-W
On Fri, Feb 13, 2009 at 12:12 AM, Hark wrote:
> Yesterday I got this error again:
> Feb 12 19:20:52 xxx kernel: [1410045.600863] BUG: soft lockup - CPU#3
> stuck for 11s! [kvm:10534]
>
> I had to use the remote power switch to get the machine running again,
>
Yesterday I got this error again:
Feb 12 19:20:52 xxx kernel: [1410045.600863] BUG: soft lockup - CPU#3
stuck for 11s! [kvm:10534]
I had to use the remote power switch to get the machine running again,
and that's definitely not something I want on a production machine!
--
Server 8.04 LTS:
Hi-
Actually, I think I have one better. The latest redhat kernel patch release
for 2.6.18-128 seems to have fixed the issue (two weeks now, no reboot or
lockup), even though there is no "official" fix listed. It looks like they
made some alterations to the bonding code to fix some bogus MAC addre
This isn't a solution to the bug, but you may find that using the
backports repository to install xen 3.3.0 and the 2.6.24-23 kernel
yields some positive results. On one of my boxes, I could consistently
trigger the 'CPU#1 stuck' problem, and after upgrading it hasn't locked
up once. Of course, on
Howdy-
All of my units are using dual or quad-core Intels. The quads don't seem to
throw the softlock error- top just shows that one of the cores is slammed,
and everything slows to a crawl. I can't seem to be able to kill the bonding
kmod- so I always end up having to reboot the units. I'm going
I think there might be two bugs here. Something regarding bonding,
which I've seen on our Dell machines with Centos 5 too.
And then a general cpu softlock problem, which I'm also experiencing
with Hardy as a Xen guest - that I think is Xen related (I see it come
up with various processes - whatev
Lily, you use kernel 2.6.24-19. That's not the newest one for Hardy, the
newest one is currently 2.6.24-22. Using the latest kernels this bug
hasn't occurred on my servers anymore for some time now. But when, on a
updated server, I start a KVM with an older kernel and multiple
processors configured
I am seeing this same issue across multiple Dell platforms running
CentOS 5.2. I have a bug report there:
http://bugs.centos.org/view.php?id=3318
I'm seeing this item with both the 2.6.17 and 2.6.18 kernels- the base
kernels seem to be the most stable. Occasionally, I don't get the soft
lockup mes
I have a Dell 6650 running whatever the latest xen server image is (and
I run update/upgrade/dist-upgrade frequently). One DomU locks up pretty
regularly with "BUG: soft lockup - CPU#1 stuck for 11s!", usually during
large file transfers. DomU Kernel version is 2.6.24-19. The bug
*requires* destroy
I noticed that debbugs #490156 was closed, and was marked as being fixed in
2.6.26.
Will this kernel (or the fix) ever be available in hardy? Or am i going to have
to upgrade all of my servers to Intrepid?
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https:
I experienced this bond driver lockup problem in a few Xen dom0
instances (though on Centos with a 2.6.18 kernel). Reducing number of
cpus in dom0 to 1 worked around it for now. No crash in weeks since.
Probably not an option for everyone, but is fine for us.
--
Server 8.04 LTS: soft lockup - CP
** Changed in: linux (Debian)
Status: New => Fix Released
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Well, no luck.
I first added it to the kernel params on dom0, and it didn't take long
before I had a vm lockup. So then I added it into the domU kernel
params. Things were going good for almost 2 days, but it did lock up
again.
So I don't think NO_HZ=y has made any difference.
--
Server 8.04 LT
No, I haven't tried that before, but I'm willing to give it a try. This
parameter goes on dom0, correct?
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Ubuntu
sitzmar, have you tried the NO_HZ=y boot option?
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mai
Stuck in the same boat. Just wanted to add that I've been running
2.6.24-22-xen for a week now, with really no change in behavior. Random
lockups still occur.
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received thi
Dave, what's the verdict on the -21 kernel? Did it fix your lockups?
Also, did you try the NO_HZ=y boot option?
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of
I've been fighting with this bug for 2 months now. Sometimes I get
uptime of a couple of weeks. Sometimes only a couple of days. Very weird
and seems resilient to kernel changes.
My setup is a Dual Quad Core Xeon 5405 (6Mbyte cache) mounted on a
supermicro X7DCL-i motherboard with 8gigs of DDR2 EC
I have the same problem on totally different hardware. Today one of our
Dell PowerEdge R300 servers crashed with the message:
BUG: soft lockup - CPU#2 stuck for 11s! [kvm:5246]
This machine was still using kernel 2.6.24-19.36. I updated it to
2.6.24-19.41 now, but after reading the comments here
BAD NEWS!!BAD NEWS!!BAD NEWS!!BAD NEWS!!BAD NEWS!!BAD
NEWS!!
My server was broken today, after 23 days, with kernel Ubuntu
2.6.24-19.41-server
Here output:
[2015093.126455] BUG: soft lockup - CPU#0 stuck for 11s! [bond0:3867]
[20150.] BUG: soft l
Update:
@Leann Ogasawara - Hi! I'm running Kernel "Ubuntu 2.6.24-19.41-server"
from 21 days, without any problem ( for now ;-) )
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because y
@Sim - 'cat /proc/version_signature' should give you the exact Ubuntu
kernel version
@Malex - I'm not quite sure I understand your question. Testing the
upcoming Intrepid Ibex 8.10 Alpha# is completely voluntary if you choose
to do so. Also, only Intrepid will contain this newer 2.6.27 kernel, i
Hi Leann,
excuse me but I don't understand a thing:
why must I upgrade the 8.04 "HH" to 8.10 "II" to alpha5 (at the link
that you have reported there isn't that version!)?
>From what I read, Sim has upgrade the 8.04 at the last(?) available
Kernel that is 2.6.24.-19.41 server
Coul
Hi!
Now I'm running last kernel on my server.
I have a question. Can I know exactly version of kernel?
# cat /proc/sys/kernel/osrelease
or
# uname -a
show only: 2.6.24-19-server
and not 2.6.24-19.xx
Thanks
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
h
Hi Leann,
hi to all.
I will try this release next day.
My servers are critical and I have to do these tests with attention.
Unfortunately the problem does not appear immediately and takes 1 to 2 weeks of
uptime.
I can confirm the same problem with Ubuntu 8.04 LTS run on VMware ESX
3.5 (and in t
Hi Malex,
The kernel team sent out this call for testing to a majority of the bug
reports to get immediate feedback regarding the 2.6.27 kernel from those
willing to test. Unfortunately It is unknown if the newer 2.6.27 kernel
will specifically resolve the issue reported here. Would anyone else
Hello Leann,
I would ask you this question:
Has The Kernel Team identified the reason that causing the bug reported
here with this release of new kernel or not?
I ask you this because it's difficoult for me to stop crucial server if
also with this new update the bug continues
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
...In addition to the my previous post, this problem is happened in a VM
(ESX 3.5i) without bonding.
Regards.
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of
Hello everybody,
I also have the same problem that Sim describes on the top of this
thread.
I know that is out the new Kernel (Ubuntu Security Notice USN-637-1 --August
25, 2008) : linux-image-2.6.24-19 --->2.6.24-19.41
but I have many fear to upgrade because I should stop some crucial serv
It would appear from reading that thread on the lkml that the temporary
fix is to set a boot option of NO_HZ=y. I no longer have my 8.04.01
machine to test this on, but might be able to set it up dual boot some
weekend to play.
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795]
This bug is discussed in the lkml from last december.
http://lkml.org/lkml/2007/12/7/299
It is not apparent that it was actually fixed
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification bec
I too can confirm this problem with 8.04.01 with all updates / upgrades
applied. I WAS running on a dual quad core opteron machine with a tyan
server class mobo, 32 Gigs of 667MHz ram, and an Areca 1680 SAS card
with 16 drives in a large RAID-10 configuration. Under even moderate db
loads I would
Hi,
same errot at me with 2.6.24-18 too during boots...
aty
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ub
** Changed in: linux (Debian)
Status: Unknown => New
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubun
** Also affects: linux (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490156
Importance: Unknown
Status: Unknown
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification
Hi!
20 days uptime with old kernel version!
I can confirm 2.6.24-19 affected and not 2.6.24-18 !!
Pls. fix it
Thanks!
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a mem
I've seen a very similar bug with a debian testing 2.6.24-1-686 kernel,
which will be very closely related to the ubuntu 8.04 one
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490156#2).
I've had it twice on two different but identical chassis - Viglen
branded Intel chassis with Intel Server
I have the following facts:
- I got the same error message, after a kernel upgrade to -19. It repeats
itself after hald is loaded. By googling for a solution with that message I
found this topic.
- I run Ubuntu 8.04
- I do have a different processor
- The pc wouldn't accept any input (except rese
Hi brupje,
I'm not sure that it is the same problem.
Have you bonding?
Have you read changelog of your bios upgrade?
I our case we have message repeated at the console with freeze of all
(ethernet, keyboard, ping, bonding, etc).
This is the bessage:
BUG: soft lockup - CPU#1 stuck for xx s! [bon
I experienced the problem with my Asus p5b-deluxe with core 2 duo E6400.
While browsing for a solution I found some hints that this problem
requires a micro code update for your processor, provided by a BIOS
update. I figured it couldn't hurt much, so I did.
I rebooted a few times and the problem
** Tags added: regression
** Changed in: linux (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received t
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ub
** Summary changed:
- Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795]
+ Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond -
bond0
--
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You
93 matches
Mail list logo
