This version is now outdated and no more supported
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:2331
** Branch linked: lp:ubuntu/lucid-updates/dpkg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocked for more than 120 seconds.
To manage notifications about thi
This bug was fixed in the package dpkg - 1.15.5.6ubuntu4.6
---
dpkg (1.15.5.6ubuntu4.6) lucid-proposed; urgency=low
* Cherry-pick fixes for sync() behaviour in dpkg (LP: #624877):
- Disable by default usage of synchronous sync(2), as it causes undesired
I/O on unrelated fi
So I have verified that the proposed dpkg no longer hangs. I used the
following script to generate heavy load on the system:
#!/bin/bash
#
# Generate IO load
echo "starting load"
#dd if=/dev/zero of=zero &
sleep 1s
dd if=/dev/urandom of=urandom &
sleep 1s
dd if=/dev/sda1 of=sda1_backup1 &
sleep 1s
** Branch linked: lp:ubuntu/lucid-proposed/dpkg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocked for more than 120 seconds.
To manage notifications about th
Thanks to Ted for clearly elucidating the two competing issues. For the
time being we can't move from 10.04 (whole OS upgrades tend to be
unpopular with customers for point releases). However as the kernel lock
is always triggered by dpkg I'm hoping that just fixing dpkg will be
enough. I assume if
Hello Thomas, or anyone else affected,
Accepted dpkg into lucid-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/dpkg/1.15.5.6ubuntu4.6
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
There are two issues here, that interact and so they are confusing
people. The first is that the kernel has a potential livelock problem
in the writeback code, such that if there are constantly new pages
dirtied that requires writeback, the sync(2) system call will never
return (at least until all
The behaviour we are seeing is dpkg hangs and never returns. As dpkg is
left in the "D" state and is un-killable the only recourse is to hard
reset the box (power-cycle) it. However it might be due to file-system
load it can never achieve the file-system sync. I'm currently trying to
come up with a
My understanding of the bug, backed by the Debian lists, is that the
kernel isn't hanging or otherwise behaving improperly - a system-wide
sync call is being issued, and the system is waiting for all of the
filesystems to sync (as directed).
--
You received this bug notification because you are a
Surely the fix required is for the kernel? While dpkg might be good at
triggering the bug it may not be the only thing that can hang the kernel
requiring a hard reset.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Hey Scott, I've been keeping an eye on that one and am waiting for
someone knowledgeable about dpkg to review the actual fix before I
sponsor this fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624
Hi Michael,
Thank you for your patch attached in comment 50 above. A bot identified this
as a fix for lucid, and subscribed ubuntu-sponsors which put this bug on the
sponsorship queue at [1].
You stated:
| This should resolve the problem for people getting "Task blocked" errors
| without i
I'm confused as to when this fix was released. I can't see any
reference to this bug in the changelogs of either dpkg or the linux-
image. I'm seeing on customer 10.04LTS machines running the latest
packages which makes me think the bug is still there.
--
You received this bug notification becau
** Description changed:
- I try´d today to update my system with "aptitude update && aptitude
- dist-upgrade -y"
+ [Impact]
+
+ [Fix]
+
+ [Test Case]
+
+ [Regression Potential]
+
+ [Original Report]
+ I try´d today to update my system with "aptitude update && aptitude
dist-upgrade -y"
Ev
** Also affects: linux (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Lucid)
** Changed in: dpkg (Ubuntu)
Status: New => Fix Released
** Changed in: dpkg (Ubuntu Luc
** Changed in: linux
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocked for more than 120 seconds.
To manage notifications
The attachment "dpkg_1.15.5.6ubuntu4.5.debdiff" of this bug report has
been identified as being a patch in the form of a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. In the event that this is in
fact not a patc
This patch to lucid's current dpkg package disables the use of sync()
and backports the performance fix for fsync() on ext4 that was
introduced in 1.15.8.7
This should resolve the problem for people getting "Task blocked" errors
without impacting the performance on ext4, it requires more testing,
I think I just had this problem while running Precise as guest in
Virtualbox (4.1.18 on a Precise host). Installation of package linux-
header-generic would always hang on:
Unpacking replacement linux-headers-3.2.0-27 ...
while being unable to use Ctrl-C, killall -9 dpkg would kill the process
t
Those 2 commits cherry-picked on the current lucid kernel seem to fix the
problem for me :
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-oneiric.git;a=commit;h=b9543dac5bbc4aef0a598965b6b34f6259ab9a9b
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-oneiric.git;a=commit;h=aa373cf550994623efb5d49a4d8775
HorstBort --- could you try using VirtualBox on a more modern kernel
(ideally v3.3) and see whether VirtualBox is still doing this? And if
so, it would be great to strace VirtualBox so we can see what it is
doing.
Thanks,
--
You received this bug notification because you are a member of Ubuntu
I also experience this behaviour on 10.04 with kernel linux-image-
generic-lts-backport-natty :
Linux quantus 2.6.38-13-generic #57~lucid1-Ubuntu SMP Tue Mar 6 20:05:46
UTC 2012 x86_64 GNU/Linux
Apparently, Virtualbox is the culprit on my system. I have virtual
machines on a ext4 RAID1. When this
Please help. I am upgrading my ubuntu in my Intel learning series
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocked for more than 120 seconds.
To manage noti
+1 - this is happening to me as well, on EBS root EC2 instances that do
a *lot* of I/O. Please, this needs to be backported.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dp
These workarounds are all pretty ugly. Is there really not an official
fix for this. It happens on Amazon EC2 instances with EBS volumes. I'd
vote for a backport to 10.04...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
As I no longer use Ubuntu, I don't know about applying the official fix.
There are WORKAROUNDS in the thread, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:2331
I just installed 10.04 AMD 64. I took all the updates. I am getting
the error described here (bug #624229). Software I am running requires
10.04, so upgrading is not an option. I've read all the comments here.
I see it is fixed, but I do not see what I should do to get the fix?
--
You receiv
** Changed in: dpkg (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocked for more than 120 seconds.
To manage no
Could this bug be a duplicate og bug #570805?
** Also affects: dpkg (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584254
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On an busy lxc server 2.6.38-8-server amd64, I had elevator=cfq in the
cmdline, no dpkg was running, yet it got stuck with the same symptoms
(see the attached screenshot).
It is notable that the error happened across all dm- devices.
I ran the following command, let's see whether that would help:
Should note: we haven't had any issues since upgrading to dpkg/natty and
adding unsafe-io.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocked for more than 120
Amendment to above instructions (free advice warnings abound :-) )
Using the following:
Package: *
Pin: release n=natty
Pin-Priority: -500
NOTE: n= instead of a=. a= does not capture updates or security, which
caused confusion (and a potential problem).
I'm also placing it directly in /etc/apt
** Tags removed: regression-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocked for more than 120 seconds.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
I've had this problem while installing packages to production webservers
(no external drives or nfs volumes mounted). I just now noticed that,
at least in this case, stopping apache for a moment allowed sync to
finish.
--
You received this bug notification because you are a member of Ubuntu
Bugs
I believe I'm being affected by the same bug, though I have a different
stacktrace in my dmesg log:
[3187763.844945] INFO: task dpkg:25373 blocked for more than 120 seconds.
[3187763.844955] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[3187763.844960] dpkg D
My system was busy with a very large 'rsync' backup process on an
external drive and there was no possibility to 'aptitude safe-upgrade'
anything (hanging at unpacking). I killed the 'rsync' process and the
'aptitude safe-upgrade' ran smoothly.
I tested around a bit and noticed that it is really t
Do I get it right that the only immediate workaround is to upgrade dpkg?
The magic sys string didn't unstuck things for me. I did't try sync
though.
If the only way to fix the bug is to upgrade dpkg, how about rolling out
an updated dpkg for maverick?!
Thanks!
--
You received this bug notificat
Note that dpkg 1.15.8.7 and later uses sync_file_range() to help address
the sync latency problem. So simply upgrading to dpkg 1.16.0 may be
sufficient, without enabling --force-unsafe-io option.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
astrostl,
thanks for your instructions on dpkg, i'll wait a bit and then i guess do a
hard reset if nothing happens... hopefully things won't be in a defunct state
upon restart.
I'm using maverick 10.10 and not lucid (actually, i wish i had gone with the
LTS lucid...), and I think I understand
WARNING: those previous commands are for LUCID, and involve installing
packages from NATTY. Buyer beware! Furthermore, if it's run on a non-
LUCID system it will result in NATTY packages being installed by DEFAULT
unless the Pin-Priority setting is changed from LUCID to whatever the
system is act
FWIW, here is the command set for what I'm doing on my Lucid systems:
# make it so that lucid packages have default priority over natty ones
cat << EOF > /etc/apt/preferences.d/prefsources
Package: *
Pin: release a=natty
Pin-Priority: -10
Package: *
Pin: release a=lucid
Pin-Priority: 900
EOF
# cr
Hello,
I am currently experiencing this issue and reading through the bug comments I
am not quite sure how best to resolve it without damaging anything. It seems
like this will be fixed in a future release (natty), but is there a resource or
instructions available for troubleshooting and/or fix
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocked for more than 120 seconds.
--
ubuntu-bugs ma
"force-unsafe-io" can be added to /etc/dpkg/dpkg.cfg to make it a
default (hopefully for apt invocations too)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocke
Minor update: dpkg-dev and libdpkg-perl from Natty are also needed if
you have, say, build-essentials installed.
Total package list for an (EXPERIMENTAL) update -
dpkg_1.16.0~ubuntu6_amd64.deb
dpkg-dev_1.16.0~ubuntu6_all.deb
libdpkg-perl_1.16.0~ubuntu6_all.deb
liblzma2_5.0.0-2_amd64.deb
xz-utils_
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584254
Rich W ran into a thread on dpkg sync behavior, which led to that bug.
dpkg's fsync() call was changed to a sync() call, in order to improve
ext4/btrfs performance. Those of us with busy, completely unrelated
filesystems (such as heavy NFS t
Same problem, ubuntu 10.10 maverick, x86.
100% repeatable steps:
Plug in external drive (in my case, activated USB storage on my Nexus One, and
plugged it in, and opened the drive with nautilus, no other file transfer other
than however nautilus queries the drive I suspect)
Attempt to install s
We are also being affected by this bug. We roll packages to our cluster
which is always under heavy i/o pressure from nfs mounted volumes and
the dpkg installs hang for long periods of time due to this sync issue.
Hope this can get fixed since we are relying more on dpkg for updates to
our cluster
I was using apt-mirror to create an ubuntu mirror, decided to install
"bmon" and this happened to me. Disk activity seems related, but could
be a coincidence.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
I don't think this has to do with heavy disk activity - I had nothing
intensive running, and still don't. dpkg itself is certainly generating
zero activity.
This has happened to me twice now, on my Ubuntu 10.04 64 Desktop. Not
only can't I sudo pkill -9 dpkg, I can't shut down the machine; I have
Same problem here on Ubuntu 10.04 64
#uname -a
Linux ipf-srv001.ipf.local 2.6.32-28-server #55-Ubuntu SMP Mon Jan 10 23:57:16
UTC 2011 x86_64 GNU/Linux
with 1 external USB disk attached (ext4).
Dpkg is stuck on 'unkaping' and the only way to kill it is to rm
/var/lib/dpkg/lock
Any solution (exc
I am seeing this on a busy server as well. I am running Ubuntu 10.4 in
an openvz container on a busy server. Ext3 is the underlying file system
and the server itself is quite busy.
Dpkg hangs for at least a good hour on:
/usr/bin/dpkg --status-fd 14 --unpack --auto-deconfigure
/var/cache/apt/arch
I also seem to be experiencing this on high-traffic Ubuntu 10.04.2 LTS /
2.6.35-23-server / x64 / NFS/SAN-connected systems.
No ext4. From one host's mounts: binfmt_misc, debugfs, devpts,
devtmpfs, ext3, fusectl, nfs, proc, securityfs, sysfs, tmpfs.
It appears to be strongly correlated with heav
Does the problem go away in 2.6.37? There's an ext4 commit that may be
relevant, which hit mainline in 2.6.37:
5b41d92437 ext4: implement writeback livelock avoidance using page
tagging
The fact that changing the IO scheduler from "deadline" to "cfq" is also
interesting, given that most of the
A friend of mine just ran into this and we spent some time debugging it.
Long story short, I stumbled onto an lkml thread that seemed related
[1].
Something tytso said in his first reply [2], and the fact that the root
fs was ext4, led me to try:
echo 4 > /sys/fs/ext4/sda1/max_writeback_mb_bump
** Changed in: linux
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocked for more than 120 seconds.
--
ubuntu-bugs mailing li
@Filiprino
/boot/config-2.6.32-28-server : CONFIG_DEFAULT_IOSCHED="deadline"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocked for more than 120 seconds.
--
@Filiprino
/boot/config-2.6.32-2 : CONFIG_DEFAULT_IOSCHED="deadline"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocked for more than 120 seconds.
--
ubuntu
I though that the completely fair queuing scheduler was the default one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocked for more than 120 seconds.
--
ubu
Setting the io scheduler to cfq seems to have resolved/workaround the
issue for me.
Kernel parameter: elevator=cfq
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317
I suspect this issue is related to
https://bugzilla.kernel.org/show_bug.cgi?id=15426. Should a patch or
updated kernel be released, this issue should resolve itself. However,
this will require that the patch be included in a subsequent kernel or
backported and then packaged and deployed. I propo
For instance, a duplicate bug is
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/606341
And an interesting comment of that bug is
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/606341/comments/10 and
subsequent ones.
The bug seems related to heavy disk activity.
--
You received this
There are some duplicates of this bug and the problem is in a sync call.
Instead of executing an upgrade or installing new packages, try to do a sync.
user@computer:~$ sync;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Changed in: linux
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocked for more than 120 seconds.
--
ubuntu-bugs mailing
** Tags added: acpi-table-checksum
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624877
Title:
INFO: task dpkg:23317 blocked for more than 120 seconds.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
P.P.S. in /var/log/kern.log
Nov 12 16:48:16 evo1 kernel: [ 4316.056166] INFO: task dpkg:11443 blocked for
more than 120 seconds.
Nov 12 16:48:16 evo1 kernel: [ 4316.056454] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 12 16:48:16 evo1 kernel: [ 4316.056774] dpkg
P.S. I take it back, I don't think screen is involved... just did
another install (not inside of screen) and it hangs.
$ sudo apt-get install texinfo
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
texlive-latex-base texlive-gen
Possible hint: I also got this stuck dpkg process when running "apt-get
install" inside of "screen". Could not kill it with kill -9. It also
stuck on the unpacking step.
(I don't think it matters but I was installing the package "m4".)
After rebooting, I ran the same install without "screen" and
I've tried to get around this first by doing:
rm /var/lib/dpkg/lock
rm /var/cache/apt/archives/lock
dpkg --configure -a
apt-get install -f
But what I installed previously is now held in an inconsistent state. I can't
be apt-get purge'd and it can't be properly installed. So I:
dpkg --remove --f
9.10 updated to 10.04 I now get this behavior when trying to apt-get
install.
2.6.32-24-generic-pae i686
ps -ux shows /usr/bin/dpkg with a state of Ds
Is this caused by disk locking?
--
INFO: task dpkg:23317 blocked for more than 120 seconds.
https://bugs.launchpad.net/bugs/624877
You received
** Bug watch added: Linux Kernel Bug Tracker #18632
http://bugzilla.kernel.org/show_bug.cgi?id=18632
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=18632
Importance: Unknown
Status: Unknown
--
INFO: task dpkg:23317 blocked for more than 120 seconds.
https:/
the only solution to "kill" the dpkg process is a reboot.
But after it is the same behaviour...
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut
Status-Informationen einlesen... Fertig
Lese erweiterte Statusinformationen
Initialisiere Paketstatus... Fertig
Schreibe erweiterte
Any Update there?
Cant install / Upgrade my System!!!
[ 1321.499551] INFO: task dpkg:3764 blocked for more than 120 seconds.
[ 1321.499822] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 1321.526755] dpkg D 0 3764 3719 0x
[ 13
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/624877/+attachment/1521095/+files/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/624877/+attachment/1521096/+files/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http
75 matches
Mail list logo
