[btrfs] slow boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
upstart (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Bootup from power on to login prompt takes several minutes. In the bootchart I can see that there is sometimes a lot of IO while other times there is no cpu usage and no io. I cannot identify the reason for this. Several updates doesn't change anything. I assumed that upstart will boot rather fast.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.8.0-29-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: sk 2509 F...m pulseaudio
CRDA:
country DE:
(2400 - 2483 @ 40), (N/A, 20)
(5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
(5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
(5470 - 5725 @ 40), (N/A, 26), DFS
Date: Thu Aug 29 21:03:20 2013
HibernationDevice: RESUME=
InstallationDate: Installed on 2011-01-25 (946 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7501
MarkForUpload: True
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.106
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-05-03 (118 days ago)
dmi.bios.date: 09/02/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.5B1
dmi.board.
dmi.board.name: MS-7501
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-7501
dmi.product.
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
description: | updated |
tags: | added: bios-outdated-a1.c |
summary: |
- slow boot + [btrfs] slow boot |
Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.