Regression in gdm-2.18 since 2.6.24

Regression in gdm-2.18 since 2.6.24

[Ken Moffat]

 Third attempt, with luck this time I've managed to find what really
broke it.  Sorry, this is going to be a long mail to explain my
current attribution of 'blame'.

 Summary: kernels newer than 2.6.24 break gdm's shutdown (and
restart) for me.

Action to replicate:
choose 'shutdown' or 'restart' from gdm, and confirm

Expected behaviour: X disappears and I'm back at a tty window
watching my bootscripts change to runlevel 0 or 6.

Actual behaviour: many times (with 2.6.24.X 'mostly', with 2.6.25-rc
'often') the gdm window disappears but the background remains and
the box stays in runlevel 5.

 This only happens when this box is running a 'pure64' x86_64
system, when it runs with a rather different 32-bit config it is
fine.  The system is now somewhat old (gcc-4.1.2, binutils-2.17,
glibc-2.5), and the parts of gnome that I use are 2.20 except for
gdm which is 2.18 (because I want to see the shutdown messages, in
case things fail.)

 I first saw this on 2.6.24.2, but by that time I was mostly using
x86 or other arches (I was behind on list mail, and missed the
security fix in 2.6.24.1 among the other changes there).   The problem
seemed consistent on the few occasions I used this system with
2.6.24.2.  I still had a large amount of debugging info from gdm,
and (from an earlier posting where I mistook the cause of this
problem) I had the following:

Mar 24 13:49:29 bluesbreaker gdm[2554]: Handling user message:
'GET_CONFIG greeter/SetPosition :0'
Mar 24 13:49:29 bluesbreaker gdmlogin[2995]:   Got response: 'OK
false'
Mar 24 13:49:29 bluesbreaker gdmlogin[2995]: Sending command:
'CLOSE'
Mar 24 13:49:29 bluesbreaker gdm[2554]: Handling user message:
'CLOSE'
Mar 24 13:49:29 bluesbreaker gdm[2562]: gdm_slave_wait_for_login: In
loop
Mar 24 13:49:35 bluesbreaker gdm[2562]: gdm_slave_wait_for_login:
end verify for ''
Mar 24 13:49:35 bluesbreaker gdm[2562]: gdm_slave_wait_for_login: No
login/Bad login
Mar 24 13:49:35 bluesbreaker gdm[2562]: gdm_slave_wait_for_login: In
loop
Mar 24 13:49:35 bluesbreaker gdm[2562]: gdm_slave_wait_for_login:
end verify for ''
Mar 24 13:49:35 bluesbreaker gdm[2562]: gdm_slave_wait_for_login: No
login/Bad login
... about 165 repeats of these 3 lines ...
 messages seemed to stop of their own accord until I shut down
 from a tty

 On my first attempt to find the cause, I was under the impression
that it happened every time (in 2.6.24.2 and 2.6.24.4). Speculatively
reverting some of the patches, plus an error where I forgot to set
an extraversion, overwrote the modules, and later had a successful
shutdown from 2.6.24.4 led me to erroneously point the finger at
either the drm patches or i2c-viapro.  In fact, the problem doesn't
appear every time, and I needed to do 10 attempts (a mix of 5
shutdowns and 5 restarts) before saying that a kernel seemed to be
ok.

 In my second attempt, I tried to bisect (v2.6.24 good, v2.6.25-rc1
bad) and ended up in 2.6.24-rc4.  I haven't had any replies to my
post yesterday about that, so I conclude that 'git bisect' is
another "flexible and powerful tool" which will bite non-experts like
me.

 For my third attempt (yesterday evening, and today) I established
that 2.6.24 shuts down perfectly on this system, but anything
newer is "variable".  Hence, the mix of 5 restarts and 5 shutdowns
before believing a particular kernel is ok.

 I used 2.6.24.x for this third attempt.  After confirming that
2.6.24 was rock solid for this, I tried some of the patches applied
in 2.6.24.{1,2}.  This was a lttle tricky, because security fixes
meant the normal stable "we'll apply these patches unless somebody
objects" considerations didn't apply and I didn't get to see which
individual changes were being applied to stable.

 For the first pass, I cherry-picked the stable fixes for
fs/eventpoll.c, fs/splice.c, kernel/sched_fair.c, and then
include/linx/wait.h to make eventpoll compile.  That kernel
restarted once, then failed (I'm no longer certain if the second
attempt was a restart or a shutdown).  At that point, I had
confirmed that even in 2.6.24-stable the failure didn't happen all
the time, so I reverted to extended testing.

 First up was the pair of changes to fs/splice.c.  They were fine.
Then I added eventpoll.c and wait.h and ran a few tests - seemed fine.
After that I added the change to sched_fair and things became
interesting - all the restarts were ok, all the shutdowns failed.

 At that point I tried 2.6.24.4 and reverted what should be the first
attachment for sched_fair.  That passed all my tests for restart and
shutdown.

 Next I went forward to 2.6.25-rc8.  Here, I found that 'patch'
would not revert the first hunk of that attachment because of a
context change.  So, I tried reverting only the second hunk (I didn't
know why it had been changed, so maybe they were to fix different
problems) - interestingly, that passed all 5 attempts to restart,
and failed all 5 attempts to shutdown.  I then tried the second
attachment (which reverts both hunks from rc8) and all of my tests
passed.  Probably, there is some option for patch to ignore context,
and I have no idea what problem(s) the original change was supposed
to fix.  For me, reverting the original would be wonderful but if
that will cause problems for others then I'm willing to test any
suggested changes.

 My .config for 2.6.25 is the third attachment.  Clearly, I'd like
this to be fixed in both 25 and stable.  Thanks for reading this far.

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

Re: Regression in gdm-2.18 since 2.6.24

[Rafael J. Wysocki]

