FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 05-26-2011, 09:04 PM
Ian Malone
 
Default very long boot time in fedora 15

Hi,

I'm trying to work out why Fedora 15 takes an incredibly long time to
start on this machine (Intel Core 2 Duo T5500, 1GB RAM laptop),
booting takes several minutes as opposed to F13. No custom modules,
just stock Fedora, intel wireless and graphics, used preupgrade to go
F13 to F15. I can try and provide more information, but I'm not sure
where to start with this, any ideas? Some things that might be
relevant below.

dmesg, at the 'gap':
[ 43.006805] sky2 0000:02:00.0: eth0: enabling interface
[ 43.010915] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 43.044360] iwl3945 0000:06:00.0: loaded firmware version 15.32.2.9
[ 43.111086] iwl3945 0000:06:00.0: Error setting Tx power (-5).
[ 43.132498] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 344.645061] RPC: Registered udp transport module.
[ 344.645066] RPC: Registered tcp transport module.
[ 344.645069] RPC: Registered tcp NFSv4.1 backchannel transport module.

The point in /var/log/boot.log where it stops:
Starting LSB: Port reservation utility...
Started LSB: Port reservation utility.
Started LSB: processor frequency scaling support.
**** <- several minutes spent here
Starting LSB: Bring up/down networking ESC[1;31mfailedESC[0m, see
'systemctl status network.service' for details.
Starting SYSV: The rpcbind utility is a server that converts RPC
program numbers into universal addresses. It must be running on the
host to be able to make RPC calls on a server on that machine....

Unfortunately those instructions aren't very informative:
# systemctl status network.service
network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network)
Active: failed since Thu, 26 May 2011 21:29:35 +0100; 7min ago
Process: 882 ExecStart=/etc/rc.d/init.d/network start (code=killed,
signal=TERM)
CGroup: name=systemd:/system/network.service

Doesn't explain why it waits for networking at this point, nor why it
attempts (or seems to attempt) to start several services after this,
which seems contrary to the way systemd is supposed to work:
Starting LSB: Starts the NFSv4 id mapping daemon...
Starting LSB: Start up the NFS file locking sevice...
Starting LSB: The CUPS scheduler...
Starting LSB: Start and stop the MD software RAID monitor...
Starting LSB: Mount and unmount network filesystems....
Starting LSB: Starts the RPCSEC GSS client daemon...
Started LSB: Start and stop the MD software RAID monitor.
Started LSB: Starts the RPCSEC GSS client daemon.
Started LSB: Mount and unmount network filesystems..

etc., of course this might just be that it's not reporting these until
after the network.service fail.

Top ten in systemd-analyze, network doesn't appear at all:
$ systemd-analyze blame
15464ms fedora-sysinit-hack.service
14464ms var-lock.mount
14449ms var-run.mount
14047ms systemd-vconsole-setup.service
13680ms systemd-binfmt.service
13608ms media.mount
13149ms remount-rootfs.service
13142ms systemd-remount-api-vfs.service
13134ms hwclock-load.service
9852ms proc-sys-fs-binfmt_misc.mount

--
imalone
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 05-26-2011, 09:45 PM
Rahul Sundaram
 
Default very long boot time in fedora 15

On 05/27/2011 02:34 AM, Ian Malone wrote:
> Hi,
>
> I'm trying to work out why Fedora 15 takes an incredibly long time to
> start on this machine (Intel Core 2 Duo T5500, 1GB RAM laptop),
> booting takes several minutes as opposed to F13. No custom modules,
> just stock Fedora, intel wireless and graphics, used preupgrade to go
> F13 to F15. I can try and provide more information, but I'm not sure
> where to start with this, any ideas?

I recommend filing a bug report against systemd and we can take it from
there.

Rahul

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 05-26-2011, 10:19 PM
Ian Malone
 
Default very long boot time in fedora 15

On 26 May 2011 22:45, Rahul Sundaram <metherid@gmail.com> wrote:
> On 05/27/2011 02:34 AM, Ian Malone wrote:
>> Hi,
>>
>> I'm trying to work out why Fedora 15 takes an incredibly long time to
>> start on this machine (Intel Core 2 Duo T5500, 1GB RAM laptop),
>> booting takes several minutes as opposed to F13. No custom modules,
>> just stock Fedora, intel wireless and graphics, used preupgrade to go
>> F13 to F15. I can try and provide more information, but I'm not sure
>> where to start with this, any ideas?
>
> I recommend filing a bug report against systemd and we can take it from
> there.
>

Okay, it's in.
https://bugzilla.redhat.com/show_bug.cgi?id=708207

--
imalone
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 05-27-2011, 04:36 PM
"R. G. Newbury"
 
Default very long boot time in fedora 15

On 05/26/2011 05:04 PM, Ian Malone<ibmalone@gmail.com> wrote

> I'm trying to work out why Fedora 15 takes an incredibly long time to
> start on this machine (Intel Core 2 Duo T5500, 1GB RAM laptop),
> booting takes several minutes as opposed to F13. No custom modules,
> just stock Fedora, intel wireless and graphics, used preupgrade to go
> F13 to F15. I can try and provide more information, but I'm not sure
> where to start with this, any ideas? Some things that might be
> relevant below.
>
> dmesg, at the 'gap':
> [ 43.006805] sky2 0000:02:00.0: eth0: enabling interface
> [ 43.010915] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 43.044360] iwl3945 0000:06:00.0: loaded firmware version 15.32.2.9
> [ 43.111086] iwl3945 0000:06:00.0: Error setting Tx power (-5).
> [ 43.132498] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 344.645061] RPC: Registered udp transport module.
> [ 344.645066] RPC: Registered tcp transport module.
> [ 344.645069] RPC: Registered tcp NFSv4.1 backchannel transport module.

