Manual partition install hangs for Kubuntu Netbook Karmic Alpha 3 candidate

[Scott Kitterman]

Binary package hint: ubiquity

Installer hangs at updating initramfs stage (twice) while kdeui sucks up 100% CPU. Partition that I am attempting to install into is ~8GB on a Dell mini 10v.

The last bit of /var/log/messages:

Jul 22 10:08:27 ubuntu ubiquity: Processing triggers for man-db ...
Jul 22 10:08:31 ubuntu ubiquity: Setting up b43-fwcutter (1:012-1) ...
Jul 22 10:08:36 ubuntu ubiquity:
Jul 22 10:08:36 ubuntu ubiquity: Setting up dkms (2.0.21.1-0ubuntu3) ...
Jul 22 10:08:36 ubuntu ubiquity:
Jul 22 10:08:36 ubuntu ubiquity: Setting up bcmwl-kernel-source (5.10.91.9+bdcom-0ubuntu4) ...
Jul 22 10:08:37 ubuntu ubiquity: First Installation: checking all kernels...
Jul 22 10:08:37 ubuntu ubiquity: Directory for kernel 2.6.31-3-generic found in /lib/modules
Jul 22 10:08:37 ubuntu ubiquity: Adding Module to DKMS build system
Jul 22 10:08:37 ubuntu ubiquity: Doing initial module build
Jul 22 10:08:59 ubuntu ubiquity: Installing initial module
Jul 22 10:09:03 ubuntu ubiquity: Done.
Jul 22 10:09:03 ubuntu ubiquity: update-initramfs: deferring update (trigger activated)
Jul 22 10:09:03 ubuntu ubiquity:
Jul 22 10:09:03 ubuntu ubiquity: Setting up fakeroot (1.12.4ubuntu1) ...
Jul 22 10:09:03 ubuntu ubiquity: update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode.
Jul 22 10:09:04 ubuntu ubiquity:
Jul 22 10:09:04 ubuntu ubiquity: Setting up patch (2.5.9-5) ...
Jul 22 10:09:04 ubuntu ubiquity: Processing triggers for initramfs-tools ...
Jul 22 10:09:04 ubuntu ubiquity: update-initramfs: Generating /boot/initrd.img-2.6.31-3-generic

From the output of ps -aux:

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 4933 0.0 0.1 3664 1040 ? S Jul22 0:00 hal-lock --interface org.freedesktop.Hal.Device.Storage --exclusive --run /usr/lib/ubiquity/bin/ubiquity kde_ui
ubuntu 4937 98.1 5.2 175360 53564 ? R Jul22 315:35 /usr/bin/python /usr/lib/ubiquity/bin/ubiquity kde_ui

strace doesn't seem to my untrained eye very helpful:

[00378fec] clock_gettime(CLOCK_MONOTONIC, {18495, 389494441}) = 0
[00816422] read(9, 0x8890158, 4096) = -1 EAGAIN (Resource temporarily unavailable)
[00378fec] clock_gettime(CLOCK_MONOTONIC, {18495, 389776320}) = 0
[00816422] read(9, 0x8890158, 4096) = -1 EAGAIN (Resource temporarily unavailable)
[00816422] poll([{fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=9, events=POLLIN}, {fd=15, events=POLLPRI}, {fd=15, events=POLLIN}, {fd=15, events=POLLPRI}, {fd=15, events=POLLIN}, {fd=15, events=POLLOUT}, {fd=15, events=POLLPRI}, {fd=15, events=POLLIN}, {fd=15, events=POLLOUT}, {fd=15, events=POLLPRI}], 12, 0) = 0 (Timeout)
[00378fec] clock_gettime(CLOCK_MONOTONIC, {18495, 390271635}) = 0
[00816422] read(9, 0x8890158, 4096) = -1 EAGAIN (Resource temporarily unavailable)
[00378fec] clock_gettime(CLOCK_MONOTONIC, {18495, 390539685}) = 0
[00816422] read(9, 0x8890158, 4096) = -1 EAGAIN (Resource temporarily unavailable)
[00816422] poll([{fd=5, events=POLLIN}, {fd=10, events=POLLIN}, {fd=9, events=POLLIN}, {fd=15, events=POLLPRI}, {fd=15, events=POLLIN}, {fd=15, events=POLLPRI}, {fd=15, events=POLLIN}, {fd=15, events=POLLOUT}, {fd=15, events=POLLPRI}, {fd=15, events=POLLIN}, {fd=15, events=POLLOUT}, {fd=15, events=POLLPRI}], 12, 0) = 0 (Timeout)
[00378fec] clock_gettime(CLOCK_MONOTONIC, {18495, 391017469}) = 0
[00816422] read(9, 0x8890158, 4096) = -1 EAGAIN (Resource temporarily unavailable)
[00378fec] clock_gettime(CLOCK_MONOTONIC, {18495, 391298231}) = 0
[00816422] read(9, 0x8890158, 4096) = -1 EAGAIN (Resource temporarily unavailable)

