2.6.15-rc5-mm2
Subsystems (4)
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
Quoted 9 lines · Andrew Morton
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
arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c +0 -4
@@ -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 );
Quoted 9 lines · Andrew Morton
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.
Quoted 1 line
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
[17179569.184000] Linux version 2.6.15-rc5-mm2-casaverde (tonfa@casaverde) (gcc version 4.0.2 (Gentoo 4.0.2-r1, pie-8.7.8)) #6 Sun Dec 11 16:02:01 CET 2005 [17179569.184000] BIOS-provided physical RAM map: [17179569.184000] BIOS-e820: 0000000000000000 - 000000000009f000 (usable) [17179569.184000] BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved) [17179569.184000] BIOS-e820: 0000000000100000 - 000000001ffae000 (usable) [17179569.184000] BIOS-e820: 000000001ffae000 - 0000000020000000 (reserved) [17179569.184000] BIOS-e820: 00000000feda0000 - 00000000fee00000 (reserved) [17179569.184000] BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved) [17179569.184000] 511MB LOWMEM available. [17179569.184000] On node 0 totalpages: 130990 [17179569.184000] DMA zone: 4096 pages, LIFO batch:0 [17179569.184000] DMA32 zone: 0 pages, LIFO batch:0 [17179569.184000] Normal zone: 126894 pages, LIFO batch:31 [17179569.184000] HighMem zone: 0 pages, LIFO batch:0 [17179569.184000] DMI 2.3 present. [17179569.184000] ACPI: RSDP (v000 DELL ) @ 0x000fdf00 [17179569.184000] ACPI: RSDT (v001 DELL CPi R 0x27d5011a ASL 0x00000061) @ 0x1fff0000 [17179569.184000] ACPI: FADT (v001 DELL CPi R 0x27d5011a ASL 0x00000061) @ 0x1fff0400 [17179569.184000] ACPI: ASF! (v016 DELL CPi R 0x27d5011a ASL 0x00000061) @ 0x1fff0800 [17179569.184000] ACPI: DSDT (v001 INT430 SYSFexxx 0x00001001 MSFT 0x0100000e) @ 0x00000000 [17179569.184000] Allocating PCI resources starting at 30000000 (gap: 20000000:deda0000) [17179569.184000] Built 1 zonelists [17179569.184000] Local APIC disabled by BIOS -- you can enable it with "lapic" [17179569.184000] mapped APIC to ffffd000 (01401000) [17179569.184000] Enabling fast FPU save and restore... done. [17179569.184000] Enabling unmasked SIMD FPU exception support... done. [17179569.184000] Initializing CPU#0 [17179569.184000] Kernel command line: root=/dev/hda5 video=vesa:mtrr vga=0x317 resume=/dev/hda3 [17179569.184000] CPU 0 irqstacks, hard=c03f9000 soft=c03f8000 [17179569.184000] PID hash table entries: 2048 (order: 11, 32768 bytes) [ 0.000000] Detected 1598.905 MHz processor. [ 6.713094] Using tsc for high-res timesource [ 6.713130] Console: colour dummy device 80x25 [ 6.713822] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 6.714589] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 6.728683] Memory: 515208k/523960k available (2163k kernel code, 8228k reserved, 671k data, 180k init, 0k highmem) [ 6.728696] Checking if this processor honours the WP bit even in supervisor mode... Ok. [ 6.805330] Calibrating delay using timer specific routine.. 3201.11 BogoMIPS (lpj=6402220) [ 6.805370] Mount-cache hash table entries: 512 [ 6.805468] CPU: After generic identify, caps: afe9f9bf 00000000 00000000 00000000 00000180 00000000 00000000 [ 6.805477] CPU: After vendor identify, caps: afe9f9bf 00000000 00000000 00000000 00000180 00000000 00000000 [ 6.805486] CPU: L1 I cache: 32K, L1 D cache: 32K [ 6.805491] CPU: L2 cache: 2048K [ 6.805495] CPU: After all inits, caps: afe9f9bf 00000000 00000000 00000040 00000180 00000000 00000000 [ 6.805501] Intel machine check architecture supported. [ 6.805507] Intel machine check reporting enabled on CPU#0. [ 6.805517] mtrr: v2.0 (20020519) [ 6.805524] CPU: Intel(R) Pentium(R) M processor 1.60GHz stepping 06 [ 6.805531] Checking 'hlt' instruction... OK. [ 6.834114] ACPI: setting ELCR to 0200 (from 0800) [ 6.836912] NET: Registered protocol family 16 [ 6.836936] ACPI: bus type pci registered [ 6.836944] PCI: Using configuration type 1 [ 6.837285] ACPI: Subsystem revision 20050916 [ 6.853055] ACPI: Interpreter enabled [ 6.853060] ACPI: Using PIC for interrupt routing [ 6.854270] ACPI: PCI Root Bridge [PCI0] (0000:00) [ 6.854398] ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 [ 6.864947] PCI quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO [ 6.864954] PCI quirk: region 0880-08bf claimed by ICH4 GPIO [ 6.865000] PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 [ 6.865111] Boot video device is 0000:01:00.0 [ 6.865355] PCI: Transparent bridge - 0000:00:1e.0 [ 6.865413] PCI: Bus #03 (-#06) may be hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses') [ 6.865450] PCI: Bus #07 (-#0a) may be hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses') [ 6.865468] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ 6.887855] ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 *11) [ 6.888096] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *11 [ 6.888335] ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 *11) [ 6.888573] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 9 10 *11) [ 6.888804] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. [ 6.889048] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) [ 6.890187] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT] [ 6.890890] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIE._PRT] [ 6.891846] Linux Plug and Play Support v0.97 (c) Adam Belay [ 6.891856] pnp: PnP ACPI init [ 6.920566] pnp: PnP ACPI: found 13 devices [ 6.920611] Generic PHY: Registered new driver [ 6.920701] SCSI subsystem initialized [ 6.920731] PCI: Using ACPI for IRQ routing [ 6.920735] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report [ 6.925838] pnp: 00:02: ioport range 0x4d0-0x4d1 has been reserved [ 6.925844] pnp: 00:02: ioport range 0x800-0x805 could not be reserved [ 6.925849] pnp: 00:02: ioport range 0x808-0x80f could not be reserved [ 6.925855] pnp: 00:03: ioport range 0xf400-0xf4fe has been reserved [ 6.925860] pnp: 00:03: ioport range 0x806-0x807 has been reserved [ 6.925864] pnp: 00:03: ioport range 0x810-0x85f could not be reserved [ 6.925869] pnp: 00:03: ioport range 0x860-0x87f has been reserved [ 6.925873] pnp: 00:03: ioport range 0x880-0x8bf has been reserved [ 6.925878] pnp: 00:03: ioport range 0x8c0-0x8df has been reserved [ 6.925885] pnp: 00:08: ioport range 0x900-0x97f has been reserved [ 6.926055] PCI: Bridge: 0000:00:01.0 [ 6.926059] IO window: c000-cfff [ 6.926064] MEM window: fc000000-fdffffff [ 6.926069] PREFETCH window: e8000000-efffffff [ 6.926084] PCI: Bus 3, cardbus bridge: 0000:02:01.0 [ 6.926088] IO window: 0000d000-0000d0ff [ 6.926093] IO window: 0000d400-0000d4ff [ 6.926099] PREFETCH window: 30000000-31ffffff [ 6.926104] MEM window: f6000000-f7ffffff [ 6.926110] PCI: Bus 7, cardbus bridge: 0000:02:01.1 [ 6.926113] IO window: 0000d800-0000d8ff [ 6.926118] IO window: 0000dc00-0000dcff [ 6.926124] PREFETCH window: 32000000-33ffffff [ 6.926129] MEM window: f8000000-f9ffffff [ 6.926134] PCI: Bridge: 0000:00:1e.0 [ 6.926138] IO window: d000-efff [ 6.926145] MEM window: f6000000-fbffffff [ 6.926150] PREFETCH window: 30000000-33ffffff [ 6.926167] PCI: Setting latency timer of device 0000:00:1e.0 to 64 [ 6.926179] PCI: Enabling device 0000:02:01.0 (0000 -> 0003) [ 6.926354] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 [ 6.926359] PCI: setting IRQ 11 as level-triggered [ 6.926362] ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 [ 6.926381] PCI: Enabling device 0000:02:01.1 (0000 -> 0003) [ 6.926386] ACPI: PCI Interrupt 0000:02:01.1[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 [ 6.926882] Initializing Cryptographic API [ 6.926888] io scheduler noop registered [ 6.926894] io scheduler anticipatory registered [ 6.926900] io scheduler deadline registered [ 6.926910] io scheduler cfq registered [ 6.927194] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 [ 6.927199] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 [ 6.927238] radeonfb: Retreived PLL infos from BIOS [ 6.927243] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=220.00 Mhz, System=200.00 MHz [ 6.927249] radeonfb: PLL min 20000 max 35000 [ 7.860497] Non-DDC laptop panel detected [ 8.796754] radeonfb: Monitor 1 type LCD found [ 8.796758] radeonfb: Monitor 2 type no found [ 8.796763] radeonfb: panel ID string: 6J5644141XB [ 8.796764] [ 8.796769] radeonfb: detected LVDS panel size from BIOS: 1024x768 [ 8.796772] radeondb: BIOS provided dividers will be used [ 8.915659] radeonfb: Dynamic Clock Power Management enabled [ 8.945498] Console: switching to colour frame buffer device 128x48 [ 8.946600] radeonfb (0000:01:00.0): ATI Radeon Lf [ 8.946793] vesafb: cannot reserve video memory at 0xe8000000 [ 8.946871] vesafb: framebuffer at 0xe8000000, mapped to 0xe1900000, using 3072k, total 32704k [ 8.946969] vesafb: mode is 1024x768x16, linelength=2048, pages=20 [ 8.947046] vesafb: protected mode interface info at c000:57f3 [ 8.947118] vesafb: scrolling: redraw [ 8.947168] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0 [ 8.947278] fb1: VESA VGA frame buffer device [ 8.961426] Real Time Clock Driver v1.12 [ 8.961501] Linux agpgart interface v0.101 (c) Dave Jones [ 8.961608] agpgart: Detected an Intel 855PM Chipset. [ 8.970229] agpgart: AGP aperture is 128M @ 0xe0000000 [ 8.970403] PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 [ 8.973898] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 8.974274] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 8.974414] mice: PS/2 mouse device common for all mice [ 8.984069] input: AT Translated Set 2 keyboard as /class/input/input0 [ 11.985230] floppy0: no floppy controllers found [ 11.988931] RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize [ 11.992550] loop: loaded (max 8 devices) [ 11.996058] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 [ 11.999501] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx [ 12.003017] ICH4: IDE controller at PCI slot 0000:00:1f.1 [ 12.006545] PCI: Enabling device 0000:00:1f.1 (0005 -> 0007) [ 12.010126] ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 [ 12.013893] ICH4: chipset revision 1 [ 12.017694] ICH4: not 100% native mode: will probe irqs later [ 12.021521] ide0: BM-DMA at 0xbfa0-0xbfa7, BIOS settings: hda:DMA, hdb:pio [ 12.025413] ide1: BM-DMA at 0xbfa8-0xbfaf, BIOS settings: hdc:DMA, hdd:pio [ 12.029192] Probing IDE interface ide0... [ 12.317121] hda: TOSHIBA MK4026GAX, ATA DISK drive [ 12.988502] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [ 12.992260] Probing IDE interface ide1... [ 13.728003] hdc: SAMSUNG CDRW/DVD SN-324S, ATAPI CD/DVD-ROM drive [ 14.399870] ide1 at 0x170-0x177,0x376 on irq 15 [ 14.404008] hda: max request size: 128KiB [ 14.456566] hda: 78140160 sectors (40007 MB), CHS=65535/16/63, UDMA(100) [ 14.460475] hda: cache flushes supported [ 14.464332] hda: hda1 hda2 hda3 hda4 < hda5 hda6 > [ 14.501940] i2c /dev entries driver [ 14.505928] NET: Registered protocol family 2 [ 14.543243] IP route cache hash table entries: 8192 (order: 3, 32768 bytes) [ 14.547243] TCP established hash table entries: 32768 (order: 5, 131072 bytes) [ 14.551241] TCP bind hash table entries: 32768 (order: 5, 131072 bytes) [ 14.555226] TCP: Hash tables configured (established 32768 bind 32768) [ 14.559059] TCP reno registered [ 14.562957] TCP bic registered [ 14.566700] NET: Registered protocol family 1 [ 14.570395] NET: Registered protocol family 17 [ 14.574054] Using IPI Shortcut mode [ 14.591704] ACPI wakeup devices: [ 14.595332] LID PBTN PCI0 USB0 USB1 USB2 USB3 MODM PCIE [ 14.599184] ACPI: (supports S0 S1 S3 S4 S5) [ 14.613136] ReiserFS: hda5: found reiserfs format "3.6" with standard journal [ 15.476013] ReiserFS: hda5: using ordered data mode [ 15.493521] ReiserFS: hda5: journal params: device hda5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [ 15.501949] ReiserFS: hda5: checking transaction log (hda5) [ 15.591446] ReiserFS: hda5: Using r5 hash to sort names [ 15.595520] VFS: Mounted root (reiserfs filesystem) readonly. [ 15.599704] Freeing unused kernel memory: 180k freed [ 15.603736] Write protecting the kernel read-only data: 304k [ 19.433898] Adding 979956k swap on /dev/hda3. Priority:-1 extents:1 across:979956k [ 20.629124] hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33) [ 20.629133] Uniform CD-ROM driver Revision: 3.20 [ 20.802001] ieee80211_crypt: registered algorithm 'NULL' [ 20.842859] ieee80211: 802.11 data/management/control stack, git-1.1.7 [ 20.842864] ieee80211: Copyright (C) 2004-2005 Intel Corporation <[email protected]> [ 20.908616] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.0.8 [ 20.908621] ipw2200: Copyright(c) 2003-2005 Intel Corporation [ 20.908939] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5 [ 20.908943] PCI: setting IRQ 5 as level-triggered [ 20.908946] ACPI: PCI Interrupt 0000:02:03.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5 [ 20.909760] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection [ 21.249384] tg3.c:v3.44 (Dec 6, 2005) [ 21.249649] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 [ 21.249653] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 [ 21.279578] eth0: Tigon3 [partno(BCM95705A50) rev 3001 PHY(5705)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet 00:0f:1f:ca:d7:a8 [ 21.279585] eth0: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[1] [ 21.279588] eth0: dma_rwctrl[763f0000] [ 21.421797] input: DualPoint Stick as /class/input/input1 [ 21.444635] input: AlpsPS/2 ALPS DualPoint TouchPad as /class/input/input2 [ 21.609241] usbcore: registered new driver usbfs [ 21.609266] usbcore: registered new driver hub [ 21.741786] ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11 [ 21.741792] ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNKH] -> GSI 11 (level, low) -> IRQ 11 [ 21.741807] PCI: Setting latency timer of device 0000:00:1d.7 to 64 [ 21.741811] ehci_hcd 0000:00:1d.7: EHCI Host Controller [ 21.741840] ehci_hcd 0000:00:1d.7: debug port 1 [ 21.741850] PCI: cache line size of 32 is not supported by device 0000:00:1d.7 [ 21.742080] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1 [ 21.742089] ehci_hcd 0000:00:1d.7: irq 11, io mem 0xf4fffc00 [ 21.745966] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 [ 21.746026] usb usb1: configuration #1 chosen from 1 choice [ 21.746049] hub 1-0:1.0: USB hub found [ 21.746055] hub 1-0:1.0: 6 ports detected [ 21.944599] USB Universal Host Controller Interface driver v2.3 [ 21.944651] ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 [ 21.944664] PCI: Setting latency timer of device 0000:00:1d.0 to 64 [ 21.944668] uhci_hcd 0000:00:1d.0: UHCI Host Controller [ 21.944712] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2 [ 21.944722] uhci_hcd 0000:00:1d.0: irq 11, io base 0x0000bf80 [ 21.944799] usb usb2: configuration #1 chosen from 1 choice [ 21.944824] hub 2-0:1.0: USB hub found [ 21.944831] hub 2-0:1.0: 2 ports detected [ 22.045347] ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 [ 22.045361] PCI: Setting latency timer of device 0000:00:1d.1 to 64 [ 22.045366] uhci_hcd 0000:00:1d.1: UHCI Host Controller [ 22.045399] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3 [ 22.045408] uhci_hcd 0000:00:1d.1: irq 11, io base 0x0000bf40 [ 22.045477] usb usb3: configuration #1 chosen from 1 choice [ 22.045497] hub 3-0:1.0: USB hub found [ 22.045503] hub 3-0:1.0: 2 ports detected [ 22.149260] ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 [ 22.149273] PCI: Setting latency timer of device 0000:00:1d.2 to 64 [ 22.149277] uhci_hcd 0000:00:1d.2: UHCI Host Controller [ 22.149314] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4 [ 22.149322] uhci_hcd 0000:00:1d.2: irq 11, io base 0x0000bf20 [ 22.149386] usb usb4: configuration #1 chosen from 1 choice [ 22.149406] hub 4-0:1.0: USB hub found [ 22.149412] hub 4-0:1.0: 2 ports detected [ 22.374690] ACPI: AC Adapter [AC] (on-line) [ 22.964591] ACPI: Battery Slot [BAT0] (battery present) [ 22.964664] ACPI: Battery Slot [BAT1] (battery absent) [ 23.247501] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3] C4[C3]) [ 23.247508] ACPI: Processor [CPU0] (supports 8 throttling states) [ 23.271434] ACPI: Thermal Zone [THM] (43 C) [ 23.284975] ACPI: Lid Switch [LID] [ 23.284984] ACPI: Power Button (CM) [PBTN] [ 23.284992] ACPI: Sleep Button (CM) [SBTN] [ 31.396382] kjournald starting. Commit interval 5 seconds [ 31.396393] EXT3-fs: mounted filesystem with ordered data mode. [ 31.424636] ReiserFS: hda6: found reiserfs format "3.6" with standard journal [ 34.132210] ReiserFS: hda6: using ordered data mode [ 34.157151] ReiserFS: hda6: journal params: device hda6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [ 34.157613] ReiserFS: hda6: checking transaction log (hda6) [ 34.200573] ReiserFS: hda6: Using r5 hash to sort names [ 40.644815] ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5 [ 40.644841] PCI: Setting latency timer of device 0000:00:1f.5 to 64 [ 41.411602] intel8x0_measure_ac97_clock: measured 55471 usecs [ 41.411606] intel8x0: clocking to 48000 [ 43.298413] Netfilter messages via NETLINK v0.30. [ 43.385586] ip_conntrack version 2.4 (4093 buckets, 32744 max) - 216 bytes per conntrack [ 43.550112] ip_tables: (C) 2000-2002 Netfilter core team [ 44.384419] hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error } [ 44.384428] hdc: drive_cmd: error=0x04 { AbortedCommand } [ 44.384431] ide: failed opcode was: 0xec [ 44.392275] hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error } [ 44.392282] hdc: drive_cmd: error=0x04 { AbortedCommand } [ 44.392285] ide: failed opcode was: 0xec [ 44.400036] hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error } [ 44.400044] hdc: drive_cmd: error=0x04 { AbortedCommand } [ 44.400046] ide: failed opcode was: 0xec [ 52.066446] [drm] Initialized drm 1.0.1 20051102 [ 52.094409] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 [ 52.096030] [drm] Initialized radeon 1.19.0 20050911 on minor 0 [ 52.096903] mtrr: 0xe8000000,0x8000000 overlaps existing 0xe8000000,0x2000000 [ 52.097333] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. [ 52.097344] agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode [ 52.097370] agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode [ 52.159038] [drm] Loading R200 Microcode [ 99.194572] mtrr: 0xe8000000,0x8000000 overlaps existing 0xe8000000,0x2000000 [ 99.194736] mtrr: 0xe8000000,0x8000000 overlaps existing 0xe8000000,0x2000000 [ 99.194794] mtrr: 0xe8000000,0x8000000 overlaps existing 0xe8000000,0x2000000 [ 99.195065] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. [ 99.195080] agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode [ 99.195107] agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode [ 99.199658] [drm] Loading R200 Microcode [ 315.282095] mtrr: 0xe8000000,0x8000000 overlaps existing 0xe8000000,0x2000000 [ 315.282315] mtrr: 0xe8000000,0x8000000 overlaps existing 0xe8000000,0x2000000 [ 315.282428] mtrr: 0xe8000000,0x8000000 overlaps existing 0xe8000000,0x2000000 [ 315.283177] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. [ 315.283201] agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode [ 315.283237] agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode [ 315.290306] [drm] Loading R200 Microcode
Hi,
Quoted 1 line · Andrew Morton
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
Re: 2.6.15-rc5-mm2: broken resume from disk on x86-64
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.
arch/x86_64/kernel/time.c | 9 +++++++++ 1 files changed, 9 insertions(+)
arch/x86_64/kernel/time.c +9 -0
@@ -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 irdtscll_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);
Re: 2.6.15-rc5-mm2: evdev problem
In reply to Rafael J. WysockiThe 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.
drivers/input/evdev.c +3 -3
@@ -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 ; }
Re: 2.6.15-rc5-mm2: evdev problem
Quoted 3 lines · Rafael J. Wysocki
The evdev driver is still broken due to the wrong order of arguments of
copy_to_user()inevdev_event_to_user().
I added the correct version to my tree so next time Andrew pulls from -mm it will be there.
Signature · 1 line
Dmitry
Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
In reply to Rafael J. WysockiThe ehci_hcd driver causes problems like this:
ehci_hcd 0000:00:02.2: EHCI Host Controllerehci_hcd 0000:00:02.2: debug port 1ehci_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 choiceehci_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 8bRIP <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.
Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
Quoted 11 lines · Rafael J. Wysocki
The
ehci_hcddriver causes problems like this:
ehci_hcd0000:00:02.2: EHCI Host Controllerehci_hcd0000:00:02.2: debug port 1ehci_hcd0000:00:02.2: new USB bus registered, assigned bus number 3ehci_hcd0000:00:02.2: irq 5, io mem0xfebfdc00
usb 2-2: Product: USB Receiver
usb 2-2: Manufacturer: Logitech
usb 2-2: configuration #1 chosen from 1 choiceehci_hcd0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
Quoted 2 lines
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?
Quoted 41 lines
PGD
2dba6067PUD2d477067PMD 0Oops: 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 8bRIP <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.
Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
Quoted 15 lines · Andrew Morton
Quoted 11 lines · Rafael J. Wysocki
The
ehci_hcddriver causes problems like this:
ehci_hcd0000:00:02.2: EHCI Host Controllerehci_hcd0000:00:02.2: debug port 1ehci_hcd0000:00:02.2: new USB bus registered, assigned bus number 3ehci_hcd0000:00:02.2: irq 5, io mem0xfebfdc00
usb 2-2: Product: USB Receiver
usb 2-2: Manufacturer: Logitech
usb 2-2: configuration #1 chosen from 1 choiceehci_hcd0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004Quoted 2 lines
Unable to handle kernel NULL pointer dereference at 00000000000002a4 RIP:<ffffffff880ad9d0>{:ehci_hcd:ehci_irq+224}
Quoted 1 line
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>.
Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
Quoted 17 lines · Rafael J. Wysocki
Quoted 15 lines · Andrew Morton
Quoted 13 lines · Rafael J. Wysocki
The
ehci_hcddriver causes problems like this:
ehci_hcd0000:00:02.2: EHCI Host Controllerehci_hcd0000:00:02.2: debug port 1ehci_hcd0000:00:02.2: new USB bus registered, assigned bus number 3ehci_hcd0000:00:02.2: irq 5, io mem0xfebfdc00
usb 2-2: Product: USB Receiver
usb 2-2: Manufacturer: Logitech
usb 2-2: configuration #1 chosen from 1 choiceehci_hcd0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004Unable to handle kernel NULL pointer dereference at 00000000000002a4 RIP:<ffffffff880ad9d0>{:ehci_hcd:ehci_irq+224}
Quoted 6 lines
Quoted 1 line
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 address0x69c3<ehci_irq+211>
and ends at0x69e2<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..
Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
Quoted 20 lines · Andrew Morton
Quoted 19 lines · Rafael J. Wysocki
Quoted 16 lines · Andrew Morton
Quoted 11 lines · Rafael J. Wysocki
The
ehci_hcddriver causes problems like this:
ehci_hcd0000:00:02.2: EHCI Host Controllerehci_hcd0000:00:02.2: debug port 1ehci_hcd0000:00:02.2: new USB bus registered, assigned bus number 3ehci_hcd0000:00:02.2: irq 5, io mem0xfebfdc00
usb 2-2: Product: USB Receiver
usb 2-2: Manufacturer: Logitech
usb 2-2: configuration #1 chosen from 1 choiceehci_hcd0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004Quoted 2 lines
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?
Quoted 8 lines
Quoted 4 lines
It looks like at the line 620. At least here's what gdb told me:
Line 620 of "
ehci-hcd.c" starts at address0x69c3<ehci_irq+211>
and ends at0x69e2<ehci_irq+242>.On my tree that's
if ((status & STS_PCD) && device_may_wakeup(&hcd->self.root_hub->dev)) {
Yes, that's it.
Quoted 5 lines
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 thenl *0xffffffff880ad9d0'.
Does it work for modules too?
Quoted 5 lines
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 ...
Signature · 1 line
Beer is proof that God loves us and wants us to be happy - Benjamin Franklin
Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
Quoted 8 lines · Rafael J. Wysocki
Quoted 6 lines
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 thenl *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.
Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
Quoted 8 lines · Andrew Morton
Quoted 7 lines · Rafael J. Wysocki
Quoted 6 lines
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 thenl *0xffffffff880ad9d0'.
Quoted 7 lines
Quoted 1 line
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.
Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
Quoted 27 lines · Rafael J. Wysocki
Quoted 8 lines · Andrew Morton
Quoted 7 lines · Rafael J. Wysocki
Quoted 6 lines
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 thenl *0xffffffff880ad9d0'.Quoted 7 lines
Quoted 1 line
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:
Quoted 8 lines
gdb
drivers/usb/host/ehci-hcd.oIn gdb I did:
info line
ehci_irqand 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.
Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
In reply to Rafael J. WysockiQuoted 4 lines · Rafael J. Wysocki
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:
Quoted 8 lines
gdb
drivers/usb/host/ehci-hcd.oIn gdb I did:
info line
ehci_irqand it told me the address the line started at, so I added 224 to it and got the line 620.
You can do the arithmetic yourself like that, but it's easier to just type
info line *ehci_irq+224
and let gdb do it for you.
Signature · 3 lines
Ben Pfaff email: [email protected] web: http://benpfaff.org
Re: [linux-usb-devel] Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
In reply to Andrew MortonQuoted 2 lines
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
Re: [linux-usb-devel] Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
Quoted 8 lines · David Brownell
Quoted 2 lines
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
Re: [linux-usb-devel] Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
Quoted 4 lines · Rafael J. Wysocki
Quoted 3 lines · David Brownell
Quoted 2 lines
if ((status & STS_PCD) && device_may_wakeup(&hcd->self.root_hub->dev)) {
Quoted 8 lines
Quoted 5 lines
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
Re: [linux-usb-devel] Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
Quoted 9 lines · David Brownell
Quoted 8 lines · Rafael J. Wysocki
Quoted 7 lines · David Brownell
Quoted 2 lines
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) {
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
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
Re: [linux-usb-devel] Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 7 lines
Quoted 1 line
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?
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
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
Quoted 2 lines · Andrew Morton
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
Quoted 1 line
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
PATCH 1/1 Fix vesafb display panning regression
Fix vesafb hang when scroll mode is REDRAW.
---
Quoted 13 lines · Jesper Juhl
Quoted 2 lines · Andrew Morton
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(-)
drivers/video/vesafb.c +3 -0
@@ -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;
Re: [PATCH] Fix vesafb display panning regression
Quoted 20 lines · Antonino A. Daplas
Fix vesafb hang when scroll mode is REDRAW.
Signed-off-by Antonino Daplas <[email protected]>---
Quoted 13 lines · Jesper Juhl
Quoted 2 lines · Andrew Morton
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.
Quoted 1 line
Sorry about that.
No problem, it happens :)
Quoted 3 lines
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
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
Re: 2.6.15-rc5-mm2 :-)
In reply to Andrew MortonHello Andrew,
Quoted 1 line · you
- 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?
Signature · 2 lines
Best regards, Maciej
Re: 2.6.15-rc5-mm2 :-)
Quoted 11 lines · Maciej Soltysiak
Hello Andrew,
Quoted 1 line · you
- 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_BATCHrelies 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
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: 2.6.15-rc5-mm2 :-)
Quoted 9 lines · Maciej Soltysiak
Hello Con,
Quoted 5 lines · you
I missed this announcement (been on leave for a while). This
SCHED_BATCHimplementation 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.
Quoted 5 lines
Thanks a lot. That's good anyway.
If I understand correctly, if Ingo's version gets merged with linus' tree your implementions of
SCHED_BATCHin -ck will be replacing the one from Ingo.
Yes. SCHED_BATCH in Ingo's implementation is more like turning off the interactive setting in staircase, and the idle scheduling staircase offers is extremely useful.
Quoted 3 lines
A silly question. Is SCHED_BATCH-kind-of-thing a standard in Unices or general operating system engineering know-how? Or is this concept only available for Linux?
Fairly standard in Unices but prone to all sorts of priority inversion starvation scenarios so very few implement it. In freebsd for example you can use their idle scheduling only if you are root to prevent this starvation - which kind of makes it useless in practice. My implementation is fairly robust at avoiding the priority inversion problem - at least I haven't seen a bug report about it for years since I address it :)
Cheers,
Con
Re: 2.6.15-rc5-mm2 :-)
Quoted 22 lines · Con Kolivas
Quoted 10 lines · Maciej Soltysiak
Hello Con,
Quoted 5 lines · you
I missed this announcement (been on leave for a while). This
SCHED_BATCHimplementation 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.Quoted 5 lines
Thanks a lot. That's good anyway.
If I understand correctly, if Ingo's version gets merged with linus' tree your implementions of
SCHED_BATCHin -ck will be replacing the one from Ingo.Yes.
SCHED_BATCHin Ingo's implementation is more like turning off the interactive setting in staircase, and the idle scheduling staircase offers is extremely useful.
Quoted 7 lines
Quoted 3 lines
A silly question. Is SCHED_BATCH-kind-of-thing a standard in Unices or general operating system engineering know-how? Or is this concept only available for Linux?
Fairly standard in Unices but prone to all sorts of priority inversion starvation scenarios so very few implement it. In freebsd for example you can use their idle scheduling only if you are root to prevent this starvation - which kind of makes it useless in practice. My implementation is fairly robust at avoiding the priority inversion problem - at least I haven't seen a bug report about it for years since I address it :)
FYI, the 6.1.6 version of PlugSched for 2.6.15-rc5-mm2 that I announced yesterday applies the same SCHED_BATCH semantics as Ingo's patch to the ingosched, nicksched, zaphod and spa_ws schedulers (i.e. it suppresses interactive bonuses for tasks in the SCHED_BATCH policy class). As spa_no_frills and spa_svr do not have interactive bonuses there is no change to their semantics. The staircase scheduler in PlugSched will be updated to the same SCHED_BATCH as the stand alone version in due course.
Peter
Signature · 4 lines
Peter Williams [email protected] "Learning, n. The kind of ignorance distinguishing the studious." -- Ambrose Bierce
2.6.15-rc5-mm2: two cs5535 modules
In reply to Andrew MortonQuoted 7 lines · Andrew Morton
...
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
Signature · 4 lines
"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 Seed2.6.15-rc5-mm2: two cs5535 modules
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
Quoted 26 lines · Adrian Bunk
Quoted 7 lines · Andrew Morton
...
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 underdrivers/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
Re: 2.6.15-rc5-mm2: two cs5535 modules
Quoted 6 lines · Ben Gardner
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)
Quoted 2 lines · Andrew Morton
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.
blacklist.c | 7 +++---- css.c | 10 ++++++++++ 2 files changed, 13 insertions(+), 4 deletions(-)
drivers/s390/cio/blacklist.c +3 -4
@@ -299,10 +299,9 @@ cio_ignore_proc_seq_start(struct seq_filif (*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_fileif (*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 ;
drivers/s390/cio/css.c +10 -0
@@ -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); }
SMP+nosmp=hang [was: Re: 2.6.15-rc5-mm2]
In reply to Andrew MortonQuoted 3 lines · Andrew Morton
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))
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: SMP+nosmp=hang [was: Re: 2.6.15-rc5-mm2]
Quoted 33 lines · Andrew Morton
Quoted 32 lines · J.A. Magallon
Quoted 3 lines · Andrew Morton
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_piix0000: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 cmd0xC000ctl0xC402bmdma0xD000irq 16
ata2: SATA max UDMA/133 cmd0xC800ctl0xCC02bmdma0xD008irq 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 status0x7Fon port0xC807
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
Quoted 4 lines
Quoted 2 lines
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))
Re: SMP+nosmp=hang [was: Re: 2.6.15-rc5-mm2]
Quoted 59 lines · On Sun, 22 Jan 2006 00:46:36 +0100 J.A. Magallon wrote:
Quoted 33 lines · Andrew Morton
Quoted 32 lines · J.A. Magallon
Quoted 3 lines · Andrew Morton
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_piix0000: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 cmd0xC000ctl0xC402bmdma0xD000irq 16
ata2: SATA max UDMA/133 cmd0xC800ctl0xCC02bmdma0xD008irq 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 status0x7Fon port0xC807
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 sdaQuoted 4 lines
Quoted 2 lines
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
Quoted 4 lines
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
Hi,
Quoted 7 lines · Andrew Morton
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