Boot pauses for 2 minutes after upgrade to wily

Bug #1500046 reported by Tony Middleton
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Since upgrade to wily the boot process pauses for two minutes before continuing.

systemd-analyse shows

Startup finished in 16.356s (firmware) + 2.898s (loader) + 2min 46.836s (kernel) + 16.298s (userspace) = 3min 22.389s

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-11-generic 4.2.0-11.13
ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
Uname: Linux 4.2.0-11-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: tony 2547 F.... pulseaudio
 /dev/snd/controlC0: tony 2547 F.... pulseaudio
Date: Sat Sep 26 16:17:33 2015
HibernationDevice: RESUME=UUID=925ed755-51a9-4968-ab9d-1a8c4c0cc93c
InstallationDate: Installed on 2015-06-12 (106 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic root=UUID=f32dfa71-d154-4f81-9515-bef34b96bc2a ro nomdmonddf nomdmonisw
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-11-generic N/A
 linux-backports-modules-4.2.0-11-generic N/A
 linux-firmware 1.148
RfKill:

SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A85X-UP4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/31/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A85X-UP4:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Tony Middleton (ximera) wrote :
Revision history for this message
Tony Middleton (ximera) wrote :

CurrentDmesg.txt shows where the problem occurs.

[ 3.031482] random: nonblocking pool is initialized
[ 3.055042] clocksource: Switched to clocksource tsc
[ 121.818788] md: linear personality registered for level -1
[ 121.821422] md: multipath personality registered for level -4
[ 121.823927] md: raid0 personality registered for level 0

The clocksource line is the last showing on the screen during the pause.

Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Tony Middleton (ximera) wrote :

Maybe same as

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308264

however the tpm_tis.force=1 fix mentioned has no effect.

penalvch (penalvch)
tags: added: bios-outdated-f3
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Tony Middleton (ximera) wrote :

I will update BIOS as requested but I won't be able to do that for a couple of days.

In the meantime I must apologise as I haven't mentioned that there is another delay of about 40s as shown here

[ 122.281863] md: raid4 personality registered for level 4
[ 122.287699] md: raid10 personality registered for level 10
[ 122.326579] EXT4-fs (md3): mounted filesystem with ordered data mode. Opts: (null)
[ 167.081506] systemd[1]: Failed to insert module 'kdbus': Function not implemented
[ 167.099649] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
[ 167.099847] systemd[1]: Detected architecture x86-64.
[ 167.101419] systemd[1]: Set hostname to <rose>.

On the screen there are a number of messages about running scripts in /scripts the last one before the delay being
/scripts/init-bottom

Also, today I took out LVM temporarily and both of these problems went away and I booted in 18s. When I put LVM back the problems came back.

Revision history for this message
Tony Middleton (ximera) wrote :

Managed to try updating after all. I tried both the F3 and F4 BIOS and both still had both of the delays mentioned above. Here is the output requested on the F3

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
F3
02/05/2013

I'm currently on F3 but both F3 & F4 cause a new problem in that my USB keyboard/mouse isn't recognised during BIOS and GRUB. Had to borrow a PS/2 and if I can't find a solution will need to revert to F2.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Tony Middleton (ximera) wrote :

I recently removed an LVM snapshot that had been in place for some time. When I next rebooted the delay problem had gone away.

It seems this is a known problem. There are a number of bugs where root is on LVM and the delay causes boot to fail. I don't have root on LVM so boot did not fail but was unreasonably slow.

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.