Takes over 2 minutes to boot up.

Bug #975125 reported by oshirowanen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debian-installer (Ubuntu)
Triaged
Low
Unassigned

Bug Description

I've installed Ubuntu 12.04 Beta 2 for testing purposes.

When I power on the computer now, I get the following message beneath the ubuntu logo:

Waiting for network configuration

About a minute later I get this message:

Waiting up to 60 more seconds for network configuration

About a minute later I get this message:

Booting system without full network configuation

About 10 seconds later I get the ubuntu login screen.

Why is this happening?

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
Uname: Linux 3.2.0-21-generic i686
ApportVersion: 2.0-0ubuntu4
Architecture: i386
CurrentDmesg: [ 176.870560] ISOFS: changing to secondary root
Date: Fri Apr 6 14:01:12 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
MachineType: TOSHIBA TECRA A2
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic root=UUID=65d903c3-0be6-4617-a5a8-46bec2c13217 ro splash quiet vt.handoff=7
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic root=UUID=65d903c3-0be6-4617-a5a8-46bec2c13217 ro splash quiet vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2005
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.40
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.40:bd04/25/2005:svnTOSHIBA:pnTECRAA2:pvrPTA20E-00P01YEN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: TECRA A2
dmi.product.version: PTA20E-00P01YEN
dmi.sys.vendor: TOSHIBA

Revision history for this message
oshirowanen (oshirowanen) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

Not a plymouth bug; plymouth is just the messenger. Reassigning to ifupdown.

Is this bug reproducible on every boot, or only on the first boot after install?

What Ubuntu image did you use to install this system?

Please attach the file /etc/network/interfaces from the affected system, and show the output of the following two commands:

 ls -l /etc/network/if-up.d/
 ls -l /run/network/

affects: plymouth (Ubuntu) → ifupdown (Ubuntu)
Changed in ifupdown (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
oshirowanen (oshirowanen) wrote :

Thanks for reassigning.

Yes, this happened on first boot after installation, and it continues to happen on all boots after that too.

I used the ubuntu 12.04 beta 2 mini cd iso to install a command line system after which I installed the ubuntu-desktop using tasksel.

I've attached the /etc/network/interfaces file.

Here are the outputs requested:

oshirowanen@ubuntu:~$ ls -l /etc/network/if-up.d/
total 20
-rwxr-xr-x 1 root root 525 Mar 29 21:37 000resolvconf
-rwxr-xr-x 1 root root 892 Oct 18 04:54 avahi-autoipd
-rwxr-xr-x 1 root root 431 Oct 18 04:54 avahi-daemon
-rwxr-xr-x 1 root root 1298 Oct 26 15:14 ntpdate
-rwxr-xr-x 1 root root 1286 Mar 29 17:26 upstart
lrwxrwxrwx 1 root root 32 Mar 16 14:02 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh
oshirowanen@ubuntu:~$

oshirowanen@ubuntu:~$ ls -l /run/network/
total 4
-rw-r--r-- 1 root root 6 Apr 6 19:10 ifstate
-rw-r--r-- 1 root root 0 Apr 6 19:05 ifup.eth1
-rw-r--r-- 1 root root 0 Apr 6 19:05 ifup.lo
oshirowanen@ubuntu:~$

Not sure if the next bit of info is important or not, but I installed the installation using an ethernet cable, after the installation on first boot, I removed the ethernet cable and used the wireless.

Revision history for this message
oshirowanen (oshirowanen) wrote :

I just notice this bug:

https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/37285

So I tried booting with the ethernet cable plugged in and it booted extremely quickly. Tried it without the ethernet cable with wifi enable, and it took over 2 minutes to boot with the same messages as I described earlier. Tried this a couple of times and each time the ethernet cable if plugged in, it boots very fast, and each time the cable is not plugged in, with wifi enabled or disabled, it takes over 2 minutes too boot up.

So it seems to be the same bug, but with different messages.

Revision history for this message
Steve Langasek (vorlon) wrote :

Ok, thanks. This isn't an ifupdown bug either then; it's working as designed, which is that if there's a network interface marked 'auto' in /etc/network/interfaces, the boot waits to give it a chance to come up before proceeding to start services.

This is not an issue when installing from the desktop CD, or when installing a server system using the same network interface that will be used post-install; it's specific to the method you used for installing (booting mini CD, installing over ethernet, then switching to wifi).

So to fix this issue, you should delete the eth0 lines from /etc/network/interfaces.

I'm reassigning this bug to debian-installer. Maybe it should be configurable whether the config for the interface used for installation gets copied to the installed system.

affects: ifupdown (Ubuntu) → debian-installer (Ubuntu)
Changed in debian-installer (Ubuntu):
importance: Medium → Low
status: Incomplete → Triaged
Revision history for this message
Clint Byrum (clint-fewbar) wrote : Re: [Bug 975125] [NEW] Takes over 2 minutes to boot up.

Excerpts from Launchpad Bug Tracker's message of Fri Apr 06 16:01:51 UTC 2012:
> You have been subscribed to a public bug:
>
> I've installed Ubuntu 12.04 Beta 2 for testing purposes.
>
> When I power on the computer now, I get the following message beneath
> the ubuntu logo:
>
> Waiting for network configuration
>
> About a minute later I get this message:
>
> Waiting up to 60 more seconds for network configuration
>
> About a minute later I get this message:
>
> Booting system without full network configuation
>
> About 10 seconds later I get the ubuntu login screen.
>
> Why is this happening?
>

Hi, perhaps check /etc/network/interfaces. The system waits for those
network interfaces to be up before moving on to the rest of the boot.
If this is a mobile system, you'll be better served by configuring the
interfaces using NetworkManager. If you don't want to use NetworkManager,
you can lower the timeout in /etc/init/failsafe.conf, but this may mean
that services designed to be started after networking is up will not
work properly.

> ProblemType: Bug
> DistroRelease: Ubuntu 12.04
> Package: plymouth 0.8.2-2ubuntu28
> ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
> Uname: Linux 3.2.0-21-generic i686
> ApportVersion: 2.0-0ubuntu4
> Architecture: i386
> CurrentDmesg: [ 176.870560] ISOFS: changing to secondary root
> Date: Fri Apr 6 14:01:12 2012
> DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
> MachineType: TOSHIBA TECRA A2
> PccardctlIdent:
> Socket 0:
> no product info available
> PccardctlStatus:
> Socket 0:
> no card
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic root=UUID=65d903c3-0be6-4617-a5a8-46bec2c13217 ro splash quiet vt.handoff=7
> ProcEnviron:
> LANGUAGE=en_GB:en
> TERM=xterm
> LANG=en_GB.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic root=UUID=65d903c3-0be6-4617-a5a8-46bec2c13217 ro splash quiet vt.handoff=7
> SourcePackage: plymouth
> TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 04/25/2005
> dmi.bios.vendor: TOSHIBA
> dmi.bios.version: Version 1.40
> dmi.board.name: Portable PC
> dmi.board.vendor: TOSHIBA
> dmi.board.version: Version A0
> dmi.chassis.asset.tag: 0000000000
> dmi.chassis.type: 10
> dmi.chassis.vendor: TOSHIBA
> dmi.chassis.version: Version 1.0
> dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.40:bd04/25/2005:svnTOSHIBA:pnTECRAA2:pvrPTA20E-00P01YEN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
> dmi.product.name: TECRA A2
> dmi.product.version: PTA20E-00P01YEN
> dmi.sys.vendor: TOSHIBA
>
> ** Affects: ifupdown (Ubuntu)
> Importance: Medium
> Status: Incomplete
>
>
> ** Tags: apport-bug i386 precise

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.