+ restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

+ restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[akpm]

The patch titled
     restore missing sysfs max_cstate attr
has been added to the -mm tree.  Its filename is
     restore-missing-sysfs-max_cstate-attr.patch

*** Remember to use Documentation/SubmitChecklist when testing your code ***

See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this

------------------------------------------------------
Subject: restore missing sysfs max_cstate attr
From: Mark Lord <lkml@rtr.ca>

Restore visibility of /sys/module/processor/parameters/max_cstate
for compatibility with kernels prior to 2.6.24.

Signed-off-by: Mark Lord <mlord@pobox.com>
Cc: Len Brown <lenb@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Cc: Adam Belay <abelay@novell.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 acpi/processor_idle.c.orig    |    0 
 drivers/acpi/processor_idle.c |    2 +-
 2 files changed, 1 insertion(+), 1 deletion(-)

diff -puN drivers/acpi/processor_idle.c~restore-missing-sysfs-max_cstate-attr drivers/acpi/processor_idle.c
--- a/drivers/acpi/processor_idle.c~restore-missing-sysfs-max_cstate-attr
+++ a/drivers/acpi/processor_idle.c
@@ -76,7 +76,7 @@ static void (*pm_idle_save) (void) __rea
 #define PM_TIMER_TICKS_TO_US(p)		(((p) * 1000)/(PM_TIMER_FREQUENCY/1000))
 
 static unsigned int max_cstate __read_mostly = ACPI_PROCESSOR_MAX_POWER;
-module_param(max_cstate, uint, 0000);
+module_param(max_cstate, uint, 0644);
 static unsigned int nocst __read_mostly;
 module_param(nocst, uint, 0000);
 
diff -puN drivers/acpi/processor_idle.c.orig~restore-missing-sysfs-max_cstate-attr drivers/acpi/processor_idle.c.orig
_

Patches currently in -mm which might be from lkml@rtr.ca are

rtc-dont-write-rtc-century-when-setting-a-wake-alarm.patch
pcie-fix-double-initialization-bug.patch
restore-missing-sysfs-max_cstate-attr.patch

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Andrew Morton]

On Fri, 30 Nov 2007 14:06:55 -0800
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com> wrote:

Please dont go off-list like this.  I put Mark's original mailing list cc's
back.

> 
> I will have to Nack this. The reason max_cstate was initentionally
> removed due to couple of reasons:

It broke userspace without any warning or migration period, afaict.

> 1) All in kernel users of max_cstate should rather be using
> pm_qos/latency interfaces. All such max_cstate usages must already be
> migrated.

That code isn't merged.

> 2) Supporting max_cstate as a dynamic parameter cleanly is no longer
> possible in acpi/processor_idle.c as the C-state policy has moved to
> cpuidle instead. It can be done if it is needed. But, just below patch
> will not really work with cpuidle.
> 
> Selecting max_cstate at boot time as a debug option still works without
> this patch.
> 
> So, just this patch will not get back the functionality with cpuidle.
> Infact changing it at run time will have no effect. Question however is:
> Is there a real need to revive this parameter so that user can change
> max_cstate at run time?

It is not known whether Mark is actually writing to this thing.  Perhaps
read-only permissions would be a suitable fix?

RE: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Pallipadi, Venkatesh]

 

>On Fri, 30 Nov 2007 14:06:55 -0800
>"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com> wrote:
>
>Please dont go off-list like this.  I put Mark's original 
>mailing list cc's
>back.

Sorry for missing some cc's earlier. I blindly did a reply-all to the
mm-commits mail I got.

>> I will have to Nack this. The reason max_cstate was initentionally
>> removed due to couple of reasons:
>
>It broke userspace without any warning or migration period, afaict.

Yes. That's true. I will have to take the blame for that. It has been
known for a while during cpuidle development. But, it was never
documented as deprecating.
 
>> 1) All in kernel users of max_cstate should rather be using
>> pm_qos/latency interfaces. All such max_cstate usages must already be
>> migrated.
>
>That code isn't merged.

All kernel part is already merged. I mean, there are do drivers that
depend on max_cstate. They use latency_notifier thing today and their
migration to pm_qos part is not merged yet.

>> 2) Supporting max_cstate as a dynamic parameter cleanly is no longer
>> possible in acpi/processor_idle.c as the C-state policy has moved to
>> cpuidle instead. It can be done if it is needed. But, just 
>below patch
>> will not really work with cpuidle.
>> 
>> Selecting max_cstate at boot time as a debug option still 
>works without
>> this patch.
>> 
>> So, just this patch will not get back the functionality with cpuidle.
>> Infact changing it at run time will have no effect. Question 
>however is:
>> Is there a real need to revive this parameter so that user can change
>> max_cstate at run time?
>
>It is not known whether Mark is actually writing to this 
>thing.  Perhaps
>read-only permissions would be a suitable fix?
>

Exporting it as read only should be OK. We also need to know if there
are hard user space dependency on writing to this from userspace.

Thanks,
Venki  

RE: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Pallipadi, Venkatesh]

 

>On Fri, 30 Nov 2007 14:06:55 -0800
>"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com> wrote:
>
>Please dont go off-list like this.  I put Mark's original 
>mailing list cc's
>back.

Sorry for missing some cc's earlier. I blindly did a reply-all to the
mm-commits mail I got.

>> I will have to Nack this. The reason max_cstate was initentionally
>> removed due to couple of reasons:
>
>It broke userspace without any warning or migration period, afaict.

Yes. That's true. I will have to take the blame for that. It has been
known for a while during cpuidle development. But, it was never
documented as deprecating.
 
>> 1) All in kernel users of max_cstate should rather be using
>> pm_qos/latency interfaces. All such max_cstate usages must already be
>> migrated.
>
>That code isn't merged.

All kernel part is already merged. I mean, there are do drivers that
depend on max_cstate. They use latency_notifier thing today and their
migration to pm_qos part is not merged yet.

>> 2) Supporting max_cstate as a dynamic parameter cleanly is no longer
>> possible in acpi/processor_idle.c as the C-state policy has moved to
>> cpuidle instead. It can be done if it is needed. But, just 
>below patch
>> will not really work with cpuidle.
>> 
>> Selecting max_cstate at boot time as a debug option still 
>works without
>> this patch.
>> 
>> So, just this patch will not get back the functionality with cpuidle.
>> Infact changing it at run time will have no effect. Question 
>however is:
>> Is there a real need to revive this parameter so that user can change
>> max_cstate at run time?
>
>It is not known whether Mark is actually writing to this 
>thing.  Perhaps
>read-only permissions would be a suitable fix?
>

Exporting it as read only should be OK. We also need to know if there
are hard user space dependency on writing to this from userspace.

Thanks,
Venki  

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Pallipadi, Venkatesh wrote:
>  
> 
>> On Fri, 30 Nov 2007 14:06:55 -0800
>> "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com> wrote:
>>
>> Please dont go off-list like this.  I put Mark's original 
>> mailing list cc's
>> back.
> 
> Sorry for missing some cc's earlier. I blindly did a reply-all to the
> mm-commits mail I got.
> 
>>> I will have to Nack this. The reason max_cstate was initentionally
>>> removed due to couple of reasons:
>> It broke userspace without any warning or migration period, afaict.
> 
> Yes. That's true. I will have to take the blame for that. It has been
> known for a while during cpuidle development. But, it was never
> documented as deprecating.
>  
>>> 1) All in kernel users of max_cstate should rather be using
>>> pm_qos/latency interfaces. All such max_cstate usages must already be
>>> migrated.
>> That code isn't merged.
> 
> All kernel part is already merged. I mean, there are do drivers that
> depend on max_cstate. They use latency_notifier thing today and their
> migration to pm_qos part is not merged yet.
> 
>>> 2) Supporting max_cstate as a dynamic parameter cleanly is no longer
>>> possible in acpi/processor_idle.c as the C-state policy has moved to
>>> cpuidle instead. It can be done if it is needed. But, just 
>> below patch
>>> will not really work with cpuidle.
>>>
>>> Selecting max_cstate at boot time as a debug option still 
>> works without
>>> this patch.
>>>
>>> So, just this patch will not get back the functionality with cpuidle.
>>> Infact changing it at run time will have no effect. Question 
>> however is:
>>> Is there a real need to revive this parameter so that user can change
>>> max_cstate at run time?
>> It is not known whether Mark is actually writing to this 
>> thing.  Perhaps
>> read-only permissions would be a suitable fix?
>>
> 
> Exporting it as read only should be OK. We also need to know if there
> are hard user space dependency on writing to this from userspace.
..

Well, actually..  my scripts have a firm need to write "1" to it,
and then later restore the original value.

This is needed to *greatly* speed up an otherwise sluggish binary I use,
as well as whenever I want to semi-accurately benchmark I/O.

Is there another way to achieve exactly the same behaviour?

Thanks

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Arjan van de Ven]

On Fri, 30 Nov 2007 21:52:40 -0500
Mark Lord <lkml@rtr.ca> wrote:

> Pallipadi, Venkatesh wrote:

> > 
> > Exporting it as read only should be OK. We also need to know if
> > there are hard user space dependency on writing to this from
> > userspace.
> ..
> 
> Well, actually..  my scripts have a firm need to write "1" to it,
> and then later restore the original value.
> 
> This is needed to *greatly* speed up an otherwise sluggish binary I
> use, 

just curious, but this does sound like the c-state code has a bug...
independent of the sysfs thing, I think that really needs solving

Can you describe the behavior a little? Or provide information to the
degree that some of us can figure out how to tweak the algorithm..,.


>as well as whenever I want to semi-accurately benchmark I/O.
> 
> Is there another way to achieve exactly the same behaviour?

in -mm there is.. the QoS stuff allows you to set maximum tolerable
latency. If your app cant take any latency, you should set those... and
the side effect is that the kernel will not do long-latency C-states or
P-state transitions..

-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Arjan van de Ven wrote:
> On Fri, 30 Nov 2007 21:52:40 -0500
> Mark Lord <lkml@rtr.ca> wrote:
> 
>> Pallipadi, Venkatesh wrote:
> 
>>> Exporting it as read only should be OK. We also need to know if
>>> there are hard user space dependency on writing to this from
>>> userspace.
>> ..
>>
>> Well, actually..  my scripts have a firm need to write "1" to it,
>> and then later restore the original value.
>>
>> This is needed to *greatly* speed up an otherwise sluggish binary I
>> use, 
> 
> just curious, but this does sound like the c-state code has a bug...
> independent of the sysfs thing, I think that really needs solving
> 
> Can you describe the behavior a little? Or provide information to the
> degree that some of us can figure out how to tweak the algorithm..,.
> 
> 
>> as well as whenever I want to semi-accurately benchmark I/O.
>>
>> Is there another way to achieve exactly the same behaviour?
> 
> in -mm there is.. the QoS stuff allows you to set maximum tolerable
..

That's encouraging, I think, but not for 2.6.24.

> latency. If your app cant take any latency, you should set those... and
> the side effect is that the kernel will not do long-latency C-states or
> P-state transitions..
..

I don't mind the cpufreq changing (actually, I want it to drop in cpugfreq
to save power and keep the fan off), but the C-states just kill this app.

The app is VMware.  I force the max_state=1 when launching,
and restore it to (prior value) 8 when it exits.
Makes a *huge* difference for text input and the like.
Yes, there's something there that could get fixed in the app,
and maybe one day will get fixed.  But I'm not holding my breath.

I think it manages to resonate at exactly the harmonic required that
the chip transitions to C?? just prior to the app wanting to wake up 
and do another poll.  Just kills it.

I'm not sure about C?? -- it could be C8 or even be C2 or whatever.
I suppose I should find out, but that really takes a lot of fuss (hours)
to measure, and isn't strictly repeatable.



 

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Arjan van de Ven]

On Fri, 30 Nov 2007 22:14:08 -0500
Mark Lord <lkml@rtr.ca> wrote:

> > in -mm there is.. the QoS stuff allows you to set maximum tolerable
> ..
> 
> That's encouraging, I think, but not for 2.6.24.
> 
> > latency. If your app cant take any latency, you should set those...
> > and the side effect is that the kernel will not do long-latency
> > C-states or P-state transitions..
> ..
> 
> I don't mind the cpufreq changing (actually, I want it to drop in
> cpugfreq to save power and keep the fan off), but the C-states just
> kill this app.
> 
> The app is VMware.  I force the max_state=1 when launching,

ah but then its' even easier... and can be done in 2.6.24 already.
VMWare after all has a kernel module, and the latency stuff is in
2.6.23 and 2.6.24 available inside the kernel already.

> 
> I'm not sure about C?? -- it could be C8 or even be C2 or whatever.
> I suppose I should find out, but that really takes a lot of fuss
> (hours) to measure, and isn't strictly repeatable.

(also hope you don't have one of those AMD machines where the bios
turns C1 into C2/C3/etc behind the OSes back ;-)


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Arjan van de Ven wrote:
> On Fri, 30 Nov 2007 22:14:08 -0500
> Mark Lord <lkml@rtr.ca> wrote:
> 
>>> in -mm there is.. the QoS stuff allows you to set maximum tolerable
>> ..
>>
>> That's encouraging, I think, but not for 2.6.24.
>>
>>> latency. If your app cant take any latency, you should set those...
>>> and the side effect is that the kernel will not do long-latency
>>> C-states or P-state transitions..
>> ..
>>
>> I don't mind the cpufreq changing (actually, I want it to drop in
>> cpugfreq to save power and keep the fan off), but the C-states just
>> kill this app.
>>
>> The app is VMware.  I force the max_state=1 when launching,
> 
> ah but then its' even easier... and can be done in 2.6.24 already.
> VMWare after all has a kernel module, and the latency stuff is in
> 2.6.23 and 2.6.24 available inside the kernel already.
..

Oh, I'm perfectly happy to write my own kernel module if that's what
is going to be needed here, but just doing an echo into sysfs was simpler.
But yes, it appears to have no effect even with the chmod patch I posted,
so something different is needed here.

>> I'm not sure about C?? -- it could be C8 or even be C2 or whatever.
>> I suppose I should find out, but that really takes a lot of fuss
>> (hours) to measure, and isn't strictly repeatable.
> 
> (also hope you don't have one of those AMD machines where the bios
> turns C1 into C2/C3/etc behind the OSes back ;-)
..

Just a nice Intel Core2 Duo notebook.

Speaking of which.. what's with powertop on 2.6.24 ???
It's gone from 100-200 wakeups/sec to 20000 wakeups/sec !!!!!!!

New thread time..

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Arjan van de Ven wrote:
> On Fri, 30 Nov 2007 22:31:17 -0500
> Mark Lord <lkml@rtr.ca> wrote:
> 
>> Arjan van de Ven wrote:
>>> On Fri, 30 Nov 2007 22:14:08 -0500
>>> Mark Lord <lkml@rtr.ca> wrote:
>>>
>>>>> in -mm there is.. the QoS stuff allows you to set maximum
>>>>> tolerable
>>>> ..
>>>>
>>>> That's encouraging, I think, but not for 2.6.24.
>>>>
>>>>> latency. If your app cant take any latency, you should set
>>>>> those... and the side effect is that the kernel will not do
>>>>> long-latency C-states or P-state transitions..
>>>> ..
>>>>
>>>> I don't mind the cpufreq changing (actually, I want it to drop in
>>>> cpugfreq to save power and keep the fan off), but the C-states just
>>>> kill this app.
>>>>
>>>> The app is VMware.  I force the max_state=1 when launching,
>>> ah but then its' even easier... and can be done in 2.6.24 already.
>>> VMWare after all has a kernel module, and the latency stuff is in
>>> 2.6.23 and 2.6.24 available inside the kernel already.
>> ..
>>
>> Oh, I'm perfectly happy to write my own kernel module if that's what
> 
> all you need to do in your kernel module is call
> 
> add_latency_constraint("mark_wants_his_mouse", 5);

Okay, and how to change it back again?  (thanks)

Then why not have a sysfs entry for scripts to write to
to trigger the exact same end result?  :)

>> Speaking of which.. what's with powertop on 2.6.24 ???
>> It's gone from 100-200 wakeups/sec to 20000 wakeups/sec !!!!!!!
> 
> ho hum.. Lenovo T61?
> I have some reports that that happens once in a while (but it's not
> limited to .24 and it's also real, it's not a powertop bug but it
> actually is waking up that much)..
..

No, it's my hefty Dell Inspiron 9400.

And I just figured out the powertop:  it needed the kernel timers
patch from the powertop site that was originally for 2.6.21.. 

Any chance of somebody actually pushing that patch upstream some year ??
Patch reproduced here for interest's sake only.
Hey, look who's on the Signed-off list for it, *Arjan* !

* * *

>From e6f2ff1e4763212f1dcc945db76fb744b951ac53 Mon Sep 17 00:00:00 2001
From: Josh Triplett <josh@freedesktop.org>
Date: Sun, 13 May 2007 15:21:39 -0700
Subject: [PATCH] Lengthen and align background timers to decrease wakeups

This patch changes a few background timers in the Linux kernel to
1) be aligned to full seconds so that multiple timers get handled in one
   processor wakeup
2) have longer timeouts for those timers that can use such longer timeouts

Some of these are a bit crude, but it's effective.

Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
[Josh: Updates for 2.6.22-rc1]
Signed-off-by: Josh Triplett <josh@kernel.org>
---
 kernel/time/clocksource.c |   10 ++++++++--
 mm/page-writeback.c       |    8 ++++----
 mm/slab.c                 |    6 +++---
 net/core/neighbour.c      |    4 ++--
 4 files changed, 17 insertions(+), 11 deletions(-)

diff --git a/kernel/time/clocksource.c b/kernel/time/clocksource.c
index 3db5c3c..77308c4 100644
--- a/kernel/time/clocksource.c
+++ b/kernel/time/clocksource.c
@@ -79,11 +79,17 @@ static int watchdog_resumed;
 /*
  * Interval: 0.5sec Threshold: 0.0625s
  */
-#define WATCHDOG_INTERVAL (HZ >> 1)
+#define WATCHDOG_INTERVAL (HZ*10)
 #define WATCHDOG_THRESHOLD (NSEC_PER_SEC >> 4)
 
+static int secondtime;
+
 static void clocksource_ratewd(struct clocksource *cs, int64_t delta)
 {
+	if (!secondtime) {
+		secondtime = 1;
+		return;
+	};
 	if (delta > -WATCHDOG_THRESHOLD && delta < WATCHDOG_THRESHOLD)
 		return;
 
@@ -145,7 +151,7 @@ static void clocksource_watchdog(unsigned long data)
 
 	if (!list_empty(&watchdog_list)) {
 		__mod_timer(&watchdog_timer,
-			    watchdog_timer.expires + WATCHDOG_INTERVAL);
+			    round_jiffies(watchdog_timer.expires + WATCHDOG_INTERVAL));
 	}
 	spin_unlock(&watchdog_lock);
 }
diff --git a/mm/page-writeback.c b/mm/page-writeback.c
index eec1481..26318e5 100644
--- a/mm/page-writeback.c
+++ b/mm/page-writeback.c
@@ -77,7 +77,7 @@ int vm_dirty_ratio = 10;
 /*
  * The interval between `kupdate'-style writebacks, in jiffies
  */
-int dirty_writeback_interval = 5 * HZ;
+int dirty_writeback_interval = 15 * HZ;
 
 /*
  * The longest number of jiffies for which data is allowed to remain dirty
@@ -450,7 +450,7 @@ static void wb_kupdate(unsigned long arg)
 
 	oldest_jif = jiffies - dirty_expire_interval;
 	start_jif = jiffies;
-	next_jif = start_jif + dirty_writeback_interval;
+	next_jif = round_jiffies(start_jif + dirty_writeback_interval);
 	nr_to_write = global_page_state(NR_FILE_DIRTY) +
 			global_page_state(NR_UNSTABLE_NFS) +
 			(inodes_stat.nr_inodes - inodes_stat.nr_unused);
@@ -467,7 +467,7 @@ static void wb_kupdate(unsigned long arg)
 		nr_to_write -= MAX_WRITEBACK_PAGES - wbc.nr_to_write;
 	}
 	if (time_before(next_jif, jiffies + HZ))
-		next_jif = jiffies + HZ;
+		next_jif = round_jiffies(jiffies + HZ);
 	if (dirty_writeback_interval)
 		mod_timer(&wb_timer, next_jif);
 }
@@ -491,7 +491,7 @@ int dirty_writeback_centisecs_handler(ctl_table *table, int write,
 static void wb_timer_fn(unsigned long unused)
 {
 	if (pdflush_operation(wb_kupdate, 0) < 0)
-		mod_timer(&wb_timer, jiffies + HZ); /* delay 1 second */
+		mod_timer(&wb_timer, round_jiffies(jiffies + HZ)); /* delay 1 second */
 }
 
 static void laptop_flush(unsigned long unused)
diff --git a/mm/slab.c b/mm/slab.c
index 944b205..6003eef 100644
--- a/mm/slab.c
+++ b/mm/slab.c
@@ -467,8 +467,8 @@ struct kmem_cache {
  * OTOH the cpuarrays can contain lots of objects,
  * which could lock up otherwise freeable slabs.
  */
-#define REAPTIMEOUT_CPUC	(2*HZ)
-#define REAPTIMEOUT_LIST3	(4*HZ)
+#define REAPTIMEOUT_CPUC	(12*HZ)
+#define REAPTIMEOUT_LIST3	(20*HZ)
 
 #if STATS
 #define	STATS_INC_ACTIVE(x)	((x)->num_active++)
@@ -959,7 +959,7 @@ static void __devinit start_cpu_timer(int cpu)
 		init_reap_node(cpu);
 		INIT_DELAYED_WORK(reap_work, cache_reap);
 		schedule_delayed_work_on(cpu, reap_work,
-					__round_jiffies_relative(HZ, cpu));
+					__round_jiffies_relative(HZ*4, cpu));
 	}
 }
 
diff --git a/net/core/neighbour.c b/net/core/neighbour.c
index 6f3bb73..e6aaa9c 100644
--- a/net/core/neighbour.c
+++ b/net/core/neighbour.c
@@ -696,10 +696,10 @@ next_elt:
 	if (!expire)
 		expire = 1;
 
-	if (expire>HZ)
+	if (expire>4*HZ)
 		mod_timer(&tbl->gc_timer, round_jiffies(now + expire));
 	else
-		mod_timer(&tbl->gc_timer, now + expire);
+		mod_timer(&tbl->gc_timer, round_jiffies(now + 4*HZ));
 
 	write_unlock(&tbl->lock);
 }
-- 
1.5.2-rc2.GIT

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Mark Lord wrote:
>..
> And I just figured out the powertop:  it needed the kernel timers
> patch from the powertop site that was originally for 2.6.21..
> Any chance of somebody actually pushing that patch upstream some year ??
> Patch reproduced here for interest's sake only.
> Hey, look who's on the Signed-off list for it, *Arjan* !
...

Mmm.. hey, I was using this patch on 2.6.23 as well..

I wonder if perhaps this is the culprit for the mysterious 1-second delays
that sometimes slow down resume (from RAM) on my machine from 2 seconds
(normal) to 20 seconds (slow) ?   

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Arjan van de Ven wrote:
> On Fri, 30 Nov 2007 22:44:25 -0500
> Mark Lord <lkml@rtr.ca> wrote:
>>> all you need to do in your kernel module is call
>>>
>>> add_latency_constraint("mark_wants_his_mouse", 5);
>> Okay, and how to change it back again?  (thanks)
> 
> 
> sorry I misremember it's called
> set_acceptable_latency("mark", 5);
> 
> and to remove the constraint again you just do
> 
> remove_acceptable_latency("mark");
> 
> (and there's modify_ too to change existing)
> 
>> Then why not have a sysfs entry for scripts to write tsoro
>> to trigger the exact same end result?  :)
> 
> that's what is in current -mm pretty much
> well not sysfs, but it goes via a file descriptor
> (so that if the process that sets the contraint dies, the latency
> requirement can be given up automatically)
...

But doesn't that approach also make it nearly impossible to script ????

Having to hack source for any apps that one wants to use it on
sounds rather barbaric.. 

(sure I *can* still script it, with background tasksand wait and ..
 but that's getting rather complex again).

Meanwhile.. I'll now cook up a module to try the set/remove_acceptable_latency thing.

Thanks

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Mark Lord wrote:
> Arjan van de Ven wrote:
>> On Fri, 30 Nov 2007 22:44:25 -0500
>> Mark Lord <lkml@rtr.ca> wrote:
>>>> all you need to do in your kernel module is call
...
>> set_acceptable_latency("mark", 5);
>>
>> and to remove the constraint again you just do
>>
>> remove_acceptable_latency("mark");
..
>>> Then why not have a sysfs entry for scripts to write tsoro
>>> to trigger the exact same end result?  :)
>>
>> that's what is in current -mm pretty much
>> well not sysfs, but it goes via a file descriptor
>> (so that if the process that sets the contraint dies, the latency
>> requirement can be given up automatically)
> ...
> 
> But doesn't that approach also make it nearly impossible to script ????
...

Okay, I have a working trivial kernel module that I can load/unload
to tweak this.  But a simple sysfs attribute would be *so much* better
as a permanent kernel feature.

Binary interfaces (fd) are fine for some uses, but not nice for scripts.

Cheers

20000+ wake-ups/second in 2.6.24. Bug?

[Mark Lord]

Mark Lord wrote:
> Arjan van de Ven wrote:
>> On Fri, 30 Nov 2007 22:31:17 -0500
>> Mark Lord <lkml@rtr.ca> wrote:
...
>>> Speaking of which.. what's with powertop on 2.6.24 ???
>>> It's gone from 100-200 wakeups/sec to 20000 wakeups/sec !!!!!!!
>>
>> ho hum.. Lenovo T61?
>> I have some reports that that happens once in a while (but it's not
>> limited to .24 and it's also real, it's not a powertop bug but it
>> actually is waking up that much)..
> ..
> 
> No, it's my hefty Dell Inspiron 9400.
> 
> And I just figured out the powertop:  it needed the kernel timers
> patch from the powertop site that was originally for 2.6.21..
...

Dagnabbit.. it's done it again.. went from 100-200 wakeups/sec
back up to 20000+ wakeups/sec.  This time *with* the powertop patches in place.

Somethings broken in there, but I don't know what.
Or how to make it happen on demand.. it's fine after rebooting again.

???

At least now I know to look when I hear the fan turning on
when the system is otherwise supposed to be idle..

2.6.23 did not have this problem.

Re: 20000+ wake-ups/second in 2.6.24. Bug?

[Arjan van de Ven]

On Sat, 01 Dec 2007 18:43:39 -0500
Mark Lord <lkml@rtr.ca> wrote:

> 
> Dagnabbit.. it's done it again.. went from 100-200 wakeups/sec
> back up to 20000+ wakeups/sec.  This time *with* the powertop patches
> in place.
> 
> Somethings broken in there, but I don't know what.
> Or how to make it happen on demand.. it's fine after rebooting again.
> 
> ???
> 
> At least now I know to look when I hear the fan turning on
> when the system is otherwise supposed to be idle..
> 
> 2.6.23 did not have this problem.

actually we have reports of 2.6.23 having the exact same problem.
The thing is, "something" is causing the system to go into a state
where the cpu throws us right out of the C-state the kernel asks for.

Some people have seen that not loading yenta at all will just make this
not happen at all...


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

Re: 20000+ wake-ups/second in 2.6.24. Bug?

[Mark Lord]

