Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-1
Followup-For: Bug #493479


Well, I really believed I had found a way to isolate the config option that
was causing the kernel to freeze. Of the list of options I listed in my
previous message, I found that only 7 could be manually configured via
'make menuconfig'. For each of those options, I decided to make a kernel
with all of my previously working customized options from 2.6.25 except the
one option I was testing, each of:

CONFIG_NUMA=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_NO_HZ=y
CONFIG_MIGRATION=y
CONFIG_SCHED_MC=y
CONFIG_SECCOMP=y
CONFIG_SMP=y

I hoped to install them all, them boot them all one at a time in the hope
that at least one of them would boot successfully.

All failed.

That leaves me back with one kernel -- with most of its guts configured out
-- which very nearly boots: it avoids the lockup early in the boot
process, but I removed so much of its configuration that it cannot mount
the filesystem later in the boot process.

The only approach I can think of now is to add features back into the semi-
working kernel until it stops working.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org