Re: Sloooow Boot [was NFS Mounting oddity...]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2011-12-05 at 19:42 +0000, Arthur Dent wrote:
> On Mon, 2011-12-05 at 18:08 +0530, Soham Chakraborty wrote:

snip

> 
> So the long boot times (c. 2 mins) seem to be random, given no changes
> in configuration.
> 
> I looked at dmesg. I am no expert in what dmesg tells me, but here is
> the last few lines of one of the long boots:
> 
> ===============8<====================================
> [root@localhost ~]# dmesg
> [       snip ]
> [   32.248789] e1000e 0000:00:19.0: em1: 10/100 speed: disabling TSO
> [   32.248955] ADDRCONF(NETDEV_CHANGE): em1: link becomes ready
> [   42.354015] em1: no IPv6 routers present
> [   90.858903] SELinux: initialized (dev 0:21, type nfs4), uses genfs_contexts
> [   90.863622] SELinux: initialized (dev 0:22, type nfs4), uses genfs_contexts
> [   90.867429] SELinux: initialized (dev 0:23, type nfs4), uses genfs_contexts
> [   90.868787] SELinux: initialized (dev 0:24, type nfs4), uses genfs_contexts
> [   90.872920] SELinux: initialized (dev 0:22, type nfs4), uses genfs_contexts
> [   90.877188] SELinux: initialized (dev 0:25, type nfs4), uses genfs_contexts
> [   90.878883] mount[998]: mount.nfs: /mnt/NFSmark is busy or already mounted
> [   90.887451] SELinux: initialized (dev 0:22, type nfs4), uses genfs_contexts
> [   90.927896] SELinux: initialized (dev 0:21, type nfs4), uses genfs_contexts
> [   90.932400] SELinux: initialized (dev 0:22, type nfs4), uses genfs_contexts
> [   92.714872] [drm:drm_debugfs_create_files] *ERROR* Cannot create /sys/kernel/debug/dri/channel\xfffffff0i\xffffff80]\xffffffc0\x03/3
> [   95.940096] [drm:drm_debugfs_create_files] *ERROR* Cannot create /sys/kernel/debug/dri/channel\xffffffe9i\xffffff80]\xffffffc0\x03/3
> [root@localhost ~]# 
> 
> ===============8<====================================
> On the successful boots dmesg ends with the "no IPv6 routers present"
> line at around 44s.
> 
> What is this telling me and how do I fix it?

Dumb question - but how do I read the above dmesg output?
i.e. does the timestamp refer to the time that task started or the time
it completed?

I guess what I am asking is wast it the "em1: no IPv6 routers present"
that took 48 seconds or was it the SELinux line that was the culprit?

Apologies for asking such an elementary question but google turned up
lots of stuff about dmesg, but no answer to this specific question.

And further... How do I fix it!

Thanks again for the help so far...

Mark
 

Attachment: signature.asc
Description: This is a digitally signed message part

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux