2.6.14-rc5-mm1
Subsystems (9)
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/
- At great personal cost I managed to coax most of the USB devel tree into compiling and booting. We're hoping that the changes in here will improve USB-related power management (suspend and resume). Please cc [email protected] on any bug reports (or use bugzilla).
- Added git-blktrace.patch to the -mm lineup: Jens's block-layer tracing
infrastructure. It appears to be undocumented...
- Added git-block.patch to the -mm lineup: Jens's block tree (drivers/block/*.c, basically).
- Added git-mips.patch to the -mm lineup: Ralf's MIPS development tree.
- Lots more core MM changes from Hugh: mainly to address page_table_lock SMP scalability issuse. All this code is in place now (I think), so performance testing time is here.
- Demand-paging for hugetlb pages. Needs very careful testing.
- Added Thomas's ktimer patch.
- A number of tty drivers still won't compile.
Changes since 2.6.14-rc4-mm1:
linus.patch
git-acpi.patch
git-agpgart.patch
git-blktrace.patch
git-block.patch
git-cifs.patch
git-cpufreq.patch
git-drm.patch
git-ia64.patch
git-audit.patch
git-jfs.patch
git-libata-all.patch
git-mips.patch
git-mtd.patch
git-netdev-all.patch
git-nfs.patch
git-ntfs.patch
git-ocfs2.patch
git-scsi-misc.patch
git-sas.patch
git-cryptodev.patch
Subsystem trees
-list-add-missing-rcu_dereference-on-first-element.patch -ip6_tables-build-fix.patch
-svgatextmode-fix.patch -fix-vpx3220-offset-issue-in-secam.patch -fix-black-white-only-svideo-input-in-vpx3220.patch -revert-orinoco-information-leakage-due-to-incorrect-padding.patch -better-fixup-for-the-orinoco-driver.patch -libata-build-fix.patch
-e1000_intr-build-fix.patch -git-netedv-all-s2io-build-fix.patch -git-netdev-all-e1000-fix.patch -guarantee-dma-area-for-alloc_bootmem_low.patch -mm-hugetlb-truncation-fixes.patch -switch-sibyte-profiling-driver-to-compat_ioctl.patch -switch-sibyte-profiling-driver-to-compat_ioctl-fix.patch -fix-exit_itimers-vs-posix_timer_event-ab-ba-deadlock.patch -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 -au1100fb-use-preprocessor-instruction-for-error.patch -cpufreq-kmalloc-memset-kzalloc-conversion.patch -hwmon-kmalloc-memset-kzalloc-conversion.patch -i2c-kmalloc-memset-kzalloc-conversion.patch -kfree-cleanup-documentation.patch
Merged
+alpha-atomic-dependency-fix.patch
Alpha build fix
+git-acpi-build-fix-3.patch
Fix git-acpi.patch
+agp-performance-fixes.patch +agp-updates-owner-field-of-struct-pci_driver.patch
AGP things
+nm256-reset-workaround-for-latitude-csx.patch
Sound driver fix
+gregkh-driver-class-device.h-documentation.patch +gregkh-driver-input-register-class_device-sooner.patch +gregkh-driver-input-input_dev_class-export.patch +gregkh-driver-input-class_device-move.patch +gregkh-driver-input_oops_fix.patch +gregkh-driver-input-remove-input_class.patch +gregkh-driver-input-rename-input_dev_class.patch +gregkh-driver-input_backward_compatible_symlink.patch +gregkh-driver-input-remove-custom-hotplug.patch +gregkh-driver-drivers-base-fix-sparse-warnings.patch +gregkh-driver-driver-core-big-kfree-null-check-cleanup-documentation.patch
Driver tree updates
+gregkh-i2c-i2c-owner-field-01-struct-pci-driver.patch +gregkh-i2c-i2c-owner-field-02-struct-device-driver.patch +gregkh-i2c-i2c-owner-field-03-i2c-keywest.patch +gregkh-i2c-i2c-owner-field-04-i2c-core.patch +gregkh-i2c-i2c-owner-field-05-i2c-isa.patch +gregkh-i2c-hwmon-smsc47b397-new-id.patch +gregkh-i2c-hwmon-missing-driver-class.patch +gregkh-i2c-i2c-x1205.patch +gregkh-i2c-kzalloc-01-i2c-ixp.patch +gregkh-i2c-kzalloc-02-hwmon.patch +gregkh-i2c-kzalloc-03-i2c-other.patch +gregkh-i2c-kzalloc-04-drop-useless-casts.patch +gregkh-i2c-kzalloc-05-i2c-amd756-s4882.patch +gregkh-i2c-kzalloc-06-i2c-documentation-update.patch
I2C tree updates
+input-evdev-allow-querying-ev_sw-from-compat_ioctl.patch +input-add-logitech-mx3100-to-logips2ppc.patch
Input tree updates
+git-netdev-all-ieee80211_tx-fix.patch +git-netdev-all-ieee80211_get_payload-warning-fix.patch +git-netdev-all-b44-build-fix.patch
Fixes for git-netdev-all.patch
+ntfs-printk-warning-fixes.patch
Warning fixes
+serial-remove-unneeded-code-from-serial_corec.patch
Serial driver cleanup
+gregkh-pci-shpc-01-shpc-use-pci-core.patch +gregkh-pci-shpc-02-remove-redundant-res-display.patch +gregkh-pci-shpc-03-reduce-acpi-dependence.patch +gregkh-pci-shpc-04-probe-bail-early.patch +gregkh-pci-shpc-05-dont-save-pci-configs.patch +gregkh-pci-shpc-06-remove-redundant-data-structures.patch +gregkh-pci-shpc-07--misc-cleanup.patch +gregkh-pci-shpc-08-reduce-dbg-verbosity.patch +gregkh-pci-shpc-09-remove-sysfs-files-on-unload.patch +gregkh-pci-pci-fix-edac-drivers-for-radisys-82600-borkage.patch +gregkh-pci-pci-fixup-pci-driver-shutdown.patch +gregkh-pci-pci-convert-megaraid-to-use-pci_driver-shutdown-method.patch +gregkh-pci-acpiphp-allocate-resources-for-adapters-with-bridges.patch
PCI tree updates
+scsi-remove-dead-code-from-src.patch +scsi_error-thread-exits-in-task_interruptible-state.patch +scsi-disk-report-size-without-overflow.patch
scsi fixes
+gregkh-usb-usb-pm-01.patch
+gregkh-usb-usb-pm-02.patch
+gregkh-usb-usb-pm-03.patch
+gregkh-usb-usb-pm-04.patch
+gregkh-usb-usb-pm-05.patch
+gregkh-usb-usb-pm-06.patch
+gregkh-usb-usb-pm-07.patch
+gregkh-usb-usb-pm-08.patch
+gregkh-usb-usb-pm-10.patch
+gregkh-usb-usb-pm-11.patch
+gregkh-usb-usb-pm-12.patch
+gregkh-usb-usb-pm-13.patch +gregkh-usb-usb-rename-hcd-hub_suspend-to-hcd-bus_suspend.patch +gregkh-usb-uhci-improve-handling-of-iso-tds.patch +gregkh-usb-usb-storage-another-unusual_devs-entry.patch +gregkh-usb-usb-buffer-overflow-patch-for-yealink-driver.patch +gregkh-usb-usb-doc-fix-kernel-doc-warning.patch +gregkh-usb-omap_udc-dma-off-by-one-fix.patch +gregkh-usb-fix-hcd-state-assignments-in-uhci-hcd.patch +gregkh-usb-add-usb-transceiver-set_suspend-method.patch +gregkh-usb-usb-s3c2410-ohci-add-driver-owner-field.patch +gregkh-usb-usb-gadget-drivers-add-.owner-initialisation.patch +gregkh-usb-usb-add-owner-initialisation-to-host-drivers.patch +gregkh-usb-missing-transfer_flags-setting-in-usbtest.patch +gregkh-usb-usb-remove-devio-global.patch +gregkh-usb-usb-notify-devices-and-busses.patch +gregkh-usb-usb-use-notifier-devio.patch +gregkh-usb-usb-use-notifier-inode.patch +gregkh-usb-usb-use-notifier-usbmon.patch +gregkh-usb-usb-patch-for-usbdevfs_ioctl-from-32-bit-programs.patch +gregkh-usb-usb-remove-bluetty.patch +gregkh-usb-usb-serial-driver-cleanup-01.patch +gregkh-usb-usb-serial-driver-cleanup-02.patch +gregkh-usb-usb-serial-driver-cleanup-03.patch +gregkh-usb-usb-serial-driver-cleanup-04.patch +gregkh-usb-usb-serial-driver-cleanup-05.patch
USB tree updates (gregkh-usb-usb-pm-09.patch breaks one of my machines)
+gregkh-usb-usb-rename-hcd-hub_suspend-to-hcd-bus_suspend-fix.patch +gregkh-usb-usb-rename-hcd-hub_suspend-to-hcd-bus_suspend-config_pm-fix.patch +gregkh-usb-usb-serial-driver-cleanup-01-fixes.patch +gregkh-usb-usb-serial-driver-cleanup-04-fixes.patch +gregkh-usb-usb-serial-driver-cleanup-04-keyspan-fixes.patch +gregkh-usb-usb-patch-for-usbdevfs_ioctl-from-32-bit-programs-fix.patch +gregkh-usb-usb-pm-04-fix.patch
+gregkh-usb-usb-pm-03-fix.patch
+export-usb_suspend_device.patch
All the fixes I had to do, dammit.
+x86_64-intel-multi-core.patch
+x86_64-intel-cache.patch
x86_64 tree updates
+clean-crypto-sha1c-up-a-bit.patch
crypto cleanup
+touchkit-ps-2-touchscreen-driver.patch
+touchkit-ps-2-touchscreen-driver-fixes.patch
New touchscreen driver
+mm-rss-=-file_rss-anon_rss-warning-fix.patch
Fix mm-rss-=-file_rss-anon_rss.patch
+core-remove-pagereserved-fix.patch
Fix core-remove-pagereserved.patch
+mm-i386-sh-sh64-ready-for-split-ptlock.patch
+mm-arm-ready-for-split-ptlock.patch
+mm-parisc-pte-atomicity.patch
+mm-cris-v32-mmu_context_lock.patch
+mm-uml-pte-atomicity.patch
+mm-uml-kill-unused.patch
+mm-split-page-table-lock.patch
+mm-split-page-table-lock-fixes.patch
+mm-split-page-table-lock-fixes-2.patch
+mm-split-page-table-lock-fixes-3.patch
+mm-fix-rss-and-mmlist-locking.patch
+mm-update-comments-to-pte-lock.patch
More core MM rework from Hugh.
+hugetlb-demand-fault-handler.patch
+hugetlb-overcommit-accounting-check.patch
+hugetlb-overcommit-accounting-check-fix.patch
Demand-paging for hugetlb pages
+mm-swap-prefetch-magnify.patch
Swap prefetching tuning
+mm-wider-use-of-for_each_cpu.patch
+mm-filemapcfilemap_populate-move-export.patch
mm cleanups
+net-wider-use-of-for_each_cpu.patch +netlink-remove-dead-code-in-af_netlinkc.patch +ipv4-remove-dead-code-from-ip_outputc.patch +fix-behavior-of-ip6_route_input-for-link-local-address.patch
Net fixes
+3c59x-dont-enable-scatter-gather-w-o-checksum.patch
3Com net driver fix
+revert-orinoco-information-leakage-due-to-incorrect-padding.patch +better-fixup-for-the-orinoco-driver.patch
Orinoco driver tweaks
+e1000-fixes-e1000_suspend-warning-when-config_pm-is-not.patch
Warning fix
+acx-update-2.patch
Update to the acx1xx wireless driver in -mm.
+selinux-remove-unecessary-size_t-checks-in-selinuxfs.patch
Cleanup
+ppc32-85xx-phy-platform-update.patch
+ppc32-ppc_sys-fixes-for-8xx-and-82xx.patch
ppc32 updates
+various-powerpc-32bit-ppc64-build-fixes.patch +ppc64-reenable-make-install-with-defconfig.patch +ppc64-change-name-of-target-file-during-make-install.patch +ppc64-remove-duplicate-local-variable-in-set_preferred_console.patch
ppc64 updates
+i386-move-apic-init-in-init_irqs-fix.patch
Fix i386-move-apic-init-in-init_irqs.patch
+x86-inline-spin_unlock-if-not-config_debug_spinlock-and-not-config_preempt.patch +x86-inline-spin_unlock_irq-if-not-config_debug_spinlock-and-not-config_preempt.patch +allow-users-to-force-a-panic-on-nmi.patch
x86 tweaks
+wistron-laptop-button-driver.patch
+wistron-laptop-button-driver-x86_64-fix.patch
Little laptop button driver
+x86_64-two-timer-entries-in-sys.patch
Fix duplicated sysfs entry on x86_64
+sharp-sl-5500-touchscreen-support.patch
+support-pcmcia-slot-on-sharp-sl-5500.patch
Sharp SL driver work
+swsusp-reduce-the-use-of-global-variables.patch +swsusp-remove-unneccessary-includes.patch +swsusp-cleanups.patch +swsusp-get-rid-of-unnecessary-wrapper-function.patch +swsusp-two-simplifications.patch
swsusp stuff
+get-rid-of-the-obsolete-tri-level-suspend-resume-callbacks-tda9887-fix.patch
Fix get-rid-of-the-obsolete-tri-level-suspend-resume-callbacks.patch
+cpuset-remove-depth-counted-locking-hack.patch
+cpuset-dual-semaphore-locking-overhaul.patch
+cpuset-simple-rename.patch
+cpuset-confine-pdflush-to-its-cpuset.patch
cpusets updates
+keys-get-rid-of-warning-in-kmodc-if-keys-disabled.patch
key management warning fix
+setkeys-needs-root.patch
The setkeys command now requires elevated caps
+extable-remove-needless-declaration.patch
Cleanup
+modules-fix-sparse-warning-for-every-module_parm.patch
sparse fixes
+compat-fcntl-fixes.patch
Fix compat_fcntl()
+fix-nr_unused-accounting-and-avoid-recursing-in-iput-with-i_will_free-set.patch
Fix dcache accounting
+test-for-sb_getblk-return-value.patch
+test-for-sb_getblk-return-value-fixes.patch
Check for sb_getblk() errors.
+fix-vgacon-blanking.patch
Fix blanking on the VGA console
+ktimers-kt2.patch
+ktimers-kt2-gcc-295-fix.patch
+ktimers-kt2-sparc64-fix.patch
Kernel timer infrastructure
+epca-updates-owner-field-of-struct-pci_driver.patch +synclink-adapters-updates-owner-field-of-struct-pci_driver.patch +watchdog-update-owner-field-of-struct-pci_driver.patch
sysfs friendliness for a few drivers
+include-linux-kernelhbuild_bug_on-fix-a-comment.patch
Comment fix
+fs-attrc-remove-bug.patch
Removed redundant check
+rcu-torture-testing-kernel-module.patch
In-kernel testbed for the RCU core
+propogate-gfp_t-changes-further.patch
Warning fixes
+ib-add-idr_destroy-calls-on-module-unload.patch
Infiniband microleak fix
+posix-cpu-timers-fix-overrun-reporting.patch
Fix posix CPU timers
-edac-drivers-for-radisys-82600-gregkh-borkage.patch
Dropped
+edac-core-edac-support-code-fixes-2.patch
+edac-core-edac-support-code-fixes-3.patch
+edac-clean-up-atomic-stuff.patch
EDAC driver updates
+hpet-allow-hpet-fixed_mem32-resource-type.patch
+hpet-use-hpet-physical-addresses-for-dup.patch
+hpet-hpet-driver-cleanups.patch
HPET updates
+remove-duplicate-code-in-signalc.patch
Cleanup
+ipmi-use-refcount-in-message-handler.patch
+ipmi-various-si-cleanup.patch
+ipmi-watchdog-parms-in-sysfs.patch
+ipmi-poweroff-cleanups.patch
+ipmi-more-dell-fixes.patch
+ipmi-si-start-transaction-hook.patch
+ipmi-bt-restart-reset-fixes.patch
+ipmi-kcs-error0-delay.patch
+ipmi-add-timer-thread.patch
IPMI updates
+udf-fix-issues-reported-by-coverity-in-inodec.patch +udf-fix-issues-reported-by-coverity-in-nameic.patch +ipmi-fix-issues-reported-by-coverity-in-ipmi_msghandlerc.patch +kernel-modulec-removed-dead-code.patch
Fix a few things from the Coverity checker
+dvb-usb-urb-printk-fix.patch
Warning fix
-deprecate-openfoo-3.patch
Dropped (it got a reject and I'm not really convinced about it)
+reiser4-page-private-fixes.patch
Update reiser4 for mm changes.
+serial-new-hp-diva-console-port.patch
Serial driver update
+rocketpoint-1520-fails-clock-stabilization-fix.patch
Fix rocketpoint-1520-fails-clock-stabilization.patch
+ide-explain-the-pci-bus-test.patch
Comment update
+nvidiafb-fix-mode-setting-ppc-support-fix.patch
Fix nvidiafb-fix-mode-setting-ppc-support.patch
+fbcon-fbdev-move-softcursor-out-of-fbdev-to-fbcon.patch +fbcon-consolidate-redundant-code.patch +fbcon-use-helper-function-when-filling-out-var-structure.patch +fbcon-initialize-new-driver-when-old-driver-is-released.patch +fbdev-remove-software-clipping-from-drawing.patch +vesafb-fix-color-palette-handling.patch +atyfb-get-initial-mode-timings-from-lcd-bios.patch +savagefb-convert-from-vga-io-access-to-mmio-access.patch +pm2fb-manual-configuration-of-timings-for-elsa-winner.patch +fbdev-workaround-for-buggy-edid-blocks.patch +nvidiafb-fix-empty-macro.patch +fbdev-fix-the-fb_find_nearest_mode-function.patch +s3c2410fb-initialise-device_driver-owner.patch +vesafb-disable-mtrr-as-the-default.patch +i810fb-cleanup-i2c-code.patch +console-fix-compile-error.patch +fbcon-add-rl-roman-large-font.patch
fbdev updates
+doc-hpettxt-change-to-80-columns.patch
+more-kernel-doc-cleanups-additions.patch
kerneldoc updates
+serial-disable-jsm-in-ppc64-defconfig.patch
Disable one currently-broken tty driver in defconfig
+isicom-pci-probing-added-fix.patch
Fix isicom-pci-probing-added.patch
All 1059 patches:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/patch-list
Andrew,
Could you please consider including the following in your -mm tree?
srat fix on i386, simple fix - no interest.
http://lkml.org/lkml/2005/9/16/14
cpusets on non-smp hardware, acked by Paul Jackson.
http://lkml.org/lkml/2005/10/3/48
Both applies on top of 2.6.14-rc5-mm1.
Many thanks,
/ magnus
Review
Quoted 9 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/
(quoted diff) +2
-0+x86-inline-spin_unlock-if-not-config_debug_spinlock-and-not-config_preempt.patch +x86-inline-spin_unlock_irq-if-not-config_debug_spinlock-and-not-config_preempt.patch x86 tweaks
those two breaks on UP since the lock can be NULL and it deferences it.
regards,
Benoit
Quoted 2 lines · Andrew Morton
- Added git-blktrace.patch to the -mm lineup: Jens's block-layer tracing
infrastructure. It appears to be undocumented...
If 20 pages of pdf documentation is undocumented, then we've raised the bar a lot when it comes to documentation :-)
If you pull the blktrace tools, there's a README in there and if you do a make docs it will generate a users manual for you.
I will update the in-kernel documentation, it does need a little work in the Kconfig section. And I'll add a pointer to the user tool repo which has a lot more info.
Signature · 1 line
Jens Axboe
Hiya,
Quoted 3 lines · Andrew Morton
+clean-crypto-sha1c-up-a-bit.patch
crypto cleanup
It seems this one breaks sha1 (on my AMD Sempron); quoting dmesg:
testing sha1
test 1:9c80d0f72a11fe6f3919c20ced200a71ea6a9a93
fail
test 2:ac94a4c354401d31f6642a6d53fe732c0cdca39a
fail
testing sha1 across pages
test 1:ac94a4c354401d31f6642a6d53fe732c0cdca39a
fail
Cheers,
Signature · 2 lines
Jasper Spaans http://jsp.vs19.net/ 16:03:17 up 10477 days, 6:50, 0 users, load average: 5.00 5.19 6.10
Quoted 1 line · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/
Compile problems.
Thanks,
Badari
elm3b29:/usr/src/linux-2.6.14-rc5 # make -j40 modules
CHK include/linux/version.h
CC [M] drivers/serial/jsm/jsm_tty.odrivers/serial/jsm/jsm_tty.c: In function `jsm_input':drivers/serial/jsm/jsm_tty.c:592: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:619: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:620: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:623: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:624: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:667: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:668: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:669: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:670: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:671: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:672: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:674: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:677: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:680: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:681: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:682: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:691: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:692: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:693: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:694: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:695: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:696: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:698: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:701: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:742: error: structure has no member named `flip'drivers/serial/jsm/jsm_tty.c:742: error: structure has no member named `flip'
make[3]: *** [drivers/serial/jsm/jsm_tty.o] Error 1 make[2]: *** [drivers/serial/jsm] Error 2
make[1]: *** [drivers/serial] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [drivers] Error 2
Quoted 8 lines · Badari Pulavarty
Quoted 1 line · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/
Compile problems.
Thanks,
Badari
Quoted 7 lines
elm3b29:/usr/src/linux-2.6.14-rc5 # make -j40 modules
CHKinclude/linux/version.h
CC [M]drivers/serial/jsm/jsm_tty.odrivers/serial/jsm/jsm_tty.c: In function `jsm_input':drivers/serial/jsm/jsm_tty.c:592: error: structure has no member named `flip'
...
Quoting Andrew's announcement:
- A number of tty drivers still won't compile.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 9 lines · Adrian Bunk
Quoted 5 lines
CC [M]
drivers/serial/jsm/jsm_tty.odrivers/serial/jsm/jsm_tty.c: In function `jsm_input':drivers/serial/jsm/jsm_tty.c:592: error: structure has no member named `flip'
...Quoting Andrew's announcement:
- A number of tty drivers still won't compile.
Should only be jsm that won't compile for any mainstream platform, if you find others that don't please email me.
Quoted 7 lines · Alan Cox
Quoted 6 lines · Adrian Bunk
Quoted 5 lines
CC [M]
drivers/serial/jsm/jsm_tty.odrivers/serial/jsm/jsm_tty.c: In function `jsm_input':drivers/serial/jsm/jsm_tty.c:592: error: structure has no member named `flip'
...
Quoted 6 lines
Quoted 3 lines
Quoting Andrew's announcement:
- A number of tty drivers still won't compile.
Should only be jsm that won't compile for any mainstream platform, if you find others that don't please email me.
The other ones I know about on i386 are:
drivers/char/stallion.c
drivers/char/istallion.c
drivers/char/riscom8.c
drivers/char/rio/riointr.c
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 5 lines · Adrian Bunk
The other ones I know about on i386 are:
drivers/char/stallion.c
drivers/char/istallion.c
drivers/char/riscom8.c
drivers/char/rio/riointr.c
Looking at the code I doubt they worked anyway given the cli() use and the like but the patch is attached for them.
drivers/char/stallion.c +15 -35
@@ -2902,7 +2902,8 @@if (portp->tty != (struct tty_struct *)NULL ) {if (portp->tty->driver_data == portp) { portp->stats.ttystate = portp->tty->flags; - portp->stats.rxbuffered = portp->tty->flip.count; +/* No longer available as a statistic */ + portp->stats.rxbuffered =1 ;/*portp->tty->flip.count; */ if (portp->tty->termios != (struct termios *)NULL ) { portp->stats.cflags = portp->tty->termios->c_cflag; portp->stats.iflags = portp->tty->termios->c_iflag;
@@ -4046,9 +4047,7 @@if ((ioack &ACK_TYPMASK ) ==ACK_TYPRXGOOD ) {outb ((RDCR + portp->uartaddr), ioaddr); len =inb (ioaddr +EREG_DATA ); -if ((tty == (struct tty_struct *)NULL ) || - (tty->flip.char_buf_ptr == (char *)NULL ) || - ((buflen =TTY_FLIPBUF_SIZE - tty->flip.count) ==0 )) { +if (tty ==NULL || (buflen =tty_buffer_request_room (tty, len)) ==0 ) { len =MIN (len,sizeof (stl_unwanted));outb ((RDSR + portp->uartaddr), ioaddr);insb ((ioaddr +EREG_DATA ), &stl_unwanted[0 ], len);
@@ -4057,12 +4056,10 @@ }else { len =MIN (len, buflen);if (len >0 ) { +unsigned char *ptr;outb ((RDSR + portp->uartaddr), ioaddr); -insb ((ioaddr +EREG_DATA ), tty->flip.char_buf_ptr, len); -memset (tty->flip.flag_buf_ptr,0 , len); - tty->flip.flag_buf_ptr += len; - tty->flip.char_buf_ptr += len; - tty->flip.count += len; +tty_prepare_flip_string (tty, &ptr, len); +insb ((ioaddr +EREG_DATA ), ptr, len);tty_schedule_flip (tty); portp->stats.rxtotal += len; }
@@ -4086,8 +4083,7 @@ portp->stats.txxoff++; goto stl_rxalldone; } -if ((tty != (struct tty_struct *)NULL ) && - ((portp->rxignoremsk & status) ==0 )) { +if (tty !=NULL && (portp->rxignoremsk & status) ==0 ) {if (portp->rxmarkmsk & status) {if (status &ST_BREAK ) { status =TTY_BREAK ;
@@ -4107,14 +4103,8 @@ }else { status =0 ; } -if (tty->flip.char_buf_ptr != (char *)NULL ) { -if (tty->flip.count <TTY_FLIPBUF_SIZE ) { - *tty->flip.flag_buf_ptr++ = status; - *tty->flip.char_buf_ptr++ = ch; - tty->flip.count++; - } -tty_schedule_flip (tty); - } +tty_insert_flip_char (tty, ch, status); +tty_schedule_flip (tty); } }else {printk ("STALLION: bad RX interrupt ack value=%x\n" , ioack);
@@ -5013,9 +5003,7 @@ len =inb (ioaddr +XP_DATA ) +1 ;if ((iack &IVR_TYPEMASK ) ==IVR_RXDATA ) { -if ((tty == (struct tty_struct *)NULL ) || - (tty->flip.char_buf_ptr == (char *)NULL ) || - ((buflen =TTY_FLIPBUF_SIZE - tty->flip.count) ==0 )) { +if (tty ==NULL || (buflen =tty_buffer_request_room (tty, len)) ==0 ) { len =MIN (len,sizeof (stl_unwanted));outb (GRXFIFO , (ioaddr +XP_ADDR ));insb ((ioaddr +XP_DATA ), &stl_unwanted[0 ], len);
@@ -5024,12 +5012,10 @@ }else { len =MIN (len, buflen);if (len >0 ) { +unsigned char *ptr;outb (GRXFIFO , (ioaddr +XP_ADDR )); -insb ((ioaddr +XP_DATA ), tty->flip.char_buf_ptr, len); -memset (tty->flip.flag_buf_ptr,0 , len); - tty->flip.flag_buf_ptr += len; - tty->flip.char_buf_ptr += len; - tty->flip.count += len; +tty_prepare_flip_string (tty, &ptr, len); +insb ((ioaddr +XP_DATA ), ptr, len);tty_schedule_flip (tty); portp->stats.rxtotal += len; }
@@ -5097,14 +5083,8 @@ status =0 ; } -if (tty->flip.char_buf_ptr != (char *)NULL ) { -if (tty->flip.count <TTY_FLIPBUF_SIZE ) { - *tty->flip.flag_buf_ptr++ = status; - *tty->flip.char_buf_ptr++ = ch; - tty->flip.count++; - } -tty_schedule_flip (tty); - } +tty_insert_flip_char (tty, ch, status); +tty_schedule_flip (tty);if (status ==0 ) portp->stats.rxtotal++;
drivers/char/istallion.c +9 -17
@@ -2714,17 +2714,13 @@ stlen = size - tail; } - len =MIN (len, (TTY_FLIPBUF_SIZE - tty->flip.count)); + len =tty_buffer_request_room (tty, len); +/* FIXME : iomap ? */ shbuf = (volatile char *)EBRDGETMEMPTR (brdp, portp->rxoffset);while (len >0 ) { stlen =MIN (len, stlen); -memcpy (tty->flip.char_buf_ptr, (char *) (shbuf + tail), stlen); -memset (tty->flip.flag_buf_ptr,0 , stlen); - tty->flip.char_buf_ptr += stlen; - tty->flip.flag_buf_ptr += stlen; - tty->flip.count += stlen; - +tty_insert_flip_string (tty, (char *)(shbuf + tail), stlen); len -= stlen; tail += stlen;if (tail >= size) {
@@ -2909,16 +2905,12 @@if ((nt.data &DT_RXBREAK ) && (portp->rxmarkmsk &BRKINT )) {if (tty != (struct tty_struct *)NULL ) { -if (tty->flip.count <TTY_FLIPBUF_SIZE ) { - tty->flip.count++; - *tty->flip.flag_buf_ptr++ =TTY_BREAK ; - *tty->flip.char_buf_ptr++ =0 ; -if (portp->flags &ASYNC_SAK ) { -do_SAK (tty); -EBRDENABLE (brdp); - } -tty_schedule_flip (tty); +tty_insert_flip_char (tty,0 ,TTY_BREAK ); +if (portp->flags &ASYNC_SAK ) { +do_SAK (tty); +EBRDENABLE (brdp); } +tty_schedule_flip (tty); } }
@@ -4943,7 +4935,7 @@if (portp->tty != (struct tty_struct *)NULL ) {if (portp->tty->driver_data == portp) { stli_comstats.ttystate = portp->tty->flags; - stli_comstats.rxbuffered = portp->tty->flip.count; + stli_comstats.rxbuffered =-1 /*portp->tty->flip.count*/ ;if (portp->tty->termios != (struct termios *)NULL ) { stli_comstats.cflags = portp->tty->termios->c_cflag; stli_comstats.iflags = portp->tty->termios->c_iflag;
drivers/char/riscom8.c +2 -2
@@ -399,7 +399,7 @@ flag =TTY_NORMAL ;tty_insert_flip_char (tty, ch, flag); -schedule_delayed_work (&tty->flip.work,1 ); +tty_flip_buffer_push (tty); }static inline void rc_receive (struct riscom_board const * bp)
@@ -428,7 +428,7 @@ }tty_insert_flip_char (tty,rc_in (bp,CD180_RDR ),TTY_NORMAL ); } -schedule_delayed_work (&tty->flip.work,1 ); +tty_flip_buffer_push (tty); }static inline void rc_transmit (struct riscom_board const * bp)
drivers/char/rio/riointr.c +5 -8
@@ -38,6 +38,7 @@#include <linux/slab.h> #include <linux/errno.h> #include <linux/tty.h> +#include <linux/tty_flip.h> #include <asm/io.h> #include <asm/system.h> #include <asm/string.h>
@@ -560,6 +561,7 @@struct PKT *PacketP; registeruint DataCnt;uchar * ptr; +unsigned char *buf;int copied =0 ;static int intCount, RxIntCnt;
@@ -657,8 +659,7 @@** and available space. */ - transCount = min_t(unsigned int, PacketP->len & PKT_LEN_MASK, -TTY_FLIPBUF_SIZE - TtyP->flip.count); + transCount =tty_buffer_request_room (TtyP, PacketP->len &PKT_LEN_MASK );rio_dprintk (RIO_DEBUG_REC ,"port %d: Copy %d bytes\n" , PortP->PortNum, transCount);/*
@@ -678,9 +679,8 @@#endif ptr = (uchar *) PacketP->data + PortP->RxDataStart; -rio_memcpy_fromio (TtyP->flip.char_buf_ptr, ptr, transCount); -memset (TtyP->flip.flag_buf_ptr,TTY_NORMAL , transCount); - +tty_prepare_flip_string (TtyP, &buf, transCount); +rio_memcpy_fromio (buf, ptr, transCount);#ifdef STATS /* ** keep a count for statistical purposes
@@ -690,9 +690,6 @@ PortP->RxDataStart += transCount; PacketP->len -= transCount; copied += transCount; - TtyP->flip.count += transCount; - TtyP->flip.char_buf_ptr += transCount; - TtyP->flip.flag_buf_ptr += transCount;#ifdef ___DEBUG_IT___
Quoted 10 lines · Alan Cox
Quoted 5 lines · Adrian Bunk
The other ones I know about on i386 are:
drivers/char/stallion.c
drivers/char/istallion.c
drivers/char/riscom8.c
drivers/char/rio/riointr.cLooking at the code I doubt they worked anyway given the
cli()use and the like but the patch is attached for them.
...
This left the following compile error solved by the trivial patch below:
<-- snip -->
...
CC drivers/char/riscom8.o
...drivers/char/riscom8.c: In function 'rc_receive_exc':drivers/char/riscom8.c:401: warning: implicit declaration of function 'tty_insert_flip_char' drivers/char/riscom8.c: In function 'rc_receive':drivers/char/riscom8.c:423: warning: implicit declaration of function 'tty_buffer_request_room'
...
LD .tmp_vmlinux1drivers/built-in.o: In function `rc_interrupt':
riscom8.c:(.text+0x281817): undefined reference to tty_insert_flip_char' riscom8.c:(.text+0x28189e): undefined reference to tty_insert_flip_char'
make: *** [.tmp_vmlinux1] Error 1
<-- snip -->
drivers/char/riscom8.c renamed from drivers/char/riscom8.c.old +1 -0
@@ -46,6 +46,7 @@#include <linux/major.h> #include <linux/init.h> #include <linux/delay.h> +#include <linux/tty_flip.h> #include <asm/uaccess.h>
Hi Andrew,
Quoted 2 lines · On Mon, 24 Oct 2005 01:48:38 -0700 Andrew Morton <[email protected]> wrote:
- Added git-mips.patch to the -mm lineup: Ralf's MIPS development tree.
This patch thrust back vr41xx to old Kconfig.
Also tb0287_config has been removed.
Please apply this patch.
Yoichi
arch/mips/Kconfig +4 -5
@@ -458,7 +458,9 @@ config DDB5477 ether port USB, AC97, PCI, etc. config MACH_VR41XX - bool "Support for NEC VR41XX-based machines" + bool "Support for NEC VR4100 series based machines" + select SYS_SUPPORTS_32BIT_KERNEL + select SYS_SUPPORTS_64BIT_KERNEL if EXPERIMENTAL config PMC_YOSEMITE bool "Support for PMC-Sierra Yosemite eval board"
@@ -937,9 +939,6 @@ config MIPS_L1_CACHE_SHIFT config HAVE_STD_PC_SERIAL_PORT bool -config VR4181 - bool - config ARC_CONSOLE bool "ARC console support" depends on SGI_IP22 || SNI_RM200_PCI
@@ -1044,7 +1043,7 @@ config CPU_VR41XX select CPU_SUPPORTS_32BIT_KERNEL select CPU_SUPPORTS_64BIT_KERNEL help - The options selects support for the NEC VR41xx series of processors. + The options selects support for the NEC VR4100 series of processors. Only choose this option if you have one of these processors as a kernel built with this option will not run on any other type of processor or vice versa.
arch/mips/configs/tb0287_defconfig +1105 -0
1,105 lines not on this page · raw message
arch/mips/vr41xx/Kconfig +35 -42
123 lines not on this page · raw message
Quoted 19 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/
- At great personal cost I managed to coax most of the USB devel tree into compiling and booting. We're hoping that the changes in here will improve USB-related power management (suspend and resume). Please cc [email protected] on any bug reports (or use bugzilla).
- Added git-blktrace.patch to the -mm lineup: Jens's block-layer tracing
infrastructure. It appears to be undocumented...- Added git-block.patch to the -mm lineup: Jens's block tree (
drivers/block/*.c, basically).- Added git-mips.patch to the -mm lineup: Ralf's MIPS development tree.
- Lots more core MM changes from Hugh: mainly to address
page_table_lockSMP scalability issuse. All this code is in place now (I think), so performance testing time is here.
Quoted 6 lines
- Demand-paging for hugetlb pages. Needs very careful testing.
- Added Thomas's ktimer patch.
- A number of tty drivers still won't compile.
(Second try at sending this message. The first one got eaten by the gmane server. Apologies for the noise if you receive this twice.)
Hi,
This release has a number of build errors for me. I used the vanilla 2.6.14-rc5 + 2.6.14-rc5-mm1 patch + CK's 1GB lowmem patch.
Here is the make output and the .config listing:
$ make
CHK include/linux/version.h
UPD include/linux/version.h
SYMLINK include/asm -> include/asm-i386
SPLIT include/linux/autoconf.h -> include/config/*
CC arch/i386/kernel/asm-offsets.s
GEN include/asm-i386/asm-offsets.h
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/mod/modpost.o
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
HOSTCC scripts/conmakehash
CC init/main.o
In file included from init/main.c:50:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
CC init/do_mounts.o
LD init/mounts.o
CC init/initramfs.o
CC init/calibrate.o
LD init/built-in.o
HOSTCC usr/gen_init_cpio
CHK usr/initramfs_list
UPD usr/initramfs_list
CPIO usr/initramfs_data.cpio
GZIP usr/initramfs_data.cpio.gz
AS usr/initramfs_data.o
LD usr/built-in.o
CC arch/i386/kernel/process.o
CC arch/i386/kernel/semaphore.o
CC arch/i386/kernel/signal.o
AS arch/i386/kernel/entry.o
CC arch/i386/kernel/traps.o
CC arch/i386/kernel/irq.o
CC arch/i386/kernel/vm86.o
CC arch/i386/kernel/ptrace.o
arch/i386/kernel/ptrace.c: In function `sys_ptrace':
arch/i386/kernel/ptrace.c:383: warning: implicit declaration of function `__raw_read_unlock'
CC arch/i386/kernel/time.o
CC arch/i386/kernel/ioport.o
CC arch/i386/kernel/ldt.o
CC arch/i386/kernel/setup.o
CC arch/i386/kernel/i8259.o
CC arch/i386/kernel/sys_i386.o
CC arch/i386/kernel/pci-dma.o
CC arch/i386/kernel/i386_ksyms.o
CC arch/i386/kernel/i387.o
CC arch/i386/kernel/dmi_scan.o
CC arch/i386/kernel/bootflag.o
CC arch/i386/kernel/doublefault.o
CC arch/i386/kernel/quirks.o
CC arch/i386/kernel/i8237.o
CC arch/i386/kernel/cpu/common.o
CC arch/i386/kernel/cpu/proc.o
CC arch/i386/kernel/cpu/amd.o
CC arch/i386/kernel/cpu/cyrix.o
CC arch/i386/kernel/cpu/centaur.o
CC arch/i386/kernel/cpu/transmeta.o
CC arch/i386/kernel/cpu/intel.o
CC arch/i386/kernel/cpu/intel_cacheinfo.o
CC arch/i386/kernel/cpu/rise.o
CC arch/i386/kernel/cpu/nexgen.o
CC arch/i386/kernel/cpu/umc.o
CC arch/i386/kernel/cpu/mcheck/mce.o
CC arch/i386/kernel/cpu/mcheck/k7.o
CC arch/i386/kernel/cpu/mcheck/p4.o
CC arch/i386/kernel/cpu/mcheck/p5.o
CC arch/i386/kernel/cpu/mcheck/p6.o
CC arch/i386/kernel/cpu/mcheck/winchip.o
CC arch/i386/kernel/cpu/mcheck/non-fatal.o
LD arch/i386/kernel/cpu/mcheck/built-in.o
CC arch/i386/kernel/cpu/mtrr/main.o
CC arch/i386/kernel/cpu/mtrr/if.o
CC arch/i386/kernel/cpu/mtrr/generic.o
CC arch/i386/kernel/cpu/mtrr/state.o
CC arch/i386/kernel/cpu/mtrr/amd.o
CC arch/i386/kernel/cpu/mtrr/cyrix.o
CC arch/i386/kernel/cpu/mtrr/centaur.o
LD arch/i386/kernel/cpu/mtrr/built-in.o
LD arch/i386/kernel/cpu/built-in.o
CC arch/i386/kernel/timers/timer.o
CC arch/i386/kernel/timers/timer_none.o
CC arch/i386/kernel/timers/timer_tsc.o
CC arch/i386/kernel/timers/timer_pit.o
CC arch/i386/kernel/timers/common.o
CC arch/i386/kernel/timers/timer_hpet.o
LD arch/i386/kernel/timers/built-in.o
CC arch/i386/kernel/reboot.o
CC arch/i386/kernel/apm.o
arch/i386/kernel/apm.c: In function `suspend':
arch/i386/kernel/apm.c:1186: warning: `pm_send_all' is deprecated (declared at include/linux/pm.h:122)
arch/i386/kernel/apm.c:1240: warning: `pm_send_all' is deprecated (declared at include/linux/pm.h:122)
arch/i386/kernel/apm.c: In function `check_events':
arch/i386/kernel/apm.c:1361: warning: `pm_send_all' is deprecated (declared at include/linux/pm.h:122)
CC arch/i386/kernel/mpparse.o
CC arch/i386/kernel/apic.o
CC arch/i386/kernel/nmi.o
CC arch/i386/kernel/io_apic.o
CC arch/i386/kernel/module.o
CC arch/i386/kernel/sysenter.o
LDS arch/i386/kernel/vsyscall.lds
AS arch/i386/kernel/vsyscall-int80.o
AS arch/i386/kernel/vsyscall-note.o
SYSCALL arch/i386/kernel/vsyscall-int80.so
AS arch/i386/kernel/vsyscall-sysenter.o
SYSCALL arch/i386/kernel/vsyscall-sysenter.so
AS arch/i386/kernel/vsyscall.o
CC arch/i386/kernel/time_hpet.o
CC arch/i386/kernel/early_printk.o
SYSCALL arch/i386/kernel/vsyscall-syms.o
LD arch/i386/kernel/built-in.o
AS arch/i386/kernel/head.o
CC arch/i386/kernel/init_task.o
LDS arch/i386/kernel/vmlinux.lds
CC arch/i386/mm/init.o
CC arch/i386/mm/pgtable.o
CC arch/i386/mm/fault.o
CC arch/i386/mm/ioremap.o
arch/i386/mm/ioremap.c: In function `iounmap':
arch/i386/mm/ioremap.c:257: warning: implicit declaration of function `__raw_write_unlock'
CC arch/i386/mm/extable.o
CC arch/i386/mm/pageattr.o
CC arch/i386/mm/mmap.o
LD arch/i386/mm/built-in.o
CC arch/i386/mach-default/setup.o
CC arch/i386/mach-default/topology.o
LD arch/i386/mach-default/built-in.o
LD arch/i386/crypto/built-in.o
CC kernel/sched.o
kernel/sched.c: In function `do_sched_setscheduler':
kernel/sched.c:3805: warning: implicit declaration of function `__raw_read_unlock'
CC kernel/fork.o
kernel/fork.c: In function `__copy_fs_struct':
kernel/fork.c:542: warning: implicit declaration of function `__raw_read_unlock'
kernel/fork.c: In function `copy_process':
kernel/fork.c:1070: warning: implicit declaration of function `__raw_write_unlock'
CC kernel/exec_domain.o
kernel/exec_domain.c: In function `lookup_exec_domain':
kernel/exec_domain.c:70: warning: implicit declaration of function `__raw_read_unlock'
kernel/exec_domain.c: In function `register_exec_domain':
kernel/exec_domain.c:110: warning: implicit declaration of function `__raw_write_unlock'
CC kernel/panic.o
CC kernel/printk.o
CC kernel/profile.o
CC kernel/exit.o
kernel/exit.c: In function `release_task':
kernel/exit.c:104: warning: implicit declaration of function `__raw_write_unlock'
kernel/exit.c: In function `session_of_pgrp':
kernel/exit.c:151: warning: implicit declaration of function `__raw_read_unlock'
CC kernel/itimer.o
kernel/itimer.c: In function `do_getitimer':
kernel/itimer.c:78: warning: implicit declaration of function `__raw_read_unlock'
CC kernel/time.o
CC kernel/softirq.o
CC kernel/resource.o
kernel/resource.c: In function `r_stop':
kernel/resource.c:73: warning: implicit declaration of function `__raw_read_unlock'
kernel/resource.c: In function `request_resource':
kernel/resource.c:207: warning: implicit declaration of function `__raw_write_unlock'
CC kernel/sysctl.o
CC kernel/capability.o
kernel/capability.c: In function `sys_capget':
kernel/capability.c:81: warning: implicit declaration of function `__raw_read_unlock'
CC kernel/ptrace.o
kernel/ptrace.c: In function `ptrace_check_attach':
kernel/ptrace.c:114: warning: implicit declaration of function `__raw_read_unlock'
kernel/ptrace.c: In function `ptrace_attach':
kernel/ptrace.c:176: warning: implicit declaration of function `__raw_write_unlock'
CC kernel/timer.o
CC kernel/user.o
CC kernel/signal.o
kernel/signal.c: In function `exit_sighand':
kernel/signal.c:339: warning: implicit declaration of function `__raw_write_unlock'
kernel/signal.c: In function `kill_pg_info':
kernel/signal.c:1137: warning: implicit declaration of function `__raw_read_unlock'
CC kernel/sys.o
kernel/sys.c: In function `notifier_chain_register':
kernel/sys.c:119: warning: implicit declaration of function `__raw_write_unlock'
kernel/sys.c: In function `sys_setpriority':
kernel/sys.c:298: warning: implicit declaration of function `__raw_read_unlock'
CC kernel/kmod.o
CC kernel/workqueue.o
kernel/workqueue.c: In function `current_is_keventd':
kernel/workqueue.c:460: warning: unused variable `cpu'
CC kernel/pid.o
CC kernel/rcupdate.o
CC kernel/intermodule.o
kernel/intermodule.c:178: warning: `inter_module_register' is deprecated (declared at kernel/intermodule.c:38)
kernel/intermodule.c:179: warning: `inter_module_unregister' is deprecated (declared at kernel/intermodule.c:78)
kernel/intermodule.c:181: warning: `inter_module_put' is deprecated (declared at kernel/intermodule.c:159)
CC kernel/extable.o
CC kernel/params.o
CC kernel/posix-timers.o
kernel/posix-timers.c: In function `sys_timer_create':
kernel/posix-timers.c:546: warning: implicit declaration of function `__raw_read_unlock'
CC kernel/kthread.o
CC kernel/wait.o
CC kernel/kfifo.o
CC kernel/sys_ni.o
CC kernel/posix-cpu-timers.o
kernel/posix-cpu-timers.c: In function `check_clock':
kernel/posix-cpu-timers.c:28: warning: implicit declaration of function `__raw_read_unlock'
CC kernel/ktimers.o
CC kernel/futex.o
CC kernel/dma.o
CC kernel/uid16.o
CC kernel/module.o
CC kernel/irq/handle.o
CC kernel/irq/manage.o
CC kernel/irq/spurious.o
CC kernel/irq/autoprobe.o
CC kernel/irq/proc.o
LD kernel/irq/built-in.o
CC kernel/power/main.o
CC kernel/power/process.o
kernel/power/process.c: In function `freeze_processes':
kernel/power/process.c:82: warning: implicit declaration of function `__raw_read_unlock'
CC kernel/power/console.o
CC kernel/power/pm.o
kernel/power/pm.c:258: warning: `pm_register' is deprecated (declared at kernel/power/pm.c:62)
kernel/power/pm.c:259: warning: `pm_unregister' is deprecated (declared at kernel/power/pm.c:85)
kernel/power/pm.c:260: warning: `pm_unregister_all' is deprecated (declared at kernel/power/pm.c:114)
kernel/power/pm.c:261: warning: `pm_send_all' is deprecated (declared at kernel/power/pm.c:233)
LD kernel/power/built-in.o
CC kernel/ksysfs.o
CC kernel/seccomp.o
LD kernel/built-in.o
CC mm/bootmem.o
CC mm/filemap.o
mm/filemap.c: In function `remove_from_page_cache':
mm/filemap.c:130: warning: implicit declaration of function `__raw_write_unlock'
mm/filemap.c: In function `find_get_page':
mm/filemap.c:532: warning: implicit declaration of function `__raw_read_unlock'
CC mm/mempool.o
CC mm/oom_kill.o
mm/oom_kill.c: In function `out_of_memory':
mm/oom_kill.c:286: warning: implicit declaration of function `__raw_read_unlock'
CC mm/fadvise.o
CC mm/page_alloc.o
CC mm/page-writeback.o
mm/page-writeback.c: In function `__set_page_dirty_nobuffers':
mm/page-writeback.c:633: warning: implicit declaration of function `__raw_write_unlock'
CC mm/pdflush.o
CC mm/readahead.o
mm/readahead.c: In function `__do_page_cache_readahead':
mm/readahead.c:287: warning: implicit declaration of function `__raw_read_unlock'
CC mm/slab.o
CC mm/swap.o
CC mm/truncate.o
mm/truncate.c: In function `invalidate_complete_page':
mm/truncate.c:79: warning: implicit declaration of function `__raw_write_unlock'
CC mm/vmscan.o
mm/vmscan.c: In function `shrink_list':
mm/vmscan.c:532: warning: implicit declaration of function `__raw_write_unlock'
CC mm/prio_tree.o
CC mm/fremap.o
CC mm/highmem.o
CC mm/madvise.o
CC mm/memory.o
CC mm/mincore.o
CC mm/mlock.o
CC mm/mmap.o
CC mm/mprotect.o
CC mm/mremap.o
CC mm/msync.o
CC mm/rmap.o
CC mm/vmalloc.o
mm/vmalloc.c: In function `__get_vm_area_node':
mm/vmalloc.c:221: warning: implicit declaration of function `__raw_write_unlock'
mm/vmalloc.c: In function `vread':
mm/vmalloc.c:594: warning: implicit declaration of function `__raw_read_unlock'
CC mm/page_io.o
CC mm/swap_state.o
mm/swap_state.c: In function `__add_to_swap_cache':
mm/swap_state.c:90: warning: implicit declaration of function `__raw_write_unlock'
CC mm/swapfile.o
mm/swapfile.c: In function `remove_exclusive_swap_page':
mm/swapfile.c:355: warning: implicit declaration of function `__raw_write_unlock'
CC mm/thrash.o
CC mm/swap_prefetch.o
mm/swap_prefetch.c: In function `trickle_swap_cache_async':
mm/swap_prefetch.c:232: warning: implicit declaration of function `__raw_read_unlock'
CC mm/shmem.o
LD mm/built-in.o
CC fs/open.o
CC fs/read_write.o
CC fs/file_table.o
CC fs/buffer.o
fs/buffer.c: In function `__set_page_dirty_buffers':
fs/buffer.c:871: warning: implicit declaration of function `__raw_write_unlock'
CC fs/bio.o
CC fs/super.o
CC fs/block_dev.o
CC fs/char_dev.o
CC fs/stat.o
CC fs/exec.o
fs/exec.c: In function `register_binfmt':
fs/exec.c:80: warning: implicit declaration of function `__raw_write_unlock'
fs/exec.c: In function `sys_uselib':
fs/exec.c:156: warning: implicit declaration of function `__raw_read_unlock'
CC fs/pipe.o
CC fs/namei.o
fs/namei.c: In function `walk_init_root':
fs/namei.c:463: warning: implicit declaration of function `__raw_read_unlock'
fs/namei.c: In function `set_fs_altroot':
fs/namei.c:1026: warning: implicit declaration of function `__raw_write_unlock'
CC fs/fcntl.o
fs/fcntl.c: In function `f_modown':
fs/fcntl.c:259: warning: implicit declaration of function `__raw_write_unlock'
fs/fcntl.c: In function `send_sigio':
fs/fcntl.c:489: warning: implicit declaration of function `__raw_read_unlock'
CC fs/ioctl.o
CC fs/readdir.o
CC fs/select.o
CC fs/fifo.o
CC fs/locks.o
CC fs/dcache.o
fs/dcache.c: In function `d_path':
fs/dcache.c:1601: warning: implicit declaration of function `__raw_read_unlock'
CC fs/inode.o
CC fs/attr.o
CC fs/bad_inode.o
CC fs/file.o
CC fs/filesystems.o
fs/filesystems.c: In function `register_filesystem':
fs/filesystems.c:83: warning: implicit declaration of function `__raw_write_unlock'
fs/filesystems.c: In function `fs_index':
fs/filesystems.c:141: warning: implicit declaration of function `__raw_read_unlock'
CC fs/namespace.o
fs/namespace.c: In function `set_fs_root':
fs/namespace.c:1210: warning: implicit declaration of function `__raw_write_unlock'
fs/namespace.c: In function `chroot_fs_refs':
fs/namespace.c:1260: warning: implicit declaration of function `__raw_read_unlock'
CC fs/aio.o
fs/aio.c: In function `ioctx_alloc':
fs/aio.c:244: warning: implicit declaration of function `__raw_write_unlock'
fs/aio.c: In function `lookup_ioctx':
fs/aio.c:545: warning: implicit declaration of function `__raw_read_unlock'
CC fs/seq_file.o
CC fs/xattr.o
CC fs/libfs.o
CC fs/fs-writeback.o
CC fs/mpage.o
CC fs/direct-io.o
CC fs/ioprio.o
fs/ioprio.c: In function `sys_ioprio_set':
fs/ioprio.c:116: warning: implicit declaration of function `__raw_read_unlock'
CC fs/eventpoll.o
CC fs/nfsctl.o
CC fs/binfmt_script.o
CC fs/binfmt_elf.o
fs/binfmt_elf.c: In function `elf_core_dump':
fs/binfmt_elf.c:1459: warning: implicit declaration of function `__raw_read_unlock'
LD fs/cifs/built-in.o
CC [M] fs/cifs/cifsfs.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/cifsfs.c:36:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
fs/cifs/cifsfs.c: At top level:
fs/cifs/cifsfs.c:409: warning: 'cifs_umount_begin' defined but not used
CC [M] fs/cifs/cifssmb.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/cifssmb.c:35:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/cifs_debug.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/cifs_debug.c:28:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/connect.o
In file included from include/linux/tcp.h:180,
from include/linux/ipv6.h:177,
from fs/cifs/connect.c:26:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/dir.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/dir.c:28:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/file.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/file.c:35:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/inode.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/inode.c:27:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/link.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/link.c:25:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/misc.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/misc.c:25:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/netmisc.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/netmisc.c:34:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/smbdes.o
CC [M] fs/cifs/smbencrypt.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/smbencrypt.c:32:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/transport.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/transport.c:30:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/asn1.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/asn1.c:26:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/md4.o
CC [M] fs/cifs/md5.o
CC [M] fs/cifs/cifs_unicode.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/cifs_unicode.c:24:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/nterr.o
CC [M] fs/cifs/xattr.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/xattr.c:25:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/cifsencrypt.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/cifsencrypt.c:23:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/fcntl.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/cifsglob.h:56,
from fs/cifs/fcntl.c:26:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/readdir.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/readdir.c:26:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/cifs/ioctl.o
In file included from fs/cifs/cifspdu.h:25,
from fs/cifs/ioctl.c:26:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
LD [M] fs/cifs/cifs.o
CC fs/devpts/inode.o
LD fs/devpts/devpts.o
LD fs/devpts/built-in.o
LD fs/exportfs/built-in.o
CC [M] fs/exportfs/expfs.o
LD [M] fs/exportfs/exportfs.o
LD fs/ext2/built-in.o
CC [M] fs/ext2/balloc.o
fs/ext2/balloc.c: In function `ext2_new_block':
fs/ext2/balloc.c:500: warning: implicit declaration of function `__raw_write_unlock'
CC [M] fs/ext2/bitmap.o
CC [M] fs/ext2/dir.o
CC [M] fs/ext2/file.o
CC [M] fs/ext2/fsync.o
CC [M] fs/ext2/ialloc.o
CC [M] fs/ext2/inode.o
fs/ext2/inode.c: In function `ext2_discard_prealloc':
fs/ext2/inode.c:102: warning: implicit declaration of function `__raw_write_unlock'
fs/ext2/inode.c: In function `ext2_get_branch':
fs/ext2/inode.c:287: warning: implicit declaration of function `__raw_read_unlock'
CC [M] fs/ext2/ioctl.o
CC [M] fs/ext2/namei.o
CC [M] fs/ext2/super.o
CC [M] fs/ext2/symlink.o
LD [M] fs/ext2/ext2.o
LD fs/fat/built-in.o
CC [M] fs/fat/cache.o
CC [M] fs/fat/dir.o
CC [M] fs/fat/fatent.o
CC [M] fs/fat/file.o
CC [M] fs/fat/inode.o
CC [M] fs/fat/misc.o
LD [M] fs/fat/fat.o
LD fs/fuse/built-in.o
CC [M] fs/fuse/dev.o
CC [M] fs/fuse/dir.o
CC [M] fs/fuse/file.o
CC [M] fs/fuse/inode.o
LD [M] fs/fuse/fuse.o
LD fs/isofs/built-in.o
CC [M] fs/isofs/namei.o
CC [M] fs/isofs/inode.o
CC [M] fs/isofs/dir.o
CC [M] fs/isofs/util.o
CC [M] fs/isofs/rock.o
CC [M] fs/isofs/export.o
CC [M] fs/isofs/joliet.o
LD [M] fs/isofs/isofs.o
LD fs/lockd/built-in.o
CC [M] fs/lockd/clntlock.o
CC [M] fs/lockd/clntproc.o
CC [M] fs/lockd/host.o
CC [M] fs/lockd/svc.o
CC [M] fs/lockd/svclock.o
CC [M] fs/lockd/svcshare.o
CC [M] fs/lockd/svcproc.o
CC [M] fs/lockd/svcsubs.o
CC [M] fs/lockd/mon.o
CC [M] fs/lockd/xdr.o
CC [M] fs/lockd/xdr4.o
CC [M] fs/lockd/svc4proc.o
LD [M] fs/lockd/lockd.o
LD fs/nfs/built-in.o
CC [M] fs/nfs/dir.o
CC [M] fs/nfs/file.o
CC [M] fs/nfs/inode.o
CC [M] fs/nfs/nfs2xdr.o
CC [M] fs/nfs/pagelist.o
CC [M] fs/nfs/proc.o
CC [M] fs/nfs/read.o
CC [M] fs/nfs/symlink.o
CC [M] fs/nfs/unlink.o
CC [M] fs/nfs/write.o
CC [M] fs/nfs/nfs3proc.o
CC [M] fs/nfs/nfs3xdr.o
LD [M] fs/nfs/nfs.o
LD fs/nfs_common/built-in.o
LD fs/nfsd/built-in.o
CC [M] fs/nfsd/nfssvc.o
CC [M] fs/nfsd/nfsctl.o
CC [M] fs/nfsd/nfsproc.o
CC [M] fs/nfsd/nfsfh.o
CC [M] fs/nfsd/vfs.o
CC [M] fs/nfsd/export.o
fs/nfsd/export.c: In function `svc_expkey_lookup':
fs/nfsd/export.c:259: warning: implicit declaration of function `__raw_write_unlock'
fs/nfsd/export.c:259: warning: implicit declaration of function `__raw_read_unlock'
CC [M] fs/nfsd/auth.o
CC [M] fs/nfsd/lockd.o
CC [M] fs/nfsd/nfscache.o
CC [M] fs/nfsd/nfsxdr.o
CC [M] fs/nfsd/stats.o
CC [M] fs/nfsd/nfs3proc.o
CC [M] fs/nfs/nfs3xdr.o
LD [M] fs/nfs/nfs.o
LD fs/nfs_common/built-in.o
LD fs/nfsd/built-in.o
CC [M] fs/nfsd/nfssvc.o
CC [M] fs/nfsd/nfsctl.o
CC [M] fs/nfsd/nfsproc.o
CC [M] fs/nfsd/nfsfh.o
CC [M] fs/nfsd/vfs.o
CC [M] fs/nfsd/export.o
fs/nfsd/export.c: In function `svc_expkey_lookup':
fs/nfsd/export.c:259: warning: implicit declaration of function `__raw_write_unlock'
fs/nfsd/export.c:259: warning: implicit declaration of function `__raw_read_unlock'
CC [M] fs/nfsd/auth.o
CC [M] fs/nfsd/lockd.o
CC [M] fs/nfsd/nfscache.o
CC [M] fs/nfsd/nfsxdr.o
CC [M] fs/nfsd/stats.o
CC [M] fs/nfsd/nfs3proc.o
CC [M] fs/nfsd/nfs3xdr.o
LD [M] fs/nfsd/nfsd.o
LD fs/nls/built-in.o
CC [M] fs/nls/nls_base.o
CC fs/partitions/check.o
CC fs/partitions/msdos.o
LD fs/partitions/built-in.o
CC fs/proc/mmu.o
fs/proc/mmu.c: In function `get_vmalloc_info':
fs/proc/mmu.c:75: warning: implicit declaration of function `__raw_read_unlock'
CC fs/proc/task_mmu.o
CC fs/proc/inode.o
CC fs/proc/root.o
CC fs/proc/base.o
fs/proc/base.c: In function `proc_cwd_link':
fs/proc/base.c:329: warning: implicit declaration of function `__raw_read_unlock'
CC fs/proc/generic.o
CC fs/proc/array.o
fs/proc/array.c: In function `task_state':
fs/proc/array.c:182: warning: implicit declaration of function `__raw_read_unlock'
CC fs/proc/kmsg.o
CC fs/proc/proc_tty.o
CC fs/proc/proc_misc.o
LD fs/proc/proc.o
LD fs/proc/built-in.o
CC fs/ramfs/inode.o
LD fs/ramfs/ramfs.o
LD fs/ramfs/built-in.o
CC fs/reiserfs/bitmap.o
CC fs/reiserfs/do_balan.o
CC fs/reiserfs/namei.o
CC fs/reiserfs/inode.o
CC fs/reiserfs/file.o
CC fs/reiserfs/dir.o
CC fs/reiserfs/fix_node.o
CC fs/reiserfs/super.o
CC fs/reiserfs/prints.o
CC fs/reiserfs/objectid.o
CC fs/reiserfs/lbalance.o
CC fs/reiserfs/ibalance.o
CC fs/reiserfs/stree.o
CC fs/reiserfs/hashes.o
CC fs/reiserfs/tail_conversion.o
CC fs/reiserfs/journal.o
CC fs/reiserfs/resize.o
CC fs/reiserfs/item_ops.o
CC fs/reiserfs/ioctl.o
CC fs/reiserfs/procfs.o
LD fs/reiserfs/reiserfs.o
LD fs/reiserfs/built-in.o
CC fs/sysfs/inode.o
CC fs/sysfs/file.o
CC fs/sysfs/dir.o
CC fs/sysfs/symlink.o
CC fs/sysfs/mount.o
CC fs/sysfs/bin.o
CC fs/sysfs/group.o
LD fs/sysfs/built-in.o
LD fs/vfat/built-in.o
CC [M] fs/vfat/namei.o
LD [M] fs/vfat/vfat.o
LD fs/built-in.o
CC ipc/util.o
CC ipc/msgutil.o
CC ipc/msg.o
CC ipc/sem.o
CC ipc/shm.o
LD ipc/built-in.o
CC security/commoncap.o
LD security/built-in.o
LD crypto/built-in.o
CC drivers/base/core.o
CC drivers/base/sys.o
CC drivers/base/bus.o
CC drivers/base/dd.o
CC drivers/base/driver.o
CC drivers/base/class.o
CC drivers/base/platform.o
CC drivers/base/cpu.o
CC drivers/base/firmware.o
CC drivers/base/init.o
CC drivers/base/map.o
CC drivers/base/dmapool.o
CC drivers/base/attribute_container.o
CC drivers/base/transport_class.o
CC drivers/base/power/shutdown.o
CC drivers/base/power/main.o
CC drivers/base/power/suspend.o
CC drivers/base/power/resume.o
CC drivers/base/power/runtime.o
CC drivers/base/power/sysfs.o
LD drivers/base/power/built-in.o
LD drivers/base/built-in.o
CC drivers/block/elevator.o
drivers/block/elevator.c: In function `elv_unregister':
drivers/block/elevator.c:597: warning: implicit declaration of function `__raw_read_unlock'
CC drivers/block/ll_rw_blk.o
CC drivers/block/ioctl.o
CC drivers/block/genhd.o
CC drivers/block/scsi_ioctl.o
CC drivers/block/noop-iosched.o
CC drivers/block/cfq-iosched.o
LD drivers/block/built-in.o
CC [M] drivers/block/floppy.o
CC [M] drivers/block/loop.o
CC drivers/cdrom/cdrom.o
LD drivers/cdrom/built-in.o
CC drivers/char/mem.o
CC drivers/char/random.o
CC drivers/char/tty_io.o
drivers/char/tty_io.c: In function `do_tty_hangup':
drivers/char/tty_io.c:1085: warning: implicit declaration of function `__raw_read_unlock'
CC drivers/char/n_tty.o
CC drivers/char/tty_ioctl.o
CC drivers/char/pty.o
CC drivers/char/misc.o
CC drivers/char/vt_ioctl.o
CC drivers/char/vc_screen.o
CC drivers/char/consolemap.o
CONMK drivers/char/consolemap_deftbl.c
CC drivers/char/consolemap_deftbl.o
CC drivers/char/selection.o
CC drivers/char/keyboard.o
CC drivers/char/vt.o
SHIPPED drivers/char/defkeymap.c
CC drivers/char/defkeymap.o
LD drivers/char/built-in.o
LD drivers/firmware/built-in.o
LD drivers/ide/arm/built-in.o
LD drivers/ide/legacy/built-in.o
CC drivers/ide/pci/amd74xx.o
LD drivers/ide/pci/built-in.o
CC drivers/ide/ide.o
CC drivers/ide/ide-io.o
CC drivers/ide/ide-iops.o
CC drivers/ide/ide-lib.o
CC drivers/ide/ide-probe.o
CC drivers/ide/ide-taskfile.o
CC drivers/ide/setup-pci.o
CC drivers/ide/ide-dma.o
CC drivers/ide/ide-proc.o
LD drivers/ide/ide-core.o
CC drivers/ide/ide-disk.o
CC drivers/ide/ide-cd.o
LD drivers/ide/built-in.o
CC drivers/input/input.o
CC drivers/input/keyboard/atkbd.o
LD drivers/input/keyboard/built-in.o
LD drivers/input/built-in.o
CC drivers/input/serio/serio.o
CC drivers/input/serio/i8042.o
CC drivers/input/serio/libps2.o
LD drivers/input/serio/built-in.o
LD drivers/media/common/built-in.o
LD drivers/media/built-in.o
LD drivers/mfd/built-in.o
LD drivers/misc/built-in.o
CC drivers/net/Space.o
CC drivers/net/loopback.o
In file included from drivers/net/loopback.c:53:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
LD drivers/net/built-in.o
CC [M] drivers/net/3c59x.o
CC [M] drivers/net/mii.o
CC [M] drivers/net/dummy.o
CC drivers/pci/access.o
CC drivers/pci/bus.o
CC drivers/pci/probe.o
CC drivers/pci/remove.o
CC drivers/pci/pci.o
CC drivers/pci/quirks.o
CC drivers/pci/pci-driver.o
CC drivers/pci/search.o
CC drivers/pci/pci-sysfs.o
CC drivers/pci/rom.o
CC drivers/pci/setup-res.o
CC drivers/pci/proc.o
CC drivers/pci/setup-bus.o
CC drivers/pci/msi.o
LD drivers/pci/built-in.o
LD drivers/serial/built-in.o
CC drivers/usb/host/pci-quirks.o
LD drivers/usb/host/built-in.o
LD drivers/usb/built-in.o
LD drivers/video/backlight/built-in.o
CC drivers/video/console/dummycon.o
CC drivers/video/console/vgacon.o
LD drivers/video/console/built-in.o
LD drivers/video/built-in.o
LD drivers/built-in.o
LD sound/built-in.o
CC arch/i386/pci/i386.o
CC arch/i386/pci/direct.o
CC arch/i386/pci/fixup.o
CC arch/i386/pci/legacy.o
CC arch/i386/pci/irq.o
CC arch/i386/pci/common.o
LD arch/i386/pci/built-in.o
CC arch/i386/power/cpu.o
LD arch/i386/power/built-in.o
CC net/socket.o
In file included from net/socket.c:97:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/802/p8023.o
CC net/802/sysctl_net_802.o
LD net/802/built-in.o
CC net/core/sock.o
In file included from include/linux/tcp.h:180,
from net/core/sock.c:112:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/request_sock.o
In file included from include/net/request_sock.h:22,
from net/core/request_sock.c:19:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/skbuff.o
In file included from net/core/skbuff.c:64:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/iovec.o
In file included from net/core/iovec.c:30:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/datagram.o
In file included from net/core/datagram.c:55:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/stream.o
In file included from include/linux/tcp.h:180,
from net/core/stream.c:18:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/scm.o
In file included from net/core/scm.c:32:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/gen_stats.o
CC net/core/gen_estimator.o
In file included from net/core/gen_estimator.c:34:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/sysctl_net_core.o
In file included from net/core/sysctl_net_core.c:13:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/dev.o
In file included from net/core/dev.c:94:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/ethtool.o
CC net/core/dev_mcast.o
In file included from include/net/request_sock.h:22,
from include/linux/ip.h:84,
from include/net/ip.h:28,
from net/core/dev_mcast.c:46:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/dst.o
CC net/core/neighbour.o
In file included from net/core/neighbour.c:32:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/rtnetlink.o
In file included from include/net/request_sock.h:22,
from include/linux/ip.h:84,
from include/net/ip.h:28,
from net/core/rtnetlink.c:45:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/utils.o
CC net/core/link_watch.o
In file included from net/core/link_watch.c:18:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/filter.o
In file included from include/net/request_sock.h:22,
from include/linux/ip.h:84,
from include/net/ip.h:28,
from net/core/filter.c:28:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/core/net-sysfs.o
In file included from net/core/net-sysfs.c:16:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
LD net/core/built-in.o
CC net/ethernet/eth.o
In file included from include/net/request_sock.h:22,
from include/linux/ip.h:84,
from net/ethernet/eth.c:49:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
CC net/ethernet/sysctl_net_ether.o
LD net/ethernet/built-in.o
CC net/ipv4/route.o
In file included from include/linux/mroute.h:129,
from net/ipv4/route.c:89:
include/net/sock.h: In function `sk_dst_get':
include/net/sock.h:972: warning: implicit declaration of function `__raw_read_unlock'
include/net/sock.h: In function `sk_dst_set':
include/net/sock.h:991: warning: implicit declaration of function `__raw_write_unlock'
net/ipv4/route.c: In function `rt_check_expire':
net/ipv4/route.c:663: warning: dereferencing `void *' pointer
net/ipv4/route.c:663: error: request for member `raw_lock' in something not a structure or union
make[2]: *** [net/ipv4/route.o] Error 1
make[1]: *** [net/ipv4] Error 2
make: *** [net] Error 2And the .config:
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.14-rc5-mm1
# Mon Oct 24 18:12:00 2005
#CONFIG_X86_32=yCONFIG_SEMAPHORE_SLEEPERS=yCONFIG_X86=yCONFIG_MMU=yCONFIG_UID16=yCONFIG_GENERIC_ISA_DMA=yCONFIG_GENERIC_IOMAP=yCONFIG_ARCH_MAY_HAVE_PC_FDC=y
#
# Code maturity level options
#CONFIG_EXPERIMENTAL=yCONFIG_CLEAN_COMPILE=yCONFIG_BROKEN_ON_SMP=yCONFIG_INIT_ENV_ARG_LIMIT=32
#
# General setup
#CONFIG_LOCALVERSION="-minerva1"
# CONFIG_LOCALVERSION_AUTO is not setCONFIG_SWAP=yCONFIG_SWAP_PREFETCH=yCONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not setCONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
# CONFIG_HOTPLUG is not setCONFIG_KOBJECT_UEVENT=y
# CONFIG_IKCONFIG is not setCONFIG_INITRAMFS_SOURCE=""CONFIG_EMBEDDED=y
# CONFIG_KALLSYMS is not setCONFIG_PRINTK=yCONFIG_BUG=yCONFIG_BASE_FULL=yCONFIG_FUTEX=yCONFIG_EPOLL=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not setCONFIG_SHMEM=yCONFIG_CC_ALIGN_FUNCTIONS=0CONFIG_CC_ALIGN_LABELS=0CONFIG_CC_ALIGN_LOOPS=0CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not setCONFIG_BASE_SMALL=0
#
# Loadable module support
#CONFIG_MODULES=yCONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not setCONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not setCONFIG_KMOD=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 is not set
# CONFIG_MK6 is not setCONFIG_MK7=y
# 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 is not setCONFIG_X86_CMPXCHG=yCONFIG_X86_XADD=yCONFIG_X86_L1_CACHE_SHIFT=6CONFIG_RWSEM_XCHGADD_ALGORITHM=yCONFIG_GENERIC_CALIBRATE_DELAY=yCONFIG_X86_WP_WORKS_OK=yCONFIG_X86_INVLPG=yCONFIG_X86_BSWAP=yCONFIG_X86_POPAD_OK=yCONFIG_X86_CMPXCHG64=yCONFIG_X86_GOOD_APIC=yCONFIG_X86_INTEL_USERCOPY=yCONFIG_X86_USE_PPRO_CHECKSUM=yCONFIG_X86_USE_3DNOW=yCONFIG_HPET_TIMER=y
# CONFIG_SMP is not setCONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not setCONFIG_X86_UP_APIC=yCONFIG_X86_UP_IOAPIC=yCONFIG_X86_LOCAL_APIC=yCONFIG_X86_IO_APIC=yCONFIG_X86_TSC=yCONFIG_X86_MCE=yCONFIG_X86_MCE_NONFATAL=y
# CONFIG_X86_MCE_P4THERMAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_X86_REBOOTFIXUPS is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not setCONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not setCONFIG_1GLOWMEM=yCONFIG_ARCH_SPARSEMEM_ENABLE=yCONFIG_ARCH_SELECT_MEMORY_MODEL=yCONFIG_SELECT_MEMORY_MODEL=yCONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not setCONFIG_FLATMEM=yCONFIG_FLAT_NODE_MEM_MAP=yCONFIG_SPARSEMEM_STATIC=yCONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_MATH_EMULATION is not setCONFIG_MTRR=y
# CONFIG_REGPARM is not setCONFIG_SECCOMP=yCONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_1000 is not setCONFIG_HZ=100CONFIG_PHYSICAL_START=0x100000
# CONFIG_KEXEC is not set
#
# Power management options (ACPI, APM)
#CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND is not set
#
# ACPI (Advanced Configuration and Power Interface) Support #
# CONFIG_ACPI is not set
#
# APM (Advanced Power Management) BIOS Support
#CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not setCONFIG_APM_CPU_IDLE=y
# CONFIG_APM_DISPLAY_BLANK is not setCONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not setCONFIG_APM_REAL_MODE_POWER_OFF=y
#
# 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 setCONFIG_PCI_GODIRECT=y
# CONFIG_PCI_GOANY is not setCONFIG_PCI_DIRECT=y
# CONFIG_PCIEPORTBUS is not setCONFIG_PCI_MSI=y
# CONFIG_PCI_LEGACY_PROC is not setCONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 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 is not set
# CONFIG_BINFMT_MISC is not set
#
# Networking
#CONFIG_NET=y
#
# Networking options
#CONFIG_PACKET=mCONFIG_PACKET_MMAP=yCONFIG_UNIX=m
# CONFIG_NET_KEY is not setCONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not setCONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not setCONFIG_INET_DIAG=mCONFIG_INET_TCP_DIAG=mCONFIG_TCP_CONG_ADVANCED=y
#
# TCP congestion control
#CONFIG_TCP_CONG_BIC=m
# CONFIG_TCP_CONG_WESTWOOD is not set
# CONFIG_TCP_CONG_HTCP is not set
# CONFIG_TCP_CONG_HSTCP is not set
# CONFIG_TCP_CONG_HYBLA is not set
# CONFIG_TCP_CONG_VEGAS is not set
# CONFIG_TCP_CONG_SCALABLE is not set
# CONFIG_IPV6 is not set
# CONFIG_NETFILTER is not set
#
# DCCP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# 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=yCONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FW_LOADER is not set
#
# Connector - unified userspace <-> kernelspace linker #
# CONFIG_CONNECTOR is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
#
# Block devices
#CONFIG_BLK_DEV_FD=m
# 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 setCONFIG_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_RAM is not setCONFIG_BLK_DEV_RAM_COUNT=16
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_CDROM_PKTCDVD is not set
#
# IO Schedulers
#CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
# CONFIG_IOSCHED_DEADLINE is not setCONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not setCONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not setCONFIG_DEFAULT_IOSCHED="cfq"
# CONFIG_ATA_OVER_ETH is not set
#
# ATA/ATAPI/MFM/RLL support
#CONFIG_IDE=yCONFIG_BLK_DEV_IDE=y
#
# 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=yCONFIG_IDEDISK_MULTI_MODE=yCONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set CONFIG_IDE_TASK_IOCTL=y
#
# IDE chipset support/bugfixes
#
# CONFIG_IDE_GENERIC is not set
# CONFIG_BLK_DEV_CMD640 is not setCONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not setCONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not setCONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not setCONFIG_BLK_DEV_AMD74XX=y
# 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 is not set
# 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 setCONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not setCONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
# CONFIG_SCSI is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION 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=yCONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
#
# PHY device support
#
# CONFIG_PHYLIB is not set
#
# Ethernet (10 or 100Mbit)
#CONFIG_NET_ETHERNET=yCONFIG_MII=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not setCONFIG_NET_VENDOR_3COM=yCONFIG_VORTEX=m
# CONFIG_TYPHOON is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
# CONFIG_NET_PCI 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 is not set
# 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_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_KGDBOE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NETPOLL_RX is not set
# CONFIG_NETPOLL_TRAP is not set
# CONFIG_NET_POLL_CONTROLLER is not set
#
# 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 is not set
# 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=yCONFIG_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 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=yCONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not setCONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#CONFIG_VT=yCONFIG_VT_CONSOLE=yCONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_JSM is not setCONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# 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_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER 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 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 is not set
# CONFIG_VIDEO_SELECT is not set
#
# Console display driver support
#CONFIG_VGA_CONSOLE=yCONFIG_DUMMY_CONSOLE=y
#
# Speakup console speech
#
# CONFIG_SPEAKUP is not set
#
# Sound
#
# CONFIG_SOUND is not set
#
# USB support
#CONFIG_USB_ARCH_HAS_HCD=yCONFIG_USB_ARCH_HAS_OHCI=y
# CONFIG_USB is not set
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk 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
#
# Distributed Lock Manager
#
# CONFIG_DLM is not set
#
# File systems
#CONFIG_EXT2_FS=m
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
# CONFIG_EXT3_FS is not set
# CONFIG_REISER4_FS is not setCONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
# CONFIG_XFS_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_INOTIFY is not set
# CONFIG_QUOTA is not set
# CONFIG_DNOTIFY is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not setCONFIG_FUSE_FS=m
#
# CD-ROM/DVD Filesystems
#CONFIG_ISO9660_FS=mCONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#CONFIG_FAT_FS=m
# CONFIG_MSDOS_FS is not setCONFIG_VFAT_FS=mCONFIG_FAT_DEFAULT_CODEPAGE=437CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#CONFIG_PROC_FS=y
# CONFIG_PROC_KCORE is not setCONFIG_SYSFS=yCONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not setCONFIG_RAMFS=y
# CONFIG_RELAYFS_FS is not set
# CONFIG_CONFIGFS_FS is not set
#
# 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=mCONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not setCONFIG_NFSD=mCONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
# CONFIG_NFSD_V4 is not setCONFIG_NFSD_TCP=yCONFIG_LOCKD=mCONFIG_LOCKD_V4=yCONFIG_EXPORTFS=mCONFIG_NFS_COMMON=yCONFIG_SUNRPC=m
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not setCONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_EXPERIMENTAL 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 setCONFIG_MSDOS_PARTITION=y
#
# Native Language Support
#CONFIG_NLS=mCONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# 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 is not set
# 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 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# 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 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# Instrumentation Support
#
# CONFIG_PROFILING is not set
# CONFIG_KPROBES is not set
#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
# CONFIG_DEBUG_KERNEL is not setCONFIG_LOG_BUF_SHIFT=14
# CONFIG_DEBUG_BUGVERBOSE is not setCONFIG_EARLY_PRINTK=yCONFIG_X86_FIND_SMP_CONFIG=yCONFIG_X86_MPPARSE=y
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Hardware crypto devices
#
#
# Library routines
#
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
# CONFIG_CRC32 is not set
# CONFIG_LIBCRC32C is not setCONFIG_GENERIC_HARDIRQS=yCONFIG_GENERIC_IRQ_PROBE=yCONFIG_X86_BIOS_REBOOT=y
- LL
Quoted 4 lines · Lexington Luthor
Hi,
This release has a number of build errors for me. I used the vanilla 2.6.14-rc5 + 2.6.14-rc5-mm1 patch + CK's 1GB lowmem patch.
you should revert those two patches:
+x86-inline-spin_unlock-if-not-config_debug_spinlock-and-not-config_preempt.patch +x86-inline-spin_unlock_irq-if-not-config_debug_spinlock-and-not-config_preempt.patch
Quoted 11 lines
Here is the make output and the .config listing:
$ make [snip] net/ipv4/route.c: In function `rt_check_expire': net/ipv4/route.c:663: warning: dereferencing `void *' pointer net/ipv4/route.c:663: error: request for member `raw_lock' in something not a structure or union make[2]: *** [net/ipv4/route.o] Error 1 make[1]: *** [net/ipv4] Error 2 make: *** [net] Error 2
regards,
Benoit
Quoted 2 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/
I can't seem to keep my AMD64 machine up with 2.6.14-rc5-mm1. Keep running into following. qlogic driver problem ?
Thanks,
Badari
NMI Watchdog detected LOCKUP on CPU 0
CPU 0
Modules linked in: qlogicfc qla2300 qla2200 qla2xxx firmware_class
ohci_hcd hw_r andom usbcore dm_mod
Pid: 4414, comm: modprobe Not tainted 2.6.14-rc5-mm1 #3
RIP: 0010:[<ffffffff80401d94>] <ffffffff80401d94>{.text.lock.spinlock
+34}
RSP: 0000:ffff81019da91c28 EFLAGS: 00000086
RAX: 0000000000000000 RBX: ffff81017991f288 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000286 RDI: ffff81017991f290
RBP: ffff81019da91c28 R08: 0000000000000034 R09: 0000000000000000
R10: ffff81019da91c08 R11: 0000000000000000 R12: ffff81017991f290
R13: 00000000fffffff4 R14: ffff81017991c000 R15: 0000000000000100
FS: 00002aaaaade36e0(0000) GS:ffffffff80649800(0000)knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000836018 CR3: 00000001bdf2a000 CR4: 00000000000006e0 Process modprobe (pid: 4414, threadinfo ffff81019da90000, task ffff81019e3bb500)
Stack: ffff81019da91cb8 ffffffff80400dec ffff81019da91c78
ffffffff80142ed0
0000000000000000 0000000000000000 0000000000000001
0000000000000001
ffff81017991c000 0000000000000100
Call Trace:<ffffffff80400dec>{wait_for_completion+28}
<ffffffff80142ed0>{group_s end_sig_info+128}
<ffffffff80142f89>{kill_proc_info+73}
<ffffffff8805753c>{:qla2xxx:qla2x00 _free_device+188}
<ffffffff8805880b>{:qla2xxx:qla2x00_probe_one+4187}
<ffffffff80132ce0>{set_cpus_allowed+336}
<ffffffff8012dca3>{__wake_up_com mon+67}
<ffffffff8029741a>{kobject_get+26}
<ffffffff8807c01d>{:qla2200:qla2200_pr obe_one+13}
<ffffffff802a516c>{pci_device_probe+252}
<ffffffff80308d29>{driver_probe_ device+89}
<ffffffff80308da0>{__driver_attach+0}
<ffffffff80308de2>{__driver_attach+ 66}
<ffffffff803086af>{bus_for_each_dev+79}
<ffffffff80308bbc>{driver_attach+ 28}
<ffffffff80308108>{bus_add_driver+136}
<ffffffff80308f0c>{driver_register +76}
<ffffffff802a4ebe>{pci_register_driver+158}
<ffffffff8804d010>{:qla2200:q la2200_init+16}
<ffffffff80154072>{sys_init_module+274}<ffffffff8010dd2e>{system_call+12 6}
Code: 83 3f 00 7e f9 e9 67 fd ff ff e8 71 ac e9 ff e9 82 fd ff ff
console shuts up ...
scsi3 : QLogic ISP2200 SCSI on PCI bus 19 device 08 irq 21 base 0x4000
Quoted 7 lines · Badari Pulavarty
Quoted 2 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/
I can't seem to keep my AMD64 machine up with 2.6.14-rc5-mm1. Keep running into following. qlogic driver problem ?
I don't know why the qlogic driver has suddenly started doing this - were there any earlier messages which might tell us? Is it possible to increase the debugging level?
I can spot one bug in there, but the lockup is just a symptom.
There are no qlogic changes in 2.6.14-rc5-mm1.
Quoted 10 lines
Thanks,
BadariNMI Watchdog detected LOCKUP on CPU 0
CPU 0Modules linked in: qlogicfc qla2300 qla2200 qla2xxx firmware_class ohci_hcd hw_r andom usbcore dm_mod Pid: 4414, comm: modprobe Not tainted 2.6.14-rc5-mm1 #3 RIP: 0010:[<ffffffff80401d94>] <ffffffff80401d94>{.text.lock.spinlock+34}
That's a corrupted spinlock.
Quoted 37 lines
RSP: 0000:ffff81019da91c28 EFLAGS: 00000086 RAX: 0000000000000000 RBX: ffff81017991f288 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000286 RDI: ffff81017991f290 RBP: ffff81019da91c28 R08: 0000000000000034 R09: 0000000000000000 R10: ffff81019da91c08 R11: 0000000000000000 R12: ffff81017991f290 R13: 00000000fffffff4 R14: ffff81017991c000 R15: 0000000000000100 FS: 00002aaaaade36e0(0000) GS:ffffffff80649800(0000)knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0:000000008005003b
CR2: 0000000000836018 CR3:00000001bdf2a000CR4:00000000000006e0Process modprobe (pid: 4414, threadinfoffff81019da90000, taskffff81019e3bb500)Stack: ffff81019da91cb8 ffffffff80400dec ffff81019da91c78 ffffffff80142ed0 0000000000000000 0000000000000000 0000000000000001 0000000000000001 ffff81017991c000 0000000000000100 Call Trace:<ffffffff80400dec>{wait_for_completion+28} <ffffffff80142ed0>{group_s end_sig_info+128} <ffffffff80142f89>{kill_proc_info+73} <ffffffff8805753c>{:qla2xxx:qla2x00 _free_device+188} <ffffffff8805880b>{:qla2xxx:qla2x00_probe_one+4187} <ffffffff80132ce0>{set_cpus_allowed+336} <ffffffff8012dca3>{__wake_up_com mon+67} <ffffffff8029741a>{kobject_get+26} <ffffffff8807c01d>{:qla2200:qla2200_pr obe_one+13} <ffffffff802a516c>{pci_device_probe+252} <ffffffff80308d29>{driver_probe_ device+89} <ffffffff80308da0>{__driver_attach+0} <ffffffff80308de2>{__driver_attach+ 66} <ffffffff803086af>{bus_for_each_dev+79} <ffffffff80308bbc>{driver_attach+ 28} <ffffffff80308108>{bus_add_driver+136} <ffffffff80308f0c>{driver_register +76} <ffffffff802a4ebe>{pci_register_driver+158} <ffffffff8804d010>{:qla2200:q la2200_init+16} <ffffffff80154072>{sys_init_module+274}
Quoted 1 line
<ffffffff8010dd2e>{system_call+12 6}
qla2x00_probe_one() has called qla2x00_free_device() and qla2x00_free_device() has locked up in wait_for_completion(&ha->dpc_exited);
Presumably, ha->dpc_exited is not initialised yet.
The first `goto probe_failed' in qla2x00_probe_one() will cause qla2x00_free_device() to run wait_for_completion() against an uninitialised completion struct. Because ha->dpc_pid will be >= 0.
This patch might fix the lockup, but if so, qla2x00_iospace_config() failed. Please debug that a bit for us?
Andrew, this driver should be converted to use the kthread API - using kill_proc() from within a driver to terminate a kernel thread is kinda gross.
drivers/scsi/qla2xxx/qla_os.c renamed from drivers/scsi/qla2xxx/qla_os.c~qlogic-lockup-fix +2 -1
@@ -1325,6 +1325,8 @@ int qla2x00_probe_one(struct pci_dev *pd ha->brd_info = brd_info;sprintf (ha->host_str,"%s_%ld" , ha->brd_info->drv_name, ha->host_no); + ha->dpc_pid =-1 ; +/* Configure PCI I/O space */ ret =qla2x00_iospace_config (ha);if (ret)
@@ -1448,7 +1450,6 @@ int qla2x00_probe_one(struct pci_dev *pd*/ spin_lock_init (&ha->mbx_reg_lock); - ha->dpc_pid =-1 ;init_completion (&ha->dpc_inited);init_completion (&ha->dpc_exited);
_
On Mon, 2005-10-24 at 14:16 -0700, Andrew Morton wrote:
..
Quoted 5 lines
qla2x00_probe_one()has calledqla2x00_free_device()andqla2x00_free_device()has locked up inwait_for_completion(&ha->dpc_exited);
Quoted 8 lines
Presumably,
ha->dpc_exitedis not initialised yet.The first `goto
probe_failed' inqla2x00_probe_one()will causeqla2x00_free_device()to runwait_for_completion()against an uninitialised completion struct. Becauseha->dpc_pidwill be >= 0.This patch might fix the lockup, but if so,
qla2x00_iospace_config()failed. Please debug that a bit for us?
Yes. This patch helped. Due to power failures, my disk trays are powered off. qla2x00_iospace_config() is failing and causing the panic on -mm kernel. For odd reasons, older -mm kernels & mainline kernels doesn't panic.
Thanks,
Badari
Quoted 14 lines · Badari Pulavarty
On Mon, 2005-10-24 at 14:16 -0700, Andrew Morton wrote:
..Quoted 11 lines
qla2x00_probe_one()has calledqla2x00_free_device()andqla2x00_free_device()has locked up inwait_for_completion(&ha->dpc_exited);Presumably,
ha->dpc_exitedis not initialised yet.The first `goto
probe_failed' inqla2x00_probe_one()will causeqla2x00_free_device()to runwait_for_completion()against an uninitialised completion struct. Becauseha->dpc_pidwill be >= 0.
Quoted 7 lines
Quoted 2 lines
This patch might fix the lockup, but if so,
qla2x00_iospace_config()failed. Please debug that a bit for us?Yes. This patch helped. Due to power failures, my disk trays are powered off.
qla2x00_iospace_config()is failing and causing the panic on -mm kernel. For odd reasons, older -mm kernels & mainline kernels doesn't panic.
OK, thanks. Andrew seems offline and this patch is sufficiently obvious that I think I'll just jam it into 2.6.14...
Quoted 3 lines · Andrew Morton
qla2x00_probe_one()has calledqla2x00_free_device()andqla2x00_free_device()has locked up inwait_for_completion(&ha->dpc_exited);
one more reason to use one-for-one goto-style unwinding instead of calling _free routines ;-)
While we're at it - Andew, would you converting qla2xxx to the kthread_ API for thread handling?
Quoted 9 lines · Andrew Morton
Quoted 7 lines · Badari Pulavarty
Quoted 2 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/
I can't seem to keep my AMD64 machine up with 2.6.14-rc5-mm1. Keep running into following. qlogic driver problem ?
Quoted 14 lines
I don't know why the qlogic driver has suddenly started doing this - were there any earlier messages which might tell us? Is it possible to increase the debugging level?
I can spot one bug in there, but the lockup is just a symptom.
There are no qlogic changes in 2.6.14-rc5-mm1.
Quoted 6 lines
Thanks,
BadariNMI Watchdog detected LOCKUP on CPU 0
CPU 0Modules linked in: qlogicfc qla2300 qla2200 qla2xxx firmware_class
qlogicfc attaches to both 2100 and 2200 ISPs. It seems you're then trying to load qla2xxx driver along with the 2300 and 2200 firmware loader modules. The pci_request_regions() call during 2200 probing fails.
Quoted 8 lines
Quoted 1 line
<ffffffff8010dd2e>{system_call+12 6}
qla2x00_probe_one()has calledqla2x00_free_device()andqla2x00_free_device()has locked up inwait_for_completion(&ha->dpc_exited);Presumably,
ha->dpc_exitedis not initialised yet.
Causing this cleanup badness.
Quoted 6 lines
The first `goto
probe_failed' inqla2x00_probe_one()will causeqla2x00_free_device()to runwait_for_completion()against an uninitialised completion struct. Becauseha->dpc_pidwill be >= 0.This patch might fix the lockup, but if so,
qla2x00_iospace_config()failed. Please debug that a bit for us?
Badari, is there some reason you are using qlogicfc? THe qla2xxx driver supports all QLogic ISP parts.
Quoted 3 lines
Andrew, this driver should be converted to use the kthread API - using
kill_proc()from within a driver to terminate a kernel thread is kinda gross.
I'll look into this as well
Thanks,
Andrew Vasquez
Quoted 27 lines · Andrew Vasquez
Quoted 9 lines · Andrew Morton
Quoted 7 lines · Badari Pulavarty
Quoted 2 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/
I can't seem to keep my AMD64 machine up with 2.6.14-rc5-mm1. Keep running into following. qlogic driver problem ?
Quoted 14 lines
I don't know why the qlogic driver has suddenly started doing this - were there any earlier messages which might tell us? Is it possible to increase the debugging level?
I can spot one bug in there, but the lockup is just a symptom.
There are no qlogic changes in 2.6.14-rc5-mm1.
Quoted 6 lines
Thanks,
BadariNMI Watchdog detected LOCKUP on CPU 0
CPU 0Modules linked in: qlogicfc qla2300 qla2200 qla2xxx firmware_class
Quoted 4 lines
qlogicfc attaches to both 2100 and 2200 ISPs. It seems you're then trying to load qla2xxx driver along with the 2300 and 2200 firmware loader modules. The
pci_request_regions()call during 2200 probing fails.
Hmm. This is happening because I have both qlogicfc and qla2200 as modules ?
Quoted 16 lines
Quoted 9 lines
Quoted 2 lines
<ffffffff8010dd2e>{system_call+12 6}
qla2x00_probe_one()has calledqla2x00_free_device()andqla2x00_free_device()has locked up inwait_for_completion(&ha->dpc_exited);Presumably,
ha->dpc_exitedis not initialised yet.Causing this cleanup badness.
Quoted 4 lines
The first `goto
probe_failed' inqla2x00_probe_one()will causeqla2x00_free_device()to runwait_for_completion()against an uninitialised completion struct. Becauseha->dpc_pidwill be >= 0.
Quoted 5 lines
Quoted 2 lines
This patch might fix the lockup, but if so,
qla2x00_iospace_config()failed. Please debug that a bit for us?Badari, is there some reason you are using qlogicfc? THe qla2xxx driver supports all QLogic ISP parts.
Not intentionally. I have qla2200, qla2300 cards in my machine. I build all the qlogic drivers as modules.
I hate to admit it - but I do use modules for qlogic disks. I can't seem to compile the qlogic drivers (2200, 2300) into the kernel and boot without problems (consistently on all my machines
- I run into few issues):
(1) Between kernels, sometimes probing order changes and my local disks get probed last and screws up my boot process - I don't think this is a qlogic problem.
(2) Sometimes, one of the driver complains something like "PCI region already in use" and hangs on boot.
BTW, (2) happens even if its modules and I can't boot my machine. Sometimes I had to boot with old kernel and hide the modules - so boot process can't find them to workaround the problem.
Is there a "dont-load-modules" option or don't load a specific module option on boot ?
Thanks,
Badari
Quoted 8 lines · Badari Pulavarty
Quoted 4 lines · Andrew Vasquez
qlogicfc attaches to both 2100 and 2200 ISPs. It seems you're then trying to load qla2xxx driver along with the 2300 and 2200 firmware loader modules. The
pci_request_regions()call during 2200 probing fails.Hmm. This is happening because I have both qlogicfc and qla2200 as modules ?
Yes. You don't need (unless there is a compeling reason) to compile qlogicfc (CONFIG_SCSI_QLOGIC_FC) as the qla2xxx driver along with the 2200 and 2300 firmware mofules:
CONFIG_SCSI_QLA2XXX=m CONFIG_SCSI_QLA22XX=m CONFIG_SCSI_QLA2300=m
will be fine.
Quoted 5 lines
Quoted 2 lines
Badari, is there some reason you are using qlogicfc? THe qla2xxx driver supports all QLogic ISP parts.
Not intentionally. I have qla2200, qla2300 cards in my machine. I build all the qlogic drivers as modules.
Could you send me your .config file? I have a fealing you have and entry similar to the following:
CONFIG_SCSI_QLOGIC_FC=m
in there. Don't compile the qlogicfc driver.
Quoted 1 line
I hate to admit it - but I do use modules for qlogic disks.
Thats fine.
Quoted 7 lines
I can't seem to compile the qlogic drivers (2200, 2300) into the kernel and boot without problems (consistently on all my machines
- I run into few issues):(1) Between kernels, sometimes probing order changes and my local disks get probed last and screws up my boot process - I don't think this is a qlogic problem.
Not sure there, but the removal of the qlogicfc driver could help clear up some of the noise, like...
Quoted 2 lines
(2) Sometimes, one of the driver complains something like "PCI region already in use" and hangs on boot.
this. the qlogicfc driver is being loaded before qla2xxx and the supporting 2200 firmware module.
Quoted 7 lines
BTW, (2) happens even if its modules and I can't boot my machine. Sometimes I had to boot with old kernel and hide the modules - so boot process can't find them to workaround the problem.
Is there a "dont-load-modules" option or don't load a specific module option on boot ?
--
Andrew Vasquez
Quoted 4 lines · Andrew Vasquez
qlogicfc attaches to both 2100 and 2200 ISPs. It seems you're then trying to load qla2xxx driver along with the 2300 and 2200 firmware loader modules. The
pci_request_regions()call during 2200 probing fails.
Btw, now that devfs is gone and thus DaveM's host renumbering issues are modd we'd like to kill qlogicfc. I vaguely remember people complaing qla2xxx made trouble on qla2100 hardware. Andrew do you have any success or error reports for that hardware?
Quoted 10 lines · Christoph Hellwig
Quoted 4 lines · Andrew Vasquez
qlogicfc attaches to both 2100 and 2200 ISPs. It seems you're then trying to load qla2xxx driver along with the 2300 and 2200 firmware loader modules. The
pci_request_regions()call during 2200 probing fails.Btw, now that devfs is gone and thus DaveM's host renumbering issues are modd we'd like to kill qlogicfc. I vaguely remember people complaing qla2xxx made trouble on qla2100 hardware. Andrew do you have any success or error reports for that hardware?
A couple of months ago I had worked with a 2100 user who was having some serious problems within a configuration. I was able to reproduce something similar in-house and (to make a long-story, short), it turns out there are some error-recovery problems in the firmware version currently shipping in qla2xxx (1.19.25 TP firmware to be exact).
After numerous trial and error efforts, we were able to find a reasonbly stable release with which the customer's configuration could recover and run (1.17.38 EF, quite old).
In any case, formally, QLogic has dropped *all* support for ISP2100 cards, and thus, it's quite difficult to get any type of traction from the firmware folk to begin to root-cause the failures.
I'm still in the process of ironing out the .bin distribution details locally, but perhaps once we migrate to firmware-loading exclusively via request_firmware(), the (small?) contigent of 2100 could use the EF variant I referenced above.
Could I get another informal count of 2100 users who are still having problems with qla2xxx?
Regards,
Andrew Vasquez
HEADS UP for QLA2100 users
Quoted 7 lines · Andrew Vasquez
After numerous trial and error efforts, we were able to find a reasonbly stable release with which the customer's configuration could recover and run (1.17.38 EF, quite old).
In any case, formally, QLogic has dropped *all* support for ISP2100 cards, and thus, it's quite difficult to get any type of traction from the firmware folk to begin to root-cause the failures.
Sure. We're all very happy that you invest time to help these users anyway, and will allow us to get rid of one more unmaintained driver.
Quoted 4 lines
I'm still in the process of ironing out the .bin distribution details locally, but perhaps once we migrate to firmware-loading exclusively via
request_firmware(), the (small?) contigent of 2100 could use the EF variant I referenced above.
You know, I'm in favour of getting firmware images in the kernel image, but what's the problem of simply downgrading the 2100 firmware until we get rid of the builtin firmware for all qla2xxx variants?
Quoted 2 lines
Could I get another informal count of 2100 users who are still having problems with qla2xxx?
Re: HEADS UP for QLA2100 users
Quoted 10 lines · Christoph Hellwig
Quoted 4 lines · Andrew Vasquez
I'm still in the process of ironing out the .bin distribution details locally, but perhaps once we migrate to firmware-loading exclusively via
request_firmware(), the (small?) contigent of 2100 could use the EF variant I referenced above.You know, I'm in favour of getting firmware images in the kernel image, but what's the problem of simply downgrading the 2100 firmware until we get rid of the builtin firmware for all qla2xxx variants?
I have no problems with submitting 1.17.38 EF for inclusion upstream. My only hope is that for the (other) 2100 user out there that use the latest 2100 firmware and are not experiencing problems, the downgrade does not break anything.
That's another reason I posed the following question:
Quoted 2 lines
Quoted 2 lines
Could I get another informal count of 2100 users who are still having problems with qla2xxx?
Perhaps I should also ask:
Who's running 2100 cards with the latest qla2xxx driver and are experiencing no problems?
--
AV
Re: HEADS UP for QLA2100 users
Quoted 20 lines · Andrew Vasquez
Quoted 10 lines · Christoph Hellwig
Quoted 4 lines · Andrew Vasquez
I'm still in the process of ironing out the .bin distribution details locally, but perhaps once we migrate to firmware-loading exclusively via
request_firmware(), the (small?) contigent of 2100 could use the EF variant I referenced above.You know, I'm in favour of getting firmware images in the kernel image, but what's the problem of simply downgrading the 2100 firmware until we get rid of the builtin firmware for all qla2xxx variants?
I have no problems with submitting 1.17.38 EF for inclusion upstream. My only hope is that for the (other) 2100 user out there that use the latest 2100 firmware and are not experiencing problems, the downgrade does not break anything.
That's another reason I posed the following question:
Quoted 7 lines
Quoted 2 lines
Quoted 2 lines
Could I get another informal count of 2100 users who are still having problems with qla2xxx?
Perhaps I should also ask:
Who's running 2100 cards with the latest qla2xxx driver and are experiencing no problems?
Hmm.. I thought qla2xxx driver doesn't like qla2100. I had troubles getting my qla2100 cards to work with qal2xxx (9 months ago) and gave up and using only qla2200 and qla2300 card.
Is there a point in me going back and trying qla2100 ? (Ofcourse, I need to locate those cards).
Thanks,
Badari
Re: HEADS UP for QLA2100 users
Quoted 29 lines · Badari Pulavarty
Quoted 20 lines · Andrew Vasquez
Quoted 10 lines · Christoph Hellwig
Quoted 4 lines · Andrew Vasquez
I'm still in the process of ironing out the .bin distribution details locally, but perhaps once we migrate to firmware-loading exclusively via
request_firmware(), the (small?) contigent of 2100 could use the EF variant I referenced above.You know, I'm in favour of getting firmware images in the kernel image, but what's the problem of simply downgrading the 2100 firmware until we get rid of the builtin firmware for all qla2xxx variants?
I have no problems with submitting 1.17.38 EF for inclusion upstream. My only hope is that for the (other) 2100 user out there that use the latest 2100 firmware and are not experiencing problems, the downgrade does not break anything.
That's another reason I posed the following question:
Quoted 7 lines
Quoted 2 lines
Quoted 2 lines
Could I get another informal count of 2100 users who are still having problems with qla2xxx?
Perhaps I should also ask:
Who's running 2100 cards with the latest qla2xxx driver and are experiencing no problems?
Quoted 6 lines
Hmm.. I thought qla2xxx driver doesn't like qla2100. I had troubles getting my qla2100 cards to work with qal2xxx (9 months ago) and gave up and using only qla2200 and qla2300 card.
Is there a point in me going back and trying qla2100 ? (Ofcourse, I need to locate those cards).
Now that in 2.6.16-rc the recommended method for firmware loading in qla2xxx is to load it from userspace, the firmware version problems should have become non-issues.
If ypu have hardware that works in 2.6.16-rc2 with the qlogicfc driver but not with the qal2xxx driver, a bug report would be appreciated.
Quoted 2 lines
Thanks,
Badari
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedPATCH 1/1 schedule the SCSI qlogicfc driver for removal
As usual, there isn't much feedback regarding problems with one driver from people using an obsolete driver for the same hardware.
So schedule the SCSI qlogicfc driver for removal and let the flames^Wfeedback begin...
---
Documentation/feature-removal-schedule.txt | 7 +++++++ drivers/scsi/qlogicfc.c | 1 + 2 files changed, 8 insertions(+)
Documentation/feature-removal-schedule.txt renamed from Documentation/feature-removal-schedule.txt.old +7 -0
@@ -153,0 +154,7 @@ +What: SCSI qlogicfc driver +When: August 2006 +Why: replaced by the qla2xxx driver +Who: Adrian Bunk <[email protected]> + +--------------------------- +
drivers/scsi/qlogicfc.c renamed from drivers/scsi/qlogicfc.c.old +1 -0
@@ -724,6 +724,7 @@dma_addr_t busaddr;int i; +printk (KERN_WARNING "qlogicfc will be removed soon, please use the qla2xxx driver\n" );ENTER ("isp2x00_detect" );
Re: [2.6 patch] schedule the SCSI qlogicfc driver for removal
Quoted 5 lines · Adrian Bunk
As usual, there isn't much feedback regarding problems with one driver from people using an obsolete driver for the same hardware.
So schedule the SCSI qlogicfc driver for removal and let the flames^Wfeedback begin...
The driver has been deprecatedd since long before the official deprecation mechanisms existed. It'll go away for 2.6.17.
Re: [2.6 patch] schedule the SCSI qlogicfc driver for removal
Quoted 9 lines · Christoph Hellwig
Quoted 5 lines · Adrian Bunk
As usual, there isn't much feedback regarding problems with one driver from people using an obsolete driver for the same hardware.
So schedule the SCSI qlogicfc driver for removal and let the flames^Wfeedback begin...
The driver has been deprecatedd since long before the official deprecation mechanisms existed. It'll go away for 2.6.17.
Is this patch pending somewhere or should I send a patch?
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seedintel-agp and yenta-socket issues (was Re: 2.6.14-rc5-mm1
In reply to Andrew MortonQuoted 4 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/
+agp-updates-owner-field-of-struct-pci_driver.patch
intel-agp would hang during modprobe until I backed this one out.
Am still seeing a hang trying to modprobe yenta-socket during early boot. I'm not seeing any obvious candidates to back out here - the -rc4-mm1 version is identical, and -rc4-mm1 boots OK for me.
I wasn't seeing any output from alt-sysrq-T, but it occurs to me that maybe the console level wasn't set nicely yet - this is happening pretty early in rc.sysinit.
Is there an undocumented requirement for a newer modprobe? I'm currently using the Fedora -devel tree's version:
# modprobe -V module-init-tools version 3.2-pre7
Re: intel-agp and yenta-socket issues (was Re: 2.6.14-rc5-mm1
Quoted 8 lines · [email protected] wrote:
Quoted 4 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/
+agp-updates-owner-field-of-struct-pci_driver.patch
intel-agp would hang during modprobe until I backed this one out.
A sysrq trace would be nice.
Quoted 7 lines
Am still seeing a hang trying to modprobe yenta-socket during early boot. I'm not seeing any obvious candidates to back out here - the -rc4-mm1 version is identical, and -rc4-mm1 boots OK for me.
I wasn't seeing any output from alt-sysrq-T, but it occurs to me that maybe the console level wasn't set nicely yet - this is happening pretty early in rc.sysinit.
Can you wait until the system is fully booted, get sysrq working then modprobe the module by hand?
Quoted 1 line
Is there an undocumented requirement for a newer modprobe?
I hope not. I'm using some ancient thing - it works OK.
Re: intel-agp and yenta-socket issues (was Re: 2.6.14-rc5-mm1
Quoted 3 lines · Andrew Morton
Quoted 1 line
intel-agp would hang during modprobe until I backed this one out.
A sysrq trace would be nice.
Did some further testing, this time passing a loglevel= so I'd see the output, and sysrq-T showed that both modprobe issues were due to an even earlier modprobe that went south. Looking like a bad merge of a local patch caused some locking to get corrupted (always a bad sign when atomic_dec_and_test throws an "atomic counter underflow" message on a refcount). It's now unclear why backing out the agp-updates patch allowed modprobe to succeed - it *shouldn't* have made a difference. Oddness.
2.6.14-rc5-mm1 crypto issues (was Re: intel-agp and yenta-socket issues (was Re: 2.6.14-rc5-mm1
I finally tracked down the root cause of the hangs - I had applied the modsign patches from the Fedora kernel, and hit several bugs.
1) The hangs in modprobe were caused by a bug in RedHat code (a function returned a bum pointer instead of NULL, and things went pear-shaped). I've reported this as bug 171835 in RedHat's bugzilla system. Redhat problem, not yours or lkml's.
2) It turns out that the issue in 171835 only bites if other things have already gone bad. It turns out that a patch in -rc5-mm1 causes the indigestion.
clean-crypto-sha1c-up-a-bit.patch gives the modsign patches indigestion. I'm not sure why yet, or who's code is busticated. All I've verified for sure is that modsign allocates a 20-byte buffer, and with the cleanup patch applied, I'm seeing different values in buffer[12..19].
It's 4AM, and I'm not going to chase this any further until evening. *yawn* ;)
Quoted 1 line · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/
After upgrading to 2.6.14-rc5-mm1 I have been greeted with:
PCI-Bridge- Detected Parity Error on 0000:00:08.0 0000:00:08.0
Which is:
0000:00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 00009000-0000afff
Memory behind bridge: e2000000-e5ffffff
Prefetchable memory behind bridge: e6000000-e6ffffff
BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-... I probably get a new one every minute or so. Is this new, perhaps part of the new EDAC stuff? And what kind of adverse effect does this have on my computer (the actual parity error)?
Thanks,
avuton
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
Quoted 10 lines · Avuton Olrich
Quoted 1 line · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc5/2.6.14-rc5-mm1/
After upgrading to 2.6.14-rc5-mm1 I have been greeted with:
PCI-Bridge- Detected Parity Error on 0000:00:08.0 0000:00:08.0
... I probably get a new one every minute or so. Is this new, perhaps part of the new EDAC stuff? And what kind of adverse effect does this have on my computer (the actual parity error)?
If the parity error is real then it would indicate a bad PCI transfer has occurred and data corrupted in the transfer. Unfortunately because some vendors don't use PCI parity checking much and some card vendors don't debug their products except on that OS there are some cards that generate spurious parity errors.
Can you send an lspci -vxx. That'll help the EDAC folk build up a view of what needs to be blacklisted.
Alan
Quoted 8 lines · Alan Cox
Quoted 6 lines · Avuton Olrich
After upgrading to 2.6.14-rc5-mm1 I have been greeted with:
PCI-Bridge- Detected Parity Error on 0000:00:08.0 0000:00:08.0... I probably get a new one every minute or so. Is this new, perhaps part of the new EDAC stuff? And what kind of adverse effect does this have on my computer (the actual parity error)?
Quoted 8 lines
If the parity error is real then it would indicate a bad PCI transfer has occurred and data corrupted in the transfer. Unfortunately because some vendors don't use PCI parity checking much and some card vendors don't debug their products except on that OS there are some cards that generate spurious parity errors.
Can you send an lspci -vxx. That'll help the EDAC folk build up a view of what needs to be blacklisted.
Thanks for the answer, here's the lspci -vxx:
0000:00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev a2)
Subsystem: ASUSTeK Computer Inc.: Unknown device 80ac
Flags: bus master, 66Mhz, fast devsel, latency 0 Memory at e0000000 (32-bit, prefetchable) [size=32M]
Capabilities: [40] AGP version 2.0
Capabilities: [60] #08 [2001]
00: de 10 e0 01 06 00 b0 00 a2 00 00 06 00 00 80 00
10: 08 00 00 e0 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 ac 80
30: 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00
0000:00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev a2)
Subsystem: ASUSTeK Computer Inc.: Unknown device 80ac
Flags: 66Mhz, fast devsel
00: de 10 eb 01 00 00 20 00 a2 00 00 05 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 ac 80
30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00
0000:00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev a2)
Subsystem: ASUSTeK Computer Inc.: Unknown device 80ac
Flags: 66Mhz, fast devsel
00: de 10 ee 01 00 00 20 00 a2 00 00 05 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 ac 80
30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00
0000:00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev a2)
Subsystem: ASUSTeK Computer Inc.: Unknown device 80ac
Flags: 66Mhz, fast devsel
00: de 10 ed 01 00 00 20 00 a2 00 00 05 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 ac 80
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000:00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev a2)
Subsystem: ASUSTeK Computer Inc.: Unknown device 80ac
Flags: 66Mhz, fast devsel
00: de 10 ec 01 00 00 20 00 a2 00 00 05 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 ac 80
30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00
0000:00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev a2)
Subsystem: ASUSTeK Computer Inc.: Unknown device 80ac
Flags: 66Mhz, fast devsel
00: de 10 ef 01 00 00 20 00 a2 00 00 05 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 ac 80
30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 00 00 00
0000:00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a3)
Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
Flags: bus master, 66Mhz, fast devsel, latency 0
Capabilities: [48] #08 [01e1]
00: de 10 60 00 0f 00 b0 00 a3 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 ad 80
30: 00 00 00 00 48 00 00 00 00 00 00 00 00 00 00 00
0000:00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
Subsystem: ASUSTeK Computer Inc.: Unknown device 0c11
Flags: 66Mhz, fast devsel, IRQ 5
I/O ports at c800 [size=32]
Capabilities: [44] Power Management version 2
00: de 10 64 00 01 00 b0 00 a2 00 05 0c 00 00 80 00
10: 01 c8 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 11 0c
30: 00 00 00 00 44 00 00 00 00 00 00 00 05 01 03 01
0000:00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 17 Memory at e9080000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
00: de 10 67 00 07 00 b0 00 a3 10 03 0c 00 00 80 00
10: 00 00 08 e9 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 11 0c
30: 00 00 00 00 44 00 00 00 00 00 00 00 0a 01 03 01
0000:00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 18 Memory at e9082000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
00: de 10 67 00 07 00 b0 00 a3 10 03 0c 00 00 80 00
10: 00 20 08 e9 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 11 0c
30: 00 00 00 00 44 00 00 00 00 00 00 00 0c 02 03 01
0000:00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 16 Memory at e9083000 (32-bit, non-prefetchable) [size=256]
Capabilities: [44] #0a [2080]
Capabilities: [80] Power Management version 2
00: de 10 68 00 06 00 b0 00 a3 20 03 0c 00 00 80 00
10: 00 30 08 e9 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 11 0c
30: 00 00 00 00 44 00 00 00 00 00 00 00 0a 03 03 01
0000:00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard onboard nForce2 Ethernet
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 17 Memory at e9084000 (32-bit, non-prefetchable) [size=4K]
I/O ports at cc00 [size=8]
Capabilities: [44] Power Management version 2
00: de 10 66 00 07 00 b0 00 a1 00 00 02 00 00 00 00
10: 00 40 08 e9 01 cc 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 a7 80
30: 00 00 00 00 44 00 00 00 00 00 00 00 05 01 01 14
0000:00:05.0 Multimedia audio controller: nVidia Corporation nForce Audio Processing Unit (rev a2)
Subsystem: ASUSTeK Computer Inc.: Unknown device 0c11
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 3 Memory at e9000000 (32-bit, non-prefetchable) [size=512K]
Capabilities: [44] Power Management version 2
00: de 10 6b 00 06 00 b0 00 a2 00 01 04 00 00 00 00
10: 00 00 00 e9 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 11 0c
30: 00 00 00 00 44 00 00 00 00 00 00 00 03 01 01 0c
0000:00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1)
Subsystem: ASUSTeK Computer Inc.: Unknown device 8095 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 11 I/O ports at c000 [size=256] I/O ports at c400 [size=128] Memory at e9081000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2
00: de 10 6a 00 07 00 b0 00 a1 00 01 04 00 00 00 00 10: 01 c0 00 00 01 c4 00 00 00 10 08 e9 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 95 80 30: 00 00 00 00 44 00 00 00 00 00 00 00 0b 01 02 05
0000:00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3) (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: 00009000-0000afff Memory behind bridge: e2000000-e5ffffff Prefetchable memory behind bridge: e6000000-e6ffffff
00: de 10 6c 00 07 01 a0 00 a3 00 04 06 00 00 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 20 90 a0 80 a2 20: 00 e2 f0 e5 00 e6 f0 e6 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0a 06
0000:00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2) (prog-if 8a [Master SecP PriP])
Subsystem: ASUSTeK Computer Inc.: Unknown device 0c11
Flags: bus master, 66Mhz, fast devsel, latency 0 I/O ports at f000 [size=16]
Capabilities: [44] Power Management version 2
00: de 10 65 00 05 00 b0 00 a2 8a 01 01 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 f0 00 00 00 00 00 00 00 00 00 00 43 10 11 0c
30: 00 00 00 00 44 00 00 00 00 00 00 00 00 00 03 01
0000:00:0c.0 PCI bridge: nVidia Corporation nForce2 PCI Bridge (rev a3) (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=32 I/O behind bridge: 0000b000-0000bfff Memory behind bridge: e7000000-e8ffffff Prefetchable memory behind bridge: 30000000-300fffff
00: de 10 6d 00 07 01 a0 00 a3 00 04 06 00 00 01 00 10: 00 00 00 00 00 00 00 00 00 02 02 20 b0 b0 80 02 20: 00 e7 f0 e8 00 30 00 30 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00
0000:00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev a2) (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 32 Bus: primary=00, secondary=03, subordinate=03, sec-latency=32
00: de 10 e8 01 07 01 20 02 a2 00 04 06 00 20 01 00 10: 00 00 00 00 00 00 00 00 00 03 03 20 f0 00 20 22 20: f0 ff 00 00 f0 ff 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00
0000:01:07.0 VGA compatible controller: Matrox Graphics, Inc. MGA 1064SG [Mystique] (rev 03) (prog-if 00 [VGA])
Subsystem: Matrox Graphics, Inc.: Unknown device 0000 Flags: bus master, stepping, medium devsel, latency 32, IRQ 7 Memory at e6000000 (32-bit, prefetchable) [size=8M] Memory at e2000000 (32-bit, non-prefetchable) [size=16K] Memory at e3000000 (32-bit, non-prefetchable) [size=8M] Expansion ROM at e68a0000 [disabled] [size=64K]
00: 2b 10 1a 05 87 00 80 02 03 00 00 03 00 20 00 00 10: 08 00 00 e6 00 00 00 e2 00 00 00 e3 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 2b 10 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 07 01 00 00
0000:01:09.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
Subsystem: Creative Labs SB Audigy 2 ZS (SB0350)
Flags: bus master, medium devsel, latency 32, IRQ 21 I/O ports at 9000 [size=64]
Capabilities: [dc] Power Management version 2
00: 02 11 04 00 05 00 90 02 04 00 01 04 00 20 80 00
10: 01 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 02 11 02 20
30: 00 00 00 00 dc 00 00 00 00 00 00 00 04 01 02 14
0000:01:09.1 Input device controller: Creative Labs SB Audigy MIDI/Game port (rev 04)
Subsystem: Creative Labs SB Audigy MIDI/Game Port
Flags: bus master, medium devsel, latency 32 I/O ports at 9400 [size=8]
Capabilities: [dc] Power Management version 2
00: 02 11 03 70 05 00 90 02 04 00 80 09 00 20 80 00 10: 01 94 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 02 11 40 00 30: 00 00 00 00 dc 00 00 00 00 00 00 00 00 00 00 00
0000:01:09.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04) (prog-if 10 [OHCI])
Subsystem: Creative Labs SB Audigy FireWire Port
Flags: bus master, medium devsel, latency 32, IRQ 11 Memory at e5004000 (32-bit, non-prefetchable) [size=2K] Memory at e5000000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] Power Management version 2
00: 02 11 01 40 06 00 10 02 04 10 00 0c 08 20 80 00
10: 00 40 00 e5 00 00 00 e5 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 02 11 10 00
30: 00 00 00 00 44 00 00 00 00 00 00 00 0b 02 02 04
0000:01:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 19 I/O ports at 9800 [size=256] Memory at e5005000 (32-bit, non-prefetchable) [size=256] Expansion ROM at e6880000 [disabled] [size=128K] Capabilities: [dc] Power Management version 2
00: ec 10 69 81 17 00 b0 02 10 00 00 02 10 20 00 00 10: 01 98 00 00 00 50 00 e5 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 ec 10 69 81 30: 00 00 00 00 dc 00 00 00 00 00 00 00 0c 01 20 40
0000:01:0b.0 RAID bus controller: Silicon Image, Inc. SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev 01)
Subsystem: Silicon Image, Inc. SiI 3112 SATARaid Controller Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 20 I/O ports at 9c00 [size=8] I/O ports at a000 [size=4] I/O ports at a400 [size=8] I/O ports at a800 [size=4] I/O ports at ac00 [size=16] Memory at e5006000 (32-bit, non-prefetchable) [size=512] Expansion ROM at e6800000 [disabled] [size=512K] Capabilities: [60] Power Management version 2
00: 95 10 12 31 07 00 b0 02 01 00 04 01 08 20 00 00 10: 01 9c 00 00 01 a0 00 00 01 a4 00 00 01 a8 00 00 20: 01 ac 00 00 00 60 00 e5 00 00 00 00 95 10 12 61 30: 00 00 00 00 60 00 00 00 00 00 00 00 0b 01 00 00
0000:02:01.0 Ethernet controller: 3Com Corporation 3C920B-EMB Integrated Fast Ethernet Controller [Tornado] (rev 40)
Subsystem: ASUSTeK Computer Inc. A7N8X Deluxe onboard 3C920B-EMB
Integrated Fast Ethernet Controller
Flags: bus master, medium devsel, latency 32, IRQ 16 I/O ports at b000 [size=128] Memory at e8000000 (32-bit, non-prefetchable) [size=128] Expansion ROM at 30000000 [disabled] [size=128K] Capabilities: [dc] Power Management version 2
00: b7 10 01 92 07 00 10 02 40 00 00 02 08 20 00 00 10: 01 b0 00 00 00 00 00 e8 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 ab 80 30: 00 00 00 00 dc 00 00 00 00 00 00 00 0a 01 0a 0a
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
EDAC (was: Re: 2.6.14-rc5-mm1)
In reply to Alan CoxAlan Cox wrote (ao):
Quoted 9 lines · Avuton Olrich
Quoted 7 lines
After upgrading to 2.6.14-rc5-mm1 I have been greeted with:
PCI-Bridge- Detected Parity Error on 0000:00:08.0 0000:00:08.0
... I probably get a new one every minute or so. Is this new, perhaps part of the new EDAC stuff? And what kind of adverse effect does this have on my computer (the actual parity error)?
Quoted 8 lines
If the parity error is real then it would indicate a bad PCI transfer has occurred and data corrupted in the transfer. Unfortunately because some vendors don't use PCI parity checking much and some card vendors don't debug their products except on that OS there are some cards that generate spurious parity errors.
Can you send an lspci -vxx. That'll help the EDAC folk build up a view of what needs to be blacklisted.
Stupid question: should EDAC work on a Via Epia board? Because I see the "Detected Parity Error" messages too (and a lot of them), but figured that the option is just 'not an option' :-)
If it should work I'll be happy to send the error and lspci if that helps.
Signature · 2 lines
Humilis IT Services and Solutions http://www.humilis.net
Re: EDAC (was: Re: 2.6.14-rc5-mm1)
Quoted 3 lines · Sander
Stupid question: should EDAC work on a Via Epia board? Because I see the "Detected Parity Error" messages too (and a lot of them), but figured that the option is just 'not an option' :-)
The PCI parity check should work on every correctly built PCI card and bridge.
Quoted 2 lines
If it should work I'll be happy to send the error and lspci if that helps.
Please do. I'm trying to find the common items that cause spurious pci errors
Re: EDAC (was: Re: 2.6.14-rc5-mm1)
Alan Cox wrote (ao):
Quoted 5 lines · Sander
Quoted 3 lines
Stupid question: should EDAC work on a Via Epia board? Because I see the "Detected Parity Error" messages too (and a lot of them), but figured that the option is just 'not an option' :-)
Quoted 8 lines
The PCI parity check should work on every correctly built PCI card and bridge.
Quoted 2 lines
If it should work I'll be happy to send the error and lspci if that helps.
Please do. I'm trying to find the common items that cause spurious pci errors
Via Epia MII 10000, kernel 2.6.14-rc4-mm1:
$ grep EDAC .config # EDAC - error detection and reporting (RAS) CONFIG_EDAC=y # CONFIG_EDAC_DEBUG is not set CONFIG_EDAC_MM_EDAC=y # CONFIG_EDAC_AMD76X is not set # CONFIG_EDAC_E7XXX is not set # CONFIG_EDAC_E752X is not set # CONFIG_EDAC_I82875P is not set # CONFIG_EDAC_I82860 is not set # CONFIG_EDAC_R82600 is not set CONFIG_EDAC_POLL=y
[42949380.590000] Freeing unused kernel memory: 168k freed [42949381.350000] PCI- Detected Parity Error on 0000:00:01.0 0000:00:01.0 [42949382.350000] PCI- Detected Parity Error on 0000:00:01.0 0000:00:01.0 [42949383.350000] PCI- Detected Parity Error on 0000:00:01.0 0000:00:01.0 [42949384.350000] PCI- Detected Parity Error on 0000:00:01.0 0000:00:01.0
etc
lspci -vxx:
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8623 [Apollo CLE266]
Subsystem: VIA Technologies, Inc.: Unknown device aa01
Flags: bus master, 66MHz, medium devsel, latency 8 Memory at e7000000 (32-bit, prefetchable) [size=4M]
Capabilities: [a0] AGP version 2.0
Capabilities: [c0] Power Management version 2
00: 06 11 23 31 06 00 30 22 00 00 00 06 00 08 00 00
10: 08 00 00 e7 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 01 aa
30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: e4000000-e5ffffff
Prefetchable memory behind bridge: e0000000-e3ffffff
Capabilities: [80] Power Management version 2
00: 06 11 91 b0 07 01 30 a2 00 00 04 06 00 00 01 00
10: 00 00 00 00 00 00 00 00 00 01 01 00 f0 00 20 a2
20: 00 e4 f0 e5 00 e0 f0 e3 00 00 00 00 00 00 00 00
30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 0c 00
0000:00:0a.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 80)
Subsystem: VIA Technologies, Inc.: Unknown device aa01 Flags: bus master, medium devsel, latency 32, IRQ 5 Memory at e742b000 (32-bit, non-prefetchable) [size=4K] Bus: primary=00, secondary=02, subordinate=05, sec-latency=176 Memory window 0: 40000000-41fff000 (prefetchable) Memory window 1: 42000000-43fff000 (prefetchable) I/O window 0: 00001000-00001fff I/O window 1: 00002000-00002fff 16-bit legacy interface ports at 0001
00: 80 11 76 04 07 00 10 02 80 00 07 06 00 20 82 00 10: 00 b0 42 e7 dc 00 00 02 00 02 05 b0 00 00 00 40 20: 00 f0 ff 41 00 00 00 42 00 f0 ff 43 00 10 00 00 30: fc 1f 00 00 00 20 00 00 fc 2f 00 00 05 01 80 07 40: 06 11 01 aa 01 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000:00:0a.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 80)
Subsystem: VIA Technologies, Inc.: Unknown device aa01 Flags: bus master, medium devsel, latency 32, IRQ 12 Memory at e7423000 (32-bit, non-prefetchable) [size=4K] Bus: primary=00, secondary=06, subordinate=09, sec-latency=176 Memory window 0: 44000000-45fff000 (prefetchable) Memory window 1: 46000000-47fff000 (prefetchable) I/O window 0: 00003000-00003fff I/O window 1: 00004000-00004fff 16-bit legacy interface ports at 0001
00: 80 11 76 04 07 00 10 02 80 00 07 06 00 20 82 00 10: 00 30 42 e7 dc 00 00 02 00 06 09 b0 00 00 00 44 20: 00 f0 ff 45 00 00 00 46 00 f0 ff 47 00 30 00 00 30: fc 3f 00 00 00 40 00 00 fc 4f 00 00 0c 02 80 07 40: 06 11 01 aa 01 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc.: Unknown device aa01
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at c000 [size=32]
Capabilities: [80] Power Management version 2
00: 06 11 38 30 07 00 10 02 80 00 03 0c 08 20 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 c0 00 00 00 00 00 00 00 00 00 00 06 11 01 aa
30: 00 00 00 00 80 00 00 00 00 00 00 00 05 01 00 00
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc.: Unknown device aa01
Flags: bus master, medium devsel, latency 32, IRQ 12
I/O ports at c400 [size=32]
Capabilities: [80] Power Management version 2
00: 06 11 38 30 07 00 10 02 80 00 03 0c 08 20 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 c4 00 00 00 00 00 00 00 00 00 00 06 11 01 aa
30: 00 00 00 00 80 00 00 00 00 00 00 00 0c 02 00 00
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc.: Unknown device aa01
Flags: bus master, medium devsel, latency 32, IRQ 7
I/O ports at c800 [size=32]
Capabilities: [80] Power Management version 2
00: 06 11 38 30 07 00 10 02 80 00 03 0c 08 20 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 c8 00 00 00 00 00 00 00 00 00 00 06 11 01 aa
30: 00 00 00 00 80 00 00 00 00 00 00 00 07 03 00 00
0000:00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI])
Subsystem: VIA Technologies, Inc. USB 2.0
Flags: bus master, medium devsel, latency 32, IRQ 9
Memory at e7428000 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2
00: 06 11 04 31 07 00 10 02 82 20 03 0c 08 20 00 00
10: 00 80 42 e7 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 04 31
30: 00 00 00 00 80 00 00 00 00 00 00 00 09 04 00 00
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
Subsystem: VIA Technologies, Inc.: Unknown device aa01
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: [c0] Power Management version 2
00: 06 11 77 31 87 00 10 02 00 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 01 aa
30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00
0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc.: Unknown device aa01
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at cc00 [size=16]
Capabilities: [c0] Power Management version 2
00: 06 11 71 05 07 00 90 02 06 8a 01 01 00 20 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 cc 00 00 00 00 00 00 00 00 00 00 06 11 01 aa
30: 00 00 00 00 c0 00 00 00 00 00 00 00 ff 01 00 00
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded Ethernet Controller on VT8235
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at d400 [size=256]
Memory at e7429000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2
00: 06 11 65 30 07 00 10 02 74 00 00 02 08 20 00 00
10: 01 d4 00 00 00 90 42 e7 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 02 01
30: 00 00 00 00 40 00 00 00 00 00 00 00 05 01 03 08
0000:00:14.0 Mass storage controller: Promise Technology, Inc. PDC20318 (SATA150 TX4) (rev 02)
Subsystem: Promise Technology, Inc. PDC20318 (SATA150 TX4) Flags: bus master, 66MHz, medium devsel, latency 96, IRQ 12 I/O ports at d800 [size=64] I/O ports at dc00 [size=16] I/O ports at e000 [size=128] Memory at e742a000 (32-bit, non-prefetchable) [size=4K] Memory at e7400000 (32-bit, non-prefetchable) [size=128K] Expansion ROM at 48000000 [disabled] [size=16K] Capabilities: [60] Power Management version 2
00: 5a 10 18 33 07 00 30 02 02 00 80 01 90 60 00 00 10: 01 d8 00 00 01 dc 00 00 01 e0 00 00 00 a0 42 e7 20: 00 00 40 e7 00 00 00 00 00 00 00 00 5a 10 18 33 30: 00 00 00 00 60 00 00 00 00 00 00 00 0c 01 04 12
0000:01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics (rev 03) (prog-if 00 [VGA])
Subsystem: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 5
Memory at e0000000 (32-bit, prefetchable) [size=64M]
Memory at e4000000 (32-bit, non-prefetchable) [size=16M]
Expansion ROM at e5000000 [disabled] [size=64K]
Capabilities: [60] Power Management version 2
Capabilities: [70] AGP version 2.0
00: 06 11 22 31 07 00 30 02 03 00 00 03 00 20 00 00
10: 08 00 00 e0 00 00 00 e4 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 22 31
30: 00 00 00 00 60 00 00 00 00 00 00 00 05 01 02 00
Re: EDAC (was: Re: 2.6.14-rc5-mm1)
Quoted 45 lines · --- Sander
Alan Cox wrote (ao):
Quoted 2 lines · Sander
Quoted 1 line
Stupid question: should EDAC work on a Via Epia
board? Because I see the
Quoted 1 line
Quoted 1 line
"Detected Parity Error" messages too (and a lot
of them), but figured
Quoted 3 lines
Quoted 1 line
that the option is just 'not an option' :-)
The PCI parity check should work on every
correctly built PCI card and
Quoted 3 lines
bridge.
Quoted 1 line
If it should work I'll be happy to send the
error and lspci if that
Quoted 3 lines
Quoted 1 line
helps.
Please do. I'm trying to find the common items
that cause spurious pci
Quoted 1 line
errors
Via Epia MII 10000, kernel 2.6.14-rc4-mm1:
$ grep EDAC .config # EDAC - error detection and reporting (RAS) CONFIG_EDAC=y # CONFIG_EDAC_DEBUG is not set CONFIG_EDAC_MM_EDAC=y # CONFIG_EDAC_AMD76X is not set # CONFIG_EDAC_E7XXX is not set # CONFIG_EDAC_E752X is not set # CONFIG_EDAC_I82875P is not set # CONFIG_EDAC_I82860 is not set # CONFIG_EDAC_R82600 is not set CONFIG_EDAC_POLL=y[42949380.590000] Freeing unused kernel memory: 168k freed [42949381.350000] PCI- Detected Parity Error on 0000:00:01.0 0000:00:01.0 [42949382.350000] PCI- Detected Parity Error on 0000:00:01.0 0000:00:01.0 [42949383.350000] PCI- Detected Parity Error on 0000:00:01.0 0000:00:01.0 [42949384.350000] PCI- Detected Parity Error on
Quoted 4 lines
0000:00:01.0 0000:00:01.0
etc
The EDAC scanning code first scans the STATUS register of all the PCI devices in the system. This status register reflects operations on the main bus. Second, the code scans the SECONDARY STATUS register of all bridge devices, which reflects operations on the sub-bus.
This instance (0000:00:01.0) of output shows me the VIA VT8633 is generating the parity bit. The default poll interval if 1000 ms and the above output shows this. This bridge is either having a parity error on the main bus OR more likely is generating false positives. How to determine which? More investigation is needed.
But at least there is some DETECTION occurring. If it is false positives, then this device could be placed on the "future" blacklist list and at boot time fed to the EDAC module.
There is a difference between "detecting" the parity and "handling" it. Currently edac is setup to detect and report.
doug thompson
Quoted 3 lines
lspci -vxx:
<snip>
Quoted 8 lines
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: e4000000-e5ffffff Prefetchable memory behind bridge:
Quoted 6 lines
e0000000-e3ffffff
Capabilities: [80] Power Management version 2
00: 06 11 91 b0 07 01 30 a2 00 00 04 06 00 00 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 00 f0 00 20 a2 20: 00 e4 f0 e5 00 e0 f0 e3 00 00 00 00 00 00 00 00 30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 0c 00
"If you think Education is expensive, just try Ignorance"
"Don't tell people HOW to do things, tell them WHAT you want and they will surprise you with their ingenuity."
Gen George Patton
Re: EDAC (was: Re: 2.6.14-rc5-mm1)
Doug Thompson wrote (ao):
Quoted 10 lines
Quoted 1 line · --- Sander
Via Epia MII 10000, kernel 2.6.14-rc4-mm1:
The EDAC scanning code first scans the STATUS register of all the PCI devices in the system. This status register reflects operations on the main bus. Second, the code scans the SECONDARY STATUS register of all bridge devices, which reflects operations on the sub-bus.
Quoted 7 lines
This instance (0000:00:01.0) of output shows me the VIA VT8633 is generating the parity bit. The default poll interval if 1000 ms and the above output shows this. This bridge is either having a parity error on the main bus OR more likely is generating false positives. How to determine which? More investigation is needed.
Anything I can do? And will blacklisting make EDAC useless? If so, does it make more sense not to configure EDAC?
Signature · 2 lines
Humilis IT Services and Solutions http://www.humilis.net
Re: EDAC (was: Re: 2.6.14-rc5-mm1)
Quoted 20 lines · --- Sander
Doug Thompson wrote (ao):
Quoted 4 lines
Quoted 1 line · --- Sander
Via Epia MII 10000, kernel 2.6.14-rc4-mm1:
The EDAC scanning code first scans the STATUS
register
Quoted 3 lines
of all the PCI devices in the system. This status register reflects operations on the main bus. Second, the code scans the SECONDARY STATUS
register
Quoted 1 line
of all bridge devices, which reflects operations
on
Quoted 3 lines
the sub-bus.
This instance (0000:00:01.0) of output shows me
the
Quoted 1 line
VIA VT8633 is generating the parity bit. The
default
Quoted 1 line
poll interval if 1000 ms and the above output
shows
Quoted 8 lines
Quoted 1 line
this. This bridge is either having a parity error
on
Quoted 2 lines
the main bus OR more likely is generating false positives. How to determine which? More
investigation
Quoted 1 line
is needed.
Anything I can do?
To help? Keep an eye for other devices which post parity errors.
To overcome this on your own system? If you don't want so many message for the moment, turn off EDAC. Later when the blacklist is avaliable, put this device in the blacklist.
Quoted 1 line
And will blacklisting make EDAC useless?
No, just less closure, less complete. If we were SURE all devices followed the rules, then a parity event is a BAD thing we could then count on. Since it is an imperfect world, we gather the "blacklist" of cards that don't follow the PCI spec, send them a blasting letter, buy alternatives that do work and continue to scan for parity errors.
This scanning of parity errrors allowed my company to isolate data corruption between an interconnect in nodes on a cluster. The fault? The riser card had failings. With this parity scanner, we isolated the borderline risers and replaced them. Saved alot of time. Luckily, the card we had did NOT generate false positives. We have another high speed interconnect which does generate false positives, we told them about it. Helped them reproduce the reporting via script using 'setpci'. They finally ack'd they had a firmware problem and will rev the FW in january - yeah!
Quoted 1 line
If so, does it make more sense not to configure
EDAC?
depends on your requirements.
we have been living with systems with PCI devices for a decade now. how many times have events occurred that had no explaination and are simply dismissed? There were no detectors.
We assume many things, even today. How many desktops with gigs of memory have no ECC? I have learned my lesson while refactoring bluesmoke/edac that ECC is very important. ECC always in my machines for now on, for me anyway.
For PCI devices, if you want to "know" data is being transmitted correctly, then there needs to be "detector" and "reporter" and "handler" agents of this bad events to properly notice, report and process them.
doug thompson
Quoted 5 lines
Signature · 3 lines
-- Humilis IT Services and Solutions http://www.humilis.net
"If you think Education is expensive, just try Ignorance"
"Don't tell people HOW to do things, tell them WHAT you want and they will surprise you with their ingenuity."
Gen George Patton
Re: EDAC (was: Re: 2.6.14-rc5-mm1)
(Cc: trimmed)
Doug Thompson wrote (ao):
Quoted 11 lines
Quoted 7 lines · --- Sander
Doug Thompson wrote (ao):
Quoted 4 lines
This bridge is either having a parity error on the main bus OR more likely is generating false positives. How to determine which? More investigation is needed.
Anything I can do?
To help? Keep an eye for other devices which post parity errors.
Ok :-) But you also say more investigation is needed. Is this something I can help with, as an owner of this hardware?
And is there an EDAC list which reports should go to or is lkml fine? There is no MAINTAINERS entry or info in Documentation (in 2.6.14-rc4-mm1).
If not, is it useful if I make a website and collect reports?
Quoted 15 lines
Quoted 1 line
If so, does it make more sense not to configure EDAC?
depends on your requirements.
we have been living with systems with PCI devices for a decade now. how many times have events occurred that had no explaination and are simply dismissed? There were no detectors.
We assume many things, even today. How many desktops with gigs of memory have no ECC? I have learned my lesson while refactoring bluesmoke/edac that ECC is very important. ECC always in my machines for now on, for me anyway.
Quoted 5 lines
For PCI devices, if you want to "know" data is being transmitted correctly, then there needs to be "detector" and "reporter" and "handler" agents of this bad events to properly notice, report and process them.
I'd better configure EDAC :-)
Thanks for your answers Doug.
Signature · 2 lines
Humilis IT Services and Solutions http://www.humilis.net
RE: EDAC (was: Re: 2.6.14-rc5-mm1)
Quoted 4 lines
Ok :-) But you also say more investigation is needed. Is this something I can help with, as an owner of this hardware?
You might try something like HPL or some other benchmark that validates its results, I have found that if you have PCI parity errors, even potentially
on cards that the benchmark should not be using, it will usually cause invalid results in the benchmark when it is ran over several days.
This is even worse if the benchmark is using an interconnect board with a lot of its communication going across the board.
Quoted 5 lines
And is there an EDAC list which reports should go to or is lkml fine? There is no
MAINTAINERSentry or info in Documentation (in 2.6.14-rc4-mm1).
Lists.sourceforge.net
Search for bluesmoke, the original name. It may be in the process
of being changed to EDAC.
Quoted 4 lines
I'd better configure EDAC :-)
Thanks for your answers Doug.
If you have ECC ram, just the ECC monitoring is important enough even without the PCI parity stuff working.
Roger
RE: EDAC (was: Re: 2.6.14-rc5-mm1)
In reply to Doug ThompsonQuoted 6 lines
depends on your requirements.
Quoted 8 lines
we have been living with systems with PCI devices for a decade now. how many times have events occurred that had no explaination and are simply dismissed? There were no detectors.
We assume many things, even today. How many desktops with gigs of memory have no ECC? I have learned my lesson while refactoring bluesmoke/edac that ECC is very important. ECC always in my machines for now on, for me anyway.
The bigger question is how many machines have ecc but no one is watching it for errors of any sort, the answer for this question
is almost all. On opteron's mcelog does a decent job of alerting
people to memory issues, but not even all Enterprise distributions include mcelog, but on the Xeons there is almost nothing warning any of ecc failures, unless someone checks the bios event logs on the few machinces that work, and this is fairly difficult, so almost no one does.
Quoted 5 lines
For PCI devices, if you want to "know" data is being transmitted correctly, then there needs to be "detector" and "reporter" and "handler" agents of this bad events to properly notice, report and process them.
And there are other PCI cards/motherboards that have timing issues also, I know because I have personally found and debugged a couple of them, one was nasty enough that it corrupted data on every 5-10GB of reads, and it was *ALL* motherboards of this type with a certain given card running at 133mhz. With a different manufacturer's similar card it crashed with a MTBF of about when one would expect corrupted data.
Roger
2.6.14-rc5-mm1 - ide-cs, pcmcia ioctl
In reply to Andrew MortonLe Monday 24 October 2005 10:48, Andrew Morton a écrit :
| - A number of tty drivers still won't compile.
after disabling jsm, i finally build once again a mm-kernel successfully!
booting the fresh kernel26mm, i ran into a problem with ide-cs:
info while booting / start of hotplug:
Oct 26 01:02:28 localhost kernel: [17179579.008000] Yenta: CardBus bridge found at 0000:02:00.1 [1014:0185] Oct 26 01:02:28 localhost kernel: [17179579.160000] Yenta: ISA IRQ mask 0x04b8, PCI irq 11 Oct 26 01:02:28 localhost kernel: [17179579.184000] Socket status: 30000006 Oct 26 01:02:28 localhost kernel: [17179579.208000] pcmcia: parent PCI bridge I/O window: 0x4000 - 0x8fff Oct 26 01:02:28 localhost kernel: [17179579.232000] cs: IO port probe 0x4000-0x8fff: clean. Oct 26 01:02:28 localhost kernel: [17179579.256000] pcmcia: parent PCI bridge Memory window: 0xd0200000 - 0xdfffffff Oct 26 01:02:28 localhost kernel: [17179579.280000] pcmcia: parent PCI bridge Memory window: 0xf0000000 - 0xf80fffff
when i plug in the pcmcia-compact-flash adapter into the laptop:
Oct 26 01:05:10 localhost kernel: [17179767.840000] cs: memory probe 0xf0000000-0xf80fffff: excluding 0xf0000000-0xf87fffff Oct 26 01:05:11 localhost kernel: [17179767.924000] ide_cs: Unknown symbol cs_error Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_deregister_client Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_get_first_tuple Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_unregister_driver Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_get_tuple_data Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_get_next_tuple Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_register_client Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_get_configuration_info Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_request_io Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_request_configuration Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_release_configuration Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_parse_tuple Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_release_io Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_register_driver Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_release_irq Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_request_irq Oct 26 01:05:11 localhost kernel: [17179768.176000] Probing IDE interface ide2... Oct 26 01:05:11 localhost kernel: [17179768.464000] hde: 1024MB Flash Card, CFA DISK drive Oct 26 01:05:12 localhost kernel: [17179769.136000] ide2 at 0x4100-0x4107,0x410e on irq 3 Oct 26 01:05:12 localhost kernel: [17179769.136000] hde: max request size: 128KiB Oct 26 01:05:12 localhost kernel: [17179769.136000] hde: 2001888 sectors (1024 MB) w/1KiB Cache, CHS=1986/16/63 Oct 26 01:05:12 localhost kernel: [17179769.136000] hde: cache flushes not supported Oct 26 01:05:12 localhost kernel: [17179769.140000] hde: hde1 Oct 26 01:05:12 localhost kernel: [17179769.148000] ide-cs: hde: Vcc = 3.3, Vpp = 0.0 Oct 26 01:05:12 localhost kernel: [17179769.260000] hde: hde1 Oct 26 01:05:12 localhost kernel: [17179769.292000] hde: hde1 Oct 26 01:05:12 localhost kernel: [17179769.300000] hde: hde1 Oct 26 01:05:12 localhost kernel: [17179769.440000] hde: hde1 Oct 26 01:05:12 localhost kernel: [17179769.532000] hde: hde1 Oct 26 01:05:12 localhost kernel: [17179769.720000] hde: hde1 Oct 26 01:05:12 localhost kernel: [17179769.868000] hde: hde1 Oct 26 01:05:13 localhost kernel: [17179770.016000] hde: hde1
...
and it repeats this untill i either power off the machine or take out the pcmcia compact flash addapter (what results in a freeze of everything (unfortunately no log output and no sysrq working (probably because keyboard also not working)), so powering off is anyway the only option)
as a semi-professional photographer, i depend on a working ide-cs device. the last kernel it worked is some months old... until now i never checked and now i discovered this break.
i use pcmciautils 010
if you need more information, i will try to help wherever i can to help to make ide-cs work again.
greetings,
Damir
Signature · 2 lines
If a man has talent and cannot use it, he has failed. -- Thomas Wolfe
2.6.14-rc5-mm1 - ide-cs broken!
isn't anybody else using ide-cs? i feel lonely!
greetings,
Damir
Signature · 2 lines
Oh this age! How tasteless and ill-bred it is. -- Gaius Valerius Catullus
Re: 2.6.14-rc5-mm1 - ide-cs broken!
Quoted 3 lines · Damir Perisa
isn't anybody else using ide-cs? i feel lonely!
That's called "stunned silence".
Quoted 12 lines
booting the fresh kernel26mm, i ran into a problem with ide-cs:
info while booting / start of hotplug:
Oct 26 01:02:28 localhost kernel: [17179579.008000] Yenta: CardBus bridge found at 0000:02:00.1 [1014:0185] Oct 26 01:02:28 localhost kernel: [17179579.160000] Yenta: ISA IRQ mask 0x04b8, PCI irq 11 Oct 26 01:02:28 localhost kernel: [17179579.184000] Socket status: 30000006 Oct 26 01:02:28 localhost kernel: [17179579.208000] pcmcia: parent PCI bridge I/O window: 0x4000 - 0x8fff Oct 26 01:02:28 localhost kernel: [17179579.232000] cs: IO port probe 0x4000-0x8fff: clean. Oct 26 01:02:28 localhost kernel: [17179579.256000] pcmcia: parent PCI bridge Memory window: 0xd0200000 - 0xdfffffff Oct 26 01:02:28 localhost kernel: [17179579.280000] pcmcia: parent PCI bridge Memory window: 0xf0000000 - 0xf80fffffwhen i plug in the pcmcia-compact-flash adapter into the laptop:
Quoted 13 lines
Oct 26 01:05:10 localhost kernel: [17179767.840000] cs: memory probe 0xf0000000-0xf80fffff: excluding 0xf0000000-0xf87fffff Oct 26 01:05:11 localhost kernel: [17179767.924000] ide_cs: Unknown symbol cs_error Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_deregister_client Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_get_first_tuple Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_unregister_driver Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_get_tuple_data Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_get_next_tuple Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_register_client Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_get_configuration_info Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_request_io Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_request_configuration Oct 26 01:05:11 localhost kernel: [17179767.928000] ide_cs: Unknown symbol pcmcia_release_configuration
I'd have thought this was basically impossible. It's saying that drivers/pcmcia/ds.c isn't present. What's the setting of CONFIG_PCMCIA in your .config?
Perhaps the modprobe dependencies are screwed up. Try modprobing pcmcia.o by hand before inserting the card?
Re: 2.6.14-rc5-mm1 - ide-cs broken!
Le Friday 28 October 2005 00:03, Andrew Morton a écrit :
| Damir Perisa <[email protected]> wrote: | > isn't anybody else using ide-cs? i feel lonely! | | That's called "stunned silence".
ah ... then it's ok ;-)
| | [...] | | I'd have thought this was basically impossible. It's saying that | drivers/pcmcia/ds.c isn't present. What's the setting of | CONFIG_PCMCIA in your .config?
CONFIG_PCMCIA=mCONFIG_PCMCIA_LOAD_CIS=yCONFIG_PCMCIA_IOCTL=yCONFIG_PCMCIA_PROBE=y
all other PCMCIA are modules ( =m)
| Perhaps the modprobe dependencies are screwed up. Try modprobing | pcmcia.o by hand before inserting the card?
[17194333.620000] cs: memory probe 0xf0000000-0xf80fffff: excluding 0xf0000000-0xf87fffff [17194333.644000] pcmcia: Detected deprecated PCMCIA ioctl usage. [17194333.644000] pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools. [17194333.644000] pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details. [17194334.032000] Probing IDE interface ide2... [17194334.320000] hde: 1024MB Flash Card, CFA DISK drive [17194334.992000] ide2 at 0x4100-0x4107,0x410e on irq 3 [17194334.992000] hde: max request size: 128KiB [17194334.992000] hde: 2001888 sectors (1024 MB) w/1KiB Cache, CHS=1986/16/63 [17194334.992000] hde: cache flushes not supported [17194334.992000] hde: hde1 [17194335.004000] ide-cs: hde: Vcc = 3.3, Vpp = 0.0 [17194335.224000] hde: hde1 [17194335.632000] hde: hde1 [17194335.736000] hde: hde1 [17194335.744000] hde: hde1
... ("hde: hde1" repeating)...
ok, now the situation is less lethal, but still no proper ide-cs working. there are no unknown symbols now, but the other output in dmesg is the same. especially, the loop to output "hde: hde1" is here, but if i remove the card, it stops and the system is still responsible.
i checked something i forgot to check before... is the hde device seen in /sys somewhere, when the card is plugged in. the answer is yes!:
/sys/block/hde/hde1/
presents itself fully normal like other ide drives. in /sys/block/hde/hde1/sample.sh
i found "mknod /dev/hde1 b 33 1" and tried to run it. successfully! the result is: in dmesg, the "hde: hde1" output loop stopped and my card is working again!!!
so the trouble seems not only (or not at all) related to the kernel but (also) to udev (i use 071), hotplug (mine is 2004_09_23), pcmciautils
(010) or something else.
can somebody tell me, what state of this process (discovering device, loading needed modules, udev creating node under /dev) is the output "hde: hde1" to dmesg and how can it be possible that it loops?
it seems that this chain of processing is stuck somewhere and needs a execution of the command to create the node under /dev by hand to finish.
please anybody around with more experience with this systems help or suggest where to search.
thank you in advance + greetings,
Damir
Signature · 2 lines
Penicillin doesn't kill bacteria. Technically, it keeps it from reproducing.
2.6.14-rc5-mm1: EDAC: several options without a help text
In reply to Andrew MortonHi Alan,
the hardware-specific EDAC drivers don't have a help text.
Can you add help texts?
TIA
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedRe: 2.6.14-rc5-mm1: EDAC: several options without a help text
Quoted 5 lines · Adrian Bunk
Hi Alan,
the hardware-specific EDAC drivers don't have a help text.
Can you add help texts?
Done
edac/Kconfig renamed from edac/Kconfig~ +18 -0
@@ -44,26 +44,44 @@ config EDAC_AMD76X tristate "AMD 76x (760, 762, 768)" depends on EDAC + help + Support for error detection and correction on the AMD 76x + series of chipsets used with the Athlon processor. config EDAC_E7XXX tristate "Intel e7xxx (e7205, e7500, e7501, e7505)" depends on EDAC + help + Support for error detection and correction on the Intel + E7205, E7500, E7501 and E7505 server chipsets. config EDAC_E752X tristate "Intel e752x (e7520, e7525, e7320)" depends on EDAC + help + Support for error detection and correction on the Intel + E7520, E7525, E7320 server chipsets. config EDAC_I82875P tristate "Intel 82875p (D82875P, E7210)" depends on EDAC + help + Support for error detection and correction on the Intel + DP82785P and E7210 server chipsets. config EDAC_I82860 tristate "Intel 82860" depends on EDAC + help + Support for error detection and correction on the Intel + 82860 chipset. config EDAC_R82600 tristate "Radisys 82600 embedded chipset" depends on EDAC + help + Support for error detection and correction on the Radisys + 82600 embedded chipset. choice prompt "Error detecting method"
2.6.14-rc5-mm1: reiser4: ICE with gcc 2.95
In reply to Andrew MortonTrying to compile 2.6.14-rc5-mm1 with gcc 2.95 and CONFIG_REISER4_DEBUG=y results in the following ICE:
<-- snip -->
...
CC fs/reiser4/plugin/space/bitmap.ofs/reiser4/plugin/space/bitmap.c: In function `parse_blocknr':fs/reiser4/plugin/space/bitmap.c:608: Internal compiler error:fs/reiser4/plugin/space/bitmap.c:608: internal error--unrecognizable insn:
(insn 93 266 269 (parallel[
(set (reg:SI 0 %eax)
(asm_operands ("") ("=a") 0[
(reg:DI 1 %edx)
]
[
(asm_input:DI ("A"))
] ("fs/reiser4/plugin/space/bitmap.c") 603))
(set (reg:SI 1 %edx)
(asm_operands ("") ("=d") 1[
(reg:DI 1 %edx)
]
[
(asm_input:DI ("A"))
] ("fs/reiser4/plugin/space/bitmap.c") 603))
] ) -1 (insn_list 83 (nil))
(nil))make[2]: *** [fs/reiser4/plugin/space/bitmap.o] Error 1 make[1]: *** [fs/reiser4] Error 2
make: *** [fs] Error 2
<-- snip -->
Although this is technically an error in gcc 2.95, the code should be fixed to work around this issue since gcc 2.95 is a supported compiler for compiling kernel 2.6.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed2.6.14-rc5-mm1: SAS: compile error with gcc 2.95
In reply to Andrew MortonQuoted 7 lines · Andrew Morton
...
Changes since 2.6.14-rc4-mm1:
...
git-sas.patch
...
Subsystem trees
...
This gives the following compile error with gcc 2.95:
<-- snip -->
...
CC drivers/scsi/aic94xx/aic94xx_init.o
In file included from include/scsi/sas/sas.h:90,
from include/scsi/sas/sas_class.h:33,
from include/scsi/sas/sas_discover.h:29,
from drivers/scsi/aic94xx/aic94xx.h:33,
from drivers/scsi/aic94xx/aic94xx_init.c:36:include/scsi/sas/sas_frames.h:46: warning: unnamed struct/union that defines no instances include/scsi/sas/sas_frames.h:47: warning: unnamed struct/union that defines no instances include/scsi/sas/sas_frames.h:55: warning: unnamed struct/union that defines no instances include/scsi/sas/sas_frames.h:70: warning: unnamed struct/union that defines no instances include/scsi/sas/sas_frames.h:71: warning: unnamed struct/union that defines no instances include/scsi/sas/sas_frames.h:79: warning: unnamed struct/union that defines no instances In file included from include/scsi/sas/sas_frames.h:90,
from include/scsi/sas/sas.h:90,
from include/scsi/sas/sas_class.h:33,
from include/scsi/sas/sas_discover.h:29,
from drivers/scsi/aic94xx/aic94xx.h:33,
from drivers/scsi/aic94xx/aic94xx_init.c:36:include/scsi/sas/sas_frames_le.h:51: warning: unnamed struct/union that defines no instances include/scsi/sas/sas_frames_le.h:53: warning: unnamed struct/union that defines no instances include/scsi/sas/sas_frames_le.h:63: warning: unnamed struct/union that defines no instances include/scsi/sas/sas_frames_le.h:65: warning: unnamed struct/union that defines no instances include/scsi/sas/sas_frames_le.h:219: warning: unnamed struct/union that defines no instances In file included from drivers/scsi/aic94xx/aic94xx.h:33,
from drivers/scsi/aic94xx/aic94xx_init.c:36:
include/scsi/sas/sas_discover.h:157: warning: unnamed struct/union that defines no instances include/scsi/sas/sas_discover.h: In function `sas_init_dev':include/scsi/sas/sas_discover.h:201: structure has no member named end_dev' include/scsi/sas/sas_discover.h:201: structure has no member named end_dev' include/scsi/sas/sas_discover.h:201: structure has no member named end_dev' include/scsi/sas/sas_discover.h:201: structure has no member named end_dev' include/scsi/sas/sas_discover.h:205: structure has no member named ex_dev' include/scsi/sas/sas_discover.h:205: structure has no member named ex_dev' include/scsi/sas/sas_discover.h:205: structure has no member named ex_dev' include/scsi/sas/sas_discover.h:205: structure has no member named ex_dev' include/scsi/sas/sas_discover.h:210: structure has no member named sata_dev' include/scsi/sas/sas_discover.h:210: structure has no member named sata_dev' include/scsi/sas/sas_discover.h:210: structure has no member named sata_dev' include/scsi/sas/sas_discover.h:210: structure has no member named sata_dev' In file included from drivers/scsi/aic94xx/aic94xx_hwi.h:36,
from drivers/scsi/aic94xx/aic94xx_reg.h:32,
from drivers/scsi/aic94xx/aic94xx_init.c:37:drivers/scsi/aic94xx/aic94xx_sas.h: At top level:drivers/scsi/aic94xx/aic94xx_sas.h:363: warning: unnamed struct/union that defines no instances drivers/scsi/aic94xx/aic94xx_sas.h:643: warning: unnamed struct/union that defines no instances make[3]: *** [drivers/scsi/aic94xx/aic94xx_init.o] Error 1
<-- snip -->
Since gcc 2.95 is a supported compiler for 2.6, the code has to be changed to compile with gcc 2.95.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedRe: 2.6.14-rc5-mm1: SAS: compile error with gcc 2.95
Quoted 75 lines · --- Adrian Bunk
Quoted 7 lines · Andrew Morton
...
Changes since 2.6.14-rc4-mm1:
...
git-sas.patch
...
Subsystem trees
...This gives the following compile error with gcc 2.95:
<-- snip -->
...
CCdrivers/scsi/aic94xx/aic94xx_init.o
In file included frominclude/scsi/sas/sas.h:90,from include/scsi/sas/sas_class.h:33, from include/scsi/sas/sas_discover.h:29, from drivers/scsi/aic94xx/aic94xx.h:33, from drivers/scsi/aic94xx/aic94xx_init.c:36:
include/scsi/sas/sas_frames.h:46: warning: unnamed struct/union that defines no instancesinclude/scsi/sas/sas_frames.h:47: warning: unnamed struct/union that defines no instancesinclude/scsi/sas/sas_frames.h:55: warning: unnamed struct/union that defines no instancesinclude/scsi/sas/sas_frames.h:70: warning: unnamed struct/union that defines no instancesinclude/scsi/sas/sas_frames.h:71: warning: unnamed struct/union that defines no instancesinclude/scsi/sas/sas_frames.h:79: warning: unnamed struct/union that defines no instances
In file included frominclude/scsi/sas/sas_frames.h:90,from include/scsi/sas/sas.h:90, from include/scsi/sas/sas_class.h:33, from include/scsi/sas/sas_discover.h:29, from drivers/scsi/aic94xx/aic94xx.h:33, from drivers/scsi/aic94xx/aic94xx_init.c:36:
include/scsi/sas/sas_frames_le.h:51: warning: unnamed struct/union that defines no instancesinclude/scsi/sas/sas_frames_le.h:53: warning: unnamed struct/union that defines no instancesinclude/scsi/sas/sas_frames_le.h:63: warning: unnamed struct/union that defines no instancesinclude/scsi/sas/sas_frames_le.h:65: warning: unnamed struct/union that defines no instancesinclude/scsi/sas/sas_frames_le.h:219: warning: unnamed struct/union that defines no instances
In file included fromdrivers/scsi/aic94xx/aic94xx.h:33,from drivers/scsi/aic94xx/aic94xx_init.c:36:
include/scsi/sas/sas_discover.h:157: warning: unnamed struct/union that defines no instancesinclude/scsi/sas/sas_discover.h: In function `sas_init_dev':include/scsi/sas/sas_discover.h:201: structure has no member namedend_dev' include/scsi/sas/sas_discover.h:201: structure has no member namedend_dev'include/scsi/sas/sas_discover.h:201: structure has no member namedend_dev' include/scsi/sas/sas_discover.h:201: structure has no member namedend_dev'include/scsi/sas/sas_discover.h:205: structure has no member namedex_dev' include/scsi/sas/sas_discover.h:205: structure has no member namedex_dev'include/scsi/sas/sas_discover.h:205: structure has no member namedex_dev' include/scsi/sas/sas_discover.h:205: structure has no member namedex_dev'include/scsi/sas/sas_discover.h:210: structure has no member namedsata_dev' include/scsi/sas/sas_discover.h:210: structure has no member namedsata_dev'include/scsi/sas/sas_discover.h:210: structure has no member namedsata_dev' include/scsi/sas/sas_discover.h:210: structure has no member namedsata_dev' In file included fromdrivers/scsi/aic94xx/aic94xx_hwi.h:36,from drivers/scsi/aic94xx/aic94xx_reg.h:32, from drivers/scsi/aic94xx/aic94xx_init.c:37:
drivers/scsi/aic94xx/aic94xx_sas.h: At top level:drivers/scsi/aic94xx/aic94xx_sas.h:363: warning: unnamed struct/union that defines no instancesdrivers/scsi/aic94xx/aic94xx_sas.h:643: warning: unnamed struct/union that defines no instances
make[3]: *** [drivers/scsi/aic94xx/aic94xx_init.o] Error 1
Quoted 4 lines
<-- snip -->
Since gcc 2.95 is a supported compiler for 2.6, the code has to be changed to compile with gcc 2.95.
Yes, I've been meaning to add names to unions to fix compilation with gcc 2.95 for some time now. Andrew has pointed that out to me before.
I'll submit a patch shortly.
Luben
Signature · 2 lines
http://linux.adaptec.com/sas/ http://www.adaptec.com/sas/
PATCH 1/1 EDAC drivers: missing PCI dependencies
In reply to Andrew MortonThis patch fixes the following compile errors with CONFIG_PCI=n:
<-- snip -->
...
LD .tmp_vmlinux1drivers/built-in.o: In function `amd76x_probe1':
amd76x_edac.c:(.text+0x56dc56): undefined reference to pci_dev_get' drivers/built-in.o: In function e752x_probe1':
e752x_edac.c:(.text+0x56f152): undefined reference to pci_scan_single_device' e752x_edac.c:(.text+0x56f330): undefined reference to pci_dev_get' drivers/built-in.o: In function `i82875p_probe1':
i82875p_edac.c:(.text+0x56f6b4): undefined reference to pci_scan_single_device' i82875p_edac.c:(.text+0x56f6dd): undefined reference to pci_release_regions' i82875p_edac.c:(.text+0x56f6ef): undefined reference to `pci_proc_attach_device'
make: *** [.tmp_vmlinux1] Error 1
<-- snip -->
drivers/edac/Kconfig renamed from drivers/edac/Kconfig.old +3 -3
@@ -43,7 +43,7 @@ config EDAC_AMD76X tristate "AMD 76x (760, 762, 768)" - depends on EDAC + depends on EDAC && PCI config EDAC_E7XXX tristate "Intel e7xxx (e7205, e7500, e7501, e7505)"
@@ -51,11 +51,11 @@ config EDAC_E752X tristate "Intel e752x (e7520, e7525, e7320)" - depends on EDAC + depends on EDAC && PCI config EDAC_I82875P tristate "Intel 82875p (D82875P, E7210)" - depends on EDAC + depends on EDAC && PCI config EDAC_I82860 tristate "Intel 82860"
PATCH 1/1 fs/namei.c: make path_lookup_create() static
In reply to Andrew MortonQuoted 7 lines · Andrew Morton
...
Changes since 2.6.14-rc4-mm1:
...
git-nfs.patch
...
Subsystem trees
...
<-- snip -->
This patch makes the needlessly global function path_lookup_create() static.
fs/namei.c renamed from fs/namei.c.old +3 -2
@@ -1109,8 +1109,9 @@* @open_flags: open intent flags * @create_mode: create intent flags */ -int path_lookup_create (const char *name,unsigned int lookup_flags, -struct nameidata *nd,int open_flags,int create_mode) +static int path_lookup_create (const char *name,unsigned int lookup_flags, +struct nameidata *nd,int open_flags, +int create_mode) {return __path_lookup_intent_open (name, lookup_flags|LOOKUP_CREATE , nd, open_flags, create_mode);
Re: [-mm patch] fs/namei.c: make path_lookup_create() static
su den 30.10.2005 klokka 16:53 (+0100) skreiv Adrian Bunk:
Quoted 10 lines · Andrew Morton
Quoted 7 lines
...
Changes since 2.6.14-rc4-mm1:
...
git-nfs.patch
...
Subsystem trees
...
Quoted 5 lines
<-- snip -->
This patch makes the needlessly global function
path_lookup_create()static.
ACK...
Trond
PATCH 1/1 fix NET_RADIO=n, IEEE80211=y compile
In reply to Andrew MortonQuoted 7 lines · Andrew Morton
...
Changes since 2.6.14-rc4-mm1:
...
git-netdev-all.patch
...
Subsystem trees
...
<-- snip -->
This patch fixes the following compile error with CONFIG_NET_RADIO=n and CONFIG_IEEE80211=y:
LD .tmp_vmlinux1net/built-in.o: In function `ieee80211_rx':
: undefined reference to `wireless_spy_update'
make: *** [.tmp_vmlinux1] Error 1
net/ieee80211/ieee80211_rx.c renamed from net/ieee80211/ieee80211_rx.c.old +2 -0
@@ -370,6 +370,7 @@/* Put this code here so that we avoid duplicating it in all * Rx paths. - Jean II */ #ifdef IW_WIRELESS_SPY /* defined in iw_handler.h */ +#ifdef CONFIG_NET_RADIO /* If spy monitoring on */ if (ieee->spy_data.spy_number > 0) { struct iw_quality wstats;
@@ -396,6 +397,7 @@/* Update spy records */ wireless_spy_update (ieee->dev, hdr->addr2, &wstats); } +#endif /* CONFIG_NET_RADIO */ #endif /* IW_WIRELESS_SPY */ #ifdef NOT_YET
PATCH 1/1 EDAC: remove proc_ent from struct mem_ctl_info
In reply to Andrew MortonWhile fixing a compile error with CONFIG_PROC_FS=n in the EDAC code, I discovered that the proc_ent member of struct mem_ctl_info is only used in a debug printk.
Is this patch to remove proc_ent OK?
drivers/edac/edac_mc.c | 8 ++------ drivers/edac/edac_mc.h | 3 --- 2 files changed, 2 insertions(+), 9 deletions(-)
drivers/edac/edac_mc.h renamed from drivers/edac/edac_mc.h.old +0 -3
@@ -313,9 +313,6 @@const char *mod_ver;const char *ctl_name;char proc_name[MC_PROC_NAME_MAX_LEN +1 ]; -#ifdef CONFIG_PROC_FS -struct proc_dir_entry *proc_ent; -#endif void *pvt_info;u32 ue_noinfo_count;/* Uncorrectable Errors w/o info */ u32 ce_noinfo_count;/* Correctable Errors w/o info */
drivers/edac/edac_mc.c renamed from drivers/edac/edac_mc.c.old +2 -6
@@ -362,8 +362,6 @@printk (KERN_INFO "\tpdev = %p\n" , mci->pdev);printk (KERN_INFO "\tmod_name:ctl_name = %s:%s\n" , mci->mod_name, mci->ctl_name); -printk (KERN_INFO "\tproc_name = %s, proc_ent = %p\n" , - mci->proc_name, mci->proc_ent);printk (KERN_INFO "\tpvt_info = %p\n\n" , mci->pvt_info); }
@@ -575,10 +573,8 @@ goto finish; } - mci->proc_ent =create_proc_read_entry (mci->proc_name,0 , proc_mc, - mc_read_proc, (void *) mci); - -if (mci->proc_ent ==NULL ) { +if (create_proc_read_entry (mci->proc_name,0 , proc_mc, + mc_read_proc, (void *) mci) ==NULL ) {printk (KERN_WARNING "MC%d: failed to create proc entry for controller\n" , mci->mc_idx);
Re: [-mm patch] EDAC: remove proc_ent from struct mem_ctl_info
Quoted 5 lines · Adrian Bunk
While fixing a compile error with
CONFIG_PROC_FS=nin the EDAC code, I discovered that theproc_entmember of structmem_ctl_infois only used in a debug printk.Is this patch to remove
proc_entOK?
Looks sane to me.
Quoted 3 lines
Signed-off-by Adrian Bunk <[email protected]>