2.6.18-rc1-mm1

2.6.18-rc1-mm1

[Andrew Morton]

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/

- We're getting a relatively large number of crash reports coming out of the
  core sysfs/kobject/driver/bus code, and they're all really hard to diagnose.

  I am suspecting that what's happening is that some registration functions
  are failing and the caller is ignoring that failure.  The code proceeds and
  crashes much later, in obscure ways.

  All these functions return error codes, and we're not checking them.  We
  should.  So there's a patch which marks all these things as __must_check,
  which causes around 1,500 new warnings.

  These are all bugs and they all need to be fixed.

  In some cases (eg, sysfs file removal) there's not a lot the caller can do
  apart from warn, so we should probably change those things to return void
  and put a diagnostic message into the callee itself.

  These new warnings can be turned off with CONFIG_ENABLE_MUST_CHECK=n, but
  I'll probably drop that patch.  There's just no excuse for ignoring error
  codes and then blundering on to crash.

- There are some improvements to the swsusp disk IO handling.  You should
  find that the suspend-time writeout and resume-time readin speeds are
  approximately doubled.

- reiser4 doesn't build, due to changes in

	vectorize-aio_read-aio_write-fileop-methods.patch
	remove-readv-writev-methods-and-use-aio_read-aio_write.patch
	streamline-generic_file_-interfaces-and-filemap.patch

- You'll probably see these:

	WARNING: drivers/net/3c59x ids 36 bad size (each on 16)
	WARNING: drivers/net/depca ids 24 bad size (each on 16)
	WARNING: drivers/net/dgrs ids 24 bad size (each on 16)
	WARNING: drivers/net/hp100 ids 84 bad size (each on 16)
	WARNING: drivers/net/ne3210 ids 36 bad size (each on 16)
	WARNING: drivers/net/tulip/de4x5 ids 24 bad size (each on 16)
	WARNING: drivers/scsi/aha1740 ids 60 bad size (each on 16)
	WARNING: drivers/scsi/aic7xxx/aic7xxx ids 84 bad size (each on 16)

  They're triggered by eisa-bus-modalias-attributes-support-1.patch but I
  don't know where the error lies.  But I love the error message!  Would be
  good to see on a tee shirt.

- powerpc (on Mac G5's at least) appears to be dead, probably due to the
  interrupt management changes in 2.6.18-rc1.

- please read the "Boilerplate", below.  Especially the last point.



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 v2.6.16-rc2-mm1

- -mm kernel commit activity can be reviewed by subscribing to the
  mm-commits mailing list.

        echo "subscribe mm-commits" | mail majordomo@vger.kernel.org

- If you hit a bug in -mm and it is not obvious which patch caused it, it is
  most valuable if you can perform a bisection search to identify which patch
  introduced the bug.  Instructions for this process are at

        http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt

  But beware that this process takes some time (around ten rebuilds and
  reboots), so consider reporting the bug first and if we cannot immediately
  identify the faulty patch, then perform the bisection search.

- When reporting bugs, please try to Cc: the relevant maintainer and mailing
  list on any email.




Changes since 2.6.17-mm6:


 origin.patch
 git-acpi.patch
 git-alsa.patch
 git-cifs.patch
 git-cpufreq.patch
 git-geode.patch
 git-gfs2.patch
 git-ia64.patch
 git-ieee1394.patch
 git-infiniband.patch
 git-input.patch
 git-intelfb.patch
 git-jfs.patch
 git-klibc.patch
 git-libata-all.patch
 git-mtd.patch
 git-netdev-all.patch
 git-ocfs2.patch
 git-pcmcia.patch
 git-powerpc.patch
 git-sas.patch
 git-s390.patch
 git-scsi-target.patch
 git-supertrak.patch
 git-watchdog.patch
 git-xfs.patch
 git-cryptodev.patch

 git trees

-time-initialisation-fix.patch
-genirq-ia64-cleanup.patch
-lockdep-special-s390-print_symbol-version.patch
-bcm43xx-netlink-deadlock-fix.patch
-uml-build-fix.patch
-pnpacpi-support-shareable-interrupts.patch
-serial-allow-shared-8250_pnp-interrupts.patch
-zvc-zone_reclaim-leave-1%-of-unmapped-pagecache-pages-for-file-i-o.patch
-binfmt_elf-fix-checks-for-bad-address.patch
-kernel-doc-maintainers.patch
-add-mike-isely-as-pvrusb2-maintainer.patch
-fbdev-add-framebuffer-and-display-update-module-support.patch
-vt-decrement-ref-count-of-the-vt-backend-on-deallocation.patch
-make-more-file_operation-structs-static.patch
-sparc-i8042-build-fix.patch
-sparc-resource-warning-fixes.patch
-lockdep-floppyc-irq-release-fix.patch
-lockdep-console_init-after-local_irq_enable.patch
-lockdep-add-is_module_address.patch
-lockdep-add-print_ip_sym.patch
-lockdep-add-per_cpu_offset.patch
-lockdep-add-disable-enable_irq_lockdep-api.patch
-lockdep-add-local_irq_enable_in_hardirq-api.patch
-lockdep-add-declare_completion_onstack-api.patch
-lockdep-clean-up-rwsems.patch
-lockdep-remove-rwsem_debug-remnants.patch
-lockdep-rename-debug_warn_on.patch
-lockdep-remove-debug_bug_on.patch
-lockdep-remove-mutex-deadlock-checking-code.patch
-lockdep-better-lock-debugging.patch
-lockdep-mutex-section-binutils-workaround.patch
-lockdep-locking-init-debugging-improvement.patch
-lockdep-beautify-x86_64-stacktraces.patch
-lockdep-x86_64-document-stack-frame-internals.patch
-lockdep-i386-remove-multi-entry-backtraces.patch
-lockdep-stacktrace-subsystem-core.patch
-lockdep-s390-config_frame_pointer-support.patch
-lockdep-stacktrace-subsystem-i386-support.patch
-lockdep-stacktrace-subsystem-x86_64-support.patch
-lockdep-stacktrace-subsystem-s390-support.patch
-lockdep-irqtrace-subsystem-core.patch
-lockdep-irqtrace-subsystem-docs.patch
-lockdep-irqtrace-subsystem-i386-support.patch
-lockdep-irqtrace-cleanup-of-include-asm-i386-irqflagsh.patch
-lockdep-irqtrace-subsystem-x86_64-support.patch
-lockdep-irqtrace-cleanup-of-include-asm-x86_64-irqflagsh.patch
-lockdep-irqtrace-subsystem-s390-support.patch
-lockdep-locking-api-self-tests.patch
-lockdep-core.patch
-lockdep-allow-read_lock-recursion-of-same-class.patch
-lockdep-design-docs.patch
-lockdep-procfs.patch
-lockdep-prove-rwsem-locking-correctness.patch
-lockdep-prove-spinlock-rwlock-locking-correctness.patch
-lockdep-prove-mutex-locking-correctness.patch
-lockdep-kconfig.patch
-lockdep-print-all-lock-classes-on-sysrq-d.patch
-lockdep-x86_64-early-init.patch
-lockdep-x86-smp-alternatives-workaround.patch
-lockdep-do-not-recurse-in-printk.patch
-lockdep-fix-rt_hash_lock_sz.patch
-lockdep-s390-turn-validator-off-in-machine-check-handler.patch
-lockdep-enable-on-i386.patch
-lockdep-enable-on-x86_64.patch
-lockdep-enable-on-s390.patch
-lockdep-annotate-direct-io.patch
-lockdep-annotate-serial.patch
-lockdep-annotate-dcache.patch
-lockdep-annotate-i_mutex.patch
-lockdep-annotate-futex.patch
-lockdep-annotate-genirq.patch
-lockdep-annotate-waitqueues.patch
-lockdep-annotate-mm.patch
-lockdep-annotate-serio.patch
-lockdep-annotate-skb_queue_head_init.patch
-lockdep-annotate-timer-base-locks.patch
-lockdep-annotate-scheduler-runqueue-locks.patch
-lockdep-annotate-hrtimer-base-locks.patch
-lockdep-annotate-sock_lock_init.patch
-lockdep-annotate-af_unix-locking.patch
-lockdep-annotate-bh_lock_sock.patch
-lockdep-annotate-ieee1394-skb-queue-head-locking.patch
-lockdep-annotate-mmap_sem.patch
-lockdep-annotate-sunrpc-code.patch
-lockdep-annotate-ntfs-locking-rules.patch
-lockdep-annotate-the-quota-code.patch
-lockdep-annotate-usbfs.patch
-lockdep-annotate-sound-core-seq-seq_portsc.patch
-lockdep-annotate-sound-core-seq-seq_devicec.patch
-lockdep-annotate-8390c-disable_irq.patch
-lockdep-annotate-3c59xc-disable_irq.patch
-lockdep-annotate-enable_in_hardirq.patch
-lockdep-annotate-on-stack-completions.patch
-lockdep-annotate-qeth-driver.patch
-lockdep-annotate-s_lock.patch
-lockdep-annotate-sb-s_umount.patch
-lockdep-annotate-slab-code.patch
-lockdep-annotate-blkdev-nesting.patch
-lockdep-annotate-vlan-net-device-as-being-a-special-class.patch
-lockdep-annotate-on-stack-completions-mmc.patch
-lockdep-annotate-sk_locks.patch
-lockdep-annotate-hostap-netdev-xmit_lock.patch
-forcedeth-typecast-cleanup.patch
-lockdep-annotate-forcedethc-disable_irq.patch
-lockdep-irqtrace-subsystem-move-account_system_vtime-calls-into-kernel-softirqc.patch
-sched-clean-up-fallout-of-recent-changes.patch
-sched-cleanup-remove-task_t-convert-to-struct-task_struct.patch
-sched-cleanup-convert-schedc-internal-typedefs-to-struct.patch
-gfs2-get_sb_dev-fix.patch
-8139cp-printk-fix.patch
-git-e1000.patch
-git-e1000-fixup.patch
-lock-validator-fix-ns83820c-irq-flags-bug.patch
-ni5010-netcard-cleanup.patch
-remove-dead-entry-in-net-wan-kconfig.patch
-ioat-fix-sparse-ulong-warning.patch
-af_unix-datagram-getpeersec-fix.patch
-drivers-dma-iovlockc-make-num_pages_spanned-static.patch
-fix-a-warning-in-ioatdma.patch
-ioat-fix-header-file-kernel-doc.patch
-ioat-fix-kernel-doc-in-source-files.patch
-net-adduse-poison-defines.patch
-atm-adduse-poison-defines.patch
-drivers-scsi-megaraidc-add-a-dummy-mega_create_proc_entry-for-proc_fs=y.patch
-gregkh-usb-usb-serial-dynamic-id.patch
-gregkh-usb-usbip.patch
-gregkh-usb-usb-usbip-build-fix.patch
-gregkh-usb-usb-usbip-more-dead-code-fix.patch
-gregkh-usb-usb-usbip-warning-fixes.patch
-gregkh-usb-airprime_major_update.patch
-fix-sco-on-some-bluetooth-adapters-2.patch
-mm-x86_64-mm-init-rdtscp-warning-fix.patch
-sleazy-fpu-feature-x86_64-support-fix.patch
-x86_64-fix-calgary-copyright-statements-per-ibm-guidelines.patch
-x86_64-add-a-maintainers-entry-for-calgary.patch
-sched-fix-bug-in-__migrate_task.patch
-small-kernel-schedc-cleanup.patch
-enable-oprofile-on-pentium-d.patch
-valid_mmap_phys_addr_range-cleanup.patch
-reiserfsfix-journaling-issue-regarding-fsync.patch
-jmicron-pci-identifiers.patch
-vt-remove-vt-specific-declarations-and-definitions-from.patch
-vt-remove-vt-specific-declarations-and-definitions-from-fix.patch
-tty-remove-include-of-screen_infoh-from-ttyh.patch
-tty-remove-include-of-screen_infoh-from-ttyh-fix.patch
-tty-remove-include-of-screen_infoh-from-ttyh-fix-fix.patch
-md-oops-workaround.patch
-kernel-printkc-export_symbol_unused.patch
-mm-bootmemc-export_unused_symbol.patch
-mm-memoryc-export_unused_symbol.patch
-mm-mmzonec-export_unused_symbol.patch
-fs-read_writec-export_unused_symbol.patch
-kernel-softirqc-export_unused_symbol.patch

 Merged into mainline or a subsystem tree.

+dont-select-config_hotplug.patch
+x86_64-e820c-needs-pgtableh.patch
+acpi-bus-add-missing-newline.patch
+count_vm_events-fix.patch
+sched-fix-bug-in-__migrate_task.patch
+small-kernel-schedc-cleanup.patch
+selinux-decouple-fscontext-context-mount-options.patch
+selinux-add-rootcontext=-option-to-label-root-inode.patch
+reiserfsfix-journaling-issue-regarding-fsync.patch
+nfs-update-documentation-nfsroottxt-to-include-dhcp-syslinux-and-isolinux.patch
+add-computone-intelliport-plus-serial-hotplug-support.patch
+add-specialix-io8-card-support-hotplug-support.patch
+partitions-let-partitions-inherit-policy-from-disk.patch
+fadvise-remove-dead-comments.patch
+minor-cleanup-to-lockdepc.patch
+lockdep-add-more-rwsemh-documentation.patch
+improve-lockdep-debug-output.patch
+lockdep-core-reduce-per-lock-class-cache-size.patch
+lockdep-clean-up-completion-initializer-in-smpbootc.patch
+put-a-comment-at-register_die_notifier-that-the-export-is-used.patch
+rcu-documentation-fix.patch
+vfs-documentation-tweak.patch
+cdrom-fix-bad-cgcbuflen-assignment.patch
+release_firmware-fixes.patch
+updates-credits-file.patch
+hisax-fix-usage-of-__init.patch
+vt-remove-vt-specific-declarations-and-definitions-from.patch
+tty-remove-include-of-screen_infoh-from-ttyh.patch
+md-possible-fix-for-unplug-problem.patch
+md-set-desc_nr-correctly-for-version-1-superblocks.patch
+md-delay-starting-md-threads-until-array-is-completely-setup.patch
+md-fix-resync-speed-calculation-for-restarted-resyncs.patch
+md-fix-a-plug-unplug-race-in-raid5.patch
+md-fix-some-small-races-in-bitmap-plugging-in-raid5.patch
+md-fix-usage-of-wrong-variable-in-raid1.patch
+md-unify-usage-of-symbolic-names-for-perms.patch
+md-require-cap_sys_admin-for-re-configuring-md-devices-via-sysfs.patch
+md-include-sector-number-in-messages-about-corrected-read-errors.patch
+md-oops-workaround.patch
+kernel-printkc-export_symbol_unused.patch
+mm-bootmemc-export_unused_symbol.patch
+mm-memoryc-export_unused_symbol.patch
+mm-mmzonec-export_unused_symbol.patch
+fs-read_writec-export_unused_symbol.patch
+kernel-softirqc-export_unused_symbol.patch
+h8300-remove-duplicate-define.patch
+acpi-fix-fan-thermal-resume.patch
+pi-futex-validate-futex-type-instead-of-oopsing.patch
+zvc-add-__inc_zone_state-for-smp-configuration.patch
+vmstat-export-all_vm_events.patch
+acpi-init-dock-notifier-list.patch
+acpi-fix-boot-with-acpi=off.patch
+adjust-clock-for-lost-ticks.patch

 2.6.18-rc2 queue.

+acpi-do-not-abort-method-execution-if-asked-to-release.patch
+acpi-disable-sbs-by-default.patch
+acpi-initialise-cm_sbs_sem.patch
+acpi-resume-allocation-mode-fix.patch

 ACPI fixes.

+cpufreq-add-__find_governor-helper-and-clean-up-some.patch
+cpufreq-demand-load-governor-modules.patch

 cpufreq updates

+gregkh-driver-device_rename.patch
+gregkh-driver-network-class_device-to-device.patch
+gregkh-driver-class_device_rename-remove.patch

 driver tree updates.

+add-__must_check-to-device-management-code.patch
+add-config_enable_must_check.patch
+v4l-dev2-handle-__must_check.patch

 Add __must_check to lots of driver-layer API functions.

+allow-drm-detection-of-new-via-chipsets.patch

 DRM device support.

+videodev-check-return-values.patch

 Reduce the __must_check warning storm.

+gregkh-i2c-i2c-fix-ignore-module-parameter-handling-in-i2c-core.patch
+gregkh-i2c-i2c-iop3xx-avoid-addressing-self.patch
+gregkh-i2c-scx200_acb-fix-the-state-machine.patch
+gregkh-i2c-scx200_acb-fix-the-block-transactions.patch
+gregkh-i2c-i2c-powermac-fix-master-xfer-return.patch
+gregkh-i2c-i2c-plan-ite-bus-driver-for-removal.patch
+gregkh-i2c-i2c-new-mailing-list.patch
+gregkh-i2c-i2c-algo-error-handling-fix.patch
+gregkh-i2c-i2c-algo-bit-wipe-out-dead-code.patch
+gregkh-i2c-i2c-pca9539-force.patch
+gregkh-i2c-i2c-dev-cleanups.patch
+gregkh-i2c-i2c-dev-convert-array-to-list.patch
+gregkh-i2c-i2c-dev-drop-template-client.patch
+gregkh-i2c-i2c-dev-device.patch

 i2v tree updates.

-ieee1394-sbp2-enable-auto-spin-up-for-maxtor-disks.patch
-ieee1394-fix-calculation-of-csr-expire.patch
-ieee1394-fix-cosmetic-problem-in-speed-probe.patch
-ieee1394-skip-dummy-loop-in-build_speed_map.patch
-ieee1394-replace-__inline__-by-inline.patch
-ieee1394-coding-style-and-comment-fixes-in-midlayer.patch
-ieee1394-update-include-directives-in-midlayer-header.patch
-ieee1394-remove-redundant-code-from-ieee1394_hotplugh.patch
-ieee1394-remove-unused-macros-hpsb_panic-and.patch
-ieee1394-clean-up-declarations-of-hpsb__config_rom.patch
-ieee1394-dv1394-sem2mutex-conversion.patch
-ieee1394-raw1394-remove-redundant-counting-semaphore.patch
-ieee1394-nodemgr-remove-unnecessary-includes.patch
-ieee1394-nodemgr-do-not-spawn-kernel_thread-for-sysfs.patch
-ieee1394-nodemgr-make-module-parameter-ignore_drivers.patch
-ieee1394-nodemgr-switch-to-kthread-api-replace-reset.patch
-ieee1394-nodemgr-convert-nodemgr_serialize-semaphore.patch

 Merged.

+git-ieee1394-fixup.patch

 Fix reject due to git-ieee1394.patch

+git-input-list_for_each_entry-fix.patch

 Fix bug in git-input.patch

+drivers-usb-input-ati_remotec-autorepeat-fix.patch

 USB fix.

-git-hdrinstall2.patch

 Dropped.

+pata-jmicron-add-quirks-to-force-the-device-into-a-sane-mode.patch
+pata-jmicron-configuration.patch
+pata-ata_generic-generic-bios-setup-sff-ata-driver.patch
+pata-jmicron-ide-old-type-driver.patch
+sata-add-pci-id.patch

 PATA updates

-git-netdev-all-fixup.patch

 Unneeded.

+lockdep-fix-atm-ipcommonc-deadlock.patch
+lockdep-annotate-8390c-disable_irq-2.patch

 net fixes.

+8139cp-printk-fix.patch
+82596-section-fixes.patch
+ac3200-section-fixes.patch
+cops-section-fix.patch
+cs89x0-section-fix.patch
+at1700-section-fix.patch
+e2100-section-fix.patch
+eepro-section-fix.patch
+eexpress-section-fix.patch
+es3210-section-fix.patch
+eth16i-section-fix.patch
+smsc-ircc2-fix-section-reference-mismatches.patch
+lance-section-fix.patch
+lne390-section-fix.patch
+ni52-section-fix.patch
+ibmtr-section-fix.patch
+smctr-section-fix.patch
+wd-section-fix.patch
+ni65-section-fix.patch
+seeq8005-section-fix.patch
+winbond-840-section-fix.patch
+fealnx-section-fix.patch
+sundance-section-fix.patch

 Fix various __init section bloopers.  These were done quickly and need a
 second round.

+drivers-net-e1000-possible-cleanups.patch
+e1000_7033_dump_ring.patch
+forcedeth-deferral-fixup.patch
+forcedeth-watermark-fixup.patch
+freescale-qe-ucc-gigabit-ethernet-driver.patch

 Net driver updates.

+via-ircc-fix-memory-leak.patch
+lockdep-fix-sk_dst_check-deadlock.patch
+netlink-improve-string-attribute-validation.patch

 Net things.

+fs-nfs-make-code-static.patch

 NFS cleanup

+pcmcia-update-alloc_io_space-for-conflict-checking-for-multifunction-pc-card-for-linux-kernel-26154.patch

 PCMCIA update

+git-powerpc-briq_panel-Kconfig-fix.patch
+powermac-combined-fixes-for-backlight-code.patch

 powerpc fixes.

-gregkh-pci-msi-merge-existing-msi-disabling-quirks.patch
-gregkh-pci-msi-rename-pci_cap_id_ht_irqconf-into-pci_cap_id_ht.patch
-gregkh-pci-msi-blacklist-pci-e-chipsets-depending-on-hypertransport-msi-capabality.patch
-gregkh-pci-msi-factorize-common-msi-detection-code-from-pci_enable_msi-and-msix.patch
-gregkh-pci-msi-stop-inheriting-bus-flags-and-check-root-chipset-bus-flags-instead.patch
-gregkh-pci-msi-drop-pci_msi_quirk.patch
 gregkh-pci-resources-insert-identical-resources-above-existing-resources.patch
+gregkh-pci-msi-01-merge_msi_disabling_quirks.patch
+gregkh-pci-msi-02-factorize_pci_msi_supported.patch
+gregkh-pci-msi-03-use_root_chipset_dev_no_msi_instead_of_pci_bus_flags.patch
+gregkh-pci-msi-04-rename_pci_cap_id_ht_irqconf.patch
+gregkh-pci-msi-05-check_hypertransport_msi_capabilities.patch
+gregkh-pci-msi-06-drop_pci_msi_quirk.patch
+gregkh-pci-msi-07-drop_pci_bus_flags.patch
-revert-gregkh-pci-msi-drop-pci_msi_quirk.patch
-revert-gregkh-pci-msi-stop-inheriting-bus-flags-and-check-root-chipset-bus-flags-instead.patch
-revert-gregkh-pci-msi-factorize-common-msi-detection-code-from-pci_enable_msi-and-msix.patch
-revert-gregkh-pci-msi-blacklist-pci-e-chipsets-depending-on-hypertransport-msi-capabality.patch
-revert-gregkh-pci-msi-rename-pci_cap_id_ht_irqconf-into-pci_cap_id_ht.patch
-revert-gregkh-pci-msi-merge-existing-msi-disabling-quirks.patch

 New set of PCI MSI patches.

-git-scsi-misc-fixup.patch

 Unneeded.

+pci-initialize-struct-pci_dev-error_state.patch
+pcie-check-and-return-bus_register-errors.patch
+pcie-cleanup-on-probe-error.patch

 PCI later updates.

+make-drivers-scsi-aic7xxx-aic79xx_coreahd_set_tags-static.patch
+NCR_D700-section-fix.patch
+megaraid-fix-warnings-when-config_proc_fs=n.patch

 SCSI updates

+areca-raid-linux-scsi-driver-update7.patch
+areca-raid-linux-scsi-driver-update7-fix.patch

 Update drivers-scsi-arcmsr-cleanups.patch

+sparc64-of_device_register-error-checking-fix.patch

 Add missing error check.

+gregkh-usb-usb-remove-devfs-information-from-kconfig.patch
+gregkh-usb-usb-ipw.c-driver-fix.patch
+gregkh-usb-usb-add-support-for-wisegroup.-ltd-smartjoy-dual-plus-adapter.patch
+gregkh-usb-usbfs-private-mutex-for-open-release-and-remove.patch
+gregkh-usb-usbfs-detect-device-unregistration.patch
+gregkh-usb-usb-skeleton-don-t-submit-urbs-after-disconnection.patch

 USB tree udpates (part thereof - I dropped ten-odd patches due to oopsing)

+rtl8150_disconnect-needs-tasklet_kill.patch
+usb-storage-wait-for-urb-to-complete.patch

 USB fixes.

+x86_64-mm-tif-restore-sigmask.patch
+x86_64-mm-add-ppoll-pselect.patch
+x86_64-mm-bring-x86-64-ia32-emul-in-sync-with-i386-on-read_implies_exec-enabling.patch
+x86_64-mm-getcpu-vsyscall.patch
+x86_64-mm-tif-flags-for-debug-regs-and-io-bitmap-in-ctxsw.patch
+x86_64-mm-add-a-maintainers-entry-for-calgary.patch
+x86_64-mm-fix-calgary-copyright-statements-per-ibm-guidelines.patch
+x86_64-mm-fix-acpi-defaults.patch
+x86_64-mm-oprofile-p4-model.patch

 x86_64 updates

 Folded into sleazy-fpu-feature-x86_64-support.patch

+x86_64-wire-up-oops_enter-oops_exit.patch

 Implement pause_on_oops on x86_64.

+xfs-move-xfs_ioc_getversion-to-main-multiplexer.patch

 XFS cleanup

+mmap-zero-length-hugetlb-file-with-prot_none-to-protect-a.patch

 hugetlb fixlet.

+convert-i386-numa-kva-space-to-bootmem.patch
+convert-i386-numa-kva-space-to-bootmem-tidy.patch
+bootmem-remove-useless-__init-in-header-file.patch
+bootmem-mark-link_bootmem-as-part-of-the-__init-section.patch
+bootmem-remove-useless-parentheses-in-bootmem-header.patch
+bootmem-limit-to-80-columns-width.patch
+bootmem-remove-useless-headers-inclusions.patch
+bootmem-use-pfn-page-conversion-macros.patch
+bootmem-miscellaneous-coding-style-fixes.patch
+reduce-max_nr_zones-remove-two-strange-uses-of-max_nr_zones.patch
+reduce-max_nr_zones-fix-max_nr_zones-array-initializations.patch
+reduce-max_nr_zones-make-display-of-highmem-counters-conditional-on-config_highmem.patch
+reduce-max_nr_zones-make-display-of-highmem-counters-conditional-on-config_highmem-tidy.patch
+reduce-max_nr_zones-move-highmem-counters-into-highmemc-h.patch
+reduce-max_nr_zones-page-allocator-zone_highmem-cleanup.patch
+reduce-max_nr_zones-use-enum-to-define-zones-reformat-and-comment.patch
+reduce-max_nr_zones-use-enum-to-define-zones-reformat-and-comment-cleanup.patch
+reduce-max_nr_zones-make-zone_dma32-optional.patch
+reduce-max_nr_zones-make-zone_highmem-optional.patch
+reduce-max_nr_zones-remove-display-of-counters-for-unconfigured-zones.patch
+reduce-max_nr_zones-remove-display-of-counters-for-unconfigured-zones-s390-fix.patch
+reduce-max_nr_zones-fix-i386-srat-check-for-max_nr_zones.patch

 Memory management updates.

+tiacx-build-fix.patch

 Fix acx1xx-wireless-driver.patch

+binfmt_elf-consistently-use-loff_t.patch

 binfmt_elf fixlet.

+fdpic-fix-fdpic-compile-errors-2.patch
+frv-fix-frv-arch-compile-errors.patch
+nommu-fix-execution-off-of-ramfs-with-mmap.patch
+fdpic-adjust-the-elf-fdpic-driver-to-conform-more-to-the-codingstyle.patch
+fdpic-define-seek_-constants-in-the-linux-kernel-headers.patch
+fdpic-move-roundup-into-linux-kernelh.patch
+fdpic-move-roundup-into-linux-kernelh-fix.patch
+fdpic-add-coredump-capability-for-the-elf-fdpic-binfmt.patch
+frv-introduce-asm-offsets-for-frv-arch.patch

 FRV/nommu updates

+i386-early-fault-handler.patch
+i386-require-acpi-for-numa-with-generic-architecture.patch
+add-seccomp_disable_tsc-config-option.patch
+i386-defconfig-set-config_pm_std_partition=.patch
+get_cmos_time-locking-fix.patch

 x86 updates

+swsusp-do-not-use-memcpy-for-snapshotting-memory.patch
+swsusp-warning-fix.patch
+fix-panic-when-swsusp-signature-cant-be-read.patch
+swsusp-write-timer.patch
+swsusp-write-speedup.patch
+swsusp-read-timer.patch
+swsusp-read-speedup.patch
+swsusp-read-speedup-fix.patch
+swsusp-read-speedup-cleanup.patch
+swsusp-read-speedup-cleanup-2.patch

 swsusp updates

+cris-switch-to-iminor-imajor.patch
+pcf8563-remove-mod_inc_use_count-mod_dec_use_count.patch

 cris fixlets.

+uml-clean-up-address-space-limits-code.patch
+uml-timer-initialization-cleanup.patch
+uml-timer-initialization-cleanup-fix.patch
+uml-remove-some-useless-exports.patch
+uml-fix-static-binary-segfault.patch
+uml-remove-useless-declaration.patch
+uml-signal-initialization-cleanup.patch
+uml-timer-handler-tidying.patch
+uml-ifdef-a-mode-specific-function.patch
+uml-mark-forward_interrupts-as-being-mode-specific.patch
+uml-remove-spinlock-wrapper-functions.patch
+uml-remove-os_isatty.patch
+uml-fix-exitcall-ordering-bug.patch
+uml-make-some-symbols-static.patch
+uml-remove-syscall-debugging.patch
+uml-move-_kernc-files.patch
+uml-move-_kernc-files-fix.patch
+uml-formatting-fixes.patch
+uml-add-some-eintr-protection.patch
+uml-remove-unused-variable.patch
+uml-make-mconsole-version-requests-happen-in-a-process.patch

 UML updates

+drivers-edac-make-code-static.patch

 EDAC cleanup

+inode-diet-eliminate-i_blksize-and-use-a-per-superblock-default-fix.patch

 Fix inode-diet-eliminate-i_blksize-and-use-a-per-superblock-default.patch

-inode-diet-fix-size-of-i_blkbits-i_version-and-i_dnotify_mask.patch

 Dropped.

+x86-microcode-add-sysfs-and-hotplug-support-fix-fix.patch

 Fix x86-microcode-add-sysfs-and-hotplug-support.patch some more.

+consistently-use-max_errno-in-__syscall_return.patch
+consistently-use-max_errno-in-__syscall_return-fix.patch
+sanitize-3c589_cs.patch
+eisa-bus-modalias-attributes-support-1.patch
+add-address_space_operationsbatch_write.patch
+add-address_space_operationsbatch_write-tidy.patch
+null-terminate-over-long-proc-kallsyms-symbols.patch
+fix-weird-logic-in-alloc_fdtable.patch
+alloc_fdtable-cleanup.patch
+uninline-init_waitqueue_head.patch
+aoe-cleanup-i_rdev-usage.patch
+remove-leftover-ext3-acl-declarations.patch
+reiserfs-warn-about-the-useless-nolargeio-option.patch
+pata-pata_qdi-fix-return-code.patch
+pata-ide-jmicron-finish-writing.patch
+pata-jmicron-it-works-better-if-you-get-the-file-name-right.patch
+pata-jmicron-further-clean-up.patch
+pata-ata_jmicro-fix-an-escapee.patch
+pata-jmicron-jmicron-multifunction-setup.patch
+pata-jmicron-missed-one.patch
+pata-libata-enable-per-device-speed-setting.patch
+remove-kernel-kthreadckthread_stop_sem.patch
+include-__param-section-in-read-only-data-range.patch
+remove-open_max-check-from-poll-syscall.patch
+# led-class-support-for-soekris-net48xx.patch needs SOB
+led-class-support-for-soekris-net48xx.patch
+led-class-support-for-soekris-net48xx-fix.patch
+pc8736x_gpio-fix-re-modprobe-errors.patch
+pc8736x_gpio-fix-re-modprobe-errors-undo-region-reservation.patch
+pc8736x_gpio-fix-re-modprobe-errors-fix-finish-cdev-init.patch
+pc8736x_gpio-fix-re-modprobe-errors-fix-finish-cdev-init-tidy.patch
+snsc-switch-from-force_sig-to-kill_proc.patch
+disallow-modular-binfmt_elf32.patch
+remove-the-tasklist_lock-export.patch

 Misc updates.

+revert-pcmcia-make-ide_cs-work-with-the-memory-space-of-cf-cards-if-io-space-is-not-available.patch

 Revert possibly-broken IDE-CS patch.

+vectorize-aio_read-aio_write-fileop-methods.patch
+remove-readv-writev-methods-and-use-aio_read-aio_write.patch
+streamline-generic_file_-interfaces-and-filemap.patch

 Fiddle around with core pagecache APIs, break reiser4.

+per-task-delay-accounting-taskstats-interface-control-exit-data-through-cpumasks.patch
+per-task-delay-accounting-taskstats-interface-control-exit-data-through-cpumasks-fix.patch

 Improve scalability of the task accounting infrastructure in -mm.

+isdn-cleanup-i_rdev-udage.patch

 ISDN cleanup

+knfsd-nfsd4-add-per-operation-server-stats.patch

 knfsd update

+reduce-max_nr_zones-swap_prefetch-remove-incorrect-use-of-zone_highmem.patch

 Update swap prefetch for other patches in -mm.

+ecryptfs-partial-signed-integer-to-size_t-conversion-updated-ii.patch

 Update ecryptfs.

+streamline-generic_file_-interfaces-and-filemap-ecryptfs.patch

 Fix ecryptfs for the pagecache fiiddling.

-drivers-ide-legacy-ide-csc-make-2-functions-static.patch

 IDE cleanup

+move-ide-to-unmaintained-drop-reference-to-old-git-tree.patch

 Seems we don't have an IDE maintainer.

+cirrus-logic-framebuffer-i2c-support.patch
+cirrus-logic-framebuffer-i2c-support-fix.patch

 fbdev updates (these need work)

+statistics-infrastructure-update-9.patch

 Update statistics-infrastructure.patch

+statistics-replace-inode-ugeneric_ip-with-i_private.patch

 Fix it for the inode-diet patches.

-srcu-rcu-variant-permitting-read-side-blocking.patch
-srcu-2-rcu-variant-permitting-read-side-blocking.patch
-srcu-add-srcu-operations-to-rcutorture.patch
-srcu-2-add-srcu-operations-to-rcutorture.patch
+srcu-3-rcu-variant-permitting-read-side-blocking.patch
+srcu-3-rcu-variant-permitting-read-side-blocking-fix.patch
+srcu-3-add-srcu-operations-to-rcutorture.patch

 Updated srcu patchset.

+the-scheduled-removal-of-some-oss-drivers-fix.patch

 Fix the-scheduled-removal-of-some-oss-drivers.patch

+serial-core-adds-atomic-context-debug-code.patch

 Little debugging aid.




All 807 patches:

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

Re: 2.6.18-rc1-mm1

[Michal Piotrowski]

Hi,

Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> 
[snip]
> - When reporting bugs, please try to Cc: the relevant maintainer and mailing
>   list on any email.

make headers_install gives the following error

  INSTALL include/linux/wavefront.h
sed: can't read /usr/src/linux-mm/include/linux/wavefront.h: No such file or directory
make[3]: *** [wavefront.h] Error 2
make[2]: *** [linux] Error 2
make[1]: *** [headers_install] Error 2
make: *** [headers_install] Error 2

We don't use this file anymore.


Regards,
Michal

--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)

