Discussion:
2.6.21-rc4-mm1
(too old to reply)
Andrew Morton
2007-03-20 04:56:23 UTC
Permalink
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 ***@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
Michal Piotrowski
2007-03-20 07:54:01 UTC
Permalink
Post by Andrew Morton
Temporarily at
=20
http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
=20
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/493=
4
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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

l *avail_to_resrv_perfctr_nmi_bit+0x2b/0x43
0xc01169fb is in avail_to_resrv_perfctr_nmi_bit (/mnt/md0/devel/linux-m=
m/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_o=
wner)));
128 }


BUG: using smp_processor_id() in preemptible [00000001] code: mount/493=
4
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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
BUG: using smp_processor_id() in preemptible [00000001] code: mount/493=
4
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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
BUG: using smp_processor_id() in preemptible [00000001] code: mount/493=
4
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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
SELinux: initialized (dev oprofilefs, type oprofilefs), uses genfs_cont=
exts

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
[ 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 [opr=
ofile]
{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_interru=
pt+0x29/0x38
softirqs last enabled at (1022784): [<c0128eb4>] __do_softirq+0xe4/0xe=
a
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 vola=
tile unsigned long *addr)
245 {
246 return ((1UL << (nr & 31)) & (addr[nr >> 5])) !=3D 0;
247 }
248
249 static inline int variable_test_bit(int nr, const volatile unsi=
gned 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 vola=
tile unsigned long *addr)
245 {
246 return ((1UL << (nr & 31)) & (addr[nr >> 5])) !=3D 0;
247 }
248
249 static inline int variable_test_bit(int nr, const volatile unsi=
gned 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:2=
71).
266 pending =3D 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 =3D sidtab_search(&sidtab, ssid);
528 if (!scontext) {
529 printk(KERN_ERR "security_compute_av: unrecogn=
ized SID %d\n",
530 ssid);
531 rc =3D -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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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

--=20
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/)
Andy Whitcroft
2007-03-20 09:45:52 UTC
Permalink
Post by Andrew Morton
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.]
Post by Andrew Morton
- 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.
------------[ 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>
------------[ 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>
Andy Whitcroft
2007-03-22 08:41:32 UTC
Permalink
Post by Andy Whitcroft
Post by Andrew Morton
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.]
Post by Andrew Morton
- 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
Andy Whitcroft
2007-03-22 09:48:48 UTC
Permalink
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Andrew Morton
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.]
Post by Andrew Morton
- 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
Con Kolivas
2007-03-22 10:04:06 UTC
Permalink
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Andrew Morton
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.]
Post by Andrew Morton
- 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
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.
sched-rsdl-improvements.patch
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
Andy Whitcroft
2007-03-22 17:07:31 UTC
Permalink
Post by Con Kolivas
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Andrew Morton
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.]
Post by Andrew Morton
- 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
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.
sched-rsdl-improvements.patch
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
Andy Whitcroft
2007-03-22 18:17:31 UTC
Permalink
Post by Andy Whitcroft
Post by Con Kolivas
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Andrew Morton
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.]
Post by Andrew Morton
- 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
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.
sched-rsdl-improvements.patch
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
Con Kolivas
2007-03-22 22:14:24 UTC
Permalink
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Con Kolivas
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Andrew Morton
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.]
Post by Andrew Morton
- 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
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.
sched-rsdl-improvements.patch
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
Con Kolivas
2007-03-23 06:18:20 UTC
Permalink
Post by Andy Whitcroft
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
Andy Whitcroft
2007-03-23 08:45:23 UTC
Permalink
Post by Con Kolivas
Post by Andy Whitcroft
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
Andy Whitcroft
2007-03-23 12:28:28 UTC
Permalink
Post by Andy Whitcroft
Post by Con Kolivas
Post by Andy Whitcroft
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
Fortier,Vincent [Montreal]
2007-03-23 15:53:07 UTC
Permalink
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Con Kolivas
Post by Andy Whitcroft
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.
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Con Kolivas
Post by Andy Whitcroft
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
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Con Kolivas
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
Con Kolivas
2007-03-23 21:45:30 UTC
Permalink
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Con Kolivas
Post by Andy Whitcroft
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
Con Kolivas
2007-03-23 23:26:56 UTC
Permalink
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Andy Whitcroft
Post by Con Kolivas
Post by Andy Whitcroft
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.
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
Stephane Jourdois
2007-03-20 10:52:01 UTC
Permalink
Post by Andrew Morton
=20
Temporarily at
=20
http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
[..]
Post by Andrew Morton
+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):

