LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   It is very slow to enter the desktop (https://www.linuxquestions.org/questions/linux-newbie-8/it-is-very-slow-to-enter-the-desktop-742613/)

zcbenz 07-24-2009 10:30 PM
It is very slow to enter the desktop
 
I use ubuntu 9.04 on a laptop (hp 6530s).
Ubuntu boots well,but after I login,it takes about 30s to enter the desktop entirely.

Here is part of dmesg results,which I think may be the cause:
Code:
[  11.210123] type=1505 audit(1248488509.729:9): operation="profile_load" name="/usr/sbin/tcpdump" name2="default" pid=2190
[  18.708492] vboxdrv: Trying to deactivate the NMI watchdog permanently...
[  18.708526] vboxdrv: Successfully done.
Code:
[  28.568078] wlan0: direct probe to AP 00:74:04:ee:28:3d try 3
[  28.768055] wlan0: direct probe to AP 00:74:04:ee:28:3d timed out
[  46.168386] CPU0 attaching NULL sched-domain.
[  46.168390] CPU1 attaching NULL sched-domain.
[  46.172114] CPU0 attaching sched-domain:
[  46.172119]  domain 0: span 0-1 level MC
[  46.172124]  groups: 0 1
[  46.172132] CPU1 attaching sched-domain:
[  46.172136]  domain 0: span 0-1 level MC
[  46.172140]  groups: 1 0
It seems that vbox service starts slowly and something related to CPU is wrong,can someone help me solve it?

Sorry for my bad English

GrapefruiTgirl 08-14-2009 09:54 PM
Your English is just fine, don't worry ;)

It appears that the delay you are experiencing, based on the output you provided above, might be in part due to the failed attempt(s) at probing the wireless equipment. However, there's a 10-second chunk of time missing between the two sections of `dmesg` that you posted.

It'd be better if you could post *more* of the dmesg: include the area in between those two pieces above; what you did post covers a total of 35 seconds, but we need to see all of it to make a better estimate of what's going on.

Sasha

zcbenz 08-15-2009 03:11 AM
Thanks to your reply.
It has been so long that I nearly forget this post:)Though the problem remains the same,and even worse.But the good message is that I have got used to it.

Here is the detailed dmesg results:
Code:
[    6.302636] phy0: Selected rate control algorithm 'iwl-agn-rs'
[    6.801695] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
[    6.801705] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    6.801803] HDA Intel 0000:00:1b.0: setting latency timer to 64
[    7.116582] Synaptics Touchpad, model: 1, fw: 6.3, id: 0x1a0b1, caps: 0xa04711/0x200000
[    7.156701] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input9
[    7.860008] hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x016f000c
[    8.065375] Adding 497972k swap on /dev/sda10.  Priority:-1 extents:1 across:497972k
[    8.589756] EXT4 FS on sda7, internal journal on sda7:8
[    8.643966] lp: driver loaded but no devices found
[  15.053254] EXT4-fs: barriers enabled
[  15.053456] kjournald2 starting.  Commit interval 5 seconds
[  15.053842] EXT4 FS on sda11, internal journal on sda11:8
[  15.053845] EXT4-fs: delayed allocation enabled
[  15.053848] EXT4-fs: file extents enabled
[  15.063963] EXT4-fs: mballoc enabled
[  15.063966] EXT4-fs: mounted filesystem with ordered data mode.
[  15.214591] EXT4-fs: barriers enabled
[  15.214865] kjournald2 starting.  Commit interval 5 seconds
[  15.215156] EXT4 FS on sda8, internal journal on sda8:8
[  15.215160] EXT4-fs: delayed allocation enabled
[  15.215163] EXT4-fs: file extents enabled
[  15.216588] EXT4-fs: mballoc enabled
[  15.216591] EXT4-fs: mounted filesystem with ordered data mode.
[  15.280471] EXT4-fs: barriers enabled
[  15.280740] kjournald2 starting.  Commit interval 5 seconds
[  15.281006] EXT4 FS on sda9, internal journal on sda9:8
[  15.281010] EXT4-fs: delayed allocation enabled
[  15.281012] EXT4-fs: file extents enabled
[  15.281082] EXT4-fs: mballoc enabled
[  15.281086] EXT4-fs: mounted filesystem with ordered data mode.
[  24.498964] NET: Registered protocol family 24
[  27.958834] [drm] Initialized drm 1.1.0 20060810
[  27.963661] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[  27.963666] pci 0000:00:02.0: setting latency timer to 64
[  27.963907] pci 0000:00:02.0: irq 2295 for MSI/MSI-X
[  27.963987] [drm] Initialized i915 1.6.0 20080730 on minor 0
[  27.965387] [drm:i915_setparam] *ERROR* unknown parameter 4
[  29.521982] sky2 eth0: enabling interface
[  29.522182] ADDRCONF(NETDEV_UP): eth0: link is not ready
[  29.522836] iwlagn 0000:02:00.0: firmware: requesting iwlwifi-5000-1.ucode
[  29.746947] Registered led device: iwl-phy0:radio
[  29.746974] Registered led device: iwl-phy0:assoc
[  29.746999] Registered led device: iwl-phy0:RX
[  29.747022] Registered led device: iwl-phy0:TX
[  30.244062] iwlagn: Error sending REPLY_ADD_STA: time out after 500ms.
[  30.249059] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  31.212568] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
[  31.212737] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  41.596042] eth0: no IPv6 routers present
[  60.675509] CPU0 attaching NULL sched-domain.
[  60.675514] CPU1 attaching NULL sched-domain.
[  60.692450] CPU0 attaching sched-domain:
[  60.692453]  domain 0: span 0-1 level MC
[  60.692456]  groups: 0 1
[  60.692461] CPU1 attaching sched-domain:
[  60.692463]  domain 0: span 0-1 level MC
[  60.692465]  groups: 1 0
[  61.376198] CPU0 attaching NULL sched-domain.
[  61.376202] CPU1 attaching NULL sched-domain.
[  61.376642] CPU0 attaching sched-domain:
[  61.376647]  domain 0: span 0-1 level MC
[  61.376652]  groups: 0 1
[  61.376660] CPU1 attaching sched-domain:
[  61.376664]  domain 0: span 0-1 level MC
[  61.376668]  groups: 1 0


All times are GMT -5. The time now is 09:41 AM.