Signed-off-by: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>

diff -uprN -X linux-mm/Documentation/dontdiff linux-mm-clean/include/linux/Kbuild linux-mm/include/linux/Kbuild
--- linux-mm-clean/include/linux/Kbuild	2006-07-09 12:07:15.000000000 +0200
+++ linux-mm/include/linux/Kbuild	2006-07-09 12:04:46.000000000 +0200
@@ -28,7 +28,7 @@ header-y += affs_fs.h affs_hardblocks.h
 	sockios.h som.h sound.h stddef.h synclink.h telephony.h		\
 	termios.h ticable.h times.h tiocl.h tipc.h toshiba.h		\
 	ultrasound.h un.h utime.h utsname.h video_decoder.h		\
-	video_encoder.h videotext.h vt.h wavefront.h wireless.h xattr.h	\
+	video_encoder.h videotext.h vt.h wireless.h xattr.h	\
 	x25.h zorro_ids.h

 unifdef-y += acct.h adb.h adfs_fs.h agpgart.h apm_bios.h atalk.h	\

Re: 2.6.18-rc1-mm1

[Fabio Comolli]

This was not present in 2.6.17-mm5:

=======================================================
[ INFO: possible circular locking dependency detected ]
-------------------------------------------------------
cpuspeed/1520 is trying to acquire lock:
 (&policy->lock){--..}, at: [<c02c130f>] mutex_lock+0x21/0x24

but task is already holding lock:
 (cpucontrol){--..}, at: [<c02c130f>] mutex_lock+0x21/0x24

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (cpucontrol){--..}:
       [<c0135b93>] lock_acquire+0x60/0x80
       [<c02c11aa>] __mutex_lock_slowpath+0xb0/0x1f4
       [<c02c130f>] mutex_lock+0x21/0x24
       [<c0138af1>] __lock_cpu_hotplug+0x36/0x56
       [<c0138b2a>] lock_cpu_hotplug+0xa/0xc
       [<c0268315>] __cpufreq_driver_target+0x15/0x6d
       [<c02691c0>] cpufreq_governor_userspace+0x199/0x1cc
       [<c0267d61>] __cpufreq_governor+0x57/0xd8
       [<c0267f85>] __cpufreq_set_policy+0x1a3/0x1bc
       [<c0267fcb>] cpufreq_set_policy+0x2d/0x6f
       [<c02689f8>] cpufreq_add_dev+0x31a/0x496
       [<c0229463>] sysdev_driver_register+0x5d/0xa0
       [<c0267c5a>] cpufreq_register_driver+0x9e/0x14e
       [<f909009b>] 0xf909009b
       [<c013bb34>] sys_init_module+0x162c/0x17bd
       [<c0102d55>] sysenter_past_esp+0x56/0x8d

-> #1 (userspace_mutex){--..}:
       [<c0135b93>] lock_acquire+0x60/0x80
       [<c02c11aa>] __mutex_lock_slowpath+0xb0/0x1f4
       [<c02c130f>] mutex_lock+0x21/0x24
       [<c026907a>] cpufreq_governor_userspace+0x53/0x1cc
       [<c0267d61>] __cpufreq_governor+0x57/0xd8
       [<c0267f30>] __cpufreq_set_policy+0x14e/0x1bc
       [<c0267fcb>] cpufreq_set_policy+0x2d/0x6f
       [<c02689f8>] cpufreq_add_dev+0x31a/0x496
       [<c0229463>] sysdev_driver_register+0x5d/0xa0
       [<c0267c5a>] cpufreq_register_driver+0x9e/0x14e
       [<f909009b>] 0xf909009b
       [<c013bb34>] sys_init_module+0x162c/0x17bd
       [<c0102d55>] sysenter_past_esp+0x56/0x8d

-> #0 (&policy->lock){--..}:
       [<c0135b93>] lock_acquire+0x60/0x80
       [<c02c11aa>] __mutex_lock_slowpath+0xb0/0x1f4
       [<c02c130f>] mutex_lock+0x21/0x24
       [<c0268159>] store_scaling_governor+0x14c/0x1a3
       [<c026774e>] store+0x37/0x48
       [<c018e72c>] sysfs_write_file+0xab/0xd1
       [<c016053a>] vfs_write+0x86/0xea
       [<c0160ac8>] sys_write+0x3b/0x60
       [<c0102d55>] sysenter_past_esp+0x56/0x8d

other info that might help us debug this:

1 lock held by cpuspeed/1520:
 #0:  (cpucontrol){--..}, at: [<c02c130f>] mutex_lock+0x21/0x24

stack backtrace:
 [<c0103dbb>] show_trace+0xd/0x10
 [<c01043af>] dump_stack+0x19/0x1b
 [<c0134f00>] print_circular_bug_tail+0x59/0x64
 [<c0135736>] __lock_acquire+0x82b/0x9b6
 [<c0135b93>] lock_acquire+0x60/0x80
 [<c02c11aa>] __mutex_lock_slowpath+0xb0/0x1f4
 [<c02c130f>] mutex_lock+0x21/0x24
 [<c0268159>] store_scaling_governor+0x14c/0x1a3
 [<c026774e>] store+0x37/0x48
 [<c018e72c>] sysfs_write_file+0xab/0xd1
 [<c016053a>] vfs_write+0x86/0xea
 [<c0160ac8>] sys_write+0x3b/0x60
 [<c0102d55>] sysenter_past_esp+0x56/0x8d




