Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

2.6.12-mm2

0 views
Skip to first unread message

Andrew Morton

unread,
Jun 26, 2005, 7:12:19 AM6/26/05
to linux-...@vger.kernel.org

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm2/


- A reminder that there is a vger mailing list for tracking patches which
are added to -mm. Do

`echo subscribe mm-commits | mail majo...@vger.kernel.org'

- Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get
the recent PCI breakage sorted out.

- Big arch/cris update.


Changes since 2.6.12-mm1:


-x86_64-task_size-fixes-for-compatibility-mode-processes.patch
-smp_processor_id-cleanup.patch
-smp_processor_id-cleanup-fix.patch
-git-alsa-fix.patch
-git-alsa-usbaudio-fix.patch
-gregkh-driver-driver-device_attr-08-fix.patch
-gregkh-i2c-i2c-ds1374-01-fix.patch
-toshiba-driver-cleanup.patch
-i8k-pass-through-lindent.patch
-i8k-use-standard-dmi-interface.patch
-i8k-convert-to-seqfile.patch
-i8k-initialization-code-cleanup-formatting.patch
-i8k-add-new-bios-signatures.patch
-biarch-compiler-support-for-i386.patch
-use-cross_compileinstallkernel-in-arch-boot-installsh.patch
-ipvs-add-and-reorder-bh-locks-after-moving-to-keventd.patch
-drivers-net-chelsio-cxgb2-use-the-dma_3264bit_mask-constants.patch
-tcp-fastroute-stats-remove.patch
-tcp-no-congestion.patch
-tcp-no-throttle.patch
-tcp-bigger-backlog.patch
-tcp-tcp_super_tso_v3.patch
-tcp-tcp_infra.patch
-tcp-tcp_bic.patch
-tcp-tcp_westwood.patch
-tcp-hstcp.patch
-tcp-hybla.patch
-tcp-vegas.patch
-tcp-h-tcp.patch
-tcp-scaleable_tcp.patch
-gregkh-pci-pci-driver-device_attr-fixup.patch
-vmscan-notice-slab-shrinking.patch
-madvise-do-not-split-the-maps.patch
-madvise-merge-the-maps.patch
-remove-non-discontig-use-of-pgdat-node_mem_map.patch
-resubmit-sparsemem-base-early_pfn_to_nid-works-before-sparse-is-initialized.patch
-resubmit-sparsemem-base-simple-numa-remap-space-allocator.patch
-resubmit-sparsemem-base-reorganize-page-flags-bit-operations.patch
-resubmit-sparsemem-base-teach-discontig-about-sparse-ranges.patch
-create-mm-kconfig-for-arch-independent-memory-options.patch
-make-each-arch-use-mm-kconfig.patch
-make-each-arch-use-mm-kconfig-fix.patch
-update-all-defconfigs-for-arch_discontigmem_enable.patch
-introduce-new-kconfig-option-for-numa-or-discontig.patch
-sparsemem-fix-minor-defaults-issue-in-mm-kconfig.patch
-mm-kconfig-kill-unused-arch_flatmem_disable.patch
-mm-kconfig-hide-memory-model-selection-menu.patch
-mm-kconfig-give-discontig-more-help-text.patch
-ppc64-kconfig-memory-models.patch
-generify-early_pfn_to_nid.patch
-generify-memory-present.patch
-sparsemem-memory-model.patch
-sparsemem-memory-model-fix.patch
-sparsemem-memory-model-fix-3.patch
-sparsemem-memory-model-fix-4.patch
-sparsemem-memory-model-fix-5.patch
-sparsemem-memory-model-fix-6.patch
-sparsemem-memory-model-section-numbers-unsigned-long.patch
-sparsemem-memory-model-for-i386.patch
-sparsemem-memory-model-for-i386-fix.patch
-sparsemem-swiss-cheese-numa-layouts.patch
-sparsemem-hotplug-base.patch
-sparsemem-hotplug-base-fix.patch
-sparsemem-hotplug-base-abstract-section-number-to-section-mapping.patch
-ppc64-add-early_pfn_to_nid.patch
-ppc64-add-memory-present.patch
-ppc64-sparsemem-memory-model.patch
-ppc64-sparsemem-memory-model-fix.patch
-ppc64-sparsemem-memory-model-fix-2.patch
-remove-direct-ref-to-contig_page_data-for-x86-64.patch
-add-x86-64-kconfig-options-for-sparsemem.patch
-reorganize-x86-64-numa-and-discontigmem-config-options.patch
-add-x86-64-specific-support-for-sparsemem.patch
-add-x86-64-specific-support-for-sparsemem-tidy.patch
-add-page_state-info-to-show_mem.patch
-add-page_state-info-to-show_mem-warning-fixes.patch
-mm-add-proc-zoneinfo.patch
-vm-add-may_swap-flag-to-scan_control.patch
-vm-early-zone-reclaim.patch
-vm-early-zone-reclaim-tidy.patch
-vm-add-__gfp_noreclaim.patch
-vm-rate-limit-early-reclaim.patch
-hugepage-consolidation.patch
-hugepage-consolidation-fix.patch
-hugepage-consolidation-fix-fix.patch
-hugepage-consolidation-ia64-fix.patch
-node-local-per-cpu-pages.patch
-node-local-per-cpu-pages-tidy.patch
-node-local-per-cpu-pages-tidy-2.patch
-node-local-per-cpu-pages-tidy-2-fix.patch
-avoiding-mmap-fragmentation.patch
-avoiding-mmap-fragmentation-tidy.patch
-avoiding-mmap-fragmentation-fix.patch
-avoiding-mmap-fragmentation-revert-unneeded-64-bit-changes.patch
-avoiding-mmap-fragmentation-revert-unneeded-64-bit-changes-vs-x86_64-task_size-fixes-for-compatibility-mode-processes.patch
-avoiding-mmap-fragmentation-revert-unneeded-64-bit-changes-vs-x86_64-task_size-fixes-for-compatibility-mode-processes-fix.patch
-avoiding-mmap-fragmentation-fix-2.patch
-avoiding-mmap-fragmentation-fix-3.patch
-mmap-topdown-fix-for-large-stack-limit-large-allocation.patch
-#avoiding-mmap-fragmentation-clean-rev.patch
-mm-remove-pg_highmem.patch
-mm-remove-pg_highmem-tidy.patch
-vm-try_to_free_pages-unused-argument.patch
-__mod_page_state-pass-unsigned-long-instead-of-unsigned.patch
-__read_page_state-pass-unsigned-long-instead-of-unsigned.patch
-add-oom-debug.patch
-periodically-drain-non-local-pagesets.patch
-periodically-drain-non-local-pagesets-fix.patch
-reduce-size-of-huge-boot-per_cpu_pageset.patch
-ia64-uncached-alloc.patch
-sn2-xpc-build-patches.patch
-shmem-restore-superblock-info.patch
-mbind-fix-verify_pages-pte_page.patch
-mbind-check_range-use-standard-ptwalk.patch
-dup_mmap-update-comment-on-new-vma.patch
-bad_page-clear-reclaim-and-slab.patch
-rme96xx-fix-pagereserved-range.patch
-get_user_pages-kill-get_page_map.patch
-do_wp_page-cannot-share-file-page.patch
-can_share_swap_page-use-page_mapcount.patch
-msync-check-pte-dirty-earlier.patch
-kill-stray-newline.patch
-netfilter-debug-locking-fix.patch
-tulip-fixes-for-uli5261.patch
-3c509-device-support.patch
-ppp_mppe-add-ppp-mppe-encryption-module-kconfig-fix.patch
-dm9000-network-driver-bugfix.patch
-x25-selective-sub-address-matching-with.patch
-x25-selective-sub-address-matching-with-fix.patch
-x25-fast-select-with-no-restriction-on.patch
-sunzilog-warning-fixes.patch
-ppp-handle-misaligned-accesses.patch
-3c59x-remove-superfluous-vortex_debug-test-from-boomerang_start_xmit.patch
-kbuild-display-compile-version.patch
-vfs-memory-leak-in-do_kern_mount.patch
-selinux-memory-leak-in-selinux_sb_copy_data.patch
-ppc32-added-support-for-new-mpc8548-family-of-powerquicc.patch
-ppc32-added-preliminary-support-for-the-mpc8548-cds-board.patch
-ppc32-removed-dependency-on-config_cpm2-for-building.patch
-ppc32-converted-mpc10x-bridge-to-use-platform.patch
-cpm_uart-route-scc2-pins-for-the-stx-gp3-board.patch
-ppc32-fix-config_task_size-handling-on-40x.patch
-ppc32-add-support-for-mpc8245-8250-serial-ports-on-sandpoint.patch
-ppc32-remove-orphaned-ppc4xx_kgdbc.patch
-ppc32-added-support-for-all-mpc8548-internal-interrupts.patch
-ppc32-clean-up-num_tlbcams-usage-for-freescale-book-e-ppcs.patch
-ppc32-factor-out-common-exception-code-into-macros-for.patch
-ppc32-remove-some-unnecessary-includes-of-promh.patch
-ppc32-dont-recursively-crash-in-die-on-chrp-prep-machines.patch
-ppc32-kill-embedded-systemmap-use-kallsyms.patch
-ppc64-abolish-ioremap_mm.patch
-ppc64-quieten-rtas-printks.patch
-ppc64-override-command-line-as-ld-cc-variables-when-adding-m64-and-co-for-biarch-compilers.patch
-ppc64-use-cpu_has_feature-macro.patch
-ppc64-iseries-remove-iseries_proch.patch
-ppc64-iseries-header-file-white-space-cleanups.patch
-ppc64-iseries-more-header-file-white-space-cleanups.patch
-ppc64-iseries-obvious-code-simplifications.patch
-ppc64-iseries-remove-lpardatah.patch
-ppc64-iseries-eliminate-some-unused-inline-functions.patch
-ppc64-iseries-remove-hvcallcfgh.patch
-ppc64-iseries-cleanup-itlpqueueh.patch
-ppc64-iseries-tidy-up-some-includes-and-hvcallh.patch
-ppc64-iseries-misc-header-cleanups.patch
-ppc64-iseries-remove-iseries_pci_resetc.patch
-ppc64-iseries-iommuh-cleanups.patch
-ppc64-iseries-iseries_vpdinfoc-cleanups.patch
-ppc64-iseries-iseries_pcih-cleanups.patch
-ppc64-iseries-remove-ioretry-from-iseries_device_node.patch
-ppc64-iseries-remove-some-more-members-of.patch
-ppc64-iseries-irq-simple-cleanups.patch
-ppc64-iseries-remove-xmpcilpeventc.patch
-ppc64-iseries-tidy-up-irq-code-after-merge.patch
-ppc64-iseries-allow-build-with-no-pci.patch
-ppc64-tidy-up-vio-devices-fake-parent.patch
-mips-add-vr41xx-gpio-support.patch
-mips-add-vr41xx-gpio-support-fix.patch
-#sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
-platform-smis-and-their-interferance-with-tsc-based-delay-calibration.patch
-platform-smis-and-their-interferance-with-tsc-based-delay-calibration-fix.patch
-m32r-build-fix-for-asm-m32r-topologyh.patch
-ppc64-pcibus_to_node-fix.patch
-x86-x86_64-pcibus_to_node.patch
-x86-x86_64-pcibus_to_node-fix.patch
-fix-pcibus_to_node-for-x86_64.patch
-allow-pcibus_to_node-to-return-undetermined.patch
-numa-aware-block-device-control-structure-allocation.patch
-numa-aware-block-device-control-structure-allocation-tidy.patch
-i386-never-block-forced-sigsegv.patch
-do-not-enforce-unique-io_apic_id-check-for-xapic-systems-i386.patch
-adjust-i386-watchdog-tick-calculation.patch
-allow-early-printk-to-use-more-than-25-lines.patch
-i386-selectable-frequency-of-the-timer-interrupt.patch
-i386-selectable-frequency-of-the-timer-interrupt-fix.patch
-ia64-selectable-timer-interrupt-frequency.patch
-x86-avoid-wasting-irqs-for-pci-devices.patch
-via-82c586b-irq-routing-fix.patch
-x86-include-asm-uaccessh-in-asm-checksumh.patch
-x86-remove-i386_ksymsc-almost.patch
-x86-cpu_khz-type-fix.patch
-x86_64-i8259c-iso99-structure-initialization.patch
-x86_64-fix-hpet-for-systems-that-dont-support-legacy.patch
-optimise-storage-of-read-mostly-variables.patch
-optimise-storage-of-read-mostly-variables-fix.patch
-optimise-storage-of-read-mostly-variables-x86_64-fix.patch
-optimise-storage-of-read-mostly-variables-x86_64-fix-fix.patch
-optimise-storage-of-read-mostly-variables-x86_64-fix-fix-fix.patch
-move-some-more-structures-into-mostly_readonly-and-readonly.patch
-x86_64-never-block-forced-sigsegv.patch
-x86_64-eliminate-duplicate-rdpmc-definition.patch
-x86_64-avoid-wasting-irqs.patch
-dmi-move-acpi-boot-quirk.patch
-dmi-move-acpi-sleep-quirk.patch
-dmi-move-acpi-sleep-quirk-fix.patch
-dmi-remove-central-blacklist.patch
-dmi-code-spring-cleanup.patch
-xen-x86-add-macro-for-debugreg.patch
-xen-x86-use-new-macro-for-debugreg.patch
-xen-x86-rename-usermode-macro.patch
-xen-x86-rename-usermode-macro-fix.patch
-xen-x86-use-more-usermode-macro.patch
-xen-x86_64-add-macro-for-debugreg.patch
-xen-x86_64-use-more-usermode-macro.patch
-ptrace_h8300-condition-bugfix.patch
-arm-irqs_disabled-type-fix.patch
-ioc4-core-driver-rewrite.patch
-ioc4-config-split.patch
-ioc4-pci-bus-speed-detection.patch
-variable-overflow-after-hundreds-round-of-hotplug-cpu.patch
-i386-cpu-hotplug-updated-for-mm.patch
-i386-cpu-hotplug-updated-for-mm-smp_processor_id-cleanup-fix.patch
-i386-dont-use-ipi-broadcast-when-using-cpu-hotplug.patch
-sep-initializing-rework.patch
-sep-initializing-rework-fix.patch
-sep-initializing-rework-cleanup.patch
-i386-hold-call_lock-when-updating-cpu_online_map.patch
-sibling-map-initializing-rework.patch
-sibling-map-initializing-rework-smp_processor_id-cleanup-fix.patch
-init-call-cleanup.patch
-cpu-state-clean-after-hot-remove.patch
-cpu-state-clean-after-hot-remove-smp_processor_id-cleanup-fix.patch
-cpu-state-clean-after-hot-remove-set-cpu_state-for-cpu-hotplug.patch
-cpu-state-clean-after-hot-remove-fix.patch
-cpu-state-clean-after-hot-remove-fix-2.patch
-physical-cpu-hot-add.patch
-physical-cpu-hot-add-fix.patch
-suspend-resume-smp-support.patch
-suspend-resume-smp-support-fix.patch
-suspend-resume-smp-support-fix-2.patch
-suspend-resume-smp-support-fix-3.patch
-swsusp-documentation-updates.patch
-swsusp-kill-config_pm_disk.patch
-s-t-ram-load-gdt-the-right-way.patch
-acpi-fix-video-docs.patch
-properly-stop-devices-before-poweroff.patch
-properly-stop-devices-before-poweroff-fix.patch
-swsusp-kill-unneccessary-does_collide_order.patch
-swsusp-cleanup-whitespace.patch
-swsusp-fix-nr_copy_pages.patch
-swsusp-clean-assembly-parts.patch
-cpu-hotplug-printk-fix.patch
-suspend-pci-power-managment-reference-implementation.patch
-swsusp-only-allow-it-when-it-makes-sense.patch
-update-video-after-suspend-documentation.patch
-x86_64-change-init-sections-for-cpu-hotplug-support.patch
-x86_64-change-init-sections-for-cpu-hotplug-support-fix.patch
-x86_64-cpu-hotplug-support.patch
-x86_64-cpu-hotplug-support-fix.patch
-x86_64-cpu-hotplug-sibling-map-cleanup.patch
-x86_64-dont-use-broadcast-shortcut-to-make-it-cpu-hotplug-safe.patch
-x86_64-dont-use-broadcast-shortcut-to-make-it-cpu-hotplug-safe-fix.patch
-x86_64-dont-use-broadcast-shortcut-to-make-it-cpu-hotplug-safe-fix-set-cpu_state-for-cpu-hotplug.patch
-x86_64-provide-ability-to-choose-using-shortcuts-for-ipi-in-flat-mode.patch
-set-cpu_state-for-cpu-hotplug-ia64.patch
-m32r-support-m3a-2170mappi-iii-platform.patch
-m32r-support-m3a-2170mappi-iii-platform-fix.patch
-m32r-support-m3a-2170mappi-iii-platform-fix-2.patch
-m32r-update-setup_xxxxxc.patch
-m32r-update-m32r_cfc-to-support-mappi-iii.patch
-m32r-update-m32r_cfc-to-support-mappi-iii-fix.patch
-m32r-cleanup-arch-m32r-mm-extablec.patch
-m32r-remove-include-asm-m32r-m32102perih.patch
-m32r-update-defconfig-files.patch
-m32r-use-asm-generic-div64h.patch
-uml-add-and-use-generic-hw_controller_type-release.patch
-uml-complete-hw_controller_type-release-conversion.patch
-uml-make-hw_controller_type-release-exist-only-for-archs-needing-it.patch
-uml-link-tt-mode-against-nptl.patch
-s390-cio-max-channels-checks.patch
-s390-cio-documentation.patch
-s390-ifdefs-in-compat_ioctls.patch
-s390-kernel-stack-overflow-panic.patch
-s390-cmm-sender-parameter-visibility.patch
-s390-memory-detection-32gb.patch
-s390-pending-interrupt-after-ipl-from-reader.patch
-mtrr-size-and-base-debug.patch
-blk-use-find_first_zero_bit-in-blk_queue_start_tag.patch
-blk-remove-blk_queue_tag-real_max_depth-optimization.patch
-blk-remove-blk_tags_per_longmask.patch
-blk-cleanup-generic-tag-support-error-messages.patch
-blk-no-memory-barrier.patch
-blk-branch-hints.patch
-blk-unplug-later.patch
-keys-discard-key-spinlock-and-use-rcu-for-key-payload.patch
-keys-discard-key-spinlock-and-use-rcu-for-key-payload-try-4.patch
-keys-pass-session-keyring-to-call_usermodehelper.patch
-keys-pass-session-keyring-to-call_usermodehelper-fix.patch
-keys-use-rcu-to-manage-session-keyring-pointer.patch
-keys-make-request-key-create-an-authorisation-key.patch
-keys-make-request-key-create-an-authorisation-key-fix.patch
-ecryptfs-export-user-key-type.patch
-timers-fixes-improvements.patch
-timers-fixes-improvements-smp_processor_id-fix.patch
-timers-fixes-improvements-fix.patch
-timers-fixes-improvements-smp_processor_id-cleanup-fix.patch
-timers-fix-__mod_timer-vs-__run_timers-deadlock.patch
-timers-fix-__mod_timer-vs-__run_timers-deadlock-tidy.patch
-timers-comments-update.patch
-kernel-timerc-remove-a-goto-construct.patch
-timers-introduce-try_to_del_timer_sync.patch
-posix-timers-use-try_to_del_timer_sync.patch
-fix-for-prune_icache-forced-final-iput-races.patch
-create-a-kstrdup-library-function.patch
-create-a-kstrdup-library-function-fixes.patch
-create-a-kstrdup-library-function-fix-include-slab.patch
-create-a-kstrdup-library-function-ppc-fix.patch
-kstrdup-convert-a-few-existing-implementations.patch
-con_consdev-bit-not-set-correctly-on-last-console.patch
-as-limit-queue-depth.patch
-as-limit-queue-depth-fix.patch
-generate-hotplug-events-for-cpu-online.patch
-optimise-loop-driver-a-bit.patch
-optimise-loop-driver-a-bit-tidy.patch
-streamline-preempt_count-type-across-archs.patch
-preempt_count-is-int-remove-cast-and-dont-assign-to.patch
-add-check-to-proc-devices-read-routines.patch
-rpc-kick-off-socket-connect-operations-faster.patch
-remove-register_ioctl32_conversion-and-unregister_ioctl32_conversion.patch
-remove-duplicate-get_dentry-functions-in-various-places.patch
-avoid-recursive-oopses.patch
-quota-consolidate-code-surrounding-vfs_quota_on_mount.patch
-quota-sanitize-dentry-handling-in-vfs_quota_on_mount.patch
-kprobes-function-return-probes.patch
-kprobes-function-return-probes-fix.patch
-kprobes-function-return-probes-fix-2.patch
-kprobes-function-return-probes-fix-3.patch
-kprobes-function-return-probes-fix-4.patch
-kprobes-move-aggregate-probe-handlers-and-few-return-probe-routines-to-static.patch
-kprobes-arch_supports_kretprobes-cleanup.patch
-kprobes-function-return-probes-fix-5.patch
-x86_64-specific-function-return-probes.patch
-move-kprobe-arming-into-arch-specific-code.patch
-kprobes-moves-lock-unlock-to-non-arch-kprobe_flush_task.patch
-kprobes-ia64-kdebug-die-notification.patch
-kprobes-ia64-kdebug-die-notification-fix.patch
-kprobes-ia64-arch-specific-handling-of-kprobes.patch
-kprobes-ia64-arch-specific-handling-of-kprobes-fix.patch
-kprobes-ia64-architecture-specific-support.patch
-kprobes-ia64-support-kprobe-on-branch-call-instructions.patch
-kprobes-ia64-cleanup.patch
-kprobes-ia64-qp-fix.patch
-kprobes-ia64-cleanup-2.patch
-kprobes-ia64-cmp-ctype-unc-support.patch # fold
-kprobes-ia64-safe-register-kprobe.patch
-kprobes-ia64-check-jprobe-break-before-handling.patch
-kprobes-temporary-disarming-of-reentrant-probe.patch
-kprobes-temporary-disarming-of-reentrant-probe-for-i386.patch
-kprobes-temporary-disarming-of-reentrant-probe-for-x86_64.patch
-kprobes-temporary-disarming-of-reentrant-probe-for-x86_64-fix.patch
-kprobes-temporary-disarming-of-reentrant-probe-for-ppc64.patch
-kprobes-temporary-disarming-of-reentrant-probe-for-sparc64.patch
-kprobes-temporary-disarming-of-reentrant-probe-for-ia64.patch
-allow-a-jprobe-to-coexist-with-muliple-kprobes.patch
-setuid-core-dump.patch
-support-for-dx-directories-in-ext3_get_parent-nfsd.patch
-document-the-fact-that-linux-arm-kernel-is-subscribers-only.patch
-add-some-comments-to-lookup_create.patch
-fix-of-bogus-file-max-limit-messages.patch
-software-suspend-and-recalc-sigpending-bug-fix.patch
-o1-sb-list-traversing-on-syncs.patch
-26-altix-shut-off-xmit-intr-if-done-xmitting.patch
-parport-netmos-nm9855-fix.patch
-dont-force-o_largefile-for-32-bit-processes-on-ia64-2612-rc3.patch
-ide-floppy-adjustments.patch
-adjust-per_cpu-definition-in-non-smp-case.patch
-apply-quotation-handling-to-makefilebuild.patch
-mempool-only-init-waitqueue-in-slow-path.patch
#seccomp-disable-tsc-for-seccomp-enabled-tasks.patch
-factor-out-common-code-in-sys_fsync-sys_fdatasync.patch
-improve-cd-dvd-packet-driver-write-performance.patch
-remove-eventpoll-macro-obfuscation.patch
-optimize-sys_times-for-a-single-thread-process.patch
-optimize-sys_times-for-a-single-thread-process-update.patch
-optimize-sys_times-for-a-single-thread-process-update-2.patch
-turn-off-sibling-call-optimization-w-frame-pointers.patch
-ipcsem-remove-superflous-decrease-variable-from-sys_semtimedop.patch
-e1000-numa-aware-allocation-of-descriptors-v2.patch
-gconfig-only-show-scrollbars-if-needed.patch
-potential-null-pointer-dereference-in-amiga-serial-driver.patch
-add-offseth-to-dontdiff.patch
-yenta-ti-turn-off-interrupts-during-card-power-on-more-2.patch
-compat-introduce-compat_time_t.patch
-cs4236-irq-handling-fix.patch
-block-add-unlocked_ioctl-support-for-block-devices.patch
-pcdp-handle-tables-that-dont-supply-baud-rate.patch
-remove-f_error-field-from-struct-file.patch
-use-drivers-kconfig-for-sparc32.patch
-acl-endianess-annotations.patch
-remove-linux-xattr_aclh.patch
-bug-in-error-recovery-in-fs-bufferc__block_prepare_write.patch
-dpt_i2o-waitqueue-fix.patch
-aio-fix-do_sync_readwrite-to-properly-handle-aio-retries.patch
-aio-make-wait_queue-task-private.patch
-add-note-about-verify_area-removal-to.patch
-ide-cd-reports-current-speed.patch
-pwc-uncompress-warning-fix.patch
-introduce-tty_unregister_ldisc.patch
-convert-users-to-tty_unregister_ldisc.patch
-ibmasm-driver-fix-command-buffer-size.patch
-ibmasm-driver-correctly-wake-up-sleeping-threads.patch
-ibmasm-driver-redesign-handling-of-remote-control.patch
-ibmasm-driver-redesign-handling-of-remote-control-fix.patch
-ibmasm-driver-fix-race-in-command-refcount-logic.patch
-autofs4-avoid-panic-on-bind-mount-of-autofs-owned-directory.patch
-autofs4-post-expire-race-fix.patch
-autofs4-bad-lookup-fix.patch
-autofs4-subversion-bump-to-identify-these-changes.patch
-pass-iocb-to-dio_iodone_t.patch
-reiserfs-add-checking-of-journal_begin-return-value.patch
-quota-improve-credits-estimates.patch
-quota-ext3-improve-quota-credit-estimates.patch
-quota-reiserfs-improve-quota-credit-estimates.patch
-xtensa-tensilica-xtensa-cpu-arch-maintainer-record.patch
-xtensa-architecture-support-for-tensilica-xtensa-part-1.patch
-xtensa-architecture-support-for-tensilica-xtensa-part-2.patch
-xtensa-architecture-support-for-tensilica-xtensa-part-3.patch
-xtensa-architecture-support-for-tensilica-xtensa-part-4.patch
-xtensa-architecture-support-for-tensilica-xtensa-part-5.patch
-xtensa-architecture-support-for-tensilica-xtensa-part-6.patch
-xtensa-architecture-support-for-tensilica-xtensa-part-7.patch
-xtensa-architecture-support-for-tensilica-xtensa-part-8.patch
-make-reiserfs-bug-on-too-big-transaction.patch
-ipmi-doc-updates-for-ipmi.patch
-ipmi-ipmi-timer-shutdown-cleanup.patch
-ipmi-add-ipmi-power-cycle-capability.patch
-ipmi-use-completions-not-semaphores-in-the-ipmi-powerdown-code.patch
-ipmi-add-32-bit-ioctl-translations-for-64-bit-platforms.patch
-char-tpm-use-msleep-clean-up-timers.patch
-fix-concerns-with-tpm-driver-use-enums.patch
-fix-tpm-driver-address-missing-const-defs.patch
-fix-tpm-driver-remove-unnecessary-module-stuff.patch
-fix-tpm-driver-read-return-code-issue.patch
-fix-tpm-driver-large-stack-objects.patch
-fix-tpm-driver-how-timer-is-initialized.patch
-fix-tpm-driver-use-to_pci_dev.patch
-fix-tpm-driver-remove-unnecessary-__force.patch
-fix-tpm-driver-sysfs-owernship-changes.patch
-fix-tpm-driver-sysfs-owernship-changes-fix.patch
-fix-tpm-driver-sysfs-owernship-changes-fix-2.patch
-fix-tpm-driver-sysfs-owernship-changes-fix-3.patch
-fix-tpm-driver-add-cancel-function.patch
-fix-tpm-driver-locks.patch
-tpm-support-for-tpms-on-additional-lpc-bus.patch
-tpm-support-for-tpms-on-additional-lpc-bus-fix-2.patch
-tpm-replace-odd-LPC-init-function.patch
-tpm-add-debugging-output.patch
-tpm-improve-output-in-sysfs-files-when-the-tpm-fails.patch
-i2o-bugfixes-and-compability-enhancements.patch
-i2o-first-code-cleanup-of-spare-warnings-and-unused.patch
-i2o-new-sysfs-attributes-and-adaptec-specific-block.patch
-i2o-new-sysfs-attributes-and-adaptec-specific-block-fix.patch
-i2o-new-sysfs-attributes-and-adaptec-specific-block-fix-fix.patch
-i2o-adaptec-specific-sg_io-access-firmware-access-through.patch
-i2o-second-code-cleanup-of-sparse-warnings-and-unneeded.patch
-i2o-lindent-run-and-replacement-of-printk-through-osm.patch
-i2o-limit-max-sector-workaround-for-promise-controllers.patch
-i2o-build-fix.patch
-i2o-device-attribute-fixes.patch
-drop-obsolete-dibusb-driver.patch
-add-generalized-dvb-usb-driver.patch
-add-generalized-dvb-usb-driver-fix-2.patch
-add-generalized-dvb-usb-driver-fix-3.patch
-add-generalized-dvb-usb-driver-fix-4.patch
-dvb-usb-fix-init-error-checking.patch
-dvb_frontend-use-time_after.patch
-flexcop-add-bcm3510-atsc-frontend-support-for-air2pc-card.patch
-flexcop-add-bcm3510-atsc-frontend-support-for-air2pc-card-fix.patch
-tuner-corec-improvments-and-ymec-tvision-tvf8533mf.patch
-dvb-documentation-fixes.patch
-oprofile-report-anonymous-region-samples.patch
-nfsd4-find_delegation_file.patch
-nfsd4-nfs4_check_delegmode.patch
-nfsd4-dont-reopen-for-delegated-client.patch
-nfsd4-add-open-state-code-for-claim_delegate_cur.patch
-nfsd4-support-claim_delegate_cur.patch
-nfsd4-fix-fh_expire_type.patch
-nfsd4-block-metadata-ops-during-grace-period.patch
-nfsd4-slabify-nfs4_files.patch
-nfsd4-slabify-stateids.patch
-nfsd4-slabify-delegations.patch
-nfsd4-remove-debugging-counters.patch
-nfsd4-rename-nfs4_file-fields.patch
-nfsd4-reference-count-struct-nfs4_file.patch
-lockd-flush-signals-on-shutdown.patch
-nfs4-hold-filp-while-reading-or-writing.patch
-nfsd4-fix-probe_callback.patch
-nfsd4-nfs4_check_open_reclaim-cleanup.patch
-nfsd4-create-separate-laundromat-workqueue.patch
-nfsd4-simplify-lease-changing.patch
-nfsd4-delegation-recovery.patch
-nfsd4-rename-nfs4_state_init.patch
-nfsd4-clean-up-state-initialization.patch
-nfsd4-remove-nfs4_reclaim_init.patch
-nfsd4-idmap-initialization.patch
-nfsd4-setclientid-simplification.patch
-nfsd4-reboot-hash.patch
-nfsd4-add-find_unconf_by_str-functions-to-simplify-setclientid.patch
-nfsd4-grace-period-end.patch
-nfsd4-make-needlessly-global-code-static.patch
-nfsd4-fix-uncomfirmed-list.patch
-nfsd4-fix-setclientid_confirm-cases.patch
-nfsd4-fix-setclientid_confirm-error-return.patch
-nfsd4-setclientid_confirm-gotoectomy.patch
-nfsd4-setclientid_confirm-comments.patch
-nfsd4-miscellaneous-setclientid_confirm-cleanup.patch
-nfsd4-rename-state-list-fields.patch
-nfsd4-allow-multiple-lockowners.patch
-nfsd4-remove-cb_parsed.patch
-nfsd4-initialize-recovery-directory.patch
-nfsd4-reboot-recovery.patch
-nfsd4-reboot-dirname.patch
-nfsacl-solaris-nfsacl-workaround.patch
-nfs-client-latencies.patch
-rock-lindent.patch
-rock-manual-tidies.patch
-rock-remove-CHECK_SP.patch
-rock-remove-CONTINUE_DECLS.patch
-rock-remove-CHECK_CE.patch
-rock-remove-SETUP_ROCK_RIDGE.patch
-rock-remove-MAYBE_CONTINUE.patch
-rock-remove-MAYBE_CONTINUE-fix.patch
-rock-comment-tidies.patch
-rock-lindent-rock-h.patch
-isofs-remove-debug-stuff.patch
-rock-handle-corrupted-directories.patch
-rock-rename-union-members.patch
-rock-handle-directory-overflows.patch
-rock-handle-directory-overflows-fix.patch
-isofs-show-hidden-files-add-granularity-for-assoc-hidden-files-flags.patch
-isofs-show-hidden-files-add-granularity-for-assoc-hidden-files-flags-tidy.patch
-isofs-show-hidden-files-add-granularity-for-assoc-hidden-files-flags-fix.patch
-sched2-cleanup-wake_idle.patch
-sched2-improve-load-balancing-pinned-tasks.patch
-sched2-reduce-active-load-balancing.patch
-sched2-fix-smt-scheduling-problems.patch
-sched2-fix-smt-scheduling-problems-fix.patch
-sched2-add-debugging.patch
-sched2-less-aggressive-idle-balancing.patch
-sched2-balance-timers.patch
-sched2-tweak-affine-wakeups.patch
-sched2-no-aggressive-idle-balancing.patch
-sched2-balance-on-fork.patch
-sched2-schedstats-update-for-balance-on-fork.patch
-sched2-sched-tuning.patch
-sched2-sched-tuning-fix.patch
-sched2-sched-domain-sysctl.patch
-sched-uninline-task_timeslice.patch
-sched-cleanup-context-switch-locking.patch
-sched-null-domains.patch
-sched-remove-degenerate-domains.patch
-sched-remove-degenerate-domains-fix.patch
-sched-multilevel-sbe-sbf.patch
-sched-rcu-domains.patch
-sched-rcu-domains-fix.patch
-sched-consolidate-sbe-sbf.patch
-sched-consolidate-sbe-sbf-fix-2.patch
-sched-consolidate-sbe-sbf-fix-3.patch
-sched-relax-pinned-balancing.patch
-sched-micro-optimize-task-requeueing-in-schedule.patch
-sched-changing-rt-priority-without-cap_sys_nice.patch
-dynamic-sched-domains-sched-changes.patch
-dynamic-sched-domains-sched-changes-fix.patch
-dynamic-sched-domains-cpuset-changes.patch
-dynamic-sched-domains-ia64-changes.patch
-v4l-saa7134-byteorder-fix.patch
-v4l-saa7134-mark-little-endian-ptr.patch
-video_cx88_dvb-must-select-dvb_cx22702.patch
-fix-for-cx88-cardsc-for-dvico-fusionhdtv-3-gold-q.patch
-bttv-support-for-adlink-rtv24-capture-card.patch
-bttv-support-for-adlink-rtv24-capture-card-tidy.patch
-bttv-support-for-adlink-rtv24-capture-card-more-tidy.patch
-v4l-saa7134-ntsc-vbi-fix.patch
-v4l-pal-m-chroma-subcarrier-frequency-fix.patch
-video-for-linux-docummentation.patch
-v4l-add-support-for-pixelview-ultra-pro.patch
-dvico-fusionhdtv3-gold-t-documentation-fix.patch
-v4l-support-tuner-thomson-ddt-7611-atsc-ntsc.patch
-bttv-update.patch
-v4l-cx88-cards-update.patch
-v4l-update-for-tuner-cards-and-some-chips.patch
-v4l-update-for-tuner-cards-and-some-chips-fix.patch
-v4l-update-for-saa7134-cards.patch
-v4l-update-for-saa7134-cards-fix.patch
-v4l-update-for-saa7134-cards-fix-2.patch
-gregkh-i2c-i2c-address_range_removal-v4l-fix.patch
-gregkh-i2c-i2c-address_range_removal-v4l-fix-fix.patch
-nfs-patch-for-fscache.patch
-nfs-patch-for-fscache-fixes.patch
-nfs-patch-for-fscache-warning-fix.patch
-x86-rename-apic_mode_exint.patch
-x86-local-apic-fix.patch
-x86_64-e820-64bit.patch
-x86-i8259-shutdown.patch
-x86_64-i8259-shutdown.patch
-x86-apic-virtwire-on-shutdown.patch
-x86_64-apic-virtwire-on-shutdown.patch
-vmlinux-fix-physical-addrs.patch
-x86-vmlinux-fix-physical-addrs.patch
-x86_64-vmlinux-fix-physical-addrs.patch
-kexec-x86_64-optimise-storage-of-read-mostly-variables-x86_64-fix.patch
-x86-config-kernel-start.patch
-kexec-reserve-bootmem-fix-for-booting-nondefault-location-kernel.patch
-x86_64-config-kernel-start.patch
-kexec-kexec-generic.patch
-kexec-kexec-generic-maintainers-fix.patch
-kexec-disable-preempt-in-panic.patch
-kexec-kexec-generic-fix.patch
-kexec-kexec-generic-kexec-use-unsigned-bitfield.patch
-x86-machine_shutdown.patch
-x86-kexec.patch
-x86-crashkernel.patch
-x86-crashkernel-fix.patch
-x86_64-machine_shutdown.patch
-x86_64-kexec.patch
-x86_64-kexec-build-fix.patch
-x86_64-crashkernel.patch
-kexec-ppc-support.patch
-kexec-ppc-fix-noret_type.patch
-ppc64-kexec-native-hash-clear.patch
-ppc64-kexec-support-for-ppc64.patch
-x86-crash_shutdown-nmi-shootdown.patch
-x86-crash_shutdown-snapshot-registers.patch
-x86-crash_shutdown-apic-shutdown.patch
-kexec-s390-support.patch
-s390-kexec-fixes.patch
-kdump-export-crash-notes-section-address-through.patch
-kdump-export-crash-notes-section-address-through-x86_64-fix.patch
-kdump-nmi-handler-segment-selector-stack.patch
-kexec-kexec-on-panic-fix-with-nmi-watchdog-enabled.patch
-kdump-documentation-for-kdump.patch
-kdump-documentation-for-kdump-update.patch
-kdump-documentation-for-kdump-update-fix.patch
-kdump-documentation-update-to-add-gdb-macros.patch
-kdump-retrieve-saved-max-pfn.patch
-kdump-kconfig-for-kdump.patch
-kdump-routines-for-copying-dump-pages.patch
-kdump-retrieve-elfcorehdr-address-from-command.patch
-kdump-access-dump-file-in-elf-format.patch
-kdump-parse-elf32-headers-and-export-through.patch
-kdump-accessing-dump-file-in-linear-raw-format.patch
-kdump-cleanups-for-dump-file-access-in-linear.patch
-kdump-sysrq-trigger-mechanism-for-kexec-based-crashdumps.patch
-kdump-use-real-pt_regs-from-exception.patch
-kdump-use-real-pt_regs-from-exception-fix.patch
-kdump-use-real-pt_regs-from-exception-fix-fix.patch
-kdump-save-trap-information-for-later-analysis.patch
-kexec-code-cleanup.patch
-serial-eliminate-magic-numbers.patch
-bring-back-tux-on-chips-65550-framebuffer.patch
-s1d13xxxfb-linkage-fix.patch
-some-vesafb-fixes.patch
-intelfbdrv-naming-fix.patch
-fbdev-iomove-removal.patch
-pm3fb-typo-fix.patch
-vga-to-fbcon-fix.patch
-intelfb-add-voffset-option-to-avoid-conficts-with-xorg-i810-driver.patch
-intelfb-add-voffset-option-to-avoid-conficts-with-xorg-i810-driver-fix.patch
-intelfb-fix-accel-detection-when-changing-video-modes.patch
-intelfb-documentation.patch
-intelfb-documentation-fix.patch
-framebuffer-driver-for-arc-lcd-board.patch
-framebuffer-driver-for-arc-lcd-board-tidy.patch
-framebuffer-driver-for-arc-lcd-board-update.patch
-new-pci-id-for-chipsfb.patch
-new-framebuffer-fonts-updated-12x22-font-available.patch
-fbdev-stack-reduction.patch
-fbdev-fill-in-the-access_align-field.patch
-md-cause-md-raid1-to-repack-working-devices-when-number-of-drives-is-changed.patch
-md-make-sure-recovery-happens-when-add_new_disk-is-used-for-hot_add.patch
-md-merge-md_enter_safemode-into-md_check_recovery.patch
-md-improve-locking-on-safemode-and-move-superblock-writes.patch
-md-improve-the-interface-to-sync_request.patch
-md-optimised-resync-using-bitmap-based-intent-logging.patch
-md-optimised-resync-using-bitmap-based-intent-logging-mempool-fix.patch
-md-a-couple-of-tidyups-relating-to-the-bitmap-file.patch
-md-call-bitmap_daemon_work-regularly.patch
-md-print-correct-pid-for-newly-created-bitmap-writeback-daemon.patch
-md-minor-code-rearrangement-in-bitmap_init_from_disk.patch
-md-make-sure-md-bitmap-is-cleared-on-a-clean-start.patch
-md-printk-fix.patch
-md-improve-debug-printing-of-bitmap-superblock.patch
-md-check-return-value-of-write_page-rather-than-ignore-it.patch
-md-enable-the-bitmap-write-back-daemon-and-wait-for-it.patch
-md-dont-skip-bitmap-pages-due-to-lack-of-bit-that-we-just-cleared.patch
-md-optimised-resync-using-bitmap-based-intent-logging-fix.patch
-md-raid1-support-for-bitmap-intent-logging.patch
-md-fix-bug-when-raid1-attempts-a-partial-reconstruct.patch
-md-raid1-support-for-bitmap-intent-logging-fix.patch
-md-optimise-reconstruction-when-re-adding-a-recently-failed-drive.patch
-md-fix-deadlock-due-to-md-thread-processing-delayed-requests.patch
-md-allow-md-intent-bitmap-to-be-stored-near-the-superblock.patch
-md-allow-md-to-update-multiple-superblocks-in-parallel.patch
-md-allow-md-to-update-multiple-superblocks-in-parallel-fix.patch
-md-two-small-fixes-for-md-verion-1-superblocks.patch
-md-dont-skip-bitmap-pages-due-to-lack-of-bit-that-we-just-cleared-fix.patch
-md-remove-unneeded-null-checks-before-kfree.patch
-modules-add-version-and-srcversion-to-sysfs.patch
-modules-add-version-and-srcversion-to-sysfs-fix.patch
-modules-add-version-and-srcversion-to-sysfs-fix-2.patch
-modules-add-version-and-srcversion-to-sysfs-fix-3.patch
-detect-atomic-counter-underflows.patch
-docbook-build-fix.patch
-docbook-only-use-tabular-style-for-long-synopsis.patch
-docbook-update-comments.patch
-xip-bdev-execute-in-place-3rd-version.patch
-xip-fs-mm-execute-in-place-3rd-version.patch
-xip-fs-mm-execute-in-place-3rd-version-fix.patch
-xip-ext2-execute-in-place-3rd-version.patch
-xip-ext2-execute-in-place-3rd-version-fixes.patch
-xip-reduce-code-duplication.patch
-xip-madvice-fadvice-execute-in-place-3rd-version.patch
-xip-description.patch
-drivers-media-video-tvaudioc-make-some-variables-static.patch
-kernel-irq-spuriousc-make-a-function-static.patch
-kernel-power-swsuspc-make-a-variable-static.patch
-kernel-modulec-make-a-function-static.patch
-fs-reiserfs-streec-make-max_key-static.patch
-make-umount_tree-static.patch
-scsi-make-code-static.patch
-drivers-media-common-saa7146_fopsc-make-a-function-static.patch
-net-sctp-make-two-functions-static.patch
-drivers-isdn-sc-possible-cleanups.patch
-drivers-isdn-pcbit-possible-cleanups.patch
-drivers-isdn-i4l-possible-cleanups.patch
-unexport-mca_find_device_by_slot.patch
-drivers-isdn-hardware-avm-misc-cleanups.patch
-drivers-isdn-act2000-capic-if-0-an-unused-function.patch
-x86-64-add-memcpy-memset-prototypes.patch
-au1100fb-convert-to-c99-inits.patch
-riottyc-cleanups-and-warning-fix.patch
-char-ds1620-use-msleep-instead-of-schedule_timeout.patch
-char-tty_io-replace-schedule_timeout-with-msleep_interruptible.patch
-kernel-timer-fix-msleep_interruptible-comment.patch
-init-do_mounts_initrdc-fix-sparse-warning.patch
-arch-i386-kernel-trapsc-fix-sparse-warnings.patch
-arch-i386-kernel-apmc-fix-sparse-warnings.patch
-arch-i386-mm-faultc-fix-sparse-warnings.patch
-arch-i386-crypto-aesc-fix-sparse-warnings.patch
-small-partitions-msdos-cleanups.patch
-remove-redundant-null-check-before-before-kfree-in.patch
-get-rid-of-redundant-null-checks-before-kfree-in-arch-i386.patch
-remove-redundant-null-checks-before-kfree-in-sound-and.patch
-drivers-scsi-initioc-cleanups.patch
-dont-do-pointless-null-checks-and-casts-before-kfree.patch
-drivers-char-isicomc-section-fixes.patch
-sound-oss-cleanups.patch
-sound-oss-cleanups-fix.patch
-sound-oss-rme96xxc-remove-kernel-22-ifs.patch
-drivers-char-mwave-tp3780ic-remove-kernel-22-ifs.patch
-serial-icom-remove-custom-msescs_to_jiffies-macro.patch
-printk-drivers-char-applicomc.patch
-printk-drivers-char-ftape-compressor-zftape-compressc.patch
-lib-sha1c-fix-sparse-warning.patch
-x86_64-coding-style-and-whitespace-fixups.patch
-use-align-to-remove-duplicate-code.patch
-cosmetic-fixes-for-example-programs-in-documentation-cdrom-sbpcd.patch
-drivers-scsi-dpt-remove-versionh-dependencies.patch
-sound-oss-sscapec-remove-dead-code.patch
-drivers-char-istallionc-remove-an-unneeded-variable.patch
-drivers-char-mwave-3780ic-cleanups.patch
-drivers-char-nvramc-possible-cleanups.patch
-drivers-char-rocketc-cleanups.patch
-fs-jffs-cleanups.patch
-fs-ncpfs-remove-unused-ifdef-use_old_slow_directory_listing-code.patch
-drivers-block-sx8c-remove-unused-code.patch
-drivers-video-matrox-matroxfb_miscc-remove-dead-code.patch
-drivers-char-mwave-tp3780ic-remove-dead-code.patch
-drivers-block-ll_rw_blkc-cleanups.patch
-change-the-sound_prime-handling.patch
-i386-cleanup-boot_cpu_logical_apicid-variables.patch
-update-computone-maintainers-entry.patch
-remove-pointless-null-check-before-kfree-in-sony535c.patch
-kfree-cleanups-in-ixjc.patch
-kfree-cleanups-for-drivers-firmware.patch
-drivers-char-ip2-cleanups.patch
-drivers-cdrom-cm206c-cleanups.patch
-drivers-isdn-hisax-possible-cleanups.patch
-ll_merge_requests_fn-cleanup.patch
-update-comment-about-gzip-scratch-size.patch
-kill-signed-chars.patch
-printk-arch-i386-mm-pgtablec.patch
-printk-arch-i386-mm-ioremapc.patch
-sound-oss-esssolo1-use-the-dma_32bit_mask-constant.patch
-sound-oss-es1371-use-the-dma_32bit_mask-constant.patch
-sound-oss-es1370-use-the-dma_32bit_mask-constant.patch
-sound-oss-cmpci-use-the-dma_32bit_mask-constant.patch
-remove-duplicate-file-in-documentation-networking-drivers_net_wan_kconfig.patch
-remove-duplicate-file-in-documentation-networking-00-index.patch
-remove-duplicate-file-in-documentation-networking.patch
-remove-redundant-info-from-submittingpatches.patch

Merged

-aic79xx-deadlock-fix.patch
-aic79xx-deadlock-fix-2.patch
-aic79xx-deadlock-fix-3.patch

Dropped - it was fixed differently.

+jffs2-build-fix.patch
+arm-swsusp-build-fix.patch

Fix damage from recent swsusp cleanups

-ia64-disable-preempt.patch

Dropped: unneeded

+alsa-maestro3-div-by-zero-fix.patch

Revert an alsa change which appears to cause a divide-by-zero.

-gregkh-driver-driver-name-const-01.patch
-gregkh-driver-driver-name-const-02.patch
-gregkh-driver-driver-name-const-03.patch
-gregkh-driver-driver-name-const-04.patch
-gregkh-driver-driver-name-const-05.patch
-gregkh-driver-driver-name-const-06.patch
-gregkh-driver-sysfs-show_store_eio-01.patch
-gregkh-driver-sysfs-show_store_eio-02.patch
-gregkh-driver-sysfs-show_store_eio-03.patch
-gregkh-driver-sysfs-show_store_eio-04.patch
-gregkh-driver-sysfs-show_store_eio-05.patch
-gregkh-driver-class-01-core.patch
-gregkh-driver-class-02-tty.patch
-gregkh-driver-class-03-input.patch
-gregkh-driver-class-04-usb.patch
-gregkh-driver-class-05-sound.patch
-gregkh-driver-class-06-block.patch
-gregkh-driver-class-07-char.patch
-gregkh-driver-class-08-ieee1394.patch
-gregkh-driver-class-09-scsi.patch
-gregkh-driver-class-10-arch.patch
-gregkh-driver-class-11-drivers.patch
-gregkh-driver-class-11-drivers-usb-fix.patch
-gregkh-driver-class-12-the_rest.patch
-gregkh-driver-class-13-kerneldoc.patch
-gregkh-driver-class-14-no_more_class_simple.patch
-gregkh-driver-fix-make-mandocs-after-class_simple-removal.patch
-gregkh-driver-ipmi-class_simple-fixes.patch
-gregkh-driver-klist-01.patch
-gregkh-driver-klist-02.patch
-gregkh-driver-klist-03.patch
-gregkh-driver-klist-04.patch
-gregkh-driver-klist-05.patch
-gregkh-driver-klist-06.patch
-gregkh-driver-klist-07.patch
-gregkh-driver-klist-08.patch
-gregkh-driver-klist-09.patch
-gregkh-driver-klist-10.patch
-gregkh-driver-klist-11.patch
-gregkh-driver-klist-12.patch
-gregkh-driver-klist-13.patch
-gregkh-driver-klist-14.patch
-gregkh-driver-klist-15.patch
-gregkh-driver-klist-16.patch
-gregkh-driver-klist-17.patch
-gregkh-driver-klist-18.patch
-gregkh-driver-klist-scsi-01.patch
-gregkh-driver-klist-scsi-02.patch
-gregkh-driver-klist-20.patch
-gregkh-driver-klist-21.patch
-gregkh-driver-klist-22.patch
-gregkh-driver-klist-23.patch
-gregkh-driver-klist-ieee1394.patch
-gregkh-driver-klist-pcie.patch
-gregkh-driver-klist-24.patch
-gregkh-driver-klist-25.patch
-gregkh-driver-klist-26.patch
-gregkh-driver-klist-usb_node_attached_fix.patch
-gregkh-driver-klist-sn_fix.patch
-gregkh-driver-klist-driver_detach_fixes.patch
-gregkh-driver-klist-usbcore-dont_call_device_release_driver_recursivly.patch
-gregkh-driver-driver-create-unregister_node.patch
-gregkh-driver-driver-model-documentation-update.patch
-gregkh-driver-libfs-add-simple-attribute-files.patch
-gregkh-driver-driver-fix-error-handling-in-bus_add_device.patch
-gregkh-driver-driver-device_attr-01.patch
-gregkh-driver-driver-device_attr-02.patch
-gregkh-driver-driver-device_attr-03.patch
-gregkh-driver-driver-device_attr-04.patch
-gregkh-driver-driver-device_attr-05.patch
-gregkh-driver-driver-device_attr-06.patch
-gregkh-driver-driver-device_attr-07.patch
-gregkh-driver-driver-device_attr-08.patch
-gregkh-driver-driver-device_attr-09.patch
-gregkh-driver-driver-device_attr-10.patch
-gregkh-driver-driver-device_attr-11.patch
-gregkh-driver-driver-device_attr-12.patch
-gregkh-driver-driver-device_attr-i2c-sysfs.h.patch
-gregkh-driver-driver-device_attr-i2c-adm1026.patch
-gregkh-driver-sysfs-permissions-01.patch
-gregkh-driver-sysfs-permissions-02.patch
-gregkh-driver-sysfs-permissions-03.patch
-gregkh-driver-dont-loose-devices-on-suspend-failure.patch
-gregkh-driver-sysfs-page_size-check.patch
+gregkh-driver-driver-bus_find_device.patch
+gregkh-driver-driver-unbind.patch
+gregkh-driver-driver-bind.patch
+gregkh-driver-driver-bus_rescan_devices-nocount.patch

Greg's driver core tree

-gregkh-i2c-i2c-address_range_removal.patch
-gregkh-i2c-i2c-address_merge_video.patch
-gregkh-i2c-i2c-rtc8564_duplicate_include.patch
-gregkh-i2c-i2c-vid_h.patch
-gregkh-i2c-i2c-atxp1.patch
-gregkh-i2c-i2c-atxp1-cleanup.patch
-gregkh-i2c-i2c-ds1337-01.patch
-gregkh-i2c-i2c-ds1337-02.patch
-gregkh-i2c-i2c-ds1337-03.patch
-gregkh-i2c-i2c-ds1337_make_time_format_consistent.patch
-gregkh-i2c-i2c-ds1337_i2c_transfer_check.patch
-gregkh-i2c-i2c-ds1337_search_by_bus_number.patch
-gregkh-i2c-i2c-ds1337-config-update.patch
-gregkh-i2c-i2c-ds1337-export-ds1337_do_command.patch
-gregkh-i2c-i2c-config_cleanup-01.patch
-gregkh-i2c-i2c-config_cleanup-02.patch
-gregkh-i2c-i2c-adm9240.patch
-gregkh-i2c-i2c-w83627ehf.patch
-gregkh-i2c-i2c-w83627ehf-cleanup.patch
-gregkh-i2c-i2c-smsc47m1.patch
-gregkh-i2c-i2c-spelling_fixes.patch
-gregkh-i2c-i2c-mpc-share_interrupt.patch
-gregkh-i2c-i2c-remove_redundancy_from_i2c_core.patch
-gregkh-i2c-i2c-remove_delay_h_from_via686a.patch
-gregkh-i2c-i2c-w83627hf-fan-divisor-fix.patch
-gregkh-i2c-i2c-rename-cpu0_vid.patch
-gregkh-i2c-i2c-adm9240-cleanup.patch
-gregkh-i2c-i2c-jiffies.h.patch
-gregkh-i2c-i2c-macro-abuse-cleanup.patch
-gregkh-i2c-i2c-via686a-code-cleanup.patch
-gregkh-i2c-i2c-adm1021-remove_die_code.patch
-gregkh-i2c-i2c-Kconfig-corrections.patch
-gregkh-i2c-i2c-macro-abuse-cleanup-via686a.patch
-gregkh-i2c-i2c-driver-device_attr-fixup.patch
-gregkh-i2c-i2c-spelling-fixes-more-01.patch
-gregkh-i2c-i2c-spelling-fixes-more-02.patch
-gregkh-i2c-i2c-spelling-fixes-more-03.patch
-gregkh-i2c-i2c-spelling-fixes-more-04.patch
-gregkh-i2c-i2c-mpc-race-fix.patch
-gregkh-i2c-i2c-mailing-list-move.patch
-gregkh-i2c-i2c-tps6501x.patch
-gregkh-i2c-i2c-docs-update-1.patch
-gregkh-i2c-i2c-docs-update-2.patch
-gregkh-i2c-i2c-docs-update-3.patch
-gregkh-i2c-i2c-Kconfig-update.patch
-gregkh-i2c-i2c-pcf8574-cleanup.patch
-gregkh-i2c-i2c-adm9240-docs.patch
-gregkh-i2c-i2c-device-attr-lm90.patch
-gregkh-i2c-i2c-device-attr-lm83.patch
-gregkh-i2c-i2c-device-attr-lm63.patch
-gregkh-i2c-i2c-device-attr-it87.patch
-gregkh-i2c-i2c-max6875.patch
-gregkh-i2c-i2c-rename-i2c-sysfs.patch
-gregkh-i2c-i2c-pca9539.patch
-gregkh-i2c-i2c-ds1374-01.patch
-gregkh-i2c-i2c-ds1374-02.patch
-gregkh-i2c-i2c-ds1374-03.patch
-gregkh-i2c-i2c-w83781d-remove-non-i2c-chips.patch
-gregkh-i2c-w1-ds18xx_sensors.patch
-gregkh-i2c-w1-new_rom_family.patch
-gregkh-i2c-w1-cleanups.patch
-gregkh-i2c-w1-new-family-structure.patch
-gregkh-i2c-w1-build-fixups.patch
-gregkh-i2c-w1-remove-dup-family-id.patch
-gregkh-i2c-w1-01.patch
-gregkh-i2c-w1-02.patch
-gregkh-i2c-w1-03.patch
-gregkh-i2c-w1-04.patch
-gregkh-i2c-w1-05.patch
-gregkh-i2c-w1-06.patch
-gregkh-i2c-w1-07.patch

Greg's i2c tree

+i2c-new-max6875-driver-may-corrupt-eeproms.patch

i2c eeprom corruption fix

+git-libata-adma-mwi.patch
+git-libata-chs-support.patch
+git-libata-passthru.patch
+git-libata-promise-sata-pata.patch

Bring these libata trees back

+samsung-sn-124-works-perfectly-well-with-dma-on-sata-too.patch

SATA fix

+git-netdev-janitor-fixup.patch

Fix rejects in git-netdev-janitor.patch

+ipw2100-remove-by-hand-function-entry-exit-debugging.patch
+ipw2100-remove-commented-out-code.patch
+pcnet_csc-irq-handler-optimization.patch
+is_multicast_ether_addr-hack.patch
+wireless-device-attr-fixes.patch
+wireless-device-attr-fixes-2.patch
+ipw2100-old-gcc-fix.patch

Various netdev fixups

-git-ocfs.patch
+git-ocfs2.patch

Renamed this patch

+gregkh-pci-pci-fix-drivers-setting-shutdown.patch

Addition to Greg's PCI tree

+gregkh-pci-pci-assign-unassigned-resources-fix.patch

Try to fix it

+revert-gregkh-pci-pci-assign-unassigned-resources.patch

Revert a bad patch in it

+pci-yenta-cardbus-fix.patch

Try to fix the `resource 0 busy, reconfiguring...' bug

