ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
- x86 NMI handling seems to be bust in 2.6.12-rc2. Try using
`nmi_watchdog=0' if you experience weird crashes.
- The possible kernel-timer related hangs might possibly be fixed. We
haven't heard yet.
- Nobody said anything about the PM resume and DRI behaviour in
2.6.12-rc1-mm4. So it's all perfect now?
- Various fixes and updates. Nothing earth-shattering.
Changes since 2.6.12-rc1-mm4:
bk-acpi.patch
bk-agpgart.patch
bk-cifs.patch
bk-cpufreq.patch
bk-cryptodev.patch
bk-driver-core.patch
bk-drm.patch
bk-drm-via.patch
bk-ia64.patch
bk-audit.patch
bk-input.patch
bk-jfs.patch
bk-kbuild.patch
bk-mtd.patch
bk-netdev.patch
bk-nfs.patch
bk-ntfs.patch
bk-scsi.patch
bk-watchdog.patch
Latest versions of subsystem trees
-arm-atomic_sub_and_test.patch
-nfs-fix-typo-in-access-caching-code.patch
-ia64-msi-warning-fixes.patch
-ia64-config_apci_numa-fix.patch
-acpi-ec-warning-fix.patch
-acpi-create_polling_proc-fix.patch
-uml-make-deb-pkg-build-target-build-a-debian-style-user-mode-linux-package.patch
-uml-restore-proper-descriptions-in-make-deb-pkg-target.patch
-doc-describe-kbuild-pitfall.patch
-complete-cpufreq-kconfig-cleanup.patch
-pcnet32-79c975-fiber-fix.patch
-drivers-net-smc-mcac-cleanups.patch
-debug-for-pci-io-mem-allocation.patch
-drivers-scsi-dptih-remove-kernel-22-ifs.patch
-fix-help-for-acpi_container.patch
-bdi-provide-backing-device-capability-information.patch
-cpusets-big-numa-cpu-and-memory-placement-backing_dev-fix.patch
-read_kmem-fixes.patch
-cpusets-special-case-gfp_atomic-allocs.patch
-cpusets-gfp_atomic-fix-tonedown-panic-comment.patch
-cpuset-make-function-decl-ansi.patch
-e1000-flush-work-queues-on-remove.patch
-drivers-net-amd8111ec-fix-napi-interrupt-in-poll.patch
-orinoco-merge-updates-part-the-fourth-wireless-stats-updates.patch
-orinoco-merge-updates-part-the-fourth-ignore_disconnect-flag.patch
-orinoco-merge-updates-part-the-fourth-kill-dump_recs.patch
-orinoco-merge-updates-part-the-fourth-dont-set-channel-in-managed-mode.patch
-orinoco-merge-updates-part-the-fourth-consolidate-allocation-code.patch
-ppp-multilink-fragmentation-improvements.patch
-e100-use-eeprom-config-for-auto-mdi-mdi-x.patch
-ppc32-remove-unnecessary-test-in-mpc52xx-reset-code.patch
-ppc32-remove-the-ocp-system-from-the-freescale-mpc52xx.patch
-ppc32-change-constants-style-in-freescale-mpc52xx.patch
-ppc32-use-platform-bus--ppc_sys-model-for-freescale.patch
-serial-update-mpc52xx_uartc-to-use-platform-bus.patch
-ppc32-adds-necessary-cpu-init-to-use-usb-on-lite5200.patch
-ppc32-cleanup-of-book-e-exception-handling.patch
-ppc32-cpm2-pic-cleanup.patch
-ppc32-cpm2-pic-cleanup-irq_to_siubit-array-updated.patch
-ppc32-fix-mpc8555-mpc8555e-device-lists-updated.patch
-ppc32-mpc8555-cpm2-size-pointers-for-fccs-aka-all-ones-problem.patch
-seccomp-for-ppc64.patch
-ppc64-fix-zilog-link-error.patch
-ppc64-add-mem=x-boot-command-line-option.patch
-x86-reduce-cacheline-bouncing-in-cpu_idle_wait.patch
-x86-via-workaround.patch
-x86-fix-esp-corruption-cpu-bug-take-2.patch
-arch-i386-kernel-smpc-remove-a-pointless-inline.patch
-x86_64-avoid-panic-lockup.patch
-x86_64-reduce-cacheline-bouncing-in-cpu_idle_wait.patch
-x86-64-kprobes-handle-%rip-relative-addressing-mode.patch
-x86-x86_64-reading-deterministic-cache-parameters-and-exporting-it-in-sysfs.patch
-m32r-fix-spinlockh-for-config_debug_spinlock.patch
-m32r-build-fix-for-config_discontigmem.patch
-uml-fix-sigio-spinlock.patch
-uml-gprof-depends-on-tt.patch
-uml-quick-fix-syscall-table.patch
-uml-fixes-a-build-failure-with-config_mode_skas-disabled.patch
-uml-fix-hostfs-special-perm-handling.patch
-uml-correct-error-message.patch
-uml-fix-the-console-stuttering.patch
-make-sysrq-f-call-oom_kill.patch
-cx24110-conexant-frontend-update.patch
-consolidate-asm-ipch.patch
-sx-cli-conversion.patch
-make-documentation-oops-tracingtxt-relevant-to-26.patch
-kill-stupid-warning-when-compiling-riocmdc.patch
-kernel-rcupdatec-make-the-exports-export_symbol_gpl.patch
-nommuc-build-error-fix.patch
-parport-oops-fix.patch
-kprobe_handler-should-check-pre_handler-function.patch
-iput-can-sleep.patch
-zr36050-typo-fix.patch
-ext3-dynamic-allocating-block-reservation-info.patch
-ext3-reservation-info-cleanup-remove-rsv_seqlock.patch
-ext3-reservation-info-cleanup-remove-rsv_seqlock-fix.patch
-ext3-move-goal-logical-block-into-block-allocation-info.patch
-kfree-null-pointer-cleanups-no-need-to-check-fs-ext3.patch
-svcrpc-auth_domain-documentation.patch
-nfsd4-fix-share-conflict-tests.patch
-nfsd4-remove-unneeded-stateowner-arguments.patch
-nfsd4-fix-use-after-put-in-cb_recall.patch
-nfsd4-allow-read-on-open-for-write.patch
-nfsd4-factor-out-common-open_truncate-code.patch
-nfsd4-fix-failure-to-truncate-on-some-opens.patch
-nfsd4_remove_unused_acl_function.patch
-nfsd4-dont-set-write_owner-in-either-allow-or-deny-bits.patch
-nfsd4-acl-dont-set-named-attrs.patch
-nfsd4-acl-error-fix.patch
-nfsd4-rename-release_delegation.patch
-nfsd4-remove-trailing-whitespace-from-nfs4procc.patch
-nfsd4-fix-open-returns-for-other-claim-types.patch
-nfsd4-fix-indentation-in-nfsd4_open.patch
-sched2-fix-schedstats-warning.patch
-vt-dont-call-unblank-at-irq-time.patch
-ppc32-move-powermac-backlight-stuff-to-a-workqueue.patch
-radeonfb-implement-proper-workarounds-for-pll-accesses.patch
-radeonfb-ddc-i2c-fix.patch
-fbdev-nvidia-licensing-clarification.patch
-fbcon-stop-framebuffer-operations-before-hardware-is-properly-initialized.patch
-nvidiafb-maximize-blit-buffer-capacity.patch
-nvidiafb-fix-section-references.patch
-nvidiafb-process-boot-options-earlier.patch
-nvidiafb-kconfig-help-text-update-for-config-fb_nvidia.patch
-nvidiafb-delete-i2c-bus-on-driver-unload.patch
-pm2fb-x-and-vt-switching-crash-fix.patch
-fbdev-cleanups-in-drivers-video-part-2.patch
-fbdev-cleanups-in-drivers-video-part-2-fix.patch
-excessive-atyfb-debug-messages.patch
-atyfb-add-boot-module-option-to-override-composite-sync.patch
-fbdev-kconfig-fix-for-macmodes-and-ppc.patch
-fbdev-convert-drivers-to-pci_register_driver.patch
-sisfb-trivial-cleanups.patch
-tridentfb-clean-up-printks.patch
-s1d13xxxfb-add-support-for-epson-s1d13806-fb.patch
-fbcon-save-var-rotate-field-in-struct-display.patch
-fbcon-call-set_par-per-fb_info-once-during-init.patch
-fbcon-do-not-set-palette-if-console-is-not-visible.patch
-neofb-mmio-fixes.patch
-neofb-set-hwaccel-flags-properly.patch
-remove-redundant-null-checks-before-kfree-in-drivers-video.patch
-remove-redundant-null-checks-before-kfree-in-drivers-video-fix.patch
-fix-matroxfb-on-big-endian-hardware.patch
-radeonfb-fix-mode-setting-on-crt-monitors.patch
-radeonfb-preserve-tmds-setting.patch
-fix-atyfb-build-on-ppc.patch
-doc-where-to-find-ldd3.patch
Merged
-linus.patch
There's nothing there.
+bk-acpi-alpha-build-fix.patch
Fix bk-acpi for non-ACPI machines.
+fix-agp-code-to-work-again-with-non-pci-agp-bridges.patch
agp fix
+add-suspend-method-to-cpufreq-core.patch
+add-suspend-method-to-cpufreq-core-warning-fix.patch
cpufreq suspend support
-bk-driver-core-noisiness.patch
Dropped (although it's still needed)
+bk-driver-core-fix.patch
Revert dud patch in bk-driver-core.patch
-bk-ide-dev.patch
Too many bk conflicts for me.
+bk-driver-core-sn2-build-fix.patch
Fix bk-driver-core for sn2.
+quiet-ide-cd-warning.patch
Kill compile warning.
+serio-resume-fix.patch
+alps-resume-fix.patch
+serport-oops-fix.patch
+serio-id-attributes.patch
input driver resume fixes
+tulip-fix-for-64-bit-mips.patch
+pcnet_csc-irq-handler-optimization.patch
net driver fixes
+pci_module_init-pci_register_driver.patch
pci_module_init() conversions.
+usb-turn-a-user-mode-driver-error-into-a-hard-error.patch
USB fix
+create-mm-kconfig-for-arch-independent-memory-options.patch
+make-each-arch-use-mm-kconfig.patch
+update-all-defconfigs-for-arch_discontigmem_enable.patch
+introduce-new-kconfig-option-for-numa-or-discontig.patch
More sparsemem preparatory work.
+oom-killer-disable-for-iscsi-lvm2-multipath-userland-critical-sections.patch
per-process oom-killer override
+vmscan-pageout-remove-unneeded-test.patch
+end_buffer_write_sync-avoid-pointless-assignments.patch
Little cleanups
+meminfo-add-cached-underflow-check.patch
/proc/meminfo fix
+ppc32-fix-bogosity-in-process-freezing-code.patch
+ppc32-ppc4xx_pic-add-acknowledge-when-enabling-level-sensitive-irq.patch
+ppc32-improve-timebase-sync-for-smp.patch
+ppc32-oops-on-kernel-altivec-assist-exceptions.patch
+ppc32-fix-single-stepping-of-emulated-instructions.patch
+ppc32-fix-errata-for-some-g3-cpus.patch
+ppc32-fix-cpufreq-problems.patch
+ppc64-fix-semantics-of-__ioremap.patch
ppc32, ppc64 updates
+mips-remove-obsolete-vr41xx-rtc-function.patch
+mips-update-vr41xx-cpu-pci-bridge.patch
MIPS fixes
+sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
scheduler clock accuracy fix
+x86_64-use-a-vma-for-the-32bit-vsyscall.patch
x86_64 fix
-x86_64-remove-duplicated-sys_time64.patch
-x86_64-remove-dup-syscall.patch
Andi spat these out.
+x86_64-genapic-update.patch
x86_64 APIC handling fixes
+pm_message_t-more-fixes-in-common-and-i386.patch
+fix-u32-vs-pm_message_t-in-drivers-char.patch
+u32-vs-pm_message_t-fixes-for-drivers-net.patch
+fix-u32-vs-pm_message_t-in-pcmcia.patch
+fix-u32-vs-pm_message_t-in-drivers-media.patch
+fix-u32-vs-pm_message_t-in-drivers-message.patch
+fix-u32-vs-pm_message_t-in-drivers-mmcmtdscsi.patch
+fix-pm_message_t-vs-u32-in-alsa.patch
+fix-u32-vs-pm_message_t-in-x86-64.patch
+fix-u32-vs-pm_message_t-in-drivers-macintosh.patch
+fix-u32-vs-pm_message_t-in-pci-pcie.patch
+u32-vs-pm_message_t-in-ppc-and-radeon.patch
More u32->pm_message_t fixes
+uml-fix-compilation-for-__choose_mode-addition.patch
UML fix
+keys-make-request-key-create-an-authorisation-key-fix.patch
Fix keys-make-request-key-create-an-authorisation-key.patch
-timers-prepare-for-del_timer_sync-changes.patch
-timers-rework-del_timer_sync.patch
-timers-serialize-timers.patch
-timers-remove-memory-barriers.patch
-timers-cleanup-kill-__get_base.patch
-timers-enable-irqs-in-__mod_timer.patch
-timers-enable-irqs-in-__mod_timer-tidy.patch
+timers-fixes-improvements.patch
+timers-fixes-improvements-smp_processor_id-fix.patch
+timers-fixes-improvements-fix.patch
New kernel timer speedup patchset
+quota-fix-possible-oops-on-quotaoff.patch
+quota-possible-bug-in-quota-format-v2-support.patch
Quota fixes
+kill-ifndef-have_arch_get_signal_to_deliver-in-signalc.patch
cleanup
+officially-deprecate-register_ioctl32_conversion.patch
deprecate a compat function (mainly affects DRI)
+undo-do_readv_writev-behavior-change.patch
Fix readv/writev return value
+kprobes-incorrect-handling-of-probes-on-ret-lret-instruction.patch
kprobes fix
+sysfs-for-ipmi-for-new-mm-kernels.patch
IPMI fix
+remove-all-kernel-bugs.patch
Permit BUG() and BUG_ON() to generate no code.
+exterminate-page_bug.patch
Remove PAGE_BUG()
+clean-up-kernel-messages.patch
Permit all printk's and their associated code and data to be absent fro the
kernel image.
+move-sa_xxx-defines-to-linux-signalh.patch
signal header cleanup
+procfs-fix-hardlink-counts.patch
+procfs-fix-hardlink-counts-for-proc-pid-task.patch
profs fixes
+show-thread_info-flags-in-proc-pid-status.patch
Additional process into in /proc (I meant to drop this - it'll break m68k)
+direct-io-async-short-read-fix.patch
Fix AIO/DIO read return values.
+set-ms_active-bit-before-calling-fill_super.patch
Fix weird oopses in isofs mount versus inode reclaim.
+some-changes-and-extensions-to-the-kernel-documentation.patch
kerneldoc fixes
+kernel-rcupdatec-make-the-exports-export_symbol_gpl.patch
+add-deprecated_for_modules.patch
+add-deprecated_for_modules-fix.patch
+deprecate-synchronize_kernel-gpl-replacement.patch
+deprecate-synchronize_kernel-gpl-replacement-fix.patch
+change-synchronize_kernel-to-_rcu-and-_sched.patch
+update-rcu-documentation.patch
Various changes to the RCU interfaces
+fix-comment-in-listh-that-refers-to-nonexistent-api.patch
Fix buggy comment
+pnpbios-eliminate-bad-section-references.patch
+hd-eliminate-bad-section-references.patch
+efi-eliminate-bad-section-references.patch
Some section fixes
+create-a-kstrdup-library-function.patch
+create-a-kstrdup-library-function-fixes.patch
kstrdup().
+add-big-endian-variants-of-ioread-iowrite.patch
big-endian I/O funtions.
-inotify-43.patch
+inotify-022-for-2612-rc1-mm4.patch
Another inotify release.
+ipoib-set-skb-macraw-on-receive.patch
+ipoib-fix-static-rate-calculation.patch
+ipoib-convert-to-debugfs.patch
+ipoib-document-conversion-to.patch
+ib-keep-mad-work-completion-valid.patch
+ib-remove-unneeded-includes.patch
+ib-fix-fmr-pool-crash.patch
+ib-trivial-fmr-printk-cleanup.patch
+ib-fix-user-mad-registrations-with-class-0.patch
+ib-remove-incorrect-comments.patch
+ib-mthca-map-mpt-mtt-context-in-mem-free-mode.patch
+ib-mthca-fill-in-more-device-query-fields.patch
+ib-mthca-fix-calculation-of-rdb-shift.patch
+ib-mthca-fix-posting-sends-with-immediate-data.patch
+ib-mthca-allow-unaligned-memory-regions.patch
+ib-mthca-allocate-correct-number-of-doorbell-pages.patch
+ib-mthca-clean-up-mthca_dereg_mr.patch
+ib-mthca-fix-mr-allocation-error-path.patch
+ib-mthca-release-mutex-on-doorbell-alloc-error-path.patch
+ib-mthca-print-assigned-irq-when-interrupt-test-fails.patch
+ib-mthca-only-free-doorbell-records-in-mem-free-mode.patch
+ib-mthca-fix-format-of-cq-number-for-cq-events.patch
+ib-mthca-implement-rdma-atomic-operations-for-mem-free-mode.patch
+ib-mthca-fix-mtt-allocation-in-mem-free-mode.patch
+ib-mthca-fill-in-opcode-field-for-send-completions.patch
+ib-mthca-allow-address-handle-creation-in-interrupt-context.patch
+ib-mthca-encapsulate-mtt-buddy-allocator.patch
+ib-mthca-add-sync_tpt-firmware-command.patch
+ib-mthca-add-mthca_write64_raw-for-writing-to-mtt-table-directly.patch
+ib-mthca-add-mthca_table_find-function.patch
+ib-mthca-split-mr-key-munging-routines.patch
+ib-mthca-add-fast-memory-region-implementation.patch
+ib-mthca-tweaks-to-mthca_cmdc.patch
+ib-mthca-encapsulate-mem-free-check-into-mthca_is_memfree.patch
+ib-mthca-map-context-for-rdma-responder-in-mem-free-mode.patch
+ib-mthca-update-receive-queue-initialization-for-new-hcas.patch
+ib-mthca-add-support-for-new-mt25204-hca.patch
Infiniband update
+jbd-dirty-buffer-leak-fix.patch
Fix ext3 memleak
+pcmcia-resource-handling-fixes.patch
pcmcia fix
+nfs-client-latencies.patch
Reduce scheduling latencies in NFS
-figure-out-who-is-inserting-bogus-modules.patch
Dropped - old debuggig stuff.
+perfctr-ppc64-arch-hooks.patch
+perfctr-common-updates-for-ppc64.patch
+perfctr-ppc64-driver-core.patch
perfctr updates
+sched-remove-unnecessary-sched-domains.patch
+sched-improve-pinned-task-handling-again.patch
+sched-cleanup-context-switch-locking.patch
CPU scheduler updates
+make-page-becoming-writable-notification-a-vma-op-only.patch
+make-page-becoming-writable-notification-a-vma-op-only-kafs-fix.patch
Rework the page_becoming_writable() implementation.
+kdump-sysrq-trigger-mechanism-for-kexec-based-crashdumps.patch
Add a sysrq key to force a kdump
+fuse-device-functions-abi-version-change.patch
+fuse-read-only-operations-add-offset-to-fuse_dirent.patch
+fuse-read-only-operations-readdir-fixes.patch
+fuse-add-padding.patch
+fuse-direct-i-o-fix-warning-on-x86_64.patch
+fuse-add-fsync-operation-for-directories.patch
FUSE updates
number of patches in -mm: 634
number of changesets in external trees: 698
number of patches in -mm only: 612
total patches: 1310
All 634 patches:
bk-acpi.patch
bk-acpi-alpha-build-fix.patch
bk-acpi alpha build fix
acpi-toshiba-failure-handling.patch
acpi: Toshiba failure handling
acpi-video-pointer-size-fix.patch
acpi video pointer size fix
bk-agpgart.patch
agp-fix-for-xen-vmm.patch
AGP fix for Xen VMM
fix-agp-code-to-work-again-with-non-pci-agp-bridges.patch
fix AGP code to work again with non-PCI AGP bridges
include-linux-soundcardh-endianness-fix.patch
include/linux/soundcard.h: endianness fix
bk-cifs.patch
bk-cpufreq.patch
add-suspend-method-to-cpufreq-core.patch
Add suspend method to cpufreq core
add-suspend-method-to-cpufreq-core-warning-fix.patch
add-suspend-method-to-cpufreq-core-warning-fix
powernow-k7recalibrate-cpu_khz.patch
powernowk7: recalibrate cpu_khz
cpufreq-timers-recalibrate_cpu_khz.patch
cpufreq timers: recalibrate cpu_khz
bk-cryptodev.patch
bk-driver-core.patch
bk-driver-core-fix.patch
bk-driver-core fix
fix-typo-in-scdrv_init.patch
Fix typo in scdrv_init()
export-platform_add_devices.patch
export platform_add_devices
fix-ver_linux-script-for-no-udev-utils.patch
Fix ver_linux script for no udev utils.
bk-drm.patch
bk-drm-via.patch
bk-ia64.patch
bk-driver-core-sn2-build-fix.patch
bk-driver-core sn build fix
bk-audit.patch
quiet-ide-cd-warning.patch
quiet ide-cd warning
bk-input.patch
alps-printk-tidy.patch
alps-printk-tidy
serio-resume-fix.patch
serio resume fix
alps-resume-fix.patch
ALPS resume fix
serport-oops-fix.patch
serport oops fix
serio-id-attributes.patch
serio 'id' attributes
bk-jfs.patch
bk-kbuild.patch
use-cross_compileinstallkernel-in-arch-boot-installsh.patch
use ${CROSS_COMPILE}installkernel in arch/*/boot/install.sh
kconfig-i18n-support.patch
Kconfig i18n support
libata-flush-comreset-set-and-clear.patch
libata: flush COMRESET set and clear
bk-mtd.patch
bk-netdev.patch
tulip-fix-for-64-bit-mips.patch
tulip: fix for 64-bit mips
pcnet_csc-irq-handler-optimization.patch
pcnet_cs.c: IRQ handler optimization
bk-nfs.patch
bk-ntfs.patch
pci_module_init-pci_register_driver.patch
pci_module_init -> pci_register_driver
pci-pci-transparent-bridge-handling-improvements-pci-core.patch
PCI-PCI transparent bridge handling improvements (pci core)
pci-pci-transparent-bridge-handling-improvements-yenta_socket.patch
PCI-PCI transparent bridge handling improvements (yenta_socket)
acpi-bridge-hotadd-acpi-based-root-bridge-hot-add.patch
acpi bridge hotadd: ACPI based root bridge hot-add
acpi-bridge-hotadd-fix-pci_enable_device-for-p2p-bridges.patch
acpi bridge hotadd: Fix pci_enable_device() for p2p bridges
acpi-bridge-hotadd-make-pcibios_fixup_bus-hot-plug-safe.patch
acpi bridge hotadd: Make pcibios_fixup_bus() hot-plug safe
acpi-bridge-hotadd-prevent-duplicate-bus-numbers-when-scanning-pci-bridge.patch
acpi bridge hotadd: Prevent duplicate bus numbers when scanning PCI bridge
acpi-bridge-hotadd-take-the-pci-lock-when-modifying-pci-bus-or-device-lists.patch
acpi bridge hotadd: Take the PCI lock when modifying pci bus or device lists
acpi-bridge-hotadd-link-newly-created-pci-child-bus-to-its-parent-on-creation.patch
acpi bridge hotadd: Link newly created pci child bus to its parent on creation
acpi-bridge-hotadd-make-the-pci-remove-routines-safe-for-failed-hot-plug.patch
acpi bridge hotadd: Make the PCI remove routines safe for failed hot-plug
acpi-bridge-hotadd-remove-hot-plugged-devices-that-could-not-be-allocated-resources.patch
acpi bridge hotadd: Remove hot-plugged devices that could not be allocated resources
acpi-bridge-hotadd-read-bridge-resources-when-fixing-up-the-bus.patch
acpi bridge hotadd: Read bridge resources when fixing up the bus
acpi-bridge-hotadd-allow-acpi-add-and-start-operations-to-be-done-independently.patch
acpi bridge hotadd: Allow ACPI .add and .start operations to be done independently
acpi-bridge-hotadd-export-the-interface-to-get-pci-id-for-an-acpi-handle.patch
acpi bridge hotadd: Export the interface to get PCI id for an ACPI handle
bk-scsi.patch
megaraid_sas-announcing-new-module-for.patch
megaraid_sas: new module for LSI Logic's SAS based MegaRAID controllers
add-scsi-changer-driver.patch
add scsi changer driver
scsi-ch-build-fix.patch
scsi ch.c build fix
usb-wacom-tablet-driver.patch
usb wacom tablet driver
add-new-wacom-device-to-usb-hid-core-list.patch
add new wacom device to usb hid-core list
usb_cdc-build-fix.patch
usb_cdc build fix
usb-resume-fixes.patch
usb resume fixes
usb-suspend-updates-interface-suspend.patch
usb suspend updates (interface suspend)
hcd-suspend-uses-pm_message_t.patch
hcd suspend uses pm_message_t
zd1201-build-fix.patch
zd1201 build fix
usb-support-for-new-ipod-mini-and-possibly-others.patch
usb: support for new ipod mini (and possibly others)
pm-support-for-zd1201.patch
PM support for zd1201
bug-fix-in-usbdevfs.patch
bug fix in usbdevfs
usb-turn-a-user-mode-driver-error-into-a-hard-error.patch
usb: turn a user mode driver error into a hard error
bk-watchdog.patch
mm.patch
add -mmN to EXTRAVERSION
swapspace-layout-improvements.patch
swapspace-layout-improvements
/proc/swaps negative Used
add-a-clear_pages-function-to-clear-pages-of-higher.patch
add a clear_pages function to clear pages of higher order
vmscan-notice-slab-shrinking.patch
vmscan: notice slab shrinking
madvise-do-not-split-the-maps.patch
madvise: do not split the maps
madvise-merge-the-maps.patch
madvise: merge the maps
freepgt-free_pgtables-use-vma-list.patch
freepgt: free_pgtables use vma list
freepgt-remove-mm_vm_sizemm.patch
freepgt: remove MM_VM_SIZE(mm)
freepgt-hugetlb_free_pgd_range.patch
freepgt: hugetlb_free_pgd_range
freepgt-hugetlb_free_pgd_range-fix-aio-panic-fix.patch
ppc64-fix-aio-panic-caused-by-is_hugepage_only_range-ia64-fix
freepgt-remove-arch-pgd_addr_end.patch
freepgt: remove arch pgd_addr_end
freepgt-mpnt-to-vma-cleanup.patch
freepgt: mpnt to vma cleanup
freepgt-hugetlb-area-is-clean.patch
freepgt: hugetlb area is clean
remove-non-discontig-use-of-pgdat-node_mem_map.patch
remove non-DISCONTIG use of pgdat->node_mem_map
resubmit-sparsemem-base-early_pfn_to_nid-works-before-sparse-is-initialized.patch
sparsemem base: early_pfn_to_nid() (works before sparse is initialized)
resubmit-sparsemem-base-simple-numa-remap-space-allocator.patch
sparsemem base: simple NUMA remap space allocator
resubmit-sparsemem-base-reorganize-page-flags-bit-operations.patch
sparsemem base: reorganize page->flags bit operations
resubmit-sparsemem-base-teach-discontig-about-sparse-ranges.patch
sparsemem base: teach discontig about sparse ranges
create-mm-kconfig-for-arch-independent-memory-options.patch
create mm/Kconfig for arch-independent memory options
make-each-arch-use-mm-kconfig.patch
make each arch use mm/Kconfig
update-all-defconfigs-for-arch_discontigmem_enable.patch
update all defconfigs for ARCH_DISCONTIGMEM_ENABLE
introduce-new-kconfig-option-for-numa-or-discontig.patch
Introduce new Kconfig option for NUMA or DISCONTIG
filemap_getpage-can-block-when-map_nonblock-specified.patch
filemap_getpage can block when MAP_NONBLOCK specified
add-kmalloc_node-inline-cleanup.patch
add kmalloc_node, inline cleanup
oom-killer-disable-for-iscsi-lvm2-multipath-userland-critical-sections.patch
oom-killer disable for iscsi/lvm2/multipath userland critical sections
vmscan-pageout-remove-unneeded-test.patch
vmscan: pageout(): remove unneeded test
end_buffer_write_sync-avoid-pointless-assignments.patch
end_buffer_write_sync() avoid pointless assignments
meminfo-add-cached-underflow-check.patch
meminfo: add Cached underflow check
eni155p-error-handling-fix.patch
ENI155P error handling fix
a-new-10gb-ethernet-driver-by-chelsio-communications.patch
A new 10GB Ethernet Driver by Chelsio Communications
dm9000-network-driver.patch
DM9000 network driver
ppc32-fix-bogosity-in-process-freezing-code.patch
ppc32: fix bogosity in process-freezing code
ppc32-ppc4xx_pic-add-acknowledge-when-enabling-level-sensitive-irq.patch
ppc32: ppc4xx_pic - add acknowledge when enabling level-sensitive IRQ
ppc32-improve-timebase-sync-for-smp.patch
ppc32: improve timebase sync for SMP
ppc32-oops-on-kernel-altivec-assist-exceptions.patch
ppc32: oops on kernel altivec assist exceptions
ppc32-fix-single-stepping-of-emulated-instructions.patch
ppc32: fix single-stepping of emulated instructions
ppc32-fix-errata-for-some-g3-cpus.patch
ppc32: Fix errata for some G3 CPUs
ppc32-fix-cpufreq-problems.patch
ppc32: Fix cpufreq problems
ppc64-fix-semantics-of-__ioremap.patch
ppc64: Fix semantics of __ioremap
mips-remove-obsolete-vr41xx-rtc-function.patch
mips: remove obsolete VR41xx RTC function from vr41xx.h
mips-update-vr41xx-cpu-pci-bridge.patch
mips: update VR41xx CPU-PCI bridge support
fix-i386-memcpy.patch
fix i386 memcpy
i386-x86_64-segment-register-access-update.patch
i386/x86_64 segment register access update
rfc-check-nmi-watchdog-is-broken.patch
check nmi watchdog is broken
sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
sched: x86 sched_clock() to use TSC on CONFIG_HPET or CONFIG_NUMA systems
x86_64-show_stack-touch_nmi_watchdog.patch
x86_64 show_stack(): call touch_nmi_watchdog
x86_64-use-a-vma-for-the-32bit-vsyscall.patch
x86_64: Use a VMA for the 32bit vsyscall
x86-x86_64-intel-dual-core-detection.patch
x86, x86_64: Intel dual-core detection
x86-cacheline-alignment-for-cpu-maps.patch
x86: cacheline alignment for cpu maps
x86_64-genapic-update.patch
x86_64 genapic update
ia64-reduce-cacheline-bouncing-in-cpu_idle_wait.patch
ia64: reduce cacheline bouncing in cpu_idle_wait
pm_message_t-more-fixes-in-common-and-i386.patch
pm_message_t: more fixes in common and i386
fix-u32-vs-pm_message_t-in-drivers-char.patch
Fix u32 vs. pm_message_t in drivers/char
u32-vs-pm_message_t-fixes-for-drivers-net.patch
u32 vs. pm_message_t fixes for drivers/net
fix-u32-vs-pm_message_t-in-pcmcia.patch
fix u32 vs. pm_message_t in pcmcia
fix-u32-vs-pm_message_t-in-drivers-media.patch
fix u32 vs. pm_message_t in drivers/media
fix-u32-vs-pm_message_t-in-drivers-message.patch
fix u32 vs. pm_message_t in drivers/message
fix-u32-vs-pm_message_t-in-drivers-mmcmtdscsi.patch
fix u32 vs. pm_message_t in drivers/mmc,mtd,scsi
fix-pm_message_t-vs-u32-in-alsa.patch
fix pm_message_t vs. u32 in alsa
fix-u32-vs-pm_message_t-in-x86-64.patch
Fix u32 vs. pm_message_t in x86-64
fix-u32-vs-pm_message_t-in-drivers-macintosh.patch
fix u32 vs. pm_message_t in drivers/macintosh
fix-u32-vs-pm_message_t-in-pci-pcie.patch
fix u32 vs. pm_message_t in PCI, PCIE
u32-vs-pm_message_t-in-ppc-and-radeon.patch
u32 vs. pm_message_t in ppc and radeon
uml-fix-compilation-for-__choose_mode-addition.patch
uml: fix compilation for __CHOOSE_MODE addition
mtrr-size-and-base-debug.patch
mtrr size-and-base debugging
iounmap-debugging.patch
iounmap debugging
detect-soft-lockups.patch
detect soft lockups
detect-soft-lockups-from-touch_nmi_watchdog.patch
detect-soft-lockups: call from touch_nmi_watchdog
areca-raid-linux-scsi-driver.patch
ARECA RAID Linux scsi driver
rt-lsm.patch
RT-LSM
tty-output-lossage-fix.patch
tty output lossage fix
nice-and-rt-prio-rlimits.patch
nice and rt-prio rlimits
relayfs.patch
relayfs
relayfs-properly-handle-oversized-events.patch
relayfs: properly handle oversized events
relayfs-backing_dev-fix.patch
relayfs-backing_dev-fix
cfq-iosched-update-to-time-sliced-design.patch
cfq-iosched: update to time sliced design
cfq-iosched-update-to-time-sliced-design-export-task_nice.patch
cfq-iosched-update-to-time-sliced-design-export-task_nice
cfq-iosched-update-to-time-sliced-design-fix.patch
cfq-iosched-update-to-time-sliced-design fix
cfq-iosched-update-to-time-sliced-design-fix-fix.patch
cfq-iosched-update-to-time-sliced-design-fix-fix
cfq-iosched-update-to-time-sliced-design-use-bio_data_dir.patch
cfq-iosched-update-to-time-sliced-design: use bio_data_dir()
cfq-ioschedc-fix-soft-hang-with-non-fs-requests.patch
cfq-iosched.c: fix soft hang with non-fs requests
keys-discard-key-spinlock-and-use-rcu-for-key-payload.patch
keys: Discard key spinlock and use RCU for key payload
keys-discard-key-spinlock-and-use-rcu-for-key-payload-try-4.patch
keys: Discard key spinlock and use RCU for key payload - try #4
keys-pass-session-keyring-to-call_usermodehelper.patch
Keys: Pass session keyring to call_usermodehelper()
keys-pass-session-keyring-to-call_usermodehelper-fix.patch
keys-pass-session-keyring-to-call_usermodehelper fix
keys-use-rcu-to-manage-session-keyring-pointer.patch
Keys: Use RCU to manage session keyring pointer
keys-make-request-key-create-an-authorisation-key.patch
Keys: Make request-key create an authorisation key
keys-make-request-key-create-an-authorisation-key-fix.patch
Keys: Make request-key create an authorisation key (fix)
binfmt_elf-bss-padding-fix.patch
binfmt_elf bss padding fix
timers-fixes-improvements.patch
timers fixes/improvements
timers-fixes-improvements-smp_processor_id-fix.patch
timers-fixes-improvements-smp_processor_id-fix
timers-fixes-improvements-fix.patch
timers fixes/improvements fix
enable-sig_ign-on-blocked-signals.patch
Enable SIG_IGN on blocked signals
async-io-using-rt-signals.patch
AYSNC IO using singals other than SIGIO
kernel-paramc-dont-use-max-when-num-is-null-in.patch
kernel/param.c: don't use .max when .num is NULL in param_array_set()
fix-module_param_string-calls.patch
fix module_param_string() calls
use-cheaper-elv_queue_empty-when-unplug-a-device.patch
use cheaper elv_queue_empty when unplug a device
fixup-newly-added-jsm-driver.patch
fix up newly added jsm driver
ext2-corruption-regression-between-269-and-2610.patch
ext2 corruption - regression between 2.6.9 and 2.6.10
quota-fix-possible-oops-on-quotaoff.patch
quota: fix possible oops on quotaoff
quota-possible-bug-in-quota-format-v2-support.patch
quota: possible bug in quota format v2 support
kill-ifndef-have_arch_get_signal_to_deliver-in-signalc.patch
kill #ifndef HAVE_ARCH_GET_SIGNAL_TO_DELIVER in signal.c
officially-deprecate-register_ioctl32_conversion.patch
officially deprecate register_ioctl32_conversion
undo-do_readv_writev-behavior-change.patch
undo do_readv_writev() behavior change
kprobes-incorrect-handling-of-probes-on-ret-lret-instruction.patch
Kprobes: Incorrect handling of probes on ret/lret instruction
sysfs-for-ipmi-for-new-mm-kernels.patch
sysfs for IPMI
remove-all-kernel-bugs.patch
remove all kernel BUGs
exterminate-page_bug.patch
Exterminate PAGE_BUG
clean-up-kernel-messages.patch
clean up kernel messages
move-sa_xxx-defines-to-linux-signalh.patch
move SA_xxx defines to linux/signal.h
procfs-fix-hardlink-counts.patch
procfs: Fix hardlink counts
procfs-fix-hardlink-counts-for-proc-pid-task.patch
procfs: Fix hardlink counts for /proc/<PID>/task
show-thread_info-flags-in-proc-pid-status.patch
Show thread_info->flags in /proc/PID/status
direct-io-async-short-read-fix.patch
Direct IO async short read fix
set-ms_active-bit-before-calling-fill_super.patch
Set MS_ACTIVE bit before calling ->fill_super functions
some-changes-and-extensions-to-the-kernel-documentation.patch
Some changes and extensions to the Kernel documentation
kernel-rcupdatec-make-the-exports-export_symbol_gpl.patch
kernel/rcupdate.c: make the exports EXPORT_SYMBOL_GPL
add-deprecated_for_modules.patch
Add deprecated_for_modules
add-deprecated_for_modules-fix.patch
deprecate-synchronize_kernel-gpl-replacement fix
deprecate-synchronize_kernel-gpl-replacement.patch
Deprecate synchronize_kernel, GPL replacement
deprecate-synchronize_kernel-gpl-replacement-fix.patch
deprecate-synchronize_kernel-gpl-replacement-fix
change-synchronize_kernel-to-_rcu-and-_sched.patch
Change synchronize_kernel to _rcu and _sched
update-rcu-documentation.patch
Update RCU documentation
fix-comment-in-listh-that-refers-to-nonexistent-api.patch
Fix comment in list.h that refers to nonexistent API
pnpbios-eliminate-bad-section-references.patch
pnpbios: eliminate bad section references
hd-eliminate-bad-section-references.patch
hd: eliminate bad section references
efi-eliminate-bad-section-references.patch
efi: eliminate bad section references
create-a-kstrdup-library-function.patch
create a kstrdup library function
create-a-kstrdup-library-function-fixes.patch
create-a-kstrdup-library-function-fixes
add-big-endian-variants-of-ioread-iowrite.patch
add Big Endian variants of ioread/iowrite
inotify-022-for-2612-rc1-mm4.patch
inotify 0.22 for 2.6.12-rc1-mm4
ipoib-set-skb-macraw-on-receive.patch
IPoIB: set skb->mac.raw on receive
ipoib-fix-static-rate-calculation.patch
IPoIB: fix static rate calculation
ipoib-convert-to-debugfs.patch
IPoIB: convert to debugfs
ipoib-document-conversion-to.patch
IPoIB: document conversion to debugfs
ib-keep-mad-work-completion-valid.patch
IB: Keep MAD work completion valid
ib-remove-unneeded-includes.patch
IB: remove unneeded includes
ib-fix-fmr-pool-crash.patch
IB: Fix FMR pool crash
ib-trivial-fmr-printk-cleanup.patch
IB: Trivial FMR printk cleanup
ib-fix-user-mad-registrations-with-class-0.patch
IB: Fix user MAD registrations with class 0
ib-remove-incorrect-comments.patch
IB: Remove incorrect comments
ib-mthca-map-mpt-mtt-context-in-mem-free-mode.patch
IB/mthca: map MPT/MTT context in mem-free mode
ib-mthca-fill-in-more-device-query-fields.patch
IB/mthca: fill in more device query fields
ib-mthca-fix-calculation-of-rdb-shift.patch
IB/mthca: fix calculation of RDB shift
ib-mthca-fix-posting-sends-with-immediate-data.patch
IB/mthca: fix posting sends with immediate data
ib-mthca-allow-unaligned-memory-regions.patch
IB/mthca: allow unaligned memory regions
ib-mthca-allocate-correct-number-of-doorbell-pages.patch
IB/mthca: allocate correct number of doorbell pages
ib-mthca-clean-up-mthca_dereg_mr.patch
IB/mthca: clean up mthca_dereg_mr()
ib-mthca-fix-mr-allocation-error-path.patch
IB/mthca: fix MR allocation error path
ib-mthca-release-mutex-on-doorbell-alloc-error-path.patch
IB/mthca: release mutex on doorbell alloc error path
ib-mthca-print-assigned-irq-when-interrupt-test-fails.patch
IB/mthca: print assigned IRQ when interrupt test fails
ib-mthca-only-free-doorbell-records-in-mem-free-mode.patch
IB/mthca: only free doorbell records in mem-free mode
ib-mthca-fix-format-of-cq-number-for-cq-events.patch
IB/mthca: fix format of CQ number for CQ events
ib-mthca-implement-rdma-atomic-operations-for-mem-free-mode.patch
IB/mthca: implement RDMA/atomic operations for mem-free mode
ib-mthca-fix-mtt-allocation-in-mem-free-mode.patch
IB/mthca: fix MTT allocation in mem-free mode
ib-mthca-fill-in-opcode-field-for-send-completions.patch
IB/mthca: fill in opcode field for send completions
ib-mthca-allow-address-handle-creation-in-interrupt-context.patch
IB/mthca: allow address handle creation in interrupt context
ib-mthca-encapsulate-mtt-buddy-allocator.patch
IB/mthca: encapsulate MTT buddy allocator
ib-mthca-add-sync_tpt-firmware-command.patch
IB/mthca: add SYNC_TPT firmware command
ib-mthca-add-mthca_write64_raw-for-writing-to-mtt-table-directly.patch
IB/mthca: add mthca_write64_raw() for writing to MTT table directly
ib-mthca-add-mthca_table_find-function.patch
IB/mthca: add mthca_table_find() function
ib-mthca-split-mr-key-munging-routines.patch
IB/mthca: split MR key munging routines
ib-mthca-add-fast-memory-region-implementation.patch
IB/mthca: add fast memory region implementation
ib-mthca-tweaks-to-mthca_cmdc.patch
IB/mthca: tweaks to mthca_cmd.c
ib-mthca-encapsulate-mem-free-check-into-mthca_is_memfree.patch
IB/mthca: encapsulate mem-free check into mthca_is_memfree()
ib-mthca-map-context-for-rdma-responder-in-mem-free-mode.patch
IB/mthca: map context for RDMA responder in mem-free mode
ib-mthca-update-receive-queue-initialization-for-new-hcas.patch
IB/mthca: update receive queue initialization for new HCAs
ib-mthca-add-support-for-new-mt25204-hca.patch
IB/mthca: add support for new MT25204 HCA
jbd-dirty-buffer-leak-fix.patch
jbd dirty buffer leak fix
pcmcia-hotplug-event-for-pcmcia-devices.patch
pcmcia: hotplug event for PCMCIA devices
pcmcia-hotplug-event-for-pcmcia-socket-devices.patch
pcmcia: hotplug event for PCMCIA socket devices
pcmcia-device-and-driver-matching.patch
pcmcia: device and driver matching
pcmcia-check-for-invalid-crc32-hashes-in-id_tables.patch
pcmcia: check for invalid crc32 hashes in id_tables
pcmcia-match-for-fake-cis.patch
pcmcia: match for fake CIS
pcmcia-export-cis-in-sysfs.patch
pcmcia: export CIS in sysfs
pcmcia-cis-overrid-via-sysfs.patch
pcmcia: CIS overrid via sysfs
pcmcia-match-anonymous-cards.patch
pcmcia: match "anonymous" cards
pcmcia-allow-function-id-based-match.patch
pcmcia: allow function-ID based match
pcmcia-file2alias.patch
pcmcia: file2alias
pcmcia-request-cis-via-firmware-interface.patch
pcmcia: request CIS via firmware interface
pcmcia-cleanups.patch
pcmcia: cleanups
pcmcia-rescan-bus-always-upon-echoing-into-setup_done.patch
pcmcia: rescan bus always upon echoing into setup_done
pcmcia-id_table-for-serial_cs.patch
pcmcia: id_table for serial_cs
pcmcia-id_table-for-3c574_cs.patch
pcmcia: id_table for 3c574_cs
pcmcia-id_table-for-3c589_cs.patch
pcmcia: id_table for 3c589_cs
pcmcia-id_table-for-aha152x.patch
pcmcia: id_table for aha152x
pcmcia-id_table-for-airo_cs.patch
pcmcia: id_table for airo_cs
pcmcia-id_table-for-axnet_cs.patch
pcmcia: id_table for axnet_cs
pcmcia-id_table-for-fdomain_stub.patch
pcmcia: id_table for fdomain_stub
pcmcia-id_table-for-fmvj18x_cs.patch
pcmcia: id_table for fmvj18x_cs
pcmcia-id_table-for-ibmtr_cs.patch
pcmcia: id_table for ibmtr_cs
pcmcia-id_table-for-netwave_cs.patch
pcmcia: id_table for netwave_cs
pcmcia-id_table-for-nmclan_cs.patch
pcmcia: id_table for nmclan_cs
pcmcia-id_table-for-teles_cs.patch
pcmcia: id_table for teles_cs
pcmcia-id_table-for-ray_cs.patch
pcmcia: id_table for ray_cs
pcmcia-id_table-for-wavelan_cs.patch
pcmcia: id_table for wavelan_cs
pcmcia-id_table-for-sym53c500_csc.patch
pcmcia: id_table for sym53c500_cs.c
pcmcia-id_table-for-qlogic_stubc.patch
pcmcia: id_table for qlogic_stub.c
pcmcia-id_table-for-smc91c92_csc.patch
pcmcia: id_table for smc91c92_cs.c
pcmcia-id_table-for-orinoco_cs.patch
pcmcia: id_table for orinoco_cs
pcmcia-id_table-for-xirc2ps_csc.patch
pcmcia: id_table for xirc2ps_cs.c
pcmcia-id_table-for-ide_csc.patch
pcmcia: id_table for ide_cs.c
pcmcia-id_table-for-parport_csc.patch
pcmcia: id_table for parport_cs.c
pcmcia-id_table-for-pcnet_csc.patch
pcmcia: id_table for pcnet_cs.c
pcmcia-id_table-for-pcmciamtdc.patch
pcmcia: id_table for pcmciamtd.c
pcmcia-id_table-for-vxpocketc.patch
pcmcia: id_table for vxpocket.c
pcmcia-id_table-for-atmel_csc.patch
pcmcia: id_table for atmel_cs.c
pcmcia-id_table-for-avma1_csc.patch
pcmcia: id_table for avma1_cs.c
pcmcia-id_table-for-avm_csc.patch
pcmcia: id_table for avm_cs.c
pcmcia-id_table-for-bluecard_csc.patch
pcmcia: id_table for bluecard_cs.c
pcmcia-id_table-for-bt3c_csc.patch
pcmcia: id_table for bt3c_cs.c
pcmcia-id_table-for-btuart_csc.patch
pcmcia: id_table for btuart_cs.c
pcmcia-id_table-for-com20020_csc.patch
pcmcia: id_table for com20020_cs.c
pcmcia-id_table-for-dtl1_csc.patch
pcmcia: id_table for dtl1_cs.c
pcmcia-id_table-for-elsa_csc.patch
pcmcia: id_table for elsa_cs.c
pcmcia-id_table-for-ixj_pcmciac.patch
pcmcia: id_table for ixj_pcmcia.c
pcmcia-id_table-for-nsp_csc.patch
pcmcia: id_table for nsp_cs.c
pcmcia-id_table-for-sedlbauer_csc.patch
pcmcia: id_table for sedlbauer_cs.c
pcmcia-id_table-for-wl3501_csc.patch
pcmcia: id_table for wl3501_cs.c
pcmcia-id_table-for-pdaudiocfc.patch
pcmcia: id_table for pdaudiocf.c
pcmcia-id_table-for-synclink_csc.patch
pcmcia: id_table for synclink_cs.c
pcmcia-add-some-documentation.patch
pcmcia: add some Documentation
pcmcia-update-resource-database-adjust-routines-to-use-unsigned-long-values.patch
pcmcia: update resource database adjust routines to use unsigned long values
pcmcia-mark-parent-bridge-windows-as-resources-available-for-pcmcia-devices.patch
pcmcia: mark parent bridge windows as resources available for PCMCIA devices
pcmcia-add-a-config-option-for-the-pcmica-ioctl.patch
pcmcia: add a config option for the PCMICA ioctl
pcmcia-move-pcmcia-ioctl-to-a-separate-file.patch
pcmcia: move PCMCIA ioctl to a separate file
pcmcia-clean-up-cs-ds-callback.patch
pcmcia: clean up cs ds callback
pcmcia-clean-up-cs-ds-callback-fix.patch
pcmcia-clean-up-cs-ds-callback-fix
pcmcia-make-pcmcia-status-a-bitfield.patch
pcmcia: make PCMCIA status a bitfield
pcmcia-merge-struct-pcmcia_bus_socket-into-struct-pcmcia_socket.patch
pcmcia: merge struct pcmcia_bus_socket into struct pcmcia_socket
pcmcia-remove-unneeded-includes-in-dsc.patch
pcmcia: remove unneeded includes in ds.c
pcmcia-rename-some-functions.patch
pcmcia: rename some functions
pcmcia-move-pcmcia-resource-handling-out-of-csc.patch
pcmcia: move pcmcia resource handling out of cs.c
pcmcia-csc-cleanup.patch
pcmcia: cs.c cleanup
pcmcia-dsc-cleanup.patch
pcmcia: ds.c cleanup
pcmcia-release_class.patch
pcmcia: release_class
pcmcia-use-request_region-in-i82365.patch
pcmcia: use request_region in i82365
pcmcia-synclink_cs-irq_info2_info-is-gone.patch
pcmcia: synclink_cs IRQ_INFO2_INFO is gone
pcmcia-mod_devicetableh-fix-for-different-sizes-in-kernel-and-userspace.patch
pcmcia: mod_devicetable.h fix for different sizes in kernel- and userspace
pcmcia-select-crc32-in-kconfig-for-pcmcia.patch
pcmcia: select crc32 in Kconfig for PCMCIA
pcmcia-resource-handling-fixes.patch
pcmcia: resource handling fixes
nfsacl-solaris-nfsacl-workaround.patch
nfsacl: Solaris nfsacl workaround
nfs-client-latencies.patch
NFS client latency fixes
kgdb-ga.patch
kgdb stub for ia32 (George Anzinger's one)
kgdbL warning fix
kgdb buffer overflow fix
kgdbL warning fix
kgdb: CONFIG_DEBUG_INFO fix
x86_64 fixes
correct kgdb.txt Documentation link (against 2.6.1-rc1-mm2)
kgdb: fix for recent gcc
kgdb warning fixes
THREAD_SIZE fixes for kgdb
Fix stack overflow test for non-8k stacks
kgdb-ga.patch fix for i386 single-step into sysenter
fix TRAP_BAD_SYSCALL_EXITS on i386
add TRAP_BAD_SYSCALL_EXITS config for i386
kgdb-is-incompatible-with-kprobes
kgdb-ga-build-fix
kgdb-ga-fixes
kgdb: kill off highmem_start_page
kgdb documentation fix
kgdb-x86-config_debug_info-fix.patch
kgdb CONFIG_DEBUG_INFO fix
kgdboe-netpoll.patch
kgdb-over-ethernet via netpoll
kgdboe: fix configuration of MAC address
kgdb-x86_64-support.patch
kgdb-x86_64-support.patch for 2.6.2-rc1-mm3
kgdb-x86_64-warning-fixes
kgdb-x86_64-fix
kgdb-x86_64-serial-fix
kprobes exception notifier fix
kgdb-x86_64-config_debug_info-fix.patch
kgdb CONFIG_DEBUG_INFO fix
rock-lindent.patch
rock: lindent it
rock-manual-tidies.patch
rock: manual tidies
rock-remove-CHECK_SP.patch
rock: remove CHECK_SP
rock-remove-CONTINUE_DECLS.patch
rock: remove CONTINUE_DECLS
rock-remove-CHECK_CE.patch
rock: remove CHECK_CE
rock-remove-SETUP_ROCK_RIDGE.patch
rock: remove SETUP_ROCK_RIDGE
rock-remove-MAYBE_CONTINUE.patch
rock: remove MAYBE_CONTINUE
rock-comment-tidies.patch
rock: comment tidies
rock-lindent-rock-h.patch
rock: lindent rock.h
isofs-remove-debug-stuff.patch
isofs: remove debug stuff
rock-handle-corrupted-directories.patch
rock.c: handle corrupted directories
rock-rename-union-members.patch
rock: rename union members
rock-handle-directory-overflows.patch
rock: handle directory overflows
rock-handle-directory-overflows-fix.patch
rock-handle-directory-overflows-fix
journal_add_journal_head-debug.patch
journal_add_journal_head-debug
list_del-debug.patch
list_del debug check
page-owner-tracking-leak-detector.patch
Page owner tracking leak detector
make-page_owner-handle-non-contiguous-page-ranges.patch
make page_owner handle non-contiguous page ranges
add-gfp_mask-to-page-owner.patch
add gfp_mask to page owner
unplug-can-sleep.patch
unplug functions can sleep
firestream-warnings.patch
firestream warnings
periodically-scan-redzone-entries-and-slab-control-structures.patch
periodically scan redzone entries and slab control structures
slab-leak-detector.patch
slab leak detector
slab-leak-detector-warning-fixes.patch
slab leak detector warning fixes
irqpoll.patch
irqpoll
releasing-resources-with-children.patch
Releasing resources with children
perfctr-core.patch
perfctr: core
perfctr: remove bogus perfctr_sample_thread() calls
perfctr-i386.patch
perfctr: i386
perfctr-x86-core-updates.patch
perfctr x86 core updates
perfctr-x86-driver-updates.patch
perfctr x86 driver updates
perfctr-x86-driver-cleanup.patch
perfctr: x86 driver cleanup
perfctr-prescott-fix.patch
Prescott fix for perfctr
perfctr-x86-update-2.patch
perfctr x86 update 2
perfctr-x86_64.patch
perfctr: x86_64
perfctr-x86_64-core-updates.patch
perfctr x86_64 core updates
perfctr-ppc.patch
perfctr: PowerPC
perfctr-ppc32-driver-update.patch
perfctr: ppc32 driver update
perfctr-ppc32-mmcr0-handling-fixes.patch
perfctr ppc32 MMCR0 handling fixes
perfctr-ppc32-update.patch
perfctr ppc32 update
perfctr-ppc32-update-2.patch
perfctr ppc32 update
perfctr-virtualised-counters.patch
perfctr: virtualised counters
perfctr-remap_page_range-fix.patch
virtual-perfctr-illegal-sleep.patch
virtual perfctr illegal sleep
make-perfctr_virtual-default-in-kconfig-match-recommendation.patch
Make PERFCTR_VIRTUAL default in Kconfig match recommendation in help text
perfctr-ifdef-cleanup.patch
perfctr ifdef cleanup
perfctr-update-2-6-kconfig-related-updates.patch
perfctr: Kconfig-related updates
perfctr-virtual-updates.patch
perfctr virtual updates
perfctr-virtual-cleanup.patch
perfctr: virtual cleanup
perfctr-ppc32-preliminary-interrupt-support.patch
perfctr ppc32 preliminary interrupt support
perfctr-update-5-6-reduce-stack-usage.patch
perfctr: reduce stack usage
perfctr-interrupt-support-kconfig-fix.patch
perfctr interrupt_support Kconfig fix
perfctr-low-level-documentation.patch
perfctr low-level documentation
perfctr-inheritance-1-3-driver-updates.patch
perfctr inheritance: driver updates
perfctr-inheritance-2-3-kernel-updates.patch
perfctr inheritance: kernel updates
perfctr-inheritance-3-3-documentation-updates.patch
perfctr inheritance: documentation updates
perfctr-inheritance-locking-fix.patch
perfctr inheritance locking fix
perfctr-api-changes-first-step.patch
perfctr API changes: first step
perfctr-virtual-update.patch
perfctr virtual update
perfctr-x86-64-ia32-emulation-fix.patch
perfctr x86-64 ia32 emulation fix
perfctr-sysfs-update-1-4-core.patch
perfctr sysfs update: core
perfctr-sysfs-update.patch
Perfctr sysfs update
perfctr-sysfs-update-2-4-x86.patch
perfctr sysfs update: x86
perfctr-sysfs-update-3-4-x86-64.patch
perfctr sysfs update: x86-64
perfctr: syscall numbers in x86-64 ia32-emulation
perfctr x86_64 native syscall numbers fix
perfctr-sysfs-update-4-4-ppc32.patch
perfctr sysfs update: ppc32
perfctr-2710-api-update-1-4-common.patch
perfctr-2.7.10 API update 1/4: common
perfctr-2710-api-update-2-4-i386.patch
perfctr-2.7.10 API update 2/4: i386
perfctr-2710-api-update-3-4-x86_64.patch
perfctr-2.7.10 API update 3/4: x86_64
perfctr-2710-api-update-4-4-ppc32.patch
perfctr-2.7.10 API update 4/4: ppc32
perfctr-api-update-1-9-physical-indexing-x86.patch
perfctr API update 1/9: physical indexing, x86
perfctr-api-update-2-9-physical-indexing-ppc32.patch
perfctr API update 2/9: physical indexing, ppc32
perfctr-api-update-3-9-cpu_control_header-x86.patch
perfctr API update 3/9: cpu_control_header, x86
perfctr-api-update-4-9-cpu_control_header-ppc32.patch
perfctr API update 4/9: cpu_control_header, ppc32
perfctr-api-update-5-9-cpu_control_header-common.patch
perfctr API update 5/9: cpu_control_header, common
perfctr-api-update-6-9-cpu_control-access-common.patch
perfctr API update 6/9: cpu_control access, common
perfctr-api-update-7-9-cpu_control-access-x86.patch
perfctr API update 7/9: cpu_control access, x86
perfctr-api-update-8-9-cpu_control-access-ppc32.patch
perfctr API update 8/9: cpu_control access, ppc32
perfctr-api-update-9-9-domain-based-read-write-syscalls.patch
perfctr API update 9/9: domain-based read/write syscalls
perfctr-ia32-syscalls-on-x86-64-fix.patch
perfctr ia32 syscalls on x86-64 fix
perfctr-cleanups-1-3-common.patch
perfctr cleanups: common
perfctr-cleanups-2-3-ppc32.patch
perfctr cleanups: ppc32
perfctr-cleanups-3-3-x86.patch
perfctr cleanups: x86
perfctr-x86-fix-and-cleanups.patch
perfctr: x86 fix and cleanups
perfctr-ppc32-fix-and-cleanups.patch
perfctr: ppc32 fix and cleanups
perfctr-64-bit-values-in-register-descriptors.patch
perfctr: 64-bit values in register descriptors
perfctr-64-bit-values-in-register-descriptors-fix.patch
perfctr-64-bit-values-in-register-descriptors fix
perfctr-mapped-state-cleanup-x86.patch
perfctr: mapped state cleanup: x86
perfctr-mapped-state-cleanup-ppc32.patch
perfctr: mapped state cleanup: ppc32
perfctr-mapped-state-cleanup-common.patch
perfctr: mapped state cleanup: common
perfctr-ppc64-arch-hooks.patch
perfctr: ppc64 arch hooks
perfctr-common-updates-for-ppc64.patch
perfctr: common updates for ppc64
perfctr-ppc64-driver-core.patch
perfctr: ppc64 driver core
sched2-cleanup-wake_idle.patch
sched: cleanup wake_idle
sched2-improve-load-balancing-pinned-tasks.patch
sched: improve load balancing pinned tasks
sched2-reduce-active-load-balancing.patch
sched: reduce active load balancing
sched2-fix-smt-scheduling-problems.patch
sched: fix SMT scheduling problems
sched2-add-debugging.patch
sched: add debugging
sched2-less-aggressive-idle-balancing.patch
sched: less aggressive idle balancing
sched2-balance-timers.patch
sched: balance timers
sched2-tweak-affine-wakeups.patch
sched: tweak affine wakeups
sched2-no-aggressive-idle-balancing.patch
sched: no aggressive idle balancing
sched2-balance-on-fork.patch
sched: balance on fork
sched2-schedstats-update-for-balance-on-fork.patch
sched: schedstats update for balance on fork
sched2-sched-tuning.patch
sched: sched tuning
sched2-sched-tuning-fix.patch
sched2-sched-tuning-fix
sched2-sched-domain-sysctl.patch
sched: sched domain sysctl
sched-uninline-task_timeslice.patch
sched: uninline task_timeslice
sched-remove-unnecessary-sched-domains.patch
sched: remove unnecessary sched domains
sched-improve-pinned-task-handling-again.patch
Subject: [patch] sched: improve pinned task handling again!
sched-cleanup-context-switch-locking.patch
sched: cleanup context switch locking
add-do_proc_doulonglongvec_minmax-to-sysctl-functions.patch
Add do_proc_doulonglongvec_minmax to sysctl functions
add-do_proc_doulonglongvec_minmax-to-sysctl-functions-fix
add-do_proc_doulonglongvec_minmax-to-sysctl-functions fix 2
allow-x86_64-to-reenable-interrupts-on-contention.patch
Allow x86_64 to reenable interrupts on contention
i386-cpu-hotplug-updated-for-mm.patch
i386 CPU hotplug
disable-atykb-warning.patch
disable atykb "too many keys pressed" warning
export-file_ra_state_init-again.patch
Export file_ra_state_init() again
cachefs-filesystem.patch
CacheFS filesystem
numa-policies-for-file-mappings-mpol_mf_move-cachefs.patch
numa-policies-for-file-mappings-mpol_mf_move for cachefs
cachefs-release-search-records-lest-they-return-to-haunt-us.patch
CacheFS: release search records lest they return to haunt us
fix-64-bit-problems-in-cachefs.patch
Fix 64-bit problems in cachefs
cachefs-fixed-typos-that-cause-wrong-pointer-to-be-kunmapped.patch
cachefs: fixed typos that cause wrong pointer to be kunmapped
cachefs-return-the-right-error-upon-invalid-mount.patch
CacheFS: return the right error upon invalid mount
fix-cachefs-barrier-handling-and-other-kernel-discrepancies.patch
Fix CacheFS barrier handling and other kernel discrepancies
remove-error-from-linux-cachefsh.patch
Remove #error from linux/cachefs.h
cachefs-warning-fix-2.patch
cachefs warning fix 2
cachefs-linkage-fix-2.patch
cachefs linkage fix
cachefs-build-fix.patch
cachefs build fix
cachefs-documentation.patch
CacheFS documentation
add-page-becoming-writable-notification.patch
Add page becoming writable notification
add-page-becoming-writable-notification-fix.patch
do_wp_page_mk_pte_writable() fix
add-page-becoming-writable-notification-build-fix.patch
add-page-becoming-writable-notification build fix
make-page-becoming-writable-notification-a-vma-op-only.patch
Make page-becoming-writable notification a VMA-op only
provide-a-filesystem-specific-syncable-page-bit.patch
Provide a filesystem-specific sync'able page bit
provide-a-filesystem-specific-syncable-page-bit-fix.patch
provide-a-filesystem-specific-syncable-page-bit-fix
provide-a-filesystem-specific-syncable-page-bit-fix-2.patch
provide-a-filesystem-specific-syncable-page-bit-fix-2
make-afs-use-cachefs.patch
Make AFS use CacheFS
afs-cachefs-dependency-fix.patch
afs-cachefs-dependency-fix
split-general-cache-manager-from-cachefs.patch
Split general cache manager from CacheFS
turn-cachefs-into-a-cache-backend.patch
Turn CacheFS into a cache backend
rework-the-cachefs-documentation-to-reflect-fs-cache-split.patch
Rework the CacheFS documentation to reflect FS-Cache split
update-afs-client-to-reflect-cachefs-split.patch
Update AFS client to reflect CacheFS split
make-page-becoming-writable-notification-a-vma-op-only-kafs-fix.patch
Make page-becoming-writable notification a VMA-op only (kafs fix)
fscache-menuconfig-help-fix-documentation-path.patch
fscache-menuconfig-help-fix-documentation-pathc
x86-rename-apic_mode_exint.patch
kexec: x86: rename APIC_MODE_EXINT
x86-local-apic-fix.patch
kexec: x86: local apic fix
x86_64-e820-64bit.patch
kexec: x86_64: e820 64bit fix
x86-i8259-shutdown.patch
kexec: x86: i8259 shutdown: disable interrupts
x86_64-i8259-shutdown.patch
kexec: x86_64: add i8259 shutdown method
x86-apic-virtwire-on-shutdown.patch
kexec: x86: resture apic virtual wire mode on shutdown
x86_64-apic-virtwire-on-shutdown.patch
kexec: x86_64: restore apic virtual wire mode on shutdown
vmlinux-fix-physical-addrs.patch
kexec: vmlinux: fix physical addresses
x86-vmlinux-fix-physical-addrs.patch
kexec: x86: vmlinux: fix physical addresses
x86_64-vmlinux-fix-physical-addrs.patch
kexec: x86_64: vmlinux: fix physical addresses
x86-config-kernel-start.patch
kexec: x86: add CONFIG_PYSICAL_START
kexec-reserve-bootmem-fix-for-booting-nondefault-location-kernel.patch
kexec: reserve Bootmem fix for booting nondefault location kernel
x86_64-config-kernel-start.patch
kexec: x86_64: add CONFIG_PHYSICAL_START
kexec-kexec-generic.patch
kexec: add kexec syscalls
kexec-kexec-generic-kexec-use-unsigned-bitfield.patch
kexec: use unsigned bitfield
x86-machine_shutdown.patch
kexec: x86: factor out apic shutdown code
x86-kexec.patch
kexec: x86 kexec core
x86-crashkernel.patch
crashdump: x86 crashkernel option
x86-crashkernel-fix.patch
kexec: fix for broken kexec on panic
x86_64-machine_shutdown.patch
kexec: x86_64: factor out apic shutdown code
x86_64-kexec.patch
kexec: x86_64 kexec implementation
x86_64-crashkernel.patch
crashdump: x86_64: crashkernel option
kexec-ppc-support.patch
kexec: kexec ppc support
kexec-ppc-fix-noret_type.patch
kexec: ppc: fix NORET_TYPE
x86-crash_shutdown-nmi-shootdown.patch
crashdump: x86: add NMI handler to capture other CPUs
x86-crash_shutdown-snapshot-registers.patch
kexec: x86: snapshot registers during crash shutdown
x86-crash_shutdown-apic-shutdown.patch
kexec: x86 shutdown APICs during crash_shutdown
kdump-export-crash-notes-section-address-through.patch
Kdump: Export crash notes section address through sysfs
kdump-export-crash-notes-section-address-through-x86_64-fix.patch
kdump-export-crash-notes-section-address-through x86_64 fix
kdump-nmi-handler-segment-selector-stack.patch
kdump: NMI handler segment selector, stack pointer fix
kdump-documentation-for-kdump.patch
kdump: Documentation for Kdump
kdump-retrieve-saved-max-pfn.patch
kdump: Retrieve saved max pfn
kdump-kconfig-for-kdump.patch
kdump: Kconfig
kdump-routines-for-copying-dump-pages.patch
kdump: Routines for copying dump pages
kdump-retrieve-elfcorehdr-address-from-command.patch
Retrieve elfcorehdr address from command line
kdump-access-dump-file-in-elf-format.patch
kdump: Access dump file in elf format (/proc/vmcore)
kdump-parse-elf32-headers-and-export-through.patch
kdump: Parse elf32 headers and export through /proc/vmcore
kdump-accessing-dump-file-in-linear-raw-format.patch
kdump: Accessing dump file in linear raw format (/dev/oldmem)
kdump-cleanups-for-dump-file-access-in-linear.patch
kdump: cleanups for dump file access in linear raw format
kdump-sysrq-trigger-mechanism-for-kexec-based-crashdumps.patch
kdump: sysrq trigger mechanism for kexec based crashdumps
reiser4-sb_sync_inodes.patch
reiser4: vfs: add super_operations.sync_inodes()
reiser4-allow-drop_inode-implementation.patch
reiser4: export vfs inode.c symbols
reiser4-truncate_inode_pages_range.patch
reiser4: vfs: add truncate_inode_pages_range()
reiser4-export-remove_from_page_cache.patch
reiser4: export pagecache add/remove functions to modules
reiser4-export-page_cache_readahead.patch
reiser4: export page_cache_readahead to modules
reiser4-reget-page-mapping.patch
reiser4: vfs: re-check page->mapping after calling try_to_release_page()
reiser4-rcu-barrier.patch
reiser4: add rcu_barrier() synchronization point
reiser4-rcu-barrier-license-fix.patch
reiser4-rcu-barrier-license-fix
reiser4-export-inode_lock.patch
reiser4: export inode_lock to modules
reiser4-export-pagevec-funcs.patch
reiser4: export pagevec functions to modules
reiser4-export-radix_tree_preload.patch
reiser4: export radix_tree_preload() to modules
reiser4-export-find_get_pages.patch
reiser4-radix_tree_lookup_slot.patch
reiser4: add radix_tree_lookup_slot()
reiser4-include-reiser4.patch
reiser4: add to build system
reiser4-doc.patch
reiser4: documentation
reiser4-only.patch
reiser4: main fs
reiser4-kconfig-help-cleanup.patch
reiser4 Kconfig help cleanup
add-acpi-based-floppy-controller-enumeration.patch
Add ACPI-based floppy controller enumeration.
possible-dcache-bug-debugging-patch.patch
Possible dcache BUG: debugging patch
serial-add-support-for-non-standard-xtals-to-16c950-driver.patch
serial: add support for non-standard XTALs to 16c950 driver
add-support-for-possio-gcc-aka-pcmcia-siemens-mc45.patch
Add support for Possio GCC AKA PCMCIA Siemens MC45
remove-lock_section-from-x86_64-spin_lock-asm.patch
remove LOCK_SECTION from x86_64 spin_lock asm
kfree_skb-dump_stack.patch
kfree_skb-dump_stack
minimal-ide-disk-updates.patch
Minimal ide-disk updates
md-merge-md_enter_safemode-into-md_check_recovery.patch
md: merge md_enter_safemode into md_check_recovery
md-improve-locking-on-safemode-and-move-superblock-writes.patch
md: improve locking on 'safemode' and move superblock writes
md-improve-the-interface-to-sync_request.patch
md: improve the interface to sync_request
md-optimised-resync-using-bitmap-based-intent-logging.patch
md: optimised resync using Bitmap based intent logging
md-optimised-resync-using-bitmap-based-intent-logging-mempool-fix.patch
md-optimised-resync-using-bitmap-based-intent-logging-mempool-fix
md-a-couple-of-tidyups-relating-to-the-bitmap-file.patch
md: a couple of tidyups relating to the bitmap file.
md-call-bitmap_daemon_work-regularly.patch
md: call bitmap_daemon_work regularly
md-print-correct-pid-for-newly-created-bitmap-writeback-daemon.patch
md: print correct pid for newly created bitmap-writeback-daemon.
md-minor-code-rearrangement-in-bitmap_init_from_disk.patch
md: minor code rearrangement in bitmap_init_from_disk
md-make-sure-md-bitmap-is-cleared-on-a-clean-start.patch
md: make sure md bitmap is cleared on a clean start.
md-printk-fix.patch
md printk fix
md-improve-debug-printing-of-bitmap-superblock.patch
md: improve debug-printing of bitmap superblock.
md-check-return-value-of-write_page-rather-than-ignore-it.patch
md: check return value of write_page, rather than ignore it
md-enable-the-bitmap-write-back-daemon-and-wait-for-it.patch
md: enable the bitmap write-back daemon and wait for it.
md-dont-skip-bitmap-pages-due-to-lack-of-bit-that-we-just-cleared.patch
md: don't skip bitmap pages due to lack of bit that we just cleared.
md-optimised-resync-using-bitmap-based-intent-logging-fix.patch
md-optimised-resync-using-bitmap-based-intent-logging fix
md-raid1-support-for-bitmap-intent-logging.patch
md: raid1 support for bitmap intent logging
md-fix-bug-when-raid1-attempts-a-partial-reconstruct.patch
md: fix bug when raid1 attempts a partial reconstruct.
md-raid1-support-for-bitmap-intent-logging-fix.patch
md: initialise sync_blocks in raid1 resync
md-optimise-reconstruction-when-re-adding-a-recently-failed-drive.patch
md: optimise reconstruction when re-adding a recently failed drive.
md-fix-deadlock-due-to-md-thread-processing-delayed-requests.patch
md: fix deadlock due to md thread processing delayed requests.
md-allow-md-intent-bitmap-to-be-stored-near-the-superblock.patch
md: allow md intent bitmap to be stored near the superblock.
md-allow-md-to-update-multiple-superblocks-in-parallel.patch
md: allow md to update multiple superblocks in parallel.
detect-atomic-counter-underflows.patch
detect atomic counter underflows
post-halloween-doc.patch
post halloween doc
fuse-maintainers-kconfig-and-makefile-changes.patch
FUSE - MAINTAINERS, Kconfig and Makefile changes
fuse-core.patch
FUSE - core
fuse-device-functions.patch
FUSE - device functions
fuse-device-functions-abi-version-change.patch
FUSE: ABI version change
fuse-device-functions-comments-and-documentation.patch
FUSE: comments and documentation
fuse-device-functions-cleanup.patch
FUSE: trivial cleanups
fuse-read-only-operations.patch
FUSE - read-only operations
fuse-read-only-operations-add-offset-to-fuse_dirent.patch
FUSE: add offset to fuse_dirent
fuse-read-only-operations-readdir-fixes.patch
FUSE: readdir fixes
fuse-read-write-operations.patch
FUSE - read-write operations
fuse-file-operations.patch
FUSE - file operations
fuse-mount-options.patch
FUSE - mount options
fuse-mount-options-fix.patch
fuse: fix busy inodes after unmount
fuse-mount-options-comments-and-documentation.patch
FUSE: comments and documentation
fuse-mount-options-fix-cleanup.patch
FUSE: trivial cleanups
fuse-mount-options-fix-fix.patch
FUSE: fix locking for background list
fuse-extended-attribute-operations.patch
FUSE - extended attribute operations
fuse-add-padding.patch
FUSE: add padding
fuse-readpages-operation.patch
FUSE - readpages operation
fuse-nfs-export.patch
FUSE - NFS export
fuse-direct-i-o.patch
FUSE - direct I/O
fuse-direct-i-o-fix-warning-on-x86_64.patch
FUSE: fix warning on x86_64
fuse-transfer-readdir-data-through-device.patch
fuse: transfer readdir data through device
fuse-add-fsync-operation-for-directories.patch
FUSE: add fsync operation for directories
drivers-isdn-divert-isdn_divertc-make-5-functions-static.patch
drivers/isdn/divert/isdn_divert.c: make 5 functions static
drivers-isdn-capi-make-some-code-static.patch
drivers/isdn/capi/: make some code static
drivers-scsi-pas16c-make-code-static.patch
drivers/scsi/pas16.c: make code static
i386-x86_64-early_printkc-make-early_serial_base-static.patch
i386/x86_64 early_printk.c: make early_serial_base static
kernel-exitc-make-exit_mm-static.patch
kernel/exit.c: make exit_mm static
cyrix-eliminate-bad-section-references.patch
cyrix: eliminate bad section references
drivers-media-video-tvaudioc-make-some-variables-static.patch
drivers/media/video/tvaudio.c: make some variables static
drivers-isdn-sc-possible-cleanups.patch
drivers/isdn/sc/: possible cleanups
drivers-isdn-pcbit-possible-cleanups.patch
drivers/isdn/pcbit/: possible cleanups
drivers-isdn-i4l-possible-cleanups.patch
drivers/isdn/i4l/: possible cleanups
unexport-mca_find_device_by_slot.patch
unexport mca_find_device_by_slot
drivers-isdn-hardware-avm-misc-cleanups.patch
drivers/isdn/hardware/avm/: misc cleanups
drivers-isdn-act2000-capic-if-0-an-unused-function.patch
drivers/isdn/act2000/capi.c: #if 0 an unused function
tpm-fix-gcc-printk-warnings.patch
tpm: fix gcc printk warnings
x86-64-add-memcpy-memset-prototypes.patch
x86-64: add memcpy/memset prototypes
au1100fb-convert-to-c99-inits.patch
au1100fb: convert to C99 inits.
reiserfs-use-null-instead-of-0.patch
reiserfs: use NULL instead of 0
comments-on-locking-of-task-comm.patch
comments on locking of task->comm
riottyc-cleanups-and-warning-fix.patch
riotty.c cleanups and warning fix
fixup-a-comment-still-refering-to-verify_area.patch
fix up a comment still refering to verify_area
char-ds1620-use-msleep-instead-of-schedule_timeout.patch
char/ds1620: use msleep() instead of schedule_timeout()
char-tty_io-replace-schedule_timeout-with-msleep_interruptible.patch
char/tty_io: replace schedule_timeout() with msleep_interruptible()
kernel-timer-fix-msleep_interruptible-comment.patch
kernel/timer: fix msleep_interruptible() comment
ixj-compile-warning-cleanup.patch
ixj* - compile warning cleanup
spelling-cleanups-in-shrinker-code.patch
Spelling cleanups in shrinker code
init-do_mounts_initrdc-fix-sparse-warning.patch
init/do_mounts_initrd.c: fix sparse warning
arch-i386-kernel-trapsc-fix-sparse-warnings.patch
arch/i386/kernel/traps.c: fix sparse warnings
arch-i386-kernel-apmc-fix-sparse-warnings.patch
arch/i386/kernel/apm.c: fix sparse warnings
arch-i386-mm-faultc-fix-sparse-warnings.patch
arch/i386/mm/fault.c: fix sparse warnings
arch-i386-crypto-aesc-fix-sparse-warnings.patch
arch/i386/crypto/aes.c: fix sparse warnings
codingstyle-trivial-whitespace-fixups.patch
CodingStyle: trivial whitespace fixups
small-partitions-msdos-cleanups.patch
small partitions/msdos cleanups
remove-redundant-null-check-before-before-kfree-in.patch
remove redundant NULL check before before kfree() in kernel/sysctl.c
update-ross-biro-bouncing-email-address.patch
update Ross Biro bouncing email address
get-rid-of-redundant-null-checks-before-kfree-in-arch-i386.patch
get rid of redundant NULL checks before kfree() in arch/i386/
remove-redundant-null-checks-before-kfree-in-sound-and.patch
remove redundant NULL checks before kfree() in sound/ and avoid casting pointers about to be kfree()'ed
x86-geode-support-fixes.patch
x86: geode support fixes
drivers-scsi-initioc-cleanups.patch
drivers/scsi/initio.c: cleanups
dont-do-pointless-null-checks-and-casts-before-kfree.patch
selinux: kfree cleanup
drivers-char-isicomc-section-fixes.patch
drivers/char/isicom.c: section fixes
sound-oss-cleanups.patch
sound/oss/: cleanups
sound-oss-rme96xxc-remove-kernel-22-ifs.patch
sound/oss/rme96xx.c: remove kernel 2.2 #if's
drivers-char-mwave-tp3780ic-remove-kernel-22-ifs.patch
drivers/char/mwave/tp3780i.c: remove kernel 2.2 #if's
drivers-net-skfp-cleanups.patch
drivers/net/skfp/: cleanups
net-atm-resourcesc-remove-__free_atm_dev.patch
Subject: [2.6 patch] net/atm/resources.c: remove __free_atm_dev
fix-ncr53c9xc-compile-warning.patch
fix NCR53C9x.c compile warning
mm-mmapnommuc-several-unexports.patch
mm/{mmap,nommu}.c: several unexports
unexport-hugetlb_total_pages.patch
unexport hugetlb_total_pages
unexport-clear_page_dirty_for_io.patch
unexport clear_page_dirty_for_io
mm-filemapc-make-sync_page_range_nolock-static.patch
mm/filemap.c: make sync_page_range_nolock static
mm-filemapc-make-generic_file_direct_io-static.patch
mm/filemap.c: make generic_file_direct_IO static
remove-exports-for-oem-modules.patch
remove exports for oem modules
mm-page_allocc-unexport-nr_swap_pages.patch
unexport nr_swap_pages
unexport-console_unblank.patch
unexport console_unblank
mm-swapc-unexport-vm_acct_memory.patch
mm/swap.c: unexport vm_acct_memory
mm-swapfilec-unexport-total_swap_pages.patch
mm/swapfile.c: unexport total_swap_pages
mm-swap_statec-unexport-swapper_space.patch
mm/swap_state.c: unexport swapper_space
unexport-slab_reclaim_pages.patch
unexport slab_reclaim_pages
unexport-idle_cpu.patch
unexport idle_cpu
>
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
Well the DRI is, both reports of bugs have been fixed :-), the bug
should be closed on bugs.kernel.org I think, and it looks rock solid
on my box both FC3 and Debian sarge..
Dave.
Andrew Morton wrote:
> +sched-remove-unnecessary-sched-domains.patch
> +sched-improve-pinned-task-handling-again.patch
[snip]
>
> CPU scheduler updates
>
It is no problem that you picked these up for testing. But
don't merge them yet, please.
Suresh's underlying problem with the unnecessary sched domains
is a failing of sched-balance-exec and sched-balance-fork, which
I am working on now.
Removing unnecessary domains is a nice optimisation, but just
needs to account for a few more flags before declaring that a
domain is unnecessary (not to mention this probably breaks if
isolcpus= is used). I have made some modifications to the patch
to fix these problems.
Lastly, I'd like to be a bit less intrusive with pinned task
handling improvements. I think we can do this while still being
effective in preventing livelocks.
I will keep you posted with regards to the various scheduler
patches.
--
SUSE Labs, Novell Inc.
>[ 0.000000] PCI: Using ACPI for IRQ routing
[ 0.000000] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
[ 0.000000] pnp: 00:0b: ioport range 0x140-0x14f has been reserved
[ 0.000000] pnp: 00:0c: ioport range 0x4d0-0x4d1 has been reserved
[ 0.000000] pnp: 00:0c: ioport range 0x1000-0x1087 could not be reserved
[ 0.000000] pnp: 00:0c: ioport range 0x1100-0x113f has been reserved
[ 0.000000] pnp: 00:0c: ioport range 0x1200-0x121f has been reserved
[ 0.000000] Machine check exception polling timer started.
[ 0.000000] apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
[ 0.000000] apm: overridden by ACPI.
[ 0.000000] inotify device minor=63
[ 0.000000] devfs: 2004-01-31 Richard Gooch ([email protected])
[ 0.000000] devfs: boot_options: 0x0
[ 0.000000] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.000000] fakephp: Fake PCI Hot Plug Controller Driver
[ 0.000000] cpqphp: Compaq Hot Plug PCI Controller Driver version: 0.9.8
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt Link [C0BB] enabled at IRQ 11
[ 0.000000] PCI: setting IRQ 11 as level-triggered
[ 0.000000] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [C0BB] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] radeonfb: Retreived PLL infos from BIOS
[ 0.000000] radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=166.00 Mhz, System=166.00 MHz
[ 0.000000] radeonfb: PLL min 12000 max 35000
[ 0.000000] Non-DDC laptop panel detected
[ 0.000000] radeonfb: Monitor 1 type LCD found
[ 0.000000] radeonfb: Monitor 2 type no found
[ 0.000000] radeonfb: panel ID string: 1024x768
[ 0.000000] radeonfb: detected LVDS panel size from BIOS: 1024x768
[ 0.000000] radeondb: BIOS provided dividers will be used
[ 0.000000] radeonfb: Dynamic Clock Power Management enabled
[ 0.000000] Console: switching to colour frame buffer device 128x48
[ 0.000000] radeonfb (0000:01:00.0): ATI Radeon LY
[ 0.000000] ACPI: AC Adapter [C1A2] (off-line)
[ 0.000000] ACPI: Battery Slot [C19F] (battery present)
[ 0.000000] ACPI: Battery Slot [C1A0] (battery absent)
[ 0.000000] ACPI: Power Button (FF) [PWRF]
[ 0.000000] ACPI: Sleep Button (CM) [C1A3]
[ 0.000000] ACPI: Lid Switch [C1A4]
[ 0.000000] ACPI: Fan [C1F6] (off)
[ 0.000000] ACPI: Fan [C1F7] (off)
[ 0.000000] ACPI: Fan [C1F8] (off)
[ 0.000000] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
[ 0.000000] ACPI: Thermal Zone [TZ1] (57 C)
[ 0.000000] Linux agpgart interface v0.101 (c) Dave Jones
[ 0.000000] agpgart: Detected an Intel 830M Chipset.
[ 0.000000] agpgart: AGP aperture is 256M @ 0x60000000
[ 0.000000] [drm] Initialized drm 1.0.0 20040925
[ 0.000000] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [C0BB] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] [drm] Initialized radeon 1.16.0 20050311 on minor 0: ATI Technologies Inc Radeon Mobility M6 LY
[ 0.000000] PNP: PS/2 Controller [PNP0303:C171,PNP0f0e:C172] at 0x60,0x64 irq 1,12
[ 0.000000] i8042: probe of i8042 failed with error 0
[ 0.000000] ACPI: No ACPI bus support for i8042
[ 0.000000] i8042.c: Detected active multiplexing controller, rev 1.1.
[ 0.000000] serio: i8042 AUX0 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 AUX1 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 AUX2 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 AUX3 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.000000] Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
[ 0.000000] i8042: probe of serial8250 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for serial8250
[ 0.000000] ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.000000] ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
[ 0.000000] ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.000000] io scheduler noop registered
[ 0.000000] io scheduler anticipatory registered
[ 0.000000] io scheduler deadline registered
[ 0.000000] io scheduler cfq registered
[ 0.000000] e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
[ 0.000000] e100: Copyright(c) 1999-2004 Intel Corporation
[ 0.000000] ACPI: PCI Interrupt Link [C0BE] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [C0BE] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] e100: eth0: e100_probe: addr 0x40100000, irq 11, MAC addr 00:02:A5:B5:03:7C
[ 0.000000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[ 0.000000] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[ 0.000000] ICH3M: IDE controller at PCI slot 0000:00:1f.1
[ 0.000000] PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
[ 0.000000] ACPI: PCI Interrupt Link [C0BC] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [C0BC] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] ICH3M: chipset revision 1
[ 0.000000] ICH3M: not 100% native mode: will probe irqs later
[ 0.000000] ide0: BM-DMA at 0x4060-0x4067, BIOS settings: hda:DMA, hdb:pio
[ 0.000000] ide1: BM-DMA at 0x4068-0x406f, BIOS settings: hdc:DMA, hdd:pio
[ 0.000000] Probing IDE interface ide0...
[ 0.000000] ACPI: No ACPI bus support for serio0
[ 0.000000] ACPI: No ACPI bus support for serio1
[ 0.000000] ACPI: No ACPI bus support for serio2
[ 0.000000] ACPI: No ACPI bus support for serio3
[ 0.000000] ACPI: No ACPI bus support for serio4
[ 0.000000] hda: IC25N020ATDA04-0, ATA DISK drive
[ 0.000000] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[ 0.000000] ACPI: No ACPI bus support for 0.0
[ 0.000000] Probing IDE interface ide1...
[ 0.000000] hdc: Compaq DVD-ROM SD-C2402, ATAPI CD/DVD-ROM drive
[ 0.000000] ide1 at 0x170-0x177,0x376 on irq 15
[ 0.000000] ACPI: No ACPI bus support for 1.0
[ 0.000000] ide2: I/O resource 0x3EE-0x3EE not free.
[ 0.000000] ide2: ports already in use, skipping probe
[ 0.000000] Probing IDE interface ide3...
[ 0.000000] Probing IDE interface ide4...
[ 0.000000] Probing IDE interface ide5...
[ 0.000000] hda: max request size: 128KiB
[ 0.000000] hda: 39070080 sectors (20003 MB) w/1806KiB Cache, CHS=38760/16/63, UDMA(100)
[ 0.000000] hda: cache flushes not supported
[ 0.000000] /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4
[ 0.000000] hdc: ATAPI 24X DVD-ROM drive, 128kB Cache, DMA
[ 0.000000] Uniform CD-ROM driver Revision: 3.20
[ 0.000000] mice: PS/2 mouse device common for all mice
[ 0.000000] NET: Registered protocol family 2
[ 0.000000] IP: routing cache hash table of 8192 buckets, 64Kbytes
[ 0.000000] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.000000] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.000000] NET: Registered protocol family 1
[ 0.000000] NET: Registered protocol family 17
[ 0.000000] PM: Checking swsusp image.
[ 0.000000] swsusp: Resume From Partition /dev/hda4
[ 0.000000] swsusp: Suspend partition has wrong signature?
[ 0.000000] swsusp: Error -22 check for resume file
[ 0.000000] PM: Resume from disk failed.
[ 0.000000] ACPI wakeup devices:
[ 0.000000] C052 C17E C185 C0A4 C0AA C19F C1A0 C1A3 C1A4
[ 0.000000] ACPI: (supports S0 S1 S3 S4 S4bios S5)
[ 0.000000] input: AT Translated Set 2 keyboard on isa0060/serio0
[ 0.000000] kjournald starting. Commit interval 5 seconds
[ 0.000000] EXT3-fs: hda2: orphan cleanup on readonly fs
[ 0.000000] ext3_orphan_cleanup: deleting unreferenced inode 531194
[ 0.000000] ext3_orphan_cleanup: deleting unreferenced inode 531191
[ 0.000000] EXT3-fs: hda2: 2 orphan inodes deleted
[ 0.000000] EXT3-fs: recovery complete.
[ 0.000000] EXT3-fs: mounted filesystem with ordered data mode.
[ 0.000000] VFS: Mounted root (ext3 filesystem) readonly.
[ 0.000000] Freeing unused kernel memory: 176k freed
[ 0.000000] Synaptics Touchpad, model: 1
[ 0.000000] Firmware: 5.8
[ 0.000000] 180 degree mounted touchpad
[ 0.000000] Sensor: 27
[ 0.000000] new absolute packet format
[ 0.000000] Touchpad has extended capability bits
[ 0.000000] -> multifinger detection
[ 0.000000] -> palm detection
[ 0.000000] -> pass-through port
[ 0.000000] serio: Synaptics pass-through port at isa0060/serio4/input0
[ 0.000000] input: SynPS/2 Synaptics TouchPad on isa0060/serio4
[ 0.000000] atkbd: probe of serio5 failed with error -19
[ 0.000000] Adding 665272k swap on /dev/hda4. Priority:-1 extents:1
[ 0.000000] EXT3 FS on hda2, internal journal
[ 0.000000] device-mapper: 4.4.0-ioctl (2005-01-12) initialised: [email protected]
[ 0.000000] input: PS/2 Generic Mouse on synaptics-pt/serio0
[ 0.000000] psmouse: probe of serio5 failed with error 0
[ 0.000000] ACPI: No ACPI bus support for serio5
[ 0.000000] kjournald starting. Commit interval 5 seconds
[ 0.000000] EXT3 FS on hda3, internal journal
[ 0.000000] EXT3-fs: mounted filesystem with ordered data mode.
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt Link [C0C0] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:02:03.0[A] -> Link [C0C0] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] Yenta: CardBus bridge found at 0000:02:03.0 [0e11:004e]
[ 0.000000] Yenta: Enabling burst memory read transactions
[ 0.000000] Yenta: Using CSCINT to route CSC interrupts to PCI
[ 0.000000] Yenta: Routing CardBus interrupts to PCI
[ 0.000000] Yenta TI: socket 0000:02:03.0, mfunc 0x01001002, devctl 0x64
[ 0.000000] Yenta: ISA IRQ mask 0x04f8, PCI irq 11
[ 0.000000] Socket status: 30000006
[ 0.000000] pcmcia: I/O behind socket: 0x2000 - 0x2fff
[ 0.000000] cs: IO port probe 0x2000-0x2fff: clean.
[ 0.000000] pcmcia: Memory behind socket: 0x40000000 - 0x401fffff
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt 0000:02:03.1[A] -> Link [C0C0] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] Yenta: CardBus bridge found at 0000:02:03.1 [0e11:004e]
[ 0.000000] Yenta: Using CSCINT to route CSC interrupts to PCI
[ 0.000000] Yenta: Routing CardBus interrupts to PCI
[ 0.000000] Yenta TI: socket 0000:02:03.1, mfunc 0x01001002, devctl 0x64
[ 0.000000] Yenta: ISA IRQ mask 0x04f8, PCI irq 11
[ 0.000000] Socket status: 30000010
[ 0.000000] pcmcia: I/O behind socket: 0x2000 - 0x2fff
[ 0.000000] cs: IO port probe 0x2000-0x2fff: clean.
[ 0.000000] pcmcia: Memory behind socket: 0x40000000 - 0x401fffff
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt Link [C0BA] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [C0BA] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] usbcore: registered new driver usbfs
[ 0.000000] usbcore: registered new driver hub
[ 0.000000] USB Universal Host Controller Interface driver v2.2
[ 0.000000] ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [C0BA] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[ 0.000000] uhci_hcd 0000:00:1d.0: Intel Corporation 82801CA/CAM USB (Hub #1)
[ 0.000000] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
[ 0.000000] uhci_hcd 0000:00:1d.0: irq 11, io base 0x00004000
[ 0.000000] ACPI: No ACPI bus support for usb1
[ 0.000000] usbfs: probe of 1-0:1.0 failed with error -19
[ 0.000000] hub 1-0:1.0: USB hub found
[ 0.000000] hub 1-0:1.0: 2 ports detected
[ 0.000000] hub: probe of 1-0:1.0 failed with error 0
[ 0.000000] usb: probe of 1-0:1.0 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for 1-0:1.0
[ 0.000000] ACPI: PCI Interrupt Link [C0BD] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [C0BD] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[ 0.000000] uhci_hcd 0000:00:1d.1: Intel Corporation 82801CA/CAM USB (Hub #2)
[ 0.000000] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
[ 0.000000] uhci_hcd 0000:00:1d.1: irq 11, io base 0x00004020
[ 0.000000] ACPI: No ACPI bus support for usb2
[ 0.000000] usbfs: probe of 2-0:1.0 failed with error -19
[ 0.000000] hub 2-0:1.0: USB hub found
[ 0.000000] hub 2-0:1.0: 2 ports detected
[ 0.000000] hub: probe of 2-0:1.0 failed with error 0
[ 0.000000] usb: probe of 2-0:1.0 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for 2-0:1.0
[ 0.000000] ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [C0BC] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[ 0.000000] uhci_hcd 0000:00:1d.2: Intel Corporation 82801CA/CAM USB (Hub #3)
[ 0.000000] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
[ 0.000000] uhci_hcd 0000:00:1d.2: irq 11, io base 0x00004040
[ 0.000000] ACPI: No ACPI bus support for usb3
[ 0.000000] usbfs: probe of 3-0:1.0 failed with error -19
[ 0.000000] hub 3-0:1.0: USB hub found
[ 0.000000] hub 3-0:1.0: 2 ports detected
[ 0.000000] hub: probe of 3-0:1.0 failed with error 0
[ 0.000000] usb: probe of 3-0:1.0 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for 3-0:1.0
[ 0.000000] hw_random hardware driver 1.0.0 loaded
[ 0.000000] irda_init()
[ 0.000000] NET: Registered protocol family 23
[ 0.000000] parport: PnPBIOS parport detected.
[ 0.000000] parport0: PC-style at 0x378, irq 7 [PCSPP(,...)]
[ 0.000000] input: PC Speaker
[ 0.000000] Real Time Clock Driver v1.12
[ 0.000000] cs: memory probe 0x40000000-0x401fffff: excluding 0x40000000-0x4001ffff 0x40040000-0x4009ffff 0x400c0000-0x4011ffff 0x40140000-0x4019ffff 0x401c0000-0x401fffff
[ 0.000000] ACPI: No ACPI bus support for 1.0
[ 0.000000] cs: IO port probe 0x100-0x4ff: excluding 0x100-0x107 0x200-0x207
[ 0.000000] cs: IO port probe 0x100-0x4ff: excluding 0x100-0x107 0x200-0x207
[ 0.000000] cs: IO port probe 0x800-0x8ff: clean.
[ 0.000000] cs: IO port probe 0x800-0x8ff: clean.
[ 0.000000] cs: IO port probe 0xc00-0xcff: clean.
[ 0.000000] cs: IO port probe 0xc00-0xcff: clean.
[ 0.000000] cs: IO port probe 0xa00-0xaff: clean.
[ 0.000000] cs: IO port probe 0xa00-0xaff: clean.
[ 0.000000] orinoco 0.14alpha2 (David Gibson <[email protected]>, Pavel Roskin <[email protected]>, et al)
[ 0.000000] orinoco_cs 0.14alpha2 (David Gibson <[email protected]>, Pavel Roskin <[email protected]>, et al)
[ 0.000000] eth1: Hardware identity 0001:0004:0005:0000
[ 0.000000] eth1: Station identity 001f:0001:0008:002a
[ 0.000000] eth1: Firmware determined as Lucent/Agere 8.42
[ 0.000000] eth1: Ad-hoc demo mode supported
[ 0.000000] eth1: IEEE standard IBSS ad-hoc mode supported
[ 0.000000] eth1: WEP supported, 104-bit key
[ 0.000000] eth1: MAC address 00:02:A5:6F:9E:14
[ 0.000000] eth1: Station name "HERMES I"
[ 0.000000] eth1: ready
[ 0.000000] eth1: index 0x01: Vcc 5.0, irq 3, io 0x2100-0x213f
[ 0.000000] eth1: New link status: Connected (0001)
[ 0.000000] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
[ 0.000000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
[ 0.000000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
On Tue, Apr 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
> +officially-deprecate-register_ioctl32_conversion.patch
>
> deprecate a compat function (mainly affects DRI)
Those DRI callers aren't in mainline but introduced in bk-drm.patch,
looks like the DRI folks need beating with a big stick..
* Nick Piggin <[email protected]> wrote:
> Andrew Morton wrote:
>
> >+sched-remove-unnecessary-sched-domains.patch
> >+sched-improve-pinned-task-handling-again.patch
> [snip]
> >
> > CPU scheduler updates
> >
>
> It is no problem that you picked these up for testing. But
> don't merge them yet, please.
almost all current scheduler patches in -mm are post-2.6.12 items and
are conditional on testing feedback from the big boxes, but otherwise
have my conceptual ack. The only trivial one that would be fine for
2.6.12 is sched-uninline-task_timeslice.patch.
Ingo
Andrew Morton a ?crit :
> Brice Goglin <[email protected]> wrote:
>
>>Andrew Morton a ?crit :
>> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>>
>> Hi Andrew,
>>
>> printk timing seems broken.
>> It always shows [ 0.000000] on my Compaq Evo N600c.
>
>
> What sort of CPU does that thing have? Please share the /proc/cpuinfo
> output.
It's a Mobile Pentium 3:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 11
model name : Intel(R) Pentium(R) III Mobile CPU 1000MHz
stepping : 1
cpu MHz : 996.763
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca
cmov pat pse36 mmx fxsr sse
bogomips : 1977.25
> Does reverting
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/broken-out/sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
> fix it?
Yes!
Brice
Brice Goglin <[email protected]> wrote:
>
> Andrew Morton a ?crit :
> > Brice Goglin <[email protected]> wrote:
> >
> >>Andrew Morton a ?crit :
> >> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
> >>
> >> Hi Andrew,
> >>
> >> printk timing seems broken.
> >> It always shows [ 0.000000] on my Compaq Evo N600c.
> >
> >
> > What sort of CPU does that thing have? Please share the /proc/cpuinfo
> > output.
>
> It's a Mobile Pentium 3:
>
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 11
> model name : Intel(R) Pentium(R) III Mobile CPU 1000MHz
> stepping : 1
> cpu MHz : 996.763
> cache size : 512 KB
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 2
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca
> cmov pat pse36 mmx fxsr sse
> bogomips : 1977.25
Mobile p3 has a TSC, doesn't it? Confused.
Anyway,
> > Does reverting
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/broken-out/sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
> > fix it?
>
> Yes!
>
Ingo broke my kernel!
Christoph Hellwig <[email protected]> wrote:
>
> (btw, could you please add to all patches who's responsible for them,
> bk-audit.patch doesn't tell)
It's supposed to, but if I have to fix rejects and refresh the patch, I
lose that info. Right now, bk-audit stomps on bk-ia64, so we lost the info.
I'll finally get around to fixing that up right now.
Anyway. dwmw2.
Andrew Morton a ?crit :
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
I'm sorry, I did not follow this "PM resume broken" thread.
But, suspend to disk does not work here, at least since 2.6.12-rc1-mm4
(I can't be sure about other releases, I don't use suspend-to-disk
intensively).
Basically, "Freeing memory" looks much slower than before but suspend
finally looks ok.
When resuming, it says it's restarting tasks. But actually it does not
resume anyone of my real applications.
Here's a part of what I see with rc2-mm1:
input: AT Translated Set 2 keyboard on isa0060/serio0
Stopping tasks: =<6>Synaptics Touchpad, model: 1
Firmware: 5.8
180 degree mounted touchpad
[...]
-> pass-through port
serio: Synaptics pass-through port at isa0060/serio4/input0
input: SynPS/2 Synaptics TouchPad on isa0060/serio4
atkbd: probe of serio5 failed with error -19
input: PS/2 Generic Mouse on synaptics-pt/serio0
Restarting tasks...<6> Strange, kseriod not stopped
done
Actually, most of these lines appear when booting a fresh kernel.
The resume-specific ones are "Stopping tasks", "Restarting tasks"
and "Strange, kseriod not stopped".
Brice
> bk-audit.patch
This introduces various AUDIT_ARCH numerical constants, which is a blatantly
stupid idea. We already have a way to uniquely identify architectures, and
that's the ELF headers, no need for another parallel namespace.
(btw, could you please add to all patches who's responsible for them,
bk-audit.patch doesn't tell)
Brice Goglin <[email protected]> wrote:
>
> Andrew Morton a ?crit :
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>
> Hi Andrew,
>
> printk timing seems broken.
> It always shows [ 0.000000] on my Compaq Evo N600c.
What sort of CPU does that thing have? Please share the /proc/cpuinfo
output.
Does reverting
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/broken-out/sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
fix it?
Thanks.
* Brice Goglin <[email protected]> wrote:
> Andrew Morton a ?crit :
> >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>
> Hi Andrew,
>
> printk timing seems broken.
> It always shows [ 0.000000] on my Compaq Evo N600c.
could you send the full bootlog (starting at the 'gcc...' line)? I'm not
sure whether TSC calibration was done on your CPU. If cyc2ns_scale is
not set up then sched_clock() will return 0, and this could result in
that printk symptom.
Ingo
Hi,
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>
> - x86 NMI handling seems to be bust in 2.6.12-rc2. Try using
> `nmi_watchdog=0' if you experience weird crashes.
>
> - The possible kernel-timer related hangs might possibly be fixed. We
> haven't heard yet.
>
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
>
> - Various fixes and updates. Nothing earth-shattering.
>
>
>
> Changes since 2.6.12-rc1-mm4:
>
>
> bk-acpi.patch
> bk-agpgart.patch
> bk-cifs.patch
> bk-cpufreq.patch
> bk-cryptodev.patch
> bk-driver-core.patch
> bk-drm.patch
> bk-drm-via.patch
> bk-ia64.patch
> bk-audit.patch
> bk-input.patch
> bk-jfs.patch
> bk-kbuild.patch
> bk-mtd.patch
> bk-netdev.patch
> bk-nfs.patch
> bk-ntfs.patch
> bk-scsi.patch
> bk-watchdog.patch
>
> Latest versions of subsystem trees
Hrm. Something changed between the last -mm release which compiled
through, and this one..
CHK include/linux/compile.h
CHK usr/initramfs_list
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
arch/i386/kernel/built-in.o(.init.text+0x1823): In function `setup_arch':
: undefined reference to `acpi_boot_table_init'
arch/i386/kernel/built-in.o(.init.text+0x1828): In function `setup_arch':
: undefined reference to `acpi_boot_init'
make: *** [.tmp_vmlinux1] Error 1
[root@tornado linux-2.6]#
Backing out bk-acpi.patch works around it..
reuben
1.4.1#16: restart.
klogd 1.4.1#16, log source = /proc/kmsg started.
Cannot find map file.
No module symbols loaded - kernel modules not enabled.
[4294667.296000] Linux version 2.6.12-rc2-mm1=LoulousMobile (bgoglin@puligny) (version gcc 3.3.5 (Debian 1:3.3.5-8)) #9 PREEMPT Tue Apr 5 09:28:57 CEST 2005
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 0000000027fd0000 (usable)
[ 0.000000] BIOS-e820: 0000000027fd0000 - 0000000027ff0c00 (reserved)
[ 0.000000] BIOS-e820: 0000000027ff0c00 - 0000000027ffc000 (ACPI NVS)
[ 0.000000] BIOS-e820: 0000000027ffc000 - 0000000028000000 (reserved)
[ 0.000000] 639MB LOWMEM available.
[ 0.000000] DMI 2.3 present.
[ 0.000000] ACPI: PM-Timer IO Port: 0x1008
[ 0.000000] Allocating PCI resources starting at 28000000 (gap: 28000000:d8000000)
[ 0.000000] Built 1 zonelists
[ 0.000000] Local APIC disabled by BIOS -- you can enable it with "lapic"
[ 0.000000] Initializing CPU#0
[ 0.000000] Kernel command line: root=/dev/hda2 ro
[ 0.000000] CPU 0 irqstacks, hard=c04a0000 soft=c049f000
[ 0.000000] PID hash table entries: 4096 (order: 12, 65536 bytes)
[ 0.000000] Detected 730.935 MHz processor.
[ 0.000000] Using pmtmr for high-res timesource
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 644672k/655168k available (2314k kernel code, 9976k reserved, 1191k data, 176k init, 0k highmem)
[ 0.000000] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[ 0.000000] Mount-cache hash table entries: 512
[ 0.000000] CPU: L1 I cache: 16K, L1 D cache: 16K
[ 0.000000] CPU: L2 cache: 512K
[ 0.000000] Intel machine check architecture supported.
[ 0.000000] Intel machine check reporting enabled on CPU#0.
[ 0.000000] CPU: Intel(R) Pentium(R) III Mobile CPU 1000MHz stepping 01
[ 0.000000] Enabling fast FPU save and restore... done.
[ 0.000000] Enabling unmasked SIMD FPU exception support... done.
[ 0.000000] Checking 'hlt' instruction... OK.
[ 0.000000] tbxface-0118 [02] acpi_load_tables : ACPI Tables successfully acquired
[ 0.000000] Parsing all Control Methods:..........................................................................................................................................................................................................................................................................
[ 0.000000] Table [DSDT](id F006) - 833 Objects with 89 Devices 266 Methods 26 Regions
[ 0.000000] Parsing all Control Methods:.
[ 0.000000] Table [SSDT](id F003) - 3 Objects with 0 Devices 1 Methods 0 Regions
[ 0.000000] Parsing all Control Methods:..
[ 0.000000] Table [SSDT](id F004) - 4 Objects with 0 Devices 2 Methods 0 Regions
[ 0.000000] ACPI Namespace successfully loaded at root c04d56c0
[ 0.000000] ACPI: setting ELCR to 0200 (from 0800)
[ 0.000000] evxfevnt-0094 [03] acpi_enable : Transition to ACPI mode successful
[ 0.000000] softlockup thread 0 started up.
[ 0.000000] NET: Registered protocol family 16
[ 0.000000] PCI: PCI BIOS revision 2.10 entry at 0xf04dd, last bus=4
[ 0.000000] PCI: Using configuration type 1
[ 0.000000] mtrr: v2.0 (20020519)
[ 0.000000] ACPI: Subsystem revision 20050309
[ 0.000000] evgpeblk-0275 [08] ev_save_method_info : Unknown GPE method type: C13E (name not of form _Lxx or _Exx)
[ 0.000000] evgpeblk-0275 [08] ev_save_method_info : Unknown GPE method type: C18F (name not of form _Lxx or _Exx)
[ 0.000000] evgpeblk-0275 [08] ev_save_method_info : Unknown GPE method type: C1DC (name not of form _Lxx or _Exx)
[ 0.000000] evgpeblk-0979 [06] ev_create_gpe_block : GPE 00 to 0F [_GPE] 2 regs on int 0x9
[ 0.000000] evgpeblk-0987 [06] ev_create_gpe_block : Found 3 Wake, Enabled 1 Runtime GPEs in this block
[ 0.000000] evgpeblk-0275 [08] ev_save_method_info : Unknown GPE method type: C13E (name not of form _Lxx or _Exx)
[ 0.000000] evgpeblk-0275 [08] ev_save_method_info : Unknown GPE method type: C18F (name not of form _Lxx or _Exx)
[ 0.000000] evgpeblk-0275 [08] ev_save_method_info : Unknown GPE method type: C1DC (name not of form _Lxx or _Exx)
[ 0.000000] evgpeblk-0979 [06] ev_create_gpe_block : GPE 10 to 1F [_GPE] 2 regs on int 0x9
[ 0.000000] evgpeblk-0987 [06] ev_create_gpe_block : Found 2 Wake, Enabled 5 Runtime GPEs in this block
[ 0.000000] Completing Region/Field/Buffer/Package initialization:..................................................................................................
[ 0.000000] Initialized 25/26 Regions 0/0 Fields 26/26 Buffers 47/56 Packages (849 nodes)
[ 0.000000] Executing all Device _STA and_INI methods:...........................................................................................
[ 0.000000] 91 Devices found containing: 91 _STA, 8 _INI methods
[ 0.000000] ACPI: Interpreter enabled
[ 0.000000] ACPI: Using PIC for interrupt routing
[ 0.000000] ACPI: PCI Root Bridge [C03E] (0000:00)
[ 0.000000] PCI: Probing PCI hardware (bus 00)
[ 0.000000] ACPI: Assume root bridge [\_SB_.C03E] segment is 0
[ 0.000000] ACPI: Assume root bridge [\_SB_.C03E] bus is 0
[ 0.000000] PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
[ 0.000000] ACPI: Can't get handler for 0000:02:08.0
[ 0.000000] ACPI: Power Resource [C14E] (on)
[ 0.000000] ACPI: Power Resource [C167] (on)
[ 0.000000] ACPI: Power Resource [C16B] (on)
[ 0.000000] ACPI: Power Resource [C174] (on)
[ 0.000000] ACPI: PCI Interrupt Link [C0BA] (IRQs 5 10 *11)
[ 0.000000] ACPI: PCI Interrupt Link [C0BB] (IRQs 5 10 *11)
[ 0.000000] ACPI: PCI Interrupt Link [C0BC] (IRQs 5 10 *11)
[ 0.000000] ACPI: PCI Interrupt Link [C0BD] (IRQs 5 10 *11)
[ 0.000000] ACPI: PCI Interrupt Link [C0BE] (IRQs 5 10 *11)
[ 0.000000] ACPI: PCI Interrupt Link [C0BF] (IRQs 5 10 *11)
[ 0.000000] ACPI: PCI Interrupt Link [C0C0] (IRQs 5 10 *11)
[ 0.000000] ACPI: PCI Interrupt Link [C0C1] (IRQs 5 10 11) *0, disabled.
[ 0.000000] ACPI: Power Resource [C1F3] (off)
[ 0.000000] ACPI: Power Resource [C1F4] (off)
[ 0.000000] ACPI: Power Resource [C1F5] (off)
[ 0.000000] Linux Plug and Play Support v0.97 (c) Adam Belay
[ 0.000000] pnp: PnP ACPI init
[ 0.000000] ACPI: No ACPI bus support for 00:00
[ 0.000000] ACPI: No ACPI bus support for 00:01
[ 0.000000] ACPI: No ACPI bus support for 00:02
[ 0.000000] ACPI: No ACPI bus support for 00:03
[ 0.000000] ACPI: No ACPI bus support for 00:04
[ 0.000000] ACPI: No ACPI bus support for 00:05
[ 0.000000] ACPI: No ACPI bus support for 00:06
[ 0.000000] ACPI: No ACPI bus support for 00:07
[ 0.000000] ACPI: No ACPI bus support for 00:08
[ 0.000000] ACPI: No ACPI bus support for 00:09
[ 0.000000] ACPI: No ACPI bus support for 00:0a
[ 0.000000] ACPI: No ACPI bus support for 00:0b
[ 0.000000] ACPI: No ACPI bus support for 00:0c
[ 0.000000] ACPI: No ACPI bus support for 00:0d
[ 0.000000] pnp: PnP ACPI: found 14 devices
[ 0.000000] PnPBIOS: Disabled by ACPI PNP
[ 0.000000] SCSI subsystem initialized
[ 0.000000] PCI: Using ACPI for IRQ routing
[ 0.000000] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
[ 0.000000] pnp: 00:0b: ioport range 0x140-0x14f has been reserved
[ 0.000000] pnp: 00:0c: ioport range 0x4d0-0x4d1 has been reserved
[ 0.000000] pnp: 00:0c: ioport range 0x1000-0x1087 could not be reserved
[ 0.000000] pnp: 00:0c: ioport range 0x1100-0x113f has been reserved
[ 0.000000] pnp: 00:0c: ioport range 0x1200-0x121f has been reserved
[ 0.000000] Machine check exception polling timer started.
[ 0.000000] apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
[ 0.000000] apm: overridden by ACPI.
[ 0.000000] inotify device minor=63
[ 0.000000] devfs: 2004-01-31 Richard Gooch ([email protected])
[ 0.000000] devfs: boot_options: 0x0
[ 0.000000] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.000000] fakephp: Fake PCI Hot Plug Controller Driver
[ 0.000000] cpqphp: Compaq Hot Plug PCI Controller Driver version: 0.9.8
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt Link [C0BB] enabled at IRQ 11
[ 0.000000] PCI: setting IRQ 11 as level-triggered
[ 0.000000] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [C0BB] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] radeonfb: Retreived PLL infos from BIOS
[ 0.000000] radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=166.00 Mhz, System=166.00 MHz
[ 0.000000] radeonfb: PLL min 12000 max 35000
[ 0.000000] Non-DDC laptop panel detected
[ 0.000000] radeonfb: Monitor 1 type LCD found
[ 0.000000] radeonfb: Monitor 2 type no found
[ 0.000000] radeonfb: panel ID string: 1024x768
[ 0.000000] radeonfb: detected LVDS panel size from BIOS: 1024x768
[ 0.000000] radeondb: BIOS provided dividers will be used
[ 0.000000] radeonfb: Dynamic Clock Power Management enabled
[ 0.000000] Console: switching to colour frame buffer device 128x48
[ 0.000000] radeonfb (0000:01:00.0): ATI Radeon LY
[ 0.000000] ACPI: AC Adapter [C1A2] (off-line)
[ 0.000000] ACPI: Battery Slot [C19F] (battery present)
[ 0.000000] ACPI: Battery Slot [C1A0] (battery absent)
[ 0.000000] ACPI: Power Button (FF) [PWRF]
[ 0.000000] ACPI: Sleep Button (CM) [C1A3]
[ 0.000000] ACPI: Lid Switch [C1A4]
[ 0.000000] ACPI: Fan [C1F6] (off)
[ 0.000000] ACPI: Fan [C1F7] (off)
[ 0.000000] ACPI: Fan [C1F8] (off)
[ 0.000000] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
[ 0.000000] ACPI: Thermal Zone [TZ1] (57 C)
[ 0.000000] Linux agpgart interface v0.101 (c) Dave Jones
[ 0.000000] agpgart: Detected an Intel 830M Chipset.
[ 0.000000] agpgart: AGP aperture is 256M @ 0x60000000
[ 0.000000] [drm] Initialized drm 1.0.0 20040925
[ 0.000000] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [C0BB] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] [drm] Initialized radeon 1.16.0 20050311 on minor 0: ATI Technologies Inc Radeon Mobility M6 LY
[ 0.000000] PNP: PS/2 Controller [PNP0303:C171,PNP0f0e:C172] at 0x60,0x64 irq 1,12
[ 0.000000] i8042: probe of i8042 failed with error 0
[ 0.000000] ACPI: No ACPI bus support for i8042
[ 0.000000] i8042.c: Detected active multiplexing controller, rev 1.1.
[ 0.000000] serio: i8042 AUX0 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 AUX1 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 AUX2 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 AUX3 port at 0x60,0x64 irq 12
[ 0.000000] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.000000] Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
[ 0.000000] i8042: probe of serial8250 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for serial8250
[ 0.000000] ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.000000] ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
[ 0.000000] ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.000000] io scheduler noop registered
[ 0.000000] io scheduler anticipatory registered
[ 0.000000] io scheduler deadline registered
[ 0.000000] io scheduler cfq registered
[ 0.000000] e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
[ 0.000000] e100: Copyright(c) 1999-2004 Intel Corporation
[ 0.000000] ACPI: PCI Interrupt Link [C0BE] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [C0BE] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] e100: eth0: e100_probe: addr 0x40100000, irq 11, MAC addr 00:02:A5:B5:03:7C
[ 0.000000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[ 0.000000] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[ 0.000000] ICH3M: IDE controller at PCI slot 0000:00:1f.1
[ 0.000000] PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
[ 0.000000] ACPI: PCI Interrupt Link [C0BC] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [C0BC] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] ICH3M: chipset revision 1
[ 0.000000] ICH3M: not 100%% native mode: will probe irqs later
[ 0.000000] ide0: BM-DMA at 0x4060-0x4067, BIOS settings: hda:DMA, hdb:pio
[ 0.000000] ide1: BM-DMA at 0x4068-0x406f, BIOS settings: hdc:DMA, hdd:pio
[ 0.000000] ACPI: No ACPI bus support for serio0
[ 0.000000] ACPI: No ACPI bus support for serio1
[ 0.000000] ACPI: No ACPI bus support for serio2
[ 0.000000] ACPI: No ACPI bus support for serio3
[ 0.000000] ACPI: No ACPI bus support for serio4
[ 0.000000] hda: IC25N020ATDA04-0, ATA DISK drive
[ 0.000000] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[ 0.000000] ACPI: No ACPI bus support for 0.0
[ 0.000000] hdc: Compaq DVD-ROM SD-C2402, ATAPI CD/DVD-ROM drive
[ 0.000000] ide1 at 0x170-0x177,0x376 on irq 15
[ 0.000000] ACPI: No ACPI bus support for 1.0
[ 0.000000] hda: max request size: 128KiB
[ 0.000000] hda: 39070080 sectors (20003 MB) w/1806KiB Cache, CHS=38760/16/63, UDMA(100)
[ 0.000000] hda: cache flushes not supported
[ 0.000000] /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4
[ 0.000000] hdc: ATAPI 24X DVD-ROM drive, 128kB Cache, DMA
[ 0.000000] Uniform CD-ROM driver Revision: 3.20
[ 0.000000] mice: PS/2 mouse device common for all mice
[ 0.000000] NET: Registered protocol family 2
[ 0.000000] IP: routing cache hash table of 8192 buckets, 64Kbytes
[ 0.000000] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.000000] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.000000] NET: Registered protocol family 1
[ 0.000000] NET: Registered protocol family 17
[ 0.000000] ACPI wakeup devices:
[ 0.000000] C052 C17E C185 C0A4 C0AA C19F C1A0 C1A3 C1A4
[ 0.000000] ACPI: (supports S0 S1 S3 S4 S4bios S5)
[ 0.000000] input: AT Translated Set 2 keyboard on isa0060/serio0
[ 0.000000] kjournald starting. Commit interval 5 seconds
[ 0.000000] EXT3-fs: hda2: orphan cleanup on readonly fs
[ 0.000000] EXT3-fs: hda2: 2 orphan inodes deleted
[ 0.000000] EXT3-fs: recovery complete.
[ 0.000000] EXT3-fs: mounted filesystem with ordered data mode.
[ 0.000000] VFS: Mounted root (ext3 filesystem) readonly.
[ 0.000000] Freeing unused kernel memory: 176k freed
[ 0.000000] Synaptics Touchpad, model: 1
[ 0.000000] Firmware: 5.8
[ 0.000000] 180 degree mounted touchpad
[ 0.000000] Sensor: 27
[ 0.000000] new absolute packet format
[ 0.000000] Touchpad has extended capability bits
[ 0.000000] -> multifinger detection
[ 0.000000] -> palm detection
[ 0.000000] -> pass-through port
[ 0.000000] serio: Synaptics pass-through port at isa0060/serio4/input0
[ 0.000000] input: SynPS/2 Synaptics TouchPad on isa0060/serio4
[ 0.000000] atkbd: probe of serio5 failed with error -19
[ 0.000000] Adding 665272k swap on /dev/hda4. Priority:-1 extents:1
[ 0.000000] EXT3 FS on hda2, internal journal
[ 0.000000] device-mapper: 4.4.0-ioctl (2005-01-12) initialised: [email protected]
[ 0.000000] input: PS/2 Generic Mouse on synaptics-pt/serio0
[ 0.000000] psmouse: probe of serio5 failed with error 0
[ 0.000000] ACPI: No ACPI bus support for serio5
[ 0.000000] kjournald starting. Commit interval 5 seconds
[ 0.000000] EXT3 FS on hda3, internal journal
[ 0.000000] EXT3-fs: mounted filesystem with ordered data mode.
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt Link [C0C0] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:02:03.0[A] -> Link [C0C0] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] Yenta: CardBus bridge found at 0000:02:03.0 [0e11:004e]
[ 0.000000] Yenta: Enabling burst memory read transactions
[ 0.000000] Yenta: Using CSCINT to route CSC interrupts to PCI
[ 0.000000] Yenta: Routing CardBus interrupts to PCI
[ 0.000000] Yenta TI: socket 0000:02:03.0, mfunc 0x01001002, devctl 0x64
[ 0.000000] Yenta: ISA IRQ mask 0x04f8, PCI irq 11
[ 0.000000] Socket status: 30000006
[ 0.000000] pcmcia: I/O behind socket: 0x2000 - 0x2fff
[ 0.000000] cs: IO port probe 0x2000-0x2fff: clean.
[ 0.000000] pcmcia: Memory behind socket: 0x40000000 - 0x401fffff
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt 0000:02:03.1[A] -> Link [C0C0] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] Yenta: CardBus bridge found at 0000:02:03.1 [0e11:004e]
[ 0.000000] Yenta: Using CSCINT to route CSC interrupts to PCI
[ 0.000000] Yenta: Routing CardBus interrupts to PCI
[ 0.000000] Yenta TI: socket 0000:02:03.1, mfunc 0x01001002, devctl 0x64
[ 0.000000] Yenta: ISA IRQ mask 0x04f8, PCI irq 11
[ 0.000000] Socket status: 30000010
[ 0.000000] pcmcia: I/O behind socket: 0x2000 - 0x2fff
[ 0.000000] cs: IO port probe 0x2000-0x2fff: clean.
[ 0.000000] pcmcia: Memory behind socket: 0x40000000 - 0x401fffff
[ 0.000000] acpi_bus-0212 [01] acpi_bus_set_power : Device is not power manageable
[ 0.000000] ACPI: PCI Interrupt Link [C0BA] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [C0BA] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] usbcore: registered new driver usbfs
[ 0.000000] usbcore: registered new driver hub
[ 0.000000] USB Universal Host Controller Interface driver v2.2
[ 0.000000] ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [C0BA] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] uhci_hcd 0000:00:1d.0: Intel Corporation 82801CA/CAM USB (Hub #1)
[ 0.000000] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
[ 0.000000] uhci_hcd 0000:00:1d.0: irq 11, io base 0x00004000
[ 0.000000] ACPI: No ACPI bus support for usb1
[ 0.000000] usbfs: probe of 1-0:1.0 failed with error -19
[ 0.000000] hub 1-0:1.0: USB hub found
[ 0.000000] hub 1-0:1.0: 2 ports detected
[ 0.000000] hub: probe of 1-0:1.0 failed with error 0
[ 0.000000] usb: probe of 1-0:1.0 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for 1-0:1.0
[ 0.000000] ACPI: PCI Interrupt Link [C0BD] enabled at IRQ 11
[ 0.000000] ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [C0BD] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] uhci_hcd 0000:00:1d.1: Intel Corporation 82801CA/CAM USB (Hub #2)
[ 0.000000] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
[ 0.000000] uhci_hcd 0000:00:1d.1: irq 11, io base 0x00004020
[ 0.000000] ACPI: No ACPI bus support for usb2
[ 0.000000] usbfs: probe of 2-0:1.0 failed with error -19
[ 0.000000] hub 2-0:1.0: USB hub found
[ 0.000000] hub 2-0:1.0: 2 ports detected
[ 0.000000] hub: probe of 2-0:1.0 failed with error 0
[ 0.000000] usb: probe of 2-0:1.0 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for 2-0:1.0
[ 0.000000] ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [C0BC] -> GSI 11 (level, low) -> IRQ 11
[ 0.000000] uhci_hcd 0000:00:1d.2: Intel Corporation 82801CA/CAM USB (Hub #3)
[ 0.000000] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
[ 0.000000] uhci_hcd 0000:00:1d.2: irq 11, io base 0x00004040
[ 0.000000] ACPI: No ACPI bus support for usb3
[ 0.000000] usbfs: probe of 3-0:1.0 failed with error -19
[ 0.000000] hub 3-0:1.0: USB hub found
[ 0.000000] hub 3-0:1.0: 2 ports detected
[ 0.000000] hub: probe of 3-0:1.0 failed with error 0
[ 0.000000] usb: probe of 3-0:1.0 failed with error -19
[ 0.000000] ACPI: No ACPI bus support for 3-0:1.0
[ 0.000000] hw_random hardware driver 1.0.0 loaded
[ 0.000000] NET: Registered protocol family 23
[ 0.000000] parport: PnPBIOS parport detected.
[ 0.000000] parport0: PC-style at 0x378, irq 7 [PCSPP(,...)]
[ 0.000000] input: PC Speaker
[ 0.000000] Real Time Clock Driver v1.12
[ 0.000000] cs: memory probe 0x40000000-0x401fffff: excluding 0x40000000-0x4001ffff 0x40040000-0x4009ffff 0x400c0000-0x4011ffff 0x40140000-0x4019ffff 0x401c0000-0x401fffff
[ 0.000000] ACPI: No ACPI bus support for 1.0
[ 0.000000] cs: IO port probe 0x100-0x4ff: excluding 0x100-0x107 0x200-0x207
[ 0.000000] cs: IO port probe 0x100-0x4ff: excluding 0x100-0x107 0x200-0x207
[ 0.000000] cs: IO port probe 0x800-0x8ff: clean.
[ 0.000000] cs: IO port probe 0x800-0x8ff: clean.
[ 0.000000] cs: IO port probe 0xc00-0xcff: clean.
[ 0.000000] cs: IO port probe 0xc00-0xcff: clean.
[ 0.000000] cs: IO port probe 0xa00-0xaff: clean.
[ 0.000000] cs: IO port probe 0xa00-0xaff: clean.
[ 0.000000] eth1: New link status: Connected (0001)
[ 0.000000] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
[ 0.000000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
[ 0.000000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
Hi,
On Tuesday, 5 of April 2005 09:05, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>
> - x86 NMI handling seems to be bust in 2.6.12-rc2. Try using
> `nmi_watchdog=0' if you experience weird crashes.
>
> - The possible kernel-timer related hangs might possibly be fixed. We
> haven't heard yet.
>
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
Well, "my" problem with the PM suspend has turned out to be at least partially
hardware/BIOS-related, so it is not easily reproducible. It is being worked on,
however, AFAICS, so I didn't reported it all over again.
There also is a problem with the ACPI battery driver, which is known to the
right people, too.
Anyway, the patches that cause these issues to appear have been identified
(they both come from the ACPI -bk tree).
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
On Apr 5, 2005 5:44 PM, Christoph Hellwig <[email protected]> wrote:
> On Tue, Apr 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
> > +officially-deprecate-register_ioctl32_conversion.patch
> >
> > deprecate a compat function (mainly affects DRI)
>
> Those DRI callers aren't in mainline but introduced in bk-drm.patch,
> looks like the DRI folks need beating with a big stick..
Paulus these look like your patches care to update them with the "new"
method of doing stuff..
Deprecating would be no fun if the DRI didn't produce a bucket of
warnings every time..
Dave.
Christoph Hellwig writes:
> Those DRI callers aren't in mainline but introduced in bk-drm.patch,
> looks like the DRI folks need beating with a big stick..
Settle down Christoph, the compat_ioctl method is less than 3 months
old, has only been in one official 2.6.x release, and isn't documented
at all in the Documentation directory AFAICS. Don't be so impatient.
Anyway, I did the 32-bit ioctl conversion stuff for the DRM. I'll
look at changing it to use compat_ioctl. The big question of course
is whether the DRM code will work correctly without the BKL held.
Paul.
On Tue, Apr 05, 2005 at 07:11:26PM +1000, Paul Mackerras wrote:
> Christoph Hellwig writes:
>
> > Those DRI callers aren't in mainline but introduced in bk-drm.patch,
> > looks like the DRI folks need beating with a big stick..
>
> Settle down Christoph, the compat_ioctl method is less than 3 months
> old, has only been in one official 2.6.x release, and isn't documented
> at all in the Documentation directory AFAICS. Don't be so impatient.
It's documented where the other filesystem entry points are documented.
This is not about beeing impatient but about adding APIs that at the same
time are actively removed all over the tree.
> Anyway, I did the 32-bit ioctl conversion stuff for the DRM. I'll
> look at changing it to use compat_ioctl. The big question of course
> is whether the DRM code will work correctly without the BKL held.
You can of course take the BKL inside your ->compat_ioctl method.
Dave Airlie writes:
> Paulus these look like your patches care to update them with the "new"
> method of doing stuff..
What are we going to do about the DRM CVS? Change it to the new way
and break everyone running 2.6.10 or earlier, or leave it at the old
way that will work for people with distro kernels, and have a
divergence between it and what's in the kernel?
Also, the compat_ioctl method is called without the BKL held, unlike
the ioctl method. What impact will that have? Do we need to take the
BKL in the compat_ioctl method?
Paul.
>
> > Paulus these look like your patches care to update them with the "new"
> > method of doing stuff..
>
> What are we going to do about the DRM CVS? Change it to the new way
> and break everyone running 2.6.10 or earlier, or leave it at the old
> way that will work for people with distro kernels, and have a
> divergence between it and what's in the kernel?
Yet more backwards compatibility is more than likely going to be
needed, but if it is a biggie I'd be happy to drop the older 32/64-bit
stuff from CVS and make it contingent on having 2.6.11 or greater as
it is a new feature anyways and hasn't seen a release yet...
>
> Also, the compat_ioctl method is called without the BKL held, unlike
> the ioctl method. What impact will that have? Do we need to take the
> BKL in the compat_ioctl method?
I don't think so as the DRM has its own locking that handles most of
the issues at a higher level... I've been thinking of switching DRM to
ioctl_unlocked but I'd really want someone with an SMP system to beat
on it .. (not that the DRI has a great record on SMP anyways..)
Dave.
Dave.
Btw, some more comments on the 32bit compat code in drm:
- instead of set_fs & co and passing kernel addresses to drm_ioctl
please use compat_alloc_user_space()
- this:
+ifeq ($(CONFIG_COMPAT),y)
+drm-objs += drm_ioc32.o
+radeon-objs += radeon_ioc32.o
+endif
should be written as
drm-$(CONFIG_COMPAT) += drm_ioc32.o
radeon-$(CONFIG_COMPAT) += radeon_ioc32.o
and everything else should use foo-y instead of foo-objs
- the magic CONFIG_COMPAT changes for SHM handles should only be done when
a module is set. CONFIG_COMPAT is set for mostly 64bit systems that can
run 32bit code and drm shouldn't behave differently just because we can
run 32bit code.
On Tue, 2005-04-05 at 19:20 +1000, Paul Mackerras wrote:
> Dave Airlie writes:
>
> > Paulus these look like your patches care to update them with the "new"
> > method of doing stuff..
>
> What are we going to do about the DRM CVS? Change it to the new way
> and break everyone running 2.6.10 or earlier, or leave it at the old
> way that will work for people with distro kernels, and have a
> divergence between it and what's in the kernel?
(some distros like Fedora Core have modern kernels even for older
releases)
> Also, the compat_ioctl method is called without the BKL held, unlike
> the ioctl method. What impact will that have? Do we need to take the
> BKL in the compat_ioctl method?
How much does DRM actually depend on the BKL? I would hope not too
much...
On Tue, Apr 05, 2005 at 07:44:38PM +1000, Paul Mackerras wrote:
> Christoph Hellwig writes:
>
> > - the magic CONFIG_COMPAT changes for SHM handles should only be done when
> > a module is set. CONFIG_COMPAT is set for mostly 64bit systems that can
> > run 32bit code and drm shouldn't behave differently just because we can
> > run 32bit code.
>
> Yes it should - we can have a 64-bit X server and a 32-bit DRI
> client. In this case the server will allocate a _DRM_SHM area and
> pass the handle to the client, which will then try to mmap the area.
> If we give a 64-bit handle to the server the client won't be able to
> access the area.
Please make it a module option so it doesn't regress everyone for your
specific needs.
Christoph Hellwig writes:
> Please make it a module option so it doesn't regress everyone for your
> specific needs.
Sorry, I don't follow you.
Christoph Hellwig writes:
> It's documented where the other filesystem entry points are documented.
Which is?
$ grep -r compat_ioctl Documentation
Documentation/filesystems/Locking: long (*compat_ioctl) (struct file *, unsigned int, unsigned long);
Documentation/filesystems/Locking:compat_ioctl: no
Marvellous documentation, that. :)
> This is not about beeing impatient but about adding APIs that at the same
> time are actively removed all over the tree.
Sure, just don't be so impatient... :)
> You can of course take the BKL inside your ->compat_ioctl method.
Yes, the question is whether we need to or not.
Paul.
Christoph Hellwig writes:
> E.g. on my ia64 box CONFIG_COMPAT is set because I have support compiled
> in for running i386 apps. But I don't want dri to hand out 32bit handles
> everywhere just because of that, because I most certainly won't be running
> i386 OpenGL apps.
The handle for a _DRM_SHM area is almost completely arbitrary, why do
you care whether it fits in 32 bits or not? All that matters is that
you can take the handle you get and use it as the offset in an mmap
call. The CONFIG_COMPAT changes don't break 64-bit clients.
Paul.
>
> E.g. on my ia64 box CONFIG_COMPAT is set because I have support compiled
> in for running i386 apps. But I don't want dri to hand out 32bit handles
> everywhere just because of that, because I most certainly won't be running
> i386 OpenGL apps.
>
It doesn't actually matter what size the handles are from what I
understand of this... as long as they are hashed properly.. I've been
thinking of changing the handle from something with meaning to a hash
just to find out some more bugs.. even on plain 32-bit systems..
Dave.
Andrew Morton wrote:
[...]
Does not compile on AthlonXP. For mmx_clear_page, only the prototype was
changed, but the implementation is still the same. I guess that part of
the patch slipped out somehow.
-extern void mmx_clear_page(void *page);
+extern void mmx_clear_page(void *page, int order);
--
Jindrich Makovicka
On Tue, Apr 05, 2005 at 07:58:19PM +1000, Dave Airlie wrote:
> >
> > E.g. on my ia64 box CONFIG_COMPAT is set because I have support compiled
> > in for running i386 apps. But I don't want dri to hand out 32bit handles
> > everywhere just because of that, because I most certainly won't be running
> > i386 OpenGL apps.
> >
>
> It doesn't actually matter what size the handles are from what I
> understand of this... as long as they are hashed properly.. I've been
> thinking of changing the handle from something with meaning to a hash
> just to find out some more bugs.. even on plain 32-bit systems..
Or, I though the handle was related to the dma_mask somewhat. I'll take
all flames on this subject back and apologize for not researching the subject
better, although I still think it's not a good idea to have a different
handle format depending on whether CONFIG_COMPAT is set or not.
Christoph Hellwig writes:
> - the magic CONFIG_COMPAT changes for SHM handles should only be done when
> a module is set. CONFIG_COMPAT is set for mostly 64bit systems that can
> run 32bit code and drm shouldn't behave differently just because we can
> run 32bit code.
Yes it should - we can have a 64-bit X server and a 32-bit DRI
client. In this case the server will allocate a _DRM_SHM area and
pass the handle to the client, which will then try to mmap the area.
If we give a 64-bit handle to the server the client won't be able to
access the area.
Paul.
On 095, 04 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
what useful this part of the patch is supposed to do ?
Looks like the result of whitespace damage.
--- linux-2.6.12-rc2/drivers/acpi/sleep/main.c 2005-03-02 01:09:19.000000000 -0800
+++ 25/drivers/acpi/sleep/main.c 2005-04-04 22:33:10.000000000 -0700
<snip>
@@ -190,16 +180,16 @@ static int __init init_ints_after_s1(str
static struct dmi_system_id __initdata acpisleep_dmi_table[] = {
{
- .callback = init_ints_after_s1,
- .ident = "Toshiba Satellite 4030cdt",
- .matches = { DMI_MATCH(DMI_PRODUCT_NAME, "S4030CDT/4.3"), },
- },
- { },
+ .callback = init_ints_after_s1,
+ .ident = "Toshiba Satellite 4030cdt",
+ .matches = {DMI_MATCH(DMI_PRODUCT_NAME, "S4030CDT/4.3"),},
+ },
+ {},
};
On Tue, Apr 05, 2005 at 07:51:57PM +1000, Paul Mackerras wrote:
> Christoph Hellwig writes:
>
> > Please make it a module option so it doesn't regress everyone for your
> > specific needs.
>
> Sorry, I don't follow you.
E.g. on my ia64 box CONFIG_COMPAT is set because I have support compiled
in for running i386 apps. But I don't want dri to hand out 32bit handles
everywhere just because of that, because I most certainly won't be running
i386 OpenGL apps.
On Tue, Apr 05, 2005 at 07:35:46PM +1000, Paul Mackerras wrote:
> Christoph Hellwig writes:
>
> > It's documented where the other filesystem entry points are documented.
>
> Which is?
>
> $ grep -r compat_ioctl Documentation
> Documentation/filesystems/Locking: long (*compat_ioctl) (struct file *, unsigned int, unsigned long);
> Documentation/filesystems/Locking:compat_ioctl: no
>
> Marvellous documentation, that. :)
The other methods don't have much more documentation either ;-)
On Tue, Apr 05, 2005 at 08:34:11PM +1200, Reuben Farrelly wrote:
> Hi,
Hi Reuben,
>...
> Hrm. Something changed between the last -mm release which compiled
> through, and this one..
>...
> LD .tmp_vmlinux1
> arch/i386/kernel/built-in.o(.init.text+0x1823): In function `setup_arch':
> : undefined reference to `acpi_boot_table_init'
> arch/i386/kernel/built-in.o(.init.text+0x1828): In function `setup_arch':
> : undefined reference to `acpi_boot_init'
> make: *** [.tmp_vmlinux1] Error 1
> [root@tornado linux-2.6]#
>
> Backing out bk-acpi.patch works around it..
Please send your .config .
> reuben
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
On Tue, Apr 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.12-rc1-mm4:
>...
> bk-kbuild.patch
>...
GNU Emacs correctly complains because of spaces instead of a tab.
Signed-off-by: Adrian Bunk <[email protected]>
--- linux-2.6.12-rc2-mm1-full/Makefile.old 2005-04-05 14:00:06.000000000 +0200
+++ linux-2.6.12-rc2-mm1-full/Makefile 2005-04-05 14:00:16.000000000 +0200
@@ -577,7 +577,7 @@
ifdef CONFIG_LOCALVERSION_AUTO
localversion-auto := \
- $(shell $(PERL) $(srctree)/scripts/setlocalversion $(srctree))
+ $(shell $(PERL) $(srctree)/scripts/setlocalversion $(srctree))
LOCALVERSION := $(LOCALVERSION)$(localversion-auto)
endif
Hi again
At 12:14 a.m. 6/04/2005, Adrian Bunk wrote:
>On Tue, Apr 05, 2005 at 08:34:11PM +1200, Reuben Farrelly wrote:
>
> > Hi,
>
>Hi Reuben,
>
> >...
> > Hrm. Something changed between the last -mm release which compiled
> > through, and this one..
> >...
> > LD .tmp_vmlinux1
> > arch/i386/kernel/built-in.o(.init.text+0x1823): In function `setup_arch':
> > : undefined reference to `acpi_boot_table_init'
> > arch/i386/kernel/built-in.o(.init.text+0x1828): In function `setup_arch':
> > : undefined reference to `acpi_boot_init'
> > make: *** [.tmp_vmlinux1] Error 1
> > [root@tornado linux-2.6]#
> >
> > Backing out bk-acpi.patch works around it..
>
>Please send your .config .
Have just figured out that it seems to be caused by having ACPI
disabled in .config, once I re-enabled ACPI the build problem went away.
Config attached anyway, I imagine the problem is quite reproduceable..
Reuben
<snip>
a missing include:
...
drivers/usb/storage/debug.c: In function `usb_stor_show_sense':
drivers/usb/storage/debug.c:166: warning: implicit declaration of function `scsi_sense_key_string'
drivers/usb/storage/debug.c:167: warning: implicit declaration of function `scsi_extd_sense_format'
...
--- drivers/usb/storage/debug.c.orig 2005-04-05 14:24:21.000000000 +0200
+++ drivers/usb/storage/debug.c 2005-04-05 14:24:35.000000000 +0200
@@ -47,7 +47,7 @@
#include <linux/cdrom.h>
#include <scsi/scsi.h>
#include <scsi/scsi_cmnd.h>
-
+#include <scsi/scsi_dbg.h>
#include "debug.h"
#include "scsi.h"
Regards,
Boris.
On Tue, Apr 05, 2005 at 02:21:57PM +0200, Adrian Bunk wrote:
> GNU Emacs correctly complains because of spaces instead of a tab.
>
> Signed-off-by: Adrian Bunk <[email protected]>
>
> --- linux-2.6.12-rc2-mm1-full/Makefile.old 2005-04-05 14:00:06.000000000 +0200
> +++ linux-2.6.12-rc2-mm1-full/Makefile 2005-04-05 14:00:16.000000000 +0200
> @@ -577,7 +577,7 @@
>
> ifdef CONFIG_LOCALVERSION_AUTO
> localversion-auto := \
> - $(shell $(PERL) $(srctree)/scripts/setlocalversion $(srctree))
> + $(shell $(PERL) $(srctree)/scripts/setlocalversion $(srctree))
> LOCALVERSION := $(LOCALVERSION)$(localversion-auto)
> endif
In this case it makes sense - thanks.
Sam
On Wed, Apr 06, 2005 at 12:32:52AM +1200, Reuben Farrelly wrote:
> Hi again
>
> At 12:14 a.m. 6/04/2005, Adrian Bunk wrote:
> >On Tue, Apr 05, 2005 at 08:34:11PM +1200, Reuben Farrelly wrote:
> >
> >> Hi,
> >
> >Hi Reuben,
> >
> >>...
> >> Hrm. Something changed between the last -mm release which compiled
> >> through, and this one..
> >>...
> >> LD .tmp_vmlinux1
> >> arch/i386/kernel/built-in.o(.init.text+0x1823): In function `setup_arch':
> >> : undefined reference to `acpi_boot_table_init'
> >> arch/i386/kernel/built-in.o(.init.text+0x1828): In function `setup_arch':
> >> : undefined reference to `acpi_boot_init'
> >> make: *** [.tmp_vmlinux1] Error 1
> >> [root@tornado linux-2.6]#
> >>
> >> Backing out bk-acpi.patch works around it..
> >
> >Please send your .config .
>
> Have just figured out that it seems to be caused by having ACPI
> disabled in .config, once I re-enabled ACPI the build problem went away.
>
> Config attached anyway, I imagine the problem is quite reproduceable..
Ah, this was the working .config .
fter setting CONFIG_ACPI=n I started seeing different but most likely
related problems.
@Len:
ACPI=y and ACPI_BOOT=n seems to be a legal configuration (with
X86_HT=y), but it breaks into pieces if you try the compilation.
The first error I get is:
<-- snip -->
CC arch/i386/kernel/setup.o
arch/i386/kernel/setup.c:96: error: parse error before "acpi_sci_flags"
arch/i386/kernel/setup.c:96: warning: type defaults to `int' in
declaration of `acpi_sci_flags'
arch/i386/kernel/setup.c:96: warning: data definition has no type or
storage class
arch/i386/kernel/setup.c: In function `parse_cmdline_early':
arch/i386/kernel/setup.c:811: error: request for member `trigger' in
something not a structure or union
arch/i386/kernel/setup.c:814: error: request for member `trigger' in
something not a structure or union
arch/i386/kernel/setup.c:817: error: request for member `polarity' in
something not a structure or union
arch/i386/kernel/setup.c:820: error: request for member `polarity' in
something not a structure or union
arch/i386/kernel/setup.c: In function `setup_arch':
arch/i386/kernel/setup.c:1571: warning: implicit declaration of function
`acpi_boot_table_init'
arch/i386/kernel/setup.c:1572: warning: implicit declaration of function
`acpi_boot_init'
make[1]: *** [arch/i386/kernel/setup.o] Error 1
make: *** [arch/i386/kernel] Error 2
<-- snip -->
> Reuben
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
On Tue, Apr 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
No, I just didn't get a chance to send mail yet.
Compared to 2.6.11-ac5, I'm seeing one regression: the part of the
resume where it says something like:
swsusp: reading slkf;jalksfsadflkjas;dlfasdfkl (12345 pages): 34%
[sorry, I just got up so my short-term memory isn't working that well
yet]
takes 10-30 minutes (depending on whether it's closer to 11000 pages or
20000) rather than the 5-10 seconds or so that it takes under 2.6.11-ac5
(or mainline 2.6.11 if I remember correctly).
However, this is not vanilla 2.6.12-rc1-mm4. It has my own modified
version of the Win4Lin patch applied; this is GPL, but the userspace
program that uses this patch (Win4Lin 5.1) isn't, nor is the software
ultimately executed by this patch via Win4Lin (Microsoft Windows
Millennium Edition[*]). And I didn't try swsusp on any kernels between
2.6.11 and 2.6.12-rc1-mm4.
I'll try to do some more testing to see (a) when this problem started
and (b) whether it still exists in 2.6.12-rc2 or later. This is going to
be ridiculously difficult for me to fit into my schedule right now, but
I'll try....
BTW, ieee1394 is still broken after resume (impossible to rmmod, too) and
snd_cmipci (but this can be resurrected by quitting anything that uses
sound, rmmod snd_cmipci, then modprobe snd_cmipci). But these are
long-standing issues, and under 2.6.12-rc1-mm4, ieee1394/sbp2 can at
least stay up indefinitely as long as I don't suspend -- that's a
tremendous improvement over 2.6.11.
-Barry K. Nathan <[email protected]>
On Tue, Apr 05, 2005 at 06:44:08AM -0700, Barry K. Nathan wrote:
> swsusp: reading slkf;jalksfsadflkjas;dlfasdfkl (12345 pages): 34%
> [sorry, I just got up so my short-term memory isn't working that well
> yet]
>
> takes 10-30 minutes (depending on whether it's closer to 11000 pages or
> 20000) rather than the 5-10 seconds or so that it takes under 2.6.11-ac5
> (or mainline 2.6.11 if I remember correctly).
[snip]
> I'll try to do some more testing to see (a) when this problem started
> and (b) whether it still exists in 2.6.12-rc2 or later. This is going to
> be ridiculously difficult for me to fit into my schedule right now, but
> I'll try....
2.6.11-bk9 works (actually it takes under 2 seconds, not 5-10).
2.6.11-bk10 has the weird slowdown.
I'll see if I can isolate it any further.
-Barry K. Nathan <[email protected]>
On Tue, Apr 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.12-rc1-mm4:
>...
> +ib-mthca-add-support-for-new-mt25204-hca.patch
>
> Infiniband update
>...
This patch causes the following compile warning:
<-- snip -->
...
CC drivers/infiniband/hw/mthca/mthca_main.o
drivers/infiniband/hw/mthca/mthca_main.c: In function `mthca_init_icm':
drivers/infiniband/hw/mthca/mthca_main.c:479: warning: label
`err_unmap_eqp' defined but not used
...
<-- snip -->
I'm not sure whether this patch to remove this label is correct, but if
it isn't correct there must be a bug somewhere.
Signed-off-by: Adrian Bunk <[email protected]>
--- linux-2.6.12-rc2-mm1-full/drivers/infiniband/hw/mthca/mthca_main.c.old 2005-04-05 16:18:09.000000000 +0200
+++ linux-2.6.12-rc2-mm1-full/drivers/infiniband/hw/mthca/mthca_main.c 2005-04-05 16:19:15.000000000 +0200
@@ -475,8 +475,6 @@
err_unmap_rdb:
mthca_free_icm_table(mdev, mdev->qp_table.rdb_table);
-
-err_unmap_eqp:
mthca_free_icm_table(mdev, mdev->qp_table.eqp_table);
err_unmap_qp:
On Tue, 2005-04-05 at 10:24, Adrian Bunk wrote:
> On Tue, Apr 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
> >...
> > Changes since 2.6.12-rc1-mm4:
> >...
> > +ib-mthca-add-support-for-new-mt25204-hca.patch
> >
> > Infiniband update
> >...
>
>
> This patch causes the following compile warning:
>
> <-- snip -->
>
> ...
> CC drivers/infiniband/hw/mthca/mthca_main.o
> drivers/infiniband/hw/mthca/mthca_main.c: In function `mthca_init_icm':
> drivers/infiniband/hw/mthca/mthca_main.c:479: warning: label
> `err_unmap_eqp' defined but not used
> ...
>
> <-- snip -->
>
>
> I'm not sure whether this patch to remove this label is correct, but if
> it isn't correct there must be a bug somewhere.
>
>
> Signed-off-by: Adrian Bunk <[email protected]>
>
> --- linux-2.6.12-rc2-mm1-full/drivers/infiniband/hw/mthca/mthca_main.c.old 2005-04-05 16:18:09.000000000 +0200
> +++ linux-2.6.12-rc2-mm1-full/drivers/infiniband/hw/mthca/mthca_main.c 2005-04-05 16:19:15.000000000 +0200
> @@ -475,8 +475,6 @@
>
> err_unmap_rdb:
> mthca_free_icm_table(mdev, mdev->qp_table.rdb_table);
> -
> -err_unmap_eqp:
> mthca_free_icm_table(mdev, mdev->qp_table.eqp_table);
>
> err_unmap_qp:
Roland caught this recently and there is a patch for this which will
sent upstream. The proper fix is different from this.
-- Hal
> bk-kbuild.patch
Something has broken make O= :
$ make mrproper
$ mkdir /tmp/42
$ make ARCH=alpha CROSS_COMPILE=alpha-linux- O=/tmp/42 defconfig
$ make ARCH=alpha CROSS_COMPILE=alpha-linux- O=/tmp/42
Using /home/jdittmer/src/lk/linus as source for kernel
GEN /tmp/42/Makefile
CHK include/linux/version.h
SYMLINK /tmp/42/include/asm -> include/asm-alpha
SPLIT include/linux/autoconf.h -> include/config/*
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/mod/modpost.o
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
HOSTCC scripts/kallsyms
HOSTCC scripts/conmakehash
make[1]: *** No rule to make target `include/asm', needed by `arch/alpha/kernel/asm-offsets.s'. Stop.
make: *** [_all] Error 2
Happens for most archs. See http://l4x.org/k/
Jan
On Tue, 2005-04-05 at 08:45 +0100, Christoph Hellwig wrote:
> This introduces various AUDIT_ARCH numerical constants, which is a blatantly
> stupid idea. We already have a way to uniquely identify architectures, and
> that's the ELF headers, no need for another parallel namespace.
We do use the EM_xxx number space but that isn't sufficient to
distinguish between 32-bit and 64-bit incarnations of certain machine
types (S390,SH,MIPS,...). I didn't much like adding it either, but
couldn't see a better option.
I pondered strings but we want to filter on this and don't want to have
to use strcmp. Got any better answers?
> (btw, could you please add to all patches who's responsible for them,
> bk-audit.patch doesn't tell)
If it were just to point to the BK tree, that might help.
( linux-audit.bkbits.net/audit-2.6-mm )
--
dwmw2
Hi Andrew,
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
Yes, works for me. DRI (i915) is working again and USB is now happy
after a PM resume too.
> CC drivers/infiniband/hw/mthca/mthca_main.o
> drivers/infiniband/hw/mthca/mthca_main.c: In function `mthca_init_icm':
> drivers/infiniband/hw/mthca/mthca_main.c:479: warning: label
> `err_unmap_eqp' defined but not used
Thanks, good catch. I screwed up the error path in that function a
little while merging patches. Here's the correct fix.
Correct unwinding in error path of mthca_init_icm().
Signed-off-by: Roland Dreier <[email protected]>
--- linux-2.6.12-rc2-mm1.orig/drivers/infiniband/hw/mthca/mthca_main.c 2005-04-05 09:49:02.944473724 -0700
+++ linux-2.6.12-rc2-mm1/drivers/infiniband/hw/mthca/mthca_main.c 2005-04-05 09:49:15.679708865 -0700
@@ -437,7 +437,7 @@
if (!mdev->qp_table.rdb_table) {
mthca_err(mdev, "Failed to map RDB context memory, aborting\n");
err = -ENOMEM;
- goto err_unmap_rdb;
+ goto err_unmap_eqp;
}
mdev->cq_table.table = mthca_alloc_icm_table(mdev, init_hca->cqc_base,
* Brice Goglin <[email protected]> wrote:
> >could you send the full bootlog (starting at the 'gcc...' line)? I'm not
> >sure whether TSC calibration was done on your CPU. If cyc2ns_scale is
> >not set up then sched_clock() will return 0, and this could result in
> >that printk symptom.
>
> Here you are.
weird - none of the WARN_ON(1)'s show up. In particular, the
sched_clock() ones should have triggered at least once! I've attached a
new version of the patch below (please unapply the previous patch),
could you try it and send me the log? (It will unconditionally print
something in tsc_init(), which is always called during the boot
process.)
Ingo
--- linux/arch/i386/kernel/timers/timer_tsc.c.orig
+++ linux/arch/i386/kernel/timers/timer_tsc.c
@@ -137,16 +137,15 @@ static unsigned long long monotonic_cloc
unsigned long long sched_clock(void)
{
unsigned long long this_offset;
+ static int once = 1;
- /*
- * In the NUMA case we dont use the TSC as they are not
- * synchronized across all CPUs.
- */
-#ifndef CONFIG_NUMA
- if (!use_tsc)
-#endif
+ if (!cpu_has_tsc) {
+ if (once) { once = 0; WARN_ON(1); }
/* no locking but a rare wrong value is not a big deal */
return jiffies_64 * (1000000000 / HZ);
+ }
+
+ if (once) { once = 0; WARN_ON(1); }
/* Read the Time Stamp Counter */
rdtscll(this_offset);
@@ -434,7 +433,8 @@ static void mark_offset_tsc(void)
static int __init init_tsc(char* override)
{
-
+ printk("TSC init.\n");
+ WARN_ON(1);
/* check clock override */
if (override[0] && strncmp(override,"tsc",3)) {
#ifdef CONFIG_HPET_TIMER
@@ -443,6 +443,7 @@ static int __init init_tsc(char* overrid
} else
#endif
{
+ WARN_ON(1);
return -ENODEV;
}
}
@@ -518,8 +519,10 @@ static int __init init_tsc(char* overrid
}
set_cyc2ns_scale(cpu_khz/1000);
return 0;
- }
+ } else
+ WARN_ON(1);
}
+ WARN_ON(1);
return -ENODEV;
}
@@ -528,12 +531,14 @@ static int __init init_tsc(char* overrid
* in cpu/common.c */
static int __init tsc_setup(char *str)
{
+ WARN_ON(1);
tsc_disable = 1;
return 1;
}
#else
static int __init tsc_setup(char *str)
{
+ WARN_ON(1);
printk(KERN_WARNING "notsc: Kernel compiled with CONFIG_X86_TSC, "
"cannot disable TSC.\n");
return 1;
--- linux/arch/i386/kernel/timers/common.c.orig
+++ linux/arch/i386/kernel/timers/common.c
@@ -39,8 +39,10 @@ unsigned long __init calibrate_tsc(void)
/* Error: ECTCNEVERSET */
- if (count <= 1)
+ if (count <= 1) {
+ WARN_ON(1);
goto bad_ctc;
+ }
/* 64-bit subtract - gcc just messes up with long longs */
__asm__("subl %2,%0\n\t"
@@ -50,12 +52,16 @@ unsigned long __init calibrate_tsc(void)
"0" (endlow), "1" (endhigh));
/* Error: ECPUTOOFAST */
- if (endhigh)
+ if (endhigh) {
+ WARN_ON(1);
goto bad_ctc;
+ }
/* Error: ECPUTOOSLOW */
- if (endlow <= CALIBRATE_TIME)
+ if (endlow <= CALIBRATE_TIME) {
+ WARN_ON(1);
goto bad_ctc;
+ }
__asm__("divl %2"
:"=a" (endlow), "=d" (endhigh)
@@ -107,12 +113,16 @@ unsigned long __init calibrate_tsc_hpet(
"0" (tsc_endlow), "1" (tsc_endhigh));
/* Error: ECPUTOOFAST */
- if (tsc_endhigh)
+ if (tsc_endhigh) {
+ WARN_ON(1);
goto bad_calibration;
+ }
/* Error: ECPUTOOSLOW */
- if (tsc_endlow <= CALIBRATE_TIME_HPET)
+ if (tsc_endlow <= CALIBRATE_TIME_HPET) {
+ WARN_ON(1);
goto bad_calibration;
+ }
ASM_DIV64_REG(result, remain, tsc_endlow, 0, CALIBRATE_TIME_HPET);
if (remain > (tsc_endlow >> 1))
On Tue, Apr 05, 2005 at 05:33:49PM +1000, Nick Piggin wrote:
> Andrew Morton wrote:
>
> > +sched-remove-unnecessary-sched-domains.patch
> > +sched-improve-pinned-task-handling-again.patch
> [snip]
> >
> > CPU scheduler updates
> >
>
> It is no problem that you picked these up for testing. But
> don't merge them yet, please.
>
> Suresh's underlying problem with the unnecessary sched domains
> is a failing of sched-balance-exec and sched-balance-fork, which
That wasn't the only motivation. For example, on non-HT cpu's we shouldn't
be setting up SMT sched-domain, same with NUMA domains on non-NUMA systems.
> I am working on now.
>
> Removing unnecessary domains is a nice optimisation, but just
> needs to account for a few more flags before declaring that a
Can you elaborate when we require a domain with special flags but has
no or only one group in it.
> domain is unnecessary (not to mention this probably breaks if
> isolcpus= is used). I have made some modifications to the patch
I have tested my patch with "ioslcpus=" and it works just fine.
> to fix these problems.
>
> Lastly, I'd like to be a bit less intrusive with pinned task
> handling improvements. I think we can do this while still being
> effective in preventing livelocks.
We want to see this fixed. Please post your patch and I can let you know
the test results.
>
> I will keep you posted with regards to the various scheduler
> patches.
Nick, Can you post the patches you sent me earlier to this list?
thanks,
suresh
Adrian Bunk wrote:
> On Wed, Apr 06, 2005 at 12:32:52AM +1200, Reuben Farrelly wrote:
>
>>Hi again
>>
>>At 12:14 a.m. 6/04/2005, Adrian Bunk wrote:
>>
>>>On Tue, Apr 05, 2005 at 08:34:11PM +1200, Reuben Farrelly wrote:
>>>
>>>
>>>>Hi,
>>>
>>>Hi Reuben,
>>>
>>>
>>>>...
>>>>Hrm. Something changed between the last -mm release which compiled
>>>>through, and this one..
>>>>...
>>>> LD .tmp_vmlinux1
>>>>arch/i386/kernel/built-in.o(.init.text+0x1823): In function `setup_arch':
>>>>: undefined reference to `acpi_boot_table_init'
>>>>arch/i386/kernel/built-in.o(.init.text+0x1828): In function `setup_arch':
>>>>: undefined reference to `acpi_boot_init'
>>>>make: *** [.tmp_vmlinux1] Error 1
>>>>[root@tornado linux-2.6]#
>>>>
>>>>Backing out bk-acpi.patch works around it..
>>>
>>>Please send your .config .
>>
>>Have just figured out that it seems to be caused by having ACPI
>>disabled in .config, once I re-enabled ACPI the build problem went away.
>>
>>Config attached anyway, I imagine the problem is quite reproduceable..
>
>
> Ah, this was the working .config .
> fter setting CONFIG_ACPI=n I started seeing different but most likely
> related problems.
>
>
> @Len:
> ACPI=y and ACPI_BOOT=n seems to be a legal configuration (with
> X86_HT=y), but it breaks into pieces if you try the compilation.
>
Here is some additional and hopefully helpful information.
Without CONFIG_ACPI=y, I first got:
arch/i386/kernel/setup.c: In function 'setup_arch':
arch/i386/kernel/setup.c:1571: warning: implicit declaration of function 'acpi_boot_table_init'
arch/i386/kernel/setup.c:1572: warning: implicit declaration of function 'acpi_boot_init'
and then at the end:
arch/i386/kernel/built-in.o(.init.text+0x1b81): In function `setup_arch':
: undefined reference to `acpi_boot_table_init'
arch/i386/kernel/built-in.o(.init.text+0x1b86): In function `setup_arch':
: undefined reference to `acpi_boot_init'
make: *** [.tmp_vmlinux1] Error 1
With these set linux-2.6.12-rc2-mm1 built OK.
[steven@spc1 linux-2.6.12-rc2-mm1]$ grep ^CONFIG_ACPI .config
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
Steven
On Tue, Apr 05, 2005 at 05:45:58PM +0200, Jan Dittmer wrote:
> Something has broken make O= :
>
> HOSTCC scripts/kallsyms
> HOSTCC scripts/conmakehash
> make[1]: *** No rule to make target `include/asm', needed by `arch/alpha/kernel/asm-offsets.s'. Stop.
> make: *** [_all] Error 2
>
> Happens for most archs. See http://l4x.org/k/
Thanks - here is a patch:
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2005/04/05 23:37:09+02:00 [email protected]
# kbuild: fix make O=... build
#
# It fixes the following error:
#
# make[1]: *** No rule to make target `include/asm', needed by `arch/alpha/kernel/asm-offsets.s'. Stop.
#
# Reported by:
# From: Jan Dittmer <[email protected]>
#
# In same patch fix spaces to tabs as reported by:
# From: Adrian Bunk <[email protected]>
#
# Signed-off-by: Sam Ravnborg <[email protected]>
#
# Makefile
# 2005/04/05 23:36:45+02:00 [email protected] +3 -3
# fix make O=... build
#
diff -Nru a/Makefile b/Makefile
--- a/Makefile 2005-04-05 23:37:38 +02:00
+++ b/Makefile 2005-04-05 23:37:38 +02:00
@@ -576,7 +576,7 @@
ifdef CONFIG_LOCALVERSION_AUTO
localversion-auto := \
- $(shell $(PERL) $(srctree)/scripts/setlocalversion $(srctree))
+ $(shell $(PERL) $(srctree)/scripts/setlocalversion $(srctree))
LOCALVERSION := $(LOCALVERSION)$(localversion-auto)
endif
@@ -808,7 +808,7 @@
# prepare1 creates a makefile if using a separate output directory
prepare1: prepare2 outputmakefile
-prepare0: prepare1 include/linux/version.h $(objtree)/include/asm \
+prepare0: prepare1 include/linux/version.h include/asm \
include/config/MARKER
ifneq ($(KBUILD_MODULES),)
$(Q)rm -rf $(MODVERDIR)
@@ -845,7 +845,7 @@
# hard to detect, but I suppose "make mrproper" is a good idea
# before switching between archs anyway.
-$(objtree)/include/asm:
+include/asm:
@echo ' SYMLINK $@ -> include/asm-$(ARCH)'
$(Q)if [ ! -d include ]; then mkdir -p include; fi;
@ln -fsn asm-$(ARCH) $@
On Tue, Apr 05, 2005 at 07:14:45AM -0700, Barry K. Nathan wrote:
> 2.6.11-bk9 works (actually it takes under 2 seconds, not 5-10).
> 2.6.11-bk10 has the weird slowdown.
>
> I'll see if I can isolate it any further.
2.6.11-mm2 works, but 2.6.11-mm3 has the ridiculously slow resumes.
Later today I'll see if I can narrow things down any further (e.g. to a
specific patch in 2.6.11-mm3 or whatever).
-Barry K. Nathan <[email protected]>
Siddha, Suresh B wrote:
> On Tue, Apr 05, 2005 at 05:33:49PM +1000, Nick Piggin wrote:
>>Suresh's underlying problem with the unnecessary sched domains
>>is a failing of sched-balance-exec and sched-balance-fork, which
>
>
> That wasn't the only motivation. For example, on non-HT cpu's we shouldn't
> be setting up SMT sched-domain, same with NUMA domains on non-NUMA systems.
>
Yep, sure. It is a good, if slight, optimisation. And I've also just
slightly extended your patch, so we don't have any domains if booting
with maxcpus=1
>
>>I am working on now.
>>
>>Removing unnecessary domains is a nice optimisation, but just
>>needs to account for a few more flags before declaring that a
>
>
> Can you elaborate when we require a domain with special flags but has
> no or only one group in it.
>
The SD_WAKE_* flags do not use groups, so it would be legitimate to
have a domain that has one of these set, with no groups.
>
>>domain is unnecessary (not to mention this probably breaks if
>>isolcpus= is used). I have made some modifications to the patch
>
>
> I have tested my patch with "ioslcpus=" and it works just fine.
>
OK, my apologies ;)
>
>>to fix these problems.
>>
>>Lastly, I'd like to be a bit less intrusive with pinned task
>>handling improvements. I think we can do this while still being
>>effective in preventing livelocks.
>
>
> We want to see this fixed. Please post your patch and I can let you know
> the test results.
>
I will try to get it working and tested tonight for you.
>
>>I will keep you posted with regards to the various scheduler
>>patches.
>
>
> Nick, Can you post the patches you sent me earlier to this list?
>
Yep, I'll post them.
--
SUSE Labs, Novell Inc.
"Barry K. Nathan" <[email protected]> wrote:
>
> On Tue, Apr 05, 2005 at 06:44:08AM -0700, Barry K. Nathan wrote:
> > swsusp: reading slkf;jalksfsadflkjas;dlfasdfkl (12345 pages): 34%
> > [sorry, I just got up so my short-term memory isn't working that well
> > yet]
> >
> > takes 10-30 minutes (depending on whether it's closer to 11000 pages or
> > 20000) rather than the 5-10 seconds or so that it takes under 2.6.11-ac5
> > (or mainline 2.6.11 if I remember correctly).
Odd.
> [snip]
> > I'll try to do some more testing to see (a) when this problem started
> > and (b) whether it still exists in 2.6.12-rc2 or later. This is going to
> > be ridiculously difficult for me to fit into my schedule right now, but
> > I'll try....
>
> 2.6.11-bk9 works (actually it takes under 2 seconds, not 5-10).
> 2.6.11-bk10 has the weird slowdown.
Unfortunately that's a pretty bug diff (2 megs).
The only thing I can see in the memory reclaim area is this:
--- b/mm/vmscan.c 2005-03-10 00:39:02 -08:00
+++ b/mm/vmscan.c 2005-03-13 15:29:39 -08:00
@@ -313,8 +313,20 @@
*/
if (!is_page_cache_freeable(page))
return PAGE_KEEP;
- if (!mapping)
+ if (!mapping) {
+ /*
+ * Some data journaling orphaned pages can have
+ * page->mapping == NULL while being dirty with clean buffers.
+ */
+ if (PageDirty(page) && PagePrivate(page)) {
+ if (try_to_free_buffers(page)) {
+ ClearPageDirty(page);
+ printk("%s: orphaned page\n", __FUNCTION__);
+ return PAGE_CLEAN;
+ }
+ }
return PAGE_KEEP;
+ }
if (mapping->a_ops->writepage == NULL)
return PAGE_ACTIVATE;
if (!may_write_to_queue(mapping->backing_dev_info))
but you'd be getting a printk storm if that was triggering.
> I'll see if I can isolate it any further.
Please, that would help.
Steven Cole <[email protected]> wrote:
>
> arch/i386/kernel/setup.c: In function 'setup_arch':
> arch/i386/kernel/setup.c:1571: warning: implicit declaration of function 'acpi_boot_table_init'
> arch/i386/kernel/setup.c:1572: warning: implicit declaration of function 'acpi_boot_init'
diff -puN include/linux/acpi.h~no-acpi-build-fix include/linux/acpi.h
--- 25/include/linux/acpi.h~no-acpi-build-fix 2005-04-05 00:14:46.000000000 -0700
+++ 25-akpm/include/linux/acpi.h 2005-04-05 00:23:39.000000000 -0700
@@ -418,16 +418,6 @@ extern int sbf_port ;
#define acpi_mp_config 0
-static inline int acpi_boot_init(void)
-{
- return 0;
-}
-
-static inline int acpi_boot_table_init(void)
-{
- return 0;
-}
-
#endif /*!CONFIG_ACPI_BOOT*/
unsigned int acpi_register_gsi (u32 gsi, int edge_level, int active_high_low);
@@ -538,5 +528,18 @@ static inline int acpi_get_pxm(acpi_hand
extern int pnpacpi_disabled;
+#else /* CONFIG_ACPI */
+
+static inline int acpi_boot_init(void)
+{
+ return 0;
+}
+
+static inline int acpi_boot_table_init(void)
+{
+ return 0;
+}
+
#endif /* CONFIG_ACPI */
+
#endif /* _LINUX_ACPI_H */
_
On Tuesday April 5, [email protected] wrote:
>
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
Well, Seeing you asked...
PM resume certainly seems to be improving.
My main problem in rc1-mm3 is with PCMCIA.
If I stop cardmgr before suspend-to-RAM, and then try to
restart it after resume, I cannot. Some message about the socket
being in use, and am I sure there is no other cardmgr running (there
isn't).
I can stop and restart happily before suspending, but not after.
If I leave it running during a suspend/resume cycle it keeps working
but if I then stop and restart, it fails.
(and if I do leave it running, my PCMCIA wireless gets started before
my tg3 wired, so eth0 and eth1 get swapped).
I just tried rc2-mm1 and... decided to go back to rc1-mm3.
It seemed to boot mostly OK. I tried suspend-to-RAM and it seems to
suspend. But when I turned it back on again it rebooted rather than
resumed.
During boot I got:
Apr 6 10:18:46 localhost kernel: cs: memory probe 0xf6000000-0xfbffffff:iounmap: bad address f8828000
Apr 6 10:18:46 localhost kernel: [set_cis_map+150/256] set_cis_map+0x96/0x100
Apr 6 10:18:46 localhost kernel: [remove_vm_area+60/80] remove_vm_area+0x3c/0x50
Apr 6 10:18:46 localhost kernel: [pcmcia_read_cis_mem+412/560] pcmcia_read_cis_mem+0x19c/0x230
Apr 6 10:18:46 localhost kernel: [set_cis_map+150/256] set_cis_map+0x96/0x100
Apr 6 10:18:46 localhost kernel: [read_cis_cache+358/400] read_cis_cache+0x166/0x190
Apr 6 10:18:46 localhost kernel: [follow_link+141/544] follow_link+0x8d/0x220
Apr 6 10:18:46 localhost kernel: [pccard_get_next_tuple+688/784] pccard_get_next_tuple+0x2b0/0x310
Apr 6 10:18:46 localhost kernel: [pccard_get_first_tuple+144/336] pccard_get_first_tuple+0x90/0x150
Apr 6 10:18:46 localhost kernel: [pccard_validate_cis+151/592] pccard_validate_cis+0x97/0x250
Apr 6 10:18:46 localhost kernel: [readable+90/160] readable+0x5a/0xa0
Apr 6 10:18:46 localhost kernel: [cis_readable+129/224] cis_readable+0x81/0xe0
Apr 6 10:18:46 localhost kernel: [do_mem_probe+469/496] do_mem_probe+0x1d5/0x1f0
Apr 6 10:18:46 localhost kernel: [inv_probe+159/176] inv_probe+0x9f/0xb0
Apr 6 10:18:46 localhost kernel: [validate_mem+271/304] validate_mem+0x10f/0x130
Apr 6 10:18:46 localhost kernel: [default_wake_function+0/32] default_wake_function+0x0/0x20
Apr 6 10:18:46 localhost kernel: [pcmcia_nonstatic_validate_mem+120/128] pcmcia_nonstatic_validate_mem+0x78/0x80
Apr 6 10:18:46 localhost kernel: [pcmcia_validate_mem+26/32] pcmcia_validate_mem+0x1a/0x20
Apr 6 10:18:46 localhost kernel: [pcmcia_card_add+42/208] pcmcia_card_add+0x2a/0xd0
....
Then it hung in some device discovery. Not sure which device, maybe
firewire.
Alt-Sysrq-T showed
Apr 6 10:19:45 localhost kernel: khpsbpkt S C04643E0 0 1956 1 1973 915 (L-TLB)
Apr 6 10:19:45 localhost kernel: f6cf3f94 00000046 f68dd070 c04643e0 f7c0f030 c0464410 00000000 f7c0f030
Apr 6 10:19:45 localhost kernel: f6cf3f8c 00000000 00000000 00000000 f68dd070 f68dd198 f8af2444 f6cf2000
Apr 6 10:19:45 localhost kernel: 00000246 f68dd070 c031ce5d f8af244c 00000000 00000001 f68dd070 c0114a70
Apr 6 10:19:45 localhost kernel: Call Trace:
Apr 6 10:19:45 localhost kernel: [__down_interruptible+157/300] __down_interruptible+0x9d/0x12c
Apr 6 10:19:45 localhost kernel: [default_wake_function+0/32] default_wake_function+0x0/0x20
Apr 6 10:19:45 localhost kernel: [__down_failed_interruptible+7/12] __down_failed_interruptible+0x7/0xc
Apr 6 10:19:45 localhost kernel: [pg0+945105653/1067918336] .text.lock.ieee1394_core+0x1b/0x26 [ieee1394]
Apr 6 10:19:45 localhost kernel: [pg0+945105424/1067918336] hpsbpkt_thread+0x0/0xb0 [ieee1394]
Apr 6 10:19:45 localhost kernel: [kernel_thread_helper+5/24] kernel_thread_helper+0x5/0x18
Apr 6 10:19:45 localhost kernel: knodemgrd_0 S C04643E0 0 1973 1 2023 1956 (L-TLB)
Apr 6 10:19:45 localhost kernel: f7e75f7c 00000046 f7c0f030 c04643e0 0000a1ff 00000000 c018a7cc f648e62c
Apr 6 10:19:45 localhost kernel: f6ec8380 00000000 00000000 00000000 f7c0f030 f7c0f158 f6f6b670 f7e74000
Apr 6 10:19:45 localhost kernel: 00000246 f7c0f030 c031ce5d f6f6b678 00000000 00000001 f7c0f030 c0114a70
Apr 6 10:19:45 localhost kernel: Call Trace:
Apr 6 10:19:45 localhost kernel: [sysfs_make_dirent+44/160] sysfs_make_dirent+0x2c/0xa0
Apr 6 10:19:45 localhost kernel: [__down_interruptible+157/300] __down_interruptible+0x9d/0x12c
Apr 6 10:19:45 localhost kernel: [default_wake_function+0/32] default_wake_function+0x0/0x20
Apr 6 10:19:45 localhost kernel: [__down_failed_interruptible+7/12] __down_failed_interruptible+0x7/0xc
Apr 6 10:19:45 localhost kernel: [pg0+945133083/1067918336] .text.lock.nodemgr+0x112/0x1a7 [ieee1394]
Apr 6 10:19:45 localhost kernel: [pg0+945131536/1067918336] nodemgr_host_thread+0x0/0x190 [ieee1394]
Apr 6 10:19:45 localhost kernel: [kernel_thread_helper+5/24] kernel_thread_helper+0x5/0x18
Apr 6 10:19:45 localhost kernel: grep D C04643E0 0 2023 1 2036 1973 (NOTLB)
Apr 6 10:19:45 localhost kernel: f640beec 00000086 f6c6da50 c04643e0 00000000 f640bec4 f710ca50 f640bec4
Apr 6 10:19:45 localhost kernel: f640bec4 00000000 00000000 00000000 f6c6da50 f6c6db78 f7291424 f6c6da50
Apr 6 10:19:45 localhost kernel: 00000282 f729142c c031cd4b 00000001 f6c6da50 c0114a70 f729142c f729142c
Apr 6 10:19:45 localhost kernel: Call Trace:
Apr 6 10:19:45 localhost kernel: [__down+123/240] __down+0x7b/0xf0
Apr 6 10:19:45 localhost kernel: [default_wake_function+0/32] default_wake_function+0x0/0x20
Apr 6 10:19:45 localhost kernel: [__down_failed+7/12] __down_failed+0x7/0xc
Apr 6 10:19:45 localhost kernel: [.text.lock.usb+22/186] .text.lock.usb+0x16/0xba
Apr 6 10:19:45 localhost kernel: [usb_device_read+186/288] usb_device_read+0xba/0x120
Apr 6 10:19:45 localhost kernel: [usb_device_read+0/288] usb_device_read+0x0/0x120
Apr 6 10:19:45 localhost kernel: [vfs_read+182/368] vfs_read+0xb6/0x170
Apr 6 10:19:45 localhost kernel: [sys_read+81/128] sys_read+0x51/0x80
Apr 6 10:19:45 localhost kernel: [syscall_call+7/11] syscall_call+0x7/0xb
I think those are the interesting processes, but I can get the full
list if it is useful.
I managed to proceed into the boot with alt-sysrq-E (tErm) but when it
came up enough bits had been killed that I decided to cut my losses
and go back to a previous working kernel...
This in on a Dell Lattitude D800
NeilBrown
>@Len:
>ACPI=y and ACPI_BOOT=n seems to be a legal configuration (with
>X86_HT=y), but it breaks into pieces if you try the compilation.
yeah, don't do that:-)
I'm sorry I didn't push the patch to delete CONFIG_ACPI_BOOT earlier.
For now, just enable them both.
thanks,
-Len
On Tue, Apr 05, 2005 at 05:56:00PM -0700, Andrew Morton wrote:
> Odd.
Yes, it is odd...
> > 2.6.11-bk9 works (actually it takes under 2 seconds, not 5-10).
> > 2.6.11-bk10 has the weird slowdown.
>
> Unfortunately that's a pretty bug diff (2 megs).
Yeah, I know. *sigh*
[snip]
> but you'd be getting a printk storm if that was triggering.
I'm not seeing a printk storm, at least, none that I can discern...
> > I'll see if I can isolate it any further.
>
> Please, that would help.
I'm working on it right now.
2.6.11 + linus.patch from 2.6.11-mm3 works.
2.6.11 + approx. 292 patches from 2.6.11-mm3 is broken.
2.6.11 + approx. 130 patches (a proper subset of the 292 patches) works.
(this is counting each subsystem bk tree as a single patch)
The diff between the latter two trees is still larger than the
2.6.11-bk9 -> -bk10 diff, but after one or two more iterations of
(psuedo-)binary search, it should be much smaller.
I'm planning to go as far as I can before going to bed tonight.
-Barry K. Nathan <[email protected]>
Ingo Molnar a ?crit :
> weird - none of the WARN_ON(1)'s show up. In particular, the
> sched_clock() ones should have triggered at least once! I've attached a
> new version of the patch below (please unapply the previous patch),
> could you try it and send me the log? (It will unconditionally print
> something in tsc_init(), which is always called during the boot
> process.)
Hi Ingo,
The result is exactly the same, except the following lines at the
begining of dmesg. Note that only these lines have a valid timestamp.
All remaining lines show 0.000.
[4294667.296000] Linux version 2.6.12-rc2-mm1=LoulousMobile
(bgoglin@puligny) (version gcc 3.3.5 (Debian 1:3.3.5-8)) #9 PREEMPT Tue
Apr 5 09:28:57 CEST 2005
[4294667.296000] Badness in sched_clock at
arch/i386/kernel/timers/timer_tsc.c:143
[4294667.296000] [<c010f464>] sched_clock+0x84/0x110
[4294667.296000] [<c01d7b5b>] vscnprintf+0x2b/0x40
[4294667.296000] [<c011e252>] vprintk+0xa2/0x260
[4294667.296000] [<c011e1a7>] printk+0x17/0x20
[4294667.296000] [<c046f6f4>] start_kernel+0x14/0x180
[4294667.296000] art_kernel+0x14/0x180
Brice
On Tue, Apr 05, 2005 at 05:56:00PM -0700, Andrew Morton wrote:
> > I'll see if I can isolate it any further.
>
> Please, that would help.
[Right now I'm in a race against my lack of sleep. I'm trying to send
this e-mail before I involuntarily fall asleep, so the contents
and/or recipient list may be incomplete...]
Ok, I've narrowed the problem down to one patch. In 2.6.11-mm3, the
problem goes away if I remove this patch:
swsusp-enable-resume-from-initrd.patch
(Recap of the problem in case this gets forwarded: Resume is almost
instant without the apparently-guilty patch. With the patch, resume
takes almost half an hour.)
BTW, there's another strange thing that's introduced by 2.6.11-rc2-mm1:
With that kernel, suspend is also ridiculously slow (speed is comparable
to the slow resume with the aforementioned patch). 2.6.11-rc2 does not
have that problem.
Also, with 2.6.12-rc2-mm1, this computer happens to hit the bug where
all the printk timestamps are 0000000.0000000 (don't take the # of
digits too literally). Probably unrelated, but I may as well mention it.
(System is an Athlon XP 2200+ with SiS chipset. I can't remember which
model of SiS chipset.)
-Barry K. Nathan <[email protected]>
Andrew Morton wrote:
> Steven Cole <[email protected]> wrote:
>
>>arch/i386/kernel/setup.c: In function 'setup_arch':
>> arch/i386/kernel/setup.c:1571: warning: implicit declaration of function 'acpi_boot_table_init'
>> arch/i386/kernel/setup.c:1572: warning: implicit declaration of function 'acpi_boot_init'
>
>
>
> diff -puN include/linux/acpi.h~no-acpi-build-fix include/linux/acpi.h
> --- 25/include/linux/acpi.h~no-acpi-build-fix 2005-04-05 00:14:46.000000000 -0700
> +++ 25-akpm/include/linux/acpi.h 2005-04-05 00:23:39.000000000 -0700
> @@ -418,16 +418,6 @@ extern int sbf_port ;
[patch snipped]
Yes, that worked with no CONFIG_ACPI. Thanks.
On a slightly offtopic note, I'm now using this gcc:
gcc (GCC) 4.0.0 20050308 (Red Hat 4.0.0-0.32)
I don't have any quantitative data at hand, this seems SLOOOOW.
I guess that's progress. But it slows down testing somewhat.
Steven
Index: linux-2.6/kernel/sched.c
===================================================================
--- linux-2.6.orig/kernel/sched.c 2005-04-07 02:39:22.000000000 +1000
+++ linux-2.6/kernel/sched.c 2005-04-07 02:45:26.000000000 +1000
@@ -2041,6 +2041,12 @@ static runqueue_t *find_busiest_queue(st
}
/*
+ * Max backoff if we encounter pinned tasks. Pretty arbitrary value, but
+ * so long as it is large enough.
+ */
+#define MAX_PINNED_INTERVAL 1024
+
+/*
* Check this_cpu to ensure it is balanced within domain. Attempt to move
* tasks if there is an imbalance.
*
@@ -2052,7 +2058,7 @@ static int load_balance(int this_cpu, ru
struct sched_group *group;
runqueue_t *busiest;
unsigned long imbalance;
- int nr_moved, all_pinned;
+ int nr_moved, all_pinned = 0;
int active_balance = 0;
spin_lock(&this_rq->lock);
@@ -2143,7 +2149,8 @@ out_balanced:
sd->nr_balance_failed = 0;
/* tune up the balancing interval */
- if (sd->balance_interval < sd->max_interval)
+ if ((all_pinned && sd->balance_interval < MAX_PINNED_INTERVAL) ||
+ (sd->balance_interval < sd->max_interval))
sd->balance_interval *= 2;
return 0;
Steven Cole <[email protected]> wrote:
>
> Andrew Morton wrote:
> > Steven Cole <[email protected]> wrote:
> >
> >>arch/i386/kernel/setup.c: In function 'setup_arch':
> >> arch/i386/kernel/setup.c:1571: warning: implicit declaration of function 'acpi_boot_table_init'
> >> arch/i386/kernel/setup.c:1572: warning: implicit declaration of function 'acpi_boot_init'
> >
> >
> >
> > diff -puN include/linux/acpi.h~no-acpi-build-fix include/linux/acpi.h
> > --- 25/include/linux/acpi.h~no-acpi-build-fix 2005-04-05 00:14:46.000000000 -0700
> > +++ 25-akpm/include/linux/acpi.h 2005-04-05 00:23:39.000000000 -0700
> > @@ -418,16 +418,6 @@ extern int sbf_port ;
> [patch snipped]
>
> Yes, that worked with no CONFIG_ACPI. Thanks.
OK, I'll keep spamming the acpi guys with it until they tell me to shut up.
> On a slightly offtopic note, I'm now using this gcc:
> gcc (GCC) 4.0.0 20050308 (Red Hat 4.0.0-0.32)
>
> I don't have any quantitative data at hand, this seems SLOOOOW.
> I guess that's progress. But it slows down testing somewhat.
>
There's a reason why I persist in keeping the kernel working with
gcc-2.95.4!
"Barry K. Nathan" <[email protected]> wrote:
>
> Ok, I've narrowed the problem down to one patch. In 2.6.11-mm3, the
> problem goes away if I remove this patch:
> swsusp-enable-resume-from-initrd.patch
That really helps, thanks.
The patch looks fairly innocent. I'll give up on this and cc the
developers.
> (Recap of the problem in case this gets forwarded: Resume is almost
> instant without the apparently-guilty patch. With the patch, resume
> takes almost half an hour.)
>
> BTW, there's another strange thing that's introduced by 2.6.11-rc2-mm1:
> With that kernel, suspend is also ridiculously slow (speed is comparable
> to the slow resume with the aforementioned patch). 2.6.11-rc2 does not
> have that problem.
Does reverting swsusp-enable-resume-from-initrd.patch fix this also?
> Also, with 2.6.12-rc2-mm1, this computer happens to hit the bug where
> all the printk timestamps are 0000000.0000000 (don't take the # of
> digits too literally). Probably unrelated, but I may as well mention it.
> (System is an Athlon XP 2200+ with SiS chipset. I can't remember which
> model of SiS chipset.)
Yes, sorry. Reverting
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/broken-out/sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
will fix that one.
Jindrich Makovicka <[email protected]> wrote:
>
> oes not compile on AthlonXP. For mmx_clear_page, only the prototype was
> changed, but the implementation is still the same. I guess that part of
> the patch slipped out somehow.
>
> -extern void mmx_clear_page(void *page);
>
> +extern void mmx_clear_page(void *page, int order);
I guess this will fix it...
diff -puN arch/i386/lib/mmx.c~add-a-clear_pages-function-to-clear-pages-of-higher-fix arch/i386/lib/mmx.c
--- 25/arch/i386/lib/mmx.c~add-a-clear_pages-function-to-clear-pages-of-higher-fix Wed Apr 6 15:00:54 2005
+++ 25-akpm/arch/i386/lib/mmx.c Wed Apr 6 15:06:09 2005
@@ -128,9 +128,10 @@ void *_mmx_memcpy(void *to, const void *
* other MMX using processors do not.
*/
-static void fast_clear_page(void *page)
+static void fast_clear_page(void *page, int order)
{
int i;
+ int chunks = (4096 << order) / 64;
kernel_fpu_begin();
@@ -138,8 +139,7 @@ static void fast_clear_page(void *page)
" pxor %%mm0, %%mm0\n" : :
);
- for(i=0;i<4096/64;i++)
- {
+ for (i = 0; i < chunks; i++) {
__asm__ __volatile__ (
" movntq %%mm0, (%0)\n"
" movntq %%mm0, 8(%0)\n"
@@ -257,18 +257,18 @@ static void fast_copy_page(void *to, voi
* Generic MMX implementation without K7 specific streaming
*/
-static void fast_clear_page(void *page)
+static void fast_clear_page(void *page, int order)
{
int i;
-
+ int chunks = (4096 << order) / 128;
+
kernel_fpu_begin();
__asm__ __volatile__ (
" pxor %%mm0, %%mm0\n" : :
);
- for(i=0;i<4096/128;i++)
- {
+ for (i = 0; i < chunks; i++) {
__asm__ __volatile__ (
" movq %%mm0, (%0)\n"
" movq %%mm0, 8(%0)\n"
@@ -359,23 +359,23 @@ static void fast_copy_page(void *to, voi
* Favour MMX for page clear and copy.
*/
-static void slow_zero_page(void * page)
+static void slow_zero_page(void *page, int order)
{
int d0, d1;
__asm__ __volatile__( \
"cld\n\t" \
"rep ; stosl" \
: "=&c" (d0), "=&D" (d1)
- :"a" (0),"1" (page),"0" (1024)
+ :"a" (0),"1" (page),"0" (1024 << order)
:"memory");
}
-void mmx_clear_page(void * page)
+void mmx_clear_page(void *page, int order)
{
if(unlikely(in_interrupt()))
- slow_zero_page(page);
+ slow_zero_page(page, order);
else
- fast_clear_page(page);
+ fast_clear_page(page, order);
}
static void slow_copy_page(void *to, void *from)
_
Neil Brown <[email protected]> wrote:
>
> On Tuesday April 5, [email protected] wrote:
> >
> > - Nobody said anything about the PM resume and DRI behaviour in
> > 2.6.12-rc1-mm4. So it's all perfect now?
>
> Well, Seeing you asked...
>
> PM resume certainly seems to be improving.
> My main problem in rc1-mm3 is with PCMCIA.
> If I stop cardmgr before suspend-to-RAM, and then try to
> restart it after resume, I cannot. Some message about the socket
> being in use, and am I sure there is no other cardmgr running (there
> isn't).
I don't know whether the PCMCIA problem is due to PCMCIA changes or not.
The only thing I see having changed between 2.6.12-rc1-mm3 and
2.6.12-rc2-mm1 is the addition of pcmcia-resource-handling-fixes.patch.
Would you have time to revert that, retest?
There have been a few problem in the area of device management in
bk-driver-core. I think we're getting that settled down now.
On Tuesday 05 April 2005 03:05, Andrew Morton wrote:
> - x86 NMI handling seems to be bust in 2.6.12-rc2. ?Try using
> ? `nmi_watchdog=0' if you experience weird crashes.
>
> - The possible kernel-timer related hangs might possibly be fixed. ?We
> ? haven't heard yet.
>
> - Nobody said anything about the PM resume and DRI behaviour in
> ? 2.6.12-rc1-mm4. ?So it's all perfect now?
>
> - Various fixes and updates. ?Nothing earth-shattering.
This refuses to boot here. It dies when assigning the EHCI driver. The mb is an MSI-7030 K8N Neo Platinium
based on a nForce 3 250Gb Chipset (x86_64). I`ve been on vacation - the last kernel tried was 11-mm3 which
booted fine but refuses to use all the usb ports supplied by the system (two work, three do not all using low
speed).
Any ideas what might be happening?
Ed Tomlinson
On Wed, Apr 06, 2005 at 02:27:49PM -0700, Andrew Morton wrote:
> "Barry K. Nathan" <[email protected]> wrote:
> >
> > Ok, I've narrowed the problem down to one patch. In 2.6.11-mm3, the
> > problem goes away if I remove this patch:
> > swsusp-enable-resume-from-initrd.patch
>
> That really helps, thanks.
You're welcome.
> The patch looks fairly innocent. I'll give up on this and cc the
> developers.
Yeah, it *seemed* innocent enough -- that's why I had to do a binary
search on the 2.6.11-mm3 "series" file in order to find it as the
culprit...
> > (Recap of the problem in case this gets forwarded: Resume is almost
> > instant without the apparently-guilty patch. With the patch, resume
> > takes almost half an hour.)
> >
> > BTW, there's another strange thing that's introduced by 2.6.11-rc2-mm1:
> > With that kernel, suspend is also ridiculously slow (speed is comparable
> > to the slow resume with the aforementioned patch). 2.6.11-rc2 does not
> > have that problem.
>
> Does reverting swsusp-enable-resume-from-initrd.patch fix this also?
No. Reverting it from 2.6.12-rc2-mm1 (oops, I got the version number
wrong in my previous mail -- and that should also be 2.6.12-rc2 not
2.6.11-rc2) speeds up resume to the original speed, but suspend is still
ridiculously slow. Time to narrow things down again, I presume...
> > Also, with 2.6.12-rc2-mm1, this computer happens to hit the bug where
> > all the printk timestamps are 0000000.0000000 (don't take the # of
> > digits too literally). Probably unrelated, but I may as well mention it.
> > (System is an Athlon XP 2200+ with SiS chipset. I can't remember which
> > model of SiS chipset.)
>
> Yes, sorry. Reverting
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/broken-out/sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
> will fix that one.
I kind of figured that from another LKML discussion but I wasn't 100%
sure that's what I should do.
-Barry K. Nathan <[email protected]>
On Wed, Apr 06, 2005 at 08:06:14PM -0700, Barry K. Nathan wrote:
> > > BTW, there's another strange thing that's introduced by 2.6.11-rc2-mm1:
> > > With that kernel, suspend is also ridiculously slow (speed is comparable
> > > to the slow resume with the aforementioned patch). 2.6.11-rc2 does not
> > > have that problem.
> >
> > Does reverting swsusp-enable-resume-from-initrd.patch fix this also?
>
> No. Reverting it from 2.6.12-rc2-mm1 (oops, I got the version number
> wrong in my previous mail -- and that should also be 2.6.12-rc2 not
> 2.6.11-rc2) speeds up resume to the original speed, but suspend is still
> ridiculously slow. Time to narrow things down again, I presume...
>
> > > Also, with 2.6.12-rc2-mm1, this computer happens to hit the bug where
> > > all the printk timestamps are 0000000.0000000 (don't take the # of
> > > digits too literally). Probably unrelated, but I may as well mention it.
> > > (System is an Athlon XP 2200+ with SiS chipset. I can't remember which
> > > model of SiS chipset.)
> >
> > Yes, sorry. Reverting
> > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/broken-out/sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
> > will fix that one.
Reverting
sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
fixed both the printk timestamps and the slow suspend. And it also fixed
a **major** interactivity problem (running kernel compiles made X almost
unusably slow) which I discovered since sending the previous e-mail. So,
something about this patch is seriously evil.
-Barry K. Nathan <[email protected]>
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>
> - x86 NMI handling seems to be bust in 2.6.12-rc2. Try using
> `nmi_watchdog=0' if you experience weird crashes.
>
> - The possible kernel-timer related hangs might possibly be fixed. We
> haven't heard yet.
>
> - Nobody said anything about the PM resume and DRI behaviour in
> 2.6.12-rc1-mm4. So it's all perfect now?
>
> - Various fixes and updates. Nothing earth-shattering.
>
Hi,
-> compiling 2.6.12-rc2-mm1 on amd64 :
arch/x86_64/kernel/nmi.c:116: error: static declaration of
'check_nmi_watchdog' follows non-static declaration
include/asm/apic.h:102: error: previous declaration of
'check_nmi_watchdog' was here
I guess the fix is easy enough :)
-> while I am it, I got a soft lookup on a bi-opteron using
2.6.12-rc1-mm4 (while stressing reiser4 with rsync so I guess it is
reiser4's fault ;)
config at
http://www-fourier.ujf-grenoble.fr/~mmarcha/config-2.6.12-rc1-mm4.gz
I also got some "flushing like mad" warning messages from reiser4 (which
are safe apparently).
BUG: soft lockup detected on CPU#0!
Modules linked in: ipv6 parport_pc parport eth1394 ehci_hcd uhci_hcd
ohci1394 ieee1394 ohci_hcd usbcore snd_intel8x0 snd_ac97_codec snd_pcm
snd_timer snd snd_page_alloc i2c_amd756 i2c_amd8111 i2c_isa w83781d
i2c_sensor i2c_core e1000
Pid: 25291, comm: pdflush Not tainted 2.6.12-rc1-mm4
RIP: 0010:[<ffffffff8021f7de>] <ffffffff8021f7de>{protect_extent_nodes+382}
RSP: 0018:ffff81007df45678 EFLAGS: 00000202
RAX: ffff810015c7c5e0 RBX: ffff81007c609000 RCX: ffff81001074ba60
RDX: ffff81001074b220 RSI: ffff81001074b1c0 RDI: ffff81001074b210
RBP: 0000002000000000 R08: ffff81007df458a0 R09: ffff810044068e14
R10: 000000000000001c R11: ffffffff802119a0 R12: 00007fe07df455e0
R13: ffff81007c609004 R14: ffff81007df4565c R15: 00007fe000000001
FS: 00002aaaaadfeae0(0000) GS:ffffffff806e7840(0000) knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00002aaaaaac2000 CR3: 000000009bc83000 CR4: 00000000000006e0
Call Trace:<ffffffff8021f7da>{protect_extent_nodes+378}
<ffffffff8021c00e>{extent_size+30}
<ffffffff801f5df9>{txnh_get_atom+41}
<ffffffff8021ffd2>{alloc_extent+562}
<ffffffff8020a0bc>{plugin_by_unsafe_id+28}
<ffffffff80220bd1>{item_length_by_coord+17}
<ffffffff801f8a4f>{handle_pos_on_twig+351}
<ffffffff801fabc6>{flush_current_atom+2022}
<ffffffff801f7aca>{flush_some_atom+458}
<ffffffff801a2993>{generic_sync_sb_inodes+723}
<ffffffff8014cc50>{keventd_create_kthread+0}
<ffffffff80203b85>{reiser4_sync_inodes+229}
<ffffffff801a2bd9>{writeback_inodes+137}
<ffffffff8016012c>{background_writeout+124}
<ffffffff80160c10>{pdflush+0} <ffffffff80160d4c>{pdflush+316}
<ffffffff801600b0>{background_writeout+0}
<ffffffff8014cec9>{kthread+217}
<ffffffff80133160>{schedule_tail+64} <ffffffff8010f59b>{child_rip+8}
<ffffffff8014cc50>{keventd_create_kthread+0}
<ffffffff8014cdf0>{kthread+0}
<ffffffff8010f593>{child_rip+0}
Cheers,
Mik
Hi Andrew,
Le Tuesday 05 April 2005 09:45, Andrew Morton a ?crit?:
> Brice Goglin <[email protected]> wrote:
> > Andrew Morton a ?crit :
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.
> > >12-rc2/2.6.12-rc2-mm1/
> >
> > Hi Andrew,
> >
> > printk timing seems broken.
> > It always shows [ 0.000000] on my Compaq Evo N600c.
>
> What sort of CPU does that thing have? Please share the /proc/cpuinfo
> output.
i can reproduce this "[ 0.000000]"-bug with a Thinkpad A31p with a P4M:
cpu family : 15
model : 2
model name : Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz
stepping : 7
cpu MHz : 1998.447
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
> Does reverting
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc
>2/2.6.12-rc2-mm1/broken-out/sched-x86-sched_clock-to-use-tsc-on-config_h
>pet-or-config_numa-systems.patch fix it?
for me too - yes
strange, because the cpu supports tsc as the flags indicate in the cpuinfo
i posted. hopefully this mystery is no more, soon ;-)
best regards,
Damir
--
Don't confuse things that need action with those that take care of
themselves.
On Thu, Apr 07, 2005 at 03:11:12AM +1000, Nick Piggin wrote:
> Using the attached patch, a puny dual PIII-650 with ~400MB RAM swapped
> itself to death after 20000 infinite loop tasks had been pinned to one
> of the CPUs. See how you go.
Its goes well beyond the initial 7000 number I mentioned. Thanks.
One side-effect of this patch is: for example we have only two processes
running on a cpu and both are pinned to that cpu. If someone comes and
changes the affinity of one of these processes to all cpu's in the system,
then it might take MAX_PINNED_INTERVAL before this process moves to an idle cpu.
thanks,
suresh
On Thu, 2005-04-07 at 18:08 -0700, Siddha, Suresh B wrote:
> On Thu, Apr 07, 2005 at 03:11:12AM +1000, Nick Piggin wrote:
> > Using the attached patch, a puny dual PIII-650 with ~400MB RAM swapped
> > itself to death after 20000 infinite loop tasks had been pinned to one
> > of the CPUs. See how you go.
>
> Its goes well beyond the initial 7000 number I mentioned. Thanks.
>
OK, good thanks for testing that. I'll send it to Andrew.
> One side-effect of this patch is: for example we have only two processes
> running on a cpu and both are pinned to that cpu. If someone comes and
> changes the affinity of one of these processes to all cpu's in the system,
> then it might take MAX_PINNED_INTERVAL before this process moves to an idle cpu.
>
Yeah, that is true. OTOH it is a bit of a special case, and our
multiprocessor scheduling in general practically shuts down when
we have a situation with a single queue with a lot of pinned tasks.
What did I have for MAX_PINNED_INTERVAL? ~1second. I guess that could
come down a bit - maybe 1/4 or 1/2 a second? I think it is a "good
enough for now" kind of situation.
--
SUSE Labs, Novell Inc.
Hi!
> > > Ok, I've narrowed the problem down to one patch. In 2.6.11-mm3, the
> > > problem goes away if I remove this patch:
> > > swsusp-enable-resume-from-initrd.patch
> >
> > That really helps, thanks.
>
> You're welcome.
>
> > The patch looks fairly innocent. I'll give up on this and cc the
> > developers.
>
> Yeah, it *seemed* innocent enough -- that's why I had to do a binary
> search on the 2.6.11-mm3 "series" file in order to find it as the
> culprit...
Do you have XFS compiled in, by chance?
You are not actually resuming from initrd, right?
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
On Thu, Apr 07, 2005 at 09:14:19AM +0200, Mickael Marchand wrote:
>...
> -> compiling 2.6.12-rc2-mm1 on amd64 :
>
> arch/x86_64/kernel/nmi.c:116: error: static declaration of
> 'check_nmi_watchdog' follows non-static declaration
> include/asm/apic.h:102: error: previous declaration of
> 'check_nmi_watchdog' was here
Is this with gcc 4.0?
> I guess the fix is easy enough :)
>...
Yup, fix below.
> Cheers,
> Mik
cu
Adrian
<-- snip -->
This patch kills an obsolete check_nmi_watchdog prototype
(check_nmi_watchdog is now static) found by
Mickael Marchand <[email protected]>.
Signed-off-by: Adrian Bunk <[email protected]>
--- linux-2.6.12-rc2-mm1-full/include/asm-x86_64/apic.h.old 2005-04-08 20:12:01.000000000 +0200
+++ linux-2.6.12-rc2-mm1-full/include/asm-x86_64/apic.h 2005-04-08 20:12:11.000000000 +0200
@@ -99,7 +99,6 @@
extern void enable_APIC_timer(void);
extern void clustered_apic_check(void);
-extern int check_nmi_watchdog(void);
extern void nmi_watchdog_default(void);
extern int setup_nmi_watchdog(char *);
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Adrian Bunk a ?crit :
> On Thu, Apr 07, 2005 at 09:14:19AM +0200, Mickael Marchand wrote:
>
>>...
>>-> compiling 2.6.12-rc2-mm1 on amd64 :
>>
>>arch/x86_64/kernel/nmi.c:116: error: static declaration of
>>'check_nmi_watchdog' follows non-static declaration
>>include/asm/apic.h:102: error: previous declaration of
>>'check_nmi_watchdog' was here
>
>
> Is this with gcc 4.0?
yes :)
>
>
>>I guess the fix is easy enough :)
>>...
>
>
> Yup, fix below.
yes, I realize that I should just have just posted it.
thanks for doing it.
Cheers,
Mik
>
>
>>Cheers,
>>Mik
>
>
> cu
> Adrian
>
>
> <-- snip -->
>
>
> This patch kills an obsolete check_nmi_watchdog prototype
> (check_nmi_watchdog is now static) found by
> Mickael Marchand <[email protected]>.
>
> Signed-off-by: Adrian Bunk <[email protected]>
>
> --- linux-2.6.12-rc2-mm1-full/include/asm-x86_64/apic.h.old 2005-04-08 20:12:01.000000000 +0200
> +++ linux-2.6.12-rc2-mm1-full/include/asm-x86_64/apic.h 2005-04-08 20:12:11.000000000 +0200
> @@ -99,7 +99,6 @@
> extern void enable_APIC_timer(void);
> extern void clustered_apic_check(void);
>
> -extern int check_nmi_watchdog(void);
> extern void nmi_watchdog_default(void);
> extern int setup_nmi_watchdog(char *);
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCVsubyOYzc4nQ8j0RAooBAJ9wnRNrhAVmRM6VUuqLY7Bms/uxTgCgml3R
OezYa56tE0cw6GBn0BYO2Qo=
=aK0h
-----END PGP SIGNATURE-----
(Sorry I took so long to respond. I was busy with tons of stuff
offline...)
On Fri, Apr 08, 2005 at 12:33:27PM +0200, Pavel Machek wrote:
> Do you have XFS compiled in, by chance?
Yes.
> You are not actually resuming from initrd, right?
That is correct.
-Barry K. Nathan <[email protected]>
Hi!
> (Sorry I took so long to respond. I was busy with tons of stuff
> offline...)
>
> On Fri, Apr 08, 2005 at 12:33:27PM +0200, Pavel Machek wrote:
> > Do you have XFS compiled in, by chance?
>
> Yes.
Can you try without XFS?
I do not why it interferes, but I've seen that before on suse
kernels...
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
On Sun, Apr 10, 2005 at 11:27:47PM +0200, Pavel Machek wrote:
> Can you try without XFS?
No, XFS is my root filesystem. :( (Now that I think about it, would
modularizing XFS and using an initrd be OK?)
I'll see if I can reproduce this on one of my test boxes. I'll *try* to
get to it later today, but it's possible that I won't be able to get to
it until next Friday or Saturday.
> I do not why it interferes, but I've seen that before on suse
> kernels...
Have you seen it without the resume-from-initrd patch too, or only with
that patch?
-Barry K. Nathan <[email protected]>
Hi!
> > Can you try without XFS?
>
> No, XFS is my root filesystem. :( (Now that I think about it, would
> modularizing XFS and using an initrd be OK?)
Yes, loading xfs from initrd should help. [At least it did during
suse9.3 testing.]
> I'll see if I can reproduce this on one of my test boxes. I'll *try* to
> get to it later today, but it's possible that I won't be able to get to
> it until next Friday or Saturday.
>
> > I do not why it interferes, but I've seen that before on suse
> > kernels...
>
> Have you seen it without the resume-from-initrd patch too, or only with
> that patch?
Only with resume-from-initrd.
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
On Mon, Apr 11, 2005 at 01:00:53AM +0200, Pavel Machek wrote:
> > No, XFS is my root filesystem. :( (Now that I think about it, would
> > modularizing XFS and using an initrd be OK?)
>
> Yes, loading xfs from initrd should help. [At least it did during
> suse9.3 testing.]
Once I modularized xfs and switched to using an initrd, the problem
disappeared.
I just noticed a difference between the kernel messages with XFS
built-in and with it modularized. I'm having trouble putting my finger
on it; it seems like the screen gets cleared at some point during
resume, and with XFS built-in, it starts reading the data from swap
*after* the screen gets cleared. In contrast, if the enable-initrd patch
is removed or XFS is modularized, it reads in from swap *before* the
screen gets cleared. Or something like that.
I'll see if I can get anything more detailed & useful with a serial
console... Failing that, I'll try a camcorder or digital camera and
transcribe from that.
-Barry K. Nathan <[email protected]>
Barry K. Nathan wrote:
> On Sun, Apr 10, 2005 at 11:27:47PM +0200, Pavel Machek wrote:
>> Can you try without XFS?
>
> No, XFS is my root filesystem. :( (Now that I think about it, would
> modularizing XFS and using an initrd be OK?)
Yes, although it is not totally trivial.
> I'll see if I can reproduce this on one of my test boxes. I'll *try* to
> get to it later today, but it's possible that I won't be able to get to
> it until next Friday or Saturday.
>
>> I do not why it interferes, but I've seen that before on suse
>> kernels...
>
> Have you seen it without the resume-from-initrd patch too, or only with
> that patch?
We have seen it in 9.3-beta, exact scenario was:
- root fs is XFS, ide driver is modular
=> xfs module and ide-controller module is in initramfs
=> first all modules were loaded (device driver + fs)
=> resume was triggered, resume was _really_ slow.
we worked around it in the initramfs by first loading device drivers,
triggering resume, then loading the fs modules and continuing boot.
In the resume case, we'd never reach the "load fs modules" part and
generally it seems a good idea (if the drivers are modular) to keep the
setup before resume as minimalistic as possible.
We never tried with XFS compiled in. It seems we can no longer hide from
fixing XFS ;-)
Best regards,
Stefan
Hi!
> > > No, XFS is my root filesystem. :( (Now that I think about it, would
> > > modularizing XFS and using an initrd be OK?)
> >
> > Yes, loading xfs from initrd should help. [At least it did during
> > suse9.3 testing.]
>
> Once I modularized xfs and switched to using an initrd, the problem
> disappeared.
I reproduced it locally. Problem is that xfsbufd goes refrigerated,
but someone still tries to wake it up *very* often. Probably something
else in xfs needs refrigerating, too, but I'm not a XFS wizard...
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
On Mon, Apr 11, 2005 at 12:57:59PM +0200, Pavel Machek wrote:
> Hi!
>
> > > > No, XFS is my root filesystem. :( (Now that I think about it, would
> > > > modularizing XFS and using an initrd be OK?)
> > >
> > > Yes, loading xfs from initrd should help. [At least it did during
> > > suse9.3 testing.]
> >
> > Once I modularized xfs and switched to using an initrd, the problem
> > disappeared.
>
> I reproduced it locally. Problem is that xfsbufd goes refrigerated,
> but someone still tries to wake it up *very* often. Probably something
> else in xfs needs refrigerating, too, but I'm not a XFS wizard...
Thanks Pavel - I've been reading the thread from the other side
of the fence, not understanding the swsusp side of things. :)
There are two ways the xfsbufd thread will wake up - either by its
timer going off (for it to flush delayed write metadata buffers)
or by being explicitly woken up when we're low on memory (in which
case it also flushes out dirty metadata, such that pages can be
cleaned and made available to the system).
Since the refrigerator() call is in place in the main xfsbufd loop,
I suspect we're hitting that second case here, where a low memory
situation is resulting in someone attempting to wakeup xfsbufd --
I'm not sure if this is the right way to check if we're in that
state, but does this patch help? (it would certainly prevent the
spurious wakeups, but only if the caller has PF_FREEZE set - will
that be the case here?)
cheers.
--
Nathan
--- fs/xfs/linux-2.6/xfs_buf.c.orig 2005-04-12 09:00:26.375351560 +1000
+++ fs/xfs/linux-2.6/xfs_buf.c 2005-04-12 08:59:38.973557728 +1000
@@ -1753,6 +1753,8 @@ pagebuf_daemon_wakeup(
int priority,
unsigned int mask)
{
+ if (current->flags & PF_FREEZE)
+ return 0;
force_flush = 1;
barrier();
wake_up_process(pagebuf_daemon_task);
Hi!
> > > > > No, XFS is my root filesystem. :( (Now that I think about it, would
> > > > > modularizing XFS and using an initrd be OK?)
> > > >
> > > > Yes, loading xfs from initrd should help. [At least it did during
> > > > suse9.3 testing.]
> > >
> > > Once I modularized xfs and switched to using an initrd, the problem
> > > disappeared.
> >
> > I reproduced it locally. Problem is that xfsbufd goes refrigerated,
> > but someone still tries to wake it up *very* often. Probably something
> > else in xfs needs refrigerating, too, but I'm not a XFS wizard...
>
> Thanks Pavel - I've been reading the thread from the other side
> of the fence, not understanding the swsusp side of things. :)
>
> There are two ways the xfsbufd thread will wake up - either by its
> timer going off (for it to flush delayed write metadata buffers)
> or by being explicitly woken up when we're low on memory (in which
> case it also flushes out dirty metadata, such that pages can be
> cleaned and made available to the system).
>
> Since the refrigerator() call is in place in the main xfsbufd loop,
> I suspect we're hitting that second case here, where a low memory
> situation is resulting in someone attempting to wakeup xfsbufd --
> I'm not sure if this is the right way to check if we're in that
> state, but does this patch help? (it would certainly prevent the
> spurious wakeups, but only if the caller has PF_FREEZE set - will
> that be the case here?)
I should take some sleep now, so I can't test the patch, but I don't
think it will help. If someone has PF_FREEZE set, he should be in
refrigerator.
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
On Tue, Apr 12, 2005 at 01:51:10AM +0200, Pavel Machek wrote:
> I should take some sleep now, so I can't test the patch, but I don't
> think it will help. If someone has PF_FREEZE set, he should be in
> refrigerator.
OK, so if that doesn't help, here's an alternate approach - this
lets xfsbufd track when its entering the refrigerator(), so that
other callers know that attempts to wake it are futile.
cheers.
--
Nathan
--- fs/xfs/linux-2.6/xfs_buf.c.orig 2005-04-12 09:00:26.375351560 +1000
+++ fs/xfs/linux-2.6/xfs_buf.c 2005-04-12 10:14:27.468202824 +1000
@@ -1746,13 +1746,15 @@ STATIC DECLARE_COMPLETION(pagebuf_daemon
STATIC struct task_struct *pagebuf_daemon_task;
STATIC int pagebuf_daemon_active;
STATIC int force_flush;
-
+STATIC int force_sleep;
STATIC int
pagebuf_daemon_wakeup(
int priority,
unsigned int mask)
{
+ if (force_sleep)
+ return 0;
force_flush = 1;
barrier();
wake_up_process(pagebuf_daemon_task);
@@ -1778,7 +1780,12 @@ pagebuf_daemon(
INIT_LIST_HEAD(&tmp);
do {
- try_to_freeze(PF_FREEZE);
+ if (unlikely(current->flags & PF_FREEZE)) {
+ force_sleep = 1;
+ refrigerator(PF_FREEZE);
+ } else {
+ force_sleep = 0;
+ }
set_current_state(TASK_INTERRUPTIBLE);
schedule_timeout((xfs_buf_timer_centisecs * HZ) / 100);
On Tue, Apr 12, 2005 at 01:04:25PM +0200, Pavel Machek wrote:
> > OK, so if that doesn't help, here's an alternate approach - this
> > lets xfsbufd track when its entering the refrigerator(), so that
> > other callers know that attempts to wake it are futile.
>
> Thanks, this patch helped.
I can confirm, the 2nd patch worked and the 1st one didn't. (This is
against 2.6.12-rc2-mm1 with sched-x86-patch-name-is-way-too-long.patch
backed out. ;) )
-Barry K. Nathan <[email protected]>
Hi,
On Tuesday, 12 of April 2005 01:51, Pavel Machek wrote:
]--snip--[
> > Since the refrigerator() call is in place in the main xfsbufd loop,
> > I suspect we're hitting that second case here, where a low memory
> > situation is resulting in someone attempting to wakeup xfsbufd --
> > I'm not sure if this is the right way to check if we're in that
> > state, but does this patch help? (it would certainly prevent the
> > spurious wakeups, but only if the caller has PF_FREEZE set - will
> > that be the case here?)
>
> I should take some sleep now, so I can't test the patch, but I don't
> think it will help. If someone has PF_FREEZE set, he should be in
> refrigerator.
Or he was in TASK_UNINTERRUPTIBLE while processes were being frozen. :-)
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
Hi!
> > I should take some sleep now, so I can't test the patch, but I don't
> > think it will help. If someone has PF_FREEZE set, he should be in
> > refrigerator.
>
> OK, so if that doesn't help, here's an alternate approach - this
> lets xfsbufd track when its entering the refrigerator(), so that
> other callers know that attempts to wake it are futile.
Thanks, this patch helped.
Pavel
--
Boycott Kodak -- for their patent abuse against Java.