[solved] [again] delay after booting

[chconnor]

Hi -

Recently (last couple/few weeks?) noticed a delay after booting: desktop appears, plasma widgets, etc, but everything is waiting for some background task for about 10s (e.g. mouse moves, my auto-hide plasma bars appear and disappear, etc, but can't do anything useful).

Normally my system tray contains the notifier, wicd, volume widget, and the recent-devices widget. I noticed that during the delay the notifier and the recent devices widgets were present, but not wicd or the audio.

I started tailing the wicd logs during this pause, but it didn't seem to be holding things up (at least as far as the log was indicating.) When I looked at syslog during the pause, nothing audio-related seemed to be a problem, but I noticed some suspect lines corresponding to the delay (9s in this case, between the 2nd and 3rd line):

Dec 28 11:36:26 mylinux avahi-daemon[882]: New relevant interface eth1.IPv6 for mDNS.
Dec 28 11:36:26 mylinux avahi-daemon[882]: Registering new address record for fe80::20c:eff:fea4:f8f3 on eth1.*.
Dec 28 11:36:35 mylinux kernel: [ 61.568017] eth1: no IPv6 routers present

When I boot with "ipv6.disable=1" on the kernel option line, the delay goes away (as do the log lines).

Any thoughts on that, or if i should file a bug report? It shouldn't hold the hold system up looking for routers, even if there was some misconfiguration with eth1, right?

Would this be an avahi issue or some other part of the system?

Thanks,
-c

[oshunluvr]

Re: [solved] [workaround] ~10s delay after booting, IPv6 apparently the cause?

This has been around awhile. I've been using that boot option for quite some time.

I think it's not actually a bug, but rather an issue with IPV6 not yet being supported by all DNS providers. I'm not trying to discourage you from attempting a bug post, just voicing my opinion.

[chconnor]

Re: [solved] [workaround] ~10s delay after booting, IPv6 apparently the cause?

Ok, thanks for that. I wonder why it only started happening recently for me (I used to disable IPv6 but wasn't in the last year or so) but that'll have to be chalked up to the mysteries of DNS, i suppose.

I guess the "bug" to me isn't that it takes a while to determine DNS info, or that my router doesn't speak v6, etc, but rather that the desktop experience is held hostage to that process. I.e., when my wireless is connecting i can still use the computer, but when this is happening everything has to wait as if the system can go no further until it sorts out whether or not the router supports IPv6 (I can't start apps, other system tray applications aren't started, etc etc).

Actually, now that I type that, I wonder if I can start apps or if it's just holding up the system tray... i always use custom hotkeys to start apps, but i'm not sure now if i even tried the actual menu. Maybe the hotkeys have to wait for DNS to get sorted out (a more minor "bug"), but not other stuff... I will sheepishly test that out. Let's assume it's just the system tray and I'll post again if not. :-)

Thanks,
-c

[chconnor]

~10s delay after booting

Hmmm, I take it all back.

Just saw the delay again, but this time with ipv6.disable=1... so I don't think it's the net after all... I sure thought I saw a clear correlation to that before, though. Anyway...

Can a moderator move this post, or should I post a new thread elsewhere?

Here's the recent syslog:

Dec 29 14:29:57 mylinux acpid: client connected from 886[0:0]
Dec 29 14:29:57 mylinux kernel: [ 70.353760] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
Dec 29 14:29:57 mylinux acpid: 1 client rule loaded
[at this point the systray is half-populated, as described]
Dec 29 14:30:03 mylinux pulseaudio[1840]: module.c: Failed to open module "module-x11-publish": file not found
Dec 29 14:30:03 mylinux pulseaudio[1840]: module.c: Failed to open module "module-x11-bell": file not found
Dec 29 14:30:09 mylinux acpid: client 886[0:0] has disconnected
Dec 29 14:30:09 mylinux kernel: [ 82.678807] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
Dec 29 14:30:09 mylinux acpid: client connected from 886[0:0]
Dec 29 14:30:09 mylinux acpid: 1 client rule loaded

Not sure if it's relevant/correct, but PID 886 (see log lines, above) seems to be X:
root 886 848 3 15671 53400 0 14:29 tty7 00:00:13 /usr/bin/X :0 vt7 -nr -nolisten tcp -auth /var/run/xauth/A:0-J00Zsa

I'll keep checking the log as this happens... any help is much appreciated.

-c

[dibl]

Re: ~10s delay after booting

Dec 29 14:29:57 mylinux kernel: [ 70.353760] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

I'm no framebuffer guru, but I agree that looks like the kind of thing (a video-related issue) that can hang the boot for a few seconds.

The little bit that I know about framebuffer-fiddling came from here: http://idyllictux.wordpress.com/

[chconnor]

Re: [solved] [again] delay after booting

Thanks for the link.

It does seem that i have some video issue related to that link you posted, as i can't seem to run certain apps (e.g. stellarium) because of OpenGL not working, and the error messages in my syslog seem related. Seems as if some current kernel bug is causing that, and it appears to be fixed in 2.6.36 (but i don't know when that will come to 10.10, if ever, maybe only in 11.04). I will probably just wait until it comes down the pipe rather than mess with it.

BUT i found a workaround/fix for the delay, which may be related to this issue or not, dunno:

I added the line

Hidden=true

to the file: ~/.kde/share/autostart/jockey-kde.desktop

(i may have had to copy that file to my ~/.kde/share/autostart dir from /etc/xdg/autostart/, but i think it was there already).

As far as i can tell, that autostart is doing a check for changes in video hardware or drivers or something along those lines, and it appears to have been causing the sporadic delay (of 5 to 30+ seconds). Adding that "Hidden=true" line disables it and stops the delay. Of course it may also have repercussions i'm not aware of, but so far so good.

I also noticed that the /etc/xdg/pulseaudio* startups seemed to both be starting... pulseaudio.desktop, which runs start-pulseaudio-x11, and pulseaudio-kde.desktop which runs start-pulseaudio-kde. The latter has an "OnlyShowIn=KDE;", but the former has no OnlyShowIn=, NotShowIn=, or Hidden=. I have gnome installed, and i wonder if that file is missing an "OnlyShowIn=GNOME;", or if both of those are supposed to execute when KDE starts up for some reason. I added an "OnlyShowIn=GNOME;" to the pulseaudio.desktop file and all seems well... so far...

I also stopped the pulseaudio errors by commenting out the relevant module-loading line(s) in /etc/pulse/default.pa

Anyway, thanks for the help, and, moderator, feel free to move this thread, as it's really out of scope for networking at this point. :-)

-c