Arjan van de Ven wrote:
> On Sat, 01 Dec 2007 18:43:39 -0500
> Mark Lord <lkml@rtr.ca> wrote:
> 
>> Dagnabbit.. it's done it again.. went from 100-200 wakeups/sec
>> back up to 20000+ wakeups/sec.  This time *with* the powertop patches
>> in place.
>>
>> Somethings broken in there, but I don't know what.
>> Or how to make it happen on demand.. it's fine after rebooting again.
>>
>> ???
>>
>> At least now I know to look when I hear the fan turning on
>> when the system is otherwise supposed to be idle..
>>
>> 2.6.23 did not have this problem.
> 
> actually we have reports of 2.6.23 having the exact same problem.
> The thing is, "something" is causing the system to go into a state
> where the cpu throws us right out of the C-state the kernel asks for.
...

Ahh.  Okay, this machine here did not have the problem on 2.6.23.

> Some people have seen that not loading yenta at all will just make this
> not happen at all...
...

No yenta/cardbus here -- it's all PCIe.
If you have any debug patches that could detect or help next time I see it,
then feel free to toss them this way.

Cheers!

Re: 20000+ wake-ups/second in 2.6.24. Bug?

[Arjan van de Ven]

On Sat, 01 Dec 2007 18:55:48 -0500
Mark Lord <lkml@rtr.ca> wrote:

> Arjan van de Ven wrote:
> > On Sat, 01 Dec 2007 18:43:39 -0500
> > Mark Lord <lkml@rtr.ca> wrote:
> > 
> >> Dagnabbit.. it's done it again.. went from 100-200 wakeups/sec
> >> back up to 20000+ wakeups/sec.  This time *with* the powertop
> >> patches in place.
> >>
> >> Somethings broken in there, but I don't know what.
> >> Or how to make it happen on demand.. it's fine after rebooting
> >> again.
> >>
> >> ???
> >>
> >> At least now I know to look when I hear the fan turning on
> >> when the system is otherwise supposed to be idle..
> >>
> >> 2.6.23 did not have this problem.
> > 
> > actually we have reports of 2.6.23 having the exact same problem.
> > The thing is, "something" is causing the system to go into a state
> > where the cpu throws us right out of the C-state the kernel asks
> > for.
> ...
> 
> Ahh.  Okay, this machine here did not have the problem on 2.6.23.
> 
> > Some people have seen that not loading yenta at all will just make
> > this not happen at all...
> ...
> 
> No yenta/cardbus here -- it's all PCIe.

but.. is yenta loaded or built into the kernel?
or is the config option off?
Also, do you have a TI firewire bridge?
(just asking the common patterns we've sort of kinda seen so far)

> If you have any debug patches that could detect or help next time I
> see it, then feel free to toss them this way.

one thing to try (just as data collection) is to do 
lspci -vvxxx 
before it happens, and then again after it happens
and then diff to see if something changed ;(

(yes this is very crude; we've not been able to chase this one down at
all so far).
-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

Re: 20000+ wake-ups/second in 2.6.24. Bug?

[Andres Freund]

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

Hi,

On Sunday 02 December 2007, Arjan van de Ven wrote in "Re: 20000+ 
wake-ups/second in 2.6.24.   Bug?":
> > > Mark Lord <lkml@rtr.ca> wrote:
> > >> 2.6.23 did not have this problem.
> > > actually we have reports of 2.6.23 having the exact same problem.
> > > The thing is, "something" is causing the system to go into a state
> > > where the cpu throws us right out of the C-state the kernel asks
> > > for.
Just as an Information - I see the same problem here, with an ubuntu 2.6.22 
kernel. I did not report it so far, as I couldnt reliably reproduce it with 
an upstream kernel.
Just as an additional datapoint (Lenovo T60 here).

For me it happens only when using battery. Thats another reason I havent 
reported it so far - it only happened while on the road with work to do. 

If there is any testing needed - just say it.

Greetings, 

Andres

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: 20000+ wake-ups/second in 2.6.24. Bug?

[Rafael J. Wysocki]

On Sunday, 2 of December 2007, Mark Lord wrote:
> Arjan van de Ven wrote:
> > On Sat, 01 Dec 2007 18:43:39 -0500
> > Mark Lord <lkml@rtr.ca> wrote:
> > 
> >> Dagnabbit.. it's done it again.. went from 100-200 wakeups/sec
> >> back up to 20000+ wakeups/sec.  This time *with* the powertop patches
> >> in place.
> >>
> >> Somethings broken in there, but I don't know what.
> >> Or how to make it happen on demand.. it's fine after rebooting again.
> >>
> >> ???
> >>
> >> At least now I know to look when I hear the fan turning on
> >> when the system is otherwise supposed to be idle..
> >>
> >> 2.6.23 did not have this problem.
> > 
> > actually we have reports of 2.6.23 having the exact same problem.
> > The thing is, "something" is causing the system to go into a state
> > where the cpu throws us right out of the C-state the kernel asks for.
> ...
> 
> Ahh.  Okay, this machine here did not have the problem on 2.6.23.

So on this particular machine it is a regression.

I'm tempted to add it to the list of recent regressions in case it appears on
someone else's system on which 2.6.23 works correctly.  Objections?

Rafael

Re: 20000+ wake-ups/second in 2.6.24. Bug?

[Mark Lord]

re:  http://bugzilla.kernel.org/show_bug.cgi?id=9489

This just happened here again.  Or at least I finally noticed that
the fan on my notebook seemed to be running hard for much longer
than usual.  :)

Powertop showed 2.6.24-final running with 10000-36000 wakeups/sec,
with *nothing* significant running:  top showed 97+% idle on both cores.

/proc/interrupts didn't have anything interesting either.

I've put a snap of the powertop output into Bug 9489 (link above),
along with the kernel .config again.

This was after an uptime of many days, with lots of suspend/resume (RAM)
cycles and even a few hibernate/resume cycles.

lspci -vv  doesn't show much different from a fresh reboot
versus what was seem "during" the problem:

--- lspci.rebooted      2008-02-04 12:18:53.000000000 -0500
+++ lspci.during        2008-02-04 12:16:04.000000000 -0500
@@ -44,7 +44,7 @@
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 64 bytes
-       Interrupt: pin A routed to IRQ 21
+       Interrupt: pin A routed to IRQ 20
        Region 0: Memory at efffc000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
@@ -174,7 +174,7 @@
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
-       Interrupt: pin B routed to IRQ 21
+       Interrupt: pin B routed to IRQ 20
        Region 4: I/O ports at bf60 [size=32]

 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 01) (prog-if 00 [UHCI])
@@ -182,7 +182,7 @@
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
-       Interrupt: pin C routed to IRQ 22
+       Interrupt: pin C routed to IRQ 21
        Region 4: I/O ports at bf40 [size=32]

 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 01) (prog-if 00 [UHCI])
@@ -190,7 +190,7 @@
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
-       Interrupt: pin D routed to IRQ 23
+       Interrupt: pin D routed to IRQ 22
        Region 4: I/O ports at bf20 [size=32]

 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01) (prog-if 20 [EHCI])
@@ -296,7 +296,7 @@
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 64
-       Interrupt: pin B routed to IRQ 20
+       Interrupt: pin B routed to IRQ 23
        Region 0: Memory at ef9fd400 (32-bit, non-prefetchable) [size=256]
        Capabilities: [80] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)


Interestingly, lspci *does* show larger differences from "fresh reboot"
to "fresh resume from hibernate" after said reboot.  I don't think this should happen:

--- lspci.rebooted      2008-02-04 12:18:53.000000000 -0500
+++ lspci.afterhib2     2008-02-04 12:22:29.000000000 -0500
@@ -13,7 +13,7 @@
        I/O behind bridge: 0000e000-0000efff
        Memory behind bridge: efd00000-efefffff
        Prefetchable memory behind bridge: 00000000d0000000-00000000dfffffff
-       Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
+       Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
        BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-
        Capabilities: [88] Subsystem: Dell Unknown device 01cd
        Capabilities: [80] Power Management version 2
@@ -24,7 +24,7 @@
        Capabilities: [a0] Express Root Port (Slot+) IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s <64ns, L1 <1us
-               Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
+               Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
                Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 2
@@ -69,12 +69,12 @@
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 64 bytes
        Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0
-       Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
+       Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
        BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
        Capabilities: [40] Express Root Port (Slot+) IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s unlimited, L1 unlimited
-               Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
+               Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
                Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 1
@@ -101,12 +101,12 @@
        Latency: 0, Cache Line Size: 64 bytes
        Bus: primary=00, secondary=0c, subordinate=0c, sec-latency=0
        Memory behind bridge: efc00000-efcfffff
-       Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
+       Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
        BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
        Capabilities: [40] Express Root Port (Slot+) IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s unlimited, L1 unlimited
-               Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
+               Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
                Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 2
@@ -140,7 +140,7 @@
        Capabilities: [40] Express Root Port (Slot+) IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s unlimited, L1 unlimited
-               Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
+               Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
                Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 4


Rafael ?

Re: 20000+ wake-ups/second in 2.6.24. Bug?

[Arjan van de Ven]

On Mon, 04 Feb 2008 12:29:03 -0500
Mark Lord <lkml@rtr.ca> wrote:

> re:  http://bugzilla.kernel.org/show_bug.cgi?id=9489
> 
> This just happened here again.  Or at least I finally noticed that
> the fan on my notebook seemed to be running hard for much longer
> than usual.  :)
> 
> Powertop showed 2.6.24-final running with 10000-36000 wakeups/sec,
> with *nothing* significant running:  top showed 97+% idle on both
> cores.
> 
> -               Device: Errors: Correctable- Non-Fatal- Fatal+
> Unsupported-
> +               Device: Errors: Correctable+ Non-Fatal+ Fatal+
> Unsupported+ Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
>                 Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
>                 Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1,
> Port 1 @@ -101,12 +101,12 @@
>         Latency: 0, Cache Line Size: 64 bytes
>         Bus: primary=00, secondary=0c, subordinate=0c, sec-latency=0
>         Memory behind bridge: efc00000-efcfffff
> -       Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast
> >TAbort- <TAbort- <MAbort- <SERR- <PERR-
> +       Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast
> >TAbort- <TAbort- <MAbort+ <SERR- <PERR- BridgeCtl: Parity- SERR+
> >NoISA- VGA- MAbort- >Reset- FastB2B-

this shows you're having various types of really bad things going on, like PCI
master aborts and the like. Those would certainly be a factor in waking the cpu up;
they're basically hardware exceptions, and I can totally believe (would need to find out
from hw guys how this works in practice) that this sort of serious error would keep the
cpu out of deep C states until resolved.

Re: 20000+ wake-ups/second in 2.6.24. Bug?

[Mark Lord]

Arjan van de Ven wrote:
> On Mon, 04 Feb 2008 12:29:03 -0500
> Mark Lord <lkml@rtr.ca> wrote:
> 
>> re:  http://bugzilla.kernel.org/show_bug.cgi?id=9489
>>
>> This just happened here again.  Or at least I finally noticed that
>> the fan on my notebook seemed to be running hard for much longer
>> than usual.  :)
>>
>> Powertop showed 2.6.24-final running with 10000-36000 wakeups/sec,
>> with *nothing* significant running:  top showed 97+% idle on both
>> cores.
>>
>> -               Device: Errors: Correctable- Non-Fatal- Fatal+
>> Unsupported-
>> +               Device: Errors: Correctable+ Non-Fatal+ Fatal+
>> Unsupported+ Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
>>                 Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
>>                 Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1,
>> Port 1 @@ -101,12 +101,12 @@
>>         Latency: 0, Cache Line Size: 64 bytes
>>         Bus: primary=00, secondary=0c, subordinate=0c, sec-latency=0
>>         Memory behind bridge: efc00000-efcfffff
>> -       Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast
>>> TAbort- <TAbort- <MAbort- <SERR- <PERR-
>> +       Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast
>>> TAbort- <TAbort- <MAbort+ <SERR- <PERR- BridgeCtl: Parity- SERR+
>>> NoISA- VGA- MAbort- >Reset- FastB2B-
> 
> this shows you're having various types of really bad things going on, like PCI
> master aborts and the like. Those would certainly be a factor in waking the cpu up;
> they're basically hardware exceptions, and I can totally believe (would need to find out
> from hw guys how this works in practice) that this sort of serious error would keep the
> cpu out of deep C states until resolved.
..

Or perhaps some initialization on the main-boot patch
just doesn't happen on the resume-from-hibernate paths ?
(either in the BIOS or kernel or drivers ..)

Re: 20000+ wake-ups/second in 2.6.24. Bug?

[Adrian Bunk]

On Sat, Dec 01, 2007 at 06:43:39PM -0500, Mark Lord wrote:
> Mark Lord wrote:
>> Arjan van de Ven wrote:
>>> On Fri, 30 Nov 2007 22:31:17 -0500
>>> Mark Lord <lkml@rtr.ca> wrote:
> ...
>>>> Speaking of which.. what's with powertop on 2.6.24 ???
>>>> It's gone from 100-200 wakeups/sec to 20000 wakeups/sec !!!!!!!
>>>
>>> ho hum.. Lenovo T61?
>>> I have some reports that that happens once in a while (but it's not
>>> limited to .24 and it's also real, it's not a powertop bug but it
>>> actually is waking up that much)..
>> ..
>>
>> No, it's my hefty Dell Inspiron 9400.
>>
>> And I just figured out the powertop:  it needed the kernel timers
>> patch from the powertop site that was originally for 2.6.21..
> ...
>
> Dagnabbit.. it's done it again.. went from 100-200 wakeups/sec
> back up to 20000+ wakeups/sec.  This time *with* the powertop patches in place.

What is the status with an unpatched 2.6.23?

> Somethings broken in there, but I don't know what.
> Or how to make it happen on demand.. it's fine after rebooting again.
>
> ???
>
> At least now I know to look when I hear the fan turning on
> when the system is otherwise supposed to be idle..
>
> 2.6.23 did not have this problem.

Please send the output of "dmesg -s 1000000" for both 2.6.23 and 2.6.24.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: 20000+ wake-ups/second in 2.6.24. Bug?

[Mark Lord]

Adrian Bunk wrote:
> On Sat, Dec 01, 2007 at 06:43:39PM -0500, Mark Lord wrote:
>> Mark Lord wrote:
>>> Arjan van de Ven wrote:
>>>> On Fri, 30 Nov 2007 22:31:17 -0500
>>>> Mark Lord <lkml@rtr.ca> wrote:
>> ...
>>>>> Speaking of which.. what's with powertop on 2.6.24 ???
>>>>> It's gone from 100-200 wakeups/sec to 20000 wakeups/sec !!!!!!!
>>>> ho hum.. Lenovo T61?
>>>> I have some reports that that happens once in a while (but it's not
>>>> limited to .24 and it's also real, it's not a powertop bug but it
>>>> actually is waking up that much)..
>>> ..
>>>
>>> No, it's my hefty Dell Inspiron 9400.
>>>
>>> And I just figured out the powertop:  it needed the kernel timers
>>> patch from the powertop site that was originally for 2.6.21..
>> ...
>>
>> Dagnabbit.. it's done it again.. went from 100-200 wakeups/sec
>> back up to 20000+ wakeups/sec.  This time *with* the powertop patches in place.
> 
> What is the status with an unpatched 2.6.23?
..

More wakeups than without patching, but still on the order of hundreds
of wakeups/sec; nowhere near the 20000+ wakeups/sec range when it goes wonky.

> Please send the output of "dmesg -s 1000000" for both 2.6.23 and 2.6.24.
..

Okay, I'll do a couple of reboots and collect that info for private email,
and maybe post a diff of the two here.

Cheers

Re: 20000+ wake-ups/second in 2.6.24. Bug?

[Adrian Bunk]

On Sun, Dec 02, 2007 at 09:59:57AM -0500, Mark Lord wrote:
> Adrian Bunk wrote:
>> On Sat, Dec 01, 2007 at 06:43:39PM -0500, Mark Lord wrote:
>>> Mark Lord wrote:
>>>> Arjan van de Ven wrote:
>>>>> On Fri, 30 Nov 2007 22:31:17 -0500
>>>>> Mark Lord <lkml@rtr.ca> wrote:
>>> ...
>>>>>> Speaking of which.. what's with powertop on 2.6.24 ???
>>>>>> It's gone from 100-200 wakeups/sec to 20000 wakeups/sec !!!!!!!
>>>>> ho hum.. Lenovo T61?
>>>>> I have some reports that that happens once in a while (but it's not
>>>>> limited to .24 and it's also real, it's not a powertop bug but it
>>>>> actually is waking up that much)..
>>>> ..
>>>>
>>>> No, it's my hefty Dell Inspiron 9400.
>>>>
>>>> And I just figured out the powertop:  it needed the kernel timers
>>>> patch from the powertop site that was originally for 2.6.21..
>>> ...
>>>
>>> Dagnabbit.. it's done it again.. went from 100-200 wakeups/sec
>>> back up to 20000+ wakeups/sec.  This time *with* the powertop patches in place.
>>
>> What is the status with an unpatched 2.6.23?
> ..
>
> More wakeups than without patching, but still on the order of hundreds
> of wakeups/sec; nowhere near the 20000+ wakeups/sec range when it goes wonky.

OK.

>> Please send the output of "dmesg -s 1000000" for both 2.6.23 and 2.6.24.
> ..
>
> Okay, I'll do a couple of reboots and collect that info for private email,
> and maybe post a diff of the two here.

Thanks for doing this.

But please send the dmesg output to the list - it's better when everyone 
who looks at this thread also sees all information.

> Cheers

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: 20000+ wake-ups/second in 2.6.24. Bug?

[Mark Lord]

Here's the info from 2.6.23:  dmesg + lsmod + lspci-v + PowerTop:

