I'm going to update the bug title to help the appropriate action occur.
"INFO: task blocked for more than 120 seconds" is a diagnostic message
for when a process that wants to run in blocked from running for a long
time. It's a symptom, not a disease (read: bug). Just like you'd file a
new bug if
Should someone change the status of this bug in order to pull some
attraction on it again?
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have a machine running two guests under kvm, the first guest was
upgraded to lucid just after release and has never shown an issue.
However, just recently I upgraded the other guest and the host to lucid
and now the recently upgraded guest locks up completely with a similar
log to the ones above
P.S.: Even killing the cronjob did not helped to re-create a useable
system. I had to perfom a reboot :(
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Is definitely not fixed in Lucid 10.04. I'm facing this since upgrading
to Lucid.
Excerpt from the syslog:
--
May 18 11:43:05 damballah kernel: [ 2245.176082] usb 4-1: reset full speed USB
device using ohci_hcd and address 2
May 18 11:43:40 damballah kernel: [ 2280.216126]
Rebooting the machine does seem to help.
The "basically unusable" level was after 26 days of uptime.
Karmic, running on ESXi 4
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of
Encountering same issue w/ Ubuntu as a vmware guest. Very unpleasant
since I'd only recently made the move to the new virtual server layout.
Has made a previously reliable server almost unusable.
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bug
I have this problem too, it appears when i attach my camera to the
laptop. Attaching any of the other USB mass storage devices i have does
not cause problem. However once triggered the bug prevents any other USB
storage device from functioning.
And why is the status 'Fix Released' as even with t
Even in Lucid this error is present. They should worry more about serious
things like this than stupid colors and button placements.
-- Forwarded message --
From: danep
Date: 2010/5/4
Subject: [Bug 276476] Re: INFO: task blocked for more than 120 seconds
causes system freeze
To
I saw this in 9.10, and was very hopeful that upgrading to 10.04 would
fix it, but no cigar :( This morning I started seeing these errors
again. For me, they only occur on cron tasks. Symptoms include not being
able to log in via SSH or IMAP for the duration of the errors.
--
INFO: task blocked f
Since upgrading to Ubuntu 10.04, my LTSP clients are showing this
problem. The first client starts without any issues. All the other ones
display messages like: "[...] INFO: task sshd: 493 blocked for more than
120 seconds..." and similarly for other services.
--
INFO: task blocked for more than
I'm on ext3 and this is affecting me as well, so it may not be limited
to ext4 and xfs
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I think It could be related to this ext4 bug on kernel.org...hopefully a
kernel dev can shed more light on the issue?
https://bugzilla.kernel.org/show_bug.cgi?id=14830
I'm guessing this issue is also present on XFS too given the debug in
comment #3
** Bug watch added: Linux Kernel Bug Tracker #1
Hi,
sorry for double post (bug 494476) but this one seems to get more attention.
I'm getting the same errors (INFO: task xyz blocked for more than 120
seconds) since I upgraded to ext4 on my 4TB /home partition. It gets a
lot of I/O including rsync backups, smbd and nfs fileserver for ~20
people.
Hi,
I don't think this bug is defined correctly. I believe its not the hung
process that CAUSES the system freeze. Its something in the kernel/scheduler
that CAUSES a process to HANG, which then precipitates to the entire system.
So I don't recommend looking at individual programs or services
Per comment #34
Should we move on to separate bugs about the blocked tasks? (like bug 494476)
There are quite a lot of those (rsync, kvm, pdflush, kjournald, and more,...)
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this
bug exists. During a mv command through nfs with big video files in the client
machine got the following output
Client nfs machine:
Linux htpc 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 04:38:19 UTC 2010 x86_64
GNU/Linux
Server nfs machine:
Linux asterias 2.6.31-20-server #58-Ubuntu SMP Fri Mar
This particular bug has been fixed it was a scheduler problem.
The printout is a sanity check and there is many many different reasons
for it to be printed. Your problem looks to be related to the X display
driver. You should open a new bug for your problem.
--
INFO: task blocked for more than 1
Hi,
A friend of my has the same problem. He is using:
Linux smi01 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 05:23:09 UTC 2010 i686
GNU/Linux (Release 9.10)
Unfortunately the system freezes frequently. Looking into his dmesg learns me
that we are facing the same issue as described above. A sma
When I add kernel.hung_task_timeout_secs = 0 in my sysctl.conf, Most of the
time, I have small freeze from 1/2 seconds max...
But sometimes, I have a big freeze (need a reboot). The disk is new (and there
is no problem on it - checked before...)
Here a trace:
Feb 28 21:05:10 redshield kernel: [
I have the same problem. The freeze happens in disk-heavy tasks being
run.. (cp, dd, ...)
I'm on Linux welcome 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28
02:39:34 UTC 2010 x86_64 GNU/Linux
Here a trace from Virtualbox (when I was creating a disk of 40GB)
[ 600.427705] INFO: task VirtualBox:249
I'm seeing this on
Linux box05 2.6.32-02063209-generic #02063209 SMP Wed Feb 24 10:09:53 UTC 2010
x86_64 GNU/Linux
occurs while coping a disk to nfs share on another box
Feb 24 21:11:29 box05 kernel: [ 600.530615] INFO: task flush-0:25:2623 blocked
for more than 120 seconds.
Feb 24 21:11:29 bo
Sorry bad pronostic, forget my last comment ;-(
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
I had this problem on my eeepc 1201 ION on karmic ubuntu (2.6.31-17-generic).
I upgrade to 2.6.33-020633rc4-generic with the
NVIDIA-Linux-x86_64-195.30-pkg2.run nividia drivers.
I submitted my netbook to highload (I found out that the freeze occured
mostly on heavy hdd access )
Several hours aft
I've the same problem with karmic server (AMD 64), Linux
2.6.31-17-server #54-Ubuntu SMP. System freezes when I'm using a cpu
intensive scientific program. With Ubuntu 6.04 I not have this problem.
This is very annoying because I installed karmic in 20 computers last
week and they started to freeze
I can confirm this bug in karmic too, kernel
2.6.31-16-generic2.6.31-16-generic. System freezes often using chromium,
flashplugin eats 100% cpu and then computer hangs for a few minutes; in
terminal task block messages popup too.
--
INFO: task blocked for more than 120 seconds causes system freez
I believe this - very very bad problem - also happens in karmic according to a
poster above.
I'm beginning to think that the blocked task is not the "cause" but the
"effect" of this problem.
In other words, perhaps the scheduler or something in the kernel is foobar and
it thus results
in a task
> This started happening to me on 8.10 (2.6.27-16-generic) when I started a
> real-disk-to-real-disk "cp -a" inside a guest 9.10 running inside VMware.
In addition to the "blocked for more than 120 seconds" errors, I'm also
seeing characters that I'm typing repeat themselves. Reading LKML,
I see
This started happening to me on 8.10 (2.6.27-16-generic) when I started a
real-disk-to-real-disk "cp -a" inside a guest 9.10 running inside VMware.
The host 8.10 is having a very hard time with this.
Yesterday, the time-outs were all firefox:
# grep 'blocked for more than 120 seconds' syslog.0 |
This bug (or a similar one) is still affecting me, and I'm using
2.6.31-16 generic on Karmic.
It was frozen today for about 20 minutes before I gave up and restarted
it using SysRq+rseiub.
Does this mean we need to open a new bug report?
[23400.464046] INFO: task i915/0:318 blocked for more than
I have been bitten by this several times in Karmic.
For what it's worth I run FC12 on the same machine, and so far I haven't been
bitten by it there. (I believe FC12 also uses kernel 2.6.31).
I'll be getting more experience with FC12 now, since crashing every two
hours isn't acceptable. I'll po
A new bug should be filed for any 'task blocked' issues remaining in
Karmic, since the commits to fix the original issue are already in
kernel 2.6.31. This bug should actually be in the 'Fix Released' state,
so I'll fix that.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
This bug is still present in the final karmic.
What is the status with these commits being backported ?
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi,
I see what seems to be this same problem on my 8.10 server AMI's on EC2. They
freeze predictably after a certain period of activity. I found that memory got
below 35MB free when it froze and my 'top' listing showed kswapd with nice of
-5 appearing 2nd on the process list. My server image ha
Hi again.
Sorry I have to recall my confirmation.
Here are not the »120 seconds freeze« error messages any more but I had a
frozen system. I'm not sure it is caused by the same bug.
But it is definitely harder to get a frozen system.
Lars
--
INFO: task blocked for more than 120 seconds causes
@Andy, Can you please build kernels for karmic?
It happens for me on 2.6.31-3-generic #19-Ubuntu SMP, running on a
Intel(R) Pentium(R) 4 CPU 3.20GHz with two hyperthreads.
It does not involve any background processes (as far as I can tell).
It seems to happen when RAM gets tight (I run one or two
Hi Andy,
I can confirm that the amd64 version seems to fix the problem, at least with my
setup.
Thank you _very_much_!
Lars
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of
To fix this I would need someone to test the kernels I posted. As the
primary fixes to the scheduler we pulled in via a second stable update I
will regenerate these test kernels. Ok updated kernels are available at
the URL below, if you could test those and report back here:
http://people.ca
Hi!
I vote this bug to be changed to a higher importance.
It is very annoying because it happens quite often a day and more often when
the computer is running on high load.
(niced processes => 100% CPU load, e.g. boinc)
When playing mplayer video files (-vo xv) while the computer being on high l
It seems karmic affected too (2.6.30-9-generic)
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
Hi there!
I still have these problems (sometimes very often) with ubuntu 9.04
jaunty and 2.6.28-11-generic kernel.
Is a fixed kernel in sight?
Thanks
Lars
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notificat
On Wed, 2009-03-04 at 17:59 +, unikob wrote:
> Tested using Brian Rogers program from LKML:
>
> Current 8.10 chokes albeit doesn't hang, system becomes unusable.
>
> Current Jaunty (of 4.4.2009) gets a little choppy when four instances of
> the program runs at the same time,.
>
> Jaunty with
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Confirmed on Jaunty Alpha 6.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Tested using Brian Rogers program from LKML:
Current 8.10 chokes albeit doesn't hang, system becomes unusable.
Current Jaunty (of 4.4.2009) gets a little choppy when four instances of
the program runs at the same time,.
Jaunty with patched kernel fares best, no choppines when four instances
simu
We are indeed only carrying one of the three upstream commits (for
completeness):
cce7ade803699463ecc62a065ca522004f7ccb3d
6bc912b71b6f33b041cfde93ca3f019cbaa852bc
e17036dac189dd034c092a91df56aa740db7146d
We picked up the third of these via the v2.6.28.2 stable updates. I had
a chat
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andy Whitcroft (apw)
Status: Confirmed => In Progress
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubun
** Tags added: cherry-pick
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
** Description changed:
-
- This appears to be a kernel bug related to IO. Although everytime I get this
I've got Firefox open, latest incident happened when I had mp3gain running
through my music collection.
-
+ The following commits can be cleanly cherry-picked into 2.6.28 to fix this
bug:
Only one of the three commits for scheduler issues has been backported
in 2.6.28.2, and I can still produce this problem with 2.6.28-6-generic.
I believe the critical commit for this issue is
6bc912b71b6f33b041cfde93ca3f019cbaa852bc.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Co
Fix(es) Committed on latest stable kernel 2.6.28.2
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ub
Great!
I'll close this bug when I see the fix backported to current kernel in
8.10
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
This bug has been fixed upstream, by the following commits:
cce7ade803699463ecc62a065ca522004f7ccb3d
6bc912b71b6f33b041cfde93ca3f019cbaa852bc
e17036dac189dd034c092a91df56aa740db7146d
See this thread:
http://lkml.org/lkml/2009/1/11/70
It also looks like these fixes will be backported to the stable
kenjo wrote:
> On Tue, 2009-01-13 at 10:35 +, Martin Lindhe wrote:
>
>> kenjo wrote:
>>
>>> Are you also running a background process??
>>>
>>> I have changed to 2.6.28 and its much much better but still have had a
>>> few short freezes
>>>
>>>
>> What would qualify as a backg
On Tue, 2009-01-13 at 10:35 +, Martin Lindhe wrote:
> kenjo wrote:
> > Are you also running a background process??
> >
> > I have changed to 2.6.28 and its much much better but still have had a
> > few short freezes
> >
>
> What would qualify as a background process? I run several
> such as
kenjo wrote:
> Are you also running a background process??
>
> I have changed to 2.6.28 and its much much better but still have had a
> few short freezes
>
What would qualify as a background process? I run several
such as sshd, cupsd, bluetoothd ;)
However i also am running distributed.net cli
On Thu, 2009-01-08 at 10:38 +, Martin Lindhe wrote:
> I am also hit by this bug on my work PC (amd64 and fully updated Ubuntu
> 8.10).
>
> The issue usually shows up every work day. Gnome fully freeze up, even mouse
> cursor cant move.
> If you leave the computer alone for a couple of minutes
I am also hit by this bug on my work PC (amd64 and fully updated Ubuntu
8.10).
The issue usually shows up every work day. Gnome fully freeze up, even mouse
cursor cant move.
If you leave the computer alone for a couple of minutes it resumes to working
state.
Often the freeze happens in combinati
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
server-kernel 2.6.27-7 woks only slightly better: still have the issue,
but instead of freezing the entire system, it freezes only 1 application
(firefox or mplayer or any other active app you are using).
Also tried "Folding at Home" instead of Boinc (just to see if Boinc is
the real cause) - same
I cannot enclose the system log right now (not at home) - I can do it tonight,
but you won't see anything more than you have already posted above (no mention
of boincmgr in my syslog). Have you also noticed that pdflush is *always* the
first program frozen - could be a coincidence, maybe not
I
Apparently the bug is present even on the server kernel, as I just got
hit with this again.
Uname -a:
Linux ubuntu 2.6.27-8-server #1 SMP Thu Nov 6 18:18:16 UTC 2008 x86_64
GNU/Linux
And killing Boinc rectifies the system usability.
Previous server-kernels worked fine on my machine, what have c
Hi Ioan, could you attach your kern.log also?
I'm running boinc too, but in my case killing boinc did not fix the
issue. Anyway I'm changing status to confirmed.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
INFO: task blocked for more than 120 seconds causes system freeze
ht
server-kernel did not fix my issue - it still freezes.
Interesting fact - if it can help - I am running BOINC, and when the
system gets frozen, if I kill BOINC task - everything gets back to
normal. BTW, my config is amd64 (on Core2Duo), patched with latest
kernel 2.6.27-8
Any help will be highly
The problem went away when I switched to server-kernel. I don't know
what the differences are between generic and server kernel, but maybe
someone with more knowledge can find this info useful.
--
INFO: task blocked for more than 120 seconds causes system freeze
https://bugs.launchpad.net/bugs/27
Seems to be resemble bug #257331:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/257331
Searches around the interwebs seems to indicate dm-crypt as a potential
candidate, although I'm certain I'm not running my disks encrypted..
seems that there are other appearances of this floating around
As this happens frequently I've found out that the system recovers from
the freeze and resumes normal operation two to ten minutes after.
However the system continues to freeze periodically after that.
Steps to reproduce:
1. Do something that causes a lot of IO operations ie. copy images,
mp3's a
Changed to linux (kernel) as it appears it is not a nspluginwrapper bug
afterall.
** Summary changed:
- npviewer.bin segfaults, causes havoc, forces to reboot
+ INFO: task blocked for more than 120 seconds causes system freeze
** Description changed:
- Npviewer segfaults when visiting a website
68 matches
Mail list logo
