Boot takes ten minutes after upgrade to Karmic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Using Jaunty I had my system set up to use a swap file instead of a swap partition. I added 'resume=
Booting without 'quiet splash' the system appears to hang after these messages are printed to the screen:
[ 7.608079] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 7.628028] sd 4:0:0:1: [sdc] Attached SCSI removable disk
[ 7.648025] sd 4:0:0:2: [sdd] Attached SCSI removable disk
[ 7.688020] sd 4:0:0:3: [sde] Attached SCSI removable disk
However, if you wait for about ten minutes, the boot process continues with this message printed after the above:
[ 644.440694] PM: Starting manual resume from disk
And then things continue on from there. Again, this is on an upgrade from 9.04 to 9.10, and using kernel 2.6.31.14.27
ProblemType: Bug
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'V8237'/'VIA 8237 with ALC658D at 0xc000, irq 22'
Mixer name : 'Realtek ALC658D'
Components : 'AC97a:414c4781'
Controls : 45
Simple ctrls : 27
Date: Mon Nov 9 17:20:13 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: resume=
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
MachineType: Compaq Presario 061 PP150AA-ABA SR1303WM NA510
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux
Uname: Linux 2.6.31-14-generic i686
WpaSupplicantLog:
dmi.bios.date: 06/06/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 3.15
dmi.board.name: Kelut
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 2.02
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: PP150AA-ABA SR1303WM NA510
dmi.product.
dmi.sys.vendor: Compaq Presario 061
Adding boot messages from when I first encountered the problem