On Wed, Apr 07, 2010 at 12:18:35PM +0200, Davide Ferrari wrote:
> I don't think it's fixed in 2.6.32 (I'm using the one from backports)
> I have webservers running Apache which reach very very high loads and the
> server becomes completely unrensponsive through ssh, althoung ping (for
> example)
I don't think it's fixed in 2.6.32 (I'm using the one from backports)
I have webservers running Apache which reach very very high loads and the
server becomes completely unrensponsive through ssh, althoung ping (for
example) works.
This appears in the kernel log:
[ 1079.886691] INFO: task flush
Hello,
Am 25.03.2010 um 13:49 Uhr schrieb Pasi Kärkkäinen :
> On Tue, Mar 23, 2010 at 03:58:57PM +0100, Markus Hochholdinger wrote:
[..]
> Btw what kind of shared storage are you using?
I use lvm2 to use the hard disks of one server, cut out logical volumes with
stripping over all hard disks for
On Tue, Mar 23, 2010 at 03:58:57PM +0100, Markus Hochholdinger wrote:
> Hello,
>
> > There's a lot of people using Xen and Debian, how is the best solution
> > for a stable (production) kernel? (Xen+Lenny) ? Use the 2.6.32-10-xen
> > sid kernel in production servers?!?
>
> i use plain lenny for m
On Wed, 2010-03-24 at 09:53 -0300, Jorge Eduardo Birck wrote:
> I'm now using the most recent update in stable. No crashes in last week.
Excellent news!
> i will do it with the 2.6.32 stuff in my
> deploy servers to provide you a feedback. Provide feedback in this
> list/thread ?
If you find iss
happy to see this great support.
Thank you.
On Tue, Mar 23, 2010 at 6:02 AM, Ian Campbell wrote:
> On Mon, 2010-03-22 at 15:24 -0300, Jorge Eduardo Birck wrote:
>> Ok, this bug is fixed in non Xen-specific packages
>> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516374)
>
&
Hello,
> There's a lot of people using Xen and Debian, how is the best solution
> for a stable (production) kernel? (Xen+Lenny) ? Use the 2.6.32-10-xen
> sid kernel in production servers?!?
i use plain lenny for my dom0s and with 4) you're very near to what i use:
4b) 64-Bit for domUs is possibl
On Mon, 2010-03-22 at 15:24 -0300, Jorge Eduardo Birck wrote:
> Ok, this bug is fixed in non Xen-specific packages
> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516374)
The "120 seconds" message is a very generic symptom which can have lots
of root causes. As Ben notes to
Ok, this bug is fixed in non Xen-specific packages
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516374) , how about
the Xen-specific kernels, how to use a non-xen kernel in 64 xen
servers? How to keep it stable?
There's a lot of people using Xen and Debian, how is the best solution
Bug #516374 <http://bugs.debian.org/516374> has now been closed. This
was done on the assumption that a newer version of the Xen patch fixes
it, but since most of you reported problems on non-Xen systems this
cannot be true!
However, this bug report was becoming useless because it referre
On Wed, Mar 17, 2010 at 06:12:56PM +0100, maximilian attems wrote:
> On Wed, Mar 17, 2010 at 05:33:42PM +0100, Per Foreby wrote:
> > One simple(?) questions before you close the bug:
> >
> > - Which kernel should be upgraded to avoid this bug? dom0, domU or both?
>
> 2.6.33-10 images in linux uns
On Wed, Mar 17, 2010 at 05:33:42PM +0100, Per Foreby wrote:
> One simple(?) questions before you close the bug:
>
> - Which kernel should be upgraded to avoid this bug? dom0, domU or both?
2.6.33-10 images in linux unstable are assumed fixed.
primarly dom0, if you can still reproduce bug please
One simple(?) questions before you close the bug:
- Which kernel should be upgraded to avoid this bug? dom0, domU or both?
/Per
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://list
Your message dated Wed, 17 Mar 2010 16:10:17 +
with message-id
and subject line Bug#516374: fixed in linux-2.6 2.6.32-10
has caused the Debian Bug report #516374,
regarding INFO: task * blocked for more than 120 seconds. in numerous
non-SCHED_IDLE workloads
to be marked as done.
This means
I'm also having this problem.
Dom0 running 2.6.26-2-xen-amd64, domU on 2.6.26-2-686-bigmem. All domU:s
are using all available processor cores.
I've been having problems on and off since the machine was installed
last summer. Typically it would be days or weeks between lockups.
I've been ke
I'm experiencing this bug also, with kernel 2.6.26-2-xen-amd64 in a domU
on XenServer 5.5.0. Kernel traces below.
Would using a lenny backport of 2.6.30 be an appropriate workaround? It
appears to be listed on backports.org.
Mar 14 00:10:38 db kernel: [49210.688195] INFO: task mysqld:9248 blo
In case it's of any use to anyone reading this, I have a system which
was experiencing hangs of this nature:
[862971.676821] INFO: task apache2:29156 blocked for more than 120 seconds
every week or too. The dom0 kernel is current 2.6.26-2-xen-amd64 and the
domU kernel was current 2.6.26-2-686-big
On Tue, 2010-01-19 at 19:09 +, Phillip Mumford wrote:
> Any idea on this? I've been having similar problems on a variety of machines:
This message indicates only a particular class of bug ('soft-lockup'),
not a specific bug. So unfortunately I cannot make any general
suggestions.
[...]
> I'
Any idea on this? I've been having similar problems on a variety of machines:
[682451.031376] INFO: task murmur.x86:2205 blocked for more than 120 seconds.
[696016.661609] INFO: task syslogd:1745 blocked for more than 120 seconds.
[696205.632817] INFO: task syslogd:1745 blocked for more than 120
Hi,
Iam currently experiencing this as well on a VM, running KVM on a host.
Only running mysql, currently pretty low usage, but this evening, with a
pretty large query and it looks with pretty high I/O it was caused this
bug with the next messages in dmesg:
[669930.073036] INFO: task mysqld:
Good to know. Thanks.
// Ola
On Mon, Dec 14, 2009 at 03:14:52PM +0300, Vitaliy Gusev wrote:
> On Saturday 12 December 2009 11:58:19 pm Ola Lundqvist wrote:
> > Vitaliy
> >
> > Do you know the status?
>
> I don't know. However I see that it is not OpenVZ bug as reproduced on non
> ovz kernels.
On Saturday 12 December 2009 11:58:19 pm Ola Lundqvist wrote:
> Vitaliy
>
> Do you know the status?
I don't know. However I see that it is not OpenVZ bug as reproduced on non ovz
kernels.
> // Ola
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubsc
Vitaliy
Do you know the status?
// Ola
On Tue, Dec 08, 2009 at 11:58:08AM +0300, kay wrote:
> Could you please inform about the bug status? Do you need more logs?
> The bug is very annoying, as it is the backup server with squid and
> internet doesn't work when system is "in stuck". System stuck
Could you please inform about the bug status? Do you need more logs?
The bug is very annoying, as it is the backup server with squid and
internet doesn't work when system is "in stuck". System stucks
approximately 5 times in hour.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.o
On Monday 30 November 2009 09:23:48 pm kay wrote:
> Debian Lenny freezes for about 10-15 minutes, and I can not log in via SSH.
Hello! How did you obtain this log ?
Can you try to use netconsole to catch a whole kernel log?
>
> uname -a
> Linux dc 2.6.26-2-openvz-amd64 #1 SMP Thu Nov 5 03:06:00
Debian Lenny freezes for about 10-15 minutes, and I can not log in via SSH.
uname -a
Linux dc 2.6.26-2-openvz-amd64 #1 SMP Thu Nov 5 03:06:00 UTC 2009
x86_64 GNU/Linux
Here is the one of the logs:
[2410004.934456] INFO: task kjournald:23648 blocked for more than 120 seconds.
[2410004.934497] "ech
We're still seeing this, but with different workloads than before (i.e., the
workload which was affected in our earlier reports was fixed by
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=54;bug=517449, but there
are other workloads under which we're now observing this).
The common thread seems
We have too big problems with this scheduler bug.
It occurs on several Lenny Machines running as VM on ESX3.5U4
Installed Kernel Package is 2.6.26-19
The Machines are not crashing, but they tend to consume lots of cpu
resources until they are nearly unusable or affect other VMs running on
the ESX
Hi all!
Hardware: Dell PowerEdge 2900 with Hardware Raid and LVM on it.
This also happen on latest `lenny`'s kernel. mainly while Heavy load on I/O
subsystem:
[275692.879178] INFO: task pdflush:14958 blocked for more than 120 seconds.
[275692.879207] "echo 0 > /proc/sys/kernel/hung_
I believe I'm seeing this as well:
Oct 5 13:16:02 city-liza-lnx kernel: [2667853.298270] INFO: task squid:25807
blocked for more than 120 seconds.
Oct 5 13:16:02 city-liza-lnx kernel: [2667853.298303] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 5 13:16:02 cit
I am having a similar problem with 2.26.30-6. Here are the log entries.
I hope this helps.
Yours
John
[43680.636045] INFO: task bacula-sd:12964 blocked for more than 120 seconds.
[43680.636079] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[43680.636125] bacula-sd
Hi,
Quoting Ben Hutchings :
This is not exactly a crash, though I realise the effects are often just
as bad as a crash.
Yep, that's not really a crash. It can take some hours for the host to
be unresponsive due to the high load average (ssh, local login down).
It's like the system is wait
On Mon, 2009-09-07 at 09:25 +0200, Darck wrote:
> > This bug report is about systems that are *not* making use of
> > SCHED_IDLE, which are probably not due to the known scheduler bug. This
> > particular error message typically indicates a lock ordering bug or
> > infinite delay while holding a l
This bug report is about systems that are *not* making use of
SCHED_IDLE, which are probably not due to the known scheduler bug. This
particular error message typically indicates a lock ordering bug or
infinite delay while holding a lock, and can be caused by any kernel
component.
One such case
On Thu, 2009-09-03 at 10:14 +0200, Darck wrote:
> Hi,
>
> Still no news about this problem ?...
>
> While upgrading to a newer (unstable) kernel is easy with kernels
> provided by Debian, this is not the case with the Xen support.
>
> The 2.6.26-2 xen release is NOT useable in production envir
Hi,
Still no news about this problem ?...
While upgrading to a newer (unstable) kernel is easy with kernels
provided by Debian, this is not the case with the Xen support.
The 2.6.26-2 xen release is NOT useable in production environment, and
keep crashing the host due to this scheduler bug
Hi Ben
Ben Hutchings ben-at-decadent.org.uk |DebianBug| wrote:
On Fri, 2009-06-26 at 14:15 +1200, Brendon Green wrote:
I could rebuild the 2.6.26 host and guest kernels for the system in
question (I archive the .config files using a local version number
which, unfortunately, bears little or
On Thu, Jun 11, 2009 at 11:53:03AM -0400, John Morrissey wrote:
> On Mon, Jun 08, 2009 at 07:14:44PM -0400, John Morrissey wrote:
> > Thanks, Ben. Rebuilt with this patch and threw the resulting kernel on a
> > couple of machines running several KVM VMs. I'll be able to provide
> > confident feedba
On Mon, Jun 08, 2009 at 07:14:44PM -0400, John Morrissey wrote:
> Thanks, Ben. Rebuilt with this patch and threw the resulting kernel on a
> couple of machines running several KVM VMs. I'll be able to provide
> confident feedback in a couple of days.
These machines have been stable since running k
On Fri, Jun 05, 2009 at 03:37:33AM +0100, Ben Hutchings wrote:
> Please try the patch I posted here:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=54;bug=517449
>
> It includes a fix made between 2.6.26 and .28 that may address this bug.
Thanks, Ben. Rebuilt with this patch and threw the
Please try the patch I posted here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=54;bug=517449
It includes a fix made between 2.6.26 and .28 that may address this bug.
Ben.
--
Ben Hutchings
Logic doesn't apply to the real world. - Marvin Minsky
signature.asc
Description: This is a digita
Hi,
I am running to this bug very frequently (several time a day) on a 16
CPU ia64 system running linux-image-2.6.26-2-mckinley 2.6.26-15lenny2
Is there any progress being made in getting the fixes backported into a
lenny kernel?
Cheers,
Guy
--
Dr. Guy Coates, Informatics System Group
The We
ug report recently?
Nothing new since:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516374#20
I haven't been able to raise anybody on debian-kernel@ about this, and I've
reached the point where I don't know how to continue.
john
--
John Morrissey
I'm experiencing the same thing sporadically with two machines running a
handful of KVM VMs. It usually starts with one VM blocking, then spreads to
the rest, and eventually the host itself stops responding.
I cherry-picked the three patches in LP 276476 and applied them to the
2.6.28 kernel curre
Package: linux-source-2.6.26
Version: 2.6.26-13
Severity: important
I am experiencing the same bug as ubuntu # 276476
( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/276476 ),
albeit with an earlier kernel version.
I am submitting this bug report because Google tells me that 2.6.26
is not
45 matches
Mail list logo