***@ambre:/usr/src/linux-2.6.21-rc4-mm1 $ rm init/missing_syscalls.=
h=20
***@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
***@ambre:/usr/src/linux-2.6.21-rc4-mm1 $ cat init/.missing_syscall=
s.h.cmd
cmd_init/missing_syscalls.h :=3D sed -n '/^\#define/s/[^_]*__NR_\([^[:s=
pace:]]*\).*/ \#if !defined (__NR_) \&\& !defined (__IGNORE_)
\#warning syscall not implemented
\#endif/p' /usr/src/linux-2.6.21-rc4-mm1/include/asm-i386/unistd.h >in=
it/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

***@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=E9parateur manquant . Arr=EAt.
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=E9phane.

# 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=E9phane (kwisatz) Jourdois <***@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.0000000=
00 +0100
+++ linux-2.6.21-rc4-mm1/init/Makefile 2007-03-20 11:19:02.000000000 +0=
100
@@ -35,10 +35,8 @@
=20
=20
quiet_cmd_missing_syscalls =3D GEN $@
- cmd_missing_syscalls =3D sed -n '/^\#define/s/[^_]*__NR_\([^[:sp=
ace:]]*\).*/\
- \#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 =3D sed -n -f scripts/mkmissing_syscalls_h =
\
+ $(srctree)/include/asm-i386/unistd.h >$@
targets +=3D 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 0=
1: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
+}

--=20
/// Stephane Jourdois /"\ ASCII RIBBON CAMPAIGN \\\
((( Consultant securite \ / AGAINST HTML MAIL )))
\\\ 24 rue Cauchy X ///
\\\ 75015 Paris / \ +33 6 8643 3085 ///
Ben Nizette
2007-03-20 12:55:56 UTC
Permalink
Post by Andrew Morton
Temporarily at
http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
=20
[..]
=20
Post by Andrew Morton
+complain-about-missing-system-calls.patch
+complain-about-missing-system-calls-update.patch
=20
=20
Hi,
=20
I needed the following patch to fix this compile error (which does no=
t
[..]
# (note all three \1 missing, replaced by char '^A', not visible here=
=2E
# note also that my /bin/sh is symlinked to dash (not bash) 0.5.3
[..]=20
Can someone confirm that this is the right way to patch this ?
=20
Can't confirm the correctness but I can confirm that this problem
appears for me using both bash and dash and that the attached patch
allows compile to progress. Cheers :)

--Ben.
=20
Thanks,
- St=E9phane.
Jiri Slaby
2007-03-20 14:31:02 UTC
Permalink
Post by Andrew Morton
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
Andrew Morton
2007-03-20 16:09:44 UTC
Permalink
Post by Jiri Slaby
Post by Andrew Morton
http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
Stopping tasks ...
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.
Pavel Machek
2007-03-20 18:38:21 UTC
Permalink
Hi!
Post by Andrew Morton
Post by Jiri Slaby
Post by Andrew Morton
http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
Stopping tasks ...
swapper
Restarting tasks ... done.
What to test? Enable PM_DEBUG?
Is it repeatable? Freezer normally works better than that.
Post by Andrew Morton
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
Jiri Slaby
2007-03-20 19:40:14 UTC
Permalink
Post by Pavel Machek
Hi!
Post by Andrew Morton
Post by Jiri Slaby
Post by Andrew Morton
http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
Stopping tasks ...
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.
Post by Pavel Machek
Post by Andrew Morton
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
Pavel Machek
2007-03-20 19:56:59 UTC
Permalink
Hi!
Post by Jiri Slaby
Post by Pavel Machek
Post by Andrew Morton
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
Jiri Slaby
2007-03-20 20:13:52 UTC
Permalink
Post by Pavel Machek
Hi!
Post by Jiri Slaby
Post by Pavel Machek
Post by Andrew Morton
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
Pavel Machek
2007-03-20 20:21:41 UTC
Permalink
Hi!
Post by Jiri Slaby
Post by Pavel Machek
Post by Jiri Slaby
Post by Pavel Machek
Post by Andrew Morton
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
Rafael J. Wysocki
2007-03-20 20:58:48 UTC
Permalink
Post by Pavel Machek
Hi!
Post by Jiri Slaby
Post by Pavel Machek
Post by Jiri Slaby
Post by Pavel Machek
Post by Andrew Morton
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
Jiri Slaby
2007-03-20 20:58:42 UTC
Permalink
Post by Rafael J. Wysocki
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
Rafael J. Wysocki
2007-03-20 21:06:37 UTC
Permalink
Post by Jiri Slaby
Post by Rafael J. Wysocki
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
Rafael J. Wysocki
2007-03-21 00:49:32 UTC
Permalink
Post by Rafael J. Wysocki
Post by Jiri Slaby
Post by Rafael J. Wysocki
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
use-task_pgrp-task_session-in-copy_process.patch

