* 2.6.21-rc4-mm1
@ 2007-03-20 4:56 Andrew Morton
2007-03-20 7:54 ` 2.6.21-rc4-mm1 Michal Piotrowski
` (23 more replies)
0 siblings, 24 replies; 146+ messages in thread
From: Andrew Morton @ 2007-03-20 4:56 UTC (permalink / raw)
To: linux-kernel
Temporarily at
http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
Will appear later at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
- Restored the RSDL CPU scheduler (a new version thereof)
Boilerplate:
- See the `hot-fixes' directory for any important updates to this patchset.
- To fetch an -mm tree using git, use (for example)
git-fetch git://git.kernel.org/pub/scm/linux/kernel/git/smurf/linux-trees.git tag v2.6.16-rc2-mm1
git-checkout -b local-v2.6.16-rc2-mm1 v2.6.16-rc2-mm1
- -mm kernel commit activity can be reviewed by subscribing to the
mm-commits mailing list.
echo "subscribe mm-commits" | mail majordomo@vger.kernel.org
- If you hit a bug in -mm and it is not obvious which patch caused it, it is
most valuable if you can perform a bisection search to identify which patch
introduced the bug. Instructions for this process are at
http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt
But beware that this process takes some time (around ten rebuilds and
reboots), so consider reporting the bug first and if we cannot immediately
identify the faulty patch, then perform the bisection search.
- When reporting bugs, please try to Cc: the relevant maintainer and mailing
list on any email.
- When reporting bugs in this kernel via email, please also rewrite the
email Subject: in some manner to reflect the nature of the bug. Some
developers filter by Subject: when looking for messages to read.
- Occasional snapshots of the -mm lineup are uploaded to
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/ and are announced on
the mm-commits list.
Changes since 2.6.21-rc3-mm1:
origin.patch
git-acpi.patch
git-alsa.patch
git-arm-master.patch
git-arm.patch
git-avr32.patch
git-cifs.patch
git-cpufreq.patch
git-powerpc.patch
git-drm.patch
git-dvb.patch
git-gfs2-nmw.patch
git-hid.patch
git-ia64.patch
git-ieee1394.patch
git-infiniband.patch
git-input.patch
git-kbuild.patch
git-kvm.patch
git-leds.patch
git-libata-all.patch
git-md-accel.patch
git-mmc.patch
git-mtd.patch
git-ubi.patch
git-netdev-all.patch
git-ioat.patch
git-ocfs2.patch
git-parisc.patch
git-selinux.patch
git-pciseg.patch
git-s390.patch
git-sh.patch
git-scsi-misc.patch
git-scsi-rc-fixes.patch
git-unionfs.patch
git-wireless.patch
git-ipwireless_cs.patch
git-gccbug.patch
git trees
-uml-hostfs-fix-double-free.patch
-uml-hostfs-make-hostfs=-option-work-as-a-jail-as-intended.patch
-uml-fix-a-memory-leak-in-the-multicast-driver.patch
-uml-remove-dead-code-about-os_usr1_signal-and-os_usr1_process.patch
-uml-mark-both-consoles-as-con_anytime.patch
-uml-fix-confusion-irq-early-reenabling.patch
-uml-activate_fd-return-enomem-only-when-appropriate.patch
-uml-fix-errno-usage.patch
-x86_64-fix-2618-regression-ptrace_oldsetoptions-should-be-accepted.patch
-bluetooth-fix-socket-locking-in-hci_sock_dev_event.patch
-add-epoll-compat_-code-to-fs-compatc.patch
-check_partition-fix-error-check.patch
-uml-arch_prctl-should-set-thread-fs.patch
-connector-bugfix-for-cn_call_callback.patch
-26-altix-console-fix-for-config_debug_shirq-usage.patch
-ecryptfs-nested-locking-annotation.patch
-swsusp-disable-nonboot-cpus-before-entering-platform-suspend.patch
-paravirt-build-fixes.patch
-acpi-disabled-due-to-dmi-failure-or-blacklisted-year-should-be-noted-as-is-done-with-other-acpi-blacklisting.patch
-git-alsa-oops-fix.patch
-avr32-dma-mappingh.patch
-gregkh-driver-device-symlink.patch
-gregkh-driver-platform-reorder-platform_device_del.patch
-gregkh-driver-remove-devfs-from-maintainers.patch
-gregkh-driver-driver-core-export-device_rename.patch
-gregkh-driver-uio-irq.patch
-scheduled-removal-of-sa_xxx-interrupt-flags-fixups-4.patch
-make-drivers-char-drm-drm_vmcdrm_io_prot-static.patch
-fix-saa7146_clipping_mem-size.patch
-drivers-media-video-cpia_ppc-dont-use-_work_nar.patch
-dvb-core-fix-several-locking-related-problems.patch
-saa7134-fix-modules=n-compilation.patch
-ivtv-warning-fix.patch
-jdelvare-i2c-i2c-03-use-i2c_adapterdevparent-for-messages.patch
-jdelvare-i2c-i2c-i801-restore-initial-state.patch
-jdelvare-i2c-ds1374-check-for-workqueue-creation.patch
-crash-on-evdev-disconnect.patch
-expose-set_mode-method-so-it-can-be-wrapped.patch
-ata_piix-remove-ugly-layering-violation.patch
-pata_cmd640-multiple-updates.patch
-ide-cmd64x-fix-recovery-time-calculation-take2.patch
-mtd-maps-ck804xromc-pci_module_init-to-pci_register_driver.patch
-mtd-chips-oops-in-cfi_amdstd_sync.patch
-mtd-esb2-check-for-closed-rom-window.patch
-dilnetpc-fix-warning.patch
-mtd-correct-misspelled-preprocessor-variable.patch
-git-netdev-all-ipw2200-fix.patch
-mv643xx-ethernet-driver-irq-registration-fix.patch
-via-rhine-set-avoid_d3-for-broken-bioses.patch
-netxen-fix-warnings.patch
-e1000-fix-be-ready-for-incoming-irq-at-pci_request_irq.patch
-e1000-fix-firmware-handover-bits.patch
-e1000-fix-stop-raw-interrupts-disabled-nag-from-rt.patch
-tulip-fix-shutdown-dma-irq-race.patch
-tulip-fix-for-64-bit-mips.patch
-tulip-natsemi-dp83840a-phy-fix.patch
-nfs-fix-congestion-control-v4.patch
-nfs-nfs_getattr-cant-call-nfs_sync_mapping_range-for-non-regular-files.patch
-gregkh-pci-pci-allow-multiple-calls-to-pcim_pin_device.patch
-gregkh-pci-pcie-fix-section-mismatch-warning.patch
-gregkh-pci-pci-aer-fix-section-mismatch-warning.patch
-gregkh-pci-pci-fix-section-mismatch-warning.patch
-scatterlisth-needs-typesh.patch
-cleanup-the-includes-of-linux-pcih.patch
-gregkh-usb-usb-at91_udc-fix-more-modpost-bogosity.patch
-gregkh-usb-usb-storage-removed-duplicate-supertop-unusual_dev-entry.patch
-gregkh-usb-usb-storage-nokia-6288-unusual_devs-entry.patch
-gregkh-usb-usb-goku_udc-remove-crude-cache-coherency-code.patch
-gregkh-usb-usb-set-the-correct-interval-for-interrupt-urbs.patch
-gregkh-usb-uhci-fix-port-resume-problem.patch
-gregkh-usb-usb-ratelimit-debounce-error-messages.patch
-gregkh-usb-usb-kill-dead-code-from-hubc.patch
-gregkh-usb-usb-new-device-ids-for-cp2101-driver.patch
-gregkh-usb-usb-add-ql355p-power-supply-ids-to-fdti_sio.patch
-gregkh-usb-usb-add-additional-pids-in-ftdi_sio.patch
-gregkh-usb-usb-serial-fix-shutdown-device_unregister-order.patch
-gregkh-usb-usb-ftdi_sio-use-port_probe-port_remove-thereby-fixing-access-to-the-latency_timer.patch
-gregkh-usb-usb-rts-dtr-signal-patch-for-airprime-driver.patch
-gregkh-usb-usb-fix-usb-serial-device-naming-bug.patch
-gregkh-usb-usb-further-fix-for-usb-serial.patch
-gregkh-usb-usb-ipaqc-additional-devices.patch
-gregkh-usb-usbnet-dm9501-add-corega-fether-usb-txc-support.patch
-usbatm-create-sysfs-link-device-from-atm-class-device.patch
-usb-elan-ftdi-check-for-workqueue-creation-v2.patch
-cxacru-export-detailed-device-info-through-sysfs-updated.patch
-maintainers-add-myself-for-cxacru-in-drivers-usb-atm.patch
-x86_64-mm-defconfig-update.patch
-x86_64-mm-i386-defconfig-update.patch
-x86_64-wire-up-compat-sched_rr_get_interval2.patch
-x86_64-fix-section-mismatch-warnings.patch
Merged into mainline or a subsystem tree
+return-eperm-not-echild-on-security_task_wait-failure.patch
+splice-dont-steal.patch
+splice-dont-readpage.patch
+shmem-fix-bug-in-shmem_writepage.patch
+shmem-dont-release-lock-for-hole-punching.patch
Possible 2.6.21 queue.
-macintosh-mangle-caps-lock-events-on-adb-keyboards.patch
Dropped
+git-alsa-fixup.patch
Fix rejects in git-alsa.
+drivers-char-agp-convert-to-generic-boolean.patch
AGP cleanup
+git-arm-master.patch
New ARM tree
+remove-unused-header-file-arch-arm-mach-s3c2410-basth.patch
Cleanup
+cifs-remove-unneeded-checks.patch
CIFS cleanup
+remove-unused-header-file-arch-ppc-syslib-cpc710h.patch
+remove-unused-header-file-arch-powerpc-platforms-83xx-mpc834x_itxh.patch
+powerpc-fix-breakage-caused-by-72486f1f8f0a2bc828b9d30cf4690cf2dd6807fc.patch
+ibmebus-uevent-support.patch
+ocotea-board-ntpd-complains-that-the-frequency-error-exceeds-the-tolerance.patch
ppc stuff
+gregkh-driver-driver-core-fix-device_add-error-path.patch
+gregkh-driver-driver-core-fix-namespace-issue-with-devices-assigned-to-classes.patch
+gregkh-driver-dev_printk-and-new-style-class-devices.patch
+gregkh-driver-driver-core-use-attribute-groups-in-struct-device_type.patch
+gregkh-driver-named-device_type.patch
+gregkh-driver-uio-hilscher-cif-card-driver.patch
Driver tree updates
+kobject-kobject_shadow_add-cleanup.patch
+driver-core-handles-kobject_uevent-failure-while-device_add.patch
+driver-core-handle-sysfs_op-failure-while-device_add.patch
Driver things
+jdelvare-i2c-i2c-i801-restore-initial-state.patch
+jdelvare-i2c-ds1374-check-for-workqueue-creation.patch
+jdelvare-i2c-i2c-09-i2c-class-attribute-cleanup.patch
+jdelvare-i2c-i2c-10-rename-dev_to_i2c_adapter.patch
+jdelvare-i2c-scx200_acb-fix-pci-device-reference-count.patch
+jdelvare-i2c-i2c-parport-fix-race-on-unload.patch
+jdelvare-i2c-i2c-parport-light-to-platform-driver.patch
+jdelvare-i2c-i2c-elektor-to-isa-driver.patch
+jdelvare-i2c-i2c-pca-isa-to-isa-driver.patch
+jdelvare-i2c-i2c-algo-bit-document-udelay.patch
+jdelvare-i2c-i2c-01-i2c-stack-can-probe.patch
+jdelvare-i2c-i2c-02-i2c-stack-can-remove.patch
+jdelvare-i2c-i2c-03-i2c-document-probe-and-remove.patch
+jdelvare-i2c-i2c-04-i2c_board_info-and-i2c_new_device.patch
+jdelvare-i2c-i2c-05-i2c_add_numbered_adapter.patch
+jdelvare-i2c-i2c-06-export_symbol-cleanup.patch
+jdelvare-i2c-i2c-07-i2c_bit_add_numbered_bus.patch
+jdelvare-i2c-i2c-isa-exports-only-to-i2c-isa.patch
+jdelvare-i2c-i2c-del-driver-returns-void.patch
+jdelvare-i2c-i2c-rpx-will-be-removed.patch
I2C tree updates
+jdelvare-hwmon-hwmon-w83627hf-cleanups.patch
+jdelvare-hwmon-hwmon-w83627hf-to-platform-driver.patch
+jdelvare-hwmon-hwmon-sysfs-interface-add-fan-target.patch
+jdelvare-hwmon-hwmon-smsc47m1-to-platform-driver.patch
+jdelvare-hwmon-hwmon-smsc47m1-use-drvname-consistently.patch
+jdelvare-hwmon-hwmon-max6650-new-driver.patch
+jdelvare-hwmon-hwmon-lm78-to-platform-driver.patch
+jdelvare-hwmon-hwmon-lm78-less-client-centric.patch
+jdelvare-hwmon-hwmon-lm78-use-dynamic-attributes.patch
+jdelvare-hwmon-hwmon-lm75-use-dynamic-attributes.patch
hwmon tree updates
-fix-locking-in-mousedev.patch
Dropped - git-input changes broke it.
+ata_generic-remove-all-the-crud-again-and-use-cable.patch
+pata_ali-remove-all-the-crap-again-and-switch-to.patch
+pata_amd-remove-all-the-crud-and-restore-the-cable-detect.patch
+pata_cs5535-re-remove-all-the-crap-and-switch-to-the-cable.patch
+pata_cypress-re-remove-all-the-crap-and-switch-back-to.patch
+pata_netcell-re-remove-all-the-crud.patch
+pata_qdi-restore-cable-detect.patch
+pata_sl82c105-restore-cable-detect-method.patch
+pata_winbond-restore-cable-method.patch
+libata-acpi-add-infrastructure-for-drivers-to-use.patch
+pata_optidma-rework-for-cable-detect-and-to-remove.patch
+pata_acpi-restore-driver.patch
+ata-ncq-is-broken-on-maxtor-6l250s0.patch
pata/sata things
+ide-ide-fix-pio-setup-on-resume-for-atapi.patch
+ide-it821x-pio-mode-setup-fixes.patch
+ide-siimage-swdma-mask-fix.patch
+ide-ide-cris-fix-speedproc-and-swdma-mask.patch
+ide-ide-dma-off-quietly-fix.patch
+ide-ide-no-mdma-udma-sharing-filter.patch
+ide-ide-tune-dma-2.patch
+ide-cs5530-sc1200-dma-cleanup.patch
+ide-cs5530-sc1200-add-speedproc.patch
+ide-sl82c105-add-speedproc.patch
+ide-ide-dma-enable.patch
+ide-ide-check-dma-words-validity.patch
+ide-ide-remove-ide-use-dma.patch
IDE tree updates
+revert-rm-pointless-dmaengine-exports.patch
Revert a merged patch to make git-md-accel.patch easier to apply.
-git-md-accel-fixup.patch
Unneeded
+git-md-accel-fix.patch
Fix git-md-accel tree
-remove-fs-jffs2-ioctlc.patch
Dropped
+mmc-consolidate-voltage-definitions.patch
+mmc-fix-handling-of-low-voltage-cards.patch
+remove-mmc_deselect_cards.patch
MMC things
+mtd-pmc-msp71xx-flash-rootfs-mappings.patch
+jffs2-delete-everything-related-to-obsolete-jffs2_proc.patch
+romfs-printk-format-warnings.patch
MTD stuff
+baycom_ser_fdx-also-allow-i-o-ports-=-0x1000-and-enhanced.patch
+remove-unused-header-file-drivers-net-skfp-h-lnkstath.patch
+tulip-fix-shutdown-dma-irq-race.patch
+sun3-3x-lance-trivial-fix-improved.patch
+remove-unused-header-file-drivers-net-wan-lmc-lmc_mediah.patch
+smc-superio-chip-lpc47n227-not-identified-properly.patch
netdev things
+pcmcia-delete-obsolete-pcmcia_ioctl-feature.patch
PCMCIA cleanup
+gregkh-pci-pciehp-event-handling-rework.patch
+gregkh-pci-pciehp-adapt-to-device-driver-model.patch
+gregkh-pci-pci-scatterlisth-needs-typesh.patch
+gregkh-pci-pci-cleanup-the-includes-of-linux-pcih.patch
PCI tree updates
-resurrect-sdev.patch
-bug-in-gdthc-crashing-machine.patch
Dropped
+make-elv_register-output-atomic.patch
Block cleanup
+unionfs-sioq-not-__exit.patch
unionfs fixlet
+gregkh-usb-usb-fix-usb-serial-regression.patch
+gregkh-usb-usb-two-more-device-ids-for-dm9601-usbnet-driver.patch
+gregkh-usb-usb-razr-v3i-unusual_devs.patch
+gregkh-usb-usb-necessary-update-for-mos7720-driver.patch
+gregkh-usb-airprime-usb-id-for-novatel-ev620-mini-pci-e-card.patch
+gregkh-usb-ub-bind-to-first-endpoint-not-to-last.patch
+gregkh-usb-libusual-change-block-scope-variable-to-function-scope.patch
+gregkh-usb-usbcore-move-usb_autosuspend_work.patch
+gregkh-usb-usb-unnecessary-gfp_atomic-in-mos7720-driver.patch
+gregkh-usb-usbatm-create-sysfs-link-device-from-atm-class-device-to-usb-interface.patch
+gregkh-usb-usb-cxacru-export-detailed-device-info-through-sysfs.patch
+gregkh-usb-usb-maintainers-cxacru.patch
+gregkh-usb-usb-fix-race-in-hcd-removal.patch
+gregkh-usb-ehci-fsl-change-si_ctrl-pri_ctrl-register-offsets-according-to-errata.patch
+gregkh-usb-mos7720-update.patch
+gregkh-usb-usb-help-text-for-mos-7720-driver.patch
+gregkh-usb-usb-fix-gadget-serial-response-on-usb_cdc_req_set_line_coding.patch
+gregkh-usb-usb-separate-autosuspend-from-external-suspend.patch
+gregkh-usb-usb-allow-autosuspend-delay-to-equal-0.patch
+gregkh-usb-ehci-add-delay-to-bus_resume-before-accessing-ports.patch
+gregkh-usb-usb-usb_serial_driver-insufficient-for-clean-disconnect-handling.patch
USB tree updates
+usb-serial-io_edgeport-convert-to-generic-boolean.patch
+usb-serial-whiteheat-convert-to-generic-boolean.patch
USB stuff
+hack-to-make-wireless-work.patch
The wireless tree seems to have broken the firmware loader. Work around it.
+i386-x86_64-early_printkc-make-simnow_init-static.patch
+make-arch-i386-kernel-vmicvmi_pmd_clear-static.patch
+i386-fix-gdts-number-of-quadwords-in.patch
+i386-fix-usage-of-mtune-when-x86_generic=y-or-config_mcore2=y.patch
+x86_64-configurable-fake-numa-node-sizes-fix.patch
+lguest-the-host-code-lgko-cleanup-allocate-separate-pages-for-switcher-code.patch
+lguest-the-host-code-lgko-cleanup-clean-up-regs-save-restore.patch
+lguest-the-host-code-lgko-pin-stack-page-optimization.patch
+lguest-use-read-only-pages-rather-than-segments-to-protect-high-mapped-switcher.patch
+lguest-optimize-away-copy-in-and-out-of-per-cpu-guest-pages.patch
+lguest-dont-crash-host-on-nmi.patch
+lguest-trivial-guest-block-driver-lguest-block-device-speedup.patch
+lguest-documentatation-and-example-launcher-bridging-support-in-example-code.patch
+lguest-documentatation-and-example-launcher-bridging-support-in-example-codelguest-documentation-fixes.patch
+x86_64-remove-duplicated-code-for-reading-control-registers.patch
+introduce-load_tls-to-the-for-loop.patch
+remove-unused-set_seg_base.patch
+clarify-config_reorder-explanation.patch
+mm-inconsistent-use-of-node-ids.patch
+dma_ops-as-const.patch
+allow-i386-crash-kernels-to-handle-x86_64-dumps.patch
+allow-i386-crash-kernels-to-handle-x86_64-dumps-fix.patch
+prevent-acpi-quirk-warning-mass-spamming-in-logs.patch
+prevent-acpi-quirk-warning-mass-spamming-in-logs-tidy.patch
x86/x86_64 updates
-xfs-use-xfs_get_buf_noaddr-for-iclogs.patch
-xfs-stop-using-kmalloc-in-xfs_buf_get_noaddr.patch
Dropped - they need updating.
+uhci-fix-problem-caused-by-lack-of-terminating-qh.patch
USB fix
+move-free-pages-between-lists-on-steal-fix-2.patch
+move-free-pages-between-lists-on-steal-avoid-unsafe-use-of-struct-pages-in-move_freepages-when-config_holes_in_zone-is-set.patch
Fix move-free-pages-between-lists-on-steal.atch some more
+fix-corruption-of-memmap-on-ia64-sparsemem-when-mem_section-is-not-a-power-of-2.patch
ia64 fix
-mm-debug-check-for-the-fault-vs-invalidate-race.patch
-mm-debug-check-for-the-fault-vs-invalidate-race-tidy.patch
Drop this debug patch: the fault-vs-invalidate patches cause the BUG_ON() to
trigger.
+mm-merge-nopfn-into-fault-fix.patch
Fix mm-merge-nopfn-into-fault.patch
+lumpy-reclaim-v4.patch
+lumpy-back-out-removal-of-active-check-in-isolate_lru_pages.patch
+lumpy-only-count-taken-pages-as-scanned.patch
Lumpy reclaim came back
+mm-filemapc-fix-mark_page_accessed-logic.patch
Tighten use-once logic
+bias-the-location-of-pages-freed-for-min_free_kbytes-in-the-same-max_order_nr_pages-blocks.patch
+bias-the-location-of-pages-freed-for-min_free_kbytes-in-the-same-max_order_nr_pages-blocks-tidy.patch
More page allocator work
+blackfin-arch-balance-parenthesis-in-macros.patch
blackfin fix
+remove-unused-header-file-arch-m68k-atari-atasoundh.patch
m68k cleanup
+remove-unused-header-file-drivers-serial-crisv10h.patch
+cris-check-for-memory-allocation.patch
Cris updates
+remove-unused-header-file-arch-um-kernel-tt-include-mode_kern-tth.patch
UML cleanup
+ext3-dirindex-error-pointer-issues-fix.patch
Fix ext3-dirindex-error-pointer-issues.patch
+fix-race-between-proc_readdir-and-remove_proc_entry.patch
+proc-remove-pathetic-deleted-warn_on.patch
Fiddle with /proc races some more
+complain-about-missing-system-calls.patch
+complain-about-missing-system-calls-update.patch
+proc-maps-protection.patch
+proc-maps-protection-fix.patch
+proc-maps-protection-tidy.patch
+proc-maps-protection-fix-2.patch
+remove-unused-header-file-include-linux-elfnoteh.patch
+remove-unused-header-file-drivers-message-i2o-i2o_lanh.patch
+remove-unused-header-file-drivers-char-digih.patch
+array_size-check-for-type.patch
+drivers-char-synclinkc-check-kmalloc-return-value.patch
+procfs-reorder-struct-pid_dentry-to-save-space-on-64bit-archs-and-constify-them.patch
+vfs-delay-the-dentry-name-generation-on-sockets-and.patch
+tty-i386-x86_64-arbitary-speed-support.patch
+kprobes-make-kprobesymbol_name-const.patch
+fix-cycladesh-for-x86_64-and-probably-others.patch
+fix-cycladesh-for-x86_64-and-probably-others-fix.patch
+cyclades-remove-custom-types.patch
+splice-partial-write-handling-fix.patch
+small-fixes-for-jsm-driver.patch
+jsm-driver-fix-for-linuxpps-support.patch
+serial-allocate-minor-device-numbers-for.patch
+as-fix-antic_expire-check.patch
+rtc-add-rtc-rs5c313-driver.patch
+rtc-add-rtc-rs5c313-driver-tidy.patch
+rtc-add-rtc-rs5c313-driver-is-busted.patch
+rtc-add-rtc-class-driver-for-the-maxim-max6900.patch
+fix-rmmod-read-write-races-in-proc-entries.patch
+getrusage-fill-ru_inblock-and-ru_oublock-fields-if-possible.patch
+futex-restartable-futex_wait.patch
+futex-restartable-futex_wait-fix.patch
+proc-oom_score-oops-re-badness.patch
+fixes-and-cleanups-for-earlyprintk-aka-boot-console.patch
+tty-remove-unnecessary-export-of-proc_clear_tty.patch
+tty-simplify-calling-of-put_pid.patch
+tty-introduce-no_tty-and-use-it-in-selinux.patch
+tty-in-tiocsctty-when-we-steal-a-tty-hang-it-up.patch
+reiserfs-proc-support-requires-proc_fs.patch
Misc
+make-drivers-isdn-capi-capiutilccdebbuf_alloc-static.patch
+drivers-isdn-hardware-eicon-remove-unused-header-files.patch
ISDN updates
+lists-add-list-splice-tail.patch
+sched-remove-sleepavg-from-proc.patch
+sched-remove-noninteractive-flag.patch
+sched-dont-renice-kernel-threads.patch
+sched-implement-rsdl-cpu-scheduler.patch
+sched-document-rsdl-cpu-scheduler.patch
RSDL CPU scheduler
-rcu-split-classic-rcu.patch
-rcu-softirq-for-rcu.patch
-rcu-fix-barriers.patch
-rcu-preemptible-rcu.patch
-rcu-debug-trace-for-rcu.patch
Dropped. It's too early to merge preemptible RCU, and the ther patches had
dependencies on it.
-utrace-prep.patch
+proc-maps-protection-vs-utrace.patch
+utrace-utrace-tracehook-um.patch
-revert-utrace-prep-2.patch
+avr32-implement-utrace-support.patch
+utrace-printk-borkage.patch
+ptrace-needs-proc_fs.patch
utrace updates
+some-grammatical-fixups-and-additions-to-atomich-kernel-doc.patch
Cleanup
+udf-possible-null-pointer-dereference-while-load_partition.patch
UDF fix
+add-ability-to-keep-track-of-callers-of-symbol_getput.patch
+add-ability-to-keep-track-of-callers-of-symbol_getput-update.patch
+update-mtd-use-of-symbol_getput.patch
+update-dvb-use-of-symbol_getput.patch
Fiddle with symbol_get()
+attach_pid-with-struct-pid-parameter.patch
+statically-initialize-struct-pid-for-swapper.patch
+explicitly-set-pgid-and-sid-of-init-process.patch
+use-struct-pid-parameter-in-copy_process.patch
+# remove-the-likelypid-check-in-copy_process.patch: Oleg issues
+remove-the-likelypid-check-in-copy_process.patch
+use-task_pgrp-task_session-in-copy_process.patch
+kill-unused-sesssion-and-group-values-in-rocket-driver.patch
+fix-some-coding-style-errors-in-autofs.patch
+replace-pid_t-in-autofs-with-struct-pid-reference.patch
PID management updates
+revoke-special-mmap-handling.patch
+revoke-special-mmap-handling-vs-fault-vs-invalidate.patch
+revoke-core-code.patch
+revoke-core-code-misc-fixes.patch
+revoke-core-code-fix-shared-mapping-revoke.patch
+revoke-core-code-move-magic.patch
+revoke-support-for-ext2-and-ext3.patch
+revoke-add-documentation.patch
+revoke-wire-up-i386-system-calls.patch
revoke() syscall
+readahead-state-based-method-check-node-id.patch
+readahead-state-based-method-decouple-readahead_ratio-from-growth_limit.patch
+readahead-state-based-method-cancel-lookahead-gracefully.patch
+readahead-thrashing-recovery-method-check-unbalanced-aging.patch
+readahead-thrashing-recovery-method-refill-holes.patch
+readahead-call-scheme-cleanup.patch
+readahead-call-scheme-catch-thrashing-on-lookahead-time.patch
+readahead-remove-parameter-ra_max-from-thrashing_recovery_readahead.patch
+readahead-remove-parameter-ra_max-from-adjust_rala.patch
+readahead-state-based-method-protect-against-tiny-size.patch
+readahead-rename-state_based_readahead-to-clock_based_readahead.patch
+readahead-account-i-o-block-times-for-stock-readahead.patch
+readahead-rescue_pages-updates.patch
+readahead-remove-noaction-shrink-events.patch
Update the readahead patches in -mm.
+remove-unused-header-file-drivers-video-riva-nv4refh.patch
+fbdev-avoid-vertical-overflow-when-making-space-for-the-logo.patch
+fbdev-fb_do_show_logo-updates.patch
+fbdev-correct-image-offsets-when-rotating-logo.patch
+radeonfb-add-support-for-radeon-xpress-200m.patch
fbdev updates
+statistics-infrastructure-simplify-statistics-debugfs-write-function.patch
Update statistics patches in -mm.
-ia64-enable-config_debug_spinlock_sleep.patch
-msi-debug-code.patch
Dropped.
All 934 patches:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/patch-list
^ permalink raw reply [flat|nested] 146+ messages in thread* Re: 2.6.21-rc4-mm1 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton @ 2007-03-20 7:54 ` Michal Piotrowski 2007-03-20 9:45 ` 2.6.21-rc4-mm1 Andy Whitcroft ` (22 subsequent siblings) 23 siblings, 0 replies; 146+ messages in thread From: Michal Piotrowski @ 2007-03-20 7:54 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel Andrew Morton napisał(a): > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > Some new details about http://www.ussg.iu.edu/hypermail/linux/kernel/0703.2/1367.html I can reproduce it by running this on AutoTest for profiler in ('oprofile', ): try: print "Testing profiler %s ..." % profiler job.profilers.add(profiler) job.run_test('aiostress',) job.profilers.delete(profiler) except: print "Test of profiler %s failed" % profiler raise I guess that oprofile triggers it. BUG: using smp_processor_id() in preemptible [00000001] code: mount/4934 caller is avail_to_resrv_perfctr_nmi_bit+0x2b/0x43 [<c0105256>] show_trace_log_lvl+0x1a/0x2f [<c010597b>] show_trace+0x12/0x14 [<c0105a3d>] dump_stack+0x16/0x18 [<c0212f43>] debug_smp_processor_id+0xb3/0xc8 [<c0116a26>] avail_to_resrv_perfctr_nmi_bit+0x2b/0x43 [<fdc829b9>] nmi_create_files+0x2a/0x10e [oprofile] [<fdc81f52>] oprofile_create_files+0xe6/0xec [oprofile] [<fdc82157>] oprofilefs_fill_super+0x78/0x7e [oprofile] [<c018296e>] get_sb_single+0x59/0x9f [<fdc8208f>] oprofilefs_get_sb+0x1c/0x1e [oprofile] [<c01823d2>] vfs_kern_mount+0x81/0xf1 [<c0182492>] do_kern_mount+0x38/0xde [<c01962b1>] do_mount+0x605/0x693 [<c01963bf>] sys_mount+0x80/0xb5 [<c0104270>] syscall_call+0x7/0xb ======================= l *avail_to_resrv_perfctr_nmi_bit+0x2b/0x43 0xc01169fb is in avail_to_resrv_perfctr_nmi_bit (/mnt/md0/devel/linux-mm/arch/i386/kernel/nmi.c:124). 119 return 0; 120 } 121 122 /* checks for a bit availability (hack for oprofile) */ 123 int avail_to_resrv_perfctr_nmi_bit(unsigned int counter) 124 { 125 BUG_ON(counter > NMI_MAX_COUNTER_BITS); 126 127 return (!test_bit(counter, &__get_cpu_var(perfctr_nmi_owner))); 128 } BUG: using smp_processor_id() in preemptible [00000001] code: mount/4934 caller is avail_to_resrv_perfctr_nmi_bit+0x2b/0x43 [<c0105256>] show_trace_log_lvl+0x1a/0x2f [<c010597b>] show_trace+0x12/0x14 [<c0105a3d>] dump_stack+0x16/0x18 [<c0212f43>] debug_smp_processor_id+0xb3/0xc8 [<c0116a26>] avail_to_resrv_perfctr_nmi_bit+0x2b/0x43 [<fdc829b9>] nmi_create_files+0x2a/0x10e [oprofile] [<fdc81f52>] oprofile_create_files+0xe6/0xec [oprofile] [<fdc82157>] oprofilefs_fill_super+0x78/0x7e [oprofile] [<c018296e>] get_sb_single+0x59/0x9f [<fdc8208f>] oprofilefs_get_sb+0x1c/0x1e [oprofile] [<c01823d2>] vfs_kern_mount+0x81/0xf1 [<c0182492>] do_kern_mount+0x38/0xde [<c01962b1>] do_mount+0x605/0x693 [<c01963bf>] sys_mount+0x80/0xb5 [<c0104270>] syscall_call+0x7/0xb ======================= BUG: using smp_processor_id() in preemptible [00000001] code: mount/4934 caller is avail_to_resrv_perfctr_nmi_bit+0x2b/0x43 [<c0105256>] show_trace_log_lvl+0x1a/0x2f [<c010597b>] show_trace+0x12/0x14 [<c0105a3d>] dump_stack+0x16/0x18 [<c0212f43>] debug_smp_processor_id+0xb3/0xc8 [<c0116a26>] avail_to_resrv_perfctr_nmi_bit+0x2b/0x43 [<fdc829b9>] nmi_create_files+0x2a/0x10e [oprofile] [<fdc81f52>] oprofile_create_files+0xe6/0xec [oprofile] [<fdc82157>] oprofilefs_fill_super+0x78/0x7e [oprofile] [<c018296e>] get_sb_single+0x59/0x9f [<fdc8208f>] oprofilefs_get_sb+0x1c/0x1e [oprofile] [<c01823d2>] vfs_kern_mount+0x81/0xf1 [<c0182492>] do_kern_mount+0x38/0xde [<c01962b1>] do_mount+0x605/0x693 [<c01963bf>] sys_mount+0x80/0xb5 [<c0104270>] syscall_call+0x7/0xb ======================= BUG: using smp_processor_id() in preemptible [00000001] code: mount/4934 caller is avail_to_resrv_perfctr_nmi_bit+0x2b/0x43 [<c0105256>] show_trace_log_lvl+0x1a/0x2f [<c010597b>] show_trace+0x12/0x14 [<c0105a3d>] dump_stack+0x16/0x18 [<c0212f43>] debug_smp_processor_id+0xb3/0xc8 [<c0116a26>] avail_to_resrv_perfctr_nmi_bit+0x2b/0x43 [<fdc829b9>] nmi_create_files+0x2a/0x10e [oprofile] [<fdc81f52>] oprofile_create_files+0xe6/0xec [oprofile] [<fdc82157>] oprofilefs_fill_super+0x78/0x7e [oprofile] [<c018296e>] get_sb_single+0x59/0x9f [<fdc8208f>] oprofilefs_get_sb+0x1c/0x1e [oprofile] [<c01823d2>] vfs_kern_mount+0x81/0xf1 [<c0182492>] do_kern_mount+0x38/0xde [<c01962b1>] do_mount+0x605/0x693 [<c01963bf>] sys_mount+0x80/0xb5 [<c0104270>] syscall_call+0x7/0xb ======================= SELinux: initialized (dev oprofilefs, type oprofilefs), uses genfs_contexts ================================= [ INFO: inconsistent lock state ] 2.6.21-rc4-mm1 #5 --------------------------------- inconsistent {hardirq-on-W} -> {in-hardirq-W} usage. init/1 [HC1[1]:SC0[0]:HE0:SE1] takes: (oprofilefs_lock){+-..}, at: [<fdc82b6e>] nmi_cpu_setup+0x15/0x4f [oprofile] {hardirq-on-W} state was registered at: [<c0140c15>] __lock_acquire+0x4e8/0xceb [<c0141491>] lock_acquire+0x79/0x93 [<c033eb3f>] _spin_lock+0x35/0x42 [<fdc82347>] oprofilefs_ulong_from_user+0x4e/0x74 [oprofile] [<fdc81fc7>] depth_write+0x27/0x43 [oprofile] [<c0180afa>] vfs_write+0xd1/0x15a [<c018112a>] sys_write+0x3d/0x72 [<c0104270>] syscall_call+0x7/0xb [<ffffffff>] 0xffffffff irq event stamp: 1022800 hardirqs last enabled at (1022799): [<c01042b8>] restore_nocheck+0x12/0x15 hardirqs last disabled at (1022800): [<c0104cf1>] call_function_interrupt+0x29/0x38 softirqs last enabled at (1022784): [<c0128eb4>] __do_softirq+0xe4/0xea softirqs last disabled at (1022779): [<c0128ef3>] do_softirq+0x39/0x55 l *0xc01042b8 0xc01042b8 is at include2/asm/bitops.h:246. 241 static int test_bit(int nr, const volatile void * addr); 242 #endif 243 244 static __always_inline int constant_test_bit(int nr, const volatile unsigned long *addr) 245 { 246 return ((1UL << (nr & 31)) & (addr[nr >> 5])) != 0; 247 } 248 249 static inline int variable_test_bit(int nr, const volatile unsigned long * addr) 250 { l *0xc0104cf1 0xc0104cf1 is at include2/asm/bitops.h:246. 241 static int test_bit(int nr, const volatile void * addr); 242 #endif 243 244 static __always_inline int constant_test_bit(int nr, const volatile unsigned long *addr) 245 { 246 return ((1UL << (nr & 31)) & (addr[nr >> 5])) != 0; 247 } 248 249 static inline int variable_test_bit(int nr, const volatile unsigned long * addr) 250 { l *0xc0128eb4 0xc0128eb4 is in __do_softirq (/mnt/md0/devel/linux-mm/kernel/softirq.c:252). 247 248 trace_softirq_exit(); 249 250 account_system_vtime(current); 251 _local_bh_enable(); 252 } 253 254 #ifndef __ARCH_HAS_DO_SOFTIRQ 255 256 asmlinkage void do_softirq(void) l *0xc0128ef3 0xc0128ef3 is in do_softirq (/mnt/md0/devel/linux-mm/kernel/softirq.c:271). 266 pending = local_softirq_pending(); 267 268 if (pending) 269 __do_softirq(); 270 271 local_irq_restore(flags); 272 } 273 274 EXPORT_SYMBOL(do_softirq); 275 other info that might help us debug this: 2 locks held by init/1: #0: (tasklist_lock){..??}, at: [<c01261b6>] do_wait+0x54/0xba4 #1: (policy_rwlock){..??}, at: [<c01ef326>] security_compute_av+0x4f/0xbf l *0xc01261b6 0xc01261b6 is in do_wait (include2/asm/current.h:11). 6 7 struct task_struct; 8 9 static __always_inline struct task_struct *get_current(void) 10 { 11 return read_pda(pcurrent); 12 } 13 14 #define current get_current() 15 l *0xc01ef326 0xc01ef326 is in security_compute_av (/mnt/md0/devel/linux-mm/security/selinux/ss/services.c:527). 522 return 0; 523 } 524 525 POLICY_RDLOCK; 526 527 scontext = sidtab_search(&sidtab, ssid); 528 if (!scontext) { 529 printk(KERN_ERR "security_compute_av: unrecognized SID %d\n", 530 ssid); 531 rc = -EINVAL; stack backtrace: [<c0105256>] show_trace_log_lvl+0x1a/0x2f [<c010597b>] show_trace+0x12/0x14 [<c0105a3d>] dump_stack+0x16/0x18 [<c013f327>] print_usage_bug+0x140/0x14a [<c013fbbf>] mark_lock+0xc9/0x510 [<c0140b86>] __lock_acquire+0x459/0xceb [<c0141491>] lock_acquire+0x79/0x93 [<c033eb3f>] _spin_lock+0x35/0x42 [<fdc82b6e>] nmi_cpu_setup+0x15/0x4f [oprofile] [<c0113b63>] smp_call_function_interrupt+0x3a/0x56 [<c0104cfb>] call_function_interrupt+0x33/0x38 [<c01ef380>] security_compute_av+0xa9/0xbf [<c01e2649>] avc_has_perm_noaudit+0x1cf/0x490 [<c01e34da>] avc_has_perm+0x28/0x58 [<c01e3cd7>] task_has_perm+0x2d/0x2f [<c01e6e74>] selinux_task_wait+0x2f/0x31 [<c0126295>] do_wait+0x133/0xba4 [<c0126d36>] sys_wait4+0x30/0x32 [<c0126d5f>] sys_waitpid+0x27/0x29 [<c01041e6>] sysenter_past_esp+0x5f/0x99 ======================= http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.21-rc4-mm1/mm-dmesg http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.21-rc4-mm1/mm-config Regards, Michal -- Michal K. K. Piotrowski LTG - Linux Testers Group (PL) (http://www.stardust.webpages.pl/ltg/) LTG - Linux Testers Group (EN) (http://www.stardust.webpages.pl/linux_testers_group_en/) ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton 2007-03-20 7:54 ` 2.6.21-rc4-mm1 Michal Piotrowski @ 2007-03-20 9:45 ` Andy Whitcroft 2007-03-22 8:41 ` 2.6.21-rc4-mm1 Andy Whitcroft 2007-03-20 10:52 ` 2.6.21-rc4-mm1 [PATCH] init/missing_syscalls.h fix Stephane Jourdois ` (21 subsequent siblings) 23 siblings, 1 reply; 146+ messages in thread From: Andy Whitcroft @ 2007-03-20 9:45 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel, Steve Fox, Martin J. Bligh, Con Kolivas Andrew Morton wrote: > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > Will appear later at > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > > > [All of the below is from the pre hot-fix runs. The very few results which are in for the hot-fix runs seem worse if anything. :( All results should be out on TKO.] > - Restored the RSDL CPU scheduler (a new version thereof) Unsure if the above is the culprit but there seems to be a smattering of BUG's in kernbench from the schedular on several systems, and panics which do not fully dump out. elm3b239 is about 2/4 kernbench being the test in progress when we blammo in both failed tests, elm3b234 doesn't boot at all. >From elm3b239: ------------[ cut here ]------------ kernel BUG at kernel/sched.c:3505! invalid opcode: 0000 [1] SMP last sysfs file: devices/pci0000:00/0000:00:00.0/irq CPU 19 Modules linked in: loop dm_mod md_mod sg Pid: 59, comm: migration/19 Not tainted 2.6.21-rc4-mm1-autokern1 #1 RIP: 0010:[<ffffffff804924f6>] [<ffffffff804924f6>] __sched_text_start+0x3a6/0x882 RSP: 0018:ffff810100cefe20 EFLAGS: 00010002 RAX: 000000000000008c RBX: ffff81002b0f64d8 RCX: 000000000000000c RDX: 0000000000000000 RSI: 000000000000008c RDI: ffff81002b0f6da8 RBP: ffff810100cefeb0 R08: 000000000000008c R09: ffff81002b0f6d98 R10: 0000000000000034 R11: ffffffff8021ab20 R12: ffff81002b0f5a40 R13: 0000000000000002 R14: 000000725eb99ef7 R15: 0000000000000013 FS: 0000000000000000(0000) GS:ffff810100c42bc0(0000) knlGS:0000000000000000 CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b CR2: 00002ba9c431ab70 CR3: 00000001060fc000 CR4: 00000000000006e0 Process migration/19 (pid: 59, threadinfo ffff810100cee000, task ffff810100ced8e0) Stack: 0000000000000001 0000000000000001 ffff81010b681e98 ffff810100ced8e0 ffff810100cefe80 ffff810100ceda78 0000000300000000 ffff81010b681e88 ffff81010b681e90 0000000000000286 0000000000000013 0000000000000000 Call Trace: [<ffffffff80224a00>] migration_thread+0x1b0/0x250 [<ffffffff80224850>] migration_thread+0x0/0x250 [<ffffffff8023c85b>] kthread+0xdb/0x120 [<ffffffff8020a7a8>] child_rip+0xa/0x12 [<ffffffff8023c780>] kthread+0x0/0x120 [<ffffffff8020a79e>] child_rip+0x0/0x12 Code: 0f 0b eb fe 49 8b 94 24 b8 01 00 00 49 8b 84 24 b0 01 00 00 RIP [<ffffffff804924f6>] __sched_text_start+0x3a6/0x882 RSP <ffff810100cefe20> ------------[ cut here ]------------ kernel BUG at kernel/sched.c:3505! invalid opcode: 0000 [1] SMP last sysfs file: devices/pci0000:00/0000:00:00.0/irq CPU 21 Modules linked in: loop dm_mod md_mod sg Pid: 15583, comm: cc1 Not tainted 2.6.21-rc4-mm1-autokern1 #1 RIP: 0010:[<ffffffff80496686>] [<ffffffff80496686>] __sched_text_start+0x3a6/0x882 RSP: 0000:ffff81010aca7ee0 EFLAGS: 00010002 RAX: 000000000000008c RBX: ffff81002b111358 RCX: 000000000000000c RDX: 0000000000000000 RSI: 000000000000008c RDI: ffff81002b111c28 RBP: ffff81010aca7f70 R08: 000000000000008c R09: ffff81002b111c18 R10: 0000000000000034 R11: 0000000000000001 R12: ffff81002b1108c0 R13: 0000000000000002 R14: 0000006cb9bdff1a R15: 0000000000000015 FS: 00002b6ef0bc66d0(0000) GS:ffff810100d02e40(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00002b6ef20c1000 CR3: 0000000106e2b000 CR4: 00000000000006e0 Process cc1 (pid: 15583, threadinfo ffff81010aca6000, task ffff810105b03620) Stack: 0000000000000100 0000000000000100 ffff81010964c148 ffff810105b03620 ffffffff8054c9b7 ffff810105b037c0 0000000b0000000e ffff81010b216d80 0000000000000000 00002b6ef20b7d00 00002b6ef20c1000 0000000000000400 Call Trace: [<ffffffff80209f17>] retint_careful+0xd/0x21 Code: 0f 0b eb fe 49 8b 94 24 b8 01 00 00 49 8b 84 24 b0 01 00 00 RIP [<ffffffff80496686>] __sched_text_start+0x3a6/0x882 RSP <ffff81010aca7ee0> >From elm3b245: ------------[ cut here ]------------ kernel BUG at kernel/sched.c:3505! invalid opcode: 0000 [1] SMP last sysfs file: CPU 0 Modules linked in: Pid: 1, comm: init Not tainted 2.6.21-rc4-mm1-autokern1 #1 RIP: 0010:[<ffffffff8049cbb7>] [<ffffffff8049cbb7>] __sched_text_start+0x377/0x819 RSP: 0018:ffff81010037dee0 EFLAGS: 00010002 RAX: 000000000000008c RBX: 0000000000000002 RCX: 0000000000000000 RDX: 0000000000000034 RSI: 000000000000008c RDI: ffff810002c15210 RBP: ffff81010037df70 R08: 000000000000008c R09: 000000000000000c R10: ffff810002c15200 R11: ffffffff8020968e R12: ffff810002c14940 R13: 00007fff1da16360 R14: ffff810002c14780 R15: 0000000000000000 FS: 00002b428d88d6d0(0000) GS:ffffffff805af000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000586a48 CR3: 0000000008c2f000 CR4: 00000000000006e0 Process init (pid: 1, threadinfo ffff81010037c000, task ffff810003369450) Stack: 000003e10059d1b0 ffff81010037df28 ffffffff80276dd3 ffff810003369450 ffff810008313880 0000003727988fe6 ffff8100033695f0 00007fff1da16250 00007fff1da16360 000000000059bb70 ffffffff8020968e ffff81010037df48 Call Trace: [<ffffffff80276dd3>] generic_file_llseek+0x87/0x96 [<ffffffff8020968e>] system_call+0x7e/0x83 [<ffffffff80207db2>] sys_clone+0x23/0x25 [<ffffffff802096f8>] sysret_careful+0xd/0x10 Code: 0f 0b eb fe 49 8b 96 b8 01 00 00 49 8b 86 b0 01 00 00 be 8c RIP [<ffffffff8049cbb7>] __sched_text_start+0x377/0x819 RSP <ffff81010037dee0> ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 9:45 ` 2.6.21-rc4-mm1 Andy Whitcroft @ 2007-03-22 8:41 ` Andy Whitcroft 2007-03-22 9:48 ` 2.6.21-rc4-mm1 Andy Whitcroft 0 siblings, 1 reply; 146+ messages in thread From: Andy Whitcroft @ 2007-03-22 8:41 UTC (permalink / raw) To: Andy Whitcroft Cc: Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh, Con Kolivas Andy Whitcroft wrote: > Andrew Morton wrote: >> Temporarily at >> >> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ >> >> Will appear later at >> >> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ >> >> >> > > [All of the below is from the pre hot-fix runs. The very few results > which are in for the hot-fix runs seem worse if anything. :( All > results should be out on TKO.] > >> - Restored the RSDL CPU scheduler (a new version thereof) > > Unsure if the above is the culprit but there seems to be a smattering of > BUG's in kernbench from the schedular on several systems, and panics > which do not fully dump out. > > elm3b239 is about 2/4 kernbench being the test in progress when we > blammo in both failed tests, elm3b234 doesn't boot at all. Well I have one result through for backing RSDL out on elm3b239 and that does indeed seem to give us a successful boot and test. peterz has pointed me to an incremental patch from Con which I'll push through testing and see if that sorts it out. -apw ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 8:41 ` 2.6.21-rc4-mm1 Andy Whitcroft @ 2007-03-22 9:48 ` Andy Whitcroft 2007-03-22 10:04 ` 2.6.21-rc4-mm1 Con Kolivas 0 siblings, 1 reply; 146+ messages in thread From: Andy Whitcroft @ 2007-03-22 9:48 UTC (permalink / raw) To: Andy Whitcroft Cc: Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh, Con Kolivas Andy Whitcroft wrote: > Andy Whitcroft wrote: >> Andrew Morton wrote: >>> Temporarily at >>> >>> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ >>> >>> Will appear later at >>> >>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ >>> >>> >>> >> [All of the below is from the pre hot-fix runs. The very few results >> which are in for the hot-fix runs seem worse if anything. :( All >> results should be out on TKO.] >> >>> - Restored the RSDL CPU scheduler (a new version thereof) >> Unsure if the above is the culprit but there seems to be a smattering of >> BUG's in kernbench from the schedular on several systems, and panics >> which do not fully dump out. >> >> elm3b239 is about 2/4 kernbench being the test in progress when we >> blammo in both failed tests, elm3b234 doesn't boot at all. > > Well I have one result through for backing RSDL out on elm3b239 and that > does indeed seem to give us a successful boot and test. peterz has > pointed me to an incremental patch from Con which I'll push through > testing and see if that sorts it out. Ok, tested the patch below on top of 2.6.21-rc4-mm1 and this seems to fix the problem: http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc4-mm1-rsdl-0.32.patch Hard to tell from that patch whether it will be fixed in the changes already committed to the next -mm. Its possible that it may be fixed by the following patch: sched-rsdl-improvements.patch Which has the following slipped in at the end of the changelog: A tiny change checking for MAX_PRIO in normal_prio() may prevent oopses on bootup on large SMP due to forking off the idle task. Con, are all the changes in the 0.32 patch above with akpm? -apw ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 9:48 ` 2.6.21-rc4-mm1 Andy Whitcroft @ 2007-03-22 10:04 ` Con Kolivas 2007-03-22 17:07 ` 2.6.21-rc4-mm1 Andy Whitcroft 0 siblings, 1 reply; 146+ messages in thread From: Con Kolivas @ 2007-03-22 10:04 UTC (permalink / raw) To: Andy Whitcroft; +Cc: Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh On Thursday 22 March 2007 20:48, Andy Whitcroft wrote: > Andy Whitcroft wrote: > > Andy Whitcroft wrote: > >> Andrew Morton wrote: > >>> Temporarily at > >>> > >>> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > >>> > >>> Will appear later at > >>> > >>> > >>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc > >>>4/2.6.21-rc4-mm1/ > >> > >> [All of the below is from the pre hot-fix runs. The very few results > >> which are in for the hot-fix runs seem worse if anything. :( All > >> results should be out on TKO.] > >> > >>> - Restored the RSDL CPU scheduler (a new version thereof) > >> > >> Unsure if the above is the culprit but there seems to be a smattering of > >> BUG's in kernbench from the schedular on several systems, and panics > >> which do not fully dump out. > >> > >> elm3b239 is about 2/4 kernbench being the test in progress when we > >> blammo in both failed tests, elm3b234 doesn't boot at all. > > > > Well I have one result through for backing RSDL out on elm3b239 and that > > does indeed seem to give us a successful boot and test. peterz has > > pointed me to an incremental patch from Con which I'll push through > > testing and see if that sorts it out. > > Ok, tested the patch below on top of 2.6.21-rc4-mm1 and this seems to > fix the problem: > > http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc4-mm1-rsdl-0.32.p >atch > > Hard to tell from that patch whether it will be fixed in the changes > already committed to the next -mm. > > Its possible that it may be fixed by the following patch: > > sched-rsdl-improvements.patch > > Which has the following slipped in at the end of the changelog: > > A tiny change checking for MAX_PRIO in normal_prio() > may prevent oopses on bootup on large SMP due to > forking off the idle task. > > Con, are all the changes in the 0.32 patch above with akpm? Yes he's queued everything in that patch you tested for the next -mm. Thanks very much for testing it. -- -ck ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 10:04 ` 2.6.21-rc4-mm1 Con Kolivas @ 2007-03-22 17:07 ` Andy Whitcroft 2007-03-22 18:17 ` 2.6.21-rc4-mm1 Andy Whitcroft 0 siblings, 1 reply; 146+ messages in thread From: Andy Whitcroft @ 2007-03-22 17:07 UTC (permalink / raw) To: Con Kolivas; +Cc: Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh Con Kolivas wrote: > On Thursday 22 March 2007 20:48, Andy Whitcroft wrote: >> Andy Whitcroft wrote: >>> Andy Whitcroft wrote: >>>> Andrew Morton wrote: >>>>> Temporarily at >>>>> >>>>> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ >>>>> >>>>> Will appear later at >>>>> >>>>> >>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc >>>>> 4/2.6.21-rc4-mm1/ >>>> [All of the below is from the pre hot-fix runs. The very few results >>>> which are in for the hot-fix runs seem worse if anything. :( All >>>> results should be out on TKO.] >>>> >>>>> - Restored the RSDL CPU scheduler (a new version thereof) >>>> Unsure if the above is the culprit but there seems to be a smattering of >>>> BUG's in kernbench from the schedular on several systems, and panics >>>> which do not fully dump out. >>>> >>>> elm3b239 is about 2/4 kernbench being the test in progress when we >>>> blammo in both failed tests, elm3b234 doesn't boot at all. >>> Well I have one result through for backing RSDL out on elm3b239 and that >>> does indeed seem to give us a successful boot and test. peterz has >>> pointed me to an incremental patch from Con which I'll push through >>> testing and see if that sorts it out. >> Ok, tested the patch below on top of 2.6.21-rc4-mm1 and this seems to >> fix the problem: >> >> http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc4-mm1-rsdl-0.32.p >> atch >> >> Hard to tell from that patch whether it will be fixed in the changes >> already committed to the next -mm. >> >> Its possible that it may be fixed by the following patch: >> >> sched-rsdl-improvements.patch >> >> Which has the following slipped in at the end of the changelog: >> >> A tiny change checking for MAX_PRIO in normal_prio() >> may prevent oopses on bootup on large SMP due to >> forking off the idle task. >> >> Con, are all the changes in the 0.32 patch above with akpm? > > Yes he's queued everything in that patch you tested for the next -mm. Thanks > very much for testing it. No worries. I've just got through the results on the other machine in the mix. That machine seems to be fixed by backing out RSDL and not by the fixup 0.32 patch ... This second machine seems to had hard very soon after user space starts executing but without a panic. I can't say that the symptoms are very definitive, but I do have a good result from that machine without RSDL and not with rsdl-0.32. The machine is a dual-core x86_64 machine: Dual Core AMD Opteron(tm) Processor 275. I'll let you know if I find out anything else. Shout if you want any information or have anything you want poked or tested. -apw ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 17:07 ` 2.6.21-rc4-mm1 Andy Whitcroft @ 2007-03-22 18:17 ` Andy Whitcroft 2007-03-22 22:14 ` 2.6.21-rc4-mm1 Con Kolivas 2007-03-23 6:18 ` 2.6.21-rc4-mm1 Con Kolivas 0 siblings, 2 replies; 146+ messages in thread From: Andy Whitcroft @ 2007-03-22 18:17 UTC (permalink / raw) To: Con Kolivas Cc: Andy Whitcroft, Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh Andy Whitcroft wrote: > Con Kolivas wrote: >> On Thursday 22 March 2007 20:48, Andy Whitcroft wrote: >>> Andy Whitcroft wrote: >>>> Andy Whitcroft wrote: >>>>> Andrew Morton wrote: >>>>>> Temporarily at >>>>>> >>>>>> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ >>>>>> >>>>>> Will appear later at >>>>>> >>>>>> >>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc >>>>>> 4/2.6.21-rc4-mm1/ >>>>> [All of the below is from the pre hot-fix runs. The very few results >>>>> which are in for the hot-fix runs seem worse if anything. :( All >>>>> results should be out on TKO.] >>>>> >>>>>> - Restored the RSDL CPU scheduler (a new version thereof) >>>>> Unsure if the above is the culprit but there seems to be a smattering of >>>>> BUG's in kernbench from the schedular on several systems, and panics >>>>> which do not fully dump out. >>>>> >>>>> elm3b239 is about 2/4 kernbench being the test in progress when we >>>>> blammo in both failed tests, elm3b234 doesn't boot at all. >>>> Well I have one result through for backing RSDL out on elm3b239 and that >>>> does indeed seem to give us a successful boot and test. peterz has >>>> pointed me to an incremental patch from Con which I'll push through >>>> testing and see if that sorts it out. >>> Ok, tested the patch below on top of 2.6.21-rc4-mm1 and this seems to >>> fix the problem: >>> >>> http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc4-mm1-rsdl-0.32.p >>> atch >>> >>> Hard to tell from that patch whether it will be fixed in the changes >>> already committed to the next -mm. >>> >>> Its possible that it may be fixed by the following patch: >>> >>> sched-rsdl-improvements.patch >>> >>> Which has the following slipped in at the end of the changelog: >>> >>> A tiny change checking for MAX_PRIO in normal_prio() >>> may prevent oopses on bootup on large SMP due to >>> forking off the idle task. >>> >>> Con, are all the changes in the 0.32 patch above with akpm? >> Yes he's queued everything in that patch you tested for the next -mm. Thanks >> very much for testing it. > > No worries. I've just got through the results on the other machine in > the mix. That machine seems to be fixed by backing out RSDL and not by > the fixup 0.32 patch ... > > This second machine seems to had hard very soon after user space starts > executing but without a panic. I can't say that the symptoms are very > definitive, but I do have a good result from that machine without RSDL > and not with rsdl-0.32. > > The machine is a dual-core x86_64 machine: Dual Core AMD Opteron(tm) > Processor 275. > > I'll let you know if I find out anything else. Shout if you want any > information or have anything you want poked or tested. Ok, I have yet a third x86_64 machine is is blowing up with the latest 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with 2.6.21-rc4-mm1+hotfixes-RSDL. I have results on various hotfix levels so I have just fired off a set of tests across the affected machines on that latest hotfix stack plus the RSDL backout and the results should be in in the next hour or two. I think there is a strong correlation between RSDL and these hangs. Any suggestions as to the next step. -apw ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 18:17 ` 2.6.21-rc4-mm1 Andy Whitcroft @ 2007-03-22 22:14 ` Con Kolivas 2007-03-23 6:18 ` 2.6.21-rc4-mm1 Con Kolivas 1 sibling, 0 replies; 146+ messages in thread From: Con Kolivas @ 2007-03-22 22:14 UTC (permalink / raw) To: Andy Whitcroft; +Cc: Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh On Friday 23 March 2007 05:17, Andy Whitcroft wrote: > Andy Whitcroft wrote: > > Con Kolivas wrote: > >> On Thursday 22 March 2007 20:48, Andy Whitcroft wrote: > >>> Andy Whitcroft wrote: > >>>> Andy Whitcroft wrote: > >>>>> Andrew Morton wrote: > >>>>>> Temporarily at > >>>>>> > >>>>>> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > >>>>>> > >>>>>> Will appear later at > >>>>>> > >>>>>> > >>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21 > >>>>>>-rc 4/2.6.21-rc4-mm1/ > >>>>> > >>>>> [All of the below is from the pre hot-fix runs. The very few results > >>>>> which are in for the hot-fix runs seem worse if anything. :( All > >>>>> results should be out on TKO.] > >>>>> > >>>>>> - Restored the RSDL CPU scheduler (a new version thereof) > >>>>> > >>>>> Unsure if the above is the culprit but there seems to be a smattering > >>>>> of BUG's in kernbench from the schedular on several systems, and > >>>>> panics which do not fully dump out. > >>>>> > >>>>> elm3b239 is about 2/4 kernbench being the test in progress when we > >>>>> blammo in both failed tests, elm3b234 doesn't boot at all. > >>>> > >>>> Well I have one result through for backing RSDL out on elm3b239 and > >>>> that does indeed seem to give us a successful boot and test. peterz > >>>> has pointed me to an incremental patch from Con which I'll push > >>>> through testing and see if that sorts it out. > >>> > >>> Ok, tested the patch below on top of 2.6.21-rc4-mm1 and this seems to > >>> fix the problem: > >>> > >>> http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc4-mm1-rsdl-0. > >>>32.p atch > >>> > >>> Hard to tell from that patch whether it will be fixed in the changes > >>> already committed to the next -mm. > >>> > >>> Its possible that it may be fixed by the following patch: > >>> > >>> sched-rsdl-improvements.patch > >>> > >>> Which has the following slipped in at the end of the changelog: > >>> > >>> A tiny change checking for MAX_PRIO in normal_prio() > >>> may prevent oopses on bootup on large SMP due to > >>> forking off the idle task. > >>> > >>> Con, are all the changes in the 0.32 patch above with akpm? > >> > >> Yes he's queued everything in that patch you tested for the next -mm. > >> Thanks very much for testing it. > > > > No worries. I've just got through the results on the other machine in > > the mix. That machine seems to be fixed by backing out RSDL and not by > > the fixup 0.32 patch ... > > > > This second machine seems to had hard very soon after user space starts > > executing but without a panic. I can't say that the symptoms are very > > definitive, but I do have a good result from that machine without RSDL > > and not with rsdl-0.32. > > > > The machine is a dual-core x86_64 machine: Dual Core AMD Opteron(tm) > > Processor 275. > > > > I'll let you know if I find out anything else. Shout if you want any > > information or have anything you want poked or tested. > > Ok, I have yet a third x86_64 machine is is blowing up with the latest > 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with > 2.6.21-rc4-mm1+hotfixes-RSDL. I have results on various hotfix levels > so I have just fired off a set of tests across the affected machines on > that latest hotfix stack plus the RSDL backout and the results should be > in in the next hour or two. > > I think there is a strong correlation between RSDL and these hangs. Any > suggestions as to the next step. If it's hitting the bug_on that I put in sched.c which you say it is then it is most certainly my fault. It implies a task has been queued without a corresponding bit being anywhere in the priority bitmaps. Somehow you only seem to be hitting it on big(ger) smp which is why I haven't seen it. It implies some complication occuring at sched or idle init/fork off these accounting not working. If I could reproduce it on qemu I'd step through the kernel init checking where each task is being queued and see if the bitmaps are being set. This is obviously time consuming and laborious so I don't expect you to do it. The next best thing is if you can send me the config of one of the machines that's oopsing I can try that on qemu but qemu is only good at debugging i386. If any of the machines that were oopsing were i386 that would be very helpful, otherwise x86_64 is the next best. Then I need to make a creative debugging patch for you to try which checks every queued/dequeued task and dumps all that information. I don't have that patch just yet so I need to find enough accumulated short stints at the pc to do that (still hurts a lot and worsens my condition). Thanks! -- -ck ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 18:17 ` 2.6.21-rc4-mm1 Andy Whitcroft 2007-03-22 22:14 ` 2.6.21-rc4-mm1 Con Kolivas @ 2007-03-23 6:18 ` Con Kolivas 2007-03-23 8:45 ` 2.6.21-rc4-mm1 Andy Whitcroft 1 sibling, 1 reply; 146+ messages in thread From: Con Kolivas @ 2007-03-23 6:18 UTC (permalink / raw) To: Andy Whitcroft; +Cc: Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh On Friday 23 March 2007 05:17, Andy Whitcroft wrote: > Ok, I have yet a third x86_64 machine is is blowing up with the latest > 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with > 2.6.21-rc4-mm1+hotfixes-RSDL. I have results on various hotfix levels > so I have just fired off a set of tests across the affected machines on > that latest hotfix stack plus the RSDL backout and the results should be > in in the next hour or two. > > I think there is a strong correlation between RSDL and these hangs. Any > suggestions as to the next step. Found a nasty in requeue_task + if (list_empty(old_array->queue + old_prio)) + __clear_bit(old_prio, p->array->prio_bitmap); see anything wrong there? I do :P I'll queue that up with the other changes pending and hopefully that will fix your bug. -- -ck ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-23 6:18 ` 2.6.21-rc4-mm1 Con Kolivas @ 2007-03-23 8:45 ` Andy Whitcroft 2007-03-23 12:28 ` 2.6.21-rc4-mm1 Andy Whitcroft 0 siblings, 1 reply; 146+ messages in thread From: Andy Whitcroft @ 2007-03-23 8:45 UTC (permalink / raw) To: Con Kolivas; +Cc: Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh Con Kolivas wrote: > On Friday 23 March 2007 05:17, Andy Whitcroft wrote: >> Ok, I have yet a third x86_64 machine is is blowing up with the latest >> 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with >> 2.6.21-rc4-mm1+hotfixes-RSDL. I have results on various hotfix levels >> so I have just fired off a set of tests across the affected machines on >> that latest hotfix stack plus the RSDL backout and the results should be >> in in the next hour or two. >> >> I think there is a strong correlation between RSDL and these hangs. Any >> suggestions as to the next step. > > Found a nasty in requeue_task > + if (list_empty(old_array->queue + old_prio)) > + __clear_bit(old_prio, p->array->prio_bitmap); > > see anything wrong there? I do :P > > I'll queue that up with the other changes pending and hopefully that will fix > your bug. Tests queued with your rdsl-0.33 patch (I am assuming its in there). Will let you know how it looks. -apw ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-23 8:45 ` 2.6.21-rc4-mm1 Andy Whitcroft @ 2007-03-23 12:28 ` Andy Whitcroft 2007-03-23 15:53 ` 2.6.21-rc4-mm1 Fortier,Vincent [Montreal] 2007-03-23 21:45 ` 2.6.21-rc4-mm1 Con Kolivas 0 siblings, 2 replies; 146+ messages in thread From: Andy Whitcroft @ 2007-03-23 12:28 UTC (permalink / raw) To: Andy Whitcroft Cc: Con Kolivas, Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh Andy Whitcroft wrote: > Con Kolivas wrote: >> On Friday 23 March 2007 05:17, Andy Whitcroft wrote: >>> Ok, I have yet a third x86_64 machine is is blowing up with the latest >>> 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with >>> 2.6.21-rc4-mm1+hotfixes-RSDL. I have results on various hotfix levels >>> so I have just fired off a set of tests across the affected machines on >>> that latest hotfix stack plus the RSDL backout and the results should be >>> in in the next hour or two. >>> >>> I think there is a strong correlation between RSDL and these hangs. Any >>> suggestions as to the next step. >> Found a nasty in requeue_task >> + if (list_empty(old_array->queue + old_prio)) >> + __clear_bit(old_prio, p->array->prio_bitmap); >> >> see anything wrong there? I do :P >> >> I'll queue that up with the other changes pending and hopefully that will fix >> your bug. > > Tests queued with your rdsl-0.33 patch (I am assuming its in there). > Will let you know how it looks. Hmmm, this is good for the original machine (as was 0.32) but not for either of the other two. I am seeing panics as below on those two. -apw elm3b245: NULL pointer dereference at 0000000000000020 RIP: [<ffffffff80497d94>] __sched_text_start+0x424/0x8a5 PGD 0 Oops: 0000 [1] SMP last sysfs file: block/ram0/uevent CPU 0 Modules linked in: Pid: 1038, comm: udevd Not tainted 2.6.21-rc4-mm1-autokern1 #1 RIP: 0010:[<ffffffff80497d94>] [<ffffffff80497d94>] __sched_text_start+0x424/0x8a5 RSP: 0018:ffff81000316de68 EFLAGS: 00010017 RAX: 00000000000006c6 RBX: 0000000000000001 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 000000000000008c RDI: ffffffffffffffd0 RBP: ffff81000316def8 R08: 0000000000000064 R09: 0000000000000024 R10: ffff810001014ad8 R11: 0000000000000286 R12: ffff810001014218 R13: ffff810001013780 R14: ffff810001769450 R15: 0000000000000000 FS: 00002b75d89c66d0(0000) GS:ffffffff805aa000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000020 CR3: 0000000000201000 CR4: 00000000000006e0 Process udevd (pid: 1038, threadinfo ffff81000316c000, task ffff8100031cebb0) Stack: 0000000000000000 0000000000000001 0000000000000000 ffff8100031cebb0 ffffffffffffffd0 00000036e28ef568 ffff8100031ced48 0000000000000292 ffff81000316def8 0000000000000246 ffff81000316def8 ffffffff8022af3d Call Trace: [<ffffffff8022af3d>] put_files_struct+0xbd/0xc9 [<ffffffff8022c773>] do_exit+0x7d2/0x7d6 [<ffffffff8022c801>] sys_exit_group+0x0/0x14 [<ffffffff8022c813>] sys_exit_group+0x12/0x14 [<ffffffff8020968e>] system_call+0x7e/0x83 Code: 48 39 47 50 74 51 48 c7 47 40 00 00 00 00 8b 52 f4 48 b9 40 RIP [<ffffffff80497d94>] __sched_text_start+0x424/0x8a5 RSP <ffff81000316de68> CR2: 0000000000000020 Fixing recursive fault but reboot is needed! elm3b6: Unable to handle kernel paging request at 000000000000fb6c RIP: [<ffffffff8020c573>] convert_rip_to_linear+0x53/0x91 PGD 180780067 PUD 182242067 PMD 0 Oops: 0000 [1] SMP last sysfs file: devices/pci0000:00/0000:00:0a.0/0000:02:04.0/host0/target0:0:6/0:0:6:0/type CPU 0 Modules linked in: Pid: 2442, comm: autorun Not tainted 2.6.21-rc4-mm1-autokern1 #1 RIP: 0010:[<ffffffff8020c573>] [<ffffffff8020c573>] convert_rip_to_linear+0x53/0x91 RSP: 0000:ffff810181a53cf8 EFLAGS: 00010002 RAX: 000000000000fb68 RBX: ffff810181a53e28 RCX: ffff8101823d6930 RDX: ffffffff8049fb6d RSI: ffff810182342180 RDI: ffff810182342440 RBP: ffff810181a53cf8 R08: 0000000080209bb9 R09: 000000000000008c R10: 0000000000000000 R11: 0000000001200011 R12: 0000000000000000 R13: ffff810182342180 R14: ffff810181a53e28 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffffffff805b2000(0063) knlGS:00000000f7f1cb80 CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b CR2: 000000000000fb6c CR3: 0000000181a5b000 CR4: 00000000000006e0 Process autorun (pid: 2442, threadinfo ffff810181a52000, task ffff8101823d6930) Stack: ffff810181a53d18 ffffffff80219075 ffff8101823d84a8 0000000000000020 ffff810181a53e18 ffffffff80219ab4 ffff8101fff654d8 ffff810181a53d48 ffffffff80264291 ffff8101823d6930 ffff810181a53e28 0000000000000046 Call Trace: [<ffffffff80219075>] is_prefetch+0x29/0x217 [<ffffffff80219ab4>] do_page_fault+0x608/0x7f0 [<ffffffff80264291>] page_dup_rmap+0x1d/0x24 [<ffffffff8024567c>] search_module_extables+0x83/0x8f [<ffffffff80229b43>] oops_enter+0xe/0x10 [<ffffffff8020ae62>] oops_begin+0x3c/0x70 [<ffffffff80219b31>] do_page_fault+0x685/0x7f0 [<ffffffff8022404d>] task_running_tick+0xad/0x290 [<ffffffff8049fb6d>] error_exit+0x0/0x84 [<ffffffff8049fb6d>] error_exit+0x0/0x84 [<ffffffff8049dc11>] thread_return+0x22/0xd3 [<ffffffff80209802>] int_careful+0xd/0x11 Code: 8b 48 04 0f b7 50 02 0f b6 c1 c1 e0 10 09 c2 89 c8 25 00 00 RIP [<ffffffff8020c573>] convert_rip_to_linear+0x53/0x91 RSP <ffff810181a53cf8> CR2: 000000000000fb6c ^ permalink raw reply [flat|nested] 146+ messages in thread
* RE: 2.6.21-rc4-mm1 2007-03-23 12:28 ` 2.6.21-rc4-mm1 Andy Whitcroft @ 2007-03-23 15:53 ` Fortier,Vincent [Montreal] 2007-03-23 21:45 ` 2.6.21-rc4-mm1 Con Kolivas 1 sibling, 0 replies; 146+ messages in thread From: Fortier,Vincent [Montreal] @ 2007-03-23 15:53 UTC (permalink / raw) To: Andy Whitcroft, Con Kolivas Cc: Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh > > Andy Whitcroft wrote: > > Con Kolivas wrote: > >> On Friday 23 March 2007 05:17, Andy Whitcroft wrote: > >>> Ok, I have yet a third x86_64 machine is is blowing up with the > >>> latest > >>> 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with > >>> 2.6.21-rc4-mm1+hotfixes-RSDL. I have results on various hotfix > >>> levels so I have just fired off a set of tests across the affected > >>> machines on that latest hotfix stack plus the RSDL backout and the > >>> results should be in in the next hour or two. > >>> > >>> I think there is a strong correlation between RSDL and these hangs. > >>> Any suggestions as to the next step. > >> Found a nasty in requeue_task > >> + if (list_empty(old_array->queue + old_prio)) > >> + __clear_bit(old_prio, p->array->prio_bitmap); > >> > >> see anything wrong there? I do :P > >> > >> I'll queue that up with the other changes pending and hopefully that > >> will fix your bug. > > > > Tests queued with your rdsl-0.33 patch (I am assuming its in there). > > Will let you know how it looks. > > Hmmm, this is good for the original machine (as was 0.32) but > not for either of the other two. I am seeing panics as below > on those two. > > -apw > I don't know if this might help out or even if it is related but I get a "similar" crash every time using my backported rsdl patch on a 2.6.19.7 kernel. "Maybie" this type of BUG might be easier to trigger under that specific kernel? Here is a picture of the output: http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/bug-2.6.19 .7-rsdl-033.jpg. - vin ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-23 12:28 ` 2.6.21-rc4-mm1 Andy Whitcroft 2007-03-23 15:53 ` 2.6.21-rc4-mm1 Fortier,Vincent [Montreal] @ 2007-03-23 21:45 ` Con Kolivas 2007-03-23 23:26 ` debug rsdl 0.33 Con Kolivas 1 sibling, 1 reply; 146+ messages in thread From: Con Kolivas @ 2007-03-23 21:45 UTC (permalink / raw) To: Andy Whitcroft; +Cc: Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh On Friday 23 March 2007 23:28, Andy Whitcroft wrote: > Andy Whitcroft wrote: > > Con Kolivas wrote: > >> On Friday 23 March 2007 05:17, Andy Whitcroft wrote: > >>> Ok, I have yet a third x86_64 machine is is blowing up with the latest > >>> 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with > >>> 2.6.21-rc4-mm1+hotfixes-RSDL. I have results on various hotfix levels > >>> so I have just fired off a set of tests across the affected machines on > >>> that latest hotfix stack plus the RSDL backout and the results should > >>> be in in the next hour or two. > >>> > >>> I think there is a strong correlation between RSDL and these hangs. > >>> Any suggestions as to the next step. > >> > >> Found a nasty in requeue_task > >> + if (list_empty(old_array->queue + old_prio)) > >> + __clear_bit(old_prio, p->array->prio_bitmap); > >> > >> see anything wrong there? I do :P > >> > >> I'll queue that up with the other changes pending and hopefully that > >> will fix your bug. > > > > Tests queued with your rdsl-0.33 patch (I am assuming its in there). > > Will let you know how it looks. > > Hmmm, this is good for the original machine (as was 0.32) but not for > either of the other two. I am seeing panics as below on those two. This machine seems most sensitive to it (first column): elm3b6 amd64 newisys 4cpu config: amd64 Can you throw this debugging patch at it please? The console output might be very helpful. On top of sched-rsdl-0.33 thanks! --- kernel/sched.c | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) Index: linux-2.6.21-rc4-mm1/kernel/sched.c =================================================================== --- linux-2.6.21-rc4-mm1.orig/kernel/sched.c 2007-03-24 08:32:19.000000000 +1100 +++ linux-2.6.21-rc4-mm1/kernel/sched.c 2007-03-24 08:42:04.000000000 +1100 @@ -659,6 +659,25 @@ static inline void set_task_entitlement( p->time_slice = p->quota; } +static int debug_rqbitmap(struct rq *rq) +{ + struct list_head *queue; + int idx = 0, error = 0; + struct prio_array *array = rq->active; + + for (idx = 0; idx < MAX_PRIO; idx++) { + queue = array->queue + idx; + if (!list_empty(queue)) { + if (!test_bit(idx, rq->dyn_bitmap)) { + __set_bit(idx, rq->dyn_bitmap); + error = 1; + printk(KERN_ERR "MISSING DYNAMIC BIT %d\n", idx); + } + } + } + return error; +} + /* * There is no specific hard accounting. The dynamic bits can have * false positives. rt_tasks can only be on the active queue. @@ -679,6 +698,7 @@ static void dequeue_task(struct task_str list_del_init(&p->run_list); if (list_empty(p->array->queue + p->prio)) __clear_bit(p->prio, p->array->prio_bitmap); + WARN_ON(debug_rqbitmap(rq)); } /* @@ -797,12 +817,14 @@ static void enqueue_task(struct task_str { __enqueue_task(p, rq); list_add_tail(&p->run_list, p->array->queue + p->prio); + WARN_ON(debug_rqbitmap(rq)); } static inline void enqueue_task_head(struct task_struct *p, struct rq *rq) { __enqueue_task(p, rq); list_add(&p->run_list, p->array->queue + p->prio); + WARN_ON(debug_rqbitmap(rq)); } /* @@ -820,6 +842,7 @@ static void requeue_task(struct task_str __clear_bit(old_prio, old_array->prio_bitmap); set_dynamic_bit(p, rq); } + WARN_ON(debug_rqbitmap(rq)); } /* @@ -906,6 +929,7 @@ static inline void __activate_task(struc { enqueue_task(p, rq); inc_nr_running(p, rq); + WARN_ON(debug_rqbitmap(rq)); } /* @@ -1006,6 +1030,7 @@ static void deactivate_task(struct task_ { dec_nr_running(p, rq); dequeue_task(p, rq); + WARN_ON(debug_rqbitmap(rq)); } /* @@ -1718,9 +1743,11 @@ void fastcall wake_up_new_task(struct ta * Parent and child are on different CPUs, now get the * parent runqueue to update the parent's ->flags: */ + WARN_ON(debug_rqbitmap(rq)); task_rq_unlock(rq, &flags); this_rq = task_rq_lock(current, &flags); } + WARN_ON(debug_rqbitmap(this_rq)); task_rq_unlock(this_rq, &flags); } @@ -3357,6 +3384,7 @@ static inline void major_prio_rotation(s rq->dyn_bitmap = rq->active->prio_bitmap; rq->best_static_prio = MAX_PRIO - 1; rq->prio_rotation++; + WARN_ON(debug_rqbitmap(rq)); } /* @@ -3399,6 +3427,8 @@ static inline void rotate_runqueue_prior } memset(rq->prio_quota, 0, ARRAY_SIZE(rq->prio_quota)); major_prio_rotation(rq); + WARN_ON(debug_rqbitmap(rq)); + } else { /* Minor rotation */ new_prio_level = rq->prio_level + 1; @@ -3409,6 +3439,7 @@ static inline void rotate_runqueue_prior __set_bit(new_prio_level, rq->dyn_bitmap); } rq_quota(rq, rq->prio_level) = 0; + WARN_ON(debug_rqbitmap(rq)); } rq->prio_level = new_prio_level; /* @@ -3431,6 +3462,10 @@ static void task_running_tick(struct rq return; spin_lock(&rq->lock); + if (!p->time_slice) { + printk(KERN_ERR "NO TIME_SLICE IN TRT \n"); + p->time_slice++; + } /* * Accounting is performed by both the task and the runqueue. This * allows frequently sleeping tasks to get their proper quota of @@ -3460,6 +3495,7 @@ static void task_running_tick(struct rq set_tsk_need_resched(p); } out_unlock: + WARN_ON(debug_rqbitmap(rq)); spin_unlock(&rq->lock); } @@ -3479,6 +3515,7 @@ void scheduler_tick(void) if (!idle_at_tick) task_running_tick(rq, p, 1); + WARN_ON(debug_rqbitmap(rq)); #ifdef CONFIG_SMP update_load(rq); rq->idle_at_tick = idle_at_tick; @@ -3548,6 +3585,7 @@ static inline struct task_struct *next_d struct prio_array *array = rq->active; int expirations = 0; + WARN_ON(debug_rqbitmap(rq)); retry: if (idx >= MAX_PRIO) { BUG_ON(++expirations > 1); @@ -3601,6 +3639,7 @@ retry: if (next->static_prio < rq->best_static_prio && next->policy != SCHED_BATCH) rq->best_static_prio = next->static_prio; + WARN_ON(debug_rqbitmap(rq)); return next; } -- -ck ^ permalink raw reply [flat|nested] 146+ messages in thread
* debug rsdl 0.33 2007-03-23 21:45 ` 2.6.21-rc4-mm1 Con Kolivas @ 2007-03-23 23:26 ` Con Kolivas 2007-03-25 12:27 ` Andy Whitcroft 2007-03-25 18:28 ` Torsten Kaiser 0 siblings, 2 replies; 146+ messages in thread From: Con Kolivas @ 2007-03-23 23:26 UTC (permalink / raw) To: Andy Whitcroft, William Lee Irwin III Cc: Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh On Saturday 24 March 2007 08:45, Con Kolivas wrote: > On Friday 23 March 2007 23:28, Andy Whitcroft wrote: > > Andy Whitcroft wrote: > > > Con Kolivas wrote: > > >> On Friday 23 March 2007 05:17, Andy Whitcroft wrote: > > >>> Ok, I have yet a third x86_64 machine is is blowing up with the > > >>> latest 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with > > >>> 2.6.21-rc4-mm1+hotfixes-RSDL. I have results on various hotfix > > >>> levels so I have just fired off a set of tests across the affected > > >>> machines on that latest hotfix stack plus the RSDL backout and the > > >>> results should be in in the next hour or two. > > >>> > > >>> I think there is a strong correlation between RSDL and these hangs. > > >>> Any suggestions as to the next step. > > >> > > >> Found a nasty in requeue_task > > >> + if (list_empty(old_array->queue + old_prio)) > > >> + __clear_bit(old_prio, p->array->prio_bitmap); > > >> > > >> see anything wrong there? I do :P > > >> > > >> I'll queue that up with the other changes pending and hopefully that > > >> will fix your bug. > > > > > > Tests queued with your rdsl-0.33 patch (I am assuming its in there). > > > Will let you know how it looks. > > > > Hmmm, this is good for the original machine (as was 0.32) but not for > > either of the other two. I am seeing panics as below on those two. > > This machine seems most sensitive to it (first column): > elm3b6 > amd64 > newisys > 4cpu > config: amd64 > > Can you throw this debugging patch at it please? The console output might > be very helpful. On top of sched-rsdl-0.33 thanks! Better yet this one which checks the expired array as well and after pull_task. If anyone's getting a bug they think might be due to rsdl please try this (on rsdl 0.33). --- kernel/sched.c | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 51 insertions(+) Index: linux-2.6.21-rc4-mm1/kernel/sched.c =================================================================== --- linux-2.6.21-rc4-mm1.orig/kernel/sched.c 2007-03-24 08:32:19.000000000 +1100 +++ linux-2.6.21-rc4-mm1/kernel/sched.c 2007-03-24 10:22:59.000000000 +1100 @@ -659,6 +659,35 @@ static inline void set_task_entitlement( p->time_slice = p->quota; } +static int debug_rqbitmap(struct rq *rq) +{ + struct list_head *queue; + int idx = 0, error = 0; + struct prio_array *array; + + for (idx = 0; idx < MAX_PRIO; idx++) { + array = rq->active; + queue = array->queue + idx; + if (!list_empty(queue)) { + if (!test_bit(idx, rq->dyn_bitmap)) { + __set_bit(idx, rq->dyn_bitmap); + error = 1; + printk(KERN_ERR "MISSING DYNAMIC BIT %d\n", idx); + } + } + array = rq->expired; + queue = array->queue + idx; + if (!list_empty(queue)) { + if (!test_bit(idx, rq->exp_bitmap)) { + __set_bit(idx, rq->exp_bitmap); + error = 1; + printk(KERN_ERR "MISSING EXPIRED BIT %d\n", idx); + } + } + } + return error; +} + /* * There is no specific hard accounting. The dynamic bits can have * false positives. rt_tasks can only be on the active queue. @@ -679,6 +708,7 @@ static void dequeue_task(struct task_str list_del_init(&p->run_list); if (list_empty(p->array->queue + p->prio)) __clear_bit(p->prio, p->array->prio_bitmap); + WARN_ON(debug_rqbitmap(rq)); } /* @@ -797,12 +827,14 @@ static void enqueue_task(struct task_str { __enqueue_task(p, rq); list_add_tail(&p->run_list, p->array->queue + p->prio); + WARN_ON(debug_rqbitmap(rq)); } static inline void enqueue_task_head(struct task_struct *p, struct rq *rq) { __enqueue_task(p, rq); list_add(&p->run_list, p->array->queue + p->prio); + WARN_ON(debug_rqbitmap(rq)); } /* @@ -820,6 +852,7 @@ static void requeue_task(struct task_str __clear_bit(old_prio, old_array->prio_bitmap); set_dynamic_bit(p, rq); } + WARN_ON(debug_rqbitmap(rq)); } /* @@ -906,6 +939,7 @@ static inline void __activate_task(struc { enqueue_task(p, rq); inc_nr_running(p, rq); + WARN_ON(debug_rqbitmap(rq)); } /* @@ -1006,6 +1040,7 @@ static void deactivate_task(struct task_ { dec_nr_running(p, rq); dequeue_task(p, rq); + WARN_ON(debug_rqbitmap(rq)); } /* @@ -1718,9 +1753,11 @@ void fastcall wake_up_new_task(struct ta * Parent and child are on different CPUs, now get the * parent runqueue to update the parent's ->flags: */ + WARN_ON(debug_rqbitmap(rq)); task_rq_unlock(rq, &flags); this_rq = task_rq_lock(current, &flags); } + WARN_ON(debug_rqbitmap(this_rq)); task_rq_unlock(this_rq, &flags); } @@ -2124,6 +2161,8 @@ static void pull_task(struct rq *src_rq, enqueue_pulled_task(src_rq, this_rq, p); p->timestamp = (p->timestamp - src_rq->most_recent_timestamp) + this_rq->most_recent_timestamp; + WARN_ON(debug_rqbitmap(src_rq)); + WARN_ON(debug_rqbitmap(this_rq)); try_preempt(p, this_rq); } @@ -3357,6 +3396,7 @@ static inline void major_prio_rotation(s rq->dyn_bitmap = rq->active->prio_bitmap; rq->best_static_prio = MAX_PRIO - 1; rq->prio_rotation++; + WARN_ON(debug_rqbitmap(rq)); } /* @@ -3399,6 +3439,8 @@ static inline void rotate_runqueue_prior } memset(rq->prio_quota, 0, ARRAY_SIZE(rq->prio_quota)); major_prio_rotation(rq); + WARN_ON(debug_rqbitmap(rq)); + } else { /* Minor rotation */ new_prio_level = rq->prio_level + 1; @@ -3409,6 +3451,7 @@ static inline void rotate_runqueue_prior __set_bit(new_prio_level, rq->dyn_bitmap); } rq_quota(rq, rq->prio_level) = 0; + WARN_ON(debug_rqbitmap(rq)); } rq->prio_level = new_prio_level; /* @@ -3431,6 +3474,10 @@ static void task_running_tick(struct rq return; spin_lock(&rq->lock); + if (!p->time_slice) { + printk(KERN_ERR "NO TIME_SLICE IN TRT \n"); + p->time_slice++; + } /* * Accounting is performed by both the task and the runqueue. This * allows frequently sleeping tasks to get their proper quota of @@ -3460,6 +3507,7 @@ static void task_running_tick(struct rq set_tsk_need_resched(p); } out_unlock: + WARN_ON(debug_rqbitmap(rq)); spin_unlock(&rq->lock); } @@ -3479,6 +3527,7 @@ void scheduler_tick(void) if (!idle_at_tick) task_running_tick(rq, p, 1); + WARN_ON(debug_rqbitmap(rq)); #ifdef CONFIG_SMP update_load(rq); rq->idle_at_tick = idle_at_tick; @@ -3548,6 +3597,7 @@ static inline struct task_struct *next_d struct prio_array *array = rq->active; int expirations = 0; + WARN_ON(debug_rqbitmap(rq)); retry: if (idx >= MAX_PRIO) { BUG_ON(++expirations > 1); @@ -3601,6 +3651,7 @@ retry: if (next->static_prio < rq->best_static_prio && next->policy != SCHED_BATCH) rq->best_static_prio = next->static_prio; + WARN_ON(debug_rqbitmap(rq)); return next; } -- -ck ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: debug rsdl 0.33 2007-03-23 23:26 ` debug rsdl 0.33 Con Kolivas @ 2007-03-25 12:27 ` Andy Whitcroft 2007-03-25 18:28 ` Torsten Kaiser 1 sibling, 0 replies; 146+ messages in thread From: Andy Whitcroft @ 2007-03-25 12:27 UTC (permalink / raw) To: Con Kolivas Cc: William Lee Irwin III, Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh Con Kolivas wrote: > On Saturday 24 March 2007 08:45, Con Kolivas wrote: >> On Friday 23 March 2007 23:28, Andy Whitcroft wrote: >>> Andy Whitcroft wrote: >>>> Con Kolivas wrote: >>>>> On Friday 23 March 2007 05:17, Andy Whitcroft wrote: >>>>>> Ok, I have yet a third x86_64 machine is is blowing up with the >>>>>> latest 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with >>>>>> 2.6.21-rc4-mm1+hotfixes-RSDL. I have results on various hotfix >>>>>> levels so I have just fired off a set of tests across the affected >>>>>> machines on that latest hotfix stack plus the RSDL backout and the >>>>>> results should be in in the next hour or two. >>>>>> >>>>>> I think there is a strong correlation between RSDL and these hangs. >>>>>> Any suggestions as to the next step. >>>>> Found a nasty in requeue_task >>>>> + if (list_empty(old_array->queue + old_prio)) >>>>> + __clear_bit(old_prio, p->array->prio_bitmap); >>>>> >>>>> see anything wrong there? I do :P >>>>> >>>>> I'll queue that up with the other changes pending and hopefully that >>>>> will fix your bug. >>>> Tests queued with your rdsl-0.33 patch (I am assuming its in there). >>>> Will let you know how it looks. >>> Hmmm, this is good for the original machine (as was 0.32) but not for >>> either of the other two. I am seeing panics as below on those two. >> This machine seems most sensitive to it (first column): >> elm3b6 >> amd64 >> newisys >> 4cpu >> config: amd64 >> >> Can you throw this debugging patch at it please? The console output might >> be very helpful. On top of sched-rsdl-0.33 thanks! > > Better yet this one which checks the expired array as well and after > pull_task. > > If anyone's getting a bug they think might be due to rsdl please try this (on > rsdl 0.33). Ok, new round of tests across the sensitive machines with 0.33 plus the above debug patch are in the queue. Will let you know how they pan out. The tests with -rc4 + 0.33 are also in. Failing there also. Both out of __sched_text_start, so I'd guess the same cause and the schedular is fingered. -apw ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: debug rsdl 0.33 2007-03-23 23:26 ` debug rsdl 0.33 Con Kolivas 2007-03-25 12:27 ` Andy Whitcroft @ 2007-03-25 18:28 ` Torsten Kaiser 2007-03-25 22:01 ` Andrew Morton 2007-03-25 22:49 ` Con Kolivas 1 sibling, 2 replies; 146+ messages in thread From: Torsten Kaiser @ 2007-03-25 18:28 UTC (permalink / raw) To: Con Kolivas Cc: Andy Whitcroft, William Lee Irwin III, Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh On 3/24/07, Con Kolivas <kernel@kolivas.org> wrote: > kernel/sched.c | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 51 insertions(+) 2.6.21-rc4-mm1 also fails for me. I tried pure 2.6.21-rc4-mm1, +hotfixes, +hotfixes+rsdl33 and at last also added above debug patch. The oops from with the debug-patch added: [ 65.426126] Freeing unused kernel memory: 312k freed (on the console the system is starting up, getting until "Letting udev process events ...") [ 66.665611] Unable to handle kernel NULL pointer dereference at 0000000000000020 RIP: [ 66.682030] [<ffffffff8026167c>] __sched_text_start+0x4dc/0xa0e [ 66.707402] PGD 0 [ 66.713473] Oops: 0000 [1] SMP [ 66.722968] last sysfs file: devices/pci0000:00/0000:00:05.0/host2/target2:0:0/2:0:0:0/type [ 66.747954] CPU 0 [ 66.754025] Modules linked in: [ 66.763209] Pid: 1200, comm: udevd Not tainted 2.6.21-rc4-mm1 #4 [ 66.781162] RIP: 0010:[<ffffffff8026167c>] [<ffffffff8026167c>] __sched_text_start+0x4dc/0xa0e [ 66.807236] RSP: 0018:ffff81007d38fe78 EFLAGS: 00010082 [ 66.823115] RAX: ffffffffffffffd0 RBX: 000000000000008c RCX: 000000000000058e [ 66.844439] RDX: 0000000000000000 RSI: 000000000000000c RDI: 0000000000000000 [ 66.865767] RBP: ffff81007d38ff08 R08: 0000000000000064 R09: ffff810001014a58 [ 66.887092] R10: 000000000000001c R11: 0000000000000246 R12: ffff810001013700 [ 66.908418] R13: ffff810001014198 R14: 0000000000000001 R15: 0000000f859461fc [ 66.929745] FS: 00002b67df90e6d0(0000) GS:ffffffff807aa000(0000) knlGS:0000000000000000 [ 66.953950] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [ 66.971126] CR2: 0000000000000020 CR3: 0000000000201000 CR4: 00000000000006e0 [ 66.992451] Process udevd (pid: 1200, threadinfo ffff81007d38e000, task ffff81007e354100) [ 67.016915] Stack: 00000000000004b0 0000000000000000 0000000000000000 ffff81007e354100 [ 67.041097] ffffffffffffffd0 ffff81007e354298 ffff81011d420680 ffffffff802234b1 [ 67.063407] 0000000000000001 0000000000000000 0000000000000000 0000000000000246 [ 67.085149] Call Trace: [ 67.093037] [<ffffffff802234b1>] filp_close+0x71/0x90 [ 67.108397] [<ffffffff80214d97>] do_exit+0x7e7/0x800 [ 67.123495] [<ffffffff80248372>] do_group_exit+0x82/0x90 [ 67.139634] [<ffffffff8025c1de>] system_call+0x7e/0x83 [ 67.155277] [ 67.159739] [ 67.159740] Code: 48 39 48 50 0f 84 8b 00 00 00 48 c7 40 40 00 00 00 00 8b 52 [ 67.186877] RIP [<ffffffff8026167c>] __sched_text_start+0x4dc/0xa0e [ 67.205919] RSP <ffff81007d38fe78> [ 67.216348] CR2: 0000000000000020 [ 67.226260] Fixing recursive fault but reboot is needed! The system in x86_64, two 2218 on a MCP55 nvidia chipset. 2.6.21-rc3-mm1 works fine. (gdb) list *0xffffffff8026167c 0xffffffff8026167c is in schedule (kernel/sched.c:3619). 3614 /* 3615 * When the task is chosen it is checked to see if its quota has been 3616 * added to this runqueue level which is only performed once per 3617 * level per major rotation for each running task. 3618 */ 3619 if (next->rotation != rq->prio_rotation) { 3620 /* Task has moved during major rotation */ 3621 task_new_array(next, rq); 3622 if (!entitled_slot(next->static_prio, idx)) 3623 exchange_slot(next, rq); Torsten ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: debug rsdl 0.33 2007-03-25 18:28 ` Torsten Kaiser @ 2007-03-25 22:01 ` Andrew Morton 2007-03-25 22:49 ` Con Kolivas 1 sibling, 0 replies; 146+ messages in thread From: Andrew Morton @ 2007-03-25 22:01 UTC (permalink / raw) To: Torsten Kaiser Cc: Con Kolivas, Andy Whitcroft, William Lee Irwin III, linux-kernel, Steve Fox, Martin J. Bligh On Sun, 25 Mar 2007 19:28:57 +0100 "Torsten Kaiser" <just.for.lkml@googlemail.com> wrote: > On 3/24/07, Con Kolivas <kernel@kolivas.org> wrote: > > kernel/sched.c | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 51 insertions(+) > > 2.6.21-rc4-mm1 also fails for me. > > I tried pure 2.6.21-rc4-mm1, +hotfixes, +hotfixes+rsdl33 and at last > also added above debug patch. > > The oops from with the debug-patch added: > [ 65.426126] Freeing unused kernel memory: 312k freed > (on the console the system is starting up, getting until "Letting udev > process events ...") > [ 66.665611] Unable to handle kernel NULL pointer dereference at > 0000000000000020 RIP: > [ 66.682030] [<ffffffff8026167c>] __sched_text_start+0x4dc/0xa0e > [ 66.707402] PGD 0 > [ 66.713473] Oops: 0000 [1] SMP > [ 66.722968] last sysfs file: > devices/pci0000:00/0000:00:05.0/host2/target2:0:0/2:0:0:0/type > [ 66.747954] CPU 0 > [ 66.754025] Modules linked in: > [ 66.763209] Pid: 1200, comm: udevd Not tainted 2.6.21-rc4-mm1 #4 > [ 66.781162] RIP: 0010:[<ffffffff8026167c>] [<ffffffff8026167c>] > __sched_text_start+0x4dc/0xa0e > [ 66.807236] RSP: 0018:ffff81007d38fe78 EFLAGS: 00010082 > [ 66.823115] RAX: ffffffffffffffd0 RBX: 000000000000008c RCX: 000000000000058e > [ 66.844439] RDX: 0000000000000000 RSI: 000000000000000c RDI: 0000000000000000 > [ 66.865767] RBP: ffff81007d38ff08 R08: 0000000000000064 R09: ffff810001014a58 > [ 66.887092] R10: 000000000000001c R11: 0000000000000246 R12: ffff810001013700 > [ 66.908418] R13: ffff810001014198 R14: 0000000000000001 R15: 0000000f859461fc > [ 66.929745] FS: 00002b67df90e6d0(0000) GS:ffffffff807aa000(0000) > knlGS:0000000000000000 > [ 66.953950] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b > [ 66.971126] CR2: 0000000000000020 CR3: 0000000000201000 CR4: 00000000000006e0 > [ 66.992451] Process udevd (pid: 1200, threadinfo ffff81007d38e000, > task ffff81007e354100) > [ 67.016915] Stack: 00000000000004b0 0000000000000000 > 0000000000000000 ffff81007e354100 > [ 67.041097] ffffffffffffffd0 ffff81007e354298 ffff81011d420680 > ffffffff802234b1 > [ 67.063407] 0000000000000001 0000000000000000 0000000000000000 > 0000000000000246 > [ 67.085149] Call Trace: > [ 67.093037] [<ffffffff802234b1>] filp_close+0x71/0x90 > [ 67.108397] [<ffffffff80214d97>] do_exit+0x7e7/0x800 > [ 67.123495] [<ffffffff80248372>] do_group_exit+0x82/0x90 > [ 67.139634] [<ffffffff8025c1de>] system_call+0x7e/0x83 > [ 67.155277] > [ 67.159739] > [ 67.159740] Code: 48 39 48 50 0f 84 8b 00 00 00 48 c7 40 40 00 00 00 00 8b 52 > [ 67.186877] RIP [<ffffffff8026167c>] __sched_text_start+0x4dc/0xa0e > [ 67.205919] RSP <ffff81007d38fe78> > [ 67.216348] CR2: 0000000000000020 > [ 67.226260] Fixing recursive fault but reboot is needed! We've seen multiple reports of this. For some reason we've managed to confuse kallsyms too. > The system in x86_64, two 2218 on a MCP55 nvidia chipset. > > 2.6.21-rc3-mm1 works fine. > > (gdb) list *0xffffffff8026167c > 0xffffffff8026167c is in schedule (kernel/sched.c:3619). > 3614 /* > 3615 * When the task is chosen it is checked to see if its > quota has been > 3616 * added to this runqueue level which is only performed once per > 3617 * level per major rotation for each running task. > 3618 */ > 3619 if (next->rotation != rq->prio_rotation) { > 3620 /* Task has moved during major rotation */ > 3621 task_new_array(next, rq); > 3622 if (!entitled_slot(next->static_prio, idx)) > 3623 exchange_slot(next, rq); > > Ah, that helps, thanks. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: debug rsdl 0.33 2007-03-25 18:28 ` Torsten Kaiser 2007-03-25 22:01 ` Andrew Morton @ 2007-03-25 22:49 ` Con Kolivas 2007-03-25 22:59 ` Con Kolivas 1 sibling, 1 reply; 146+ messages in thread From: Con Kolivas @ 2007-03-25 22:49 UTC (permalink / raw) To: Torsten Kaiser Cc: Andy Whitcroft, William Lee Irwin III, Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh On Monday 26 March 2007 04:28, Torsten Kaiser wrote: > On 3/24/07, Con Kolivas <kernel@kolivas.org> wrote: > > kernel/sched.c | 51 > > +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 51 > > insertions(+) > > 2.6.21-rc4-mm1 also fails for me. > > I tried pure 2.6.21-rc4-mm1, +hotfixes, +hotfixes+rsdl33 and at last > also added above debug patch. Thank you very much for the effort! > > The oops from with the debug-patch added: > [ 65.426126] Freeing unused kernel memory: 312k freed > (on the console the system is starting up, getting until "Letting udev > process events ...") > [ 66.665611] Unable to handle kernel NULL pointer dereference at > 0000000000000020 RIP: > [ 66.682030] [<ffffffff8026167c>] __sched_text_start+0x4dc/0xa0e The debug patch didn't do anything. This means it is not an unset bitmap problem at all otherwise it should have self corrected itself. > The system in x86_64, two 2218 on a MCP55 nvidia chipset. > > 2.6.21-rc3-mm1 works fine. > > (gdb) list *0xffffffff8026167c > 0xffffffff8026167c is in schedule (kernel/sched.c:3619). next = list_entry(queue->next, struct task_struct, run_list); rq->prio_level = idx; > 3614 /* > 3615 * When the task is chosen it is checked to see if its > quota has been > 3616 * added to this runqueue level which is only performed > once per 3617 * level per major rotation for each running task. > 3618 */ > 3619 if (next->rotation != rq->prio_rotation) { Urgh. Dereferencing there? That can only be next that's deferencing meaning the run_list entry is bogus. That should only ever be done under runqueue lock so I have a race somewhere where it's not. Time for more looking. > Torsten Thanks! -- -ck ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: debug rsdl 0.33 2007-03-25 22:49 ` Con Kolivas @ 2007-03-25 22:59 ` Con Kolivas 2007-03-26 7:49 ` Andy Whitcroft 0 siblings, 1 reply; 146+ messages in thread From: Con Kolivas @ 2007-03-25 22:59 UTC (permalink / raw) To: Torsten Kaiser Cc: Andy Whitcroft, William Lee Irwin III, Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh On Monday 26 March 2007 08:49, Con Kolivas wrote: > On Monday 26 March 2007 04:28, Torsten Kaiser wrote: > > On 3/24/07, Con Kolivas <kernel@kolivas.org> wrote: > > > kernel/sched.c | 51 > > > +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 51 > > > insertions(+) > > > > 2.6.21-rc4-mm1 also fails for me. > > > > I tried pure 2.6.21-rc4-mm1, +hotfixes, +hotfixes+rsdl33 and at last > > also added above debug patch. > > Thank you very much for the effort! > > > The oops from with the debug-patch added: > > [ 65.426126] Freeing unused kernel memory: 312k freed > > (on the console the system is starting up, getting until "Letting udev > > process events ...") > > [ 66.665611] Unable to handle kernel NULL pointer dereference at > > 0000000000000020 RIP: > > [ 66.682030] [<ffffffff8026167c>] __sched_text_start+0x4dc/0xa0e > > The debug patch didn't do anything. This means it is not an unset bitmap > problem at all otherwise it should have self corrected itself. > > > The system in x86_64, two 2218 on a MCP55 nvidia chipset. > > > > 2.6.21-rc3-mm1 works fine. > > > > (gdb) list *0xffffffff8026167c > > 0xffffffff8026167c is in schedule (kernel/sched.c:3619). > > next = list_entry(queue->next, struct task_struct, run_list); > rq->prio_level = idx; > > > 3614 /* > > 3615 * When the task is chosen it is checked to see if its > > quota has been > > 3616 * added to this runqueue level which is only performed > > once per 3617 * level per major rotation for each running > > task. 3618 */ > > 3619 if (next->rotation != rq->prio_rotation) { > > Urgh. Dereferencing there? That can only be next that's deferencing meaning > the run_list entry is bogus. That should only ever be done under runqueue > lock so I have a race somewhere where it's not. Time for more looking. This is about the only place I can see the run_list is looked at unlocked. Can you see if this simple patch helps? The debug patch is unnecessary now. Thanks! -- Ensure checking task_queued() is only done under runqueue lock. Signed-off-by: Con Kolivas <kernel@kolivas.org> --- kernel/sched.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) Index: linux-2.6.21-rc4-mm1/kernel/sched.c =================================================================== --- linux-2.6.21-rc4-mm1.orig/kernel/sched.c 2007-03-26 08:54:15.000000000 +1000 +++ linux-2.6.21-rc4-mm1/kernel/sched.c 2007-03-26 08:55:21.000000000 +1000 @@ -3421,16 +3421,16 @@ static inline void rotate_runqueue_prior static void task_running_tick(struct rq *rq, struct task_struct *p, int tick) { - if (unlikely(!task_queued(p))) { - /* Task has expired but was not scheduled yet */ - set_tsk_need_resched(p); - return; - } /* SCHED_FIFO tasks never run out of timeslice. */ if (unlikely(p->policy == SCHED_FIFO)) return; spin_lock(&rq->lock); + if (unlikely(!task_queued(p))) { + /* Task has expired but was not scheduled off yet */ + set_tsk_need_resched(p); + goto out_unlock; + } /* * Accounting is performed by both the task and the runqueue. This * allows frequently sleeping tasks to get their proper quota of -- -ck ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: debug rsdl 0.33 2007-03-25 22:59 ` Con Kolivas @ 2007-03-26 7:49 ` Andy Whitcroft 2007-03-26 15:28 ` Andy Whitcroft 0 siblings, 1 reply; 146+ messages in thread From: Andy Whitcroft @ 2007-03-26 7:49 UTC (permalink / raw) To: Con Kolivas Cc: Torsten Kaiser, William Lee Irwin III, Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh Con Kolivas wrote: > This is about the only place I can see the run_list is looked at unlocked. Can > you see if this simple patch helps? The debug patch is unnecessary now. Tests queued with this patch. Will let you know. -apw ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: debug rsdl 0.33 2007-03-26 7:49 ` Andy Whitcroft @ 2007-03-26 15:28 ` Andy Whitcroft 2007-03-26 16:12 ` Con Kolivas 0 siblings, 1 reply; 146+ messages in thread From: Andy Whitcroft @ 2007-03-26 15:28 UTC (permalink / raw) To: Andy Whitcroft Cc: Con Kolivas, Torsten Kaiser, William Lee Irwin III, Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh Andy Whitcroft wrote: > Con Kolivas wrote: > >> This is about the only place I can see the run_list is looked at unlocked. Can >> you see if this simple patch helps? The debug patch is unnecessary now. > > Tests queued with this patch. Will let you know. That patch had no effect on the problem. ... Since then we have performed some more debugging on the issue and it appears that the first stanza in next_dynamic_task is tripping, triggering a "major_priority_rotation" and the resulting runq bitmap indicating there is nothing to run. Discussions with Con seem to indicate that this is not possible :/. Subsequent to that Con suggested testing a refactored RSDL patch. That patch seemed to work on the machine at hand, so tests have been submitted for all the affected machines. http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc4-mm1-rsdl-0.34-test.patch ... Ok, the preliminary results are in and we seem to have good boots in the three machines I was hitting early boot oops. So I think we can say that the new stack is a lot better than the old. Con, have a Tested-by: :/ -apw ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: debug rsdl 0.33 2007-03-26 15:28 ` Andy Whitcroft @ 2007-03-26 16:12 ` Con Kolivas 0 siblings, 0 replies; 146+ messages in thread From: Con Kolivas @ 2007-03-26 16:12 UTC (permalink / raw) To: Andy Whitcroft Cc: Torsten Kaiser, William Lee Irwin III, Andrew Morton, linux-kernel, Steve Fox, Martin J. Bligh On Tuesday 27 March 2007 01:28, Andy Whitcroft wrote: > Andy Whitcroft wrote: > Subsequent to that Con suggested testing a refactored RSDL patch. That > patch seemed to work on the machine at hand, so tests have been > submitted for all the affected machines. > > http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc4-mm1-rsdl-0.34-t >est.patch > > ... > > Ok, the preliminary results are in and we seem to have good boots in the > three machines I was hitting early boot oops. So I think we can say > that the new stack is a lot better than the old. > > Con, have a Tested-by: > :/ > > -apw Well thank you very much indeed. I'm pleased that the code I decided to rip out of the next update also took whatever bug was there with it. Fortunately it also is not dependant on the buggy sched: accurate user accounting patch that I gave up on so here is an incremental from the current -mm queue to this code without the "accurate user accounting patch" component for anyone who's trying to track just what I'm planning on moving forward with. http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc4-mm1/sched-rsdl-sd-0.35-test.patch Summary: 3 files changed, 86 insertions(+), 249 deletions(-) It also makes lists-add_list_splice_tail.patch unnecessary -- -ck ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 [PATCH] init/missing_syscalls.h fix 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton 2007-03-20 7:54 ` 2.6.21-rc4-mm1 Michal Piotrowski 2007-03-20 9:45 ` 2.6.21-rc4-mm1 Andy Whitcroft @ 2007-03-20 10:52 ` Stephane Jourdois 2007-03-20 14:31 ` 2.6.21-rc4-mm1 Jiri Slaby ` (20 subsequent siblings) 23 siblings, 0 replies; 146+ messages in thread From: Stephane Jourdois @ 2007-03-20 10:52 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel, David Woodhouse On Mon, Mar 19, 2007 at 08:56:23PM -0800, Andrew Morton wrote: > > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ [..] > +complain-about-missing-system-calls.patch > +complain-about-missing-system-calls-update.patch Hi, I needed the following patch to fix this compile error (which does not happend at first compile): kwisatz@ambre:/usr/src/linux-2.6.21-rc4-mm1 $ rm init/missing_syscalls.h kwisatz@ambre:/usr/src/linux-2.6.21-rc4-mm1 $ make init CHK include/linux/version.h CHK include/linux/utsrelease.h CHK include/linux/compile.h GEN init/missing_syscalls.h CC init/missing_syscalls.o LD init/built-in.o kwisatz@ambre:/usr/src/linux-2.6.21-rc4-mm1 $ cat init/.missing_syscalls.h.cmd cmd_init/missing_syscalls.h := sed -n '/^\#define/s/[^_]*__NR_\([^[:space:]]*\).*/ \#if !defined (__NR_) \&\& !defined (__IGNORE_) \#warning syscall not implemented \#endif/p' /usr/src/linux-2.6.21-rc4-mm1/include/asm-i386/unistd.h >init/missing_syscalls.h # (note all three \1 missing, replaced by char '^A', not visible here. # note also that my /bin/sh is symlinked to dash (not bash) 0.5.3 kwisatz@ambre:/usr/src/linux-2.6.21-rc4-mm1 $ make init CHK include/linux/version.h CHK include/linux/utsrelease.h init/.missing_syscalls.h.cmd:2: *** séparateur manquant . Arrêt. make: *** [init] Erreur 2 As far as I understand it, Makefile rule cmd_missing_syscalls (from init/Makefile) is used twice in two different ways: - At first compile: - run the command directly from Makefile, - dump this command to init/.missing_syscalls.h.cmd for further use; - At every but first compile: - run existing init/.missing_syscalls.h.cmd Can someone confirm that this is the right way to patch this ? Thanks, - Stéphane. # complain-about-missing-system-calls-fix.patch # Make generation of init/missing_syscalls.h more robust. # Note: This fix is required only for "all but first" compilations, and # perhaps only on some configurations (cf. /bin/sh). Signed-off-by: Stéphane (kwisatz) Jourdois <kwisatz@rubis.org> diff -uNr linux-2.6.21-rc4-mm1.orig/init/Makefile linux-2.6.21-rc4-mm1/init/Makefile --- linux-2.6.21-rc4-mm1.orig/init/Makefile 2007-03-20 09:54:23.000000000 +0100 +++ linux-2.6.21-rc4-mm1/init/Makefile 2007-03-20 11:19:02.000000000 +0100 @@ -35,10 +35,8 @@ quiet_cmd_missing_syscalls = GEN $@ - cmd_missing_syscalls = sed -n '/^\#define/s/[^_]*__NR_\([^[:space:]]*\).*/\ - \#if !defined (__NR_\1) \&\& !defined (__IGNORE_\1)\n\ - \#warning syscall \1 not implemented\n\ - \#endif/p' $(srctree)/include/asm-i386/unistd.h >$@ + cmd_missing_syscalls = sed -n -f scripts/mkmissing_syscalls_h \ + $(srctree)/include/asm-i386/unistd.h >$@ targets += missing_syscalls.h $(obj)/missing_syscalls.h: include/asm-i386/unistd.h $(call if_changed,missing_syscalls) diff -uNr linux-2.6.21-rc4-mm1.orig/scripts/mkmissing_syscalls_h linux-2.6.21-rc4-mm1/scripts/mkmissing_syscalls_h --- linux-2.6.21-rc4-mm1.orig/scripts/mkmissing_syscalls_h 1970-01-01 01:00:00.000000000 +0100 +++ linux-2.6.21-rc4-mm1/scripts/mkmissing_syscalls_h 2007-03-20 11:34:21.000000000 +0100 @@ -0,0 +1,6 @@ +/^\#define/ { + s/[^_]*__NR_\([^[:space:]]*\).*/\ +\#if !defined (__NR_\1) \&\& !defined (__IGNORE_\1)\ +\#warning syscall \1 not implemented\ +\#endif/p +} -- /// Stephane Jourdois /"\ ASCII RIBBON CAMPAIGN \\\ ((( Consultant securite \ / AGAINST HTML MAIL ))) \\\ 24 rue Cauchy X /// \\\ 75015 Paris / \ +33 6 8643 3085 /// ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (2 preceding siblings ...) 2007-03-20 10:52 ` 2.6.21-rc4-mm1 [PATCH] init/missing_syscalls.h fix Stephane Jourdois @ 2007-03-20 14:31 ` Jiri Slaby 2007-03-20 16:09 ` 2.6.21-rc4-mm1 Andrew Morton 2007-03-20 16:36 ` 2.6.21-rc4-mm1 J.A. Magallón ` (19 subsequent siblings) 23 siblings, 1 reply; 146+ messages in thread From: Jiri Slaby @ 2007-03-20 14:31 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel, pavel, linux-pm Andrew Morton napsal(a): > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ I'm getting this while trying to swsusp: Stopping tasks ... Stopping kernel threads timed out after 20 seconds (1 tasks refusing to freeze): swapper Restarting tasks ... done. What to test? Enable PM_DEBUG? regards, -- http://www.fi.muni.cz/~xslaby/ Jiri Slaby faculty of informatics, masaryk university, brno, cz e-mail: jirislaby gmail com, gpg pubkey fingerprint: B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 14:31 ` 2.6.21-rc4-mm1 Jiri Slaby @ 2007-03-20 16:09 ` Andrew Morton 2007-03-20 18:38 ` 2.6.21-rc4-mm1 Pavel Machek 0 siblings, 1 reply; 146+ messages in thread From: Andrew Morton @ 2007-03-20 16:09 UTC (permalink / raw) To: Jiri Slaby; +Cc: linux-kernel, pavel, linux-pm, Rafael J. Wysocki On Tue, 20 Mar 2007 15:31:02 +0100 Jiri Slaby <jirislaby@gmail.com> wrote: > Andrew Morton napsal(a): > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > I'm getting this while trying to swsusp: > Stopping tasks ... > Stopping kernel threads timed out after 20 seconds (1 tasks refusing to freeze): > swapper > Restarting tasks ... done. > > What to test? Enable PM_DEBUG? hm, OK. Rafael has been working on fixing the process freezer and it'll take some time to get it to where we want it to be, I expect. Rafael, I think that we could afford to add heaps of debug in there at this stage to help us track down problems like this. Also, it might be useful to add a temporary /proc/freeze-unfreeze thing which will simply do a freeze/unfreeze cycle. Then we can apply various workloads to the machine while madly stressing the freezer code. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 16:09 ` 2.6.21-rc4-mm1 Andrew Morton @ 2007-03-20 18:38 ` Pavel Machek 2007-03-20 19:40 ` 2.6.21-rc4-mm1 Jiri Slaby 0 siblings, 1 reply; 146+ messages in thread From: Pavel Machek @ 2007-03-20 18:38 UTC (permalink / raw) To: Andrew Morton; +Cc: Jiri Slaby, linux-kernel, linux-pm, Rafael J. Wysocki Hi! > > Andrew Morton napsal(a): > > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > > > I'm getting this while trying to swsusp: > > Stopping tasks ... > > Stopping kernel threads timed out after 20 seconds (1 tasks refusing to freeze): > > swapper > > Restarting tasks ... done. > > > > What to test? Enable PM_DEBUG? Is it repeatable? Freezer normally works better than that. > hm, OK. Rafael has been working on fixing the process freezer and it'll > take some time to get it to where we want it to be, I expect. > Rafael, I think that we could afford to add heaps of debug in there at this > stage to help us track down problems like this. > > Also, it might be useful to add a temporary /proc/freeze-unfreeze thing > which will simply do a freeze/unfreeze cycle. Then we can apply various > workloads to the machine while madly stressing the freezer code. echo testproc > /sys/power/disk; echo disk > /sys/power/state ... is pretty much what you want. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 18:38 ` 2.6.21-rc4-mm1 Pavel Machek @ 2007-03-20 19:40 ` Jiri Slaby 2007-03-20 19:56 ` 2.6.21-rc4-mm1 Pavel Machek 2007-03-20 20:12 ` 2.6.21-rc4-mm1 Rafael J. Wysocki 0 siblings, 2 replies; 146+ messages in thread From: Jiri Slaby @ 2007-03-20 19:40 UTC (permalink / raw) To: Pavel Machek; +Cc: Andrew Morton, linux-kernel, linux-pm, Rafael J. Wysocki Pavel Machek napsal(a): > Hi! > >>> Andrew Morton napsal(a): >>>> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ >>> I'm getting this while trying to swsusp: >>> Stopping tasks ... >>> Stopping kernel threads timed out after 20 seconds (1 tasks refusing to freeze): >>> swapper >>> Restarting tasks ... done. >>> >>> What to test? Enable PM_DEBUG? > > Is it repeatable? Freezer normally works better than that. Yes, at least it happened 3 times consecutively, when I tried to asleep the machine, then I turned it off. >> Also, it might be useful to add a temporary /proc/freeze-unfreeze thing >> which will simply do a freeze/unfreeze cycle. Then we can apply various >> workloads to the machine while madly stressing the freezer code. > > echo testproc > /sys/power/disk; echo disk > /sys/power/state ... is > pretty much what you want. Ok, I'll try this. thanks, -- http://www.fi.muni.cz/~xslaby/ Jiri Slaby faculty of informatics, masaryk university, brno, cz e-mail: jirislaby gmail com, gpg pubkey fingerprint: B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 19:40 ` 2.6.21-rc4-mm1 Jiri Slaby @ 2007-03-20 19:56 ` Pavel Machek 2007-03-20 20:13 ` 2.6.21-rc4-mm1 Jiri Slaby 2007-03-20 20:12 ` 2.6.21-rc4-mm1 Rafael J. Wysocki 1 sibling, 1 reply; 146+ messages in thread From: Pavel Machek @ 2007-03-20 19:56 UTC (permalink / raw) To: Jiri Slaby; +Cc: Andrew Morton, linux-kernel, linux-pm, Rafael J. Wysocki Hi! > >> Also, it might be useful to add a temporary /proc/freeze-unfreeze thing > >> which will simply do a freeze/unfreeze cycle. Then we can apply various > >> workloads to the machine while madly stressing the freezer code. > > > > echo testproc > /sys/power/disk; echo disk > /sys/power/state ... is > > pretty much what you want. > > Ok, I'll try this. It will not help you -- probably -- it is equivalent to just running s2ram. But it should make "successful" testing easier, because you no longer need machine with working suspend to test refrigerator. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 19:56 ` 2.6.21-rc4-mm1 Pavel Machek @ 2007-03-20 20:13 ` Jiri Slaby 2007-03-20 20:21 ` [linux-pm] 2.6.21-rc4-mm1 Pavel Machek 0 siblings, 1 reply; 146+ messages in thread From: Jiri Slaby @ 2007-03-20 20:13 UTC (permalink / raw) To: Pavel Machek; +Cc: Andrew Morton, linux-kernel, linux-pm, Rafael J. Wysocki Pavel Machek napsal(a): > Hi! > >>>> Also, it might be useful to add a temporary /proc/freeze-unfreeze thing >>>> which will simply do a freeze/unfreeze cycle. Then we can apply various >>>> workloads to the machine while madly stressing the freezer code. >>> echo testproc > /sys/power/disk; echo disk > /sys/power/state ... is >>> pretty much what you want. >> Ok, I'll try this. > > It will not help you -- probably -- it is equivalent to just running > s2ram. But it should make "successful" testing easier, because you no > longer need machine with working suspend to test refrigerator. Aha, I didn't read it carefully. Suspend is working, but not in this kernel. I haven't tried s2ram in this version. Should I (I'm away from it) -- would it show something? regards, -- http://www.fi.muni.cz/~xslaby/ Jiri Slaby faculty of informatics, masaryk university, brno, cz e-mail: jirislaby gmail com, gpg pubkey fingerprint: B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1 2007-03-20 20:13 ` 2.6.21-rc4-mm1 Jiri Slaby @ 2007-03-20 20:21 ` Pavel Machek 2007-03-20 20:58 ` Rafael J. Wysocki 0 siblings, 1 reply; 146+ messages in thread From: Pavel Machek @ 2007-03-20 20:21 UTC (permalink / raw) To: Jiri Slaby; +Cc: Andrew Morton, linux-pm, linux-kernel Hi! > >>>> Also, it might be useful to add a temporary /proc/freeze-unfreeze thing > >>>> which will simply do a freeze/unfreeze cycle. Then we can apply various > >>>> workloads to the machine while madly stressing the freezer code. > >>> echo testproc > /sys/power/disk; echo disk > /sys/power/state ... is > >>> pretty much what you want. > >> Ok, I'll try this. > > > > It will not help you -- probably -- it is equivalent to just running > > s2ram. But it should make "successful" testing easier, because you no > > longer need machine with working suspend to test refrigerator. > > Aha, I didn't read it carefully. Suspend is working, but not in this kernel. > I haven't tried s2ram in this version. Should I (I'm away from it) -- would > it show something? No, probably not. git bisect would help, but I guess it is easier to let Rafael sort it out. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1 2007-03-20 20:21 ` [linux-pm] 2.6.21-rc4-mm1 Pavel Machek @ 2007-03-20 20:58 ` Rafael J. Wysocki 2007-03-20 20:58 ` Jiri Slaby 0 siblings, 1 reply; 146+ messages in thread From: Rafael J. Wysocki @ 2007-03-20 20:58 UTC (permalink / raw) To: Pavel Machek; +Cc: Jiri Slaby, Andrew Morton, linux-pm, linux-kernel On Tuesday, 20 March 2007 21:21, Pavel Machek wrote: > Hi! > > > >>>> Also, it might be useful to add a temporary /proc/freeze-unfreeze thing > > >>>> which will simply do a freeze/unfreeze cycle. Then we can apply various > > >>>> workloads to the machine while madly stressing the freezer code. > > >>> echo testproc > /sys/power/disk; echo disk > /sys/power/state ... is > > >>> pretty much what you want. > > >> Ok, I'll try this. > > > > > > It will not help you -- probably -- it is equivalent to just running > > > s2ram. But it should make "successful" testing easier, because you no > > > longer need machine with working suspend to test refrigerator. > > > > Aha, I didn't read it carefully. Suspend is working, but not in this kernel. > > I haven't tried s2ram in this version. Should I (I'm away from it) -- would > > it show something? > > No, probably not. git bisect would help, but I guess it is easier to > let Rafael sort it out. Actually, the problem is 100% reproducible on my system too and I doubt it's caused by the recent freezer patches. Investigating. Rafael ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1 2007-03-20 20:58 ` Rafael J. Wysocki @ 2007-03-20 20:58 ` Jiri Slaby 2007-03-20 21:06 ` Rafael J. Wysocki 0 siblings, 1 reply; 146+ messages in thread From: Jiri Slaby @ 2007-03-20 20:58 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: Pavel Machek, Andrew Morton, linux-pm, linux-kernel Rafael J. Wysocki napsal(a): > Actually, the problem is 100% reproducible on my system too and I doubt it's > caused by the recent freezer patches. I don't know what exactly do you mean by recent, but 2.6.21-rc3-mm2 works for me. regards, -- http://www.fi.muni.cz/~xslaby/ Jiri Slaby faculty of informatics, masaryk university, brno, cz e-mail: jirislaby gmail com, gpg pubkey fingerprint: B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1 2007-03-20 20:58 ` Jiri Slaby @ 2007-03-20 21:06 ` Rafael J. Wysocki [not found] ` <200703210149.33240.rjw@sisk.pl> 0 siblings, 1 reply; 146+ messages in thread From: Rafael J. Wysocki @ 2007-03-20 21:06 UTC (permalink / raw) To: Jiri Slaby; +Cc: Pavel Machek, Andrew Morton, linux-pm, linux-kernel On Tuesday, 20 March 2007 21:58, Jiri Slaby wrote: > Rafael J. Wysocki napsal(a): > > Actually, the problem is 100% reproducible on my system too and I doubt it's > > caused by the recent freezer patches. > > I don't know what exactly do you mean by recent, but 2.6.21-rc3-mm2 works > for me. Thanks for the confirmation. The patches I was talking about had already been in 2.6.21-rc3-mm2, so the reason of this failure must be different. Greetings, Rafael ^ permalink raw reply [flat|nested] 146+ messages in thread
[parent not found: <200703210149.33240.rjw@sisk.pl>]
* Re: [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken [not found] ` <200703210149.33240.rjw@sisk.pl> @ 2007-03-21 1:23 ` Eric W. Biederman 2007-03-21 2:47 ` sukadev ` (2 more replies) 0 siblings, 3 replies; 146+ messages in thread From: Eric W. Biederman @ 2007-03-21 1:23 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Jiri Slaby, Andrew Morton, Pavel Machek, linux-pm, linux-kernel, Sukadev Bhattiprolu, Oleg Nesterov "Rafael J. Wysocki" <rjw@sisk.pl> writes: > On Tuesday, 20 March 2007 22:06, Rafael J. Wysocki wrote: >> On Tuesday, 20 March 2007 21:58, Jiri Slaby wrote: >> > Rafael J. Wysocki napsal(a): >> > > Actually, the problem is 100% reproducible on my system too and I doubt > it's >> > > caused by the recent freezer patches. >> > >> > I don't know what exactly do you mean by recent, but 2.6.21-rc3-mm2 works >> > for me. >> >> Thanks for the confirmation. >> >> The patches I was talking about had already been in 2.6.21-rc3-mm2, so the >> reason of this failure must be different. > > Bisection shows that the freezing of processes has been broken by one of the > patches: > > remove-the-likelypid-check-in-copy_process.patch Grr. Oleg's review of remove-the-likelypid-check-in-copy-process showed it to be questionable (and it was just an optimization) so we can get rid of that one easily. Although all it did that was really questionable was add the idle process to the global process list and bump a process count when we forked the idle process. Not dramatically dangerous things. > use-task_pgrp-task_session-in-copy_process.patch As I recall that patch was pretty trivial, and shouldn't have anything to do with the freezer. The process freezer doesn't care about pids does it? Eric ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken 2007-03-21 1:23 ` [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken Eric W. Biederman @ 2007-03-21 2:47 ` sukadev 2007-03-21 3:13 ` Nigel Cunningham 2007-03-21 12:08 ` Rafael J. Wysocki 2 siblings, 0 replies; 146+ messages in thread From: sukadev @ 2007-03-21 2:47 UTC (permalink / raw) To: Eric W. Biederman Cc: Rafael J. Wysocki, Jiri Slaby, Andrew Morton, Pavel Machek, linux-pm, linux-kernel, Oleg Nesterov Eric W. Biederman [ebiederm@xmission.com] wrote: | "Rafael J. Wysocki" <rjw@sisk.pl> writes: | | > On Tuesday, 20 March 2007 22:06, Rafael J. Wysocki wrote: | >> On Tuesday, 20 March 2007 21:58, Jiri Slaby wrote: | >> > Rafael J. Wysocki napsal(a): | >> > > Actually, the problem is 100% reproducible on my system too and I doubt | > it's | >> > > caused by the recent freezer patches. | >> > | >> > I don't know what exactly do you mean by recent, but 2.6.21-rc3-mm2 works | >> > for me. | >> | >> Thanks for the confirmation. | >> | >> The patches I was talking about had already been in 2.6.21-rc3-mm2, so the | >> reason of this failure must be different. | > | > Bisection shows that the freezing of processes has been broken by one of the | > patches: | > | > remove-the-likelypid-check-in-copy_process.patch | | Grr. Oleg's review of remove-the-likelypid-check-in-copy-process | showed it to be questionable (and it was just an optimization) | so we can get rid of that one easily. | | Although all it did that was really questionable was add | the idle process to the global process list and bump a process | count when we forked the idle process. Not dramatically dangerous | things. | | > use-task_pgrp-task_session-in-copy_process.patch | | As I recall that patch was pretty trivial, and shouldn't have | anything to do with the freezer. The process freezer doesn't care | about pids does it? Yes. I think this one is trivial too. Here is the effective change in copy_process(): - attach_pid(p, PIDTYPE_PGID, find_pid(pgid)); - attach_pid(p, PIDTYPE_SID, find_pid(sid)); + attach_pid(p, PIDTYPE_PGID, task_pgrp(current)); + attach_pid(p, PIDTYPE_SID, task_session(current)); | | Eric ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken 2007-03-21 1:23 ` [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken Eric W. Biederman 2007-03-21 2:47 ` sukadev @ 2007-03-21 3:13 ` Nigel Cunningham 2007-03-21 14:23 ` Oleg Nesterov 2007-03-21 12:08 ` Rafael J. Wysocki 2 siblings, 1 reply; 146+ messages in thread From: Nigel Cunningham @ 2007-03-21 3:13 UTC (permalink / raw) To: Eric W. Biederman Cc: Rafael J. Wysocki, Sukadev Bhattiprolu, Jiri Slaby, Pavel Machek, Andrew Morton, linux-pm, linux-kernel, Oleg Nesterov Hi. On Tue, 2007-03-20 at 19:23 -0600, Eric W. Biederman wrote: > "Rafael J. Wysocki" <rjw@sisk.pl> writes: > > > On Tuesday, 20 March 2007 22:06, Rafael J. Wysocki wrote: > >> On Tuesday, 20 March 2007 21:58, Jiri Slaby wrote: > >> > Rafael J. Wysocki napsal(a): > >> > > Actually, the problem is 100% reproducible on my system too and I doubt > > it's > >> > > caused by the recent freezer patches. > >> > > >> > I don't know what exactly do you mean by recent, but 2.6.21-rc3-mm2 works > >> > for me. > >> > >> Thanks for the confirmation. > >> > >> The patches I was talking about had already been in 2.6.21-rc3-mm2, so the > >> reason of this failure must be different. > > > > Bisection shows that the freezing of processes has been broken by one of the > > patches: > > > > remove-the-likelypid-check-in-copy_process.patch > > Grr. Oleg's review of remove-the-likelypid-check-in-copy-process > showed it to be questionable (and it was just an optimization) > so we can get rid of that one easily. > > Although all it did that was really questionable was add > the idle process to the global process list and bump a process > count when we forked the idle process. Not dramatically dangerous > things. > > > use-task_pgrp-task_session-in-copy_process.patch > > As I recall that patch was pretty trivial, and shouldn't have > anything to do with the freezer. The process freezer doesn't care > about pids does it? Could the freezer code be trying to freeze the idle thread as a result? Regards, Nigel ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken 2007-03-21 3:13 ` Nigel Cunningham @ 2007-03-21 14:23 ` Oleg Nesterov 2007-03-21 14:45 ` Rafael J. Wysocki 0 siblings, 1 reply; 146+ messages in thread From: Oleg Nesterov @ 2007-03-21 14:23 UTC (permalink / raw) To: Nigel Cunningham Cc: Eric W. Biederman, Rafael J. Wysocki, Sukadev Bhattiprolu, Jiri Slaby, Pavel Machek, Andrew Morton, linux-pm, linux-kernel On 03/21, Nigel Cunningham wrote: > > On Tue, 2007-03-20 at 19:23 -0600, Eric W. Biederman wrote: > > >> > Rafael J. Wysocki napsal(a): > > > > > > Bisection shows that the freezing of processes has been broken by one of the > > > patches: > > > > > > remove-the-likelypid-check-in-copy_process.patch > > > > Grr. Oleg's review of remove-the-likelypid-check-in-copy-process > > showed it to be questionable (and it was just an optimization) > > so we can get rid of that one easily. > > > > Although all it did that was really questionable was add > > the idle process to the global process list and bump a process > > count when we forked the idle process. Not dramatically dangerous > > things. > > Could the freezer code be trying to freeze the idle thread as a result? Yes. remove-the-likelypid-check-in-copy_process.patch make idle threads visible to for_each_process/do_each_thread. Note also that idle threads have ->mm != NULL. freezer, oom_kill, move_task_off_dead_cpu, etc, should not see idle threads, but they do now. Oleg. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken 2007-03-21 14:23 ` Oleg Nesterov @ 2007-03-21 14:45 ` Rafael J. Wysocki 2007-03-21 16:20 ` Andrew Morton 0 siblings, 1 reply; 146+ messages in thread From: Rafael J. Wysocki @ 2007-03-21 14:45 UTC (permalink / raw) To: Oleg Nesterov, Andrew Morton Cc: Nigel Cunningham, Eric W. Biederman, Sukadev Bhattiprolu, Jiri Slaby, Pavel Machek, linux-pm, linux-kernel On Wednesday, 21 March 2007 15:23, Oleg Nesterov wrote: > On 03/21, Nigel Cunningham wrote: > > > > On Tue, 2007-03-20 at 19:23 -0600, Eric W. Biederman wrote: > > > >> > Rafael J. Wysocki napsal(a): > > > > > > > > Bisection shows that the freezing of processes has been broken by one of the > > > > patches: > > > > > > > > remove-the-likelypid-check-in-copy_process.patch > > > > > > Grr. Oleg's review of remove-the-likelypid-check-in-copy-process > > > showed it to be questionable (and it was just an optimization) > > > so we can get rid of that one easily. > > > > > > Although all it did that was really questionable was add > > > the idle process to the global process list and bump a process > > > count when we forked the idle process. Not dramatically dangerous > > > things. > > > > Could the freezer code be trying to freeze the idle thread as a result? > > Yes. remove-the-likelypid-check-in-copy_process.patch make idle threads > visible to for_each_process/do_each_thread. Note also that idle threads > have ->mm != NULL. freezer, oom_kill, move_task_off_dead_cpu, etc, should > not see idle threads, but they do now. Well, I think this is a good enough reason for asking Andrew to drop this patch. Greetings, Rafael ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken 2007-03-21 14:45 ` Rafael J. Wysocki @ 2007-03-21 16:20 ` Andrew Morton 2007-03-21 16:55 ` Oleg Nesterov 0 siblings, 1 reply; 146+ messages in thread From: Andrew Morton @ 2007-03-21 16:20 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Oleg Nesterov, Nigel Cunningham, Eric W. Biederman, Sukadev Bhattiprolu, Jiri Slaby, Pavel Machek, linux-pm, linux-kernel On Wed, 21 Mar 2007 15:45:16 +0100 "Rafael J. Wysocki" <rjw@sisk.pl> wrote: > On Wednesday, 21 March 2007 15:23, Oleg Nesterov wrote: > > On 03/21, Nigel Cunningham wrote: > > > > > > On Tue, 2007-03-20 at 19:23 -0600, Eric W. Biederman wrote: > > > > >> > Rafael J. Wysocki napsal(a): > > > > > > > > > > Bisection shows that the freezing of processes has been broken by one of the > > > > > patches: > > > > > > > > > > remove-the-likelypid-check-in-copy_process.patch > > > > > > > > Grr. Oleg's review of remove-the-likelypid-check-in-copy-process > > > > showed it to be questionable (and it was just an optimization) > > > > so we can get rid of that one easily. > > > > > > > > Although all it did that was really questionable was add > > > > the idle process to the global process list and bump a process > > > > count when we forked the idle process. Not dramatically dangerous > > > > things. > > > > > > Could the freezer code be trying to freeze the idle thread as a result? > > > > Yes. remove-the-likelypid-check-in-copy_process.patch make idle threads > > visible to for_each_process/do_each_thread. Note also that idle threads > > have ->mm != NULL. freezer, oom_kill, move_task_off_dead_cpu, etc, should > > not see idle threads, but they do now. > > Well, I think this is a good enough reason for asking Andrew to drop this > patch. Or we change the freezer to skip pid==0 tasks. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken 2007-03-21 16:20 ` Andrew Morton @ 2007-03-21 16:55 ` Oleg Nesterov 2007-03-21 17:08 ` Andrew Morton 2007-03-21 17:15 ` Oleg Nesterov 0 siblings, 2 replies; 146+ messages in thread From: Oleg Nesterov @ 2007-03-21 16:55 UTC (permalink / raw) To: Andrew Morton Cc: Rafael J. Wysocki, Nigel Cunningham, Eric W. Biederman, Sukadev Bhattiprolu, Jiri Slaby, Pavel Machek, linux-pm, linux-kernel On 03/21, Andrew Morton wrote: > > On Wed, 21 Mar 2007 15:45:16 +0100 "Rafael J. Wysocki" <rjw@sisk.pl> wrote: > > > On Wednesday, 21 March 2007 15:23, Oleg Nesterov wrote: > > > > > > > > Could the freezer code be trying to freeze the idle thread as a result? > > > > > > Yes. remove-the-likelypid-check-in-copy_process.patch make idle threads > > > visible to for_each_process/do_each_thread. Note also that idle threads > > > have ->mm != NULL. freezer, oom_kill, move_task_off_dead_cpu, etc, should > > > not see idle threads, but they do now. > > > > Well, I think this is a good enough reason for asking Andrew to drop this > > patch. > > Or we change the freezer to skip pid==0 tasks. I strongly disagree. In that case we should audit all users of for_each_process. Imho, this change is too dangerous. Actually, I personally think it is very good that idle threads are special and not visible, imho we should not change this. Btw. Rafael, Andrew, what about [PATCH] Make XFS workqueues nonfreezable http://marc.info/?l=linux-kernel&m=117270675922229 , don't you think this should go to 2.6.21 ? Oleg. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken 2007-03-21 16:55 ` Oleg Nesterov @ 2007-03-21 17:08 ` Andrew Morton 2007-03-21 18:07 ` sukadev 2007-03-21 17:15 ` Oleg Nesterov 1 sibling, 1 reply; 146+ messages in thread From: Andrew Morton @ 2007-03-21 17:08 UTC (permalink / raw) To: Oleg Nesterov, David Chinner Cc: Rafael J. Wysocki, Nigel Cunningham, Eric W. Biederman, Sukadev Bhattiprolu, Jiri Slaby, Pavel Machek, linux-pm, linux-kernel On Wed, 21 Mar 2007 19:55:34 +0300 Oleg Nesterov <oleg@tv-sign.ru> wrote: > On 03/21, Andrew Morton wrote: > > > > On Wed, 21 Mar 2007 15:45:16 +0100 "Rafael J. Wysocki" <rjw@sisk.pl> wrote: > > > > > On Wednesday, 21 March 2007 15:23, Oleg Nesterov wrote: > > > > > > > > > > Could the freezer code be trying to freeze the idle thread as a result? > > > > > > > > Yes. remove-the-likelypid-check-in-copy_process.patch make idle threads > > > > visible to for_each_process/do_each_thread. Note also that idle threads > > > > have ->mm != NULL. freezer, oom_kill, move_task_off_dead_cpu, etc, should > > > > not see idle threads, but they do now. > > > > > > Well, I think this is a good enough reason for asking Andrew to drop this > > > patch. > > > > Or we change the freezer to skip pid==0 tasks. > > I strongly disagree. In that case we should audit all users of for_each_process. > Imho, this change is too dangerous. Actually, I personally think it is very good > that idle threads are special and not visible, imho we should not change this. OK, I'll tentatively drop remove-the-likelypid-check-in-copy_process.patch > Btw. Rafael, Andrew, what about > > [PATCH] Make XFS workqueues nonfreezable > http://marc.info/?l=linux-kernel&m=117270675922229 > > , don't you think this should go to 2.6.21 ? > I've sent it to the XFS guys a couple of times, but their black hole is one of the deeper ones. David? ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken 2007-03-21 17:08 ` Andrew Morton @ 2007-03-21 18:07 ` sukadev 2007-03-21 18:16 ` Eric W. Biederman 0 siblings, 1 reply; 146+ messages in thread From: sukadev @ 2007-03-21 18:07 UTC (permalink / raw) To: Andrew Morton Cc: Oleg Nesterov, David Chinner, Rafael J. Wysocki, Nigel Cunningham, Eric W. Biederman, Jiri Slaby, Pavel Machek, linux-pm, linux-kernel Andrew Morton [akpm@linux-foundation.org] wrote: | On Wed, 21 Mar 2007 19:55:34 +0300 Oleg Nesterov <oleg@tv-sign.ru> wrote: | | > On 03/21, Andrew Morton wrote: | > > | > > On Wed, 21 Mar 2007 15:45:16 +0100 "Rafael J. Wysocki" <rjw@sisk.pl> wrote: | > > | > > > On Wednesday, 21 March 2007 15:23, Oleg Nesterov wrote: | > > > > > | > > > > > Could the freezer code be trying to freeze the idle thread as a result? | > > > > | > > > > Yes. remove-the-likelypid-check-in-copy_process.patch make idle threads | > > > > visible to for_each_process/do_each_thread. Note also that idle threads | > > > > have ->mm != NULL. freezer, oom_kill, move_task_off_dead_cpu, etc, should | > > > > not see idle threads, but they do now. | > > > | > > > Well, I think this is a good enough reason for asking Andrew to drop this | > > > patch. | > > | > > Or we change the freezer to skip pid==0 tasks. | > | > I strongly disagree. In that case we should audit all users of for_each_process. | > Imho, this change is too dangerous. Actually, I personally think it is very good | > that idle threads are special and not visible, imho we should not change this. | | OK, I'll tentatively drop remove-the-likelypid-check-in-copy_process.patch Yes. Pls drop it for now. Here is the slightly modified use-task_pgrp-task_session-in-copy_process.patch This applies cleanly with remove-the-likelypid-check-in-copy_process.patch removed. --- From: Sukadev Bhattiprolu <sukadev@us.ibm.com> Subject: [PATCH] Use task_pgrp() task_session() in copy_process(). Use task_pgrp() and task_session() in copy_process(), and avoid find_pid() call when attaching the task to its process group and session. Signed-off-by: Sukadev Bhattiprolu <sukadev@us.ibm.com> --- kernel/fork.c | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) Index: lx26-21-rc3-mm2/kernel/fork.c =================================================================== --- lx26-21-rc3-mm2.orig/kernel/fork.c 2007-03-21 10:51:44.000000000 -0700 +++ lx26-21-rc3-mm2/kernel/fork.c 2007-03-21 10:53:48.000000000 -0700 @@ -1253,14 +1253,11 @@ static struct task_struct *copy_process( tracehook_init_task(p); if (thread_group_leader(p)) { - pid_t pgid = process_group(current); - pid_t sid = process_session(current); - p->signal->tty = current->signal->tty; - p->signal->pgrp = pgid; + p->signal->pgrp = process_group(current); set_signal_session(p->signal, process_session(current)); - attach_pid(p, PIDTYPE_PGID, find_pid(pgid)); - attach_pid(p, PIDTYPE_SID, find_pid(sid)); + attach_pid(p, PIDTYPE_PGID, task_pgrp(current)); + attach_pid(p, PIDTYPE_SID, task_session(current)); list_add_tail_rcu(&p->tasks, &init_task.tasks); __get_cpu_var(process_counts)++; ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken 2007-03-21 18:07 ` sukadev @ 2007-03-21 18:16 ` Eric W. Biederman 2007-03-21 18:23 ` sukadev 0 siblings, 1 reply; 146+ messages in thread From: Eric W. Biederman @ 2007-03-21 18:16 UTC (permalink / raw) To: sukadev Cc: Andrew Morton, Oleg Nesterov, David Chinner, Rafael J. Wysocki, Nigel Cunningham, Jiri Slaby, Pavel Machek, linux-pm, linux-kernel While we are on the topic. What became of the notion of zeroing the session and process group values for the init_task? Eric ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken 2007-03-21 18:16 ` Eric W. Biederman @ 2007-03-21 18:23 ` sukadev 0 siblings, 0 replies; 146+ messages in thread From: sukadev @ 2007-03-21 18:23 UTC (permalink / raw) To: Eric W. Biederman Cc: Andrew Morton, Oleg Nesterov, David Chinner, Rafael J. Wysocki, Nigel Cunningham, Jiri Slaby, Pavel Machek, linux-pm, linux-kernel Eric W. Biederman [ebiederm@xmission.com] wrote: | | While we are on the topic. What became of the notion of zeroing the | session and process group values for the init_task? I just sent that patch a few minutes ago. | | Eric ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken 2007-03-21 16:55 ` Oleg Nesterov 2007-03-21 17:08 ` Andrew Morton @ 2007-03-21 17:15 ` Oleg Nesterov 1 sibling, 0 replies; 146+ messages in thread From: Oleg Nesterov @ 2007-03-21 17:15 UTC (permalink / raw) To: Andrew Morton Cc: Rafael J. Wysocki, Nigel Cunningham, Eric W. Biederman, Sukadev Bhattiprolu, Jiri Slaby, Pavel Machek, linux-pm, linux-kernel On 03/21, Oleg Nesterov wrote: > > On 03/21, Andrew Morton wrote: > > > > On Wed, 21 Mar 2007 15:45:16 +0100 "Rafael J. Wysocki" <rjw@sisk.pl> wrote: > > > > > On Wednesday, 21 March 2007 15:23, Oleg Nesterov wrote: > > > > > > > > > > Could the freezer code be trying to freeze the idle thread as a result? > > > > > > > > Yes. remove-the-likelypid-check-in-copy_process.patch make idle threads > > > > visible to for_each_process/do_each_thread. Note also that idle threads > > > > have ->mm != NULL. freezer, oom_kill, move_task_off_dead_cpu, etc, should > > > > not see idle threads, but they do now. > > > > > > Well, I think this is a good enough reason for asking Andrew to drop this > > > patch. > > > > Or we change the freezer to skip pid==0 tasks. > > I strongly disagree. In that case we should audit all users of for_each_process. Just in case, this is not the only problem with this patch. The things like attach_pid(PIDTYPE_PGID/PIDTYPE_SID) or add_parent() are wrong for the idle threads unless the parent is "swapper". But this is not always so. Oleg. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken 2007-03-21 1:23 ` [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken Eric W. Biederman 2007-03-21 2:47 ` sukadev 2007-03-21 3:13 ` Nigel Cunningham @ 2007-03-21 12:08 ` Rafael J. Wysocki 2 siblings, 0 replies; 146+ messages in thread From: Rafael J. Wysocki @ 2007-03-21 12:08 UTC (permalink / raw) To: Eric W. Biederman Cc: Jiri Slaby, Andrew Morton, Pavel Machek, linux-pm, linux-kernel, Sukadev Bhattiprolu, Oleg Nesterov, Nigel Cunningham On Wednesday, 21 March 2007 02:23, Eric W. Biederman wrote: > "Rafael J. Wysocki" <rjw@sisk.pl> writes: > > > On Tuesday, 20 March 2007 22:06, Rafael J. Wysocki wrote: > >> On Tuesday, 20 March 2007 21:58, Jiri Slaby wrote: > >> > Rafael J. Wysocki napsal(a): > >> > > Actually, the problem is 100% reproducible on my system too and I doubt > > it's > >> > > caused by the recent freezer patches. > >> > > >> > I don't know what exactly do you mean by recent, but 2.6.21-rc3-mm2 works > >> > for me. > >> > >> Thanks for the confirmation. > >> > >> The patches I was talking about had already been in 2.6.21-rc3-mm2, so the > >> reason of this failure must be different. > > > > Bisection shows that the freezing of processes has been broken by one of the > > patches: > > > > remove-the-likelypid-check-in-copy_process.patch > > Grr. Oleg's review of remove-the-likelypid-check-in-copy-process > showed it to be questionable (and it was just an optimization) > so we can get rid of that one easily. > > Although all it did that was really questionable was add > the idle process to the global process list and bump a process > count when we forked the idle process. Not dramatically dangerous > things. I think this patch is the culprit, though, as it seems that the freezer tries to freeze the idle process and fails. Yesterday I didn't have the time to figure out the exact reason, I'll try to look at it later today. > > use-task_pgrp-task_session-in-copy_process.patch > > As I recall that patch was pretty trivial, and shouldn't have > anything to do with the freezer. The process freezer doesn't care > about pids does it? No, it doesn't, at least not directly. I'll try to run the kernel with this change and without remove-the-likelypid-check-in-copy_process.patch . Greetings, Rafael ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 19:40 ` 2.6.21-rc4-mm1 Jiri Slaby 2007-03-20 19:56 ` 2.6.21-rc4-mm1 Pavel Machek @ 2007-03-20 20:12 ` Rafael J. Wysocki 1 sibling, 0 replies; 146+ messages in thread From: Rafael J. Wysocki @ 2007-03-20 20:12 UTC (permalink / raw) To: Jiri Slaby; +Cc: Pavel Machek, Andrew Morton, linux-kernel, linux-pm On Tuesday, 20 March 2007 20:40, Jiri Slaby wrote: > Pavel Machek napsal(a): > > Hi! > > > >>> Andrew Morton napsal(a): > >>>> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > >>> I'm getting this while trying to swsusp: > >>> Stopping tasks ... > >>> Stopping kernel threads timed out after 20 seconds (1 tasks refusing to freeze): > >>> swapper > >>> Restarting tasks ... done. > >>> > >>> What to test? Enable PM_DEBUG? > > > > Is it repeatable? Freezer normally works better than that. > > Yes, at least it happened 3 times consecutively, when I tried to asleep the > machine, then I turned it off. > > >> Also, it might be useful to add a temporary /proc/freeze-unfreeze thing > >> which will simply do a freeze/unfreeze cycle. Then we can apply various > >> workloads to the machine while madly stressing the freezer code. > > > > echo testproc > /sys/power/disk; echo disk > /sys/power/state ... is > > pretty much what you want. > > Ok, I'll try this. Can I see .config please? Rafael ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (3 preceding siblings ...) 2007-03-20 14:31 ` 2.6.21-rc4-mm1 Jiri Slaby @ 2007-03-20 16:36 ` J.A. Magallón 2007-03-21 0:14 ` 2.6.21-rc4-mm1 J.A. Magallón 2007-03-20 17:31 ` 2.6.21-rc4-mm1 Randy Dunlap ` (18 subsequent siblings) 23 siblings, 1 reply; 146+ messages in thread From: J.A. Magallón @ 2007-03-20 16:36 UTC (permalink / raw) To: Linux-Kernel, On Mon, 19 Mar 2007 20:56:23 -0800, Andrew Morton <akpm@linux-foundation.org> wrote: > > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > Will appear later at > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > (oops, I forgot LKML) I have no udev events for my dvd-rw... When I insert a disc in the dvd reader: werewolf:~# udevmonitor udevmonitor prints the received event from the kernel [UEVENT] and the event which udev sends out after rule processing [UDEV] UEVENT[1174385162.607021] mount /block/sr1 (block) UDEV [1174385162.610056] mount /block/sr1 (block) If I insert it in the dvd-rw drive, nothing happens. extracts from dmesg: (I have just noticed the message for the 40 wire cable, I will check) (btw, why the h**l ata busses start nubering in 1 and scsi ones in 0 :((((, it ata also begun in 0 life will be much easier...) ata_piix 0000:00:1f.1: version 2.10ac1 ata1: PATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001f000 irq 14 ata2: PATA max UDMA/133 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001f008 irq 15 scsi0 : ata_piix ata1.00: ATAPI, max UDMA/33 ata1.01: ATAPI, max MWDMA0, CDB intr ata1.00: configured for UDMA/33 ata1.01: configured for PIO3 scsi1 : ata_piix ata2.00: ATA-6: ST3120022A, 3.06, max UDMA/100 ata2.00: 234441648 sectors, multi 16: LBA48 ata2.01: ATAPI, max UDMA/33 ata2.00: limited to UDMA/33 due to 40-wire cable ata2.00: configured for UDMA/33 ata2.01: configured for UDMA/33 scsi 0:0:0:0: CD-ROM HL-DT-ST DVDRAM GSA-H10N JL10 PQ: 0 ANSI: 5 sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 0:0:0:0: Attached scsi CD-ROM sr0 scsi 0:0:1:0: Direct-Access IOMEGA ZIP 250 51.G PQ: 0 ANSI: 5 sd 0:0:1:0: [sda] Attached SCSI removable disk scsi 1:0:0:0: Direct-Access ATA ST3120022A 3.06 PQ: 0 ANSI: 5 sd 1:0:0:0: [sdb] 234441648 512-byte hardware sectors (120034 MB) sd 1:0:0:0: [sdb] Attached SCSI disk scsi 1:0:1:0: CD-ROM TOSHIBA DVD-ROM SD-M1712 1004 PQ: 0 ANSI: 5 sr1: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray sr 1:0:1:0: Attached scsi CD-ROM sr1 ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ] ata3: SATA max UDMA/133 cmd 0x0001c000 ctl 0x0001c402 bmdma 0x0001d000 irq 18 ata4: SATA max UDMA/133 cmd 0x0001c800 ctl 0x0001cc02 bmdma 0x0001d008 irq 18 scsi2 : ata_piix ata3.00: ATA-6: ST3200822AS, 3.01, max UDMA/133 ata3.00: 390721968 sectors, multi 16: LBA48 ata3.00: configured for UDMA/133 scsi3 : ata_piix ATA: abnormal status 0x7F on port 0x0001c807 scsi 2:0:0:0: Direct-Access ATA ST3200822AS 3.01 PQ: 0 ANSI: 5 sd 2:0:0:0: [sdc] 390721968 512-byte hardware sectors (200050 MB) sd 2:0:0:0: [sdc] Write Protect is off sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 2:0:0:0: [sdc] 390721968 512-byte hardware sectors (200050 MB) sd 2:0:0:0: [sdc] Write Protect is off sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdc: sdc1 sdc2 sdc3 sd 2:0:0:0: [sdc] Attached SCSI disk -- J.A. Magallon <jamagallon()ono!com> \ Software is like sex: \ It's better when it's free Mandriva Linux release 2007.1 (Cooker) for i586 Linux 2.6.20-jam05 (gcc 4.1.2 20070302 (prerelease) (4.1.2-1mdv2007.1)) #1 SMP PREEMPT ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 16:36 ` 2.6.21-rc4-mm1 J.A. Magallón @ 2007-03-21 0:14 ` J.A. Magallón 0 siblings, 0 replies; 146+ messages in thread From: J.A. Magallón @ 2007-03-21 0:14 UTC (permalink / raw) To: Linux-Kernel, On Tue, 20 Mar 2007 17:36:57 +0100, "J.A. Magallón" <jamagallon@ono.com> wrote: > On Mon, 19 Mar 2007 20:56:23 -0800, Andrew Morton <akpm@linux-foundation.org> wrote: > > > > > Temporarily at > > > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > > > Will appear later at > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > > > > (oops, I forgot LKML) > > I have no udev events for my dvd-rw... > When I insert a disc in the dvd reader: > > werewolf:~# udevmonitor > udevmonitor prints the received event from the kernel [UEVENT] > and the event which udev sends out after rule processing [UDEV] > > UEVENT[1174385162.607021] mount /block/sr1 (block) > UDEV [1174385162.610056] mount /block/sr1 (block) > > If I insert it in the dvd-rw drive, nothing happens. > I realized that my scsi devices were like this: werewolf:~# lsscsi [0:0:0:0] cd/dvd HL-DT-ST DVDRAM GSA-H10N JL10 /dev/.tmp-11-0 [0:0:1:0] disk IOMEGA ZIP 250 51.G /dev/sda [1:0:0:0] disk ATA ST3120022A 3.06 /dev/sdb [1:0:1:0] cd/dvd TOSHIBA DVD-ROM SD-M1712 1004 /dev/.tmp-11-1 [2:0:0:0] disk ATA ST3200822AS 3.01 /dev/sdc [7:0:0:0] disk LG USBDrive 1100 /dev/sdd After a service udev force-reload: werewolf:~# lsscsi [0:0:0:0] cd/dvd HL-DT-ST DVDRAM GSA-H10N JL10 /dev/sr0 [0:0:1:0] disk IOMEGA ZIP 250 51.G /dev/sda [1:0:0:0] disk ATA ST3120022A 3.06 /dev/sdb [1:0:1:0] cd/dvd TOSHIBA DVD-ROM SD-M1712 1004 /dev/sr1 [2:0:0:0] disk ATA ST3200822AS 3.01 /dev/sdc [7:0:0:0] disk LG USBDrive 1100 /dev/sdd If I insert a disc in /dev/sr1 and eject it: werewolf:~# lsscsi [0:0:0:0] cd/dvd HL-DT-ST DVDRAM GSA-H10N JL10 /dev/sr0 [0:0:1:0] disk IOMEGA ZIP 250 51.G /dev/sda [1:0:0:0] disk ATA ST3120022A 3.06 /dev/sdb [1:0:1:0] cd/dvd TOSHIBA DVD-ROM SD-M1712 1004 /dev/.tmp-11-1 [2:0:0:0] disk ATA ST3200822AS 3.01 /dev/sdc [7:0:0:0] disk LG USBDrive 1100 /dev/sdd If I reload the disc in the TOSHIBA, it is automounted but the strange device is still there. Trying with /dev/sr0 still gives no events. What is happening here ? It is the kernel or is udev setup ? TIA -- J.A. Magallon <jamagallon()ono!com> \ Software is like sex: \ It's better when it's free Mandriva Linux release 2007.1 (Cooker) for i586 Linux 2.6.20-jam05 (gcc 4.1.2 20070302 (prerelease) (4.1.2-1mdv2007.1)) #2 SMP PREEMPT ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (4 preceding siblings ...) 2007-03-20 16:36 ` 2.6.21-rc4-mm1 J.A. Magallón @ 2007-03-20 17:31 ` Randy Dunlap 2007-03-20 19:20 ` 2.6.21-rc4-mm1 Kees Cook 2007-03-20 18:09 ` [PATCH] utrace: make an inline void Randy Dunlap ` (17 subsequent siblings) 23 siblings, 1 reply; 146+ messages in thread From: Randy Dunlap @ 2007-03-20 17:31 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel, kees On Mon, 19 Mar 2007 20:56:23 -0800 Andrew Morton wrote: > > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > Will appear later at > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > Changes since 2.6.21-rc3-mm1: LD .tmp_vmlinux1 kernel/built-in.o:(.data+0xfc0): undefined reference to `maps_protect' make: *** [.tmp_vmlinux1] Error 1 with CONFIG_PROC_FS=n Kees? --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 17:31 ` 2.6.21-rc4-mm1 Randy Dunlap @ 2007-03-20 19:20 ` Kees Cook 2007-03-20 20:42 ` 2.6.21-rc4-mm1 Stéphane Jourdois ` (2 more replies) 0 siblings, 3 replies; 146+ messages in thread From: Kees Cook @ 2007-03-20 19:20 UTC (permalink / raw) To: Randy Dunlap; +Cc: Andrew Morton, linux-kernel On Tue, Mar 20, 2007 at 10:31:51AM -0700, Randy Dunlap wrote: > LD .tmp_vmlinux1 > kernel/built-in.o:(.data+0xfc0): undefined reference to `maps_protect' > make: *** [.tmp_vmlinux1] Error 1 > > with CONFIG_PROC_FS=n Gah! Apologies. This should fix it, but I can't test it since I can't get 2.6.21-rc4-mm1 to compile (with or without this fix): GEN .version init/.missing_syscalls.h.cmd:2: *** missing separator. Stop. make: *** [.tmp_vmlinux1] Error 2 Signed-off-by: Kees Cook <kees@outflux.net> --- diff -uNrp linux-2.6.21-rc4-mm1/kernel/sysctl.c linux-2.6.21-rc4-mm1-kees/kernel/sysctl.c --- linux-2.6.21-rc4-mm1/kernel/sysctl.c 2007-03-20 10:45:06.000000000 -0700 +++ linux-2.6.21-rc4-mm1-kees/kernel/sysctl.c 2007-03-20 11:36:06.000000000 -0700 @@ -77,9 +77,12 @@ extern int pid_max_min, pid_max_max; extern int sysctl_drop_caches; extern int percpu_pagelist_fraction; extern int compat_log; -extern int maps_protect; extern int print_fatal_signals; +#ifdef CONFIG_PROC_FS +extern int maps_protect; +#endif + #if defined(CONFIG_ADAPTIVE_READAHEAD) extern int readahead_ratio; extern int readahead_hit_rate; @@ -619,6 +622,7 @@ static ctl_table kern_table[] = { .proc_handler = &proc_dointvec, }, #endif +#ifdef CONFIG_PROC_FS { .ctl_name = CTL_UNNUMBERED, .procname = "maps_protect", @@ -627,6 +631,7 @@ static ctl_table kern_table[] = { .mode = 0644, .proc_handler = &proc_dointvec, }, +#endif { .ctl_name = 0 } }; -- Kees Cook @outflux.net ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 19:20 ` 2.6.21-rc4-mm1 Kees Cook @ 2007-03-20 20:42 ` Stéphane Jourdois 2007-03-20 20:50 ` 2.6.21-rc4-mm1 Randy Dunlap 2007-03-21 5:47 ` 2.6.21-rc4-mm1 Andrew Morton 2 siblings, 0 replies; 146+ messages in thread From: Stéphane Jourdois @ 2007-03-20 20:42 UTC (permalink / raw) To: Kees Cook; +Cc: linux-kernel Kees Cook a écrit : > Gah! Apologies. This should fix it, but I can't test it since I can't > get 2.6.21-rc4-mm1 to compile (with or without this fix): > > GEN .version > init/.missing_syscalls.h.cmd:2: *** missing separator. Stop. > make: *** [.tmp_vmlinux1] Error 2 Hi, Would you please try the following patch, after removing init/.missing_syscalls.h.cmd ? http://lkml.org/lkml/2007/3/20/79 thanks. - Stéphane. -- /// Stephane Jourdois /"\ ASCII RIBBON CAMPAIGN \\\ ((( Consultant securite \ / AGAINST HTML MAIL ))) \\\ 24 rue Cauchy X /// \\\ 75015 Paris / \ +33 6 8643 3085 /// ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 19:20 ` 2.6.21-rc4-mm1 Kees Cook 2007-03-20 20:42 ` 2.6.21-rc4-mm1 Stéphane Jourdois @ 2007-03-20 20:50 ` Randy Dunlap 2007-03-21 5:47 ` 2.6.21-rc4-mm1 Andrew Morton 2 siblings, 0 replies; 146+ messages in thread From: Randy Dunlap @ 2007-03-20 20:50 UTC (permalink / raw) To: Kees Cook; +Cc: Andrew Morton, linux-kernel On Tue, 20 Mar 2007 12:20:16 -0700 Kees Cook wrote: > On Tue, Mar 20, 2007 at 10:31:51AM -0700, Randy Dunlap wrote: > > LD .tmp_vmlinux1 > > kernel/built-in.o:(.data+0xfc0): undefined reference to `maps_protect' > > make: *** [.tmp_vmlinux1] Error 1 > > > > with CONFIG_PROC_FS=n > > Gah! Apologies. This should fix it, but I can't test it since I can't > get 2.6.21-rc4-mm1 to compile (with or without this fix): > > GEN .version > init/.missing_syscalls.h.cmd:2: *** missing separator. Stop. > make: *** [.tmp_vmlinux1] Error 2 > > > Signed-off-by: Kees Cook <kees@outflux.net> Yes, that works_for_me. Acked-by: Randy Dunlap <randy.dunlap@oracle.com> > --- > diff -uNrp linux-2.6.21-rc4-mm1/kernel/sysctl.c linux-2.6.21-rc4-mm1-kees/kernel/sysctl.c > --- linux-2.6.21-rc4-mm1/kernel/sysctl.c 2007-03-20 10:45:06.000000000 -0700 > +++ linux-2.6.21-rc4-mm1-kees/kernel/sysctl.c 2007-03-20 11:36:06.000000000 -0700 > @@ -77,9 +77,12 @@ extern int pid_max_min, pid_max_max; > extern int sysctl_drop_caches; > extern int percpu_pagelist_fraction; > extern int compat_log; > -extern int maps_protect; > extern int print_fatal_signals; > > +#ifdef CONFIG_PROC_FS > +extern int maps_protect; > +#endif > + > #if defined(CONFIG_ADAPTIVE_READAHEAD) > extern int readahead_ratio; > extern int readahead_hit_rate; > @@ -619,6 +622,7 @@ static ctl_table kern_table[] = { > .proc_handler = &proc_dointvec, > }, > #endif > +#ifdef CONFIG_PROC_FS > { > .ctl_name = CTL_UNNUMBERED, > .procname = "maps_protect", > @@ -627,6 +631,7 @@ static ctl_table kern_table[] = { > .mode = 0644, > .proc_handler = &proc_dointvec, > }, > +#endif > > { .ctl_name = 0 } > }; --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 19:20 ` 2.6.21-rc4-mm1 Kees Cook 2007-03-20 20:42 ` 2.6.21-rc4-mm1 Stéphane Jourdois 2007-03-20 20:50 ` 2.6.21-rc4-mm1 Randy Dunlap @ 2007-03-21 5:47 ` Andrew Morton 2007-03-21 11:25 ` 2.6.21-rc4-mm1 David Woodhouse ` (2 more replies) 2 siblings, 3 replies; 146+ messages in thread From: Andrew Morton @ 2007-03-21 5:47 UTC (permalink / raw) To: Kees Cook; +Cc: Randy Dunlap, linux-kernel, Sam Ravnborg, David Woodhouse On Tue, 20 Mar 2007 12:20:16 -0700 Kees Cook <kees@outflux.net> wrote: > I can't > get 2.6.21-rc4-mm1 to compile (with or without this fix): > > GEN .version > init/.missing_syscalls.h.cmd:2: *** missing separator. Stop. > make: *** [.tmp_vmlinux1] Error 2 How'd you manage that? Sam, I think this is a you-thing rather than a dwmw2-thing? ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 5:47 ` 2.6.21-rc4-mm1 Andrew Morton @ 2007-03-21 11:25 ` David Woodhouse 2007-03-21 11:59 ` 2.6.21-rc4-mm1 Sam Ravnborg 2007-03-21 22:19 ` 2.6.21-rc4-mm1 Sam Ravnborg 2 siblings, 0 replies; 146+ messages in thread From: David Woodhouse @ 2007-03-21 11:25 UTC (permalink / raw) To: Andrew Morton; +Cc: Kees Cook, Randy Dunlap, linux-kernel, Sam Ravnborg On Tue, 2007-03-20 at 21:47 -0800, Andrew Morton wrote: > On Tue, 20 Mar 2007 12:20:16 -0700 Kees Cook <kees@outflux.net> wrote: > > > I can't > > get 2.6.21-rc4-mm1 to compile (with or without this fix): > > > > GEN .version > > init/.missing_syscalls.h.cmd:2: *** missing separator. Stop. > > make: *** [.tmp_vmlinux1] Error 2 What if you remove init/.missing_syscalls.h.cmd _and_ apply the patch, then try again? -- dwmw2 ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 5:47 ` 2.6.21-rc4-mm1 Andrew Morton 2007-03-21 11:25 ` 2.6.21-rc4-mm1 David Woodhouse @ 2007-03-21 11:59 ` Sam Ravnborg 2007-03-22 9:17 ` 2.6.21-rc4-mm1 David Woodhouse 2007-03-21 22:19 ` 2.6.21-rc4-mm1 Sam Ravnborg 2 siblings, 1 reply; 146+ messages in thread From: Sam Ravnborg @ 2007-03-21 11:59 UTC (permalink / raw) To: Andrew Morton; +Cc: Kees Cook, Randy Dunlap, linux-kernel, David Woodhouse On Tue, Mar 20, 2007 at 09:47:14PM -0800, Andrew Morton wrote: > On Tue, 20 Mar 2007 12:20:16 -0700 Kees Cook <kees@outflux.net> wrote: > > > I can't > > get 2.6.21-rc4-mm1 to compile (with or without this fix): > > > > GEN .version > > init/.missing_syscalls.h.cmd:2: *** missing separator. Stop. > > make: *** [.tmp_vmlinux1] Error 2 > > How'd you manage that? > > Sam, I think this is a you-thing rather than a dwmw2-thing? I will give it a shot tonight. One issue I have with current approach is that the ARCH specific things are in a single .h file. Sam ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 11:59 ` 2.6.21-rc4-mm1 Sam Ravnborg @ 2007-03-22 9:17 ` David Woodhouse 2007-03-22 11:41 ` 2.6.21-rc4-mm1 Sam Ravnborg 0 siblings, 1 reply; 146+ messages in thread From: David Woodhouse @ 2007-03-22 9:17 UTC (permalink / raw) To: Sam Ravnborg; +Cc: Andrew Morton, Kees Cook, Randy Dunlap, linux-kernel On Wed, 2007-03-21 at 12:59 +0100, Sam Ravnborg wrote: > I will give it a shot tonight. Thanks. I'll delete the syscalls-2.6.git tree now that you have it. > One issue I have with current approach is that the ARCH specific > things are in a single .h file. Que? There aren't really any arch-specific things, except for a list of syscalls to be ignored which are i386-specific. That's because we're pulling in the 'master' system call list from asm-i386/unistd.h, and we need to exclude some of those which we don't really need on other architectures. -- dwmw2 ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 9:17 ` 2.6.21-rc4-mm1 David Woodhouse @ 2007-03-22 11:41 ` Sam Ravnborg 2007-03-22 16:25 ` 2.6.21-rc4-mm1 David Woodhouse 0 siblings, 1 reply; 146+ messages in thread From: Sam Ravnborg @ 2007-03-22 11:41 UTC (permalink / raw) To: David Woodhouse; +Cc: Andrew Morton, Kees Cook, Randy Dunlap, linux-kernel On Thu, Mar 22, 2007 at 09:17:00AM +0000, David Woodhouse wrote: > On Wed, 2007-03-21 at 12:59 +0100, Sam Ravnborg wrote: > > I will give it a shot tonight. > > Thanks. I'll delete the syscalls-2.6.git tree now that you have it. > > > One issue I have with current approach is that the ARCH specific > > things are in a single .h file. > > Que? There aren't really any arch-specific things, except for a list of > syscalls to be ignored which are i386-specific. That's because we're > pulling in the 'master' system call list from asm-i386/unistd.h, and we > need to exclude some of those which we don't really need on other > architectures. Yep - realized this when I took a closer look. One thing striked my mind. It is correct that new things gets added to i386 first these days? To me it looks like x86_64 is growing larger than i386 among the developers these days so using asm-x86_64/unistd.h could be a better choice? Sam ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 11:41 ` 2.6.21-rc4-mm1 Sam Ravnborg @ 2007-03-22 16:25 ` David Woodhouse 2007-03-22 16:28 ` 2.6.21-rc4-mm1 Sam Ravnborg 0 siblings, 1 reply; 146+ messages in thread From: David Woodhouse @ 2007-03-22 16:25 UTC (permalink / raw) To: Sam Ravnborg; +Cc: Andrew Morton, Kees Cook, Randy Dunlap, linux-kernel On Thu, 2007-03-22 at 12:41 +0100, Sam Ravnborg wrote: > Yep - realized this when I took a closer look. > One thing striked my mind. It is correct that new things gets added > to i386 first these days? Personally I tend to do PowerPC first, but most others seem to do i386, yes. There are still system calls being added to i386 and not x86_64... init/missing_syscalls.h:947:3: warning: #warning syscall getcpu not implemented init/missing_syscalls.h:950:3: warning: #warning syscall epoll_pwait not implemented init/missing_syscalls.h:953:3: warning: #warning syscall lutimesat not implemented init/missing_syscalls.h:956:3: warning: #warning syscall revokeat not implemented init/missing_syscalls.h:959:3: warning: #warning syscall frevoke not implemented > To me it looks like x86_64 is growing larger than i386 among the > developers these days so using asm-x86_64/unistd.h could be a better > choice? Or perhaps the union of i386, x86_64 and powerpc. But I think i386 is good enough for now. -- dwmw2 ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 16:25 ` 2.6.21-rc4-mm1 David Woodhouse @ 2007-03-22 16:28 ` Sam Ravnborg 0 siblings, 0 replies; 146+ messages in thread From: Sam Ravnborg @ 2007-03-22 16:28 UTC (permalink / raw) To: David Woodhouse; +Cc: Andrew Morton, Kees Cook, Randy Dunlap, linux-kernel On Thu, Mar 22, 2007 at 04:25:53PM +0000, David Woodhouse wrote: > On Thu, 2007-03-22 at 12:41 +0100, Sam Ravnborg wrote: > > Yep - realized this when I took a closer look. > > One thing striked my mind. It is correct that new things gets added > > to i386 first these days? > > Personally I tend to do PowerPC first, but most others seem to do i386, > yes. There are still system calls being added to i386 and not x86_64... > > init/missing_syscalls.h:947:3: warning: #warning syscall getcpu not implemented > init/missing_syscalls.h:950:3: warning: #warning syscall epoll_pwait not implemented > init/missing_syscalls.h:953:3: warning: #warning syscall lutimesat not implemented > init/missing_syscalls.h:956:3: warning: #warning syscall revokeat not implemented > init/missing_syscalls.h:959:3: warning: #warning syscall frevoke not implemented > > > To me it looks like x86_64 is growing larger than i386 among the > > developers these days so using asm-x86_64/unistd.h could be a better > > choice? > > Or perhaps the union of i386, x86_64 and powerpc. But I think i386 is > good enough for now. I kept i386 as default so all is good. Sam ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 5:47 ` 2.6.21-rc4-mm1 Andrew Morton 2007-03-21 11:25 ` 2.6.21-rc4-mm1 David Woodhouse 2007-03-21 11:59 ` 2.6.21-rc4-mm1 Sam Ravnborg @ 2007-03-21 22:19 ` Sam Ravnborg 2007-03-21 22:22 ` [PATCH 1/3] kbuild: complain about missing system calls Sam Ravnborg ` (3 more replies) 2 siblings, 4 replies; 146+ messages in thread From: Sam Ravnborg @ 2007-03-21 22:19 UTC (permalink / raw) To: Andrew Morton; +Cc: Kees Cook, Randy Dunlap, linux-kernel, David Woodhouse, sam On Tue, Mar 20, 2007 at 09:47:14PM -0800, Andrew Morton wrote: > On Tue, 20 Mar 2007 12:20:16 -0700 Kees Cook <kees@outflux.net> wrote: > > > I can't > > get 2.6.21-rc4-mm1 to compile (with or without this fix): > > > > GEN .version > > init/.missing_syscalls.h.cmd:2: *** missing separator. Stop. > > make: *** [.tmp_vmlinux1] Error 2 > > How'd you manage that? > > Sam, I think this is a you-thing rather than a dwmw2-thing? Took a look. Things looked pretty OK but an updated patch applied to kbuild.git. Corrected a few things in the Makefile and combined the patch from dwmw2 and Stephane. kbuild.git pused out and patches follows. Sam ^ permalink raw reply [flat|nested] 146+ messages in thread
* [PATCH 1/3] kbuild: complain about missing system calls. 2007-03-21 22:19 ` 2.6.21-rc4-mm1 Sam Ravnborg @ 2007-03-21 22:22 ` Sam Ravnborg 2007-05-07 22:29 ` Tony Luck 2007-03-21 22:23 ` [PATCH 2/3] kbuild: ignore more i386 legacy syscalls Sam Ravnborg ` (2 subsequent siblings) 3 siblings, 1 reply; 146+ messages in thread From: Sam Ravnborg @ 2007-03-21 22:22 UTC (permalink / raw) To: Andrew Morton; +Cc: Kees Cook, Randy Dunlap, linux-kernel, David Woodhouse >From 5fbf06eb42fdaf81529d2433fe0953297cbc7cc6 Mon Sep 17 00:00:00 2001 From: David Woodhouse <dwmw2@infradead.org> Date: Thu, 8 Mar 2007 23:01:13 +0000 Subject: [PATCH] kbuild: complain about missing system calls. Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Most system calls seem to get added to i386 first. This patch automatically generates a warning for any new system call which is implemented on i386 but not the architecture currently being compiled. On PowerPC at the moment, for example, it results in these warnings: init/missing_syscalls.h:935:3: warning: #warning syscall sync_file_range not implemented init/missing_syscalls.h:947:3: warning: #warning syscall getcpu not implemented init/missing_syscalls.h:950:3: warning: #warning syscall epoll_pwait not implemented Other contributors to this patch are Russell King <rmk+lkml@arm.linux.org.uk> and Stéphane Jourdois <kwisatz@rubis.org> Signed-off-by: David Woodhouse <dwmw2@infradead.org> Signed-off-by: Sam Ravnborg <sam@ravnborg.org> --- init/Makefile | 12 +++++++++- init/missing_syscalls.c | 57 +++++++++++++++++++++++++++++++++++++++++++++++ scripts/syscallchk | 6 +++++ 3 files changed, 74 insertions(+), 1 deletions(-) diff --git a/init/Makefile b/init/Makefile index 0154aea..af9f529 100644 --- a/init/Makefile +++ b/init/Makefile @@ -2,7 +2,7 @@ # Makefile for the linux kernel. # -obj-y := main.o version.o mounts.o +obj-y := main.o version.o mounts.o missing_syscalls.o ifneq ($(CONFIG_BLK_DEV_INITRD),y) obj-y += noinitramfs.o else @@ -21,6 +21,7 @@ clean-files := ../include/linux/compile.h # dependencies on generated files need to be listed explicitly $(obj)/version.o: include/linux/compile.h +$(obj)/missing_syscalls.o: $(obj)/missing_syscalls.h # compile.h changes depending on hostname, generation number, etc, # so we regenerate it always. @@ -31,3 +32,12 @@ include/linux/compile.h: FORCE @echo ' CHK $@' $(Q)$(CONFIG_SHELL) $(srctree)/scripts/mkcompile_h $@ \ "$(UTS_MACHINE)" "$(CONFIG_SMP)" "$(CONFIG_PREEMPT)" "$(CC) $(CFLAGS)" + + +quiet_cmd_missing_syscalls = GEN $@ + cmd_missing_syscalls = sed -n -f $(srctree)/scripts/syscallchk $< > $@ + +targets += missing_syscalls.h +$(obj)/missing_syscalls.h: include/asm-i386/unistd.h \ + $(srctree)/scripts/syscallchk $(src)/Makefile + $(call if_changed,missing_syscalls) diff --git a/init/missing_syscalls.c b/init/missing_syscalls.c new file mode 100644 index 0000000..e802b06 --- /dev/null +++ b/init/missing_syscalls.c @@ -0,0 +1,57 @@ +#include <asm/types.h> +#include <asm/unistd.h> + +/* Force recompilation (and thus warnings) every time we rebuild the kernel */ +#include <linux/compile.h> + +/* System calls for 32-bit kernels only */ +#if BITS_PER_LONG == 64 +#define __IGNORE_sendfile64 +#define __IGNORE_ftruncate64 +#define __IGNORE_truncate64 +#define __IGNORE_stat64 +#define __IGNORE_lstat64 +#define __IGNORE_fstat64 +#define __IGNORE_fcntl64 +#define __IGNORE_fadvise64_64 +#define __IGNORE_fstatat64 +#endif + +/* i386-specific or historical system calls */ +#define __IGNORE_mmap2 +#define __IGNORE_vm86 +#define __IGNORE_vm86old +#define __IGNORE_set_thread_area +#define __IGNORE_get_thread_area +#define __IGNORE_madvise1 +#define __IGNORE_oldstat +#define __IGNORE_oldfstat +#define __IGNORE_oldlstat +#define __IGNORE_oldolduname +#define __IGNORE_olduname +#define __IGNORE_umount2 +/* ... including the "new" 32-bit uid syscalls */ +#define __IGNORE_lchown32 +#define __IGNORE_getuid32 +#define __IGNORE_getgid32 +#define __IGNORE_geteuid32 +#define __IGNORE_getegid32 +#define __IGNORE_setreuid32 +#define __IGNORE_setregid32 +#define __IGNORE_getgroups32 +#define __IGNORE_setgroups32 +#define __IGNORE_fchown32 +#define __IGNORE_setresuid32 +#define __IGNORE_getresuid32 +#define __IGNORE_setresgid32 +#define __IGNORE_getresgid32 +#define __IGNORE_chown32 +#define __IGNORE_setuid32 +#define __IGNORE_setgid32 +#define __IGNORE_setfsuid32 +#define __IGNORE_setfsgid32 + +/* Not yet upstream */ +#define __IGNORE_vserver + +#include "missing_syscalls.h" diff --git a/scripts/syscallchk b/scripts/syscallchk new file mode 100644 index 0000000..d545717 --- /dev/null +++ b/scripts/syscallchk @@ -0,0 +1,6 @@ +/^\#define/ { + s/[^_]*__NR_\([^[:space:]]*\).*/\ +\#if !defined (__NR_\1) \&\& !defined (__IGNORE_\1)\ +\#warning syscall \1 not implemented\ +\#endif/p +} -- 1.4.4.2 ^ permalink raw reply related [flat|nested] 146+ messages in thread
* Re: [PATCH 1/3] kbuild: complain about missing system calls. 2007-03-21 22:22 ` [PATCH 1/3] kbuild: complain about missing system calls Sam Ravnborg @ 2007-05-07 22:29 ` Tony Luck 2007-05-07 22:39 ` David Woodhouse 0 siblings, 1 reply; 146+ messages in thread From: Tony Luck @ 2007-05-07 22:29 UTC (permalink / raw) To: Sam Ravnborg Cc: Andrew Morton, Kees Cook, Randy Dunlap, linux-kernel, David Woodhouse On 3/21/07, Sam Ravnborg <sam@ravnborg.org> wrote: > Most system calls seem to get added to i386 first. This patch > automatically generates a warning for any new system call which is > implemented on i386 but not the architecture currently being compiled. This is now upstream, and so I see a bunch of warnings for every ia64 build. Some of them are real, I need to add some syscalls, but there are a few bogus ones because ia64 chose different names (e.g. we have a sys_clone() that glibc uses to implement fork() and vfork()). Just checking that the right way for me to shut checksyscalls.sh up is to add: #define __IGNORE_fork #define __IGNORE_vfork etc. to include/asm-ia64/unistd.h for each of the bogus ones. Or is there some other preferred mechanism? -Tony ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [PATCH 1/3] kbuild: complain about missing system calls. 2007-05-07 22:29 ` Tony Luck @ 2007-05-07 22:39 ` David Woodhouse 2007-05-07 22:51 ` Luck, Tony 0 siblings, 1 reply; 146+ messages in thread From: David Woodhouse @ 2007-05-07 22:39 UTC (permalink / raw) To: Tony Luck Cc: Sam Ravnborg, Andrew Morton, Kees Cook, Randy Dunlap, linux-kernel On Mon, 2007-05-07 at 15:29 -0700, Tony Luck wrote: > On 3/21/07, Sam Ravnborg <sam@ravnborg.org> wrote: > > Most system calls seem to get added to i386 first. This patch > > automatically generates a warning for any new system call which is > > implemented on i386 but not the architecture currently being compiled. > > This is now upstream, and so I see a bunch of warnings for every ia64 > build. Some of them are real, I need to add some syscalls, but there > are a few bogus ones because ia64 chose different names (e.g. we have > a sys_clone() that glibc uses to implement fork() and vfork()). > > Just checking that the right way for me to shut checksyscalls.sh up is > to add: > > #define __IGNORE_fork > #define __IGNORE_vfork > > etc. to include/asm-ia64/unistd.h for each of the bogus ones. Or is there > some other preferred mechanism? You could add them to scripts/checksyscalls.sh itself -- I think it's fairly unlikely that those are syscalls which a new arch port is going to 'forget' :) -- dwmw2 ^ permalink raw reply [flat|nested] 146+ messages in thread
* RE: [PATCH 1/3] kbuild: complain about missing system calls. 2007-05-07 22:39 ` David Woodhouse @ 2007-05-07 22:51 ` Luck, Tony 2007-05-08 18:24 ` Sam Ravnborg 0 siblings, 1 reply; 146+ messages in thread From: Luck, Tony @ 2007-05-07 22:51 UTC (permalink / raw) To: David Woodhouse Cc: Sam Ravnborg, Andrew Morton, Kees Cook, Randy Dunlap, linux-kernel > You could add them to scripts/checksyscalls.sh itself -- I think it's > fairly unlikely that those are syscalls which a new arch port is going > to 'forget' :) Like this? diff --git a/scripts/checksyscalls.sh b/scripts/checksyscalls.sh index f98171f..4d49056 100755 --- a/scripts/checksyscalls.sh +++ b/scripts/checksyscalls.sh @@ -98,6 +98,14 @@ cat << EOF #define __IGNORE_setgid32 #define __IGNORE_setfsuid32 #define __IGNORE_setfsgid32 +/* ... some legacy names not used by ia64 */ +#define __IGNORE_fork +#define __IGNORE_time +#define __IGNORE_alarm +#define __IGNORE_pause +#define __IGNORE_utime +#define __IGNORE_getpgrp +#define __IGNORE_vfork /* Unmerged syscalls for AFS, STREAMS, etc. */ #define __IGNORE_afs_syscall ^ permalink raw reply related [flat|nested] 146+ messages in thread
* Re: [PATCH 1/3] kbuild: complain about missing system calls. 2007-05-07 22:51 ` Luck, Tony @ 2007-05-08 18:24 ` Sam Ravnborg 2007-05-08 18:35 ` Luck, Tony 0 siblings, 1 reply; 146+ messages in thread From: Sam Ravnborg @ 2007-05-08 18:24 UTC (permalink / raw) To: Luck, Tony Cc: David Woodhouse, Andrew Morton, Kees Cook, Randy Dunlap, linux-kernel On Mon, May 07, 2007 at 03:51:49PM -0700, Luck, Tony wrote: > > You could add them to scripts/checksyscalls.sh itself -- I think it's > > fairly unlikely that those are syscalls which a new arch port is going > > to 'forget' :) > > Like this? > > diff --git a/scripts/checksyscalls.sh b/scripts/checksyscalls.sh > index f98171f..4d49056 100755 > --- a/scripts/checksyscalls.sh > +++ b/scripts/checksyscalls.sh > @@ -98,6 +98,14 @@ cat << EOF > #define __IGNORE_setgid32 > #define __IGNORE_setfsuid32 > #define __IGNORE_setfsgid32 > +/* ... some legacy names not used by ia64 */ > +#define __IGNORE_fork > +#define __IGNORE_time > +#define __IGNORE_alarm > +#define __IGNORE_pause > +#define __IGNORE_utime > +#define __IGNORE_getpgrp > +#define __IGNORE_vfork > > /* Unmerged syscalls for AFS, STREAMS, etc. */ > #define __IGNORE_afs_syscall I would prefer to introduce something in checksyscalls.sh that allows us to do something arch specific. I recall that x86_64 had one syscall implemented using VDSO or similar and therefore got listed. This is just a quick hack - can be done better by someone that is more fluent in shell scripting... diff --git a/scripts/checksyscalls.sh b/scripts/checksyscalls.sh index f98171f..715ed62 100755 --- a/scripts/checksyscalls.sh +++ b/scripts/checksyscalls.sh @@ -107,6 +107,13 @@ cat << EOF EOF } +ignore_arch_list() { + f=include/asm/ignore_syscalls + if [ -f $f ]; then + source $f + fi +} + syscall_list() { sed -n -e '/^\#define/ { s/[^_]*__NR_\([^[:space:]]*\).*/\ \#if !defined \(__NR_\1\) \&\& !defined \(__IGNORE_\1\)\ @@ -114,5 +121,5 @@ sed -n -e '/^\#define/ { s/[^_]*__NR_\([^[:space:]]*\).*/\ \#endif/p }' $1 } -(ignore_list && syscall_list ${srctree}/include/asm-i386/unistd.h) | \ +(ignore_list && ignore_arch_list && syscall_list ${srctree}/include/asm-i386/unistd.h) | \ $* -E -x c - > /dev/null Then adding a fie like this to include/asm-x86_64 will allow us to ignore getcpu for x86_64 only. # syscalls that are ignored for x86_64 # on top of generic ones specified in scripts/checksyscalls.sh cat << EOF #define __IGNORE_getcpu EOF Comments? Sam ^ permalink raw reply related [flat|nested] 146+ messages in thread
* RE: [PATCH 1/3] kbuild: complain about missing system calls. 2007-05-08 18:24 ` Sam Ravnborg @ 2007-05-08 18:35 ` Luck, Tony 2007-05-08 18:49 ` Sam Ravnborg 0 siblings, 1 reply; 146+ messages in thread From: Luck, Tony @ 2007-05-08 18:35 UTC (permalink / raw) To: Sam Ravnborg Cc: David Woodhouse, Andrew Morton, Kees Cook, Randy Dunlap, linux-kernel Looks more complex than necessary. Why do you want to execute an arch specific script to list the __IGNORE symbols? That would allow an arch to generate a list with sed/perl/etc. but that looks like overkill. If you just have an arch specific file with the right defines. E.g. for x86_64 in include/asm-x86_64/ignore_syscalls: #include __IGNORE_getcpu Then the checksyscalls.sh changes would just be something like (do I need a ${srctree} before the include??): diff --git a/scripts/checksyscalls.sh b/scripts/checksyscalls.sh index f98171f..616f7c5 100755 --- a/scripts/checksyscalls.sh +++ b/scripts/checksyscalls.sh @@ -105,6 +105,10 @@ cat << EOF #define __IGNORE_putpmsg #define __IGNORE_vserver EOF +if [ -f include/asm/ignore_syscalls ] +then + cat include/asm/ignore_syscalls +fi } syscall_list() { -Tony ^ permalink raw reply related [flat|nested] 146+ messages in thread
* Re: [PATCH 1/3] kbuild: complain about missing system calls. 2007-05-08 18:35 ` Luck, Tony @ 2007-05-08 18:49 ` Sam Ravnborg 0 siblings, 0 replies; 146+ messages in thread From: Sam Ravnborg @ 2007-05-08 18:49 UTC (permalink / raw) To: Luck, Tony Cc: David Woodhouse, Andrew Morton, Kees Cook, Randy Dunlap, linux-kernel On Tue, May 08, 2007 at 11:35:27AM -0700, Luck, Tony wrote: > Looks more complex than necessary. Why do you want to execute > an arch specific script to list the __IGNORE symbols? That would > allow an arch to generate a list with sed/perl/etc. but that > looks like overkill. > > If you just have an arch specific file with the right defines. > E.g. for x86_64 in include/asm-x86_64/ignore_syscalls: > > #include __IGNORE_getcpu > > Then the checksyscalls.sh changes would just be something like > (do I need a ${srctree} before the include??): Much better - thanks. Yes. For "make O=..." builds we need to refer to the file in the srctree. include/asm/... is not pointing back to the original tree. So I had to use: if [ -f ${srctree}/include/asm-${ARCH}/ignore_syscalls ]; then cat ${srctree}/include/asm-${ARCH}/ignore_syscalls fi To make it work. I will push this change out during the weekend I hope. Sam ^ permalink raw reply [flat|nested] 146+ messages in thread
* [PATCH 2/3] kbuild: ignore more i386 legacy syscalls 2007-03-21 22:19 ` 2.6.21-rc4-mm1 Sam Ravnborg 2007-03-21 22:22 ` [PATCH 1/3] kbuild: complain about missing system calls Sam Ravnborg @ 2007-03-21 22:23 ` Sam Ravnborg 2007-03-21 22:24 ` [PATCH 3/3] kbuild: exempt more syscalls from warnings, for x86_64 and ARM Sam Ravnborg 2007-03-21 23:01 ` 2.6.21-rc4-mm1 Andrew Morton 3 siblings, 0 replies; 146+ messages in thread From: Sam Ravnborg @ 2007-03-21 22:23 UTC (permalink / raw) To: Andrew Morton; +Cc: Kees Cook, Randy Dunlap, linux-kernel, David Woodhouse >From 9ca09c1ca8e5f65ea9f7f0bb3de71cc70a0f6511 Mon Sep 17 00:00:00 2001 From: David Miller <davem@davemloft.net> Date: Thu, 8 Mar 2007 16:14:07 -0800 Subject: [PATCH] kbuild: ignore more i386 legacy syscalls The vast majority of them vector to sys_ni_syscall in the i386 syscall table. sys_ugetrlimit is only necessary if the platform started out using the non-SuS compliant sys_old_getrlimit() The rest, like ioperm, iopl, modify_ldt, et al. are i386 specific. Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Sam Ravnborg <sam@ravnborg.org> --- init/missing_syscalls.c | 16 ++++++++++++++++ 1 files changed, 16 insertions(+), 0 deletions(-) diff --git a/init/missing_syscalls.c b/init/missing_syscalls.c index e802b06..dc6b97d 100644 --- a/init/missing_syscalls.c +++ b/init/missing_syscalls.c @@ -18,6 +18,22 @@ #endif /* i386-specific or historical system calls */ +#define __IGNORE_break +#define __IGNORE_stty +#define __IGNORE_gtty +#define __IGNORE_ftime +#define __IGNORE_prof +#define __IGNORE_lock +#define __IGNORE_mpx +#define __IGNORE_ulimit +#define __IGNORE_profil +#define __IGNORE_ioperm +#define __IGNORE_iopl +#define __IGNORE_idle +#define __IGNORE_modify_ldt +#define __IGNORE_getpmsg +#define __IGNORE_putpmsg +#define __IGNORE_ugetrlimit #define __IGNORE_mmap2 #define __IGNORE_vm86 #define __IGNORE_vm86old -- 1.4.4.2 ^ permalink raw reply related [flat|nested] 146+ messages in thread
* [PATCH 3/3] kbuild: exempt more syscalls from warnings, for x86_64 and ARM. 2007-03-21 22:19 ` 2.6.21-rc4-mm1 Sam Ravnborg 2007-03-21 22:22 ` [PATCH 1/3] kbuild: complain about missing system calls Sam Ravnborg 2007-03-21 22:23 ` [PATCH 2/3] kbuild: ignore more i386 legacy syscalls Sam Ravnborg @ 2007-03-21 22:24 ` Sam Ravnborg 2007-03-21 23:01 ` 2.6.21-rc4-mm1 Andrew Morton 3 siblings, 0 replies; 146+ messages in thread From: Sam Ravnborg @ 2007-03-21 22:24 UTC (permalink / raw) To: Andrew Morton; +Cc: Kees Cook, Randy Dunlap, linux-kernel, David Woodhouse >From 984d35ec37866c9b10c2193fcd1b1b5c6ee4c6cb Mon Sep 17 00:00:00 2001 From: David Woodhouse <dwmw2@infradead.org> Date: Wed, 21 Mar 2007 11:20:51 +0000 Subject: [PATCH] kbuild: exempt more syscalls from warnings, for x86_64 and ARM. Signed-off-by: David Woodhouse <dwmw2@infradead.org> Signed-off-by: Sam Ravnborg <sam@ravnborg.org> --- init/missing_syscalls.c | 30 +++++++++++++++++++++++++++--- 1 files changed, 27 insertions(+), 3 deletions(-) diff --git a/init/missing_syscalls.c b/init/missing_syscalls.c index dc6b97d..0b7e7d2 100644 --- a/init/missing_syscalls.c +++ b/init/missing_syscalls.c @@ -15,6 +15,8 @@ #define __IGNORE_fcntl64 #define __IGNORE_fadvise64_64 #define __IGNORE_fstatat64 +#define __IGNORE_fstatfs64 +#define __IGNORE_statfs64 #endif /* i386-specific or historical system calls */ @@ -31,8 +33,6 @@ #define __IGNORE_iopl #define __IGNORE_idle #define __IGNORE_modify_ldt -#define __IGNORE_getpmsg -#define __IGNORE_putpmsg #define __IGNORE_ugetrlimit #define __IGNORE_mmap2 #define __IGNORE_vm86 @@ -46,6 +46,27 @@ #define __IGNORE_oldolduname #define __IGNORE_olduname #define __IGNORE_umount2 +#define __IGNORE_umount +#define __IGNORE_waitpid +#define __IGNORE_stime +#define __IGNORE_nice +#define __IGNORE_signal +#define __IGNORE_sigaction +#define __IGNORE_sgetmask +#define __IGNORE_sigsuspend +#define __IGNORE_sigpending +#define __IGNORE_readdir +#define __IGNORE_socketcall +#define __IGNORE_ipc +#define __IGNORE_sigreturn +#define __IGNORE_sigprocmask +#define __IGNORE_bdflush +#define __IGNORE__llseek +#define __IGNORE__newselect +#define __IGNORE_create_module +#define __IGNORE_delete_module +#define __IGNORE_query_module +#define __IGNORE_get_kernel_syms /* ... including the "new" 32-bit uid syscalls */ #define __IGNORE_lchown32 #define __IGNORE_getuid32 @@ -67,7 +88,10 @@ #define __IGNORE_setfsuid32 #define __IGNORE_setfsgid32 -/* Not yet upstream */ +/* Unmerged syscalls for AFS, STREAMS, etc. */ +#define __IGNORE_afs_syscall +#define __IGNORE_getpmsg +#define __IGNORE_putpmsg #define __IGNORE_vserver #include "missing_syscalls.h" -- 1.4.4.2 ^ permalink raw reply related [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 22:19 ` 2.6.21-rc4-mm1 Sam Ravnborg ` (2 preceding siblings ...) 2007-03-21 22:24 ` [PATCH 3/3] kbuild: exempt more syscalls from warnings, for x86_64 and ARM Sam Ravnborg @ 2007-03-21 23:01 ` Andrew Morton 2007-03-22 8:54 ` 2.6.21-rc4-mm1 Sam Ravnborg 3 siblings, 1 reply; 146+ messages in thread From: Andrew Morton @ 2007-03-21 23:01 UTC (permalink / raw) To: Sam Ravnborg; +Cc: Kees Cook, Randy Dunlap, linux-kernel, David Woodhouse On Wed, 21 Mar 2007 23:19:05 +0100 Sam Ravnborg <sam@ravnborg.org> wrote: > On Tue, Mar 20, 2007 at 09:47:14PM -0800, Andrew Morton wrote: > > On Tue, 20 Mar 2007 12:20:16 -0700 Kees Cook <kees@outflux.net> wrote: > > > > > I can't > > > get 2.6.21-rc4-mm1 to compile (with or without this fix): > > > > > > GEN .version > > > init/.missing_syscalls.h.cmd:2: *** missing separator. Stop. > > > make: *** [.tmp_vmlinux1] Error 2 > > > > How'd you manage that? > > > > Sam, I think this is a you-thing rather than a dwmw2-thing? > Took a look. Things looked pretty OK but an updated patch > applied to kbuild.git. > Corrected a few things in the Makefile and combined the > patch from dwmw2 and Stephane. > > kbuild.git pused out and patches follows. > David has set up a git tree with this stuff, so you presumably have an out-of-date copy. git://git.infradead.org/~dwmw2/syscalls-2.6.git I don't know what's changed in there. One never does, with git trees :( ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 23:01 ` 2.6.21-rc4-mm1 Andrew Morton @ 2007-03-22 8:54 ` Sam Ravnborg 0 siblings, 0 replies; 146+ messages in thread From: Sam Ravnborg @ 2007-03-22 8:54 UTC (permalink / raw) To: Andrew Morton; +Cc: Kees Cook, Randy Dunlap, linux-kernel, David Woodhouse On Wed, Mar 21, 2007 at 04:01:11PM -0700, Andrew Morton wrote: > On Wed, 21 Mar 2007 23:19:05 +0100 > Sam Ravnborg <sam@ravnborg.org> wrote: > > > On Tue, Mar 20, 2007 at 09:47:14PM -0800, Andrew Morton wrote: > > > On Tue, 20 Mar 2007 12:20:16 -0700 Kees Cook <kees@outflux.net> wrote: > > > > > > > I can't > > > > get 2.6.21-rc4-mm1 to compile (with or without this fix): > > > > > > > > GEN .version > > > > init/.missing_syscalls.h.cmd:2: *** missing separator. Stop. > > > > make: *** [.tmp_vmlinux1] Error 2 > > > > > > How'd you manage that? > > > > > > Sam, I think this is a you-thing rather than a dwmw2-thing? > > Took a look. Things looked pretty OK but an updated patch > > applied to kbuild.git. > > Corrected a few things in the Makefile and combined the > > patch from dwmw2 and Stephane. > > > > kbuild.git pused out and patches follows. > > > > David has set up a git tree with this stuff, so you presumably > have an out-of-date copy. > > git://git.infradead.org/~dwmw2/syscalls-2.6.git > > I don't know what's changed in there. One never does, with git > trees :( I pulled that one and last patch in my serie was from that tree. Sam ^ permalink raw reply [flat|nested] 146+ messages in thread
* [PATCH] utrace: make an inline void 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (5 preceding siblings ...) 2007-03-20 17:31 ` 2.6.21-rc4-mm1 Randy Dunlap @ 2007-03-20 18:09 ` Randy Dunlap 2007-03-21 1:48 ` Roland McGrath 2007-03-20 20:49 ` 2.6.21-rc4-mm1: multiple definition of `queue_pushbutton_work' Adrian Bunk ` (16 subsequent siblings) 23 siblings, 1 reply; 146+ messages in thread From: Randy Dunlap @ 2007-03-20 18:09 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel, roland On Mon, 19 Mar 2007 20:56:23 -0800 Andrew Morton wrote: > > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > Will appear later at > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ From: Randy Dunlap <randy.dunlap@oracle.com> Avoid multiple/repeated warnings: include/linux/utrace.h:594: warning: return type defaults to 'int' Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com> --- include/linux/utrace.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- linux-2.6.21-rc4-mm1.orig/include/linux/utrace.h +++ linux-2.6.21-rc4-mm1/include/linux/utrace.h @@ -590,7 +590,7 @@ static inline void utrace_report_death(s { BUG(); } -static inline utrace_report_delayed_group_leader(struct task_struct *tsk) +static inline void utrace_report_delayed_group_leader(struct task_struct *tsk) { BUG(); } ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [PATCH] utrace: make an inline void 2007-03-20 18:09 ` [PATCH] utrace: make an inline void Randy Dunlap @ 2007-03-21 1:48 ` Roland McGrath 0 siblings, 0 replies; 146+ messages in thread From: Roland McGrath @ 2007-03-21 1:48 UTC (permalink / raw) To: Randy Dunlap; +Cc: Andrew Morton, linux-kernel > Avoid multiple/repeated warnings: > include/linux/utrace.h:594: warning: return type defaults to 'int' Oops! Thanks for catching this. Thanks, Roland ^ permalink raw reply [flat|nested] 146+ messages in thread
* 2.6.21-rc4-mm1: multiple definition of `queue_pushbutton_work' 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (6 preceding siblings ...) 2007-03-20 18:09 ` [PATCH] utrace: make an inline void Randy Dunlap @ 2007-03-20 20:49 ` Adrian Bunk 2007-03-21 18:45 ` Kristen Carlson Accardi 2007-03-20 21:04 ` 2.6.21-rc4-mm1 J.A. Magallón ` (15 subsequent siblings) 23 siblings, 1 reply; 146+ messages in thread From: Adrian Bunk @ 2007-03-20 20:49 UTC (permalink / raw) To: Andrew Morton, Kenji Kaneshige Cc: linux-kernel, Kristen Carlson Accardi, Greg Kroah-Hartman, linux-pci On Mon, Mar 19, 2007 at 08:56:23PM -0800, Andrew Morton wrote: >... > Changes since 2.6.21-rc3-mm1: >... > +gregkh-pci-pciehp-event-handling-rework.patch >... > PCI tree updates >... <-- snip --> ... LD drivers/pci/hotplug/built-in.o drivers/pci/hotplug/shpchp.o: In function `queue_pushbutton_work':(.text+0x112f): multiple definition of `queue_pushbutton_work' drivers/pci/hotplug/pciehp.o:(.text+0x1004): first defined here make[4]: *** [drivers/pci/hotplug/built-in.o] Error 1 <-- snip --> cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1: multiple definition of `queue_pushbutton_work' 2007-03-20 20:49 ` 2.6.21-rc4-mm1: multiple definition of `queue_pushbutton_work' Adrian Bunk @ 2007-03-21 18:45 ` Kristen Carlson Accardi 0 siblings, 0 replies; 146+ messages in thread From: Kristen Carlson Accardi @ 2007-03-21 18:45 UTC (permalink / raw) To: Adrian Bunk Cc: Andrew Morton, Kenji Kaneshige, linux-kernel, Greg Kroah-Hartman, linux-pci Fix duplicate names in shpchp and pciehp. Signed-off-by: Kristen Carlson Accardi <kristen.c.accardi@intel.com> Index: 2.6-mm/drivers/pci/hotplug/pciehp.h =================================================================== --- 2.6-mm.orig/drivers/pci/hotplug/pciehp.h +++ 2.6-mm/drivers/pci/hotplug/pciehp.h @@ -158,7 +158,7 @@ extern u8 pciehp_handle_presence_change( extern u8 pciehp_handle_power_fault(u8 hp_slot, struct controller *ctrl); extern int pciehp_configure_device(struct slot *p_slot); extern int pciehp_unconfigure_device(struct slot *p_slot); -extern void queue_pushbutton_work(struct work_struct *work); +extern void pciehp_queue_pushbutton_work(struct work_struct *work); int pcie_init(struct controller *ctrl, struct pcie_device *dev); static inline struct slot *pciehp_find_slot(struct controller *ctrl, u8 device) Index: 2.6-mm/drivers/pci/hotplug/pciehp_core.c =================================================================== --- 2.6-mm.orig/drivers/pci/hotplug/pciehp_core.c +++ 2.6-mm/drivers/pci/hotplug/pciehp_core.c @@ -229,7 +229,7 @@ static int init_slots(struct controller slot->hpc_ops = ctrl->hpc_ops; slot->number = ctrl->first_slot; mutex_init(&slot->lock); - INIT_DELAYED_WORK(&slot->work, queue_pushbutton_work); + INIT_DELAYED_WORK(&slot->work, pciehp_queue_pushbutton_work); /* register this slot with the hotplug pci core */ hotplug_slot->private = slot; Index: 2.6-mm/drivers/pci/hotplug/pciehp_ctrl.c =================================================================== --- 2.6-mm.orig/drivers/pci/hotplug/pciehp_ctrl.c +++ 2.6-mm/drivers/pci/hotplug/pciehp_ctrl.c @@ -351,7 +351,7 @@ static void pciehp_power_thread(struct w kfree(info); } -void queue_pushbutton_work(struct work_struct *work) +void pciehp_queue_pushbutton_work(struct work_struct *work) { struct slot *p_slot = container_of(work, struct slot, work.work); struct power_work_info *info; Index: 2.6-mm/drivers/pci/hotplug/shpchp.h =================================================================== --- 2.6-mm.orig/drivers/pci/hotplug/shpchp.h +++ 2.6-mm/drivers/pci/hotplug/shpchp.h @@ -166,7 +166,7 @@ extern u8 shpchp_handle_power_fault(u8 h extern int shpchp_configure_device(struct slot *p_slot); extern int shpchp_unconfigure_device(struct slot *p_slot); extern void cleanup_slots(struct controller *ctrl); -extern void queue_pushbutton_work(struct work_struct *work); +extern void shpchp_queue_pushbutton_work(struct work_struct *work); extern int shpc_init( struct controller *ctrl, struct pci_dev *pdev); #ifdef CONFIG_ACPI Index: 2.6-mm/drivers/pci/hotplug/shpchp_core.c =================================================================== --- 2.6-mm.orig/drivers/pci/hotplug/shpchp_core.c +++ 2.6-mm/drivers/pci/hotplug/shpchp_core.c @@ -136,7 +136,7 @@ static int init_slots(struct controller slot->hpc_ops = ctrl->hpc_ops; slot->number = ctrl->first_slot + (ctrl->slot_num_inc * i); mutex_init(&slot->lock); - INIT_DELAYED_WORK(&slot->work, queue_pushbutton_work); + INIT_DELAYED_WORK(&slot->work, shpchp_queue_pushbutton_work); /* register this slot with the hotplug pci core */ hotplug_slot->private = slot; Index: 2.6-mm/drivers/pci/hotplug/shpchp_ctrl.c =================================================================== --- 2.6-mm.orig/drivers/pci/hotplug/shpchp_ctrl.c +++ 2.6-mm/drivers/pci/hotplug/shpchp_ctrl.c @@ -433,7 +433,7 @@ static void shpchp_pushbutton_thread(str kfree(info); } -void queue_pushbutton_work(struct work_struct *work) +void shpchp_queue_pushbutton_work(struct work_struct *work) { struct slot *p_slot = container_of(work, struct slot, work.work); struct pushbutton_work_info *info; ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (7 preceding siblings ...) 2007-03-20 20:49 ` 2.6.21-rc4-mm1: multiple definition of `queue_pushbutton_work' Adrian Bunk @ 2007-03-20 21:04 ` J.A. Magallón 2007-03-20 23:10 ` FireWire update in -mm (was 2.6.21-rc4-mm1) Stefan Richter ` (14 subsequent siblings) 23 siblings, 0 replies; 146+ messages in thread From: J.A. Magallón @ 2007-03-20 21:04 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel On Mon, 19 Mar 2007 20:56:23 -0800, Andrew Morton <akpm@linux-foundation.org> wrote: > > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > After applying hot-fixes, I get this: MODPOST vmlinux WARNING: init/built-in.o - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xfa) and 'try_name' WARNING: arch/i386/kernel/built-in.o - Section mismatch: reference to .init.text:cpu_set_gdt from .text between 'initialize_secondary' (at offset 0xbce3) and 'mp_find_ioapic' WARNING: mm/built-in.o - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'set_up_list3s' (at offset 0x1b384) and 's_start' If you need anything, just ask (.config or the like) -- J.A. Magallon <jamagallon()ono!com> \ Software is like sex: \ It's better when it's free Mandriva Linux release 2007.1 (Cooker) for i586 Linux 2.6.20-jam05 (gcc 4.1.2 20070302 (prerelease) (4.1.2-1mdv2007.1)) #2 SMP PREEMPT ^ permalink raw reply [flat|nested] 146+ messages in thread
* FireWire update in -mm (was 2.6.21-rc4-mm1) 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (8 preceding siblings ...) 2007-03-20 21:04 ` 2.6.21-rc4-mm1 J.A. Magallón @ 2007-03-20 23:10 ` Stefan Richter 2007-03-20 23:49 ` 2.6.21-rc4-mm1 Randy Dunlap ` (13 subsequent siblings) 23 siblings, 0 replies; 146+ messages in thread From: Stefan Richter @ 2007-03-20 23:10 UTC (permalink / raw) To: linux-kernel; +Cc: Andrew Morton, linux1394-devel, Kristian Høgsberg Andrew Morton wrote: > Will appear later at > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ ... > git-ieee1394.patch ... Just a note for readers of lkml: git-ieee1394.patch is steadily growing thanks to Kristian Høgsberg's work on his new alternative FireWire drivers. Recently Kristian posted preliminary patches to the popular low-level FireWire libraries libraw1394 and libdc1394, making them interoperable with his newly designed kernel--userspace ABI. (Mainline Linux' IEEE 1394 subsystem features a slightly unfortunate variety of userspace ABIs, some of them abstracted by the mentioned libraries, some directly used.) I heard Kristian also already worked on integration with HAL, i.e. there are now more and more pieces of the puzzle coming together. -- Stefan Richter -=====-=-=== --== =-=-- http://arcgraph.de/sr/ ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (9 preceding siblings ...) 2007-03-20 23:10 ` FireWire update in -mm (was 2.6.21-rc4-mm1) Stefan Richter @ 2007-03-20 23:49 ` Randy Dunlap 2007-03-21 1:47 ` 2.6.21-rc4-mm1 Randy Dunlap ` (12 subsequent siblings) 23 siblings, 0 replies; 146+ messages in thread From: Randy Dunlap @ 2007-03-20 23:49 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel On Mon, 19 Mar 2007 20:56:23 -0800 Andrew Morton wrote: > > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > Will appear later at > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ I think that this: config EEPROM_93CX6 tristate "EEPROM 93CX6 support" ---help--- This is a driver for the EEPROM chipsets 93c46 and 93c66. The driver supports both read as well as write commands. should not be in lib/Kconfig. lib/ is not for drivers. or (simpler) s/driver/library/ but I think I'd rather see it in drivers/misc/. and the help text needs to be indented 2 more spaces... --- ~Randy boilerplate: *** Remember to use Documentation/SubmitChecklist when testing your code *** ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (10 preceding siblings ...) 2007-03-20 23:49 ` 2.6.21-rc4-mm1 Randy Dunlap @ 2007-03-21 1:47 ` Randy Dunlap 2007-03-21 18:36 ` 2.6.21-rc4-mm1 Greg KH [not found] ` <1174433034.62033.16.camel@localhost> ` (11 subsequent siblings) 23 siblings, 1 reply; 146+ messages in thread From: Randy Dunlap @ 2007-03-21 1:47 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel, gregkh, tglx On Mon, 19 Mar 2007 20:56:23 -0800 Andrew Morton wrote: > > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > Will appear later at > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ UIO_CIF should depend on PCI ?? With CONFIG_PCI=n, I get: ERROR: "pci_module_init" [drivers/uio/uio_cif.ko] undefined! ERROR: "pci_release_regions" [drivers/uio/uio_cif.ko] undefined! make[1]: *** [__modpost] Error 1 make: *** [modules] Error 2 --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 1:47 ` 2.6.21-rc4-mm1 Randy Dunlap @ 2007-03-21 18:36 ` Greg KH 0 siblings, 0 replies; 146+ messages in thread From: Greg KH @ 2007-03-21 18:36 UTC (permalink / raw) To: Randy Dunlap; +Cc: Andrew Morton, linux-kernel, tglx On Tue, Mar 20, 2007 at 06:47:04PM -0700, Randy Dunlap wrote: > On Mon, 19 Mar 2007 20:56:23 -0800 Andrew Morton wrote: > > > > > Temporarily at > > > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > > > Will appear later at > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > > > UIO_CIF should depend on PCI ?? > > With CONFIG_PCI=n, I get: > > ERROR: "pci_module_init" [drivers/uio/uio_cif.ko] undefined! > ERROR: "pci_release_regions" [drivers/uio/uio_cif.ko] undefined! > make[1]: *** [__modpost] Error 1 > make: *** [modules] Error 2 Thanks, I've made that change now. greg k-h ^ permalink raw reply [flat|nested] 146+ messages in thread
[parent not found: <1174433034.62033.16.camel@localhost>]
* Re: 2.6.21-rc4-mm1 [not found] ` <1174433034.62033.16.camel@localhost> @ 2007-03-21 6:36 ` Andrew Morton 2007-03-21 9:52 ` 2.6.21-rc4-mm1 Edward Shishkin ` (4 more replies) 0 siblings, 5 replies; 146+ messages in thread From: Andrew Morton @ 2007-03-21 6:36 UTC (permalink / raw) To: Zan Lynx; +Cc: linux-kernel, linux-wireless, bluez-devel, reiserfs-dev On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote: > On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote: > > Temporarily at > > > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > > > Will appear later at > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > > First impressions: > Several of the same bugs as rc3-mm*: > * Freezes immediately if I touch the wlan0 device after loading > the new Broadcom wireless driver. cc linux-wireless > * Freezes immediately if I allow Bluetooth to configure. cc bluez-devel > * All freezes simply stop, no BUG or panic happens, no watchdog, > soft or NMI ever triggers. Thinking about it, I wonder if > disabling EDAC_K8 would help here? Does it steal NMI? I'll try > that later. Mabe that will be fixed by the just-uploaded ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/hot-fixes/tty-in-tiocsctty-when-we-steal-a-tty-hang-it-up-fix.patch > * I am using Reiser4 and after one of the above freezes and hard > power cycle, files that were in use *read*only* are filled with > zeros. For example, while testing and experiencing the above > freezes, I lost /etc/ld.so.preload > and /lib/security/pam_limits.so. What the heck? cc reiserfs-dev <most of remainder retained, sorry> > Good points: > * Runs longer than 5 minutes, since I am typing this while using > it. > * I like RDSL so far. > > Advice on who to annoy with further bug reports is welcome. Bluetooth > people? USB people? Broadcom driver people, probably. > > The system is a Athlon64 laptop, nForce3 motherboard. > Current lspci, dmesg (cannot get the frozen dmesgs, sorry) and .config > follow: > 00:00.0 Host bridge: nVidia Corporation nForce3 Host Bridge (rev a4) > 00:01.0 ISA bridge: nVidia Corporation nForce3 LPC Bridge (rev a6) > 00:01.1 SMBus: nVidia Corporation nForce3 SMBus (rev a4) > 00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5) > 00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5) > 00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2) > 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 Audio (rev a2) > 00:06.1 Modem: nVidia Corporation nForce3 Audio (rev a2) > 00:08.0 IDE interface: nVidia Corporation nForce3 IDE (rev a5) > 00:0a.0 PCI bridge: nVidia Corporation nForce3 PCI Bridge (rev a2) > 00:0b.0 PCI bridge: nVidia Corporation nForce3 AGP Bridge (rev a4) > 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration > 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map > 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller > 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control > 01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 420 Go 32M] (rev a3) > 02:00.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link) > 02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) > 02:02.0 Network controller: Broadcom Corporation BCM4303 802.11b Wireless LAN Controller (rev 02) > 02:04.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01) > 02:04.1 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01) > 02:04.2 System peripheral: Texas Instruments PCI1620 Firmware Loading Function (rev 01) > > [ 0.000000] Linux version 2.6.21-rc4-mm1 (root@zephyr) (gcc version 4.2.0-alpha20070307 (prerelease) (Gentoo 4.2.0_alpha20070307)) #1 SMP PREEMPT Tue Mar 20 14:25:42 MDT 2007 > [ 0.000000] Command line: root=/dev/sda2 rootfstype=reiser4 ro i8042.nomux elevator=cfq resume=/dev/sda3 single > [ 0.000000] BIOS-provided physical RAM map: > [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable) > [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) > [ 0.000000] BIOS-e820: 00000000000d0000 - 0000000000100000 (reserved) > [ 0.000000] BIOS-e820: 0000000000100000 - 000000003ff70000 (usable) > [ 0.000000] BIOS-e820: 000000003ff70000 - 000000003ff7f000 (ACPI data) > [ 0.000000] BIOS-e820: 000000003ff7f000 - 000000003ff80000 (ACPI NVS) > [ 0.000000] BIOS-e820: 000000003ff80000 - 0000000040000000 (reserved) > [ 0.000000] BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved) > [ 0.000000] Entering add_active_range(0, 0, 159) 0 entries of 256 used > [ 0.000000] Entering add_active_range(0, 256, 262000) 1 entries of 256 used > [ 0.000000] end_pfn_map = 1048576 > [ 0.000000] DMI present. > [ 0.000000] ACPI: RSDP 000F7240, 0014 (r0 PTLTD ) > [ 0.000000] ACPI: RSDT 3FF7A87E, 0034 (r1 PTLTD RSDT 6040000 LTP 0) > [ 0.000000] ACPI: FACP 3FF7EE13, 0074 (r1 NVIDIA CK8 6040000 PTL_ F4240) > [ 0.000000] ACPI: DSDT 3FF7A8B2, 4561 (r1 NVIDIA CK8 6040000 MSFT 100000E) > [ 0.000000] ACPI: FACS 3FF7FFC0, 0040 > [ 0.000000] ACPI: APIC 3FF7EE87, 005A (r1 NVIDIA NV_APIC_ 6040000 LTP 0) > [ 0.000000] ACPI: BOOT 3FF7EEE1, 0028 (r1 PTLTD $SBFTBL$ 6040000 LTP 1) > [ 0.000000] ACPI: SSDT 3FF7EF09, 00F7 (r1 PTLTD POWERNOW 6040000 LTP 1) > [ 0.000000] Entering add_active_range(0, 0, 159) 0 entries of 256 used > [ 0.000000] Entering add_active_range(0, 256, 262000) 1 entries of 256 used > [ 0.000000] No mptable found. > [ 0.000000] sizeof(struct page) = 88 > [ 0.000000] Zone PFN ranges: > [ 0.000000] DMA 0 -> 4096 > [ 0.000000] DMA32 4096 -> 1048576 > [ 0.000000] Normal 1048576 -> 1048576 > [ 0.000000] Movable zone start PFN for each node > [ 0.000000] early_node_map[2] active PFN ranges > [ 0.000000] 0: 0 -> 159 > [ 0.000000] 0: 256 -> 262000 > [ 0.000000] On node 0 totalpages: 261903 > [ 0.000000] Node 0 memmap at 0xffff810001000000 size 23068672 first pfn 0xffff810001000000 > [ 0.000000] DMA zone: 88 pages used for memmap > [ 0.000000] DMA zone: 2335 pages reserved > [ 0.000000] DMA zone: 1576 pages, LIFO batch:0 > [ 0.000000] DMA32 zone: 5540 pages used for memmap > [ 0.000000] DMA32 zone: 252364 pages, LIFO batch:31 > [ 0.000000] Normal zone: 0 pages used for memmap > [ 0.000000] Movable zone: 0 pages used for memmap > [ 0.000000] Nvidia board detected. Ignoring ACPI timer override. > [ 0.000000] If you got timer trouble try acpi_use_timer_override > [ 0.000000] ACPI: PM-Timer IO Port: 0x8008 > [ 0.000000] ACPI: Local APIC address 0xfee00000 > [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) > [ 0.000000] Processor #0 (Bootup-CPU) > [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) > [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) > [ 0.000000] IOAPIC[0]: apic_id 2, address 0xfec00000, GSI 0-23 > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > [ 0.000000] ACPI: BIOS IRQ0 pin2 override ignored. > [ 0.000000] ACPI: IRQ9 used by override. > [ 0.000000] Setting APIC routing to flat > [ 0.000000] Using ACPI (MADT) for SMP configuration information > [ 0.000000] Nosave address range: 000000000009f000 - 00000000000a0000 > [ 0.000000] Nosave address range: 00000000000a0000 - 00000000000d0000 > [ 0.000000] Nosave address range: 00000000000d0000 - 0000000000100000 > [ 0.000000] Allocating PCI resources starting at 50000000 (gap: 40000000:bff80000) > [ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs > [ 0.000000] PERCPU: Allocating 37312 bytes of per cpu data > [ 0.000000] Built 1 zonelists. Total pages: 253940 > [ 0.000000] Kernel command line: root=/dev/sda2 rootfstype=reiser4 ro i8042.nomux elevator=cfq resume=/dev/sda3 single > [ 0.000000] Initializing CPU#0 > [ 0.000000] PID hash table entries: 4096 (order: 12, 32768 bytes) > [ 17.397762] time.c: Detected 2194.378 MHz processor. > [ 17.399354] Console: colour VGA+ 80x25 > [ 17.402298] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar > [ 17.402371] ... MAX_LOCKDEP_SUBCLASSES: 8 > [ 17.402423] ... MAX_LOCK_DEPTH: 30 > [ 17.402476] ... MAX_LOCKDEP_KEYS: 2048 > [ 17.402528] ... CLASSHASH_SIZE: 1024 > [ 17.402581] ... MAX_LOCKDEP_ENTRIES: 8192 > [ 17.402633] ... MAX_LOCKDEP_CHAINS: 16384 > [ 17.402685] ... CHAINHASH_SIZE: 8192 > [ 17.402744] memory used by lock dependency info: 1648 kB > [ 17.402798] per task-struct memory footprint: 1680 bytes > [ 17.402853] ------------------------ > [ 17.402903] | Locking API testsuite: > [ 17.402954] ---------------------------------------------------------------------------- > [ 17.403028] | spin |wlock |rlock |mutex | wsem | rsem | > [ 17.403101] -------------------------------------------------------------------------- > [ 17.403179] A-A deadlock: ok | ok | ok | ok | ok | ok | > [ 17.404370] A-B-B-A deadlock: ok | ok | ok | ok | ok | ok | > [ 17.405486] A-B-B-C-C-A deadlock: ok | ok | ok | ok | ok | ok | > [ 17.406652] A-B-C-A-B-C deadlock: ok | ok | ok | ok | ok | ok | > [ 17.407826] A-B-B-C-C-D-D-A deadlock: ok | ok | ok | ok | ok | ok | > [ 17.409052] A-B-C-D-B-D-D-A deadlock: ok | ok | ok | ok | ok | ok | > [ 17.410280] A-B-C-D-B-C-D-A deadlock: ok | ok | ok | ok | ok | ok | > [ 17.411514] double unlock: ok | ok | ok | ok | ok | ok | > [ 17.412580] initialize held: ok | ok | ok | ok | ok | ok | > [ 17.413647] bad unlock order: ok | ok | ok | ok | ok | ok | > [ 17.414777] -------------------------------------------------------------------------- > [ 17.414851] recursive read-lock: | ok | | ok | > [ 17.415334] recursive read-lock #2: | ok | | ok | > [ 17.415824] mixed read-write-lock: | ok | | ok | > [ 17.416312] mixed write-read-lock: | ok | | ok | > [ 17.416807] -------------------------------------------------------------------------- > [ 17.416880] hard-irqs-on + irq-safe-A/12: ok | ok | ok | > [ 17.417444] soft-irqs-on + irq-safe-A/12: ok | ok | ok | > [ 17.418018] hard-irqs-on + irq-safe-A/21: ok | ok | ok | > [ 17.418583] soft-irqs-on + irq-safe-A/21: ok | ok | ok | > [ 17.419156] sirq-safe-A => hirqs-on/12: ok | ok | ok | > [ 17.419730] sirq-safe-A => hirqs-on/21: ok | ok | ok | > [ 17.420294] hard-safe-A + irqs-on/12: ok | ok | ok | > [ 17.420865] soft-safe-A + irqs-on/12: ok | ok | ok | > [ 17.421432] hard-safe-A + irqs-on/21: ok | ok | ok | > [ 17.422003] soft-safe-A + irqs-on/21: ok | ok | ok | > [ 17.422568] hard-safe-A + unsafe-B #1/123: ok | ok | ok | > [ 17.423164] soft-safe-A + unsafe-B #1/123: ok | ok | ok | > [ 17.423759] hard-safe-A + unsafe-B #1/132: ok | ok | ok | > [ 17.424347] soft-safe-A + unsafe-B #1/132: ok | ok | ok | > [ 17.424943] hard-safe-A + unsafe-B #1/213: ok | ok | ok | > [ 17.425530] soft-safe-A + unsafe-B #1/213: ok | ok | ok | > [ 17.426126] hard-safe-A + unsafe-B #1/231: ok | ok | ok | > [ 17.426713] soft-safe-A + unsafe-B #1/231: ok | ok | ok | > [ 17.427296] hard-safe-A + unsafe-B #1/312: ok | ok | ok | > [ 17.427874] soft-safe-A + unsafe-B #1/312: ok | ok | ok | > [ 17.428446] hard-safe-A + unsafe-B #1/321: ok | ok | ok | > [ 17.429035] soft-safe-A + unsafe-B #1/321: ok | ok | ok | > [ 17.429618] hard-safe-A + unsafe-B #2/123: ok | ok | ok | > [ 17.430205] soft-safe-A + unsafe-B #2/123: ok | ok | ok | > [ 17.430798] hard-safe-A + unsafe-B #2/132: ok | ok | ok | > [ 17.431376] soft-safe-A + unsafe-B #2/132: ok | ok | ok | > [ 17.431969] hard-safe-A + unsafe-B #2/213: ok | ok | ok | > [ 17.432550] soft-safe-A + unsafe-B #2/213: ok | ok | ok | > [ 17.433143] hard-safe-A + unsafe-B #2/231: ok | ok | ok | > [ 17.433726] soft-safe-A + unsafe-B #2/231: ok | ok | ok | > [ 17.434307] hard-safe-A + unsafe-B #2/312: ok | ok | ok | > [ 17.434894] soft-safe-A + unsafe-B #2/312: ok | ok | ok | > [ 17.435479] hard-safe-A + unsafe-B #2/321: ok | ok | ok | > [ 17.436063] soft-safe-A + unsafe-B #2/321: ok | ok | ok | > [ 17.436647] hard-irq lock-inversion/123: ok | ok | ok | > [ 17.437237] soft-irq lock-inversion/123: ok | ok | ok | > [ 17.437831] hard-irq lock-inversion/132: ok | ok | ok | > [ 17.438410] soft-irq lock-inversion/132: ok | ok | ok | > [ 17.439004] hard-irq lock-inversion/213: ok | ok | ok | > [ 17.439586] soft-irq lock-inversion/213: ok | ok | ok | > [ 17.440180] hard-irq lock-inversion/231: ok | ok | ok | > [ 17.440765] soft-irq lock-inversion/231: ok | ok | ok | > [ 17.441347] hard-irq lock-inversion/312: ok | ok | ok | > [ 17.441934] soft-irq lock-inversion/312: ok | ok | ok | > [ 17.442520] hard-irq lock-inversion/321: ok | ok | ok | > [ 17.443105] soft-irq lock-inversion/321: ok | ok | ok | > [ 17.443694] hard-irq read-recursion/123: ok | > [ 17.443943] soft-irq read-recursion/123: ok | > [ 17.444193] hard-irq read-recursion/132: ok | > [ 17.444441] soft-irq read-recursion/132: ok | > [ 17.444700] hard-irq read-recursion/213: ok | > [ 17.444949] soft-irq read-recursion/213: ok | > [ 17.445199] hard-irq read-recursion/231: ok | > [ 17.445448] soft-irq read-recursion/231: ok | > [ 17.445707] hard-irq read-recursion/312: ok | > [ 17.445956] soft-irq read-recursion/312: ok | > [ 17.446206] hard-irq read-recursion/321: ok | > [ 17.446454] soft-irq read-recursion/321: ok | > [ 17.446711] ------------------------------------------------------- > [ 17.446767] Good, all 218 testcases passed! | > [ 17.446820] --------------------------------- > [ 17.447871] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) > [ 17.448711] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) > [ 17.448901] Checking aperture... > [ 17.448953] CPU 0: aperture @ e8000000 size 128 MB > [ 17.470739] Memory: 1013752k/1048000k available (3200k kernel code, 33568k reserved, 1519k data, 212k init) > [ 17.530543] Calibrating delay using timer specific routine.. 4390.56 BogoMIPS (lpj=2195280) > [ 17.530799] Mount-cache hash table entries: 256 > [ 17.531328] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > [ 17.531387] CPU: L2 Cache: 1024K (64 bytes/line) > [ 17.531462] SMP alternatives: switching to UP code > [ 17.531743] Freeing SMP alternatives: 28k freed > [ 17.531816] ACPI: Core revision 20070126 > [ 17.536624] Parsing all Control Methods: > [ 17.536769] Table [DSDT](id 0001) - 650 Objects with 66 Devices 205 Methods 24 Regions > [ 17.538016] Parsing all Control Methods: > [ 17.538146] Table [SSDT](id 0002) - 3 Objects with 0 Devices 1 Methods 0 Regions > [ 17.538263] tbxface-0587 [02] tb_load_namespace : ACPI Tables successfully acquired > [ 17.558729] evxfevnt-0091 [02] enable : Transition to ACPI mode successful > [ 17.569330] Using local APIC timer interrupts. > [ 17.614892] result 12468058 > [ 17.614942] Detected 12.468 MHz APIC timer. > [ 17.615526] Brought up 1 CPUs > [ 17.615800] PM: Adding info for No Bus:platform > [ 17.616047] NET: Registered protocol family 16 > [ 17.616280] No dock devices found. > [ 17.616370] PM: Adding info for No Bus:vtcon0 > [ 17.616570] ACPI: bus type pci registered > [ 17.616634] PCI: Using configuration type 1 > [ 17.618818] evgpeblk-0952 [04] ev_create_gpe_block : GPE 00 to 1F [_GPE] 4 regs on int 0x9 > [ 17.618981] evgpeblk-0952 [04] ev_create_gpe_block : GPE 20 to 5F [_GPE] 8 regs on int 0x9 > [ 17.619507] evgpeblk-1049 [03] ev_initialize_gpe_bloc: Found 5 Wake, Enabled 1 Runtime GPEs in this block > [ 17.619786] evgpeblk-1049 [03] ev_initialize_gpe_bloc: Found 0 Wake, Enabled 1 Runtime GPEs in this block > [ 17.620361] Completing Region/Field/Buffer/Package initialization:..................................................................... > [ 17.624273] Initialized 24/24 Regions 2/2 Fields 29/29 Buffers 14/21 Packages (662 nodes) > [ 17.624393] Initializing Device/Processor/Thermal objects by executing _INI methods:. > [ 17.624561] Executed 1 _INI methods requiring 0 _STA executions (examined 70 objects) > [ 17.624693] ACPI: Interpreter enabled > [ 17.624745] ACPI: (supports S0 S3 S4 S5) > [ 17.624983] ACPI: Using IOAPIC for interrupt routing > [ 17.625149] PM: Adding info for acpi:acpi_system:00 > [ 17.625225] PM: Adding info for acpi:button_power:00 > [ 17.625289] PM: Adding info for acpi:ACPI0007:00 > [ 17.625374] PM: Adding info for acpi:device:00 > [ 17.625455] PM: Adding info for acpi:pnp0c14:00 > [ 17.625608] PM: Adding info for acpi:PNP0C0C:00 > [ 17.625690] PM: Adding info for acpi:PNP0C0D:00 > [ 17.625774] PM: Adding info for acpi:PNP0A03:00 > [ 17.625928] PM: Adding info for acpi:device:01 > [ 17.626084] PM: Adding info for acpi:device:02 > [ 17.626170] PM: Adding info for acpi:device:03 > [ 17.626256] PM: Adding info for acpi:device:04 > [ 17.626338] PM: Adding info for acpi:device:05 > [ 17.626447] PM: Adding info for acpi:device:06 > [ 17.626525] PM: Adding info for acpi:device:07 > [ 17.626610] PM: Adding info for acpi:device:08 > [ 17.626686] PM: Adding info for acpi:device:09 > [ 17.626768] PM: Adding info for acpi:device:0a > [ 17.626847] PM: Adding info for acpi:device:0b > [ 17.626934] PM: Adding info for acpi:device:0c > [ 17.627011] PM: Adding info for acpi:device:0d > [ 17.627094] PM: Adding info for acpi:device:0e > [ 17.627176] PM: Adding info for acpi:device:0f > [ 17.627258] PM: Adding info for acpi:device:10 > [ 17.627336] PM: Adding info for acpi:device:11 > [ 17.627427] PM: Adding info for acpi:device:12 > [ 17.627506] PM: Adding info for acpi:device:13 > [ 17.627590] PM: Adding info for acpi:device:14 > [ 17.627672] PM: Adding info for acpi:device:15 > [ 17.627753] PM: Adding info for acpi:ACPI0003:00 > [ 17.627832] PM: Adding info for acpi:PNP0C02:00 > [ 17.627913] PM: Adding info for acpi:PNP0C01:00 > [ 17.628002] PM: Adding info for acpi:PNP0C09:00 > [ 17.667388] PM: Adding info for acpi:PNP0C0A:00 > [ 17.667474] PM: Adding info for acpi:PNP0C02:01 > [ 17.667555] PM: Adding info for acpi:PNP0000:00 > [ 17.667629] PM: Adding info for acpi:PNP0100:00 > [ 17.667708] PM: Adding info for acpi:PNP0200:00 > [ 17.667782] PM: Adding info for acpi:PNP0800:00 > [ 17.667862] PM: Adding info for acpi:PNP0B00:00 > [ 17.667936] PM: Adding info for acpi:PNP0C04:00 > [ 17.668093] PM: Adding info for acpi:PNP0303:00 > [ 17.668243] PM: Adding info for acpi:PNP0F13:00 > [ 17.668330] PM: Adding info for acpi:PNP0A05:00 > [ 17.668800] PM: Adding info for acpi:PNP0700:00 > [ 17.673598] PM: Adding info for acpi:PNP0401:00 > [ 17.673814] PM: Adding info for acpi:device:16 > [ 17.673974] PM: Adding info for acpi:device:17 > [ 17.674122] PM: Adding info for acpi:device:18 > [ 17.674287] PM: Adding info for acpi:video:00 > [ 17.674407] PM: Adding info for acpi:device:19 > [ 17.674526] PM: Adding info for acpi:device:1a > [ 17.674640] PM: Adding info for acpi:device:1b > [ 17.675014] PM: Adding info for acpi:PNP0C0F:00 > [ 17.675187] PM: Adding info for acpi:PNP0C0F:01 > [ 17.675371] PM: Adding info for acpi:PNP0C0F:02 > [ 17.675544] PM: Adding info for acpi:PNP0C0F:03 > [ 17.675724] PM: Adding info for acpi:PNP0C0F:04 > [ 17.675894] PM: Adding info for acpi:PNP0C0F:05 > [ 17.676072] PM: Adding info for acpi:PNP0C0F:06 > [ 17.676245] PM: Adding info for acpi:PNP0C0F:07 > [ 17.676430] PM: Adding info for acpi:PNP0C0F:08 > [ 17.676616] PM: Adding info for acpi:PNP0C0F:09 > [ 17.676795] PM: Adding info for acpi:PNP0C0F:0a > [ 17.676968] PM: Adding info for acpi:PNP0C0F:0b > [ 17.677150] PM: Adding info for acpi:PNP0C0F:0c > [ 17.677354] PM: Adding info for acpi:PNP0C0F:0d > [ 17.677428] PM: Adding info for acpi:thermal:00 > [ 17.677487] PM: Adding info for acpi:thermal:01 > [ 17.677838] ACPI: PCI Root Bridge [PCI0] (0000:00) > [ 17.677936] PM: Adding info for No Bus:pci0000:00 > [ 17.678314] 0000:00:08.0: cannot adjust BAR0 (not I/O) > [ 17.678371] 0000:00:08.0: cannot adjust BAR1 (not I/O) > [ 17.678427] 0000:00:08.0: cannot adjust BAR2 (not I/O) > [ 17.678481] 0000:00:08.0: cannot adjust BAR3 (not I/O) > [ 17.679034] PCI: Bus #03 (-#06) is hidden behind bridge #02 (-#02) (try 'pci=assign-busses') > [ 17.679109] Please report the result to linux-kernel to fix this permanently > [ 17.679229] PCI: Bus #07 (-#0a) is hidden behind bridge #02 (-#02) (try 'pci=assign-busses') > [ 17.679304] Please report the result to linux-kernel to fix this permanently > [ 17.679476] Boot video device is 0000:01:00.0 > [ 17.679535] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] > [ 17.679678] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P0._PRT] > [ 17.679749] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP0._PRT] > [ 17.680943] PM: Adding info for pci:0000:00:00.0 > [ 17.682179] PM: Adding info for pci:0000:00:01.0 > [ 17.683404] PM: Adding info for pci:0000:00:01.1 > [ 17.684622] PM: Adding info for pci:0000:00:02.0 > [ 17.685836] PM: Adding info for pci:0000:00:02.1 > [ 17.687056] PM: Adding info for pci:0000:00:02.2 > [ 17.688272] PM: Adding info for pci:0000:00:06.0 > [ 17.689498] PM: Adding info for pci:0000:00:06.1 > [ 17.690712] PM: Adding info for pci:0000:00:08.0 > [ 17.691935] PM: Adding info for pci:0000:00:0a.0 > [ 17.693149] PM: Adding info for pci:0000:00:0b.0 > [ 17.694382] PM: Adding info for pci:0000:00:18.0 > [ 17.695596] PM: Adding info for pci:0000:00:18.1 > [ 17.696821] PM: Adding info for pci:0000:00:18.2 > [ 17.698035] PM: Adding info for pci:0000:00:18.3 > [ 17.698147] PM: Adding info for pci:0000:02:00.0 > [ 17.698253] PM: Adding info for pci:0000:02:01.0 > [ 17.698373] PM: Adding info for pci:0000:02:02.0 > [ 17.698479] PM: Adding info for pci:0000:02:04.0 > [ 17.698590] PM: Adding info for pci:0000:02:04.1 > [ 17.698697] PM: Adding info for pci:0000:02:04.2 > [ 17.698814] PM: Adding info for pci:0000:01:00.0 > [ 17.699206] ACPI: PCI Interrupt Link [LNK1] (IRQs 16 18 19) *0 > [ 17.699725] ACPI: PCI Interrupt Link [LNK2] (IRQs 16 18 19) *0 > [ 17.700246] ACPI: PCI Interrupt Link [LNK3] (IRQs 17) *0 > [ 17.700706] ACPI: PCI Interrupt Link [LNK4] (IRQs 16 18 19) *0, disabled. > [ 17.701249] ACPI: PCI Interrupt Link [LNK5] (IRQs 16 18 19) *0 > [ 17.701754] ACPI: PCI Interrupt Link [LSMB] (IRQs 20 21 22) *0 > [ 17.702253] ACPI: PCI Interrupt Link [LUS0] (IRQs 20 21 22) *0 > [ 17.702761] ACPI: PCI Interrupt Link [LUS1] (IRQs 20 21 22) *0 > [ 17.703260] ACPI: PCI Interrupt Link [LUS2] (IRQs 20 21 22) *0 > [ 17.703775] ACPI: PCI Interrupt Link [LMAC] (IRQs 20 21 22) *0, disabled. > [ 17.704311] ACPI: PCI Interrupt Link [LACI] (IRQs 20 21 22) *0 > [ 17.704816] ACPI: PCI Interrupt Link [LMCI] (IRQs 20 21 22) *0 > [ 17.705333] ACPI: PCI Interrupt Link [LPID] (IRQs 20 21 22) *0, disabled. > [ 17.705879] ACPI: PCI Interrupt Link [LTID] (IRQs 20 21 22) *0, disabled. > [ 17.706254] Linux Plug and Play Support v0.97 (c) Adam Belay > [ 17.706334] pnp: PnP ACPI init > [ 17.706401] PM: Adding info for No Bus:pnp0 > [ 17.706597] PM: Adding info for pnp:00:00 > [ 17.707281] PM: Adding info for pnp:00:01 > [ 17.707475] PM: Adding info for pnp:00:02 > [ 17.728319] PM: Adding info for pnp:00:03 > [ 17.728404] PM: Adding info for pnp:00:04 > [ 17.728465] PM: Adding info for pnp:00:05 > [ 17.728541] PM: Adding info for pnp:00:06 > [ 17.728606] PM: Adding info for pnp:00:07 > [ 17.728716] PM: Adding info for pnp:00:08 > [ 17.728822] PM: Adding info for pnp:00:09 > [ 17.729092] PM: Adding info for pnp:00:0a > [ 17.731090] PM: Adding info for pnp:00:0b > [ 17.732020] pnp: PnP ACPI: found 12 devices > [ 17.732153] Generic PHY: Registered new driver > [ 17.732403] SCSI subsystem initialized > [ 17.732504] libata version 2.20 loaded. > [ 17.732614] PCI: Using ACPI for IRQ routing > [ 17.732668] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report > [ 17.732752] PCI: Cannot allocate resource region 0 of device 0000:00:00.0 > [ 17.733015] agpgart: Detected AGP bridge 0 > [ 17.733072] agpgart: Setting up Nforce3 AGP. > [ 17.737586] PM: Adding info for No Bus:agpgart > [ 17.737683] agpgart: AGP aperture is 128M @ 0xe8000000 > [ 17.737871] pnp: 00:01: ioport range 0x8000-0x807f has been reserved > [ 17.737929] pnp: 00:01: ioport range 0x8080-0x80ff has been reserved > [ 17.737986] pnp: 00:01: ioport range 0x8400-0x847f has been reserved > [ 17.738044] pnp: 00:01: ioport range 0x8480-0x84ff has been reserved > [ 17.738101] pnp: 00:01: ioport range 0x8800-0x887f has been reserved > [ 17.738158] pnp: 00:01: ioport range 0x8880-0x88ff has been reserved > [ 17.738216] Time: tsc clocksource has been installed. > [ 17.738275] pnp: 00:01: ioport range 0x2040-0x207f has been reserved > [ 17.738332] pnp: 00:01: ioport range 0x2000-0x203f has been reserved > [ 17.738396] pnp: 00:02: iomem range 0xfff80000-0xffffffff has been reserved > [ 17.738455] pnp: 00:02: iomem range 0xfec00000-0xfec00fff has been reserved > [ 17.738514] pnp: 00:02: iomem range 0xfee00000-0xfeefffff has been reserved > [ 17.738572] pnp: 00:02: iomem range 0xfed00000-0xfed00fff has been reserved > [ 17.738673] PM: Adding info for No Bus:mem > [ 17.738725] PM: Adding info for No Bus:kmem > [ 17.738768] PM: Adding info for No Bus:null > [ 17.738816] PM: Adding info for No Bus:port > [ 17.738858] PM: Adding info for No Bus:zero > [ 17.738905] PM: Adding info for No Bus:full > [ 17.738947] PM: Adding info for No Bus:random > [ 17.738997] PM: Adding info for No Bus:urandom > [ 17.739039] PM: Adding info for No Bus:kmsg > [ 17.739158] PCI: Failed to allocate mem resource #10:4000000@e4000000 for 0000:02:04.0 > [ 17.739235] PCI: Failed to allocate mem resource #10:4000000@e4000000 for 0000:02:04.1 > [ 17.739313] PCI: Bus 3, cardbus bridge: 0000:02:04.0 > [ 17.739367] IO window: 00003000-000030ff > [ 17.739421] IO window: 00003400-000034ff > [ 17.739476] PREFETCH window: 50000000-53ffffff > [ 17.739531] PCI: Bus 7, cardbus bridge: 0000:02:04.1 > [ 17.739585] IO window: 00003800-000038ff > [ 17.739639] IO window: 00003c00-00003cff > [ 17.739693] PREFETCH window: 54000000-57ffffff > [ 17.739748] PCI: Bridge: 0000:00:0a.0 > [ 17.739800] IO window: 3000-7fff > [ 17.739853] MEM window: e0100000-e17fffff > [ 17.739906] PREFETCH window: 50000000-57ffffff > [ 17.739962] PCI: Bridge: 0000:00:0b.0 > [ 17.740013] IO window: disabled. > [ 17.740067] MEM window: e2000000-e2ffffff > [ 17.740121] PREFETCH window: f0000000-f80fffff > [ 17.740183] PCI: Setting latency timer of device 0000:00:0a.0 to 64 > [ 17.740708] ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 19 > [ 17.740772] ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [LNK1] -> GSI 19 (level, low) -> IRQ 19 > [ 17.741334] ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 18 > [ 17.741394] ACPI: PCI Interrupt 0000:02:04.1[B] -> Link [LNK2] -> GSI 18 (level, low) -> IRQ 18 > [ 17.741573] NET: Registered protocol family 2 > [ 17.751310] IP route cache hash table entries: 32768 (order: 6, 262144 bytes) > [ 17.751620] TCP established hash table entries: 65536 (order: 10, 4194304 bytes) > [ 17.757500] TCP bind hash table entries: 65536 (order: 9, 3670016 bytes) > [ 17.762325] TCP: Hash tables configured (established 65536 bind 65536) > [ 17.762418] TCP reno registered > [ 17.765663] Simple Boot Flag at 0x37 set to 0x1 > [ 17.765831] PM: Adding info for No Bus:mcelog > [ 17.765911] PM: Adding info for No Bus:msr0 > [ 17.765974] PM: Adding info for No Bus:cpu0 > [ 17.766279] PM: Adding info for platform:pcspkr > [ 17.766553] PM: Adding info for No Bus:snapshot > [ 17.766602] audit: initializing netlink socket (disabled) > [ 17.766677] audit(1174429488.298:1): initialized > [ 17.766920] Total HugeTLB memory allocated, 0 > [ 17.767309] Loading Reiser4. See www.namesys.com for a description of Reiser4. > [ 17.767640] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). > [ 17.768058] io scheduler noop registered > [ 17.768111] io scheduler anticipatory registered > [ 17.768164] io scheduler deadline registered > [ 17.768257] io scheduler cfq registered (default) > [ 17.769736] ACPI: AC Adapter [ACAD] (on-line) > [ 17.791230] ACPI: Battery Slot [BAT1] (battery present) > [ 17.791428] input: Power Button (FF) as /class/input/input0 > [ 17.791490] ACPI: Power Button (FF) [PWRF] > [ 17.791611] input: Power Button (CM) as /class/input/input1 > [ 17.791667] ACPI: Power Button (CM) [PWRB] > [ 17.791799] input: Lid Switch as /class/input/input2 > [ 17.791854] ACPI: Lid Switch [LID] > [ 17.792327] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) > [ 17.793720] ACPI: CPU0 (power states: C1[C1] C2[C2]) > [ 17.793997] cpuidle: using driver acpi_idle > [ 17.825473] ACPI Exception (thermal-0412): AE_NOT_FOUND, Invalid active threshold [0] [20070126] > [ 17.828471] ACPI: Thermal Zone [THRM] (62 C) > [ 17.828571] PM: Adding info for No Bus:tty > [ 17.828615] PM: Adding info for No Bus:console > [ 17.828663] PM: Adding info for No Bus:ptmx > [ 17.828702] PM: Adding info for No Bus:tty0 > [ 17.828765] PM: Adding info for No Bus:vcs > [ 17.828811] PM: Adding info for No Bus:vcsa > [ 17.828858] PM: Adding info for No Bus:tty1 > [ 17.828908] PM: Adding info for No Bus:tty2 > [ 17.828949] PM: Adding info for No Bus:tty3 > [ 17.828996] PM: Adding info for No Bus:tty4 > [ 17.829035] PM: Adding info for No Bus:tty5 > [ 17.829089] PM: Adding info for No Bus:tty6 > [ 17.829132] PM: Adding info for No Bus:tty7 > [ 17.829183] PM: Adding info for No Bus:tty8 > [ 17.829228] PM: Adding info for No Bus:tty9 > [ 17.829280] PM: Adding info for No Bus:tty10 > [ 17.829323] PM: Adding info for No Bus:tty11 > [ 17.829374] PM: Adding info for No Bus:tty12 > [ 17.829418] PM: Adding info for No Bus:tty13 > [ 17.829474] PM: Adding info for No Bus:tty14 > [ 17.829518] PM: Adding info for No Bus:tty15 > [ 17.829570] PM: Adding info for No Bus:tty16 > [ 17.829614] PM: Adding info for No Bus:tty17 > [ 17.829667] PM: Adding info for No Bus:tty18 > [ 17.829713] PM: Adding info for No Bus:tty19 > [ 17.829767] PM: Adding info for No Bus:tty20 > [ 17.829820] PM: Adding info for No Bus:tty21 > [ 17.829874] PM: Adding info for No Bus:tty22 > [ 17.829922] PM: Adding info for No Bus:tty23 > [ 17.829976] PM: Adding info for No Bus:tty24 > [ 17.830024] PM: Adding info for No Bus:tty25 > [ 17.830083] PM: Adding info for No Bus:tty26 > [ 17.830130] PM: Adding info for No Bus:tty27 > [ 17.830185] PM: Adding info for No Bus:tty28 > [ 17.830230] PM: Adding info for No Bus:tty29 > [ 17.830286] PM: Adding info for No Bus:tty30 > [ 17.830332] PM: Adding info for No Bus:tty31 > [ 17.830387] PM: Adding info for No Bus:tty32 > [ 17.830433] PM: Adding info for No Bus:tty33 > [ 17.830489] PM: Adding info for No Bus:tty34 > [ 17.830540] PM: Adding info for No Bus:tty35 > [ 17.830600] PM: Adding info for No Bus:tty36 > [ 17.830647] PM: Adding info for No Bus:tty37 > [ 17.830705] PM: Adding info for No Bus:tty38 > [ 17.830751] PM: Adding info for No Bus:tty39 > [ 17.830807] PM: Adding info for No Bus:tty40 > [ 17.830855] PM: Adding info for No Bus:tty41 > [ 17.830912] PM: Adding info for No Bus:tty42 > [ 17.830960] PM: Adding info for No Bus:tty43 > [ 17.831015] PM: Adding info for No Bus:tty44 > [ 17.831063] PM: Adding info for No Bus:tty45 > [ 17.831138] PM: Adding info for No Bus:tty46 > [ 17.831181] PM: Adding info for No Bus:tty47 > [ 17.831235] PM: Adding info for No Bus:tty48 > [ 17.831280] PM: Adding info for No Bus:tty49 > [ 17.831334] PM: Adding info for No Bus:tty50 > [ 17.831378] PM: Adding info for No Bus:tty51 > [ 17.831429] PM: Adding info for No Bus:tty52 > [ 17.831474] PM: Adding info for No Bus:tty53 > [ 17.831527] PM: Adding info for No Bus:tty54 > [ 17.831574] PM: Adding info for No Bus:tty55 > [ 17.831633] PM: Adding info for No Bus:tty56 > [ 17.831683] PM: Adding info for No Bus:tty57 > [ 17.831740] PM: Adding info for No Bus:tty58 > [ 17.831787] PM: Adding info for No Bus:tty59 > [ 17.831844] PM: Adding info for No Bus:tty60 > [ 17.831893] PM: Adding info for No Bus:tty61 > [ 17.831952] PM: Adding info for No Bus:tty62 > [ 17.832002] PM: Adding info for No Bus:tty63 > [ 17.832160] PM: Adding info for No Bus:rtc > [ 17.832208] Real Time Clock Driver v1.12ac > [ 17.832270] PM: Adding info for No Bus:hpet > [ 17.832420] PM: Adding info for No Bus:watchdog > [ 17.832457] Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60 sec (nowayout= 0) > [ 17.832534] Linux agpgart interface v0.102 (c) Dave Jones > [ 17.832589] Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds). > [ 17.832664] Hangcheck: Using get_cycles(). > [ 17.833305] loop: loaded (max 8 devices) > [ 17.833391] Marvell 88E1101: Registered new driver > [ 17.833475] Marvell 88E1111: Registered new driver > [ 17.833560] Marvell 88E1145: Registered new driver > [ 17.833652] Davicom DM9161E: Registered new driver > [ 17.833736] Davicom DM9131: Registered new driver > [ 17.833821] Cicada Cis8204: Registered new driver > [ 17.833905] Cicada Cis8201: Registered new driver > [ 17.833997] LXT970: Registered new driver > [ 17.834087] LXT971: Registered new driver > [ 17.834171] QS6612: Registered new driver > [ 17.834254] SMSC LAN83C185: Registered new driver > [ 17.834402] PM: Adding info for No Bus:lo > [ 17.834607] 8139too Fast Ethernet driver 0.9.28 > [ 17.834685] ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [LNK2] -> GSI 18 (level, low) -> IRQ 18 > [ 17.835148] PM: Adding info for No Bus:eth0 > [ 17.835216] eth0: RealTek RTL8139 at 0xffffc20000018800, 00:0f:b0:07:dc:49, IRQ 18 > [ 17.835290] eth0: Identified 8139 chip type 'RTL-8101' > [ 17.835500] pata_amd 0000:00:08.0: version 0.3.8 > [ 17.835526] PCI: Setting latency timer of device 0000:00:08.0 to 64 > [ 17.835636] ata1: PATA max UDMA/133 cmd 0x00000000000101f0 ctl 0x00000000000103f6 bmdma 0x0000000000012080 irq 14 > [ 17.835753] ata2: PATA max UDMA/133 cmd 0x0000000000010170 ctl 0x0000000000010376 bmdma 0x0000000000012088 irq 15 > [ 17.835848] scsi0 : pata_amd > [ 17.835912] PM: Adding info for No Bus:host0 > [ 17.990015] ata1.00: ATA-6: HTS721010G9AT00, MCZOA51A, max UDMA/100 > [ 17.990073] ata1.00: 195371568 sectors, multi 16: LBA48 > [ 17.993003] ata1.00: configured for UDMA/100 > [ 17.993061] scsi1 : pata_amd > [ 17.993119] PM: Adding info for No Bus:host1 > [ 18.297591] ata2.00: ATAPI, max MWDMA2 > [ 18.451340] ata2.00: configured for MWDMA2 > [ 18.451405] PM: Adding info for No Bus:target0:0:0 > [ 18.451680] scsi 0:0:0:0: Direct-Access ATA HTS721010G9AT00 MCZO PQ: 0 ANSI: 5 > [ 18.452894] PM: Adding info for scsi:0:0:0:0 > [ 18.453120] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB) > [ 18.453193] sd 0:0:0:0: [sda] Write Protect is off > [ 18.453248] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > [ 18.453271] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > [ 18.453648] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB) > [ 18.453717] sd 0:0:0:0: [sda] Write Protect is off > [ 18.453771] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > [ 18.453793] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > [ 18.453901] sda: sda1 sda2 sda3 > [ 18.471748] sd 0:0:0:0: [sda] Attached SCSI disk > [ 18.471874] PM: Adding info for No Bus:target1:0:0 > [ 18.472353] scsi 1:0:0:0: CD-ROM HL-DT-ST DVD+RW GCA-4040N 1.19 PQ: 0 ANSI: 5 > [ 18.472434] PM: Adding info for scsi:1:0:0:0 > [ 18.474384] sr0: scsi3-mmc drive: 40x/24x writer cd/rw xa/form2 cdda tray > [ 18.474443] Uniform CD-ROM driver Revision: 3.20 > [ 18.474628] sr 1:0:0:0: Attached scsi CD-ROM sr0 > [ 18.474809] Yenta: CardBus bridge found at 0000:02:04.0 [103c:006d] > [ 18.474880] PCI: Bus 3, cardbus bridge: 0000:02:04.0 > [ 18.474934] IO window: 00003000-000030ff > [ 18.474988] IO window: 00003400-000034ff > [ 18.475043] PREFETCH window: 50000000-53ffffff > [ 18.475103] MEM window: e0400000-e07fffff > [ 18.475159] Yenta: Enabling burst memory read transactions > [ 18.475215] Yenta: Using CSCINT to route CSC interrupts to PCI > [ 18.475270] Yenta: Routing CardBus interrupts to PCI > [ 18.475327] Yenta TI: socket 0000:02:04.0, mfunc 0x01111d22, devctl 0x64 > [ 18.698633] Yenta: ISA IRQ mask 0x0cf8, PCI irq 19 > [ 18.698687] Socket status: 30000086 > [ 18.698742] Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06 > [ 18.698816] pcmcia: parent PCI bridge I/O window: 0x3000 - 0x7fff > [ 18.698886] pcmcia: parent PCI bridge Memory window: 0xe0100000 - 0xe17fffff > [ 18.698945] pcmcia: parent PCI bridge Memory window: 0x50000000 - 0x57ffffff > [ 18.699145] PM: Adding info for No Bus:pcmcia_socket0 > [ 18.949375] Yenta: CardBus bridge found at 0000:02:04.1 [103c:006d] > [ 18.949447] Yenta: Using CSCINT to route CSC interrupts to PCI > [ 18.949502] Yenta: Routing CardBus interrupts to PCI > [ 18.949560] Yenta TI: socket 0000:02:04.1, mfunc 0x01111d22, devctl 0x64 > [ 19.172901] Yenta: ISA IRQ mask 0x0cf8, PCI irq 18 > [ 19.172955] Socket status: 30000006 > [ 19.173009] Yenta: Raising subordinate bus# of parent bus (#02) from #06 to #0a > [ 19.173083] pcmcia: parent PCI bridge I/O window: 0x3000 - 0x7fff > [ 19.173140] pcmcia: parent PCI bridge Memory window: 0xe0100000 - 0xe17fffff > [ 19.173198] pcmcia: parent PCI bridge Memory window: 0x50000000 - 0x57ffffff > [ 19.173373] PM: Adding info for No Bus:pcmcia_socket1 > [ 19.423712] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 > [ 19.423836] PM: Adding info for platform:i8042 > [ 19.433971] serio: i8042 KBD port at 0x60,0x64 irq 1 > [ 19.434082] PM: Adding info for serio:serio0 > [ 19.434178] serio: i8042 AUX port at 0x60,0x64 irq 12 > [ 19.434240] PM: Adding info for serio:serio1 > [ 19.434351] PM: Adding info for No Bus:psaux > [ 19.434390] mice: PS/2 mouse device common for all mice > [ 19.434590] async_tx: api initialized (sync-only) > [ 19.434645] xor: automatically using best checksumming function: generic_sse > [ 19.439565] generic_sse: 6560.000 MB/sec > [ 19.439618] xor: using function: generic_sse (6560.000 MB/sec) > [ 19.439674] EDAC MC: Ver: 2.0.1 Mar 20 2007 > [ 19.440144] EDAC MC0: Giving out device to k8_edac Athlon64/Opteron: DEV 0000:00:18.2 > [ 19.440257] cpuidle: using governor ladder > [ 19.440389] TCP cubic registered > [ 19.440440] Initializing XFRM netlink socket > [ 19.440515] NET: Registered protocol family 1 > [ 19.440575] NET: Registered protocol family 17 > [ 19.440642] NET: Registered protocol family 15 > [ 19.440746] powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3400+ processors (version 2.00.00) > [ 19.440940] powernow-k8: 0 : fid 0xe (2200 MHz), vid 0x2 > [ 19.440995] powernow-k8: 1 : fid 0xa (1800 MHz), vid 0xa > [ 19.441050] powernow-k8: 2 : fid 0x0 (800 MHz), vid 0x12 > [ 19.441737] swsusp: Resume From Partition /dev/sda3 > [ 19.441739] PM: Checking swsusp image. > [ 19.444558] Marking TSC unstable due to possible TSC halt in C2 > [ 19.444618] Time: acpi_pm clocksource has been installed. > [ 19.458341] PM: Resume from disk failed. > [ 19.499700] input: AT Translated Set 2 keyboard as /class/input/input3 > [ 19.576971] reiser4: sda2: found disk format 4.0.0. > [ 25.172977] VFS: Mounted root (reiser4 filesystem) readonly. > [ 25.173099] Freeing unused kernel memory: 212k freed > [ 25.223972] PM: Adding info for No Bus:vcs1 > [ 25.453962] PM: Adding info for No Bus:vcsa1 > [ 26.020896] PM: Removing info for No Bus:vcs1 > [ 26.021468] PM: Removing info for No Bus:vcsa1 > [ 26.021876] PM: Adding info for No Bus:vcs1 > [ 26.022218] PM: Adding info for No Bus:vcsa1 > [ 26.022602] PM: Removing info for No Bus:vcs1 > [ 26.022952] PM: Removing info for No Bus:vcsa1 > [ 26.233012] PM: Adding info for No Bus:vcs1 > [ 26.233388] PM: Adding info for No Bus:vcsa1 > [ 26.233839] PM: Removing info for No Bus:vcs1 > [ 26.234049] PM: Removing info for No Bus:vcsa1 > [ 26.235514] PM: Adding info for No Bus:vcs1 > [ 26.235956] PM: Adding info for No Bus:vcsa1 > [ 26.236402] PM: Removing info for No Bus:vcs1 > [ 26.236784] PM: Removing info for No Bus:vcsa1 > [ 26.237017] PM: Adding info for No Bus:vcs1 > [ 26.237587] PM: Adding info for No Bus:vcsa1 > [ 26.238069] PM: Removing info for No Bus:vcs1 > [ 26.238457] PM: Removing info for No Bus:vcsa1 > [ 26.302723] PM: Adding info for No Bus:vcs1 > [ 26.303340] PM: Adding info for No Bus:vcsa1 > [ 29.773194] sd 0:0:0:0: Attached scsi generic sg0 type 0 > [ 29.773218] sr 1:0:0:0: Attached scsi generic sg1 type 5 > [ 29.936763] usbcore: registered new interface driver usbfs > [ 29.936876] usbcore: registered new interface driver hub > [ 29.936938] usbcore: registered new device driver usb > [ 29.938045] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver > [ 29.938092] PCI: Enabling device 0000:00:02.0 (0004 -> 0006) > [ 29.938715] ACPI: PCI Interrupt Link [LUS0] enabled at IRQ 22 > [ 29.938727] ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LUS0] -> GSI 22 (level, low) -> IRQ 22 > [ 29.938746] PCI: Setting latency timer of device 0000:00:02.0 to 64 > [ 29.938750] ohci_hcd 0000:00:02.0: OHCI Host Controller > [ 29.943103] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1 > [ 30.154957] ohci_hcd 0000:00:02.0: irq 22, io mem 0xe0000000 > [ 30.190412] PM: Adding info for No Bus:timer > [ 30.208166] usb usb1: new device found, idVendor=0000, idProduct=0000 > [ 30.208171] usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1 > [ 30.208173] usb usb1: Product: OHCI Host Controller > [ 30.208175] usb usb1: Manufacturer: Linux 2.6.21-rc4-mm1 ohci_hcd > [ 30.208177] usb usb1: SerialNumber: 0000:00:02.0 > [ 30.208266] PM: Adding info for usb:usb1 > [ 30.208743] PM: Adding info for No Bus:usbdev1.1_ep00 > [ 30.208769] usb usb1: configuration #1 chosen from 1 choice > [ 30.209010] PM: Adding info for usb:1-0:1.0 > [ 30.209168] hub 1-0:1.0: USB hub found > [ 30.209274] hub 1-0:1.0: 3 ports detected > [ 30.310069] PM: Adding info for No Bus:usbdev1.1_ep81 > [ 30.310414] PM: Adding info for No Bus:usbdev1.1 > [ 30.310803] PCI: Enabling device 0000:00:02.1 (0004 -> 0006) > [ 30.311309] ACPI: PCI Interrupt Link [LUS1] enabled at IRQ 21 > [ 30.311320] ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [LUS1] -> GSI 21 (level, low) -> IRQ 21 > [ 30.311341] PCI: Setting latency timer of device 0000:00:02.1 to 64 > [ 30.311344] ohci_hcd 0000:00:02.1: OHCI Host Controller > [ 30.311377] ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2 > [ 30.523351] ohci_hcd 0000:00:02.1: irq 21, io mem 0xe0001000 > [ 30.576281] usb usb2: new device found, idVendor=0000, idProduct=0000 > [ 30.576285] usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1 > [ 30.576288] usb usb2: Product: OHCI Host Controller > [ 30.576290] usb usb2: Manufacturer: Linux 2.6.21-rc4-mm1 ohci_hcd > [ 30.576292] usb usb2: SerialNumber: 0000:00:02.1 > [ 30.576318] PM: Adding info for usb:usb2 > [ 30.576410] PM: Adding info for No Bus:usbdev2.1_ep00 > [ 30.576433] usb usb2: configuration #1 chosen from 1 choice > [ 30.576451] PM: Adding info for usb:2-0:1.0 > [ 30.576485] hub 2-0:1.0: USB hub found > [ 30.576499] hub 2-0:1.0: 3 ports detected > [ 30.677124] PM: Adding info for No Bus:usbdev2.1_ep81 > [ 30.677190] PM: Adding info for No Bus:usbdev2.1 > [ 30.677819] ACPI: PCI Interrupt Link [LUS2] enabled at IRQ 20 > [ 30.677832] ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [LUS2] -> GSI 20 (level, low) -> IRQ 20 > [ 30.677853] PCI: Setting latency timer of device 0000:00:02.2 to 64 > [ 30.677856] ehci_hcd 0000:00:02.2: EHCI Host Controller > [ 30.677889] ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3 > [ 30.677932] PCI: cache line size of 64 is not supported by device 0000:00:02.2 > [ 30.677957] ehci_hcd 0000:00:02.2: irq 20, io mem 0xe0004000 > [ 30.677962] ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 > [ 30.678054] usb usb3: new device found, idVendor=0000, idProduct=0000 > [ 30.678057] usb usb3: new device strings: Mfr=3, Product=2, SerialNumber=1 > [ 30.678059] usb usb3: Product: EHCI Host Controller > [ 30.678061] usb usb3: Manufacturer: Linux 2.6.21-rc4-mm1 ehci_hcd > [ 30.678063] usb usb3: SerialNumber: 0000:00:02.2 > [ 30.678072] PM: Adding info for usb:usb3 > [ 30.678141] PM: Adding info for No Bus:usbdev3.1_ep00 > [ 30.678162] usb usb3: configuration #1 chosen from 1 choice > [ 30.678184] PM: Adding info for usb:3-0:1.0 > [ 30.678207] hub 3-0:1.0: USB hub found > [ 30.678380] hub 3-0:1.0: 6 ports detected > [ 30.778960] PM: Adding info for No Bus:usbdev3.1_ep81 > [ 30.779025] PM: Adding info for No Bus:usbdev3.1 > [ 30.783028] ACPI: PCI Interrupt Link [LACI] enabled at IRQ 22 > [ 30.783033] ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LACI] -> GSI 22 (level, low) -> IRQ 22 > [ 30.783069] PCI: Setting latency timer of device 0000:00:06.0 to 64 > [ 30.867183] input: PS/2 Mouse as /class/input/input4 > [ 30.879995] input: AlpsPS/2 ALPS GlidePoint as /class/input/input5 > [ 30.886726] AC'97 0 analog subsections not ready > [ 31.288300] usb 2-2: new full speed USB device using ohci_hcd and address 2 > [ 31.446880] intel8x0_measure_ac97_clock: measured 50191 usecs > [ 31.446884] intel8x0: clocking to 47393 > [ 31.446930] PM: Adding info for No Bus:card0 > [ 31.447154] PM: Adding info for No Bus:pcmC0D2p > [ 31.447411] PM: Adding info for No Bus:pcmC0D1c > [ 31.447441] PM: Adding info for No Bus:pcmC0D0p > [ 31.447539] PM: Adding info for No Bus:pcmC0D0c > [ 31.447565] PM: Adding info for ac97:0-0:AD1981B > [ 31.447601] PM: Adding info for No Bus:controlC0 > [ 31.508940] usb 2-2: new device found, idVendor=049f, idProduct=0086 > [ 31.508945] usb 2-2: new device strings: Mfr=1, Product=2, SerialNumber=0 > [ 31.508948] usb 2-2: Product: Bluetooth by hp > [ 31.508950] usb 2-2: Manufacturer: ACTIONTEC > [ 31.508975] PM: Adding info for usb:2-2 > [ 31.509068] PM: Adding info for No Bus:usbdev2.2_ep00 > [ 31.509092] usb 2-2: configuration #1 chosen from 1 choice > [ 31.512951] PM: Adding info for usb:2-2:1.0 > [ 31.513032] PM: Adding info for No Bus:usbdev2.2_ep81 > [ 31.513073] PM: Adding info for No Bus:usbdev2.2_ep02 > [ 31.513107] PM: Adding info for No Bus:usbdev2.2_ep82 > [ 31.513141] PM: Adding info for usb:2-2:1.1 > [ 31.513182] PM: Adding info for No Bus:usbdev2.2_ep03 > [ 31.513221] PM: Adding info for No Bus:usbdev2.2_ep83 > [ 31.513249] PM: Adding info for usb:2-2:1.2 > [ 31.513329] PM: Adding info for No Bus:usbdev2.2 > [ 31.717722] hci_usb: Unknown symbol hci_suspend_dev > [ 31.717763] hci_usb: Unknown symbol hci_free_dev > [ 31.717983] hci_usb: Unknown symbol hci_resume_dev > [ 31.718035] hci_usb: Unknown symbol hci_alloc_dev > [ 31.718136] hci_usb: Unknown symbol hci_unregister_dev > [ 31.718243] hci_usb: Unknown symbol hci_register_dev > [ 31.781354] hci_usb: Unknown symbol hci_suspend_dev > [ 31.781394] hci_usb: Unknown symbol hci_free_dev > [ 31.781614] hci_usb: Unknown symbol hci_resume_dev > [ 31.781666] hci_usb: Unknown symbol hci_alloc_dev > [ 31.781767] hci_usb: Unknown symbol hci_unregister_dev > [ 31.781874] hci_usb: Unknown symbol hci_register_dev > [ 31.787382] hci_usb: Unknown symbol hci_suspend_dev > [ 31.787422] hci_usb: Unknown symbol hci_free_dev > [ 31.787642] hci_usb: Unknown symbol hci_resume_dev > [ 31.787694] hci_usb: Unknown symbol hci_alloc_dev > [ 31.787795] hci_usb: Unknown symbol hci_unregister_dev > [ 31.787901] hci_usb: Unknown symbol hci_register_dev > [ 33.005970] NET: Registered protocol family 10 > [ 34.776248] ReiserFS: sda1: found reiserfs format "3.6" with standard journal > [ 34.776310] ReiserFS: sda1: using ordered data mode > [ 34.776796] ReiserFS: sda1: journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 > [ 34.778707] ReiserFS: sda1: checking transaction log (sda1) > [ 34.810342] ReiserFS: sda1: Using r5 hash to sort names > [ 35.034524] Adding 2843496k swap on /dev/disk/by-uuid/fd35277a-8dc7-4afe-8257-fda61b757344. Priority:100 extents:1 across:2843496k > [ 42.116195] PM: Removing info for No Bus:vcs1 > [ 42.116521] PM: Removing info for No Bus:vcsa1 > [ 42.146081] PM: Adding info for No Bus:vcs1 > [ 42.146219] PM: Adding info for No Bus:vcsa1 > [ 1061.733883] su[2639]: segfault at 0000000000000008 rip 0000003103c098b2 rsp 00007fffb0fea590 error 4 > [ 1601.898867] PM: Removing info for No Bus:vcs1 > [ 1601.899098] PM: Removing info for No Bus:vcsa1 > [ 1601.905470] PM: Adding info for No Bus:vcs1 > [ 1601.905622] PM: Adding info for No Bus:vcsa1 > [ 1606.464599] PM: Adding info for No Bus:vcs2 > [ 1606.464845] PM: Adding info for No Bus:vcsa2 > [ 1606.466860] PM: Removing info for No Bus:vcs2 > [ 1606.466969] PM: Removing info for No Bus:vcsa2 > [ 1606.473400] PM: Adding info for No Bus:vcs3 > [ 1606.473561] PM: Adding info for No Bus:vcsa3 > [ 1606.475560] PM: Removing info for No Bus:vcs3 > [ 1606.475667] PM: Removing info for No Bus:vcsa3 > [ 1606.478811] PM: Adding info for No Bus:vcs4 > [ 1606.478973] PM: Adding info for No Bus:vcsa4 > [ 1606.479291] PM: Removing info for No Bus:vcs4 > [ 1606.479321] PM: Removing info for No Bus:vcsa4 > [ 1606.479397] PM: Adding info for No Bus:vcs5 > [ 1606.479420] PM: Adding info for No Bus:vcsa5 > [ 1606.479450] PM: Removing info for No Bus:vcs5 > [ 1606.479472] PM: Removing info for No Bus:vcsa5 > [ 1606.479549] PM: Adding info for No Bus:vcs6 > [ 1606.479572] PM: Adding info for No Bus:vcsa6 > [ 1606.479604] PM: Removing info for No Bus:vcs6 > [ 1606.479626] PM: Removing info for No Bus:vcsa6 > [ 1606.479694] PM: Adding info for No Bus:vcs7 > [ 1606.479716] PM: Adding info for No Bus:vcsa7 > [ 1606.479745] PM: Removing info for No Bus:vcs7 > [ 1606.479767] PM: Removing info for No Bus:vcsa7 > [ 1606.479835] PM: Adding info for No Bus:vcs8 > [ 1606.479859] PM: Adding info for No Bus:vcsa8 > [ 1606.479928] PM: Removing info for No Bus:vcs8 > [ 1606.479951] PM: Removing info for No Bus:vcsa8 > [ 1606.480018] PM: Adding info for No Bus:vcs9 > [ 1606.480041] PM: Adding info for No Bus:vcsa9 > [ 1606.480071] PM: Removing info for No Bus:vcs9 > [ 1606.480093] PM: Removing info for No Bus:vcsa9 > [ 1606.480160] PM: Adding info for No Bus:vcs10 > [ 1606.480183] PM: Adding info for No Bus:vcsa10 > [ 1606.480212] PM: Removing info for No Bus:vcs10 > [ 1606.480234] PM: Removing info for No Bus:vcsa10 > [ 1606.480302] PM: Adding info for No Bus:vcs11 > [ 1606.480325] PM: Adding info for No Bus:vcsa11 > [ 1606.480354] PM: Removing info for No Bus:vcs11 > [ 1606.480376] PM: Removing info for No Bus:vcsa11 > [ 1606.910477] PM: Adding info for No Bus:vcs2 > [ 1606.910514] PM: Adding info for No Bus:vcsa2 > [ 1606.917302] PM: Removing info for No Bus:vcs2 > [ 1606.917349] PM: Removing info for No Bus:vcsa2 > [ 1606.919043] PM: Adding info for No Bus:vcs3 > [ 1606.919071] PM: Adding info for No Bus:vcsa3 > [ 1606.927621] PM: Adding info for No Bus:vcs4 > [ 1606.927658] PM: Adding info for No Bus:vcsa4 > [ 1606.928858] PM: Removing info for No Bus:vcs3 > [ 1606.928892] PM: Removing info for No Bus:vcsa3 > [ 1606.935224] PM: Removing info for No Bus:vcs4 > [ 1606.935269] PM: Removing info for No Bus:vcsa4 > [ 1606.937061] PM: Adding info for No Bus:vcs5 > [ 1606.937089] PM: Adding info for No Bus:vcsa5 > [ 1606.947922] PM: Removing info for No Bus:vcs5 > [ 1606.947970] PM: Removing info for No Bus:vcsa5 > [ 1606.951331] PM: Adding info for No Bus:vcs6 > [ 1606.951366] PM: Adding info for No Bus:vcsa6 > [ 1606.958845] PM: Removing info for No Bus:vcs6 > [ 1606.958892] PM: Removing info for No Bus:vcsa6 > [ 1606.961602] PM: Adding info for No Bus:vcs7 > [ 1606.961636] PM: Adding info for No Bus:vcsa7 > [ 1606.972031] PM: Removing info for No Bus:vcs7 > [ 1606.972082] PM: Removing info for No Bus:vcsa7 > [ 1606.973903] PM: Adding info for No Bus:vcs8 > [ 1606.973933] PM: Adding info for No Bus:vcsa8 > [ 1606.982366] PM: Removing info for No Bus:vcs8 > [ 1606.982413] PM: Removing info for No Bus:vcsa8 > [ 1606.986078] PM: Adding info for No Bus:vcs9 > [ 1606.986113] PM: Adding info for No Bus:vcsa9 > [ 1607.000479] PM: Adding info for No Bus:vcs10 > [ 1607.000514] PM: Adding info for No Bus:vcsa10 > [ 1607.000750] PM: Removing info for No Bus:vcs9 > [ 1607.000782] PM: Removing info for No Bus:vcsa9 > [ 1607.025869] PM: Adding info for No Bus:vcs11 > [ 1607.025904] PM: Adding info for No Bus:vcsa11 > [ 1607.031896] PM: Removing info for No Bus:vcs11 > [ 1607.031941] PM: Removing info for No Bus:vcsa11 > [ 1607.043139] PM: Removing info for No Bus:vcs10 > [ 1607.043185] PM: Removing info for No Bus:vcsa10 > [ 1608.025861] eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1 > [ 1608.343434] PM: Removing info for No Bus:vcs1 > [ 1608.343599] PM: Removing info for No Bus:vcsa1 > [ 1608.348965] PM: Adding info for No Bus:vcs1 > [ 1608.349084] PM: Adding info for No Bus:vcsa1 > [ 1608.350359] PM: Removing info for No Bus:vcs1 > [ 1608.350447] PM: Removing info for No Bus:vcsa1 > [ 1608.350790] PM: Adding info for No Bus:vcs1 > [ 1608.350809] PM: Adding info for No Bus:vcsa1 > [ 1608.350872] PM: Removing info for No Bus:vcs1 > [ 1608.350891] PM: Removing info for No Bus:vcsa1 > [ 1608.350927] PM: Adding info for No Bus:vcs1 > [ 1608.350945] PM: Adding info for No Bus:vcsa1 > [ 1608.351049] PM: Removing info for No Bus:vcs1 > [ 1608.351068] PM: Removing info for No Bus:vcsa1 > [ 1608.353580] PM: Adding info for No Bus:vcs1 > [ 1608.353616] PM: Adding info for No Bus:vcsa1 > [ 1617.090942] eth0: no IPv6 routers present > [ 1617.123609] ata1.00: configured for UDMA/100 > [ 1617.123618] ata1: EH complete > [ 1617.140588] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB) > [ 1617.140902] sd 0:0:0:0: [sda] Write Protect is off > [ 1617.140905] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > [ 1617.149976] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > [ 1620.665587] process `named' is using obsolete setsockopt SO_BSDCOMPAT > [ 1620.742991] PM: Adding info for No Bus:vcs7 > [ 1620.744509] PM: Adding info for No Bus:vcsa7 > [ 1620.792323] PM: Removing info for No Bus:vcs7 > [ 1620.793678] PM: Removing info for No Bus:vcsa7 > [ 1621.266697] PM: Adding info for No Bus:vcs7 > [ 1621.268278] PM: Adding info for No Bus:vcsa7 > [ 1622.859425] PM: Adding info for No Bus:mixer > [ 1622.939896] PM: Adding info for No Bus:adsp > [ 1622.955211] PM: Adding info for No Bus:dsp > [ 1622.958759] PM: Adding info for No Bus:audio > [ 1624.113602] esound-esd[57956]: segfault at 000000000000ac44 rip 00000036a8c55b2b rsp 00007fff9723d8f0 error 4 > [ 1625.283022] PM: Adding info for No Bus:vcs2 > [ 1625.284318] PM: Adding info for No Bus:vcsa2 > [ 1625.285611] PM: Adding info for No Bus:vcs3 > [ 1625.286744] PM: Adding info for No Bus:vcsa3 > [ 1625.289092] PM: Adding info for No Bus:vcs4 > [ 1625.290316] PM: Adding info for No Bus:vcsa4 > [ 1625.292624] PM: Adding info for No Bus:vcs5 > [ 1625.293892] PM: Adding info for No Bus:vcsa5 > [ 1625.296159] PM: Adding info for No Bus:vcs6 > [ 1625.297535] PM: Adding info for No Bus:vcsa6 > [ 1651.450090] esd[58205]: segfault at 000000000000ac44 rip 00000036a8c55b2b rsp 00007fffebe7fcd0 error 4 > [ 1658.130375] ISO 9660 Extensions: Microsoft Joliet Level 3 > [ 1658.254107] ISO 9660 Extensions: RRIP_1991A > [ 1660.022177] [ACPI Debug] String: [0x12] "=====QUERY_25=====" > [ 1663.057766] > [ 1663.057769] ======================================================= > [ 1663.057775] [ INFO: possible circular locking dependency detected ] > [ 1663.057778] 2.6.21-rc4-mm1 #1 > [ 1663.057780] ------------------------------------------------------- > [ 1663.057783] evolution-data-/58416 is trying to acquire lock: > [ 1663.057785] (&mm->mmap_sem){----}, at: [<ffffffff80269eda>] do_page_fault+0x35a/0x800 > [ 1663.057795] > [ 1663.057796] but task is already holding lock: > [ 1663.057798] (&data->latch){----}, at: [<ffffffff8036a835>] read_unix_file+0x95/0x450 > [ 1663.057806] > [ 1663.057807] which lock already depends on the new lock. > [ 1663.057808] > [ 1663.057809] > [ 1663.057810] the existing dependency chain (in reverse order) is: > [ 1663.057812] > [ 1663.057813] -> #1 (&data->latch){----}: > [ 1663.057816] [<ffffffff802ae4c1>] __lock_acquire+0xd61/0x1010 > [ 1663.057823] [<ffffffff802ae7b9>] lock_acquire+0x49/0x70 > [ 1663.057829] [<ffffffff8036c721>] get_exclusive_access+0x11/0x20 > [ 1663.057836] [<ffffffff802a8c9f>] down_write+0x2f/0x40 > [ 1663.057843] [<ffffffff8036c721>] get_exclusive_access+0x11/0x20 > [ 1663.057849] [<ffffffff8036ac50>] mmap_unix_file+0x60/0x140 > [ 1663.057855] [<ffffffff8020dbf7>] do_mmap_pgoff+0x4f7/0x800 > [ 1663.057862] [<ffffffff802acfd6>] mark_held_locks+0x76/0xa0 > [ 1663.057868] [<ffffffff80267754>] _spin_unlock_irq+0x24/0x50 > [ 1663.057873] [<ffffffff8026775f>] _spin_unlock_irq+0x2f/0x50 > [ 1663.057879] [<ffffffff80234db3>] elf_map+0xa3/0x100 > [ 1663.057886] [<ffffffff80217de2>] load_elf_binary+0x902/0x1c30 > [ 1663.057893] [<ffffffff8028de20>] load_aout_binary+0x0/0x960 > [ 1663.057899] [<ffffffff802174e0>] load_elf_binary+0x0/0x1c30 > [ 1663.057905] [<ffffffff802406b3>] search_binary_handler+0xf3/0x2b0 > [ 1663.057912] [<ffffffff8024f322>] load_script+0x212/0x240 > [ 1663.057919] [<ffffffff802174e0>] load_elf_binary+0x0/0x1c30 > [ 1663.057925] [<ffffffff8024f110>] load_script+0x0/0x240 > [ 1663.057930] [<ffffffff802406b3>] search_binary_handler+0xf3/0x2b0 > [ 1663.057936] [<ffffffff8023f9f8>] do_execve+0x188/0x250 > [ 1663.057942] [<ffffffff802a1a10>] __call_usermodehelper+0x0/0x80 > [ 1663.057950] [<ffffffff80255034>] sys_execve+0x44/0x70 > [ 1663.057956] [<ffffffff80260044>] kernel_execve+0x64/0xd0 > [ 1663.057963] [<ffffffff802a1a10>] __call_usermodehelper+0x0/0x80 > [ 1663.057969] [<ffffffff802a1e0b>] ____call_usermodehelper+0x15b/0x170 > [ 1663.057975] [<ffffffff8025ffd8>] child_rip+0xa/0x12 > [ 1663.057981] [<ffffffff80267754>] _spin_unlock_irq+0x24/0x50 > [ 1663.057987] [<ffffffff8025f6c0>] restore_args+0x0/0x30 > [ 1663.057993] [<ffffffff802a1cb0>] ____call_usermodehelper+0x0/0x170 > [ 1663.057999] [<ffffffff8025ffce>] child_rip+0x0/0x12 > [ 1663.058004] [<ffffffffffffffff>] 0xffffffffffffffff > [ 1663.058042] > [ 1663.058043] -> #0 (&mm->mmap_sem){----}: > [ 1663.058045] [<ffffffff802ac62b>] print_circular_bug_header+0xdb/0x100 > [ 1663.058051] [<ffffffff802ae390>] __lock_acquire+0xc30/0x1010 > [ 1663.058057] [<ffffffff802ae7b9>] lock_acquire+0x49/0x70 > [ 1663.058062] [<ffffffff80269eda>] do_page_fault+0x35a/0x800 > [ 1663.058068] [<ffffffff802a8bc2>] down_read+0x32/0x40 > [ 1663.058074] [<ffffffff80269eda>] do_page_fault+0x35a/0x800 > [ 1663.058080] [<ffffffff80264207>] thread_return+0xef/0x148 > [ 1663.058088] [<ffffffff802676fd>] _spin_unlock_irqrestore+0x3d/0x70 > [ 1663.058094] [<ffffffff80267d2d>] error_exit+0x0/0x96 > [ 1663.058100] [<ffffffff8020ccbf>] file_read_actor+0x6f/0x190 > [ 1663.058105] [<ffffffff80240a6f>] __lock_page+0x5f/0x70 > [ 1663.058111] [<ffffffff8020bcd7>] do_generic_mapping_read+0x1f7/0x500 > [ 1663.058117] [<ffffffff8020cc50>] file_read_actor+0x0/0x190 > [ 1663.058123] [<ffffffff802162ca>] generic_file_aio_read+0x19a/0x1f0 > [ 1663.058129] [<ffffffff8020c91f>] do_sync_read+0xcf/0x120 > [ 1663.058135] [<ffffffff802a61f0>] autoremove_wake_function+0x0/0x30 > [ 1663.058141] [<ffffffff802675f9>] _spin_unlock+0x29/0x50 > [ 1663.058146] [<ffffffff8034f6fe>] reiser4_grab+0xae/0xd0 > [ 1663.058155] [<ffffffff8036a879>] read_unix_file+0xd9/0x450 > [ 1663.058161] [<ffffffff8020acea>] vfs_read+0xba/0x180 > [ 1663.058166] [<ffffffff80212b2e>] sys_pread64+0x5e/0x90 > [ 1663.058172] [<ffffffff8025f11e>] system_call+0x7e/0x83 > [ 1663.058178] [<ffffffffffffffff>] 0xffffffffffffffff > [ 1663.058184] > [ 1663.058185] other info that might help us debug this: > [ 1663.058186] > [ 1663.058188] 1 lock held by evolution-data-/58416: > [ 1663.058190] #0: (&data->latch){----}, at: [<ffffffff8036a835>] read_unix_file+0x95/0x450 > [ 1663.058196] > [ 1663.058196] stack backtrace: > [ 1663.058198] > [ 1663.058198] Call Trace: > [ 1663.058204] [<ffffffff802ac214>] print_circular_bug_tail+0x74/0x90 > [ 1663.058208] [<ffffffff802ac62b>] print_circular_bug_header+0xdb/0x100 > [ 1663.058211] [<ffffffff802ae390>] __lock_acquire+0xc30/0x1010 > [ 1663.058216] [<ffffffff802ae7b9>] lock_acquire+0x49/0x70 > [ 1663.058219] [<ffffffff80269eda>] do_page_fault+0x35a/0x800 > [ 1663.058223] [<ffffffff802a8bc2>] down_read+0x32/0x40 > [ 1663.058226] [<ffffffff80269eda>] do_page_fault+0x35a/0x800 > [ 1663.058232] [<ffffffff80264207>] thread_return+0xef/0x148 > [ 1663.058236] [<ffffffff802676fd>] _spin_unlock_irqrestore+0x3d/0x70 > [ 1663.058240] [<ffffffff80267d2d>] error_exit+0x0/0x96 > [ 1663.058245] [<ffffffff8020ccbf>] file_read_actor+0x6f/0x190 > [ 1663.058248] [<ffffffff80240a6f>] __lock_page+0x5f/0x70 > [ 1663.058253] [<ffffffff8020bcd7>] do_generic_mapping_read+0x1f7/0x500 > [ 1663.058256] [<ffffffff8020cc50>] file_read_actor+0x0/0x190 > [ 1663.058263] [<ffffffff802162ca>] generic_file_aio_read+0x19a/0x1f0 > [ 1663.058267] [<ffffffff8020c91f>] do_sync_read+0xcf/0x120 > [ 1663.058272] [<ffffffff802a61f0>] autoremove_wake_function+0x0/0x30 > [ 1663.058276] [<ffffffff802675f9>] _spin_unlock+0x29/0x50 > [ 1663.058280] [<ffffffff8034f6fe>] reiser4_grab+0xae/0xd0 > [ 1663.058284] [<ffffffff8036a879>] read_unix_file+0xd9/0x450 > [ 1663.058290] [<ffffffff8020acea>] vfs_read+0xba/0x180 > [ 1663.058294] [<ffffffff80212b2e>] sys_pread64+0x5e/0x90 > [ 1663.058298] [<ffffffff8025f11e>] system_call+0x7e/0x83 > [ 1663.058301] > [ 1714.279224] process `rndc' is using obsolete setsockopt SO_BSDCOMPAT > [ 1717.959422] eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1 > [ 1721.544091] process `named' is using obsolete setsockopt SO_BSDCOMPAT > [ 1725.344372] eth0: no IPv6 routers present > ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 6:36 ` 2.6.21-rc4-mm1 Andrew Morton @ 2007-03-21 9:52 ` Edward Shishkin 2007-03-21 14:12 ` [Bluez-devel] 2.6.21-rc4-mm1 Marcel Holtmann ` (3 subsequent siblings) 4 siblings, 0 replies; 146+ messages in thread From: Edward Shishkin @ 2007-03-21 9:52 UTC (permalink / raw) To: Zan Lynx Cc: Andrew Morton, linux-kernel, linux-wireless, bluez-devel, reiserfs-dev Andrew Morton wrote: >On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote: > > > >>On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote: >> >> >>>Temporarily at >>> >>> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ >>> >>>Will appear later at >>> >>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ >>> >>> >>First impressions: >>Several of the same bugs as rc3-mm*: >> * Freezes immediately if I touch the wlan0 device after loading >> the new Broadcom wireless driver. >> >> > >cc linux-wireless > > > >> * Freezes immediately if I allow Bluetooth to configure. >> >> > >cc bluez-devel > > > >> * All freezes simply stop, no BUG or panic happens, no watchdog, >> soft or NMI ever triggers. Thinking about it, I wonder if >> disabling EDAC_K8 would help here? Does it steal NMI? I'll try >> that later. >> >> > >Mabe that will be fixed by the just-uploaded >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/hot-fixes/tty-in-tiocsctty-when-we-steal-a-tty-hang-it-up-fix.patch > > > >> * I am using Reiser4 and after one of the above freezes and hard >> power cycle, files that were in use *read*only* are filled with >> zeros. >> did you enable compression announced not so long ago? anyway, it would be better to check your fs by fsck.reiser4 >> For example, while testing and experiencing the above >> freezes, I lost /etc/ld.so.preload >> and /lib/security/pam_limits.so. What the heck? >> >> > >cc reiserfs-dev > > ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [Bluez-devel] 2.6.21-rc4-mm1 2007-03-21 6:36 ` 2.6.21-rc4-mm1 Andrew Morton 2007-03-21 9:52 ` 2.6.21-rc4-mm1 Edward Shishkin @ 2007-03-21 14:12 ` Marcel Holtmann 2007-03-23 19:45 ` Zan Lynx 2007-03-21 16:13 ` 2.6.21-rc4-mm1 Larry Finger ` (2 subsequent siblings) 4 siblings, 1 reply; 146+ messages in thread From: Marcel Holtmann @ 2007-03-21 14:12 UTC (permalink / raw) To: BlueZ development; +Cc: Zan Lynx, reiserfs-dev, linux-wireless, linux-kernel Hi Andrew, > > * Freezes immediately if I allow Bluetooth to configure. > > cc bluez-devel is the -mm specific or does this also happens with 2.6.21-rc4? Regards Marcel ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [Bluez-devel] 2.6.21-rc4-mm1 2007-03-21 14:12 ` [Bluez-devel] 2.6.21-rc4-mm1 Marcel Holtmann @ 2007-03-23 19:45 ` Zan Lynx 0 siblings, 0 replies; 146+ messages in thread From: Zan Lynx @ 2007-03-23 19:45 UTC (permalink / raw) To: Marcel Holtmann; +Cc: BlueZ development, linux-kernel [-- Attachment #1: Type: text/plain, Size: 773 bytes --] On Wed, 2007-03-21 at 15:12 +0100, Marcel Holtmann wrote: > Hi Andrew, > > > > * Freezes immediately if I allow Bluetooth to configure. > > > > cc bluez-devel > > is the -mm specific or does this also happens with 2.6.21-rc4? Bluetooth works now, so it isn't entirely -mm's fault. I applied a posted patch for the Sonic Silicon Backplane. I also set all the older BCM43xx driver modules to N, and my freeze with wireless went away. On this laptop (a Compaq R3000) the Bluetooth and the wireless are controlled by the same front panel button, so I wonder if they are related in other ways as well. If I get a chance to play with it this weekend I will see if I can isolate the change that fixes/breaks it. -- Zan Lynx <zlynx@acm.org> [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 189 bytes --] ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 6:36 ` 2.6.21-rc4-mm1 Andrew Morton 2007-03-21 9:52 ` 2.6.21-rc4-mm1 Edward Shishkin 2007-03-21 14:12 ` [Bluez-devel] 2.6.21-rc4-mm1 Marcel Holtmann @ 2007-03-21 16:13 ` Larry Finger 2007-03-23 19:40 ` 2.6.21-rc4-mm1 Zan Lynx 2007-03-21 18:14 ` 2.6.21-rc4-mm1 Larry Finger 2007-03-21 18:49 ` 2.6.21-rc4-mm1 - problem with cpuidle routine Larry Finger 4 siblings, 1 reply; 146+ messages in thread From: Larry Finger @ 2007-03-21 16:13 UTC (permalink / raw) To: Zan Lynx Cc: Andrew Morton, linux-kernel, linux-wireless, bluez-devel, reiserfs-dev Andrew Morton wrote: > On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote: > >> On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote: >>> Temporarily at >>> >>> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ >>> >>> Will appear later at >>> >>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ >> First impressions: >> Several of the same bugs as rc3-mm*: >> * Freezes immediately if I touch the wlan0 device after loading >> the new Broadcom wireless driver. --snip-- >> 02:02.0 Network controller: Broadcom Corporation BCM4303 802.11b Wireless LAN Controller (rev 02) I'm a little confused. The bcm43xx-mac80211 driver does not handle 802.11b devices, and the bcm43xx-softmac driver should not freeze. Which one was configured here? Larry ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 16:13 ` 2.6.21-rc4-mm1 Larry Finger @ 2007-03-23 19:40 ` Zan Lynx 2007-03-24 1:49 ` 2.6.21-rc4-mm1 Larry Finger 0 siblings, 1 reply; 146+ messages in thread From: Zan Lynx @ 2007-03-23 19:40 UTC (permalink / raw) To: Larry Finger Cc: Andrew Morton, linux-kernel, linux-wireless, bluez-devel, reiserfs-dev [-- Attachment #1: Type: text/plain, Size: 1222 bytes --] On Wed, 2007-03-21 at 11:13 -0500, Larry Finger wrote: > Andrew Morton wrote: > > On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote: > >> First impressions: > >> Several of the same bugs as rc3-mm*: > >> * Freezes immediately if I touch the wlan0 device after loading > >> the new Broadcom wireless driver. > > --snip-- > > >> 02:02.0 Network controller: Broadcom Corporation BCM4303 802.11b Wireless LAN Controller (rev 02) > > I'm a little confused. The bcm43xx-mac80211 driver does not handle 802.11b devices, and the > bcm43xx-softmac driver should not freeze. Which one was configured here? It may have partly been a problem of having half of softmac and half devicescape. I'm not entirely sure what udev did. I tried a patch for the Sonic Silicon that was posted and I turned off all the configuration for the softmac driver. It isn't crashing right now but 802.11 isn't working either. I may get a chance this weekend to try some things with it, and some different firmware sets. If the new bcm43xx drivers do not support 802.11b at all and never will, I missed the documentation. Someone should add that to Kconfig. -- Zan Lynx <zlynx@acm.org> [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 189 bytes --] ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-23 19:40 ` 2.6.21-rc4-mm1 Zan Lynx @ 2007-03-24 1:49 ` Larry Finger 0 siblings, 0 replies; 146+ messages in thread From: Larry Finger @ 2007-03-24 1:49 UTC (permalink / raw) To: Zan Lynx Cc: Andrew Morton, linux-kernel, linux-wireless, bluez-devel, reiserfs-dev Zan Lynx wrote: > > It may have partly been a problem of having half of softmac and half > devicescape. I'm not entirely sure what udev did. > > I tried a patch for the Sonic Silicon that was posted and I turned off > all the configuration for the softmac driver. > > It isn't crashing right now but 802.11 isn't working either. I may get > a chance this weekend to try some things with it, and some different > firmware sets. That is my experience with a 4311. It does the open authentication and associates, but the WPA authentication step times out and I never get connected. > If the new bcm43xx drivers do not support 802.11b at all and never will, > I missed the documentation. Someone should add that to Kconfig. Yes it should. Until bcm43xx-mac80211 got picked up by -mm, it was only used within the bcm43xx group and that was understood in that circle. It has just been decided that the softmac version of the driver will be renamed bcm4301 and be converted to use mac80211. When bcm43xx-mac80211 goes mainline, bcm4301 will be restricted to 802.11b-only cards. That is the way we will support the older cards. The reason for a separate driver is that the bcm4301 and bcm4303 do not have sufficient memory to run the latest firmware (V4), and bcm43xx-mac80211 only uses that firmware; whereas bcm4301 will use the older V3 firmware. Larry ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 6:36 ` 2.6.21-rc4-mm1 Andrew Morton ` (2 preceding siblings ...) 2007-03-21 16:13 ` 2.6.21-rc4-mm1 Larry Finger @ 2007-03-21 18:14 ` Larry Finger 2007-03-21 18:34 ` 2.6.21-rc4-mm1 Michael Buesch 2007-03-21 18:59 ` 2.6.21-rc4-mm1 John W. Linville 2007-03-21 18:49 ` 2.6.21-rc4-mm1 - problem with cpuidle routine Larry Finger 4 siblings, 2 replies; 146+ messages in thread From: Larry Finger @ 2007-03-21 18:14 UTC (permalink / raw) To: Andrew Morton Cc: Zan Lynx, linux-kernel, linux-wireless, Michael Buesch, bcm43xx devel [-- Attachment #1: Type: text/plain, Size: 1748 bytes --] Andrew Morton wrote: > On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote: > >> On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote: >>> Temporarily at >>> >>> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ >>> >>> Will appear later at >>> >>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ >> First impressions: >> Several of the same bugs as rc3-mm*: >> * Freezes immediately if I touch the wlan0 device after loading >> the new Broadcom wireless driver. The version of the ssb driver in 2.6.21-rc4-mm1 has a bug that causes a kernel oops if the bcm43xx chip contains a USB (dangling) core. This bug has been fixed in Michael Buesch's tree, but apparently not yet in Linville's wireless-dev tree. The patch is as follows: commit 08531ff130bcc8181d9294a66e25010f48eefb97 Author: Michael Buesch <mb@bu3sch.de> Date: Wed Mar 7 23:01:08 2007 +0100 ssb: Don't freeze unregistered devices. Signed-off-by: Michael Buesch <mb@bu3sch.de> diff --git a/drivers/ssb/core.c b/drivers/ssb/core.c index 2facada..c956edf 100644 --- a/drivers/ssb/core.c +++ b/drivers/ssb/core.c @@ -163,6 +163,8 @@ int ssb_devices_freeze(struct ssb_bus *bus) dev = &(bus->devices[i]); if (!dev->dev->driver) continue; + if (!device_is_registered(dev->dev)) + continue; drv = drv_to_ssb_drv(dev->dev->driver); if (drv && drv->suspend) { err = drv->suspend(dev, state); @@ -185,6 +187,8 @@ int ssb_devices_thaw(struct ssb_bus *bus) dev = &(bus->devices[i]); if (!dev->dev->driver) continue; + if (!device_is_registered(dev->dev)) + continue; drv = drv_to_ssb_drv(dev->dev->driver); if (drv && drv->resume) { err = drv->resume(dev); Larry [-- Attachment #2: usb_freeze --] [-- Type: text/plain, Size: 939 bytes --] commit 08531ff130bcc8181d9294a66e25010f48eefb97 Author: Michael Buesch <mb@bu3sch.de> Date: Wed Mar 7 23:01:08 2007 +0100 ssb: Don't freeze unregistered devices. Signed-off-by: Michael Buesch <mb@bu3sch.de> diff --git a/drivers/ssb/main.c b/drivers/ssb/main.c index 2facada..c956edf 100644 --- a/drivers/ssb/main.c +++ b/drivers/ssb/main.c @@ -163,6 +163,8 @@ int ssb_devices_freeze(struct ssb_bus *bus) dev = &(bus->devices[i]); if (!dev->dev->driver) continue; + if (!device_is_registered(dev->dev)) + continue; drv = drv_to_ssb_drv(dev->dev->driver); if (drv && drv->suspend) { err = drv->suspend(dev, state); @@ -185,6 +187,8 @@ int ssb_devices_thaw(struct ssb_bus *bus) dev = &(bus->devices[i]); if (!dev->dev->driver) continue; + if (!device_is_registered(dev->dev)) + continue; drv = drv_to_ssb_drv(dev->dev->driver); if (drv && drv->resume) { err = drv->resume(dev); ^ permalink raw reply related [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 18:14 ` 2.6.21-rc4-mm1 Larry Finger @ 2007-03-21 18:34 ` Michael Buesch 2007-03-21 19:00 ` 2.6.21-rc4-mm1 John W. Linville 2007-03-21 18:59 ` 2.6.21-rc4-mm1 John W. Linville 1 sibling, 1 reply; 146+ messages in thread From: Michael Buesch @ 2007-03-21 18:34 UTC (permalink / raw) To: Larry Finger Cc: Andrew Morton, Zan Lynx, linux-kernel, linux-wireless, bcm43xx devel, John Linville On Wednesday 21 March 2007 19:14, Larry Finger wrote: > Andrew Morton wrote: > > On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote: > > > >> On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote: > >>> Temporarily at > >>> > >>> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > >>> > >>> Will appear later at > >>> > >>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > >> First impressions: > >> Several of the same bugs as rc3-mm*: > >> * Freezes immediately if I touch the wlan0 device after loading > >> the new Broadcom wireless driver. > > The version of the ssb driver in 2.6.21-rc4-mm1 has a bug that causes a kernel oops if the bcm43xx > chip contains a USB (dangling) core. This bug has been fixed in Michael Buesch's tree, but > apparently not yet in Linville's wireless-dev tree. The patch is as follows: > > commit 08531ff130bcc8181d9294a66e25010f48eefb97 > Author: Michael Buesch <mb@bu3sch.de> > Date: Wed Mar 7 23:01:08 2007 +0100 > > ssb: Don't freeze unregistered devices. No, that's a different fix for suspend. This is the fix: http://bu3sch.de/gitweb?p=wireless-dev.git;a=commitdiff;h=b87f743f3643ea162892dce0bbc91e6f026a49bf Pull request was sent to John. -- Greetings Michael. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 18:34 ` 2.6.21-rc4-mm1 Michael Buesch @ 2007-03-21 19:00 ` John W. Linville 0 siblings, 0 replies; 146+ messages in thread From: John W. Linville @ 2007-03-21 19:00 UTC (permalink / raw) To: Michael Buesch Cc: Larry Finger, Andrew Morton, Zan Lynx, linux-kernel, linux-wireless, bcm43xx devel On Wed, Mar 21, 2007 at 07:34:28PM +0100, Michael Buesch wrote: > On Wednesday 21 March 2007 19:14, Larry Finger wrote: > > Andrew Morton wrote: > > > On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote: > > > > > >> On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote: > > >>> Temporarily at > > >>> > > >>> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > >>> > > >>> Will appear later at > > >>> > > >>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > > >> First impressions: > > >> Several of the same bugs as rc3-mm*: > > >> * Freezes immediately if I touch the wlan0 device after loading > > >> the new Broadcom wireless driver. > > > > The version of the ssb driver in 2.6.21-rc4-mm1 has a bug that causes a kernel oops if the bcm43xx > > chip contains a USB (dangling) core. This bug has been fixed in Michael Buesch's tree, but > > apparently not yet in Linville's wireless-dev tree. The patch is as follows: > > > > commit 08531ff130bcc8181d9294a66e25010f48eefb97 > > Author: Michael Buesch <mb@bu3sch.de> > > Date: Wed Mar 7 23:01:08 2007 +0100 > > > > ssb: Don't freeze unregistered devices. > > No, that's a different fix for suspend. > > This is the fix: > http://bu3sch.de/gitweb?p=wireless-dev.git;a=commitdiff;h=b87f743f3643ea162892dce0bbc91e6f026a49bf > > Pull request was sent to John. That's "ssb-ohci: Completely disable the driver on non-embedded systems", also in wireless-dev as of yesterday. Thanks, John -- John W. Linville linville@tuxdriver.com ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 18:14 ` 2.6.21-rc4-mm1 Larry Finger 2007-03-21 18:34 ` 2.6.21-rc4-mm1 Michael Buesch @ 2007-03-21 18:59 ` John W. Linville 2007-03-21 20:22 ` 2.6.21-rc4-mm1 Matt Mackall 1 sibling, 1 reply; 146+ messages in thread From: John W. Linville @ 2007-03-21 18:59 UTC (permalink / raw) To: Larry Finger Cc: Andrew Morton, Zan Lynx, linux-kernel, linux-wireless, Michael Buesch, bcm43xx devel On Wed, Mar 21, 2007 at 01:14:55PM -0500, Larry Finger wrote: > Andrew Morton wrote: > > On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote: > > > >> On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote: > >>> Temporarily at > >>> > >>> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > >>> > >>> Will appear later at > >>> > >>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > >> First impressions: > >> Several of the same bugs as rc3-mm*: > >> * Freezes immediately if I touch the wlan0 device after loading > >> the new Broadcom wireless driver. > > The version of the ssb driver in 2.6.21-rc4-mm1 has a bug that causes a kernel oops if the bcm43xx > chip contains a USB (dangling) core. This bug has been fixed in Michael Buesch's tree, but > apparently not yet in Linville's wireless-dev tree. The patch is as follows: FWIW, that patch is in my tree as of yesterday. Presumably it should be in the next -mm. John -- John W. Linville linville@tuxdriver.com ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 18:59 ` 2.6.21-rc4-mm1 John W. Linville @ 2007-03-21 20:22 ` Matt Mackall 2007-03-21 20:48 ` 2.6.21-rc4-mm1 Larry Finger ` (3 more replies) 0 siblings, 4 replies; 146+ messages in thread From: Matt Mackall @ 2007-03-21 20:22 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel, linux-wireless With the latest -mm, I'm now getting this: Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected value (0) Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2 Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2 Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network device -- Mathematics is the supreme nostalgia of our time. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 20:22 ` 2.6.21-rc4-mm1 Matt Mackall @ 2007-03-21 20:48 ` Larry Finger 2007-03-21 21:03 ` 2.6.21-rc4-mm1 Larry Finger ` (2 subsequent siblings) 3 siblings, 0 replies; 146+ messages in thread From: Larry Finger @ 2007-03-21 20:48 UTC (permalink / raw) To: Matt Mackall; +Cc: Andrew Morton, linux-kernel, linux-wireless Matt Mackall wrote: > With the latest -mm, I'm now getting this: > > Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless > 2200BG Network Connection > Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected > value (0) > Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw > request_firmware failed: > Reason -2 > Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2 > Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network > device > I am seeing similar messages trying to load bcm43xx firmware with 2.6.21-rc4-mm1. Larry ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 20:22 ` 2.6.21-rc4-mm1 Matt Mackall 2007-03-21 20:48 ` 2.6.21-rc4-mm1 Larry Finger @ 2007-03-21 21:03 ` Larry Finger 2007-03-21 21:39 ` 2.6.21-rc4-mm1 Randy Dunlap 2007-03-21 21:45 ` 2.6.21-rc4-mm1 Andrew Morton 2007-03-22 7:39 ` 2.6.21-rc4-mm1 Andrew Morton 3 siblings, 1 reply; 146+ messages in thread From: Larry Finger @ 2007-03-21 21:03 UTC (permalink / raw) To: Matt Mackall; +Cc: Andrew Morton, linux-kernel, linux-wireless Matt Mackall wrote: > With the latest -mm, I'm now getting this: > > Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless > 2200BG Network Connection > Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected > value (0) > Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw > request_firmware failed: > Reason -2 > Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2 > Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network > device The problem for me is a general protection fault. kernel: general protection fault: 0000 [1] SMP kernel: last sysfs file: class/firmware/0000:01:00.0/loading kernel: CPU 0 kernel: Modules linked in: af_packet snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device cpufreq_conservative cpufreq_ondemand cpufreq_userspace cpufreq_powersave powernow_k8 freq_table button battery ac nls_utf8 ntfs loop nfsd exportfs nfs lockd nfs_acl sunrpc sr_mod usb_storage libusual snd_hda_intel snd_hda_codec sdhci snd_pcm snd_timer ohci1394 mmc_core snd ieee1394 forcedeth soundcore snd_page_alloc ohci_hcd ide_cd ehci_hcd cdrom usbcore i2c_nforce2 bcm43xx firmware_class ieee80211softmac ieee80211 ieee80211_crypt ext3 mbcache jbd sg edd fan sata_nv libata amd74xx thermal processor sd_mod scsi_mod ide_disk ide_core kernel: Pid: 4026, comm: cat Not tainted 2.6.21-rc4-mm1-mm1 #6 kernel: RIP: 0010:[<ffffffff80251f99>] [<ffffffff80251f99>] module_put+0x1f/0x35 kernel: RSP: 0018:ffff810006f85ea8 EFLAGS: 00010256 kernel: RAX: 6b6b6b6b6b6b6dab RBX: ffff810005dbe1f0 RCX: ffffffff803f6160 kernel: RDX: 0000000000000001 RSI: ffffffff802ec3dc RDI: 6b6b6b6b6b6b6b6b kernel: RBP: ffff810006f85ea8 R08: 0000000000000000 R09: ffff810005918888 kernel: R10: 0000000000000000 R11: ffffffff8811b020 R12: ffff81000850d000 kernel: R13: ffff810004ec25a8 R14: ffff810006f38c18 R15: ffff8100034017c0 kernel: FS: 00002b621c2f86f0(0000) GS:ffffffff8051e000(0000) knlGS:0000000000000000 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b kernel: CR2: 00002b621c01d3c0 CR3: 0000000008154000 CR4: 00000000000006e0 kernel: Process cat (pid: 4026, threadinfo ffff810006f84000, task ffff810005dd3140) kernel: Stack: ffff810006f85ec8 ffffffff802cf4ba 0000000000000008 ffff810006f38c18 kernel: ffff810006f85f08 ffffffff80290a44 ffff81000853bde0 ffff810004ec25a8 kernel: ffff8100035d1cb0 0000000000000000 ffff810004ec25a8 00007fff8ed0f6d0 kernel: Call Trace: kernel: [<ffffffff802cf4ba>] release+0x3a/0x49 kernel: [<ffffffff80290a44>] __fput+0xca/0x180 kernel: [<ffffffff80290b0e>] fput+0x14/0x16 kernel: [<ffffffff8028e1aa>] filp_close+0x66/0x71 kernel: [<ffffffff8028f3c2>] sys_close+0x98/0xdd kernel: [<ffffffff80209f6e>] system_call+0x7e/0x83 kernel: kernel: kernel: Code: 48 ff 08 83 3f 02 75 0c 48 8b bf 50 22 00 00 e8 08 9d fd ff kernel: RIP [<ffffffff80251f99>] module_put+0x1f/0x35 kernel: RSP <ffff810006f85ea8> Larry ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 21:03 ` 2.6.21-rc4-mm1 Larry Finger @ 2007-03-21 21:39 ` Randy Dunlap 0 siblings, 0 replies; 146+ messages in thread From: Randy Dunlap @ 2007-03-21 21:39 UTC (permalink / raw) To: Larry Finger; +Cc: Matt Mackall, Andrew Morton, linux-kernel, linux-wireless On Wed, 21 Mar 2007 16:03:24 -0500 Larry Finger wrote: > Matt Mackall wrote: > > With the latest -mm, I'm now getting this: > > > > Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless > > 2200BG Network Connection > > Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected > > value (0) > > Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw > > request_firmware failed: > > Reason -2 > > Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2 > > Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network > > device > > The problem for me is a general protection fault. > > kernel: general protection fault: 0000 [1] SMP > kernel: last sysfs file: class/firmware/0000:01:00.0/loading > kernel: CPU 0 > kernel: Modules linked in: af_packet snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device > cpufreq_conservative cpufreq_ondemand cpufreq_userspace cpufreq_powersave powernow_k8 freq_table > button battery ac nls_utf8 ntfs loop nfsd exportfs nfs lockd nfs_acl sunrpc sr_mod usb_storage > libusual snd_hda_intel snd_hda_codec sdhci snd_pcm snd_timer ohci1394 mmc_core snd ieee1394 > forcedeth soundcore snd_page_alloc ohci_hcd ide_cd ehci_hcd cdrom usbcore i2c_nforce2 bcm43xx > firmware_class ieee80211softmac ieee80211 ieee80211_crypt ext3 mbcache jbd sg edd fan sata_nv libata > amd74xx thermal processor sd_mod scsi_mod ide_disk ide_core > kernel: Pid: 4026, comm: cat Not tainted 2.6.21-rc4-mm1-mm1 #6 > kernel: RIP: 0010:[<ffffffff80251f99>] [<ffffffff80251f99>] module_put+0x1f/0x35 > kernel: RSP: 0018:ffff810006f85ea8 EFLAGS: 00010256 > kernel: RAX: 6b6b6b6b6b6b6dab RBX: ffff810005dbe1f0 RCX: ffffffff803f6160 > kernel: RDX: 0000000000000001 RSI: ffffffff802ec3dc RDI: 6b6b6b6b6b6b6b6b > kernel: RBP: ffff810006f85ea8 R08: 0000000000000000 R09: ffff810005918888 > kernel: R10: 0000000000000000 R11: ffffffff8811b020 R12: ffff81000850d000 > kernel: R13: ffff810004ec25a8 R14: ffff810006f38c18 R15: ffff8100034017c0 > kernel: FS: 00002b621c2f86f0(0000) GS:ffffffff8051e000(0000) knlGS:0000000000000000 > kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b > kernel: CR2: 00002b621c01d3c0 CR3: 0000000008154000 CR4: 00000000000006e0 > kernel: Process cat (pid: 4026, threadinfo ffff810006f84000, task ffff810005dd3140) > kernel: Stack: ffff810006f85ec8 ffffffff802cf4ba 0000000000000008 ffff810006f38c18 > kernel: ffff810006f85f08 ffffffff80290a44 ffff81000853bde0 ffff810004ec25a8 > kernel: ffff8100035d1cb0 0000000000000000 ffff810004ec25a8 00007fff8ed0f6d0 > kernel: Call Trace: > kernel: [<ffffffff802cf4ba>] release+0x3a/0x49 > kernel: [<ffffffff80290a44>] __fput+0xca/0x180 > kernel: [<ffffffff80290b0e>] fput+0x14/0x16 > kernel: [<ffffffff8028e1aa>] filp_close+0x66/0x71 > kernel: [<ffffffff8028f3c2>] sys_close+0x98/0xdd > kernel: [<ffffffff80209f6e>] system_call+0x7e/0x83 > kernel: > kernel: > kernel: Code: 48 ff 08 83 3f 02 75 0c 48 8b bf 50 22 00 00 e8 08 9d fd ff > kernel: RIP [<ffffffff80251f99>] module_put+0x1f/0x35 > kernel: RSP <ffff810006f85ea8> which is 'decq' instruction in the local_dec() below: void module_put(struct module *module) { if (module) { unsigned int cpu = get_cpu(); local_dec(&module->ref[cpu].count); /* Maybe they're waiting for us to drop reference? */ if (unlikely(!module_is_live(module))) wake_up_process(module->waiter); put_cpu(); } } 0000000000000f4e <module_put>: module_put(): f4e: 55 push %rbp f4f: 48 85 ff test %rdi,%rdi f52: 48 89 e5 mov %rsp,%rbp f55: 74 2a je f81 <module_put+0x33> f57: 65 8b 04 25 24 00 00 mov %gs:0x24,%eax f5e: 00 f5f: 89 c0 mov %eax,%eax f61: 48 c1 e0 07 shl $0x7,%rax f65: 48 8d 84 38 00 02 00 lea 0x200(%rax,%rdi,1),%rax f6c: 00 * f6d: 48 ff 08 decq (%rax) f70: 83 3f 02 cmpl $0x2,(%rdi) f73: 75 0c jne f81 <module_put+0x33> f75: 48 8b bf 10 06 00 00 mov 0x610(%rdi),%rdi f7c: e8 00 00 00 00 callq f81 <module_put+0x33> f7d: R_X86_64_PC32 wake_up_process+0xfffffffffffffffc f81: c9 leaveq f82: c3 retq --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 20:22 ` 2.6.21-rc4-mm1 Matt Mackall 2007-03-21 20:48 ` 2.6.21-rc4-mm1 Larry Finger 2007-03-21 21:03 ` 2.6.21-rc4-mm1 Larry Finger @ 2007-03-21 21:45 ` Andrew Morton 2007-03-22 7:39 ` 2.6.21-rc4-mm1 Andrew Morton 3 siblings, 0 replies; 146+ messages in thread From: Andrew Morton @ 2007-03-21 21:45 UTC (permalink / raw) To: Matt Mackall; +Cc: linux-kernel, linux-wireless On Wed, 21 Mar 2007 15:22:25 -0500 Matt Mackall <mpm@selenic.com> wrote: > With the latest -mm, I'm now getting this: > > Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless > 2200BG Network Connection > Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected > value (0) > Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw > request_firmware failed: > Reason -2 > Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2 > Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network > device > Yes, someone seems to have thoroughly bollixed firmware loading. I was able to make it pretend to work for my ipw2200, but that obviously wasn't sufficient. I plan to do a bisection this evening, find the dud patch. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-21 20:22 ` 2.6.21-rc4-mm1 Matt Mackall ` (2 preceding siblings ...) 2007-03-21 21:45 ` 2.6.21-rc4-mm1 Andrew Morton @ 2007-03-22 7:39 ` Andrew Morton 2007-03-22 11:35 ` 2.6.21-rc4-mm1 Cornelia Huck 2007-03-24 22:32 ` 2.6.21-rc4-mm1 Matt Mackall 3 siblings, 2 replies; 146+ messages in thread From: Andrew Morton @ 2007-03-22 7:39 UTC (permalink / raw) To: Matt Mackall; +Cc: linux-kernel, linux-wireless, Monakhov Dmitriy On Wed, 21 Mar 2007 15:22:25 -0500 Matt Mackall <mpm@selenic.com> wrote: > With the latest -mm, I'm now getting this: > > Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless > 2200BG Network Connection > Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected > value (0) > Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw > request_firmware failed: > Reason -2 > Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2 > Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network > device The firmware loading bug is caused by driver-core-handles-kobject_uevent-failure-while-device_add.patch I've uploaded a revert patch to ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/hot-fixes/ ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 7:39 ` 2.6.21-rc4-mm1 Andrew Morton @ 2007-03-22 11:35 ` Cornelia Huck [not found] ` <4602752A.5050109@lwfinger.net> 2007-03-24 22:32 ` 2.6.21-rc4-mm1 Matt Mackall 1 sibling, 1 reply; 146+ messages in thread From: Cornelia Huck @ 2007-03-22 11:35 UTC (permalink / raw) To: Andrew Morton Cc: Matt Mackall, linux-kernel, linux-wireless, Monakhov Dmitriy On Wed, 21 Mar 2007 23:39:17 -0800, Andrew Morton <akpm@linux-foundation.org> wrote: > On Wed, 21 Mar 2007 15:22:25 -0500 Matt Mackall <mpm@selenic.com> wrote: > > > With the latest -mm, I'm now getting this: > > > > Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless > > 2200BG Network Connection > > Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected > > value (0) > > Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw > > request_firmware failed: > > Reason -2 > > Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2 > > Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network > > device > > The firmware loading bug is caused by > driver-core-handles-kobject_uevent-failure-while-device_add.patch Hm, this patch looks sane. It might be a good idea to enable CONFIG_DEBUG_KOBJECT and find out why kobject_uevent() actually fails in this case... ^ permalink raw reply [flat|nested] 146+ messages in thread
[parent not found: <4602752A.5050109@lwfinger.net>]
* Re: 2.6.21-rc4-mm1 [not found] ` <4602752A.5050109@lwfinger.net> @ 2007-03-22 17:10 ` Cornelia Huck 2007-03-22 18:55 ` 2.6.21-rc4-mm1 Larry Finger 0 siblings, 1 reply; 146+ messages in thread From: Cornelia Huck @ 2007-03-22 17:10 UTC (permalink / raw) To: Larry Finger Cc: Andrew Morton, Matt Mackall, linux-kernel, linux-wireless, Monakhov Dmitriy On Thu, 22 Mar 2007 07:23:06 -0500, Larry Finger <larry.finger@lwfinger.net> wrote: > Cornelia Huck wrote: > > On Wed, 21 Mar 2007 23:39:17 -0800, > > Andrew Morton <akpm@linux-foundation.org> wrote: > > > >> On Wed, 21 Mar 2007 15:22:25 -0500 Matt Mackall <mpm@selenic.com> wrote: > >> > >>> With the latest -mm, I'm now getting this: > >>> > >>> Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless > >>> 2200BG Network Connection > >>> Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected > >>> value (0) > >>> Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw > >>> request_firmware failed: > >>> Reason -2 > >>> Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2 > >>> Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network > >>> device > >> The firmware loading bug is caused by > >> driver-core-handles-kobject_uevent-failure-while-device_add.patch > > > > Hm, this patch looks sane. It might be a good idea to enable > > CONFIG_DEBUG_KOBJECT and find out why kobject_uevent() actually fails > > in this case... > > Attached is the appropriate portion of /var/log/messages with Kobject debugging enabled. > Mar 22 07:01:42 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices > Mar 22 07:01:42 larrylap2 kernel: kobject_uevent_env > Mar 22 07:01:42 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' > Mar 22 07:01:42 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' > Mar 22 07:01:42 larrylap2 kernel: kobject_uevent_env > Mar 22 07:01:42 larrylap2 ntpd[3434]: frequency initialized -31.513 PPM from /var/lib/ntp/drift/ntp.drift > Mar 22 07:01:43 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' > Mar 22 07:01:43 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' > Mar 22 07:01:43 larrylap2 kernel: firmware_loading_store: unexpected value (0) > Mar 22 07:01:43 larrylap2 kernel: kobject_uevent_env > Mar 22 07:01:43 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' > Mar 22 07:01:43 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' > Mar 22 07:01:43 larrylap2 kernel: kobject 0000:01:00.0: cleaning up (Repeating several times) This would indicate that dev_uevent had been called. But how could kobject_uevent then return an error without moaning about an uevent() error code? Maybe the following debug patch could shed some light on this (all moaning is prefixed with kobject_uevent_env, so it should be easy to spot)... --- lib/kobject_uevent.c | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) --- linux-2.6.orig/lib/kobject_uevent.c +++ linux-2.6/lib/kobject_uevent.c @@ -85,11 +85,11 @@ int kobject_uevent_env(struct kobject *k int retval = 0; int j; - pr_debug("%s\n", __FUNCTION__); + pr_debug("%s: %s\n", __FUNCTION__, kobject_name(kobj)); action_string = action_to_string(action); if (!action_string) { - pr_debug("kobject attempted to send uevent without action_string!\n"); + pr_debug("%s: kobject attempted to send uevent without action_string!\n", __FUNCTION__); return -EINVAL; } @@ -101,7 +101,7 @@ int kobject_uevent_env(struct kobject *k } while (!top_kobj->kset && top_kobj->parent); } if (!top_kobj->kset) { - pr_debug("kobject attempted to send uevent without kset!\n"); + pr_debug("%s: kobject attempted to send uevent without kset!\n", __FUNCTION__); return -EINVAL; } @@ -111,7 +111,7 @@ int kobject_uevent_env(struct kobject *k /* skip the event, if the filter returns zero. */ if (uevent_ops && uevent_ops->filter) if (!uevent_ops->filter(kset, kobj)) { - pr_debug("kobject filter function caused the event to drop!\n"); + pr_debug("%s: kobject filter function caused the event to drop!\n", __FUNCTION__); return 0; } @@ -121,18 +121,20 @@ int kobject_uevent_env(struct kobject *k else subsystem = kobject_name(&kset->kobj); if (!subsystem) { - pr_debug("unset subsytem caused the event to drop!\n"); + pr_debug("%s: unset subsytem caused the event to drop!\n", __FUNCTION__); return 0; } /* environment index */ envp = kzalloc(NUM_ENVP * sizeof (char *), GFP_KERNEL); - if (!envp) + if (!envp) { + pr_debug("%s: couldn't alloc envp\n", __FUNCTION__); return -ENOMEM; - + } /* environment values */ buffer = kmalloc(BUFFER_SIZE, GFP_KERNEL); if (!buffer) { + pr_debug("%s: couldn't alloc buffer\n", __FUNCTION__); retval = -ENOMEM; goto exit; } @@ -140,6 +142,7 @@ int kobject_uevent_env(struct kobject *k /* complete object path */ devpath = kobject_get_path(kobj, GFP_KERNEL); if (!devpath) { + pr_debug("%s: couldn't get kobject path\n", __FUNCTION__); retval = -ENOENT; goto exit; } @@ -221,6 +224,7 @@ exit: kfree(devpath); kfree(buffer); kfree(envp); + pr_debug("%s: returning %d\n", __FUNCTION__, retval); return retval; } ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 17:10 ` 2.6.21-rc4-mm1 Cornelia Huck @ 2007-03-22 18:55 ` Larry Finger 2007-03-23 10:10 ` 2.6.21-rc4-mm1 Cornelia Huck 0 siblings, 1 reply; 146+ messages in thread From: Larry Finger @ 2007-03-22 18:55 UTC (permalink / raw) To: Cornelia Huck Cc: Andrew Morton, Matt Mackall, linux-kernel, linux-wireless, Monakhov Dmitriy [-- Attachment #1: Type: text/plain, Size: 545 bytes --] Cornelia Huck wrote: > On Thu, 22 Mar 2007 07:23:06 -0500, > > This would indicate that dev_uevent had been called. But how could > kobject_uevent then return an error without moaning about an uevent() > error code? Maybe the following debug patch could shed some light on > this (all moaning is prefixed with kobject_uevent_env, so it should be > easy to spot)... I applied the debug patch, but I don't see any error codes being returned. This time I also got the General Protection Faults. An excerpt of the log is attached. Thanks, Larry [-- Attachment #2: messages --] [-- Type: text/plain, Size: 15127 bytes --] Mar 22 13:01:21 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices Mar 22 13:01:21 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:01:21 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:01:21 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:01:21 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:01:21 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:01:21 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:01:21 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:01:21 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:01:21 larrylap2 kernel: firmware_loading_store: unexpected value (0) Mar 22 13:01:21 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:01:21 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:01:21 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:01:21 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:01:21 larrylap2 kernel: kobject 0000:01:00.0: cleaning up Mar 22 13:01:21 larrylap2 kernel: bcm43xx: Error: PCM "bcm43xx_pcm5.fw" not available or load failed. Mar 22 13:01:21 larrylap2 kernel: bcm43xx: core_up for active 802.11 core failed (-2) Mar 22 13:01:45 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices Mar 22 13:01:45 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:01:45 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:01:45 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:01:45 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:01:45 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:01:45 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:01:45 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:01:45 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:01:46 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices Mar 22 13:01:46 larrylap2 kernel: firmware_loading_store: unexpected value (0) Mar 22 13:01:46 larrylap2 kernel: kobject 0000:01:00.0: cleaning up Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:01:46 larrylap2 kernel: kobject 0000:01:00.0: cleaning up Mar 22 13:01:46 larrylap2 kernel: bcm43xx: Error: PCM "bcm43xx_pcm5.fw" not available or load failed. Mar 22 13:01:46 larrylap2 kernel: bcm43xx: core_up for active 802.11 core failed (-2) Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: cleaning up Mar 22 13:02:10 larrylap2 kernel: general protection fault: 0000 [2] SMP Mar 22 13:02:10 larrylap2 kernel: last sysfs file: class/firmware/0000:01:00.0/loading Mar 22 13:02:10 larrylap2 kernel: CPU 0 Mar 22 13:02:10 larrylap2 kernel: Modules linked in: snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device cpufreq_conservative cpufreq_ondemand cpufreq_userspace cpufreq_powersave powernow_k8 freq_table button battery ac nls_utf8 ntfs loop nfsd exportfs nfs lockd nfs_acl sunrpc sr_mod usb_storage libusual snd_hda_intel snd_hda_codec snd_pcm snd_timer snd ohci1394 sdhci ieee1394 soundcore mmc_core snd_page_alloc forcedeth ehci_hcd ide_cd cdrom ohci_hcd usbcore i2c_nforce2 bcm43xx firmware_class ieee80211softmac ieee80211 ieee80211_crypt ext3 mbcache jbd edd sg fan sata_nv libata amd74xx thermal processor sd_mod scsi_mod ide_disk ide_core Mar 22 13:02:10 larrylap2 kernel: Pid: 4178, comm: cat Not tainted 2.6.21-rc4-mm1-mm1 #14 Mar 22 13:02:10 larrylap2 kernel: RIP: 0010:[<ffffffff80251f99>] [<ffffffff80251f99>] module_put+0x1f/0x35 Mar 22 13:02:10 larrylap2 kernel: RSP: 0018:ffff810009161ea8 EFLAGS: 00010256 Mar 22 13:02:10 larrylap2 kernel: RAX: 6b6b6b6b6b6b6dab RBX: ffff810005e0c420 RCX: ffffffff803f6183 Mar 22 13:02:10 larrylap2 kernel: RDX: 0000000000000001 RSI: ffffffff802ec409 RDI: 6b6b6b6b6b6b6b6b Mar 22 13:02:10 larrylap2 kernel: RBP: ffff810009161ea8 R08: 0000000000000000 R09: ffff81000879a888 Mar 22 13:02:10 larrylap2 kernel: R10: 0000000000000000 R11: ffffffff8811b020 R12: ffff810007c7d000 Mar 22 13:02:10 larrylap2 kernel: R13: ffff8100089c86f8 R14: ffff8100082ba048 R15: ffff8100034017c0 Mar 22 13:02:10 larrylap2 kernel: FS: 00002adf2d6ee6f0(0000) GS:ffffffff8051e000(0000) knlGS:00000000f70776d0 Mar 22 13:02:10 larrylap2 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Mar 22 13:02:10 larrylap2 kernel: CR2: 00002adf2d4133c0 CR3: 0000000009146000 CR4: 00000000000006e0 Mar 22 13:02:10 larrylap2 kernel: Process cat (pid: 4178, threadinfo ffff810009160000, task ffff810004d94080) Mar 22 13:02:10 larrylap2 kernel: Stack: ffff810009161ec8 ffffffff802cf4ba 0000000000000008 ffff8100082ba048 Mar 22 13:02:10 larrylap2 kernel: ffff810009161f08 ffffffff80290a44 ffff8100086c2390 ffff8100089c86f8 Mar 22 13:02:10 larrylap2 kernel: ffff810003590368 0000000000000000 ffff8100089c86f8 00007fff7d91b2d0 Mar 22 13:02:10 larrylap2 kernel: Call Trace: Mar 22 13:02:10 larrylap2 kernel: [<ffffffff802cf4ba>] release+0x3a/0x49 Mar 22 13:02:10 larrylap2 kernel: [<ffffffff80290a44>] __fput+0xca/0x180 Mar 22 13:02:10 larrylap2 kernel: [<ffffffff80290b0e>] fput+0x14/0x16 Mar 22 13:02:10 larrylap2 kernel: [<ffffffff8028e1aa>] filp_close+0x66/0x71 Mar 22 13:02:10 larrylap2 kernel: [<ffffffff8028f3c2>] sys_close+0x98/0xdd Mar 22 13:02:10 larrylap2 kernel: [<ffffffff80209f6e>] system_call+0x7e/0x83 Mar 22 13:02:10 larrylap2 kernel: Mar 22 13:02:10 larrylap2 kernel: Mar 22 13:02:10 larrylap2 kernel: Code: 48 ff 08 83 3f 02 75 0c 48 8b bf 50 22 00 00 e8 08 9d fd ff Mar 22 13:02:10 larrylap2 kernel: RIP [<ffffffff80251f99>] module_put+0x1f/0x35 Mar 22 13:02:10 larrylap2 kernel: RSP <ffff810009161ea8> Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: cleaning up Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:02:10 larrylap2 kernel: firmware_loading_store: unexpected value (0) Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: cleaning up Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0 Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0' Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0 Mar 22 13:02:10 larrylap2 kernel: bcm43xx: Error: InitVals "bcm43xx_initval06.fw" not available or load failed. Mar 22 13:02:10 larrylap2 kernel: bcm43xx: core_up for active 802.11 core failed (-2) Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: cleaning up Mar 22 13:02:10 larrylap2 kernel: general protection fault: 0000 [3] SMP Mar 22 13:02:10 larrylap2 kernel: last sysfs file: class/firmware/0000:01:00.0/loading Mar 22 13:02:10 larrylap2 kernel: CPU 0 Mar 22 13:02:10 larrylap2 kernel: Modules linked in: snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device cpufreq_conservative cpufreq_ondemand cpufreq_userspace cpufreq_powersave powernow_k8 freq_table button battery ac nls_utf8 ntfs loop nfsd exportfs nfs lockd nfs_acl sunrpc sr_mod usb_storage libusual snd_hda_intel snd_hda_codec snd_pcm snd_timer snd ohci1394 sdhci ieee1394 soundcore mmc_core snd_page_alloc forcedeth ehci_hcd ide_cd cdrom ohci_hcd usbcore i2c_nforce2 bcm43xx firmware_class ieee80211softmac ieee80211 ieee80211_crypt ext3 mbcache jbd edd sg fan sata_nv libata amd74xx thermal processor sd_mod scsi_mod ide_disk ide_core Mar 22 13:02:10 larrylap2 kernel: Pid: 4199, comm: cat Not tainted 2.6.21-rc4-mm1-mm1 #14 Mar 22 13:02:10 larrylap2 kernel: RIP: 0010:[<ffffffff80251f99>] [<ffffffff80251f99>] module_put+0x1f/0x35 Mar 22 13:02:10 larrylap2 kernel: RSP: 0018:ffff810008bfdea8 EFLAGS: 00010256 Mar 22 13:02:10 larrylap2 kernel: RAX: 6b6b6b6b6b6b6dab RBX: ffff8100070eb308 RCX: ffffffff803f6183 Mar 22 13:02:10 larrylap2 kernel: RDX: 0000000000000001 RSI: ffffffff802ec409 RDI: 6b6b6b6b6b6b6b6b Mar 22 13:02:10 larrylap2 kernel: RBP: ffff810008bfdea8 R08: 0000000000000000 R09: ffff810008745338 Mar 22 13:02:10 larrylap2 kernel: R10: 0000000000000000 R11: ffffffff8811b020 R12: ffff81000999c000 Mar 22 13:02:10 larrylap2 kernel: R13: ffff8100089945a8 R14: ffff81000883e828 R15: ffff8100034017c0 Mar 22 13:02:10 larrylap2 kernel: FS: 00002b325c21c6f0(0000) GS:ffffffff8051e000(0000) knlGS:00000000f70776d0 Mar 22 13:02:10 larrylap2 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Mar 22 13:02:10 larrylap2 kernel: CR2: 00002b325bf413c0 CR3: 0000000005a02000 CR4: 00000000000006e0 Mar 22 13:02:10 larrylap2 kernel: Process cat (pid: 4199, threadinfo ffff810008bfc000, task ffff810006b78140) Mar 22 13:02:10 larrylap2 kernel: Stack: ffff810008bfdec8 ffffffff802cf4ba 0000000000000008 ffff81000883e828 Mar 22 13:02:10 larrylap2 kernel: ffff810008bfdf08 ffffffff80290a44 ffff8100086c26a8 ffff8100089945a8 Mar 22 13:02:10 larrylap2 kernel: ffff810009010050 0000000000000000 ffff8100089945a8 00007fff4edeb7a0 Mar 22 13:02:10 larrylap2 kernel: Call Trace: Mar 22 13:02:10 larrylap2 kernel: [<ffffffff802cf4ba>] release+0x3a/0x49 Mar 22 13:02:10 larrylap2 kernel: [<ffffffff80290a44>] __fput+0xca/0x180 Mar 22 13:02:10 larrylap2 kernel: [<ffffffff80290b0e>] fput+0x14/0x16 Mar 22 13:02:10 larrylap2 kernel: [<ffffffff8028e1aa>] filp_close+0x66/0x71 Mar 22 13:02:10 larrylap2 kernel: [<ffffffff8028f3c2>] sys_close+0x98/0xdd Mar 22 13:02:10 larrylap2 kernel: [<ffffffff80209f6e>] system_call+0x7e/0x83 Mar 22 13:02:10 larrylap2 kernel: Mar 22 13:02:10 larrylap2 kernel: Mar 22 13:02:10 larrylap2 kernel: Code: 48 ff 08 83 3f 02 75 0c 48 8b bf 50 22 00 00 e8 08 9d fd ff Mar 22 13:02:10 larrylap2 kernel: RIP [<ffffffff80251f99>] module_put+0x1f/0x35 Mar 22 13:02:10 larrylap2 kernel: RSP <ffff810008bfdea8> ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 18:55 ` 2.6.21-rc4-mm1 Larry Finger @ 2007-03-23 10:10 ` Cornelia Huck 2007-03-23 15:00 ` 2.6.21-rc4-mm1 Larry Finger 2007-03-24 5:06 ` 2.6.21-rc4-mm1 Andrew Morton 0 siblings, 2 replies; 146+ messages in thread From: Cornelia Huck @ 2007-03-23 10:10 UTC (permalink / raw) To: Larry Finger Cc: Andrew Morton, Matt Mackall, linux-kernel, linux-wireless, Monakhov Dmitriy On Thu, 22 Mar 2007 13:55:51 -0500, Larry Finger <larry.finger@lwfinger.net> wrote: > Cornelia Huck wrote: > > On Thu, 22 Mar 2007 07:23:06 -0500, > > > > This would indicate that dev_uevent had been called. But how could > > kobject_uevent then return an error without moaning about an uevent() > > error code? Maybe the following debug patch could shed some light on > > this (all moaning is prefixed with kobject_uevent_env, so it should be > > easy to spot)... > > I applied the debug patch, but I don't see any error codes being returned. This time I also got the > General Protection Faults. An excerpt of the log is attached. Hm, I think I have an idea about what happened. The firmware class tried to suppress the first KOBJ_ADD uevent by returning -ENODEV in firmware_uevent if FW_STATUS_READY was not set. This only worked as long as the return code of kobject_uevent was not checked in device_add. hack-to-make-wireless-work.patch made that first uevent return successfully, but this possible triggered some udev rule too early, leading to firmware load failures. The following (completely untested) patch uses uevent_suppress to stop the uevent from being generated during device_add. Does this work for you? --- drivers/base/firmware_class.c | 2 ++ 1 file changed, 2 insertions(+) --- linux-2.6.orig/drivers/base/firmware_class.c +++ linux-2.6/drivers/base/firmware_class.c @@ -333,6 +333,7 @@ static int fw_register_device(struct dev f_dev->parent = device; f_dev->class = &firmware_class; dev_set_drvdata(f_dev, fw_priv); + f_dev->uevent_suppress = 1; retval = device_register(f_dev); if (retval) { printk(KERN_ERR "%s: device_register failed\n", @@ -385,6 +386,7 @@ static int fw_setup_device(struct firmwa set_bit(FW_STATUS_READY, &fw_priv->status); else set_bit(FW_STATUS_READY_NOHOTPLUG, &fw_priv->status); + f_dev->uevent_suppress = 0; *dev_p = f_dev; goto out; ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-23 10:10 ` 2.6.21-rc4-mm1 Cornelia Huck @ 2007-03-23 15:00 ` Larry Finger 2007-03-24 5:06 ` 2.6.21-rc4-mm1 Andrew Morton 1 sibling, 0 replies; 146+ messages in thread From: Larry Finger @ 2007-03-23 15:00 UTC (permalink / raw) To: Cornelia Huck Cc: Andrew Morton, Matt Mackall, linux-kernel, linux-wireless, Monakhov Dmitriy Cornelia Huck wrote: > On Thu, 22 Mar 2007 13:55:51 -0500, > Larry Finger <larry.finger@lwfinger.net> wrote: >> I applied the debug patch, but I don't see any error codes being returned. This time I also got the >> General Protection Faults. An excerpt of the log is attached. > > Hm, I think I have an idea about what happened. > > The firmware class tried to suppress the first KOBJ_ADD uevent by > returning -ENODEV in firmware_uevent if FW_STATUS_READY was not set. > This only worked as long as the return code of kobject_uevent was not > checked in device_add. hack-to-make-wireless-work.patch made that first > uevent return successfully, but this possible triggered some udev rule > too early, leading to firmware load failures. > > The following (completely untested) patch uses uevent_suppress to stop > the uevent from being generated during device_add. Does this work for > you? Yes it does. Good job. On my first reboot with the new code, the startup of X hung with the black screen and the big X cursor, but that seems to have been a single occurrence. With the patch, the bcm43xx firmware is loaded and the device is working. Thanks, Larry ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-23 10:10 ` 2.6.21-rc4-mm1 Cornelia Huck 2007-03-23 15:00 ` 2.6.21-rc4-mm1 Larry Finger @ 2007-03-24 5:06 ` Andrew Morton 2007-03-26 9:09 ` 2.6.21-rc4-mm1 Cornelia Huck 1 sibling, 1 reply; 146+ messages in thread From: Andrew Morton @ 2007-03-24 5:06 UTC (permalink / raw) To: Cornelia Huck Cc: Larry Finger, Matt Mackall, linux-kernel, linux-wireless, Monakhov Dmitriy On Fri, 23 Mar 2007 11:10:29 +0100 Cornelia Huck <cornelia.huck@de.ibm.com> wrote: > On Thu, 22 Mar 2007 13:55:51 -0500, > Larry Finger <larry.finger@lwfinger.net> wrote: > > > Cornelia Huck wrote: > > > On Thu, 22 Mar 2007 07:23:06 -0500, > > > > > > This would indicate that dev_uevent had been called. But how could > > > kobject_uevent then return an error without moaning about an uevent() > > > error code? Maybe the following debug patch could shed some light on > > > this (all moaning is prefixed with kobject_uevent_env, so it should be > > > easy to spot)... > > > > I applied the debug patch, but I don't see any error codes being returned. This time I also got the > > General Protection Faults. An excerpt of the log is attached. > > Hm, I think I have an idea about what happened. > > The firmware class tried to suppress the first KOBJ_ADD uevent by > returning -ENODEV in firmware_uevent if FW_STATUS_READY was not set. > This only worked as long as the return code of kobject_uevent was not > checked in device_add. hack-to-make-wireless-work.patch made that first > uevent return successfully, but this possible triggered some udev rule > too early, leading to firmware load failures. > > The following (completely untested) patch uses uevent_suppress to stop > the uevent from being generated during device_add. Does this work for > you? > > --- > drivers/base/firmware_class.c | 2 ++ > 1 file changed, 2 insertions(+) > > --- linux-2.6.orig/drivers/base/firmware_class.c > +++ linux-2.6/drivers/base/firmware_class.c > @@ -333,6 +333,7 @@ static int fw_register_device(struct dev > f_dev->parent = device; > f_dev->class = &firmware_class; > dev_set_drvdata(f_dev, fw_priv); > + f_dev->uevent_suppress = 1; > retval = device_register(f_dev); > if (retval) { > printk(KERN_ERR "%s: device_register failed\n", > @@ -385,6 +386,7 @@ static int fw_setup_device(struct firmwa > set_bit(FW_STATUS_READY, &fw_priv->status); > else > set_bit(FW_STATUS_READY_NOHOTPLUG, &fw_priv->status); > + f_dev->uevent_suppress = 0; > *dev_p = f_dev; > goto out; hm. Would I be right in guessing that this was all triggered by uevent-improve-error-checking-and-handling.patch? If so, do you think I should labour on with uevent-improve-error-checking-and-handling.patch plus your fix, or should I drop the lot? (I'm inclined toward the latter, but I'm still not sure which patch(es) need to be dropped). Thanks. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-24 5:06 ` 2.6.21-rc4-mm1 Andrew Morton @ 2007-03-26 9:09 ` Cornelia Huck 2007-03-26 9:22 ` 2.6.21-rc4-mm1 Andrew Morton 0 siblings, 1 reply; 146+ messages in thread From: Cornelia Huck @ 2007-03-26 9:09 UTC (permalink / raw) To: Andrew Morton Cc: Larry Finger, Matt Mackall, linux-kernel, linux-wireless, Monakhov Dmitriy, Eric Rannaud On Fri, 23 Mar 2007 21:06:18 -0800, Andrew Morton <akpm@linux-foundation.org> wrote: > Would I be right in guessing that this was all triggered by > uevent-improve-error-checking-and-handling.patch? Looks like it, since it passed the uevent failures to the upper layer. > If so, do you think I should labour on with > uevent-improve-error-checking-and-handling.patch plus your fix, or should I > drop the lot? (I'm inclined toward the latter, but I'm still not > sure which patch(es) need to be dropped). This depends on what semantics uevent returning an error code should have. The firmware code was using it to suppress uevents, but uevent_suppress is a better idea now. So if we want uevent returning != 0 to imply "something really bad happened", all uevent functions have to be audited and those that work like firmware_uevent have to be converted to uevent_suppress. This would be cleaner, but I'm not sure it's worth the work. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-26 9:09 ` 2.6.21-rc4-mm1 Cornelia Huck @ 2007-03-26 9:22 ` Andrew Morton 2007-03-26 10:34 ` 2.6.21-rc4-mm1 Eric Rannaud 0 siblings, 1 reply; 146+ messages in thread From: Andrew Morton @ 2007-03-26 9:22 UTC (permalink / raw) To: Cornelia Huck Cc: Larry Finger, Matt Mackall, linux-kernel, linux-wireless, Monakhov Dmitriy, Eric Rannaud On Mon, 26 Mar 2007 11:09:49 +0200 Cornelia Huck <cornelia.huck@de.ibm.com> wrote: > On Fri, 23 Mar 2007 21:06:18 -0800, > Andrew Morton <akpm@linux-foundation.org> wrote: > > > Would I be right in guessing that this was all triggered by > > uevent-improve-error-checking-and-handling.patch? > > Looks like it, since it passed the uevent failures to the upper layer. OK, thanks. > > If so, do you think I should labour on with > > uevent-improve-error-checking-and-handling.patch plus your fix, or should I > > drop the lot? (I'm inclined toward the latter, but I'm still not > > sure which patch(es) need to be dropped). > > This depends on what semantics uevent returning an error code should > have. The firmware code was using it to suppress uevents, but > uevent_suppress is a better idea now. So if we want uevent returning != > 0 to imply "something really bad happened", all uevent functions have > to be audited and those that work like firmware_uevent have to be > converted to uevent_suppress. This would be cleaner, but I'm not sure > it's worth the work. We're generally struggling to stay alive amongst all the bugs at present - I'll drop all those patches. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-26 9:22 ` 2.6.21-rc4-mm1 Andrew Morton @ 2007-03-26 10:34 ` Eric Rannaud 2007-03-26 10:44 ` 2.6.21-rc4-mm1 Andrew Morton 2007-03-27 9:25 ` 2.6.21-rc4-mm1 Kay Sievers 0 siblings, 2 replies; 146+ messages in thread From: Eric Rannaud @ 2007-03-26 10:34 UTC (permalink / raw) To: Andrew Morton Cc: Cornelia Huck, Larry Finger, Matt Mackall, linux-kernel, linux-wireless, Monakhov Dmitriy On Mon, Mar 26, 2007 at 01:22:32AM -0800, Andrew Morton wrote: > On Mon, 26 Mar 2007 11:09:49 +0200 Cornelia Huck <cornelia.huck@de.ibm.com> wrote: > > > If so, do you think I should labour on with > > > uevent-improve-error-checking-and-handling.patch plus your fix, or should I > > > drop the lot? (I'm inclined toward the latter, but I'm still not > > > sure which patch(es) need to be dropped). > > > > This depends on what semantics uevent returning an error code should > > have. The firmware code was using it to suppress uevents, but > > uevent_suppress is a better idea now. So if we want uevent returning != > > 0 to imply "something really bad happened", all uevent functions have > > to be audited and those that work like firmware_uevent have to be > > converted to uevent_suppress. This would be cleaner, but I'm not sure > > it's worth the work. > > We're generally struggling to stay alive amongst all the bugs at present - > I'll drop all those patches. My mistake, I wrote the guilty patch uevent-improve-error-checking-and-handling.patch assuming it was safe to treat the return value as an error code, since several uevent functions returns things like -ENOMEM. Should I rework the patch as Cornelia suggests and resubmit later, when things have settled down a little? Thanks. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-26 10:34 ` 2.6.21-rc4-mm1 Eric Rannaud @ 2007-03-26 10:44 ` Andrew Morton 2007-03-27 9:25 ` 2.6.21-rc4-mm1 Kay Sievers 1 sibling, 0 replies; 146+ messages in thread From: Andrew Morton @ 2007-03-26 10:44 UTC (permalink / raw) To: Eric Rannaud Cc: Cornelia Huck, Larry Finger, Matt Mackall, linux-kernel, linux-wireless, Monakhov Dmitriy On Mon, 26 Mar 2007 12:34:33 +0200 Eric Rannaud <eric.rannaud@gmail.com> wrote: > On Mon, Mar 26, 2007 at 01:22:32AM -0800, Andrew Morton wrote: > > On Mon, 26 Mar 2007 11:09:49 +0200 Cornelia Huck <cornelia.huck@de.ibm.com> wrote: > > > > If so, do you think I should labour on with > > > > uevent-improve-error-checking-and-handling.patch plus your fix, or should I > > > > drop the lot? (I'm inclined toward the latter, but I'm still not > > > > sure which patch(es) need to be dropped). > > > > > > This depends on what semantics uevent returning an error code should > > > have. The firmware code was using it to suppress uevents, but > > > uevent_suppress is a better idea now. So if we want uevent returning != > > > 0 to imply "something really bad happened", all uevent functions have > > > to be audited and those that work like firmware_uevent have to be > > > converted to uevent_suppress. This would be cleaner, but I'm not sure > > > it's worth the work. > > > > We're generally struggling to stay alive amongst all the bugs at present - > > I'll drop all those patches. > > My mistake, I wrote the guilty patch > uevent-improve-error-checking-and-handling.patch assuming it was safe to > treat the return value as an error code, since several uevent functions > returns things like -ENOMEM. > > Should I rework the patch as Cornelia suggests and resubmit later, when > things have settled down a little? Sure, when we've fixed all the bugs ;) I think we now know what to test for - firmware loading simply collapsed all over the place with these changes. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-26 10:34 ` 2.6.21-rc4-mm1 Eric Rannaud 2007-03-26 10:44 ` 2.6.21-rc4-mm1 Andrew Morton @ 2007-03-27 9:25 ` Kay Sievers 2007-03-27 17:17 ` 2.6.21-rc4-mm1 Cornelia Huck 1 sibling, 1 reply; 146+ messages in thread From: Kay Sievers @ 2007-03-27 9:25 UTC (permalink / raw) To: Eric Rannaud Cc: Andrew Morton, Cornelia Huck, Larry Finger, Matt Mackall, linux-kernel, linux-wireless, Monakhov Dmitriy On 3/26/07, Eric Rannaud <eric.rannaud@gmail.com> wrote: > On Mon, Mar 26, 2007 at 01:22:32AM -0800, Andrew Morton wrote: > > On Mon, 26 Mar 2007 11:09:49 +0200 Cornelia Huck <cornelia.huck@de.ibm.com> wrote: > > > > If so, do you think I should labour on with > > > > uevent-improve-error-checking-and-handling.patch plus your fix, or should I > > > > drop the lot? (I'm inclined toward the latter, but I'm still not > > > > sure which patch(es) need to be dropped). > > > > > > This depends on what semantics uevent returning an error code should > > > have. The firmware code was using it to suppress uevents, but > > > uevent_suppress is a better idea now. So if we want uevent returning != > > > 0 to imply "something really bad happened", all uevent functions have > > > to be audited and those that work like firmware_uevent have to be > > > converted to uevent_suppress. This would be cleaner, but I'm not sure > > > it's worth the work. > > > > We're generally struggling to stay alive amongst all the bugs at present - > > I'll drop all those patches. > > My mistake, I wrote the guilty patch > uevent-improve-error-checking-and-handling.patch assuming it was safe to > treat the return value as an error code, since several uevent functions > returns things like -ENOMEM. > > Should I rework the patch as Cornelia suggests and resubmit later, when > things have settled down a little? I don't see any point in deregistering a kernel device, if the event to userspace goes wrong, or a subsytem returns a non-zero value in the filter. Checking the uevent return value, will not prevent any malfunction, usually this kind of "error handling" just prevents bringing up a whole subsystem, or booting-up a box, because the needed device does not exist at all. Thanks, Kay ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-27 9:25 ` 2.6.21-rc4-mm1 Kay Sievers @ 2007-03-27 17:17 ` Cornelia Huck 2007-03-28 1:26 ` 2.6.21-rc4-mm1 Eric Rannaud 0 siblings, 1 reply; 146+ messages in thread From: Cornelia Huck @ 2007-03-27 17:17 UTC (permalink / raw) To: Kay Sievers Cc: Eric Rannaud, Andrew Morton, Larry Finger, Matt Mackall, linux-kernel, linux-wireless, Monakhov Dmitriy On Tue, 27 Mar 2007 11:25:57 +0200, "Kay Sievers" <kay.sievers@vrfy.org> wrote: > I don't see any point in deregistering a kernel device, if the event > to userspace goes wrong, or a subsytem returns a non-zero value in the > filter. But if we filter the event, we just return 0? > Checking the uevent return value, will not prevent any malfunction, > usually this kind of "error handling" just prevents bringing up a > whole subsystem, or booting-up a box, because the needed device does > not exist at all. OK, if we consider uevents to be non-vital to a functioning device. OTOH, I think using something like uevent_suppress (maybe via dev_uevent_filter?) is a saner way to suppress a uevent than to return an error code in the uevent function. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-27 17:17 ` 2.6.21-rc4-mm1 Cornelia Huck @ 2007-03-28 1:26 ` Eric Rannaud 2007-03-28 8:25 ` 2.6.21-rc4-mm1 Cornelia Huck 0 siblings, 1 reply; 146+ messages in thread From: Eric Rannaud @ 2007-03-28 1:26 UTC (permalink / raw) To: Cornelia Huck Cc: Kay Sievers, Andrew Morton, Larry Finger, Matt Mackall, linux-kernel, linux-wireless, Monakhov Dmitriy On Tue, Mar 27, 2007 at 07:17:49PM +0200, Cornelia Huck wrote: > On Tue, 27 Mar 2007 11:25:57 +0200, > "Kay Sievers" <kay.sievers@vrfy.org> wrote: > > Checking the uevent return value, will not prevent any malfunction, > > usually this kind of "error handling" just prevents bringing up a > > whole subsystem, or booting-up a box, because the needed device does > > not exist at all. > > OK, if we consider uevents to be non-vital to a functioning device. The reason for that original patch was that it is actually possible for the uevent functions to return -ENOMEM, the uevent buffer being statically allocated to BUFFER_SIZE (2048). It used to be 1024 but that was not always enough and it was doubled a while ago [1]. Using add_uevent_var() makes this less of a problem as such an overflow should be catched cleanly [2]. > OTOH, I think using something like uevent_suppress (maybe via > dev_uevent_filter?) is a saner way to suppress a uevent than to return > an error code in the uevent function. That makes sense, I guess. I will try that. Thanks. [1] http://marc.info/?t=113797361200002&r=1&w=2 [2] uevent-use-add_uevent_var-instead-of-open-coding-it.patch in rc4-mm1 ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-28 1:26 ` 2.6.21-rc4-mm1 Eric Rannaud @ 2007-03-28 8:25 ` Cornelia Huck 0 siblings, 0 replies; 146+ messages in thread From: Cornelia Huck @ 2007-03-28 8:25 UTC (permalink / raw) To: Eric Rannaud Cc: Kay Sievers, Andrew Morton, Larry Finger, Matt Mackall, linux-kernel, linux-wireless, Monakhov Dmitriy On Wed, 28 Mar 2007 03:26:35 +0200, Eric Rannaud <eric.rannaud@gmail.com> wrote: > The reason for that original patch was that it is actually possible for the > uevent functions to return -ENOMEM, the uevent buffer being statically > allocated to BUFFER_SIZE (2048). So maybe -ENOMEM should still be propagated? We just don't want to fail device_add because of it. > It used to be 1024 but that was not > always enough and it was doubled a while ago [1]. Using add_uevent_var() > makes this less of a problem as such an overflow should be catched > cleanly [2]. Reminds me that I need to look into ccw_uevent :) ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 7:39 ` 2.6.21-rc4-mm1 Andrew Morton 2007-03-22 11:35 ` 2.6.21-rc4-mm1 Cornelia Huck @ 2007-03-24 22:32 ` Matt Mackall 1 sibling, 0 replies; 146+ messages in thread From: Matt Mackall @ 2007-03-24 22:32 UTC (permalink / raw) To: Andrew Morton, Cornelia Huck Cc: linux-kernel, linux-wireless, Monakhov Dmitriy On Wed, Mar 21, 2007 at 11:39:17PM -0800, Andrew Morton wrote: > On Wed, 21 Mar 2007 15:22:25 -0500 Matt Mackall <mpm@selenic.com> wrote: > > > With the latest -mm, I'm now getting this: > > > > Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless > > 2200BG Network Connection > > Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected > > value (0) > > Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw > > request_firmware failed: > > Reason -2 > > Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2 > > Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network > > device > > The firmware loading bug is caused by > driver-core-handles-kobject_uevent-failure-while-device_add.patch > > I've uploaded a revert patch to > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/hot-fixes/ For the record, with the following patches: # hotfixes mm-debug-check-for-the-fault-vs-invalidate-race.patch mm-fix-fault-vs-invalidate-race-for-linear-mappings-fix-2.patch mm-fix-fault-vs-invalidate-race-for-linear-mappings-fix.patch revert-driver-core-handles-kobject_uevent-failure-while-device_add.patch tty-in-tiocsctty-when-we-steal-a-tty-hang-it-up-fix.patch ...I just had a boot where firmware loading failed again. rmmod+insmod fixed it. -- Mathematics is the supreme nostalgia of our time. ^ permalink raw reply [flat|nested] 146+ messages in thread
* 2.6.21-rc4-mm1 - problem with cpuidle routine 2007-03-21 6:36 ` 2.6.21-rc4-mm1 Andrew Morton ` (3 preceding siblings ...) 2007-03-21 18:14 ` 2.6.21-rc4-mm1 Larry Finger @ 2007-03-21 18:49 ` Larry Finger 2007-03-21 20:38 ` Andrew Morton 2007-03-21 20:39 ` 2.6.21-rc4-mm1 " Venki Pallipadi 4 siblings, 2 replies; 146+ messages in thread From: Larry Finger @ 2007-03-21 18:49 UTC (permalink / raw) To: Andrew Morton; +Cc: LKML When I configure 'CPU Idle PM Support' on my HP dv2125nr notebook with a Turion X64 X2 processor and X86_64 architecture selected, the computer freezes on bootup. I have included a portion the configuration file and part of /var/log/boot.msg for my working system. Please let me know if further info from my system is required. I would be happy to test any patches, etc. Larry ============================================================== The console log ends with the following entries: ACPI: Processor [CPU0] (supports 8 throttling states) ACPI: Processor [CPU1] (supports 8 throttling states) cpuidle: driver acpi_idle failed to attach to cpu 0 cpuidle: driver acpi_idle failed to attach to cpu 0 cpuidle: using driver acpi_idle Loading thermal At this point, the system hangs. ================================================= The beginning section of my .config is as follows: # # Automatically generated make config: don't edit # Linux kernel version: 2.6.21-rc4-mm1 # Wed Mar 21 13:05:07 2007 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_ZONE_DMA32=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_DMI=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="-mm1" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SWAP_PREFETCH=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y # CONFIG_TASK_XACCT is not set # CONFIG_UTS_NS is not set CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_CPUSETS=y CONFIG_SYSFS_DEPRECATED=y CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set CONFIG_PAGE_GROUP_BY_MOBILITY=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_MODVERSIONS=y CONFIG_MODULE_SRCVERSION_ALL=y CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Process debugging support # CONFIG_UTRACE=y CONFIG_PTRACE=y # # Block layer # CONFIG_BLOCK=y # CONFIG_BLK_DEV_IO_TRACE is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_VSMP is not set CONFIG_MK8=y # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y # CONFIG_MICROCODE is not set CONFIG_X86_MSR=m CONFIG_X86_CPUID=m CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_MTRR=y CONFIG_SMP=y CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set # CONFIG_PREEMPT_BKL is not set # CONFIG_NUMA is not set CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_RESOURCES_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_ADAPTIVE_READAHEAD=y # CONFIG_DEBUG_READAHEAD is not set CONFIG_NR_CPUS=128 CONFIG_HOTPLUG_CPU=y CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_IOMMU=y # CONFIG_CALGARY_IOMMU is not set CONFIG_SWIOTLB=y CONFIG_X86_MCE=y CONFIG_X86_MCE_INTEL=y CONFIG_X86_MCE_AMD=y CONFIG_KEXEC=y # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x200000 CONFIG_SECCOMP=y # CONFIG_CC_STACKPROTECTOR is not set # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_300 is not set # CONFIG_HZ_1000 is not set CONFIG_HZ=250 # CONFIG_REORDER is not set CONFIG_K8_NB=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_ISA_DMA_API=y CONFIG_GENERIC_PENDING_IRQ=y # # Power management options # CONFIG_PM=y CONFIG_PM_LEGACY=y # CONFIG_PM_DEBUG is not set # CONFIG_PM_SYSFS_DEPRECATED is not set CONFIG_SOFTWARE_SUSPEND=y CONFIG_PM_STD_PARTITION="" CONFIG_SUSPEND_SMP=y # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y CONFIG_ACPI_SLEEP_PROC_SLEEP=y CONFIG_ACPI_PROCFS=y CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_FAN=m CONFIG_ACPI_DOCK=m # CONFIG_ACPI_BAY is not set CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_HOTPLUG_CPU=y CONFIG_ACPI_THERMAL=m # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_IBM is not set # CONFIG_ACPI_TOSHIBA is not set # CONFIG_ACPI_CUSTOM_DSDT is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y CONFIG_ACPI_CONTAINER=m CONFIG_ACPI_SBS=m # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=m # CONFIG_CPU_FREQ_DEBUG is not set CONFIG_CPU_FREQ_STAT=m CONFIG_CPU_FREQ_STAT_DETAILS=y CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=m CONFIG_CPU_FREQ_GOV_ONDEMAND=m CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m # # CPUFreq processor drivers # CONFIG_X86_POWERNOW_K8=m CONFIG_X86_POWERNOW_K8_ACPI=y # CONFIG_X86_SPEEDSTEP_CENTRINO is not set CONFIG_X86_ACPI_CPUFREQ=m # # shared options # # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set # CONFIG_X86_SPEEDSTEP_LIB is not set # # CPU idle PM support # CONFIG_CPU_IDLE=y # # Governors # CONFIG_CPU_IDLE_GOV_LADDER=y # # Bus options (PCI etc.) # ... ================================================================= A listing of /var/log/boot.msg (from my running system) to the point at which it fails when cpuidle is loaded is as follows: Inspecting /boot/System.map-2.6.21-rc3-L2.6-g61ae474e-dirty Loaded 23859 symbols from /boot/System.map-2.6.21-rc3-L2.6-g61ae474e-dirty. Symbols match kernel version 2.6.21. No module symbols loaded - kernel modules not enabled. klogd 1.4.1, log source = ksyslog started. <5>Linux version 2.6.21-rc3-L2.6-g61ae474e-dirty (finger@larrylap2) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #2 SMP Mon Mar 12 14:51:06 CDT 2007 <6>Command line: root=/dev/sda3 vga=0x317 resume=/dev/sda2 splash=silent <6>BIOS-provided physical RAM map: <4> BIOS-e820: 0000000000000000 - 000000000009dc00 (usable) <4> BIOS-e820: 000000000009dc00 - 00000000000a0000 (reserved) <4> BIOS-e820: 00000000000d2000 - 0000000000100000 (reserved) <4> BIOS-e820: 0000000000100000 - 000000005bf10000 (usable) <4> BIOS-e820: 000000005bf10000 - 000000005bf19000 (ACPI data) <4> BIOS-e820: 000000005bf19000 - 000000005bf80000 (ACPI NVS) <4> BIOS-e820: 000000005bf80000 - 0000000060000000 (reserved) <4> BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) <4> BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved) <4> BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) <4> BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved) <7>Entering add_active_range(0, 0, 157) 0 entries of 256 used <7>Entering add_active_range(0, 256, 376592) 1 entries of 256 used <4>end_pfn_map = 1048576 <6>DMI present. <4>ACPI: RSDP 000F87C0, 0014 (r0 HP ) <4>ACPI: RSDT 5BF131F0, 0038 (r1 HP 30B5 6040000 LTP 0) <4>ACPI: FACP 5BF18D52, 0074 (r1 HP 30B5 6040000 PTL_ F4240) <4>ACPI: DSDT 5BF13228, 5B2A (r1 HP 30B5 6040000 MSFT 100000E) <4>ACPI: FACS 5BF19FC0, 0040 <4>ACPI: MCFG 5BF18DC6, 003C (r1 HP 30B5 6040000 LTP 0) <4>ACPI: APIC 5BF18E02, 0054 (r1 HP 30B5 6040000 LTP 0) <4>ACPI: BOOT 5BF18E56, 0028 (r1 HP 30B5 6040000 LTP 1) <4>ACPI: SSDT 5BF18E7E, 0182 (r1 HP 30B5 6040000 LTP 1) <7>Entering add_active_range(0, 0, 157) 0 entries of 256 used <7>Entering add_active_range(0, 256, 376592) 1 entries of 256 used <4>Zone PFN ranges: <4> DMA 0 -> 4096 <4> DMA32 4096 -> 1048576 <4> Normal 1048576 -> 1048576 <4>early_node_map[2] active PFN ranges <4> 0: 0 -> 157 <4> 0: 256 -> 376592 <7>On node 0 totalpages: 376493 <7> DMA zone: 88 pages used for memmap <7> DMA zone: 2241 pages reserved <7> DMA zone: 1668 pages, LIFO batch:0 <7> DMA32 zone: 8002 pages used for memmap <7> DMA32 zone: 364494 pages, LIFO batch:31 <7> Normal zone: 0 pages used for memmap <6>ACPI: PM-Timer IO Port: 0x1008 <7>ACPI: Local APIC address 0xfee00000 <6>ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) <6>Processor #0 (Bootup-CPU) <6>ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) <6>Processor #1 <6>ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) <6>ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) <6>ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) <6>IOAPIC[0]: apic_id 2, address 0xfec00000, GSI 0-23 <7>ACPI: IRQ9 used by override. <6>Setting APIC routing to physical flat <6>Using ACPI (MADT) for SMP configuration information <4>Nosave address range: 000000000009d000 - 000000000009e000 <4>Nosave address range: 000000000009e000 - 00000000000a0000 <4>Nosave address range: 00000000000a0000 - 00000000000d2000 <4>Nosave address range: 00000000000d2000 - 0000000000100000 <6>Allocating PCI resources starting at 68000000 (gap: 60000000:80000000) <6>SMP: Allowing 2 CPUs, 0 hotplug CPUs <6>PERCPU: Allocating 49728 bytes of per cpu data <4>Built 1 zonelists. Total pages: 366162 <5>Kernel command line: root=/dev/sda3 vga=0x317 resume=/dev/sda2 splash=silent <4>Initializing CPU#0 <4>PID hash table entries: 4096 (order: 12, 32768 bytes) <6>time.c: Detected 1607.353 MHz processor. <4>Console: colour dummy device 80x25 <4>Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar <4>... MAX_LOCKDEP_SUBCLASSES: 8 <4>... MAX_LOCK_DEPTH: 30 <4>... MAX_LOCKDEP_KEYS: 2048 <4>... CLASSHASH_SIZE: 1024 <4>... MAX_LOCKDEP_ENTRIES: 8192 <4>... MAX_LOCKDEP_CHAINS: 16384 <4>... CHAINHASH_SIZE: 8192 <4> memory used by lock dependency info: 1648 kB <4> per task-struct memory footprint: 1680 bytes <4>Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) <4>Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) <4>Checking aperture... <4>CPU 0: aperture @ 8492000000 size 32 MB <4>Aperture too small (32 MB) <4>No AGP bridge found <4>Memory: 1457524k/1506368k available (1886k kernel code, 48008k reserved, 1205k data, 220k init) <4>Calibrating delay using timer specific routine.. 3218.55 BogoMIPS (lpj=6437119) <4>Mount-cache hash table entries: 256 <6>CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) <6>CPU: L2 Cache: 256K (64 bytes/line) <6>CPU: Physical Processor ID: 0 <6>CPU: Processor Core ID: 0 <4>lockdep: not fixing up alternatives. <6>ACPI: Core revision 20070126 <6>Using local APIC timer interrupts. <4>result 12557461 <6>Detected 12.557 MHz APIC timer. <4>lockdep: not fixing up alternatives. <6>Booting processor 1/2 APIC 0x1 <4>Initializing CPU#1 <4>Calibrating delay using timer specific routine.. 3214.91 BogoMIPS (lpj=6429832) <6>CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) <6>CPU: L2 Cache: 256K (64 bytes/line) <6>CPU: Physical Processor ID: 0 <6>CPU: Processor Core ID: 1 <4>AMD Turion(tm) 64 X2 stepping 02 <6>Brought up 2 CPUs <6>testing NMI watchdog ... OK. <4>migration_cost=163 <6>NET: Registered protocol family 16 <6>ACPI: bus type pci registered <6>PCI: Using MMCONFIG at e0000000 - e02fffff <5>PCI: No mmconfig possible on device 00:18 <5>PCI: No mmconfig possible on device 03:09 <6>ACPI: Interpreter enabled <6>ACPI: (supports S0 S3 S4 S5) <6>ACPI: Using IOAPIC for interrupt routing <6>ACPI: PCI Root Bridge [PCI0] (0000:00) <7>PCI: Probing PCI hardware (bus 00) <7>PCI: Scanning bus 0000:00 <7>PCI: Found 0000:00:00.0 [10de/02f0] 000500 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:00.0 <7>PCI: Found 0000:00:00.1 [10de/02fa] 000500 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:00.1 <7>PCI: Found 0000:00:00.2 [10de/02fe] 000500 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:00.2 <7>PCI: Found 0000:00:00.3 [10de/02f8] 000500 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:00.3 <7>PCI: Found 0000:00:00.4 [10de/02f9] 000500 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:00.4 <7>PCI: Found 0000:00:00.5 [10de/02ff] 000500 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:00.5 <7>PCI: Found 0000:00:00.6 [10de/027f] 000500 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:00.6 <7>PCI: Found 0000:00:00.7 [10de/027e] 000500 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:00.7 <7>PCI: Found 0000:00:02.0 [10de/02fc] 000604 01 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:02.0 <7>PCI: Found 0000:00:03.0 [10de/02fd] 000604 01 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:03.0 <7>PCI: Found 0000:00:05.0 [10de/0244] 000300 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:05.0 <7>Boot video device is 0000:00:05.0 <7>PCI: Found 0000:00:09.0 [10de/0270] 000500 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:09.0 <7>PCI: Found 0000:00:0a.0 [10de/0260] 000601 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:0a.0 <7>PCI: Found 0000:00:0a.1 [10de/0264] 000c05 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:0a.1 <7>PCI: Found 0000:00:0a.3 [10de/0271] 000b40 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:0a.3 <7>PCI: Found 0000:00:0b.0 [10de/026d] 000c03 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:0b.0 <7>PCI: Found 0000:00:0b.1 [10de/026e] 000c03 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:0b.1 <7>PCI: Found 0000:00:0d.0 [10de/0265] 000101 00 <4>0000:00:0d.0: cannot adjust BAR0 (not I/O) <4>0000:00:0d.0: cannot adjust BAR1 (not I/O) <4>0000:00:0d.0: cannot adjust BAR2 (not I/O) <4>0000:00:0d.0: cannot adjust BAR3 (not I/O) <7>PCI: Calling quirk ffffffff8037061c for 0000:00:0d.0 <7>PCI: Found 0000:00:0e.0 [10de/0266] 000101 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:0e.0 <7>PCI: Found 0000:00:10.0 [10de/026f] 000604 01 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:10.0 <7>PCI: Found 0000:00:10.1 [10de/026c] 000403 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:10.1 <7>PCI: Found 0000:00:14.0 [10de/0269] 000680 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:14.0 <7>PCI: Found 0000:00:18.0 [1022/1100] 000600 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:18.0 <7>PCI: Found 0000:00:18.1 [1022/1101] 000600 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:18.1 <7>PCI: Found 0000:00:18.2 [1022/1102] 000600 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:18.2 <7>PCI: Found 0000:00:18.3 [1022/1103] 000600 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:00:18.3 <7>PCI: Fixups for bus 0000:00 <7>PCI: Scanning behind PCI bridge 0000:00:02.0, config 010100, pass 0 <7>PCI: Scanning bus 0000:01 <7>PCI: Found 0000:01:00.0 [14e4/4311] 000280 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:01:00.0 <7>PCI: Fixups for bus 0000:01 <7>PCI: Bus scan for 0000:01 returning with max=01 <7>PCI: Scanning behind PCI bridge 0000:00:03.0, config 020200, pass 0 <7>PCI: Scanning bus 0000:02 <7>PCI: Fixups for bus 0000:02 <7>PCI: Bus scan for 0000:02 returning with max=02 <7>PCI: Scanning behind PCI bridge 0000:00:10.0, config 030300, pass 0 <7>PCI: Scanning bus 0000:03 <7>PCI: Found 0000:03:09.0 [1180/0832] 000c00 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:03:09.0 <7>PCI: Found 0000:03:09.1 [1180/0822] 000805 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:03:09.1 <7>PCI: Found 0000:03:09.2 [1180/0843] 000880 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:03:09.2 <7>PCI: Found 0000:03:09.3 [1180/0592] 000880 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:03:09.3 <7>PCI: Found 0000:03:09.4 [1180/0852] 000880 00 <7>PCI: Calling quirk ffffffff8037061c for 0000:03:09.4 <7>PCI: Fixups for bus 0000:03 <6>PCI: Transparent bridge - 0000:00:10.0 <7>PCI: Bus scan for 0000:03 returning with max=03 <7>PCI: Scanning behind PCI bridge 0000:00:02.0, config 010100, pass 1 <7>PCI: Scanning behind PCI bridge 0000:00:03.0, config 020200, pass 1 <7>PCI: Scanning behind PCI bridge 0000:00:10.0, config 030300, pass 1 <7>PCI: Bus scan for 0000:00 returning with max=03 <7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] <7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P0._PRT] <7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.XVR1._PRT] <7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.XVR2._PRT] <4>ACPI: PCI Interrupt Link [LNK1] (IRQs 16 17 18 19 20 21 22 23) *0, disabled. <4>ACPI: PCI Interrupt Link [LNK2] (IRQs 16 17 18 19 20 21 22 23) *10 <4>ACPI: PCI Interrupt Link [LNK3] (IRQs 5 7 10 *11 14 15) <4>ACPI: PCI Interrupt Link [LNK4] (IRQs 5 7 10 11 14 15) *0, disabled. <4>ACPI: PCI Interrupt Link [LK1E] (IRQs 20) *0, disabled. <4>ACPI: PCI Interrupt Link [LK2E] (IRQs 19) *10 <4>ACPI: PCI Interrupt Link [LK3E] (IRQs 21) *10 <4>ACPI: PCI Interrupt Link [LK4E] (IRQs 16 17 18 19 20 21 22 23) *0, disabled. <4>ACPI: PCI Interrupt Link [LSMB] (IRQs 16 17 18 19 20 21 22 23) *10 <4>ACPI: PCI Interrupt Link [LSMU] (IRQs 16 17 18 19 20 21 22 23) *11 <4>ACPI: PCI Interrupt Link [LUS0] (IRQs 16 17 18 19 20 21 22 23) *11 <4>ACPI: PCI Interrupt Link [LUS2] (IRQs 16 17 18 19 20 21 22 23) *7 <4>ACPI: PCI Interrupt Link [LMAC] (IRQs 16 17 18 19 20 21 22 23) *11 <4>ACPI: PCI Interrupt Link [LAZA] (IRQs 16 17 18 19 20 21 22 23) *0, disabled. <4>ACPI: PCI Interrupt Link [LACI] (IRQs 16 17 18 19 20 21 22 23) *0, disabled. <4>ACPI: PCI Interrupt Link [LMCI] (IRQs 16 17 18 19 20 21 22 23) *0, disabled. <4>ACPI: PCI Interrupt Link [LPID] (IRQs 16 17 18 19 20 21 22 23) *0, disabled. <4>ACPI: PCI Interrupt Link [LTID] (IRQs 16 17 18 19 20 21 22 23) *5 <4>ACPI: PCI Interrupt Link [LSI1] (IRQs 16 17 18 19 20 21 22 23) *0 <6>Linux Plug and Play Support v0.97 (c) Adam Belay <6>pnp: PnP ACPI init <7>pnp: ACPI device : hid PNP0C01 <7>pnp: ACPI device : hid PNP0A03 <7>pnp: ACPI device : hid PNP0C02 <7>pnp: ACPI device : hid PNP0C02 <7>pnp: ACPI device : hid PNP0C02 <7>pnp: ACPI device : hid PNP0200 <7>pnp: ACPI device : hid PNP0800 <7>pnp: ACPI device : hid PNP0B00 <7>pnp: ACPI device : hid PNP0C04 <7>pnp: ACPI device : hid PNP0303 <7>pnp: ACPI device : hid SYN0127 <6>pnp: PnP ACPI: found 11 devices <6>PCI: Using ACPI for IRQ routing <6>PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report <7>pnp: the driver 'system' has been registered <7>pnp: match found with the PnP device '00:00' and the driver 'system' <6>pnp: 00:00: iomem range 0xffc00000-0xffffffff has been reserved <6>pnp: 00:00: iomem range 0xfec00000-0xfec00fff has been reserved <6>pnp: 00:00: iomem range 0xfee00000-0xfeefffff has been reserved <6>pnp: 00:00: iomem range 0x0-0x0 could not be reserved <7>pnp: match found with the PnP device '00:02' and the driver 'system' <6>pnp: 00:02: iomem range 0xe0000000-0xefffffff has been reserved <7>pnp: match found with the PnP device '00:03' and the driver 'system' <6>pnp: 00:03: ioport range 0x1000-0x107f has been reserved <6>pnp: 00:03: ioport range 0x1080-0x10ff has been reserved <6>pnp: 00:03: ioport range 0x1400-0x147f has been reserved <6>pnp: 00:03: ioport range 0x1480-0x14ff has been reserved <6>pnp: 00:03: ioport range 0x1800-0x187f has been reserved <6>pnp: 00:03: ioport range 0x1880-0x18ff has been reserved <6>pnp: 00:03: ioport range 0x2000-0x203f has been reserved <7>pnp: match found with the PnP device '00:04' and the driver 'system' <6>Time: tsc clocksource has been installed. <7> got res [68000000:6801ffff] bus [68000000:6801ffff] flags 7202 for BAR 6 of 0000:00:05.0 <6>PCI: Bridge: 0000:00:02.0 <6> IO window: disabled. <6> MEM window: c3000000-c30fffff <6> PREFETCH window: disabled. <6>PCI: Bridge: 0000:00:03.0 <6> IO window: 4000-4fff <6> MEM window: c8000000-c87fffff <6> PREFETCH window: disabled. <6>PCI: Bridge: 0000:00:10.0 <6> IO window: disabled. <6> MEM window: c3100000-c31fffff <6> PREFETCH window: disabled. <7>PCI: Setting latency timer of device 0000:00:02.0 to 64 <7>PCI: Setting latency timer of device 0000:00:03.0 to 64 <7>PCI: Setting latency timer of device 0000:00:10.0 to 64 <6>NET: Registered protocol family 2 <6>Time: acpi_pm clocksource has been installed. <4>IP route cache hash table entries: 65536 (order: 7, 524288 bytes) <4>TCP established hash table entries: 65536 (order: 10, 4194304 bytes) <4>TCP bind hash table entries: 65536 (order: 9, 3670016 bytes) <6>TCP: Hash tables configured (established 65536 bind 65536) <6>TCP reno registered <6>checking if image is initramfs... it is <6>Freeing initrd memory: 3311k freed <6>Simple Boot Flag at 0x36 set to 0x1 <6>audit: initializing netlink socket (disabled) <5>audit(1174482018.004:1): initialized <6>io scheduler noop registered <6>io scheduler anticipatory registered <6>io scheduler deadline registered <6>io scheduler cfq registered (default) <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:00.0 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:00.0 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:00.1 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:00.1 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:00.2 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:00.2 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:00.3 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:00.3 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:00.4 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:00.4 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:00.5 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:00.5 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:00.6 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:00.6 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:00.7 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:00.7 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:02.0 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:02.0 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:03.0 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:03.0 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:05.0 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:05.0 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:09.0 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:09.0 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:0a.0 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:0a.0 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:0a.1 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:0a.1 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:0a.3 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:0a.3 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:0b.0 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:0b.0 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:0b.1 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:0b.1 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:0d.0 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:0d.0 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:0e.0 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:0e.0 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:10.0 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:10.0 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:10.1 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:10.1 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:14.0 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:14.0 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:18.0 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:18.0 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:18.1 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:18.1 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:18.2 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:18.2 <7>PCI: Calling quirk ffffffff802f3139 for 0000:00:18.3 <7>PCI: Calling quirk ffffffff80358d25 for 0000:00:18.3 <7>PCI: Calling quirk ffffffff802f3139 for 0000:01:00.0 <7>PCI: Calling quirk ffffffff80358d25 for 0000:01:00.0 <7>PCI: Calling quirk ffffffff802f3139 for 0000:03:09.0 <7>PCI: Calling quirk ffffffff80358d25 for 0000:03:09.0 <7>PCI: Calling quirk ffffffff802f3139 for 0000:03:09.1 <7>PCI: Calling quirk ffffffff80358d25 for 0000:03:09.1 <7>PCI: Calling quirk ffffffff802f3139 for 0000:03:09.2 <7>PCI: Calling quirk ffffffff80358d25 for 0000:03:09.2 <7>PCI: Calling quirk ffffffff802f3139 for 0000:03:09.3 <7>PCI: Calling quirk ffffffff80358d25 for 0000:03:09.3 <7>PCI: Calling quirk ffffffff802f3139 for 0000:03:09.4 <7>PCI: Calling quirk ffffffff80358d25 for 0000:03:09.4 <7>PCI: Setting latency timer of device 0000:00:02.0 to 64 <4>assign_interrupt_mode Found MSI capability <7>Allocate Port Service[0000:00:02.0:pcie00] <7>Allocate Port Service[0000:00:02.0:pcie03] <7>PCI: Setting latency timer of device 0000:00:03.0 to 64 <4>assign_interrupt_mode Found MSI capability <7>Allocate Port Service[0000:00:03.0:pcie00] <7>Allocate Port Service[0000:00:03.0:pcie03] <6>vesafb: framebuffer at 0xd0000000, mapped to 0xffffc20000400000, using 3072k, total 65536k <6>vesafb: mode is 1024x768x16, linelength=2048, pages=1 <6>vesafb: scrolling: redraw <6>vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0 <4>Console: switching to colour frame buffer device 128x48 <6>fb0: VESA VGA frame buffer device <6>Real Time Clock Driver v1.12ac <6>Non-volatile memory driver v1.2 <6>Linux agpgart interface v0.102 (c) Dave Jones <6>Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled <7>pnp: the driver 'serial' has been registered <4>RAMDISK driver initialized: 16 RAM disks of 128000K size 1024 blocksize <7>pnp: the driver 'i8042 kbd' has been registered <7>pnp: match found with the PnP device '00:09' and the driver 'i8042 kbd' <7>pnp: the driver 'i8042 aux' has been registered <7>pnp: match found with the PnP device '00:0a' and the driver 'i8042 aux' <6>PNP: PS/2 Controller [PNP0303:KBD0,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 <6>i8042.c: Detected active multiplexing controller, rev 1.1. <6>serio: i8042 KBD port at 0x60,0x64 irq 1 <6>serio: i8042 AUX0 port at 0x60,0x64 irq 12 <6>serio: i8042 AUX1 port at 0x60,0x64 irq 12 <6>serio: i8042 AUX2 port at 0x60,0x64 irq 12 <6>serio: i8042 AUX3 port at 0x60,0x64 irq 12 <6>mice: PS/2 mouse device common for all mice <6>input: PC Speaker as /class/input/input0 <6>TCP cubic registered <6>NET: Registered protocol family 1 <6>Freeing unused kernel memory: 220k freed <6>Synaptics Touchpad, model: 1, fw: 6.2, id: 0x1a0b1, caps: 0xa04713/0x200000 <6>input: SynPS/2 Synaptics TouchPad as /class/input/input1 <6>input: AT Translated Set 2 keyboard as /class/input/input2 <6>Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 <6>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx <5>SCSI subsystem initialized <6>ACPI: Processor [CPU0] (supports 8 throttling states) <6>ACPI: Processor [CPU1] (supports 8 throttling states) <6>ACPI: Thermal Zone [TZS0] (54 C) <6>ACPI: Thermal Zone [TZS1] (57 C) ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 - problem with cpuidle routine 2007-03-21 18:49 ` 2.6.21-rc4-mm1 - problem with cpuidle routine Larry Finger @ 2007-03-21 20:38 ` Andrew Morton 2007-03-22 0:33 ` Venkatesh Pallipadi 2007-03-21 20:39 ` 2.6.21-rc4-mm1 " Venki Pallipadi 1 sibling, 1 reply; 146+ messages in thread From: Andrew Morton @ 2007-03-21 20:38 UTC (permalink / raw) To: Larry Finger; +Cc: LKML, Venkatesh Pallipadi, linux-acpi On Wed, 21 Mar 2007 13:49:58 -0500 Larry Finger <larry.finger@lwfinger.net> wrote: > When I configure 'CPU Idle PM Support' on my HP dv2125nr notebook with a Turion X64 X2 processor and > X86_64 architecture selected, the computer freezes on bootup. I have included a portion the > configuration file and part of /var/log/boot.msg for my working system. Please let me know if > further info from my system is required. I would be happy to test any patches, etc. > > Larry > > ============================================================== > > The console log ends with the following entries: > > ACPI: Processor [CPU0] (supports 8 throttling states) > ACPI: Processor [CPU1] (supports 8 throttling states) > cpuidle: driver acpi_idle failed to attach to cpu 0 > cpuidle: driver acpi_idle failed to attach to cpu 0 > cpuidle: using driver acpi_idle > Loading thermal > > At this point, the system hangs. > > ================================================= > > The beginning section of my .config is as follows: > Thanks. Cc's added.. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 - problem with cpuidle routine 2007-03-21 20:38 ` Andrew Morton @ 2007-03-22 0:33 ` Venkatesh Pallipadi 2007-03-30 1:25 ` 2.6.21-rc4-mm1 and rc5-mm2 " Ed Sweetman 0 siblings, 1 reply; 146+ messages in thread From: Venkatesh Pallipadi @ 2007-03-22 0:33 UTC (permalink / raw) To: Andrew Morton; +Cc: Larry Finger, LKML, Len Brown, linux-acpi On Wed, Mar 21, 2007 at 01:38:15PM -0700, Andrew Morton wrote: > On Wed, 21 Mar 2007 13:49:58 -0500 > Larry Finger <larry.finger@lwfinger.net> wrote: > > > When I configure 'CPU Idle PM Support' on my HP dv2125nr notebook with a Turion X64 X2 processor and > > X86_64 architecture selected, the computer freezes on bootup. I have included a portion the > > configuration file and part of /var/log/boot.msg for my working system. Please let me know if > > further info from my system is required. I would be happy to test any patches, etc. > > > > Larry > > > > ============================================================== > > > > The console log ends with the following entries: > > > > ACPI: Processor [CPU0] (supports 8 throttling states) > > ACPI: Processor [CPU1] (supports 8 throttling states) > > cpuidle: driver acpi_idle failed to attach to cpu 0 > > cpuidle: driver acpi_idle failed to attach to cpu 0 > > cpuidle: using driver acpi_idle > > Loading thermal > > > > At this point, the system hangs. > > > > ================================================= > > > > The beginning section of my .config is as follows: > > > > Thanks. Cc's added.. Patch below resolves this issue. Patch for cpuidle boot hang reported by Larry Finger here. http://www.ussg.iu.edu/hypermail/linux/kernel/0703.2/2025.html Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com> Index: new/drivers/cpuidle/cpuidle.c =================================================================== --- new.orig/drivers/cpuidle/cpuidle.c 2007-03-21 14:25:11.000000000 -0800 +++ new/drivers/cpuidle/cpuidle.c 2007-03-21 14:25:33.000000000 -0800 @@ -119,6 +119,7 @@ dev = &per_cpu(cpuidle_devices, cpu); + dev->cpu = cpu; mutex_lock(&cpuidle_lock); if (cpu_is_offline(cpu)) { mutex_unlock(&cpuidle_lock); @@ -129,15 +130,26 @@ mutex_unlock(&cpuidle_lock); return 0; } - dev->status |= CPUIDLE_STATUS_DETECTED; - list_add(&dev->device_list, &cpuidle_detected_devices); - cpuidle_add_sysfs(sys_dev); - if (cpuidle_curr_driver) - cpuidle_attach_driver(dev); - if (cpuidle_curr_governor) - cpuidle_attach_governor(dev); + if (cpuidle_curr_driver) { + if (cpuidle_attach_driver(dev)) + goto err_ret; + } + + if (cpuidle_curr_governor) { + if (cpuidle_attach_governor(dev)) { + cpuidle_detach_driver(dev); + goto err_ret; + } + } + if (cpuidle_device_can_idle(dev)) cpuidle_install_idle_handler(); + + list_add(&dev->device_list, &cpuidle_detected_devices); + cpuidle_add_sysfs(sys_dev); + dev->status |= CPUIDLE_STATUS_DETECTED; + +err_ret: mutex_unlock(&cpuidle_lock); return 0; Index: new/drivers/cpuidle/driver.c =================================================================== --- new.orig/drivers/cpuidle/driver.c 2007-03-21 14:25:15.000000000 -0800 +++ new/drivers/cpuidle/driver.c 2007-03-21 14:25:53.000000000 -0800 @@ -37,7 +37,7 @@ ret = cpuidle_curr_driver->init(dev); if (ret) { module_put(cpuidle_curr_driver->owner); - printk(KERN_ERROR "cpuidle: driver %s failed to attach to cpu %d\n", + printk(KERN_INFO "cpuidle: driver %s failed to attach to cpu %d\n", cpuidle_curr_driver->name, dev->cpu); } else { if (dev->status & CPUIDLE_STATUS_GOVERNOR_ATTACHED) ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 and rc5-mm2 - problem with cpuidle routine 2007-03-22 0:33 ` Venkatesh Pallipadi @ 2007-03-30 1:25 ` Ed Sweetman 2007-03-30 2:17 ` Lee Revell 0 siblings, 1 reply; 146+ messages in thread From: Ed Sweetman @ 2007-03-30 1:25 UTC (permalink / raw) To: Venkatesh Pallipadi Cc: Andrew Morton, Larry Finger, LKML, Len Brown, linux-acpi [-- Attachment #1: Type: text/plain, Size: 3827 bytes --] I have an athlon64 X2 system that freezes just after loading the cpuidle ladder governer. No output about not being able to attach, just the driver string and then nothing. I've attached my lspci output, .config and dmesg output of the same kernel without cpuidle. Any further info just ask. I'm guessing this patch isn't in 2.6.21-rc5-mm2 ...either that or i'm having a separate problem. Venkatesh Pallipadi wrote: > On Wed, Mar 21, 2007 at 01:38:15PM -0700, Andrew Morton wrote: > >> On Wed, 21 Mar 2007 13:49:58 -0500 >> Larry Finger <larry.finger@lwfinger.net> wrote: >> >> >>> When I configure 'CPU Idle PM Support' on my HP dv2125nr notebook with a Turion X64 X2 processor and >>> X86_64 architecture selected, the computer freezes on bootup. I have included a portion the >>> configuration file and part of /var/log/boot.msg for my working system. Please let me know if >>> further info from my system is required. I would be happy to test any patches, etc. >>> >>> Larry >>> >>> ============================================================== >>> >>> The console log ends with the following entries: >>> >>> ACPI: Processor [CPU0] (supports 8 throttling states) >>> ACPI: Processor [CPU1] (supports 8 throttling states) >>> cpuidle: driver acpi_idle failed to attach to cpu 0 >>> cpuidle: driver acpi_idle failed to attach to cpu 0 >>> cpuidle: using driver acpi_idle >>> Loading thermal >>> >>> At this point, the system hangs. >>> >>> ================================================= >>> >>> The beginning section of my .config is as follows: >>> >>> >> Thanks. Cc's added.. >> > > Patch below resolves this issue. > > > Patch for cpuidle boot hang reported by Larry Finger here. > http://www.ussg.iu.edu/hypermail/linux/kernel/0703.2/2025.html > > Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com> > > Index: new/drivers/cpuidle/cpuidle.c > =================================================================== > --- new.orig/drivers/cpuidle/cpuidle.c 2007-03-21 14:25:11.000000000 -0800 > +++ new/drivers/cpuidle/cpuidle.c 2007-03-21 14:25:33.000000000 -0800 > @@ -119,6 +119,7 @@ > > dev = &per_cpu(cpuidle_devices, cpu); > > + dev->cpu = cpu; > mutex_lock(&cpuidle_lock); > if (cpu_is_offline(cpu)) { > mutex_unlock(&cpuidle_lock); > @@ -129,15 +130,26 @@ > mutex_unlock(&cpuidle_lock); > return 0; > } > - dev->status |= CPUIDLE_STATUS_DETECTED; > - list_add(&dev->device_list, &cpuidle_detected_devices); > - cpuidle_add_sysfs(sys_dev); > - if (cpuidle_curr_driver) > - cpuidle_attach_driver(dev); > - if (cpuidle_curr_governor) > - cpuidle_attach_governor(dev); > + if (cpuidle_curr_driver) { > + if (cpuidle_attach_driver(dev)) > + goto err_ret; > + } > + > + if (cpuidle_curr_governor) { > + if (cpuidle_attach_governor(dev)) { > + cpuidle_detach_driver(dev); > + goto err_ret; > + } > + } > + > if (cpuidle_device_can_idle(dev)) > cpuidle_install_idle_handler(); > + > + list_add(&dev->device_list, &cpuidle_detected_devices); > + cpuidle_add_sysfs(sys_dev); > + dev->status |= CPUIDLE_STATUS_DETECTED; > + > +err_ret: > mutex_unlock(&cpuidle_lock); > > return 0; > Index: new/drivers/cpuidle/driver.c > =================================================================== > --- new.orig/drivers/cpuidle/driver.c 2007-03-21 14:25:15.000000000 -0800 > +++ new/drivers/cpuidle/driver.c 2007-03-21 14:25:53.000000000 -0800 > @@ -37,7 +37,7 @@ > ret = cpuidle_curr_driver->init(dev); > if (ret) { > module_put(cpuidle_curr_driver->owner); > - printk(KERN_ERROR "cpuidle: driver %s failed to attach to cpu %d\n", > + printk(KERN_INFO "cpuidle: driver %s failed to attach to cpu %d\n", > cpuidle_curr_driver->name, dev->cpu); > } else { > if (dev->status & CPUIDLE_STATUS_GOVERNOR_ATTACHED) > - > [-- Attachment #2: config-output --] [-- Type: text/plain, Size: 35385 bytes --] # # Automatically generated make config: don't edit # Linux kernel version: 2.6.21-rc5-mm2 # Thu Mar 29 20:52:27 2007 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_ZONE_DMA32=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_DMI=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set # CONFIG_SWAP is not set CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # CONFIG_UTS_NS is not set # CONFIG_AUDIT is not set # CONFIG_IKCONFIG is not set # CONFIG_CPUSETS is not set # CONFIG_SYSFS_DEPRECATED is not set # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set # CONFIG_PAGE_GROUP_BY_MOBILITY is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_MODVERSIONS=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Process debugging support # CONFIG_UTRACE=y CONFIG_PTRACE=y # # Block layer # CONFIG_BLOCK=y # CONFIG_BLK_DEV_IO_TRACE is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y # CONFIG_IOSCHED_DEADLINE is not set # CONFIG_IOSCHED_CFQ is not set CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="anticipatory" # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_VSMP is not set CONFIG_MK8=y # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y # CONFIG_MICROCODE is not set CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_MTRR=y CONFIG_SMP=y # CONFIG_SCHED_SMT is not set CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y # CONFIG_NUMA is not set CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_RESOURCES_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_ADAPTIVE_READAHEAD=y CONFIG_NR_CPUS=2 # CONFIG_HOTPLUG_CPU is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_HPET_TIMER=y # CONFIG_HPET_EMULATE_RTC is not set CONFIG_IOMMU=y # CONFIG_CALGARY_IOMMU is not set CONFIG_SWIOTLB=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_INTEL is not set CONFIG_X86_MCE_AMD=y # CONFIG_KEXEC is not set # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x200000 CONFIG_SECCOMP=y # CONFIG_CC_STACKPROTECTOR is not set # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set CONFIG_HZ_300=y # CONFIG_HZ_1000 is not set CONFIG_HZ=300 CONFIG_REORDER=y CONFIG_K8_NB=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_ISA_DMA_API=y CONFIG_GENERIC_PENDING_IRQ=y # # Power management options # CONFIG_PM=y # CONFIG_PM_LEGACY is not set # CONFIG_PM_DEBUG is not set # CONFIG_PM_SYSFS_DEPRECATED is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y # CONFIG_ACPI_PROCFS is not set # CONFIG_ACPI_AC is not set # CONFIG_ACPI_BATTERY is not set # CONFIG_ACPI_BUTTON is not set # CONFIG_ACPI_FAN is not set # CONFIG_ACPI_DOCK is not set CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_TOSHIBA is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y CONFIG_ACPI_CONTAINER=y # CONFIG_ACPI_SBS is not set # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y # CONFIG_CPU_FREQ_DEBUG is not set # CONFIG_CPU_FREQ_STAT is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y # CONFIG_CPU_FREQ_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_GOV_POWERSAVE is not set CONFIG_CPU_FREQ_GOV_USERSPACE=y # CONFIG_CPU_FREQ_GOV_ONDEMAND is not set CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y # # CPUFreq processor drivers # CONFIG_X86_POWERNOW_K8=y CONFIG_X86_POWERNOW_K8_ACPI=y # CONFIG_X86_SPEEDSTEP_CENTRINO is not set # CONFIG_X86_ACPI_CPUFREQ is not set # # shared options # # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set # CONFIG_X86_SPEEDSTEP_LIB is not set # # CPU idle PM support # # CONFIG_CPU_IDLE is not set # # Bus options (PCI etc.) # CONFIG_PCI=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y # CONFIG_PCI_DOMAINS is not set CONFIG_PCIEPORTBUS=y CONFIG_PCIEAER=y CONFIG_PCI_MSI=y CONFIG_HT_IRQ=y # # PCCARD (PCMCIA/CardBus) support # # CONFIG_PCCARD is not set # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=m CONFIG_IA32_EMULATION=y CONFIG_IA32_AOUT=y CONFIG_COMPAT=y CONFIG_SYSVIPC_COMPAT=y # # Networking # CONFIG_NET=y # # Networking options # # CONFIG_NETDEBUG is not set CONFIG_PACKET=m CONFIG_PACKET_MMAP=y CONFIG_UNIX=m CONFIG_XFRM=y CONFIG_XFRM_USER=m # CONFIG_XFRM_SUB_POLICY is not set # CONFIG_XFRM_MIGRATE is not set CONFIG_NET_KEY=m # CONFIG_NET_KEY_MIGRATE is not set CONFIG_INET=y CONFIG_IP_MULTICAST=y # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_FIB_HASH=y # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_IP_MROUTE 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_XFRM_TUNNEL is not set # CONFIG_INET_TUNNEL is not set # CONFIG_INET_XFRM_MODE_TRANSPORT is not set # CONFIG_INET_XFRM_MODE_TUNNEL is not set # CONFIG_INET_XFRM_MODE_BEET is not set # CONFIG_INET_DIAG is not set # CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_CUBIC=y CONFIG_DEFAULT_TCP_CONG="cubic" # CONFIG_TCP_MD5SIG is not set # CONFIG_IPV6 is not set # CONFIG_INET6_XFRM_TUNNEL is not set # CONFIG_INET6_TUNNEL is not set # CONFIG_NETWORK_SECMARK 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 # # TIPC Configuration (EXPERIMENTAL) # # CONFIG_TIPC 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_ECONET is not set # CONFIG_WAN_ROUTER is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED 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 # # Wireless # # CONFIG_CFG80211 is not set # CONFIG_WIRELESS_EXT is not set # CONFIG_MAC80211 is not set # CONFIG_IEEE80211 is not set # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y # CONFIG_PREVENT_FIRMWARE_BUILD is not set CONFIG_FW_LOADER=m # CONFIG_SYS_HYPERVISOR 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 # CONFIG_PNP=y # CONFIG_PNP_DEBUG is not set # # Protocols # CONFIG_PNPACPI=y # # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=m # CONFIG_BLK_DEV_CRYPTOLOOP is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set # CONFIG_BLK_DEV_UB is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_CDROM_PKTCDVD is not set # CONFIG_ATA_OVER_ETH is not set # # Misc devices # # CONFIG_IBM_ASM is not set # CONFIG_SGI_IOC4 is not set # CONFIG_TIFM_CORE is not set # CONFIG_SONY_LAPTOP is not set # CONFIG_ACPI_IBM is not set # # ATA/ATAPI/MFM/RLL support # # CONFIG_IDE is not set # # SCSI device support # CONFIG_RAID_ATTRS=m CONFIG_SCSI=y # CONFIG_SCSI_TGT is not set # CONFIG_SCSI_NETLINK is not set # CONFIG_SCSI_PROC_FS is not set # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set CONFIG_BLK_DEV_SR=y # CONFIG_BLK_DEV_SR_VENDOR is not set CONFIG_CHR_DEV_SG=y # CONFIG_CHR_DEV_SCH is not set # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # CONFIG_SCSI_MULTI_LUN=y # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set CONFIG_SCSI_SCAN_ASYNC=y CONFIG_SCSI_WAIT_SCAN=m # # SCSI Transports # # CONFIG_SCSI_SPI_ATTRS is not set # CONFIG_SCSI_FC_ATTRS is not set # CONFIG_SCSI_ISCSI_ATTRS is not set # CONFIG_SCSI_SAS_ATTRS is not set # CONFIG_SCSI_SAS_LIBSAS is not set # # SCSI low-level drivers # # CONFIG_ISCSI_TCP is not set # CONFIG_BLK_DEV_3W_XXXX_RAID is not set # CONFIG_SCSI_3W_9XXX is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AACRAID is not set # CONFIG_SCSI_AIC7XXX is not set # CONFIG_SCSI_AIC7XXX_OLD is not set # CONFIG_SCSI_AIC79XX is not set # CONFIG_SCSI_AIC94XX is not set # CONFIG_SCSI_ARCMSR is not set # CONFIG_MEGARAID_NEWGEN is not set # CONFIG_MEGARAID_LEGACY is not set # CONFIG_MEGARAID_SAS is not set # CONFIG_SCSI_HPTIOP is not set # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_IPS is not set # CONFIG_SCSI_INITIO is not set # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_STEX is not set # CONFIG_SCSI_SYM53C8XX_2 is not set # CONFIG_SCSI_IPR is not set # CONFIG_SCSI_QLOGIC_1280 is not set # CONFIG_SCSI_QLA_FC is not set # CONFIG_SCSI_QLA_ISCSI is not set # CONFIG_SCSI_LPFC is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_DEBUG is not set # CONFIG_SCSI_SRP is not set # # Serial ATA (prod) and Parallel ATA (experimental) drivers # CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set # CONFIG_SATA_AHCI is not set # CONFIG_SATA_SVW is not set # CONFIG_ATA_PIIX is not set # CONFIG_SATA_MV is not set CONFIG_SATA_NV=y # CONFIG_PDC_ADMA is not set # CONFIG_SATA_QSTOR is not set # CONFIG_SATA_PROMISE is not set # CONFIG_SATA_SX4 is not set # CONFIG_SATA_SIL is not set # CONFIG_SATA_SIL24 is not set # CONFIG_SATA_SIS is not set # CONFIG_SATA_ULI is not set # CONFIG_SATA_VIA is not set # CONFIG_SATA_VITESSE is not set # CONFIG_SATA_INIC162X is not set CONFIG_SATA_ACPI=y # CONFIG_PATA_ACPI is not set # CONFIG_PATA_ALI is not set CONFIG_PATA_AMD=y # CONFIG_PATA_ARTOP is not set # CONFIG_PATA_ATIIXP is not set # CONFIG_PATA_CMD640_PCI is not set # CONFIG_PATA_CMD64X is not set # CONFIG_PATA_CS5520 is not set # CONFIG_PATA_CS5530 is not set # CONFIG_PATA_CYPRESS is not set # CONFIG_PATA_EFAR is not set # CONFIG_ATA_GENERIC is not set # CONFIG_PATA_HPT366 is not set # CONFIG_PATA_HPT37X is not set # CONFIG_PATA_HPT3X2N is not set # CONFIG_PATA_HPT3X3 is not set # CONFIG_PATA_IT821X is not set # CONFIG_PATA_IT8213 is not set # CONFIG_PATA_JMICRON is not set # CONFIG_PATA_TRIFLEX is not set # CONFIG_PATA_MARVELL is not set # CONFIG_PATA_MPIIX is not set # CONFIG_PATA_OLDPIIX is not set # CONFIG_PATA_NETCELL is not set # CONFIG_PATA_NS87410 is not set # CONFIG_PATA_OPTI is not set # CONFIG_PATA_OPTIDMA is not set # CONFIG_PATA_PDC_OLD is not set # CONFIG_PATA_RADISYS is not set # CONFIG_PATA_RZ1000 is not set # CONFIG_PATA_SC1200 is not set # CONFIG_PATA_SERVERWORKS is not set # CONFIG_PATA_PDC2027X is not set # CONFIG_PATA_SIL680 is not set # CONFIG_PATA_SIS is not set # CONFIG_PATA_VIA is not set # CONFIG_PATA_WINBOND is not set # # Multi-device support (RAID and LVM) # CONFIG_MD=y CONFIG_BLK_DEV_MD=y # CONFIG_MD_LINEAR is not set CONFIG_MD_RAID0=y # CONFIG_MD_RAID1 is not set # CONFIG_MD_RAID10 is not set # CONFIG_MD_RAID456 is not set # CONFIG_MD_MULTIPATH is not set CONFIG_MD_FAULTY=m # CONFIG_BLK_DEV_DM is not set # # Fusion MPT device support # # CONFIG_FUSION is not set # CONFIG_FUSION_SPI is not set # CONFIG_FUSION_FC is not set # CONFIG_FUSION_SAS is not set # # IEEE 1394 (FireWire) support # # CONFIG_FIREWIRE is not set # CONFIG_IEEE1394 is not set # # I2O device support # # CONFIG_I2O is not set # # Macintosh device drivers # # CONFIG_MAC_EMUMOUSEBTN is not set # # Network device support # CONFIG_NETDEVICES=y # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # CONFIG_NET_SB1000 is not set # # ARCnet devices # CONFIG_ARCNET=m CONFIG_ARCNET_1201=m CONFIG_ARCNET_1051=m CONFIG_ARCNET_RAW=m # CONFIG_ARCNET_CAP is not set CONFIG_ARCNET_COM90xx=m CONFIG_ARCNET_COM90xxIO=m CONFIG_ARCNET_RIM_I=m CONFIG_ARCNET_COM20020=m CONFIG_ARCNET_COM20020_PCI=m # # PHY device support # CONFIG_PHYLIB=y # # MII PHY device drivers # CONFIG_MARVELL_PHY=y # CONFIG_DAVICOM_PHY is not set # CONFIG_QSEMI_PHY is not set # CONFIG_LXT_PHY is not set # CONFIG_CICADA_PHY is not set # CONFIG_VITESSE_PHY is not set # CONFIG_SMSC_PHY is not set # CONFIG_BROADCOM_PHY is not set # CONFIG_FIXED_PHY is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y CONFIG_MII=m # CONFIG_HAPPYMEAL is not set # CONFIG_SUNGEM is not set # CONFIG_CASSINI is not set # CONFIG_NET_VENDOR_3COM is not set # # Tulip family network device support # # CONFIG_NET_TULIP is not set # CONFIG_HP100 is not set CONFIG_NET_PCI=y # CONFIG_PCNET32 is not set # CONFIG_AMD8111_ETH is not set # CONFIG_ADAPTEC_STARFIRE is not set # CONFIG_B44 is not set CONFIG_FORCEDETH=y # CONFIG_FORCEDETH_NAPI is not set # CONFIG_DGRS is not set # CONFIG_EEPRO100 is not set # CONFIG_E100 is not set # CONFIG_FEALNX is not set # CONFIG_NATSEMI is not set # CONFIG_NE2K_PCI is not set # CONFIG_8139CP is not set # CONFIG_8139TOO is not set # CONFIG_SIS900 is not set # CONFIG_EPIC100 is not set # CONFIG_SUNDANCE is not set # CONFIG_VIA_RHINE is not set # CONFIG_SC92031 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=m # CONFIG_R8169_NAPI is not set # CONFIG_SIS190 is not set # CONFIG_SKGE is not set # CONFIG_SKY2 is not set CONFIG_SK98LIN=m # CONFIG_VIA_VELOCITY is not set # CONFIG_TIGON3 is not set # CONFIG_BNX2 is not set # CONFIG_QLA3XXX is not set # CONFIG_ATL1 is not set # # Ethernet (10000 Mbit) # # CONFIG_CHELSIO_T1 is not set # CONFIG_CHELSIO_T3 is not set # CONFIG_IXGB is not set # CONFIG_S2IO is not set # CONFIG_MYRI10GE is not set # CONFIG_NETXEN_NIC is not set # CONFIG_VIOC is not set # # Token Ring devices # # CONFIG_TR is not set # # Wireless LAN # # CONFIG_WLAN_PRE80211 is not set # CONFIG_WLAN_80211 is not set # CONFIG_RTL818X 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_NET_FC is not set # CONFIG_SHAPER is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL 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 # CONFIG_INPUT_FF_MEMLESS is not set # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1280 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1024 # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_TSDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set # CONFIG_KEYBOARD_STOWAWAY is not set CONFIG_INPUT_MOUSE=y # CONFIG_MOUSE_PS2 is not set # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set CONFIG_INPUT_MISC=y # CONFIG_INPUT_PCSPKR is not set # CONFIG_INPUT_ATLAS_BTNS is not set CONFIG_INPUT_UINPUT=y # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y # CONFIG_SERIO_SERPORT is not set # CONFIG_SERIO_CT82C710 is not set # CONFIG_SERIO_PCIPS2 is not set CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_VT_HW_CONSOLE_BINDING is not set # CONFIG_SERIAL_NONSTANDARD is not set # CONFIG_NOZOMI is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set # # Non-8250 serial port support # # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 # # IPMI # CONFIG_IPMI_HANDLER=m # CONFIG_IPMI_PANIC_EVENT is not set CONFIG_IPMI_DEVICE_INTERFACE=m CONFIG_IPMI_SI=m CONFIG_IPMI_WATCHDOG=m # CONFIG_IPMI_POWEROFF is not set # # Watchdog Cards # CONFIG_WATCHDOG=y # CONFIG_WATCHDOG_NOWAYOUT is not set # # Watchdog Device Drivers # CONFIG_SOFT_WATCHDOG=y # CONFIG_ACQUIRE_WDT is not set # CONFIG_ADVANTECH_WDT is not set # CONFIG_ALIM1535_WDT is not set # CONFIG_ALIM7101_WDT is not set # CONFIG_SC520_WDT is not set # CONFIG_EUROTECH_WDT is not set # CONFIG_IB700_WDT is not set # CONFIG_IBMASR is not set # CONFIG_WAFER_WDT is not set # CONFIG_I6300ESB_WDT is not set # CONFIG_I8XX_TCO is not set # CONFIG_ITCO_WDT is not set # CONFIG_SC1200_WDT is not set # CONFIG_PC87413_WDT is not set # CONFIG_60XX_WDT is not set # CONFIG_SBC8360_WDT is not set # CONFIG_CPU5_WDT is not set # CONFIG_SMSC37B787_WDT is not set # CONFIG_W83627HF_WDT is not set # CONFIG_W83697HF_WDT is not set # CONFIG_W83877F_WDT is not set # CONFIG_W83977F_WDT is not set # CONFIG_MACHZ_WDT is not set # CONFIG_SBC_EPX_C3_WATCHDOG is not set # # PCI-based Watchdog Cards # # CONFIG_PCIPCWATCHDOG is not set # CONFIG_WDTPCI is not set # # USB-based Watchdog Cards # # CONFIG_USBPCWATCHDOG is not set # CONFIG_HW_RANDOM is not set # CONFIG_NVRAM is not set CONFIG_RTC=y # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set CONFIG_AGP=y CONFIG_AGP_AMD64=y # CONFIG_AGP_INTEL is not set # CONFIG_AGP_SIS is not set # CONFIG_AGP_VIA is not set CONFIG_DRM=m # CONFIG_DRM_TDFX is not set # CONFIG_DRM_R128 is not set # CONFIG_DRM_RADEON is not set # CONFIG_DRM_MGA is not set # CONFIG_DRM_SIS is not set # CONFIG_DRM_VIA is not set # CONFIG_DRM_SAVAGE is not set # CONFIG_MWAVE is not set # CONFIG_PC8736x_GPIO is not set # CONFIG_RAW_DRIVER is not set # CONFIG_HPET is not set CONFIG_HANGCHECK_TIMER=m # # TPM devices # # CONFIG_TCG_TPM is not set # CONFIG_TELCLOCK is not set # # I2C support # CONFIG_I2C=m CONFIG_I2C_BOARDINFO=y CONFIG_I2C_CHARDEV=m # # I2C Algorithms # CONFIG_I2C_ALGOBIT=m CONFIG_I2C_ALGOPCF=m CONFIG_I2C_ALGOPCA=m # # I2C Hardware Bus support # # CONFIG_I2C_ALI1535 is not set # CONFIG_I2C_ALI1563 is not set # CONFIG_I2C_ALI15X3 is not set # CONFIG_I2C_AMD756 is not set # CONFIG_I2C_AMD8111 is not set # CONFIG_I2C_I801 is not set # CONFIG_I2C_I810 is not set # CONFIG_I2C_PIIX4 is not set CONFIG_I2C_ISA=m CONFIG_I2C_NFORCE2=m # CONFIG_I2C_OCORES is not set # CONFIG_I2C_PARPORT_LIGHT is not set # CONFIG_I2C_PASEMI is not set # CONFIG_I2C_PROSAVAGE is not set # CONFIG_I2C_SAVAGE4 is not set # CONFIG_I2C_SIS5595 is not set # CONFIG_I2C_SIS630 is not set # CONFIG_I2C_SIS96X is not set # CONFIG_I2C_STUB is not set # CONFIG_I2C_VIA is not set # CONFIG_I2C_VIAPRO is not set # CONFIG_I2C_VOODOO3 is not set # # Miscellaneous I2C Chip support # # CONFIG_SENSORS_DS1337 is not set # CONFIG_SENSORS_DS1374 is not set CONFIG_SENSORS_EEPROM=m # CONFIG_SENSORS_PCF8574 is not set # CONFIG_SENSORS_PCA9539 is not set # CONFIG_SENSORS_PCF8591 is not set # CONFIG_SENSORS_MAX6875 is not set # CONFIG_SENSORS_TSL2550 is not set # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set # CONFIG_I2C_DEBUG_CHIP is not set # # SPI support # # CONFIG_SPI is not set # CONFIG_SPI_MASTER is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Hardware Monitoring support # CONFIG_HWMON=m CONFIG_HWMON_VID=m # CONFIG_SENSORS_ABITUGURU is not set # CONFIG_SENSORS_ADM1021 is not set # CONFIG_SENSORS_ADM1025 is not set # CONFIG_SENSORS_ADM1026 is not set # CONFIG_SENSORS_ADM1029 is not set # CONFIG_SENSORS_ADM1031 is not set # CONFIG_SENSORS_ADM9240 is not set CONFIG_SENSORS_K8TEMP=m # CONFIG_SENSORS_ASB100 is not set # CONFIG_SENSORS_ATXP1 is not set # CONFIG_SENSORS_DS1621 is not set # CONFIG_SENSORS_F71805F is not set # CONFIG_SENSORS_FSCHER is not set # CONFIG_SENSORS_FSCPOS is not set # CONFIG_SENSORS_GL518SM is not set # CONFIG_SENSORS_GL520SM is not set # CONFIG_SENSORS_CORETEMP is not set CONFIG_SENSORS_IT87=m # CONFIG_SENSORS_LM63 is not set # CONFIG_SENSORS_LM75 is not set # CONFIG_SENSORS_LM77 is not set # CONFIG_SENSORS_LM78 is not set # CONFIG_SENSORS_LM80 is not set # CONFIG_SENSORS_LM83 is not set # CONFIG_SENSORS_LM85 is not set # CONFIG_SENSORS_LM87 is not set # CONFIG_SENSORS_LM90 is not set # CONFIG_SENSORS_LM92 is not set # CONFIG_SENSORS_MAX1619 is not set # CONFIG_SENSORS_MAX6650 is not set # CONFIG_SENSORS_PC87360 is not set # CONFIG_SENSORS_PC87427 is not set # CONFIG_SENSORS_SIS5595 is not set # CONFIG_SENSORS_SMSC47M1 is not set # CONFIG_SENSORS_SMSC47M192 is not set # CONFIG_SENSORS_SMSC47B397 is not set # CONFIG_SENSORS_VIA686A is not set # CONFIG_SENSORS_VT1211 is not set # CONFIG_SENSORS_VT8231 is not set # CONFIG_SENSORS_W83781D is not set # CONFIG_SENSORS_W83791D is not set # CONFIG_SENSORS_W83792D is not set # CONFIG_SENSORS_W83793 is not set # CONFIG_SENSORS_W83L785TS is not set # CONFIG_SENSORS_W83627HF is not set # CONFIG_SENSORS_W83627EHF is not set # CONFIG_SENSORS_HDAPS is not set # CONFIG_SENSORS_APPLESMC is not set # CONFIG_HWMON_DEBUG_CHIP is not set # # Sonics Silicon Backplane # # CONFIG_SSB is not set # # Multifunction device drivers # # CONFIG_MFD_SM501 is not set # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # CONFIG_DVB is not set # CONFIG_USB_DABUSB is not set # # Graphics support # # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Display device support # # CONFIG_DISPLAY_SUPPORT is not set # CONFIG_FB is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_VGACON_SOFT_SCROLLBACK is not set CONFIG_VIDEO_SELECT=y CONFIG_DUMMY_CONSOLE=y # # Sound # CONFIG_SOUND=y # # Advanced Linux Sound Architecture # CONFIG_SND=y CONFIG_SND_TIMER=y CONFIG_SND_PCM=y # CONFIG_SND_SEQUENCER is not set CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=y CONFIG_SND_PCM_OSS=y CONFIG_SND_PCM_OSS_PLUGINS=y CONFIG_SND_RTCTIMER=y # CONFIG_SND_DYNAMIC_MINORS is not set # CONFIG_SND_SUPPORT_OLD_API is not set CONFIG_SND_VERBOSE_PROCFS=y # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set # # Generic devices # CONFIG_SND_AC97_CODEC=y # CONFIG_SND_DUMMY is not set # CONFIG_SND_MTPAV is not set # CONFIG_SND_SERIAL_U16550 is not set # CONFIG_SND_MPU401 is not set # # PCI devices # # CONFIG_SND_AD1889 is not set # CONFIG_SND_ALS300 is not set # CONFIG_SND_ALS4000 is not set # CONFIG_SND_ALI5451 is not set # CONFIG_SND_ATIIXP is not set # CONFIG_SND_ATIIXP_MODEM is not set # CONFIG_SND_AU8810 is not set # CONFIG_SND_AU8820 is not set # CONFIG_SND_AU8830 is not set # CONFIG_SND_AZT3328 is not set # CONFIG_SND_BT87X is not set # CONFIG_SND_CA0106 is not set # CONFIG_SND_CMIPCI is not set # CONFIG_SND_CS4281 is not set # CONFIG_SND_CS46XX is not set # CONFIG_SND_DARLA20 is not set # CONFIG_SND_GINA20 is not set # CONFIG_SND_LAYLA20 is not set # CONFIG_SND_DARLA24 is not set # CONFIG_SND_GINA24 is not set # CONFIG_SND_LAYLA24 is not set # CONFIG_SND_MONA is not set # CONFIG_SND_MIA is not set # CONFIG_SND_ECHO3G is not set # CONFIG_SND_INDIGO is not set # CONFIG_SND_INDIGOIO is not set # CONFIG_SND_INDIGODJ is not set # CONFIG_SND_EMU10K1 is not set # CONFIG_SND_EMU10K1X is not set # CONFIG_SND_ENS1370 is not set # CONFIG_SND_ENS1371 is not set # CONFIG_SND_ES1938 is not set # CONFIG_SND_ES1968 is not set # CONFIG_SND_FM801 is not set # CONFIG_SND_HDA_INTEL is not set # CONFIG_SND_HDSP is not set # CONFIG_SND_HDSPM is not set # CONFIG_SND_ICE1712 is not set # CONFIG_SND_ICE1724 is not set CONFIG_SND_INTEL8X0=y # CONFIG_SND_INTEL8X0M is not set # CONFIG_SND_KORG1212 is not set # CONFIG_SND_MAESTRO3 is not set # CONFIG_SND_MIXART is not set # CONFIG_SND_NM256 is not set # CONFIG_SND_PCXHR is not set # CONFIG_SND_RIPTIDE is not set # CONFIG_SND_RME32 is not set # CONFIG_SND_RME96 is not set # CONFIG_SND_RME9652 is not set # CONFIG_SND_SONICVIBES is not set # CONFIG_SND_TRIDENT is not set # CONFIG_SND_VIA82XX is not set # CONFIG_SND_VIA82XX_MODEM is not set # CONFIG_SND_VX222 is not set # CONFIG_SND_YMFPCI is not set # CONFIG_SND_AC97_POWER_SAVE is not set # # USB devices # # CONFIG_SND_USB_AUDIO is not set # CONFIG_SND_USB_USX2Y is not set # CONFIG_SND_USB_CAIAQ is not set # # SoC audio support # # CONFIG_SND_SOC is not set # # Open Sound System # # CONFIG_SOUND_PRIME is not set CONFIG_AC97_BUS=y # # HID Devices # CONFIG_HID=y # CONFIG_HID_DEBUG is not set # CONFIG_HIDRAW is not set # # USB Input Devices # CONFIG_USB_HID=y # CONFIG_USB_HIDINPUT_POWERBOOK is not set # CONFIG_HID_FF is not set # CONFIG_USB_HIDDEV is not set # # USB support # CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_USB=y # CONFIG_USB_DEBUG is not set # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y # CONFIG_USB_DEVICE_CLASS is not set CONFIG_USB_DYNAMIC_MINORS=y # CONFIG_USB_SUSPEND is not set # CONFIG_USB_OTG is not set # # USB Host Controller Drivers # CONFIG_USB_EHCI_HCD=y # CONFIG_USB_EHCI_SPLIT_ISO is not set CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_TT_NEWSCHED=y # CONFIG_USB_EHCI_BIG_ENDIAN_MMIO is not set # CONFIG_USB_ISP116X_HCD is not set CONFIG_USB_OHCI_HCD=y # CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set # CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set CONFIG_USB_OHCI_LITTLE_ENDIAN=y # CONFIG_USB_UHCI_HCD is not set # CONFIG_USB_SL811_HCD is not set # # USB Device Class drivers # # CONFIG_USB_ACM is not set # CONFIG_USB_PRINTER is not set # # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' # # # may also be needed; see USB_STORAGE Help for more information # CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_DPCM is not set # CONFIG_USB_STORAGE_USBAT is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_SDDR55 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # CONFIG_USB_STORAGE_ALAUDA is not set # CONFIG_USB_STORAGE_KARMA is not set # CONFIG_USB_LIBUSUAL is not set # # USB Input Devices # # CONFIG_USB_AIPTEK is not set # CONFIG_USB_WACOM is not set # CONFIG_USB_ACECAD is not set # CONFIG_USB_KBTAB is not set # CONFIG_USB_POWERMATE is not set # CONFIG_USB_TOUCHSCREEN is not set # CONFIG_USB_YEALINK is not set # CONFIG_USB_XPAD is not set # CONFIG_USB_ATI_REMOTE is not set # CONFIG_USB_ATI_REMOTE2 is not set # CONFIG_USB_KEYSPAN_REMOTE is not set # CONFIG_USB_APPLETOUCH is not set # CONFIG_USB_GTCO is not set # # USB Imaging devices # # CONFIG_USB_MDC800 is not set # CONFIG_USB_MICROTEK is not set # # USB Network Adapters # CONFIG_USB_CATC=m CONFIG_USB_KAWETH=m CONFIG_USB_PEGASUS=m CONFIG_USB_RTL8150=m CONFIG_USB_USBNET_MII=m CONFIG_USB_USBNET=m CONFIG_USB_NET_AX8817X=m CONFIG_USB_NET_CDCETHER=m # CONFIG_USB_NET_DM9601 is not set # CONFIG_USB_NET_GL620A is not set CONFIG_USB_NET_NET1080=m # CONFIG_USB_NET_PLUSB is not set # CONFIG_USB_NET_MCS7830 is not set # CONFIG_USB_NET_RNDIS_HOST is not set # CONFIG_USB_NET_CDC_SUBSET is not set CONFIG_USB_NET_ZAURUS=m # CONFIG_USB_MON is not set # # USB port drivers # # # USB Serial Converter support # # CONFIG_USB_SERIAL is not set # # USB Miscellaneous drivers # # CONFIG_USB_EMI62 is not set # CONFIG_USB_EMI26 is not set # CONFIG_USB_ADUTUX is not set # CONFIG_USB_AUERSWALD is not set # CONFIG_USB_RIO500 is not set # CONFIG_USB_LEGOTOWER is not set # CONFIG_USB_LCD is not set # CONFIG_USB_BERRY_CHARGE is not set # CONFIG_USB_LED is not set # CONFIG_USB_CYPRESS_CY7C63 is not set # CONFIG_USB_CYTHERM is not set # CONFIG_USB_PHIDGET is not set # CONFIG_USB_IDMOUSE is not set # CONFIG_USB_FTDI_ELAN is not set # CONFIG_USB_APPLEDISPLAY is not set # CONFIG_USB_SISUSBVGA is not set # CONFIG_USB_LD is not set # CONFIG_USB_TRANCEVIBRATOR is not set # CONFIG_USB_IOWARRIOR is not set # CONFIG_USB_TEST is not set # CONFIG_USB_GOTEMP is not set # # USB DSL modem support # # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # # CONFIG_MMC is not set # # LED devices # # CONFIG_NEW_LEDS is not set # # LED drivers # # # LED Triggers # # # InfiniBand support # # CONFIG_INFINIBAND is not set # # EDAC - error detection and reporting (RAS) (EXPERIMENTAL) # # CONFIG_EDAC is not set # # Real Time Clock # # CONFIG_RTC_CLASS is not set # # DMA Engine support # CONFIG_DMA_ENGINE=y # # DMA Clients # CONFIG_NET_DMA=y CONFIG_ASYNC_TX_DMA=y # # DMA Devices # # CONFIG_INTEL_IOATDMA is not set # # Auxiliary Display support # # # Virtualization # # CONFIG_KVM is not set # # Userspace I/O # # CONFIG_UIO is not set # # Firmware Drivers # CONFIG_EDD=m # CONFIG_DELL_RBU is not set # CONFIG_DCDBAS is not set # # File systems # # CONFIG_EXT2_FS is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y # CONFIG_EXT4DEV_FS is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISER4_FS is not set # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set CONFIG_FS_POSIX_ACL=y # CONFIG_XFS_FS is not set # CONFIG_GFS2_FS is not set # CONFIG_OCFS2_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_ROMFS_FS is not set CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y CONFIG_AUTOFS_FS=m CONFIG_AUTOFS4_FS=y # CONFIG_FUSE_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=m CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_UDF_FS=m CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=m CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" CONFIG_NTFS_FS=m # CONFIG_NTFS_DEBUG is not set # CONFIG_NTFS_RW is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_SYSCTL=y CONFIG_SYSFS=y CONFIG_TMPFS=y # CONFIG_TMPFS_POSIX_ACL is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # CONFIG_CONFIGFS_FS is not set # # Layered filesystems # # CONFIG_UNION_FS is not set # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_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 is not set # CONFIG_NFSD is not set # CONFIG_SMB_FS is not set CONFIG_CIFS=m # CONFIG_CIFS_STATS is not set # CONFIG_CIFS_WEAK_PW_HASH is not set CONFIG_CIFS_XATTR=y CONFIG_CIFS_POSIX=y # CONFIG_CIFS_DEBUG2 is not set CONFIG_CIFS_EXPERIMENTAL=y # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set # CONFIG_9P_FS is not set # # Partition Types # # CONFIG_PARTITION_ADVANCED is not set CONFIG_MSDOS_PARTITION=y # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="cp437" CONFIG_NLS_CODEPAGE_437=m # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 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=m # 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=m # # Distributed Lock Manager # # CONFIG_DLM is not set # # Instrumentation Support # # CONFIG_PROFILING is not set # CONFIG_KPROBES is not set # CONFIG_MARKERS is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # CONFIG_PRINTK_TIME is not set # CONFIG_ENABLE_MUST_CHECK is not set # CONFIG_MAGIC_SYSRQ is not set # CONFIG_UNUSED_SYMBOLS is not set # CONFIG_DEBUG_FS is not set # CONFIG_HEADERS_CHECK is not set # CONFIG_DEBUG_KERNEL is not set CONFIG_LOG_BUF_SHIFT=15 CONFIG_DEBUG_BUGVERBOSE=y # CONFIG_PROFILE_LIKELY is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_INTEGRITY is not set # CONFIG_SECURITY is not set # CONFIG_SECURITY_FILE_CAPABILITIES is not set # # Cryptographic options # # CONFIG_CRYPTO is not set # # Library routines # CONFIG_BITREVERSE=m CONFIG_CRC_CCITT=m CONFIG_CRC16=m CONFIG_CRC32=m CONFIG_CRC_ITU_T=m CONFIG_LIBCRC32C=m # CONFIG_EEPROM_93CX6 is not set CONFIG_ZLIB_INFLATE=m CONFIG_PLIST=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y [-- Attachment #3: lspci-output --] [-- Type: text/plain, Size: 7516 bytes --] 00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3) Subsystem: ASUSTeK Computer Inc. Unknown device 815a Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: [44] HyperTransport: Slave or Primary Interface Capabilities: [e0] HyperTransport: MSI Mapping 00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: bus master, 66MHz, fast devsel, latency 0 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: 66MHz, fast devsel, IRQ 255 I/O ports at e400 [size=32] I/O ports at 4c00 [size=64] I/O ports at 4c40 [size=64] Capabilities: [44] Power Management version 2 00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23 Memory at c8104000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 20 Memory at feb00000 (32-bit, non-prefetchable) [size=256] Capabilities: [44] Debug port Capabilities: [80] Power Management version 2 00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22 I/O ports at dc00 [size=256] I/O ports at e000 [size=256] Memory at c8103000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2) (prog-if 8a [Master SecP PriP]) Subsystem: Unknown device f043:815a Flags: bus master, 66MHz, fast devsel, latency 0 [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled] [size=8] [virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled] [size=1] [virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled] [size=8] [virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled] [size=1] I/O ports at f000 [size=16] Capabilities: [44] Power Management version 2 00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) (prog-if 85 [Master SecO PriO]) Subsystem: ASUSTeK Computer Inc. Unknown device 815a Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22 I/O ports at 09f0 [size=8] I/O ports at 0bf0 [size=4] I/O ports at 0970 [size=8] I/O ports at 0b70 [size=4] I/O ports at d800 [size=16] Memory at c8102000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) (prog-if 85 [Master SecO PriO]) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21 I/O ports at 09e0 [size=8] I/O ports at 0be0 [size=4] I/O ports at 0960 [size=8] I/O ports at 0b60 [size=4] I/O ports at c400 [size=16] Memory at c8101000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2) (prog-if 01 [Subtractive decode]) Flags: bus master, 66MHz, fast devsel, latency 0 Bus: primary=00, secondary=05, subordinate=05, sec-latency=128 Prefetchable memory behind bridge: c8000000-c80fffff 00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23 Memory at c8100000 (32-bit, non-prefetchable) [size=4K] I/O ports at b000 [size=8] Capabilities: [44] Power Management version 2 00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 Capabilities: [40] Power Management version 2 Capabilities: [48] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+ Capabilities: [58] HyperTransport: MSI Mapping Capabilities: [80] Express Root Port (Slot+) IRQ 0 Capabilities: [100] Virtual Channel 00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 Capabilities: [40] Power Management version 2 Capabilities: [48] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+ Capabilities: [58] HyperTransport: MSI Mapping Capabilities: [80] Express Root Port (Slot+) IRQ 0 Capabilities: [100] Virtual Channel 00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 Capabilities: [40] Power Management version 2 Capabilities: [48] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+ Capabilities: [58] HyperTransport: MSI Mapping Capabilities: [80] Express Root Port (Slot+) IRQ 0 Capabilities: [100] Virtual Channel 00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: c0000000-c7ffffff Prefetchable memory behind bridge: 00000000b0000000-00000000bfffffff Capabilities: [40] Power Management version 2 Capabilities: [48] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+ Capabilities: [58] HyperTransport: MSI Mapping Capabilities: [80] Express Root Port (Slot+) IRQ 0 Capabilities: [100] Virtual Channel 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration Flags: fast devsel Capabilities: [80] HyperTransport: Host or Secondary Interface 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map Flags: fast devsel 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller Flags: fast devsel 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control Flags: fast devsel 01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev a2) (prog-if 00 [VGA]) Subsystem: ASUSTeK Computer Inc. Unknown device 81b0 Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at c0000000 (32-bit, non-prefetchable) [size=64M] Memory at b0000000 (64-bit, prefetchable) [size=256M] Memory at c4000000 (64-bit, non-prefetchable) [size=16M] [virtual] Expansion ROM at c5000000 [disabled] [size=128K] Capabilities: [60] Power Management version 2 Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Capabilities: [78] Express Endpoint IRQ 0 Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting 05:08.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 02) Subsystem: Hauppauge computer works Inc. WinTV Series Flags: bus master, medium devsel, latency 32, IRQ 255 Memory at c8000000 (32-bit, prefetchable) [size=4K] 05:08.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 02) Subsystem: Hauppauge computer works Inc. WinTV Series Flags: bus master, medium devsel, latency 32, IRQ 255 Memory at c8001000 (32-bit, prefetchable) [size=4K] [-- Attachment #4: dmesg-output --] [-- Type: text/plain, Size: 23939 bytes --] Linux version 2.6.21-rc5-mm2 (root@psuedomode) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #3 SMP PREEMPT Thu Mar 29 20:56:38 EDT 2007 Command line: root=/dev/sda1 ro console=tty0 libata.atapi_enabled=1 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f400 (usable) BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000007fff0000 (usable) BIOS-e820: 000000007fff0000 - 000000007fff3000 (ACPI NVS) BIOS-e820: 000000007fff3000 - 0000000080000000 (ACPI data) BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved) Entering add_active_range(0, 0, 159) 0 entries of 256 used Entering add_active_range(0, 256, 524272) 1 entries of 256 used end_pfn_map = 1048576 DMI 2.3 present. ACPI: RSDP 000F7580, 0014 (r0 Nvidia) ACPI: RSDT 7FFF3040, 0034 (r1 Nvidia AWRDACPI 42302E31 AWRD 0) ACPI: FACP 7FFF30C0, 0074 (r1 Nvidia AWRDACPI 42302E31 AWRD 0) ACPI: DSDT 7FFF3180, 65F2 (r1 NVIDIA AWRDACPI 1000 MSFT 100000E) ACPI: FACS 7FFF0000, 0040 ACPI: SSDT 7FFF9880, 0188 (r1 PTLTD POWERNOW 1 LTP 1) ACPI: MCFG 7FFF9A80, 003C (r1 Nvidia AWRDACPI 42302E31 AWRD 0) ACPI: APIC 7FFF97C0, 007C (r1 Nvidia AWRDACPI 42302E31 AWRD 0) Entering add_active_range(0, 0, 159) 0 entries of 256 used Entering add_active_range(0, 256, 524272) 1 entries of 256 used sizeof(struct page) = 56 Zone PFN ranges: DMA 0 -> 4096 DMA32 4096 -> 1048576 Normal 1048576 -> 1048576 Movable zone start PFN for each node early_node_map[2] active PFN ranges 0: 0 -> 159 0: 256 -> 524272 On node 0 totalpages: 524175 Node 0 memmap at 0xffff810001000000 size 29360128 first pfn 0xffff810001000000 DMA zone: 56 pages used for memmap DMA zone: 989 pages reserved DMA zone: 2954 pages, LIFO batch:0 DMA32 zone: 7111 pages used for memmap DMA32 zone: 513065 pages, LIFO batch:31 Normal zone: 0 pages used for memmap Movable zone: 0 pages used for memmap Nvidia board detected. Ignoring ACPI timer override. If you got timer trouble try acpi_use_timer_override ACPI: PM-Timer IO Port: 0x4008 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 (Bootup-CPU) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Processor #1 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: BIOS IRQ0 pin2 override ignored. ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge) ACPI: IRQ9 used by override. ACPI: IRQ14 used by override. ACPI: IRQ15 used by override. Setting APIC routing to flat Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 88000000 (gap: 80000000:60000000) PERCPU: Allocating 32704 bytes of per cpu data Built 1 zonelists. Total pages: 516019 Kernel command line: root=/dev/sda1 ro console=tty0 libata.atapi_enabled=1 Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) Marking TSC unstable due to TSCs unsynchronized time.c: Detected 2010.324 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) Checking aperture... CPU 0: aperture @ 1600000000 size 32 MB Aperture too small (32 MB) No AGP bridge found Memory: 2060556k/2097088k available (2429k kernel code, 35868k reserved, 978k data, 220k init) Calibrating delay using timer specific routine.. 4023.72 BogoMIPS (lpj=6703564) Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 Freeing SMP alternatives: 24k freed ACPI: Core revision 20070126 Using local APIC timer interrupts. result 12564542 Detected 12.564 MHz APIC timer. Booting processor 1/2 APIC 0x1 Initializing CPU#1 Calibrating delay using timer specific routine.. 4021.89 BogoMIPS (lpj=6700633) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU: Physical Processor ID: 0 CPU: Processor Core ID: 1 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ stepping 02 Brought up 2 CPUs migration_cost=157 NET: Registered protocol family 16 ACPI: bus type pci registered PCI: Using MMCONFIG at e0000000 - efffffff PCI: No mmconfig possible on device 00:18 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) 0000:00:06.0: cannot adjust BAR0 (not I/O) 0000:00:06.0: cannot adjust BAR1 (not I/O) 0000:00:06.0: cannot adjust BAR2 (not I/O) 0000:00:06.0: cannot adjust BAR3 (not I/O) PCI: Transparent bridge - 0000:00:09.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 *5 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LMAC] (IRQs *3 4 5 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 *7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LSID] (IRQs 3 4 5 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LFID] (IRQs 3 4 *5 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [LPCA] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0, disabled. ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0, disabled. ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0 ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0, disabled. ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled. ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0 ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22 23) *0 ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0 ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0 ACPI: PCI Interrupt Link [APCP] (IRQs 20 21 22 23) *0, disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 9 devices Generic PHY: Registered new driver SCSI subsystem initialized libata version 2.20 loaded. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report pnp: 00:01: ioport range 0x4000-0x407f has been reserved pnp: 00:01: ioport range 0x4080-0x40ff has been reserved pnp: 00:01: ioport range 0x4400-0x447f has been reserved pnp: 00:01: ioport range 0x4480-0x44ff has been reserved pnp: 00:01: ioport range 0x4800-0x487f has been reserved pnp: 00:01: ioport range 0x4880-0x48ff has been reserved pnp: 00:07: iomem range 0xe0000000-0xefffffff has been reserved pnp: 00:08: iomem range 0xf0000-0xf3fff could not be reserved pnp: 00:08: iomem range 0xf4000-0xf7fff could not be reserved pnp: 00:08: iomem range 0xf8000-0xfbfff could not be reserved pnp: 00:08: iomem range 0xfc000-0xfffff could not be reserved Time: tsc clocksource has been installed. PCI: Bridge: 0000:00:09.0 IO window: disabled. MEM window: disabled. PREFETCH window: c8000000-c80fffff PCI: Bridge: 0000:00:0b.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Bridge: 0000:00:0c.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Bridge: 0000:00:0d.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Bridge: 0000:00:0e.0 IO window: disabled. MEM window: c0000000-c7ffffff PREFETCH window: b0000000-bfffffff PCI: Setting latency timer of device 0000:00:09.0 to 64 PCI: Setting latency timer of device 0000:00:0b.0 to 64 PCI: Setting latency timer of device 0000:00:0c.0 to 64 PCI: Setting latency timer of device 0000:00:0d.0 to 64 PCI: Setting latency timer of device 0000:00:0e.0 to 64 NET: Registered protocol family 2 Time: acpi_pm clocksource has been installed. IP route cache hash table entries: 65536 (order: 7, 524288 bytes) TCP established hash table entries: 131072 (order: 9, 3145728 bytes) TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered io scheduler noop registered io scheduler anticipatory registered (default) PCI: Linking AER extended capability on 0000:00:0b.0 PCI: Found disabled HT MSI Mapping on 0000:00:0b.0 PCI: Found enabled HT MSI Mapping on 0000:00:00.0 PCI: Linking AER extended capability on 0000:00:0c.0 PCI: Found disabled HT MSI Mapping on 0000:00:0c.0 PCI: Found enabled HT MSI Mapping on 0000:00:00.0 PCI: Linking AER extended capability on 0000:00:0d.0 PCI: Found disabled HT MSI Mapping on 0000:00:0d.0 PCI: Found enabled HT MSI Mapping on 0000:00:00.0 PCI: Linking AER extended capability on 0000:00:0e.0 PCI: Found disabled HT MSI Mapping on 0000:00:0e.0 PCI: Found enabled HT MSI Mapping on 0000:00:00.0 Boot video device is 0000:01:00.0 PCI: Setting latency timer of device 0000:00:0b.0 to 64 assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:0b.0:pcie00] Allocate Port Service[0000:00:0b.0:pcie03] PCI: Setting latency timer of device 0000:00:0c.0 to 64 assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:0c.0:pcie00] Allocate Port Service[0000:00:0c.0:pcie03] PCI: Setting latency timer of device 0000:00:0d.0 to 64 assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:0d.0:pcie00] Allocate Port Service[0000:00:0d.0:pcie03] PCI: Setting latency timer of device 0000:00:0e.0 to 64 assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:0e.0:pcie00] Allocate Port Service[0000:00:0e.0:pcie03] ACPI: Thermal Zone [THRM] (40 C) Real Time Clock Driver v1.12ac Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60 sec (nowayout= 0) Linux agpgart interface v0.102 (c) Dave Jones Marvell 88E1101: Registered new driver Marvell 88E1111: Registered new driver Marvell 88E1145: Registered new driver forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60. ACPI: PCI Interrupt Link [APCH] enabled at IRQ 23 ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [APCH] -> GSI 23 (level, low) -> IRQ 23 PCI: Setting latency timer of device 0000:00:0a.0 to 64 forcedeth: using HIGHDMA eth0: forcedeth.c: subsystem: 01043:8141 bound to 0000:00:0a.0 sata_nv 0000:00:07.0: version 3.3 ACPI: PCI Interrupt Link [APSI] enabled at IRQ 22 ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [APSI] -> GSI 22 (level, low) -> IRQ 22 sata_nv 0000:00:07.0: Using ADMA mode PCI: Setting latency timer of device 0000:00:07.0 to 64 ata1: SATA max UDMA/133 cmd 0xffffc20000012480 ctl 0xffffc200000124a0 bmdma 0x000000000001d800 irq 22 ata2: SATA max UDMA/133 cmd 0xffffc20000012580 ctl 0xffffc200000125a0 bmdma 0x000000000001d808 irq 22 scsi0 : sata_nv ata1: SATA link down (SStatus 0 SControl 300) scsi1 : sata_nv ata2: SATA link down (SStatus 0 SControl 300) ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 21 ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [APSJ] -> GSI 21 (level, low) -> IRQ 21 sata_nv 0000:00:08.0: Using ADMA mode PCI: Setting latency timer of device 0000:00:08.0 to 64 ata3: SATA max UDMA/133 cmd 0xffffc20000014480 ctl 0xffffc200000144a0 bmdma 0x000000000001c400 irq 21 ata4: SATA max UDMA/133 cmd 0xffffc20000014580 ctl 0xffffc200000145a0 bmdma 0x000000000001c408 irq 21 scsi2 : sata_nv ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: ATA-7: Maxtor 6L200S0, BACE1G10, max UDMA/133 ata3.00: 398297088 sectors, multi 1: LBA48 NCQ (depth 31/32) ata3.00: configured for UDMA/133 scsi3 : sata_nv ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata4.00: ATA-7: Maxtor 6L200S0, BACE1G10, max UDMA/133 ata4.00: 398297088 sectors, multi 1: LBA48 NCQ (depth 31/32) ata4.00: configured for UDMA/133 scsi 2:0:0:0: Direct-Access ATA Maxtor 6L200S0 BACE PQ: 0 ANSI: 5 ata3: bounce limit 0xFFFFFFFFFFFFFFFF, segment boundary 0xFFFFFFFF, hw segs 61 sd 2:0:0:0: [sda] 398297088 512-byte hardware sectors (203928 MB) sd 2:0:0:0: [sda] Write Protect is off sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 2:0:0:0: [sda] 398297088 512-byte hardware sectors (203928 MB) sd 2:0:0:0: [sda] Write Protect is off sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sd 2:0:0:0: [sda] Attached SCSI disk sd 2:0:0:0: Attached scsi generic sg0 type 0 scsi 3:0:0:0: Direct-Access ATA Maxtor 6L200S0 BACE PQ: 0 ANSI: 5 ata4: bounce limit 0xFFFFFFFFFFFFFFFF, segment boundary 0xFFFFFFFF, hw segs 61 sd 3:0:0:0: [sdb] 398297088 512-byte hardware sectors (203928 MB) sd 3:0:0:0: [sdb] Write Protect is off sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00 sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 3:0:0:0: [sdb] 398297088 512-byte hardware sectors (203928 MB) sd 3:0:0:0: [sdb] Write Protect is off sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00 sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdb: sdb1 sdb2 sd 3:0:0:0: [sdb] Attached SCSI disk sd 3:0:0:0: Attached scsi generic sg1 type 0 pata_amd 0000:00:06.0: version 0.3.8 PCI: Setting latency timer of device 0000:00:06.0 to 64 ata5: PATA max UDMA/133 cmd 0x00000000000101f0 ctl 0x00000000000103f6 bmdma 0x000000000001f000 irq 14 ata6: PATA max UDMA/133 cmd 0x0000000000010170 ctl 0x0000000000010376 bmdma 0x000000000001f008 irq 15 scsi4 : pata_amd ata5.00: ATA-7: Maxtor 6Y120P0, YAR41VW0, max UDMA/133 ata5.00: 240121728 sectors, multi 1: LBA ata5.01: ATA-5: WDC WD1000BB-00CAA0, 16.06V16, max UDMA/100 ata5.01: 195371568 sectors, multi 1: LBA ata5.00: configured for UDMA/133 ata5.01: configured for UDMA/100 scsi5 : pata_amd ata6.00: ATAPI, max MWDMA2 ata6.00: configured for MWDMA2 scsi 4:0:0:0: Direct-Access ATA Maxtor 6Y120P0 YAR4 PQ: 0 ANSI: 5 sd 4:0:0:0: [sdc] 240121728 512-byte hardware sectors (122942 MB) sd 4:0:0:0: [sdc] Write Protect is off sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00 sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 4:0:0:0: [sdc] 240121728 512-byte hardware sectors (122942 MB) sd 4:0:0:0: [sdc] Write Protect is off sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00 sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdc: sdc1 sd 4:0:0:0: [sdc] Attached SCSI disk sd 4:0:0:0: Attached scsi generic sg2 type 0 scsi 4:0:1:0: Direct-Access ATA WDC WD1000BB-00C 16.0 PQ: 0 ANSI: 5 sd 4:0:1:0: [sdd] 195371568 512-byte hardware sectors (100030 MB) sd 4:0:1:0: [sdd] Write Protect is off sd 4:0:1:0: [sdd] Mode Sense: 00 3a 00 00 sd 4:0:1:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 4:0:1:0: [sdd] 195371568 512-byte hardware sectors (100030 MB) sd 4:0:1:0: [sdd] Write Protect is off sd 4:0:1:0: [sdd] Mode Sense: 00 3a 00 00 sd 4:0:1:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdd: sdd1 sd 4:0:1:0: [sdd] Attached SCSI disk sd 4:0:1:0: Attached scsi generic sg3 type 0 scsi 5:0:0:0: CD-ROM PLEXTOR DVDR PX-712A 1.09 PQ: 0 ANSI: 5 sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 5:0:0:0: Attached scsi CD-ROM sr0 sr 5:0:0:0: Attached scsi generic sg4 type 5 ACPI: PCI Interrupt Link [APCL] enabled at IRQ 20 ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCL] -> GSI 20 (level, low) -> IRQ 20 PCI: Setting latency timer of device 0000:00:02.1 to 64 ehci_hcd 0000:00:02.1: EHCI Host Controller ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1 ehci_hcd 0000:00:02.1: debug port 1 PCI: cache line size of 64 is not supported by device 0000:00:02.1 ehci_hcd 0000:00:02.1: irq 20, io mem 0xfeb00000 ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb1: new device found, idVendor=0000, idProduct=0000 usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: EHCI Host Controller usb usb1: Manufacturer: Linux 2.6.21-rc5-mm2 ehci_hcd usb usb1: SerialNumber: 0000:00:02.1 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 10 ports detected ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver ACPI: PCI Interrupt Link [APCF] enabled at IRQ 23 ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 23 (level, low) -> IRQ 23 PCI: Setting latency timer of device 0000:00:02.0 to 64 ohci_hcd 0000:00:02.0: OHCI Host Controller ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2 ohci_hcd 0000:00:02.0: irq 23, io mem 0xc8104000 usb usb2: new device found, idVendor=0000, idProduct=0000 usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: OHCI Host Controller usb usb2: Manufacturer: Linux 2.6.21-rc5-mm2 ohci_hcd usb usb2: SerialNumber: 0000:00:02.0 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 10 ports detected PNP: No PS/2 controller found. Probing ports directly. serio: i8042 KBD port at 0x60,0x64 irq 1 serio: i8042 AUX port at 0x60,0x64 irq 12 mice: PS/2 mouse device common for all mice async_tx: api initialized (async) xor: automatically using best checksumming function: generic_sse generic_sse: 6381.600 MB/sec xor: using function: generic_sse (6381.600 MB/sec) md: raid0 personality registered for level 0 usb 2-3: new low speed USB device using ohci_hcd and address 2 usb 2-3: new device found, idVendor=1241, idProduct=1177 usb 2-3: new device strings: Mfr=0, Product=0, SerialNumber=0 usb 2-3: configuration #1 chosen from 1 choice usb 2-4: new low speed USB device using ohci_hcd and address 3 usb 2-4: new device found, idVendor=1267, idProduct=0103 usb 2-4: new device strings: Mfr=0, Product=0, SerialNumber=0 usb 2-4: configuration #1 chosen from 1 choice input: HID 1241:1177 as /class/input/input0 input: USB HID v1.00 Mouse [HID 1241:1177] on usb-0000:00:02.0-3 input: HID 1267:0103 as /class/input/input1 input: USB HID v1.10 Keyboard [HID 1267:0103] on usb-0000:00:02.0-4 input: HID 1267:0103 as /class/input/input2 input: USB HID v1.10 Device [HID 1267:0103] on usb-0000:00:02.0-4 usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.14rc3 (Wed Mar 14 07:25:50 2007 UTC). ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 22 ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCJ] -> GSI 22 (level, low) -> IRQ 22 PCI: Setting latency timer of device 0000:00:04.0 to 64 intel8x0_measure_ac97_clock: measured 50747 usecs intel8x0: clocking to 46843 ALSA device list: #0: NVidia CK804 with ALC850 at irq 22 TCP cubic registered powernow-k8: Found 2 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ processors (version 2.00.00) powernow-k8: 0 : fid 0xc (2000 MHz), vid 0x8 powernow-k8: 1 : fid 0xa (1800 MHz), vid 0xa powernow-k8: 2 : fid 0x2 (1000 MHz), vid 0x12 md: Autodetecting RAID arrays. md: autorun ... md: considering sdb2 ... md: adding sdb2 ... md: adding sda2 ... md: created md0 md: bind<sda2> md: bind<sdb2> md: running: <sdb2><sda2> md0: setting max_sectors to 128, segment boundary to 32767 raid0: looking at sdb2 raid0: comparing sdb2(195237824) with sdb2(195237824) raid0: END raid0: ==> UNIQUE raid0: 1 zones raid0: looking at sda2 raid0: comparing sda2(195237824) with sdb2(195237824) raid0: EQUAL raid0: FINAL 1 zones raid0: done. raid0 : md_size is 390475648 blocks. raid0 : conf->hash_spacing is 390475648 blocks. raid0 : nb_zone is 1. raid0 : Allocating 8 bytes for hash. md: ... autorun DONE. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 220k freed NET: Registered protocol family 1 EXT3 FS on sda1, internal journal i2c-adapter i2c-0: nForce2 SMBus adapter at 0x4c00 i2c-adapter i2c-1: nForce2 SMBus adapter at 0x4c40 it87: Found IT8712F chip at 0x290, revision 7 it87: in3 is VCC (+5V) it87: in7 is VCCH (+5V Stand-By) it87-isa 9191-0290: Detected broken BIOS defaults, disabling PWM interface kjournald starting. Commit interval 5 seconds EXT3 FS on sdb1, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on md0, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3 FS on sdc1, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3 FS on sdd1, internal journal EXT3-fs: mounted filesystem with ordered data mode. vmmon: module license 'unspecified' taints kernel. /dev/vmmon[4202]: Module vmmon: registered with major=10 minor=165 /dev/vmmon[4202]: Module vmmon: initialized /dev/vmmon[4212]: Module vmmon: unloaded /dev/vmmon[4586]: Module vmmon: registered with major=10 minor=165 /dev/vmmon[4586]: Module vmmon: initialized /dev/vmnet: open called by PID 4625 (vmnet-bridge) /dev/vmnet: hub 0 does not exist, allocating memory. /dev/vmnet: port on hub 0 successfully opened bridge-eth0: enabling the bridge bridge-eth0: up bridge-eth0: already up bridge-eth0: attached /dev/vmnet: open called by PID 4854 (vmnet-netifup) /dev/vmnet: hub 1 does not exist, allocating memory. /dev/vmnet: port on hub 1 successfully opened /dev/vmnet: open called by PID 4874 (vmnet-dhcpd) /dev/vmnet: port on hub 1 successfully opened ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18 ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 18 PCI: Setting latency timer of device 0000:01:00.0 to 64 NVRM: loading NVIDIA UNIX x86_64 Kernel Module 1.0-9746 Fri Dec 15 10:19:35 PST 2006 PCI: Setting latency timer of device 0000:01:00.0 to 64 NVRM: loading NVIDIA UNIX x86_64 Kernel Module 1.0-9746 Fri Dec 15 10:19:35 PST 2006 **WARNING** I2C adapter driver [NVIDIA i2c adapter ] forgot to specify physical device; fix it! **WARNING** I2C adapter driver [NVIDIA i2c adapter ] forgot to specify physical device; fix it! **WARNING** I2C adapter driver [NVIDIA i2c adapter ] forgot to specify physical device; fix it! ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 and rc5-mm2 - problem with cpuidle routine 2007-03-30 1:25 ` 2.6.21-rc4-mm1 and rc5-mm2 " Ed Sweetman @ 2007-03-30 2:17 ` Lee Revell 0 siblings, 0 replies; 146+ messages in thread From: Lee Revell @ 2007-03-30 2:17 UTC (permalink / raw) To: Ed Sweetman Cc: Venkatesh Pallipadi, Andrew Morton, Larry Finger, LKML, Len Brown, linux-acpi On 3/29/07, Ed Sweetman <safemode2@comcast.net> wrote: > NVRM: loading NVIDIA UNIX x86_64 Kernel Module 1.0-9746 Fri Dec 15 10:19:35 PST 2006 > PCI: Setting latency timer of device 0000:01:00.0 to 64 > NVRM: loading NVIDIA UNIX x86_64 Kernel Module 1.0-9746 Fri Dec 15 10:19:35 PST 2006 > **WARNING** I2C adapter driver [NVIDIA i2c adapter ] forgot to specify physical Please try to reproduce with an untainted kernel. Lee ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 - problem with cpuidle routine 2007-03-21 18:49 ` 2.6.21-rc4-mm1 - problem with cpuidle routine Larry Finger 2007-03-21 20:38 ` Andrew Morton @ 2007-03-21 20:39 ` Venki Pallipadi 1 sibling, 0 replies; 146+ messages in thread From: Venki Pallipadi @ 2007-03-21 20:39 UTC (permalink / raw) To: Larry Finger; +Cc: Andrew Morton, LKML On Mar 21, 2007, at 11:49 AM, Larry Finger wrote: > When I configure 'CPU Idle PM Support' on my HP dv2125nr notebook > with a Turion X64 X2 processor and > X86_64 architecture selected, the computer freezes on bootup. I > have included a portion the > configuration file and part of /var/log/boot.msg for my working > system. Please let me know if > further info from my system is required. I would be happy to test > any patches, etc. > > Larry > Looking at this failure. Will get back to you once I have some update... In the mean time, can you send me the complete boot message when you disable cpuidle and system boots ok. Thanks, ~Venki ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (12 preceding siblings ...) [not found] ` <1174433034.62033.16.camel@localhost> @ 2007-03-21 10:14 ` Reuben Farrelly 2007-03-22 23:27 ` 2.6.21-rc4-mm1 J.A. Magallón ` (9 subsequent siblings) 23 siblings, 0 replies; 146+ messages in thread From: Reuben Farrelly @ 2007-03-21 10:14 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel On 20/03/2007 3:56 PM, Andrew Morton wrote: > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > Will appear later at > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > > > > - Restored the RSDL CPU scheduler (a new version thereof) Just booted into this kernel, and hit this, which locked up the machine: This is tornado.reub.net (Linux x86_64 2.6.21-rc4-mm1) 20:16:58 tornado login: ------------[ cut here ]------------ kernel BUG at kernel/sched.c:3505! invalid opcode: 0000 [1] SMP last sysfs file: devices/pci0000:00/0000:00:1f.3/i2c-adapter/i2c-0/0-002e/pwm3 CPU 1 Modules linked in: firmware_class eeprom lm85 hwmon_vid i2c_i801 8021q iptable_filter iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nfnetlink iptable_mangle ip_tables nfs lockd sunrpc ohci1394 ieee1394 usb_storage Pid: 8250, comm: clamd Not tainted 2.6.21-rc4-mm1 #1 RIP: 0010:[<ffffffff8025d2cb>] [<ffffffff8025d2cb>] __sched_text_start+0x3cb/0x8b3 RSP: 0000:ffff8100023cfee0 EFLAGS: 00010002 RAX: 000000000000008c RBX: ffff810001e040e8 RCX: 000000000000000c RDX: 0000000000000000 RSI: 000000000000008c RDI: ffff810001e049b8 RBP: ffff8100023cff70 R08: 000000000000008c R09: ffff810001e049a8 R10: 0000000000000034 R11: 0000000000000000 R12: ffff810001e03f00 R13: 0000000000000002 R14: 00000000ffffffff R15: 000000521b55f827 FS: 00002b1dfda2ec00(0000) GS:ffff81000208ec40(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00002aaaaafcf000 CR3: 0000000004ac3000 CR4: 00000000000006e0 Process clamd (pid: 8250, threadinfo ffff8100023ce000, task ffff810004c090a0) Stack: ffff810004c090a0 ffffffff8025fdb7 ffff810004c090a0 00007fffae43e955 ffff810004c09248 00000001023cff28 ffffffff8029635d 0000000000c5aac0 0000000000000005 00002b1dfc7d6d5a ffffffff8025fdb7 0000000000000000 Call Trace: [<ffffffff8025fdb7>] trace_hardirqs_on_thunk+0x35/0x37 [<ffffffff8029635d>] trace_hardirqs_on+0x12a/0x15d [<ffffffff8025fdb7>] trace_hardirqs_on_thunk+0x35/0x37 [<ffffffff8025a7e0>] retint_careful+0x12/0x2e Code: 0f 0b eb fe 49 8b 94 24 e0 01 00 00 49 8b 84 24 d8 01 00 00 RIP [<ffffffff8025d2cb>] __sched_text_start+0x3cb/0x8b3 RSP <ffff8100023cfee0> BUG: spinlock lockup on CPU#0, swapper/0, ffff810001e03f00 BUG: spinlock lockup on CPU#1, clamd/8250, ffff810001e03f00 every few minutes the last two lines would be repeated. This kernel does not include the hotfixes (the gentoo portage ebuild for this release does not yet include them), however I am uncertain if they fix this problem or not anyway. Also, what happened to the -mm announcements sent to linux-kernel-announce@vger.kernel.org? Maybe I'm the only person to miss them :-) Reuben ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (13 preceding siblings ...) 2007-03-21 10:14 ` 2.6.21-rc4-mm1 Reuben Farrelly @ 2007-03-22 23:27 ` J.A. Magallón 2007-03-23 1:41 ` 2.6.21-rc4-mm1 Andrew Morton 2007-03-26 20:31 ` 2.6.21-rc4-mm1 J.A. Magallón 2007-03-24 13:06 ` [-mm patch] lguest: #if 0 check_bug_kill() Adrian Bunk ` (8 subsequent siblings) 23 siblings, 2 replies; 146+ messages in thread From: J.A. Magallón @ 2007-03-22 23:27 UTC (permalink / raw) To: linux-kernel On Mon, 19 Mar 2007 20:56:23 -0800, Andrew Morton <akpm@linux-foundation.org> wrote: > > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > Will appear later at > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > Is anybody having problems with optical drives and this kernel ? I can't get my dvdrw to spit any events to udevmonitor. If I mount it manually everything works fine. Perhaps the problem is in hal/g-v-m or anything else, but I suppose that udevmonitor receives events directly from kernel, isn't it ? TIA -- J.A. Magallon <jamagallon()ono!com> \ Software is like sex: \ It's better when it's free Mandriva Linux release 2007.1 (Cooker) for i586 Linux 2.6.20-jam05 (gcc 4.1.2 20070302 (prerelease) (4.1.2-1mdv2007.1)) #1 SMP PREEMPT ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 23:27 ` 2.6.21-rc4-mm1 J.A. Magallón @ 2007-03-23 1:41 ` Andrew Morton 2007-03-26 20:31 ` 2.6.21-rc4-mm1 J.A. Magallón 1 sibling, 0 replies; 146+ messages in thread From: Andrew Morton @ 2007-03-23 1:41 UTC (permalink / raw) To: "J.A. =?ISO-8859-1?B?TWFnYWxs824i?= <jamagallon; +Cc: linux-kernel Please always do reply-to-all. On Fri, 23 Mar 2007 00:27:09 +0100 "J.A. Magallón" <jamagallon@ono.com> wrote: > On Mon, 19 Mar 2007 20:56:23 -0800, Andrew Morton <akpm@linux-foundation.org> wrote: > > > > > Temporarily at > > > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > > > Will appear later at > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > > > > Is anybody having problems with optical drives and this kernel ? > I can't get my dvdrw to spit any events to udevmonitor. If I mount it > manually everything works fine. Yes, I think one person reported something similar. > Perhaps the problem is in hal/g-v-m or anything else, but I suppose that > udevmonitor receives events directly from kernel, isn't it ? Probably related to the not-yet-completely-solved firmware loader failures. It would be good if someone could do a bisection search on this. I face a fun evening hunting down a horrendous ext3 performance regression which is now in mainline. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-22 23:27 ` 2.6.21-rc4-mm1 J.A. Magallón 2007-03-23 1:41 ` 2.6.21-rc4-mm1 Andrew Morton @ 2007-03-26 20:31 ` J.A. Magallón 1 sibling, 0 replies; 146+ messages in thread From: J.A. Magallón @ 2007-03-26 20:31 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel On Fri, 23 Mar 2007 00:27:09 +0100, "J.A. Magallón" <jamagallon@ono.com> wrote: > On Mon, 19 Mar 2007 20:56:23 -0800, Andrew Morton <akpm@linux-foundation.org> wrote: > > > > > Temporarily at > > > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > > > Will appear later at > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > > > > Is anybody having problems with optical drives and this kernel ? > I can't get my dvdrw to spit any events to udevmonitor. If I mount it > manually everything works fine. > > Perhaps the problem is in hal/g-v-m or anything else, but I suppose that > udevmonitor receives events directly from kernel, isn't it ? > Finally, this was a userspace problem (hal): http://lists.freedesktop.org/archives/hal/2007-March/007545.html What I don't understand is this: I supposed that udev (and so udevmonitor) is independent of hal, more or less hal monitors udev events and does things, like looking the disc label and so on. But I do not get any events in udevmonitor if I'm not logged in gnome. How's this ? TIA -- J.A. Magallon <jamagallon()ono!com> \ Software is like sex: \ It's better when it's free Mandriva Linux release 2007.1 (Cooker) for i586 Linux 2.6.20-jam05 (gcc 4.1.2 20070302 (prerelease) (4.1.2-1mdv2007.1)) #2 SMP PREEMPT ^ permalink raw reply [flat|nested] 146+ messages in thread
* [-mm patch] lguest: #if 0 check_bug_kill() 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (14 preceding siblings ...) 2007-03-22 23:27 ` 2.6.21-rc4-mm1 J.A. Magallón @ 2007-03-24 13:06 ` Adrian Bunk 2007-03-25 7:33 ` Rusty Russell 2007-03-24 13:06 ` [-mm patch] drivers/scsi/constants.c: make 2 functions static Adrian Bunk ` (7 subsequent siblings) 23 siblings, 1 reply; 146+ messages in thread From: Adrian Bunk @ 2007-03-24 13:06 UTC (permalink / raw) To: Andrew Morton, Rusty Russell; +Cc: linux-kernel On Mon, Mar 19, 2007 at 08:56:23PM -0800, Andrew Morton wrote: >... > Changes since 2.6.21-rc3-mm1: >... > +lguest-use-read-only-pages-rather-than-segments-to-protect-high-mapped-switcher.patch >... > x86/x86_64 updates >... check_bug_kill() is no longer used. Signed-off-by: Adrian Bunk <bunk@stusta.de> --- arch/i386/lguest/interrupts_and_traps.c | 2 ++ arch/i386/lguest/lg.h | 1 - 2 files changed, 2 insertions(+), 1 deletion(-) --- linux-2.6.21-rc4-mm1/arch/i386/lguest/lg.h.old 2007-03-23 23:17:05.000000000 +0100 +++ linux-2.6.21-rc4-mm1/arch/i386/lguest/lg.h 2007-03-23 23:17:10.000000000 +0100 @@ -195,7 +195,6 @@ /* interrupts_and_traps.c: */ void maybe_do_interrupt(struct lguest *lg); int deliver_trap(struct lguest *lg, unsigned int num); -void check_bug_kill(struct lguest *lg); void load_guest_idt_entry(struct lguest *lg, unsigned int i, u32 low, u32 hi); void pin_stack_pages(struct lguest *lg); void pin_trap_pages(struct lguest *lg); --- linux-2.6.21-rc4-mm1/arch/i386/lguest/interrupts_and_traps.c.old 2007-03-23 23:17:18.000000000 +0100 +++ linux-2.6.21-rc4-mm1/arch/i386/lguest/interrupts_and_traps.c 2007-03-23 23:17:38.000000000 +0100 @@ -118,6 +118,7 @@ return 1; } +#if 0 void check_bug_kill(struct lguest *lg) { #ifdef CONFIG_BUG @@ -144,6 +145,7 @@ } #endif /* CONFIG_BUG */ } +#endif /* 0 */ static int direct_trap(const struct lguest *lg, const struct desc_struct *trap, ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [-mm patch] lguest: #if 0 check_bug_kill() 2007-03-24 13:06 ` [-mm patch] lguest: #if 0 check_bug_kill() Adrian Bunk @ 2007-03-25 7:33 ` Rusty Russell 2007-03-25 14:57 ` [-mm patch] lguest: remove check_bug_kill() Adrian Bunk 0 siblings, 1 reply; 146+ messages in thread From: Rusty Russell @ 2007-03-25 7:33 UTC (permalink / raw) To: Adrian Bunk; +Cc: Andrew Morton, linux-kernel On Sat, 2007-03-24 at 14:06 +0100, Adrian Bunk wrote: > On Mon, Mar 19, 2007 at 08:56:23PM -0800, Andrew Morton wrote: > >... > > Changes since 2.6.21-rc3-mm1: > >... > > +lguest-use-read-only-pages-rather-than-segments-to-protect-high-mapped-switcher.patch > >... > > x86/x86_64 updates > >... > > > check_bug_kill() is no longer used. Thanks Adrian, that was actually an oversight. However, this function is most useful in early bringup, so I didn't notice it was gone. I'd prefer a patch which eliminates it altogether, rather than #if 0 it out. Thanks! Rusty. ^ permalink raw reply [flat|nested] 146+ messages in thread
* [-mm patch] lguest: remove check_bug_kill() 2007-03-25 7:33 ` Rusty Russell @ 2007-03-25 14:57 ` Adrian Bunk 0 siblings, 0 replies; 146+ messages in thread From: Adrian Bunk @ 2007-03-25 14:57 UTC (permalink / raw) To: Rusty Russell; +Cc: Andrew Morton, linux-kernel On Sun, Mar 25, 2007 at 05:33:45PM +1000, Rusty Russell wrote: > On Sat, 2007-03-24 at 14:06 +0100, Adrian Bunk wrote: > > On Mon, Mar 19, 2007 at 08:56:23PM -0800, Andrew Morton wrote: > > >... > > > Changes since 2.6.21-rc3-mm1: > > >... > > > +lguest-use-read-only-pages-rather-than-segments-to-protect-high-mapped-switcher.patch > > >... > > > x86/x86_64 updates > > >... > > > > > > check_bug_kill() is no longer used. > > Thanks Adrian, that was actually an oversight. However, this function > is most useful in early bringup, so I didn't notice it was gone. > > I'd prefer a patch which eliminates it altogether, rather than #if 0 it > out. Patch below. > Thanks! > Rusty. cu Adrian <-- snip --> check_bug_kill() is no longer used. Signed-off-by: Adrian Bunk <bunk@stusta.de> --- arch/i386/lguest/interrupts_and_traps.c | 27 ------------------------ arch/i386/lguest/lg.h | 1 2 files changed, 28 deletions(-) --- linux-2.6.21-rc4-mm1/arch/i386/lguest/lg.h.old 2007-03-25 14:38:22.000000000 +0200 +++ linux-2.6.21-rc4-mm1/arch/i386/lguest/lg.h 2007-03-25 14:41:13.000000000 +0200 @@ -195,7 +195,6 @@ /* interrupts_and_traps.c: */ void maybe_do_interrupt(struct lguest *lg); int deliver_trap(struct lguest *lg, unsigned int num); -void check_bug_kill(struct lguest *lg); void load_guest_idt_entry(struct lguest *lg, unsigned int i, u32 low, u32 hi); void pin_stack_pages(struct lguest *lg); void pin_trap_pages(struct lguest *lg); --- linux-2.6.21-rc4-mm1/arch/i386/lguest/interrupts_and_traps.c.old 2007-03-25 14:38:46.000000000 +0200 +++ linux-2.6.21-rc4-mm1/arch/i386/lguest/interrupts_and_traps.c 2007-03-25 14:41:25.000000000 +0200 @@ -118,33 +118,6 @@ return 1; } -void check_bug_kill(struct lguest *lg) -{ -#ifdef CONFIG_BUG - u32 eip = lg->regs->eip - PAGE_OFFSET; - u16 insn; - - /* This only works for addresses in linear mapping... */ - if (lg->regs->eip < PAGE_OFFSET) - return; - lhread(lg, &insn, eip, sizeof(insn)); - if (insn == 0x0b0f) { -#ifdef CONFIG_DEBUG_BUGVERBOSE - u16 l; - u32 f; - char file[128]; - lhread(lg, &l, eip+sizeof(insn), sizeof(l)); - lhread(lg, &f, eip+sizeof(insn)+sizeof(l), sizeof(f)); - lhread(lg, file, f - PAGE_OFFSET, sizeof(file)); - file[sizeof(file)-1] = 0; - kill_guest(lg, "BUG() at %#x %s:%u", eip, file, l); -#else - kill_guest(lg, "BUG() at %#x", eip); -#endif /* CONFIG_DEBUG_BUGVERBOSE */ - } -#endif /* CONFIG_BUG */ -} - static int direct_trap(const struct lguest *lg, const struct desc_struct *trap, unsigned int num) ^ permalink raw reply [flat|nested] 146+ messages in thread
* [-mm patch] drivers/scsi/constants.c: make 2 functions static 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (15 preceding siblings ...) 2007-03-24 13:06 ` [-mm patch] lguest: #if 0 check_bug_kill() Adrian Bunk @ 2007-03-24 13:06 ` Adrian Bunk 2007-03-24 16:11 ` Douglas Gilbert 2007-03-24 13:07 ` [-mm patch] fs/revoke.c: cleanups (and bugfix for 64bit systems) Adrian Bunk ` (6 subsequent siblings) 23 siblings, 1 reply; 146+ messages in thread From: Adrian Bunk @ 2007-03-24 13:06 UTC (permalink / raw) To: Andrew Morton, James.Bottomley; +Cc: linux-kernel, linux-scsi On Mon, Mar 19, 2007 at 08:56:23PM -0800, Andrew Morton wrote: >... > Changes since 2.6.21-rc3-mm1: >... > git-scsi-misc.patch >... > git trees >... This patch makes two needlessly global functions static. Signed-off-by: Adrian Bunk <bunk@stusta.de> --- drivers/scsi/constants.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- linux-2.6.21-rc4-mm1/drivers/scsi/constants.c.old 2007-03-23 23:26:39.000000000 +0100 +++ linux-2.6.21-rc4-mm1/drivers/scsi/constants.c 2007-03-23 23:26:55.000000000 +0100 @@ -1235,7 +1235,7 @@ } EXPORT_SYMBOL(scsi_print_sense_hdr); -void +static void scsi_decode_sense_buffer(const unsigned char *sense_buffer, int sense_len, struct scsi_sense_hdr *sshdr) { @@ -1258,7 +1258,7 @@ } } -void +static void scsi_decode_sense_extras(const unsigned char *sense_buffer, int sense_len, struct scsi_sense_hdr *sshdr) { ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [-mm patch] drivers/scsi/constants.c: make 2 functions static 2007-03-24 13:06 ` [-mm patch] drivers/scsi/constants.c: make 2 functions static Adrian Bunk @ 2007-03-24 16:11 ` Douglas Gilbert 2007-03-24 17:02 ` Adrian Bunk 0 siblings, 1 reply; 146+ messages in thread From: Douglas Gilbert @ 2007-03-24 16:11 UTC (permalink / raw) To: Adrian Bunk; +Cc: Andrew Morton, James.Bottomley, linux-kernel, linux-scsi Adrian Bunk wrote: > On Mon, Mar 19, 2007 at 08:56:23PM -0800, Andrew Morton wrote: >> ... >> Changes since 2.6.21-rc3-mm1: >> ... >> git-scsi-misc.patch >> ... >> git trees >> ... > > > This patch makes two needlessly global functions static. > > Signed-off-by: Adrian Bunk <bunk@stusta.de> > > --- > > drivers/scsi/constants.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > --- linux-2.6.21-rc4-mm1/drivers/scsi/constants.c.old 2007-03-23 23:26:39.000000000 +0100 > +++ linux-2.6.21-rc4-mm1/drivers/scsi/constants.c 2007-03-23 23:26:55.000000000 +0100 > @@ -1235,7 +1235,7 @@ > } > EXPORT_SYMBOL(scsi_print_sense_hdr); > > -void > +static void > scsi_decode_sense_buffer(const unsigned char *sense_buffer, int sense_len, > struct scsi_sense_hdr *sshdr) > { > @@ -1258,7 +1258,7 @@ > } > } > > -void > +static void > scsi_decode_sense_extras(const unsigned char *sense_buffer, int sense_len, > struct scsi_sense_hdr *sshdr) > { Adrian, Who put those functions in? The names and arguments look very similar to these exported functions in scsi_error.c *** : scsi_normalize_sense scsi_sense_desc_find scsi_get_sense_info_fld that I can see in 2.6.21-rc4 The proposed scsi_decode_sense_buffer() looks broken because it can fail and should return an int reflecting that. How scsi_decode_sense_extras() works is intriguing, unless struct scsi_sense_hdr has been changed as well. *** Putting sense decode logic in scsi_error.c is wrong because: - the ATA command set is proposing an ATA REQUEST SENSE command to yield a sense buffer - sense buffers don't necessarily indicate errors. So moving those functions out of scsi_error.c IMO is a good idea. Breaking them in the move isn't. Doug Gilbert ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [-mm patch] drivers/scsi/constants.c: make 2 functions static 2007-03-24 16:11 ` Douglas Gilbert @ 2007-03-24 17:02 ` Adrian Bunk 0 siblings, 0 replies; 146+ messages in thread From: Adrian Bunk @ 2007-03-24 17:02 UTC (permalink / raw) To: Douglas Gilbert, Martin K. Petersen Cc: Andrew Morton, James.Bottomley, linux-kernel, linux-scsi On Sat, Mar 24, 2007 at 12:11:05PM -0400, Douglas Gilbert wrote: > Adrian Bunk wrote: > > On Mon, Mar 19, 2007 at 08:56:23PM -0800, Andrew Morton wrote: > >> ... > >> Changes since 2.6.21-rc3-mm1: > >> ... > >> git-scsi-misc.patch > >> ... > >> git trees > >> ... > > > > > > This patch makes two needlessly global functions static. > > > > Signed-off-by: Adrian Bunk <bunk@stusta.de> > > > > --- > > > > drivers/scsi/constants.c | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > --- linux-2.6.21-rc4-mm1/drivers/scsi/constants.c.old 2007-03-23 23:26:39.000000000 +0100 > > +++ linux-2.6.21-rc4-mm1/drivers/scsi/constants.c 2007-03-23 23:26:55.000000000 +0100 > > @@ -1235,7 +1235,7 @@ > > } > > EXPORT_SYMBOL(scsi_print_sense_hdr); > > > > -void > > +static void > > scsi_decode_sense_buffer(const unsigned char *sense_buffer, int sense_len, > > struct scsi_sense_hdr *sshdr) > > { > > @@ -1258,7 +1258,7 @@ > > } > > } > > > > -void > > +static void > > scsi_decode_sense_extras(const unsigned char *sense_buffer, int sense_len, > > struct scsi_sense_hdr *sshdr) > > { > > Adrian, > Who put those functions in? [SCSI] constants.c: cleanup, verbose result printing From: Martin K. Petersen Clean up constants.c and make result printing more user friendly: - Refactor the command and sense functions so that the actual formatting can be called from the various helper functions with the correct prefix. - Replace scsi_print_hostbyte() and scsi_print_driverbyte() with scsi_print_result() which is verbose when CONFIG_SCSI_CONSTANTS is on. Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com> > The names and arguments look very similar to these > exported functions in scsi_error.c *** : > scsi_normalize_sense > scsi_sense_desc_find > scsi_get_sense_info_fld > > that I can see in 2.6.21-rc4 > > The proposed scsi_decode_sense_buffer() looks broken because > it can fail and should return an int reflecting that. > How scsi_decode_sense_extras() works is intriguing, unless > struct scsi_sense_hdr has been changed as well. > > > *** Putting sense decode logic in scsi_error.c is wrong > because: > - the ATA command set is proposing an ATA REQUEST SENSE > command to yield a sense buffer > - sense buffers don't necessarily indicate errors. > > So moving those functions out of scsi_error.c IMO is a > good idea. Breaking them in the move isn't. > > Doug Gilbert > cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed ^ permalink raw reply [flat|nested] 146+ messages in thread
* [-mm patch] fs/revoke.c: cleanups (and bugfix for 64bit systems) 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (16 preceding siblings ...) 2007-03-24 13:06 ` [-mm patch] drivers/scsi/constants.c: make 2 functions static Adrian Bunk @ 2007-03-24 13:07 ` Adrian Bunk 2007-03-24 13:15 ` Pekka Enberg 2007-03-24 13:07 ` [-mm patch] unexport bio_{,un}map_user Adrian Bunk ` (5 subsequent siblings) 23 siblings, 1 reply; 146+ messages in thread From: Adrian Bunk @ 2007-03-24 13:07 UTC (permalink / raw) To: Andrew Morton, Pekka Enberg; +Cc: linux-kernel On Mon, Mar 19, 2007 at 08:56:23PM -0800, Andrew Morton wrote: >... > Changes since 2.6.21-rc3-mm1: >... > +revoke-core-code.patch >... > revoke() syscall >... This patch contains the following: - every file should #include the headers containing the prototypes for it's global functions - fix the wrong return value of sys_frevoke() gcc was now able to detect - make 2 needlessly global structs static Signed-off-by: Adrian Bunk <bunk@stusta.de> --- fs/revoke.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) --- linux-2.6.21-rc4-mm1/fs/revoke.c.old 2007-03-23 23:31:46.000000000 +0100 +++ linux-2.6.21-rc4-mm1/fs/revoke.c 2007-03-23 23:50:39.000000000 +0100 @@ -16,6 +16,7 @@ #include <linux/mount.h> #include <linux/sched.h> #include <linux/revoked_fs_i.h> +#include <linux/syscalls.h> /* * This is used for pre-allocating an array of file pointers so that we don't @@ -28,7 +29,7 @@ unsigned long restore_start; }; -struct kmem_cache *revokefs_inode_cache; +static struct kmem_cache *revokefs_inode_cache; /* * Revoked file descriptors point to inodes in the revokefs filesystem. @@ -551,7 +552,7 @@ return err; } -asmlinkage int sys_frevoke(unsigned int fd) +asmlinkage long sys_frevoke(unsigned int fd) { struct file *file = fget(fd); int err = -EBADF; @@ -618,7 +619,7 @@ REVOKEFS_MAGIC, mnt); } -struct file_system_type revokefs_fs_type = { +static struct file_system_type revokefs_fs_type = { .name = "revokefs", .get_sb = revokefs_get_sb, .kill_sb = kill_anon_super ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: [-mm patch] fs/revoke.c: cleanups (and bugfix for 64bit systems) 2007-03-24 13:07 ` [-mm patch] fs/revoke.c: cleanups (and bugfix for 64bit systems) Adrian Bunk @ 2007-03-24 13:15 ` Pekka Enberg 0 siblings, 0 replies; 146+ messages in thread From: Pekka Enberg @ 2007-03-24 13:15 UTC (permalink / raw) To: Adrian Bunk; +Cc: Andrew Morton, linux-kernel On 3/24/07, Adrian Bunk <bunk@stusta.de> wrote: > This patch contains the following: > - every file should #include the headers containing the prototypes for > it's global functions > - fix the wrong return value of sys_frevoke() gcc was now able to detect > - make 2 needlessly global structs static > > Signed-off-by: Adrian Bunk <bunk@stusta.de> Looks good. Thanks! Acked-by: Pekka Enberg <penberg@cs.helsinki.fi> ^ permalink raw reply [flat|nested] 146+ messages in thread
* [-mm patch] unexport bio_{,un}map_user 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (17 preceding siblings ...) 2007-03-24 13:07 ` [-mm patch] fs/revoke.c: cleanups (and bugfix for 64bit systems) Adrian Bunk @ 2007-03-24 13:07 ` Adrian Bunk 2007-03-25 14:58 ` [-mm patch] drivers/eisa/pci_eisa.c:pci_eisa_init() should be init Adrian Bunk ` (4 subsequent siblings) 23 siblings, 0 replies; 146+ messages in thread From: Adrian Bunk @ 2007-03-24 13:07 UTC (permalink / raw) To: Andrew Morton, Jens Axboe; +Cc: linux-kernel On Mon, Mar 19, 2007 at 08:56:23PM -0800, Andrew Morton wrote: >... > Changes since 2.6.21-rc3-mm1: >... > git-scsi-misc.patch >... > git trees >... bio_{,un}map_user do no longer have any modular users. Signed-off-by: Adrian Bunk <bunk@stusta.de> --- --- linux-2.6.21-rc4-mm1/fs/bio.c.old 2007-03-24 11:42:28.000000000 +0100 +++ linux-2.6.21-rc4-mm1/fs/bio.c 2007-03-24 11:42:39.000000000 +0100 @@ -1253,8 +1253,6 @@ EXPORT_SYMBOL(bio_add_page); EXPORT_SYMBOL(bio_add_pc_page); EXPORT_SYMBOL(bio_get_nr_vecs); -EXPORT_SYMBOL(bio_map_user); -EXPORT_SYMBOL(bio_unmap_user); EXPORT_SYMBOL(bio_map_kern); EXPORT_SYMBOL(bio_pair_release); EXPORT_SYMBOL(bio_split); ^ permalink raw reply [flat|nested] 146+ messages in thread
* [-mm patch] drivers/eisa/pci_eisa.c:pci_eisa_init() should be init 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (18 preceding siblings ...) 2007-03-24 13:07 ` [-mm patch] unexport bio_{,un}map_user Adrian Bunk @ 2007-03-25 14:58 ` Adrian Bunk 2007-03-26 0:24 ` Wrong IDE cable detection in libata [Re: 2.6.21-rc4-mm1] J.A. Magallón ` (3 subsequent siblings) 23 siblings, 0 replies; 146+ messages in thread From: Adrian Bunk @ 2007-03-25 14:58 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel I was looking at the following section error: <-- snip --> WARNING: drivers/built-in.o - Section mismatch: reference to .init.text:eisa_root_register from .text between 'pci_eisa_init' (at offset 0xabf670) and 'virtual_eisa_release' <-- snip --> AFAIK a PCI to EISA bridge isn't anything hotpluggable, so pci_eisa_init() can become __init. Signed-off-by: Adrian Bunk <bunk@stusta.de> --- --- linux-2.6.21-rc4-mm1/drivers/eisa/pci_eisa.c.old 2007-03-25 15:51:01.000000000 +0200 +++ linux-2.6.21-rc4-mm1/drivers/eisa/pci_eisa.c 2007-03-25 15:51:17.000000000 +0200 @@ -19,8 +19,8 @@ /* There is only *one* pci_eisa device per machine, right ? */ static struct eisa_root_device pci_eisa_root; -static int __devinit pci_eisa_init (struct pci_dev *pdev, - const struct pci_device_id *ent) +static int __init pci_eisa_init(struct pci_dev *pdev, + const struct pci_device_id *ent) { int rc; ^ permalink raw reply [flat|nested] 146+ messages in thread
* Wrong IDE cable detection in libata [Re: 2.6.21-rc4-mm1] 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (19 preceding siblings ...) 2007-03-25 14:58 ` [-mm patch] drivers/eisa/pci_eisa.c:pci_eisa_init() should be init Adrian Bunk @ 2007-03-26 0:24 ` J.A. Magallón 2007-03-26 11:01 ` Tejun Heo 2007-03-26 19:47 ` 2.6.21-rc4-mm1 Badari Pulavarty ` (2 subsequent siblings) 23 siblings, 1 reply; 146+ messages in thread From: J.A. Magallón @ 2007-03-26 0:24 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel, linux-ide On Mon, 19 Mar 2007 20:56:23 -0800, Andrew Morton <akpm@linux-foundation.org> wrote: > > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > Libata seems to misdetect my cable. I have double-checked and the cable is 80 pin... ata1 is PATA ICH5 bus 1 with DVD-RW + ZIP and 40 pin cable ata2 is PATA ICH5 bus 2 with extra HD + DVD and 80 pin cable ata3 is real SATA ICH5 with boot HD (mm, I chaged bios settings to get the box booting from the SATA disk) werewolf:~# lsscsi [0:0:0:0] cd/dvd HL-DT-ST DVDRAM GSA-H10N JL12 /dev/.tmp-11-0 [0:0:1:0] disk IOMEGA ZIP 250 51.G /dev/sda [1:0:0:0] disk ATA ST3120022A 3.06 /dev/sdb [1:0:1:0] cd/dvd TOSHIBA DVD-ROM SD-M1712 1004 /dev/sr1 [2:0:0:0] disk ATA ST3200822AS 3.01 /dev/sdc ata_piix 0000:00:1f.1: version 2.10ac1 ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18 PCI: Setting latency timer of device 0000:00:1f.1 to 64 ata1: PATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001f000 irq 14 ata2: PATA max UDMA/133 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001f008 irq 15 scsi0 : ata_piix ata1.00: ATAPI, max UDMA/33 ata1.01: ATAPI, max MWDMA0, CDB intr ata1.00: configured for UDMA/33 ata1.01: configured for PIO3 scsi1 : ata_piix ata2.00: ATA-6: ST3120022A, 3.06, max UDMA/100 ata2.00: 234441648 sectors, multi 16: LBA48 ata2.01: ATAPI, max UDMA/33 ata2.00: limited to UDMA/33 due to 40-wire cable <======================= ata2.00: configured for UDMA/33 ata2.01: configured for UDMA/33 scsi 0:0:0:0: CD-ROM HL-DT-ST DVDRAM GSA-H10N JL12 PQ: 0 ANSI: 5 sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 0:0:0:0: Attached scsi CD-ROM sr0 scsi 0:0:1:0: Direct-Access IOMEGA ZIP 250 51.G PQ: 0 ANSI: 5 sd 0:0:1:0: [sda] Attached SCSI removable disk scsi 1:0:0:0: Direct-Access ATA ST3120022A 3.06 PQ: 0 ANSI: 5 sd 1:0:0:0: [sdb] 234441648 512-byte hardware sectors (120034 MB) sd 1:0:0:0: [sdb] Write Protect is off sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 1:0:0:0: [sdb] 234441648 512-byte hardware sectors (120034 MB) sd 1:0:0:0: [sdb] Write Protect is off sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdb: sdb1 sd 1:0:0:0: [sdb] Attached SCSI disk scsi 1:0:1:0: CD-ROM TOSHIBA DVD-ROM SD-M1712 1004 PQ: 0 ANSI: 5 sr1: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray sr 1:0:1:0: Attached scsi CD-ROM sr1 Any ideas ? -- J.A. Magallon <jamagallon()ono!com> \ Software is like sex: \ It's better when it's free Mandriva Linux release 2007.1 (Cooker) for i586 Linux 2.6.20-jam05 (gcc 4.1.2 20070302 (prerelease) (4.1.2-1mdv2007.1)) #1 SMP PREEMPT ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: Wrong IDE cable detection in libata [Re: 2.6.21-rc4-mm1] 2007-03-26 0:24 ` Wrong IDE cable detection in libata [Re: 2.6.21-rc4-mm1] J.A. Magallón @ 2007-03-26 11:01 ` Tejun Heo 2007-03-26 20:18 ` J.A. Magallón 0 siblings, 1 reply; 146+ messages in thread From: Tejun Heo @ 2007-03-26 11:01 UTC (permalink / raw) To: "J.A. Magallón"; +Cc: Andrew Morton, linux-kernel, linux-ide J.A. Magallón wrote: > Libata seems to misdetect my cable. > I have double-checked and the cable is 80 pin... Does the following patch fix your problem? http://article.gmane.org/gmane.linux.ide/17444 (You can get the raw message by appending /raw to the URL). -- tejun ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: Wrong IDE cable detection in libata [Re: 2.6.21-rc4-mm1] 2007-03-26 11:01 ` Tejun Heo @ 2007-03-26 20:18 ` J.A. Magallón 0 siblings, 0 replies; 146+ messages in thread From: J.A. Magallón @ 2007-03-26 20:18 UTC (permalink / raw) To: Tejun Heo; +Cc: Andrew Morton, linux-kernel, linux-ide On Mon, 26 Mar 2007 20:01:52 +0900, Tejun Heo <htejun@gmail.com> wrote: > J.A. Magallón wrote: > > Libata seems to misdetect my cable. > > I have double-checked and the cable is 80 pin... > > Does the following patch fix your problem? > > http://article.gmane.org/gmane.linux.ide/17444 > > (You can get the raw message by appending /raw to the URL). > Yes it works !! Disk is back at nice speed of 50 Mb/s. dmesg: ata_piix 0000:00:1f.1: version 2.10ac1 ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18 PCI: Setting latency timer of device 0000:00:1f.1 to 64 ata1: PATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001f000 irq 14 ata2: PATA max UDMA/133 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001f008 irq 15 scsi0 : ata_piix ata1.00: ATAPI, max UDMA/33 ata1.01: ATAPI, max MWDMA0, CDB intr ata1.00: configured for UDMA/33 ata1.01: configured for PIO3 scsi1 : ata_piix ata2.00: ATA-6: ST3120022A, 3.06, max UDMA/100 ata2.00: 234441648 sectors, multi 16: LBA48 ata2.01: ATAPI, max UDMA/33 ata2.00: configured for UDMA/100 <============= ata2.01: configured for UDMA/33 <============= Thanks !! -- J.A. Magallon <jamagallon()ono!com> \ Software is like sex: \ It's better when it's free Mandriva Linux release 2007.1 (Cooker) for i586 Linux 2.6.20-jam05 (gcc 4.1.2 20070302 (prerelease) (4.1.2-1mdv2007.1)) #2 SMP PREEMPT ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (20 preceding siblings ...) 2007-03-26 0:24 ` Wrong IDE cable detection in libata [Re: 2.6.21-rc4-mm1] J.A. Magallón @ 2007-03-26 19:47 ` Badari Pulavarty 2007-03-26 23:29 ` 2.6.21-rc4-mm1 Paul Mackerras 2007-03-26 20:05 ` 2.6.21-rc4-mm1 Badari Pulavarty 2007-03-26 21:57 ` 2.6.21-rc4-mm1 Badari Pulavarty 23 siblings, 1 reply; 146+ messages in thread From: Badari Pulavarty @ 2007-03-26 19:47 UTC (permalink / raw) To: Andrew Morton, fenkes; +Cc: lkml, paulus, benh On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote: > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > Will appear later at > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > CC arch/powerpc/kernel/ibmebus.o arch/powerpc/kernel/ibmebus.c:463: error: ‘of_device_uevent’ undeclared here (not in a function) make[1]: *** [arch/powerpc/kernel/ibmebus.o] Error 1 make: *** [arch/powerpc/kernel] Error 2 Patch causing the problem in -mm: ibmebus-uevent-support.patch I don't see where ‘of_device_uevent’ is defined :( Thanks, Badari ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-26 19:47 ` 2.6.21-rc4-mm1 Badari Pulavarty @ 2007-03-26 23:29 ` Paul Mackerras 0 siblings, 0 replies; 146+ messages in thread From: Paul Mackerras @ 2007-03-26 23:29 UTC (permalink / raw) To: Badari Pulavarty; +Cc: Andrew Morton, fenkes, lkml, benh Badari Pulavarty writes: > Patch causing the problem in -mm: > ibmebus-uevent-support.patch > > I don't see where ^[$,1rx^[(Bof_device_uevent^[$,1ry^[(B is defined :( That patch depends on another one from Sylvain Munaut that I haven't yet managed to get Ben H. to express an opinion on, and which isn't in -mm. I thought I mentioned that to Andrew, but maybe I only intended to... Paul. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (21 preceding siblings ...) 2007-03-26 19:47 ` 2.6.21-rc4-mm1 Badari Pulavarty @ 2007-03-26 20:05 ` Badari Pulavarty 2007-03-26 19:35 ` 2.6.21-rc4-mm1 Jean Delvare 2007-03-26 21:57 ` 2.6.21-rc4-mm1 Badari Pulavarty 23 siblings, 1 reply; 146+ messages in thread From: Badari Pulavarty @ 2007-03-26 20:05 UTC (permalink / raw) To: Andrew Morton, khali, gregkh; +Cc: lkml On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote: > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > Will appear later at > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ # make -j8 modules CHK include/linux/version.h CHK include/linux/utsrelease.h LD [M] sound/soundcore.o CC [M] sound/ppc/beep.o sound/ppc/beep.c: In function ‘snd_pmac_attach_beep’: sound/ppc/beep.c:224: error: dereferencing pointer to incomplete type sound/ppc/beep.c:242: error: dereferencing pointer to incomplete type sound/ppc/beep.c:265: error: dereferencing pointer to incomplete type sound/ppc/beep.c: In function ‘snd_pmac_detach_beep’: sound/ppc/beep.c:275: error: dereferencing pointer to incomplete type make[2]: *** [sound/ppc/beep.o] Error 1 make[1]: *** [sound/ppc] Error 2 make: *** [sound] Error 2 make: *** Waiting for unfinished jobs.... Patch that is causing the problem in -mm: gregkh-pci-pci-cleanup-the-includes-of-linux-pcih.patch sound/ppc/beep.c needs to include <linux/pci.h> Thanks, Badari ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-26 20:05 ` 2.6.21-rc4-mm1 Badari Pulavarty @ 2007-03-26 19:35 ` Jean Delvare 2007-03-26 23:26 ` 2.6.21-rc4-mm1 Greg KH 0 siblings, 1 reply; 146+ messages in thread From: Jean Delvare @ 2007-03-26 19:35 UTC (permalink / raw) To: Badari Pulavarty, Greg KH; +Cc: Andrew Morton, LKML Hi Badari, On Mon, 26 Mar 2007 12:05:56 -0800, Badari Pulavarty wrote: > On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote: > > Temporarily at > > > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > > > Will appear later at > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > > # make -j8 modules > CHK include/linux/version.h > CHK include/linux/utsrelease.h > LD [M] sound/soundcore.o > CC [M] sound/ppc/beep.o > sound/ppc/beep.c: In function ‘snd_pmac_attach_beep’: > sound/ppc/beep.c:224: error: dereferencing pointer to incomplete type > sound/ppc/beep.c:242: error: dereferencing pointer to incomplete type > sound/ppc/beep.c:265: error: dereferencing pointer to incomplete type > sound/ppc/beep.c: In function ‘snd_pmac_detach_beep’: > sound/ppc/beep.c:275: error: dereferencing pointer to incomplete type > make[2]: *** [sound/ppc/beep.o] Error 1 > make[1]: *** [sound/ppc] Error 2 > make: *** [sound] Error 2 > make: *** Waiting for unfinished jobs.... > > > Patch that is causing the problem in -mm: > gregkh-pci-pci-cleanup-the-includes-of-linux-pcih.patch > > sound/ppc/beep.c needs to include <linux/pci.h> Good catch, thanks for reporting. I expected a few false positives to be left in my patch, but couldn't test everything. Greg, please update your copy with this version of the patch. The only change is that sound/ppc/beep.c is removed from the patch. * * * * * I noticed that many source files include <linux/pci.h> while they do not appear to need it. Here is an attempt to clean it all up. In order to find all possibly affected files, I searched for all files including <linux/pci.h> but without any other occurence of "pci" or "PCI". I removed the include statement from all of these, then I compiled an allmodconfig kernel on both i386 and x86_64 and fixed the false positives manually. My tests covered 66% of the affected files, so there could be false positives remaining. Untested files are: arch/alpha/kernel/err_common.c arch/alpha/kernel/err_ev6.c arch/alpha/kernel/err_ev7.c arch/ia64/sn/kernel/huberror.c arch/ia64/sn/kernel/xpnet.c arch/m68knommu/kernel/dma.c arch/mips/lib/iomap.c arch/powerpc/platforms/pseries/ras.c arch/ppc/8260_io/enet.c arch/ppc/8260_io/fcc_enet.c arch/ppc/8xx_io/enet.c arch/ppc/syslib/ppc4xx_sgdma.c arch/sh64/mach-cayman/iomap.c arch/xtensa/kernel/xtensa_ksyms.c arch/xtensa/platform-iss/setup.c drivers/i2c/busses/i2c-at91.c drivers/i2c/busses/i2c-mpc.c drivers/media/video/saa711x.c drivers/misc/hdpuftrs/hdpu_cpustate.c drivers/misc/hdpuftrs/hdpu_nexus.c drivers/net/au1000_eth.c drivers/net/fec_8xx/fec_main.c drivers/net/fec_8xx/fec_mii.c drivers/net/fs_enet/fs_enet-main.c drivers/net/fs_enet/mac-fcc.c drivers/net/fs_enet/mac-fec.c drivers/net/fs_enet/mac-scc.c drivers/net/fs_enet/mii-bitbang.c drivers/net/fs_enet/mii-fec.c drivers/net/ibm_emac/ibm_emac_core.c drivers/net/lasi_82596.c drivers/parisc/hppb.c drivers/sbus/sbus.c drivers/video/g364fb.c drivers/video/platinumfb.c drivers/video/stifb.c drivers/video/valkyriefb.c include/asm-arm/arch-ixp4xx/dma.h sound/oss/au1550_ac97.c I would welcome test reports for these files. I am fine with removing the untested files from the patch if the general opinion is that these changes aren't safe. The tested part would still be nice to have. Note that this patch depends on another header fixup patch I submitted to LKML yesterday: [PATCH] scatterlist.h needs types.h http://lkml.org/lkml/2007/3/01/141 Signed-off-by: Jean Delvare <khali@linux-fr.org> --- arch/alpha/kernel/err_common.c | 1 - arch/alpha/kernel/err_ev6.c | 1 - arch/alpha/kernel/err_ev7.c | 1 - arch/i386/kernel/cpu/cpufreq/speedstep-lib.c | 1 - arch/i386/kernel/cpu/cpufreq/speedstep-smi.c | 2 +- arch/ia64/sn/kernel/huberror.c | 1 - arch/ia64/sn/kernel/xpnet.c | 1 - arch/m68knommu/kernel/dma.c | 1 - arch/mips/lib/iomap.c | 1 - arch/powerpc/platforms/pseries/ras.c | 1 - arch/ppc/8260_io/enet.c | 1 - arch/ppc/8260_io/fcc_enet.c | 1 - arch/ppc/8xx_io/enet.c | 1 - arch/ppc/syslib/ppc4xx_sgdma.c | 1 - arch/sh64/mach-cayman/iomap.c | 1 - arch/xtensa/kernel/xtensa_ksyms.c | 1 - arch/xtensa/platform-iss/setup.c | 1 - drivers/ata/pata_winbond.c | 1 - drivers/atm/adummy.c | 1 - drivers/char/hw_random/via-rng.c | 1 - drivers/char/pcmcia/synclink_cs.c | 1 - drivers/char/tpm/tpm.h | 1 - drivers/char/watchdog/sc1200wdt.c | 1 - drivers/char/watchdog/scx200_wdt.c | 2 +- drivers/i2c/busses/i2c-at91.c | 1 - drivers/i2c/busses/i2c-mpc.c | 1 - drivers/i2c/busses/i2c-pca-isa.c | 1 - drivers/ieee1394/hosts.c | 1 - drivers/infiniband/core/cm.c | 1 - drivers/infiniband/core/iwcm.c | 1 - drivers/infiniband/core/mad_priv.h | 1 - drivers/infiniband/core/multicast.c | 1 - drivers/infiniband/core/sa_query.c | 1 - drivers/infiniband/core/user_mad.c | 1 - drivers/infiniband/hw/ipath/ipath_fs.c | 1 - drivers/infiniband/hw/ipath/ipath_layer.c | 1 - drivers/infiniband/hw/ipath/ipath_stats.c | 2 -- drivers/infiniband/hw/ipath/ipath_sysfs.c | 1 - drivers/infiniband/hw/mthca/mthca_memfree.h | 1 - drivers/infiniband/ulp/ipoib/ipoib.h | 1 - drivers/isdn/hisax/netjet.c | 1 - drivers/isdn/hysdn/hysdn_proclog.c | 1 - drivers/media/dvb/cinergyT2/cinergyT2.c | 2 +- drivers/media/video/adv7170.c | 1 - drivers/media/video/adv7175.c | 1 - drivers/media/video/bt819.c | 1 - drivers/media/video/bt856.c | 1 - drivers/media/video/bt866.c | 1 - drivers/media/video/cx88/cx88-tvaudio.c | 1 - drivers/media/video/em28xx/em28xx-cards.c | 1 - drivers/media/video/saa7111.c | 1 - drivers/media/video/saa7114.c | 1 - drivers/media/video/saa711x.c | 1 - drivers/media/video/saa7185.c | 1 - drivers/misc/hdpuftrs/hdpu_cpustate.c | 1 - drivers/misc/hdpuftrs/hdpu_nexus.c | 1 - drivers/mtd/devices/doc2000.c | 1 - drivers/mtd/devices/doc2001.c | 1 - drivers/mtd/devices/doc2001plus.c | 1 - drivers/mtd/devices/docecc.c | 1 - drivers/mtd/inftlmount.c | 1 - drivers/mtd/nand/cs553x_nand.c | 1 - drivers/mtd/nftlcore.c | 1 - drivers/net/atl1/atl1_param.c | 1 - drivers/net/au1000_eth.c | 1 - drivers/net/fec_8xx/fec_main.c | 1 - drivers/net/fec_8xx/fec_mii.c | 1 - drivers/net/fs_enet/fs_enet-main.c | 1 - drivers/net/fs_enet/mac-fcc.c | 1 - drivers/net/fs_enet/mac-fec.c | 1 - drivers/net/fs_enet/mac-scc.c | 1 - drivers/net/fs_enet/mii-bitbang.c | 1 - drivers/net/fs_enet/mii-fec.c | 1 - drivers/net/ibm_emac/ibm_emac_core.c | 1 - drivers/net/ixgb/ixgb_osdep.h | 1 - drivers/net/lasi_82596.c | 1 - drivers/net/tokenring/madgemc.c | 1 - drivers/net/tokenring/smctr.c | 1 - drivers/net/tulip/21142.c | 1 - drivers/net/tulip/pnic.c | 1 - drivers/net/tulip/pnic2.c | 1 - drivers/net/tulip/timer.c | 1 - drivers/net/tulip/tulip.h | 1 + drivers/net/wan/lmc/lmc_media.c | 1 - drivers/net/wan/lmc/lmc_proto.c | 1 - drivers/net/wan/pc300_tty.c | 1 - drivers/parisc/hppb.c | 2 -- drivers/pcmcia/cs.c | 1 - drivers/pcmcia/socket_sysfs.c | 1 - drivers/sbus/sbus.c | 1 - drivers/scsi/aacraid/dpcsup.c | 1 - drivers/scsi/aacraid/sa.c | 1 - drivers/scsi/aha1542.c | 1 - drivers/scsi/aic94xx/aic94xx_scb.c | 1 - drivers/scsi/arcmsr/arcmsr_attr.c | 1 - drivers/scsi/libsas/sas_expander.c | 1 - drivers/scsi/libsrp.c | 1 - drivers/usb/net/kaweth.c | 1 - drivers/video/aty/radeon_i2c.c | 1 - drivers/video/g364fb.c | 1 - drivers/video/platinumfb.c | 1 - drivers/video/stifb.c | 1 - drivers/video/valkyriefb.c | 1 - include/asm-arm/arch-ixp4xx/dma.h | 1 - include/rdma/ib_mad.h | 2 -- sound/core/init.c | 1 - sound/oss/au1550_ac97.c | 1 - sound/oss/soundcard.c | 1 + sound/pci/ca0106/ca0106_mixer.c | 2 +- sound/pci/ca0106/ca0106_proc.c | 2 +- sound/pci/cs46xx/dsp_spos.c | 1 - sound/pci/cs46xx/dsp_spos_scb_lib.c | 1 - sound/pci/hda/hda_generic.c | 1 - sound/pci/hda/hda_proc.c | 1 - sound/pci/hda/patch_atihdmi.c | 1 - sound/pci/hda/patch_si3054.c | 1 - sound/pci/hda/patch_via.c | 1 - 117 files changed, 7 insertions(+), 118 deletions(-) --- linux-2.6.21-rc5.orig/arch/alpha/kernel/err_common.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/alpha/kernel/err_common.c 2007-03-26 13:54:33.000000000 +0200 @@ -7,7 +7,6 @@ */ #include <linux/init.h> -#include <linux/pci.h> #include <linux/sched.h> #include <asm/io.h> --- linux-2.6.21-rc5.orig/arch/alpha/kernel/err_ev6.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/alpha/kernel/err_ev6.c 2007-03-26 13:54:33.000000000 +0200 @@ -7,7 +7,6 @@ */ #include <linux/init.h> -#include <linux/pci.h> #include <linux/sched.h> #include <asm/io.h> --- linux-2.6.21-rc5.orig/arch/alpha/kernel/err_ev7.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/alpha/kernel/err_ev7.c 2007-03-26 13:54:33.000000000 +0200 @@ -7,7 +7,6 @@ */ #include <linux/init.h> -#include <linux/pci.h> #include <linux/sched.h> #include <asm/io.h> --- linux-2.6.21-rc5.orig/arch/i386/kernel/cpu/cpufreq/speedstep-lib.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/i386/kernel/cpu/cpufreq/speedstep-lib.c 2007-03-26 13:54:33.000000000 +0200 @@ -13,7 +13,6 @@ #include <linux/moduleparam.h> #include <linux/init.h> #include <linux/cpufreq.h> -#include <linux/pci.h> #include <linux/slab.h> #include <asm/msr.h> --- linux-2.6.21-rc5.orig/arch/i386/kernel/cpu/cpufreq/speedstep-smi.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/i386/kernel/cpu/cpufreq/speedstep-smi.c 2007-03-26 13:54:33.000000000 +0200 @@ -17,10 +17,10 @@ #include <linux/moduleparam.h> #include <linux/init.h> #include <linux/cpufreq.h> -#include <linux/pci.h> #include <linux/slab.h> #include <linux/delay.h> #include <asm/ist.h> +#include <asm/io.h> #include "speedstep-lib.h" --- linux-2.6.21-rc5.orig/arch/ia64/sn/kernel/huberror.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/ia64/sn/kernel/huberror.c 2007-03-26 13:54:33.000000000 +0200 @@ -8,7 +8,6 @@ #include <linux/types.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <asm/delay.h> #include <asm/sn/sn_sal.h> #include "ioerror.h" --- linux-2.6.21-rc5.orig/arch/ia64/sn/kernel/xpnet.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/ia64/sn/kernel/xpnet.c 2007-03-26 13:54:33.000000000 +0200 @@ -24,7 +24,6 @@ #include <linux/module.h> #include <linux/kernel.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/ioport.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/arch/m68knommu/kernel/dma.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/m68knommu/kernel/dma.c 2007-03-26 13:54:33.000000000 +0200 @@ -8,7 +8,6 @@ #include <linux/types.h> #include <linux/mm.h> #include <linux/string.h> -#include <linux/pci.h> #include <asm/io.h> void *dma_alloc_coherent(struct device *dev, size_t size, --- linux-2.6.21-rc5.orig/arch/mips/lib/iomap.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/mips/lib/iomap.c 2007-03-26 13:54:33.000000000 +0200 @@ -6,7 +6,6 @@ * (C) Copyright 2007 MIPS Technologies, Inc. * written by Ralf Baechle <ralf@linux-mips.org> */ -#include <linux/pci.h> #include <linux/module.h> #include <asm/io.h> --- linux-2.6.21-rc5.orig/arch/powerpc/platforms/pseries/ras.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/powerpc/platforms/pseries/ras.c 2007-03-26 13:54:33.000000000 +0200 @@ -31,7 +31,6 @@ #include <linux/timex.h> #include <linux/init.h> #include <linux/slab.h> -#include <linux/pci.h> #include <linux/delay.h> #include <linux/irq.h> #include <linux/random.h> --- linux-2.6.21-rc5.orig/arch/ppc/8260_io/enet.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/ppc/8260_io/enet.c 2007-03-26 13:54:33.000000000 +0200 @@ -32,7 +32,6 @@ #include <linux/ioport.h> #include <linux/slab.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/delay.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/arch/ppc/8260_io/fcc_enet.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/ppc/8260_io/fcc_enet.c 2007-03-26 13:54:33.000000000 +0200 @@ -29,7 +29,6 @@ #include <linux/ioport.h> #include <linux/slab.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/delay.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/arch/ppc/8xx_io/enet.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/ppc/8xx_io/enet.c 2007-03-26 13:54:33.000000000 +0200 @@ -30,7 +30,6 @@ #include <linux/ioport.h> #include <linux/slab.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/delay.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/arch/ppc/syslib/ppc4xx_sgdma.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/ppc/syslib/ppc4xx_sgdma.c 2007-03-26 13:54:33.000000000 +0200 @@ -23,7 +23,6 @@ #include <linux/mm.h> #include <linux/init.h> #include <linux/module.h> -#include <linux/pci.h> #include <asm/system.h> #include <asm/io.h> --- linux-2.6.21-rc5.orig/arch/sh64/mach-cayman/iomap.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/sh64/mach-cayman/iomap.c 2007-03-26 13:54:33.000000000 +0200 @@ -9,7 +9,6 @@ * License. See the file "COPYING" in the main directory of this archive * for more details. */ -#include <linux/pci.h> #include <asm/io.h> #include <asm/cayman.h> --- linux-2.6.21-rc5.orig/arch/xtensa/kernel/xtensa_ksyms.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/xtensa/kernel/xtensa_ksyms.c 2007-03-26 13:54:33.000000000 +0200 @@ -18,7 +18,6 @@ #include <linux/interrupt.h> #include <asm/irq.h> #include <linux/in6.h> -#include <linux/pci.h> #include <linux/ide.h> #include <asm/uaccess.h> --- linux-2.6.21-rc5.orig/arch/xtensa/platform-iss/setup.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/arch/xtensa/platform-iss/setup.c 2007-03-26 13:54:33.000000000 +0200 @@ -20,7 +20,6 @@ #include <linux/init.h> #include <linux/errno.h> #include <linux/reboot.h> -#include <linux/pci.h> #include <linux/kdev_t.h> #include <linux/types.h> #include <linux/major.h> --- linux-2.6.21-rc5.orig/drivers/ata/pata_winbond.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/ata/pata_winbond.c 2007-03-26 13:54:33.000000000 +0200 @@ -8,7 +8,6 @@ #include <linux/kernel.h> #include <linux/module.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/blkdev.h> #include <linux/delay.h> --- linux-2.6.21-rc5.orig/drivers/atm/adummy.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/atm/adummy.c 2007-03-26 13:54:33.000000000 +0200 @@ -6,7 +6,6 @@ #include <linux/version.h> #include <linux/kernel.h> #include <linux/skbuff.h> -#include <linux/pci.h> #include <linux/errno.h> #include <linux/types.h> #include <linux/string.h> --- linux-2.6.21-rc5.orig/drivers/char/hw_random/via-rng.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/char/hw_random/via-rng.c 2007-03-26 13:54:33.000000000 +0200 @@ -26,7 +26,6 @@ #include <linux/module.h> #include <linux/kernel.h> -#include <linux/pci.h> #include <linux/hw_random.h> #include <asm/io.h> #include <asm/msr.h> --- linux-2.6.21-rc5.orig/drivers/char/pcmcia/synclink_cs.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/char/pcmcia/synclink_cs.c 2007-03-26 13:54:33.000000000 +0200 @@ -42,7 +42,6 @@ #include <linux/timer.h> #include <linux/time.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/tty.h> #include <linux/tty_flip.h> #include <linux/serial.h> --- linux-2.6.21-rc5.orig/drivers/char/tpm/tpm.h 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/char/tpm/tpm.h 2007-03-26 13:54:33.000000000 +0200 @@ -19,7 +19,6 @@ * */ #include <linux/module.h> -#include <linux/pci.h> #include <linux/delay.h> #include <linux/fs.h> #include <linux/sched.h> --- linux-2.6.21-rc5.orig/drivers/char/watchdog/sc1200wdt.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/char/watchdog/sc1200wdt.c 2007-03-26 13:54:33.000000000 +0200 @@ -38,7 +38,6 @@ #include <linux/init.h> #include <linux/pnp.h> #include <linux/fs.h> -#include <linux/pci.h> #include <asm/semaphore.h> #include <asm/io.h> --- linux-2.6.21-rc5.orig/drivers/char/watchdog/scx200_wdt.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/char/watchdog/scx200_wdt.c 2007-03-26 13:54:33.000000000 +0200 @@ -25,7 +25,7 @@ #include <linux/notifier.h> #include <linux/reboot.h> #include <linux/fs.h> -#include <linux/pci.h> +#include <linux/ioport.h> #include <linux/scx200.h> #include <asm/uaccess.h> --- linux-2.6.21-rc5.orig/drivers/i2c/busses/i2c-at91.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/i2c/busses/i2c-at91.c 2007-03-26 13:54:33.000000000 +0200 @@ -17,7 +17,6 @@ #include <linux/version.h> #include <linux/kernel.h> #include <linux/slab.h> -#include <linux/pci.h> #include <linux/types.h> #include <linux/delay.h> #include <linux/i2c.h> --- linux-2.6.21-rc5.orig/drivers/i2c/busses/i2c-mpc.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/i2c/busses/i2c-mpc.c 2007-03-26 13:54:33.000000000 +0200 @@ -17,7 +17,6 @@ #include <linux/module.h> #include <linux/sched.h> #include <linux/init.h> -#include <linux/pci.h> #include <linux/platform_device.h> #include <asm/io.h> --- linux-2.6.21-rc5.orig/drivers/i2c/busses/i2c-pca-isa.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/i2c/busses/i2c-pca-isa.c 2007-03-26 21:30:22.000000000 +0200 @@ -25,7 +25,6 @@ #include <linux/slab.h> #include <linux/init.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/wait.h> #include <linux/i2c.h> --- linux-2.6.21-rc5.orig/drivers/ieee1394/hosts.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/ieee1394/hosts.c 2007-03-26 13:54:33.000000000 +0200 @@ -15,7 +15,6 @@ #include <linux/list.h> #include <linux/init.h> #include <linux/slab.h> -#include <linux/pci.h> #include <linux/timer.h> #include <linux/jiffies.h> #include <linux/mutex.h> --- linux-2.6.21-rc5.orig/drivers/infiniband/core/cm.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/infiniband/core/cm.c 2007-03-26 13:54:33.000000000 +0200 @@ -40,7 +40,6 @@ #include <linux/err.h> #include <linux/idr.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/random.h> #include <linux/rbtree.h> #include <linux/spinlock.h> --- linux-2.6.21-rc5.orig/drivers/infiniband/core/iwcm.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/infiniband/core/iwcm.c 2007-03-26 13:54:33.000000000 +0200 @@ -39,7 +39,6 @@ #include <linux/err.h> #include <linux/idr.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/rbtree.h> #include <linux/spinlock.h> #include <linux/workqueue.h> --- linux-2.6.21-rc5.orig/drivers/infiniband/core/mad_priv.h 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/infiniband/core/mad_priv.h 2007-03-26 13:54:33.000000000 +0200 @@ -39,7 +39,6 @@ #include <linux/completion.h> #include <linux/err.h> -#include <linux/pci.h> #include <linux/workqueue.h> #include <rdma/ib_mad.h> #include <rdma/ib_smi.h> --- linux-2.6.21-rc5.orig/drivers/infiniband/core/multicast.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/infiniband/core/multicast.c 2007-03-26 13:54:33.000000000 +0200 @@ -34,7 +34,6 @@ #include <linux/dma-mapping.h> #include <linux/err.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/bitops.h> #include <linux/random.h> --- linux-2.6.21-rc5.orig/drivers/infiniband/core/sa_query.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/infiniband/core/sa_query.c 2007-03-26 13:54:33.000000000 +0200 @@ -40,7 +40,6 @@ #include <linux/random.h> #include <linux/spinlock.h> #include <linux/slab.h> -#include <linux/pci.h> #include <linux/dma-mapping.h> #include <linux/kref.h> #include <linux/idr.h> --- linux-2.6.21-rc5.orig/drivers/infiniband/core/user_mad.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/infiniband/core/user_mad.c 2007-03-26 13:54:33.000000000 +0200 @@ -40,7 +40,6 @@ #include <linux/err.h> #include <linux/fs.h> #include <linux/cdev.h> -#include <linux/pci.h> #include <linux/dma-mapping.h> #include <linux/poll.h> #include <linux/rwsem.h> --- linux-2.6.21-rc5.orig/drivers/infiniband/hw/ipath/ipath_fs.c 2007-03-26 13:54:18.000000000 +0200 +++ linux-2.6.21-rc5/drivers/infiniband/hw/ipath/ipath_fs.c 2007-03-26 13:54:33.000000000 +0200 @@ -38,7 +38,6 @@ #include <linux/pagemap.h> #include <linux/init.h> #include <linux/namei.h> -#include <linux/pci.h> #include "ipath_kernel.h" --- linux-2.6.21-rc5.orig/drivers/infiniband/hw/ipath/ipath_layer.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/infiniband/hw/ipath/ipath_layer.c 2007-03-26 13:54:33.000000000 +0200 @@ -37,7 +37,6 @@ */ #include <linux/io.h> -#include <linux/pci.h> #include <asm/byteorder.h> #include "ipath_kernel.h" --- linux-2.6.21-rc5.orig/drivers/infiniband/hw/ipath/ipath_stats.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/infiniband/hw/ipath/ipath_stats.c 2007-03-26 13:54:33.000000000 +0200 @@ -31,8 +31,6 @@ * SOFTWARE. */ -#include <linux/pci.h> - #include "ipath_kernel.h" struct infinipath_stats ipath_stats; --- linux-2.6.21-rc5.orig/drivers/infiniband/hw/ipath/ipath_sysfs.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/infiniband/hw/ipath/ipath_sysfs.c 2007-03-26 13:54:33.000000000 +0200 @@ -32,7 +32,6 @@ */ #include <linux/ctype.h> -#include <linux/pci.h> #include "ipath_kernel.h" #include "ipath_common.h" --- linux-2.6.21-rc5.orig/drivers/infiniband/hw/mthca/mthca_memfree.h 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/infiniband/hw/mthca/mthca_memfree.h 2007-03-26 13:54:33.000000000 +0200 @@ -38,7 +38,6 @@ #define MTHCA_MEMFREE_H #include <linux/list.h> -#include <linux/pci.h> #include <linux/mutex.h> #define MTHCA_ICM_CHUNK_LEN \ --- linux-2.6.21-rc5.orig/drivers/infiniband/ulp/ipoib/ipoib.h 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/infiniband/ulp/ipoib/ipoib.h 2007-03-26 13:54:33.000000000 +0200 @@ -41,7 +41,6 @@ #include <linux/skbuff.h> #include <linux/netdevice.h> #include <linux/workqueue.h> -#include <linux/pci.h> #include <linux/kref.h> #include <linux/if_infiniband.h> #include <linux/mutex.h> --- linux-2.6.21-rc5.orig/drivers/isdn/hisax/netjet.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/isdn/hisax/netjet.c 2007-03-26 13:54:33.000000000 +0200 @@ -19,7 +19,6 @@ #include "isac.h" #include "hscx.h" #include "isdnl1.h" -#include <linux/pci.h> #include <linux/interrupt.h> #include <linux/ppp_defs.h> #include <asm/io.h> --- linux-2.6.21-rc5.orig/drivers/isdn/hysdn/hysdn_proclog.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/isdn/hysdn/hysdn_proclog.c 2007-03-26 13:54:33.000000000 +0200 @@ -13,7 +13,6 @@ #include <linux/module.h> #include <linux/poll.h> #include <linux/proc_fs.h> -#include <linux/pci.h> #include <linux/smp_lock.h> #include "hysdn_defs.h" --- linux-2.6.21-rc5.orig/drivers/media/dvb/cinergyT2/cinergyT2.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/media/dvb/cinergyT2/cinergyT2.c 2007-03-26 13:54:33.000000000 +0200 @@ -26,11 +26,11 @@ #include <linux/module.h> #include <linux/slab.h> #include <linux/usb.h> -#include <linux/pci.h> #include <linux/input.h> #include <linux/dvb/frontend.h> #include <linux/mutex.h> #include <linux/mm.h> +#include <asm/io.h> #include "dmxdev.h" #include "dvb_demux.h" --- linux-2.6.21-rc5.orig/drivers/media/video/adv7170.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/media/video/adv7170.c 2007-03-26 13:54:33.000000000 +0200 @@ -37,7 +37,6 @@ #include <linux/major.h> #include <linux/slab.h> #include <linux/mm.h> -#include <linux/pci.h> #include <linux/signal.h> #include <asm/io.h> #include <asm/pgtable.h> --- linux-2.6.21-rc5.orig/drivers/media/video/adv7175.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/media/video/adv7175.c 2007-03-26 13:54:33.000000000 +0200 @@ -33,7 +33,6 @@ #include <linux/major.h> #include <linux/slab.h> #include <linux/mm.h> -#include <linux/pci.h> #include <linux/signal.h> #include <asm/io.h> #include <asm/pgtable.h> --- linux-2.6.21-rc5.orig/drivers/media/video/bt819.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/media/video/bt819.c 2007-03-26 13:54:33.000000000 +0200 @@ -37,7 +37,6 @@ #include <linux/major.h> #include <linux/slab.h> #include <linux/mm.h> -#include <linux/pci.h> #include <linux/signal.h> #include <asm/io.h> #include <asm/pgtable.h> --- linux-2.6.21-rc5.orig/drivers/media/video/bt856.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/media/video/bt856.c 2007-03-26 13:54:33.000000000 +0200 @@ -37,7 +37,6 @@ #include <linux/major.h> #include <linux/slab.h> #include <linux/mm.h> -#include <linux/pci.h> #include <linux/signal.h> #include <asm/io.h> #include <asm/pgtable.h> --- linux-2.6.21-rc5.orig/drivers/media/video/bt866.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/media/video/bt866.c 2007-03-26 13:54:33.000000000 +0200 @@ -37,7 +37,6 @@ #include <linux/major.h> #include <linux/slab.h> #include <linux/mm.h> -#include <linux/pci.h> #include <linux/signal.h> #include <asm/io.h> #include <asm/pgtable.h> --- linux-2.6.21-rc5.orig/drivers/media/video/cx88/cx88-tvaudio.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/media/video/cx88/cx88-tvaudio.c 2007-03-26 13:54:33.000000000 +0200 @@ -43,7 +43,6 @@ #include <linux/slab.h> #include <linux/mm.h> #include <linux/poll.h> -#include <linux/pci.h> #include <linux/signal.h> #include <linux/ioport.h> #include <linux/types.h> --- linux-2.6.21-rc5.orig/drivers/media/video/em28xx/em28xx-cards.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/media/video/em28xx/em28xx-cards.c 2007-03-26 13:54:33.000000000 +0200 @@ -23,7 +23,6 @@ #include <linux/init.h> #include <linux/module.h> -#include <linux/pci.h> #include <linux/delay.h> #include <linux/i2c.h> #include <linux/usb.h> --- linux-2.6.21-rc5.orig/drivers/media/video/saa7111.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/media/video/saa7111.c 2007-03-26 13:54:33.000000000 +0200 @@ -36,7 +36,6 @@ #include <linux/major.h> #include <linux/slab.h> #include <linux/mm.h> -#include <linux/pci.h> #include <linux/signal.h> #include <asm/io.h> #include <asm/pgtable.h> --- linux-2.6.21-rc5.orig/drivers/media/video/saa7114.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/media/video/saa7114.c 2007-03-26 13:54:33.000000000 +0200 @@ -39,7 +39,6 @@ #include <linux/slab.h> #include <linux/mm.h> -#include <linux/pci.h> #include <linux/signal.h> #include <asm/io.h> #include <asm/pgtable.h> --- linux-2.6.21-rc5.orig/drivers/media/video/saa711x.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/media/video/saa711x.c 2007-03-26 13:54:33.000000000 +0200 @@ -30,7 +30,6 @@ #include <linux/major.h> #include <linux/slab.h> #include <linux/mm.h> -#include <linux/pci.h> #include <linux/signal.h> #include <asm/io.h> #include <asm/pgtable.h> --- linux-2.6.21-rc5.orig/drivers/media/video/saa7185.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/media/video/saa7185.c 2007-03-26 13:54:33.000000000 +0200 @@ -33,7 +33,6 @@ #include <linux/major.h> #include <linux/slab.h> #include <linux/mm.h> -#include <linux/pci.h> #include <linux/signal.h> #include <asm/io.h> #include <asm/pgtable.h> --- linux-2.6.21-rc5.orig/drivers/misc/hdpuftrs/hdpu_cpustate.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/misc/hdpuftrs/hdpu_cpustate.c 2007-03-26 13:54:33.000000000 +0200 @@ -18,7 +18,6 @@ #include <linux/kernel.h> #include <linux/spinlock.h> #include <linux/miscdevice.h> -#include <linux/pci.h> #include <linux/proc_fs.h> #include <linux/platform_device.h> #include <asm/uaccess.h> --- linux-2.6.21-rc5.orig/drivers/misc/hdpuftrs/hdpu_nexus.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/misc/hdpuftrs/hdpu_nexus.c 2007-03-26 13:54:33.000000000 +0200 @@ -18,7 +18,6 @@ #include <linux/kernel.h> #include <linux/proc_fs.h> #include <linux/hdpu_features.h> -#include <linux/pci.h> #include <linux/platform_device.h> --- linux-2.6.21-rc5.orig/drivers/mtd/devices/doc2000.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/mtd/devices/doc2000.c 2007-03-26 13:54:33.000000000 +0200 @@ -13,7 +13,6 @@ #include <asm/io.h> #include <asm/uaccess.h> #include <linux/miscdevice.h> -#include <linux/pci.h> #include <linux/delay.h> #include <linux/slab.h> #include <linux/sched.h> --- linux-2.6.21-rc5.orig/drivers/mtd/devices/doc2001.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/mtd/devices/doc2001.c 2007-03-26 13:54:33.000000000 +0200 @@ -13,7 +13,6 @@ #include <asm/io.h> #include <asm/uaccess.h> #include <linux/miscdevice.h> -#include <linux/pci.h> #include <linux/delay.h> #include <linux/slab.h> #include <linux/init.h> --- linux-2.6.21-rc5.orig/drivers/mtd/devices/doc2001plus.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/mtd/devices/doc2001plus.c 2007-03-26 13:54:33.000000000 +0200 @@ -17,7 +17,6 @@ #include <asm/io.h> #include <asm/uaccess.h> #include <linux/miscdevice.h> -#include <linux/pci.h> #include <linux/delay.h> #include <linux/slab.h> #include <linux/init.h> --- linux-2.6.21-rc5.orig/drivers/mtd/devices/docecc.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/mtd/devices/docecc.c 2007-03-26 13:54:33.000000000 +0200 @@ -29,7 +29,6 @@ #include <asm/io.h> #include <asm/uaccess.h> #include <linux/miscdevice.h> -#include <linux/pci.h> #include <linux/delay.h> #include <linux/slab.h> #include <linux/init.h> --- linux-2.6.21-rc5.orig/drivers/mtd/inftlmount.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/mtd/inftlmount.c 2007-03-26 13:54:33.000000000 +0200 @@ -31,7 +31,6 @@ #include <asm/io.h> #include <asm/uaccess.h> #include <linux/miscdevice.h> -#include <linux/pci.h> #include <linux/delay.h> #include <linux/slab.h> #include <linux/init.h> --- linux-2.6.21-rc5.orig/drivers/mtd/nand/cs553x_nand.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/mtd/nand/cs553x_nand.c 2007-03-26 13:54:33.000000000 +0200 @@ -20,7 +20,6 @@ #include <linux/init.h> #include <linux/module.h> #include <linux/delay.h> -#include <linux/pci.h> #include <linux/mtd/mtd.h> #include <linux/mtd/nand.h> #include <linux/mtd/nand_ecc.h> --- linux-2.6.21-rc5.orig/drivers/mtd/nftlcore.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/mtd/nftlcore.c 2007-03-26 13:54:33.000000000 +0200 @@ -17,7 +17,6 @@ #include <asm/io.h> #include <asm/uaccess.h> #include <linux/miscdevice.h> -#include <linux/pci.h> #include <linux/delay.h> #include <linux/slab.h> #include <linux/init.h> --- linux-2.6.21-rc5.orig/drivers/net/atl1/atl1_param.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/atl1/atl1_param.c 2007-03-26 13:54:33.000000000 +0200 @@ -22,7 +22,6 @@ */ #include <linux/types.h> -#include <linux/pci.h> #include <linux/moduleparam.h> #include "atl1.h" --- linux-2.6.21-rc5.orig/drivers/net/au1000_eth.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/au1000_eth.c 2007-03-26 13:54:33.000000000 +0200 @@ -45,7 +45,6 @@ #include <linux/bitops.h> #include <linux/slab.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/netdevice.h> #include <linux/etherdevice.h> --- linux-2.6.21-rc5.orig/drivers/net/fec_8xx/fec_main.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/fec_8xx/fec_main.c 2007-03-26 13:54:33.000000000 +0200 @@ -19,7 +19,6 @@ #include <linux/ioport.h> #include <linux/slab.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/delay.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/drivers/net/fec_8xx/fec_mii.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/fec_8xx/fec_mii.c 2007-03-26 13:54:33.000000000 +0200 @@ -19,7 +19,6 @@ #include <linux/ioport.h> #include <linux/slab.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/delay.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/drivers/net/fs_enet/fs_enet-main.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/fs_enet/fs_enet-main.c 2007-03-26 13:54:33.000000000 +0200 @@ -24,7 +24,6 @@ #include <linux/ioport.h> #include <linux/slab.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/delay.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/drivers/net/fs_enet/mac-fcc.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/fs_enet/mac-fcc.c 2007-03-26 13:54:33.000000000 +0200 @@ -21,7 +21,6 @@ #include <linux/ioport.h> #include <linux/slab.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/delay.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/drivers/net/fs_enet/mac-fec.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/fs_enet/mac-fec.c 2007-03-26 13:54:33.000000000 +0200 @@ -21,7 +21,6 @@ #include <linux/ioport.h> #include <linux/slab.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/delay.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/drivers/net/fs_enet/mac-scc.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/fs_enet/mac-scc.c 2007-03-26 13:54:33.000000000 +0200 @@ -21,7 +21,6 @@ #include <linux/ioport.h> #include <linux/slab.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/delay.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/drivers/net/fs_enet/mii-bitbang.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/fs_enet/mii-bitbang.c 2007-03-26 13:54:33.000000000 +0200 @@ -22,7 +22,6 @@ #include <linux/ioport.h> #include <linux/slab.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/delay.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/drivers/net/fs_enet/mii-fec.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/fs_enet/mii-fec.c 2007-03-26 13:54:33.000000000 +0200 @@ -21,7 +21,6 @@ #include <linux/ioport.h> #include <linux/slab.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/delay.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/drivers/net/ibm_emac/ibm_emac_core.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/ibm_emac/ibm_emac_core.c 2007-03-26 13:54:33.000000000 +0200 @@ -27,7 +27,6 @@ #include <linux/delay.h> #include <linux/init.h> #include <linux/types.h> -#include <linux/pci.h> #include <linux/netdevice.h> #include <linux/etherdevice.h> #include <linux/skbuff.h> --- linux-2.6.21-rc5.orig/drivers/net/ixgb/ixgb_osdep.h 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/ixgb/ixgb_osdep.h 2007-03-26 13:54:33.000000000 +0200 @@ -34,7 +34,6 @@ #define _IXGB_OSDEP_H_ #include <linux/types.h> -#include <linux/pci.h> #include <linux/delay.h> #include <asm/io.h> #include <linux/interrupt.h> --- linux-2.6.21-rc5.orig/drivers/net/lasi_82596.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/lasi_82596.c 2007-03-26 13:54:33.000000000 +0200 @@ -81,7 +81,6 @@ #include <linux/etherdevice.h> #include <linux/skbuff.h> #include <linux/init.h> -#include <linux/pci.h> #include <linux/types.h> #include <linux/bitops.h> --- linux-2.6.21-rc5.orig/drivers/net/tokenring/madgemc.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/tokenring/madgemc.c 2007-03-26 13:54:33.000000000 +0200 @@ -23,7 +23,6 @@ static const char version[] = "madgemc.c #include <linux/mca.h> #include <linux/kernel.h> #include <linux/errno.h> -#include <linux/pci.h> #include <linux/init.h> #include <linux/netdevice.h> #include <linux/trdevice.h> --- linux-2.6.21-rc5.orig/drivers/net/tokenring/smctr.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/tokenring/smctr.c 2007-03-26 13:54:33.000000000 +0200 @@ -41,7 +41,6 @@ #include <linux/time.h> #include <linux/errno.h> #include <linux/init.h> -#include <linux/pci.h> #include <linux/mca-legacy.h> #include <linux/delay.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/drivers/net/tulip/21142.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/tulip/21142.c 2007-03-26 13:54:33.000000000 +0200 @@ -14,7 +14,6 @@ */ -#include <linux/pci.h> #include <linux/delay.h> #include "tulip.h" --- linux-2.6.21-rc5.orig/drivers/net/tulip/pnic.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/tulip/pnic.c 2007-03-26 13:54:33.000000000 +0200 @@ -15,7 +15,6 @@ */ #include <linux/kernel.h> -#include <linux/pci.h> #include <linux/jiffies.h> #include "tulip.h" --- linux-2.6.21-rc5.orig/drivers/net/tulip/pnic2.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/tulip/pnic2.c 2007-03-26 13:54:33.000000000 +0200 @@ -76,7 +76,6 @@ -#include <linux/pci.h> #include "tulip.h" #include <linux/delay.h> --- linux-2.6.21-rc5.orig/drivers/net/tulip/timer.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/tulip/timer.c 2007-03-26 13:54:33.000000000 +0200 @@ -14,7 +14,6 @@ */ -#include <linux/pci.h> #include "tulip.h" --- linux-2.6.21-rc5.orig/drivers/net/tulip/tulip.h 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/tulip/tulip.h 2007-03-26 13:54:33.000000000 +0200 @@ -22,6 +22,7 @@ #include <linux/netdevice.h> #include <linux/timer.h> #include <linux/delay.h> +#include <linux/pci.h> #include <asm/io.h> #include <asm/irq.h> --- linux-2.6.21-rc5.orig/drivers/net/wan/lmc/lmc_media.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/wan/lmc/lmc_media.c 2007-03-26 13:54:33.000000000 +0200 @@ -8,7 +8,6 @@ #include <linux/ioport.h> #include <linux/slab.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/in.h> #include <linux/if_arp.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/drivers/net/wan/lmc/lmc_proto.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/wan/lmc/lmc_proto.c 2007-03-26 13:54:33.000000000 +0200 @@ -27,7 +27,6 @@ #include <linux/ioport.h> #include <linux/slab.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/in.h> #include <linux/if_arp.h> #include <linux/netdevice.h> --- linux-2.6.21-rc5.orig/drivers/net/wan/pc300_tty.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/net/wan/pc300_tty.c 2007-03-26 13:54:33.000000000 +0200 @@ -38,7 +38,6 @@ #include <linux/module.h> #include <linux/kernel.h> -#include <linux/pci.h> #include <linux/errno.h> #include <linux/string.h> #include <linux/init.h> --- linux-2.6.21-rc5.orig/drivers/parisc/hppb.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/parisc/hppb.c 2007-03-26 13:54:33.000000000 +0200 @@ -22,8 +22,6 @@ #include <asm/hardware.h> #include <asm/parisc-device.h> -#include <linux/pci.h> - struct hppb_card { unsigned long hpa; struct resource mmio_region; --- linux-2.6.21-rc5.orig/drivers/pcmcia/cs.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/pcmcia/cs.c 2007-03-26 13:54:33.000000000 +0200 @@ -26,7 +26,6 @@ #include <linux/ioport.h> #include <linux/delay.h> #include <linux/pm.h> -#include <linux/pci.h> #include <linux/device.h> #include <linux/kthread.h> #include <linux/freezer.h> --- linux-2.6.21-rc5.orig/drivers/pcmcia/socket_sysfs.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/pcmcia/socket_sysfs.c 2007-03-26 13:54:33.000000000 +0200 @@ -22,7 +22,6 @@ #include <linux/ioport.h> #include <linux/delay.h> #include <linux/pm.h> -#include <linux/pci.h> #include <linux/device.h> #include <linux/mutex.h> #include <asm/system.h> --- linux-2.6.21-rc5.orig/drivers/sbus/sbus.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/sbus/sbus.c 2007-03-26 13:54:33.000000000 +0200 @@ -6,7 +6,6 @@ #include <linux/kernel.h> #include <linux/slab.h> #include <linux/init.h> -#include <linux/pci.h> #include <linux/device.h> #include <asm/system.h> --- linux-2.6.21-rc5.orig/drivers/scsi/aacraid/dpcsup.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/scsi/aacraid/dpcsup.c 2007-03-26 13:54:33.000000000 +0200 @@ -32,7 +32,6 @@ #include <linux/kernel.h> #include <linux/init.h> #include <linux/types.h> -#include <linux/pci.h> #include <linux/spinlock.h> #include <linux/slab.h> #include <linux/completion.h> --- linux-2.6.21-rc5.orig/drivers/scsi/aacraid/sa.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/scsi/aacraid/sa.c 2007-03-26 13:54:33.000000000 +0200 @@ -31,7 +31,6 @@ #include <linux/kernel.h> #include <linux/init.h> #include <linux/types.h> -#include <linux/pci.h> #include <linux/spinlock.h> #include <linux/slab.h> #include <linux/blkdev.h> --- linux-2.6.21-rc5.orig/drivers/scsi/aha1542.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/scsi/aha1542.c 2007-03-26 13:54:33.000000000 +0200 @@ -35,7 +35,6 @@ #include <linux/proc_fs.h> #include <linux/init.h> #include <linux/spinlock.h> -#include <linux/pci.h> #include <linux/isapnp.h> #include <linux/blkdev.h> #include <linux/mca.h> --- linux-2.6.21-rc5.orig/drivers/scsi/aic94xx/aic94xx_scb.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/scsi/aic94xx/aic94xx_scb.c 2007-03-26 13:54:33.000000000 +0200 @@ -24,7 +24,6 @@ * */ -#include <linux/pci.h> #include <scsi/scsi_host.h> #include "aic94xx.h" --- linux-2.6.21-rc5.orig/drivers/scsi/arcmsr/arcmsr_attr.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/scsi/arcmsr/arcmsr_attr.c 2007-03-26 13:54:33.000000000 +0200 @@ -49,7 +49,6 @@ #include <linux/init.h> #include <linux/errno.h> #include <linux/delay.h> -#include <linux/pci.h> #include <scsi/scsi_cmnd.h> #include <scsi/scsi_device.h> --- linux-2.6.21-rc5.orig/drivers/scsi/libsas/sas_expander.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/scsi/libsas/sas_expander.c 2007-03-26 13:54:33.000000000 +0200 @@ -22,7 +22,6 @@ * */ -#include <linux/pci.h> #include <linux/scatterlist.h> #include "sas_internal.h" --- linux-2.6.21-rc5.orig/drivers/scsi/libsrp.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/scsi/libsrp.c 2007-03-26 13:54:33.000000000 +0200 @@ -22,7 +22,6 @@ #include <linux/kfifo.h> #include <linux/scatterlist.h> #include <linux/dma-mapping.h> -#include <linux/pci.h> #include <scsi/scsi.h> #include <scsi/scsi_cmnd.h> #include <scsi/scsi_tcq.h> --- linux-2.6.21-rc5.orig/drivers/usb/net/kaweth.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/usb/net/kaweth.c 2007-03-26 13:54:33.000000000 +0200 @@ -55,7 +55,6 @@ #include <linux/usb.h> #include <linux/types.h> #include <linux/ethtool.h> -#include <linux/pci.h> #include <linux/dma-mapping.h> #include <linux/wait.h> #include <asm/uaccess.h> --- linux-2.6.21-rc5.orig/drivers/video/aty/radeon_i2c.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/video/aty/radeon_i2c.c 2007-03-26 21:30:25.000000000 +0200 @@ -1,7 +1,6 @@ #include <linux/module.h> #include <linux/kernel.h> #include <linux/delay.h> -#include <linux/pci.h> #include <linux/fb.h> --- linux-2.6.21-rc5.orig/drivers/video/g364fb.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/video/g364fb.c 2007-03-26 13:54:33.000000000 +0200 @@ -26,7 +26,6 @@ #include <linux/interrupt.h> #include <linux/fb.h> #include <linux/init.h> -#include <linux/pci.h> #include <asm/io.h> #include <asm/jazz.h> --- linux-2.6.21-rc5.orig/drivers/video/platinumfb.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/video/platinumfb.c 2007-03-26 13:54:33.000000000 +0200 @@ -28,7 +28,6 @@ #include <linux/interrupt.h> #include <linux/fb.h> #include <linux/init.h> -#include <linux/pci.h> #include <linux/nvram.h> #include <asm/io.h> #include <asm/prom.h> --- linux-2.6.21-rc5.orig/drivers/video/stifb.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/video/stifb.c 2007-03-26 13:54:33.000000000 +0200 @@ -64,7 +64,6 @@ #include <linux/fb.h> #include <linux/init.h> #include <linux/ioport.h> -#include <linux/pci.h> #include <asm/grfioctl.h> /* for HP-UX compatibility */ #include <asm/uaccess.h> --- linux-2.6.21-rc5.orig/drivers/video/valkyriefb.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/drivers/video/valkyriefb.c 2007-03-26 13:54:33.000000000 +0200 @@ -51,7 +51,6 @@ #include <linux/fb.h> #include <linux/selection.h> #include <linux/init.h> -#include <linux/pci.h> #include <linux/nvram.h> #include <linux/adb.h> #include <linux/cuda.h> --- linux-2.6.21-rc5.orig/include/asm-arm/arch-ixp4xx/dma.h 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/include/asm-arm/arch-ixp4xx/dma.h 2007-03-26 13:54:33.000000000 +0200 @@ -12,7 +12,6 @@ #define __ASM_ARCH_DMA_H #include <linux/device.h> -#include <linux/pci.h> #include <asm/page.h> #include <asm/sizes.h> #include <asm/hardware.h> --- linux-2.6.21-rc5.orig/include/rdma/ib_mad.h 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/include/rdma/ib_mad.h 2007-03-26 13:54:33.000000000 +0200 @@ -39,8 +39,6 @@ #if !defined( IB_MAD_H ) #define IB_MAD_H -#include <linux/pci.h> - #include <rdma/ib_verbs.h> /* Management base version */ --- linux-2.6.21-rc5.orig/sound/core/init.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/sound/core/init.c 2007-03-26 13:54:33.000000000 +0200 @@ -26,7 +26,6 @@ #include <linux/slab.h> #include <linux/time.h> #include <linux/ctype.h> -#include <linux/pci.h> #include <linux/pm.h> #include <sound/core.h> --- linux-2.6.21-rc5.orig/sound/oss/au1550_ac97.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/sound/oss/au1550_ac97.c 2007-03-26 13:54:33.000000000 +0200 @@ -47,7 +47,6 @@ #include <linux/interrupt.h> #include <linux/kernel.h> #include <linux/poll.h> -#include <linux/pci.h> #include <linux/bitops.h> #include <linux/spinlock.h> #include <linux/smp_lock.h> --- linux-2.6.21-rc5.orig/sound/oss/soundcard.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/sound/oss/soundcard.c 2007-03-26 13:54:33.000000000 +0200 @@ -44,6 +44,7 @@ #include <linux/smp_lock.h> #include <linux/module.h> #include <linux/mm.h> +#include <linux/device.h> /* * This ought to be moved into include/asm/dma.h --- linux-2.6.21-rc5.orig/sound/pci/ca0106/ca0106_mixer.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/sound/pci/ca0106/ca0106_mixer.c 2007-03-26 13:54:33.000000000 +0200 @@ -62,7 +62,6 @@ #include <linux/delay.h> #include <linux/init.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/slab.h> #include <linux/moduleparam.h> #include <sound/core.h> @@ -71,6 +70,7 @@ #include <sound/ac97_codec.h> #include <sound/info.h> #include <sound/tlv.h> +#include <asm/io.h> #include "ca0106.h" --- linux-2.6.21-rc5.orig/sound/pci/ca0106/ca0106_proc.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/sound/pci/ca0106/ca0106_proc.c 2007-03-26 13:54:33.000000000 +0200 @@ -64,7 +64,6 @@ #include <linux/delay.h> #include <linux/init.h> #include <linux/interrupt.h> -#include <linux/pci.h> #include <linux/slab.h> #include <linux/moduleparam.h> #include <sound/core.h> @@ -73,6 +72,7 @@ #include <sound/ac97_codec.h> #include <sound/info.h> #include <sound/asoundef.h> +#include <asm/io.h> #include "ca0106.h" --- linux-2.6.21-rc5.orig/sound/pci/cs46xx/dsp_spos.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/sound/pci/cs46xx/dsp_spos.c 2007-03-26 13:54:33.000000000 +0200 @@ -23,7 +23,6 @@ #include <sound/driver.h> #include <asm/io.h> #include <linux/delay.h> -#include <linux/pci.h> #include <linux/pm.h> #include <linux/init.h> #include <linux/slab.h> --- linux-2.6.21-rc5.orig/sound/pci/cs46xx/dsp_spos_scb_lib.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/sound/pci/cs46xx/dsp_spos_scb_lib.c 2007-03-26 13:54:33.000000000 +0200 @@ -24,7 +24,6 @@ #include <sound/driver.h> #include <asm/io.h> #include <linux/delay.h> -#include <linux/pci.h> #include <linux/pm.h> #include <linux/init.h> #include <linux/slab.h> --- linux-2.6.21-rc5.orig/sound/pci/hda/hda_generic.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/sound/pci/hda/hda_generic.c 2007-03-26 13:54:33.000000000 +0200 @@ -23,7 +23,6 @@ #include <sound/driver.h> #include <linux/init.h> #include <linux/slab.h> -#include <linux/pci.h> #include <sound/core.h> #include "hda_codec.h" #include "hda_local.h" --- linux-2.6.21-rc5.orig/sound/pci/hda/hda_proc.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/sound/pci/hda/hda_proc.c 2007-03-26 13:54:33.000000000 +0200 @@ -23,7 +23,6 @@ #include <sound/driver.h> #include <linux/init.h> -#include <linux/pci.h> #include <sound/core.h> #include "hda_codec.h" #include "hda_local.h" --- linux-2.6.21-rc5.orig/sound/pci/hda/patch_atihdmi.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/sound/pci/hda/patch_atihdmi.c 2007-03-26 13:54:33.000000000 +0200 @@ -25,7 +25,6 @@ #include <linux/init.h> #include <linux/delay.h> #include <linux/slab.h> -#include <linux/pci.h> #include <sound/core.h> #include "hda_codec.h" #include "hda_local.h" --- linux-2.6.21-rc5.orig/sound/pci/hda/patch_si3054.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/sound/pci/hda/patch_si3054.c 2007-03-26 13:54:33.000000000 +0200 @@ -26,7 +26,6 @@ #include <linux/init.h> #include <linux/delay.h> #include <linux/slab.h> -#include <linux/pci.h> #include <sound/core.h> #include "hda_codec.h" #include "hda_local.h" --- linux-2.6.21-rc5.orig/sound/pci/hda/patch_via.c 2007-03-26 13:51:51.000000000 +0200 +++ linux-2.6.21-rc5/sound/pci/hda/patch_via.c 2007-03-26 13:54:33.000000000 +0200 @@ -35,7 +35,6 @@ #include <linux/init.h> #include <linux/delay.h> #include <linux/slab.h> -#include <linux/pci.h> #include <sound/core.h> #include "hda_codec.h" #include "hda_local.h" -- Jean Delvare ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-26 19:35 ` 2.6.21-rc4-mm1 Jean Delvare @ 2007-03-26 23:26 ` Greg KH 0 siblings, 0 replies; 146+ messages in thread From: Greg KH @ 2007-03-26 23:26 UTC (permalink / raw) To: Jean Delvare; +Cc: Badari Pulavarty, Greg KH, Andrew Morton, LKML On Mon, Mar 26, 2007 at 09:35:48PM +0200, Jean Delvare wrote: > > Greg, please update your copy with this version of the patch. The only > change is that sound/ppc/beep.c is removed from the patch. Done. thanks, greg k-h ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton ` (22 preceding siblings ...) 2007-03-26 20:05 ` 2.6.21-rc4-mm1 Badari Pulavarty @ 2007-03-26 21:57 ` Badari Pulavarty 2007-03-26 22:22 ` 2.6.21-rc4-mm1 Andrew Morton 23 siblings, 1 reply; 146+ messages in thread From: Badari Pulavarty @ 2007-03-26 21:57 UTC (permalink / raw) To: Andrew Morton; +Cc: lkml On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote: > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > Will appear later at > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > Panics my x86-64 box. 2.6.21-rc4 works fine. Ideas on where to start ? Bisect ? Thanks, Badari .. ReiserFS: hda2: found reiserfs format "3.6" with standard journal ReiserFS: hda2: using ordered data mode ReiserFS: hda2: journal params: device hda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: hda2: checking transaction log (hda2) ReiserFS: hda2: Using r5 hash to sort names VFS: Mounted root (reiserfs filesystem) readonly. Freeing unused kernel memory: 376k freed INIT: version 2.86 booting Unable to handle kernel NULL pointer dereference at 0000000000000020 RIP: [<ffffffff804ec090>] __sched_text_start+0x460/0x889 PGD 1c1898067 PUD 1c1897067 PMD 0 Oops: 0000 [1] SMP last sysfs file: block/hda/range CPU 3 Modules linked in: Pid: 900, comm: boot Not tainted 2.6.21-rc4-mm1 #1 RIP: 0010:[<ffffffff804ec090>] [<ffffffff804ec090>] __sched_text_start +0x460/0x889 RSP: 0018:ffff8101014dfee0 EFLAGS: 00010086 RAX: 0000000000000001 RBX: ffff8101c0010218 RCX: 0000000000000000 RDX: ffff8101c0010ae8 RSI: 0000000000000000 RDI: ffffffffffffffd0 RBP: ffff8101014dff70 R08: 000000000000008c R09: ffff8101c0010ad8 R10: 000000000000001c R11: ffffffff802099be R12: ffff8101c000f780 R13: 0000000000000001 R14: 0000000a7bcffd6e R15: 0000000000000003 FS: 00002b9ef1d40ae0(0000) GS:ffff8101c07b6e40(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000020 CR3: 0000000100f8d000 CR4: 00000000000006e0 Process boot (pid: 900, threadinfo ffff8101014de000, task ffff8101014dd490) Stack: 0000038c802848cf ffff8101014dfef8 ffffffff80238d82 ffff8101014dd490 ffffffffffffffd0 ffff8101014dd630 0000000000000000 00007fffb955ff80 00007fffb9560090 0000000000000000 ffffffff802099be ffff8101014dff48 Call Trace: [<ffffffff80238d82>] recalc_sigpending+0x12/0x20 [<ffffffff802099be>] system_call+0x7e/0x83 [<ffffffff80207ef3>] sys_clone+0x23/0x30 [<ffffffff80209a28>] sysret_careful+0xd/0x10 Code: 48 39 47 50 74 38 48 c7 47 40 00 00 00 00 48 63 56 f4 49 8b RIP [<ffffffff804ec090>] __sched_text_start+0x460/0x889 RSP <ffff8101014dfee0> CR2: 0000000000000020 ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-26 21:57 ` 2.6.21-rc4-mm1 Badari Pulavarty @ 2007-03-26 22:22 ` Andrew Morton 2007-03-26 23:43 ` 2.6.21-rc4-mm1 Badari Pulavarty 0 siblings, 1 reply; 146+ messages in thread From: Andrew Morton @ 2007-03-26 22:22 UTC (permalink / raw) To: Badari Pulavarty; +Cc: lkml, Con Kolivas On Mon, 26 Mar 2007 13:57:57 -0800 Badari Pulavarty <pbadari@gmail.com> wrote: > On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote: > > Temporarily at > > > > http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/ > > > > Will appear later at > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/ > > > > > Panics my x86-64 box. 2.6.21-rc4 works fine. > Ideas on where to start ? Bisect ? > > Thanks, > Badari > > .. > ReiserFS: hda2: found reiserfs format "3.6" with standard journal > ReiserFS: hda2: using ordered data mode > ReiserFS: hda2: journal params: device hda2, size 8192, journal first > block 18, max trans len 1024, max batch 900, max commit age 30, max > trans age 30 > ReiserFS: hda2: checking transaction log (hda2) > ReiserFS: hda2: Using r5 hash to sort names > VFS: Mounted root (reiserfs filesystem) readonly. > Freeing unused kernel memory: 376k freed > INIT: version 2.86 booting > Unable to handle kernel NULL pointer dereference at 0000000000000020 > RIP: > [<ffffffff804ec090>] __sched_text_start+0x460/0x889 > PGD 1c1898067 PUD 1c1897067 PMD 0 > Oops: 0000 [1] SMP > last sysfs file: block/hda/range > CPU 3 > Modules linked in: > Pid: 900, comm: boot Not tainted 2.6.21-rc4-mm1 #1 > RIP: 0010:[<ffffffff804ec090>] [<ffffffff804ec090>] __sched_text_start This is a very popular oops, caused by the rsdl scheduler. I don't _think_ we yet know exactly why it is happening. Con, did you get to the bottom of this? We don't know why it confused kallsyms either. I'll try to shove rc5-mm1 out the door this evening, minus rsdl. And -mm2, with rsdl. ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 2007-03-26 22:22 ` 2.6.21-rc4-mm1 Andrew Morton @ 2007-03-26 23:43 ` Badari Pulavarty 0 siblings, 0 replies; 146+ messages in thread From: Badari Pulavarty @ 2007-03-26 23:43 UTC (permalink / raw) To: Andrew Morton; +Cc: lkml, Con Kolivas On Mon, 2007-03-26 at 15:22 -0700, Andrew Morton wrote: .. > > Unable to handle kernel NULL pointer dereference at 0000000000000020 > > RIP: > > [<ffffffff804ec090>] __sched_text_start+0x460/0x889 > > PGD 1c1898067 PUD 1c1897067 PMD 0 > > Oops: 0000 [1] SMP > > last sysfs file: block/hda/range > > CPU 3 > > Modules linked in: > > Pid: 900, comm: boot Not tainted 2.6.21-rc4-mm1 #1 > > RIP: 0010:[<ffffffff804ec090>] [<ffffffff804ec090>] __sched_text_start > > This is a very popular oops, caused by the rsdl scheduler. I don't _think_ > we yet know exactly why it is happening. Con, did you get to the bottom > of this? > > We don't know why it confused kallsyms either. > > I'll try to shove rc5-mm1 out the door this evening, minus rsdl. And > -mm2, with rsdl. Okay, my ppc64 box hangs on boot. It could be different. I will wait till rc5-mm1 for debugging that one. Thanks, Badari ... md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. ReiserFS: sda2: found reiserfs format "3.6" with standard journal ReiserFS: sda2: using ordered data mode ReiserFS: sda2: journal params: device sda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: sda2: checking transaction log (sda2) ReiserFS: sda2: Using r5 hash to sort names VFS: Mounted root (reiserfs filesystem) readonly. Freeing unused kernel memory: 272k freed Warning: unable to open an initial console. ioctl32(showconsole:1020): Unknown cmd fd(0) cmd(40045432){00} arg (ffecdb48) on /dev/tty0 ioctl32(showconsole:1048): Unknown cmd fd(0) cmd(40045432){00} arg (ffb4aad8) on /dev/tty0 PDC20275: IDE controller at PCI slot 0002:d0:01.0 PDC20275: chipset revision 1 PDC20275: PLL input clock is 32814 kHz PDC20275: 100% native mode on irq 119 ide2: BM-DMA at 0x2eec00-0x2eec07, BIOS settings: hde:pio, hdf:pio ide3: BM-DMA at 0x2eec08-0x2eec0f, BIOS settings: hdg:pio, hdh:pio scsi 0:0:15:0: Attached scsi generic sg0 type 13 scsi 0:255:255:255: Attached scsi generic sg1 type 31 sd 1:0:4:0: Attached scsi generic sg2 type 0 sd 1:0:5:0: Attached scsi generic sg3 type 0 scsi 1:0:15:0: Attached scsi generic sg4 type 13 scsi 1:255:255:255: Attached scsi generic sg5 type 31 hde: IBM DROM00205, ATAPI CD/DVD-ROM drive ide2 at 0x2ee400-0x2ee407,0x2edc02 on irq 119 hde: ATAPI 24X DVD-ROM drive, 256kB Cache Uniform CD-ROM driver Revision: 3.20 device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm- devel@redhat.com ioctl32(showconsole:1918): Unknown cmd fd(0) cmd(40045432){00} arg (fff00ad8) on /dev/tty0 loop: loaded (max 8 devices) ioctl32(showconsole:2091): Unknown cmd fd(0) cmd(40045432){00} arg (fff71ae8) on /dev/tty0 Adding 1050616k swap on /dev/sdb2. Priority:-1 extents:1 across:1050616k ioctl32(showconsole:2137): Unknown cmd fd(0) cmd(40045432){00} arg (ffdd7b28) on /dev/tty0 e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX audit(1174945021.442:2): audit_pid=2735 old=0 by auid=4294967295 ^ permalink raw reply [flat|nested] 146+ messages in thread
* Re: 2.6.21-rc4-mm1 @ 2007-03-21 22:45 Nicolas Mailhot 0 siblings, 0 replies; 146+ messages in thread From: Nicolas Mailhot @ 2007-03-21 22:45 UTC (permalink / raw) To: Matt Mackall, Larry Finger, Andrew Morton; +Cc: linux-kernel Firmware loading is broken for all subsystems, not just network → http://bugzilla.kernel.org/show_bug.cgi?id=8239 -- Nicolas Mailhot ^ permalink raw reply [flat|nested] 146+ messages in thread
end of thread, other threads:[~2007-05-08 19:11 UTC | newest]
Thread overview: 146+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-20 4:56 2.6.21-rc4-mm1 Andrew Morton
2007-03-20 7:54 ` 2.6.21-rc4-mm1 Michal Piotrowski
2007-03-20 9:45 ` 2.6.21-rc4-mm1 Andy Whitcroft
2007-03-22 8:41 ` 2.6.21-rc4-mm1 Andy Whitcroft
2007-03-22 9:48 ` 2.6.21-rc4-mm1 Andy Whitcroft
2007-03-22 10:04 ` 2.6.21-rc4-mm1 Con Kolivas
2007-03-22 17:07 ` 2.6.21-rc4-mm1 Andy Whitcroft
2007-03-22 18:17 ` 2.6.21-rc4-mm1 Andy Whitcroft
2007-03-22 22:14 ` 2.6.21-rc4-mm1 Con Kolivas
2007-03-23 6:18 ` 2.6.21-rc4-mm1 Con Kolivas
2007-03-23 8:45 ` 2.6.21-rc4-mm1 Andy Whitcroft
2007-03-23 12:28 ` 2.6.21-rc4-mm1 Andy Whitcroft
2007-03-23 15:53 ` 2.6.21-rc4-mm1 Fortier,Vincent [Montreal]
2007-03-23 21:45 ` 2.6.21-rc4-mm1 Con Kolivas
2007-03-23 23:26 ` debug rsdl 0.33 Con Kolivas
2007-03-25 12:27 ` Andy Whitcroft
2007-03-25 18:28 ` Torsten Kaiser
2007-03-25 22:01 ` Andrew Morton
2007-03-25 22:49 ` Con Kolivas
2007-03-25 22:59 ` Con Kolivas
2007-03-26 7:49 ` Andy Whitcroft
2007-03-26 15:28 ` Andy Whitcroft
2007-03-26 16:12 ` Con Kolivas
2007-03-20 10:52 ` 2.6.21-rc4-mm1 [PATCH] init/missing_syscalls.h fix Stephane Jourdois
2007-03-20 14:31 ` 2.6.21-rc4-mm1 Jiri Slaby
2007-03-20 16:09 ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-20 18:38 ` 2.6.21-rc4-mm1 Pavel Machek
2007-03-20 19:40 ` 2.6.21-rc4-mm1 Jiri Slaby
2007-03-20 19:56 ` 2.6.21-rc4-mm1 Pavel Machek
2007-03-20 20:13 ` 2.6.21-rc4-mm1 Jiri Slaby
2007-03-20 20:21 ` [linux-pm] 2.6.21-rc4-mm1 Pavel Machek
2007-03-20 20:58 ` Rafael J. Wysocki
2007-03-20 20:58 ` Jiri Slaby
2007-03-20 21:06 ` Rafael J. Wysocki
[not found] ` <200703210149.33240.rjw@sisk.pl>
2007-03-21 1:23 ` [linux-pm] 2.6.21-rc4-mm1: freezing of processes broken Eric W. Biederman
2007-03-21 2:47 ` sukadev
2007-03-21 3:13 ` Nigel Cunningham
2007-03-21 14:23 ` Oleg Nesterov
2007-03-21 14:45 ` Rafael J. Wysocki
2007-03-21 16:20 ` Andrew Morton
2007-03-21 16:55 ` Oleg Nesterov
2007-03-21 17:08 ` Andrew Morton
2007-03-21 18:07 ` sukadev
2007-03-21 18:16 ` Eric W. Biederman
2007-03-21 18:23 ` sukadev
2007-03-21 17:15 ` Oleg Nesterov
2007-03-21 12:08 ` Rafael J. Wysocki
2007-03-20 20:12 ` 2.6.21-rc4-mm1 Rafael J. Wysocki
2007-03-20 16:36 ` 2.6.21-rc4-mm1 J.A. Magallón
2007-03-21 0:14 ` 2.6.21-rc4-mm1 J.A. Magallón
2007-03-20 17:31 ` 2.6.21-rc4-mm1 Randy Dunlap
2007-03-20 19:20 ` 2.6.21-rc4-mm1 Kees Cook
2007-03-20 20:42 ` 2.6.21-rc4-mm1 Stéphane Jourdois
2007-03-20 20:50 ` 2.6.21-rc4-mm1 Randy Dunlap
2007-03-21 5:47 ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-21 11:25 ` 2.6.21-rc4-mm1 David Woodhouse
2007-03-21 11:59 ` 2.6.21-rc4-mm1 Sam Ravnborg
2007-03-22 9:17 ` 2.6.21-rc4-mm1 David Woodhouse
2007-03-22 11:41 ` 2.6.21-rc4-mm1 Sam Ravnborg
2007-03-22 16:25 ` 2.6.21-rc4-mm1 David Woodhouse
2007-03-22 16:28 ` 2.6.21-rc4-mm1 Sam Ravnborg
2007-03-21 22:19 ` 2.6.21-rc4-mm1 Sam Ravnborg
2007-03-21 22:22 ` [PATCH 1/3] kbuild: complain about missing system calls Sam Ravnborg
2007-05-07 22:29 ` Tony Luck
2007-05-07 22:39 ` David Woodhouse
2007-05-07 22:51 ` Luck, Tony
2007-05-08 18:24 ` Sam Ravnborg
2007-05-08 18:35 ` Luck, Tony
2007-05-08 18:49 ` Sam Ravnborg
2007-03-21 22:23 ` [PATCH 2/3] kbuild: ignore more i386 legacy syscalls Sam Ravnborg
2007-03-21 22:24 ` [PATCH 3/3] kbuild: exempt more syscalls from warnings, for x86_64 and ARM Sam Ravnborg
2007-03-21 23:01 ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-22 8:54 ` 2.6.21-rc4-mm1 Sam Ravnborg
2007-03-20 18:09 ` [PATCH] utrace: make an inline void Randy Dunlap
2007-03-21 1:48 ` Roland McGrath
2007-03-20 20:49 ` 2.6.21-rc4-mm1: multiple definition of `queue_pushbutton_work' Adrian Bunk
2007-03-21 18:45 ` Kristen Carlson Accardi
2007-03-20 21:04 ` 2.6.21-rc4-mm1 J.A. Magallón
2007-03-20 23:10 ` FireWire update in -mm (was 2.6.21-rc4-mm1) Stefan Richter
2007-03-20 23:49 ` 2.6.21-rc4-mm1 Randy Dunlap
2007-03-21 1:47 ` 2.6.21-rc4-mm1 Randy Dunlap
2007-03-21 18:36 ` 2.6.21-rc4-mm1 Greg KH
[not found] ` <1174433034.62033.16.camel@localhost>
2007-03-21 6:36 ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-21 9:52 ` 2.6.21-rc4-mm1 Edward Shishkin
2007-03-21 14:12 ` [Bluez-devel] 2.6.21-rc4-mm1 Marcel Holtmann
2007-03-23 19:45 ` Zan Lynx
2007-03-21 16:13 ` 2.6.21-rc4-mm1 Larry Finger
2007-03-23 19:40 ` 2.6.21-rc4-mm1 Zan Lynx
2007-03-24 1:49 ` 2.6.21-rc4-mm1 Larry Finger
2007-03-21 18:14 ` 2.6.21-rc4-mm1 Larry Finger
2007-03-21 18:34 ` 2.6.21-rc4-mm1 Michael Buesch
2007-03-21 19:00 ` 2.6.21-rc4-mm1 John W. Linville
2007-03-21 18:59 ` 2.6.21-rc4-mm1 John W. Linville
2007-03-21 20:22 ` 2.6.21-rc4-mm1 Matt Mackall
2007-03-21 20:48 ` 2.6.21-rc4-mm1 Larry Finger
2007-03-21 21:03 ` 2.6.21-rc4-mm1 Larry Finger
2007-03-21 21:39 ` 2.6.21-rc4-mm1 Randy Dunlap
2007-03-21 21:45 ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-22 7:39 ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-22 11:35 ` 2.6.21-rc4-mm1 Cornelia Huck
[not found] ` <4602752A.5050109@lwfinger.net>
2007-03-22 17:10 ` 2.6.21-rc4-mm1 Cornelia Huck
2007-03-22 18:55 ` 2.6.21-rc4-mm1 Larry Finger
2007-03-23 10:10 ` 2.6.21-rc4-mm1 Cornelia Huck
2007-03-23 15:00 ` 2.6.21-rc4-mm1 Larry Finger
2007-03-24 5:06 ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-26 9:09 ` 2.6.21-rc4-mm1 Cornelia Huck
2007-03-26 9:22 ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-26 10:34 ` 2.6.21-rc4-mm1 Eric Rannaud
2007-03-26 10:44 ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-27 9:25 ` 2.6.21-rc4-mm1 Kay Sievers
2007-03-27 17:17 ` 2.6.21-rc4-mm1 Cornelia Huck
2007-03-28 1:26 ` 2.6.21-rc4-mm1 Eric Rannaud
2007-03-28 8:25 ` 2.6.21-rc4-mm1 Cornelia Huck
2007-03-24 22:32 ` 2.6.21-rc4-mm1 Matt Mackall
2007-03-21 18:49 ` 2.6.21-rc4-mm1 - problem with cpuidle routine Larry Finger
2007-03-21 20:38 ` Andrew Morton
2007-03-22 0:33 ` Venkatesh Pallipadi
2007-03-30 1:25 ` 2.6.21-rc4-mm1 and rc5-mm2 " Ed Sweetman
2007-03-30 2:17 ` Lee Revell
2007-03-21 20:39 ` 2.6.21-rc4-mm1 " Venki Pallipadi
2007-03-21 10:14 ` 2.6.21-rc4-mm1 Reuben Farrelly
2007-03-22 23:27 ` 2.6.21-rc4-mm1 J.A. Magallón
2007-03-23 1:41 ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-26 20:31 ` 2.6.21-rc4-mm1 J.A. Magallón
2007-03-24 13:06 ` [-mm patch] lguest: #if 0 check_bug_kill() Adrian Bunk
2007-03-25 7:33 ` Rusty Russell
2007-03-25 14:57 ` [-mm patch] lguest: remove check_bug_kill() Adrian Bunk
2007-03-24 13:06 ` [-mm patch] drivers/scsi/constants.c: make 2 functions static Adrian Bunk
2007-03-24 16:11 ` Douglas Gilbert
2007-03-24 17:02 ` Adrian Bunk
2007-03-24 13:07 ` [-mm patch] fs/revoke.c: cleanups (and bugfix for 64bit systems) Adrian Bunk
2007-03-24 13:15 ` Pekka Enberg
2007-03-24 13:07 ` [-mm patch] unexport bio_{,un}map_user Adrian Bunk
2007-03-25 14:58 ` [-mm patch] drivers/eisa/pci_eisa.c:pci_eisa_init() should be init Adrian Bunk
2007-03-26 0:24 ` Wrong IDE cable detection in libata [Re: 2.6.21-rc4-mm1] J.A. Magallón
2007-03-26 11:01 ` Tejun Heo
2007-03-26 20:18 ` J.A. Magallón
2007-03-26 19:47 ` 2.6.21-rc4-mm1 Badari Pulavarty
2007-03-26 23:29 ` 2.6.21-rc4-mm1 Paul Mackerras
2007-03-26 20:05 ` 2.6.21-rc4-mm1 Badari Pulavarty
2007-03-26 19:35 ` 2.6.21-rc4-mm1 Jean Delvare
2007-03-26 23:26 ` 2.6.21-rc4-mm1 Greg KH
2007-03-26 21:57 ` 2.6.21-rc4-mm1 Badari Pulavarty
2007-03-26 22:22 ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-26 23:43 ` 2.6.21-rc4-mm1 Badari Pulavarty
-- strict thread matches above, loose matches on Subject: below --
2007-03-21 22:45 2.6.21-rc4-mm1 Nicolas Mailhot
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).