All of lore.kernel.org
 help / color / mirror / Atom feed
* mmotm 2010-12-02-16-34 uploaded
@ 2010-12-03  0:34 ` akpm
  0 siblings, 0 replies; 77+ messages in thread
From: akpm @ 2010-12-03  0:34 UTC (permalink / raw)
  To: mm-commits, linux-kernel, linux-mm, linux-fsdevel

The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to

   http://userweb.kernel.org/~akpm/mmotm/

and will soon be available at

   git://zen-kernel.org/kernel/mmotm.git

It contains the following patches against 2.6.37-rc4:

origin.patch
mm-hugetlbc-avoid-double-unlock_page-in-hugetlb_fault.patch
mm-mempolicyc-add-rcu-read-lock-to-protect-pid-structure.patch
vmstat-fix-dirty-threshold-ordering.patch
leds-fix-up-dependencies.patch
reiserfs-dont-acquire-lock-recursively-in-reiserfs_acl_chmod.patch
cs5535-gpio-apply-cs5536-errata-workaround-for-gpios.patch
vmalloc-eagerly-clear-ptes-on-vunmap.patch
documentation-filesystems-vfstxt-fix-repeasepage-description.patch
mem-hotplug-introduce-unlock_memory_hotplug.patch
ksm-annotate-ksm_thread_mutex-is-no-deadlock-source.patch
do_exit-make-sure-we-run-with-get_fs-==-user_ds.patch
linux-next.patch
linux-next-git-rejects.patch
next-remove-localversion.patch
i-need-old-gcc.patch
aesni-nfg.patch
arch-alpha-kernel-systblss-remove-debug-check.patch
memblock-fix-memblock_is_region_memory.patch
mm-vmap-area-cache.patch
arch-arm-plat-omap-iovmmc-fix-end-address-of-vm-area-comparation-in-alloc_iovm_area.patch
backlight-fix-88pm860x_bl-macro-collision.patch
cciss-fix-botched-tag-masking-for-scsi-tape-commands.patch
hpsa-fix-redefinition-of-pci_device_id_cissf.patch
acerhdf-add-support-for-aspire-1410-bios-v13314.patch
arch-x86-kernel-apic-io_apicc-fix-warning.patch
x86-olpc-add-xo-1-suspend-resume-support.patch
x86-olpc-add-xo-1-suspend-resume-support-fix.patch
arch-arm-mach-tegra-timerc-separate-clocksource-and-sched_clock.patch
fs-btrfs-inodec-eliminate-memory-leak.patch
btrfs-dont-dereference-extent_mapping-if-null.patch
cifs-dont-overwrite-dentry-name-in-d_revalidate.patch
cpufreq-fix-ondemand-governor-powersave_bias-execution-time-misuse.patch
drivers-dma-use-the-ccflag-y-instead-of-extra_cflags.patch
drivers-dma-ioat-use-the-ccflag-y-instead-of-extra_cflags.patch
jfs-dont-overwrite-dentry-name-in-d_revalidate.patch
debugfs-remove-module_exit.patch
drivers-gpu-drm-radeon-atomc-fix-warning.patch
irq-use-per_cpu-kstat_irqs.patch
irq-use-per_cpu-kstat_irqs-checkpatch-fixes.patch
timers-use-this_cpu_read.patch
headers_check-better-search-for-functions-in-headers.patch
headers_check-better-search-for-functions-in-headers-fix.patch
headers_check-better-search-for-functions-in-headers-fix-checkpatch-fixes.patch
drivers-leds-leds-lp5521c-fix-potential-buffer-overflow.patch
leds-route-kbd-leds-through-the-generic-leds-layer.patch
mips-enable-arch_dma_addr_t_64bit-with-highmem-64bit_phys_addr-64bit.patch
isdn-capi-unregister-capictr-notifier-after-init-failure.patch
isdn-capi-make-kcapi-use-a-separate-workqueue.patch
drivers-video-backlight-l4f00242t03c-make-1-bit-signed-field-unsigned.patch
drivers-video-backlight-l4f00242t03c-full-implement-fb-power-states-for-this-lcd.patch
drivers-video-backlight-l4f00242t03c-prevent-unbalanced-calls-to-regulator-enable-disable.patch
btusb-patch-add_apple_macbookpro62.patch
atmel_serial-fix-rts-high-after-initialization-in-rs485-mode.patch
atmel_serial-fix-rts-high-after-initialization-in-rs485-mode-fix.patch
drivers-message-fusion-mptsasc-fix-warning.patch
scsi-fix-a-header-to-include-linux-typesh.patch
drivers-block-makefile-replace-the-use-of-module-objs-with-module-y.patch
drivers-block-aoe-makefile-replace-the-use-of-module-objs-with-module-y.patch
vfs-remove-a-warning-on-open_fmode.patch
vfs-add-__fmode_exec.patch
n_hdlc-fix-read-and-write-locking.patch
n_hdlc-fix-read-and-write-locking-update.patch
mm.patch
mm-page-allocator-adjust-the-per-cpu-counter-threshold-when-memory-is-low.patch
mm-vmstat-use-a-single-setter-function-and-callback-for-adjusting-percpu-thresholds.patch
mm-vmstat-use-a-single-setter-function-and-callback-for-adjusting-percpu-thresholds-fix.patch
mm-vmstat-use-a-single-setter-function-and-callback-for-adjusting-percpu-thresholds-update.patch
mm-vmstat-use-a-single-setter-function-and-callback-for-adjusting-percpu-thresholds-fix-set_pgdat_percpu_threshold-dont-use-for_each_online_cpu.patch
writeback-integrated-background-writeback-work.patch
writeback-trace-wakeup-event-for-background-writeback.patch
writeback-stop-background-kupdate-works-from-livelocking-other-works.patch
writeback-stop-background-kupdate-works-from-livelocking-other-works-update.patch
writeback-avoid-livelocking-wb_sync_all-writeback.patch
writeback-avoid-livelocking-wb_sync_all-writeback-update.patch
writeback-check-skipped-pages-on-wb_sync_all.patch
writeback-check-skipped-pages-on-wb_sync_all-update.patch
writeback-check-skipped-pages-on-wb_sync_all-update-fix.patch
writeback-io-less-balance_dirty_pages.patch
writeback-consolidate-variable-names-in-balance_dirty_pages.patch
writeback-per-task-rate-limit-on-balance_dirty_pages.patch
writeback-per-task-rate-limit-on-balance_dirty_pages-fix.patch
writeback-prevent-duplicate-balance_dirty_pages_ratelimited-calls.patch
writeback-account-per-bdi-accumulated-written-pages.patch
writeback-bdi-write-bandwidth-estimation.patch
writeback-bdi-write-bandwidth-estimation-fix.patch
writeback-show-bdi-write-bandwidth-in-debugfs.patch
writeback-quit-throttling-when-bdi-dirty-pages-dropped-low.patch
writeback-reduce-per-bdi-dirty-threshold-ramp-up-time.patch
writeback-make-reasonable-gap-between-the-dirty-background-thresholds.patch
writeback-scale-down-max-throttle-bandwidth-on-concurrent-dirtiers.patch
writeback-add-trace-event-for-balance_dirty_pages.patch
writeback-make-nr_to_write-a-per-file-limit.patch
writeback-make-nr_to_write-a-per-file-limit-fix.patch
sync_inode_metadata-fix-comment.patch
mm-page-writebackc-fix-__set_page_dirty_no_writeback-return-value.patch
vmscan-factor-out-kswapd-sleeping-logic-from-kswapd.patch
mm-find_get_pages_contig-fixlet.patch
fs-mpagec-consolidate-code.patch
fs-mpagec-consolidate-code-checkpatch-fixes.patch
mm-convert-sprintf_symbol-to-%ps.patch
mm-smaps-export-mlock-information.patch
mm-compaction-add-trace-events-for-memory-compaction-activity.patch
mm-vmscan-convert-lumpy_mode-into-a-bitmask.patch
mm-vmscan-reclaim-order-0-and-use-compaction-instead-of-lumpy-reclaim.patch
mm-vmscan-reclaim-order-0-and-use-compaction-instead-of-lumpy-reclaim-fix.patch
mm-migration-allow-migration-to-operate-asynchronously-and-avoid-synchronous-compaction-in-the-faster-path.patch
mm-migration-allow-migration-to-operate-asynchronously-and-avoid-synchronous-compaction-in-the-faster-path-fix.patch
mm-migration-cleanup-migrate_pages-api-by-matching-types-for-offlining-and-sync.patch
mm-compaction-perform-a-faster-migration-scan-when-migrating-asynchronously.patch
mm-vmscan-rename-lumpy_mode-to-reclaim_mode.patch
mm-deactivate-invalidated-pages.patch
mm-deactivate-invalidated-pages-fix.patch
mm-remove-unused-get_vm_area_node.patch
mm-remove-gfp-mask-from-pcpu_get_vm_areas.patch
mm-unify-module_alloc-code-for-vmalloc.patch
oom-allow-a-non-cap_sys_resource-proces-to-oom_score_adj-down.patch
mm-clear-pageerror-bit-in-msync-fsync.patch
do_wp_page-remove-the-reuse-flag.patch
do_wp_page-clarify-dirty_page-handling.patch
mlock-avoid-dirtying-pages-and-triggering-writeback.patch
frv-duplicate-output_buffer-of-e03.patch
frv-duplicate-output_buffer-of-e03-checkpatch-fixes.patch
hpet-factor-timer-allocate-from-open.patch
um-mark-config_highmem-as-broken.patch
arch-um-drivers-linec-safely-iterate-over-list-of-winch-handlers.patch
kmsg_dump-constrain-mtdoops-and-ramoops-to-perform-their-actions-only-for-kmsg_dump_panic.patch
kmsg_dump-add-kmsg_dump-calls-to-the-reboot-halt-poweroff-and-emergency_restart-paths.patch
set_rtc_mmss-show-warning-message-only-once.patch
include-linux-kernelh-abs-fix-handling-of-32-bit-unsigneds-on-64-bit.patch
include-linux-kernelh-abs-fix-handling-of-32-bit-unsigneds-on-64-bit-fix.patch
add-the-common-dma_addr_t-typedef-to-include-linux-typesh.patch
toshibah-hide-a-function-prototypes-behind-__kernel__-macro.patch
dca-remove-unneeded-null-check.patch
printk-use-rcu-to-prevent-potential-lock-contention-in-kmsg_dump.patch
scripts-get_maintainerpl-make-rolestats-the-default.patch
scripts-get_maintainerpl-use-git-fallback-more-often.patch
percpucounter-optimize-__percpu_counter_add-a-bit-through-the-use-of-this_cpu-operations.patch
drivers-mmc-host-omapc-use-resource_size.patch
drivers-mmc-host-omap_hsmmcc-use-resource_size.patch
scripts-checkpatchpl-add-check-for-multiple-terminating-semicolons-and-casts-of-vmalloc.patch
checkpatchpl-fix-cast-detection.patch
fs-select-fix-information-leak-to-userspace.patch
fs-select-fix-information-leak-to-userspace-fix.patch
epoll-convert-max_user_watches-to-long.patch
binfmt_elf-cleanups.patch
drivers-rtc-rtc-omapc-fix-a-memory-leak.patch
rtc-add-real-time-clock-driver-for-nvidia-tegra.patch
drivers-gpio-cs5535-gpioc-add-some-additional-cs5535-specific-gpio-functionality.patch
drivers-staging-olpc_dcon-convert-to-new-cs5535-gpio-api.patch
cyber2000fb-avoid-palette-corruption-at-higher-clocks.patch
jbd-remove-dependency-on-__gfp_nofail.patch
memcg-add-page_cgroup-flags-for-dirty-page-tracking.patch
memcg-document-cgroup-dirty-memory-interfaces.patch
memcg-document-cgroup-dirty-memory-interfaces-fix.patch
memcg-create-extensible-page-stat-update-routines.patch
memcg-add-lock-to-synchronize-page-accounting-and-migration.patch
memcg-fix-unit-mismatch-in-memcg-oom-limit-calculation.patch
memcg-use-zalloc-rather-than-mallocmemset.patch
fs-proc-basec-kernel-latencytopc-convert-sprintf_symbol-to-%ps.patch
fs-proc-basec-kernel-latencytopc-convert-sprintf_symbol-to-%ps-checkpatch-fixes.patch
proc-use-unsigned-long-inside-proc-statm.patch
proc-use-seq_puts-seq_putc-where-possible.patch
exec_domain-establish-a-linux32-domain-on-config_compat-systems.patch
rapidio-use-common-destid-storage-for-endpoints-and-switches.patch
rapidio-integrate-rio_switch-into-rio_dev.patch
fs-execc-provide-the-correct-process-pid-to-the-pipe-helper.patch
nfc-driver-for-nxp-semiconductors-pn544-nfc-chip.patch
nfc-driver-for-nxp-semiconductors-pn544-nfc-chip-update.patch
remove-dma64_addr_t.patch
pps-trivial-fixes.patch
pps-declare-variables-where-they-are-used-in-switch.patch
pps-fix-race-in-pps_fetch-handler.patch
pps-unify-timestamp-gathering.patch
pps-access-pps-device-by-direct-pointer.patch
pps-convert-printk-pr_-to-dev_.patch
pps-move-idr-stuff-to-ppsc.patch
pps-add-async-pps-event-handler.patch
pps-add-async-pps-event-handler-fix.patch
pps-dont-disable-interrupts-when-using-spin-locks.patch
pps-use-bug_on-for-kernel-api-safety-checks.patch
pps-simplify-conditions-a-bit.patch
ntp-add-hardpps-implementation.patch
pps-capture-monotonic_raw-timestamps-as-well.patch
pps-add-kernel-consumer-support.patch
pps-add-parallel-port-pps-client.patch
pps-add-parallel-port-pps-signal-generator.patch
memstick-a-few-changes-to-core.patch
memstick-add-support-for-legacy-memorysticks.patch
memstick-add-driver-for-ricoh-r5c592-card-reader.patch
memstick-add-driver-for-ricoh-r5c592-card-reader-fix.patch
memstick-core-fix-device_register-error-handling.patch
w1-ds2423-counter-driver-and-documentation.patch
w1-ds2423-counter-driver-and-documentation-fix.patch
cramfs-hide-function-prototypes-behind-__kernel__-macro.patch
romfs-have-romfs_fsh-pull-in-necessary-headers.patch
decompressors-add-missing-init-ie-__init.patch
decompressors-get-rid-of-set_error_fn-macro.patch
decompressors-include-linux-slabh-in-linux-decompress-mmh.patch
decompressors-remove-unused-function-from-lib-decompress_unlzmac.patch
decompressors-fix-header-validation-in-decompress_unlzmac.patch
decompressors-check-for-read-errors-in-decompress_unlzmac.patch
decompressors-check-for-write-errors-in-decompress_unlzmac.patch
decompressors-validate-match-distance-in-decompress_unlzmac.patch
decompressors-check-for-write-errors-in-decompress_unlzoc.patch
decompressors-check-input-size-in-decompress_unlzoc.patch
decompressors-fix-callback-to-callback-mode-in-decompress_unlzoc.patch
bitops-merge-little-and-big-endian-definisions-in-asm-generic-bitops-leh.patch
bitops-rename-generic-little-endian-bitops-functions.patch
s390-introduce-little-endian-bitops.patch
arm-introduce-little-endian-bitops.patch
m68k-introduce-little-endian-bitops.patch
bitops-introduce-config_generic_find_le_bit.patch
m68knommu-introduce-little-endian-bitops.patch
m68knommu-introduce-little-endian-bitops-build-fix.patch
bitops-introduce-little-endian-bitops-for-most-architectures.patch
rds-stop-including-asm-generic-bitops-leh.patch
kvm-stop-including-asm-generic-bitops-leh.patch
asm-generic-use-little-endian-bitops.patch
ext3-use-little-endian-bitops.patch
ext4-use-little-endian-bitops.patch
ocfs2-use-little-endian-bitops.patch
nilfs2-use-little-endian-bitops.patch
reiserfs-use-little-endian-bitops.patch
udf-use-little-endian-bitops.patch
ufs-use-little-endian-bitops.patch
md-use-little-endian-bit-operations.patch
dm-use-little-endian-bit-operations.patch
bitops-remove-ext2-non-atomic-bitops-from-asm-bitopsh.patch
m68k-remove-inline-asm-from-minix_find_first_zero_bit.patch
bitops-remove-minix-bitops-from-asm-bitopsh.patch
bitops-use-find_first_zero_bit-instead-of-find_next_zero_bitaddr-size-0.patch
make-sure-nobodys-leaking-resources.patch
journal_add_journal_head-debug.patch
releasing-resources-with-children.patch
make-frame_pointer-default=y.patch
mutex-subsystem-synchro-test-module.patch
mutex-subsystem-synchro-test-module-add-missing-header-file.patch
slab-leaks3-default-y.patch
put_bh-debug.patch
add-debugging-aid-for-memory-initialisation-problems.patch
workaround-for-a-pci-restoring-bug.patch
prio_tree-debugging-patch.patch
single_open-seq_release-leak-diagnostics.patch
add-a-refcount-check-in-dput.patch
getblk-handle-2tb-devices.patch
memblock-add-input-size-checking-to-memblock_find_region.patch
memblock-add-input-size-checking-to-memblock_find_region-fix.patch

^ permalink raw reply	[flat|nested] 77+ messages in thread

* mmotm 2010-12-02-16-34 uploaded
@ 2010-12-03  0:34 ` akpm
  0 siblings, 0 replies; 77+ messages in thread
From: akpm @ 2010-12-03  0:34 UTC (permalink / raw)
  To: mm-commits, linux-kernel, linux-mm, linux-fsdevel

The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to

   http://userweb.kernel.org/~akpm/mmotm/

and will soon be available at

   git://zen-kernel.org/kernel/mmotm.git

It contains the following patches against 2.6.37-rc4:

origin.patch
mm-hugetlbc-avoid-double-unlock_page-in-hugetlb_fault.patch
mm-mempolicyc-add-rcu-read-lock-to-protect-pid-structure.patch
vmstat-fix-dirty-threshold-ordering.patch
leds-fix-up-dependencies.patch
reiserfs-dont-acquire-lock-recursively-in-reiserfs_acl_chmod.patch
cs5535-gpio-apply-cs5536-errata-workaround-for-gpios.patch
vmalloc-eagerly-clear-ptes-on-vunmap.patch
documentation-filesystems-vfstxt-fix-repeasepage-description.patch
mem-hotplug-introduce-unlock_memory_hotplug.patch
ksm-annotate-ksm_thread_mutex-is-no-deadlock-source.patch
do_exit-make-sure-we-run-with-get_fs-==-user_ds.patch
linux-next.patch
linux-next-git-rejects.patch
next-remove-localversion.patch
i-need-old-gcc.patch
aesni-nfg.patch
arch-alpha-kernel-systblss-remove-debug-check.patch
memblock-fix-memblock_is_region_memory.patch
mm-vmap-area-cache.patch
arch-arm-plat-omap-iovmmc-fix-end-address-of-vm-area-comparation-in-alloc_iovm_area.patch
backlight-fix-88pm860x_bl-macro-collision.patch
cciss-fix-botched-tag-masking-for-scsi-tape-commands.patch
hpsa-fix-redefinition-of-pci_device_id_cissf.patch
acerhdf-add-support-for-aspire-1410-bios-v13314.patch
arch-x86-kernel-apic-io_apicc-fix-warning.patch
x86-olpc-add-xo-1-suspend-resume-support.patch
x86-olpc-add-xo-1-suspend-resume-support-fix.patch
arch-arm-mach-tegra-timerc-separate-clocksource-and-sched_clock.patch
fs-btrfs-inodec-eliminate-memory-leak.patch
btrfs-dont-dereference-extent_mapping-if-null.patch
cifs-dont-overwrite-dentry-name-in-d_revalidate.patch
cpufreq-fix-ondemand-governor-powersave_bias-execution-time-misuse.patch
drivers-dma-use-the-ccflag-y-instead-of-extra_cflags.patch
drivers-dma-ioat-use-the-ccflag-y-instead-of-extra_cflags.patch
jfs-dont-overwrite-dentry-name-in-d_revalidate.patch
debugfs-remove-module_exit.patch
drivers-gpu-drm-radeon-atomc-fix-warning.patch
irq-use-per_cpu-kstat_irqs.patch
irq-use-per_cpu-kstat_irqs-checkpatch-fixes.patch
timers-use-this_cpu_read.patch
headers_check-better-search-for-functions-in-headers.patch
headers_check-better-search-for-functions-in-headers-fix.patch
headers_check-better-search-for-functions-in-headers-fix-checkpatch-fixes.patch
drivers-leds-leds-lp5521c-fix-potential-buffer-overflow.patch
leds-route-kbd-leds-through-the-generic-leds-layer.patch
mips-enable-arch_dma_addr_t_64bit-with-highmem-64bit_phys_addr-64bit.patch
isdn-capi-unregister-capictr-notifier-after-init-failure.patch
isdn-capi-make-kcapi-use-a-separate-workqueue.patch
drivers-video-backlight-l4f00242t03c-make-1-bit-signed-field-unsigned.patch
drivers-video-backlight-l4f00242t03c-full-implement-fb-power-states-for-this-lcd.patch
drivers-video-backlight-l4f00242t03c-prevent-unbalanced-calls-to-regulator-enable-disable.patch
btusb-patch-add_apple_macbookpro62.patch
atmel_serial-fix-rts-high-after-initialization-in-rs485-mode.patch
atmel_serial-fix-rts-high-after-initialization-in-rs485-mode-fix.patch
drivers-message-fusion-mptsasc-fix-warning.patch
scsi-fix-a-header-to-include-linux-typesh.patch
drivers-block-makefile-replace-the-use-of-module-objs-with-module-y.patch
drivers-block-aoe-makefile-replace-the-use-of-module-objs-with-module-y.patch
vfs-remove-a-warning-on-open_fmode.patch
vfs-add-__fmode_exec.patch
n_hdlc-fix-read-and-write-locking.patch
n_hdlc-fix-read-and-write-locking-update.patch
mm.patch
mm-page-allocator-adjust-the-per-cpu-counter-threshold-when-memory-is-low.patch
mm-vmstat-use-a-single-setter-function-and-callback-for-adjusting-percpu-thresholds.patch
mm-vmstat-use-a-single-setter-function-and-callback-for-adjusting-percpu-thresholds-fix.patch
mm-vmstat-use-a-single-setter-function-and-callback-for-adjusting-percpu-thresholds-update.patch
mm-vmstat-use-a-single-setter-function-and-callback-for-adjusting-percpu-thresholds-fix-set_pgdat_percpu_threshold-dont-use-for_each_online_cpu.patch
writeback-integrated-background-writeback-work.patch
writeback-trace-wakeup-event-for-background-writeback.patch
writeback-stop-background-kupdate-works-from-livelocking-other-works.patch
writeback-stop-background-kupdate-works-from-livelocking-other-works-update.patch
writeback-avoid-livelocking-wb_sync_all-writeback.patch
writeback-avoid-livelocking-wb_sync_all-writeback-update.patch
writeback-check-skipped-pages-on-wb_sync_all.patch
writeback-check-skipped-pages-on-wb_sync_all-update.patch
writeback-check-skipped-pages-on-wb_sync_all-update-fix.patch
writeback-io-less-balance_dirty_pages.patch
writeback-consolidate-variable-names-in-balance_dirty_pages.patch
writeback-per-task-rate-limit-on-balance_dirty_pages.patch
writeback-per-task-rate-limit-on-balance_dirty_pages-fix.patch
writeback-prevent-duplicate-balance_dirty_pages_ratelimited-calls.patch
writeback-account-per-bdi-accumulated-written-pages.patch
writeback-bdi-write-bandwidth-estimation.patch
writeback-bdi-write-bandwidth-estimation-fix.patch
writeback-show-bdi-write-bandwidth-in-debugfs.patch
writeback-quit-throttling-when-bdi-dirty-pages-dropped-low.patch
writeback-reduce-per-bdi-dirty-threshold-ramp-up-time.patch
writeback-make-reasonable-gap-between-the-dirty-background-thresholds.patch
writeback-scale-down-max-throttle-bandwidth-on-concurrent-dirtiers.patch
writeback-add-trace-event-for-balance_dirty_pages.patch
writeback-make-nr_to_write-a-per-file-limit.patch
writeback-make-nr_to_write-a-per-file-limit-fix.patch
sync_inode_metadata-fix-comment.patch
mm-page-writebackc-fix-__set_page_dirty_no_writeback-return-value.patch
vmscan-factor-out-kswapd-sleeping-logic-from-kswapd.patch
mm-find_get_pages_contig-fixlet.patch
fs-mpagec-consolidate-code.patch
fs-mpagec-consolidate-code-checkpatch-fixes.patch
mm-convert-sprintf_symbol-to-%ps.patch
mm-smaps-export-mlock-information.patch
mm-compaction-add-trace-events-for-memory-compaction-activity.patch
mm-vmscan-convert-lumpy_mode-into-a-bitmask.patch
mm-vmscan-reclaim-order-0-and-use-compaction-instead-of-lumpy-reclaim.patch
mm-vmscan-reclaim-order-0-and-use-compaction-instead-of-lumpy-reclaim-fix.patch
mm-migration-allow-migration-to-operate-asynchronously-and-avoid-synchronous-compaction-in-the-faster-path.patch
mm-migration-allow-migration-to-operate-asynchronously-and-avoid-synchronous-compaction-in-the-faster-path-fix.patch
mm-migration-cleanup-migrate_pages-api-by-matching-types-for-offlining-and-sync.patch
mm-compaction-perform-a-faster-migration-scan-when-migrating-asynchronously.patch
mm-vmscan-rename-lumpy_mode-to-reclaim_mode.patch
mm-deactivate-invalidated-pages.patch
mm-deactivate-invalidated-pages-fix.patch
mm-remove-unused-get_vm_area_node.patch
mm-remove-gfp-mask-from-pcpu_get_vm_areas.patch
mm-unify-module_alloc-code-for-vmalloc.patch
oom-allow-a-non-cap_sys_resource-proces-to-oom_score_adj-down.patch
mm-clear-pageerror-bit-in-msync-fsync.patch
do_wp_page-remove-the-reuse-flag.patch
do_wp_page-clarify-dirty_page-handling.patch
mlock-avoid-dirtying-pages-and-triggering-writeback.patch
frv-duplicate-output_buffer-of-e03.patch
frv-duplicate-output_buffer-of-e03-checkpatch-fixes.patch
hpet-factor-timer-allocate-from-open.patch
um-mark-config_highmem-as-broken.patch
arch-um-drivers-linec-safely-iterate-over-list-of-winch-handlers.patch
kmsg_dump-constrain-mtdoops-and-ramoops-to-perform-their-actions-only-for-kmsg_dump_panic.patch
kmsg_dump-add-kmsg_dump-calls-to-the-reboot-halt-poweroff-and-emergency_restart-paths.patch
set_rtc_mmss-show-warning-message-only-once.patch
include-linux-kernelh-abs-fix-handling-of-32-bit-unsigneds-on-64-bit.patch
include-linux-kernelh-abs-fix-handling-of-32-bit-unsigneds-on-64-bit-fix.patch
add-the-common-dma_addr_t-typedef-to-include-linux-typesh.patch
toshibah-hide-a-function-prototypes-behind-__kernel__-macro.patch
dca-remove-unneeded-null-check.patch
printk-use-rcu-to-prevent-potential-lock-contention-in-kmsg_dump.patch
scripts-get_maintainerpl-make-rolestats-the-default.patch
scripts-get_maintainerpl-use-git-fallback-more-often.patch
percpucounter-optimize-__percpu_counter_add-a-bit-through-the-use-of-this_cpu-operations.patch
drivers-mmc-host-omapc-use-resource_size.patch
drivers-mmc-host-omap_hsmmcc-use-resource_size.patch
scripts-checkpatchpl-add-check-for-multiple-terminating-semicolons-and-casts-of-vmalloc.patch
checkpatchpl-fix-cast-detection.patch
fs-select-fix-information-leak-to-userspace.patch
fs-select-fix-information-leak-to-userspace-fix.patch
epoll-convert-max_user_watches-to-long.patch
binfmt_elf-cleanups.patch
drivers-rtc-rtc-omapc-fix-a-memory-leak.patch
rtc-add-real-time-clock-driver-for-nvidia-tegra.patch
drivers-gpio-cs5535-gpioc-add-some-additional-cs5535-specific-gpio-functionality.patch
drivers-staging-olpc_dcon-convert-to-new-cs5535-gpio-api.patch
cyber2000fb-avoid-palette-corruption-at-higher-clocks.patch
jbd-remove-dependency-on-__gfp_nofail.patch
memcg-add-page_cgroup-flags-for-dirty-page-tracking.patch
memcg-document-cgroup-dirty-memory-interfaces.patch
memcg-document-cgroup-dirty-memory-interfaces-fix.patch
memcg-create-extensible-page-stat-update-routines.patch
memcg-add-lock-to-synchronize-page-accounting-and-migration.patch
memcg-fix-unit-mismatch-in-memcg-oom-limit-calculation.patch
memcg-use-zalloc-rather-than-mallocmemset.patch
fs-proc-basec-kernel-latencytopc-convert-sprintf_symbol-to-%ps.patch
fs-proc-basec-kernel-latencytopc-convert-sprintf_symbol-to-%ps-checkpatch-fixes.patch
proc-use-unsigned-long-inside-proc-statm.patch
proc-use-seq_puts-seq_putc-where-possible.patch
exec_domain-establish-a-linux32-domain-on-config_compat-systems.patch
rapidio-use-common-destid-storage-for-endpoints-and-switches.patch
rapidio-integrate-rio_switch-into-rio_dev.patch
fs-execc-provide-the-correct-process-pid-to-the-pipe-helper.patch
nfc-driver-for-nxp-semiconductors-pn544-nfc-chip.patch
nfc-driver-for-nxp-semiconductors-pn544-nfc-chip-update.patch
remove-dma64_addr_t.patch
pps-trivial-fixes.patch
pps-declare-variables-where-they-are-used-in-switch.patch
pps-fix-race-in-pps_fetch-handler.patch
pps-unify-timestamp-gathering.patch
pps-access-pps-device-by-direct-pointer.patch
pps-convert-printk-pr_-to-dev_.patch
pps-move-idr-stuff-to-ppsc.patch
pps-add-async-pps-event-handler.patch
pps-add-async-pps-event-handler-fix.patch
pps-dont-disable-interrupts-when-using-spin-locks.patch
pps-use-bug_on-for-kernel-api-safety-checks.patch
pps-simplify-conditions-a-bit.patch
ntp-add-hardpps-implementation.patch
pps-capture-monotonic_raw-timestamps-as-well.patch
pps-add-kernel-consumer-support.patch
pps-add-parallel-port-pps-client.patch
pps-add-parallel-port-pps-signal-generator.patch
memstick-a-few-changes-to-core.patch
memstick-add-support-for-legacy-memorysticks.patch
memstick-add-driver-for-ricoh-r5c592-card-reader.patch
memstick-add-driver-for-ricoh-r5c592-card-reader-fix.patch
memstick-core-fix-device_register-error-handling.patch
w1-ds2423-counter-driver-and-documentation.patch
w1-ds2423-counter-driver-and-documentation-fix.patch
cramfs-hide-function-prototypes-behind-__kernel__-macro.patch
romfs-have-romfs_fsh-pull-in-necessary-headers.patch
decompressors-add-missing-init-ie-__init.patch
decompressors-get-rid-of-set_error_fn-macro.patch
decompressors-include-linux-slabh-in-linux-decompress-mmh.patch
decompressors-remove-unused-function-from-lib-decompress_unlzmac.patch
decompressors-fix-header-validation-in-decompress_unlzmac.patch
decompressors-check-for-read-errors-in-decompress_unlzmac.patch
decompressors-check-for-write-errors-in-decompress_unlzmac.patch
decompressors-validate-match-distance-in-decompress_unlzmac.patch
decompressors-check-for-write-errors-in-decompress_unlzoc.patch
decompressors-check-input-size-in-decompress_unlzoc.patch
decompressors-fix-callback-to-callback-mode-in-decompress_unlzoc.patch
bitops-merge-little-and-big-endian-definisions-in-asm-generic-bitops-leh.patch
bitops-rename-generic-little-endian-bitops-functions.patch
s390-introduce-little-endian-bitops.patch
arm-introduce-little-endian-bitops.patch
m68k-introduce-little-endian-bitops.patch
bitops-introduce-config_generic_find_le_bit.patch
m68knommu-introduce-little-endian-bitops.patch
m68knommu-introduce-little-endian-bitops-build-fix.patch
bitops-introduce-little-endian-bitops-for-most-architectures.patch
rds-stop-including-asm-generic-bitops-leh.patch
kvm-stop-including-asm-generic-bitops-leh.patch
asm-generic-use-little-endian-bitops.patch
ext3-use-little-endian-bitops.patch
ext4-use-little-endian-bitops.patch
ocfs2-use-little-endian-bitops.patch
nilfs2-use-little-endian-bitops.patch
reiserfs-use-little-endian-bitops.patch
udf-use-little-endian-bitops.patch
ufs-use-little-endian-bitops.patch
md-use-little-endian-bit-operations.patch
dm-use-little-endian-bit-operations.patch
bitops-remove-ext2-non-atomic-bitops-from-asm-bitopsh.patch
m68k-remove-inline-asm-from-minix_find_first_zero_bit.patch
bitops-remove-minix-bitops-from-asm-bitopsh.patch
bitops-use-find_first_zero_bit-instead-of-find_next_zero_bitaddr-size-0.patch
make-sure-nobodys-leaking-resources.patch
journal_add_journal_head-debug.patch
releasing-resources-with-children.patch
make-frame_pointer-default=y.patch
mutex-subsystem-synchro-test-module.patch
mutex-subsystem-synchro-test-module-add-missing-header-file.patch
slab-leaks3-default-y.patch
put_bh-debug.patch
add-debugging-aid-for-memory-initialisation-problems.patch
workaround-for-a-pci-restoring-bug.patch
prio_tree-debugging-patch.patch
single_open-seq_release-leak-diagnostics.patch
add-a-refcount-check-in-dput.patch
getblk-handle-2tb-devices.patch
memblock-add-input-size-checking-to-memblock_find_region.patch
memblock-add-input-size-checking-to-memblock_find_region-fix.patch

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: mmotm 2010-12-02-16-34 uploaded (acpi_video)
  2010-12-03  0:34 ` akpm
  (?)
@ 2010-12-03 17:33 ` Randy Dunlap
  -1 siblings, 0 replies; 77+ messages in thread
From: Randy Dunlap @ 2010-12-03 17:33 UTC (permalink / raw)
  To: linux-kernel, linux-acpi, lenb; +Cc: akpm

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

On Thu, 02 Dec 2010 16:34:54 -0800 akpm@linux-foundation.org wrote:

> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> 
>    http://userweb.kernel.org/~akpm/mmotm/
> 
> and will soon be available at
> 
>    git://zen-kernel.org/kernel/mmotm.git
> 
> It contains the following patches against 2.6.37-rc4:


drivers/built-in.o: In function `acpi_video_bus_put_one_device':
video.c:(.text+0x9fd9b): undefined reference to `video_output_unregister'
drivers/built-in.o: In function `acpi_video_device_find_cap':
video.c:(.text+0xa0c4d): undefined reference to `video_output_register'


kernel .config file is attached.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

[-- Attachment #2: config-r9476 --]
[-- Type: application/octet-stream, Size: 68300 bytes --]

#
# Automatically generated make config: don't edit
# Linux/i386 2.6.37-rc4-mm1 Kernel Configuration
# Thu Dec  2 17:27:42 2010
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf32-i386"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
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_MMU=y
CONFIG_ZONE_DMA=y
# CONFIG_NEED_DMA_MAP_STATE is not set
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
# CONFIG_GENERIC_TIME_VSYSCALL is not set
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
# CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
# CONFIG_ZONE_DMA32 is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_X86_32_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_X86_32_LAZY_GS=y
CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-ecx -fcall-saved-edx"
CONFIG_KTIME_SCALAR=y
CONFIG_ARCH_CPU_PROBE_RELEASE=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_CONSTRUCTORS=y
CONFIG_HAVE_IRQ_WORK=y
CONFIG_IRQ_WORK=y

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_LZO=y
# CONFIG_KERNEL_GZIP is not set
CONFIG_KERNEL_BZIP2=y
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_SWAP is not set
# CONFIG_SYSVIPC is not set
# CONFIG_POSIX_MQUEUE is not set
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
# CONFIG_TASKSTATS is not set
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y
CONFIG_HAVE_GENERIC_HARDIRQS=y

#
# IRQ subsystem
#
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
# CONFIG_GENERIC_HARDIRQS_NO_DEPRECATED is not set
CONFIG_HAVE_SPARSE_IRQ=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
# CONFIG_AUTO_IRQ_AFFINITY is not set
# CONFIG_IRQ_PER_CPU is not set
# CONFIG_HARDIRQS_SW_RESEND is not set
# CONFIG_SPARSE_IRQ is not set

#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_PREEMPT_RCU is not set
CONFIG_RCU_TRACE=y
CONFIG_RCU_FANOUT=32
CONFIG_RCU_FANOUT_EXACT=y
# CONFIG_RCU_FAST_NO_HZ is not set
CONFIG_TREE_RCU_TRACE=y
CONFIG_IKCONFIG=y
# CONFIG_IKCONFIG_PROC is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_CGROUP_NS is not set
CONFIG_CGROUP_FREEZER=y
# CONFIG_CGROUP_DEVICE is not set
CONFIG_CPUSETS=y
# CONFIG_PROC_PID_CPUSET is not set
CONFIG_CGROUP_CPUACCT=y
# CONFIG_RESOURCE_COUNTERS is not set
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
# CONFIG_BLK_CGROUP is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_USER_NS=y
# CONFIG_PID_NS is not set
CONFIG_NET_NS=y
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_LZO=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_HAVE_PERF_EVENTS=y

#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
CONFIG_PERF_COUNTERS=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_SLUB_DEBUG=y
CONFIG_COMPAT_BRK=y
# CONFIG_SLAB is not set
CONFIG_SLUB=y
CONFIG_PROFILING=y
# CONFIG_OPROFILE is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_JUMP_LABEL is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y
CONFIG_HAVE_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_PERF_EVENTS_NMI=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y

#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
# CONFIG_MODULES is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_LBDAF=y
CONFIG_BLK_DEV_BSG=y
CONFIG_BLK_DEV_INTEGRITY=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_DEADLINE is not set
# CONFIG_IOSCHED_CFQ is not set
CONFIG_DEFAULT_NOOP=y
CONFIG_DEFAULT_IOSCHED="noop"
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_PADATA=y
# CONFIG_INLINE_SPIN_TRYLOCK is not set
# CONFIG_INLINE_SPIN_TRYLOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK is not set
# CONFIG_INLINE_SPIN_LOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK_IRQ is not set
# CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set
CONFIG_INLINE_SPIN_UNLOCK=y
# CONFIG_INLINE_SPIN_UNLOCK_BH is not set
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
# CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_READ_TRYLOCK is not set
# CONFIG_INLINE_READ_LOCK is not set
# CONFIG_INLINE_READ_LOCK_BH is not set
# CONFIG_INLINE_READ_LOCK_IRQ is not set
# CONFIG_INLINE_READ_LOCK_IRQSAVE is not set
CONFIG_INLINE_READ_UNLOCK=y
# CONFIG_INLINE_READ_UNLOCK_BH is not set
CONFIG_INLINE_READ_UNLOCK_IRQ=y
# CONFIG_INLINE_READ_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_WRITE_TRYLOCK is not set
# CONFIG_INLINE_WRITE_LOCK is not set
# CONFIG_INLINE_WRITE_LOCK_BH is not set
# CONFIG_INLINE_WRITE_LOCK_IRQ is not set
# CONFIG_INLINE_WRITE_LOCK_IRQSAVE is not set
CONFIG_INLINE_WRITE_UNLOCK=y
# CONFIG_INLINE_WRITE_UNLOCK_BH is not set
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
# CONFIG_INLINE_WRITE_UNLOCK_IRQRESTORE is not set
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_FREEZER=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_MPPARSE is not set
CONFIG_X86_BIGSMP=y
# CONFIG_X86_EXTENDED_PLATFORM is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_X86_32_IRIS is not set
# CONFIG_SCHED_OMIT_FRAME_POINTER is not set
# CONFIG_PARAVIRT_GUEST is not set
CONFIG_NO_BOOTMEM=y
# CONFIG_MEMTEST 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=y
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_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_MCORE2 is not set
# CONFIG_MATOM is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CPU=y
CONFIG_X86_INTERNODE_CACHE_SHIFT=5
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_XADD=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=5
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_CYRIX_32=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_CPU_SUP_TRANSMETA_32=y
CONFIG_CPU_SUP_UMC_32=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
# CONFIG_IOMMU_HELPER is not set
# CONFIG_IOMMU_API is not set
CONFIG_NR_CPUS=32
# CONFIG_SCHED_SMT is not set
# CONFIG_SCHED_MC is not set
CONFIG_IRQ_TIME_ACCOUNTING=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_INTEL is not set
CONFIG_X86_MCE_AMD=y
CONFIG_X86_ANCIENT_MCE=y
CONFIG_X86_MCE_THRESHOLD=y
CONFIG_X86_MCE_INJECT=y
CONFIG_VM86=y
CONFIG_TOSHIBA=y
CONFIG_I8K=y
# CONFIG_X86_REBOOTFIXUPS is not set
CONFIG_MICROCODE=y
# CONFIG_MICROCODE_INTEL is not set
CONFIG_MICROCODE_AMD=y
CONFIG_MICROCODE_OLD_INTERFACE=y
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
# CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set
# CONFIG_ARCH_DMA_ADDR_T_64BIT is not set
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ILLEGAL_POINTER_VALUE=0
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_HAVE_MEMBLOCK=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_COMPACTION=y
CONFIG_MIGRATION=y
# CONFIG_PHYS_ADDR_T_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_MMU_NOTIFIER=y
CONFIG_KSM=y
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
CONFIG_MEMORY_FAILURE=y
CONFIG_CLEANCACHE=y
CONFIG_HIGHPTE=y
CONFIG_X86_CHECK_BIOS_CORRUPTION=y
# CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK is not set
CONFIG_X86_RESERVE_LOW=64
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_MTRR_SANITIZER is not set
CONFIG_X86_PAT=y
CONFIG_ARCH_USES_PG_UNCACHED=y
CONFIG_EFI=y
# CONFIG_SECCOMP is not set
# CONFIG_CC_STACKPROTECTOR 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 is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x1000000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x1000000
CONFIG_HOTPLUG_CPU=y
CONFIG_COMPAT_VDSO=y
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management and ACPI options
#
CONFIG_PM=y
CONFIG_PM_DEBUG=y
CONFIG_PM_ADVANCED_DEBUG=y
# CONFIG_PM_VERBOSE is not set
CONFIG_CAN_PM_TRACE=y
# CONFIG_PM_TRACE_RTC is not set
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
# CONFIG_PM_SLEEP_ADVANCED_DEBUG is not set
CONFIG_SUSPEND_NVS=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_PM_RUNTIME is not set
CONFIG_PM_OPS=y
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
# CONFIG_ACPI_PROCFS is not set
CONFIG_ACPI_PROCFS_POWER=y
# CONFIG_ACPI_POWER_METER is not set
CONFIG_ACPI_EC_DEBUGFS=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=y
# CONFIG_ACPI_BATTERY is not set
# CONFIG_ACPI_BUTTON is not set
CONFIG_ACPI_VIDEO=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
# CONFIG_ACPI_PROCESSOR is not set
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_ACPI_DEBUG=y
# CONFIG_ACPI_DEBUG_FUNC_TRACE is not set
# CONFIG_ACPI_PCI_SLOT is not set
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set
# CONFIG_ACPI_SBS is not set
CONFIG_ACPI_HED=y
CONFIG_ACPI_APEI=y
CONFIG_ACPI_APEI_GHES=y
# CONFIG_ACPI_APEI_EINJ is not set
CONFIG_ACPI_APEI_ERST_DEBUG=y
# CONFIG_SFI is not set
# CONFIG_APM is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
# CONFIG_CPU_IDLE is not set

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCI_CNB20LE_QUIRK=y
# CONFIG_DMAR is not set
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=y
# CONFIG_PCIEAER is not set
CONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
# CONFIG_PCI_STUB is not set
# CONFIG_HT_IRQ is not set
CONFIG_PCI_IOV=y
CONFIG_PCI_IOAPIC=y
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
CONFIG_MCA=y
CONFIG_MCA_LEGACY=y
# CONFIG_MCA_PROC_FS is not set
# CONFIG_SCx200 is not set
CONFIG_OLPC_OPENFIRMWARE=y
CONFIG_AMD_NB=y
CONFIG_PCCARD=y
# CONFIG_PCMCIA is not set
# CONFIG_CARDBUS is not set

#
# PC-card bridges
#
# CONFIG_YENTA is not set
CONFIG_HOTPLUG_PCI=y
# CONFIG_HOTPLUG_PCI_FAKE is not set
# CONFIG_HOTPLUG_PCI_COMPAQ is not set
# CONFIG_HOTPLUG_PCI_IBM is not set
CONFIG_HOTPLUG_PCI_ACPI=y
CONFIG_HOTPLUG_PCI_ACPI_IBM=y
# CONFIG_HOTPLUG_PCI_CPCI is not set
CONFIG_HOTPLUG_PCI_SHPC=y
# CONFIG_VBUS_PROXY is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
CONFIG_HAVE_AOUT=y
CONFIG_BINFMT_AOUT=y
# CONFIG_BINFMT_MISC is not set
CONFIG_HAVE_ATOMIC_IOMAP=y
CONFIG_HAVE_TEXT_POKE_SMP=y
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
CONFIG_XFRM_MIGRATE=y
CONFIG_XFRM_STATISTICS=y
CONFIG_XFRM_IPCOMP=y
CONFIG_NET_KEY=y
CONFIG_NET_KEY_MIGRATE=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
CONFIG_IP_PNP_RARP=y
# CONFIG_NET_IPIP is not set
CONFIG_NET_IPGRE_DEMUX=y
CONFIG_NET_IPGRE=y
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
# CONFIG_IP_PIMSM_V2 is not set
CONFIG_ARPD=y
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=y
CONFIG_INET_ESP=y
CONFIG_INET_IPCOMP=y
CONFIG_INET_XFRM_TUNNEL=y
CONFIG_INET_TUNNEL=y
CONFIG_INET_XFRM_MODE_TRANSPORT=y
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
CONFIG_INET_XFRM_MODE_BEET=y
# CONFIG_INET_LRO is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=y
CONFIG_TCP_CONG_CUBIC=y
# CONFIG_TCP_CONG_WESTWOOD is not set
# CONFIG_TCP_CONG_HTCP is not set
# CONFIG_TCP_CONG_HSTCP is not set
# CONFIG_TCP_CONG_HYBLA is not set
CONFIG_TCP_CONG_VEGAS=y
CONFIG_TCP_CONG_SCALABLE=y
# CONFIG_TCP_CONG_LP is not set
# CONFIG_TCP_CONG_VENO is not set
CONFIG_TCP_CONG_YEAH=y
# CONFIG_TCP_CONG_ILLINOIS is not set
# CONFIG_DEFAULT_BIC is not set
# CONFIG_DEFAULT_CUBIC is not set
CONFIG_DEFAULT_VEGAS=y
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="vegas"
# CONFIG_TCP_MD5SIG is not set
CONFIG_IPV6=y
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_IPV6_ROUTER_PREF is not set
CONFIG_IPV6_OPTIMISTIC_DAD=y
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
CONFIG_INET6_IPCOMP=y
# CONFIG_IPV6_MIP6 is not set
CONFIG_INET6_XFRM_TUNNEL=y
CONFIG_INET6_TUNNEL=y
# CONFIG_INET6_XFRM_MODE_TRANSPORT is not set
CONFIG_INET6_XFRM_MODE_TUNNEL=y
CONFIG_INET6_XFRM_MODE_BEET=y
CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=y
# CONFIG_IPV6_SIT is not set
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_IPV6_MULTIPLE_TABLES is not set
CONFIG_IPV6_MROUTE=y
CONFIG_IPV6_MROUTE_MULTIPLE_TABLES=y
# CONFIG_IPV6_PIMSM_V2 is not set
CONFIG_NETLABEL=y
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
CONFIG_NETFILTER=y
CONFIG_NETFILTER_DEBUG=y
CONFIG_NETFILTER_ADVANCED=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=y
CONFIG_NETFILTER_NETLINK_QUEUE=y
# CONFIG_NETFILTER_NETLINK_LOG is not set
CONFIG_NF_CONNTRACK=y
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
# CONFIG_NF_CT_PROTO_DCCP is not set
CONFIG_NF_CT_PROTO_GRE=y
# CONFIG_NF_CT_PROTO_SCTP is not set
CONFIG_NF_CT_PROTO_UDPLITE=y
CONFIG_NF_CONNTRACK_AMANDA=y
# CONFIG_NF_CONNTRACK_FTP is not set
# CONFIG_NF_CONNTRACK_H323 is not set
CONFIG_NF_CONNTRACK_IRC=y
CONFIG_NF_CONNTRACK_NETBIOS_NS=y
CONFIG_NF_CONNTRACK_PPTP=y
# CONFIG_NF_CONNTRACK_SANE is not set
CONFIG_NF_CONNTRACK_SIP=y
CONFIG_NF_CONNTRACK_TFTP=y
CONFIG_NF_CT_NETLINK=y
CONFIG_NETFILTER_XTABLES=y

#
# Xtables combined modules
#
# CONFIG_NETFILTER_XT_MARK is not set
CONFIG_NETFILTER_XT_CONNMARK=y

#
# Xtables targets
#
# CONFIG_NETFILTER_XT_TARGET_CHECKSUM is not set
# CONFIG_NETFILTER_XT_TARGET_CLASSIFY is not set
CONFIG_NETFILTER_XT_TARGET_CONNMARK=y
# CONFIG_NETFILTER_XT_TARGET_CT is not set
# CONFIG_NETFILTER_XT_TARGET_DSCP is not set
# CONFIG_NETFILTER_XT_TARGET_HL is not set
# CONFIG_NETFILTER_XT_TARGET_IDLETIMER is not set
CONFIG_NETFILTER_XT_TARGET_LED=y
# CONFIG_NETFILTER_XT_TARGET_MARK is not set
# CONFIG_NETFILTER_XT_TARGET_NFLOG is not set
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=y
# CONFIG_NETFILTER_XT_TARGET_NOTRACK is not set
CONFIG_NETFILTER_XT_TARGET_RATEEST=y
CONFIG_NETFILTER_XT_TARGET_TEE=y
CONFIG_NETFILTER_XT_TARGET_TRACE=y
CONFIG_NETFILTER_XT_TARGET_TCPMSS=y
CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=y

#
# Xtables matches
#
CONFIG_NETFILTER_XT_MATCH_CLUSTER=y
CONFIG_NETFILTER_XT_MATCH_COMMENT=y
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=y
# CONFIG_NETFILTER_XT_MATCH_CONNLIMIT is not set
CONFIG_NETFILTER_XT_MATCH_CONNMARK=y
# CONFIG_NETFILTER_XT_MATCH_CONNTRACK is not set
CONFIG_NETFILTER_XT_MATCH_CPU=y
# CONFIG_NETFILTER_XT_MATCH_DCCP is not set
# CONFIG_NETFILTER_XT_MATCH_DSCP is not set
# CONFIG_NETFILTER_XT_MATCH_ESP is not set
# CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is not set
CONFIG_NETFILTER_XT_MATCH_HELPER=y
# CONFIG_NETFILTER_XT_MATCH_HL is not set
CONFIG_NETFILTER_XT_MATCH_IPRANGE=y
# CONFIG_NETFILTER_XT_MATCH_LENGTH is not set
# CONFIG_NETFILTER_XT_MATCH_LIMIT is not set
CONFIG_NETFILTER_XT_MATCH_MAC=y
# CONFIG_NETFILTER_XT_MATCH_MARK is not set
# CONFIG_NETFILTER_XT_MATCH_MULTIPORT is not set
CONFIG_NETFILTER_XT_MATCH_OSF=y
CONFIG_NETFILTER_XT_MATCH_OWNER=y
# CONFIG_NETFILTER_XT_MATCH_POLICY is not set
# CONFIG_NETFILTER_XT_MATCH_PKTTYPE is not set
# CONFIG_NETFILTER_XT_MATCH_QUOTA is not set
# CONFIG_NETFILTER_XT_MATCH_RATEEST is not set
CONFIG_NETFILTER_XT_MATCH_REALM=y
# CONFIG_NETFILTER_XT_MATCH_RECENT is not set
CONFIG_NETFILTER_XT_MATCH_SCTP=y
# CONFIG_NETFILTER_XT_MATCH_STATE is not set
# CONFIG_NETFILTER_XT_MATCH_STATISTIC is not set
CONFIG_NETFILTER_XT_MATCH_STRING=y
CONFIG_NETFILTER_XT_MATCH_TCPMSS=y
CONFIG_NETFILTER_XT_MATCH_TIME=y
# CONFIG_NETFILTER_XT_MATCH_U32 is not set
# CONFIG_IP_VS is not set

#
# IP: Netfilter Configuration
#
# CONFIG_NF_DEFRAG_IPV4 is not set
# CONFIG_NF_CONNTRACK_IPV4 is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=y
# CONFIG_IP_NF_MATCH_ADDRTYPE is not set
# CONFIG_IP_NF_MATCH_AH is not set
# CONFIG_IP_NF_MATCH_ECN is not set
# CONFIG_IP_NF_MATCH_TTL is not set
# CONFIG_IP_NF_FILTER is not set
CONFIG_IP_NF_TARGET_LOG=y
# CONFIG_IP_NF_TARGET_ULOG is not set
# CONFIG_IP_NF_MANGLE is not set
CONFIG_IP_NF_RAW=y
CONFIG_IP_NF_SECURITY=y
CONFIG_IP_NF_ARPTABLES=y
CONFIG_IP_NF_ARPFILTER=y
# CONFIG_IP_NF_ARP_MANGLE is not set

#
# IPv6: Netfilter Configuration
#
# CONFIG_NF_DEFRAG_IPV6 is not set
# CONFIG_NF_CONNTRACK_IPV6 is not set
CONFIG_IP6_NF_QUEUE=y
CONFIG_IP6_NF_IPTABLES=y
CONFIG_IP6_NF_MATCH_AH=y
# CONFIG_IP6_NF_MATCH_EUI64 is not set
# CONFIG_IP6_NF_MATCH_FRAG is not set
CONFIG_IP6_NF_MATCH_OPTS=y
# CONFIG_IP6_NF_MATCH_HL is not set
# CONFIG_IP6_NF_MATCH_IPV6HEADER is not set
CONFIG_IP6_NF_MATCH_MH=y
# CONFIG_IP6_NF_MATCH_RT is not set
# CONFIG_IP6_NF_TARGET_HL is not set
# CONFIG_IP6_NF_TARGET_LOG is not set
# CONFIG_IP6_NF_FILTER is not set
CONFIG_IP6_NF_MANGLE=y
# CONFIG_IP6_NF_RAW is not set
# CONFIG_IP6_NF_SECURITY is not set

#
# DECnet: Netfilter Configuration
#
CONFIG_DECNET_NF_GRABULATOR=y
CONFIG_IP_DCCP=y
CONFIG_INET_DCCP_DIAG=y

#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP_CCID2_DEBUG=y
# CONFIG_IP_DCCP_CCID3 is not set
CONFIG_IP_SCTP=y
# 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_RDS=y
CONFIG_RDS_TCP=y
# CONFIG_RDS_DEBUG is not set
CONFIG_TIPC=y
CONFIG_TIPC_ADVANCED=y
CONFIG_TIPC_ZONES=3
CONFIG_TIPC_CLUSTERS=1
CONFIG_TIPC_NODES=255
CONFIG_TIPC_PORTS=8191
CONFIG_TIPC_LOG=0
# CONFIG_TIPC_DEBUG is not set
CONFIG_ATM=y
# CONFIG_ATM_CLIP is not set
# CONFIG_ATM_LANE is not set
# CONFIG_ATM_BR2684 is not set
CONFIG_L2TP=y
CONFIG_L2TP_DEBUGFS=y
# CONFIG_L2TP_V3 is not set
# CONFIG_BRIDGE is not set
CONFIG_NET_DSA=y
# CONFIG_NET_DSA_TAG_DSA is not set
CONFIG_NET_DSA_TAG_EDSA=y
CONFIG_NET_DSA_TAG_TRAILER=y
CONFIG_NET_DSA_MV88E6XXX=y
CONFIG_NET_DSA_MV88E6060=y
# CONFIG_NET_DSA_MV88E6XXX_NEED_PPU is not set
# CONFIG_NET_DSA_MV88E6131 is not set
CONFIG_NET_DSA_MV88E6123_61_65=y
# CONFIG_VLAN_8021Q is not set
CONFIG_DECNET=y
CONFIG_DECNET_ROUTER=y
CONFIG_LLC=y
# CONFIG_LLC2 is not set
CONFIG_IPX=y
CONFIG_IPX_INTERN=y
CONFIG_ATALK=y
CONFIG_DEV_APPLETALK=y
CONFIG_IPDDP=y
# CONFIG_IPDDP_ENCAP is not set
CONFIG_IPDDP_DECAP=y
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
CONFIG_ECONET=y
# CONFIG_ECONET_AUNUDP is not set
CONFIG_ECONET_NATIVE=y
CONFIG_WAN_ROUTER=y
CONFIG_PHONET=y
CONFIG_PHONET_PIPECTRLR=y
CONFIG_IEEE802154=y
# CONFIG_NET_SCHED is not set
CONFIG_NET_CLS_ROUTE=y
CONFIG_DCB=y
CONFIG_DNS_RESOLVER=y
CONFIG_RPS=y
CONFIG_XPS=y

#
# Network testing
#
CONFIG_NET_PKTGEN=y
CONFIG_HAMRADIO=y

#
# Packet Radio protocols
#
# CONFIG_AX25 is not set
# CONFIG_CAN is not set
CONFIG_IRDA=y

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

#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
# CONFIG_IRDA_DEBUG is not set

#
# Infrared-port device drivers
#

#
# SIR device drivers
#
# CONFIG_IRTTY_SIR is not set

#
# Dongle support
#
# CONFIG_KINGSUN_DONGLE is not set
# CONFIG_KSDAZZLE_DONGLE is not set
# CONFIG_KS959_DONGLE is not set

#
# FIR device drivers
#
CONFIG_USB_IRDA=y
# CONFIG_SIGMATEL_FIR is not set
# CONFIG_NSC_FIR is not set
CONFIG_WINBOND_FIR=y
# CONFIG_TOSHIBA_FIR is not set
# CONFIG_SMC_IRCC_FIR is not set
# CONFIG_ALI_FIR is not set
# CONFIG_VLSI_FIR is not set
CONFIG_VIA_FIR=y
# CONFIG_MCS_FIR is not set
CONFIG_BT=y
CONFIG_BT_L2CAP=y
# CONFIG_BT_SCO is not set
# CONFIG_BT_RFCOMM is not set
# CONFIG_BT_BNEP is not set
# CONFIG_BT_CMTP is not set

#
# Bluetooth device drivers
#
CONFIG_BT_HCIBTUSB=y
# CONFIG_BT_HCIUART is not set
# CONFIG_BT_HCIBCM203X is not set
CONFIG_BT_HCIBPA10X=y
CONFIG_BT_HCIBFUSB=y
# CONFIG_BT_HCIVHCI is not set
CONFIG_BT_MRVL=y
# CONFIG_BT_ATH3K is not set
CONFIG_AF_RXRPC=y
# CONFIG_AF_RXRPC_DEBUG is not set
CONFIG_RXKAD=y
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
# CONFIG_CFG80211 is not set
# CONFIG_LIB80211 is not set

#
# CFG80211 needs to be enabled for MAC80211
#

#
# Some wireless drivers require a rate control algorithm
#
# CONFIG_WIMAX is not set
# CONFIG_RFKILL is not set
CONFIG_NET_9P=y
CONFIG_NET_9P_VIRTIO=y
# CONFIG_NET_9P_DEBUG is not set
CONFIG_CAIF=y
CONFIG_CAIF_DEBUG=y
CONFIG_CAIF_NETDEV=y
CONFIG_CEPH_LIB=y
# CONFIG_CEPH_LIB_PRETTYDEBUG is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH=""
CONFIG_DEVTMPFS=y
# CONFIG_DEVTMPFS_MOUNT is not set
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_PNP=y
CONFIG_PNP_DEBUG_MESSAGES=y

#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_BLK_DEV_UMEM=y
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_OSD is not set
CONFIG_BLK_DEV_SX8=y
# CONFIG_BLK_DEV_UB is not set
# CONFIG_BLK_DEV_RAM is not set
CONFIG_CDROM_PKTCDVD=y
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_ATA_OVER_ETH=y
# CONFIG_VIRTIO_BLK is not set
# CONFIG_BLK_DEV_HD is not set
# CONFIG_BLK_DEV_RBD is not set
# CONFIG_MISC_DEVICES is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set

#
# SCSI device support
#
CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=y
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 is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
CONFIG_CHR_DEV_SCH=y
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SCSI_FC_ATTRS=y
CONFIG_SCSI_FC_TGT_ATTRS=y
CONFIG_SCSI_ISCSI_ATTRS=y
CONFIG_SCSI_SAS_ATTRS=y
CONFIG_SCSI_SAS_LIBSAS=y
# CONFIG_SCSI_SAS_ATA is not set
# CONFIG_SCSI_SAS_HOST_SMP is not set
# CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set
CONFIG_SCSI_SRP_ATTRS=y
CONFIG_SCSI_SRP_TGT_ATTRS=y
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
CONFIG_ISCSI_BOOT_SYSFS=y
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_BE2ISCSI is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_HPSA is not set
# CONFIG_SCSI_3W_9XXX is not set
CONFIG_SCSI_3W_SAS=y
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=32
CONFIG_AIC7XXX_RESET_DELAY_MS=5000
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
CONFIG_AIC7XXX_DEBUG_MASK=0
# CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set
CONFIG_SCSI_AIC7XXX_OLD=y
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
CONFIG_SCSI_MVSAS=y
# CONFIG_SCSI_MVSAS_DEBUG is not set
CONFIG_SCSI_DPT_I2O=y
CONFIG_SCSI_ADVANSYS=y
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_MPT2SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
CONFIG_VMWARE_PVSCSI=y
CONFIG_LIBFC=y
CONFIG_LIBFCOE=y
CONFIG_FCOE=y
CONFIG_FCOE_FNIC=y
CONFIG_SCSI_DMX3191D=y
CONFIG_SCSI_EATA=y
CONFIG_SCSI_EATA_TAGGED_QUEUE=y
CONFIG_SCSI_EATA_LINKED_COMMANDS=y
CONFIG_SCSI_EATA_MAX_TAGS=16
CONFIG_SCSI_FUTURE_DOMAIN=y
CONFIG_SCSI_FD_MCS=y
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IBMMCA is not set
CONFIG_SCSI_IPS=y
# CONFIG_SCSI_INITIO is not set
CONFIG_SCSI_INIA100=y
# CONFIG_SCSI_NCR_D700 is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
CONFIG_SCSI_IPR=y
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
# CONFIG_SCSI_NCR_Q720 is not set
CONFIG_SCSI_QLOGIC_1280=y
CONFIG_SCSI_QLA_FC=y
CONFIG_SCSI_QLA_ISCSI=y
# CONFIG_SCSI_LPFC is not set
CONFIG_SCSI_SIM710=y
CONFIG_SCSI_DC395x=y
# CONFIG_SCSI_DC390T is not set
CONFIG_SCSI_NSP32=y
CONFIG_SCSI_DEBUG=y
CONFIG_SCSI_PMCRAID=y
CONFIG_SCSI_PM8001=y
# CONFIG_SCSI_SRP is not set
CONFIG_SCSI_BFA_FC=y
CONFIG_SCSI_DH=y
# CONFIG_SCSI_DH_RDAC is not set
CONFIG_SCSI_DH_HP_SW=y
CONFIG_SCSI_DH_EMC=y
CONFIG_SCSI_DH_ALUA=y
CONFIG_SCSI_OSD_INITIATOR=y
CONFIG_SCSI_OSD_ULD=y
CONFIG_SCSI_OSD_DPRINT_SENSE=1
CONFIG_SCSI_OSD_DEBUG=y
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_VERBOSE_ERROR=y
# CONFIG_ATA_ACPI is not set
CONFIG_SATA_PMP=y

#
# Controllers with non-SFF native interface
#
CONFIG_SATA_AHCI=y
CONFIG_SATA_AHCI_PLATFORM=y
# CONFIG_SATA_INIC162X is not set
CONFIG_SATA_ACARD_AHCI=y
CONFIG_SATA_SIL24=y
# CONFIG_ATA_SFF is not set
# CONFIG_MD is not set
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
CONFIG_FIREWIRE=y
CONFIG_FIREWIRE_OHCI=y
CONFIG_FIREWIRE_OHCI_DEBUG=y
CONFIG_FIREWIRE_SBP2=y
CONFIG_FIREWIRE_NET=y
CONFIG_FIREWIRE_NOSY=y
CONFIG_I2O=y
# CONFIG_I2O_LCT_NOTIFY_ON_CHANGES is not set
CONFIG_I2O_EXT_ADAPTEC=y
CONFIG_I2O_CONFIG=y
CONFIG_I2O_CONFIG_OLD_IOCTL=y
CONFIG_I2O_BUS=y
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_SCSI is not set
CONFIG_I2O_PROC=y
CONFIG_MACINTOSH_DRIVERS=y
# CONFIG_MAC_EMUMOUSEBTN is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
CONFIG_BONDING=y
CONFIG_MACVLAN=y
CONFIG_MACVTAP=y
CONFIG_EQUALIZER=y
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
CONFIG_MII=y
CONFIG_PHYLIB=y

#
# MII PHY device drivers
#
# CONFIG_MARVELL_PHY is not set
# CONFIG_DAVICOM_PHY is not set
CONFIG_QSEMI_PHY=y
# CONFIG_LXT_PHY is not set
CONFIG_CICADA_PHY=y
# CONFIG_VITESSE_PHY is not set
CONFIG_SMSC_PHY=y
# CONFIG_BROADCOM_PHY is not set
CONFIG_BCM63XX_PHY=y
CONFIG_ICPLUS_PHY=y
# CONFIG_REALTEK_PHY is not set
# CONFIG_NATIONAL_PHY is not set
CONFIG_STE10XP=y
CONFIG_LSI_ET1011C_PHY=y
# CONFIG_MICREL_PHY is not set
CONFIG_FIXED_PHY=y
CONFIG_MDIO_BITBANG=y
CONFIG_NET_ETHERNET=y
# CONFIG_HAPPYMEAL is not set
CONFIG_SUNGEM=y
CONFIG_CASSINI=y
# CONFIG_NET_VENDOR_3COM is not set
CONFIG_NET_VENDOR_SMC=y
# CONFIG_ULTRAMCA is not set
# CONFIG_ENC28J60 is not set
# CONFIG_ETHOC is not set
# CONFIG_DNET is not set
# CONFIG_NET_TULIP is not set
CONFIG_AT1700=y
# CONFIG_DEPCA is not set
CONFIG_HP100=y
# CONFIG_NE2_MCA is not set
# CONFIG_IBMLANA is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set
# CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
# CONFIG_NET_PCI is not set
# CONFIG_B44 is not set
CONFIG_KS8851=y
CONFIG_KS8851_MLL=y
# CONFIG_ATL2 is not set
# CONFIG_NETDEV_1000 is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set
# CONFIG_WLAN is not set

#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
CONFIG_USB_RTL8150=y
# CONFIG_USB_USBNET is not set
CONFIG_USB_CDC_PHONET=y
# CONFIG_USB_IPHETH is not set
CONFIG_WAN=y
# CONFIG_HDLC is not set
CONFIG_DLCI=y
CONFIG_DLCI_MAX=8
CONFIG_WAN_ROUTER_DRIVERS=y
CONFIG_CYCLADES_SYNC=y
CONFIG_CYCLOMX_X25=y
CONFIG_SBNI=y
CONFIG_SBNI_MULTILINE=y
CONFIG_ATM_DRIVERS=y
# CONFIG_ATM_DUMMY is not set
CONFIG_ATM_TCP=y
# CONFIG_ATM_LANAI is not set
# CONFIG_ATM_ENI is not set
CONFIG_ATM_FIRESTREAM=y
# CONFIG_ATM_ZATM is not set
# CONFIG_ATM_NICSTAR is not set
# CONFIG_ATM_IDT77252 is not set
# CONFIG_ATM_AMBASSADOR is not set
# CONFIG_ATM_HORIZON is not set
# CONFIG_ATM_IA is not set
CONFIG_ATM_FORE200E=y
CONFIG_ATM_FORE200E_USE_TASKLET=y
CONFIG_ATM_FORE200E_TX_RETRY=16
CONFIG_ATM_FORE200E_DEBUG=0
# CONFIG_ATM_HE is not set
# CONFIG_ATM_SOLOS is not set
# CONFIG_IEEE802154_DRIVERS is not set

#
# CAIF transport drivers
#
CONFIG_CAIF_TTY=y
# CONFIG_CAIF_SPI_SLAVE is not set
# CONFIG_FDDI is not set
CONFIG_HIPPI=y
CONFIG_ROADRUNNER=y
# CONFIG_ROADRUNNER_LARGE_RINGS is not set
CONFIG_PPP=y
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
# CONFIG_PPP_DEFLATE is not set
CONFIG_PPP_BSDCOMP=y
CONFIG_PPP_MPPE=y
# CONFIG_PPPOE is not set
CONFIG_PPTP=y
CONFIG_PPPOATM=y
CONFIG_PPPOL2TP=y
CONFIG_SLIP=y
# CONFIG_SLIP_COMPRESSED is not set
CONFIG_SLHC=y
# CONFIG_SLIP_SMART is not set
# CONFIG_SLIP_MODE_SLIP6 is not set
CONFIG_NET_FC=y
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
CONFIG_VIRTIO_NET=y
# CONFIG_VMXNET3 is not set
CONFIG_ISDN=y
# CONFIG_ISDN_I4L is not set
CONFIG_ISDN_CAPI=y
CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON=y
CONFIG_CAPI_TRACE=y
CONFIG_ISDN_CAPI_MIDDLEWARE=y
# CONFIG_ISDN_CAPI_CAPI20 is not set

#
# CAPI hardware drivers
#
CONFIG_CAPI_AVM=y
CONFIG_ISDN_DRV_AVMB1_B1PCI=y
# CONFIG_ISDN_DRV_AVMB1_B1PCIV4 is not set
# CONFIG_ISDN_DRV_AVMB1_T1PCI is not set
CONFIG_ISDN_DRV_AVMB1_C4=y
# CONFIG_CAPI_EICON is not set
# CONFIG_ISDN_DRV_GIGASET is not set
# CONFIG_MISDN is not set
CONFIG_PHONE=y
# CONFIG_PHONE_IXJ is not set

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

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

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ADP5588=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_KEYBOARD_QT2160=y
# CONFIG_KEYBOARD_LKKBD is not set
CONFIG_KEYBOARD_TCA6416=y
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
CONFIG_KEYBOARD_MCS=y
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_KEYBOARD_OPENCORES=y
CONFIG_KEYBOARD_STOWAWAY=y
CONFIG_KEYBOARD_SUNKBD=y
CONFIG_KEYBOARD_TWL4030=y
CONFIG_KEYBOARD_XTKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_ELANTECH is not set
CONFIG_MOUSE_PS2_SENTELIC=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_SERIAL=y
CONFIG_MOUSE_APPLETOUCH=y
CONFIG_MOUSE_BCM5974=y
# CONFIG_MOUSE_VSXXXAA is not set
CONFIG_MOUSE_SYNAPTICS_I2C=y
CONFIG_INPUT_JOYSTICK=y
# CONFIG_JOYSTICK_ANALOG is not set
# CONFIG_JOYSTICK_A3D is not set
# CONFIG_JOYSTICK_ADI is not set
# CONFIG_JOYSTICK_COBRA is not set
CONFIG_JOYSTICK_GF2K=y
# CONFIG_JOYSTICK_GRIP is not set
CONFIG_JOYSTICK_GRIP_MP=y
# CONFIG_JOYSTICK_GUILLEMOT is not set
CONFIG_JOYSTICK_INTERACT=y
CONFIG_JOYSTICK_SIDEWINDER=y
# CONFIG_JOYSTICK_TMDC is not set
CONFIG_JOYSTICK_IFORCE=y
CONFIG_JOYSTICK_IFORCE_USB=y
CONFIG_JOYSTICK_IFORCE_232=y
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDJOY is not set
CONFIG_JOYSTICK_ZHENHUA=y
CONFIG_JOYSTICK_JOYDUMP=y
# CONFIG_JOYSTICK_XPAD is not set
# CONFIG_INPUT_TABLET is not set
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_88PM860X=y
CONFIG_TOUCHSCREEN_ADS7846=y
CONFIG_TOUCHSCREEN_AD7877=y
# CONFIG_TOUCHSCREEN_AD7879 is not set
CONFIG_TOUCHSCREEN_BU21013=y
CONFIG_TOUCHSCREEN_DA9034=y
CONFIG_TOUCHSCREEN_DYNAPRO=y
CONFIG_TOUCHSCREEN_HAMPSHIRE=y
CONFIG_TOUCHSCREEN_EETI=y
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
CONFIG_TOUCHSCREEN_ELO=y
CONFIG_TOUCHSCREEN_WACOM_W8001=y
# CONFIG_TOUCHSCREEN_MCS5000 is not set
CONFIG_TOUCHSCREEN_MTOUCH=y
CONFIG_TOUCHSCREEN_INEXIO=y
# CONFIG_TOUCHSCREEN_MK712 is not set
CONFIG_TOUCHSCREEN_PENMOUNT=y
CONFIG_TOUCHSCREEN_QT602240=y
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
CONFIG_TOUCHSCREEN_TOUCHWIN=y
CONFIG_TOUCHSCREEN_USB_COMPOSITE=y
# CONFIG_TOUCHSCREEN_MC13783 is not set
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_TOUCHSCREEN_USB_JASTEC=y
CONFIG_TOUCHSCREEN_USB_E2I=y
CONFIG_TOUCHSCREEN_USB_ZYTRONIC=y
CONFIG_TOUCHSCREEN_USB_ETT_TC45USB=y
CONFIG_TOUCHSCREEN_USB_NEXIO=y
CONFIG_TOUCHSCREEN_TOUCHIT213=y
# CONFIG_TOUCHSCREEN_TSC2007 is not set
CONFIG_TOUCHSCREEN_PCAP=y
CONFIG_TOUCHSCREEN_TPS6507X=y
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
CONFIG_SERIO_CT82C710=y
CONFIG_SERIO_PCIPS2=y
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
CONFIG_SERIO_ALTERA_PS2=y
# CONFIG_SERIO_PS2MULT is not set
CONFIG_GAMEPORT=y
# CONFIG_GAMEPORT_NS558 is not set
# CONFIG_GAMEPORT_L4 is not set
# CONFIG_GAMEPORT_EMU10K1 is not set
# CONFIG_GAMEPORT_FM801 is not set

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

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

#
# Non-8250 serial port support
#
CONFIG_SERIAL_MAX3100=y
# CONFIG_SERIAL_MAX3107 is not set
CONFIG_SERIAL_MFD_HSU=y
# CONFIG_SERIAL_MFD_HSU_CONSOLE is not set
CONFIG_SERIAL_CORE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_SERIAL_TIMBERDALE=y
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
CONFIG_SERIAL_ALTERA_UART=y
CONFIG_SERIAL_ALTERA_UART_MAXPORTS=4
CONFIG_SERIAL_ALTERA_UART_BAUDRATE=115200
# CONFIG_SERIAL_ALTERA_UART_CONSOLE is not set
CONFIG_SERIAL_PCH_UART=y
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_HVC_DRIVER=y
# CONFIG_VIRTIO_CONSOLE is not set
CONFIG_IPMI_HANDLER=y
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=y
CONFIG_IPMI_SI=y
# CONFIG_IPMI_WATCHDOG is not set
CONFIG_IPMI_POWEROFF=y
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
CONFIG_HW_RANDOM_INTEL=y
CONFIG_HW_RANDOM_AMD=y
CONFIG_HW_RANDOM_GEODE=y
# CONFIG_HW_RANDOM_VIA is not set
# CONFIG_HW_RANDOM_VIRTIO is not set
CONFIG_NVRAM=y
CONFIG_RTC=y
# CONFIG_R3964 is not set
CONFIG_APPLICOM=y
# CONFIG_SONYPI is not set
CONFIG_MWAVE=y
# CONFIG_PC8736x_GPIO is not set
CONFIG_NSC_GPIO=y
CONFIG_CS5535_GPIO=y
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set
CONFIG_TCG_TPM=y
CONFIG_TCG_TIS=y
CONFIG_TCG_NSC=y
CONFIG_TCG_ATMEL=y
# CONFIG_TCG_INFINEON is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
# CONFIG_RAMOOPS is not set
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
# CONFIG_I2C_CHARDEV is not set
# CONFIG_I2C_MUX is not set
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_ALGOBIT=y
CONFIG_I2C_ALGOPCF=y
CONFIG_I2C_ALGOPCA=y

#
# I2C Hardware Bus support
#

#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
CONFIG_I2C_ALI1563=y
CONFIG_I2C_ALI15X3=y
CONFIG_I2C_AMD756=y
# CONFIG_I2C_AMD756_S4882 is not set
CONFIG_I2C_AMD8111=y
# CONFIG_I2C_I801 is not set
CONFIG_I2C_ISCH=y
CONFIG_I2C_PIIX4=y
# CONFIG_I2C_NFORCE2 is not set
CONFIG_I2C_SIS5595=y
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
CONFIG_I2C_VIA=y
CONFIG_I2C_VIAPRO=y

#
# ACPI drivers
#
CONFIG_I2C_SCMI=y

#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
CONFIG_I2C_INTEL_MID=y
CONFIG_I2C_OCORES=y
CONFIG_I2C_PCA_PLATFORM=y
CONFIG_I2C_SIMTEC=y
CONFIG_I2C_XILINX=y
CONFIG_I2C_EG20T=y

#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set

#
# Other I2C/SMBus bus drivers
#
CONFIG_SCx200_ACB=y
# CONFIG_I2C_DEBUG_CORE is not set
CONFIG_I2C_DEBUG_ALGO=y
# CONFIG_I2C_DEBUG_BUS is not set
CONFIG_SPI=y
CONFIG_SPI_MASTER=y

#
# SPI Master Controller Drivers
#
CONFIG_SPI_BITBANG=y
# CONFIG_SPI_TOPCLIFF_PCH is not set
CONFIG_SPI_XILINX=y
CONFIG_SPI_XILINX_PLTFM=y
# CONFIG_SPI_DESIGNWARE is not set

#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not set
CONFIG_SPI_TLE62X0=y

#
# PPS support
#
# CONFIG_PPS is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
CONFIG_W1=y
# CONFIG_W1_CON is not set

#
# 1-wire Bus Masters
#
CONFIG_W1_MASTER_MATROX=y
# CONFIG_W1_MASTER_DS2490 is not set
CONFIG_W1_MASTER_DS2482=y

#
# 1-wire Slaves
#
CONFIG_W1_SLAVE_THERM=y
# CONFIG_W1_SLAVE_SMEM is not set
# CONFIG_W1_SLAVE_DS2423 is not set
CONFIG_W1_SLAVE_DS2431=y
# CONFIG_W1_SLAVE_DS2433 is not set
CONFIG_W1_SLAVE_DS2760=y
CONFIG_W1_SLAVE_BQ27000=y
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
CONFIG_MAX8925_POWER=y
# CONFIG_WM8350_POWER is not set
CONFIG_TEST_POWER=y
CONFIG_BATTERY_DS2760=y
CONFIG_BATTERY_DS2782=y
CONFIG_BATTERY_BQ20Z75=y
# CONFIG_BATTERY_BQ27x00 is not set
CONFIG_BATTERY_DA9030=y
# CONFIG_BATTERY_MAX17040 is not set
CONFIG_CHARGER_PCF50633=y
# CONFIG_CHARGER_TWL4030 is not set
CONFIG_HWMON=y
CONFIG_HWMON_VID=y
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Native drivers
#
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7414 is not set
CONFIG_SENSORS_AD7418=y
# CONFIG_SENSORS_ADCXX is not set
CONFIG_SENSORS_ADM1021=y
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
CONFIG_SENSORS_ADM1029=y
# CONFIG_SENSORS_ADM1031 is not set
CONFIG_SENSORS_ADM9240=y
# CONFIG_SENSORS_ADT7411 is not set
CONFIG_SENSORS_ADT7462=y
CONFIG_SENSORS_ADT7470=y
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_ASC7621 is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_K10TEMP is not set
CONFIG_SENSORS_ASB100=y
# CONFIG_SENSORS_ATXP1 is not set
CONFIG_SENSORS_DS1621=y
CONFIG_SENSORS_I5K_AMB=y
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
CONFIG_SENSORS_FSCHMD=y
# CONFIG_SENSORS_G760A is not set
CONFIG_SENSORS_GL518SM=y
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_CORETEMP is not set
# CONFIG_SENSORS_PKGTEMP is not set
CONFIG_SENSORS_IBMAEM=y
CONFIG_SENSORS_IBMPEX=y
CONFIG_SENSORS_IT87=y
CONFIG_SENSORS_JC42=y
# CONFIG_SENSORS_LM63 is not set
CONFIG_SENSORS_LM70=y
# CONFIG_SENSORS_LM73 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
CONFIG_SENSORS_LM90=y
# CONFIG_SENSORS_LM92 is not set
CONFIG_SENSORS_LM93=y
CONFIG_SENSORS_LTC4215=y
CONFIG_SENSORS_LTC4245=y
# CONFIG_SENSORS_LTC4261 is not set
# CONFIG_SENSORS_LM95241 is not set
# CONFIG_SENSORS_MAX1111 is not set
# CONFIG_SENSORS_MAX1619 is not set
CONFIG_SENSORS_MAX6650=y
CONFIG_SENSORS_PC87360=y
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_PCF8591 is not set
CONFIG_SENSORS_SIS5595=y
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_EMC1403 is not set
CONFIG_SENSORS_EMC2103=y
CONFIG_SENSORS_SMSC47M1=y
CONFIG_SENSORS_SMSC47M192=y
CONFIG_SENSORS_SMSC47B397=y
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_ADS7871 is not set
# CONFIG_SENSORS_AMC6821 is not set
CONFIG_SENSORS_THMC50=y
CONFIG_SENSORS_TMP102=y
CONFIG_SENSORS_TMP401=y
# CONFIG_SENSORS_TMP421 is not set
# CONFIG_SENSORS_VIA_CPUTEMP is not set
CONFIG_SENSORS_VIA686A=y
CONFIG_SENSORS_VT1211=y
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
CONFIG_SENSORS_W83791D=y
CONFIG_SENSORS_W83792D=y
CONFIG_SENSORS_W83793=y
# CONFIG_SENSORS_W83795 is not set
# CONFIG_SENSORS_W83L785TS is not set
CONFIG_SENSORS_W83L786NG=y
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
CONFIG_SENSORS_WM8350=y
# CONFIG_SENSORS_LIS3_I2C is not set
# CONFIG_SENSORS_APPLESMC is not set
# CONFIG_SENSORS_MC13783_ADC is not set

#
# ACPI drivers
#
# CONFIG_SENSORS_ATK0110 is not set
CONFIG_SENSORS_LIS3LV02D=y
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y

#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set
CONFIG_MFD_SUPPORT=y
CONFIG_MFD_CORE=y
CONFIG_MFD_88PM860X=y
CONFIG_MFD_SM501=y
CONFIG_HTC_PASIC3=y
# CONFIG_TPS6507X is not set
CONFIG_TWL4030_CORE=y
# CONFIG_TWL4030_CODEC is not set
# CONFIG_TWL6030_PWM is not set
# CONFIG_MFD_STMPE is not set
CONFIG_MFD_TC35892=y
# CONFIG_MFD_TMIO is not set
CONFIG_PMIC_DA903X=y
# CONFIG_PMIC_ADP5520 is not set
CONFIG_MFD_MAX8925=y
CONFIG_MFD_MAX8998=y
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM831X_SPI is not set
CONFIG_MFD_WM8350=y
CONFIG_MFD_WM8350_I2C=y
CONFIG_MFD_WM8994=y
CONFIG_MFD_PCF50633=y
CONFIG_MFD_MC13783=y
CONFIG_MFD_MC13XXX=y
# CONFIG_PCF50633_ADC is not set
# CONFIG_PCF50633_GPIO is not set
CONFIG_ABX500_CORE=y
# CONFIG_AB3100_CORE is not set
CONFIG_EZX_PCAP=y
# CONFIG_AB3550_CORE is not set
# CONFIG_MFD_CS5535 is not set
CONFIG_LPC_SCH=y
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_JANZ_CMODIO is not set
CONFIG_MFD_VX855=y
CONFIG_REGULATOR=y
CONFIG_REGULATOR_DEBUG=y
CONFIG_REGULATOR_DUMMY=y
# CONFIG_REGULATOR_FIXED_VOLTAGE is not set
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
# CONFIG_REGULATOR_USERSPACE_CONSUMER is not set
CONFIG_REGULATOR_BQ24022=y
CONFIG_REGULATOR_MAX1586=y
CONFIG_REGULATOR_MAX8649=y
# CONFIG_REGULATOR_MAX8660 is not set
CONFIG_REGULATOR_MAX8925=y
CONFIG_REGULATOR_MAX8952=y
CONFIG_REGULATOR_MAX8998=y
CONFIG_REGULATOR_TWL4030=y
CONFIG_REGULATOR_WM8350=y
CONFIG_REGULATOR_WM8994=y
CONFIG_REGULATOR_DA903X=y
CONFIG_REGULATOR_PCF50633=y
# CONFIG_REGULATOR_LP3971 is not set
# CONFIG_REGULATOR_LP3972 is not set
CONFIG_REGULATOR_PCAP=y
CONFIG_REGULATOR_MC13783=y
# CONFIG_REGULATOR_TPS65023 is not set
# CONFIG_REGULATOR_TPS6507X is not set
CONFIG_REGULATOR_88PM8607=y
CONFIG_REGULATOR_ISL6271A=y
CONFIG_REGULATOR_AD5398=y
CONFIG_MEDIA_SUPPORT=y

#
# Multimedia core support
#
CONFIG_VIDEO_DEV=y
CONFIG_VIDEO_V4L2_COMMON=y
# CONFIG_VIDEO_ALLOW_V4L1 is not set
# CONFIG_VIDEO_V4L1_COMPAT is not set
# CONFIG_DVB_CORE is not set
CONFIG_VIDEO_MEDIA=y

#
# Multimedia drivers
#
CONFIG_RC_CORE=y
CONFIG_LIRC=y
# CONFIG_RC_MAP is not set
CONFIG_IR_NEC_DECODER=y
CONFIG_IR_RC5_DECODER=y
# CONFIG_IR_RC6_DECODER is not set
# CONFIG_IR_JVC_DECODER is not set
CONFIG_IR_SONY_DECODER=y
# CONFIG_IR_RC5_SZ_DECODER is not set
# CONFIG_IR_LIRC_CODEC is not set
CONFIG_IR_ENE=y
# CONFIG_IR_IMON is not set
CONFIG_IR_MCEUSB=y
CONFIG_IR_NUVOTON=y
CONFIG_IR_STREAMZAP=y
CONFIG_IR_WINBOND_CIR=y
CONFIG_MEDIA_TUNER=y
CONFIG_MEDIA_TUNER_CUSTOMISE=y

#
# Customize TV tuners
#
# CONFIG_MEDIA_TUNER_SIMPLE is not set
CONFIG_MEDIA_TUNER_TDA8290=y
CONFIG_MEDIA_TUNER_TDA827X=y
CONFIG_MEDIA_TUNER_TDA18271=y
# CONFIG_MEDIA_TUNER_TDA9887 is not set
CONFIG_MEDIA_TUNER_TEA5761=y
# CONFIG_MEDIA_TUNER_TEA5767 is not set
CONFIG_MEDIA_TUNER_MT20XX=y
# CONFIG_MEDIA_TUNER_MT2060 is not set
# CONFIG_MEDIA_TUNER_MT2266 is not set
# CONFIG_MEDIA_TUNER_MT2131 is not set
CONFIG_MEDIA_TUNER_QT1010=y
# CONFIG_MEDIA_TUNER_XC2028 is not set
CONFIG_MEDIA_TUNER_XC5000=y
# CONFIG_MEDIA_TUNER_MXL5005S is not set
# CONFIG_MEDIA_TUNER_MXL5007T is not set
CONFIG_MEDIA_TUNER_MC44S803=y
CONFIG_MEDIA_TUNER_MAX2165=y
CONFIG_MEDIA_TUNER_TDA18218=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEOBUF_GEN=y
CONFIG_VIDEOBUF_VMALLOC=y
CONFIG_VIDEOBUF_DMA_CONTIG=y
CONFIG_V4L2_MEM2MEM_DEV=y
# CONFIG_VIDEO_CAPTURE_DRIVERS is not set
CONFIG_V4L_MEM2MEM_DRIVERS=y
CONFIG_VIDEO_MEM2MEM_TESTDEV=y
# CONFIG_RADIO_ADAPTERS is not set
# CONFIG_DAB is not set

#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_ALI=y
CONFIG_AGP_ATI=y
# CONFIG_AGP_AMD is not set
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=y
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
CONFIG_AGP_SWORKS=y
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_VGA_ARB=y
CONFIG_VGA_ARB_MAX_GPUS=16
# CONFIG_VGA_SWITCHEROO is not set
CONFIG_DRM=y
CONFIG_DRM_KMS_HELPER=y
CONFIG_DRM_TTM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
CONFIG_DRM_I810=y
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
CONFIG_DRM_VIA=y
CONFIG_DRM_SAVAGE=y
# CONFIG_STUB_POULSBO is not set
CONFIG_VGASTATE=y
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
CONFIG_FB_DDC=y
CONFIG_FB_BOOT_VESA_SUPPORT=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
CONFIG_FB_SYS_FILLRECT=y
CONFIG_FB_SYS_COPYAREA=y
CONFIG_FB_SYS_IMAGEBLIT=y
CONFIG_FB_FOREIGN_ENDIAN=y
# CONFIG_FB_BOTH_ENDIAN is not set
CONFIG_FB_BIG_ENDIAN=y
# CONFIG_FB_LITTLE_ENDIAN is not set
CONFIG_FB_SYS_FOPS=y
# CONFIG_FB_WMT_GE_ROPS is not set
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_SVGALIB=y
# 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=y
# CONFIG_FB_PM2 is not set
CONFIG_FB_CYBER2000=y
CONFIG_FB_ARC=y
# CONFIG_FB_ASILIANT is not set
CONFIG_FB_IMSTT=y
CONFIG_FB_VGA16=y
# CONFIG_FB_UVESA is not set
CONFIG_FB_VESA=y
# CONFIG_FB_EFI is not set
# CONFIG_FB_N411 is not set
CONFIG_FB_HGA=y
# CONFIG_FB_HGA_ACCEL is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
CONFIG_FB_LE80578=y
CONFIG_FB_CARILLO_RANCH=y
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
CONFIG_FB_ATY=y
# CONFIG_FB_ATY_CT is not set
# CONFIG_FB_ATY_GX is not set
# CONFIG_FB_ATY_BACKLIGHT is not set
CONFIG_FB_S3=y
CONFIG_FB_SAVAGE=y
CONFIG_FB_SAVAGE_I2C=y
# CONFIG_FB_SAVAGE_ACCEL is not set
CONFIG_FB_SIS=y
CONFIG_FB_SIS_300=y
CONFIG_FB_SIS_315=y
# CONFIG_FB_VIA is not set
CONFIG_FB_NEOMAGIC=y
CONFIG_FB_KYRO=y
CONFIG_FB_3DFX=y
CONFIG_FB_3DFX_ACCEL=y
# CONFIG_FB_3DFX_I2C is not set
CONFIG_FB_VOODOO1=y
# CONFIG_FB_VT8623 is not set
CONFIG_FB_TRIDENT=y
CONFIG_FB_ARK=y
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
CONFIG_FB_GEODE=y
CONFIG_FB_GEODE_LX=y
# CONFIG_FB_GEODE_GX is not set
# CONFIG_FB_GEODE_GX1 is not set
CONFIG_FB_TMIO=y
CONFIG_FB_TMIO_ACCELL=y
CONFIG_FB_SM501=y
CONFIG_FB_VIRTUAL=y
CONFIG_FB_METRONOME=y
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_BROADSHEET is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_GENERIC=y
CONFIG_BACKLIGHT_PROGEAR=y
CONFIG_BACKLIGHT_DA903X=y
# CONFIG_BACKLIGHT_MAX8925 is not set
# CONFIG_BACKLIGHT_MBP_NVIDIA is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
CONFIG_BACKLIGHT_88PM860X=y
# CONFIG_BACKLIGHT_PCF50633 is not set

#
# Display device support
#
CONFIG_DISPLAY_SUPPORT=y

#
# Display hardware drivers
#

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_FONT_6x11=y
# CONFIG_FONT_7x14 is not set
CONFIG_FONT_PEARL_8x8=y
CONFIG_FONT_ACORN_8x8=y
CONFIG_FONT_MINI_4x6=y
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set
# CONFIG_FONT_10x18 is not set
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
# CONFIG_LOGO_LINUX_CLUT224 is not set
# CONFIG_SOUND is not set
# CONFIG_HID_SUPPORT is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
CONFIG_USB_DEBUG=y
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set

#
# Miscellaneous USB options
#
# CONFIG_USB_DEVICEFS is not set
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_MON is not set
CONFIG_USB_WUSB=y
# CONFIG_USB_WUSB_CBAF is not set

#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
# CONFIG_USB_XHCI_HCD is not set
# CONFIG_USB_EHCI_HCD is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_ISP1760_HCD=y
CONFIG_USB_ISP1362_HCD=y
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
CONFIG_USB_WHCI_HCD=y
CONFIG_USB_HWA_HCD=y

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

#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#

#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=y
CONFIG_USB_STORAGE_DEBUG=y
# CONFIG_USB_STORAGE_DATAFAB is not set
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_USBAT=y
# CONFIG_USB_STORAGE_SDDR09 is not set
CONFIG_USB_STORAGE_SDDR55=y
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_ONETOUCH is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
# CONFIG_USB_UAS is not set
# CONFIG_USB_LIBUSUAL is not set

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

#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=y
CONFIG_USB_EMI26=y
# CONFIG_USB_ADUTUX is not set
CONFIG_USB_SEVSEG=y
CONFIG_USB_RIO500=y
# CONFIG_USB_LEGOTOWER is not set
CONFIG_USB_LCD=y
CONFIG_USB_LED=y
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
CONFIG_USB_IDMOUSE=y
# CONFIG_USB_FTDI_ELAN is not set
CONFIG_USB_APPLEDISPLAY=y
CONFIG_USB_LD=y
# CONFIG_USB_TRANCEVIBRATOR is not set
CONFIG_USB_IOWARRIOR=y
CONFIG_USB_TEST=y
CONFIG_USB_ISIGHTFW=y
# CONFIG_USB_YUREX is not set
# CONFIG_USB_ATM is not set
# CONFIG_USB_GADGET is not set

#
# OTG and related infrastructure
#
# CONFIG_TWL4030_USB is not set
# CONFIG_NOP_USB_XCEIV is not set
CONFIG_UWB=y
CONFIG_UWB_HWA=y
CONFIG_UWB_WHCI=y
# CONFIG_UWB_I1480U is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y

#
# LED drivers
#
# CONFIG_LEDS_88PM860X is not set
# CONFIG_LEDS_INPUT is not set
CONFIG_LEDS_PCA9532=y
CONFIG_LEDS_LP3944=y
CONFIG_LEDS_LP5521=y
CONFIG_LEDS_LP5523=y
CONFIG_LEDS_CLEVO_MAIL=y
CONFIG_LEDS_PCA955X=y
# CONFIG_LEDS_WM8350 is not set
CONFIG_LEDS_DA903X=y
# CONFIG_LEDS_DAC124S085 is not set
# CONFIG_LEDS_REGULATOR is not set
CONFIG_LEDS_BD2802=y
CONFIG_LEDS_INTEL_SS4200=y
# CONFIG_LEDS_MC13783 is not set
CONFIG_LEDS_TRIGGERS=y

#
# LED Triggers
#
# CONFIG_LEDS_TRIGGER_TIMER is not set
CONFIG_LEDS_TRIGGER_HEARTBEAT=y
CONFIG_LEDS_TRIGGER_BACKLIGHT=y
# CONFIG_LEDS_TRIGGER_DEFAULT_ON is not set

#
# iptables trigger is under Netfilter config (LED target)
#
CONFIG_NFC_DEVICES=y
CONFIG_PN544_NFC=y
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
# CONFIG_EDAC is not set
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
# CONFIG_AUXDISPLAY is not set
CONFIG_UIO=y
CONFIG_UIO_CIF=y
# CONFIG_UIO_PDRV is not set
CONFIG_UIO_PDRV_GENIRQ=y
CONFIG_UIO_AEC=y
# CONFIG_UIO_SERCOS3 is not set
CONFIG_UIO_PCI_GENERIC=y
# CONFIG_UIO_NETX is not set
CONFIG_STAGING=y
# CONFIG_STAGING_EXCLUDE_BUILD is not set
CONFIG_BKL=y
# CONFIG_VIDEO_TM6000 is not set
CONFIG_USB_IP_COMMON=y
# CONFIG_USB_IP_VHCI_HCD is not set
CONFIG_USB_IP_HOST=y
CONFIG_USB_IP_DEBUG_ENABLE=y
# CONFIG_ECHO is not set
# CONFIG_ASUS_OLED is not set
CONFIG_TRANZPORT=y
CONFIG_POHMELFS=y
# CONFIG_POHMELFS_DEBUG is not set
CONFIG_POHMELFS_CRYPTO=y
CONFIG_AUTOFS_FS=y
CONFIG_DRM_VMWGFX=y
CONFIG_DRM_NOUVEAU=y
CONFIG_DRM_NOUVEAU_BACKLIGHT=y
CONFIG_DRM_NOUVEAU_DEBUG=y

#
# I2C encoder or helper chips
#
CONFIG_DRM_I2C_CH7006=y
# CONFIG_DRM_I2C_SIL164 is not set
CONFIG_FB_UDL=y
# CONFIG_VME_BUS is not set
CONFIG_DX_SEP=y
CONFIG_IIO=y
CONFIG_IIO_RING_BUFFER=y
CONFIG_IIO_SW_RING=y
CONFIG_IIO_TRIGGER=y

#
# Accelerometers
#
# CONFIG_ADIS16201 is not set
# CONFIG_ADIS16203 is not set
CONFIG_ADIS16204=y
CONFIG_ADIS16209=y
# CONFIG_ADIS16220 is not set
# CONFIG_ADIS16240 is not set
# CONFIG_KXSD9 is not set
# CONFIG_LIS3L02DQ is not set
CONFIG_SCA3000=y

#
# Analog to digital convertors
#
CONFIG_MAX1363=y
CONFIG_MAX1363_RING_BUFFER=y
# CONFIG_AD7150 is not set
CONFIG_AD7152=y
CONFIG_AD7291=y
CONFIG_AD7298=y
# CONFIG_AD7314 is not set
CONFIG_AD799X=y
CONFIG_AD799X_RING_BUFFER=y
CONFIG_AD7476=y
CONFIG_AD7887=y
# CONFIG_AD7745 is not set
CONFIG_AD7816=y
# CONFIG_ADT75 is not set
CONFIG_ADT7310=y
# CONFIG_ADT7410 is not set

#
# Analog digital bi-direction convertors
#
# CONFIG_ADT7316 is not set

#
# Digital to analog convertors
#
CONFIG_AD5624R_SPI=y
CONFIG_AD5446=y

#
# Direct Digital Synthesis
#
CONFIG_AD5930=y
# CONFIG_AD9832 is not set
# CONFIG_AD9850 is not set
# CONFIG_AD9852 is not set
# CONFIG_AD9910 is not set
# CONFIG_AD9951 is not set

#
# Digital gyroscope sensors
#
# CONFIG_ADIS16060 is not set
CONFIG_ADIS16080=y
CONFIG_ADIS16130=y
CONFIG_ADIS16260=y
# CONFIG_ADIS16251 is not set

#
# Inertial measurement units
#
CONFIG_ADIS16300=y
CONFIG_ADIS16350=y
# CONFIG_ADIS16400 is not set

#
# Light sensors
#
CONFIG_SENSORS_TSL2563=y
# CONFIG_SENSORS_ISL29018 is not set

#
# Magnetometer sensors
#
CONFIG_SENSORS_AK8975=y
CONFIG_SENSORS_HMC5843=y

#
# Active energy metering IC
#
CONFIG_ADE7753=y
# CONFIG_ADE7754 is not set
CONFIG_ADE7758=y
CONFIG_ADE7759=y
# CONFIG_ADE7854 is not set

#
# Resolver to digital converters
#
CONFIG_AD2S90=y
# CONFIG_AD2S120X is not set
CONFIG_AD2S1210=y
CONFIG_AD2S1210_GPIO_INPUT=y
# CONFIG_AD2S1210_GPIO_OUTPUT is not set
# CONFIG_AD2S1210_GPIO_NONE is not set

#
# Triggers - standalone
#
# CONFIG_ZRAM is not set
CONFIG_BATMAN_ADV=y
CONFIG_BATMAN_ADV_DEBUG=y
CONFIG_FB_SM7XX=y
CONFIG_VIDEO_DT3155=y
# CONFIG_DT3155_CCIR is not set
# CONFIG_CRYSTALHD is not set

#
# Texas Instruments shared transport line discipline
#
# CONFIG_ADIS16255 is not set
CONFIG_FB_XGI=y
# CONFIG_LIRC_STAGING is not set
CONFIG_SMB_FS=y
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
CONFIG_EASYCAP=y
# CONFIG_ACPI_QUICKSTART is not set
CONFIG_MACH_NO_WESTBRIDGE=y
# CONFIG_BCM_WIMAX is not set
CONFIG_FT1000=y
CONFIG_FT1000_USB=y

#
# Speakup console speech
#
# CONFIG_SPEAKUP is not set
# CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI4 is not set
# CONFIG_X86_PLATFORM_DEVICES is not set

#
# Firmware Drivers
#
CONFIG_EDD=y
# CONFIG_EDD_OFF is not set
CONFIG_FIRMWARE_MEMMAP=y
CONFIG_EFI_VARS=y
CONFIG_DELL_RBU=y
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y
CONFIG_ISCSI_IBFT_FIND=y
CONFIG_ISCSI_IBFT=y

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
# CONFIG_EXT2_FS_POSIX_ACL is not set
# CONFIG_EXT2_FS_SECURITY is not set
CONFIG_EXT2_FS_XIP=y
CONFIG_EXT3_FS=y
# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_EXT4_FS=y
# CONFIG_EXT4_FS_XATTR is not set
CONFIG_EXT4_DEBUG=y
CONFIG_FS_XIP=y
CONFIG_JBD=y
CONFIG_JBD_DEBUG=y
CONFIG_JBD2=y
CONFIG_JBD2_DEBUG=y
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# 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=y
# CONFIG_JFS_POSIX_ACL is not set
# CONFIG_JFS_SECURITY is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=y
# CONFIG_XFS_QUOTA is not set
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
CONFIG_XFS_DEBUG=y
CONFIG_GFS2_FS=y
CONFIG_GFS2_FS_LOCKING_DLM=y
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
CONFIG_NILFS2_FS=y
CONFIG_EXPORTFS=y
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
# CONFIG_INOTIFY_USER is not set
# CONFIG_FANOTIFY is not set
CONFIG_QUOTA=y
# CONFIG_QUOTA_NETLINK_INTERFACE is not set
# CONFIG_PRINT_QUOTA_WARNING is not set
# CONFIG_QUOTA_DEBUG is not set
CONFIG_QUOTA_TREE=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set

#
# Caches
#
# CONFIG_FSCACHE is not set

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

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

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
# CONFIG_TMPFS is not set
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_CONFIGFS_FS=y
# CONFIG_MISC_FILESYSTEMS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_V4_1 is not set
# CONFIG_ROOT_NFS is not set
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
CONFIG_NFS_USE_NEW_IDMAPPER=y
CONFIG_NFSD=y
# CONFIG_NFSD_DEPRECATED is not set
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_V4 is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
CONFIG_CEPH_FS=y
CONFIG_CIFS=y
CONFIG_CIFS_STATS=y
CONFIG_CIFS_STATS2=y
# CONFIG_CIFS_WEAK_PW_HASH is not set
# CONFIG_CIFS_UPCALL is not set
# CONFIG_CIFS_XATTR is not set
CONFIG_CIFS_DEBUG2=y
# CONFIG_CIFS_DFS_UPCALL is not set
CONFIG_CIFS_EXPERIMENTAL=y
CONFIG_NCP_FS=y
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_NLS is not set
CONFIG_NCPFS_EXTRAS=y
# CONFIG_CODA_FS is not set
CONFIG_AFS_FS=y
# CONFIG_AFS_DEBUG is not set
# CONFIG_9P_FS is not set

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

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
# CONFIG_ENABLE_WARN_DEPRECATED is not set
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=1024
# CONFIG_MAGIC_SYSRQ is not set
CONFIG_STRIP_ASM_SYMS=y
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_DEBUG_FS=y
CONFIG_HEADERS_CHECK=y
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_HARDLOCKUP_DETECTOR is not set
CONFIG_SLUB_DEBUG_ON=y
# CONFIG_SLUB_STATS is not set
CONFIG_SPARSE_RCU_POINTER=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_MEMORY_INIT=y
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_FRAME_POINTER=y
CONFIG_RCU_CPU_STALL_DETECTOR=y
CONFIG_RCU_CPU_STALL_TIMEOUT=60
CONFIG_RCU_CPU_STALL_DETECTOR_RUNNABLE=y
CONFIG_LKDTM=y
CONFIG_SYSCTL_SYSCALL_CHECK=y
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_C_RECORDMCOUNT=y
CONFIG_TRACING_SUPPORT=y
# CONFIG_FTRACE is not set
CONFIG_PROVIDE_OHCI1394_DMA_INIT=y
# CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set
# CONFIG_BUILD_DOCSRC is not set
CONFIG_DYNAMIC_DEBUG=y
# CONFIG_DMA_API_DEBUG is not set
CONFIG_ATOMIC64_SELFTEST=y
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
CONFIG_HAVE_ARCH_KMEMCHECK=y
# CONFIG_STRICT_DEVMEM is not set
# CONFIG_X86_VERBOSE_BOOTUP is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_EARLY_PRINTK_DBGP is not set
CONFIG_DOUBLEFAULT=y
# CONFIG_IOMMU_STRESS is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
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=y
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=1
# CONFIG_OPTIMIZE_INLINING is not set

#
# Security options
#
CONFIG_KEYS=y
# CONFIG_TRUSTED_KEYS is not set
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
CONFIG_SECURITY_DMESG_RESTRICT=y
CONFIG_SECURITY=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_NETWORK_XFRM is not set
CONFIG_SECURITY_PATH=y
# CONFIG_SECURITY_SELINUX is not set
# CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
CONFIG_SECURITY_APPARMOR=y
CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
CONFIG_IMA=y
CONFIG_IMA_MEASURE_PCR_IDX=10
CONFIG_IMA_AUDIT=y
# CONFIG_DEFAULT_SECURITY_APPARMOR is not set
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_DEFAULT_SECURITY=""
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
# CONFIG_CRYPTO_FIPS is not set
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
CONFIG_CRYPTO_GF128MUL=y
CONFIG_CRYPTO_NULL=y
CONFIG_CRYPTO_PCRYPT=y
CONFIG_CRYPTO_WORKQUEUE=y
CONFIG_CRYPTO_CRYPTD=y
CONFIG_CRYPTO_AUTHENC=y

#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
CONFIG_CRYPTO_GCM=y
CONFIG_CRYPTO_SEQIV=y

#
# Block modes
#
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_CTR=y
# CONFIG_CRYPTO_CTS is not set
CONFIG_CRYPTO_ECB=y
CONFIG_CRYPTO_LRW=y
CONFIG_CRYPTO_PCBC=y
CONFIG_CRYPTO_XTS=y

#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_VMAC is not set

#
# Digest
#
CONFIG_CRYPTO_CRC32C=y
# CONFIG_CRYPTO_CRC32C_INTEL is not set
CONFIG_CRYPTO_GHASH=y
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
CONFIG_CRYPTO_RMD128=y
CONFIG_CRYPTO_RMD160=y
# CONFIG_CRYPTO_RMD256 is not set
CONFIG_CRYPTO_RMD320=y
CONFIG_CRYPTO_SHA1=y
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
CONFIG_CRYPTO_WP512=y

#
# Ciphers
#
CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_AES_586 is not set
CONFIG_CRYPTO_ANUBIS=y
CONFIG_CRYPTO_ARC4=y
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
CONFIG_CRYPTO_CAST6=y
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_FCRYPT=y
CONFIG_CRYPTO_KHAZAD=y
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_586 is not set
CONFIG_CRYPTO_SEED=y
CONFIG_CRYPTO_SERPENT=y
# CONFIG_CRYPTO_TEA is not set
CONFIG_CRYPTO_TWOFISH=y
CONFIG_CRYPTO_TWOFISH_COMMON=y
# CONFIG_CRYPTO_TWOFISH_586 is not set

#
# Compression
#
CONFIG_CRYPTO_DEFLATE=y
# CONFIG_CRYPTO_ZLIB is not set
# CONFIG_CRYPTO_LZO is not set

#
# Random Number Generation
#
CONFIG_CRYPTO_ANSI_CPRNG=y
# CONFIG_CRYPTO_USER_API_HASH is not set
# CONFIG_CRYPTO_USER_API_SKCIPHER is not set
CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO_DEV_PADLOCK=y
CONFIG_CRYPTO_DEV_PADLOCK_AES=y
# CONFIG_CRYPTO_DEV_PADLOCK_SHA is not set
CONFIG_CRYPTO_DEV_GEODE=y
CONFIG_CRYPTO_DEV_HIFN_795X=y
CONFIG_CRYPTO_DEV_HIFN_795X_RNG=y
CONFIG_HAVE_KVM=y
CONFIG_HAVE_KVM_IRQCHIP=y
CONFIG_HAVE_KVM_EVENTFD=y
CONFIG_KVM_APIC_ARCHITECTURE=y
CONFIG_KVM_MMIO=y
CONFIG_KVM_ASYNC_PF=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=y
CONFIG_KVM_INTEL=y
# CONFIG_KVM_AMD is not set
CONFIG_VHOST_NET=y
CONFIG_LGUEST=y
CONFIG_VIRTIO=y
CONFIG_VIRTIO_RING=y
CONFIG_VIRTIO_PCI=y
CONFIG_VIRTIO_BALLOON=y
# CONFIG_BINARY_PRINTF is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_FIND_LAST_BIT=y
CONFIG_CRC_CCITT=y
CONFIG_CRC16=y
CONFIG_CRC_T10DIF=y
CONFIG_CRC_ITU_T=y
CONFIG_CRC32=y
CONFIG_CRC7=y
CONFIG_LIBCRC32C=y
CONFIG_AUDIT_GENERIC=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_DECOMPRESS_LZO=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=y
CONFIG_TEXTSEARCH_BM=y
CONFIG_TEXTSEARCH_FSM=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_CHECK_SIGNATURE=y
CONFIG_NLATTR=y
CONFIG_SHM_SIGNAL=y
# CONFIG_IOQ is not set

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: mmotm 2010-12-02-16-34 uploaded (netfilter-related)
  2010-12-03  0:34 ` akpm
  (?)
  (?)
@ 2010-12-03 17:37 ` Randy Dunlap
  -1 siblings, 0 replies; 77+ messages in thread
From: Randy Dunlap @ 2010-12-03 17:37 UTC (permalink / raw)
  To: linux-kernel; +Cc: akpm, netdev

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

On Thu, 02 Dec 2010 16:34:54 -0800 akpm@linux-foundation.org wrote:

> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> 
>    http://userweb.kernel.org/~akpm/mmotm/
> 
> and will soon be available at
> 
>    git://zen-kernel.org/kernel/mmotm.git
> 
> It contains the following patches against 2.6.37-rc4:


When CONFIG_NF_CONNTRACK is not enabled:

mmotm-2010-1202-1634/include/net/netfilter/nf_conntrack.h:94: error: field 'ct_general' has incomplete type
mmotm-2010-1202-1634/include/net/netfilter/nf_conntrack.h: In function 'nf_ct_get':
mmotm-2010-1202-1634/include/net/netfilter/nf_conntrack.h:174: error: 'const struct sk_buff' has no member named 'nfct'
mmotm-2010-1202-1634/include/net/netfilter/nf_conntrack.h: In function 'nf_ct_put':
mmotm-2010-1202-1634/include/net/netfilter/nf_conntrack.h:181: error: implicit declaration of function 'nf_conntrack_put'
In file included from mmotm-2010-1202-1634/include/net/netfilter/nf_conntrack_core.h:18,
                 from mmotm-2010-1202-1634/net/ipv6/netfilter/nf_defrag_ipv6_hooks.c:26:
mmotm-2010-1202-1634/include/net/netfilter/nf_conntrack_ecache.h: In function 'nf_ct_ecache_ext_add':
mmotm-2010-1202-1634/include/net/netfilter/nf_conntrack_ecache.h:35: error: 'struct net' has no member named 'ct'
In file included from mmotm-2010-1202-1634/net/ipv6/netfilter/nf_defrag_ipv6_hooks.c:26:
mmotm-2010-1202-1634/include/net/netfilter/nf_conntrack_core.h: In function 'nf_conntrack_confirm':
mmotm-2010-1202-1634/include/net/netfilter/nf_conntrack_core.h:60: error: 'struct sk_buff' has no member named 'nfct'
mmotm-2010-1202-1634/net/ipv6/netfilter/nf_defrag_ipv6_hooks.c: In function 'nf_ct6_defrag_user':
mmotm-2010-1202-1634/net/ipv6/netfilter/nf_defrag_ipv6_hooks.c:36: error: 'struct sk_buff' has no member named 'nfct'
mmotm-2010-1202-1634/net/ipv6/netfilter/nf_defrag_ipv6_hooks.c:37: error: implicit declaration of function 'nf_ct_zone'
mmotm-2010-1202-1634/net/ipv6/netfilter/nf_defrag_ipv6_hooks.c:37: error: 'struct sk_buff' has no member named 'nfct'
mmotm-2010-1202-1634/net/ipv6/netfilter/nf_defrag_ipv6_hooks.c: In function 'ipv6_defrag':
mmotm-2010-1202-1634/net/ipv6/netfilter/nf_defrag_ipv6_hooks.c:60: error: 'struct sk_buff' has no member named 'nfct'
mmotm-2010-1202-1634/net/ipv6/netfilter/nf_defrag_ipv6_hooks.c:60: error: 'struct sk_buff' has no member named 'nfct'
mmotm-2010-1202-1634/net/ipv6/netfilter/nf_conntrack_reasm.c: In function 'nf_ct_frag6_output':
mmotm-2010-1202-1634/net/ipv6/netfilter/nf_conntrack_reasm.c:598: error: implicit declaration of function 'nf_conntrack_put_reasm'
mmotm-2010-1202-1634/net/ipv6/netfilter/nf_conntrack_reasm.c:598: error: 'struct sk_buff' has no member named 'nfct_reasm'
mmotm-2010-1202-1634/net/ipv6/netfilter/nf_conntrack_reasm.c:599: error: implicit declaration of function 'nf_conntrack_get_reasm'
mmotm-2010-1202-1634/net/ipv6/netfilter/nf_conntrack_reasm.c:600: error: 'struct sk_buff' has no member named 'nfct_reasm'


kernel .config file is attached.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

[-- Attachment #2: config-r9490 --]
[-- Type: application/octet-stream, Size: 47341 bytes --]

#
# Automatically generated make config: don't edit
# Linux/x86_64 2.6.37-rc4-mm1 Kernel Configuration
# Thu Dec  2 18:16:33 2010
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
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_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
# CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set
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_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11"
# CONFIG_KTIME_SCALAR is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_CONSTRUCTORS=y
CONFIG_HAVE_IRQ_WORK=y
CONFIG_IRQ_WORK=y

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_LZO=y
# CONFIG_KERNEL_GZIP is not set
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
CONFIG_KERNEL_LZO=y
# CONFIG_SWAP is not set
# CONFIG_SYSVIPC is not set
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
CONFIG_HAVE_GENERIC_HARDIRQS=y

#
# IRQ subsystem
#
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
# CONFIG_GENERIC_HARDIRQS_NO_DEPRECATED is not set
CONFIG_HAVE_SPARSE_IRQ=y
CONFIG_GENERIC_IRQ_PROBE=y
# CONFIG_GENERIC_PENDING_IRQ is not set
# CONFIG_AUTO_IRQ_AFFINITY is not set
# CONFIG_IRQ_PER_CPU is not set
# CONFIG_HARDIRQS_SW_RESEND is not set
# CONFIG_SPARSE_IRQ is not set

#
# RCU Subsystem
#
CONFIG_TINY_RCU=y
# CONFIG_PREEMPT_RCU is not set
# CONFIG_RCU_TRACE is not set
# CONFIG_TREE_RCU_TRACE is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=17
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
# CONFIG_CGROUPS is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
# CONFIG_NET_NS is not set
# CONFIG_SYSFS_DEPRECATED is not set
CONFIG_RELAY=y
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
# CONFIG_EMBEDDED is not set
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_HAVE_PERF_EVENTS=y

#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_PERF_COUNTERS is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_PROFILING is not set
CONFIG_HAVE_OPROFILE=y
CONFIG_JUMP_LABEL=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y
CONFIG_HAVE_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_PERF_EVENTS_NMI=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y

#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
# CONFIG_MODULES is not set
CONFIG_BLOCK=y
CONFIG_BLK_DEV_BSG=y
# CONFIG_BLK_DEV_INTEGRITY is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
# CONFIG_IOSCHED_CFQ is not set
CONFIG_DEFAULT_DEADLINE=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="deadline"
# CONFIG_INLINE_SPIN_TRYLOCK is not set
# CONFIG_INLINE_SPIN_TRYLOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK is not set
# CONFIG_INLINE_SPIN_LOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK_IRQ is not set
# CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set
CONFIG_INLINE_SPIN_UNLOCK=y
# CONFIG_INLINE_SPIN_UNLOCK_BH is not set
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
# CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_READ_TRYLOCK is not set
# CONFIG_INLINE_READ_LOCK is not set
# CONFIG_INLINE_READ_LOCK_BH is not set
# CONFIG_INLINE_READ_LOCK_IRQ is not set
# CONFIG_INLINE_READ_LOCK_IRQSAVE is not set
CONFIG_INLINE_READ_UNLOCK=y
# CONFIG_INLINE_READ_UNLOCK_BH is not set
CONFIG_INLINE_READ_UNLOCK_IRQ=y
# CONFIG_INLINE_READ_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_WRITE_TRYLOCK is not set
# CONFIG_INLINE_WRITE_LOCK is not set
# CONFIG_INLINE_WRITE_LOCK_BH is not set
# CONFIG_INLINE_WRITE_LOCK_IRQ is not set
# CONFIG_INLINE_WRITE_LOCK_IRQSAVE is not set
CONFIG_INLINE_WRITE_UNLOCK=y
# CONFIG_INLINE_WRITE_UNLOCK_BH is not set
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
# CONFIG_INLINE_WRITE_UNLOCK_IRQRESTORE is not set
# CONFIG_MUTEX_SPIN_ON_OWNER is not set
# CONFIG_FREEZER is not set

#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
# CONFIG_SMP is not set
CONFIG_X86_MPPARSE=y
# CONFIG_X86_EXTENDED_PLATFORM is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_SCHED_OMIT_FRAME_POINTER is not set
CONFIG_PARAVIRT_GUEST=y
CONFIG_XEN=y
# CONFIG_XEN_PRIVILEGED_GUEST is not set
CONFIG_XEN_PVHVM=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=128
CONFIG_XEN_DEBUG_FS=y
# CONFIG_KVM_CLOCK is not set
# CONFIG_KVM_GUEST is not set
CONFIG_PARAVIRT=y
CONFIG_PARAVIRT_CLOCK=y
CONFIG_NO_BOOTMEM=y
# CONFIG_MEMTEST is not set
# CONFIG_MK8 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_CPU=y
CONFIG_X86_INTERNODE_CACHE_SHIFT=6
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_HPET_TIMER=y
CONFIG_DMI=y
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
# CONFIG_IOMMU_API is not set
CONFIG_NR_CPUS=1
# CONFIG_IRQ_TIME_ACCOUNTING is not set
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
# CONFIG_X86_MCE_AMD is not set
CONFIG_X86_MCE_THRESHOLD=y
# CONFIG_X86_MCE_INJECT is not set
CONFIG_X86_THERMAL_VECTOR=y
CONFIG_I8K=y
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
CONFIG_X86_CPUID=y
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_ARCH_DMA_ADDR_T_64BIT=y
CONFIG_DIRECT_GBPAGES=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_MEMORY_PROBE=y
CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y
CONFIG_SPARSEMEM_VMEMMAP=y
CONFIG_HAVE_MEMBLOCK=y
CONFIG_MEMORY_HOTPLUG=y
CONFIG_MEMORY_HOTPLUG_SPARSE=y
CONFIG_MEMORY_HOTREMOVE=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_COMPACTION=y
CONFIG_MIGRATION=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_KSM=y
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
CONFIG_MEMORY_FAILURE=y
CONFIG_NEED_PER_CPU_KM=y
# CONFIG_CLEANCACHE is not set
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
CONFIG_X86_RESERVE_LOW=64
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
CONFIG_X86_PAT=y
CONFIG_ARCH_USES_PG_UNCACHED=y
# CONFIG_SECCOMP is not set
CONFIG_CC_STACKPROTECTOR=y
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
CONFIG_SCHED_HRTICK=y
# CONFIG_KEXEC is not set
CONFIG_CRASH_DUMP=y
CONFIG_PHYSICAL_START=0x1000000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x1000000
CONFIG_CMDLINE_BOOL=y
CONFIG_CMDLINE=""
# CONFIG_CMDLINE_OVERRIDE is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y

#
# Power management and ACPI options
#
# CONFIG_PM is not set
CONFIG_SFI=y

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
# CONFIG_INTEL_IDLE is not set

#
# Memory power savings
#
# CONFIG_I7300_IDLE is not set

#
# Bus options (PCI etc.)
#
# CONFIG_PCI is not set
# CONFIG_ARCH_SUPPORTS_MSI is not set
CONFIG_ISA_DMA_API=y
CONFIG_PCCARD=y
# CONFIG_PCMCIA is not set

#
# PC-card bridges
#
# CONFIG_VBUS_PROXY is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
# CONFIG_HAVE_AOUT is not set
# CONFIG_BINFMT_MISC is not set
# CONFIG_IA32_EMULATION is not set
# CONFIG_COMPAT_FOR_U64_ALIGNMENT is not set
CONFIG_HAVE_TEXT_POKE_SMP=y
CONFIG_NET=y

#
# Networking options
#
# CONFIG_PACKET is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
CONFIG_XFRM_MIGRATE=y
# CONFIG_XFRM_STATISTICS is not set
CONFIG_XFRM_IPCOMP=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
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 is not set
CONFIG_IP_ROUTE_MULTIPATH=y
# CONFIG_IP_ROUTE_VERBOSE is not set
CONFIG_IP_PNP=y
# CONFIG_IP_PNP_DHCP is not set
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
# CONFIG_NET_IPIP is not set
CONFIG_NET_IPGRE_DEMUX=y
# CONFIG_NET_IPGRE is not set
CONFIG_ARPD=y
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
CONFIG_INET_TUNNEL=y
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
# CONFIG_INET_XFRM_MODE_BEET is not set
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=y
CONFIG_TCP_CONG_CUBIC=y
# CONFIG_TCP_CONG_WESTWOOD is not set
CONFIG_TCP_CONG_HTCP=y
# CONFIG_TCP_CONG_HSTCP is not set
# CONFIG_TCP_CONG_HYBLA is not set
CONFIG_TCP_CONG_VEGAS=y
CONFIG_TCP_CONG_SCALABLE=y
CONFIG_TCP_CONG_LP=y
# CONFIG_TCP_CONG_VENO is not set
CONFIG_TCP_CONG_YEAH=y
CONFIG_TCP_CONG_ILLINOIS=y
# CONFIG_DEFAULT_BIC is not set
# CONFIG_DEFAULT_CUBIC is not set
CONFIG_DEFAULT_HTCP=y
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="htcp"
CONFIG_TCP_MD5SIG=y
CONFIG_IPV6=y
# CONFIG_IPV6_PRIVACY is not set
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
CONFIG_IPV6_OPTIMISTIC_DAD=y
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
CONFIG_INET6_IPCOMP=y
# CONFIG_IPV6_MIP6 is not set
CONFIG_INET6_XFRM_TUNNEL=y
CONFIG_INET6_TUNNEL=y
# CONFIG_INET6_XFRM_MODE_TRANSPORT is not set
CONFIG_INET6_XFRM_MODE_TUNNEL=y
# CONFIG_INET6_XFRM_MODE_BEET is not set
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
CONFIG_IPV6_SIT=y
# CONFIG_IPV6_SIT_6RD is not set
CONFIG_IPV6_NDISC_NODETYPE=y
# CONFIG_IPV6_TUNNEL is not set
CONFIG_IPV6_MULTIPLE_TABLES=y
# CONFIG_IPV6_SUBTREES is not set
# CONFIG_IPV6_MROUTE is not set
CONFIG_NETLABEL=y
CONFIG_NETWORK_SECMARK=y
CONFIG_NETWORK_PHY_TIMESTAMPING=y
CONFIG_NETFILTER=y
CONFIG_NETFILTER_DEBUG=y
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=y
CONFIG_NETFILTER_NETLINK_QUEUE=y
# CONFIG_NETFILTER_NETLINK_LOG is not set
# CONFIG_NF_CONNTRACK is not set
CONFIG_NETFILTER_TPROXY=y
CONFIG_NETFILTER_XTABLES=y

#
# Xtables combined modules
#
CONFIG_NETFILTER_XT_MARK=y

#
# Xtables targets
#
CONFIG_NETFILTER_XT_TARGET_CHECKSUM=y
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=y
# CONFIG_NETFILTER_XT_TARGET_DSCP is not set
CONFIG_NETFILTER_XT_TARGET_HL=y
# CONFIG_NETFILTER_XT_TARGET_IDLETIMER is not set
CONFIG_NETFILTER_XT_TARGET_LED=y
CONFIG_NETFILTER_XT_TARGET_MARK=y
# CONFIG_NETFILTER_XT_TARGET_NFLOG is not set
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=y
CONFIG_NETFILTER_XT_TARGET_RATEEST=y
# CONFIG_NETFILTER_XT_TARGET_TEE is not set
CONFIG_NETFILTER_XT_TARGET_TPROXY=y
# CONFIG_NETFILTER_XT_TARGET_TRACE is not set
# CONFIG_NETFILTER_XT_TARGET_SECMARK is not set
# CONFIG_NETFILTER_XT_TARGET_TCPMSS is not set
# CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is not set

#
# Xtables matches
#
# CONFIG_NETFILTER_XT_MATCH_COMMENT is not set
# CONFIG_NETFILTER_XT_MATCH_CPU is not set
# CONFIG_NETFILTER_XT_MATCH_DCCP is not set
CONFIG_NETFILTER_XT_MATCH_DSCP=y
CONFIG_NETFILTER_XT_MATCH_ESP=y
# CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is not set
CONFIG_NETFILTER_XT_MATCH_HL=y
CONFIG_NETFILTER_XT_MATCH_IPRANGE=y
# CONFIG_NETFILTER_XT_MATCH_LENGTH is not set
# CONFIG_NETFILTER_XT_MATCH_LIMIT is not set
CONFIG_NETFILTER_XT_MATCH_MAC=y
# CONFIG_NETFILTER_XT_MATCH_MARK is not set
# CONFIG_NETFILTER_XT_MATCH_MULTIPORT is not set
CONFIG_NETFILTER_XT_MATCH_OSF=y
CONFIG_NETFILTER_XT_MATCH_OWNER=y
CONFIG_NETFILTER_XT_MATCH_POLICY=y
# CONFIG_NETFILTER_XT_MATCH_PHYSDEV is not set
# CONFIG_NETFILTER_XT_MATCH_PKTTYPE is not set
# CONFIG_NETFILTER_XT_MATCH_QUOTA is not set
# CONFIG_NETFILTER_XT_MATCH_RATEEST is not set
# CONFIG_NETFILTER_XT_MATCH_REALM is not set
CONFIG_NETFILTER_XT_MATCH_RECENT=y
CONFIG_NETFILTER_XT_MATCH_SCTP=y
CONFIG_NETFILTER_XT_MATCH_SOCKET=y
CONFIG_NETFILTER_XT_MATCH_STATISTIC=y
CONFIG_NETFILTER_XT_MATCH_STRING=y
CONFIG_NETFILTER_XT_MATCH_TCPMSS=y
# CONFIG_NETFILTER_XT_MATCH_TIME is not set
CONFIG_NETFILTER_XT_MATCH_U32=y
# CONFIG_IP_VS is not set

#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=y
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=y
# CONFIG_IP_NF_MATCH_ADDRTYPE is not set
# CONFIG_IP_NF_MATCH_AH is not set
# CONFIG_IP_NF_MATCH_ECN is not set
# CONFIG_IP_NF_MATCH_TTL is not set
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
# CONFIG_IP_NF_TARGET_LOG is not set
CONFIG_IP_NF_TARGET_ULOG=y
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_ECN=y
# CONFIG_IP_NF_TARGET_TTL is not set
CONFIG_IP_NF_RAW=y
# CONFIG_IP_NF_SECURITY is not set
# CONFIG_IP_NF_ARPTABLES is not set

#
# IPv6: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV6=y
CONFIG_IP6_NF_QUEUE=y
CONFIG_IP6_NF_IPTABLES=y
# CONFIG_IP6_NF_MATCH_AH is not set
# CONFIG_IP6_NF_MATCH_EUI64 is not set
CONFIG_IP6_NF_MATCH_FRAG=y
# CONFIG_IP6_NF_MATCH_OPTS is not set
CONFIG_IP6_NF_MATCH_HL=y
# CONFIG_IP6_NF_MATCH_IPV6HEADER is not set
# CONFIG_IP6_NF_MATCH_MH is not set
CONFIG_IP6_NF_MATCH_RT=y
CONFIG_IP6_NF_TARGET_HL=y
# CONFIG_IP6_NF_TARGET_LOG is not set
CONFIG_IP6_NF_FILTER=y
# CONFIG_IP6_NF_TARGET_REJECT is not set
CONFIG_IP6_NF_MANGLE=y
# CONFIG_IP6_NF_RAW is not set
# CONFIG_IP6_NF_SECURITY is not set

#
# DECnet: Netfilter Configuration
#
CONFIG_DECNET_NF_GRABULATOR=y
CONFIG_BRIDGE_NF_EBTABLES=y
CONFIG_BRIDGE_EBT_BROUTE=y
CONFIG_BRIDGE_EBT_T_FILTER=y
CONFIG_BRIDGE_EBT_T_NAT=y
CONFIG_BRIDGE_EBT_802_3=y
# CONFIG_BRIDGE_EBT_AMONG is not set
CONFIG_BRIDGE_EBT_ARP=y
CONFIG_BRIDGE_EBT_IP=y
# CONFIG_BRIDGE_EBT_IP6 is not set
CONFIG_BRIDGE_EBT_LIMIT=y
CONFIG_BRIDGE_EBT_MARK=y
CONFIG_BRIDGE_EBT_PKTTYPE=y
CONFIG_BRIDGE_EBT_STP=y
CONFIG_BRIDGE_EBT_VLAN=y
# CONFIG_BRIDGE_EBT_ARPREPLY is not set
CONFIG_BRIDGE_EBT_DNAT=y
CONFIG_BRIDGE_EBT_MARK_T=y
CONFIG_BRIDGE_EBT_REDIRECT=y
CONFIG_BRIDGE_EBT_SNAT=y
# CONFIG_BRIDGE_EBT_LOG is not set
CONFIG_BRIDGE_EBT_ULOG=y
CONFIG_BRIDGE_EBT_NFLOG=y
# CONFIG_IP_DCCP is not set
CONFIG_IP_SCTP=y
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
CONFIG_SCTP_HMAC_NONE=y
# CONFIG_SCTP_HMAC_SHA1 is not set
# CONFIG_SCTP_HMAC_MD5 is not set
# CONFIG_RDS is not set
CONFIG_TIPC=y
# CONFIG_TIPC_ADVANCED is not set
# CONFIG_TIPC_DEBUG is not set
# CONFIG_ATM is not set
CONFIG_L2TP=y
# CONFIG_L2TP_DEBUGFS is not set
# CONFIG_L2TP_V3 is not set
CONFIG_STP=y
CONFIG_BRIDGE=y
# CONFIG_BRIDGE_IGMP_SNOOPING is not set
# CONFIG_VLAN_8021Q is not set
CONFIG_DECNET=y
# CONFIG_DECNET_ROUTER is not set
CONFIG_LLC=y
CONFIG_LLC2=y
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
CONFIG_X25=y
CONFIG_LAPB=y
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_PHONET is not set
CONFIG_IEEE802154=y
# CONFIG_NET_SCHED is not set
# CONFIG_DCB is not set
CONFIG_DNS_RESOLVER=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_HAMRADIO=y

#
# Packet Radio protocols
#
# CONFIG_AX25 is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
CONFIG_BT=y
# CONFIG_BT_L2CAP is not set
CONFIG_BT_SCO=y

#
# Bluetooth device drivers
#
CONFIG_BT_HCIUART=y
CONFIG_BT_HCIUART_H4=y
# CONFIG_BT_HCIUART_BCSP is not set
# CONFIG_BT_HCIUART_ATH3K is not set
CONFIG_BT_HCIUART_LL=y
CONFIG_BT_HCIVHCI=y
CONFIG_BT_MRVL=y
CONFIG_AF_RXRPC=y
# CONFIG_AF_RXRPC_DEBUG is not set
# CONFIG_RXKAD is not set
CONFIG_FIB_RULES=y
# CONFIG_WIRELESS is not set
# CONFIG_WIMAX is not set
CONFIG_RFKILL=y
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
CONFIG_NET_9P=y
CONFIG_NET_9P_VIRTIO=y
CONFIG_NET_9P_DEBUG=y
CONFIG_CAIF=y
# CONFIG_CAIF_DEBUG is not set
CONFIG_CAIF_NETDEV=y
CONFIG_CEPH_LIB=y
# CONFIG_CEPH_LIB_PRETTYDEBUG is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH=""
# CONFIG_DEVTMPFS is not set
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_FIRMWARE_IN_KERNEL is not set
CONFIG_EXTRA_FIRMWARE=""
CONFIG_SYS_HYPERVISOR=y
CONFIG_CONNECTOR=y
# CONFIG_PROC_EVENTS is not set
CONFIG_MTD=y
CONFIG_MTD_DEBUG=y
CONFIG_MTD_DEBUG_VERBOSE=0
# CONFIG_MTD_CONCAT is not set
CONFIG_MTD_PARTITIONS=y
# CONFIG_MTD_REDBOOT_PARTS is not set
CONFIG_MTD_CMDLINE_PARTS=y
CONFIG_MTD_AR7_PARTS=y

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

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=y
CONFIG_MTD_JEDECPROBE=y
CONFIG_MTD_GEN_PROBE=y
CONFIG_MTD_CFI_ADV_OPTIONS=y
# CONFIG_MTD_CFI_NOSWAP is not set
# CONFIG_MTD_CFI_BE_BYTE_SWAP is not set
CONFIG_MTD_CFI_LE_BYTE_SWAP=y
# CONFIG_MTD_CFI_GEOMETRY 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_OTP=y
# CONFIG_MTD_CFI_INTELEXT is not set
CONFIG_MTD_CFI_AMDSTD=y
CONFIG_MTD_CFI_STAA=y
CONFIG_MTD_CFI_UTIL=y
# CONFIG_MTD_RAM is not set
CONFIG_MTD_ROM=y
CONFIG_MTD_ABSENT=y

#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_NETSC520 is not set
CONFIG_MTD_TS5500=y
CONFIG_MTD_AMD76XROM=y
# CONFIG_MTD_ICHXROM is not set
# CONFIG_MTD_SCB2_FLASH is not set
# CONFIG_MTD_NETtel is not set
CONFIG_MTD_L440GX=y
# CONFIG_MTD_PLATRAM is not set

#
# Self-contained MTD device drivers
#
CONFIG_MTD_DATAFLASH=y
# CONFIG_MTD_DATAFLASH_WRITE_VERIFY is not set
CONFIG_MTD_DATAFLASH_OTP=y
# CONFIG_MTD_M25P80 is not set
CONFIG_MTD_SST25L=y
# CONFIG_MTD_SLRAM is not set
CONFIG_MTD_PHRAM=y
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLOCK2MTD is not set

#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
CONFIG_MTD_NAND_ECC=y
# CONFIG_MTD_NAND_ECC_SMC is not set
# CONFIG_MTD_NAND is not set
CONFIG_MTD_ONENAND=y
CONFIG_MTD_ONENAND_VERIFY_WRITE=y
CONFIG_MTD_ONENAND_GENERIC=y
CONFIG_MTD_ONENAND_OTP=y
# CONFIG_MTD_ONENAND_2X_PROGRAM is not set
# CONFIG_MTD_ONENAND_SIM is not set

#
# LPDDR flash memory drivers
#
CONFIG_MTD_LPDDR=y
CONFIG_MTD_QINFO_PROBE=y
# CONFIG_MTD_UBI is not set
# CONFIG_PARPORT is not set
# CONFIG_BLK_DEV is not set
# CONFIG_MISC_DEVICES is not set
CONFIG_HAVE_IDE=y
CONFIG_IDE=y

#
# Please see Documentation/ide/ide.txt for help/info on IDE drives
#
CONFIG_IDE_XFER_MODE=y
CONFIG_IDE_TIMINGS=y
CONFIG_IDE_ATAPI=y
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_IDE_GD is not set
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_PROC_FS=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_PLATFORM is not set
CONFIG_BLK_DEV_CMD640=y
CONFIG_BLK_DEV_CMD640_ENHANCED=y
# CONFIG_BLK_DEV_IDEDMA is not set

#
# SCSI device support
#
CONFIG_SCSI_MOD=y
CONFIG_RAID_ATTRS=y
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=y
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=y
CONFIG_CHR_DEV_OSST=y
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y

#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
CONFIG_SCSI_FC_ATTRS=y
# CONFIG_SCSI_FC_TGT_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
CONFIG_SCSI_SAS_ATTRS=y
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
# CONFIG_SCSI_LOWLEVEL is not set
CONFIG_SCSI_DH=y
CONFIG_SCSI_DH_RDAC=y
# CONFIG_SCSI_DH_HP_SW is not set
# CONFIG_SCSI_DH_EMC is not set
CONFIG_SCSI_DH_ALUA=y
CONFIG_SCSI_OSD_INITIATOR=y
CONFIG_SCSI_OSD_ULD=y
CONFIG_SCSI_OSD_DPRINT_SENSE=1
CONFIG_SCSI_OSD_DEBUG=y
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_VERBOSE_ERROR=y
# CONFIG_SATA_PMP is not set

#
# Controllers with non-SFF native interface
#
CONFIG_SATA_AHCI_PLATFORM=y
CONFIG_ATA_SFF=y

#
# SFF controllers with custom DMA interface
#
# CONFIG_ATA_BMDMA is not set

#
# PIO-only SFF controllers
#

#
# Generic fallback / legacy drivers
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
CONFIG_MD_LINEAR=y
# CONFIG_MD_RAID0 is not set
CONFIG_MD_RAID1=y
# CONFIG_MD_RAID10 is not set
CONFIG_MD_RAID456=y
CONFIG_MD_MULTIPATH=y
# CONFIG_MD_FAULTY is not set
# CONFIG_BLK_DEV_DM is not set
CONFIG_MACINTOSH_DRIVERS=y
CONFIG_MAC_EMUMOUSEBTN=y
# CONFIG_NETDEVICES is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

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

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

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5520 is not set
CONFIG_KEYBOARD_ADP5588=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_KEYBOARD_QT2160=y
# CONFIG_KEYBOARD_LKKBD is not set
CONFIG_KEYBOARD_TCA6416=y
CONFIG_KEYBOARD_LM8323=y
# CONFIG_KEYBOARD_MAX7359 is not set
CONFIG_KEYBOARD_MCS=y
CONFIG_KEYBOARD_NEWTON=y
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
CONFIG_KEYBOARD_SUNKBD=y
CONFIG_KEYBOARD_STMPE=y
# CONFIG_KEYBOARD_TWL4030 is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_INPUT_MOUSE is not set
CONFIG_INPUT_JOYSTICK=y
# CONFIG_JOYSTICK_ANALOG is not set
CONFIG_JOYSTICK_A3D=y
CONFIG_JOYSTICK_ADI=y
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
# CONFIG_JOYSTICK_SIDEWINDER is not set
CONFIG_JOYSTICK_TMDC=y
CONFIG_JOYSTICK_IFORCE=y
# CONFIG_JOYSTICK_IFORCE_232 is not set
CONFIG_JOYSTICK_WARRIOR=y
# CONFIG_JOYSTICK_MAGELLAN is not set
CONFIG_JOYSTICK_SPACEORB=y
CONFIG_JOYSTICK_SPACEBALL=y
CONFIG_JOYSTICK_STINGER=y
CONFIG_JOYSTICK_TWIDJOY=y
# CONFIG_JOYSTICK_ZHENHUA is not set
CONFIG_JOYSTICK_JOYDUMP=y
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_88PM860X_ONKEY is not set
CONFIG_INPUT_AD714X=y
# CONFIG_INPUT_AD714X_I2C is not set
# CONFIG_INPUT_AD714X_SPI is not set
# CONFIG_INPUT_PCSPKR is not set
CONFIG_INPUT_MAX8925_ONKEY=y
# CONFIG_INPUT_APANEL is not set
# CONFIG_INPUT_TWL4030_PWRBUTTON is not set
# CONFIG_INPUT_TWL4030_VIBRA is not set
CONFIG_INPUT_UINPUT=y
CONFIG_INPUT_PCF50633_PMU=y
# CONFIG_INPUT_PCF8574 is not set
# CONFIG_INPUT_WM831X_ON is not set
# CONFIG_INPUT_ADXL34X is not set
# CONFIG_INPUT_CMA3000 is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
CONFIG_SERIO_ALTERA_PS2=y
CONFIG_SERIO_PS2MULT=y
CONFIG_GAMEPORT=y
CONFIG_GAMEPORT_NS558=y
# CONFIG_GAMEPORT_L4 is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_DEVKMEM=y
CONFIG_SERIAL_NONSTANDARD=y
CONFIG_N_HDLC=y
# CONFIG_N_GSM is not set
CONFIG_RISCOM8=y
CONFIG_SPECIALIX=y
# CONFIG_STALDRV is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_NR_UARTS=4
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=y
# CONFIG_SERIAL_8250_RSA is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_MAX3100=y
CONFIG_SERIAL_MAX3107=y
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_TIMBERDALE is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
CONFIG_SERIAL_ALTERA_UART=y
CONFIG_SERIAL_ALTERA_UART_MAXPORTS=4
CONFIG_SERIAL_ALTERA_UART_BAUDRATE=115200
# CONFIG_SERIAL_ALTERA_UART_CONSOLE is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_HVC_DRIVER=y
# CONFIG_HVC_XEN is not set
CONFIG_VIRTIO_CONSOLE=y
# CONFIG_IPMI_HANDLER is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
CONFIG_GEN_RTC=y
CONFIG_GEN_RTC_X=y
CONFIG_R3964=y
CONFIG_MWAVE=y
# CONFIG_RAW_DRIVER is not set
CONFIG_HANGCHECK_TIMER=y
CONFIG_TCG_TPM=y
# CONFIG_TCG_TIS is not set
# CONFIG_TCG_NSC is not set
# CONFIG_TCG_ATMEL is not set
# CONFIG_TELCLOCK is not set
CONFIG_RAMOOPS=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_MUX=y

#
# Multiplexer I2C Chip support
#
CONFIG_I2C_MUX_PCA9541=y
CONFIG_I2C_MUX_PCA954x=y
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_SMBUS=y
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_ALGOPCF is not set
CONFIG_I2C_ALGOPCA=y

#
# I2C Hardware Bus support
#

#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
CONFIG_I2C_OCORES=y
CONFIG_I2C_PCA_PLATFORM=y
CONFIG_I2C_SIMTEC=y
CONFIG_I2C_XILINX=y

#
# External I2C/SMBus adapter drivers
#
CONFIG_I2C_PARPORT_LIGHT=y
# CONFIG_I2C_TAOS_EVM is not set

#
# Other I2C/SMBus bus drivers
#
CONFIG_I2C_DEBUG_CORE=y
CONFIG_I2C_DEBUG_ALGO=y
CONFIG_I2C_DEBUG_BUS=y
CONFIG_SPI=y
CONFIG_SPI_MASTER=y

#
# SPI Master Controller Drivers
#
CONFIG_SPI_BITBANG=y
CONFIG_SPI_XILINX=y
CONFIG_SPI_XILINX_PLTFM=y
CONFIG_SPI_DESIGNWARE=y

#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not set
CONFIG_SPI_TLE62X0=y

#
# PPS support
#
CONFIG_PPS=y
CONFIG_PPS_DEBUG=y
CONFIG_NTP_PPS=y

#
# PPS clients support
#
CONFIG_PPS_CLIENT_KTIMER=y
CONFIG_PPS_CLIENT_LDISC=y

#
# PPS generators support
#
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
CONFIG_W1=y
CONFIG_W1_CON=y

#
# 1-wire Bus Masters
#
# CONFIG_W1_MASTER_DS2482 is not set

#
# 1-wire Slaves
#
CONFIG_W1_SLAVE_THERM=y
# CONFIG_W1_SLAVE_SMEM is not set
CONFIG_W1_SLAVE_DS2423=y
CONFIG_W1_SLAVE_DS2431=y
CONFIG_W1_SLAVE_DS2433=y
# CONFIG_W1_SLAVE_DS2433_CRC is not set
CONFIG_W1_SLAVE_DS2760=y
CONFIG_W1_SLAVE_BQ27000=y
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_MAX8925_POWER is not set
# CONFIG_WM831X_BACKUP is not set
# CONFIG_WM831X_POWER is not set
# CONFIG_TEST_POWER is not set
# CONFIG_BATTERY_DS2760 is not set
# CONFIG_BATTERY_DS2782 is not set
CONFIG_BATTERY_BQ20Z75=y
# CONFIG_BATTERY_BQ27x00 is not set
# CONFIG_BATTERY_DA9030 is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_CHARGER_PCF50633 is not set
CONFIG_CHARGER_TWL4030=y
CONFIG_HWMON=y
CONFIG_HWMON_VID=y
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Native drivers
#
CONFIG_SENSORS_ABITUGURU=y
# CONFIG_SENSORS_ABITUGURU3 is not set
CONFIG_SENSORS_AD7414=y
# CONFIG_SENSORS_AD7418 is not set
CONFIG_SENSORS_ADCXX=y
CONFIG_SENSORS_ADM1021=y
CONFIG_SENSORS_ADM1025=y
CONFIG_SENSORS_ADM1026=y
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
CONFIG_SENSORS_ADM9240=y
# CONFIG_SENSORS_ADT7411 is not set
# CONFIG_SENSORS_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7475 is not set
CONFIG_SENSORS_ASC7621=y
CONFIG_SENSORS_ASB100=y
CONFIG_SENSORS_ATXP1=y
# CONFIG_SENSORS_DS1621 is not set
CONFIG_SENSORS_F71805F=y
CONFIG_SENSORS_F71882FG=y
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FSCHMD is not set
CONFIG_SENSORS_G760A=y
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
CONFIG_SENSORS_PKGTEMP=y
CONFIG_SENSORS_IT87=y
CONFIG_SENSORS_JC42=y
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM70 is not set
# CONFIG_SENSORS_LM73 is not set
CONFIG_SENSORS_LM75=y
CONFIG_SENSORS_LM77=y
# CONFIG_SENSORS_LM78 is not set
CONFIG_SENSORS_LM80=y
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
CONFIG_SENSORS_LM87=y
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
CONFIG_SENSORS_LM93=y
CONFIG_SENSORS_LTC4215=y
# CONFIG_SENSORS_LTC4245 is not set
CONFIG_SENSORS_LTC4261=y
# CONFIG_SENSORS_LM95241 is not set
CONFIG_SENSORS_MAX1111=y
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX6650 is not set
CONFIG_SENSORS_PC87360=y
CONFIG_SENSORS_PC87427=y
CONFIG_SENSORS_PCF8591=y
CONFIG_SENSORS_SMM665=y
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_EMC1403 is not set
CONFIG_SENSORS_EMC2103=y
CONFIG_SENSORS_SMSC47M1=y
CONFIG_SENSORS_SMSC47M192=y
# CONFIG_SENSORS_SMSC47B397 is not set
CONFIG_SENSORS_ADS7828=y
CONFIG_SENSORS_ADS7871=y
# CONFIG_SENSORS_AMC6821 is not set
CONFIG_SENSORS_THMC50=y
# CONFIG_SENSORS_TMP102 is not set
# CONFIG_SENSORS_TMP401 is not set
# CONFIG_SENSORS_TMP421 is not set
# CONFIG_SENSORS_VIA_CPUTEMP is not set
CONFIG_SENSORS_VT1211=y
# CONFIG_SENSORS_W83781D is not set
CONFIG_SENSORS_W83791D=y
# CONFIG_SENSORS_W83792D is not set
CONFIG_SENSORS_W83793=y
# CONFIG_SENSORS_W83795 is not set
# CONFIG_SENSORS_W83L785TS is not set
CONFIG_SENSORS_W83L786NG=y
CONFIG_SENSORS_W83627HF=y
CONFIG_SENSORS_W83627EHF=y
CONFIG_SENSORS_WM831X=y
CONFIG_SENSORS_LIS3_SPI=y
CONFIG_SENSORS_LIS3_I2C=y
CONFIG_SENSORS_APPLESMC=y
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y

#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set
CONFIG_MFD_SUPPORT=y
CONFIG_MFD_CORE=y
CONFIG_MFD_88PM860X=y
CONFIG_MFD_SM501=y
# CONFIG_HTC_PASIC3 is not set
CONFIG_TPS6507X=y
CONFIG_TWL4030_CORE=y
# CONFIG_TWL4030_CODEC is not set
# CONFIG_TWL6030_PWM is not set
CONFIG_MFD_STMPE=y
# CONFIG_MFD_TC35892 is not set
# CONFIG_MFD_TMIO is not set
CONFIG_PMIC_DA903X=y
CONFIG_PMIC_ADP5520=y
CONFIG_MFD_MAX8925=y
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_WM8400 is not set
CONFIG_MFD_WM831X=y
# CONFIG_MFD_WM831X_I2C is not set
CONFIG_MFD_WM831X_SPI=y
# CONFIG_MFD_WM8350_I2C is not set
CONFIG_MFD_WM8994=y
CONFIG_MFD_PCF50633=y
# CONFIG_MFD_MC13XXX is not set
# CONFIG_PCF50633_ADC is not set
# CONFIG_PCF50633_GPIO is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_EZX_PCAP is not set
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set
# CONFIG_REGULATOR_DUMMY is not set
CONFIG_REGULATOR_FIXED_VOLTAGE=y
CONFIG_REGULATOR_VIRTUAL_CONSUMER=y
CONFIG_REGULATOR_USERSPACE_CONSUMER=y
CONFIG_REGULATOR_BQ24022=y
# CONFIG_REGULATOR_MAX1586 is not set
# CONFIG_REGULATOR_MAX8649 is not set
CONFIG_REGULATOR_MAX8660=y
CONFIG_REGULATOR_MAX8925=y
CONFIG_REGULATOR_MAX8952=y
# CONFIG_REGULATOR_TWL4030 is not set
# CONFIG_REGULATOR_WM831X is not set
# CONFIG_REGULATOR_WM8994 is not set
CONFIG_REGULATOR_DA903X=y
CONFIG_REGULATOR_PCF50633=y
CONFIG_REGULATOR_LP3971=y
# CONFIG_REGULATOR_LP3972 is not set
# CONFIG_REGULATOR_TPS65023 is not set
# CONFIG_REGULATOR_TPS6507X is not set
# CONFIG_REGULATOR_88PM8607 is not set
CONFIG_REGULATOR_ISL6271A=y
# CONFIG_REGULATOR_AD5398 is not set
# CONFIG_MEDIA_SUPPORT is not set

#
# Graphics support
#
# CONFIG_DRM is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Display device support
#
CONFIG_DISPLAY_SUPPORT=y

#
# Display hardware drivers
#

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_SOUND=y
CONFIG_SOUND_OSS_CORE=y
CONFIG_SOUND_OSS_CORE_PRECLAIM=y
# CONFIG_SND is not set
CONFIG_SOUND_PRIME=y
# CONFIG_SOUND_OSS is not set
CONFIG_HID_SUPPORT=y
# CONFIG_HID is not set
# CONFIG_HID_PID is not set
# CONFIG_USB_SUPPORT is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y

#
# LED drivers
#
CONFIG_LEDS_88PM860X=y
# CONFIG_LEDS_INPUT is not set
# CONFIG_LEDS_ALIX2 is not set
CONFIG_LEDS_PCA9532=y
CONFIG_LEDS_LP3944=y
CONFIG_LEDS_LP5521=y
CONFIG_LEDS_LP5523=y
# CONFIG_LEDS_CLEVO_MAIL is not set
# CONFIG_LEDS_PCA955X is not set
CONFIG_LEDS_WM831X_STATUS=y
# CONFIG_LEDS_DA903X is not set
# CONFIG_LEDS_DAC124S085 is not set
CONFIG_LEDS_REGULATOR=y
# CONFIG_LEDS_BD2802 is not set
CONFIG_LEDS_ADP5520=y
CONFIG_LEDS_TRIGGERS=y

#
# LED Triggers
#
# CONFIG_LEDS_TRIGGER_TIMER is not set
# CONFIG_LEDS_TRIGGER_HEARTBEAT is not set
CONFIG_LEDS_TRIGGER_BACKLIGHT=y
# CONFIG_LEDS_TRIGGER_DEFAULT_ON is not set

#
# iptables trigger is under Netfilter config (LED target)
#
# CONFIG_NFC_DEVICES is not set
CONFIG_ACCESSIBILITY=y
CONFIG_A11Y_BRAILLE_CONSOLE=y
CONFIG_EDAC=y

#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_DECODE_MCE=y
CONFIG_EDAC_MCE_INJ=y
CONFIG_EDAC_MM_EDAC=y
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
CONFIG_AUXDISPLAY=y
CONFIG_UIO=y
# CONFIG_UIO_PDRV is not set
# CONFIG_UIO_PDRV_GENIRQ is not set

#
# Xen driver support
#
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
# CONFIG_XEN_DEV_EVTCHN is not set
# CONFIG_XENFS is not set
CONFIG_XEN_SYS_HYPERVISOR=y
# CONFIG_XEN_GNTDEV is not set
# CONFIG_XEN_PLATFORM_PCI is not set
CONFIG_STAGING=y
# CONFIG_STAGING_EXCLUDE_BUILD is not set
CONFIG_BKL=y
# CONFIG_ECHO is not set
CONFIG_POHMELFS=y
CONFIG_POHMELFS_DEBUG=y
# CONFIG_POHMELFS_CRYPTO is not set
CONFIG_AUTOFS_FS=y
CONFIG_IIO=y
CONFIG_IIO_RING_BUFFER=y
CONFIG_IIO_SW_RING=y
CONFIG_IIO_TRIGGER=y

#
# Accelerometers
#
# CONFIG_ADIS16201 is not set
CONFIG_ADIS16203=y
# CONFIG_ADIS16204 is not set
CONFIG_ADIS16209=y
# CONFIG_ADIS16220 is not set
# CONFIG_ADIS16240 is not set
CONFIG_KXSD9=y
CONFIG_LIS3L02DQ=y
# CONFIG_SCA3000 is not set

#
# Analog to digital convertors
#
# CONFIG_MAX1363 is not set
# CONFIG_AD7150 is not set
CONFIG_AD7152=y
CONFIG_AD7291=y
# CONFIG_AD7298 is not set
# CONFIG_AD7314 is not set
CONFIG_AD799X=y
CONFIG_AD799X_RING_BUFFER=y
CONFIG_AD7476=y
# CONFIG_AD7887 is not set
CONFIG_AD7745=y
CONFIG_AD7816=y
CONFIG_ADT75=y
CONFIG_ADT7310=y
CONFIG_ADT7410=y

#
# Analog digital bi-direction convertors
#
# CONFIG_ADT7316 is not set

#
# Digital to analog convertors
#
# CONFIG_AD5624R_SPI is not set
CONFIG_AD5446=y

#
# Direct Digital Synthesis
#
CONFIG_AD5930=y
# CONFIG_AD9832 is not set
CONFIG_AD9850=y
# CONFIG_AD9852 is not set
# CONFIG_AD9910 is not set
CONFIG_AD9951=y

#
# Digital gyroscope sensors
#
CONFIG_ADIS16060=y
CONFIG_ADIS16080=y
# CONFIG_ADIS16130 is not set
CONFIG_ADIS16260=y
# CONFIG_ADIS16251 is not set

#
# Inertial measurement units
#
CONFIG_ADIS16300=y
# CONFIG_ADIS16350 is not set
CONFIG_ADIS16400=y

#
# Light sensors
#
CONFIG_SENSORS_TSL2563=y
# CONFIG_SENSORS_ISL29018 is not set

#
# Magnetometer sensors
#
CONFIG_SENSORS_AK8975=y
# CONFIG_SENSORS_HMC5843 is not set

#
# Active energy metering IC
#
CONFIG_ADE7753=y
CONFIG_ADE7754=y
CONFIG_ADE7758=y
CONFIG_ADE7759=y
# CONFIG_ADE7854 is not set

#
# Resolver to digital converters
#
# CONFIG_AD2S90 is not set
CONFIG_AD2S120X=y
CONFIG_AD2S1210=y
# CONFIG_AD2S1210_GPIO_INPUT is not set
CONFIG_AD2S1210_GPIO_OUTPUT=y
# CONFIG_AD2S1210_GPIO_NONE is not set

#
# Triggers - standalone
#
# CONFIG_ZRAM is not set
# CONFIG_BATMAN_ADV is not set

#
# Texas Instruments shared transport line discipline
#
# CONFIG_ST_BT is not set
CONFIG_ADIS16255=y
# CONFIG_SMB_FS is not set
CONFIG_MACH_NO_WESTBRIDGE=y
# CONFIG_FT1000 is not set

#
# Speakup console speech
#
# CONFIG_SPEAKUP is not set
CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI4=y
# CONFIG_X86_PLATFORM_DEVICES is not set

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

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
# CONFIG_EXT2_FS_SECURITY is not set
CONFIG_EXT2_FS_XIP=y
# CONFIG_EXT3_FS is not set
CONFIG_EXT4_FS=y
# CONFIG_EXT4_USE_FOR_EXT23 is not set
CONFIG_EXT4_FS_XATTR=y
# CONFIG_EXT4_FS_POSIX_ACL is not set
# CONFIG_EXT4_FS_SECURITY is not set
# CONFIG_EXT4_DEBUG is not set
CONFIG_FS_XIP=y
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=y
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
# CONFIG_XFS_RT is not set
# CONFIG_XFS_DEBUG is not set
CONFIG_GFS2_FS=y
# CONFIG_GFS2_FS_LOCKING_DLM is not set
CONFIG_OCFS2_FS=y
CONFIG_OCFS2_FS_O2CB=y
# CONFIG_OCFS2_FS_STATS is not set
CONFIG_OCFS2_DEBUG_MASKLOG=y
# CONFIG_OCFS2_DEBUG_FS is not set
# CONFIG_BTRFS_FS is not set
CONFIG_NILFS2_FS=y
CONFIG_EXPORTFS=y
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
# CONFIG_INOTIFY_USER is not set
# CONFIG_FANOTIFY is not set
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
CONFIG_PRINT_QUOTA_WARNING=y
CONFIG_QUOTA_DEBUG=y
CONFIG_QUOTA_TREE=y
CONFIG_QFMT_V1=y
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set

#
# Caches
#
# CONFIG_FSCACHE is not set

#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
# CONFIG_VFAT_FS is not set
CONFIG_FAT_DEFAULT_CODEPAGE=437
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
# CONFIG_PROC_KCORE is not set
CONFIG_PROC_VMCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_CONFIGFS_FS=y
# CONFIG_MISC_FILESYSTEMS is not set
CONFIG_NETWORK_FILESYSTEMS=y
# CONFIG_NFS_FS is not set
CONFIG_NFSD=y
CONFIG_NFSD_DEPRECATED=y
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_V4 is not set
CONFIG_LOCKD=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_CEPH_FS is not set
CONFIG_CIFS=y
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
CONFIG_CIFS_UPCALL=y
# CONFIG_CIFS_XATTR is not set
CONFIG_CIFS_DEBUG2=y
CONFIG_CIFS_DFS_UPCALL=y
CONFIG_CIFS_EXPERIMENTAL=y
CONFIG_NCP_FS=y
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
CONFIG_NCPFS_OS2_NS=y
CONFIG_NCPFS_SMALLDOS=y
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
CONFIG_9P_FS=y
# CONFIG_9P_FS_POSIX_ACL is not set

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

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=2048
CONFIG_MAGIC_SYSRQ=y
CONFIG_STRIP_ASM_SYMS=y
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_HARDLOCKUP_DETECTOR is not set
CONFIG_SLUB_DEBUG_ON=y
CONFIG_SLUB_STATS=y
# CONFIG_SPARSE_RCU_POINTER is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_MEMORY_INIT=y
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_FRAME_POINTER=y
CONFIG_LKDTM=y
# CONFIG_SYSCTL_SYSCALL_CHECK is not set
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_C_RECORDMCOUNT=y
CONFIG_TRACING_SUPPORT=y
# CONFIG_FTRACE is not set
# CONFIG_DYNAMIC_DEBUG is not set
# CONFIG_DMA_API_DEBUG is not set
CONFIG_ATOMIC64_SELFTEST=y
CONFIG_ASYNC_RAID6_TEST=y
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
CONFIG_HAVE_ARCH_KMEMCHECK=y
# CONFIG_STRICT_DEVMEM is not set
# CONFIG_X86_VERBOSE_BOOTUP is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_IOMMU_STRESS is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
CONFIG_OPTIMIZE_INLINING=y

#
# Security options
#
CONFIG_KEYS=y
# CONFIG_TRUSTED_KEYS is not set
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
CONFIG_SECURITY_DMESG_RESTRICT=y
CONFIG_SECURITY=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_NETWORK_XFRM is not set
CONFIG_SECURITY_PATH=y
CONFIG_SECURITY_SMACK=y
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_IMA is not set
CONFIG_DEFAULT_SECURITY_SMACK=y
# CONFIG_DEFAULT_SECURITY_DAC is not set
CONFIG_DEFAULT_SECURITY="smack"
CONFIG_XOR_BLOCKS=y
CONFIG_ASYNC_CORE=y
CONFIG_ASYNC_MEMCPY=y
CONFIG_ASYNC_XOR=y
CONFIG_ASYNC_PQ=y
CONFIG_ASYNC_RAID6_RECOV=y
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
CONFIG_CRYPTO_GF128MUL=y
CONFIG_CRYPTO_NULL=y
CONFIG_CRYPTO_WORKQUEUE=y
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=y

#
# Authenticated Encryption with Associated Data
#
CONFIG_CRYPTO_CCM=y
CONFIG_CRYPTO_GCM=y
CONFIG_CRYPTO_SEQIV=y

#
# Block modes
#
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_CTR=y
CONFIG_CRYPTO_CTS=y
CONFIG_CRYPTO_ECB=y
CONFIG_CRYPTO_LRW=y
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_XTS is not set

#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=y
# CONFIG_CRYPTO_VMAC is not set

#
# Digest
#
CONFIG_CRYPTO_CRC32C=y
CONFIG_CRYPTO_CRC32C_INTEL=y
CONFIG_CRYPTO_GHASH=y
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
CONFIG_CRYPTO_RMD160=y
CONFIG_CRYPTO_RMD256=y
# CONFIG_CRYPTO_RMD320 is not set
CONFIG_CRYPTO_SHA1=y
# CONFIG_CRYPTO_SHA256 is not set
CONFIG_CRYPTO_SHA512=y
CONFIG_CRYPTO_TGR192=y
CONFIG_CRYPTO_WP512=y
# CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL is not set

#
# Ciphers
#
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_X86_64=y
CONFIG_CRYPTO_ANUBIS=y
CONFIG_CRYPTO_ARC4=y
CONFIG_CRYPTO_BLOWFISH=y
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_FCRYPT=y
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_X86_64 is not set
CONFIG_CRYPTO_SEED=y
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
CONFIG_CRYPTO_TWOFISH=y
CONFIG_CRYPTO_TWOFISH_COMMON=y
# CONFIG_CRYPTO_TWOFISH_X86_64 is not set

#
# Compression
#
CONFIG_CRYPTO_DEFLATE=y
# CONFIG_CRYPTO_ZLIB is not set
# CONFIG_CRYPTO_LZO is not set

#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
# CONFIG_CRYPTO_USER_API_HASH is not set
# CONFIG_CRYPTO_USER_API_SKCIPHER is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_PADLOCK is not set
CONFIG_HAVE_KVM=y
CONFIG_VIRTUALIZATION=y
CONFIG_VHOST_NET=y
CONFIG_VIRTIO=y
CONFIG_VIRTIO_RING=y
CONFIG_VIRTIO_BALLOON=y
# CONFIG_BINARY_PRINTF is not set

#
# Library routines
#
CONFIG_RAID6_PQ=y
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_FIND_LAST_BIT=y
CONFIG_CRC_CCITT=y
CONFIG_CRC16=y
CONFIG_CRC_T10DIF=y
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=y
CONFIG_TEXTSEARCH_BM=y
CONFIG_TEXTSEARCH_FSM=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_NLATTR=y
CONFIG_SHM_SIGNAL=y
# CONFIG_IOQ is not set

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: mmotm 2010-12-02-16-34 uploaded
  2010-12-03  0:34 ` akpm
@ 2010-12-03 21:43   ` Zimny Lech
  -1 siblings, 0 replies; 77+ messages in thread
From: Zimny Lech @ 2010-12-03 21:43 UTC (permalink / raw)
  To: akpm; +Cc: mm-commits, linux-kernel, linux-mm, linux-fsdevel

Ave,

2010/12/3  <akpm@linux-foundation.org>:
> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>

23 builds, and only known problems, nothing new

arch/x86/built-in.o: In function `kvm_smp_prepare_boot_cpu':
kvm.c:(.init.text+0xdb49): undefined reference to `kvm_register_clock'
make[1]: *** [.tmp_vmlinux1] Error 1
make: *** [sub-make] Error 2

drivers/built-in.o: In function `pch_uart_shutdown':
pch_uart.c:(.text+0x1a9921): undefined reference to `dma_release_channel'
pch_uart.c:(.text+0x1a9939): undefined reference to `dma_release_channel'
drivers/built-in.o: In function `pch_uart_startup':
pch_uart.c:(.text+0x1a9bdd): undefined reference to `__dma_request_channel'
pch_uart.c:(.text+0x1a9c3e): undefined reference to `__dma_request_channel'
pch_uart.c:(.text+0x1a9e38): undefined reference to `dma_release_channel'
make[1]: *** [.tmp_vmlinux1] Error 1
make: *** [sub-make] Error 2

make[4]: *** No rule to make target
`drivers/scsi/aic7xxx/aicasm/*.[chyl]', needed by
`drivers/scsi/aic7xxx/aicasm/aicasm'.  Stop.
make[3]: *** [drivers/scsi/aic7xxx] Error 2
make[2]: *** [drivers/scsi] Error 2
make[1]: *** [drivers] Error 2
make: *** [sub-make] Error 2




-- 
Slawa!
Zimny "Spie dziadu!" Lech z Wawelu

Piekielny strach zagrzmiał
Patrzę na sufit
Krew tam
Strzępy głów w bólach jęczą coś

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: mmotm 2010-12-02-16-34 uploaded
@ 2010-12-03 21:43   ` Zimny Lech
  0 siblings, 0 replies; 77+ messages in thread
From: Zimny Lech @ 2010-12-03 21:43 UTC (permalink / raw)
  To: akpm; +Cc: mm-commits, linux-kernel, linux-mm, linux-fsdevel

Ave,

2010/12/3  <akpm@linux-foundation.org>:
> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>

23 builds, and only known problems, nothing new

arch/x86/built-in.o: In function `kvm_smp_prepare_boot_cpu':
kvm.c:(.init.text+0xdb49): undefined reference to `kvm_register_clock'
make[1]: *** [.tmp_vmlinux1] Error 1
make: *** [sub-make] Error 2

drivers/built-in.o: In function `pch_uart_shutdown':
pch_uart.c:(.text+0x1a9921): undefined reference to `dma_release_channel'
pch_uart.c:(.text+0x1a9939): undefined reference to `dma_release_channel'
drivers/built-in.o: In function `pch_uart_startup':
pch_uart.c:(.text+0x1a9bdd): undefined reference to `__dma_request_channel'
pch_uart.c:(.text+0x1a9c3e): undefined reference to `__dma_request_channel'
pch_uart.c:(.text+0x1a9e38): undefined reference to `dma_release_channel'
make[1]: *** [.tmp_vmlinux1] Error 1
make: *** [sub-make] Error 2

make[4]: *** No rule to make target
`drivers/scsi/aic7xxx/aicasm/*.[chyl]', needed by
`drivers/scsi/aic7xxx/aicasm/aicasm'.  Stop.
make[3]: *** [drivers/scsi/aic7xxx] Error 2
make[2]: *** [drivers/scsi] Error 2
make[1]: *** [drivers] Error 2
make: *** [sub-make] Error 2




-- 
Slawa!
Zimny "Spie dziadu!" Lech z Wawelu

Piekielny strach zagrzmiał
Patrzę na sufit
Krew tam
Strzępy głów w bólach jęczą coś

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: mmotm 2010-12-02-16-34 uploaded
  2010-12-03  0:34 ` akpm
                   ` (3 preceding siblings ...)
  (?)
@ 2010-12-04  0:39 ` Stephen Rothwell
  2010-12-06 17:11     ` Randy Dunlap
  -1 siblings, 1 reply; 77+ messages in thread
From: Stephen Rothwell @ 2010-12-04  0:39 UTC (permalink / raw)
  To: akpm; +Cc: mm-commits, linux-kernel, linux-mm, linux-fsdevel

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

Hi Andrew,

On Thu, 02 Dec 2010 16:34:54 -0800 akpm@linux-foundation.org wrote:
>
> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> 
>    http://userweb.kernel.org/~akpm/mmotm/

Build results here (as they get done): http://kisskb.ellerman.id.au/kisskb/head/3514/
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

P.S. hungry, yet?

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2010-12-03  0:34 ` akpm
                   ` (4 preceding siblings ...)
  (?)
@ 2010-12-05  8:25 ` Jiri Slaby
  2010-12-05 13:08   ` Rafael J. Wysocki
  2010-12-05 13:08   ` Rafael J. Wysocki
  -1 siblings, 2 replies; 77+ messages in thread
From: Jiri Slaby @ 2010-12-05  8:25 UTC (permalink / raw)
  To: akpm; +Cc: linux-kernel, Linux-pm mailing list, Rafael J. Wysocki

On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to

Hi, this kernel regresses with respect to resume. It doesn't wake up,
the screen is black with blinking cursor at position [1, 1].
2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
far.

I'm using pm-suspend, any ideas what to test before I start to find the
reason on my own?

regards,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2010-12-03  0:34 ` akpm
                   ` (5 preceding siblings ...)
  (?)
@ 2010-12-05  8:25 ` Jiri Slaby
  -1 siblings, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2010-12-05  8:25 UTC (permalink / raw)
  To: akpm; +Cc: Rafael J. Wysocki, Linux-pm mailing list, linux-kernel

On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to

Hi, this kernel regresses with respect to resume. It doesn't wake up,
the screen is black with blinking cursor at position [1, 1].
2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
far.

I'm using pm-suspend, any ideas what to test before I start to find the
reason on my own?

regards,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2010-12-05  8:25 ` Resume hangs [was: mmotm 2010-12-02-16-34 uploaded] Jiri Slaby
@ 2010-12-05 13:08   ` Rafael J. Wysocki
  2010-12-13 10:04     ` Jiri Slaby
  2010-12-13 10:04     ` Jiri Slaby
  2010-12-05 13:08   ` Rafael J. Wysocki
  1 sibling, 2 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-12-05 13:08 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: akpm, linux-kernel, Linux-pm mailing list

On Sunday, December 05, 2010, Jiri Slaby wrote:
> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> 
> Hi, this kernel regresses with respect to resume. It doesn't wake up,
> the screen is black with blinking cursor at position [1, 1].
> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
> far.
> 
> I'm using pm-suspend, any ideas what to test before I start to find the
> reason on my own?

Please try the pm_test tests for core, processors and devices, eg.:

# echo core > /sys/power/pm_test
# echo mem > /sys/power/state

(this is described in Documentation/power/basic-pm-debugging.txt .

That will tell you if you need to go through the BIOS for the bug to show up
and perhaps at what "level" the problem occurs.

It looks like the problem caused by NX-ing of the kernel code.

Thanks,
Rafael

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2010-12-05  8:25 ` Resume hangs [was: mmotm 2010-12-02-16-34 uploaded] Jiri Slaby
  2010-12-05 13:08   ` Rafael J. Wysocki
@ 2010-12-05 13:08   ` Rafael J. Wysocki
  1 sibling, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-12-05 13:08 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: akpm, linux-kernel, Linux-pm mailing list

On Sunday, December 05, 2010, Jiri Slaby wrote:
> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> 
> Hi, this kernel regresses with respect to resume. It doesn't wake up,
> the screen is black with blinking cursor at position [1, 1].
> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
> far.
> 
> I'm using pm-suspend, any ideas what to test before I start to find the
> reason on my own?

Please try the pm_test tests for core, processors and devices, eg.:

# echo core > /sys/power/pm_test
# echo mem > /sys/power/state

(this is described in Documentation/power/basic-pm-debugging.txt .

That will tell you if you need to go through the BIOS for the bug to show up
and perhaps at what "level" the problem occurs.

It looks like the problem caused by NX-ing of the kernel code.

Thanks,
Rafael

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: mmotm 2010-12-02-16-34 uploaded
  2010-12-04  0:39 ` Stephen Rothwell
@ 2010-12-06 17:11     ` Randy Dunlap
  0 siblings, 0 replies; 77+ messages in thread
From: Randy Dunlap @ 2010-12-06 17:11 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: akpm, linux-kernel, linux-mm, linux-fsdevel

On Sat, 4 Dec 2010 11:39:20 +1100 Stephen Rothwell wrote:

> Hi Andrew,
> 
> On Thu, 02 Dec 2010 16:34:54 -0800 akpm@linux-foundation.org wrote:
> >
> > The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> > 
> >    http://userweb.kernel.org/~akpm/mmotm/
> 
> Build results here (as they get done): http://kisskb.ellerman.id.au/kisskb/head/3514/
> -- 

Lots of the errors seem to be toolchain related.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: mmotm 2010-12-02-16-34 uploaded
@ 2010-12-06 17:11     ` Randy Dunlap
  0 siblings, 0 replies; 77+ messages in thread
From: Randy Dunlap @ 2010-12-06 17:11 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: akpm, linux-kernel, linux-mm, linux-fsdevel

On Sat, 4 Dec 2010 11:39:20 +1100 Stephen Rothwell wrote:

> Hi Andrew,
> 
> On Thu, 02 Dec 2010 16:34:54 -0800 akpm@linux-foundation.org wrote:
> >
> > The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> > 
> >    http://userweb.kernel.org/~akpm/mmotm/
> 
> Build results here (as they get done): http://kisskb.ellerman.id.au/kisskb/head/3514/
> -- 

Lots of the errors seem to be toolchain related.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2010-12-05 13:08   ` Rafael J. Wysocki
  2010-12-13 10:04     ` Jiri Slaby
@ 2010-12-13 10:04     ` Jiri Slaby
  2010-12-13 21:10       ` Rafael J. Wysocki
  2010-12-13 21:10       ` Rafael J. Wysocki
  1 sibling, 2 replies; 77+ messages in thread
From: Jiri Slaby @ 2010-12-13 10:04 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
> On Sunday, December 05, 2010, Jiri Slaby wrote:
>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>>
>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
>> the screen is black with blinking cursor at position [1, 1].
>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
>> far.
>>
>> I'm using pm-suspend, any ideas what to test before I start to find the
>> reason on my own?
> 
> Please try the pm_test tests for core, processors and devices, eg.:

Hmm, I haven't seen the issues since then. So it had to be some kind of
coincidence -- I see the issue occasionally for some time already. Now
it triggered twice in a row after I updated the kernel.

regards,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2010-12-05 13:08   ` Rafael J. Wysocki
@ 2010-12-13 10:04     ` Jiri Slaby
  2010-12-13 10:04     ` Jiri Slaby
  1 sibling, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2010-12-13 10:04 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
> On Sunday, December 05, 2010, Jiri Slaby wrote:
>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>>
>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
>> the screen is black with blinking cursor at position [1, 1].
>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
>> far.
>>
>> I'm using pm-suspend, any ideas what to test before I start to find the
>> reason on my own?
> 
> Please try the pm_test tests for core, processors and devices, eg.:

Hmm, I haven't seen the issues since then. So it had to be some kind of
coincidence -- I see the issue occasionally for some time already. Now
it triggered twice in a row after I updated the kernel.

regards,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2010-12-13 10:04     ` Jiri Slaby
  2010-12-13 21:10       ` Rafael J. Wysocki
@ 2010-12-13 21:10       ` Rafael J. Wysocki
  2010-12-14 22:08         ` Jiri Slaby
  2010-12-14 22:08         ` Jiri Slaby
  1 sibling, 2 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-12-13 21:10 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: akpm, linux-kernel, Linux-pm mailing list

On Monday, December 13, 2010, Jiri Slaby wrote:
> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
> > On Sunday, December 05, 2010, Jiri Slaby wrote:
> >> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
> >>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> >>
> >> Hi, this kernel regresses with respect to resume. It doesn't wake up,
> >> the screen is black with blinking cursor at position [1, 1].
> >> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
> >> far.
> >>
> >> I'm using pm-suspend, any ideas what to test before I start to find the
> >> reason on my own?
> > 
> > Please try the pm_test tests for core, processors and devices, eg.:
> 
> Hmm, I haven't seen the issues since then. So it had to be some kind of
> coincidence -- I see the issue occasionally for some time already. Now
> it triggered twice in a row after I updated the kernel.

Hmm.  What hardware is that?

Rafael

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2010-12-13 10:04     ` Jiri Slaby
@ 2010-12-13 21:10       ` Rafael J. Wysocki
  2010-12-13 21:10       ` Rafael J. Wysocki
  1 sibling, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-12-13 21:10 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: akpm, linux-kernel, Linux-pm mailing list

On Monday, December 13, 2010, Jiri Slaby wrote:
> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
> > On Sunday, December 05, 2010, Jiri Slaby wrote:
> >> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
> >>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> >>
> >> Hi, this kernel regresses with respect to resume. It doesn't wake up,
> >> the screen is black with blinking cursor at position [1, 1].
> >> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
> >> far.
> >>
> >> I'm using pm-suspend, any ideas what to test before I start to find the
> >> reason on my own?
> > 
> > Please try the pm_test tests for core, processors and devices, eg.:
> 
> Hmm, I haven't seen the issues since then. So it had to be some kind of
> coincidence -- I see the issue occasionally for some time already. Now
> it triggered twice in a row after I updated the kernel.

Hmm.  What hardware is that?

Rafael

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2010-12-13 21:10       ` Rafael J. Wysocki
@ 2010-12-14 22:08         ` Jiri Slaby
  2010-12-14 22:22           ` Rafael J. Wysocki
  2010-12-14 22:22           ` Rafael J. Wysocki
  2010-12-14 22:08         ` Jiri Slaby
  1 sibling, 2 replies; 77+ messages in thread
From: Jiri Slaby @ 2010-12-14 22:08 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
> On Monday, December 13, 2010, Jiri Slaby wrote:
>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>>>>
>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
>>>> the screen is black with blinking cursor at position [1, 1].
>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
>>>> far.
>>>>
>>>> I'm using pm-suspend, any ideas what to test before I start to find the
>>>> reason on my own?
>>>
>>> Please try the pm_test tests for core, processors and devices, eg.:
>>
>> Hmm, I haven't seen the issues since then. So it had to be some kind of
>> coincidence -- I see the issue occasionally for some time already. Now
>> it triggered twice in a row after I updated the kernel.
> 
> Hmm.  What hardware is that?

What exactly do you want to know about it? It's some specific intel
desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
raid, dvb-t usb receiver (af9015), usb keyboard and mouse.

regards,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2010-12-13 21:10       ` Rafael J. Wysocki
  2010-12-14 22:08         ` Jiri Slaby
@ 2010-12-14 22:08         ` Jiri Slaby
  1 sibling, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2010-12-14 22:08 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
> On Monday, December 13, 2010, Jiri Slaby wrote:
>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>>>>
>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
>>>> the screen is black with blinking cursor at position [1, 1].
>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
>>>> far.
>>>>
>>>> I'm using pm-suspend, any ideas what to test before I start to find the
>>>> reason on my own?
>>>
>>> Please try the pm_test tests for core, processors and devices, eg.:
>>
>> Hmm, I haven't seen the issues since then. So it had to be some kind of
>> coincidence -- I see the issue occasionally for some time already. Now
>> it triggered twice in a row after I updated the kernel.
> 
> Hmm.  What hardware is that?

What exactly do you want to know about it? It's some specific intel
desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
raid, dvb-t usb receiver (af9015), usb keyboard and mouse.

regards,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2010-12-14 22:08         ` Jiri Slaby
  2010-12-14 22:22           ` Rafael J. Wysocki
@ 2010-12-14 22:22           ` Rafael J. Wysocki
  2011-01-06 14:18             ` Jiri Slaby
  2011-01-06 14:18             ` Jiri Slaby
  1 sibling, 2 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-12-14 22:22 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: akpm, linux-kernel, Linux-pm mailing list

On Tuesday, December 14, 2010, Jiri Slaby wrote:
> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
> > On Monday, December 13, 2010, Jiri Slaby wrote:
> >> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
> >>> On Sunday, December 05, 2010, Jiri Slaby wrote:
> >>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
> >>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> >>>>
> >>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
> >>>> the screen is black with blinking cursor at position [1, 1].
> >>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
> >>>> far.
> >>>>
> >>>> I'm using pm-suspend, any ideas what to test before I start to find the
> >>>> reason on my own?
> >>>
> >>> Please try the pm_test tests for core, processors and devices, eg.:
> >>
> >> Hmm, I haven't seen the issues since then. So it had to be some kind of
> >> coincidence -- I see the issue occasionally for some time already. Now
> >> it triggered twice in a row after I updated the kernel.
> > 
> > Hmm.  What hardware is that?
> 
> What exactly do you want to know about it? It's some specific intel
> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.

I'm seeing pretty much the same symptoms on quite different hardware, except
for one thing: USB keyboard and mouse.

Have you checked if writing 0 to /sys/power/pm_async helps?

Rafael

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2010-12-14 22:08         ` Jiri Slaby
@ 2010-12-14 22:22           ` Rafael J. Wysocki
  2010-12-14 22:22           ` Rafael J. Wysocki
  1 sibling, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2010-12-14 22:22 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: akpm, linux-kernel, Linux-pm mailing list

On Tuesday, December 14, 2010, Jiri Slaby wrote:
> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
> > On Monday, December 13, 2010, Jiri Slaby wrote:
> >> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
> >>> On Sunday, December 05, 2010, Jiri Slaby wrote:
> >>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
> >>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> >>>>
> >>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
> >>>> the screen is black with blinking cursor at position [1, 1].
> >>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
> >>>> far.
> >>>>
> >>>> I'm using pm-suspend, any ideas what to test before I start to find the
> >>>> reason on my own?
> >>>
> >>> Please try the pm_test tests for core, processors and devices, eg.:
> >>
> >> Hmm, I haven't seen the issues since then. So it had to be some kind of
> >> coincidence -- I see the issue occasionally for some time already. Now
> >> it triggered twice in a row after I updated the kernel.
> > 
> > Hmm.  What hardware is that?
> 
> What exactly do you want to know about it? It's some specific intel
> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.

I'm seeing pretty much the same symptoms on quite different hardware, except
for one thing: USB keyboard and mouse.

Have you checked if writing 0 to /sys/power/pm_async helps?

Rafael

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2010-12-14 22:22           ` Rafael J. Wysocki
  2011-01-06 14:18             ` Jiri Slaby
@ 2011-01-06 14:18             ` Jiri Slaby
  2011-01-20 15:23               ` Jiri Slaby
  2011-01-20 15:23               ` Jiri Slaby
  1 sibling, 2 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-01-06 14:18 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 12/14/2010 11:22 PM, Rafael J. Wysocki wrote:
> On Tuesday, December 14, 2010, Jiri Slaby wrote:
>> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
>>> On Monday, December 13, 2010, Jiri Slaby wrote:
>>>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
>>>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
>>>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
>>>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>>>>>>
>>>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
>>>>>> the screen is black with blinking cursor at position [1, 1].
>>>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
>>>>>> far.
>>>>>>
>>>>>> I'm using pm-suspend, any ideas what to test before I start to find the
>>>>>> reason on my own?
>>>>>
>>>>> Please try the pm_test tests for core, processors and devices, eg.:
>>>>
>>>> Hmm, I haven't seen the issues since then. So it had to be some kind of
>>>> coincidence -- I see the issue occasionally for some time already. Now
>>>> it triggered twice in a row after I updated the kernel.
>>>
>>> Hmm.  What hardware is that?
>>
>> What exactly do you want to know about it? It's some specific intel
>> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
>> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.
> 
> I'm seeing pretty much the same symptoms on quite different hardware, except
> for one thing: USB keyboard and mouse.
> 
> Have you checked if writing 0 to /sys/power/pm_async helps?

It's very hard to reproduce (it happens once a week or two), so I can't
say yet. As it happened yesterday again, going to test it from now on.

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2010-12-14 22:22           ` Rafael J. Wysocki
@ 2011-01-06 14:18             ` Jiri Slaby
  2011-01-06 14:18             ` Jiri Slaby
  1 sibling, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-01-06 14:18 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 12/14/2010 11:22 PM, Rafael J. Wysocki wrote:
> On Tuesday, December 14, 2010, Jiri Slaby wrote:
>> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
>>> On Monday, December 13, 2010, Jiri Slaby wrote:
>>>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
>>>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
>>>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
>>>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>>>>>>
>>>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
>>>>>> the screen is black with blinking cursor at position [1, 1].
>>>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
>>>>>> far.
>>>>>>
>>>>>> I'm using pm-suspend, any ideas what to test before I start to find the
>>>>>> reason on my own?
>>>>>
>>>>> Please try the pm_test tests for core, processors and devices, eg.:
>>>>
>>>> Hmm, I haven't seen the issues since then. So it had to be some kind of
>>>> coincidence -- I see the issue occasionally for some time already. Now
>>>> it triggered twice in a row after I updated the kernel.
>>>
>>> Hmm.  What hardware is that?
>>
>> What exactly do you want to know about it? It's some specific intel
>> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
>> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.
> 
> I'm seeing pretty much the same symptoms on quite different hardware, except
> for one thing: USB keyboard and mouse.
> 
> Have you checked if writing 0 to /sys/power/pm_async helps?

It's very hard to reproduce (it happens once a week or two), so I can't
say yet. As it happened yesterday again, going to test it from now on.

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-01-06 14:18             ` Jiri Slaby
  2011-01-20 15:23               ` Jiri Slaby
@ 2011-01-20 15:23               ` Jiri Slaby
  2011-01-20 21:02                 ` Rafael J. Wysocki
  2011-01-20 21:02                 ` Rafael J. Wysocki
  1 sibling, 2 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-01-20 15:23 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 01/06/2011 03:18 PM, Jiri Slaby wrote:
> On 12/14/2010 11:22 PM, Rafael J. Wysocki wrote:
>> On Tuesday, December 14, 2010, Jiri Slaby wrote:
>>> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
>>>> On Monday, December 13, 2010, Jiri Slaby wrote:
>>>>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
>>>>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
>>>>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
>>>>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>>>>>>>
>>>>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
>>>>>>> the screen is black with blinking cursor at position [1, 1].
>>>>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
>>>>>>> far.
>>>>>>>
>>>>>>> I'm using pm-suspend, any ideas what to test before I start to find the
>>>>>>> reason on my own?
>>>>>>
>>>>>> Please try the pm_test tests for core, processors and devices, eg.:
>>>>>
>>>>> Hmm, I haven't seen the issues since then. So it had to be some kind of
>>>>> coincidence -- I see the issue occasionally for some time already. Now
>>>>> it triggered twice in a row after I updated the kernel.
>>>>
>>>> Hmm.  What hardware is that?
>>>
>>> What exactly do you want to know about it? It's some specific intel
>>> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
>>> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.
>>
>> I'm seeing pretty much the same symptoms on quite different hardware, except
>> for one thing: USB keyboard and mouse.
>>
>> Have you checked if writing 0 to /sys/power/pm_async helps?
> 
> It's very hard to reproduce (it happens once a week or two), so I can't
> say yet. As it happened yesterday again, going to test it from now on.

Ok, I haven't seen the issue with 0 in /sys/power/pm_async for two weeks
now (I added it to boot.local). I would say it's related to that...

regards,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-01-06 14:18             ` Jiri Slaby
@ 2011-01-20 15:23               ` Jiri Slaby
  2011-01-20 15:23               ` Jiri Slaby
  1 sibling, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-01-20 15:23 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 01/06/2011 03:18 PM, Jiri Slaby wrote:
> On 12/14/2010 11:22 PM, Rafael J. Wysocki wrote:
>> On Tuesday, December 14, 2010, Jiri Slaby wrote:
>>> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
>>>> On Monday, December 13, 2010, Jiri Slaby wrote:
>>>>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
>>>>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
>>>>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
>>>>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>>>>>>>
>>>>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
>>>>>>> the screen is black with blinking cursor at position [1, 1].
>>>>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
>>>>>>> far.
>>>>>>>
>>>>>>> I'm using pm-suspend, any ideas what to test before I start to find the
>>>>>>> reason on my own?
>>>>>>
>>>>>> Please try the pm_test tests for core, processors and devices, eg.:
>>>>>
>>>>> Hmm, I haven't seen the issues since then. So it had to be some kind of
>>>>> coincidence -- I see the issue occasionally for some time already. Now
>>>>> it triggered twice in a row after I updated the kernel.
>>>>
>>>> Hmm.  What hardware is that?
>>>
>>> What exactly do you want to know about it? It's some specific intel
>>> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
>>> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.
>>
>> I'm seeing pretty much the same symptoms on quite different hardware, except
>> for one thing: USB keyboard and mouse.
>>
>> Have you checked if writing 0 to /sys/power/pm_async helps?
> 
> It's very hard to reproduce (it happens once a week or two), so I can't
> say yet. As it happened yesterday again, going to test it from now on.

Ok, I haven't seen the issue with 0 in /sys/power/pm_async for two weeks
now (I added it to boot.local). I would say it's related to that...

regards,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-01-20 15:23               ` Jiri Slaby
@ 2011-01-20 21:02                 ` Rafael J. Wysocki
  2011-01-21  9:16                   ` Jiri Slaby
                                     ` (3 more replies)
  2011-01-20 21:02                 ` Rafael J. Wysocki
  1 sibling, 4 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2011-01-20 21:02 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: akpm, linux-kernel, Linux-pm mailing list

On Thursday, January 20, 2011, Jiri Slaby wrote:
> On 01/06/2011 03:18 PM, Jiri Slaby wrote:
> > On 12/14/2010 11:22 PM, Rafael J. Wysocki wrote:
> >> On Tuesday, December 14, 2010, Jiri Slaby wrote:
> >>> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
> >>>> On Monday, December 13, 2010, Jiri Slaby wrote:
> >>>>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
> >>>>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
> >>>>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
> >>>>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> >>>>>>>
> >>>>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
> >>>>>>> the screen is black with blinking cursor at position [1, 1].
> >>>>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
> >>>>>>> far.
> >>>>>>>
> >>>>>>> I'm using pm-suspend, any ideas what to test before I start to find the
> >>>>>>> reason on my own?
> >>>>>>
> >>>>>> Please try the pm_test tests for core, processors and devices, eg.:
> >>>>>
> >>>>> Hmm, I haven't seen the issues since then. So it had to be some kind of
> >>>>> coincidence -- I see the issue occasionally for some time already. Now
> >>>>> it triggered twice in a row after I updated the kernel.
> >>>>
> >>>> Hmm.  What hardware is that?
> >>>
> >>> What exactly do you want to know about it? It's some specific intel
> >>> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
> >>> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.
> >>
> >> I'm seeing pretty much the same symptoms on quite different hardware, except
> >> for one thing: USB keyboard and mouse.
> >>
> >> Have you checked if writing 0 to /sys/power/pm_async helps?
> > 
> > It's very hard to reproduce (it happens once a week or two), so I can't
> > say yet. As it happened yesterday again, going to test it from now on.
> 
> Ok, I haven't seen the issue with 0 in /sys/power/pm_async for two weeks
> now (I added it to boot.local). I would say it's related to that...

In that case the next step would be to build the kernel with
CONFIG_PM_ADVANCED_DEBUG set and try to switch the async flag for individual
devices (it is located is /sys/devices/.../power/ for each device).

For example, I wonder if it is sufficient to unset it for all USB devices.

Thanks,
Rafael

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-01-20 15:23               ` Jiri Slaby
  2011-01-20 21:02                 ` Rafael J. Wysocki
@ 2011-01-20 21:02                 ` Rafael J. Wysocki
  1 sibling, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2011-01-20 21:02 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: akpm, linux-kernel, Linux-pm mailing list

On Thursday, January 20, 2011, Jiri Slaby wrote:
> On 01/06/2011 03:18 PM, Jiri Slaby wrote:
> > On 12/14/2010 11:22 PM, Rafael J. Wysocki wrote:
> >> On Tuesday, December 14, 2010, Jiri Slaby wrote:
> >>> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
> >>>> On Monday, December 13, 2010, Jiri Slaby wrote:
> >>>>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
> >>>>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
> >>>>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
> >>>>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> >>>>>>>
> >>>>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
> >>>>>>> the screen is black with blinking cursor at position [1, 1].
> >>>>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
> >>>>>>> far.
> >>>>>>>
> >>>>>>> I'm using pm-suspend, any ideas what to test before I start to find the
> >>>>>>> reason on my own?
> >>>>>>
> >>>>>> Please try the pm_test tests for core, processors and devices, eg.:
> >>>>>
> >>>>> Hmm, I haven't seen the issues since then. So it had to be some kind of
> >>>>> coincidence -- I see the issue occasionally for some time already. Now
> >>>>> it triggered twice in a row after I updated the kernel.
> >>>>
> >>>> Hmm.  What hardware is that?
> >>>
> >>> What exactly do you want to know about it? It's some specific intel
> >>> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
> >>> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.
> >>
> >> I'm seeing pretty much the same symptoms on quite different hardware, except
> >> for one thing: USB keyboard and mouse.
> >>
> >> Have you checked if writing 0 to /sys/power/pm_async helps?
> > 
> > It's very hard to reproduce (it happens once a week or two), so I can't
> > say yet. As it happened yesterday again, going to test it from now on.
> 
> Ok, I haven't seen the issue with 0 in /sys/power/pm_async for two weeks
> now (I added it to boot.local). I would say it's related to that...

In that case the next step would be to build the kernel with
CONFIG_PM_ADVANCED_DEBUG set and try to switch the async flag for individual
devices (it is located is /sys/devices/.../power/ for each device).

For example, I wonder if it is sufficient to unset it for all USB devices.

Thanks,
Rafael

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-01-20 21:02                 ` Rafael J. Wysocki
  2011-01-21  9:16                   ` Jiri Slaby
@ 2011-01-21  9:16                   ` Jiri Slaby
  2011-01-31 21:37                   ` Jiri Slaby
  2011-01-31 21:37                   ` Jiri Slaby
  3 siblings, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-01-21  9:16 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 01/20/2011 10:02 PM, Rafael J. Wysocki wrote:
> In that case the next step would be to build the kernel with
> CONFIG_PM_ADVANCED_DEBUG set and try to switch the async flag for individual
> devices (it is located is /sys/devices/.../power/ for each device).
> 
> For example, I wonder if it is sufficient to unset it for all USB devices.

Ok, I added
for aa in /sys/bus/usb/devices/*/power/async; do
        echo disabled > $aa
done
to /etc/init.d/boot.local. Let's see :).

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-01-20 21:02                 ` Rafael J. Wysocki
@ 2011-01-21  9:16                   ` Jiri Slaby
  2011-01-21  9:16                   ` Jiri Slaby
                                     ` (2 subsequent siblings)
  3 siblings, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-01-21  9:16 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 01/20/2011 10:02 PM, Rafael J. Wysocki wrote:
> In that case the next step would be to build the kernel with
> CONFIG_PM_ADVANCED_DEBUG set and try to switch the async flag for individual
> devices (it is located is /sys/devices/.../power/ for each device).
> 
> For example, I wonder if it is sufficient to unset it for all USB devices.

Ok, I added
for aa in /sys/bus/usb/devices/*/power/async; do
        echo disabled > $aa
done
to /etc/init.d/boot.local. Let's see :).

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-01-20 21:02                 ` Rafael J. Wysocki
  2011-01-21  9:16                   ` Jiri Slaby
  2011-01-21  9:16                   ` Jiri Slaby
@ 2011-01-31 21:37                   ` Jiri Slaby
  2011-01-31 21:40                     ` Jiri Slaby
                                       ` (3 more replies)
  2011-01-31 21:37                   ` Jiri Slaby
  3 siblings, 4 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-01-31 21:37 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 01/20/2011 10:02 PM, Rafael J. Wysocki wrote:
> On Thursday, January 20, 2011, Jiri Slaby wrote:
>> On 01/06/2011 03:18 PM, Jiri Slaby wrote:
>>> On 12/14/2010 11:22 PM, Rafael J. Wysocki wrote:
>>>> On Tuesday, December 14, 2010, Jiri Slaby wrote:
>>>>> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
>>>>>> On Monday, December 13, 2010, Jiri Slaby wrote:
>>>>>>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
>>>>>>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
>>>>>>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
>>>>>>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>>>>>>>>>
>>>>>>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
>>>>>>>>> the screen is black with blinking cursor at position [1, 1].
>>>>>>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
>>>>>>>>> far.
>>>>>>>>>
>>>>>>>>> I'm using pm-suspend, any ideas what to test before I start to find the
>>>>>>>>> reason on my own?
>>>>>>>>
>>>>>>>> Please try the pm_test tests for core, processors and devices, eg.:
>>>>>>>
>>>>>>> Hmm, I haven't seen the issues since then. So it had to be some kind of
>>>>>>> coincidence -- I see the issue occasionally for some time already. Now
>>>>>>> it triggered twice in a row after I updated the kernel.
>>>>>>
>>>>>> Hmm.  What hardware is that?
>>>>>
>>>>> What exactly do you want to know about it? It's some specific intel
>>>>> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
>>>>> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.
>>>>
>>>> I'm seeing pretty much the same symptoms on quite different hardware, except
>>>> for one thing: USB keyboard and mouse.
>>>>
>>>> Have you checked if writing 0 to /sys/power/pm_async helps?
>>>
>>> It's very hard to reproduce (it happens once a week or two), so I can't
>>> say yet. As it happened yesterday again, going to test it from now on.
>>
>> Ok, I haven't seen the issue with 0 in /sys/power/pm_async for two weeks
>> now (I added it to boot.local). I would say it's related to that...
> 
> In that case the next step would be to build the kernel with
> CONFIG_PM_ADVANCED_DEBUG set and try to switch the async flag for individual
> devices (it is located is /sys/devices/.../power/ for each device).
> 
> For example, I wonder if it is sufficient to unset it for all USB devices.

It seems to suffice... No hangs still. Should I enable pm_async back
again to confirm the issue is still present?

Note that I also had had issues with fan which was at full speed after
resume sometimes (very rarely, like this issue). Full power-cycle was
needed to cure that. I don't see that now as well.

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-01-20 21:02                 ` Rafael J. Wysocki
                                     ` (2 preceding siblings ...)
  2011-01-31 21:37                   ` Jiri Slaby
@ 2011-01-31 21:37                   ` Jiri Slaby
  3 siblings, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-01-31 21:37 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 01/20/2011 10:02 PM, Rafael J. Wysocki wrote:
> On Thursday, January 20, 2011, Jiri Slaby wrote:
>> On 01/06/2011 03:18 PM, Jiri Slaby wrote:
>>> On 12/14/2010 11:22 PM, Rafael J. Wysocki wrote:
>>>> On Tuesday, December 14, 2010, Jiri Slaby wrote:
>>>>> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
>>>>>> On Monday, December 13, 2010, Jiri Slaby wrote:
>>>>>>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
>>>>>>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
>>>>>>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
>>>>>>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>>>>>>>>>
>>>>>>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
>>>>>>>>> the screen is black with blinking cursor at position [1, 1].
>>>>>>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
>>>>>>>>> far.
>>>>>>>>>
>>>>>>>>> I'm using pm-suspend, any ideas what to test before I start to find the
>>>>>>>>> reason on my own?
>>>>>>>>
>>>>>>>> Please try the pm_test tests for core, processors and devices, eg.:
>>>>>>>
>>>>>>> Hmm, I haven't seen the issues since then. So it had to be some kind of
>>>>>>> coincidence -- I see the issue occasionally for some time already. Now
>>>>>>> it triggered twice in a row after I updated the kernel.
>>>>>>
>>>>>> Hmm.  What hardware is that?
>>>>>
>>>>> What exactly do you want to know about it? It's some specific intel
>>>>> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
>>>>> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.
>>>>
>>>> I'm seeing pretty much the same symptoms on quite different hardware, except
>>>> for one thing: USB keyboard and mouse.
>>>>
>>>> Have you checked if writing 0 to /sys/power/pm_async helps?
>>>
>>> It's very hard to reproduce (it happens once a week or two), so I can't
>>> say yet. As it happened yesterday again, going to test it from now on.
>>
>> Ok, I haven't seen the issue with 0 in /sys/power/pm_async for two weeks
>> now (I added it to boot.local). I would say it's related to that...
> 
> In that case the next step would be to build the kernel with
> CONFIG_PM_ADVANCED_DEBUG set and try to switch the async flag for individual
> devices (it is located is /sys/devices/.../power/ for each device).
> 
> For example, I wonder if it is sufficient to unset it for all USB devices.

It seems to suffice... No hangs still. Should I enable pm_async back
again to confirm the issue is still present?

Note that I also had had issues with fan which was at full speed after
resume sometimes (very rarely, like this issue). Full power-cycle was
needed to cure that. I don't see that now as well.

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-01-31 21:37                   ` Jiri Slaby
  2011-01-31 21:40                     ` Jiri Slaby
@ 2011-01-31 21:40                     ` Jiri Slaby
  2011-01-31 22:00                     ` Rafael J. Wysocki
  2011-01-31 22:00                     ` Rafael J. Wysocki
  3 siblings, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-01-31 21:40 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 01/31/2011 10:37 PM, Jiri Slaby wrote:
> On 01/20/2011 10:02 PM, Rafael J. Wysocki wrote:
>> On Thursday, January 20, 2011, Jiri Slaby wrote:
>>> On 01/06/2011 03:18 PM, Jiri Slaby wrote:
>>>> On 12/14/2010 11:22 PM, Rafael J. Wysocki wrote:
>>>>> On Tuesday, December 14, 2010, Jiri Slaby wrote:
>>>>>> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
>>>>>>> On Monday, December 13, 2010, Jiri Slaby wrote:
>>>>>>>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
>>>>>>>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
>>>>>>>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
>>>>>>>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>>>>>>>>>>
>>>>>>>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
>>>>>>>>>> the screen is black with blinking cursor at position [1, 1].
>>>>>>>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
>>>>>>>>>> far.
>>>>>>>>>>
>>>>>>>>>> I'm using pm-suspend, any ideas what to test before I start to find the
>>>>>>>>>> reason on my own?
>>>>>>>>>
>>>>>>>>> Please try the pm_test tests for core, processors and devices, eg.:
>>>>>>>>
>>>>>>>> Hmm, I haven't seen the issues since then. So it had to be some kind of
>>>>>>>> coincidence -- I see the issue occasionally for some time already. Now
>>>>>>>> it triggered twice in a row after I updated the kernel.
>>>>>>>
>>>>>>> Hmm.  What hardware is that?
>>>>>>
>>>>>> What exactly do you want to know about it? It's some specific intel
>>>>>> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
>>>>>> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.
>>>>>
>>>>> I'm seeing pretty much the same symptoms on quite different hardware, except
>>>>> for one thing: USB keyboard and mouse.
>>>>>
>>>>> Have you checked if writing 0 to /sys/power/pm_async helps?
>>>>
>>>> It's very hard to reproduce (it happens once a week or two), so I can't
>>>> say yet. As it happened yesterday again, going to test it from now on.
>>>
>>> Ok, I haven't seen the issue with 0 in /sys/power/pm_async for two weeks
>>> now (I added it to boot.local). I would say it's related to that...
>>
>> In that case the next step would be to build the kernel with
>> CONFIG_PM_ADVANCED_DEBUG set and try to switch the async flag for individual
>> devices (it is located is /sys/devices/.../power/ for each device).
>>
>> For example, I wonder if it is sufficient to unset it for all USB devices.
> 
> It seems to suffice... No hangs still. Should I enable pm_async back
> again to confirm the issue is still present?

BTW. I'm currently writing "disabled" into:
/sys/bus/usb/devices/usb1/power/async
/sys/bus/usb/devices/usb2/power/async
/sys/bus/usb/devices/usb3/power/async
/sys/bus/usb/devices/usb4/power/async
/sys/bus/usb/devices/usb5/power/async
/sys/bus/usb/devices/usb6/power/async
/sys/bus/usb/devices/usb7/power/async
/sys/bus/usb/devices/usb8/power/async
/sys/bus/usb/devices/1-0:1.0/power/async
/sys/bus/usb/devices/2-0:1.0/power/async
/sys/bus/usb/devices/2-6/power/async
/sys/bus/usb/devices/2-6:1.0/power/async
/sys/bus/usb/devices/2-6:1.1/power/async
/sys/bus/usb/devices/3-0:1.0/power/async
/sys/bus/usb/devices/4-0:1.0/power/async
/sys/bus/usb/devices/4-2/power/async
/sys/bus/usb/devices/4-2.1/power/async
/sys/bus/usb/devices/4-2:1.0/power/async
/sys/bus/usb/devices/4-2.1:1.0/power/async
/sys/bus/usb/devices/4-2.1:1.1/power/async
/sys/bus/usb/devices/4-2.2/power/async
/sys/bus/usb/devices/4-2.2:1.0/power/async
/sys/bus/usb/devices/5-0:1.0/power/async
/sys/bus/usb/devices/6-0:1.0/power/async
/sys/bus/usb/devices/7-0:1.0/power/async
/sys/bus/usb/devices/8-0:1.0/power/async


/sys/power/pm_async is 1

lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0413:6029 Leadtek Research, Inc. WinFast DTV
Dongle Gold
Bus 004 Device 002: ID 04b4:2050 Cypress Semiconductor Corp. hub
Bus 004 Device 003: ID 0458:004c KYE Systems Corp. (Mouse Systems)
Slimstar Pro Keyboard
Bus 004 Device 004: ID 045e:00f0 Microsoft Corp.


regards,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-01-31 21:37                   ` Jiri Slaby
@ 2011-01-31 21:40                     ` Jiri Slaby
  2011-01-31 21:40                     ` Jiri Slaby
                                       ` (2 subsequent siblings)
  3 siblings, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-01-31 21:40 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 01/31/2011 10:37 PM, Jiri Slaby wrote:
> On 01/20/2011 10:02 PM, Rafael J. Wysocki wrote:
>> On Thursday, January 20, 2011, Jiri Slaby wrote:
>>> On 01/06/2011 03:18 PM, Jiri Slaby wrote:
>>>> On 12/14/2010 11:22 PM, Rafael J. Wysocki wrote:
>>>>> On Tuesday, December 14, 2010, Jiri Slaby wrote:
>>>>>> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
>>>>>>> On Monday, December 13, 2010, Jiri Slaby wrote:
>>>>>>>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
>>>>>>>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
>>>>>>>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
>>>>>>>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>>>>>>>>>>
>>>>>>>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
>>>>>>>>>> the screen is black with blinking cursor at position [1, 1].
>>>>>>>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
>>>>>>>>>> far.
>>>>>>>>>>
>>>>>>>>>> I'm using pm-suspend, any ideas what to test before I start to find the
>>>>>>>>>> reason on my own?
>>>>>>>>>
>>>>>>>>> Please try the pm_test tests for core, processors and devices, eg.:
>>>>>>>>
>>>>>>>> Hmm, I haven't seen the issues since then. So it had to be some kind of
>>>>>>>> coincidence -- I see the issue occasionally for some time already. Now
>>>>>>>> it triggered twice in a row after I updated the kernel.
>>>>>>>
>>>>>>> Hmm.  What hardware is that?
>>>>>>
>>>>>> What exactly do you want to know about it? It's some specific intel
>>>>>> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
>>>>>> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.
>>>>>
>>>>> I'm seeing pretty much the same symptoms on quite different hardware, except
>>>>> for one thing: USB keyboard and mouse.
>>>>>
>>>>> Have you checked if writing 0 to /sys/power/pm_async helps?
>>>>
>>>> It's very hard to reproduce (it happens once a week or two), so I can't
>>>> say yet. As it happened yesterday again, going to test it from now on.
>>>
>>> Ok, I haven't seen the issue with 0 in /sys/power/pm_async for two weeks
>>> now (I added it to boot.local). I would say it's related to that...
>>
>> In that case the next step would be to build the kernel with
>> CONFIG_PM_ADVANCED_DEBUG set and try to switch the async flag for individual
>> devices (it is located is /sys/devices/.../power/ for each device).
>>
>> For example, I wonder if it is sufficient to unset it for all USB devices.
> 
> It seems to suffice... No hangs still. Should I enable pm_async back
> again to confirm the issue is still present?

BTW. I'm currently writing "disabled" into:
/sys/bus/usb/devices/usb1/power/async
/sys/bus/usb/devices/usb2/power/async
/sys/bus/usb/devices/usb3/power/async
/sys/bus/usb/devices/usb4/power/async
/sys/bus/usb/devices/usb5/power/async
/sys/bus/usb/devices/usb6/power/async
/sys/bus/usb/devices/usb7/power/async
/sys/bus/usb/devices/usb8/power/async
/sys/bus/usb/devices/1-0:1.0/power/async
/sys/bus/usb/devices/2-0:1.0/power/async
/sys/bus/usb/devices/2-6/power/async
/sys/bus/usb/devices/2-6:1.0/power/async
/sys/bus/usb/devices/2-6:1.1/power/async
/sys/bus/usb/devices/3-0:1.0/power/async
/sys/bus/usb/devices/4-0:1.0/power/async
/sys/bus/usb/devices/4-2/power/async
/sys/bus/usb/devices/4-2.1/power/async
/sys/bus/usb/devices/4-2:1.0/power/async
/sys/bus/usb/devices/4-2.1:1.0/power/async
/sys/bus/usb/devices/4-2.1:1.1/power/async
/sys/bus/usb/devices/4-2.2/power/async
/sys/bus/usb/devices/4-2.2:1.0/power/async
/sys/bus/usb/devices/5-0:1.0/power/async
/sys/bus/usb/devices/6-0:1.0/power/async
/sys/bus/usb/devices/7-0:1.0/power/async
/sys/bus/usb/devices/8-0:1.0/power/async


/sys/power/pm_async is 1

lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0413:6029 Leadtek Research, Inc. WinFast DTV
Dongle Gold
Bus 004 Device 002: ID 04b4:2050 Cypress Semiconductor Corp. hub
Bus 004 Device 003: ID 0458:004c KYE Systems Corp. (Mouse Systems)
Slimstar Pro Keyboard
Bus 004 Device 004: ID 045e:00f0 Microsoft Corp.


regards,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-01-31 21:37                   ` Jiri Slaby
                                       ` (2 preceding siblings ...)
  2011-01-31 22:00                     ` Rafael J. Wysocki
@ 2011-01-31 22:00                     ` Rafael J. Wysocki
  2011-02-04 18:33                       ` Jiri Slaby
  2011-02-04 18:33                       ` Jiri Slaby
  3 siblings, 2 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2011-01-31 22:00 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: akpm, linux-kernel, Linux-pm mailing list

On Monday, January 31, 2011, Jiri Slaby wrote:
> On 01/20/2011 10:02 PM, Rafael J. Wysocki wrote:
> > On Thursday, January 20, 2011, Jiri Slaby wrote:
> >> On 01/06/2011 03:18 PM, Jiri Slaby wrote:
> >>> On 12/14/2010 11:22 PM, Rafael J. Wysocki wrote:
> >>>> On Tuesday, December 14, 2010, Jiri Slaby wrote:
> >>>>> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
> >>>>>> On Monday, December 13, 2010, Jiri Slaby wrote:
> >>>>>>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
> >>>>>>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
> >>>>>>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
> >>>>>>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> >>>>>>>>>
> >>>>>>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
> >>>>>>>>> the screen is black with blinking cursor at position [1, 1].
> >>>>>>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
> >>>>>>>>> far.
> >>>>>>>>>
> >>>>>>>>> I'm using pm-suspend, any ideas what to test before I start to find the
> >>>>>>>>> reason on my own?
> >>>>>>>>
> >>>>>>>> Please try the pm_test tests for core, processors and devices, eg.:
> >>>>>>>
> >>>>>>> Hmm, I haven't seen the issues since then. So it had to be some kind of
> >>>>>>> coincidence -- I see the issue occasionally for some time already. Now
> >>>>>>> it triggered twice in a row after I updated the kernel.
> >>>>>>
> >>>>>> Hmm.  What hardware is that?
> >>>>>
> >>>>> What exactly do you want to know about it? It's some specific intel
> >>>>> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
> >>>>> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.
> >>>>
> >>>> I'm seeing pretty much the same symptoms on quite different hardware, except
> >>>> for one thing: USB keyboard and mouse.
> >>>>
> >>>> Have you checked if writing 0 to /sys/power/pm_async helps?
> >>>
> >>> It's very hard to reproduce (it happens once a week or two), so I can't
> >>> say yet. As it happened yesterday again, going to test it from now on.
> >>
> >> Ok, I haven't seen the issue with 0 in /sys/power/pm_async for two weeks
> >> now (I added it to boot.local). I would say it's related to that...
> > 
> > In that case the next step would be to build the kernel with
> > CONFIG_PM_ADVANCED_DEBUG set and try to switch the async flag for individual
> > devices (it is located is /sys/devices/.../power/ for each device).
> > 
> > For example, I wonder if it is sufficient to unset it for all USB devices.
> 
> It seems to suffice... No hangs still. Should I enable pm_async back
> again to confirm the issue is still present?

Yes, please, it would be good to know for sure.

> Note that I also had had issues with fan which was at full speed after
> resume sometimes (very rarely, like this issue). Full power-cycle was
> needed to cure that. I don't see that now as well.

This most likely was a different issue and I'd expect it to be fixed by
the ACPI patches that went in during the last merge window.

Thanks,
Rafael

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-01-31 21:37                   ` Jiri Slaby
  2011-01-31 21:40                     ` Jiri Slaby
  2011-01-31 21:40                     ` Jiri Slaby
@ 2011-01-31 22:00                     ` Rafael J. Wysocki
  2011-01-31 22:00                     ` Rafael J. Wysocki
  3 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2011-01-31 22:00 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: akpm, linux-kernel, Linux-pm mailing list

On Monday, January 31, 2011, Jiri Slaby wrote:
> On 01/20/2011 10:02 PM, Rafael J. Wysocki wrote:
> > On Thursday, January 20, 2011, Jiri Slaby wrote:
> >> On 01/06/2011 03:18 PM, Jiri Slaby wrote:
> >>> On 12/14/2010 11:22 PM, Rafael J. Wysocki wrote:
> >>>> On Tuesday, December 14, 2010, Jiri Slaby wrote:
> >>>>> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
> >>>>>> On Monday, December 13, 2010, Jiri Slaby wrote:
> >>>>>>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
> >>>>>>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
> >>>>>>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
> >>>>>>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> >>>>>>>>>
> >>>>>>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
> >>>>>>>>> the screen is black with blinking cursor at position [1, 1].
> >>>>>>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
> >>>>>>>>> far.
> >>>>>>>>>
> >>>>>>>>> I'm using pm-suspend, any ideas what to test before I start to find the
> >>>>>>>>> reason on my own?
> >>>>>>>>
> >>>>>>>> Please try the pm_test tests for core, processors and devices, eg.:
> >>>>>>>
> >>>>>>> Hmm, I haven't seen the issues since then. So it had to be some kind of
> >>>>>>> coincidence -- I see the issue occasionally for some time already. Now
> >>>>>>> it triggered twice in a row after I updated the kernel.
> >>>>>>
> >>>>>> Hmm.  What hardware is that?
> >>>>>
> >>>>> What exactly do you want to know about it? It's some specific intel
> >>>>> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
> >>>>> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.
> >>>>
> >>>> I'm seeing pretty much the same symptoms on quite different hardware, except
> >>>> for one thing: USB keyboard and mouse.
> >>>>
> >>>> Have you checked if writing 0 to /sys/power/pm_async helps?
> >>>
> >>> It's very hard to reproduce (it happens once a week or two), so I can't
> >>> say yet. As it happened yesterday again, going to test it from now on.
> >>
> >> Ok, I haven't seen the issue with 0 in /sys/power/pm_async for two weeks
> >> now (I added it to boot.local). I would say it's related to that...
> > 
> > In that case the next step would be to build the kernel with
> > CONFIG_PM_ADVANCED_DEBUG set and try to switch the async flag for individual
> > devices (it is located is /sys/devices/.../power/ for each device).
> > 
> > For example, I wonder if it is sufficient to unset it for all USB devices.
> 
> It seems to suffice... No hangs still. Should I enable pm_async back
> again to confirm the issue is still present?

Yes, please, it would be good to know for sure.

> Note that I also had had issues with fan which was at full speed after
> resume sometimes (very rarely, like this issue). Full power-cycle was
> needed to cure that. I don't see that now as well.

This most likely was a different issue and I'd expect it to be fixed by
the ACPI patches that went in during the last merge window.

Thanks,
Rafael

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-01-31 22:00                     ` Rafael J. Wysocki
@ 2011-02-04 18:33                       ` Jiri Slaby
  2011-02-04 19:33                         ` [linux-pm] " Alan Stern
  2011-02-04 19:33                         ` Alan Stern
  2011-02-04 18:33                       ` Jiri Slaby
  1 sibling, 2 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-02-04 18:33 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 01/31/2011 11:00 PM, Rafael J. Wysocki wrote:
> On Monday, January 31, 2011, Jiri Slaby wrote:
>> On 01/20/2011 10:02 PM, Rafael J. Wysocki wrote:
>>> On Thursday, January 20, 2011, Jiri Slaby wrote:
>>>> On 01/06/2011 03:18 PM, Jiri Slaby wrote:
>>>>> On 12/14/2010 11:22 PM, Rafael J. Wysocki wrote:
>>>>>> On Tuesday, December 14, 2010, Jiri Slaby wrote:
>>>>>>> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
>>>>>>>> On Monday, December 13, 2010, Jiri Slaby wrote:
>>>>>>>>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
>>>>>>>>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
>>>>>>>>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
>>>>>>>>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>>>>>>>>>>>
>>>>>>>>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
>>>>>>>>>>> the screen is black with blinking cursor at position [1, 1].
>>>>>>>>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
>>>>>>>>>>> far.
>>>>>>>>>>>
>>>>>>>>>>> I'm using pm-suspend, any ideas what to test before I start to find the
>>>>>>>>>>> reason on my own?
>>>>>>>>>>
>>>>>>>>>> Please try the pm_test tests for core, processors and devices, eg.:
>>>>>>>>>
>>>>>>>>> Hmm, I haven't seen the issues since then. So it had to be some kind of
>>>>>>>>> coincidence -- I see the issue occasionally for some time already. Now
>>>>>>>>> it triggered twice in a row after I updated the kernel.
>>>>>>>>
>>>>>>>> Hmm.  What hardware is that?
>>>>>>>
>>>>>>> What exactly do you want to know about it? It's some specific intel
>>>>>>> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
>>>>>>> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.
>>>>>>
>>>>>> I'm seeing pretty much the same symptoms on quite different hardware, except
>>>>>> for one thing: USB keyboard and mouse.
>>>>>>
>>>>>> Have you checked if writing 0 to /sys/power/pm_async helps?
>>>>>
>>>>> It's very hard to reproduce (it happens once a week or two), so I can't
>>>>> say yet. As it happened yesterday again, going to test it from now on.
>>>>
>>>> Ok, I haven't seen the issue with 0 in /sys/power/pm_async for two weeks
>>>> now (I added it to boot.local). I would say it's related to that...
>>>
>>> In that case the next step would be to build the kernel with
>>> CONFIG_PM_ADVANCED_DEBUG set and try to switch the async flag for individual
>>> devices (it is located is /sys/devices/.../power/ for each device).
>>>
>>> For example, I wonder if it is sufficient to unset it for all USB devices.
>>
>> It seems to suffice... No hangs still. Should I enable pm_async back
>> again to confirm the issue is still present?
> 
> Yes, please, it would be good to know for sure.

Ok, confirmed right now :).

I disabled pm_async for USB again. What do you suggest next?

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-01-31 22:00                     ` Rafael J. Wysocki
  2011-02-04 18:33                       ` Jiri Slaby
@ 2011-02-04 18:33                       ` Jiri Slaby
  1 sibling, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-02-04 18:33 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 01/31/2011 11:00 PM, Rafael J. Wysocki wrote:
> On Monday, January 31, 2011, Jiri Slaby wrote:
>> On 01/20/2011 10:02 PM, Rafael J. Wysocki wrote:
>>> On Thursday, January 20, 2011, Jiri Slaby wrote:
>>>> On 01/06/2011 03:18 PM, Jiri Slaby wrote:
>>>>> On 12/14/2010 11:22 PM, Rafael J. Wysocki wrote:
>>>>>> On Tuesday, December 14, 2010, Jiri Slaby wrote:
>>>>>>> On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
>>>>>>>> On Monday, December 13, 2010, Jiri Slaby wrote:
>>>>>>>>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
>>>>>>>>>> On Sunday, December 05, 2010, Jiri Slaby wrote:
>>>>>>>>>>> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
>>>>>>>>>>>> The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
>>>>>>>>>>>
>>>>>>>>>>> Hi, this kernel regresses with respect to resume. It doesn't wake up,
>>>>>>>>>>> the screen is black with blinking cursor at position [1, 1].
>>>>>>>>>>> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
>>>>>>>>>>> far.
>>>>>>>>>>>
>>>>>>>>>>> I'm using pm-suspend, any ideas what to test before I start to find the
>>>>>>>>>>> reason on my own?
>>>>>>>>>>
>>>>>>>>>> Please try the pm_test tests for core, processors and devices, eg.:
>>>>>>>>>
>>>>>>>>> Hmm, I haven't seen the issues since then. So it had to be some kind of
>>>>>>>>> coincidence -- I see the issue occasionally for some time already. Now
>>>>>>>>> it triggered twice in a row after I updated the kernel.
>>>>>>>>
>>>>>>>> Hmm.  What hardware is that?
>>>>>>>
>>>>>>> What exactly do you want to know about it? It's some specific intel
>>>>>>> desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
>>>>>>> raid, dvb-t usb receiver (af9015), usb keyboard and mouse.
>>>>>>
>>>>>> I'm seeing pretty much the same symptoms on quite different hardware, except
>>>>>> for one thing: USB keyboard and mouse.
>>>>>>
>>>>>> Have you checked if writing 0 to /sys/power/pm_async helps?
>>>>>
>>>>> It's very hard to reproduce (it happens once a week or two), so I can't
>>>>> say yet. As it happened yesterday again, going to test it from now on.
>>>>
>>>> Ok, I haven't seen the issue with 0 in /sys/power/pm_async for two weeks
>>>> now (I added it to boot.local). I would say it's related to that...
>>>
>>> In that case the next step would be to build the kernel with
>>> CONFIG_PM_ADVANCED_DEBUG set and try to switch the async flag for individual
>>> devices (it is located is /sys/devices/.../power/ for each device).
>>>
>>> For example, I wonder if it is sufficient to unset it for all USB devices.
>>
>> It seems to suffice... No hangs still. Should I enable pm_async back
>> again to confirm the issue is still present?
> 
> Yes, please, it would be good to know for sure.

Ok, confirmed right now :).

I disabled pm_async for USB again. What do you suggest next?

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-04 18:33                       ` Jiri Slaby
@ 2011-02-04 19:33                         ` Alan Stern
  2011-02-04 19:38                           ` Jiri Slaby
                                             ` (3 more replies)
  2011-02-04 19:33                         ` Alan Stern
  1 sibling, 4 replies; 77+ messages in thread
From: Alan Stern @ 2011-02-04 19:33 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On Fri, 4 Feb 2011, Jiri Slaby wrote:

> >> It seems to suffice... No hangs still. Should I enable pm_async back
> >> again to confirm the issue is still present?
> > 
> > Yes, please, it would be good to know for sure.
> 
> Ok, confirmed right now :).
> 
> I disabled pm_async for USB again. What do you suggest next?

What happens if you leave pm_async enabled but unplug all the USB 
devices before suspending?  If there are any USB devices you can't 
unplug, you can get an equivalent result by unconfiguring the root 
hubs:

	for a in /sys/bus/usb/devices/usb* ; do
		echo 0 >$a/bConfigurationValue
	done

Alan Stern


^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-04 18:33                       ` Jiri Slaby
  2011-02-04 19:33                         ` [linux-pm] " Alan Stern
@ 2011-02-04 19:33                         ` Alan Stern
  1 sibling, 0 replies; 77+ messages in thread
From: Alan Stern @ 2011-02-04 19:33 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On Fri, 4 Feb 2011, Jiri Slaby wrote:

> >> It seems to suffice... No hangs still. Should I enable pm_async back
> >> again to confirm the issue is still present?
> > 
> > Yes, please, it would be good to know for sure.
> 
> Ok, confirmed right now :).
> 
> I disabled pm_async for USB again. What do you suggest next?

What happens if you leave pm_async enabled but unplug all the USB 
devices before suspending?  If there are any USB devices you can't 
unplug, you can get an equivalent result by unconfiguring the root 
hubs:

	for a in /sys/bus/usb/devices/usb* ; do
		echo 0 >$a/bConfigurationValue
	done

Alan Stern

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-04 19:33                         ` [linux-pm] " Alan Stern
  2011-02-04 19:38                           ` Jiri Slaby
@ 2011-02-04 19:38                           ` Jiri Slaby
  2011-02-04 20:07                             ` Alan Stern
  2011-02-04 20:07                             ` [linux-pm] " Alan Stern
  2011-02-22  8:45                           ` Jiri Slaby
  2011-02-22  8:45                           ` [linux-pm] " Jiri Slaby
  3 siblings, 2 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-02-04 19:38 UTC (permalink / raw)
  To: Alan Stern; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On 02/04/2011 08:33 PM, Alan Stern wrote:
> On Fri, 4 Feb 2011, Jiri Slaby wrote:
> 
>>>> It seems to suffice... No hangs still. Should I enable pm_async back
>>>> again to confirm the issue is still present?
>>>
>>> Yes, please, it would be good to know for sure.
>>
>> Ok, confirmed right now :).
>>
>> I disabled pm_async for USB again. What do you suggest next?
> 
> What happens if you leave pm_async enabled but unplug all the USB 
> devices before suspending?

Then I cannot suspend at all (ENOINPUTDEVICE)... And this would be
painful as the bug occurs once a week or so.

> If there are any USB devices you can't 
> unplug, you can get an equivalent result by unconfiguring the root 
> hubs:
> 
> 	for a in /sys/bus/usb/devices/usb* ; do
> 		echo 0 >$a/bConfigurationValue
> 	done

Well, I can put this into suspend/resume scripts. What's the opposite
operation? 1 > $a/bConfigurationValue?

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-04 19:33                         ` [linux-pm] " Alan Stern
@ 2011-02-04 19:38                           ` Jiri Slaby
  2011-02-04 19:38                           ` [linux-pm] " Jiri Slaby
                                             ` (2 subsequent siblings)
  3 siblings, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-02-04 19:38 UTC (permalink / raw)
  To: Alan Stern; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On 02/04/2011 08:33 PM, Alan Stern wrote:
> On Fri, 4 Feb 2011, Jiri Slaby wrote:
> 
>>>> It seems to suffice... No hangs still. Should I enable pm_async back
>>>> again to confirm the issue is still present?
>>>
>>> Yes, please, it would be good to know for sure.
>>
>> Ok, confirmed right now :).
>>
>> I disabled pm_async for USB again. What do you suggest next?
> 
> What happens if you leave pm_async enabled but unplug all the USB 
> devices before suspending?

Then I cannot suspend at all (ENOINPUTDEVICE)... And this would be
painful as the bug occurs once a week or so.

> If there are any USB devices you can't 
> unplug, you can get an equivalent result by unconfiguring the root 
> hubs:
> 
> 	for a in /sys/bus/usb/devices/usb* ; do
> 		echo 0 >$a/bConfigurationValue
> 	done

Well, I can put this into suspend/resume scripts. What's the opposite
operation? 1 > $a/bConfigurationValue?

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-04 19:38                           ` [linux-pm] " Jiri Slaby
  2011-02-04 20:07                             ` Alan Stern
@ 2011-02-04 20:07                             ` Alan Stern
  1 sibling, 0 replies; 77+ messages in thread
From: Alan Stern @ 2011-02-04 20:07 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On Fri, 4 Feb 2011, Jiri Slaby wrote:

> On 02/04/2011 08:33 PM, Alan Stern wrote:
> > On Fri, 4 Feb 2011, Jiri Slaby wrote:
> > 
> >>>> It seems to suffice... No hangs still. Should I enable pm_async back
> >>>> again to confirm the issue is still present?
> >>>
> >>> Yes, please, it would be good to know for sure.
> >>
> >> Ok, confirmed right now :).
> >>
> >> I disabled pm_async for USB again. What do you suggest next?
> > 
> > What happens if you leave pm_async enabled but unplug all the USB 
> > devices before suspending?
> 
> Then I cannot suspend at all (ENOINPUTDEVICE)... And this would be
> painful as the bug occurs once a week or so.

You can suspend using a remote network login.  Agreed, this would be 
painful.

> > If there are any USB devices you can't 
> > unplug, you can get an equivalent result by unconfiguring the root 
> > hubs:
> > 
> > 	for a in /sys/bus/usb/devices/usb* ; do
> > 		echo 0 >$a/bConfigurationValue
> > 	done
> 
> Well, I can put this into suspend/resume scripts. What's the opposite
> operation? 1 > $a/bConfigurationValue?

Yes.

Alan Stern


^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-04 19:38                           ` [linux-pm] " Jiri Slaby
@ 2011-02-04 20:07                             ` Alan Stern
  2011-02-04 20:07                             ` [linux-pm] " Alan Stern
  1 sibling, 0 replies; 77+ messages in thread
From: Alan Stern @ 2011-02-04 20:07 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On Fri, 4 Feb 2011, Jiri Slaby wrote:

> On 02/04/2011 08:33 PM, Alan Stern wrote:
> > On Fri, 4 Feb 2011, Jiri Slaby wrote:
> > 
> >>>> It seems to suffice... No hangs still. Should I enable pm_async back
> >>>> again to confirm the issue is still present?
> >>>
> >>> Yes, please, it would be good to know for sure.
> >>
> >> Ok, confirmed right now :).
> >>
> >> I disabled pm_async for USB again. What do you suggest next?
> > 
> > What happens if you leave pm_async enabled but unplug all the USB 
> > devices before suspending?
> 
> Then I cannot suspend at all (ENOINPUTDEVICE)... And this would be
> painful as the bug occurs once a week or so.

You can suspend using a remote network login.  Agreed, this would be 
painful.

> > If there are any USB devices you can't 
> > unplug, you can get an equivalent result by unconfiguring the root 
> > hubs:
> > 
> > 	for a in /sys/bus/usb/devices/usb* ; do
> > 		echo 0 >$a/bConfigurationValue
> > 	done
> 
> Well, I can put this into suspend/resume scripts. What's the opposite
> operation? 1 > $a/bConfigurationValue?

Yes.

Alan Stern

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-04 19:33                         ` [linux-pm] " Alan Stern
                                             ` (2 preceding siblings ...)
  2011-02-22  8:45                           ` Jiri Slaby
@ 2011-02-22  8:45                           ` Jiri Slaby
  2011-02-22 15:36                             ` Alan Stern
  2011-02-22 15:36                             ` Alan Stern
  3 siblings, 2 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-02-22  8:45 UTC (permalink / raw)
  To: Alan Stern; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On 02/04/2011 08:33 PM, Alan Stern wrote:
> On Fri, 4 Feb 2011, Jiri Slaby wrote:
> 
>>>> It seems to suffice... No hangs still. Should I enable pm_async back
>>>> again to confirm the issue is still present?
>>>
>>> Yes, please, it would be good to know for sure.
>>
>> Ok, confirmed right now :).
>>
>> I disabled pm_async for USB again. What do you suggest next?
> 
> What happens if you leave pm_async enabled but unplug all the USB 
> devices before suspending?  If there are any USB devices you can't 
> unplug, you can get an equivalent result by unconfiguring the root 
> hubs:
> 
> 	for a in /sys/bus/usb/devices/usb* ; do
> 		echo 0 >$a/bConfigurationValue
> 	done

This doesn't seem to help. The hang happened 3 times during the 2 weeks.

I have /etc/pm/sleep.d/99usb-debug with:
#!/bin/bash

send() {
        for a in /sys/bus/usb/devices/usb* ; do
                echo $1 >$a/bConfigurationValue
        done
}

case "$1" in
        hibernate|suspend)
                        send 0
                ;;
        thaw|resume)
                        send 1
                ;;
        *)
                ;;
esac

exit 0

And it indeed properly enable/disable usb before/after suspend.

regards,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-04 19:33                         ` [linux-pm] " Alan Stern
  2011-02-04 19:38                           ` Jiri Slaby
  2011-02-04 19:38                           ` [linux-pm] " Jiri Slaby
@ 2011-02-22  8:45                           ` Jiri Slaby
  2011-02-22  8:45                           ` [linux-pm] " Jiri Slaby
  3 siblings, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-02-22  8:45 UTC (permalink / raw)
  To: Alan Stern; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On 02/04/2011 08:33 PM, Alan Stern wrote:
> On Fri, 4 Feb 2011, Jiri Slaby wrote:
> 
>>>> It seems to suffice... No hangs still. Should I enable pm_async back
>>>> again to confirm the issue is still present?
>>>
>>> Yes, please, it would be good to know for sure.
>>
>> Ok, confirmed right now :).
>>
>> I disabled pm_async for USB again. What do you suggest next?
> 
> What happens if you leave pm_async enabled but unplug all the USB 
> devices before suspending?  If there are any USB devices you can't 
> unplug, you can get an equivalent result by unconfiguring the root 
> hubs:
> 
> 	for a in /sys/bus/usb/devices/usb* ; do
> 		echo 0 >$a/bConfigurationValue
> 	done

This doesn't seem to help. The hang happened 3 times during the 2 weeks.

I have /etc/pm/sleep.d/99usb-debug with:
#!/bin/bash

send() {
        for a in /sys/bus/usb/devices/usb* ; do
                echo $1 >$a/bConfigurationValue
        done
}

case "$1" in
        hibernate|suspend)
                        send 0
                ;;
        thaw|resume)
                        send 1
                ;;
        *)
                ;;
esac

exit 0

And it indeed properly enable/disable usb before/after suspend.

regards,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-22  8:45                           ` [linux-pm] " Jiri Slaby
@ 2011-02-22 15:36                             ` Alan Stern
  2011-02-23 11:58                               ` Jiri Slaby
                                                 ` (7 more replies)
  2011-02-22 15:36                             ` Alan Stern
  1 sibling, 8 replies; 77+ messages in thread
From: Alan Stern @ 2011-02-22 15:36 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On Tue, 22 Feb 2011, Jiri Slaby wrote:

> On 02/04/2011 08:33 PM, Alan Stern wrote:
> > On Fri, 4 Feb 2011, Jiri Slaby wrote:
> > 
> >>>> It seems to suffice... No hangs still. Should I enable pm_async back
> >>>> again to confirm the issue is still present?
> >>>
> >>> Yes, please, it would be good to know for sure.
> >>
> >> Ok, confirmed right now :).
> >>
> >> I disabled pm_async for USB again. What do you suggest next?
> > 
> > What happens if you leave pm_async enabled but unplug all the USB 
> > devices before suspending?  If there are any USB devices you can't 
> > unplug, you can get an equivalent result by unconfiguring the root 
> > hubs:
> > 
> > 	for a in /sys/bus/usb/devices/usb* ; do
> > 		echo 0 >$a/bConfigurationValue
> > 	done
> 
> This doesn't seem to help. The hang happened 3 times during the 2 weeks.
> 
> I have /etc/pm/sleep.d/99usb-debug with:
> #!/bin/bash
> 
> send() {
>         for a in /sys/bus/usb/devices/usb* ; do
>                 echo $1 >$a/bConfigurationValue
>         done
> }
> 
> case "$1" in
>         hibernate|suspend)
>                         send 0
>                 ;;
>         thaw|resume)
>                         send 1
>                 ;;
>         *)
>                 ;;
> esac
> 
> exit 0
> 
> And it indeed properly enable/disable usb before/after suspend.

Strange indeed.  It's worth noting that the async stuff affects only
the normal suspend and resume operations, not the late-suspend and
early-resume operations.  This means that it all likelihood, the system
crashes either before finishing the suspend or after doing a fair
amount of the resume.  And yet that's not consistent with what you see
on the screen.

By the way, are you booting with no_console_suspend?  And do you do 
"echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
suspending?

What about if you leave async enabled for all the USB devices _except_ 
usb[1-N]?

Alan Stern


^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-22  8:45                           ` [linux-pm] " Jiri Slaby
  2011-02-22 15:36                             ` Alan Stern
@ 2011-02-22 15:36                             ` Alan Stern
  1 sibling, 0 replies; 77+ messages in thread
From: Alan Stern @ 2011-02-22 15:36 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On Tue, 22 Feb 2011, Jiri Slaby wrote:

> On 02/04/2011 08:33 PM, Alan Stern wrote:
> > On Fri, 4 Feb 2011, Jiri Slaby wrote:
> > 
> >>>> It seems to suffice... No hangs still. Should I enable pm_async back
> >>>> again to confirm the issue is still present?
> >>>
> >>> Yes, please, it would be good to know for sure.
> >>
> >> Ok, confirmed right now :).
> >>
> >> I disabled pm_async for USB again. What do you suggest next?
> > 
> > What happens if you leave pm_async enabled but unplug all the USB 
> > devices before suspending?  If there are any USB devices you can't 
> > unplug, you can get an equivalent result by unconfiguring the root 
> > hubs:
> > 
> > 	for a in /sys/bus/usb/devices/usb* ; do
> > 		echo 0 >$a/bConfigurationValue
> > 	done
> 
> This doesn't seem to help. The hang happened 3 times during the 2 weeks.
> 
> I have /etc/pm/sleep.d/99usb-debug with:
> #!/bin/bash
> 
> send() {
>         for a in /sys/bus/usb/devices/usb* ; do
>                 echo $1 >$a/bConfigurationValue
>         done
> }
> 
> case "$1" in
>         hibernate|suspend)
>                         send 0
>                 ;;
>         thaw|resume)
>                         send 1
>                 ;;
>         *)
>                 ;;
> esac
> 
> exit 0
> 
> And it indeed properly enable/disable usb before/after suspend.

Strange indeed.  It's worth noting that the async stuff affects only
the normal suspend and resume operations, not the late-suspend and
early-resume operations.  This means that it all likelihood, the system
crashes either before finishing the suspend or after doing a fair
amount of the resume.  And yet that's not consistent with what you see
on the screen.

By the way, are you booting with no_console_suspend?  And do you do 
"echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
suspending?

What about if you leave async enabled for all the USB devices _except_ 
usb[1-N]?

Alan Stern

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-22 15:36                             ` Alan Stern
  2011-02-23 11:58                               ` Jiri Slaby
@ 2011-02-23 11:58                               ` Jiri Slaby
  2011-02-23 15:59                                 ` Alan Stern
  2011-02-23 15:59                                 ` Alan Stern
  2011-02-24 18:41                               ` [linux-pm] " Jiri Slaby
                                                 ` (5 subsequent siblings)
  7 siblings, 2 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-02-23 11:58 UTC (permalink / raw)
  To: Alan Stern; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On 02/22/2011 04:36 PM, Alan Stern wrote:
> By the way, are you booting with no_console_suspend?  And do you do 
> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> suspending?

Nope.

> What about if you leave async enabled for all the USB devices _except_ 
> usb[1-N]?

Ok, so now I have:
/sys/bus/usb/devices/usb1/power/async:disabled
/sys/bus/usb/devices/usb2/power/async:disabled
/sys/bus/usb/devices/usb3/power/async:disabled
/sys/bus/usb/devices/usb4/power/async:disabled
/sys/bus/usb/devices/usb5/power/async:disabled
/sys/bus/usb/devices/usb6/power/async:disabled
/sys/bus/usb/devices/usb7/power/async:disabled
/sys/bus/usb/devices/usb8/power/async:disabled
/sys/bus/usb/devices/1-0:1.0/power/async:enabled
/sys/bus/usb/devices/2-0:1.0/power/async:enabled
/sys/bus/usb/devices/2-6/power/async:enabled
/sys/bus/usb/devices/2-6:1.0/power/async:enabled
/sys/bus/usb/devices/2-6:1.1/power/async:enabled
/sys/bus/usb/devices/3-0:1.0/power/async:enabled
/sys/bus/usb/devices/4-0:1.0/power/async:enabled
/sys/bus/usb/devices/4-2/power/async:enabled
/sys/bus/usb/devices/4-2.1/power/async:enabled
/sys/bus/usb/devices/4-2:1.0/power/async:enabled
/sys/bus/usb/devices/4-2.1:1.0/power/async:enabled
/sys/bus/usb/devices/4-2.1:1.1/power/async:enabled
/sys/bus/usb/devices/4-2.2/power/async:enabled
/sys/bus/usb/devices/4-2.2:1.0/power/async:enabled
/sys/bus/usb/devices/5-0:1.0/power/async:enabled
/sys/bus/usb/devices/6-0:1.0/power/async:enabled
/sys/bus/usb/devices/7-0:1.0/power/async:enabled
/sys/bus/usb/devices/8-0:1.0/power/async:enabled

Let's see.

regards,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-22 15:36                             ` Alan Stern
@ 2011-02-23 11:58                               ` Jiri Slaby
  2011-02-23 11:58                               ` [linux-pm] " Jiri Slaby
                                                 ` (6 subsequent siblings)
  7 siblings, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-02-23 11:58 UTC (permalink / raw)
  To: Alan Stern; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On 02/22/2011 04:36 PM, Alan Stern wrote:
> By the way, are you booting with no_console_suspend?  And do you do 
> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> suspending?

Nope.

> What about if you leave async enabled for all the USB devices _except_ 
> usb[1-N]?

Ok, so now I have:
/sys/bus/usb/devices/usb1/power/async:disabled
/sys/bus/usb/devices/usb2/power/async:disabled
/sys/bus/usb/devices/usb3/power/async:disabled
/sys/bus/usb/devices/usb4/power/async:disabled
/sys/bus/usb/devices/usb5/power/async:disabled
/sys/bus/usb/devices/usb6/power/async:disabled
/sys/bus/usb/devices/usb7/power/async:disabled
/sys/bus/usb/devices/usb8/power/async:disabled
/sys/bus/usb/devices/1-0:1.0/power/async:enabled
/sys/bus/usb/devices/2-0:1.0/power/async:enabled
/sys/bus/usb/devices/2-6/power/async:enabled
/sys/bus/usb/devices/2-6:1.0/power/async:enabled
/sys/bus/usb/devices/2-6:1.1/power/async:enabled
/sys/bus/usb/devices/3-0:1.0/power/async:enabled
/sys/bus/usb/devices/4-0:1.0/power/async:enabled
/sys/bus/usb/devices/4-2/power/async:enabled
/sys/bus/usb/devices/4-2.1/power/async:enabled
/sys/bus/usb/devices/4-2:1.0/power/async:enabled
/sys/bus/usb/devices/4-2.1:1.0/power/async:enabled
/sys/bus/usb/devices/4-2.1:1.1/power/async:enabled
/sys/bus/usb/devices/4-2.2/power/async:enabled
/sys/bus/usb/devices/4-2.2:1.0/power/async:enabled
/sys/bus/usb/devices/5-0:1.0/power/async:enabled
/sys/bus/usb/devices/6-0:1.0/power/async:enabled
/sys/bus/usb/devices/7-0:1.0/power/async:enabled
/sys/bus/usb/devices/8-0:1.0/power/async:enabled

Let's see.

regards,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-23 11:58                               ` [linux-pm] " Jiri Slaby
@ 2011-02-23 15:59                                 ` Alan Stern
  2011-02-23 15:59                                 ` Alan Stern
  1 sibling, 0 replies; 77+ messages in thread
From: Alan Stern @ 2011-02-23 15:59 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On Wed, 23 Feb 2011, Jiri Slaby wrote:

> On 02/22/2011 04:36 PM, Alan Stern wrote:
> > By the way, are you booting with no_console_suspend?  And do you do 
> > "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> > suspending?
> 
> Nope.

If you do, it's possible you might get some useful information on the 
screen the next time one of these hangs occurs.

Alan Stern


^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-23 11:58                               ` [linux-pm] " Jiri Slaby
  2011-02-23 15:59                                 ` Alan Stern
@ 2011-02-23 15:59                                 ` Alan Stern
  1 sibling, 0 replies; 77+ messages in thread
From: Alan Stern @ 2011-02-23 15:59 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On Wed, 23 Feb 2011, Jiri Slaby wrote:

> On 02/22/2011 04:36 PM, Alan Stern wrote:
> > By the way, are you booting with no_console_suspend?  And do you do 
> > "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> > suspending?
> 
> Nope.

If you do, it's possible you might get some useful information on the 
screen the next time one of these hangs occurs.

Alan Stern

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-22 15:36                             ` Alan Stern
  2011-02-23 11:58                               ` Jiri Slaby
  2011-02-23 11:58                               ` [linux-pm] " Jiri Slaby
@ 2011-02-24 18:41                               ` Jiri Slaby
  2011-02-24 18:41                               ` Jiri Slaby
                                                 ` (4 subsequent siblings)
  7 siblings, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-02-24 18:41 UTC (permalink / raw)
  To: Alan Stern; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On 02/22/2011 04:36 PM, Alan Stern wrote:
> By the way, are you booting with no_console_suspend?  And do you do 
> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> suspending?
> 
> What about if you leave async enabled for all the USB devices _except_ 
> usb[1-N]?

It died right now.

So I booted with no_console_suspend.

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-22 15:36                             ` Alan Stern
                                                 ` (2 preceding siblings ...)
  2011-02-24 18:41                               ` [linux-pm] " Jiri Slaby
@ 2011-02-24 18:41                               ` Jiri Slaby
  2011-03-08  9:13                               ` Jiri Slaby
                                                 ` (3 subsequent siblings)
  7 siblings, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-02-24 18:41 UTC (permalink / raw)
  To: Alan Stern; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On 02/22/2011 04:36 PM, Alan Stern wrote:
> By the way, are you booting with no_console_suspend?  And do you do 
> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> suspending?
> 
> What about if you leave async enabled for all the USB devices _except_ 
> usb[1-N]?

It died right now.

So I booted with no_console_suspend.

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-22 15:36                             ` Alan Stern
                                                 ` (4 preceding siblings ...)
  2011-03-08  9:13                               ` Jiri Slaby
@ 2011-03-08  9:13                               ` Jiri Slaby
  2011-03-08 19:25                                 ` Rafael J. Wysocki
  2011-03-08 19:25                                 ` Rafael J. Wysocki
  2011-03-30 14:11                               ` [linux-pm] " Jiri Slaby
  2011-03-30 14:11                               ` Jiri Slaby
  7 siblings, 2 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-03-08  9:13 UTC (permalink / raw)
  To: Alan Stern; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On 02/22/2011 04:36 PM, Alan Stern wrote:
> By the way, are you booting with no_console_suspend?  And do you do 
> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> suspending?

Unfortunately there are no messages at all.

Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
switch a console in such case? And if yes, to which one?

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-22 15:36                             ` Alan Stern
                                                 ` (3 preceding siblings ...)
  2011-02-24 18:41                               ` Jiri Slaby
@ 2011-03-08  9:13                               ` Jiri Slaby
  2011-03-08  9:13                               ` [linux-pm] " Jiri Slaby
                                                 ` (2 subsequent siblings)
  7 siblings, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-03-08  9:13 UTC (permalink / raw)
  To: Alan Stern; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On 02/22/2011 04:36 PM, Alan Stern wrote:
> By the way, are you booting with no_console_suspend?  And do you do 
> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> suspending?

Unfortunately there are no messages at all.

Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
switch a console in such case? And if yes, to which one?

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-08  9:13                               ` [linux-pm] " Jiri Slaby
@ 2011-03-08 19:25                                 ` Rafael J. Wysocki
  2011-03-08 20:31                                   ` Jiri Slaby
  2011-03-08 20:31                                   ` Jiri Slaby
  2011-03-08 19:25                                 ` Rafael J. Wysocki
  1 sibling, 2 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2011-03-08 19:25 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Alan Stern, akpm, linux-kernel, Linux-pm mailing list

On Tuesday, March 08, 2011, Jiri Slaby wrote:
> On 02/22/2011 04:36 PM, Alan Stern wrote:
> > By the way, are you booting with no_console_suspend?  And do you do 
> > "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> > suspending?
> 
> Unfortunately there are no messages at all.
> 
> Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
> switch a console in such case? And if yes, to which one?

pm-utils don't, but s2ram does, I'm not sure from the top of my head to
which one, though.

If you use a KMS driver (I get you do), please just "chmod a-x /usr/sbin/s2ram".

Thanks,
Rafael

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-08  9:13                               ` [linux-pm] " Jiri Slaby
  2011-03-08 19:25                                 ` Rafael J. Wysocki
@ 2011-03-08 19:25                                 ` Rafael J. Wysocki
  1 sibling, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2011-03-08 19:25 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: akpm, linux-kernel, Linux-pm mailing list

On Tuesday, March 08, 2011, Jiri Slaby wrote:
> On 02/22/2011 04:36 PM, Alan Stern wrote:
> > By the way, are you booting with no_console_suspend?  And do you do 
> > "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> > suspending?
> 
> Unfortunately there are no messages at all.
> 
> Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
> switch a console in such case? And if yes, to which one?

pm-utils don't, but s2ram does, I'm not sure from the top of my head to
which one, though.

If you use a KMS driver (I get you do), please just "chmod a-x /usr/sbin/s2ram".

Thanks,
Rafael

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-08 19:25                                 ` Rafael J. Wysocki
@ 2011-03-08 20:31                                   ` Jiri Slaby
  2011-03-08 22:12                                     ` Rafael J. Wysocki
  2011-03-08 22:12                                     ` [linux-pm] " Rafael J. Wysocki
  2011-03-08 20:31                                   ` Jiri Slaby
  1 sibling, 2 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-03-08 20:31 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: Alan Stern, akpm, linux-kernel, Linux-pm mailing list

On 03/08/2011 08:25 PM, Rafael J. Wysocki wrote:
> On Tuesday, March 08, 2011, Jiri Slaby wrote:
>> On 02/22/2011 04:36 PM, Alan Stern wrote:
>>> By the way, are you booting with no_console_suspend?  And do you do 
>>> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
>>> suspending?
>>
>> Unfortunately there are no messages at all.
>>
>> Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
>> switch a console in such case? And if yes, to which one?
> 
> pm-utils don't, but s2ram does, I'm not sure from the top of my head to
> which one, though.
> 
> If you use a KMS driver (I get you do), please just "chmod a-x /usr/sbin/s2ram".

Yeah, I meant kernel modesetting, of course. Sorry for the confusion.

I don't have /usr/sbin/s2ram. So I commented the --quirk-no-chvt thing
in a pm-utils script.

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-08 19:25                                 ` Rafael J. Wysocki
  2011-03-08 20:31                                   ` Jiri Slaby
@ 2011-03-08 20:31                                   ` Jiri Slaby
  1 sibling, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-03-08 20:31 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 03/08/2011 08:25 PM, Rafael J. Wysocki wrote:
> On Tuesday, March 08, 2011, Jiri Slaby wrote:
>> On 02/22/2011 04:36 PM, Alan Stern wrote:
>>> By the way, are you booting with no_console_suspend?  And do you do 
>>> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
>>> suspending?
>>
>> Unfortunately there are no messages at all.
>>
>> Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
>> switch a console in such case? And if yes, to which one?
> 
> pm-utils don't, but s2ram does, I'm not sure from the top of my head to
> which one, though.
> 
> If you use a KMS driver (I get you do), please just "chmod a-x /usr/sbin/s2ram".

Yeah, I meant kernel modesetting, of course. Sorry for the confusion.

I don't have /usr/sbin/s2ram. So I commented the --quirk-no-chvt thing
in a pm-utils script.

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-08 20:31                                   ` Jiri Slaby
  2011-03-08 22:12                                     ` Rafael J. Wysocki
@ 2011-03-08 22:12                                     ` Rafael J. Wysocki
  2011-03-08 22:14                                       ` Jiri Slaby
  2011-03-08 22:14                                       ` Jiri Slaby
  1 sibling, 2 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2011-03-08 22:12 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Alan Stern, akpm, linux-kernel, Linux-pm mailing list

On Tuesday, March 08, 2011, Jiri Slaby wrote:
> On 03/08/2011 08:25 PM, Rafael J. Wysocki wrote:
> > On Tuesday, March 08, 2011, Jiri Slaby wrote:
> >> On 02/22/2011 04:36 PM, Alan Stern wrote:
> >>> By the way, are you booting with no_console_suspend?  And do you do 
> >>> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> >>> suspending?
> >>
> >> Unfortunately there are no messages at all.
> >>
> >> Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
> >> switch a console in such case? And if yes, to which one?
> > 
> > pm-utils don't, but s2ram does, I'm not sure from the top of my head to
> > which one, though.
> > 
> > If you use a KMS driver (I get you do), please just "chmod a-x /usr/sbin/s2ram".
> 
> Yeah, I meant kernel modesetting, of course. Sorry for the confusion.
> 
> I don't have /usr/sbin/s2ram.

Ah.  So it's gone from Factory?  Interesting.

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-08 20:31                                   ` Jiri Slaby
@ 2011-03-08 22:12                                     ` Rafael J. Wysocki
  2011-03-08 22:12                                     ` [linux-pm] " Rafael J. Wysocki
  1 sibling, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2011-03-08 22:12 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: akpm, linux-kernel, Linux-pm mailing list

On Tuesday, March 08, 2011, Jiri Slaby wrote:
> On 03/08/2011 08:25 PM, Rafael J. Wysocki wrote:
> > On Tuesday, March 08, 2011, Jiri Slaby wrote:
> >> On 02/22/2011 04:36 PM, Alan Stern wrote:
> >>> By the way, are you booting with no_console_suspend?  And do you do 
> >>> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> >>> suspending?
> >>
> >> Unfortunately there are no messages at all.
> >>
> >> Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
> >> switch a console in such case? And if yes, to which one?
> > 
> > pm-utils don't, but s2ram does, I'm not sure from the top of my head to
> > which one, though.
> > 
> > If you use a KMS driver (I get you do), please just "chmod a-x /usr/sbin/s2ram".
> 
> Yeah, I meant kernel modesetting, of course. Sorry for the confusion.
> 
> I don't have /usr/sbin/s2ram.

Ah.  So it's gone from Factory?  Interesting.

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-08 22:12                                     ` [linux-pm] " Rafael J. Wysocki
@ 2011-03-08 22:14                                       ` Jiri Slaby
  2011-03-08 22:15                                         ` Rafael J. Wysocki
                                                           ` (3 more replies)
  2011-03-08 22:14                                       ` Jiri Slaby
  1 sibling, 4 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-03-08 22:14 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: Alan Stern, akpm, linux-kernel, Linux-pm mailing list

On 03/08/2011 11:12 PM, Rafael J. Wysocki wrote:
> On Tuesday, March 08, 2011, Jiri Slaby wrote:
>> On 03/08/2011 08:25 PM, Rafael J. Wysocki wrote:
>>> On Tuesday, March 08, 2011, Jiri Slaby wrote:
>>>> On 02/22/2011 04:36 PM, Alan Stern wrote:
>>>>> By the way, are you booting with no_console_suspend?  And do you do 
>>>>> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
>>>>> suspending?
>>>>
>>>> Unfortunately there are no messages at all.
>>>>
>>>> Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
>>>> switch a console in such case? And if yes, to which one?
>>>
>>> pm-utils don't, but s2ram does, I'm not sure from the top of my head to
>>> which one, though.
>>>
>>> If you use a KMS driver (I get you do), please just "chmod a-x /usr/sbin/s2ram".
>>
>> Yeah, I meant kernel modesetting, of course. Sorry for the confusion.
>>
>> I don't have /usr/sbin/s2ram.
> 
> Ah.  So it's gone from Factory?  Interesting.

I don't know, maybe it's in suspend package which I don't have installed.

-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-08 22:12                                     ` [linux-pm] " Rafael J. Wysocki
  2011-03-08 22:14                                       ` Jiri Slaby
@ 2011-03-08 22:14                                       ` Jiri Slaby
  1 sibling, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-03-08 22:14 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 03/08/2011 11:12 PM, Rafael J. Wysocki wrote:
> On Tuesday, March 08, 2011, Jiri Slaby wrote:
>> On 03/08/2011 08:25 PM, Rafael J. Wysocki wrote:
>>> On Tuesday, March 08, 2011, Jiri Slaby wrote:
>>>> On 02/22/2011 04:36 PM, Alan Stern wrote:
>>>>> By the way, are you booting with no_console_suspend?  And do you do 
>>>>> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
>>>>> suspending?
>>>>
>>>> Unfortunately there are no messages at all.
>>>>
>>>> Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
>>>> switch a console in such case? And if yes, to which one?
>>>
>>> pm-utils don't, but s2ram does, I'm not sure from the top of my head to
>>> which one, though.
>>>
>>> If you use a KMS driver (I get you do), please just "chmod a-x /usr/sbin/s2ram".
>>
>> Yeah, I meant kernel modesetting, of course. Sorry for the confusion.
>>
>> I don't have /usr/sbin/s2ram.
> 
> Ah.  So it's gone from Factory?  Interesting.

I don't know, maybe it's in suspend package which I don't have installed.

-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-08 22:14                                       ` Jiri Slaby
  2011-03-08 22:15                                         ` Rafael J. Wysocki
@ 2011-03-08 22:15                                         ` Rafael J. Wysocki
  2011-03-08 22:16                                         ` Rafael J. Wysocki
  2011-03-08 22:16                                         ` Rafael J. Wysocki
  3 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2011-03-08 22:15 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Alan Stern, akpm, linux-kernel, Linux-pm mailing list

On Tuesday, March 08, 2011, Jiri Slaby wrote:
> On 03/08/2011 11:12 PM, Rafael J. Wysocki wrote:
> > On Tuesday, March 08, 2011, Jiri Slaby wrote:
> >> On 03/08/2011 08:25 PM, Rafael J. Wysocki wrote:
> >>> On Tuesday, March 08, 2011, Jiri Slaby wrote:
> >>>> On 02/22/2011 04:36 PM, Alan Stern wrote:
> >>>>> By the way, are you booting with no_console_suspend?  And do you do 
> >>>>> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> >>>>> suspending?
> >>>>
> >>>> Unfortunately there are no messages at all.
> >>>>
> >>>> Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
> >>>> switch a console in such case? And if yes, to which one?
> >>>
> >>> pm-utils don't, but s2ram does, I'm not sure from the top of my head to
> >>> which one, though.
> >>>
> >>> If you use a KMS driver (I get you do), please just "chmod a-x /usr/sbin/s2ram".
> >>
> >> Yeah, I meant kernel modesetting, of course. Sorry for the confusion.
> >>
> >> I don't have /usr/sbin/s2ram.
> > 
> > Ah.  So it's gone from Factory?  Interesting.
> 
> I don't know, maybe it's in suspend package which I don't have installed.

It's there, yes.

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-08 22:14                                       ` Jiri Slaby
@ 2011-03-08 22:15                                         ` Rafael J. Wysocki
  2011-03-08 22:15                                         ` [linux-pm] " Rafael J. Wysocki
                                                           ` (2 subsequent siblings)
  3 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2011-03-08 22:15 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: akpm, linux-kernel, Linux-pm mailing list

On Tuesday, March 08, 2011, Jiri Slaby wrote:
> On 03/08/2011 11:12 PM, Rafael J. Wysocki wrote:
> > On Tuesday, March 08, 2011, Jiri Slaby wrote:
> >> On 03/08/2011 08:25 PM, Rafael J. Wysocki wrote:
> >>> On Tuesday, March 08, 2011, Jiri Slaby wrote:
> >>>> On 02/22/2011 04:36 PM, Alan Stern wrote:
> >>>>> By the way, are you booting with no_console_suspend?  And do you do 
> >>>>> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> >>>>> suspending?
> >>>>
> >>>> Unfortunately there are no messages at all.
> >>>>
> >>>> Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
> >>>> switch a console in such case? And if yes, to which one?
> >>>
> >>> pm-utils don't, but s2ram does, I'm not sure from the top of my head to
> >>> which one, though.
> >>>
> >>> If you use a KMS driver (I get you do), please just "chmod a-x /usr/sbin/s2ram".
> >>
> >> Yeah, I meant kernel modesetting, of course. Sorry for the confusion.
> >>
> >> I don't have /usr/sbin/s2ram.
> > 
> > Ah.  So it's gone from Factory?  Interesting.
> 
> I don't know, maybe it's in suspend package which I don't have installed.

It's there, yes.

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-08 22:14                                       ` Jiri Slaby
  2011-03-08 22:15                                         ` Rafael J. Wysocki
  2011-03-08 22:15                                         ` [linux-pm] " Rafael J. Wysocki
@ 2011-03-08 22:16                                         ` Rafael J. Wysocki
  2011-03-08 22:18                                           ` Jiri Slaby
  2011-03-08 22:18                                           ` Jiri Slaby
  2011-03-08 22:16                                         ` Rafael J. Wysocki
  3 siblings, 2 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2011-03-08 22:16 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Alan Stern, akpm, linux-kernel, Linux-pm mailing list

On Tuesday, March 08, 2011, Jiri Slaby wrote:
> On 03/08/2011 11:12 PM, Rafael J. Wysocki wrote:
> > On Tuesday, March 08, 2011, Jiri Slaby wrote:
> >> On 03/08/2011 08:25 PM, Rafael J. Wysocki wrote:
> >>> On Tuesday, March 08, 2011, Jiri Slaby wrote:
> >>>> On 02/22/2011 04:36 PM, Alan Stern wrote:
> >>>>> By the way, are you booting with no_console_suspend?  And do you do 
> >>>>> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> >>>>> suspending?
> >>>>
> >>>> Unfortunately there are no messages at all.
> >>>>
> >>>> Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
> >>>> switch a console in such case? And if yes, to which one?
> >>>
> >>> pm-utils don't, but s2ram does, I'm not sure from the top of my head to
> >>> which one, though.
> >>>
> >>> If you use a KMS driver (I get you do), please just "chmod a-x /usr/sbin/s2ram".
> >>
> >> Yeah, I meant kernel modesetting, of course. Sorry for the confusion.
> >>
> >> I don't have /usr/sbin/s2ram.
> > 
> > Ah.  So it's gone from Factory?  Interesting.
> 
> I don't know, maybe it's in suspend package which I don't have installed.

Hm.  So you use the in-kernel hibernate code?

The one in the suspend package is generally faster.

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-08 22:14                                       ` Jiri Slaby
                                                           ` (2 preceding siblings ...)
  2011-03-08 22:16                                         ` Rafael J. Wysocki
@ 2011-03-08 22:16                                         ` Rafael J. Wysocki
  3 siblings, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2011-03-08 22:16 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: akpm, linux-kernel, Linux-pm mailing list

On Tuesday, March 08, 2011, Jiri Slaby wrote:
> On 03/08/2011 11:12 PM, Rafael J. Wysocki wrote:
> > On Tuesday, March 08, 2011, Jiri Slaby wrote:
> >> On 03/08/2011 08:25 PM, Rafael J. Wysocki wrote:
> >>> On Tuesday, March 08, 2011, Jiri Slaby wrote:
> >>>> On 02/22/2011 04:36 PM, Alan Stern wrote:
> >>>>> By the way, are you booting with no_console_suspend?  And do you do 
> >>>>> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> >>>>> suspending?
> >>>>
> >>>> Unfortunately there are no messages at all.
> >>>>
> >>>> Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
> >>>> switch a console in such case? And if yes, to which one?
> >>>
> >>> pm-utils don't, but s2ram does, I'm not sure from the top of my head to
> >>> which one, though.
> >>>
> >>> If you use a KMS driver (I get you do), please just "chmod a-x /usr/sbin/s2ram".
> >>
> >> Yeah, I meant kernel modesetting, of course. Sorry for the confusion.
> >>
> >> I don't have /usr/sbin/s2ram.
> > 
> > Ah.  So it's gone from Factory?  Interesting.
> 
> I don't know, maybe it's in suspend package which I don't have installed.

Hm.  So you use the in-kernel hibernate code?

The one in the suspend package is generally faster.

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-08 22:16                                         ` Rafael J. Wysocki
@ 2011-03-08 22:18                                           ` Jiri Slaby
  2011-03-08 22:18                                           ` Jiri Slaby
  1 sibling, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-03-08 22:18 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: Alan Stern, akpm, linux-kernel, Linux-pm mailing list

On 03/08/2011 11:16 PM, Rafael J. Wysocki wrote:
> On Tuesday, March 08, 2011, Jiri Slaby wrote:
>> On 03/08/2011 11:12 PM, Rafael J. Wysocki wrote:
>>> On Tuesday, March 08, 2011, Jiri Slaby wrote:
>>>> On 03/08/2011 08:25 PM, Rafael J. Wysocki wrote:
>>>>> On Tuesday, March 08, 2011, Jiri Slaby wrote:
>>>>>> On 02/22/2011 04:36 PM, Alan Stern wrote:
>>>>>>> By the way, are you booting with no_console_suspend?  And do you do 
>>>>>>> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
>>>>>>> suspending?
>>>>>>
>>>>>> Unfortunately there are no messages at all.
>>>>>>
>>>>>> Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
>>>>>> switch a console in such case? And if yes, to which one?
>>>>>
>>>>> pm-utils don't, but s2ram does, I'm not sure from the top of my head to
>>>>> which one, though.
>>>>>
>>>>> If you use a KMS driver (I get you do), please just "chmod a-x /usr/sbin/s2ram".
>>>>
>>>> Yeah, I meant kernel modesetting, of course. Sorry for the confusion.
>>>>
>>>> I don't have /usr/sbin/s2ram.
>>>
>>> Ah.  So it's gone from Factory?  Interesting.
>>
>> I don't know, maybe it's in suspend package which I don't have installed.
> 
> Hm.  So you use the in-kernel hibernate code?
> 
> The one in the suspend package is generally faster.

I don't use hibernation at all. This is a desktop -- suspending to S3.

-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-08 22:16                                         ` Rafael J. Wysocki
  2011-03-08 22:18                                           ` Jiri Slaby
@ 2011-03-08 22:18                                           ` Jiri Slaby
  1 sibling, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-03-08 22:18 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, linux-kernel, Linux-pm mailing list

On 03/08/2011 11:16 PM, Rafael J. Wysocki wrote:
> On Tuesday, March 08, 2011, Jiri Slaby wrote:
>> On 03/08/2011 11:12 PM, Rafael J. Wysocki wrote:
>>> On Tuesday, March 08, 2011, Jiri Slaby wrote:
>>>> On 03/08/2011 08:25 PM, Rafael J. Wysocki wrote:
>>>>> On Tuesday, March 08, 2011, Jiri Slaby wrote:
>>>>>> On 02/22/2011 04:36 PM, Alan Stern wrote:
>>>>>>> By the way, are you booting with no_console_suspend?  And do you do 
>>>>>>> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
>>>>>>> suspending?
>>>>>>
>>>>>> Unfortunately there are no messages at all.
>>>>>>
>>>>>> Rafael, this is a Factory with intel gfx (modesetting). Do pm-utils
>>>>>> switch a console in such case? And if yes, to which one?
>>>>>
>>>>> pm-utils don't, but s2ram does, I'm not sure from the top of my head to
>>>>> which one, though.
>>>>>
>>>>> If you use a KMS driver (I get you do), please just "chmod a-x /usr/sbin/s2ram".
>>>>
>>>> Yeah, I meant kernel modesetting, of course. Sorry for the confusion.
>>>>
>>>> I don't have /usr/sbin/s2ram.
>>>
>>> Ah.  So it's gone from Factory?  Interesting.
>>
>> I don't know, maybe it's in suspend package which I don't have installed.
> 
> Hm.  So you use the in-kernel hibernate code?
> 
> The one in the suspend package is generally faster.

I don't use hibernation at all. This is a desktop -- suspending to S3.

-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-22 15:36                             ` Alan Stern
                                                 ` (5 preceding siblings ...)
  2011-03-08  9:13                               ` [linux-pm] " Jiri Slaby
@ 2011-03-30 14:11                               ` Jiri Slaby
  2011-03-30 15:10                                 ` Alan Stern
  2011-03-30 15:10                                 ` Alan Stern
  2011-03-30 14:11                               ` Jiri Slaby
  7 siblings, 2 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-03-30 14:11 UTC (permalink / raw)
  To: Alan Stern; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On 02/22/2011 04:36 PM, Alan Stern wrote:
> On Tue, 22 Feb 2011, Jiri Slaby wrote:
> 
>> On 02/04/2011 08:33 PM, Alan Stern wrote:
>>> On Fri, 4 Feb 2011, Jiri Slaby wrote:
>>>
>>>>>> It seems to suffice... No hangs still. Should I enable pm_async back
>>>>>> again to confirm the issue is still present?
>>>>>
>>>>> Yes, please, it would be good to know for sure.
>>>>
>>>> Ok, confirmed right now :).
>>>>
>>>> I disabled pm_async for USB again. What do you suggest next?
>>>
>>> What happens if you leave pm_async enabled but unplug all the USB 
>>> devices before suspending?  If there are any USB devices you can't 
>>> unplug, you can get an equivalent result by unconfiguring the root 
>>> hubs:
>>>
>>> 	for a in /sys/bus/usb/devices/usb* ; do
>>> 		echo 0 >$a/bConfigurationValue
>>> 	done
>>
>> This doesn't seem to help. The hang happened 3 times during the 2 weeks.
>>
>> I have /etc/pm/sleep.d/99usb-debug with:
>> #!/bin/bash
>>
>> send() {
>>         for a in /sys/bus/usb/devices/usb* ; do
>>                 echo $1 >$a/bConfigurationValue
>>         done
>> }
>>
>> case "$1" in
>>         hibernate|suspend)
>>                         send 0
>>                 ;;
>>         thaw|resume)
>>                         send 1
>>                 ;;
>>         *)
>>                 ;;
>> esac
>>
>> exit 0
>>
>> And it indeed properly enable/disable usb before/after suspend.
> 
> Strange indeed.  It's worth noting that the async stuff affects only
> the normal suspend and resume operations, not the late-suspend and
> early-resume operations.  This means that it all likelihood, the system
> crashes either before finishing the suspend or after doing a fair
> amount of the resume.  And yet that's not consistent with what you see
> on the screen.
> 
> By the way, are you booting with no_console_suspend?  And do you do 
> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> suspending?

I'm testing this on my desktop. I found out yesterday, that I had async
completely disabled. So I have no output yet.

I took my dvb-t tuner from desktop and connected it to my notebook. And
got a similar hang during resume right now. It may not be related
though. The trace is:
s2disk          D 0000000000000000     0  6125   5902 0x00000004
 ffff8800797aba78 0000000000000082 ffff8800797ab9f8 0000000000012ac0
 ffff8800797abfd8 0000000000012ac0 ffff8800797abfd8 ffff8800797abfd8
 ffff8800777fe7f0 0000000000012ac0 0000000000012ac0 ffff8800797aa000
Call Trace:
 [<ffffffff8151e2ed>] schedule_timeout+0x28d/0x310
 [<ffffffff8151d410>] wait_for_common+0xc0/0x150
 [<ffffffff8133ad22>] _request_firmware+0x132/0x270
 [<ffffffffa06df2c7>] dvb_usb_download_firmware+0x37/0xf0 [dvb_usb]
 [<ffffffffa06dfbe5>] dvb_usb_device_init+0x165/0x1b0 [dvb_usb]
 [<ffffffffa06d6c27>] af9015_usb_probe+0x87/0xa0 [dvb_usb_af9015]
 [<ffffffff8138d9d2>] usb_probe_interface+0x142/0x270
 [<ffffffff8132f3c0>] really_probe+0x70/0x220
 [<ffffffff8132f757>] driver_probe_device+0x47/0xa0
 [<ffffffff8132e19c>] bus_for_each_drv+0x5c/0x90
 [<ffffffff8132f62f>] device_attach+0x8f/0xb0
 [<ffffffff8138d5b0>] usb_rebind_intf+0x60/0xa0
 [<ffffffff8138d6c7>] do_unbind_rebind+0x77/0xb0
 [<ffffffff8138d76b>] usb_resume+0x6b/0xb0
 [<ffffffff8137f96b>] usb_dev_complete+0xb/0x10
 [<ffffffff81334d1e>] device_complete+0x8e/0xe0
 [<ffffffff81335da1>] dpm_resume_end+0xa1/0x120
 [<ffffffff8109d890>] hibernation_snapshot+0xc0/0x120
 [<ffffffff810a1cde>] snapshot_ioctl+0x3ae/0x590
 [<ffffffff81169794>] do_vfs_ioctl+0x84/0x2f0
 [<ffffffff81169a98>] sys_ioctl+0x98/0xa0
 [<ffffffff81002ed2>] system_call_fastpath+0x16/0x1b
 [<00007fe6c82f8ce7>] 0x7fe6c82f8ce7


The firmware request should time out. I think I waited for longer than
60 s before when I saw the hangs on the desktop, But do you have an idea
why it doesn't load the FW immediately?

The device is:
Bus 001 Device 010: ID 0413:6029 Leadtek Research, Inc. WinFast DTV
Dongle Gold
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0413 Leadtek Research, Inc.
  idProduct          0x6029 WinFast DTV Dongle Gold
  bcdDevice            2.00
  iManufacturer           1 Leadtek
  iProduct                2 WinFast DTV Dongle Gold
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           71
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           4
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      1 Keyboard
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.01
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      65
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval              16
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-02-22 15:36                             ` Alan Stern
                                                 ` (6 preceding siblings ...)
  2011-03-30 14:11                               ` [linux-pm] " Jiri Slaby
@ 2011-03-30 14:11                               ` Jiri Slaby
  7 siblings, 0 replies; 77+ messages in thread
From: Jiri Slaby @ 2011-03-30 14:11 UTC (permalink / raw)
  To: Alan Stern; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On 02/22/2011 04:36 PM, Alan Stern wrote:
> On Tue, 22 Feb 2011, Jiri Slaby wrote:
> 
>> On 02/04/2011 08:33 PM, Alan Stern wrote:
>>> On Fri, 4 Feb 2011, Jiri Slaby wrote:
>>>
>>>>>> It seems to suffice... No hangs still. Should I enable pm_async back
>>>>>> again to confirm the issue is still present?
>>>>>
>>>>> Yes, please, it would be good to know for sure.
>>>>
>>>> Ok, confirmed right now :).
>>>>
>>>> I disabled pm_async for USB again. What do you suggest next?
>>>
>>> What happens if you leave pm_async enabled but unplug all the USB 
>>> devices before suspending?  If there are any USB devices you can't 
>>> unplug, you can get an equivalent result by unconfiguring the root 
>>> hubs:
>>>
>>> 	for a in /sys/bus/usb/devices/usb* ; do
>>> 		echo 0 >$a/bConfigurationValue
>>> 	done
>>
>> This doesn't seem to help. The hang happened 3 times during the 2 weeks.
>>
>> I have /etc/pm/sleep.d/99usb-debug with:
>> #!/bin/bash
>>
>> send() {
>>         for a in /sys/bus/usb/devices/usb* ; do
>>                 echo $1 >$a/bConfigurationValue
>>         done
>> }
>>
>> case "$1" in
>>         hibernate|suspend)
>>                         send 0
>>                 ;;
>>         thaw|resume)
>>                         send 1
>>                 ;;
>>         *)
>>                 ;;
>> esac
>>
>> exit 0
>>
>> And it indeed properly enable/disable usb before/after suspend.
> 
> Strange indeed.  It's worth noting that the async stuff affects only
> the normal suspend and resume operations, not the late-suspend and
> early-resume operations.  This means that it all likelihood, the system
> crashes either before finishing the suspend or after doing a fair
> amount of the resume.  And yet that's not consistent with what you see
> on the screen.
> 
> By the way, are you booting with no_console_suspend?  And do you do 
> "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> suspending?

I'm testing this on my desktop. I found out yesterday, that I had async
completely disabled. So I have no output yet.

I took my dvb-t tuner from desktop and connected it to my notebook. And
got a similar hang during resume right now. It may not be related
though. The trace is:
s2disk          D 0000000000000000     0  6125   5902 0x00000004
 ffff8800797aba78 0000000000000082 ffff8800797ab9f8 0000000000012ac0
 ffff8800797abfd8 0000000000012ac0 ffff8800797abfd8 ffff8800797abfd8
 ffff8800777fe7f0 0000000000012ac0 0000000000012ac0 ffff8800797aa000
Call Trace:
 [<ffffffff8151e2ed>] schedule_timeout+0x28d/0x310
 [<ffffffff8151d410>] wait_for_common+0xc0/0x150
 [<ffffffff8133ad22>] _request_firmware+0x132/0x270
 [<ffffffffa06df2c7>] dvb_usb_download_firmware+0x37/0xf0 [dvb_usb]
 [<ffffffffa06dfbe5>] dvb_usb_device_init+0x165/0x1b0 [dvb_usb]
 [<ffffffffa06d6c27>] af9015_usb_probe+0x87/0xa0 [dvb_usb_af9015]
 [<ffffffff8138d9d2>] usb_probe_interface+0x142/0x270
 [<ffffffff8132f3c0>] really_probe+0x70/0x220
 [<ffffffff8132f757>] driver_probe_device+0x47/0xa0
 [<ffffffff8132e19c>] bus_for_each_drv+0x5c/0x90
 [<ffffffff8132f62f>] device_attach+0x8f/0xb0
 [<ffffffff8138d5b0>] usb_rebind_intf+0x60/0xa0
 [<ffffffff8138d6c7>] do_unbind_rebind+0x77/0xb0
 [<ffffffff8138d76b>] usb_resume+0x6b/0xb0
 [<ffffffff8137f96b>] usb_dev_complete+0xb/0x10
 [<ffffffff81334d1e>] device_complete+0x8e/0xe0
 [<ffffffff81335da1>] dpm_resume_end+0xa1/0x120
 [<ffffffff8109d890>] hibernation_snapshot+0xc0/0x120
 [<ffffffff810a1cde>] snapshot_ioctl+0x3ae/0x590
 [<ffffffff81169794>] do_vfs_ioctl+0x84/0x2f0
 [<ffffffff81169a98>] sys_ioctl+0x98/0xa0
 [<ffffffff81002ed2>] system_call_fastpath+0x16/0x1b
 [<00007fe6c82f8ce7>] 0x7fe6c82f8ce7


The firmware request should time out. I think I waited for longer than
60 s before when I saw the hangs on the desktop, But do you have an idea
why it doesn't load the FW immediately?

The device is:
Bus 001 Device 010: ID 0413:6029 Leadtek Research, Inc. WinFast DTV
Dongle Gold
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0413 Leadtek Research, Inc.
  idProduct          0x6029 WinFast DTV Dongle Gold
  bcdDevice            2.00
  iManufacturer           1 Leadtek
  iProduct                2 WinFast DTV Dongle Gold
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           71
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           4
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      1 Keyboard
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.01
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      65
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval              16
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

thanks,
-- 
js

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-30 14:11                               ` [linux-pm] " Jiri Slaby
@ 2011-03-30 15:10                                 ` Alan Stern
  2011-03-30 20:02                                   ` Rafael J. Wysocki
  2011-03-30 20:02                                   ` [linux-pm] " Rafael J. Wysocki
  2011-03-30 15:10                                 ` Alan Stern
  1 sibling, 2 replies; 77+ messages in thread
From: Alan Stern @ 2011-03-30 15:10 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On Wed, 30 Mar 2011, Jiri Slaby wrote:

> > Strange indeed.  It's worth noting that the async stuff affects only
> > the normal suspend and resume operations, not the late-suspend and
> > early-resume operations.  This means that it all likelihood, the system
> > crashes either before finishing the suspend or after doing a fair
> > amount of the resume.  And yet that's not consistent with what you see
> > on the screen.
> > 
> > By the way, are you booting with no_console_suspend?  And do you do 
> > "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> > suspending?
> 
> I'm testing this on my desktop. I found out yesterday, that I had async
> completely disabled. So I have no output yet.
> 
> I took my dvb-t tuner from desktop and connected it to my notebook. And
> got a similar hang during resume right now. It may not be related
> though. The trace is:
> s2disk          D 0000000000000000     0  6125   5902 0x00000004
>  ffff8800797aba78 0000000000000082 ffff8800797ab9f8 0000000000012ac0
>  ffff8800797abfd8 0000000000012ac0 ffff8800797abfd8 ffff8800797abfd8
>  ffff8800777fe7f0 0000000000012ac0 0000000000012ac0 ffff8800797aa000
> Call Trace:
>  [<ffffffff8151e2ed>] schedule_timeout+0x28d/0x310
>  [<ffffffff8151d410>] wait_for_common+0xc0/0x150
>  [<ffffffff8133ad22>] _request_firmware+0x132/0x270
>  [<ffffffffa06df2c7>] dvb_usb_download_firmware+0x37/0xf0 [dvb_usb]
>  [<ffffffffa06dfbe5>] dvb_usb_device_init+0x165/0x1b0 [dvb_usb]
>  [<ffffffffa06d6c27>] af9015_usb_probe+0x87/0xa0 [dvb_usb_af9015]
>  [<ffffffff8138d9d2>] usb_probe_interface+0x142/0x270
>  [<ffffffff8132f3c0>] really_probe+0x70/0x220
>  [<ffffffff8132f757>] driver_probe_device+0x47/0xa0
>  [<ffffffff8132e19c>] bus_for_each_drv+0x5c/0x90
>  [<ffffffff8132f62f>] device_attach+0x8f/0xb0
>  [<ffffffff8138d5b0>] usb_rebind_intf+0x60/0xa0
>  [<ffffffff8138d6c7>] do_unbind_rebind+0x77/0xb0
>  [<ffffffff8138d76b>] usb_resume+0x6b/0xb0
>  [<ffffffff8137f96b>] usb_dev_complete+0xb/0x10
>  [<ffffffff81334d1e>] device_complete+0x8e/0xe0
>  [<ffffffff81335da1>] dpm_resume_end+0xa1/0x120
>  [<ffffffff8109d890>] hibernation_snapshot+0xc0/0x120
>  [<ffffffff810a1cde>] snapshot_ioctl+0x3ae/0x590
>  [<ffffffff81169794>] do_vfs_ioctl+0x84/0x2f0
>  [<ffffffff81169a98>] sys_ioctl+0x98/0xa0
>  [<ffffffff81002ed2>] system_call_fastpath+0x16/0x1b
>  [<00007fe6c82f8ce7>] 0x7fe6c82f8ce7
> 
> 
> The firmware request should time out. I think I waited for longer than
> 60 s before when I saw the hangs on the desktop, But do you have an idea
> why it doesn't load the FW immediately?

I don't know why the request didn't time out, but this behavior should
at least be reproducible.  Your stack trace implies that the firmware
will need to be transferred every time the device resumes... but of
course this leaves open the question of why your desktop crashed only
occasionally.

Probably the firmware wasn't transferred immediately because the kernel
relies on a userspace process to find and load the firmware, but at
that point userspace was still frozen.

Rafael, this does seem to be a general problem.  Suppose a new device
gets connected while the system is suspended.  How is the driver's
probe method supposed to cope if it gets called while userspace is
still frozen but it needs to load some firmware?

Is the answer that probing should always be delayed until after tasks
are thawed?  There must be lots of subsystems which would have trouble 
doing that, although we ought to be able to implement delayed probing 
from within the driver core easily enough.

Alan Stern


^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-30 14:11                               ` [linux-pm] " Jiri Slaby
  2011-03-30 15:10                                 ` Alan Stern
@ 2011-03-30 15:10                                 ` Alan Stern
  1 sibling, 0 replies; 77+ messages in thread
From: Alan Stern @ 2011-03-30 15:10 UTC (permalink / raw)
  To: Jiri Slaby; +Cc: Rafael J. Wysocki, akpm, linux-kernel, Linux-pm mailing list

On Wed, 30 Mar 2011, Jiri Slaby wrote:

> > Strange indeed.  It's worth noting that the async stuff affects only
> > the normal suspend and resume operations, not the late-suspend and
> > early-resume operations.  This means that it all likelihood, the system
> > crashes either before finishing the suspend or after doing a fair
> > amount of the resume.  And yet that's not consistent with what you see
> > on the screen.
> > 
> > By the way, are you booting with no_console_suspend?  And do you do 
> > "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> > suspending?
> 
> I'm testing this on my desktop. I found out yesterday, that I had async
> completely disabled. So I have no output yet.
> 
> I took my dvb-t tuner from desktop and connected it to my notebook. And
> got a similar hang during resume right now. It may not be related
> though. The trace is:
> s2disk          D 0000000000000000     0  6125   5902 0x00000004
>  ffff8800797aba78 0000000000000082 ffff8800797ab9f8 0000000000012ac0
>  ffff8800797abfd8 0000000000012ac0 ffff8800797abfd8 ffff8800797abfd8
>  ffff8800777fe7f0 0000000000012ac0 0000000000012ac0 ffff8800797aa000
> Call Trace:
>  [<ffffffff8151e2ed>] schedule_timeout+0x28d/0x310
>  [<ffffffff8151d410>] wait_for_common+0xc0/0x150
>  [<ffffffff8133ad22>] _request_firmware+0x132/0x270
>  [<ffffffffa06df2c7>] dvb_usb_download_firmware+0x37/0xf0 [dvb_usb]
>  [<ffffffffa06dfbe5>] dvb_usb_device_init+0x165/0x1b0 [dvb_usb]
>  [<ffffffffa06d6c27>] af9015_usb_probe+0x87/0xa0 [dvb_usb_af9015]
>  [<ffffffff8138d9d2>] usb_probe_interface+0x142/0x270
>  [<ffffffff8132f3c0>] really_probe+0x70/0x220
>  [<ffffffff8132f757>] driver_probe_device+0x47/0xa0
>  [<ffffffff8132e19c>] bus_for_each_drv+0x5c/0x90
>  [<ffffffff8132f62f>] device_attach+0x8f/0xb0
>  [<ffffffff8138d5b0>] usb_rebind_intf+0x60/0xa0
>  [<ffffffff8138d6c7>] do_unbind_rebind+0x77/0xb0
>  [<ffffffff8138d76b>] usb_resume+0x6b/0xb0
>  [<ffffffff8137f96b>] usb_dev_complete+0xb/0x10
>  [<ffffffff81334d1e>] device_complete+0x8e/0xe0
>  [<ffffffff81335da1>] dpm_resume_end+0xa1/0x120
>  [<ffffffff8109d890>] hibernation_snapshot+0xc0/0x120
>  [<ffffffff810a1cde>] snapshot_ioctl+0x3ae/0x590
>  [<ffffffff81169794>] do_vfs_ioctl+0x84/0x2f0
>  [<ffffffff81169a98>] sys_ioctl+0x98/0xa0
>  [<ffffffff81002ed2>] system_call_fastpath+0x16/0x1b
>  [<00007fe6c82f8ce7>] 0x7fe6c82f8ce7
> 
> 
> The firmware request should time out. I think I waited for longer than
> 60 s before when I saw the hangs on the desktop, But do you have an idea
> why it doesn't load the FW immediately?

I don't know why the request didn't time out, but this behavior should
at least be reproducible.  Your stack trace implies that the firmware
will need to be transferred every time the device resumes... but of
course this leaves open the question of why your desktop crashed only
occasionally.

Probably the firmware wasn't transferred immediately because the kernel
relies on a userspace process to find and load the firmware, but at
that point userspace was still frozen.

Rafael, this does seem to be a general problem.  Suppose a new device
gets connected while the system is suspended.  How is the driver's
probe method supposed to cope if it gets called while userspace is
still frozen but it needs to load some firmware?

Is the answer that probing should always be delayed until after tasks
are thawed?  There must be lots of subsystems which would have trouble 
doing that, although we ought to be able to implement delayed probing 
from within the driver core easily enough.

Alan Stern

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-30 15:10                                 ` Alan Stern
  2011-03-30 20:02                                   ` Rafael J. Wysocki
@ 2011-03-30 20:02                                   ` Rafael J. Wysocki
  2011-03-30 21:19                                     ` Alan Stern
  2011-03-30 21:19                                     ` Alan Stern
  1 sibling, 2 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2011-03-30 20:02 UTC (permalink / raw)
  To: Alan Stern; +Cc: Jiri Slaby, akpm, linux-kernel, Linux-pm mailing list

On Wednesday, March 30, 2011, Alan Stern wrote:
> On Wed, 30 Mar 2011, Jiri Slaby wrote:
> 
> > > Strange indeed.  It's worth noting that the async stuff affects only
> > > the normal suspend and resume operations, not the late-suspend and
> > > early-resume operations.  This means that it all likelihood, the system
> > > crashes either before finishing the suspend or after doing a fair
> > > amount of the resume.  And yet that's not consistent with what you see
> > > on the screen.
> > > 
> > > By the way, are you booting with no_console_suspend?  And do you do 
> > > "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> > > suspending?
> > 
> > I'm testing this on my desktop. I found out yesterday, that I had async
> > completely disabled. So I have no output yet.
> > 
> > I took my dvb-t tuner from desktop and connected it to my notebook. And
> > got a similar hang during resume right now. It may not be related
> > though. The trace is:
> > s2disk          D 0000000000000000     0  6125   5902 0x00000004
> >  ffff8800797aba78 0000000000000082 ffff8800797ab9f8 0000000000012ac0
> >  ffff8800797abfd8 0000000000012ac0 ffff8800797abfd8 ffff8800797abfd8
> >  ffff8800777fe7f0 0000000000012ac0 0000000000012ac0 ffff8800797aa000
> > Call Trace:
> >  [<ffffffff8151e2ed>] schedule_timeout+0x28d/0x310
> >  [<ffffffff8151d410>] wait_for_common+0xc0/0x150
> >  [<ffffffff8133ad22>] _request_firmware+0x132/0x270
> >  [<ffffffffa06df2c7>] dvb_usb_download_firmware+0x37/0xf0 [dvb_usb]
> >  [<ffffffffa06dfbe5>] dvb_usb_device_init+0x165/0x1b0 [dvb_usb]
> >  [<ffffffffa06d6c27>] af9015_usb_probe+0x87/0xa0 [dvb_usb_af9015]
> >  [<ffffffff8138d9d2>] usb_probe_interface+0x142/0x270
> >  [<ffffffff8132f3c0>] really_probe+0x70/0x220
> >  [<ffffffff8132f757>] driver_probe_device+0x47/0xa0
> >  [<ffffffff8132e19c>] bus_for_each_drv+0x5c/0x90
> >  [<ffffffff8132f62f>] device_attach+0x8f/0xb0
> >  [<ffffffff8138d5b0>] usb_rebind_intf+0x60/0xa0
> >  [<ffffffff8138d6c7>] do_unbind_rebind+0x77/0xb0
> >  [<ffffffff8138d76b>] usb_resume+0x6b/0xb0
> >  [<ffffffff8137f96b>] usb_dev_complete+0xb/0x10
> >  [<ffffffff81334d1e>] device_complete+0x8e/0xe0
> >  [<ffffffff81335da1>] dpm_resume_end+0xa1/0x120
> >  [<ffffffff8109d890>] hibernation_snapshot+0xc0/0x120
> >  [<ffffffff810a1cde>] snapshot_ioctl+0x3ae/0x590
> >  [<ffffffff81169794>] do_vfs_ioctl+0x84/0x2f0
> >  [<ffffffff81169a98>] sys_ioctl+0x98/0xa0
> >  [<ffffffff81002ed2>] system_call_fastpath+0x16/0x1b
> >  [<00007fe6c82f8ce7>] 0x7fe6c82f8ce7
> > 
> > 
> > The firmware request should time out. I think I waited for longer than
> > 60 s before when I saw the hangs on the desktop, But do you have an idea
> > why it doesn't load the FW immediately?
> 
> I don't know why the request didn't time out, but this behavior should
> at least be reproducible.  Your stack trace implies that the firmware
> will need to be transferred every time the device resumes... but of
> course this leaves open the question of why your desktop crashed only
> occasionally.
> 
> Probably the firmware wasn't transferred immediately because the kernel
> relies on a userspace process to find and load the firmware, but at
> that point userspace was still frozen.
> 
> Rafael, this does seem to be a general problem.  Suppose a new device
> gets connected while the system is suspended.  How is the driver's
> probe method supposed to cope if it gets called while userspace is
> still frozen but it needs to load some firmware?
> 
> Is the answer that probing should always be delayed until after tasks
> are thawed?  There must be lots of subsystems which would have trouble 
> doing that, although we ought to be able to implement delayed probing 
> from within the driver core easily enough.

I don't know how to solve that.

First off, the prepare routines of drivers that need to load firmware during
resume probably should preload the firmware for the devices present during the
suspend.

Second, I don't generally think drivers should probe for devices during resume.
I guess the delayed probing would be the cleanest appoach here.

Thanks,
Rafael

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-30 15:10                                 ` Alan Stern
@ 2011-03-30 20:02                                   ` Rafael J. Wysocki
  2011-03-30 20:02                                   ` [linux-pm] " Rafael J. Wysocki
  1 sibling, 0 replies; 77+ messages in thread
From: Rafael J. Wysocki @ 2011-03-30 20:02 UTC (permalink / raw)
  To: Alan Stern; +Cc: akpm, Linux-pm mailing list, Jiri Slaby, linux-kernel

On Wednesday, March 30, 2011, Alan Stern wrote:
> On Wed, 30 Mar 2011, Jiri Slaby wrote:
> 
> > > Strange indeed.  It's worth noting that the async stuff affects only
> > > the normal suspend and resume operations, not the late-suspend and
> > > early-resume operations.  This means that it all likelihood, the system
> > > crashes either before finishing the suspend or after doing a fair
> > > amount of the resume.  And yet that's not consistent with what you see
> > > on the screen.
> > > 
> > > By the way, are you booting with no_console_suspend?  And do you do 
> > > "echo 8 >/proc/sys/kernel/printk" (or equivalently, Alt-SysRq-8) before 
> > > suspending?
> > 
> > I'm testing this on my desktop. I found out yesterday, that I had async
> > completely disabled. So I have no output yet.
> > 
> > I took my dvb-t tuner from desktop and connected it to my notebook. And
> > got a similar hang during resume right now. It may not be related
> > though. The trace is:
> > s2disk          D 0000000000000000     0  6125   5902 0x00000004
> >  ffff8800797aba78 0000000000000082 ffff8800797ab9f8 0000000000012ac0
> >  ffff8800797abfd8 0000000000012ac0 ffff8800797abfd8 ffff8800797abfd8
> >  ffff8800777fe7f0 0000000000012ac0 0000000000012ac0 ffff8800797aa000
> > Call Trace:
> >  [<ffffffff8151e2ed>] schedule_timeout+0x28d/0x310
> >  [<ffffffff8151d410>] wait_for_common+0xc0/0x150
> >  [<ffffffff8133ad22>] _request_firmware+0x132/0x270
> >  [<ffffffffa06df2c7>] dvb_usb_download_firmware+0x37/0xf0 [dvb_usb]
> >  [<ffffffffa06dfbe5>] dvb_usb_device_init+0x165/0x1b0 [dvb_usb]
> >  [<ffffffffa06d6c27>] af9015_usb_probe+0x87/0xa0 [dvb_usb_af9015]
> >  [<ffffffff8138d9d2>] usb_probe_interface+0x142/0x270
> >  [<ffffffff8132f3c0>] really_probe+0x70/0x220
> >  [<ffffffff8132f757>] driver_probe_device+0x47/0xa0
> >  [<ffffffff8132e19c>] bus_for_each_drv+0x5c/0x90
> >  [<ffffffff8132f62f>] device_attach+0x8f/0xb0
> >  [<ffffffff8138d5b0>] usb_rebind_intf+0x60/0xa0
> >  [<ffffffff8138d6c7>] do_unbind_rebind+0x77/0xb0
> >  [<ffffffff8138d76b>] usb_resume+0x6b/0xb0
> >  [<ffffffff8137f96b>] usb_dev_complete+0xb/0x10
> >  [<ffffffff81334d1e>] device_complete+0x8e/0xe0
> >  [<ffffffff81335da1>] dpm_resume_end+0xa1/0x120
> >  [<ffffffff8109d890>] hibernation_snapshot+0xc0/0x120
> >  [<ffffffff810a1cde>] snapshot_ioctl+0x3ae/0x590
> >  [<ffffffff81169794>] do_vfs_ioctl+0x84/0x2f0
> >  [<ffffffff81169a98>] sys_ioctl+0x98/0xa0
> >  [<ffffffff81002ed2>] system_call_fastpath+0x16/0x1b
> >  [<00007fe6c82f8ce7>] 0x7fe6c82f8ce7
> > 
> > 
> > The firmware request should time out. I think I waited for longer than
> > 60 s before when I saw the hangs on the desktop, But do you have an idea
> > why it doesn't load the FW immediately?
> 
> I don't know why the request didn't time out, but this behavior should
> at least be reproducible.  Your stack trace implies that the firmware
> will need to be transferred every time the device resumes... but of
> course this leaves open the question of why your desktop crashed only
> occasionally.
> 
> Probably the firmware wasn't transferred immediately because the kernel
> relies on a userspace process to find and load the firmware, but at
> that point userspace was still frozen.
> 
> Rafael, this does seem to be a general problem.  Suppose a new device
> gets connected while the system is suspended.  How is the driver's
> probe method supposed to cope if it gets called while userspace is
> still frozen but it needs to load some firmware?
> 
> Is the answer that probing should always be delayed until after tasks
> are thawed?  There must be lots of subsystems which would have trouble 
> doing that, although we ought to be able to implement delayed probing 
> from within the driver core easily enough.

I don't know how to solve that.

First off, the prepare routines of drivers that need to load firmware during
resume probably should preload the firmware for the devices present during the
suspend.

Second, I don't generally think drivers should probe for devices during resume.
I guess the delayed probing would be the cleanest appoach here.

Thanks,
Rafael

^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: [linux-pm] Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-30 20:02                                   ` [linux-pm] " Rafael J. Wysocki
@ 2011-03-30 21:19                                     ` Alan Stern
  2011-03-30 21:19                                     ` Alan Stern
  1 sibling, 0 replies; 77+ messages in thread
From: Alan Stern @ 2011-03-30 21:19 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: Jiri Slaby, akpm, linux-kernel, Linux-pm mailing list

On Wed, 30 Mar 2011, Rafael J. Wysocki wrote:

> > Rafael, this does seem to be a general problem.  Suppose a new device
> > gets connected while the system is suspended.  How is the driver's
> > probe method supposed to cope if it gets called while userspace is
> > still frozen but it needs to load some firmware?
> > 
> > Is the answer that probing should always be delayed until after tasks
> > are thawed?  There must be lots of subsystems which would have trouble 
> > doing that, although we ought to be able to implement delayed probing 
> > from within the driver core easily enough.
> 
> I don't know how to solve that.
> 
> First off, the prepare routines of drivers that need to load firmware during
> resume probably should preload the firmware for the devices present during the
> suspend.

That's okay for drivers that are bound to a device before the suspend 
starts.  But we also need to handle new devices added while the system 
was asleep.

> Second, I don't generally think drivers should probe for devices during resume.
> I guess the delayed probing would be the cleanest appoach here.

Here's the difficulty.  Normally the USB subsystem does use delayed
probing -- in fact, probing is done in a freezable thread.  However
this is a special case.  Not all USB drivers support suspend/resume;
those that don't get unbound during suspend and then rebound during
resume.  The rebinding occurs in the "complete" phase of the resume,
before tasks are thawed.

I suppose the rebinding could be delayed.  It would be better to fix
the USB DVB drivers, though, by adding PM support.  But there's a bunch
of them in drivers/media/dvb/dvb-usb, and AFAICS they would all need to
be fixed.  And I have no idea of what changes they would need.

Do you have any better suggestions?

Alan Stern


^ permalink raw reply	[flat|nested] 77+ messages in thread

* Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
  2011-03-30 20:02                                   ` [linux-pm] " Rafael J. Wysocki
  2011-03-30 21:19                                     ` Alan Stern
@ 2011-03-30 21:19                                     ` Alan Stern
  1 sibling, 0 replies; 77+ messages in thread
From: Alan Stern @ 2011-03-30 21:19 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: akpm, Linux-pm mailing list, Jiri Slaby, linux-kernel

On Wed, 30 Mar 2011, Rafael J. Wysocki wrote:

> > Rafael, this does seem to be a general problem.  Suppose a new device
> > gets connected while the system is suspended.  How is the driver's
> > probe method supposed to cope if it gets called while userspace is
> > still frozen but it needs to load some firmware?
> > 
> > Is the answer that probing should always be delayed until after tasks
> > are thawed?  There must be lots of subsystems which would have trouble 
> > doing that, although we ought to be able to implement delayed probing 
> > from within the driver core easily enough.
> 
> I don't know how to solve that.
> 
> First off, the prepare routines of drivers that need to load firmware during
> resume probably should preload the firmware for the devices present during the
> suspend.

That's okay for drivers that are bound to a device before the suspend 
starts.  But we also need to handle new devices added while the system 
was asleep.

> Second, I don't generally think drivers should probe for devices during resume.
> I guess the delayed probing would be the cleanest appoach here.

Here's the difficulty.  Normally the USB subsystem does use delayed
probing -- in fact, probing is done in a freezable thread.  However
this is a special case.  Not all USB drivers support suspend/resume;
those that don't get unbound during suspend and then rebound during
resume.  The rebinding occurs in the "complete" phase of the resume,
before tasks are thawed.

I suppose the rebinding could be delayed.  It would be better to fix
the USB DVB drivers, though, by adding PM support.  But there's a bunch
of them in drivers/media/dvb/dvb-usb, and AFAICS they would all need to
be fixed.  And I have no idea of what changes they would need.

Do you have any better suggestions?

Alan Stern

^ permalink raw reply	[flat|nested] 77+ messages in thread

end of thread, other threads:[~2011-03-30 21:20 UTC | newest]

Thread overview: 77+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-12-03  0:34 mmotm 2010-12-02-16-34 uploaded akpm
2010-12-03  0:34 ` akpm
2010-12-03 17:33 ` mmotm 2010-12-02-16-34 uploaded (acpi_video) Randy Dunlap
2010-12-03 17:37 ` mmotm 2010-12-02-16-34 uploaded (netfilter-related) Randy Dunlap
2010-12-03 21:43 ` mmotm 2010-12-02-16-34 uploaded Zimny Lech
2010-12-03 21:43   ` Zimny Lech
2010-12-04  0:39 ` Stephen Rothwell
2010-12-06 17:11   ` Randy Dunlap
2010-12-06 17:11     ` Randy Dunlap
2010-12-05  8:25 ` Resume hangs [was: mmotm 2010-12-02-16-34 uploaded] Jiri Slaby
2010-12-05 13:08   ` Rafael J. Wysocki
2010-12-13 10:04     ` Jiri Slaby
2010-12-13 10:04     ` Jiri Slaby
2010-12-13 21:10       ` Rafael J. Wysocki
2010-12-13 21:10       ` Rafael J. Wysocki
2010-12-14 22:08         ` Jiri Slaby
2010-12-14 22:22           ` Rafael J. Wysocki
2010-12-14 22:22           ` Rafael J. Wysocki
2011-01-06 14:18             ` Jiri Slaby
2011-01-06 14:18             ` Jiri Slaby
2011-01-20 15:23               ` Jiri Slaby
2011-01-20 15:23               ` Jiri Slaby
2011-01-20 21:02                 ` Rafael J. Wysocki
2011-01-21  9:16                   ` Jiri Slaby
2011-01-21  9:16                   ` Jiri Slaby
2011-01-31 21:37                   ` Jiri Slaby
2011-01-31 21:40                     ` Jiri Slaby
2011-01-31 21:40                     ` Jiri Slaby
2011-01-31 22:00                     ` Rafael J. Wysocki
2011-01-31 22:00                     ` Rafael J. Wysocki
2011-02-04 18:33                       ` Jiri Slaby
2011-02-04 19:33                         ` [linux-pm] " Alan Stern
2011-02-04 19:38                           ` Jiri Slaby
2011-02-04 19:38                           ` [linux-pm] " Jiri Slaby
2011-02-04 20:07                             ` Alan Stern
2011-02-04 20:07                             ` [linux-pm] " Alan Stern
2011-02-22  8:45                           ` Jiri Slaby
2011-02-22  8:45                           ` [linux-pm] " Jiri Slaby
2011-02-22 15:36                             ` Alan Stern
2011-02-23 11:58                               ` Jiri Slaby
2011-02-23 11:58                               ` [linux-pm] " Jiri Slaby
2011-02-23 15:59                                 ` Alan Stern
2011-02-23 15:59                                 ` Alan Stern
2011-02-24 18:41                               ` [linux-pm] " Jiri Slaby
2011-02-24 18:41                               ` Jiri Slaby
2011-03-08  9:13                               ` Jiri Slaby
2011-03-08  9:13                               ` [linux-pm] " Jiri Slaby
2011-03-08 19:25                                 ` Rafael J. Wysocki
2011-03-08 20:31                                   ` Jiri Slaby
2011-03-08 22:12                                     ` Rafael J. Wysocki
2011-03-08 22:12                                     ` [linux-pm] " Rafael J. Wysocki
2011-03-08 22:14                                       ` Jiri Slaby
2011-03-08 22:15                                         ` Rafael J. Wysocki
2011-03-08 22:15                                         ` [linux-pm] " Rafael J. Wysocki
2011-03-08 22:16                                         ` Rafael J. Wysocki
2011-03-08 22:18                                           ` Jiri Slaby
2011-03-08 22:18                                           ` Jiri Slaby
2011-03-08 22:16                                         ` Rafael J. Wysocki
2011-03-08 22:14                                       ` Jiri Slaby
2011-03-08 20:31                                   ` Jiri Slaby
2011-03-08 19:25                                 ` Rafael J. Wysocki
2011-03-30 14:11                               ` [linux-pm] " Jiri Slaby
2011-03-30 15:10                                 ` Alan Stern
2011-03-30 20:02                                   ` Rafael J. Wysocki
2011-03-30 20:02                                   ` [linux-pm] " Rafael J. Wysocki
2011-03-30 21:19                                     ` Alan Stern
2011-03-30 21:19                                     ` Alan Stern
2011-03-30 15:10                                 ` Alan Stern
2011-03-30 14:11                               ` Jiri Slaby
2011-02-22 15:36                             ` Alan Stern
2011-02-04 19:33                         ` Alan Stern
2011-02-04 18:33                       ` Jiri Slaby
2011-01-31 21:37                   ` Jiri Slaby
2011-01-20 21:02                 ` Rafael J. Wysocki
2010-12-14 22:08         ` Jiri Slaby
2010-12-05 13:08   ` Rafael J. Wysocki
2010-12-05  8:25 ` Jiri Slaby

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.