Greetings,
Rafael
Eric W. Biederman
2007-03-21 01:23:10 UTC
Permalink
Post by Rafael J. Wysocki
Post by Rafael J. Wysocki
Post by Jiri Slaby
Post by Rafael J. Wysocki
Actually, the problem is 100% reproducible on my system too and I doubt
it's
Post by Rafael J. Wysocki
Post by Jiri Slaby
Post by Rafael J. Wysocki
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
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.
Post by Rafael J. Wysocki
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
s***@us.ibm.com
2007-03-21 02:47:01 UTC
Permalink
Eric W. Biederman [***@xmission.com] wrote:
| "Rafael J. Wysocki" <***@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
Nigel Cunningham
2007-03-21 03:13:54 UTC
Permalink
Hi.
Post by Eric W. Biederman
Post by Rafael J. Wysocki
Post by Rafael J. Wysocki
Post by Jiri Slaby
Post by Rafael J. Wysocki
Actually, the problem is 100% reproducible on my system too and I doubt
it's
Post by Rafael J. Wysocki
Post by Jiri Slaby
Post by Rafael J. Wysocki
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
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.
Post by Rafael J. Wysocki
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
Oleg Nesterov
2007-03-21 14:23:50 UTC
Permalink
Post by Nigel Cunningham
Post by Eric W. Biederman
Post by Rafael J. Wysocki
Bisection shows that the freezing of processes has been broken by one of the
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.
Rafael J. Wysocki
2007-03-21 14:45:16 UTC
Permalink
Post by Oleg Nesterov
Post by Nigel Cunningham
Post by Eric W. Biederman
Post by Rafael J. Wysocki
Bisection shows that the freezing of processes has been broken by one of the
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
Andrew Morton
2007-03-21 16:20:29 UTC
Permalink
Post by Rafael J. Wysocki
Post by Oleg Nesterov
Post by Nigel Cunningham
Post by Eric W. Biederman
Post by Rafael J. Wysocki
Bisection shows that the freezing of processes has been broken by one of the
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.
Oleg Nesterov
2007-03-21 16:55:34 UTC
Permalink
Post by Andrew Morton
Post by Rafael J. Wysocki
Post by Oleg Nesterov
Post by Nigel Cunningham
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.
Andrew Morton
2007-03-21 17:08:24 UTC
Permalink
Post by Oleg Nesterov
Post by Andrew Morton
Post by Rafael J. Wysocki
Post by Oleg Nesterov
Post by Nigel Cunningham
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
Post by Oleg Nesterov
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?
s***@us.ibm.com
2007-03-21 18:07:13 UTC
Permalink
Andrew Morton [***@linux-foundation.org] wrote:
| On Wed, 21 Mar 2007 19:55:34 +0300 Oleg Nesterov <***@tv-sign.ru> wrote:
|
| > On 03/21, Andrew Morton wrote:
| > >
| > > On Wed, 21 Mar 2007 15:45:16 +0100 "Rafael J. Wysocki" <***@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 <***@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 <***@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)++;
Eric W. Biederman
2007-03-21 18:16:22 UTC
Permalink
While we are on the topic. What became of the notion of zeroing the
session and process group values for the init_task?

Eric
s***@us.ibm.com
2007-03-21 18:23:37 UTC
Permalink
Eric W. Biederman [***@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
Oleg Nesterov
2007-03-21 17:15:38 UTC
Permalink
Post by Oleg Nesterov
Post by Andrew Morton
Post by Rafael J. Wysocki
Post by Oleg Nesterov
Post by Nigel Cunningham
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.
Rafael J. Wysocki
2007-03-21 12:08:32 UTC
Permalink
Post by Eric W. Biederman
Post by Rafael J. Wysocki
Post by Rafael J. Wysocki
Post by Jiri Slaby
Post by Rafael J. Wysocki
Actually, the problem is 100% reproducible on my system too and I doubt
it's
Post by Rafael J. Wysocki
Post by Jiri Slaby
Post by Rafael J. Wysocki
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
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.
Post by Eric W. Biederman
Post by Rafael J. Wysocki
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
Rafael J. Wysocki
2007-03-20 20:12:17 UTC
Permalink
Post by Jiri Slaby
Post by Pavel Machek
Hi!
Post by Andrew Morton
Post by Jiri Slaby
Post by Andrew Morton
http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
Stopping tasks ...
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.
Post by Pavel Machek
Post by Andrew Morton
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
J.A. Magallón
2007-03-20 16:36:57 UTC
Permalink
Post by Andrew Morton
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
J.A. Magallón
2007-03-21 00:14:32 UTC
Permalink
Post by J.A. Magallón
=20
Post by Andrew Morton
=20
Temporarily at
=20
http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
=20
Will appear later at
=20
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6=
=2E21-rc4/2.6.21-rc4-mm1/
Post by J.A. Magallón
Post by Andrew Morton
=20
=20
(oops, I forgot LKML)
=20
I have no udev events for my dvd-rw...
=20
werewolf:~# udevmonitor
udevmonitor prints the received event from the kernel [UEVENT]
and the event which udev sends out after rule processing [UDEV]
=20
UEVENT[1174385162.607021] mount /block/sr1 (block)
UDEV [1174385162.610056] mount /block/sr1 (block)
=20
If I insert it in the dvd-rw drive, nothing happens.
=20
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 lik=
e 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
Randy Dunlap
2007-03-20 17:31:51 UTC
Permalink
Post by Andrew Morton
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/
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 ***
Kees Cook
2007-03-20 19:20:16 UTC
Permalink
Post by Randy Dunlap
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 <***@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
Stéphane Jourdois
2007-03-20 20:42:44 UTC
Permalink
Gah! Apologies. This should fix it, but I can't test it since I can=
't=20
=20
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=E9phane.

--=20
/// Stephane Jourdois /"\ ASCII RIBBON CAMPAIGN \\\
((( Consultant securite \ / AGAINST HTML MAIL )))
\\\ 24 rue Cauchy X ///
\\\ 75015 Paris / \ +33 6 8643 3085 ///
Randy Dunlap
2007-03-20 20:50:03 UTC
Permalink
Post by Kees Cook
Post by Randy Dunlap
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
GEN .version
init/.missing_syscalls.h.cmd:2: *** missing separator. Stop.
make: *** [.tmp_vmlinux1] Error 2
Yes, that works_for_me.
Post by Kees Cook
---
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 ***
Andrew Morton
2007-03-21 05:47:14 UTC
Permalink
Post by Kees Cook
I can't
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?
David Woodhouse
2007-03-21 11:25:03 UTC
Permalink
Post by Kees Cook
I can't
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
Sam Ravnborg
2007-03-21 11:59:55 UTC
Permalink
Post by Andrew Morton
Post by Kees Cook
I can't
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
David Woodhouse
2007-03-22 09:17:00 UTC
Permalink
Post by Sam Ravnborg
I will give it a shot tonight.
Thanks. I'll delete the syscalls-2.6.git tree now that you have it.
Post by Sam Ravnborg
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
Sam Ravnborg
2007-03-22 11:41:44 UTC
Permalink
Post by David Woodhouse
Post by Sam Ravnborg
I will give it a shot tonight.
Thanks. I'll delete the syscalls-2.6.git tree now that you have it.
Post by Sam Ravnborg
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
David Woodhouse
2007-03-22 16:25:53 UTC
Permalink
Post by Sam Ravnborg
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
Post by Sam Ravnborg
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
Sam Ravnborg
2007-03-22 16:28:27 UTC
Permalink
Post by David Woodhouse
Post by Sam Ravnborg
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
Post by Sam Ravnborg
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
Sam Ravnborg
2007-03-21 22:19:05 UTC
Permalink
Post by Andrew Morton
Post by Kees Cook
I can't
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
Sam Ravnborg
2007-03-21 22:23:17 UTC
Permalink
From 9ca09c1ca8e5f65ea9f7f0bb3de71cc70a0f6511 Mon Sep 17 00:00:00 2001
From: David Miller <***@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 <***@davemloft.net>
Signed-off-by: Sam Ravnborg <***@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
Sam Ravnborg
2007-03-21 22:22:36 UTC
Permalink
=46rom 5fbf06eb42fdaf81529d2433fe0953297cbc7cc6 Mon Sep 17 00:00:00 200=
1
=46rom: David Woodhouse <***@infradead.org>
Date: Thu, 8 Mar 2007 23:01:13 +0000
Subject: [PATCH] kbuild: complain about missing system calls.
Content-Type: text/plain; charset=3DUTF-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_rang=
e not implemented
init/missing_syscalls.h:947:3: warning: #warning syscall getcpu not imp=
lemented
init/missing_syscalls.h:950:3: warning: #warning syscall epoll_pwait no=
t implemented

Other contributors to this patch are Russell King <rmk+***@arm.linux.o=
rg.uk>
and St=E9phane Jourdois <***@rubis.org>

Signed-off-by: David Woodhouse <***@infradead.org>
Signed-off-by: Sam Ravnborg <***@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.
#
=20
-obj-y :=3D main.o version.o mounts.o
+obj-y :=3D main.o version.o mounts.o missing_=
syscalls.o
ifneq ($(CONFIG_BLK_DEV_INITRD),y)
obj-y +=3D noinitramfs.o
else
@@ -21,6 +21,7 @@ clean-files :=3D ../include/linux/compile.h
# dependencies on generated files need to be listed explicitly
=20
$(obj)/version.o: include/linux/compile.h
+$(obj)/missing_syscalls.o: $(obj)/missing_syscalls.h
=20
# 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 =3D GEN $@
+ cmd_missing_syscalls =3D sed -n -f $(srctree)/scripts/syscallchk=
$< > $@
+
+targets +=3D missing_syscalls.h
+$(obj)/missing_syscalls.h: include/asm-i386/unistd.h \
+ $(srctree)/scripts/syscallchk $(src)/Makefi=
le
+ $(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 k=
ernel */
+#include <linux/compile.h>
+
+/* System calls for 32-bit kernels only */
+#if BITS_PER_LONG =3D=3D 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
+}
--=20
1.4.4.2
Sam Ravnborg
2007-03-21 22:24:00 UTC
Permalink
From 984d35ec37866c9b10c2193fcd1b1b5c6ee4c6cb Mon Sep 17 00:00:00 2001
From: David Woodhouse <***@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 <***@infradead.org>
Signed-off-by: Sam Ravnborg <***@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
Andrew Morton
2007-03-21 23:01:11 UTC
Permalink
On Wed, 21 Mar 2007 23:19:05 +0100
Post by Sam Ravnborg
Post by Andrew Morton
Post by Kees Cook
I can't
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 :(
Sam Ravnborg
2007-03-22 08:54:29 UTC
Permalink
Post by Andrew Morton
On Wed, 21 Mar 2007 23:19:05 +0100
Post by Sam Ravnborg
Post by Andrew Morton
Post by Kees Cook
I can't
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
Randy Dunlap
2007-03-20 18:09:26 UTC
Permalink
Post by Andrew Morton
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 <***@oracle.com>

Avoid multiple/repeated warnings:
include/linux/utrace.h:594: warning: return type defaults to 'int'

Signed-off-by: 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();
}
Roland McGrath
2007-03-21 01:48:41 UTC
Permalink
Post by Randy Dunlap
include/linux/utrace.h:594: warning: return type defaults to 'int'
Oops! Thanks for catching this.


Thanks,
Roland
Adrian Bunk
2007-03-20 20:49:36 UTC
Permalink
Post by Andrew Morton
...
...
+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
Kristen Carlson Accardi
2007-03-21 18:45:31 UTC
Permalink
Fix duplicate names in shpchp and pciehp.

Signed-off-by: Kristen Carlson 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;
J.A. Magallón
2007-03-20 21:04:57 UTC
Permalink
Post by Andrew Morton
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
Stefan Richter
2007-03-20 23:10:42 UTC
Permalink
Post by Andrew Morton
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/
...
Post by Andrew Morton
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/

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Randy Dunlap
2007-03-20 23:49:23 UTC
Permalink
Post by Andrew Morton
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 ***
Randy Dunlap
2007-03-21 01:47:04 UTC
Permalink
Post by Andrew Morton
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 ***
Greg KH
2007-03-21 18:36:08 UTC
Permalink
Post by Randy Dunlap
Post by Andrew Morton
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 ??
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
Andrew Morton
2007-03-21 06:36:43 UTC
Permalink
Post by Andrew Morton
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/
* 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>
* 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
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] Command line: root=/dev/sda2 rootfstype=reiser4 ro i8042.nomux elevator=cfq resume=/dev/sda3 single
[ 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] 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.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.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.536769] Table [DSDT](id 0001) - 650 Objects with 66 Devices 205 Methods 24 Regions
[ 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.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.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.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.057785] (&mm->mmap_sem){----}, at: [<ffffffff80269eda>] do_page_fault+0x35a/0x800
[ 1663.057795]
[ 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.057812]
[ 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.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.058186]
[ 1663.058190] #0: (&data->latch){----}, at: [<ffffffff8036a835>] read_unix_file+0x95/0x450
[ 1663.058196]
[ 1663.058198]
[ 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
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Edward Shishkin
2007-03-21 09:52:31 UTC
Permalink
Post by Andrew Morton
Post by Andrew Morton
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/
* 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
Post by Andrew Morton
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
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Marcel Holtmann
2007-03-21 14:12:50 UTC
Permalink
Hi Andrew,
Post by Andrew Morton
* 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



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Zan Lynx
2007-03-23 19:45:54 UTC
Permalink
Post by Marcel Holtmann
Hi Andrew,
Post by Andrew Morton
* 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 <***@acm.org>
Larry Finger
2007-03-21 16:13:04 UTC
Permalink
Post by Andrew Morton
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/
* 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
Zan Lynx
2007-03-23 19:40:32 UTC
Permalink
Post by Larry Finger
* 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 <***@acm.org>
Larry Finger
2007-03-24 01:49:41 UTC
Permalink
Post by Zan Lynx
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.
Post by Zan Lynx
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

Larry Finger
2007-03-21 18:14:55 UTC
Permalink
Post by Andrew Morton
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/
* 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-fseUSCV1ubazQB+***@public.gmane.org>
Date: Wed Mar 7 23:01:08 2007 +0100

ssb: Don't freeze unregistered devices.

Signed-off-by: Michael Buesch <mb-fseUSCV1ubazQB+***@public.gmane.org>

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
Michael Buesch
2007-03-21 18:34:28 UTC
Permalink
Post by Larry Finger
Post by Andrew Morton
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/
* 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
commit 08531ff130bcc8181d9294a66e25010f48eefb97
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.
John W. Linville
2007-03-21 19:00:03 UTC
Permalink
Post by Michael Buesch
Post by Larry Finger
Post by Andrew Morton
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/
* 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
commit 08531ff130bcc8181d9294a66e25010f48eefb97
Date: Wed Mar 7 23:01:08 2007 +0100
ssb: Don't freeze unregistered devices.
No, that's a different fix for suspend.
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-***@public.gmane.org
John W. Linville
2007-03-21 18:59:00 UTC
Permalink
Post by Larry Finger
Post by Andrew Morton
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/
* 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
FWIW, that patch is in my tree as of yesterday. Presumably it should
be in the next -mm.

John
--
John W. Linville
linville-***@public.gmane.org
Matt Mackall
2007-03-21 20:22:25 UTC
Permalink
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.
Larry Finger
2007-03-21 20:48:31 UTC
Permalink
Post by Matt Mackall
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
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
Larry Finger
2007-03-21 21:03:24 UTC
Permalink
Post by Matt Mackall
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
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
Randy Dunlap
2007-03-21 21:39:31 UTC
Permalink
Post by Larry Finger
Post by Matt Mackall
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
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: [<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: 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 ***
Andrew Morton
2007-03-21 21:45:03 UTC
Permalink
On Wed, 21 Mar 2007 15:22:25 -0500
Post by Matt Mackall
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
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.
Andrew Morton
2007-03-22 07:39:17 UTC
Permalink
Post by Matt Mackall
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
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/
Cornelia Huck
2007-03-22 11:35:08 UTC
Permalink
On Wed, 21 Mar 2007 23:39:17 -0800,
Post by Andrew Morton
Post by Matt Mackall
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
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...
Cornelia Huck
2007-03-22 17:10:19 UTC
Permalink
On Thu, 22 Mar 2007 07:23:06 -0500,
Post by Cornelia Huck
On Wed, 21 Mar 2007 23:39:17 -0800,
Post by Andrew Morton
Post by Matt Mackall
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
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;
}
Larry Finger
2007-03-22 18:55:51 UTC
Permalink
Post by Cornelia Huck
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
Cornelia Huck
2007-03-23 10:10:29 UTC
Permalink
On Thu, 22 Mar 2007 13:55:51 -0500,
Post by Larry Finger
Post by Cornelia Huck
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;
Larry Finger
2007-03-23 15:00:17 UTC
Permalink
Post by Cornelia Huck
On Thu, 22 Mar 2007 13:55:51 -0500,
Post by Larry Finger
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
Larry Finger
2007-03-21 18:49:58 UTC
Permalink
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 (***@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)
Venki Pallipadi
2007-03-21 20:39:58 UTC
Permalink
Post by Larry Finger
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
Andrew Morton
2007-03-21 20:38:15 UTC
Permalink
On Wed, 21 Mar 2007 13:49:58 -0500
Post by Larry Finger
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
==============================================================
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.
=================================================
Thanks. Cc's added..
Venkatesh Pallipadi
2007-03-22 00:33:15 UTC
Permalink
Post by Andrew Morton
On Wed, 21 Mar 2007 13:49:58 -0500
Post by Larry Finger
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
==============================================================
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.
=================================================
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 <***@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)
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Reuben Farrelly
2007-03-21 10:14:46 UTC
Permalink
Post by Andrew Morton
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-***@vger.kernel.org? Maybe I'm the only person to miss them :-)

Reuben
Nicolas Mailhot
2007-03-21 22:45:52 UTC
Permalink
=46irmware loading is broken for all subsystems, not just network

=E2=86=92 http://bugzilla.kernel.org/show_bug.cgi?id=3D8239

--=20
Nicolas Mailhot
J.A. Magallón
2007-03-22 23:27:09 UTC
Permalink
Post by Andrew Morton
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
Andrew Morton
2007-03-23 01:41:40 UTC
Permalink
Please always do reply-to-all.
Post by J.A. Magallón
=20
Post by Andrew Morton
=20
Temporarily at
=20
http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
=20
Will appear later at
=20
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6=
=2E21-rc4/2.6.21-rc4-mm1/
Post by J.A. Magallón
Post by Andrew Morton
=20
=20
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.
Post by J.A. Magallón
Perhaps the problem is in hal/g-v-m or anything else, but I suppose t=
hat
Post by J.A. Magallón
udevmonitor receives events directly from kernel, isn't it ?
Probably related to the not-yet-completely-solved firmware loader failu=
res.

It would be good if someone could do a bisection search on this. I fac=
e a
fun evening hunting down a horrendous ext3 performance regression which=
is
now in mainline.
Continue reading on narkive:
Loading...