Bug 382167 - unexplainable 30s delay in boot process
Summary: unexplainable 30s delay in boot process
Status: RESOLVED DUPLICATE of bug 371776
: 384341 (view as bug list)
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Beta 1
Hardware: x86-64 openSUSE 11.0
: P5 - None : Major (vote)
Target Milestone: Beta 2
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-22 00:35 UTC by Jörg Hermsdorf
Modified: 2008-05-08 17:39 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
/var/log/boot.msg (48.10 KB, text/plain)
2008-04-22 00:35 UTC, Jörg Hermsdorf
Details
/var/log/boot.msg with bluetooth off (43.86 KB, text/plain)
2008-05-05 17:25 UTC, Jan Matejek
Details
/var/log/boot.msg with bluetooth on (44.55 KB, text/plain)
2008-05-05 17:30 UTC, Jan Matejek
Details
Boot logs and dmesg output (33.20 KB, application/zip)
2008-05-08 09:30 UTC, Willem Meens
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jörg Hermsdorf 2008-04-22 00:35:10 UTC
Created attachment 209469 [details]
/var/log/boot.msg

Since I installed openSUSE 11.0 the first time (I think it was Alpha2) I always noticed a strange 30 second delay in the boot process.

On openSUSE 10.3 it takes about 29 seconds from Grub to KDM login promt. On openSUSE 11.0 it takes 64 seconds on my system.

If I press ESC during the boot process to quit the bootsplash, I notice a 30 seconds delay between the lines:

> wmaster0 renamed to wmaster0_rename

and

> Loading required kernel modules

I'll attach my /var/log/boot.msg logfile. If I look at this one and search for 'wmaster0 renamed to wmaster0_rename' the next line is:
Adding 1542168k swap on /dev/sda5.  Priority:-1 extents:1 across:1542168k

/dev/sda5 is my swap partion. Could it be, that whatever this line means, it takes about 30 seconds to add this swap and that this is done on every reboot?

My system is a Lenovo ThinkPad T60p using openSUSE 11.0 Beta1 x86_64.
Comment 1 Willem Meens 2008-04-24 09:32:18 UTC
I had this issue to, until I did a factory update yesterday (23 04) giving me a new kernel (amongst others). So here it seems fixed!
Comment 2 Willem Meens 2008-04-24 09:50:11 UTC
Looks like a duplicate of Bug 371776
Comment 3 Jörg Hermsdorf 2008-04-24 11:16:49 UTC
Yes, after the update the problem is gone. I'm setting this to fixed.
Comment 4 Jörg Hermsdorf 2008-04-28 16:59:39 UTC
*** Bug 384341 has been marked as a duplicate of this bug. ***
Comment 5 Jan Matejek 2008-05-05 17:24:39 UTC
sorry, still present with kernel-default-2.6.25-26 - reopening
my system is a MSI PR200 with 11.0 beta 2
Comment 6 Jan Matejek 2008-05-05 17:25:45 UTC
Created attachment 212415 [details]
/var/log/boot.msg with bluetooth off
Comment 7 Jan Matejek 2008-05-05 17:30:41 UTC
Created attachment 212418 [details]
/var/log/boot.msg with bluetooth on

this is when bluetooth is turned on - i.e., Bug 371776 is actually a duplicate of this one
Comment 8 Greg Kroah-Hartman 2008-05-07 20:06:43 UTC

*** This bug has been marked as a duplicate of bug 371776 ***
Comment 9 Willem Meens 2008-05-08 09:29:16 UTC
Sorry to be a sack of jumping beans on this... but the delay issue is back on my laptop.

Boot is taking 1m-40s (was roughly 65 secs).  
There is a delay after I see my network driver (b44) getting loaded - then nothing happens (not even hd activity) for 25~30 seconds and the line 'Loading required kernel modules' is printed and the system resumes booting. There are no errors printed and I will attach my boot logs and dmesg output.

Can I reopen this bug or make a new one?  And what info is needed to further diagnose?

Cheers,
  Wj
Comment 10 Willem Meens 2008-05-08 09:30:01 UTC
Created attachment 213455 [details]
Boot logs and dmesg output
Comment 11 Willem Meens 2008-05-08 09:31:12 UTC
Also as note : the delay was back after a fresh install using the Beta2 DVD iso.
Comment 12 Jan Matejek 2008-05-08 17:39:02 UTC
(In reply to comment #9 from Willem Meens)
> Can I reopen this bug or make a new one?  And what info is needed to further
> diagnose?

i reopened the duplicate, bug 371776. come join me in there :e)