ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/
- Many new driver updates and architecture updates
- New CPU scheduler policy: SCHED_BATCH.
- New version of the hrtimers code.
Changes since 2.6.15-rc5-mm1:
linus.patch
git-acpi.patch
git-alsa.patch
git-arm.patch
git-blktrace.patch
git-block.patch
git-cfq.patch
git-cifs.patch
git-cpufreq.patch
git-drm.patch
git-audit.patch
git-ia64.patch
git-ieee1394.patch
git-infiniband.patch
git-kbuild.patch
git-libata-all.patch
git-mmc.patch
git-netdev-all.patch
git-net.patch
git-nfs.patch
git-ntfs.patch
git-ocfs2.patch
git-powerpc.patch
git-sym2.patch
git-pcmcia.patch
git-scsi-rc-fixes.patch
git-sas-jg.patch
git-sparc64.patch
git-watchdog.patch
git-xfs.patch
git-cryptodev.patch
Subsystem trees
-sound-pci-au88x0-remove-unneeded-call-to-pci_dma_supported.patch
-ieee1394-write-broadcast_channel-only-to-select-nodes.patch
-git-libata-all-stat_sil-build-fix.patch
-arch-replace-pci_module_init-with-pci_register_driver.patch
-drivers-block-replace-pci_module_init-with-pci_register_driver.patch
-drivers-net-replace-pci_module_init-with-pci_register_driver.patch
-drivers-scsi-replace-pci_module_init-with-pci_register_driver.patch
-drivers-rest-replace-pci_module_init-with-pci_register_driver.patch
-git-pcmcia-dev_to_instance-fix.patch
-usb-storage-add-debug-entry-for-report-luns.patch
-mpcore_wdtc-bogus-fpos-check.patch
-ppc32-remove-unused-variables.patch
-add-new-quirk-for-devices-with-mute-leds-and-separate-headphone-volume.patch
-aoe-type-cleanups.patch
-aoe-skb_check-cleanup.patch
-ide-modalias-support-for-autoloading-of-ide-cd-ide-disk.patch
-net-make-function-pointer-argument-parseable-by-kernel-doc.patch
-pci-schedule-removal-of-pci_module_init-was-re-patch.patch
Merged
-pfnmap-fix-2615-rc3-driver-breakage.patch
Dropped
+fix-bug-in-rcu-torture-test.patch
+fix-rcu-race-in-access-of-nohz_cpu_mask.patch
+fix-rcu-race-in-access-of-nohz_cpu_mask-comment.patch
RCU fixes
+fix-listxattr-for-generic-security-attributes.patch
xattr fix
+add-getnstimestamp-function.patch
+add-timestamp-field-to-process-events.patch
Process connector feature
+rcu-add-hlist_replace_rcu.patch
+kprobes-fix-race-in-aggregate-kprobe-registration.patch
kprobes fix
+cciss-double-put_disk.patch
cciss driver fix
+add-two-inotify_add_watch-flags.patch
inotify feature
+um-fix-compile-error-for-tt.patch
UML fix
+powerpc-fix-a-huge-page-bug.patch
+powerpc-remove-debug-code-in-hash-path.patch
+fix-windfarm-model-id-table.patch
powerpc fixes
+mm-go-back-to-checking-pageanon-in-vm_normal_page.patch
Fix recent MM changes for oddball drivers
+mips-setup_zero_pages-count-1.patch
MIPS fix
+v4l-dvb-3086a-whitespaces-cleanups-part-1.patch
+v4l-dvb-3086b-whitespaces-cleanups-part-2.patch
+v4l-dvb-3086c-whitespaces-cleanups-part-3.patch
+v4l-dvb-3086c-whitespaces-cleanups-part-4.patch
+v4l-dvb-3135-fix-tuner-init-for-pinnacle-pctv-stereo.patch
+v4l-dvb-3113-convert-em28xx-to-use-vm_insert_page.patch
+v4l-dvb-3151-i2c-id-renamed-to-i2c_driverid_infrared.patch
v4l/dvb fixes
+powerpc-set-cache-info-defaults.patch
+powerpc-fix-slb-flushing-path-in-hugepage.patch
+powerpc-add-missing-icache-flushes-for-hugepages.patch
powerpc fixes
+sparc-atomic_clear_mask-build-fix.patch
+sparc32-block-needed-in-final-image-link-build-fix.patch
sparc32 build fixes
+ipmi-fix-panic-generator-id.patch
IPMI driver fix
+kprobes-no-probes-on-critical-path.patch
+kprobes-no-probes-on-critical-path-fix.patch
+kprobes-increment-kprobe-missed-count-for-multiprobes.patch
kprobes fixes
+broken-cast-in-parport_pc.patch
Build fix
+input-fix-ucb1x00-ts-breakage-after-conversion-to-dynamic.patch
Input driver fix
+fix-kconfig-of-dma32-for-ia64.patch
ia64 Kconfig fix
+ppc32-set-smp_tb_synchronized-on-up-with-smp-kernel.patch
ppc32 fix
+fix-in-__alloc_bootmem_core-when-there-is-no-free-page-in-first-nodes-memory.patch
bootmem initialisation fix
+x86_64-numa-bug-correction-in-populate_memnodemap.patch
x86_64 numa init fix
+acpi-fix-sleeping-whilst-atomic-warnings-on-resume.patch
ACPI fix
+2.6-sony_acpi4.patch
ACPI driver for Sony laptops
+git-alsa-sparc64-fix.patch
Fix git-alsa.patch
+gregkh-driver-ide-modalias-support-for-autoloading-of-ide-cd-ide-disk.patch
+gregkh-driver-aoe-type-cleanups.patch-added-to-mm-tree.patch
+gregkh-driver-aoe-skb_check-cleanup.patch
driver tree updates
+gregkh-i2c-i2c-mv64xxx-compilation-error-fix.patch
-gregkh-i2c-i2c-parport-barco-ltp-dvi.patch
+gregkh-i2c-i2c-parport-barco-lpt-dvi.patch
-gregkh-i2c-i2c-device-id-lm75.patch
+gregkh-i2c-i2c-driver-owner-cleanup-01.patch
+gregkh-i2c-i2c-driver-owner-cleanup-02.patch
+gregkh-i2c-i2c-driver-owner-cleanup-03.patch
+gregkh-i2c-w1-change-the-type-unsigned-long-member-of-struct-w1_bus_master-to-void.patch
+gregkh-i2c-w1-move-w1-bus-master-code-into-w1-masters-and-move-w1-slave-code-into-w1-slaves.patch
+gregkh-i2c-w1-add-the-ds2482-i2c-to-w1-bridge-driver.patch
+gregkh-i2c-i2c-device-id-lm75.patch
I2C tree fixes
+drivers-input-misc-added-acer-travelmate-240-support-to-the-wistron-button-interface.patch
Input driver update
+git-net-revert-af_unix-changes.patch
+git-net-selinux-xfrm-build-fix.patch
Fix things in git-net.patch
+spufs-build-fix.patch
Fix git-powerpc.patch
+gregkh-pci-x86-pci-domain-support-a-humble-fix.patch
+gregkh-pci-x86-pci-domain-support-struct-pci_sysdata.patch
+gregkh-pci-x86-pci-domain-support-the-meat.patch
+gregkh-pci-pci-error-recovery-documentation.patch
+gregkh-pci-pci-hotplug-powerpc-remove-duplicated-code.patch
+gregkh-pci-pci-hotplug-powerpc-more-removal-of-duplicated-code.patch
+gregkh-pci-arch-replace-pci_module_init-with-pci_register_driver.patch
+gregkh-pci-drivers-block-replace-pci_module_init-with-pci_register_driver.patch
+gregkh-pci-drivers-net-replace-pci_module_init-with-pci_register_driver.patch
+gregkh-pci-drivers-scsi-replace-pci_module_init-with-pci_register_driver.patch
+gregkh-pci-drivers-rest-replace-pci_module_init-with-pci_register_driver.patch
+gregkh-pci-drivers-sound-oss-replace-pci_module_init-with-pci_register_driver.patch
+gregkh-pci-pci-schedule-removal-of-pci_module_init.patch
+gregkh-pci-shpchp-implement-get_address-callback.patch
+gregkh-pci-pci-quirk-1k-i-o-space-granularity-on-intel-p64h2.patch
+gregkh-pci-pciehp-handle-sticky-power-fault-status.patch
+gregkh-pci-pciehp-allow-bridged-card-hotplug.patch
+gregkh-pci-pci-use-bus-numbers-sparsely-if-necessary.patch
PCI tree updates
+gregkh-usb-uhci-add-missing-memory-barriers.patch
-gregkh-usb-usb-gotemp.patch
+gregkh-usb-uhci-edit-some-comments.patch
+gregkh-usb-usb-let-usbmon-collect-less-garbage.patch
+gregkh-usb-usb-storage-make-onetouch-pm-aware.patch
+gregkh-usb-usb-storage-cleanups-of-sddr09.patch
+gregkh-usb-usb-storage-sddr09-cleanups.patch
+gregkh-usb-usb-storage-more-sddr09-cleanups.patch
+gregkh-usb-usb-storage-add-alauda-support.patch
+gregkh-usb-usb-storage-update-maintainers.patch
+gregkh-usb-usb-storage-add-debug-entry-for-report-luns.patch
+gregkh-usb-usb-gotemp.patch
USB tree updates
+usb-support-for-posiflex-pp-7000-retail-printer-for-ftdi_sio-driver.patch
USB device support
+x86_64-dont-save-eflags-in-x86-64-switch_to.patch
+x86_64-iommu-newline.patch
+x86_64-remove-pci-bus.patch
+x86_64-dmi.patch
+x86_64-fxsave-prefix.patch
x86_64 tree updates
+x86_64-dmi-fix.patch
Fix it.
-preserve-irq-status-in-release_pages-__pagevec_lru_add.patch
Unneeded
+add-schedule_on_each_cpu.patch
Used in updated swap migration patches
+swap-migration-v5-mpol_mf_move-interface-update-vma_migratable.patch
Fix swap-migration-v5-mpol_mf_move-interface.patch
+kill-last-zone_reclaim-bits-fix.patch
Fix kill-last-zone_reclaim-bits.patch
+make-high-and-batch-sizes-of-per_cpu_pagelists-configurable.patch
+make-high-and-batch-sizes-of-per_cpu_pagelists-configurable-fix.patch
+make-high-and-batch-sizes-of-per_cpu_pagelists-configurable-fix-fix.patch
Make the per-cpu-pagews batchsize tunable
+consolidate-lru_add_drain-and-lru_drain_cache.patch
+simplify-build_zonelists_node-by-removing-the-case.patch
+move-determination-of-policy_zone-into-page-allocator.patch
mm cleanups
+pcnet32-use-mac-address-from-prom-also-on-powerpc.patch
Net driver fix
+selinux-array_size-cleanups.patch
+selinux-more-array_size-cleanups.patch
SELinux cleanups
+macintosh-mangle-caps-lock-events-on-adb-keyboards.patch
Dink with the ADB driver. Probably not mergeable.
-i386-support-for-the-geode-cs5535-companion-chip.patch
-i386-support-for-the-geode-cs5535-companion-chip-tidy.patch
+i386-cs5535-chip-support-cpu.patch
+i386-cs5535-chip-support-gpio.patch
+i386-cs5535-chip-support-smbus.patch
Updated. Still need work.
-cpu-frequency-display-in-proc-cpuinfo.patch
Dropped.
+arch-i386-kernel-cpuidc-unused-variable.patch
Warning fix
+change-maxaligned_in_smp-alignemnt-macros-to-internodealigned_in_smp-macros.patch
+kill-l1_cache_shift_max.patch
+kill-l1_cache_shift_max-fix.patch
+kill-l1_cache_shift_max-fix-fix.patch
Fiddle with the max cache alignment
+x86_64-fix-delay-resolution.patch
Fix x86_64 delay accuracy
+alpha-convert-to-generic-irq-framework-generic-part.patch
+alpha-convert-to-generic-irq-framework-alpha-part.patch
Use generic IRQ code on alpha
+reconfigure-msi-registers-after-resume.patch
+swsusp-limit-image-size.patch
PM updates
+m32r-trivial-fix-to-remove-unused-instructions.patch
+m32r-support-m32104ut-target-platform.patch
+m32r-update-syscall-macros-for-mmu-less.patch
+m32r-update-_port2addr-to-use.patch
+m32r-fix-m32104-cache-flushing-routines.patch
+m32r-remove-unnecessary-icu_data_t.patch
m32r updates
+s390-cputime_t-fixes.patch
+s390-re-activated-path-detection.patch
+s390-move-s390_root_dev_-out-of-the-cio-layer.patch
+s390-biodasdprrd-ioctl-return-code.patch
+s390-dasd-failfast-support.patch
+s390-add-oprofile-callgraph-support.patch
+s390-in-kernel-crypto-rename.patch
+s390-sha256-support.patch
+s390-aes-support.patch
+s390-in-kernel-crypto-test-vectors.patch
+s390-qdio-v=v-pass-through.patch
+s390-introduce-struct-subchannel_id.patch
+s390-introduce-for_each_subchannel.patch
+s390-introduce-struct-channel_subsystem.patch
+s390-convert-proc-cio_ignore.patch
+s390-multiple-subchannel-sets-support.patch
+s390-add-support-for-cex2a-crypto-cards.patch
s390 updates
+cpuset-remove-marker_pid-documentation.patch
+cpuset-minor-spacing-initializer-fixes.patch
+cpuset-update_nodemask-code-reformat.patch
+cpuset-fork-hook-fix.patch
+cpuset-combine-refresh_mems-and-update_mems.patch
+cpuset-implement-cpuset_mems_allowed.patch
+cpuset-numa_policy_rebind-cleanup.patch
+cpuset-number_of_cpusets-optimization.patch
+cpuset-rebind-vma-mempolicies-fix.patch
+cpuset-rebind-vma-mempolicies-fix-fix.patch
+cpuset-rebind-vma-mempolicies-fix-tweaks.patch
+cpuset-migrate-all-tasks-in-cpuset-at-once.patch
cpuset updates
+extend-rcu-torture-module-to-test-tickless-idle-cpu.patch
+extend-rcu-torture-module-to-test-tickless-idle-cpu-fixes.patch
RCU updates
+update-to-the-initramfs-docs.patch
Documentation
+fadvise-return-espipe-on-fifo-pipe.patch
fadvise fix
+untangle-smph-vs-thread_info.patch
Header cleanup
+dont-attempt-to-power-off-if-power-off-is-not-implemented.patch
poweroff fix
+tpmdd-remove-global-event-log.patch
+tpmdd-remove-global-event-log-tidy.patch
TPM driver update
+cciss-adds-msi-and-msi-x-support.patch
+cciss-adds-msi-and-msi-x-support-fix.patch
CCISS update
+support-for-preadv-pwritev.patch
+support-for-preadv-pwritev-fix.patch
preadv() and pwritev() syscalls.
+fork-fix-race-in-setting-childs-pgrp-and-tty.patch
race fix
+block-stattxt.patch
Documentation
+reduce-nr-of-ptr-derefs-in-fs-jffs2-summaryc.patch
Microoptimisation
-ktimers-move-div_long_long_rem-out-of-jiffiesh.patch
-ktimers-remove-duplicate-div_long_long_rem-implementation.patch
-ktimers-deinline-mktime-and-set_normalized_timespec.patch
-ktimers-clean-up-mktime-and-add-const-modifiers.patch
-ktimers-export-deinlined-mktime.patch
-ktimers-remove-unused-clock-constants.patch
-ktimers-cleanup-clock-constants-coding-style.patch
-ktimers-coding-style-and-whitespace-cleanup-timeh.patch
-ktimers-make-clock-selectors-in-posix-timers-const.patch
-ktimers-coding-style-and-white-space-cleanup-posix-timerh.patch
-ktimers-create-timespec_valid-macro.patch
-ktimers-check-user-space-timespec-in-do_sys_settimeofday.patch
-ktimers-introduce-nsec_t-type-and-conversion-functions.patch
-ktimers-introduce-ktime_t-time-format.patch
-ktimers-ktimer-core-code.patch
-ktimers-ktimer-documentation.patch
-ktimers-switch-itimers-to-ktimer.patch
-ktimers-remove-now-unnecessary-includes.patch
-ktimers-introduce-ktimer_nanosleep-apis.patch
-ktimers-convert-sys_nanosleep-to-ktimer_nanosleep.patch
-ktimers-switch-clock_nanosleep-to-ktimer-nanosleep-api.patch
-ktimers-convert-posix-interval-timers-to-use-ktimers.patch
-ktimers-simplify-ktimers-rearm-code.patch
-ktimers-split-timeout-code-into-kernel-ktimeoutc.patch
-ktimers-create-ktimeouth-and-move-timerh-code-into-it.patch
-ktimers-rename-struct-timer_list-to-struct-ktimeout.patch
-ktimers-convert-timer_list-users-to-ktimeout.patch
-ktimers-convert-ktimeouth-and-create-wrappers.patch
-ktimers-convert-ktimeoutc-to-ktimeout-struct-and-apis.patch
-ktimers-ktimeout-documentation.patch
-ktimers-rename-init_ktimeout-to-ktimeout_init.patch
-ktimers-rename-setup_ktimeout-to-ktimeout_setup.patch
-ktimers-rename-add_ktimeout_on-to-ktimeout_add_on.patch
-ktimers-rename-del_ktimeout-to-ktimeout_del.patch
-ktimers-rename-__mod_ktimeout-to-__mod_ktimeout.patch
-ktimers-rename-mod_ktimeout-to-ktimeout_mod.patch
-ktimers-rename-next_ktimeout_interrupt-to.patch
-ktimers-rename-add_ktimeout-to-ktimeout_add.patch
-ktimers-rename-try_to_del_ktimeout_sync-to.patch
-ktimers-rename-del_ktimeout_sync-to-del_ktimeout_sync.patch
-ktimers-rename-del_singleshot_ktimeout_sync-to.patch
-ktimers-rename-timer_softirq-to-timeout_softirq.patch
-ktimers-ktimeout-code-style-cleanups.patch
-ktimers-ktimeout-code-style-cleanups-fix.patch
+hrtimer-move-div_long_long_rem-out-of-jiffiesh.patch
+hrtimer-move-div_long_long_rem-out-of-jiffiesh-sparc64-fix.patch
+hrtimer-remove-duplicate-div_long_long_rem-implementation.patch
+hrtimer-deinline-mktime-and-set_normalized_timespec.patch
+hrtimer-clean-up-mktime-and-make-arguments-const.patch
+hrtimer-export-deinlined-mktime.patch
+hrtimer-remove-unused-clock-constants.patch
+hrtimer-coding-style-clean-up-of-clock-constants.patch
+hrtimer-coding-style-and-white-space-cleanup.patch
+hrtimer-make-clockid_t-arguments-const.patch
+hrtimer-coding-style-and-white-space-cleanup-2.patch
+hrtimer-create-and-use-timespec_valid-macro.patch
+hrtimer-validate-timespec-of-do_sys_settimeofday.patch
+hrtimer-introduce-nsec_t-type-and-conversion-functions.patch
+hrtimer-introduce-ktime_t-time-format.patch
+hrtimer-hrtimer-core-code.patch
+hrtimer-hrtimer-documentation.patch
+hrtimer-switch-itimers-to-hrtimer.patch
+hrtimer-create-hrtimer-nanosleep-api.patch
+hrtimer-switch-sys_nanosleep-to-hrtimer.patch
+hrtimer-switch-clock_nanosleep-to-hrtimer-nanosleep-api.patch
+hrtimer-convert-posix-timers-completely.patch
+hrtimer-convert-posix-timers-completely-fix.patch
New hrtimer implementation
+v4l-926_2-moves-compat32-functions-from-fs-to-v4l.patch
+v4l-963-explicit-compat_ioctl32-handler-to-em28xx.patch
+v4l-dvb-3120-adds-32-bit-compatibility-for-v4l2.patch
+v4l-0987-added-secam-l-std-on-tda9887-and-common.patch
+v4l-1019-added-basic-support-tv-radio-for.patch
+v4l-1023-added-hauppauge-impactvcb-board.patch
+v4l-0979-added-v4l-support-for-the-nova-s-plus-and.patch
+v4l-0990-enable-ir-support-for-the-nova-s-plus.patch
+v4l-1007-add-support-for-kworld-dvb-s-100.patch
+v4l-0988-tuner-cleanups-by-removing-video-if-from.patch
+v4l-1021-tuner-description-now-follows-the-same.patch
+dvb-2420-makes-integration-of-future-devices-easier.patch
+dvb-2421-fixed-oddities-at-firmware-download.patch
+dvb-2428-fixes-for-the-topuptv-scm-mediaguard-cam.patch
+dvb-2431-fixed-dishnetwork-support-for-nexus-s-rev.patch
+dvb-2432-lnb-power-can-now-be-switched-off-for.patch
+dvb-2440-fixed-mpeg-audio-on-spdif-from-nexus-ca.patch
+dvb-2441-driver-support-for-live-ac3-firmware-=.patch
+dvb-2444-implement-frontend-specific-tuning-and.patch
+dvb-2445-added-demodulator-driver-for-nova-s-plus.patch
+dvb-2446-minor-cleanups.patch
+dvb-2451-add-support-for-kworld-dvb-s-100-based.patch
+dvb-2454-port-code-for-su1278-sh2-tua6100-from.patch
+dvb-2390-adds-a-time-delay-to-ir-remote-button.patch
+v4l-dvb-3062-fix-wrong-tunerh-define-for-tuner-46.patch
+v4l-dvb-3064-some-cleanups-on-msp3400.patch
+v4l-dvb-3065-fix-gcc-402-compile-error-in.patch
+v4l-dvb-3081-added-offset-parameter-for-adjusting.patch
+v4l-dvb-3084-added-a-new-debug-msg-to-help.patch
+v4l-dvb-3086-vfreenull-is-legal.patch
+v4l-dvb-3089-adding-support-for-the-hauppauge.patch
+v4l-dvb-3090-cleanup-check-for-dvb.patch
+v4l-dvb-3092-add-support-for-another-nova-t-pci.patch
+v4l-dvb-3099-fixed-device-controls-for-em28xx-on.patch
+v4l-dvb-3100-fix-compile-error-remove-dead-code.patch
+v4l-dvb-3103-add-vidioc_log_status-to-tuner-corec.patch
+v4l-dvb-3104-msp3400-miscelaneous-fixes.patch
+v4l-dvb-3105-remove-audc_config_pinnacle-horror.patch
+v4l-dvb-3108-tveeprom-cleanup-of-hardcoded-tuner.patch
+v4l-dvb-3112-several-fixes-for-hauppauge-roselyn.patch
+v4l-dvb-3115-add-missing-video_adv_debug-config.patch
+v4l-dvb-3116-tda9887-improvements-better.patch
+v4l-dvb-3117-fix-broken-tv-standard-check.patch
+v4l-dvb-3118-enable-remote-control-on-avertv.patch
+v4l-dvb-3123-include-reorder-to-be-in-sync-with.patch
+v4l-dvb-3123a-remove-uneeded-if-from-v4l-subsystem.patch
+v4l-dvb-3123b-syncs-v4l-subsystem-tree-with-kernel.patch
+v4l-dvb-3129-correct-fe_read_uncorrected_blocks.patch
+v4l-dvb-3130-cx24123-cleanup-timout-handling.patch
+v4l-dvb-3145-syncronizes-some-changes-between-v4l.patch
v4l/dvb updates
+scheduler-cache-hot-autodetect-section-fixes.patch
+scheduler-cache-hot-autodetect-limit-to-affected-cpu-map.patch
+scheduler-cache-hot-autodetect-be-less-verbose.patch
Update scheduler-cache-hot-autodetect.patch
+sched-add-sched_batch-policy.patch
New CPU scheduler policy
+ide-restore-support-for-aec6280m-cards-in-aec62xxc.patch
+via82cxxx-ide-add-vt8251-isa-bridge.patch
IDE updates
+nvidiafb-fix-6xxx-7xxx-cards.patch
+fbcon-add-ability-to-save-restore-graphics-state.patch
+fbdev-pan-display-fixes.patch
+rivafb-trim-rivafb_pan_display.patch
+savagefb-trim-savagefb_pan_display.patch
+vesafb-trim-vesafb_pan_display.patch
+vga16fb-trim-vga16fb_pan_display.patch
+fbcon-avoid-illegal-display-panning.patch
+atyfb-fix-spelling.patch
+atyfb-reduce-verbosity.patch
+atyfb-fix-crtc_fifo_lwm-mask.patch
+atyfb-fix-interlaced-modes.patch
+atyfb-dont-stretch-with-crt.patch
+atyfb-set-ecp-divider.patch
+atyfb-improve-blanking.patch
+atyfb-rage-xl-xc-cleanup.patch
+atyfb-vt-gt-cleanup.patch
+atyfb-lt-lg-cleanup.patch
+nvidiafb-add-support-for-some-pci-e-chipsets.patch
+nvidiafb-add-support-for-some-pci-e-chipsets-fix.patch
+fbdev-fixing-switch-to-kd_text-enhanced-version.patch
+skeletonfb-documentation-update.patch
fbdev updates
+page-owner-tracking-leak-detector-fix.patch
Fix page-owner-tracking-leak-detector.patch
+decrease-number-of-pointer-derefs-in-exitc.patch
+decrease-number-of-pointer-derefs-in-flexcop-fe-tunerc.patch
+decrease-number-of-pointer-derefs-in-nfnetlink_queuec.patch
+decrease-number-of-pointer-derefs-in-nf_conntrack_corec.patch
+decrease-number-of-pointer-derefs-in-multipathc.patch
+decrease-number-of-pointer-derefs-in-connectionc.patch
+decrease-number-of-pointer-derefs-in-jsm_ttyc.patch
Microoptimisations
All 1164 patches:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/patch-list
On 12/11/05, Andrew Morton <[email protected]> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/
>
> - Many new driver updates and architecture updates
>
> - New CPU scheduler policy: SCHED_BATCH.
>
> - New version of the hrtimers code.
>
Fix unused variable warning
Signed-off-by: Benoit Boissinot <[email protected]>
Index: linux/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
===================================================================
--- linux.orig/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
+++ linux/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
@@ -305,10 +305,6 @@ acpi_cpufreq_cpu_init (
unsigned int result = 0;
struct cpuinfo_x86 *c = &cpu_data[policy->cpu];
- union acpi_object arg0 = {ACPI_TYPE_BUFFER};
- u32 arg0_buf[3];
- struct acpi_object_list arg_list = {1, &arg0};
-
dprintk("acpi_cpufreq_cpu_init\n");
data = kzalloc(sizeof(struct cpufreq_acpi_io), GFP_KERNEL);
On 12/11/05, Andrew Morton <[email protected]> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/
>
> - Many new driver updates and architecture updates
>
> - New CPU scheduler policy: SCHED_BATCH.
>
> - New version of the hrtimers code.
>
I have some issues with this kernel (both issue are reproductible on two
different computers):
- i cannot login with xdm, as soon as i login, the X server restarts.
Login with startx works (.xinitrc is a symlink to .xsession)
It works fine with 2.6.15-rc5-mm1.
If you need any log please ask.
- there is a warning when pinging an inexistent ip
(it works fine with 2.6.15-rc5-mm1 too)
casaverde tonfa # ping 192.168.1.42
PING 192.168.1.42 (192.168.1.42) 56(84) bytes of data.
WARNING: kernel is not very fresh, upgrade is recommended.
>From 192.168.42.1: icmp_seq=2 Destination Host Unreachable
from iputils source code (ping.c):
} else {
static int once;
/* Sigh, IP_RECVERR for raw socket
* was broken until 2.4.9. So, we ignore
* the first error and warn on the second.
*/
if (once++ == 1)
fprintf(stderr, "\rWARNING: kernel is not very fresh, upgrade is recommended.\n");
if (once == 1)
return 0;
}
dmesg and config are attached, please ask if you need something else.
regards,
Benoit
It is impossible to resume from disk on x86-64 machines due to the changes
introduced by the x86_64-hpet-overflow patch. The problem is known
(appeared in -mm1), but there's no official fix yet.
The appended patch fixes the issue, although I'm not sure if this is the right
fix.
Signed-off-by: Rafael J. Wysocki <[email protected]>
arch/x86_64/kernel/time.c | 9 +++++++++
1 files changed, 9 insertions(+)
Index: linux-2.6.15-rc5-mm1/arch/x86_64/kernel/time.c
===================================================================
--- linux-2.6.15-rc5-mm1.orig/arch/x86_64/kernel/time.c 2005-12-08 22:57:33.000000000 +0100
+++ linux-2.6.15-rc5-mm1/arch/x86_64/kernel/time.c 2005-12-09 14:37:31.000000000 +0100
@@ -65,6 +65,7 @@ unsigned long hpet_tick;
static int hpet_use_timer;
unsigned long vxtime_hz = PIT_TICK_RATE;
unsigned long long monotonic_base;
+static int vxtime_last_invalid; /* for the interrupt handler */
static int report_lost_ticks; /* command line option */
@@ -417,6 +418,13 @@ static irqreturn_t timer_interrupt(int i
rdtscll_sync(&tsc);
+ if (vxtime_last_invalid) {
+ if (vxtime.mode == VXTIME_HPET)
+ vxtime.last = offset;
+ vxtime.last_tsc = tsc;
+ vxtime_last_invalid = 0;
+ }
+
if (vxtime.mode == VXTIME_HPET) {
if (hpet64 > 0) {
unsigned long delta = offset - vxtime.last;
@@ -1125,6 +1133,7 @@ static int timer_resume(struct sys_devic
sec = ctime + clock_cmos_diff;
write_seqlock_irqsave(&xtime_lock,flags);
+ vxtime_last_invalid = 1;
xtime.tv_sec = sec;
xtime.tv_nsec = 0;
write_sequnlock_irqrestore(&xtime_lock,flags);
The evdev driver is still broken due to the wrong order of arguments of
copy_to_user() in evdev_event_to_user().
The following patch fixes this issue.
Signed-off-by: Rafael J. Wysocki <[email protected]>
Signed-off-by: Dmitry Torokhov <[email protected]>
Index: linux-2.6.15-rc2-mm1/drivers/input/evdev.c
===================================================================
--- linux-2.6.15-rc2-mm1.orig/drivers/input/evdev.c 2005-11-23 22:07:30.000000000 +0100
+++ linux-2.6.15-rc2-mm1/drivers/input/evdev.c 2005-11-26 17:38:02.000000000 +0100
@@ -194,7 +194,7 @@
return 0;
}
-static int evdev_event_to_user(const char __user *buffer, struct input_event *event)
+static int evdev_event_to_user(char __user *buffer, struct input_event *event)
{
if (COMPAT_TEST) {
struct input_event_compat compat_event;
@@ -205,11 +205,11 @@
compat_event.code = event->code;
compat_event.value = event->value;
- if (copy_to_user(&compat_event, buffer, sizeof(struct input_event_compat)))
+ if (copy_to_user(buffer, &compat_event, sizeof(struct input_event_compat)))
return -EFAULT;
} else {
- if (copy_to_user(event, buffer, sizeof(struct input_event)))
+ if (copy_to_user(buffer, event, sizeof(struct input_event)))
return -EFAULT;
}
Hi,
On Sunday, 11 December 2005 13:13, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/
I see three problems, but they are unrelated, so I'll describe them separately
in replies to this message.
Greetings,
Rafael
The ehci_hcd driver causes problems like this:
ehci_hcd 0000:00:02.2: EHCI Host Controller
ehci_hcd 0000:00:02.2: debug port 1
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3
ehci_hcd 0000:00:02.2: irq 5, io mem 0xfebfdc00
usb 2-2: Product: USB Receiver
usb 2-2: Manufacturer: Logitech
usb 2-2: configuration #1 chosen from 1 choice
ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
Unable to handle kernel NULL pointer dereference at 00000000000002a4 RIP:
<ffffffff880ad9d0>{:ehci_hcd:ehci_irq+224}
PGD 2dba6067 PUD 2d477067 PMD 0
Oops: 0000 [1] PREEMPT
CPU 0
Modules linked in: ehci_hcd ohci_hcd sk98lin sd_mod scsi_mod ide_cd cdrom dm_mod parport_pc lp parport
Pid: 1336, comm: modprobe Not tainted 2.6.15-rc5-mm2 #2
RIP: 0010:[<ffffffff880ad9d0>] <ffffffff880ad9d0>{:ehci_hcd:ehci_irq+224}
RSP: 0018:ffffffff80481e08 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 0000000000000000
RDX: ffffc2000007ac20 RSI: 00000000ffffffff RDI: ffff81002c5d3c78
RBP: ffffffff80481ee8 R08: 0000000000010000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: ffff81002c5d3c78
R13: ffff81002c5d3c58 R14: ffff81002c5d3b08 R15: 0000000000000000
FS: 00002aaaaade8b00(0000) GS:ffffffff8050f000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00000000000002a4 CR3: 000000002cc54000 CR4: 00000000000006e0
Process modprobe (pid: 1336, threadinfo ffff81002dac6000, task ffff81002fdf2790)
Stack: ffffffff80481e38 ffff81002dac7b88 ffffffff801819e0 ffff810001c365c0
ffff81002fdf32f0 ffff81002fdf3000 ffffffff80481e78 ffffffff8017b5f5
ffffffff80481e58 ffff810001c365c0
Call Trace: <IRQ> <ffffffff801819e0>{filp_dtor+0} <ffffffff8017b5f5>{cache_free_debugcheck+597}
<ffffffff80181516>{file_free_rcu+22} <ffffffff802dbe04>{usb_hcd_irq+52}
<ffffffff8015b563>{handle_IRQ_event+51} <ffffffff8015b652>{__do_IRQ+162}
<ffffffff801114b7>{do_IRQ+55} <ffffffff8010f0b0>{ret_from_intr+0}
<EOI> <ffffffff801c1a01>{sysfs_add_file+1} <ffffffff801c1aad>{sysfs_create_file+61}
<ffffffff802bfd47>{class_device_create_file+23} <ffffffff880ae0c9>{:ehci_hcd:ehci_run+377}
<ffffffff802d6a86>{usb_alloc_dev+262} <ffffffff802dd4df>{usb_add_hcd+1007}
<ffffffff802e6f53>{usb_hcd_pci_probe+691} <ffffffff802584da>{pci_device_probe+106}
<ffffffff802bed79>{driver_probe_device+89} <ffffffff802bedf0>{__driver_attach+0}
<ffffffff802bee51>{__driver_attach+97} <ffffffff802be68f>{bus_for_each_dev+79}
<ffffffff802bec0c>{driver_attach+28} <ffffffff802be058>{bus_add_driver+136}
<ffffffff802beff9>{driver_register+121} <ffffffff8025878e>{__pci_register_driver+206}
<ffffffff88011050>{:ehci_hcd:ehci_hcd_pci_init+80} <ffffffff80150a1d>{sys_init_module+253}
<ffffffff8010eb0e>{system_call+126}
Code: 0f b6 80 a4 02 00 00 83 e0 03 3c 03 0f 85 9e 00 00 00 45 8b
RIP <ffffffff880ad9d0>{:ehci_hcd:ehci_irq+224} RSP <ffffffff80481e08>
CR2: 00000000000002a4
<0>Kernel panic - not syncing: Aiee, killing interrupt handler!
to appear from time to time when it's being loaded (20% of times or so).
If it loads successfully, it seems to work fine.
On 12/11/05, Andrew Morton <[email protected]> wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/
>
When booting this kernel with vga=791 like I normally do, the kernel
hangs on boot. Booting with vga=normal works just fine.
I don't have very much info since as soon as the videomode is switched
I get a small rectangle of messed up colours in the top left corner of
the screen (the rest is just black) and then it hangs - even the
keyboard is dead, I have to powercycle the machine.
Nothing makes it to the logs and I don't have a second machine atm to
get logs via serial console or netconsole.
I've got the vesafb driver build in, none of the other fb drivers.
Videocard is :
01:05.0 VGA compatible controller: Matrox Graphics, Inc. MGA Parhelia
AGP (rev 03) (prog-if 00 [VGA])
Subsystem: Matrox Graphics, Inc. Parhelia 128Mb
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (4000ns min, 8000ns max), cache line size 08
Interrupt: pin A routed to IRQ 4
Region 0: Memory at e8000000 (32-bit, prefetchable) [size=128M]
Region 1: Memory at e5000000 (32-bit, non-prefetchable) [size=8K]
Expansion ROM at e7fe0000 [disabled] [size=128K]
Capabilities: <available only to root>
00: 2b 10 27 05 07 00 b0 02 03 00 00 03 08 40 00 00
10: 08 00 00 e8 00 00 00 e5 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 2b 10 40 08
30: 00 00 fe e7 dc 00 00 00 00 00 00 00 04 01 10 20
--
Jesper Juhl <[email protected]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
Hello Andrew,
Sunday, December 11, 2005, 1:13:08 PM, you wrote:
> - New CPU scheduler policy: SCHED_BATCH.
Yes, Yes, Yesss. THANKS! Me not worthy, me bow before Con and Andrew ;-)
As for apache/python voting rules, here's my +1 for vanilla inclusion.
Anyway this makes me think. I remember Con saying that SCHED_BATCH relies
on his staircase scheduler. I understand this is kind of a rewrite for
the current scheduler, right?
--
Best regards,
Maciej
On Sun, Dec 11, 2005 at 04:13:08AM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.15-rc5-mm1:
>...
> +i386-cs5535-chip-support-cpu.patch
>...
> Updated. Still need work.
>...
This patch adds a module cs5535 under arch/i386/kernel/, but there's
already a module of the same name present under drivers/ide/pci/.
This is a problem if both are modular since two modules of the same name
are not possible.
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 Sunday 11 December 2005 11:02, Rafael J. Wysocki wrote:
> The evdev driver is still broken due to the wrong order of arguments of
> copy_to_user() in evdev_event_to_user().
>
I added the correct version to my tree so next time Andrew pulls from -mm
it will be there.
--
Dmitry
"Rafael J. Wysocki" <[email protected]> wrote:
>
> The ehci_hcd driver causes problems like this:
>
> ehci_hcd 0000:00:02.2: EHCI Host Controller
> ehci_hcd 0000:00:02.2: debug port 1
> ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3
> ehci_hcd 0000:00:02.2: irq 5, io mem 0xfebfdc00
> usb 2-2: Product: USB Receiver
> usb 2-2: Manufacturer: Logitech
> usb 2-2: configuration #1 chosen from 1 choice
> ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
> Unable to handle kernel NULL pointer dereference at 00000000000002a4 RIP:
> <ffffffff880ad9d0>{:ehci_hcd:ehci_irq+224}
Can you poke around in gdb, see which line it's dying at?
> PGD 2dba6067 PUD 2d477067 PMD 0
> Oops: 0000 [1] PREEMPT
> CPU 0
> Modules linked in: ehci_hcd ohci_hcd sk98lin sd_mod scsi_mod ide_cd cdrom dm_mod parport_pc lp parport
> Pid: 1336, comm: modprobe Not tainted 2.6.15-rc5-mm2 #2
> RIP: 0010:[<ffffffff880ad9d0>] <ffffffff880ad9d0>{:ehci_hcd:ehci_irq+224}
> RSP: 0018:ffffffff80481e08 EFLAGS: 00010202
> RAX: 0000000000000000 RBX: 0000000000000004 RCX: 0000000000000000
> RDX: ffffc2000007ac20 RSI: 00000000ffffffff RDI: ffff81002c5d3c78
> RBP: ffffffff80481ee8 R08: 0000000000010000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000246 R12: ffff81002c5d3c78
> R13: ffff81002c5d3c58 R14: ffff81002c5d3b08 R15: 0000000000000000
> FS: 00002aaaaade8b00(0000) GS:ffffffff8050f000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 00000000000002a4 CR3: 000000002cc54000 CR4: 00000000000006e0
> Process modprobe (pid: 1336, threadinfo ffff81002dac6000, task ffff81002fdf2790)
> Stack: ffffffff80481e38 ffff81002dac7b88 ffffffff801819e0 ffff810001c365c0
> ffff81002fdf32f0 ffff81002fdf3000 ffffffff80481e78 ffffffff8017b5f5
> ffffffff80481e58 ffff810001c365c0
> Call Trace: <IRQ> <ffffffff801819e0>{filp_dtor+0} <ffffffff8017b5f5>{cache_free_debugcheck+597}
> <ffffffff80181516>{file_free_rcu+22} <ffffffff802dbe04>{usb_hcd_irq+52}
> <ffffffff8015b563>{handle_IRQ_event+51} <ffffffff8015b652>{__do_IRQ+162}
> <ffffffff801114b7>{do_IRQ+55} <ffffffff8010f0b0>{ret_from_intr+0}
> <EOI> <ffffffff801c1a01>{sysfs_add_file+1} <ffffffff801c1aad>{sysfs_create_file+61}
> <ffffffff802bfd47>{class_device_create_file+23} <ffffffff880ae0c9>{:ehci_hcd:ehci_run+377}
> <ffffffff802d6a86>{usb_alloc_dev+262} <ffffffff802dd4df>{usb_add_hcd+1007}
> <ffffffff802e6f53>{usb_hcd_pci_probe+691} <ffffffff802584da>{pci_device_probe+106}
> <ffffffff802bed79>{driver_probe_device+89} <ffffffff802bedf0>{__driver_attach+0}
> <ffffffff802bee51>{__driver_attach+97} <ffffffff802be68f>{bus_for_each_dev+79}
> <ffffffff802bec0c>{driver_attach+28} <ffffffff802be058>{bus_add_driver+136}
> <ffffffff802beff9>{driver_register+121} <ffffffff8025878e>{__pci_register_driver+206}
> <ffffffff88011050>{:ehci_hcd:ehci_hcd_pci_init+80} <ffffffff80150a1d>{sys_init_module+253}
> <ffffffff8010eb0e>{system_call+126}
>
> Code: 0f b6 80 a4 02 00 00 83 e0 03 3c 03 0f 85 9e 00 00 00 45 8b
> RIP <ffffffff880ad9d0>{:ehci_hcd:ehci_irq+224} RSP <ffffffff80481e08>
> CR2: 00000000000002a4
> <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
>
> to appear from time to time when it's being loaded (20% of times or so).
> If it loads successfully, it seems to work fine.
Fix vesafb hang when scroll mode is REDRAW.
Signed-off-by: Antonino Daplas <[email protected]>
---
Jesper Juhl wrote:
> On 12/11/05, Andrew Morton <[email protected]> wrote:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/
>>
> When booting this kernel with vga=791 like I normally do, the kernel
> hangs on boot. Booting with vga=normal works just fine.
> I don't have very much info since as soon as the videomode is switched
> I get a small rectangle of messed up colours in the top left corner of
> the screen (the rest is just black) and then it hangs - even the
> keyboard is dead, I have to powercycle the machine.
> Nothing makes it to the logs and I don't have a second machine atm to
> get logs via serial console or netconsole.
> I've got the vesafb driver build in, none of the other fb drivers.
>
Sorry about that. This particular hunk was missing in the
vesafb_trim_pan_display.patch
Tony
drivers/video/vesafb.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/video/vesafb.c b/drivers/video/vesafb.c
index e6e56b8..8982e54 100644
--- a/drivers/video/vesafb.c
+++ b/drivers/video/vesafb.c
@@ -417,6 +417,9 @@ static int __init vesafb_probe(struct pl
info->flags = FBINFO_FLAG_DEFAULT |
(ypan) ? FBINFO_HWACCEL_YPAN : 0;
+ if (!ypan)
+ info->fbops->fb_pan_display = NULL;
+
if (fb_alloc_cmap(&info->cmap, 256, 0) < 0) {
err = -ENOMEM;
goto err;
On 12/11/05, Antonino A. Daplas <[email protected]> wrote:
> Fix vesafb hang when scroll mode is REDRAW.
>
> Signed-off-by: Antonino Daplas <[email protected]>
> ---
>
> Jesper Juhl wrote:
> > On 12/11/05, Andrew Morton <[email protected]> wrote:
> >> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/
> >>
> > When booting this kernel with vga=791 like I normally do, the kernel
> > hangs on boot. Booting with vga=normal works just fine.
> > I don't have very much info since as soon as the videomode is switched
> > I get a small rectangle of messed up colours in the top left corner of
> > the screen (the rest is just black) and then it hangs - even the
> > keyboard is dead, I have to powercycle the machine.
> > Nothing makes it to the logs and I don't have a second machine atm to
> > get logs via serial console or netconsole.
> > I've got the vesafb driver build in, none of the other fb drivers.
> >
>
> Sorry about that.
No problem, it happens :)
> This particular hunk was missing in the
> vesafb_trim_pan_display.patch
>
I just rebuild 2.6.15-rc5-mm2 with that patch applied and I can
confirm that it fixes the problem.
So, I guess I should add
Acked-by: Jesper Juhl <[email protected]>
Andrew, could you please merge that patch from Antonio?
One small detail; With 2.6.15-rc5-mm2 I see a small (rather
insignificant) difference in behaviour compared to 2.6.15-rc5-git1
just at the time when the video mode is switched at boot.
With 2.6.15-rc5-git1 it goes straight from the text mode display to
the graphical one with the boot logo in the top left corner. With
2.6.15-rc5-mm2 + your patch I get a brief, split second, image with
random green/grey/white pixels in the location where the penguin
appears a few ms later - then everything is normal.
No big deal and it doesn't bother me, just thought it might be
something you'd want to know about...
--
Jesper Juhl <[email protected]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
On Sun, 11 Dec 2005 04:13:08 -0800, Andrew Morton <[email protected]> wrote:
>
>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/
Locked up on boot just after
"USB 2.0 initialised, EHCI 1.00, driver 10 Dec 2004",
where I'd expect to see the first "USB hub found" message.
box info: http://bugsplatter.mine.nu/test/boxen/sempro/
Sempron SktA on VIA chipset.
Grant.
Hi Andrew,
the following patch fixes the issues in
s390-introduce-struct-channel_subsystem.patch and
s390-convert-proc-cio_ignore.patch.
s390: Fix missing release function and cosmetic changes.
- Use kzalloc() in blacklist.c.
- Kill unwanted casts in blacklist.c.
- Provide release function for struct channel_subsystem.
Signed-off-by: Cornelia Huck <[email protected]>
CC: Martin Schwidefsky <[email protected]>
blacklist.c | 7 +++----
css.c | 10 ++++++++++
2 files changed, 13 insertions(+), 4 deletions(-)
diff -Naurp linux-2.6.15-rc5-mm2/drivers/s390/cio/blacklist.c linux-2.6.15-rc5-mm2+cio/drivers/s390/cio/blacklist.c
--- linux-2.6.15-rc5-mm2/drivers/s390/cio/blacklist.c 2005-12-12 13:20:53.000000000 +0100
+++ linux-2.6.15-rc5-mm2+cio/drivers/s390/cio/blacklist.c 2005-12-12 13:21:05.000000000 +0100
@@ -299,10 +299,9 @@ cio_ignore_proc_seq_start(struct seq_fil
if (*offset >= (__MAX_SUBCHANNEL + 1) * (__MAX_SSID + 1))
return NULL;
- iter = kmalloc(sizeof(struct ccwdev_iter), GFP_KERNEL);
+ iter = kzalloc(sizeof(struct ccwdev_iter), GFP_KERNEL);
if (!iter)
return ERR_PTR(-ENOMEM);
- memset(iter, 0, sizeof(struct ccwdev_iter));
iter->ssid = *offset / (__MAX_SUBCHANNEL + 1);
iter->devno = *offset % (__MAX_SUBCHANNEL + 1);
return iter;
@@ -322,7 +321,7 @@ cio_ignore_proc_seq_next(struct seq_file
if (*offset >= (__MAX_SUBCHANNEL + 1) * (__MAX_SSID + 1))
return NULL;
- iter = (struct ccwdev_iter *)it;
+ iter = it;
if (iter->devno == __MAX_SUBCHANNEL) {
iter->devno = 0;
iter->ssid++;
@@ -339,7 +338,7 @@ cio_ignore_proc_seq_show(struct seq_file
{
struct ccwdev_iter *iter;
- iter = (struct ccwdev_iter *)it;
+ iter = it;
if (!is_blacklisted(iter->ssid, iter->devno))
/* Not blacklisted, nothing to output. */
return 0;
diff -Naurp linux-2.6.15-rc5-mm2/drivers/s390/cio/css.c linux-2.6.15-rc5-mm2+cio/drivers/s390/cio/css.c
--- linux-2.6.15-rc5-mm2/drivers/s390/cio/css.c 2005-12-12 13:20:53.000000000 +0100
+++ linux-2.6.15-rc5-mm2+cio/drivers/s390/cio/css.c 2005-12-12 13:21:05.000000000 +0100
@@ -444,6 +444,15 @@ css_generate_pgid(struct channel_subsyst
}
+static void
+channel_subsystem_release(struct device *dev)
+{
+ struct channel_subsystem *css;
+
+ css = to_css(dev);
+ kfree(css);
+}
+
static inline void __init
setup_css(int nr)
{
@@ -453,6 +462,7 @@ setup_css(int nr)
css[nr]->valid = 1;
css[nr]->cssid = nr;
sprintf(css[nr]->device.bus_id, "css%x", nr);
+ css[nr]->device.release = channel_subsystem_release;
tod_high = (u32) (get_clock() >> 32);
css_generate_pgid(css[nr], tod_high);
}
Hi Adrian,
Thanks for pointing that out. I'll use a different name.
Perhaps the cs5535 ide module should also be renamed to something more
sane, like "cs5535-ide".
Ben
On 12/11/05, Adrian Bunk <[email protected]> wrote:
> On Sun, Dec 11, 2005 at 04:13:08AM -0800, Andrew Morton wrote:
> >...
> > Changes since 2.6.15-rc5-mm1:
> >...
> > +i386-cs5535-chip-support-cpu.patch
> >...
> > Updated. Still need work.
> >...
>
> This patch adds a module cs5535 under arch/i386/kernel/, but there's
> already a module of the same name present under drivers/ide/pci/.
>
> This is a problem if both are modular since two modules of the same name
> are not possible.
>
> 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 Sunday, 11 December 2005 21:38, Andrew Morton wrote:
> "Rafael J. Wysocki" <[email protected]> wrote:
> >
> > The ehci_hcd driver causes problems like this:
> >
> > ehci_hcd 0000:00:02.2: EHCI Host Controller
> > ehci_hcd 0000:00:02.2: debug port 1
> > ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3
> > ehci_hcd 0000:00:02.2: irq 5, io mem 0xfebfdc00
> > usb 2-2: Product: USB Receiver
> > usb 2-2: Manufacturer: Logitech
> > usb 2-2: configuration #1 chosen from 1 choice
> > ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
> > Unable to handle kernel NULL pointer dereference at 00000000000002a4 RIP:
> > <ffffffff880ad9d0>{:ehci_hcd:ehci_irq+224}
>
> Can you poke around in gdb, see which line it's dying at?
It looks like at the line 620. At least here's what gdb told me:
Line 620 of "ehci-hcd.c" starts at address 0x69c3 <ehci_irq+211>
and ends at 0x69e2 <ehci_irq+242>.
"Rafael J. Wysocki" <[email protected]> wrote:
>
> On Sunday, 11 December 2005 21:38, Andrew Morton wrote:
> > "Rafael J. Wysocki" <[email protected]> wrote:
> > >
> > > The ehci_hcd driver causes problems like this:
> > >
> > > ehci_hcd 0000:00:02.2: EHCI Host Controller
> > > ehci_hcd 0000:00:02.2: debug port 1
> > > ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3
> > > ehci_hcd 0000:00:02.2: irq 5, io mem 0xfebfdc00
> > > usb 2-2: Product: USB Receiver
> > > usb 2-2: Manufacturer: Logitech
> > > usb 2-2: configuration #1 chosen from 1 choice
> > > ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
> > > Unable to handle kernel NULL pointer dereference at 00000000000002a4 RIP:
> > > <ffffffff880ad9d0>{:ehci_hcd:ehci_irq+224}
> >
> > Can you poke around in gdb, see which line it's dying at?
>
> It looks like at the line 620. At least here's what gdb told me:
>
> Line 620 of "ehci-hcd.c" starts at address 0x69c3 <ehci_irq+211>
> and ends at 0x69e2 <ehci_irq+242>.
On my tree that's
if ((status & STS_PCD) && device_may_wakeup(&hcd->self.root_hub->dev)) {
It's best to actually send a copy of line 620 - kernels vary a lot, and
many developers won't have that particualr -mm tree handy.
The way I normally do this is to do `gdb vmlinux' and then `l
*0xffffffff880ad9d0'. If that lands you in some inline function then poke
around, displacing the EIP by +/- amounts until it lands outside the
inlined function so you can see the callsite.
Anyway. Greg's tree seems rather buggy lately..
On Monday, 12 December 2005 21:29, Andrew Morton wrote:
> "Rafael J. Wysocki" <[email protected]> wrote:
> >
> > On Sunday, 11 December 2005 21:38, Andrew Morton wrote:
> > > "Rafael J. Wysocki" <[email protected]> wrote:
> > > >
> > > > The ehci_hcd driver causes problems like this:
> > > >
> > > > ehci_hcd 0000:00:02.2: EHCI Host Controller
> > > > ehci_hcd 0000:00:02.2: debug port 1
> > > > ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3
> > > > ehci_hcd 0000:00:02.2: irq 5, io mem 0xfebfdc00
> > > > usb 2-2: Product: USB Receiver
> > > > usb 2-2: Manufacturer: Logitech
> > > > usb 2-2: configuration #1 chosen from 1 choice
> > > > ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
> > > > Unable to handle kernel NULL pointer dereference at 00000000000002a4 RIP:
> > > > <ffffffff880ad9d0>{:ehci_hcd:ehci_irq+224}
> > >
> > > Can you poke around in gdb, see which line it's dying at?
> >
> > It looks like at the line 620. At least here's what gdb told me:
> >
> > Line 620 of "ehci-hcd.c" starts at address 0x69c3 <ehci_irq+211>
> > and ends at 0x69e2 <ehci_irq+242>.
>
> On my tree that's
>
> if ((status & STS_PCD) && device_may_wakeup(&hcd->self.root_hub->dev)) {
Yes, that's it.
> It's best to actually send a copy of line 620 - kernels vary a lot, and
> many developers won't have that particualr -mm tree handy.
>
> The way I normally do this is to do `gdb vmlinux' and then `l
> *0xffffffff880ad9d0'.
Does it work for modules too?
> If that lands you in some inline function then poke
> around, displacing the EIP by +/- amounts until it lands outside the
> inlined function so you can see the callsite.
>
> Anyway. Greg's tree seems rather buggy lately..
Well ...
--
Beer is proof that God loves us and wants us to be happy - Benjamin Franklin
"Rafael J. Wysocki" <[email protected]> wrote:
>
> > It's best to actually send a copy of line 620 - kernels vary a lot, and
> > many developers won't have that particualr -mm tree handy.
> >
> > The way I normally do this is to do `gdb vmlinux' and then `l
> > *0xffffffff880ad9d0'.
>
> Does it work for modules too?
Ah. There are certainly ways of doing this - see the kgdb documentation.
Or you can work out the module load address, gdb the module and do the
appropriate arithmetic I guess.
Generally I just statically link anything which I want to play with.
On Monday, 12 December 2005 22:09, Andrew Morton wrote:
> "Rafael J. Wysocki" <[email protected]> wrote:
> >
> > > It's best to actually send a copy of line 620 - kernels vary a lot, and
> > > many developers won't have that particualr -mm tree handy.
> > >
> > > The way I normally do this is to do `gdb vmlinux' and then `l
> > > *0xffffffff880ad9d0'.
> >
> > Does it work for modules too?
>
> Ah. There are certainly ways of doing this - see the kgdb documentation.
> Or you can work out the module load address, gdb the module and do the
> appropriate arithmetic I guess.
>
> Generally I just statically link anything which I want to play with.
Still, the oops is from a module. I could link it statically for debugging,
but then the address would be different to the one in the oops.
Anyway, please tell me if my reasoning was correct: I thought I couldn't
figure it out based on the absolute address, but I could use the
displacements. Namely, it followed from the oops that the problem
occured at the address {:ehci_hcd:ehci_irq+224}, which is at the
offset 224 wrt ehci_irq, so I did:
gdb drivers/usb/host/ehci-hcd.o
In gdb I did:
info line ehci_irq
and it told me the address the line started at, so I added 224 to it and
got the line 620.
"Rafael J. Wysocki" <[email protected]> wrote:
>
> On Monday, 12 December 2005 22:09, Andrew Morton wrote:
> > "Rafael J. Wysocki" <[email protected]> wrote:
> > >
> > > > It's best to actually send a copy of line 620 - kernels vary a lot, and
> > > > many developers won't have that particualr -mm tree handy.
> > > >
> > > > The way I normally do this is to do `gdb vmlinux' and then `l
> > > > *0xffffffff880ad9d0'.
> > >
> > > Does it work for modules too?
> >
> > Ah. There are certainly ways of doing this - see the kgdb documentation.
> > Or you can work out the module load address, gdb the module and do the
> > appropriate arithmetic I guess.
> >
> > Generally I just statically link anything which I want to play with.
>
> Still, the oops is from a module. I could link it statically for debugging,
> but then the address would be different to the one in the oops.
>
> Anyway, please tell me if my reasoning was correct: I thought I couldn't
> figure it out based on the absolute address, but I could use the
> displacements. Namely, it followed from the oops that the problem
> occured at the address {:ehci_hcd:ehci_irq+224}, which is at the
> offset 224 wrt ehci_irq, so I did:
>
> gdb drivers/usb/host/ehci-hcd.o
>
> In gdb I did:
>
> info line ehci_irq
>
> and it told me the address the line started at, so I added 224 to it and
> got the line 620.
That's a good way of doing it.
On Llu, 2005-12-12 at 12:29 -0600, Ben Gardner wrote:
> Hi Adrian,
>
> Thanks for pointing that out. I'll use a different name.
>
> Perhaps the cs5535 ide module should also be renamed to something more
> sane, like "cs5535-ide".
Historically all chipsets for IDE have been known by the chipset name.
Its already changed for the new sata layer. Its probably better to
rename the gpio type module, if indeed its even worth having in the
kernel (which I'm dubious about)
On Monday 12 December 2005 03:12, Maciej Soltysiak wrote:
> Hello Andrew,
>
> Sunday, December 11, 2005, 1:13:08 PM, you wrote:
> > - New CPU scheduler policy: SCHED_BATCH.
>
> Yes, Yes, Yesss. THANKS! Me not worthy, me bow before Con and Andrew ;-)
> As for apache/python voting rules, here's my +1 for vanilla inclusion.
>
> Anyway this makes me think. I remember Con saying that SCHED_BATCH relies
> on his staircase scheduler. I understand this is kind of a rewrite for
> the current scheduler, right?
Hi Maciej
I missed this announcement (been on leave for a while). This SCHED_BATCH
implementation is by Ingo and it it is not "idle" scheduling as I have
implemented in the staircase scheduler. This is just to restrict a task to
not having any interactive bonus at any stage and to have predictable
scheduling behaviour I guess.
Cheers,
Con
On 12/12/2005 1:20 a.m., Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/
>
> - Many new driver updates and architecture updates
>
> - New CPU scheduler policy: SCHED_BATCH.
>
> - New version of the hrtimers code.
Works fine. However now that Redhat Rawhide contains gcc version 4.1.0 20051207
(Red Hat 4.1.0-0.6) I'm seeing quite a few compile warnings, one in particular
appearing in hundreds of lines:
In file included from include/asm/mpspec.h:5,
from include/asm/smp.h:18,
from include/linux/smp.h:22,
from include/linux/sched.h:26,
from include/linux/module.h:10,
from drivers/net/sky2.c:39:
include/asm/mpspec_def.h:78: warning: 'packed' attribute ignored for field of
type 'unsigned char[5u]'
There is a patch in the Fedora Core Kernel RPM that 'fixes' this for the FC kernels:
http://cvs.fedora.redhat.com/viewcvs/devel/kernel/linux-2.6-gcc41.patch
http://cvs.fedora.redhat.com/viewcvs/devel/kernel/linux-2.6-gcc41.patch?rev=1.3&view=markup
Perhaps part or all of it could go into -mm for further testing? Is this a gcc
glitch or something that ought to be fixed in the kernel? (davej?)
reuben
>
> if ((status & STS_PCD) && device_may_wakeup(&hcd->self.root_hub->dev)) {
What happens if you make that line read
if ((status & STS_PCD) != 0) {
and ignore the root hub thing? There's some confusion about when the root
hub becomes available ... it should be done a lot earlier than it is now,
like before any HCD code may need to rely on it.
- Dave
On Tuesday, 13 December 2005 07:52, David Brownell wrote:
> >
> > if ((status & STS_PCD) && device_may_wakeup(&hcd->self.root_hub->dev)) {
>
> What happens if you make that line read
>
> if ((status & STS_PCD) != 0) {
>
> and ignore the root hub thing?
So far, so good. It works and hasn't triggered the oops yet. I'll report if there's
anything wrong with it.
Greetings,
Rafael
On Tuesday 13 December 2005 2:10 pm, Rafael J. Wysocki wrote:
> On Tuesday, 13 December 2005 07:52, David Brownell wrote:
> > >
> > > if ((status & STS_PCD) && device_may_wakeup(&hcd->self.root_hub->dev)) {
> >
> > What happens if you make that line read
> >
> > if ((status & STS_PCD) != 0) {
> >
> > and ignore the root hub thing?
>
> So far, so good. It works and hasn't triggered the oops yet. I'll report if there's
> anything wrong with it.
I suspect that should be safe to merge for 2.6.15, and it might be
worth considering that. You were using kexec() right?
- Dave
On Tuesday, 13 December 2005 23:22, David Brownell wrote:
> On Tuesday 13 December 2005 2:10 pm, Rafael J. Wysocki wrote:
> > On Tuesday, 13 December 2005 07:52, David Brownell wrote:
> > > >
> > > > if ((status & STS_PCD) && device_may_wakeup(&hcd->self.root_hub->dev)) {
> > >
> > > What happens if you make that line read
> > >
> > > if ((status & STS_PCD) != 0) {
> > >
> > > and ignore the root hub thing?
> >
> > So far, so good. It works and hasn't triggered the oops yet. I'll report if there's
> > anything wrong with it.
>
> I suspect that should be safe to merge for 2.6.15, and it might be
> worth considering that. You were using kexec() right?
No, I was not. Why would that be important?
Rafael
> > > > > if ((status & STS_PCD) && device_may_wakeup(&hcd->self.root_hub->dev)) {
> > > >
> > > > What happens if you make that line read
> > > >
> > > > if ((status & STS_PCD) != 0) {
> > > >
> > > > and ignore the root hub thing?
> > >
> > > So far, so good. It works and hasn't triggered the oops yet. I'll report if there's
> > > anything wrong with it.
> >
> > I suspect that should be safe to merge for 2.6.15, and it might be
> > worth considering that. You were using kexec() right?
>
> No, I was not. Why would that be important?
Just trying to keep the symptoms straight, that's all.
- Dave
On Sun, 11 Dec 2005 04:13:08 -0800, Andrew Morton <[email protected]> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/
>
Booting a SMP built kernel with 'nosmp' just hangs at the VFS layer, with
the message about 'not being able to find root device sda1'.
sda is a SATA drive on an Intel ICH5 controller:
libata version 1.20 loaded.
ata_piix 0000:00:1f.2: version 1.05
ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0xC000 ctl 0xC402 bmdma 0xD000 irq 16
ata2: SATA max UDMA/133 cmd 0xC800 ctl 0xCC02 bmdma 0xD008 irq 16
ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:407f
ata1: dev 0 ATA-6, max UDMA/133, 390721968 sectors: LBA48
ata1: dev 0 configured for UDMA/133
scsi0 : ata_piix
ATA: abnormal status 0x7F on port 0xC807
scsi1 : ata_piix
Vendor: ATA Model: ST3200822AS Rev: 3.01
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3
sd 0:0:0:0: Attached scsi disk sda
I would have to double check, but I think it even missed the USB keyboard.
Something really strange...
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandriva Linux release 2006.1 (Cooker) for i586
Linux 2.6.14-jam4 (gcc 4.0.2 (4.0.2-1mdk for Mandriva Linux release 2006.1))
Hi,
On 11/12/2005 11:13 p.m., Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/
>
> - Many new driver updates and architecture updates
>
> - New CPU scheduler policy: SCHED_BATCH.
>
> - New version of the hrtimers code.
I've just had my kernel suffer a meltdown with 2.6.15-rc5-mm2, there was a
massive amount of console output streaming for an hour or so till I got control
but this was logged in the messages log immediately after it went amiss.
I'm about to run up -mm3 but didn't see any obvious fix for this so possibly
it's still a problem in that one too?
Dec 16 00:01:41 tornado kernel: BUG: soft lockup detected on CPU#0!
Dec 16 00:01:41 tornado kernel:
Dec 16 00:01:41 tornado kernel: Pid: 8, comm: events/0
Dec 16 00:01:41 tornado kernel: EIP: 0060:[<c031fb4b>] CPU: 0
Dec 16 00:01:41 tornado kernel: EIP is at _spin_unlock_irqrestore+0x5/0x6
Dec 16 00:01:41 tornado kernel: EFLAGS: 00000286 Not tainted (2.6.15-rc5-mm2)
Dec 16 00:01:41 tornado kernel: EAX: c0444e60 EBX: 0000003e ECX: 00000a19 EDX:
00000286
Dec 16 00:01:41 tornado kernel: ESI: 00000000 EDI: cecd5981 EBP: f76b7000 DS:
007b ES: 007b
Dec 16 00:01:41 tornado kernel: CR0: 8005003b CR2: b7aff004 CR3: 0040f000 CR4:
000006d0
Dec 16 00:01:41 tornado kernel: [<c021f458>] n_tty_receive_buf+0x664/0xa03
Dec 16 00:01:41 tornado kernel: [<c011635e>] load_balance+0x4e/0x1eb
Dec 16 00:01:41 tornado kernel: [<c01169cb>] scheduler_tick+0x31/0x36f
Dec 16 00:01:41 tornado kernel: [<c01107ba>] smp_apic_timer_interrupt+0xc1/0xca
Dec 16 00:01:41 tornado kernel: [<c0104dd1>] do_IRQ+0x41/0x52
Dec 16 00:01:41 tornado kernel: [<c01034e6>] common_interrupt+0x1a/0x20
Dec 16 00:01:41 tornado kernel: [<c021d92a>] flush_to_ldisc+0x64/0xcb
Dec 16 00:01:41 tornado kernel: [<c012a94e>] worker_thread+0x1bf/0x249
Dec 16 00:01:41 tornado kernel: [<c021d8c6>] flush_to_ldisc+0x0/0xcb
Dec 16 00:01:41 tornado kernel: [<c0116d09>] default_wake_function+0x0/0xc
Dec 16 00:01:41 tornado kernel: [<c012a78f>] worker_thread+0x0/0x249
Dec 16 00:01:41 tornado kernel: [<c012d8f9>] kthread+0x93/0x97
Dec 16 00:01:41 tornado kernel: [<c012d866>] kthread+0x0/0x97
Dec 16 00:01:41 tornado kernel: [<c0100fcd>] kernel_thread_helper+0x5/0xb
Dec 16 00:01:51 tornado kernel: BUG: soft lockup detected on CPU#0!
Dec 16 00:01:51 tornado kernel:
Dec 16 00:01:51 tornado kernel: Pid: 8, comm: events/0
Dec 16 00:01:51 tornado kernel: EIP: 0060:[<c021f686>] CPU: 0
Dec 16 00:01:51 tornado kernel: EIP is at n_tty_receive_buf+0x892/0xa03
Dec 16 00:01:51 tornado kernel: EFLAGS: 00000246 Not tainted (2.6.15-rc5-mm2)
Dec 16 00:01:51 tornado kernel: EAX: f76b7404 EBX: f76b7404 ECX: f76b7000 EDX:
00000246
Dec 16 00:01:51 tornado kernel: ESI: 00000246 EDI: cecd59c6 EBP: f76b7000 DS:
007b ES: 007b
Dec 16 00:01:51 tornado kernel: CR0: 8005003b CR2: b7aff004 CR3: 0040f000 CR4:
000006d0
Dec 16 00:01:51 tornado kernel: [<c011635e>] load_balance+0x4e/0x1eb
Dec 16 00:01:51 tornado kernel: [<c01107ba>] smp_apic_timer_interrupt+0xc1/0xca
Dec 16 00:01:51 tornado kernel: [<c0104dd1>] do_IRQ+0x41/0x52
Dec 16 00:01:51 tornado kernel: [<c01034e6>] common_interrupt+0x1a/0x20
Dec 16 00:01:51 tornado kernel: [<c021edf6>] n_tty_receive_buf+0x2/0xa03
Dec 16 00:01:51 tornado kernel: [<c021d92a>] flush_to_ldisc+0x64/0xcb
Dec 16 00:01:51 tornado kernel: [<c012a94e>] worker_thread+0x1bf/0x249
Dec 16 00:01:51 tornado kernel: [<c021d8c6>] flush_to_ldisc+0x0/0xcb
Dec 16 00:01:51 tornado kernel: [<c0116d09>] default_wake_function+0x0/0xc
Dec 16 00:01:51 tornado kernel: [<c012a78f>] worker_thread+0x0/0x249
Dec 16 00:01:51 tornado kernel: [<c012d8f9>] kthread+0x93/0x97
Dec 16 00:01:51 tornado kernel: [<c012d866>] kthread+0x0/0x97
Dec 16 00:01:51 tornado kernel: [<c0100fcd>] kernel_thread_helper+0x5/0xb
Dec 16 00:02:01 tornado kernel: BUG: soft lockup detected on CPU#0!
Dec 16 00:02:01 tornado kernel:
Dec 16 00:02:01 tornado kernel: Pid: 8, comm: events/0
Dec 16 00:02:01 tornado kernel: EIP: 0060:[<c01674b4>] CPU: 0
Dec 16 00:02:01 tornado kernel: EIP is at kill_fasync+0x2d/0x39
Dec 16 00:02:01 tornado kernel: EFLAGS: 00000246 Not tainted (2.6.15-rc5-mm2)
Dec 16 00:02:01 tornado kernel: EAX: f76b70d4 EBX: f76b7404 ECX: 00000000 EDX:
0000001d
Dec 16 00:02:01 tornado kernel: ESI: 00000246 EDI: 0000001d EBP: f76b7000 DS:
007b ES: 007b
Dec 16 00:02:01 tornado kernel: CR0: 8005003b CR2: b7aff004 CR3: 0040f000 CR4:
000006d0
Dec 16 00:02:01 tornado kernel: [<c021f69b>] n_tty_receive_buf+0x8a7/0xa03
Dec 16 00:02:01 tornado kernel: [<c011635e>] load_balance+0x4e/0x1eb
Dec 16 00:02:01 tornado kernel: [<c01169cb>] scheduler_tick+0x31/0x36f
Dec 16 00:02:01 tornado kernel: [<c01107ba>] smp_apic_timer_interrupt+0xc1/0xca
Dec 16 00:02:01 tornado kernel: [<c0104dd1>] do_IRQ+0x41/0x52
Dec 16 00:02:01 tornado kernel: [<c01034e6>] common_interrupt+0x1a/0x20
Dec 16 00:02:01 tornado kernel: [<c021007b>] acpi_ec_gpe_intr_handler+0x35/0xa6
Dec 16 00:02:01 tornado kernel: [<c021d92a>] flush_to_ldisc+0x64/0xcb
Dec 16 00:02:01 tornado kernel: [<c012a94e>] worker_thread+0x1bf/0x249
Dec 16 00:02:01 tornado kernel: [<c021d8c6>] flush_to_ldisc+0x0/0xcb
Dec 16 00:02:01 tornado kernel: [<c0116d09>] default_wake_function+0x0/0xc
Dec 16 00:02:01 tornado kernel: [<c012a78f>] worker_thread+0x0/0x249
Dec 16 00:02:01 tornado kernel: [<c012d8f9>] kthread+0x93/0x97
Dec 16 00:02:01 tornado kernel: [<c012d866>] kthread+0x0/0x97
Dec 16 00:02:01 tornado kernel: [<c0100fcd>] kernel_thread_helper+0x5/0xb
Dec 16 00:02:11 tornado kernel: BUG: soft lockup detected on CPU#0!
Dec 16 00:02:11 tornado kernel:
Dec 16 00:02:11 tornado kernel: Pid: 8, comm: events/0
Dec 16 00:02:11 tornado kernel: EIP: 0060:[<c0230455>] CPU: 0
Dec 16 00:02:11 tornado kernel: EIP is at uart_write_room+0x0/0x18
Dec 16 00:02:11 tornado kernel: EFLAGS: 00000286 Not tainted (2.6.15-rc5-mm2)
Dec 16 00:02:11 tornado kernel: EAX: f76b7000 EBX: 0000000a ECX: 00000439 EDX:
f7cac400
Dec 16 00:02:11 tornado kernel: ESI: f76b7000 EDI: cecd593f EBP: f76b7000 DS:
007b ES: 007b
Dec 16 00:02:11 tornado kernel: CR0: 8005003b CR2: b7aff004 CR3: 0040f000 CR4:
000006d0
Dec 16 00:02:11 tornado kernel: [<c021e5d2>] opost+0x12/0x1cd
Dec 16 00:02:11 tornado kernel: [<c021f63a>] n_tty_receive_buf+0x846/0xa03
Dec 16 00:02:11 tornado kernel: [<c011635e>] load_balance+0x4e/0x1eb
Dec 16 00:02:11 tornado kernel: [<c011679f>] rebalance_tick+0xec/0x10b
Dec 16 00:02:11 tornado kernel: [<c01107ba>] smp_apic_timer_interrupt+0xc1/0xca
Dec 16 00:02:11 tornado kernel: [<c0104dd1>] do_IRQ+0x41/0x52
Dec 16 00:02:11 tornado kernel: [<c01034e6>] common_interrupt+0x1a/0x20
Dec 16 00:02:11 tornado kernel: [<c021007b>] acpi_ec_gpe_intr_handler+0x35/0xa6
Dec 16 00:02:11 tornado kernel: [<c021d92a>] flush_to_ldisc+0x64/0xcb
Dec 16 00:02:11 tornado kernel: [<c012a94e>] worker_thread+0x1bf/0x249
Dec 16 00:02:11 tornado kernel: [<c021d8c6>] flush_to_ldisc+0x0/0xcb
Dec 16 00:02:11 tornado kernel: [<c0116d09>] default_wake_function+0x0/0xc
Dec 16 00:02:11 tornado kernel: [<c012a78f>] worker_thread+0x0/0x249
Dec 16 00:02:11 tornado kernel: [<c012d8f9>] kthread+0x93/0x97
Dec 16 00:02:11 tornado kernel: [<c012d866>] kthread+0x0/0x97
Dec 16 00:02:11 tornado kernel: [<c0100fcd>] kernel_thread_helper+0x5/0xb
Dec 16 00:02:21 tornado kernel: BUG: soft lockup detected on CPU#0!
Dec 16 00:02:21 tornado kernel:
Usual details including .config are up at http://www.reub.net/files/kernel/
reuben
On Fri, 20 Jan 2006 19:22:59 -0800, Andrew Morton <[email protected]> wrote:
> "J.A. Magallon" <[email protected]> wrote:
> >
> > On Sun, 11 Dec 2005 04:13:08 -0800, Andrew Morton <[email protected]> wrote:
> >
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/
> > >
> >
> > Booting a SMP built kernel with 'nosmp' just hangs at the VFS layer, with
> > the message about 'not being able to find root device sda1'.
> > sda is a SATA drive on an Intel ICH5 controller:
> >
> > libata version 1.20 loaded.
> > ata_piix 0000:00:1f.2: version 1.05
> > ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 16
> > PCI: Setting latency timer of device 0000:00:1f.2 to 64
> > ata1: SATA max UDMA/133 cmd 0xC000 ctl 0xC402 bmdma 0xD000 irq 16
> > ata2: SATA max UDMA/133 cmd 0xC800 ctl 0xCC02 bmdma 0xD008 irq 16
> > ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:407f
> > ata1: dev 0 ATA-6, max UDMA/133, 390721968 sectors: LBA48
> > ata1: dev 0 configured for UDMA/133
> > scsi0 : ata_piix
> > ATA: abnormal status 0x7F on port 0xC807
> > scsi1 : ata_piix
> > Vendor: ATA Model: ST3200822AS Rev: 3.01
> > Type: Direct-Access ANSI SCSI revision: 05
> > SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
> > SCSI device sda: drive cache: write back
> > SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
> > SCSI device sda: drive cache: write back
> > sda: sda1 sda2 sda3
> > sd 0:0:0:0: Attached scsi disk sda
> >
> > I would have to double check, but I think it even missed the USB keyboard.
> >
>
> Is this still happening?
Yes. I have just tried with 2.6.16-rc1-mm2, and the result is the same.
No root device.
The nosmp-booted kernel looks much much slow than the SMP one, it takes
ages to detect devices like usb ones, and even spent about 20 seconds here:
[ 0.431601] libata version 1.20 loaded.
[ 0.431652] ata_piix 0000:00:1f.2: version 1.05
[ 0.431670] ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 16
[ 0.431792] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[ 0.431852] ata1: SATA max UDMA/133 cmd 0xC000 ctl 0xC402 bmdma 0xD000 irq 16
[ 0.431950] ata2: SATA max UDMA/133 cmd 0xC800 ctl 0xCC02 bmdma 0xD008 irq 16
>>>>>>>>>>>>> here <<<<<<<<<<<<<<<<<<
[ 0.690451] ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:407f
[ 0.690456] ata1: dev 0 ATA-6, max UDMA/133, 390721968 sectors: LBA48
[ 0.696278] ata1: dev 0 configured for UDMA/133
[ 0.701627] scsi0 : ata_piix
[ 1.937443] scsi1 : ata_piix
and it did not detect any drive, so the no-root-device error. This one can be
a detection timeout, but as I say also the USB detection is dog slooow.
Need some info ? .config, or the like ?
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandriva Linux release 2006.1 (Cooker) for i586
Linux 2.6.15-jam5 (gcc 4.0.2 (4.0.2-1mdk for Mandriva Linux release 2006.1))
On Sun, 22 Jan 2006 00:46:36 +0100 J.A. Magallon wrote:
> On Fri, 20 Jan 2006 19:22:59 -0800, Andrew Morton <[email protected]> wrote:
>
> > "J.A. Magallon" <[email protected]> wrote:
> > >
> > > On Sun, 11 Dec 2005 04:13:08 -0800, Andrew Morton <[email protected]> wrote:
> > >
> > > >
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/
> > > >
> > >
> > > Booting a SMP built kernel with 'nosmp' just hangs at the VFS layer, with
> > > the message about 'not being able to find root device sda1'.
> > > sda is a SATA drive on an Intel ICH5 controller:
> > >
> > > libata version 1.20 loaded.
> > > ata_piix 0000:00:1f.2: version 1.05
> > > ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 16
> > > PCI: Setting latency timer of device 0000:00:1f.2 to 64
> > > ata1: SATA max UDMA/133 cmd 0xC000 ctl 0xC402 bmdma 0xD000 irq 16
> > > ata2: SATA max UDMA/133 cmd 0xC800 ctl 0xCC02 bmdma 0xD008 irq 16
> > > ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:407f
> > > ata1: dev 0 ATA-6, max UDMA/133, 390721968 sectors: LBA48
> > > ata1: dev 0 configured for UDMA/133
> > > scsi0 : ata_piix
> > > ATA: abnormal status 0x7F on port 0xC807
> > > scsi1 : ata_piix
> > > Vendor: ATA Model: ST3200822AS Rev: 3.01
> > > Type: Direct-Access ANSI SCSI revision: 05
> > > SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
> > > SCSI device sda: drive cache: write back
> > > SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
> > > SCSI device sda: drive cache: write back
> > > sda: sda1 sda2 sda3
> > > sd 0:0:0:0: Attached scsi disk sda
> > >
> > > I would have to double check, but I think it even missed the USB keyboard.
> > >
> >
> > Is this still happening?
>
> Yes. I have just tried with 2.6.16-rc1-mm2, and the result is the same.
> No root device.
>
> The nosmp-booted kernel looks much much slow than the SMP one, it takes
> ages to detect devices like usb ones, and even spent about 20 seconds here:
>
> [ 0.431601] libata version 1.20 loaded.
> [ 0.431652] ata_piix 0000:00:1f.2: version 1.05
> [ 0.431670] ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 16
> [ 0.431792] PCI: Setting latency timer of device 0000:00:1f.2 to 64
> [ 0.431852] ata1: SATA max UDMA/133 cmd 0xC000 ctl 0xC402 bmdma 0xD000 irq 16
> [ 0.431950] ata2: SATA max UDMA/133 cmd 0xC800 ctl 0xCC02 bmdma 0xD008 irq 16
> >>>>>>>>>>>>> here <<<<<<<<<<<<<<<<<<
> [ 0.690451] ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:407f
> [ 0.690456] ata1: dev 0 ATA-6, max UDMA/133, 390721968 sectors: LBA48
> [ 0.696278] ata1: dev 0 configured for UDMA/133
> [ 0.701627] scsi0 : ata_piix
> [ 1.937443] scsi1 : ata_piix
>
> and it did not detect any drive, so the no-root-device error. This one can be
> a detection timeout, but as I say also the USB detection is dog slooow.
>
> Need some info ? .config, or the like ?
Hi,
I've been testing this also. I also see the problem.
I don't yet know what to do about it, but it's easy to
reproduce. I'll continue to look at it.
For a temporary workaround, booting with "irqpoll" might help,
but that's not the real solution IMO.
---
~Randy
I think nosmp has been broken for a long time:
http://bugzilla.kernel.org/show_bug.cgi?id=1641
try maxcpus=1 instead of nosmp.
-Len
On Sun, 22 Jan 2006 16:47:24 -0500 Brown, Len wrote:
> I think nosmp has been broken for a long time:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=1641
>
> try maxcpus=1 instead of nosmp.
Yes, I know that it's not recent.
Thanks for the bugz #. I had already searched for that
but didn't find it.
---
~Randy