ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
- New git tree git-powerpc-galak.patch added to the -mm lineup: ppc32
things, mainly (Kumar Gala <[email protected]>)
Boilerplate:
- See the `hot-fixes' directory for any important updates to this patchset.
- To fetch an -mm tree using git, use (for example)
git-fetch git://git.kernel.org/pub/scm/linux/kernel/git/smurf/linux-trees.git tag v2.6.16-rc2-mm1
git-checkout -b local-v2.6.16-rc2-mm1 v2.6.16-rc2-mm1
- -mm kernel commit activity can be reviewed by subscribing to the
mm-commits mailing list.
echo "subscribe mm-commits" | mail [email protected]
- If you hit a bug in -mm and it is not obvious which patch caused it, it is
most valuable if you can perform a bisection search to identify which patch
introduced the bug. Instructions for this process are at
http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt
But beware that this process takes some time (around ten rebuilds and
reboots), so consider reporting the bug first and if we cannot immediately
identify the faulty patch, then perform the bisection search.
- When reporting bugs, please try to Cc: the relevant maintainer and mailing
list on any email.
- When reporting bugs in this kernel via email, please also rewrite the
email Subject: in some manner to reflect the nature of the bug. Some
developers filter by Subject: when looking for messages to read.
- Occasional snapshots of the -mm lineup are uploaded to
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/ and are announced on
the mm-commits list.
Changes since 2.6.23-rc6-mm1:
origin.patch
git-acpi.patch
git-alsa.patch
git-arm.patch
git-audit-master.patch
git-avr32.patch
git-cifs.patch
git-cpufreq.patch
git-powerpc.patch
git-powerpc-galak.patch
git-drm.patch
git-dvb.patch
git-hwmon.patch
git-gfs2-nmw.patch
git-hid.patch
git-ieee1394.patch
git-infiniband.patch
git-input.patch
git-jfs.patch
git-jg-misc.patch
git-kbuild.patch
git-kvm.patch
git-libata-all.patch
git-md-accel.patch
git-mips.patch
git-mmc.patch
git-mtd.patch
git-ubi.patch
git-net.patch
git-backlight.patch
git-battery.patch
git-nfs.patch
git-nfsd.patch
git-ocfs2.patch
git-r8169.patch
git-selinux.patch
git-s390.patch
git-sched.patch
git-sh.patch
git-scsi-misc.patch
git-scsi-rc-fixes.patch
git-block.patch
git-unionfs.patch
git-watchdog.patch
git-wireless.patch
git-ipwireless_cs.patch
git-newsetup.patch
git-xfs.patch
git-cryptodev.patch
git-kgdb.patch
git-block-vs-reiser4.patch
git-nfsd-broke-reiser4.patch
git trees
-fix-dac960-driver-on-machines-which-dont-support-64-bit-dma-fix.patch
-uml-use-correct-type-in-blkgetsize-ioctl.patch
-atyfb-force-29mhz-xtal-on-g3-powerbooks.patch
-fix-failure-to-resume-from-initrds.patch
-fix-uts-corruption-during-cloneclone_newuts.patch
-rtc-ds1742c-should-use-resource_size_t-for-base-address.patch
-rtc-rtc-ds1553c-should-use-resource_size_t-for-base.patch
-mspec-handle-shrinking-virtual-memory-areas.patch
-mspec-handle-shrinking-virtual-memory-areas-3.patch
-pci-fix-unterminated-pci_device_id-lists.patch
-pci-fix-unterminated-pci_device_id-lists-fix.patch
-xen-dont-bother-trying-to-set-cr4.patch
-intelfb-fix-bug-in-dpll-disable.patch
-intel-agp-fix-i830-mask-variable-that-changed-with-g33-support.patch
-dir_index-error-out-instead-of-bug-on-corrupt-dx-dirs.patch
-nfs-fix-oops-re-sysctls-and-v4-support.patch
-disable-sys_timerfd-for-2623.patch
-ext34-ensure-do_split-leaves-enough-free-space-in-both-blocks.patch
-kernel-userc-use-list_for_each_entry-instead-of-list_for_each.patch
-convert-uid-hash-to-hlist.patch
-fix-user-namespace-exiting-oops.patch
-fix-numa-memory-policy-reference-counting.patch
-git-alsa-sc6000-build-fix.patch
-ess-maestro-1-2-2e-sound-card-use-list_for_each_entry.patch
-routines-for-effect-processor-fx8010-use-list_for_each_entry.patch
-arm-unbalanced-parenthesis-fix.patch
-ppc-remove-apus-support.patch
-fix-gregkh-driver-sysfs-spit-a-warning-to-users-when-they-try-to-create-a-duplicate-sysfs-file.patch
-drivers-char-nozomic-__devexit_p-usage-build-fix.patch
-i2c-i801-documentation-patch-for-intel-tolapai.patch
-i2c-i801-smbus-patch-for-intel-tolapai.patch
-i2c-i801-smbus-patch-for-intel-tolapai-fix.patch
-ata-add-the-sw-ncq-support-to-sata_nv-for-mcp51-mcp55-mcp61patch.patch
-ahci-raid-mode-sata-patch-for-intel-tolapai.patch
-st340823a-hpa-and-libata.patch
-ata-increase-allowed-config-flags.patch
-ata_piix-replace-spaces-with-tabs.patch
-ide-ide-remove-ide-rate-filter-from-speedproc.patch
-ide-ide-use-only-set-pio-mode-for-programming-pio-modes.patch
-ide-ide-remove-ide-dma-check.patch
-ide-ide-add-mwdma-mask-and-swdma-mask-to-ide-pci-device-t.patch
-git-net-fix-2.patch
-nit-net-skge-build-fix.patch
-git-net-af_iucv-fixes.patch
-git-net-sgiseeq-fix.patch
-git-net-fix-ibmveth.patch
-git-net-af_iucv-fixes.patch
-git-net-sgiseeq-fix.patch
-git-net-fix-ibmveth.patch
-sky2-118.patch
-sb1250-macc-de-typedef-de-volatile-de-etc.patch
-net_sb1250_mac-update-kconfig-entry.patch
-net_sb1250_mac-rename-to-sb1250_mac.patch
-ipg-add-ip1000a-driver-to-kernel-tree.patch
-git-net-broke-ipg-add-ip1000a-driver-to-kernel-tree.patch
-use-mutex-instead-of-semaphore-in-the-onstream-scsi-tape-driver.patch
-git-block-fix-u14-34f.patch
-ll_rw_blk-blk_cpu_notifier-should-be-__cpuinitdata.patch
-x86_64-mm-fix-section-mismatch-warnings.patch
-therm_throtc-fix-section-mismatch.patch
-i386-cpuid_count-fix-argument-signedness-warnings.patch
-i386-fix-section-mismatch-warning-in-intelc.patch
-x86-misc-constifications.patch
-x86-constify-wd_ops.patch
-x86-multi-byte-single-instruction-nops.patch
-enforce-noreplace-smp-in-alternative_instructions.patch
-i386-apic-fix-4-bit-apicid-assumption-of-mach-default.patch
-scsi-use-lock-per-host-instead-of-per-device-for-shared-queue-tag-host.patch
-x86_64-nx-bit-handling-in-change_page_attr.patch
-driver-core-fix-deprectated-sysfs-structure-for-nested-class-devices.patch
-pvrusb2-hdw-terminate-usb-device-id-table-differently.patch
-cpu-hotplug-cpuid-fix-cpu-hotplug-error-handling.patch
Merged into mainline or a subsystem tree
+ufs-fix-sun-state.patch
+fix-potential-oops-in-generic_setlease.patch
+fix-potential-oops-in-generic_setlease-v2.patch
+fix-mspec-handle-shrinking-virtual-memory-areas.patch
+missing-null-termination-in-one-wire-uevent.patch
+typo-fix-kernel-config-option.patch
2.6.23 queue
+fix-oops-in-platform-uevent.patch
Also 2.6.23 I guess
-git-acpi-fixup.patch
Unneeded
+acpi-sbs-fix-sbs-add-alarm-patch.patch
ACPI fix
+agk-dm-dm-ioctl-fix-compat-bounds-test.patch
+agk-dm-dm-tidy-bio_io_error-usage.patch
+agk-dm-dm-ioctl-remove-vmalloc-void-cast.patch
+agk-dm-dm-crypt-use-per-device-singlethread-workqueues.patch
+agk-dm-dm-crypt-add-post-processing-queue.patch
device mapped tree updates
+fix-3-gregkh-driver-kobject-remove-the-static-array-for-the-name.patch
+kobject-temporarily-save-k_name-on-cleanup-for-debug-message.patch
Fix Greg's driver core tree
+jdelvare-i2c-i2c-i801-tolapai-support.patch
i2c tree update
Dropped
+first-stab-at-elantech-touchpad-driver-for-26226-testers.patch
+first-stab-at-elantech-touchpad-driver-for-26226-testers-fix.patch
+make-wistron-btns-recognize-special-keys-on-medion-wim2160-notebooks.patch
Input stuff
+menuconfig-distinguish-between-selected-by-another-options-and-comments.patch
Kconfig
+pata_acpi-use-ata_sff_port_start.patch
pata update
+libata-add-a-horkage-entry-for-drq-mishandling-atapi.patch
+ahci-add-mcp79-support-to-ahci-driver.patch
+ahci-add-mcp79-support-to-ahci-driver-update.patch
ata updates
+ide-ide-call-udma_filter-before-resorting-to-the-ultradma-mask.patch
+ide-ide-remove-ide-rate-filter-from-speedproc-take-2.patch
+ide-ide-use-only-set-pio-mode-for-programming-pio-modes-take-2.patch
+ide-ide-remove-ide-dma-check-take-2.patch
+ide-ide-add-mwdma-mask-and-swdma-mask-to-ide-pci-device-t-take-2.patch
+ide-alim15x3-fix-cd_rom-dma-and-pio-fifo-settings-setup.patch
+ide-alim15x3-use-host-flags-and-udma-mask-fields-from-ide-pci-device-t.patch
+ide-aec62xx-remove-aec62xx-dma-lost-irq.patch
+ide-siimage-separate-pata-and-sata-methods.patch
+ide-ide-add-fixup-method-to-ide-hwif-t.patch
+ide-ide-add-ide-device-add.patch
+ide-maintainers-mark-ide-scsi-as-orhpan.patch
+ide-ide-add-ide-find-port-helper.patch
+ide-ide-remove-redundant-comments-from-ide-h.patch
+ide-ide-add-config-ide-arch-obsolete-init.patch
IDE tree updates
+git-mtd-vs-powerpc.patch
Fix mtd borkage
+git-net-fix-macec.patch
+git-net-sky2-fixups.patch
+git-net-fix-wireless-kconfig.patch
+git-net-fix-spidernet-build.patch
+spider_net_ethtool-keep-up-with-recent-netdev-stats-changes.patch
+pasemi_mac-build-fix-after-recent-netdev-stats.patch
+make-mv643xx_ethc-build-again.patch
+dgrs-remove-from-build-config-and-maintainer-list.patch
net fixes
+phylib-spinlock-fixes-for-softirqs.patch
+forcedeth-power-down-phy-when-interface-is-down.patch
+forcedeth-no-link-is-informational.patch
+phylib-irq-event-workqueue-handling-fixes.patch
+phylib-fix-an-interrupt-loop-potential-when-halting.patch
netdev updates
+git-battery.patch
+revert-git-battery.patch
Greg's driver tree breaks this git tree
-git-nfsd-fixup.patch
Unneeded
+provide-stubs-for-enable_irq_wake-and-disable_irq_wake.patch
+serial_txx9-use-upf_fixed_port.patch
serial stuff
+some-proc-entries-are-missed-in-sched_domain-sys_ctl-debug.patch
sched fix
+mpt-fusion-shut-up-uninitialized-variable.patch
+mptbase-reset-ioc-initiator-during-pci-resume.patch
scsi fixes
+usb-gadget-ether-prevent-oops-caused-by-error-interrupt-race.patch
USB fix
+9p-fix-compile-error-if-config_sysctl.patch
9pfs fix
-git-net-vs-git-wireless.patch
-git-net-vs-git-wireless-2.patch
-ath5k-panic-fix.patch
-git-net-vs-git-wireless-3.patch
-git-net-broke-git-wireless.patch
-more-wireless-borkage.patch
-more-wireless-borkage-2.patch
-more-wireless-borkage-3.patch
-git-wireless-fix-99.patch
more wireless churn, getting sorted out now. b44 is still disabled in -mm,
perhaps unjustly.
+x86_64-mm-misc_-constifications.patch
+x86_64-mm-constify-stacktrace_ops.patch
+x86_64-mm-unwinder-default.patch
+x86_64-mm-less-stack-alignment.patch
+x86_64-mm-fix-argument-signedness-warnings.patch
+x86_64-mm-cpu-hotplug-cpuid-fix-cpu-hotplug-error-handling.patch
+x86_64-mm-die-lock.patch
+x86_64-mm-mce-setup.patch
+x86_64-mm-fix-off-by-one-in-find_next_zero_string.patch
+x86_64-mm-fix-4-bit-apicid-assumption-of-mach-default.patch
+x86_64-mm-fix-section-mismatch.patch
+x86_64-mm-fix-section-mismatch-warning-in-intel_c.patch
+x86_64-mm-constify-wd_ops.patch
+x86_64-mm-multi-byte-single-instruction-nops.patch
+x86_64-mm-introduce-used_vectors-bitmap-which-can-be-used-to-reserve-vectors.patch
+x86_64-mm-configure-hpet_emulate_rtc-automatically.patch
+x86_64-mm-also-show-non-zero-irq-counts-for-vectors-that-currently-dont-have-a-handler.patch
+x86_64-mm-avoid-temporarily-inconsistent-pte-s.patch
+x86_64-mm-return-correct-error-code-from-child_rip-in-x86_64-entry_s.patch
+x86_64-mm-agp-flush.patch
+x86_64-mm-aout-regs.patch
+x86_64-mm-remove-fpu-port.patch
x86 tree updates
+agp-fix-race-condition-between-unmapping-and-freeing-pages.patch
AGP fix
+convert-cpu_sibling_map-to-a-per_cpu-data-array-ppc64-fix-2.patch
Fix convert-cpu_sibling_map-to-a-per_cpu-data-array.patch even more
+x86_64-nx-bit-handling-in-change_page_attr.patch
x86 fix
+kgdb-fix-help-text.patch
+kgdb-fix-docbook-and-kernel-doc-typos.patch
kgdb updates
+usb-dont-propagate-freeze-or-prethaw-suspends.patch
+ppp_mppe-dont-put-interimkey-on-the-stack.patch
Maybe 2.6.23 material
+mm-use-pagevec-to-rotate-reclaimable-page.patch
+mm-use-pagevec-to-rotate-reclaimable-page-fix.patch
+git-nfs-vs-nfs-convert-to-new-aops-fix.patch
+slub-avoid-touching-page-struct-when-freeing-to-per-cpu-slab-fix.patch
+fix-memory-hot-remove-not-configured-case.patch
+fix-memory-hot-remove-not-configured-case-fix.patch
+mm-per-device-dirty-threshold-fix.patch
MM updates
+oom-move-prototypes-to-appropriate-header-file.patch
+oom-move-constraints-to-enum.patch
+oom-change-all_unreclaimable-zone-member-to-flags.patch
+oom-change-all_unreclaimable-zone-member-to-flags-fix.patch
+oom-add-per-zone-locking.patch
+oom-serialize-out-of-memory-calls.patch
+oom-add-oom_kill_allocating_task-sysctl.patch
+oom-suppress-extraneous-stack-and-memory-dump.patch
+oom-compare-cpuset-mems_allowed-instead-of-exclusive.patch
+oom-do-not-take-callback_mutex.patch
+oom-do-not-take-callback_mutex-fix.patch
oom-killer work
+alpha-beautify-vmlinuxlds.patch
alpha cleanup
+tty-bring-the-old-cris-driver-back-somewhere-into-the.patch
cris update
+uml-stop-saving-process-fp-state-fix.patch
Fix uml-stop-saving-process-fp-state.patch
+uml-rename-pt_regs-general-purpose-register-file-fix.patch
Fix uml-rename-pt_regs-general-purpose-register-file.patch
+uml-eliminate-hz.patch
+uml-fix-timer-switching.patch
+uml-simplify-interval-setting.patch
+uml-separate-timer-initialization.patch
+uml-generic_time-support.patch
+uml-generic_clockevents-support.patch
+uml-clocksource-support.patch
+uml-clocksource-support-fix.patch
+uml-tickless-support.patch
+uml-tickless-support-fix.patch
+uml-eliminate-interrupts-in-the-idle-loop.patch
+uml-eliminate-sigalrm.patch
+uml-use-sec_per_sec-constants.patch
UML updates
-remove-superfluous-definition-of-__setup_null_param-macro-and-broken-for-module-__setup_param.patch
Dropped
+keys-make-request_key-and-co-fundamentally-asynchronous-update.patch
+keys-missing-word-in-documentation.patch
Fix keys-make-request_key-and-co-fundamentally-asynchronous.patch
+jbd-slab-cleanups-2.patch
+jbd-slab-cleanups-3.patch
Fix jbd-slab-cleanups.patch
+shrink_dcache_sb-speedup.patch
+add-consts-where-appropriate-in-fs-nls.patch
+reiserfs-workaround-for-dead-loop-in-finish_unfinished.patch
+reiserfs-workaround-for-dead-loop-in-finish_unfinished-fix.patch
+unify-dma_bit_mask-definitions-v31.patch
+delete-gcc-295-compatible-structure-definition.patch
+fs-isofs-nameic-remove-uninitialized-local-vars-warning.patch
+ide-cd-is-unmaintained.patch
+tty-expose-new-methods-needed-for-drivers-to-get-termios.patch
+tty-expose-new-methods-needed-for-drivers-to-get-termios-fix.patch
+kernel-printkc-concerns-about-the-console-handover.patch
+atomic_opstxt-has-incorrect-misleading-and-insufficient-information.patch
+udf-code-style-fixup-v3.patch
+aio-dont-confuse-debug-define-location.patch
+userc-deinline.patch
+userc-ifdef-mq_bytes.patch
+userc-ifdef-mq_bytes-fix.patch
Misc
+isdn-hisax-hfc_usbc-fix-check-after-use.patch
ISDN fix
+ecryptfs-remove-header_extent_size.patch
+ecryptfs-remove-assignments-in-if-statements.patch
+ecryptfs-read_writec-routines.patch
+ecryptfs-replace-encrypt-decrypt-and-inode-size-write.patch
+ecryptfs-set-up-and-destroy-persistent-lower-file.patch
+ecryptfs-update-metadata-read-write-functions.patch
+ecryptfs-make-open-truncate-and-setattr-use-persistent-file.patch
+ecryptfs-convert-mmap-functions-to-use-persistent-file.patch
+ecryptfs-convert-mmap-functions-to-use-persistent-file-fix.patch
+ecryptfs-initialize-persistent-lower-file-on-inode-create.patch
+ecryptfs-remove-unused-functions-and-kmem_cache.patch
+ecryptfs-replace-magic-numbers.patch
ecryptfs update (ugly, can't think of a better way, needs better review)
+radeonfb-xpress-200m-rc410-support-patch.patch
+drivers-video-pmag-ba-fbc-improve-diagnostics.patch
+drivers-video-pmag-ba-fbc-improve-diagnostics-fix.patch
fbdev updates
+ext4-uninitialized-block-groups.patch
+ext4-uninitialized-block-groups-fix.patch
+introduce-ext4_find_next_bit.patch
+ext4-fix-sparse-warnings.patch
+ext4-flex_bg-kernel-support-v2.patch
ext4 stuff
+ecryptfs-allow-lower-fs-to-interpret-attr_kill_sid.patch
+knfsd-only-set-attr_kill_sid-if-attr_mode-isnt-being-explicitly-set.patch
+reiserfs-turn-of-attr_kill_sid-at-beginning-of-reiserfs_setattr.patch
+unionfs-fix-unionfs_setattr-to-handle-attr_kill_sid.patch
+vfs-make-notify_change-pass-attr_kill_sid-to-setattr-operations.patch
+nfs-if-attr_kill_sid-bits-are-set-then-skip-mode-change.patch
+cifs-ignore-mode-change-if-its-just-for-clearing-setuid-setgid-bits.patch
VFS attributes work
+r-o-bind-mounts-filesystem-helpers-for-custom-struct-files.patch
+r-o-bind-mounts-rearrange-may_open-to-be-r-o-friendly.patch
+r-o-bind-mounts-give-permission-a-local-mnt-variable.patch
+r-o-bind-mounts-create-cleanup-helper-svc_msnfs.patch
+r-o-bind-mounts-stub-functions.patch
+r-o-bind-mounts-elevate-write-count-opend-files.patch
+r-o-bind-mounts-elevate-write-count-for-some-ioctls.patch
+r-o-bind-mounts-elevate-writer-count-for-chown-and-friends.patch
+r-o-bind-mounts-make-access-use-mnt-check.patch
+r-o-bind-mounts-elevate-mnt-writers-for-callers-of-vfs_mkdir.patch
+r-o-bind-mounts-elevate-write-count-during-entire-ncp_ioctl.patch
+r-o-bind-mounts-elevate-write-count-during-entire-ncp_ioctl-fix.patch
+r-o-bind-mounts-elevate-write-count-for-link-and-symlink-calls.patch
+r-o-bind-mounts-elevate-mount-count-for-extended-attributes.patch
+r-o-bind-mounts-elevate-write-count-for-file_update_time.patch
+r-o-bind-mounts-unix_find_other-elevate-write-count-for-touch_atime.patch
+r-o-bind-mounts-elevate-write-count-over-calls-to-vfs_rename.patch
+r-o-bind-mounts-nfs-check-mnt-instead-of-superblock-directly.patch
+r-o-bind-mounts-elevate-writer-count-for-do_sys_truncate.patch
+r-o-bind-mounts-elevate-write-count-for-do_utimes.patch
+r-o-bind-mounts-elevate-write-count-for-do_sys_utime-and-touch_atime.patch
+r-o-bind-mounts-sys_mknodat-elevate-write-count-for-vfs_mknod-create.patch
+r-o-bind-mounts-elevate-mnt-writers-for-vfs_unlink-callers.patch
+r-o-bind-mounts-do_rmdir-elevate-write-count.patch
+r-o-bind-mounts-track-number-of-mount-writers.patch
+r-o-bind-mounts-track-number-of-mount-writers-hack-hack-hack.patch
+r-o-bind-mounts-honor-r-w-changes-at-do_remount-time.patch
read-only bind mounts
+add-a-missing-00-index-file-for-documentation-vm-fix.patch
Fix add-a-missing-00-index-file-for-documentation-vm.patch
+remove-broken-netfilter-binary-sysctls-from-bridging-code.patch
sysctl fixes
+make-access-to-tasks-nsproxy-lighterpatch-breaks-unshare.patch
Fix make-access-to-tasks-nsproxy-lighter.patch
-isolate-some-explicit-usage-of-task-tgid-fix.patch
-isolate-some-explicit-usage-of-task-tgid-fix-fix.patch
Folded into isolate-some-explicit-usage-of-task-tgid.patch
+memory-controller-oom-handling-v7-vs-oom-killer-stuff.patch
Fix memory-controller-oom-handling-v7.patch
+mem-controller-gfp-mask-fix.patch
Fix memory-controller patches in -mm.
+ipc-integrate-ipc_checkid-into-ipc_lock-fix-2.patch
+ipc-integrate-ipc_checkid-into-ipc_lock-fix-3.patch
Fix ipc-integrate-ipc_checkid-into-ipc_lock-fix.patch
+ipc_fix_wrong_comments.patch
Fix ipc comments
+extended-crashkernel-command-line.patch
+use-extended-crashkernel-command-line-on-i386.patch
+use-extended-crashkernel-command-line-on-x86_64.patch
+use-extended-crashkernel-command-line-on-ia64.patch
+use-extended-crashkernel-command-line-on-ppc64.patch
+use-extended-crashkernel-command-line-on-sh.patch
+add-documentation-for-extended-crashkernel-syntax.patch
kdump stuff
+cleanup-macros-for-distinguishing-mandatory-locks.patch
+gfs2-cleanup-explicit-check-for-mandatory-locks.patch
+9pfs-cleanup-explicit-check-for-mandatory-locks.patch
+afs-cleanup-explicit-check-for-mandatory-locks.patch
+nfs-cleanup-explicit-check-for-mandatory-locks.patch
+rework-proc-locks-via-seq_files-and-seq_list-helpers.patch
+rework-proc-locks-via-seq_files-and-seq_list-helpers-fix.patch
+rework-proc-locks-via-seq_files-and-seq_list-helpers-fix-2.patch
file locking rework
+exportfs-add-fid-type.patch
+exportfs-add-new-methods.patch
+ext2-new-export-ops.patch
+ext3-new-export-ops.patch
+ext4-new-export-ops.patch
+efs-new-export-ops.patch
+jfs-new-export-ops.patch
+ntfs-new-export-ops.patch
+xfs-new-export-ops.patch
+fat-new-export-ops.patch
+isofs-new-export-ops.patch
+shmem-new-export-ops.patch
+reiserfs-new-export-ops.patch
+gfs2-new-export-ops.patch
+ocfs2-new-export-ops.patch
+exportfs-remove-old-methods.patch
+exportfs-make-struct-export_operations-const.patch
+exportfs-update-documentation.patch
nfsd export rework
5392 commits in 2031 patch files
All patches:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/patch-list
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>
> - New git tree git-powerpc-galak.patch added to the -mm lineup: ppc32
> things, mainly (Kumar Gala <[email protected]>)
>
>
<snip>
Hi Andrew,
The link error for a PowerMac G5 (powerpc) is still seen with
2.6.23-rc7-mm1,
and was reported for 2.6.23-rc6-mm1 (http://lkml.org/lkml/2007/9/19/62).
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux.o
ld: dynreloc miscount for fs/built-in.o, section .opd
ld: can not edit opd Bad value
make: *** [vmlinux.o] Error 1
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
On Mon, 24 Sep 2007 02:17:16 PDT, Andrew Morton said:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
It lived fast, it died young, it didn't leave a pretty corpse...
Something in the startup scripts did a 'touch', and ker-blam.
[ 15.668000] Unable to handle kernel NULL pointer dereference at 0000000000000252 RIP:
[ 15.668000] [<ffffffff802a1dd1>] __mnt_is_readonly+0x9/0x1e
[ 15.668000] PGD 52be067 PUD 5645067 PMD 0
[ 15.668000] Oops: 0000 [1] PREEMPT SMP
[ 15.668000] last sysfs file: /block/dm-13/dev
[ 15.668000] CPU 0
[ 15.668000] Modules linked in: rtc
[ 15.668000] Pid: 528, comm: touch Not tainted 2.6.23-rc7-mm1 #1
[ 15.668000] RIP: 0010:[<ffffffff802a1dd1>] [<ffffffff802a1dd1>] __mnt_is_readonly+0x9/0x1e
[ 15.668000] RSP: 0018:ffff8100045fddd8 EFLAGS: 00010202
[ 15.668000] RAX: 0000000000000001 RBX: ffff810002c10680 RCX: 0000000000000001
[ 15.668000] RDX: ffff810082504000 RSI: ffff810005243168 RDI: 0000000000000202
[ 15.668000] RBP: ffff8100045fddd8 R08: 0000000000000001 R09: 0000000000000002
[ 15.668000] R10: 0000000000000000 R11: ffff8100045fde68 R12: 0000000000000202
[ 15.668000] R13: 00000000ffffffe2 R14: ffff8100052c1d80 R15: ffff8100039aa8a0
[ 15.668000] FS: 00007f9527f596f0(0000) GS:ffffffff806b6000(0000) knlGS:0000000000000000
[ 15.668000] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 15.668000] CR2: 0000000000000252 CR3: 00000000052cb000 CR4: 00000000000006e0
[ 15.668000] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 15.668000] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 15.668000] Process touch (pid: 528, threadinfo ffff8100045fc000, task ffff8100047517e0)
[ 15.668000] last branch before last exception/interrupt
[ 15.668000] from [<ffffffff802a4d1b>] mnt_want_write+0x44/0xb5
[ 15.668000] to [<ffffffff802a1dc8>] __mnt_is_readonly+0x0/0x1e
[ 15.668000] Stack: ffff8100045fde08 ffffffff802a4d20 ffff8100045fddf8 0000000000000000
[ 15.668000] 00000000fffffff7 ffff810005243140 ffff8100045fdf28 ffffffff802ad288
[ 15.668000] ffff8100045fde58 0000000000000202 ffff8100045fde58 ffffffff8035437b
[ 15.668000] Call Trace:
[ 15.668000] [<ffffffff802a4d20>] mnt_want_write+0x49/0xb5
[ 15.668000] [<ffffffff802ad288>] do_utimes+0xd0/0x220
[ 15.668000] [<ffffffff8035437b>] __up_read+0x7a/0x83
[ 15.668000] [<ffffffff8024b1af>] up_read+0x9/0xb
[ 15.668000] [<ffffffff8051977c>] do_page_fault+0x421/0x7d0
[ 15.668000] [<ffffffff8028b370>] do_filp_open+0x36/0x46
[ 15.668000] [<ffffffff802ad519>] sys_utimensat+0x8b/0xa5
[ 15.668000] [<ffffffff80517a4d>] error_exit+0x0/0x84
[ 15.668000] [<ffffffff8020c10e>] system_call+0x7e/0x83
[ 15.668000]
[ 15.668000]
[ 15.668000] Code: f6 47 50 40 75 0d 48 8b 47 28 8a 40 58 83 e0 01 0f b6 c0 c9
[ 15.668000] RIP [<ffffffff802a1dd1>] __mnt_is_readonly+0x9/0x1e
[ 15.668000] RSP <ffff8100045fddd8>
[ 15.668000] CR2: 0000000000000252
[email protected] wrote:
> On Mon, 24 Sep 2007 02:17:16 PDT, Andrew Morton said:
>
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>
> It lived fast, it died young, it didn't leave a pretty corpse...
>
> Something in the startup scripts did a 'touch', and ker-blam.
>
> [ 15.668000] Unable to handle kernel NULL pointer dereference at 0000000000000252 RIP:
> [ 15.668000] [<ffffffff802a1dd1>] __mnt_is_readonly+0x9/0x1e
> [ 15.668000] PGD 52be067 PUD 5645067 PMD 0
> [ 15.668000] Oops: 0000 [1] PREEMPT SMP
> [ 15.668000] last sysfs file: /block/dm-13/dev
> [ 15.668000] CPU 0
> [ 15.668000] Modules linked in: rtc
> [ 15.668000] Pid: 528, comm: touch Not tainted 2.6.23-rc7-mm1 #1
> [ 15.668000] RIP: 0010:[<ffffffff802a1dd1>] [<ffffffff802a1dd1>] __mnt_is_readonly+0x9/0x1e
> [ 15.668000] RSP: 0018:ffff8100045fddd8 EFLAGS: 00010202
> [ 15.668000] RAX: 0000000000000001 RBX: ffff810002c10680 RCX: 0000000000000001
> [ 15.668000] RDX: ffff810082504000 RSI: ffff810005243168 RDI: 0000000000000202
> [ 15.668000] RBP: ffff8100045fddd8 R08: 0000000000000001 R09: 0000000000000002
> [ 15.668000] R10: 0000000000000000 R11: ffff8100045fde68 R12: 0000000000000202
> [ 15.668000] R13: 00000000ffffffe2 R14: ffff8100052c1d80 R15: ffff8100039aa8a0
> [ 15.668000] FS: 00007f9527f596f0(0000) GS:ffffffff806b6000(0000) knlGS:0000000000000000
> [ 15.668000] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> [ 15.668000] CR2: 0000000000000252 CR3: 00000000052cb000 CR4: 00000000000006e0
> [ 15.668000] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ 15.668000] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [ 15.668000] Process touch (pid: 528, threadinfo ffff8100045fc000, task ffff8100047517e0)
> [ 15.668000] last branch before last exception/interrupt
> [ 15.668000] from [<ffffffff802a4d1b>] mnt_want_write+0x44/0xb5
> [ 15.668000] to [<ffffffff802a1dc8>] __mnt_is_readonly+0x0/0x1e
> [ 15.668000] Stack: ffff8100045fde08 ffffffff802a4d20 ffff8100045fddf8 0000000000000000
> [ 15.668000] 00000000fffffff7 ffff810005243140 ffff8100045fdf28 ffffffff802ad288
> [ 15.668000] ffff8100045fde58 0000000000000202 ffff8100045fde58 ffffffff8035437b
> [ 15.668000] Call Trace:
> [ 15.668000] [<ffffffff802a4d20>] mnt_want_write+0x49/0xb5
> [ 15.668000] [<ffffffff802ad288>] do_utimes+0xd0/0x220
> [ 15.668000] [<ffffffff8035437b>] __up_read+0x7a/0x83
> [ 15.668000] [<ffffffff8024b1af>] up_read+0x9/0xb
> [ 15.668000] [<ffffffff8051977c>] do_page_fault+0x421/0x7d0
> [ 15.668000] [<ffffffff8028b370>] do_filp_open+0x36/0x46
> [ 15.668000] [<ffffffff802ad519>] sys_utimensat+0x8b/0xa5
> [ 15.668000] [<ffffffff80517a4d>] error_exit+0x0/0x84
> [ 15.668000] [<ffffffff8020c10e>] system_call+0x7e/0x83
> [ 15.668000]
> [ 15.668000]
> [ 15.668000] Code: f6 47 50 40 75 0d 48 8b 47 28 8a 40 58 83 e0 01 0f b6 c0 c9
> [ 15.668000] RIP [<ffffffff802a1dd1>] __mnt_is_readonly+0x9/0x1e
> [ 15.668000] RSP <ffff8100045fddd8>
> [ 15.668000] CR2: 0000000000000252
>
CC'ing Dave, he might be interested in looking into this. Do you know
which file was touched. I suspect either mnt or mnt_sb is NULL in
__mnt_is_readonly(). mnt is extracted from the nameidata structure.
It's interesting to see utimenstat in the stack, I suspect that
the filename was probably NULL and dfd was something other than
AT_FDCWD (Just a wild guess). I'll try to reproduce your problem.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
This patch:
- makes hidp_setup_input() return int to indicate errors;
- checks its return value to handle errors.
And this time it is against -rc7-mm1 tree.
Thanks to roel and Marcel Holtmann for comments.
Signed-off-by: WANG Cong <[email protected]>
---
net/bluetooth/hidp/core.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
Index: linux-2.6.23-rc7-mm1/net/bluetooth/hidp/core.c
===================================================================
--- linux-2.6.23-rc7-mm1.orig/net/bluetooth/hidp/core.c
+++ linux-2.6.23-rc7-mm1/net/bluetooth/hidp/core.c
@@ -625,7 +625,7 @@ static struct device *hidp_get_device(st
return conn ? &conn->dev : NULL;
}
-static inline void hidp_setup_input(struct hidp_session *session, struct hidp_connadd_req *req)
+static inline int hidp_setup_input(struct hidp_session *session, struct hidp_connadd_req *req)
{
struct input_dev *input = session->input;
int i;
@@ -669,7 +669,7 @@ static inline void hidp_setup_input(stru
input->event = hidp_input_event;
- input_register_device(input);
+ return input_register_device(input);
}
static int hidp_open(struct hid_device *hid)
@@ -822,8 +822,11 @@ int hidp_add_connection(struct hidp_conn
session->flags = req->flags & (1 << HIDP_BLUETOOTH_VENDOR_ID);
session->idle_to = req->idle_to;
- if (session->input)
- hidp_setup_input(session, req);
+ if (session->input) {
+ err = hidp_setup_input(session, req);
+ if (err < 0)
+ goto failed;
+ }
if (session->hid)
hidp_setup_hid(session, req);
Hi Andrew,
The kernel build fails with
CC arch/ia64/kernel/efi.o
arch/ia64/kernel/efi.c: In function 'efi_memmap_init':
arch/ia64/kernel/efi.c:1088: error: 'total_memory' undeclared (first use in this function)
arch/ia64/kernel/efi.c:1088: error: (Each undeclared identifier is reported only once
arch/ia64/kernel/efi.c:1088: error: for each function it appears in.)
make[1]: *** [arch/ia64/kernel/efi.o] Error 1
make: *** [arch/ia64/kernel] Error 2
The use-extended-crashkernel-command-line-on-ia64.patch uses total_mem and
return total_memory.
Signed-off-by: Kamalesh Babulal <[email protected]>
---
--- linux-2.6.23-rc7/arch/ia64/kernel/efi.c 2007-09-24 15:28:06.000000000 +0530
+++ linux-2.6.23-rc7/arch/ia64/kernel/~efi.c 2007-09-24 16:56:03.000000000 +0530
@@ -1085,7 +1085,7 @@ efi_memmap_init(unsigned long *s, unsign
*s = (u64)kern_memmap;
*e = (u64)++k;
- return total_memory;
+ return total_mem;
}
void
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
On Mon, Sep 24, 2007 at 06:35:50AM -0400, [email protected] wrote:
> On Mon, 24 Sep 2007 02:17:16 PDT, Andrew Morton said:
>
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>
> It lived fast, it died young, it didn't leave a pretty corpse...
>
> Something in the startup scripts did a 'touch', and ker-blam.
> [ 15.668000] Call Trace:
> [ 15.668000] [<ffffffff802a4d20>] mnt_want_write+0x49/0xb5
> [ 15.668000] [<ffffffff802ad288>] do_utimes+0xd0/0x220
> [ 15.668000] [<ffffffff8035437b>] __up_read+0x7a/0x83
> [ 15.668000] [<ffffffff8024b1af>] up_read+0x9/0xb
> [ 15.668000] [<ffffffff8051977c>] do_page_fault+0x421/0x7d0
> [ 15.668000] [<ffffffff8028b370>] do_filp_open+0x36/0x46
> [ 15.668000] [<ffffffff802ad519>] sys_utimensat+0x8b/0xa5
> [ 15.668000] [<ffffffff80517a4d>] error_exit+0x0/0x84
> [ 15.668000] [<ffffffff8020c10e>] system_call+0x7e/0x83
do_times passes an unitialized vfsmount into mnt_want_write. Here's
the quick fix (untested), but the right fix is to restructure the complete
mess do_utimes is (never let a libc developer write your kernel code.. :)):
Index: linux-2.6.23-rc6/fs/utimes.c
===================================================================
--- linux-2.6.23-rc6.orig/fs/utimes.c 2007-09-24 14:02:24.000000000 +0200
+++ linux-2.6.23-rc6/fs/utimes.c 2007-09-24 14:03:57.000000000 +0200
@@ -59,6 +59,7 @@ long do_utimes(int dfd, char __user *fil
struct inode *inode;
struct iattr newattrs;
struct file *f = NULL;
+ struct vfsmount *mnt;
error = -EINVAL;
if (times && (!nsec_valid(times[0].tv_nsec) ||
@@ -79,17 +80,19 @@ long do_utimes(int dfd, char __user *fil
if (!f)
goto out;
dentry = f->f_path.dentry;
+ mnt = f->f_path.mnt;
} else {
error = __user_walk_fd(dfd, filename, (flags & AT_SYMLINK_NOFOLLOW) ? 0 : LOOKUP_FOLLOW, &nd);
if (error)
goto out;
dentry = nd.dentry;
+ mnt = nd.mnt;
}
inode = dentry->d_inode;
- error = mnt_want_write(nd.mnt);
+ error = mnt_want_write(mnt);
if (error)
goto dput_and_out;
Getting compile errors on S390:
CC arch/s390/mm/cmm.o
arch/s390/mm/cmm.c: In function `cmm_init':
arch/s390/mm/cmm.c:431: error: implicit declaration of function
`register_oom_notifier'
arch/s390/mm/cmm.c:443: error: implicit declaration of function
`unregister_oom_notifier'
make[1]: *** [arch/s390/mm/cmm.o] Error 1
make: *** [arch/s390/mm] Error 2
-apw
On 09/24/2007 11:17 AM, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
Fine, but on some boots (I noticed this on rc6-mm1 too, but not before):
0000:00:1a.7 EHCI: BIOS handoff failed (BIOS bug ?) 01010001
0000:00:1d.7 EHCI: BIOS handoff failed (BIOS bug ?) 01010001
# lspci -vns 0000:00:1a.7
00:1a.7 0c03: 8086:293c (rev 02) (prog-if 20 [EHCI])
Subsystem: 8086:293c
Flags: bus master, medium devsel, latency 0, IRQ 19
Memory at ffa7b400 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port
Capabilities: [98] Vendor Specific Information
# lspci -vns 0000:00:1d.7
00:1d.7 0c03: 8086:293a (rev 02) (prog-if 20 [EHCI])
Subsystem: 8086:293a
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at ffa7b000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port
Capabilities: [98] Vendor Specific Information
regards,
--
Jiri Slaby ([email protected])
Faculty of Informatics, Masaryk University
Seeing the following from an older power LPAR, pretty sure we had
this in the previous -mm also:
Unable to handle kernel paging request for data at address 0x00000000
Faulting instruction address: 0xc000000000047ac8
cpu 0x0: Vector: 300 (Data Access) at [c00000000058f750]
pc: c000000000047ac8: .pSeries_log_error+0x364/0x420
lr: c000000000047a4c: .pSeries_log_error+0x2e8/0x420
sp: c00000000058f9d0
msr: 8000000000001032
dar: 0
dsisr: 42000000
current = 0xc0000000004a9b30
paca = 0xc0000000004aa700
pid = 0, comm = swapper
enter ? for help
[c00000000058faf0] c000000000021164 .rtas_call+0x200/0x250
[c00000000058fba0] c000000000049cd0 .early_enable_eeh+0x168/0x360
[c00000000058fc70] c00000000002f674 .traverse_pci_devices+0x8c/0x138
[c00000000058fd10] c000000000460ce8 .eeh_init+0x1a8/0x200
[c00000000058fdb0] c00000000045fb70 .pSeries_setup_arch+0x128/0x234
[c00000000058fe40] c00000000044f830 .setup_arch+0x214/0x24c
[c00000000058fee0] c000000000446a38 .start_kernel+0xd4/0x3e4
[c00000000058ff90] c000000000373194 .start_here_common+0x54/0x58
This machine is a:
processor : 0
cpu : POWER4+ (gq)
clock : 1703.965296MHz
revision : 19.0
[...]
timebase : 212995662
machine : CHRP IBM,7040-681
-apw
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c: In function `dasd_eckd_build_cp':
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1181: error: syntax error before "struct"
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: error: `iter' undeclared (first use in this function)
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: error: (Each undeclared identifier is reported only once
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: error: for each function it appears in.)
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: error: `bv' undeclared (first use in this function)
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: warning: left-hand operand of comma expression has no effect
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: warning: left-hand operand of comma expression has no effect
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1257: warning: left-hand operand of comma expression has no effect
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1257: warning: left-hand operand of comma expression has no effect
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: warning: statement with no effect
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: warning: statement with no effect
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1257: warning: statement with no effect
/home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1257: warning: statement with no effect
make[3]: *** [drivers/s390/block/dasd_eckd.o] Error 1
make[2]: *** [drivers/s390/block] Error 2
Signed-off-by: Cedric Le Goater <[email protected]>
---
drivers/s390/block/dasd_eckd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: 2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c
===================================================================
--- 2.6.23-rc7-mm1.orig/drivers/s390/block/dasd_eckd.c
+++ 2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c
@@ -1176,7 +1176,7 @@ dasd_eckd_build_cp(struct dasd_device *
struct LO_eckd_data *LO_data;
struct dasd_ccw_req *cqr;
struct ccw1 *ccw;
- struct req_iterator iter
+ struct req_iterator iter;
struct bio_vec *bv;
char *dst;
unsigned int blksize, blk_per_trk, off;
Andy Whitcroft wrote:
> Getting compile errors on S390:
>
> CC arch/s390/mm/cmm.o
> arch/s390/mm/cmm.c: In function `cmm_init':
> arch/s390/mm/cmm.c:431: error: implicit declaration of function
> `register_oom_notifier'
> arch/s390/mm/cmm.c:443: error: implicit declaration of function
> `unregister_oom_notifier'
> make[1]: *** [arch/s390/mm/cmm.o] Error 1
> make: *** [arch/s390/mm] Error 2
yes. It's from oom-move-prototypes-to-appropriate-header-file.patch.
I think this patch fixes it.
C.
Signed-off-by: Cedric Le Goater <[email protected]>
---
arch/s390/mm/cmm.c | 1 +
1 file changed, 1 insertion(+)
Index: 2.6.23-rc7-mm1/arch/s390/mm/cmm.c
===================================================================
--- 2.6.23-rc7-mm1.orig/arch/s390/mm/cmm.c
+++ 2.6.23-rc7-mm1/arch/s390/mm/cmm.c
@@ -17,6 +17,7 @@
#include <linux/ctype.h>
#include <linux/swap.h>
#include <linux/kthread.h>
+#include <linux/oom.h>
#include <asm/pgalloc.h>
#include <asm/uaccess.h>
Hi Andrew,
Kernel oops over x86_64 (AMD Opteron(tm) Processor 844)
Unable to handle kernel NULL pointer dereference at 0000000000000070 RIP:
[<ffffffff80290630>] fasync_helper+0x6b/0xe4
PGD 181949067 PUD 182228067 PMD 0
Oops: 0000 [1] SMP
last sysfs file: /devices/system/node/possible
CPU 3
Modules linked in:
Pid: 18156, comm: fcntl23 Not tainted 2.6.23-rc7-mm1-autokern1 #1
RIP: 0010:[<ffffffff80290630>] [<ffffffff80290630>] fasync_helper+0x6b/0xe4
RSP: 0000:ffff810082bdfdb8 EFLAGS: 00010046
RAX: 00000000fffffff4 RBX: ffff8101821a9000 RCX: 0000000000000000
RDX: ffff8101821a9000 RSI: ffff810180026900 RDI: ffffffff806286b8
RBP: ffff810082bdfde8 R08: 0000000000000002 R09: ffff81018072124b
R10: 0000000000000000 R11: 0000000000000002 R12: 0000000000000070
R13: 0000000000000001 R14: 0000000000000000 R15: ffff810181875cc0
FS: 0000000000000000(0000) GS:ffff810180721380(0063) knlGS:00000000556aa2a0
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 0000000000000070 CR3: 00000001818c4000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process fcntl23 (pid: 18156, threadinfo ffff810082bde000, task ffff810082309530)
last branch before last exception/interrupt
from [<ffffffff804ad9e0>] _write_lock_irq+0x14/0x15
to [<ffffffff80290630>] fasync_helper+0x6b/0xe4
Stack: 0000000400000004 0000000000000000 0000000000000000 ffff810181875cc0
0000000000000004 ffff810182b3d238 ffff810082bdfee8 ffffffff802939cc
ffff810082bdfe18 0000000000000000 0000000000000000 ffff810082bdfe10
Call Trace:
[<ffffffff802939cc>] fcntl_setlease+0x99/0x101
[<ffffffff80290370>] sys_fcntl+0x2a3/0x2ce
[<ffffffff802b14cf>] compat_sys_fcntl64+0x2ee/0x2ff
[<ffffffff80224292>] ia32_sysret+0x0/0xa
DWARF2 unwinder stuck at ia32_sysret+0x0/0xa
Leftover inexact backtrace:
Code: 49 8b 34 24 4c 89 e2 48 85 f6 74 2a 4c 39 7e 10 75 1a 45 85
RIP [<ffffffff80290630>] fasync_helper+0x6b/0xe4
RSP <ffff810082bdfdb8>
CR2: 0000000000000070
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
On Mon, 24 Sep 2007 13:05:08 BST, Christoph Hellwig said:
> On Mon, Sep 24, 2007 at 06:35:50AM -0400, [email protected] wrote:
> > On Mon, 24 Sep 2007 02:17:16 PDT, Andrew Morton said:
> >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
> >
> > It lived fast, it died young, it didn't leave a pretty corpse...
(adding Dave Hansen to the cc: list, his patch added the mnt_want_write stuff)
> do_times passes an unitialized vfsmount into mnt_want_write. Here's
> the quick fix (untested), but the right fix is to restructure the complete
> mess do_utimes is (never let a libc developer write your kernel code.. :)):
Close - it still blew up, as one reference to nd.mnt remained. Fixed patch
is appended - system boots all the way with this applied.
--- linux-2.6.23-rc7-mm1/fs/utimes.c.dist 2007-09-24 05:57:38.000000000 -0400
+++ linux-2.6.23-rc7-mm1/fs/utimes.c 2007-09-24 08:48:34.000000000 -0400
@@ -59,6 +59,7 @@ long do_utimes(int dfd, char __user *fil
struct inode *inode;
struct iattr newattrs;
struct file *f = NULL;
+ struct vfsmount *mnt;
error = -EINVAL;
if (times && (!nsec_valid(times[0].tv_nsec) ||
@@ -79,17 +80,19 @@ long do_utimes(int dfd, char __user *fil
if (!f)
goto out;
dentry = f->f_path.dentry;
+ mnt = f->f_path.mnt;
} else {
error = __user_walk_fd(dfd, filename, (flags & AT_SYMLINK_NOFOLLOW) ? 0 : LOOKUP_FOLLOW, &nd);
if (error)
goto out;
dentry = nd.dentry;
+ mnt = nd.mnt;
}
inode = dentry->d_inode;
- error = mnt_want_write(nd.mnt);
+ error = mnt_want_write(mnt);
if (error)
goto dput_and_out;
@@ -135,7 +138,7 @@ long do_utimes(int dfd, char __user *fil
error = notify_change(dentry, &newattrs);
mutex_unlock(&inode->i_mutex);
mnt_drop_write_and_out:
- mnt_drop_write(nd.mnt);
+ mnt_drop_write(mnt);
dput_and_out:
if (f)
fput(f);
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
I also get this compile error on s390. 'linux/scatterlist.h' has disappeared
from the #include pile but where ?
/home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c: In function `sctp_auth_calculate_hmac':
/home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c:695: error: storage size of 'sg' isn't known
/home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c:695: warning: unused variable `sg'
Cheers,
C.
putting Vlad in Cc:
Cedric Le Goater wrote:
> Andrew Morton wrote:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>
> I also get this compile error on s390. 'linux/scatterlist.h' has disappeared
> from the #include pile but where ?
>
> /home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c: In function `sctp_auth_calculate_hmac':
> /home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c:695: error: storage size of 'sg' isn't known
> /home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c:695: warning: unused variable `sg'
The following patch works of course but it seems to simplistic for s390.
Cheers,
C.
Signed-off-by: Cedric Le Goater <[email protected]>
---
net/sctp/auth.c | 1 +
1 file changed, 1 insertion(+)
Index: 2.6.23-rc7-mm1/net/sctp/auth.c
===================================================================
--- 2.6.23-rc7-mm1.orig/net/sctp/auth.c
+++ 2.6.23-rc7-mm1/net/sctp/auth.c
@@ -36,6 +36,7 @@
#include <linux/types.h>
#include <linux/crypto.h>
+#include <linux/scatterlist.h>
#include <net/sctp/sctp.h>
#include <net/sctp/auth.h>
Hi Andrew,
Kernel BUG over x86_64 (AMD Opteron(tm) Processor 844).
Similar kernel Bug was reported for 2.6.23-rc2-mm1
at http://lkml.org/lkml/2007/8/10/20 and the
mm-dirty-balancing-for-tasks.patch was dropped from 2.6.23-rc2-mm2.
And the same patch is in this -mm version, suspect whether is it the
same patch triggering this Bug.
BUG: soft lockup - CPU#0 stuck for 11s! [events/0:15]
CPU 0:
Modules linked in:
Pid: 15, comm: events/0 Tainted: G D 2.6.23-rc7-mm1-autokern1 #1
RIP: 0010:[<ffffffff8021be46>] [<ffffffff8021be46>] __smp_call_function_mask+0x9a/0xc4
RSP: 0000:ffff8100017add80 EFLAGS: 00000297
RAX: 00000000000000fc RBX: ffff8100017adde0 RCX: 0000000000000001
RDX: 00000000000008fc RSI: 00000000000000fc RDI: 000000000000000e
RBP: ffffc20002d11000 R08: ffff8100017ac000 R09: ffffffff80675e38
R10: 0000000000000000 R11: 0000000000000000 R12: 000000000000000f
R13: ffffffff8021bcfe R14: 0000000000000000 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffffffff8065a000(0000) knlGS:00000000556aa2a0
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: ffffc20002d11008 CR3: 0000000000201000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
Inexact backtrace:
[<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
[<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
[<ffffffff8021becf>] smp_call_function_mask+0x5f/0x72
[<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
[<ffffffff8021bf82>] smp_call_function+0x19/0x1b
[<ffffffff8023a773>] on_each_cpu+0x16/0x2b
[<ffffffff802158a2>] mcheck_timer+0x0/0x7c
[<ffffffff802158c0>] mcheck_timer+0x1e/0x7c
[<ffffffff802444b9>] run_workqueue+0x88/0x109
[<ffffffff8024453a>] worker_thread+0x0/0xf4
[<ffffffff80244623>] worker_thread+0xe9/0xf4
[<ffffffff8024841d>] autoremove_wake_function+0x0/0x37
[<ffffffff8024841d>] autoremove_wake_function+0x0/0x37
[<ffffffff80247e5c>] kthread+0x44/0x6d
[<ffffffff8020c5a8>] child_rip+0xa/0x12
[<ffffffff80247e18>] kthread+0x0/0x6d
[<ffffffff8020c59e>] child_rip+0x0/0x12
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
a.k.a. mm-use-pagevec-to-rotate-reclaimable-page-fix-2.patch
rotate_reclaimable_page() is not necessarily called with IRQ disabled:
it must do so when calling the helpfully commented pagevec_move_tail().
Hmm, if pagevec_move_tail() is assuming IRQ disabled, why should it
bother with irqsave/irqrestore variants of spin_lock? Because we like
to see them on lru_lock? But vmscan.c already has one bare spin_lock().
Signed-off-by: Hugh Dickins <[email protected]>
---
mm/swap.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
--- 2.6.23-rc7-mm1/mm/swap.c 2007-09-24 11:05:55.000000000 +0100
+++ linux/mm/swap.c 2007-09-24 13:08:12.000000000 +0100
@@ -102,7 +102,6 @@ static void pagevec_move_tail(struct pag
int i;
int pgmoved = 0;
struct zone *zone = NULL;
- unsigned long uninitialized_var(flags);
for (i = 0; i < pagevec_count(pvec); i++) {
struct page *page = pvec->pages[i];
@@ -110,9 +109,9 @@ static void pagevec_move_tail(struct pag
if (pagezone != zone) {
if (zone)
- spin_unlock_irqrestore(&zone->lru_lock, flags);
+ spin_unlock(&zone->lru_lock);
zone = pagezone;
- spin_lock_irqsave(&zone->lru_lock, flags);
+ spin_lock(&zone->lru_lock);
}
if (PageLRU(page) && !PageActive(page)) {
list_move_tail(&page->lru, &zone->inactive_list);
@@ -120,7 +119,7 @@ static void pagevec_move_tail(struct pag
}
}
if (zone)
- spin_unlock_irqrestore(&zone->lru_lock, flags);
+ spin_unlock(&zone->lru_lock);
__count_vm_events(PGROTATED, pgmoved);
release_pages(pvec->pages, pvec->nr, pvec->cold);
pagevec_reinit(pvec);
@@ -150,6 +149,7 @@ void move_tail_pages()
int rotate_reclaimable_page(struct page *page)
{
struct pagevec *pvec;
+ unsigned long flags;
if (PageLocked(page))
return 1;
@@ -162,9 +162,11 @@ int rotate_reclaimable_page(struct page
if (PageLRU(page) && !PageActive(page)) {
page_cache_get(page);
+ local_irq_save(flags);
pvec = &__get_cpu_var(rotate_pvecs);
if (!pagevec_add(pvec, page))
pagevec_move_tail(pvec);
+ local_irq_restore(flags);
}
if (!test_clear_page_writeback(page))
BUG();
Please, try with this patch too:
diff --git a/fs/locks.c b/fs/locks.c
index c0fe71a..f599508 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -1423,7 +1423,7 @@ int generic_setlease(struct file *filp,
locks_copy_lock(new_fl, lease);
locks_insert_lock(before, new_fl);
- *flp = fl;
+ *flp = new_fl;
return 0;
out:
Pavel Emelyanov wrote:
> Please, try with this patch too:
>
> diff --git a/fs/locks.c b/fs/locks.c
> index c0fe71a..f599508 100644
> --- a/fs/locks.c
> +++ b/fs/locks.c
> @@ -1423,7 +1423,7 @@ int generic_setlease(struct file *filp,
> locks_copy_lock(new_fl, lease);
> locks_insert_lock(before, new_fl);
>
> - *flp = fl;
> + *flp = new_fl;
> return 0;
>
> out:
>
Hi, Pavel,
You did not signoff on the patch.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
Cedric Le Goater wrote:
> putting Vlad in Cc:
>
> Cedric Le Goater wrote:
>> Andrew Morton wrote:
>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>> I also get this compile error on s390. 'linux/scatterlist.h' has disappeared
>> from the #include pile but where ?
>>
>> /home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c: In function `sctp_auth_calculate_hmac':
>> /home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c:695: error: storage size of 'sg' isn't known
>> /home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c:695: warning: unused variable `sg'
>
> The following patch works of course but it seems to simplistic for s390.
Odd that it didn't show up on x86 or ia64, but simple enough.
ACK.
-vlad
>
> Cheers,
>
> C.
>
>
> Signed-off-by: Cedric Le Goater <[email protected]>
> ---
> net/sctp/auth.c | 1 +
> 1 file changed, 1 insertion(+)
>
> Index: 2.6.23-rc7-mm1/net/sctp/auth.c
> ===================================================================
> --- 2.6.23-rc7-mm1.orig/net/sctp/auth.c
> +++ 2.6.23-rc7-mm1/net/sctp/auth.c
> @@ -36,6 +36,7 @@
>
> #include <linux/types.h>
> #include <linux/crypto.h>
> +#include <linux/scatterlist.h>
> #include <net/sctp/sctp.h>
> #include <net/sctp/auth.h>
>
On Mon, 24 Sep 2007, Jiri Slaby wrote:
> On 09/24/2007 11:17 AM, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>
> Fine, but on some boots (I noticed this on rc6-mm1 too, but not before):
> 0000:00:1a.7 EHCI: BIOS handoff failed (BIOS bug ?) 01010001
> 0000:00:1d.7 EHCI: BIOS handoff failed (BIOS bug ?) 01010001
Any changes in your BIOS setup?
What about with vanilla 2.6.23-rc6? Or vanilla 2.6.23-rc7?
The USB part of the code here hasn't changed in quite a while. Any
difference in behavior must be the result of changes in some other part
of the kernel. Possibly ACPI.
This might be a good job for git-bisect.
Alan Stern
On 24/09/2007 7:17 PM, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>
> - New git tree git-powerpc-galak.patch added to the -mm lineup: ppc32
> things, mainly (Kumar Gala <[email protected]>)
I'm observing a problem with this kernel (as well as 2.6.23-rc6-mm1) which
manifests itself only in my Postfix/application mail.logs:
Sep 25 00:25:40 tornado postfix/smtp[12520]: fatal: select lock: Cannot allocate
memory
Sep 25 00:25:41 tornado postfix/master[8002]: warning: process
/usr/lib64/postfix/smtp pid 12520 exit status 1
This is happening frequently with processes started via 'master' (smtp, smtpd
and cleanup), but it does not appear to have any noticeable operational impact
apart from logging a lot of copies of this message.
The corresponding code in Postfix which triggers this is (choice of 3 files in
src/master are all possibilities which all have much the same code)
/*
* The event loop, at last.
*/
while (var_use_limit == 0 || use_count < var_use_limit || client_count > 0) {
if (multi_server_lock != 0) {
watchdog_stop(watchdog);
if (myflock(vstream_fileno(multi_server_lock), INTERNAL_LOCK,
MYFLOCK_OP_EXCLUSIVE) < 0)
msg_fatal("select lock: %m");
}
watchdog_start(watchdog);
delay = loop ? loop(multi_server_name, multi_server_argv) : -1;
event_loop(delay);
}
multi_server_exit();
}
Now I'm not convinced this is an application problem, because I'm only seeing
this after running up kernel 2.6.23-rc6-mm1 or 2.6.23-rc7-mm1 and with NO
changes to the application itself. Using the same application binaries it does
not occur with 2.6.22 mainline. [I didn't get a lot of testing with the -mm
release prior to that unfortunately due to some other breakage.]
Is there anything new in the last two or so -mm kernels which could have caused
this?
I've put my .config up at http://www.reub.net/files/kernel/2.6.23-rc7-mm1.config
Thanks,
Reuben
There isn't a total_memory identifier within this function's scope. The
patch was compile/link tested.
Signed-off-by: Bob Picco <[email protected]>
arch/ia64/kernel/efi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.23-rc7-mm1/arch/ia64/kernel/efi.c
===================================================================
--- linux-2.6.23-rc7-mm1.orig/arch/ia64/kernel/efi.c 2007-09-24 09:54:40.000000000 -0400
+++ linux-2.6.23-rc7-mm1/arch/ia64/kernel/efi.c 2007-09-24 10:50:51.000000000 -0400
@@ -1085,7 +1085,7 @@ efi_memmap_init(unsigned long *s, unsign
*s = (u64)kern_memmap;
*e = (u64)++k;
- return total_memory;
+ return total_mem;
}
void
Balbir Singh wrote:
> Pavel Emelyanov wrote:
>> Please, try with this patch too:
>>
>> diff --git a/fs/locks.c b/fs/locks.c
>> index c0fe71a..f599508 100644
>> --- a/fs/locks.c
>> +++ b/fs/locks.c
>> @@ -1423,7 +1423,7 @@ int generic_setlease(struct file *filp,
>> locks_copy_lock(new_fl, lease);
>> locks_insert_lock(before, new_fl);
>>
>> - *flp = fl;
>> + *flp = new_fl;
>> return 0;
>>
>> out:
>>
>
> Hi, Pavel,
>
> You did not signoff on the patch.
I did not, but this is just a patch to test. I know, that it
most likely fixes the problem, but since Kamalesh didn't tell
us how he had triggered it, I'd like him to Ack it :)
Thanks,
Pavel
On Mon, 2007-09-24 at 08:58 -0400, [email protected] wrote:
> > do_times passes an unitialized vfsmount into mnt_want_write. Here's
> > the quick fix (untested), but the right fix is to restructure the complete
> > mess do_utimes is (never let a libc developer write your kernel code.. :)):
>
> Close - it still blew up, as one reference to nd.mnt remained. Fixed patch
> is appended - system boots all the way with this applied.
Any idea which fs and distro this was? I'd like to add it to my tests.
-- Dave
On Mon, 24 Sep 2007 08:45:32 PDT, Dave Hansen said:
> Any idea which fs and distro this was? I'd like to add it to my tests.
initscripts-8.56-1, from Fedora Rawhide, /etc/rc.sysinit, line 325:
touch /dev/.in_sysinit >/dev/null 2>&1
Specific enough? :)
Pavel Emelyanov wrote:
> Balbir Singh wrote:
>> Pavel Emelyanov wrote:
>>> Please, try with this patch too:
>>>
>>> diff --git a/fs/locks.c b/fs/locks.c
>>> index c0fe71a..f599508 100644
>>> --- a/fs/locks.c
>>> +++ b/fs/locks.c
>>> @@ -1423,7 +1423,7 @@ int generic_setlease(struct file *filp,
>>> locks_copy_lock(new_fl, lease);
>>> locks_insert_lock(before, new_fl);
>>>
>>> - *flp = fl;
>>> + *flp = new_fl;
>>> return 0;
>>>
>>> out:
>>>
>> Hi, Pavel,
>>
>> You did not signoff on the patch.
>
> I did not, but this is just a patch to test. I know, that it
> most likely fixes the problem, but since Kamalesh didn't tell
> us how he had triggered it, I'd like him to Ack it :)
>
> Thanks,
> Pavel
>
>
Ok, just wanted to let you know in case you missed it out.
In case Andrew picked it up. That's all!
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
On Mon, 24 Sep 2007 18:43:33 +0530 Kamalesh Babulal <[email protected]> wrote:
> Hi Andrew,
>
> Kernel BUG over x86_64 (AMD Opteron(tm) Processor 844).
>
> Similar kernel Bug was reported for 2.6.23-rc2-mm1
> at http://lkml.org/lkml/2007/8/10/20 and the
> mm-dirty-balancing-for-tasks.patch was dropped from 2.6.23-rc2-mm2.
> And the same patch is in this -mm version, suspect whether is it the
> same patch triggering this Bug.
>
> BUG: soft lockup - CPU#0 stuck for 11s! [events/0:15]
> CPU 0:
> Modules linked in:
> Pid: 15, comm: events/0 Tainted: G D 2.6.23-rc7-mm1-autokern1 #1
> RIP: 0010:[<ffffffff8021be46>] [<ffffffff8021be46>] __smp_call_function_mask+0x9a/0xc4
> RSP: 0000:ffff8100017add80 EFLAGS: 00000297
> RAX: 00000000000000fc RBX: ffff8100017adde0 RCX: 0000000000000001
> RDX: 00000000000008fc RSI: 00000000000000fc RDI: 000000000000000e
> RBP: ffffc20002d11000 R08: ffff8100017ac000 R09: ffffffff80675e38
> R10: 0000000000000000 R11: 0000000000000000 R12: 000000000000000f
> R13: ffffffff8021bcfe R14: 0000000000000000 R15: 0000000000000001
> FS: 0000000000000000(0000) GS:ffffffff8065a000(0000) knlGS:00000000556aa2a0
> CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> CR2: ffffc20002d11008 CR3: 0000000000201000 CR4: 00000000000006e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>
> Call Trace:
> Inexact backtrace:
> [<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
> [<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
> [<ffffffff8021becf>] smp_call_function_mask+0x5f/0x72
> [<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
> [<ffffffff8021bf82>] smp_call_function+0x19/0x1b
> [<ffffffff8023a773>] on_each_cpu+0x16/0x2b
> [<ffffffff802158a2>] mcheck_timer+0x0/0x7c
> [<ffffffff802158c0>] mcheck_timer+0x1e/0x7c
> [<ffffffff802444b9>] run_workqueue+0x88/0x109
> [<ffffffff8024453a>] worker_thread+0x0/0xf4
> [<ffffffff80244623>] worker_thread+0xe9/0xf4
> [<ffffffff8024841d>] autoremove_wake_function+0x0/0x37
> [<ffffffff8024841d>] autoremove_wake_function+0x0/0x37
> [<ffffffff80247e5c>] kthread+0x44/0x6d
> [<ffffffff8020c5a8>] child_rip+0xa/0x12
> [<ffffffff80247e18>] kthread+0x0/0x6d
> [<ffffffff8020c59e>] child_rip+0x0/0x12
hm, I thought we'd fixed the problems in that patchset. Peter, were
you aware of this one?
On Mon, Sep 24 2007, Cedric Le Goater wrote:
> Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>
> /home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c: In function `dasd_eckd_build_cp':
> /home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1181: error: syntax error before "struct"
> /home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: error: `iter' undeclared (first use in this function)
> /home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: error: (Each undeclared identifier is reported only once
> /home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: error: for each function it appears in.)
> /home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: error: `bv' undeclared (first use in this function)
> /home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: warning: left-hand operand of comma expression has no effect
> /home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: warning: left-hand operand of comma expression has no effect
> /home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1257: warning: left-hand operand of comma expression has no effect
> /home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1257: warning: left-hand operand of comma expression has no effect
> /home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: warning: statement with no effect
> /home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1209: warning: statement with no effect
> /home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1257: warning: statement with no effect
> /home/clg/linux/2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c:1257: warning: statement with no effect
> make[3]: *** [drivers/s390/block/dasd_eckd.o] Error 1
> make[2]: *** [drivers/s390/block] Error 2
>
> Signed-off-by: Cedric Le Goater <[email protected]>
> ---
> drivers/s390/block/dasd_eckd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: 2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c
> ===================================================================
> --- 2.6.23-rc7-mm1.orig/drivers/s390/block/dasd_eckd.c
> +++ 2.6.23-rc7-mm1/drivers/s390/block/dasd_eckd.c
> @@ -1176,7 +1176,7 @@ dasd_eckd_build_cp(struct dasd_device *
> struct LO_eckd_data *LO_data;
> struct dasd_ccw_req *cqr;
> struct ccw1 *ccw;
> - struct req_iterator iter
> + struct req_iterator iter;
> struct bio_vec *bv;
> char *dst;
> unsigned int blksize, blk_per_trk, off;
Oops, looks like neither Neil nor I cross compiled this on s390. Thanks,
I'll apply it.
--
Jens Axboe
On Mon, Sep 24 2007, Cedric Le Goater wrote:
> putting Vlad in Cc:
>
> Cedric Le Goater wrote:
> > Andrew Morton wrote:
> >> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
> >
> > I also get this compile error on s390. 'linux/scatterlist.h' has disappeared
> > from the #include pile but where ?
> >
> > /home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c: In function `sctp_auth_calculate_hmac':
> > /home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c:695: error: storage size of 'sg' isn't known
> > /home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c:695: warning: unused variable `sg'
>
> The following patch works of course but it seems to simplistic for s390.
>
> Cheers,
>
> C.
>
>
> Signed-off-by: Cedric Le Goater <[email protected]>
> ---
> net/sctp/auth.c | 1 +
> 1 file changed, 1 insertion(+)
>
> Index: 2.6.23-rc7-mm1/net/sctp/auth.c
> ===================================================================
> --- 2.6.23-rc7-mm1.orig/net/sctp/auth.c
> +++ 2.6.23-rc7-mm1/net/sctp/auth.c
> @@ -36,6 +36,7 @@
>
> #include <linux/types.h>
> #include <linux/crypto.h>
> +#include <linux/scatterlist.h>
> #include <net/sctp/sctp.h>
> #include <net/sctp/auth.h>
Thanks, applied.
--
Jens Axboe
On Mon, Sep 24 2007, Vlad Yasevich wrote:
> Cedric Le Goater wrote:
> > putting Vlad in Cc:
> >
> > Cedric Le Goater wrote:
> >> Andrew Morton wrote:
> >>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
> >> I also get this compile error on s390. 'linux/scatterlist.h' has disappeared
> >> from the #include pile but where ?
> >>
> >> /home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c: In function `sctp_auth_calculate_hmac':
> >> /home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c:695: error: storage size of 'sg' isn't known
> >> /home/clg/linux/2.6.23-rc7-mm1/net/sctp/auth.c:695: warning: unused variable `sg'
> >
> > The following patch works of course but it seems to simplistic for s390.
>
> Odd that it didn't show up on x86 or ia64, but simple enough.
Most likely those archs end up pulling in scatterlist.h through some
other maze of includes.
--
Jens Axboe
On Mon, 24 Sep 2007 09:44:48 -0700 Andrew Morton
<[email protected]> wrote:
> On Mon, 24 Sep 2007 18:43:33 +0530 Kamalesh Babulal <[email protected]> wrote:
>
> > Hi Andrew,
> >
> > Kernel BUG over x86_64 (AMD Opteron(tm) Processor 844).
> >
> > Similar kernel Bug was reported for 2.6.23-rc2-mm1
> > at http://lkml.org/lkml/2007/8/10/20 and the
> > mm-dirty-balancing-for-tasks.patch was dropped from 2.6.23-rc2-mm2.
> > And the same patch is in this -mm version, suspect whether is it the
> > same patch triggering this Bug.
> >
> > BUG: soft lockup - CPU#0 stuck for 11s! [events/0:15]
> > CPU 0:
> > Modules linked in:
> > Pid: 15, comm: events/0 Tainted: G D 2.6.23-rc7-mm1-autokern1 #1
> > RIP: 0010:[<ffffffff8021be46>] [<ffffffff8021be46>] __smp_call_function_mask+0x9a/0xc4
> > RSP: 0000:ffff8100017add80 EFLAGS: 00000297
> > RAX: 00000000000000fc RBX: ffff8100017adde0 RCX: 0000000000000001
> > RDX: 00000000000008fc RSI: 00000000000000fc RDI: 000000000000000e
> > RBP: ffffc20002d11000 R08: ffff8100017ac000 R09: ffffffff80675e38
> > R10: 0000000000000000 R11: 0000000000000000 R12: 000000000000000f
> > R13: ffffffff8021bcfe R14: 0000000000000000 R15: 0000000000000001
> > FS: 0000000000000000(0000) GS:ffffffff8065a000(0000) knlGS:00000000556aa2a0
> > CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> > CR2: ffffc20002d11008 CR3: 0000000000201000 CR4: 00000000000006e0
> > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> >
> > Call Trace:
> > Inexact backtrace:
> > [<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
> > [<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
> > [<ffffffff8021becf>] smp_call_function_mask+0x5f/0x72
> > [<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
> > [<ffffffff8021bf82>] smp_call_function+0x19/0x1b
> > [<ffffffff8023a773>] on_each_cpu+0x16/0x2b
> > [<ffffffff802158a2>] mcheck_timer+0x0/0x7c
> > [<ffffffff802158c0>] mcheck_timer+0x1e/0x7c
> > [<ffffffff802444b9>] run_workqueue+0x88/0x109
> > [<ffffffff8024453a>] worker_thread+0x0/0xf4
> > [<ffffffff80244623>] worker_thread+0xe9/0xf4
> > [<ffffffff8024841d>] autoremove_wake_function+0x0/0x37
> > [<ffffffff8024841d>] autoremove_wake_function+0x0/0x37
> > [<ffffffff80247e5c>] kthread+0x44/0x6d
> > [<ffffffff8020c5a8>] child_rip+0xa/0x12
> > [<ffffffff80247e18>] kthread+0x0/0x6d
> > [<ffffffff8020c59e>] child_rip+0x0/0x12
>
> hm, I thought we'd fixed the problems in that patchset. Peter, were
> you aware of this one?
Nope, and the stacktrace is utterly puzzling.
/me goes read the lkml.org link
Kamalesh Babulal: do you still get:
BUG: spinlock bad magic on
msgs?
Because those I could reproduce using fsx, and I fixed all that.
On Tue, 25 Sep 2007 00:52:30 +1000 Reuben Farrelly <[email protected]> wrote:
>
>
> On 24/09/2007 7:17 PM, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
> >
> > - New git tree git-powerpc-galak.patch added to the -mm lineup: ppc32
> > things, mainly (Kumar Gala <[email protected]>)
>
> I'm observing a problem with this kernel (as well as 2.6.23-rc6-mm1) which
> manifests itself only in my Postfix/application mail.logs:
>
> Sep 25 00:25:40 tornado postfix/smtp[12520]: fatal: select lock: Cannot allocate
> memory
> Sep 25 00:25:41 tornado postfix/master[8002]: warning: process
> /usr/lib64/postfix/smtp pid 12520 exit status 1
>
> This is happening frequently with processes started via 'master' (smtp, smtpd
> and cleanup), but it does not appear to have any noticeable operational impact
> apart from logging a lot of copies of this message.
>
> The corresponding code in Postfix which triggers this is (choice of 3 files in
> src/master are all possibilities which all have much the same code)
>
> /*
> * The event loop, at last.
> */
> while (var_use_limit == 0 || use_count < var_use_limit || client_count > 0) {
> if (multi_server_lock != 0) {
> watchdog_stop(watchdog);
> if (myflock(vstream_fileno(multi_server_lock), INTERNAL_LOCK,
> MYFLOCK_OP_EXCLUSIVE) < 0)
> msg_fatal("select lock: %m");
> }
> watchdog_start(watchdog);
> delay = loop ? loop(multi_server_name, multi_server_argv) : -1;
> event_loop(delay);
> }
> multi_server_exit();
> }
>
>
> Now I'm not convinced this is an application problem, because I'm only seeing
> this after running up kernel 2.6.23-rc6-mm1 or 2.6.23-rc7-mm1 and with NO
> changes to the application itself. Using the same application binaries it does
> not occur with 2.6.22 mainline. [I didn't get a lot of testing with the -mm
> release prior to that unfortunately due to some other breakage.]
>
> Is there anything new in the last two or so -mm kernels which could have caused
> this?
>
> I've put my .config up at http://www.reub.net/files/kernel/2.6.23-rc7-mm1.config
ug.
Lots of people have been futzing with the fs/locks.c code:
cleanup-macros-for-distinguishing-mandatory-locks.patch
fix-potential-oops-in-generic_setlease-v2.patch
fix-potential-oops-in-generic_setlease.patch
fs-locksc-use-list_for_each_entry-instead-of-list_for_each.patch
git-nfs.patch
git-nfsd.pc
rework-proc-locks-via-seq_files-and-seq_list-helpers-fix-2.patch
rework-proc-locks-via-seq_files-and-seq_list-helpers.patch
slab-api-remove-useless-ctor-parameter-and-reorder-parameters.patch
Peter Zijlstra wrote:
> On Mon, 24 Sep 2007 09:44:48 -0700 Andrew Morton
> <[email protected]> wrote:
>
>> On Mon, 24 Sep 2007 18:43:33 +0530 Kamalesh Babulal <[email protected]> wrote:
>>
>>> Hi Andrew,
>>>
>>> Kernel BUG over x86_64 (AMD Opteron(tm) Processor 844).
>>>
>>> Similar kernel Bug was reported for 2.6.23-rc2-mm1
>>> at http://lkml.org/lkml/2007/8/10/20 and the
>>> mm-dirty-balancing-for-tasks.patch was dropped from 2.6.23-rc2-mm2.
>>> And the same patch is in this -mm version, suspect whether is it the
>>> same patch triggering this Bug.
>>>
>>> BUG: soft lockup - CPU#0 stuck for 11s! [events/0:15]
>>> CPU 0:
>>> Modules linked in:
>>> Pid: 15, comm: events/0 Tainted: G D 2.6.23-rc7-mm1-autokern1 #1
>>> RIP: 0010:[<ffffffff8021be46>] [<ffffffff8021be46>] __smp_call_function_mask+0x9a/0xc4
>>> RSP: 0000:ffff8100017add80 EFLAGS: 00000297
>>> RAX: 00000000000000fc RBX: ffff8100017adde0 RCX: 0000000000000001
>>> RDX: 00000000000008fc RSI: 00000000000000fc RDI: 000000000000000e
>>> RBP: ffffc20002d11000 R08: ffff8100017ac000 R09: ffffffff80675e38
>>> R10: 0000000000000000 R11: 0000000000000000 R12: 000000000000000f
>>> R13: ffffffff8021bcfe R14: 0000000000000000 R15: 0000000000000001
>>> FS: 0000000000000000(0000) GS:ffffffff8065a000(0000) knlGS:00000000556aa2a0
>>> CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
>>> CR2: ffffc20002d11008 CR3: 0000000000201000 CR4: 00000000000006e0
>>> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>>> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>>>
>>> Call Trace:
>>> Inexact backtrace:
>>> [<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
>>> [<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
>>> [<ffffffff8021becf>] smp_call_function_mask+0x5f/0x72
>>> [<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
>>> [<ffffffff8021bf82>] smp_call_function+0x19/0x1b
>>> [<ffffffff8023a773>] on_each_cpu+0x16/0x2b
>>> [<ffffffff802158a2>] mcheck_timer+0x0/0x7c
>>> [<ffffffff802158c0>] mcheck_timer+0x1e/0x7c
>>> [<ffffffff802444b9>] run_workqueue+0x88/0x109
>>> [<ffffffff8024453a>] worker_thread+0x0/0xf4
>>> [<ffffffff80244623>] worker_thread+0xe9/0xf4
>>> [<ffffffff8024841d>] autoremove_wake_function+0x0/0x37
>>> [<ffffffff8024841d>] autoremove_wake_function+0x0/0x37
>>> [<ffffffff80247e5c>] kthread+0x44/0x6d
>>> [<ffffffff8020c5a8>] child_rip+0xa/0x12
>>> [<ffffffff80247e18>] kthread+0x0/0x6d
>>> [<ffffffff8020c59e>] child_rip+0x0/0x12
>> hm, I thought we'd fixed the problems in that patchset. Peter, were
>> you aware of this one?
>
> Nope, and the stacktrace is utterly puzzling.
>
> /me goes read the lkml.org link
>
> Kamalesh Babulal: do you still get:
> BUG: spinlock bad magic on
>
> msgs?
>
> Because those I could reproduce using fsx, and I fixed all that.
Hi Peter,
I do not get BUG: spinlock bad magic messages any more, but the softlock message is
thrown more than 30 time, while running the ltp runall.
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
On Mon, Sep 24, 2007 at 09:59:29AM -0700, Andrew Morton wrote:
> On Tue, 25 Sep 2007 00:52:30 +1000 Reuben Farrelly <[email protected]> wrote:
>
> >
> >
> > On 24/09/2007 7:17 PM, Andrew Morton wrote:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
> > >
> > > - New git tree git-powerpc-galak.patch added to the -mm lineup: ppc32
> > > things, mainly (Kumar Gala <[email protected]>)
> >
> > I'm observing a problem with this kernel (as well as 2.6.23-rc6-mm1) which
> > manifests itself only in my Postfix/application mail.logs:
> >
> > Sep 25 00:25:40 tornado postfix/smtp[12520]: fatal: select lock: Cannot allocate
> > memory
> > Sep 25 00:25:41 tornado postfix/master[8002]: warning: process
> > /usr/lib64/postfix/smtp pid 12520 exit status 1
> >
> > This is happening frequently with processes started via 'master' (smtp, smtpd
> > and cleanup), but it does not appear to have any noticeable operational impact
> > apart from logging a lot of copies of this message.
> >
> > The corresponding code in Postfix which triggers this is (choice of 3 files in
> > src/master are all possibilities which all have much the same code)
Oog. Looks like it's the "Memory shortage can result in inconsistent
flocks state" patch--the error variable is being set in some cases when
it shouldn't be. Does the following fix it?
That's in my git tree, not in mainline. I'll fix up my copy.
And I'll spend some time today figuring out what to do about regression
testing for the posix lock, flock, and lease code.
Thanks for the bug report!
--b.
diff --git a/fs/locks.c b/fs/locks.c
index a6c5917..3e8bfd2 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -740,6 +740,7 @@ static int flock_lock_file(struct file *filp, struct file_lock *request)
new_fl = locks_alloc_lock();
if (new_fl == NULL)
goto out;
+ error = 0;
}
for_each_lock(inode, before) {
On 09/24/2007 04:41 PM, Alan Stern wrote:
> On Mon, 24 Sep 2007, Jiri Slaby wrote:
>
>> On 09/24/2007 11:17 AM, Andrew Morton wrote:
>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>> Fine, but on some boots (I noticed this on rc6-mm1 too, but not before):
>> 0000:00:1a.7 EHCI: BIOS handoff failed (BIOS bug ?) 01010001
>> 0000:00:1d.7 EHCI: BIOS handoff failed (BIOS bug ?) 01010001
>
> Any changes in your BIOS setup?
unlikely, but still possible -- I've made some changes in BIOS recently when I
looking backwards. Which concrete changes would turn it in such behaviour?
> What about with vanilla 2.6.23-rc6? Or vanilla 2.6.23-rc7?
>
> The USB part of the code here hasn't changed in quite a while. Any
> difference in behavior must be the result of changes in some other part
> of the kernel. Possibly ACPI.
>
> This might be a good job for git-bisect.
Ok, I'll play with that little bit.
thanks,
--
Jiri Slaby ([email protected])
Faculty of Informatics, Masaryk University
On Mon, 24 Sep 2007, Jiri Slaby wrote:
> On 09/24/2007 04:41 PM, Alan Stern wrote:
> > On Mon, 24 Sep 2007, Jiri Slaby wrote:
> >
> >> On 09/24/2007 11:17 AM, Andrew Morton wrote:
> >>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
> >> Fine, but on some boots (I noticed this on rc6-mm1 too, but not before):
> >> 0000:00:1a.7 EHCI: BIOS handoff failed (BIOS bug ?) 01010001
> >> 0000:00:1d.7 EHCI: BIOS handoff failed (BIOS bug ?) 01010001
> >
> > Any changes in your BIOS setup?
>
> unlikely, but still possible -- I've made some changes in BIOS recently when I
> looking backwards. Which concrete changes would turn it in such behaviour?
USB Legacy Support is about the only change which springs to mind. But
who knows... A buggy BIOS could do almost anything.
Alan Stern
On 9/24/07, Andrew Morton <[email protected]> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
With the five hotfixes applied it works for me.
But it fails to power down my system when shutting down.
It prints twice 'System halted' and blinks the keyboard leds, but does
not switch off. On all other kernel version I only see one keyboard
blink before the power goes out.
I compared its dmesg to vanilla-rc7 and -rc4-mm1, but expect that rc-4
assigns different IRQs I can't see any differences except the normal
variation in BogoMips etc.
As the system still responded to SysRq I got the following informations:
[ 415.770000] SysRq : Show Regs
[ 415.770000] CPU 3:
[ 415.780000] Modules linked in: radeon drm nfsd exportfs ipv6 tuner
tea5767 tda8290 tuner_simple mt20xx tvaudio msp3400 bttv video_buf
ir_common compat_ioctl32 btcx_risc tveeprom videodev v4l2_common
v4l1_compat pata_amd usbhid hid sg
[ 415.780000] Pid: 0, comm: swapper Not tainted 2.6.23-rc7-mm1 #1
[ 415.780000] RIP: 0010:[<ffffffff8020ac79>] [<ffffffff8020ac79>]
default_idle+0x29/0x40
[ 415.780000] RSP: 0018:ffff81010038bf30 EFLAGS: 00000246
[ 415.780000] RAX: 0000000000000400 RBX: ffffffff80810040 RCX: 0000000000000000
[ 415.780000] RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000005
[ 415.780000] RBP: 0000000000030400 R08: 0000000000000000 R09: ffff81010038be68
[ 415.950000] R10: 000000000100002c R11: ffffffff80219be0 R12: 0000000000000000
[ 415.950000] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 415.950000] FS: 00007f35c69726f0(0000) GS:ffff810100319700(0000)
knlGS:0000000000000000
[ 415.950000] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
[ 415.950000] CR2: 00007fe432928c40 CR3: 0000000000201000 CR4: 00000000000006e0
[ 416.070000] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 416.070000] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 416.070000]
[ 416.070000] Call Trace:
[ 416.070000] [<ffffffff8020acea>] cpu_idle+0x5a/0x90
[ 416.070000]
No blocked tasks were shown with SysRq+W.
Last lines before I used SysRq+B (That worked, a normal reboot started):
[ 450.780000] SysRq : Emergency Remount R/O
[ 450.790000] Emergency Remount complete
[ 453.650000] SysRq : Emergency Sync
[ 453.660000] Emergency Sync complete
[ 455.910000] SysRq : Power Off
[ 455.920000] md: stopping all md devices.
[ 455.930000] md: md1 still in use.
[ 456.940000] sd 8:0:1:0: [sdd] Synchronizing SCSI cache
[ 456.960000] sd 8:0:1:0: [sdd] Stopping disk
[ 457.480000] sd 2:0:0:0: [sdc] Synchronizing SCSI cache
[ 457.490000] sd 2:0:0:0: [sdc] Stopping disk
[ 457.500000] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 457.520000] sd 1:0:0:0: [sdb] Stopping disk
[ 457.530000] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 457.550000] sd 0:0:0:0: [sda] Stopping disk
[ 457.560000] Power down.
[ 479.090000] SysRq : Power Off
[ 479.100000] md: stopping all md devices.
[ 479.110000] md: md1 still in use.
[ 480.120000] sd 8:0:1:0: [sdd] Synchronizing SCSI cache
[ 480.140000] sd 8:0:1:0: [sdd] Stopping disk
[ 480.660000] sd 2:0:0:0: [sdc] Synchronizing SCSI cache
[ 480.670000] sd 2:0:0:0: [sdc] Stopping disk
[ 480.680000] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 480.700000] sd 1:0:0:0: [sdb] Stopping disk
[ 480.710000] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 480.730000] sd 0:0:0:0: [sda] Stopping disk
[ 480.740000] Power down.
[ 489.030000] SysRq : Resetting
Torsten
On 09/24/2007 09:06 PM, Alan Stern wrote:
> On Mon, 24 Sep 2007, Jiri Slaby wrote:
>
>> On 09/24/2007 04:41 PM, Alan Stern wrote:
>>> On Mon, 24 Sep 2007, Jiri Slaby wrote:
>>>
>>>> On 09/24/2007 11:17 AM, Andrew Morton wrote:
>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>>>> Fine, but on some boots (I noticed this on rc6-mm1 too, but not before):
>>>> 0000:00:1a.7 EHCI: BIOS handoff failed (BIOS bug ?) 01010001
>>>> 0000:00:1d.7 EHCI: BIOS handoff failed (BIOS bug ?) 01010001
>>> Any changes in your BIOS setup?
>> unlikely, but still possible -- I've made some changes in BIOS recently when I
>> looking backwards. Which concrete changes would turn it in such behaviour?
>
> USB Legacy Support is about the only change which springs to mind. But
> who knows... A buggy BIOS could do almost anything.
Hmm, I have usb legacy keyboard switched on because of grub and bios to allow me
typing.
I booted 23-rc7 4 times, and the latest -mm 3 times just now and can't reproduce
it, I just wonder by what is this conditioned.
regards,
--
Jiri Slaby ([email protected])
Faculty of Informatics, Masaryk University
On Mon, 24 Sep 2007 22:38:03 +0530 Kamalesh Babulal
<[email protected]> wrote:
> Peter Zijlstra wrote:
> > On Mon, 24 Sep 2007 09:44:48 -0700 Andrew Morton
> > <[email protected]> wrote:
> >
> >> On Mon, 24 Sep 2007 18:43:33 +0530 Kamalesh Babulal <[email protected]> wrote:
> >>
> >>> Hi Andrew,
> >>>
> >>> Kernel BUG over x86_64 (AMD Opteron(tm) Processor 844).
> >>>
> >>> Similar kernel Bug was reported for 2.6.23-rc2-mm1
> >>> at http://lkml.org/lkml/2007/8/10/20 and the
> >>> mm-dirty-balancing-for-tasks.patch was dropped from 2.6.23-rc2-mm2.
> >>> And the same patch is in this -mm version, suspect whether is it the
> >>> same patch triggering this Bug.
> >>>
> >>> BUG: soft lockup - CPU#0 stuck for 11s! [events/0:15]
> >>> CPU 0:
> >>> Modules linked in:
> >>> Pid: 15, comm: events/0 Tainted: G D 2.6.23-rc7-mm1-autokern1 #1
> >>> RIP: 0010:[<ffffffff8021be46>] [<ffffffff8021be46>] __smp_call_function_mask+0x9a/0xc4
> >>> RSP: 0000:ffff8100017add80 EFLAGS: 00000297
> >>> RAX: 00000000000000fc RBX: ffff8100017adde0 RCX: 0000000000000001
> >>> RDX: 00000000000008fc RSI: 00000000000000fc RDI: 000000000000000e
> >>> RBP: ffffc20002d11000 R08: ffff8100017ac000 R09: ffffffff80675e38
> >>> R10: 0000000000000000 R11: 0000000000000000 R12: 000000000000000f
> >>> R13: ffffffff8021bcfe R14: 0000000000000000 R15: 0000000000000001
> >>> FS: 0000000000000000(0000) GS:ffffffff8065a000(0000) knlGS:00000000556aa2a0
> >>> CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> >>> CR2: ffffc20002d11008 CR3: 0000000000201000 CR4: 00000000000006e0
> >>> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> >>> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> >>>
> >>> Call Trace:
> >>> Inexact backtrace:
> >>> [<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
> >>> [<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
> >>> [<ffffffff8021becf>] smp_call_function_mask+0x5f/0x72
> >>> [<ffffffff802157a4>] mcheck_check_cpu+0x0/0x31
> >>> [<ffffffff8021bf82>] smp_call_function+0x19/0x1b
> >>> [<ffffffff8023a773>] on_each_cpu+0x16/0x2b
> >>> [<ffffffff802158a2>] mcheck_timer+0x0/0x7c
> >>> [<ffffffff802158c0>] mcheck_timer+0x1e/0x7c
> >>> [<ffffffff802444b9>] run_workqueue+0x88/0x109
> >>> [<ffffffff8024453a>] worker_thread+0x0/0xf4
> >>> [<ffffffff80244623>] worker_thread+0xe9/0xf4
> >>> [<ffffffff8024841d>] autoremove_wake_function+0x0/0x37
> >>> [<ffffffff8024841d>] autoremove_wake_function+0x0/0x37
> >>> [<ffffffff80247e5c>] kthread+0x44/0x6d
> >>> [<ffffffff8020c5a8>] child_rip+0xa/0x12
> >>> [<ffffffff80247e18>] kthread+0x0/0x6d
> >>> [<ffffffff8020c59e>] child_rip+0x0/0x12
> >> hm, I thought we'd fixed the problems in that patchset. Peter, were
> >> you aware of this one?
> >
> > Nope, and the stacktrace is utterly puzzling.
> >
> > /me goes read the lkml.org link
> >
> > Kamalesh Babulal: do you still get:
> > BUG: spinlock bad magic on
> >
> > msgs?
> >
> > Because those I could reproduce using fsx, and I fixed all that.
> Hi Peter,
>
> I do not get BUG: spinlock bad magic messages any more, but the softlock message is
> thrown more than 30 time, while running the ltp runall.
It would be good to know what function on_each_cpu is executing, could
you try something like:
---
kernel/softirq.c | 5 +++++
kernel/softlockup.c | 7 +++++++
2 files changed, 12 insertions(+)
Index: linux-2.6/kernel/softirq.c
===================================================================
--- linux-2.6.orig/kernel/softirq.c
+++ linux-2.6/kernel/softirq.c
@@ -645,6 +645,8 @@ __init int spawn_ksoftirqd(void)
}
#ifdef CONFIG_SMP
+
+DEFINE_PER_CPU(void (*)(void *info), last_on_each_cpu);
/*
* Call a function on all processors
*/
@@ -653,6 +655,9 @@ int on_each_cpu(void (*func) (void *info
int ret = 0;
preempt_disable();
+
+ per_cpu(last_on_each_cpu, smp_processor_id()) = func;
+
ret = smp_call_function(func, info, retry, wait);
local_irq_disable();
func(info);
Index: linux-2.6/kernel/softlockup.c
===================================================================
--- linux-2.6.orig/kernel/softlockup.c
+++ linux-2.6/kernel/softlockup.c
@@ -15,6 +15,8 @@
#include <linux/notifier.h>
#include <linux/module.h>
#include <linux/kgdb.h>
+#include <linux/percpu.h>
+#include <linux/kallsyms.h>
#include <asm/irq_regs.h>
@@ -71,6 +73,8 @@ void touch_all_softlockup_watchdogs(void
}
EXPORT_SYMBOL(touch_all_softlockup_watchdogs);
+DECLARE_PER_CPU(void (*)(void *), last_on_each_cpu);
+
/*
* This callback runs from the timer interrupt, and checks
* whether the watchdog thread has hung or not:
@@ -122,6 +126,9 @@ void softlockup_tick(void)
printk(KERN_ERR "BUG: soft lockup - CPU#%d stuck for %lus! [%s:%d]\n",
this_cpu, now - touch_timestamp,
current->comm, task_pid_nr(current));
+ printk(KERN_ERR " last_on_each_cpu: [<%p>] ",
+ per_cpu(last_on_each_cpu, this_cpu));
+ print_symbol("%s\n", (unsigned long)per_cpu(last_on_each_cpu, this_cpu));
if (regs)
show_regs(regs);
else
On Mon, 24 Sep 2007 21:07:19 +0200
"Torsten Kaiser" <[email protected]> wrote:
> On 9/24/07, Andrew Morton <[email protected]> wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>
> With the five hotfixes applied it works for me.
>
> But it fails to power down my system when shutting down.
>
> It prints twice 'System halted' and blinks the keyboard leds, but does
> not switch off. On all other kernel version I only see one keyboard
> blink before the power goes out.
ok...
> I compared its dmesg to vanilla-rc7 and -rc4-mm1, but expect that rc-4
> assigns different IRQs I can't see any differences except the normal
> variation in BogoMips etc.
>
> As the system still responded to SysRq I got the following informations:
good move.
> [ 415.770000] SysRq : Show Regs
> [ 415.770000] CPU 3:
> [ 415.780000] Modules linked in: radeon drm nfsd exportfs ipv6 tuner
> tea5767 tda8290 tuner_simple mt20xx tvaudio msp3400 bttv video_buf
> ir_common compat_ioctl32 btcx_risc tveeprom videodev v4l2_common
> v4l1_compat pata_amd usbhid hid sg
> [ 415.780000] Pid: 0, comm: swapper Not tainted 2.6.23-rc7-mm1 #1
> [ 415.780000] RIP: 0010:[<ffffffff8020ac79>] [<ffffffff8020ac79>]
> default_idle+0x29/0x40
> [ 415.780000] RSP: 0018:ffff81010038bf30 EFLAGS: 00000246
> [ 415.780000] RAX: 0000000000000400 RBX: ffffffff80810040 RCX: 0000000000000000
> [ 415.780000] RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000005
> [ 415.780000] RBP: 0000000000030400 R08: 0000000000000000 R09: ffff81010038be68
> [ 415.950000] R10: 000000000100002c R11: ffffffff80219be0 R12: 0000000000000000
> [ 415.950000] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
> [ 415.950000] FS: 00007f35c69726f0(0000) GS:ffff810100319700(0000)
> knlGS:0000000000000000
> [ 415.950000] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> [ 415.950000] CR2: 00007fe432928c40 CR3: 0000000000201000 CR4: 00000000000006e0
> [ 416.070000] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ 416.070000] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [ 416.070000]
> [ 416.070000] Call Trace:
> [ 416.070000] [<ffffffff8020acea>] cpu_idle+0x5a/0x90
> [ 416.070000]
>
> No blocked tasks were shown with SysRq+W.
> Last lines before I used SysRq+B (That worked, a normal reboot started):
>
> [ 450.780000] SysRq : Emergency Remount R/O
> [ 450.790000] Emergency Remount complete
> [ 453.650000] SysRq : Emergency Sync
> [ 453.660000] Emergency Sync complete
> [ 455.910000] SysRq : Power Off
> [ 455.920000] md: stopping all md devices.
> [ 455.930000] md: md1 still in use.
> [ 456.940000] sd 8:0:1:0: [sdd] Synchronizing SCSI cache
> [ 456.960000] sd 8:0:1:0: [sdd] Stopping disk
> [ 457.480000] sd 2:0:0:0: [sdc] Synchronizing SCSI cache
> [ 457.490000] sd 2:0:0:0: [sdc] Stopping disk
> [ 457.500000] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
> [ 457.520000] sd 1:0:0:0: [sdb] Stopping disk
> [ 457.530000] sd 0:0:0:0: [sda] Synchronizing SCSI cache
> [ 457.550000] sd 0:0:0:0: [sda] Stopping disk
> [ 457.560000] Power down.
> [ 479.090000] SysRq : Power Off
> [ 479.100000] md: stopping all md devices.
> [ 479.110000] md: md1 still in use.
> [ 480.120000] sd 8:0:1:0: [sdd] Synchronizing SCSI cache
> [ 480.140000] sd 8:0:1:0: [sdd] Stopping disk
> [ 480.660000] sd 2:0:0:0: [sdc] Synchronizing SCSI cache
> [ 480.670000] sd 2:0:0:0: [sdc] Stopping disk
> [ 480.680000] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
> [ 480.700000] sd 1:0:0:0: [sdb] Stopping disk
> [ 480.710000] sd 0:0:0:0: [sda] Synchronizing SCSI cache
> [ 480.730000] sd 0:0:0:0: [sda] Stopping disk
> [ 480.740000] Power down.
> [ 489.030000] SysRq : Resetting
>
hm, dunno. The only substantial patch which touches
arch/x86_64/kernel/process.c (which is where cpu_idle lives) is
x86_64-prep-idle-loop-for-dynticks.patch.
The problem is, 2.6.23-rc6-mm1's git-acpi patch had all the new cpuidle
code in it. Len dropped all that code over the weekend (which is when I
picked this copy of his tree), so 2.6.23-rc7-mm1 doesn't have the cpuidle
code. Len will be reapplying the cpuidle patches today(ish) so next -mm
_will_ have the cpuidle code.
So what we have in rc7-mm1 is this transient no-cpuidle state. It could be
that the x86_64 dynticks code (which was developed previously tested in
conjunction with the cpuidle patches) has some dependency on cpuidle.
So it's all a bit of a mess :(
I think I'll basically stop applying things which don't look like bugfixes
for a while and try to get more -mm's out, as we seriously need to get this
lot stabilised asap.
Len, would it be possible to restore cpuidle sometime today please?
On Mon, 24 Sep 2007, Jiri Slaby wrote:
> Hmm, I have usb legacy keyboard switched on because of grub and bios to allow me
> typing.
>
> I booted 23-rc7 4 times, and the latest -mm 3 times just now and can't reproduce
> it, I just wonder by what is this conditioned.
Warm boot vs. cold boot, maybe.
Alan Stern
Hi Andrew,
The build fails with following error
CC drivers/block/ps3disk.o
drivers/block/ps3disk.c: In function ‘ps3disk_scatter_gather’:
drivers/block/ps3disk.c:115: error: ‘bio’ undeclared (first use in this
function)
drivers/block/ps3disk.c:115: error: (Each undeclared identifier is
reported only once
drivers/block/ps3disk.c:115: error: for each function it appears in.)
drivers/block/ps3disk.c:115: error: ‘j’ undeclared (first use in this
function)
drivers/block/ps3disk.c:116: error: implicit declaration of function
‘bio_kunmap_bvec’
make[2]: *** [drivers/block/ps3disk.o] Error 1
make[1]: *** [drivers/block] Error 2
make: *** [drivers] Error 2
The function bio_kunmap_bvec is missing.I tried checking the git-block.patch
as well as the linux/kernel/git/axboe/linux-2.6-block.git and did not
find this function.
Previously this function was replaced by __bio_kunmap_atomic();
This patch does not solves the implicit "declaration of function
‘bio_kunmap_bvec’"
Signed-off-by: Kamalesh Babulal <[email protected]
<mailto:[email protected]>>
---
--- linux-2.6.23-rc7/drivers/block/ps3disk.c 2007-09-24 20:50:41.000000000 +0530
+++ linux-2.6.23-rc7/drivers/block/~ps3disk.c 2007-09-24 20:50:59.000000000 +0530
@@ -112,7 +112,7 @@ static void ps3disk_scatter_gather(struc
else
memcpy(buf, dev->bounce_buf+offset, size);
offset += size;
- flush_kernel_dcache_page(bio_iovec_idx(bio, j)->bv_page);
+ flush_kernel_dcache_page(bio_iovec_idx(iter.bio, iter.i)->bv_page);
bio_kunmap_bvec(bvec, flags);
i++;
}
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
On Mon, 2007-09-24 at 12:34 -0700, Andrew Morton wrote:
> > It prints twice 'System halted' and blinks the keyboard leds, but does
> > not switch off. On all other kernel version I only see one keyboard
> > blink before the power goes out.
>
> ok...
>
> > I compared its dmesg to vanilla-rc7 and -rc4-mm1, but expect that rc-4
> > assigns different IRQs I can't see any differences except the normal
> > variation in BogoMips etc.
Can your check whether 2.6.23-rc7 +
http://tglx.de/projects/hrtimers/2.6.23-rc7/patch-2.6.23-rc7-hrt1.patch
works for you ?
> hm, dunno. The only substantial patch which touches
> arch/x86_64/kernel/process.c (which is where cpu_idle lives) is
> x86_64-prep-idle-loop-for-dynticks.patch.
>
> The problem is, 2.6.23-rc6-mm1's git-acpi patch had all the new cpuidle
> code in it. Len dropped all that code over the weekend (which is when I
> picked this copy of his tree), so 2.6.23-rc7-mm1 doesn't have the cpuidle
> code. Len will be reapplying the cpuidle patches today(ish) so next -mm
> _will_ have the cpuidle code.
>
> So what we have in rc7-mm1 is this transient no-cpuidle state. It could be
> that the x86_64 dynticks code (which was developed previously tested in
> conjunction with the cpuidle patches) has some dependency on cpuidle.
It should not. cpuidle makes use of dynticks not the other way round.
tglx
Hi Kamalesh.
> The link error for a PowerMac G5 (powerpc) is still seen with
> 2.6.23-rc7-mm1,
> and was reported for 2.6.23-rc6-mm1 (http://lkml.org/lkml/2007/9/19/62).
>
> KSYM .tmp_kallsyms1.S
> AS .tmp_kallsyms1.o
> LD .tmp_vmlinux2
> KSYM .tmp_kallsyms2.S
> AS .tmp_kallsyms2.o
> LD vmlinux.o
> ld: dynreloc miscount for fs/built-in.o, section .opd
> ld: can not edit opd Bad value
> make: *** [vmlinux.o] Error 1
Can you try to narrow it down a bit further...
As this happens when building fs/built-in.o it should be
straightforward to do so.
First step would be to do:
rm fs/built-in.o
make fs/ V=1
Then copy the ld invocation and try to remove the input .o files one-by-one.
This should tell you which .o file is causing the bug.
Next step is to try to squeze down the offending file until the
errornous part remains.
Last time I did a
make fs/file.i
And then I used gcc & ld to compile and link.
Gradually removing stuff from file.i made me spot the problem
with the weak prototype in a header file.
I guess something else is making ld hit this error now.
PS. Just reinstalled my dev box so no crosscompiler atm.
Sam
On 25/09/2007 3:12 AM, J. Bruce Fields wrote:
> On Mon, Sep 24, 2007 at 09:59:29AM -0700, Andrew Morton wrote:
>> On Tue, 25 Sep 2007 00:52:30 +1000 Reuben Farrelly <[email protected]> wrote:
>>
>>>
>>> On 24/09/2007 7:17 PM, Andrew Morton wrote:
>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
>>>>
>>>> - New git tree git-powerpc-galak.patch added to the -mm lineup: ppc32
>>>> things, mainly (Kumar Gala <[email protected]>)
>>> I'm observing a problem with this kernel (as well as 2.6.23-rc6-mm1) which
>>> manifests itself only in my Postfix/application mail.logs:
>>>
>>> Sep 25 00:25:40 tornado postfix/smtp[12520]: fatal: select lock: Cannot allocate
>>> memory
>>> Sep 25 00:25:41 tornado postfix/master[8002]: warning: process
>>> /usr/lib64/postfix/smtp pid 12520 exit status 1
>>>
>>> This is happening frequently with processes started via 'master' (smtp, smtpd
>>> and cleanup), but it does not appear to have any noticeable operational impact
>>> apart from logging a lot of copies of this message.
>>>
>>> The corresponding code in Postfix which triggers this is (choice of 3 files in
>>> src/master are all possibilities which all have much the same code)
>
> Oog. Looks like it's the "Memory shortage can result in inconsistent
> flocks state" patch--the error variable is being set in some cases when
> it shouldn't be. Does the following fix it?
>
> That's in my git tree, not in mainline. I'll fix up my copy.
>
> And I'll spend some time today figuring out what to do about regression
> testing for the posix lock, flock, and lease code.
>
> Thanks for the bug report!
>
> --b.
>
> diff --git a/fs/locks.c b/fs/locks.c
> index a6c5917..3e8bfd2 100644
> --- a/fs/locks.c
> +++ b/fs/locks.c
> @@ -740,6 +740,7 @@ static int flock_lock_file(struct file *filp, struct file_lock *request)
> new_fl = locks_alloc_lock();
> if (new_fl == NULL)
> goto out;
> + error = 0;
> }
>
> for_each_lock(inode, before) {
Yes that has fixed it, thanks!
Reuben
On Mon, Sep 24, 2007 at 11:02:22PM +0200, Sam Ravnborg wrote:
> Hi Kamalesh.
>
> > The link error for a PowerMac G5 (powerpc) is still seen with
> > 2.6.23-rc7-mm1,
> > and was reported for 2.6.23-rc6-mm1 (http://lkml.org/lkml/2007/9/19/62).
> >
> > KSYM .tmp_kallsyms1.S
> > AS .tmp_kallsyms1.o
> > LD .tmp_vmlinux2
> > KSYM .tmp_kallsyms2.S
> > AS .tmp_kallsyms2.o
> > LD vmlinux.o
> > ld: dynreloc miscount for fs/built-in.o, section .opd
> > ld: can not edit opd Bad value
> > make: *** [vmlinux.o] Error 1
>
> Can you try to narrow it down a bit further...
> As this happens when building fs/built-in.o it should be
> straightforward to do so.
>
> First step would be to do:
> rm fs/built-in.o
> make fs/ V=1
>
> Then copy the ld invocation and try to remove the input .o files one-by-one.
> This should tell you which .o file is causing the bug.
>
> Next step is to try to squeze down the offending file until the
> errornous part remains.
>
> Last time I did a
> make fs/file.i
>
> And then I used gcc & ld to compile and link.
> Gradually removing stuff from file.i made me spot the problem
> with the weak prototype in a header file.
>
> I guess something else is making ld hit this error now.
>
> PS. Just reinstalled my dev box so no crosscompiler atm.
Got powerpc toolchain running now but cannot reproduce.
What config do you use (I used g5_defconfig)?
And what ld version?
Sam
Hi Wang,
> This patch:
> - makes hidp_setup_input() return int to indicate errors;
> - checks its return value to handle errors.
>
> And this time it is against -rc7-mm1 tree.
>
> Thanks to roel and Marcel Holtmann for comments.
>
> Signed-off-by: WANG Cong <[email protected]>
Signed-off-by: Marcel Holtmann <[email protected]>
Regards
Marcel
Hi Andrew,
The drivers/net/pasemi_mac seems to be broken and build fails with
CC [M] drivers/net/pasemi_mac.o
drivers/net/pasemi_mac.c: In function ‘pasemi_mac_probe’:
drivers/net/pasemi_mac.c:1153: error: conflicting types for ‘mac’
drivers/net/pasemi_mac.c:1151: error: previous declaration of ‘mac’ was here
drivers/net/pasemi_mac.c:1170: error: incompatible types in assignment
drivers/net/pasemi_mac.c:1172: error: request for member ‘pdev’ in
something not a structure or union
drivers/net/pasemi_mac.c:1173: error: request for member ‘netdev’ in
something not a structure or union
drivers/net/pasemi_mac.c:1175: error: request for member ‘napi’ in
something not a structure or union
drivers/net/pasemi_mac.c:1180: error: request for member ‘dma_txch’ in
something not a structure or union
drivers/net/pasemi_mac.c:1181: error: request for member ‘dma_rxch’ in
something not a structure or union
drivers/net/pasemi_mac.c:1187: error: request for member ‘dma_if’ in
something not a structure or union
drivers/net/pasemi_mac.c:1189: error: request for member ‘dma_if’ in
something not a structure or union
drivers/net/pasemi_mac.c:1194: error: request for member ‘type’ in
something not a structure or union
drivers/net/pasemi_mac.c:1197: error: request for member ‘type’ in
something not a structure or union
drivers/net/pasemi_mac.c:1205: warning: passing argument 1 of
‘pasemi_get_mac_addr’ from incompatible pointer type
drivers/net/pasemi_mac.c:1205: error: request for member ‘mac_addr’ in
something not a structure or union
drivers/net/pasemi_mac.c:1209: error: request for member ‘mac_addr’ in
something not a structure or union
drivers/net/pasemi_mac.c:1209: error: request for member ‘mac_addr’ in
something not a structure or union
drivers/net/pasemi_mac.c:1216: warning: passing argument 1 of
‘pasemi_mac_map_regs’ from incompatible pointer type
drivers/net/pasemi_mac.c:1220: error: request for member ‘rx_status’ in
something not a structure or union
drivers/net/pasemi_mac.c:1220: error: request for member ‘dma_rxch’ in
something not a structure or union
drivers/net/pasemi_mac.c:1221: error: request for member ‘tx_status’ in
something not a structure or union
drivers/net/pasemi_mac.c:1221: error: request for member ‘dma_txch’ in
something not a structure or union
drivers/net/pasemi_mac.c:1223: error: request for member ‘msg_enable’ in
something not a structure or union
drivers/net/pasemi_mac.c:1226: error: request for member ‘msg_enable’ in
something not a structure or union
drivers/net/pasemi_mac.c:1231: error: request for member ‘pdev’ in
something not a structure or union
drivers/net/pasemi_mac.c:1231: error: request for member ‘pdev’ in
something not a structure or union
drivers/net/pasemi_mac.c:1237: error: request for member ‘type’ in
something not a structure or union
drivers/net/pasemi_mac.c:1238: error: request for member ‘dma_if’ in
something not a structure or union
drivers/net/pasemi_mac.c:1238: error: request for member ‘dma_txch’ in
something not a structure or union
drivers/net/pasemi_mac.c:1238: error: request for member ‘dma_rxch’ in
something not a structure or union
drivers/net/pasemi_mac.c:1244: error: request for member ‘iob_pdev’ in
something not a structure or union
drivers/net/pasemi_mac.c:1245: error: request for member ‘iob_pdev’ in
something not a structure or union
drivers/net/pasemi_mac.c:1246: error: request for member ‘dma_pdev’ in
something not a structure or union
drivers/net/pasemi_mac.c:1247: error: request for member ‘dma_pdev’ in
something not a structure or union
drivers/net/pasemi_mac.c:1248: error: request for member ‘dma_regs’ in
something not a structure or union
drivers/net/pasemi_mac.c:1249: error: request for member ‘dma_regs’ in
something not a structure or union
drivers/net/pasemi_mac.c:1250: error: request for member ‘iob_regs’ in
something not a structure or union
drivers/net/pasemi_mac.c:1251: error: request for member ‘iob_regs’ in
something not a structure or union
drivers/net/pasemi_mac.c:1252: error: request for member ‘regs’ in
something not a structure or union
drivers/net/pasemi_mac.c:1253: error: request for member ‘regs’ in
something not a structure or union
make[2]: *** [drivers/net/pasemi_mac.o] Error 1
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
In the function
static int __devinit
pasemi_mac_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
{
<snip>
struct pasemi_mac *mac;
int err;
DECLARE_MAC_BUF(mac);
introduction of mac as var [18] triggers the build failure, so in the
below patch
renaming mac as mac_buf is done, because it is used to print the mac
address using
the newly introduced print_mac function.
Signed-off-by: Kamalesh Babulal <[email protected]>
---
--- linux-2.6.23-rc7/drivers/net/pasemi_mac.c 2007-09-25 03:27:45.000000000 +0530
+++ linux-2.6.23-rc7/drivers/net/~pasemi_mac.c 2007-09-25 03:27:27.000000000 +0530
@@ -1150,7 +1150,7 @@ pasemi_mac_probe(struct pci_dev *pdev, c
struct net_device *dev;
struct pasemi_mac *mac;
int err;
- DECLARE_MAC_BUF(mac);
+ DECLARE_MAC_BUF(mac_buf);
err = pci_enable_device(pdev);
if (err)
@@ -1236,7 +1236,7 @@ pasemi_mac_probe(struct pci_dev *pdev, c
"hw addr %s\n",
dev->name, mac->type == MAC_TYPE_GMAC ? "GMAC" : "XAUI",
mac->dma_if, mac->dma_txch, mac->dma_rxch,
- print_mac(mac, dev->dev_addr));
+ print_mac(mac_buf, dev->dev_addr));
return err;
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.23-rc7-mm1
# Mon Sep 24 20:25:04 2007
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_QUICKLIST=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_USER_NS is not set
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=15
# CONFIG_CGROUPS is not set
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_EMBEDDED=y
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_PROC_KPAGEMAP=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_BLOCK=y
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set
# CONFIG_BLK_DEV_BSG is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
# CONFIG_HIGH_RES_TIMERS is not set
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
# CONFIG_SMP is not set
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
# CONFIG_PARAVIRT is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MCORE2 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_XADD=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
CONFIG_X86_TSC=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=4
CONFIG_HPET_TIMER=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=m
CONFIG_X86_MCE_P4THERMAL=y
CONFIG_VM86=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_X86_REBOOTFIXUPS=y
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=m
# CONFIG_X86_CPUID is not set
#
# Firmware Drivers
#
CONFIG_EDD=y
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_3G_OPT is not set
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_2G_OPT is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
# CONFIG_X86_PAE is not set
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
# CONFIG_SPARSEMEM_VMEMMAP_ENABLE is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_NR_QUICK=1
CONFIG_VIRT_TO_BUS=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_KEXEC=y
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
# CONFIG_COMPAT_VDSO is not set
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_LEGACY is not set
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND_UP_POSSIBLE=y
CONFIG_SUSPEND=y
CONFIG_HIBERNATION_UP_POSSIBLE=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION="/dev/hdb6"
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
# CONFIG_ACPI_PROCFS is not set
CONFIG_ACPI_PROC_EVENT=y
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_ACPI_DEBUG=y
# CONFIG_ACPI_DEBUG_FUNC_TRACE is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set
# CONFIG_ACPI_SBS is not set
# CONFIG_APM is not set
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCIEPORTBUS is not set
CONFIG_ARCH_SUPPORTS_MSI=y
# CONFIG_PCI_MSI is not set
# CONFIG_PCI_DEBUG is not set
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_MISC=m
#
# Networking
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=m
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_MULTIPLE_TABLES is not set
# CONFIG_IP_ROUTE_MULTIPATH is not set
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
CONFIG_INET_XFRM_MODE_BEET=y
# CONFIG_INET_LRO is not set
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_NETWORK_SECMARK is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
# CONFIG_NF_CONNTRACK_ENABLED is not set
# CONFIG_NF_CONNTRACK is not set
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
# CONFIG_NETFILTER_XT_TARGET_DSCP is not set
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
# CONFIG_NETFILTER_XT_TARGET_NFLOG is not set
# CONFIG_NETFILTER_XT_TARGET_TCPMSS is not set
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
# 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_LENGTH is not set
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
# CONFIG_NETFILTER_XT_MATCH_MULTIPORT is not set
# CONFIG_NETFILTER_XT_MATCH_PKTTYPE is not set
# CONFIG_NETFILTER_XT_MATCH_QUOTA is not set
# CONFIG_NETFILTER_XT_MATCH_REALM is not set
CONFIG_NETFILTER_XT_MATCH_SCTP=m
# CONFIG_NETFILTER_XT_MATCH_STATISTIC is not set
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
# CONFIG_NETFILTER_XT_MATCH_U32 is not set
# CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is not set
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
# CONFIG_IP_NF_MATCH_ECN is not set
# CONFIG_IP_NF_MATCH_AH is not set
# CONFIG_IP_NF_MATCH_TTL is not set
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
# CONFIG_IP_NF_RAW is not set
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
# CONFIG_IP_NF_ARP_MANGLE is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set
# CONFIG_ATM_LANE is not set
CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_FIFO=y
#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
# CONFIG_NET_SCH_ATM is not set
CONFIG_NET_SCH_PRIO=m
# CONFIG_NET_SCH_RR is not set
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
# CONFIG_NET_SCH_NETEM is not set
CONFIG_NET_SCH_INGRESS=m
#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_EMATCH is not set
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=y
# CONFIG_NET_ACT_GACT is not set
# CONFIG_NET_ACT_MIRRED is not set
# CONFIG_NET_ACT_IPT is not set
# CONFIG_NET_ACT_PEDIT is not set
# CONFIG_NET_ACT_SIMP is not set
CONFIG_NET_CLS_POLICE=y
# CONFIG_NET_CLS_IND is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
#
# Wireless
#
CONFIG_CFG80211=m
CONFIG_NL80211=y
CONFIG_WIRELESS_EXT=y
CONFIG_MAC80211=m
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_DEBUG is not set
CONFIG_IEEE80211=m
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=m
CONFIG_IEEE80211_CRYPT_TKIP=m
CONFIG_IEEE80211_SOFTMAC=m
# CONFIG_IEEE80211_SOFTMAC_DEBUG is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_AX88796 is not set
CONFIG_PARPORT_1284=y
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set
#
# Protocols
#
# CONFIG_ISAPNP is not set
# CONFIG_PNPBIOS is not set
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_MISC_DEVICES is not set
# CONFIG_IDE is not set
#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=m
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
# CONFIG_CHR_DEV_SCH is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
# CONFIG_SCSI_LOWLEVEL is not set
CONFIG_ATA=m
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_ACPI=y
# CONFIG_SATA_AHCI is not set
# CONFIG_SATA_SVW is not set
# CONFIG_ATA_PIIX is not set
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SX4 is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIL24 is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5535 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
CONFIG_ATA_GENERIC=m
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_LEGACY is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_QDI is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
CONFIG_PATA_VIA=m
# CONFIG_PATA_WINBOND is not set
# CONFIG_PATA_WINBOND_VLB is not set
CONFIG_PATA_PLATFORM=m
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
CONFIG_MD_RAID5_RESHAPE=y
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
CONFIG_BLK_DEV_DM=m
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
CONFIG_FIREWIRE=m
CONFIG_FIREWIRE_OHCI=m
# CONFIG_FIREWIRE_SBP2 is not set
CONFIG_IEEE1394=m
#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
#
# Controllers
#
# CONFIG_IEEE1394_PCILYNX is not set
CONFIG_IEEE1394_OHCI1394=m
#
# Protocols
#
CONFIG_IEEE1394_VIDEO1394=m
# CONFIG_IEEE1394_SBP2 is not set
# CONFIG_IEEE1394_ETH1394_ROM_ENTRY is not set
# CONFIG_IEEE1394_ETH1394 is not set
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_NETDEVICES_MULTIQUEUE is not set
# CONFIG_IFB is not set
CONFIG_DUMMY=m
CONFIG_BONDING=m
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m
# CONFIG_VETH is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_IP1000 is not set
# CONFIG_ARCNET is not set
# CONFIG_PHYLIB is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
CONFIG_NE2K_PCI=m
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SC92031 is not set
# CONFIG_NET_POCKET is not set
# CONFIG_NETDEV_1000 is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set
#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
CONFIG_WLAN_80211=y
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not set
# CONFIG_LIBERTAS is not set
# CONFIG_AIRO is not set
# CONFIG_HERMES is not set
# CONFIG_USB_ATMEL is not set
# CONFIG_ATMEL is not set
# CONFIG_PRISM54 is not set
# CONFIG_USB_ZD1201 is not set
# CONFIG_RTL8187 is not set
# CONFIG_ADM8211 is not set
# CONFIG_P54_COMMON is not set
# CONFIG_ATH5K is not set
# CONFIG_HOSTAP is not set
# CONFIG_BCM43XX is not set
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not set
CONFIG_ZD1211RW=m
# CONFIG_ZD1211RW_DEBUG is not set
# CONFIG_RT2X00 is not set
CONFIG_Z1211=m
# CONFIG_Z1211_DEBUG is not set
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET_MII is not set
# CONFIG_USB_USBNET is not set
# CONFIG_WAN is not set
# CONFIG_ATM_DRIVERS is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=m
# CONFIG_PPP_MULTILINK is not set
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
# CONFIG_PPP_MPPE is not set
CONFIG_PPPOE=m
CONFIG_PPPOATM=m
# CONFIG_PPPOL2TP is not set
# CONFIG_SLIP is not set
CONFIG_SLHC=m
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER 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 is not set
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_PS2_ALPS is not set
# CONFIG_MOUSE_PS2_LOGIPS2PP is not set
# CONFIG_MOUSE_PS2_SYNAPTICS is not set
# CONFIG_MOUSE_PS2_LIFEBOOK is not set
# CONFIG_MOUSE_PS2_TRACKPOINT is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_PS2_ELANTECH is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA is not set
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
# CONFIG_JOYSTICK_A3D is not set
# CONFIG_JOYSTICK_ADI is not set
# 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 is not set
# CONFIG_JOYSTICK_IFORCE is not set
# 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_DB9 is not set
# CONFIG_JOYSTICK_GAMECON is not set
# CONFIG_JOYSTICK_TURBOGRAFX is not set
# CONFIG_JOYSTICK_JOYDUMP is not set
# CONFIG_JOYSTICK_XPAD is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_WISTRON_BTNS is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
# CONFIG_INPUT_ATI_REMOTE is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
CONFIG_INPUT_UINPUT=m
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
CONFIG_GAMEPORT=m
# 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_VT_UNICODE is not set
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=m
CONFIG_FIX_EARLYCON_MEM=y
# CONFIG_SERIAL_8250_PCI is not set
CONFIG_SERIAL_8250_PNP=m
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=m
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=m
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
CONFIG_AGP_VIA=m
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_GPIO is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=m
#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=y
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_ALGOPCA=m
#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_ELEKTOR is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_TINY_USB is not set
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set
#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
# CONFIG_DS1682 is not set
CONFIG_SENSORS_EEPROM=m
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_FSCPOS is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_CORETEMP is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
CONFIG_SENSORS_LM80=m
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_THMC50 is not set
CONFIG_SENSORS_VIA686A=m
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
CONFIG_SENSORS_W83781D=m
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_SENSORS_APPLESMC is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not set
# CONFIG_WATCHDOG is not set
#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set
#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_PMS is not set
# CONFIG_VIDEO_BWQCAM is not set
# CONFIG_VIDEO_CQCAM is not set
# CONFIG_VIDEO_W9966 is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set
# CONFIG_VIDEO_IVTV is not set
# CONFIG_VIDEO_CAFE_CCIC is not set
CONFIG_V4L_USB_DRIVERS=y
# CONFIG_VIDEO_PVRUSB2 is not set
# CONFIG_VIDEO_EM28XX is not set
# CONFIG_VIDEO_USBVISION is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_QUICKCAM_MESSENGER is not set
# CONFIG_USB_ET61X251 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
# CONFIG_USB_W9968CF is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_ZC0301 is not set
# CONFIG_USB_PWC is not set
# CONFIG_USB_ZR364XX is not set
# CONFIG_USB_STK11XX is not set
# CONFIG_RADIO_ADAPTERS is not set
# CONFIG_DVB_CORE is not set
# CONFIG_DAB is not set
#
# Graphics support
#
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_SYS_FOPS is not set
CONFIG_FB_DEFERRED_IO=y
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
# CONFIG_FB_EFI is not set
# CONFIG_FB_HECUBA is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
CONFIG_FB_RADEON=y
CONFIG_FB_RADEON_I2C=y
# CONFIG_FB_RADEON_BACKLIGHT is not set
# CONFIG_FB_RADEON_DEBUG is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_CYBLA is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
#
# Sound
#
CONFIG_SOUND=m
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
CONFIG_SND_DYNAMIC_MINORS=y
# CONFIG_SND_SUPPORT_OLD_API is not set
# CONFIG_SND_VERBOSE_PROCFS is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
CONFIG_SND_AC97_CODEC=m
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_MTS64 is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
# CONFIG_SND_PORTMAN2X4 is not set
#
# ISA devices
#
# CONFIG_SND_ADLIB is not set
# CONFIG_SND_AD1816A is not set
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_ALS100 is not set
# CONFIG_SND_AZT2320 is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_DT019X is not set
# CONFIG_SND_ES968 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_SC6000 is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_MIRO is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set
# CONFIG_SND_WAVEFRONT is not set
#
# PCI devices
#
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_CS5535AUDIO is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
CONFIG_SND_ENS1371=m
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_HDA_INTEL is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0
#
# USB devices
#
CONFIG_SND_USB_AUDIO=m
# CONFIG_SND_USB_USX2Y is not set
# CONFIG_SND_USB_CAIAQ is not set
#
# System on Chip audio support
#
# CONFIG_SND_SOC is not set
#
# SoC Audio support for SuperH
#
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
CONFIG_AC97_BUS=m
CONFIG_HID_SUPPORT=y
CONFIG_HID=m
# CONFIG_HID_DEBUG is not set
# CONFIG_HIDRAW is not set
#
# USB Input Devices
#
CONFIG_USB_HID=m
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_DEVICE_CLASS=y
CONFIG_USB_DYNAMIC_MINORS=y
CONFIG_USB_SUSPEND=y
# CONFIG_USB_PERSIST is not set
# CONFIG_USB_OTG is not set
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
# CONFIG_USB_EHCI_SPLIT_ISO is not set
CONFIG_USB_EHCI_ROOT_HUB_TT=y
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=m
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#
#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_LIBUSUAL is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_MON is not set
#
# USB port drivers
#
# CONFIG_USB_USS720 is not set
#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GOTEMP is not set
#
# USB DSL modem support
#
CONFIG_USB_ATM=m
# CONFIG_USB_SPEEDTOUCH is not set
# CONFIG_USB_CXACRU is not set
CONFIG_USB_UEAGLEATM=m
# CONFIG_USB_XUSBATM is not set
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
# CONFIG_MMC is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC=y
#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_MM_EDAC=m
CONFIG_EDAC_AMD76X=m
# CONFIG_EDAC_E7XXX is not set
# CONFIG_EDAC_E752X is not set
# CONFIG_EDAC_I82875P is not set
# CONFIG_EDAC_I82975X is not set
# CONFIG_EDAC_I3000 is not set
# CONFIG_EDAC_I82860 is not set
# CONFIG_EDAC_R82600 is not set
# CONFIG_EDAC_I5000 is not set
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
# CONFIG_AUXDISPLAY is not set
# CONFIG_VIRTUALIZATION is not set
#
# Userspace I/O
#
# CONFIG_UIO is not set
#
# 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_FS_XIP=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
# CONFIG_EXT3_FS_SECURITY is not set
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISER4_FS=m
# CONFIG_REISER4_DEBUG is not set
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
# CONFIG_REISERFS_FS_POSIX_ACL is not set
# CONFIG_REISERFS_FS_SECURITY is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=m
# CONFIG_FUSE_FS is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=850
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_CONFIGFS_FS=m
#
# Layered filesystems
#
CONFIG_ECRYPT_FS=m
# CONFIG_UNION_FS is not set
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
# CONFIG_SUNRPC_BIND34 is not set
CONFIG_RPCSEC_GSS_KRB5=m
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
CONFIG_CIFS=m
CONFIG_CIFS_STATS=y
# CONFIG_CIFS_STATS2 is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
# CONFIG_SYSV68_PARTITION is not set
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=m
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=m
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=m
#
# Distributed Lock Manager
#
# CONFIG_DLM is not set
CONFIG_INSTRUMENTATION=y
CONFIG_PROFILING=y
CONFIG_OPROFILE=m
# CONFIG_KPROBES is not set
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_PAGE_OWNER is not set
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
# CONFIG_DETECT_SOFTLOCKUP is not set
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_SLAB_LEAK=y
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_DEBUG_LOCKING_API_SELFTESTS=y
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_LIST is not set
CONFIG_FRAME_POINTER=y
# CONFIG_UNWIND_INFO is not set
# CONFIG_PROFILE_LIKELY is not set
# CONFIG_FORCED_INLINING is not set
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_DEBUG_SYNCHRO_TEST is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_WANT_EXTRA_DEBUG_INFORMATION is not set
# CONFIG_KGDB is not set
# CONFIG_KGDB_ATTACH_WAIT is not set
CONFIG_EARLY_PRINTK=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_STACK_USAGE=y
#
# Page alloc debug is incompatible with Software Suspend on i386
#
CONFIG_DEBUG_RODATA=y
CONFIG_4KSTACKS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y
#
# Security options
#
CONFIG_KEYS=y
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_XOR_BLOCKS=m
CONFIG_ASYNC_CORE=m
CONFIG_ASYNC_MEMCPY=m
CONFIG_ASYNC_XOR=m
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_GF128MUL is not set
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_PCBC=m
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_XTS is not set
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_DES=m
# CONFIG_CRYPTO_FCRYPT is not set
CONFIG_CRYPTO_BLOWFISH=m
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_586 is not set
# CONFIG_CRYPTO_SERPENT is not set
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
CONFIG_CRYPTO_ARC4=m
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_SEED is not set
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_TEST is not set
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_HW is not set
#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=m
# CONFIG_CRC16 is not set
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_LZO_COMPRESS=m
CONFIG_LZO_DECOMPRESS=m
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_KTIME_SCALAR=y
[adding kexec m-l]
On Mon, 24 Sep 2007 22:10:36 +0200 Laurent Riffard wrote:
> Le 24.09.2007 11:17, Andrew Morton a ?crit :
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
> >
>
> I've got this compilation when CONFIG_KEXEC=y and CCONFIG_NOHIGHMEM=y:
>
> linux-2.6-mm$ LANG=C make
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> CALL scripts/checksyscalls.sh
> CHK include/linux/compile.h
> CC arch/i386/kernel/setup.o
> arch/i386/kernel/setup.c: In function 'reserve_crashkernel':
> arch/i386/kernel/setup.c:391: error: 'highend_pfn' undeclared (first use in this function)
> arch/i386/kernel/setup.c:391: error: (Each undeclared identifier is reported only once
> arch/i386/kernel/setup.c:391: error: for each function it appears in.)
> arch/i386/kernel/setup.c:391: error: 'highstart_pfn' undeclared (first use in this function)
> make[1]: *** [arch/i386/kernel/setup.o] Error 1
> make: *** [arch/i386/kernel] Error 2
>
>
> .config attached.
> ~~
> laurent
>
---
~Randy
Phaedrus says that Quality is about caring.
Sam Ravnborg wrote:
> On Mon, Sep 24, 2007 at 11:02:22PM +0200, Sam Ravnborg wrote:
>> Hi Kamalesh.
>>
>>> The link error for a PowerMac G5 (powerpc) is still seen with
>>> 2.6.23-rc7-mm1,
>>> and was reported for 2.6.23-rc6-mm1 (http://lkml.org/lkml/2007/9/19/62).
>>>
>>> KSYM .tmp_kallsyms1.S
>>> AS .tmp_kallsyms1.o
>>> LD .tmp_vmlinux2
>>> KSYM .tmp_kallsyms2.S
>>> AS .tmp_kallsyms2.o
>>> LD vmlinux.o
>>> ld: dynreloc miscount for fs/built-in.o, section .opd
>>> ld: can not edit opd Bad value
>>> make: *** [vmlinux.o] Error 1
>> Can you try to narrow it down a bit further...
>> As this happens when building fs/built-in.o it should be
>> straightforward to do so.
>>
>> First step would be to do:
>> rm fs/built-in.o
>> make fs/ V=1
>>
>> Then copy the ld invocation and try to remove the input .o files one-by-one.
>> This should tell you which .o file is causing the bug.
>>
>> Next step is to try to squeze down the offending file until the
>> errornous part remains.
>>
>> Last time I did a
>> make fs/file.i
>>
>> And then I used gcc & ld to compile and link.
>> Gradually removing stuff from file.i made me spot the problem
>> with the weak prototype in a header file.
>>
>> I guess something else is making ld hit this error now.
>>
>> PS. Just reinstalled my dev box so no crosscompiler atm.
>
> Got powerpc toolchain running now but cannot reproduce.
> What config do you use (I used g5_defconfig)?
> And what ld version?
>
> Sam
Hi Sam,
root@elm3b19:~# ld -v
GNU ld version 2.16.1 Debian GNU/Linux
root@elm3b19:~# gcc -v
Using built-in specs.
Target: powerpc-linux-gnu
Configured with: ../src/configure -v --enable-languages=c,c++,java,f95,objc,ada,treelang --prefix=/usr --with-gxx-include-dir=/usr/include/c++/4.0.2 --enable-shared --with-system-zlib --libexecdir=/usr/lib --enable-nls --without-included-gettext --enable-threads=posix --program-suffix=-4.0 --enable-__cxa_atexit --enable-libstdcxx-allocator=mt --enable-clocale=gnu --enable-libstdcxx-debug --enable-java-gc=boehm --enable-java-awt=gtk-default --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/jre --enable-mpfr --disable-softfloat --enable-targets=powerpc-linux,powerpc64-linux --with-cpu=default32 --disable-werror --enable-checking=release powerpc-linux-gnu
Thread model: posix
gcc version 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu9)
and the .config file is a custom file which i have attached.
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
On 9/24/07, Thomas Gleixner <[email protected]> wrote:
> Can your check whether 2.6.23-rc7 +
> http://tglx.de/projects/hrtimers/2.6.23-rc7/patch-2.6.23-rc7-hrt1.patch
>
> works for you ?
Yes, powers off normally.
Torsten
On Tue, 2007-09-25 at 09:32 +0200, Torsten Kaiser wrote:
> On 9/24/07, Thomas Gleixner <[email protected]> wrote:
> > Can your check whether 2.6.23-rc7 +
> > http://tglx.de/projects/hrtimers/2.6.23-rc7/patch-2.6.23-rc7-hrt1.patch
> >
> > works for you ?
>
> Yes, powers off normally.
Ok, so it's probably some merge artifact in -mm. We'll get this sorted
out once Len has his new tree available.
tglx
On (25/09/07 01:11), Kamalesh Babulal didst pronounce:
Hi Kamalesh,
> The build fails with following error
>
> CC drivers/block/ps3disk.o
> drivers/block/ps3disk.c: In function ???ps3disk_scatter_gather???:
> drivers/block/ps3disk.c:115: error: ???bio??? undeclared (first use in this
> function)
> drivers/block/ps3disk.c:115: error: (Each undeclared identifier is
> reported only once
> drivers/block/ps3disk.c:115: error: for each function it appears in.)
> drivers/block/ps3disk.c:115: error: ???j??? undeclared (first use in this
> function)
> drivers/block/ps3disk.c:116: error: implicit declaration of function
> ???bio_kunmap_bvec???
> make[2]: *** [drivers/block/ps3disk.o] Error 1
> make[1]: *** [drivers/block] Error 2
> make: *** [drivers] Error 2
>
> The function bio_kunmap_bvec is missing.I tried checking the git-block.patch
> as well as the linux/kernel/git/axboe/linux-2.6-block.git and did not
> find this function.
>
> Previously this function was replaced by __bio_kunmap_atomic();
> This patch does not solves the implicit "declaration of function
> ???bio_kunmap_bvec???"
>
> Signed-off-by: Kamalesh Babulal <[email protected]
> <mailto:[email protected]>>
Your mailer appears to have mangled both your signoff and the whitespace in
the patch and it does not apply. However, fixing it does not solve the problem
because of this mysterious bio_kunmap_bvec() that is only referenced by this
driver. Was it accidently added during the addition of sg chaining support?
> ---
>
> --- linux-2.6.23-rc7/drivers/block/ps3disk.c 2007-09-24 20:50:41.000000000 +0530
> +++ linux-2.6.23-rc7/drivers/block/~ps3disk.c 2007-09-24 20:50:59.000000000 +0530
> @@ -112,7 +112,7 @@ static void ps3disk_scatter_gather(struc
> else
> memcpy(buf, dev->bounce_buf+offset, size);
> offset += size;
> - flush_kernel_dcache_page(bio_iovec_idx(bio, j)->bv_page);
> + flush_kernel_dcache_page(bio_iovec_idx(iter.bio, iter.i)->bv_page);
> bio_kunmap_bvec(bvec, flags);
> i++;
> }
>
> --
>
> Thanks & Regards,
> Kamalesh Babulal,
> Linux Technology Center,
> IBM, ISTL.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
On Tue, Sep 25 2007, Mel Gorman wrote:
> On (25/09/07 01:11), Kamalesh Babulal didst pronounce:
>
> Hi Kamalesh,
>
> > The build fails with following error
> >
> > CC drivers/block/ps3disk.o
> > drivers/block/ps3disk.c: In function ???ps3disk_scatter_gather???:
> > drivers/block/ps3disk.c:115: error: ???bio??? undeclared (first use in this
> > function)
> > drivers/block/ps3disk.c:115: error: (Each undeclared identifier is
> > reported only once
> > drivers/block/ps3disk.c:115: error: for each function it appears in.)
> > drivers/block/ps3disk.c:115: error: ???j??? undeclared (first use in this
> > function)
> > drivers/block/ps3disk.c:116: error: implicit declaration of function
> > ???bio_kunmap_bvec???
> > make[2]: *** [drivers/block/ps3disk.o] Error 1
> > make[1]: *** [drivers/block] Error 2
> > make: *** [drivers] Error 2
> >
> > The function bio_kunmap_bvec is missing.I tried checking the git-block.patch
> > as well as the linux/kernel/git/axboe/linux-2.6-block.git and did not
> > find this function.
> >
> > Previously this function was replaced by __bio_kunmap_atomic();
> > This patch does not solves the implicit "declaration of function
> > ???bio_kunmap_bvec???"
> >
> > Signed-off-by: Kamalesh Babulal <[email protected]
> > <mailto:[email protected]>>
>
> Your mailer appears to have mangled both your signoff and the whitespace in
> the patch and it does not apply. However, fixing it does not solve the problem
> because of this mysterious bio_kunmap_bvec() that is only referenced by this
> driver. Was it accidently added during the addition of sg chaining support?
This should fix things up.
diff --git a/drivers/block/ps3disk.c b/drivers/block/ps3disk.c
index 8e05ba7..a7fd66a 100644
--- a/drivers/block/ps3disk.c
+++ b/drivers/block/ps3disk.c
@@ -106,14 +106,14 @@ static void ps3disk_scatter_gather(struct ps3_storage_device *dev,
(unsigned long)iter.bio->bi_sector);
size = bvec->bv_len;
- buf = bvec_kmap_irq(bvec, flags);
+ buf = bvec_kmap_irq(bvec, &flags);
if (gather)
memcpy(dev->bounce_buf+offset, buf, size);
else
memcpy(buf, dev->bounce_buf+offset, size);
offset += size;
- flush_kernel_dcache_page(bio_iovec_idx(bio, j)->bv_page);
- bio_kunmap_bvec(bvec, flags);
+ flush_kernel_dcache_page(bvec->bv_page);
+ bvec_kunmap_irq(buf, &flags);
i++;
}
}
--
Jens Axboe
On Mon, 24 Sep 2007 21:20:58 +0200 Peter Zijlstra
<[email protected]> wrote:
> > > Nope, and the stacktrace is utterly puzzling.
> > >
> > > /me goes read the lkml.org link
> > >
> > > Kamalesh Babulal: do you still get:
> > > BUG: spinlock bad magic on
> > >
> > > msgs?
> > >
> > > Because those I could reproduce using fsx, and I fixed all that.
> > Hi Peter,
> >
> > I do not get BUG: spinlock bad magic messages any more, but the softlock message is
> > thrown more than 30 time, while running the ltp runall.
>
> It would be good to know what function on_each_cpu is executing, could
> you try something like:
I've just completed 2 full ltp runs on a dual-core opteron machine but
could not reproduce this problem.
Kamalesh, would it be possible for you to reproduce with that patch, so
we can see what function is holding up the cpu?
On (25/09/07 12:31), Jens Axboe didst pronounce:
> On Tue, Sep 25 2007, Mel Gorman wrote:
> > On (25/09/07 01:11), Kamalesh Babulal didst pronounce:
> >
> > Hi Kamalesh,
> >
> > > The build fails with following error
> > >
> > > CC drivers/block/ps3disk.o
> > > drivers/block/ps3disk.c: In function ???ps3disk_scatter_gather???:
> > > drivers/block/ps3disk.c:115: error: ???bio??? undeclared (first use in this
> > > function)
> > > drivers/block/ps3disk.c:115: error: (Each undeclared identifier is
> > > reported only once
> > > drivers/block/ps3disk.c:115: error: for each function it appears in.)
> > > drivers/block/ps3disk.c:115: error: ???j??? undeclared (first use in this
> > > function)
> > > drivers/block/ps3disk.c:116: error: implicit declaration of function
> > > ???bio_kunmap_bvec???
> > > make[2]: *** [drivers/block/ps3disk.o] Error 1
> > > make[1]: *** [drivers/block] Error 2
> > > make: *** [drivers] Error 2
> > >
> > > The function bio_kunmap_bvec is missing.I tried checking the git-block.patch
> > > as well as the linux/kernel/git/axboe/linux-2.6-block.git and did not
> > > find this function.
> > >
> > > Previously this function was replaced by __bio_kunmap_atomic();
> > > This patch does not solves the implicit "declaration of function
> > > ???bio_kunmap_bvec???"
> > >
> > > Signed-off-by: Kamalesh Babulal <[email protected]
> > > <mailto:[email protected]>>
> >
> > Your mailer appears to have mangled both your signoff and the whitespace in
> > the patch and it does not apply. However, fixing it does not solve the problem
> > because of this mysterious bio_kunmap_bvec() that is only referenced by this
> > driver. Was it accidently added during the addition of sg chaining support?
>
> This should fix things up.
>
This builds although I lack the hardware to really test it. However, in
2.6.23-rc8-mm1 it collides with git-block-ps3disk-fix.patch. This is a
version on top of that stack but I guess the best thing to do is replace
git-block-ps3disk-fix.patch with Jens patch once it is signed off.
Not signing off because this is just a rebase. Assuming the other one
gets signed off, consider it;
Acked-by: Mel Gorman <[email protected]>
---
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff linux-2.6.23-rc8-mm1-clean/drivers/block/ps3disk.c linux-2.6.23-rc8-mm1-fix-ps3disk/drivers/block/ps3disk.c
--- linux-2.6.23-rc8-mm1-clean/drivers/block/ps3disk.c 2007-09-25 12:05:40.000000000 +0100
+++ linux-2.6.23-rc8-mm1-fix-ps3disk/drivers/block/ps3disk.c 2007-09-25 12:09:19.000000000 +0100
@@ -106,14 +106,14 @@ static void ps3disk_scatter_gather(struc
(unsigned long)iter.bio->bi_sector);
size = bvec->bv_len;
- buf = bvec_kmap_irq(bvec, flags);
+ buf = bvec_kmap_irq(bvec, &flags);
if (gather)
memcpy(dev->bounce_buf+offset, buf, size);
else
memcpy(buf, dev->bounce_buf+offset, size);
offset += size;
- flush_kernel_dcache_page(bio_iovec_idx(iter.bio, iter.i)->bv_page);
- bio_kunmap_bvec(bvec, flags);
+ flush_kernel_dcache_page(bvec->bv_page);
+ bvec_kunmap_irq(buf, &flags);
i++;
}
}
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
On Tue, Sep 25 2007, Mel Gorman wrote:
> On (25/09/07 12:31), Jens Axboe didst pronounce:
> > On Tue, Sep 25 2007, Mel Gorman wrote:
> > > On (25/09/07 01:11), Kamalesh Babulal didst pronounce:
> > >
> > > Hi Kamalesh,
> > >
> > > > The build fails with following error
> > > >
> > > > CC drivers/block/ps3disk.o
> > > > drivers/block/ps3disk.c: In function ???ps3disk_scatter_gather???:
> > > > drivers/block/ps3disk.c:115: error: ???bio??? undeclared (first use in this
> > > > function)
> > > > drivers/block/ps3disk.c:115: error: (Each undeclared identifier is
> > > > reported only once
> > > > drivers/block/ps3disk.c:115: error: for each function it appears in.)
> > > > drivers/block/ps3disk.c:115: error: ???j??? undeclared (first use in this
> > > > function)
> > > > drivers/block/ps3disk.c:116: error: implicit declaration of function
> > > > ???bio_kunmap_bvec???
> > > > make[2]: *** [drivers/block/ps3disk.o] Error 1
> > > > make[1]: *** [drivers/block] Error 2
> > > > make: *** [drivers] Error 2
> > > >
> > > > The function bio_kunmap_bvec is missing.I tried checking the git-block.patch
> > > > as well as the linux/kernel/git/axboe/linux-2.6-block.git and did not
> > > > find this function.
> > > >
> > > > Previously this function was replaced by __bio_kunmap_atomic();
> > > > This patch does not solves the implicit "declaration of function
> > > > ???bio_kunmap_bvec???"
> > > >
> > > > Signed-off-by: Kamalesh Babulal <[email protected]
> > > > <mailto:[email protected]>>
> > >
> > > Your mailer appears to have mangled both your signoff and the whitespace in
> > > the patch and it does not apply. However, fixing it does not solve the problem
> > > because of this mysterious bio_kunmap_bvec() that is only referenced by this
> > > driver. Was it accidently added during the addition of sg chaining support?
> >
> > This should fix things up.
> >
>
> This builds although I lack the hardware to really test it. However, in
> 2.6.23-rc8-mm1 it collides with git-block-ps3disk-fix.patch. This is a
> version on top of that stack but I guess the best thing to do is replace
> git-block-ps3disk-fix.patch with Jens patch once it is signed off.
>
> Not signing off because this is just a rebase. Assuming the other one
> gets signed off, consider it;
Thanks, but I already integrated the fix into the existing patch, so
that bisect will work.
--
Jens Axboe
Peter Zijlstra wrote:
> On Mon, 24 Sep 2007 21:20:58 +0200 Peter Zijlstra
> <[email protected]> wrote:
>
>>>> Nope, and the stacktrace is utterly puzzling.
>>>>
>>>> /me goes read the lkml.org link
>>>>
>>>> Kamalesh Babulal: do you still get:
>>>> BUG: spinlock bad magic on
>>>>
>>>> msgs?
>>>>
>>>> Because those I could reproduce using fsx, and I fixed all that.
>>> Hi Peter,
>>>
>>> I do not get BUG: spinlock bad magic messages any more, but the softlock message is
>>> thrown more than 30 time, while running the ltp runall.
>> It would be good to know what function on_each_cpu is executing, could
>> you try something like:
>
> I've just completed 2 full ltp runs on a dual-core opteron machine but
> could not reproduce this problem.
>
> Kamalesh, would it be possible for you to reproduce with that patch, so
> we can see what function is holding up the cpu?
Hi Peter,
After running the test with the patch you provided, i observed an oops message
which was at the top of the these soft lockup message and the oops is the same as
the oops reported at http://lkml.org/lkml/2007/9/24/107.
And when i applied the patch for the oops proposed at
http://lkml.org/lkml/2007/9/25/57 the oops as well as the soft lockup's are not seen.
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
From: Marcel Holtmann <[email protected]>
Date: Tue, 25 Sep 2007 00:18:07 +0200
> Hi Wang,
>
> > This patch:
> > - makes hidp_setup_input() return int to indicate errors;
> > - checks its return value to handle errors.
> >
> > And this time it is against -rc7-mm1 tree.
> >
> > Thanks to roel and Marcel Holtmann for comments.
> >
> > Signed-off-by: WANG Cong <[email protected]>
>
> Signed-off-by: Marcel Holtmann <[email protected]>
Applied, thanks.
On 09/24/2007 09:41 PM, Alan Stern wrote:
> On Mon, 24 Sep 2007, Jiri Slaby wrote:
>
>> Hmm, I have usb legacy keyboard switched on because of grub and bios to allow me
>> typing.
>>
>> I booted 23-rc7 4 times, and the latest -mm 3 times just now and can't reproduce
>> it, I just wonder by what is this conditioned.
>
> Warm boot vs. cold boot, maybe.
Hmm, no. I don't know, I can't see it anymore so far (using rc8-mm2). I'll keep
eyes on it, anyways.
thanks,
--
Jiri Slaby ([email protected])
Faculty of Informatics, Masaryk University
On Mon, Sep 24, 2007 at 01:35:31PM +0100, Andy Whitcroft wrote:
> Seeing the following from an older power LPAR, pretty sure we had
> this in the previous -mm also:
I haven't forgetten about this ... and am looking at it now.
Seems that whenever I go to reserve the machine pSeries-102,
someone else is using it :-)
--linas
On Tue, Oct 02, 2007 at 06:28:19PM -0500, Linas Vepstas wrote:
> On Mon, Sep 24, 2007 at 01:35:31PM +0100, Andy Whitcroft wrote:
> > Seeing the following from an older power LPAR, pretty sure we had
> > this in the previous -mm also:
>
> I haven't forgetten about this ... and am looking at it now.
> Seems that whenever I go to reserve the machine pSeries-102,
> someone else is using it :-)
This panic is caused by "[POWERPC] pseries: Fix jumbled no_logging flag."
(79c0108d1b9db4864ab77b2a95dfa04f2dcf264c), in the powerpc/for-2.6.24
branch. It looks to me that we have logging enabled too early now.
I think the following is a reasonable fix?
---
Explicitly enable RTAS error logging, when it should be ready.
Signed-off-by: Tony Breeds <[email protected]>
---
arch/powerpc/platforms/pseries/rtasd.c | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/platforms/pseries/rtasd.c b/arch/powerpc/platforms/pseries/rtasd.c
index 30925d2..0df5d0d 100644
--- a/arch/powerpc/platforms/pseries/rtasd.c
+++ b/arch/powerpc/platforms/pseries/rtasd.c
@@ -54,7 +54,10 @@ static unsigned int rtas_event_scan_rate;
static int full_rtas_msgs = 0;
/* Stop logging to nvram after first fatal error */
-static int no_more_logging;
+static int no_more_logging = 1; /* Until we initialize everything,
+ * make sure we don't try logging
+ * anything */
+
static int error_log_cnt;
@@ -414,6 +417,8 @@ static int rtasd(void *unused)
memset(logdata, 0, rtas_error_log_max);
rc = nvram_read_error_log(logdata, rtas_error_log_max,
&err_type, &error_log_cnt);
+ /* We can use rtas_log_buf now */
+ no_more_logging = 0;
if (!rc) {
if (err_type != ERR_FLAG_ALREADY_LOGGED) {
Yours Tony
linux.conf.au http://linux.conf.au/ || http://lca2008.linux.org.au/
Jan 28 - Feb 02 2008 The Australian Linux Technical Conference!
On Wed, 2007-10-03 at 10:26 +1000, Tony Breeds wrote:
> On Tue, Oct 02, 2007 at 06:28:19PM -0500, Linas Vepstas wrote:
> > On Mon, Sep 24, 2007 at 01:35:31PM +0100, Andy Whitcroft wrote:
> > > Seeing the following from an older power LPAR, pretty sure we had
> > > this in the previous -mm also:
> >
> > I haven't forgetten about this ... and am looking at it now.
> > Seems that whenever I go to reserve the machine pSeries-102,
> > someone else is using it :-)
>
> This panic is caused by "[POWERPC] pseries: Fix jumbled no_logging flag."
> (79c0108d1b9db4864ab77b2a95dfa04f2dcf264c), in the powerpc/for-2.6.24
> branch. It looks to me that we have logging enabled too early now.
>
> I think the following is a reasonable fix?
>
> ---
> Explicitly enable RTAS error logging, when it should be ready.
>
>
> Signed-off-by: Tony Breeds <[email protected]>
>
> ---
>
> arch/powerpc/platforms/pseries/rtasd.c | 7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/arch/powerpc/platforms/pseries/rtasd.c b/arch/powerpc/platforms/pseries/rtasd.c
> index 30925d2..0df5d0d 100644
> --- a/arch/powerpc/platforms/pseries/rtasd.c
> +++ b/arch/powerpc/platforms/pseries/rtasd.c
> @@ -54,7 +54,10 @@ static unsigned int rtas_event_scan_rate;
> static int full_rtas_msgs = 0;
>
> /* Stop logging to nvram after first fatal error */
> -static int no_more_logging;
> +static int no_more_logging = 1; /* Until we initialize everything,
> + * make sure we don't try logging
> + * anything */
> +
I realise it'll make the patch bigger, but this doesn't seem like a
particularly good name for the variable anymore.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
On Wed, Oct 03, 2007 at 10:30:16AM +1000, Michael Ellerman wrote:
> I realise it'll make the patch bigger, but this doesn't seem like a
> particularly good name for the variable anymore.
Sure, what about?
Clarify when RTAS logging is enabled.
Signed-off-by: Tony Breeds <[email protected]>
---
arch/powerpc/platforms/pseries/rtasd.c | 15 +++++++++------
1 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/arch/powerpc/platforms/pseries/rtasd.c b/arch/powerpc/platforms/pseries/rtasd.c
index 30925d2..73401c8 100644
--- a/arch/powerpc/platforms/pseries/rtasd.c
+++ b/arch/powerpc/platforms/pseries/rtasd.c
@@ -54,8 +54,9 @@ static unsigned int rtas_event_scan_rate;
static int full_rtas_msgs = 0;
/* Stop logging to nvram after first fatal error */
-static int no_more_logging;
-
+static int logging_enabled; /* Until we initialize everything,
+ * make sure we don't try logging
+ * anything */
static int error_log_cnt;
/*
@@ -217,7 +218,7 @@ void pSeries_log_error(char *buf, unsigned int err_type, int fatal)
}
/* Write error to NVRAM */
- if (!no_more_logging && !(err_type & ERR_FLAG_BOOT))
+ if (logging_enabled && !(err_type & ERR_FLAG_BOOT))
nvram_write_error_log(buf, len, err_type, error_log_cnt);
/*
@@ -229,8 +230,8 @@ void pSeries_log_error(char *buf, unsigned int err_type, int fatal)
printk_log_rtas(buf, len);
/* Check to see if we need to or have stopped logging */
- if (fatal || no_more_logging) {
- no_more_logging = 1;
+ if (fatal || !logging_enabled) {
+ logging_enabled = 0;
spin_unlock_irqrestore(&rtasd_log_lock, s);
return;
}
@@ -302,7 +303,7 @@ static ssize_t rtas_log_read(struct file * file, char __user * buf,
spin_lock_irqsave(&rtasd_log_lock, s);
/* if it's 0, then we know we got the last one (the one in NVRAM) */
- if (rtas_log_size == 0 && !no_more_logging)
+ if (rtas_log_size == 0 && logging_enabled)
nvram_clear_error_log();
spin_unlock_irqrestore(&rtasd_log_lock, s);
@@ -414,6 +415,8 @@ static int rtasd(void *unused)
memset(logdata, 0, rtas_error_log_max);
rc = nvram_read_error_log(logdata, rtas_error_log_max,
&err_type, &error_log_cnt);
+ /* We can use rtas_log_buf now */
+ logging_enabled = 1;
if (!rc) {
if (err_type != ERR_FLAG_ALREADY_LOGGED) {
Yours Tony
linux.conf.au http://linux.conf.au/ || http://lca2008.linux.org.au/
Jan 28 - Feb 02 2008 The Australian Linux Technical Conference!
On Wed, 2007-10-03 at 11:19 +1000, Tony Breeds wrote:
> On Wed, Oct 03, 2007 at 10:30:16AM +1000, Michael Ellerman wrote:
>
> > I realise it'll make the patch bigger, but this doesn't seem like a
> > particularly good name for the variable anymore.
>
> Sure, what about?
Better .. but .. :D
> diff --git a/arch/powerpc/platforms/pseries/rtasd.c b/arch/powerpc/platforms/pseries/rtasd.c
> index 30925d2..73401c8 100644
> --- a/arch/powerpc/platforms/pseries/rtasd.c
> +++ b/arch/powerpc/platforms/pseries/rtasd.c
> @@ -54,8 +54,9 @@ static unsigned int rtas_event_scan_rate;
> static int full_rtas_msgs = 0;
>
> /* Stop logging to nvram after first fatal error */
> -static int no_more_logging;
> -
> +static int logging_enabled; /* Until we initialize everything,
> + * make sure we don't try logging
> + * anything */
Until we initialise what exactly?
> static int error_log_cnt;
>
> /*
> @@ -217,7 +218,7 @@ void pSeries_log_error(char *buf, unsigned int err_type, int fatal)
> }
>
> /* Write error to NVRAM */
> - if (!no_more_logging && !(err_type & ERR_FLAG_BOOT))
> + if (logging_enabled && !(err_type & ERR_FLAG_BOOT))
> nvram_write_error_log(buf, len, err_type, error_log_cnt);
>
> /*
> @@ -229,8 +230,8 @@ void pSeries_log_error(char *buf, unsigned int err_type, int fatal)
> printk_log_rtas(buf, len);
>
> /* Check to see if we need to or have stopped logging */
> - if (fatal || no_more_logging) {
> - no_more_logging = 1;
> + if (fatal || !logging_enabled) {
> + logging_enabled = 0;
> spin_unlock_irqrestore(&rtasd_log_lock, s);
> return;
> }
Hmmm, this routine has 4 separate lock-dropping exit paths ..
> @@ -302,7 +303,7 @@ static ssize_t rtas_log_read(struct file * file, char __user * buf,
>
> spin_lock_irqsave(&rtasd_log_lock, s);
> /* if it's 0, then we know we got the last one (the one in NVRAM) */
> - if (rtas_log_size == 0 && !no_more_logging)
> + if (rtas_log_size == 0 && logging_enabled)
> nvram_clear_error_log();
> spin_unlock_irqrestore(&rtasd_log_lock, s);
>
> @@ -414,6 +415,8 @@ static int rtasd(void *unused)
> memset(logdata, 0, rtas_error_log_max);
> rc = nvram_read_error_log(logdata, rtas_error_log_max,
> &err_type, &error_log_cnt);
> + /* We can use rtas_log_buf now */
> + logging_enabled = 1;
>
> if (!rc) {
> if (err_type != ERR_FLAG_ALREADY_LOGGED) {
What exactly happens that allows us to do logging? I don't see any
ordering between anything else and the setting of the flag, and AFAICT
we're not inside a spinlock or anything here.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
On Wed, Oct 03, 2007 at 02:09:46PM +1000, Michael Ellerman wrote:
>
> Until we initialise what exactly?
Until we allocate the error log buffer. The original crash was
for a null-pointer deref of the unallocated buffer. I just sent
out a patch to fix this; its a bit simpler than the below.
In that email, I remarked:
Andy Whitcroft's crash was appearently due to firmware complaining
about lost power, (actually, lost power supply redundancy!), which
occurred very early during boot.
Type 00000040 (EPOW)
Status: bypassed new
Residual error from previous boot.
EPOW Sensor Value: 00000002
EPOW warning due to loss of redundancy.
EPOW general power fault.
I've no clue why firmware thought it was OK to report this
during one of the earliest calls to RTAS; I'm still investiigating
that.
--linas
On 10/2/07, Tony Breeds <[email protected]> wrote:
> On Wed, Oct 03, 2007 at 10:30:16AM +1000, Michael Ellerman wrote:
>
> > I realise it'll make the patch bigger, but this doesn't seem like a
> > particularly good name for the variable anymore.
>
> Sure, what about?
>
> Clarify when RTAS logging is enabled.
>
> Signed-off-by: Tony Breeds <[email protected]>
For what it's worth, on a different ppc64 box, this resolves a similar
panic for me.
Tested-by: Nishanth Aravamudan <[email protected]>
Thanks,
Nish
On Thu, Oct 04, 2007 at 05:01:47PM -0700, Nish Aravamudan wrote:
> On 10/2/07, Tony Breeds <[email protected]> wrote:
> > On Wed, Oct 03, 2007 at 10:30:16AM +1000, Michael Ellerman wrote:
> >
> > > I realise it'll make the patch bigger, but this doesn't seem like a
> > > particularly good name for the variable anymore.
> >
> > Sure, what about?
> >
> > Clarify when RTAS logging is enabled.
> >
> > Signed-off-by: Tony Breeds <[email protected]>
>
> For what it's worth, on a different ppc64 box, this resolves a similar
> panic for me.
>
> Tested-by: Nishanth Aravamudan <[email protected]>
For the reasons explained, I'd really like to nack Tony's patch.
--linas
On 10/5/07, Linas Vepstas <[email protected]> wrote:
> On Thu, Oct 04, 2007 at 05:01:47PM -0700, Nish Aravamudan wrote:
> > On 10/2/07, Tony Breeds <[email protected]> wrote:
> > > On Wed, Oct 03, 2007 at 10:30:16AM +1000, Michael Ellerman wrote:
> > >
> > > > I realise it'll make the patch bigger, but this doesn't seem like a
> > > > particularly good name for the variable anymore.
> > >
> > > Sure, what about?
> > >
> > > Clarify when RTAS logging is enabled.
> > >
> > > Signed-off-by: Tony Breeds <[email protected]>
> >
> > For what it's worth, on a different ppc64 box, this resolves a similar
> > panic for me.
> >
> > Tested-by: Nishanth Aravamudan <[email protected]>
>
> For the reasons explained, I'd really like to nack Tony's patch.
I see. Can you reply in this thread with the patch you mentioned in
your other reply? (or point me to a copy of it)
Thanks,
Nish