On 7/9/06, Andrew Morton <akpm@osdl.org> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
>
> - We're getting a relatively large number of crash reports coming out of the
>   core sysfs/kobject/driver/bus code, and they're all really hard to diagnose.
>
>   I am suspecting that what's happening is that some registration functions
>   are failing and the caller is ignoring that failure.  The code proceeds and
>   crashes much later, in obscure ways.
>
>   All these functions return error codes, and we're not checking them.  We
>   should.  So there's a patch which marks all these things as __must_check,
>   which causes around 1,500 new warnings.
>
>   These are all bugs and they all need to be fixed.
>
>   In some cases (eg, sysfs file removal) there's not a lot the caller can do
>   apart from warn, so we should probably change those things to return void
>   and put a diagnostic message into the callee itself.
>
>   These new warnings can be turned off with CONFIG_ENABLE_MUST_CHECK=n, but
>   I'll probably drop that patch.  There's just no excuse for ignoring error
>   codes and then blundering on to crash.
>
> - There are some improvements to the swsusp disk IO handling.  You should
>   find that the suspend-time writeout and resume-time readin speeds are
>   approximately doubled.
>
> - reiser4 doesn't build, due to changes in
>
>         vectorize-aio_read-aio_write-fileop-methods.patch
>         remove-readv-writev-methods-and-use-aio_read-aio_write.patch
>         streamline-generic_file_-interfaces-and-filemap.patch
>
> - You'll probably see these:
>
>         WARNING: drivers/net/3c59x ids 36 bad size (each on 16)
>         WARNING: drivers/net/depca ids 24 bad size (each on 16)
>         WARNING: drivers/net/dgrs ids 24 bad size (each on 16)
>         WARNING: drivers/net/hp100 ids 84 bad size (each on 16)
>         WARNING: drivers/net/ne3210 ids 36 bad size (each on 16)
>         WARNING: drivers/net/tulip/de4x5 ids 24 bad size (each on 16)
>         WARNING: drivers/scsi/aha1740 ids 60 bad size (each on 16)
>         WARNING: drivers/scsi/aic7xxx/aic7xxx ids 84 bad size (each on 16)
>
>   They're triggered by eisa-bus-modalias-attributes-support-1.patch but I
>   don't know where the error lies.  But I love the error message!  Would be
>   good to see on a tee shirt.
>
> - powerpc (on Mac G5's at least) appears to be dead, probably due to the
>   interrupt management changes in 2.6.18-rc1.
>
> - please read the "Boilerplate", below.  Especially the last point.
>
>
>
> 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 v2.6.16-rc2-mm1
>
> - -mm kernel commit activity can be reviewed by subscribing to the
>   mm-commits mailing list.
>
>         echo "subscribe mm-commits" | mail majordomo@vger.kernel.org
>
> - If you hit a bug in -mm and it is not obvious which patch caused it, it is
>   most valuable if you can perform a bisection search to identify which patch
>   introduced the bug.  Instructions for this process are at
>
>         http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt
>
>   But beware that this process takes some time (around ten rebuilds and
>   reboots), so consider reporting the bug first and if we cannot immediately
>   identify the faulty patch, then perform the bisection search.
>
> - When reporting bugs, please try to Cc: the relevant maintainer and mailing
>   list on any email.
>
>
>
>
> Changes since 2.6.17-mm6:
>
>
>  origin.patch
>  git-acpi.patch
>  git-alsa.patch
>  git-cifs.patch
>  git-cpufreq.patch
>  git-geode.patch
>  git-gfs2.patch
>  git-ia64.patch
>  git-ieee1394.patch
>  git-infiniband.patch
>  git-input.patch
>  git-intelfb.patch
>  git-jfs.patch
>  git-klibc.patch
>  git-libata-all.patch
>  git-mtd.patch
>  git-netdev-all.patch
>  git-ocfs2.patch
>  git-pcmcia.patch
>  git-powerpc.patch
>  git-sas.patch
>  git-s390.patch
>  git-scsi-target.patch
>  git-supertrak.patch
>  git-watchdog.patch
>  git-xfs.patch
>  git-cryptodev.patch
>
>  git trees
>
> -time-initialisation-fix.patch
> -genirq-ia64-cleanup.patch
> -lockdep-special-s390-print_symbol-version.patch
> -bcm43xx-netlink-deadlock-fix.patch
> -uml-build-fix.patch
> -pnpacpi-support-shareable-interrupts.patch
> -serial-allow-shared-8250_pnp-interrupts.patch
> -zvc-zone_reclaim-leave-1%-of-unmapped-pagecache-pages-for-file-i-o.patch
> -binfmt_elf-fix-checks-for-bad-address.patch
> -kernel-doc-maintainers.patch
> -add-mike-isely-as-pvrusb2-maintainer.patch
> -fbdev-add-framebuffer-and-display-update-module-support.patch
> -vt-decrement-ref-count-of-the-vt-backend-on-deallocation.patch
> -make-more-file_operation-structs-static.patch
> -sparc-i8042-build-fix.patch
> -sparc-resource-warning-fixes.patch
> -lockdep-floppyc-irq-release-fix.patch
> -lockdep-console_init-after-local_irq_enable.patch
> -lockdep-add-is_module_address.patch
> -lockdep-add-print_ip_sym.patch
> -lockdep-add-per_cpu_offset.patch
> -lockdep-add-disable-enable_irq_lockdep-api.patch
> -lockdep-add-local_irq_enable_in_hardirq-api.patch
> -lockdep-add-declare_completion_onstack-api.patch
> -lockdep-clean-up-rwsems.patch
> -lockdep-remove-rwsem_debug-remnants.patch
> -lockdep-rename-debug_warn_on.patch
> -lockdep-remove-debug_bug_on.patch
> -lockdep-remove-mutex-deadlock-checking-code.patch
> -lockdep-better-lock-debugging.patch
> -lockdep-mutex-section-binutils-workaround.patch
> -lockdep-locking-init-debugging-improvement.patch
> -lockdep-beautify-x86_64-stacktraces.patch
> -lockdep-x86_64-document-stack-frame-internals.patch
> -lockdep-i386-remove-multi-entry-backtraces.patch
> -lockdep-stacktrace-subsystem-core.patch
> -lockdep-s390-config_frame_pointer-support.patch
> -lockdep-stacktrace-subsystem-i386-support.patch
> -lockdep-stacktrace-subsystem-x86_64-support.patch
> -lockdep-stacktrace-subsystem-s390-support.patch
> -lockdep-irqtrace-subsystem-core.patch
> -lockdep-irqtrace-subsystem-docs.patch
> -lockdep-irqtrace-subsystem-i386-support.patch
> -lockdep-irqtrace-cleanup-of-include-asm-i386-irqflagsh.patch
> -lockdep-irqtrace-subsystem-x86_64-support.patch
> -lockdep-irqtrace-cleanup-of-include-asm-x86_64-irqflagsh.patch
> -lockdep-irqtrace-subsystem-s390-support.patch
> -lockdep-locking-api-self-tests.patch
> -lockdep-core.patch
> -lockdep-allow-read_lock-recursion-of-same-class.patch
> -lockdep-design-docs.patch
> -lockdep-procfs.patch
> -lockdep-prove-rwsem-locking-correctness.patch
> -lockdep-prove-spinlock-rwlock-locking-correctness.patch
> -lockdep-prove-mutex-locking-correctness.patch
> -lockdep-kconfig.patch
> -lockdep-print-all-lock-classes-on-sysrq-d.patch
> -lockdep-x86_64-early-init.patch
> -lockdep-x86-smp-alternatives-workaround.patch
> -lockdep-do-not-recurse-in-printk.patch
> -lockdep-fix-rt_hash_lock_sz.patch
> -lockdep-s390-turn-validator-off-in-machine-check-handler.patch
> -lockdep-enable-on-i386.patch
> -lockdep-enable-on-x86_64.patch
> -lockdep-enable-on-s390.patch
> -lockdep-annotate-direct-io.patch
> -lockdep-annotate-serial.patch
> -lockdep-annotate-dcache.patch
> -lockdep-annotate-i_mutex.patch
> -lockdep-annotate-futex.patch
> -lockdep-annotate-genirq.patch
> -lockdep-annotate-waitqueues.patch
> -lockdep-annotate-mm.patch
> -lockdep-annotate-serio.patch
> -lockdep-annotate-skb_queue_head_init.patch
> -lockdep-annotate-timer-base-locks.patch
> -lockdep-annotate-scheduler-runqueue-locks.patch
> -lockdep-annotate-hrtimer-base-locks.patch
> -lockdep-annotate-sock_lock_init.patch
> -lockdep-annotate-af_unix-locking.patch
> -lockdep-annotate-bh_lock_sock.patch
> -lockdep-annotate-ieee1394-skb-queue-head-locking.patch
> -lockdep-annotate-mmap_sem.patch
> -lockdep-annotate-sunrpc-code.patch
> -lockdep-annotate-ntfs-locking-rules.patch
> -lockdep-annotate-the-quota-code.patch
> -lockdep-annotate-usbfs.patch
> -lockdep-annotate-sound-core-seq-seq_portsc.patch
> -lockdep-annotate-sound-core-seq-seq_devicec.patch
> -lockdep-annotate-8390c-disable_irq.patch
> -lockdep-annotate-3c59xc-disable_irq.patch
> -lockdep-annotate-enable_in_hardirq.patch
> -lockdep-annotate-on-stack-completions.patch
> -lockdep-annotate-qeth-driver.patch
> -lockdep-annotate-s_lock.patch
> -lockdep-annotate-sb-s_umount.patch
> -lockdep-annotate-slab-code.patch
> -lockdep-annotate-blkdev-nesting.patch
> -lockdep-annotate-vlan-net-device-as-being-a-special-class.patch
> -lockdep-annotate-on-stack-completions-mmc.patch
> -lockdep-annotate-sk_locks.patch
> -lockdep-annotate-hostap-netdev-xmit_lock.patch
> -forcedeth-typecast-cleanup.patch
> -lockdep-annotate-forcedethc-disable_irq.patch
> -lockdep-irqtrace-subsystem-move-account_system_vtime-calls-into-kernel-softirqc.patch
> -sched-clean-up-fallout-of-recent-changes.patch
> -sched-cleanup-remove-task_t-convert-to-struct-task_struct.patch
> -sched-cleanup-convert-schedc-internal-typedefs-to-struct.patch
> -gfs2-get_sb_dev-fix.patch
> -8139cp-printk-fix.patch
> -git-e1000.patch
> -git-e1000-fixup.patch
> -lock-validator-fix-ns83820c-irq-flags-bug.patch
> -ni5010-netcard-cleanup.patch
> -remove-dead-entry-in-net-wan-kconfig.patch
> -ioat-fix-sparse-ulong-warning.patch
> -af_unix-datagram-getpeersec-fix.patch
> -drivers-dma-iovlockc-make-num_pages_spanned-static.patch
> -fix-a-warning-in-ioatdma.patch
> -ioat-fix-header-file-kernel-doc.patch
> -ioat-fix-kernel-doc-in-source-files.patch
> -net-adduse-poison-defines.patch
> -atm-adduse-poison-defines.patch
> -drivers-scsi-megaraidc-add-a-dummy-mega_create_proc_entry-for-proc_fs=y.patch
> -gregkh-usb-usb-serial-dynamic-id.patch
> -gregkh-usb-usbip.patch
> -gregkh-usb-usb-usbip-build-fix.patch
> -gregkh-usb-usb-usbip-more-dead-code-fix.patch
> -gregkh-usb-usb-usbip-warning-fixes.patch
> -gregkh-usb-airprime_major_update.patch
> -fix-sco-on-some-bluetooth-adapters-2.patch
> -mm-x86_64-mm-init-rdtscp-warning-fix.patch
> -sleazy-fpu-feature-x86_64-support-fix.patch
> -x86_64-fix-calgary-copyright-statements-per-ibm-guidelines.patch
> -x86_64-add-a-maintainers-entry-for-calgary.patch
> -sched-fix-bug-in-__migrate_task.patch
> -small-kernel-schedc-cleanup.patch
> -enable-oprofile-on-pentium-d.patch
> -valid_mmap_phys_addr_range-cleanup.patch
> -reiserfsfix-journaling-issue-regarding-fsync.patch
> -jmicron-pci-identifiers.patch
> -vt-remove-vt-specific-declarations-and-definitions-from.patch
> -vt-remove-vt-specific-declarations-and-definitions-from-fix.patch
> -tty-remove-include-of-screen_infoh-from-ttyh.patch
> -tty-remove-include-of-screen_infoh-from-ttyh-fix.patch
> -tty-remove-include-of-screen_infoh-from-ttyh-fix-fix.patch
> -md-oops-workaround.patch
> -kernel-printkc-export_symbol_unused.patch
> -mm-bootmemc-export_unused_symbol.patch
> -mm-memoryc-export_unused_symbol.patch
> -mm-mmzonec-export_unused_symbol.patch
> -fs-read_writec-export_unused_symbol.patch
> -kernel-softirqc-export_unused_symbol.patch
>
>  Merged into mainline or a subsystem tree.
>
> +dont-select-config_hotplug.patch
> +x86_64-e820c-needs-pgtableh.patch
> +acpi-bus-add-missing-newline.patch
> +count_vm_events-fix.patch
> +sched-fix-bug-in-__migrate_task.patch
> +small-kernel-schedc-cleanup.patch
> +selinux-decouple-fscontext-context-mount-options.patch
> +selinux-add-rootcontext=-option-to-label-root-inode.patch
> +reiserfsfix-journaling-issue-regarding-fsync.patch
> +nfs-update-documentation-nfsroottxt-to-include-dhcp-syslinux-and-isolinux.patch
> +add-computone-intelliport-plus-serial-hotplug-support.patch
> +add-specialix-io8-card-support-hotplug-support.patch
> +partitions-let-partitions-inherit-policy-from-disk.patch
> +fadvise-remove-dead-comments.patch
> +minor-cleanup-to-lockdepc.patch
> +lockdep-add-more-rwsemh-documentation.patch
> +improve-lockdep-debug-output.patch
> +lockdep-core-reduce-per-lock-class-cache-size.patch
> +lockdep-clean-up-completion-initializer-in-smpbootc.patch
> +put-a-comment-at-register_die_notifier-that-the-export-is-used.patch
> +rcu-documentation-fix.patch
> +vfs-documentation-tweak.patch
> +cdrom-fix-bad-cgcbuflen-assignment.patch
> +release_firmware-fixes.patch
> +updates-credits-file.patch
> +hisax-fix-usage-of-__init.patch
> +vt-remove-vt-specific-declarations-and-definitions-from.patch
> +tty-remove-include-of-screen_infoh-from-ttyh.patch
> +md-possible-fix-for-unplug-problem.patch
> +md-set-desc_nr-correctly-for-version-1-superblocks.patch
> +md-delay-starting-md-threads-until-array-is-completely-setup.patch
> +md-fix-resync-speed-calculation-for-restarted-resyncs.patch
> +md-fix-a-plug-unplug-race-in-raid5.patch
> +md-fix-some-small-races-in-bitmap-plugging-in-raid5.patch
> +md-fix-usage-of-wrong-variable-in-raid1.patch
> +md-unify-usage-of-symbolic-names-for-perms.patch
> +md-require-cap_sys_admin-for-re-configuring-md-devices-via-sysfs.patch
> +md-include-sector-number-in-messages-about-corrected-read-errors.patch
> +md-oops-workaround.patch
> +kernel-printkc-export_symbol_unused.patch
> +mm-bootmemc-export_unused_symbol.patch
> +mm-memoryc-export_unused_symbol.patch
> +mm-mmzonec-export_unused_symbol.patch
> +fs-read_writec-export_unused_symbol.patch
> +kernel-softirqc-export_unused_symbol.patch
> +h8300-remove-duplicate-define.patch
> +acpi-fix-fan-thermal-resume.patch
> +pi-futex-validate-futex-type-instead-of-oopsing.patch
> +zvc-add-__inc_zone_state-for-smp-configuration.patch
> +vmstat-export-all_vm_events.patch
> +acpi-init-dock-notifier-list.patch
> +acpi-fix-boot-with-acpi=off.patch
> +adjust-clock-for-lost-ticks.patch
>
>  2.6.18-rc2 queue.
>
> +acpi-do-not-abort-method-execution-if-asked-to-release.patch
> +acpi-disable-sbs-by-default.patch
> +acpi-initialise-cm_sbs_sem.patch
> +acpi-resume-allocation-mode-fix.patch
>
>  ACPI fixes.
>
> +cpufreq-add-__find_governor-helper-and-clean-up-some.patch
> +cpufreq-demand-load-governor-modules.patch
>
>  cpufreq updates
>
> +gregkh-driver-device_rename.patch
> +gregkh-driver-network-class_device-to-device.patch
> +gregkh-driver-class_device_rename-remove.patch
>
>  driver tree updates.
>
> +add-__must_check-to-device-management-code.patch
> +add-config_enable_must_check.patch
> +v4l-dev2-handle-__must_check.patch
>
>  Add __must_check to lots of driver-layer API functions.
>
> +allow-drm-detection-of-new-via-chipsets.patch
>
>  DRM device support.
>
> +videodev-check-return-values.patch
>
>  Reduce the __must_check warning storm.
>
> +gregkh-i2c-i2c-fix-ignore-module-parameter-handling-in-i2c-core.patch
> +gregkh-i2c-i2c-iop3xx-avoid-addressing-self.patch
> +gregkh-i2c-scx200_acb-fix-the-state-machine.patch
> +gregkh-i2c-scx200_acb-fix-the-block-transactions.patch
> +gregkh-i2c-i2c-powermac-fix-master-xfer-return.patch
> +gregkh-i2c-i2c-plan-ite-bus-driver-for-removal.patch
> +gregkh-i2c-i2c-new-mailing-list.patch
> +gregkh-i2c-i2c-algo-error-handling-fix.patch
> +gregkh-i2c-i2c-algo-bit-wipe-out-dead-code.patch
> +gregkh-i2c-i2c-pca9539-force.patch
> +gregkh-i2c-i2c-dev-cleanups.patch
> +gregkh-i2c-i2c-dev-convert-array-to-list.patch
> +gregkh-i2c-i2c-dev-drop-template-client.patch
> +gregkh-i2c-i2c-dev-device.patch
>
>  i2v tree updates.
>
> -ieee1394-sbp2-enable-auto-spin-up-for-maxtor-disks.patch
> -ieee1394-fix-calculation-of-csr-expire.patch
> -ieee1394-fix-cosmetic-problem-in-speed-probe.patch
> -ieee1394-skip-dummy-loop-in-build_speed_map.patch
> -ieee1394-replace-__inline__-by-inline.patch
> -ieee1394-coding-style-and-comment-fixes-in-midlayer.patch
> -ieee1394-update-include-directives-in-midlayer-header.patch
> -ieee1394-remove-redundant-code-from-ieee1394_hotplugh.patch
> -ieee1394-remove-unused-macros-hpsb_panic-and.patch
> -ieee1394-clean-up-declarations-of-hpsb__config_rom.patch
> -ieee1394-dv1394-sem2mutex-conversion.patch
> -ieee1394-raw1394-remove-redundant-counting-semaphore.patch
> -ieee1394-nodemgr-remove-unnecessary-includes.patch
> -ieee1394-nodemgr-do-not-spawn-kernel_thread-for-sysfs.patch
> -ieee1394-nodemgr-make-module-parameter-ignore_drivers.patch
> -ieee1394-nodemgr-switch-to-kthread-api-replace-reset.patch
> -ieee1394-nodemgr-convert-nodemgr_serialize-semaphore.patch
>
>  Merged.
>
> +git-ieee1394-fixup.patch
>
>  Fix reject due to git-ieee1394.patch
>
> +git-input-list_for_each_entry-fix.patch
>
>  Fix bug in git-input.patch
>
> +drivers-usb-input-ati_remotec-autorepeat-fix.patch
>
>  USB fix.
>
> -git-hdrinstall2.patch
>
>  Dropped.
>
> +pata-jmicron-add-quirks-to-force-the-device-into-a-sane-mode.patch
> +pata-jmicron-configuration.patch
> +pata-ata_generic-generic-bios-setup-sff-ata-driver.patch
> +pata-jmicron-ide-old-type-driver.patch
> +sata-add-pci-id.patch
>
>  PATA updates
>
> -git-netdev-all-fixup.patch
>
>  Unneeded.
>
> +lockdep-fix-atm-ipcommonc-deadlock.patch
> +lockdep-annotate-8390c-disable_irq-2.patch
>
>  net fixes.
>
> +8139cp-printk-fix.patch
> +82596-section-fixes.patch
> +ac3200-section-fixes.patch
> +cops-section-fix.patch
> +cs89x0-section-fix.patch
> +at1700-section-fix.patch
> +e2100-section-fix.patch
> +eepro-section-fix.patch
> +eexpress-section-fix.patch
> +es3210-section-fix.patch
> +eth16i-section-fix.patch
> +smsc-ircc2-fix-section-reference-mismatches.patch
> +lance-section-fix.patch
> +lne390-section-fix.patch
> +ni52-section-fix.patch
> +ibmtr-section-fix.patch
> +smctr-section-fix.patch
> +wd-section-fix.patch
> +ni65-section-fix.patch
> +seeq8005-section-fix.patch
> +winbond-840-section-fix.patch
> +fealnx-section-fix.patch
> +sundance-section-fix.patch
>
>  Fix various __init section bloopers.  These were done quickly and need a
>  second round.
>
> +drivers-net-e1000-possible-cleanups.patch
> +e1000_7033_dump_ring.patch
> +forcedeth-deferral-fixup.patch
> +forcedeth-watermark-fixup.patch
> +freescale-qe-ucc-gigabit-ethernet-driver.patch
>
>  Net driver updates.
>
> +via-ircc-fix-memory-leak.patch
> +lockdep-fix-sk_dst_check-deadlock.patch
> +netlink-improve-string-attribute-validation.patch
>
>  Net things.
>
> +fs-nfs-make-code-static.patch
>
>  NFS cleanup
>
> +pcmcia-update-alloc_io_space-for-conflict-checking-for-multifunction-pc-card-for-linux-kernel-26154.patch
>
>  PCMCIA update
>
> +git-powerpc-briq_panel-Kconfig-fix.patch
> +powermac-combined-fixes-for-backlight-code.patch
>
>  powerpc fixes.
>
> -gregkh-pci-msi-merge-existing-msi-disabling-quirks.patch
> -gregkh-pci-msi-rename-pci_cap_id_ht_irqconf-into-pci_cap_id_ht.patch
> -gregkh-pci-msi-blacklist-pci-e-chipsets-depending-on-hypertransport-msi-capabality.patch
> -gregkh-pci-msi-factorize-common-msi-detection-code-from-pci_enable_msi-and-msix.patch
> -gregkh-pci-msi-stop-inheriting-bus-flags-and-check-root-chipset-bus-flags-instead.patch
> -gregkh-pci-msi-drop-pci_msi_quirk.patch
>  gregkh-pci-resources-insert-identical-resources-above-existing-resources.patch
> +gregkh-pci-msi-01-merge_msi_disabling_quirks.patch
> +gregkh-pci-msi-02-factorize_pci_msi_supported.patch
> +gregkh-pci-msi-03-use_root_chipset_dev_no_msi_instead_of_pci_bus_flags.patch
> +gregkh-pci-msi-04-rename_pci_cap_id_ht_irqconf.patch
> +gregkh-pci-msi-05-check_hypertransport_msi_capabilities.patch
> +gregkh-pci-msi-06-drop_pci_msi_quirk.patch
> +gregkh-pci-msi-07-drop_pci_bus_flags.patch
> -revert-gregkh-pci-msi-drop-pci_msi_quirk.patch
> -revert-gregkh-pci-msi-stop-inheriting-bus-flags-and-check-root-chipset-bus-flags-instead.patch
> -revert-gregkh-pci-msi-factorize-common-msi-detection-code-from-pci_enable_msi-and-msix.patch
> -revert-gregkh-pci-msi-blacklist-pci-e-chipsets-depending-on-hypertransport-msi-capabality.patch
> -revert-gregkh-pci-msi-rename-pci_cap_id_ht_irqconf-into-pci_cap_id_ht.patch
> -revert-gregkh-pci-msi-merge-existing-msi-disabling-quirks.patch
>
>  New set of PCI MSI patches.
>
> -git-scsi-misc-fixup.patch
>
>  Unneeded.
>
> +pci-initialize-struct-pci_dev-error_state.patch
> +pcie-check-and-return-bus_register-errors.patch
> +pcie-cleanup-on-probe-error.patch
>
>  PCI later updates.
>
> +make-drivers-scsi-aic7xxx-aic79xx_coreahd_set_tags-static.patch
> +NCR_D700-section-fix.patch
> +megaraid-fix-warnings-when-config_proc_fs=n.patch
>
>  SCSI updates
>
> +areca-raid-linux-scsi-driver-update7.patch
> +areca-raid-linux-scsi-driver-update7-fix.patch
>
>  Update drivers-scsi-arcmsr-cleanups.patch
>
> +sparc64-of_device_register-error-checking-fix.patch
>
>  Add missing error check.
>
> +gregkh-usb-usb-remove-devfs-information-from-kconfig.patch
> +gregkh-usb-usb-ipw.c-driver-fix.patch
> +gregkh-usb-usb-add-support-for-wisegroup.-ltd-smartjoy-dual-plus-adapter.patch
> +gregkh-usb-usbfs-private-mutex-for-open-release-and-remove.patch
> +gregkh-usb-usbfs-detect-device-unregistration.patch
> +gregkh-usb-usb-skeleton-don-t-submit-urbs-after-disconnection.patch
>
>  USB tree udpates (part thereof - I dropped ten-odd patches due to oopsing)
>
> +rtl8150_disconnect-needs-tasklet_kill.patch
> +usb-storage-wait-for-urb-to-complete.patch
>
>  USB fixes.
>
> +x86_64-mm-tif-restore-sigmask.patch
> +x86_64-mm-add-ppoll-pselect.patch
> +x86_64-mm-bring-x86-64-ia32-emul-in-sync-with-i386-on-read_implies_exec-enabling.patch
> +x86_64-mm-getcpu-vsyscall.patch
> +x86_64-mm-tif-flags-for-debug-regs-and-io-bitmap-in-ctxsw.patch
> +x86_64-mm-add-a-maintainers-entry-for-calgary.patch
> +x86_64-mm-fix-calgary-copyright-statements-per-ibm-guidelines.patch
> +x86_64-mm-fix-acpi-defaults.patch
> +x86_64-mm-oprofile-p4-model.patch
>
>  x86_64 updates
>
>  Folded into sleazy-fpu-feature-x86_64-support.patch
>
> +x86_64-wire-up-oops_enter-oops_exit.patch
>
>  Implement pause_on_oops on x86_64.
>
> +xfs-move-xfs_ioc_getversion-to-main-multiplexer.patch
>
>  XFS cleanup
>
> +mmap-zero-length-hugetlb-file-with-prot_none-to-protect-a.patch
>
>  hugetlb fixlet.
>
> +convert-i386-numa-kva-space-to-bootmem.patch
> +convert-i386-numa-kva-space-to-bootmem-tidy.patch
> +bootmem-remove-useless-__init-in-header-file.patch
> +bootmem-mark-link_bootmem-as-part-of-the-__init-section.patch
> +bootmem-remove-useless-parentheses-in-bootmem-header.patch
> +bootmem-limit-to-80-columns-width.patch
> +bootmem-remove-useless-headers-inclusions.patch
> +bootmem-use-pfn-page-conversion-macros.patch
> +bootmem-miscellaneous-coding-style-fixes.patch
> +reduce-max_nr_zones-remove-two-strange-uses-of-max_nr_zones.patch
> +reduce-max_nr_zones-fix-max_nr_zones-array-initializations.patch
> +reduce-max_nr_zones-make-display-of-highmem-counters-conditional-on-config_highmem.patch
> +reduce-max_nr_zones-make-display-of-highmem-counters-conditional-on-config_highmem-tidy.patch
> +reduce-max_nr_zones-move-highmem-counters-into-highmemc-h.patch
> +reduce-max_nr_zones-page-allocator-zone_highmem-cleanup.patch
> +reduce-max_nr_zones-use-enum-to-define-zones-reformat-and-comment.patch
> +reduce-max_nr_zones-use-enum-to-define-zones-reformat-and-comment-cleanup.patch
> +reduce-max_nr_zones-make-zone_dma32-optional.patch
> +reduce-max_nr_zones-make-zone_highmem-optional.patch
> +reduce-max_nr_zones-remove-display-of-counters-for-unconfigured-zones.patch
> +reduce-max_nr_zones-remove-display-of-counters-for-unconfigured-zones-s390-fix.patch
> +reduce-max_nr_zones-fix-i386-srat-check-for-max_nr_zones.patch
>
>  Memory management updates.
>
> +tiacx-build-fix.patch
>
>  Fix acx1xx-wireless-driver.patch
>
> +binfmt_elf-consistently-use-loff_t.patch
>
>  binfmt_elf fixlet.
>
> +fdpic-fix-fdpic-compile-errors-2.patch
> +frv-fix-frv-arch-compile-errors.patch
> +nommu-fix-execution-off-of-ramfs-with-mmap.patch
> +fdpic-adjust-the-elf-fdpic-driver-to-conform-more-to-the-codingstyle.patch
> +fdpic-define-seek_-constants-in-the-linux-kernel-headers.patch
> +fdpic-move-roundup-into-linux-kernelh.patch
> +fdpic-move-roundup-into-linux-kernelh-fix.patch
> +fdpic-add-coredump-capability-for-the-elf-fdpic-binfmt.patch
> +frv-introduce-asm-offsets-for-frv-arch.patch
>
>  FRV/nommu updates
>
> +i386-early-fault-handler.patch
> +i386-require-acpi-for-numa-with-generic-architecture.patch
> +add-seccomp_disable_tsc-config-option.patch
> +i386-defconfig-set-config_pm_std_partition=.patch
> +get_cmos_time-locking-fix.patch
>
>  x86 updates
>
> +swsusp-do-not-use-memcpy-for-snapshotting-memory.patch
> +swsusp-warning-fix.patch
> +fix-panic-when-swsusp-signature-cant-be-read.patch
> +swsusp-write-timer.patch
> +swsusp-write-speedup.patch
> +swsusp-read-timer.patch
> +swsusp-read-speedup.patch
> +swsusp-read-speedup-fix.patch
> +swsusp-read-speedup-cleanup.patch
> +swsusp-read-speedup-cleanup-2.patch
>
>  swsusp updates
>
> +cris-switch-to-iminor-imajor.patch
> +pcf8563-remove-mod_inc_use_count-mod_dec_use_count.patch
>
>  cris fixlets.
>
> +uml-clean-up-address-space-limits-code.patch
> +uml-timer-initialization-cleanup.patch
> +uml-timer-initialization-cleanup-fix.patch
> +uml-remove-some-useless-exports.patch
> +uml-fix-static-binary-segfault.patch
> +uml-remove-useless-declaration.patch
> +uml-signal-initialization-cleanup.patch
> +uml-timer-handler-tidying.patch
> +uml-ifdef-a-mode-specific-function.patch
> +uml-mark-forward_interrupts-as-being-mode-specific.patch
> +uml-remove-spinlock-wrapper-functions.patch
> +uml-remove-os_isatty.patch
> +uml-fix-exitcall-ordering-bug.patch
> +uml-make-some-symbols-static.patch
> +uml-remove-syscall-debugging.patch
> +uml-move-_kernc-files.patch
> +uml-move-_kernc-files-fix.patch
> +uml-formatting-fixes.patch
> +uml-add-some-eintr-protection.patch
> +uml-remove-unused-variable.patch
> +uml-make-mconsole-version-requests-happen-in-a-process.patch
>
>  UML updates
>
> +drivers-edac-make-code-static.patch
>
>  EDAC cleanup
>
> +inode-diet-eliminate-i_blksize-and-use-a-per-superblock-default-fix.patch
>
>  Fix inode-diet-eliminate-i_blksize-and-use-a-per-superblock-default.patch
>
> -inode-diet-fix-size-of-i_blkbits-i_version-and-i_dnotify_mask.patch
>
>  Dropped.
>
> +x86-microcode-add-sysfs-and-hotplug-support-fix-fix.patch
>
>  Fix x86-microcode-add-sysfs-and-hotplug-support.patch some more.
>
> +consistently-use-max_errno-in-__syscall_return.patch
> +consistently-use-max_errno-in-__syscall_return-fix.patch
> +sanitize-3c589_cs.patch
> +eisa-bus-modalias-attributes-support-1.patch
> +add-address_space_operationsbatch_write.patch
> +add-address_space_operationsbatch_write-tidy.patch
> +null-terminate-over-long-proc-kallsyms-symbols.patch
> +fix-weird-logic-in-alloc_fdtable.patch
> +alloc_fdtable-cleanup.patch
> +uninline-init_waitqueue_head.patch
> +aoe-cleanup-i_rdev-usage.patch
> +remove-leftover-ext3-acl-declarations.patch
> +reiserfs-warn-about-the-useless-nolargeio-option.patch
> +pata-pata_qdi-fix-return-code.patch
> +pata-ide-jmicron-finish-writing.patch
> +pata-jmicron-it-works-better-if-you-get-the-file-name-right.patch
> +pata-jmicron-further-clean-up.patch
> +pata-ata_jmicro-fix-an-escapee.patch
> +pata-jmicron-jmicron-multifunction-setup.patch
> +pata-jmicron-missed-one.patch
> +pata-libata-enable-per-device-speed-setting.patch
> +remove-kernel-kthreadckthread_stop_sem.patch
> +include-__param-section-in-read-only-data-range.patch
> +remove-open_max-check-from-poll-syscall.patch
> +# led-class-support-for-soekris-net48xx.patch needs SOB
> +led-class-support-for-soekris-net48xx.patch
> +led-class-support-for-soekris-net48xx-fix.patch
> +pc8736x_gpio-fix-re-modprobe-errors.patch
> +pc8736x_gpio-fix-re-modprobe-errors-undo-region-reservation.patch
> +pc8736x_gpio-fix-re-modprobe-errors-fix-finish-cdev-init.patch
> +pc8736x_gpio-fix-re-modprobe-errors-fix-finish-cdev-init-tidy.patch
> +snsc-switch-from-force_sig-to-kill_proc.patch
> +disallow-modular-binfmt_elf32.patch
> +remove-the-tasklist_lock-export.patch
>
>  Misc updates.
>
> +revert-pcmcia-make-ide_cs-work-with-the-memory-space-of-cf-cards-if-io-space-is-not-available.patch
>
>  Revert possibly-broken IDE-CS patch.
>
> +vectorize-aio_read-aio_write-fileop-methods.patch
> +remove-readv-writev-methods-and-use-aio_read-aio_write.patch
> +streamline-generic_file_-interfaces-and-filemap.patch
>
>  Fiddle around with core pagecache APIs, break reiser4.
>
> +per-task-delay-accounting-taskstats-interface-control-exit-data-through-cpumasks.patch
> +per-task-delay-accounting-taskstats-interface-control-exit-data-through-cpumasks-fix.patch
>
>  Improve scalability of the task accounting infrastructure in -mm.
>
> +isdn-cleanup-i_rdev-udage.patch
>
>  ISDN cleanup
>
> +knfsd-nfsd4-add-per-operation-server-stats.patch
>
>  knfsd update
>
> +reduce-max_nr_zones-swap_prefetch-remove-incorrect-use-of-zone_highmem.patch
>
>  Update swap prefetch for other patches in -mm.
>
> +ecryptfs-partial-signed-integer-to-size_t-conversion-updated-ii.patch
>
>  Update ecryptfs.
>
> +streamline-generic_file_-interfaces-and-filemap-ecryptfs.patch
>
>  Fix ecryptfs for the pagecache fiiddling.
>
> -drivers-ide-legacy-ide-csc-make-2-functions-static.patch
>
>  IDE cleanup
>
> +move-ide-to-unmaintained-drop-reference-to-old-git-tree.patch
>
>  Seems we don't have an IDE maintainer.
>
> +cirrus-logic-framebuffer-i2c-support.patch
> +cirrus-logic-framebuffer-i2c-support-fix.patch
>
>  fbdev updates (these need work)
>
> +statistics-infrastructure-update-9.patch
>
>  Update statistics-infrastructure.patch
>
> +statistics-replace-inode-ugeneric_ip-with-i_private.patch
>
>  Fix it for the inode-diet patches.
>
> -srcu-rcu-variant-permitting-read-side-blocking.patch
> -srcu-2-rcu-variant-permitting-read-side-blocking.patch
> -srcu-add-srcu-operations-to-rcutorture.patch
> -srcu-2-add-srcu-operations-to-rcutorture.patch
> +srcu-3-rcu-variant-permitting-read-side-blocking.patch
> +srcu-3-rcu-variant-permitting-read-side-blocking-fix.patch
> +srcu-3-add-srcu-operations-to-rcutorture.patch
>
>  Updated srcu patchset.
>
> +the-scheduled-removal-of-some-oss-drivers-fix.patch
>
>  Fix the-scheduled-removal-of-some-oss-drivers.patch
>
> +serial-core-adds-atomic-context-debug-code.patch
>
>  Little debugging aid.
>
>
>
>
> All 807 patches:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/patch-list
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Re: 2.6.18-rc1-mm1

[Michal Piotrowski]

Hi,

On 09/07/06, Andrew Morton <akpm@osdl.org> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
>

This looks like a problem with cpufreq.

=======================================================
[ INFO: possible circular locking dependency detected ]
-------------------------------------------------------
cpuspeed/1426 is trying to acquire lock:
 (&inode->i_data.tree_lock){.+..}, at: [<c0151dc7>] find_get_page+0x12/0x70

but task is already holding lock:
 (&mm->mmap_sem){----}, at: [<c0116cab>] do_page_fault+0x10d/0x4ea

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (cpucontrol){--..}:
       [<c0139a55>] lock_acquire+0x71/0x91
       [<c02ee288>] __mutex_lock_slowpath+0xd2/0x2f5
       [<c02ee4c7>] mutex_lock+0x1c/0x1f
       [<c013dd3b>] __lock_cpu_hotplug+0x34/0x4c
       [<c013dd6c>] lock_cpu_hotplug+0xa/0xc
       [<c029b587>] __cpufreq_driver_target+0x15/0x50
       [<c029c3ca>] cpufreq_governor_performance+0x1a/0x20
       [<c029a89b>] __cpufreq_governor+0x95/0x18c
       [<c029aa72>] __cpufreq_set_policy+0xe0/0x118
       [<c029af49>] cpufreq_set_policy+0x2d/0x6f
       [<c029bc45>] cpufreq_add_dev+0x3ee/0x4f3
       [<c024dccb>] sysdev_driver_register+0x5e/0x9e
       [<c029be70>] cpufreq_register_driver+0x80/0xf4
       [<fdba202a>] 0xfdba202a
       [<c0140f22>] sys_init_module+0xa6/0x21d
       [<c0103179>] sysenter_past_esp+0x56/0x8d

-> #0 (&inode->i_data.tree_lock){.+..}:
       [<c0139a55>] lock_acquire+0x71/0x91
       [<c02ee288>] __mutex_lock_slowpath+0xd2/0x2f5
       [<c02ee4c7>] mutex_lock+0x1c/0x1f
       [<c029b7f2>] store_scaling_governor+0x14a/0x1a2
       [<c029b223>] store+0x37/0x48
       [<c01a9f4b>] sysfs_write_file+0xa6/0xcc
       [<c0172dab>] vfs_write+0xc9/0x172
       [<c017341d>] sys_write+0x3b/0x71
       [<c0103179>] sysenter_past_esp+0x56/0x8d

other info that might help us debug this:

1 lock held by cpuspeed/1426:
 #0:  (cpucontrol){--..}, at: [<c02ee4c7>] mutex_lock+0x1c/0x1f

stack backtrace:
 [<c01041f0>] show_trace_log_lvl+0x54/0x101
 [<c0104827>] show_trace+0xd/0x10
 [<c0104949>] dump_stack+0x19/0x1b
 [<c0138b99>] print_circular_bug_tail+0x59/0x64
 [<c013950a>] __lock_acquire+0x966/0xb39
 [<c0139a55>] lock_acquire+0x71/0x91
 [<c02ee288>] __mutex_lock_slowpath+0xd2/0x2f5
 [<c02ee4c7>] mutex_lock+0x1c/0x1f
 [<c029b7f2>] store_scaling_governor+0x14a/0x1a2
 [<c029b223>] store+0x37/0x48
 [<c01a9f4b>] sysfs_write_file+0xa6/0xcc
 [<c0172dab>] vfs_write+0xc9/0x172
 [<c017341d>] sys_write+0x3b/0x71
 [<c0103179>] sysenter_past_esp+0x56/0x8d

Here is a dmesg log
http://www.stardust.webpages.pl/files/mm/2.6.18-rc1-mm1/mm-dmesg

Here is a config file
http://www.stardust.webpages.pl/files/mm/2.6.18-rc1-mm1/mm-config

Regards,
Michal

-- 
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)

Re: 2.6.18-rc1-mm1

[Michal Piotrowski]

Sorry, I forgot CC.

On 09/07/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> Hi,
>
> On 09/07/06, Andrew Morton <akpm@osdl.org> wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> >
>
> This looks like a problem with cpufreq.
>
> =======================================================
> [ INFO: possible circular locking dependency detected ]
> -------------------------------------------------------
> cpuspeed/1426 is trying to acquire lock:
>  (&inode->i_data.tree_lock){.+..}, at: [<c0151dc7>] find_get_page+0x12/0x70
>
> but task is already holding lock:
>  (&mm->mmap_sem){----}, at: [<c0116cab>] do_page_fault+0x10d/0x4ea
>
> which lock already depends on the new lock.
>
>
> the existing dependency chain (in reverse order) is:
>
> -> #1 (cpucontrol){--..}:
>        [<c0139a55>] lock_acquire+0x71/0x91
>        [<c02ee288>] __mutex_lock_slowpath+0xd2/0x2f5
>        [<c02ee4c7>] mutex_lock+0x1c/0x1f
>        [<c013dd3b>] __lock_cpu_hotplug+0x34/0x4c
>        [<c013dd6c>] lock_cpu_hotplug+0xa/0xc
>        [<c029b587>] __cpufreq_driver_target+0x15/0x50
>        [<c029c3ca>] cpufreq_governor_performance+0x1a/0x20
>        [<c029a89b>] __cpufreq_governor+0x95/0x18c
>        [<c029aa72>] __cpufreq_set_policy+0xe0/0x118
>        [<c029af49>] cpufreq_set_policy+0x2d/0x6f
>        [<c029bc45>] cpufreq_add_dev+0x3ee/0x4f3
>        [<c024dccb>] sysdev_driver_register+0x5e/0x9e
>        [<c029be70>] cpufreq_register_driver+0x80/0xf4
>        [<fdba202a>] 0xfdba202a
>        [<c0140f22>] sys_init_module+0xa6/0x21d
>        [<c0103179>] sysenter_past_esp+0x56/0x8d
>
> -> #0 (&inode->i_data.tree_lock){.+..}:
>        [<c0139a55>] lock_acquire+0x71/0x91
>        [<c02ee288>] __mutex_lock_slowpath+0xd2/0x2f5
>        [<c02ee4c7>] mutex_lock+0x1c/0x1f
>        [<c029b7f2>] store_scaling_governor+0x14a/0x1a2
>        [<c029b223>] store+0x37/0x48
>        [<c01a9f4b>] sysfs_write_file+0xa6/0xcc
>        [<c0172dab>] vfs_write+0xc9/0x172
>        [<c017341d>] sys_write+0x3b/0x71
>        [<c0103179>] sysenter_past_esp+0x56/0x8d
>
> other info that might help us debug this:
>
> 1 lock held by cpuspeed/1426:
>  #0:  (cpucontrol){--..}, at: [<c02ee4c7>] mutex_lock+0x1c/0x1f
>
> stack backtrace:
>  [<c01041f0>] show_trace_log_lvl+0x54/0x101
>  [<c0104827>] show_trace+0xd/0x10
>  [<c0104949>] dump_stack+0x19/0x1b
>  [<c0138b99>] print_circular_bug_tail+0x59/0x64
>  [<c013950a>] __lock_acquire+0x966/0xb39
>  [<c0139a55>] lock_acquire+0x71/0x91
>  [<c02ee288>] __mutex_lock_slowpath+0xd2/0x2f5
>  [<c02ee4c7>] mutex_lock+0x1c/0x1f
>  [<c029b7f2>] store_scaling_governor+0x14a/0x1a2
>  [<c029b223>] store+0x37/0x48
>  [<c01a9f4b>] sysfs_write_file+0xa6/0xcc
>  [<c0172dab>] vfs_write+0xc9/0x172
>  [<c017341d>] sys_write+0x3b/0x71
>  [<c0103179>] sysenter_past_esp+0x56/0x8d
>
> Here is a dmesg log
> http://www.stardust.webpages.pl/files/mm/2.6.18-rc1-mm1/mm-dmesg
>
> Here is a config file
> http://www.stardust.webpages.pl/files/mm/2.6.18-rc1-mm1/mm-config
>
> Regards,
> Michal
>
> --
> Michal K. K. Piotrowski
> LTG - Linux Testers Group
> (http://www.stardust.webpages.pl/ltg/wiki/)
>


-- 
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)

Re: 2.6.18-rc1-mm1

[Andrew Morton]

On Sun, 9 Jul 2006 12:26:45 +0200
"Fabio Comolli" <fabio.comolli@gmail.com> wrote:

> =======================================================
> [ INFO: possible circular locking dependency detected ]
> -------------------------------------------------------
> cpuspeed/1520 is trying to acquire lock:
>  (&policy->lock){--..}, at: [<c02c130f>] mutex_lock+0x21/0x24
> 
> but task is already holding lock:
>  (cpucontrol){--..}, at: [<c02c130f>] mutex_lock+0x21/0x24
> 
> which lock already depends on the new lock.

Yeah, that's lock_cpu_hotplug().  We've made a complete and utter mess of
that thing.

And I don't know how to fix it, really.  Is it a highly-localised innermost
lock?  Or a broad-coverage outermost lock?  Nobody knows, neither suits.

I'm suspecting is was a bad idea and we should just rip it out altogether.

- If a piece of kernel code is dealing with cpu-local data it needs to be
  running atomically, and that'll hold off hot hotplug anyway.

- If a piece of kernel code is dealing with per-cpu data and cannot run
  atomically then it should have its own cpu hotplug handlers anyway.  It
  is up to that code (ie: cpufreq) to provide its own locking against its
  own CPU hotplug callback.

Voila, no more lock_cpu_hotplug().

Re: 2.6.18-rc1-mm1

[Andrew Morton]

On Sun, 9 Jul 2006 12:32:27 +0200
"Michal Piotrowski" <michal.k.k.piotrowski@gmail.com> wrote:

> Hi,
> 
> On 09/07/06, Andrew Morton <akpm@osdl.org> wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> >
> 
> This looks like a problem with cpufreq.
> 
> =======================================================
> [ INFO: possible circular locking dependency detected ]
> -------------------------------------------------------
> cpuspeed/1426 is trying to acquire lock:
>  (&inode->i_data.tree_lock){.+..}, at: [<c0151dc7>] find_get_page+0x12/0x70
> 
> but task is already holding lock:
>  (&mm->mmap_sem){----}, at: [<c0116cab>] do_page_fault+0x10d/0x4ea
> 
> which lock already depends on the new lock.
> 

rofl.  You broke lockdep.

Well.  I guess it's barely conceivable that you earlier took an oops while
holding tree_lock, so lockdep decided that mmap_sem nests inside tree_lock.


> the existing dependency chain (in reverse order) is:
> 
> -> #1 (cpucontrol){--..}:
>        [<c0139a55>] lock_acquire+0x71/0x91
>        [<c02ee288>] __mutex_lock_slowpath+0xd2/0x2f5
>        [<c02ee4c7>] mutex_lock+0x1c/0x1f
>        [<c013dd3b>] __lock_cpu_hotplug+0x34/0x4c
>        [<c013dd6c>] lock_cpu_hotplug+0xa/0xc
>        [<c029b587>] __cpufreq_driver_target+0x15/0x50
>        [<c029c3ca>] cpufreq_governor_performance+0x1a/0x20
>        [<c029a89b>] __cpufreq_governor+0x95/0x18c
>        [<c029aa72>] __cpufreq_set_policy+0xe0/0x118
>        [<c029af49>] cpufreq_set_policy+0x2d/0x6f
>        [<c029bc45>] cpufreq_add_dev+0x3ee/0x4f3
>        [<c024dccb>] sysdev_driver_register+0x5e/0x9e
>        [<c029be70>] cpufreq_register_driver+0x80/0xf4
>        [<fdba202a>] 0xfdba202a
>        [<c0140f22>] sys_init_module+0xa6/0x21d
>        [<c0103179>] sysenter_past_esp+0x56/0x8d
> 
> -> #0 (&inode->i_data.tree_lock){.+..}:
>        [<c0139a55>] lock_acquire+0x71/0x91
>        [<c02ee288>] __mutex_lock_slowpath+0xd2/0x2f5
>        [<c02ee4c7>] mutex_lock+0x1c/0x1f
>        [<c029b7f2>] store_scaling_governor+0x14a/0x1a2
>        [<c029b223>] store+0x37/0x48
>        [<c01a9f4b>] sysfs_write_file+0xa6/0xcc
>        [<c0172dab>] vfs_write+0xc9/0x172
>        [<c017341d>] sys_write+0x3b/0x71
>        [<c0103179>] sysenter_past_esp+0x56/0x8d

Straightforward ab/ba deadlock between cpufreq_policy.lock and
lock_cpu_hotplug().  But lockdep got confused about the identity of the
lock.

Re: 2.6.18-rc1-mm1

[Michal Piotrowski]

On 09/07/06, Andrew Morton <akpm@osdl.org> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
>

LTP hangs on

<<<test_output>>>
setrlimit01    1  PASS  :  RLIMIT_NOFILE functionality is correct
setrlimit01    0  WARN  :  caught signal 2, not SIGSEGV
<<<execution_status>>>
duration=1071 termination_type=driver_interrupt termination_id=1 corefile=no
cutime=0 cstime=1
<<<test_end>>>

[michal@ltg01-fedora linux-mm]$ ps aux | grep setr
root      5155 99.1  0.0   1612   188 pts/0    R    12:39  20:30 setrlimit01

sudo kill -9 5155

[michal@ltg01-fedora linux-mm]$ ps aux | grep setr
root      5155 99.0  0.0   1612   188 pts/0    R    12:39  20:57 setrlimit01

unkillable process? I'll try to strace this.

Regards,
Michal

-- 
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)

Re: 2.6.18-rc1-mm1

[Michal Piotrowski]

On 09/07/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> On 09/07/06, Andrew Morton <akpm@osdl.org> wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> >
>
> LTP hangs on
>
> <<<test_output>>>
> setrlimit01    1  PASS  :  RLIMIT_NOFILE functionality is correct
> setrlimit01    0  WARN  :  caught signal 2, not SIGSEGV
> <<<execution_status>>>
> duration=1071 termination_type=driver_interrupt termination_id=1 corefile=no
> cutime=0 cstime=1
> <<<test_end>>>
>
> [michal@ltg01-fedora linux-mm]$ ps aux | grep setr
> root      5155 99.1  0.0   1612   188 pts/0    R    12:39  20:30 setrlimit01
>
> sudo kill -9 5155
>
> [michal@ltg01-fedora linux-mm]$ ps aux | grep setr
> root      5155 99.0  0.0   1612   188 pts/0    R    12:39  20:57 setrlimit01
>
> unkillable process? I'll try to strace this.
>

Here is a strace output
http://www.stardust.webpages.pl/files/mm/2.6.18-rc1-mm1/strace.txt

Regards,
Michal

-- 
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)

Re: 2.6.18-rc1-mm1

[Reuben Farrelly]

On 9/07/2006 9:11 p.m., Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> 
> - We're getting a relatively large number of crash reports coming out of the
>   core sysfs/kobject/driver/bus code, and they're all really hard to diagnose.
> 
>   I am suspecting that what's happening is that some registration functions
>   are failing and the caller is ignoring that failure.  The code proceeds and
>   crashes much later, in obscure ways.
> 
>   All these functions return error codes, and we're not checking them.  We
>   should.  So there's a patch which marks all these things as __must_check,
>   which causes around 1,500 new warnings.
> 
>   These are all bugs and they all need to be fixed.

Works.  Well, it boots without crashing here and has been up for 30 or so 
minutes without incident or so much as a log entry.

I assume that the bulk of those warnings about the return error codes will be 
largely dealt with by individual maintainers as there are far too many to post here?

Some minor problems noted - possibly PCI/ACPI related (read on past the IDE bit 
if that's not your cup of tea).

1. I've disabled the old IDE stuff and enabled Alan's IDE support 
(CONFIG_SCSI_ATA_GENERIC=y).  But it seems to be a bit unhappy with my IDE CD 
burner:

ata_piix 0000:00:1f.1: version 2.00ac5
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1f.1 to 64
ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x30B0 irq 14
scsi4 : ata_piix
ata5.00: ATAPI, max UDMA/66
ata5.00: configured for UDMA/66
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata5.00: (BMDMA stat 0x24)
ata5.00: tag 0 cmd 0xa0 Emask 0x4 stat 0x40 err 0x0 (timeout)
ata5: soft resetting port
ata5.00: configured for UDMA/66
ata5: EH complete
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata5.00: (BMDMA stat 0x24)
ata5.00: tag 0 cmd 0xa0 Emask 0x4 stat 0x40 err 0x0 (timeout)
ata5: soft resetting port
ata5.00: configured for UDMA/66
Losing some ticks... checking if CPU frequency changed.
ata5: EH complete
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata5.00: (BMDMA stat 0x24)
ata5.00: tag 0 cmd 0xa0 Emask 0x4 stat 0x40 err 0x0 (timeout)
ata5: soft resetting port
ata5.00: configured for UDMA/66
ata5: EH complete
ata5.00: limiting speed to UDMA/44
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata5.00: (BMDMA stat 0x24)
ata5.00: tag 0 cmd 0xa0 Emask 0x4 stat 0x40 err 0x0 (timeout)
ata5: soft resetting port
ata5.00: configured for UDMA/44
ata5: EH complete
ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x30B8 irq 15
scsi5 : ata_piix
ata6: port disabled. ignoring.
ATA: abnormal status 0xFF on port 0x177
SCSI device sda: 586072368 512-byte hdwr sectors (300069 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back

Note also the message midway through about losing some ticks, which if I recall 
correctly is not new to this -mm release.  I'm not sure who to cc about this.

The IDE device obviously ended up not being detected by the system.  Usually 
this device comes up as:

Jul  2 12:03:28 tornado kernel: hda: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 
2000kB Cache, UDMA(66)


2. Onto some more minor warnings:

ACPI: bus type pci registered
PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
PCI: Not using MMCONFIG.
PCI: Using configuration type 1
ACPI: Interpreter enabled

Is there any way to verify that there really is a BIOS bug there?  If it is, is 
there anyone within Intel or are there any known contacts who can push and poke 
to get this looked at/fixed?  (It's a new Intel board, I'd hope they could get 
it right..).

Plus we're not using MMCONFIG - even though I have it enabled.

Based on previous postings to lkml, I believe Randy Dunlap may have one of these 
boards too - Randy are you seeing this and the next bunch of warnings I am seeing?

3. Power Management warnings, been there ages, but I've had bigger things to 
worry about (like fatal oopses) so haven't bothered asking:

Device `[PEX0]' is not power manageable
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1c.0 to 64
Device `[PEX2]' is not power manageable
ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1c.2 to 64
Device `[PEX3]' is not power manageable
ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1c.3 to 64
Device `[PEX4]' is not power manageable
ACPI: PCI Interrupt 0000:00:1c.4[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1c.4 to 64
Device `[PEX5]' is not power manageable
ACPI: PCI Interrupt 0000:00:1c.5[B] -> GSI 16 (level, low) -> IRQ 16

and

Device `[IDES]' is not power manageable

[root@tornado ~]# cat /proc/interrupts
            CPU0       CPU1
   0:     258266          0   IO-APIC-edge     timer
   4:        355          0   IO-APIC-edge     serial
   6:          5          0   IO-APIC-edge     floppy
   8:          1          0   IO-APIC-edge     rtc
   9:          0          0   IO-APIC-fasteoi  acpi
  14:         28          0   IO-APIC-edge     libata
  15:          0          0   IO-APIC-edge     libata
  16:          0          0   IO-APIC-fasteoi  uhci_hcd:usb5
  18:          0          0   IO-APIC-fasteoi  uhci_hcd:usb4
  19:        980          0   IO-APIC-fasteoi  uhci_hcd:usb3, serial
  23:        105          0   IO-APIC-fasteoi  ehci_hcd:usb1, uhci_hcd:usb2
313:      82513          0   PCI-MSI-<NULL>  eth0
314:      57370          0   PCI-MSI-<NULL>  libata
NMI:        217        188
LOC:     258118     257890
ERR:          0
MIS:          0
[root@tornado ~]#

The full dmesg is up at http://www.reub.net/files/kernel/2.6.18-rc1-mm1.dmesg 
and config is up at http://www.reub.net/files/kernel/2.6.18-rc1-mm1.config

Minor issues and possibly most if not all are not of concern, but occasionally 
supposedly minor things show up much bigger problems when questions are asked 
and people start poking around :)

Reuben

Re: 2.6.18-rc1-mm1

[Andrew Morton]

On Sun, 9 Jul 2006 13:02:48 +0200
"Michal Piotrowski" <michal.k.k.piotrowski@gmail.com> wrote:

> TP hangs on
> 
> <<<test_output>>>
> setrlimit01    1  PASS  :  RLIMIT_NOFILE functionality is correct
> setrlimit01    0  WARN  :  caught signal 2, not SIGSEGV
> <<<execution_status>>>
> duration=1071 termination_type=driver_interrupt termination_id=1 corefile=no
> cutime=0 cstime=1
> <<<test_end>>>

Yep, thanks.


RLIMIT_FSIZE can cause generic_write_checks() to reduce `count'.  So we cannot
assume that `count' is equal to the total length size of the incoming iovec.

--- a/mm/filemap.c~add-address_space_operationsbatch_write-fix
+++ a/mm/filemap.c
@@ -2205,9 +2205,9 @@ generic_file_buffered_write(struct kiocb
 	do {
 		/* do not walk over current segment */
 		desc.buf = cur_iov->iov_base + iov_base;
-		desc.count = cur_iov->iov_len - iov_base;
+		desc.count = min(count, cur_iov->iov_len - iov_base);
 		if (desc.count > 0)
-			status = batch_write(file, &desc, &copied);
+			status = (*batch_write)(file, &desc, &copied);
 		else {
 			copied = 0;
 			status = 0;
_

Re: 2.6.18-rc1-mm1

[Andrew Morton]

On Sun, 09 Jul 2006 23:22:14 +1200
Reuben Farrelly <reuben-lkml@reub.net> wrote:

> 
> 
> On 9/07/2006 9:11 p.m., Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> > 
> > - We're getting a relatively large number of crash reports coming out of the
> >   core sysfs/kobject/driver/bus code, and they're all really hard to diagnose.
> > 
> >   I am suspecting that what's happening is that some registration functions
> >   are failing and the caller is ignoring that failure.  The code proceeds and
> >   crashes much later, in obscure ways.
> > 
> >   All these functions return error codes, and we're not checking them.  We
> >   should.  So there's a patch which marks all these things as __must_check,
> >   which causes around 1,500 new warnings.
> > 
> >   These are all bugs and they all need to be fixed.
> 
> Works.  Well, it boots without crashing here and has been up for 30 or so 
> minutes without incident or so much as a log entry.

Shock.  Have you tested suspend-to-ram and suspend-to-disk?

> I assume that the bulk of those warnings about the return error codes will be 
> largely dealt with by individual maintainers as there are far too many to post here?

I admire your faith in your fellow man.  I'll see what can be done to
reduce the warnings by changing some deregistration/removal API
functions so they return void.  That should remove maybe half of them.

As for the rest I guess we just need to slam that patch into mainline and
start bitching at people.


> Some minor problems noted - possibly PCI/ACPI related (read on past the IDE bit 
> if that's not your cup of tea).
> 
> 1. I've disabled the old IDE stuff and enabled Alan's IDE support 
> (CONFIG_SCSI_ATA_GENERIC=y).  But it seems to be a bit unhappy with my IDE CD 
> burner:
> 
> ata_piix 0000:00:1f.1: version 2.00ac5
> ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18
> PCI: Setting latency timer of device 0000:00:1f.1 to 64
> ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x30B0 irq 14
> scsi4 : ata_piix
> ata5.00: ATAPI, max UDMA/66
> ata5.00: configured for UDMA/66
> ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata5.00: (BMDMA stat 0x24)
> ata5.00: tag 0 cmd 0xa0 Emask 0x4 stat 0x40 err 0x0 (timeout)
> ata5: soft resetting port
> ata5.00: configured for UDMA/66
> ata5: EH complete
> ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata5.00: (BMDMA stat 0x24)
> ata5.00: tag 0 cmd 0xa0 Emask 0x4 stat 0x40 err 0x0 (timeout)
> ata5: soft resetting port
> ata5.00: configured for UDMA/66
> Losing some ticks... checking if CPU frequency changed.
> ata5: EH complete
> ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata5.00: (BMDMA stat 0x24)
> ata5.00: tag 0 cmd 0xa0 Emask 0x4 stat 0x40 err 0x0 (timeout)
> ata5: soft resetting port
> ata5.00: configured for UDMA/66
> ata5: EH complete
> ata5.00: limiting speed to UDMA/44
> ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata5.00: (BMDMA stat 0x24)
> ata5.00: tag 0 cmd 0xa0 Emask 0x4 stat 0x40 err 0x0 (timeout)
> ata5: soft resetting port
> ata5.00: configured for UDMA/44
> ata5: EH complete
> ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x30B8 irq 15
> scsi5 : ata_piix
> ata6: port disabled. ignoring.
> ATA: abnormal status 0xFF on port 0x177
> SCSI device sda: 586072368 512-byte hdwr sectors (300069 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: drive cache: write back

Alan stuff.

> Note also the message midway through about losing some ticks, which if I recall 
> correctly is not new to this -mm release.  I'm not sure who to cc about this.

John stuff.  I suspect it's natural and normal, if the IDE error handling
did something rude with interrupt holdoff.


> The IDE device obviously ended up not being detected by the system.  Usually 
> this device comes up as:
> 
> Jul  2 12:03:28 tornado kernel: hda: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 
> 2000kB Cache, UDMA(66)
> 
> 
> 2. Onto some more minor warnings:
> 
> ACPI: bus type pci registered
> PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
> PCI: Not using MMCONFIG.
> PCI: Using configuration type 1
> ACPI: Interpreter enabled
> 
> Is there any way to verify that there really is a BIOS bug there?  If it is, is 
> there anyone within Intel or are there any known contacts who can push and poke 
> to get this looked at/fixed?  (It's a new Intel board, I'd hope they could get 
> it right..).
> 
> Plus we're not using MMCONFIG - even though I have it enabled.

Andi stuff.

> Based on previous postings to lkml, I believe Randy Dunlap may have one of these 
> boards too - Randy are you seeing this and the next bunch of warnings I am seeing?
> 
> 3. Power Management warnings, been there ages, but I've had bigger things to 
> worry about (like fatal oopses) so haven't bothered asking:
> 
> Device `[PEX0]' is not power manageable
> ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 17
> PCI: Setting latency timer of device 0000:00:1c.0 to 64
> Device `[PEX2]' is not power manageable
> ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 18
> PCI: Setting latency timer of device 0000:00:1c.2 to 64
> Device `[PEX3]' is not power manageable
> ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 19
> PCI: Setting latency timer of device 0000:00:1c.3 to 64
> Device `[PEX4]' is not power manageable
> ACPI: PCI Interrupt 0000:00:1c.4[A] -> GSI 17 (level, low) -> IRQ 17
> PCI: Setting latency timer of device 0000:00:1c.4 to 64
> Device `[PEX5]' is not power manageable
> ACPI: PCI Interrupt 0000:00:1c.5[B] -> GSI 16 (level, low) -> IRQ 16

ACPI stuff.  I suspect the kernel isn't doing anything wrong here.

> and
> 
> Device `[IDES]' is not power manageable

I don't know what device that is.

> [root@tornado ~]# cat /proc/interrupts
>             CPU0       CPU1
>    0:     258266          0   IO-APIC-edge     timer
>    4:        355          0   IO-APIC-edge     serial
>    6:          5          0   IO-APIC-edge     floppy
>    8:          1          0   IO-APIC-edge     rtc
>    9:          0          0   IO-APIC-fasteoi  acpi
>   14:         28          0   IO-APIC-edge     libata
>   15:          0          0   IO-APIC-edge     libata
>   16:          0          0   IO-APIC-fasteoi  uhci_hcd:usb5
>   18:          0          0   IO-APIC-fasteoi  uhci_hcd:usb4
>   19:        980          0   IO-APIC-fasteoi  uhci_hcd:usb3, serial
>   23:        105          0   IO-APIC-fasteoi  ehci_hcd:usb1, uhci_hcd:usb2
> 313:      82513          0   PCI-MSI-<NULL>  eth0
> 314:      57370          0   PCI-MSI-<NULL>  libata
> NMI:        217        188
> LOC:     258118     257890
> ERR:          0
> MIS:          0
> [root@tornado ~]#
> 
> The full dmesg is up at http://www.reub.net/files/kernel/2.6.18-rc1-mm1.dmesg 
> and config is up at http://www.reub.net/files/kernel/2.6.18-rc1-mm1.config
> 
> Minor issues and possibly most if not all are not of concern, but occasionally 
> supposedly minor things show up much bigger problems when questions are asked 
> and people start poking around :)
> 

Thanks.

Re: 2.6.18-rc1-mm1

[Nick Piggin]

Andrew Morton wrote:
> On Sun, 9 Jul 2006 12:26:45 +0200
> "Fabio Comolli" <fabio.comolli@gmail.com> wrote:
> 
> 
>>=======================================================
>>[ INFO: possible circular locking dependency detected ]
>>-------------------------------------------------------
>>cpuspeed/1520 is trying to acquire lock:
>> (&policy->lock){--..}, at: [<c02c130f>] mutex_lock+0x21/0x24
>>
>>but task is already holding lock:
>> (cpucontrol){--..}, at: [<c02c130f>] mutex_lock+0x21/0x24
>>
>>which lock already depends on the new lock.
> 
> 
> Yeah, that's lock_cpu_hotplug().  We've made a complete and utter mess of
> that thing.
> 
> And I don't know how to fix it, really.  Is it a highly-localised innermost
> lock?  Or a broad-coverage outermost lock?  Nobody knows, neither suits.
> 
> I'm suspecting is was a bad idea and we should just rip it out altogether.
> 
> - If a piece of kernel code is dealing with cpu-local data it needs to be
>   running atomically, and that'll hold off hot hotplug anyway.

These guys don't need lock_cpu_hotplug() today.

> 
> - If a piece of kernel code is dealing with per-cpu data and cannot run
>   atomically then it should have its own cpu hotplug handlers anyway.  It
>   is up to that code (ie: cpufreq) to provide its own locking against its
>   own CPU hotplug callback.

This still does not solve this cpufreq problem where it is trying to
take the same lock twice down the same call path. Whether it is the
lock_cpu_hotplug mutex or another one, the code must be just busted.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

Re: 2.6.18-rc1-mm1

[Nick Piggin]

Nick Piggin wrote:
> Andrew Morton wrote:

>>
>> - If a piece of kernel code is dealing with per-cpu data and cannot run
>>   atomically then it should have its own cpu hotplug handlers anyway.  It
>>   is up to that code (ie: cpufreq) to provide its own locking against its
>>   own CPU hotplug callback.
> 
> 
> This still does not solve this cpufreq problem where it is trying to
> take the same lock twice down the same call path. Whether it is the
> lock_cpu_hotplug mutex or another one, the code must be just busted.
> 

Err...

s/twice down the same call path/inverted with another lock

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

Re: 2.6.18-rc1-mm1

[Alan Cox]

Ar Sul, 2006-07-09 am 05:22 -0700, ysgrifennodd Andrew Morton:
> > ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x30B0 irq 14
> > scsi4 : ata_piix
> > ata5.00: ATAPI, max UDMA/66
> > ata5.00: configured for UDMA/66

More ATAPI devices getting uppity about mode setting.

> John stuff.  I suspect it's natural and normal, if the IDE error handling
> did something rude with interrupt holdoff.

The new libata should be more polite than that, although since the ATA
drive can stall the CPU indefinitely you lose anyway 8(

> > Jul  2 12:03:28 tornado kernel: hda: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 
> > 2000kB Cache, UDMA(66)

Can you send me the full hdparm identify stuff for this ?


The old drivers/ide code uses much longer delays than the spec for some
ATAPI commands, and it looks as if there is a good reason for doing
so ...

That or I've got a mistuning case I've missed.

Alan

Re: 2.6.18-rc1-mm1

[Michal Piotrowski]

On 09/07/06, Andrew Morton <akpm@osdl.org> wrote:
> On Sun, 9 Jul 2006 13:02:48 +0200
> "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com> wrote:
>
> > TP hangs on
> >
> > <<<test_output>>>
> > setrlimit01    1  PASS  :  RLIMIT_NOFILE functionality is correct
> > setrlimit01    0  WARN  :  caught signal 2, not SIGSEGV
> > <<<execution_status>>>
> > duration=1071 termination_type=driver_interrupt termination_id=1 corefile=no
> > cutime=0 cstime=1
> > <<<test_end>>>
>
> Yep, thanks.
>
>
> RLIMIT_FSIZE can cause generic_write_checks() to reduce `count'.  So we cannot
> assume that `count' is equal to the total length size of the incoming iovec.
>

Problem solved, thanks.

Regards,
Michal

-- 
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)

Re: 2.6.18-rc1-mm1

[Reuben Farrelly]

On 10/07/2006 12:56 a.m., Alan Cox wrote:
> Ar Sul, 2006-07-09 am 05:22 -0700, ysgrifennodd Andrew Morton:
>>> ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x30B0 irq 14
>>> scsi4 : ata_piix
>>> ata5.00: ATAPI, max UDMA/66
>>> ata5.00: configured for UDMA/66
> 
> More ATAPI devices getting uppity about mode setting.
> 
>> John stuff.  I suspect it's natural and normal, if the IDE error handling
>> did something rude with interrupt holdoff.
> 
> The new libata should be more polite than that, although since the ATA
> drive can stall the CPU indefinitely you lose anyway 8(

It may not be related to ATA.  I just reloaded into 2.6.17-mm6 to get the info 
for Alan and saw it when booting up on that too:

PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
Losing some ticks... checking if CPU frequency changed.
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 128 is not supported by device 0000:00:1d.7

Note it was in a different place in here than in -rc1-mm1 (slightly later in the 
bootup).

I'm fairly sure it's not new to this release.

>>> Jul  2 12:03:28 tornado kernel: hda: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 
>>> 2000kB Cache, UDMA(66)
> 
> Can you send me the full hdparm identify stuff for this ?

sh-3.1# hdparm -I /dev/hda

/dev/hda:

ATAPI CD-ROM, with removable media
         Model Number:       PIONEER DVD-RW  DVR-111D
         Serial Number:      FADC005671WL
         Firmware Revision:  1.23
Standards:
         Likely used CD-ROM ATAPI-1
Configuration:
         DRQ response: 50us.
         Packet size: 12 bytes
Capabilities:
         LBA, IORDY(can be disabled)
         Buffer size: 64.0kB
         DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
              Cycle time: min=120ns recommended=120ns
         PIO: pio0 pio1 pio2 pio3 pio4
              Cycle time: no flow control=240ns  IORDY flow control=120ns
Commands/features:
         Enabled Supported:
            *    Power Management feature set
            *    PACKET command feature set
            *    DEVICE_RESET command
HW reset results:
         CBLID- above Vih
         Device num = 0 determined by the jumper
sh-3.1#
sh-3.1# hdparm -i /dev/hda

/dev/hda:

  Model=PIONEER DVD-RW DVR-111D, FwRev=1.23, SerialNo=
  Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
  RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
  BuffType=13395, BuffSize=64kB, MaxMultSect=0
  (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
  IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
  PIO modes:  pio0 pio1 pio2 pio3 pio4
  DMA modes:  mdma0 mdma1 mdma2
  UDMA modes: udma0 udma1 udma2 udma3 *udma4
  AdvancedPM=no
  Drive conforms to: Unspecified:  ATA/ATAPI-2 ATA/ATAPI-3 ATA/ATAPI-4 ATA/ATAPI-5

  * signifies the current active mode

sh-3.1#


Reuben

Re: 2.6.18-rc1-mm1

[Jeff Garzik]

Alan Cox wrote:
> The old drivers/ide code uses much longer delays than the spec for some
> ATAPI commands, and it looks as if there is a good reason for doing
> so ...


FWIW, the code that ATADRVR (http://www.ata-atapi.com/) uses to issue 
commands does something like

	write Command register to start command
	if (device == ATAPI)			# i.e. not ATA
		delay(150 msec)
	pound Status / AltStatus, kick DMA engine, whatever else

ATADRVR is open code (for an MS-DOS-level driver), and really worth a 
read.  Between ATADRVR and drivers/ide, you get a pretty good idea about 
what __field experience__ has shown is needed for ATAPI devices.

	Jeff

Re: 2.6.18-rc1-mm1

[Dominik Karall]

On Sunday, 9. July 2006 11:11, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1
>8-rc1/2.6.18-rc1-mm1/

There are stil problems with initializing the bt878 chip. I'm not sure 
if it is the same bug, but I had problems with all -mm versions since 
2.6.17-mm1
Screenshot: 
http://stud4.tuwien.ac.at/~e0227135/kernel/060709_190546.jpg

I'm sorry about the quality, but I have only a mobile here.

hth,
dominik

Re: 2.6.18-rc1-mm1

[Randy.Dunlap]

On Sun, 09 Jul 2006 23:22:14 +1200 Reuben Farrelly wrote:

> On 9/07/2006 9:11 p.m., Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> > 
> > - We're getting a relatively large number of crash reports coming out of the
> >   core sysfs/kobject/driver/bus code, and they're all really hard to diagnose.
> > 
> >   I am suspecting that what's happening is that some registration functions
> >   are failing and the caller is ignoring that failure.  The code proceeds and
> >   crashes much later, in obscure ways.
> > 
> >   All these functions return error codes, and we're not checking them.  We
> >   should.  So there's a patch which marks all these things as __must_check,
> >   which causes around 1,500 new warnings.
> > 
> >   These are all bugs and they all need to be fixed.
> 
> Works.  Well, it boots without crashing here and has been up for 30 or so 
> minutes without incident or so much as a log entry.
> 
> I assume that the bulk of those warnings about the return error codes will be 
> largely dealt with by individual maintainers as there are far too many to post here?

Yeah, right.  (quoting Kathy Mallory with her usual sarcasm)


> Some minor problems noted - possibly PCI/ACPI related (read on past the IDE bit 
> if that's not your cup of tea).
> 
> 2. Onto some more minor warnings:
> 
> ACPI: bus type pci registered
> PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
> PCI: Not using MMCONFIG.
> PCI: Using configuration type 1
> ACPI: Interpreter enabled
> 
> Is there any way to verify that there really is a BIOS bug there?  If it is, is 
> there anyone within Intel or are there any known contacts who can push and poke 
> to get this looked at/fixed?  (It's a new Intel board, I'd hope they could get 
> it right..).
> 
> Plus we're not using MMCONFIG - even though I have it enabled.
> 
> Based on previous postings to lkml, I believe Randy Dunlap may have one of these 
> boards too - Randy are you seeing this and the next bunch of warnings I am seeing?

I just found 2.6.18-rc1-mm1.  I'll build + check.
I have an Intel ICH7 motherboard with SATA.
Is that close to what you have?


> 3. Power Management warnings, been there ages, but I've had bigger things to 
> worry about (like fatal oopses) so haven't bothered asking:
> 
> Device `[PEX0]' is not power manageable
> ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 17
> PCI: Setting latency timer of device 0000:00:1c.0 to 64
> Device `[PEX2]' is not power manageable
> ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 18
> PCI: Setting latency timer of device 0000:00:1c.2 to 64
> Device `[PEX3]' is not power manageable
> ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 19
> PCI: Setting latency timer of device 0000:00:1c.3 to 64
> Device `[PEX4]' is not power manageable
> ACPI: PCI Interrupt 0000:00:1c.4[A] -> GSI 17 (level, low) -> IRQ 17
> PCI: Setting latency timer of device 0000:00:1c.4 to 64
> Device `[PEX5]' is not power manageable
> ACPI: PCI Interrupt 0000:00:1c.5[B] -> GSI 16 (level, low) -> IRQ 16
> 
> and
> 
> Device `[IDES]' is not power manageable

I guess that's from here:

/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDES

which contains 2 directories:  PRID and SECD.
Apparently ATA/IDE primary and secondary controllers,
but I'm not sure.  Those empty directory structures
don't tell me much.


> [root@tornado ~]# cat /proc/interrupts
>             CPU0       CPU1
>    0:     258266          0   IO-APIC-edge     timer
>    4:        355          0   IO-APIC-edge     serial
>    6:          5          0   IO-APIC-edge     floppy
>    8:          1          0   IO-APIC-edge     rtc
>    9:          0          0   IO-APIC-fasteoi  acpi
>   14:         28          0   IO-APIC-edge     libata
>   15:          0          0   IO-APIC-edge     libata
>   16:          0          0   IO-APIC-fasteoi  uhci_hcd:usb5
>   18:          0          0   IO-APIC-fasteoi  uhci_hcd:usb4
>   19:        980          0   IO-APIC-fasteoi  uhci_hcd:usb3, serial
>   23:        105          0   IO-APIC-fasteoi  ehci_hcd:usb1, uhci_hcd:usb2
> 313:      82513          0   PCI-MSI-<NULL>  eth0
> 314:      57370          0   PCI-MSI-<NULL>  libata

"We" need to fix that <NULL> there.

> NMI:        217        188
> LOC:     258118     257890
> ERR:          0
> MIS:          0
> [root@tornado ~]#
> 
> The full dmesg is up at http://www.reub.net/files/kernel/2.6.18-rc1-mm1.dmesg 
> and config is up at http://www.reub.net/files/kernel/2.6.18-rc1-mm1.config

---
~Randy

RE: 2.6.18-rc1-mm1

[Brown, Len]

>> 2. Onto some more minor warnings:
>> 
>> ACPI: bus type pci registered
>> PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
>> PCI: Not using MMCONFIG.
>> PCI: Using configuration type 1
>> ACPI: Interpreter enabled
>> 
>> Is there any way to verify that there really is a BIOS bug 
>there?  If it is, is there anyone within Intel or are there any
>known contacts 
>who can push and poke > to get this looked at/fixed?
>(It's a new Intel board, I'd hope they could get it right..).

Arjan should probably comment on that one.

>> 3. Power Management warnings, been there ages, but I've had 
>bigger things to 
>> worry about (like fatal oopses) so haven't bothered asking:
>> 
>> Device `[PEX0]' is not power manageable
>> ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 17
>> PCI: Setting latency timer of device 0000:00:1c.0 to 64
>> Device `[PEX2]' is not power manageable

I'll revert this message to CONFIG_ACPI_DEBUG=y like it used to be.

>I guess that's from here:
>
>/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDES
>
>which contains 2 directories:  PRID and SECD.
>Apparently ATA/IDE primary and secondary controllers,
>but I'm not sure.  Those empty directory structures
>don't tell me much.

/sys/firmware/acpi/namespace should not exist at all
and is waiting to die.  You can ignore it.

cheers,
-Len

Re: 2.6.18-rc1-mm1

[Andi Kleen]

On Sun, Jul 09, 2006 at 05:22:52AM -0700, Andrew Morton wrote:
> > ACPI: bus type pci registered
> > PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
> > PCI: Not using MMCONFIG.
> > PCI: Using configuration type 1
> > ACPI: Interpreter enabled
> > 
> > Is there any way to verify that there really is a BIOS bug there?  If it is, is 
> > there anyone within Intel or are there any known contacts who can push and poke 
> > to get this looked at/fixed?  (It's a new Intel board, I'd hope they could get 
> > it right..).
> > 
> > Plus we're not using MMCONFIG - even though I have it enabled.
> 
> Andi stuff.

Greg has patches to relax the checking a bit. 

I don't know when he intends to merge them.

Anyways it should be completely harmless - mmconfig does nothing
essential right now.

-Andi

Re: 2.6.18-rc1-mm1

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 1783 bytes --]

On Sun, 09 Jul 2006 02:11:06 PDT, Andrew Morton said:
> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/

Congrats to all the maintainers I've hassled the last few -mm's (in particular,
Alan Cox, Roman Zippel, and John Stultz) - this one came up basically OK..

1) The timer issues with booting with 'vga=794' causing slow console output
and confusing the error correcting seem resolved - the problem section of
early userspace is back to the 2-3 seconds it used to be, rather than 2-3 mins.

2) libata is now setting the speeds sanely for both IDE devices:

[    7.808637] libata version 2.00 loaded.
[    7.808888] ata_piix 0000:00:1f.1: version 2.00ac5
[    7.808908] PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
[    7.810374] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
[    7.810910] ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
[    7.811767] PCI: Setting latency timer of device 0000:00:1f.1 to 64
[    7.811855] ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0xBFA0 irq 14
[    7.812510] scsi0 : ata_piix
[    7.964218] ata1.00: ATA-6, max UDMA/100, 117210240 sectors: LBA 
[    7.964790] ata1.00: ata1: dev 0 multi count 8
[    8.116060] ata1.01: ATAPI, max UDMA/33
[    8.121104] ata1.00: configured for UDMA/100
[    8.272621] ata1.01: configured for UDMA/33
[    8.273139]   Vendor: ATA       Model: FUJITSU MHV2060A  Rev: 0000
[    8.274258]   Type:   Direct-Access                      ANSI SCSI revision:05
[    8.277954]   Vendor: TOSHIBA   Model: CDRW/DVD SDR2102  Rev: 1D13
[    8.279074]   Type:   CD-ROM                             ANSI SCSI revision:05

(Alan - I *did* have to apply the piix_pata_ops to ich_pata_ops one-liner,
that didn't seem to be in -rc1-mm1).

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Re: 2.6.18-rc1-mm1

[Andrew Morton]

On Sun, 9 Jul 2006 19:28:07 +0200
Dominik Karall <dominik.karall@gmx.net> wrote:

> On Sunday, 9. July 2006 11:11, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1
> >8-rc1/2.6.18-rc1-mm1/
> 
> There are stil problems with initializing the bt878 chip. I'm not sure 
> if it is the same bug, but I had problems with all -mm versions since 
> 2.6.17-mm1
> Screenshot: 
> http://stud4.tuwien.ac.at/~e0227135/kernel/060709_190546.jpg
> 

Right - this is one of those mysterious crashes deep in sysfs from calling
code which basically hasn't changed.  Mauro and Greg are vacationing or
otherwise offline so not much is likely to happen short-term.

Is 2.6.18-rc1 OK?

Re: 2.6.18-rc1-mm1

[Arjan van de Ven]

On Sun, 2006-07-09 at 03:52 -0700, Andrew Morton wrote:
> On Sun, 9 Jul 2006 12:32:27 +0200
> "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com> wrote:
> 
> > Hi,
> > 
> > On 09/07/06, Andrew Morton <akpm@osdl.org> wrote:
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> > >
> > 
> > This looks like a problem with cpufreq.
> > 
> > =======================================================
> > [ INFO: possible circular locking dependency detected ]
> > -------------------------------------------------------
> > cpuspeed/1426 is trying to acquire lock:
> >  (&inode->i_data.tree_lock){.+..}, at: [<c0151dc7>] find_get_page+0x12/0x70
> > 
> > but task is already holding lock:
> >  (&mm->mmap_sem){----}, at: [<c0116cab>] do_page_fault+0x10d/0x4ea
> > 
> > which lock already depends on the new lock.
> > 
> 
> rofl.  You broke lockdep.
> 
> Well.  I guess it's barely conceivable that you earlier took an oops while
> holding tree_lock, so lockdep decided that mmap_sem nests inside tree_lock.

I think it would be justified to disable lockdep in an oops; after all
the kernel state can't really be trusted once that happen.... 

Re: 2.6.18-rc1-mm1

[john stultz]

On Sun, 2006-07-09 at 05:22 -0700, Andrew Morton wrote:
> On Sun, 09 Jul 2006 23:22:14 +1200
> Reuben Farrelly <reuben-lkml@reub.net> wrote:
> > Note also the message midway through about losing some ticks, which if I recall 
> > correctly is not new to this -mm release.  I'm not sure who to cc about this.
> 
> John stuff.  I suspect it's natural and normal, if the IDE error handling
> did something rude with interrupt holdoff.

Actually that's an x86-64 system, so the timekeeping changes shouldn't
really being affecting it.

thanks
-john

Re: 2.6.18-rc1-mm1

[john stultz]

On Sun, 2006-07-09 at 15:24 -0400, Valdis.Kletnieks@vt.edu wrote:
> On Sun, 09 Jul 2006 02:11:06 PDT, Andrew Morton said:
> > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> 
> Congrats to all the maintainers I've hassled the last few -mm's (in particular,
> Alan Cox, Roman Zippel, and John Stultz) - this one came up basically OK..
> 
> 1) The timer issues with booting with 'vga=794' causing slow console output
> and confusing the error correcting seem resolved - the problem section of
> early userspace is back to the 2-3 seconds it used to be, rather than 2-3 mins.

Great to hear! Thanks for all the testing and feedback! I really
appreciate it!

-john

Re: 2.6.18-rc1-mm1

[Andrew Morton]

On Sun, 9 Jul 2006 10:33:12 -0700
"Randy.Dunlap" <rdunlap@xenotime.net> wrote:

> > [root@tornado ~]# cat /proc/interrupts
> >             CPU0       CPU1
> >    0:     258266          0   IO-APIC-edge     timer
> >    4:        355          0   IO-APIC-edge     serial
> >    6:          5          0   IO-APIC-edge     floppy
> >    8:          1          0   IO-APIC-edge     rtc
> >    9:          0          0   IO-APIC-fasteoi  acpi
> >   14:         28          0   IO-APIC-edge     libata
> >   15:          0          0   IO-APIC-edge     libata
> >   16:          0          0   IO-APIC-fasteoi  uhci_hcd:usb5
> >   18:          0          0   IO-APIC-fasteoi  uhci_hcd:usb4
> >   19:        980          0   IO-APIC-fasteoi  uhci_hcd:usb3, serial
> >   23:        105          0   IO-APIC-fasteoi  ehci_hcd:usb1, uhci_hcd:usb2
> > 313:      82513          0   PCI-MSI-<NULL>  eth0
> > 314:      57370          0   PCI-MSI-<NULL>  libata
> 
> "We" need to fix that <NULL> there.

Seems that irq_desc[i].handle_irq is msi_irq_wo_maskbit_type or
msi_irq_w_maskbit_type and kernel/irq/chip.c:handle_irq_name() doesn't know
about that.

handle_irq_name() is a bit of a crock - this info should be in the irq_desc
struct or somewhere like that.

Re: 2.6.18-rc1-mm1

[J.A. Magallón]

On Sun, 9 Jul 2006 02:11:06 -0700, Andrew Morton <akpm@osdl.org> wrote:

> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> 

Booted fine and running, after changing my fstab to match the libata SATA/PATA
ordering.

More questions on this:
I also built in the sata-promise driver. With both ata_piix and sata_promise
builtin, host detenction seems to go in PCI order but... promise detects
first the SATA drives. I'm trying to get a way to predict what switchng
from IDE to libata will do on my boxes, but...

current state:

00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02)
03:04.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak 378/SATA 378) (rev 02)

ata_piix 0000:00:1f.1: version 2.00ac5
ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
ata3: SATA max UDMA/133 cmd 0xC000 ctl 0xC402 bmdma 0xD000 irq 16
ata4: SATA max UDMA/133 cmd 0xC800 ctl 0xCC02 bmdma 0xD008 irq 16
sata_promise 0000:03:04.0: version 1.04
ata5: SATA max UDMA/133 cmd 0xF8804200 ctl 0xF8804238 bmdma 0x0 irq 17
ata6: SATA max UDMA/133 cmd 0xF8804280 ctl 0xF88042B8 bmdma 0x0 irq 17
ata7: PATA max UDMA/133 cmd 0xF8804300 ctl 0xF8804338 bmdma 0x0 irq 17

full dmesg:

libata version 2.00 loaded.
ata_piix 0000:00:1f.1: version 2.00ac5
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1f.1 to 64
ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
scsi0 : ata_piix
in ich_pata_cbl_detect
controller has 80c support
... and we defaulted to 40-pin
ata1.00: ATAPI, max UDMA/33
ata1.01: ATAPI, max MWDMA0, CDB intr
ata1.00: configured for UDMA/33
ata1.01: configured for PIO3
  Vendor: HL-DT-ST  Model: DVDRAM GSA-4120B  Rev: A111
  Type:   CD-ROM                             ANSI SCSI revision: 05
  Vendor: IOMEGA    Model: ZIP 250           Rev: 51.G
  Type:   Direct-Access                      ANSI SCSI revision: 05
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
scsi1 : ata_piix
in ich_pata_cbl_detect
controller has 80c support
... and we found an 80-pin cable
ata2.00: ATA-6, max UDMA/100, 234441648 sectors: LBA48
ata2.00: ata2: dev 0 multi count 16
ata2.01: ATAPI, max UDMA/33
ata2.00: configured for UDMA/100
ata2.01: configured for UDMA/33
  Vendor: ATA       Model: ST3120022A        Rev: 3.06
  Type:   Direct-Access                      ANSI SCSI revision: 05
  Vendor: TOSHIBA   Model: DVD-ROM SD-M1712  Rev: 1004
  Type:   CD-ROM                             ANSI SCSI revision: 05
ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata3: SATA max UDMA/133 cmd 0xC000 ctl 0xC402 bmdma 0xD000 irq 16
ata4: SATA max UDMA/133 cmd 0xC800 ctl 0xCC02 bmdma 0xD008 irq 16
scsi2 : ata_piix
ata3: ENTER, pcs=0x13 base=0
ata3: LEAVE, pcs=0x13 present_mask=0x1
ata3.00: ATA-6, max UDMA/133, 390721968 sectors: LBA48
ata3.00: ata3: dev 0 multi count 16
ata3.00: configured for UDMA/133
scsi3 : ata_piix
ata4: ENTER, pcs=0x13 base=2
ata4: LEAVE, pcs=0x11 present_mask=0x0
ata4: SATA port has no device.
ATA: abnormal status 0x7F on port 0xC807
  Vendor: ATA       Model: ST3200822AS       Rev: 3.01
  Type:   Direct-Access                      ANSI SCSI revision: 05
sata_promise 0000:03:04.0: version 1.04
ACPI: PCI Interrupt 0000:03:04.0[A] -> GSI 23 (level, low) -> IRQ 17
sata_promise PATA port found
ata5: SATA max UDMA/133 cmd 0xF8804200 ctl 0xF8804238 bmdma 0x0 irq 17
ata6: SATA max UDMA/133 cmd 0xF8804280 ctl 0xF88042B8 bmdma 0x0 irq 17
ata7: PATA max UDMA/133 cmd 0xF8804300 ctl 0xF8804338 bmdma 0x0 irq 17
scsi4 : sata_promise
ata5: SATA link down (SStatus 0 SControl 300)
scsi5 : sata_promise
ata6: SATA link down (SStatus 0 SControl 0)
scsi6 : sata_promise
ATA: abnormal status 0x7F on port 0xF880431C
ata7: disabling port
sd 0:0:1:0: Attached scsi removable disk sda
SCSI device sdb: 234441648 512-byte hdwr sectors (120034 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
SCSI device sdb: 234441648 512-byte hdwr sectors (120034 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
 sdb: sdb1
sd 1:0:0:0: Attached scsi disk sdb
SCSI device sdc: 390721968 512-byte hdwr sectors (200050 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: drive cache: write back
SCSI device sdc: 390721968 512-byte hdwr sectors (200050 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: drive cache: write back
 sdc: sdc1 sdc2 sdc3
sd 2:0:0:0: Attached scsi disk sdc
sr0: scsi3-mmc drive: 40x/40x 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
sr1: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
sr 1:0:1:0: Attached scsi CD-ROM sr1
...

--
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free
Mandriva Linux release 2007.0 (Cooker) for i586
Linux 2.6.17-jam03 (gcc 4.1.1 20060518 (prerelease)) #3 SMP PREEMPT Mon

Re: 2.6.18-rc1-mm1

[Brice Goglin]

Andrew Morton wrote:
>   All these functions return error codes, and we're not checking them.  We
>   should.  So there's a patch which marks all these things as __must_check,
>   which causes around 1,500 new warnings.
>   


Hi Andrew,

The following patch fixes such a warning in myri10ge.

thanks,
Brice


Check pci_enable_device() return value in myri10ge_resume().

Signed-off-by: Brice Goglin <brice@myri.com>
---
 drivers/net/myri10ge/myri10ge.c |   13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

Index: linux-mm/drivers/net/myri10ge/myri10ge.c
===================================================================
--- linux-mm.orig/drivers/net/myri10ge/myri10ge.c	2006-07-09 10:36:22.000000000 -0400
+++ linux-mm/drivers/net/myri10ge/myri10ge.c	2006-07-09 11:05:23.000000000 -0400
@@ -2412,14 +2412,20 @@
 		return -EIO;
 	}
 	myri10ge_restore_state(mgp);
-	pci_enable_device(pdev);
+
+	status = pci_enable_device(pdev);
+	if (status < 0) {
+		dev_err(&pdev->dev, "failed to enable device\n");
+		return -EIO;
+	}
+
 	pci_set_master(pdev);
 
 	status = request_irq(pdev->irq, myri10ge_intr, IRQF_SHARED,
 			     netdev->name, mgp);
 	if (status != 0) {
 		dev_err(&pdev->dev, "failed to allocate IRQ\n");
-		goto abort_with_msi;
+		goto abort_with_enabled;
 	}
 
 	myri10ge_reset(mgp);
@@ -2438,7 +2444,8 @@
 
 	return 0;
 
-abort_with_msi:
+abort_with_enabled:
+	pci_disable_device(pdev);
 	return -EIO;
 
 }

Re: 2.6.18-rc1-mm1

[Randy.Dunlap]

[-- Attachment #1: Type: text/plain, Size: 3563 bytes --]

On Sun, 09 Jul 2006 23:22:14 +1200 Reuben Farrelly wrote:

> On 9/07/2006 9:11 p.m., Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> > 

> 2. Onto some more minor warnings:
> 
> ACPI: bus type pci registered
> PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
> PCI: Not using MMCONFIG.
> PCI: Using configuration type 1
> ACPI: Interpreter enabled
> 
> Is there any way to verify that there really is a BIOS bug there?  If it is, is 
> there anyone within Intel or are there any known contacts who can push and poke 
> to get this looked at/fixed?  (It's a new Intel board, I'd hope they could get 
> it right..).
> 
> Plus we're not using MMCONFIG - even though I have it enabled.
> 
> Based on previous postings to lkml, I believe Randy Dunlap may have one of these 
> boards too - Randy are you seeing this and the next bunch of warnings I am seeing?

I don't get far enough to see that.

Has this already been addressed?


[   82.315906] ----------- [cut here ] --------- [please bite here ] ---------
[   82.329754] Kernel BUG at mm/page_alloc.c:252
[   82.338412] invalid opcode: 0000 [1] SMP 
[   82.346396] last sysfs file: 
[   82.352287] CPU 0 
[   82.356283] Modules linked in:
[   82.362356] Pid: 1, comm: swapper Not tainted 2.6.18-rc1-mm1 #6
[   82.374126] RIP: 0010:[<ffffffff80156911>]  [<ffffffff80156911>] get_page_from_free7
[   82.392140] RSP: 0000:ffff81007f61fdc8  EFLAGS: 00010246
[   82.402700] RAX: 0000000000000000 RBX: ffffffff80456c80 RCX: 0000000000001000
[   82.416892] RDX: 0000000000000000 RSI: ffff8100010cf900 RDI: ffffffff80456c00
[   82.431083] RBP: ffff81007f61fe28 R08: 0000000000000000 R09: 0000000000000000
[   82.445275] R10: 000000000007b9b7 R11: 0000000000000000 R12: ffff8100010cf900
[   82.459467] R13: 0000000000000246 R14: 0000000000000001 R15: ffffffff80456c00
[   82.473659] FS:  0000000000000000(0000) GS:ffffffff8054c000(0000) knlGS:000000000000
[   82.489754] CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
[   82.501179] CR2: 0000000000000000 CR3: 0000000000101000 CR4: 00000000000006e0
[   82.515372] Process swapper (pid: 1, threadinfo ffff81007f61e000, task ffff81000332)
[   82.531465] Stack:  00000044033d6700 0002802000000000 ffffffff80457b00 0000000100006
[   82.547431]  0000000000000001 0000000000000000 ffff81007f61fe88 ffffffff80457b00
[   82.562177]  0000000000008020 ffffffffff600000 ffffffff80457b00 ffff81000332c760
[   82.576568] Call Trace:
[   82.581779]  [<ffffffff80156a2c>] __alloc_pages+0x6e/0x2c2
[   82.592688]  [<ffffffff801f5b38>] kobject_add+0xd9/0x19a
[   82.603250]  [<ffffffff80156cb3>] get_zeroed_page+0x33/0x5e
[   82.614331]  [<ffffffff8057621d>] spp_getpage+0x17/0x62
[   82.624719]  [<ffffffff80576aa4>] __set_fixmap+0x126/0x202
[   82.635627]  [<ffffffff8056dd67>] vsyscall_init+0x89/0x9b
[   82.646361]  [<ffffffff80107163>] init+0x13b/0x2b4
[   82.655884]  [<ffffffff803b4773>] _spin_unlock_irq+0x9/0xc
[   82.666792]  [<ffffffff801253ec>] schedule_tail+0x43/0xbe
[   82.677527]  [<ffffffff8010a00a>] child_rip+0x8/0x12
[   82.687397]  [<ffffffff80107028>] init+0x0/0x2b4
[   82.696574]  [<ffffffff8010a002>] child_rip+0x0/0x12
[   82.706442] 
[   82.709392] 
[   82.709393] Code: 0f 0b 68 d4 84 3e 80 c2 fc 00 eb ec 48 89 df 48 2b 3d 71 9e 
[   82.728279] RIP  [<ffffffff80156911>] get_page_from_freelist+0x2da/0x387
[   82.741617]  RSP <ffff81007f61fdc8>
[   82.748545]  <0>Kernel panic - not syncing: Attempted to kill init!


Pentium-D 3 GHz, 2 GB RAM, SATA.
config attached.

---
~Randy

[-- Attachment #2: config-2618-rc1mm1 --]
[-- Type: application/octet-stream, Size: 42194 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.18-rc1-mm1
# Sun Jul  9 21:19:23 2006
#
CONFIG_X86_64=y
CONFIG_64BIT=y
CONFIG_X86=y
CONFIG_ZONE_DMA32=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=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_DMI=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

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

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SWAP_PREFETCH=y
CONFIG_SYSVIPC=y
# CONFIG_IPC_NS is not set
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
CONFIG_SYSCTL=y
# CONFIG_UTS_NS is not set
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_CPUSETS is not set
CONFIG_RELAY=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_KLIBC_ERRLIST=y
CONFIG_KLIBC_ZLIB=y
CONFIG_UID16=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_EMBEDDED=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# 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_RT_MUTEXES=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_SLAB=y
CONFIG_VM_EVENT_COUNTERS=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set

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

#
# Block layer
#
CONFIG_LBD=y
# CONFIG_BLK_DEV_IO_TRACE is not set
CONFIG_LSF=y

#
# 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 is not set
CONFIG_MPSC=y
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_L1_CACHE_BYTES=128
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_INTERNODE_CACHE_BYTES=128
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_X86_HT=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_MTRR=y
CONFIG_SMP=y
# CONFIG_SCHED_SMT is not set
CONFIG_SCHED_MC=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y
# CONFIG_NUMA is not set
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
# CONFIG_ADAPTIVE_READAHEAD is not set
CONFIG_NR_CPUS=8
# CONFIG_HOTPLUG_CPU is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_HPET_TIMER=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 is not set
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_SECCOMP is not set
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
# 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

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

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
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=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y

#
# CPUFreq processor drivers
#
# CONFIG_X86_POWERNOW_K8 is not set
CONFIG_X86_SPEEDSTEP_CENTRINO=y
CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
CONFIG_X86_ACPI_CPUFREQ=y

#
# shared options
#
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
# CONFIG_X86_P4_CLOCKMOD is not set
# CONFIG_X86_SPEEDSTEP_LIB is not set

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCIEPORTBUS=y
CONFIG_PCI_MSI=y
# CONFIG_PCI_DEBUG is not set

#
# PCCARD (PCMCIA/CardBus) support
#
CONFIG_PCCARD=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=m
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y

#
# PC-card bridges
#
CONFIG_YENTA=m
# CONFIG_YENTA_O2 is not set
# CONFIG_YENTA_RICOH is not set
# CONFIG_YENTA_TI is not set
# CONFIG_YENTA_TOSHIBA is not set
CONFIG_PD6729=m
CONFIG_I82092=m
CONFIG_PCCARD_NONSTATIC=m

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=y
CONFIG_COMPAT=y
CONFIG_SYSVIPC_COMPAT=y

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
# CONFIG_NETDEBUG is not set
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_MULTIPLE_TABLES is not set
# CONFIG_IP_ROUTE_MULTIPATH is not set
# CONFIG_IP_ROUTE_VERBOSE is not set
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=y
CONFIG_NET_IPGRE=y
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
CONFIG_INET_TUNNEL=y
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_BIC=y
# CONFIG_IPV6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set

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

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set

#
# TIPC Configuration (EXPERIMENTAL)
#
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

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

#
# Device Drivers
#

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

#
# Connector - unified userspace <-> kernelspace linker
#
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y

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

#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_PC_PCMCIA is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_AX88796 is not set
CONFIG_PARPORT_1284=y

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

#
# Protocols
#
CONFIG_PNPACPI=y

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

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_IDE_MAX_HWIFS=4
CONFIG_BLK_DEV_IDE=y

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

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

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

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

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

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=m
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_SCSI_SAS_DOMAIN_ATTRS=m
CONFIG_SCSI_SAS_DOMAIN_DEBUG=y

#
# SCSI low-level drivers
#
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=32
CONFIG_AIC7XXX_RESET_DELAY_MS=5000
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
# CONFIG_SCSI_AIC7XXX_OLD is not set
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=15000
# CONFIG_AIC79XX_ENABLE_RD_STRM is not set
CONFIG_AIC79XX_DEBUG_ENABLE=y
CONFIG_AIC79XX_DEBUG_MASK=0
CONFIG_AIC79XX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC94XX=m
CONFIG_AIC94XX_DEBUG=y
CONFIG_SCSI_ARCMSR=m
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
CONFIG_SCSI_SATA=y
CONFIG_SCSI_SATA_AHCI=y
# CONFIG_SCSI_PATA_ALI is not set
# CONFIG_SCSI_PATA_AMD is not set
# CONFIG_SCSI_PATA_ARTOP is not set
# CONFIG_SCSI_PATA_ATIIXP is not set
# CONFIG_SCSI_PATA_CMD64X is not set
# CONFIG_SCSI_PATA_CS5520 is not set
# CONFIG_SCSI_PATA_CS5530 is not set
# CONFIG_SCSI_PATA_CYPRESS is not set
# CONFIG_SCSI_PATA_EFAR is not set
# CONFIG_SCSI_ATA_GENERIC is not set
# CONFIG_SCSI_PATA_HPT366 is not set
# CONFIG_SCSI_PATA_HPT37X is not set
# CONFIG_SCSI_PATA_HPT3X2N is not set
# CONFIG_SCSI_PATA_HPT3X3 is not set
# CONFIG_SCSI_PATA_IT8172 is not set
# CONFIG_SCSI_PATA_IT821X is not set
# CONFIG_SCSI_ATA_JMICRON is not set
# CONFIG_SCSI_PATA_LEGACY is not set
# CONFIG_SCSI_SATA_SVW is not set
# CONFIG_SCSI_PATA_TRIFLEX is not set
# CONFIG_SCSI_PATA_MPIIX is not set
# CONFIG_SCSI_PATA_OLDPIIX is not set
# CONFIG_SCSI_ATA_PIIX is not set
# CONFIG_SCSI_SATA_MV is not set
# CONFIG_SCSI_PATA_NETCELL is not set
# CONFIG_SCSI_PATA_NS87410 is not set
# CONFIG_SCSI_SATA_NV is not set
# CONFIG_SCSI_PATA_OPTI is not set
# CONFIG_SCSI_PATA_OPTIDMA is not set
# CONFIG_SCSI_PATA_PCMCIA is not set
# CONFIG_SCSI_PATA_PDC_OLD is not set
# CONFIG_SCSI_PATA_QDI is not set
# CONFIG_SCSI_PATA_RADISYS is not set
# CONFIG_SCSI_PATA_RZ1000 is not set
# CONFIG_SCSI_PATA_SC1200 is not set
# CONFIG_SCSI_PATA_SERVERWORKS is not set
# CONFIG_SCSI_PDC_ADMA is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_SATA_QSTOR is not set
# CONFIG_SCSI_PATA_PDC2027X is not set
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_SX4 is not set
# CONFIG_SCSI_SATA_SIL is not set
# CONFIG_SCSI_SATA_SIL24 is not set
# CONFIG_SCSI_PATA_SIL680 is not set
# CONFIG_SCSI_PATA_SIS is not set
# CONFIG_SCSI_SATA_SIS is not set
# CONFIG_SCSI_SATA_ULI is not set
# CONFIG_SCSI_PATA_VIA is not set
# CONFIG_SCSI_SATA_VIA is not set
# CONFIG_SCSI_SATA_VITESSE is not set
CONFIG_SCSI_SATA_INTEL_COMBINED=y
# CONFIG_SCSI_PATA_WINBOND is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
CONFIG_SCSI_PPA=m
CONFIG_SCSI_IMM=m
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
CONFIG_SCSI_DEBUG=m
# CONFIG_SCSI_SRP is not set

#
# PCMCIA SCSI adapter support
#
# CONFIG_PCMCIA_FDOMAIN is not set
# CONFIG_PCMCIA_QLOGIC is not set
# CONFIG_PCMCIA_SYM53C500 is not set

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

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

#
# IEEE 1394 (FireWire) support
#
CONFIG_IEEE1394=m

#
# Subsystem Options
#
CONFIG_IEEE1394_VERBOSEDEBUG=y
CONFIG_IEEE1394_OUI_DB=y
CONFIG_IEEE1394_EXTRA_CONFIG_ROMS=y
CONFIG_IEEE1394_CONFIG_ROM_IP1394=y
# CONFIG_IEEE1394_EXPORT_FULL_API is not set

#
# Device Drivers
#
CONFIG_IEEE1394_PCILYNX=m
CONFIG_IEEE1394_OHCI1394=m

#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
CONFIG_IEEE1394_ETH1394=m
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m

#
# I2O device support
#
# CONFIG_I2O is not set

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

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# PHY device support
#
CONFIG_PHYLIB=y

#
# MII PHY device drivers
#
# CONFIG_MARVELL_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_SMSC_PHY is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=y
# CONFIG_E1000_NAPI is not set
CONFIG_E1000_DISABLE_PACKET_SPLIT=y
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2 is not set
# CONFIG_QLA3XXX is not set

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

#
# Token Ring devices
#
# CONFIG_TR is not set

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

#
# PCMCIA network device support
#
# CONFIG_NET_PCMCIA is not set

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

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_EFFECTS is not set

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

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

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

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

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
# CONFIG_SERIAL_8250_PCI is not set
# CONFIG_SERIAL_8250_PNP is not set
# CONFIG_SERIAL_8250_CS is not set
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

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

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set

#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=y
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_ALIM1535_WDT is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_SC520_WDT is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_IBMASR is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_I6300ESB_WDT is not set
# CONFIG_I8XX_TCO is not set
# CONFIG_ITCO_WDT is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SBC8360_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_W83627HF_WDT is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_W83977F_WDT is not set
# CONFIG_MACHZ_WDT is not set
# CONFIG_SBC_EPX_C3_WATCHDOG is not set

#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set

#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
# CONFIG_HW_RANDOM is not set
CONFIG_NVRAM=y
# CONFIG_RTC is not set
CONFIG_GEN_RTC=y
CONFIG_GEN_RTC_X=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# Ftape, the floppy tape device driver
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_VIA is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set

#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_CARDMAN_4000 is not set
# CONFIG_CARDMAN_4040 is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
CONFIG_HPET_RTC_IRQ=y
CONFIG_HPET_MMAP=y
CONFIG_HANGCHECK_TIMER=y

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

#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y

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

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

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

#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set

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

#
# Hardware Monitoring support
#
CONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_FSCPOS is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
CONFIG_VIDEO_DEV=y
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_VIDEO_V4L2=y

#
# Video Capture Adapters
#

#
# Video Capture Adapters
#
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_BWQCAM is not set
# CONFIG_VIDEO_CQCAM is not set
# CONFIG_VIDEO_W9966 is not set
CONFIG_VIDEO_CPIA=m
# CONFIG_VIDEO_CPIA_PP is not set
CONFIG_VIDEO_CPIA_USB=m
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set

#
# Encoders and Decoders
#
# CONFIG_VIDEO_MSP3400 is not set
# CONFIG_VIDEO_CS53L32A is not set
# CONFIG_VIDEO_TLV320AIC23B is not set
# CONFIG_VIDEO_WM8775 is not set
# CONFIG_VIDEO_WM8739 is not set
# CONFIG_VIDEO_CX2341X is not set
# CONFIG_VIDEO_CX25840 is not set
# CONFIG_VIDEO_SAA711X is not set
# CONFIG_VIDEO_SAA7127 is not set
# CONFIG_VIDEO_UPD64031A is not set
# CONFIG_VIDEO_UPD64083 is not set

#
# V4L USB devices
#
# CONFIG_VIDEO_PVRUSB2 is not set
# CONFIG_VIDEO_EM28XX is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_QUICKCAM_MESSENGER is not set
# CONFIG_USB_ET61X251 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
# CONFIG_USB_W9968CF is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_ZC0301 is not set
# CONFIG_USB_PWC is not set

#
# Radio Adapters
#
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set

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

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

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_VIDEO_SELECT=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
# CONFIG_LOGO is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Sound
#
CONFIG_SOUND=y

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_SEQUENCER=y
# CONFIG_SND_SEQ_DUMMY is not set
# CONFIG_SND_MIXER_OSS is not set
# CONFIG_SND_PCM_OSS is not set
# CONFIG_SND_SEQUENCER_OSS is not set
# CONFIG_SND_DYNAMIC_MINORS is not set
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# PCI devices
#
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
CONFIG_SND_HDA_INTEL=y
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set

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

#
# PCMCIA devices
#
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_PDAUDIOCF is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
CONFIG_USB_DEBUG=y

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

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set

#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m

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

#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
CONFIG_USB_LIBUSUAL=y

#
# USB Input Devices
#
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
CONFIG_USB_HIDDEV=y
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_ACECAD is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_TOUCHSCREEN is not set
# CONFIG_USB_YEALINK is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set
# CONFIG_USB_ATI_REMOTE2 is not set
# CONFIG_USB_KEYSPAN_REMOTE is not set
# CONFIG_USB_APPLETOUCH is not set

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

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

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_CONSOLE=y
CONFIG_USB_SERIAL_GENERIC=y
# CONFIG_USB_SERIAL_AIRPRIME is not set
# CONFIG_USB_SERIAL_ANYDATA is not set
# CONFIG_USB_SERIAL_ARK3116 is not set
CONFIG_USB_SERIAL_BELKIN=y
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_CP2101 is not set
# CONFIG_USB_SERIAL_CYPRESS_M8 is not set
# CONFIG_USB_SERIAL_EMPEG is not set
# CONFIG_USB_SERIAL_FTDI_SIO is not set
# CONFIG_USB_SERIAL_FUNSOFT is not set
# CONFIG_USB_SERIAL_VISOR is not set
# CONFIG_USB_SERIAL_IPAQ is not set
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
# CONFIG_USB_SERIAL_GARMIN is not set
# CONFIG_USB_SERIAL_IPW is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_MOS7720 is not set
# CONFIG_USB_SERIAL_NAVMAN is not set
# CONFIG_USB_SERIAL_PL2303 is not set
# CONFIG_USB_SERIAL_HP4X is not set
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_SIERRAWIRELESS is not set
# CONFIG_USB_SERIAL_TI is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OPTION is not set
# CONFIG_USB_SERIAL_OMNINET is not set

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

#
# USB DSL modem support
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

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

#
# LED devices
#
# CONFIG_NEW_LEDS is not set

#
# LED drivers
#

#
# LED Triggers
#

#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set
# CONFIG_IPATH_CORE is not set

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

#
# Real Time Clock
#
# CONFIG_RTC_CLASS is not set

#
# DMA Engine support
#
# CONFIG_DMA_ENGINE is not set

#
# DMA Clients
#

#
# DMA Devices
#

#
# Firmware Drivers
#
CONFIG_EDD=y
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_REISER4_FS is not set
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
# CONFIG_REISERFS_FS_XATTR is not set
CONFIG_JFS_FS=m
# CONFIG_JFS_POSIX_ACL is not set
# CONFIG_JFS_SECURITY is not set
# CONFIG_JFS_DEBUG is not set
CONFIG_JFS_STATISTICS=y
# CONFIG_FS_POSIX_ACL is not set
CONFIG_XFS_FS=m
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_SECURITY is not set
# CONFIG_XFS_POSIX_ACL is not set
# CONFIG_XFS_RT is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
CONFIG_MINIX_FS=m
CONFIG_ROMFS_FS=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set

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

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

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_RAMFS=y
CONFIG_CONFIGFS_FS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_CRAMFS=y
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
CONFIG_SYSV_FS=m
CONFIG_UFS_FS=m
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_UFS_DEBUG is not set

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

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set

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

#
# Distributed Lock Manager
#

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

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_UNUSED_SYMBOLS=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_LOG_BUF_SHIFT=16
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHEDSTATS is not set
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_SLAB_LEAK=y
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
# CONFIG_DEBUG_RWSEMS is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_PAGE_OWNER is not set
CONFIG_DEBUG_FS=y
CONFIG_DEBUG_VM=y
CONFIG_FRAME_POINTER=y
# CONFIG_UNWIND_INFO is not set
# CONFIG_PROFILE_LIKELY is not set
# CONFIG_FORCED_INLINING is not set
# CONFIG_DEBUG_SYNCHRO_TEST is not set
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_DEBUG_RODATA=y
# CONFIG_IOMMU_DEBUG is not set
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_STACK_USAGE=y

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Hardware crypto devices
#

#
# Library routines
#
CONFIG_CRC_CCITT=y
CONFIG_CRC16=y
CONFIG_CRC32=y
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
CONFIG_PLIST=y

Re: 2.6.18-rc1-mm1

[Andrew Morton]

On Sun, 9 Jul 2006 21:56:49 -0700
"Randy.Dunlap" <rdunlap@xenotime.net> wrote:

> Has this already been addressed?
> 
> 
> [   82.315906] ----------- [cut here ] --------- [please bite here ] ---------
> [   82.329754] Kernel BUG at mm/page_alloc.c:252

CONFIG_DEBUG_VM=n should make that go away.

Re: 2.6.18-rc1-mm1

[Randy.Dunlap]

On Sun, 09 Jul 2006 23:22:14 +1200 Reuben Farrelly wrote:

> 2. Onto some more minor warnings:
> 
> ACPI: bus type pci registered
> PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
> PCI: Not using MMCONFIG.
> PCI: Using configuration type 1

Yes, I have all of those.

> ACPI: Interpreter enabled
> 
> Is there any way to verify that there really is a BIOS bug there?  If it is, is 
> there anyone within Intel or are there any known contacts who can push and poke 
> to get this looked at/fixed?  (It's a new Intel board, I'd hope they could get 
> it right..).
> 
> Plus we're not using MMCONFIG - even though I have it enabled.
> 
> Based on previous postings to lkml, I believe Randy Dunlap may have one of these 
> boards too - Randy are you seeing this and the next bunch of warnings I am seeing?

Yes, but Len says that they (*/namespace/*) will be going away.

---
~Randy

Re: 2.6.18-rc1-mm1

[Mauro Carvalho Chehab]

Em Dom, 2006-07-09 às 13:24 -0700, Andrew Morton escreveu:
> On Sun, 9 Jul 2006 19:28:07 +0200
> Dominik Karall <dominik.karall@gmx.net> wrote:
> 
> > On Sunday, 9. July 2006 11:11, Andrew Morton wrote:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1
> > >8-rc1/2.6.18-rc1-mm1/
> > 
> > There are stil problems with initializing the bt878 chip. I'm not sure 
> > if it is the same bug, but I had problems with all -mm versions since 
> > 2.6.17-mm1
> > Screenshot: 
> > http://stud4.tuwien.ac.at/~e0227135/kernel/060709_190546.jpg
> > 
> 
> Right - this is one of those mysterious crashes deep in sysfs from calling
> code which basically hasn't changed.  Mauro and Greg are vacationing or
> otherwise offline so not much is likely to happen short-term.
I should be returning back from vacations by the end of this week. 

About the errors you are suffering, image is not clean enough to allow
reading the log. There were some changes on -mm that may affect people
with third-party drivers (like, for example, some webcam drivers). This
is due to a change at video_device structure, used to register video
devices. Several third-party drivers just have a copy of videodev.h. So,
those drivers compile using the old struct definition, but tries to
register the device by calling a function that is expecting the newer
struct. Maybe this is your case.
> 
> Is 2.6.18-rc1 OK?
Cheers, 
Mauro.

Re: 2.6.18-rc1-mm1

[Ingo Molnar]

* Andrew Morton <akpm@osdl.org> wrote:

> > This looks like a problem with cpufreq.
> > 
> > =======================================================
> > [ INFO: possible circular locking dependency detected ]
> > -------------------------------------------------------
> > cpuspeed/1426 is trying to acquire lock:
> >  (&inode->i_data.tree_lock){.+..}, at: [<c0151dc7>] find_get_page+0x12/0x70
> > 
> > but task is already holding lock:
> >  (&mm->mmap_sem){----}, at: [<c0116cab>] do_page_fault+0x10d/0x4ea
> > 
> > which lock already depends on the new lock.
> > 
> 
> rofl.  You broke lockdep.

ouch! the lock identifications look quite funny :-| Never saw that 
happen before, i'm wondering what's going on. Michal, did this happen 
straight during bootup? Or did you remove/recompile/reinsert any modules 
perhaps?

> Well.  I guess it's barely conceivable that you earlier took an oops 
> while holding tree_lock, so lockdep decided that mmap_sem nests inside 
> tree_lock.

Arjan is preparing a patch to turn off lockdep when we crash. Although i 
dont see any trace of an earlier oops in the dmesg.

	Ingo

RE: 2.6.18-rc1-mm1

[Arjan van de Ven]

On Sun, 2006-07-09 at 13:47 -0400, Brown, Len wrote:
> >> 2. Onto some more minor warnings:
> >> 
> >> ACPI: bus type pci registered
> >> PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
> >> PCI: Not using MMCONFIG.
> >> PCI: Using configuration type 1
> >> ACPI: Interpreter enabled
> >> 
> >> Is there any way to verify that there really is a BIOS bug 
> >there?  If it is, is there anyone within Intel or are there any
> >known contacts 
> >who can push and poke > to get this looked at/fixed?
> >(It's a new Intel board, I'd hope they could get it right..).
> 
> Arjan should probably comment on that one.

I could.. but please next time if you want to CC me use an email address
I actually read ;)

Greg has a patch to relax this check, and Rajesh has a further patch to
relax it more. However, to a large degree we cannot relax it too much
without breaking the reason this check is there: detect a buggy MCFG
table and not crash and burn later on, but rather just not use it.

Re: 2.6.18-rc1-mm1

[Arjan van de Ven]

> > - If a piece of kernel code is dealing with per-cpu data and cannot run
> >   atomically then it should have its own cpu hotplug handlers anyway.  It
> >   is up to that code (ie: cpufreq) to provide its own locking against its
> >   own CPU hotplug callback.
> 
> This still does not solve this cpufreq problem where it is trying to
> take the same lock twice down the same call path.

that is broken beyond discussing anyway... "we don't know our locking
rules so we do recursive mutexes" is ... NOT a good reason.

Re: 2.6.18-rc1-mm1

[Michal Piotrowski]

Hi Ingo,

On 10/07/06, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Andrew Morton <akpm@osdl.org> wrote:
>
> > > This looks like a problem with cpufreq.
> > >
> > > =======================================================
> > > [ INFO: possible circular locking dependency detected ]
> > > -------------------------------------------------------
> > > cpuspeed/1426 is trying to acquire lock:
> > >  (&inode->i_data.tree_lock){.+..}, at: [<c0151dc7>] find_get_page+0x12/0x70
> > >
> > > but task is already holding lock:
> > >  (&mm->mmap_sem){----}, at: [<c0116cab>] do_page_fault+0x10d/0x4ea
> > >
> > > which lock already depends on the new lock.
> > >
> >
> > rofl.  You broke lockdep.
>
> ouch! the lock identifications look quite funny :-| Never saw that
> happen before,

:)

> i'm wondering what's going on. Michal, did this happen
> straight during bootup? Or did you remove/recompile/reinsert any modules
> perhaps?

It's happening while /etc/init.d/cpuspeed execution.

I forgot about "make O=/dir/ clean". When new -mm is out I always
remove kernel directory and create new one.

>
> > Well.  I guess it's barely conceivable that you earlier took an oops
> > while holding tree_lock, so lockdep decided that mmap_sem nests inside
> > tree_lock.
>
> Arjan is preparing a patch to turn off lockdep when we crash. Although i
> dont see any trace of an earlier oops in the dmesg.
>
>         Ingo
>

Regards,
Michal

-- 
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)

Re: 2.6.18-rc1-mm1

[Ingo Molnar]

* Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:

> >> rofl.  You broke lockdep.
> >
> >ouch! the lock identifications look quite funny :-| Never saw that
> >happen before,
> 
> :)
> 
> >i'm wondering what's going on. Michal, did this happen
> >straight during bootup? Or did you remove/recompile/reinsert any modules
> >perhaps?
> 
> It's happening while /etc/init.d/cpuspeed execution.
> 
> I forgot about "make O=/dir/ clean". When new -mm is out I always 
> remove kernel directory and create new one.

ah, ok. So i'll put this under the 'unclean-build artifact' section, 
i.e. not a lockdep bug for now, it seems. Please re-report if it ever 
occurs again with a clean kernel build.

	Ingo

Re: 2.6.18-rc1-mm1

[Michal Piotrowski]

On 10/07/06, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
>
> > >> rofl.  You broke lockdep.
> > >
> > >ouch! the lock identifications look quite funny :-| Never saw that
> > >happen before,
> >
> > :)
> >
> > >i'm wondering what's going on. Michal, did this happen
> > >straight during bootup? Or did you remove/recompile/reinsert any modules
> > >perhaps?
> >
> > It's happening while /etc/init.d/cpuspeed execution.
> >
> > I forgot about "make O=/dir/ clean". When new -mm is out I always
> > remove kernel directory and create new one.
>
> ah, ok. So i'll put this under the 'unclean-build artifact' section,
> i.e. not a lockdep bug for now, it seems. Please re-report if it ever
> occurs again with a clean kernel build.

Unfortunately "make O=/dir clean" doesn't help. I'll disable lockdep,
and see what happens.

>
>         Ingo
>

Regards,
Michal

-- 
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)

Re: 2.6.18-rc1-mm1

[Alan Cox]

Ar Llu, 2006-07-10 am 02:33 +0200, ysgrifennodd J.A. Magallón:
> builtin, host detenction seems to go in PCI order but... promise detects
> first the SATA drives. I'm trying to get a way to predict what switchng
> from IDE to libata will do on my boxes, but...

PCI order. Some controllers put the PATA ports before the SATA ones,
some controllers the reverse, some even mix them up according to BIOS
setup. Generally they are doing this so the user can land their
preferred disk type as BIOS disk 0x80 (C:) for booting.

Alan

Re: 2.6.18-rc1-mm1

[Michal Piotrowski]

On 10/07/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> On 10/07/06, Ingo Molnar <mingo@elte.hu> wrote:
> > ah, ok. So i'll put this under the 'unclean-build artifact' section,
> > i.e. not a lockdep bug for now, it seems. Please re-report if it ever
> > occurs again with a clean kernel build.
>
> Unfortunately "make O=/dir clean" doesn't help. I'll disable lockdep,
> and see what happens.
>

When I set DEBUG_LOCK_ALLOC=n and CONFIG_PROVE_LOCKING=n everything is ok.
It maybe a gcc 4.2 bug.

Regards,
Michal

-- 
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)

Re: 2.6.18-rc1-mm1

[Ingo Molnar]

* Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:

> On 10/07/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> >On 10/07/06, Ingo Molnar <mingo@elte.hu> wrote:
> >> ah, ok. So i'll put this under the 'unclean-build artifact' section,
> >> i.e. not a lockdep bug for now, it seems. Please re-report if it ever
> >> occurs again with a clean kernel build.
> >
> >Unfortunately "make O=/dir clean" doesn't help. I'll disable lockdep,
> >and see what happens.
> >
>
> When I set DEBUG_LOCK_ALLOC=n and CONFIG_PROVE_LOCKING=n everything is 
> ok. It maybe a gcc 4.2 bug.

well ... if you disable lockdep then you wont get lockdep messages - 
that's normal. Or did i miss what the bug is about?

	Ingo

Re: 2.6.18-rc1-mm1

[Michal Piotrowski]

On 10/07/06, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
>
> > On 10/07/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> > >On 10/07/06, Ingo Molnar <mingo@elte.hu> wrote:
> > >> ah, ok. So i'll put this under the 'unclean-build artifact' section,
> > >> i.e. not a lockdep bug for now, it seems. Please re-report if it ever
> > >> occurs again with a clean kernel build.
> > >
> > >Unfortunately "make O=/dir clean" doesn't help. I'll disable lockdep,
> > >and see what happens.
> > >
> >
> > When I set DEBUG_LOCK_ALLOC=n and CONFIG_PROVE_LOCKING=n everything is
> > ok. It maybe a gcc 4.2 bug.

It's not gcc 4.2 bug.

>
> well ... if you disable lockdep then you wont get lockdep messages -
> that's normal.

I'm just checking ;).

> Or did i miss what the bug is about?
>
>         Ingo
>

Regards,
Michal

-- 
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)

Re: 2.6.18-rc1-mm1

[Rafael J. Wysocki]

On Sunday 09 July 2006 11:11, Andrew Morton wrote:
> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/

The sk98lin driver stopped working on my box.  It loads, but doesn't seem to
do anything else.  Fortunately skge forks just fine, so it's not a big deal.

]--snip--[ 
> - There are some improvements to the swsusp disk IO handling.  You should
>   find that the suspend-time writeout and resume-time readin speeds are
>   approximately doubled.

The swsusp IO changes work very well for me, and that's a huge improvement.
Thanks a lot for it.

Rafael

Re: 2.6.18-rc1-mm1

[J.A. Magallón]

On Sun, 9 Jul 2006 02:11:06 -0700, Andrew Morton <akpm@osdl.org> wrote:

> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> 

Hi...

I'm using this plus Jeff Garzik's alloc/free cleanup patch for libata.
In my home box it works fine wrt CD-ROMs (ata-piix).

My RAID box at work has this hardware:

00:00.0 Host bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266] (rev 01)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
00:07.0 RAID bus controller: Promise Technology, Inc. PDC20319 (FastTrak S150 TX4) (rev 02)
00:08.0 RAID bus controller: Promise Technology, Inc. PDC20319 (FastTrak S150 TX4) (rev 02)
00:0a.0 SCSI storage controller: Adaptec AIC-7892B U160/m (rev 02)
00:0b.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
00:0c.0 RAID bus controller: Promise Technology, Inc. PDC20267 (FastTrak100/Ultra100) (rev 02)
00:0d.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1b)
00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1b)
00:11.4 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1b)
01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev a4)

ie, a VIA PATA on-board (with just a DVD-RW), a Promise 20267 also on board
(anything hung there), an Adaptec 7892 for the system disk and 2 Promise
SATA cards for a RAID5 (software md).

I have aic driver builtin, and sata_promise and pata_via as modules.
In previous kernels I used the IDE drivers for the CD, but I have tried to
switch to libata. I looked here:

http://zeniv.linux.org.uk/~alan/IDE/STATUS.txt

and read:

VIA:
	Added IRQ masking support
	Completed

Now the problems. pata_via takes an eon to load:

nada:~# time modprobe pata_via0.00user 0.01system 2:13.17elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k0inputs+0outputs (0major+208minor)pagefaults 0swaps
and it does not detect the burner, as ata_piix did in my home box:

Jul 10 16:15:28 nada kernel: pata_via 0000:00:11.1: version 0.1.13
Jul 10 16:15:28 nada kernel: PCI: VIA IRQ fixup for 0000:00:11.1, from 255 to 0
Jul 10 16:15:28 nada kernel: ata9: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0xD800 irq 14
Jul 10 16:15:28 nada kernel: scsi9 : pata_via
Jul 10 16:15:29 nada kernel: ata9.00: ATAPI, max UDMA/33
Jul 10 16:15:59 nada kernel: ata9.00: qc timeout (cmd 0xa1)
Jul 10 16:15:59 nada kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Jul 10 16:15:59 nada kernel: ata9.00: revalidation failed (errno=-5)
Jul 10 16:15:59 nada kernel: ata9.00: limiting speed to UDMA/25
Jul 10 16:15:59 nada kernel: ata9: failed to recover some devices, retrying in 5 secs
Jul 10 16:16:34 nada kernel: ata9.00: qc timeout (cmd 0xa1)
Jul 10 16:16:34 nada kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Jul 10 16:16:34 nada kernel: ata9.00: revalidation failed (errno=-5)
Jul 10 16:16:34 nada kernel: ata9: failed to recover some devices, retrying in 5 secs
Jul 10 16:17:10 nada kernel: ata9.00: qc timeout (cmd 0xa1)
Jul 10 16:17:10 nada kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Jul 10 16:17:10 nada kernel: ata9.00: revalidation failed (errno=-5)
Jul 10 16:17:10 nada kernel: ata9.00: disabled
Jul 10 16:17:10 nada kernel: ata10: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xD808 irq 15
Jul 10 16:17:10 nada kernel: scsi10 : pata_via
Jul 10 16:17:17 nada kernel: ata10: port is slow to respond, please be patient
Jul 10 16:17:40 nada kernel: ata10: port failed to respond (30 secs)
Jul 10 16:17:40 nada kernel: ata10: SRST failed (status 0xFF)
Jul 10 16:17:40 nada kernel: ata10: SRST failed (err_mask=0x100)
Jul 10 16:17:40 nada kernel: ata10: softreset failed, retrying in 5 secs
Jul 10 16:17:45 nada kernel: ata10: SRST failed (status 0xFF)
Jul 10 16:17:45 nada kernel: ata10: SRST failed (err_mask=0x100)
Jul 10 16:17:45 nada kernel: ata10: softreset failed, retrying in 5 secs
Jul 10 16:17:51 nada kernel: ata10: SRST failed (status 0xFF)
Jul 10 16:17:51 nada kernel: ata10: SRST failed (err_mask=0x100)
Jul 10 16:17:51 nada kernel: ata10: reset failed, giving up

(note: the previous ata channels are:
libata version 2.00 loaded.
sata_promise 0000:00:07.0: version 1.04
ACPI: PCI Interrupt 0000:00:07.0[A] -> GSI 17 (level, low) -> IRQ 17
ata1: SATA max UDMA/133 cmd 0xF8818200 ctl 0xF8818238 bmdma 0x0 irq 17
ata2: SATA max UDMA/133 cmd 0xF8818280 ctl 0xF88182B8 bmdma 0x0 irq 17
ata3: SATA max UDMA/133 cmd 0xF8818300 ctl 0xF8818338 bmdma 0x0 irq 17
ata4: SATA max UDMA/133 cmd 0xF8818380 ctl 0xF88183B8 bmdma 0x0 irq 17
ata5: SATA max UDMA/133 cmd 0xF881A200 ctl 0xF881A238 bmdma 0x0 irq 18
ata6: SATA max UDMA/133 cmd 0xF881A280 ctl 0xF881A2B8 bmdma 0x0 irq 18
ata7: SATA max UDMA/133 cmd 0xF881A300 ctl 0xF881A338 bmdma 0x0 irq 18
ata8: SATA max UDMA/133 cmd 0xF881A380 ctl 0xF881A3B8 bmdma 0x0 irq 18
)

nada:/var/log# lsscsi -H
[0]    aic7xxx     
[1]    sata_promise
[2]    sata_promise
[3]    sata_promise
[4]    sata_promise
[5]    sata_promise
[6]    sata_promise
[7]    sata_promise
[8]    sata_promise
[9]    pata_via    
[10]    pata_via    

nada:/var/log# lsscsi
[0:0:0:0]    disk    IBM      DDYS-T18350N     S96H  /dev/sda
[1:0:0:0]    disk    ATA      Maxtor 7Y250M0   YAR5  /dev/sdb
[2:0:0:0]    disk    ATA      Maxtor 7Y250M0   YAR5  /dev/sdc
[3:0:0:0]    disk    ATA      Maxtor 7Y250M0   YAR5  /dev/sdd
[4:0:0:0]    disk    ATA      Maxtor 7Y250M0   YAR5  /dev/sde
[5:0:0:0]    disk    ATA      Maxtor 7Y250M0   YAR5  /dev/sdf
[6:0:0:0]    disk    ATA      Maxtor 7Y250M0   YAR5  /dev/sdg
[7:0:0:0]    disk    ATA      Maxtor 7Y250M0   YAR5  /dev/sdh

In my home box I get:

werewolf:~> lsscsi -H
[0]    ata_piix    
[1]    ata_piix    
[2]    ata_piix    
[3]    ata_piix    
[4]    sata_promise
[5]    sata_promise
[6]    sata_promise
[7]    usb-storage 

werewolf:~> lsscsi
[0:0:0:0]    cd/dvd  HL-DT-ST DVDRAM GSA-4120B A111  /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

Any ideas ? There is a CDRW in ata9...

--
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free
Mandriva Linux release 2007.0 (Cooker) for i586
Linux 2.6.17-jam03 (gcc 4.1.1 20060518 (prerelease)) #3 SMP PREEMPT Mon

Re: 2.6.18-rc1-mm1

[Dominik Karall]

On Monday, 10. July 2006 09:11, Mauro Carvalho Chehab wrote:
> Em Dom, 2006-07-09 às 13:24 -0700, Andrew Morton escreveu:
> > On Sun, 9 Jul 2006 19:28:07 +0200
> > Right - this is one of those mysterious crashes deep in sysfs
> > from calling code which basically hasn't changed.  Mauro and Greg
> > are vacationing or otherwise offline so not much is likely to
> > happen short-term.
>
> I should be returning back from vacations by the end of this week.
>
> About the errors you are suffering, image is not clean enough to
> allow reading the log. There were some changes on -mm that may
> affect people with third-party drivers (like, for example, some
> webcam drivers). This is due to a change at video_device structure,
> used to register video devices. Several third-party drivers just
> have a copy of videodev.h. So, those drivers compile using the old
> struct definition, but tries to register the device by calling a
> function that is expecting the newer struct. Maybe this is your
> case.

hi,
thx for your reply, but I'm not using any binary drivers, neither 
other external driver sources.

> > Is 2.6.18-rc1 OK?
I will check it tomorrow and let you know if it works!

cheers,
dominik

Re: 2.6.18-rc1-mm1

[Chuck Ebbert]

On Sun, 9 Jul 2006 02:11:06 -0700, Andrew morton wrote:

> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/

Warnings(?) during build:

/home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/ipconfig' given more than once in the same rule.
/home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/nfsmount' given more than once in the same rule.
/home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/run-init' given more than once in the same rule.
/home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/fstype' given more than once in the same rule.

-- 
Chuck

Re: 2.6.18-rc1-mm1

[Randy.Dunlap]

On Mon, 10 Jul 2006 22:58:50 -0400 Chuck Ebbert wrote:

> On Sun, 9 Jul 2006 02:11:06 -0700, Andrew morton wrote:
> 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> 
> Warnings(?) during build:
> 
> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/ipconfig' given more than once in the same rule.
> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/nfsmount' given more than once in the same rule.
> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/run-init' given more than once in the same rule.
> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/fstype' given more than once in the same rule.

Yes, and these:

fs/ecryptfs/main.c:327: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
fs/ecryptfs/crypto.c:1599: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
fs/ecryptfs/crypto.c:1621: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
fs/ecryptfs/crypto.c:1628: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
fs/ecryptfs/crypto.c:1635: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
fs/ecryptfs/crypto.c:1642: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
fs/ecryptfs/crypto.c:1649: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
fs/ecryptfs/crypto.c:1656: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
drivers/acpi/executer/exmutex.c:268: warning: format ‘%X’ expects type ‘unsigned int’, but argument 4 has type ‘struct task_struct *’
drivers/acpi/executer/exmutex.c:268: warning: format ‘%X’ expects type ‘unsigned int’, but argument 6 has type ‘struct task_struct *’


I'll get to these sometime this week if noone else does.
(not the klibc warnings)

---
~Randy

Re: 2.6.18-rc1-mm1

[H. Peter Anvin]

Chuck Ebbert wrote:
> On Sun, 9 Jul 2006 02:11:06 -0700, Andrew morton wrote:
> 
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> 
> Warnings(?) during build:
> 
> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/ipconfig' given more than once in the same rule.
> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/nfsmount' given more than once in the same rule.
> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/run-init' given more than once in the same rule.
> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/fstype' given more than once in the same rule.
> 

Already resolved.

	-hpa

Re: 2.6.18-rc1-mm1

[Cedric Le Goater]

Randy.Dunlap wrote:
> On Mon, 10 Jul 2006 22:58:50 -0400 Chuck Ebbert wrote:
> 
>> On Sun, 9 Jul 2006 02:11:06 -0700, Andrew morton wrote:
>>
>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
>> Warnings(?) during build:
>>
>> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/ipconfig' given more than once in the same rule.
>> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/nfsmount' given more than once in the same rule.
>> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/run-init' given more than once in the same rule.
>> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/fstype' given more than once in the same rule.
> 
> Yes, and these:
> 
> fs/ecryptfs/main.c:327: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
> fs/ecryptfs/crypto.c:1599: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
> fs/ecryptfs/crypto.c:1621: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
> fs/ecryptfs/crypto.c:1628: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
> fs/ecryptfs/crypto.c:1635: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
> fs/ecryptfs/crypto.c:1642: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
> fs/ecryptfs/crypto.c:1649: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
> fs/ecryptfs/crypto.c:1656: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
> drivers/acpi/executer/exmutex.c:268: warning: format ‘%X’ expects type ‘unsigned int’, but argument 4 has type ‘struct task_struct *’
> drivers/acpi/executer/exmutex.c:268: warning: format ‘%X’ expects type ‘unsigned int’, but argument 6 has type ‘struct task_struct *’

and these :

arch/i386/kernel/io_apic.c:2431: warning: 'vector' might be used
uninitialized in this function
drivers/scsi/libata-core.c:3055: warning: unused variable `i'
drivers/acpi/utilities/utmutex.c:260: warning: cast from pointer to integer
of different size
arch/s390/hypfs/inode.c:432: warning: initialization from incompatible
pointer type
arch/s390/hypfs/inode.c:433: warning: initialization from incompatible
pointer type

C.

---
 drivers/scsi/libata-core.c |    1 -
 1 file changed, 1 deletion(-)

Index: 2.6.18-rc1-mm1/drivers/scsi/libata-core.c
===================================================================
--- 2.6.18-rc1-mm1.orig/drivers/scsi/libata-core.c
+++ 2.6.18-rc1-mm1/drivers/scsi/libata-core.c
@@ -3052,7 +3052,6 @@ static void ata_dev_xfermask(struct ata_
        struct ata_port *ap = dev->ap;
        struct ata_host_set *hs = ap->host_set;
        unsigned long xfer_mask;
-       int i;

        /* Controller modes available */
        xfer_mask = ata_pack_xfermask(ap->pio_mask,

Re: 2.6.18-rc1-mm1

[Greg KH]

On Sun, Jul 09, 2006 at 08:35:38PM +0200, Andi Kleen wrote:
> On Sun, Jul 09, 2006 at 05:22:52AM -0700, Andrew Morton wrote:
> > > ACPI: bus type pci registered
> > > PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
> > > PCI: Not using MMCONFIG.
> > > PCI: Using configuration type 1
> > > ACPI: Interpreter enabled
> > > 
> > > Is there any way to verify that there really is a BIOS bug there?  If it is, is 
> > > there anyone within Intel or are there any known contacts who can push and poke 
> > > to get this looked at/fixed?  (It's a new Intel board, I'd hope they could get 
> > > it right..).
> > > 
> > > Plus we're not using MMCONFIG - even though I have it enabled.
> > 
> > Andi stuff.
> 
> Greg has patches to relax the checking a bit. 
> 
> I don't know when he intends to merge them.

I think they are all merged into 2.6.18-rc1, as I do't see any MMCONFIG
patches in my tree right now, nor in my queue.

thanks,

greg k-h

Re: 2.6.18-rc1-mm1

[Greg KH]

On Mon, Jul 10, 2006 at 10:48:49AM +0200, Arjan van de Ven wrote:
> On Sun, 2006-07-09 at 13:47 -0400, Brown, Len wrote:
> > >> 2. Onto some more minor warnings:
> > >> 
> > >> ACPI: bus type pci registered
> > >> PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
> > >> PCI: Not using MMCONFIG.
> > >> PCI: Using configuration type 1
> > >> ACPI: Interpreter enabled
> > >> 
> > >> Is there any way to verify that there really is a BIOS bug 
> > >there?  If it is, is there anyone within Intel or are there any
> > >known contacts 
> > >who can push and poke > to get this looked at/fixed?
> > >(It's a new Intel board, I'd hope they could get it right..).
> > 
> > Arjan should probably comment on that one.
> 
> I could.. but please next time if you want to CC me use an email address
> I actually read ;)
> 
> Greg has a patch to relax this check, and Rajesh has a further patch to
> relax it more.

Hm, no, my patch should already be in 2.6.18-rc1, I don't have any
pending MMCONFIG patches in my queue or tree.

So if you think I'm missing one, please resend it to me.

thanks,

greg k-h

Re: 2.6.18-rc1-mm1

[Chuck Ebbert]

In-Reply-To: <20060711230055.GL18838@kroah.com>

On Tue, 11 Jul 2006 16:00:55 -0700, Greg KH wrote:

> > > >> PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
> > > >> PCI: Not using MMCONFIG.
> > > >> PCI: Using configuration type 1
> > > >> ACPI: Interpreter enabled
> > > >> 
> > > >> Is there any way to verify that there really is a BIOS bug 
> > > >there?  If it is, is there anyone within Intel or are there any
> > > >known contacts 
> > > >who can push and poke > to get this looked at/fixed?
> > > >(It's a new Intel board, I'd hope they could get it right..).
> > > 
> > > Arjan should probably comment on that one.
> > 
> > I could.. but please next time if you want to CC me use an email address
> > I actually read ;)
> > 
> > Greg has a patch to relax this check, and Rajesh has a further patch to
> > relax it more.
> 
> Hm, no, my patch should already be in 2.6.18-rc1, I don't have any
> pending MMCONFIG patches in my queue or tree.
> 
> So if you think I'm missing one, please resend it to me.

What happened to:

        http://lkml.org/2006/6/26/640

        [patch 0/2] PCI: improve extended config space verification - take #2

I tested the first round of this patchset on i386 and it worked for me (TM).

-- 
Chuck
 "You can't read a newspaper if you can't read."  --George W. Bush

Re: 2.6.18-rc1-mm1

[Badari Pulavarty]

Cedric Le Goater wrote:
> Randy.Dunlap wrote:
>   
>> On Mon, 10 Jul 2006 22:58:50 -0400 Chuck Ebbert wrote:
>>
>>     
>>> On Sun, 9 Jul 2006 02:11:06 -0700, Andrew morton wrote:
>>>
>>>       
>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
>>>>         
>>> Warnings(?) during build:
>>>
>>> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/ipconfig' given more than once in the same rule.
>>> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/nfsmount' given more than once in the same rule.
>>> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/run-init' given more than once in the same rule.
>>> /home/me/linux/2.6.18-rc1-mm1-64/scripts/Kbuild.klibc:315: target `usr/kinit/fstype' given more than once in the same rule.
>>>       
>> Yes, and these:
>>
>> fs/ecryptfs/main.c:327: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
>> fs/ecryptfs/crypto.c:1599: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
>> fs/ecryptfs/crypto.c:1621: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
>> fs/ecryptfs/crypto.c:1628: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
>> fs/ecryptfs/crypto.c:1635: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
>> fs/ecryptfs/crypto.c:1642: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
>> fs/ecryptfs/crypto.c:1649: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
>> fs/ecryptfs/crypto.c:1656: warning: format ‘%d’ expects type ‘int’, but argument 2 has type ‘size_t’
>> drivers/acpi/executer/exmutex.c:268: warning: format ‘%X’ expects type ‘unsigned int’, but argument 4 has type ‘struct task_struct *’
>> drivers/acpi/executer/exmutex.c:268: warning: format ‘%X’ expects type ‘unsigned int’, but argument 6 has type ‘struct task_struct *’
>>     
> ...

> arch/s390/hypfs/inode.c:432: warning: initialization from incompatible
> pointer type
> arch/s390/hypfs/inode.c:433: warning: initialization from incompatible
> pointer type
>
>   

Yuck. Its due to my vfs ops clean up changes.
Michael, do you have time to fix it up or do you want me to ?

Thanks,
Badari

Re: 2.6.18-rc1-mm1

[Reuben Farrelly]

On 9/07/2006 9:11 p.m., Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc1/2.6.18-rc1-mm1/
> 
> - We're getting a relatively large number of crash reports coming out of the
>   core sysfs/kobject/driver/bus code, and they're all really hard to diagnose.

Just noticed this in the logs from yesterday.  It didn't cause the machine to go 
down so I didn't notice it at the time:

Jul 12 13:48:47 tornado smartd[1853]: Device: /dev/sdb, SMART Usage Attribute: 
195 Hardware_ECC_Recovered changed from 64 to 63
Jul 12 13:51:24 tornado kernel: rpmq[11203]: segfault at 00002b3f41eb445f rip 
00002b3f44aa7108 rsp 00007fff667aef80 error 4
Jul 12 13:51:24 tornado kernel: general protection fault: 0000 [1] SMP
Jul 12 13:51:24 tornado kernel: last sysfs file: /block/fd0/dev
Jul 12 13:51:24 tornado kernel: CPU 1
Jul 12 13:51:24 tornado kernel: Modules linked in: hidp rfcomm l2cap bluetooth 
ipv6 ip_gre iptable_filter iptable_nat ip_nat ip_conntrack nfnetlink iptable_man
gle ip_tables binfmt_misc i2c_i801 iTCO_wdt serio_raw
Jul 12 13:51:24 tornado kernel: Pid: 5067, comm: nagios Not tainted 
2.6.18-rc1-mm1 #1
Jul 12 13:51:24 tornado kernel: RIP: 0010:[<ffffffff8028f3a1>] 
[<ffffffff8028f3a1>] notifier_call_chain+0x1e/0x45
Jul 12 13:51:24 tornado kernel: RSP: 0018:ffff810012979d58  EFLAGS: 00010202
Jul 12 13:51:24 tornado kernel: RAX: 6b6b6b6b6b6b6b6b RBX: ffff810014ae5040 RCX: 
6b6b6b6b6b6b6b6b
Jul 12 13:51:24 tornado kernel: RDX: ffff810014ae5040 RSI: 0000000000000001 RDI: 
ffff810008034f88
Jul 12 13:51:24 tornado kernel: RBP: ffff810012979d78 R08: 0000000000000000 R09: 
0000000000000001
Jul 12 13:51:24 tornado kernel: R10: 0000000000000001 R11: 0000000000000001 R12: 
ffff810014ae5040
Jul 12 13:51:24 tornado kernel: R13: 0000000000000001 R14: ffff810014ae5040 R15: 
ffff810014ae5040
Jul 12 13:51:24 tornado kernel: FS:  00002b8b610af6f0(0000) 
GS:ffff81003f6eb430(0000) knlGS:0000000000000000
Jul 12 13:51:24 tornado kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Jul 12 13:51:24 tornado kernel: CR2: 0000000000678ae8 CR3: 000000000c86e000 CR4: 
00000000000006e0
Jul 12 13:51:24 tornado kernel: Process nagios (pid: 5067, threadinfo 
ffff810012978000, task ffff810020fce080)
Jul 12 13:51:24 tornado kernel: Stack:  ffff810012979d88 ffff810014ae5040 
0000000000000001 0000000001200011
Jul 12 13:51:24 tornado kernel:  ffff810012979d88 ffffffff8028f3f6 
ffff810012979da8 ffffffff8028f76f
Jul 12 13:51:24 tornado kernel:  ffff81002375e000 ffff810020fce080 
ffff810012979e78 ffffffff8021ea6c
Jul 12 13:51:24 tornado kernel: Call Trace:
Jul 12 13:51:24 tornado kernel:  [<ffffffff8028f3f6>] 
raw_notifier_call_chain+0x9/0x13
Jul 12 13:51:24 tornado kernel:  [<ffffffff8028f76f>] notify_watchers+0x64/0x69
Jul 12 13:51:24 tornado kernel:  [<ffffffff8021ea6c>] copy_process+0x4dc/0x15c0
Jul 12 13:51:24 tornado kernel:  [<ffffffff80231837>] do_fork+0xf7/0x208
Jul 12 13:51:24 tornado kernel:  [<ffffffff80268ad0>] sys_clone+0x23/0x25
Jul 12 13:51:24 tornado kernel:  [<ffffffff8025f4c7>] ptregscall_common+0x67/0xac
Jul 12 13:51:24 tornado kernel:  [<ffffffff8025f182>] system_call+0x7e/0x83
Jul 12 13:51:24 tornado kernel:  [<00002b8b60df8aa9>]
Jul 12 13:51:24 tornado kernel:
Jul 12 13:51:24 tornado kernel: Code: 48 8b 59 08 4c 89 e2 4c 89 ee 48 89 cf ff 
11 66 85 c0 78 08
Jul 12 13:51:24 tornado kernel: RIP  [<ffffffff8028f3a1>] 
notifier_call_chain+0x1e/0x45
Jul 12 13:51:24 tornado kernel:  RSP <ffff810012979d58>
Jul 12 14:18:46 tornado smartd[1853]: Device: /dev/sdb, SMART Prefailure 
Attribute: 1 Raw_Read_Error_Rate changed from 63 to 64

I'm not sure who the relevant people are to look at this in more detail.

Reuben

Re: 2.6.18-rc1-mm1

[Etienne Lorrain]

 Error while compiling:
  CC      kernel/uid16.o
  CC      kernel/kallsyms.o
kernel/kallsyms.c: In function ‘get_ksymbol_mod’:
kernel/kallsyms.c:279: error: too many arguments to function ‘module_get_kallsym’
make[1]: *** [kernel/kallsyms.o] Error 1
make: *** [kernel] Error 2

  With a .config containing:
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set

 Fixed by removing CONFIG_KALLSYMS.
 Using my usual monolitic kernel (no modules) if it has a relation at all.

 Cheers,
 Etienne.


	

	
		
___________________________________________________________________________ 
Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire.
http://fr.mail.yahoo.com

Re: 2.6.18-rc1-mm1

[Dominik Karall]

On Monday, 10. July 2006 09:11, Mauro Carvalho Chehab wrote:
> Em Dom, 2006-07-09 às 13:24 -0700, Andrew Morton escreveu:
> > On Sun, 9 Jul 2006 19:28:07 +0200
> >
> > Dominik Karall <dominik.karall@gmx.net> wrote:
> > > On Sunday, 9. July 2006 11:11, Andrew Morton wrote:
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6
> > > >/2.6.1 8-rc1/2.6.18-rc1-mm1/
> > >
> > > There are stil problems with initializing the bt878 chip. I'm
> > > not sure if it is the same bug, but I had problems with all -mm
> > > versions since 2.6.17-mm1
> > > Screenshot:
> > > http://stud4.tuwien.ac.at/~e0227135/kernel/060709_190546.jpg
> >
> > Right - this is one of those mysterious crashes deep in sysfs
> > from calling code which basically hasn't changed.  Mauro and Greg
> > are vacationing or otherwise offline so not much is likely to
> > happen short-term.
>
> I should be returning back from vacations by the end of this week.
>
> About the errors you are suffering, image is not clean enough to
> allow reading the log. There were some changes on -mm that may
> affect people with third-party drivers (like, for example, some
> webcam drivers). This is due to a change at video_device structure,
> used to register video devices. Several third-party drivers just
> have a copy of videodev.h. So, those drivers compile using the old
> struct definition, but tries to register the device by calling a
> function that is expecting the newer struct. Maybe this is your
> case.
>
> > Is 2.6.18-rc1 OK?

It's the same bug with 2.6.18-rc1.

cheers,
dominik