2.6.15-rc1-mm1
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc1/2.6.15-rc1-mm1
- reiser4 significantly updated
Changes since 2.6.14-mm2:
linus.patch
git-acpi.patch
git-agpgart.patch
git-arm.patch
git-blktrace.patch
git-block.patch
git-cfq.patch
git-cifs.patch
git-drm.patch
git-ieee1394.patch
git-infiniband.patch
git-libata-all.patch
git-netdev-all.patch
git-ocfs2.patch
git-pcmcia.patch
git-sas.patch
git-cryptodev.patch
Subsystem trees
-work-around-gcc-32x-cpp-bug.patch
-x86_64-fix-tss-limit.patch
-x86_64-two-timer-entries-in-sys.patch -reorder-struct-files_struct.patch
-git-acpi-pciehprm_acpi-fix.patch
-speakup-is-busted-on-pc64.patch
-libatah-needs-dma-mappingh.patch
-sky2-needs-dma_mappingh.patch -serial-dont-disable-xscale-serial-ports-after-autoconfig.patch -gregkh-pci-pci_find_next_capability.patch -gregkh-pci-pci-pciehp-01.patch
-gregkh-pci-pci-pciehp-02.patch
-gregkh-pci-pci-pciehp-03.patch
-gregkh-pci-pci-pciehp-04.patch
-gregkh-pci-pci-pciehp-05.patch
-gregkh-pci-pci-pciehp-06.patch
-gregkh-pci-pci-pciehp-07.patch
-gregkh-pci-pci-pciehp-08.patch -gregkh-pci-pci-via-686-quirk-name-fix.patch -gregkh-pci-pci-ncr-53c810-quirk.patch -gregkh-pci-pci-driver-store_new_id-not-inline.patch -gregkh-pci-pci_driver_auto_set_owner.patch -gregkh-pci-pci-driver-owner-removal.patch -gregkh-pci-dlpar-regression-for-ppc64-probe-change.patch -gregkh-pci-pci_ids-cleanup-fix-two-additional-ids-in-bt87x.patch -gregkh-pci-pci-drivers-pci-small-cleanups.patch -gregkh-pci-pci-changing-msi-to-use-physical-delivery-mode-always.patch -gregkh-pci-pci-fix-namespace-clashes.patch -gregkh-pci-pci-fix-for-toshiba-ohci1394-quirk.patch -gregkh-pci-pci-driver-owner-removal-fix-lpfc.patch -gregkh-pci-pci-driver-owner-removal-fix-spider_net.patch -pciehp_hpc-build-fix.patch
-shpchp_hpc-build-fix.patch -kill-libata-scsi_wait_req-usage-make-libata-compile-in.patch -display7seg-build-fix.patch
-gregkh-usb-usb-pxa27x-update-01.patch -gregkh-usb-usb-pxa27x-update-02.patch -gregkh-usb-add-new-wacom-devices-to-usb-hid-core-list.patch -gregkh-usb-usb-wacom-tablet-driver-update.patch -gregkh-usb-usb-onetouch-doesn-t-suspend-yet.patch -x86_64-defconfig-update.patch
-x86_64-dma32.patch
-x86_64-dma32-ia64-compat.patch
-x86_64-dma32-srat32.patch
-x86_64-pagealloc-cpu-up-cancel.patch -x86_64-vm-holes-reserved.patch
-x86_64-hpet-regs.patch
-x86_64-mce-thresh.patch
-x86_64-vect-share.patch
-x86_64-pfn-valid-comment.patch
-x86_64-page-flags-cleanup.patch
-x86_64-dma32-iommu.patch
-x86_64-cpuinit-duplicate.patch -x86_64-extend-model-for-family6.patch
-x86_64-aper-warn.patch
-x86_64-faster-numa-node-id.patch
-x86_64-zap-low.patch
-x86_64-physical-mask.patch
-x86_64-sections-include.patch
-x86_64-pda-extern.patch
-x86_64-swiotlb-extern.patch
-x86_64-mm-clarification.patch
-x86_64-largespinlock.patch
-x86_64-hotplug-cpus.patch
-x86_64-signal-code-segment.patch
-x86_64-numa-hash-opt.patch
-x86_64-agp-new-bridges.patch
-x86_64-agp-amd64-unsupported.patch
-x86_64-agp-gart-iterator.patch
-x86_64-intel-cpuid-fixup.patch
-x86_64-aout-module.patch
-x86_64-process-indent.patch
-x86_64-reboot-irq.patch
-x86_64-numa-hash-debug.patch
-x86_64-intel-multi-core.patch
-x86_64-intel-cache.patch
-x86_64-reboot-loop.patch
-x86_64-remove-stepping-b-opts.patch
-x86_64-remove-rwsem.patch
-x86_64-max-alignment.patch
-x86_64-time64.patch
-x86_64-numa-kconfig.patch
-x86_64-mce-intel.patch
-x86_64-node-range.patch
-x86_64-remove-checking.patch
-x86_64-max-apics.patch
-x86_64-sparse-fix.patch
-dma32-change-zones_shift-back-to-2.patch -dma32-change-zones_shift-back-to-2-gfp_zonemask-too.patch -mm-__gfp_nofail-fix.patch
-mm-zap_block-causes-redundant-work.patch -mm-zap_block-causes-redundant-work-warning-fix.patch -mm-__alloc_pages-cleanup.patch
-mm-__alloc_pages-cleanup-tidy.patch
-mm-highmem-watermarks.patch -mm-dont-print-per-cpu-vm-stats-for-offline-cpus.patch -fix-sparse-warning-in-horizon-atm-driver.patch -ppc-add-support-for-new-powerbooks.patch -ppc32-add-support-for-handling-pci-interrupts-on-mpc834x.patch -powerpc-check_for_initrd-fix.patch
-powerpc-xmon-build-fix.patch -arch-i386-mm-initc-small-cleanups.patch -i386-nmi-pointer-comparison-fix.patch -move-pm_register-etc-to-config_pm_legacy-pm_legacyh.patch -m68k-introduce-task_thread_info.patch -m68k-introduce-setup_thread_stack-end_of_stack.patch -m68k-thread_info-header-cleanup.patch -m68k-m68k-specific-thread_info-changes.patch -m68k-convert-thread-flags-to-use-bit-fields.patch -add-stack-field-to-task_struct.patch -rename-allocfree_thread_info-to-allocfree_thread_stack.patch -rename-allocfree_thread_info-to-allocfree_thread_stack-powerpc-fix.patch -use-end_of_stack.patch
-change-thread_info-access-to-stack.patch -use-task_thread_info.patch
-new-omnikey-cardman-4040-driver.patch -new-omnikey-cardman-4000-driver.patch -signal-handling-revert-sigkill-priority-fix.patch -ext3-journal-handling-on-error-path-in-ext3_journalled_writepage.patch -synclink-update-to-use-dma-mapping-api.patch -fix-sparse-warning-in-proc-task_mmuc.patch -shut-up-per_cpu_ptr-on-up.patch -pktcdvd-remove-subscribers-only-list.patch -rcutorture-renice-to-low-priority.patch
-i386-generic-cmpxchg.patch
-i386-generic-cmpxchg-tidy.patch
-atomic-cmpxchg.patch
-atomic-cmpxchg-tidy.patch
-atomic-inc_not_zero.patch
-atomic-inc_not_zero-tidy.patch -arch-mips-au1000-common-usbdevc-dont-concatenate-__function__-with-strings.patch -stop_machine-vs-synchronous-ipi-send-deadlock.patch -aio-remove-kioctx-from-mm_struct.patch -aio-replace-locking-comments-with-assert_spin_locked.patch -aio-dont-ref-kioctx-after-decref-in-put_ioctx.patch -relayfs-add-support-for-non-relay-files.patch -relayfs-documentation-for-non-relay-file-support.patch -relayfs-make-exported-relay-fileops-useful.patch -relayfs-documentation-for-exported-relay-fileops.patch -ext2-remove-duplicate-newlines-in-ext2_fill_super.patch -accth-needs-jiffies-h.patch -hdaps-convert-to-dynamic-input_dev-allocation.patch -v4l-9261-added-compiling-options-for-wm8775-and.patch -v4l-930-alsa-fixes-and-improvements.patch -v4l-943-added-secam-l-video-standard.patch -v4l-935-moved-common-ir-stuff-to-ir-commonc.patch -v4l-936-support-for-sabrent-bt848-version.patch -v4l-937-included-missing-interrupth-at.patch -v4l-939-support-for-nebula-rc5-based-gpio-remote.patch -v4l-944-added-driver-for-saa7127-video.patch -v4l-944-added-driver-for-saa7127-video-tidy.patch -v4l-945-adds-a-new-include-for-internal.patch -v4l-946-adds-support-for-cx25840-video.patch -v4l-949-added-support-for-secam-l.patch -v4l-950-added-compiler-options-for-cx25840-saa7115.patch -v4l-951-make-saa7134-oss-as-a-stand-alone-module.patch -v4l-958-make-cx25840-use-firmware-image-named.patch -v4l-962-added-new-saa7134-card-msi-tv-anywhere.patch -v4l-963-em28xx-ir-fixup.patch -v4l-9631-hybrid-v4l-dvb-remove-duplicated-code.patch -v4l-948-adds-support-for-saa7115-video.patch -v4l-966-authorship-fixes-for-new-modules.patch -v4l-9661-removes-obsoleted-i2c-compath-from.patch -v4l-prevent-saa7134-alsa-undefined-warnings.patch -v4l-saa711x-driver-doesnt-need-segmenth.patch -make-vesafb-build-without-config_mtrr.patch -docbook-allow-to-mark-structure-members-private.patch -docbook-include-printk-documentation.patch -docbook-comment-about-paper-type.patch -docbook-revert-xmlto-use-for-ps-and-pdf-documentation.patch
Merged
+e1000-fix-for-dhcp-issue.patch
e1000 fix
+fix-copy-paste-bug-in-ohci-ppc-socc.patch
ppc driver fix.
+add-success-failure-indication-to-rcu-torture-test.patch
Update to the RCU correctness tests.
+export-clear_page_dirty_for_io.patch
Re-export an ill-advised un-export.
+ipmi-missing-null-test-for-kthread.patch
IPMI fix.
+ppc32-added-missing-define-for-fs_enet-ethernet-driver.patch
ppc32 net driver fix
+tpm-use-flush_scheduled_work.patch
+tpm-use-ioread8-and-iowrite8.patch
TPM driver updates.
+md-dont-pass-null-file-into-prepare_write.patch +md-fix-is_mddev_idle-calculation-now-that-disk-sector-accounting-happens-when-request-completes.patch
md fixes
+cifs-build-fix.patch
Fix git-cifs.patch.
+cpufreq-documentation-for-ondemand-and-conservative.patch +cpufreq-silence-warning-for-up.patch
Cpufreq fixes.
+gregkh-driver-move-pnpbios-usermod_helper.patch
+gregkh-driver-remove-KOBJECT_UEVENT.patch
+gregkh-driver-add-uevent_helper.patch
+gregkh-driver-remove-mount-events.patch
+gregkh-driver-merge-hotplug-and-uevent.patch
Updates to the driver tree.
+gregkh-i2c-hwmon-w83627hf-missing-in0-limit-check.patch +gregkh-i2c-hwmon-lm78-fix-vid.patch
Updates to the i2c tree.
+input-attempt-to-re-synchronize-mouse-every-5-seconds.patch
Try to fix glitches with ps/2 mice and KVMs
+blkmtd-use-clear_page_dirty.patch
blkmtd fixes
+gregkh-pci-pci-trivial-printk-updates-in-common.c.patch +gregkh-pci-pci-express-hotplug-clear-sticky-power-fault-bit.patch
PCI tree updates
+git-pcmcia-validate_mem-fix.patch
git-pcmcia fix
+gregkh-usb-usb-fix-dummy_hcd-breakage.patch +gregkh-usb-usb-serial-history-not-old.patch +gregkh-usb-add-new-wacom-devices-to-usb-hid-core-list.patch +gregkh-usb-usb-wacom-tablet-driver-update.patch +gregkh-usb-usb-onetouch-doesn-t-suspend-yet.patch +gregkh-usb-usb-pl2303-adds-new-ids.patch +gregkh-usb-usb-pl2303-updates-pl2303_update_line_status.patch +gregkh-usb-usb-adapt-microtek-driver-to-new-scsi-features.patch +gregkh-usb-usb-storage-fix-detection-of-kodak-flash-readers-in-shuttle_usbat-driver.patch +gregkh-usb-usb-fix-race-in-kaweth-disconnect.patch +gregkh-usb-usb-devio-warning-fix.patch +gregkh-usb-usb-maxtor-onetouch-button-support-for-older-drives.patch +gregkh-usb-usb-ohci-lh7a404-platform-device-conversion-fixup.patch +gregkh-usb-pxa27x-ohci-separate-platform-code-from-main-driver.patch +gregkh-usb-add-pxa27x-ohci-pm-functions.patch +gregkh-usb-usb-file-storage-gadget-add-reference-count-for-children.patch +gregkh-usb-usb-net-removes-redundant-return.patch +gregkh-usb-usb-net-new-device-id-passed-through-module-parameter.patch +gregkh-usb-usb-dummy_hcd-rename-variables.patch +gregkh-usb-usbcore-central-handling-for-host-controllers-that-were-reset-during-suspend-resume.patch
USB tree updates
+x86_64-amd-constant-tsc.patch
+x86_64-config-unwind-info.patch
+x86_64-bound-gate.patch
+x86_64-remove-die-if-kernel.patch
+x86_64-die-trap-info.patch
+x86_64-doublefault-cleanup.patch
+x86_64-iret-handling.patch
+x86_64-pagefault-vmalloc.patch
x86_64 tree updates
+mm-fix-__alloc_pages-cpuset-alloc_-flags.patch +mm-simplify-__alloc_pages-cpuset-alloc_-flags.patch +mm-rationalize-__alloc_pages-alloc_-flag-names.patch +mm-simplify-__alloc_pages-cpuset-hardwall-logic.patch +mm-gfp_atomic-comment.patch +memhotplug-__add_section-remove-unused-pgdat-definition.patch +memhotplug-register_-and-unregister_memory_notifier-should-be-global.patch +memhotplug-register_memory-should-be-global.patch +memhotplug-memory_hotplug_name-should-be-const.patch +mm-redo-alloc_-flag-names-again.patch
Memory management updates
+madvise-remove-remove-pages-from-tmpfs-shm-backing-store.patch +madvise-remove-remove-pages-from-tmpfs-shm-backing-store-tidy.patch +madvise-remove-remove-pages-from-tmpfs-shm-backing-store-fix.patch
Weird feature to shoot down shm pages
+dequeue-a-huge-page-near-to-this-node.patch +add-numa-policy-support-for-huge-pages.patch +add-numa-policy-support-for-huge-pages-fix.patch +add-numa-policy-support-for-huge-pages-fix-fix.patch +remove-old-node-based-policy-interface-from-mempolicyc.patch +hugepages-fold-find_or_alloc_pages-into-huge_no_page.patch
NUMA updates
+mm-kvaddr_to_nid-not-used-in-common-code.patch
+mm-pfn_to_pgdat-not-used-in-common-code.patch
+mm-sparse-provide-pfn_to_nid.patch
MM cleanups
+preserve-irq-status-in-release_pages-__pagevec_lru_add.patch
The swap-based migration patches need extra interrupt coverage
-swap-migration-v5-lru-operations-tweaks.patch
-swap-migration-v5-lru-operations-fix.patch
Folded into swap-migration-v5-lru-operations.patch
+swap-migration-v5-lru-operations-inline-shrinkage.patch
Reduce inlining bloat
+swap-migration-v5-migrate_pages-function-tweak.patch
Against swap-migration-v5-migrate_pages-function.patch
+swap-migration-add-config_migration-for-page-migration-support-tweaks.patch
Against swap-migration-add-config_migration-for-page-migration-support.patch
+swap-migration-v5-mpol_mf_move-interface-tweaks.patch
Against swap-migration-v5-mpol_mf_move-interface.patch
-swap-migration-v5-sys_migrate_pages-interface-update.patch
Folded into swap-migration-v5-sys_migrate_pages-interface.patch
+mm-make-hugepages-obey-cpusets.patch
cpuset control of hugepages
+fix-ifenslave-to-not-fail-on-lack-of-ip-information.patch
Fix the ifenslave sample app
+r8169-printk_ratelimit-fix.patch +ipw2200-disallow-direct-scanning-when-device-is-down.patch +drivers-net-wireless-tiacx-add-missing-include-linux-vmallocha.patch
netdev fixes
+ppc32-fix-incorrect-pci-frequency-value.patch
ppc32 update
+remove-include-asm-mips-riscos-syscallh.patch
MIPS cleanup
+x86-handle-wsign-compare-in-bitops.patch
Signedness fix
+i386-sparsemem-for-single-node-systems.patch +allow-flatmem-to-be-disabled-when-only-sparsemem-is-implemented.patch
x86 mm updates
+arm-ixdp425-setup-bug.patch
ARM fix.
+m68knommu-enable_irq-disable_irq.patch
+m68knommu-remove-enable_irq_nosync.patch
m68knommu updates
+cpuset-document-additional-features.patch
cupsets documentation
+fix-missing-includes-for-2615-rc1.patch
More preparatory work for header file untangling
-gregkh-pci-pci-driver-owner-removal-synclink_gt-fix.patch +new-char-driver-synclink_gt-fix.patch
Updated synclink_gt driver
+relayfs-decouple-buffer-creation-from-inode-creation.patch +relayfs-export-relayfs_create_file-with-fileops-param.patch +relayfs-add-relayfs_remove_file.patch +relayfs-use-generic_ip-for-private-data.patch +relayfs-remove-unused-alloc-destroy_inode.patch +relayfs-add-documention-for-non-relay-files.patch +relayfs-add-support-for-relay-files-in-other-filesystems.patch +relayfs-add-documentation-on-relay-files-in-other-filesystems.patch +relayfs-add-support-for-global-relay-buffers.patch +relayfs-add-documentation-on-global-relay-buffers.patch +relayfs-cleanup-change-relayfs_file_-to-relay_file_.patch +relayfs-documentation-cleanup-remove-obsolete-info.patch
relayfs updates
+use-ptrace_get_task_struct-in-various-places-2.patch +use-ptrace_get_task_struct-in-various-places-2-powerpc-fix.patch +use-ptrace_get_task_struct-in-various-places-2-x86_64-fix.patch
ptrace cleanup
+udf-remove-bogus-inode-==-null-check-in-inode_bmap.patch
UDF fixlet
+vgacon-fix-doublescan-mode.patch +vgacon-workaround-for-resize-bug-in-some-chipsets.patch
VGA console fixes
+fix-sysfs-access-to-module-parameters-with-config_modules=n.patch
Make module parameters in sysfs work with CONFIG_MODULES=n
+permit-multiple-inclusion-of-linux-pagevech.patch
include fix
+add-list_for_each_entry_safe_reverse.patch
New list feature
+fix-some-problems-with-truncate-and-mtime-semantics.patch
inode timestamping fixes
+fix-overflow-tests-for-compat_sys_fcntl64-locking.patch
fcntl compat fix
+printk-return-value-fix-it.patch
+kmsg_write-dont-return-printk-return-value.patch
Dink with the printk() return value
+writeback_control-flag-writepages.patch +nfs-work-correctly-with-single-page-writepage-calls.patch
NFS performance fix
+keys-permit-key-expiry-time-to-be-set.patch +keys-discard-duplicate-keys-from-a-keyring-on-link.patch +keys-permit-running-process-to-instantiate-keys.patch
key management updates
+sigaction-should-clear-all-signals-on-sig_ign-not-just.patch
Signal code fix
+spufs-the-spu-file-system-base.patch
+spufs-make-all-exports-gpl-only.patch
+spufs-switchable-spu-contexts.patch
+kernel-side-context-switch-code-for-spufs.patch
+spufs-add-spu-side-context-switch-code.patch
+spufs-cooperative-scheduler-support.patch
Filesystem for accessing the POWER Cell processors
+perfmon2-reserve-system-calls.patch
Reserve a bunch of syscalls for perfmon.
+tiny-add-bloat-o-meter-to-scripts.patch +tiny-uninline-some-nameic-functions.patch +tiny-uninline-some-openc-functions.patch +tiny-uninline-some-inodec-functions.patch +tiny-uninline-some-fslocksc-functions.patch +tiny-trim-non-ipx-builds.patch +tiny-make-x86-doublefault-handling-optional.patch +tiny-make-id16-support-optional.patch +tiny-configure-elf-core-dump-support.patch +tiny-configurable-support-for-pci-serial-ports.patch
A bunch of kernel footprint shrinking features.
+replace-inode_update_time-with-file_update_time-comments.patch
Update replace-inode_update_time-with-file_update_time.patch
+add-compat_ioctl-methods-to-dasd-fix.patch
Fix add-compat_ioctl-methods-to-dasd.patch
+parisc-remove-drm-compat-ioctls-handlers.patch
+parisc-implement-compat_ioctl-for-pa_perf.patch
+common-compat_sys_timer_create.patch
More compat layer cleanups
-udf-fix-issues-reported-by-coverity-in-inodec.patch
Obsolete
+keep-nfsd-from-exiting-when-seeing-recv-errors.patch
knfsd fix
+scheduler-cache-hot-autodetect-fix.patch
Fix CPU scheduler patch in -mm.
+reiser4-remove-rwx-perm-plugin.patch
+reiser4-fix-link_common.patch
+reiser4-fix-readlink.patch
+reiser4-add-crc-sendfile.patch
+reiser4-back-to-one-makefile.patch
+reiser4-rename-cluster-files.patch
+reiser4-crypt2cipher-rename.patch
+reiser4-lock-ordering-fix.patch
+reiser4-improved-comment.patch
+reiser4-try_capture_block-update.patch
+reiser4-fix-zeroing-in-crc-files.patch
reiser4 updates
+cs5520-fix-return-value-of-cs5520_init_one.patch
Fix a sound driver
+vesafb-drop-blank-hook.patch
+aty-remove-unnecessary-config_pci.patch
fbdev fixes
-make-kmalloc-fail-for-swapped-size--gfp-flags.patch
Dropped - we can detect this statically with sparse now
+slab-cache-shrinker-statistics-fix.patch
Fix slab-cache-shrinker-statistics.patch
+mm-debug-dump-pageframes-on-bad_page.patch
Extra memory management debugging
+turn-const-static-into-static-const.patch +fix-sparse-using-plain-integer-as-null-pointer-warnings.patch
Cleanups
All 598 patches:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc1/2.6.15-rc1-mm1/patch-list
Quoted 6 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc1/2.6.15-rc1-mm1
+keys-permit-running-process-to-instantiate-keys.patch
key management updates
This causes a compile issue:
CC security/keys/keyctl.osecurity/keys/keyctl.c:1029: error: conflicting types for 'keyctl_assume_authority' security/keys/internal.h:141: error: previous declaration of 'keyctl_assume_authority' was here make[2]: *** [security/keys/keyctl.o] Error 1
Why does keyctl.c declare it as 'asmlinkage'?
security/keys/keyctl.c renamed from security/keys/keyctl.c.dist +1 -1
@@ -1025,7 +1025,7 @@/* * assume the authority to instantiate the specified key */ -asmlinkage long keyctl_assume_authority (key_serial_t id) +long keyctl_assume_authority (key_serial_t id) {struct key *authkey;long ret;
Quoted 1 line · [email protected] wrote:
Why does
keyctl.cdeclare it as 'asmlinkage'?
Because it's wrong.
Quoted 6 lines · David Howells
Quoted 1 line · [email protected] wrote:
Why does
keyctl.cdeclare it as 'asmlinkage'?Because it's wrong.
Am chasing another issue - once I got past that, it wouldn't boot at all. Grub would act like it was loading, then 2 seconds or so later, grub would start up again. My first guess was CONFIG_DEBUG_RODATA=y, but I ruled that out. More detail once I've done some more binary searching and ruled out self-inflicted idiocy....
2.6.15-rc1-mm1 - immediate system reset at boot
Quoted 5 lines · On Thu, 17 Nov 2005 17:23:30 EST, [email protected] said:
Am chasing another issue - once I got past that, it wouldn't boot at all. Grub would act like it was loading, then 2 seconds or so later, grub would start up again. My first guess was
CONFIG_DEBUG_RODATA=y, but I ruled that out. More detail once I've done some more binary searching and ruled out self-inflicted idiocy....
Rebuilt from a completely new and clean tree, 2.6.14-mm1 is fine, 2.6.15-rc1 will start booting OK, -rc1-mm1 chokes up almost instantly. It doesn't live long enough for either/both earlyprintk=vga or initcall_debug to output anything - grub says "loading", clears the screen, and 2 seconds later the laptop gives the 'ka-chunk' noise it does on a system reset, and I'm looking at the BIOS splash screen.
Any obvious places to look, or time to play bisection on the 600 patches in -mm?
Re: 2.6.15-rc1-mm1 - immediate system reset at boot
Quoted 16 lines · [email protected] wrote:
Quoted 5 lines · On Thu, 17 Nov 2005 17:23:30 EST, [email protected] said:
Am chasing another issue - once I got past that, it wouldn't boot at all. Grub would act like it was loading, then 2 seconds or so later, grub would start up again. My first guess was
CONFIG_DEBUG_RODATA=y, but I ruled that out. More detail once I've done some more binary searching and ruled out self-inflicted idiocy....Rebuilt from a completely new and clean tree, 2.6.14-mm1 is fine, 2.6.15-rc1 will start booting OK, -rc1-mm1 chokes up almost instantly. It doesn't live long enough for either/both earlyprintk=vga or
initcall_debugto output anything - grub says "loading", clears the screen, and 2 seconds later the laptop gives the 'ka-chunk' noise it does on a system reset, and I'm looking at the BIOS splash screen.
Quoted 2 lines
Any obvious places to look, or time to play bisection on the 600 patches in -mm?
Can't think of anything, sorry. The obvious area to probe is around the x86 and mm patch subserieses.
Hi
Quoted 3 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc1/2.6.15-rc1-mm1
Got a compiler-error:
CC drivers/serial/jsm/jsm_tty.odrivers/serial/jsm/jsm_tty.c: In function `jsm_input':drivers/serial/jsm/jsm_tty.c:592: error: structure has no member named flip' drivers/serial/jsm/jsm_tty.c:619: error: structure has no member named flip' drivers/serial/jsm/jsm_tty.c:620: error: structure has no member named `flip'
...
(in file drivers/serial/jsm/jsm_tty.c, line 592)
flip_len = TTY_FLIPBUF_SIZE - tp->flip.count;
I could not find the patch but I tracked it to the change:
include/linux/tty.h +0 -0
@@ -74,8 +74,7 @@ struct screen_info {
u16 vesapm_off; /* 0x30 */ u16 pages; /* 0x32 */ u16 vesa_attributes; /* 0x34 */
- u32 capabilities; /* 0x36 */
- /* 0x3a -- 0x3f reserved for future expansion */
+ /* 0x36 -- 0x3f reserved for future expansion */
};
extern struct screen_info screen_info;
@@ -121,16 +120,22 @@ extern struct screen_info screen_info;
*/
#define TTY_FLIPBUF_SIZE 512
-struct tty_flip_buffer {
+struct tty_buffer {
+ struct tty_buffer *next;
+ char *char_buf_ptr;
+ unsigned char *flag_buf_ptr;
+ int used;
+ int size;
+ /* Data points here */
+ unsigned long data[0];
+};
+
+struct tty_bufhead {
struct work_struct work;
struct semaphore pty_sem;- char *char_buf_ptr;
- unsigned char *flag_buf_ptr;
- int count;
- int buf_num;
- unsigned char char_buf[2*TTY_FLIPBUF_SIZE];
- char flag_buf[2*TTY_FLIPBUF_SIZE];
- unsigned char slop[4]; /* N.B. bug overwrites buffer by 1 */
+ struct tty_buffer *head; /* Queue head */
+ struct tty_buffer *tail; /* Active buffer */
+ struct tty_buffer *free; /* Free queue head */
};
/*
* The pty uses char_buf and flag_buf as a contiguous buffer
@@ -256,10 +261,11 @@ struct tty_struct {
unsigned char stopped:1, hw_stopped:1, flow_stopped:1, packet:1;
unsigned char low_latency:1, warned:1;
unsigned char ctrl_status;+ unsigned int receive_room; /* Bytes free for queue */
struct tty_struct *link; struct fasync_struct *fasync; - struct tty_flip_buffer flip; + struct tty_bufhead buf; int max_flip_cnt; int alt_speed; /* For magic substitution of 38400 bps */ wait_queue_head_t write_wait;
tty_flip_buffer have been split up to tty_buffer and tty_bufhead, so I do not know what the correct replacement for flip.count is.
/Richard Knutsson
Quoted 11 lines · Richard Knutsson
Quoted 4 lines
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc1/2.6.15-rc1-mm1
Got a compiler-error:
CC
drivers/serial/jsm/jsm_tty.o
drivers/serial/jsm/jsm_tty.c: In function `jsm_input':
drivers/serial/jsm/jsm_tty.c:592: error: structure has no member namedflip' drivers/serial/jsm/jsm_tty.c:619: error: structure has no member namedflip'drivers/serial/jsm/jsm_tty.c:620: error: structure has no member named `flip'
Yes, sorry, JSM is known-to-be-bust-in-mm. The maintainers are working (slowly) on fixing it up.
PATCH 1/1 kernel/signal.c: fix compile warning
In reply to Andrew MortonQuoted 7 lines · Andrew Morton
...
Changes since 2.6.14-mm2:
...
+sigaction-should-clear-all-signals-on-sig_ign-not-just.patchSignal code fix
...
Patches get bonus points when they don't introduce new compile warnings...
<-- snip -->
...
CC kernel/signal.okernel/signal.c: In function 'rm_from_queue_full':kernel/signal.c:638: warning: control may reach end of non-void function 'sigisemptyset' being inlined
...
<-- snip -->
include/linux/signal.h renamed from include/linux/signal.h.old +1 -0
@@ -102,6 +102,7 @@return set->sig[0 ] ==0 ;default :_NSIG_WORDS_is_unsupported_size (); +return 0 ; } }
Re: [-mm patch] kernel/signal.c: fix compile warning
Quoted 7 lines · Adrian Bunk
Quoted 5 lines · Andrew Morton
...
Changes since 2.6.14-mm2:
...
+sigaction-should-clear-all-signals-on-sig_ign-not-just.patch
Quoted 6 lines
Quoted 2 lines
Signal code fix
...Patches get bonus points when they don't introduce new compile warnings...
Even more when the fix them. My loss, your gain :). Still I wonder why I did not see that.
George
Signature · 3 lines
-- George Anzinger [email protected] HRT (High-res-timers): http://sourceforge.net/projects/high-res-timers/
Hi,
Quoted 8 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc1/2.6.15-rc1-mm1
- reiser4 significantly updated
Changes since 2.6.14-mm2:
This has been one of the best -mm releases in a while. No problems compiling or running - and so far nearly 18 hours uptime without any surprises.
Following up on a posting from the last -mm release, I'm still seeing errors loading multiple network drivers as modules (e100 and sky2) when CONFIG_PREEMPT_BKL is enabled, with 2.6.14-mm1, 2.6.14-mm2 and now 2.6.15-rc1-mm1. Mainline git doesn't exhibit the problem, so it's -mm specific.
This is what is logged:
Nov 18 17:40:42 tornado kernel: e100: 0000:06:03.0: e100_eeprom_load: EEPROM corrupted Nov 18 17:40:42 tornado kernel: ACPI: PCI interrupt for device 0000:06:03.0 disabled Nov 18 17:40:42 tornado kernel: e100: probe of 0000:06:03.0 failed with error -11 Nov 18 17:40:43 tornado kernel: ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 177 Nov 18 17:40:43 tornado kernel: sky2 0000:04:00.0: unsupported chip type 0xff Nov 18 17:40:43 tornado kernel: ACPI: PCI interrupt for device 0000:04:00.0 disabled Nov 18 17:40:43 tornado kernel: sky2: probe of 0000:04:00.0 failed with error -95
I'm certain that both of these NIC's are OK as they work fine with CONFIG_PREEMPT_BKL not selected.
With CONFIG_PREEMPT_BKL disabled and an otherwise identical config, the driver modules load up just fine.
A known good kernel with this config was 2.6.14-rc5-mm1.
I have backed out git-netdev-all but it made no difference, as well as backed out the e100 changes in -mm on 2.6.15-mm2, again no difference. So I suspect it's not a netdev driver problem.
What else can I do to help narrow down the problem? What other trees or patches would be worth backing out to try and narrow it down?
.config and system details are up on http://www.reub.net/kernel/
Reuben
Quoted 11 lines · Reuben Farrelly
Hi,
Quoted 7 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc1/2.6.15-rc1-mm1
- reiser4 significantly updated
Quoted 4 lines
Quoted 1 line
Changes since 2.6.14-mm2:
This has been one of the best -mm releases in a while. No problems compiling or running - and so far nearly 18 hours uptime without any surprises.
We'll have to try harder. -mm2 is up there now, to break everything again.
Quoted 25 lines
Following up on a posting from the last -mm release, I'm still seeing errors loading multiple network drivers as modules (e100 and sky2) when
CONFIG_PREEMPT_BKLis enabled, with 2.6.14-mm1, 2.6.14-mm2 and now 2.6.15-rc1-mm1. Mainline git doesn't exhibit the problem, so it's -mm specific.This is what is logged:
Nov 18 17:40:42 tornado kernel: e100: 0000:06:03.0: e100_eeprom_load: EEPROM corrupted Nov 18 17:40:42 tornado kernel: ACPI: PCI interrupt for device 0000:06:03.0 disabled Nov 18 17:40:42 tornado kernel: e100: probe of 0000:06:03.0 failed with error -11 Nov 18 17:40:43 tornado kernel: ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 177 Nov 18 17:40:43 tornado kernel: sky2 0000:04:00.0: unsupported chip type 0xff Nov 18 17:40:43 tornado kernel: ACPI: PCI interrupt for device 0000:04:00.0 disabled Nov 18 17:40:43 tornado kernel: sky2: probe of 0000:04:00.0 failed with error -95I'm certain that both of these NIC's are OK as they work fine with
CONFIG_PREEMPT_BKLnot selected.With
CONFIG_PREEMPT_BKLdisabled and an otherwise identical config, the driver modules load up just fine.
Quoted 7 lines
A known good kernel with this config was 2.6.14-rc5-mm1.
I have backed out git-netdev-all but it made no difference, as well as backed out the e100 changes in -mm on 2.6.15-mm2, again no difference. So I suspect it's not a netdev driver problem.What else can I do to help narrow down the problem? What other trees or patches would be worth backing out to try and narrow it down?
I'd be suspecting the PCI changes firstly. That's gregkh-pci-*.
Conceivably git-acpi, but that hasn't changed in quite some time. In fact, no ACPI changes since 2.6.14-rc5-mm1.
After that I don't know, sorry. Binary search time?
Andrew Morton wrote (ao):
Quoted 9 lines
Quoted 8 lines · Reuben Farrelly
Quoted 7 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc1/2.6.15-rc1-mm1
- reiser4 significantly updated
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
Changes since 2.6.14-mm2:
This has been one of the best -mm releases in a while. No problems compiling or running - and so far nearly 18 hours uptime without any surprises.
I second this. It is stable under (my) load where the 2.6.14-mm releases crashed. Most likely due to Reiser4, but couldn't capture anything yet (netconsole troubles, have to investigate more) so not sure.
Reiser4 is very slow though, as is discussed on the reiserfs list atm.
Quoted 1 line
We'll have to try harder. -mm2 is up there now, to break everything again.
Nice :-)
Signature · 2 lines
Humilis IT Services and Solutions http://www.humilis.net
Quoted 42 lines · Andrew Morton
Quoted 5 lines · Reuben Farrelly
Hi,
Quoted 2 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc1/2.6.15-rc1-mm1
Quoted 8 lines
Quoted 6 lines
- reiser4 significantly updated
Changes since 2.6.14-mm2:
This has been one of the best -mm releases in a while. No problems compiling or running - and so far nearly 18 hours uptime without any surprises.
We'll have to try harder. -mm2 is up there now, to break everything again.
Quoted 25 lines
Following up on a posting from the last -mm release, I'm still seeing errors loading multiple network drivers as modules (e100 and sky2) when
CONFIG_PREEMPT_BKLis enabled, with 2.6.14-mm1, 2.6.14-mm2 and now 2.6.15-rc1-mm1. Mainline git doesn't exhibit the problem, so it's -mm specific.This is what is logged:
Nov 18 17:40:42 tornado kernel: e100: 0000:06:03.0: e100_eeprom_load: EEPROM corrupted Nov 18 17:40:42 tornado kernel: ACPI: PCI interrupt for device 0000:06:03.0 disabled Nov 18 17:40:42 tornado kernel: e100: probe of 0000:06:03.0 failed with error -11 Nov 18 17:40:43 tornado kernel: ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 177 Nov 18 17:40:43 tornado kernel: sky2 0000:04:00.0: unsupported chip type 0xff Nov 18 17:40:43 tornado kernel: ACPI: PCI interrupt for device 0000:04:00.0 disabled Nov 18 17:40:43 tornado kernel: sky2: probe of 0000:04:00.0 failed with error -95I'm certain that both of these NIC's are OK as they work fine with
CONFIG_PREEMPT_BKLnot selected.With
CONFIG_PREEMPT_BKLdisabled and an otherwise identical config, the driver modules load up just fine.A known good kernel with this config was 2.6.14-rc5-mm1.
I have backed out git-netdev-all but it made no difference, as well as backed out the e100 changes in -mm on 2.6.15-mm2, again no difference. So I suspect it's not a netdev driver problem.
Quoted 8 lines
Quoted 1 line
What else can I do to help narrow down the problem? What other trees or patches would be worth backing out to try and narrow it down?
I'd be suspecting the PCI changes firstly. That's gregkh-pci-*.
Conceivably git-acpi, but that hasn't changed in quite some time. In fact, no ACPI changes since 2.6.14-rc5-mm1.
After that I don't know, sorry. Binary search time?
Still looking into this one. It appears that backing out the gregkh-pci patches in -rc1-mm2 made no difference.
I don't think I should be able to make this happen so easily though:
[root@tornado ~]# rmmod e100
[root@tornado ~]# rmmod sky2
[root@tornado ~]# strace modprobe e100
Unable to handle kernel NULL pointer dereference at virtual address 00000010 printing eip: c0124fc7 *pde = 00000000 Oops: 0000 [#1] PREEMPT SMP last sysfs file: /class/net/eth0/flags Modules linked in: nfsd exportfs lockd sunrpc autofs4 lm85 hwmon_vid eeprom ipv6 binfmt_misc hw_random crc32 piix i2c_i801 CPU: 0 EIP: 0060:[<c0124fc7>] Not tainted VLI EFLAGS: 00010202 (2.6.15-rc1-mm2-preempt)
EIP is at ptrace_check_attach+0x14/0xaf
eax: 00000001 ebx: 00000000 ecx: 00000001 edx: c0417c00
esi: 00000000 edi: 00000000 ebp: e93b0f9c esp: e93b0f90
ds: 007b es: 007b ss: 0068
Process strace (pid: 3386, threadinfo=e93b0000 task=ec4c0130)
Stack: 00000000 00000000 00000018 e93b0fb4 c0125840 00000000 00000018 00000000
4521bff4 e93b0000 c0102cb7 00000018 00000d3b 00000001 00000000 4521bff4
bf819eb8 0000001a 0000007b c010007b 0000001a ffffe410 00000073 00000202
Call Trace:
[<c0103c09>] show_stack+0x94/0xca
[<c0103dd2>] show_registers+0x17a/0x210
[<c0104008>] die+0x116/0x19d
[<c03394dd>] do_page_fault+0x1ed/0x63d
[<c01038af>] error_code+0x4f/0x54
[<c0125840>] sys_ptrace+0x50/0xb9
[<c0102cb7>] sysenter_past_esp+0x54/0x75
---------------------------| preempt count: 00000002 ]
| 2 level deep critical section nesting:
----------------------------------------
.. [<c03389cc>] .... _read_lock+0x10/0x6b
.....[<c0124fc7>] .. ( <= ptrace_check_attach+0x14/0xaf)
.. [<c0338938>] .... _spin_lock_irqsave+0x11/0x71
.....[<c0103f36>] .. ( <= die+0x44/0x19d)
Code: 4c 5b 39 c0 a3 4c 5b 39 c0 c7 43 68 48 5b 39 c0 89 50 04 89 02 eb a8 55 89 e5 57 56 53 89 c3 89 d7 b8 00 7c 41 c0 e8 f5 39 21 00 <8b> 53 10 f6 c2 01 75 21 be fd ff ff ff b8 00 7c 41 c0 e8 43 3c <3>Debug: sleeping function called from invalid context at include/linux/rwsem.h:43 in_atomic():1, irqs_disabled():0 [<c0103c56>] dump_stack+0x17/0x19 [<c011a173>] __might_sleep+0x9c/0xae [<c011da06>] profile_task_exit+0x16/0x49 [<c011f6f7>] do_exit+0x1c/0x47a [<c010408f>] do_divide_error+0x0/0x9e [<c03394dd>] do_page_fault+0x1ed/0x63d [<c01038af>] error_code+0x4f/0x54 [<c0125840>] sys_ptrace+0x50/0xb9 [<c0102cb7>] sysenter_past_esp+0x54/0x75 ---------------------------
| preempt count: 00000001 ]
| 1 level deep critical section nesting:
----------------------------------------
.. [<c03389cc>] .... _read_lock+0x10/0x6b
.....[<c0124fc7>] .. ( <= ptrace_check_attach+0x14/0xaf)
BUG: strace[3386] exited with nonzero preempt_count 1! ---------------------------
| preempt count: 00000001 ]
| 1 level deep critical section nesting:
----------------------------------------
.. [<c03389cc>] .... _read_lock+0x10/0x6b
.....[<c0124fc7>] .. ( <= ptrace_check_attach+0x14/0xaf)
BUG: soft lockup detected on CPU#0!
Pid: 3386, comm: strace
EIP: 0060:[<c0338b8c>] CPU: 0
EIP is at _write_lock_irqsave+0x65/0x7b
EFLAGS: 00000202 Not tainted (2.6.15-rc1-mm2-preempt)
EAX: 00ffffff EBX: 00000286 ECX: 00000000 EDX: 00000001
ESI: c0417c00 EDI: ec4c05ec EBP: e93b0e6c DS: 007b ES: 007b
CR0: 8005003b CR2: 00000010 CR3: 00456000 CR4: 000006d0
---------------------------
| preempt count: 00010001 ]
| 1 level deep critical section nesting:
----------------------------------------
.. [<c03389cc>] .... _read_lock+0x10/0x6b
.....[<c0124fc7>] .. ( <= ptrace_check_attach+0x14/0xaf)
BUG: soft lockup detected on CPU#0!
Pid: 3386, comm: strace
EIP: 0060:[<c0338b8c>] CPU: 0
EIP is at _write_lock_irqsave+0x65/0x7b
EFLAGS: 00000202 Not tainted (2.6.15-rc1-mm2-preempt)
EAX: 00ffffff EBX: 00000286 ECX: 00000000 EDX: 00000001
ESI: c0417c00 EDI: ec4c05ec EBP: e93b0e6c DS: 007b ES: 007b
CR0: 8005003b CR2: 00000010 CR3: 00456000 CR4: 000006d0
---------------------------
| preempt count: 00010001 ]
| 1 level deep critical section nesting:
----------------------------------------
.. [<c03389cc>] .... _read_lock+0x10/0x6b
.....[<c0124fc7>] .. ( <= ptrace_check_attach+0x14/0xaf)
BUG: soft lockup detected on CPU#0!
Pid: 3386, comm: strace
EIP: 0060:[<c0338b8c>] CPU: 0
EIP is at _write_lock_irqsave+0x65/0x7b
EFLAGS: 00000202 Not tainted (2.6.15-rc1-mm2-preempt)
EAX: 00ffffff EBX: 00000286 ECX: 00000000 EDX: 00000001
ESI: c0417c00 EDI: ec4c05ec EBP: e93b0e6c DS: 007b ES: 007b
CR0: 8005003b CR2: 00000010 CR3: 00456000 CR4: 000006d0
---------------------------
| preempt count: 00010001 ]
| 1 level deep critical section nesting:
----------------------------------------
.. [<c03389cc>] .... _read_lock+0x10/0x6b
.....[<c0124fc7>] .. ( <= ptrace_check_attach+0x14/0xaf)
BUG: soft lockup detected on CPU#0!
Pid: 3386, comm: strace
EIP: 0060:[<c0338b8a>] CPU: 0
EIP is at _write_lock_irqsave+0x63/0x7b
EFLAGS: 00000202 Not tainted (2.6.15-rc1-mm2-preempt)
EAX: 00ffffff EBX: 00000286 ECX: 00000000 EDX: 00000001
ESI: c0417c00 EDI: ec4c05ec EBP: e93b0e6c DS: 007b ES: 007b
CR0: 8005003b CR2: 00000010 CR3: 00456000 CR4: 000006d0
---------------------------
| preempt count: 00010001 ]
| 1 level deep critical section nesting:
----------------------------------------
.. [<c03389cc>] .... _read_lock+0x10/0x6b
.....[<c0124fc7>] .. ( <= ptrace_check_attach+0x14/0xaf)
BUG: soft lockup detected on CPU#0!
Pid: 3386, comm: strace
EIP: 0060:[<c0338b8a>] CPU: 0
EIP is at _write_lock_irqsave+0x63/0x7b
EFLAGS: 00000202 Not tainted (2.6.15-rc1-mm2-preempt)
EAX: 00ffffff EBX: 00000286 ECX: 00000000 EDX: 00000001
ESI: c0417c00 EDI: ec4c05ec EBP: e93b0e6c DS: 007b ES: 007b
CR0: 8005003b CR2: 00000010 CR3: 00456000 CR4: 000006d0
---------------------------
| preempt count: 00010001 ]
| 1 level deep critical section nesting:
----------------------------------------
.. [<c03389cc>] .... _read_lock+0x10/0x6b
.....[<c0124fc7>] .. ( <= ptrace_check_attach+0x14/0xaf)
reuben
Quoted 7 lines · Reuben Farrelly
I don't think I should be able to make this happen so easily though:
[root@tornado ~]# rmmod e100
[root@tornado ~]# rmmod sky2
[root@tornado ~]# strace modprobe e100
Quoted 13 lines
Unable to handle kernel NULL pointer dereference at virtual address 00000010 printing eip: c0124fc7 *pde = 00000000 Oops: 0000 [#1] PREEMPT SMP last sysfs file: /class/net/eth0/flags Modules linked in: nfsd exportfs lockd sunrpc autofs4 lm85 hwmon_vid eeprom ipv6 binfmt_misc hw_random crc32 piix i2c_i801 CPU: 0 EIP: 0060:[<c0124fc7>] Not tainted VLI EFLAGS: 00010202 (2.6.15-rc1-mm2-preempt) EIP is at ptrace_check_attach+0x14/0xaf
This might help..
Begin forwarded message:
Date: Fri, 18 Nov 2005 18:07:43 +0000
From: Christoph Hellwig <[email protected]>
To: Badari Pulavarty <[email protected]>
Cc: [email protected], lkml <[email protected]>
Subject: Re: 2.6.15-rc1-mm1 panic in ptrace_check_attach()
Quoted 6 lines · Badari Pulavarty
Hi Andrew,
I am not sure if its already reported. I get panic in
ptrace_check_attach()while trying to run UML on 2.6.15-rc1-mm1.Going to try 2.6.15-rc1-mm2 now.
Looks like 2.6.15-rc1-mm1 has total crap in ptrace_get_task_struct (and it looks like my fault because I sent out a wrong patch).
The patch below should fix it:
kernel/ptrace.c +1 -1
@@ -459,7 +459,7 @@read_unlock (&tasklist_lock);if (!child)return ERR_PTR (-ESRCH ); -return 0 ; +return child; }#ifndef __ARCH_SYS_PTRACE
Quoted 1 line · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc1/2.6.15-rc1-mm1
Hi,
Any ideas why the mousedev module does not load automaticly with 15-rc1-mm1?
With 14-rc4-mm1 all is ok. With 15-rc1-mm1 I have no /dev/input which causes Xorg fun. The mouse is connected to a usb hub and is detected when I unplug and replug it. I used make oldconfig from a 14-rc4-mm1 config. Dist is debian amd64 unstable and is up to date.
When I manually modprobe mousedev things work as expected
DRM works fine and dri is enabled.
Ideas,
Ed Tomlinson
Quoted 6 lines · Ed Tomlinson
Quoted 1 line · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc1/2.6.15-rc1-mm1
Hi,
Any ideas why the mousedev module does not load automaticly with 15-rc1-mm1?
Are you using debian?
If so, what version of udev are you using? There are some known reported problems with this, so I would suggest referring to the udev bug list.
If you aren't using Debian, please let us know. Also, what version of udev are you using?
thanks,
greg k-h
Quoted 5 lines · Greg KH
Are you using debian?
If so, what version of udev are you using? There are some known reported problems with this, so I would suggest referring to the udev bug list.
In particular check the version requirements for udev - you need to be on a version greater than or equal to 71. Sarge/stable has a really old version. In particular I am running unstable as I had too many funny errors (including this one) - but etch should be fine.
If running another distribution check this also as it is a real requirement.
To find the latest version of udev required check Documentation/Changes
Ian
--
Ian McDonald
http://wand.net.nz/~iam4
WAND Network Research Group
University of Waikato
New Zealand
Quoted 6 lines · Ian McDonald
Quoted 5 lines · Greg KH
Are you using debian?
If so, what version of udev are you using? There are some known reported problems with this, so I would suggest referring to the udev bug list.
Quoted 8 lines
In particular check the version requirements for udev - you need to be on a version greater than or equal to 71. Sarge/stable has a really old version. In particular I am running unstable as I had too many funny errors (including this one) - but etch should be fine.
If running another distribution check this also as it is a real requirement.
To find the latest version of udev required check
Documentation/Changes
devinfo -v
udevinfo, version 074
dpkg -s
Package: udev
Status: install ok installed
Priority: extra
Section: admin
Installed-Size: 1072
Maintainer: Marco d'Itri <[email protected]>
Architecture: amd64
Version: 0.074-3
Interestingly the same udev works fine with 14-rc4-mm1. I'll check the debian bugs.
Thanks
Ed Tomlinson
Quoted 29 lines · Ed Tomlinson
Quoted 6 lines · Ian McDonald
Quoted 5 lines · Greg KH
Are you using debian?
If so, what version of udev are you using? There are some known reported problems with this, so I would suggest referring to the udev bug list.Quoted 8 lines
In particular check the version requirements for udev - you need to be on a version greater than or equal to 71. Sarge/stable has a really old version. In particular I am running unstable as I had too many funny errors (including this one) - but etch should be fine.
If running another distribution check this also as it is a real requirement.
To find the latest version of udev required check
Documentation/Changesdevinfo -v
udevinfo, version 074dpkg -s
Package: udev
Status: install ok installed
Priority: extra
Section: admin
Installed-Size: 1072
Maintainer: Marco d'Itri <[email protected]>
Architecture: amd64
Version: 0.074-3
Quoted 2 lines
Interestingly the same udev works fine with 14-rc4-mm1. I'll check the debian bugs.
Lots of things have changed in the input core since that kernel version. Others have reported this same issue, see the thread from Ted Tso on lkml a while ago when 2.6.15-rc1 came out.
thanks,
greg k-h
Quoted 29 lines · Ed Tomlinson
Quoted 6 lines · Ian McDonald
Quoted 5 lines · Greg KH
Are you using debian?
If so, what version of udev are you using? There are some known reported problems with this, so I would suggest referring to the udev bug list.Quoted 8 lines
In particular check the version requirements for udev - you need to be on a version greater than or equal to 71. Sarge/stable has a really old version. In particular I am running unstable as I had too many funny errors (including this one) - but etch should be fine.
If running another distribution check this also as it is a real requirement.
To find the latest version of udev required check
Documentation/Changesdevinfo -v
udevinfo, version 074dpkg -s
Package: udev
Status: install ok installed
Priority: extra
Section: admin
Installed-Size: 1072
Maintainer: Marco d'Itri <[email protected]>
Architecture: amd64
Version: 0.074-3
Quoted 2 lines
Interestingly the same udev works fine with 14-rc4-mm1. I'll check the debian bugs.
There does not seem to be anything that fits this reported as a debian bug. Where is the udev bugs list?
TIA
Ed Tomlinson
Quoted 30 lines · Ed Tomlinson
Quoted 29 lines · Ed Tomlinson
Quoted 6 lines · Ian McDonald
Quoted 5 lines · Greg KH
Are you using debian?
If so, what version of udev are you using? There are some known reported problems with this, so I would suggest referring to the udev bug list.Quoted 8 lines
In particular check the version requirements for udev - you need to be on a version greater than or equal to 71. Sarge/stable has a really old version. In particular I am running unstable as I had too many funny errors (including this one) - but etch should be fine.
If running another distribution check this also as it is a real requirement.
To find the latest version of udev required check
Documentation/Changesdevinfo -v
udevinfo, version 074dpkg -s
Package: udev
Status: install ok installed
Priority: extra
Section: admin
Installed-Size: 1072
Maintainer: Marco d'Itri <[email protected]>
Architecture: amd64
Version: 0.074-3
Quoted 5 lines
Quoted 2 lines
Interestingly the same udev works fine with 14-rc4-mm1. I'll check the debian bugs.
There does not seem to be anything that fits this reported as a debian bug. Where is the udev bugs list?
For Debian? I have no idea as I do not use it :)
For general udev issues/queries try the linux-hotplug-devel mailing list.
Oh, and are you sure you actually have the proper module loaded?
thanks,
greg k-h
Quoted 37 lines · Greg KH
Quoted 30 lines · Ed Tomlinson
Quoted 29 lines · Ed Tomlinson
Quoted 6 lines · Ian McDonald
Quoted 5 lines · Greg KH
Are you using debian?
If so, what version of udev are you using? There are some known reported problems with this, so I would suggest referring to the udev bug list.Quoted 8 lines
In particular check the version requirements for udev - you need to be on a version greater than or equal to 71. Sarge/stable has a really old version. In particular I am running unstable as I had too many funny errors (including this one) - but etch should be fine.
If running another distribution check this also as it is a real requirement.
To find the latest version of udev required check
Documentation/Changesdevinfo -v
udevinfo, version 074dpkg -s
Package: udev
Status: install ok installed
Priority: extra
Section: admin
Installed-Size: 1072
Maintainer: Marco d'Itri <[email protected]>
Architecture: amd64
Version: 0.074-3Quoted 5 lines
Quoted 2 lines
Interestingly the same udev works fine with 14-rc4-mm1. I'll check the debian bugs.
There does not seem to be anything that fits this reported as a debian bug. Where is the udev bugs list?
Quoted 6 lines
For Debian? I have no idea as I do not use it :)
For general udev issues/queries try the linux-hotplug-devel mailing list.
Oh, and are you sure you actually have the proper module loaded?
Think only the mousedev module is not loaded. Once I modprobe it the mouse works and the /dev/input/mice appears. The mouse works normally with all buttons and wheels acting normal.
Ed
Quoted 4 lines
Think only the mousedev module is not loaded. Once I modprobe it the mouse works and the
/dev/input/miceappears. The mouse works normally with all buttons and wheels acting normal.
I was having this on one of my machines. I'll try and track this down next week probably if it still occurs and use git-bisect on it if nobody else does first though. I'll check out the thread mentioned as well.
Ian
--
Ian McDonald
http://wand.net.nz/~iam4
WAND Network Research Group
University of Waikato
New Zealand
Quoted 40 lines · Ed Tomlinson
Quoted 39 lines · Greg KH
Quoted 30 lines · Ed Tomlinson
Quoted 29 lines · Ed Tomlinson
Quoted 6 lines · Ian McDonald
Quoted 5 lines · Greg KH
Are you using debian?
If so, what version of udev are you using? There are some known reported problems with this, so I would suggest referring to the udev bug list.Quoted 8 lines
In particular check the version requirements for udev - you need to be on a version greater than or equal to 71. Sarge/stable has a really old version. In particular I am running unstable as I had too many funny errors (including this one) - but etch should be fine.
If running another distribution check this also as it is a real requirement.
To find the latest version of udev required check
Documentation/Changesdevinfo -v
udevinfo, version 074dpkg -s
Package: udev
Status: install ok installed
Priority: extra
Section: admin
Installed-Size: 1072
Maintainer: Marco d'Itri <[email protected]>
Architecture: amd64
Version: 0.074-3Quoted 5 lines
Quoted 2 lines
Interestingly the same udev works fine with 14-rc4-mm1. I'll check the debian bugs.
There does not seem to be anything that fits this reported as a debian bug. Where is the udev bugs list?
For Debian? I have no idea as I do not use it :)
Quoted 8 lines
Quoted 4 lines
For general udev issues/queries try the linux-hotplug-devel mailing list.
Oh, and are you sure you actually have the proper module loaded?
Think only the mousedev module is not loaded. Once I modprobe it the mouse works and the
/dev/input/miceappears. The mouse works normally with all buttons and wheels acting normal.
Then you just need to make sure that module is loaded properly, which doesn't sound like a udev issue :)
thanks,
greg k-h
Quoted 7 lines
Quoted 3 lines
Think only the mousedev module is not loaded. Once I modprobe it the mouse works and the
/dev/input/miceappears. The mouse works normally with all buttons and wheels acting normal.Then you just need to make sure that module is loaded properly, which doesn't sound like a udev issue :)
My personal experience was that all my modules loaded automatically, including mousedev and then mousedev doesn't anymore (but haven't checked very latest kernel tree) and then you have to manually load.
Ian
--
Ian McDonald
http://wand.net.nz/~iam4
WAND Network Research Group
University of Waikato
New Zealand
Quoted 44 lines · Greg KH
Quoted 43 lines · Ed Tomlinson
Quoted 42 lines · Greg KH
Quoted 30 lines · Ed Tomlinson
Quoted 29 lines · Ed Tomlinson
Quoted 6 lines · Ian McDonald
Quoted 5 lines · Greg KH
Are you using debian?
If so, what version of udev are you using? There are some known reported problems with this, so I would suggest referring to the udev bug list.Quoted 8 lines
In particular check the version requirements for udev - you need to be on a version greater than or equal to 71. Sarge/stable has a really old version. In particular I am running unstable as I had too many funny errors (including this one) - but etch should be fine.
If running another distribution check this also as it is a real requirement.
To find the latest version of udev required check
Documentation/Changesdevinfo -v
udevinfo, version 074dpkg -s
Package: udev
Status: install ok installed
Priority: extra
Section: admin
Installed-Size: 1072
Maintainer: Marco d'Itri <[email protected]>
Architecture: amd64
Version: 0.074-3Quoted 5 lines
Quoted 2 lines
Interestingly the same udev works fine with 14-rc4-mm1. I'll check the debian bugs.
There does not seem to be anything that fits this reported as a debian bug. Where is the udev bugs list?
For Debian? I have no idea as I do not use it :)
For general udev issues/queries try the linux-hotplug-devel mailing list.
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
Oh, and are you sure you actually have the proper module loaded?
Think only the mousedev module is not loaded. Once I modprobe it the mouse works and the
/dev/input/miceappears. The mouse works normally with all buttons and wheels acting normal.Then you just need to make sure that module is loaded properly, which doesn't sound like a udev issue :)
Then its a kernel problem.
It works with the _same_ user space in 2.6.14-rc4-mm1 and fails with 15-rc1-mm2... This implies either something is broken in the kernel or udev is not doing its job with the new (input?) changes. Since I switched to udev this summer I have not had to load many modules certainly not mousedev.
I'll do a bit of experimenting this weekend to see if I cannot figure out more about what is happening.
Thanks for the help
Ed
Quoted 11 lines
It works with the _same_ user space in 2.6.14-rc4-mm1 and fails with 15-rc1-mm2... This implies either something is broken in the kernel or udev is not doing its job with the new (input?) changes. Since I switched to udev this summer I have not had to load many modules certainly not mousedev.
I'll do a bit of experimenting this weekend to see if I cannot figure out more about what is happening.
Thanks for the help
Ed
I would suggest using git-bisect to find the problem - I do know that the problem was/is in Linus Torvalds tree. It was fine around 2.6.13 timeframe and broke sometime after this. I find git-bisect very powerful for testing these types of bugs.
I was going to test myself in this way but the machine which experienced the problem caught fire!! I know this sounds like the dog ate my homework but unfortunately it was true and it was a machine I borrowed too....
Ian
--
Ian McDonald
http://wand.net.nz/~iam4
WAND Network Research Group
University of Waikato
New Zealand
Quoted 47 lines · Ed Tomlinson
Quoted 46 lines · Greg KH
Quoted 45 lines · Ed Tomlinson
Quoted 43 lines · Greg KH
Quoted 30 lines · Ed Tomlinson
Quoted 29 lines · Ed Tomlinson
Quoted 6 lines · Ian McDonald
Quoted 5 lines · Greg KH
Are you using debian?
If so, what version of udev are you using? There are some known reported problems with this, so I would suggest referring to the udev bug list.Quoted 8 lines
In particular check the version requirements for udev - you need to be on a version greater than or equal to 71. Sarge/stable has a really old version. In particular I am running unstable as I had too many funny errors (including this one) - but etch should be fine.
If running another distribution check this also as it is a real requirement.
To find the latest version of udev required check
Documentation/Changesdevinfo -v
udevinfo, version 074dpkg -s
Package: udev
Status: install ok installed
Priority: extra
Section: admin
Installed-Size: 1072
Maintainer: Marco d'Itri <[email protected]>
Architecture: amd64
Version: 0.074-3Quoted 5 lines
Quoted 2 lines
Interestingly the same udev works fine with 14-rc4-mm1. I'll check the debian bugs.
There does not seem to be anything that fits this reported as a debian bug. Where is the udev bugs list?
For Debian? I have no idea as I do not use it :)
For general udev issues/queries try the linux-hotplug-devel mailing list.
Oh, and are you sure you actually have the proper module loaded?
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
Think only the mousedev module is not loaded. Once I modprobe it the mouse works and the
/dev/input/miceappears. The mouse works normally with all buttons and wheels acting normal.Then you just need to make sure that module is loaded properly, which doesn't sound like a udev issue :)
Then its a kernel problem.
Or a broken userspace configuration that just happened to work previously :)
I really don't know which one this is, but as it seems it only is showing up on Debian systems...
thanks,
greg k-h
Quoted 10 lines
Or a broken userspace configuration that just happened to work previously :)
I really don't know which one this is, but as it seems it only is showing up on Debian systems...
thanks,
greg k-h
OK. Have got quite a bit further in tracking this down and will now log with Debian somehow.
It is definitely userspace but I don't know enough about that to say whether it is udev (Debian rules) or something else.
I used git-bisect with 2.6.14 and 2.6.15-rc1 as start and end points. In the end the patch which caused it to break was the final one - just altering the Makefile with the version number. I've reverified as well by going back to 2.6.15-rc1 and just altering it to 2.6.14 and the problem (mousedev not loaded automatically and no /dev/input /mice) disappears. I almost thought I'd made a mistake in my testing until I manually altered that makefile!!
It is definitely not a kernel issue in my opinion.
Ian
--
Ian McDonald
http://wand.net.nz/~iam4
WAND Network Research Group
University of Waikato
New Zealand
Quoted 1 line · Ian McDonald
It is definitely not a kernel issue in my opinion.
Thank you for following up on this and letting us know.
greg k-h
Quoted 7 lines · Greg KH
Quoted 1 line · Ian McDonald
It is definitely not a kernel issue in my opinion.
Thank you for following up on this and letting us know.
greg k-h
It is in debian bug system as bug 340202. I have just posted more information to it which should appear soon:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=340202
--
Ian McDonald
http://wand.net.nz/~iam4
WAND Network Research Group
University of Waikato
New Zealand