ProblemType: Bug
Architecture: i386
Date: Thu Jul 23 03:07:03 2009
DistroRelease: Ubuntu 9.10
LiveMediaBuild: Kubuntu-Netbook 9.10 "Karmic Koala" - Alpha i386 (20090722.1)
Package: ubiquity 1.99.1
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SourcePackage: ubiquity
Uname: Linux 2.6.31-3-generic i686

[Scott Kitterman (kitterman)]

Failed both manual and full disk. Free software only worked, so probably related to the broadcom install with Jockey.

[Mario Limonciello (superm1)]

Actually, why did you have *both* b43-fwcutter and bcmwl-kernel-source
getting installed? Normally it's one or the other. Since b43-fwcutter
tries to wget firmware, wouldn't surprise me if it was sitting there hanging
because it couldn't get ahold of firmware.

On Wed, Jul 22, 2009 at 23:42, Scott Kitterman <email address hidden> wrote:

> Failed both manual and full disk. Free software only worked, so
> probably related to the broadcom install with Jockey.
>
> --
> Manual partition install hangs for Kubuntu Netbook Karmic Alpha 3 candidate
> https://bugs.launchpad.net/bugs/403308
> You received this bug notification because you are a member of Ubuntu
> Installer Team, which is subscribed to ubiquity in ubuntu.
>

--
Mario Limonciello
<email address hidden>

[Scott Kitterman (kitterman)]

Good question. I didn't pick that manually, so I think that's a potential jockey issue.

[don hardaway (don-hardaway)]

I just tried to install kubuntu netbook on my Acer netbook that has 3 other Ubuntu OSes on it (all Karmic). When i go to manually partition the drive it does not show the other partitions --- on the sda drive without sda1, sda3 and sda6. I am using the RC candidate and this appears to be a big problem.

[Evan (ev)]

Scott, what's the contents of /var/cache/jockey/installed_packages when the install fails?

Thanks!

[Evan (ev)]

Don,
Your bug is different. Please file a new bug by first running the installer in debug mode (`ubiquity -d` from a konsole window) and then running `ubuntu-bug ubiquity` when you get to the manual partitioning page.

Thanks!

[Scott Kitterman (kitterman)]

Please file a new bug for that.

[Scott Kitterman (kitterman)]

I've reinstalled since I had this problem. I'll be doing some installs
this week and we'll see what I can dig up.

[Martin Pitt (pitti)]

However, your log shows that both the b43-fwcutter and the bcmwl-kernel-source packages finished installing. Neither driver downloads anything in their initramfs script. Also, drivers being busy wouldn't explain why kdeui takes 100% CPU. The strace of it looks like it's spinlocking on the apt pipe/socket, waiting for apt/update-initramfs to complete?

[Scott Kitterman (kitterman)]

I've done quite a number of manual partition installs for Natty without seeing this, so I'll call it fixed.