2.6.25-rc8-git2: Reported regressions from 2.6.24

2.6.25-rc8-git2: Reported regressions from 2.6.24

[Rafael J. Wysocki]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 10809 bytes --]

[This time I'm going to do something new: I'll send a series of messages with
individual regression entries CCed to the people involved in handling them in
replies to this message.  Let's see how this works, fingers crossed.  Thx. R.]

This message contains a list of some regressions from 2.6.24, for which there
are no fixes in the mainline I know of.  If any of them have been fixed already,
please let me know.

If you know of any other unresolved regressions from 2.6.24, please let me know
either and I'll add them to the list.  Also, please let me know if any of the
entries below are invalid.


Listed regressions statistics:

  Date          Total  Pending  Unresolved
  ----------------------------------------
  2008-04-04      183       32          28
  2008-03-31      177       34          31
  2008-03-27      171       38          30
  2008-03-22      159       35          31
  2008-03-17      148       38          30
  2008-03-16      146       42          35
  2008-03-14      145       45          39
  2008-03-12      143       51          41
  2008-03-11      141       58          43
  2008-03-10      138       66          47
  2008-03-03      115       65          49
  2008-02-25       90       51          39
  2008-02-17       61       45          37


Unresolved regressions
----------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10391
Subject		: 2.6.25-rc7/8: Another resume regression
Submitter	: Mark Lord <lkml@rtr.ca>
Date		: 2008-04-03 15:06 (1 days old)
References	: http://lkml.org/lkml/2008/4/3/283


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10390
Subject		: Oops while reading /proc/ioports or /proc/iomem
Submitter	: Jan Kara <jack@suse.cz>
Date		: 2008-04-03 15:25 (1 days old)
References	: http://lkml.org/lkml/2008/4/3/149


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10387
Subject		: rc6+ regression - backlight reset to 0 on boot after 7c0ea45be4f114d85ee35caeead8e1660699c46f
Submitter	: Andrey Borzenkov <arvidjaar@mail.ru>
Date		: 2008-04-02 22:53 (2 days old)
References	: http://lkml.org/lkml/2008/4/2/366


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10384
Subject		: 2.6.25-rc6-git2: warn_on_slowpath for tcp_simple_retransmit
Submitter	: Alessandro Suardi <alessandro.suardi@gmail.com>
Date		: 2008-04-02 00:28 (2 days old)
References	: http://lkml.org/lkml/2008/4/1/408
Handled-By	: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10382
Subject		: 2.6.25-rc5.git4 regression PS/2 mouse not detected/working
Submitter	: Yanko Kaneti <yaneti@declera.com>
Date		: 2008-04-02 10:59 (2 days old)
References	: http://lkml.org/lkml/2008/4/2/210
Handled-By	: Dmitry Torokhov <dmitry.torokhov@gmail.com>
		  Balaji Rao <balajirrao@gmail.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10377
Subject		: Kernel freezes during boot when AC is unplugged
Submitter	: Roman Jarosz <kedgedev@centrum.cz>
Date		: 2008-04-01 16:23 (3 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10369
Subject		: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7
Submitter	: Chr <chunkeey@web.de>
Date		: 2008-03-30 21:09 (5 days old)
References	: http://lkml.org/lkml/2008/3/30/87


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10365
Subject		: usb-storage, error reading the last 8 sectors, regression in 2.6.25-rc7
Submitter	: Sergey Dolgov <solkaa@gmail.com>
Date		: 2008-03-30 11:49 (5 days old)
References	: http://lkml.org/lkml/2008/3/30/11


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10349
Subject		: regression: am-utils stopped working in 2.6.25-rc*
Submitter	: Meelis Roos <mroos@linux.ee>
Date		: 2008-03-28 15:20 (7 days old)
References	: http://lkml.org/lkml/2008/3/28/174


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10346
Subject		: Linux 2.6.25-rc6: WARNING: at net/ipv4/tcp_input.c:2510
Submitter	: Georgi Chorbadzhiyski <gf@unixsol.org>
Date		: 2008-03-27 17:29 (8 days old)
References	: http://lkml.org/lkml/2008/3/27/246


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10344
Subject		: [2.6.25-rc6] possible regression: X server dying
Submitter	: Tilman Schmidt <tilman@imap.cc>
Date		: 2008-03-24 23:38 (11 days old)
References	: http://lkml.org/lkml/2008/3/24/260
Handled-By	: Dave Airlie <airlied@gmail.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10324
Subject		: kernel panic ip_route_input
Submitter	: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
Date		: 2008-03-25 12:48 (10 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10323
Subject		: panic using bridging on linus kernel 2.6.25-rc6
Submitter	: Andy Gospodarek <andy@greyhouse.net>
Date		: 2008-03-25 11:40 (10 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10320
Subject		: rt2x00 does not associate or give scan results
Submitter	: Marcus Better <marcus@better.se>
Date		: 2008-03-25 06:04 (10 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10319
Subject		: 2.6.25-rc6 regression - hang on resume
Submitter	: Soeren Sonnenburg <kernel@nn7.de>
Date		: 2008-03-25 04:44 (10 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10302
Subject		: 2.6.25-git regression with snd-hda-intel on Dell XPS M1330, no analog sound
Submitter	: Andre Tomt <andre@tomt.net>
Date		: 2008-03-21 20:03 (14 days old)
References	: http://lkml.org/lkml/2008/3/21/295
Handled-By	: Matthew Ranostay <mranostay@embeddedalley.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10300
Subject		: volume wheel does not work in 2.6.25-rc6
Submitter	: Romano Giannetti <romano.giannetti@gmail.com>
Date		: 2008-03-21 11:42 (14 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10290
Subject		: [BUG] Linux 2.6.25-rc6 - kernel BUG at fs/mpage.c:476! on powerpc
Submitter	: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Date		: 2008-03-20 13:13 (15 days old)
References	: http://lkml.org/lkml/2008/3/20/39


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10235
Subject		: 2.6.25-rc5: Blank Screen with Intel 945
Submitter	: Rafael J. Wysocki <rjw@sisk.pl>
Date		: 2008-03-12 12:02 (23 days old)
References	: http://lkml.org/lkml/2008/3/12/290
Handled-By	: Jesse Barnes <jbarnes@virtuousgeek.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10172
Subject		: kvm: INFO: inconsistent lock state
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2008-03-05 03:26 (30 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10156
Subject		: KVM &amp; Qemu crashed with infinite recursive kernel loop in the guest
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2008-02-28 11:25 (36 days old)
References	: http://lkml.org/lkml/2008/2/28/106


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10133
Subject		: INFO: possible circular locking in the resume
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2008-02-27 (37 days old)
References	: http://lkml.org/lkml/2008/2/26/479
Handled-By	: Gautham R Shenoy <ego@in.ibm.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10117
Subject		: 2.6.25-current-git hangs on boot (pci=nommconf helps)
Submitter	: Soeren Sonnenburg <kernel@nn7.de>
Date		: 2008-02-23 18:55 (41 days old)
References	: http://lkml.org/lkml/2008/2/23/263


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10093
Subject		: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n - Apple
Submitter	: Soeren Sonnenburg <kernel@nn7.de>
Date		: 2008-02-23 18:55 (41 days old)
References	: http://lkml.org/lkml/2008/2/23/263
		  http://marc.info/?l=linux-acpi&amp;m=120387537018467&amp;w=4
Handled-By	: Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10082
Subject		: 2.6.25-rc2-git4 - Kernel oops while running kernbench and tbench on powerpc
Submitter	: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Date		: 2008-02-20 16:01 (44 days old)
References	: http://lkml.org/lkml/2008/2/20/218
		  http://lkml.org/lkml/2008/1/18/71


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10067
Subject		: TUNER_TDA8290=y, VIDEO_DEV=n build error
Submitter	: Toralf Förster <toralf.foerster@gmx.de>
Date		: 2008-02-22 10:36 (42 days old)
References	: http://lkml.org/lkml/2008/2/19/262


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=9980
Subject		: 2.6.25-rc1 on Sun Ultra 40- HPET clocksource which causes it to hang
Submitter	: Jasper Bryant-Greene <jasper@unix.geek.nz>
Date		: 2008-02-13 12:25 (51 days old)
References	: http://lkml.org/lkml/2008/2/13/181


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=9978
Subject		: 2.6.25-rc1: volanoMark regression
Submitter	: Zhang, Yanmin <yanmin_zhang@linux.intel.com>
Date		: 2008-02-13 10:30 (51 days old)
References	: http://lkml.org/lkml/2008/2/13/128
Handled-By	: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>


Regressionn with patches
------------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10373
Subject		: slub compile error
Submitter	: Toralf Förster <toralf.foerster@gmx.de>
Date		: 2008-03-31 14:46 (4 days old)
References	: http://lkml.org/lkml/2008/3/31/120
Handled-By	: Christoph Lameter <clameter@sgi.com>
Patch		: http://lkml.org/lkml/2008/3/31/261


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10366
Subject		: 2.6.25-rc7: warn_on_slowpath triggered
Submitter	: Bob Tracy <rct@frus.com>
Date		: 2008-03-29 17:29 (6 days old)
References	: http://lkml.org/lkml/2008/3/29/125
Handled-By	: Björn Steinbrink <B.Steinbrink@gmx.de>
Patch		: http://lkml.org/lkml/2008/3/30/245


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10326
Subject		: inconsistent lock state in net_rx_action
Submitter	: Marcus Better <marcus@better.se>
Date		: 2008-03-25 13:21 (10 days old)
Patch		: http://bugzilla.kernel.org/show_bug.cgi?id=10326#c20


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10153
Subject		: (regression) kernel/timeconst.h bugs with HZ=128
Submitter	: David Brownell <david-b@pacbell.net>
Date		: 2008-02-26 19:32 (38 days old)
References	: http://lkml.org/lkml/2008/2/26/294
Handled-By	: H. Peter Anvin <hpa@zytor.com>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=15114&amp;action=view
		  http://bugzilla.kernel.org/attachment.cgi?id=15115&amp;action=view


For details, please visit the bug entries and follow the links given in
references.

As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions from 2.6.24,
unresolved as well as resolved, at:

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

Please let me know if there are any Bugzilla entries that should be added to
the list in there.

Thanks,
Rafael

TUNER_TDA8290=y, VIDEO_DEV=n build error

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10067
Subject		: TUNER_TDA8290=y, VIDEO_DEV=n build error
Submitter	: Toralf Foerster <toralf.foerster@gmx.de>
Date		: 2008-02-22 10:36 (42 days old)
References	: http://lkml.org/lkml/2008/2/19/262

2.6.25-rc2-git4 - Kernel oops while running kernbench and tbench on powerpc

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10082
Subject		: 2.6.25-rc2-git4 - Kernel oops while running kernbench and tbench on powerpc
Submitter	: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Date		: 2008-02-20 16:01 (44 days old)
References	: http://lkml.org/lkml/2008/2/20/218
		  http://lkml.org/lkml/2008/1/18/71

2.6.25-current-git hangs on boot (pci=nommconf helps)

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10117
Subject		: 2.6.25-current-git hangs on boot (pci=nommconf helps)
Submitter	: Soeren Sonnenburg <kernel@nn7.de>
Date		: 2008-02-23 18:55 (41 days old)
References	: http://lkml.org/lkml/2008/2/23/263

KVM & Qemu crashed with infinite recursive kernel loop in the guest

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10156
Subject		: KVM & Qemu crashed with infinite recursive kernel loop in the guest
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2008-02-28 11:25 (36 days old)
References	: http://lkml.org/lkml/2008/2/28/106

kvm: INFO: inconsistent lock state

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10172
Subject		: kvm: INFO: inconsistent lock state
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2008-03-05 03:26 (30 days old)

INFO: possible circular locking in the resume

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10133
Subject		: INFO: possible circular locking in the resume
Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date		: 2008-02-27 (37 days old)
References	: http://lkml.org/lkml/2008/2/26/479
Handled-By	: Gautham R Shenoy <ego@in.ibm.com>

2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n - Apple

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10093
Subject		: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n - Apple
Submitter	: Soeren Sonnenburg <kernel@nn7.de>
Date		: 2008-02-23 18:55 (41 days old)
References	: http://lkml.org/lkml/2008/2/23/263
		  http://marc.info/?l=linux-acpi&amp;m=120387537018467&amp;w=4
Handled-By	: Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>

2.6.25-git regression with snd-hda-intel on Dell XPS M1330, no analog sound

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10302
Subject		: 2.6.25-git regression with snd-hda-intel on Dell XPS M1330, no analog sound
Submitter	: Andre Tomt <andre@tomt.net>
Date		: 2008-03-21 20:03 (14 days old)
References	: http://lkml.org/lkml/2008/3/21/295
Handled-By	: Matthew Ranostay <mranostay@embeddedalley.com>

[BUG] Linux 2.6.25-rc6 - kernel BUG at fs/mpage.c:476! on powerpc

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10290
Subject		: [BUG] Linux 2.6.25-rc6 - kernel BUG at fs/mpage.c:476! on powerpc
Submitter	: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Date		: 2008-03-20 13:13 (15 days old)
References	: http://lkml.org/lkml/2008/3/20/39

volume wheel does not work in 2.6.25-rc6

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10300
Subject		: volume wheel does not work in 2.6.25-rc6
Submitter	: Romano Giannetti <romano.giannetti@gmail.com>
Date		: 2008-03-21 11:42 (14 days old)

2.6.25-rc6 regression - hang on resume

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10319
Subject		: 2.6.25-rc6 regression - hang on resume
Submitter	: Soeren Sonnenburg <kernel@nn7.de>
Date		: 2008-03-25 04:44 (10 days old)

panic using bridging on linus kernel 2.6.25-rc6

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10323
Subject		: panic using bridging on linus kernel 2.6.25-rc6
Submitter	: Andy Gospodarek <andy@greyhouse.net>
Date		: 2008-03-25 11:40 (10 days old)

rt2x00 does not associate or give scan results

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10320
Subject		: rt2x00 does not associate or give scan results
Submitter	: Marcus Better <marcus@better.se>
Date		: 2008-03-25 06:04 (10 days old)

kernel panic ip_route_input

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10324
Subject		: kernel panic ip_route_input
Submitter	: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
Date		: 2008-03-25 12:48 (10 days old)

inconsistent lock state in net_rx_action

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10326
Subject		: inconsistent lock state in net_rx_action
Submitter	: Marcus Better <marcus@better.se>
Date		: 2008-03-25 13:21 (10 days old)
Patch		: http://bugzilla.kernel.org/show_bug.cgi?id=10326#c20

Linux 2.6.25-rc6: WARNING: at net/ipv4/tcp_input.c:2510

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10346
Subject		: Linux 2.6.25-rc6: WARNING: at net/ipv4/tcp_input.c:2510
Submitter	: Georgi Chorbadzhiyski <gf@unixsol.org>
Date		: 2008-03-27 17:29 (8 days old)
References	: http://lkml.org/lkml/2008/3/27/246

regression: am-utils stopped working in 2.6.25-rc*

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10349
Subject		: regression: am-utils stopped working in 2.6.25-rc*
Submitter	: Meelis Roos <mroos@linux.ee>
Date		: 2008-03-28 15:20 (7 days old)
References	: http://lkml.org/lkml/2008/3/28/174

[2.6.25-rc6] possible regression: X server dying

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10344
Subject		: [2.6.25-rc6] possible regression: X server dying
Submitter	: Tilman Schmidt <tilman@imap.cc>
Date		: 2008-03-24 23:38 (11 days old)
References	: http://lkml.org/lkml/2008/3/24/260
Handled-By	: Dave Airlie <airlied@gmail.com>

usb-storage, error reading the last 8 sectors, regression in 2.6.25-rc7

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10365
Subject		: usb-storage, error reading the last 8 sectors, regression in 2.6.25-rc7
Submitter	: Sergey Dolgov <solkaa@gmail.com>
Date		: 2008-03-30 11:49 (5 days old)
References	: http://lkml.org/lkml/2008/3/30/11

slub compile error

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10373
Subject		: slub compile error
Submitter	: Toralf Foerster <toralf.foerster@gmx.de>
Date		: 2008-03-31 14:46 (4 days old)
References	: http://lkml.org/lkml/2008/3/31/120
Handled-By	: Christoph Lameter <clameter@sgi.com>
Patch		: http://lkml.org/lkml/2008/3/31/261

2.6.25-rc7: warn_on_slowpath triggered

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10366
Subject		: 2.6.25-rc7: warn_on_slowpath triggered
Submitter	: Bob Tracy <rct@frus.com>
Date		: 2008-03-29 17:29 (6 days old)
References	: http://lkml.org/lkml/2008/3/29/125
Handled-By	: Bjoern Steinbrink <B.Steinbrink@gmx.de>
Patch		: http://lkml.org/lkml/2008/3/30/245

Kernel freezes during boot when AC is unplugged

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10377
Subject		: Kernel freezes during boot when AC is unplugged
Submitter	: Roman Jarosz <kedgedev@centrum.cz>
Date		: 2008-04-01 16:23 (3 days old)

The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10369
Subject		: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7
Submitter	: Chr <chunkeey@web.de>
Date		: 2008-03-30 21:09 (5 days old)
References	: http://lkml.org/lkml/2008/3/30/87

2.6.25-rc5.git4 regression PS/2 mouse not detected/working

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10382
Subject		: 2.6.25-rc5.git4 regression PS/2 mouse not detected/working
Submitter	: Yanko Kaneti <yaneti@declera.com>
Date		: 2008-04-02 10:59 (2 days old)
References	: http://lkml.org/lkml/2008/4/2/210
Handled-By	: Dmitry Torokhov <dmitry.torokhov@gmail.com>
		  Balaji Rao <balajirrao@gmail.com>

rc6+ regression - backlight reset to 0 on boot after 7c0ea45be4f114d85ee35caeead8e1660699c46f

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10387
Subject		: rc6+ regression - backlight reset to 0 on boot after 7c0ea45be4f114d85ee35caeead8e1660699c46f
Submitter	: Andrey Borzenkov <arvidjaar@mail.ru>
Date		: 2008-04-02 22:53 (2 days old)
References	: http://lkml.org/lkml/2008/4/2/366

2.6.25-rc7/8: Another resume regression

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10391
Subject		: 2.6.25-rc7/8: Another resume regression
Submitter	: Mark Lord <lkml@rtr.ca>
Date		: 2008-04-03 15:06 (1 days old)
References	: http://lkml.org/lkml/2008/4/3/283

Oops while reading /proc/ioports or /proc/iomem

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10390
Subject		: Oops while reading /proc/ioports or /proc/iomem
Submitter	: Jan Kara <jack@suse.cz>
Date		: 2008-04-03 15:25 (1 days old)
References	: http://lkml.org/lkml/2008/4/3/149

2.6.25-rc6-git2: warn_on_slowpath for tcp_simple_retransmit

[Rafael J. Wysocki]

The following report is on the current list of known regressions
from 2.6.24.  Please verify if the issue is still present in the
mainline.


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10384
Subject		: 2.6.25-rc6-git2: warn_on_slowpath for tcp_simple_retransmit
Submitter	: Alessandro Suardi <alessandro.suardi@gmail.com>
Date		: 2008-04-02 00:28 (2 days old)
References	: http://lkml.org/lkml/2008/4/1/408
Handled-By	: Ilpo Jarvinen <ilpo.jarvinen@helsinki.fi>

Re: 2.6.25-rc8-git2: Reported regressions from 2.6.24

[Linus Torvalds]

On Fri, 4 Apr 2008, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10390
> Subject		: Oops while reading /proc/ioports or /proc/iomem
> Submitter	: Jan Kara <jack@suse.cz>
> Date		: 2008-04-03 15:25 (1 days old)
> References	: http://lkml.org/lkml/2008/4/3/149

This sounds very much like some module registered IO ports/memory and was 
then unloaded without unregistering them.

It's a bit hard to guess which module it is, though. The oops says "[last 
unloaded: parport]", so that's likely to be the area.

So I *suspect* this patch might be relevant. Bug apparently introduced in 
f63fd7e299ee13da071ecfce2b90b58c5e1562b1 ("parport_pc: detection for 
SuperIO IT87XX POST") by Petr Cvek.

Petr?

		Linus

---
 drivers/parport/parport_pc.c |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/drivers/parport/parport_pc.c b/drivers/parport/parport_pc.c
index d76d37b..a858089 100644
--- a/drivers/parport/parport_pc.c
+++ b/drivers/parport/parport_pc.c
@@ -1568,9 +1568,8 @@ static void __devinit detect_and_report_it87(void)
 		outb(r | 8, 0x2F);
 		outb(0x02, 0x2E);	/* Lock */
 		outb(0x02, 0x2F);
-
-		release_region(0x2e, 1);
 	}
+	release_region(0x2e, 1);
 }
 #endif /* CONFIG_PARPORT_PC_SUPERIO */
 

RE: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n - Apple

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Rafael J. Wysocki [mailto:rjw@sisk.pl] 
>Sent: Thursday, April 03, 2008 4:23 PM
>To: Linux Kernel Mailing List
>Cc: Pallipadi@ogre.sisk.pl; Pallipadi, Venkatesh; Soeren Sonnenburg
>Subject: 2.6.25-current-git hangs on boot unless 
>CONFIG_CPU_IDLE=n - Apple
>
>The following report is on the current list of known regressions
>from 2.6.24.  Please verify if the issue is still present in the
>mainline.
>
>
>Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10093
>Subject		: 2.6.25-current-git hangs on boot 
>unless CONFIG_CPU_IDLE=n - Apple
>Submitter	: Soeren Sonnenburg <kernel@nn7.de>
>Date		: 2008-02-23 18:55 (41 days old)
>References	: http://lkml.org/lkml/2008/2/23/263
>		  
>http://marc.info/?l=linux-acpi&amp;m=120387537018467&amp;w=4
>Handled-By	: Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>
>

Last comment I saw from Soeren says it does not really hang. It waits
for 5-10 seconds sometimes before continuing. We are still trying to
narrow this down with max_cstate etc..

Thanks,
Venki

Re: kernel panic ip_route_input

[David Miller]

From: "Rafael J. Wysocki" <rjw@sisk.pl>
Date: Fri,  4 Apr 2008 01:22:43 +0200 (CEST)

> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10324
> Subject		: kernel panic ip_route_input
> Submitter	: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
> Date		: 2008-03-25 12:48 (10 days old)

This has been confirmed by the reporter to be fixed in the current
tree.

Re: inconsistent lock state in net_rx_action

[David Miller]

From: "Rafael J. Wysocki" <rjw@sisk.pl>
Date: Fri,  4 Apr 2008 01:22:43 +0200 (CEST)

> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10326
> Subject		: inconsistent lock state in net_rx_action
> Submitter	: Marcus Better <marcus@better.se>
> Date		: 2008-03-25 13:21 (10 days old)
> Patch		: http://bugzilla.kernel.org/show_bug.cgi?id=10326#c20

The patch in the report has been added to the tree
and it fixes this problem.

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n - Apple

[Carlos R. Mafra]

On Thu  3.Apr'08 at 17:14:22 -0700, Pallipadi, Venkatesh wrote:
> >The following report is on the current list of known regressions
> >from 2.6.24.  Please verify if the issue is still present in the
> >mainline.
> >
> >
> >Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10093
> >Subject		: 2.6.25-current-git hangs on boot 
> >unless CONFIG_CPU_IDLE=n - Apple
> >Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> >Date		: 2008-02-23 18:55 (41 days old)
> >References	: http://lkml.org/lkml/2008/2/23/263
> >		  
> >http://marc.info/?l=linux-acpi&amp;m=120387537018467&amp;w=4
> >Handled-By	: Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>
> >
> 
> Last comment I saw from Soeren says it does not really hang. It waits
> for 5-10 seconds sometimes before continuing. We are still trying to
> narrow this down with max_cstate etc..

I should say that my laptop (Vaio) _hangs_ at boot (less than 10% of boots)
and this is the last message I see:

"ACPI: Processor [CPU1] (supports 8 throttling states)"

and it stays there "forever" (more than 1 or 2 minutes at least).

I am not using my laptop too much these days, and I thought this
bug had been solved because it didn't hang for the last week (but
I boot it once per day), however it hang last night (using some
post 2.6.25-rc7 kernel)

I have pictures of the screen while showing this last message at boot, 
should I post it somewhere or that is not necessary?.

Re: slub compile error

[Christoph Lameter]

On Fri, 4 Apr 2008, Rafael J. Wysocki wrote:

> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.

The bug was not in 2.6.24. It was introduced a couple of days 
before 2.6.25-rc8 and the fix was the last commit added before rc8 was 
released.

Re: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7

[Chr]

On Friday 04 April 2008 01:22:44 Rafael J. Wysocki wrote:
> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10369
> Subject		: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7
> Submitter	: Chr <chunkeey@web.de>
> Date		: 2008-03-30 21:09 (5 days old)
> References	: http://lkml.org/lkml/2008/3/30/87

Yep, it's still present... but I don't have no time to debug it. :(

Rhe proposed workaround: "noapictimer" and "hpet=force" works so far...
Maybe it's buggy/bad hardware after all and 2.6.24.4 just doesn't trigger it?! 

Regards,
	Chr.

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n - Apple

[Ray Lee]

On Thu, Apr 3, 2008 at 6:10 PM, Carlos R. Mafra <crmafra2@gmail.com> wrote:
> On Thu  3.Apr'08 at 17:14:22 -0700, Pallipadi, Venkatesh wrote:
>  > >The following report is on the current list of known regressions
>  > >from 2.6.24.  Please verify if the issue is still present in the
>  > >mainline.
>  > >
>  > >
>  > >Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=10093
>  > >Subject              : 2.6.25-current-git hangs on boot
>  > >unless CONFIG_CPU_IDLE=n - Apple
>  > >Submitter    : Soeren Sonnenburg <kernel@nn7.de>
>  > >Date         : 2008-02-23 18:55 (41 days old)
>  > >References   : http://lkml.org/lkml/2008/2/23/263
>  > >
>  > >http://marc.info/?l=linux-acpi&amp;m=120387537018467&amp;w=4
>  > >Handled-By   : Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>
>  > >
>  >
>  > Last comment I saw from Soeren says it does not really hang. It waits
>  > for 5-10 seconds sometimes before continuing. We are still trying to
>  > narrow this down with max_cstate etc..
>
>  I should say that my laptop (Vaio) _hangs_ at boot (less than 10% of boots)
>  and this is the last message I see:
>
>  "ACPI: Processor [CPU1] (supports 8 throttling states)"
>
>  and it stays there "forever" (more than 1 or 2 minutes at least).
>
>  I am not using my laptop too much these days, and I thought this
>  bug had been solved because it didn't hang for the last week (but
>  I boot it once per day), however it hang last night (using some
>  post 2.6.25-rc7 kernel)
>
>  I have pictures of the screen while showing this last message at boot,
>  should I post it somewhere or that is not necessary?.

If the sysrq key still works when that happens, try to do a sysrq-t,
s, b to generate a trace, sync the filesystem, and reboot. If anything
made it to the logs, please post it.

Re: 2.6.25-rc8-git2: Reported regressions from 2.6.24

[Andrew Morton]

On Thu, 3 Apr 2008 16:59:02 -0700 (PDT) Linus Torvalds <torvalds@linux-foundation.org> wrote:

> 
> 
> On Fri, 4 Apr 2008, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10390
> > Subject		: Oops while reading /proc/ioports or /proc/iomem
> > Submitter	: Jan Kara <jack@suse.cz>
> > Date		: 2008-04-03 15:25 (1 days old)
> > References	: http://lkml.org/lkml/2008/4/3/149
> 
> This sounds very much like some module registered IO ports/memory and was 
> then unloaded without unregistering them.
> 
> It's a bit hard to guess which module it is, though. The oops says "[last 
> unloaded: parport]", so that's likely to be the area.
> 
> So I *suspect* this patch might be relevant. Bug apparently introduced in 
> f63fd7e299ee13da071ecfce2b90b58c5e1562b1 ("parport_pc: detection for 
> SuperIO IT87XX POST") by Petr Cvek.
> 
> Petr?
> 
> 		Linus
> 
> ---
>  drivers/parport/parport_pc.c |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/parport/parport_pc.c b/drivers/parport/parport_pc.c
> index d76d37b..a858089 100644
> --- a/drivers/parport/parport_pc.c
> +++ b/drivers/parport/parport_pc.c
> @@ -1568,9 +1568,8 @@ static void __devinit detect_and_report_it87(void)
>  		outb(r | 8, 0x2F);
>  		outb(0x02, 0x2E);	/* Lock */
>  		outb(0x02, 0x2F);
> -
> -		release_region(0x2e, 1);
>  	}
> +	release_region(0x2e, 1);
>  }
>  #endif /* CONFIG_PARPORT_PC_SUPERIO */

Looks very correct to me.

Re: INFO: possible circular locking in the resume

[Gautham R Shenoy]

On Fri, Apr 04, 2008 at 01:22:43AM +0200, Rafael J. Wysocki wrote:
> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10133
> Subject		: INFO: possible circular locking in the resume
> Submitter	: Zdenek Kabelac <zdenek.kabelac@gmail.com>
> Date		: 2008-02-27 (37 days old)
> References	: http://lkml.org/lkml/2008/2/26/479
> Handled-By	: Gautham R Shenoy <ego@in.ibm.com>
> 

Yes it still is present in the mainline.

Sorry, didn't have time to fix it, since I have been busy with other stuff. 
Will have a look at it over the weekend.

-- 
Thanks and Regards
gautham

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n - Apple

[Soeren Sonnenburg]

On Thu, 2008-04-03 at 20:15 -0700, Ray Lee wrote:
> On Thu, Apr 3, 2008 at 6:10 PM, Carlos R. Mafra <crmafra2@gmail.com> wrote:
> > On Thu  3.Apr'08 at 17:14:22 -0700, Pallipadi, Venkatesh wrote:
> >  > >The following report is on the current list of known regressions
> >  > >from 2.6.24.  Please verify if the issue is still present in the
> >  > >mainline.
> >  > >
> >  > >
> >  > >Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=10093
> >  > >Subject              : 2.6.25-current-git hangs on boot
> >  > >unless CONFIG_CPU_IDLE=n - Apple
> >  > >Submitter    : Soeren Sonnenburg <kernel@nn7.de>
> >  > >Date         : 2008-02-23 18:55 (41 days old)
> >  > >References   : http://lkml.org/lkml/2008/2/23/263
> >  > >
> >  > >http://marc.info/?l=linux-acpi&m=120387537018467&w=4
> >  > >Handled-By   : Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>
> >  > >
> >  >
> >  > Last comment I saw from Soeren says it does not really hang. It waits
> >  > for 5-10 seconds sometimes before continuing. We are still trying to
> >  > narrow this down with max_cstate etc..
> >
> >  I should say that my laptop (Vaio) _hangs_ at boot (less than 10% of boots)
> >  and this is the last message I see:
> >
> >  "ACPI: Processor [CPU1] (supports 8 throttling states)"
> >
> >  and it stays there "forever" (more than 1 or 2 minutes at least).
> >
> >  I am not using my laptop too much these days, and I thought this
> >  bug had been solved because it didn't hang for the last week (but
> >  I boot it once per day), however it hang last night (using some
> >  post 2.6.25-rc7 kernel)
> >
> >  I have pictures of the screen while showing this last message at boot,
> >  should I post it somewhere or that is not necessary?.
> 
> If the sysrq key still works when that happens, try to do a sysrq-t,
> s, b to generate a trace, sync the filesystem, and reboot. If anything
> made it to the logs, please post it.

How could I potentially do that on this #^%^! apple keyboard?
Soeren

Re: regression: am-utils stopped working in 2.6.25-rc*

[Meelis Roos]

> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10349
> Subject		: regression: am-utils stopped working in 2.6.25-rc*
> Submitter	: Meelis Roos <mroos@linux.ee>
> Date		: 2008-03-28 15:20 (7 days old)
> References	: http://lkml.org/lkml/2008/3/28/174

Still present, active discussion in bugzilla. At least partly am-utils 
problem (actually there are 2 of them, one am-utils mount structure 
version problem, another NFS locking problem that was also uncoveredy by 
stricter checking in 2.6.25).

-- 
Meelis Roos (mroos@linux.ee)

Re: 2.6.25-rc6 regression - hang on resume

[Soeren Sonnenburg]

On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10319
> Subject		: 2.6.25-rc6 regression - hang on resume
> Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> Date		: 2008-03-25 04:44 (10 days old)

Yes. The machine resumes and display stays black using s2ram -f -p
(blindly typing reboot etc on keyboard does what is expected). However
display comes back on 2.6.24.

Soeren

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n - Apple

[Soeren Sonnenburg]

On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10093
> Subject		: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n - Apple
> Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> Date		: 2008-02-23 18:55 (41 days old)
> References	: http://lkml.org/lkml/2008/2/23/263
> 		  http://marc.info/?l=linux-acpi&m=120387537018467&w=4
> Handled-By	: Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>

yes still there, but not a hangs forever hang anymore but only a hang
for (this time) 15 seconds hang.

Soeren

RE: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n -Apple

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Soeren Sonnenburg [mailto:kernel@nn7.de] 
>Sent: Thursday, April 03, 2008 11:32 PM
>To: Rafael J. Wysocki
>Cc: Linux Kernel Mailing List; Pallipadi@ogre.sisk.pl; 
>Pallipadi, Venkatesh
>Subject: Re: 2.6.25-current-git hangs on boot unless 
>CONFIG_CPU_IDLE=n -Apple
>
>On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
>> The following report is on the current list of known regressions
>> from 2.6.24.  Please verify if the issue is still present in the
>> mainline.
>> 
>> 
>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10093
>> Subject		: 2.6.25-current-git hangs on boot 
>unless CONFIG_CPU_IDLE=n - Apple
>> Submitter	: Soeren Sonnenburg <kernel@nn7.de>
>> Date		: 2008-02-23 18:55 (41 days old)
>> References	: http://lkml.org/lkml/2008/2/23/263
>> 		  http://marc.info/?l=linux-acpi&m=120387537018467&w=4
>> Handled-By	: Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>
>
>yes still there, but not a hangs forever hang anymore but only a hang
>for (this time) 15 seconds hang.
>

Can you please try the max_cstate experiments that I mentioned in the
bugzilla.

Thanks,
Venki

Re: 2.6.25-current-git hangs on boot (pci=nommconf helps)

[Soeren Sonnenburg]

On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10117
> Subject		: 2.6.25-current-git hangs on boot (pci=nommconf helps)
> Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> Date		: 2008-02-23 18:55 (41 days old)
> References	: http://lkml.org/lkml/2008/2/23/263

I rebooted >10 times and couldn't trigger this hang with current
mainstream anymore.... so I guess it is gone.

Soeren

Re: TUNER_TDA8290=y, VIDEO_DEV=n build error

[Adrian Bunk]

On Fri, Apr 04, 2008 at 01:20:32AM +0200, Rafael J. Wysocki wrote:
> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.

When you asked me just 2 days ago exactly the same question in the 
Bugzilla entry I immediately confirmed it's still present.

Was anything wrong with my answer (and the subsequent discussions) that 
you now also ask Toralf for confirmation?

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10067
> Subject		: TUNER_TDA8290=y, VIDEO_DEV=n build error
> Submitter	: Toralf Foerster <toralf.foerster@gmx.de>
> Date		: 2008-02-22 10:36 (42 days old)
> References	: http://lkml.org/lkml/2008/2/19/262

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: TUNER_TDA8290=y, VIDEO_DEV=n build error

[Rafael J. Wysocki]

On Friday, 4 of April 2008, Adrian Bunk wrote:
> On Fri, Apr 04, 2008 at 01:20:32AM +0200, Rafael J. Wysocki wrote:
> > The following report is on the current list of known regressions
> > from 2.6.24.  Please verify if the issue is still present in the
> > mainline.
> 
> When you asked me just 2 days ago exactly the same question in the 
> Bugzilla entry I immediately confirmed it's still present.
> 
> Was anything wrong with my answer (and the subsequent discussions) that 
> you now also ask Toralf for confirmation?

This text is automatically added to the messages sent in replies to the main
report.

Well, it probably could be better.  I'm open for suggestions. :-)

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10067
> > Subject		: TUNER_TDA8290=y, VIDEO_DEV=n build error
> > Submitter	: Toralf Foerster <toralf.foerster@gmx.de>
> > Date		: 2008-02-22 10:36 (42 days old)
> > References	: http://lkml.org/lkml/2008/2/19/262

Thanks,
Rafael

Re: kernel panic ip_route_input

[Rafael J. Wysocki]

On Friday, 4 of April 2008, David Miller wrote:
> From: "Rafael J. Wysocki" <rjw@sisk.pl>
> Date: Fri,  4 Apr 2008 01:22:43 +0200 (CEST)
> 
> > The following report is on the current list of known regressions
> > from 2.6.24.  Please verify if the issue is still present in the
> > mainline.
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10324
> > Subject		: kernel panic ip_route_input
> > Submitter	: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
> > Date		: 2008-03-25 12:48 (10 days old)
> 
> This has been confirmed by the reporter to be fixed in the current
> tree.

I've closed the bug.

Thanks,
Rafael

Re: slub compile error

[Rafael J. Wysocki]

On Friday, 4 of April 2008, Christoph Lameter wrote:
> On Fri, 4 Apr 2008, Rafael J. Wysocki wrote:
> 
> > The following report is on the current list of known regressions
> > from 2.6.24.  Please verify if the issue is still present in the
> > mainline.
> 
> The bug was not in 2.6.24. It was introduced a couple of days 
> before 2.6.25-rc8 and the fix was the last commit added before rc8 was 
> released.

Bug closed.

Thanks,
Rafael

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n - Apple

[Carlos R. Mafra]

On Thu  3.Apr'08 at 20:15:02 -0700, Ray Lee wrote:
> On Thu, Apr 3, 2008 at 6:10 PM, Carlos R. Mafra <crmafra2@gmail.com> wrote:
> > On Thu  3.Apr'08 at 17:14:22 -0700, Pallipadi, Venkatesh wrote:
> >  > >The following report is on the current list of known regressions
> >  > >from 2.6.24.  Please verify if the issue is still present in the
> >  > >mainline.
> >  > >
> >  > >
> >  > >Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=10093
> >  > >Subject              : 2.6.25-current-git hangs on boot
> >  > >unless CONFIG_CPU_IDLE=n - Apple
> >  > >Submitter    : Soeren Sonnenburg <kernel@nn7.de>
> >  > >Date         : 2008-02-23 18:55 (41 days old)
> >  > >References   : http://lkml.org/lkml/2008/2/23/263
> >  > >
> >  > >http://marc.info/?l=linux-acpi&amp;m=120387537018467&amp;w=4
> >  > >Handled-By   : Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>
> >  > >
> >  >
> >  > Last comment I saw from Soeren says it does not really hang. It waits
> >  > for 5-10 seconds sometimes before continuing. We are still trying to
> >  > narrow this down with max_cstate etc..
> >
> >  I should say that my laptop (Vaio) _hangs_ at boot (less than 10% of boots)
> >  and this is the last message I see:
> >
> >  "ACPI: Processor [CPU1] (supports 8 throttling states)"
> >
> >  and it stays there "forever" (more than 1 or 2 minutes at least).
> >
> >  I am not using my laptop too much these days, and I thought this
> >  bug had been solved because it didn't hang for the last week (but
> >  I boot it once per day), however it hang last night (using some
> >  post 2.6.25-rc7 kernel)
> >
> >  I have pictures of the screen while showing this last message at boot,
> >  should I post it somewhere or that is not necessary?.
> 
> If the sysrq key still works when that happens, try to do a sysrq-t,
> s, b to generate a trace, sync the filesystem, and reboot. If anything
> made it to the logs, please post it.

Sysrq keys don't work when it hangs, I have to push the power button.

Another thing to notice is that when it happens, it usually happens
more times in a row (like 3 times). And then it can take many boots to
happen again.

I've uploaded the picture where it hangs, it is in the very beginning
of the boot process:

http://www.ift.unesp.br/users/crmafra/dsc04673.jpg

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n - Apple

[Soeren Sonnenburg]

On Fri, 2008-04-04 at 08:47 -0300, Carlos R. Mafra wrote:
> On Thu  3.Apr'08 at 20:15:02 -0700, Ray Lee wrote:
> > On Thu, Apr 3, 2008 at 6:10 PM, Carlos R. Mafra <crmafra2@gmail.com> wrote:
> > > On Thu  3.Apr'08 at 17:14:22 -0700, Pallipadi, Venkatesh wrote:
> > >  > >The following report is on the current list of known regressions
> > >  > >from 2.6.24.  Please verify if the issue is still present in the
> > >  > >mainline.
> > >  > >
> > >  > >
> > >  > >Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=10093
> > >  > >Subject              : 2.6.25-current-git hangs on boot
> > >  > >unless CONFIG_CPU_IDLE=n - Apple
> > >  > >Submitter    : Soeren Sonnenburg <kernel@nn7.de>
> > >  > >Date         : 2008-02-23 18:55 (41 days old)
> > >  > >References   : http://lkml.org/lkml/2008/2/23/263
> > >  > >
> > >  > >http://marc.info/?l=linux-acpi&m=120387537018467&w=4
> > >  > >Handled-By   : Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>
> > >  > >
> > >  >
> > >  > Last comment I saw from Soeren says it does not really hang. It waits
> > >  > for 5-10 seconds sometimes before continuing. We are still trying to
> > >  > narrow this down with max_cstate etc..
> > >
> > >  I should say that my laptop (Vaio) _hangs_ at boot (less than 10% of boots)
> > >  and this is the last message I see:
> > >
> > >  "ACPI: Processor [CPU1] (supports 8 throttling states)"
> > >
> > >  and it stays there "forever" (more than 1 or 2 minutes at least).
> > >
> > >  I am not using my laptop too much these days, and I thought this
> > >  bug had been solved because it didn't hang for the last week (but
> > >  I boot it once per day), however it hang last night (using some
> > >  post 2.6.25-rc7 kernel)
> > >
> > >  I have pictures of the screen while showing this last message at boot,
> > >  should I post it somewhere or that is not necessary?.
> > 
> > If the sysrq key still works when that happens, try to do a sysrq-t,
> > s, b to generate a trace, sync the filesystem, and reboot. If anything
> > made it to the logs, please post it.
> 
> Sysrq keys don't work when it hangs, I have to push the power button.
> 
> Another thing to notice is that when it happens, it usually happens
> more times in a row (like 3 times). And then it can take many boots to
> happen again.
> 
> I've uploaded the picture where it hangs, it is in the very beginning
> of the boot process:
> 
> http://www.ift.unesp.br/users/crmafra/dsc04673.jpg

