[Bugme-new] [Bug 16495] New: Kernel 2.6.35 takes almost half an hour to boot
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Mon Aug 2 10:16:28 PDT 2010
https://bugzilla.kernel.org/show_bug.cgi?id=16495
Summary: Kernel 2.6.35 takes almost half an hour to boot
Product: Other
Version: 2.5
Kernel Version: 2.6.35
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Other
AssignedTo: other_other at kernel-bugs.osdl.org
ReportedBy: claudiomkd at gmail.com
Regression: No
Created an attachment (id=27323)
--> (https://bugzilla.kernel.org/attachment.cgi?id=27323)
.config for 2.6.35 (exactly the same as my working 2.6.34.1)
I just compiled the brand new 2.6.35.
I have a Vaio SR11M with an Intel processor Core 2 Duo Penryn P8400.
When I booted my system, it took about half an hour to reach the console login
(getty). At boot, the whole system is stuck (no cursor blinking anymore,
although I can press CapsLocks and the led will light up). It takes about 5
minutes for udev scripts to run.
After about 7 minutes, the kernel reports that it was unable to load the
iwlwifi-5000-ucode firmware (this is probably another bug, but wifi worked
perfectly with 2.6.34.1). Still, after this the boot process continues but very
very slowly. Every line appears every 2 or 3 minutes, and it seems that the
kernel is doing something.
After waiting for almost half an hour, the system finally boots, I can see the
display manager, but in console 0 (in text mode). Again (although this should
be another topic) I can see ioctl errors about wlan0, my wireless device is not
recognized.
I use Debian Sid (up to date), kernel 2.6.35 vanilla with the same options as
2.6.34.1 (which works perfectly in the exact same environment). My system is
64-bits (Debian amd64).
Any clues why 2.6.35 boots so extremely slowly?
Please find enclosed my .config-2.6.35.
--Claudio
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the Bugme-new
mailing list