Bug 16605 - Hang on boot, just after "Booting the kernel." message
Summary: Hang on boot, just after "Booting the kernel." message
Status: RESOLVED OBSOLETE
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: i386 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: platform_i386
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-16 13:06 UTC by buildyear68
Modified: 2012-08-13 15:54 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.35.2
Tree: Mainline
Regression: No


Attachments
.config for kernel 2.6.35.2 (54.61 KB, text/plain)
2010-08-16 13:06 UTC, buildyear68
Details
changes to the not working .config file (12.29 KB, patch)
2010-08-25 13:25 UTC, buildyear68
Details | Diff

Description buildyear68 2010-08-16 13:06:20 UTC
Created attachment 27466 [details]
.config for kernel 2.6.35.2

I've moved my old /usr/src/linux-2.6.34.4/.config which boots my system to the current kernel 2.6.35.2. Then I do the 'make oldconfig' build the kernel, but after booting the 2.6.35.2 kernel it hangs on boot.

Kernel parameters are:
[acpi=off] noapic clocksource=jiffies

The System is a vmware server 1.0.5 build-80187.
Comment 1 buildyear68 2010-08-25 13:25:46 UTC
Created attachment 27941 [details]
changes to the not working .config file

With the patch in this file to my first given .config it is possible to boot the kernel 2.6.35.2 on vmware again.
Comment 2 H. Peter Anvin 2010-08-25 16:34:45 UTC
There are just way too many differences between these two config files, not to mention that they are generated on different kernel versions.  It changes several "large" options, including CONFIG_SMP; any way to narrow down the differences?
Comment 3 Roland Kletzing 2010-12-29 12:29:41 UTC
>The System is a vmware server 1.0.5 build-80187.

that is quite old. (~2 yrs)

i would recommend updating to the latest "old" vmware server release 1.0.10 first or switch to vmware server 2.x. With that you would get rid of some serious vmware bugs and fix many security issues, too.

Note You need to log in before you can comment on or make changes to this bug.