It *looks* like it is waiting for the link to become ready.

You could try using the iwlagn module instead of the iwl3945, to see if
that module reacts better. It is supposed to work with the 3945 chipset
iirc.

I would then try turning off ALL network services and dependencies of
those. and timing boot in that condition. Then timing startup of the
network with the wired NIC only, and then with the wireless NIC only,
etc. etc.

It *could* be that the delay is some other module which actually depends
on network services, such as an NFS or samba share etc..


Geoff


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 05-27-2011, 04:40 PM
Ian Malone
 
Default very long boot time in fedora 15

On 27 May 2011 17:36, R. G. Newbury <newbury@mandamus.org> wrote:
> On 05/26/2011 05:04 PM, Ian Malone<ibmalone@gmail.com> wrote
>
>> I'm trying to work out why Fedora 15 takes an incredibly long time to
>> start on this machine (Intel Core 2 Duo T5500, 1GB RAM laptop),
>> booting takes several minutes as opposed to F13. No custom modules,
>> just stock Fedora, intel wireless and graphics, used preupgrade to go
>> F13 to F15. I can try and provide more information, but I'm not sure
>> where to start with this, any ideas? Some things that might be
>> relevant below.
>>
>> dmesg, at the 'gap':
>> [ * 43.006805] sky2 0000:02:00.0: eth0: enabling interface
>> [ * 43.010915] ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [ * 43.044360] iwl3945 0000:06:00.0: loaded firmware version 15.32.2.9
>> [ * 43.111086] iwl3945 0000:06:00.0: Error setting Tx power (-5).
>> [ * 43.132498] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>> [ *344.645061] RPC: Registered udp transport module.
>> [ *344.645066] RPC: Registered tcp transport module.
>> [ *344.645069] RPC: Registered tcp NFSv4.1 backchannel transport module.
>
> It *looks* like it is waiting for the link to become ready.
>
> You could try using the iwlagn module instead of the iwl3945, to see if
> that module reacts better. It is supposed to work with the 3945 chipset
> iirc.
>
> I would then try turning off ALL network services and dependencies of
> those. and timing boot in that condition. Then timing startup of the
> network with the wired NIC only, and then with the wireless NIC only,
> etc. etc.
>
> It *could* be that the delay is some other module which actually depends
> on network services, such as an NFS or samba share etc..
>

Per https://bugzilla.redhat.com/show_bug.cgi?id=708207 what's actually
happening is startup is waiting while the wireless attempts to connect
to every NM generated ifcfg-Auto_X on the system, and in fact times
out before it gets through them all. Presumably something is waiting
on this to finish that's not actually needed, but the immediate
problem is solved by cleaning them out.

--
imalone
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 

Thread Tools




All times are GMT. The time now is 08:38 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org