2.6.15-mm3

2.6.15-mm3

[Andrew Morton]

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/

- New config options (VMSPLIT_*) to permit non-standard user/kernel
  splitting on x86.  Needs testing please.

- Lots of updates to the USB, PCI, driver and I2C trees.  This is usually a
  worry.

- Multiblock allocation speedup for ext3.  This is only used by direct-IO at
  present.

- Reminder: -mm kernel commit activity can be reviewed by subscribing to the
  mm-commits mailing list.

  echo "subscribe mm-commits" | mail marordomo@vger.kernel.org

- If you hit a bug in -mm and it's not obvious which patch caused it, it is
  most valuable if you can perform a bisection search to identify which patch
  introduced the bug.  Instructions for this process are at

	http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt

  But beware that this process takes some time (around ten rebuilds and
  reboots), so consider reporting the bug first and if we cannot immediately
  identify the faulty patch, then perform the bisection search.



Changes since 2.6.15-mm2:

 linus.patch
 git-acpi.patch
 git-agpgart.patch
 git-audit.patch
 git-blktrace.patch
 git-blkdev-fixup.patch
 git-cfq.patch
 git-cifs.patch
 git-drm.patch
 git-infiniband.patch
 git-netdev-all.patch
 git-ntfs.patch
 git-ocfs2.patch
 git-sym2.patch
 git-pcmcia.patch
 git-scsi-misc-fixup.patch
 git-sas-jg.patch
 git-watchdog.patch
 git-xfs.patch

-revert-mm-page_state-fixes.patch
-asm-generic-atomich-needs-typesh.patch
-small-hp_sdc_rtc-cleanup-use-no_llseek.patch
-md-support-check-without-repair-of-raid10-arrays.patch
-git-acpi-memhotplug-build-fix.patch
-git-acpi-warning-fix.patch
-acpi-disable-c2-c3-for-_all_-ibm-r40e-laptops-for-2613-bug-3549.patch
-acpi-kernel-doc-fixes-for-scanc.patch
-pnpacpi-only-parse-device-that-have-crs-method.patch
-pnpacpi-clean-blacklist.patch
-acpi-remove-kconfig-acpi-laptop-default-settings.patch
-pnpacpi-handle-address-descriptors-in-_prs-2.patch
-fix-sys-class-net-if-wireless-without-dev-get_wireless_stats.patch
-fix-sys-class-net-if-wireless-without-dev-get_wireless_stats-fix.patch
-gregkh-pci-x86-pci-domain-support-the-meat.patch
-gregkh-pci-pci-store-pci_interrupt_pin-in-pci_dev.patch
-gregkh-pci-apci-use-pin-stored-in-pci_dev.patch
-gregkh-pci-pci-use-pin-stored-in-pci_dev.patch
-gregkh-pci-pci-call-pci_read_irq-for-bridges.patch
-gregkh-pci-pci-pci_find_device-remove-sys_sio.patch
-gregkh-pci-pci-pci_find_device-remove-sys_alcor.patch
-gregkh-pci-pci-pci_find_device-remove-pci-ppc.patch
-gregkh-pci-pci-pci_find_device-remove-pci-mpc85xx_cds_common.patch
-gregkh-pci-pci-pci_find_device-remove-pci-frv.patch
-gregkh-pci-pci-pci_find_device-remove-pci-ebus.patch
-gregkh-pci-pci-arch-pci_find_device-remove-frv.patch
-gregkh-pci-pci-arch-i386-pci-acpi.c-use-for_each_pci_dev.patch
-gregkh-pci-pcie-make-bus_id-for-pci-express-devices-unique.patch
-gregkh-pci-pci-hotplug-ibmphp_pci.c-copy-n-paste-fix.patch
-gregkh-pci-pci-hotplug-cpqphp_ctrl.c-remove-dead-code.patch
-gregkh-pci-shpchp-replace-pci_find_slot-with-pci_get_slot.patch
-gregkh-pci-shpchp-fix-improper-reference-to-slot-avail-regsister.patch
-gregkh-pci-shpchp-fix-improper-reference-to-mode-1-ecc-capability-bit.patch
-gregkh-pci-shpchp-fix-improper-mmio-mapping.patch
-gregkh-pci-shpchp-fix-improper-write-to-command-completion-detect-bit.patch
-gregkh-pci-shpchp-fix-improper-wait-for-command-completion.patch
-gregkh-pci-pci-irq.c-trivial-printk-and-dbg-updates.patch
-gregkh-pci-pci-error-recovery-documentation.patch
-gregkh-pci-pci-hotplug-powerpc-remove-duplicated-code.patch
-gregkh-pci-pci-hotplug-powerpc-more-removal-of-duplicated-code.patch
-gregkh-pci-arch-replace-pci_module_init-with-pci_register_driver.patch
-gregkh-pci-drivers-block-replace-pci_module_init-with-pci_register_driver.patch
-gregkh-pci-drivers-rest-replace-pci_module_init-with-pci_register_driver.patch
-gregkh-pci-drivers-sound-oss-replace-pci_module_init-with-pci_register_driver.patch
-gregkh-pci-shpchp-implement-get_address-callback.patch
-gregkh-pci-pci-quirk-1k-i-o-space-granularity-on-intel-p64h2.patch
-gregkh-pci-pciehp-handle-sticky-power-fault-status.patch
-gregkh-pci-pciehp-allow-bridged-card-hotplug.patch
-gregkh-pci-pci-use-bus-numbers-sparsely-if-necessary.patch
-gregkh-pci-pci-document-sysfs-rom-file-interface.patch
-gregkh-pci-reduce-nr-of-ptr-derefs-in-drivers-pci-hotplug-cpqphp_core.c.patch
-gregkh-pci-reduce-nr-of-ptr-derefs-in-drivers-pci-hotplug-rpaphp_pci.c.patch
-gregkh-pci-reduce-nr-of-ptr-derefs-in-drivers-pci-hotplug-pciehprm_acpi.c.patch
-gregkh-pci-reduce-nr-of-ptr-derefs-in-drivers-pci-hotplug-pciehp_core.c.patch
-gregkh-pci-cpqphp-sysfs-fixup.patch
-gregkh-pci-acpiphp-only-size-new-bus.patch
-gregkh-pci-pci-drivers-pci-some-cleanups.patch
-gregkh-pci-pci-update-toshiba-ohci-quirk-dmi-table.patch
-pci-restore-2-missing-pci-ids.patch
-au1xx0-replace-casual-readl-with-au_readl-in-the-drivers.patch
-arm-netwinder-watchdog-wdt977-update.patch
-i386-io_apic-use-correct-index-variable-when-computing-the.patch
-x86_64-cpufreq-constant-tsc-fix.patch
-inclusion-of-scalemp-vsmp-architecture-patches-vsmp_arch.patch
-inclusion-of-scalemp-vsmp-architecture-patches-vsmp_align.patch
-fix-compilation-with-config_memory_hotplug=y-and-gcc41.patch
-slab-remove-unused-align-parameter-from-alloc_percpu.patch
-slab-extract-slabinfo-header-printing-to-separate-function.patch
-slab-extract-slab-order-calculation-to-separate-function.patch
-slab-fix-code-formatting.patch
-slab-remove-nested-ifdef-config_numa.patch
-drop-pagecache.patch
-make-high-and-batch-sizes-of-per_cpu_pagelists-configurable.patch
-make-high-and-batch-sizes-of-per_cpu_pagelists-configurable-fix.patch
-make-high-and-batch-sizes-of-per_cpu_pagelists-configurable-fix-fix.patch
-mm-cleanup-zone_pcp.patch
-mm-free_pages-opt.patch
-add-schedule_on_each_cpu.patch
-swap-migration-v5-lru-operations.patch
-swap-migration-v5-pf_swapwrite-to-allow-writing-to-swap.patch
-swap-migration-v5-migrate_pages-function.patch
-swap-migration-add-config_migration-for-page-migration-support.patch
-swap-migration-v5-mpol_mf_move-interface.patch
-swap-migration-v5-sys_migrate_pages-interface.patch
-swap-migration-v5-sys_migrate_pages-interface-x86_64-fix.patch
-swapmig-config_migration-fixes.patch
-swapmig-add_to_swap-avoid-atomic-allocations.patch
-swapmig-drop-unused-pages-immediately.patch
-swapmig-extend-parameters-for-migrate_pages.patch
-swapmig-switch-error-handling-in-migrate_pages-to-use-exx.patch
-cpusets-swap-migration-interface.patch
-mm-make-hugepages-obey-cpusets.patch
-set_page_count-macro-safety.patch
-mm-clean-up-local-variables.patch
-rmap-additional-diagnostics-in-page_remove_rmap.patch
-mempolicies-private-pointer-in-check_range-and-mpol_mf_invert.patch
-fold-numa_maps-into-memopoliciesc.patch
-drop-page-table-lock-before-calling-migrate_page_add.patch
-mempolicies-unexport-get_vma_policy.patch
-move-page-migration-related-functions-near-do_migrate_pages.patch
-oom-kill-of-current-task.patch
-add-mips-dependency-for-dm9000-driver.patch
-drivers-net-arcnet-possible-cleanups.patch
-drivers-net-kconfig-indentation-fix.patch
-drivers-net-bonding-bondingh-extern-inline-static-inline.patch
-drivers-net-gianfarh-extern-inline-static-inline.patch
-e1000-fix-invalid-memory-reference.patch
-remove-bouncing-mail-address-of-mv643xx_eth-maintainer.patch
-forcedeth-tso-fix-for-large-buffers.patch
-cs89x0-make-readwriteword-take-base_addr.patch
-cs89x0-convert-inwoutw-calls-to-readwriteword.patch
-cs89x0-swap-readwritereg-and-readwriteword.patch
-cs89x0-make-readwritereg-use-readwriteword.patch
-cs89x0-cleanly-implement-ixdp2x01-and-pnx0501-support.patch
-cs89x0-switch-inoutsw-to-readwritewords.patch
-fix-kconfig-depends-for-cs89x0-pnx010x-support.patch
-cs89x0-fix-up-after-pnx0105-kconfig-symbol-renaming.patch
-fix-a-few-warning-cleanup_card-defined-but-not-used.patch
-xfrm-sparse-warning-fix.patch
-frv-suppress-configuration-of-certain-features-for-frv.patch
-frv-drop-8-16-bit-xchg-and-cmpxchg.patch
-frv-drop-unsupported-debugging-features.patch
-frv-implement-and-export-various-things-required-by-modules.patch
-frv-support-module-exception-tables.patch
-frv-supply-various-missing-i-o-access-primitives.patch
-frv-add-module-support-stubs.patch
-frv-add-pci_iomap.patch
-frv-fix-pcmcia-configuration.patch
-frv-force-serial-driver-inclusion.patch
-frv-make-get_user-macro-cast-pointers.patch
-frv-miscellaneous-changes.patch
-frv-fix-uninitialised-variable-in-atm-nicstar-driver.patch
-frv-fix-uninitialised-variable-in-serverworks-driver.patch
-i386-gpio-driver-for-amd-cs5535-cs5536.patch
-change-maxaligned_in_smp-alignemnt-macros-to-internodealigned_in_smp-macros.patch
-kill-l1_cache_shift_max.patch
-kill-l1_cache_shift_max-fix.patch
-kill-l1_cache_shift_max-fix-fix.patch
-x86_64-ioapic-virtual-wire-mode-fix.patch
-arm-netwinder-ds1620-driver-needs-an-export-to-be-built.patch
-uml-move-libc-dependent-code-from-signal_userc.patch
-uml-move-libc-dependent-code-from-trap_userc.patch
-uml-merge-trap_userc-and-trap_kernc.patch
-consolidate-asm-futexh.patch
-uml-whitespace-cleanup.patch
-uml-prevent-mode_skas=n-and-mode_tt=n.patch
-make-rcu-task_struct-safe-for-oprofile.patch
-rcu-signal-handling.patch
-rcu-signal-handling-tidies.patch
-rcu-signal-handling-fixes.patch
-rcu-signal-handling-fix-in-attach_pid.patch
-simpler-signal-exit-concurrency-handling.patch
-remove-get_task_struct_rcu.patch
-fix-sigstop-locking-issue.patch
-additional-catchup-rcu-signal-fixes-for-mm.patch
-additional-catchup-rcu-signal-fixes-for-mm-warning-fix.patch
-radix-tree-code-consolidation.patch
-radix_tree-early-termination-of-tag-clearing.patch
-radix-tree-reduce-tree-height-upon-partial-truncation.patch
-debug_slab-depends-on-slab.patch
-slob-introduce-mm-utilc-for-shared-functions.patch
-slob-introduce-the-slob-allocator.patch
-slob-introduce-the-slob-allocator-fixes.patch
-slob-introduce-the-slob-allocator-64-bit-fixes.patch
-cpuset-better-bitmap-remap-defaults.patch
-cpuset-mempolicy-one-more-nodemask-conversion.patch
-cpuset-memory-pressure-meter.patch
-cpuset-memory-pressure-meter-gcc-295-fix.patch
-cpuset-document-additional-features.patch
-cpuset-remove-marker_pid-documentation.patch
-cpuset-minor-spacing-initializer-fixes.patch
-cpuset-update_nodemask-code-reformat.patch
-cpuset-fork-hook-fix.patch
-cpuset-combine-refresh_mems-and-update_mems.patch
-cpuset-implement-cpuset_mems_allowed.patch
-cpuset-numa_policy_rebind-cleanup.patch
-cpuset-number_of_cpusets-optimization.patch
-cpuset-rebind-vma-mempolicies-fix.patch
-cpuset-rebind-vma-mempolicies-fix-fix.patch
-cpuset-rebind-vma-mempolicies-fix-tweaks.patch
-cpuset-migrate-all-tasks-in-cpuset-at-once.patch
-cpuset-remove-test-for-null-cpuset-from-alloc-code-path.patch
-cpuset-use-rcu-directly-optimization.patch
-cpuset-mark-number_of_cpusets-read_mostly.patch
-cpuset-skip-rcu-check-if-task-is-in-root-cpuset.patch
-fix-missing-includes-for-2614-git11.patch
-fix-missing-includes-for-2615-rc1.patch
-new-driver-synclink_gt.patch
-new-char-driver-synclink_gt-2.patch
-new-char-driver-synclink_gt-fix.patch
-irq-type-flags.patch
-irq-type-flags-arm-fix.patch
-irq-type-flags-use-new-flags.patch
-fat-move-fat_clusters_flush-to-write_super.patch
-fat-use-sb_find_get_block-instead-of-sb_getblk.patch
-fat-add-the-read-writepages.patch
-fat-s-export_symbol-export_symbol_gpl.patch
-fat-support-direct_io.patch
-export-change-sync_page_range-_nolock.patch
-fat-support-a-truncate-for-expanding-size-2.patch
-fix-and-add-export_symbolfilemap_write_and_wait.patch
-move-rtc_interrupt-prototype-to-rtch.patch
-drivers-isdn-extern-inline-static-inline.patch
-kernel-small-cleanups.patch
-pktcdvd-use-bd_claim-to-get-exclusive-access.patch
-atomic-dec_and_lock-use-atomic-primitives.patch
-rcu-file-use-atomic-primitives.patch
-rcu-file-use-atomic-primitives-fix.patch
-rcu-file-use-atomic-primitives-tidy.patch
-elf-symbol-table-type-additions.patch
-ipc-expand-shm_flags.patch
-relayfs-decouple-buffer-creation-from-inode-creation.patch
-relayfs-export-relayfs_create_file-with-fileops-param.patch
-relayfs-add-relayfs_remove_file.patch
-relayfs-use-generic_ip-for-private-data.patch
-relayfs-remove-unused-alloc-destroy_inode.patch
-relayfs-add-documention-for-non-relay-files.patch
-relayfs-add-support-for-relay-files-in-other-filesystems.patch
-relayfs-add-documentation-on-relay-files-in-other-filesystems.patch
-relayfs-add-support-for-global-relay-buffers.patch
-relayfs-add-documentation-on-global-relay-buffers.patch
-relayfs-cleanup-change-relayfs_file_-to-relay_file_.patch
-relayfs-documentation-cleanup-remove-obsolete-info.patch
-use-ptrace_get_task_struct-in-various-places-2.patch
-use-ptrace_get_task_struct-in-various-places-2-powerpc-fix.patch
-use-ptrace_get_task_struct-in-various-places-2-x86_64-fix.patch
-use-ptrace_get_task_struct-in-various-places-fix-3.patch
-udf-remove-bogus-inode-==-null-check-in-inode_bmap.patch
-vgacon-fix-doublescan-mode.patch
-vgacon-workaround-for-resize-bug-in-some-chipsets.patch
-permit-multiple-inclusion-of-linux-pagevech.patch
-add-list_for_each_entry_safe_reverse.patch
-fix-some-problems-with-truncate-and-mtime-semantics.patch
-fix-overflow-tests-for-compat_sys_fcntl64-locking.patch
-fix-overflow-tests-for-compat_sys_fcntl64-locking-re-fix.patch
-printk-return-value-fix-it.patch
-kmsg_write-dont-return-printk-return-value.patch
-keys-permit-key-expiry-time-to-be-set.patch
-keys-discard-duplicate-keys-from-a-keyring-on-link.patch
-keys-permit-running-process-to-instantiate-keys.patch
-keys-permit-running-process-to-instantiate-keys-warning-fix.patch
-sigaction-should-clear-all-signals-on-sig_ign-not-just.patch
-sigaction-should-clear-all-signals-on-sig_ign-not-just-fix.patch
-docs-updated-some-code-docs.patch
-add-block_device_operationsgetgeo-block-device-method.patch
-add-block_device_operationsgetgeo-block-device-method-fix.patch
-add-block_device_operationsgetgeo-block-device-method-fix-2.patch
-nbd-remove-duplicate-assignment.patch
-unchecked-alloc_percpu-return-in-__create_workqueue.patch
-fix-possible-page_cache_shift-overflows.patch
-kill_proc_info_as_uid-dont-use-hardcoded-constants.patch
-do_coredump-should-reset-group_stop_count-earlier.patch
-little-do_group_exit-cleanup.patch
-tpm-add-bios-measurement-log.patch
-tpm-add-bios-measurement-log-tidy.patch
-tpm-add-bios-measurement-log-fix.patch
-updated-cpu-hotplug-documentation.patch
-pivot_root-add-comment.patch
-shared-mounts-cleanup.patch
-ext3-external-journal-device-as-a-mount-option.patch
-ext3-external-journal-device-as-a-mount-option-update.patch
-oprofile-use-vmalloc_node-in-alloc_cpu_buffers.patch
-ext3-remove-trailing-newlines-from-ext3_warning-calls.patch
-ext3-use-sbi-instead-of-ext3_sb-in-resize-code.patch
-maintainers-line-duplication.patch
-remove-unneeded-sig-curr_target-recalculation.patch
-sigio-cleanup-dont-take-tasklist-twice.patch
-nfsroot-do-not-silently-stop-parsing-on-an-unknown-option.patch
-shrink-dentry-struct.patch
-shrink-dentry-struct-fix.patch
-shrink-dentry-struct-spufs-fix.patch
-printk-levels-for-spinlock-debug.patch
-printk-levels-for-i386-oops-code.patch
-drivers-connector-cn_procc-typos.patch
-fix-handling-of-elf-segments-with-zero-filesize.patch
-drivers-mfd-header-included-twice.patch
-documentation-small-applying-patchestxt-update.patch
-fs-remove-s_old_blocksize-from-struct-super_block.patch
-remove-unused-blkp-field-in-percpu_data.patch
-add-tainting-for-proprietary-helper-modules.patch
-extend-rcu-torture-module-to-test-tickless-idle-cpu.patch
-extend-rcu-torture-module-to-test-tickless-idle-cpu-fixes.patch
-update-to-the-initramfs-docs.patch
-fadvise-return-espipe-on-fifo-pipe.patch
-dont-attempt-to-power-off-if-power-off-is-not-implemented.patch
-dont-attempt-to-power-off-if-power-off-is-not-implemented-alpha-fix.patch
-dont-attempt-to-power-off-if-power-off-is-not-implemented-m32r-fix.patch
-dont-attempt-to-power-off-if-power-off-is-not-implemented-uml-fix.patch
-tpmdd-remove-global-event-log.patch
-tpmdd-remove-global-event-log-tidy.patch
-cciss-adds-msi-and-msi-x-support.patch
-cciss-adds-msi-and-msi-x-support-fix.patch
-fork-fix-race-in-setting-childs-pgrp-and-tty.patch
-setpgid-should-work-for-sub-threads.patch
-setsid-should-work-for-sub-threads.patch
-setpgid-should-not-accept-ptraced-childs.patch
-block-stattxt.patch
-fix-ipmi-compile-errors-with-proc_fs=n.patch
-fs-udf-ballocc-extern-inline-static-inline.patch
-copy_process-error-path-cleanup.patch
-abandon-gcc-295x.patch
-remove-gcc2-checks.patch
-more-updates-for-the-gcc-=-32-requirement.patch
-dev-mem-__have_phys_mem_access_prot-tidy-up.patch
-dev-mem-validate-mmap-requests.patch
-fs-proc-function-prototypes-belong-into-header-files.patch
-sonypi-convert-to-the-new-platform-device-interface.patch
-sonypi-enable-acpi-events-for-sony-laptop-hotkeys.patch
-modules-prevent-overriding-of-symbols.patch
-modules-mark-taint_forced_rmmod-correctly.patch
-reorder-kiocb-structure-elements-to-make-sync-iocb-setup-faster.patch
-shrink-struct-page.patch
-kernel-modulec-getting-rid-of-the-redundant-spinlock-in-resolve_symbol.patch
-ptrace_sysemu-is-only-for-i386-and-clashes-with-other-ptrace-codes-of-other-archs.patch
-fs-smbfs-procc-fix-data-corruption-in-smb_proc_setattr_unix.patch
-ufs-inode-i_sem-is-not-released-in-error-path.patch
-submittingpatches-diffstat-options.patch
-credits-update-eugene-surovegin.patch
 reduce-size-of-bio-mempools.patch
-split-out-screen_info-from-ttyh.patch
-v9fs-fix-fd_close.patch
-v9fs-new-multiplexer-implementation.patch
-v9fs-new-multiplexer-implementation-tidy.patch
-v9fs-fix-fid-management-in-v9fs_create.patch
-v9fs-zero-copy-implementation.patch
-fix-gcc41-build-failure-on-xconfig.patch
-hw_random-82801ab-pci-bridge-support.patch
-add-a-section-about-inlining-to-documentation-codingstyle.patch
-parport_pc-arm-build-fix.patch
-parport-bring-back-an-unused-phase-for-ppdev-ioctl.patch
-eliminate-__attribute__-packed-warnings-for-gcc-41.patch
-afs-remove-unnecessary-__attribute__-packed.patch
-i4l-__attribute__packed-for-the-capi-message-structs.patch
-make-apm-buildable-without-legacy-pm.patch
-remove-semicolons-from-save_flags.patch
-drivers-block-use-array_size-macro.patch
-fix-workqueue-oops-during-cpu-offline.patch
-kconf-check-for-eof-from-input-stream.patch
-i810_audio-request_irq-fix.patch
-simplify-k_getrusage.patch
-drivers-isdn-add-missing-includes.patch
-drivers-isdn-hardware-eicon-os_4bric-correct-the-xdiloadfile-signature.patch
-dump_thread-cleanup.patch
-cciss-avoid-defining-useless-major_nr-macro.patch
-remove-set_fs-in-stop_machine.patch
-kdump-i386-save-ss-esp-bug-fix.patch
-kdump-dynamic-per-cpu-allocation-of-memory-for-saving-cpu-registers.patch
-kdump-export-per-cpu-crash-notes-pointer-through-sysfs.patch
-kdump-export-crash-notes-sysfs-remove-get-cpu.patch
-kdump-save-registers-early-inline-functions.patch
-kdump-save-registers-early-inline-functions-fix.patch
-kdump-save-registers-early-inline-functions-fix-2.patch
-kdump-x86_64-add-memmmap-command-line-option.patch
-kdump-x86_64-add-elfcorehdr-command-line-option.patch
-kdump-x86_64-add-elfcorehdr-command-line-option-fix.patch
-kdump-x86_64-add-elfcorehdr-command-line-option-fix-2.patch
-kdump-x86_64-kexec-on-panic.patch
-kdump-x86_64-save-cpu-registers-upon-crash.patch
-kdump-read-previous-kernels-memory.patch
-kdump-read-previous-kernels-memory-fix.patch
-kexec-increase-max-segment-limit.patch
-kexec-change-config_physical_start-dependency.patch
-kdump-documentation-update.patch
-simple-spi-framework.patch
-simple-spi-framework-priority-inversion-tweak.patch
-simple-spi-framework-gregkh-hotplug-fix.patch
-ads7846-driver-spi-framework.patch
-ads7846-driver-spi-framework-fix.patch
-mtd-dataflash-driver-spi-framework-2.patch
-mtd-dataflash-driver-spi-framework-2-mtd_dataflash-updates.patch
-spi-add-spi_driver-to-spi-framework.patch
-spi-core-tweaks-bugfix.patch
-spi-ads7836-uses-spi_driver.patch
-spi-add-spi_bitbang-driver.patch
-spi-add-spi_bitbang-driver-bitbanging-becomes-library-code.patch
-m25-series-spi-flash.patch
-m25-series-spi-flash-fix.patch
-tiny-add-bloat-o-meter-to-scripts.patch
-tiny-uninline-some-openc-functions.patch
-tiny-uninline-some-inodec-functions.patch
-tiny-uninline-some-fslocksc-functions.patch
-tiny-trim-non-ipx-builds.patch
-tiny-make-x86-doublefault-handling-optional.patch
-tiny-make-id16-support-optional.patch
-tiny-make-id16-support-optional-fix.patch
-tiny-configure-elf-core-dump-support.patch
-make-vm86-support-optional.patch
-add-vfs_-helpers-for-xattr-operations.patch
-add-vfs_-helpers-for-xattr-operations-fix.patch
-add-vfs_-helpers-for-xattr-operations-fix-2.patch
-move-xattr-permission-checks-into-the-vfs.patch
-remove-jfs-xattr-permission-checks.patch
-remove-ext2-xattr-permission-checks.patch
-remove-ext2-xattr-permission-checks-warning-fixes.patch
-remove-ext3-xattr-permission-checks.patch
-remove-reiserfs-xattr-permission-checks.patch
-remove-xfs-xattr-permission-checks.patch
-remove-xfs-xattr-permission-checks-warning-fixes.patch
-replace-inode_update_time-with-file_update_time.patch
-replace-inode_update_time-with-file_update_time-comments.patch
-replace-inode_update_time-with-file_update_time-switch-ntfs-to-touch_atime.patch
-switch-autofs4-to-touch_atime.patch
-ocfs-update-atime-borkage.patch
-remove-update_atime.patch
-__deprecated_for_modules-the-lookup_hash-prototype.patch
-switch-fs3270-to-compat_ioctl.patch
-remove-tiocgserial-tiocsserial-compat_ioctl-entries-for-390.patch
-compat_ioctl-for-390-tape_char.patch
-common-compat_sys_timer_create.patch
-move-rtc-compat-ioctl-handling-to-fs-compat_ioctlc.patch
-add-compat_ioctl-to-dasd.patch
-add-compat_ioctl-to-dasd-fix.patch
-sanitize-building-of-fs-compat_ioctlc.patch
-ntfs-remove-superflous-ms_noatime-ms_nodiratime-assignments.patch
-9p-remove-superflous-ms_nodiratime-assignment.patch
-per-mount-noatime-and-nodiratime-2.patch
-dont-include-ioctl32h-in-drivers.patch
-generic-ioctlh.patch
-mutex-subsystem-add-atomic_xchg-to-all-arches.patch
-mutex-subsystem-add-typecheck_fntype-function.patch
-mutex-subsystem-add-asm-generic-mutex-h-implementations.patch
-mutex-subsystem-memory-ordering-fixes.patch
-mutex-subsystem-add-include-asm-i386-mutexh.patch
-mutex-subsystem-add-include-asm-x86_64-mutexh.patch
-mutex-subsystem-add-include-asm-arm-mutexh.patch
-mutex-subsystem-add-default-include-asm-mutexh-files.patch
-mutex-subsystem-core.patch
-mutex-subsystem-documentation.patch
-mutex-subsystem-debugging-code.patch
-mutex-subsystem-more-debugging-code.patch
-mutex-subsystem-semaphore-to-mutex-xfs.patch
-mutex-subsystem-semaphore-to-mutex-vfs-i_sem.patch
-mutex-subsystem-semaphore-to-mutex-vfs-i_sem-more.patch
-mutex-subsystem-semaphore-to-mutex-vfs-i_sem-fixes.patch
-mutex-subsystem-semaphore-to-mutex-vfs-i_sem-fixes-2.patch
-mutex-subsystem-semaphore-to-mutex-vfs-i_sem-fixes-3.patch
-mutex-subsystem-semaphore-to-mutex-vfs-sb-s_lock.patch
-mutex-subsystem-semaphore-to-completion-sx8.patch
-mutex-subsystem-semaphore-to-completion-cpu3wdt.patch
-mutex-subsystem-semaphore-to-completion-ide-gendev_rel_sem.patch
-mutex-subsystem-semaphore-to-completion-drivers-block-loopc.patch
-hrtimer-move-div_long_long_rem-out-of-jiffiesh.patch
-hrtimer-move-div_long_long_rem-out-of-jiffiesh-sparc64-fix.patch
-hrtimer-remove-duplicate-div_long_long_rem-implementation.patch
-hrtimer-deinline-mktime-and-set_normalized_timespec.patch
-hrtimer-clean-up-mktime-and-make-arguments-const.patch
-hrtimer-export-deinlined-mktime.patch
-hrtimer-remove-unused-clock-constants.patch
-hrtimer-coding-style-clean-up-of-clock-constants.patch
-hrtimer-coding-style-and-white-space-cleanup.patch
-hrtimer-make-clockid_t-arguments-const.patch
-hrtimer-coding-style-and-white-space-cleanup-2.patch
-hrtimer-create-and-use-timespec_valid-macro.patch
-hrtimer-validate-timespec-of-do_sys_settimeofday.patch
-hrtimer-introduce-nsec_t-type-and-conversion-functions.patch
-hrtimer-introduce-ktime_t-time-format.patch
-hrtimer-hrtimer-core-code.patch
-hrtimer-hrtimer-documentation.patch
-hrtimer-switch-itimers-to-hrtimer.patch
-hrtimer-create-hrtimer-nanosleep-api.patch
-hrtimer-switch-sys_nanosleep-to-hrtimer.patch
-hrtimer-switch-clock_nanosleep-to-hrtimer-nanosleep-api.patch
-hrtimer-convert-posix-timers-completely.patch
-hrtimer-convert-posix-timers-completely-fix.patch
-hrtimer-convert-posix-timers-completely-fix-2.patch
-export-ktime_get_ts.patch
-switch-getnstimestamp-calls-to-ktime_get_ts.patch
-remove-getnstimestamp.patch
-kprobes-enable-funcions-only-for-required-arch.patch
-kprobes-cleanup-include_asm_kprobes_h.patch
-kprobes-changed-from-using-spinlock-to-mutex.patch
-kprobes-changed-from-using-spinlock-to-mutex-fix.patch
-kprobes-cleanup-arch_remove_kprobe.patch
-kprobes-fix-build-break-in-2615-rc5-mm3.patch
-kprobes-conversion-from-kcalloc-to-kzalloc.patch
-v4l-926_2-moves-compat32-functions-from-fs-to-v4l.patch
-v4l-963-explicit-compat_ioctl32-handler-to-em28xx.patch
-v4l-dvb-3120-adds-32-bit-compatibility-for-v4l2.patch
-v4l-0987-added-secam-l-std-on-tda9887-and-common.patch
-v4l-1019-added-basic-support-tv-radio-for.patch
-v4l-1023-added-hauppauge-impactvcb-board.patch
-v4l-0979-added-v4l-support-for-the-nova-s-plus-and.patch
-v4l-0990-enable-ir-support-for-the-nova-s-plus.patch
-v4l-1007-add-support-for-kworld-dvb-s-100.patch
-v4l-0988-tuner-cleanups-by-removing-video-if-from.patch
-v4l-1021-tuner-description-now-follows-the-same.patch
-dvb-2420-makes-integration-of-future-devices-easier.patch
-dvb-2421-fixed-oddities-at-firmware-download.patch
-dvb-2428-fixes-for-the-topuptv-scm-mediaguard-cam.patch
-dvb-2431-fixed-dishnetwork-support-for-nexus-s-rev.patch
-dvb-2432-lnb-power-can-now-be-switched-off-for.patch
-dvb-2440-fixed-mpeg-audio-on-spdif-from-nexus-ca.patch
-dvb-2441-driver-support-for-live-ac3-firmware-=.patch
-dvb-2444-implement-frontend-specific-tuning-and.patch
-dvb-2445-added-demodulator-driver-for-nova-s-plus.patch
-dvb-2446-minor-cleanups.patch
-dvb-2451-add-support-for-kworld-dvb-s-100-based.patch
-dvb-2454-port-code-for-su1278-sh2-tua6100-from.patch
-dvb-2390-adds-a-time-delay-to-ir-remote-button.patch
-v4l-dvb-3062-fix-wrong-tunerh-define-for-tuner-46.patch
-v4l-dvb-3064-some-cleanups-on-msp3400.patch
-v4l-dvb-3065-fix-gcc-402-compile-error-in.patch
-v4l-dvb-3081-added-offset-parameter-for-adjusting.patch
-v4l-dvb-3084-added-a-new-debug-msg-to-help.patch
-v4l-dvb-3086-vfreenull-is-legal.patch
-v4l-dvb-3089-adding-support-for-the-hauppauge.patch
-v4l-dvb-3090-cleanup-check-for-dvb.patch
-v4l-dvb-3092-add-support-for-another-nova-t-pci.patch
-v4l-dvb-3099-fixed-device-controls-for-em28xx-on.patch
-v4l-dvb-3100-fix-compile-error-remove-dead-code.patch
-v4l-dvb-3103-add-vidioc_log_status-to-tuner-corec.patch
-v4l-dvb-3104-msp3400-miscelaneous-fixes.patch
-v4l-dvb-3105-remove-audc_config_pinnacle-horror.patch
-v4l-dvb-3108-tveeprom-cleanup-of-hardcoded-tuner.patch
-v4l-dvb-3112-several-fixes-for-hauppauge-roselyn.patch
-v4l-dvb-3115-add-missing-video_adv_debug-config.patch
-v4l-dvb-3116-tda9887-improvements-better.patch
-v4l-dvb-3117-fix-broken-tv-standard-check.patch
-v4l-dvb-3118-enable-remote-control-on-avertv.patch
-v4l-dvb-3123-include-reorder-to-be-in-sync-with.patch
-v4l-dvb-3123a-remove-uneeded-if-from-v4l-subsystem.patch
-v4l-dvb-3123b-syncs-v4l-subsystem-tree-with-kernel.patch
-v4l-dvb-3129-correct-fe_read_uncorrected_blocks.patch
-v4l-dvb-3130-cx24123-cleanup-timout-handling.patch
-v4l-dvb-3145-syncronizes-some-changes-between-v4l.patch
-dvb-2401-usb-hot-unplug-oops-fix.patch
-v4l-dvb-3154-ttusb-dec-driver-patch-roundup.patch
-v4l-dvb-3159-replaces-max-min-by-kernelh.patch
-v4l-dvb-3160-updates-to-the-tveeprom-eeprom.patch
-v4l-dvb-3161-ir-kbd-gpio-is-now-part-of-bttv.patch
-v4l-dvb-3166-philips-1236d-atsc-ntsc-dual-in.patch
-media-radio-pci-probing-for-maestro-radio.patch
-media-radio-pci-probing-for-maestro-radio-fix.patch
-media-radio-maestro-radio-lindent.patch
-media-radio-maestro-types-change.patch
-media-radio-maestro-avoid-accessing-private-structures-directly.patch
-media-radio-maestro-radio-delete-owner-line-from-video-device.patch
-ingo-nfs-stuff.patch
-mips-namespace-pollution-dump_regs-elf_dump_regs.patch
-vesafb-drop-blank-hook.patch
-aty-remove-unnecessary-config_pci.patch
-fbcon-sanitize-fbcon.patch
-nvidiafb-i2c-bus-name-beautification.patch
-fbcon-store-struct-display-when-setting-all-vcs.patch
-matroxfb-remove-fbconh-from-the-main-header-file.patch
-savagefb-one-more-i2c-enabled-device-in-savagefb.patch
-add-sysfs-entry-to-disable-framebuffer-access.patch
-add-sysfs-entry-to-disable-framebuffer-access-tidy.patch
-fbdev-nvidiafb-driver-cleanup.patch
-fbdev-savagefb-driver-cleanup.patch
-fbdev-i810fb-driver-cleanups.patch
-fbdev-rivafb-driver-cleanups.patch
-fbdev-asiliantfb-driver-cleanups.patch
-fbdev-hgafb-convert-to-platform-device.patch
-fbdev-imsttfb-driver-cleanups.patch
-fbdev-kyrofb-driver-cleanups.patch
-fbdev-neofb-driver-cleanups.patch
-fbdev-pm2fb-driver-cleanups.patch
-fbdev-tdfxfb-driver-cleanups.patch
-fbdev-fbdev-cleanup.patch
-fbdev-atyfb-remove-bios-less-booting.patch
-fbdev-sstfb-driver-cleanups.patch
-rivafb-trim-rivafb_pan_display.patch
-savagefb-trim-savagefb_pan_display.patch
-vesafb-trim-vesafb_pan_display.patch
-vesafb-trim-vesafb_pan_display-fix.patch
-vga16fb-trim-vga16fb_pan_display.patch
-atyfb-fix-spelling.patch
-atyfb-reduce-verbosity.patch
-atyfb-fix-crtc_fifo_lwm-mask.patch
-atyfb-fix-interlaced-modes.patch
-atyfb-dont-stretch-with-crt.patch
-atyfb-set-ecp-divider.patch
-atyfb-improve-blanking.patch
-atyfb-rage-xl-xc-cleanup.patch
-atyfb-vt-gt-cleanup.patch
-atyfb-lt-lg-cleanup.patch
-nvidiafb-add-support-for-some-pci-e-chipsets.patch
-nvidiafb-add-support-for-some-pci-e-chipsets-fix.patch
-skeletonfb-documentation-update.patch
-include-video-newporth-extern-inline-static-inline.patch
-fbcon-disable-ywrap-if-not-supported-by-fbcon-scrolling-code.patch
-fbdev-fixed-and-updated-cyblafb.patch
-fbdev-fixed-and-updated-cyblafb-fix.patch
-cyblafb-remove-unneeded-code.patch
-fbdev-fix-return-code-of-fb_read-and-fb_write.patch
-fbdev-reduce-stack-usage.patch
-nvidiafb-add-boot-option-bpp.patch
-nvidiafb-reduce-stack-usage.patch
-s3c2410fb-cleanup-and-fix.patch
-i810fb-fix-suspend-and-resume-hooks.patch
-fbcon-code-cleanups.patch
-fbdev-replace-kmalloc-with-kzalloc.patch
-fb-typoes-in-kconfig.patch
-fbcon-dont-call-set_par-in-fbcon_init-if-vc_mode==kd_graphics.patch
-fix-console-blanking.patch
-kbuild-call-gcc_version-earlier.patch
-fix-some-f_ops-abuse-in-acpi.patch
-fix-input-layer-f_ops-abuse.patch
-fix-cifs-bugs-wrt-writing-to-f_ops.patch
-codingstyle-correction.patch
-docbook-add-gitignore-file.patch
-add-git-tree-for-docbook.patch
-docbook-fix-kernel-doc-comments.patch
-docbook-warn-for-missing-macro-parameters.patch
-docs-update-typos-corrections-and-additions-to-applying-patchestxt.patch
-docs-update-small-spelling-formating-etc-fixes-for-filesystems-ext3txt.patch
-docs-update-remove-obsolete-patch-from-lockstxt.patch
-docs-update-small-fixes-to-stable_kernel_rulestxt.patch
-drivers-net-irda-irportc-cleanups.patch
-turn-const-static-into-static-const.patch
-drivers-char-use-array_size-macro.patch
-drivers-video-possible-cleanups.patch
-fs-ext2-bitmapc-ext2_count_free-is-only-required-ifdef-ext2fs_debug.patch
-fs-ext3-small-cleanups.patch
-lib-zlib-possible-cleanups.patch
-tty-layer-buffering-revamp-jsm-is-broken.patch
-tty-layer-buffering-revamp.patch
-synclink_gt-conversion-to-new-buffering.patch
-m32r-buildfix-of-m32r_sioc.patch
-tty-layer-buffering-revamp-pmac_zilog-warning-fix.patch
-tty-layer-buffering-revamp-further-tty-bits.patch
-tty-layer-buffering-revamp-uml-fix.patch
-tty-layer-buffering-revamp-ia64-fix.patch
-tty-layer-buffering-revamp-usb-white-heat-fix.patch
-tty-layer-buffering-revamp-s390-fixes.patch
-tty-layer-buffering-revamp-sunsab-build-fix.patch
-moxa-intellio.patch
-tty-layer-buffering-revamp-mkiss-update-re-introduced-defunct-receive_room-function.patch
-clean-up-computone-remaining-cli-use.patch
-tty-layer-buffering-revamp-icom-fixes.patch
-tty-layer-buffering-revamp-isdn-layer.patch
-driver-char-n_hdlcc-remove-unused-declaration.patch
-serial-disable-jsm-in-ppc64-defconfig.patch
-tty-layer-buffering-revamp-stallion-rio-fixes.patch
-tty-layer-buffering-revamp-stallion-rio-fixes-fix.patch
-isicom-whitespace-cleanup.patch
-isicom-type-conversion-and-variables-deletion.patch
-isicom-other-little-changes.patch
-isicom-pci-probing-added.patch
-isicom-pci-probing-added-fix.patch
-isicom-pci-probing-added-fix-vs-gregkh-pci-pci-driver-owner-removal.patch
-isicom-firmware-loading.patch
-isicom-more-whitespaces-and-coding-style.patch
-drivers-replace-pci_module_init-with-pci_register_driver-in-mm.patch
-sound-replace-pci_module_init-with-pci_register_driver-in-mm.patch
-decrease-number-of-pointer-derefs-in-exitc.patch
-decrease-number-of-pointer-derefs-in-flexcop-fe-tunerc.patch
-decrease-number-of-pointer-derefs-in-multipathc.patch
-decrease-number-of-pointer-derefs-in-connectionc.patch
-fs-binfmt_elf-remove-unneeded-kmalloc-return-value-casts.patch
-net-remove-unneeded-kmalloc-return-value-casts.patch
-drivers-atm-remove-unneeded-kmalloc-return-value-casts-tiny-whitespace-cleanup.patch
-selinux-remove-unneeded-kalloc-return-value-casts.patch
-include-asm-sh64-extern-inline-static-inline.patch
-video-matrox-matroxfb_miscc-remove-dead-code.patch
-kill-drivers-net-irda-sir_corec.patch
-kernel-resourcec-__check_region-remove-pointless-__deprecated.patch
-include-linux-schedh-no-need-to-guard-the-normalize_rt_tasks-prototype.patch
-let-magic_sysrq-no-longer-depend-on-debug_kernel.patch
-fs-hfsplus-remove-the-hfsplus_inode_check-debug-function.patch

 Merged

+kdump-emove-remaining-crash_notes-variable-from-arch-powerpc-kernel-machine_kexecc.patch

 powerpc build fix

+sound-remove-bkl-from-sound-core-infoc.patch

 Remove some lock_kernel()s

+git-blktrace-build-fix.patch

 Fix rejects in git-blktrace.patch

+gregkh-driver-input-MODALIAS-02.patch
+gregkh-driver-add-bus_type-probe-remove-shutdown-methods..patch
+gregkh-driver-add-pci_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-ecard_bus_type-probe-remove-shutdown-methods.patch
+gregkh-driver-add-sa1111-bus_type-probe-remove-methods.patch
+gregkh-driver-add-locomo-bus_type-probe-remove-methods.patch
+gregkh-driver-add-logic-module-bus_type-probe-remove-methods.patch
+gregkh-driver-add-tiocx-bus_type-probe-remove-methods.patch
+gregkh-driver-add-parisc_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-ocp_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-sh_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-of_platform_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-vio_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-dio_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-i2c_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-gameport-bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-serio-bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-macio_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-mcp-bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-mmc_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-pcmcia_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-pnp_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-ccwgroup_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-superhyway_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-usb_serial_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-zorro_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-rio_bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-pseudo-lld-bus_type-probe-and-remove-methods.patch
+gregkh-driver-add-ide_bus_type-probe-and-remove-methods.patch
+gregkh-driver-remove-usb-gadget-generic-driver-methods.patch
+gregkh-driver-add-bttv-sub-bus_type-probe-and-remove-methods.patch
+gregkh-driver-platform-device-del-typo-fix.patch
+gregkh-driver-spi-simple-spi-framework.patch
+gregkh-driver-spi-ads7846-driver.patch
+gregkh-driver-spi-mtd-dataflash-driver.patch
+gregkh-driver-spi-add-spi_driver-to-spi-framework.patch
+gregkh-driver-spi-core-tweaks-bugfix.patch
+gregkh-driver-spi-ads7836-uses-spi_driver.patch
+gregkh-driver-spi-add-spi_bitbang-driver.patch
+gregkh-driver-spi-m25-series-spi-flash.patch
+gregkh-driver-spi-use-linked-lists-rather-than-an-array.patch
+gregkh-driver-spi-misc-fixes.patch
+gregkh-driver-aoe-zero-packet-data-after-skb-allocation.patch
+gregkh-driver-aoe-support-dynamic-resizing-of-aoe-devices.patch
+gregkh-driver-aoe-increase-allowed-outstanding-packets.patch
+gregkh-driver-aoe-use-less-confusing-driver-name.patch
+gregkh-driver-aoe-allow-network-interface-migration-on-packet-retransmit.patch
+gregkh-driver-aoe-update-device-information-on-last-close.patch
+gregkh-driver-aoe-update-driver-version-number.patch

 driver tree updates

+gregkh-driver-spi-simple-spi-framework-kconfig-simplification.patch
+spi-add-spi_butterfly-driver.patch
+spi-remove-fastcall-crap.patch
+spi-add-bus-methods-instead-of-drivers-ones.patch
+spi-add-bus-methods-instead-of-drivers-ones-fixes.patch

 Fix it.

+hdaps-convert-to-the-new-platform-device-interface.patch
+vr41xx-convert-to-the-new-platform-device-interface.patch
+mv64x600_wdt-convert-to-the-new-platform-device-interface.patch
+tb0219-convert-to-the-new-platform-device-interface.patch
+serial8250-convert-to-the-new-platform-device-interface.patch
+dcdbas-convert-to-the-new-platform-device-interface.patch

 Driver API updates.

+add-drm-support-for-radeon-x600.patch

 DRM feature work

+gregkh-i2c-i2c-i801-i2c-patch-for-intel-ich8.patch
+gregkh-i2c-i2c-resurrect-i2c_smbus_write_i2c_block_data..patch
+gregkh-i2c-hwmon-lm77-negative-temp-fix.patch
+gregkh-i2c-i2c-sis96x-rename-documentation.patch
+gregkh-i2c-hwmon-w83792d-inline-register-access-functions.patch
+gregkh-i2c-i2c-algo-sibyte-module-param.patch
+gregkh-i2c-i2c-busses-use-array-size-macro.patch
+gregkh-i2c-hwmon-allow-sensor-attr-arrays.patch
+gregkh-i2c-hwmon-pc87360-use-attr-arrays.patch
+gregkh-i2c-hwmon-f71805f-new-driver.patch
+gregkh-i2c-hwmon-f71805f-use-attr-arrays.patch
+gregkh-i2c-hwmon-f71805f-add-documentation.patch
+gregkh-i2c-fix-w1_master_ds9490_bridge-dependencies.patch
+gregkh-i2c-w1-remove-incorrect-module_alias.patch

 i2c tree updates

+pre-udma-eide-pio-mode-selection.patch

 libata fix

+no-longer-mark-mtd_obsolete_chips-as-broken.patch

 MTD

+via-rhine-link-loss-autoneg-off-==-trouble.patch
+corruption-during-e100-mdi-register-access.patch
+corruption-during-e100-mdi-register-access-tidy.patch
+config_airo-needs-config_crypto.patch
+gfar-fix-compile-error.patch
+gianfar-mii-use-proper-resource-for-mii-memory-region.patch
+phy-added-a-macro-to-represent-the-string-format-used-to.patch
+gianfar-use-new-phy_id_fmt-macro.patch

 net driver fixes

+hash-table-corruption-in-bond_albc.patch
+happtmeal-add-pci-probing.patch
+net-fix-prio-qdisc-bands-init.patch
+net-fix-1.patch
+net-fix-2.patch
+net-fix-3.patch
+net-fix-4.patch

 net fixes

+git-pcmcia-ssh-needs-mutexh.patch

 Fix git-pcmcia.patch

-git-powerpc-reexport-handle_mm_fault.patch

 Droped.

+gregkh-pci-pci-schedule-pci_legacy_proc-for-removal.patch
+gregkh-pci-pci-irq-and-pci_ids-patch-for-intel-ich8.patch
+gregkh-pci-pci-drivers-pci-pci.c-if-0-pci_find_ext_capability.patch
+gregkh-pci-pci-make-it-easier-to-see-that-set_msi_affinity-is-used.patch
+gregkh-pci-pci-hotplug-fix-up-coding-style-issues.patch
+gregkh-pci-pci-hotplug-fix-up-kconfig-help-text.patch
+gregkh-pci-pci-restore-2-missing-pci-ids.patch
+gregkh-pci-x86-pci-domain-support-struct-pci_sysdata-fix-fix.patch

 PCI tree updates

+gregkh-pci-x86-pci-domain-support-struct-pci_sysdata-fix.patch

 Fix it.

+aic7xxx-fix-timer-handling.patch
-aic7xxx-crash-on-data-overrun.patch

 New fix for adaptec driver timer handling

+scsi-aha1740c-handle-scsi_add_host-failure.patch
+scsi-arm-ecoscsic-handle-scsi_add_host-failure.patch
+scsi-pcmcia-fdomain_stubc-handle-scsi_add_host-failure.patch
+add-scsi_add_host-failure-handling-for-nsp32.patch

 scsi updates

+gregkh-usb-usb-ub-03-oops-with-cfq.patch
+gregkh-usb-usb-ub-04-loss-of-timer-and-a-hang.patch
+gregkh-usb-usb-ub-05-bulk-reset.patch
+gregkh-usb-usb-new-id-for-ftdi_sio.c-and-ftdi_sio.h.patch
+gregkh-usb-usb-ftdi_sio-new-ids-for-westrex-devices.patch
+gregkh-usb-usb-isp116x-hcd-replace-mdelay-by-msleep.patch
+gregkh-usb-usb-yealink.c-cleanup-device-matching-code.patch
+gregkh-usb-usb-usb-storage-add-support-for-rio-karma.patch
+gregkh-usb-usb-gadgetfs-set-zero-flag-for-short-control-in-response.patch
+gregkh-usb-usb-remove-linux_version_code-check-in-pwc-pwc-ctrl.c.patch
+gregkh-usb-usb-cleanup-of-usblp.patch
+gregkh-usb-usb-fix-oops-in-acm-disconnect.patch
+gregkh-usb-usb-ehci-fix-gfp_t-sparse-warning.patch
+gregkh-usb-usb-usb-storage-support-for-sony-dsc-t5-still-camera.patch
+gregkh-usb-usb-sn9c10x-driver-updates-and-bugfixes.patch
+gregkh-usb-usb-asix-add-device-ids-for-0g0-cable-ethernet.patch
+gregkh-usb-usb-drivers-usb-media-w9968cf.c-remove-hooks-for-the-vpp-module.patch
+gregkh-usb-usb-drivers-usb-media-ov511.c-remove-hooks-for-the-decomp-module.patch
+gregkh-usb-usb-remove-extra-newline-in-hid_init_reports.patch
+gregkh-usb-usb-optimise-devio.c-usbdev_read.patch
+gregkh-usb-usb-mdc800.c-to-kzalloc.patch
+gregkh-usb-usb-kzalloc-for-storage.patch
+gregkh-usb-usb-kzalloc-for-hid.patch
+gregkh-usb-usb-kzalloc-in-dabusb.patch
+gregkh-usb-usb-kzalloc-in-w9968cf.patch
+gregkh-usb-usb-kzalloc-in-usbvideo.patch
+gregkh-usb-usb-kzalloc-in-cytherm.patch
+gregkh-usb-usb-kzalloc-in-idmouse.patch
+gregkh-usb-usb-kzalloc-in-ldusb.patch
+gregkh-usb-usb-kzalloc-in-phidgetinterfacekit.patch
+gregkh-usb-usb-kzalloc-in-phidgetservo.patch
+gregkh-usb-usb-kzalloc-in-usbled.patch
+gregkh-usb-usb-kzalloc-in-sisusbvga.patch
+gregkh-usb-usb-touchkitusb.c-fix.patch
+gregkh-usb-usb-pl2303-added-support-for-ca-42-clone-cable.patch
+gregkh-usb-usb-iomega-umini-is-unusual.patch
+gregkh-usb-usb-au1xx0-replace-casual-readl-with-au_readl-in-the-drivers.patch
+gregkh-usb-usb-uhci-no-fsbr-until-device-is-configured.patch

 USB tree updates

+gregkh-usb-usb-optimise-devio.c-usbdev_read-fix.patch

 Fix it

+x86_64-dma-ops.patch
+x86_64-cpu_pda_local_simple.patch
+x86_64-noiommu-printk.patch
+x86_64-atomic-include.patch
+x86_64-inclusion-of-scalemp-vsmp-architecture-patches---vsmp_align.patch
+x86_64-inclusion-of-scalemp-vsmp-architecture-patches---vsmp_arch.patch
+x86_64-ioapic-virtual-wire-mode-fix.patch
+x86_64-remove-obsolete-segments.patch
+x86_64-out-of-line-numa-funcs.patch
+x86_64-sparse-warning-cleanups-x86_64-code.patch

 x86_64 tree updates

+git-xfs-remove-is_noatime.patch

 Revert temp thing from XFS.

+xfs_iomap-warning-fixes.patch

 xfs warning fixes

+restore-kern_emerg-to-each-line-printed-by-bad_page.patch

 printk facility level fix

+zone-reclaim-resurrect-may_swap.patch
+zone-reclaim-reclaim-logic.patch
+zone-reclaim-reclaim-logic-tidy.patch
+zone-reclaim-reclaim-logic-tweaks.patch
+zone-reclaim-proc-override.patch

 Resurrect and fix zone reclaim logic for NUMA

+mm-gfp_atomic-comments.patch

 Fix some comments

+direct-migration-v9-pageswapcache-checks.patch
+direct-migration-v9-migrate_pages-extension.patch
+direct-migration-v9-migrate_pages-extension-fixes.patch
+direct-migration-v9-remove_from_swap-to-remove-swap-ptes.patch
+direct-migration-v9-remove_from_swap-to-remove-swap-ptes-fixes.patch
+direct-migration-v9-upgrade-mpol_mf_move-and-sys_migrate_pages.patch
+direct-migration-v9-upgrade-mpol_mf_move-and-sys_migrate_pages-fixes.patch
+direct-migration-v9-avoid-writeback--page_migrate-method.patch
+direct-migration-v9-avoid-writeback--page_migrate-method-fixes.patch
+direct-migration-v9-avoid-writeback-page_migrate-method-locking-fix.patch

 Internode page migration without going through swap.

-ethtoolh-dont-leak-kernel-types.patch
-miih-dont-leak-kernel-types.patch

 Dropped.

+i386-let-regparm-no-longer-depend-on-experimental.patch
+i386-put-hotplug_cpu-under-processor-type-not-bus-options.patch
+vmsplit-config-options.patch
+hpet-rtc-emulation-add-watchdog-timer.patch

 x86 updates

+include-asm-h8300-pageh-remove-unused-kthread_size-define.patch

 cleanup

+swsusp-low-level-interface-rev-2.patch
+swsusp-separate-swap-writing-reading-code-rev-2.patch

 swsusp updates

+uml-fix-missing-kbuild_basename.patch
+uml-update-kconfig-help.patch
+uml-revert-compile-time-option-checking.patch
+uml-eliminate-doubled-boot-output.patch
+uml-fix-debug-output-on-x86_64.patch
+uml-kill-an-unused-variable.patch

 UML updates

+device_shutdown-can-loop-if-the-driver-frees-itself.patch

 device management fix

+tell-kallsyms_lookup_name-to-ignore-type-u-entries.patch

 kallsyms fix

+kdump-add-dmesg-gdbmacro-into-document.patch
+doc-refer-to-kdump-in-oops-tracingtxt.patch

 kdump documentation

+ext3-fix-documentation-of-online-resizing.patch

 ext3 documentation

+allow-reading-cmos-day-of-week-register.patch

 RTC feature

+tclk-fix-typos-exclamation-mark-frenzy-and-missing-device-id-on.patch

 telco clock driver fixes

+cs89x0-fix-setting-of-allow_dma.patch
+cs89x0-fix-the-kconfig-help-text.patch

 cs89x0 fixes

+kdump-vmcore-compilation-warning-fix.patch

 Compile fix

+protect-remove_proc_entry.patch

 /proc locking fix

+maintainers-remove-dead-project.patch

 MAINTAINERS cleanup

+piix-ide-pata-patch-for-intel-ich8m.patch
+hda_intel-patch-for-intel-ich8.patch
+ata_piix-ide-mode-sata-patch-for-intel-ich8.patch
+ahci-ahci-mode-sata-patch-for-intel-ich8.patch

 Intel ich8 device support

+random-get-rid-of-sparse-warning.patch

 sparse fix

+synclink_gt-remove-unnecessary-page-alignment.patch

 serial driver cleanup

+fix-assertion-failure-in-reiserfsjournaled-quotas.patch

 reiserfs fix

+kprobes-fix-unloading-of-self-probed-module.patch
+kprobes-fix-race-in-recovery-of-reentrant-probe.patch

 kprobes updates

+remove-unused-out_pio-label-in-i810_audio.patch

 fix warning

+ipmi-use-config_dmi-instead-of-config_x86.patch

 IPMI cleanup

+fix-processing-of-obsolete-style-setup-options.patch

 boot option parsing fix

+ext3-get-blocks-maping-multiple-blocks-at-a-once.patch
+ext3-get-blocks-multiple-block-allocation.patch
+ext3-get-blocks-support-multiple-blocks-allocation-in.patch
+ext3-get-blocks-adjust-accounting-info-in.patch
+ext3-get-blocks-adjust-accounting-info-in-build-fix.patch
+ext3-get-blocks-adjust-reservation-window-size-for.patch
+ext3-get-blocks-maping-multiple-blocks-at-a-once-vs-ext3_readdir-use-generic-readahead.patch

 Multiblock allocation for ext3

+mutex-subsystem-add-include-asm-arm-mutexh-fix-2.patch
+powerpc-fastpaths-for-mutex-subsystem.patch

 Warm up mutexes on arm and powerpc

+mutex-subsystem-synchro-test-module-fix.patch
+mutex-subsystem-synchro-test-module-fix-2.patch

 Mutex test module

+edac-swsusp-fixes.patch
+edac-change-default-also-handle-pulled-hardware.patch

 EDAC driver updates

+v4l-dvb-3120-adds-32-bit-compatibility-for-v4l2-fix.patch

 v4l fix

-scheduler-cache-hot-autodetect-fix.patch
-scheduler-cache-hot-autodetect-less-verbose.patch
-scheduler-cache-hot-autodetect-docs.patch
-scheduler-cache-hot-autodetect-section-fixes.patch
-scheduler-cache-hot-autodetect-section-fixes-2.patch
-scheduler-cache-hot-autodetect-limit-to-affected-cpu-map.patch
-scheduler-cache-hot-autodetect-be-less-verbose.patch

 Folded into scheduler-cache-hot-autodetect.patch

+sched-fix-wrong-priority-calculation.patch

 CPU scheduler fix

+fix-arm26-thread_size.patch

 arm26 fix

-sis5513-support-sis-965l.patch

 Dropped

+ide-disk-restore-missing-space-in-log-message.patch

 IDE fixlet

-md-dm-reduce-stack-usage-with-stacked-block-devices-fixes.patch

 Folded into md-dm-reduce-stack-usage-with-stacked-block-devices.patch

+drivers-md-dm-raid1c-fix-inconsistent-mirroring-after-interrupted.patch

 devicemapper fix

+mark-several-functions-__always_inline-fix.patch

 Fix mark-several-functions-__always_inline.patch

+drivers-acpi-make-two-functions-static.patch

 ACPI cleanup

+make-most-file-operations-structs-in-fs-const.patch

 Move file_operations tables into .rodata

+move-capable-to-capabilityh.patch
+capable-capabilityh-fs.patch
+capable-capabilityh-net.patch
+capable-capabilityh-arch.patch

 capable() cleanup

+make-frame_pointer-default=y.patch

 Default to enabling framepointers - we get better stack traces (-mm only)

+lindent-rio-drivers.patch

 Re-indent the rio drivers



All 737 patches:

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/patch-list

Re: 2.6.15-mm3

[Pekka Enberg]

On 1/11/06, Andrew Morton <akpm@osdl.org> wrote:
> - If you hit a bug in -mm and it's not obvious which patch caused it, it is
>   most valuable if you can perform a bisection search to identify which patch
>   introduced the bug.  Instructions for this process are at
>
>         http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt

You probably meant this one:

http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt

Re: 2.6.15-mm3

[Ashutosh Naik]

On 1/11/06, Andrew Morton <akpm@osdl.org> wrote:

> - Reminder: -mm kernel commit activity can be reviewed by subscribing to the
>   mm-commits mailing list.
>
>   echo "subscribe mm-commits" | mail marordomo@vger.kernel.org
>

You probably meant

echo "subscribe mm-commits" | mail majordomo@vger.kernel.org

Re: 2.6.15-mm3

[Dominik Karall]

On Wednesday, 11. January 2006 13:21, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15
>-mm3/

hi!
it doesn't compile here.

  CC      drivers/media/video/tveeprom.o
  LD      drivers/media/video/built-in.o
drivers/media/video/tuner.o:(.bss+0x0): multiple definition of `debug'
drivers/media/video/msp3400.o:(.bss+0xc): first defined here
make[3]: *** [drivers/media/video/built-in.o] Fehler 1
make[2]: *** [drivers/media/video] Fehler 2
make[1]: *** [drivers/media] Fehler 2
make: *** [drivers] Fehler 2

config file can be downloaded here:
http://stud4.tuwien.ac.at/~e0227135/kernel/config-2.6.15-mm3

greets,
dominik

2.6.15-mm3, current -git: drivers/media/video/ compile errors

[Adrian Bunk]

On Wed, Jan 11, 2006 at 05:21:23PM +0100, Dominik Karall wrote:
> 
> hi!
> it doesn't compile here.
> 
>   CC      drivers/media/video/tveeprom.o
>   LD      drivers/media/video/built-in.o
> drivers/media/video/tuner.o:(.bss+0x0): multiple definition of `debug'
> drivers/media/video/msp3400.o:(.bss+0xc): first defined here
> make[3]: *** [drivers/media/video/built-in.o] Fehler 1
>...

I'm getting even one more error:

<--  snip  -->

...
drivers/media/video/tuner.o:(.bss+0x0): multiple definition of `debug'
drivers/media/video/msp3400.o:(.bss+0xc): first defined here
drivers/media/video/cx25840/built-in.o:(.bss+0x0): multiple definition of `debug'
drivers/media/video/msp3400.o:(.bss+0xc): first defined here
make[3]: *** [drivers/media/video/built-in.o] Error 1

<--  snip  -->

There's sometime a need for variables being global being visible in 
all objects of a module.

That's OK.

But they should never have generic names like "debug" or "once" (the 
latter and some similar ones don't seem to cause compile errors since 
they are currently used only once, but they are equally wrong.

> greets,
> dominik

cu
Adrian

-- 

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

Re: 2.6.15-mm3, current -git: drivers/media/video/ compile errors

[Mauro Carvalho Chehab]

Adrian,

	Sorry for that. It is already fixed on v4l-dvb.git tree (branch new).
I'm just testing make allyesconfig right now.

Cheers
Mauro

Em Qua, 2006-01-11 às 23:22 +0100, Adrian Bunk escreveu:
> On Wed, Jan 11, 2006 at 05:21:23PM +0100, Dominik Karall wrote:
> > 
> > hi!
> > it doesn't compile here.
> > 
> >   CC      drivers/media/video/tveeprom.o
> >   LD      drivers/media/video/built-in.o
> > drivers/media/video/tuner.o:(.bss+0x0): multiple definition of `debug'
> > drivers/media/video/msp3400.o:(.bss+0xc): first defined here
> > make[3]: *** [drivers/media/video/built-in.o] Fehler 1
> >...
> 
> I'm getting even one more error:
> 
> <--  snip  -->
> 
> ...
> drivers/media/video/tuner.o:(.bss+0x0): multiple definition of `debug'
> drivers/media/video/msp3400.o:(.bss+0xc): first defined here
> drivers/media/video/cx25840/built-in.o:(.bss+0x0): multiple definition of `debug'
> drivers/media/video/msp3400.o:(.bss+0xc): first defined here
> make[3]: *** [drivers/media/video/built-in.o] Error 1
> 
> <--  snip  -->
> 
> There's sometime a need for variables being global being visible in 
> all objects of a module.
> 
> That's OK.
> 
> But they should never have generic names like "debug" or "once" (the 
> latter and some similar ones don't seem to cause compile errors since 
> they are currently used only once, but they are equally wrong.
> 
> > greets,
> > dominik
> 
> cu
> Adrian
> 
Cheers, 
Mauro.

[PATCH -mm] mm/rmap.c: don't forget to include module.h

[Alexey Dobriyan]

  CC      mm/rmap.o
mm/rmap.c:235: warning: type defaults to `int' in declaration of `EXPORT_SYMBOL'
mm/rmap.c:235: warning: parameter names (without types) in function declaration
mm/rmap.c:235: warning: data definition has no type or storage class

Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
---

 mm/rmap.c |    3 +++
 1 file changed, 3 insertions(+)

--- linux-2.6.15-mm3/mm/rmap.c	2006-01-11 19:42:39.000000000 +0300
+++ linux-2.6.15-mm3-rmap/mm/rmap.c	2006-01-11 19:48:12.000000000 +0300
@@ -52,6 +52,9 @@
 #include <linux/init.h>
 #include <linux/rmap.h>
 #include <linux/rcupdate.h>
+#ifdef CONFIG_MIGRATION
+#include <linux/module.h>
+#endif
 
 #include <asm/tlbflush.h>
 

Re: [PATCH -mm] mm/rmap.c: don't forget to include module.h

[Adrian Bunk]

On Wed, Jan 11, 2006 at 07:57:58PM +0300, Alexey Dobriyan wrote:
>   CC      mm/rmap.o
> mm/rmap.c:235: warning: type defaults to `int' in declaration of `EXPORT_SYMBOL'
> mm/rmap.c:235: warning: parameter names (without types) in function declaration
> mm/rmap.c:235: warning: data definition has no type or storage class
> 
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> ---
> 
>  mm/rmap.c |    3 +++
>  1 file changed, 3 insertions(+)
> 
> --- linux-2.6.15-mm3/mm/rmap.c	2006-01-11 19:42:39.000000000 +0300
> +++ linux-2.6.15-mm3-rmap/mm/rmap.c	2006-01-11 19:48:12.000000000 +0300
> @@ -52,6 +52,9 @@
>  #include <linux/init.h>
>  #include <linux/rmap.h>
>  #include <linux/rcupdate.h>
> +#ifdef CONFIG_MIGRATION
> +#include <linux/module.h>
> +#endif
>...

There's no need for an #ifdef.

cu
Adrian

-- 

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

Re: [PATCH -mm] mm/rmap.c: don't forget to include module.h

[Christoph Lameter]

On Wed, 11 Jan 2006, Adrian Bunk wrote:

> There's no need for an #ifdef.

Correct. Just put the #include back.

Re: 2.6.15-mm3

[Roman Zippel]

Hi,

On Wed, 11 Jan 2006, Andrew Morton wrote:

> -hrtimer-...

Andrew, why did you merge this one? :-(

bye, Roman

Re: 2.6.15-mm3

[Andrew Morton]

Roman Zippel <zippel@linux-m68k.org> wrote:
>
> Hi,
> 
> On Wed, 11 Jan 2006, Andrew Morton wrote:
> 
> > -hrtimer-...
> 
> Andrew, why did you merge this one? :-(
> 

Because the egregious rename-the-whole-world parts got taken out and
everyone who'd looked at and worked on the code except for yourself was
happy with it.

Ignoring the objections of a long-standing and respected kernel developer
is not a thing I like to do, but fortunately it's very rare.

Can you summarise, yet again, in as few words as possible, what you find
wrong with it?  I'd really like to understand, but there were waay too many
lengthy emails..

Re: 2.6.15-mm3

[Roman Zippel]

Hi,

On Wed, 11 Jan 2006, Andrew Morton wrote:

> Ignoring the objections of a long-standing and respected kernel developer
> is not a thing I like to do, but fortunately it's very rare.

I really hoped where would be a question before if there were outstanding 
issues.

> Can you summarise, yet again, in as few words as possible, what you find
> wrong with it?  I'd really like to understand, but there were waay too many
> lengthy emails..

The whole resolution issue is still outstanding. It basically assumes 
already high resolution timer and makes it hard to allow simple low 
resolution timer.

The rounding is broken for relative timer started on low resolution 
clocks. The run_hrtimer_queue() calls get_time() every interrupt, wasting 
time if that call should be slow (and could be avoided completely for low 
resolution timers).
I haven't even gotten to a number of small issues, because it's impossible 
to discuss even the general issues with Thomas. :-(

bye, Roman

Re: 2.6.15-mm3

[Brice Goglin]

Andrew Morton wrote:

> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/


Hi Andrew,

I am seeing the following message (which does not seem to cause any
problem):

pcmcia: Detected deprecated PCMCIA ioctl usage.
This interface will soon be removed from the kernel; please expect
breakage unless you upgrade to new tools.
pcmcia: see
http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
cs: IO port probe 0x100-0x4ff: excluding 0x3f0-0x3ff 0x4d0-0x4d7
cs: IO port probe 0x800-0x8ff: clean.
cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff
cs: IO port probe 0xa00-0xaff: clean.
BUG: atomic counter underflow at:
 [<c01a0921>] kref_put+0x4d/0x68
 [<c01a0051>] kobject_put+0x16/0x19
 [<c01a0475>] kobject_release+0x0/0xa
 [<e0a40b20>] ds_ioctl+0x380/0x6e8 [pcmcia]
 [<c0153301>] do_ioctl+0x3d/0x4e
 [<c01534fc>] vfs_ioctl+0x1ea/0x1fb
 [<c0153538>] sys_ioctl+0x2b/0x47
 [<c0102a2d>] syscall_call+0x7/0xb

Any idea about what patch I could revert ?

Regards,
Brice

Re: 2.6.15-mm3

[Dominik Brodowski]

Hi,

On Wed, Jan 11, 2006 at 01:34:33PM -0500, Brice Goglin wrote:
> Andrew Morton wrote:
> 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/
> 
> I am seeing the following message (which does not seem to cause any
> problem):
> 
> pcmcia: Detected deprecated PCMCIA ioctl usage.
> This interface will soon be removed from the kernel; please expect
> breakage unless you upgrade to new tools.
> pcmcia: see
> http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
> cs: IO port probe 0x100-0x4ff: excluding 0x3f0-0x3ff 0x4d0-0x4d7
> cs: IO port probe 0x800-0x8ff: clean.
> cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff
> cs: IO port probe 0xa00-0xaff: clean.
> BUG: atomic counter underflow at:
>  [<c01a0921>] kref_put+0x4d/0x68
>  [<c01a0051>] kobject_put+0x16/0x19
>  [<c01a0475>] kobject_release+0x0/0xa
>  [<e0a40b20>] ds_ioctl+0x380/0x6e8 [pcmcia]
>  [<c0153301>] do_ioctl+0x3d/0x4e
>  [<c01534fc>] vfs_ioctl+0x1ea/0x1fb
>  [<c0153538>] sys_ioctl+0x2b/0x47
>  [<c0102a2d>] syscall_call+0x7/0xb

git-pcmcia . I'll look at what's broken. Thanks for reporting this.

	Dominik

Re: 2.6.15-mm3

[Brice Goglin]

Dominik Brodowski wrote:

>>pcmcia: Detected deprecated PCMCIA ioctl usage.
>>This interface will soon be removed from the kernel; please expect
>>breakage unless you upgrade to new tools.
>>pcmcia: see
>>http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
>>cs: IO port probe 0x100-0x4ff: excluding 0x3f0-0x3ff 0x4d0-0x4d7
>>cs: IO port probe 0x800-0x8ff: clean.
>>cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff
>>cs: IO port probe 0xa00-0xaff: clean.
>>BUG: atomic counter underflow at:
>> [<c01a0921>] kref_put+0x4d/0x68
>> [<c01a0051>] kobject_put+0x16/0x19
>> [<c01a0475>] kobject_release+0x0/0xa
>> [<e0a40b20>] ds_ioctl+0x380/0x6e8 [pcmcia]
>> [<c0153301>] do_ioctl+0x3d/0x4e
>> [<c01534fc>] vfs_ioctl+0x1ea/0x1fb
>> [<c0153538>] sys_ioctl+0x2b/0x47
>> [<c0102a2d>] syscall_call+0x7/0xb
>>    
>>
>
>git-pcmcia . I'll look at what's broken. Thanks for reporting this.
>  
>
Confirmed, works after reverting it.

Brice

Re: 2.6.15-mm3

[Dominik Brodowski]

Hi,

On Wed, Jan 11, 2006 at 02:07:13PM -0500, Brice Goglin wrote:
> >git-pcmcia . I'll look at what's broken. Thanks for reporting this.
> >  
> >
> Confirmed, works after reverting it.

Could you check whether this patch helps, please?

diff --git a/drivers/pcmcia/pcmcia_ioctl.c b/drivers/pcmcia/pcmcia_ioctl.c
index c4f7dfb..5f815bf 100644
--- a/drivers/pcmcia/pcmcia_ioctl.c
+++ b/drivers/pcmcia/pcmcia_ioctl.c
@@ -69,25 +69,26 @@ extern int ds_pc_debug;
 #define ds_dbg(lvl, fmt, arg...) do { } while (0)
 #endif
 
-static struct pcmcia_device * get_pcmcia_device (struct pcmcia_socket *s,
-						 unsigned int function)
+static struct pcmcia_device *get_pcmcia_device(struct pcmcia_socket *s,
+						unsigned int function)
 {
 	struct pcmcia_device *p_dev = NULL;
-
 	unsigned long flags;
+
 	spin_lock_irqsave(&pcmcia_dev_list_lock, flags);
-        list_for_each_entry(p_dev, &s->devices_list, socket_device_list) {
+	list_for_each_entry(p_dev, &s->devices_list, socket_device_list) {
 		if (p_dev->func == function) {
 			p_dev = pcmcia_get_dev(p_dev);
 			break;
 		}
 	}
+	spin_unlock_irqrestore(&pcmcia_dev_list_lock, flags);
 	return p_dev;
 }
 
 /* backwards-compatible accessing of driver --- by name! */
 
-static struct pcmcia_driver * get_pcmcia_driver (dev_info_t *dev_info)
+static struct pcmcia_driver *get_pcmcia_driver(dev_info_t *dev_info)
 {
 	struct device_driver *drv;
 	struct pcmcia_driver *p_drv;
@@ -625,15 +626,15 @@ static int ds_ioctl(struct inode * inode
 	ret = pccard_reset_card(s);
 	break;
     case DS_GET_STATUS:
-	if (buf->status.Function &&
-	   (buf->status.Function >= s->functions))
-	    ret = CS_BAD_ARGS;
-	else {
-	    struct pcmcia_device *p_dev = get_pcmcia_device(s, buf->status.Function);
-	    ret = pccard_get_status(s, p_dev, &buf->status);
-	    pcmcia_put_dev(p_dev);
-	}
-	break;
+	    if (buf->status.Function &&
+		(buf->status.Function >= s->functions))
+		    ret = CS_BAD_ARGS;
+	    else {
+		    struct pcmcia_device *p_dev = get_pcmcia_device(s, buf->status.Function);
+		    ret = pccard_get_status(s, p_dev, &buf->status);
+		    pcmcia_put_dev(p_dev);
+	    }
+	    break;
     case DS_VALIDATE_CIS:
 	mutex_lock(&s->skt_mutex);
 	pcmcia_validate_mem(s);

Re: 2.6.15-mm3

[Brice Goglin]

Dominik Brodowski wrote:

>Could you check whether this patch helps, please?
>
>  
>
No, sorry, it does not fix it.
This patch is actually only white spaces cleanups and the addition of a
spin_lock_irqrestore, right ?

Brice



>diff --git a/drivers/pcmcia/pcmcia_ioctl.c b/drivers/pcmcia/pcmcia_ioctl.c
>index c4f7dfb..5f815bf 100644
>--- a/drivers/pcmcia/pcmcia_ioctl.c
>+++ b/drivers/pcmcia/pcmcia_ioctl.c
>@@ -69,25 +69,26 @@ extern int ds_pc_debug;
> #define ds_dbg(lvl, fmt, arg...) do { } while (0)
> #endif
> 
>-static struct pcmcia_device * get_pcmcia_device (struct pcmcia_socket *s,
>-						 unsigned int function)
>+static struct pcmcia_device *get_pcmcia_device(struct pcmcia_socket *s,
>+						unsigned int function)
> {
> 	struct pcmcia_device *p_dev = NULL;
>-
> 	unsigned long flags;
>+
> 	spin_lock_irqsave(&pcmcia_dev_list_lock, flags);
>-        list_for_each_entry(p_dev, &s->devices_list, socket_device_list) {
>+	list_for_each_entry(p_dev, &s->devices_list, socket_device_list) {
> 		if (p_dev->func == function) {
> 			p_dev = pcmcia_get_dev(p_dev);
> 			break;
> 		}
> 	}
>+	spin_unlock_irqrestore(&pcmcia_dev_list_lock, flags);
> 	return p_dev;
> }
> 
> /* backwards-compatible accessing of driver --- by name! */
> 
>-static struct pcmcia_driver * get_pcmcia_driver (dev_info_t *dev_info)
>+static struct pcmcia_driver *get_pcmcia_driver(dev_info_t *dev_info)
> {
> 	struct device_driver *drv;
> 	struct pcmcia_driver *p_drv;
>@@ -625,15 +626,15 @@ static int ds_ioctl(struct inode * inode
> 	ret = pccard_reset_card(s);
> 	break;
>     case DS_GET_STATUS:
>-	if (buf->status.Function &&
>-	   (buf->status.Function >= s->functions))
>-	    ret = CS_BAD_ARGS;
>-	else {
>-	    struct pcmcia_device *p_dev = get_pcmcia_device(s, buf->status.Function);
>-	    ret = pccard_get_status(s, p_dev, &buf->status);
>-	    pcmcia_put_dev(p_dev);
>-	}
>-	break;
>+	    if (buf->status.Function &&
>+		(buf->status.Function >= s->functions))
>+		    ret = CS_BAD_ARGS;
>+	    else {
>+		    struct pcmcia_device *p_dev = get_pcmcia_device(s, buf->status.Function);
>+		    ret = pccard_get_status(s, p_dev, &buf->status);
>+		    pcmcia_put_dev(p_dev);
>+	    }
>+	    break;
>     case DS_VALIDATE_CIS:
> 	mutex_lock(&s->skt_mutex);
> 	pcmcia_validate_mem(s);
>  
>

Re: 2.6.15-mm3

[Dominik Brodowski]

Hi,

On Wed, Jan 11, 2006 at 03:28:28PM -0500, Brice Goglin wrote:
> Dominik Brodowski wrote:
> 
> >Could you check whether this patch helps, please?
> >
> >  
> >
> No, sorry, it does not fix it.

Ouch.

> This patch is actually only white spaces cleanups and the addition of a
> spin_lock_irqrestore, right ?

Exactly. Could you pass the parameter pc_debug=9 to the "pcmcia" module,
please, and send me the resulting dmesg? I can't reproduce it here,
unfortunately...

Thanks!
	Dominik

Re: 2.6.15-mm3

[Brice Goglin]

Dominik Brodowski wrote:

>Exactly. Could you pass the parameter pc_debug=9 to the "pcmcia" module,
>please, and send me the resulting dmesg? I can't reproduce it here,
>unfortunately...
>  
>
Here you are (I had to enable CONFIG_PCMCIA_DEBUG).
Brice


ds: ds_open(socket 0)
pcmcia: Detected deprecated PCMCIA ioctl usage.
pcmcia: This interface will soon be removed from the kernel; please
expect breakage unless you upgrade to new tools.
pcmcia: see
http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
ds: ds_open(socket 1)
ds: ds_open(socket 1)
ds: ds_ioctl(socket 0, 0xc0146402, 0x8070358)
cs: IO port probe 0x100-0x4ff: excluding 0x3f0-0x3ff 0x4d0-0x4d7
ds: ds_ioctl(socket 0, 0xc0146402, 0x8070378)
cs: IO port probe 0x800-0x8ff: clean.
ds: ds_ioctl(socket 0, 0xc0146402, 0x8070398)
cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff
ds: ds_ioctl(socket 0, 0xc0146402, 0x80703b8)
ds: ds_ioctl(socket 0, 0xc0146402, 0x80703d8)
ds: ds_ioctl(socket 0, 0xc0146402, 0x80703f8)
ds: ds_ioctl(socket 0, 0xc0146402, 0x8070418)
cs: IO port probe 0xa00-0xaff: clean.
ds: ds_ioctl(socket 0, 0xc0146402, 0x8070438)
ds: ds_ioctl(socket 0, 0xc0146402, 0x8070458)
ds: ds_ioctl(socket 0, 0xc00c6409, 0xbf9fd974)
BUG: atomic counter underflow at:
 [<c01a0921>] kref_put+0x4d/0x68
 [<c01a0051>] kobject_put+0x16/0x19
 [<c01a0475>] kobject_release+0x0/0xa
 [<e0a3abfa>] ds_ioctl+0x3dd/0x781 [pcmcia]
 [<c0153301>] do_ioctl+0x3d/0x4e
 [<c01534fc>] vfs_ioctl+0x1ea/0x1fb
 [<c0153538>] sys_ioctl+0x2b/0x47
 [<c0102a2d>] syscall_call+0x7/0xb
ds: ds_ioctl: ret = 20
ds: ds_poll(socket 0)
ds: ds_poll(socket 0)

Re: 2.6.15-mm3

[Dominik Brodowski]

On Wed, Jan 11, 2006 at 05:47:30PM -0500, Brice Goglin wrote:
> Dominik Brodowski wrote:
> 
> >Exactly. Could you pass the parameter pc_debug=9 to the "pcmcia" module,
> >please, and send me the resulting dmesg? I can't reproduce it here,
> >unfortunately...
> >  
> >
> Here you are (I had to enable CONFIG_PCMCIA_DEBUG).

Many thanks... Could you try out this patch instead of the other one,
please? get_pcmcia_device() seems to be the buggiest function I've ever
written, sorry about that...

Thanks,
	Dominik

diff --git a/drivers/pcmcia/pcmcia_ioctl.c b/drivers/pcmcia/pcmcia_ioctl.c
index c4f7dfb..be08bc9 100644
--- a/drivers/pcmcia/pcmcia_ioctl.c
+++ b/drivers/pcmcia/pcmcia_ioctl.c
@@ -69,25 +69,26 @@ extern int ds_pc_debug;
 #define ds_dbg(lvl, fmt, arg...) do { } while (0)
 #endif
 
-static struct pcmcia_device * get_pcmcia_device (struct pcmcia_socket *s,
-						 unsigned int function)
+static struct pcmcia_device *get_pcmcia_device(struct pcmcia_socket *s,
+						unsigned int function)
 {
 	struct pcmcia_device *p_dev = NULL;
-
 	unsigned long flags;
+
 	spin_lock_irqsave(&pcmcia_dev_list_lock, flags);
-        list_for_each_entry(p_dev, &s->devices_list, socket_device_list) {
+	list_for_each_entry(p_dev, &s->devices_list, socket_device_list) {
 		if (p_dev->func == function) {
-			p_dev = pcmcia_get_dev(p_dev);
-			break;
+			spin_unlock_irqrestore(&pcmcia_dev_list_lock, flags);
+			return pcmcia_get_dev(p_dev);
 		}
 	}
-	return p_dev;
+	spin_unlock_irqrestore(&pcmcia_dev_list_lock, flags);
+	return NULL;
 }
 
 /* backwards-compatible accessing of driver --- by name! */
 
-static struct pcmcia_driver * get_pcmcia_driver (dev_info_t *dev_info)
+static struct pcmcia_driver *get_pcmcia_driver(dev_info_t *dev_info)
 {
 	struct device_driver *drv;
 	struct pcmcia_driver *p_drv;
@@ -625,15 +626,15 @@ static int ds_ioctl(struct inode * inode
 	ret = pccard_reset_card(s);
 	break;
     case DS_GET_STATUS:
-	if (buf->status.Function &&
-	   (buf->status.Function >= s->functions))
-	    ret = CS_BAD_ARGS;
-	else {
-	    struct pcmcia_device *p_dev = get_pcmcia_device(s, buf->status.Function);
-	    ret = pccard_get_status(s, p_dev, &buf->status);
-	    pcmcia_put_dev(p_dev);
-	}
-	break;
+	    if (buf->status.Function &&
+		(buf->status.Function >= s->functions))
+		    ret = CS_BAD_ARGS;
+	    else {
+		    struct pcmcia_device *p_dev = get_pcmcia_device(s, buf->status.Function);
+		    ret = pccard_get_status(s, p_dev, &buf->status);
+		    pcmcia_put_dev(p_dev);
+	    }
+	    break;
     case DS_VALIDATE_CIS:
 	mutex_lock(&s->skt_mutex);
 	pcmcia_validate_mem(s);

Re: 2.6.15-mm3

[Brice Goglin]

Dominik Brodowski wrote:

>Many thanks... Could you try out this patch instead of the other one,
>please? get_pcmcia_device() seems to be the buggiest function I've ever
>written, sorry about that...
>  
>
It works, thanks. Good job!

Brice

Re: 2.6.15-mm3

[Andrew Morton]

Brice Goglin <Brice.Goglin@ens-lyon.org> wrote:
>
> Andrew Morton wrote:
> 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/
> 
> 
> Hi Andrew,
> 
> I am seeing the following message (which does not seem to cause any
> problem):
> 
> pcmcia: Detected deprecated PCMCIA ioctl usage.
> This interface will soon be removed from the kernel; please expect
> breakage unless you upgrade to new tools.
> pcmcia: see
> http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
> cs: IO port probe 0x100-0x4ff: excluding 0x3f0-0x3ff 0x4d0-0x4d7
> cs: IO port probe 0x800-0x8ff: clean.
> cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff
> cs: IO port probe 0xa00-0xaff: clean.
> BUG: atomic counter underflow at:
>  [<c01a0921>] kref_put+0x4d/0x68
>  [<c01a0051>] kobject_put+0x16/0x19
>  [<c01a0475>] kobject_release+0x0/0xa
>  [<e0a40b20>] ds_ioctl+0x380/0x6e8 [pcmcia]
>  [<c0153301>] do_ioctl+0x3d/0x4e
>  [<c01534fc>] vfs_ioctl+0x1ea/0x1fb
>  [<c0153538>] sys_ioctl+0x2b/0x47
>  [<c0102a2d>] syscall_call+0x7/0xb
> 
> Any idea about what patch I could revert ?

git-pcmcia-ssh-needs-mutexh.patch and then git-pcmcia.patch, I expect.

Re: 2.6.15-mm3

[Grant Coady]

On Wed, 11 Jan 2006 04:21:35 -0800, Andrew Morton <akpm@osdl.org> wrote:

>
>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/
>
>- New config options (VMSPLIT_*) to permit non-standard user/kernel
>  splitting on x86.  Needs testing please.
>
>- Lots of updates to the USB, PCI, driver and I2C trees.  This is usually a
>  worry.

Well, it booted :o)  but I get these strange:

grant@sempro:~$ dmesg |grep -B 5 "SET:"
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:0f.1
**** SET: Misaligned resource pointer: efe7ac22 Type 07 Len 0
--
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
 sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 >
sd 1:0:0:0: Attached scsi disk sdb
**** SET: Misaligned resource pointer: efe7ac22 Type 07 Len 0
--
Advanced Linux Sound Architecture Driver Version 1.0.11rc2 (Wed Jan 04 08:57:20 2006 UTC).
via82xx: Assuming DXS channels with 48k fixed sample rate.
         Please try dxs_support=5 option
         and report if it works on your machine.
         For more details, read ALSA-Configuration.txt.
**** SET: Misaligned resource pointer: b19c5b82 Type 07 Len 0
--
e100: Copyright(c) 1999-2005 Intel Corporation
ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 17 (level, low) -> IRQ 19
e100: eth0: e100_probe: addr 0xee100000, irq 19, MAC addr 00:02:B3:3F:EA:67
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker
**** SET: Misaligned resource pointer: efed7662 Type 07 Len 0

Plus a warning:
Driver 'w83627hf' needs updating - please use bus_type methods

Full dmesg appended.  grep = .config at:
  http://bugsplatter.mine.nu/test/boxen/sempro/config-2.6.15-mm3a.gz

Thanks,
Grant.

grant@sempro:~$ dmesg
Linux version 2.6.15-mm3a (grant@sempro) (gcc version 3.3.6) #1 Thu Jan 12 09:28:24 EST 2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
 BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
 BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
 BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
1023MB LOWMEM available.
found SMP MP-table at 000f52f0
On node 0 totalpages: 262128
  DMA zone: 4096 pages, LIFO batch:0
  DMA32 zone: 0 pages, LIFO batch:0
  Normal zone: 258032 pages, LIFO batch:31
  HighMem zone: 0 pages, LIFO batch:0
DMI 2.3 present.
ACPI: RSDP (v000 KM400                                 ) @ 0x000f6dd0
ACPI: RSDT (v001 KM400  AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff3000
ACPI: FADT (v001 KM400  AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff3040
ACPI: MADT (v001 KM400  AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff7f40
ACPI: DSDT (v001 KM400  AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x00000000
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:8 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 3, 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 dfl dfl)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
Detected 1833.216 MHz processor.
Built 1 zonelists
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Kernel command line: auto BOOT_IMAGE=2.6.15-mm3a ro root=803 video=vesafb:mtrr,ywrap
CPU 0 irqstacks, hard=b0479000 soft=b0478000
PID hash table entries: 4096 (order: 12, 65536 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 131072 (order: 7, 524288 bytes)
Memory: 1034408k/1048512k available (2502k kernel code, 13608k reserved, 843k data, 180k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 3669.41 BogoMIPS (lpj=18347083)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1cbfbff 00000000 00000020 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
mtrr: v2.0 (20020519)
CPU: AMD Sempron(tm)   2600+ stepping 01
Checking 'hlt' instruction... OK.
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfbaf0, last bus=1
PCI: Using configuration type 1
ACPI: Subsystem revision 20051216
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 *10 11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 6 7 10 *11 12)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 11 *12)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [ALKA] (IRQs *20)
ACPI: PCI Interrupt Link [ALKB] (IRQs *21)
ACPI: PCI Interrupt Link [ALKC] (IRQs *22)
ACPI: PCI Interrupt Link [ALKD] (IRQs *23)
Linux Plug and Play Support v0.97 (c) Adam Belay
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
pnp: the driver 'system' has been registered
PCI: Bridge: 0000:00:01.0
  IO window: disabled.
  MEM window: ec000000-edffffff
  PREFETCH window: e8000000-ebffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
Machine check exception polling timer started.
io scheduler noop registered
io scheduler deadline registered
PCI: Bypassing VIA 8237 APIC De-Assert Message
vesafb: framebuffer at 0xe8000000, mapped to 0xf0880000, using 1536k, total 65536k
vesafb: mode is 1024x768x8, linelength=1024, pages=3
vesafb: protected mode interface info at c000:e710
vesafb: pmi: set display start = b00ce755, set palette = b00ce7da
vesafb: pmi: ports = b4c3 b503 ba03 c003 c103 c403 c503 c603 c703 c803 c903 cc03 ce03 cf03 d003 d103 d203 d303 d403 d503 da03 ff03
vesafb: scrolling: ywrap using protected mode interface, yres_virtual=1536
vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0
Time: tsc clocksource has been installed.
Console: switching to colour frame buffer device 85x34
fb0: VESA VGA frame buffer device
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [PWRB]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Fan [FAN] (on)
Using specific hotkey driver
ACPI: Thermal Zone [THRM] (50 C)
Real Time Clock Driver v1.12ac
pnp: the driver 'i8042 kbd' has been registered
pnp: the driver 'i8042 aux' has been registered
pnp: the driver 'i8042 kbd' has been unregistered
pnp: the driver 'i8042 aux' has been unregistered
PNP: No PS/2 controller found. Probing ports directly.
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 $ 0 ports, IRQ sharing disabled
pnp: the driver 'serial' has been registered
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:0f.1
**** SET: Misaligned resource pointer: efe7ac22 Type 07 Len 0
ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20
ACPI: PCI Interrupt 0000:00:0f.1[A] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 16
PCI: Via IRQ fixup for 0000:00:0f.1, from 255 to 0
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
    ide0: BM-DMA at 0xe700-0xe707, BIOS settings: hda:pio, hdb:DMA
    ide1: BM-DMA at 0xe708-0xe70f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hdb: LITE-ON DVDRW SOHW-812S, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
ide1 at 0x170-0x177,0x376 on irq 15
QLogic Fibre Channel HBA Driver
libata version 1.20 loaded.
sata_via 0000:00:0f.0: version 1.1
ACPI: PCI Interrupt 0000:00:0f.0[B] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 16
PCI: Via IRQ fixup for 0000:00:0f.0, from 11 to 0
sata_via 0000:00:0f.0: routed to hard irq line 0
ata1: SATA max UDMA/133 cmd 0xE100 ctl 0xE202 bmdma 0xE500 irq 16
ata2: SATA max UDMA/133 cmd 0xE300 ctl 0xE402 bmdma 0xE508 irq 16
ata1: SATA link up 1.5 Gbps (SStatus 113)
ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:407f
ata1: dev 0 ATA-6, max UDMA/133, 234441648 sectors: LBA48
ata1: dev 0 configured for UDMA/133
scsi0 : sata_via
ata2: SATA link up 1.5 Gbps (SStatus 113)
ata2: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:407f
ata2: dev 0 ATA-6, max UDMA/133, 312581808 sectors: LBA48
ata2: dev 0 configured for UDMA/133
scsi1 : sata_via
  Vendor: ATA       Model: ST3120827AS       Rev: 3.42
  Type:   Direct-Access                      ANSI SCSI revision: 05
  Vendor: ATA       Model: ST3160827AS       Rev: 3.42
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15 >
sd 0:0:0:0: Attached scsi disk sda
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
 sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 >
sd 1:0:0:0: Attached scsi disk sdb
**** SET: Misaligned resource pointer: efe7ac22 Type 07 Len 0
ACPI: PCI Interrupt Link [ALKB] enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:10.4[C] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 17
PCI: Via IRQ fixup for 0000:00:10.4, from 12 to 1
ehci_hcd 0000:00:10.4: EHCI Host Controller
ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:10.4: irq 17, io mem 0xee102000
ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 17
PCI: Via IRQ fixup for 0000:00:10.0, from 10 to 1
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:10.0: irq 17, io base 0x0000e800
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.1[A] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 17
PCI: Via IRQ fixup for 0000:00:10.1, from 10 to 1
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:10.1: irq 17, io base 0x0000e900
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.2[B] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 17
PCI: Via IRQ fixup for 0000:00:10.2, from 11 to 1
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:10.2: irq 17, io base 0x0000ea00
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.3[B] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 17
PCI: Via IRQ fixup for 0000:00:10.3, from 11 to 1
uhci_hcd 0000:00:10.3: UHCI Host Controller
uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:10.3: irq 17, io base 0x0000eb00
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
usb 2-2: new low speed USB device using uhci_hcd and address 2
Initializing USB Mass Storage driver...
usb 2-2: configuration #1 chosen from 1 choice
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
input: Microsoft Microsoft IntelliMouse® Optical as /class/input/input0
input: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb-0000:00:10.0-2
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
mice: PS/2 mouse device common for all mice
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
Advanced Linux Sound Architecture Driver Version 1.0.11rc2 (Wed Jan 04 08:57:20 2006 UTC).
via82xx: Assuming DXS channels with 48k fixed sample rate.
         Please try dxs_support=5 option
         and report if it works on your machine.
         For more details, read ALSA-Configuration.txt.
**** SET: Misaligned resource pointer: b19c5b82 Type 07 Len 0
ACPI: PCI Interrupt Link [ALKC] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [ALKC] -> GSI 22 (level, low) -> IRQ 18
PCI: Via IRQ fixup for 0000:00:11.5, from 12 to 2
PCI: Setting latency timer of device 0000:00:11.5 to 64
input: AT Translated Set 2 keyboard as /class/input/input1
atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
ALSA device list:
  #0: VIA 8237 with VIA1617A at 0xec00, irq 18
NET: Registered protocol family 2
input: AT Translated Set 2 keyboard as /class/input/input2
IP route cache hash table entries: 65536 (order: 6, 262144 bytes)
TCP established hash table entries: 262144 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
ReiserFS: sda3: found reiserfs format "3.6" with standard journal
ReiserFS: sda3: using ordered data mode
ReiserFS: sda3: journal params: device sda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda3: checking transaction log (sda3)
ReiserFS: sda3: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 180k freed
Adding 514040k swap on /dev/sda5.  Priority:1 extents:1 across:514040k
Adding 1028120k swap on /dev/sdb1.  Priority:1 extents:1 across:1028120k
ReiserFS: sdb5: found reiserfs format "3.6" with standard journal
ReiserFS: sdb5: using ordered data mode
ReiserFS: sdb5: journal params: device sdb5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sdb5: checking transaction log (sdb5)
ReiserFS: sdb5: Using r5 hash to sort names
ReiserFS: sda6: found reiserfs format "3.6" with standard journal
ReiserFS: sda6: using ordered data mode
ReiserFS: sda6: journal params: device sda6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda6: checking transaction log (sda6)
ReiserFS: sda6: Using r5 hash to sort names
ReiserFS: sda7: found reiserfs format "3.6" with standard journal
ReiserFS: sda7: using ordered data mode
ReiserFS: sda7: journal params: device sda7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda7: checking transaction log (sda7)
ReiserFS: sda7: Using r5 hash to sort names
e100: Intel(R) PRO/100 Network Driver, 3.4.14-k4-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 17 (level, low) -> IRQ 19
e100: eth0: e100_probe: addr 0xee100000, irq 19, MAC addr 00:02:B3:3F:EA:67
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker
**** SET: Misaligned resource pointer: efed7662 Type 07 Len 0
ACPI: PCI Interrupt Link [ALKD] enabled at IRQ 23
ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [ALKD] -> GSI 23 (level, low) -> IRQ 20
PCI: Via IRQ fixup for 0000:00:12.0, from 10 to 4
eth1: VIA Rhine II at 0xee103000, 00:11:09:d1:8e:23, IRQ 20.
eth1: MII PHY found at address 1, status 0x786d advertising 05e1 Link 41e1.
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
Driver 'w83627hf' needs updating - please use bus_type methods
grant@sempro:~$

2.6.15-mm3: arch/ia64/sn/kernel/sn2/sn_proc_fs.c compile error

[Adrian Bunk]

Arjan, it seems the following compile error on ia64 is caused by a patch 
of you that makes some stuff static:

<--  snip  -->

...
  CC      arch/ia64/sn/kernel/sn2/sn_proc_fs.o
arch/ia64/sn/kernel/sn2/sn_proc_fs.c: In function 'sn_procfs_create_entry':
arch/ia64/sn/kernel/sn2/sn_proc_fs.c:104: warning: passing argument 1 of 'memset' discards qualifiers from pointer target type
arch/ia64/sn/kernel/sn2/sn_proc_fs.c:105: error: assignment of read-only member 'open'
arch/ia64/sn/kernel/sn2/sn_proc_fs.c:106: error: assignment of read-only member 'read'
arch/ia64/sn/kernel/sn2/sn_proc_fs.c:107: error: assignment of read-only member 'llseek'
arch/ia64/sn/kernel/sn2/sn_proc_fs.c:108: error: assignment of read-only member 'release'
arch/ia64/sn/kernel/sn2/sn_proc_fs.c: In function 'register_sn_procfs':
arch/ia64/sn/kernel/sn2/sn_proc_fs.c:140: error: assignment of read-only member 'write'
make[3]: *** [arch/ia64/sn/kernel/sn2/sn_proc_fs.o] Error 1

<--  snip  -->

cu
Adrian

-- 

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

2.6.15-mm3: arch/ia64/sn/kernel/sn2/sn_proc_fs.c compile error

[Adrian Bunk]

Arjan, it seems the following compile error on ia64 is caused by a patch 
of you that makes some stuff static:

<--  snip  -->

...
  CC      arch/ia64/sn/kernel/sn2/sn_proc_fs.o
arch/ia64/sn/kernel/sn2/sn_proc_fs.c: In function 'sn_procfs_create_entry':
arch/ia64/sn/kernel/sn2/sn_proc_fs.c:104: warning: passing argument 1 of 'memset' discards qualifiers from pointer target type
arch/ia64/sn/kernel/sn2/sn_proc_fs.c:105: error: assignment of read-only member 'open'
arch/ia64/sn/kernel/sn2/sn_proc_fs.c:106: error: assignment of read-only member 'read'
arch/ia64/sn/kernel/sn2/sn_proc_fs.c:107: error: assignment of read-only member 'llseek'
arch/ia64/sn/kernel/sn2/sn_proc_fs.c:108: error: assignment of read-only member 'release'
arch/ia64/sn/kernel/sn2/sn_proc_fs.c: In function 'register_sn_procfs':
arch/ia64/sn/kernel/sn2/sn_proc_fs.c:140: error: assignment of read-only member 'write'
make[3]: *** [arch/ia64/sn/kernel/sn2/sn_proc_fs.o] Error 1

<--  snip  -->

cu
Adrian

-- 

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

Re: 2.6.15-mm3: arch/ia64/sn/kernel/sn2/sn_proc_fs.c compile error

[Andrew Morton]

Adrian Bunk <bunk@stusta.de> wrote:
>
> Arjan, it seems the following compile error on ia64 is caused by a patch 
>  of you that makes some stuff static:
> 
>  <--  snip  -->
> 
>  ...
>    CC      arch/ia64/sn/kernel/sn2/sn_proc_fs.o
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c: In function 'sn_procfs_create_entry':
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:104: warning: passing argument 1 of 'memset' discards qualifiers from pointer target type
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:105: error: assignment of read-only member 'open'
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:106: error: assignment of read-only member 'read'
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:107: error: assignment of read-only member 'llseek'
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:108: error: assignment of read-only member 'release'
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c: In function 'register_sn_procfs':
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:140: error: assignment of read-only member 'write'

This?

--- devel/arch/ia64/sn/kernel/sn2/sn_proc_fs.c~ia64-const-f_ops-fix	2006-01-11 15:58:41.000000000 -0800
+++ devel-akpm/arch/ia64/sn/kernel/sn2/sn_proc_fs.c	2006-01-11 16:00:50.000000000 -0800
@@ -98,14 +98,15 @@ static struct proc_dir_entry *sn_procfs_
 	struct proc_dir_entry *e = create_proc_entry(name, 0444, parent);
 
 	if (e) {
-		e->proc_fops = (struct file_operations *)kmalloc(
-			sizeof(struct file_operations), GFP_KERNEL);
-		if (e->proc_fops) {
-			memset(e->proc_fops, 0, sizeof(struct file_operations));
-			e->proc_fops->open = openfunc;
-			e->proc_fops->read = seq_read;
-			e->proc_fops->llseek = seq_lseek;
-			e->proc_fops->release = releasefunc;
+		struct file_operations *f;
+
+		f = kzalloc(sizeof(*f), GFP_KERNEL);
+		if (f) {
+			f->open = openfunc;
+			f->read = seq_read;
+			f->llseek = seq_lseek;
+			f->release = releasefunc;
+			e->proc_fops = f;
 		}
 	}
 
_

Re: 2.6.15-mm3: arch/ia64/sn/kernel/sn2/sn_proc_fs.c compile error

[Andrew Morton]

Adrian Bunk <bunk@stusta.de> wrote:
>
> Arjan, it seems the following compile error on ia64 is caused by a patch 
>  of you that makes some stuff static:
> 
>  <--  snip  -->
> 
>  ...
>    CC      arch/ia64/sn/kernel/sn2/sn_proc_fs.o
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c: In function 'sn_procfs_create_entry':
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:104: warning: passing argument 1 of 'memset' discards qualifiers from pointer target type
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:105: error: assignment of read-only member 'open'
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:106: error: assignment of read-only member 'read'
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:107: error: assignment of read-only member 'llseek'
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:108: error: assignment of read-only member 'release'
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c: In function 'register_sn_procfs':
>  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:140: error: assignment of read-only member 'write'

This?

--- devel/arch/ia64/sn/kernel/sn2/sn_proc_fs.c~ia64-const-f_ops-fix	2006-01-11 15:58:41.000000000 -0800
+++ devel-akpm/arch/ia64/sn/kernel/sn2/sn_proc_fs.c	2006-01-11 16:00:50.000000000 -0800
@@ -98,14 +98,15 @@ static struct proc_dir_entry *sn_procfs_
 	struct proc_dir_entry *e = create_proc_entry(name, 0444, parent);
 
 	if (e) {
-		e->proc_fops = (struct file_operations *)kmalloc(
-			sizeof(struct file_operations), GFP_KERNEL);
-		if (e->proc_fops) {
-			memset(e->proc_fops, 0, sizeof(struct file_operations));
-			e->proc_fops->open = openfunc;
-			e->proc_fops->read = seq_read;
-			e->proc_fops->llseek = seq_lseek;
-			e->proc_fops->release = releasefunc;
+		struct file_operations *f;
+
+		f = kzalloc(sizeof(*f), GFP_KERNEL);
+		if (f) {
+			f->open = openfunc;
+			f->read = seq_read;
+			f->llseek = seq_lseek;
+			f->release = releasefunc;
+			e->proc_fops = f;
 		}
 	}
 
_

Re: 2.6.15-mm3: arch/ia64/sn/kernel/sn2/sn_proc_fs.c compile error

[Adrian Bunk]

On Wed, Jan 11, 2006 at 04:01:21PM -0800, Andrew Morton wrote:
> Adrian Bunk <bunk@stusta.de> wrote:
> >
> > Arjan, it seems the following compile error on ia64 is caused by a patch 
> >  of you that makes some stuff static:
> > 
> >  <--  snip  -->
> > 
> >  ...
> >    CC      arch/ia64/sn/kernel/sn2/sn_proc_fs.o
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c: In function 'sn_procfs_create_entry':
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:104: warning: passing argument 1 of 'memset' discards qualifiers from pointer target type
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:105: error: assignment of read-only member 'open'
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:106: error: assignment of read-only member 'read'
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:107: error: assignment of read-only member 'llseek'
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:108: error: assignment of read-only member 'release'
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c: In function 'register_sn_procfs':
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:140: error: assignment of read-only member 'write'
> 
> This?
>...

Nearly.

The last compile error (line 140) is still present.

cu
Adrian

-- 

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

Re: 2.6.15-mm3: arch/ia64/sn/kernel/sn2/sn_proc_fs.c compile error

[Adrian Bunk]

On Wed, Jan 11, 2006 at 04:01:21PM -0800, Andrew Morton wrote:
> Adrian Bunk <bunk@stusta.de> wrote:
> >
> > Arjan, it seems the following compile error on ia64 is caused by a patch 
> >  of you that makes some stuff static:
> > 
> >  <--  snip  -->
> > 
> >  ...
> >    CC      arch/ia64/sn/kernel/sn2/sn_proc_fs.o
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c: In function 'sn_procfs_create_entry':
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:104: warning: passing argument 1 of 'memset' discards qualifiers from pointer target type
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:105: error: assignment of read-only member 'open'
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:106: error: assignment of read-only member 'read'
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:107: error: assignment of read-only member 'llseek'
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:108: error: assignment of read-only member 'release'
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c: In function 'register_sn_procfs':
> >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:140: error: assignment of read-only member 'write'
> 
> This?
>...

Nearly.

The last compile error (line 140) is still present.

cu
Adrian

-- 

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

Re: 2.6.15-mm3: arch/ia64/sn/kernel/sn2/sn_proc_fs.c compile error

[Andrew Morton]

Adrian Bunk <bunk@stusta.de> wrote:
>
> > >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:140: error: assignment of read-only member 'write'
>  > 
>  > This?
>  >...
> 
>  Nearly.
> 
>  The last compile error (line 140) is still present.

Bah.


diff -puN arch/ia64/sn/kernel/sn2/sn_proc_fs.c~ia64-const-f_ops-fix arch/ia64/sn/kernel/sn2/sn_proc_fs.c
--- devel/arch/ia64/sn/kernel/sn2/sn_proc_fs.c~ia64-const-f_ops-fix	2006-01-11 16:04:18.000000000 -0800
+++ devel-akpm/arch/ia64/sn/kernel/sn2/sn_proc_fs.c	2006-01-11 16:22:38.000000000 -0800
@@ -93,19 +93,22 @@ static int coherence_id_open(struct inod
 static struct proc_dir_entry *sn_procfs_create_entry(
 	const char *name, struct proc_dir_entry *parent,
 	int (*openfunc)(struct inode *, struct file *),
-	int (*releasefunc)(struct inode *, struct file *))
+	int (*releasefunc)(struct inode *, struct file *),
+	ssize_t (*write) (struct file *, const char __user *, size_t, loff_t *))
 {
 	struct proc_dir_entry *e = create_proc_entry(name, 0444, parent);
 
 	if (e) {
-		e->proc_fops = (struct file_operations *)kmalloc(
-			sizeof(struct file_operations), GFP_KERNEL);
-		if (e->proc_fops) {
-			memset(e->proc_fops, 0, sizeof(struct file_operations));
-			e->proc_fops->open = openfunc;
-			e->proc_fops->read = seq_read;
-			e->proc_fops->llseek = seq_lseek;
-			e->proc_fops->release = releasefunc;
+		struct file_operations *f;
+
+		f = kzalloc(sizeof(*f), GFP_KERNEL);
+		if (f) {
+			f->open = openfunc;
+			f->read = seq_read;
+			f->llseek = seq_lseek;
+			f->release = releasefunc;
+			f->write = write;
+			e->proc_fops = f;
 		}
 	}
 
@@ -119,31 +122,29 @@ extern int sn_topology_release(struct in
 void register_sn_procfs(void)
 {
 	static struct proc_dir_entry *sgi_proc_dir = NULL;
-	struct proc_dir_entry *e;
 
 	BUG_ON(sgi_proc_dir != NULL);
 	if (!(sgi_proc_dir = proc_mkdir("sgi_sn", NULL)))
 		return;
 
 	sn_procfs_create_entry("partition_id", sgi_proc_dir,
-		partition_id_open, single_release);
+		partition_id_open, single_release, NULL);
 
 	sn_procfs_create_entry("system_serial_number", sgi_proc_dir,
-		system_serial_number_open, single_release);
+		system_serial_number_open, single_release, NULL);
 
 	sn_procfs_create_entry("licenseID", sgi_proc_dir, 
-		licenseID_open, single_release);
+		licenseID_open, single_release, NULL);
 
-	e = sn_procfs_create_entry("sn_force_interrupt", sgi_proc_dir, 
-		sn_force_interrupt_open, single_release);
-	if (e) 
-		e->proc_fops->write = sn_force_interrupt_write_proc;
+	sn_procfs_create_entry("sn_force_interrupt", sgi_proc_dir,
+		sn_force_interrupt_open, single_release,
+		sn_force_interrupt_write_proc);
 
 	sn_procfs_create_entry("coherence_id", sgi_proc_dir, 
-		coherence_id_open, single_release);
+		coherence_id_open, single_release, NULL);
 	
 	sn_procfs_create_entry("sn_topology", sgi_proc_dir,
-		sn_topology_open, sn_topology_release);
+		sn_topology_open, sn_topology_release, NULL);
 }
 
 #endif /* CONFIG_PROC_FS */
_

Re: 2.6.15-mm3: arch/ia64/sn/kernel/sn2/sn_proc_fs.c compile error

[Andrew Morton]

Adrian Bunk <bunk@stusta.de> wrote:
>
> > >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:140: error: assignment of read-only member 'write'
>  > 
>  > This?
>  >...
> 
>  Nearly.
> 
>  The last compile error (line 140) is still present.

Bah.


diff -puN arch/ia64/sn/kernel/sn2/sn_proc_fs.c~ia64-const-f_ops-fix arch/ia64/sn/kernel/sn2/sn_proc_fs.c
--- devel/arch/ia64/sn/kernel/sn2/sn_proc_fs.c~ia64-const-f_ops-fix	2006-01-11 16:04:18.000000000 -0800
+++ devel-akpm/arch/ia64/sn/kernel/sn2/sn_proc_fs.c	2006-01-11 16:22:38.000000000 -0800
@@ -93,19 +93,22 @@ static int coherence_id_open(struct inod
 static struct proc_dir_entry *sn_procfs_create_entry(
 	const char *name, struct proc_dir_entry *parent,
 	int (*openfunc)(struct inode *, struct file *),
-	int (*releasefunc)(struct inode *, struct file *))
+	int (*releasefunc)(struct inode *, struct file *),
+	ssize_t (*write) (struct file *, const char __user *, size_t, loff_t *))
 {
 	struct proc_dir_entry *e = create_proc_entry(name, 0444, parent);
 
 	if (e) {
-		e->proc_fops = (struct file_operations *)kmalloc(
-			sizeof(struct file_operations), GFP_KERNEL);
-		if (e->proc_fops) {
-			memset(e->proc_fops, 0, sizeof(struct file_operations));
-			e->proc_fops->open = openfunc;
-			e->proc_fops->read = seq_read;
-			e->proc_fops->llseek = seq_lseek;
-			e->proc_fops->release = releasefunc;
+		struct file_operations *f;
+
+		f = kzalloc(sizeof(*f), GFP_KERNEL);
+		if (f) {
+			f->open = openfunc;
+			f->read = seq_read;
+			f->llseek = seq_lseek;
+			f->release = releasefunc;
+			f->write = write;
+			e->proc_fops = f;
 		}
 	}
 
@@ -119,31 +122,29 @@ extern int sn_topology_release(struct in
 void register_sn_procfs(void)
 {
 	static struct proc_dir_entry *sgi_proc_dir = NULL;
-	struct proc_dir_entry *e;
 
 	BUG_ON(sgi_proc_dir != NULL);
 	if (!(sgi_proc_dir = proc_mkdir("sgi_sn", NULL)))
 		return;
 
 	sn_procfs_create_entry("partition_id", sgi_proc_dir,
-		partition_id_open, single_release);
+		partition_id_open, single_release, NULL);
 
 	sn_procfs_create_entry("system_serial_number", sgi_proc_dir,
-		system_serial_number_open, single_release);
+		system_serial_number_open, single_release, NULL);
 
 	sn_procfs_create_entry("licenseID", sgi_proc_dir, 
-		licenseID_open, single_release);
+		licenseID_open, single_release, NULL);
 
-	e = sn_procfs_create_entry("sn_force_interrupt", sgi_proc_dir, 
-		sn_force_interrupt_open, single_release);
-	if (e) 
-		e->proc_fops->write = sn_force_interrupt_write_proc;
+	sn_procfs_create_entry("sn_force_interrupt", sgi_proc_dir,
+		sn_force_interrupt_open, single_release,
+		sn_force_interrupt_write_proc);
 
 	sn_procfs_create_entry("coherence_id", sgi_proc_dir, 
-		coherence_id_open, single_release);
+		coherence_id_open, single_release, NULL);
 	
 	sn_procfs_create_entry("sn_topology", sgi_proc_dir,
-		sn_topology_open, sn_topology_release);
+		sn_topology_open, sn_topology_release, NULL);
 }
 
 #endif /* CONFIG_PROC_FS */
_

Re: 2.6.15-mm3: arch/ia64/sn/kernel/sn2/sn_proc_fs.c compile error

[Adrian Bunk]

On Wed, Jan 11, 2006 at 04:23:19PM -0800, Andrew Morton wrote:
> Adrian Bunk <bunk@stusta.de> wrote:
> >
> > > >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:140: error: assignment of read-only member 'write'
> >  > 
> >  > This?
> >  >...
> > 
> >  Nearly.
> > 
> >  The last compile error (line 140) is still present.
> 
> Bah.
>...

This patch fixed this compile error.

Patch for the next compile error on ia64 follows in a minute...  ;-)

cu
Adrian

-- 

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

Re: 2.6.15-mm3: arch/ia64/sn/kernel/sn2/sn_proc_fs.c compile error

[Adrian Bunk]

On Wed, Jan 11, 2006 at 04:23:19PM -0800, Andrew Morton wrote:
> Adrian Bunk <bunk@stusta.de> wrote:
> >
> > > >  arch/ia64/sn/kernel/sn2/sn_proc_fs.c:140: error: assignment of read-only member 'write'
> >  > 
> >  > This?
> >  >...
> > 
> >  Nearly.
> > 
> >  The last compile error (line 140) is still present.
> 
> Bah.
>...

This patch fixed this compile error.

Patch for the next compile error on ia64 follows in a minute...  ;-)

cu
Adrian

-- 

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

[-mm patch] fix arch/ia64/sn/kernel/tiocx.c compilation

[Adrian Bunk]

On Wed, Jan 11, 2006 at 04:21:35AM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.15-mm2:
>...
> +gregkh-driver-add-tiocx-bus_type-probe-remove-methods.patch
>...
>  driver tree updates
>...

This patch caused the following compile error:

<--  snip  -->

...
  CC      arch/ia64/sn/kernel/tiocx.o
arch/ia64/sn/kernel/tiocx.c:151: error: 'cx_device_remove' undeclared here (not in a function)
make[2]: *** [arch/ia64/sn/kernel/tiocx.o] Error 1

<--  snip  -->


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

--- linux-2.6.15-mm3/arch/ia64/sn/kernel/tiocx.c.old	2006-01-12 01:58:20.000000000 +0100
+++ linux-2.6.15-mm3/arch/ia64/sn/kernel/tiocx.c	2006-01-12 01:58:35.000000000 +0100
@@ -148,7 +148,7 @@
 	.match = tiocx_match,
 	.uevent = tiocx_uevent,
 	.probe = cx_device_probe,
-	.remove = cx_device_remove,
+	.remove = cx_driver_remove,
 };
 
 /**

[-mm patch] fix arch/ia64/sn/kernel/tiocx.c compilation

[Adrian Bunk]

On Wed, Jan 11, 2006 at 04:21:35AM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.15-mm2:
>...
> +gregkh-driver-add-tiocx-bus_type-probe-remove-methods.patch
>...
>  driver tree updates
>...

This patch caused the following compile error:

<--  snip  -->

...
  CC      arch/ia64/sn/kernel/tiocx.o
arch/ia64/sn/kernel/tiocx.c:151: error: 'cx_device_remove' undeclared here (not in a function)
make[2]: *** [arch/ia64/sn/kernel/tiocx.o] Error 1

<--  snip  -->


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

--- linux-2.6.15-mm3/arch/ia64/sn/kernel/tiocx.c.old	2006-01-12 01:58:20.000000000 +0100
+++ linux-2.6.15-mm3/arch/ia64/sn/kernel/tiocx.c	2006-01-12 01:58:35.000000000 +0100
@@ -148,7 +148,7 @@
 	.match = tiocx_match,
 	.uevent = tiocx_uevent,
 	.probe = cx_device_probe,
-	.remove = cx_device_remove,
+	.remove = cx_driver_remove,
 };
 
 /**

Re: [-mm patch] fix arch/ia64/sn/kernel/tiocx.c compilation

[Greg KH]

On Thu, Jan 12, 2006 at 02:02:40AM +0100, Adrian Bunk wrote:
> On Wed, Jan 11, 2006 at 04:21:35AM -0800, Andrew Morton wrote:
> >...
> > Changes since 2.6.15-mm2:
> >...
> > +gregkh-driver-add-tiocx-bus_type-probe-remove-methods.patch
> >...
> >  driver tree updates
> >...
> 
> This patch caused the following compile error:
> 
> <--  snip  -->
> 
> ...
>   CC      arch/ia64/sn/kernel/tiocx.o
> arch/ia64/sn/kernel/tiocx.c:151: error: 'cx_device_remove' undeclared here (not in a function)
> make[2]: *** [arch/ia64/sn/kernel/tiocx.o] Error 1
> 
> <--  snip  -->
> 
> 
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
> 
> --- linux-2.6.15-mm3/arch/ia64/sn/kernel/tiocx.c.old	2006-01-12 01:58:20.000000000 +0100
> +++ linux-2.6.15-mm3/arch/ia64/sn/kernel/tiocx.c	2006-01-12 01:58:35.000000000 +0100
> @@ -148,7 +148,7 @@
>  	.match = tiocx_match,
>  	.uevent = tiocx_uevent,
>  	.probe = cx_device_probe,
> -	.remove = cx_device_remove,
> +	.remove = cx_driver_remove,
>  };

Thanks, I've merged it into the original patch now.

greg k-h

Re: [-mm patch] fix arch/ia64/sn/kernel/tiocx.c compilation

[Greg KH]

On Thu, Jan 12, 2006 at 02:02:40AM +0100, Adrian Bunk wrote:
> On Wed, Jan 11, 2006 at 04:21:35AM -0800, Andrew Morton wrote:
> >...
> > Changes since 2.6.15-mm2:
> >...
> > +gregkh-driver-add-tiocx-bus_type-probe-remove-methods.patch
> >...
> >  driver tree updates
> >...
> 
> This patch caused the following compile error:
> 
> <--  snip  -->
> 
> ...
>   CC      arch/ia64/sn/kernel/tiocx.o
> arch/ia64/sn/kernel/tiocx.c:151: error: 'cx_device_remove' undeclared here (not in a function)
> make[2]: *** [arch/ia64/sn/kernel/tiocx.o] Error 1
> 
> <--  snip  -->
> 
> 
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
> 
> --- linux-2.6.15-mm3/arch/ia64/sn/kernel/tiocx.c.old	2006-01-12 01:58:20.000000000 +0100
> +++ linux-2.6.15-mm3/arch/ia64/sn/kernel/tiocx.c	2006-01-12 01:58:35.000000000 +0100
> @@ -148,7 +148,7 @@
>  	.match = tiocx_match,
>  	.uevent = tiocx_uevent,
>  	.probe = cx_device_probe,
> -	.remove = cx_device_remove,
> +	.remove = cx_driver_remove,
>  };

Thanks, I've merged it into the original patch now.

greg k-h

Re: 2.6.15-mm3

[Reuben Farrelly]

On 12/01/2006 1:21 a.m., Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/
> 
> - New config options (VMSPLIT_*) to permit non-standard user/kernel
>   splitting on x86.  Needs testing please.
> 
> - Lots of updates to the USB, PCI, driver and I2C trees.  This is usually a
>   worry.
> 
> - Multiblock allocation speedup for ext3.  This is only used by direct-IO at
>   present.
> 
> - Reminder: -mm kernel commit activity can be reviewed by subscribing to the
>   mm-commits mailing list.
> 
>   echo "subscribe mm-commits" | mail marordomo@vger.kernel.org
> 
> - If you hit a bug in -mm and it's not obvious which patch caused it, it is
>   most valuable if you can perform a bisection search to identify which patch
>   introduced the bug.  Instructions for this process are at
> 
> 	http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
> 
>   But beware that this process takes some time (around ten rebuilds and
>   reboots), so consider reporting the bug first and if we cannot immediately
>   identify the faulty patch, then perform the bisection search.

I'm not sure if this is new to -mm3, but it's the first time I have seen it.

The sequence of events leading up to this was to reboot the machine, it came up 
and crashed:

Call Trace:
  [<c0103c5d>] show_stack+0x9b/0xc0
  [<c0103de4>] show_registers+0x162/0x1e7
  [<c0103f8f>] die+0x126/0x231
  [<c01140db>] do_page_fault+0x271/0x5b9
  [<c01037df>] error_code+0x4f/0x54
  [<c023cabd>] class_device_del+0xa3/0x156
  [<c023cb7b>] class_device_unregister+0xb/0x15
  [<c0255dbf>] scsi_remove_host+0xb4/0xef

See the previous bug report about this one that I just posted in it's original 
thread.  I had to reset the box to clear that one.

After rebooting, now a new problem:

Linux version 2.6.15-mm3 (root@tornado.reub.net) (gcc version 4.1.0 20060106 
(Red Hat 4.1.0-0.14)) #4 SMP Thu Jan 12 16:26:28 NZDT 2006
BIOS-provided physical RAM map:
  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
  BIOS-e820: 00000000000e6000 - 0000000000100000 (reserved)
  BIOS-e820: 0000000000100000 - 000000003fe2f800 (usable)
  BIOS-e820: 000000003fe2f800 - 000000003fe3f8e3 (ACPI NVS)
  BIOS-e820: 000000003ff2f800 - 000000003ff30000 (ACPI NVS)
  BIOS-e820: 000000003ff30000 - 000000003ff40000 (ACPI data)
  BIOS-e820: 000000003ff40000 - 000000003fff0000 (ACPI NVS)
  BIOS-e820: 000000003fff0000 - 0000000040000000 (reserved)
  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
  BIOS-e820: 00000000fed13000 - 00000000fed1a000 (reserved)
  BIOS-e820: 00000000fed1c000 - 00000000feda0000 (reserved)
126MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000ff780
DMI 2.3 present.
ACPI: PM-Timer IO Port: 0x408
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:3 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:3 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] 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 50000000 (gap: 40000000:a0000000)
Detected 2800.156 MHz processor.
Built 1 zonelists
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Kernel command line: ro root=/dev/md0 panic=60 console=ttyS0,57600
CPU 0 irqstacks, hard=c040a000 soft=c0408000
PID hash table entries: 4096 (order: 12, 65536 bytes)
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: 1033552k/1046716k available (2161k kernel code, 12500k reserved, 713k 
data, 204k init, 129212k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 5607.77 BogoMIPS (lpj=11215558)
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
mtrr: v2.0 (20020519)
Checking 'hlt' instruction... OK.
CPU0: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 04
Booting processor 1/1 eip 2000
CPU 1 irqstacks, hard=c040b000 soft=c0409000
Initializing CPU#1
Calibrating delay using timer specific routine.. 5600.66 BogoMIPS (lpj=11201332)
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 04
Total of 2 processors activated (11208.44 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
checking TSC synchronization across 2 CPUs: passed.
Brought up 2 CPUs
migration_cost=144
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using MMCONFIG
ACPI: Subsystem revision 20051216
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: Transparent bridge - 0000:00:1e.0
ACPI: Power Resource [URP1] (off)
ACPI: Power Resource [FDDP] (off)
ACPI: Power Resource [LPTP] (off)
ACPI: Power Resource [URP2] (off)
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 [LNKG] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (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
PCI: Bridge: 0000:00:01.0
   IO window: disabled.
   MEM window: ffa00000-ffafffff
   PREFETCH window: fdf00000-fdffffff
PCI: Bridge: 0000:00:1c.0
   IO window: disabled.
   MEM window: ff600000-ff6fffff
   PREFETCH window: fdb00000-fdbfffff
PCI: Bridge: 0000:00:1c.1
   IO window: a000-afff
   MEM window: ff700000-ff7fffff
   PREFETCH window: fdc00000-fdcfffff
PCI: Bridge: 0000:00:1c.2
   IO window: disabled.
   MEM window: ff800000-ff8fffff
   PREFETCH window: fdd00000-fddfffff
PCI: Bridge: 0000:00:1c.3
   IO window: disabled.
   MEM window: ff900000-ff9fffff
   PREFETCH window: fde00000-fdefffff
PCI: Bridge: 0000:00:1e.0
   IO window: b000-bfff
   MEM window: ff500000-ff5fffff
   PREFETCH window: fe000000-fe7fffff
ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 169
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 177
PCI: Enabling device 0000:00:1c.1 (0106 -> 0107)
ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 16 (level, low) -> IRQ 169
ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 185
ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 193
Machine check exception polling timer started.
highmem bounce pool size: 64 pages
Initializing Cryptographic API
io scheduler noop registered<6>Time: tsc clocksource has been installed.

io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 169
assign_interrupt_mode Found MSI capability
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 177
assign_interrupt_mode Found MSI capability
ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 16 (level, low) -> IRQ 169
assign_interrupt_mode Found MSI capability
ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 185
assign_interrupt_mode Found MSI capability
ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 193
assign_interrupt_mode Found MSI capability
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [PWRB]
ACPI: Processor [CPU1] (supports 8 throttling states)
ACPI: Processor [CPU2] (supports 8 throttling states)
Real Time Clock Driver v1.12ac
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 $ 4 ports, IRQ sharing enabled
ÿserial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ACPI: PCI Interrupt 0000:06:02.0[A] -> GSI 18 (level, low) -> IRQ 185
0000:06:02.0: ttyS1 at I/O 0xbc00 (irq = 185) is a 16550A
0000:06:02.0: ttyS2 at I/O 0xbc08 (irq = 185) is a 16550A
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 193
ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 4 ports 1.5 Gbps 0xf impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq led slum part
ata1: SATA max UDMA/133 cmd 0xF8804D00 ctl 0x0 bmdma 0x0 irq 50
ata2: SATA max UDMA/133 cmd 0xF8804D80 ctl 0x0 bmdma 0x0 irq 50
ata3: SATA max UDMA/133 cmd 0xF8804E00 ctl 0x0 bmdma 0x0 irq 50
ata4: SATA max UDMA/133 cmd 0xF8804E80 ctl 0x0 bmdma 0x0 irq 50
ata1: SATA link up 1.5 Gbps (SStatus 113)
ata1 is slow to respond, please be patient
ata1 failed to respond (30 secs)
scsi0 : ahci
ata2: SATA link up 1.5 Gbps (SStatus 113)
ata2 is slow to respond, please be patient
ata2 failed to respond (30 secs)
scsi1 : ahci
ata3: SATA link up 1.5 Gbps (SStatus 113)
ata3 is slow to respond, please be patient
ata3 failed to respond (30 secs)
scsi2 : ahci
ata4: SATA link down (SStatus 0)
scsi3 : ahci
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 58
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: irq 58, io mem 0xff4ff800
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 58
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 58, io base 0x0000cc00
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 193
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 193, io base 0x0000d000
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 185
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 185, io base 0x0000d400
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 169
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: irq 169, io base 0x0000d800
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
irq 193: nobody cared (try booting with the "irqpoll" option)
  [<c01041d9>] dump_stack+0x17/0x19
  [<c0139f47>] __report_bad_irq+0x27/0x83
  [<c013a021>] note_interrupt+0x7e/0x21d
  [<c0139af4>] __do_IRQ+0xd3/0xef
  [<c0105038>] do_IRQ+0x3d/0x57
  =======================
  [<c0103686>] common_interrupt+0x1a/0x20
  [<c0101bc4>] cpu_idle+0x63/0x78
  [<c0100615>] rest_init+0x23/0x2e
  [<c03d070f>] start_kernel+0x2ca/0x34b
  [<c0100210>] 0xc0100210
handlers:
[<c027017e>] (usb_hcd_irq+0x0/0x56)
Disabling IRQ #193
usb 5-1: new full speed USB device using uhci_hcd and address 2
usb 5-1: configuration #1 chosen from 1 choice
usb 5-2: new full speed USB device using uhci_hcd and address 3
usb 5-2: configuration #1 chosen from 1 choice
hub 5-2:1.0: USB hub found
hub 5-2:1.0: 4 ports detected
usb 5-2.1: new low speed USB device using uhci_hcd and address 4
usb 5-2.1: configuration #1 chosen from 1 choice
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver libusual
usbcore: registered new driver hiddev
input: Belkin Components Belkin OmniView KVM Switch as /class/input/input0
input: USB HID v1.00 Keyboard [Belkin Components Belkin OmniView KVM Switch] on 
usb-0000:00:1d.3-2.1
input: Belkin Components Belkin OmniView KVM Switch as /class/input/input1
input: USB HID v1.00 Mouse [Belkin Components Belkin OmniView KVM Switch] on 
usb-0000:00:1d.3-2.1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
mice: PS/2 mouse device common for all mice
md: raid1 personality registered for level 1
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
IPv4 over IPv4 tunneling driver
ip_conntrack version 2.4 (8177 buckets, 65416 max) - 212 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>. 
http://snowman.net/projects/ipt_recent/
arp_tables: (C) 2002 David S. Miller
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available
Starting balanced_irq
Using IPI Shortcut mode
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 
2, size 4096)
ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 
16, size 4096)
EXT3-fs: unable to read superblock
EXT2-fs: unable to read superblock
isofs_fill_super: bread failed, dev=md0, iso_blknum=16, block=32
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0)

Then cold booted/power cycled again, and it came up OK (and it's still up).

I reported a bug in November about SATA timing out in a similar fashion when 
booted on an SMP kernel but with 'nosmp' on the kernel command line, it had 
similar symptoms FWIW, and may or may not be something related.

Reuben

Re: 2.6.15-mm3

[Andrew Morton]

Reuben Farrelly <reuben-lkml-MwA23MxOyI4@public.gmane.org> wrote:
>
> 
> 
> On 12/01/2006 1:21 a.m., Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/
> > 
> > - New config options (VMSPLIT_*) to permit non-standard user/kernel
> >   splitting on x86.  Needs testing please.
> > 
> > - Lots of updates to the USB, PCI, driver and I2C trees.  This is usually a
> >   worry.
> > 
> > - Multiblock allocation speedup for ext3.  This is only used by direct-IO at
> >   present.
> > 
> > - Reminder: -mm kernel commit activity can be reviewed by subscribing to the
> >   mm-commits mailing list.
> > 
> >   echo "subscribe mm-commits" | mail marordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > 
> > - If you hit a bug in -mm and it's not obvious which patch caused it, it is
> >   most valuable if you can perform a bisection search to identify which patch
> >   introduced the bug.  Instructions for this process are at
> > 
> > 	http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
> > 
> >   But beware that this process takes some time (around ten rebuilds and
> >   reboots), so consider reporting the bug first and if we cannot immediately
> >   identify the faulty patch, then perform the bisection search.
> 
> I'm not sure if this is new to -mm3, but it's the first time I have seen it.
> 
> The sequence of events leading up to this was to reboot the machine, it came up 
> and crashed:
> 
> Call Trace:
>   [<c0103c5d>] show_stack+0x9b/0xc0
>   [<c0103de4>] show_registers+0x162/0x1e7
>   [<c0103f8f>] die+0x126/0x231
>   [<c01140db>] do_page_fault+0x271/0x5b9
>   [<c01037df>] error_code+0x4f/0x54
>   [<c023cabd>] class_device_del+0xa3/0x156
>   [<c023cb7b>] class_device_unregister+0xb/0x15
>   [<c0255dbf>] scsi_remove_host+0xb4/0xef
> 

There's some trace missing here.  I assume it's the same ata_device_add()
thing.

> uhci_hcd 0000:00:1d.2: irq 185, io base 0x0000d400
> usb usb4: configuration #1 chosen from 1 choice
> hub 4-0:1.0: USB hub found
> hub 4-0:1.0: 2 ports detected
> ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 169
> uhci_hcd 0000:00:1d.3: UHCI Host Controller
> uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
> uhci_hcd 0000:00:1d.3: irq 169, io base 0x0000d800
> usb usb5: configuration #1 chosen from 1 choice
> hub 5-0:1.0: USB hub found
> hub 5-0:1.0: 2 ports detected
> Initializing USB Mass Storage driver...
> irq 193: nobody cared (try booting with the "irqpoll" option)
>   [<c01041d9>] dump_stack+0x17/0x19
>   [<c0139f47>] __report_bad_irq+0x27/0x83
>   [<c013a021>] note_interrupt+0x7e/0x21d
>   [<c0139af4>] __do_IRQ+0xd3/0xef
>   [<c0105038>] do_IRQ+0x3d/0x57
>   =======================
>   [<c0103686>] common_interrupt+0x1a/0x20
>   [<c0101bc4>] cpu_idle+0x63/0x78
>   [<c0100615>] rest_init+0x23/0x2e
>   [<c03d070f>] start_kernel+0x2ca/0x34b
>   [<c0100210>] 0xc0100210
> handlers:
> [<c027017e>] (usb_hcd_irq+0x0/0x56)
> Disabling IRQ #193

USB lost its interrupt.  Could be USB, more likely ACPI.

> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 
> 2, size 4096)
> ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 
> 16, size 4096)
> EXT3-fs: unable to read superblock
> EXT2-fs: unable to read superblock
> isofs_fill_super: bread failed, dev=md0, iso_blknum=16, block=32
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0)
> 

Looks like RAID0 keeled over.
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.15-mm3

[Andrew Morton]

Reuben Farrelly <reuben-lkml@reub.net> wrote:
>
> 
> 
> On 12/01/2006 1:21 a.m., Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/
> > 
> > - New config options (VMSPLIT_*) to permit non-standard user/kernel
> >   splitting on x86.  Needs testing please.
> > 
> > - Lots of updates to the USB, PCI, driver and I2C trees.  This is usually a
> >   worry.
> > 
> > - Multiblock allocation speedup for ext3.  This is only used by direct-IO at
> >   present.
> > 
> > - Reminder: -mm kernel commit activity can be reviewed by subscribing to the
> >   mm-commits mailing list.
> > 
> >   echo "subscribe mm-commits" | mail marordomo@vger.kernel.org
> > 
> > - If you hit a bug in -mm and it's not obvious which patch caused it, it is
> >   most valuable if you can perform a bisection search to identify which patch
> >   introduced the bug.  Instructions for this process are at
> > 
> > 	http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
> > 
> >   But beware that this process takes some time (around ten rebuilds and
> >   reboots), so consider reporting the bug first and if we cannot immediately
> >   identify the faulty patch, then perform the bisection search.
> 
> I'm not sure if this is new to -mm3, but it's the first time I have seen it.
> 
> The sequence of events leading up to this was to reboot the machine, it came up 
> and crashed:
> 
> Call Trace:
>   [<c0103c5d>] show_stack+0x9b/0xc0
>   [<c0103de4>] show_registers+0x162/0x1e7
>   [<c0103f8f>] die+0x126/0x231
>   [<c01140db>] do_page_fault+0x271/0x5b9
>   [<c01037df>] error_code+0x4f/0x54
>   [<c023cabd>] class_device_del+0xa3/0x156
>   [<c023cb7b>] class_device_unregister+0xb/0x15
>   [<c0255dbf>] scsi_remove_host+0xb4/0xef
> 

There's some trace missing here.  I assume it's the same ata_device_add()
thing.

> uhci_hcd 0000:00:1d.2: irq 185, io base 0x0000d400
> usb usb4: configuration #1 chosen from 1 choice
> hub 4-0:1.0: USB hub found
> hub 4-0:1.0: 2 ports detected
> ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 169
> uhci_hcd 0000:00:1d.3: UHCI Host Controller
> uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
> uhci_hcd 0000:00:1d.3: irq 169, io base 0x0000d800
> usb usb5: configuration #1 chosen from 1 choice
> hub 5-0:1.0: USB hub found
> hub 5-0:1.0: 2 ports detected
> Initializing USB Mass Storage driver...
> irq 193: nobody cared (try booting with the "irqpoll" option)
>   [<c01041d9>] dump_stack+0x17/0x19
>   [<c0139f47>] __report_bad_irq+0x27/0x83
>   [<c013a021>] note_interrupt+0x7e/0x21d
>   [<c0139af4>] __do_IRQ+0xd3/0xef
>   [<c0105038>] do_IRQ+0x3d/0x57
>   =======================
>   [<c0103686>] common_interrupt+0x1a/0x20
>   [<c0101bc4>] cpu_idle+0x63/0x78
>   [<c0100615>] rest_init+0x23/0x2e
>   [<c03d070f>] start_kernel+0x2ca/0x34b
>   [<c0100210>] 0xc0100210
> handlers:
> [<c027017e>] (usb_hcd_irq+0x0/0x56)
> Disabling IRQ #193

USB lost its interrupt.  Could be USB, more likely ACPI.

> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 
> 2, size 4096)
> ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 
> 16, size 4096)
> EXT3-fs: unable to read superblock
> EXT2-fs: unable to read superblock
> isofs_fill_super: bread failed, dev=md0, iso_blknum=16, block=32
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0)
> 

Looks like RAID0 keeled over.

Re: 2.6.15-mm3

[Reuben Farrelly]

On 12/01/2006 5:33 p.m., Andrew Morton wrote:
> Reuben Farrelly <reuben-lkml-MwA23MxOyI4@public.gmane.org> wrote:
>>
>>
>> On 12/01/2006 1:21 a.m., Andrew Morton wrote:
>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/
>>>
>>> - New config options (VMSPLIT_*) to permit non-standard user/kernel
>>>   splitting on x86.  Needs testing please.
>>>
>>> - Lots of updates to the USB, PCI, driver and I2C trees.  This is usually a
>>>   worry.
>>>
>>> - Multiblock allocation speedup for ext3.  This is only used by direct-IO at
>>>   present.
>>>
>>> - Reminder: -mm kernel commit activity can be reviewed by subscribing to the
>>>   mm-commits mailing list.
>>>
>>>   echo "subscribe mm-commits" | mail marordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>>>
>>> - If you hit a bug in -mm and it's not obvious which patch caused it, it is
>>>   most valuable if you can perform a bisection search to identify which patch
>>>   introduced the bug.  Instructions for this process are at
>>>
>>> 	http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
>>>
>>>   But beware that this process takes some time (around ten rebuilds and
>>>   reboots), so consider reporting the bug first and if we cannot immediately
>>>   identify the faulty patch, then perform the bisection search.
>> I'm not sure if this is new to -mm3, but it's the first time I have seen it.
>>
>> The sequence of events leading up to this was to reboot the machine, it came up 
>> and crashed:
>>
>> Call Trace:
>>   [<c0103c5d>] show_stack+0x9b/0xc0
>>   [<c0103de4>] show_registers+0x162/0x1e7
>>   [<c0103f8f>] die+0x126/0x231
>>   [<c01140db>] do_page_fault+0x271/0x5b9
>>   [<c01037df>] error_code+0x4f/0x54
>>   [<c023cabd>] class_device_del+0xa3/0x156
>>   [<c023cb7b>] class_device_unregister+0xb/0x15
>>   [<c0255dbf>] scsi_remove_host+0xb4/0xef
>>
> 
> There's some trace missing here.  I assume it's the same ata_device_add()
> thing.

Correct.  I included it to suggest a possible link with the other ATA problems I 
am having and to show it's a separate report.

The important bit in this report was the SATA timing out - which it should not 
be doing.  There are three disks all hooked up and (most of the time) working. 
Box is locked in a cabinet so it's not like any hardware had mysteriously come 
loose or been bumped.

>> uhci_hcd 0000:00:1d.2: irq 185, io base 0x0000d400
>> usb usb4: configuration #1 chosen from 1 choice
>> hub 4-0:1.0: USB hub found
>> hub 4-0:1.0: 2 ports detected
>> ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 169
>> uhci_hcd 0000:00:1d.3: UHCI Host Controller
>> uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
>> uhci_hcd 0000:00:1d.3: irq 169, io base 0x0000d800
>> usb usb5: configuration #1 chosen from 1 choice
>> hub 5-0:1.0: USB hub found
>> hub 5-0:1.0: 2 ports detected
>> Initializing USB Mass Storage driver...
>> irq 193: nobody cared (try booting with the "irqpoll" option)
>>   [<c01041d9>] dump_stack+0x17/0x19
>>   [<c0139f47>] __report_bad_irq+0x27/0x83
>>   [<c013a021>] note_interrupt+0x7e/0x21d
>>   [<c0139af4>] __do_IRQ+0xd3/0xef
>>   [<c0105038>] do_IRQ+0x3d/0x57
>>   =======================
>>   [<c0103686>] common_interrupt+0x1a/0x20
>>   [<c0101bc4>] cpu_idle+0x63/0x78
>>   [<c0100615>] rest_init+0x23/0x2e
>>   [<c03d070f>] start_kernel+0x2ca/0x34b
>>   [<c0100210>] 0xc0100210
>> handlers:
>> [<c027017e>] (usb_hcd_irq+0x0/0x56)
>> Disabling IRQ #193
> 
> USB lost its interrupt.  Could be USB, more likely ACPI.
> 
>> md: Autodetecting RAID arrays.
>> md: autorun ...
>> md: ... autorun DONE.
>> ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 
>> 2, size 4096)
>> ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 
>> 16, size 4096)
>> EXT3-fs: unable to read superblock
>> EXT2-fs: unable to read superblock
>> isofs_fill_super: bread failed, dev=md0, iso_blknum=16, block=32
>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0)
>>
> 
> Looks like RAID0 keeled over.

md0 is the root partition, I assume because the SATA crapped out the box was 
unable to assemble the raid arrays, find root on md0 and so it panic'd.

reuben

-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.15-mm3

[Reuben Farrelly]

On 12/01/2006 5:33 p.m., Andrew Morton wrote:
> Reuben Farrelly <reuben-lkml@reub.net> wrote:
>>
>>
>> On 12/01/2006 1:21 a.m., Andrew Morton wrote:
>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/
>>>
>>> - New config options (VMSPLIT_*) to permit non-standard user/kernel
>>>   splitting on x86.  Needs testing please.
>>>
>>> - Lots of updates to the USB, PCI, driver and I2C trees.  This is usually a
>>>   worry.
>>>
>>> - Multiblock allocation speedup for ext3.  This is only used by direct-IO at
>>>   present.
>>>
>>> - Reminder: -mm kernel commit activity can be reviewed by subscribing to the
>>>   mm-commits mailing list.
>>>
>>>   echo "subscribe mm-commits" | mail marordomo@vger.kernel.org
>>>
>>> - If you hit a bug in -mm and it's not obvious which patch caused it, it is
>>>   most valuable if you can perform a bisection search to identify which patch
>>>   introduced the bug.  Instructions for this process are at
>>>
>>> 	http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
>>>
>>>   But beware that this process takes some time (around ten rebuilds and
>>>   reboots), so consider reporting the bug first and if we cannot immediately
>>>   identify the faulty patch, then perform the bisection search.
>> I'm not sure if this is new to -mm3, but it's the first time I have seen it.
>>
>> The sequence of events leading up to this was to reboot the machine, it came up 
>> and crashed:
>>
>> Call Trace:
>>   [<c0103c5d>] show_stack+0x9b/0xc0
>>   [<c0103de4>] show_registers+0x162/0x1e7
>>   [<c0103f8f>] die+0x126/0x231
>>   [<c01140db>] do_page_fault+0x271/0x5b9
>>   [<c01037df>] error_code+0x4f/0x54
>>   [<c023cabd>] class_device_del+0xa3/0x156
>>   [<c023cb7b>] class_device_unregister+0xb/0x15
>>   [<c0255dbf>] scsi_remove_host+0xb4/0xef
>>
> 
> There's some trace missing here.  I assume it's the same ata_device_add()
> thing.

Correct.  I included it to suggest a possible link with the other ATA problems I 
am having and to show it's a separate report.

The important bit in this report was the SATA timing out - which it should not 
be doing.  There are three disks all hooked up and (most of the time) working. 
Box is locked in a cabinet so it's not like any hardware had mysteriously come 
loose or been bumped.

>> uhci_hcd 0000:00:1d.2: irq 185, io base 0x0000d400
>> usb usb4: configuration #1 chosen from 1 choice
>> hub 4-0:1.0: USB hub found
>> hub 4-0:1.0: 2 ports detected
>> ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 169
>> uhci_hcd 0000:00:1d.3: UHCI Host Controller
>> uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
>> uhci_hcd 0000:00:1d.3: irq 169, io base 0x0000d800
>> usb usb5: configuration #1 chosen from 1 choice
>> hub 5-0:1.0: USB hub found
>> hub 5-0:1.0: 2 ports detected
>> Initializing USB Mass Storage driver...
>> irq 193: nobody cared (try booting with the "irqpoll" option)
>>   [<c01041d9>] dump_stack+0x17/0x19
>>   [<c0139f47>] __report_bad_irq+0x27/0x83
>>   [<c013a021>] note_interrupt+0x7e/0x21d
>>   [<c0139af4>] __do_IRQ+0xd3/0xef
>>   [<c0105038>] do_IRQ+0x3d/0x57
>>   =======================
>>   [<c0103686>] common_interrupt+0x1a/0x20
>>   [<c0101bc4>] cpu_idle+0x63/0x78
>>   [<c0100615>] rest_init+0x23/0x2e
>>   [<c03d070f>] start_kernel+0x2ca/0x34b
>>   [<c0100210>] 0xc0100210
>> handlers:
>> [<c027017e>] (usb_hcd_irq+0x0/0x56)
>> Disabling IRQ #193
> 
> USB lost its interrupt.  Could be USB, more likely ACPI.
> 
>> md: Autodetecting RAID arrays.
>> md: autorun ...
>> md: ... autorun DONE.
>> ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 
>> 2, size 4096)
>> ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 
>> 16, size 4096)
>> EXT3-fs: unable to read superblock
>> EXT2-fs: unable to read superblock
>> isofs_fill_super: bread failed, dev=md0, iso_blknum=16, block=32
>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0)
>>
> 
> Looks like RAID0 keeled over.

md0 is the root partition, I assume because the SATA crapped out the box was 
unable to assemble the raid arrays, find root on md0 and so it panic'd.

reuben

Re: 2.6.15-mm3 [USB lost interrupt bug]

[Reuben Farrelly]

On 12/01/2006 5:33 p.m., Andrew Morton wrote:

>> hub 5-0:1.0: USB hub found
>> hub 5-0:1.0: 2 ports detected
>> Initializing USB Mass Storage driver...
>> irq 193: nobody cared (try booting with the "irqpoll" option)
>>   [<c01041d9>] dump_stack+0x17/0x19
>>   [<c0139f47>] __report_bad_irq+0x27/0x83
>>   [<c013a021>] note_interrupt+0x7e/0x21d
>>   [<c0139af4>] __do_IRQ+0xd3/0xef
>>   [<c0105038>] do_IRQ+0x3d/0x57
>>   =======================
>>   [<c0103686>] common_interrupt+0x1a/0x20
>>   [<c0101bc4>] cpu_idle+0x63/0x78
>>   [<c0100615>] rest_init+0x23/0x2e
>>   [<c03d070f>] start_kernel+0x2ca/0x34b
>>   [<c0100210>] 0xc0100210
>> handlers:
>> [<c027017e>] (usb_hcd_irq+0x0/0x56)
>> Disabling IRQ #193
> 
> USB lost its interrupt.  Could be USB, more likely ACPI.

I've seen this one happen nearly every boot since then including bootups that 
are otherwise OK (no oopses), so it's probably worth more looking into rather 
than being written off as a 'once off':

uhci_hcd 0000:00:1d.3: Unlink after no-IRQ?  Controller is probably using the 
wrong IRQ.

Details:

dmesg-

ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: irq 169, io base 0x0000d800


lspci -vv

00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #4 (rev 03) (prog-if 00 [UHCI])
         Subsystem: Intel Corporation Unknown device 4356
         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
         Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Interrupt: pin D routed to IRQ 169
         Region 4: I/O ports at d800 [size=32]


It's a new regression to -mm3.

For the ACPI people - I can't test with ACPI off because the machine won't boot 
without ACPI :(  [see 
http://www.ussg.iu.edu/hypermail/linux/kernel/0601.1/0044.html for what happens 
with acpi=off].
I'm not even sure if inability to boot with acpi=off is a bug or not - would 
appreciate if someone can let me know.

reuben
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.15-mm3 [USB lost interrupt bug]

[Reuben Farrelly]

On 12/01/2006 5:33 p.m., Andrew Morton wrote:

>> hub 5-0:1.0: USB hub found
>> hub 5-0:1.0: 2 ports detected
>> Initializing USB Mass Storage driver...
>> irq 193: nobody cared (try booting with the "irqpoll" option)
>>   [<c01041d9>] dump_stack+0x17/0x19
>>   [<c0139f47>] __report_bad_irq+0x27/0x83
>>   [<c013a021>] note_interrupt+0x7e/0x21d
>>   [<c0139af4>] __do_IRQ+0xd3/0xef
>>   [<c0105038>] do_IRQ+0x3d/0x57
>>   =======================
>>   [<c0103686>] common_interrupt+0x1a/0x20
>>   [<c0101bc4>] cpu_idle+0x63/0x78
>>   [<c0100615>] rest_init+0x23/0x2e
>>   [<c03d070f>] start_kernel+0x2ca/0x34b
>>   [<c0100210>] 0xc0100210
>> handlers:
>> [<c027017e>] (usb_hcd_irq+0x0/0x56)
>> Disabling IRQ #193
> 
> USB lost its interrupt.  Could be USB, more likely ACPI.

I've seen this one happen nearly every boot since then including bootups that 
are otherwise OK (no oopses), so it's probably worth more looking into rather 
than being written off as a 'once off':

uhci_hcd 0000:00:1d.3: Unlink after no-IRQ?  Controller is probably using the 
wrong IRQ.

Details:

dmesg-

ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: irq 169, io base 0x0000d800


lspci -vv

00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #4 (rev 03) (prog-if 00 [UHCI])
         Subsystem: Intel Corporation Unknown device 4356
         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
         Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Interrupt: pin D routed to IRQ 169
         Region 4: I/O ports at d800 [size=32]


It's a new regression to -mm3.

For the ACPI people - I can't test with ACPI off because the machine won't boot 
without ACPI :(  [see 
http://www.ussg.iu.edu/hypermail/linux/kernel/0601.1/0044.html for what happens 
with acpi=off].
I'm not even sure if inability to boot with acpi=off is a bug or not - would 
appreciate if someone can let me know.

reuben

Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Alan Stern]

On Thu, 12 Jan 2006, Reuben Farrelly wrote:

> >> Initializing USB Mass Storage driver...
> >> irq 193: nobody cared (try booting with the "irqpoll" option)

> >> handlers:
> >> [<c027017e>] (usb_hcd_irq+0x0/0x56)
> >> Disabling IRQ #193
> > 
> > USB lost its interrupt.  Could be USB, more likely ACPI.
> 
> I've seen this one happen nearly every boot since then including bootups that 
> are otherwise OK (no oopses), so it's probably worth more looking into rather 
> than being written off as a 'once off':
> 
> uhci_hcd 0000:00:1d.3: Unlink after no-IRQ?  Controller is probably using the 
> wrong IRQ.

> It's a new regression to -mm3.

Did the same IRQ get assigned to that controller in earlier kernel 
versions?

Alan Stern

-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Alan Stern]

On Thu, 12 Jan 2006, Reuben Farrelly wrote:

> >> Initializing USB Mass Storage driver...
> >> irq 193: nobody cared (try booting with the "irqpoll" option)

> >> handlers:
> >> [<c027017e>] (usb_hcd_irq+0x0/0x56)
> >> Disabling IRQ #193
> > 
> > USB lost its interrupt.  Could be USB, more likely ACPI.
> 
> I've seen this one happen nearly every boot since then including bootups that 
> are otherwise OK (no oopses), so it's probably worth more looking into rather 
> than being written off as a 'once off':
> 
> uhci_hcd 0000:00:1d.3: Unlink after no-IRQ?  Controller is probably using the 
> wrong IRQ.

> It's a new regression to -mm3.

Did the same IRQ get assigned to that controller in earlier kernel 
versions?

Alan Stern

Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Reuben Farrelly]

On 13/01/2006 4:53 a.m., Alan Stern wrote:
> On Thu, 12 Jan 2006, Reuben Farrelly wrote:
> 
>>>> Initializing USB Mass Storage driver...
>>>> irq 193: nobody cared (try booting with the "irqpoll" option)
> 
>>>> handlers:
>>>> [<c027017e>] (usb_hcd_irq+0x0/0x56)
>>>> Disabling IRQ #193
>>> USB lost its interrupt.  Could be USB, more likely ACPI.
>> I've seen this one happen nearly every boot since then including bootups that 
>> are otherwise OK (no oopses), so it's probably worth more looking into rather 
>> than being written off as a 'once off':
>>
>> uhci_hcd 0000:00:1d.3: Unlink after no-IRQ?  Controller is probably using the 
>> wrong IRQ.
> 
>> It's a new regression to -mm3.
> 
> Did the same IRQ get assigned to that controller in earlier kernel 
> versions?
> 
> Alan Stern

Hi Alan,

If it's any use, here's some simply and easy-to-get information which may even 
be what you are looking for:

[root@tornado dovecot]# uname -a
Linux tornado.reub.net 2.6.15-mm1 #1 SMP Sun Jan 8 03:42:25 NZDT 2006 i686 i686 
i386 GNU/Linux
[root@tornado ~]# cat /proc/interrupts
            CPU0       CPU1
   0:   21638510          0    IO-APIC-edge  timer
   4:        356          0    IO-APIC-edge  serial
   8:          1          0    IO-APIC-edge  rtc
   9:          0          0   IO-APIC-level  acpi
  14:          1          0    IO-APIC-edge  ide0
  50:          3          0   IO-APIC-level  ehci_hcd:usb1, uhci_hcd:usb2
169:        120          0   IO-APIC-level  uhci_hcd:usb5
177:    2837992          0   IO-APIC-level  sky2
185:      61450          0   IO-APIC-level  uhci_hcd:usb4, serial
193:    4722447          0   IO-APIC-level  libata, uhci_hcd:usb3
NMI:          0          0
LOC:   21638418   21638338
ERR:          0
MIS:          0
[root@tornado ~]#
[root@tornado ~]# lspci
00:00.0 Host bridge: Intel Corporation 925X/XE Memory Controller Hub (rev 04)
00:01.0 PCI bridge: Intel Corporation 925X/XE PCI Express Root Port (rev 04)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI 
Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI 
Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI 
Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI 
Express Port 4 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3)
00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface 
Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE 
Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801FR/FRW (ICH6R/ICH6RW) SATA 
Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus 
Controller (rev 03)
04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8050 PCI-E ASF 
Gigabit Ethernet Controller (rev 17)
06:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA 2064W [Millennium] 
(rev 01)
06:02.0 Serial controller: Timedia Technology Co Ltd PCI2S550 (Dual 16550 UART) 
(rev 01)
[root@tornado ~]#

I guess this looks like it was assigned the same IRQ ?

Currently booted into -mm1 which is OK and hasn't shown any nasty symptoms yet.

Reuben




-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Reuben Farrelly]

On 13/01/2006 4:53 a.m., Alan Stern wrote:
> On Thu, 12 Jan 2006, Reuben Farrelly wrote:
> 
>>>> Initializing USB Mass Storage driver...
>>>> irq 193: nobody cared (try booting with the "irqpoll" option)
> 
>>>> handlers:
>>>> [<c027017e>] (usb_hcd_irq+0x0/0x56)
>>>> Disabling IRQ #193
>>> USB lost its interrupt.  Could be USB, more likely ACPI.
>> I've seen this one happen nearly every boot since then including bootups that 
>> are otherwise OK (no oopses), so it's probably worth more looking into rather 
>> than being written off as a 'once off':
>>
>> uhci_hcd 0000:00:1d.3: Unlink after no-IRQ?  Controller is probably using the 
>> wrong IRQ.
> 
>> It's a new regression to -mm3.
> 
> Did the same IRQ get assigned to that controller in earlier kernel 
> versions?
> 
> Alan Stern

Hi Alan,

If it's any use, here's some simply and easy-to-get information which may even 
be what you are looking for:

[root@tornado dovecot]# uname -a
Linux tornado.reub.net 2.6.15-mm1 #1 SMP Sun Jan 8 03:42:25 NZDT 2006 i686 i686 
i386 GNU/Linux
[root@tornado ~]# cat /proc/interrupts
            CPU0       CPU1
   0:   21638510          0    IO-APIC-edge  timer
   4:        356          0    IO-APIC-edge  serial
   8:          1          0    IO-APIC-edge  rtc
   9:          0          0   IO-APIC-level  acpi
  14:          1          0    IO-APIC-edge  ide0
  50:          3          0   IO-APIC-level  ehci_hcd:usb1, uhci_hcd:usb2
169:        120          0   IO-APIC-level  uhci_hcd:usb5
177:    2837992          0   IO-APIC-level  sky2
185:      61450          0   IO-APIC-level  uhci_hcd:usb4, serial
193:    4722447          0   IO-APIC-level  libata, uhci_hcd:usb3
NMI:          0          0
LOC:   21638418   21638338
ERR:          0
MIS:          0
[root@tornado ~]#
[root@tornado ~]# lspci
00:00.0 Host bridge: Intel Corporation 925X/XE Memory Controller Hub (rev 04)
00:01.0 PCI bridge: Intel Corporation 925X/XE PCI Express Root Port (rev 04)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI 
Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI 
Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI 
Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI 
Express Port 4 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3)
00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface 
Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE 
Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801FR/FRW (ICH6R/ICH6RW) SATA 
Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus 
Controller (rev 03)
04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8050 PCI-E ASF 
Gigabit Ethernet Controller (rev 17)
06:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA 2064W [Millennium] 
(rev 01)
06:02.0 Serial controller: Timedia Technology Co Ltd PCI2S550 (Dual 16550 UART) 
(rev 01)
[root@tornado ~]#

I guess this looks like it was assigned the same IRQ ?

Currently booted into -mm1 which is OK and hasn't shown any nasty symptoms yet.

Reuben

Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Alan Stern]

On Mon, 16 Jan 2006, Reuben Farrelly wrote:

> On 13/01/2006 4:53 a.m., Alan Stern wrote:
> > On Thu, 12 Jan 2006, Reuben Farrelly wrote:
> > 
> >>>> Initializing USB Mass Storage driver...
> >>>> irq 193: nobody cared (try booting with the "irqpoll" option)
> > 
> >>>> handlers:
> >>>> [<c027017e>] (usb_hcd_irq+0x0/0x56)
> >>>> Disabling IRQ #193
> >>> USB lost its interrupt.  Could be USB, more likely ACPI.
> >> I've seen this one happen nearly every boot since then including bootups that 
> >> are otherwise OK (no oopses), so it's probably worth more looking into rather 
> >> than being written off as a 'once off':
> >>
> >> uhci_hcd 0000:00:1d.3: Unlink after no-IRQ?  Controller is probably using the 
> >> wrong IRQ.

Note the PCI ID is 1d.3 and the IRQ is 193.

> Hi Alan,
> 
> If it's any use, here's some simply and easy-to-get information which may even 
> be what you are looking for:
> 
> [root@tornado dovecot]# uname -a
> Linux tornado.reub.net 2.6.15-mm1 #1 SMP Sun Jan 8 03:42:25 NZDT 2006 i686 i686 
> i386 GNU/Linux
> [root@tornado ~]# cat /proc/interrupts
>             CPU0       CPU1
>    0:   21638510          0    IO-APIC-edge  timer
>    4:        356          0    IO-APIC-edge  serial
>    8:          1          0    IO-APIC-edge  rtc
>    9:          0          0   IO-APIC-level  acpi
>   14:          1          0    IO-APIC-edge  ide0
>   50:          3          0   IO-APIC-level  ehci_hcd:usb1, uhci_hcd:usb2
> 169:        120          0   IO-APIC-level  uhci_hcd:usb5
> 177:    2837992          0   IO-APIC-level  sky2
> 185:      61450          0   IO-APIC-level  uhci_hcd:usb4, serial
> 193:    4722447          0   IO-APIC-level  libata, uhci_hcd:usb3

Note that in the earlier kernel, IRQ 193 is assigned to usb3.  That's the 
second UHCI controller, since usb1 is EHCI.

> [root@tornado ~]# lspci

> 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
> USB UHCI #1 (rev 03)
> 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
> USB UHCI #2 (rev 03)
> 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
> USB UHCI #3 (rev 03)
> 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
> USB UHCI #4 (rev 03)
> 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
> USB2 EHCI Controller (rev 03)

Note that 1d.3 is the fourth UHCI controller; the second is 1d.1.

> I guess this looks like it was assigned the same IRQ ?

I don't think so.  To be certain you'd have to check the boot-up log and
verify that 1d.1 is usb3 and 1d.3 is usb5.

>From the information presented here, it looks like -mm1 correctly routes
the 1d.1 controller to IRQ 193 and the 1d.3 controller to IRQ 169, whereas
-mm3 incorrectly routes the 1d.3 controller to IRQ 193.  That would make 
it an ACPI problem.

Alan Stern

-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Alan Stern]

On Mon, 16 Jan 2006, Reuben Farrelly wrote:

> On 13/01/2006 4:53 a.m., Alan Stern wrote:
> > On Thu, 12 Jan 2006, Reuben Farrelly wrote:
> > 
> >>>> Initializing USB Mass Storage driver...
> >>>> irq 193: nobody cared (try booting with the "irqpoll" option)
> > 
> >>>> handlers:
> >>>> [<c027017e>] (usb_hcd_irq+0x0/0x56)
> >>>> Disabling IRQ #193
> >>> USB lost its interrupt.  Could be USB, more likely ACPI.
> >> I've seen this one happen nearly every boot since then including bootups that 
> >> are otherwise OK (no oopses), so it's probably worth more looking into rather 
> >> than being written off as a 'once off':
> >>
> >> uhci_hcd 0000:00:1d.3: Unlink after no-IRQ?  Controller is probably using the 
> >> wrong IRQ.

Note the PCI ID is 1d.3 and the IRQ is 193.

> Hi Alan,
> 
> If it's any use, here's some simply and easy-to-get information which may even 
> be what you are looking for:
> 
> [root@tornado dovecot]# uname -a
> Linux tornado.reub.net 2.6.15-mm1 #1 SMP Sun Jan 8 03:42:25 NZDT 2006 i686 i686 
> i386 GNU/Linux
> [root@tornado ~]# cat /proc/interrupts
>             CPU0       CPU1
>    0:   21638510          0    IO-APIC-edge  timer
>    4:        356          0    IO-APIC-edge  serial
>    8:          1          0    IO-APIC-edge  rtc
>    9:          0          0   IO-APIC-level  acpi
>   14:          1          0    IO-APIC-edge  ide0
>   50:          3          0   IO-APIC-level  ehci_hcd:usb1, uhci_hcd:usb2
> 169:        120          0   IO-APIC-level  uhci_hcd:usb5
> 177:    2837992          0   IO-APIC-level  sky2
> 185:      61450          0   IO-APIC-level  uhci_hcd:usb4, serial
> 193:    4722447          0   IO-APIC-level  libata, uhci_hcd:usb3

Note that in the earlier kernel, IRQ 193 is assigned to usb3.  That's the 
second UHCI controller, since usb1 is EHCI.

> [root@tornado ~]# lspci

> 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
> USB UHCI #1 (rev 03)
> 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
> USB UHCI #2 (rev 03)
> 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
> USB UHCI #3 (rev 03)
> 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
> USB UHCI #4 (rev 03)
> 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
> USB2 EHCI Controller (rev 03)

Note that 1d.3 is the fourth UHCI controller; the second is 1d.1.

> I guess this looks like it was assigned the same IRQ ?

I don't think so.  To be certain you'd have to check the boot-up log and
verify that 1d.1 is usb3 and 1d.3 is usb5.

>From the information presented here, it looks like -mm1 correctly routes
the 1d.1 controller to IRQ 193 and the 1d.3 controller to IRQ 169, whereas
-mm3 incorrectly routes the 1d.3 controller to IRQ 193.  That would make 
it an ACPI problem.

Alan Stern

Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Reuben Farrelly]

On 16/01/2006 4:22 p.m., Alan Stern wrote:
> On Mon, 16 Jan 2006, Reuben Farrelly wrote:
> 
>> On 13/01/2006 4:53 a.m., Alan Stern wrote:
>>> On Thu, 12 Jan 2006, Reuben Farrelly wrote:
>>>
>>>>>> Initializing USB Mass Storage driver...
>>>>>> irq 193: nobody cared (try booting with the "irqpoll" option)
>>>>>> handlers:
>>>>>> [<c027017e>] (usb_hcd_irq+0x0/0x56)
>>>>>> Disabling IRQ #193
>>>>> USB lost its interrupt.  Could be USB, more likely ACPI.
>>>> I've seen this one happen nearly every boot since then including bootups that 
>>>> are otherwise OK (no oopses), so it's probably worth more looking into rather 
>>>> than being written off as a 'once off':
>>>>
>>>> uhci_hcd 0000:00:1d.3: Unlink after no-IRQ?  Controller is probably using the 
>>>> wrong IRQ.
> 
> Note the PCI ID is 1d.3 and the IRQ is 193.
> 
>> Hi Alan,
>>
>> If it's any use, here's some simply and easy-to-get information which may even 
>> be what you are looking for:
>>
>> [root@tornado dovecot]# uname -a
>> Linux tornado.reub.net 2.6.15-mm1 #1 SMP Sun Jan 8 03:42:25 NZDT 2006 i686 i686 
>> i386 GNU/Linux
>> [root@tornado ~]# cat /proc/interrupts
>>             CPU0       CPU1
>>    0:   21638510          0    IO-APIC-edge  timer
>>    4:        356          0    IO-APIC-edge  serial
>>    8:          1          0    IO-APIC-edge  rtc
>>    9:          0          0   IO-APIC-level  acpi
>>   14:          1          0    IO-APIC-edge  ide0
>>   50:          3          0   IO-APIC-level  ehci_hcd:usb1, uhci_hcd:usb2
>> 169:        120          0   IO-APIC-level  uhci_hcd:usb5
>> 177:    2837992          0   IO-APIC-level  sky2
>> 185:      61450          0   IO-APIC-level  uhci_hcd:usb4, serial
>> 193:    4722447          0   IO-APIC-level  libata, uhci_hcd:usb3
> 
> Note that in the earlier kernel, IRQ 193 is assigned to usb3.  That's the 
> second UHCI controller, since usb1 is EHCI.
> 
>> [root@tornado ~]# lspci
> 
>> 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
>> USB UHCI #1 (rev 03)
>> 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
>> USB UHCI #2 (rev 03)
>> 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
>> USB UHCI #3 (rev 03)
>> 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
>> USB UHCI #4 (rev 03)
>> 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
>> USB2 EHCI Controller (rev 03)
> 
> Note that 1d.3 is the fourth UHCI controller; the second is 1d.1.
> 
>> I guess this looks like it was assigned the same IRQ ?
> 
> I don't think so.  To be certain you'd have to check the boot-up log and
> verify that 1d.1 is usb3 and 1d.3 is usb5.
> 
> From the information presented here, it looks like -mm1 correctly routes
> the 1d.1 controller to IRQ 193 and the 1d.3 controller to IRQ 169, whereas
> -mm3 incorrectly routes the 1d.3 controller to IRQ 193.  That would make 
> it an ACPI problem.

Is this likely to be the same or similar issue to the IRQ 0 problem I see quite 
frequently on the SATA ports on later -mm releases?
(see http://www.ussg.iu.edu/hypermail/linux/kernel/0601.1/1851.html)

Reuben

-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Reuben Farrelly]

On 16/01/2006 4:22 p.m., Alan Stern wrote:
> On Mon, 16 Jan 2006, Reuben Farrelly wrote:
> 
>> On 13/01/2006 4:53 a.m., Alan Stern wrote:
>>> On Thu, 12 Jan 2006, Reuben Farrelly wrote:
>>>
>>>>>> Initializing USB Mass Storage driver...
>>>>>> irq 193: nobody cared (try booting with the "irqpoll" option)
>>>>>> handlers:
>>>>>> [<c027017e>] (usb_hcd_irq+0x0/0x56)
>>>>>> Disabling IRQ #193
>>>>> USB lost its interrupt.  Could be USB, more likely ACPI.
>>>> I've seen this one happen nearly every boot since then including bootups that 
>>>> are otherwise OK (no oopses), so it's probably worth more looking into rather 
>>>> than being written off as a 'once off':
>>>>
>>>> uhci_hcd 0000:00:1d.3: Unlink after no-IRQ?  Controller is probably using the 
>>>> wrong IRQ.
> 
> Note the PCI ID is 1d.3 and the IRQ is 193.
> 
>> Hi Alan,
>>
>> If it's any use, here's some simply and easy-to-get information which may even 
>> be what you are looking for:
>>
>> [root@tornado dovecot]# uname -a
>> Linux tornado.reub.net 2.6.15-mm1 #1 SMP Sun Jan 8 03:42:25 NZDT 2006 i686 i686 
>> i386 GNU/Linux
>> [root@tornado ~]# cat /proc/interrupts
>>             CPU0       CPU1
>>    0:   21638510          0    IO-APIC-edge  timer
>>    4:        356          0    IO-APIC-edge  serial
>>    8:          1          0    IO-APIC-edge  rtc
>>    9:          0          0   IO-APIC-level  acpi
>>   14:          1          0    IO-APIC-edge  ide0
>>   50:          3          0   IO-APIC-level  ehci_hcd:usb1, uhci_hcd:usb2
>> 169:        120          0   IO-APIC-level  uhci_hcd:usb5
>> 177:    2837992          0   IO-APIC-level  sky2
>> 185:      61450          0   IO-APIC-level  uhci_hcd:usb4, serial
>> 193:    4722447          0   IO-APIC-level  libata, uhci_hcd:usb3
> 
> Note that in the earlier kernel, IRQ 193 is assigned to usb3.  That's the 
> second UHCI controller, since usb1 is EHCI.
> 
>> [root@tornado ~]# lspci
> 
>> 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
>> USB UHCI #1 (rev 03)
>> 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
>> USB UHCI #2 (rev 03)
>> 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
>> USB UHCI #3 (rev 03)
>> 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
>> USB UHCI #4 (rev 03)
>> 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
>> USB2 EHCI Controller (rev 03)
> 
> Note that 1d.3 is the fourth UHCI controller; the second is 1d.1.
> 
>> I guess this looks like it was assigned the same IRQ ?
> 
> I don't think so.  To be certain you'd have to check the boot-up log and
> verify that 1d.1 is usb3 and 1d.3 is usb5.
> 
> From the information presented here, it looks like -mm1 correctly routes
> the 1d.1 controller to IRQ 193 and the 1d.3 controller to IRQ 169, whereas
> -mm3 incorrectly routes the 1d.3 controller to IRQ 193.  That would make 
> it an ACPI problem.

Is this likely to be the same or similar issue to the IRQ 0 problem I see quite 
frequently on the SATA ports on later -mm releases?
(see http://www.ussg.iu.edu/hypermail/linux/kernel/0601.1/1851.html)

Reuben

Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Alan Stern]

On Mon, 16 Jan 2006, Reuben Farrelly wrote:

> > From the information presented here, it looks like -mm1 correctly routes
> > the 1d.1 controller to IRQ 193 and the 1d.3 controller to IRQ 169, whereas
> > -mm3 incorrectly routes the 1d.3 controller to IRQ 193.  That would make 
> > it an ACPI problem.
> 
> Is this likely to be the same or similar issue to the IRQ 0 problem I see quite 
> frequently on the SATA ports on later -mm releases?
> (see http://www.ussg.iu.edu/hypermail/linux/kernel/0601.1/1851.html)

I doubt they are at all related.  In the USB problem the resource is there 
but ACPI is routing it wrongly.  In the SATA problem the resource isn't 
there to begin with.

But then I know almost nothing about ACPI, so I could be wrong...

Alan Stern

-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Alan Stern]

On Mon, 16 Jan 2006, Reuben Farrelly wrote:

> > From the information presented here, it looks like -mm1 correctly routes
> > the 1d.1 controller to IRQ 193 and the 1d.3 controller to IRQ 169, whereas
> > -mm3 incorrectly routes the 1d.3 controller to IRQ 193.  That would make 
> > it an ACPI problem.
> 
> Is this likely to be the same or similar issue to the IRQ 0 problem I see quite 
> frequently on the SATA ports on later -mm releases?
> (see http://www.ussg.iu.edu/hypermail/linux/kernel/0601.1/1851.html)

I doubt they are at all related.  In the USB problem the resource is there 
but ACPI is routing it wrongly.  In the SATA problem the resource isn't 
there to begin with.

But then I know almost nothing about ACPI, so I could be wrong...

Alan Stern

Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Reuben Farrelly]

On 16/01/2006 4:46 p.m., Alan Stern wrote:
> On Mon, 16 Jan 2006, Reuben Farrelly wrote:
> 
>>> From the information presented here, it looks like -mm1 correctly routes
>>> the 1d.1 controller to IRQ 193 and the 1d.3 controller to IRQ 169, whereas
>>> -mm3 incorrectly routes the 1d.3 controller to IRQ 193.  That would make 
>>> it an ACPI problem.
>> Is this likely to be the same or similar issue to the IRQ 0 problem I see quite 
>> frequently on the SATA ports on later -mm releases?
>> (see http://www.ussg.iu.edu/hypermail/linux/kernel/0601.1/1851.html)
> 
> I doubt they are at all related.  In the USB problem the resource is there 
> but ACPI is routing it wrongly.  In the SATA problem the resource isn't 
> there to begin with.
> 
> But then I know almost nothing about ACPI, so I could be wrong...
> 
> Alan Stern

Some good news.  I think it's fixed in 2.6.16-rc1-mm2.  In fact a whole boatload 
of problems I was having are fixed in this -mm release, including a nasty libata 
oops that seemed to have a few people scratching their heads.

I've now done in excess of 20 reboots with this code and haven't had either 
problem show up at all.

So for now I'll keep a record of things for a bit longer, but I guess I've 
reason to be fairly confident that both this USB/IRQ problem and my ATA/IRQ 
problem are now fixed.

It does make me wonder if the ACPI update in rc1-mm2 fixed it, and was actually 
the cause of most of my problems......it would be nice to know for sure.

Thanks,
Reuben

Re: Re: 2.6.15-mm3 [USB lost interrupt bug]

[Andrew Morton]

Reuben Farrelly <reuben-lkml@reub.net> wrote:
>
> 
> 
> On 16/01/2006 4:46 p.m., Alan Stern wrote:
> > On Mon, 16 Jan 2006, Reuben Farrelly wrote:
> > 
> >>> From the information presented here, it looks like -mm1 correctly routes
> >>> the 1d.1 controller to IRQ 193 and the 1d.3 controller to IRQ 169, whereas
> >>> -mm3 incorrectly routes the 1d.3 controller to IRQ 193.  That would make 
> >>> it an ACPI problem.
> >> Is this likely to be the same or similar issue to the IRQ 0 problem I see quite 
> >> frequently on the SATA ports on later -mm releases?
> >> (see http://www.ussg.iu.edu/hypermail/linux/kernel/0601.1/1851.html)
> > 
> > I doubt they are at all related.  In the USB problem the resource is there 
> > but ACPI is routing it wrongly.  In the SATA problem the resource isn't 
> > there to begin with.
> > 
> > But then I know almost nothing about ACPI, so I could be wrong...
> > 
> > Alan Stern
> 
> Some good news.  I think it's fixed in 2.6.16-rc1-mm2.  In fact a whole boatload 
> of problems I was having are fixed in this -mm release, including a nasty libata 
> oops that seemed to have a few people scratching their heads.

OK, but probably that libata error-path bug is still in there.  It's just
that you're no longer taking the error paths.  And now we've lost our means
to reproduce it.

> I've now done in excess of 20 reboots with this code and haven't had either 
> problem show up at all.
> 
> So for now I'll keep a record of things for a bit longer, but I guess I've 
> reason to be fairly confident that both this USB/IRQ problem and my ATA/IRQ 
> problem are now fixed.
> 
> It does make me wonder if the ACPI update in rc1-mm2 fixed it, and was actually 
> the cause of most of my problems......it would be nice to know for sure.

We probably won't know.  Did you ever test 2.6.16-rc1 plus 2.6.16-rc1-mm1's
acpi.patch?  If that plays up we'd have confirmation.



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Andrew Morton]

Reuben Farrelly <reuben-lkml@reub.net> wrote:
>
> 
> 
> On 16/01/2006 4:46 p.m., Alan Stern wrote:
> > On Mon, 16 Jan 2006, Reuben Farrelly wrote:
> > 
> >>> From the information presented here, it looks like -mm1 correctly routes
> >>> the 1d.1 controller to IRQ 193 and the 1d.3 controller to IRQ 169, whereas
> >>> -mm3 incorrectly routes the 1d.3 controller to IRQ 193.  That would make 
> >>> it an ACPI problem.
> >> Is this likely to be the same or similar issue to the IRQ 0 problem I see quite 
> >> frequently on the SATA ports on later -mm releases?
> >> (see http://www.ussg.iu.edu/hypermail/linux/kernel/0601.1/1851.html)
> > 
> > I doubt they are at all related.  In the USB problem the resource is there 
> > but ACPI is routing it wrongly.  In the SATA problem the resource isn't 
> > there to begin with.
> > 
> > But then I know almost nothing about ACPI, so I could be wrong...
> > 
> > Alan Stern
> 
> Some good news.  I think it's fixed in 2.6.16-rc1-mm2.  In fact a whole boatload 
> of problems I was having are fixed in this -mm release, including a nasty libata 
> oops that seemed to have a few people scratching their heads.

OK, but probably that libata error-path bug is still in there.  It's just
that you're no longer taking the error paths.  And now we've lost our means
to reproduce it.

> I've now done in excess of 20 reboots with this code and haven't had either 
> problem show up at all.
> 
> So for now I'll keep a record of things for a bit longer, but I guess I've 
> reason to be fairly confident that both this USB/IRQ problem and my ATA/IRQ 
> problem are now fixed.
> 
> It does make me wonder if the ACPI update in rc1-mm2 fixed it, and was actually 
> the cause of most of my problems......it would be nice to know for sure.

We probably won't know.  Did you ever test 2.6.16-rc1 plus 2.6.16-rc1-mm1's
acpi.patch?  If that plays up we'd have confirmation.

Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Reuben Farrelly]

On 21/01/2006 6:47 p.m., Andrew Morton wrote:

>> I've now done in excess of 20 reboots with this code and haven't had either 
>> problem show up at all.
>>
>> So for now I'll keep a record of things for a bit longer, but I guess I've 
>> reason to be fairly confident that both this USB/IRQ problem and my ATA/IRQ 
>> problem are now fixed.
>>
>> It does make me wonder if the ACPI update in rc1-mm2 fixed it, and was actually 
>> the cause of most of my problems......it would be nice to know for sure.
> 
> We probably won't know.  Did you ever test 2.6.16-rc1 plus 2.6.16-rc1-mm1's
> acpi.patch?  If that plays up we'd have confirmation.

It has been OK over 15x reboots (just tested now).  2.6.16-rc1-mm1 wasn't the 
usual standard award winning release for me because of the reiserfs problems so 
I only booted into it once and ran it for a couple of hours before retreating to 
2.6.15-rc1.

Last *known* problematic release on that box was 2.6.15-mm4.

[PATCH] Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Jeff Garzik]

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


On the libata side of things, does this patch produce any useful results?

	Jeff




[-- Attachment #2: patch.pci-region-check --]
[-- Type: text/plain, Size: 1544 bytes --]

diff --git a/drivers/scsi/libata-core.c b/drivers/scsi/libata-core.c
index 46c4cdb..4691f8d 100644
--- a/drivers/scsi/libata-core.c
+++ b/drivers/scsi/libata-core.c
@@ -4794,7 +4794,14 @@ ata_pci_init_native_mode(struct pci_dev 
 			pci_resource_start(pdev, 1) | ATA_PCI_CTL_OFS;
 		probe_ent->port[p].bmdma_addr = pci_resource_start(pdev, 4);
 		ata_std_ports(&probe_ent->port[p]);
-		p++;
+
+		if (pci_resource_start(pdev, 0) &&
+		    pci_resource_len(pdev, 0) &&
+		    pci_resource_start(pdev, 1) &&
+		    pci_resource_len(pdev, 1) &&
+		    pci_resource_start(pdev, 4) &&
+		    pci_resource_len(pdev, 4))
+			p++;
 	}
 
 	if (ports & ATA_PORT_SECONDARY) {
@@ -4804,10 +4811,23 @@ ata_pci_init_native_mode(struct pci_dev 
 			pci_resource_start(pdev, 3) | ATA_PCI_CTL_OFS;
 		probe_ent->port[p].bmdma_addr = pci_resource_start(pdev, 4) + 8;
 		ata_std_ports(&probe_ent->port[p]);
-		p++;
+
+		if (pci_resource_start(pdev, 2) &&
+		    pci_resource_len(pdev, 2) &&
+		    pci_resource_start(pdev, 3) &&
+		    pci_resource_len(pdev, 3) &&
+		    pci_resource_start(pdev, 4) &&
+		    pci_resource_len(pdev, 4) > 8)
+			p++;
 	}
 
 	probe_ent->n_ports = p;
+
+	if (p == 0) {
+		kfree(probe_ent);
+		probe_ent = NULL;
+	}
+
 	return probe_ent;
 }
 
@@ -4815,6 +4835,10 @@ static struct ata_probe_ent *ata_pci_ini
 {
 	struct ata_probe_ent *probe_ent;
 
+	if (!pci_resource_start(pdev, 4) ||
+	    !pci_resource_len(pdev, 4))
+		return NULL;
+
 	probe_ent = ata_probe_ent_alloc(pci_dev_to_dev(pdev), port);
 	if (!probe_ent)
 		return NULL;

Re: [PATCH] Re: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]

[Reuben Farrelly]

On 21/01/2006 9:32 p.m., Jeff Garzik wrote:
> 
> On the libata side of things, does this patch produce any useful results?
> 
>     Jeff
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> diff --git a/drivers/scsi/libata-core.c b/drivers/scsi/libata-core.c
> index 46c4cdb..4691f8d 100644
> --- a/drivers/scsi/libata-core.c
> +++ b/drivers/scsi/libata-core.c
> @@ -4794,7 +4794,14 @@ ata_pci_init_native_mode(struct pci_dev 
>  			pci_resource_start(pdev, 1) | ATA_PCI_CTL_OFS;
>  		probe_ent->port[p].bmdma_addr = pci_resource_start(pdev, 4);
>  		ata_std_ports(&probe_ent->port[p]);
> -		p++;

I've patched 2.6.15-mm4 with this, and yes, this patch changed the behaviour:

OK TIMEOUT OK OK TIMEOUT TIMEOUT TIMEOUT TIMEOUT OK TIMEOUT TIMEOUT OK TIMEOUT 
TIMEOUT TIMEOUT

OK was when we got through to completion of single user mode, TIMEOUT - see below.

So no oopsing with that patch applied, which is a definite improvement. 
Previously to this I was seeing the OOPSing most of the time and the TIMEOUTS 
more occasionally.

---

Now, looking at the timeouts, here's the log from a boot:

ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 193
ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 4 ports 1.5 Gbps 0xf impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq led slum part
ata1: SATA max UDMA/133 cmd 0xF8804D00 ctl 0x0 bmdma 0x0 irq 50
ata2: SATA max UDMA/133 cmd 0xF8804D80 ctl 0x0 bmdma 0x0 irq 50
ata3: SATA max UDMA/133 cmd 0xF8804E00 ctl 0x0 bmdma 0x0 irq 50
ata4: SATA max UDMA/133 cmd 0xF8804E80 ctl 0x0 bmdma 0x0 irq 50
ata1: SATA link up 1.5 Gbps (SStatus 113)
ata1 is slow to respond, please be patient
ata1 failed to respond (30 secs)
scsi0 : ahci
ata2: SATA link up 1.5 Gbps (SStatus 113)
ata2 is slow to respond, please be patient
ata2 failed to respond (30 secs)
scsi1 : ahci
ata3: SATA link up 1.5 Gbps (SStatus 113)
ata3 is slow to respond, please be patient
ata3 failed to respond (30 secs)
scsi2 : ahci
ata4: SATA link down (SStatus 0)
scsi3 : ahci

When there is no timeout it looks like this:

ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 193
ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 4 ports 1.5 Gbps 0xf impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq led slum part
ata1: SATA max UDMA/133 cmd 0xF8804D00 ctl 0x0 bmdma 0x0 irq 193
ata2: SATA max UDMA/133 cmd 0xF8804D80 ctl 0x0 bmdma 0x0 irq 193
ata3: SATA max UDMA/133 cmd 0xF8804E00 ctl 0x0 bmdma 0x0 irq 193
ata4: SATA max UDMA/133 cmd 0xF8804E80 ctl 0x0 bmdma 0x0 irq 193
ata1: SATA link up 1.5 Gbps (SStatus 113)
ata1: dev 0 ATA-6, max UDMA/133, 156301488 sectors: LBA48
ata1: dev 0 configured for UDMA/133
scsi0 : ahci
ata2: SATA link up 1.5 Gbps (SStatus 113)
ata2: dev 0 ATA-6, max UDMA/133, 156301488 sectors: LBA48
ata2: dev 0 configured for UDMA/133
scsi1 : ahci
ata3: SATA link up 1.5 Gbps (SStatus 113)
ata3: dev 0 ATA-6, max UDMA/133, 156299375 sectors: LBA48
ata3: dev 0 configured for UDMA/133
scsi2 : ahci
ata4: SATA link down (SStatus 0)
scsi3 : ahci

Note the different IRQ numbers (50, 193) and how when it breaks, the ATA 
interfaces have a different IRQ to the AHCI controller.

There's a full log up at http://lkml.org/lkml/2006/1/11/492 from when I posted 
on lkml and at http://www.reub.net/files/kernel/ when the box isn't down for 
testing ;-)

This may be a separate but related problem to the oops, I guess.

reuben

[RFC: -mm patch] swsusp: make some code static

[Adrian Bunk]

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

On Wed, Jan 11, 2006 at 04:21:35AM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.15-mm2:
>...
> +swsusp-low-level-interface-rev-2.patch
>...
>  swsusp updates
>...

After this patch, we can make some code static.


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

---

 include/linux/swap.h    |    1 -
 kernel/power/power.h    |    1 -
 kernel/power/snapshot.c |    4 ++--
 mm/swapfile.c           |    2 +-
 4 files changed, 3 insertions(+), 5 deletions(-)

--- linux-2.6.15-mm3-full/kernel/power/power.h.old	2006-01-12 01:01:49.000000000 +0100
+++ linux-2.6.15-mm3-full/kernel/power/power.h	2006-01-12 01:01:55.000000000 +0100
@@ -48,7 +48,6 @@
 /* References to section boundaries */
 extern const void __nosave_begin, __nosave_end;
 
-extern unsigned int nr_copy_pages;
 extern struct pbe *pagedir_nosave;
 
 /* Preferred image size in MB (default 500) */
--- linux-2.6.15-mm3-full/kernel/power/snapshot.c.old	2006-01-12 01:02:03.000000000 +0100
+++ linux-2.6.15-mm3-full/kernel/power/snapshot.c	2006-01-12 01:02:18.000000000 +0100
@@ -35,8 +35,8 @@
 #include "power.h"
 
 struct pbe *pagedir_nosave;
-unsigned int nr_copy_pages;
-unsigned int nr_meta_pages;
+static unsigned int nr_copy_pages;
+static unsigned int nr_meta_pages;
 
 #ifdef CONFIG_HIGHMEM
 unsigned int count_highmem_pages(void)
--- linux-2.6.15-mm3-full/include/linux/swap.h.old	2006-01-12 01:04:21.000000000 +0100
+++ linux-2.6.15-mm3-full/include/linux/swap.h	2006-01-12 01:04:33.000000000 +0100
@@ -232,7 +232,6 @@
 /* linux/mm/swapfile.c */
 extern long total_swap_pages;
 extern unsigned int nr_swapfiles;
-extern struct swap_info_struct swap_info[];
 extern void si_swapinfo(struct sysinfo *);
 extern swp_entry_t get_swap_page(void);
 extern swp_entry_t get_swap_page_of_type(int);
--- linux-2.6.15-mm3-full/mm/swapfile.c.old	2006-01-12 01:04:42.000000000 +0100
+++ linux-2.6.15-mm3-full/mm/swapfile.c	2006-01-12 01:04:51.000000000 +0100
@@ -44,7 +44,7 @@
 
 struct swap_list_t swap_list = {-1, -1};
 
-struct swap_info_struct swap_info[MAX_SWAPFILES];
+static struct swap_info_struct swap_info[MAX_SWAPFILES];
 
 static DECLARE_MUTEX(swapon_sem);
 


[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

[RFC: -mm patch] swsusp: make some code static

[Adrian Bunk]

On Wed, Jan 11, 2006 at 04:21:35AM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.15-mm2:
>...
> +swsusp-low-level-interface-rev-2.patch
>...
>  swsusp updates
>...

After this patch, we can make some code static.


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

---

 include/linux/swap.h    |    1 -
 kernel/power/power.h    |    1 -
 kernel/power/snapshot.c |    4 ++--
 mm/swapfile.c           |    2 +-
 4 files changed, 3 insertions(+), 5 deletions(-)

--- linux-2.6.15-mm3-full/kernel/power/power.h.old	2006-01-12 01:01:49.000000000 +0100
+++ linux-2.6.15-mm3-full/kernel/power/power.h	2006-01-12 01:01:55.000000000 +0100
@@ -48,7 +48,6 @@
 /* References to section boundaries */
 extern const void __nosave_begin, __nosave_end;
 
-extern unsigned int nr_copy_pages;
 extern struct pbe *pagedir_nosave;
 
 /* Preferred image size in MB (default 500) */
--- linux-2.6.15-mm3-full/kernel/power/snapshot.c.old	2006-01-12 01:02:03.000000000 +0100
+++ linux-2.6.15-mm3-full/kernel/power/snapshot.c	2006-01-12 01:02:18.000000000 +0100
@@ -35,8 +35,8 @@
 #include "power.h"
 
 struct pbe *pagedir_nosave;
-unsigned int nr_copy_pages;
-unsigned int nr_meta_pages;
+static unsigned int nr_copy_pages;
+static unsigned int nr_meta_pages;
 
 #ifdef CONFIG_HIGHMEM
 unsigned int count_highmem_pages(void)
--- linux-2.6.15-mm3-full/include/linux/swap.h.old	2006-01-12 01:04:21.000000000 +0100
+++ linux-2.6.15-mm3-full/include/linux/swap.h	2006-01-12 01:04:33.000000000 +0100
@@ -232,7 +232,6 @@
 /* linux/mm/swapfile.c */
 extern long total_swap_pages;
 extern unsigned int nr_swapfiles;
-extern struct swap_info_struct swap_info[];
 extern void si_swapinfo(struct sysinfo *);
 extern swp_entry_t get_swap_page(void);
 extern swp_entry_t get_swap_page_of_type(int);
--- linux-2.6.15-mm3-full/mm/swapfile.c.old	2006-01-12 01:04:42.000000000 +0100
+++ linux-2.6.15-mm3-full/mm/swapfile.c	2006-01-12 01:04:51.000000000 +0100
@@ -44,7 +44,7 @@
 
 struct swap_list_t swap_list = {-1, -1};
 
-struct swap_info_struct swap_info[MAX_SWAPFILES];
+static struct swap_info_struct swap_info[MAX_SWAPFILES];
 
 static DECLARE_MUTEX(swapon_sem);
 

Re: [RFC: -mm patch] swsusp: make some code static

[Pavel Machek]

On Čt 12-01-06 11:48:12, Adrian Bunk wrote:
> On Wed, Jan 11, 2006 at 04:21:35AM -0800, Andrew Morton wrote:
> >...
> > Changes since 2.6.15-mm2:
> >...
> > +swsusp-low-level-interface-rev-2.patch
> >...
> >  swsusp updates
> >...
> 
> After this patch, we can make some code static.
> 
> 
> Signed-off-by: Adrian Bunk <bunk@stusta.de>

Rafael should comment here. It is okay, but Rafael has some patches in
the queue, and it would be better if there were to clashes.
								Pavel

-- 
Thanks, Sharp!

Re: [RFC: -mm patch] swsusp: make some code static

[Rafael J. Wysocki]

Hi,

On Thursday, 12 January 2006 16:29, you wrote:
> On Čt 12-01-06 11:48:12, Adrian Bunk wrote:
> > On Wed, Jan 11, 2006 at 04:21:35AM -0800, Andrew Morton wrote:
> > >...
> > > Changes since 2.6.15-mm2:
> > >...
> > > +swsusp-low-level-interface-rev-2.patch
> > >...
> > >  swsusp updates
> > >...
> > 
> > After this patch, we can make some code static.

Nice catch. ;-)

> > 
> > 
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> 
> Rafael should comment here. It is okay, but Rafael has some patches in
> the queue, and it would be better if there were to clashes.

It doesn't clash with any of my patches (just tested).

Greetings,
Rafael

[-mm patch] drivers/block/aoe/aoecmd.c: make aoecmd_cfg_pkts() static

[Adrian Bunk]

On Wed, Jan 11, 2006 at 04:21:35AM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.15-mm2:
>...
> +gregkh-driver-aoe-support-dynamic-resizing-of-aoe-devices.patch
>...
>  driver tree updates
>...

aoecmd_cfg_pkts() can be static.


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

---

 drivers/block/aoe/aoe.h    |    1 
 drivers/block/aoe/aoecmd.c |   94 ++++++++++++++++++-------------------
 2 files changed, 47 insertions(+), 48 deletions(-)

--- linux-2.6.15-mm3-full/drivers/block/aoe/aoe.h.old	2006-01-12 00:56:33.000000000 +0100
+++ linux-2.6.15-mm3-full/drivers/block/aoe/aoe.h	2006-01-12 00:56:38.000000000 +0100
@@ -154,7 +154,6 @@
 
 void aoecmd_work(struct aoedev *d);
 void aoecmd_cfg(ushort aoemajor, unsigned char aoeminor);
-struct sk_buff *aoecmd_cfg_pkts(ushort, unsigned char, struct sk_buff **);
 void aoecmd_ata_rsp(struct sk_buff *);
 void aoecmd_cfg_rsp(struct sk_buff *);
 void aoecmd_sleepwork(void *vp);
--- linux-2.6.15-mm3-full/drivers/block/aoe/aoecmd.c.old	2006-01-12 00:56:47.000000000 +0100
+++ linux-2.6.15-mm3-full/drivers/block/aoe/aoecmd.c	2006-01-12 00:57:29.000000000 +0100
@@ -190,6 +190,53 @@
 	}
 }
 
+/* some callers cannot sleep, and they can call this function,
+ * transmitting the packets later, when interrupts are on
+ */
+static struct sk_buff *
+aoecmd_cfg_pkts(ushort aoemajor, unsigned char aoeminor, struct sk_buff **tail)
+{
+	struct aoe_hdr *h;
+	struct aoe_cfghdr *ch;
+	struct sk_buff *skb, *sl, *sl_tail;
+	struct net_device *ifp;
+
+	sl = sl_tail = NULL;
+
+	read_lock(&dev_base_lock);
+	for (ifp = dev_base; ifp; dev_put(ifp), ifp = ifp->next) {
+		dev_hold(ifp);
+		if (!is_aoe_netif(ifp))
+			continue;
+
+		skb = new_skb(ifp, sizeof *h + sizeof *ch);
+		if (skb == NULL) {
+			printk(KERN_INFO "aoe: aoecmd_cfg: skb alloc failure\n");
+			continue;
+		}
+		if (sl_tail == NULL)
+			sl_tail = skb;
+		h = (struct aoe_hdr *) skb->mac.raw;
+		memset(h, 0, sizeof *h + sizeof *ch);
+
+		memset(h->dst, 0xff, sizeof h->dst);
+		memcpy(h->src, ifp->dev_addr, sizeof h->src);
+		h->type = __constant_cpu_to_be16(ETH_P_AOE);
+		h->verfl = AOE_HVER;
+		h->major = cpu_to_be16(aoemajor);
+		h->minor = aoeminor;
+		h->cmd = AOECMD_CFG;
+
+		skb->next = sl;
+		sl = skb;
+	}
+	read_unlock(&dev_base_lock);
+
+	if (tail != NULL)
+		*tail = sl_tail;
+	return sl;
+}
+
 /* enters with d->lock held */
 void
 aoecmd_work(struct aoedev *d)
@@ -543,53 +590,6 @@
 	aoenet_xmit(sl);
 }
 
-/* some callers cannot sleep, and they can call this function,
- * transmitting the packets later, when interrupts are on
- */
-struct sk_buff *
-aoecmd_cfg_pkts(ushort aoemajor, unsigned char aoeminor, struct sk_buff **tail)
-{
-	struct aoe_hdr *h;
-	struct aoe_cfghdr *ch;
-	struct sk_buff *skb, *sl, *sl_tail;
-	struct net_device *ifp;
-
-	sl = sl_tail = NULL;
-
-	read_lock(&dev_base_lock);
-	for (ifp = dev_base; ifp; dev_put(ifp), ifp = ifp->next) {
-		dev_hold(ifp);
-		if (!is_aoe_netif(ifp))
-			continue;
-
-		skb = new_skb(ifp, sizeof *h + sizeof *ch);
-		if (skb == NULL) {
-			printk(KERN_INFO "aoe: aoecmd_cfg: skb alloc failure\n");
-			continue;
-		}
-		if (sl_tail == NULL)
-			sl_tail = skb;
-		h = (struct aoe_hdr *) skb->mac.raw;
-		memset(h, 0, sizeof *h + sizeof *ch);
-
-		memset(h->dst, 0xff, sizeof h->dst);
-		memcpy(h->src, ifp->dev_addr, sizeof h->src);
-		h->type = __constant_cpu_to_be16(ETH_P_AOE);
-		h->verfl = AOE_HVER;
-		h->major = cpu_to_be16(aoemajor);
-		h->minor = aoeminor;
-		h->cmd = AOECMD_CFG;
-
-		skb->next = sl;
-		sl = skb;
-	}
-	read_unlock(&dev_base_lock);
-
-	if (tail != NULL)
-		*tail = sl_tail;
-	return sl;
-}
-
 void
 aoecmd_cfg(ushort aoemajor, unsigned char aoeminor)
 {

Re: [-mm patch] drivers/block/aoe/aoecmd.c: make aoecmd_cfg_pkts() static

[Ed L. Cashin]

On Thu, Jan 12, 2006 at 11:48:33AM +0100, Adrian Bunk wrote:

...
> aoecmd_cfg_pkts() can be static.

Nice catch.  This patch follows a series of seven aoe driver patches
that haven't made it into the mainline because they need a fix that
I've just made.

I'll be resending the patches with the fix included, and at that time
I'll include this change.

Thanks!

-- 
  Ed L Cashin <ecashin@coraid.com>

Re: 2.6.15-mm3

[Rafael J. Wysocki]

Hi,

On Wednesday, 11 January 2006 13:21, Andrew Morton wrote:
> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/

I got that on system shutdown (x86-64, 1 CPU):

Unable to handle kernel NULL pointer dereference at 00000000000001b4 RIP:
<ffffffff881cba51>{:ipv6:ip6_xmit+593}
PGD 2441f067 PUD 231b1067 PMD 0
Oops: 0000 [1] PREEMPT
CPU 0
Modules linked in: ipt_LOG ipt_limit ipt_pkttype ipt_state ipt_REJECT iptable_mangle iptable_nat iptable_filter ip6table_mangle ip_nat_ftp
ip_nat ip_conntrack_ftp ip_conntrack ip_tables ip6table_filter ip6_tables ipv6 usbserial thermal processor fan button battery ac snd_pcm_os
s snd_mixer_oss snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc af_packet pcmcia firmware_class yen
ta_socket rsrc_nonstatic pcmcia_core usbhid ehci_hcd ohci_hcd sk98lin evdev joydev sg st sr_mod sd_mod scsi_mod ide_cd cdrom dm_mod parport
_pc lp parport
Pid: 18912, comm: kcminit Not tainted 2.6.15-mm3 #25
RIP: 0010:[<ffffffff881cba51>] <ffffffff881cba51>{:ipv6:ip6_xmit+593}
RSP: 0018:ffffffff80489cc8  EFLAGS: 00010246
RAX: ffff810029a47658 RBX: ffff810029a47658 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff80489d50 RDI: ffff810001f33e00
RBP: ffffffff80489d28 R08: 0000000000000000 R09: 0000000000000080
R10: ffff8100201a9f5c R11: ffffffff80489d40 R12: ffff810001f33dd8
R13: 0000000000000000 R14: ffffffff80489d38 R15: 0000000000000014
FS:  00002aaaae769de0(0000) GS:ffffffff80515000(0000) knlGS:000000005617d560
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00000000000001b4 CR3: 00000000249eb000 CR4: 00000000000006e0
Process kcminit (pid: 18912, threadinfo ffff8100233ca000, task ffff810028afa090)
Stack: ffff810029a476a0 ffff8100201a9e60 0000000000000000 00000000881cb324
       ffff810029a47658 ffffffff80489d40 0600000180489d48 ffff810029a476a0
       ffffffff80489d40 ffff810001f33e00
Call Trace: <IRQ> <ffffffff881e9aad>{:ipv6:tcp_v6_send_reset+525}
       <ffffffff80361dd8>{inet6_lookup_listener+264} <ffffffff881ec8e2>{:ipv6:tcp_v6_rcv+1842}
       <ffffffff881ccd48>{:ipv6:ip6_input+568} <ffffffff881cd14f>{:ipv6:ipv6_rcv+527}
       <ffffffff8030283b>{netif_receive_skb+635} <ffffffff80302939>{process_backlog+153}
       <ffffffff803014c3>{net_rx_action+179} <ffffffff80135f10>{__do_softirq+80}
       <ffffffff8010fd12>{call_softirq+30}  <EOI> <ffffffff801116e5>{do_softirq+53}
       <ffffffff801361b2>{local_bh_enable+114} <ffffffff80302fc7>{dev_queue_xmit+583}
       <ffffffff8030971f>{neigh_resolve_output+639} <ffffffff881cbf82>{:ipv6:ip6_output2+562}
       <ffffffff881c9d40>{:ipv6:dst_output+0} <ffffffff881cc7cd>{:ipv6:ip6_output+2045}
       <ffffffff881cbaeb>{:ipv6:ip6_xmit+747} <ffffffff881f0f21>{:ipv6:inet6_csk_xmit+769}
       <ffffffff803357ff>{tcp_transmit_skb+1743} <ffffffff802fe4ff>{__alloc_skb+127}
       <ffffffff80335e43>{tcp_connect+723} <ffffffff881eba49>{:ipv6:tcp_v6_connect+1529}
       <ffffffff80148d33>{__mutex_init+83} <ffffffff803652d8>{_spin_unlock_bh+24}
       <ffffffff8034871f>{inet_stream_connect+207} <ffffffff803652d8>{_spin_unlock_bh+24}
       <ffffffff802fa369>{lock_sock+201} <ffffffff803652d8>{_spin_unlock_bh+24}
       <ffffffff80180b0a>{fget+170} <ffffffff802f92ac>{sys_connect+140}
       <ffffffff802f8022>{sys_setsockopt+162} <ffffffff8010ec9e>{system_call+126}


Code: 41 8b 95 b4 01 00 00 89 90 98 00 00 00 48 8b 45 a8 8b 58 40
RIP <ffffffff881cba51>{:ipv6:ip6_xmit+593} RSP <ffffffff80489cc8>
CR2: 00000000000001b4
 <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
 <4>atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.

and so on forever.

Greetings,
Rafael

Re: 2.6.15-mm3

[Andrew Morton]

"Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
> Hi,
> 
> On Wednesday, 11 January 2006 13:21, Andrew Morton wrote:
> > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/
> 
> I got that on system shutdown (x86-64, 1 CPU):

Thanks.   ipv6 died.  I think shemminger had a recent problem with ipv6 too?

I don't think there were any core networking changes in -mm3 which weren't
in linus-at-that-time.

> Unable to handle kernel NULL pointer dereference at 00000000000001b4 RIP:
> <ffffffff881cba51>{:ipv6:ip6_xmit+593}
> PGD 2441f067 PUD 231b1067 PMD 0
> Oops: 0000 [1] PREEMPT
> CPU 0
> Modules linked in: ipt_LOG ipt_limit ipt_pkttype ipt_state ipt_REJECT iptable_mangle iptable_nat iptable_filter ip6table_mangle ip_nat_ftp
> ip_nat ip_conntrack_ftp ip_conntrack ip_tables ip6table_filter ip6_tables ipv6 usbserial thermal processor fan button battery ac snd_pcm_os
> s snd_mixer_oss snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc af_packet pcmcia firmware_class yen
> ta_socket rsrc_nonstatic pcmcia_core usbhid ehci_hcd ohci_hcd sk98lin evdev joydev sg st sr_mod sd_mod scsi_mod ide_cd cdrom dm_mod parport
> _pc lp parport
> Pid: 18912, comm: kcminit Not tainted 2.6.15-mm3 #25
> RIP: 0010:[<ffffffff881cba51>] <ffffffff881cba51>{:ipv6:ip6_xmit+593}
> RSP: 0018:ffffffff80489cc8  EFLAGS: 00010246
> RAX: ffff810029a47658 RBX: ffff810029a47658 RCX: 0000000000000000
> RDX: 0000000000000000 RSI: ffffffff80489d50 RDI: ffff810001f33e00
> RBP: ffffffff80489d28 R08: 0000000000000000 R09: 0000000000000080
> R10: ffff8100201a9f5c R11: ffffffff80489d40 R12: ffff810001f33dd8
> R13: 0000000000000000 R14: ffffffff80489d38 R15: 0000000000000014
> FS:  00002aaaae769de0(0000) GS:ffffffff80515000(0000) knlGS:000000005617d560
> CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 00000000000001b4 CR3: 00000000249eb000 CR4: 00000000000006e0
> Process kcminit (pid: 18912, threadinfo ffff8100233ca000, task ffff810028afa090)
> Stack: ffff810029a476a0 ffff8100201a9e60 0000000000000000 00000000881cb324
>        ffff810029a47658 ffffffff80489d40 0600000180489d48 ffff810029a476a0
>        ffffffff80489d40 ffff810001f33e00
> Call Trace: <IRQ> <ffffffff881e9aad>{:ipv6:tcp_v6_send_reset+525}
>        <ffffffff80361dd8>{inet6_lookup_listener+264} <ffffffff881ec8e2>{:ipv6:tcp_v6_rcv+1842}
>        <ffffffff881ccd48>{:ipv6:ip6_input+568} <ffffffff881cd14f>{:ipv6:ipv6_rcv+527}
>        <ffffffff8030283b>{netif_receive_skb+635} <ffffffff80302939>{process_backlog+153}
>        <ffffffff803014c3>{net_rx_action+179} <ffffffff80135f10>{__do_softirq+80}
>        <ffffffff8010fd12>{call_softirq+30}  <EOI> <ffffffff801116e5>{do_softirq+53}
>        <ffffffff801361b2>{local_bh_enable+114} <ffffffff80302fc7>{dev_queue_xmit+583}
>        <ffffffff8030971f>{neigh_resolve_output+639} <ffffffff881cbf82>{:ipv6:ip6_output2+562}
>        <ffffffff881c9d40>{:ipv6:dst_output+0} <ffffffff881cc7cd>{:ipv6:ip6_output+2045}
>        <ffffffff881cbaeb>{:ipv6:ip6_xmit+747} <ffffffff881f0f21>{:ipv6:inet6_csk_xmit+769}
>        <ffffffff803357ff>{tcp_transmit_skb+1743} <ffffffff802fe4ff>{__alloc_skb+127}
>        <ffffffff80335e43>{tcp_connect+723} <ffffffff881eba49>{:ipv6:tcp_v6_connect+1529}
>        <ffffffff80148d33>{__mutex_init+83} <ffffffff803652d8>{_spin_unlock_bh+24}
>        <ffffffff8034871f>{inet_stream_connect+207} <ffffffff803652d8>{_spin_unlock_bh+24}
>        <ffffffff802fa369>{lock_sock+201} <ffffffff803652d8>{_spin_unlock_bh+24}
>        <ffffffff80180b0a>{fget+170} <ffffffff802f92ac>{sys_connect+140}
>        <ffffffff802f8022>{sys_setsockopt+162} <ffffffff8010ec9e>{system_call+126}
> 
> 
> Code: 41 8b 95 b4 01 00 00 89 90 98 00 00 00 48 8b 45 a8 8b 58 40
> RIP <ffffffff881cba51>{:ipv6:ip6_xmit+593} RSP <ffffffff80489cc8>
> CR2: 00000000000001b4
>  <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
>  <4>atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
> atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
> atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
> atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
> 
> and so on forever.
> 
> Greetings,
> Rafael

Re: 2.6.15-mm3

[Patrick McHardy]

Andrew Morton wrote:
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> 
>>Hi,
>>
>>On Wednesday, 11 January 2006 13:21, Andrew Morton wrote:
>>
>>>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/
>>
>>I got that on system shutdown (x86-64, 1 CPU):
> 
> 
> Thanks.   ipv6 died.  I think shemminger had a recent problem with ipv6 too?
> 
> I don't think there were any core networking changes in -mm3 which weren't
> in linus-at-that-time.
> 
> 
>>Unable to handle kernel NULL pointer dereference at 00000000000001b4 RIP:
>><ffffffff881cba51>{:ipv6:ip6_xmit+593}

That crash is already fixed in Linus' latest tree by this patch:

tree 3d4ce288b86cb2845d79c6adec9e254054bb0e02
parent a7768097557be91d0d4c37e8f2e38cd126c4cdf9
author David Woodhouse <dwmw2@infradead.org> Thu, 12 Jan 2006 07:53:04 -0800
committer David S. Miller <davem@sunset.davemloft.net> Thu, 12 Jan 2006 
08:32:13 -0800

[IPV6]: Avoid calling ip6_xmit() with NULL sk
The ip6_xmit() function now assumes that its sk argument is non-NULL,
which isn't currently true when TCPv6 code is sending RST or ACK
packets. This fixes that code to use a socket of its own for sending
such packets, as TCPv4 does. (Thanks Andi for the pointer).

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
Signed-off-by: David S. Miller <davem@davemloft.net>

Re: 2.6.15-mm3

[Sachin Sant]

Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/

I got this compile time error on a powerpc box.

...
   CC [M]  drivers/usb/input/mtouchusb.o
   CC [M]  drivers/usb/input/powermate.o
   CC [M]  drivers/usb/input/wacom.o
drivers/usb/input/wacom.c:98: error: conflicting types for `G4'
include/asm/cputable.h:37: error: previous declaration of `G4'
make[3]: *** [drivers/usb/input/wacom.o] Error 1
make[2]: *** [drivers/usb/input] Error 2
make[1]: *** [drivers/usb] Error 2
make: *** [drivers] Error 2

Problem seems to be because of the following in 
include/asm-powerpc/cputable.h

enum powerpc_oprofile_type {
         INVALID = 0,
         RS64 = 1,
         POWER4 = 2,
         G4 = 3,     <====Defined here
         BOOKE = 4,
};


Thanks
-Sachin

Re: 2.6.15-mm3

[Andrew Morton]

Sachin Sant <sachinp@in.ibm.com> wrote:
>

Please always do reply-to-all.

> Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/
> 
> I got this compile time error on a powerpc box.
> 

yup, thanks.

> ...
>    CC [M]  drivers/usb/input/mtouchusb.o
>    CC [M]  drivers/usb/input/powermate.o
>    CC [M]  drivers/usb/input/wacom.o
> drivers/usb/input/wacom.c:98: error: conflicting types for `G4'
> include/asm/cputable.h:37: error: previous declaration of `G4'
> make[3]: *** [drivers/usb/input/wacom.o] Error 1
> make[2]: *** [drivers/usb/input] Error 2
> make[1]: *** [drivers/usb] Error 2
> make: *** [drivers] Error 2
> 
> Problem seems to be because of the following in 
> include/asm-powerpc/cputable.h
> 
> enum powerpc_oprofile_type {
>          INVALID = 0,
>          RS64 = 1,
>          POWER4 = 2,
>          G4 = 3,     <====Defined here
>          BOOKE = 4,
> };
> 

err, Ben.  Not a great choice of identifier...

Re: 2.6.15-mm3

[Benjamin Herrenschmidt]

> > 
> > Problem seems to be because of the following in 
> > include/asm-powerpc/cputable.h
> > 
> > enum powerpc_oprofile_type {
> >          INVALID = 0,
> >          RS64 = 1,
> >          POWER4 = 2,
> >          G4 = 3,     <====Defined here
> >          BOOKE = 4,
> > };
> > 
> 
> err, Ben.  Not a great choice of identifier...

Very bad indeed, /me blames whoever did that oprofile support... I'll
get that fixed asap.

Ben.