| 2006-09-29 14:22:54 |
JosefK |
bug |
|
|
added bug |
| 2006-09-29 23:34:39 |
Kevin Kubasik |
None: statusexplanation |
|
Assigning to the ubuntu installer, hopefully someone there can help you! |
|
| 2006-10-02 13:17:25 |
Colin Watson |
ubiquity: statusexplanation |
Assigning to the ubuntu installer, hopefully someone there can help you! |
For future reference, Kevin, bugs about the alternate install CD should go to 'debian-installer' (not 'ubiquity') unless you have more accurate information. I'll set this to pkgsel for now, as that's the component responsible for this stage of the installation.
Josef, I've had reports of this stage being very slow, but getting there eventually. How long did you leave it? |
|
| 2006-10-27 09:29:29 |
Mikkel Kamstrup Erlandsen |
bug |
|
|
added attachment 'lspci.log' (lspci -vv) |
| 2007-06-06 09:44:20 |
Colin Watson |
bug |
|
|
assigned to Debian |
| 2007-06-06 09:47:25 |
Colin Watson |
pkgsel: status |
Unconfirmed |
Needs Info |
|
| 2007-06-06 09:47:25 |
Colin Watson |
pkgsel: importance |
Undecided |
High |
|
| 2007-06-06 09:47:25 |
Colin Watson |
pkgsel: statusexplanation |
For future reference, Kevin, bugs about the alternate install CD should go to 'debian-installer' (not 'ubiquity') unless you have more accurate information. I'll set this to pkgsel for now, as that's the component responsible for this stage of the installation.
Josef, I've had reports of this stage being very slow, but getting there eventually. How long did you leave it? |
|
|
| 2007-06-06 09:47:25 |
Colin Watson |
pkgsel: assignee |
|
kamion |
|
| 2007-06-07 07:43:31 |
Bug Watch Updater |
None: status |
Unknown |
Unconfirmed |
|
| 2007-07-25 14:39:01 |
Colin Watson |
pkgsel: status |
Incomplete |
Fix Released |
|
| 2007-07-25 14:39:01 |
Colin Watson |
pkgsel: statusexplanation |
|
I *believe* that I've finally got this fixed. However, I never could reproduce it myself, and the change to debconf-apt-progress verges on a rewrite of its main loop, so I would very much appreciate testing by anyone who could reproduce this. Tomorrow's daily build of Gutsy's alternate images, or Tribe 4 if you prefer, should include this fix.
debconf (1.5.14) unstable; urgency=low
[ Colin Watson ]
* Retry flock() on EINTR. Failing that, print the errno if flock() fails
so that we have a better chance of working out why.
* Install Python confmodule for python2.5 as well.
* Add confmodule bindings for the DATA command.
* Somebody looking at confmodule(3) probably actually wants
debconf-devel(7). Add a reference in SEE ALSO.
* Make sure that apt status commands and debconf protocol commands under
debconf-apt-progress are properly interleaved. Closes: #425397
[ Debconf Translations ]
* Marathi added. Closes: #416805
* Basque updated. Closes: #418897
[ Programs Translations ]
* Marathi added. Closes: #416805
* Punjabi added. Closes: #427327
* Basque updated. Closes: #418902
* Esperanto added. Closes: #428275
[ Joey Hess ]
* Increase selectspacer to 13 for dialog. May be needed due to changes in
new versions of dialog.
* Update url to web site in README.
[ Trent Buck ]
* Fix bash_completion syntax. Closes: #425676
-- Colin Watson <cjwatson@debian.org> Wed, 25 Jul 2007 14:58:39 +0100 |
|
| 2007-07-26 08:11:02 |
Bug Watch Updater |
debconf: status |
New |
Fix Released |
|
| 2007-07-27 10:28:50 |
Colin Watson |
debconf: status |
New |
Confirmed |
|
| 2007-07-27 10:28:50 |
Colin Watson |
debconf: importance |
Undecided |
High |
|
| 2007-07-27 10:28:50 |
Colin Watson |
debconf: statusexplanation |
|
This causes frequent hangs during installation. If the fix is confirmed to work well in Gutsy, I'd like to propose it for Ubuntu 6.06.2. |
|
| 2007-07-27 10:28:50 |
Colin Watson |
debconf: assignee |
|
kamion |
|
| 2007-07-27 10:35:46 |
Colin Watson |
bug |
|
|
added attachment 'debconf.r2214.diff' (debconf r2214, possible fix for this) |
| 2007-08-05 15:57:49 |
Colin Watson |
debconf: status |
Confirmed |
In Progress |
|
| 2007-08-05 15:57:49 |
Colin Watson |
debconf: statusexplanation |
This causes frequent hangs during installation. If the fix is confirmed to work well in Gutsy, I'd like to propose it for Ubuntu 6.06.2. |
I have posted modified versions of the i386 alternate install CDs for Dapper, Edgy, and Feisty here:
http://cdimage.ubuntu.com/custom/20070805-bug62986/
I would very much appreciate it if anyone affected by this bug could attempt installations from these and report whether they fix the hangs you reported. I would *particularly* appreciate testing of the Dapper image, as my ability to get this fix into Ubuntu 6.06.2 (due in about a month's time, but the fix needs to go into the archive this week) is directly dependent on successful testing by affected users.
Please report successes or failures at fixing the specific problem in this bug here. Please report any other problems as separate bugs.
Thanks in advance! |
|
| 2007-08-07 08:41:27 |
Colin Watson |
description |
No more specific information to add than the title. Both the amd64 and i386 alternate cds hang during package selection\installation. No useful information in dmesg or the installer log.
Debian netinst daily from 28-Sep-2006 runs fine on the same machine, and memtest doesnt report any problems. |
debconf-apt-progress is a helper program used by the installer to run apt-get and turn its progress output into debconf progress bar commands, while passing through any genuine debconf interaction by the packages being installed. Ever since I originally wrote it, that passthrough function has been handled incorrectly: it simply passes through its debconf file descriptors to the child process, which means that child processes may collide with debconf-apt-progress itself while communicating with debconf.
The effect of this is that users installing on SMP systems experience sporadic hangs during the pkgsel step of d-i ("Select and install software"). Since it is a race, frequencies vary; I've heard 30% recently from one person installing on a large number of machines at once. There is absolutely no indication of what has gone wrong, so it gives a very bad impression, and I think therefore it is worth fixing this in Ubuntu 6.06.2.
I believe that this has been fixed in debconf 1.5.14 in Debian unstable and Ubuntu gutsy. While the patch is substantial as it reorganises debconf-apt-progress' main loop, it operates by opening two additional pipes for the command and reply ends of the debconf protocol, and serialising apt status messages and debconf protocol messages using a select loop, ensuring that collisions cannot occur. I am still actively soliciting testing to confirm that this fixes the bug experienced by users and does not regress.
Since this is a race, I cannot provide cast-iron instructions on reproducing the bug. However, installing several times (ideally automated with a fresh disk) on a multi-processor system should be sufficient to hit it eventually.
The only code outside the installer that uses debconf-apt-progress is tasksel. Thus, unless one is using tasksel regularly (which is relatively rare), this patch is not likely to have any effect on upgraders. If it goes wrong, the consequences are likely to be similar to the original bug, i.e. hangs in the pkgsel step of d-i. |
|
| 2007-08-07 08:41:27 |
Colin Watson |
title |
edgy installer randomly hangs on Core 2 Duo, Dell D620 |
debconf-apt-progress hangs sometimes on SMP systems due to racy debconf protocol handling |
|
| 2007-08-07 08:42:11 |
Colin Watson |
bug |
|
|
added attachment 'debconf.dapper-proposed.diff' (patch applicable to dapper) |
| 2007-08-07 08:43:49 |
Colin Watson |
description |
debconf-apt-progress is a helper program used by the installer to run apt-get and turn its progress output into debconf progress bar commands, while passing through any genuine debconf interaction by the packages being installed. Ever since I originally wrote it, that passthrough function has been handled incorrectly: it simply passes through its debconf file descriptors to the child process, which means that child processes may collide with debconf-apt-progress itself while communicating with debconf.
The effect of this is that users installing on SMP systems experience sporadic hangs during the pkgsel step of d-i ("Select and install software"). Since it is a race, frequencies vary; I've heard 30% recently from one person installing on a large number of machines at once. There is absolutely no indication of what has gone wrong, so it gives a very bad impression, and I think therefore it is worth fixing this in Ubuntu 6.06.2.
I believe that this has been fixed in debconf 1.5.14 in Debian unstable and Ubuntu gutsy. While the patch is substantial as it reorganises debconf-apt-progress' main loop, it operates by opening two additional pipes for the command and reply ends of the debconf protocol, and serialising apt status messages and debconf protocol messages using a select loop, ensuring that collisions cannot occur. I am still actively soliciting testing to confirm that this fixes the bug experienced by users and does not regress.
Since this is a race, I cannot provide cast-iron instructions on reproducing the bug. However, installing several times (ideally automated with a fresh disk) on a multi-processor system should be sufficient to hit it eventually.
The only code outside the installer that uses debconf-apt-progress is tasksel. Thus, unless one is using tasksel regularly (which is relatively rare), this patch is not likely to have any effect on upgraders. If it goes wrong, the consequences are likely to be similar to the original bug, i.e. hangs in the pkgsel step of d-i. |
debconf-apt-progress is a helper program used by the installer to run apt-get and turn its progress output into debconf progress bar commands, while passing through any genuine debconf interaction by the packages being installed. Ever since I originally wrote it, that passthrough function has been handled incorrectly: it simply passes through its debconf file descriptors to the child process, which means that child processes may collide with debconf-apt-progress itself while communicating with debconf. This bug is present in all releases since Ubuntu 6.06.
The effect of this is that users installing on SMP systems experience sporadic hangs during the pkgsel step of d-i ("Select and install software"). Since it is a race, frequencies vary; I've heard 30% recently from one person installing on a large number of machines at once. There is absolutely no indication of what has gone wrong, so it gives a very bad impression, and I think therefore it is worth fixing this in Ubuntu 6.06.2.
I believe that this has been fixed in debconf 1.5.14 in Debian unstable and Ubuntu gutsy. While the patch is substantial as it reorganises debconf-apt-progress' main loop, it operates by opening two additional pipes for the command and reply ends of the debconf protocol, and serialising apt status messages and debconf protocol messages using a select loop, ensuring that collisions cannot occur. I am still actively soliciting testing to confirm that this fixes the bug experienced by users and does not regress. https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/62986/comments/16 links to the patch I applied to the test CD images linked to from this bug.
Since this is a race, I cannot provide cast-iron instructions on reproducing the bug. However, installing several times (ideally automated with a fresh disk) on a multi-processor system should be sufficient to hit it eventually.
The only code outside the installer that uses debconf-apt-progress is tasksel. Thus, unless one is using tasksel regularly (which is relatively rare), this patch is not likely to have any effect on upgraders. If it goes wrong, the consequences are likely to be similar to the original bug, i.e. hangs in the pkgsel step of d-i. |
|
| 2007-08-07 08:44:46 |
Colin Watson |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2007-08-10 09:50:41 |
Martin Pitt |
debconf: status |
In Progress |
Fix Committed |
|
| 2007-08-10 09:50:41 |
Martin Pitt |
debconf: statusexplanation |
I have posted modified versions of the i386 alternate install CDs for Dapper, Edgy, and Feisty here:
http://cdimage.ubuntu.com/custom/20070805-bug62986/
I would very much appreciate it if anyone affected by this bug could attempt installations from these and report whether they fix the hangs you reported. I would *particularly* appreciate testing of the Dapper image, as my ability to get this fix into Ubuntu 6.06.2 (due in about a month's time, but the fix needs to go into the archive this week) is directly dependent on successful testing by affected users.
Please report successes or failures at fixing the specific problem in this bug here. Please report any other problems as separate bugs.
Thanks in advance! |
Accepted into dapper-proposed, please go ahead with QA testing.
Tests should include:
* Verify that the installation hang is fixed (with the test ISOs that Colin provided)
* Install a few packages in dapper which use debconf, to check for regressions. |
|
| 2007-08-10 10:03:18 |
Colin Watson |
debconf: status |
Fix Committed |
Fix Released |
|
| 2007-08-10 10:15:16 |
Martin Pitt |
debconf: status |
Fix Released |
Fix Committed |
|
| 2007-08-10 10:15:16 |
Martin Pitt |
debconf: statusexplanation |
Accepted into dapper-proposed, please go ahead with QA testing.
Tests should include:
* Verify that the installation hang is fixed (with the test ISOs that Colin provided)
* Install a few packages in dapper which use debconf, to check for regressions. |
|
|
| 2007-09-19 11:07:10 |
Martin Pitt |
debconf: status |
Fix Committed |
Fix Released |
|
| 2009-12-05 06:58:38 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/dapper-updates/debconf |
|
