During first boot system is extreamly slow

[John Vivirito]

During first boot system is extreamly slow menus, mouse, windows open/close

After a reboot system is normal again.
This started happening after the upgrade to 2.6.32-10 and continues with *-11
I'm not exactly sure what package this falls under but i saw it after kernel update.
It is almost unusably slow, You can use it but it takes forever for even a terminal window to open.

ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gnomefreak 1995 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Live'/'SB Live! Value [CT4780] (rev.7, serial:0x80221102) at 0xece0, irq 16'
   Mixer name : 'TriTech TR28602'
   Components : 'AC97a:54524123'
   Controls : 216
   Simple ctrls : 38
Date: Mon Jan 25 12:03:25 2010
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=cd9cb0b9-ffbd-45f5-9c42-016f6f84ea16
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 002 Device 002: ID 03f0:c002 Hewlett-Packard PhotoSmart 7800 series
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 09da:0006 A4 Tech Co., Ltd Optical Mouse WOP-35 / Trust 450L Optical Mouse
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Computer Corporation OptiPlex GX400
NonfreeKernelModules: nvidia
Package: linux-image-2.6.32-11-generic 2.6.32-11.15
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-11-generic root=UUID=827d343c-f880-4c45-943d-8fa7e3cec73b ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=C
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.28
Reproducible: Yes
RfKill:

SourcePackage: linux
TestedUpstream: No
Uname: Linux 2.6.32-11-generic i686
dmi.bios.date: 10/05/2001
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A05
dmi.board.name: OptiPlex GX400
dmi.board.vendor: Dell Computer Corporation
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComputerCorporation:bvrA05:bd10/05/2001:svnDellComputerCorporation:pnOptiPlexGX400:pvr:rvnDellComputerCorporation:rnOptiPlexGX400:rvr:cvnDellComputerCorporation:ct6:cvr:
dmi.product.name: OptiPlex GX400
dmi.sys.vendor: Dell Computer Corporation

[Jeremy Foshee (jeremyfoshee)]

John,
     During the first boot, the system is profiling the hardware for the very first time. I am informed by reliable resources that this will not likely change. As such, I am closing this bug as invalid.

-JFo

[John Vivirito (gnomefreak)]

Jeremy, ok i can see how that would work but since the hardware profiling would have to happen on "every" start/reboot wouldnt it always be slow and not just on first cold boot.

1. boot PC at 6:00am == very slow
2. reboot at 6:03am == normal
3. all reboots are normal
4. turn system off for say 1 hour
5. boot system == very slow
6. reboot == normal
and the cycle continues

[John Vivirito (gnomefreak)]

I opened this bug back up, since i am waiting for a reply

[Iain Buclaw (iainb)]

The "hardware profiling" you are referring to I presume is ureadahead. No, this doesn't profile on every start. It is my understanding that it periodically updates the cache file once every month, and only forces a re-profiling when installing/upgrading certain system components.

Is the cycle that you mention persistent/reproducible?

Regards
Iain

[Iain Buclaw (iainb)]

I also notice that this is in your BootMesg attachment.

NVRM: The NVIDIA GeForce FX 5200 GPU installed in this system is
NVRM: supported through the NVIDIA 173.14.xx Legacy drivers. Please
NVRM: visit http://www.nvidia.com/object/unix.html for more
NVRM: information. The 190.53 NVIDIA driver will ignore
NVRM: this GPU. Continuing probe...
NVRM: ignoring the legacy GPU 02:09.0
nvidia: probe of 0000:02:09.0 failed with error -1

Have you tried uninstalling the 190 driver and sticking with the 173 Nvidia driver? Or even using the Nouveau driver instead?

[John Vivirito (gnomefreak)]

On 03/06/2010 07:36 PM, Iain Bucław wrote:
> The "hardware profiling" you are referring to I presume is
> ureadahead. No, this doesn't profile on every start. It is my
> understanding that it periodically updates the cache file once every
> month, and only forces a re-profiling when installing/upgrading
> certain system components.
>
> Is the cycle that you mention persistent/reproducible?
>
> Regards Iain
>
This is reproducible on every first boot even if system was shut down
for a couple of hours.
I am not sure what system updates that would cause this but after
updates i restart and it works fine, it is just the first cold boot

> I also notice that this is in your BootMesg attachment.
>
> NVRM: The NVIDIA GeForce FX 5200 GPU installed in this system is
> NVRM: supported through the NVIDIA 173.14.xx Legacy drivers. Please
> NVRM: visit http://www.nvidia.com/object/unix.html for more NVRM:
> information. The 190.53 NVIDIA driver will ignore NVRM: this GPU.
> Continuing probe... NVRM: ignoring the legacy GPU 02:09.0 nvidia:
> probe of 0000:02:09.0 failed with error -1
>
> Have you tried uninstalling the 190 driver and sticking with the 173
> Nvidia driver? Or even using the Nouveau driver instead?
Yes i have tested with other drivers including Nouveau(replaced "nv"
IIRC) but yes have tried all other drivers and found no change.

--
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

"How can i get lost, if i have no where to go"
    -- Metallica from Unforgiven III

[John Vivirito (gnomefreak)]

No longer happens with the 2.6.35* kernel

gnomefreak@development:~$ uname -a
Linux development 2.6.35-5-generic #6-Ubuntu SMP Mon Jun 21 21:33:48 UTC 2010 i686 GNU/Linux
gnomefreak@development:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu maverick (development branch)
Release: 10.10
Codename: maverick

[John Vivirito (gnomefreak)]

I have to assume either the Kernel fixed this on the 2.6.35* or another app fixed this bug.

[John Vivirito (gnomefreak)]

It happens once in a while with:

gnomefreak@Development:~$ lsb_release -a && uname -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu maverick (development branch)
Release: 10.10
Codename: maverick
Linux Development 2.6.35-12-generic #17-Ubuntu SMP Mon Jul 26 18:09:52 UTC 2010 i686 GNU/Linux

[John Vivirito (gnomefreak)]

Jeremy,
Are you seeing this bug?
Please do not change status of bug without giving a reason why.

[John Vivirito (gnomefreak)]

With my new system this is no longer an issue. i have to assume it was memory related since it only had 256mb