On Thursday, 3 of April 2008, Ken Moffat wrote:
>  Third attempt, with luck this time I've managed to find what really
> broke it.  Sorry, this is going to be a long mail to explain my
> current attribution of 'blame'.
> 
>  Summary: kernels newer than 2.6.24 break gdm's shutdown (and
> restart) for me.
> 
> Action to replicate:
> choose 'shutdown' or 'restart' from gdm, and confirm
> 
> Expected behaviour: X disappears and I'm back at a tty window
> watching my bootscripts change to runlevel 0 or 6.
> 
> Actual behaviour: many times (with 2.6.24.X 'mostly', with 2.6.25-rc
> 'often') the gdm window disappears but the background remains and
> the box stays in runlevel 5.
> 
>  This only happens when this box is running a 'pure64' x86_64
> system, when it runs with a rather different 32-bit config it is
> fine.  The system is now somewhat old (gcc-4.1.2, binutils-2.17,
> glibc-2.5), and the parts of gnome that I use are 2.20 except for
> gdm which is 2.18 (because I want to see the shutdown messages, in
> case things fail.)
> 
>  I first saw this on 2.6.24.2, but by that time I was mostly using
> x86 or other arches (I was behind on list mail, and missed the
> security fix in 2.6.24.1 among the other changes there).   The problem
> seemed consistent on the few occasions I used this system with
> 2.6.24.2.  I still had a large amount of debugging info from gdm,
> and (from an earlier posting where I mistook the cause of this
> problem) I had the following:
> 
> Mar 24 13:49:29 bluesbreaker gdm[2554]: Handling user message:
> 'GET_CONFIG greeter/SetPosition :0'
> Mar 24 13:49:29 bluesbreaker gdmlogin[2995]:   Got response: 'OK
> false'
> Mar 24 13:49:29 bluesbreaker gdmlogin[2995]: Sending command:
> 'CLOSE'
> Mar 24 13:49:29 bluesbreaker gdm[2554]: Handling user message:
> 'CLOSE'
> Mar 24 13:49:29 bluesbreaker gdm[2562]: gdm_slave_wait_for_login: In
> loop
> Mar 24 13:49:35 bluesbreaker gdm[2562]: gdm_slave_wait_for_login:
> end verify for ''
> Mar 24 13:49:35 bluesbreaker gdm[2562]: gdm_slave_wait_for_login: No
> login/Bad login
> Mar 24 13:49:35 bluesbreaker gdm[2562]: gdm_slave_wait_for_login: In
> loop
> Mar 24 13:49:35 bluesbreaker gdm[2562]: gdm_slave_wait_for_login:
> end verify for ''
> Mar 24 13:49:35 bluesbreaker gdm[2562]: gdm_slave_wait_for_login: No
> login/Bad login
> ... about 165 repeats of these 3 lines ...
>  messages seemed to stop of their own accord until I shut down
>  from a tty
> 
>  On my first attempt to find the cause, I was under the impression
> that it happened every time (in 2.6.24.2 and 2.6.24.4). Speculatively
> reverting some of the patches, plus an error where I forgot to set
> an extraversion, overwrote the modules, and later had a successful
> shutdown from 2.6.24.4 led me to erroneously point the finger at
> either the drm patches or i2c-viapro.  In fact, the problem doesn't
> appear every time, and I needed to do 10 attempts (a mix of 5
> shutdowns and 5 restarts) before saying that a kernel seemed to be
> ok.
> 
>  In my second attempt, I tried to bisect (v2.6.24 good, v2.6.25-rc1
> bad) and ended up in 2.6.24-rc4.  I haven't had any replies to my
> post yesterday about that, so I conclude that 'git bisect' is
> another "flexible and powerful tool" which will bite non-experts like
> me.
> 
>  For my third attempt (yesterday evening, and today) I established
> that 2.6.24 shuts down perfectly on this system, but anything
> newer is "variable".  Hence, the mix of 5 restarts and 5 shutdowns
> before believing a particular kernel is ok.
> 
>  I used 2.6.24.x for this third attempt.  After confirming that
> 2.6.24 was rock solid for this, I tried some of the patches applied
> in 2.6.24.{1,2}.  This was a lttle tricky, because security fixes
> meant the normal stable "we'll apply these patches unless somebody
> objects" considerations didn't apply and I didn't get to see which
> individual changes were being applied to stable.
> 
>  For the first pass, I cherry-picked the stable fixes for
> fs/eventpoll.c, fs/splice.c, kernel/sched_fair.c, and then
> include/linx/wait.h to make eventpoll compile.  That kernel
> restarted once, then failed (I'm no longer certain if the second
> attempt was a restart or a shutdown).  At that point, I had
> confirmed that even in 2.6.24-stable the failure didn't happen all
> the time, so I reverted to extended testing.
> 
>  First up was the pair of changes to fs/splice.c.  They were fine.
> Then I added eventpoll.c and wait.h and ran a few tests - seemed fine.
> After that I added the change to sched_fair and things became
> interesting - all the restarts were ok, all the shutdowns failed.
> 
>  At that point I tried 2.6.24.4 and reverted what should be the first
> attachment for sched_fair.  That passed all my tests for restart and
> shutdown.
> 
>  Next I went forward to 2.6.25-rc8.  Here, I found that 'patch'
> would not revert the first hunk of that attachment because of a
> context change.  So, I tried reverting only the second hunk (I didn't
> know why it had been changed, so maybe they were to fix different
> problems) - interestingly, that passed all 5 attempts to restart,
> and failed all 5 attempts to shutdown.  I then tried the second
> attachment (which reverts both hunks from rc8) and all of my tests
> passed.  Probably, there is some option for patch to ignore context,
> and I have no idea what problem(s) the original change was supposed
> to fix.  For me, reverting the original would be wonderful but if
> that will cause problems for others then I'm willing to test any
> suggested changes.
> 
>  My .config for 2.6.25 is the third attachment.  Clearly, I'd like
> this to be fixed in both 25 and stable.  Thanks for reading this far.

The attachments are missing.

Can you please just provide us with the name of the git commit that you think
breaks things for you?

Also, is there CONFIG_FAIR_GROUP_SCHED set in your .config?

Thanks,
Rafael

Re: Regression in gdm-2.18 since 2.6.24

[Ken Moffat]