+git-scsi-block.patch
+git-scsi-block-fix.patch

New git tree (James Bottomley)

+scsi-ahc_target_state-check-starget-valid.patch

adaptec driver fix

-gregkh-usb-usb-driver-device_attr-fixup.patch
+gregkh-usb-usb-storage-port-reset-on-transport-error.patch

Changes in Greg's USB tree.

-swapspace-layout-improvements.patch

Dropped again. Reasonable idea, no net benefit observable, not anough time
to work on it, gets in the way.

+mm-consolidate-get_order.patch

clean up the get_order() implementations

-proc-pid-smaps-fix.patch
-proc-pid-smaps-tidy.patch
-proc-pid-smaps-fix-fix.patch

Folded into proc-pid-smaps.patch

+ppp-handle-misaligned-accesses.patch
+ipvs-add-and-reorder-bh-locks-after-moving-to-keventd.patch
+ipvs-close-race-conditions-on-ip_vs_conn_tab-list-modification.patch
+ipvs-close-race-conditions-on-ip_vs_conn_tab-list-modification-fix.patch
+zatm-kfree-fix.patch

Various net fixes

-cs89x0c-support-for-philips-pnx0105-network-adapter-tidy.patch

Folded into cs89x0c-support-for-philips-pnx0105-network-adapter.patch

+silence-cs89x0.patch

Kill a printk

+x86-i8253-i8259a-lock-cleanup.patch

x86 code cleanup

+seccomp-tsc-disable.patch

Disable tsc on processes which are running under seccomp

-mempool-bounce-buffer-restriction.patch

Not sure that I'll merge this - the problem is real but this implementation
is perhaps not the best wrt SMP scalability.

+add-suspend-resume-for-timer.patch

Add suspend and resume support for x86 timers

+cris-update-1-17-arch-split.patch
+cris-update-2-17-configuration-and-build.patch
+cris-update-3-17-console.patch
+cris-update-4-17-debug.patch
+cris-update-5-17-drivers.patch
+cris-update-6-17-i-o-and-dma-allocator.patch
+cris-update-7-17-irq.patch
+cris-update-8-17-misc-patches.patch
+cris-update-9-17-mm.patch
+cris-update-10-17-pci.patch
+cris-update-11-17-profiler.patch
+cris-update-12-17-serial-port-driver.patch # rmk said no
+cris-update-13-17-smp.patch
+cris-update-14-17-synchronous-serial-port-driver.patch
+cris-update-15-17-updates-for-2612.patch
+cris-update-16-17-usb.patch
+cris-update-17-17-new-subarchitecture-v32.patch

arch/cris updates

+uml-kill-some-useless-vmalloc-tlb-flushing.patch
+uml-remove-winch-sem.patch # "keep in -mm"

uml updates

-detect-soft-lockups-smp_processor_id-cleanup-fix.patch
-detect-soft-lockups-from-touch_nmi_watchdog.patch
-kernel-softlockup-fix-usage-of-msleep_interruptible.patch
-turn-soft-lock-off-when-panicking.patch

Folded into detect-soft-lockups.patch

-relayfs-properly-handle-oversized-events.patch
-relayfs-backing_dev-fix.patch

Folded into relayfs.patch

+relayfs-cancel-work-on-close-reset.patch
+relayfs-add-private-data-to-channel-struct.patch
+relayfs-function-docfix.patch
+relayfs-add-relayfs-website-to-documentation.patch

relayfs fixes

-fix-of-dcache-race-leading-to-busy-inodes-on-umount-fix.patch
-fix-of-dcache-race-leading-to-busy-inodes-on-umount-tidy.patch

Folded into fix-of-dcache-race-leading-to-busy-inodes-on-umount.patch

+using-msleep-instead-of-hz.patch
+using-msleep-instead-of-hz-fix.patch
+using-msleep-instead-of-hz-fix-2.patch

cleanup

+new-driver-for-yealink-usb-p1k-phone.patch
+new-driver-for-yealink-usb-p1k-phone-tidy.patch
+new-driver-for-yealink-usb-p1k-phone-fixes.patch
+new-driver-for-yealink-usb-p1k-phone-warning-sysfs-fixes.patch
+yealink-maintainer.patch

USB phone driver

+usb-makefile-update-for-sisusbvga.patch

USB fix

+drivers-char-tiparc-off-by-one-array-access.patch

tipar.c fix

+ixp4xx-ixp2000-watchdog-driver-typo.patch

Fix typos in two watchdog drivers

+de_thread-eliminate-unneccessary-sighand-locking.patch

Locking simplification

+pselect-ppoll-system-calls.patch
+pselect-ppoll-system-calls-tidy.patch
+pselect-ppoll-system-calls-fix.patch
+pselect-ppoll-system-calls-sigset_t-fix-2.patch

pselect() and ppoll() (the case seems thin)

+itimer_real-fix-possible-deadlock-and-race.patch

itimer deadlock fix

+pcie-acpi-tg3-ethernet-not-coming-back-properly-after-s3-suspendon-dellm70.patch

pcie power management fix

+adapt-drivers-char-vt_ioctlc-to-non-x86.patch

Don't use a hardwired number for clock speed

+request_firmware-avoid-race-conditions.patch

request_firmware() fixes