[    0.000000] Linux version 2.6.23.8 (root@corey) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #10 SMP PREEMPT Sun Dec 2 10:24:11 EST 2007
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
[    0.000000]  BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 00000000bfed3400 (usable)
[    0.000000]  BIOS-e820: 00000000bfed3400 - 00000000c0000000 (reserved)
[    0.000000]  BIOS-e820: 00000000f0000000 - 00000000f4007000 (reserved)
[    0.000000]  BIOS-e820: 00000000f4008000 - 00000000f400c000 (reserved)
[    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
[    0.000000]  BIOS-e820: 00000000fed20000 - 00000000feda0000 (reserved)
[    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
[    0.000000]  BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
[    0.000000] 2174MB HIGHMEM available.
[    0.000000] 896MB LOWMEM available.
[    0.000000] Entering add_active_range(0, 0, 786131) 0 entries of 256 used
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA             0 ->     4096
[    0.000000]   Normal       4096 ->   229376
[    0.000000]   HighMem    229376 ->   786131
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[1] active PFN ranges
[    0.000000]     0:        0 ->   786131
[    0.000000] On node 0 totalpages: 786131
[    0.000000]   DMA zone: 32 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 4064 pages, LIFO batch:0
[    0.000000]   Normal zone: 1760 pages used for memmap
[    0.000000]   Normal zone: 223520 pages, LIFO batch:31
[    0.000000]   HighMem zone: 4349 pages used for memmap
[    0.000000]   HighMem zone: 552406 pages, LIFO batch:31
[    0.000000]   Movable zone: 0 pages used for memmap
[    0.000000] DMI 2.4 present.
[    0.000000] ACPI: RSDP 000FC1B0, 0014 (r0 DELL  )
[    0.000000] ACPI: RSDT BFED39CD, 0040 (r1 DELL    M07     27D7061B ASL        61)
[    0.000000] ACPI: FACP BFED4800, 0074 (r1 DELL    M07     27D7061B ASL        61)
[    0.000000] ACPI: DSDT BFED5400, 4841 (r1 INT430 SYSFexxx     1001 INTL 20050624)
[    0.000000] ACPI: FACS BFEE3C00, 0040
[    0.000000] ACPI: HPET BFED4F00, 0038 (r1 DELL    M07            1 ASL        61)
[    0.000000] ACPI: APIC BFED5000, 0068 (r1 DELL    M07     27D7061B ASL        47)
[    0.000000] ACPI: MCFG BFED4FC0, 003E (r16 DELL    M07     27D7061B ASL        61)
[    0.000000] ACPI: SLIC BFED509C, 0176 (r1 DELL    M07     27D7061B ASL        61)
[    0.000000] ACPI: BOOT BFED4BC0, 0028 (r1 DELL    M07     27D7061B ASL        61)
[    0.000000] ACPI: SSDT BFED3A0D, 04DC (r1  PmRef    CpuPm     3000 INTL 20050624)
[    0.000000] ACPI: PM-Timer IO Port: 0x1008
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] Processor #0 6:15 APIC version 20
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[    0.000000] Processor #1 6:15 APIC version 20
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ2 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] Enabling APIC mode:  Flat.  Using 1 I/O APICs
[    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] Allocating PCI resources starting at c4000000 (gap: c0000000:30000000)
[    0.000000] swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
[    0.000000] swsusp: Registered nosave memory region: 00000000000a0000 - 0000000000100000
[    0.000000] Built 1 zonelists in Zone order.  Total pages: 779990
[    0.000000] Kernel command line: root=/dev/sda1 ro resume=/dev/sda3 vga=ext sysrq_always_enabled
[    0.000000] debug: sysrq always enabled.
[    0.000000] mapped APIC to ffffb000 (fee00000)
[    0.000000] mapped IOAPIC to ffffa000 (fec00000)
[    0.000000] Enabling fast FPU save and restore... done.
[    0.000000] Enabling unmasked SIMD FPU exception support... done.
[    0.000000] Initializing CPU#0
[    0.000000] CPU 0 irqstacks, hard=c0374000 soft=c0372000
[    0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
[    0.000000] Detected 2161.325 MHz processor.
[    5.995348] Console: colour VGA+ 80x50
[    5.995351] console [tty0] enabled
[    6.001688] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    6.002066] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    6.113010] Memory: 3115000k/3144524k available (1626k kernel code, 28400k reserved, 675k data, 172k init, 2227020k highmem)
[    6.113162] virtual kernel memory layout:
[    6.113162]     fixmap  : 0xfff9b000 - 0xfffff000   ( 400 kB)
[    6.113163]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
[    6.113164]     vmalloc : 0xf8800000 - 0xff7fe000   ( 111 MB)
[    6.113165]     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
[    6.113165]       .init : 0xc0344000 - 0xc036f000   ( 172 kB)
[    6.113166]       .data : 0xc0296a66 - 0xc033f9e0   ( 675 kB)
[    6.113167]       .text : 0xc0100000 - 0xc0296a66   (1626 kB)
[    6.114079] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[    6.114520] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[    6.114974] hpet0: 3 64-bit timers, 14318180 Hz
[    6.199296] Calibrating delay using timer specific routine.. 4327.44 BogoMIPS (lpj=7210311)
[    6.199563] Mount-cache hash table entries: 512
[    6.199784] CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000e3bd 00000000 00000001 00000000
[    6.199789] monitor/mwait feature present.
[    6.199903] using mwait in idle threads.
[    6.200019] CPU: L1 I cache: 32K, L1 D cache: 32K
[    6.200217] CPU: L2 cache: 4096K
[    6.200331] CPU: Physical Processor ID: 0
[    6.200445] CPU: Processor Core ID: 0
[    6.200558] CPU: After all inits, caps: bfebfbff 20100000 00000000 00003940 0000e3bd 00000000 00000001 00000000
[    6.200563] Intel machine check architecture supported.
[    6.200679] Intel machine check reporting enabled on CPU#0.
[    6.200797] Compat vDSO mapped to ffffe000.
[    6.200922] Checking 'hlt' instruction... OK.
[    6.212908] SMP alternatives: switching to UP code
[    6.213510] ACPI: Core revision 20070126
[    6.216032] CPU0: Intel(R) Core(TM)2 CPU         T7400  @ 2.16GHz stepping 06
[    6.216329] SMP alternatives: switching to SMP code
[    6.216743] Booting processor 1/1 eip 3000
[    6.216855] CPU 1 irqstacks, hard=c0375000 soft=c0373000
[    8.103293] Initializing CPU#1
[    8.185199] Calibrating delay using timer specific routine.. 4324.63 BogoMIPS (lpj=7204220)
[    8.185205] CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000e3bd 00000000 00000001 00000000
[    8.185209] monitor/mwait feature present.
[    8.185211] CPU: L1 I cache: 32K, L1 D cache: 32K
[    8.185213] CPU: L2 cache: 4096K
[    8.185214] CPU: Physical Processor ID: 0
[    8.185215] CPU: Processor Core ID: 1
[    8.185216] CPU: After all inits, caps: bfebfbff 20100000 00000000 00003940 0000e3bd 00000000 00000001 00000000
[    8.185220] Intel machine check architecture supported.
[    8.185223] Intel machine check reporting enabled on CPU#1.
[    6.313015] CPU1: Intel(R) Core(TM)2 CPU         T7400  @ 2.16GHz stepping 06
[    6.314330] Total of 2 processors activated (8652.08 BogoMIPS).
[    6.314635] ENABLING IO-APIC IRQs
[    6.314933] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[    6.452320] checking TSC synchronization [CPU#0 -> CPU#1]:
[    6.472490] Measured 4054353953 cycles TSC warp between CPUs, turning off TSC clock.
[    6.472629] Marking TSC unstable due to: check_tsc_sync_source failed.
[    6.472752] Brought up 2 CPUs
[    6.473050] NET: Registered protocol family 16
[    6.473286] ACPI: bus type pci registered
[    6.473458] PCI: Using MMCONFIG
[    6.474324] Setting up standard PCI resources
[    6.479860] ACPI: EC: Look up EC in DSDT
[    6.483426] ACPI: Interpreter enabled
[    6.483539] ACPI: (supports S0 S3 S4 S5)
[    6.483993] ACPI: Using IOAPIC for interrupt routing
[    6.497081] ACPI: PCI Root Bridge [PCI0] (0000:00)
[    6.497724] PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
[    6.497840] PCI quirk: region 1080-10bf claimed by ICH6 GPIO
[    6.499051] PCI: Transparent bridge - 0000:00:1e.0
[    6.499225] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[    6.499534] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
[    6.499606] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIE._PRT]
[    6.499701] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
[    6.499788] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
[    6.499873] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP04._PRT]
[    6.506240] ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 11) *4
[    6.506938] ACPI: PCI Interrupt Link [LNKB] (IRQs *5 7)
[    6.507464] ACPI: PCI Interrupt Link [LNKC] (IRQs *9 10 11)
[    6.508078] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 9 10 11) *3
[    6.508966] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
[    6.510274] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
[    6.511588] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
[    6.512905] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *7 9 10 11 12 14 15)
[    6.514248] Linux Plug and Play Support v0.97 (c) Adam Belay
[    6.514381] pnp: PnP ACPI init
[    6.514496] ACPI: bus type pnp registered
[    6.537611] pnp: PnP ACPI: found 12 devices
[    6.537724] ACPI: ACPI bus type pnp unregistered
[    6.537975] SCSI subsystem initialized
[    8.410882] libata version 2.21 loaded.
[    8.410978] PCI: Using ACPI for IRQ routing
[    8.411090] PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
[    8.418750] ACPI: RTC can wake from S4
[    6.548707] Time: hpet clocksource has been installed.
[    6.548833] Switched to high resolution mode on CPU 0
[    8.422048] Switched to high resolution mode on CPU 1
[    8.432341] pnp: 00:00: iomem range 0x0-0x9fbff could not be reserved
[    8.432455] pnp: 00:00: iomem range 0x9fc00-0x9ffff could not be reserved
[    8.432569] pnp: 00:00: iomem range 0xc0000-0xcffff could not be reserved
[    8.432683] pnp: 00:00: iomem range 0xe0000-0xfffff could not be reserved
[    8.432802] pnp: 00:02: ioport range 0x4d0-0x4d1 has been reserved
[    8.432915] pnp: 00:02: ioport range 0x1000-0x1005 has been reserved
[    8.433029] pnp: 00:02: ioport range 0x1008-0x100f has been reserved
[    8.433145] pnp: 00:03: ioport range 0xf400-0xf4fe has been reserved
[    8.433259] pnp: 00:03: ioport range 0x1006-0x1007 has been reserved
[    8.433373] pnp: 00:03: ioport range 0x100a-0x1059 could not be reserved
[    8.433486] pnp: 00:03: ioport range 0x1060-0x107f has been reserved
[    8.433600] pnp: 00:03: ioport range 0x1080-0x10bf has been reserved
[    8.433714] pnp: 00:03: ioport range 0x10c0-0x10df has been reserved
[    8.433831] pnp: 00:08: ioport range 0xc80-0xcff could not be reserved
[    8.433945] pnp: 00:08: ioport range 0x910-0x91f has been reserved
[    8.434059] pnp: 00:08: ioport range 0x920-0x92f has been reserved
[    8.434172] pnp: 00:08: ioport range 0xcb0-0xcbf has been reserved
[    8.434286] pnp: 00:08: ioport range 0x930-0x97f has been reserved
[    8.434403] pnp: 00:0b: iomem range 0xfed00000-0xfed003ff has been reserved
[    8.464742] PCI: Bridge: 0000:00:01.0
[    8.464857]   IO window: e000-efff
[    8.464966]   MEM window: efd00000-efefffff
[    8.465078]   PREFETCH window: d0000000-dfffffff
[    8.465191] PCI: Bridge: 0000:00:1c.0
[    8.465302]   IO window: disabled.
[    8.465416]   MEM window: disabled.
[    8.465530]   PREFETCH window: disabled.
[    8.465650] PCI: Bridge: 0000:00:1c.1
[    8.465761]   IO window: disabled.
[    8.465875]   MEM window: efc00000-efcfffff
[    8.465985]   PREFETCH window: disabled.
[    8.466100] PCI: Bridge: 0000:00:1c.3
[    8.466213]   IO window: d000-dfff
[    8.466327]   MEM window: efa00000-efbfffff
[    8.466441]   PREFETCH window: e0000000-e01fffff
[    8.466557] PCI: Bridge: 0000:00:1e.0
[    8.466668]   IO window: disabled.
[    8.467899]   MEM window: ef900000-ef9fffff
[    8.468013]   PREFETCH window: disabled.
[    8.468140] ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
[    8.468365] PCI: Setting latency timer of device 0000:00:01.0 to 64
[    8.468383] ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
[    8.468608] PCI: Setting latency timer of device 0000:00:1c.0 to 64
[    8.468628] ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 17
[    8.468854] PCI: Setting latency timer of device 0000:00:1c.1 to 64
[    8.468873] ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 18
[    8.469105] PCI: Setting latency timer of device 0000:00:1c.3 to 64
[    8.469116] PCI: Setting latency timer of device 0000:00:1e.0 to 64
[    8.469148] NET: Registered protocol family 2
[    8.502220] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    8.502413] TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
[    8.503312] TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
[    8.503777] TCP: Hash tables configured (established 131072 bind 65536)
[    8.503891] TCP reno registered
[    8.512288] Simple Boot Flag at 0x79 set to 0x1
[    8.512960] highmem bounce pool size: 64 pages
[    8.513245] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    8.513381] io scheduler noop registered
[    8.513492] io scheduler anticipatory registered
[    8.513615] io scheduler cfq registered (default)
[    8.513822] Boot video device is 0000:01:00.0
[    8.513906] PCI: Setting latency timer of device 0000:00:01.0 to 64
[    8.513922] assign_interrupt_mode Found MSI capability
[    8.514035] Allocate Port Service[0000:00:01.0:pcie00]
[    8.514066] Allocate Port Service[0000:00:01.0:pcie03]
[    8.514119] PCI: Setting latency timer of device 0000:00:1c.0 to 64
[    8.514165] assign_interrupt_mode Found MSI capability
[    8.514278] Allocate Port Service[0000:00:1c.0:pcie00]
[    8.514307] Allocate Port Service[0000:00:1c.0:pcie02]
[    8.514335] Allocate Port Service[0000:00:1c.0:pcie03]
[    8.514415] PCI: Setting latency timer of device 0000:00:1c.1 to 64
[    8.514461] assign_interrupt_mode Found MSI capability
[    8.514574] Allocate Port Service[0000:00:1c.1:pcie00]
[    8.514602] Allocate Port Service[0000:00:1c.1:pcie02]
[    8.514630] Allocate Port Service[0000:00:1c.1:pcie03]
[    8.514716] PCI: Setting latency timer of device 0000:00:1c.3 to 64
[    8.514763] assign_interrupt_mode Found MSI capability
[    8.514872] Allocate Port Service[0000:00:1c.3:pcie00]
[    8.514898] Allocate Port Service[0000:00:1c.3:pcie02]
[    8.514924] Allocate Port Service[0000:00:1c.3:pcie03]
[    8.530609] hpet_resources: 0xfed00000 is busy
[    8.530655] Generic RTC Driver v1.07
[    8.530796] Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
[    8.531197] RAMDISK driver initialized: 4 RAM disks of 8192K size 1024 blocksize
[    8.531504] ata_piix 0000:00:1f.2: version 2.12
[    8.531509] ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
[    8.531978] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 17 (level, low) -> IRQ 17
[    8.532237] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[    8.532303] scsi0 : ata_piix
[    8.532465] scsi1 : ata_piix
[    8.532615] ata1: SATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001bfa0 irq 14
[    8.532755] ata2: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001bfa8 irq 15
[    6.818767] ata1.00: ATA-7: ST9160823AS, 3.AAB, max UDMA/133
[    6.818881] ata1.00: 312581808 sectors, multi 8: LBA48 NCQ (depth 0/32)
[    6.832077] ata1.00: configured for UDMA/133
[    7.144872] ata2.00: ATAPI: SONY DVD RW DW-Q58A, UYS2, max UDMA/33
[    7.311187] ata2.00: configured for UDMA/33
[    9.184147] scsi 0:0:0:0: Direct-Access     ATA      ST9160823AS      3.AA PQ: 0 ANSI: 5
[    9.184358] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
[    9.184489] sd 0:0:0:0: [sda] Write Protect is off
[    9.184601] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    9.184614] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    9.184788] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
[    9.184908] sd 0:0:0:0: [sda] Write Protect is off
[    9.185020] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    9.185033] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    9.185172]  sda: sda1 sda2 sda3
[    9.187971] sd 0:0:0:0: [sda] Attached SCSI disk
[    9.188784] scsi 1:0:0:0: CD-ROM            SONY     DVD RW DW-Q58A   UYS2 PQ: 0 ANSI: 5
[    9.189090] PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[    9.192124] serio: i8042 KBD port at 0x60,0x64 irq 1
[    9.192239] serio: i8042 AUX port at 0x60,0x64 irq 12
[    7.319695] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
[    7.319851] rtc0: alarms up to one month, y3k
[    7.320010] TCP cubic registered
[    7.320125] Starting balanced_irq
[    7.320265] Using IPI No-Shortcut mode
[    7.326131] input: AT Translated Set 2 keyboard as /class/input/input0
[    7.347435] rtc_cmos 00:06: setting the system clock to 2007-12-02 15:29:04 (1196609344)
[    7.387122] kjournald starting.  Commit interval 5 seconds
[    7.387240] EXT3-fs: mounted filesystem with ordered data mode.
[    7.387368] VFS: Mounted root (ext3 filesystem) readonly.
[    7.387570] Freeing unused kernel memory: 172k freed
[    9.834090] NET: Registered protocol family 1
[   16.192600] ACPI: SSDT BFED4134, 0244 (r1  PmRef  Cpu0Ist     3000 INTL 20050624)
[   16.193094] ACPI: SSDT BFED3EE9, 01C6 (r1  PmRef  Cpu0Cst     3001 INTL 20050624)
[   16.193578] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
[   16.194031] ACPI: Processor [CPU0] (supports 8 throttling states)
[   16.194473] ACPI: SSDT BFED4378, 00C4 (r1  PmRef  Cpu1Ist     3000 INTL 20050624)
[   16.194907] ACPI: SSDT BFED40AF, 0085 (r1  PmRef  Cpu1Cst     3000 INTL 20050624)
[   16.195411] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
[   16.195862] ACPI: Processor [CPU1] (supports 8 throttling states)
[   16.213685] input: Lid Switch as /class/input/input1
[   16.213824] ACPI: Lid Switch [LID]
[   16.213977] input: Power Button (CM) as /class/input/input2
[   16.214110] ACPI: Power Button (CM) [PBTN]
[   16.214261] input: Sleep Button (CM) as /class/input/input3
[   16.214389] ACPI: Sleep Button (CM) [SBTN]
[   16.236937] ACPI: Thermal Zone [THM] (53 C)
[   18.240321] ACPI: Battery Slot [BAT0] (battery present)
[   18.252298] Linux agpgart interface v0.102
[   16.388095] usbcore: registered new interface driver usbfs
[   16.388234] usbcore: registered new interface driver hub
[   16.388368] usbcore: registered new device driver usb
[   18.278949] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   18.279093] scsi 1:0:0:0: Attached scsi generic sg1 type 5
[   18.282079] ACPI: AC Adapter [AC] (on-line)
[   18.286860] ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 20 (level, low) -> IRQ 19
[   18.287090] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[   18.287093] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[   18.287510] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
[   18.287682] ehci_hcd 0000:00:1d.7: debug port 1
[   18.287798] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
[   18.287806] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xffa80000
[   18.291801] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[   18.292067] usb usb1: configuration #1 chosen from 1 choice
[   18.292216] hub 1-0:1.0: USB hub found
[   18.292338] hub 1-0:1.0: 8 ports detected
[   16.422010] USB Universal Host Controller Interface driver v3.0
[   18.297635] intel_rng: FWH not detected
[   16.444131] input: PC Speaker as /class/input/input4
[   16.447586] sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
[   16.447702] Uniform CD-ROM driver Revision: 3.20
[   16.447863] sr 1:0:0:0: Attached scsi CD-ROM sr0
[   18.337541] sdhci: Secure Digital Host Controller Interface driver
[   18.337659] sdhci: Copyright(c) Pierre Ossman
[   18.387455] b44.c:v1.01 (Jun 16, 2006)
[   18.387590] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
[   18.391338] eth0: Broadcom 4400 10/100BaseT Ethernet 00:18:8b:a7:bf:42
[   16.519229] ACPI: PCI Interrupt 0000:03:01.0[A] -> GSI 19 (level, low) -> IRQ 18
[   18.463138] firewire_ohci: Added fw-ohci device 0000:03:01.0, OHCI version 1.10
[   18.463341] sdhci: SDHCI controller found at 0000:03:01.1 [1180:0822] (rev 19)
[   18.463494] ACPI: PCI Interrupt 0000:03:01.1[B] -> GSI 18 (level, low) -> IRQ 20
[   18.463780] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 20 (level, low) -> IRQ 19
[   18.464013] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[   18.464016] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[   18.464169] mmc0: SDHCI at 0xef9fd400 irq 20 DMA
[   18.464304] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
[   18.464475] uhci_hcd 0000:00:1d.0: irq 19, io base 0x0000bf80
[   18.464711] usb usb2: configuration #1 chosen from 1 choice
[   18.464861] hub 2-0:1.0: USB hub found
[   18.464978] hub 2-0:1.0: 2 ports detected
[   16.672810] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 21 (level, low) -> IRQ 21
[   16.673047] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[   16.673050] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[   16.673185] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
[   16.674529] uhci_hcd 0000:00:1d.1: irq 21, io base 0x0000bf60
[   16.674741] usb usb3: configuration #1 chosen from 1 choice
[   16.674879] hub 3-0:1.0: USB hub found
[   16.674995] hub 3-0:1.0: 2 ports detected
[   16.681775] usb 1-1: new high speed USB device using ehci_hcd and address 2
[   16.718290] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 22 (level, low) -> IRQ 22
[   16.718549] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[   16.718551] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[   16.718694] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
[   16.718869] uhci_hcd 0000:00:1d.2: irq 22, io base 0x0000bf40
[   16.719095] usb usb4: configuration #1 chosen from 1 choice
[   16.719256] hub 4-0:1.0: USB hub found
[   16.719394] hub 4-0:1.0: 2 ports detected
[   16.756300] usb 1-1: configuration #1 chosen from 1 choice
[   16.756567] hub 1-1:1.0: USB hub found
[   16.756749] hub 1-1:1.0: 4 ports detected
[   16.776034] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 23 (level, low) -> IRQ 23
[   16.776279] PCI: Setting latency timer of device 0000:00:1d.3 to 64
[   16.776282] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[   16.776419] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
[   16.776595] uhci_hcd 0000:00:1d.3: irq 23, io base 0x0000bf20
[   16.776833] usb usb5: configuration #1 chosen from 1 choice
[   16.776990] hub 5-0:1.0: USB hub found
[   16.777119] hub 5-0:1.0: 2 ports detected
[   16.791088] Synaptics Touchpad, model: 1, fw: 6.2, id: 0xfa0b1, caps: 0xa04713/0x200000
[   16.815906] input: SynPS/2 Synaptics TouchPad as /class/input/input5
[   16.836733] mice: PS/2 mouse device common for all mice
[   18.717449] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 21 (level, low) -> IRQ 21
[   18.717694] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[   16.927718] firewire_core: created new fw device fw0 (0 config rom retries, S400)
[   17.030934] usb 1-5: new high speed USB device using ehci_hcd and address 3
[   17.101823] fuse init (API version 7.8)
[   17.155328] usb 1-5: configuration #1 chosen from 1 choice
[   17.155755] hub 1-5:1.0: USB hub found
[   17.156119] hub 1-5:1.0: 4 ports detected
[   17.502517] NET: Registered protocol family 17
[   17.686610] usb 1-5.1: new low speed USB device using ehci_hcd and address 4
[   17.774233] usb 1-5.1: configuration #1 chosen from 1 choice
[   19.649731] usbcore: registered new interface driver usbserial
[   19.650358] drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
[   19.650984] usbcore: registered new interface driver usbserial_generic
[   19.651101] drivers/usb/serial/usb-serial.c: USB Serial Driver core
[   17.780071] drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OS
[   17.780225] drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5
[   17.780384] drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 5.0
[   17.780540] usbcore: registered new interface driver visor
[   17.780658] drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver
[   17.791685] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[   17.793687] pciehp: HPC vendor_id 8086 device_id 27d0 ss_vid 0 ss_did 0
[   17.793852] pciehp: pciehp_enable_slot: no adapter on slot(0011_0002)
[   17.793971] Load service driver hpdriver on pcie device 0000:00:1c.0:pcie02
[   17.793986] pciehp: HPC vendor_id 8086 device_id 27d2 ss_vid 0 ss_did 0
[   19.671719] usbcore: registered new interface driver hiddev
[   17.801165] input: Logitech Optical USB Mouse as /class/input/input6
[   17.801407] input: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-0000:00:1d.7-5.1
[   17.801722] usbcore: registered new interface driver usbhid
[   17.801835] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[   18.794488] pciehp: Device 0000:0c:00.0 already exists at c:0, cannot hot-add
[   18.794607] pciehp: Cannot add device 0xc:0
[   18.794739] Load service driver hpdriver on pcie device 0000:00:1c.1:pcie02
[   18.794759] pciehp: HPC vendor_id 8086 device_id 27d6 ss_vid 0 ss_did 0
[   18.795492] pciehp: pciehp_enable_slot: no adapter on slot(0013_0005)
[   18.795603] Load service driver hpdriver on pcie device 0000:00:1c.3:pcie02
[   18.795609] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[   18.812749] Adding 2064344k swap on /dev/sda3.  Priority:-1 extents:1 across:2064344k
[   18.921802] EXT3 FS on sda1, internal journal
[   19.100555] kjournald starting.  Commit interval 5 seconds
[   19.100683] EXT3 FS on sda2, internal journal
[   19.100686] EXT3-fs: mounted filesystem with ordered data mode.
[   21.259819] b44: eth0: Link is up at 100 Mbps, full duplex.
[   21.259821] b44: eth0: Flow control is off for TX and off for RX.
[   23.723141] IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk>
[   26.877950] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   25.061099] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[   26.934033] NFSD: starting 90-second grace period
[   27.848839] Bluetooth: Core ver 2.11
[   27.848920] NET: Registered protocol family 31
[   27.848923] Bluetooth: HCI device and connection manager initialized
[   27.848927] Bluetooth: HCI socket layer initialized
[   27.896212] Bluetooth: L2CAP ver 2.8
[   27.896219] Bluetooth: L2CAP socket layer initialized
[   26.149743] Bluetooth: RFCOMM socket layer initialized
[   26.149762] Bluetooth: RFCOMM TTY layer initialized
[   26.149765] Bluetooth: RFCOMM ver 1.8
[   29.826083] IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk>

Module                  Size  Used by
microcode              10292  0 
binfmt_misc            11400  1 
rfcomm                 36632  5 
l2cap                  22528  5 rfcomm
bluetooth              50916  4 rfcomm,l2cap
nfs                   235596  0 
nfsd                  206768  17 
exportfs                5184  1 nfsd
lockd                  61000  3 nfs,nfsd
nfs_acl                 3456  2 nfs,nfsd
auth_rpcgss            39648  1 nfsd
sunrpc                160924  9 nfs,nfsd,lockd,nfs_acl,auth_rpcgss
acpi_cpufreq            8980  1 
cpufreq_stats           5840  0 
cpufreq_userspace       4076  0 
cpufreq_ondemand        8268  1 
freq_table              4424  3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand
cpufreq_powersave       1728  0 
container               4864  0 
fan                     4996  0 
firmware_class          9600  1 microcode
usbhid                 27200  0 
hid                    25984  1 usbhid
pciehp                 34968  0 
pci_hotplug            14408  1 pciehp
visor                  18508  0 
af_packet              21128  2 
usbserial              32616  1 visor
fuse                   42196  1 
firewire_sbp2          12804  0 
mousedev               11848  1 
snd_hda_intel         258844  4 
snd_pcm_oss            36960  0 
snd_pcm                66500  3 snd_hda_intel,snd_pcm_oss
snd_mixer_oss          15296  1 snd_pcm_oss
snd_seq_dummy           3716  0 
snd_seq_oss            29568  0 
snd_seq_midi            8032  0 
snd_rawmidi            22560  1 snd_seq_midi
snd_seq_midi_event      6848  2 snd_seq_oss,snd_seq_midi
sdhci                  16908  0 
snd_seq                46800  6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
mmc_core               27652  1 sdhci
pcspkr                  3008  0 
sr_mod                 15268  0 
cdrom                  32480  1 sr_mod
firewire_ohci          16448  0 
firewire_core          39040  2 firewire_sbp2,firewire_ohci
b44                    24972  0 
mii                     5248  1 b44
uhci_hcd               22732  0 
ehci_hcd               32268  0 
ac                      5572  0 
sg                     32412  0 
crc_itu_t               2112  1 firewire_core
usbcore               131016  6 usbhid,visor,usbserial,uhci_hcd,ehci_hcd
intel_agp              23316  0 
agpgart                31564  1 intel_agp
serio_raw               6660  0 
psmouse                29640  0 
battery                12168  0 
snd_timer              21188  3 snd_pcm,snd_seq
snd_seq_device          7756  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd                    48804  15 snd_hda_intel,snd_pcm_oss,snd_pcm,snd_mixer_oss,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore               7904  1 snd
snd_page_alloc          9992  2 snd_hda_intel,snd_pcm
button                  8208  0 
thermal                15516  0 
processor              34304  2 acpi_cpufreq,thermal
unix                   26480  368 

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, fast devsel, latency 0
	Capabilities: [e0] Vendor Specific Information

00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000e000-0000efff
	Memory behind bridge: efd00000-efefffff
	Prefetchable memory behind bridge: 00000000d0000000-00000000dfffffff
	Capabilities: [88] Subsystem: Dell Unknown device 01cd
	Capabilities: [80] Power Management version 2
	Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
	Capabilities: [a0] Express Root Port (Slot+) IRQ 0
	Capabilities: [100] Virtual Channel
	Capabilities: [140] Unknown (5)

00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, fast devsel, latency 0, IRQ 21
	Memory at efffc000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
	Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
	Capabilities: [70] Express Unknown type IRQ 0
	Capabilities: [100] Virtual Channel
	Capabilities: [130] Unknown (5)

00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0
	Capabilities: [40] Express Root Port (Slot+) IRQ 0
	Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
	Capabilities: [90] Subsystem: Dell Unknown device 01cd
	Capabilities: [a0] Power Management version 2
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Unknown (5)

00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=0c, subordinate=0c, sec-latency=0
	Memory behind bridge: efc00000-efcfffff
	Capabilities: [40] Express Root Port (Slot+) IRQ 0
	Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
	Capabilities: [90] Subsystem: Dell Unknown device 01cd
	Capabilities: [a0] Power Management version 2
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Unknown (5)

00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 01) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=0d, subordinate=0e, sec-latency=0
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: efa00000-efbfffff
	Prefetchable memory behind bridge: 00000000e0000000-00000000e01fffff
	Capabilities: [40] Express Root Port (Slot+) IRQ 0
	Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
	Capabilities: [90] Subsystem: Dell Unknown device 01cd
	Capabilities: [a0] Power Management version 2
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Unknown (5)

00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 01) (prog-if 00 [UHCI])
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 0, IRQ 19
	I/O ports at bf80 [size=32]

00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 01) (prog-if 00 [UHCI])
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 0, IRQ 21
	I/O ports at bf60 [size=32]

00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 01) (prog-if 00 [UHCI])
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 0, IRQ 22
	I/O ports at bf40 [size=32]

00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 01) (prog-if 00 [UHCI])
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 0, IRQ 23
	I/O ports at bf20 [size=32]

00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01) (prog-if 20 [EHCI])
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 0, IRQ 19
	Memory at ffa80000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
	Capabilities: [58] Debug port

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1) (prog-if 01 [Subtractive decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=32
	Memory behind bridge: ef900000-ef9fffff
	Capabilities: [50] Subsystem: Dell Unknown device 01cd

00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 0
	Capabilities: [e0] Vendor Specific Information

00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 01) (prog-if 80 [Master])
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 17
	I/O ports at 01f0 [size=8]
	I/O ports at 03f4 [size=1]
	I/O ports at 0170 [size=8]
	I/O ports at 0374 [size=1]
	I/O ports at bfa0 [size=16]
	Capabilities: [70] Power Management version 2

00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
	Subsystem: Dell Unknown device 01cd
	Flags: medium devsel, IRQ 5
	I/O ports at 10c0 [size=32]

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400 (prog-if 00 [VGA])
	Subsystem: Dell Unknown device 2002
	Flags: bus master, fast devsel, latency 0, IRQ 4
	Memory at d0000000 (32-bit, prefetchable) [size=256M]
	I/O ports at ee00 [size=256]
	Memory at efdf0000 (32-bit, non-prefetchable) [size=64K]
	Expansion ROM at efe00000 [disabled] [size=128K]
	Capabilities: [50] Power Management version 2
	Capabilities: [58] Express Legacy Endpoint IRQ 0

03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, fast devsel, latency 64, IRQ 17
	Memory at ef9fe000 (32-bit, non-prefetchable) [size=8K]
	Capabilities: [40] Power Management version 2

03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd Unknown device 0832 (prog-if 10 [OHCI])
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 64, IRQ 18
	Memory at ef9fd800 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [dc] Power Management version 2

03:01.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) (prog-if 01)
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 64, IRQ 20
	Memory at ef9fd400 (32-bit, non-prefetchable) [size=256]
	Capabilities: [80] Power Management version 2

03:01.2 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 01)
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 0, IRQ 9
	Memory at ef9fd500 (32-bit, non-prefetchable) [size=256]
	Capabilities: [80] Power Management version 2

03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
	Subsystem: Dell Unknown device 01cd
	Flags: medium devsel, IRQ 9
	Memory at ef9fd600 (32-bit, non-prefetchable) [size=256]
	Capabilities: [80] Power Management version 2

03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)
	Subsystem: Dell Unknown device 01cd
	Flags: medium devsel, IRQ 9
	Memory at ef9fd700 (32-bit, non-prefetchable) [size=256]
	Capabilities: [80] Power Management version 2

0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
	Subsystem: Intel Corporation Unknown device 1000
	Flags: bus master, fast devsel, latency 0, IRQ 5
	Memory at efcff000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [c8] Power Management version 2
	Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
	Capabilities: [e0] Express Legacy Endpoint IRQ 0
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 6f-5e-72-ff-ff-d2-19-00

PowerTop:

Cn                Avg residency       P-states (frequencies)
C0 (cpu running)        ( 2.9%)         2.17 Ghz     0.0%
C1                0.0ms ( 0.0%)         1.67 Ghz     0.0%
C2                3.8ms ( 9.5%)         1333 Mhz     0.0%
C3                5.2ms (87.6%)         1000 Mhz   100.0%


Wakeups-from-idle per second : 194.5    interval: 5.0s
no ACPI power usage estimate available

Top causes for wakeups:
  31.4% ( 47.0)       <interrupt> : uhci_hcd:usb3, HDA Intel
  25.9% ( 38.8)       <interrupt> : extra timer interrupt
   8.3% ( 12.4)            kicker : schedule_timeout (process_timeout)
   7.5% ( 11.2)              Xorg : do_setitimer (it_real_fn)
   6.7% ( 10.0)     <kernel core> : ehci_work (ehci_watchdog)
   6.4% (  9.6)             artsd : schedule_timeout (process_timeout)
   3.3% (  5.0)            dhcdbd : schedule_timeout (process_timeout)
   1.3% (  2.0)     passkey-agent : schedule_timeout (process_timeout)
   1.3% (  2.0)           klipper : schedule_timeout (process_timeout)
   0.9% (  1.4)       <interrupt> : libata
   0.7% (  1.0)        atieventsd : schedule_timeout (process_timeout)
   0.7% (  1.0)          ifconfig : b44_open (b44_timer)
   0.7% (  1.0)          kwrapper : do_nanosleep (hrtimer_wakeup)
   0.7% (  1.0)             artsd : do_setitimer (it_real_fn)
   0.7% (  1.0)              ntpd : do_setitimer (it_real_fn)
   0.4% (  0.6)              kded : schedule_timeout (process_timeout)
   0.4% (  0.6)          kdesktop : schedule_timeout (process_timeout)
   0.3% (  0.4)           konsole : schedule_timeout (process_timeout)
   0.3% (  0.4)             kirqd : schedule_timeout (process_timeout)
   0.3% (  0.4)     <kernel core> : queue_delayed_work_on (delayed_work_timer_fn)
   0.3% (  0.4)               gpm : do_nanosleep (hrtimer_wakeup)
   0.3% (  0.4)              kwin : schedule_timeout (process_timeout)
   0.1% (  0.2)       <interrupt> : PS/2 keyboard/mouse/touchpad
   0.1% (  0.2)    adept_notifier : schedule_timeout (process_timeout)
   0.1% (  0.2)              Xorg : schedule_timeout (process_timeout)
   0.1% (  0.2)           syslogd : do_setitimer (it_real_fn)
   0.1% (  0.2)              hald : schedule_timeout (process_timeout)
   0.1% (  0.2)     <kernel core> : __netdev_watchdog_up (dev_watchdog)
   0.1% (  0.2)   <kernel module> : nfsacl_decode (delayed_work_timer_fn)
   0.1% (  0.2)         ssh-agent : do_setitimer (it_real_fn)
   0.1% (  0.2)        rpc.idmapd : schedule_timeout (process_timeout)
   0.1% (  0.2)   guidance-power- : schedule_timeout (process_timeout)
   0.1% (  0.2)           konsole : end_that_request_last (laptop_timer_fn)

