Your message dated Sat, 26 Nov 2022 20:46:16 +0100 (CET)
with message-id <20221126194616.70b45be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #900031,
regarding linux-image-4.9.0-6-amd64: task blocked for more th
Control: tag -1 moreinfo
On Thu, 2018-05-24 at 17:49 -0400, Allan Wind wrote:
> Package: src:linux
> Version: 4.9.88-1+deb9u1
> Severity: important
>
> Dear Maintainer,
>
> Sorry, this may not be a complete bug report, but I am happy to
> supply you with required information in a timely manner.
Processing control commands:
> tag -1 moreinfo
Bug #900031 [src:linux] linux-image-4.9.0-6-amd64: task blocked for more than
120 seconds
Added tag(s) moreinfo.
--
900031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900031
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Package: src:linux
Version: 4.9.88-1+deb9u1
Severity: important
Dear Maintainer,
Sorry, this may not be a complete bug report, but I am happy to
supply you with required information in a timely manner. On 2018-5-8, I
rebooted into 4.9.0-6, and observed various hangs since:
2018-05-24T03:17:0
Processing commands for cont...@bugs.debian.org:
> found 638316 linux-2.6/2.6.32-35
Bug #638316 [linux-image-2.6.32-5-amd64] base: Task blocked for more than 120
seconds
Bug Marked as found in versions linux-2.6/2.6.32-35.
> quit
Stopping processing here.
Please contact me if yo
found 638316 linux-2.6/2.6.32-35
quit
Hi John,
John Goerzen wrote:
> [Subject: Bug#638316: More info]
Please keep in mind that these show up as emails in a crowded inbox,
so the subject line can be a good place to put valuable context.
> Looks like there might be a patch to fix this - see
> ht
Hi Ben
> What is the Debian package version? (Run 'cat /proc/version'.)
$ cat /proc/version
Linux version 2.6.32-5-amd64 (Debian 2.6.32-39squeeze1) (da...@debian.org)
(gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Jan 9 20:49:59 UTC 2012
> Does the system recover from this, i.e. does the bac
Ben Hutchings writes:
> On Tue, 2012-01-24 at 16:09 +, Debian Bug Tracking System wrote:
>> Processing commands for cont...@bugs.debian.org:
>>
>> > reassign 657162 linux-image-2.6.32-5-amd64
>> Bug #657162 [linux-image-2.6.26-amd64] linux-image-2.6.26-amd64:
[Re-sending with the correct bug address.]
On Tue, 2012-01-24 at 15:14 +, Keith Edmunds wrote:
> Package: linux-image-2.6.26-amd64
> Version: linux-image-2.6.32-5-amd64
> Severity: important
What is the Debian package version? (Run 'cat /proc/version'.)
> We're seeing lots of the following
On Tue, 2012-01-24 at 16:09 +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
>
> > reassign 657162 linux-image-2.6.32-5-amd64
> Bug #657162 [linux-image-2.6.26-amd64] linux-image-2.6.26-amd64: task ...
> blocked for more than 120
Processing commands for cont...@bugs.debian.org:
> reassign 657162 linux-image-2.6.32-5-amd64
Bug #657162 [linux-image-2.6.26-amd64] linux-image-2.6.26-amd64: task ...
blocked for more than 120 seconds.
Warning: Unknown package 'linux-image-2.6.26-amd64'
Bug reassigned from package
Roberto Dal Zilio writes:
> On the xenserver I do not have a crashdump because the VM does not
> crash
Can you delibaretly crash it to obtain such a dump? The stuck processes
would still be visible in the dump.
> (I only get the task hang and the error in dmesg on the VM). Is it
> helpfull for y
Hi,
Roberto Dal Zilio writes:
> [904313.840676] updatedb.mloc D 880001855c40 0 14983 14979
> 0x
> [904313.840684] 880001855c40 0282 000800017880
> 8800032f5810
> [904313.840693] f9e0
> 88002cf2dfd8
> [904
Package: linux-2.6
Followup-For: Bug #582605
The last few months I'm getting these messages at more or less random
intervals (every few days or so) concerning different tasks (not only cron).
During the time
of this soft lockup the server remains unresponsive for a few minutes to
continue as norm
@ Jorge:
yes, i've searched a lot for this particular behaviour and found that almost
the roots that cause this problem are related to xen-kernels , but the
problem is that i don't have xen at all , this is a dedicated server only
running with apache2+php5 with no database backend !
@ Ben
well h
On Wed, May 26, 2010 at 10:59:07AM -0300, Jorge Eduardo Birck wrote:
> Happens to me too! And there's a lot of people with this problem, Ubuntu 10
> have this too. Look the google search (last week):
[...]
This message is a symptom of a whole class of bugs. It does not indicate a
particular bug.
Happens to me too! And there's a lot of people with this problem, Ubuntu 10
have this too. Look the google search (last week):
http://www.google.com.br/search?q=task+blocked+for+more+than+120+seconds&hl=pt-BR&tbo=1&prmdo=1&output=search&source=lnt&tbs=qdr:w&ei=py
On Fri, 2010-03-26 at 08:35 +0100, Timo Veith wrote:
> Hi all,
>
> sorry if my message from yesterday was noise too, but I haven't
> understood yet why those kernel log messages appear anyway. Somebody in
> this bug report pointed out that those "INFO: task xy blocked for more
> than 120 seconds."
same to me
a have different machines that have different services with this bug
On Fri, Mar 26, 2010 at 4:35 AM, Timo Veith wrote:
> Hi all,
>
> sorry if my message from yesterday was noise too, but I haven't
> understood yet why those kernel log messages appear anyway. Somebody in
> this bug re
Hi all,
sorry if my message from yesterday was noise too, but I haven't
understood yet why those kernel log messages appear anyway. Somebody in
this bug report pointed out that those "INFO: task xy blocked for more
than 120 seconds." are only symptoms of the real problem. Could somebody
explain th
Happens to me yesterday with
linux-image-2.6.26-2-xen-amd64_2.6.26-19lenny2_amd64.deb in differents
machines.
Hope this is fixed in 2.6.26-21
On Thu, Mar 25, 2010 at 6:47 AM, Timo Veith wrote:
> Package: linux-2.6
> Version: 2.6.26-21lenny4
> Followup-For: Bug #517449
>
>
>
> -- Package-specific
Package: linux-2.6
Version: 2.6.26-21lenny4
Followup-For: Bug #517449
-- Package-specific info:
** Version:
Linux version 2.6.26-2-vserver-amd64 (Debian 2.6.26-21lenny4)
(da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25))
#1 SMP Tue Mar 9 23:51:13 UTC 2010
** Comman
d to a
symptom (the soft-lockup warning 'INFO: task * blocked for more than 120
seconds') which indicates only a type of bug. You have probably
experienced several different bugs and they must be dealt with
separately.
If you are still seeing soft-lockups under kernel version
2.6.26-21le
Thanks for the fast answer!
On Thu, Mar 18, 2010 at 3:48 PM, Ben Hutchings wrote:
> On Thu, Mar 18, 2010 at 03:31:12PM -0300, Jorge Eduardo Birck wrote:
>> Hello.
>>
>> Im having this error:
>>
>> "task blocked for more than 120 seconds"
>&
On Thu, Mar 18, 2010 at 03:31:12PM -0300, Jorge Eduardo Birck wrote:
> Hello.
>
> Im having this error:
>
> "task blocked for more than 120 seconds"
>
> In all my Debian Lenny machines, including production servers. I
> always use Debian and a never seen
Hello.
Im having this error:
"task blocked for more than 120 seconds"
In all my Debian Lenny machines, including production servers. I
always use Debian and a never seen a kernel bug that make my servers
freezes before. It makes all my infrastructure (debian and xen based)
go unsta
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
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
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
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
Your message dated Thu, 26 Mar 2009 19:53:42 +
with message-id
and subject line Bug#518431: fixed in linux-2.6 2.6.26-14
has caused the Debian Bug report #518431,
regarding linux-2.6: NFS locking: task blocked for more than 120 seconds -> NFS
client stuck -> many processes wait on D
ote:
> NFS regression in 2.6.26?, "task blocked for more than 120 seconds"
> http://groups.google.com/group/linux.kernel/browse_thread/thread/d6fb6972a1043d95/1b0978941d189a5c?pli=1
Thanks in advance
--
Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers-Newark
Stud
t
interactively login, but seems to be be able to run non-pts-needed commands
(e.g. dmesg, etc). Both nodes started to puke those evil messages into their
logs (and netconsoles). brief googling lead me to
NFS regression in 2.6.26?, "task blocked for more than 120 seconds"
http://groups.goog
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-13
Severity: important
Once in a while the whole system start crawling with the following messages
printed in kernel log. Simple saving file in xemacs can completely freeze the
whole system for 30 seconds.
There is a similar bug reported in Ubu
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
47 matches
Mail list logo