Actually this is 
http://bugzilla.kernel.org/show_bug.cgi?id=10117 ... and what you
describe is exactly what I was seeing. 

However I thought that we are talking about the hang with 
ladder governor as the last message on the screen. Anyway I am not sure
if both bugs are related or not but I couldn't reproduce the throttling
states bug with current mainstream...

Soeren

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n - Apple

[Carlos R. Mafra]

On Fri  4.Apr'08 at 14:10:56 +0200, Soeren Sonnenburg wrote:
> On Fri, 2008-04-04 at 08:47 -0300, Carlos R. Mafra wrote:
> > On Thu  3.Apr'08 at 20:15:02 -0700, Ray Lee wrote:
> > > On Thu, Apr 3, 2008 at 6:10 PM, Carlos R. Mafra <crmafra2@gmail.com> wrote:
> > > > On Thu  3.Apr'08 at 17:14:22 -0700, Pallipadi, Venkatesh wrote:
> > > >  > >The following report is on the current list of known regressions
> > > >  > >from 2.6.24.  Please verify if the issue is still present in the
> > > >  > >mainline.
> > > >  > >
> > > >  > >
> > > >  > >Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=10093
> > > >  > >Subject              : 2.6.25-current-git hangs on boot
> > > >  > >unless CONFIG_CPU_IDLE=n - Apple
> > > >  > >Submitter    : Soeren Sonnenburg <kernel@nn7.de>
> > > >  > >Date         : 2008-02-23 18:55 (41 days old)
> > > >  > >References   : http://lkml.org/lkml/2008/2/23/263
> > > >  > >
> > > >  > >http://marc.info/?l=linux-acpi&m=120387537018467&w=4
> > > >  > >Handled-By   : Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>
> > > >  > >
> > > >  >
> > > >  > Last comment I saw from Soeren says it does not really hang. It waits
> > > >  > for 5-10 seconds sometimes before continuing. We are still trying to
> > > >  > narrow this down with max_cstate etc..
> > > >
> > > >  I should say that my laptop (Vaio) _hangs_ at boot (less than 10% of boots)
> > > >  and this is the last message I see:
> > > >
> > > >  "ACPI: Processor [CPU1] (supports 8 throttling states)"
> > > >
> > > >  and it stays there "forever" (more than 1 or 2 minutes at least).
> > > >
> > > >  I am not using my laptop too much these days, and I thought this
> > > >  bug had been solved because it didn't hang for the last week (but
> > > >  I boot it once per day), however it hang last night (using some
> > > >  post 2.6.25-rc7 kernel)
> > > >
> > > >  I have pictures of the screen while showing this last message at boot,
> > > >  should I post it somewhere or that is not necessary?.
> > > 
> > > If the sysrq key still works when that happens, try to do a sysrq-t,
> > > s, b to generate a trace, sync the filesystem, and reboot. If anything
> > > made it to the logs, please post it.
> > 
> > Sysrq keys don't work when it hangs, I have to push the power button.
> > 
> > Another thing to notice is that when it happens, it usually happens
> > more times in a row (like 3 times). And then it can take many boots to
> > happen again.
> > 
> > I've uploaded the picture where it hangs, it is in the very beginning
> > of the boot process:
> > 
> > http://www.ift.unesp.br/users/crmafra/dsc04673.jpg
> 
> Actually this is 
> http://bugzilla.kernel.org/show_bug.cgi?id=10117 ... and what you
> describe is exactly what I was seeing. 

Ops, I am sorry. But in the bug description which Rafael wrote above
there is a link to your original post

References: http://lkml.org/lkml/2008/2/23/263

so I thought this was the bug being dealt with here.

> However I thought that we are talking about the hang with 
> ladder governor as the last message on the screen. Anyway I am not sure
> if both bugs are related or not but I couldn't reproduce the throttling
> states bug with current mainstream...

I thought that the bug had vanished, but two days ago it happened
again in my Vaio. There were a couple of different messages comparing
to the picture in the link above, but the last message was exactly the
same.

And I see that Rafael closed the bug 
http://bugzilla.kernel.org/show_bug.cgi?id=10117

The hang two days ago was with 2.6.25-rc7-00150-g(can't remember),
do you think the bug was fixed since that kernel?

I will try to test with the latest git, but I don't have internet
access at my house anymore, so I will have to clone the git
repository into my pendrive and take it there...

Re: 2.6.25-rc5.git4 regression PS/2 mouse not detected/working

[Thomas Gleixner]

On Fri, 4 Apr 2008, Rafael J. Wysocki wrote:
> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.

Yes, it is. The revert of the patch which caused that is queued for
todays push to Linus.

Thanks,

	tglx

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10382
> Subject		: 2.6.25-rc5.git4 regression PS/2 mouse not detected/working
> Submitter	: Yanko Kaneti <yaneti@declera.com>
> Date		: 2008-04-02 10:59 (2 days old)
> References	: http://lkml.org/lkml/2008/4/2/210
> Handled-By	: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> 		  Balaji Rao <balajirrao@gmail.com>
> 
> 

Re: 2.6.25-rc7/8: Another resume regression

[Mark Lord]

Rafael J. Wysocki wrote:
> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10391
> Subject		: 2.6.25-rc7/8: Another resume regression
> Submitter	: Mark Lord <lkml@rtr.ca>
> Date		: 2008-04-03 15:06 (1 days old)
> References	: http://lkml.org/lkml/2008/4/3/283
..

Probably still there, but it's not easily reproduceable
and doesn't happen more than once every couple of days or so.

-ml
 

RE: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n -Apple

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: linux-kernel-owner@vger.kernel.org 
>[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of 
>Carlos R. Mafra
>Sent: Friday, April 04, 2008 4:48 AM
>To: Ray Lee
>Cc: Pallipadi, Venkatesh; Rafael J. Wysocki; Linux Kernel 
>Mailing List; Pallipadi@ogre.sisk.pl; Soeren Sonnenburg
>Subject: Re: 2.6.25-current-git hangs on boot unless 
>CONFIG_CPU_IDLE=n -Apple
>
>On Thu  3.Apr'08 at 20:15:02 -0700, Ray Lee wrote:
>> On Thu, Apr 3, 2008 at 6:10 PM, Carlos R. Mafra 
><crmafra2@gmail.com> wrote:
>> > On Thu  3.Apr'08 at 17:14:22 -0700, Pallipadi, Venkatesh wrote:
>> >  > >The following report is on the current list of known 
>regressions
>> >  > >from 2.6.24.  Please verify if the issue is still 
>present in the
>> >  > >mainline.
>> >  > >
>> >  > >
>> >  > >Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=10093
>> >  > >Subject              : 2.6.25-current-git hangs on boot
>> >  > >unless CONFIG_CPU_IDLE=n - Apple
>> >  > >Submitter    : Soeren Sonnenburg <kernel@nn7.de>
>> >  > >Date         : 2008-02-23 18:55 (41 days old)
>> >  > >References   : http://lkml.org/lkml/2008/2/23/263
>> >  > >
>> >  > >http://marc.info/?l=linux-acpi&amp;m=120387537018467&amp;w=4
>> >  > >Handled-By   : Pallipadi, Venkatesh 
><venkatesh.pallipadi@intel.com>
>> >  > >
>> >  >
>> >  > Last comment I saw from Soeren says it does not really 
>hang. It waits
>> >  > for 5-10 seconds sometimes before continuing. We are 
>still trying to
>> >  > narrow this down with max_cstate etc..
>> >
>> >  I should say that my laptop (Vaio) _hangs_ at boot (less 
>than 10% of boots)
>> >  and this is the last message I see:
>> >
>> >  "ACPI: Processor [CPU1] (supports 8 throttling states)"
>> >
>> >  and it stays there "forever" (more than 1 or 2 minutes at least).
>> >
>> >  I am not using my laptop too much these days, and I thought this
>> >  bug had been solved because it didn't hang for the last week (but
>> >  I boot it once per day), however it hang last night (using some
>> >  post 2.6.25-rc7 kernel)
>> >
>> >  I have pictures of the screen while showing this last 
>message at boot,
>> >  should I post it somewhere or that is not necessary?.
>> 
>> If the sysrq key still works when that happens, try to do a sysrq-t,
>> s, b to generate a trace, sync the filesystem, and reboot. 
>If anything
>> made it to the logs, please post it.
>
>Sysrq keys don't work when it hangs, I have to push the power button.
>
>Another thing to notice is that when it happens, it usually happens
>more times in a row (like 3 times). And then it can take many boots to
>happen again.
>
>I've uploaded the picture where it hangs, it is in the very beginning
>of the boot process:
>
>http://www.ift.unesp.br/users/crmafra/dsc04673.jpg


Can you try the latest git and see whether this still is a problem?

Thanks,
Venki

Re: Linux 2.6.25-rc6: WARNING: at net/ipv4/tcp_input.c:2510

[Georgi Chorbadzhiyski]

Around 04/04/08 02:22, Rafael J. Wysocki scribbled:
> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10346
> Subject		: Linux 2.6.25-rc6: WARNING: at net/ipv4/tcp_input.c:2510
> Submitter	: Georgi Chorbadzhiyski <gf@unixsol.org>
> Date		: 2008-03-27 17:29 (8 days old)
> References	: http://lkml.org/lkml/2008/3/27/246

Upgraded to 2.6.25-rc8-00139-ge315c12, the server is running 8 hours
already and it seems it's fixed.

Anyway, should such warnings be threated as regressions?

-- 
Georgi Chorbadzhiyski
http://georgi.unixsol.org/

Re: 2.6.25-rc5.git4 regression PS/2 mouse not detected/working

[Balaji Rao]

On Friday 04 April 2008 07:03:50 pm Thomas Gleixner wrote:
> On Fri, 4 Apr 2008, Rafael J. Wysocki wrote:
> > The following report is on the current list of known regressions
> > from 2.6.24.  Please verify if the issue is still present in the
> > mainline.
> 
> Yes, it is. The revert of the patch which caused that is queued for
> todays push to Linus.
> 
> Thanks,
> 
> 	tglx
> 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10382
> > Subject		: 2.6.25-rc5.git4 regression PS/2 mouse not detected/working
> > Submitter	: Yanko Kaneti <yaneti@declera.com>
> > Date		: 2008-04-02 10:59 (2 days old)
> > References	: http://lkml.org/lkml/2008/4/2/210
> > Handled-By	: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > 		  Balaji Rao <balajirrao@gmail.com>
> > 
> > 
> 
Hi tglx,

I think the following commit should also be reverted. 

commit 37a47db8d7f0f38dac5acf5a13abbc8f401707fa
Author: Balaji Rao <balajirrao@gmail.com>
Date:   Wed Jan 30 13:30:03 2008 +0100

    x86: assign IRQs to HPET timers, fix

-- 
regards,
Balaji Rao

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n -Apple

[Carlos R. Mafra]

On Fri  4.Apr'08 at  7:25:34 -0700, Pallipadi, Venkatesh wrote:
>  
> 
> >-----Original Message-----
> >From: linux-kernel-owner@vger.kernel.org 
> >[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of 
> >Carlos R. Mafra
> >Sent: Friday, April 04, 2008 4:48 AM
> >To: Ray Lee
> >Cc: Pallipadi, Venkatesh; Rafael J. Wysocki; Linux Kernel 
> >Mailing List; Pallipadi@ogre.sisk.pl; Soeren Sonnenburg
> >Subject: Re: 2.6.25-current-git hangs on boot unless 
> >CONFIG_CPU_IDLE=n -Apple
> >
> >On Thu  3.Apr'08 at 20:15:02 -0700, Ray Lee wrote:
> >> On Thu, Apr 3, 2008 at 6:10 PM, Carlos R. Mafra 
> ><crmafra2@gmail.com> wrote:
> >> > On Thu  3.Apr'08 at 17:14:22 -0700, Pallipadi, Venkatesh wrote:
> >> >  > >The following report is on the current list of known 
> >regressions
> >> >  > >from 2.6.24.  Please verify if the issue is still 
> >present in the
> >> >  > >mainline.
> >> >  > >
> >> >  > >
> >> >  > >Bug-Entry    : http://bugzilla.kernel.org/show_bug.cgi?id=10093
> >> >  > >Subject              : 2.6.25-current-git hangs on boot
> >> >  > >unless CONFIG_CPU_IDLE=n - Apple
> >> >  > >Submitter    : Soeren Sonnenburg <kernel@nn7.de>
> >> >  > >Date         : 2008-02-23 18:55 (41 days old)
> >> >  > >References   : http://lkml.org/lkml/2008/2/23/263
> >> >  > >
> >> >  > >http://marc.info/?l=linux-acpi&amp;m=120387537018467&amp;w=4
> >> >  > >Handled-By   : Pallipadi, Venkatesh 
> ><venkatesh.pallipadi@intel.com>
> >> >  > >
> >> >  >
> >> >  > Last comment I saw from Soeren says it does not really 
> >hang. It waits
> >> >  > for 5-10 seconds sometimes before continuing. We are 
> >still trying to
> >> >  > narrow this down with max_cstate etc..
> >> >
> >> >  I should say that my laptop (Vaio) _hangs_ at boot (less 
> >than 10% of boots)
> >> >  and this is the last message I see:
> >> >
> >> >  "ACPI: Processor [CPU1] (supports 8 throttling states)"
> >> >
> >> >  and it stays there "forever" (more than 1 or 2 minutes at least).
> >> >
> >> >  I am not using my laptop too much these days, and I thought this
> >> >  bug had been solved because it didn't hang for the last week (but
> >> >  I boot it once per day), however it hang last night (using some
> >> >  post 2.6.25-rc7 kernel)
> >> >
> >> >  I have pictures of the screen while showing this last 
> >message at boot,
> >> >  should I post it somewhere or that is not necessary?.
> >> 
> >> If the sysrq key still works when that happens, try to do a sysrq-t,
> >> s, b to generate a trace, sync the filesystem, and reboot. 
> >If anything
> >> made it to the logs, please post it.
> >
> >Sysrq keys don't work when it hangs, I have to push the power button.
> >
> >Another thing to notice is that when it happens, it usually happens
> >more times in a row (like 3 times). And then it can take many boots to
> >happen again.
> >
> >I've uploaded the picture where it hangs, it is in the very beginning
> >of the boot process:
> >
> >http://www.ift.unesp.br/users/crmafra/dsc04673.jpg
> 
> 
> Can you try the latest git and see whether this still is a problem?

I've just updated to latest git, but it may take some time for it 
to happen again (the first 3 boots were okay). Last time it happened
with 2.6.25-rc7-00149-gaf8be4e (I checked now). 

Do you have reasons to believe this issue was fixed since then?

RE: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n-Apple

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Carlos R. Mafra [mailto:crmafra2@gmail.com] 
>Sent: Friday, April 04, 2008 8:52 AM
>To: Pallipadi, Venkatesh
>Cc: Ray Lee; Rafael J. Wysocki; Linux Kernel Mailing List; 
>Pallipadi@ogre.sisk.pl; Soeren Sonnenburg
>Subject: Re: 2.6.25-current-git hangs on boot unless 
>CONFIG_CPU_IDLE=n-Apple
>
>On Fri  4.Apr'08 at  7:25:34 -0700, Pallipadi, Venkatesh wrote:
>>  
>> 
>> >-----Original Message-----
>> >From: linux-kernel-owner@vger.kernel.org 
>> >[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of 
>> >Carlos R. Mafra
>> >Sent: Friday, April 04, 2008 4:48 AM
>> >To: Ray Lee
>> >Cc: Pallipadi, Venkatesh; Rafael J. Wysocki; Linux Kernel 
>> >Mailing List; Pallipadi@ogre.sisk.pl; Soeren Sonnenburg
>> >Subject: Re: 2.6.25-current-git hangs on boot unless 
>> >CONFIG_CPU_IDLE=n -Apple
>> >
>> >On Thu  3.Apr'08 at 20:15:02 -0700, Ray Lee wrote:
>> >> On Thu, Apr 3, 2008 at 6:10 PM, Carlos R. Mafra 
>> ><crmafra2@gmail.com> wrote:
>> >> > On Thu  3.Apr'08 at 17:14:22 -0700, Pallipadi, Venkatesh wrote:
>> >> >  > >The following report is on the current list of known 
>> >regressions
>> >> >  > >from 2.6.24.  Please verify if the issue is still 
>> >present in the
>> >> >  > >mainline.
>> >> >  > >
>> >> >  > >
>> >> >  > >Bug-Entry    : 
>http://bugzilla.kernel.org/show_bug.cgi?id=10093
>> >> >  > >Subject              : 2.6.25-current-git hangs on boot
>> >> >  > >unless CONFIG_CPU_IDLE=n - Apple
>> >> >  > >Submitter    : Soeren Sonnenburg <kernel@nn7.de>
>> >> >  > >Date         : 2008-02-23 18:55 (41 days old)
>> >> >  > >References   : http://lkml.org/lkml/2008/2/23/263
>> >> >  > >
>> >> >  > >http://marc.info/?l=linux-acpi&amp;m=120387537018467&amp;w=4
>> >> >  > >Handled-By   : Pallipadi, Venkatesh 
>> ><venkatesh.pallipadi@intel.com>
>> >> >  > >
>> >> >  >
>> >> >  > Last comment I saw from Soeren says it does not really 
>> >hang. It waits
>> >> >  > for 5-10 seconds sometimes before continuing. We are 
>> >still trying to
>> >> >  > narrow this down with max_cstate etc..
>> >> >
>> >> >  I should say that my laptop (Vaio) _hangs_ at boot (less 
>> >than 10% of boots)
>> >> >  and this is the last message I see:
>> >> >
>> >> >  "ACPI: Processor [CPU1] (supports 8 throttling states)"
>> >> >
>> >> >  and it stays there "forever" (more than 1 or 2 minutes 
>at least).
>> >> >
>> >> >  I am not using my laptop too much these days, and I 
>thought this
>> >> >  bug had been solved because it didn't hang for the 
>last week (but
>> >> >  I boot it once per day), however it hang last night (using some
>> >> >  post 2.6.25-rc7 kernel)
>> >> >
>> >> >  I have pictures of the screen while showing this last 
>> >message at boot,
>> >> >  should I post it somewhere or that is not necessary?.
>> >> 
>> >> If the sysrq key still works when that happens, try to do 
>a sysrq-t,
>> >> s, b to generate a trace, sync the filesystem, and reboot. 
>> >If anything
>> >> made it to the logs, please post it.
>> >
>> >Sysrq keys don't work when it hangs, I have to push the 
>power button.
>> >
>> >Another thing to notice is that when it happens, it usually happens
>> >more times in a row (like 3 times). And then it can take 
>many boots to
>> >happen again.
>> >
>> >I've uploaded the picture where it hangs, it is in the very 
>beginning
>> >of the boot process:
>> >
>> >http://www.ift.unesp.br/users/crmafra/dsc04673.jpg
>> 
>> 
>> Can you try the latest git and see whether this still is a problem?
>
>I've just updated to latest git, but it may take some time for it 
>to happen again (the first 3 boots were okay). Last time it happened
>with 2.6.25-rc7-00149-gaf8be4e (I checked now). 
>
>Do you have reasons to believe this issue was fixed since then?

Yes. I think the patch here should have fixed the problem....
Patch : http://marc.info/?l=linux-kernel&m=120674502201007&w=4

Thanks,
Venki

>

RE: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n-Apple

[Soeren Sonnenburg]

On Fri, 2008-04-04 at 10:37 -0700, Pallipadi, Venkatesh wrote:
[...]
> >> Can you try the latest git and see whether this still is a problem?
> >
> >I've just updated to latest git, but it may take some time for it 
> >to happen again (the first 3 boots were okay). Last time it happened
> >with 2.6.25-rc7-00149-gaf8be4e (I checked now). 
> >
> >Do you have reasons to believe this issue was fixed since then?
> 
> Yes. I think the patch here should have fixed the problem....
> Patch : http://marc.info/?l=linux-kernel&m=120674502201007&w=4

But this patch is not in the current mainstream... (yet?)
Soeren

Re: 2.6.25-rc5.git4 regression PS/2 mouse not detected/working

[Thomas Gleixner]

On Fri, 4 Apr 2008, Balaji Rao wrote:

> On Friday 04 April 2008 07:03:50 pm Thomas Gleixner wrote:
> > On Fri, 4 Apr 2008, Rafael J. Wysocki wrote:
> > > The following report is on the current list of known regressions
> > > from 2.6.24.  Please verify if the issue is still present in the
> > > mainline.
> > 
> > Yes, it is. The revert of the patch which caused that is queued for
> > todays push to Linus.
> > 
> > Thanks,
> > 
> > 	tglx
> > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10382
> > > Subject		: 2.6.25-rc5.git4 regression PS/2 mouse not detected/working
> > > Submitter	: Yanko Kaneti <yaneti@declera.com>
> > > Date		: 2008-04-02 10:59 (2 days old)
> > > References	: http://lkml.org/lkml/2008/4/2/210
> > > Handled-By	: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > > 		  Balaji Rao <balajirrao@gmail.com>
> > > 
> > > 
> > 
> Hi tglx,
> 
> I think the following commit should also be reverted. 
> 
> commit 37a47db8d7f0f38dac5acf5a13abbc8f401707fa
> Author: Balaji Rao <balajirrao@gmail.com>
> Date:   Wed Jan 30 13:30:03 2008 +0100
> 
>     x86: assign IRQs to HPET timers, fix

Yup, I have both.

Anyway, thanks for the reminder 

	tglx

RE: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n-Apple

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Pallipadi, Venkatesh 
>Sent: Friday, April 04, 2008 10:37 AM
>To: 'Carlos R. Mafra'
>Cc: Ray Lee; Rafael J. Wysocki; Linux Kernel Mailing List; 
>Soeren Sonnenburg
>Subject: RE: 2.6.25-current-git hangs on boot unless 
>CONFIG_CPU_IDLE=n-Apple
>
> 
>
>>-----Original Message-----
>>From: Carlos R. Mafra [mailto:crmafra2@gmail.com] 
>>Sent: Friday, April 04, 2008 8:52 AM
>>To: Pallipadi, Venkatesh
>>Cc: Ray Lee; Rafael J. Wysocki; Linux Kernel Mailing List; 
>>Pallipadi@ogre.sisk.pl; Soeren Sonnenburg
>>Subject: Re: 2.6.25-current-git hangs on boot unless 
>>CONFIG_CPU_IDLE=n-Apple
>>
>>On Fri  4.Apr'08 at  7:25:34 -0700, Pallipadi, Venkatesh wrote:
>>>  
>>> 
>>> >-----Original Message-----
>>> >From: linux-kernel-owner@vger.kernel.org 
>>> >[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of 
>>> >Carlos R. Mafra
>>> >Sent: Friday, April 04, 2008 4:48 AM
>>> >To: Ray Lee
>>> >Cc: Pallipadi, Venkatesh; Rafael J. Wysocki; Linux Kernel 
>>> >Mailing List; Pallipadi@ogre.sisk.pl; Soeren Sonnenburg
>>> >Subject: Re: 2.6.25-current-git hangs on boot unless 
>>> >CONFIG_CPU_IDLE=n -Apple
>>> >
>>> >On Thu  3.Apr'08 at 20:15:02 -0700, Ray Lee wrote:
>>> >> On Thu, Apr 3, 2008 at 6:10 PM, Carlos R. Mafra 
>>> ><crmafra2@gmail.com> wrote:
>>> >> > On Thu  3.Apr'08 at 17:14:22 -0700, Pallipadi, Venkatesh wrote:
>>> >> >  > >The following report is on the current list of known 
>>> >regressions
>>> >> >  > >from 2.6.24.  Please verify if the issue is still 
>>> >present in the
>>> >> >  > >mainline.
>>> >> >  > >
>>> >> >  > >
>>> >> >  > >Bug-Entry    : 
>>http://bugzilla.kernel.org/show_bug.cgi?id=10093
>>> >> >  > >Subject              : 2.6.25-current-git hangs on boot
>>> >> >  > >unless CONFIG_CPU_IDLE=n - Apple
>>> >> >  > >Submitter    : Soeren Sonnenburg <kernel@nn7.de>
>>> >> >  > >Date         : 2008-02-23 18:55 (41 days old)
>>> >> >  > >References   : http://lkml.org/lkml/2008/2/23/263
>>> >> >  > >
>>> >> >  > 
>>http://marc.info/?l=linux-acpi&amp;m=120387537018467&amp;w=4
>>> >> >  > >Handled-By   : Pallipadi, Venkatesh 
>>> ><venkatesh.pallipadi@intel.com>
>>> >> >  > >
>>> >> >  >
>>> >> >  > Last comment I saw from Soeren says it does not really 
>>> >hang. It waits
>>> >> >  > for 5-10 seconds sometimes before continuing. We are 
>>> >still trying to
>>> >> >  > narrow this down with max_cstate etc..
>>> >> >
>>> >> >  I should say that my laptop (Vaio) _hangs_ at boot (less 
>>> >than 10% of boots)
>>> >> >  and this is the last message I see:
>>> >> >
>>> >> >  "ACPI: Processor [CPU1] (supports 8 throttling states)"
>>> >> >
>>> >> >  and it stays there "forever" (more than 1 or 2 minutes 
>>at least).
>>> >> >
>>> >> >  I am not using my laptop too much these days, and I 
>>thought this
>>> >> >  bug had been solved because it didn't hang for the 
>>last week (but
>>> >> >  I boot it once per day), however it hang last night 
>(using some
>>> >> >  post 2.6.25-rc7 kernel)
>>> >> >
>>> >> >  I have pictures of the screen while showing this last 
>>> >message at boot,
>>> >> >  should I post it somewhere or that is not necessary?.
>>> >> 
>>> >> If the sysrq key still works when that happens, try to do 
>>a sysrq-t,
>>> >> s, b to generate a trace, sync the filesystem, and reboot. 
>>> >If anything
>>> >> made it to the logs, please post it.
>>> >
>>> >Sysrq keys don't work when it hangs, I have to push the 
>>power button.
>>> >
>>> >Another thing to notice is that when it happens, it usually happens
>>> >more times in a row (like 3 times). And then it can take 
>>many boots to
>>> >happen again.
>>> >
>>> >I've uploaded the picture where it hangs, it is in the very 
>>beginning
>>> >of the boot process:
>>> >
>>> >http://www.ift.unesp.br/users/crmafra/dsc04673.jpg
>>> 
>>> 
>>> Can you try the latest git and see whether this still is a problem?
>>
>>I've just updated to latest git, but it may take some time for it 
>>to happen again (the first 3 boots were okay). Last time it happened
>>with 2.6.25-rc7-00149-gaf8be4e (I checked now). 
>>
>>Do you have reasons to believe this issue was fixed since then?
>
>Yes. I think the patch here should have fixed the problem....
>Patch : http://marc.info/?l=linux-kernel&m=120674502201007&w=4
>

Hmmmm.... Looking at latest git,
The above patch is not yet in git. Can you please apply the above patch
and see whether do you still see the problem.....

Thanks,
Venki

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n-Apple

[Carlos R. Mafra]

On Fri  4.Apr'08 at 13:41:45 -0700, Pallipadi, Venkatesh wrote:

> >>> Can you try the latest git and see whether this still is a problem?
> >>
> >>I've just updated to latest git, but it may take some time for it 
> >>to happen again (the first 3 boots were okay). Last time it happened
> >>with 2.6.25-rc7-00149-gaf8be4e (I checked now). 
> >>
> >>Do you have reasons to believe this issue was fixed since then?
> >
> >Yes. I think the patch here should have fixed the problem....
> >Patch : http://marc.info/?l=linux-kernel&m=120674502201007&w=4
> >
> 
> Hmmmm.... Looking at latest git,
> The above patch is not yet in git. Can you please apply the above patch
> and see whether do you still see the problem.....

OK, I will apply it manually and test it.

For the record: yesterday my laptop hang at boot with v2.6.25-rc8-139-ge315c12
(without the above patch).

Re: 2.6.25-rc8-git2: Reported regressions from 2.6.24

[Linus Torvalds]

On Fri, 4 Apr 2008, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10349
> Subject		: regression: am-utils stopped working in 2.6.25-rc*
> Submitter	: Meelis Roos <mroos@linux.ee>
> Date		: 2008-03-28 15:20 (7 days old)
> References	: http://lkml.org/lkml/2008/3/28/174

This seems to be a bug in am-utils:

	https://bugzilla.am-utils.org/show_bug.cgi?id=612

and while we try very hard to not break existing binaries that assume some 
old broken kernel behaviour, things like system setup code that is 
outright buggy is kind of exempt from that rule. So I think in this case 
it really is a user-level issue.

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10346
> Subject		: Linux 2.6.25-rc6: WARNING: at net/ipv4/tcp_input.c:2510
> Submitter	: Georgi Chorbadzhiyski <gf@unixsol.org>
> Date		: 2008-03-27 17:29 (8 days old)
> References	: http://lkml.org/lkml/2008/3/27/246

I wouldn't call this a regression. It's a hard-to-trigger warning that is 
being debugged. 

			Linus

Re: 2.6.25-git regression with snd-hda-intel on Dell XPS M1330, no analog sound

[Bill Davidsen]

Rafael J. Wysocki wrote:
> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10302
> Subject		: 2.6.25-git regression with snd-hda-intel on Dell XPS M1330, no analog sound
> Submitter	: Andre Tomt <andre@tomt.net>
> Date		: 2008-03-21 20:03 (14 days old)
> References	: http://lkml.org/lkml/2008/3/21/295
> Handled-By	: Matthew Ranostay <mranostay@embeddedalley.com>
> 
> 
Is this by any chance related to the RTC old/new vs. sound problem noted 
in another thread?

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

Re: (regression) kernel/timeconst.h bugs with HZ=128

[David Brownell]

On Thursday 03 April 2008, Rafael J. Wysocki wrote:
> The following report is on the current list of known regressions
> from 2.6.24.  Please verify if the issue is still present in the
> mainline.
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10153
> Subject		: (regression) kernel/timeconst.h bugs with HZ=128

The (new) compiler warnings are still being issued, yes.


> Submitter	: David Brownell <david-b@pacbell.net>
> Date		: 2008-02-26 19:32 (38 days old)
> References	: http://lkml.org/lkml/2008/2/26/294
> Handled-By	: H. Peter Anvin <hpa@zytor.com>
> Patch		: http://bugzilla.kernel.org/attachment.cgi?id=15114&amp;action=view
> 		  http://bugzilla.kernel.org/attachment.cgi?id=15115&amp;action=view
> 
> 

Re: (regression) kernel/timeconst.h bugs with HZ=128

[H. Peter Anvin]

David Brownell wrote:
> 
> The (new) compiler warnings are still being issued, yes.
> 

I have a cleaner patchset prepared than the one that got bikeshed 
painted out of existence, but I want to wait until post-2.6.25 for it.

The nice thing is that it deletes a lot more code than it adds:

  include/asm-alpha/types.h      |   36 --------------
  include/asm-arm/types.h        |   33 -------------
  include/asm-avr32/types.h      |   32 -------------
  include/asm-blackfin/types.h   |   34 -------------
  include/asm-cris/types.h       |   33 -------------
  include/asm-frv/types.h        |   34 -------------
  include/asm-generic/Kbuild     |    2
  include/asm-generic/int-l64.h  |   71 ++++++++++++++++++++++++++++
  include/asm-generic/int-ll64.h |   76 +++++++++++++++++++++++++++++++
  include/asm-h8300/types.h      |   33 -------------
  include/asm-ia64/types.h       |   31 ------------
  include/asm-m32r/types.h       |   32 -------------
  include/asm-m68k/types.h       |   32 -------------
  include/asm-mips/types.h       |   56 ++--------------------
  include/asm-mn10300/types.h    |   33 -------------
  include/asm-parisc/types.h     |   33 -------------
  include/asm-powerpc/types.h    |   48 ++-----------------
  include/asm-s390/types.h       |   48 ++-----------------
  include/asm-sh/types.h         |   34 -------------
  include/asm-sparc/types.h      |   30 ------------
  include/asm-sparc64/types.h    |   30 ------------
  include/asm-v850/types.h       |   32 -------------
  include/asm-x86/types.h        |   38 ---------------
  include/asm-xtensa/types.h     |   33 -------------
  kernel/time.c                  |    8 +--
  25 files changed, 201 insertions(+), 701 deletions(-)

See:

git://git.kernel.org/pub/scm/linux/kernel/git/hpa/linux-2.6-inttypes.git

	-hpa

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n-Apple

[Carlos R. Mafra]

On Fri  4.Apr'08 at 13:41:45 -0700, Pallipadi, Venkatesh wrote:
> [...]
> >>> >I've uploaded the picture where it hangs, it is in the very 
> >>beginning
> >>> >of the boot process:
> >>> >
> >>> >http://www.ift.unesp.br/users/crmafra/dsc04673.jpg
> >>> 
> >>> 
> >>> Can you try the latest git and see whether this still is a problem?
> >>
> >>I've just updated to latest git, but it may take some time for it 
> >>to happen again (the first 3 boots were okay). Last time it happened
> >>with 2.6.25-rc7-00149-gaf8be4e (I checked now). 
> >>
> >>Do you have reasons to believe this issue was fixed since then?
> >
> >Yes. I think the patch here should have fixed the problem....
> >Patch : http://marc.info/?l=linux-kernel&m=120674502201007&w=4
> >
> 
> Hmmmm.... Looking at latest git,
> The above patch is not yet in git. Can you please apply the above patch
> and see whether do you still see the problem.....

I applied Venkatesh's patch from the link above on top of 
v2.6.25-rc8-139-ge315c12, but my laptop hung at the 11th boot with the
same state show here:
http://www.ift.unesp.br/users/crmafra/dsc04673.jpg

I waited 3'30" but the boot process never resumed, so I pressed
the power button.

Any further patches I might try?

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n-Apple

[Rafael J. Wysocki]

On Saturday, 5 of April 2008, Carlos R. Mafra wrote:
> On Fri  4.Apr'08 at 13:41:45 -0700, Pallipadi, Venkatesh wrote:
> 
> > >>> Can you try the latest git and see whether this still is a problem?
> > >>
> > >>I've just updated to latest git, but it may take some time for it 
> > >>to happen again (the first 3 boots were okay). Last time it happened
> > >>with 2.6.25-rc7-00149-gaf8be4e (I checked now). 
> > >>
> > >>Do you have reasons to believe this issue was fixed since then?
> > >
> > >Yes. I think the patch here should have fixed the problem....
> > >Patch : http://marc.info/?l=linux-kernel&m=120674502201007&w=4
> > >
> > 
> > Hmmmm.... Looking at latest git,
> > The above patch is not yet in git. Can you please apply the above patch
> > and see whether do you still see the problem.....
> 
> OK, I will apply it manually and test it.
> 
> For the record: yesterday my laptop hang at boot with v2.6.25-rc8-139-ge315c12
> (without the above patch).

Carlos, please add yourself to the CC list at
http://bugzilla.kernel.org/show_bug.cgi?id=10093

Thanks,
Rafael

Re: 2.6.25-rc8-git2: Reported regressions from 2.6.24

[Rafael J. Wysocki]

On Saturday, 5 of April 2008, Linus Torvalds wrote:
> 
> On Fri, 4 Apr 2008, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10349
> > Subject		: regression: am-utils stopped working in 2.6.25-rc*
> > Submitter	: Meelis Roos <mroos@linux.ee>
> > Date		: 2008-03-28 15:20 (7 days old)
> > References	: http://lkml.org/lkml/2008/3/28/174
> 
> This seems to be a bug in am-utils:
> 
> 	https://bugzilla.am-utils.org/show_bug.cgi?id=612
> 
> and while we try very hard to not break existing binaries that assume some 
> old broken kernel behaviour, things like system setup code that is 
> outright buggy is kind of exempt from that rule. So I think in this case 
> it really is a user-level issue.

OK, closed.

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10346
> > Subject		: Linux 2.6.25-rc6: WARNING: at net/ipv4/tcp_input.c:2510
> > Submitter	: Georgi Chorbadzhiyski <gf@unixsol.org>
> > Date		: 2008-03-27 17:29 (8 days old)
> > References	: http://lkml.org/lkml/2008/3/27/246
> 
> I wouldn't call this a regression. It's a hard-to-trigger warning that is 
> being debugged. 

Dropped from the list.

Thanks,
Rafael

Re: TUNER_TDA8290=y, VIDEO_DEV=n build error

[Adrian Bunk]

On Fri, Apr 04, 2008 at 11:37:40AM +0200, Rafael J. Wysocki wrote:
> On Friday, 4 of April 2008, Adrian Bunk wrote:
> > On Fri, Apr 04, 2008 at 01:20:32AM +0200, Rafael J. Wysocki wrote:
> > > The following report is on the current list of known regressions
> > > from 2.6.24.  Please verify if the issue is still present in the
> > > mainline.
> > 
> > When you asked me just 2 days ago exactly the same question in the 
> > Bugzilla entry I immediately confirmed it's still present.
> > 
> > Was anything wrong with my answer (and the subsequent discussions) that 
> > you now also ask Toralf for confirmation?
> 
> This text is automatically added to the messages sent in replies to the main
> report.
> 
> Well, it probably could be better.  I'm open for suggestions. :-)

First of all you try to get the tracking of all bugs into Bugzilla, and 
now you've sent a batch of emails where the answers will not get into 
Bugzilla automatically.

As an example, for the bug we are talking about the main value of you 
asking me in Bugzilla was not that I confirmed it's still present, the 
main value was that this caused Mauro to make a fix. What would have 
happened if Toralf had answered in an email that the bug is still 
present?

And especially for trickier stuff like suspend/resume problems it might 
also make sense to send the email to all people who might possibly be 
involved with the bug - even if this means putting all email addresses 
from 5 MAINTAINERS entries into one email. It takes a bit more time when 
writing the emails, but my experience was it's worth it.

> Thanks,
> Rafael

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: TUNER_TDA8290=y, VIDEO_DEV=n build error

[Rafael J. Wysocki]

On Sunday, 6 of April 2008, Adrian Bunk wrote:
> On Fri, Apr 04, 2008 at 11:37:40AM +0200, Rafael J. Wysocki wrote:
> > On Friday, 4 of April 2008, Adrian Bunk wrote:
> > > On Fri, Apr 04, 2008 at 01:20:32AM +0200, Rafael J. Wysocki wrote:
> > > > The following report is on the current list of known regressions
> > > > from 2.6.24.  Please verify if the issue is still present in the
> > > > mainline.
> > > 
> > > When you asked me just 2 days ago exactly the same question in the 
> > > Bugzilla entry I immediately confirmed it's still present.
> > > 
> > > Was anything wrong with my answer (and the subsequent discussions) that 
> > > you now also ask Toralf for confirmation?
> > 
> > This text is automatically added to the messages sent in replies to the main
> > report.
> > 
> > Well, it probably could be better.  I'm open for suggestions. :-)
> 
> First of all you try to get the tracking of all bugs into Bugzilla, and 
> now you've sent a batch of emails where the answers will not get into 
> Bugzilla automatically.

So?

> As an example, for the bug we are talking about the main value of you 
> asking me in Bugzilla was not that I confirmed it's still present, the 
> main value was that this caused Mauro to make a fix. What would have 
> happened if Toralf had answered in an email that the bug is still 
> present?

Most probably, I would add a reference to his reply to the bugzilla entry.

> And especially for trickier stuff like suspend/resume problems it might 
> also make sense to send the email to all people who might possibly be 
> involved with the bug - even if this means putting all email addresses 
> from 5 MAINTAINERS entries into one email. It takes a bit more time when 
> writing the emails, but my experience was it's worth it.

Yes, I'm going to do that in the future.

Thanks,
Rafael

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n-Apple

[Carlos R. Mafra]

On Sun  6.Apr'08 at 23:01:50 +0200, Rafael J. Wysocki wrote:
> On Saturday, 5 of April 2008, Carlos R. Mafra wrote:
> > On Fri  4.Apr'08 at 13:41:45 -0700, Pallipadi, Venkatesh wrote:
> > 
> > > >>> Can you try the latest git and see whether this still is a problem?
> > > >>
> > > >>I've just updated to latest git, but it may take some time for it 
> > > >>to happen again (the first 3 boots were okay). Last time it happened
> > > >>with 2.6.25-rc7-00149-gaf8be4e (I checked now). 
> > > >>
> > > >>Do you have reasons to believe this issue was fixed since then?
> > > >
> > > >Yes. I think the patch here should have fixed the problem....
> > > >Patch : http://marc.info/?l=linux-kernel&m=120674502201007&w=4
> > > >
> > > 
> > > Hmmmm.... Looking at latest git,
> > > The above patch is not yet in git. Can you please apply the above patch
> > > and see whether do you still see the problem.....
> > 
> > OK, I will apply it manually and test it.
> > 
> > For the record: yesterday my laptop hang at boot with v2.6.25-rc8-139-ge315c12
> > (without the above patch).
> 
> Carlos, please add yourself to the CC list at
> http://bugzilla.kernel.org/show_bug.cgi?id=10093

Rafael, I added myself to bug 10117 instead of 10093.

I am sorry about this confusion, but the References: to
both bug 10093 and 10117 are this email from Soeren
http://lkml.org/lkml/2008/2/23/263 (and this is how I got
to this thread)

That is the hang which happens in my laptop with latest git.
You can check that by looking at this picture I took while
my laptop was hung http://www.ift.unesp.br/users/crmafra/dsc04673.jpg

However you closed bug 10117, but that is not fixed for me so I am 
going to reopen it if you don't mind.

By the way, thanks for all your effort to track down these regressions.

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n-Apple

[Rafael J. Wysocki]

On Monday, 7 of April 2008, Carlos R. Mafra wrote:
> On Sun  6.Apr'08 at 23:01:50 +0200, Rafael J. Wysocki wrote:
> > On Saturday, 5 of April 2008, Carlos R. Mafra wrote:
> > > On Fri  4.Apr'08 at 13:41:45 -0700, Pallipadi, Venkatesh wrote:
> > > 
> > > > >>> Can you try the latest git and see whether this still is a problem?
> > > > >>
> > > > >>I've just updated to latest git, but it may take some time for it 
> > > > >>to happen again (the first 3 boots were okay). Last time it happened
> > > > >>with 2.6.25-rc7-00149-gaf8be4e (I checked now). 
> > > > >>
> > > > >>Do you have reasons to believe this issue was fixed since then?
> > > > >
> > > > >Yes. I think the patch here should have fixed the problem....
> > > > >Patch : http://marc.info/?l=linux-kernel&m=120674502201007&w=4
> > > > >
> > > > 
> > > > Hmmmm.... Looking at latest git,
> > > > The above patch is not yet in git. Can you please apply the above patch
> > > > and see whether do you still see the problem.....
> > > 
> > > OK, I will apply it manually and test it.
> > > 
> > > For the record: yesterday my laptop hang at boot with v2.6.25-rc8-139-ge315c12
> > > (without the above patch).
> > 
> > Carlos, please add yourself to the CC list at
> > http://bugzilla.kernel.org/show_bug.cgi?id=10093
> 
> Rafael, I added myself to bug 10117 instead of 10093.
> 
> I am sorry about this confusion, but the References: to
> both bug 10093 and 10117 are this email from Soeren
> http://lkml.org/lkml/2008/2/23/263 (and this is how I got
> to this thread)
> 
> That is the hang which happens in my laptop with latest git.
> You can check that by looking at this picture I took while
> my laptop was hung http://www.ift.unesp.br/users/crmafra/dsc04673.jpg
> 
> However you closed bug 10117, but that is not fixed for me so I am 
> going to reopen it if you don't mind.

OK

Well, perhaps we should mark bug #10093 as a duplicate of bug #10117 or
vice versa.  Soeren, are they really different?

> By the way, thanks for all your effort to track down these regressions.

You're welcome. :-)

Thanks,
Rafael

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n-Apple

[Soeren Sonnenburg]

On Mon, 2008-04-07 at 01:20 +0200, Rafael J. Wysocki wrote:
> On Monday, 7 of April 2008, Carlos R. Mafra wrote:
> > On Sun  6.Apr'08 at 23:01:50 +0200, Rafael J. Wysocki wrote:
> > > On Saturday, 5 of April 2008, Carlos R. Mafra wrote:
> > > > On Fri  4.Apr'08 at 13:41:45 -0700, Pallipadi, Venkatesh wrote:
> > > > 
> > > > > >>> Can you try the latest git and see whether this still is a problem?
> > > > > >>
> > > > > >>I've just updated to latest git, but it may take some time for it 
> > > > > >>to happen again (the first 3 boots were okay). Last time it happened
> > > > > >>with 2.6.25-rc7-00149-gaf8be4e (I checked now). 
> > > > > >>
> > > > > >>Do you have reasons to believe this issue was fixed since then?
> > > > > >
> > > > > >Yes. I think the patch here should have fixed the problem....
> > > > > >Patch : http://marc.info/?l=linux-kernel&m=120674502201007&w=4
> > > > > >
> > > > > 
> > > > > Hmmmm.... Looking at latest git,
> > > > > The above patch is not yet in git. Can you please apply the above patch
> > > > > and see whether do you still see the problem.....
> > > > 
> > > > OK, I will apply it manually and test it.
> > > > 
> > > > For the record: yesterday my laptop hang at boot with v2.6.25-rc8-139-ge315c12
> > > > (without the above patch).
> > > 
> > > Carlos, please add yourself to the CC list at
> > > http://bugzilla.kernel.org/show_bug.cgi?id=10093
> > 
> > Rafael, I added myself to bug 10117 instead of 10093.
> > 
> > I am sorry about this confusion, but the References: to
> > both bug 10093 and 10117 are this email from Soeren
> > http://lkml.org/lkml/2008/2/23/263 (and this is how I got
> > to this thread)
> > 
> > That is the hang which happens in my laptop with latest git.
> > You can check that by looking at this picture I took while
> > my laptop was hung http://www.ift.unesp.br/users/crmafra/dsc04673.jpg
> > 
> > However you closed bug 10117, but that is not fixed for me so I am 
> > going to reopen it if you don't mind.
> 
> OK
> 
> Well, perhaps we should mark bug #10093 as a duplicate of bug #10117 or
> vice versa.  Soeren, are they really different?