+yenta-make-topic95-bridges-work-with-16bit-cards.patch

cardbus fix

+smsc-ircc2-whitespace-fixes.patch
+smsc-ircc2-formatting-fixes.patch
+smsc-ircc2-drop-dim-macro-in-favor-of-array_size.patch
+smsc-ircc2-remove-typedefs.patch
+smsc-ircc2-dont-pass-iobase-around.patch
+smsc-ircc2-add-to-sysfs-as-platform-device-new-pm.patch
+smsc-ircc2-pm-cleanup-do-not-close-device-when-suspending.patch
+smsc-ircc2-pm-cleanup-do-not-close-device-when-suspending-fixes.patch
+smsc-ircc2-use-netdev_priv.patch
+smsc-ircc2-dont-use-void-where-specific-type-will-do.patch

irda driver updates

+ib-mthca-add-sun-copyright-notice.patch
+ib-mthca-clean-up-error-messages.patch
+ib-mthca-clean-up-cq-debug.patch
+ib-mthca-use-dma_alloc_coherent-instead-of-pci_alloc_consistent.patch
+ib-mthca-set-qp-static-rate-correctly.patch
+ib-mthca-set-rdma-atomic-capabilities-correctly.patch
+ib-mthca-enable-unreliable-connected-transport.patch
+ib-mthca-fix-memset-size.patch
+ib-mthca-move-mthca_is_memfree-checks.patch
+ib-mthca-split-off-mtt-allocation.patch
+ib-mthca-fix-memory-leak-on-error-path.patch
+ib-mthca-encapsulate-command-interface-init.patch
+ib-mthca-align-fw-command-mailboxes-to-4k.patch
+ib-mthca-bump-version.patch
+ib-fix-race-in-sa_query.patch
+ib-fix-pack-unpack-when-size_bits-==-64.patch
+maintainers-update-roland-dreiers-email.patch

Infiniband updates

+cciss-26-pci-id-fix.patch
+cciss-26-pci-domain-info-pass-2.patch
+cciss-26-remove-partition-info-from-cciss_getluninfo.patch
+cciss-26-remove-partition-info-from-cciss_getluninfo-fix.patch

cciss fixes

+headers-enable-ppc64-___arch__swab16-and-___arch__swab32.patch
+headers-include-linux-compilerh-for-__user.patch
+headers-include-linux-typesh-for-usb_ch9h.patch

Header file cleanups

+coverity-i386-build-negative-return-to-unsigned-fix.patch
+coverity-i386-scsi_lib-buffer-overrun-fix.patch
+coverity-fs-udf-namei-null-check.patch
+coverity-fs-ext3-super-match_int-return-check.patch
+coverity-desc-bitmap-overrun-fix.patch
+coverity-tty_ldisc_ref-return-null-check.patch

Various fixes found by the Coverity checker.

+kprobes-fix-single-step-out-of-line-take2.patch
+return-probe-redesign-architecture-independant-changes.patch
+return-probe-redesign-i386-specific-changes.patch
+return-probe-redesign-x86_64-specific-changes.patch
+return-probe-redesign-ia64-specific-implementation.patch
+return-probe-redesign-ppc64-specific-implementation.patch
+kprobes-ia64-refuse-inserting-kprobe-on-slot-1.patch
+kprobes-ia64-refuse-kprobe-on-ivt-code.patch

kprobes updates

-rapidio-support-core-base-rapidio-support-core-base.patch

Folded into rapidio-support-core-base.patch

-rapidio-support-ppc32-fix.patch
-rapidio-support-ppc32-add-error-checking-to-mpc85xx.patch

Folded into rapidio-support-ppc32.patch

-dlm-lockspaces-callbacks-directory-dlm-consistent-ifdefs.patch
-dlm-lockspaces-callbacks-directory-build-fix.patch
-dlm-lockspaces-callbacks-directory-fix.patch
-dlm-lockspaces-callbacks-directory-fix-2.patch
-dlm-lockspaces-callbacks-directory-fix-2-dlm-dont-repeat-include.patch
-dlm-lockspaces-callbacks-directory-fix-3.patch
-dlm-lockspaces-callbacks-directory-dlm-dont-free-lvb-twice.patch

Folded into dlm-lockspaces-callbacks-directory.patch

-dlm-communication-dlm-dont-add-duplicate-node-addresses.patch

Folded into dlm-communication.patch

-dlm-recovery-dlm-timer-cant-be-global.patch
-dlm-recovery-dlm-clear-recovery-flags.patch

Folded into dlm-recovery.patch

-dlm-device-interface-fix.patch
-dlm-device-interface-dlm-uncomment-unregister_lockspace.patch
-dlm-device-interface-dlm-newline-in-printks.patch

Folded into dlm-device-interface.patch

-dlm-debug-fs-no-debug-build-fix.patch
-dlm-debug-fs-dlm-consistent-ifdefs.patch

Folded into dlm-debug-fs.patch

-connector-warning-fixes.patch
-connector-export-initialization-flag.patch
-connector-netlink-id-fix.patch
-connector-remove-socket-number-parameter.patch

Folded into connector.patch

-connector-add-a-fork-connector-build-fix.patch
-fork-connector-send-status-to-userspace.patch
-fork-connector-send-status-to-userspace-fix.patch

Folded into connector-add-a-fork-connector.patch

+connector-add-a-fork-connector-use-after-free-fix.patch

Fix connector-add-a-fork-connector.patch

+inotify-faq-fds.patch

Update the inotify FAQ

-ext3-reduce-allocate-with-reservation-lock-latencies-tidy.patch

Folded into ext3-reduce-allocate-with-reservation-lock-latencies.patch

-pcmcia-allow-function-id-based-match-fix.patch

Folded into pcmcia-allow-function-id-based-match.patch

+pcmcia-id_table-for-ide_csc-update.patch
+pcmcia-more-ids-for-tdk-multifunction-cards.patch

More pcmcia ID tables

-pcmcia-mark-parent-bridge-windows-as-resources-available-for-pcmcia-devices-fix.patch

Folded into pcmcia-mark-parent-bridge-windows-as-resources-available-for-pcmcia-devices.patch

-pcmcia-move-pcmcia-ioctl-to-a-separate-file-fix.patch

Folded into pcmcia-move-pcmcia-ioctl-to-a-separate-file.patch

-pcmcia-clean-up-cs-ds-callback-fix.patch

Folded into pcmcia-clean-up-cs-ds-callback.patch

+pcmcia-8-and-16-bit-access-for-static_map.patch
+pcmcia-export-modalias-in-sysfs.patch

pcmcia fixes

+nfs-fix-client-oops-when-debugging-is-on.patch
+ingo-nfs-stuff.patch
+xdr-input-validation.patch

nfs fixes

+spinlock-consolidation.patch
+spinlock-consolidation-parisc-build-fixes.patch
+spinlock-consolidation-sparc64-fix.patch

Clean up the spinlock code

-kgdb-move-config-option-for-bad_syscall_exit.patch
-kgdb-fix-bad_syscall_exit-lockup.patch
-kgdb-x86-config_debug_info-fix.patch

Folded into kgdb-ga.patch

-kgdb-x86_64-support-fix.patch
-kgdb-x86_64-config_debug_info-fix.patch

Folded into kgdb-x86_64-support.patch

-numa-aware-slab-allocator-v3-__bad_size-fix.patch

Folded into numa-aware-slab-allocator-v5.patch

+numa-aware-slab-allocator-unifdeffery.patch

Reduce ifdefs in numa-aware-slab-allocator-v5.patch

+iteraid-fix-trivial-sparse-warnings.patch
+iteraid-misc-trivial-cleanups.patch
+iteraid-remove-home-grown-memmove.patch
+iteraid-memset-fix.patch

Fixes against iteraid.patch

-silence-spinlock-rwlock-uninitialized-break_lock-member.patch

Dropped - lots of rejects and might no longer be needed and I'm not very
interested in `gcc -W' fixes.

-nmi-lockup-and-altsysrq-p-dumping-calltraces-on-_all_-cpus-fix.patch

Folded into nmi-lockup-and-altsysrq-p-dumping-calltraces-on-_all_-cpus.patch

-perfctr-ppc64-wraparound-fixes.patch
-perfctr-x86-update-with-k8-multicore-fixes-take-2.patch
-perfctr-seqlocks-for-mmaped-state-common.patch
-perfctr-seqlocks-for-mmaped-state-x86.patch
-perfctr-seqlocks-for-mmaped-state-ppc64.patch
-perfctr-seqlocks-for-mmaped-state-ppc32.patch

Folded into perfctr.patch

+perfctr-handle-non-of-ppc32-platforms.patch

perfctr update

+sched-tweak-idle-thread-setup-semantics.patch
+sched-run-sched_normal-tasks-with-real-time-tasks-on-smt-siblings.patch
+max_user_rt_prio-and-max_rt_prio-are-wrong.patch
+sched-idlest-cpus_allowed-aware.patch
+sched-cleanups.patch
+sched-task_noninteractive.patch
+scheduler-cache-hot-autodetect.patch # needs work
+scheduler-cache-hot-autodetect-section-fix.patch
+scheduler-cache-hot-autodetect-x86-cpu_khz-type-fix.patch
+scheduler-cache-hot-autodetect-x86-cpu_khz-type-fix-2.patch
+sched-add-cacheflush-asm.patch
+sched-add-cacheflush-asm-2.patch
+sched-add-cacheflush-asm-2-ia64-fix.patch
+scheduler-cache-hot-autodetect-build-fix.patch
+sched-fix-smt-scheduler-latency-bug.patch

scheduler stuff

+v4l-maintainer-patch.patch
+v4l-tuner-improvements.patch
+v4l-bttv-new-insmod-parameters.patch
+v4l-api-new-webcam-formats-included.patch
+v4l-documentation-changes-mostly-new-cards-included.patch

v4l updates

-allow-x86_64-to-reenable-interrupts-on-contention.patch

Dropped - it had rejects and Andi didn't like it anyway.

-numa-policies-for-file-mappings-mpol_mf_move-cachefs.patch
-cachefs-release-search-records-lest-they-return-to-haunt-us.patch
-fix-64-bit-problems-in-cachefs.patch
-cachefs-fixed-typos-that-cause-wrong-pointer-to-be-kunmapped.patch
-cachefs-return-the-right-error-upon-invalid-mount.patch
-fix-cachefs-barrier-handling-and-other-kernel-discrepancies.patch
-remove-error-from-linux-cachefsh.patch
-cachefs-warning-fix-2.patch
-cachefs-linkage-fix-2.patch
-cachefs-build-fix.patch

Folded into cachefs-filesystem.patch

-add-page-becoming-writable-notification-fix.patch
-add-page-becoming-writable-notification-build-fix.patch
-make-page-becoming-writable-notification-a-vma-op-only.patch

Folded into add-page-becoming-writable-notification.patch

-provide-a-filesystem-specific-syncable-page-bit-fix.patch
-provide-a-filesystem-specific-syncable-page-bit-fix-2.patch

Folded into provide-a-filesystem-specific-syncable-page-bit.patch

-afs-cachefs-dependency-fix.patch

Folded into make-afs-use-cachefs.patch

-split-general-cache-manager-from-cachefs-fix.patch

Folded into split-general-cache-manager-from-cachefs.patch

-make-page-becoming-writable-notification-a-vma-op-only-kafs-fix-fix.patch

Folded into make-page-becoming-writable-notification-a-vma-op-only-kafs-fix.patch

+files-break-up-files-struct-fix-dupfd-by-fdt-reload.patch
+files-files-struct-with-rcu-change-fd_install-assertion.patch
+files-files-locking-doc-update.patch

Fixes for the files_lock RCUification patches in -mm.

+asfs-filesystem-driver.patch
+asfs-filesystem-driver-fixes.patch

Amiga smart filesystem driver. Needs cleanups and I don't think we see a
lot of demand for this one.

+reiser4-swsusp-build-fix.patch
+reiser4-printk-warning-fix.patch
+reiser4-fix-dependencies.patch

reiser4 fixes

+v9fs-vfs-file-dentry-and-directory-operations-fix-fsf-postal-address-in-source-headers.patch
+v9fs-vfs-inode-operations-fix-fsf-postal-address-in-source-headers.patch
+v9fs-vfs-superblock-operations-and-glue-fix-fsf-postal-address-in-source-headers.patch
+v9fs-9p-protocol-implementation-fix-fsf-postal-address-in-source-headers.patch
+v9fs-transport-modules-fix-fsf-postal-address-in-source-headers.patch
+v9fs-transport-modules-fix-timeout-segfault-corner-case.patch
+v9fs-debug-and-support-routines-fix-fsf-postal-address-in-source-headers.patch
+v9fs-change-error-magic-numbers-to-defined-constants.patch
+v9fs-clean-up-vfs_inode-and-setattr-functions.patch
+v9fs-fix-support-for-special-files-devices-named-pipes-etc.patch

v9fs updates

+clean-up-the-old-digi-support-and-rescue-it.patch

Clean up the digi driver, make it work on SMP

-minimal-ide-disk-updates.patch
+ide-fix-ide-disk-inability-to-handle-lba-only-devices.patch
+ide-samsung-sn-124-works-perfectly-well-with-dma.patch
+ide-timing-violation-on-reset.patch
+ide-generic-allow-for-capture-of-other-unsupported-devices.patch
+ide-fix-the-hpt366-driver-layer.patch
+ide-fix-crashes-with-hotplug-serverworks.patch
+ide-it8212-backport-for-bartlomiej-ide.patch
+ide-sensible-probing-for-pci-systems.patch

Various IDE fixes from Alan. This includes Alan's driver for the ITE RAID
cards. Presumably you don't want to enable this at the same time as
iteraid.patch.

+doc-submitting-corrections-additions.patch

Documentation fixes

-fuse-device-functions-abi-version-change.patch
-fuse-device-functions-comments-and-documentation.patch
-fuse-device-functions-comments-and-documentation-document-security-measures.patch
-fuse-device-functions-cleanup.patch
-fuse-device-functions-fuse-serious-information-leak-fix.patch

Folded into fuse-device-functions.patch

-fuse-read-only-operations-multiple-links-to-directory-fix.patch
-fuse-read-only-operations-add-offset-to-fuse_dirent.patch
-fuse-read-only-operations-readdir-fixes.patch

Folded into fuse-read-only-operations.patch

-fuse-read-write-operations-fix-lookup-forget-interface.patch

Folded into fuse-read-write-operations.patch

-fuse-file-operations-interrupted-open-fix.patch

Folded into fuse-file-operations.patch

-fuse-mount-options-fix.patch
-fuse-mount-options-reference-counting-fix.patch
-fuse-mount-options-comments-and-documentation.patch
-fuse-mount-options-fix-cleanup.patch
-fuse-mount-options-fix-fix.patch
-fuse-mount-options-remove-allow_root-mount-option.patch

Folded into fuse-mount-options.patch

-fuse-direct-i-o-disable-sendfile-with-direct_io.patch
-fuse-direct-i-o-nfsd-with-direct_io-fix.patch
-fuse-direct-i-o-fix-warning-on-x86_64.patch

Folded into fuse-direct-i-o.patch

-fuse-add-fsync-operation-for-directories-fix.patch

Folded into fuse-add-fsync-operation-for-directories.patch

+timer-initialization-cleanup-define_timer.patch

Add DEFINE_TIMER, use it.

+more-spin_lock_unlocked-define_spinlock-conversions.patch

A few spinlock initialisation cleanups


number of patches in -mm: 619
number of changesets in external trees: 9
number of patches in -mm only: 618
total patches: 627

All 627 patches:

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm2/patch-list


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Russell King

unread,
Jun 26, 2005, 7:45:08 AM6/26/05
to Andrew Morton, linux-...@vger.kernel.org
On Sun, Jun 26, 2005 at 04:03:29AM -0700, Andrew Morton wrote:
> - Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get
> the recent PCI breakage sorted out.

I'm not sure what PCI breakage you're referring to, but a lot of the
Cardbus-centric "breakage" isn't a regression - it's new machines
with weird PCI BIOS setups being incompatible Linux's current PCI
bus handing strategy.

I've been trying to get this fixed for a considerable time, but linux-pci
folk seem to be disinterested.

The assumption that the PCI BIOS will sanely assign the PCI bus numbers
and that Linux does not need to reassign them is looking increasingly
incorrect - most of the Cardbus "why can't the system see my card"
are resolved by passing "pci=assign-busses", which causes the PCI
subsystem to renumber all PCI busses.

So far, no one who has tried this solution has reported any additional
problems that I'm aware of.

Therefore, maybe that should become the default behaviour?

--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core

Adam Kropelin

unread,
Jun 26, 2005, 10:02:24 AM6/26/05
to Andrew Morton, linux-...@vger.kernel.org, Vojtech Pavlik, Greg KH, Dmitry Torokhov, '...@mail.kroptech.com
I'd like to lobby for the merging into mainline of this patch from
git-input. It fixes a real bug, seen by real users, and has been
languishing in the input tree since March. It may also be a candidate
for the stable tree given it's one-linedness.

--

Fix extraction of HID items >= 32 bits

HID items of width 32 (bits) or greater are incorrectly extracted due to
a masking bug in hid-core.c:extract(). This patch fixes it up by forcing
the mask to be 64 bits wide.


Signed-off-by: Adam Kropelin <akro...@rochester.rr.com>


--- linux-2.6.11/drivers/usb/input/hid-core.c Thu Mar 3 20:40:49 2005
+++ linux-2.6.11.adk/drivers/usb/input/hid-core.c Sun Mar 13 14:00:47 2005
@@ -757,7 +757,7 @@
static __inline__ __u32 extract(__u8 *report, unsigned offset, unsigned n)
{
report += (offset >> 5) << 2; offset &= 31;
- return (le64_to_cpu(get_unaligned((__le64*)report)) >> offset) & ((1 << n) - 1);
+ return (le64_to_cpu(get_unaligned((__le64*)report)) >> offset) & ((1ULL << n) - 1);
}

static __inline__ void implement(__u8 *report, unsigned offset, unsigned n, __u32 value)

Michał Piotrowski

unread,
Jun 26, 2005, 10:04:28 AM6/26/05
to Andrew Morton, linux-...@vger.kernel.org
Hi Andrew,

Can you merge OOPS Reporting Tool
(http://stud.wsi.edu.pl/~piotrowskim/files/ort/beta/ort-b3.tar.bz2)
with next -mm release?

Regards,
Michał Piotrowski

Dominik Brodowski

unread,
Jun 26, 2005, 10:08:35 AM6/26/05
to Andrew Morton, gr...@kroah.com, rajes...@intel.com, linux-...@vger.kernel.org
On Sun, Jun 26, 2005 at 04:03:29AM -0700, Andrew Morton wrote:
> - Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get
> the recent PCI breakage sorted out.

pci-yenta-cardbus-fix.patch and the following patch should solve the
initialization time trouble. However, the ACPI-based PCI resource handling
is badly broken, IMHO:

- many resources of devices don't show up in the resource trees (
/proc/iomem and /proc/ioports) any longer. This means that PCMCIA, but
also possibly other subsystems (ISA, PnP, ...) do not know which resources
it cannot use.

- verify_root_windows() should fail if there are no iomem _or_ ioport
resources, not only if there are no iomem _and_ ioport resources.

Nonetheless, with the init-time trouble (hopefully) solved, I'd say that it
is time for the PCMCIA patches to get into mainline.

Dominik


Don't auto-configure yenta sockets for PCMCIA devices if it is connected to
the root PCI bus on the x86 or x86_64 architectures. Previously, this was
handled by the "ioport_resource"/"iomem_resource" check a few lines below,
but with the new ACPI-based resource handling this doesn't catch all cases
any longer.

Signed-off-by: Dominik Brodowski <li...@dominikbrodowski.net>

--- 2.6.12-mm2/drivers/pcmcia/rsrc_nonstatic.c.orig 2005-06-26 15:04:57.000000000 +0200
+++ 2.6.12-mm2/drivers/pcmcia/rsrc_nonstatic.c 2005-06-26 15:09:02.000000000 +0200
@@ -779,6 +779,17 @@
if (!s->cb_dev || !s->cb_dev->bus)
return -ENODEV;

+#if defined(CONFIG_X86) || defined(CONFIG_X86_64)
+ /* If this is the root bus, the risk of hitting
+ * some strange system devices which aren't protected
+ * by either ACPI resource tables or properly requested
+ * resources is too big. Therefore, don't do auto-adding
+ * of resources at the moment.
+ */
+ if (s->cb_dev->bus->number == 0)
+ return -EINVAL;
+#endif
+
for (i=0; i < PCI_BUS_NUM_RESOURCES; i++) {
res = s->cb_dev->bus->resource[i];
if (!res)

Adrian Bunk

unread,
Jun 26, 2005, 12:13:01 PM6/26/05
to Andrew Morton, Luca Falavigna, linux-...@vger.kernel.org, Ingo Molnar, Jeff Garzik
On Sun, Jun 26, 2005 at 04:03:29AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.12-mm1:
>...
> +using-msleep-instead-of-hz.patch
>...
> cleanup
>...

This patch causes the following warning:

<-- snip -->

..
CC kernel/irq/autoprobe.o
kernel/irq/autoprobe.c: In function `probe_irq_on':
kernel/irq/autoprobe.c:30: warning: unused variable `delay'
..

<-- snip -->


This patch removes this no longer used variable.

Signed-off-by: Adrian Bunk <bu...@stusta.de>

--- linux-2.6.12-mm2-full/kernel/irq/autoprobe.c.old 2005-06-26 14:46:35.000000000 +0200
+++ linux-2.6.12-mm2-full/kernel/irq/autoprobe.c 2005-06-26 14:46:46.000000000 +0200
@@ -27,7 +27,7 @@
*/
unsigned long probe_irq_on(void)
{
- unsigned long val, delay;
+ unsigned long val;
irq_desc_t *desc;
unsigned int i;

Andrew Morton

unread,
Jun 26, 2005, 3:18:53 PM6/26/05
to Dominik Brodowski, gr...@kroah.com, rajes...@intel.com, linux-...@vger.kernel.org
Dominik Brodowski <li...@dominikbrodowski.net> wrote:
>
> On Sun, Jun 26, 2005 at 04:03:29AM -0700, Andrew Morton wrote:
> > - Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get
> > the recent PCI breakage sorted out.
>
> pci-yenta-cardbus-fix.patch and the following patch should solve the
> initialization time trouble. However, the ACPI-based PCI resource handling
> is badly broken, IMHO:
>
> - many resources of devices don't show up in the resource trees (
> /proc/iomem and /proc/ioports) any longer. This means that PCMCIA, but
> also possibly other subsystems (ISA, PnP, ...) do not know which resources
> it cannot use.

Is this a recent regression? Is it only in -mm?

IOW: can you identify the bad patch? Or the bad patcher ;)

> - verify_root_windows() should fail if there are no iomem _or_ ioport
> resources, not only if there are no iomem _and_ ioport resources.

This too.

Andrew Morton

unread,
Jun 26, 2005, 3:27:12 PM6/26/05
to Adam Kropelin, linux-...@vger.kernel.org, voj...@suse.cz, gr...@kroah.com, dt...@mail.ru
Adam Kropelin <akro...@rochester.rr.com> wrote:
>
> I'd like to lobby for the merging into mainline of this patch from
> git-input. It fixes a real bug, seen by real users, and has been
> languishing in the input tree since March. It may also be a candidate
> for the stable tree given it's one-linedness.
>

I think we can merge all of git-input into Linus's tree immediately.

But if that'll take some time then sure, we can merge up this little bit.

Russell King

unread,
Jun 26, 2005, 3:38:14 PM6/26/05
to Andrew Morton, Dominik Brodowski, gr...@kroah.com, rajes...@intel.com, linux-...@vger.kernel.org
On Sun, Jun 26, 2005 at 12:17:10PM -0700, Andrew Morton wrote:
> Dominik Brodowski <li...@dominikbrodowski.net> wrote:
> >
> > On Sun, Jun 26, 2005 at 04:03:29AM -0700, Andrew Morton wrote:
> > > - Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get
> > > the recent PCI breakage sorted out.
> >
> > pci-yenta-cardbus-fix.patch and the following patch should solve the
> > initialization time trouble. However, the ACPI-based PCI resource handling
> > is badly broken, IMHO:
> >
> > - many resources of devices don't show up in the resource trees (
> > /proc/iomem and /proc/ioports) any longer. This means that PCMCIA, but
> > also possibly other subsystems (ISA, PnP, ...) do not know which resources
> > it cannot use.
>
> Is this a recent regression? Is it only in -mm?
>
> IOW: can you identify the bad patch? Or the bad patcher ;)

It's greg's pci-somethingortheotheraboutacpi-collection-02 patch (sorry
don't remember it exactly).

It's basically replacing the PCI bus root resources with new resources.
These aren't then attached to the resource tree. However, PCI will
attach the child resources to the (unattached) bus resources.

Hence, all PCI resources remain invisible.

--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core

Vojtech Pavlik

unread,
Jun 26, 2005, 3:47:58 PM6/26/05
to Andrew Morton, Adam Kropelin, linux-...@vger.kernel.org, gr...@kroah.com, dt...@mail.ru
On Sun, Jun 26, 2005 at 12:25:38PM -0700, Andrew Morton wrote:

> Adam Kropelin <akro...@rochester.rr.com> wrote:
> >
> > I'd like to lobby for the merging into mainline of this patch from
> > git-input. It fixes a real bug, seen by real users, and has been
> > languishing in the input tree since March. It may also be a candidate
> > for the stable tree given it's one-linedness.
> >
>
> I think we can merge all of git-input into Linus's tree immediately.
>
> But if that'll take some time then sure, we can merge up this little bit.

I have some minor issues with a few of the patches. I'll take care of
that tomorrow, and then it can be merged to Linus.

--
Vojtech Pavlik
SuSE Labs, SuSE CR

Brice Goglin

unread,
Jun 26, 2005, 3:53:24 PM6/26/05
to Andrew Morton, linux-...@vger.kernel.org
Le 26.06.2005 13:03, Andrew Morton a écrit :
> - Lots of merges. I'm holding off on the 80-odd pcmcia patches until
we get
> the recent PCI breakage sorted out.

Hi Andrew,

> +alsa-maestro3-div-by-zero-fix.patch
>
> Revert an alsa change which appears to cause a divide-by-zero.

I think you can now drop this one.
My "divide error" does not appear in -mm2.
It seems that it is fixed by the following patch:

> +revert-gregkh-pci-pci-assign-unassigned-resources.patch
>
> Revert a bad patch in it

To summarize, everything seems to now work fine on my Compaq Evo
N600c laptop. Both breakages I was seeing in -mm1 are now fixed:
* the maestro3 divide error does not appear anymore
* I reported a few days ago that my yenta hang was fixed
by pci-yenta-cardbus-fix.patch

Thanks,
Brice

Dominik Brodowski

unread,
Jun 26, 2005, 4:15:54 PM6/26/05
to Andrew Morton, gr...@kroah.com, rajes...@intel.com, linux-...@vger.kernel.org
On Sun, Jun 26, 2005 at 12:17:10PM -0700, Andrew Morton wrote:
> Dominik Brodowski <li...@dominikbrodowski.net> wrote:
> >
> > On Sun, Jun 26, 2005 at 04:03:29AM -0700, Andrew Morton wrote:
> > > - Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get
> > > the recent PCI breakage sorted out.
> >
> > pci-yenta-cardbus-fix.patch and the following patch should solve the
> > initialization time trouble. However, the ACPI-based PCI resource handling
> > is badly broken, IMHO:
> >
> > - many resources of devices don't show up in the resource trees (
> > /proc/iomem and /proc/ioports) any longer. This means that PCMCIA, but
> > also possibly other subsystems (ISA, PnP, ...) do not know which resources
> > it cannot use.
>
> Is this a recent regression? Is it only in -mm?

Yes. Yes.

> IOW: can you identify the bad patch? Or the bad patcher ;)

gregkh-pci-pci-collect-host-bridge-resources-02.patch

> > - verify_root_windows() should fail if there are no iomem _or_ ioport
> > resources, not only if there are no iomem _and_ ioport resources.
>
> This too.

Same one.

Thanks,
Dominik

Grant Coady

unread,
Jun 26, 2005, 7:21:44 PM6/26/05
to Russell King, Andrew Morton, linux-...@vger.kernel.org
On Sun, 26 Jun 2005 12:42:19 +0100, Russell King <rmk+...@arm.linux.org.uk> wrote:

>On Sun, Jun 26, 2005 at 04:03:29AM -0700, Andrew Morton wrote:
>> - Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get
>> the recent PCI breakage sorted out.
>
>I'm not sure what PCI breakage you're referring to, but a lot of the
>Cardbus-centric "breakage" isn't a regression - it's new machines
>with weird PCI BIOS setups being incompatible Linux's current PCI
>bus handing strategy.
>
>I've been trying to get this fixed for a considerable time, but linux-pci
>folk seem to be disinterested.
>
>The assumption that the PCI BIOS will sanely assign the PCI bus numbers
>and that Linux does not need to reassign them is looking increasingly
>incorrect - most of the Cardbus "why can't the system see my card"
>are resolved by passing "pci=assign-busses", which causes the PCI
>subsystem to renumber all PCI busses.

Not the case for where I'm having problems, Toshiba laptop, more
info on http://scatter.mine.nu/test/linux-2.6/tosh/

--- ioports-2.6.12.1a 2005-06-27 09:00:21.000000000 +1000
+++ ioports-2.6.12-mm2a 2005-06-27 09:03:44.000000000 +1000
@@ -10,20 +10,13 @@
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
-02f8-02ff : 0000:00:07.0
0376-0376 : ide1
0378-037a : parport0
03c0-03df : vesafb
03f6-03f6 : ide0
03f8-03ff : serial
0cf8-0cff : PCI conf1
-1c00-1cff : 0000:00:07.0
-4000-40ff : PCI CardBus #02
- 4000-407f : 0000:02:00.0
- 4000-407f : xircom_cb
-4400-44ff : PCI CardBus #02
-fc00-fcff : 0000:00:0c.0
- fc00-fcff : ESS Maestro
+fc00-fcff : ESS Maestro
fd00-fd3f : motherboard
fe00-fe3f : 0000:00:05.3
fe00-fe3f : motherboard
@@ -40,8 +33,6 @@
fe90-fe97 : motherboard
fe9e-fe9e : motherboard
feac-feac : motherboard
-ff80-ff9f : 0000:00:05.2
- ff80-ff9f : uhci_hcd
-fff0-ffff : 0000:00:05.1
- fff0-fff7 : ide0
- fff8-ffff : ide1
+ff80-ff9f : uhci_hcd
+fff0-fff7 : ide0
+fff8-ffff : ide1

lilo.conf:
image = /boot/bzImage-2.6.12-mm2a
optional
label = 2.6.12-mm2ap
append="pci=assign-busses"

--- ioports-2.6.12.1a 2005-06-27 09:00:21.000000000 +1000
+++ ioports-2.6.12-mm2ap 2005-06-27 09:06:31.000000000 +1000
@@ -10,20 +10,13 @@
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
-02f8-02ff : 0000:00:07.0
0376-0376 : ide1
0378-037a : parport0
03c0-03df : vesafb
03f6-03f6 : ide0
03f8-03ff : serial
0cf8-0cff : PCI conf1
-1c00-1cff : 0000:00:07.0
-4000-40ff : PCI CardBus #02
- 4000-407f : 0000:02:00.0
- 4000-407f : xircom_cb
-4400-44ff : PCI CardBus #02
-fc00-fcff : 0000:00:0c.0
- fc00-fcff : ESS Maestro
+fc00-fcff : ESS Maestro
fd00-fd3f : motherboard
fe00-fe3f : 0000:00:05.3
fe00-fe3f : motherboard
@@ -40,8 +33,6 @@
fe90-fe97 : motherboard
fe9e-fe9e : motherboard
feac-feac : motherboard
-ff80-ff9f : 0000:00:05.2
- ff80-ff9f : uhci_hcd
-fff0-ffff : 0000:00:05.1
- fff0-fff7 : ide0
- fff8-ffff : ide1
+ff80-ff9f : uhci_hcd
+fff0-fff7 : ide0
+fff8-ffff : ide1

--Grant.

J.A. Magallon

unread,
Jun 26, 2005, 8:48:37 PM6/26/05
to Andrew Morton, linux-...@vger.kernel.org

On 06.26, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm2/
>
>
> - A reminder that there is a vger mailing list for tracking patches which
> are added to -mm. Do
>
> `echo subscribe mm-commits | mail majo...@vger.kernel.org'
>
> - Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get
> the recent PCI breakage sorted out.
>
> - Big arch/cris update.
>
>