Re: 20000+ wake-ups/second in 2.6.24. Bug?

[Mark Lord]

Here's the info from 2.6.24:  dmesg + lsmod + lspci-v + PowerTop:

[    0.000000] Linux version 2.6.24-rc3-git5 (root@corey) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #3 SMP PREEMPT Fri Nov 30 22:35:04 EST 2007
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
[    0.000000]  BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 00000000bfed3400 (usable)
[    0.000000]  BIOS-e820: 00000000bfed3400 - 00000000c0000000 (reserved)
[    0.000000]  BIOS-e820: 00000000f0000000 - 00000000f4007000 (reserved)
[    0.000000]  BIOS-e820: 00000000f4008000 - 00000000f400c000 (reserved)
[    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
[    0.000000]  BIOS-e820: 00000000fed20000 - 00000000feda0000 (reserved)
[    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
[    0.000000]  BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
[    0.000000] 2174MB HIGHMEM available.
[    0.000000] 896MB LOWMEM available.
[    0.000000] Entering add_active_range(0, 0, 786131) 0 entries of 256 used
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA             0 ->     4096
[    0.000000]   Normal       4096 ->   229376
[    0.000000]   HighMem    229376 ->   786131
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[1] active PFN ranges
[    0.000000]     0:        0 ->   786131
[    0.000000] On node 0 totalpages: 786131
[    0.000000]   DMA zone: 32 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 4064 pages, LIFO batch:0
[    0.000000]   Normal zone: 1760 pages used for memmap
[    0.000000]   Normal zone: 223520 pages, LIFO batch:31
[    0.000000]   HighMem zone: 4349 pages used for memmap
[    0.000000]   HighMem zone: 552406 pages, LIFO batch:31
[    0.000000]   Movable zone: 0 pages used for memmap
[    0.000000] DMI 2.4 present.
[    0.000000] ACPI: RSDP 000FC1B0, 0014 (r0 DELL  )
[    0.000000] ACPI: RSDT BFED39CD, 0040 (r1 DELL    M07     27D7061B ASL        61)
[    0.000000] ACPI: FACP BFED4800, 0074 (r1 DELL    M07     27D7061B ASL        61)
[    0.000000] ACPI: DSDT BFED5400, 4841 (r1 INT430 SYSFexxx     1001 INTL 20050624)
[    0.000000] ACPI: FACS BFEE3C00, 0040
[    0.000000] ACPI: HPET BFED4F00, 0038 (r1 DELL    M07            1 ASL        61)
[    0.000000] ACPI: APIC BFED5000, 0068 (r1 DELL    M07     27D7061B ASL        47)
[    0.000000] ACPI: MCFG BFED4FC0, 003E (r16 DELL    M07     27D7061B ASL        61)
[    0.000000] ACPI: SLIC BFED509C, 0176 (r1 DELL    M07     27D7061B ASL        61)
[    0.000000] ACPI: BOOT BFED4BC0, 0028 (r1 DELL    M07     27D7061B ASL        61)
[    0.000000] ACPI: SSDT BFED3A0D, 04DC (r1  PmRef    CpuPm     3000 INTL 20050624)
[    0.000000] ACPI: PM-Timer IO Port: 0x1008
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] Processor #0 6:15 APIC version 20
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[    0.000000] Processor #1 6:15 APIC version 20
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ2 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] Enabling APIC mode:  Flat.  Using 1 I/O APICs
[    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] Allocating PCI resources starting at c4000000 (gap: c0000000:30000000)
[    0.000000] swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
[    0.000000] swsusp: Registered nosave memory region: 00000000000a0000 - 0000000000100000
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 779990
[    0.000000] Kernel command line: root=/dev/sda1 ro resume=/dev/sda3 vga=ext sysrq_always_enabled
[    0.000000] debug: sysrq always enabled.
[    0.000000] mapped APIC to ffffb000 (fee00000)
[    0.000000] mapped IOAPIC to ffffa000 (fec00000)
[    0.000000] Enabling fast FPU save and restore... done.
[    0.000000] Enabling unmasked SIMD FPU exception support... done.
[    0.000000] Initializing CPU#0
[    0.000000] CPU 0 irqstacks, hard=c038a000 soft=c0388000
[    0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
[    0.000000] Detected 2161.420 MHz processor.
[    6.428240] Console: colour VGA+ 80x50
[    6.428243] console [tty0] enabled
[    6.434703] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    6.435082] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    6.571914] Memory: 3114916k/3144524k available (1666k kernel code, 28492k reserved, 708k data, 188k init, 2227020k highmem)
[    6.572067] virtual kernel memory layout:
[    6.572068]     fixmap  : 0xfff9b000 - 0xfffff000   ( 400 kB)
[    6.572069]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
[    6.572069]     vmalloc : 0xf8800000 - 0xff7fe000   ( 111 MB)
[    6.572070]     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
[    6.572071]       .init : 0xc0356000 - 0xc0385000   ( 188 kB)
[    6.572072]       .data : 0xc02a0a76 - 0xc0351c00   ( 708 kB)
[    6.572073]       .text : 0xc0100000 - 0xc02a0a76   (1666 kB)
[    6.572993] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[    6.573258] SLUB: Genslabs=11, HWalign=64, Order=0-1, MinObjects=4, CPUs=2, Nodes=1
[    6.573525] hpet clockevent registered
[    6.656724] Calibrating delay using timer specific routine.. 4327.37 BogoMIPS (lpj=7210194)
[    6.656979] Mount-cache hash table entries: 512
[    6.657216] CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000e3bd 00000000 00000001 00000000
[    6.657222] monitor/mwait feature present.
[    6.657336] using mwait in idle threads.
[    6.657452] CPU: L1 I cache: 32K, L1 D cache: 32K
[    6.657650] CPU: L2 cache: 4096K
[    6.657765] CPU: Physical Processor ID: 0
[    6.657879] CPU: Processor Core ID: 0
[    6.657993] CPU: After all inits, caps: bfebfbff 20100000 00000000 00003940 0000e3bd 00000000 00000001 00000000
[    6.658001] Compat vDSO mapped to ffffe000.
[    6.658125] Checking 'hlt' instruction... OK.
[    6.670306] SMP alternatives: switching to UP code
[    6.670903] ACPI: Core revision 20070126
[    6.673425] CPU0: Intel(R) Core(TM)2 CPU         T7400  @ 2.16GHz stepping 06
[    6.673723] SMP alternatives: switching to SMP code
[    6.674136] Booting processor 1/1 eip 3000
[    6.674249] CPU 1 irqstacks, hard=c038b000 soft=c0389000
[    8.564513] Initializing CPU#1
[    8.644461] Calibrating delay using timer specific routine.. 4324.62 BogoMIPS (lpj=7204193)
[    8.644467] CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000e3bd 00000000 00000001 00000000
[    8.644471] monitor/mwait feature present.
[    8.644473] CPU: L1 I cache: 32K, L1 D cache: 32K
[    8.644475] CPU: L2 cache: 4096K
[    8.644476] CPU: Physical Processor ID: 0
[    8.644477] CPU: Processor Core ID: 1
[    8.644478] CPU: After all inits, caps: bfebfbff 20100000 00000000 00003940 0000e3bd 00000000 00000001 00000000
[    6.767099] CPU1: Intel(R) Core(TM)2 CPU         T7400  @ 2.16GHz stepping 06
[    6.768198] Total of 2 processors activated (8652.99 BogoMIPS).
[    6.768508] ENABLING IO-APIC IRQs
[    6.768805] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[    6.906377] checking TSC synchronization [CPU#0 -> CPU#1]:
[    6.926547] Measured 4065529416 cycles TSC warp between CPUs, turning off TSC clock.
[    6.926687] Marking TSC unstable due to: check_tsc_sync_source failed.
[    6.926809] Brought up 2 CPUs
[    6.927051] net_namespace: 64 bytes
[    6.927439] NET: Registered protocol family 16
[    6.927666] ACPI: bus type pci registered
[    6.927837] PCI: Using MMCONFIG
[    6.928704] Setting up standard PCI resources
[    6.933401] ACPI: EC: Look up EC in DSDT
[    6.936970] ACPI: Interpreter enabled
[    6.937081] ACPI: (supports S0 S3 S4 S5)
[    6.937538] ACPI: Using IOAPIC for interrupt routing
[    6.950219] ACPI: PCI Root Bridge [PCI0] (0000:00)
[    6.950910] PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
[    6.951026] PCI quirk: region 1080-10bf claimed by ICH6 GPIO
[    6.952318] PCI: Transparent bridge - 0000:00:1e.0
[    6.952491] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[    6.952806] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
[    6.952879] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIE._PRT]
[    6.952996] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
[    6.953084] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
[    6.953169] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP04._PRT]
[    6.959511] ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 11) *4
[    6.960230] ACPI: PCI Interrupt Link [LNKB] (IRQs *5 7)
[    6.960762] ACPI: PCI Interrupt Link [LNKC] (IRQs *9 10 11)
[    6.961377] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 9 10 11) *3
[    6.962246] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
[    6.963557] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
[    6.964868] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
[    6.966181] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *7 9 10 11 12 14 15)
[    6.967525] Linux Plug and Play Support v0.97 (c) Adam Belay
[    6.967656] pnp: PnP ACPI init
[    6.967772] ACPI: bus type pnp registered
[    6.981084] pnpacpi: exceeded the max number of mem resources: 12
[    6.981200] pnpacpi: exceeded the max number of mem resources: 12
[    6.981314] pnpacpi: exceeded the max number of mem resources: 12
[    6.981429] pnpacpi: exceeded the max number of mem resources: 12
[    6.981544] pnpacpi: exceeded the max number of mem resources: 12
[    6.981658] pnpacpi: exceeded the max number of mem resources: 12
[    6.991731] pnp: PnP ACPI: found 12 devices
[    6.991844] ACPI: ACPI bus type pnp unregistered
[    6.992080] SCSI subsystem initialized
[    6.992214] libata version 3.00 loaded.
[    6.992298] PCI: Using ACPI for IRQ routing
[    6.992411] PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
[    7.002826] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[    7.003277] hpet0: 3 64-bit timers, 14318180 Hz
[    7.004413] ACPI: RTC can wake from S4
[    7.006131] Time: hpet clocksource has been installed.
[    7.006253] Switched to high resolution mode on CPU 0
[    8.884597] Switched to high resolution mode on CPU 1
[    7.012838] system 00:00: iomem range 0x0-0x9fbff could not be reserved
[    7.012954] system 00:00: iomem range 0x9fc00-0x9ffff could not be reserved
[    7.013071] system 00:00: iomem range 0xc0000-0xcffff could not be reserved
[    7.013187] system 00:00: iomem range 0xe0000-0xfffff could not be reserved
[    7.013303] system 00:00: iomem range 0x100000-0xbfed33ff could not be reserved
[    7.013444] system 00:00: iomem range 0xbfed3400-0xbfefffff could not be reserved
[    7.013585] system 00:00: iomem range 0xbff00000-0xbfffffff could not be reserved
[    7.013730] system 00:00: iomem range 0xffb00000-0xffffffff could not be reserved
[    7.013872] system 00:00: iomem range 0xfec00000-0xfec0ffff could not be reserved
[    7.014013] system 00:00: iomem range 0xfee00000-0xfee0ffff could not be reserved
[    7.014154] system 00:00: iomem range 0xfed20000-0xfed9ffff could not be reserved
[    7.014296] system 00:00: iomem range 0xffa80000-0xffa83fff could not be reserved
[    7.014440] system 00:02: ioport range 0x4d0-0x4d1 has been reserved
[    7.014555] system 00:02: ioport range 0x1000-0x1005 has been reserved
[    7.014671] system 00:02: ioport range 0x1008-0x100f has been reserved
[    7.014789] system 00:03: ioport range 0xf400-0xf4fe has been reserved
[    7.014905] system 00:03: ioport range 0x1006-0x1007 has been reserved
[    7.015021] system 00:03: ioport range 0x100a-0x1059 could not be reserved
[    7.015136] system 00:03: ioport range 0x1060-0x107f has been reserved
[    7.015251] system 00:03: ioport range 0x1080-0x10bf has been reserved
[    7.015366] system 00:03: ioport range 0x10c0-0x10df has been reserved
[    7.015481] system 00:03: ioport range 0x1010-0x102f has been reserved
[    7.015596] system 00:03: ioport range 0x809-0x809 has been reserved
[    7.015715] system 00:08: ioport range 0xc80-0xcff could not be reserved
[    7.015830] system 00:08: ioport range 0x910-0x91f has been reserved
[    7.017073] system 00:08: ioport range 0x920-0x92f has been reserved
[    7.017188] system 00:08: ioport range 0xcb0-0xcbf has been reserved
[    7.017303] system 00:08: ioport range 0x930-0x97f has been reserved
[    7.017421] system 00:0b: iomem range 0xfed00000-0xfed003ff has been reserved
[    7.047781] PCI: Bridge: 0000:00:01.0
[    7.047894]   IO window: e000-efff
[    7.048006]   MEM window: efd00000-efefffff
[    7.048118]   PREFETCH window: d0000000-dfffffff
[    7.048232] PCI: Bridge: 0000:00:1c.0
[    7.048343]   IO window: disabled.
[    7.048457]   MEM window: disabled.
[    7.048570]   PREFETCH window: disabled.
[    7.048685] PCI: Bridge: 0000:00:1c.1
[    7.048796]   IO window: disabled.
[    7.048911]   MEM window: efc00000-efcfffff
[    7.049025]   PREFETCH window: disabled.
[    7.049139] PCI: Bridge: 0000:00:1c.3
[    7.049252]   IO window: d000-dfff
[    7.049367]   MEM window: efa00000-efbfffff
[    7.049486]   PREFETCH window: e0000000-e01fffff
[    7.049602] PCI: Bridge: 0000:00:1e.0
[    7.049714]   IO window: disabled.
[    7.049828]   MEM window: ef900000-ef9fffff
[    7.049942]   PREFETCH window: disabled.
[    7.050064] ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
[    7.050293] PCI: Setting latency timer of device 0000:00:01.0 to 64
[    7.050310] ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
[    7.050536] PCI: Setting latency timer of device 0000:00:1c.0 to 64
[    7.050554] ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 17
[    7.050780] PCI: Setting latency timer of device 0000:00:1c.1 to 64
[    7.050798] ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 18
[    7.051024] PCI: Setting latency timer of device 0000:00:1c.3 to 64
[    7.051034] PCI: Setting latency timer of device 0000:00:1e.0 to 64
[    7.051041] NET: Registered protocol family 2
[    7.079403] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    7.079689] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[    7.080215] TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
[    7.080623] TCP: Hash tables configured (established 131072 bind 65536)
[    7.080739] TCP reno registered
[    7.089515] Simple Boot Flag at 0x79 set to 0x1
[    8.968226] highmem bounce pool size: 64 pages
[    8.968445] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    8.968586] io scheduler noop registered
[    8.968698] io scheduler anticipatory registered
[    8.968810] io scheduler cfq registered (default)
[    8.969015] Boot video device is 0000:01:00.0
[    8.969096] PCI: Setting latency timer of device 0000:00:01.0 to 64
[    8.969112] assign_interrupt_mode Found MSI capability
[    8.969226] Allocate Port Service[0000:00:01.0:pcie00]
[    8.969256] Allocate Port Service[0000:00:01.0:pcie03]
[    8.969306] PCI: Setting latency timer of device 0000:00:1c.0 to 64
[    8.969351] assign_interrupt_mode Found MSI capability
[    8.969465] Allocate Port Service[0000:00:1c.0:pcie00]
[    8.969492] Allocate Port Service[0000:00:1c.0:pcie02]
[    8.969521] Allocate Port Service[0000:00:1c.0:pcie03]
[    8.969601] PCI: Setting latency timer of device 0000:00:1c.1 to 64
[    8.969647] assign_interrupt_mode Found MSI capability
[    8.969760] Allocate Port Service[0000:00:1c.1:pcie00]
[    8.969788] Allocate Port Service[0000:00:1c.1:pcie02]
[    8.969815] Allocate Port Service[0000:00:1c.1:pcie03]
[    8.969895] PCI: Setting latency timer of device 0000:00:1c.3 to 64
[    8.969941] assign_interrupt_mode Found MSI capability
[    8.970054] Allocate Port Service[0000:00:1c.3:pcie00]
[    8.970087] Allocate Port Service[0000:00:1c.3:pcie02]
[    8.970115] Allocate Port Service[0000:00:1c.3:pcie03]
[    8.987532] hpet_resources: 0xfed00000 is busy
[    8.987577] Generic RTC Driver v1.07
[    8.987718] Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
[    8.988156] RAMDISK driver initialized: 4 RAM disks of 8192K size 1024 blocksize
[    8.988376] ata_piix 0000:00:1f.2: version 2.12
[    8.988382] ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
[    8.988852] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 17 (level, low) -> IRQ 17
[    8.989103] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[    8.989154] scsi0 : ata_piix
[    8.989315] scsi1 : ata_piix
[    8.989574] ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xbfa0 irq 14
[    8.989690] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xbfa8 irq 15
[    7.269512] ata1.00: ATA-7: ST9160823AS, 3.AAB, max UDMA/133
[    7.269627] ata1.00: 312581808 sectors, multi 8: LBA48 NCQ (depth 0/32)
[    7.282831] ata1.00: configured for UDMA/133
[    7.595645] ata2.00: ATAPI: SONY DVD RW DW-Q58A, UYS2, max UDMA/33
[    7.761978] ata2.00: configured for UDMA/33
[    9.640101] scsi 0:0:0:0: Direct-Access     ATA      ST9160823AS      3.AA PQ: 0 ANSI: 5
[    9.640341] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
[    9.640464] sd 0:0:0:0: [sda] Write Protect is off
[    9.640577] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    9.640589] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    9.640764] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
[    9.640885] sd 0:0:0:0: [sda] Write Protect is off
[    9.640999] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    9.641010] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    9.641152]  sda: sda1 sda2 sda3
[    7.768479] sd 0:0:0:0: [sda] Attached SCSI disk
[    7.769266] scsi 1:0:0:0: CD-ROM            SONY     DVD RW DW-Q58A   UYS2 PQ: 0 ANSI: 5
[    7.769578] PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[    7.772487] serio: i8042 KBD port at 0x60,0x64 irq 1
[    7.772603] serio: i8042 AUX port at 0x60,0x64 irq 12
[    7.772840] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
[    7.772992] rtc0: alarms up to one month, y3k
[    7.773129] cpuidle: using governor ladder
[    7.773243] cpuidle: using governor menu
[    7.773399] TCP cubic registered
[    7.773512] Using IPI No-Shortcut mode
[    7.775248] input: AT Translated Set 2 keyboard as /class/input/input0
[    7.800680] rtc_cmos 00:06: setting system clock to 2007-12-02 15:31:19 UTC (1196609479)
[    7.940157] EXT3-fs: mounted filesystem with ordered data mode.
[    7.940275] VFS: Mounted root (ext3 filesystem) readonly.
[    7.940484] Freeing unused kernel memory: 188k freed
[    7.940659] kjournald starting.  Commit interval 5 seconds
[    8.538899] NET: Registered protocol family 1
[   16.854771] ACPI: SSDT BFED4134, 0244 (r1  PmRef  Cpu0Ist     3000 INTL 20050624)
[   16.855251] ACPI: SSDT BFED3EE9, 01C6 (r1  PmRef  Cpu0Cst     3001 INTL 20050624)
[   16.855962] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
[   16.856414] ACPI: Processor [CPU0] (supports 8 throttling states)
[   16.856868] ACPI: SSDT BFED4378, 00C4 (r1  PmRef  Cpu1Ist     3000 INTL 20050624)
[   16.857308] ACPI: SSDT BFED40AF, 0085 (r1  PmRef  Cpu1Cst     3000 INTL 20050624)
[   16.858037] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
[   16.858493] ACPI: Processor [CPU1] (supports 8 throttling states)
[   16.896878] input: Lid Switch as /class/input/input1
[   16.927170] ACPI: Lid Switch [LID]
[   16.927329] input: Power Button (CM) as /class/input/input2
[   16.976666] ACPI: Power Button (CM) [PBTN]
[   16.976830] input: Sleep Button (CM) as /class/input/input3
[   17.023244] ACPI: Sleep Button (CM) [SBTN]
[   17.028529] ACPI: Thermal Zone [THM] (50 C)
[   17.067787] Linux agpgart interface v0.102
[   17.139916] ACPI: AC Adapter [AC] (on-line)
[   17.170598] usbcore: registered new interface driver usbfs
[   17.170739] usbcore: registered new interface driver hub
[   17.171013] usbcore: registered new device driver usb
[   17.224823] intel_rng: FWH not detected
[   17.250299] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   17.250438] scsi 1:0:0:0: Attached scsi generic sg1 type 5
[   17.284638] ricoh-mmc: Ricoh MMC Controller disabling driver
[   17.284761] ricoh-mmc: Copyright(c) Philip Langdale
[   17.284903] ricoh-mmc: Ricoh MMC controller found at 0000:03:01.2 [1180:0843] (rev 1)
[   17.285059] ricoh-mmc: Controller is now disabled.
[   17.349704] ACPI: Battery Slot [BAT0] (battery present)
[   19.227656] input: PC Speaker as /class/input/input4
[   17.395011] sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
[   17.395130] Uniform CD-ROM driver Revision: 3.20
[   17.395270] sr 1:0:0:0: Attached scsi CD-ROM sr0
[   17.406827] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
[   17.422358] USB Universal Host Controller Interface driver v3.0
[   17.422503] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 20 (level, low) -> IRQ 19
[   17.422735] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[   17.422738] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[   17.423086] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
[   17.423260] uhci_hcd 0000:00:1d.0: irq 19, io base 0x0000bf80
[   17.423491] usb usb1: configuration #1 chosen from 1 choice
[   17.423637] hub 1-0:1.0: USB hub found
[   17.423754] hub 1-0:1.0: 2 ports detected
[   17.436471] sdhci: Secure Digital Host Controller Interface driver
[   17.436605] sdhci: Copyright(c) Pierre Ossman
[   17.456802] b44.c:v2.0
[   17.473656] eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 00:18:8b:a7:bf:42
[   17.523397] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 21 (level, low) -> IRQ 20
[   17.523631] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[   17.523635] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[   17.523767] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
[   17.523933] uhci_hcd 0000:00:1d.1: irq 20, io base 0x0000bf60
[   17.524139] usb usb2: configuration #1 chosen from 1 choice
[   17.524275] hub 2-0:1.0: USB hub found
[   17.524390] hub 2-0:1.0: 2 ports detected
[   17.626557] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 22 (level, low) -> IRQ 21
[   17.626866] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[   17.626870] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[   17.627042] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
[   17.627215] uhci_hcd 0000:00:1d.2: irq 21, io base 0x0000bf40
[   17.627425] usb usb3: configuration #1 chosen from 1 choice
[   17.627560] hub 3-0:1.0: USB hub found
[   17.627675] hub 3-0:1.0: 2 ports detected
[   17.714196] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 23 (level, low) -> IRQ 22
[   17.714425] PCI: Setting latency timer of device 0000:00:1d.3 to 64
[   17.714428] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[   17.714561] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
[   17.714760] uhci_hcd 0000:00:1d.3: irq 22, io base 0x0000bf20
[   17.714973] usb usb4: configuration #1 chosen from 1 choice
[   17.715107] hub 4-0:1.0: USB hub found
[   17.715237] hub 4-0:1.0: 2 ports detected
[   19.594226] usb 1-1: new full speed USB device using uhci_hcd and address 2
[   17.722985] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 21 (level, low) -> IRQ 20
[   17.723247] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[   17.731372] usb 1-1: configuration #1 chosen from 1 choice
[   17.731695] hub 1-1:1.0: USB hub found
[   17.732375] hub 1-1:1.0: 4 ports detected
[   17.751024] Synaptics Touchpad, model: 1, fw: 6.2, id: 0xfa0b1, caps: 0xa04713/0x200000
[   17.757327] input: SynPS/2 Synaptics TouchPad as /class/input/input5
[   17.775633] mice: PS/2 mouse device common for all mice
[   19.670449] sdhci: SDHCI controller found at 0000:03:01.1 [1180:0822] (rev 19)
[   19.670612] ACPI: PCI Interrupt 0000:03:01.1[B] -> GSI 18 (level, low) -> IRQ 23
[   19.670888] mmc0: SDHCI at 0xef9fd400 irq 23 DMA
[   17.793175] ACPI: PCI Interrupt 0000:03:01.0[A] -> GSI 19 (level, low) -> IRQ 18
[   17.793443] ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 20 (level, low) -> IRQ 19
[   17.793662] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[   17.793665] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[   17.793801] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
[   17.797847] ehci_hcd 0000:00:1d.7: debug port 1
[   17.797964] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
[   17.797968] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xffa80000
[   17.865404] usb 3-1: new full speed USB device using uhci_hcd and address 2
[   19.744154] firewire_ohci: Added fw-ohci device 0000:03:01.0, OHCI version 1.10
[   17.875381] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[   17.875636] usb usb5: configuration #1 chosen from 1 choice
[   17.875771] hub 5-0:1.0: USB hub found
[   17.875887] hub 5-0:1.0: 8 ports detected
[   17.927015] hub 1-1:1.0: hub_port_status failed (err = -71)
[   17.928236] hub 1-1:1.0: hub_port_status failed (err = -71)
[   17.929010] hub 1-1:1.0: hub_port_status failed (err = -71)
[   17.930009] hub 1-1:1.0: hub_port_status failed (err = -71)
[   17.930143] usb 1-1: USB disconnect, address 2
[   18.094628] fuse init (API version 7.9)
[   18.126244] usb 5-1: new high speed USB device using ehci_hcd and address 2
[   18.127911] NET: Registered protocol family 17
[   18.141750] firewire_core: created new fw device fw0 (0 config rom retries, S400)
[   18.154281] usb 5-1: configuration #1 chosen from 1 choice
[   18.154569] hub 5-1:1.0: USB hub found
[   18.154799] hub 5-1:1.0: 4 ports detected
[   18.404165] usb 5-5: new high speed USB device using ehci_hcd and address 3
[   18.528823] usb 5-5: configuration #1 chosen from 1 choice
[   20.408571] hub 5-5:1.0: USB hub found
[   20.409039] hub 5-5:1.0: 4 ports detected
[   18.823757] usb 5-5.1: new low speed USB device using ehci_hcd and address 4
[   18.911379] usb 5-5.1: configuration #1 chosen from 1 choice
[   20.792148] usbcore: registered new interface driver usbserial
[   20.792278] drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
[   20.792438] usbcore: registered new interface driver usbserial_generic
[   20.792553] drivers/usb/serial/usb-serial.c: USB Serial Driver core
[   20.802099] drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OS
[   20.802256] drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5
[   20.802414] drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 5.0
[   20.802572] usbcore: registered new interface driver visor
[   20.802686] drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver
[   18.979647] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[   18.984069] pciehp: HPC vendor_id 8086 device_id 27d0 ss_vid 0 ss_did 0
[   18.984763] Load service driver hpdriver on pcie device 0000:00:1c.0:pcie02
[   18.984779] pciehp: HPC vendor_id 8086 device_id 27d2 ss_vid 0 ss_did 0
[   19.003648] usbcore: registered new interface driver hiddev
[   19.005605] input: Logitech Optical USB Mouse as /class/input/input6
[   19.023185] input,hidraw0: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-0000:00:1d.7-5.1
[   19.023671] usbcore: registered new interface driver usbhid
[   19.023785] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[   19.984937] pciehp: Device 0000:0c:00.0 already exists at c:0, cannot hot-add
[   19.985057] pciehp: Cannot add device 0xc:0
[   19.985177] Load service driver hpdriver on pcie device 0000:00:1c.1:pcie02
[   19.985199] pciehp: HPC vendor_id 8086 device_id 27d6 ss_vid 0 ss_did 0
[   19.985350] Load service driver hpdriver on pcie device 0000:00:1c.3:pcie02
[   19.985356] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[   21.880534] Adding 2064344k swap on /dev/sda3.  Priority:-1 extents:1 across:2064344k
[   20.110616] EXT3 FS on sda1, internal journal
[   20.272818] kjournald starting.  Commit interval 5 seconds
[   20.272974] EXT3 FS on sda2, internal journal
[   20.272978] EXT3-fs: mounted filesystem with ordered data mode.
[   22.176681] b44: eth0: Link is up at 100 Mbps, full duplex.
[   22.176683] b44: eth0: Flow control is off for TX and off for RX.
[   24.802846] IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk>
[   27.078916] RPC: Registered udp transport module.
[   27.078922] RPC: Registered tcp transport module.
[   27.133817] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   27.233003] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[   27.233578] NFSD: starting 90-second grace period
[   27.904761] Bluetooth: Core ver 2.11
[   27.904849] NET: Registered protocol family 31
[   27.904852] Bluetooth: HCI device and connection manager initialized
[   27.904858] Bluetooth: HCI socket layer initialized
[   27.948472] Bluetooth: L2CAP ver 2.9
[   27.948703] Bluetooth: L2CAP socket layer initialized
[   28.082302] Bluetooth: RFCOMM socket layer initialized
[   28.082317] Bluetooth: RFCOMM TTY layer initialized
[   28.082320] Bluetooth: RFCOMM ver 1.8
[   31.691604] IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk>

Module                  Size  Used by
microcode              10356  0 
binfmt_misc            11336  1 
rfcomm                 37136  5 
l2cap                  23168  5 rfcomm
bluetooth              53476  4 rfcomm,l2cap
nfs                   236684  0 
nfsd                  204848  19 
lockd                  60936  3 nfs,nfsd
nfs_acl                 3392  2 nfs,nfsd
auth_rpcgss            41120  1 nfsd
sunrpc                171996  17 nfs,nfsd,lockd,nfs_acl,auth_rpcgss
exportfs                4672  1 nfsd
acpi_cpufreq            8916  1 
cpufreq_stats           5776  0 
cpufreq_userspace       4012  0 
cpufreq_conservative     7496  0 
cpufreq_powersave       1728  0 
container               4736  0 
fan                     4484  0 
firmware_class          9472  1 microcode
usbhid                 28224  0 
pciehp                 34968  0 
pci_hotplug            13960  1 pciehp
hid                    33408  1 usbhid
visor                  16908  0 
af_packet              20932  2 
usbserial              32808  1 visor
fuse                   45204  1 
firewire_sbp2          14220  0 
mousedev               13128  1 
snd_hda_intel         275036  4 
snd_pcm_oss            36064  0 
snd_pcm                66116  3 snd_hda_intel,snd_pcm_oss
snd_mixer_oss          15296  1 snd_pcm_oss
snd_seq_dummy           3652  0 
snd_seq_oss            29504  0 
snd_seq_midi            8032  0 
snd_rawmidi            22496  1 snd_seq_midi
snd_seq_midi_event      6848  2 snd_seq_oss,snd_seq_midi
snd_seq                46800  6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer              21124  3 snd_pcm,snd_seq
snd_seq_device          7692  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
firewire_ohci          16576  0 
serio_raw               6532  0 
firewire_core          39168  2 firewire_sbp2,firewire_ohci
sdhci                  17028  0 
ehci_hcd               32908  0 
uhci_hcd               23116  0 
b44                    25168  0 
ssb                    26692  1 b44
sr_mod                 15588  0 
cdrom                  32416  1 sr_mod
snd                    48996  15 snd_hda_intel,snd_pcm_oss,snd_pcm,snd_mixer_oss,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
psmouse                29640  0 
pcspkr                  2944  0 
battery                13316  0 
ricoh_mmc               3328  0 
crc_itu_t               2048  1 firewire_core
mmc_core               47044  1 sdhci
sg                     34128  0 
mii                     5184  1 b44
soundcore               7840  1 snd
snd_page_alloc          9928  2 snd_hda_intel,snd_pcm
usbcore               133740  6 usbhid,visor,usbserial,ehci_hcd,uhci_hcd
ac                      6020  0 
power_supply            8452  2 battery,ac
intel_agp              23252  0 
agpgart                31564  1 intel_agp
thermal                15900  0 
button                  8272  0 
processor              36032  4 acpi_cpufreq,thermal
unix                   26544  366 

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, fast devsel, latency 0
	Capabilities: [e0] Vendor Specific Information

00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000e000-0000efff
	Memory behind bridge: efd00000-efefffff
	Prefetchable memory behind bridge: 00000000d0000000-00000000dfffffff
	Capabilities: [88] Subsystem: Dell Unknown device 01cd
	Capabilities: [80] Power Management version 2
	Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
	Capabilities: [a0] Express Root Port (Slot+) IRQ 0
	Capabilities: [100] Virtual Channel
	Capabilities: [140] Unknown (5)

00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, fast devsel, latency 0, IRQ 20
	Memory at efffc000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
	Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
	Capabilities: [70] Express Unknown type IRQ 0
	Capabilities: [100] Virtual Channel
	Capabilities: [130] Unknown (5)

00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0
	Capabilities: [40] Express Root Port (Slot+) IRQ 0
	Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
	Capabilities: [90] Subsystem: Dell Unknown device 01cd
	Capabilities: [a0] Power Management version 2
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Unknown (5)

00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=0c, subordinate=0c, sec-latency=0
	Memory behind bridge: efc00000-efcfffff
	Capabilities: [40] Express Root Port (Slot+) IRQ 0
	Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
	Capabilities: [90] Subsystem: Dell Unknown device 01cd
	Capabilities: [a0] Power Management version 2
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Unknown (5)

00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 01) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=0d, subordinate=0e, sec-latency=0
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: efa00000-efbfffff
	Prefetchable memory behind bridge: 00000000e0000000-00000000e01fffff
	Capabilities: [40] Express Root Port (Slot+) IRQ 0
	Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
	Capabilities: [90] Subsystem: Dell Unknown device 01cd
	Capabilities: [a0] Power Management version 2
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Unknown (5)

00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 01) (prog-if 00 [UHCI])
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 0, IRQ 19
	I/O ports at bf80 [size=32]

00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 01) (prog-if 00 [UHCI])
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 0, IRQ 20
	I/O ports at bf60 [size=32]

00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 01) (prog-if 00 [UHCI])
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 0, IRQ 21
	I/O ports at bf40 [size=32]

00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 01) (prog-if 00 [UHCI])
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 0, IRQ 22
	I/O ports at bf20 [size=32]

00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01) (prog-if 20 [EHCI])
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 0, IRQ 19
	Memory at ffa80000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
	Capabilities: [58] Debug port

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1) (prog-if 01 [Subtractive decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=32
	Memory behind bridge: ef900000-ef9fffff
	Capabilities: [50] Subsystem: Dell Unknown device 01cd

00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 0
	Capabilities: [e0] Vendor Specific Information

00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 01) (prog-if 80 [Master])
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 17
	I/O ports at 01f0 [size=8]
	I/O ports at 03f4 [size=1]
	I/O ports at 0170 [size=8]
	I/O ports at 0374 [size=1]
	I/O ports at bfa0 [size=16]
	Capabilities: [70] Power Management version 2

00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
	Subsystem: Dell Unknown device 01cd
	Flags: medium devsel, IRQ 5
	I/O ports at 10c0 [size=32]

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400 (prog-if 00 [VGA])
	Subsystem: Dell Unknown device 2002
	Flags: bus master, fast devsel, latency 0, IRQ 4
	Memory at d0000000 (32-bit, prefetchable) [size=256M]
	I/O ports at ee00 [size=256]
	Memory at efdf0000 (32-bit, non-prefetchable) [size=64K]
	Expansion ROM at efe00000 [disabled] [size=128K]
	Capabilities: [50] Power Management version 2
	Capabilities: [58] Express Legacy Endpoint IRQ 0

03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, fast devsel, latency 64, IRQ 17
	Memory at ef9fe000 (32-bit, non-prefetchable) [size=8K]
	Capabilities: [40] Power Management version 2

03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd Unknown device 0832 (prog-if 10 [OHCI])
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 64, IRQ 18
	Memory at ef9fd800 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [dc] Power Management version 2

03:01.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) (prog-if 01)
	Subsystem: Dell Unknown device 01cd
	Flags: bus master, medium devsel, latency 64, IRQ 23
	Memory at ef9fd400 (32-bit, non-prefetchable) [size=256]
	Capabilities: [80] Power Management version 2

03:01.2 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 0a)
	Subsystem: Dell Unknown device 01cd
	Flags: medium devsel, IRQ 9
	Memory at ef9fd500 (32-bit, non-prefetchable) [size=256]
	Capabilities: [80] Power Management version 2

03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 05)
	Subsystem: Dell Unknown device 01cd
	Flags: medium devsel, IRQ 9
	Memory at ef9fd600 (32-bit, non-prefetchable) [size=256]
	Capabilities: [80] Power Management version 2

03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff) (prog-if ff)
	!!! Unknown header type 7f

0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
	Subsystem: Intel Corporation Unknown device 1000
	Flags: bus master, fast devsel, latency 0, IRQ 5
	Memory at efcff000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [c8] Power Management version 2
	Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
	Capabilities: [e0] Express Legacy Endpoint IRQ 0
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 6f-5e-72-ff-ff-d2-19-00

PowerTop:

Cn                Avg residency       P-states (frequencies)
C0 (cpu running)        ( 1.9%)         2.17 Ghz     0.0%
C1                0.0ms ( 0.0%)         1.67 Ghz     0.0%
C2                0.1ms ( 0.0%)         1333 Mhz     0.0%
C3                6.9ms (98.0%)         1000 Mhz   100.0%


Wakeups-from-idle per second : 142.9    interval: 5.0s
no ACPI power usage estimate available

Top causes for wakeups:
  36.3% ( 47.0)       <interrupt> : uhci_hcd:usb2, HDA Intel
  10.2% ( 13.2)            kicker : schedule_timeout (process_timeout)
   8.8% ( 11.4)      <kernel IPI> : Rescheduling interrupts
   7.9% ( 10.2)              Xorg : do_setitimer (it_real_fn)
   7.7% ( 10.0)   <kernel module> : ehci_work (ehci_watchdog)
   7.3% (  9.4)       <interrupt> : extra timer interrupt
   6.8% (  8.8)             artsd : schedule_timeout (process_timeout)
   3.7% (  4.8)            dhcdbd : schedule_timeout (process_timeout)
   1.5% (  2.0)       <interrupt> : libata
   1.5% (  2.0)     passkey-agent : schedule_timeout (process_timeout)
   0.8% (  1.0)             artsd : do_setitimer (it_real_fn)
   0.8% (  1.0)           klipper : schedule_timeout (process_timeout)
   0.8% (  1.0)              ntpd : do_setitimer (it_real_fn)
   0.8% (  1.0)        atieventsd : schedule_timeout (process_timeout)
   0.8% (  1.0)          kwrapper : do_nanosleep (hrtimer_wakeup)
   0.8% (  1.0)          ifconfig : b44_open (b44_timer)
   0.5% (  0.6)               gpm : do_nanosleep (hrtimer_wakeup)
   0.3% (  0.4)              Xorg : schedule_timeout (process_timeout)
   0.3% (  0.4)              kded : schedule_timeout (process_timeout)
   0.3% (  0.4)              kmix : schedule_timeout (process_timeout)
   0.2% (  0.2)       <interrupt> : PS/2 keyboard/mouse/touchpad
   0.2% (  0.2)           konsole : schedule_timeout (process_timeout)
   0.2% (  0.2)   guidance-power- : schedule_timeout (process_timeout)
   0.2% (  0.2)     <kernel core> : clocksource_register (clocksource_watchdog)
   0.2% (  0.2)     <kernel core> : neigh_table_init_no_netlink (neigh_periodic_timer)
   0.2% (  0.2)      kio_uiserver : schedule_timeout (process_timeout)
   0.2% (  0.2)   <kernel module> : nfsacl_decode (delayed_work_timer_fn)
   0.2% (  0.2)        rpc.idmapd : schedule_timeout (process_timeout)
   0.2% (  0.2)              kwin : schedule_timeout (process_timeout)
   0.2% (  0.2)     <kernel core> : ip_rt_init (delayed_work_timer_fn)
   0.2% (  0.2)          katapult : schedule_timeout (process_timeout)
   0.2% (  0.2)     <kernel core> : __netdev_watchdog_up (dev_watchdog)
   0.2% (  0.2)    adept_notifier : schedule_timeout (process_timeout)
   0.2% (  0.2)     <kernel core> : end_that_request_last (laptop_timer_fn)

Re: 20000+ wake-ups/second in 2.6.24. Bug?

[Mark Lord]

One .config difference I just noticed:

My 2.6.23 has IRQBALANCE=y, whereas my 2.6.24 lacked that setting.

So I'm going to rebuild 2.6.24 with that option as well.
Maybe it'll fix the slightly choppy behaviour I've noticed
from time to time since switching to 2.6.24 here.

Below are the .config files from 2.6.23 and 2.6.24 (after that change):

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.23.8
# Sun Dec  2 10:19:19 2007
#
CONFIG_X86_32=y
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_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_QUICKLIST=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
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_USER_NS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=16
# CONFIG_CPUSETS is not set
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_RELAY is not set
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_EMBEDDED=y
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=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_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set
CONFIG_BLK_DEV_BSG=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
# CONFIG_IOSCHED_DEADLINE is not set
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"

#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_SMP=y
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_PARAVIRT 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_MCORE2=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# 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_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_XADD=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
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=4
CONFIG_HPET_TIMER=y
CONFIG_NR_CPUS=2
# CONFIG_SCHED_SMT is not set
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_X86_MCE_P4THERMAL is not set
CONFIG_VM86=y
# CONFIG_TOSHIBA is not set
CONFIG_I8K=m
CONFIG_X86_REBOOTFIXUPS=y
CONFIG_MICROCODE=m
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
CONFIG_EDD=m
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
CONFIG_DMIID=y
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_3G_OPT is not set
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_2G_OPT is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_NR_QUICK=1
CONFIG_VIRT_TO_BUS=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_IRQBALANCE=y
# CONFIG_SECCOMP is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_300=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=300
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_HOTPLUG_CPU=y
# CONFIG_COMPAT_VDSO is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND_SMP_POSSIBLE=y
CONFIG_SUSPEND=y
CONFIG_HIBERNATION_SMP_POSSIBLE=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION="/dev/sda3"
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_FAN=m
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=m
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=m
# CONFIG_ACPI_SBS is not set
# CONFIG_APM is not set

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

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not set
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_GX_SUSPMOD is not set
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
# CONFIG_X86_SPEEDSTEP_ICH is not set
# CONFIG_X86_SPEEDSTEP_SMI is not set
# CONFIG_X86_P4_CLOCKMOD is not set
# CONFIG_X86_CPUFREQ_NFORCE2 is not set
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL is not set
# CONFIG_X86_E_POWERSAVER is not set

#
# shared options
#
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
# CONFIG_X86_SPEEDSTEP_LIB is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=m
# CONFIG_HOTPLUG_PCI_PCIE_POLL_EVENT_MODE is not set
CONFIG_PCIEAER=y
CONFIG_ARCH_SUPPORTS_MSI=y
# CONFIG_PCI_MSI is not set
# CONFIG_PCI_DEBUG is not set
# CONFIG_HT_IRQ is not set
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set
CONFIG_HOTPLUG_PCI=m
# CONFIG_HOTPLUG_PCI_FAKE is not set
# CONFIG_HOTPLUG_PCI_COMPAQ is not set
# CONFIG_HOTPLUG_PCI_IBM is not set
# CONFIG_HOTPLUG_PCI_ACPI is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_MISC=m

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=m
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=m
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
CONFIG_NET_KEY=m
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
# 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 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
CONFIG_BRIDGE=m
CONFIG_VLAN_8021Q=m
# CONFIG_DECNET is not set
CONFIG_LLC=m
# 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

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_FIFO=y

#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RR=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_INGRESS=m

#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
# CONFIG_NET_CLS_POLICE is not set
# CONFIG_NET_CLS_IND is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=m

#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
CONFIG_BT_HCIUSB_SCO=y
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIVHCI=m
# CONFIG_AF_RXRPC is not set
CONFIG_FIB_RULES=y

#
# Wireless
#
CONFIG_CFG80211=m
CONFIG_WIRELESS_EXT=y
CONFIG_MAC80211=m
# CONFIG_MAC80211_DEBUG is not set
CONFIG_IEEE80211=m
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=m
CONFIG_IEEE80211_CRYPT_TKIP=m
CONFIG_IEEE80211_SOFTMAC=m
# CONFIG_IEEE80211_SOFTMAC_DEBUG is not set
CONFIG_RFKILL=m
CONFIG_RFKILL_INPUT=m
# CONFIG_NET_9P is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
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 is not set
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=m
# 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=m
CONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=4
CONFIG_BLK_DEV_RAM_SIZE=8192
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_ATA_OVER_ETH=m
CONFIG_MISC_DEVICES=y
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
CONFIG_EEPROM_93CX6=m
# CONFIG_SGI_IOC4 is not set
CONFIG_TIFM_CORE=m
# CONFIG_TIFM_7XX1 is not set
# CONFIG_MSI_LAPTOP is not set
# CONFIG_SONY_LAPTOP is not set
# CONFIG_THINKPAD_ACPI is not set
# CONFIG_IDE 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=y

#
# 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=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=m
# CONFIG_CHR_DEV_SCH is not set

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

#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_LOWLEVEL 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=y
# 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=m
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X 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_CS5535 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_NS87410 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_PATA_PLATFORM is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
# CONFIG_MD_LINEAR is not set
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
CONFIG_BLK_DEV_DM=m
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS is not set

#
# IEEE 1394 (FireWire) support
#
CONFIG_FIREWIRE=m
CONFIG_FIREWIRE_OHCI=m
CONFIG_FIREWIRE_SBP2=m
# 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_IFB is not set
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_MACVLAN=m
CONFIG_EQUALIZER=m
CONFIG_TUN=m
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
CONFIG_PHYLIB=m

#
# MII PHY device drivers
#
# CONFIG_MARVELL_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_BROADCOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
CONFIG_FIXED_PHY=m
CONFIG_FIXED_MII_10_FDX=y
CONFIG_FIXED_MII_100_FDX=y
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# 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_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
CONFIG_B44=m
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS 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_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SC92031 is not set
# CONFIG_NETDEV_1000 is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
CONFIG_WLAN_80211=y
CONFIG_IPW2100=m
CONFIG_IPW2100_MONITOR=y
# CONFIG_IPW2100_DEBUG is not set
CONFIG_IPW2200=m
CONFIG_IPW2200_MONITOR=y
CONFIG_IPW2200_RADIOTAP=y
CONFIG_IPW2200_PROMISCUOUS=y
CONFIG_IPW2200_QOS=y
# CONFIG_IPW2200_DEBUG is not set
# CONFIG_LIBERTAS is not set
# CONFIG_AIRO is not set
# CONFIG_HERMES is not set
# CONFIG_ATMEL is not set
# CONFIG_PRISM54 is not set
CONFIG_USB_ZD1201=m
CONFIG_RTL8187=m
# CONFIG_HOSTAP is not set
CONFIG_BCM43XX=m
# CONFIG_BCM43XX_DEBUG is not set
CONFIG_BCM43XX_DMA=y
CONFIG_BCM43XX_PIO=y
CONFIG_BCM43XX_DMA_AND_PIO_MODE=y
# CONFIG_BCM43XX_DMA_MODE is not set
# CONFIG_BCM43XX_PIO_MODE is not set
CONFIG_ZD1211RW=m
# CONFIG_ZD1211RW_DEBUG is not set

#
# USB Network Adapters
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET_MII=m
CONFIG_USB_USBNET=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
CONFIG_USB_NET_DM9601=m
CONFIG_USB_NET_GL620A=m
CONFIG_USB_NET_NET1080=m
CONFIG_USB_NET_PLUSB=m
# CONFIG_USB_NET_MCS7830 is not set
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_KC2190=y
CONFIG_USB_NET_ZAURUS=m
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
CONFIG_PPPOL2TP=m
# CONFIG_SLIP is not set
CONFIG_SLHC=m
# CONFIG_NET_FC is not set
CONFIG_SHAPER=m
CONFIG_NETCONSOLE=m
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=m

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=m
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_TSDEV is not set
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_EVBUG=m

#
# 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=m
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
# CONFIG_MOUSE_PS2_LIFEBOOK is not set
# CONFIG_MOUSE_PS2_TRACKPOINT is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_SERIAL=m
# 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=y
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_WISTRON_BTNS is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
CONFIG_INPUT_ATI_REMOTE=m
CONFIG_INPUT_ATI_REMOTE2=m
CONFIG_INPUT_KEYSPAN_REMOTE=m
# CONFIG_INPUT_POWERMATE is not set
CONFIG_INPUT_YEALINK=m
CONFIG_INPUT_UINPUT=m

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=m
CONFIG_SERIO_CT82C710=m
CONFIG_SERIO_PCIPS2=m
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
# 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

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

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_IPMI_HANDLER is not set
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_INTEL=m
# CONFIG_HW_RANDOM_AMD is not set
# CONFIG_HW_RANDOM_GEODE is not set
# CONFIG_HW_RANDOM_VIA is not set
CONFIG_NVRAM=m
# CONFIG_RTC is not set
CONFIG_GEN_RTC=y
CONFIG_GEN_RTC_X=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
CONFIG_AGP_ATI=m
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=m
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_I915 is not set
# 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_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_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=m
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=m
CONFIG_I2C_BOARDINFO=y
# CONFIG_I2C_CHARDEV is not set

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set

#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_OCORES 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_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_TINY_USB is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set

#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
# CONFIG_DS1682 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 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=m
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_BATTERY_DS2760 is not set
# CONFIG_HWMON 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_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_PROGEAR is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT 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=m
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# 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=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y

#
# 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=y
# 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_I810 is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# 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_CYBLA 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

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_VIDEO_SELECT=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=m
# 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 is not set

#
# Sound
#
CONFIG_SOUND=m

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

#
# Generic devices
#
CONFIG_SND_AC97_CODEC=m
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# PCI devices
#
CONFIG_SND_AD1889=m
# 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_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_CS5535AUDIO 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 is not set
# 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=m
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
# 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 is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
CONFIG_SND_AC97_POWER_SAVE=y

#
# USB devices
#
CONFIG_SND_USB_AUDIO=m
CONFIG_SND_USB_USX2Y=m
CONFIG_SND_USB_CAIAQ=m
# CONFIG_SND_USB_CAIAQ_INPUT is not set

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

#
# SoC Audio support for SuperH
#

#
# Open Sound System
#
CONFIG_SOUND_PRIME=m
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
CONFIG_SOUND_OSS=m
# CONFIG_SOUND_TRACEINIT is not set
# CONFIG_SOUND_DMAP is not set
# CONFIG_SOUND_SSCAPE is not set
CONFIG_SOUND_VMIDI=m
# CONFIG_SOUND_TRIX is not set
CONFIG_SOUND_MSS=m
CONFIG_SOUND_MPU401=m
# CONFIG_SOUND_PAS is not set
# CONFIG_SOUND_PSS is not set
CONFIG_SOUND_SB=m
# CONFIG_SOUND_YM3812 is not set
CONFIG_SOUND_UART6850=m
# CONFIG_SOUND_AEDSP16 is not set
# CONFIG_SOUND_KAHLUA is not set
CONFIG_AC97_BUS=m
CONFIG_HID_SUPPORT=y
CONFIG_HID=m
# CONFIG_HID_DEBUG is not set

#
# USB Input Devices
#
CONFIG_USB_HID=m
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE 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=m
# CONFIG_USB_DEBUG is not set

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

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=m
# 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=m
# CONFIG_USB_U132_HCD is not set
CONFIG_USB_SL811_HCD=m
# CONFIG_USB_R8A66597_HCD is not set

#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m

#
# 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=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_STORAGE_ALAUDA=y
# CONFIG_USB_STORAGE_KARMA is not set
CONFIG_USB_LIBUSUAL=y

#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m
CONFIG_USB_MON=y

#
# USB port drivers
#

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_AIRCABLE=m
CONFIG_USB_SERIAL_AIRPRIME=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CP2101=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_FUNSOFT=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KEYSPAN_MPR=y
CONFIG_USB_SERIAL_KEYSPAN_USA28=y
CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
CONFIG_USB_SERIAL_KEYSPAN_USA19=y
CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_MOS7720=m
CONFIG_USB_SERIAL_MOS7840=m
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_OTI6858=m
# CONFIG_USB_SERIAL_HP4X is not set
CONFIG_USB_SERIAL_SAFE=m
CONFIG_USB_SERIAL_SAFE_PADDED=y
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
# CONFIG_USB_SERIAL_DEBUG is not set
CONFIG_USB_EZUSB=y

#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
CONFIG_USB_ADUTUX=m
CONFIG_USB_AUERSWALD=m
CONFIG_USB_RIO500=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
# CONFIG_USB_BERRY_CHARGE is not set
CONFIG_USB_LED=m
CONFIG_USB_CYPRESS_CY7C63=m
CONFIG_USB_CYTHERM=m
# CONFIG_USB_PHIDGET is not set
CONFIG_USB_IDMOUSE=m
CONFIG_USB_FTDI_ELAN=m
# CONFIG_USB_APPLEDISPLAY is not set
CONFIG_USB_SISUSBVGA=m
# CONFIG_USB_SISUSBVGA_CON is not set
CONFIG_USB_LD=m
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
CONFIG_USB_TEST=m

#
# USB DSL modem support
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
CONFIG_MMC=m
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set

#
# MMC/SD Card Drivers
#
CONFIG_MMC_BLOCK=m
CONFIG_MMC_BLOCK_BOUNCE=y

#
# MMC/SD Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
# CONFIG_MMC_WBSD is not set
CONFIG_MMC_TIFM_SD=m
# CONFIG_NEW_LEDS is not set
# CONFIG_INFINIBAND is not set
# CONFIG_EDAC is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
CONFIG_RTC_DRV_TEST=m

#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set

#
# SPI RTC drivers
#

#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
CONFIG_RTC_DRV_DS1553=m
# CONFIG_RTC_DRV_STK17TA8 is not set
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_M48T86=m
# CONFIG_RTC_DRV_M48T59 is not set
CONFIG_RTC_DRV_V3020=m

#
# on-CPU RTC drivers
#

#
# DMA Engine support
#
CONFIG_DMA_ENGINE=y

#
# DMA Clients
#
CONFIG_NET_DMA=y

#
# DMA Devices
#
CONFIG_INTEL_IOATDMA=m
# CONFIG_VIRTUALIZATION is not set

#
# Userspace I/O
#
CONFIG_UIO=m
# CONFIG_UIO_CIF is not set

#
# File systems
#
CONFIG_EXT2_FS=m
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT2_FS_XIP=y
CONFIG_FS_XIP=y
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
CONFIG_FUSE_FS=m

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y

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

#
# 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 is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
CONFIG_CONFIGFS_FS=m

#
# 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_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_SUNRPC_BIND34=y
CONFIG_RPCSEC_GSS_KRB5=m
# 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=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
# CONFIG_SYSV68_PARTITION is not set

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="cp437"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
# 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=m
# 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=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m

#
# Distributed Lock Manager
#
CONFIG_DLM=m
# CONFIG_DLM_DEBUG is not set
# CONFIG_INSTRUMENTATION is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_PREEMPT is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# 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_HIGHMEM 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_FRAME_POINTER is not set
# CONFIG_FORCED_INLINING is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_EARLY_PRINTK is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set

#
# Page alloc debug is incompatible with Software Suspend on i386
#
# CONFIG_DEBUG_RODATA is not set
CONFIG_4KSTACKS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ABLKCIPHER=m
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_HASH=m
CONFIG_CRYPTO_MANAGER=m
CONFIG_CRYPTO_HMAC=m
CONFIG_CRYPTO_XCBC=m
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=y
CONFIG_CRYPTO_MD5=m
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_GF128MUL=m
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_LRW=m
CONFIG_CRYPTO_CRYPTD=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_FCRYPT=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_TWOFISH_586=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_CAMELLIA=m
# CONFIG_CRYPTO_TEST is not set
# CONFIG_CRYPTO_HW is not set

#
# Library routines
#
CONFIG_BITREVERSE=m
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=m
CONFIG_CRC7=m
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y

=======================================================================

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.24-rc3-git5
# Sun Dec  2 10:22:10 2007
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
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_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_QUICKLIST=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
# CONFIG_GENERIC_TIME_VSYSCALL is not set
# CONFIG_ZONE_DMA32 is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
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_USER_NS is not set
# CONFIG_PID_NS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=16
# CONFIG_CGROUPS is not set
# CONFIG_FAIR_GROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_EMBEDDED=y
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
# CONFIG_SLUB_DEBUG is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
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=y
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set
CONFIG_BLK_DEV_BSG=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
# CONFIG_IOSCHED_DEADLINE is not set
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"

#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
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_VSMP is not set
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
# 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 is not set
# 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=y
# CONFIG_GENERIC_CPU is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
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=4
CONFIG_HPET_TIMER=y
CONFIG_NR_CPUS=2
# CONFIG_SCHED_SMT is not set
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_MCE is not set
CONFIG_VM86=y
# CONFIG_TOSHIBA is not set
CONFIG_I8K=m
CONFIG_X86_REBOOTFIXUPS=y
CONFIG_MICROCODE=m
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_3G_OPT is not set
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_2G_OPT is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
# CONFIG_SPARSEMEM_VMEMMAP_ENABLE is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_NR_QUICK=1
CONFIG_VIRT_TO_BUS=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_IRQBALANCE=y
# CONFIG_SECCOMP is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_300=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=300
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_HOTPLUG_CPU=y
# 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_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND_SMP_POSSIBLE=y
CONFIG_SUSPEND=y
CONFIG_HIBERNATION_SMP_POSSIBLE=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION="/dev/sda3"
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_FAN=m
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=m
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=m
# CONFIG_ACPI_SBS is not set
# CONFIG_APM 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=m
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not set
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_GX_SUSPMOD is not set
CONFIG_X86_SPEEDSTEP_CENTRINO=m
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y
CONFIG_X86_SPEEDSTEP_ICH=m
# CONFIG_X86_SPEEDSTEP_SMI is not set
# CONFIG_X86_P4_CLOCKMOD is not set
# CONFIG_X86_CPUFREQ_NFORCE2 is not set
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL is not set
# CONFIG_X86_E_POWERSAVER is not set

#
# shared options
#
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
CONFIG_X86_SPEEDSTEP_LIB=m
# CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=m
CONFIG_PCIEAER=y
CONFIG_ARCH_SUPPORTS_MSI=y
# CONFIG_PCI_MSI is not set
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_HT_IRQ is not set
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_PCCARD is not set
CONFIG_HOTPLUG_PCI=m
# CONFIG_HOTPLUG_PCI_FAKE is not set
# CONFIG_HOTPLUG_PCI_COMPAQ is not set
# CONFIG_HOTPLUG_PCI_IBM is not set
# CONFIG_HOTPLUG_PCI_ACPI is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_MISC=m

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=m
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=m
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
CONFIG_NET_KEY=m
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
# 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 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
CONFIG_BRIDGE=m
CONFIG_VLAN_8021Q=m
# CONFIG_DECNET is not set
CONFIG_LLC=m
# 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=y

#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RR=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_INGRESS=m

#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
# CONFIG_NET_ACT_NAT is not set
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
# CONFIG_NET_CLS_POLICE is not set
# CONFIG_NET_CLS_IND is not set
CONFIG_NET_SCH_FIFO=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=m

#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
CONFIG_BT_HCIUSB_SCO=y
# CONFIG_BT_HCIBTSDIO is not set
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_LL=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIVHCI=m
# CONFIG_AF_RXRPC is not set
CONFIG_FIB_RULES=y

#
# Wireless
#
CONFIG_CFG80211=m
CONFIG_NL80211=y
CONFIG_WIRELESS_EXT=y
CONFIG_MAC80211=m
CONFIG_MAC80211_RCSIMPLE=y
# CONFIG_MAC80211_DEBUG is not set
CONFIG_IEEE80211=m
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=m
CONFIG_IEEE80211_CRYPT_TKIP=m
CONFIG_IEEE80211_SOFTMAC=m
# CONFIG_IEEE80211_SOFTMAC_DEBUG is not set
CONFIG_RFKILL=m
CONFIG_RFKILL_INPUT=m
# CONFIG_NET_9P is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
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 is not set
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=m
# 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=m
CONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=4
CONFIG_BLK_DEV_RAM_SIZE=8192
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_ATA_OVER_ETH=m
CONFIG_MISC_DEVICES=y
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
CONFIG_EEPROM_93CX6=m
# CONFIG_SGI_IOC4 is not set
CONFIG_TIFM_CORE=m
# CONFIG_TIFM_7XX1 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_IDE 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=y

#
# 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=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=m
# CONFIG_CHR_DEV_SCH is not set

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

#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
# CONFIG_SCSI_LOWLEVEL 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=y
CONFIG_SATA_MV=m
# CONFIG_SATA_NV is not set
# CONFIG_PDC_ADMA is not set
CONFIG_SATA_QSTOR=m
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SX4 is not set
# CONFIG_SATA_SIL is not set
CONFIG_SATA_SIL24=m
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# 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_CS5535 is not set
# CONFIG_PATA_CS5536 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_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_PATA_PLATFORM is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
# CONFIG_MD_LINEAR is not set
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
CONFIG_BLK_DEV_DM=m
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
CONFIG_DM_UEVENT=y
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
CONFIG_FIREWIRE=m
CONFIG_FIREWIRE_OHCI=m
CONFIG_FIREWIRE_SBP2=m
# 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_IFB is not set
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_MACVLAN=m
CONFIG_EQUALIZER=m
CONFIG_TUN=m
# CONFIG_VETH is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_IP1000 is not set
# CONFIG_ARCNET is not set
CONFIG_PHYLIB=m

#
# MII PHY device drivers
#
# CONFIG_MARVELL_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_BROADCOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
CONFIG_FIXED_PHY=m
CONFIG_FIXED_MII_10_FDX=y
CONFIG_FIXED_MII_100_FDX=y
CONFIG_FIXED_MII_1000_FDX=y
CONFIG_FIXED_MII_AMNT=1
# CONFIG_MDIO_BITBANG is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# 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=m
CONFIG_B44_PCI_AUTOSELECT=y
CONFIG_B44_PCICORE_AUTOSELECT=y
CONFIG_B44_PCI=y
# 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_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SC92031 is not set
CONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_E1000E is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
CONFIG_R8169=m
# CONFIG_R8169_NAPI is not set
# CONFIG_R8169_VLAN is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2 is not set
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
CONFIG_WLAN_80211=y
CONFIG_IPW2100=m
CONFIG_IPW2100_MONITOR=y
# CONFIG_IPW2100_DEBUG is not set
CONFIG_IPW2200=m
CONFIG_IPW2200_MONITOR=y
CONFIG_IPW2200_RADIOTAP=y
CONFIG_IPW2200_PROMISCUOUS=y
CONFIG_IPW2200_QOS=y
# CONFIG_IPW2200_DEBUG is not set
# CONFIG_LIBERTAS is not set
# CONFIG_AIRO is not set
# CONFIG_HERMES is not set
# CONFIG_ATMEL is not set
# CONFIG_PRISM54 is not set
CONFIG_USB_ZD1201=m
CONFIG_RTL8187=m
# CONFIG_ADM8211 is not set
# CONFIG_P54_COMMON is not set
# CONFIG_IWLWIFI is not set
# CONFIG_HOSTAP is not set
CONFIG_BCM43XX=m
# CONFIG_BCM43XX_DEBUG is not set
CONFIG_BCM43XX_DMA=y
CONFIG_BCM43XX_PIO=y
CONFIG_BCM43XX_DMA_AND_PIO_MODE=y
# CONFIG_BCM43XX_DMA_MODE is not set
# CONFIG_BCM43XX_PIO_MODE is not set
CONFIG_B43=m
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
CONFIG_B43_RFKILL=y
# CONFIG_B43_DEBUG is not set
CONFIG_B43_DMA=y
CONFIG_B43_PIO=y
CONFIG_B43_DMA_AND_PIO_MODE=y
# CONFIG_B43_DMA_MODE is not set
# CONFIG_B43_PIO_MODE is not set
CONFIG_B43LEGACY=m
CONFIG_B43LEGACY_PCI_AUTOSELECT=y
CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
# CONFIG_B43LEGACY_DEBUG is not set
CONFIG_B43LEGACY_DMA=y
CONFIG_B43LEGACY_PIO=y
CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
# CONFIG_B43LEGACY_DMA_MODE is not set
# CONFIG_B43LEGACY_PIO_MODE is not set
CONFIG_ZD1211RW=m
# CONFIG_ZD1211RW_DEBUG is not set
# CONFIG_RT2X00 is not set

#
# USB Network Adapters
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
CONFIG_USB_NET_DM9601=m
CONFIG_USB_NET_GL620A=m
CONFIG_USB_NET_NET1080=m
CONFIG_USB_NET_PLUSB=m
# CONFIG_USB_NET_MCS7830 is not set
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_KC2190=y
CONFIG_USB_NET_ZAURUS=m
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
CONFIG_PPPOL2TP=m
# CONFIG_SLIP is not set
CONFIG_SLHC=m
# CONFIG_NET_FC is not set
CONFIG_SHAPER=m
CONFIG_NETCONSOLE=m
# 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=m

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=m
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=m

#
# 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=m
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
# CONFIG_MOUSE_PS2_LIFEBOOK is not set
# CONFIG_MOUSE_PS2_TRACKPOINT is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_SERIAL=m
# 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=y
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_WISTRON_BTNS is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
CONFIG_INPUT_ATI_REMOTE=m
CONFIG_INPUT_ATI_REMOTE2=m
CONFIG_INPUT_KEYSPAN_REMOTE=m
# CONFIG_INPUT_POWERMATE is not set
CONFIG_INPUT_YEALINK=m
CONFIG_INPUT_UINPUT=m

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=m
CONFIG_SERIO_CT82C710=m
CONFIG_SERIO_PCIPS2=m
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
# 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

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

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_INTEL=m
# CONFIG_HW_RANDOM_AMD is not set
# CONFIG_HW_RANDOM_GEODE is not set
# CONFIG_HW_RANDOM_VIA is not set
CONFIG_NVRAM=m
# CONFIG_RTC is not set
CONFIG_GEN_RTC=y
CONFIG_GEN_RTC_X=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_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=m
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=m
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set

#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_OCORES 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_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_TINY_USB is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set

#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
# CONFIG_DS1682 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 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=m
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_BATTERY_DS2760 is not set
# CONFIG_HWMON is not set
# CONFIG_WATCHDOG is not set

#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
CONFIG_SSB=m
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCIHOST=y
CONFIG_SSB_SILENT=y
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y

#
# 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=m
# CONFIG_AGP_ALI is not set
CONFIG_AGP_ATI=m
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=m
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_I915 is not set
# 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=m
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=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y

#
# 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=y
# 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_I810 is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# 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_CYBLA 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=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_VIDEO_SELECT=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=m
# 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 is not set

#
# Sound
#
CONFIG_SOUND=m

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

#
# Generic devices
#
CONFIG_SND_AC97_CODEC=m
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# PCI devices
#
CONFIG_SND_AD1889=m
# 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_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_CS5535AUDIO 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 is not set
# 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=m
# CONFIG_SND_HDA_HWDEP is not set
CONFIG_SND_HDA_CODEC_REALTEK=y
CONFIG_SND_HDA_CODEC_ANALOG=y
CONFIG_SND_HDA_CODEC_SIGMATEL=y
CONFIG_SND_HDA_CODEC_VIA=y
CONFIG_SND_HDA_CODEC_ATIHDMI=y
CONFIG_SND_HDA_CODEC_CONEXANT=y
CONFIG_SND_HDA_CODEC_CMEDIA=y
CONFIG_SND_HDA_CODEC_SI3054=y
CONFIG_SND_HDA_GENERIC=y
CONFIG_SND_HDA_POWER_SAVE=y
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=10
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
# 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 is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_SND_AC97_POWER_SAVE_DEFAULT=10

#
# USB devices
#
CONFIG_SND_USB_AUDIO=m
CONFIG_SND_USB_USX2Y=m
CONFIG_SND_USB_CAIAQ=m
# CONFIG_SND_USB_CAIAQ_INPUT is not set

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

#
# SoC Audio support for SuperH
#

#
# Open Sound System
#
CONFIG_SOUND_PRIME=m
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
CONFIG_SOUND_OSS=m
# CONFIG_SOUND_TRACEINIT is not set
# CONFIG_SOUND_DMAP is not set
# CONFIG_SOUND_SSCAPE is not set
CONFIG_SOUND_VMIDI=m
# CONFIG_SOUND_TRIX is not set
CONFIG_SOUND_MSS=m
CONFIG_SOUND_MPU401=m
# CONFIG_SOUND_PAS is not set
# CONFIG_SOUND_PSS is not set
CONFIG_SOUND_SB=m
# CONFIG_SOUND_YM3812 is not set
CONFIG_SOUND_UART6850=m
# CONFIG_SOUND_AEDSP16 is not set
# CONFIG_SOUND_KAHLUA is not set
CONFIG_AC97_BUS=m
CONFIG_HID_SUPPORT=y
CONFIG_HID=m
# CONFIG_HID_DEBUG is not set
CONFIG_HIDRAW=y

#
# USB Input Devices
#
CONFIG_USB_HID=m
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE 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=m
# CONFIG_USB_DEBUG is not set

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

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_HCD_SSB is not set
# 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=m
# CONFIG_USB_U132_HCD is not set
CONFIG_USB_SL811_HCD=m
# CONFIG_USB_R8A66597_HCD is not set

#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m

#
# 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=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_STORAGE_ALAUDA=y
# CONFIG_USB_STORAGE_KARMA is not set
CONFIG_USB_LIBUSUAL=y

#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m
CONFIG_USB_MON=y

#
# USB port drivers
#

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_AIRCABLE=m
CONFIG_USB_SERIAL_AIRPRIME=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_CH341=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CP2101=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_FUNSOFT=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KEYSPAN_MPR=y
CONFIG_USB_SERIAL_KEYSPAN_USA28=y
CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
CONFIG_USB_SERIAL_KEYSPAN_USA19=y
CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_MOS7720=m
CONFIG_USB_SERIAL_MOS7840=m
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_OTI6858=m
# CONFIG_USB_SERIAL_HP4X is not set
CONFIG_USB_SERIAL_SAFE=m
CONFIG_USB_SERIAL_SAFE_PADDED=y
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
# CONFIG_USB_SERIAL_DEBUG is not set
CONFIG_USB_EZUSB=y

#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
CONFIG_USB_ADUTUX=m
CONFIG_USB_AUERSWALD=m
CONFIG_USB_RIO500=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
# CONFIG_USB_BERRY_CHARGE is not set
CONFIG_USB_LED=m
CONFIG_USB_CYPRESS_CY7C63=m
CONFIG_USB_CYTHERM=m
# CONFIG_USB_PHIDGET is not set
CONFIG_USB_IDMOUSE=m
CONFIG_USB_FTDI_ELAN=m
# CONFIG_USB_APPLEDISPLAY is not set
CONFIG_USB_SISUSBVGA=m
# CONFIG_USB_SISUSBVGA_CON is not set
CONFIG_USB_LD=m
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
CONFIG_USB_TEST=m

#
# USB DSL modem support
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
CONFIG_MMC=m
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set

#
# MMC/SD Card Drivers
#
CONFIG_MMC_BLOCK=m
CONFIG_MMC_BLOCK_BOUNCE=y
# CONFIG_SDIO_UART is not set

#
# MMC/SD Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
CONFIG_MMC_RICOH_MMC=m
# CONFIG_MMC_WBSD is not set
CONFIG_MMC_TIFM_SD=m
# CONFIG_NEW_LEDS is not set
# CONFIG_INFINIBAND is not set
# CONFIG_EDAC is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
CONFIG_RTC_DRV_TEST=m

#
# I2C RTC drivers
#
CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1374=m
CONFIG_RTC_DRV_DS1672=m
CONFIG_RTC_DRV_MAX6900=m
CONFIG_RTC_DRV_RS5C372=m
CONFIG_RTC_DRV_ISL1208=m
CONFIG_RTC_DRV_X1205=m
CONFIG_RTC_DRV_PCF8563=m
CONFIG_RTC_DRV_PCF8583=m
# CONFIG_RTC_DRV_M41T80 is not set

#
# SPI RTC drivers
#

#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
CONFIG_RTC_DRV_DS1553=m
# CONFIG_RTC_DRV_STK17TA8 is not set
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_M48T86=m
# CONFIG_RTC_DRV_M48T59 is not set
CONFIG_RTC_DRV_V3020=m

#
# on-CPU RTC drivers
#
CONFIG_DMADEVICES=y

#
# DMA Devices
#
CONFIG_INTEL_IOATDMA=m
CONFIG_DMA_ENGINE=y

#
# DMA Clients
#
CONFIG_NET_DMA=y
CONFIG_DCA=m
# CONFIG_VIRTUALIZATION is not set

#
# Userspace I/O
#
CONFIG_UIO=m
# CONFIG_UIO_CIF is not set

#
# Firmware Drivers
#
CONFIG_EDD=m
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
CONFIG_DMIID=y

#
# File systems
#
CONFIG_EXT2_FS=m
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT2_FS_XIP=y
CONFIG_FS_XIP=y
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
CONFIG_FUSE_FS=m

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y

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

#
# 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 is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_CONFIGFS_FS=m

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
# 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_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_SUNRPC_BIND34=y
CONFIG_RPCSEC_GSS_KRB5=m
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
CONFIG_CIFS_WEAK_PW_HASH=y
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL 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=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="cp437"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
# 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=m
# 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=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m
CONFIG_DLM=m
# CONFIG_DLM_DEBUG is not set
# CONFIG_INSTRUMENTATION is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_PREEMPT is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# 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_HIGHMEM 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=y
# CONFIG_FRAME_POINTER is not set
# CONFIG_FORCED_INLINING is not set
CONFIG_BOOT_PRINTK_DELAY=y
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_SAMPLES is not set
# CONFIG_EARLY_PRINTK is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set

#
# Page alloc debug is incompatible with Software Suspend on i386
#
# CONFIG_DEBUG_RODATA is not set
CONFIG_4KSTACKS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ABLKCIPHER=m
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_HASH=m
CONFIG_CRYPTO_MANAGER=m
CONFIG_CRYPTO_HMAC=m
CONFIG_CRYPTO_XCBC=m
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=y
CONFIG_CRYPTO_MD5=m
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_GF128MUL=m
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_LRW=m
# CONFIG_CRYPTO_XTS is not set
CONFIG_CRYPTO_CRYPTD=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_FCRYPT=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_TWOFISH_586=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_ANUBIS=m
# CONFIG_CRYPTO_SEED is not set
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_CAMELLIA=m
# CONFIG_CRYPTO_TEST is not set
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_HW is not set

#
# Library routines
#
CONFIG_BITREVERSE=m
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=m
CONFIG_CRC7=m
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Arjan van de Ven wrote:
> On Fri, 30 Nov 2007 22:31:17 -0500
> Mark Lord <lkml@rtr.ca> wrote:
> 
>> Arjan van de Ven wrote:
>>> On Fri, 30 Nov 2007 22:14:08 -0500
>>> Mark Lord <lkml@rtr.ca> wrote:
>>>
>>>>> in -mm there is.. the QoS stuff allows you to set maximum
>>>>> tolerable
>>>> ..
>>>>
>>>> That's encouraging, I think, but not for 2.6.24.
>>>>
>>>>> latency. If your app cant take any latency, you should set
>>>>> those... and the side effect is that the kernel will not do
>>>>> long-latency C-states or P-state transitions..
>>>> ..
>>>>
>>>> I don't mind the cpufreq changing (actually, I want it to drop in
>>>> cpugfreq to save power and keep the fan off), but the C-states just
>>>> kill this app.
>>>>
>>>> The app is VMware.  I force the max_state=1 when launching,
>>> ah but then its' even easier... and can be done in 2.6.24 already.
>>> VMWare after all has a kernel module, and the latency stuff is in
>>> 2.6.23 and 2.6.24 available inside the kernel already.
>> ..
>>
>> Oh, I'm perfectly happy to write my own kernel module if that's what
> 
> all you need to do in your kernel module is call
> 
> add_latency_constraint("mark_wants_his_mouse", 5);
> 
> or so
..

Dredging up an old regression again now:

The "make my own module to replace /sys/.../max_cstate" doesn't work
for the single-core machine we use a lot around here.

VMware is totally sluggish unless I go to another text window and do this:

    while ( true ); do echo -n ; done

At which point VMware performs well again,
the same as with "echo 1 > max_cstate" in 2.6.23.

Anyone got any suggestions on how to fix this regression
or work around it for 2.6.24 ?

Thanks 

RE: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Mark Lord [mailto:lkml@rtr.ca] 
>Sent: Wednesday, January 02, 2008 3:42 PM
>To: Arjan van de Ven
>Cc: Pallipadi, Venkatesh; Andrew Morton; abelay@novell.com; 
>lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
>linux-acpi@vger.kernel.org
>Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>added to -mm tree
>
>Arjan van de Ven wrote:
>> On Fri, 30 Nov 2007 22:31:17 -0500
>> Mark Lord <lkml@rtr.ca> wrote:
>> 
>>> Arjan van de Ven wrote:
>>>> On Fri, 30 Nov 2007 22:14:08 -0500
>>>> Mark Lord <lkml@rtr.ca> wrote:
>>>>
>>>>>> in -mm there is.. the QoS stuff allows you to set maximum
>>>>>> tolerable
>>>>> ..
>>>>>
>>>>> That's encouraging, I think, but not for 2.6.24.
>>>>>
>>>>>> latency. If your app cant take any latency, you should set
>>>>>> those... and the side effect is that the kernel will not do
>>>>>> long-latency C-states or P-state transitions..
>>>>> ..
>>>>>
>>>>> I don't mind the cpufreq changing (actually, I want it to drop in
>>>>> cpugfreq to save power and keep the fan off), but the 
>C-states just
>>>>> kill this app.
>>>>>
>>>>> The app is VMware.  I force the max_state=1 when launching,
>>>> ah but then its' even easier... and can be done in 2.6.24 already.
>>>> VMWare after all has a kernel module, and the latency stuff is in
>>>> 2.6.23 and 2.6.24 available inside the kernel already.
>>> ..
>>>
>>> Oh, I'm perfectly happy to write my own kernel module if that's what
>> 
>> all you need to do in your kernel module is call
>> 
>> add_latency_constraint("mark_wants_his_mouse", 5);
>> 
>> or so
>..
>
>Dredging up an old regression again now:
>
>The "make my own module to replace /sys/.../max_cstate" doesn't work
>for the single-core machine we use a lot around here.
>
>VMware is totally sluggish unless I go to another text window 
>and do this:
>
>    while ( true ); do echo -n ; done
>
>At which point VMware performs well again,
>the same as with "echo 1 > max_cstate" in 2.6.23.
>
>Anyone got any suggestions on how to fix this regression
>or work around it for 2.6.24 ?
>

Easiest and clean way to do it is to have a driver with
set_acceptable_latency() for 1uS or so in init and
remove_acceptable_latency() at exit.

Thanks,
Venki

RE: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Mark Lord [mailto:lkml@rtr.ca] 
>Sent: Wednesday, January 02, 2008 3:42 PM
>To: Arjan van de Ven
>Cc: Pallipadi, Venkatesh; Andrew Morton; abelay@novell.com; 
>lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
>linux-acpi@vger.kernel.org
>Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>added to -mm tree
>
>Arjan van de Ven wrote:
>> On Fri, 30 Nov 2007 22:31:17 -0500
>> Mark Lord <lkml@rtr.ca> wrote:
>> 
>>> Arjan van de Ven wrote:
>>>> On Fri, 30 Nov 2007 22:14:08 -0500
>>>> Mark Lord <lkml@rtr.ca> wrote:
>>>>
>>>>>> in -mm there is.. the QoS stuff allows you to set maximum
>>>>>> tolerable
>>>>> ..
>>>>>
>>>>> That's encouraging, I think, but not for 2.6.24.
>>>>>
>>>>>> latency. If your app cant take any latency, you should set
>>>>>> those... and the side effect is that the kernel will not do
>>>>>> long-latency C-states or P-state transitions..
>>>>> ..
>>>>>
>>>>> I don't mind the cpufreq changing (actually, I want it to drop in
>>>>> cpugfreq to save power and keep the fan off), but the 
>C-states just
>>>>> kill this app.
>>>>>
>>>>> The app is VMware.  I force the max_state=1 when launching,
>>>> ah but then its' even easier... and can be done in 2.6.24 already.
>>>> VMWare after all has a kernel module, and the latency stuff is in
>>>> 2.6.23 and 2.6.24 available inside the kernel already.
>>> ..
>>>
>>> Oh, I'm perfectly happy to write my own kernel module if that's what
>> 
>> all you need to do in your kernel module is call
>> 
>> add_latency_constraint("mark_wants_his_mouse", 5);
>> 
>> or so
>..
>
>Dredging up an old regression again now:
>
>The "make my own module to replace /sys/.../max_cstate" doesn't work
>for the single-core machine we use a lot around here.
>
>VMware is totally sluggish unless I go to another text window 
>and do this:
>
>    while ( true ); do echo -n ; done
>
>At which point VMware performs well again,
>the same as with "echo 1 > max_cstate" in 2.6.23.
>
>Anyone got any suggestions on how to fix this regression
>or work around it for 2.6.24 ?
>

Easiest and clean way to do it is to have a driver with
set_acceptable_latency() for 1uS or so in init and
remove_acceptable_latency() at exit.

Thanks,
Venki

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Andrew Morton]

On Wed, 2 Jan 2008 16:06:20 -0800 "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com> wrote:

>  
> 
> >-----Original Message-----
> >From: Mark Lord [mailto:lkml@rtr.ca] 
> >Sent: Wednesday, January 02, 2008 3:42 PM
> >To: Arjan van de Ven
> >Cc: Pallipadi, Venkatesh; Andrew Morton; abelay@novell.com; 
> >lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
> >linux-acpi@vger.kernel.org
> >Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
> >added to -mm tree
> >
> >Arjan van de Ven wrote:
> >> On Fri, 30 Nov 2007 22:31:17 -0500
> >> Mark Lord <lkml@rtr.ca> wrote:
> >> 
> >>> Arjan van de Ven wrote:
> >>>> On Fri, 30 Nov 2007 22:14:08 -0500
> >>>> Mark Lord <lkml@rtr.ca> wrote:
> >>>>
> >>>>>> in -mm there is.. the QoS stuff allows you to set maximum
> >>>>>> tolerable
> >>>>> ..
> >>>>>
> >>>>> That's encouraging, I think, but not for 2.6.24.
> >>>>>
> >>>>>> latency. If your app cant take any latency, you should set
> >>>>>> those... and the side effect is that the kernel will not do
> >>>>>> long-latency C-states or P-state transitions..
> >>>>> ..
> >>>>>
> >>>>> I don't mind the cpufreq changing (actually, I want it to drop in
> >>>>> cpugfreq to save power and keep the fan off), but the 
> >C-states just
> >>>>> kill this app.
> >>>>>
> >>>>> The app is VMware.  I force the max_state=1 when launching,
> >>>> ah but then its' even easier... and can be done in 2.6.24 already.
> >>>> VMWare after all has a kernel module, and the latency stuff is in
> >>>> 2.6.23 and 2.6.24 available inside the kernel already.
> >>> ..
> >>>
> >>> Oh, I'm perfectly happy to write my own kernel module if that's what
> >> 
> >> all you need to do in your kernel module is call
> >> 
> >> add_latency_constraint("mark_wants_his_mouse", 5);
> >> 
> >> or so
> >..
> >
> >Dredging up an old regression again now:
> >
> >The "make my own module to replace /sys/.../max_cstate" doesn't work
> >for the single-core machine we use a lot around here.
> >
> >VMware is totally sluggish unless I go to another text window 
> >and do this:
> >
> >    while ( true ); do echo -n ; done
> >
> >At which point VMware performs well again,
> >the same as with "echo 1 > max_cstate" in 2.6.23.
> >
> >Anyone got any suggestions on how to fix this regression
> >or work around it for 2.6.24 ?
> >
> 
> Easiest and clean way to do it is to have a driver with
> set_acceptable_latency() for 1uS or so in init and
> remove_acceptable_latency() at exit.

err, you appear to be suggesting that Mark patch his kernel to make it work
as well as 2.6.23?  That would be a wrong answer.

This regression was known six weeks ago.  What do we need to do (or revert)
to fix it in 2.6.24?

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Andrew Morton]

On Wed, 2 Jan 2008 16:06:20 -0800 "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com> wrote:

>  
> 
> >-----Original Message-----
> >From: Mark Lord [mailto:lkml@rtr.ca] 
> >Sent: Wednesday, January 02, 2008 3:42 PM
> >To: Arjan van de Ven
> >Cc: Pallipadi, Venkatesh; Andrew Morton; abelay@novell.com; 
> >lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
> >linux-acpi@vger.kernel.org
> >Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
> >added to -mm tree
> >
> >Arjan van de Ven wrote:
> >> On Fri, 30 Nov 2007 22:31:17 -0500
> >> Mark Lord <lkml@rtr.ca> wrote:
> >> 
> >>> Arjan van de Ven wrote:
> >>>> On Fri, 30 Nov 2007 22:14:08 -0500
> >>>> Mark Lord <lkml@rtr.ca> wrote:
> >>>>
> >>>>>> in -mm there is.. the QoS stuff allows you to set maximum
> >>>>>> tolerable
> >>>>> ..
> >>>>>
> >>>>> That's encouraging, I think, but not for 2.6.24.
> >>>>>
> >>>>>> latency. If your app cant take any latency, you should set
> >>>>>> those... and the side effect is that the kernel will not do
> >>>>>> long-latency C-states or P-state transitions..
> >>>>> ..
> >>>>>
> >>>>> I don't mind the cpufreq changing (actually, I want it to drop in
> >>>>> cpugfreq to save power and keep the fan off), but the 
> >C-states just
> >>>>> kill this app.
> >>>>>
> >>>>> The app is VMware.  I force the max_state=1 when launching,
> >>>> ah but then its' even easier... and can be done in 2.6.24 already.
> >>>> VMWare after all has a kernel module, and the latency stuff is in
> >>>> 2.6.23 and 2.6.24 available inside the kernel already.
> >>> ..
> >>>
> >>> Oh, I'm perfectly happy to write my own kernel module if that's what
> >> 
> >> all you need to do in your kernel module is call
> >> 
> >> add_latency_constraint("mark_wants_his_mouse", 5);
> >> 
> >> or so
> >..
> >
> >Dredging up an old regression again now:
> >
> >The "make my own module to replace /sys/.../max_cstate" doesn't work
> >for the single-core machine we use a lot around here.
> >
> >VMware is totally sluggish unless I go to another text window 
> >and do this:
> >
> >    while ( true ); do echo -n ; done
> >
> >At which point VMware performs well again,
> >the same as with "echo 1 > max_cstate" in 2.6.23.
> >
> >Anyone got any suggestions on how to fix this regression
> >or work around it for 2.6.24 ?
> >
> 
> Easiest and clean way to do it is to have a driver with
> set_acceptable_latency() for 1uS or so in init and
> remove_acceptable_latency() at exit.

err, you appear to be suggesting that Mark patch his kernel to make it work
as well as 2.6.23?  That would be a wrong answer.

This regression was known six weeks ago.  What do we need to do (or revert)
to fix it in 2.6.24?

RE: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Andrew Morton [mailto:akpm@linux-foundation.org] 
>Sent: Wednesday, January 02, 2008 4:52 PM
>To: Pallipadi, Venkatesh
>Cc: Mark Lord; Arjan van de Ven; abelay@novell.com; 
>lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
>linux-acpi@vger.kernel.org
>Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>added to -mm tree
>
>On Wed, 2 Jan 2008 16:06:20 -0800 "Pallipadi, Venkatesh" 
><venkatesh.pallipadi@intel.com> wrote:
>
>>  
>> 
>> >-----Original Message-----
>> >From: Mark Lord [mailto:lkml@rtr.ca] 
>> >Sent: Wednesday, January 02, 2008 3:42 PM
>> >To: Arjan van de Ven
>> >Cc: Pallipadi, Venkatesh; Andrew Morton; abelay@novell.com; 
>> >lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
>> >linux-acpi@vger.kernel.org
>> >Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>> >added to -mm tree
>> >
>> >Arjan van de Ven wrote:
>> >> On Fri, 30 Nov 2007 22:31:17 -0500
>> >> Mark Lord <lkml@rtr.ca> wrote:
>> >> 
>> >>> Arjan van de Ven wrote:
>> >>>> On Fri, 30 Nov 2007 22:14:08 -0500
>> >>>> Mark Lord <lkml@rtr.ca> wrote:
>> >>>>
>> >>>>>> in -mm there is.. the QoS stuff allows you to set maximum
>> >>>>>> tolerable
>> >>>>> ..
>> >>>>>
>> >>>>> That's encouraging, I think, but not for 2.6.24.
>> >>>>>
>> >>>>>> latency. If your app cant take any latency, you should set
>> >>>>>> those... and the side effect is that the kernel will not do
>> >>>>>> long-latency C-states or P-state transitions..
>> >>>>> ..
>> >>>>>
>> >>>>> I don't mind the cpufreq changing (actually, I want it 
>to drop in
>> >>>>> cpugfreq to save power and keep the fan off), but the 
>> >C-states just
>> >>>>> kill this app.
>> >>>>>
>> >>>>> The app is VMware.  I force the max_state=1 when launching,
>> >>>> ah but then its' even easier... and can be done in 
>2.6.24 already.
>> >>>> VMWare after all has a kernel module, and the latency 
>stuff is in
>> >>>> 2.6.23 and 2.6.24 available inside the kernel already.
>> >>> ..
>> >>>
>> >>> Oh, I'm perfectly happy to write my own kernel module if 
>that's what
>> >> 
>> >> all you need to do in your kernel module is call
>> >> 
>> >> add_latency_constraint("mark_wants_his_mouse", 5);
>> >> 
>> >> or so
>> >..
>> >
>> >Dredging up an old regression again now:
>> >
>> >The "make my own module to replace /sys/.../max_cstate" doesn't work
>> >for the single-core machine we use a lot around here.
>> >
>> >VMware is totally sluggish unless I go to another text window 
>> >and do this:
>> >
>> >    while ( true ); do echo -n ; done
>> >
>> >At which point VMware performs well again,
>> >the same as with "echo 1 > max_cstate" in 2.6.23.
>> >
>> >Anyone got any suggestions on how to fix this regression
>> >or work around it for 2.6.24 ?
>> >
>> 
>> Easiest and clean way to do it is to have a driver with
>> set_acceptable_latency() for 1uS or so in init and
>> remove_acceptable_latency() at exit.
>
>err, you appear to be suggesting that Mark patch his kernel to 
>make it work
>as well as 2.6.23?  That would be a wrong answer.
>
>This regression was known six weeks ago.  What do we need to 
>do (or revert)
>to fix it in 2.6.24?
>

As I responded earlier here
http://www.ussg.iu.edu/hypermail/linux/kernel/0711.3/2348.html

This interface cannot be supported cleanly with cpuidle. The cleanest
way to do this is to go through latency interfaces. We have changed all
in kernel drivers to use this new interface. The issue here is, I
removed this sysfs interface without depracting it. We can call it a
regression and we can add it back for the moment. But, this will go from
sysfs sooner or later and latency interface has to be used in future.
And Mark earlier responded in this thread saying he is OK with adding
something in the kernel to get this working, That is the reason I
suggested the above option.

As I saw it 6 weeks back, max_cstate option works as a boot parameter. I
did not see anyone else (apart from Mark) saying they are depending on
this sysfs interface to change max_cstate at run time and Mark said he
can do with the kernel change if possible. Please let me know if you
think this interface is a must fix for .24. I will send a minimal patch
to add it back for .24 for !CPU_IDLE case.

Thanks,
Venki 

RE: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Andrew Morton [mailto:akpm@linux-foundation.org] 
>Sent: Wednesday, January 02, 2008 4:52 PM
>To: Pallipadi, Venkatesh
>Cc: Mark Lord; Arjan van de Ven; abelay@novell.com; 
>lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
>linux-acpi@vger.kernel.org
>Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>added to -mm tree
>
>On Wed, 2 Jan 2008 16:06:20 -0800 "Pallipadi, Venkatesh" 
><venkatesh.pallipadi@intel.com> wrote:
>
>>  
>> 
>> >-----Original Message-----
>> >From: Mark Lord [mailto:lkml@rtr.ca] 
>> >Sent: Wednesday, January 02, 2008 3:42 PM
>> >To: Arjan van de Ven
>> >Cc: Pallipadi, Venkatesh; Andrew Morton; abelay@novell.com; 
>> >lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
>> >linux-acpi@vger.kernel.org
>> >Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>> >added to -mm tree
>> >
>> >Arjan van de Ven wrote:
>> >> On Fri, 30 Nov 2007 22:31:17 -0500
>> >> Mark Lord <lkml@rtr.ca> wrote:
>> >> 
>> >>> Arjan van de Ven wrote:
>> >>>> On Fri, 30 Nov 2007 22:14:08 -0500
>> >>>> Mark Lord <lkml@rtr.ca> wrote:
>> >>>>
>> >>>>>> in -mm there is.. the QoS stuff allows you to set maximum
>> >>>>>> tolerable
>> >>>>> ..
>> >>>>>
>> >>>>> That's encouraging, I think, but not for 2.6.24.
>> >>>>>
>> >>>>>> latency. If your app cant take any latency, you should set
>> >>>>>> those... and the side effect is that the kernel will not do
>> >>>>>> long-latency C-states or P-state transitions..
>> >>>>> ..
>> >>>>>
>> >>>>> I don't mind the cpufreq changing (actually, I want it 
>to drop in
>> >>>>> cpugfreq to save power and keep the fan off), but the 
>> >C-states just
>> >>>>> kill this app.
>> >>>>>
>> >>>>> The app is VMware.  I force the max_state=1 when launching,
>> >>>> ah but then its' even easier... and can be done in 
>2.6.24 already.
>> >>>> VMWare after all has a kernel module, and the latency 
>stuff is in
>> >>>> 2.6.23 and 2.6.24 available inside the kernel already.
>> >>> ..
>> >>>
>> >>> Oh, I'm perfectly happy to write my own kernel module if 
>that's what
>> >> 
>> >> all you need to do in your kernel module is call
>> >> 
>> >> add_latency_constraint("mark_wants_his_mouse", 5);
>> >> 
>> >> or so
>> >..
>> >
>> >Dredging up an old regression again now:
>> >
>> >The "make my own module to replace /sys/.../max_cstate" doesn't work
>> >for the single-core machine we use a lot around here.
>> >
>> >VMware is totally sluggish unless I go to another text window 
>> >and do this:
>> >
>> >    while ( true ); do echo -n ; done
>> >
>> >At which point VMware performs well again,
>> >the same as with "echo 1 > max_cstate" in 2.6.23.
>> >
>> >Anyone got any suggestions on how to fix this regression
>> >or work around it for 2.6.24 ?
>> >
>> 
>> Easiest and clean way to do it is to have a driver with
>> set_acceptable_latency() for 1uS or so in init and
>> remove_acceptable_latency() at exit.
>
>err, you appear to be suggesting that Mark patch his kernel to 
>make it work
>as well as 2.6.23?  That would be a wrong answer.
>
>This regression was known six weeks ago.  What do we need to 
>do (or revert)
>to fix it in 2.6.24?
>

As I responded earlier here
http://www.ussg.iu.edu/hypermail/linux/kernel/0711.3/2348.html

This interface cannot be supported cleanly with cpuidle. The cleanest
way to do this is to go through latency interfaces. We have changed all
in kernel drivers to use this new interface. The issue here is, I
removed this sysfs interface without depracting it. We can call it a
regression and we can add it back for the moment. But, this will go from
sysfs sooner or later and latency interface has to be used in future.
And Mark earlier responded in this thread saying he is OK with adding
something in the kernel to get this working, That is the reason I
suggested the above option.

As I saw it 6 weeks back, max_cstate option works as a boot parameter. I
did not see anyone else (apart from Mark) saying they are depending on
this sysfs interface to change max_cstate at run time and Mark said he
can do with the kernel change if possible. Please let me know if you
think this interface is a must fix for .24. I will send a minimal patch
to add it back for .24 for !CPU_IDLE case.

Thanks,
Venki 

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Pallipadi, Venkatesh wrote:
>  
> 
>> -----Original Message-----
>> From: Andrew Morton [mailto:akpm@linux-foundation.org] 
>> Sent: Wednesday, January 02, 2008 4:52 PM
>> To: Pallipadi, Venkatesh
>> Cc: Mark Lord; Arjan van de Ven; abelay@novell.com; 
>> lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
>> linux-acpi@vger.kernel.org
>> Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>> added to -mm tree
>>
>> On Wed, 2 Jan 2008 16:06:20 -0800 "Pallipadi, Venkatesh" 
>> <venkatesh.pallipadi@intel.com> wrote:
>>
>>>  
>>>
>>>> -----Original Message-----
>>>> From: Mark Lord [mailto:lkml@rtr.ca] 
>>>> Sent: Wednesday, January 02, 2008 3:42 PM
>>>> To: Arjan van de Ven
>>>> Cc: Pallipadi, Venkatesh; Andrew Morton; abelay@novell.com; 
>>>> lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
>>>> linux-acpi@vger.kernel.org
>>>> Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>>>> added to -mm tree
>>>>
>>>> Arjan van de Ven wrote:
>>>>> On Fri, 30 Nov 2007 22:31:17 -0500
>>>>> Mark Lord <lkml@rtr.ca> wrote:
>>>>>
>>>>>> Arjan van de Ven wrote:
>>>>>>> On Fri, 30 Nov 2007 22:14:08 -0500
>>>>>>> Mark Lord <lkml@rtr.ca> wrote:
>>>>>>>
>>>>>>>>> in -mm there is.. the QoS stuff allows you to set maximum
>>>>>>>>> tolerable
>>>>>>>> ..
>>>>>>>>
>>>>>>>> That's encouraging, I think, but not for 2.6.24.
>>>>>>>>
>>>>>>>>> latency. If your app cant take any latency, you should set
>>>>>>>>> those... and the side effect is that the kernel will not do
>>>>>>>>> long-latency C-states or P-state transitions..
>>>>>>>> ..
>>>>>>>>
>>>>>>>> I don't mind the cpufreq changing (actually, I want it 
>> to drop in
>>>>>>>> cpugfreq to save power and keep the fan off), but the 
>>>> C-states just
>>>>>>>> kill this app.
>>>>>>>>
>>>>>>>> The app is VMware.  I force the max_state=1 when launching,
>>>>>>> ah but then its' even easier... and can be done in 
>> 2.6.24 already.
>>>>>>> VMWare after all has a kernel module, and the latency 
>> stuff is in
>>>>>>> 2.6.23 and 2.6.24 available inside the kernel already.
>>>>>> ..
>>>>>>
>>>>>> Oh, I'm perfectly happy to write my own kernel module if 
>> that's what
>>>>> all you need to do in your kernel module is call
>>>>>
>>>>> add_latency_constraint("mark_wants_his_mouse", 5);
>>>>>
>>>>> or so
>>>> ..
>>>>
>>>> Dredging up an old regression again now:
>>>>
>>>> The "make my own module to replace /sys/.../max_cstate" doesn't work
>>>> for the single-core machine we use a lot around here.
>>>>
>>>> VMware is totally sluggish unless I go to another text window 
>>>> and do this:
>>>>
>>>>    while ( true ); do echo -n ; done
>>>>
>>>> At which point VMware performs well again,
>>>> the same as with "echo 1 > max_cstate" in 2.6.23.
>>>>
>>>> Anyone got any suggestions on how to fix this regression
>>>> or work around it for 2.6.24 ?
>>>>
>>> Easiest and clean way to do it is to have a driver with
>>> set_acceptable_latency() for 1uS or so in init and
>>> remove_acceptable_latency() at exit.
>> err, you appear to be suggesting that Mark patch his kernel to 
>> make it work
>> as well as 2.6.23?  That would be a wrong answer.
>>
>> This regression was known six weeks ago.  What do we need to 
>> do (or revert)
>> to fix it in 2.6.24?
>>
> 
> As I responded earlier here
> http://www.ussg.iu.edu/hypermail/linux/kernel/0711.3/2348.html
> 
> This interface cannot be supported cleanly with cpuidle. The cleanest
> way to do this is to go through latency interfaces. We have changed all
> in kernel drivers to use this new interface. The issue here is, I
> removed this sysfs interface without depracting it. We can call it a
> regression and we can add it back for the moment. But, this will go from
> sysfs sooner or later and latency interface has to be used in future.
> And Mark earlier responded in this thread saying he is OK with adding
> something in the kernel to get this working, That is the reason I
> suggested the above option.
..

I'm fine with switching to a new interface, and even supplying my own
kernel module to do so.  But it doesn't produce the required effect
on the single-core machine we just switched over to 2.6.24
(and then promptly switched back again!).

There should be some way to get it to work with similar minimal latency
to the old "echo 1 > max_cstate" logic, but I've yet to discover it.

I wonder if the "new" latency interfaces actually work ?

> As I saw it 6 weeks back, max_cstate option works as a boot parameter.
..

That's no good.  It has to be changeable on the fly, rather than requiring
the machine be rebooted each time.

Cheers

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Pallipadi, Venkatesh wrote:
>  
> 
>> -----Original Message-----
>> From: Mark Lord [mailto:lkml@rtr.ca] 
>> Sent: Wednesday, January 02, 2008 3:42 PM
>> To: Arjan van de Ven
>> Cc: Pallipadi, Venkatesh; Andrew Morton; abelay@novell.com; 
>> lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
>> linux-acpi@vger.kernel.org
>> Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>> added to -mm tree
>>
>> Arjan van de Ven wrote:
>>> On Fri, 30 Nov 2007 22:31:17 -0500
>>> Mark Lord <lkml@rtr.ca> wrote:
>>>
>>>> Arjan van de Ven wrote:
>>>>> On Fri, 30 Nov 2007 22:14:08 -0500
>>>>> Mark Lord <lkml@rtr.ca> wrote:
>>>>>
>>>>>>> in -mm there is.. the QoS stuff allows you to set maximum
>>>>>>> tolerable
>>>>>> ..
>>>>>>
>>>>>> That's encouraging, I think, but not for 2.6.24.
>>>>>>
>>>>>>> latency. If your app cant take any latency, you should set
>>>>>>> those... and the side effect is that the kernel will not do
>>>>>>> long-latency C-states or P-state transitions..
>>>>>> ..
>>>>>>
>>>>>> I don't mind the cpufreq changing (actually, I want it to drop in
>>>>>> cpugfreq to save power and keep the fan off), but the 
>> C-states just
>>>>>> kill this app.
>>>>>>
>>>>>> The app is VMware.  I force the max_state=1 when launching,
>>>>> ah but then its' even easier... and can be done in 2.6.24 already.
>>>>> VMWare after all has a kernel module, and the latency stuff is in
>>>>> 2.6.23 and 2.6.24 available inside the kernel already.
>>>> ..
>>>>
>>>> Oh, I'm perfectly happy to write my own kernel module if that's what
>>> all you need to do in your kernel module is call
>>>
>>> add_latency_constraint("mark_wants_his_mouse", 5);
>>>
>>> or so
>> ..
>>
>> Dredging up an old regression again now:
>>
>> The "make my own module to replace /sys/.../max_cstate" doesn't work
>> for the single-core machine we use a lot around here.
>>
>> VMware is totally sluggish unless I go to another text window 
>> and do this:
>>
>>    while ( true ); do echo -n ; done
>>
>> At which point VMware performs well again,
>> the same as with "echo 1 > max_cstate" in 2.6.23.
>>
>> Anyone got any suggestions on how to fix this regression
>> or work around it for 2.6.24 ?
>>
> 
> Easiest and clean way to do it is to have a driver with
> set_acceptable_latency() for 1uS or so in init and
> remove_acceptable_latency() at exit.
..

As noted, I already do that.  It helps with my Core2Duo machine,
but not with the single-core case.  Bummer.

-ml

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Venki Pallipadi]

Reintroduce run time configurable max_cstate for !CPU_IDLE case.

Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>

Index: linux-2.6.24-rc/drivers/acpi/processor_idle.c
===================================================================
--- linux-2.6.24-rc.orig/drivers/acpi/processor_idle.c
+++ linux-2.6.24-rc/drivers/acpi/processor_idle.c
@@ -76,7 +76,11 @@ static void (*pm_idle_save) (void) __rea
 #define PM_TIMER_TICKS_TO_US(p)		(((p) * 1000)/(PM_TIMER_FREQUENCY/1000))
 
 static unsigned int max_cstate __read_mostly = ACPI_PROCESSOR_MAX_POWER;
+#ifdef CONFIG_CPU_IDLE
 module_param(max_cstate, uint, 0000);
+#else
+module_param(max_cstate, uint, 0644);
+#endif
 static unsigned int nocst __read_mostly;
 module_param(nocst, uint, 0000);
 

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Venki Pallipadi wrote:
> Reintroduce run time configurable max_cstate for !CPU_IDLE case.
> 
> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> 
> Index: linux-2.6.24-rc/drivers/acpi/processor_idle.c
> ===================================================================
> --- linux-2.6.24-rc.orig/drivers/acpi/processor_idle.c
> +++ linux-2.6.24-rc/drivers/acpi/processor_idle.c
> @@ -76,7 +76,11 @@ static void (*pm_idle_save) (void) __rea
>  #define PM_TIMER_TICKS_TO_US(p)		(((p) * 1000)/(PM_TIMER_FREQUENCY/1000))
>  
>  static unsigned int max_cstate __read_mostly = ACPI_PROCESSOR_MAX_POWER;
> +#ifdef CONFIG_CPU_IDLE
>  module_param(max_cstate, uint, 0000);
> +#else
> +module_param(max_cstate, uint, 0644);
> +#endif
>  static unsigned int nocst __read_mostly;
>  module_param(nocst, uint, 0000);
>  
..

I'll try and re-test with this on Friday.

Meanwhile, can you give a short summary of how behaviour differs
between CONFIG_CPU_IDLE and !CONFIG_CPU_IDLE  ??

I'm not at all clear on how this really affects things.

Thanks.

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Mark Lord wrote:
> Venki Pallipadi wrote:
>> Reintroduce run time configurable max_cstate for !CPU_IDLE case.
>>
>> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
>>
>> Index: linux-2.6.24-rc/drivers/acpi/processor_idle.c
>> ===================================================================
>> --- linux-2.6.24-rc.orig/drivers/acpi/processor_idle.c
>> +++ linux-2.6.24-rc/drivers/acpi/processor_idle.c
>> @@ -76,7 +76,11 @@ static void (*pm_idle_save) (void) __rea
>>  #define PM_TIMER_TICKS_TO_US(p)        (((p) * 
>> 1000)/(PM_TIMER_FREQUENCY/1000))
>>  
>>  static unsigned int max_cstate __read_mostly = ACPI_PROCESSOR_MAX_POWER;
>> +#ifdef CONFIG_CPU_IDLE
>>  module_param(max_cstate, uint, 0000);
>> +#else
>> +module_param(max_cstate, uint, 0644);
>> +#endif
>>  static unsigned int nocst __read_mostly;
>>  module_param(nocst, uint, 0000);
>>  
> ..
> 
> I'll try and re-test with this on Friday.
..

Okay, with !CONFIG_CPU_IDLE, this works fine -- same as 2.6.23 and earlier.

> Meanwhile, can you give a short summary of how behaviour differs
> between CONFIG_CPU_IDLE and !CONFIG_CPU_IDLE  ??
> 
> I'm not at all clear on how this really affects things.

???

RE: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Pallipadi, Venkatesh]

>-----Original Message-----
>From: Mark Lord [mailto:lkml@rtr.ca] 
>Sent: Friday, January 04, 2008 1:53 PM
>To: Pallipadi, Venkatesh
>Cc: Arjan van de Ven; Andrew Morton; abelay@novell.com; 
>lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
>linux-acpi@vger.kernel.org; rjw@sisk.pl
>Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>added to -mm tree
>
>Mark Lord wrote:
>> Venki Pallipadi wrote:
>>> Reintroduce run time configurable max_cstate for !CPU_IDLE case.
>>>
>>> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
>>>
>>> Index: linux-2.6.24-rc/drivers/acpi/processor_idle.c
>>> ===================================================================
>>> --- linux-2.6.24-rc.orig/drivers/acpi/processor_idle.c
>>> +++ linux-2.6.24-rc/drivers/acpi/processor_idle.c
>>> @@ -76,7 +76,11 @@ static void (*pm_idle_save) (void) __rea
>>>  #define PM_TIMER_TICKS_TO_US(p)        (((p) * 
>>> 1000)/(PM_TIMER_FREQUENCY/1000))
>>>  
>>>  static unsigned int max_cstate __read_mostly = 
>ACPI_PROCESSOR_MAX_POWER;
>>> +#ifdef CONFIG_CPU_IDLE
>>>  module_param(max_cstate, uint, 0000);
>>> +#else
>>> +module_param(max_cstate, uint, 0644);
>>> +#endif
>>>  static unsigned int nocst __read_mostly;
>>>  module_param(nocst, uint, 0000);
>>>  
>> ..
>> 
>> I'll try and re-test with this on Friday.
>..
>
>Okay, with !CONFIG_CPU_IDLE, this works fine -- same as 2.6.23 
>and earlier.
>

Good to know. Atleast we do not have a regression for 2.6.24 now.

>> Meanwhile, can you give a short summary of how behaviour differs
>> between CONFIG_CPU_IDLE and !CONFIG_CPU_IDLE  ??
>> 
>> I'm not at all clear on how this really affects things.
>

With CPU_IDLE, the C-state policy is removed from acpi driver. Ideally
policy should have nothing to do with ACPI, as ACPI only provides the
C-state mechanisms. So, with CPU_IDLE, it is not easy to control this
variable through a acpi driver module at run time. Also, the latency
interface that was mentioned before is to serve the same purpose in a
more clear manner (based on the wakeup latency) instead of a C-state
number which may not mean much from the end user point of view.

I will look at why latency does not work on a single core system
soon(Was that with UP kernel or SMP kernel?). That way we will have a
proper cover for this with CPU_IDLE in future.

Thanks,
Venki

RE: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Pallipadi, Venkatesh]

>-----Original Message-----
>From: Mark Lord [mailto:lkml@rtr.ca] 
>Sent: Friday, January 04, 2008 1:53 PM
>To: Pallipadi, Venkatesh
>Cc: Arjan van de Ven; Andrew Morton; abelay@novell.com; 
>lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
>linux-acpi@vger.kernel.org; rjw@sisk.pl
>Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>added to -mm tree
>
>Mark Lord wrote:
>> Venki Pallipadi wrote:
>>> Reintroduce run time configurable max_cstate for !CPU_IDLE case.
>>>
>>> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
>>>
>>> Index: linux-2.6.24-rc/drivers/acpi/processor_idle.c
>>> ===================================================================
>>> --- linux-2.6.24-rc.orig/drivers/acpi/processor_idle.c
>>> +++ linux-2.6.24-rc/drivers/acpi/processor_idle.c
>>> @@ -76,7 +76,11 @@ static void (*pm_idle_save) (void) __rea
>>>  #define PM_TIMER_TICKS_TO_US(p)        (((p) * 
>>> 1000)/(PM_TIMER_FREQUENCY/1000))
>>>  
>>>  static unsigned int max_cstate __read_mostly = 
>ACPI_PROCESSOR_MAX_POWER;
>>> +#ifdef CONFIG_CPU_IDLE
>>>  module_param(max_cstate, uint, 0000);
>>> +#else
>>> +module_param(max_cstate, uint, 0644);
>>> +#endif
>>>  static unsigned int nocst __read_mostly;
>>>  module_param(nocst, uint, 0000);
>>>  
>> ..
>> 
>> I'll try and re-test with this on Friday.
>..
>
>Okay, with !CONFIG_CPU_IDLE, this works fine -- same as 2.6.23 
>and earlier.
>

Good to know. Atleast we do not have a regression for 2.6.24 now.

>> Meanwhile, can you give a short summary of how behaviour differs
>> between CONFIG_CPU_IDLE and !CONFIG_CPU_IDLE  ??
>> 
>> I'm not at all clear on how this really affects things.
>

With CPU_IDLE, the C-state policy is removed from acpi driver. Ideally
policy should have nothing to do with ACPI, as ACPI only provides the
C-state mechanisms. So, with CPU_IDLE, it is not easy to control this
variable through a acpi driver module at run time. Also, the latency
interface that was mentioned before is to serve the same purpose in a
more clear manner (based on the wakeup latency) instead of a C-state
number which may not mean much from the end user point of view.

I will look at why latency does not work on a single core system
soon(Was that with UP kernel or SMP kernel?). That way we will have a
proper cover for this with CPU_IDLE in future.

Thanks,
Venki

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Pallipadi, Venkatesh wrote:
>> -----Original Message-----
>> From: Mark Lord [mailto:lkml@rtr.ca] 
..
>> Okay, with !CONFIG_CPU_IDLE, this works fine -- same as 2.6.23 
>> and earlier.
>>
> 
> Good to know. Atleast we do not have a regression for 2.6.24 now.
..

Agreed.  We're happy here, for now.

>>> Meanwhile, can you give a short summary of how behaviour differs
>>> between CONFIG_CPU_IDLE and !CONFIG_CPU_IDLE  ??
>>>
>>> I'm not at all clear on how this really affects things.
> 
> With CPU_IDLE, the C-state policy is removed from acpi driver. Ideally
> policy should have nothing to do with ACPI, as ACPI only provides the
> C-state mechanisms. So, with CPU_IDLE, it is not easy to control this
> variable through a acpi driver module at run time. Also, the latency
> interface that was mentioned before is to serve the same purpose in a
> more clear manner (based on the wakeup latency) instead of a C-state
> number which may not mean much from the end user point of view.
> 
> I will look at why latency does not work on a single core system
> soon(Was that with UP kernel or SMP kernel?). That way we will have a
> proper cover for this with CPU_IDLE in future.
..

That was with a UP kernel on a UP box.

The latency thingie really seemed to have little or no effect,
whereas setting max_cstate=1 has a quite noticeable positive impact.

Things seemed okay (with the latency thingie) on the SMP machine,
but with two cores it is probably simply more forgiving.  

cheers

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Venki Pallipadi wrote:
> Reintroduce run time configurable max_cstate for !CPU_IDLE case.
> 
> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> 
> Index: linux-2.6.24-rc/drivers/acpi/processor_idle.c
> ===================================================================
> --- linux-2.6.24-rc.orig/drivers/acpi/processor_idle.c
> +++ linux-2.6.24-rc/drivers/acpi/processor_idle.c
> @@ -76,7 +76,11 @@ static void (*pm_idle_save) (void) __rea
>  #define PM_TIMER_TICKS_TO_US(p)		(((p) * 1000)/(PM_TIMER_FREQUENCY/1000))
>  
>  static unsigned int max_cstate __read_mostly = ACPI_PROCESSOR_MAX_POWER;
> +#ifdef CONFIG_CPU_IDLE
>  module_param(max_cstate, uint, 0000);
> +#else
> +module_param(max_cstate, uint, 0644);
> +#endif
>  static unsigned int nocst __read_mostly;
>  module_param(nocst, uint, 0000);
>  
..

Can we get this patch upstream so that a stock 2.6.24 will work here?

Thanks

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Andrew Morton]

On Sun, 06 Jan 2008 16:34:16 -0500 Mark Lord <lkml@rtr.ca> wrote:

> Venki Pallipadi wrote:
> > Reintroduce run time configurable max_cstate for !CPU_IDLE case.
> > 
> > Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> > 
> > Index: linux-2.6.24-rc/drivers/acpi/processor_idle.c
> > ===================================================================
> > --- linux-2.6.24-rc.orig/drivers/acpi/processor_idle.c
> > +++ linux-2.6.24-rc/drivers/acpi/processor_idle.c
> > @@ -76,7 +76,11 @@ static void (*pm_idle_save) (void) __rea
> >  #define PM_TIMER_TICKS_TO_US(p)		(((p) * 1000)/(PM_TIMER_FREQUENCY/1000))
> >  
> >  static unsigned int max_cstate __read_mostly = ACPI_PROCESSOR_MAX_POWER;
> > +#ifdef CONFIG_CPU_IDLE
> >  module_param(max_cstate, uint, 0000);
> > +#else
> > +module_param(max_cstate, uint, 0644);
> > +#endif
> >  static unsigned int nocst __read_mostly;
> >  module_param(nocst, uint, 0000);
> >  
> ..
> 
> Can we get this patch upstream so that a stock 2.6.24 will work here?
> 

umm, OK, I queued it for 2.6.24.  I'll give people a day or so to comment
on this.

I had to invent some silly changlelog for it.  Please review it for
accuracy and completeness?

It isn't complete, really.  How come we only make max_cstate writeable if
CONFIG_CPU_IDLE=n?  What happens to people who were reliant upon writeable
max_cstate who now enable CPU_IDLE?  Things still break?  What is the
rationale behind this?  What constraints led us to this decision?




From: Venki Pallipadi <venkatesh.pallipadi@intel.com>

This was writeable in 2.6.23 but the cpuidle merge made it read-only.  But
some people's scripts (ie: Mark's) were writing to it.

As an unhappy compromise, make max_cstate writeable again if the kernel was
configured without CONFIG_CPU_IDLE.

Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Cc: Mark Lord <lkml@rtr.ca>
Cc: Arjan van de Ven <arjan@infradead.org>
Cc: Len Brown <lenb@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 drivers/acpi/processor_idle.c |    4 ++++
 1 file changed, 4 insertions(+)

diff -puN drivers/acpi/processor_idle.c~reintroduce-run-time-configurable-max_cstate-for-cpu_idle-case drivers/acpi/processor_idle.c
--- a/drivers/acpi/processor_idle.c~reintroduce-run-time-configurable-max_cstate-for-cpu_idle-case
+++ a/drivers/acpi/processor_idle.c
@@ -76,7 +76,11 @@ static void (*pm_idle_save) (void) __rea
 #define PM_TIMER_TICKS_TO_US(p)		(((p) * 1000)/(PM_TIMER_FREQUENCY/1000))
 
 static unsigned int max_cstate __read_mostly = ACPI_PROCESSOR_MAX_POWER;
+#ifdef CONFIG_CPU_IDLE
 module_param(max_cstate, uint, 0000);
+#else
+module_param(max_cstate, uint, 0644);
+#endif
 static unsigned int nocst __read_mostly;
 module_param(nocst, uint, 0000);
 
_

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Arjan van de Ven]

On Sun, 6 Jan 2008 23:18:48 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:

> On Sun, 06 Jan 2008 16:34:16 -0500 Mark Lord <lkml@rtr.ca> wrote:
> 
> > Venki Pallipadi wrote:
> > > Reintroduce run time configurable max_cstate for !CPU_IDLE case.
> > > 
> > > Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> > > 
> > > Index: linux-2.6.24-rc/drivers/acpi/processor_idle.c
> > > ===================================================================
> > > --- linux-2.6.24-rc.orig/drivers/acpi/processor_idle.c
> > > +++ linux-2.6.24-rc/drivers/acpi/processor_idle.c
> > > @@ -76,7 +76,11 @@ static void (*pm_idle_save) (void) __rea
> > >  #define PM_TIMER_TICKS_TO_US(p)		(((p) *
> > > 1000)/(PM_TIMER_FREQUENCY/1000)) 
> > >  static unsigned int max_cstate __read_mostly =
> > > ACPI_PROCESSOR_MAX_POWER; +#ifdef CONFIG_CPU_IDLE
> > >  module_param(max_cstate, uint, 0000);
> > > +#else
> > > +module_param(max_cstate, uint, 0644);
> > > +#endif
> > >  static unsigned int nocst __read_mostly;
> > >  module_param(nocst, uint, 0000);
> > >  
> > ..
> > 
> > Can we get this patch upstream so that a stock 2.6.24 will work
> > here?
> > 
> 
> umm, OK, I queued it for 2.6.24.  I'll give people a day or so to
> comment on this.
> 
> I had to invent some silly changlelog for it.  Please review it for
> accuracy and completeness?
> 
> It isn't complete, really.  How come we only make max_cstate
> writeable if CONFIG_CPU_IDLE=n?  What happens to people who were
> reliant upon writeable max_cstate who now enable CPU_IDLE?  Things
> still break?  What is the rationale behind this?  What constraints
> led us to this decision?



if we take a step back; Mark afaics only wants to put 1 in there...
And that makes sense; either you want the "no latency" C1, or you want the lot
(esp given that C2 and deeper are at the whim of the bios, what they mean varies
over time. Actually even C1 does that on some AMD systems);

Longer term I'd suggest we make an option that basically is "C1 only",
(or technically, "use hlt only")
that solves Marks VMWARE thing, and is a lot closer to what people really want.
Well, that and if VMWARE really can't deal with latency in their kernel module
they should use the proper code for that. It's also a ton easier to implement, since
it basically is "don't use the CPUIDLE idle loop, but use the traditional hlt one"

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Arjan van de Ven wrote:
..
> if we take a step back; Mark afaics only wants to put 1 in there...
> And that makes sense; either you want the "no latency" C1, or you want the lot
> (esp given that C2 and deeper are at the whim of the bios, what they mean varies
> over time. Actually even C1 does that on some AMD systems);
> 
> Longer term I'd suggest we make an option that basically is "C1 only",
> (or technically, "use hlt only")
> that solves Marks VMWARE thing, and is a lot closer to what people really want.
..

Yeah, that makes sense.

> Well, that and if VMWARE really can't deal with latency in their kernel module
> they should use the proper code for that. It's also a ton easier to implement, since
> it basically is "don't use the CPUIDLE idle loop, but use the traditional hlt one"
..

I don't think it's so much VMware itself, as it is the guest OS inside it.

Cheers

RE: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Andrew Morton [mailto:akpm@linux-foundation.org] 
>Sent: Sunday, January 06, 2008 11:19 PM
>To: Mark Lord
>Cc: Pallipadi, Venkatesh; Arjan van de Ven; abelay@novell.com; 
>lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
>linux-acpi@vger.kernel.org; rjw@sisk.pl
>Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>added to -mm tree
>
>On Sun, 06 Jan 2008 16:34:16 -0500 Mark Lord <lkml@rtr.ca> wrote:
>
>> Venki Pallipadi wrote:
>> > Reintroduce run time configurable max_cstate for !CPU_IDLE case.
>> > 
>> Can we get this patch upstream so that a stock 2.6.24 will work here?
>> 
>
>umm, OK, I queued it for 2.6.24.  I'll give people a day or so 
>to comment
>on this.
>
>I had to invent some silly changlelog for it.  Please review it for
>accuracy and completeness?
>
>It isn't complete, really.  How come we only make max_cstate 
>writeable if
>CONFIG_CPU_IDLE=n?  What happens to people who were reliant 
>upon writeable
>max_cstate who now enable CPU_IDLE?  Things still break?  What is the
>rationale behind this?  What constraints led us to this decision?

It is done only for !CPU_IDLE case to take care of regression at hand.
CPU_IDLE case technically is not a regression as it is a new config
option. It is not easy to implement this with CPU_IDLE as acpi driver
only provides the C-state mechanism and does not have the policy in it
anymore with CPU_IDLE. It still can be done with some hacky code. But, I
am incliced to switch this to using latency interface which is more
cleaner than max_cstate interface.

For example, max_cstate does not mean anything to the user, as BIOSes
normally tend to hide one C-state or more than one C-states behind one
OS visible C-state. Like C2 mapped to real C3 etc. Saying that I don't
want CPUs to enter any C-state more than 100uS latency is cleaner in
comparison (even though we depend on the latency number coming from the
BIOS).

Mark said this latency interface is not working as it is expected to at
this moment. I will look at that soon and then we will have an alternate
mechanism for this limiting C-state thing.

I am OK with the below changelog.

Thanks,
Venki

>From: Venki Pallipadi <venkatesh.pallipadi@intel.com>
>
>This was writeable in 2.6.23 but the cpuidle merge made it 
>read-only.  But
>some people's scripts (ie: Mark's) were writing to it.
>
>As an unhappy compromise, make max_cstate writeable again if 
>the kernel was
>configured without CONFIG_CPU_IDLE.
>
>Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
>Cc: Mark Lord <lkml@rtr.ca>
>Cc: Arjan van de Ven <arjan@infradead.org>
>Cc: Len Brown <lenb@kernel.org>
>Cc: Ingo Molnar <mingo@elte.hu>
>Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
>Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>---
>
> drivers/acpi/processor_idle.c |    4 ++++
> 1 file changed, 4 insertions(+)
>
>diff -puN 
>drivers/acpi/processor_idle.c~reintroduce-run-time-configurable
>-max_cstate-for-cpu_idle-case drivers/acpi/processor_idle.c
>--- 
>a/drivers/acpi/processor_idle.c~reintroduce-run-time-configurab
>le-max_cstate-for-cpu_idle-case
>+++ a/drivers/acpi/processor_idle.c
>@@ -76,7 +76,11 @@ static void (*pm_idle_save) (void) __rea
> #define PM_TIMER_TICKS_TO_US(p)		(((p) * 
>1000)/(PM_TIMER_FREQUENCY/1000))
> 
> static unsigned int max_cstate __read_mostly = 
>ACPI_PROCESSOR_MAX_POWER;
>+#ifdef CONFIG_CPU_IDLE
> module_param(max_cstate, uint, 0000);
>+#else
>+module_param(max_cstate, uint, 0644);
>+#endif
> static unsigned int nocst __read_mostly;
> module_param(nocst, uint, 0000);
> 
>_
>
>

RE: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Andrew Morton [mailto:akpm@linux-foundation.org] 
>Sent: Sunday, January 06, 2008 11:19 PM
>To: Mark Lord
>Cc: Pallipadi, Venkatesh; Arjan van de Ven; abelay@novell.com; 
>lenb@kernel.org; Ingo Molnar; linux-kernel@vger.kernel.org; 
>linux-acpi@vger.kernel.org; rjw@sisk.pl
>Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>added to -mm tree
>
>On Sun, 06 Jan 2008 16:34:16 -0500 Mark Lord <lkml@rtr.ca> wrote:
>
>> Venki Pallipadi wrote:
>> > Reintroduce run time configurable max_cstate for !CPU_IDLE case.
>> > 
>> Can we get this patch upstream so that a stock 2.6.24 will work here?
>> 
>
>umm, OK, I queued it for 2.6.24.  I'll give people a day or so 
>to comment
>on this.
>
>I had to invent some silly changlelog for it.  Please review it for
>accuracy and completeness?
>
>It isn't complete, really.  How come we only make max_cstate 
>writeable if
>CONFIG_CPU_IDLE=n?  What happens to people who were reliant 
>upon writeable
>max_cstate who now enable CPU_IDLE?  Things still break?  What is the
>rationale behind this?  What constraints led us to this decision?

It is done only for !CPU_IDLE case to take care of regression at hand.
CPU_IDLE case technically is not a regression as it is a new config
option. It is not easy to implement this with CPU_IDLE as acpi driver
only provides the C-state mechanism and does not have the policy in it
anymore with CPU_IDLE. It still can be done with some hacky code. But, I
am incliced to switch this to using latency interface which is more
cleaner than max_cstate interface.

For example, max_cstate does not mean anything to the user, as BIOSes
normally tend to hide one C-state or more than one C-states behind one
OS visible C-state. Like C2 mapped to real C3 etc. Saying that I don't
want CPUs to enter any C-state more than 100uS latency is cleaner in
comparison (even though we depend on the latency number coming from the
BIOS).

Mark said this latency interface is not working as it is expected to at
this moment. I will look at that soon and then we will have an alternate
mechanism for this limiting C-state thing.

I am OK with the below changelog.

Thanks,
Venki

>From: Venki Pallipadi <venkatesh.pallipadi@intel.com>
>
>This was writeable in 2.6.23 but the cpuidle merge made it 
>read-only.  But
>some people's scripts (ie: Mark's) were writing to it.
>
>As an unhappy compromise, make max_cstate writeable again if 
>the kernel was
>configured without CONFIG_CPU_IDLE.
>
>Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
>Cc: Mark Lord <lkml@rtr.ca>
>Cc: Arjan van de Ven <arjan@infradead.org>
>Cc: Len Brown <lenb@kernel.org>
>Cc: Ingo Molnar <mingo@elte.hu>
>Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
>Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>---
>
> drivers/acpi/processor_idle.c |    4 ++++
> 1 file changed, 4 insertions(+)
>
>diff -puN 
>drivers/acpi/processor_idle.c~reintroduce-run-time-configurable
>-max_cstate-for-cpu_idle-case drivers/acpi/processor_idle.c
>--- 
>a/drivers/acpi/processor_idle.c~reintroduce-run-time-configurab
>le-max_cstate-for-cpu_idle-case
>+++ a/drivers/acpi/processor_idle.c
>@@ -76,7 +76,11 @@ static void (*pm_idle_save) (void) __rea
> #define PM_TIMER_TICKS_TO_US(p)		(((p) * 
>1000)/(PM_TIMER_FREQUENCY/1000))
> 
> static unsigned int max_cstate __read_mostly = 
>ACPI_PROCESSOR_MAX_POWER;
>+#ifdef CONFIG_CPU_IDLE
> module_param(max_cstate, uint, 0000);
>+#else
>+module_param(max_cstate, uint, 0644);
>+#endif
> static unsigned int nocst __read_mostly;
> module_param(nocst, uint, 0000);
> 
>_
>
>

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Andrew Morton wrote:
>..
> umm, OK, I queued it for 2.6.24.  I'll give people a day or so to comment
> on this.
> 
> I had to invent some silly changlelog for it.  Please review it for
> accuracy and completeness?
..
> From: Venki Pallipadi <venkatesh.pallipadi@intel.com>
> 
> This was writeable in 2.6.23 but the cpuidle merge made it read-only.  But
> some people's scripts (ie: Mark's) were writing to it.
..

Actually, the cpuidle changes made it not appear at all in sysfs.

Thanks, Andrew & Venki.

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Len Brown]

1. Why does VMware need max_cstate=1 to load quickly?
   It should not, and the fact that it does means
   that something somewhere is seriously broken.

2. Why does the "max_csate=1" workaround help only
   on the dual-core boxes, while the single-core
   boxes still fail to load quickly?

I'm glad that we deleted run-time access to max_cstate --
it seems to have exposed a real bug that needs fixing
and has gone unreported until now.

Indeed, when the real bug is fixed, I propose that
we again move to delete max_cstate as a run-time API.

-Len

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Mark Lord]

Len Brown wrote:
> 1. Why does VMware need max_cstate=1 to load quickly?
..

Eh?  Nothing to do with "loading" anything,
but rather it's simple responsiveness to guest keyboard
input that we're experiencing trouble with.
The guest OS is probably "broken" in that regard,
but setting max_cstate=1 makes it usable here.

> 2. Why does the "max_csate=1" workaround help only
>    on the dual-core boxes, while the single-core
>    boxes still fail to load quickly?
..

Eh?  Setting max_cstate=1 helps on both single/dual core
boxes/kernels here.  The alternative (newer) latency thing
(that requires a custom kernel module to change on the fly)
is the thing that had no effect at all on our single-core box,
but did seem to help the dual-core more (not verified completely
on dual-core though).

Cheers

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Len Brown]

On Monday 07 January 2008 16:33, Mark Lord wrote:
> Len Brown wrote:
> > 1. Why does VMware need max_cstate=1 to load quickly?
> ..
> 
> Eh?  Nothing to do with "loading" anything,
> but rather it's simple responsiveness to guest keyboard
> input that we're experiencing trouble with.
> The guest OS is probably "broken" in that regard,
> but setting max_cstate=1 makes it usable here.

okay, then when vmware is loaded, but idle, please run powertop
http://www.lesswatts.org/projects/powertop

and report what you see for C-states, P-states
and wakeup sources.


> > 2. Why does the "max_csate=1" workaround help only
> >    on the dual-core boxes, while the single-core
> >    boxes still fail to load quickly?
> ..
> 
> Eh?  Setting max_cstate=1 helps on both single/dual core
> boxes/kernels here.  The alternative (newer) latency thing
> (that requires a custom kernel module to change on the fly)
> is the thing that had no effect at all on our single-core box,
> but did seem to help the dual-core more (not verified completely
> on dual-core though).

please report the contents of 
cat /proc/acpi/processor/CPU*/power
for both systems when the C-states are not limited.

what latency limit did you specific to the latency I/F?

thanks,
-Len

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Andrew Morton]

On Fri, 30 Nov 2007 22:14:08 -0500 Mark Lord <lkml@rtr.ca> wrote:

> > latency. If your app cant take any latency, you should set those... and
> > the side effect is that the kernel will not do long-latency C-states or
> > P-state transitions..
> ..
> 
> I don't mind the cpufreq changing (actually, I want it to drop in cpugfreq
> to save power and keep the fan off), but the C-states just kill this app.

semi-OT: I was finding that disabling cpufreq altogether on the Vaio speeds up
`quilt push 1000' by a lot - around 30% iirc.

There do seem to be some unsophisticated decisions in there and we're losing quite
a bit of performance as a result.

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Arjan van de Ven]

On Sat, 1 Dec 2007 02:17:40 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:

> On Fri, 30 Nov 2007 22:14:08 -0500 Mark Lord <lkml@rtr.ca> wrote:
> 
> > > latency. If your app cant take any latency, you should set
> > > those... and the side effect is that the kernel will not do
> > > long-latency C-states or P-state transitions..
> > ..
> > 
> > I don't mind the cpufreq changing (actually, I want it to drop in
> > cpugfreq to save power and keep the fan off), but the C-states just
> > kill this app.
> 
> semi-OT: I was finding that disabling cpufreq altogether on the Vaio
> speeds up `quilt push 1000' by a lot - around 30% iirc.

I assume this is using the ondemand governor and not userspace?
(some older distros mistakingly used "userspace" and yes, that will
suck)

# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor 
ondemand

(to make it easily cut-n-pastable to check)

> 
> There do seem to be some unsophisticated decisions in there and we're
> losing quite a bit of performance as a result.

if you can give a simple recipe for one of these, we can add it to our
workload testsuite that at least some of us use every time we change
either the C states or the cpufreq stuff....

(and yes we want to improve things)


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

Re: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Pavel Machek]

Hi!

> >It is not known whether Mark is actually writing to this 
> >thing.  Perhaps
> >read-only permissions would be a suitable fix?
> >
> 
> Exporting it as read only should be OK. We also need to know if there
> are hard user space dependency on writing to this from userspace.

Some people are manipulating it from their suspend scripts..

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

RE: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Pavel Machek [mailto:pavel@ucw.cz] 
>Sent: Wednesday, December 05, 2007 3:17 AM
>To: Pallipadi, Venkatesh
>Cc: Andrew Morton; lkml@rtr.ca; abelay@novell.com; 
>lenb@kernel.org; mlord@pobox.com; rjw@sisk.pl; 
>linux-kernel@vger.kernel.org; linux-acpi@vger.kernel.org
>Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>added to -mm tree
>
>Hi!
>
>> >It is not known whether Mark is actually writing to this 
>> >thing.  Perhaps
>> >read-only permissions would be a suitable fix?
>> >
>> 
>> Exporting it as read only should be OK. We also need to know if there
>> are hard user space dependency on writing to this from userspace.
>
>Some people are manipulating it from their suspend scripts..
>

That is done by default in kernel now. Deep C-states are disabled
between suspend and resume.

Thanks,
Venki

RE: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Pavel Machek [mailto:pavel@ucw.cz] 
>Sent: Wednesday, December 05, 2007 3:17 AM
>To: Pallipadi, Venkatesh
>Cc: Andrew Morton; lkml@rtr.ca; abelay@novell.com; 
>lenb@kernel.org; mlord@pobox.com; rjw@sisk.pl; 
>linux-kernel@vger.kernel.org; linux-acpi@vger.kernel.org
>Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch 
>added to -mm tree
>
>Hi!
>
>> >It is not known whether Mark is actually writing to this 
>> >thing.  Perhaps
>> >read-only permissions would be a suitable fix?
>> >
>> 
>> Exporting it as read only should be OK. We also need to know if there
>> are hard user space dependency on writing to this from userspace.
>
>Some people are manipulating it from their suspend scripts..
>

That is done by default in kernel now. Deep C-states are disabled
between suspend and resume.

Thanks,
Venki