No idea... All I can tell is that I could not trigger the 
supports 8 throttling states hang anymore since quite a while... It
looks like it got harder to trigger for Carlos too... maybe he could try
to disable CONFIG_CPUIDLE and check if it is at least CPUIDLE related?

Soeren

RE: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n-Apple

[Pallipadi, Venkatesh]

 

>-----Original Message-----
>From: Carlos R. Mafra [mailto:crmafra2@gmail.com] 
>Sent: Sunday, April 06, 2008 1:56 PM
>To: Pallipadi, Venkatesh
>Cc: Ray Lee; Rafael J. Wysocki; Linux Kernel Mailing List; 
>Soeren Sonnenburg
>Subject: Re: 2.6.25-current-git hangs on boot unless 
>CONFIG_CPU_IDLE=n-Apple
>
>On Fri  4.Apr'08 at 13:41:45 -0700, Pallipadi, Venkatesh wrote:
>> [...]
>> >>> >I've uploaded the picture where it hangs, it is in the very 
>> >>beginning
>> >>> >of the boot process:
>> >>> >
>> >>> >http://www.ift.unesp.br/users/crmafra/dsc04673.jpg
>> >>> 
>> >>> 
>> >>> Can you try the latest git and see whether this still is 
>a problem?
>> >>
>> >>I've just updated to latest git, but it may take some time for it 
>> >>to happen again (the first 3 boots were okay). Last time 
>it happened
>> >>with 2.6.25-rc7-00149-gaf8be4e (I checked now). 
>> >>
>> >>Do you have reasons to believe this issue was fixed since then?
>> >
>> >Yes. I think the patch here should have fixed the problem....
>> >Patch : http://marc.info/?l=linux-kernel&m=120674502201007&w=4
>> >
>> 
>> Hmmmm.... Looking at latest git,
>> The above patch is not yet in git. Can you please apply the 
>above patch
>> and see whether do you still see the problem.....
>
>I applied Venkatesh's patch from the link above on top of 
>v2.6.25-rc8-139-ge315c12, but my laptop hung at the 11th boot with the
>same state show here:
>http://www.ift.unesp.br/users/crmafra/dsc04673.jpg
>
>I waited 3'30" but the boot process never resumed, so I pressed
>the power button.
>
>Any further patches I might try?

Carlos,

Hmm. So, we still have some bug hidden in there..
As this is similar to 10117, we should probably track this there.
10093 is a different cpuidle specific bug looks like, as it happens at a
different place while switching between governors.

Can you attach your kernel config, acpidump output and dmesg when kernel
boots ok to that bugzilla.
Also, if you can please try processor.max_cstate=2 boot option and see
whether you still can reproduce the problem. If you can, then try
processor.max_cstate=1. For this boot option to work, you have to have
ACPI_PROCESSOR built into your kernel (and should not be a module).

One more qn. Did you see this problem witj 2.6.24 as well or is this
something that you started seeing only recently?

Thanks,
VEnki

RE: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n-Apple

[Soeren Sonnenburg]

On Sun, 2008-04-06 at 22:31 -0700, Pallipadi, Venkatesh wrote:
[...]
> >I applied Venkatesh's patch from the link above on top of 
> >v2.6.25-rc8-139-ge315c12, but my laptop hung at the 11th boot with the
> >same state show here:
> >http://www.ift.unesp.br/users/crmafra/dsc04673.jpg
> >
> >I waited 3'30" but the boot process never resumed, so I pressed
> >the power button.
> >
> >Any further patches I might try?
> 
> Carlos,
> 
> Hmm. So, we still have some bug hidden in there..
> As this is similar to 10117, we should probably track this there.
> 10093 is a different cpuidle specific bug looks like, as it happens at a
> different place while switching between governors.
> 
> Can you attach your kernel config, acpidump output and dmesg when kernel
> boots ok to that bugzilla.

you could use what I've send as I was seeing this bug too... but maybe
his config (sony vaio?) is well directly point to the problem.

[...]
> One more qn. Did you see this problem witj 2.6.24 as well or is this
> something that you started seeing only recently?

This thing I can answer: yes this is new in 2.6.25 and in there since at
least 23 Feb 2008.

Soeren

Re: 2.6.25-rc6 regression - hang on resume [Bug 10319]

[Romano Giannetti]

On Fri, 2008-04-04 at 08:31 +0200, Soeren Sonnenburg wrote:
> On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:

> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10319
> > Subject		: 2.6.25-rc6 regression - hang on resume
> > Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> > Date		: 2008-03-25 04:44 (10 days old)
> 
> Yes. The machine resumes and display stays black using s2ram -f -p
> (blindly typing reboot etc on keyboard does what is expected). However
> display comes back on 2.6.24.

I can add that on my laptop (toshiba U305, Intel 945GM chipset), s2ram
-f -p -m which used to work ok, in X and console, in 2.6.24 stopped to
work (I tested -rc8, but I think it's like that since a long time).
Machine resumes but the screen stays off after that, although machine is
working (exactly as Soeren said). 

On the other hand, now the plain "echo mem > /sys/power/state" works
perfectly, from X and console. So some of the magic vbe save/restore of
s2ram mess something up for this card. 

Is it a regression for my laptop (is evidently one for Soeren)? On one
side, a "used to work" setup is broken, but it worked with userspace
hacks; now it works with the plain way, and that's clearly better.

I added on Cc: Jesse, to whom I confirmed that Intel suspend/resume was
ok on Feb, 21, [1] and suspend-devel list, because now I do not know
what to do with the whitelist I sent for s2ram for this machine...

Romano 

[1] http://marc.info/?l=linux-kernel&m=120362475121590&w=2

-- 
Sorry for the disclaimer --- ¡I cannot stop it!



--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.

This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation. 

Re: 2.6.25-rc6 regression - hang on resume [Bug 10319]

[Rafael J. Wysocki]

On Monday, 7 of April 2008, Romano Giannetti wrote:
> 
> On Fri, 2008-04-04 at 08:31 +0200, Soeren Sonnenburg wrote:
> > On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
>>
> > Yes. The machine resumes and display stays black using s2ram -f -p
> > (blindly typing reboot etc on keyboard does what is expected). However
> > display comes back on 2.6.24.
> 
> I can add that on my laptop (toshiba U305, Intel 945GM chipset), s2ram
> -f -p -m which used to work ok, in X and console, in 2.6.24 stopped to
> work (I tested -rc8, but I think it's like that since a long time).
> Machine resumes but the screen stays off after that, although machine is
> working (exactly as Soeren said).

Your graphics adapter is different from the Soeren's one and the fact that
"echo mem > /sys/power/state" works for you now is probably a result of the
recent changes in the i915 driver that is now supposed to handle suspend
and resume.

That said, there had to be a change that affected both of your systems
between 2.6.24 and .25-rc8.  Moreover, I'm suspecting ACPI or something
generic in the DRM core.

As far as ACPI is concerned, one commit related to backlight has just been
reverted, so Soeren, can you please test the current Linus' tree?

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n-Apple

[Carlos R. Mafra]

On Sun  6.Apr'08 at 22:31:17 -0700, Pallipadi, Venkatesh wrote:
> >On Fri  4.Apr'08 at 13:41:45 -0700, Pallipadi, Venkatesh wrote:
> >> [...]
> >> >>> >I've uploaded the picture where it hangs, it is in the very 
> >> >>beginning
> >> >>> >of the boot process:
> >> >>> >
> >> >>> >http://www.ift.unesp.br/users/crmafra/dsc04673.jpg
> >> >>> 
> >> >>> 
> >> >>> Can you try the latest git and see whether this still is 
> >a problem?
> >> >>
> >> >>I've just updated to latest git, but it may take some time for it 
> >> >>to happen again (the first 3 boots were okay). Last time 
> >it happened
> >> >>with 2.6.25-rc7-00149-gaf8be4e (I checked now). 
> >> >>
> >> >>Do you have reasons to believe this issue was fixed since then?
> >> >
> >> >Yes. I think the patch here should have fixed the problem....
> >> >Patch : http://marc.info/?l=linux-kernel&m=120674502201007&w=4
> >> >
> >> 
> >> Hmmmm.... Looking at latest git,
> >> The above patch is not yet in git. Can you please apply the 
> >above patch
> >> and see whether do you still see the problem.....
> >
> >I applied Venkatesh's patch from the link above on top of 
> >v2.6.25-rc8-139-ge315c12, but my laptop hung at the 11th boot with the
> >same state show here:
> >http://www.ift.unesp.br/users/crmafra/dsc04673.jpg
> >
> >I waited 3'30" but the boot process never resumed, so I pressed
> >the power button.
> >
> >Any further patches I might try?
> 
> Carlos,
> 
> Hmm. So, we still have some bug hidden in there..
> As this is similar to 10117, we should probably track this there.
> 10093 is a different cpuidle specific bug looks like, as it happens at a
> different place while switching between governors.
> 
> Can you attach your kernel config, acpidump output and dmesg when kernel
> boots ok to that bugzilla.

I uploaded the kernel config and dmesg to the bugzilla a few minutes ago.
I don't have a copy of the acpidump with me right now (laptop is at home,
I am at the physics institute now), but if there is urgency you can look
at the acpidump I've sent here http://lkml.org/lkml/2008/2/11/364

> Also, if you can please try processor.max_cstate=2 boot option and see
> whether you still can reproduce the problem. If you can, then try
> processor.max_cstate=1. For this boot option to work, you have to have
> ACPI_PROCESSOR built into your kernel (and should not be a module).

Ok, I will try them.

> One more qn. Did you see this problem witj 2.6.24 as well or is this
> something that you started seeing only recently?

It started more or less at the same time as 2.6.25-rc1 was released.
It was not there at 2.6.24.

Well, at first I thought it was related to drivers/acpi/thermal.c, because
the next kernel message (in a successfull boot) after the point in which it 
fails is

ACPI: LNXTHERM:01 is registered as thermal_zone0

and there were some changes to that file a bit before -rc1 was out.
For example, commits 3f655ef8 and ce44e19701.

I don't know if this is recommended, but I added Zhang Rui to the Cc: list
to exclude or confirm this possibility.

Re: 2.6.25-rc6 regression - hang on resume [Bug 10319]

[Tino Keitel]

On Mon, Apr 07, 2008 at 11:10:39 +0200, Rafael J. Wysocki wrote:
> On Monday, 7 of April 2008, Romano Giannetti wrote:
> > 
> > On Fri, 2008-04-04 at 08:31 +0200, Soeren Sonnenburg wrote:
> > > On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> >>
> > > Yes. The machine resumes and display stays black using s2ram -f -p
> > > (blindly typing reboot etc on keyboard does what is expected). However
> > > display comes back on 2.6.24.
> > 
> > I can add that on my laptop (toshiba U305, Intel 945GM chipset), s2ram
> > -f -p -m which used to work ok, in X and console, in 2.6.24 stopped to
> > work (I tested -rc8, but I think it's like that since a long time).
> > Machine resumes but the screen stays off after that, although machine is
> > working (exactly as Soeren said).
> 
> Your graphics adapter is different from the Soeren's one and the fact that
> "echo mem > /sys/power/state" works for you now is probably a result of the
> recent changes in the i915 driver that is now supposed to handle suspend
> and resume.

I tried to use vbetool to get my text console back with 2.6.24 after a
suspend to RAM. As a result, I got a text working console, but a
crashing X server sometimes after resume, and the only way to get X
back was to reboot.

With 2.6.25-rc, the text console is fine after resume, due to the
recent changes to the Intel i915 DRM driver. Maybe those people who
used to use vbetool prior to 2.6.25 should check if this is still
needed.

Regards,
Tino

Re: 2.6.25-rc6 regression - hang on resume [Bug 10319]

[Romano Giannetti]

On Tue, 2008-04-08 at 10:58 +0200, Tino Keitel wrote:
> With 2.6.25-rc, the text console is fine after resume, due to the
> recent changes to the Intel i915 DRM driver. Maybe those people who
> used to use vbetool prior to 2.6.25 should check if this is still
> needed.

Yep, the problem is just that: in 2.6.24 vbetool hacks (in my case,
using s2ram -p -m options) was needed to resume graphics. Now they are
not needed anymore, and using them _break_ resume.

So, people with a working suspend-to-ram setup (even using the whitelist
in s2ram, I mean, simply calling s2ram) will discover that 2.6.25 break
their machine. Removing the s2ram package and suspending with
kernel-only machinery will work, but... well, it's not user-friendly.
 
Romano 

-- 
Sorry for the disclaimer --- ¡I cannot stop it!



--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.

This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation. 

Re: 2.6.25-rc6 regression - hang on resume [Bug 10319]

[Soeren Sonnenburg]

On Tue, 2008-04-08 at 14:35 +0200, Romano Giannetti wrote:
> 
> On Tue, 2008-04-08 at 10:58 +0200, Tino Keitel wrote:
> > With 2.6.25-rc, the text console is fine after resume, due to the
> > recent changes to the Intel i915 DRM driver. Maybe those people who
> > used to use vbetool prior to 2.6.25 should check if this is still
> > needed.
> 
> Yep, the problem is just that: in 2.6.24 vbetool hacks (in my case,
> using s2ram -p -m options) was needed to resume graphics. Now they are
> not needed anymore, and using them _break_ resume.
> 
> So, people with a working suspend-to-ram setup (even using the whitelist
> in s2ram, I mean, simply calling s2ram) will discover that 2.6.25 break
> their machine. Removing the s2ram package and suspending with
> kernel-only machinery will work, but... well, it's not user-friendly.

The above holds only if you have an intel graphics adapter. For me
(radeon) it really breaks (as in echo mem >/sys/power/state leaves me a
black screen on resume and manually typing vbetool post or vbetool
vgamode simply hangs the machine).

Soeren

Re: 2.6.25-rc6 regression - hang on resume [Bug 10319]

[Fabio Comolli]

On Tue, Apr 8, 2008 at 2:39 PM, Soeren Sonnenburg <kernel@nn7.de> wrote:
> On Tue, 2008-04-08 at 14:35 +0200, Romano Giannetti wrote:
>  >
>  > On Tue, 2008-04-08 at 10:58 +0200, Tino Keitel wrote:
>  > > With 2.6.25-rc, the text console is fine after resume, due to the
>  > > recent changes to the Intel i915 DRM driver. Maybe those people who
>  > > used to use vbetool prior to 2.6.25 should check if this is still
>  > > needed.
>  >
>  > Yep, the problem is just that: in 2.6.24 vbetool hacks (in my case,
>  > using s2ram -p -m options) was needed to resume graphics. Now they are
>  > not needed anymore, and using them _break_ resume.
>  >
>  > So, people with a working suspend-to-ram setup (even using the whitelist
>  > in s2ram, I mean, simply calling s2ram) will discover that 2.6.25 break
>  > their machine. Removing the s2ram package and suspending with
>  > kernel-only machinery will work, but... well, it's not user-friendly.
>
>  The above holds only if you have an intel graphics adapter. For me
>  (radeon) it really breaks (as in echo mem >/sys/power/state leaves me a
>  black screen on resume and manually typing vbetool post or vbetool
>  vgamode simply hangs the machine).
>

For me (radeon X700) using binary fglrx xorg driver without the binary
kernel module (which does not compile under .25rc for me)
resume-from-ram works using s2ram.

Lightly tested with -rc8.

My laptop is in whitelist as VBE_POST|VBE_SAVE|NOFB .

>  Soeren

Fabio

Re: 2.6.25-rc6 regression - hang on resume [Bug 10319]

[Soeren Sonnenburg]

On Tue, 2008-04-08 at 14:52 +0200, Fabio Comolli wrote:
> On Tue, Apr 8, 2008 at 2:39 PM, Soeren Sonnenburg <kernel@nn7.de> wrote:
> > On Tue, 2008-04-08 at 14:35 +0200, Romano Giannetti wrote:
> >  >
> >  > On Tue, 2008-04-08 at 10:58 +0200, Tino Keitel wrote:
> >  > > With 2.6.25-rc, the text console is fine after resume, due to the
> >  > > recent changes to the Intel i915 DRM driver. Maybe those people who
> >  > > used to use vbetool prior to 2.6.25 should check if this is still
> >  > > needed.
> >  >
> >  > Yep, the problem is just that: in 2.6.24 vbetool hacks (in my case,
> >  > using s2ram -p -m options) was needed to resume graphics. Now they are
> >  > not needed anymore, and using them _break_ resume.
> >  >
> >  > So, people with a working suspend-to-ram setup (even using the whitelist
> >  > in s2ram, I mean, simply calling s2ram) will discover that 2.6.25 break
> >  > their machine. Removing the s2ram package and suspending with
> >  > kernel-only machinery will work, but... well, it's not user-friendly.
> >
> >  The above holds only if you have an intel graphics adapter. For me
> >  (radeon) it really breaks (as in echo mem >/sys/power/state leaves me a
> >  black screen on resume and manually typing vbetool post or vbetool
> >  vgamode simply hangs the machine).
> >
> 
> For me (radeon X700) using binary fglrx xorg driver without the binary
> kernel module (which does not compile under .25rc for me)
> resume-from-ram works using s2ram.
> 
> Lightly tested with -rc8.
> 
> My laptop is in whitelist as VBE_POST|VBE_SAVE|NOFB .

I am talking about console only. X is a completely different issue
especially with fglrx (which will very likely do the re-init).

Soeren

Re: 2.6.25-rc6 regression - hang on resume [Bug 10319]

[Matthew Garrett]

On Tue, Apr 08, 2008 at 02:35:07PM +0200, Romano Giannetti wrote:

> So, people with a working suspend-to-ram setup (even using the whitelist
> in s2ram, I mean, simply calling s2ram) will discover that 2.6.25 break
> their machine. Removing the s2ram package and suspending with
> kernel-only machinery will work, but... well, it's not user-friendly.

The assumption that a static table of VBE-based quirks can be used 
without paying attention to the capabilities of the video driver has 
always been broken, though I'll freely admit that it's all my fault in 
the first place...

-- 
Matthew Garrett | mjg59@srcf.ucam.org

Re: 2.6.25-rc6 regression - hang on resume [Bug 10319]

[Jesse Barnes]

On Tuesday, April 08, 2008 7:41 am Matthew Garrett wrote:
> On Tue, Apr 08, 2008 at 02:35:07PM +0200, Romano Giannetti wrote:
> > So, people with a working suspend-to-ram setup (even using the whitelist
> > in s2ram, I mean, simply calling s2ram) will discover that 2.6.25 break
> > their machine. Removing the s2ram package and suspending with
> > kernel-only machinery will work, but... well, it's not user-friendly.
>
> The assumption that a static table of VBE-based quirks can be used
> without paying attention to the capabilities of the video driver has
> always been broken, though I'll freely admit that it's all my fault in
> the first place...

That said, running vbetool from the console after resuming into it with a new 
i915 driver shouldn't kill your machine...

Romano, you say this was working for you before with the suspend/resume 
enabled i915 driver, right?  So something else must have broken?

You can run the upstream DRM modules against 2.6.24 to insulate yourself from 
anything in 2.6.25 that might have broken things...  That would be a good 
data point.

Jesse

Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n-Apple

[Carlos R. Mafra]

On Sun  6.Apr'08 at 22:31:17 -0700, Pallipadi, Venkatesh wrote:
> >On Fri  4.Apr'08 at 13:41:45 -0700, Pallipadi, Venkatesh wrote:
> >> [...]
> >> >>> >I've uploaded the picture where it hangs, it is in the very 
> >> >>beginning
> >> >>> >of the boot process:
> >> >>> >
> >> >>> >http://www.ift.unesp.br/users/crmafra/dsc04673.jpg
> >> >>> 
> >> >>> 
> >> >>> Can you try the latest git and see whether this still is 
> >a problem?
> >> >>
> >> >>I've just updated to latest git, but it may take some time for it 
> >> >>to happen again (the first 3 boots were okay). Last time 
> >it happened
> >> >>with 2.6.25-rc7-00149-gaf8be4e (I checked now). 
> >> >>
> >> >>Do you have reasons to believe this issue was fixed since then?
> >> >
> >> >Yes. I think the patch here should have fixed the problem....
> >> >Patch : http://marc.info/?l=linux-kernel&m=120674502201007&w=4
> >> >
> >> 
> >> Hmmmm.... Looking at latest git,
> >> The above patch is not yet in git. Can you please apply the 
> >above patch
> >> and see whether do you still see the problem.....
> >
> >I applied Venkatesh's patch from the link above on top of 
> >v2.6.25-rc8-139-ge315c12, but my laptop hung at the 11th boot with the
> >same state show here:
> >http://www.ift.unesp.br/users/crmafra/dsc04673.jpg
> >
> >I waited 3'30" but the boot process never resumed, so I pressed
> >the power button.
> >
> >Any further patches I might try?
> 
> Carlos,
> 
> Hmm. So, we still have some bug hidden in there..
> As this is similar to 10117, we should probably track this there.
> 10093 is a different cpuidle specific bug looks like, as it happens at a
> different place while switching between governors.
> 
> Can you attach your kernel config, acpidump output and dmesg when kernel
> boots ok to that bugzilla.
> Also, if you can please try processor.max_cstate=2 boot option and see
> whether you still can reproduce the problem. If you can, then try
> processor.max_cstate=1. For this boot option to work, you have to have
> ACPI_PROCESSOR built into your kernel (and should not be a module).

I booted the laptop many times yesterday (to test these things):

1) CONFIG_CPUIDLE=n seems to help. It didn't hang after 17 boots

2) processor.max_cstate=2 doesn't help, it hung at the 10th boot

3) processor.max_cstate=1 survived 20 boots without hanging

And when it hung, it always stop at the same point shown in
the picture quoted above.

I hope this will help.

Thanks for taking a look at the problem!

Re: 2.6.25-rc6 regression - hang on resume

[Pavel Machek]

On Fri 2008-04-04 08:31:29, Soeren Sonnenburg wrote:
> On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> > The following report is on the current list of known regressions
> > from 2.6.24.  Please verify if the issue is still present in the
> > mainline.
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10319
> > Subject		: 2.6.25-rc6 regression - hang on resume
> > Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> > Date		: 2008-03-25 04:44 (10 days old)
> 
> Yes. The machine resumes and display stays black using s2ram -f -p
> (blindly typing reboot etc on keyboard does what is expected). However
> display comes back on 2.6.24.

Could you get us any debugging output from s2ram? Or maybe even strace
it in both working and broken case, and comparing them? (You may want
to disable randomization so that results are comparable).

									Pavel

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

Re: 2.6.25-rc6 regression - hang on resume

[Rafael J. Wysocki]

On Friday, 11 of April 2008, Pavel Machek wrote:
> On Fri 2008-04-04 08:31:29, Soeren Sonnenburg wrote:
> > On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> > > The following report is on the current list of known regressions
> > > from 2.6.24.  Please verify if the issue is still present in the
> > > mainline.
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10319
> > > Subject		: 2.6.25-rc6 regression - hang on resume
> > > Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> > > Date		: 2008-03-25 04:44 (10 days old)
> > 
> > Yes. The machine resumes and display stays black using s2ram -f -p
> > (blindly typing reboot etc on keyboard does what is expected). However
> > display comes back on 2.6.24.
> 
> Could you get us any debugging output from s2ram? Or maybe even strace
> it in both working and broken case, and comparing them? (You may want
> to disable randomization so that results are comparable).

Please also test the kernel with the patch from
http://bugzilla.kernel.org/attachment.cgi?id=15736&action=view
applied.

Thanks,
Rafael

Re: 2.6.25-rc6 regression - hang on resume

[Soeren Sonnenburg]

On Fri, 2008-04-11 at 23:04 +0200, Pavel Machek wrote:
> On Fri 2008-04-04 08:31:29, Soeren Sonnenburg wrote:
> > On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> > > The following report is on the current list of known regressions
> > > from 2.6.24.  Please verify if the issue is still present in the
> > > mainline.
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10319
> > > Subject		: 2.6.25-rc6 regression - hang on resume
> > > Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> > > Date		: 2008-03-25 04:44 (10 days old)
> > 
> > Yes. The machine resumes and display stays black using s2ram -f -p
> > (blindly typing reboot etc on keyboard does what is expected). However
> > display comes back on 2.6.24.
> 
> Could you get us any debugging output from s2ram? Or maybe even strace
> it in both working and broken case, and comparing them? (You may want
> to disable randomization so that results are comparable).

I did on 2.6.24

strace -ff s2ram >s2ram24.trace 2>&1

and .25

strace -ff s2ram >s2ram25.trace 2>&1

with the .24 bringing the display back and .25 not. Files are here

http://nn7.de/debugging/s2ram24.trace.bz2
http://nn7.de/debugging/s2ram25.trace.bz2

I have no idea how to 'disable randomization' and also not which
debugging options I should have set ... tell me what things/options you
need to be en/disabled and I redo the experiment.

Soeren

Re: 2.6.25-rc6 regression - hang on resume

[Pavel Machek]

On Sat 2008-04-12 09:27:42, Soeren Sonnenburg wrote:
> On Fri, 2008-04-11 at 23:04 +0200, Pavel Machek wrote:
> > On Fri 2008-04-04 08:31:29, Soeren Sonnenburg wrote:
> > > On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> > > > The following report is on the current list of known regressions
> > > > from 2.6.24.  Please verify if the issue is still present in the
> > > > mainline.
> > > > 
> > > > 
> > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10319
> > > > Subject		: 2.6.25-rc6 regression - hang on resume
> > > > Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> > > > Date		: 2008-03-25 04:44 (10 days old)
> > > 
> > > Yes. The machine resumes and display stays black using s2ram -f -p
> > > (blindly typing reboot etc on keyboard does what is expected). However
> > > display comes back on 2.6.24.
> > 
> > Could you get us any debugging output from s2ram? Or maybe even strace
> > it in both working and broken case, and comparing them? (You may want
> > to disable randomization so that results are comparable).
> 
> I did on 2.6.24
> 
> strace -ff s2ram >s2ram24.trace 2>&1
> 
> and .25
> 
> ???strace -ff s2ram >s2ram25.trace 2>&1
> 
> with the .24 bringing the display back and .25 not. Files are here
> 
> http://nn7.de/debugging/s2ram24.trace.bz2
> ???http://nn7.de/debugging/s2ram25.trace.bz2

Hmm: 

/sys/bus/pci/devices/0000:00:1b.0/irq

contains 21 in one case and 22 in another... as do other
interrupts. Is that expected? Can you post /proc/interrupts for both
versions?

Hmm, big part of trace is:

vm86old(0xb7f76c8c)                     = -1 ENOSYS (Function not
implemented)
vm86old(0xb7f76c8c)                     = -1 ENOSYS (Function not
implemented)

...I wonder why we do it so many times?

And here's the difference. .25 says:

vm86old(0xb809ac8c)                     = -1 ENOSYS (Function not
implemented)
vm86old(0xb809ac8c)                     = -1 ENOSYS (Function not
implemented)
Error: something went wrong performing real mode call
open("/sys/class/graphics",
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|0x80000) = -1 ENOENT (No
such file or directory)
open("/dev/tty", O_RDWR|O_LARGEFILE)    = 6
ioctl(6, KDGKBTYPE, 0xbfae8887)         = 0

...can you perhaps add printf-s to s2ram to find out what changed?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: 2.6.25-rc6 regression - hang on resume

[Soeren Sonnenburg]

On Sun, 2008-04-13 at 10:53 +0200, Pavel Machek wrote:
> On Sat 2008-04-12 09:27:42, Soeren Sonnenburg wrote:
> > On Fri, 2008-04-11 at 23:04 +0200, Pavel Machek wrote:
> > > On Fri 2008-04-04 08:31:29, Soeren Sonnenburg wrote:
> > > > On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> > > > > The following report is on the current list of known regressions
> > > > > from 2.6.24.  Please verify if the issue is still present in the
> > > > > mainline.
> > > > > 
> > > > > 
> > > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10319
> > > > > Subject		: 2.6.25-rc6 regression - hang on resume
> > > > > Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> > > > > Date		: 2008-03-25 04:44 (10 days old)
> > > > 
> > > > Yes. The machine resumes and display stays black using s2ram -f -p
> > > > (blindly typing reboot etc on keyboard does what is expected). However
> > > > display comes back on 2.6.24.
> > > 
> > > Could you get us any debugging output from s2ram? Or maybe even strace
> > > it in both working and broken case, and comparing them? (You may want
> > > to disable randomization so that results are comparable).
> > 
> > I did on 2.6.24
> > 
> > strace -ff s2ram >s2ram24.trace 2>&1
> > 
> > and .25
> > 
> > ???strace -ff s2ram >s2ram25.trace 2>&1
> > 
> > with the .24 bringing the display back and .25 not. Files are here
> > 
> > http://nn7.de/debugging/s2ram24.trace.bz2
> > ???http://nn7.de/debugging/s2ram25.trace.bz2
> 
> Hmm: 
> 
> /sys/bus/pci/devices/0000:00:1b.0/irq
> 
> contains 21 in one case and 22 in another... as do other
> interrupts. Is that expected? Can you post /proc/interrupts for both
> versions?

It might be that configs are slightly different - if you think this
gives a clue I will post them, but your discovery below looks promising:

> Hmm, big part of trace is:
> 
> vm86old(0xb7f76c8c)                     = -1 ENOSYS (Function not
> implemented)
> vm86old(0xb7f76c8c)                     = -1 ENOSYS (Function not
> implemented)
> 
> ...I wonder why we do it so many times?
> 
> And here's the difference. .25 says:
> 
> vm86old(0xb809ac8c)                     = -1 ENOSYS (Function not
> implemented)
> vm86old(0xb809ac8c)                     = -1 ENOSYS (Function not
> implemented)
> Error: something went wrong performing real mode call
> open("/sys/class/graphics",
> O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|0x80000) = -1 ENOENT (No
> such file or directory)
> open("/dev/tty", O_RDWR|O_LARGEFILE)    = 6
> ioctl(6, KDGKBTYPE, 0xbfae8887)         = 0
> 
> ...can you perhaps add printf-s to s2ram to find out what changed?

OK, I searched for "something went wrong performing real mode call" in
the s2ram source and found this function:

int do_real_post(unsigned pci_device)
{
    int error = 0;
    struct LRMI_regs r;
    memset(&r, 0, sizeof(r));

    /* Several machines seem to want the device that they're POSTing in
       here */
    r.eax = pci_device;

    /* 0xc000 is the video option ROM.  The init code for each
       option ROM is at 0x0003 - so jump to c000:0003 and start running
*/
    r.cs = 0xc000;
    r.ip = 0x0003;

    /* This is all heavily cargo culted but seems to work */
    r.edx = 0x80;
    r.ds = 0x0040;

    if (!LRMI_call(&r)) {
        fprintf(stderr,
            "Error: something went wrong performing real mode call\n");
        error = 1;
    }

    return error;
}

which is obviously called from

int do_post(void)
{
    struct pci_dev *p;
    unsigned int c;
    unsigned int pci_id;
    int error;

    pci_scan_bus(pacc);

    for (p = pacc->devices; p; p = p->next) {
        c = pci_read_word(p, PCI_CLASS_DEVICE);
        if (c == 0x300) {
            pci_id =
                (p->bus << 8) + (p->dev << 3) +
                (p->func & 0x7);
            error = do_real_post(pci_id);
            if (error != 0) {
                return error;
            }
        }
    }
    return 0;
}

so either the graphics adapter is somehow not ready yet or a wrong
address is used for posting?

Do you already now have an idea? Or which things should I print out?

Soeren

Re: 2.6.25-rc6 regression - hang on resume

[Rafael J. Wysocki]

On Sunday, 13 of April 2008, Pavel Machek wrote:
> On Sat 2008-04-12 09:27:42, Soeren Sonnenburg wrote:
> > On Fri, 2008-04-11 at 23:04 +0200, Pavel Machek wrote:
> > > On Fri 2008-04-04 08:31:29, Soeren Sonnenburg wrote:
> > > > On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> > > > > The following report is on the current list of known regressions
> > > > > from 2.6.24.  Please verify if the issue is still present in the
> > > > > mainline.
> > > > > 
> > > > > 
> > > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10319
> > > > > Subject		: 2.6.25-rc6 regression - hang on resume
> > > > > Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> > > > > Date		: 2008-03-25 04:44 (10 days old)
> > > > 
> > > > Yes. The machine resumes and display stays black using s2ram -f -p
> > > > (blindly typing reboot etc on keyboard does what is expected). However
> > > > display comes back on 2.6.24.
> > > 
> > > Could you get us any debugging output from s2ram? Or maybe even strace
> > > it in both working and broken case, and comparing them? (You may want
> > > to disable randomization so that results are comparable).
> > 
> > I did on 2.6.24
> > 
> > strace -ff s2ram >s2ram24.trace 2>&1
> > 
> > and .25
> > 
> > ???strace -ff s2ram >s2ram25.trace 2>&1
> > 
> > with the .24 bringing the display back and .25 not. Files are here
> > 
> > http://nn7.de/debugging/s2ram24.trace.bz2
> > ???http://nn7.de/debugging/s2ram25.trace.bz2
> 
> Hmm: 
> 
> /sys/bus/pci/devices/0000:00:1b.0/irq
> 
> contains 21 in one case and 22 in another... as do other
> interrupts. Is that expected? Can you post /proc/interrupts for both
> versions?
> 
> Hmm, big part of trace is:
> 
> vm86old(0xb7f76c8c)                     = -1 ENOSYS (Function not
> implemented)
> vm86old(0xb7f76c8c)                     = -1 ENOSYS (Function not
> implemented)
> 
> ...I wonder why we do it so many times?
> 
> And here's the difference. .25 says:
> 
> vm86old(0xb809ac8c)                     = -1 ENOSYS (Function not
> implemented)
> vm86old(0xb809ac8c)                     = -1 ENOSYS (Function not
> implemented)
> Error: something went wrong performing real mode call
> open("/sys/class/graphics",
> O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|0x80000) = -1 ENOENT (No
> such file or directory)
> open("/dev/tty", O_RDWR|O_LARGEFILE)    = 6
> ioctl(6, KDGKBTYPE, 0xbfae8887)         = 0
> 
> ...can you perhaps add printf-s to s2ram to find out what changed?

Well, that looks suspiciously similar to
http://bugzilla.kernel.org/show_bug.cgi?id=10155 .

Thanks,
Rafael

Re: 2.6.25-rc6 regression - hang on resume

[Soeren Sonnenburg]

On Sun, 2008-04-13 at 15:53 +0200, Rafael J. Wysocki wrote:
> On Sunday, 13 of April 2008, Pavel Machek wrote:
> > On Sat 2008-04-12 09:27:42, Soeren Sonnenburg wrote:
> > > On Fri, 2008-04-11 at 23:04 +0200, Pavel Machek wrote:
> > > > On Fri 2008-04-04 08:31:29, Soeren Sonnenburg wrote:
> > > > > On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> > > > > > The following report is on the current list of known regressions
> > > > > > from 2.6.24.  Please verify if the issue is still present in the
> > > > > > mainline.
> > > > > > 
> > > > > > 
> > > > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10319
> > > > > > Subject		: 2.6.25-rc6 regression - hang on resume
> > > > > > Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> > > > > > Date		: 2008-03-25 04:44 (10 days old)
> > > > > 
> > > > > Yes. The machine resumes and display stays black using s2ram -f -p
> > > > > (blindly typing reboot etc on keyboard does what is expected). However
> > > > > display comes back on 2.6.24.
> > > > 
> > > > Could you get us any debugging output from s2ram? Or maybe even strace
> > > > it in both working and broken case, and comparing them? (You may want
> > > > to disable randomization so that results are comparable).
> > > 
> > > I did on 2.6.24
> > > 
> > > strace -ff s2ram >s2ram24.trace 2>&1
> > > 
> > > and .25
> > > 
> > > ???strace -ff s2ram >s2ram25.trace 2>&1
> > > 
> > > with the .24 bringing the display back and .25 not. Files are here
> > > 
> > > http://nn7.de/debugging/s2ram24.trace.bz2
> > > ???http://nn7.de/debugging/s2ram25.trace.bz2
> > 
> > Hmm: 
> > 
> > /sys/bus/pci/devices/0000:00:1b.0/irq
> > 
> > contains 21 in one case and 22 in another... as do other
> > interrupts. Is that expected? Can you post /proc/interrupts for both
> > versions?
> > 
> > Hmm, big part of trace is:
> > 
> > vm86old(0xb7f76c8c)                     = -1 ENOSYS (Function not
> > implemented)
> > vm86old(0xb7f76c8c)                     = -1 ENOSYS (Function not
> > implemented)
> > 
> > ...I wonder why we do it so many times?
> > 
> > And here's the difference. .25 says:
> > 
> > vm86old(0xb809ac8c)                     = -1 ENOSYS (Function not
> > implemented)
> > vm86old(0xb809ac8c)                     = -1 ENOSYS (Function not
> > implemented)
> > Error: something went wrong performing real mode call
> > open("/sys/class/graphics",
> > O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|0x80000) = -1 ENOENT (No
> > such file or directory)
> > open("/dev/tty", O_RDWR|O_LARGEFILE)    = 6
> > ioctl(6, KDGKBTYPE, 0xbfae8887)         = 0
> > 
> > ...can you perhaps add printf-s to s2ram to find out what changed?
> 
> Well, that looks suspiciously similar to
> http://bugzilla.kernel.org/show_bug.cgi?id=10155 .

Hmmhh the only difference is that I don't have a core 2 duo but only a
core 1 duo but hmmmhh the flag down there looks like it does nx, or
should I see something like nx enabled in dmesg?

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 14
model name	: Genuine Intel(R) CPU            1600  @ 2.16GHz
stepping	: 8
cpu MHz		: 1000.000
cache size	: 2048 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 6
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc bts
pni monitor vmx est tm2 xtpr
bogomips	: 4333.82
clflush size	: 64


Anyway I will try noexec=off ...

Soeren

Re: 2.6.25-rc6 regression - hang on resume

[Soeren Sonnenburg]

On Sun, 2008-04-13 at 15:53 +0200, Rafael J. Wysocki wrote:
> On Sunday, 13 of April 2008, Pavel Machek wrote:
> > On Sat 2008-04-12 09:27:42, Soeren Sonnenburg wrote:
> > > On Fri, 2008-04-11 at 23:04 +0200, Pavel Machek wrote:
> > > > On Fri 2008-04-04 08:31:29, Soeren Sonnenburg wrote:
> > > > > On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> > > > > > The following report is on the current list of known regressions
> > > > > > from 2.6.24.  Please verify if the issue is still present in the
> > > > > > mainline.
> > > > > > 
> > > > > > 
> > > > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10319
> > > > > > Subject		: 2.6.25-rc6 regression - hang on resume
> > > > > > Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> > > > > > Date		: 2008-03-25 04:44 (10 days old)
> > > > > 
> > > > > Yes. The machine resumes and display stays black using s2ram -f -p
> > > > > (blindly typing reboot etc on keyboard does what is expected). However
> > > > > display comes back on 2.6.24.
> > > > 
> > > > Could you get us any debugging output from s2ram? Or maybe even strace
> > > > it in both working and broken case, and comparing them? (You may want
> > > > to disable randomization so that results are comparable).
> > > 
> > > I did on 2.6.24
> > > 
> > > strace -ff s2ram >s2ram24.trace 2>&1
> > > 
> > > and .25
> > > 
> > > ???strace -ff s2ram >s2ram25.trace 2>&1
> > > 
> > > with the .24 bringing the display back and .25 not. Files are here
> > > 
> > > http://nn7.de/debugging/s2ram24.trace.bz2
> > > ???http://nn7.de/debugging/s2ram25.trace.bz2
> > 
> > Hmm: 
> > 
> > /sys/bus/pci/devices/0000:00:1b.0/irq
> > 
> > contains 21 in one case and 22 in another... as do other
> > interrupts. Is that expected? Can you post /proc/interrupts for both
> > versions?
> > 
> > Hmm, big part of trace is:
> > 
> > vm86old(0xb7f76c8c)                     = -1 ENOSYS (Function not
> > implemented)
> > vm86old(0xb7f76c8c)                     = -1 ENOSYS (Function not
> > implemented)
> > 
> > ...I wonder why we do it so many times?
> > 
> > And here's the difference. .25 says:
> > 
> > vm86old(0xb809ac8c)                     = -1 ENOSYS (Function not
> > implemented)
> > vm86old(0xb809ac8c)                     = -1 ENOSYS (Function not
> > implemented)
> > Error: something went wrong performing real mode call
> > open("/sys/class/graphics",
> > O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|0x80000) = -1 ENOENT (No
> > such file or directory)
> > open("/dev/tty", O_RDWR|O_LARGEFILE)    = 6
> > ioctl(6, KDGKBTYPE, 0xbfae8887)         = 0
> > 
> > ...can you perhaps add printf-s to s2ram to find out what changed?
> 
> Well, that looks suspiciously similar to
> http://bugzilla.kernel.org/show_bug.cgi?id=10155 .

OK I tried noexec=off now... same error in s2ram ... so I guess my CPU
does not support NX ...

Soeren

Re: 2.6.25-rc6 regression - hang on resume

[Rafael J. Wysocki]

On Sunday, 13 of April 2008, Soeren Sonnenburg wrote:
> On Sun, 2008-04-13 at 15:53 +0200, Rafael J. Wysocki wrote:
> > On Sunday, 13 of April 2008, Pavel Machek wrote:
> > > On Sat 2008-04-12 09:27:42, Soeren Sonnenburg wrote:
> > > > On Fri, 2008-04-11 at 23:04 +0200, Pavel Machek wrote:
> > > > > On Fri 2008-04-04 08:31:29, Soeren Sonnenburg wrote:
> > > > > > On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> > > > > > > The following report is on the current list of known regressions
> > > > > > > from 2.6.24.  Please verify if the issue is still present in the
> > > > > > > mainline.
> > > > > > > 
> > > > > > > 
> > > > > > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10319
> > > > > > > Subject		: 2.6.25-rc6 regression - hang on resume
> > > > > > > Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> > > > > > > Date		: 2008-03-25 04:44 (10 days old)
> > > > > > 
> > > > > > Yes. The machine resumes and display stays black using s2ram -f -p
> > > > > > (blindly typing reboot etc on keyboard does what is expected). However
> > > > > > display comes back on 2.6.24.
> > > > > 
> > > > > Could you get us any debugging output from s2ram? Or maybe even strace
> > > > > it in both working and broken case, and comparing them? (You may want
> > > > > to disable randomization so that results are comparable).
> > > > 
> > > > I did on 2.6.24
> > > > 
> > > > strace -ff s2ram >s2ram24.trace 2>&1
> > > > 
> > > > and .25
> > > > 
> > > > ???strace -ff s2ram >s2ram25.trace 2>&1
> > > > 
> > > > with the .24 bringing the display back and .25 not. Files are here
> > > > 
> > > > http://nn7.de/debugging/s2ram24.trace.bz2
> > > > ???http://nn7.de/debugging/s2ram25.trace.bz2
> > > 
> > > Hmm: 
> > > 
> > > /sys/bus/pci/devices/0000:00:1b.0/irq
> > > 
> > > contains 21 in one case and 22 in another... as do other
> > > interrupts. Is that expected? Can you post /proc/interrupts for both
> > > versions?
> > > 
> > > Hmm, big part of trace is:
> > > 
> > > vm86old(0xb7f76c8c)                     = -1 ENOSYS (Function not
> > > implemented)
> > > vm86old(0xb7f76c8c)                     = -1 ENOSYS (Function not
> > > implemented)
> > > 
> > > ...I wonder why we do it so many times?
> > > 
> > > And here's the difference. .25 says:
> > > 
> > > vm86old(0xb809ac8c)                     = -1 ENOSYS (Function not
> > > implemented)
> > > vm86old(0xb809ac8c)                     = -1 ENOSYS (Function not
> > > implemented)
> > > Error: something went wrong performing real mode call
> > > open("/sys/class/graphics",
> > > O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|0x80000) = -1 ENOENT (No
> > > such file or directory)
> > > open("/dev/tty", O_RDWR|O_LARGEFILE)    = 6
> > > ioctl(6, KDGKBTYPE, 0xbfae8887)         = 0
> > > 
> > > ...can you perhaps add printf-s to s2ram to find out what changed?
> > 
> > Well, that looks suspiciously similar to
> > http://bugzilla.kernel.org/show_bug.cgi?id=10155 .
> 
> OK I tried noexec=off now... same error in s2ram ... so I guess my CPU
> does not support NX ...

s2ram segfaulted in that bug, but your one desn't.  Still, we could have done
another thing that prevents s2ram from doing its job on your system.

Thanks,
Rafael

Re: 2.6.25-rc6 regression - hang on resume

[Pavel Machek]

Hi!

> > /sys/bus/pci/devices/0000:00:1b.0/irq
> > 
> > contains 21 in one case and 22 in another... as do other
> > interrupts. Is that expected? Can you post /proc/interrupts for both
> > versions?
> 
> It might be that configs are slightly different - if you think this
> gives a clue I will post them, but your discovery below looks
> promising:

Yep... any chance to do git bisect to see where it broke?

> > Error: something went wrong performing real mode call
> > open("/sys/class/graphics",
> > O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|0x80000) = -1 ENOENT (No
> > such file or directory)
> > open("/dev/tty", O_RDWR|O_LARGEFILE)    = 6
> > ioctl(6, KDGKBTYPE, 0xbfae8887)         = 0
> > 
> > ...can you perhaps add printf-s to s2ram to find out what changed?
> 
> OK, I searched for ???"something went wrong performing real mode call" in
> the s2ram source and found this function:
> 
> int do_real_post(unsigned pci_device)
> {
>     int error = 0;
>     struct LRMI_regs r;
>     memset(&r, 0, sizeof(r));
> 
>     /* Several machines seem to want the device that they're POSTing in
>        here */
>     r.eax = pci_device;
> 
>     /* 0xc000 is the video option ROM.  The init code for each
>        option ROM is at 0x0003 - so jump to c000:0003 and start running
> */
>     r.cs = 0xc000;
>     r.ip = 0x0003;
> 
>     /* This is all heavily cargo culted but seems to work */
>     r.edx = 0x80;
>     r.ds = 0x0040;
> 
>     if (!LRMI_call(&r)) {
>         fprintf(stderr,
>             "Error: something went wrong performing real mode call\n");
>         error = 1;

Sweet, so the problem is inside X86EMU_exec(), right? ...and that's
bytecode interpretter. You could add printfs() all over it, to see
where the execution differs.

> so either the graphics adapter is somehow not ready yet or a wrong
> address is used for posting?

Or something goes wrong in the interpretter...

> Do you already now have an idea? Or which things should I print out?

It starts to look like git bisect is the easier way to get some
results...
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: [Suspend-devel] 2.6.25-rc6 regression - hang on resume [Bug 10319]

[Stefan Seyfried]

Romano Giannetti schrieb:
> 
> On Fri, 2008-04-04 at 08:31 +0200, Soeren Sonnenburg wrote:
>> On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> 
>>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10319
>>> Subject		: 2.6.25-rc6 regression - hang on resume
>>> Submitter	: Soeren Sonnenburg <kernel@nn7.de>
>>> Date		: 2008-03-25 04:44 (10 days old)
>> Yes. The machine resumes and display stays black using s2ram -f -p
>> (blindly typing reboot etc on keyboard does what is expected). However
>> display comes back on 2.6.24.
> 
> I can add that on my laptop (toshiba U305, Intel 945GM chipset), s2ram
> -f -p -m which used to work ok, in X and console, in 2.6.24 stopped to
> work (I tested -rc8, but I think it's like that since a long time).
> Machine resumes but the screen stays off after that, although machine is
> working (exactly as Soeren said). 

can you try if this patch to libx86 (make sure it gets installed and used...)
fixes the problem?

Index: libx86-0.99/x86-common.c
===================================================================
--- libx86-0.99.orig/x86-common.c
+++ libx86-0.99/x86-common.c
@@ -232,7 +232,7 @@ int LRMI_common_init(void)
 	}

 	m = mmap((void *)0xa0000, 0x100000 - 0xa0000,
-	 PROT_READ | PROT_WRITE,
+	 PROT_READ | PROT_WRITE | PROT_EXEC,
 	 MAP_FIXED | MAP_SHARED, fd_mem, 0xa0000);

 	if (m == (void *)-1) {

> On the other hand, now the plain "echo mem > /sys/power/state" works
> perfectly, from X and console. So some of the magic vbe save/restore of
> s2ram mess something up for this card. 

Especially the userspace stuff (VBE_*) should not interfere with the restoring
now done inside the kernel drivers.

> Is it a regression for my laptop (is evidently one for Soeren)? On one
> side, a "used to work" setup is broken, but it worked with userspace
> hacks; now it works with the plain way, and that's clearly better.
-- 
Stefan Seyfried
R&D Team Mobile Devices            |              "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."

This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

Re: [Suspend-devel] 2.6.25-rc6 regression - hang on resume [Bug 10319]

[Soeren Sonnenburg]

On Thu, 2008-04-17 at 20:20 +0200, Stefan Seyfried wrote:
> Romano Giannetti schrieb:
> > 
> > On Fri, 2008-04-04 at 08:31 +0200, Soeren Sonnenburg wrote:
> >> On Fri, 2008-04-04 at 01:22 +0200, Rafael J. Wysocki wrote:
> > 
> >>> Bug-Entry   : http://bugzilla.kernel.org/show_bug.cgi?id=10319
> >>> Subject             : 2.6.25-rc6 regression - hang on resume
> >>> Submitter   : Soeren Sonnenburg <kernel@nn7.de>
> >>> Date                : 2008-03-25 04:44 (10 days old)
> >> Yes. The machine resumes and display stays black using s2ram -f -p
> >> (blindly typing reboot etc on keyboard does what is expected).
> However
> >> display comes back on 2.6.24.
> > 
> > I can add that on my laptop (toshiba U305, Intel 945GM chipset),
> s2ram
> > -f -p -m which used to work ok, in X and console, in 2.6.24 stopped
> to
> > work (I tested -rc8, but I think it's like that since a long time).
> > Machine resumes but the screen stays off after that, although
> machine is
> > working (exactly as Soeren said). 
> 
> can you try if this patch to libx86 (make sure it gets installed and
> used...)
> fixes the problem?

for me it won't (core 1 duo), not clear whether his toshiba is a core 2
duo though supporting that flag...

anyway I tried again with the patch and 2.6.25 and same thing, display
stays black on console. then i s2ram'd again and - the display came
back!!

all my further attempts never made it come back... however from inside X
it works now (radeonhd...).

> Index: libx86-0.99/x86-common.c
> ===================================================================
> --- libx86-0.99.orig/x86-common.c
> +++ libx86-0.99/x86-common.c
> @@ -232,7 +232,7 @@ int LRMI_common_init(void)
>         }
> 
>         m = mmap((void *)0xa0000, 0x100000 - 0xa0000,
> -        PROT_READ | PROT_WRITE,
> +        PROT_READ | PROT_WRITE | PROT_EXEC,
>          MAP_FIXED | MAP_SHARED, fd_mem, 0xa0000);
> 
>         if (m == (void *)-1) {
> 
> > On the other hand, now the plain "echo mem > /sys/power/state" works
> > perfectly, from X and console. So some of the magic vbe save/restore
> of
> > s2ram mess something up for this card. 
> 
> Especially the userspace stuff (VBE_*) should not interfere with the
> restoring
> now done inside the kernel drivers.

Hmmhh maybe when the radeon(hd) fb driver enters the kernel it will work
for me nicely again...

Soeren

Re: [Suspend-devel] 2.6.25-rc6 regression - hang on resume [Bug 10319]

[Romano Giannetti]

On Thu, 2008-04-17 at 20:20 +0200, Stefan Seyfried wrote:

> can you try if this patch to libx86 (make sure it gets installed and used...)
> fixes the problem?
> 
> Index: libx86-0.99/x86-common.c

Sorry to be a bit though, but _what_ I'm supposed to patch? It's in
s2ram sources? Thanks!

Romano

-- 
Sorry for the disclaimer --- ¡I cannot stop it!



--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.

This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation. 

Re: [Suspend-devel] 2.6.25-rc6 regression - hang on resume [Bug 10319]

[Soeren Sonnenburg]

On Fri, 2008-04-18 at 09:34 +0200, Romano Giannetti wrote:
> 
> On Thu, 2008-04-17 at 20:20 +0200, Stefan Seyfried wrote:
> 
> > can you try if this patch to libx86 (make sure it gets installed and used...)
> > fixes the problem?
> > 
> > Index: libx86-0.99/x86-common.c
> 
> Sorry to be a bit though, but _what_ I'm supposed to patch? It's in
> s2ram sources? Thanks!

Patch the sources of libx86... (s2ram makes use of that lib to do the
POSTing)

Soeren

Re: regression: am-utils stopped working in 2.6.25-rc*

[Benny Halevy]

On Apr. 02, 2008, 1:14 +0300, Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> On Tue, 2008-04-01 at 17:07 -0400, J. Bruce Fields wrote:
>> On Fri, Mar 28, 2008 at 03:20:18PM +0200, Meelis Roos wrote:
>>> Current 2.6.25-rc* kernels have broken am-utils (NFS-based automounter) 
>>> support. No error messages, just "no such file or directory" when trying 
>>> to enter /net/anotherhostname. Just tried 2.6.24 and that worked fine. 
>>> am-utils is the latest in Debian unstable, 6.1.5-9.
>>>
>>> Earliest 2.6.25-rc currently tested was 2.6.25-rc3+git as of 20080304. 
>>> This version reports 
>>> Invalid hostname "pid3477@koiott:/net" in NFS lock request
>>> into dmesg and am-utils does not work.
>>>
>>> 2.6.25-rc4+git as of 20080310 and later ones do not show this message 
>>> but am-utils does still not work.
>>>
>>> Will try bisecting it further.
>> Have you figured out anything more?  Can strace show exactly which
>> system call is  failing?
> 
> See the bugzilla report:
>   http://bugzilla.kernel.org/show_bug.cgi?id=10349

FWIW, I've already opened this bug on am-utils's bugzilla:
https://bugzilla.am-utils.org/show_bug.cgi?id=612

I updated it with the info on this message.

Benny

> 
> I'm still waiting to hear back from Meelis, but to me this looks like an
> am-utils bug.
> 
> AFAICS, am-utils advertises a binary NFS mount structure version of '6',
> to the mount() syscall, but internally they only initialise the
> equivalent of a version '4' structure.
> When
>      http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=f9c3a3802119a2d30f3e4a69aef30a81e09d0209
> was merged, then this failure to initialise the selinux 'context' field
> causes mount() to return an EINVAL.
> 
> Cheers
>   Trond
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: regression: am-utils stopped working in 2.6.25-rc*

[Trond Myklebust]

On Tue, 2008-04-01 at 17:07 -0400, J. Bruce Fields wrote:
> On Fri, Mar 28, 2008 at 03:20:18PM +0200, Meelis Roos wrote:
> > Current 2.6.25-rc* kernels have broken am-utils (NFS-based automounter) 
> > support. No error messages, just "no such file or directory" when trying 
> > to enter /net/anotherhostname. Just tried 2.6.24 and that worked fine. 
> > am-utils is the latest in Debian unstable, 6.1.5-9.
> > 
> > Earliest 2.6.25-rc currently tested was 2.6.25-rc3+git as of 20080304. 
> > This version reports 
> > Invalid hostname "pid3477@koiott:/net" in NFS lock request
> > into dmesg and am-utils does not work.
> > 
> > 2.6.25-rc4+git as of 20080310 and later ones do not show this message 
> > but am-utils does still not work.
> > 
> > Will try bisecting it further.
> 
> Have you figured out anything more?  Can strace show exactly which
> system call is  failing?

See the bugzilla report:
  http://bugzilla.kernel.org/show_bug.cgi?id=10349

I'm still waiting to hear back from Meelis, but to me this looks like an
am-utils bug.

AFAICS, am-utils advertises a binary NFS mount structure version of '6',
to the mount() syscall, but internally they only initialise the
equivalent of a version '4' structure.
When
     http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=f9c3a3802119a2d30f3e4a69aef30a81e09d0209
was merged, then this failure to initialise the selinux 'context' field
causes mount() to return an EINVAL.

Cheers
  Trond

Re: regression: am-utils stopped working in 2.6.25-rc*

[J. Bruce Fields]

On Fri, Mar 28, 2008 at 03:20:18PM +0200, Meelis Roos wrote:
> Current 2.6.25-rc* kernels have broken am-utils (NFS-based automounter) 
> support. No error messages, just "no such file or directory" when trying 
> to enter /net/anotherhostname. Just tried 2.6.24 and that worked fine. 
> am-utils is the latest in Debian unstable, 6.1.5-9.
> 
> Earliest 2.6.25-rc currently tested was 2.6.25-rc3+git as of 20080304. 
> This version reports 
> Invalid hostname "pid3477@koiott:/net" in NFS lock request
> into dmesg and am-utils does not work.
> 
> 2.6.25-rc4+git as of 20080310 and later ones do not show this message 
> but am-utils does still not work.
> 
> Will try bisecting it further.

Have you figured out anything more?  Can strace show exactly which
system call is  failing?

--b.

regression: am-utils stopped working in 2.6.25-rc*

[Meelis Roos]

Current 2.6.25-rc* kernels have broken am-utils (NFS-based automounter) 
support. No error messages, just "no such file or directory" when trying 
to enter /net/anotherhostname. Just tried 2.6.24 and that worked fine. 
am-utils is the latest in Debian unstable, 6.1.5-9.

Earliest 2.6.25-rc currently tested was 2.6.25-rc3+git as of 20080304. 
This version reports 
Invalid hostname "pid3477@koiott:/net" in NFS lock request
into dmesg and am-utils does not work.

2.6.25-rc4+git as of 20080310 and later ones do not show this message 
but am-utils does still not work.

Will try bisecting it further.

amd64 host, .config below:

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.25-rc7
# Fri Mar 28 11:28:19 2008
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
# CONFIG_GENERIC_LOCKBREAK is not set
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_FAST_CMPXCHG_LOCAL=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
# CONFIG_GENERIC_GPIO is not set
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_AOUT=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_64_SMP=y
CONFIG_X86_TRAMPOLINE=y
# CONFIG_KTIME_SCALAR is not set
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_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=16
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_CGROUP_NS=y
CONFIG_CPUSETS=y
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_RT_GROUP_SCHED=y
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
# CONFIG_CGROUP_CPUACCT is not set
CONFIG_RESOURCE_COUNTERS=y
# CONFIG_CGROUP_MEM_RES_CTLR is not set
# CONFIG_SYSFS_DEPRECATED_V2 is not set
CONFIG_PROC_PID_CPUSET=y
CONFIG_RELAY=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
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_COMPAT_BRK=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_PROFILING=y
# CONFIG_MARKERS is not set
CONFIG_OPROFILE=m
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_BLK_DEV_IO_TRACE=y
# CONFIG_BLK_DEV_BSG is not set
CONFIG_BLOCK_COMPAT=y

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

#
# 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_RDC321X is not set
# CONFIG_X86_VSMP is not set
# CONFIG_PARAVIRT_GUEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
CONFIG_MK8=y
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_L1_CACHE_BYTES=64
CONFIG_X86_INTERNODE_CACHE_BYTES=64
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_GART_IOMMU=y
# CONFIG_CALGARY_IOMMU is not set
CONFIG_IOMMU_HELPER=y
CONFIG_SWIOTLB=y
CONFIG_NR_CPUS=32
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
# CONFIG_PREEMPT_RCU is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
CONFIG_X86_MCE_AMD=y
# CONFIG_I8K is not set
CONFIG_MICROCODE=m
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
# CONFIG_NUMA is not set
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
# CONFIG_DISCONTIGMEM_MANUAL is not set
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_HAVE_MEMORY_PRESENT=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_VMEMMAP=y

#
# Memory hotplug is currently incompatible with Software Suspend
#
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_MTRR=y
# CONFIG_EFI is not set
# CONFIG_SECCOMP is not set
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_SCHED_HRTICK=y
CONFIG_KEXEC=y
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x200000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x200000
CONFIG_HOTPLUG_CPU=y
CONFIG_COMPAT_VDSO=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management options
#
CONFIG_ARCH_HIBERNATION_HEADER=y
CONFIG_PM=y
# CONFIG_PM_LEGACY is not set
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_DOCK=y
# CONFIG_ACPI_BAY is not set
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_WMI=m
CONFIG_ACPI_ASUS=m
CONFIG_ACPI_TOSHIBA=m
# CONFIG_ACPI_CUSTOM_DSDT 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=m

#
# 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 is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_X86_POWERNOW_K8=m
CONFIG_X86_POWERNOW_K8_ACPI=y
CONFIG_X86_SPEEDSTEP_CENTRINO=m
CONFIG_X86_P4_CLOCKMOD=m

#
# shared options
#
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
CONFIG_X86_SPEEDSTEP_LIB=m
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_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
CONFIG_DMAR=y
CONFIG_DMAR_GFX_WA=y
CONFIG_DMAR_FLOPPY_WA=y
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=m
CONFIG_PCIEAER=y
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_K8_NB=y
CONFIG_PCCARD=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=m
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y

#
# PC-card bridges
#
CONFIG_YENTA=m
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
CONFIG_PD6729=m
CONFIG_I82092=m
CONFIG_PCCARD_NONSTATIC=m
CONFIG_HOTPLUG_PCI=m
CONFIG_HOTPLUG_PCI_FAKE=m
CONFIG_HOTPLUG_PCI_ACPI=m
CONFIG_HOTPLUG_PCI_ACPI_IBM=m
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set

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

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
CONFIG_XFRM_SUB_POLICY=y
CONFIG_XFRM_MIGRATE=y
CONFIG_XFRM_STATISTICS=y
CONFIG_NET_KEY=m
CONFIG_NET_KEY_MIGRATE=y
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=m
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=y
CONFIG_TCP_CONG_CUBIC=m
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_TCP_CONG_HSTCP=m
CONFIG_TCP_CONG_HYBLA=m
CONFIG_TCP_CONG_VEGAS=m
CONFIG_TCP_CONG_SCALABLE=m
CONFIG_TCP_CONG_LP=m
CONFIG_TCP_CONG_VENO=m
CONFIG_TCP_CONG_YEAH=m
CONFIG_TCP_CONG_ILLINOIS=m
CONFIG_DEFAULT_BIC=y
# CONFIG_DEFAULT_CUBIC is not set
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="bic"
CONFIG_TCP_MD5SIG=y
CONFIG_IP_VS=m
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12

#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y

#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m

#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
CONFIG_IPV6_OPTIMISTIC_DAD=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_IPV6_MIP6=m
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_INET6_XFRM_MODE_BEET=m
CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m
CONFIG_IPV6_SIT=m
CONFIG_IPV6_TUNNEL=m
CONFIG_IPV6_MULTIPLE_TABLES=y
CONFIG_IPV6_SUBTREES=y
# CONFIG_NETLABEL is not set
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK=m
CONFIG_NF_CT_ACCT=y
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CT_PROTO_GRE=m
CONFIG_NF_CT_PROTO_SCTP=m
CONFIG_NF_CT_PROTO_UDPLITE=m
CONFIG_NF_CONNTRACK_AMANDA=m
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CONNTRACK_H323=m
CONFIG_NF_CONNTRACK_IRC=m
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_NF_CONNTRACK_PPTP=m
CONFIG_NF_CONNTRACK_SANE=m
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_RATEEST=m
CONFIG_NETFILTER_XT_TARGET_TRACE=m
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_IPRANGE=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_OWNER=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_RATEEST=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_TIME=m
CONFIG_NETFILTER_XT_MATCH_U32=m
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m

#
# IP: Netfilter Configuration
#
CONFIG_NF_CONNTRACK_IPV4=m
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_NF_NAT=m
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_NF_NAT_SNMP_BASIC=m
CONFIG_NF_NAT_PROTO_GRE=m
CONFIG_NF_NAT_FTP=m
CONFIG_NF_NAT_IRC=m
CONFIG_NF_NAT_TFTP=m
CONFIG_NF_NAT_AMANDA=m
CONFIG_NF_NAT_PPTP=m
CONFIG_NF_NAT_H323=m
CONFIG_NF_NAT_SIP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m

#
# IPv6: Netfilter Configuration
#
CONFIG_NF_CONNTRACK_IPV6=m
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_MH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_RAW=m

#
# Bridge: Netfilter Configuration
#
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_ULOG=m
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
CONFIG_IP_DCCP_ACKVEC=y

#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP_CCID2=m
# CONFIG_IP_DCCP_CCID2_DEBUG is not set
CONFIG_IP_DCCP_CCID3=m
# CONFIG_IP_DCCP_CCID3_DEBUG is not set
CONFIG_IP_DCCP_CCID3_RTO=100
CONFIG_IP_DCCP_TFRC_LIB=m

#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG 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=m
CONFIG_TIPC_ADVANCED=y
CONFIG_TIPC_ZONES=3
CONFIG_TIPC_CLUSTERS=1
CONFIG_TIPC_NODES=255
CONFIG_TIPC_SLAVE_NODES=0
CONFIG_TIPC_PORTS=8191
CONFIG_TIPC_LOG=0
# CONFIG_TIPC_DEBUG is not set
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set
CONFIG_ATM_LANE=m
CONFIG_ATM_MPOA=m
CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set
CONFIG_BRIDGE=m
CONFIG_VLAN_8021Q=m
# CONFIG_DECNET is not set
CONFIG_LLC=y
CONFIG_LLC2=m
CONFIG_IPX=m
# CONFIG_IPX_INTERN is not set
CONFIG_ATALK=m
CONFIG_DEV_APPLETALK=m
CONFIG_IPDDP=m
CONFIG_IPDDP_ENCAP=y
CONFIG_IPDDP_DECAP=y
CONFIG_X25=m
CONFIG_LAPB=m
# CONFIG_ECONET is not set
CONFIG_WAN_ROUTER=m
CONFIG_NET_SCHED=y

#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_ATM=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_CLS_FLOW=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_IPT=m
CONFIG_NET_ACT_NAT=m
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
CONFIG_NET_CLS_IND=y
CONFIG_NET_SCH_FIFO=y

#
# Network testing
#
CONFIG_NET_PKTGEN=m
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
CONFIG_IRDA=m

#
# IrDA protocols
#
CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
# CONFIG_IRDA_ULTRA is not set

#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
CONFIG_IRDA_DEBUG=y

#
# Infrared-port device drivers
#

#
# SIR device drivers
#
CONFIG_IRTTY_SIR=m

#
# Dongle support
#
CONFIG_DONGLE=y
CONFIG_ESI_DONGLE=m
CONFIG_ACTISYS_DONGLE=m
CONFIG_TEKRAM_DONGLE=m
CONFIG_TOIM3232_DONGLE=m
CONFIG_LITELINK_DONGLE=m
CONFIG_MA600_DONGLE=m
CONFIG_GIRBIL_DONGLE=m
CONFIG_MCP2120_DONGLE=m
CONFIG_OLD_BELKIN_DONGLE=m
CONFIG_ACT200L_DONGLE=m
CONFIG_KINGSUN_DONGLE=m
CONFIG_KSDAZZLE_DONGLE=m
CONFIG_KS959_DONGLE=m

#
# FIR device drivers
#
CONFIG_USB_IRDA=m
CONFIG_SIGMATEL_FIR=m
CONFIG_NSC_FIR=m
CONFIG_WINBOND_FIR=m
CONFIG_SMC_IRCC_FIR=m
CONFIG_ALI_FIR=m
CONFIG_VLSI_FIR=m
CONFIG_VIA_FIR=m
CONFIG_MCS_FIR=m
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=m
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_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m
CONFIG_AF_RXRPC=m
# CONFIG_AF_RXRPC_DEBUG is not set
CONFIG_RXKAD=m
CONFIG_FIB_RULES=y

#
# Wireless
#
CONFIG_CFG80211=m
CONFIG_NL80211=y
CONFIG_WIRELESS_EXT=y
CONFIG_MAC80211=m

#
# Rate control algorithm selection
#
CONFIG_MAC80211_RC_DEFAULT_PID=y
# CONFIG_MAC80211_RC_DEFAULT_SIMPLE is not set
# CONFIG_MAC80211_RC_DEFAULT_NONE is not set

#
# Selecting 'y' for an algorithm will
#

#
# build the algorithm into mac80211.
#
CONFIG_MAC80211_RC_DEFAULT="pid"
CONFIG_MAC80211_RC_PID=y
# CONFIG_MAC80211_RC_SIMPLE is not set
CONFIG_MAC80211_LEDS=y
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_DEBUG_PACKET_ALIGNMENT is not set
# 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_RFKILL_LEDS=y
CONFIG_NET_9P=m
CONFIG_NET_9P_FD=m
CONFIG_NET_9P_VIRTIO=m
# CONFIG_NET_9P_DEBUG is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=m
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_CONCAT=m
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_REDBOOT_PARTS=m
CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1
# CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set
# CONFIG_MTD_REDBOOT_PARTS_READONLY is not set

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=m
CONFIG_MTD_BLKDEVS=m
CONFIG_MTD_BLOCK=m
CONFIG_MTD_BLOCK_RO=m
CONFIG_FTL=m
CONFIG_NFTL=m
CONFIG_NFTL_RW=y
CONFIG_INFTL=m
CONFIG_RFD_FTL=m
CONFIG_SSFDC=m
# CONFIG_MTD_OOPS is not set

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=m
CONFIG_MTD_JEDECPROBE=m
CONFIG_MTD_GEN_PROBE=m
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
CONFIG_MTD_CFI_INTELEXT=m
CONFIG_MTD_CFI_AMDSTD=m
CONFIG_MTD_CFI_STAA=m
CONFIG_MTD_CFI_UTIL=m
CONFIG_MTD_RAM=m
CONFIG_MTD_ROM=m
CONFIG_MTD_ABSENT=m

#
# Mapping drivers for chip access
#
CONFIG_MTD_COMPLEX_MAPPINGS=y
CONFIG_MTD_PHYSMAP=m
CONFIG_MTD_PHYSMAP_START=0x8000000
CONFIG_MTD_PHYSMAP_LEN=0x4000000
CONFIG_MTD_PHYSMAP_BANKWIDTH=2
CONFIG_MTD_SC520CDP=m
CONFIG_MTD_NETSC520=m
CONFIG_MTD_TS5500=m
CONFIG_MTD_SBC_GXX=m
# CONFIG_MTD_AMD76XROM is not set
# CONFIG_MTD_ICHXROM is not set
# CONFIG_MTD_ESB2ROM is not set
# CONFIG_MTD_CK804XROM is not set
# CONFIG_MTD_SCB2_FLASH is not set
CONFIG_MTD_NETtel=m
CONFIG_MTD_DILNETPC=m
CONFIG_MTD_DILNETPC_BOOTSIZE=0x80000
# CONFIG_MTD_L440GX is not set
CONFIG_MTD_PCI=m
CONFIG_MTD_INTEL_VR_NOR=m
CONFIG_MTD_PLATRAM=m

#
# Self-contained MTD device drivers
#
CONFIG_MTD_PMC551=m
# CONFIG_MTD_PMC551_BUGFIX is not set
# CONFIG_MTD_PMC551_DEBUG is not set
CONFIG_MTD_DATAFLASH=m
CONFIG_MTD_M25P80=m
CONFIG_MTD_SLRAM=m
CONFIG_MTD_PHRAM=m
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
CONFIG_MTD_BLOCK2MTD=m

#
# Disk-On-Chip Device Drivers
#
CONFIG_MTD_DOC2000=m
CONFIG_MTD_DOC2001=m
CONFIG_MTD_DOC2001PLUS=m
CONFIG_MTD_DOCPROBE=m
CONFIG_MTD_DOCECC=m
# CONFIG_MTD_DOCPROBE_ADVANCED is not set
CONFIG_MTD_DOCPROBE_ADDRESS=0
CONFIG_MTD_NAND=m
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
# CONFIG_MTD_NAND_ECC_SMC is not set
# CONFIG_MTD_NAND_MUSEUM_IDS is not set
CONFIG_MTD_NAND_IDS=m
CONFIG_MTD_NAND_DISKONCHIP=m
# CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set
CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0
# CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE is not set
CONFIG_MTD_NAND_CAFE=m
# CONFIG_MTD_NAND_NANDSIM is not set
CONFIG_MTD_NAND_PLATFORM=m
CONFIG_MTD_ALAUDA=m
CONFIG_MTD_ONENAND=m
CONFIG_MTD_ONENAND_VERIFY_WRITE=y
# CONFIG_MTD_ONENAND_OTP is not set
# CONFIG_MTD_ONENAND_2X_PROGRAM is not set
# CONFIG_MTD_ONENAND_SIM is not set

#
# UBI - Unsorted block images
#
CONFIG_MTD_UBI=m
CONFIG_MTD_UBI_WL_THRESHOLD=4096
CONFIG_MTD_UBI_BEB_RESERVE=1
# CONFIG_MTD_UBI_GLUEBI is not set

#
# UBI debugging options
#
# CONFIG_MTD_UBI_DEBUG is not set
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
CONFIG_PARPORT_PC_FIFO=y
# CONFIG_PARPORT_PC_SUPERIO is not set
CONFIG_PARPORT_PC_PCMCIA=m
# CONFIG_PARPORT_GSC is not set
CONFIG_PARPORT_AX88796=m
CONFIG_PARPORT_1284=y
CONFIG_PARPORT_NOT_PC=y
CONFIG_PNP=y
CONFIG_PNP_DEBUG=y

#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=m
CONFIG_PARIDE=m

#
# Parallel IDE high-level drivers
#
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
CONFIG_PARIDE_PT=m
CONFIG_PARIDE_PG=m

#
# Parallel IDE protocol modules
#
CONFIG_PARIDE_ATEN=m
CONFIG_PARIDE_BPCK=m
CONFIG_PARIDE_COMM=m
CONFIG_PARIDE_DSTR=m
CONFIG_PARIDE_FIT2=m
CONFIG_PARIDE_FIT3=m
CONFIG_PARIDE_EPAT=m
CONFIG_PARIDE_EPATC8=y
CONFIG_PARIDE_EPIA=m
CONFIG_PARIDE_FRIQ=m
CONFIG_PARIDE_FRPW=m
CONFIG_PARIDE_KBIC=m
CONFIG_PARIDE_KTTI=m
CONFIG_PARIDE_ON20=m
CONFIG_PARIDE_ON26=m
CONFIG_BLK_CPQ_DA=m
CONFIG_BLK_CPQ_CISS_DA=m
CONFIG_CISS_SCSI_TAPE=y
CONFIG_BLK_DEV_DAC960=m
CONFIG_BLK_DEV_UMEM=m
# 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=m
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=65536
CONFIG_BLK_DEV_XIP=y
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_ATA_OVER_ETH=m
CONFIG_VIRTIO_BLK=m
CONFIG_MISC_DEVICES=y
CONFIG_IBM_ASM=m
CONFIG_PHANTOM=m
CONFIG_EEPROM_93CX6=m
CONFIG_SGI_IOC4=m
CONFIG_TIFM_CORE=m
CONFIG_TIFM_7XX1=m
CONFIG_ACER_WMI=m
CONFIG_ASUS_LAPTOP=m
CONFIG_FUJITSU_LAPTOP=m
CONFIG_MSI_LAPTOP=m
CONFIG_SONY_LAPTOP=m
# CONFIG_SONYPI_COMPAT is not set
CONFIG_THINKPAD_ACPI=m
# CONFIG_THINKPAD_ACPI_DEBUG is not set
CONFIG_THINKPAD_ACPI_BAY=y
CONFIG_THINKPAD_ACPI_VIDEO=y
CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y
CONFIG_INTEL_MENLOW=m
CONFIG_ENCLOSURE_SERVICES=m
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set

#
# SCSI device support
#
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=m
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
CONFIG_CHR_DEV_SCH=m
CONFIG_SCSI_ENCLOSURE=m

#
# 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=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_FC_TGT_ATTRS=y
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_SCSI_SAS_LIBSAS=m
CONFIG_SCSI_SAS_ATA=y
CONFIG_SCSI_SAS_HOST_SMP=y
# CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set
CONFIG_SCSI_SRP_ATTRS=m
CONFIG_SCSI_SRP_TGT_ATTRS=y
CONFIG_SCSI_LOWLEVEL=y
CONFIG_ISCSI_TCP=m
CONFIG_BLK_DEV_3W_XXXX_RAID=m
CONFIG_SCSI_3W_9XXX=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=8
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC7XXX_OLD=m
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=15000
CONFIG_AIC79XX_DEBUG_ENABLE=y
CONFIG_AIC79XX_DEBUG_MASK=0
CONFIG_AIC79XX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC94XX=m
# CONFIG_AIC94XX_DEBUG is not set
CONFIG_SCSI_ADVANSYS=m
CONFIG_SCSI_ARCMSR=m
CONFIG_SCSI_ARCMSR_AER=y
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=m
CONFIG_MEGARAID_MAILBOX=m
CONFIG_MEGARAID_LEGACY=m
CONFIG_MEGARAID_SAS=m
CONFIG_SCSI_HPTIOP=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_SCSI_OMIT_FLASHPOINT is not set
CONFIG_SCSI_DMX3191D=m
CONFIG_SCSI_EATA=m
CONFIG_SCSI_EATA_TAGGED_QUEUE=y
CONFIG_SCSI_EATA_LINKED_COMMANDS=y
CONFIG_SCSI_EATA_MAX_TAGS=16
CONFIG_SCSI_FUTURE_DOMAIN=m
CONFIG_SCSI_GDTH=m
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INITIO=m
CONFIG_SCSI_INIA100=m
CONFIG_SCSI_PPA=m
CONFIG_SCSI_IMM=m
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
CONFIG_SCSI_MVSAS=m
CONFIG_SCSI_STEX=m
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_MMIO=y
CONFIG_SCSI_IPR=m
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA_FC=m
CONFIG_SCSI_QLA_ISCSI=m
CONFIG_SCSI_LPFC=m
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
CONFIG_SCSI_DEBUG=m
CONFIG_SCSI_SRP=m
# CONFIG_SCSI_LOWLEVEL_PCMCIA is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_ACPI=y
CONFIG_SATA_AHCI=m
CONFIG_SATA_SVW=m
CONFIG_ATA_PIIX=m
CONFIG_SATA_MV=m
CONFIG_SATA_NV=y
CONFIG_PDC_ADMA=m
CONFIG_SATA_QSTOR=m
CONFIG_SATA_PROMISE=m
CONFIG_SATA_SX4=m
CONFIG_SATA_SIL=m
CONFIG_SATA_SIL24=m
CONFIG_SATA_SIS=m
CONFIG_SATA_ULI=m
CONFIG_SATA_VIA=m
CONFIG_SATA_VITESSE=m
CONFIG_SATA_INIC162X=m
CONFIG_PATA_ACPI=m
CONFIG_PATA_ALI=m
CONFIG_PATA_AMD=m
CONFIG_PATA_ARTOP=m
CONFIG_PATA_ATIIXP=m
CONFIG_PATA_CMD640_PCI=m
CONFIG_PATA_CMD64X=m
CONFIG_PATA_CS5520=m
CONFIG_PATA_CS5530=m
CONFIG_PATA_CYPRESS=m
CONFIG_PATA_EFAR=m
CONFIG_ATA_GENERIC=m
CONFIG_PATA_HPT366=m
CONFIG_PATA_HPT37X=m
CONFIG_PATA_HPT3X2N=m
CONFIG_PATA_HPT3X3=m
CONFIG_PATA_HPT3X3_DMA=y
CONFIG_PATA_IT821X=m
CONFIG_PATA_IT8213=m
CONFIG_PATA_JMICRON=m
CONFIG_PATA_TRIFLEX=m
CONFIG_PATA_MARVELL=m
CONFIG_PATA_MPIIX=m
CONFIG_PATA_OLDPIIX=m
CONFIG_PATA_NETCELL=m
CONFIG_PATA_NINJA32=m
CONFIG_PATA_NS87410=m
CONFIG_PATA_NS87415=m
CONFIG_PATA_OPTI=m
CONFIG_PATA_OPTIDMA=m
CONFIG_PATA_PCMCIA=m
CONFIG_PATA_PDC_OLD=m
CONFIG_PATA_RADISYS=m
CONFIG_PATA_RZ1000=m
CONFIG_PATA_SC1200=m
CONFIG_PATA_SERVERWORKS=m
CONFIG_PATA_PDC2027X=m
CONFIG_PATA_SIL680=m
CONFIG_PATA_SIS=m
CONFIG_PATA_VIA=m
CONFIG_PATA_WINBOND=m
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
CONFIG_MD_RAID5_RESHAPE=y
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
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=m
CONFIG_DM_MULTIPATH=m
CONFIG_DM_MULTIPATH_EMC=m
CONFIG_DM_MULTIPATH_RDAC=m
CONFIG_DM_MULTIPATH_HP=m
CONFIG_DM_DELAY=m
CONFIG_DM_UEVENT=y
CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
CONFIG_FUSION_FC=m
CONFIG_FUSION_SAS=m
CONFIG_FUSION_MAX_SGE=40
CONFIG_FUSION_CTL=m
CONFIG_FUSION_LAN=m
# CONFIG_FUSION_LOGGING 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=m
CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y
CONFIG_I2O_EXT_ADAPTEC=y
CONFIG_I2O_EXT_ADAPTEC_DMA64=y
CONFIG_I2O_CONFIG=m
CONFIG_I2O_CONFIG_OLD_IOCTL=y
CONFIG_I2O_BUS=m
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_NETDEVICES_MULTIQUEUE is not set
CONFIG_IFB=m
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_MACVLAN=m
CONFIG_EQUALIZER=m
CONFIG_TUN=m
CONFIG_VETH=m
CONFIG_NET_SB1000=m
CONFIG_ARCNET=m
CONFIG_ARCNET_1201=m
CONFIG_ARCNET_1051=m
CONFIG_ARCNET_RAW=m
CONFIG_ARCNET_CAP=m
CONFIG_ARCNET_COM90xx=m
CONFIG_ARCNET_COM90xxIO=m
CONFIG_ARCNET_RIM_I=m
CONFIG_ARCNET_COM20020=m
CONFIG_ARCNET_COM20020_PCI=m
CONFIG_PHYLIB=m

#
# MII PHY device drivers
#
CONFIG_MARVELL_PHY=m
CONFIG_DAVICOM_PHY=m
CONFIG_QSEMI_PHY=m
CONFIG_LXT_PHY=m
CONFIG_CICADA_PHY=m
CONFIG_VITESSE_PHY=m
CONFIG_SMSC_PHY=m
CONFIG_BROADCOM_PHY=m
CONFIG_ICPLUS_PHY=m
CONFIG_REALTEK_PHY=m
CONFIG_MDIO_BITBANG=m
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
CONFIG_HAPPYMEAL=m
CONFIG_SUNGEM=m
CONFIG_CASSINI=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=m
CONFIG_TYPHOON=m
# CONFIG_ENC28J60 is not set
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
CONFIG_TULIP_NAPI=y
CONFIG_TULIP_NAPI_HW_MITIGATION=y
CONFIG_DE4X5=m
CONFIG_WINBOND_840=m
CONFIG_DM9102=m
CONFIG_ULI526X=m
CONFIG_PCMCIA_XIRCOM=m
CONFIG_HP100=m
# 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=m
CONFIG_PCNET32_NAPI=y
CONFIG_AMD8111_ETH=m
CONFIG_AMD8111E_NAPI=y
CONFIG_ADAPTEC_STARFIRE=m
CONFIG_ADAPTEC_STARFIRE_NAPI=y
CONFIG_B44=m
CONFIG_B44_PCI_AUTOSELECT=y
CONFIG_B44_PCICORE_AUTOSELECT=y
CONFIG_B44_PCI=y
CONFIG_FORCEDETH=m
CONFIG_FORCEDETH_NAPI=y
CONFIG_EEPRO100=m
CONFIG_E100=m
CONFIG_FEALNX=m
CONFIG_NATSEMI=m
CONFIG_NE2K_PCI=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
CONFIG_8139TOO_TUNE_TWISTER=y
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_R6040=m
CONFIG_SIS900=m
CONFIG_EPIC100=m
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
CONFIG_VIA_RHINE=m
# CONFIG_VIA_RHINE_MMIO is not set
CONFIG_VIA_RHINE_NAPI=y
CONFIG_SC92031=m
# CONFIG_NET_POCKET is not set
CONFIG_NETDEV_1000=y
CONFIG_ACENIC=m
# CONFIG_ACENIC_OMIT_TIGON_I is not set
CONFIG_DL2K=m
CONFIG_E1000=m
CONFIG_E1000_NAPI=y
# CONFIG_E1000_DISABLE_PACKET_SPLIT is not set
CONFIG_E1000E=m
CONFIG_E1000E_ENABLED=y
CONFIG_IP1000=m
CONFIG_IGB=m
CONFIG_NS83820=m
CONFIG_HAMACHI=m
CONFIG_YELLOWFIN=m
CONFIG_R8169=m
CONFIG_R8169_NAPI=y
CONFIG_R8169_VLAN=y
CONFIG_SIS190=m
CONFIG_SKGE=m
# CONFIG_SKGE_DEBUG is not set
CONFIG_SKY2=m
# CONFIG_SKY2_DEBUG is not set
CONFIG_SK98LIN=m
CONFIG_VIA_VELOCITY=m
CONFIG_TIGON3=m
CONFIG_BNX2=m
CONFIG_QLA3XXX=m
CONFIG_ATL1=m
CONFIG_NETDEV_10000=y
CONFIG_CHELSIO_T1=m
CONFIG_CHELSIO_T1_1G=y
CONFIG_CHELSIO_T1_NAPI=y
CONFIG_CHELSIO_T3=m
CONFIG_IXGBE=m
CONFIG_IXGB=m
CONFIG_IXGB_NAPI=y
CONFIG_S2IO=m
CONFIG_S2IO_NAPI=y
CONFIG_MYRI10GE=m
CONFIG_NETXEN_NIC=m
CONFIG_NIU=m
# CONFIG_MLX4_CORE is not set
CONFIG_TEHUTI=m
CONFIG_BNX2X=m
CONFIG_TR=y
CONFIG_IBMOL=m
# CONFIG_3C359 is not set
CONFIG_TMS380TR=m
CONFIG_TMSPCI=m
CONFIG_ABYSS=m

#
# Wireless LAN
#
CONFIG_WLAN_PRE80211=y
CONFIG_STRIP=m
CONFIG_PCMCIA_WAVELAN=m
CONFIG_PCMCIA_NETWAVE=m
CONFIG_WLAN_80211=y
CONFIG_PCMCIA_RAYCS=m
# CONFIG_IPW2100 is not set
CONFIG_IPW2200=m
CONFIG_IPW2200_MONITOR=y
# CONFIG_IPW2200_RADIOTAP is not set
# CONFIG_IPW2200_PROMISCUOUS is not set
CONFIG_IPW2200_QOS=y
# CONFIG_IPW2200_DEBUG is not set
CONFIG_LIBERTAS=m
CONFIG_LIBERTAS_USB=m
CONFIG_LIBERTAS_CS=m
CONFIG_LIBERTAS_SDIO=m
# CONFIG_LIBERTAS_DEBUG is not set
CONFIG_AIRO=m
CONFIG_HERMES=m
CONFIG_PLX_HERMES=m
CONFIG_TMD_HERMES=m
CONFIG_NORTEL_HERMES=m
CONFIG_PCI_HERMES=m
CONFIG_PCMCIA_HERMES=m
CONFIG_PCMCIA_SPECTRUM=m
CONFIG_ATMEL=m
CONFIG_PCI_ATMEL=m
CONFIG_PCMCIA_ATMEL=m
CONFIG_AIRO_CS=m
CONFIG_PCMCIA_WL3501=m
CONFIG_PRISM54=m
CONFIG_USB_ZD1201=m
CONFIG_USB_NET_RNDIS_WLAN=m
CONFIG_RTL8180=m
CONFIG_RTL8187=m
CONFIG_ADM8211=m
CONFIG_P54_COMMON=m
CONFIG_P54_USB=m
CONFIG_P54_PCI=m
CONFIG_ATH5K=m
CONFIG_IWL4965=m
CONFIG_IWL4965_QOS=y
CONFIG_IWL4965_SPECTRUM_MEASUREMENT=y
CONFIG_IWL4965_SENSITIVITY=y
# CONFIG_IWL4965_DEBUG is not set
CONFIG_IWL3945=m
CONFIG_IWL3945_QOS=y
CONFIG_IWL3945_SPECTRUM_MEASUREMENT=y
# CONFIG_IWL3945_DEBUG is not set
CONFIG_HOSTAP=m
CONFIG_HOSTAP_FIRMWARE=y
# CONFIG_HOSTAP_FIRMWARE_NVRAM is not set
CONFIG_HOSTAP_PLX=m
CONFIG_HOSTAP_PCI=m
CONFIG_HOSTAP_CS=m
CONFIG_BCM43XX=m
CONFIG_BCM43XX_DEBUG=y
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_PCMCIA=y
CONFIG_B43_LEDS=y
CONFIG_B43_RFKILL=y
# CONFIG_B43_DEBUG is not set
CONFIG_B43LEGACY=m
CONFIG_B43LEGACY_PCI_AUTOSELECT=y
CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
CONFIG_B43LEGACY_LEDS=y
CONFIG_B43LEGACY_RFKILL=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=m
CONFIG_RT2X00_LIB=m
CONFIG_RT2X00_LIB_PCI=m
CONFIG_RT2X00_LIB_USB=m
CONFIG_RT2X00_LIB_FIRMWARE=y
CONFIG_RT2X00_LIB_RFKILL=y
CONFIG_RT2400PCI=m
CONFIG_RT2400PCI_RFKILL=y
CONFIG_RT2500PCI=m
CONFIG_RT2500PCI_RFKILL=y
CONFIG_RT61PCI=m
CONFIG_RT61PCI_RFKILL=y
CONFIG_RT2500USB=m
CONFIG_RT73USB=m
# CONFIG_RT2X00_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=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=m
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_NET_PCMCIA=y
CONFIG_PCMCIA_3C589=m
CONFIG_PCMCIA_3C574=m
CONFIG_PCMCIA_FMVJ18X=m
CONFIG_PCMCIA_PCNET=m
CONFIG_PCMCIA_NMCLAN=m
CONFIG_PCMCIA_SMC91C92=m
CONFIG_PCMCIA_XIRC2PS=m
CONFIG_PCMCIA_AXNET=m
CONFIG_ARCNET_COM20020_CS=m
CONFIG_WAN=y
CONFIG_LANMEDIA=m
CONFIG_HDLC=m
CONFIG_HDLC_RAW=m
CONFIG_HDLC_RAW_ETH=m
CONFIG_HDLC_CISCO=m
CONFIG_HDLC_FR=m
CONFIG_HDLC_PPP=m
CONFIG_HDLC_X25=m
CONFIG_PCI200SYN=m
CONFIG_WANXL=m
CONFIG_PC300=m
CONFIG_PC300_MLPPP=y

#
# Cyclades-PC300 MLPPP support is disabled.
#

#
# Refer to the file README.mlppp, provided by PC300 package.
#
# CONFIG_PC300TOO is not set
CONFIG_FARSYNC=m
CONFIG_DSCC4=m
CONFIG_DSCC4_PCISYNC=y
CONFIG_DSCC4_PCI_RST=y
CONFIG_DLCI=m
CONFIG_DLCI_MAX=8
CONFIG_WAN_ROUTER_DRIVERS=m
CONFIG_CYCLADES_SYNC=m
CONFIG_CYCLOMX_X25=y
CONFIG_LAPBETHER=m
CONFIG_X25_ASY=m
CONFIG_SBNI=m
# CONFIG_SBNI_MULTILINE is not set
CONFIG_ATM_DRIVERS=y
CONFIG_ATM_DUMMY=m
CONFIG_ATM_TCP=m
CONFIG_ATM_LANAI=m
CONFIG_ATM_ENI=m
# CONFIG_ATM_ENI_DEBUG is not set
# CONFIG_ATM_ENI_TUNE_BURST is not set
CONFIG_ATM_FIRESTREAM=m
CONFIG_ATM_ZATM=m
# CONFIG_ATM_ZATM_DEBUG is not set
CONFIG_ATM_IDT77252=m
# CONFIG_ATM_IDT77252_DEBUG is not set
# CONFIG_ATM_IDT77252_RCV_ALL is not set
CONFIG_ATM_IDT77252_USE_SUNI=y
CONFIG_ATM_AMBASSADOR=m
# CONFIG_ATM_AMBASSADOR_DEBUG is not set
CONFIG_ATM_HORIZON=m
# CONFIG_ATM_HORIZON_DEBUG is not set
CONFIG_ATM_FORE200E_MAYBE=m
CONFIG_ATM_FORE200E_PCA=y
CONFIG_ATM_FORE200E_PCA_DEFAULT_FW=y
# CONFIG_ATM_FORE200E_USE_TASKLET is not set
CONFIG_ATM_FORE200E_TX_RETRY=16
CONFIG_ATM_FORE200E_DEBUG=0
CONFIG_ATM_FORE200E=m
CONFIG_ATM_HE=m
CONFIG_ATM_HE_USE_SUNI=y
CONFIG_FDDI=y
CONFIG_DEFXX=m
# CONFIG_DEFXX_MMIO is not set
CONFIG_SKFP=m
CONFIG_HIPPI=y
CONFIG_ROADRUNNER=m
# CONFIG_ROADRUNNER_LARGE_RINGS is not set
CONFIG_PLIP=m
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_PPPOATM=m
CONFIG_PPPOL2TP=m
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLHC=m
CONFIG_SLIP_SMART=y
# CONFIG_SLIP_MODE_SLIP6 is not set
CONFIG_NET_FC=y
CONFIG_NETCONSOLE=m
# CONFIG_NETCONSOLE_DYNAMIC is not set
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_VIRTIO_NET=m
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=m
CONFIG_INPUT_POLLDEV=m

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

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_KEYBOARD_SUNKBD=m
CONFIG_KEYBOARD_LKKBD=m
CONFIG_KEYBOARD_XTKBD=m
CONFIG_KEYBOARD_NEWTON=m
CONFIG_KEYBOARD_STOWAWAY=m
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=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_SERIAL=m
CONFIG_MOUSE_APPLETOUCH=m
CONFIG_MOUSE_VSXXXAA=m
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
CONFIG_JOYSTICK_A3D=m
CONFIG_JOYSTICK_ADI=m
CONFIG_JOYSTICK_COBRA=m
CONFIG_JOYSTICK_GF2K=m
CONFIG_JOYSTICK_GRIP=m
CONFIG_JOYSTICK_GRIP_MP=m
CONFIG_JOYSTICK_GUILLEMOT=m
CONFIG_JOYSTICK_INTERACT=m
CONFIG_JOYSTICK_SIDEWINDER=m
CONFIG_JOYSTICK_TMDC=m
CONFIG_JOYSTICK_IFORCE=m
CONFIG_JOYSTICK_IFORCE_USB=y
CONFIG_JOYSTICK_IFORCE_232=y
CONFIG_JOYSTICK_WARRIOR=m
CONFIG_JOYSTICK_MAGELLAN=m
CONFIG_JOYSTICK_SPACEORB=m
CONFIG_JOYSTICK_SPACEBALL=m
CONFIG_JOYSTICK_STINGER=m
CONFIG_JOYSTICK_TWIDJOY=m
CONFIG_JOYSTICK_DB9=m
CONFIG_JOYSTICK_GAMECON=m
CONFIG_JOYSTICK_TURBOGRAFX=m
CONFIG_JOYSTICK_JOYDUMP=m
CONFIG_JOYSTICK_XPAD=m
CONFIG_JOYSTICK_XPAD_FF=y
CONFIG_JOYSTICK_XPAD_LEDS=y
CONFIG_INPUT_TABLET=y
CONFIG_TABLET_USB_ACECAD=m
CONFIG_TABLET_USB_AIPTEK=m
CONFIG_TABLET_USB_GTCO=m
CONFIG_TABLET_USB_KBTAB=m
CONFIG_TABLET_USB_WACOM=m
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_ADS7846=m
CONFIG_TOUCHSCREEN_FUJITSU=m
CONFIG_TOUCHSCREEN_GUNZE=m
CONFIG_TOUCHSCREEN_ELO=m
CONFIG_TOUCHSCREEN_MTOUCH=m
CONFIG_TOUCHSCREEN_MK712=m
CONFIG_TOUCHSCREEN_PENMOUNT=m
CONFIG_TOUCHSCREEN_TOUCHRIGHT=m
CONFIG_TOUCHSCREEN_TOUCHWIN=m
CONFIG_TOUCHSCREEN_UCB1400=m
CONFIG_TOUCHSCREEN_USB_COMPOSITE=m
CONFIG_TOUCHSCREEN_USB_EGALAX=y
CONFIG_TOUCHSCREEN_USB_PANJIT=y
CONFIG_TOUCHSCREEN_USB_3M=y
CONFIG_TOUCHSCREEN_USB_ITM=y
CONFIG_TOUCHSCREEN_USB_ETURBO=y
CONFIG_TOUCHSCREEN_USB_GUNZE=y
CONFIG_TOUCHSCREEN_USB_DMC_TSC10=y
CONFIG_TOUCHSCREEN_USB_IRTOUCH=y
CONFIG_TOUCHSCREEN_USB_IDEALTEK=y
CONFIG_TOUCHSCREEN_USB_GENERAL_TOUCH=y
CONFIG_TOUCHSCREEN_USB_GOTOP=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_APANEL=m
CONFIG_INPUT_ATLAS_BTNS=m
CONFIG_INPUT_ATI_REMOTE=m
CONFIG_INPUT_ATI_REMOTE2=m
CONFIG_INPUT_KEYSPAN_REMOTE=m
CONFIG_INPUT_POWERMATE=m
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_PARKBD=m
CONFIG_SERIO_PCIPS2=m
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
CONFIG_GAMEPORT=m
CONFIG_GAMEPORT_NS558=m
CONFIG_GAMEPORT_L4=m
CONFIG_GAMEPORT_EMU10K1=m
CONFIG_GAMEPORT_FM801=m

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

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=16
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
CONFIG_SERIAL_8250_RSA=y

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
CONFIG_PPDEV=m
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
CONFIG_NVRAM=m
CONFIG_RTC=y
CONFIG_R3964=m
CONFIG_APPLICOM=m

#
# PCMCIA character devices
#
CONFIG_SYNCLINK_CS=m
CONFIG_CARDMAN_4000=m
CONFIG_CARDMAN_4040=m
CONFIG_IPWIRELESS=m
CONFIG_MWAVE=m
# CONFIG_PC8736x_GPIO is not set
CONFIG_RAW_DRIVER=m
CONFIG_MAX_RAW_DEVS=256
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=m
CONFIG_I2C_ALGOPCA=m

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

#
# Miscellaneous I2C Chip support
#
CONFIG_DS1682=m
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_PCF8574=m
CONFIG_PCF8575=m
CONFIG_SENSORS_PCF8591=m
CONFIG_TPS65010=m
CONFIG_SENSORS_MAX6875=m
CONFIG_SENSORS_TSL2550=m
# 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=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y

#
# SPI Master Controller Drivers
#
CONFIG_SPI_BITBANG=m
CONFIG_SPI_BUTTERFLY=m
CONFIG_SPI_LM70_LLP=m

#
# SPI Protocol Masters
#
CONFIG_SPI_AT25=m
# CONFIG_SPI_SPIDEV is not set
CONFIG_SPI_TLE62X0=m
CONFIG_W1=m
CONFIG_W1_CON=y

#
# 1-wire Bus Masters
#
CONFIG_W1_MASTER_MATROX=m
CONFIG_W1_MASTER_DS2490=m
CONFIG_W1_MASTER_DS2482=m

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

#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=m
CONFIG_ACQUIRE_WDT=m
CONFIG_ADVANTECH_WDT=m
CONFIG_ALIM1535_WDT=m
CONFIG_ALIM7101_WDT=m
CONFIG_SC520_WDT=m
CONFIG_EUROTECH_WDT=m
CONFIG_IB700_WDT=m
CONFIG_IBMASR=m
CONFIG_WAFER_WDT=m
CONFIG_I6300ESB_WDT=m
CONFIG_ITCO_WDT=m
CONFIG_ITCO_VENDOR_SUPPORT=y
CONFIG_IT8712F_WDT=m
CONFIG_HP_WATCHDOG=m
CONFIG_SC1200_WDT=m
CONFIG_PC87413_WDT=m
CONFIG_60XX_WDT=m
CONFIG_SBC8360_WDT=m
CONFIG_CPU5_WDT=m
CONFIG_SMSC37B787_WDT=m
CONFIG_W83627HF_WDT=m
CONFIG_W83697HF_WDT=m
CONFIG_W83877F_WDT=m
CONFIG_W83977F_WDT=m
CONFIG_MACHZ_WDT=m
CONFIG_SBC_EPX_C3_WATCHDOG=m

#
# PCI-based Watchdog Cards
#
CONFIG_PCIPCWATCHDOG=m
CONFIG_WDTPCI=m
CONFIG_WDT_501_PCI=y

#
# USB-based Watchdog Cards
#
CONFIG_USBPCWATCHDOG=m

#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
CONFIG_SSB=m
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCIHOST=y
CONFIG_SSB_B43_PCI_BRIDGE=y
CONFIG_SSB_PCMCIAHOST_POSSIBLE=y
CONFIG_SSB_PCMCIAHOST=y
# CONFIG_SSB_DEBUG is not set
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y

#
# Multifunction device drivers
#
CONFIG_MFD_SM501=m

#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L2_COMMON=m
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
CONFIG_VIDEO_TVAUDIO=m
CONFIG_VIDEO_TDA7432=m
CONFIG_VIDEO_TDA9840=m
CONFIG_VIDEO_TDA9875=m
CONFIG_VIDEO_TEA6415C=m
CONFIG_VIDEO_TEA6420=m
CONFIG_VIDEO_MSP3400=m
CONFIG_VIDEO_CS53L32A=m
CONFIG_VIDEO_M52790=m
CONFIG_VIDEO_WM8775=m
CONFIG_VIDEO_WM8739=m
CONFIG_VIDEO_VP27SMPX=m
CONFIG_VIDEO_BT819=m
CONFIG_VIDEO_BT856=m
CONFIG_VIDEO_KS0127=m
CONFIG_VIDEO_OV7670=m
CONFIG_VIDEO_SAA7110=m
CONFIG_VIDEO_SAA7111=m
CONFIG_VIDEO_SAA7114=m
CONFIG_VIDEO_SAA711X=m
CONFIG_VIDEO_TVP5150=m
CONFIG_VIDEO_VPX3220=m
CONFIG_VIDEO_CX25840=m
CONFIG_VIDEO_CX2341X=m
CONFIG_VIDEO_SAA7127=m
CONFIG_VIDEO_SAA7185=m
CONFIG_VIDEO_ADV7170=m
CONFIG_VIDEO_ADV7175=m
CONFIG_VIDEO_UPD64031A=m
CONFIG_VIDEO_UPD64083=m
CONFIG_VIDEO_VIVI=m
CONFIG_VIDEO_BT848=m
CONFIG_VIDEO_BT848_DVB=y
CONFIG_VIDEO_SAA6588=m
CONFIG_VIDEO_BWQCAM=m
CONFIG_VIDEO_CQCAM=m
CONFIG_VIDEO_W9966=m
CONFIG_VIDEO_CPIA=m
CONFIG_VIDEO_CPIA_PP=m
CONFIG_VIDEO_CPIA_USB=m
CONFIG_VIDEO_CPIA2=m
CONFIG_VIDEO_SAA5246A=m
CONFIG_VIDEO_SAA5249=m
CONFIG_TUNER_3036=m
CONFIG_VIDEO_STRADIS=m
CONFIG_VIDEO_ZORAN_ZR36060=m
CONFIG_VIDEO_ZORAN=m
CONFIG_VIDEO_ZORAN_BUZ=m
CONFIG_VIDEO_ZORAN_DC10=m
CONFIG_VIDEO_ZORAN_DC30=m
CONFIG_VIDEO_ZORAN_LML33=m
CONFIG_VIDEO_ZORAN_LML33R10=m
CONFIG_VIDEO_ZORAN_AVS6EYES=m
CONFIG_VIDEO_MEYE=m
CONFIG_VIDEO_SAA7134=m
CONFIG_VIDEO_SAA7134_ALSA=m
CONFIG_VIDEO_SAA7134_DVB=m
CONFIG_VIDEO_MXB=m
CONFIG_VIDEO_DPC=m
CONFIG_VIDEO_HEXIUM_ORION=m
CONFIG_VIDEO_HEXIUM_GEMINI=m
CONFIG_VIDEO_CX88=m
CONFIG_VIDEO_CX88_ALSA=m
CONFIG_VIDEO_CX88_BLACKBIRD=m
CONFIG_VIDEO_CX88_DVB=m
CONFIG_VIDEO_CX88_VP3054=m
CONFIG_VIDEO_CX23885=m
CONFIG_VIDEO_IVTV=m
CONFIG_VIDEO_FB_IVTV=m
CONFIG_VIDEO_CAFE_CCIC=m
CONFIG_V4L_USB_DRIVERS=y
CONFIG_VIDEO_PVRUSB2=m
CONFIG_VIDEO_PVRUSB2_ONAIR_CREATOR=y
CONFIG_VIDEO_PVRUSB2_ONAIR_USB2=y
CONFIG_VIDEO_PVRUSB2_SYSFS=y
# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set
CONFIG_VIDEO_EM28XX=m
CONFIG_VIDEO_EM28XX_ALSA=m
CONFIG_VIDEO_USBVISION=m
CONFIG_VIDEO_USBVIDEO=m
CONFIG_USB_VICAM=m
CONFIG_USB_IBMCAM=m
CONFIG_USB_KONICAWC=m
CONFIG_USB_QUICKCAM_MESSENGER=m
CONFIG_USB_ET61X251=m
CONFIG_VIDEO_OVCAMCHIP=m
CONFIG_USB_W9968CF=m
CONFIG_USB_OV511=m
CONFIG_USB_SE401=m
CONFIG_USB_SN9C102=m
CONFIG_USB_STV680=m
CONFIG_USB_ZC0301=m
CONFIG_USB_PWC=m
# CONFIG_USB_PWC_DEBUG is not set
CONFIG_USB_ZR364XX=m
CONFIG_USB_STKWEBCAM=m
CONFIG_RADIO_ADAPTERS=y
CONFIG_RADIO_GEMTEK_PCI=m
CONFIG_RADIO_MAXIRADIO=m
CONFIG_RADIO_MAESTRO=m
CONFIG_USB_DSBR=m
CONFIG_USB_SI470X=m
CONFIG_DVB_CORE=m
CONFIG_DVB_CORE_ATTACH=y
CONFIG_DVB_CAPTURE_DRIVERS=y

#
# Supported SAA7146 based PCI Adapters
#
CONFIG_TTPCI_EEPROM=m
CONFIG_DVB_AV7110=m
CONFIG_DVB_AV7110_OSD=y
CONFIG_DVB_BUDGET_CORE=m
CONFIG_DVB_BUDGET=m
CONFIG_DVB_BUDGET_CI=m
CONFIG_DVB_BUDGET_AV=m
CONFIG_DVB_BUDGET_PATCH=m

#
# Supported USB Adapters
#
CONFIG_DVB_USB=m
# CONFIG_DVB_USB_DEBUG is not set
CONFIG_DVB_USB_A800=m
CONFIG_DVB_USB_DIBUSB_MB=m
CONFIG_DVB_USB_DIBUSB_MB_FAULTY=y
CONFIG_DVB_USB_DIBUSB_MC=m
CONFIG_DVB_USB_DIB0700=m
CONFIG_DVB_USB_UMT_010=m
CONFIG_DVB_USB_CXUSB=m
CONFIG_DVB_USB_M920X=m
CONFIG_DVB_USB_GL861=m
CONFIG_DVB_USB_AU6610=m
CONFIG_DVB_USB_DIGITV=m
CONFIG_DVB_USB_VP7045=m
CONFIG_DVB_USB_VP702X=m
CONFIG_DVB_USB_GP8PSK=m
CONFIG_DVB_USB_NOVA_T_USB2=m
CONFIG_DVB_USB_TTUSB2=m
CONFIG_DVB_USB_DTT200U=m
CONFIG_DVB_USB_OPERA1=m
CONFIG_DVB_USB_AF9005=m
CONFIG_DVB_USB_AF9005_REMOTE=m
CONFIG_DVB_TTUSB_BUDGET=m
CONFIG_DVB_TTUSB_DEC=m
CONFIG_DVB_CINERGYT2=m
# CONFIG_DVB_CINERGYT2_TUNING is not set

#
# Supported FlexCopII (B2C2) Adapters
#
CONFIG_DVB_B2C2_FLEXCOP=m
CONFIG_DVB_B2C2_FLEXCOP_PCI=m
CONFIG_DVB_B2C2_FLEXCOP_USB=m
# CONFIG_DVB_B2C2_FLEXCOP_DEBUG is not set

#
# Supported BT878 Adapters
#
CONFIG_DVB_BT8XX=m

#
# Supported Pluto2 Adapters
#
CONFIG_DVB_PLUTO2=m

#
# Supported DVB Frontends
#

#
# Customise DVB Frontends
#
# CONFIG_DVB_FE_CUSTOMISE is not set

#
# DVB-S (satellite) frontends
#
CONFIG_DVB_STV0299=m
CONFIG_DVB_CX24110=m
CONFIG_DVB_CX24123=m
CONFIG_DVB_TDA8083=m
CONFIG_DVB_MT312=m
CONFIG_DVB_VES1X93=m
CONFIG_DVB_S5H1420=m
CONFIG_DVB_TDA10086=m

#
# DVB-T (terrestrial) frontends
#
CONFIG_DVB_SP8870=m
CONFIG_DVB_SP887X=m
CONFIG_DVB_CX22700=m
CONFIG_DVB_CX22702=m
CONFIG_DVB_L64781=m
CONFIG_DVB_TDA1004X=m
CONFIG_DVB_NXT6000=m
CONFIG_DVB_MT352=m
CONFIG_DVB_ZL10353=m
CONFIG_DVB_DIB3000MB=m
CONFIG_DVB_DIB3000MC=m
CONFIG_DVB_DIB7000M=m
CONFIG_DVB_DIB7000P=m

#
# DVB-C (cable) frontends
#
CONFIG_DVB_VES1820=m
CONFIG_DVB_TDA10021=m
CONFIG_DVB_TDA10023=m
CONFIG_DVB_STV0297=m

#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends
#
CONFIG_DVB_NXT200X=m
CONFIG_DVB_OR51211=m
CONFIG_DVB_OR51132=m
CONFIG_DVB_BCM3510=m
CONFIG_DVB_LGDT330X=m
CONFIG_DVB_S5H1409=m

#
# Tuners/PLL support
#
CONFIG_DVB_PLL=m
CONFIG_DVB_TDA826X=m
CONFIG_DVB_TDA827X=m
CONFIG_DVB_TDA18271=m
CONFIG_DVB_TUNER_QT1010=m
CONFIG_DVB_TUNER_MT2060=m
CONFIG_DVB_TUNER_MT2266=m
CONFIG_DVB_TUNER_MT2131=m
CONFIG_DVB_TUNER_DIB0070=m
CONFIG_DVB_TUNER_XC5000=m

#
# Miscellaneous devices
#
CONFIG_DVB_LNBP21=m
CONFIG_DVB_ISL6421=m
CONFIG_DVB_TUA6100=m
CONFIG_VIDEO_SAA7146=m
CONFIG_VIDEO_SAA7146_VV=m
CONFIG_VIDEO_TUNER=m
# CONFIG_VIDEO_TUNER_CUSTOMIZE is not set
CONFIG_TUNER_XC2028=m
CONFIG_TUNER_MT20XX=m
CONFIG_TUNER_TDA8290=m
CONFIG_TUNER_TEA5761=m
CONFIG_TUNER_TEA5767=m
CONFIG_TUNER_SIMPLE=m
CONFIG_TUNER_TDA9887=m
CONFIG_VIDEOBUF_GEN=m
CONFIG_VIDEOBUF_DMA_SG=m
CONFIG_VIDEOBUF_VMALLOC=m
CONFIG_VIDEOBUF_DVB=m
CONFIG_VIDEO_BTCX=m
CONFIG_VIDEO_IR_I2C=m
CONFIG_VIDEO_IR=m
CONFIG_VIDEO_TVEEPROM=m
CONFIG_DAB=y
CONFIG_USB_DABUSB=m

#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=m
CONFIG_AGP_SIS=m
CONFIG_AGP_VIA=m
CONFIG_DRM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m
CONFIG_DRM_VIA=m
CONFIG_DRM_SAVAGE=m
CONFIG_VGASTATE=m
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_FB=m
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=m
CONFIG_FB_CFB_FILLRECT=m
CONFIG_FB_CFB_COPYAREA=m
CONFIG_FB_CFB_IMAGEBLIT=m
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
CONFIG_FB_SYS_FILLRECT=m
CONFIG_FB_SYS_COPYAREA=m
CONFIG_FB_SYS_IMAGEBLIT=m
CONFIG_FB_SYS_FOPS=m
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_SVGALIB=m
# 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=m
CONFIG_FB_PM2=m
CONFIG_FB_PM2_FIFO_DISCONNECT=y
CONFIG_FB_CYBER2000=m
CONFIG_FB_ARC=m
CONFIG_FB_VGA16=m
CONFIG_FB_UVESA=m
CONFIG_FB_HECUBA=m
CONFIG_FB_HGA=m
CONFIG_FB_HGA_ACCEL=y
CONFIG_FB_S1D13XXX=m
CONFIG_FB_NVIDIA=m
CONFIG_FB_NVIDIA_I2C=y
# CONFIG_FB_NVIDIA_DEBUG is not set
CONFIG_FB_NVIDIA_BACKLIGHT=y
CONFIG_FB_RIVA=m
CONFIG_FB_RIVA_I2C=y
# CONFIG_FB_RIVA_DEBUG is not set
CONFIG_FB_RIVA_BACKLIGHT=y
CONFIG_FB_LE80578=m
CONFIG_FB_CARILLO_RANCH=m
CONFIG_FB_INTEL=m
# CONFIG_FB_INTEL_DEBUG is not set
CONFIG_FB_INTEL_I2C=y
CONFIG_FB_MATROX=m
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G=y
CONFIG_FB_MATROX_I2C=m
CONFIG_FB_MATROX_MAVEN=m
CONFIG_FB_MATROX_MULTIHEAD=y
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_FB_ATY128=m
CONFIG_FB_ATY128_BACKLIGHT=y
CONFIG_FB_ATY=m
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
CONFIG_FB_ATY_GX=y
CONFIG_FB_ATY_BACKLIGHT=y
CONFIG_FB_S3=m
CONFIG_FB_SAVAGE=m
CONFIG_FB_SAVAGE_I2C=y
CONFIG_FB_SAVAGE_ACCEL=y
CONFIG_FB_SIS=m
CONFIG_FB_SIS_300=y
CONFIG_FB_SIS_315=y
CONFIG_FB_NEOMAGIC=m
CONFIG_FB_KYRO=m
CONFIG_FB_3DFX=m
CONFIG_FB_3DFX_ACCEL=y
CONFIG_FB_VOODOO1=m
CONFIG_FB_VT8623=m
CONFIG_FB_TRIDENT=m
CONFIG_FB_TRIDENT_ACCEL=y
CONFIG_FB_ARK=m
CONFIG_FB_PM3=m
# CONFIG_FB_GEODE is not set
CONFIG_FB_SM501=m
# CONFIG_FB_VIRTUAL is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_LCD_CLASS_DEVICE=m
CONFIG_LCD_LTV350QV=m
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_CORGI=m
CONFIG_BACKLIGHT_PROGEAR=m
CONFIG_BACKLIGHT_CARILLO_RANCH=m

#
# Display device support
#
CONFIG_DISPLAY_SUPPORT=m

#
# Display hardware drivers
#

#
# 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=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# 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_RTCTIMER=m
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
CONFIG_SND_DYNAMIC_MINORS=y
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
CONFIG_SND_OPL3_LIB=m
CONFIG_SND_VX_LIB=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
CONFIG_SND_MTS64=m
CONFIG_SND_SERIAL_U16550=m
CONFIG_SND_MPU401=m
CONFIG_SND_PORTMAN2X4=m
CONFIG_SND_SB_COMMON=m
CONFIG_SND_SB16_DSP=m

#
# PCI devices
#
CONFIG_SND_AD1889=m
CONFIG_SND_ALS300=m
CONFIG_SND_ALS4000=m
CONFIG_SND_ALI5451=m
CONFIG_SND_ATIIXP=m
CONFIG_SND_ATIIXP_MODEM=m
CONFIG_SND_AU8810=m
CONFIG_SND_AU8820=m
CONFIG_SND_AU8830=m
CONFIG_SND_AZT3328=m
CONFIG_SND_BT87X=m
# CONFIG_SND_BT87X_OVERCLOCK is not set
CONFIG_SND_CA0106=m
CONFIG_SND_CMIPCI=m
CONFIG_SND_OXYGEN_LIB=m
CONFIG_SND_OXYGEN=m
CONFIG_SND_CS4281=m
CONFIG_SND_CS46XX=m
CONFIG_SND_CS46XX_NEW_DSP=y
CONFIG_SND_CS5530=m
CONFIG_SND_DARLA20=m
CONFIG_SND_GINA20=m
CONFIG_SND_LAYLA20=m
CONFIG_SND_DARLA24=m
CONFIG_SND_GINA24=m
CONFIG_SND_LAYLA24=m
CONFIG_SND_MONA=m
CONFIG_SND_MIA=m
CONFIG_SND_ECHO3G=m
CONFIG_SND_INDIGO=m
CONFIG_SND_INDIGOIO=m
CONFIG_SND_INDIGODJ=m
CONFIG_SND_EMU10K1=m
CONFIG_SND_EMU10K1X=m
CONFIG_SND_ENS1370=m
CONFIG_SND_ENS1371=m
CONFIG_SND_ES1938=m
CONFIG_SND_ES1968=m
CONFIG_SND_FM801=m
CONFIG_SND_FM801_TEA575X_BOOL=y
CONFIG_SND_FM801_TEA575X=m
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=0
CONFIG_SND_HDSP=m
CONFIG_SND_HDSPM=m
CONFIG_SND_HIFIER=m
CONFIG_SND_ICE1712=m
CONFIG_SND_ICE1724=m
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
CONFIG_SND_KORG1212=m
CONFIG_SND_KORG1212_FIRMWARE_IN_KERNEL=y
CONFIG_SND_MAESTRO3=m
CONFIG_SND_MAESTRO3_FIRMWARE_IN_KERNEL=y
CONFIG_SND_MIXART=m
CONFIG_SND_NM256=m
CONFIG_SND_PCXHR=m
CONFIG_SND_RIPTIDE=m
CONFIG_SND_RME32=m
CONFIG_SND_RME96=m
CONFIG_SND_RME9652=m
CONFIG_SND_SONICVIBES=m
CONFIG_SND_TRIDENT=m
CONFIG_SND_VIA82XX=m
CONFIG_SND_VIA82XX_MODEM=m
CONFIG_SND_VIRTUOSO=m
CONFIG_SND_VX222=m
CONFIG_SND_YMFPCI=m
CONFIG_SND_YMFPCI_FIRMWARE_IN_KERNEL=y
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0

#
# SPI devices
#

#
# USB devices
#
CONFIG_SND_USB_AUDIO=m
CONFIG_SND_USB_USX2Y=m
CONFIG_SND_USB_CAIAQ=m
CONFIG_SND_USB_CAIAQ_INPUT=y

#
# PCMCIA devices
#
CONFIG_SND_VXPOCKET=m
CONFIG_SND_PDAUDIOCF=m

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

#
# SoC Audio support for SuperH
#

#
# ALSA SoC audio for Freescale SOCs
#

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
CONFIG_AC97_BUS=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=y
CONFIG_HID_FF=y
CONFIG_HID_PID=y
CONFIG_LOGITECH_FF=y
CONFIG_PANTHERLORD_FF=y
CONFIG_THRUSTMASTER_FF=y
CONFIG_ZEROPLUS_FF=y
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
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
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y

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

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

#
# 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=y
CONFIG_USB_LIBUSUAL=y

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

#
# USB port drivers
#
CONFIG_USB_USS720=m
CONFIG_USB_SERIAL=m
CONFIG_USB_EZUSB=y
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_IUU=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=m
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=m

#
# 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=m
CONFIG_USB_LED=m
CONFIG_USB_CYPRESS_CY7C63=m
CONFIG_USB_CYTHERM=m
CONFIG_USB_PHIDGET=m
CONFIG_USB_PHIDGETKIT=m
CONFIG_USB_PHIDGETMOTORCONTROL=m
CONFIG_USB_PHIDGETSERVO=m
CONFIG_USB_IDMOUSE=m
CONFIG_USB_FTDI_ELAN=m
CONFIG_USB_APPLEDISPLAY=m
CONFIG_USB_SISUSBVGA=m
CONFIG_USB_SISUSBVGA_CON=y
CONFIG_USB_LD=m
CONFIG_USB_TRANCEVIBRATOR=m
CONFIG_USB_IOWARRIOR=m
CONFIG_USB_TEST=m
CONFIG_USB_ATM=m
CONFIG_USB_SPEEDTOUCH=m
CONFIG_USB_CXACRU=m
CONFIG_USB_UEAGLEATM=m
CONFIG_USB_XUSBATM=m
# 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=m

#
# MMC/SD Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
CONFIG_MMC_RICOH_MMC=m
CONFIG_MMC_WBSD=m
CONFIG_MMC_TIFM_SD=m
CONFIG_MMC_SPI=m
CONFIG_MEMSTICK=m
# CONFIG_MEMSTICK_DEBUG is not set

#
# MemoryStick drivers
#
# CONFIG_MEMSTICK_UNSAFE_RESUME is not set
CONFIG_MSPRO_BLOCK=m

#
# MemoryStick Host Controller Drivers
#
CONFIG_MEMSTICK_TIFM_MS=m
CONFIG_MEMSTICK_JMICRON_38X=m
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=m

#
# LED drivers
#
CONFIG_LEDS_CLEVO_MAIL=m

#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_HEARTBEAT=m
# CONFIG_INFINIBAND is not set
CONFIG_EDAC=y

#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_MM_EDAC=m
CONFIG_EDAC_E752X=m
CONFIG_EDAC_I82975X=m
CONFIG_EDAC_I3000=m
CONFIG_EDAC_I5000=m
CONFIG_RTC_LIB=m
CONFIG_RTC_CLASS=m

#
# Conflicting RTC option has been selected, check GEN_RTC and RTC
#

#
# 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 is not set

#
# 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=m
CONFIG_RTC_DRV_M41T80_WDT=y
CONFIG_RTC_DRV_S35390A=m

#
# SPI RTC drivers
#
CONFIG_RTC_DRV_MAX6902=m
CONFIG_RTC_DRV_R9701=m
CONFIG_RTC_DRV_RS5C348=m

#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=m
CONFIG_RTC_DRV_DS1511=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_STK17TA8=m
CONFIG_RTC_DRV_M48T86=m
CONFIG_RTC_DRV_M48T59=m
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_AUXDISPLAY is not set

#
# Userspace I/O
#
CONFIG_UIO=m
CONFIG_UIO_CIF=m

#
# 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=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4DEV_FS=m
CONFIG_EXT4DEV_FS_XATTR=y
CONFIG_EXT4DEV_FS_POSIX_ACL=y
CONFIG_EXT4DEV_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=m
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
CONFIG_XFS_QUOTA=y
CONFIG_XFS_SECURITY=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
CONFIG_GFS2_FS=m
CONFIG_GFS2_FS_LOCKING_NOLOCK=m
CONFIG_GFS2_FS_LOCKING_DLM=m
CONFIG_OCFS2_FS=m
CONFIG_OCFS2_DEBUG_MASKLOG=y
# CONFIG_OCFS2_DEBUG_FS is not set
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
# CONFIG_PRINT_QUOTA_WARNING is not set
CONFIG_QFMT_V1=m
CONFIG_QFMT_V2=m
CONFIG_QUOTACTL=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=m
CONFIG_GENERIC_ACL=y

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

#
# Miscellaneous filesystems
#
CONFIG_ADFS_FS=m
# CONFIG_ADFS_FS_RW is not set
CONFIG_AFFS_FS=m
CONFIG_ECRYPT_FS=m
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
CONFIG_BEFS_FS=m
# CONFIG_BEFS_DEBUG is not set
CONFIG_BFS_FS=m
CONFIG_EFS_FS=m
CONFIG_JFFS2_FS=m
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
# CONFIG_JFFS2_FS_WBUF_VERIFY is not set
# CONFIG_JFFS2_SUMMARY is not set
CONFIG_JFFS2_FS_XATTR=y
CONFIG_JFFS2_FS_POSIX_ACL=y
CONFIG_JFFS2_FS_SECURITY=y
# CONFIG_JFFS2_COMPRESSION_OPTIONS is not set
CONFIG_JFFS2_ZLIB=y
# CONFIG_JFFS2_LZO is not set
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
CONFIG_CRAMFS=y
CONFIG_VXFS_FS=m
CONFIG_MINIX_FS=m
CONFIG_HPFS_FS=m
CONFIG_QNX4FS_FS=m
CONFIG_ROMFS_FS=m
CONFIG_SYSV_FS=m
CONFIG_UFS_FS=m
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_UFS_DEBUG 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=m
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
CONFIG_NCP_FS=m
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
# CONFIG_NCPFS_SMALLDOS is not set
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
CONFIG_CODA_FS=m
# CONFIG_CODA_FS_OLD_API is not set
CONFIG_AFS_FS=m
# CONFIG_AFS_DEBUG is not set
CONFIG_9P_FS=m

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
CONFIG_ACORN_PARTITION=y
# CONFIG_ACORN_PARTITION_CUMANA is not set
# CONFIG_ACORN_PARTITION_EESOX is not set
CONFIG_ACORN_PARTITION_ICS=y
# CONFIG_ACORN_PARTITION_ADFS is not set
# CONFIG_ACORN_PARTITION_POWERTEC is not set
CONFIG_ACORN_PARTITION_RISCIX=y
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
CONFIG_ATARI_PARTITION=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
CONFIG_SGI_PARTITION=y
CONFIG_ULTRIX_PARTITION=y
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
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=y

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_SHIRQ=y
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
CONFIG_TIMER_STATS=y
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES 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_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_SAMPLES is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
CONFIG_DEBUG_RODATA=y
# CONFIG_DEBUG_RODATA_TEST is not set
# CONFIG_DEBUG_NX_TEST is not set
CONFIG_X86_MPPARSE=y
# CONFIG_IOMMU_DEBUG is not set
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
# CONFIG_IO_DELAY_0X80 is not set
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
CONFIG_IO_DELAY_NONE=y
CONFIG_DEFAULT_IO_DELAY_TYPE=3
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not set

#
# Security options
#
CONFIG_KEYS=y
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_NETWORK_XFRM=y
CONFIG_SECURITY_CAPABILITIES=y
CONFIG_SECURITY_FILE_CAPABILITIES=y
CONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR=0
CONFIG_XOR_BLOCKS=m
CONFIG_ASYNC_CORE=m
CONFIG_ASYNC_MEMCPY=m
CONFIG_ASYNC_XOR=m
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_SEQIV=m
CONFIG_CRYPTO_HASH=m
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_HMAC=m
CONFIG_CRYPTO_XCBC=m
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
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=m
CONFIG_CRYPTO_CTR=m
CONFIG_CRYPTO_GCM=m
CONFIG_CRYPTO_CCM=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_X86_64=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_X86_64=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=m
CONFIG_CRYPTO_SALSA20=m
CONFIG_CRYPTO_SALSA20_X86_64=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_CAMELLIA=m
CONFIG_CRYPTO_TEST=m
CONFIG_CRYPTO_AUTHENC=m
CONFIG_CRYPTO_LZO=m
CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO_DEV_HIFN_795X=m
CONFIG_CRYPTO_DEV_HIFN_795X_RNG=y
CONFIG_HAVE_KVM=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=m
CONFIG_KVM_INTEL=m
CONFIG_KVM_AMD=m
CONFIG_VIRTIO=m
CONFIG_VIRTIO_RING=m
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIO_BALLOON=m

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
CONFIG_CRC7=m
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_LZO_COMPRESS=m
CONFIG_LZO_DECOMPRESS=m
CONFIG_REED_SOLOMON=m
CONFIG_REED_SOLOMON_DEC16=y
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_CHECK_SIGNATURE=y

-- 
Meelis Roos (mroos@linux.ee)