This is missing. Is it critical ?

--- 2.6.12/mm/memory.c 2005-06-17 20:48:29.000000000 +0100
+++ linux/mm/memory.c 2005-06-21 20:31:42.000000000 +0100
@@ -1051,7 +1051,7 @@ int remap_pfn_range(struct vm_area_struc
{
pgd_t *pgd;
unsigned long next;
- unsigned long end = addr + size;
+ unsigned long end = addr + PAGE_ALIGN(size);
struct mm_struct *mm = vma->vm_mm;
int err;

--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandriva Linux release 2006.0 (Cooker) for i586
Linux 2.6.12-jam4 (gcc 4.0.1 (4.0.1-0.2mdk for Mandriva Linux release 2006.0))

Andrew Morton

unread,
Jun 26, 2005, 8:59:57 PM6/26/05
to J.A. Magallon, linux-...@vger.kernel.org
"J.A. Magallon" <jamag...@able.es> wrote:
>
> This is missing. Is it critical ?
>
> --- 2.6.12/mm/memory.c 2005-06-17 20:48:29.000000000 +0100
> +++ linux/mm/memory.c 2005-06-21 20:31:42.000000000 +0100
> @@ -1051,7 +1051,7 @@ int remap_pfn_range(struct vm_area_struc
> {
> pgd_t *pgd;
> unsigned long next;
> - unsigned long end = addr + size;
> + unsigned long end = addr + PAGE_ALIGN(size);
> struct mm_struct *mm = vma->vm_mm;
> int err;

That's already in Linus's tree.

Grant Coady

unread,
Jun 26, 2005, 9:41:32 PM6/26/05
to Dominik Brodowski, Andrew Morton, gr...@kroah.com, rajes...@intel.com, linux-...@vger.kernel.org
On Sun, 26 Jun 2005 16:04:12 +0200, Dominik Brodowski <li...@dominikbrodowski.net> wrote:

>On Sun, Jun 26, 2005 at 04:03:29AM -0700, Andrew Morton wrote:
>> - Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get
>> the recent PCI breakage sorted out.
>
>pci-yenta-cardbus-fix.patch and the following patch should solve the
>initialization time trouble. However, the ACPI-based PCI resource handling
>is badly broken, IMHO:
>

Well this patch doesn't do it for Toshiba laptop, ToPIC-100 ZV
bridge in 'auto' mode.

"-mm2b" info set on http://scatter.mine.nu/test/linux-2.6/tosh/

--- ioports-2.6.12.1a 2005-06-27 09:00:21.000000000 +1000

+++ ioports-2.6.12-mm2b 2005-06-27 09:54:45.000000000 +1000

--Grant.

-

Dominik Brodowski

unread,
Jun 27, 2005, 2:12:23 AM6/27/05
to Grant Coady, Andrew Morton, gr...@kroah.com, rajes...@intel.com, linux-...@vger.kernel.org
On Mon, Jun 27, 2005 at 11:38:34AM +1000, Grant Coady wrote:
> On Sun, 26 Jun 2005 16:04:12 +0200, Dominik Brodowski <li...@dominikbrodowski.net> wrote:
>
> >On Sun, Jun 26, 2005 at 04:03:29AM -0700, Andrew Morton wrote:
> >> - Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get
> >> the recent PCI breakage sorted out.
> >
> >pci-yenta-cardbus-fix.patch and the following patch should solve the
> >initialization time trouble. However, the ACPI-based PCI resource handling
> >is badly broken, IMHO:
> >
>
> Well this patch doesn't do it for Toshiba laptop, ToPIC-100 ZV
> bridge in 'auto' mode.

Does reverting
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm2/broken-out/gregkh-pci-pci-collect-host-bridge-resources-02.patch
help in your case?

Dominik

Reuben Farrelly

unread,
Jun 27, 2005, 3:01:57 AM6/27/05
to Andrew Morton, linux-...@vger.kernel.org
Hi,

On 26/06/2005 11:12 a.m., Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm2/
>
>
> - A reminder that there is a vger mailing list for tracking patches which
> are added to -mm. Do
>
> `echo subscribe mm-commits | mail majo...@vger.kernel.org'
>
> - Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get
> the recent PCI breakage sorted out.
>
> - Big arch/cris update.

Some bad stuff seems to be happening here (this is new to -mm2; -mm1 did not
have this problem).

It's 100% reproduceable, although seems to happen at slightly different places
in the bootup, especially at the end. Did I miss a patch for this?

reuben


Linux version 2.6.12-mm2 (root@tornado) (gcc version 4.0.0 20050622 (Red Hat
4.0.0-13)) #1 SMP Mon Jun 27 01:19:41 NZST 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
BIOS-e820: 000000001fff0000 - 000000001fff3000 (ACPI NVS)
BIOS-e820: 000000001fff3000 - 0000000020000000 (ACPI data)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
511MB LOWMEM available.
found SMP MP-table at 000f52e0
DMI 2.3 present.
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:3 APIC version 20
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1 15:3 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 20000000 (gap: 20000000:dec00000)
Built 1 zonelists
Initializing CPU#0
Kernel command line: ro root=/dev/md2 console=ttyS1,57600
PID hash table entries: 2048 (order: 11, 32768 bytes)
Detected 2813.906 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 515240k/524224k available (2133k kernel code, 8504k reserved, 920k
data, 204k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 5635.43 BogoMIPS (lpj=11270866)
Mount-cache hash table entries: 512
monitor/mwait feature present.
using mwait in idle threads.
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Physical Processor ID: 0
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU0: Thermal monitoring enabled
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
CPU0: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 03
Booting processor 1/1 eip 2000
Initializing CPU#1
Calibrating delay using timer specific routine.. 5627.52 BogoMIPS (lpj=11255052)

monitor/mwait feature present.
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Physical Processor ID: 0
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel P4/Xeon Extended MCE MSRs (12) available
CPU1: Thermal monitoring enabled
CPU1: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 03
Total of 2 processors activated (11262.95 BogoMIPS).
ENABLING IO-APIC IRQs
.TIMER: vector=0x31 pin1=2 pin2=-1
checking TSC synchronization across 2 CPUs: passed.
softlockup thread 0 started up.
Brought up 2 CPUs
softlockup thread 1 started up.
-> [0][1][ 524288] 0.0 [ 0.0] (0): ( 30446 15223)
-> [0][1][ 551882] 0.0 [ 0.0] (0): ( 12568 16550)
-> [0][1][ 580928] 0.0 [ 0.0] (0): ( -2456 15787)
-> [0][1][ 611503] 0.0 [ 0.0] (0): ( -4468 8899)
-> [0][1][ 643687] 0.0 [ 0.0] (0): ( -10064 7247)
-> [0][1][ 677565] 0.0 [ 0.0] (0): ( 6817 12064)
-> [0][1][ 713226] 0.0 [ 0.0] (0): ( 15269 10258)
-> [0][1][ 750764] 0.0 [ 0.0] (0): ( 16819 5904)
-> found max.
[0][1] working set size found: 524288, cost: 30446
---------------------
| migration cost matrix (max_cache_size: 1048576, cpu: 2813 MHz):
---------------------
[00] [01]
[00]: - 0.0(0)
[01]: 0.0(0) -
--------------------------------
| cacheflush times [1]: 0.0 (60892)
| calibration delay: 0 seconds
--------------------------------
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfb440, last bus=3
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20050309
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.2
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 *7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0,disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0,disabled.
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
Machine check exception polling timer started.
inotify device minor=63
Initializing Cryptographic API
Real Time Clock Driver v1.12
hw_random: RNG not detected
Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60
seconds).
Hangcheck: Using monotonic_clock().
cn_fork is registered
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[<c0103ad0>] dump_stack+0x17/0x19
[<c01cab4b>] spin_bug+0x5b/0x67
[<c01cac9c>] _raw_spin_lock+0x78/0x7a
[<c0314ad9>] _spin_lock+0x8/0xa
[<c0313370>] schedule+0x6c0/0xd68
[<c0100d31>] cpu_idle+0x64/0x66
[<c01002c5>] rest_init+0x25/0x27
[<c03fe8af>] start_kernel+0x154/0x167
[<c010020f>] 0xc010020f
Kernel panic - not syncing: bad locking
Badness in smp_call_function at arch/i386/kernel/smp.c:553
[<c0103ad0>] dump_stack+0x17/0x19
[<c010f980>] smp_call_function+0x137/0x13c
[<c010fb49>] smp_send_stop+0x1e/0x27
[<c011c2cf>] panic+0x4c/0x102
[<c01cab57>] __spin_lock_debug+0x0/0xcd
[<c01cac9c>] _raw_spin_lock+0x78/0x7a
[<c0314ad9>] _spin_lock+0x8/0xa
[<c0313370>] schedule+0x6c0/0xd68
[<c0100d31>] cpu_idle+0x64/0x66
[<c01002c5>] rest_init+0x25/0x27
[<c03fe8af>] start_kernel+0x154/0x167
[<c010020f>] 0xc010020f

Andrew Morton

unread,
Jun 27, 2005, 3:29:28 AM6/27/05
to Reuben Farrelly, linux-...@vger.kernel.org, Ingo Molnar
Reuben Farrelly <reube...@reub.net> wrote:
>
> ...

>
> Some bad stuff seems to be happening here (this is new to -mm2; -mm1 did not
> have this problem).
>
> It's 100% reproduceable, although seems to happen at slightly different places
> in the bootup, especially at the end. Did I miss a patch for this?
>

Why do you keep breaking my kernel?

> ...


> Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> [<c0103ad0>] dump_stack+0x17/0x19
> [<c01cab4b>] spin_bug+0x5b/0x67
> [<c01cac9c>] _raw_spin_lock+0x78/0x7a
> [<c0314ad9>] _spin_lock+0x8/0xa
> [<c0313370>] schedule+0x6c0/0xd68
> [<c0100d31>] cpu_idle+0x64/0x66
> [<c01002c5>] rest_init+0x25/0x27
> [<c03fe8af>] start_kernel+0x154/0x167
> [<c010020f>] 0xc010020f
> Kernel panic - not syncing: bad locking

That's odd - we lost a printk there:

printk("BUG: spinlock %s on CPU#%d, %s/%d, %p\n", msg,
smp_processor_id(), current->comm, current->pid, lock);

which is a shame, because it would have told us stuff. Do you have any
traces which do have that message?

Anyway, scary trace. It look like some spinlock is thought to be in the
wrong state in schedule(). Send the .config, please.

Reuben Farrelly

unread,
Jun 27, 2005, 3:51:13 AM6/27/05
to Andrew Morton, linux-...@vger.kernel.org, Ingo Molnar
Hi,

On 27/06/2005 7:24 p.m., Andrew Morton wrote:
> Reuben Farrelly <reube...@reub.net> wrote:
>> ...
>>
>> Some bad stuff seems to be happening here (this is new to -mm2; -mm1 did not
>> have this problem).
>>
>> It's 100% reproduceable, although seems to happen at slightly different places
>> in the bootup, especially at the end. Did I miss a patch for this?
>>
>
> Why do you keep breaking my kernel?

Sadistic enjoyment ;-)

>> Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
>> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>> [<c0103ad0>] dump_stack+0x17/0x19
>> [<c01cab4b>] spin_bug+0x5b/0x67
>> [<c01cac9c>] _raw_spin_lock+0x78/0x7a
>> [<c0314ad9>] _spin_lock+0x8/0xa
>> [<c0313370>] schedule+0x6c0/0xd68
>> [<c0100d31>] cpu_idle+0x64/0x66
>> [<c01002c5>] rest_init+0x25/0x27
>> [<c03fe8af>] start_kernel+0x154/0x167
>> [<c010020f>] 0xc010020f
>> Kernel panic - not syncing: bad locking
>
> That's odd - we lost a printk there:
>
> printk("BUG: spinlock %s on CPU#%d, %s/%d, %p\n", msg,
> smp_processor_id(), current->comm, current->pid, lock);
>
> which is a shame, because it would have told us stuff. Do you have any
> traces which do have that message?

Uh. Likely got munged within hyperterm.

Here's a better one just created using QVT:

usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
usb 3-1: new full speed USB device using uhci_hcd and address 2
hub 3-1:1.0: USB hub found
hub 3-1:1.0: 4 ports detected
usbcore: registered new driver hiddev
usb 4-1: new full speed USB device using uhci_hcd and address 2
drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 0
proto 2 vid 0x03F0 pid 0x6204
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
mice: PS/2 mouse device common for all mice
input: PC Speaker
md: raid1 personality registered as nr 3
md: md driver 0.90.2 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 3.38
NET: Registered protocol family 2
IP: routing cache hash table of 1024 buckets, 24Kbytes
TCP established hash table entries: 32768 (order: 7, 786432 bytes)
TCP bind hash table entries: 32768 (order: 7, 655360 bytes)
TCP: Hash tables configured (established 32768 bind 32768)
TCP reno registered
GRE over IPv4 tunneling driver
ip_conntrack version 2.1 (4095 buckets, 32760 max) - 212 bytes per conntrack
usb 3-1.1: new low speed USB device using uhci_hcd and address 3
BUG: spinlock recursion on CPU#0, swapper/0, c1407160


[<c0103ad0>] dump_stack+0x17/0x19
[<c01cab4b>] spin_bug+0x5b/0x67
[<c01cac9c>] _raw_spin_lock+0x78/0x7a
[<c0314ad9>] _spin_lock+0x8/0xa

[<c0117399>] scheduler_tick+0xd0/0x37c
[<c01256b3>] update_process_times+0x58/0xd7
[<c0110f50>] smp_apic_timer_interrupt+0xde/0xe0
[<c0103614>] apic_timer_interrupt+0x1c/0x24
[<c0100d1e>] cpu_idle+0x51/0x66


[<c01002c5>] rest_init+0x25/0x27
[<c03fe8af>] start_kernel+0x154/0x167
[<c010020f>] 0xc010020f
Kernel panic - not syncing: bad locking

Badness in smp_call_function at arch/i386/kernel/smp.c:553
[<c0103ad0>] dump_stack+0x17/0x19
[<c010f980>] smp_call_function+0x137/0x13c
[<c010fb49>] smp_send_stop+0x1e/0x27
[<c011c2cf>] panic+0x4c/0x102
[<c01cab57>] __spin_lock_debug+0x0/0xcd
[<c01cac9c>] _raw_spin_lock+0x78/0x7a
[<c0314ad9>] _spin_lock+0x8/0xa

[<c0117399>] scheduler_tick+0xd0/0x37c
[<c01256b3>] update_process_times+0x58/0xd7
[<c0110f50>] smp_apic_timer_interrupt+0xde/0xe0
[<c0103614>] apic_timer_interrupt+0x1c/0x24
[<c0100d1e>] cpu_idle+0x51/0x66


[<c01002c5>] rest_init+0x25/0x27
[<c03fe8af>] start_kernel+0x154/0x167
[<c010020f>] 0xc010020f

> Anyway, scary trace. It look like some spinlock is thought to be in the


> wrong state in schedule(). Send the .config, please.

Now online at http://www.reub.net/kernel/.config

Reuben

Russell King

unread,
Jun 27, 2005, 4:13:44 AM6/27/05
to Grant Coady, Andrew Morton, linux-...@vger.kernel.org
On Mon, Jun 27, 2005 at 09:17:34AM +1000, Grant Coady wrote:
> Not the case for where I'm having problems, Toshiba laptop, more
> info on http://scatter.mine.nu/test/linux-2.6/tosh/

Yes in this case. The PCI resources are the ones which say either
PCI CardBus, PCI Bus, or are of the format: xxxx:xx:xx.x, and all
of them are missing.

The ESS Maestro and others which were below these are driver
resources created by the drivers themselves, not the PCI subsystem.
Hence these still show up.

--

Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core

Andrew Morton

unread,
Jun 27, 2005, 4:27:51 AM6/27/05
to Reuben Farrelly, linux-...@vger.kernel.org, mi...@elte.hu
Reuben Farrelly <reube...@reub.net> wrote:
>
> > Anyway, scary trace. It look like some spinlock is thought to be in the
> > wrong state in schedule(). Send the .config, please.
>
> Now online at http://www.reub.net/kernel/.config

Me too.

BUG: spinlock recursion on CPU#0, swapper/0, c120d520
[<c01039ed>] dump_stack+0x19/0x20
[<c01d9af2>] spin_bug+0x42/0x54
[<c01d9bfa>] _raw_spin_lock+0x3e/0x84
[<c031d0ad>] _spin_lock+0x9/0x10
[<c031b9e9>] schedule+0x479/0xbc8
[<c0100cb4>] cpu_idle+0x88/0x8c
[<c01002c1>] rest_init+0x21/0x28
[<c0442899>] start_kernel+0x151/0x158


[<c010020f>] 0xc010020f
Kernel panic - not syncing: bad locking

The bug is in the new spinlock debugging code itself. Ingo, can you test
that .config please?

Reuben, I guess disabling CONFIG_DEBUG_SPINLOCK will get you going.

Grant Coady

unread,
Jun 27, 2005, 4:57:30 AM6/27/05
to Dominik Brodowski, Andrew Morton, gr...@kroah.com, rajes...@intel.com, linux-...@vger.kernel.org

CardBus 32-bit NIC appeared with this patch reverted :)

--Grant.

Ingo Molnar

unread,
Jun 27, 2005, 5:39:17 AM6/27/05
to Andrew Morton, Reuben Farrelly, linux-...@vger.kernel.org

is the fput()/sysfs_release() crash below known?

Ingo

Linux version 2.6.12-mm2 (mingo@jupiter) (gcc version 3.4.1 20040831 (R
ed Hat 3.4.1-10)) #11 SMP Mon Jun 27 11:19:41 CEST 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)


BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)

BIOS-e820: 0000000000100000 - 0000000010000000 (usable)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
256MB LOWMEM available.
found SMP MP-table at 000f5b30
On node 0 totalpages: 65536
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 61440 pages, LIFO batch:31
HighMem zone: 0 pages, LIFO batch:1
early console enabled
DMI 2.2 present.
ABIT i440BX-W83977 detected: force use of acpi=ht
ACPI: Unable to locate RSDP
Intel MultiProcessor Specification v1.1
Virtual Wire compatibility mode.
OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000
Processor #0 6:6 APIC version 17
Processor #1 6:6 APIC version 17
I/O APIC #2 Version 17 at 0xFEC00000.


Enabling APIC mode: Flat. Using 1 I/O APICs

Processors: 2
Allocating PCI resources starting at 10000000 (gap: 10000000:eec00000)
Built 1 zonelists
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Initializing CPU#0
Kernel command line: root=/dev/hda1 debug earlyprintk=serial,ttyS0,
115200 console=ttyS0,115200 console=tty0 3 maxcpus=2 nmi_watchdog
=1 debug profile=0
kernel profiling enabled (shift: 0)


PID hash table entries: 2048 (order: 11, 32768 bytes)

Detected 467.796 MHz processor.


Using tsc for high-res timesource

disabling early console
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 244664k/262144k available (2592k kernel code, 17052k reserved,
1061k data, 224k init, 0k highmem)


Checking if this processor honours the WP bit even in supervisor mode..

Ok.
Calibrating delay using timer specific routine.. 937.21 BogoMIPS (lpj=
1874423)


Mount-cache hash table entries: 512

CPU: After generic identify, caps: 0183fbff 00000000 00000000 00000000
00000000 00000000 00000000
CPU: After vendor identify, caps: 0183fbff 00000000 00000000 00000000 0
0000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
CPU: After all inits, caps: 0183fbff 00000000 00000000 00000040 0000000
0 00000000 00000000


Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.

Enabling fast FPU save and restore... done.

Checking 'hlt' instruction... OK.
CPU0: Intel Celeron (Mendocino) stepping 05


Booting processor 1/1 eip 2000
Initializing CPU#1

Calibrating delay using timer specific routine.. 935.62 BogoMIPS (lpj=
1871246)
CPU: After generic identify, caps: 0183fbff 00000000 00000000 00000000
00000000 00000000 00000000
CPU: After vendor identify, caps: 0183fbff 00000000 00000000 00000000 0
0000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
CPU: After all inits, caps: 0183fbff 00000000 00000000 00000040 0000000
0 00000000 00000000


Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.

CPU1: Intel Celeron (Mendocino) stepping 05
Total of 2 processors activated (1872.83 BogoMIPS).
ENABLING IO-APIC IRQs
.TIMER: vector=0x31 pin1=2 pin2=0


checking TSC synchronization across 2 CPUs: passed.
softlockup thread 0 started up.
Brought up 2 CPUs
softlockup thread 1 started up.

-> [0][1][ 65536] 0.3 [ 0.3] (0): ( 357620 178810)
-> [0][1][ 68985] 0.3 [ 0.3] (0): ( 354253 91088)
-> [0][1][ 72615] 0.3 [ 0.3] (0): ( 390935 63885)
-> [0][1][ 76436] 0.4 [ 0.4] (0): ( 415617 44283)
-> [0][1][ 80458] 0.4 [ 0.4] (0): ( 428850 28758)
-> [0][1][ 84692] 0.4 [ 0.4] (0): ( 460558 30233)
-> [0][1][ 89149] 0.5 [ 0.5] (0): ( 501929 35802)
-> [0][1][ 93841] 0.5 [ 0.5] (0): ( 543036 38454)
-> [0][1][ 98780] 0.6 [ 0.6] (0): ( 609270 52344)
-> [0][1][ 103978] 0.5 [ 0.6] (0): ( 596005 32804)
-> [0][1][ 109450] 0.6 [ 0.6] (0): ( 607209 22004)
-> [0][1][ 115210] 0.6 [ 0.6] (0): ( 643212 29003)
-> [0][1][ 121273] 0.7 [ 0.7] (0): ( 716535 51163)
-> [0][1][ 127655] 0.7 [ 0.7] (0): ( 795865 65246)
-> [0][1][ 134373] 0.7 [ 0.7] (0): ( 745335 57888)
-> [0][1][ 141445] 0.7 [ 0.7] (0): ( 796304 54428)
-> [0][1][ 148889] 0.8 [ 0.8] (0): ( 820203 39163)
-> [0][1][ 156725] 0.7 [ 0.8] (0): ( 716504 71431)
-> [0][1][ 164973] 0.6 [ 0.8] (0): ( 679884 54025)
-> [0][1][ 173655] 0.6 [ 0.8] (0): ( 662305 35802)
-> [0][1][ 182794] 0.5 [ 0.8] (0): ( 598857 49625)
-> [0][1][ 192414] 0.6 [ 0.8] (0): ( 628063 39415)
-> [0][1][ 202541] 0.5 [ 0.8] (0): ( 577476 45001)
-> found max.
[0][1] working set size found: 148889, cost: 820203
---------------------
| migration cost matrix (max_cache_size: 131072, cpu: 467 MHz):
---------------------
[00] [01]
[00]: - 1.6(0)
[01]: 1.6(0) -
--------------------------------
| cacheflush times [1]: 1.6 (1640406)


| calibration delay: 0 seconds
--------------------------------
NET: Registered protocol family 16

PCI: PCI BIOS revision 2.10 entry at 0xfb420, last bus=1


PCI: Using configuration type 1
mtrr: v2.0 (20020519)

mtrr: your CPUs had inconsistent fixed MTRR settings
mtrr: probably your BIOS does not setup all CPUs.
mtrr: corrected configuration.
ACPI: Subsystem revision 20050309
ACPI: Interpreter disabled.


SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub

PCI: Probing PCI hardware


PCI: Probing PCI hardware (bus 00)

Boot video device is 0000:01:00.0
PCI: Using IRQ router PIIX/ICH [8086/7110] at 0000:00:07.0
PCI->APIC IRQ transform: 0000:00:07.2[D] -> IRQ 19
PCI->APIC IRQ transform: 0000:00:0b.0[A] -> IRQ 18
PCI->APIC IRQ transform: 0000:00:0d.0[A] -> IRQ 17
PCI->APIC IRQ transform: 0000:00:0f.0[A] -> IRQ 16
PCI->APIC IRQ transform: 0000:00:13.0[A] -> IRQ 18
PCI->APIC IRQ transform: 0000:00:13.1[B] -> IRQ 18
PCI->APIC IRQ transform: 0000:01:00.0[A] -> IRQ 16


Machine check exception polling timer started.
inotify device minor=63
Initializing Cryptographic API

Limiting direct PCI/PCI transfers.


Real Time Clock Driver v1.12

Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin
is 60 seconds).
Hangcheck: Using monotonic_clock().
cn_fork is registered
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1

Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enable
d

ÿttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
pktcdvd: v0.2.0a 2004-07-14 Jens Axboe (ax...@suse.de) and petero2@teli
a.com
Intel(R) PRO/1000 Network Driver - version 6.0.54-k2-NAPI
Copyright (c) 1999-2004 Intel Corporation.
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e100: Intel(R) PRO/100 Network Driver, 3.4.8-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
e100: eth1: e100_probe: addr 0xef140000, irq 16, MAC addr 00:90:27:8C:A
0:50
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebu
s=xx
PIIX4: IDE controller at PCI slot 0000:00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: QUANTUM FIREBALLP LM20.5, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: QUANTUM FIREBALL SE4.3A, ATA DISK drive
hdd: LG CD-ROM CRD-8522B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 40132503 sectors (20547 MB) w/1900KiB Cache, CHS=39813/16/63, UD
MA(33)
hda: cache flushes not supported
hda: hda1
hdc: max request size: 128KiB
hdc: 8418816 sectors (4310 MB) w/80KiB Cache, CHS=14848/9/63, UDMA(33
)
hdc: cache flushes not supported
hdc: hdc1 hdc2
libata version 1.11 loaded.
USB Universal Host Controller Interface driver v2.3
uhci_hcd 0000:00:07.2: Intel Corporation 82371AB/EB/MB PIIX4 USB
uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:07.2: irq 19, io base 0x0000b000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected


usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver

usbcore: registered new driver hiddev

usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
mice: PS/2 mouse device common for all mice
input: PC Speaker
md: raid1 personality registered as nr 3
md: md driver 0.90.2 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 3.38
NET: Registered protocol family 2

input: AT Translated Set 2 keyboard on isa0060/serio0
IP: routing cache hash table of 512 buckets, 12Kbytes
TCP established hash table entries: 16384 (order: 6, 393216 bytes)
TCP bind hash table entries: 16384 (order: 6, 327680 bytes)
TCP: Hash tables configured (established 16384 bind 16384)


TCP reno registered
GRE over IPv4 tunneling driver

ip_conntrack version 2.1 (2048 buckets, 16384 max) - 212 bytes per conn
track
ip_tables: (C) 2000-2002 Netfilter core team
NET: Registered protocol family 1
NET: Registered protocol family 17
Testing NMI watchdog ... OK.
Starting balanced_irq
Using IPI Shortcut mode
BIOS EDD facility v0.16 2004-Jun-25, 2 devices found
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 224k freed
Unable to handle kernel paging request at virtual address 6b6b6ceb
printing eip:
c018b51c
*pde = 00000000
Oops: 0002 [#1]
SMP
Modules linked in:
CPU: 1
EIP: 0060:[<c018b51c>] Not tainted VLI
EFLAGS: 00010206 (2.6.12-mm2)
EIP is at sysfs_release+0x3f/0x79
eax: 6b6b6beb ebx: 6b6b6b6b ecx: ce5b5e64 edx: 00000000
esi: cf266ca4 edi: cfa3a544 ebp: ce635f50 esp: ce635f44
ds: 007b es: 007b ss: 0068
Process udev (pid: 1286, threadinfo=ce634000 task=c1fe6040)
Stack: 00000010 c1ca8b78 c1d4656c ce635f74 c01580b2 00000000 cf399e10 c
f399e10
ce5b5e64 c1d4656c c1cb275c 00000000 ce635f84 c0157f36 c1cb275c c
1d4656c
ce635f9c c0156873 00000004 00000004 c1cb275c c1cb2760 ce635fb4 c
015690a
Call Trace:
[<c0103a18>] show_stack+0x7c/0x92
[<c0103b99>] show_registers+0x152/0x1ca
[<c0103d96>] die+0xf4/0x16f
[<c011433f>] do_page_fault+0x466/0x684
[<c0103683>] error_code+0x4f/0x54
[<c01580b2>] __fput+0x176/0x1a9
[<c0157f36>] fput+0x3b/0x41
[<c0156873>] filp_close+0x36/0x65
[<c015690a>] sys_close+0x68/0x83
[<c0102b13>] sysenter_past_esp+0x54/0x75
Code: 58 8b 70 14 8b 41 58 8b 40 14 85 f6 8b 58 04 74 07 89 f0 e8 8b 22
05 00 85 db 74 1a b8 00 e0 ff ff 21 e0 8b 40 10 c1 e0 07 01 d8 <ff> 88
00 01 00 00 83 3b 02 74 22 85 ff 74 0e 8b 47 0c 85 c0 75

Ingo Molnar

unread,
Jun 27, 2005, 5:52:11 AM6/27/05
to Andrew Morton, Reuben Farrelly, linux-...@vger.kernel.org

* Andrew Morton <ak...@osdl.org> wrote:

> Reuben Farrelly <reube...@reub.net> wrote:
> >
> > > Anyway, scary trace. It look like some spinlock is thought to be in the
> > > wrong state in schedule(). Send the .config, please.
> >
> > Now online at http://www.reub.net/kernel/.config
>
> Me too.
>
> BUG: spinlock recursion on CPU#0, swapper/0, c120d520
> [<c01039ed>] dump_stack+0x19/0x20
> [<c01d9af2>] spin_bug+0x42/0x54
> [<c01d9bfa>] _raw_spin_lock+0x3e/0x84
> [<c031d0ad>] _spin_lock+0x9/0x10
> [<c031b9e9>] schedule+0x479/0xbc8
> [<c0100cb4>] cpu_idle+0x88/0x8c
> [<c01002c1>] rest_init+0x21/0x28
> [<c0442899>] start_kernel+0x151/0x158
> [<c010020f>] 0xc010020f
> Kernel panic - not syncing: bad locking
>
> The bug is in the new spinlock debugging code itself. Ingo, can you
> test that .config please?

couldnt reproduce it on an UP box, nor on an SMP/HT 2/4-way box, but it
finally triggered on a 2-way SMP box.

the bug is that current->pid is not a unique identifier on SMP (doh!).

The patch below fixes the bug - which also happens to be a speedup for
the debugging code, as the ->pid dereferencing does not have to be done
anymore. Also, i've disabled the panicing for now.

Ingo

- change owner_pid to owner, to fix bad pid uniqueness assumption on SMP
- some more debug output printed
- dont panic for now

Signed-off-by: Ingo Molnar <mi...@elte.hu>

include/linux/spinlock_types.h | 16 ++++++++++------
kernel/sched.c | 2 +-
lib/spinlock_debug.c | 30 +++++++++++++++++++-----------
3 files changed, 30 insertions(+), 18 deletions(-)

Index: linux/include/linux/spinlock_types.h
===================================================================
--- linux.orig/include/linux/spinlock_types.h
+++ linux/include/linux/spinlock_types.h
@@ -21,11 +21,12 @@ typedef struct {
unsigned int break_lock;
#endif
#ifdef CONFIG_DEBUG_SPINLOCK
- unsigned int magic, owner_pid, owner_cpu;
+ unsigned int magic, owner_cpu;
+ void *owner;
#endif
} spinlock_t;

-#define SPINLOCK_MAGIC 0xdead4ead
+#define SPINLOCK_MAGIC 0xdead4ead

typedef struct {
raw_rwlock_t raw_lock;
@@ -33,22 +34,25 @@ typedef struct {
unsigned int break_lock;
#endif
#ifdef CONFIG_DEBUG_SPINLOCK
- unsigned int magic, owner_pid, owner_cpu;
+ unsigned int magic, owner_cpu;
+ void *owner;
#endif
} rwlock_t;

-#define RWLOCK_MAGIC 0xdeaf1eed
+#define RWLOCK_MAGIC 0xdeaf1eed
+
+#define SPINLOCK_OWNER_INIT ((void *)-1L)

#ifdef CONFIG_DEBUG_SPINLOCK
# define SPIN_LOCK_UNLOCKED \
(spinlock_t) { .raw_lock = __RAW_SPIN_LOCK_UNLOCKED, \
.magic = SPINLOCK_MAGIC, \
- .owner_pid = -1, \
+ .owner = SPINLOCK_OWNER_INIT, \
.owner_cpu = -1 }
#define RW_LOCK_UNLOCKED \
(rwlock_t) { .raw_lock = __RAW_RW_LOCK_UNLOCKED, \
.magic = RWLOCK_MAGIC, \
- .owner_pid = -1, \
+ .owner = SPINLOCK_OWNER_INIT, \
.owner_cpu = -1 }
#else
# define SPIN_LOCK_UNLOCKED \
Index: linux/kernel/sched.c
===================================================================
--- linux.orig/kernel/sched.c
+++ linux/kernel/sched.c
@@ -1604,7 +1604,7 @@ static inline void finish_task_switch(ru
prev_task_flags = prev->flags;
#ifdef CONFIG_DEBUG_SPINLOCK
/* this is a valid case when another task releases the spinlock */
- rq->lock.owner_pid = current->pid;
+ rq->lock.owner = current;
#endif
finish_arch_switch(prev);
finish_lock_switch(rq, prev);
Index: linux/lib/spinlock_debug.c
===================================================================
--- linux.orig/lib/spinlock_debug.c
+++ linux/lib/spinlock_debug.c
@@ -14,16 +14,24 @@
static void spin_bug(spinlock_t *lock, const char *msg)
{
static long print_once = 1;
+ struct task_struct *owner = NULL;

if (xchg(&print_once, 0)) {
- printk("BUG: spinlock %s on CPU#%d, %s/%d, %p\n", msg,
- smp_processor_id(), current->comm, current->pid, lock);
+ if (lock->owner && lock->owner != SPINLOCK_OWNER_INIT)
+ owner = lock->owner;
+ printk("BUG: spinlock %s on CPU#%d, %s/%d\n",
+ msg, smp_processor_id(), current->comm, current->pid);
+ printk(" lock: %p, .magic: %08x, .owner: %s/%d, .owner_cpu: %d\n",
+ lock, lock->magic,
+ owner ? owner->comm : "<none>",
+ owner ? owner->pid : -1,
+ lock->owner_cpu);
dump_stack();
#ifdef CONFIG_SMP
/*
* We cannot continue on SMP:
*/
- panic("bad locking");
+// panic("bad locking");
#endif
}
}
@@ -33,7 +41,7 @@ static void spin_bug(spinlock_t *lock, c
static inline void debug_spin_lock_before(spinlock_t *lock)
{
SPIN_BUG_ON(lock->magic != SPINLOCK_MAGIC, lock, "bad magic");
- SPIN_BUG_ON(lock->owner_pid == current->pid, lock, "recursion");
+ SPIN_BUG_ON(lock->owner == current, lock, "recursion");
SPIN_BUG_ON(lock->owner_cpu == raw_smp_processor_id(),
lock, "cpu recursion");
}
@@ -41,17 +49,17 @@ static inline void debug_spin_lock_befor
static inline void debug_spin_lock_after(spinlock_t *lock)
{
lock->owner_cpu = raw_smp_processor_id();
- lock->owner_pid = current->pid;
+ lock->owner = current;
}

static inline void debug_spin_unlock(spinlock_t *lock)
{
SPIN_BUG_ON(lock->magic != SPINLOCK_MAGIC, lock, "bad magic");
SPIN_BUG_ON(!spin_is_locked(lock), lock, "already unlocked");
- SPIN_BUG_ON(lock->owner_pid != current->pid, lock, "wrong owner");
+ SPIN_BUG_ON(lock->owner != current, lock, "wrong owner");
SPIN_BUG_ON(lock->owner_cpu != raw_smp_processor_id(),
lock, "wrong CPU");
- lock->owner_pid = -1;
+ lock->owner = SPINLOCK_OWNER_INIT;
lock->owner_cpu = -1;
}

@@ -176,7 +184,7 @@ void _raw_read_unlock(rwlock_t *lock)
static inline void debug_write_lock_before(rwlock_t *lock)
{
RWLOCK_BUG_ON(lock->magic != RWLOCK_MAGIC, lock, "bad magic");
- RWLOCK_BUG_ON(lock->owner_pid == current->pid, lock, "recursion");
+ RWLOCK_BUG_ON(lock->owner == current, lock, "recursion");
RWLOCK_BUG_ON(lock->owner_cpu == raw_smp_processor_id(),
lock, "cpu recursion");
}
@@ -184,16 +192,16 @@ static inline void debug_write_lock_befo
static inline void debug_write_lock_after(rwlock_t *lock)
{
lock->owner_cpu = raw_smp_processor_id();
- lock->owner_pid = current->pid;
+ lock->owner = current;
}

static inline void debug_write_unlock(rwlock_t *lock)
{
RWLOCK_BUG_ON(lock->magic != RWLOCK_MAGIC, lock, "bad magic");
- RWLOCK_BUG_ON(lock->owner_pid != current->pid, lock, "wrong owner");
+ RWLOCK_BUG_ON(lock->owner != current, lock, "wrong owner");
RWLOCK_BUG_ON(lock->owner_cpu != raw_smp_processor_id(),
lock, "wrong CPU");
- lock->owner_pid = -1;
+ lock->owner = SPINLOCK_OWNER_INIT;
lock->owner_cpu = -1;

Reuben Farrelly

unread,
Jun 27, 2005, 7:01:11 AM6/27/05
to Ingo Molnar, Andrew Morton, linux-...@vger.kernel.org
Hi,

This patch fixes it - thanks Ingo.

reuben

Vojtech Pavlik

unread,
Jun 27, 2005, 12:27:50 PM6/27/05
to Andrew Morton, Adam Kropelin, linux-...@vger.kernel.org, gr...@kroah.com, dt...@mail.ru
On Sun, Jun 26, 2005 at 12:25:38PM -0700, Andrew Morton wrote:

> > I'd like to lobby for the merging into mainline of this patch from
> > git-input. It fixes a real bug, seen by real users, and has been
> > languishing in the input tree since March. It may also be a candidate
> > for the stable tree given it's one-linedness.
>
> I think we can merge all of git-input into Linus's tree immediately.

I've checked it, the patches I had originally problems with are already
fixed, it's ready for merging.

--
Vojtech Pavlik
SuSE Labs, SuSE CR

RogérioBrito

unread,
Jun 27, 2005, 12:47:37 PM6/27/05
to Andrew Morton, linux-...@vger.kernel.org
Hi, Andrew.

I am experiencing problems with -mm kernels and my firewire HD. I can u
se
it without any problems with Linus's 2.6.12, but I had problems with bo
th
-mm1 and -mm2 (I just compiled -mm2 to see if the problem would go away
,
but it didn't).

I am using the same .config file for all compiles, except that I wanted
to
use the -mm tree for some things that I think would be orthogonal to th
e
issue (like using FUSE, for example).

I can't provide more details now, but as soon as I go to work with the
machine that presented the problem, I can give you all the details.

Essentially, what happens with -mm kernels that don't happen with Linus
's
kernel is that the sbp2 module gets loaded, but it seems that the subsy
stem
never gets to actually see the partitions of the HD (I am using a HFS+
formatted disk for transfers of data between Linux and MacOS X).

If others also have the problem, I would like to know about it.

The Firewire controller that I am using is a vanilla VIA card and the H
D is
a Seagate PATA HD in a Firewire enclosure (it's a ADS Tech DLX-185, if
I am
not mistaken).

As I said, I can provide further details if wanted/needed.


Thanks for your work, Rogério.

--
Rogério Brito : rbr...@ime.usp.br : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat: http://freshmeat.net/projects/algorithms/

Rajesh Shah

unread,
Jun 27, 2005, 4:21:07 PM6/27/05
to Dominik Brodowski, Andrew Morton, gr...@kroah.com, rajes...@intel.com, linux-...@vger.kernel.org
On Sun, Jun 26, 2005 at 10:14:14PM +0200, Dominik Brodowski wrote:
> > Is this a recent regression? Is it only in -mm?
>
> Yes. Yes.
>
> > IOW: can you identify the bad patch? Or the bad patcher ;)
>
> gregkh-pci-pci-collect-host-bridge-resources-02.patch
>

Guilty as charged. I will look at providing a fix. In the meantime,
you can drop this patch if you like Andrew.

> > > - verify_root_windows() should fail if there are no iomem _or_ ioport
> > > resources, not only if there are no iomem _and_ ioport resources.
> >

No, I actually saw production (or close to production) machines
where BIOS was deliberately only programming memory resources, no
IO. In fact, I had to change the check to the current form for such
machines.

Rajesh

Dominik Brodowski

unread,
Jun 27, 2005, 4:34:24 PM6/27/05
to Rajesh Shah, Andrew Morton, gr...@kroah.com, linux-...@vger.kernel.org
On Mon, Jun 27, 2005 at 01:18:11PM -0700, Rajesh Shah wrote:
> > > > - verify_root_windows() should fail if there are no iomem _or_ ioport
> > > > resources, not only if there are no iomem _and_ ioport resources.
> > >
>
> No, I actually saw production (or close to production) machines
> where BIOS was deliberately only programming memory resources, no
> IO. In fact, I had to change the check to the current form for such
> machines.

Well, what should be done in this case? IMO we should fall back to the
"previous" behaviour -- is a
kfree(bus->resource[i]);
bus->resource[i] = bres[i];
needed for this to happen?

Thanks,
Dominik

Andrew Morton

unread,
Jun 27, 2005, 5:47:40 PM6/27/05
to Ingo Molnar, reube...@reub.net, linux-...@vger.kernel.org
Ingo Molnar <mi...@elte.hu> wrote:
>
> is the fput()/sysfs_release() crash below known?

It doesn't ring any bells.

You have a use-after-free error when udev is dinking with a sysfs file. It
could be anything. Could you debug it a bit, please, work out which file
caused the crash?

Andrew Morton

unread,
Jun 27, 2005, 7:48:14 PM6/27/05
to RogérioBrito, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net

(Added linux1394-devel)

Rogério Brito <rbr...@ime.usp.br> wrote:
>
> Hi, Andrew.
>
> I am experiencing problems with -mm kernels and my firewire HD. I can
use
> it without any problems with Linus's 2.6.12, but I had problems with
both
> -mm1 and -mm2 (I just compiled -mm2 to see if the problem would go aw
ay,
> but it didn't).
>
> I am using the same .config file for all compiles, except that I want

ed to


> use the -mm tree for some things that I think would be orthogonal to
the
> issue (like using FUSE, for example).
>
> I can't provide more details now, but as soon as I go to work with th
e
> machine that presented the problem, I can give you all the details.
>
> Essentially, what happens with -mm kernels that don't happen with Lin

us's


> kernel is that the sbp2 module gets loaded, but it seems that the sub
system
> never gets to actually see the partitions of the HD (I am using a HFS
+
> formatted disk for transfers of data between Linux and MacOS X).
>
> If others also have the problem, I would like to know about it.
>
> The Firewire controller that I am using is a vanilla VIA card and the

HD is


> a Seagate PATA HD in a Firewire enclosure (it's a ADS Tech DLX-185, i
f I am
> not mistaken).
>
> As I said, I can provide further details if wanted/needed.
>
>

Could you please generate the dmesg output from 2.6.12 and 2.6.12-mm2 a
nd,
if there are any relevant-looking differences, send them?

Also, try:

wget ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.
12/2.6.12-mm2/broken-out/gregkh-pci-pci-collect-host-bridge-resources-0
2.patch

patch -R -p1 < gregkh-pci-pci-collect-host-bridge-resources-02.patch

Thanks.

RogérioBrito

unread,
Jun 27, 2005, 9:04:10 PM6/27/05
to Andrew Morton, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
On Jun 27 2005, Andrew Morton wrote:
> Could you please generate the dmesg output from 2.6.12 and 2.6.12-mm2
and,
> if there are any relevant-looking differences, send them?

Ok, I put them both on <http://www.ime.usp.br/~rbrito/bug/>.

> Also, try:
>
> wget (...)
> patch -R -p1 < gregkh-pci-pci-collect-host-bridge-resources-02.patch

Ok. I am compiling the kernel right now and will post the results as so
on
as I am finished.

> Thanks.

Thank you very much for your feedback, Rogério.

P.S.: I just noticed right now that the patch listed above changes only
arch/i386/pci/acpi.c, but I am not using ACPI. Well, I will proceed any
way.


--
Rogério Brito : rbr...@ime.usp.br : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat: http://freshmeat.net/projects/algorithms/

RogérioBrito

unread,
Jun 27, 2005, 10:27:24 PM6/27/05
to Andrew Morton, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
Hi, Andrew.

On Jun 27 2005, Rogério Brito wrote:
> Ok, I put them both on <http://www.ime.usp.br/~rbrito/bug/>.

(...)


> P.S.: I just noticed right now that the patch listed above changes on
ly
> arch/i386/pci/acpi.c, but I am not using ACPI. Well, I will proceed a
nyway.

Well, as I felt before, backing out the patch didn't work. I posted the
dmesg of the new compilation on the page above like I did before.

Is there any other patch that I should try to revert?


Thanks, Rogério.

Andrew Morton

unread,
Jun 27, 2005, 11:25:31 PM6/27/05
to Rogério Brito, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
Rogério Brito <rbr...@ime.usp.br> wrote:
>
> On Jun 27 2005, Andrew Morton wrote:
> > Could you please generate the dmesg output from 2.6.12 and 2.6.12-
mm2 and,

> > if there are any relevant-looking differences, send them?
>
> Ok, I put them both on <http://www.ime.usp.br/~rbrito/bug/>.

Great, here we are:

-ieee1394: Node added: ID:BUS[0-00:1023] GUID[0050c501e00010e8]
+ieee1394: Node added: ID:BUS[0-01:1023] GUID[0050c501e00010e8]
+ieee1394: The root node is not cycle master capable; selecting a new r
oot node and resetting...
+ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
SCSI subsystem initialized
sbp2: $Rev: 1219 $ Ben Collins <bcol...@debian.org>
@@ -300,14 +308,6 @@
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Vendor: ST316002 Model: 1A Rev: 3.06
- Type: Direct-Access ANSI SCSI revision: 06
-SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
-sda: asking for cache data failed
-sda: assuming drive cache: write through
-SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
-sda: asking for cache data failed
-sda: assuming drive cache: write through
- sda: [mac] sda1 sda2 sda3 sda4
-Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
+ Type: Unknown ANSI SCSI revision: 04
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0050c501e00010e8]

Could the 1394 guys please suggest what might have caused this?

Ben Collins

unread,
Jun 28, 2005, 12:03:17 AM6/28/05
to Andrew Morton, Rog?rio Brito, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
> Could the 1394 guys please suggest what might have caused this?

Unless something is in git that isn't in subversion, nothing has really
changed in the sbp2 module for 5-6 months.

Doesn't appear to be a problem with the ieee1394 subsystem itself (the
cycle master thing isn't all that important), since that would cause not
even being able to send/recv packets.

--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
SwissDisk - http://www.swissdisk.com/

RogérioBrito

unread,
Jun 28, 2005, 3:32:11 AM6/28/05
to Ben Collins, Andrew Morton, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
On Jun 28 2005, Ben Collins wrote:
> Unless something is in git that isn't in subversion, nothing has real
ly
> changed in the sbp2 module for 5-6 months.

Is there any other information that I can provide you with that would h
elp
track this?

> Doesn't appear to be a problem with the ieee1394 subsystem itself (th
e
> cycle master thing isn't all that important), since that would cause
not
> even being able to send/recv packets.

So, could this be a problem with the SCSI layer, then?


Thank you, Rogério.

--
Rogério Brito : rbr...@ime.usp.br : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat: http://freshmeat.net/projects/algorithms/

Ingo Molnar

unread,
Jun 28, 2005, 3:42:15 AM6/28/05
to Andrew Morton, reube...@reub.net, linux-...@vger.kernel.org

* Andrew Morton <ak...@osdl.org> wrote:

> Ingo Molnar <mi...@elte.hu> wrote:
> >
> > is the fput()/sysfs_release() crash below known?
>
> It doesn't ring any bells.
>
> You have a use-after-free error when udev is dinking with a sysfs
> file. It could be anything. Could you debug it a bit, please, work
> out which file caused the crash?

unfortunately it's totally unreproducible, it triggered only once during
hundreds of bootups. Will keep eyes open though.

Ingo

Stefan Richter

unread,
Jun 28, 2005, 4:03:07 AM6/28/05
to linux-...@vger.kernel.org, linux13...@lists.sourceforge.net, Andrew Morton, Rogério Brito
Andrew Morton wrote:
> -ieee1394: Node added: ID:BUS[0-00:1023] GUID[0050c501e00010e8]
> +ieee1394: Node added: ID:BUS[0-01:1023] GUID[0050c501e00010e8]
> +ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...

> +ieee1394: Node changed: 0-01:1023 -> 0-00:1023
> ieee1394: Node changed: 0-00:1023 -> 0-01:1023

The IDs are assigned to nodes everytime they are attached to the bus in
a random order. It is a pure hardware thing; I cannot imagine any
influnce of the kernel to this procedure.

If the node with the highest ID does not fulfill certain criteria, Linux
tries to get the highest ID moved to the local node. This function is
unrelated to SBP-2 (it is necessary to let streaming devices like
cameras work) but it has been observed that it disturbs a few SBP-2
devices. But again, I don't see how -mm and the stock kernel should
differ to that respect.

You could load ieee1394 with a new parameter that supresses the "Root
node is not cycle master capable..." routine:
# modprobe ieee1394 disable_irm=1
before ohci1394 and the other 1394 related drivers are loaded.

> SCSI subsystem initialized
> sbp2: $Rev: 1219 $ Ben Collins <bcol...@debian.org>
> @@ -300,14 +308,6 @@
> ieee1394: sbp2: Logged into SBP-2 device
> ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
> Vendor: ST316002 Model: 1A Rev: 3.06
> - Type: Direct-Access ANSI SCSI revision: 06
> -SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> -sda: asking for cache data failed
> -sda: assuming drive cache: write through
> -SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> -sda: asking for cache data failed
> -sda: assuming drive cache: write through
> - sda: [mac] sda1 sda2 sda3 sda4
> -Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
> + Type: Unknown ANSI SCSI revision: 04

There was a discussion in May about discovery of devices which implement
the RBC command set: http://marc.theaimsgroup.com/?t=111620896500001 I
am not sure if the discussed change went into one or both of the kernels
in question.

> ieee1394: Node changed: 0-01:1023 -> 0-00:1023
> ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0050c501e00010e8]

What caused these two messages? Did you disconnect the drive at this point?
--
Stefan Richter
-=====-=-=-= -==- ===--
http://arcgraph.de/sr/

RogérioBrito

unread,
Jun 28, 2005, 4:35:50 AM6/28/05
to Stefan Richter, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net, Andrew Morton
On Jun 28 2005, Stefan Richter wrote:
> But again, I don't see how -mm and the stock kernel should differ to
that
> respect.

Well, I can only say that this problem is 100% reproducible with my
enclosure.

Perhaps more data is needed here? The 2.6.12 kernel is able to see the
drive without any problems while the -mm kernels aren't. I can provide
anything that you guys want.

Right now, I am using a stock/vanilla kernel, for using the drive.

> You could load ieee1394 with a new parameter that supresses the "Root

> node is not cycle master capable..." routine:
> # modprobe ieee1394 disable_irm=1
> before ohci1394 and the other 1394 related drivers are loaded.

Ok, I'll disable hotplug, udev etc and try to boot into single user mod
e
for that as soon as I wake up (I'm going to bed right now---had a lot o
f
work done for a day).

> > ieee1394: Node changed: 0-01:1023 -> 0-00:1023
> > ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0050c501e00010e8]
>
> What caused these two messages? Did you disconnect the drive at this
> point?

Yes, I did. In both cases, just to see if any messages issued to dmesg
were
different when unplugging the drive.

If you have other ideas or if any extra information is necessary, pleas
e,
let me know and I'll do my best to provide what you need.


Thank you all for the interest, Rogério.

--
Rogério Brito : rbr...@ime.usp.br : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat: http://freshmeat.net/projects/algorithms/

Ben Collins

unread,
Jun 28, 2005, 12:16:59 PM6/28/05
to Andrew Morton, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
On Tue, Jun 28, 2005 at 03:12:45AM -0300, Rog?rio Brito wrote:
> On Jun 28 2005, Ben Collins wrote:
> > Unless something is in git that isn't in subversion, nothing has really
> > changed in the sbp2 module for 5-6 months.
>
> Is there any other information that I can provide you with that would help
> track this?

Diff git2's ieee1394 directory and the SVN repo from linux1394.org if you
could.

> > Doesn't appear to be a problem with the ieee1394 subsystem itself (the
> > cycle master thing isn't all that important), since that would cause not
> > even being able to send/recv packets.
>
> So, could this be a problem with the SCSI layer, then?

Doubtful.

Stefan Richter

unread,
Jun 28, 2005, 2:50:43 PM6/28/05
to linux-...@vger.kernel.org, linux13...@lists.sourceforge.net, Rogério Brito, Andrew Morton
Rogério Brito wrote:
> On Jun 28 2005, Stefan Richter wrote:
>>But again, I don't see how -mm and the stock kernel should differ to
that
>>respect.
>
> Well, I can only say that this problem is 100% reproducible with my
> enclosure.
>
> Perhaps more data is needed here? The 2.6.12 kernel is able to see th
e
> drive without any problems while the -mm kernels aren't. I can provid
e
> anything that you guys want.

What we know is:
- With -mm, your machine started to require the switching of phy IDs
for a proper cycle master.
- With -mm, the device formerly sensed by scsi_mod's probe as
"Direct-Access" device + SCSI rev 06 is allegedly of "Unknown" type
+
SCSI rev 04 now. Vendor and model are still recognized though.

So what we don't know at the moment is:
- What did change to make the formerly "unlikely to happen" FireWire
bus reset "extremely likely to happen" now? (That is how I interpre
t
the ratio of 0% to 100% which you observed.)
- Does this reset infuence how the device answers to scsi inquiries?
So far there were only reports on the linux1394 mailinglists
indicating that with this reset, devices respond differently to
config ROM queries from the ieee1394 driver. This is way before sbp
2
and scsi_mod get to know about the device.

My current uneducated guess is that the FireWire bus reset and the SCSI

probing problem are actually unrelated. The cause for the latter proble
m
might be 2.6.12-mm2/broken-out/git-scsi-block.patch. At least that is
what I think after a look through the -mm2 patch collection.

>>You could load ieee1394 with a new parameter that supresses the "Root

>>node is not cycle master capable..." routine:
>># modprobe ieee1394 disable_irm=1
>>before ohci1394 and the other 1394 related drivers are loaded.
>
> Ok, I'll disable hotplug, udev etc and try to boot into single user m
ode
> for that as soon as I wake up (I'm going to bed right now---had a lot
of
> work done for a day).

You do not need to go through all this. Unload all 1394 drivers
(although this may fail sometimes when scsi does not let go of sbp2),
then reload ieee1394 with the parameter, then ohci1394. No need to go
into another runlevel or to mess around with hotplug or udev.

>>>ieee1394: Node changed: 0-01:1023 -> 0-00:1023
>>>ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0050c501e00010e8]
>>
>>What caused these two messages? Did you disconnect the drive at this
>>point?
>
> Yes, I did. In both cases, just to see if any messages issued to dmes
g were
> different when unplugging the drive.

Then these two messages are OK.


--
Stefan Richter
-=====-=-=-= -==- ===--
http://arcgraph.de/sr/

William Lee Irwin III

unread,
Jun 28, 2005, 9:29:23 PM6/28/05
to Andrew Morton, linux-...@vger.kernel.org
On Sun, Jun 26, 2005 at 04:03:29AM -0700, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm2/

Something reverted most of the arch/sparc/Kconfig changes, leaving
arch/sparc/ unconfigurable. This patch re-removes the parts made
redundant by drivers/Kconfig in addition to a mysterious, spurious
second instance of source "mm/Kconfig". cvs strikes again?

Signed-off-by: William Irwin <w...@holomorphy.com>


Index: mm2-2.6.12/arch/sparc/Kconfig
===================================================================
--- mm2-2.6.12.orig/arch/sparc/Kconfig 2005-06-28 17:06:54.655102470 -0700
+++ mm2-2.6.12/arch/sparc/Kconfig 2005-06-28 17:16:52.135271678 -0700
@@ -270,66 +270,10 @@

source "drivers/Kconfig"

-config PRINTER
- tristate "Parallel printer support"
- depends on PARPORT
- ---help---
- If you intend to attach a printer to the parallel port of your Linux
- box (as opposed to using a serial printer; if the connector at the
- printer has 9 or 25 holes ["female"], then it's serial), say Y.
- Also read the Printing-HOWTO, available from
- <http://www.tldp.org/docs.html#howto>.
-
- It is possible to share one parallel port among several devices
- (e.g. printer and ZIP drive) and it is safe to compile the
- corresponding drivers into the kernel. If you want to compile this
- driver as a module however, choose M here and read
- <file:Documentation/parport.txt>. The module will be called lp.
-
- If you have several parallel ports, you can specify which ports to
- use with the "lp" kernel command line option. (Try "man bootparam"
- or see the documentation of your boot loader (silo) about how to pass
- options to the kernel at boot time.) The syntax of the "lp" command
- line option can be found in <file:drivers/char/lp.c>.
-
- If you have more than 8 printers, you need to increase the LP_NO
- macro in lp.c and the PARPORT_MAX macro in parport.h.
-
-source "mm/Kconfig"
-
-endmenu
-
-source "drivers/base/Kconfig"
-
-source "drivers/video/Kconfig"
-
-source "drivers/mtd/Kconfig"
-
-source "drivers/serial/Kconfig"
-
if !SUN4
source "drivers/sbus/char/Kconfig"
endif

-source "drivers/block/Kconfig"
-
-# Don't frighten a common SBus user
-if PCI
-
-source "drivers/ide/Kconfig"
-
-endif
-
-source "drivers/isdn/Kconfig"
-
-source "drivers/scsi/Kconfig"
-
-source "drivers/fc4/Kconfig"
-
-source "drivers/md/Kconfig"
-
-source "net/Kconfig"
-
# This one must be before the filesystem configs. -DaveM

menu "Unix98 PTY support"

RogérioBrito

unread,
Jun 29, 2005, 8:45:27 PM6/29/05
to ste...@s5r6.in-berlin.de, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net, ak...@osdl.org, bcol...@debian.org
On Jun 28 2005, Stefan Richter wrote:
> If the node with the highest ID does not fulfill certain criteria, Li
nux
> tries to get the highest ID moved to the local node. This function is

> unrelated to SBP-2 (it is necessary to let streaming devices like
> cameras work) but it has been observed that it disturbs a few SBP-2
> devices. But again, I don't see how -mm and the stock kernel should
> differ to that respect.

Well, my observation is that they differ. Well, up to kernel 2.6.13-rc1
.
This latest kernel shows the same behaviour that -mm showed, unfortunat
ely.

> You could load ieee1394 with a new parameter that supresses the "Root

> node is not cycle master capable..." routine:
> # modprobe ieee1394 disable_irm=1
> before ohci1394 and the other 1394 related drivers are loaded.

Now *this* made things work! I have put another dmesg log on my homepag
e at
http://www.ime.usp.br/~rbrito/bug/ (see the 3rd-try log). This made thi
ngs
work and I could mount the device.

I had to disable hotplug and udev, since trying to unload the Firewire
modules made my machine hang (I think that it was trying to unload ohci
1394
that made my machine hang).

So, does this ring any bell? Can I provide extra information?

I am keeping the following diff just for reference's sake:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-


> SCSI subsystem initialized
> sbp2: $Rev: 1219 $ Ben Collins <bcol...@debian.org>
>@@ -300,14 +308,6 @@
> ieee1394: sbp2: Logged into SBP-2 device
> ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
> Vendor: ST316002 Model: 1A Rev: 3.06
>- Type: Direct-Access ANSI SCSI revision: 06
>-SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
>-sda: asking for cache data failed
>-sda: assuming drive cache: write through
>-SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
>-sda: asking for cache data failed
>-sda: assuming drive cache: write through
>- sda: [mac] sda1 sda2 sda3 sda4
>-Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
>+ Type: Unknown ANSI SCSI revision: 04

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

Thanks for all your kind responses, Rogério Brito.

--
Rogério Brito : rbr...@ime.usp.br : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat: http://freshmeat.net/projects/algorithms/

RogérioBrito

unread,
Jun 30, 2005, 9:04:35 PM6/30/05
to Ben Collins, Andrew Morton, Stefan Richter, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
On Jun 28 2005, Ben Collins wrote:
> On Tue, Jun 28, 2005 at 03:12:45AM -0300, Rog?rio Brito wrote:
> > Is there any other information that I can provide you with that wou
ld help
> > track this?
>
> Diff git2's ieee1394 directory and the SVN repo from linux1394.org if
you
> could.

Ok, I see that this is getting to be really important now, because I th
ink
that Andrew forwarded some patches to Linus and now the Firewire enclos
ure
doesn't seem to work with 2.6.13-rc1 anymore (it works perfectly with
vanilla kernel 2.6.12).

The behaviour that I get with 2.6.13-rc1 is the same one that I got wit
h
2.6.12-mm1 or 2.6.12-mm2. :-(

Oh, BTW, I just checked this with another drive, an iPod (2nd Generatio
n)
and its partition table is also not read (like what happens with the dr
ive
in the Firewire enclosure).

So, I guess that this is another data point that may be useful.


Thank you very much for your help, Rogério.

--
Rogério Brito : rbr...@ime.usp.br : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat: http://freshmeat.net/projects/algorithms/

Ben Collins

unread,
Jun 30, 2005, 10:00:52 PM6/30/05
to rbr...@ime.usp.br, Andrew Morton, Stefan Richter, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
On Thu, Jun 30, 2005 at 10:01:57PM -0300, Rog?rio Brito wrote:
> On Jun 28 2005, Ben Collins wrote:
> > On Tue, Jun 28, 2005 at 03:12:45AM -0300, Rog?rio Brito wrote:
> > > Is there any other information that I can provide you with that would help

> > > track this?
> >
> > Diff git2's ieee1394 directory and the SVN repo from linux1394.org if you
> > could.

Where are these patches coming from? Also, have you tried using 2.6.13-rc1
using linux1394.org's subversion tree?

> Ok, I see that this is getting to be really important now, because I think
> that Andrew forwarded some patches to Linus and now the Firewire enclosure
> doesn't seem to work with 2.6.13-rc1 anymore (it works perfectly with
> vanilla kernel 2.6.12).
>
> The behaviour that I get with 2.6.13-rc1 is the same one that I got with
> 2.6.12-mm1 or 2.6.12-mm2. :-(
>
> Oh, BTW, I just checked this with another drive, an iPod (2nd Generation)
> and its partition table is also not read (like what happens with the drive
> in the Firewire enclosure).
>
> So, I guess that this is another data point that may be useful.
>
>

> Thank you very much for your help, Rog?rio.
>
> --
> Rog?rio Brito : rbr...@ime.usp.br : http://www.ime.usp.br/~rbrito


> Homepage of the algorithms package : http://algorithms.berlios.de
> Homepage on freshmeat: http://freshmeat.net/projects/algorithms/

--

RogérioBrito

unread,
Jun 30, 2005, 10:25:31 PM6/30/05
to Ben Collins, Andrew Morton, Stefan Richter, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
On Jun 30 2005, Ben Collins wrote:
> On Thu, Jun 30, 2005 at 10:01:57PM -0300, Rog?rio Brito wrote:
> > On Jun 28 2005, Ben Collins wrote:
> > > On Tue, Jun 28, 2005 at 03:12:45AM -0300, Rog?rio Brito wrote:
> > > > Is there any other information that I can provide you with that
would help
> > > > track this?
> > >
> > > Diff git2's ieee1394 directory and the SVN repo from linux1394.or
g if you
> > > could.
>
> Where are these patches coming from? Also, have you tried using 2.6.1
3-rc1
> using linux1394.org's subversion tree?

I don't know where the patches are coming from. I have just checked out
the
trunk version of the subversion tree from linux1394.org. I will diff it
against the Linux tree that I have here.

Humm, I have just diffed both trees and there is a fair amount of chang
es
between both versions (i.e., between Linux 2.6.13-rc1 and the trunk tre
e
from linux1394.org).

The diff (in this order) is at http://www.ime.usp.br/~rbrito/bug/, if y
ou
can comment on it.

I can provide any other information that is needed. Just let me know wh
at
is desired.


Thank you very much, Rogério.

--
Rogério Brito : rbr...@ime.usp.br : http://www.ime.usp.br/~rbrito


Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat: http://freshmeat.net/projects/algorithms/

RogérioBrito

unread,
Jun 30, 2005, 10:33:59 PM6/30/05
to Ben Collins, Andrew Morton, Stefan Richter, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
On Jun 30 2005, Ben Collins wrote:
> Also, have you tried using 2.6.13-rc1 using linux1394.org's subversio
n tree?

I am doing this right now. I will let you know the resuts as soon as I
get
the kernel compiled.


Thanks, Rogério.

--
Rogério Brito : rbr...@ime.usp.br : http://www.ime.usp.br/~rbrito


Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat: http://freshmeat.net/projects/algorithms/

RogérioBrito

unread,
Jun 30, 2005, 10:52:37 PM6/30/05
to Ben Collins, Andrew Morton, Stefan Richter, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
On Jun 30 2005, Ben Collins wrote:
> Also, have you tried using 2.6.13-rc1 using linux1394.org's subversio
n tree?

Here is what I get when I try to substitute 2.6.13-rc1 with linux1394
trunk's tree:


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- -
(...)
CC [M] drivers/block/loop.o
CC [M] drivers/block/pktcdvd.o
CC [M] drivers/block/cryptoloop.o
CC [M] drivers/char/agp/intel-agp.o
CC [M] drivers/ieee1394/ieee1394_core.o
drivers/ieee1394/ieee1394_core.c: In function `hpsbpkt_thread':
drivers/ieee1394/ieee1394_core.c:1048: error: too many arguments to fun
ction `refrigerator'
drivers/ieee1394/ieee1394_core.c: In function `ieee1394_init':
drivers/ieee1394/ieee1394_core.c:1127: warning: implicit declaration of
function `class_simple_create'
drivers/ieee1394/ieee1394_core.c:1127: warning: assignment makes pointe
r from integer without a cast
drivers/ieee1394/ieee1394_core.c:1165: warning: implicit declaration of
function `class_simple_destroy'
make[3]: *** [drivers/ieee1394/ieee1394_core.o] Error 1
make[2]: *** [drivers/ieee1394] Error 2
make[1]: *** [drivers] Error 2
make[1]: Leaving directory `/usr/local/media/progs/linux/linux'
make: *** [stamp-build] Error 2


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- -

Thanks, Rogério Brito.

--
Rogério Brito : rbr...@ime.usp.br : http://www.ime.usp.br/~rbrito


Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat: http://freshmeat.net/projects/algorithms/

Ben Collins

unread,
Jun 30, 2005, 11:19:58 PM6/30/05
to rbr...@ime.usp.br, Andrew Morton, Stefan Richter, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
Most of this is class_simple changes.

However, there is a huge set of changes to sbp2. One thing that sticks out
is the entire sbp2_check_sbp2_command() function being ripped out. There's
some changes related to TYPE_SDAD devices (where did this come from?).

Try reverting just the sbp2.[ch] changes from the 2.6.13-rc1 tree.

I'll see if I can figure out why our tree and kernel tree have gotten so
far out of whack and how such huge changes that don't seem to fix anything
(like the large changes to sbp2) have gotten into the kernel proper
without being tested. Most of the sbp2 changes seem to be a new feature
rather than fixing minor or even major bugs.

On Thu, Jun 30, 2005 at 11:44:33PM -0300, Rog?rio Brito wrote:
> On Jun 30 2005, Ben Collins wrote:

> > Also, have you tried using 2.6.13-rc1 using linux1394.org's subversion tree?


>
> Here is what I get when I try to substitute 2.6.13-rc1 with linux1394
> trunk's tree:
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> (...)
> CC [M] drivers/block/loop.o
> CC [M] drivers/block/pktcdvd.o
> CC [M] drivers/block/cryptoloop.o
> CC [M] drivers/char/agp/intel-agp.o
> CC [M] drivers/ieee1394/ieee1394_core.o
> drivers/ieee1394/ieee1394_core.c: In function `hpsbpkt_thread':

> drivers/ieee1394/ieee1394_core.c:1048: error: too many arguments to function `refrigerator'


> drivers/ieee1394/ieee1394_core.c: In function `ieee1394_init':
> drivers/ieee1394/ieee1394_core.c:1127: warning: implicit declaration of function `class_simple_create'

> drivers/ieee1394/ieee1394_core.c:1127: warning: assignment makes pointer from integer without a cast


> drivers/ieee1394/ieee1394_core.c:1165: warning: implicit declaration of function `class_simple_destroy'
> make[3]: *** [drivers/ieee1394/ieee1394_core.o] Error 1
> make[2]: *** [drivers/ieee1394] Error 2
> make[1]: *** [drivers] Error 2
> make[1]: Leaving directory `/usr/local/media/progs/linux/linux'
> make: *** [stamp-build] Error 2
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>

> Thanks, Rog?rio Brito.
>
> --
> Rog?rio Brito : rbr...@ime.usp.br : http://www.ime.usp.br/~rbrito


> Homepage of the algorithms package : http://algorithms.berlios.de
> Homepage on freshmeat: http://freshmeat.net/projects/algorithms/

--

Dan Dennedy

unread,
Jul 1, 2005, 12:14:32 AM7/1/05
to Ben Collins, rbr...@ime.usp.br, Andrew Morton, Stefan Richter, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
On Thu, 2005-06-30 at 23:18 -0400, Ben Collins wrote:
> Most of this is class_simple changes.
>
> However, there is a huge set of changes to sbp2. One thing that sticks out
> is the entire sbp2_check_sbp2_command() function being ripped out. There's
> some changes related to TYPE_SDAD devices (where did this come from?).

This is the TYPE_RBC cache fixes patch by Al Viro. That discussion went
on for a while with additional changes suggested, and I did not know the
resolution. Now we do. :-)

> Try reverting just the sbp2.[ch] changes from the 2.6.13-rc1 tree.
>
> I'll see if I can figure out why our tree and kernel tree have gotten so
> far out of whack and how such huge changes that don't seem to fix anything

Obviously, much of the diff Rogerio produced (not in history below)
shows changes in our repo not yet submitted to kernel.

-

Stefan Richter

unread,
Jul 1, 2005, 12:20:36 AM7/1/05
to linux-...@vger.kernel.org, linux13...@lists.sourceforge.net, Ben Collins, rbr...@ime.usp.br, Andrew Morton
Ben Collins wrote:
> However, there is a huge set of changes to sbp2. One thing that sticks out
> is the entire sbp2_check_sbp2_command() function being ripped out. There's
> some changes related to TYPE_SDAD devices (where did this come from?).

The TYPE_SDAD -> TYPE_RBC changes come from the scsi maintainers. Here
is the related discussion from May: 'TYPE_RBC cache fixes (sbp2.c
affected)', http://marc.theaimsgroup.com/?t=111620896500001

(Back then I wanted to test their patch but did not find the time.)
--
Stefan Richter
-=====-=-=-= -=== ----=
http://arcgraph.de/sr/

RogérioBrito

unread,
Jul 1, 2005, 12:32:10 AM7/1/05
to Ben Collins, Andrew Morton, Stefan Richter, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
On Jun 30 2005, Ben Collins wrote:
> Try reverting just the sbp2.[ch] changes from the 2.6.13-rc1 tree.

Ok, I did that and it worked fine, thanks! I'm trying to upload the
resulting dmesg so that you can see yourself, but it seems that my
University's site isn't working for some reason. :-(

Oh, I got one warning when I was compiling sbp2.c (it was something lik
e an
invalid initialization around line 27xx--yes, yes, I know that this doe
sn't
help much, but I don't have the log of the compilation here).

> I'll see if I can figure out why our tree and kernel tree have gotten
so
> far out of whack and how such huge changes that don't seem to fix
> anything (like the large changes to sbp2) have gotten into the kernel
> proper without being tested. Most of the sbp2 changes seem to be a ne
w
> feature rather than fixing minor or even major bugs.

Yes, it would help a lot if the fixes were included in 2.6.13 (final).


Thank you very much again, Rogério Brito.
--
Rogério Brito : rbr...@ime.usp.br : http://www.ime.usp.br/~rbrito


Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat: http://freshmeat.net/projects/algorithms/

Stefan Richter

unread,
Jul 1, 2005, 12:50:40 AM7/1/05
to linux-...@vger.kernel.org, linux13...@lists.sourceforge.net, Dan Dennedy, Ben Collins, rbr...@ime.usp.br, Andrew Morton
Dan Dennedy wrote:
> Obviously, much of the diff Rogerio produced
> shows changes in our repo not yet submitted to kernel.

It is actually a mixture of that and of 'external' changes which were
not yet merged back into the Linux1394 repo.


--
Stefan Richter
-=====-=-=-= -=== ----=
http://arcgraph.de/sr/

Ben Collins

unread,
Jul 1, 2005, 1:17:34 AM7/1/05
to Andrew Morton, Stefan Richter, linux-...@vger.kernel.org, linux13...@lists.sourceforge.net
On Fri, Jul 01, 2005 at 01:30:39AM -0300, Rog?rio Brito wrote:
> On Jun 30 2005, Ben Collins wrote:
> > Try reverting just the sbp2.[ch] changes from the 2.6.13-rc1 tree.
>
> Ok, I did that and it worked fine, thanks! I'm trying to upload the
> resulting dmesg so that you can see yourself, but it seems that my
> University's site isn't working for some reason. :-(
>
> Oh, I got one warning when I was compiling sbp2.c (it was something like an
> invalid initialization around line 27xx--yes, yes, I know that this doesn't

> help much, but I don't have the log of the compilation here).

Ok, so the TYPE_SDAD/TYPE_RBC changes did affect sbp2. I think the changes
look a little much for what it was trying to accomplish (moving code
around between functions and changing logic paths is a little much when no
one tests it).

0 new messages