[-- Attachment #1: Type: text/plain, Size: 879 bytes --]

On Thu, Apr 03, 2008 at 09:56:53PM +0200, Rafael J. Wysocki wrote:
> On Thursday, 3 of April 2008, Ken Moffat wrote:
> >  Third attempt, with luck this time I've managed to find what really
> > broke it.  Sorry, this is going to be a long mail to explain my
> > current attribution of 'blame'.
[...]
> 
> The attachments are missing.
> 
> Can you please just provide us with the name of the git commit that you think
> breaks things for you?
> 
> Also, is there CONFIG_FAIR_GROUP_SCHED set in your .config?
> 
> Thanks,
> Rafael
 Oh!  Maybe they are there this time.  Apologies.

 For the commit, all I've got is the truncated line out of
patch-2.6.24.1:
index da7c061..2288ad8 100644

 Unfortunately, git log doesn't seem to find da7c061.

 And from the config
CONFIG_FAIR_GROUP_SCHED=y

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

[-- Attachment #2: sched-fair-26241 --]
[-- Type: text/plain, Size: 926 bytes --]

diff --git a/kernel/sched_fair.c b/kernel/sched_fair.c
index da7c061..2288ad8 100644
--- a/kernel/sched_fair.c
+++ b/kernel/sched_fair.c
@@ -511,7 +511,7 @@ place_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int initial)
 
 	if (!initial) {
 		/* sleeps upto a single latency don't count. */
-		if (sched_feat(NEW_FAIR_SLEEPERS) && entity_is_task(se))
+		if (sched_feat(NEW_FAIR_SLEEPERS))
 			vruntime -= sysctl_sched_latency;
 
 		/* ensure we never gain time by being placed backwards. */
@@ -867,7 +867,11 @@ static void check_preempt_wakeup(struct rq *rq, struct task_struct *p)
 	}
 
 	gran = sysctl_sched_wakeup_granularity;
-	if (unlikely(se->load.weight != NICE_0_LOAD))
+	/*
+	 * More easily preempt - nice tasks, while not making
+	 * it harder for + nice tasks.
+	 */
+	if (unlikely(se->load.weight > NICE_0_LOAD))
 		gran = calc_delta_fair(gran, &se->load);
 
 	if (pse->vruntime + gran < se->vruntime)

[-- Attachment #3: sched-fair-2625 --]
[-- Type: text/plain, Size: 743 bytes --]

--- linux-2.6.25-devel/kernel/sched_fair.c.orig	2008-04-03 14:48:51.000000000 +0100
+++ linux-2.6.25-devel/kernel/sched_fair.c	2008-04-03 16:49:34.000000000 +0100
@@ -510,7 +510,7 @@
 
 	if (!initial) {
 		/* sleeps upto a single latency don't count. */
-		if (sched_feat(NEW_FAIR_SLEEPERS)) {
+		if (sched_feat(NEW_FAIR_SLEEPERS) && entity_is_task(se)) {
 			vruntime -= calc_delta_fair(sysctl_sched_latency,
 						    &cfs_rq->load);
 		}
@@ -1145,7 +1145,7 @@
 	 * More easily preempt - nice tasks, while not making
 	 * it harder for + nice tasks.
 	 */
-	if (unlikely(se->load.weight > NICE_0_LOAD))
+	if (unlikely(se->load.weight != NICE_0_LOAD))
 		gran = calc_delta_fair(gran, &se->load);
 
 	if (pse->vruntime + gran < se->vruntime)

[-- Attachment #4: config-2.6.25-rc8 --]
[-- Type: text/plain, Size: 43280 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.25-rc8a
# Thu Apr  3 14:56:25 2008
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
# CONFIG_GENERIC_LOCKBREAK is not set
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_FAST_CMPXCHG_LOCAL=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
# CONFIG_GENERIC_GPIO is not set
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_AOUT=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
# CONFIG_KTIME_SCALAR is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=18
# CONFIG_CGROUPS is not set
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_RELAY is not set
CONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set
# CONFIG_IPC_NS is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
# CONFIG_COMPAT_BRK is not set
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_PROFILING=y
# CONFIG_MARKERS is not set
CONFIG_OPROFILE=y
CONFIG_HAVE_OPROFILE=y
CONFIG_KPROBES=y
CONFIG_KRETPROBES=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_BLOCK=y
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_BLK_DEV_BSG is not set
CONFIG_BLOCK_COMPAT=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_CLASSIC_RCU=y

#
# Processor type and features
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not set
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
# CONFIG_SMP is not set
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_X86_RDC321X is not set
# CONFIG_X86_VSMP is not set
# CONFIG_PARAVIRT_GUEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
CONFIG_MK8=y
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_L1_CACHE_BYTES=64
CONFIG_X86_INTERNODE_CACHE_BYTES=64
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_GART_IOMMU=y
# CONFIG_CALGARY_IOMMU is not set
CONFIG_IOMMU_HELPER=y
CONFIG_SWIOTLB=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
# CONFIG_PREEMPT_RCU is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_INTEL is not set
CONFIG_X86_MCE_AMD=y
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
# CONFIG_DISCONTIGMEM_MANUAL is not set
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_HAVE_MEMORY_PRESENT=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_VMEMMAP=y
# CONFIG_MEMORY_HOTPLUG is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
# CONFIG_SCHED_HRTICK is not set
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x200000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x200000
# CONFIG_COMPAT_VDSO is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management options
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_HIBERNATION is not set
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
# CONFIG_ACPI_PROCFS_POWER is not set
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
# CONFIG_ACPI_BAY is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_WMI is not set
# CONFIG_ACPI_ASUS is not set
CONFIG_ACPI_TOSHIBA=y
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_ACPI_DEBUG=y
# CONFIG_ACPI_DEBUG_FUNC_TRACE is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set
# CONFIG_ACPI_SBS is not set

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=y
CONFIG_X86_POWERNOW_K8=y
CONFIG_X86_POWERNOW_K8_ACPI=y
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
# CONFIG_X86_P4_CLOCKMOD is not set

#
# shared options
#
CONFIG_X86_ACPI_CPUFREQ_PROC_INTF=y
# CONFIG_X86_SPEEDSTEP_LIB is not set
# CONFIG_CPU_IDLE is not set

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
# CONFIG_DMAR is not set
# CONFIG_PCIEPORTBUS is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
# CONFIG_PCI_LEGACY is not set
# CONFIG_PCI_DEBUG is not set
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_K8_NB=y
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=y
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
# CONFIG_INET_LRO is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
CONFIG_IPV6=y
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_INET6_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET6_XFRM_MODE_TUNNEL is not set
# CONFIG_INET6_XFRM_MODE_BEET is not set
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
# CONFIG_IPV6_SIT is not set
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_IPV6_MULTIPLE_TABLES is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_TCPPROBE is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set

#
# Wireless
#
# CONFIG_CFG80211 is not set
# CONFIG_WIRELESS_EXT is not set
# CONFIG_MAC80211 is not set
# CONFIG_IEEE80211 is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_AX88796 is not set
CONFIG_PARPORT_1284=y
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_MISC_DEVICES=y
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_FUJITSU_LAPTOP is not set
# CONFIG_MSI_LAPTOP is not set
# CONFIG_SONY_LAPTOP is not set
# CONFIG_THINKPAD_ACPI is not set
# CONFIG_INTEL_MENLOW is not set
# CONFIG_ENCLOSURE_SERVICES is not set
CONFIG_HAVE_IDE=y
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_BLK_DEV_IDEACPI is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_PROC_FS=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_PLATFORM is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEDMA_SFF=y

#
# PCI IDE chipsets support
#
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_PCIBUS_ORDER=y
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_JMICRON is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_IT8213 is not set
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_BLK_DEV_TC86C001 is not set
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDE_ARCH_OBSOLETE_INIT=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
# CONFIG_SCSI_PROC_FS is not set

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=y
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
CONFIG_BLK_DEV_3W_XXXX_RAID=y
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
CONFIG_SCSI_AIC79XX=y
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=4000
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_ACPI=y
# CONFIG_SATA_AHCI is not set
# CONFIG_SATA_SVW is not set
# CONFIG_ATA_PIIX is not set
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SX4 is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIL24 is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
CONFIG_SATA_VIA=y
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_PATA_ACPI is not set
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
# CONFIG_MD is not set
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_NETDEVICES_MULTIQUEUE is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
# CONFIG_PHYLIB is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_R6040 is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SC92031 is not set
# CONFIG_NET_POCKET is not set
CONFIG_NETDEV_1000=y
CONFIG_ACENIC=m
# CONFIG_ACENIC_OMIT_TIGON_I is not set
CONFIG_DL2K=m
CONFIG_E1000=m
# CONFIG_E1000_NAPI is not set
# CONFIG_E1000_DISABLE_PACKET_SPLIT is not set
# CONFIG_E1000E is not set
# CONFIG_E1000E_ENABLED is not set
# CONFIG_IP1000 is not set
# CONFIG_IGB is not set
CONFIG_NS83820=m
CONFIG_HAMACHI=m
# CONFIG_YELLOWFIN is not set
CONFIG_R8169=m
# CONFIG_R8169_NAPI is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
CONFIG_SK98LIN=m
CONFIG_VIA_VELOCITY=m
CONFIG_TIGON3=m
CONFIG_BNX2=m
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
CONFIG_NETDEV_10000=y
# CONFIG_CHELSIO_T1 is not set
# CONFIG_CHELSIO_T3 is not set
# CONFIG_IXGBE is not set
# CONFIG_IXGB is not set
CONFIG_S2IO=y
# CONFIG_S2IO_NAPI is not set
# CONFIG_MYRI10GE is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_NIU is not set
# CONFIG_MLX4_CORE is not set
# CONFIG_TEHUTI is not set
# CONFIG_BNX2X is not set
# CONFIG_TR is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
CONFIG_NETCONSOLE=y
# CONFIG_NETCONSOLE_DYNAMIC is not set
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_PRINTER is not set
# CONFIG_PPDEV is not set
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_INTEL is not set
CONFIG_HW_RANDOM_AMD=y
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
CONFIG_HANGCHECK_TIMER=y
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=y
CONFIG_I2C_ALGOPCF=y
CONFIG_I2C_ALGOPCA=y

#
# I2C Hardware Bus support
#
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI1563=m
CONFIG_I2C_ALI15X3=m
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD756_S4882=m
CONFIG_I2C_AMD8111=m
CONFIG_I2C_I801=m
CONFIG_I2C_I810=m
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_I2C_SIMTEC is not set
CONFIG_I2C_SIS5595=m
CONFIG_I2C_SIS630=m
CONFIG_I2C_SIS96X=m
# CONFIG_I2C_TAOS_EVM is not set
CONFIG_I2C_STUB=m
# CONFIG_I2C_TINY_USB is not set
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
# CONFIG_I2C_VOODOO3 is not set

#
# Miscellaneous I2C Chip support
#
# CONFIG_DS1682 is not set
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_PCF8574=m
# CONFIG_PCF8575 is not set
CONFIG_SENSORS_PCF8591=m
# CONFIG_TPS65010 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set
# CONFIG_W1 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_BATTERY_DS2760 is not set
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
CONFIG_SENSORS_ABITUGURU=y
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7418 is not set
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
# CONFIG_SENSORS_ADM1029 is not set
CONFIG_SENSORS_ADM1031=m
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7473 is not set
CONFIG_SENSORS_K8TEMP=y
CONFIG_SENSORS_ASB100=m
# CONFIG_SENSORS_ATXP1 is not set
CONFIG_SENSORS_DS1621=m
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
CONFIG_SENSORS_FSCHER=m
# CONFIG_SENSORS_FSCPOS is not set
# CONFIG_SENSORS_FSCHMD is not set
CONFIG_SENSORS_GL518SM=m
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_CORETEMP is not set
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
CONFIG_SENSORS_MAX1619=m
# CONFIG_SENSORS_MAX6650 is not set
CONFIG_SENSORS_PC87360=m
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_DME1737 is not set
CONFIG_SENSORS_SMSC47M1=m
# CONFIG_SENSORS_SMSC47M192 is not set
CONFIG_SENSORS_SMSC47B397=m
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_THMC50 is not set
CONFIG_SENSORS_VIA686A=m
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
CONFIG_SENSORS_W83781D=m
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
CONFIG_SENSORS_W83L785TS=m
# CONFIG_SENSORS_W83L786NG is not set
CONFIG_SENSORS_W83627HF=m
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_SENSORS_APPLESMC is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
CONFIG_THERMAL=y
# CONFIG_WATCHDOG is not set

#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_DAB is not set

#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_VIA is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=y
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_SYS_FOPS is not set
CONFIG_FB_DEFERRED_IO=y
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set

#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
# CONFIG_FB_EFI is not set
# CONFIG_FB_HECUBA is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
CONFIG_FB_RADEON=y
CONFIG_FB_RADEON_I2C=y
# CONFIG_FB_RADEON_BACKLIGHT is not set
# CONFIG_FB_RADEON_DEBUG is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_CORGI is not set
# CONFIG_BACKLIGHT_PROGEAR is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
# CONFIG_VIDEO_SELECT is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y

#
# Sound
#
CONFIG_SOUND=y

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=y
CONFIG_SND_SEQUENCER=y
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=y
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
# CONFIG_SND_DYNAMIC_MINORS is not set
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
CONFIG_SND_VERBOSE_PRINTK=y
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
CONFIG_SND_MPU401_UART=y
CONFIG_SND_AC97_CODEC=y
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_MTS64 is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
# CONFIG_SND_PORTMAN2X4 is not set

#
# PCI devices
#
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_OXYGEN is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
CONFIG_SND_EMU10K1=m
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_HDA_INTEL is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_HIFIER is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=y
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
CONFIG_SND_VIA82XX=y
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VIRTUOSO is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_AC97_POWER_SAVE is not set

#
# USB devices
#
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set
# CONFIG_SND_USB_CAIAQ is not set

#
# System on Chip audio support
#
# CONFIG_SND_SOC is not set

#
# SoC Audio support for SuperH
#

#
# ALSA SoC audio for Freescale SOCs
#

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
CONFIG_AC97_BUS=y
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set
# CONFIG_HIDRAW is not set

#
# USB Input Devices
#
CONFIG_USB_HID=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_PERSIST is not set
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=y

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#

#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_KARMA is not set
CONFIG_USB_LIBUSUAL=y

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
CONFIG_USB_MON=y

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GADGET is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_INFINIBAND is not set
# CONFIG_EDAC is not set
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
# CONFIG_AUXDISPLAY is not set

#
# Userspace I/O
#
# CONFIG_UIO is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
# CONFIG_EXT2_FS_SECURITY is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
# CONFIG_EXT3_FS_SECURITY is not set
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=y
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
# CONFIG_REISERFS_FS_SECURITY is not set
CONFIG_JFS_FS=m
# CONFIG_JFS_POSIX_ACL is not set
# CONFIG_JFS_SECURITY is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_SECURITY is not set
# CONFIG_XFS_POSIX_ACL is not set
# CONFIG_XFS_RT is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
# CONFIG_JOLIET is not set
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
# CONFIG_CONFIGFS_FS is not set

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
# CONFIG_NFSD_V4 is not set
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_BIND34 is not set
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=y
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
# CONFIG_DLM is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_DEBUG_FS is not set
CONFIG_HEADERS_CHECK=y
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_SCHED_DEBUG=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
CONFIG_DEBUG_MUTEXES=y
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_KPROBES_SANITY_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_LKDTM is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_SAMPLES is not set
CONFIG_EARLY_PRINTK=y
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_RODATA is not set
# CONFIG_DEBUG_NX_TEST is not set
CONFIG_X86_MPPARSE=y
# CONFIG_IOMMU_DEBUG is not set
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
# CONFIG_CPA_DEBUG is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
# CONFIG_CRYPTO is not set
CONFIG_HAVE_KVM=y
CONFIG_VIRTUALIZATION=y
# CONFIG_KVM is not set
# CONFIG_VIRTIO_PCI is not set
# CONFIG_VIRTIO_BALLOON is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=y
# CONFIG_CRC16 is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=m
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y

Re: Regression in gdm-2.18 since 2.6.24

[Rafael J. Wysocki]

On Thursday, 3 of April 2008, Ken Moffat wrote:
> On Thu, Apr 03, 2008 at 09:56:53PM +0200, Rafael J. Wysocki wrote:
> > On Thursday, 3 of April 2008, Ken Moffat wrote:
> > >  Third attempt, with luck this time I've managed to find what really
> > > broke it.  Sorry, this is going to be a long mail to explain my
> > > current attribution of 'blame'.
> [...]
> > 
> > The attachments are missing.
> > 
> > Can you please just provide us with the name of the git commit that you think
> > breaks things for you?
> > 
> > Also, is there CONFIG_FAIR_GROUP_SCHED set in your .config?
> > 
> > Thanks,
> > Rafael
>  Oh!  Maybe they are there this time.  Apologies.
> 
>  For the commit, all I've got is the truncated line out of
> patch-2.6.24.1:
> index da7c061..2288ad8 100644
> 
>  Unfortunately, git log doesn't seem to find da7c061.
> 
>  And from the config
> CONFIG_FAIR_GROUP_SCHED=y

Please unset CONFIG_GROUP_SCHED and retest.  It is known to cause problems
(see http://bugzilla.kernel.org/show_bug.cgi?id=9969, for example).

Thanks,
Rafael

Re: Regression in gdm-2.18 since 2.6.24

[Ken Moffat]

On Thu, Apr 03, 2008 at 11:29:21PM +0200, Rafael J. Wysocki wrote:
> 
> Please unset CONFIG_GROUP_SCHED and retest.  It is known to cause problems
> (see http://bugzilla.kernel.org/show_bug.cgi?id=9969, for example).
> 
> Thanks,
> Rafael
 Thanks for the suggestion.  Tried it on 2.6.24.4, and
double-checked /proc/config.gz after booting -

# CONFIG_FAIR_GROUP_SCHED is not set

 Unfortunately, the first test reboot failed in the same way.

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

Re: Regression in gdm-2.18 since 2.6.24

[Rafael J. Wysocki]

On Friday, 4 of April 2008, Ken Moffat wrote:
> On Thu, Apr 03, 2008 at 11:29:21PM +0200, Rafael J. Wysocki wrote:
> > 
> > Please unset CONFIG_GROUP_SCHED and retest.  It is known to cause problems
> > (see http://bugzilla.kernel.org/show_bug.cgi?id=9969, for example).
> > 
> > Thanks,
> > Rafael
>  Thanks for the suggestion.  Tried it on 2.6.24.4, and
> double-checked /proc/config.gz after booting -
> 
> # CONFIG_FAIR_GROUP_SCHED is not set
> 
>  Unfortunately, the first test reboot failed in the same way.

Please unset CONFIG_GROUP_SCHED too.

Thanks,
Rafael

Re: Regression in gdm-2.18 since 2.6.24

[Ken Moffat]

On Fri, Apr 04, 2008 at 02:20:00AM +0200, Rafael J. Wysocki wrote:
> On Friday, 4 of April 2008, Ken Moffat wrote:
> > On Thu, Apr 03, 2008 at 11:29:21PM +0200, Rafael J. Wysocki wrote:
> > > 
> > > Please unset CONFIG_GROUP_SCHED and retest.  It is known to cause problems
> > > (see http://bugzilla.kernel.org/show_bug.cgi?id=9969, for example).
> > > 
> > > Thanks,
> > > Rafael
> >  Thanks for the suggestion.  Tried it on 2.6.24.4, and
> > double-checked /proc/config.gz after booting -
> > 
> > # CONFIG_FAIR_GROUP_SCHED is not set
> > 
> >  Unfortunately, the first test reboot failed in the same way.
> 
> Please unset CONFIG_GROUP_SCHED too.
> 
> Thanks,
> Rafael

 Yet again, I'm confused.  I thought you'd missed a word in what you
asked because the config for 2.6.24.4 doesn't show this.
ken@bluesbreaker ~ $zgrep GROUP /proc/config.gz 
# CONFIG_CGROUPS is not set
# CONFIG_FAIR_GROUP_SCHED is not set
ken@bluesbreaker ~ $

 I _can_ see it in the 2.6.25 configs (except for rc1).  Will retry
rc8 with them both turned off.

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

Re: Regression in gdm-2.18 since 2.6.24

[Srivatsa Vaddagiri]

On Thu, Apr 03, 2008 at 08:19:16PM +0100, Ken Moffat wrote:
>  Next I went forward to 2.6.25-rc8.  Here, I found that 'patch'
> would not revert the first hunk of that attachment because of a
> context change.  So, I tried reverting only the second hunk (I didn't
> know why it had been changed, so maybe they were to fix different
> problems) - interestingly, that passed all 5 attempts to restart,
> and failed all 5 attempts to shutdown.  I then tried the second
> attachment (which reverts both hunks from rc8) and all of my tests
> passed.

Just to confirm, are you saying you applied patch below on top of
2.6.25-rc8 and it solved your shutdown issues?


---
 kernel/sched_fair.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

Index: current/kernel/sched_fair.c
===================================================================
--- current.orig/kernel/sched_fair.c
+++ current/kernel/sched_fair.c
@@ -510,7 +510,7 @@
 
 	if (!initial) {
 		/* sleeps upto a single latency don't count. */
-		if (sched_feat(NEW_FAIR_SLEEPERS)) {
+		if (sched_feat(NEW_FAIR_SLEEPERS) && entity_is_task(se)) {
 			vruntime -= calc_delta_fair(sysctl_sched_latency,
 						    &cfs_rq->load);
 		}
@@ -1145,7 +1145,7 @@
 	 * More easily preempt - nice tasks, while not making
 	 * it harder for + nice tasks.
 	 */
-	if (unlikely(se->load.weight > NICE_0_LOAD))
+	if (unlikely(se->load.weight != NICE_0_LOAD))
 		gran = calc_delta_fair(gran, &se->load);
 
 	if (pse->vruntime + gran < se->vruntime)


The (reverse of above) patch was required to solve latency issues reported by
several folks (ex: http://ozlabs.org/pipermail/linuxppc-dev/2008-January/050355.html ).

I don't see any obvious reason why this patch affects shutdown. Is there
any way you can get more debug data? Basically when the machine enters
into problem state, I want to see dmesg, /proc/sched_debug output and Sysrq-T
o/p. You could get this by logging into the system over network or (if n/w
is not working in that state) by running this script:

[First ensure that syslogd is capturing kernel messages in
/var/log/messages:

Edit /etc/syslog.conf to ensure it has this line uncommented:

kern.*          /var/log/messages

Restart syslog after any changes
]

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

#!/bin/bash

/etc/init.d syslog stop
mv /var/log/messages /var/log/messages.old.$$
touch /var/log/messages
/etc/init.d syslog start

<Initiate Gnome shutdown thr' command line interface> &

sleep 10
echo "Process List" 	> /tmp/sched-log
ps -elf 		>> /tmp/sched-log
echo 			>> /tmp/sched-log
echo "Sched debug"	>> /tmp/sched-log
cat /proc/sched_debug 	>> /tmp/sched-log
echo "Process stack trace" >> /tmp/sched-log
echo 1 > /proc/sys/kernel/sysrq
echo t > /proc/sysrq-trigger 

echo "dmesg output"	>> /tmp/sched-log
cat /var/log/messages 	>> /tmp/sched-log


<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

sched-log file size would be large. You could send it to me privately or
host it on a website and send a pointer to it.

- vatsa

Re: Regression in gdm-2.18 since 2.6.24

[Dhaval Giani]

On Fri, Apr 04, 2008 at 12:48:39AM +0100, Ken Moffat wrote:
> On Thu, Apr 03, 2008 at 11:29:21PM +0200, Rafael J. Wysocki wrote:
> > 
> > Please unset CONFIG_GROUP_SCHED and retest.  It is known to cause problems
> > (see http://bugzilla.kernel.org/show_bug.cgi?id=9969, for example).
> > 
> > Thanks,
> > Rafael
>  Thanks for the suggestion.  Tried it on 2.6.24.4, and
> double-checked /proc/config.gz after booting -
> 
> # CONFIG_FAIR_GROUP_SCHED is not set
> 
>  Unfortunately, the first test reboot failed in the same way.
> 

Just to confirm. The bug happens even when CONFIG_FAIR_GROUP_SCHED is
unset?

-- 
regards,
Dhaval

Re: Regression in gdm-2.18 since 2.6.24

[Dhaval Giani]

On Fri, Apr 04, 2008 at 01:37:17PM +0100, Ken Moffat wrote:
> On Fri, Apr 04, 2008 at 02:20:00AM +0200, Rafael J. Wysocki wrote:
> > On Friday, 4 of April 2008, Ken Moffat wrote:
> > > On Thu, Apr 03, 2008 at 11:29:21PM +0200, Rafael J. Wysocki wrote:
> > > > 
> > > > Please unset CONFIG_GROUP_SCHED and retest.  It is known to cause problems
> > > > (see http://bugzilla.kernel.org/show_bug.cgi?id=9969, for example).
> > > > 
> > > > Thanks,
> > > > Rafael
> > >  Thanks for the suggestion.  Tried it on 2.6.24.4, and
> > > double-checked /proc/config.gz after booting -
> > > 
> > > # CONFIG_FAIR_GROUP_SCHED is not set
> > > 
> > >  Unfortunately, the first test reboot failed in the same way.
> > 
> > Please unset CONFIG_GROUP_SCHED too.
> > 
> > Thanks,
> > Rafael
> 
>  Yet again, I'm confused.  I thought you'd missed a word in what you
> asked because the config for 2.6.24.4 doesn't show this.
> ken@bluesbreaker ~ $zgrep GROUP /proc/config.gz 
> # CONFIG_CGROUPS is not set
> # CONFIG_FAIR_GROUP_SCHED is not set
> ken@bluesbreaker ~ $
> 
>  I _can_ see it in the 2.6.25 configs (except for rc1).  Will retry
> rc8 with them both turned off.
> 

Right, in 2.6.24 we called it CONFIG_FAIR_GROUP_SCHED since group
scheduling was available only for CFS. In 2.6.25 we have group
scheduling for RT as well, so it is called CONFIG_GROUP_SCHED now.

-- 
regards,
Dhaval

Re: Regression in gdm-2.18 since 2.6.24

[Ken Moffat]

On Fri, Apr 04, 2008 at 08:17:12PM +0530, Dhaval Giani wrote:
> On Fri, Apr 04, 2008 at 12:48:39AM +0100, Ken Moffat wrote:
> > On Thu, Apr 03, 2008 at 11:29:21PM +0200, Rafael J. Wysocki wrote:
> > > 
> > > Please unset CONFIG_GROUP_SCHED and retest.  It is known to cause problems
> > > (see http://bugzilla.kernel.org/show_bug.cgi?id=9969, for example).
> > > 
> > > Thanks,
> > > Rafael
> >  Thanks for the suggestion.  Tried it on 2.6.24.4, and
> > double-checked /proc/config.gz after booting -
> > 
> > # CONFIG_FAIR_GROUP_SCHED is not set
> > 
> >  Unfortunately, the first test reboot failed in the same way.
> > 
> 
> Just to confirm. The bug happens even when CONFIG_FAIR_GROUP_SCHED is
> unset?
> 
> -- 
> regards,
> Dhaval
 Yes.

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

Re: Regression in gdm-2.18 since 2.6.24

[Ken Moffat]

On Fri, Apr 04, 2008 at 08:18:25PM +0530, Dhaval Giani wrote:
> On Fri, Apr 04, 2008 at 01:37:17PM +0100, Ken Moffat wrote:
> > On Fri, Apr 04, 2008 at 02:20:00AM +0200, Rafael J. Wysocki wrote:
> > > On Friday, 4 of April 2008, Ken Moffat wrote:
> > > > On Thu, Apr 03, 2008 at 11:29:21PM +0200, Rafael J. Wysocki wrote:
> > > > > 
> > > > > Please unset CONFIG_GROUP_SCHED and retest.  It is known to cause problems
> > > > > (see http://bugzilla.kernel.org/show_bug.cgi?id=9969, for example).
> > > > > 
> > > > > Thanks,
> > > > > Rafael
> > > >  Thanks for the suggestion.  Tried it on 2.6.24.4, and
> > > > double-checked /proc/config.gz after booting -
> > > > 
> > > > # CONFIG_FAIR_GROUP_SCHED is not set
> > > > 
> > > >  Unfortunately, the first test reboot failed in the same way.
> > > 
> > > Please unset CONFIG_GROUP_SCHED too.
> > > 
> > > Thanks,
> > > Rafael
> > 
> >  Yet again, I'm confused.  I thought you'd missed a word in what you
> > asked because the config for 2.6.24.4 doesn't show this.
> > ken@bluesbreaker ~ $zgrep GROUP /proc/config.gz 
> > # CONFIG_CGROUPS is not set
> > # CONFIG_FAIR_GROUP_SCHED is not set
> > ken@bluesbreaker ~ $
> > 
> >  I _can_ see it in the 2.6.25 configs (except for rc1).  Will retry
> > rc8 with them both turned off.
> > 
> 
> Right, in 2.6.24 we called it CONFIG_FAIR_GROUP_SCHED since group
> scheduling was available only for CFS. In 2.6.25 we have group
> scheduling for RT as well, so it is called CONFIG_GROUP_SCHED now.
> 
> -- 
> regards,
> Dhaval
 OK, thanks for the explanation.  Just gave -rc8 the first test with
CONFIG_GROUP_SCHED unset, and again it fails.

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

Re: Regression in gdm-2.18 since 2.6.24

[Ken Moffat]

[-- Attachment #1: Type: text/plain, Size: 4718 bytes --]

On Fri, Apr 04, 2008 at 08:07:01PM +0530, Srivatsa Vaddagiri wrote:
> On Thu, Apr 03, 2008 at 08:19:16PM +0100, Ken Moffat wrote:
> >  Next I went forward to 2.6.25-rc8.  Here, I found that 'patch'
> > would not revert the first hunk of that attachment because of a
> > context change.  So, I tried reverting only the second hunk (I didn't
> > know why it had been changed, so maybe they were to fix different
> > problems) - interestingly, that passed all 5 attempts to restart,
> > and failed all 5 attempts to shutdown.  I then tried the second
> > attachment (which reverts both hunks from rc8) and all of my tests
> > passed.
> 
> Just to confirm, are you saying you applied patch below on top of
> 2.6.25-rc8 and it solved your shutdown issues?
> 
 Yes.  But, from your later comments I wonder if my description is
insufficiently clear:  the loss of functionality appears to be wholly
within gdm - that is, it's login window, and the confirm dialog
disappear but the background remains (covering all the screen) and
gdm is still running.  I switch to a tty (as I've done now) and I
can then reboot, or shutdown as the root user.

 Meanwhile, top shows two instances of gdm-binary and Xorg are still
running - I assume the two instances are normal.
> 
> ---
>  kernel/sched_fair.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> Index: current/kernel/sched_fair.c
> ===================================================================
> --- current.orig/kernel/sched_fair.c
> +++ current/kernel/sched_fair.c
> @@ -510,7 +510,7 @@
>  
>  	if (!initial) {
>  		/* sleeps upto a single latency don't count. */
> -		if (sched_feat(NEW_FAIR_SLEEPERS)) {
> +		if (sched_feat(NEW_FAIR_SLEEPERS) && entity_is_task(se)) {
>  			vruntime -= calc_delta_fair(sysctl_sched_latency,
>  						    &cfs_rq->load);
>  		}
> @@ -1145,7 +1145,7 @@
>  	 * More easily preempt - nice tasks, while not making
>  	 * it harder for + nice tasks.
>  	 */
> -	if (unlikely(se->load.weight > NICE_0_LOAD))

> +	if (unlikely(se->load.weight != NICE_0_LOAD))
>  		gran = calc_delta_fair(gran, &se->load);
>  
>  	if (pse->vruntime + gran < se->vruntime)
> 
> 
> The (reverse of above) patch was required to solve latency issues reported by
> several folks (ex: http://ozlabs.org/pipermail/linuxppc-dev/2008-January/050355.html ).
> 
> I don't see any obvious reason why this patch affects shutdown. Is there
> any way you can get more debug data? Basically when the machine enters
> into problem state, I want to see dmesg, /proc/sched_debug output and Sysrq-T
> o/p. You could get this by logging into the system over network or (if n/w
> is not working in that state) by running this script:
> 
> [First ensure that syslogd is capturing kernel messages in
> /var/log/messages:
> 
> Edit /etc/syslog.conf to ensure it has this line uncommented:
> 
> kern.*          /var/log/messages
> 
> Restart syslog after any changes
> ]
> 
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> 
> #!/bin/bash
> 
> /etc/init.d syslog stop
> mv /var/log/messages /var/log/messages.old.$$
> touch /var/log/messages
> /etc/init.d syslog start
> 
> <Initiate Gnome shutdown thr' command line interface> &
> 
> sleep 10
> echo "Process List" 	> /tmp/sched-log
> ps -elf 		>> /tmp/sched-log
> echo 			>> /tmp/sched-log
> echo "Sched debug"	>> /tmp/sched-log
> cat /proc/sched_debug 	>> /tmp/sched-log
> echo "Process stack trace" >> /tmp/sched-log
> echo 1 > /proc/sys/kernel/sysrq
> echo t > /proc/sysrq-trigger 
> 
> echo "dmesg output"	>> /tmp/sched-log
> cat /var/log/messages 	>> /tmp/sched-log
> 
> 
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> 
> sched-log file size would be large. You could send it to me privately or
> host it on a website and send a pointer to it.
> 
> - vatsa

 For the first attempt, I've kept to my old logging (kernel messages
in kern.log, generality in sys.log), so I've put both there.  This
is done manually (I don't have a mouse in the tty to copy the
script).  Log was about 200K, but after gzipping, it reduces to 18K
so I'll attach it.  This is a number of minutes after I tried to
shutdown from gdm (time to login on a tty, ssh to where the mail is,
and then start replying).

 I don't quite understand the 'Gnome shutdown through command line'
part, and perhaps I don't have that part of gnome compiled (I only
have what I need for the applets and applications that I use).  If
it's important, please specify in detail how you want me to
shutdown.

 If for some reason this log doesn't suit you, I'll copy your script
and do it all exactly.

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

[-- Attachment #2: sched-log.gz --]
[-- Type: application/x-gunzip, Size: 17757 bytes --]

Re: Regression in gdm-2.18 since 2.6.24

[Srivatsa Vaddagiri]

On Fri, Apr 04, 2008 at 04:32:32PM +0100, Ken Moffat wrote:
> > Just to confirm, are you saying you applied patch below on top of
> > 2.6.25-rc8 and it solved your shutdown issues?
> > 
>  Yes.

Thanks for confirming that the patch I sent was what you had tried and
found it to fix your problem. That patch however is not something we
want to apply for 2.6.25-rc8 (since it will worsen interactivity for
other cases).

Given that you seem to be seeing the problem even without
CONFIG_GROUP_SCHED, only the second hunk of the patch seems to be making
a difference for your problem i.e just the hunk below applied on
2.6.25-rc8 (to kernel/sched_fair.c) should fix your problem too:

@@ -1145,7 +1145,7 @@ static void check_preempt_wakeup(struct 
 	 * More easily preempt - nice tasks, while not making
 	 * it harder for + nice tasks.
 	 */
-	if (unlikely(se->load.weight > NICE_0_LOAD))
+	if (unlikely(se->load.weight != NICE_0_LOAD))
 		gran = calc_delta_fair(gran, &se->load);
 
 	if (pse->vruntime + gran < se->vruntime)

[The first hunk is a no-op under !CONFIG_GROUP_SCHED, since
entity_is_task() is always 1 for !CONFIG_GROUP_SCHED]

This second hunk changes how fast + or - niced tasks get preempted. 

2.6.25-rc8 (Bad case):
	Sets preempt granularity for + niced tasks at 5ms (1 CPU)

2.6.25-rc8 + the hunk above (Good case):
	Sets preempt granularity for + niced tasks at >5ms


So bumping up preempt granularity for + niced tasks seems to make things
work for you. IMO the deeper problem lies somewhere else (perhaps is
some race issue in gdm itself), which is easily exposed with 2.6.25-rc8 
which lets + niced tasks be preempted quickly.

To help validate this, can you let us know the result of tuning preempt
granularity on native 2.6.25-rc8 (without any patches applied and
CONFIG_GROUP_SCHED disabled)?

	# echo 100000000 > /proc/sys/kernel/sched_wakeup_granularity_ns

To check if echo command worked, do:

	# cat /proc/sys/kernel/sched_wakeup_granularity_ns

It should return 100000000.

Now try shutting down thr' gdm and pls let me know if it makes a
difference.

-- 
Regards,
vatsa

Re: Regression in gdm-2.18 since 2.6.24

[Ken Moffat]

On Sat, Apr 05, 2008 at 08:10:43PM +0530, Srivatsa Vaddagiri wrote:
> 
> Given that you seem to be seeing the problem even without
> CONFIG_GROUP_SCHED, only the second hunk of the patch seems to be making
> a difference for your problem i.e just the hunk below applied on
> 2.6.25-rc8 (to kernel/sched_fair.c) should fix your problem too:
> 
> @@ -1145,7 +1145,7 @@ static void check_preempt_wakeup(struct 
>  	 * More easily preempt - nice tasks, while not making
>  	 * it harder for + nice tasks.
>  	 */
> -	if (unlikely(se->load.weight > NICE_0_LOAD))
> +	if (unlikely(se->load.weight != NICE_0_LOAD))
>  		gran = calc_delta_fair(gran, &se->load);
>  
>  	if (pse->vruntime + gran < se->vruntime)
> 
> [The first hunk is a no-op under !CONFIG_GROUP_SCHED, since
> entity_is_task() is always 1 for !CONFIG_GROUP_SCHED]
> 
> This second hunk changes how fast + or - niced tasks get preempted. 
> 
> 2.6.25-rc8 (Bad case):
> 	Sets preempt granularity for + niced tasks at 5ms (1 CPU)
> 
> 2.6.25-rc8 + the hunk above (Good case):
> 	Sets preempt granularity for + niced tasks at >5ms
> 
 Well, I'm no longer sure exactly what was in the config, but after
I had confirmed the reversion would fix 2.6.24.4 I _did_ try just
the second part of the patch applied to 2.6.25-rc8 and it gave a 60%
success rate across 10 tests.
> 
> So bumping up preempt granularity for + niced tasks seems to make things
> work for you. IMO the deeper problem lies somewhere else (perhaps is
> some race issue in gdm itself), which is easily exposed with 2.6.25-rc8 
> which lets + niced tasks be preempted quickly.
> 

 I agree this is probably exposing a problem somewhere else.

> To help validate this, can you let us know the result of tuning preempt
> granularity on native 2.6.25-rc8 (without any patches applied and
> CONFIG_GROUP_SCHED disabled)?
> 
> 	# echo 100000000 > /proc/sys/kernel/sched_wakeup_granularity_ns
> 
> To check if echo command worked, do:
> 
> 	# cat /proc/sys/kernel/sched_wakeup_granularity_ns
> 
> It should return 100000000.
> 
> Now try shutting down thr' gdm and pls let me know if it makes a
> difference.
> 
> -- 
> Regards,
> vatsa

 Will do, but it might be a day or so before I can get to this.

Thanks.

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

Re: Regression in gdm-2.18 since 2.6.24

[Ken Moffat]

On Sat, Apr 05, 2008 at 10:03:47PM +0100, Ken Moffat wrote:
> On Sat, Apr 05, 2008 at 08:10:43PM +0530, Srivatsa Vaddagiri wrote:
> > 
> > Given that you seem to be seeing the problem even without
> > CONFIG_GROUP_SCHED, only the second hunk of the patch seems to be making
> > a difference for your problem i.e just the hunk below applied on
> > 2.6.25-rc8 (to kernel/sched_fair.c) should fix your problem too:
> > 
> > @@ -1145,7 +1145,7 @@ static void check_preempt_wakeup(struct 
> >  	 * More easily preempt - nice tasks, while not making
> >  	 * it harder for + nice tasks.
> >  	 */
> > -	if (unlikely(se->load.weight > NICE_0_LOAD))
> > +	if (unlikely(se->load.weight != NICE_0_LOAD))
> >  		gran = calc_delta_fair(gran, &se->load);
> >  
> >  	if (pse->vruntime + gran < se->vruntime)
> > 
> > [The first hunk is a no-op under !CONFIG_GROUP_SCHED, since
> > entity_is_task() is always 1 for !CONFIG_GROUP_SCHED]
> > 
> > This second hunk changes how fast + or - niced tasks get preempted. 
> > 
> > 2.6.25-rc8 (Bad case):
> > 	Sets preempt granularity for + niced tasks at 5ms (1 CPU)
> > 
> > 2.6.25-rc8 + the hunk above (Good case):
> > 	Sets preempt granularity for + niced tasks at >5ms
> > 
>  Well, I'm no longer sure exactly what was in the config, but after
> I had confirmed the reversion would fix 2.6.24.4 I _did_ try just
> the second part of the patch applied to 2.6.25-rc8 and it gave a 60%
> success rate across 10 tests.
> > 
> > So bumping up preempt granularity for + niced tasks seems to make things
> > work for you. IMO the deeper problem lies somewhere else (perhaps is
> > some race issue in gdm itself), which is easily exposed with 2.6.25-rc8 
> > which lets + niced tasks be preempted quickly.
> > 
> 
>  I agree this is probably exposing a problem somewhere else.
> 
> > To help validate this, can you let us know the result of tuning preempt
> > granularity on native 2.6.25-rc8 (without any patches applied and
> > CONFIG_GROUP_SCHED disabled)?
> > 
> > 	# echo 100000000 > /proc/sys/kernel/sched_wakeup_granularity_ns
> > 
> > To check if echo command worked, do:
> > 
> > 	# cat /proc/sys/kernel/sched_wakeup_granularity_ns
> > 
> > It should return 100000000.
> > 
> > Now try shutting down thr' gdm and pls let me know if it makes a
> > difference.
> > 
> > -- 
> > Regards,
> > vatsa
> 
>  Will do, but it might be a day or so before I can get to this.
> 
> Thanks.
> 
> Ken

 Well, I found your analysis convincing.  Unfortunately, my hardware
disagreed.  Testing -rc8 with CONFIG_GROUP_SCHED disabled (a test is
a mixture of 5 attempts to restart and 5 to shutdown):

1. the base version success is 4/10

2. increasing the granularity by a factor of 10 as you requested,
success is 8/10

3. applying the second part of the patch (and not altering the
granularity) success is 3/10

4. applying both parts of the patch (and not altering the
granularity), success is 5/10.

 Clearly, 3/10 and 5/10 may not be meaningfully different on such a
small sample size (but, 10 attempts is probably as much as my mind
and blood-pressure can stand!).  Whether 8/10 is meaningfully better
I don't know, the point is that it still failed some of the time.

 At this point, I started to doubt my previous results, so I
retested rc8 with CONFIG_GROUP_SCHED=y and both parts of the patch,
and again success is 10/10.  So, that combination has run through at
least 20 shutdowns or restarts without a problem.

 Summary: if I apply the patch to revert both hunks, AND use
CONFIG_GROUP_SCHED, everything is good.  All other variations fail
sooner or later within 10 tests (for the little it's worth, the
longest string of successful runs between failures is 6, so a
minimum of 10 tests is probably necessary before saying a version
seems ok).

 If I was confused earlier, I guess I must be dazed and confused
now!

Ken
-- 

das eine Mal als Tragödie, das andere Mal als Farce

Re: Regression in gdm-2.18 since 2.6.24

[Peter Zijlstra]

On Tue, 2008-04-08 at 14:20 +0530, Srivatsa Vaddagiri wrote:
> On Mon, Apr 07, 2008 at 12:48:33AM +0100, Ken Moffat wrote:
> >  Well, I found your analysis convincing.  Unfortunately, my hardware
> > disagreed.  Testing -rc8 with CONFIG_GROUP_SCHED disabled (a test is
> > a mixture of 5 attempts to restart and 5 to shutdown):
> > 
> > 1. the base version success is 4/10
> > 
> > 2. increasing the granularity by a factor of 10 as you requested,
> > success is 8/10
> 
> This makes me think that we are just exposing a timing related problem
> in gdm here.
> 
> How abt a larger factor?
> 
> 	# echo 200000000 > /proc/sys/kernel/sched_wakeup_granularity_ns
> 
> Does that make it 10/10 ?!
> 
> Anyway, it would be interesting to analyze the failure scenario more
> (with help from gdm developers). Can you get some more debug data in this 
> regard?
> 
> Before you shutdown,
> 
> 	# strace -p <gdm-binary-pid1> 2>/tmp/gdmlog1 &
> 	# strace -p <gdm-binary-pid2> 2>/tmp/gdmlog2 &
> 
> Now shutdown and wait few minutes to confirm its not working. Send me
> the strace log files ..Hopefully this will give a hint on what they are
> deadlocked on (in the last log you sent, i can see both gdm-binaries in
> sleep state ..whether that was a momentary state or whether they are 
> actually deadlocked, will be confirmed by strace logs above).
> 
> >  If I was confused earlier, I guess I must be dazed and confused
> > now!
> 
> me too!
> 
> Ingo/Peter, Any other suggestions you have?

Sounds like a race condition to me; non of these changes affect
correctness in a strict manner of speaking.

Re: Regression in gdm-2.18 since 2.6.24

[Srivatsa Vaddagiri]

On Mon, Apr 07, 2008 at 12:48:33AM +0100, Ken Moffat wrote:
>  Well, I found your analysis convincing.  Unfortunately, my hardware
> disagreed.  Testing -rc8 with CONFIG_GROUP_SCHED disabled (a test is
> a mixture of 5 attempts to restart and 5 to shutdown):
> 
> 1. the base version success is 4/10
> 
> 2. increasing the granularity by a factor of 10 as you requested,
> success is 8/10

This makes me think that we are just exposing a timing related problem
in gdm here.

How abt a larger factor?

	# echo 200000000 > /proc/sys/kernel/sched_wakeup_granularity_ns

Does that make it 10/10 ?!

Anyway, it would be interesting to analyze the failure scenario more
(with help from gdm developers). Can you get some more debug data in this 
regard?

Before you shutdown,

	# strace -p <gdm-binary-pid1> 2>/tmp/gdmlog1 &
	# strace -p <gdm-binary-pid2> 2>/tmp/gdmlog2 &

Now shutdown and wait few minutes to confirm its not working. Send me
the strace log files ..Hopefully this will give a hint on what they are
deadlocked on (in the last log you sent, i can see both gdm-binaries in
sleep state ..whether that was a momentary state or whether they are 
actually deadlocked, will be confirmed by strace logs above).

>  If I was confused earlier, I guess I must be dazed and confused
> now!

me too!

Ingo/Peter, Any other suggestions you have?


-- 
Regards,
vatsa

Re: Regression in gdm-2.18 since 2.6.24

[Carlos R. Mafra]

On Tue  8.Apr'08 at 14:20:27 +0530, Srivatsa Vaddagiri wrote:
> On Mon, Apr 07, 2008 at 12:48:33AM +0100, Ken Moffat wrote:
> >  Well, I found your analysis convincing.  Unfortunately, my hardware
> > disagreed.  Testing -rc8 with CONFIG_GROUP_SCHED disabled (a test is
> > a mixture of 5 attempts to restart and 5 to shutdown):
> > 
> > 1. the base version success is 4/10
> > 
> > 2. increasing the granularity by a factor of 10 as you requested,
> > success is 8/10
> 
> This makes me think that we are just exposing a timing related problem
> in gdm here.

I can see the same issue in my desktop with kdm, but I've never had
the energy to bisect or look further into it, so I just type halt or
reboot in xterm :-(

But the fact is that a few days ago I tried rebooting through kdm button,
but it left me with a console login screen (and no reboot).

It also happened a few times before too (and I am always using a 
uptodated 2.6.25-rcX kernel).

Re: Regression in gdm-2.18 since 2.6.24

[Ken Moffat]

On Tue, Apr 08, 2008 at 02:20:27PM +0530, Srivatsa Vaddagiri wrote:
> On Mon, Apr 07, 2008 at 12:48:33AM +0100, Ken Moffat wrote:
> >  Well, I found your analysis convincing.  Unfortunately, my hardware
> > disagreed.  Testing -rc8 with CONFIG_GROUP_SCHED disabled (a test is
> > a mixture of 5 attempts to restart and 5 to shutdown):
> > 
> > 1. the base version success is 4/10
> > 
> > 2. increasing the granularity by a factor of 10 as you requested,
> > success is 8/10
> 
> This makes me think that we are just exposing a timing related problem
> in gdm here.
> 
> How abt a larger factor?
> 
> 	# echo 200000000 > /proc/sys/kernel/sched_wakeup_granularity_ns
> 
> Does that make it 10/10 ?!
> 
[ snipping the suggestion to run strace, I've already sent the
results off-list ]

 Yes, it does.  Seems to run adequately too (a little audio playback,
a little you-tube, some untarring and compiling).  Understanding the
real problem would be nice, but for me this seems to be an adequate
work-around.  This is with CONFIG_GROUP_SCHED turned off.

Thanks

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce