Discussion:
2.6.14-rc4-mm1
(too old to reply)
Andrew Morton
2005-10-16 22:50:12 UTC
Permalink
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/

- Lots of i2c, PCI and USB updates

- Large input layer update to convert it all to dynamic input_dev allocation

- Significant x86_64 updates

- MD updates

- Lots of core memory management scalability rework




Changes since 2.6.14-rc2-mm2:


linus.patch
git-acpi.patch
git-agpgart.patch
git-cifs.patch
git-cpufreq.patch
git-cryptodev.patch
git-drm.patch
git-ia64.patch
git-audit.patch
git-jfs.patch
git-libata-all.patch
git-mtd.patch
git-netdev-all.patch
git-nfs.patch
git-ntfs.patch
git-ocfs2.patch
git-scsi-misc.patch
git-sas.patch

External trees

-fix-pgdat_list-connection-in-init_bootmem.patch
-x86_64-fix-the-bp-node_to_cpumask.patch
-x86_64-numa-node-topology-fix.patch
-make-if_etherh-compile-with-config_sysctl=n.patch
-x86-x86_64-cpuid-workaround-for-intel-cpu.patch
-aio-lock-around-kiocbtrykick.patch
-aio-remove-unlocked-task_list-test-and-resulting-race.patch
-aio-avoid-extra-aio_readwrite-call-when-ki_left-==-0.patch
-intelfb-fix-regression-blank-display-from-ioremap-patch.patch
-s3c2410fb-minor-warning-fix.patch
-ppc64-smu-driver-locking-mistake.patch
-x86-hw_irqh-warning-fix.patch
-v4l-dvico-fusionhdtv5-lite-gpio-fix.patch
-uml-fix-build-dependencies-with-kbuild-output.patch
-uml-fix-page-faults-in-skas3-mode.patch
-uml-clear-skas0-3-flags-when-running-in-tt-mode.patch
-uml-revert-run-mconsole-sysrq-in-process-context.patch
-uml-remove-empty-hostfs_truncate-method.patch
-fuse-check-o_direct.patch
-ioc4_serial-remove-bogus-error-message.patch
-remove-preempt_disable-from-powernow-k8.patch
-drivers-base-use-kzalloc-instead-of-kmallocmemset-gregkh-bits.patch
-net-reorder-some-hot-fields-of-struct-net_device.patch
-pci-block-config-access-during-bist.patch
-ipr-block-config-access-during-bist.patch
-sisusb-warning-fix.patch
-new-powerpc-4xx-on-chip-ethernet-controller-driver.patch
-binfmt_elf-bss-padding-fix.patch
-ehci-kexec-reboot-fix.patch
-dell_rbu-changes-in-packet-update-mechanism.patch
-maintainers-sbp2-driver-is-not-orphaned.patch
-sbp2-fix-deadlocks-and-delays-on-device-removal-rmmod.patch
-sbp2-default-to-serialize_io=1.patch
-ieee1394-reorder-activities-after-bus-reset-fixes-device-detection.patch
-ieee1394-skip-unnecessary-pause-when-scanning-config-roms.patch
-ieee1394-fix-for-debug-output.patch
-ieee1394-use-time_before.patch
-ieee1394-trivial-edits-of-a-few-comments.patch
-ieee1394-remove-superfluous-include-in-csr1212.patch
-eth1394-workaround-limitation-in-rawiso-routines.patch
-ieee1394-delete-legacy-module-aliases.patch
-ohci1394-less-noise-in-dmesg.patch
-nfsacl-solaris-vxfs-compatibility-fix.patch

Merged

+timers-add-missing-compensation-for-hz-==-250.patch

Timer accuracy fix

+list-add-missing-rcu_dereference-on-first-element.patch

RCU safety in list operations

+ip6_tables-build-fix.patch

net build fix

+svgatextmode-fix.patch

VGA text mode fix

+fix-vpx3220-offset-issue-in-secam.patch
+fix-black-white-only-svideo-input-in-vpx3220.patch

v4l driver fixes

+revert-orinoco-information-leakage-due-to-incorrect-padding.patch
+better-fixup-for-the-orinoco-driver.patch

Fix orinoco more cleanly

+acpi-cleanup-u32-flags-in-spin_lock-calls.patch

ACPI cleanup

+git-cifs-build-fix.patch

Fix git-cifs.patch

+gregkh-driver-aoe-01.patch
+gregkh-driver-aoe-02.patch
+gregkh-driver-driver-kobject-typo.patch
+gregkh-driver-driver-porting-typo.patch
+gregkh-driver-kobject-fix-gfp-flags-type.patch
+gregkh-driver-driver-model-wakeup-01.patch
+gregkh-driver-driver-model-wakeup-02.patch
+gregkh-driver-i2o-remove-i2o_device_class.patch
+gregkh-driver-coldplug-emit-hotplug-events-from-sysfs.patch
+gregkh-driver-class_dev_child.patch
+gregkh-driver-class_device_create_api_fixup.patch
+gregkh-driver-input-remove-devfs.patch
+gregkh-driver-input-sysfs-intregration.patch
+gregkh-driver-input-convert-to-dynamic-mouse.patch
+gregkh-driver-input-convert-to-dynamic-keyboard.patch
+gregkh-driver-input-convert-to-dynamic-usb.patch
+gregkh-driver-input-convert-to-dynamic-ucb1x00-ts.patch
+gregkh-driver-input-convert-to-dynamic-touchscreen.patch
+gregkh-driver-input-convert-to-dynamic-sonypi.patch
+gregkh-driver-input-convert-to-dynamic-onetouch.patch
+gregkh-driver-input-convert-to-dynamic-misc.patch
+gregkh-driver-input-convert-to-dynamic-media.patch
+gregkh-driver-input-convert-to-dynamic-macintosh.patch
+gregkh-driver-input-convert-to-dynamic-konicawc.patch
+gregkh-driver-input-convert-to-dynamic-joystick.patch
+gregkh-driver-input-convert-to-dynamic-bluetooth.patch
+gregkh-driver-input-convert-to-dynamic-beep.patch
+gregkh-driver-input-show-sysfs-path-in-proc.patch
+gregkh-driver-input-export-input_dev-data-in-sysfs.patch

driver tree updates

+gregkh-i2c-i2c-viapro-01.patch
+gregkh-i2c-i2c-viapro-02.patch
+gregkh-i2c-i2c-viapro-03.patch
+gregkh-i2c-i2c-viapro-04.patch
+gregkh-i2c-i2c-viapro-05.patch
+gregkh-i2c-i2c-viapro-06.patch
+gregkh-i2c-i2c-viapro-07.patch
+gregkh-i2c-i2c-viapro-08.patch
+gregkh-i2c-i2c-01.patch
+gregkh-i2c-i2c-02.patch
+gregkh-i2c-i2c-03.patch
+gregkh-i2c-i2c-04.patch
+gregkh-i2c-i2c-05.patch
+gregkh-i2c-i2c-06.patch
+gregkh-i2c-i2c-07.patch
+gregkh-i2c-i2c-08.patch
+gregkh-i2c-i2c-09.patch
+gregkh-i2c-i2c-10.patch
+gregkh-i2c-i2c-11.patch
+gregkh-i2c-i2c-12.patch
+gregkh-i2c-i2c-13.patch
+gregkh-i2c-i2c-14.patch
+gregkh-i2c-i2c-15.patch
+gregkh-i2c-i2c-16.patch
+gregkh-i2c-i2c-device-id.patch

i2c tree updates

-use-incbin-for-config_datagz.patch

Dropped - it broke the build

+libata-build-fix.patch

Fix git-libata-all.patch

+e1000_intr-build-fix.patch
+git-netedv-all-s2io-build-fix.patch
+git-netdev-all-e1000-fix.patch

Fix git-netdev-all.patch

+gregkh-pci-pci-ich6-acpi-quirk.patch
+gregkh-pci-pci-block-config-access-during-BIST-01.patch
+gregkh-pci-pci-block-config-access-during-BIST-02.patch
+gregkh-pci-pci-cleanup-need_restore-switch.patch
+gregkh-pci-pci-hotplug-enable_device-01.patch
+gregkh-pci-pci-hotplug-enable_device-02.patch
+gregkh-pci-pci-ich6-smbus-quirk.patch
+gregkh-pci-pci-ids-01.patch
+gregkh-pci-pci-ids-02.patch
+gregkh-pci-pci-ids-03.patch
+gregkh-pci-pci-rpaphp-api-fix.patch
+gregkh-pci-pci-quirk-hpd530.patch

PCI tree updates

+areca-raid-linux-scsi-driver-update-3.patch

Update areca-raid-linux-scsi-driver.patch

+gregkh-usb-usb-ehci-clean-shutdown.patch
+gregkh-usb-usb-ftdi-new-id.patch
+gregkh-usb-usb-rdl8150-oops-fix.patch
+gregkh-usb-usb-usb_bulk_message-handle-interrupt.patch
+gregkh-usb-usb-uhci-comment-cleanup.patch
+gregkh-usb-usb-sisusb-warning-fix.patch
+gregkh-usb-usb-gadget-file-storage-use-kthread.patch
+gregkh-usb-usb-wHubCharacteristics-fix.patch
+gregkh-usb-usb-ftdi_sio-id.patch
+gregkh-usb-usb-pegasus-id.patch
+gregkh-usb-usb-safe_serial-preprocessor-fix.patch
+gregkh-usb-usb-storage-Kconfig-note-cleanup.patch
+gregkh-usb-usb-storage-hp8200-device-detect-fix.patch
+gregkh-usb-usb-storage-shuttle_usbat-cleanups.patch
+gregkh-usb-usb-storage-unusual-01.patch
+gregkh-usb-usb-storage-unusual-02.patch
+gregkh-usb-usb-storage-unusual-03.patch
+gregkh-usb-usb-touchkit-id.patch
+gregkh-usb-usb-gadget-g_file_storage-race-fix.patch
+gregkh-usb-usb-uhci-unify-bios-handoff-code.patch

USB tree updates

-x86_64-no-idle-tick.patch
-x86_64-nohpet.patch
-x86_64-pat-base.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-acpi-return.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-no-idle-tick-fix.patch
-x86_64-no-idle-tick-fix-2.patch
-x86_64-mce-thresh-fix.patch
-x86_64-mce-thresh-fix-2.patch
+x86_64-vect-share-build-fix.patch

x86_64 tree updates

+mm-tlb_finish_mmu-forget-rss-fix.patch

Fix mm-tlb_finish_mmu-forget-rss.patch

+core-remove-pagereserved.patch

Remove PageReserved()

+mm-copy_one_pte-inc-rss.patch
+mm-zap_pte_range-dec-rss.patch
+mm-do_swap_page-race-major.patch
+mm-do_mremap-current-mm.patch
+mm-zap_pte-out-of-line.patch
+mm-update_hiwaters-just-in-time.patch
+mm-mm_struct-hiwaters-moved.patch
+mm-ia64-use-expand_upwards.patch
+mm-init_mm-without-ptlock.patch
+mm-ptd_alloc-inline-and-out.patch
+mm-ptd_alloc-take-ptlock.patch
+mm-arches-skip-ptlock.patch
+mm-page-fault-handler-locking.patch
+mm-pte_offset_map_lock-loops.patch
+mm-flush_tlb_range-outside-ptlock.patch
+mm-unlink-vma-before-pagetables.patch
+mm-unmap_vmas-with-inner-ptlock.patch
+mm-unmap_vmas-with-inner-ptlock-fix.patch
+mm-xip_unmap-zero_page-fix.patch
+mm-rmap-with-inner-ptlock.patch
+mm-kill-check_user_page_readable.patch
+mm-follow_page-with-inner-ptlock.patch

Mainly page_table_lock scalability improvements

+hugetlb-remove-repeated-code.patch

hugetlb cleanup

+vmalloc_node.patch

New version of vmalloc_node()

+mm-implement-swap-prefetching.patch
+mm-implement-swap-prefetching-default-y.patch
+mm-implement-swap-prefetching-tweaks.patch
+mm-implement-swap-prefetching-tweaks-2.patch

Con's swap prefetching code

+implement-sys_-do_-layering-in-the-memory-policy-layer.patch
+implement-sys_-do_-layering-in-the-memory-policy-layer-tidy.patch
+remove-policy-contextualization-from-mbind.patch

mempolicy updates

+sis900-add-wake-on-lan-support.patch

sis900 feature work

+e1000-use-vmalloc_node.patch

Use vmalloc_node() in e1000

+ppc32-nvram-driver-for-chrp.patch
+add-modalias-to-macio-sysfs-attributes.patch
+add-modalias-for-pmac-network-drivers.patch
+new-powerpc-4xx-on-chip-ethernet-controller-driver.patch
+add-maintainer-entry-for-the-new-powerpc-4xx-on-chip-ethernet-controller-driver.patch
+chrp_pegasos_eth-added-marvell-discovery.patch
+chrp_pegasos_eth-added-marvell-discovery-tidy.patch
+chrp_pegasos_eth-added-marvell-discovery-tidy-2.patch

ppc32 updates

+ppc64-add-cpufreq-support-for-smu-based-g5.patch
+ppc64-support-retreiving-missing-smu-partitions.patch
+ppc64-thermal-control-for-smu-based-machines.patch
+ppc64-boot-remove-include-from-lib-zlib_inflate-inflatec.patch
+ppc64-boot-remove-include-from-include-linux-zutilh.patch
+ppc64-boot-missing-include-for-size_t.patch
+ppc64-boot-remove-zlib.patch
+ppc64-boot-remove-need-for-imagesizec.patch
+ppc64-boot-move-gunzip-function-before-use.patch
+ppc64-boot-bootfiles-depend-on-linker-script.patch
+ppc64-boot-cleanup-linker-script.patch
+ppc64-boot-use-memset-to-clear-bss.patch
+ppc64-boot-fix-typo-in-asm-comments.patch
+ppc64-boot-remove-global-initializers.patch
+ppc64-boot-make-the-zimage-relocateable.patch
+ppc64-boot-proof-that-reloc-works.patch
+ppc64-boot-print-firmware-provided-stackpointer.patch
+ppc64-ac-power-handling-broken-for-desktops.patch
+ppc64-make-dma_addr_t-64-bits.patch
+ppc64-compile-nls_cp437-and-nls_iso8859_1-into-the-kernel-in-defconfig.patch

ppc64 updates

+es7000-platform-update-i386.patch
+i386-io_apicc-memorize-at-bootup-where-the-i8259-is-connected.patch
+i386-nmi_watchdog-merge-check_nmi_watchdog-fixes-from-x86_64.patch
+i386-move-apic-init-in-init_irqs.patch
+i386-move-apic-init-in-init_irqs-tidy.patch
+i386-kexec-on-panic-dont-shutdown-the-apics.patch
+x86-vmx-cpu-feature-detection.patch
+clean-up-mtrr-compat-ioctl-code.patch

x86 updates

-x86_64-init-and-zap-low-address-mappings-on-demand-for-cpu-hotplug.patch
+x86_64-io_apicc-memorize-at-bootup-where-the-i8259-is.patch
+x86_64-io_apicc-memorize-at-bootup-where-the-i8259-is-fix.patch
+x86_64-move-apic-init-in-init_irqs-take-2.patch
+x86_64-move-apic-init-in-init_irqs-take-2-tidy.patch

x86_64 updates

+arm-fix-bogus-cast-in-ixp2000-i-o-macro.patch
+arm-fix-ixp2x00-defconfig-nr_uarts-options.patch

ARM fixes

+swsusp-rework-image-freeing.patch
+swsusp-move-snapshot-functionality-to-separate-file.patch
+swsusp-rework-memory-freeing-on-resume.patch

swsusp updates

+get-rid-of-the-obsolete-tri-level-suspend-resume-callbacks.patch
+get-rid-of-the-obsolete-tri-level-suspend-resume-callbacks-sound-fix.patch

Power management cleanups

+m32r-remove-unused-instructions.patch
+m32r-fix-if-warnings.patch
+m32r-noncache_offset-in-_port2addr.patch
+m32r-smc91x-driver-update.patch

m32r updates

+s390-ccw-export-modalias.patch

s390 fix

-e1000-numa-aware-allocation-of-descriptors-v2.patch

Dropped

-pc-speaker-add-snd_silent.patch

Dropped (compile errors due to input code changes)

+ntp-whitespace-cleanup.patch

Clean up timer.c

+remove-timer-debug-fields-fix.patch

Fix remove-timer-debug-fields.patch

-msi-interrupts-disallow-when-no-lapic-ioapic-support.patch

Dropped

-hpet-disallow-zero-interrupt-frequency.patch

Dropped

+fuse-clean-up-dead-code-related-to-nfs-exporting.patch

FUSE cleanup

+proc-fix-of-error-path-in-proc_get_inode.patch

procfs fix

+cpuset-cleanup.patch

Clean up cpuset code

+ptrace-coredump-exit_group-deadlock.patch

ptrace fix

+fs-error-case-fix-in-__generic_file_aio_read.patch

AIO fix

+vm-remove-redundant-assignment-from-__pagevec_release_nonlru.patch
+vm-remove-unused-broken-page_pte-macros.patch

VM cleanups

+keys-export-user-defined-keyring-operations.patch
+keys-export-user-defined-keyring-operations-update.patch
+keys-add-lsm-hooks-for-key-management.patch

key management feature work

+ide-cd-mini-cleanup-of-casts.patch

ide-cd.c cleanups

+cleanup-for-kernel-printkc.patch

printk.c cleanups

+write_inode_now-write-inode-if-not-bdi_cap_no_writeback.patch

write_inode_now() fix (I think this is wrong)

+pf_dead-cleanup.patch
+pf_dead-cleanup-fixes.patch

PF_DEAD cleanup

+coredump_wait-cleanup.patch

coredump_wait() cleanup

+locking-problems-while-ext3fs_debug-on.patch

ext3 fixes

+ioc4-serial-support-mostly-cleanup.patch

ioc4 driver cleanups

+sparse-cleanups-null-pointers-c99-struct-init.patch

sparse fixes

+wait4-ptrace_attach-race-fix.patch

wait4() race fix

+small-kconfig-help-text-correction-for-config_frame_pointer.patch

Kconfig text fix

+fuse-spelling-fixes.patch
+fuse-remove-unused-define.patch

FUSE fixlets

+added-a-receive_abort-to-the-marvell-serial-driver.patch

Serial driver update

+fix-de_thread-vs-do_coredump-deadlock.patch

Fix coredumping deadlock

+telecom-clock-driver-for-mpcbl0010-atca-computer-blade.patch

New driver

+ext3-sparse-fixes.patch
+ext3-sparse-fixes-2.patch

ext3 sparse fixes

+remove-orphaned-tiocgdev-compat-ioctl.patch

Remove dead compat code

+jiffies_64-cleanup.patch

time cleanup

+ext3_show_options-warning-fix.patch

ext3 warning fix

+firmware-fix-all-kernel-doc-warnings.patch

kenreldoc fixes

+edac-atomic-scrub-operations.patch
+edac-atomic-scrub-operations-fix.patch
+edac-drivers-for-amd-76x-and-intel-e750x-e752x.patch
+edac-drivers-for-intel-i82860-i82875.patch
+edac-drivers-for-radisys-82600.patch
+edac-drivers-for-radisys-82600-gregkh-borkage.patch
+edac-core-edac-support-code.patch
+edac-core-edac-support-code-ifdef-warnings.patch
+edac-core-edac-support-code-fixes.patch

error detection and correction drivers

+shpchp-use-the-pci-core-for-hotplug-resource-management.patch
+shpchp-remove-redundant-display-of-pci-device-resources.patch
+shpchp-reduce-dependence-on-acpi.patch
+shpchp-detect-shpc-capability-before-doing-a-lot-of-work.patch
+shpchp-dont-save-pci-config-for-hotplug-slots-devices.patch
+shpchp-remove-redundant-data-structures.patch
+shpchp-miscellaneous-cleanups.patch
+shpchp-reduce-debug-message-verbosity.patch
+shpchp-fix-oops-at-driver-unload.patch

hotplug driver updates

+hpet-disallow-zero-interrupt-frequency.patch
+hpet-make-frequency-calculations-32-bit-safe.patch
+hpet-fix-hpet_info-calls-from-kernel-space.patch
+hpet-fix-division-by-zero-in-hpet_info.patch
+hpet-fix-uninitialized-variable-in-hpet_register.patch
+hpet-fix-access-to-multiple-hpet-devices.patch
+hpet-remove-superfluous-indirections.patch
+hpet-simplify-initialization-message.patch

HPET driver updates

+kprobes-rearrange-preempt_disable-enable-calls.patch
+kprobes-track-kprobe-on-a-per_cpu-basis-base-changes.patch
+kprobes-track-kprobe-on-a-per_cpu-basis-i386-changes.patch
+kprobes-track-kprobe-on-a-per_cpu-basis-ia64-changes.patch
+kprobes-track-kprobe-on-a-per_cpu-basis-ppc64-changes.patch
+kprobes-track-kprobe-on-a-per_cpu-basis-sparc64-changes.patch
+kprobes-track-kprobe-on-a-per_cpu-basis-x86_64-changes.patch
+kprobes-use-rcu-for-unregister-synchronization-base-changes.patch
+kprobes-use-rcu-for-unregister-synchronization-arch-changes.patch

kprobes work

+knfsd-fix-setattr-on-symlink-error-return.patch
+knfsd-restore-functionality-to-read-from-file-in-proc-fs-nfsd.patch
+knfsd-allow-run-time-selection-of-nfs-versions-to-export.patch
+knfsd-allow-run-time-selection-of-nfs-versions-to-export-fix.patch
+knfsd-fix-some-minor-sign-problems-in-nfsd-xdr.patch

knfsd updates

+sched-disable-preempt-in-idle-tasks-2-fix.patch
+sched-disable-preempt-in-idle-tasks-2-mips-fix.patch

Fix sched-disable-preempt-in-idle-tasks-2.patch

+v4l-cleanup-cx88-fix-sparse-warnings.patch

v4l sparse fixes

-reiser4-export-pagevec-funcs.patch

CIFS patches export all these things now

+reiser4-big-update-spin_macros-fix.patch

reiser4 fix

+siimage-enable-interrupts-on-adaptec-sa-1210-card.patch
+rocketpoint-1520-fails-clock-stabilization.patch

IDE fixes

+au1100fb-use-preprocessor-instruction-for-error.patch
+nvidiafb-fix-mode-setting-ppc-support.patch
+nvidiafb-add-flat-panel-dither-support.patch
+intelfb-extend-partial-support-of-i915g-to-include-i915gm.patch
+radeonfb-prevent-spurious-recompilations.patch

fbdev updates

+fix-dm-snapshot-tutorial-in-documentation.patch

DM documentation

+md-initial-sysfs-support-for-md.patch
+md-extend-md-sysfs-support-to-component-devices.patch
+md-add-kobject-sysfs-support-to-raid5.patch
+md-allow-a-manual-resync-with-md.patch
+md-teach-raid5-the-difference-between-check-and-repair.patch
+md-provide-proper-rcu_dereference--rcu_assign_pointer-annotations-in-md.patch
+md-fix-ref-counting-problems-with-kobjects-in-md.patch
+md-minor-md-fixes.patch
+md-change-raid5-sysfs-attribute-to-not-create-a-new-directory.patch
+md-improvements-to-raid5-handling-of-read-errors.patch
+md-convert-faulty-and-in_sync-fields-to-bits-in-flags-field.patch
+md-make-md-on-disk-bitmaps-not-host-endian.patch
+md-support-bio_rw_barrier-for-md-raid1.patch

RAID updates

+documentation-sparsetxt-mention-cf=-wbitwise.patch
+ksymoops-related-docs-update.patch
+doc-msi-howto-cleanups.patch
+jbd-doc-fix-some-kernel-doc-warnings.patch
+kernel-doc-fix-some-kernel-api-warnings.patch

Documentation updates

+drivers-cdrom-kmalloc-memset-kzalloc-conversion.patch
+cpufreq-kmalloc-memset-kzalloc-conversion.patch
+drivers-dio-kmalloc-memset-kzalloc-conversion.patch
+drivers-eisa-kmalloc-memset-kzalloc-conversion.patch
+drivers-fc4-kmalloc-memset-kzalloc-conversion.patch
+drivers-firmware-kmalloc-memset-kzalloc-conversion.patch
+hwmon-kmalloc-memset-kzalloc-conversion.patch
+i2c-kmalloc-memset-kzalloc-conversion.patch
+ide-kmalloc-memset-kzalloc-conversion.patch
+ide-kmalloc-memset-kzalloc-conversion-fix.patch
+bluetooth-kmalloc-memset-kzalloc-conversion.patch

use kzalloc()

+kfree-cleanup-drivers-scsi.patch
+kfree-cleanup-drivers-net.patch
+kfree-cleanup-net.patch
+kfree-cleanup-drivers-mtd.patch
+kfree-cleanup-drivers-char.patch
+kfree-cleanup-drivers-isdn.patch
+kfree-cleanup-drivers-s390.patch
+kfree-cleanup-drivers-media.patch
+kfree-cleanup-misc-remaining-drivers.patch
+kfree-cleanup-fs.patch
+kfree-cleanup-arch.patch
+kfree-cleanup-security.patch
+kfree-cleanup-sound.patch
+kfree-cleanup-documentation.patch

kfree(NULL) is legal

+fs-superc-unexport-user_get_super.patch

unexport user_get_super()

+isicom-whitespace-cleanup.patch
+isicom-type-conversion-and-variables-deletion.patch
+isicom-other-little-changes.patch
+isicom-pci-probing-added.patch
+isicom-firmware-loading.patch
+isicom-more-whitespaces-and-coding-style.patch

isicom driver updates (needs updating)


All 862 patches:

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/patch-list


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Dominik Karall
2005-10-17 00:10:04 UTC
Permalink
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.
6.14-rc4-mm1/
This patch should fix a compile error for fs/ntfs/namei.o, caused by a missing
header for u32 in include/asm/atomic.h.

I hope it's correctly fixed this way.

dominik
Michal Piotrowski
2005-10-17 00:20:10 UTC
Permalink
Hi,
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
[snip]

I have noticed some warnings while "make modules_install"

if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F
System.map 2.6.14-rc4-mm1; fi
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/serial_core.ko
ignored, due to loop
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250_pnp.ko ignored,
due to loop
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250_pci.ko ignored,
due to loop
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250_acpi.ko
ignored, due to loop
WARNING: Loop detected:
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250.ko needs
serial_core.ko which needs 8250.ko again!
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250.ko ignored, due
to loop

Regards,
Michal Piotrowski
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Andrew Morton
2005-10-17 03:30:08 UTC
Permalink
Post by Michal Piotrowski
Hi,
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
[snip]
I have noticed some warnings while "make modules_install"
if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F
System.map 2.6.14-rc4-mm1; fi
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/serial_core.ko
ignored, due to loop
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250_pnp.ko ignored,
due to loop
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250_pci.ko ignored,
due to loop
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250_acpi.ko
ignored, due to loop
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250.ko needs
serial_core.ko which needs 8250.ko again!
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250.ko ignored, due
to loop
Beats me. Please send .config.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Michal Piotrowski
2005-10-17 06:10:08 UTC
Permalink
Hi,
Post by Andrew Morton
Beats me. Please send .config.
Here is my -mm config:
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.14-rc4-mm1
# Mon Oct 17 01:46:39 2005
#
CONFIG_X86_32=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SWAP_PREFETCH=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_SYSCTL=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_CPUSETS is not set
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
CONFIG_MPENTIUM4=y
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HPET_TIMER is not set
CONFIG_SMP=y
CONFIG_NR_CPUS=2
CONFIG_SCHED_SMT=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=m
CONFIG_X86_MCE_P4THERMAL=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_X86_REBOOTFIXUPS is not set
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_IRQBALANCE=y
# CONFIG_REGPARM is not set
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_PHYSICAL_START=0x100000
CONFIG_KEXEC=y

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
# CONFIG_ACPI_BUTTON is not set
CONFIG_ACPI_VIDEO=m
# CONFIG_ACPI_HOTKEY is not set
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=2001
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_X86_PM_TIMER is not set
# CONFIG_ACPI_CONTAINER is not set

#
# APM (Advanced Power Management) BIOS Support
#
CONFIG_APM=m
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_RTC_IS_GMT is not set
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCIEPORTBUS is not set
# CONFIG_PCI_MSI is not set
CONFIG_PCI_LEGACY_PROC=y
# CONFIG_PCI_DEBUG is not set
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_HOTPLUG_CPU is not set

#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_MISC=m

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=m
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=m
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
CONFIG_NET_KEY=m
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
# CONFIG_NET_IPGRE_BROADCAST is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_TUNNEL=m
# CONFIG_INET_DIAG is not set
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_BIC=y
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_INET6_TUNNEL=m
CONFIG_IPV6_TUNNEL=m
# CONFIG_NETFILTER is not set

#
# DCCP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_IEEE80211 is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set

#
# Connector - unified userspace <-> kernelspace linker
#
CONFIG_CONNECTOR=m

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_GSC is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
# CONFIG_PNPACPI is not set

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
# CONFIG_BLK_DEV_RAM is not set
CONFIG_BLK_DEV_RAM_COUNT=16
# CONFIG_LBD is not set
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
CONFIG_CDROM_PKTCDVD_WCACHE=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=m
CONFIG_IOSCHED_CFQ=m
CONFIG_DEFAULT_AS=y
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="anticipatory"
# CONFIG_ATA_OVER_ETH is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=m
CONFIG_BLK_DEV_IDE=m

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=m
# CONFIG_IDEDISK_MULTI_MODE is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=m
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=m
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=m
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set

#
# SCSI Transport Layers
#
# CONFIG_SAS_CLASS is not set

#
# SCSI low-level drivers
#
# CONFIG_ISCSI_TCP is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
CONFIG_SCSI_SATA=y
# CONFIG_SCSI_ATA_ADMA is not set
# CONFIG_SCSI_SATA_AHCI is not set
# CONFIG_SCSI_SATA_SVW is not set
CONFIG_SCSI_ATA_PIIX=y
# CONFIG_SCSI_SATA_MV is not set
# CONFIG_SCSI_SATA_NV is not set
# CONFIG_SCSI_PDC_ADMA is not set
# CONFIG_SCSI_SATA_QSTOR is not set
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_SX4 is not set
# CONFIG_SCSI_SATA_SIL is not set
# CONFIG_SCSI_SATA_SIL24 is not set
# CONFIG_SCSI_SATA_SIS is not set
# CONFIG_SCSI_SATA_ULI is not set
# CONFIG_SCSI_SATA_VIA is not set
# CONFIG_SCSI_SATA_VITESSE is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA24XX is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m
# CONFIG_NET_SB1000 is not set

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# PHY device support
#

#
# Ethernet (10 or 100Mbit)
#
# CONFIG_NET_ETHERNET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
CONFIG_SK98LIN=m
# CONFIG_TIGON3 is not set
# CONFIG_BNX2 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_CHELSIO_T1 is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
# CONFIG_HOSTAP is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
CONFIG_KGDBOE=y
CONFIG_NETPOLL=y
CONFIG_NETPOLL_RX=y
CONFIG_NETPOLL_TRAP=y
CONFIG_NET_POLL_CONTROLLER=y

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
CONFIG_SERIO_PCIPS2=m
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=m
CONFIG_SERIAL_8250_ACPI=y
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=m
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_PRINTER is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=m
CONFIG_NVRAM=m
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=y
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# TPM devices
#
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set

#
# I2C support
#
CONFIG_I2C=y
# CONFIG_I2C_CHARDEV is not set

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set

#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set

#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_RTC8564 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set

#
# Hardware Monitoring support
#
# CONFIG_HWMON is not set
# CONFIG_HWMON_VID is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia Capabilities Port drivers
#

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_SOFT_CURSOR=y
# CONFIG_FB_MACMODES is not set
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
CONFIG_FB_NVIDIA=y
CONFIG_FB_NVIDIA_I2C=y
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_CYBLA is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_BACKLIGHT_CLASS_DEVICE=m
CONFIG_BACKLIGHT_DEVICE=y
CONFIG_LCD_CLASS_DEVICE=m
CONFIG_LCD_DEVICE=y

#
# Speakup console speech
#
# CONFIG_SPEAKUP is not set

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_GENERIC_DRIVER=y

#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
CONFIG_SND_MPU401=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_AC97_BUS=m

#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_CS5535AUDIO is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_HDA_INTEL is not set

#
# USB devices
#
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=m
# CONFIG_USB_SL811_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_OBSOLETE_OSS_USB_DRIVER is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#

#
# may also be needed; see USB_STORAGE Help for more information
#
# CONFIG_USB_STORAGE is not set

#
# USB Input Devices
#
# CONFIG_USB_HID is not set

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_ACECAD is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_ITMTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_YEALINK is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set
# CONFIG_USB_KEYSPAN_REMOTE is not set
# CONFIG_USB_APPLETOUCH is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set

#
# Video4Linux support is needed for USB Multimedia device support
#

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_MON is not set

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_GOTEMP is not set
# CONFIG_USB_PHIDGETKIT is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TEST is not set

#
# USB DSL modem support
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# MMC/SD Card support
#
# CONFIG_MMC is not set

#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set

#
# SN Devices
#

#
# EDAC - error detection and reporting (RAS)
#
# CONFIG_EDAC is not set
# CONFIG_EDAC_POLL is not set

#
# Distributed Lock Manager
#
CONFIG_DLM=m
CONFIG_DLM_DEVICE=m
CONFIG_DLM_DEBUG=y

#
# File systems
#
CONFIG_EXT2_FS=m
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT2_FS_XIP=y
CONFIG_FS_XIP=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISER4_FS=m
# CONFIG_REISER4_DEBUG is not set
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
CONFIG_JFS_STATISTICS=y
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
CONFIG_XFS_EXPORT=y
CONFIG_XFS_QUOTA=m
CONFIG_XFS_SECURITY=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
CONFIG_OCFS2_FS=m
# CONFIG_MINIX_FS is not set
CONFIG_ROMFS_FS=m
CONFIG_INOTIFY=y
CONFIG_QUOTA=y
CONFIG_QFMT_V1=m
CONFIG_QFMT_V2=m
CONFIG_QUOTACTL=y
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=m

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
CONFIG_RELAYFS_FS=m
CONFIG_CONFIGFS_FS=m

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ASFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
# CONFIG_NFSD_V4 is not set
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
# CONFIG_9P_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=m
CONFIG_NLS_DEFAULT="cp437"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
CONFIG_NLS_CODEPAGE_852=m
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=m
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=m

#
# Instrumentation Support
#
CONFIG_PROFILING=y
CONFIG_OPROFILE=m
# CONFIG_KPROBES is not set

#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_SCHEDSTATS=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_PREEMPT=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_DEBUG_KOBJECT=y
CONFIG_DEBUG_HIGHMEM=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
CONFIG_PAGE_OWNER=y
CONFIG_DEBUG_FS=y
CONFIG_FRAME_POINTER=y
CONFIG_EARLY_PRINTK=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_STACK_USAGE=y
CONFIG_DEBUG_PAGEALLOC=y
CONFIG_4KSTACKS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_KGDB=y
# CONFIG_KGDB_9600BAUD is not set
# CONFIG_KGDB_19200BAUD is not set
# CONFIG_KGDB_38400BAUD is not set
# CONFIG_KGDB_57600BAUD is not set
CONFIG_KGDB_115200BAUD=y
CONFIG_KGDB_PORT=3f8
CONFIG_KGDB_IRQ=4
# CONFIG_KGDB_MORE is not set
CONFIG_NO_KGDB_CPUS=2
# CONFIG_KGDB_TS is not set
# CONFIG_STACK_OVERFLOW_TEST is not set
# CONFIG_TRAP_BAD_SYSCALL_EXITS is not set
# CONFIG_KGDB_CONSOLE is not set
CONFIG_KGDB_SYSRQ=y

#
# Security options
#
CONFIG_KEYS=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_CAPABILITIES=m
CONFIG_SECURITY_ROOTPLUG=m
CONFIG_SECURITY_SECLVL=m
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_TEST=m

#
# Hardware crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set

#
# Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y

Regards,
Michal Piotrowski
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Michal Piotrowski
2005-10-17 06:50:07 UTC
Permalink
Post by Andrew Morton
Beats me. Please send .config.
Make modules_install works good on 2.6.14-rc4.

***@debian:/usr/src/linux-mm$ bzip2 -cd
/home/michal/moje/pobrane/2.6.14-rc4-mm1.bz2 | patch -p1 --dry-run |
grep serial
[..]
patching file drivers/serial/8250_acpi.c
patching file drivers/serial/8250.c
patching file drivers/serial/8250_pnp.c

I'll try revert it later.

Regards,
Michal Piotrowski
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Russell King
2005-10-17 07:50:14 UTC
Permalink
Post by Andrew Morton
Post by Michal Piotrowski
I have noticed some warnings while "make modules_install"
if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F
System.map 2.6.14-rc4-mm1; fi
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/serial_core.ko
ignored, due to loop
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250_pnp.ko ignored,
due to loop
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250_pci.ko ignored,
due to loop
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250_acpi.ko
ignored, due to loop
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250.ko needs
serial_core.ko which needs 8250.ko again!
WARNING: Module
/lib/modules/2.6.14-rc4-mm1/kernel/drivers/serial/8250.ko ignored, due
to loop
Beats me. Please send .config.
It's good ole kgdb. FWIW, Tom Rini's version which has been posted
several times to lkml doesn't have this issue.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Con Kolivas
2005-10-17 00:50:12 UTC
Permalink
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.
6.14-rc4-mm1/
+mm-implement-swap-prefetching.patch
+mm-implement-swap-prefetching-default-y.patch
+mm-implement-swap-prefetching-tweaks.patch
+mm-implement-swap-prefetching-tweaks-2.patch
Con's swap prefetching code
Thanks.

For users testing this, could you please also try larger values in:
/proc/sys/vm/swap_prefetch
Read the current value (it should be in the range of 1-10) and try a value ten
times larger.

It is currently quite gentle in the amount it prefetches, but the code is now
extremely cautious about when to prefetch and I suspect it can prefetch much
more by default, thus intensifying the effect and benefit.

Cheers,
Con
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Reuben Farrelly
2005-10-17 06:20:05 UTC
Permalink
Hi,
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
- Lots of i2c, PCI and USB updates
- Large input layer update to convert it all to dynamic input_dev allocation
- Significant x86_64 updates
- MD updates
- Lots of core memory management scalability rework
Compiles and runs here, but noting these messages when ethernet link down:

Oct 17 18:49:40 tornado kernel: NEIGH: BUG, double timer add, state is 1
Oct 17 18:51:04 tornado last message repeated 3 times
Oct 17 18:52:05 tornado last message repeated 5 times
Oct 17 18:52:11 tornado last message repeated 2 times

net/core/neighbour.c has this:

static inline void neigh_add_timer(struct neighbour *n, unsigned long when)
{
if (unlikely(mod_timer(&n->timer, when))) {
printk("NEIGH: BUG, double timer add, state is %x\n",
n->nud_state);
}
}


Network guys?

reuben
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Herbert Xu
2005-10-23 07:40:05 UTC
Permalink
Post by Reuben Farrelly
Oct 17 18:49:40 tornado kernel: NEIGH: BUG, double timer add, state is 1
Oct 17 18:51:04 tornado last message repeated 3 times
Oct 17 18:52:05 tornado last message repeated 5 times
Oct 17 18:52:11 tornado last message repeated 2 times
Excellent. Looks like we actually caught something. Pity we don't have
a stack trace which means that there might be more bugs.

Anyway, here are three patches which should fix this. This should go
into 2.6.14.

Arnaldo, you can pull them from

master.kernel.org:/pub/scm/linux/kernel/git/herbert/net-2.6.git

Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <***@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Herbert Xu
2005-10-23 07:40:07 UTC
Permalink
[NEIGH] Fix add_timer race in neigh_add_timer

neigh_add_timer cannot use add_timer unconditionally. The reason is that
by the time it has obtained the write lock someone else (e.g., neigh_update)
could have already added a new timer.

So it should only use mod_timer and deal with its return value accordingly.

This bug would have led to rare neighbour cache entry leaks.

Signed-off-by: Herbert Xu <***@gondor.apana.org.au>
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <***@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Herbert Xu
2005-10-23 07:40:08 UTC
Permalink
[NEIGH] Fix timer leak in neigh_changeaddr

neigh_changeaddr attempts to delete neighbour timers without setting
nud_state. This doesn't work because the timer may have already fired
when we acquire the write lock in neigh_changeaddr. The result is that
the timer may keep firing for quite a while until the entry reaches
NEIGH_FAILED.

It should be setting the nud_state straight away so that if the timer
has already fired it can simply exit once we relinquish the lock.

In fact, this whole function is simply duplicating the logic in
neigh_ifdown which in turn is already doing the right thing when
it comes to deleting timers and setting nud_state.

So all we have to do is take that code out and put it into a common
function and make both neigh_changeaddr and neigh_ifdown call it.

Signed-off-by: Herbert Xu <***@gondor.apana.org.au>
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <***@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Ben Greear
2005-10-23 18:10:13 UTC
Permalink
Post by Herbert Xu
[NEIGH] Fix timer leak in neigh_changeaddr
neigh_changeaddr attempts to delete neighbour timers without setting
nud_state. This doesn't work because the timer may have already fired
when we acquire the write lock in neigh_changeaddr. The result is that
the timer may keep firing for quite a while until the entry reaches
NEIGH_FAILED.
It should be setting the nud_state straight away so that if the timer
has already fired it can simply exit once we relinquish the lock.
In fact, this whole function is simply duplicating the logic in
neigh_ifdown which in turn is already doing the right thing when
it comes to deleting timers and setting nud_state.
So all we have to do is take that code out and put it into a common
function and make both neigh_changeaddr and neigh_ifdown call it.
Thanks for all who reproduced and fixed this...I'm glad to know I wasn't
insane when I first tried to fix it and then couldn't reproduce
the problem anymore! :)

Ben
--
Ben Greear <***@candelatech.com>
Candela Technologies Inc http://www.candelatech.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Herbert Xu
2005-10-23 07:40:08 UTC
Permalink
[NEIGH] Print stack trace in neigh_add_timer

Stack traces are very helpful in determining the exact nature of a bug.
So let's print a stack trace when the timer is added twice.

Signed-off-by: Herbert Xu <***@gondor.apana.org.au>
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <***@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Arnaldo Carvalho de Melo
2005-10-23 16:20:12 UTC
Permalink
Post by Herbert Xu
Post by Reuben Farrelly
Oct 17 18:49:40 tornado kernel: NEIGH: BUG, double timer add, state is 1
Oct 17 18:51:04 tornado last message repeated 3 times
Oct 17 18:52:05 tornado last message repeated 5 times
Oct 17 18:52:11 tornado last message repeated 2 times
Excellent. Looks like we actually caught something. Pity we don't have
a stack trace which means that there might be more bugs.
Anyway, here are three patches which should fix this. This should go
into 2.6.14.
Arnaldo, you can pull them from
master.kernel.org:/pub/scm/linux/kernel/git/herbert/net-2.6.git
Thanks, pulled.

I guess at some point I'll try to make the neighbour code more like the
sock one where we have things like sk_reset_timer and sk_stop_timer for
this purpose.

- Arnaldo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
WU Fengguang
2005-10-17 07:10:10 UTC
Permalink
I come across a compile error:
drivers/video/nvidia/nv_setup.c: In function `NVCommonSetup':
drivers/video/nvidia/nv_setup.c:407: error: parse error before "do"
drivers/video/nvidia/nv_setup.c:407: error: parse error before ')' token

The context lines
in drivers/video/nvidia/nv_setup.c:

if (nvidia_probe_i2c_connector(info, 1, &edidA))
nvidia_probe_of_connector(info, 1, &edidA);

in drivers/video/nvidia/nv_proto.h:

#define nvidia_probe_i2c_connector(p, c, edid) \
do { \
*(edid) = NULL; \
} while(0)

...

#define nvidia_probe_of_connector(p, c, edid) \
do { \
*(edid) = NULL; \
} while(0)


Regards,
Wu Fengguang
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
MAEDA Naoaki
2005-10-17 07:20:08 UTC
Permalink
Hi,

From: Andrew Morton <***@osdl.org>
Subject: 2.6.14-rc4-mm1
Date: Sun, 16 Oct 2005 15:41:08 -0700
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
(snip)

I've seen the following compile error on ia64.

arch/ia64/kernel/acpi-ext.c: In function `acpi_vendor_resource_match':
arch/ia64/kernel/acpi-ext.c:38: error: structure has no member named `id'
make[1]: *** [arch/ia64/kernel/acpi-ext.o] Error 1
make: *** [arch/ia64/kernel] Error 2

Attached patch fix the problem.

Thanks,
MAEDA Naoaki

------
This patch fix the following compile error on ia64.

arch/ia64/kernel/acpi-ext.c: In function `acpi_vendor_resource_match':
arch/ia64/kernel/acpi-ext.c:38: error: structure has no member named `id'

Signed-off-by: MAEDA Naoaki <***@jp.fujitsu.com>

Index: linux-2.6.13/arch/ia64/kernel/acpi-ext.c
===================================================================
--- linux-2.6.13.orig/arch/ia64/kernel/acpi-ext.c
+++ linux-2.6.13/arch/ia64/kernel/acpi-ext.c
@@ -35,7 +35,7 @@ acpi_vendor_resource_match(struct acpi_r
struct acpi_vendor_descriptor *descriptor;
u32 length;

- if (resource->id != ACPI_RSTYPE_VENDOR)
+ if (resource->type != ACPI_RSTYPE_VENDOR)
return AE_OK;

vendor = (struct acpi_resource_vendor *)&resource->data;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Benjamin Herrenschmidt
2005-10-17 07:30:19 UTC
Permalink
Wanna send fix please?
Date: Mon, 17 Oct 2005 15:07:15 +0800
Subject: Re: 2.6.14-rc4-mm1
Does that updated patch fixes it ?

Index: linux-work/drivers/video/Kconfig
===================================================================
--- linux-work.orig/drivers/video/Kconfig 2005-10-13 13:46:13.000000000 +1000
+++ linux-work/drivers/video/Kconfig 2005-10-17 17:20:51.000000000 +1000
@@ -662,7 +662,7 @@

config FB_NVIDIA_I2C
bool "Enable DDC Support"
- depends on FB_NVIDIA && !PPC_OF
+ depends on FB_NVIDIA
help
This enables I2C support for nVidia Chipsets. This is used
only for getting EDID information from the attached display
Index: linux-work/drivers/video/nvidia/nv_of.c
===================================================================
--- linux-work.orig/drivers/video/nvidia/nv_of.c 2005-10-13 13:46:13.000000000 +1000
+++ linux-work/drivers/video/nvidia/nv_of.c 2005-10-17 17:23:15.000000000 +1000
@@ -27,34 +27,60 @@
#include "nv_local.h"
#include "nv_proto.h"

-void nvidia_create_i2c_busses(struct nvidia_par *par) {}
-void nvidia_delete_i2c_busses(struct nvidia_par *par) {}
+#include "../edid.h"

-int nvidia_probe_i2c_connector(struct fb_info *info, int conn, u8 **out_edid)
+int nvidia_probe_of_connector(struct fb_info *info, int conn, u8 **out_edid)
{
struct nvidia_par *par = info->par;
- struct device_node *dp;
+ struct device_node *parent, *dp;
unsigned char *pedid = NULL;
- unsigned char *disptype = NULL;
static char *propnames[] = {
- "DFP,EDID", "LCD,EDID", "EDID", "EDID1", "EDID,B", "EDID,A", NULL };
+ "DFP,EDID", "LCD,EDID", "EDID", "EDID1",
+ "EDID,B", "EDID,A", NULL };
int i;

- dp = pci_device_to_OF_node(par->pci_dev);
- for (; dp != NULL; dp = dp->child) {
- disptype = (unsigned char *)get_property(dp, "display-type", NULL);
- if (disptype == NULL)
- continue;
- if (strncmp(disptype, "LCD", 3) != 0)
- continue;
+ parent = pci_device_to_OF_node(par->pci_dev);
+ if (parent == NULL)
+ return -1;
+ if (par->twoHeads) {
+ char *pname;
+ int len;
+
+ for (dp = NULL;
+ (dp = of_get_next_child(parent, dp)) != NULL;) {
+ pname = (char *)get_property(dp, "name", NULL);
+ if (!pname)
+ continue;
+ len = strlen(pname);
+ if ((pname[len-1] == 'A' && conn == 1) ||
+ (pname[len-1] == 'B' && conn == 2)) {
+ for (i = 0; propnames[i] != NULL; ++i) {
+ pedid = (unsigned char *)
+ get_property(dp, propnames[i],
+ NULL);
+ if (pedid != NULL)
+ break;
+ }
+ of_node_put(dp);
+ break;
+ }
+ }
+ }
+ if (pedid == NULL) {
for (i = 0; propnames[i] != NULL; ++i) {
pedid = (unsigned char *)
- get_property(dp, propnames[i], NULL);
- if (pedid != NULL) {
- *out_edid = pedid;
- return 0;
- }
+ get_property(parent, propnames[i], NULL);
+ if (pedid != NULL)
+ break;
}
}
- return 1;
+ if (pedid) {
+ *out_edid = kmalloc(EDID_LENGTH, GFP_KERNEL);
+ if (*out_edid == NULL)
+ return -1;
+ memcpy(*out_edid, pedid, EDID_LENGTH);
+ printk(KERN_DEBUG "nvidiafb: Found OF EDID for head %d\n", conn);
+ return 0;
+ }
+ return -1;
}
Index: linux-work/drivers/video/nvidia/nv_proto.h
===================================================================
--- linux-work.orig/drivers/video/nvidia/nv_proto.h 2005-10-13 13:46:13.000000000 +1000
+++ linux-work/drivers/video/nvidia/nv_proto.h 2005-10-17 17:22:28.000000000 +1000
@@ -31,7 +31,7 @@
void NVLockUnlock(struct nvidia_par *par, int);

/* in nvidia-i2c.c */
-#if defined(CONFIG_FB_NVIDIA_I2C) || defined (CONFIG_PPC_OF)
+#ifdef CONFIG_FB_NVIDIA_I2C
void nvidia_create_i2c_busses(struct nvidia_par *par);
void nvidia_delete_i2c_busses(struct nvidia_par *par);
int nvidia_probe_i2c_connector(struct fb_info *info, int conn,
@@ -39,10 +39,14 @@
#else
#define nvidia_create_i2c_busses(...)
#define nvidia_delete_i2c_busses(...)
-#define nvidia_probe_i2c_connector(p, c, edid) \
-do { \
- *(edid) = NULL; \
-} while(0)
+#define nvidia_probe_i2c_connector(p, c, edid) (-1)
+#endif
+
+#ifdef CONFIG_FB_OF
+int nvidia_probe_of_connector(struct fb_info *info, int conn,
+ u8 ** out_edid);
+#else
+#define nvidia_probe_of_connector(p, c, edid) (-1)
#endif

/* in nv_accel.c */
Index: linux-work/drivers/video/nvidia/nv_setup.c
===================================================================
--- linux-work.orig/drivers/video/nvidia/nv_setup.c 2005-10-13 13:46:13.000000000 +1000
+++ linux-work/drivers/video/nvidia/nv_setup.c 2005-10-17 17:20:51.000000000 +1000
@@ -190,9 +190,9 @@
present = (NV_RD32(PRAMDAC, 0x0608) & (1 << 28)) ? 1 : 0;

if (present)
- printk("nvidiafb: CRTC%i found\n", output);
+ printk("nvidiafb: CRTC%i analog found\n", output);
else
- printk("nvidiafb: CRTC%i not found\n", output);
+ printk("nvidiafb: CRTC%i analog not found\n", output);

NV_WR32(par->PRAMDAC0, 0x0608, NV_RD32(par->PRAMDAC0, 0x0608) &
0x0000EFFF);
@@ -305,6 +305,9 @@
int FlatPanel = -1; /* really means the CRTC is slaved */
int Television = 0;

+ memset(&monitorA, 0, sizeof(struct fb_monspecs));
+ memset(&monitorB, 0, sizeof(struct fb_monspecs));
+
par->PRAMIN = par->REGS + (0x00710000 / 4);
par->PCRTC0 = par->REGS + (0x00600000 / 4);
par->PRAMDAC0 = par->REGS + (0x00680000 / 4);
@@ -401,7 +404,8 @@
nvidia_create_i2c_busses(par);
if (!par->twoHeads) {
par->CRTCnumber = 0;
- nvidia_probe_i2c_connector(info, 1, &edidA);
+ if (nvidia_probe_i2c_connector(info, 1, &edidA))
+ nvidia_probe_of_connector(info, 1, &edidA);
if (edidA && !fb_parse_edid(edidA, &var)) {
printk("nvidiafb: EDID found from BUS1\n");
monA = &monitorA;
@@ -488,14 +492,16 @@
oldhead = NV_RD32(par->PCRTC0, 0x00000860);
NV_WR32(par->PCRTC0, 0x00000860, oldhead | 0x00000010);

- nvidia_probe_i2c_connector(info, 1, &edidA);
+ if (nvidia_probe_i2c_connector(info, 1, &edidA))
+ nvidia_probe_of_connector(info, 1, &edidA);
if (edidA && !fb_parse_edid(edidA, &var)) {
printk("nvidiafb: EDID found from BUS1\n");
monA = &monitorA;
fb_edid_to_monspecs(edidA, monA);
}

- nvidia_probe_i2c_connector(info, 2, &edidB);
+ if (nvidia_probe_i2c_connector(info, 2, &edidB))
+ nvidia_probe_of_connector(info, 2, &edidB);
if (edidB && !fb_parse_edid(edidB, &var)) {
printk("nvidiafb: EDID found from BUS2\n");
monB = &monitorB;
Index: linux-work/drivers/video/nvidia/nvidia.c
===================================================================
--- linux-work.orig/drivers/video/nvidia/nvidia.c 2005-10-13 13:46:13.000000000 +1000
+++ linux-work/drivers/video/nvidia/nvidia.c 2005-10-17 17:20:51.000000000 +1000
@@ -619,41 +619,85 @@
NVTRACE_LEAVE();
}

+#undef DUMP_REG
+
static void nvidia_write_regs(struct nvidia_par *par)
{
struct _riva_hw_state *state = &par->ModeReg;
int i;

NVTRACE_ENTER();
- NVWriteCrtc(par, 0x11, 0x00);
-
- NVLockUnlock(par, 0);

NVLoadStateExt(par, state);

NVWriteMiscOut(par, state->misc_output);

+ for (i = 1; i < NUM_SEQ_REGS; i++) {
+#ifdef DUMP_REG
+ printk(" SEQ[%02x] = %08x\n", i, state->seq[i]);
+#endif
+ NVWriteSeq(par, i, state->seq[i]);
+ }
+
+ /* Ensure CRTC registers 0-7 are unlocked by clearing bit 7 of CRTC[17] */
+ NVWriteCrtc(par, 0x11, state->crtc[0x11] & ~0x80);
+
for (i = 0; i < NUM_CRT_REGS; i++) {
switch (i) {
case 0x19:
case 0x20 ... 0x40:
break;
default:
+#ifdef DUMP_REG
+ printk("CRTC[%02x] = %08x\n", i, state->crtc[i]);
+#endif
NVWriteCrtc(par, i, state->crtc[i]);
}
}

- for (i = 0; i < NUM_ATC_REGS; i++)
- NVWriteAttr(par, i, state->attr[i]);
-
- for (i = 0; i < NUM_GRC_REGS; i++)
+ for (i = 0; i < NUM_GRC_REGS; i++) {
+#ifdef DUMP_REG
+ printk(" GRA[%02x] = %08x\n", i, state->gra[i]);
+#endif
NVWriteGr(par, i, state->gra[i]);
+ }
+
+ for (i = 0; i < NUM_ATC_REGS; i++) {
+#ifdef DUMP_REG
+ printk("ATTR[%02x] = %08x\n", i, state->attr[i]);
+#endif
+ NVWriteAttr(par, i, state->attr[i]);
+ }

- for (i = 0; i < NUM_SEQ_REGS; i++)
- NVWriteSeq(par, i, state->seq[i]);
NVTRACE_LEAVE();
}

+static void nvidia_vga_protect(struct nvidia_par *par, int on)
+{
+ unsigned char tmp;
+
+ if (on) {
+ /*
+ * Turn off screen and disable sequencer.
+ */
+ tmp = NVReadSeq(par, 0x01);
+
+ NVWriteSeq(par, 0x00, 0x01); /* Synchronous Reset */
+ NVWriteSeq(par, 0x01, tmp | 0x20); /* disable the display */
+ } else {
+ /*
+ * Reenable sequencer, then turn on screen.
+ */
+
+ tmp = NVReadSeq(par, 0x01);
+
+ NVWriteSeq(par, 0x01, tmp & ~0x20); /* reenable display */
+ NVWriteSeq(par, 0x00, 0x03); /* End Reset */
+ }
+}
+
+
+
static int nvidia_calc_regs(struct fb_info *info)
{
struct nvidia_par *par = info->par;
@@ -860,7 +904,7 @@
for (i = 0; i < 0x10; i++)
state->attr[i] = i;
state->attr[0x10] = 0x41;
- state->attr[0x11] = 0x01;
+ state->attr[0x11] = 0xff;
state->attr[0x12] = 0x0f;
state->attr[0x13] = 0x00;
state->attr[0x14] = 0x00;
@@ -983,7 +1027,6 @@

nvidia_init_vga(info);
nvidia_calc_regs(info);
- nvidia_write_regs(par);

NVLockUnlock(par, 0);
if (par->twoHeads) {
@@ -992,7 +1035,22 @@
NVLockUnlock(par, 0);
}

- NVWriteCrtc(par, 0x11, 0x00);
+ nvidia_vga_protect(par, 1);
+
+ nvidia_write_regs(par);
+
+#if defined (__BIG_ENDIAN)
+ /* turn on LFB swapping */
+ {
+ unsigned char tmp;
+
+ VGA_WR08(par->PCIO, 0x3d4, 0x46);
+ tmp = VGA_RD08(par->PCIO, 0x3d5);
+ tmp |= (1 << 7);
+ VGA_WR08(par->PCIO, 0x3d5, tmp);
+ }
+#endif
+
info->fix.line_length = (info->var.xres_virtual *
info->var.bits_per_pixel) >> 3;
if (info->var.accel_flags) {
@@ -1014,7 +1072,7 @@

par->cursor_reset = 1;

- NVWriteCrtc(par, 0x11, 0xff);
+ nvidia_vga_protect(par, 0);

NVTRACE_LEAVE();
return 0;


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
WU Fengguang
2005-10-17 08:20:03 UTC
Permalink
Post by Benjamin Herrenschmidt
Does that updated patch fixes it ?
Lots of rejects, so I manually applied the relevant part in nv_proto.h.
It worked, though there were warnings:

drivers/video/nvidia/nv_setup.c: In function `NVCommonSetup':
drivers/video/nvidia/nv_setup.c:408: warning: statement with no effect
drivers/video/nvidia/nv_setup.c:496: warning: statement with no effect
drivers/video/nvidia/nv_setup.c:504: warning: statement with no effect
Post by Benjamin Herrenschmidt
+#define nvidia_probe_i2c_connector(p, c, edid) (-1)
+#define nvidia_probe_of_connector(p, c, edid) (-1)
Do you mean TRUE/SUCCESS here with (-1)?
Post by Benjamin Herrenschmidt
Index: linux-work/drivers/video/nvidia/nv_proto.h
===================================================================
--- linux-work.orig/drivers/video/nvidia/nv_proto.h 2005-10-13 13:46:13.000000000 +1000
+++ linux-work/drivers/video/nvidia/nv_proto.h 2005-10-17 17:22:28.000000000 +1000
@@ -31,7 +31,7 @@
void NVLockUnlock(struct nvidia_par *par, int);
/* in nvidia-i2c.c */
-#if defined(CONFIG_FB_NVIDIA_I2C) || defined (CONFIG_PPC_OF)
+#ifdef CONFIG_FB_NVIDIA_I2C
void nvidia_create_i2c_busses(struct nvidia_par *par);
void nvidia_delete_i2c_busses(struct nvidia_par *par);
int nvidia_probe_i2c_connector(struct fb_info *info, int conn,
@@ -39,10 +39,14 @@
#else
#define nvidia_create_i2c_busses(...)
#define nvidia_delete_i2c_busses(...)
-#define nvidia_probe_i2c_connector(p, c, edid) \
-do { \
- *(edid) = NULL; \
-} while(0)
+#define nvidia_probe_i2c_connector(p, c, edid) (-1)
+#endif
+
+#ifdef CONFIG_FB_OF
+int nvidia_probe_of_connector(struct fb_info *info, int conn,
+ u8 ** out_edid);
+#else
+#define nvidia_probe_of_connector(p, c, edid) (-1)
#endif
Regards,
Wu Fengguang
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Benjamin Herrenschmidt
2005-10-17 08:20:08 UTC
Permalink
Post by WU Fengguang
Post by Benjamin Herrenschmidt
Does that updated patch fixes it ?
Lots of rejects, so I manually applied the relevant part in nv_proto.h.
drivers/video/nvidia/nv_setup.c:408: warning: statement with no effect
drivers/video/nvidia/nv_setup.c:496: warning: statement with no effect
drivers/video/nvidia/nv_setup.c:504: warning: statement with no effect
Post by Benjamin Herrenschmidt
+#define nvidia_probe_i2c_connector(p, c, edid) (-1)
+#define nvidia_probe_of_connector(p, c, edid) (-1)
Do you mean TRUE/SUCCESS here with (-1)?
Yes

Ben.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Anton Altaparmakov
2005-10-17 10:00:25 UTC
Permalink
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
git-ntfs.patch
This is a request for testers for ntfs. 2.6.14-rc4-mm1 contains a
pretty much complete re-write of file write support so some more testers
than just myself would be good before I submit it for inclusion in
2.6.15...

The rewrite means that the following features are now supported:

Given an existing uncompressed and unencrypted file, you can use:

- write(2) to write to the file, including beyond the end of the
existing file, and the file will be extended appropriately. Both
resident and non-resident files are supported. Support for heavily
fragmented files still has some limitations but you will just get an
EOPNOTSUPP error if you hit one. Everything will still be consistent on
the volume. Sparse files can also be written to and holes will be
filled in appropriately.

- truncate(2) and ftruncate(2) to change the size of the file, inlcuding
using open(2) with O_TRUNC flag. As with write(2) there still are some
limitations for heavily fragmented files, and as above, everything will
still be consistent on the volume if you hit an unsupported case.

What this means is that you can now run your favourite editor on an
existing file, e.g. "vim /ntfs/somefile.txt" works fine and you can save
your changes. Also things like running OpenOffice should work to edit
existing MS Office documents but I haven't tried it yet (it should work
as long as OpenOffice does not need to create temporary files in the
same directory as the document).

Still not supported features are creation/deletion of files/directories
and mmap(2) based writes to sparse regions of files. (The mmap(2)
support has not been modified since the last release, only the file
write(2) support was rewritten.)

If you do try it, please let me know how it worked for you! - Thanks a
lot in advance for testing!

Best regards,

Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Anton Altaparmakov
2005-10-19 11:20:38 UTC
Permalink
Hi,

To all: There is serious data corruption issue with ntfs in
2.6.14-rc4-mm1 (and ntfs 2.1.25 release in general, not just -mm). Fix
is below. Hopefully this is the only bug!
Hi Anton, not too lucky doing modifications with soffice to word documents.
Saving files is ok but when I reopen the files, the format is lost...
I'll try to recover them from Word.exe
I'm afraid I have bad news, I couldn't boot W2K, I got this message
STOP: C0000221 { checksum image test incorrect }
Something weird, I edited txt file A with vim, then I edited Word File
B with soffice, I close it, then I reopened. I lost format so the file
is not legible but I can see paragraphs from file A in file B!!!!!
I am really sorry about this. )-: You should be able to hopefully fix
windows by booting with the installation CD and going into recovery
console and running chkdsk on the partition. You can also try running
ntfsfix from ntfsprogs and then booting into windows. This may be
sufficient to allow it to do a chkdsk on the partition before it
crashes.

I found a bug that caused corruption of the openoffice document as you
described. The fix is below.

diff -urNp /usr/src/ntfs-2.6-devel/fs/ntfs/file.c ntfs26dev/file.c
--- /usr/src/ntfs-2.6-devel/fs/ntfs/file.c 2005-10-11 15:00:00.000000000 +0100
+++ ntfs26dev/file.c 2005-10-19 11:50:54.859558000 +0100
@@ -787,6 +787,7 @@ retry_remap:
vcn_len = rl[1].vcn - vcn;
lcn_block = lcn << (vol->cluster_size_bits -
blocksize_bits);
+ cdelta = 0;
/*
* If the number of remaining clusters in the
* @pages is smaller or equal to the number of

Thank you very much for testing and I am really sorry it caused the
corruption to your partition. In the future I will make sure to say
"Please only test on test partitions."...

Best regards,

Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Damir Perisa
2005-10-17 10:40:11 UTC
Permalink
just found that jsm-tty is still not compiling:

LD drivers/serial/jsm/built-in.o
CC [M] drivers/serial/jsm/jsm_driver.o
CC [M] drivers/serial/jsm/jsm_neo.o
CC [M] drivers/serial/jsm/jsm_tty.o
drivers/serial/jsm/jsm_tty.c: In function 'jsm_input':
drivers/serial/jsm/jsm_tty.c:592: error: 'struct tty_struct' has no member named 'flip'
drivers/serial/jsm/jsm_tty.c:619: error: 'struct tty_struct' has no member named 'flip'
drivers/serial/jsm/jsm_tty.c:620: error: 'struct tty_struct' has no member named 'flip'
drivers/serial/jsm/jsm_tty.c:623: error: 'struct tty_struct' has no member named 'flip'
...

greetings,
Damir
--
Who does not trust enough will not be trusted.
-- Lao Tsu
V. Ananda Krishnan
2005-10-17 15:10:33 UTC
Permalink
Hi,

Please give details of the distro and the compiler version that you
used. Are you building the driver as a module?

Thanks,
V. Ananda Krishnan
Post by Damir Perisa
LD drivers/serial/jsm/built-in.o
CC [M] drivers/serial/jsm/jsm_driver.o
CC [M] drivers/serial/jsm/jsm_neo.o
CC [M] drivers/serial/jsm/jsm_tty.o
drivers/serial/jsm/jsm_tty.c:592: error: 'struct tty_struct' has no member named 'flip'
drivers/serial/jsm/jsm_tty.c:619: error: 'struct tty_struct' has no member named 'flip'
drivers/serial/jsm/jsm_tty.c:620: error: 'struct tty_struct' has no member named 'flip'
drivers/serial/jsm/jsm_tty.c:623: error: 'struct tty_struct' has no member named 'flip'
...
greetings,
Damir
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Damir Perisa
2005-10-17 15:31:02 UTC
Permalink
Le Monday 17 October 2005 16:56, vous avez écrit :
|  Please give details of the distro and the compiler version that you
| used.  Are you building the driver as a module?

i'm package maintainer of kernel26mm in archlinux (i686).
the compiler is gcc 4.0.2 with some bugs fixed it had (from
4.0.3-snapshot).

yes, jsm-tty is built as module, as can be seen from output i posted.
the only difference from 2.6.14-rc4-mm1 and the one i compile is the
applied cleanup patch

2614-rc4-mm-sparse-fixes.patch

that was announced on the mailinglist just after the rc4-mm1 release.

if you need the config, it can be found here:

http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/kernels/kernel26mm/?cvsroot=Extra&only_with_tag=HEAD

i'm willing to apply any patches that would make kernel26mm again compile
all ttys successfully (the last one that did is 2.6.15-rc5-mm1).

thanx + greetings,
Damir
--
I think it's a new feature. Don't tell anyone it was an accident. :-)
-- Larry Wall on s/foo/bar/eieio in
<***@jpl-devvax.JPL.NASA.GOV>
V. Ananda Krishnan
2005-10-18 14:20:05 UTC
Permalink
Hi all,

Can some one send me pointer(s) to the recent API changes in the tty
layer that has gone in to linux-2.6.14.xxx. As Damir pointed out in his
mail yesterday, currently jsm driver is broken in 2.6.14-rc4-mm1
kernel. I am trying to debug the jsm driver at my end. Any help in
this is appreciated.

V. Ananda Krishnan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Greg KH
2005-10-18 20:20:53 UTC
Permalink
Post by V. Ananda Krishnan
Hi all,
Can some one send me pointer(s) to the recent API changes in the tty
layer that has gone in to linux-2.6.14.xxx.
You have access to the patches as well as we do. :)

Anyway, the changes are only in the -mm tree for now, not in the
mainline kernel. Look at the patches there, they should be pretty
obvious.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Alan Cox
2005-10-17 18:10:14 UTC
Permalink
Post by Damir Perisa
LD drivers/serial/jsm/built-in.o
CC [M] drivers/serial/jsm/jsm_driver.o
The authors haven't updated it to the new tty buffering API and its the
one driver which is so complex and so abuses the interface [mostly
because the old API was inadequate for it] that I couldn't see how to
fix it and it needers a fixer with hardware and docs.

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Paul Jackson
2005-10-22 02:10:07 UTC
Permalink
Alan or Andrew,

Would it be appropriate for me to send in a patch that disabled
CONFIG_SERIAL_JSM in *-mm/arch/ppc64/defconfig for the time being?

As Alan has explained, his flip buffer removal killed serial jsm
(it was already in ill health.)

I trip over it when I try to cross compile all the defconfig's.

My inclination is that it better to make an effort to keep *-mm
compiling for all defconfigs.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <***@sgi.com> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Andrew Morton
2005-10-22 06:50:08 UTC
Permalink
Post by Paul Jackson
Alan or Andrew,
Would it be appropriate for me to send in a patch that disabled
CONFIG_SERIAL_JSM in *-mm/arch/ppc64/defconfig for the time being?
If it helps, sure. It looks like those patches will be -mm-only for a
while yet. I haven't actually sat down and worked out how many drivers are
still broken, nor how important they are, but the amount of breakage does
still appear to be considerable.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Alan Cox
2005-10-22 09:30:13 UTC
Permalink
Post by Andrew Morton
If it helps, sure. It looks like those patches will be -mm-only for a
while yet. I haven't actually sat down and worked out how many drivers are
still broken, nor how important they are, but the amount of breakage does
still appear to be considerable.
The only broken driver I am aware of remaining is the jsm driver, and
possibly one or two embedded drivers that the authors simply won't fix
until it goes mainstream.

ISDN was the last big one and I sent fixes for that.

What else is broken ?

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Andrew Morton
2005-10-24 08:00:18 UTC
Permalink
Post by Alan Cox
Post by Andrew Morton
If it helps, sure. It looks like those patches will be -mm-only for a
while yet. I haven't actually sat down and worked out how many drivers are
still broken, nor how important they are, but the amount of breakage does
still appear to be considerable.
The only broken driver I am aware of remaining is the jsm driver, and
possibly one or two embedded drivers that the authors simply won't fix
until it goes mainstream.
ISDN was the last big one and I sent fixes for that.
What else is broken ?
Hard to quantify, really. One would need to iteratively disable config
options to generate a complete list. Perhaps a `make -i' will tell?

drivers/serial/sunsab.c is one.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Brice Goglin
2005-10-17 12:30:24 UTC
Permalink
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
- Lots of i2c, PCI and USB updates
- Large input layer update to convert it all to dynamic input_dev allocation
- Significant x86_64 updates
- MD updates
- Lots of core memory management scalability rework
Hi Andrew,

I got the following oops during the boot on my laptop (Compaq Evo N600c).
.config is attached.

Regards,
Brice


IBM TrackPoint firmware: 0x0b, buttons: 2/3
input: TPPS/2 IBM TrackPoint//class/input_dev as input2
hw_random hardware driver 1.0.0 loaded
NET: Registered protocol family 23
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP(,...)]
c01dda09
PREEMPT
Modules linked in: pcspkr parport_pc parport irtty_sir sir_dev irda
crc_ccitt hw_random uhci_hcd usbcore snd_maestro3 snd_ac97_codec
snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc
snd soundcore yenta_socket rsrc_nonstatic pcmcia_core nls_iso8859_15
nls_cp850 vfat fat nls_base psmouse
CPU: 0
EIP: 0060:[<c01dda09>] Not tainted VLI
EFLAGS: 00010246 (2.6.14-rc4-mm1=LoulousMobile)
EIP is at get_kobj_path_length+0x19/0x30
eax: 00000000 ebx: 00000000 ecx: ffffffff edx: e6efee50
esi: 00000001 edi: 00000000 ebp: e737eec8 esp: e737eebc
ds: 007b es: 007b ss: 0068
Process sed (pid: 3258, threadinfo=e737e000 task=e7970a90)
Stack: e6efe800 00000001 e6de4000 e737eee8 c01dda9a e6efee50 e6de42e4
00000286
e6efe800 00000001 e6de4000 e737ef24 c02a357f e6efee50 800000d0
0000000f
00000002 0000000a 00000000 e6efe800 00000000 000002e5 000002e5
e7e9ce60
Call Trace:
[<c010414b>] show_stack+0xab/0xf0
[<c010433f>] show_registers+0x18f/0x230
[<c0104592>] die+0x102/0x1c0
[<c035f27a>] do_page_fault+0x33a/0x66f
[<c0103dbb>] error_code+0x4f/0x54
[<c01dda9a>] kobject_get_path+0x1a/0x70
[<c02a357f>] input_devices_read+0x53f/0x590
[<c01a2e75>] proc_file_read+0x1b5/0x260
[<c01689f8>] vfs_read+0xa8/0x190
[<c0168dc7>] sys_read+0x47/0x70
[<c0103325>] syscall_call+0x7/0xb
Code: f8 89 ec 5d c3 8d b6 00 00 00 00 8d bc 27 00 00 00 00 55 89 e5 8b
55 08 57 56 be 01 00 00 00 53 31 db 8b 3a b9 ff ff ff ff 89 d8 <f2> ae
f7 d1 49 8b 52 24 8d 74 31 01 85 d2 75 e7 5b 89 f0 5e 5f
<6>input: isa0061/input0//class/input_dev as input3
Andrew Morton
2005-10-17 20:30:22 UTC
Permalink
Post by Brice Goglin
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
- Lots of i2c, PCI and USB updates
- Large input layer update to convert it all to dynamic input_dev allocation
- Significant x86_64 updates
- MD updates
- Lots of core memory management scalability rework
Hi Andrew,
I got the following oops during the boot on my laptop (Compaq Evo N600c).
.config is attached.
Regards,
Brice
IBM TrackPoint firmware: 0x0b, buttons: 2/3
input: TPPS/2 IBM TrackPoint//class/input_dev as input2
hw_random hardware driver 1.0.0 loaded
NET: Registered protocol family 23
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP(,...)]
c01dda09
PREEMPT
Modules linked in: pcspkr parport_pc parport irtty_sir sir_dev irda
crc_ccitt hw_random uhci_hcd usbcore snd_maestro3 snd_ac97_codec
snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc
snd soundcore yenta_socket rsrc_nonstatic pcmcia_core nls_iso8859_15
nls_cp850 vfat fat nls_base psmouse
CPU: 0
EIP: 0060:[<c01dda09>] Not tainted VLI
EFLAGS: 00010246 (2.6.14-rc4-mm1=LoulousMobile)
EIP is at get_kobj_path_length+0x19/0x30
eax: 00000000 ebx: 00000000 ecx: ffffffff edx: e6efee50
esi: 00000001 edi: 00000000 ebp: e737eec8 esp: e737eebc
ds: 007b es: 007b ss: 0068
Process sed (pid: 3258, threadinfo=e737e000 task=e7970a90)
Stack: e6efe800 00000001 e6de4000 e737eee8 c01dda9a e6efee50 e6de42e4
00000286
e6efe800 00000001 e6de4000 e737ef24 c02a357f e6efee50 800000d0
0000000f
00000002 0000000a 00000000 e6efe800 00000000 000002e5 000002e5
e7e9ce60
[<c010414b>] show_stack+0xab/0xf0
[<c010433f>] show_registers+0x18f/0x230
[<c0104592>] die+0x102/0x1c0
[<c035f27a>] do_page_fault+0x33a/0x66f
[<c0103dbb>] error_code+0x4f/0x54
[<c01dda9a>] kobject_get_path+0x1a/0x70
[<c02a357f>] input_devices_read+0x53f/0x590
[<c01a2e75>] proc_file_read+0x1b5/0x260
[<c01689f8>] vfs_read+0xa8/0x190
[<c0168dc7>] sys_read+0x47/0x70
[<c0103325>] syscall_call+0x7/0xb
Code: f8 89 ec 5d c3 8d b6 00 00 00 00 8d bc 27 00 00 00 00 55 89 e5 8b
55 08 57 56 be 01 00 00 00 53 31 db 8b 3a b9 ff ff ff ff 89 d8 <f2> ae
f7 d1 49 8b 52 24 8d 74 31 01 85 d2 75 e7 5b 89 f0 5e 5f
<6>input: isa0061/input0//class/input_dev as input3
Something went wrong under input_devices_read(). Probably culprits cc'ed.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Vojtech Pavlik
2005-10-17 21:30:16 UTC
Permalink
Post by Andrew Morton
Post by Brice Goglin
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
- Lots of i2c, PCI and USB updates
- Large input layer update to convert it all to dynamic input_dev allocation
- Significant x86_64 updates
- MD updates
- Lots of core memory management scalability rework
Hi Andrew,
I got the following oops during the boot on my laptop (Compaq Evo N600c).
.config is attached.
Regards,
Brice
Where did get support for IBM TrackPoints into that kernel? It's
certainly not in 2.6.14, and it's not in the -mm patch either ...

That's likely the cause here, since the TP patch probably relies on
non-dynamic allocation semantics.
Post by Andrew Morton
Post by Brice Goglin
IBM TrackPoint firmware: 0x0b, buttons: 2/3
input: TPPS/2 IBM TrackPoint//class/input_dev as input2
hw_random hardware driver 1.0.0 loaded
NET: Registered protocol family 23
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP(,...)]
c01dda09
PREEMPT
Modules linked in: pcspkr parport_pc parport irtty_sir sir_dev irda
crc_ccitt hw_random uhci_hcd usbcore snd_maestro3 snd_ac97_codec
snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc
snd soundcore yenta_socket rsrc_nonstatic pcmcia_core nls_iso8859_15
nls_cp850 vfat fat nls_base psmouse
CPU: 0
EIP: 0060:[<c01dda09>] Not tainted VLI
EFLAGS: 00010246 (2.6.14-rc4-mm1=LoulousMobile)
EIP is at get_kobj_path_length+0x19/0x30
eax: 00000000 ebx: 00000000 ecx: ffffffff edx: e6efee50
esi: 00000001 edi: 00000000 ebp: e737eec8 esp: e737eebc
ds: 007b es: 007b ss: 0068
Process sed (pid: 3258, threadinfo=e737e000 task=e7970a90)
Stack: e6efe800 00000001 e6de4000 e737eee8 c01dda9a e6efee50 e6de42e4
00000286
e6efe800 00000001 e6de4000 e737ef24 c02a357f e6efee50 800000d0
0000000f
00000002 0000000a 00000000 e6efe800 00000000 000002e5 000002e5
e7e9ce60
[<c010414b>] show_stack+0xab/0xf0
[<c010433f>] show_registers+0x18f/0x230
[<c0104592>] die+0x102/0x1c0
[<c035f27a>] do_page_fault+0x33a/0x66f
[<c0103dbb>] error_code+0x4f/0x54
[<c01dda9a>] kobject_get_path+0x1a/0x70
[<c02a357f>] input_devices_read+0x53f/0x590
[<c01a2e75>] proc_file_read+0x1b5/0x260
[<c01689f8>] vfs_read+0xa8/0x190
[<c0168dc7>] sys_read+0x47/0x70
[<c0103325>] syscall_call+0x7/0xb
Code: f8 89 ec 5d c3 8d b6 00 00 00 00 8d bc 27 00 00 00 00 55 89 e5 8b
55 08 57 56 be 01 00 00 00 53 31 db 8b 3a b9 ff ff ff ff 89 d8 <f2> ae
f7 d1 49 8b 52 24 8d 74 31 01 85 d2 75 e7 5b 89 f0 5e 5f
<6>input: isa0061/input0//class/input_dev as input3
Something went wrong under input_devices_read(). Probably culprits cc'ed.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Greg KH
2005-10-17 21:50:16 UTC
Permalink
Post by Vojtech Pavlik
Post by Brice Goglin
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
- Lots of i2c, PCI and USB updates
- Large input layer update to convert it all to dynamic input_dev allocation
- Significant x86_64 updates
- MD updates
- Lots of core memory management scalability rework
Hi Andrew,
I got the following oops during the boot on my laptop (Compaq Evo N600c).
.config is attached.
Regards,
Brice
Where did get support for IBM TrackPoints into that kernel? It's
certainly not in 2.6.14, and it's not in the -mm patch either ...
Yes it is. We merged it at the beginning of 2.6.14.. ;)
Post by Vojtech Pavlik
That's likely the cause here, since the TP patch probably relies on
non-dynamic allocation semantics.
It was converted but I am aftraid when Greg created sub-class devices
something broke a bit. Do you see the ugly names input core prints?
The "//" stuff you mean? Did I do that?

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Dmitry Torokhov
2005-10-17 22:00:21 UTC
Permalink
Post by Greg KH
Post by Vojtech Pavlik
Post by Brice Goglin
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
- Lots of i2c, PCI and USB updates
- Large input layer update to convert it all to dynamic input_dev allocation
- Significant x86_64 updates
- MD updates
- Lots of core memory management scalability rework
Hi Andrew,
I got the following oops during the boot on my laptop (Compaq Evo N600c).
.config is attached.
Regards,
Brice
Where did get support for IBM TrackPoints into that kernel? It's
certainly not in 2.6.14, and it's not in the -mm patch either ...
Yes it is. We merged it at the beginning of 2.6.14.. ;)
Post by Vojtech Pavlik
That's likely the cause here, since the TP patch probably relies on
non-dynamic allocation semantics.
It was converted but I am aftraid when Greg created sub-class devices
something broke a bit. Do you see the ugly names input core prints?
The "//" stuff you mean? Did I do that?
Not directly. I was trying to make names look "nice" but when you
moved stuff around they stopped being nice ;) Although that name in
front of double "/" - it should not be there... it was supposed to be
"%s as %s/%s", somehow I screwed that up.

Hopefully I'll have some time tonight to investigate further.

--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Greg KH
2005-10-18 06:50:06 UTC
Permalink
Post by Dmitry Torokhov
Post by Greg KH
Post by Vojtech Pavlik
Post by Brice Goglin
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
- Lots of i2c, PCI and USB updates
- Large input layer update to convert it all to dynamic input_dev allocation
- Significant x86_64 updates
- MD updates
- Lots of core memory management scalability rework
Hi Andrew,
I got the following oops during the boot on my laptop (Compaq Evo N600c).
.config is attached.
Regards,
Brice
Where did get support for IBM TrackPoints into that kernel? It's
certainly not in 2.6.14, and it's not in the -mm patch either ...
Yes it is. We merged it at the beginning of 2.6.14.. ;)
Post by Vojtech Pavlik
That's likely the cause here, since the TP patch probably relies on
non-dynamic allocation semantics.
It was converted but I am aftraid when Greg created sub-class devices
something broke a bit. Do you see the ugly names input core prints?
The "//" stuff you mean? Did I do that?
Not directly. I was trying to make names look "nice" but when you
moved stuff around they stopped being nice ;) Although that name in
front of double "/" - it should not be there... it was supposed to be
"%s as %s/%s", somehow I screwed that up.
Hopefully I'll have some time tonight to investigate further.
A simple:
cat /sys/class/input/input1/event1/name
causes this to happen too.

That's my fault, I'll work on fixing that.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Dmitry Torokhov
2005-10-17 21:50:19 UTC
Permalink
Post by Vojtech Pavlik
Post by Brice Goglin
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
- Lots of i2c, PCI and USB updates
- Large input layer update to convert it all to dynamic input_dev allocation
- Significant x86_64 updates
- MD updates
- Lots of core memory management scalability rework
Hi Andrew,
I got the following oops during the boot on my laptop (Compaq Evo N600c).
.config is attached.
Regards,
Brice
Where did get support for IBM TrackPoints into that kernel? It's
certainly not in 2.6.14, and it's not in the -mm patch either ...
Yes it is. We merged it at the beginning of 2.6.14.. ;)
Post by Vojtech Pavlik
That's likely the cause here, since the TP patch probably relies on
non-dynamic allocation semantics.
It was converted but I am aftraid when Greg created sub-class devices
something broke a bit. Do you see the ugly names input core prints?

--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Vojtech Pavlik
2005-10-18 06:50:08 UTC
Permalink
Post by Vojtech Pavlik
Post by Brice Goglin
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
- Lots of i2c, PCI and USB updates
- Large input layer update to convert it all to dynamic input_dev allocation
- Significant x86_64 updates
- MD updates
- Lots of core memory management scalability rework
Hi Andrew,
I got the following oops during the boot on my laptop (Compaq Evo N600c).
.config is attached.
Regards,
Brice
Where did get support for IBM TrackPoints into that kernel? It's
certainly not in 2.6.14, and it's not in the -mm patch either ...
Yes it is. We merged it at the beginning of 2.6.14.. ;)
Ahh, sorry. I've seen it cause trouble so many times before I forgot we
actually did merge it.
Post by Vojtech Pavlik
That's likely the cause here, since the TP patch probably relies on
non-dynamic allocation semantics.
It was converted but I am aftraid when Greg created sub-class devices
something broke a bit. Do you see the ugly names input core prints?
--
Dmitry
--
Vojtech Pavlik
SuSE Labs, SuSE CR
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Dmitry Torokhov
2005-10-18 06:50:09 UTC
Permalink
Post by Vojtech Pavlik
Post by Vojtech Pavlik
Post by Brice Goglin
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
- Lots of i2c, PCI and USB updates
- Large input layer update to convert it all to dynamic input_dev allocation
- Significant x86_64 updates
- MD updates
- Lots of core memory management scalability rework
Hi Andrew,
I got the following oops during the boot on my laptop (Compaq Evo N600c).
.config is attached.
Regards,
Brice
Where did get support for IBM TrackPoints into that kernel? It's
certainly not in 2.6.14, and it's not in the -mm patch either ...
Yes it is. We merged it at the beginning of 2.6.14.. ;)
Ahh, sorry. I've seen it cause trouble so many times before I forgot we
actually did merge it.
Really? It seems to be working perfectly on my laptop...
--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Greg KH
2005-10-18 07:10:10 UTC
Permalink
Post by Andrew Morton
Post by Brice Goglin
Modules linked in: pcspkr parport_pc parport irtty_sir sir_dev irda
crc_ccitt hw_random uhci_hcd usbcore snd_maestro3 snd_ac97_codec
snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc
snd soundcore yenta_socket rsrc_nonstatic pcmcia_core nls_iso8859_15
nls_cp850 vfat fat nls_base psmouse
CPU: 0
EIP: 0060:[<c01dda09>] Not tainted VLI
EFLAGS: 00010246 (2.6.14-rc4-mm1=LoulousMobile)
EIP is at get_kobj_path_length+0x19/0x30
eax: 00000000 ebx: 00000000 ecx: ffffffff edx: e6efee50
esi: 00000001 edi: 00000000 ebp: e737eec8 esp: e737eebc
ds: 007b es: 007b ss: 0068
Process sed (pid: 3258, threadinfo=e737e000 task=e7970a90)
Stack: e6efe800 00000001 e6de4000 e737eee8 c01dda9a e6efee50 e6de42e4
00000286
e6efe800 00000001 e6de4000 e737ef24 c02a357f e6efee50 800000d0
0000000f
00000002 0000000a 00000000 e6efe800 00000000 000002e5 000002e5
e7e9ce60
[<c010414b>] show_stack+0xab/0xf0
[<c010433f>] show_registers+0x18f/0x230
[<c0104592>] die+0x102/0x1c0
[<c035f27a>] do_page_fault+0x33a/0x66f
[<c0103dbb>] error_code+0x4f/0x54
[<c01dda9a>] kobject_get_path+0x1a/0x70
[<c02a357f>] input_devices_read+0x53f/0x590
[<c01a2e75>] proc_file_read+0x1b5/0x260
[<c01689f8>] vfs_read+0xa8/0x190
[<c0168dc7>] sys_read+0x47/0x70
[<c0103325>] syscall_call+0x7/0xb
Code: f8 89 ec 5d c3 8d b6 00 00 00 00 8d bc 27 00 00 00 00 55 89 e5 8b
55 08 57 56 be 01 00 00 00 53 31 db 8b 3a b9 ff ff ff ff 89 d8 <f2> ae
f7 d1 49 8b 52 24 8d 74 31 01 85 d2 75 e7 5b 89 f0 5e 5f
<6>input: isa0061/input0//class/input_dev as input3
Something went wrong under input_devices_read(). Probably culprits cc'ed.
I know this patch doesn't have the proc path, but it does fix an easy
oops that I can generate from sysfs input devices. Can you try it out
to see if it fixes your issue too?

thanks,

greg k-h

---
drivers/input/input.c | 19 ++++++++++++-------
1 file changed, 12 insertions(+), 7 deletions(-)

--- gregkh-2.6.orig/drivers/input/input.c
+++ gregkh-2.6/drivers/input/input.c
@@ -522,17 +522,22 @@ static ssize_t input_dev_show_##name(str
up(&input_dev->sem); \
\
return retval; \
-}
+} \
+static CLASS_DEVICE_ATTR(name, S_IRUGO, input_dev_show_##name, NULL);

INPUT_DEV_STRING_ATTR_SHOW(name);
INPUT_DEV_STRING_ATTR_SHOW(phys);
INPUT_DEV_STRING_ATTR_SHOW(uniq);

-static struct class_device_attribute input_dev_attrs[] = {
- __ATTR(name, S_IRUGO, input_dev_show_name, NULL),
- __ATTR(phys, S_IRUGO, input_dev_show_phys, NULL),
- __ATTR(uniq, S_IRUGO, input_dev_show_uniq, NULL),
- __ATTR_NULL
+static struct attribute *input_dev_attrs[] = {
+ &class_device_attr_name.attr,
+ &class_device_attr_phys.attr,
+ &class_device_attr_uniq.attr,
+ NULL
+};
+
+static struct attribute_group input_dev_group = {
+ .attrs = input_dev_attrs,
};

#define INPUT_DEV_ID_ATTR(name) \
@@ -694,7 +699,6 @@ struct class input_class = {
.name = "input",
.release = input_dev_release,
.hotplug = input_dev_hotplug,
- .class_dev_attrs = input_dev_attrs,
};

struct input_dev *input_allocate_device(void)
@@ -732,6 +736,7 @@ static void input_register_classdevice(s
kfree(path);

class_device_add(&dev->cdev);
+ sysfs_create_group(&dev->cdev.kobj, &input_dev_group);
sysfs_create_group(&dev->cdev.kobj, &input_dev_id_attr_group);
sysfs_create_group(&dev->cdev.kobj, &input_dev_caps_attr_group);
}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Greg KH
2005-10-18 07:20:12 UTC
Permalink
Post by Greg KH
Post by Andrew Morton
Post by Brice Goglin
Modules linked in: pcspkr parport_pc parport irtty_sir sir_dev irda
crc_ccitt hw_random uhci_hcd usbcore snd_maestro3 snd_ac97_codec
snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc
snd soundcore yenta_socket rsrc_nonstatic pcmcia_core nls_iso8859_15
nls_cp850 vfat fat nls_base psmouse
CPU: 0
EIP: 0060:[<c01dda09>] Not tainted VLI
EFLAGS: 00010246 (2.6.14-rc4-mm1=LoulousMobile)
EIP is at get_kobj_path_length+0x19/0x30
eax: 00000000 ebx: 00000000 ecx: ffffffff edx: e6efee50
esi: 00000001 edi: 00000000 ebp: e737eec8 esp: e737eebc
ds: 007b es: 007b ss: 0068
Process sed (pid: 3258, threadinfo=e737e000 task=e7970a90)
Stack: e6efe800 00000001 e6de4000 e737eee8 c01dda9a e6efee50 e6de42e4
00000286
e6efe800 00000001 e6de4000 e737ef24 c02a357f e6efee50 800000d0
0000000f
00000002 0000000a 00000000 e6efe800 00000000 000002e5 000002e5
e7e9ce60
[<c010414b>] show_stack+0xab/0xf0
[<c010433f>] show_registers+0x18f/0x230
[<c0104592>] die+0x102/0x1c0
[<c035f27a>] do_page_fault+0x33a/0x66f
[<c0103dbb>] error_code+0x4f/0x54
[<c01dda9a>] kobject_get_path+0x1a/0x70
[<c02a357f>] input_devices_read+0x53f/0x590
[<c01a2e75>] proc_file_read+0x1b5/0x260
[<c01689f8>] vfs_read+0xa8/0x190
[<c0168dc7>] sys_read+0x47/0x70
[<c0103325>] syscall_call+0x7/0xb
Code: f8 89 ec 5d c3 8d b6 00 00 00 00 8d bc 27 00 00 00 00 55 89 e5 8b
55 08 57 56 be 01 00 00 00 53 31 db 8b 3a b9 ff ff ff ff 89 d8 <f2> ae
f7 d1 49 8b 52 24 8d 74 31 01 85 d2 75 e7 5b 89 f0 5e 5f
<6>input: isa0061/input0//class/input_dev as input3
Something went wrong under input_devices_read(). Probably culprits cc'ed.
I know this patch doesn't have the proc path, but it does fix an easy
oops that I can generate from sysfs input devices. Can you try it out
to see if it fixes your issue too?
I am confused - the only thing changed is the way you create attributes,
not the way data is accessed. What is the difference and why does it fix
the OOPS?
Because before my patch, any class_device created for the input class,
had the name, phys, and uniq attributes created for them, including the
"simple" class device structures event0, event1, and so on. The kobject
being passed back to those callback functions was not of the same type
of object as input0, input1 and so on. So bad things happened.

I just moved the attribute group out of the class, and created it when
the proper input device was registered. Hm, forgot to uncreate the
group too, I'll go do that now...

Hope this helps,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Dmitry Torokhov
2005-10-18 07:30:21 UTC
Permalink
Post by Greg KH
Because before my patch, any class_device created for the input class,
had the name, phys, and uniq attributes created for them, including the
"simple" class device structures event0, event1, and so on. The kobject
being passed back to those callback functions was not of the same type
of object as input0, input1 and so on. So bad things happened.
Oh, I see. That's what you get for mixing devices of different classes
into one class ;)
--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Greg KH
2005-10-18 07:50:13 UTC
Permalink
Post by Dmitry Torokhov
Post by Greg KH
Because before my patch, any class_device created for the input class,
had the name, phys, and uniq attributes created for them, including the
"simple" class device structures event0, event1, and so on. The kobject
being passed back to those callback functions was not of the same type
of object as input0, input1 and so on. So bad things happened.
Oh, I see. That's what you get for mixing devices of different classes
into one class ;)
I agree, it's tough, nasty, and full of horrible issues like this. I
got away with much the same mess with the USB core code where we mix
devices of different types on the same bus, but I wouldn't recommend
ever doing that again.

So, when we move everything over to being only devices, I'll try to make
problems like this impossible to occur, as it's a pain...

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Dmitry Torokhov
2005-10-18 07:20:13 UTC
Permalink
Post by Greg KH
Post by Andrew Morton
Post by Brice Goglin
Modules linked in: pcspkr parport_pc parport irtty_sir sir_dev irda
crc_ccitt hw_random uhci_hcd usbcore snd_maestro3 snd_ac97_codec
snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc
snd soundcore yenta_socket rsrc_nonstatic pcmcia_core nls_iso8859_15
nls_cp850 vfat fat nls_base psmouse
CPU: 0
EIP: 0060:[<c01dda09>] Not tainted VLI
EFLAGS: 00010246 (2.6.14-rc4-mm1=LoulousMobile)
EIP is at get_kobj_path_length+0x19/0x30
eax: 00000000 ebx: 00000000 ecx: ffffffff edx: e6efee50
esi: 00000001 edi: 00000000 ebp: e737eec8 esp: e737eebc
ds: 007b es: 007b ss: 0068
Process sed (pid: 3258, threadinfo=e737e000 task=e7970a90)
Stack: e6efe800 00000001 e6de4000 e737eee8 c01dda9a e6efee50 e6de42e4
00000286
e6efe800 00000001 e6de4000 e737ef24 c02a357f e6efee50 800000d0
0000000f
00000002 0000000a 00000000 e6efe800 00000000 000002e5 000002e5
e7e9ce60
[<c010414b>] show_stack+0xab/0xf0
[<c010433f>] show_registers+0x18f/0x230
[<c0104592>] die+0x102/0x1c0
[<c035f27a>] do_page_fault+0x33a/0x66f
[<c0103dbb>] error_code+0x4f/0x54
[<c01dda9a>] kobject_get_path+0x1a/0x70
[<c02a357f>] input_devices_read+0x53f/0x590
[<c01a2e75>] proc_file_read+0x1b5/0x260
[<c01689f8>] vfs_read+0xa8/0x190
[<c0168dc7>] sys_read+0x47/0x70
[<c0103325>] syscall_call+0x7/0xb
Code: f8 89 ec 5d c3 8d b6 00 00 00 00 8d bc 27 00 00 00 00 55 89 e5 8b
55 08 57 56 be 01 00 00 00 53 31 db 8b 3a b9 ff ff ff ff 89 d8 <f2> ae
f7 d1 49 8b 52 24 8d 74 31 01 85 d2 75 e7 5b 89 f0 5e 5f
<6>input: isa0061/input0//class/input_dev as input3
Something went wrong under input_devices_read(). Probably culprits cc'ed.
I know this patch doesn't have the proc path, but it does fix an easy
oops that I can generate from sysfs input devices. Can you try it out
to see if it fixes your issue too?
I am confused - the only thing changed is the way you create attributes,
not the way data is accessed. What is the difference and why does it fix
the OOPS?

Thanks!
--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Brice Goglin
2005-10-18 07:40:03 UTC
Permalink
Post by Greg KH
I know this patch doesn't have the proc path, but it does fix an easy
oops that I can generate from sysfs input devices. Can you try it out
to see if it fixes your issue too?
thanks,
greg k-h
No sorry, it doesn't fix my oops.

By the way, your patch didn't apply to my rc4-mm1 tree.
The one I had to apply is attached.

I might add some debugging code into my tree to help debugging.
But, you'll have to tell what code and where :)

Brice
Greg KH
2005-10-18 07:50:09 UTC
Permalink
Post by Brice Goglin
Post by Greg KH
I know this patch doesn't have the proc path, but it does fix an easy
oops that I can generate from sysfs input devices. Can you try it out
to see if it fixes your issue too?
thanks,
greg k-h
No sorry, it doesn't fix my oops.
By the way, your patch didn't apply to my rc4-mm1 tree.
The one I had to apply is attached.
I might add some debugging code into my tree to help debugging.
But, you'll have to tell what code and where :)
If you disable CONFIG_PNP, does the oops go away?

Also, does this oops keep you from booting? If not, can you see what
the output of 'cat /proc/bus/input/devices' produces (it should show
what device is dying on us.)

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Brice Goglin
2005-10-18 08:30:13 UTC
Permalink
Post by Greg KH
If you disable CONFIG_PNP, does the oops go away?
Also, does this oops keep you from booting? If not, can you see what
the output of 'cat /proc/bus/input/devices' produces (it should show
what device is dying on us.)
Yes disabling CONFIG_PNP makes it disappear.

Here comes /proc/bus/input/devices from 2.6.14-rc4:

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
H: Handlers=kbd event0
B: EV=120013
B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0011 Vendor=0002 Product=0007 Version=0000
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio4/input0
H: Handlers=mouse0 event1
B: EV=b
B: KEY=6420 0 70000 0 0 0 0 0 0 0 0
B: ABS=11000003

I: Bus=0011 Vendor=0002 Product=000a Version=0000
N: Name="TPPS/2 IBM TrackPoint"
P: Phys=synaptics-pt/serio0/input0
H: Handlers=mouse1 event2
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
H: Handlers=kbd event3
B: EV=40001
B: SND=6

Without CONFIG_PNP, the last one disappears.

In rc4-mm1, the last one is a little bit different
(Name and Phys fields):

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="isa0061/input0"
P: Phys=
S: Sysfs=/class/input_dev/input3
H: Handlers=kbd event3
B: EV=40001
B: SND=6

Brice
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Greg KH
2005-10-19 03:50:10 UTC
Permalink
Post by Brice Goglin
Post by Greg KH
If you disable CONFIG_PNP, does the oops go away?
Also, does this oops keep you from booting? If not, can you see what
the output of 'cat /proc/bus/input/devices' produces (it should show
what device is dying on us.)
Yes disabling CONFIG_PNP makes it disappear.
Odd. Dmitry, any ideas?

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Dmitry Torokhov
2005-10-19 04:00:15 UTC
Permalink
Post by Greg KH
Post by Brice Goglin
Post by Greg KH
If you disable CONFIG_PNP, does the oops go away?
Also, does this oops keep you from booting? If not, can you see what
the output of 'cat /proc/bus/input/devices' produces (it should show
what device is dying on us.)
Yes disabling CONFIG_PNP makes it disappear.
Odd. Dmitry, any ideas?
Not yet, except that PC speaker is one of input devices that does not have
a parent struct device...
--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Greg KH
2005-10-17 20:50:24 UTC
Permalink
Post by Brice Goglin
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
- Lots of i2c, PCI and USB updates
- Large input layer update to convert it all to dynamic input_dev allocation
- Significant x86_64 updates
- MD updates
- Lots of core memory management scalability rework
Hi Andrew,
I got the following oops during the boot on my laptop (Compaq Evo N600c).
.config is attached.
Regards,
Brice
IBM TrackPoint firmware: 0x0b, buttons: 2/3
input: TPPS/2 IBM TrackPoint//class/input_dev as input2
hw_random hardware driver 1.0.0 loaded
NET: Registered protocol family 23
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP(,...)]
Odd, what userspace program is wanting to see the proc input stuff?

What distro and version of it are you running?

And did this oops happen after init started, or before?

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Brice Goglin
2005-10-17 22:10:11 UTC
Permalink
Post by Greg KH
Odd, what userspace program is wanting to see the proc input stuff?
What distro and version of it are you running?
And did this oops happen after init started, or before?
My distro is a Debian testing/sid.
hotplug is 0.0.20040329-25
udev is 0.70-2

This occurs after init started.

From what I see, it's during hotplug, when it scans isapnp devices.
hotplug finds PNP0800 in /sys/bus/pnp/devices/00:07/id and then
loads pcspkr. The oops occurs during "modprobe -s -q -q pcspkr"
in the isapnp.rc script.
This script is attached in case there's something specific in Debian.

I don't see how I could investigate further.
Let me know if you have any idea to debug the modprobe.

Regards,
Brice
Helge Hafting
2005-10-17 21:10:21 UTC
Permalink
This one gets me a penguin on the framebuffer, and then dies
with no further textual output.
numlock leds were working, and I could reboot with sysrq.

Single opteron, Matrox G550 AGP framebuffer. There is also
a pci radeon in the machine, but no driver for it as X has
to do int10 initialization first.

Helge Hafting

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Andrew Morton
2005-10-17 21:20:10 UTC
Permalink
Post by Helge Hafting
This one gets me a penguin on the framebuffer, and then dies
with no further textual output.
numlock leds were working, and I could reboot with sysrq.
Can we get anything useful out of sysrq-p and sysrq-t?

Also, adding initcall_debug to the boot command line might help.
Post by Helge Hafting
Single opteron, Matrox G550 AGP framebuffer. There is also
a pci radeon in the machine, but no driver for it as X has
to do int10 initialization first.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Helge Hafting
2005-10-17 21:30:19 UTC
Permalink
Post by Andrew Morton
Post by Helge Hafting
This one gets me a penguin on the framebuffer, and then dies
with no further textual output.
numlock leds were working, and I could reboot with sysrq.
Can we get anything useful out of sysrq-p and sysrq-t?
Nothing displayed - the penguin just sits there.
Seems he's not hung, merely waiting for something, even
ctrl+alt+del does a reboot.
Post by Andrew Morton
Also, adding initcall_debug to the boot command line might help.
Didn't seem to help. I get some text _before_ the penguin
appears, thre last I was able to read before the blackout
and the penguin was something about USB storage.

I had both vgacon and fbcon compiled in. I am retrying with
vgacon only, no framebuffer support, to see if it is a framebuffer
or fbcon problem. This setup worked with 2.6.14-rc3 though.

Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Helge Hafting
2005-10-17 22:00:19 UTC
Permalink
Post by Andrew Morton
Post by Helge Hafting
This one gets me a penguin on the framebuffer, and then dies
with no further textual output.
numlock leds were working, and I could reboot with sysrq.
Can we get anything useful out of sysrq-p and sysrq-t?
Also, adding initcall_debug to the boot command line might help.
Tried again without the framebuffer. Still hanging, but more info:

Last messages before getting stuck:
md autorun DONE
kjournald starting
Ext3-fs mounted fs w. ordered data mode
VFS mounted root (ext3) read-only
freeing unused kernel memory 216k freed.
warning-unable to open an initial console
kernel panic-not syncing:No init found. Try passing init= option to kernel


Somewhat silly. There certainly was a console (vgacon) or I wouldn't
be able to read the messages. And if it mounted root, then there certainly
was an init to run also.


SYSRQ P (Omitting lots of time-consuming hex numbers, please tell
if those are really needed.)
sysrq: show regs
cpu 0
Pid:1, comm: swapper not tainted 2.6.14-rc4-mm1 #17
RIP {__delay+4}
(Omitted register dump)
Call trace:
panic+315
vgacon_cursor+0
init+543
child_rip+8
init+0
child_rip+0

SYSRQ T gave me several pages, with no scrollback. Several kernel
threads and their stack dumps. Simplified:
kedac R running task
md2 S
md3 S
md0 S
kjournald S

I can provide the full 80x50 page, but I have to write it down by hand
so only if someone actually think it will be useful.

That EDAC thing was new in rc4-mm1, compared to rc3. I am testing
another rc4-mm1 kernel without it. (menuconfig adviced me to say Y
to the new EDAC thing, so I did that initially.)

Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Andrew Morton
2005-10-18 00:50:06 UTC
Permalink
Post by Helge Hafting
Post by Andrew Morton
Post by Helge Hafting
This one gets me a penguin on the framebuffer, and then dies
with no further textual output.
numlock leds were working, and I could reboot with sysrq.
Can we get anything useful out of sysrq-p and sysrq-t?
Also, adding initcall_debug to the boot command line might help.
md autorun DONE
kjournald starting
Ext3-fs mounted fs w. ordered data mode
VFS mounted root (ext3) read-only
freeing unused kernel memory 216k freed.
warning-unable to open an initial console
kernel panic-not syncing:No init found. Try passing init= option to kernel
Somewhat silly. There certainly was a console (vgacon) or I wouldn't
be able to read the messages. And if it mounted root, then there certainly
was an init to run also.
Can you send the .config please?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Michael Neuffer
2005-10-18 14:30:10 UTC
Permalink
Post by Andrew Morton
Post by Helge Hafting
Post by Andrew Morton
Post by Helge Hafting
This one gets me a penguin on the framebuffer, and then dies
with no further textual output.
numlock leds were working, and I could reboot with sysrq.
Can we get anything useful out of sysrq-p and sysrq-t?
Also, adding initcall_debug to the boot command line might help.
md autorun DONE
kjournald starting
Ext3-fs mounted fs w. ordered data mode
VFS mounted root (ext3) read-only
freeing unused kernel memory 216k freed.
warning-unable to open an initial console
kernel panic-not syncing:No init found. Try passing init= option to kernel
Somewhat silly. There certainly was a console (vgacon) or I wouldn't
be able to read the messages. And if it mounted root, then there certainly
was an init to run also.
Can you send the .config please?
I see the same effect, with the only difference
that I don't get the kernel panic line.
For me it gets stuck after the "warning-unable to open an initial console"

I'll send you the .config in a seperate mail.

Cheers
Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Helge Hafting
2005-10-17 22:30:16 UTC
Permalink
Testing without EDAC didn't help either.

Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Olaf Hering
2005-10-18 07:50:06 UTC
Permalink
Do not enable this per default during make oldconfig.
'default $foo' should not be abused like that.

Signed-off-by: Olaf Hering <***@suse.de>

Index: linux-2.6.14-rc4-mm1/kernel/Kconfig.preempt
===================================================================
--- linux-2.6.14-rc4-mm1.orig/kernel/Kconfig.preempt 2005-10-11 01:19:19.000000000 +0000
+++ linux-2.6.14-rc4-mm1/kernel/Kconfig.preempt 2005-10-18 07:41:40.702542966 +0000
@@ -55,7 +55,6 @@
config PREEMPT_BKL
bool "Preempt The Big Kernel Lock"
depends on SMP || PREEMPT
- default y
help
This option reduces the latency of the kernel by making the
big kernel lock preemptible.
--
short story of a lazy sysadmin:
alias appserv=wotan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Arjan van de Ven
2005-10-18 08:00:16 UTC
Permalink
Post by Olaf Hering
Do not enable this per default during make oldconfig.
'default $foo' should not be abused like that.
afaik that was done to increase testing.
This thing shouldn't be a config option at all in a final release imo;
the config option as I understand it is there to be able to disable it
during the testing phase in -mm to help diagnose otherwise unexplained
issues.

Maybe by now it's time to remove the config option..


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Olaf Hering
2005-10-18 08:50:14 UTC
Permalink
Post by Arjan van de Ven
Post by Olaf Hering
Do not enable this per default during make oldconfig.
'default $foo' should not be abused like that.
afaik that was done to increase testing.
This thing shouldn't be a config option at all in a final release imo;
the config option as I understand it is there to be able to disable it
during the testing phase in -mm to help diagnose otherwise unexplained
issues.
CONFIG_PREEMPT_BKL is already in Linus tree.
Its disabled in our configs.
--
short story of a lazy sysadmin:
alias appserv=wotan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Arjan van de Ven
2005-10-18 09:00:18 UTC
Permalink
Post by Olaf Hering
Post by Arjan van de Ven
Post by Olaf Hering
Do not enable this per default during make oldconfig.
'default $foo' should not be abused like that.
afaik that was done to increase testing.
This thing shouldn't be a config option at all in a final release imo;
the config option as I understand it is there to be able to disable it
during the testing phase in -mm to help diagnose otherwise unexplained
issues.
CONFIG_PREEMPT_BKL is already in Linus tree.
hmm maybe time to remove it; by now it ought to be mature enough
Post by Olaf Hering
Its disabled in our configs.
any particular reason for that? Eg are there any known or suspected
issues with this?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Olaf Hering
2005-10-18 11:20:11 UTC
Permalink
Post by Arjan van de Ven
Post by Olaf Hering
Its disabled in our configs.
any particular reason for that? Eg are there any known or suspected
issues with this?
I have no idea. Maybe it was the general 'preempt isnt right' move.
--
short story of a lazy sysadmin:
alias appserv=wotan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Ingo Molnar
2005-10-18 12:00:21 UTC
Permalink
Post by Olaf Hering
Post by Arjan van de Ven
Post by Olaf Hering
Its disabled in our configs.
any particular reason for that? Eg are there any known or suspected
issues with this?
I have no idea. Maybe it was the general 'preempt isnt right' move.
that's not a reason to apply your patch that default-disables the
feature on the upstream kernel. Distributors can pick whichever flavor
they want. E.g. Fedora rawhide has PREEMPT_BKL enabled.

i'm fine with removing the .config option for 2.6.15.

Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Alexandre Buisse
2005-10-19 15:10:09 UTC
Permalink
Post by Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
- Lots of i2c, PCI and USB updates
- Large input layer update to convert it all to dynamic input_dev allocation
- Significant x86_64 updates
- MD updates
- Lots of core memory management scalability rework
Hi Andrew,

I've been having problems with ipw2200 oopsing at modprobe since
2.6.14-rc2-mm1 (sorry for not reporting before). I use the ipw2200
included in the kernel.

.config is attached.

Regards,
Alexandre

[ 96.855956] ieee80211_crypt: registered algorithm 'NULL'
[ 96.866572] ieee80211: 802.11 data/management/control stack, git-1.1.5
[ 96.866689] ieee80211: Copyright (C) 2004-2005 Intel Corporation
<***@linux.intel.com>
[ 96.885063] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
1.0.0
[ 96.885182] ipw2200: Copyright(c) 2003-2004 Intel Corporation
[ 96.885697] ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKC] -> GSI
11 (level, low) -> IRQ 11
[ 96.885796] ipw2200: Detected Intel PRO/Wireless 2200BG Network
Connection
[ 97.932261] eth1 (WE) : Driver using old /proc/net/wireless support,
please fix driver !
[ 97.978805] eth1 (WE) : Driver using old /proc/net/wireless support,
please fix driver !
[ 98.324671] divide error: 0000 [#1]
[ 98.324675] PREEMPT
[ 98.324677] last sysfs file:
/devices/pci0000:00/0000:00:1e.0/0000:02:02.0/rf_kill
[ 98.324680] Modules linked in: ipw2200 ieee80211 ieee80211_crypt ac
thermal battery acpi_cpufreq processor radeon snd_intel8x0
snd_ac97_codec snd_ac97_bus
[ 98.324690] CPU: 0
[ 98.324691] EIP: 0060:[<e0d605c0>] Not tainted VLI
[ 98.324693] EFLAGS: 00010093 (2.6.14-rc4-mm1-ubik)
[ 98.324703] EIP is at ieee80211_wx_get_scan+0x740/0x970 [ieee80211]
[ 98.324706] eax: fffad1c8 ebx: 00000000 ecx: 00052e38 edx: ffffffff
[ 98.324710] esi: 00000000 edi: fffad1c8 ebp: d9b9fe74 esp: d9b9fc88
[ 98.324712] ds: 007b es: 007b ss: 0068
[ 98.324715] Process iwlist (pid: 6872, threadinfo=d9b9e000 task=d8242530)
[ 98.324717] Stack: d9b9fe51 00000013 e0d61d13 00000036 e0d61d0f
d7dd0079 d8a10524 d7e16054
[ 98.324724] 6c000000 00000008 d9b9fe54 d7e16098 d7e17000
00000286 d7dd0000 00000000
[ 98.324731] 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000
[ 98.324736] Call Trace:
[ 98.324738] [<c01037ef>] show_stack+0x7f/0xa0
[ 98.324745] [<c0103996>] show_registers+0x166/0x1e0
[ 98.324749] [<c0103bb2>] die+0x102/0x1b0
[ 98.324753] [<c04e73b9>] do_trap+0x89/0xd0
[ 98.324759] [<c0103d18>] do_divide_error+0xb8/0xd0
[ 98.324763] [<c010348f>] error_code+0x4f/0x54
[ 98.324766] [<e0e8952c>] ipw_wx_get_scan+0x2c/0x30 [ipw2200]
[ 98.324778] [<c044a54f>] wireless_process_ioctl+0x59f/0x7c0
[ 98.324784] [<c043e9d2>] dev_ioctl+0x112/0x320
[ 98.324788] [<c0432cf0>] sock_ioctl+0xc0/0x230
[ 98.324794] [<c0179a01>] do_ioctl+0x91/0xb0
[ 98.324799] [<c0179bc2>] vfs_ioctl+0x62/0x1e0
[ 98.324803] [<c0179d81>] sys_ioctl+0x41/0x70
[ 98.324807] [<c0103265>] syscall_call+0x7/0xb
[ 98.324810] Code: 04 b6 8d 04 80 8d 3c 85 00 00 00 00 0f be 42 5c 89
da c1 e2 04 29 da 29 c1 89 c8 c1 e0 05 29 c8 8d 04 42 0f af c8 29 cf 89
f8 99 <f7> fe 3c 64 89 c1 0f 86 ca 01 00 00 c6 45 94 64 e9 76 fe ff ff
[ 98.324839] <6>note: iwlist[6872] exited with preempt_count 1
Jiri Slaby
2005-10-19 16:00:31 UTC
Permalink
Post by Alexandre Buisse
I've been having problems with ipw2200 oopsing at modprobe since
2.6.14-rc2-mm1 (sorry for not reporting before). I use the ipw2200
2.6.14-rc2 is OK (or what was the last OK)? There are no significant
changes in rc2-mm1.
Post by Alexandre Buisse
included in the kernel.
.config is attached.
Regards,
Alexandre
[ 96.855956] ieee80211_crypt: registered algorithm 'NULL'
[ 96.866572] ieee80211: 802.11 data/management/control stack, git-1.1.5
[ 96.866689] ieee80211: Copyright (C) 2004-2005 Intel Corporation
[ 96.885063] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
1.0.0
[ 96.885182] ipw2200: Copyright(c) 2003-2004 Intel Corporation
[ 96.885697] ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKC] -> GSI
11 (level, low) -> IRQ 11
[ 96.885796] ipw2200: Detected Intel PRO/Wireless 2200BG Network
Connection
[ 97.932261] eth1 (WE) : Driver using old /proc/net/wireless support,
please fix driver !
[ 97.978805] eth1 (WE) : Driver using old /proc/net/wireless support,
please fix driver !
[ 98.324671] divide error: 0000 [#1]
[ 98.324675] PREEMPT
/devices/pci0000:00/0000:00:1e.0/0000:02:02.0/rf_kill
[ 98.324680] Modules linked in: ipw2200 ieee80211 ieee80211_crypt ac
thermal battery acpi_cpufreq processor radeon snd_intel8x0
snd_ac97_codec snd_ac97_bus
[ 98.324690] CPU: 0
[ 98.324691] EIP: 0060:[<e0d605c0>] Not tainted VLI
[ 98.324693] EFLAGS: 00010093 (2.6.14-rc4-mm1-ubik)
[ 98.324703] EIP is at ieee80211_wx_get_scan+0x740/0x970 [ieee80211]
[ 98.324706] eax: fffad1c8 ebx: 00000000 ecx: 00052e38 edx: ffffffff
[ 98.324710] esi: 00000000 edi: fffad1c8 ebp: d9b9fe74 esp: d9b9fc88
[ 98.324712] ds: 007b es: 007b ss: 0068
[ 98.324715] Process iwlist (pid: 6872, threadinfo=d9b9e000 task=d8242530)
...oopsing at modprobe since... are you sure? This seems like an iwlist.

thanks for more info,
--
Jiri Slaby www.fi.muni.cz/~xslaby
~\-/~ ***@gmail.com ~\-/~
B67499670407CE62ACC8 22A032CC55C339D47A7E

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Alexandre Buisse
2005-10-19 16:10:14 UTC
Permalink
Post by Jiri Slaby
Post by Alexandre Buisse
I've been having problems with ipw2200 oopsing at modprobe since
2.6.14-rc2-mm1 (sorry for not reporting before). I use the ipw2200
2.6.14-rc2 is OK (or what was the last OK)? There are no significant
changes in rc2-mm1.
I use only -mm, and skipped 2.6.13-mm3. 2.6.14-rc1-mm1 had some other
oops and I didn't even try ipw2200. So last OK was 2.6.13-mm2 (which
I'm still using now)
Post by Jiri Slaby
...oopsing at modprobe since... are you sure? This seems like an iwlist.
I meant that it oopsed just after I modprobed it. But as it makes a
iwlist just after having been loaded, I guess it is actually in an iwlist.

Regards,
Alexandre
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Jiri Slaby
2005-10-19 19:00:10 UTC
Permalink
Post by Alexandre Buisse
I've been having problems with ipw2200 oopsing at modprobe since
2.6.14-rc2-mm1 (sorry for not reporting before). I use the ipw2200
included in the kernel.
Can you apply this and tell me what are the numbers?

--- d/net/ieee80211/ieee80211_wx.c 2005-10-19 20:40:52.000000000 +0200
+++ d/net/ieee80211/ieee80211_wx.c.new 2005-10-19 20:44:00.000000000 +0200
@@ -152,6 +152,8 @@
iwe.u.qual.level = 0;
} else {
iwe.u.qual.level = network->stats.rssi;
+ printk(KERN_ERR "---THIS: %d, %d\n", ieee->perfect_rssi,
+ ieee->worst_rssi);
iwe.u.qual.qual =
(100 *
(ieee->perfect_rssi - ieee->worst_rssi) *
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Alexandre Buisse
2005-10-20 17:50:14 UTC
Permalink
Post by Jiri Slaby
Post by Alexandre Buisse
I've been having problems with ipw2200 oopsing at modprobe since
2.6.14-rc2-mm1 (sorry for not reporting before). I use the ipw2200
included in the kernel.
Can you apply this and tell me what are the numbers?
Hi,

I tested with -rc4 and the problem did not appear.
As for your patch, it just says ---THIS: 0,0 before oopsing.

Hope it helps.

Regards,
Alexandre
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Jiri Slaby
2005-10-20 21:10:10 UTC
Permalink
Post by Alexandre Buisse
Post by Jiri Slaby
Post by Alexandre Buisse
I've been having problems with ipw2200 oopsing at modprobe since
2.6.14-rc2-mm1 (sorry for not reporting before). I use the ipw2200
included in the kernel.
Can you apply this and tell me what are the numbers?
Hi,
I tested with -rc4 and the problem did not appear.
As for your patch, it just says ---THIS: 0,0 before oopsing.
Hope it helps.
Yes, it really does.

The problem is in git-netdev-all.patch. Somebody rewrote the function:

diff --git a/net/ieee80211/ieee80211_wx.c b/net/ieee80211/ieee80211_wx.c
--- a/net/ieee80211/ieee80211_wx.c
+++ b/net/ieee80211/ieee80211_wx.c
@@ -1,6 +1,6 @@
/******************************************************************************

- Copyright(c) 2004 Intel Corporation. All rights reserved.
+ Copyright(c) 2004-2005 Intel Corporation. All rights reserved.

Portions of this file are based on the WEP enablement code provided by the
Host AP project hostap-drivers v0.1.3
@@ -32,6 +32,7 @@

#include <linux/kmod.h>
#include <linux/module.h>
+#include <linux/jiffies.h>

#include <net/ieee80211.h>
#include <linux/wireless.h>
@@ -140,18 +141,38 @@ static inline char *ipw2100_translate_sc
start = iwe_stream_add_point(start, stop, &iwe, custom);

/* Add quality statistics */
- /* TODO: Fix these values... */
iwe.cmd = IWEVQUAL;
- iwe.u.qual.qual = network->stats.signal;
- iwe.u.qual.level = network->stats.rssi;
- iwe.u.qual.noise = network->stats.noise;
- iwe.u.qual.updated = network->stats.mask & IEEE80211_STATMASK_WEMASK;
- if (!(network->stats.mask & IEEE80211_STATMASK_RSSI))
- iwe.u.qual.updated |= IW_QUAL_LEVEL_INVALID;
- if (!(network->stats.mask & IEEE80211_STATMASK_NOISE))
+ iwe.u.qual.updated = IW_QUAL_QUAL_UPDATED | IW_QUAL_LEVEL_UPDATED |
+ IW_QUAL_NOISE_UPDATED;
+
+ if (!(network->stats.mask & IEEE80211_STATMASK_RSSI)) {
+ iwe.u.qual.updated |= IW_QUAL_QUAL_INVALID |
+ IW_QUAL_LEVEL_INVALID;
+ iwe.u.qual.qual = 0;
+ iwe.u.qual.level = 0;
+ } else {
+ iwe.u.qual.level = network->stats.rssi;
+ iwe.u.qual.qual =
+ (100 *
+ (ieee->perfect_rssi - ieee->worst_rssi) *
+ (ieee->perfect_rssi - ieee->worst_rssi) -
+ (ieee->perfect_rssi - network->stats.rssi) *
+ (15 * (ieee->perfect_rssi - ieee->worst_rssi) +
+ 62 * (ieee->perfect_rssi - network->stats.rssi))) /
+ ((ieee->perfect_rssi - ieee->worst_rssi) *
+ (ieee->perfect_rssi - ieee->worst_rssi));
But here is a problem ieee->perfect_rssi and ieee->worst_rssi is 0 and 0, as
you mentioned -- division by zero...

It seems, that it is pulled from your tree, Jeff. Any ideas?

thanks,
--
Jiri Slaby www.fi.muni.cz/~xslaby
~\-/~ ***@gmail.com ~\-/~
B67499670407CE62ACC8 22A032CC55C339D47A7E
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Mark Lord
2005-10-20 21:30:13 UTC
Permalink
There are much newer versions of the ipw2200 driver and related ieee80211
stuff available now -- including a 1.07 driver release just this week.

I wonder how long it will be until the 2.6 kernel catches up ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Jiri Slaby
2005-10-20 23:10:10 UTC
Permalink
Post by Jiri Slaby
Post by Alexandre Buisse
Post by Jiri Slaby
Post by Alexandre Buisse
I've been having problems with ipw2200 oopsing at modprobe since
2.6.14-rc2-mm1 (sorry for not reporting before). I use the ipw2200
included in the kernel.
Can you apply this and tell me what are the numbers?
Hi,
I tested with -rc4 and the problem did not appear.
As for your patch, it just says ---THIS: 0,0 before oopsing.
Hope it helps.
Yes, it really does.
diff --git a/net/ieee80211/ieee80211_wx.c b/net/ieee80211/ieee80211_wx.c
--- a/net/ieee80211/ieee80211_wx.c
+++ b/net/ieee80211/ieee80211_wx.c
@@ -1,6 +1,6 @@
/******************************************************************************
- Copyright(c) 2004 Intel Corporation. All rights reserved.
+ Copyright(c) 2004-2005 Intel Corporation. All rights reserved.
Portions of this file are based on the WEP enablement code provided by the
Host AP project hostap-drivers v0.1.3
@@ -32,6 +32,7 @@
#include <linux/kmod.h>
#include <linux/module.h>
+#include <linux/jiffies.h>
#include <net/ieee80211.h>
#include <linux/wireless.h>
@@ -140,18 +141,38 @@ static inline char *ipw2100_translate_sc
start = iwe_stream_add_point(start, stop, &iwe, custom);
/* Add quality statistics */
- /* TODO: Fix these values... */
iwe.cmd = IWEVQUAL;
- iwe.u.qual.qual = network->stats.signal;
- iwe.u.qual.level = network->stats.rssi;
- iwe.u.qual.noise = network->stats.noise;
- iwe.u.qual.updated = network->stats.mask & IEEE80211_STATMASK_WEMASK;
- if (!(network->stats.mask & IEEE80211_STATMASK_RSSI))
- iwe.u.qual.updated |= IW_QUAL_LEVEL_INVALID;
- if (!(network->stats.mask & IEEE80211_STATMASK_NOISE))
+ iwe.u.qual.updated = IW_QUAL_QUAL_UPDATED | IW_QUAL_LEVEL_UPDATED |
+ IW_QUAL_NOISE_UPDATED;
+
+ if (!(network->stats.mask & IEEE80211_STATMASK_RSSI)) {
+ iwe.u.qual.updated |= IW_QUAL_QUAL_INVALID |
+ IW_QUAL_LEVEL_INVALID;
+ iwe.u.qual.qual = 0;
+ iwe.u.qual.level = 0;
+ } else {
+ iwe.u.qual.level = network->stats.rssi;
+ iwe.u.qual.qual =
+ (100 *
+ (ieee->perfect_rssi - ieee->worst_rssi) *
+ (ieee->perfect_rssi - ieee->worst_rssi) -
+ (ieee->perfect_rssi - network->stats.rssi) *
+ (15 * (ieee->perfect_rssi - ieee->worst_rssi) +
+ 62 * (ieee->perfect_rssi - network->stats.rssi))) /
+ ((ieee->perfect_rssi - ieee->worst_rssi) *
+ (ieee->perfect_rssi - ieee->worst_rssi));
But here is a problem ieee->perfect_rssi and ieee->worst_rssi is 0 and 0, as
you mentioned -- division by zero...
It seems, that it is pulled from your tree, Jeff. Any ideas?
Yup. There is a BIG problem between ipw and 80211. 80211 is a new code and ipw
is an old one. We don't set perfect_rssi and worst_rssi in ipw and 80211 wait
some other values than 0!

What was the problem to not to add a new version of ipw into kernel?

And what about this fix (at least for the time, until ipw will be updated)?

diff --git a/net/ieee80211/ieee80211_wx.c b/net/ieee80211/ieee80211_wx.c
--- a/net/ieee80211/ieee80211_wx.c
+++ b/net/ieee80211/ieee80211_wx.c
@@ -152,15 +152,20 @@ static inline char *ipw2100_translate_sc
iwe.u.qual.level = 0;
} else {
iwe.u.qual.level = network->stats.rssi;
- iwe.u.qual.qual =
- (100 *
- (ieee->perfect_rssi - ieee->worst_rssi) *
- (ieee->perfect_rssi - ieee->worst_rssi) -
- (ieee->perfect_rssi - network->stats.rssi) *
- (15 * (ieee->perfect_rssi - ieee->worst_rssi) +
- 62 * (ieee->perfect_rssi - network->stats.rssi))) /
- ((ieee->perfect_rssi - ieee->worst_rssi) *
- (ieee->perfect_rssi - ieee->worst_rssi));
+ if (ieee->perfect_rssi)
+ iwe.u.qual.qual = (100 *
+ (ieee->perfect_rssi - ieee->worst_rssi) *
+ (ieee->perfect_rssi - ieee->worst_rssi) -
+ (ieee->perfect_rssi - network->stats.rssi) *
+ (
+ 15 * (ieee->perfect_rssi - ieee->worst_rssi) +
+ 62 * (ieee->perfect_rssi - network->stats.rssi)
+ )) /
+ ((ieee->perfect_rssi - ieee->worst_rssi) *
+ (ieee->perfect_rssi - ieee->worst_rssi));
+ else
+ iwe.u.qual.qual = network->stats.signal;
+
if (iwe.u.qual.qual > 100)
iwe.u.qual.qual = 100;
else if (iwe.u.qual.qual < 1)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Jeff Garzik
2005-10-20 23:50:05 UTC
Permalink
Post by Jiri Slaby
But here is a problem ieee->perfect_rssi and ieee->worst_rssi is 0 and 0, as
you mentioned -- division by zero...
It seems, that it is pulled from your tree, Jeff. Any ideas?
thanks,
When it was pulled? Here is the latest patch touching the code in
question...

Author: Jiri Benc <***@suse.cz>
Date: Mon Oct 10 19:16:53 2005 +0200

[PATCH] ieee80211: division by zero fix

This fixes division by zero bug in ieee80211_wx_get_scan().

Signed-off-by: Jiri Benc <***@suse.cz>
Signed-off-by: Jeff Garzik <***@pobox.com>


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Andrew Morton
2005-10-20 23:50:06 UTC
Permalink
Post by Jeff Garzik
Post by Jiri Slaby
But here is a problem ieee->perfect_rssi and ieee->worst_rssi is 0 and 0, as
you mentioned -- division by zero...
It seems, that it is pulled from your tree, Jeff. Any ideas?
thanks,
When it was pulled?
See the first line of the patch, ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/broken-out/git-netdev-all.patch

it is:

GIT 43e63da3a056da127f2e58b6ce312974b7205ad6 master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git#ALL


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Jeff Garzik
2005-10-21 00:30:13 UTC
Permalink
Post by Andrew Morton
Post by Jeff Garzik
Post by Jiri Slaby
But here is a problem ieee->perfect_rssi and ieee->worst_rssi is 0 and 0, as
you mentioned -- division by zero...
It seems, that it is pulled from your tree, Jeff. Any ideas?
thanks,
When it was pulled?
See the first line of the patch, ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/broken-out/git-netdev-all.patch
GIT 43e63da3a056da127f2e58b6ce312974b7205ad6 master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git#ALL
ah ok. I think Jiri's patch is the fix, then.

Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Continue reading on narkive:
Loading...