ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc3/2.6.19-rc3-mm1/
- ia64 doesn't compile due to improvements in acpi. I already fixed a huge
string of build errors due to this and it's someone else's turn.
- For some reason Greg has resurrected the patches which detect whether
you're using old versions of udev and if so, punish you for it.
If weird stuff happens, try upgrading udev.
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 [email protected]
- If you hit a bug in -mm and it is not obvious which patch caused it, it is
most valuable if you can perform a bisection search to identify which patch
introduced the bug. Instructions for this process are at
http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt
But beware that this process takes some time (around ten rebuilds and
reboots), so consider reporting the bug first and if we cannot immediately
identify the faulty patch, then perform the bisection search.
- When reporting bugs, please try to Cc: the relevant maintainer and mailing
list on any email.
- When reporting bugs in this kernel via email, please also rewrite the
email Subject: in some manner to reflect the nature of the bug. Some
developers filter by Subject: when looking for messages to read.
- Semi-daily snapshots of the -mm lineup are uploaded to
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/ and are announced on
the mm-commits list.
Changes since 2.6.19-rc2-mm2:
origin.patch
git-acpi.patch
git-alsa.patch
git-cpufreq.patch
git-drm.patch
git-dvb.patch
git-ia64.patch
git-ieee1394.patch
git-infiniband.patch
git-input-fixup.patch
git-libata-all.patch
git-mips.patch
git-mmc.patch
git-mtd.patch
git-netdev-all.patch
git-net.patch
git-ioat.patch
git-ocfs2.patch
git-pcmcia.patch
git-powerpc.patch
git-r8169.patch
git-pciseg.patch
git-s390.patch
git-scsi-misc.patch
git-scsi-target.patch
git-sas.patch
git-qla3xxx.patch
git-watchdog.patch
git-cryptodev.patch
git-gccbug.patch
git trees
-e100-fix-reboot-f-with-netconsole-enabled.patch
-direct-io-sync-and-invalidate-file-region-when-falling-back-to-buffered-write.patch
-ecryptfs-use-special_file.patch
-export-clear_queue_congested-and-set_queue_congested.patch
-separate-bdi-congestion-functions-from-queue-congestion-functions.patch
-make-linux-personalityh-userspace-proof.patch
-uml-mode_tt-is-bust.patch
-fix-typo-in-memory-barrier-docs.patch
-uml-remove-some-leftover-ppc-code.patch
-uml-split-memory-allocation-prototypes-out-of-userh.patch
-uml-code-convention-cleanup-of-a-file.patch
-uml-reenable-compilation-of-enable_timer-disabled-by-mistake.patch
-uml-use-defconfig_list-to-avoid-reading-hosts-config.patch
-uml-cleanup-run_helper-api-to-fix-a-leak.patch
-uml-kconfig-silence-warning.patch
-uml-mmapper-remove-just-added-but-wrong-const-attribute.patch
-kconfig-serial-typos.patch
-fix-acpi-processor-native-c-states-using-mwait.patch
-genirq-clean-up-irq-flow-type-naming-fix.patch
-readjust-comments-of-task_timeslice-for-kernel-doc.patch
-acpimemory-hotplug-change-log-level-of-a-message-of-acpi_memhotplug-to-kern_debug.patch
-acpimemory-hotplug-remove-strange-add_memory-fail-message.patch
-oom-killer-meets-userspace-headers.patch
-irq-updates-make-eata_pio-compile.patch
-fix-warnings-for-warn_on-if-config_bug-is-disabled.patch
-cad_pid-sysctl-with-proc_fs=n.patch
-fs-kconfig-move-generic_acl-fix-acl-call-errors.patch
-autofs3-make-sure-all-dentries-refs-are-released-before-calling-kill_anon_super.patch
-nfsv4-fix-thinko-in-fs-nfs-superc.patch
-nfs-fix-oops-in-nfs_cancel_commit_list.patch
-nfs-fix-error-handling-in-nfs_direct_write_result.patch
-nfs4-initialize-cl_ipaddr.patch
-nfs-fix-nfsv4-callback-regression.patch
-nfs-deal-with-failure-of-invalidate_inode_pages2.patch
-nfs-fix-minor-bug-in-new-nfs-symlink-code.patch
-nfs-__nfs_revalidate_inode-can-use-inode-before.patch
-nfs-remove-unused-check-in-nfs4_open_revalidate.patch
-sunrpc-fix-race-in-in-kernel-rpc-portmapper-client.patch
-sunrpc-fix-a-typo.patch
-bug-nfsd-nfs4xdrc-misuse-of-err_ptr.patch
-fix-svc_procfunc-declaration.patch
-lockd-endianness-annotations.patch
-xdr-annotations-nfsv2.patch
-xdr-annotations-nfsv3.patch
-xdr-annotations-nfsv4.patch
-xdr-annotations-nfs-readdir-entries.patch
-fs-nfs-callback-passes-error-values-big-endian.patch
-xdr-annotations-fs-nfs-callback.patch
-nfs-verifier-is-network-endian.patch
-xdr-annotations-mount_clnt.patch
-nfs_common-endianness-annotations.patch
-nfsd-nfserrno-endianness-annotations.patch
-nfsfh-simple-endianness-annotations.patch
-xdr-annotations-nfsd_dispatch.patch
-xdr-annotations-nfsv2-server.patch
-xdr-annotations-nfsv3-server.patch
-xdr-annotations-nfsv4-server.patch
-nfsd-vfsc-endianness-annotations.patch
-nfsd-nfs4-code-returns-error-values-in-net-endian.patch
-nfsd-nfsv23-trivial-endianness-annotations-for-error-values.patch
-nfsd-nfsv4-errno-endianness-annotations.patch
-xdr-annotations-nfsd-callback.patch
-nfsd-misc-endianness-annotations.patch
-nfsd-nfs_replay_me.patch
-fix-potential-interrupts-during-alternative-patching-was.patch
-highest_possible_node_id-linkage-fix.patch
-drivers-isdn-ioremap-balanced-with-iounmap.patch
-doc-fixing-cpu-hotplug-documentation.patch
-mmd-cache-aliasing-issue-in-cow_user_page.patch
-ipmi-fix-return-codes-in-failure-case.patch
-firmware-dcdbas-add-size-check-in-smi_data_write.patch
-mm-more-comment-lockorder.patch
-ext3-fix-j_asserttransaction-t_updates-0-in-journal_stop.patch
-kernel-nsproxyc-use-kmemdup.patch
-knfsd-fix-race-that-can-disable-nfs-server.patch
-one-more-arm-irq-fix.patch
-uml-fix-prototypes.patch
-uml-make-execvp-safe-for-our-usage.patch
-tty-signal-tty-locking.patch
-char-correct-pci_get_device-changes.patch
-drivers-ide-pci-genericc-re-add-the-__setupall-generic-ide.patch
-md-fix-calculation-of-degraded-for-multipath-and-raid10.patch
-md-add-another-compat_ioctl-for-md.patch
-md-endian-annotation-for-v1-superblock-access.patch
-md-endian-annotations-for-the-bitmap-superblock.patch
-clocksource-acpi_pm-add-another-greylist-chipset.patch
-pci-declare-pci_get_device_reverse.patch
-rpaphp-build-fix.patch
-vfs-make-d_materialise_unique-enforce-directory.patch
-nfs-cache-invalidation-fixup.patch
-mm-clean-up-pagecache-allocation.patch
-vmscan-fix-temp_priority-race.patch
-vmscan-fix-temp_priority-race-comments.patch
-vmscan-fix-temp_priority-in-__zone-reclaim.patch
-acpi-add-removable-drive-bay-support.patch
-fix-up-a-multitude-of-acpi-compiler-warnings-on-x86_64.patch
-i386-acpi-build-fix.patch
-add-support-for-the-generic-backlight-device-to-the-ibm-acpi-driver.patch
-add-support-for-the-generic-backlight-device-to-the-ibm-acpi-driver-fix.patch
-add-support-for-the-generic-backlight-device-to-the-ibm-acpi-driver-fix-2.patch
-add-support-for-the-generic-backlight-device-to-the-asus-acpi-driver.patch
-add-support-for-the-generic-backlight-device-to-the-asus-acpi-driver-fix.patch
-add-support-for-the-generic-backlight-device-to-the-toshiba-acpi-driver.patch
-add-support-for-the-generic-backlight-device-to-the-toshiba-acpi-driver-fix.patch
-acpi-cpufreq-remove-dead-code.patch
-cpufreq-handle-sysfs-errors.patch
-speedstep-centrino-remove-dead-code.patch
-driver-core-fixes-make_class_name-retval-check.patch
-driver-core-fixes-check-for-return-value-of-sysfs_create_link.patch
-driver-core-dont-ignore-bus_attach_device-retval.patch
-drm-fix-error-returns-sysfs-error-handling.patch
-drm-fix-return-code-in-error-case.patch
-gregkh-i2c-w1-ioremap-balanced-with-iounmap.patch
-remove-unnecessary-check-in-drivers-video-intelfb-intelfbhwc.patch
-intel-fb-switch-to-pci_get-api.patch
-ata-must-depend-on-block.patch
-ahci-readability-tweak.patch
-libata-sff-allow-for-wacky-systems.patch
-pata_marvell-marvell-6101-6145-pata-driver.patch
-pata_marvell-switch-to-pci_iomap-as-jeff-asked.patch
-pata_marvell-switch-to-pci_iomap-as-jeff-asked-fix.patch
-libata-use-correct-map_db-values-for-ich8.patch
-drivers-mmcmisc-handle-pci-errors-on-resume.patch
-mmc-when-rescanning-cards-check-existing-cards-after-mmc_setup.patch
-mtd-maps-add-parameter-to-amd76xrom-to-override-rom-window-size-if-set-incorrectly-by-bios.patch
-mtd-chips-support-for-sst-49lf040b-flash-chip.patch
-mtd-maps-support-for-bios-flash-chips-on-intel-esb2-southbridge.patch
-jffs2-use-rb_first-and-rb_last-cleanup.patch
-mtd-fix-comment-typo-devic.patch
-esb2rom-use-hotplug-safe-interfaces.patch
-ibmveth-fix-index-increment-calculation.patch
-e1000-reset-all-functions-after-a-pci-error.patch
-revert-mv643xx-add-pci-device-table-for-auto-module-loading.patch
-ipv6-dccp-fix-memory-leak-in-dccp_v6_do_rcv.patch
-drivers-atm-no-need-to-return-void.patch
-atm-firestream-handle-thrown-error.patch
-wan-pc300-handle-propagate-minor-errors.patch
-net-atm-handle-sysfs-errors.patch
-nicstar-fix-a-bogus-casting-warning.patch
-pcmcia-update-alloc_io_space-for-conflict-checking-for-multifunction-pc-card-for-linux-kernel-26154.patch
-pcmcia-ds-must_check-fixes.patch
-config_pm=n-slim-drivers-pcmcia.patch
-i82092-wire-up-errors-from-pci_register_driver.patch
-drivers-net-pcmcia-xirc2ps_csc-remove-unused-label.patch
-pcmcia-au1000_generic-fix.patch
-ioremap-balanced-with-iounmap-for-drivers-pcmcia.patch
-export-soc_common_drv_pcmcia_remove-to-allow-modular-pcmcia.patch
-perle-multimodem-card-pci-ras-detection.patch
-pcmcia-handle-sysfs-pci-errors.patch
-reset-pci-device-state-to-unknown-state-for-resume.patch
-x86-64-mmconfig-missing-printk-levels.patch
-remove-quirk_via_abnormal_poweroff.patch
-drivers-scsi-aic7xxx-possible-cleanups.patch
-make-drivers-scsi-aic7xxx-aic79xx_coreahd_set_tags-static.patch
-megaraid-check-for-firmware-version.patch
-ioremap-balanced-with-iounmap-drivers-scsi-zalonc.patch
-ioremap-balanced-with-iounmap-drivers-scsi-sun3_scsic.patch
-ioremap-balanced-with-iounmap-drivers-scsi-sun3_scsi_vmec.patch
-ioremap-balanced-with-iounmap-drivers-scsi-seagatec.patch
-ioremap-balanced-with-iounmap-drivers-scsi-qlogicptic.patch
-ioremap-balanced-with-iounmap-drivers-scsi-nsp32c.patch
-ioremap-balanced-with-iounmap-drivers-scsi-ncr53c8xxc.patch
-ioremap-balanced-with-iounmap-drivers-scsi-fdomainc.patch
-ioremap-balanced-with-iounmap-drivers-scsi-amiga7xxc.patch
-scsi-convert-ninja-driver-to-struct-scsi_cmnd.patch
-fc4-conversion-to-struct-scsi_cmnd-in-fc4.patch
-dereference-in-drivers-scsi-lpfc-lpfc_ctc.patch
-scsi-scsi_cmnd-convertion-in-sun3-driver.patch
-scsi-scsi_cmnd-conversion-in-qlogicfas408-driver.patch
-scsi-scsi_cmnd-convertion-in-psi240i-driver.patch
-aic94xx-sata-tag-mask-not-set-correctly.patch
-maintain-module-parameter-name-consistency-with-qla2xxx-qla4xxx.patch
-scsi_libc-use-build_bug_on.patch
-scsi-minor-bug-fixes-and-cleanups.patch
-scsi-qla2xxx-handle-sysfs-errors.patch
-switch-fdomain-to-the-pci_get-api.patch
-drivers-scsi-handcrafted-min-max-macro-removal.patch
-drivers-scsi-handcrafted-min-max-macro-removal-fix.patch
-fix-pxa2xx-udc-compilation-error.patch
-hid-core-big-endian-fix-fix.patch
-x86_64-mm-sparse-memory-srat.patch
-x86_64-mm-io-apic-vector-typo.patch
-x86_64-mm-overlapping-program-headers-in-physical-addr-space-fix.patch
-x86_64-mm-fix-.cfi_signal_frame-copy-n-paste-error.patch
-x86_64-mm-fix-for-arch-x86_64-pci-makefile-cflags.patch
-x86_64-mm-e820-page-align.patch
-x86_64-mm-accumulate-args.patch
-x86_64-mm-unwinder-speedup.patch
-x86_64-mm-x86_64-add-nx-mask-for-pte-entry.patch
-x86_64-mm-i386-fake-return-address.patch
-x86_64-dump_trace-atomicity-fix.patch
-x86_64-irq-use-irq_domain-in-ioapic_retrigger_irq.patch
-x86_64-put-more-than-one-cpu-in-target_cpus.patch
-x86-resend-remove-last-two-pci_find-offenders-in-the.patch
-i386-use-asm-offsets-for-the-offsets-of-registers-into-the-pt_regs-struct-rather-than-having-hard-coded-constants.patch
-i386-pda-basic-definitions-for-i386-pda.patch
-i386-pda-initialize-the-per-cpu-data-area.patch
-i386-pda-initialize-the-per-cpu-data-area-voyager-fix.patch
-i386-pda-use-%gs-as-the-pda-base-segment-in-the-kernel.patch
-i386-pda-fix-places-where-using-%gs-changes-the-usermode-abi.patch
-i386-pda-update-sys_vm86-to-cope-with-changed-pt_regs-and-%gs-usage.patch
-i386-pda-implement-smp_processor_id-with-the-pda.patch
-i386-pda-implement-current-with-the-pda.patch
-i386-pda-store-the-interrupt-regs-pointer-in-the-pda.patch
-unwinder-speedup-tweaks.patch
-paravirt-skip-timer-works.patch
-paravirt-skip-timer-works-tidy.patch
-paravirt-interrupts-subarch-cleanup.patch
-paravirt-fix-missing-pte-update.patch
-paravirt-fix-bad-mmu-names.patch
-paravirt-mmu-header-movement.patch
-pktcdvd-reusability-of-procfs-functions.patch
-pktcdvd-make-procfs-interface-optional.patch
-qla1280-bus-reset-typo.patch
-pktcdvd-bio-write-congestion-using-blk_congestion_wait.patch
-pktcdvd-bio-write-congestion-using-blk_congestion_wait-fix.patch
-sparc-clean-up-asm-sparc-elfh-pollution-in-userspace.patch
Merged into mainline or a subsystem tree.
+ioc4_serial-irq-flags-fix.patch
ioc4_serial fix
+ndiswrapper-dont-set-the-module-taints-flags.patch
+let-pci_multithread_probe-depend-on-broken.patch
+isdn-gigaset-avoid-cs-dev-null-pointer-dereference.patch
+m68k-consolidate-initcall-sections.patch
+taskstats-fix-sk_buff-leak.patch
+taskstats-fix-sk_buff-size-calculation.patch
+lockdep-annotate-declare_wait_queue_head.patch
+cryptocop-double-spin_lock_irqsave.patch
+mtd-fix-last-kernel-doc-warning.patch
+docbook-make-a-filesystems-book.patch
+fix-remove-the-use-of-_syscallx-macros-in-uml.patch
+uml-fix-compilation-options-for-user_objs.patch
+xacct_add_tsk-fix-pure-theoretical-mm-use-after-free.patch
+drivers-ide-pci-genericc-add-missing-newline-to-the-all-generic-ide-message.patch
+uml-ubd-driver-allow-using-up-to-16-ubd-devices.patch
+uml-ubd-driver-document-some-struct-fields.patch
+uml-ubd-driver-var-renames.patch
+uml-ubd-driver-give-better-names-to-some-functions.patch
+uml-ubd-driver-change-ubd_lock-to-be-a-mutex.patch
+uml-ubd-driver-ubd_io_lock-usage-fixup.patch
+uml-ubd-driver-reformat-ubd_config.patch
+uml-ubd-driver-convert-do_ubd-to-a-boolean-variable.patch
+uml-ubd-driver-use-bitfields-where-possible.patch
+uml-ubd-driver-do-not-store-error-codes-as-fd.patch
+uml-ubd-driver-various-little-changes.patch
2.6.19 queue.
+fs-prepare_write-fixes-fat-fix.patch
Hopefully mostly fix fatfs
+git-acpi-fixup.patch
+git-acpi-more-build-fixes.patch
+git-acpi-build-fix-99.patch
+git-acpi-mmconfig-warning-fix.patch
+git-acpi-cpufreq-fix.patch
+git-acpi-cpufreq-fix-2.patch
+git-acpi-printk-warning-fix.patch
Attempt to repair acpi disaster
+acpi-fix-single-linked-list-manipulation.patch
acpi fix
+gregkh-driver-w1-ioremap-balanced-with-iounmap.patch
+gregkh-driver-driver-core-add-notification-of-bus-events.patch
+gregkh-driver-cleanup-virtual_device_parent.patch
+gregkh-driver-config_sysfs_deprecated.patch
+gregkh-driver-udev-compatible-hack.patch
+gregkh-driver-config_sysfs_deprecated-bus.patch
+gregkh-driver-config_sysfs_deprecated-device.patch
+gregkh-driver-config_sysfs_deprecated-PHYSDEV.patch
+gregkh-driver-config_sysfs_deprecated-class.patch
+gregkh-driver-vt-device.patch
+gregkh-driver-vc-device.patch
+gregkh-driver-misc-devices.patch
+gregkh-driver-tty-device.patch
+gregkh-driver-raw-device.patch
+gregkh-driver-i2c-dev-device.patch
+gregkh-driver-msr-device.patch
+gregkh-driver-cpuid-device.patch
+gregkh-driver-ppp-device.patch
+gregkh-driver-ppdev-device.patch
+gregkh-driver-mmc-device.patch
+gregkh-driver-firmware-device.patch
+gregkh-driver-fb-device.patch
+gregkh-driver-mem-devices.patch
+gregkh-driver-sound-device.patch
+gregkh-driver-network-device.patch
driver tree udpates. Known to break old udev setups, but published
nonetheless.
+revert-gregkh-driver-tty-device.patch
Make my udev setup work.
+driver-core-fixes-make_class_name-retval-checks.patch
+driver-core-fixes-sysfs_create_link-retval-checks-in.patch
+driver-core-dont-stop-probing-on-probe-errors.patch
+driver-core-change-function-call-order-in.patch
+driver-core-per-subsystem-multithreaded-probing.patch
+driver-core-dont-fail-attaching-the-device-if-it.patch
retrn-value checking
+nozomi-irq-flags-fixes.patch
Fx nozomi driver some more.
+call-platform_notify_remove-later.patch
benh stuff.
-git-dvb-fixup.patch
Dropped.
+jdelvare-i2c-i2c-at91-new-bus-driver.patch
I2C tree update
+ia64-cpu-hotplug-fix-conflict-between-cpu-hot-add-and-ipi.patch
ia64 fix
+lightning-return-proper-return-code.patch
input driver fix
+pa-risc-fix-bogus-warnings-from-modpost.patch
+kconfig-refactoring-for-better-menu-nesting.patch
+kbuild-fix-rr-is-now-default.patch
kbuild/kconfig fixes
+sata_nv-adma-ncq-support-for-nforce4-v7.patch
Updated sata driver
+sata_sis-fix-flags-handling-for-the-secondary-port.patch
+ata-generic-platform_device-libata-driver-take-2.patch
sata things
+mtd-fix-printk-format-warning.patch
MTD fix
+git-net-configh-got-removed.patch
+netxen-build-fix.patch
+netxen-more-build-fixes.patch
git-netdev-all fixes
+defxx-big-endian-hosts-support.patch
+ehea-kzalloc-gfp_atomic-fix.patch
netdev updates
+net-fix-uaccess-handling.patch
+n2-fix-confusing-error-code.patch
+tokenring-fix-module_init-error-handling.patch
net fixes
+nfs-nfsaclsvc_encode_getaclres-fix-potential-null-deref-and-tiny-optimization.patch
+gss_spkm3-fix-error-handling-in-module-init.patch
+sunrpc-add-missing-spin_unlock.patch
+auth_gss-unregister-gss_domain-when-unloading-module.patch
+nfs-fix-nfs_readpages-error-path.patch
NFS things
+gfs2-dont-panic-needlessly.patch
gfs2 fixlet
+parisc-use-unsigned-long-flags-in-semaphore-code.patch
+parisc-fix-module_param-iommu-permission.patch
parisc things
+ppc-booke-reg-mcsr-msg-misquoted.patch
+ppc4xx-compilation-fixes-for-pci-less-configs.patch
ppc things
+perle-multimodem-card-pci-ras-detection.patch
serial driver update
-gregkh-pci-pci-check-that-mwi-bit-really-did-get-set.patch
PCI tree update
-revert-gregkh-pci-pci-check-that-mwi-bit-really-did-get-set.patch
Dropped
+pci-fix-__pci_register_driver-error-handling.patch
+acpiphp-fix-missing-acpiphp_glue_exit.patch
PCI updates
+scsi-minor-bug-fixes-and-cleanups.patch
+scsi-t128-scsi_cmnd-convertion.patch
+scsi-whitespace-cleanup-in-the-dpt-driver.patch
+scsi-fix-uaccess-handling.patch
SCSI updates
+gregkh-usb-sierra-new-device.patch
+gregkh-usb-hid-core-big-endian-fix-fix.patch
USB tree updates
+x86_64-mm-dump_trace-atomicity-fix.patch
+x86_64-mm-entry-cleanup.patch
+x86_64-mm-pda-asm-offset.patch
+x86_64-mm-pda-basics.patch
+x86_64-mm-pda-percpu-init.patch
+x86_64-mm-pda-gs-base.patch
+x86_64-mm-pda-interface.patch
+x86_64-mm-pda-vm86.patch
+x86_64-mm-pda-smp-processor-id.patch
+x86_64-mm-pda-current.patch
+x86_64-mm-pda-int-regs.patch
+x86_64-mm-paravirt-skip-timer.patch
+x86_64-mm-paravirt-subarch-cleanup.patch
+x86_64-mm-no-nested-idle-loops.patch
+x86_64-mm-paravirt-pte-update-common.patch
+x86_64-mm-paravirt-pte-update-prep.patch
+x86_64-mm-paravirt-header-cleanup.patch
+x86_64-mm-remove-pci_find.patch
+x86_64-mm-nmi-message.patch
+x86_64-mm-compat-siocsifhwbroadcast.patch
+x86_64-mm-i386-reloc-abssym.patch
+x86_64-mm-i386-reloc-cleanup-align.patch
+x86_64-mm-i386-reloc-data-4k-aligned.patch
+x86_64-mm-i386-reloc-pa-symbol.patch
+x86_64-mm-i386-reloc-cleanup-kernel-res.patch
+x86_64-mm-i386-reloc-physical-start.patch
+x86_64-mm-i386-reloc-kallsyms.patch
+x86_64-mm-i386-reloc-core.patch
+x86_64-mm-i386-reloc-warn.patch
+x86_64-mm-i386-reloc-bzimage.patch
+x86_64-mm-desc-defs.patch
+x86_64-mm-strange-work_notifysig-code-since-2.6.16.patch
+x86_64-mm-cpa-clflush.patch
+x86_64-mm-i386-clflush-size.patch
+x86_64-mm-i386-cpa-clflush.patch
+x86_64-mm-gh-sync-tsc.patch
+x86_64-mm-i386-create-e820.c-to-handle-standard-io-mem-resources.patch
+x86_64-mm-i386-create-e820.c-about-e820-map-sanitize-and-copy-function.patch
+x86_64-mm-i386-create-e820.c-to-handle-find_max_pfn-function.patch
+x86_64-mm-i386-create-e820.c-to-handle-memmap-table-walking.patch
+x86_64-mm-i386-create-e820.c-about-memap-boot-param-parse-and-print.patch
x86 tree updates
+revert-x86_64-mm-cpa-clflush.patch
It broke.
+x86_64-irq-reuse-vector-for-__assign_irq_vector.patch
+i386-mark-config_relocatable-experimental.patch
+prep-for-paravirt-be-careful-about-touching-bios.patch
+prep-for-paravirt-be-careful-about-touching-bios-warning-fix.patch
+prep-for-paravirt-cpu_detect-extraction.patch
+prep-for-paravirt-desch-clearer-parameter-names.patch
+prep-for-paravirt-desch-clearer-parameter-names-fix.patch
+prep-for-paravirt-rearrange-processorh.patch
+i386-mm-substitute-__va-lookup-with-pfn_to_kaddr.patch
+i386-extend-bzimage-protocol-for-relocatable-protected-mode-kernel.patch
+x86_64-irq-reset-more-to-default-when-clear-irq_vector-for-destroy_irq.patch
+make-x86_64-udelay-round-up-instead-of-down.patch
+i386-x86_64-comment-magic-constants-in-delayh.patch
x86 updates
+vmalloc-optimization-cleanup-bugfixes.patch
+vmalloc-optimization-cleanup-bugfixes-tweak.patch
+mm-slab-eliminate-lock_cpu_hotplug-from-slab.patch
MM updates
+add-include-linux-freezerh-and-move-definitions-from.patch
+add-include-linux-freezerh-and-move-definitions-from-ueagle-fix.patch
+quieten-freezer-if-config_pm_debug.patch
+swsusp-cleanup-whitespace-in-freezer-output.patch
+swsusp-thaw-userspace-and-kernel-space-separately.patch
+swsusp-support-i386-systems-with-pae-or-without-pse.patch
swsusp updates
+uml-fix-prototypes.patch
+uml-make-execvp-safe-for-our-usage.patch
UML
+edac_mc-fix-error-handling.patch
+kbuild-dont-put-temp-files-in-the-source-tree-fix.patch
+drivers-add-lcd-support-update-4.patch
+lockdep-internal-locking-fixes.patch
+lockdep-misc-fixes-in-lockdepc.patch
+cpuset-remove-sched-domain-hooks-from-cpusets.patch
+binfmt_elf-randomize-pie-binaries.patch
+handle-ext3-directory-corruption-better.patch
+handle-ext4-directory-corruption-better.patch
+sysctl-allow-a-zero-ctl_name-in-the-middle-of-a-sysctl-table.patch
+sysctl-implement-ctl_unnumbered.patch
+enforce-unsigned-long-flags-when-spinlocking.patch
+tifm-fix-null-ptr-and-style.patch
+function-v9fs_get_idpool-returns-int-not-u32-as-called-twice.patch
+disable-clone_child_cleartid-for-abnormal-exit.patch
+binfmt-fix-uaccess-handling.patch
+compat-fix-uaccess-handling.patch
+profile-fix-uaccess-handling.patch
+kconfig-printk_time-depends-on-printk.patch
+parport_pc-add-support-for-ox16pci952-parallel-port.patch
+probe_kernel_address-needs-to-do-set_fs.patch
+slab-use-probe_kernel_address.patch
+paride-return-proper-error-code.patch
+read_cache_pages-cleanup.patch
Misc
+tty-signal-tty-locking.patch
+tty-signal-tty-locking-3270-fix.patch
+do_task_stat-dont-take-tty_mutex.patch
+do_acct_process-dont-take-tty_mutex.patch
+trivial-make-set_special_pids-static.patch
+sys_unshare-remove-a-broken-clone_sighand-code.patch
TTY locking update
+pktcdvd-reusability-of-procfs-functions.patch
+pktcdvd-make-procfs-interface-optional.patch
+pktcdvd-bio-write-congestion-using-blk_congestion_wait.patch
+pktcdvd-bio-write-congestion-using-blk_congestion_wait-fix.patch
+pktcdvd-add-sysfs-and-debugfs-interface.patch
packet driver updates
+isdn-gigaset-use-bitrev8.patch
Cleanup
+vfs-change-struct-file-to-use-struct-path.patch
+sysfs-change-uses-of-f_dentry.patch
+proc-change-uses-of-f_dentry-vfsmnt-to-use-f_path.patch
+ext2-change-uses-of-f_dentry-vfsmnt-to-use-f_path.patch
+ext3-change-uses-of-f_dentry-vfsmnt-to-use-f_path.patch
+ext4-change-uses-of-f_dentry-vfsmnt-to-use-f_path.patch
+fat-change-uses-of-f_dentryvfsmnt-to-use-f_path.patch
+isofs-change-uses-of-f_dentry.patch
+nfs-change-uses-of-f_dentryvfsmnt-to-use-f_path.patch
+nfsd-change-uses-of-f_dentry-vfsmnt-to-use-f_path.patch
+ntfs-change-uses-of-f_dentry-vfsmnt-to-use-f_path.patch
+i386-change-uses-of-f_dentry-vfsmnt-to-use-f_path.patch
+x86_64-change-uses-of-f_dentry.patch
+kernel-change-uses-of-f_dentry.patch
+mm-change-uses-of-f_dentryvfsmnt-to-use-f_path.patch
+9p-change-uses-of-f_dentryvfsmnt-to-use-f_path.patch
+affs-change-uses-of-f_dentry-vfsmnt-to-use-f_path.patch
+autofs-change-uses-of-f_dentry.patch
+autofs4-change-uses-of-f_dentry.patch
+configfs-change-uses-of-f_dentry.patch
+cifs-change-uses-of-f_dentry-vfsmnt-to-use-f_path.patch
+ecryptfs-change-uses-of-f_dentry.patch
+xfs-change-uses-of-f_dentryvfsmnt-to-use-f_path.patch
+struct-path-convert-adfs.patch
+struct-path-convert-afs.patch
+struct-path-convert-alpha.patch
+struct-path-convert-atm.patch
+struct-path-convert-befs.patch
+struct-path-convert-bfs.patch
+struct-path-convert-block.patch
+struct-path-convert-block_drivers.patch
+struct-path-convert-char-drivers.patch
+struct-path-convert-coda.patch
+struct-path-convert-cosa.patch
+struct-path-convert-cramfs.patch
+struct-path-convert-cris.patch
+struct-path-convert-drm.patch
+struct-path-convert-efs.patch
+struct-path-convert-freevxfs.patch
+struct-path-convert-frv.patch
+struct-path-convert-fuse.patch
+struct-path-convert-gfs2.patch
+struct-path-convert-hfs.patch
+struct-path-convert-hfsplus.patch
+struct-path-convert-hostfs.patch
+struct-path-convert-hpfs.patch
+struct-path-convert-hppfs.patch
+struct-path-convert-hugetlbfs.patch
+struct-path-convert-i2c-drivers.patch
+struct-path-convert-ia64.patch
+struct-path-convert-ieee1394.patch
+struct-path-convert-infiniband.patch
+struct-path-convert-ipc.patch
+struct-path-convert-ipmi.patch
+struct-path-convert-isapnp.patch
+struct-path-convert-isdn.patch
+struct-path-convert-ixj.patch
+struct-path-convert-jffs.patch
+struct-path-convert-jffs2.patch
+struct-path-convert-jfs.patch
+struct-path-convert-kernel.patch
+struct-path-convert-lockd.patch
+struct-path-convert-md.patch
+struct-path-convert-minix.patch
+struct-path-convert-mips.patch
+struct-path-convert-mm.patch
+struct-path-convert-nbd.patch
+struct-path-convert-ncpfs.patch
+struct-path-convert-net.patch
+struct-path-convert-netfilter.patch
+struct-path-convert-netlink.patch
+struct-path-convert-ocfs2.patch
+struct-path-convert-openpromfs.patch
+struct-path-convert-oprofile.patch
+struct-path-convert-parisc.patch
+struct-path-convert-pci.patch
+struct-path-convert-pcmcia.patch
+struct-path-convert-powerpc.patch
+struct-path-convert-ppc.patch
+struct-path-convert-qnx4.patch
+struct-path-convert-ramfs.patch
+struct-path-convert-reiserfs.patch
+struct-path-convert-romfs.patch
+struct-path-convert-s390-drivers.patch
+struct-path-convert-s390.patch
+struct-path-convert-sbus.patch
+struct-path-convert-scsi.patch
+struct-path-convert-selinux.patch
+struct-path-convert-sh.patch
+struct-path-convert-smbfs.patch
+struct-path-convert-sound.patch
+struct-path-convert-sparc.patch
+struct-path-convert-sparc64.patch
+struct-path-convert-splice.patch
+struct-path-convert-sunrpc.patch
+struct-path-convert-sysv.patch
+struct-path-convert-udf.patch
+struct-path-convert-ufs.patch
+struct-path-convert-unix.patch
+struct-path-convert-usb.patch
+struct-path-convert-v4l.patch
+struct-path-convert-video.patch
+struct-path-convert-zorro.patch
102 patches to do something rather pointless.
+add-process_session-helper-routine-deprecate-old-field-fix-warnings-fix.patch
Yet more fixes to add-process_session-helper-routine-deprecate-old-field-tidy.patch
+sys_setpgid-eliminate-unnecessary-do_each_task_pidpidtype_pgid.patch
+session_of_pgrp-kill-unnecessary-do_each_task_pidpidtype_pgid.patch
Core kernel fixes
+mxser-session-warning-fix.patch
Fix mxser for other patches in -mm.
+tty-switch-to-ktermios-sclp-fix.patch
+tty-switch-to-ktermios-3270-fix.patch
+tty-switch-to-ktermios-powerpc-fix.patch
Fix the termios patches in -mm.
+char-isicom-use-completion.patch
+char-isicom-simplify-timer.patch
+char-isicom-remove-cvs-stuff.patch
+char-sx-convert-to-pci-probing.patch
+char-sx-use-kcalloc.patch
+char-sx-mark-functions-as-devinit.patch
+char-sx-use-eisa-probing.patch
+char-sx-ifdef-isa-code.patch
+char-stallion-convert-to-pci-probing.patch
+char-stallion-prints-cleanup.patch
+char-stallion-implement-fail-paths.patch
+char-stallion-correct-__init-macros.patch
Various fixes and cleanups against various serial drivers.
+isdn-fix-missing-unregister_capi_driver.patch
isdn fix
+add-include-linux-freezerh-and-move-definitions-from-prefetch.patch
Update swap-prefetch for other patches in -mm.
+resier4-add-include-linux-freezerh-and-move-definitions-from.patch
+reiser4-fix-missed-unlock-and-exit_context.patch
+reiser4-use-list_empty-instead-of-list_empty_careful-for.patch
reiser4 updates
+video-sis-remove-unnecessary-variables-in-sis_ddc2delay.patch
fbdev driver cleanup
+statistics-infrastructure-fix-buffer-overflow-in-histogram-with-linear.patch
+statistics-infrastructure-fix-buffer-overflow-in-histogram-with-linear-tidy.patch
+statistics-infrastructure-adapt-output-format-of-utilisation-indicator.patch
Fix statistics patches in -mm.
+dio-lock-refcount-operations.patch
More direct-io work
-x86-e820-debugging.patch
Dropped
-mm-only-i_size_write-debugging.patch
-mm-only-i_size_write-debugging-fix.patch
Dropped
All 1028 patches:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc3/2.6.19-rc3-mm1/patch-list
On Sun, Oct 29, 2006 at 04:00:02PM -0800, Andrew Morton wrote:
> - For some reason Greg has resurrected the patches which detect whether
> you're using old versions of udev and if so, punish you for it.
>
> If weird stuff happens, try upgrading udev.
Where "old" is how old exactly ?
Dave
--
http://www.codemonkey.org.uk
On Sun, Oct 29, 2006 at 09:50:00PM -0500, Dave Jones wrote:
> On Sun, Oct 29, 2006 at 04:00:02PM -0800, Andrew Morton wrote:
>
> > - For some reason Greg has resurrected the patches which detect whether
> > you're using old versions of udev and if so, punish you for it.
> >
> > If weird stuff happens, try upgrading udev.
>
> Where "old" is how old exactly ?
As per the Kconfig help entry, any version of udev released before 2006
will probably have problems with the new config option. So follow the
text and enable the option if you are running an old version of udev and
you should be fine.
No more need to upgrade udev if you don't want to, everything should
work as-is unless you do not want it to.
I think the CHANGES file shows the version of udev that will work
properly with this change, but I need to go verify that.
thanks,
greg k-h
On Sun, 29 Oct 2006 19:54:30 -0800
Greg KH <[email protected]> wrote:
> On Sun, Oct 29, 2006 at 09:50:00PM -0500, Dave Jones wrote:
> > On Sun, Oct 29, 2006 at 04:00:02PM -0800, Andrew Morton wrote:
> >
> > > - For some reason Greg has resurrected the patches which detect whether
> > > you're using old versions of udev and if so, punish you for it.
> > >
> > > If weird stuff happens, try upgrading udev.
> >
> > Where "old" is how old exactly ?
>
> As per the Kconfig help entry, any version of udev released before 2006
> will probably have problems with the new config option. So follow the
> text and enable the option if you are running an old version of udev and
> you should be fine.
<hunts>
Greg is referring to CONFIG_SYSFS_DEPRECATED. I didn't know it existed.
If I had known I'd have saved maybe an hour and I perhaps wouldn't have had
to revert gregkh-driver-tty-device.patch
What mailing list was this discussed and reviewed on?
The option should default to "y".
The changelog is wrong. Or garbled. Certainly confusing.
On Sun, Oct 29, 2006 at 09:16:04PM -0800, Andrew Morton wrote:
> On Sun, 29 Oct 2006 19:54:30 -0800
> Greg KH <[email protected]> wrote:
>
> > On Sun, Oct 29, 2006 at 09:50:00PM -0500, Dave Jones wrote:
> > > On Sun, Oct 29, 2006 at 04:00:02PM -0800, Andrew Morton wrote:
> > >
> > > > - For some reason Greg has resurrected the patches which detect whether
> > > > you're using old versions of udev and if so, punish you for it.
> > > >
> > > > If weird stuff happens, try upgrading udev.
> > >
> > > Where "old" is how old exactly ?
> >
> > As per the Kconfig help entry, any version of udev released before 2006
> > will probably have problems with the new config option. So follow the
> > text and enable the option if you are running an old version of udev and
> > you should be fine.
>
> <hunts>
>
> Greg is referring to CONFIG_SYSFS_DEPRECATED. I didn't know it existed.
> If I had known I'd have saved maybe an hour and I perhaps wouldn't have had
> to revert gregkh-driver-tty-device.patch
Don't you run 'make oldconfig'? :)
> What mailing list was this discussed and reviewed on?
None so far, I didn't think a "enable old, obsolete versions of udev to
still work properly" config option would be all that controversial.
> The option should default to "y".
Ok, will change it.
> The changelog is wrong. Or garbled. Certainly confusing.
Oops, you are right, the text in the changelog conflicts with the
reality in the Kconfig entry. I'll fix that up. The Kconfig text is
correct.
thanks,
greg k-h
On 30/10/2006 11:00 AM, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc3/2.6.19-rc3-mm1/
>
> - ia64 doesn't compile due to improvements in acpi. I already fixed a huge
> string of build errors due to this and it's someone else's turn.
>
> - For some reason Greg has resurrected the patches which detect whether
> you're using old versions of udev and if so, punish you for it.
>
> If weird stuff happens, try upgrading udev.
udev-095 here.
Some slightly odd messages in dmesg. Overall this -mm boots and runs and seems
to be reasonably good (the last -mm didn't boot for me).
1. NMI message - I too, am dazed and confused about this one:
Linux version 2.6.19-rc3-mm1 ([email protected]) (gcc version 4.1.1 20061025
(Red Hat 4.1.1-31)) #1 SMP Mon Oct 30 11:15:58
EST 2006
Command line: ro root=/dev/md0 panic=60 console=ttyS0,57600
...
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 2048K
using mwait in idle threads.
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU0: Thermal monitoring enabled (TM1)
Freeing SMP alternatives: 28k freed
ACPI: Core revision 20061011
Using local APIC timer interrupts.
result 12500379
Detected 12.500 MHz APIC timer.
lockdep: not fixing up alternatives.
Booting processor 1/2 APIC 0x1
Initializing CPU#1
Calibrating delay using timer specific routine.. 6000.02 BogoMIPS (lpj=12000044)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 2048K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU1: Thermal monitoring enabled (TM1)
Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 03
Brought up 2 CPUs
testing NMI watchdog ... CPU#0: NMI appears to be stuck (58->63)!
OK.
time.c: Using 14.318180 MHz WALL HPET GTOD HPET/TSC timer.
Uhhuh. NMI received for unknown reason 3c.
Do you have a strange power saving mode enabled?
Dazed and confused, but trying to continue
time.c: Detected 3000.114 MHz processor.
migration_cost=21
It's a desktop PC/server, no strange power saving mode going on here. Unsure
who looks after this or why it would occur.
2. Think this is ok, but still - timeouts, frozen - all words that suggest
suboptimal things have gone on:
ata_piix 0000:00:1f.1: version 2.00ac7
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1f.1 to 64
ata1: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x20B0 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x20B8 irq 15
scsi0 : ata_piix
ata1.00: ATAPI, max UDMA/66
ata1.00: configured for UDMA/66
scsi1 : ata_piix
ata2: port disabled. ignoring.
ATA: abnormal status 0xFF on port 0x177
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: (BMDMA stat 0x24)
ata1.00: tag 0 cmd 0xa0 Emask 0x4 stat 0x40 err 0x0 (timeout)
ata1: soft resetting port
ata1.00: configured for UDMA/66
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: (BMDMA stat 0x24)
ata1.00: tag 0 cmd 0xa0 Emask 0x4 stat 0x40 err 0x0 (timeout)
ata1: soft resetting port
ata1.00: configured for UDMA/66
ata1: EH complete
scsi 0:0:0:0: CD-ROM PIONEER DVD-RW DVR-111D 1.23 PQ: 0 ANSI: 5
scsi 0:0:0:0: Attached scsi generic sg0 type 5
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata3: SATA max UDMA/133 cmd 0x20C8 ctl 0x20EE bmdma 0x20A0 irq 19
ata4: SATA max UDMA/133 cmd 0x20C0 ctl 0x20EA bmdma 0x20A8 irq 19
scsi2 : ata_piix
The device on ata1 is the DVD-RW Atapi.
All devices seem to be detected and work, so it may be just cosmetic. Alan?
Reuben
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc3/2.6.19-rc3-mm1/
>
> - ia64 doesn't compile due to improvements in acpi. I already fixed a huge
> string of build errors due to this and it's someone else's turn.
>
> - For some reason Greg has resurrected the patches which detect whether
> you're using old versions of udev and if so, punish you for it.
>
> If weird stuff happens, try upgrading udev.
I have four machines showing problems with 2.6.19-rc3-mm1. In each case
they appear to have lost their ethernet cards completely. I have a
ppc64 using ibm_veth, two ppc64's using e1000's and an x86_64 using a
Tigon 3.
Before I had results from the non e1000 machines I did try backing out
all e1000 patches to no effect. I also had a quick scan of the
changelogs for net/ and nothing jumped out at me.
Any suggestions what to hack out next?
-apw
Andy Whitcroft wrote:
> Andrew Morton wrote:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc3/2.6.19-rc3-mm1/
>>
>> - ia64 doesn't compile due to improvements in acpi. I already fixed a huge
>> string of build errors due to this and it's someone else's turn.
>>
>> - For some reason Greg has resurrected the patches which detect whether
>> you're using old versions of udev and if so, punish you for it.
>>
>> If weird stuff happens, try upgrading udev.
>
> I have four machines showing problems with 2.6.19-rc3-mm1. In each case
> they appear to have lost their ethernet cards completely. I have a
> ppc64 using ibm_veth, two ppc64's using e1000's and an x86_64 using a
> Tigon 3.
>
> Before I had results from the non e1000 machines I did try backing out
> all e1000 patches to no effect. I also had a quick scan of the
> changelogs for net/ and nothing jumped out at me.
>
> Any suggestions what to hack out next?
At least on one machine with 8 tg3 cards, it finds all its interfaces,
but then drops into:
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8
7[?25l[1A[80C[10D[1;32mdone[m8[?25h eth0
No configuration found for eth0
7[?25l[1A[80C[10D[1munused[m8[?25h eth1
No configuration found for eth1
for all 8 cards.
(
Other ones just do this:
. . . . . . . . . . . . . . . . . . . . .
. . .7[?25l[80C[10D[1;32mdone[m8[?25h
[m[?25hSetting up network interfaces:
e1000: 0000:c8:01.0: e1000_probe: (PCI-X:133MHz:64-bit) 00:09:6b:6e:80:42
lo
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
lo IP address: 127.0.0.1/8
7[?25l[1A[80C[10D[1;32mdone[m8[?25hWaiting for mandatory devices:
eth-id-00:09:6b:6e:80:42
19 e1000: 0000:c8:01.1: e1000_probe: (PCI-X:133MHz:64-bit) 00:09:6b:6e:80:43
e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
eth-id-00:09:6b:6e:80:42 No interface found
(http://test.kernel.org/abat/59143/debug/console.log)
Sorry about the jibberish logs. Seems like SLES takes it upon itself
to spew random "enhanced" shit on bootup.
M.
On Mon, 30 Oct 2006 07:47:00 -0800
"Martin J. Bligh" <[email protected]> wrote:
> Andy Whitcroft wrote:
> > Andrew Morton wrote:
> >> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc3/2.6.19-rc3-mm1/
> >>
> >> - ia64 doesn't compile due to improvements in acpi. I already fixed a huge
> >> string of build errors due to this and it's someone else's turn.
> >>
> >> - For some reason Greg has resurrected the patches which detect whether
> >> you're using old versions of udev and if so, punish you for it.
> >>
> >> If weird stuff happens, try upgrading udev.
> >
> > I have four machines showing problems with 2.6.19-rc3-mm1. In each case
> > they appear to have lost their ethernet cards completely. I have a
> > ppc64 using ibm_veth, two ppc64's using e1000's and an x86_64 using a
> > Tigon 3.
> >
> > Before I had results from the non e1000 machines I did try backing out
> > all e1000 patches to no effect. I also had a quick scan of the
> > changelogs for net/ and nothing jumped out at me.
> >
> > Any suggestions what to hack out next?
>
> At least on one machine with 8 tg3 cards, it finds all its interfaces,
> but then drops into:
>
>
>
> Setting up network interfaces:
> lo
> lo IP address: 127.0.0.1/8
> 7[?25l[1A[80C[10D[1;32mdone[m8[?25h eth0
> No configuration found for eth0
> 7[?25l[1A[80C[10D[1munused[m8[?25h eth1
> No configuration found for eth1
>
> for all 8 cards.
What version of udev is being used?
Was CONFIG_SYSFS_DEPRECATED set?
> CPU1: Thermal monitoring enabled (TM1)
> Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 03
> Brought up 2 CPUs
> testing NMI watchdog ... CPU#0: NMI appears to be stuck (58->63)!
> OK.
> time.c: Using 14.318180 MHz WALL HPET GTOD HPET/TSC timer.
> Uhhuh. NMI received for unknown reason 3c.
> Do you have a strange power saving mode enabled?
> Dazed and confused, but trying to continue
> time.c: Detected 3000.114 MHz processor.
> migration_cost=21
Are you using AMD64 machine? Have you got powernow enabled in the bios?
I had seen the same problem. Disabling powernow / disabling HPET takes
this whining away :-)
Regards,
Om.
>>Setting up network interfaces:
>> lo
>> lo IP address: 127.0.0.1/8
>>7[?25l[1A[80C[10D[1;32mdone[m8[?25h eth0
>> No configuration found for eth0
>>7[?25l[1A[80C[10D[1munused[m8[?25h eth1
>> No configuration found for eth1
>>
>>for all 8 cards.
>
>
> What version of udev is being used?
Buggered if I know. If we could quit breaking it, that'd be good though.
If it printed its version during boot somewhere, that'd help too.
> Was CONFIG_SYSFS_DEPRECATED set?
No.
M.
Martin Bligh wrote:
>>> Setting up network interfaces:
>>> lo
>>> lo IP address: 127.0.0.1/8
>>> 7[?25l[1A[80C[10D[1;32mdone[m8[?25h eth0
>>> No configuration found for eth0
>>> 7[?25l[1A[80C[10D[1munused[m8[?25h eth1
>>> No configuration found for eth1
>>>
>>> for all 8 cards.
>>
>>
>> What version of udev is being used?
>
> Buggered if I know. If we could quit breaking it, that'd be good though.
> If it printed its version during boot somewhere, that'd help too.
>
>> Was CONFIG_SYSFS_DEPRECATED set?
>
> No.
>
> M.
These all sounds pretty old. I'll rerun them all with
CONFIG_SYSFS_DEPRECATED set and see what pans out.
-apw
elm3b239:~ # udevinfo -V
udevinfo, version 085
elm3b239:~ #
gekko-lp1:~ # udevinfo -V
udevinfo, version 021_bk
gekko-lp1:~ #
bucket:~ # udevinfo -V
udevinfo, version 021_bk
bucket:~ #
el9-92-101:~ # udevinfo -V
udevinfo, version 021_bk
el9-92-101:~ #
Hi,
On Monday, 30 October 2006 06:16, Andrew Morton wrote:
> On Sun, 29 Oct 2006 19:54:30 -0800
> Greg KH <[email protected]> wrote:
>
> > On Sun, Oct 29, 2006 at 09:50:00PM -0500, Dave Jones wrote:
> > > On Sun, Oct 29, 2006 at 04:00:02PM -0800, Andrew Morton wrote:
> > >
> > > > - For some reason Greg has resurrected the patches which detect whether
> > > > you're using old versions of udev and if so, punish you for it.
> > > >
> > > > If weird stuff happens, try upgrading udev.
> > >
> > > Where "old" is how old exactly ?
> >
> > As per the Kconfig help entry, any version of udev released before 2006
> > will probably have problems with the new config option. So follow the
> > text and enable the option if you are running an old version of udev and
> > you should be fine.
>
> <hunts>
>
> Greg is referring to CONFIG_SYSFS_DEPRECATED. I didn't know it existed.
> If I had known I'd have saved maybe an hour and I perhaps wouldn't have had
> to revert gregkh-driver-tty-device.patch
>
> What mailing list was this discussed and reviewed on?
>
> The option should default to "y".
I have this one set, but the kernel apparently fails to find the ATI SATA
controller:
00:12.0 IDE interface: ATI Technologies Inc ATI 4379 Serial ATA Controller (rev 80) (prog-if 8f [Master SecP SecO PriP PriO])
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
I/O ports at 9000 [size=8]
I/O ports at 9008 [size=4]
I/O ports at 9010 [size=8]
I/O ports at 7018 [size=4]
I/O ports at 7020 [size=16]
Memory at d4409000 (32-bit, non-prefetchable) [size=512]
[virtual] Expansion ROM at 52000000 [disabled] [size=512K]
Capabilities: [60] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: 64bit- Queue=0/0 Enable
(with 2.6.19-rc2-mm2 and before it was handled by the sata_sil driver).
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
On Mon, Oct 30, 2006 at 08:55:18PM +0100, Rafael J. Wysocki wrote:
> Hi,
>
> On Monday, 30 October 2006 06:16, Andrew Morton wrote:
> > On Sun, 29 Oct 2006 19:54:30 -0800
> > Greg KH <[email protected]> wrote:
> >
> > > On Sun, Oct 29, 2006 at 09:50:00PM -0500, Dave Jones wrote:
> > > > On Sun, Oct 29, 2006 at 04:00:02PM -0800, Andrew Morton wrote:
> > > >
> > > > > - For some reason Greg has resurrected the patches which detect whether
> > > > > you're using old versions of udev and if so, punish you for it.
> > > > >
> > > > > If weird stuff happens, try upgrading udev.
> > > >
> > > > Where "old" is how old exactly ?
> > >
> > > As per the Kconfig help entry, any version of udev released before 2006
> > > will probably have problems with the new config option. So follow the
> > > text and enable the option if you are running an old version of udev and
> > > you should be fine.
> >
> > <hunts>
> >
> > Greg is referring to CONFIG_SYSFS_DEPRECATED. I didn't know it existed.
> > If I had known I'd have saved maybe an hour and I perhaps wouldn't have had
> > to revert gregkh-driver-tty-device.patch
> >
> > What mailing list was this discussed and reviewed on?
> >
> > The option should default to "y".
>
> I have this one set, but the kernel apparently fails to find the ATI SATA
> controller:
>
> 00:12.0 IDE interface: ATI Technologies Inc ATI 4379 Serial ATA Controller (rev 80) (prog-if 8f [Master SecP SecO PriP PriO])
> Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
> I/O ports at 9000 [size=8]
> I/O ports at 9008 [size=4]
> I/O ports at 9010 [size=8]
> I/O ports at 7018 [size=4]
> I/O ports at 7020 [size=16]
> Memory at d4409000 (32-bit, non-prefetchable) [size=512]
> [virtual] Expansion ROM at 52000000 [disabled] [size=512K]
> Capabilities: [60] Power Management version 2
> Capabilities: [50] Message Signalled Interrupts: 64bit- Queue=0/0 Enable
>
> (with 2.6.19-rc2-mm2 and before it was handled by the sata_sil driver).
This has nothing to do with the CONFIG_SYSFS_DEPRECATED configuration
option. Do you have CONFIG_PCI_MULTITHREAD_PROBE also enabled? If so,
please disable it, some SATA drivers do not like it very much just yet.
thanks,
greg k-h
On Mon, 30 Oct 2006 17:21:05 +0000,
Andy Whitcroft <[email protected]> wrote:
> Martin Bligh wrote:
> >>> Setting up network interfaces:
> >>> lo
> >>> lo IP address: 127.0.0.1/8
> >>> 7[?25l[1A[80C[10D[1;32mdone[m8[?25h eth0
> >>> No configuration found for eth0
> >>> 7[?25l[1A[80C[10D[1munused[m8[?25h eth1
> >>> No configuration found for eth1
> >>>
> >>> for all 8 cards.
> >>
> >>
> >> What version of udev is being used?
> >
> > Buggered if I know. If we could quit breaking it, that'd be good though.
> > If it printed its version during boot somewhere, that'd help too.
> >
> >> Was CONFIG_SYSFS_DEPRECATED set?
> >
> > No.
> >
> > M.
>
> These all sounds pretty old. I'll rerun them all with
> CONFIG_SYSFS_DEPRECATED set and see what pans out.
With CONFIG_SYSFS_DEPRECATED set, you'll get errors for devices which
have no parent set. The kobject's parent is set to the class
subsystem's kobject, meaning there is a child with name bus_id (e.
g. /sys/class/net/lo). Unfortunately, we also try to create a link
named bus_id in /sys/class/<foo>, which will fail with -EEXIST... We
should probably drop that link if we have no parent.
FWIW, my s390 system (modified FC 4) works fine with
CONFIG_SYSFS_DEPRECATED not set (parent-less devices showing up under
virtual/):
[root@t2930034 ~]# ls -l /sys/class/net/
total 0
lrwxrwxrwx 1 root root 0 Oct 30 20:57 dummy0-> ../../devices/virtual/net/dummy0
lrwxrwxrwx 1 root root 0 Oct 30 20:57 eth0-> ../../devices/qeth/0.0.f5f0/eth0
lrwxrwxrwx 1 root root 0 Oct 30 20:57 lo-> ../../devices/virtual/net/lo
lrwxrwxrwx 1 root root 0 Oct 30 20:57 sit0 -> ../../devices/virtual/net/sit0
lrwxrwxrwx 1 root root 0 Oct 30 20:57 tunl0 -> ../../devices/virtual/net/tunl0
Maybe the initscripts have problems coping with the new layout
(symlinks instead of real devices)?
--
Cornelia Huck
Linux for zSeries Developer
Tel.: +49-7031-16-4837, Mail: [email protected]
On Monday, 30 October 2006 21:04, Greg KH wrote:
> On Mon, Oct 30, 2006 at 08:55:18PM +0100, Rafael J. Wysocki wrote:
> > Hi,
> >
> > On Monday, 30 October 2006 06:16, Andrew Morton wrote:
> > > On Sun, 29 Oct 2006 19:54:30 -0800
> > > Greg KH <[email protected]> wrote:
> > >
> > > > On Sun, Oct 29, 2006 at 09:50:00PM -0500, Dave Jones wrote:
> > > > > On Sun, Oct 29, 2006 at 04:00:02PM -0800, Andrew Morton wrote:
> > > > >
> > > > > > - For some reason Greg has resurrected the patches which detect whether
> > > > > > you're using old versions of udev and if so, punish you for it.
> > > > > >
> > > > > > If weird stuff happens, try upgrading udev.
> > > > >
> > > > > Where "old" is how old exactly ?
> > > >
> > > > As per the Kconfig help entry, any version of udev released before 2006
> > > > will probably have problems with the new config option. So follow the
> > > > text and enable the option if you are running an old version of udev and
> > > > you should be fine.
> > >
> > > <hunts>
> > >
> > > Greg is referring to CONFIG_SYSFS_DEPRECATED. I didn't know it existed.
> > > If I had known I'd have saved maybe an hour and I perhaps wouldn't have had
> > > to revert gregkh-driver-tty-device.patch
> > >
> > > What mailing list was this discussed and reviewed on?
> > >
> > > The option should default to "y".
> >
> > I have this one set, but the kernel apparently fails to find the ATI SATA
> > controller:
[--snip--]
>
> This has nothing to do with the CONFIG_SYSFS_DEPRECATED configuration
> option. Do you have CONFIG_PCI_MULTITHREAD_PROBE also enabled? If so,
> please disable it, some SATA drivers do not like it very much just yet.
Sorry, I was wrong.
The controller _is_ detected and handled properly, but udev is apparently
unable to create the special device files for SATA drives/partitions even
though CONFIG_SYSFS_DEPRECATED is set.
The system is SUSE 10.1 (udev-085-30.15).
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
On Mon, Oct 30, 2006 at 09:15:37PM +0100, Rafael J. Wysocki wrote:
> Sorry, I was wrong.
>
> The controller _is_ detected and handled properly, but udev is apparently
> unable to create the special device files for SATA drives/partitions even
> though CONFIG_SYSFS_DEPRECATED is set.
This config option should not affect the block device sysfs files at all
at this point in time.
What does 'tree /sys/block/' show?
If the files show up there properly, udev should handle them just fine.
> The system is SUSE 10.1 (udev-085-30.15).
That should not cause any problems.
thanks,
greg k-h
Rafael J. Wysocki wrote:
> The controller _is_ detected and handled properly, but udev is apparently
> unable to create the special device files for SATA drives/partitions even
> though CONFIG_SYSFS_DEPRECATED is set.
Did you forget to enable CONFIG_BLK_DEV_SD or CONFIG_BLK_DEV_SR?
Jeff
Andy Whitcroft wrote:
> Martin Bligh wrote:
>>>> Setting up network interfaces:
>>>> lo
>>>> lo IP address: 127.0.0.1/8
>>>> 7[?25l[1A[80C[10D[1;32mdone[m8[?25h eth0
>>>> No configuration found for eth0
>>>> 7[?25l[1A[80C[10D[1munused[m8[?25h eth1
>>>> No configuration found for eth1
>>>>
>>>> for all 8 cards.
>>>
>>> What version of udev is being used?
>> Buggered if I know. If we could quit breaking it, that'd be good though.
>> If it printed its version during boot somewhere, that'd help too.
>>
>>> Was CONFIG_SYSFS_DEPRECATED set?
>> No.
>>
>> M.
>
> These all sounds pretty old. I'll rerun them all with
> CONFIG_SYSFS_DEPRECATED set and see what pans out.
>
Ok, these have all popped through. Three of the four seems unchanged,
so I am inclined to think that turning on SYSFS_DEPRECATED has not
helped us.
One seems to have blown up differently:
Badness in enter_rtas at arch/powerpc/kernel/entry_64.S:641
Call Trace:
[C0000000FFF83080] [C000000000010470] .show_stack+0x74/0x1b4 (unreliable)
[C0000000FFF83130] [C00000000039FD84] .program_check_exception+0x1f4/0x6c8
[C0000000FFF83210] [C000000000004774] program_check_common+0xf4/0x100
--- Exception: 700 at .enter_rtas+0xa0/0x10c
LR = .xmon_core+0x474/0x864
[C0000000FFF83500] [C0000000004D8D1C] 0xc0000000004d8d1c (unreliable)
[C0000000FFF836E0] [C00000000004FF60] .xmon_core+0x474/0x864
[C0000000FFF83870] [C0000000000505A8] .xmon+0x34/0x44
[C0000000FFF83A40] [C000000000025D80] .die+0x5c/0x1b8
[C0000000FFF83AD0] [C00000000002F248] .bad_page_fault+0xc4/0xe0
[C0000000FFF83B50] [C000000000004B98] .handle_page_fault+0x3c/0x54
--- Exception: 300 at .llc_init+0x34/0x8c
LR = .init+0x1f4/0x3e4
[C0000000FFF83E40] [C00000000045CAB8] .md_init+0xf0/0x124 (unreliable)
[C0000000FFF83EC0] [C000000000009540] .init+0x1f4/0x3e4
[C0000000FFF83F90] [C0000000000275FC] .kernel_thread+0x4c/0x68
enter ? for help
[c0000000fff83ec0] c000000000009540 .init+0x1f4/0x3e4
[c0000000fff83f90] c0000000000275fc .kernel_thread+0x4c/0x68
-apw
On Monday, 30 October 2006 21:36, Jeff Garzik wrote:
> Rafael J. Wysocki wrote:
> > The controller _is_ detected and handled properly, but udev is apparently
> > unable to create the special device files for SATA drives/partitions even
> > though CONFIG_SYSFS_DEPRECATED is set.
>
>
> Did you forget to enable CONFIG_BLK_DEV_SD or CONFIG_BLK_DEV_SR?
Well, I took a working .config from 2.6.19-rc2-mm2 and run 'make oldconfig'
on it. :-) [CONFIG_BLK_DEV_SD=y and CONFIG_BLK_DEV_SR=m]
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
On Monday, 30 October 2006 21:22, Greg KH wrote:
> On Mon, Oct 30, 2006 at 09:15:37PM +0100, Rafael J. Wysocki wrote:
> > Sorry, I was wrong.
> >
> > The controller _is_ detected and handled properly, but udev is apparently
> > unable to create the special device files for SATA drives/partitions even
> > though CONFIG_SYSFS_DEPRECATED is set.
>
> This config option should not affect the block device sysfs files at all
> at this point in time.
>
> What does 'tree /sys/block/' show?
I can't run 'tree', but 'ls' works somehow (can't mount the root fs). The
block device sysfs files seem to be present
> If the files show up there properly, udev should handle them just fine.
It doesn't.
Well, I can binary search for the offending patch if that helps.
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
On Mon, Oct 30, 2006 at 09:48:33PM +0100, Rafael J. Wysocki wrote:
> On Monday, 30 October 2006 21:22, Greg KH wrote:
> > On Mon, Oct 30, 2006 at 09:15:37PM +0100, Rafael J. Wysocki wrote:
> > > Sorry, I was wrong.
> > >
> > > The controller _is_ detected and handled properly, but udev is apparently
> > > unable to create the special device files for SATA drives/partitions even
> > > though CONFIG_SYSFS_DEPRECATED is set.
> >
> > This config option should not affect the block device sysfs files at all
> > at this point in time.
> >
> > What does 'tree /sys/block/' show?
>
> I can't run 'tree', but 'ls' works somehow (can't mount the root fs). The
> block device sysfs files seem to be present
If they are there, then udev should work just fine.
> > If the files show up there properly, udev should handle them just fine.
>
> It doesn't.
>
> Well, I can binary search for the offending patch if that helps.
That would be very helpful, thanks.
greg k-h
Andy Whitcroft wrote:
> Andy Whitcroft wrote:
>> Martin Bligh wrote:
>>>>> Setting up network interfaces:
>>>>> lo
>>>>> lo IP address: 127.0.0.1/8
>>>>> 7[?25l[1A[80C[10D[1;32mdone[m8[?25h eth0
>>>>> No configuration found for eth0
>>>>> 7[?25l[1A[80C[10D[1munused[m8[?25h eth1
>>>>> No configuration found for eth1
>>>>>
>>>>> for all 8 cards.
>>>> What version of udev is being used?
>>> Buggered if I know. If we could quit breaking it, that'd be good though.
>>> If it printed its version during boot somewhere, that'd help too.
>>>
>>>> Was CONFIG_SYSFS_DEPRECATED set?
>>> No.
>>>
>>> M.
>> These all sounds pretty old. I'll rerun them all with
>> CONFIG_SYSFS_DEPRECATED set and see what pans out.
>>
>
> Ok, these have all popped through. Three of the four seems unchanged,
> so I am inclined to think that turning on SYSFS_DEPRECATED has not
> helped us.
>
> One seems to have blown up differently:
>
[...]
Ok, it was suggested that we revert all of gregkh's patches as a first
stab at a cuplprit. I reverted the changes between the following two
patches (inclusive):
gregkh-driver-w1-ioremap-balanced-with-iounmap.patch
call-platform_notify_remove-later.patch
The first result in is a positive test complete on that machine. Will
check the remainder of the tests in the morning.
-apw
Hello,
I got the BUG below while booting. -rc2-mm2 worked fine, but with a
different .config. I'm going to try and narrow this down further.
cheers,
Andrew Wade
agpgart: Detected VIA KT266/KY266x/KT333 chipset
agpgart: unable to get minor: 175
agpgart: agp_frontend_initialize() failed.
------------[ cut here ]------------
kernel BUG at arch/i386/mm/pageattr.c:165!
invalid opcode: 0000 [#1]
last sysfs file:
CPU: 0
EIP: 0060:[<c010fdd7>] Not tainted VLI
EFLAGS: 00010082 (2.6.19-rc3-mm1 #1)
EIP is at change_page_attr+0x167/0x234
eax: 1fc001e3 ebx: c1009c80 ecx: dfc20000 edx: c04e4dfc
esi: 1fc20000 edi: e0820000 ebp: 00000005 esp: dffc5e7c
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, ti=dffc4000 task=dffc3530 task.ti=dffc4000)
Stack: 00000011 c13f8400 00000010 00000292 c04e4dfc dfc20000 00000163 00000163
c13f8200 dfe66984 e0820000 00000005 c010fab8 c03ee740 c03ee740 dfe2334c
00000004 e080f000 c0289195 dfe2334c dfe2334c e080f000 c02881f6 fffffffb
Call Trace:
[<c010fab8>] iounmap+0xaa/0xdc
[<00000004>] 0x4
=======================
Code: 84 b7 00 00 00 eb d2 ff 43 0c eb 23 84 c0 78 1b 0b 74 24 1c 8b 54 24 10 89 32 8b 43 0c 85 c0 75 04 0f 0b eb fe 48 89 43 0c eb 04 <0f> 0b eb fe 8b 03 f6 c4 04 75 6c f6 05 0c 7c 45 c0 08 74 63 83
EIP: [<c010fdd7>] change_page_attr+0x167/0x234 SS:ESP 0068:dffc5e7c
<0>Kernel panic - not syncing: Attempted to kill init!
On Mon, 30 Oct 2006 20:26:24 -0500
Andrew James Wade <[email protected]> wrote:
> I got the BUG below while booting. -rc2-mm2 worked fine, but with a
> different .config. I'm going to try and narrow this down further.
>
> cheers,
> Andrew Wade
>
> agpgart: Detected VIA KT266/KY266x/KT333 chipset
> agpgart: unable to get minor: 175
> agpgart: agp_frontend_initialize() failed.
> ------------[ cut here ]------------
> kernel BUG at arch/i386/mm/pageattr.c:165!
> invalid opcode: 0000 [#1]
> last sysfs file:
> CPU: 0
> EIP: 0060:[<c010fdd7>] Not tainted VLI
> EFLAGS: 00010082 (2.6.19-rc3-mm1 #1)
> EIP is at change_page_attr+0x167/0x234
> eax: 1fc001e3 ebx: c1009c80 ecx: dfc20000 edx: c04e4dfc
> esi: 1fc20000 edi: e0820000 ebp: 00000005 esp: dffc5e7c
> ds: 007b es: 007b ss: 0068
> Process swapper (pid: 1, ti=dffc4000 task=dffc3530 task.ti=dffc4000)
> Stack: 00000011 c13f8400 00000010 00000292 c04e4dfc dfc20000 00000163 00000163
> c13f8200 dfe66984 e0820000 00000005 c010fab8 c03ee740 c03ee740 dfe2334c
> 00000004 e080f000 c0289195 dfe2334c dfe2334c e080f000 c02881f6 fffffffb
> Call Trace:
> [<c010fab8>] iounmap+0xaa/0xdc
> [<00000004>] 0x4
> =======================
> Code: 84 b7 00 00 00 eb d2 ff 43 0c eb 23 84 c0 78 1b 0b 74 24 1c 8b 54 24 10 89 32 8b 43 0c 85 c0 75 04 0f 0b eb fe 48 89 43 0c eb 04 <0f> 0b eb fe 8b 03 f6 c4 04 75 6c f6 05 0c 7c 45 c0 08 74 63 83
> EIP: [<c010fdd7>] change_page_attr+0x167/0x234 SS:ESP 0068:dffc5e7c
> <0>Kernel panic - not syncing: Attempted to kill init!
I'd be suspecting x86_64-mm-i386-clflush-size.patch and
x86_64-mm-i386-cpa-clflush.patch. Because x86_64-mm-cpa-clflush.patch made
my x86_64 box instacrash in a similar manner, so I reverted that.
below is a ptch which reverts x86_64-mm-i386-clflush-size.patch and
x86_64-mm-i386-cpa-clflush.patch. Can you test it please?
arch/i386/kernel/cpu/common.c | 3 ---
arch/i386/kernel/cpu/proc.c | 3 +--
arch/i386/mm/pageattr.c | 24 +++++++-----------------
include/asm-i386/cpufeature.h | 1 -
include/asm-i386/processor.h | 1 -
5 files changed, 8 insertions(+), 24 deletions(-)
diff -puN arch/i386/mm/pageattr.c~revert-x86_64-mm-i386-cpa-clflush arch/i386/mm/pageattr.c
--- a/arch/i386/mm/pageattr.c~revert-x86_64-mm-i386-cpa-clflush
+++ a/arch/i386/mm/pageattr.c
@@ -67,17 +67,11 @@ static struct page *split_large_page(uns
return base;
}
-static void flush_kernel_map(void *arg)
+static void flush_kernel_map(void *dummy)
{
- unsigned long adr = (unsigned long)arg;
-
- if (adr && cpu_has_clflush) {
- int i;
- for (i = 0; i < PAGE_SIZE; i += boot_cpu_data.x86_clflush_size)
- asm volatile("clflush (%0)" :: "r" (adr + i));
- } else if (boot_cpu_data.x86_model >= 4)
+ /* Could use CLFLUSH here if the CPU supports it (Hammer,P4) */
+ if (boot_cpu_data.x86_model >= 4)
wbinvd();
-
/* Flush all to work around Errata in early athlons regarding
* large page flushing.
*/
@@ -179,9 +173,9 @@ __change_page_attr(struct page *page, pg
return 0;
}
-static inline void flush_map(void *adr)
+static inline void flush_map(void)
{
- on_each_cpu(flush_kernel_map, adr, 1, 1);
+ on_each_cpu(flush_kernel_map, NULL, 1, 1);
}
/*
@@ -223,13 +217,9 @@ void global_flush_tlb(void)
spin_lock_irq(&cpa_lock);
list_replace_init(&df_list, &l);
spin_unlock_irq(&cpa_lock);
- if (!cpu_has_clflush)
- flush_map(0);
- list_for_each_entry_safe(pg, next, &l, lru) {
- if (cpu_has_clflush)
- flush_map(page_address(pg));
+ flush_map();
+ list_for_each_entry_safe(pg, next, &l, lru)
__free_page(pg);
- }
}
#ifdef CONFIG_DEBUG_PAGEALLOC
diff -puN include/asm-i386/cpufeature.h~revert-x86_64-mm-i386-cpa-clflush include/asm-i386/cpufeature.h
--- a/include/asm-i386/cpufeature.h~revert-x86_64-mm-i386-cpa-clflush
+++ a/include/asm-i386/cpufeature.h
@@ -137,7 +137,6 @@
#define cpu_has_pmm_enabled boot_cpu_has(X86_FEATURE_PMM_EN)
#define cpu_has_ds boot_cpu_has(X86_FEATURE_DS)
#define cpu_has_pebs boot_cpu_has(X86_FEATURE_PEBS)
-#define cpu_has_clflush boot_cpu_has(X86_FEATURE_CLFLSH)
#endif /* __ASM_I386_CPUFEATURE_H */
diff -puN arch/i386/kernel/cpu/common.c~revert-x86_64-mm-i386-cpa-clflush arch/i386/kernel/cpu/common.c
--- a/arch/i386/kernel/cpu/common.c~revert-x86_64-mm-i386-cpa-clflush
+++ a/arch/i386/kernel/cpu/common.c
@@ -314,8 +314,6 @@ static void __cpuinit generic_identify(s
#else
c->apicid = (ebx >> 24) & 0xFF;
#endif
- if (c->x86_capability[0] & (1<<19))
- c->x86_clflush_size = ((ebx >> 8) & 0xff) * 8;
} else {
/* Have CPUID level 0 only - unheard of */
c->x86 = 4;
@@ -380,7 +378,6 @@ void __cpuinit identify_cpu(struct cpuin
c->x86_vendor_id[0] = '\0'; /* Unset */
c->x86_model_id[0] = '\0'; /* Unset */
c->x86_max_cores = 1;
- c->x86_clflush_size = 32;
memset(&c->x86_capability, 0, sizeof c->x86_capability);
if (!have_cpuid_p()) {
diff -puN arch/i386/kernel/cpu/proc.c~revert-x86_64-mm-i386-cpa-clflush arch/i386/kernel/cpu/proc.c
--- a/arch/i386/kernel/cpu/proc.c~revert-x86_64-mm-i386-cpa-clflush
+++ a/arch/i386/kernel/cpu/proc.c
@@ -152,10 +152,9 @@ static int show_cpuinfo(struct seq_file
seq_printf(m, " [%d]", i);
}
- seq_printf(m, "\nbogomips\t: %lu.%02lu\n",
+ seq_printf(m, "\nbogomips\t: %lu.%02lu\n\n",
c->loops_per_jiffy/(500000/HZ),
(c->loops_per_jiffy/(5000/HZ)) % 100);
- seq_printf(m, "clflush size\t: %u\n\n", c->x86_clflush_size);
return 0;
}
diff -puN include/asm-i386/processor.h~revert-x86_64-mm-i386-cpa-clflush include/asm-i386/processor.h
--- a/include/asm-i386/processor.h~revert-x86_64-mm-i386-cpa-clflush
+++ a/include/asm-i386/processor.h
@@ -73,7 +73,6 @@ struct cpuinfo_x86 {
#endif
unsigned char x86_max_cores; /* cpuid returned max cores value */
unsigned char apicid;
- unsigned short x86_clflush_size;
#ifdef CONFIG_SMP
unsigned char booted_cores; /* number of cores as seen by OS */
__u8 phys_proc_id; /* Physical processor id. */
_
On Monday 30 October 2006 21:04, Andrew Morton wrote:
> On Mon, 30 Oct 2006 20:26:24 -0500
> Andrew James Wade <[email protected]> wrote:
>
> > I got the BUG below while booting. -rc2-mm2 worked fine, but with a
> > different .config. I'm going to try and narrow this down further.
> >
> > cheers,
> > Andrew Wade
> >
> > agpgart: Detected VIA KT266/KY266x/KT333 chipset
> > agpgart: unable to get minor: 175
> > agpgart: agp_frontend_initialize() failed.
> > ------------[ cut here ]------------
> > kernel BUG at arch/i386/mm/pageattr.c:165!
> > invalid opcode: 0000 [#1]
> > last sysfs file:
> > CPU: 0
> > EIP: 0060:[<c010fdd7>] Not tainted VLI
> > EFLAGS: 00010082 (2.6.19-rc3-mm1 #1)
> > EIP is at change_page_attr+0x167/0x234
> > eax: 1fc001e3 ebx: c1009c80 ecx: dfc20000 edx: c04e4dfc
> > esi: 1fc20000 edi: e0820000 ebp: 00000005 esp: dffc5e7c
> > ds: 007b es: 007b ss: 0068
> > Process swapper (pid: 1, ti=dffc4000 task=dffc3530 task.ti=dffc4000)
> > Stack: 00000011 c13f8400 00000010 00000292 c04e4dfc dfc20000 00000163 00000163
> > c13f8200 dfe66984 e0820000 00000005 c010fab8 c03ee740 c03ee740 dfe2334c
> > 00000004 e080f000 c0289195 dfe2334c dfe2334c e080f000 c02881f6 fffffffb
> > Call Trace:
> > [<c010fab8>] iounmap+0xaa/0xdc
> > [<00000004>] 0x4
> > =======================
> > Code: 84 b7 00 00 00 eb d2 ff 43 0c eb 23 84 c0 78 1b 0b 74 24 1c 8b 54 24 10 89 32 8b 43 0c 85 c0 75 04 0f 0b eb fe 48 89 43 0c eb 04 <0f> 0b eb fe 8b 03 f6 c4 04 75 6c f6 05 0c 7c 45 c0 08 74 63 83
> > EIP: [<c010fdd7>] change_page_attr+0x167/0x234 SS:ESP 0068:dffc5e7c
> > <0>Kernel panic - not syncing: Attempted to kill init!
>
> I'd be suspecting x86_64-mm-i386-clflush-size.patch and
> x86_64-mm-i386-cpa-clflush.patch. Because x86_64-mm-cpa-clflush.patch made
> my x86_64 box instacrash in a similar manner, so I reverted that.
>
> below is a ptch which reverts x86_64-mm-i386-clflush-size.patch and
> x86_64-mm-i386-cpa-clflush.patch. Can you test it please?
Same crash I'm afraid.
However, I was too aggressive in trimming the kernel log: there are
some earlier errors:
Unable to create device for VGA+; errno = -17
...
Unable to create device for frame buffer device; errno = -17
Hope this helps.
On Mon, 30 Oct 2006 22:03:36 -0500
Andrew James Wade <[email protected]> wrote:
> On Monday 30 October 2006 21:04, Andrew Morton wrote:
> > On Mon, 30 Oct 2006 20:26:24 -0500
> > Andrew James Wade <[email protected]> wrote:
> >
> > > I got the BUG below while booting. -rc2-mm2 worked fine, but with a
> > > different .config. I'm going to try and narrow this down further.
> > >
> > > cheers,
> > > Andrew Wade
> > >
> > > agpgart: Detected VIA KT266/KY266x/KT333 chipset
> > > agpgart: unable to get minor: 175
> > > agpgart: agp_frontend_initialize() failed.
> > > ------------[ cut here ]------------
> > > kernel BUG at arch/i386/mm/pageattr.c:165!
> > > invalid opcode: 0000 [#1]
> > > last sysfs file:
> > > CPU: 0
> > > EIP: 0060:[<c010fdd7>] Not tainted VLI
> > > EFLAGS: 00010082 (2.6.19-rc3-mm1 #1)
> > > EIP is at change_page_attr+0x167/0x234
> > > eax: 1fc001e3 ebx: c1009c80 ecx: dfc20000 edx: c04e4dfc
> > > esi: 1fc20000 edi: e0820000 ebp: 00000005 esp: dffc5e7c
> > > ds: 007b es: 007b ss: 0068
> > > Process swapper (pid: 1, ti=dffc4000 task=dffc3530 task.ti=dffc4000)
> > > Stack: 00000011 c13f8400 00000010 00000292 c04e4dfc dfc20000 00000163 00000163
> > > c13f8200 dfe66984 e0820000 00000005 c010fab8 c03ee740 c03ee740 dfe2334c
> > > 00000004 e080f000 c0289195 dfe2334c dfe2334c e080f000 c02881f6 fffffffb
> > > Call Trace:
> > > [<c010fab8>] iounmap+0xaa/0xdc
> > > [<00000004>] 0x4
> > > =======================
> > > Code: 84 b7 00 00 00 eb d2 ff 43 0c eb 23 84 c0 78 1b 0b 74 24 1c 8b 54 24 10 89 32 8b 43 0c 85 c0 75 04 0f 0b eb fe 48 89 43 0c eb 04 <0f> 0b eb fe 8b 03 f6 c4 04 75 6c f6 05 0c 7c 45 c0 08 74 63 83
> > > EIP: [<c010fdd7>] change_page_attr+0x167/0x234 SS:ESP 0068:dffc5e7c
> > > <0>Kernel panic - not syncing: Attempted to kill init!
> >
> > I'd be suspecting x86_64-mm-i386-clflush-size.patch and
> > x86_64-mm-i386-cpa-clflush.patch. Because x86_64-mm-cpa-clflush.patch made
> > my x86_64 box instacrash in a similar manner, so I reverted that.
> >
> > below is a ptch which reverts x86_64-mm-i386-clflush-size.patch and
> > x86_64-mm-i386-cpa-clflush.patch. Can you test it please?
>
> Same crash I'm afraid.
hm. Please send the .config
> However, I was too aggressive in trimming the kernel log: there are
> some earlier errors:
> Unable to create device for VGA+; errno = -17
> ...
> Unable to create device for frame buffer device; errno = -17
>
> Hope this helps.
argh. Greg, I'm not sure that work is ready for prime-time.
On Monday 30 October 2006 22:13, Andrew Morton wrote:
> On Mon, 30 Oct 2006 22:03:36 -0500
> Andrew James Wade <[email protected]> wrote:
>
> > On Monday 30 October 2006 21:04, Andrew Morton wrote:
> > > On Mon, 30 Oct 2006 20:26:24 -0500
> > > Andrew James Wade <[email protected]> wrote:
> > >
> > > > I got the BUG below while booting. -rc2-mm2 worked fine, but with a
> > > > different .config. I'm going to try and narrow this down further.
> > > >
> > > > cheers,
> > > > Andrew Wade
> > > >
> > > > agpgart: Detected VIA KT266/KY266x/KT333 chipset
> > > > agpgart: unable to get minor: 175
> > > > agpgart: agp_frontend_initialize() failed.
> > > > ------------[ cut here ]------------
> > > > kernel BUG at arch/i386/mm/pageattr.c:165!
> > > > invalid opcode: 0000 [#1]
> > > > last sysfs file:
> > > > CPU: 0
> > > > EIP: 0060:[<c010fdd7>] Not tainted VLI
> > > > EFLAGS: 00010082 (2.6.19-rc3-mm1 #1)
> > > > EIP is at change_page_attr+0x167/0x234
> > > > eax: 1fc001e3 ebx: c1009c80 ecx: dfc20000 edx: c04e4dfc
> > > > esi: 1fc20000 edi: e0820000 ebp: 00000005 esp: dffc5e7c
> > > > ds: 007b es: 007b ss: 0068
> > > > Process swapper (pid: 1, ti=dffc4000 task=dffc3530 task.ti=dffc4000)
> > > > Stack: 00000011 c13f8400 00000010 00000292 c04e4dfc dfc20000 00000163 00000163
> > > > c13f8200 dfe66984 e0820000 00000005 c010fab8 c03ee740 c03ee740 dfe2334c
> > > > 00000004 e080f000 c0289195 dfe2334c dfe2334c e080f000 c02881f6 fffffffb
> > > > Call Trace:
> > > > [<c010fab8>] iounmap+0xaa/0xdc
> > > > [<00000004>] 0x4
> > > > =======================
> > > > Code: 84 b7 00 00 00 eb d2 ff 43 0c eb 23 84 c0 78 1b 0b 74 24 1c 8b 54 24 10 89 32 8b 43 0c 85 c0 75 04 0f 0b eb fe 48 89 43 0c eb 04 <0f> 0b eb fe 8b 03 f6 c4 04 75 6c f6 05 0c 7c 45 c0 08 74 63 83
> > > > EIP: [<c010fdd7>] change_page_attr+0x167/0x234 SS:ESP 0068:dffc5e7c
> > > > <0>Kernel panic - not syncing: Attempted to kill init!
> > >
> > > I'd be suspecting x86_64-mm-i386-clflush-size.patch and
> > > x86_64-mm-i386-cpa-clflush.patch. Because x86_64-mm-cpa-clflush.patch made
> > > my x86_64 box instacrash in a similar manner, so I reverted that.
> > >
> > > below is a ptch which reverts x86_64-mm-i386-clflush-size.patch and
> > > x86_64-mm-i386-cpa-clflush.patch. Can you test it please?
> >
> > Same crash I'm afraid.
>
> hm. Please send the .config
>
Sure.
I've just found out that unsetting CONFIG_SYSFS_DEPRECATED makes the
crash go away. I can hack around the resulting udev incompatibility.
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.19-rc3-mm1
# Mon Oct 30 19:31:03 2006
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=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_BROKEN_ON_SMP=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_UTS_NS is not set
# CONFIG_AUDIT is not set
# CONFIG_KEVENT is not set
# CONFIG_IKCONFIG is not set
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_RELAY is not set
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_SLAB=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set
#
# Loadable module support
#
# CONFIG_MODULES is not set
#
# Block layer
#
CONFIG_BLOCK=y
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
#
# Processor type and features
#
# CONFIG_HIGH_RES_TIMERS is not set
# CONFIG_SMP is not set
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
CONFIG_X86_TSC=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
# CONFIG_X86_MCE_P4THERMAL is not set
CONFIG_VM86=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_X86_REBOOTFIXUPS is not set
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_ADAPTIVE_READAHEAD=y
CONFIG_READAHEAD_ALLOW_OVERHEADS=y
CONFIG_DEBUG_READAHEAD=y
CONFIG_READAHEAD_HIT_FEEDBACK=y
CONFIG_READAHEAD_SMOOTH_AGING=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_REGPARM=y
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
# CONFIG_KEXEC is not set
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
# CONFIG_COMPAT_VDSO is not set
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_LEGACY is not set
# CONFIG_PM_DEBUG is not set
# CONFIG_PM_SYSFS_DEPRECATED is not set
# CONFIG_SOFTWARE_SUSPEND is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
# CONFIG_ACPI_SLEEP is not set
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=y
# CONFIG_ACPI_HOTKEY is not set
# CONFIG_ACPI_FAN is not set
# CONFIG_ACPI_DOCK is not set
# CONFIG_ACPI_BAY is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS 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 is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set
# CONFIG_ACPI_SBS is not set
#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCIEPORTBUS is not set
CONFIG_PCI_MSI=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_HT_IRQ is not set
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set
#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=y
#
# Networking
#
CONFIG_NET=y
#
# Networking options
#
# CONFIG_NETDEBUG is not set
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_NETWORK_SECMARK is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=y
CONFIG_NETFILTER_NETLINK_QUEUE=y
# CONFIG_NETFILTER_NETLINK_LOG is not set
# CONFIG_NF_CONNTRACK is not set
CONFIG_NETFILTER_XTABLES=y
# CONFIG_NETFILTER_XT_TARGET_CLASSIFY is not set
# CONFIG_NETFILTER_XT_TARGET_MARK is not set
# CONFIG_NETFILTER_XT_TARGET_NFQUEUE is not set
# CONFIG_NETFILTER_XT_MATCH_COMMENT is not set
# CONFIG_NETFILTER_XT_MATCH_DCCP is not set
# CONFIG_NETFILTER_XT_MATCH_DSCP is not set
# CONFIG_NETFILTER_XT_MATCH_ESP is not set
# CONFIG_NETFILTER_XT_MATCH_LENGTH is not set
# CONFIG_NETFILTER_XT_MATCH_LIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_MAC is not set
# CONFIG_NETFILTER_XT_MATCH_MARK is not set
# CONFIG_NETFILTER_XT_MATCH_POLICY is not set
# CONFIG_NETFILTER_XT_MATCH_MULTIPORT is not set
# CONFIG_NETFILTER_XT_MATCH_PKTTYPE is not set
# CONFIG_NETFILTER_XT_MATCH_QUOTA is not set
# CONFIG_NETFILTER_XT_MATCH_REALM is not set
# CONFIG_NETFILTER_XT_MATCH_SCTP is not set
# CONFIG_NETFILTER_XT_MATCH_STATISTIC is not set
# CONFIG_NETFILTER_XT_MATCH_STRING is not set
# CONFIG_NETFILTER_XT_MATCH_TCPMSS is not set
#
# IP: Netfilter Configuration
#
# CONFIG_IP_NF_CONNTRACK is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=y
# CONFIG_IP_NF_MATCH_IPRANGE is not set
# CONFIG_IP_NF_MATCH_TOS is not set
CONFIG_IP_NF_MATCH_RECENT=y
# CONFIG_IP_NF_MATCH_ECN is not set
# CONFIG_IP_NF_MATCH_AH is not set
# CONFIG_IP_NF_MATCH_TTL is not set
# CONFIG_IP_NF_MATCH_OWNER is not set
# CONFIG_IP_NF_MATCH_ADDRTYPE is not set
# CONFIG_IP_NF_MATCH_HASHLIMIT is not set
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
# CONFIG_IP_NF_TARGET_LOG is not set
# CONFIG_IP_NF_TARGET_ULOG is not set
CONFIG_IP_NF_TARGET_TCPMSS=y
# CONFIG_IP_NF_MANGLE is not set
# CONFIG_IP_NF_RAW is not set
# CONFIG_IP_NF_ARPTABLES is not set
#
# DCCP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
#
# TIPC Configuration (EXPERIMENTAL)
#
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_IEEE80211 is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FW_LOADER is not set
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_SYS_HYPERVISOR is not set
#
# Connector - unified userspace <-> kernelspace linker
#
# CONFIG_CONNECTOR is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set
#
# Protocols
#
CONFIG_PNPACPI=y
#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=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 is not set
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
#
# Misc devices
#
# CONFIG_IBM_ASM is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
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=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=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 is not set
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_CS5535 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 is not set
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
# CONFIG_SCSI_PROC_FS is not set
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
#
# SCSI low-level drivers
#
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
#
# Serial ATA (prod) and Parallel ATA (experimental) drivers
#
# CONFIG_ATA is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Network device support
#
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
#
# PHY device support
#
# CONFIG_PHYLIB is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=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=y
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_SK98LIN is not set
# CONFIG_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
# CONFIG_NETXEN_NIC is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1280
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1024
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
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 is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_INTEL is not set
# CONFIG_HW_RANDOM_AMD is not set
# CONFIG_HW_RANDOM_GEODE is not set
CONFIG_HW_RANDOM_VIA=y
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
CONFIG_AGP_VIA=y
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=y
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_GPIO is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
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_LIGHT is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
CONFIG_I2C_VIAPRO=y
# 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=y
# 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_K8TEMP is not set
CONFIG_SENSORS_ASB100=y
# 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_PC87427 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_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
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
# CONFIG_USB_DABUSB is not set
#
# Graphics support
#
CONFIG_FIRMWARE_EDID=y
CONFIG_FB=y
CONFIG_FB_DDC=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 is not set
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA 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_I810 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
CONFIG_FB_RADEON=y
CONFIG_FB_RADEON_I2C=y
# CONFIG_FB_RADEON_DEBUG is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_CYBLA is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
# CONFIG_VIDEO_SELECT is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
CONFIG_FONTS=y
# CONFIG_FONT_8x8 is not set
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_7x14 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set
# CONFIG_FONT_10x18 is not set
#
# 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_HWDEP=y
CONFIG_SND_RAWMIDI=y
# CONFIG_SND_SEQUENCER is not set
# CONFIG_SND_MIXER_OSS is not set
# CONFIG_SND_PCM_OSS is not set
CONFIG_SND_RTCTIMER=y
# CONFIG_SND_DYNAMIC_MINORS is not set
# CONFIG_SND_SUPPORT_OLD_API is not set
# CONFIG_SND_VERBOSE_PROCFS is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
CONFIG_SND_MPU401_UART=y
CONFIG_SND_OPL3_LIB=y
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
#
# PCI devices
#
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
CONFIG_SND_CMIPCI=y
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5535AUDIO is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_HDA_INTEL is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 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
#
# SoC audio support
#
# CONFIG_SND_SOC 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 is not set
#
# 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_MULTITHREAD_PROBE is not set
# CONFIG_USB_OTG is not set
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=y
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#
#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=y
# 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_STORAGE_KARMA is not set
# CONFIG_USB_LIBUSUAL is not set
#
# USB Input Devices
#
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_ACECAD is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_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 is not set
#
# USB port drivers
#
#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GOTEMP is not set
#
# USB DSL modem support
#
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# MMC/SD Card support
#
# CONFIG_MMC is not set
#
# LED devices
#
# CONFIG_NEW_LEDS is not set
#
# LED drivers
#
#
# LED Triggers
#
#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set
#
# EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
#
# CONFIG_EDAC is not set
#
# Real Time Clock
#
# CONFIG_RTC_CLASS is not set
#
# DMA Engine support
#
# CONFIG_DMA_ENGINE is not set
#
# DMA Clients
#
#
# DMA Devices
#
#
# Userspace I/O
#
# CONFIG_UIO is not set
#
# Auxiliary Display support
#
#
# File systems
#
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
# CONFIG_EXT4DEV_FS is not set
CONFIG_REISER4_FS=y
# CONFIG_REISER4_DEBUG is not set
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set
#
# Caches
#
# CONFIG_CACHEFILES is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y
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 is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_RAMFS=y
# CONFIG_CONFIGFS_FS is not set
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFS_FSCACHE is not set
# CONFIG_NFSD is not set
# CONFIG_SMB_FS is not set
CONFIG_CIFS=y
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
# CONFIG_AFS_FSCACHE is not set
# CONFIG_9P_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="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 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ASCII=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 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
#
# Instrumentation Support
#
CONFIG_PROFILING=y
CONFIG_OPROFILE=y
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_PAGE_OWNER is not set
CONFIG_DEBUG_FS=y
CONFIG_UNWIND_INFO=y
CONFIG_STACK_UNWIND=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_LOG_BUF_SHIFT=18
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_SCHEDSTATS=y
# CONFIG_TIMER_STATS is not set
CONFIG_DEBUG_SLAB=y
# CONFIG_DEBUG_SLAB_LEAK is not set
CONFIG_DEBUG_RT_MUTEXES=y
CONFIG_DEBUG_PI_LIST=y
# CONFIG_RT_MUTEX_TESTER is not set
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_RWSEMS=y
CONFIG_DEBUG_LOCK_ALLOC=y
CONFIG_PROVE_LOCKING=y
CONFIG_LOCKDEP=y
CONFIG_DEBUG_LOCKDEP=y
CONFIG_TRACE_IRQFLAGS=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
CONFIG_DEBUG_VM=y
CONFIG_DEBUG_LIST=y
# CONFIG_FRAME_POINTER 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_EARLY_PRINTK=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_STACK_USAGE=y
CONFIG_DEBUG_RODATA=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_INTEGRITY is not set
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
CONFIG_CRYPTO=y
# CONFIG_CRYPTO_MANAGER is not set
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_ECB is not set
# CONFIG_CRYPTO_CBC is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_586 is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_AES_586 is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CAMELLIA is not set
#
# Hardware crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set
# CONFIG_CRYPTO_DEV_GEODE is not set
#
# Library routines
#
CONFIG_BITREVERSE=y
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
CONFIG_CRC32=y
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_PLIST=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_KTIME_SCALAR=y
On Mon, 30 Oct 2006 22:58:11 -0500
Andrew James Wade <[email protected]> wrote:
> I've just found out that unsetting CONFIG_SYSFS_DEPRECATED makes the
> crash go away.
How bizarre. sysfs changes cause unexpected pte protection values?
> I can hack around the resulting udev incompatibility.
ok..
On Mon, Oct 30, 2006 at 08:11:23PM -0800, Andrew Morton wrote:
> On Mon, 30 Oct 2006 22:58:11 -0500
> Andrew James Wade <[email protected]> wrote:
>
> > I've just found out that unsetting CONFIG_SYSFS_DEPRECATED makes the
> > crash go away.
>
> How bizarre. sysfs changes cause unexpected pte protection values?
That's just wrong. Something odd is happening here. Can you try to
bisect things to determine the patch that is causing the problem?
thanks,
greg k-h
On Mon, 30 Oct 2006 22:58:11 -0500
Andrew James Wade <[email protected]> wrote:
> >
> > hm. Please send the .config
> >
> Sure.
>
> I've just found out that unsetting CONFIG_SYSFS_DEPRECATED makes the
> crash go away. I can hack around the resulting udev incompatibility.
>
> #
> # Automatically generated make config: don't edit
> # Linux kernel version: 2.6.19-rc3-mm1
> # Mon Oct 30 19:31:03 2006
Well I tried to reproduce this, but I got such a psychedelic cornucopia of
oopses at various bisection points amongst those sysfs patches that I think
I'll just give up.
Greg, Kay: it's quite ugly. I'll drop all those patches for now, and I
suggest you do so too. Have a play with the .config which Andrew sent..
On Monday 30 October 2006 23:20, Greg KH wrote:
> On Mon, Oct 30, 2006 at 08:11:23PM -0800, Andrew Morton wrote:
> > On Mon, 30 Oct 2006 22:58:11 -0500
> > Andrew James Wade <[email protected]> wrote:
> >
> > > I've just found out that unsetting CONFIG_SYSFS_DEPRECATED makes the
> > > crash go away.
> >
> > How bizarre. sysfs changes cause unexpected pte protection values?
Perhaps one of the drivers is responding badly to device_create
failing? (-EEXIST, if I'm not mistaken).
>
> That's just wrong. Something odd is happening here. Can you try to
> bisect things to determine the patch that is causing the problem?
Sure.
Andrew Wade
On Monday, 30 October 2006 21:57, Greg KH wrote:
> On Mon, Oct 30, 2006 at 09:48:33PM +0100, Rafael J. Wysocki wrote:
> > On Monday, 30 October 2006 21:22, Greg KH wrote:
> > > On Mon, Oct 30, 2006 at 09:15:37PM +0100, Rafael J. Wysocki wrote:
> > > > Sorry, I was wrong.
> > > >
> > > > The controller _is_ detected and handled properly, but udev is apparently
> > > > unable to create the special device files for SATA drives/partitions even
> > > > though CONFIG_SYSFS_DEPRECATED is set.
> > >
> > > This config option should not affect the block device sysfs files at all
> > > at this point in time.
> > >
> > > What does 'tree /sys/block/' show?
> >
> > I can't run 'tree', but 'ls' works somehow (can't mount the root fs). The
> > block device sysfs files seem to be present
>
> If they are there, then udev should work just fine.
>
> > > If the files show up there properly, udev should handle them just fine.
> >
> > It doesn't.
> >
> > Well, I can binary search for the offending patch if that helps.
>
> That would be very helpful, thanks.
It's one of these:
git-acpi.patch
git-acpi-fixup.patch
git-acpi-more-build-fixes.patch
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
On Mon, 2006-10-30 at 21:14 +0100, Cornelia Huck wrote:
> Maybe the initscripts have problems coping with the new layout
> (symlinks instead of real devices)?
SuSE's /sbin/getcfg for one uses libsysfs, which apparently doesn't
follow symlinks (bounces off symlink and does nutty stuff instead). If
any of the boxen you're having troubles with use libsysfs in their init
stuff, that's likely the problem.
-Mike
On Mon, 2006-10-30 at 21:10 -0800, Andrew Morton wrote:
> On Mon, 30 Oct 2006 22:58:11 -0500
> Andrew James Wade <[email protected]> wrote:
>
> > >
> > > hm. Please send the .config
> > >
> > Sure.
> >
> > I've just found out that unsetting CONFIG_SYSFS_DEPRECATED makes the
> > crash go away. I can hack around the resulting udev incompatibility.
> >
> > #
> > # Automatically generated make config: don't edit
> > # Linux kernel version: 2.6.19-rc3-mm1
> > # Mon Oct 30 19:31:03 2006
>
> Well I tried to reproduce this, but I got such a psychedelic cornucopia of
> oopses at various bisection points amongst those sysfs patches that I think
> I'll just give up.
>
> Greg, Kay: it's quite ugly. I'll drop all those patches for now, and I
> suggest you do so too. Have a play with the .config which Andrew sent..
I can reproduce, and confirm that nuking CONFIG_SYSFS_DEPRECATED does
cure it. Without that, my box boots fine.
('course being SuSE, the sysfs symlink changes makes my network init
scripts unable to find config for network devices, but that's known)
Linux version 2.6.19-rc3-mm1-smp (root@Homer) (gcc version 4.1.2 20060920 (prerelease) (SUSE Linux)) #10 SMP PREEMPT Tue Oct 31 06:42:45 CET 2006
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end: 000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end: 00000000000a0000 type: 2
copy_e820_map() start: 00000000000f0000 size: 0000000000010000 end: 0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 000000003fef0000 end: 000000003fff0000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000003fff0000 size: 0000000000003000 end: 000000003fff3000 type: 4
copy_e820_map() start: 000000003fff3000 size: 000000000000d000 end: 0000000040000000 type: 3
copy_e820_map() start: 00000000fec00000 size: 0000000001400000 end: 0000000100000000 type: 2
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
127MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000f5320
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 229376
HighMem 229376 -> 262128
early_node_map[1] active PFN ranges
0: 0 -> 262128
DMI 2.3 present.
ACPI: RSDP @ 0x000f6cc0/0x0014 (v000 IntelR)
ACPI: RSDT @ 0x3fff3000/0x002C (v001 IntelR AWRDACPI 0x42302E31 AWRD 0x00000000)
ACPI: FACP @ 0x3fff3040/0x0074 (v001 IntelR AWRDACPI 0x42302E31 AWRD 0x00000000)
ACPI: DSDT @ 0x3fff30c0/0x4139 (v001 INTELR AWRDACPI 0x00001000 MSFT 0x0100000E)
ACPI: FACS @ 0x3fff0000/0x0040
ACPI: APIC @ 0x3fff7200/0x0068 (v001 IntelR AWRDACPI 0x42302E31 AWRD 0x00000000)
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:2 APIC version 20
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1 15:2 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
Detected 2992.575 MHz processor.
Built 1 zonelists. Total pages: 260081
Kernel command line: root=/dev/hdc3 vga=0x314 resume=/dev/hdc2 console=ttyS0,115200n8 console=tty profile=1
kernel profiling enabled (shift: 1)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Clock event device pit configured with caps set: 07
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1021228k/1048512k available (4012k kernel code, 26564k reserved, 1327k data, 224k init, 131008k highmem)
virtual kernel memory layout:
fixmap : 0xfff9d000 - 0xfffff000 ( 392 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB)
lowmem : 0xc0000000 - 0xf8000000 ( 896 MB)
.init : 0xc06d2000 - 0xc070a000 ( 224 kB)
.data : 0xc04eb234 - 0xc0636f1c (1327 kB)
.text : 0xc0100000 - 0xc04eb234 (4012 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 5987.35 BogoMIPS (lpj=2993678)
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Physical Processor ID: 0
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU0: Thermal monitoring enabled
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
ACPI: Core revision 20061011
CPU0: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 09
SMP alternatives: switching to SMP code
Booting processor 1/1 eip 3000
Initializing CPU#1
Calibrating delay using timer specific routine.. 5984.16 BogoMIPS (lpj=2992081)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Physical Processor ID: 0
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel P4/Xeon Extended MCE MSRs (12) available
CPU1: Thermal monitoring enabled
CPU1: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 09
Total of 2 processors activated (11971.51 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
Clock event device pit new caps set: 01
Clock event device lapic configured with caps set: 06
checking TSC synchronization across 2 CPUs: passed.
Clock event device pit new caps set: 01
Clock event device lapic configured with caps set: 06
Brought up 2 CPUs
migration_cost=83
Unpacking initramfs... done
Freeing initrd memory: 2693k freed
NET: Registered protocol family 16
Unable to create device for dummy device; errno = -17
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfb980, last bus=2
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI quirk: region 0400-047f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 0480-04bf claimed by ICH4 GPIO
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 *5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK1] (IRQs *3 4 5 7 9 10 11 12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 13 devices
intel_rng: FWH not detected
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
FS-Cache: Loaded
CacheFiles: Loaded
pnp: 00:0b: ioport range 0x400-0x4bf could not be reserved
PCI: Bridge: 0000:00:01.0
IO window: a000-afff
MEM window: e8000000-e9ffffff
PREFETCH window: d8000000-e7ffffff
PCI: Bridge: 0000:00:1e.0
IO window: b000-bfff
MEM window: ea000000-ea0fffff
PREFETCH window: ea100000-ea1fffff
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1572864 bytes)
TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Machine check exception polling timer started.
audit: initializing netlink socket (disabled)
audit(1162278006.581:1): initialized
Failed to register kevent miscdev: err=-17.
KEVENT: Added callbacks for type 2.
KEVENT: Added callbacks for type 3.
Kevent poll()/select() subsystem has been initialized.
KEVENT: Added callbacks for type 0.
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
FS-Cache: netfs 'nfs' registered for caching
Installing knfsd (copyright (C) 1996 [email protected]).
NTFS driver 2.1.27 [Flags: R/W].
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
vesafb: framebuffer at 0xd8000000, mapped to 0xf8880000, using 1875k, total 16384k
vesafb: mode is 800x600x16, linelength=1600, pages=16
vesafb: protected mode interface info at c000:b544
vesafb: pmi: set display start = c00cb5d2, set palette = c00cb612
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Unable to create device for frame buffer device; errno = -17
Console: switching to colour frame buffer device 100x37
fb0: VESA VGA frame buffer device
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [PWRB]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Fan [FAN] (on)
Using specific hotkey driver
ACPI: Thermal Zone [THRM] (40 C)
nvram: can't misc_register on minor=144
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 865 Chipset.
agpgart: unable to get minor: 175
agpgart: agp_frontend_initialize() failed.
------------[ cut here ]------------
kernel BUG at arch/i386/mm/pageattr.c:165!
invalid opcode: 0000 [#1]
PREEMPT SMP
last sysfs file:
Modules linked in:
CPU: 0
EIP: 0060:[<c011b2ed>] Not tainted VLI
EFLAGS: 00010082 (2.6.19-rc3-mm1-smp #10)
EIP is at change_page_attr+0x2a8/0x2ac
eax: c070af7c ebx: dffbe380 ecx: 00000163 edx: c1000000
esi: f8a80000 edi: c16fa000 ebp: dfd01e30 esp: dfd01df8
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, ti=dfd00000 task=c20eea90 task.ti=dfd00000)
Stack: 00000041 c16fa800 00000040 00000202 c100e140 f7d40000 c070af7c 00000163
00000163 00000001 00000000 dffbe380 f8a80000 c16fa000 dfd01e4c c011adfd
000000b4 00000000 00040000 dffb78c0 dffb78c0 dfd01e64 c034b9a6 00000006
Call Trace:
[<c011adfd>] iounmap+0xcd/0xd8
[<c034b9a6>] agp_generic_free_gatt_table+0x34/0xce
[<c034a4d5>] agp_backend_cleanup+0x20/0x55
[<c034a931>] agp_add_bridge+0x32a/0x3c9
[<c034e8db>] agp_intel_probe+0x17c/0x65c
[<c02e25ae>] pci_device_probe+0x44/0x5f
[<c0363274>] driver_probe_device+0x6c/0x132
[<c0363442>] __driver_attach+0x84/0x86
[<c0362853>] bus_for_each_dev+0x40/0x5e
[<c0363130>] driver_attach+0x19/0x1b
[<c0362b7a>] bus_add_driver+0x6a/0x185
[<c0363699>] driver_register+0x54/0x84
[<c02e272a>] __pci_register_driver+0x5f/0x90
[<c06eacf7>] agp_intel_init+0x20/0x22
[<c01004b6>] init+0x10d/0x310
[<c0103db7>] kernel_thread_helper+0x7/0x10
=======================
Code: d4 b8 00 72 5b c0 e8 1b ef 3c 00 89 d8 83 c4 2c 5b 5e 5f 5d c3 bb ea ff ff ff eb e2 0f 0b eb fe bb f4 ff ff ff eb d7 0f 0b eb fe <0f> 0b eb fe 55 89 e5 53 89 c3 85 c0 74 4d a1 8c 57 63 c0 a9 00
EIP: [<c011b2ed>] change_page_attr+0x2a8/0x2ac SS:ESP 0068:dfd01df8
<0>Kernel panic - not syncing: Attempted to kill init!
WARNING at arch/i386/kernel/smp.c:549 smp_call_function()
[<c0104282>] dump_trace+0x1b7/0x1e6
[<c01042cb>] show_trace_log_lvl+0x1a/0x30
[<c010495f>] show_trace+0x12/0x14
[<c01049e6>] dump_stack+0x16/0x18
[<c0112bb9>] smp_call_function+0x115/0x11a
[<c0112bdc>] smp_send_stop+0x1e/0x27
[<c0123594>] panic+0x5f/0x12b
[<c0126d3d>] do_exit+0x81b/0x938
[<c010487f>] do_trap+0x0/0x9d
[<c01048f2>] do_trap+0x73/0x9d
[<c0105189>] do_invalid_op+0x97/0xa1
[<c04ea3ec>] error_code+0x7c/0x84
[<c011b2ed>] change_page_attr+0x2a8/0x2ac
[<c011adfd>] iounmap+0xcd/0xd8
[<c034b9a6>] agp_generic_free_gatt_table+0x34/0xce
[<c034a4d5>] agp_backend_cleanup+0x20/0x55
[<c034a931>] agp_add_bridge+0x32a/0x3c9
[<c034e8db>] agp_intel_probe+0x17c/0x65c
[<c02e25ae>] pci_device_probe+0x44/0x5f
[<c0363274>] driver_probe_device+0x6c/0x132
[<c0363442>] __driver_attach+0x84/0x86
[<c0362853>] bus_for_each_dev+0x40/0x5e
[<c0363130>] driver_attach+0x19/0x1b
[<c0362b7a>] bus_add_driver+0x6a/0x185
[<c0363699>] driver_register+0x54/0x84
[<c02e272a>] __pci_register_driver+0x5f/0x90
[<c06eacf7>] agp_intel_init+0x20/0x22
[<c01004b6>] init+0x10d/0x310
[<c0103db7>] kernel_thread_helper+0x7/0x10
=======================
Mike Galbraith wrote:
> On Mon, 2006-10-30 at 21:14 +0100, Cornelia Huck wrote:
>
>> Maybe the initscripts have problems coping with the new layout
>> (symlinks instead of real devices)?
>
> SuSE's /sbin/getcfg for one uses libsysfs, which apparently doesn't
> follow symlinks (bounces off symlink and does nutty stuff instead). If
> any of the boxen you're having troubles with use libsysfs in their init
> stuff, that's likely the problem.
If that is what's happening, then the problem is breaking previously
working boxes by changing a userspace API. I don't know exactly which
patch broke it, but reverting all Greg's patches (except USB) from
-mm fixes the issue.
M.
On Mon, 2006-10-30 at 22:37 -0800, Martin J. Bligh wrote:
> Mike Galbraith wrote:
> > On Mon, 2006-10-30 at 21:14 +0100, Cornelia Huck wrote:
> >
> >> Maybe the initscripts have problems coping with the new layout
> >> (symlinks instead of real devices)?
> >
> > SuSE's /sbin/getcfg for one uses libsysfs, which apparently doesn't
> > follow symlinks (bounces off symlink and does nutty stuff instead). If
> > any of the boxen you're having troubles with use libsysfs in their init
> > stuff, that's likely the problem.
>
> If that is what's happening, then the problem is breaking previously
> working boxes by changing a userspace API. I don't know exactly which
> patch broke it, but reverting all Greg's patches (except USB) from
> -mm fixes the issue.
I just straced /sbin/getcfg again, and confirmed that that is indeed
what is still happening here. It's a known issue (for SuSE at least).
-Mike
On Mon, Oct 30, 2006 at 10:37:47PM -0800, Martin J. Bligh wrote:
> Mike Galbraith wrote:
> >On Mon, 2006-10-30 at 21:14 +0100, Cornelia Huck wrote:
> >
> >>Maybe the initscripts have problems coping with the new layout
> >>(symlinks instead of real devices)?
> >
> >SuSE's /sbin/getcfg for one uses libsysfs, which apparently doesn't
> >follow symlinks (bounces off symlink and does nutty stuff instead). If
> >any of the boxen you're having troubles with use libsysfs in their init
> >stuff, that's likely the problem.
>
> If that is what's happening, then the problem is breaking previously
> working boxes by changing a userspace API. I don't know exactly which
> patch broke it, but reverting all Greg's patches (except USB) from
> -mm fixes the issue.
Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
all work just fine. Doesn't anyone read the Kconfig help entries for
new kernel options?
thanks,
greg k-h
On Mon, Oct 30, 2006 at 09:10:46PM -0800, Andrew Morton wrote:
> On Mon, 30 Oct 2006 22:58:11 -0500
> Andrew James Wade <[email protected]> wrote:
>
> > >
> > > hm. Please send the .config
> > >
> > Sure.
> >
> > I've just found out that unsetting CONFIG_SYSFS_DEPRECATED makes the
> > crash go away. I can hack around the resulting udev incompatibility.
> >
> > #
> > # Automatically generated make config: don't edit
> > # Linux kernel version: 2.6.19-rc3-mm1
> > # Mon Oct 30 19:31:03 2006
>
> Well I tried to reproduce this, but I got such a psychedelic cornucopia of
> oopses at various bisection points amongst those sysfs patches that I think
> I'll just give up.
>
> Greg, Kay: it's quite ugly. I'll drop all those patches for now, and I
> suggest you do so too. Have a play with the .config which Andrew sent..
No, please don't drop them. We have tested these out on a lot of
different boxes. So far everyone's problems have either been due to
something else in -mm (acpi patches), or because they did not read the
CONFIG_SYSFS_DEPRECATED Kconfig help text.
I have yet to see any real problems with these patches, except for your
build issue with the bonding drivers, which I'm fixing up right now.
So please leave them in, we did rework them a lot from the last round,
_and_ these patches are shipping successfully in the OpenSuSE 10.2 alpha
and beta release with no reported problems. So they are not as ugly as
you imagine them to be :)
thanks,
greg k-h
On Mon, 2006-10-30 at 22:59 -0800, Greg KH wrote:
> On Mon, Oct 30, 2006 at 10:37:47PM -0800, Martin J. Bligh wrote:
> > Mike Galbraith wrote:
> > >On Mon, 2006-10-30 at 21:14 +0100, Cornelia Huck wrote:
> > >
> > >>Maybe the initscripts have problems coping with the new layout
> > >>(symlinks instead of real devices)?
> > >
> > >SuSE's /sbin/getcfg for one uses libsysfs, which apparently doesn't
> > >follow symlinks (bounces off symlink and does nutty stuff instead). If
> > >any of the boxen you're having troubles with use libsysfs in their init
> > >stuff, that's likely the problem.
> >
> > If that is what's happening, then the problem is breaking previously
> > working boxes by changing a userspace API. I don't know exactly which
> > patch broke it, but reverting all Greg's patches (except USB) from
> > -mm fixes the issue.
>
> Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
> all work just fine. Doesn't anyone read the Kconfig help entries for
> new kernel options?
That's terminal here atm: kernel BUG at arch/i386/mm/pageattr.c:165!
I did have it set, but had to disable it to not panic.
-Mike
On Tue, Oct 31, 2006 at 07:54:02AM +0100, Mike Galbraith wrote:
> On Mon, 2006-10-30 at 22:37 -0800, Martin J. Bligh wrote:
> > Mike Galbraith wrote:
> > > On Mon, 2006-10-30 at 21:14 +0100, Cornelia Huck wrote:
> > >
> > >> Maybe the initscripts have problems coping with the new layout
> > >> (symlinks instead of real devices)?
> > >
> > > SuSE's /sbin/getcfg for one uses libsysfs, which apparently doesn't
> > > follow symlinks (bounces off symlink and does nutty stuff instead). If
> > > any of the boxen you're having troubles with use libsysfs in their init
> > > stuff, that's likely the problem.
> >
> > If that is what's happening, then the problem is breaking previously
> > working boxes by changing a userspace API. I don't know exactly which
> > patch broke it, but reverting all Greg's patches (except USB) from
> > -mm fixes the issue.
>
> I just straced /sbin/getcfg again, and confirmed that that is indeed
> what is still happening here. It's a known issue (for SuSE at least).
Ick, is this 10.1? Or 10.2? Or something else?
thanks,
greg k-h
On Mon, 2006-10-30 at 23:13 -0800, Greg KH wrote:
> On Tue, Oct 31, 2006 at 07:54:02AM +0100, Mike Galbraith wrote:
> > I just straced /sbin/getcfg again, and confirmed that that is indeed
> > what is still happening here. It's a known issue (for SuSE at least).
>
> Ick, is this 10.1? Or 10.2? Or something else?
10.1 fully updated.
-Mike
On Tue, Oct 31, 2006 at 08:15:09AM +0100, Mike Galbraith wrote:
> On Mon, 2006-10-30 at 23:13 -0800, Greg KH wrote:
> > On Tue, Oct 31, 2006 at 07:54:02AM +0100, Mike Galbraith wrote:
> > > I just straced /sbin/getcfg again, and confirmed that that is indeed
> > > what is still happening here. It's a known issue (for SuSE at least).
> >
> > Ick, is this 10.1? Or 10.2? Or something else?
>
> 10.1 fully updated.
Crap, the libsysfs hooks were more intrusive than I expected. 10.2
should not have this issue anymore. Until then, just enable that config
option and you should be fine.
thanks,
greg k-h
On Tue, Oct 31, 2006 at 08:09:54AM +0100, Mike Galbraith wrote:
> On Mon, 2006-10-30 at 22:59 -0800, Greg KH wrote:
> > On Mon, Oct 30, 2006 at 10:37:47PM -0800, Martin J. Bligh wrote:
> > > Mike Galbraith wrote:
> > > >On Mon, 2006-10-30 at 21:14 +0100, Cornelia Huck wrote:
> > > >
> > > >>Maybe the initscripts have problems coping with the new layout
> > > >>(symlinks instead of real devices)?
> > > >
> > > >SuSE's /sbin/getcfg for one uses libsysfs, which apparently doesn't
> > > >follow symlinks (bounces off symlink and does nutty stuff instead). If
> > > >any of the boxen you're having troubles with use libsysfs in their init
> > > >stuff, that's likely the problem.
> > >
> > > If that is what's happening, then the problem is breaking previously
> > > working boxes by changing a userspace API. I don't know exactly which
> > > patch broke it, but reverting all Greg's patches (except USB) from
> > > -mm fixes the issue.
> >
> > Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
> > all work just fine. Doesn't anyone read the Kconfig help entries for
> > new kernel options?
>
> That's terminal here atm: kernel BUG at arch/i386/mm/pageattr.c:165!
>
> I did have it set, but had to disable it to not panic.
I think there are two different issues here. That kernel config option
should not be causing an oops in mm code.
Can you bisect the different patches to see which one causes the
problem?
thanks,
greg k-h
[Resending due to a network problem on my side.]
On Monday, 30 October 2006 21:57, Greg KH wrote:
> On Mon, Oct 30, 2006 at 09:48:33PM +0100, Rafael J. Wysocki wrote:
> > On Monday, 30 October 2006 21:22, Greg KH wrote:
> > > On Mon, Oct 30, 2006 at 09:15:37PM +0100, Rafael J. Wysocki wrote:
> > > > Sorry, I was wrong.
> > > >
> > > > The controller _is_ detected and handled properly, but udev is apparently
> > > > unable to create the special device files for SATA drives/partitions even
> > > > though CONFIG_SYSFS_DEPRECATED is set.
> > >
> > > This config option should not affect the block device sysfs files at all
> > > at this point in time.
> > >
> > > What does 'tree /sys/block/' show?
> >
> > I can't run 'tree', but 'ls' works somehow (can't mount the root fs). The
> > block device sysfs files seem to be present
>
> If they are there, then udev should work just fine.
>
> > > If the files show up there properly, udev should handle them just fine.
> >
> > It doesn't.
> >
> > Well, I can binary search for the offending patch if that helps.
>
> That would be very helpful, thanks.
It's one of these:
git-acpi.patch
git-acpi-fixup.patch
git-acpi-more-build-fixes.patch
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
On Mon, 2006-10-30 at 23:21 -0800, Greg KH wrote:
> On Tue, Oct 31, 2006 at 08:15:09AM +0100, Mike Galbraith wrote:
> > On Mon, 2006-10-30 at 23:13 -0800, Greg KH wrote:
> > > On Tue, Oct 31, 2006 at 07:54:02AM +0100, Mike Galbraith wrote:
> > > > I just straced /sbin/getcfg again, and confirmed that that is indeed
> > > > what is still happening here. It's a known issue (for SuSE at least).
> > >
> > > Ick, is this 10.1? Or 10.2? Or something else?
> >
> > 10.1 fully updated.
>
> Crap, the libsysfs hooks were more intrusive than I expected. 10.2
> should not have this issue anymore. Until then, just enable that config
> option and you should be fine.
I just grabbed latest sysfsutils and configutils srpms, and will see if
the problem has been fixed yet.
(oh... [email protected]. i guess you're already sure:)
Greg KH wrote:
> On Mon, Oct 30, 2006 at 10:37:47PM -0800, Martin J. Bligh wrote:
>> Mike Galbraith wrote:
>>> On Mon, 2006-10-30 at 21:14 +0100, Cornelia Huck wrote:
>>>
>>>> Maybe the initscripts have problems coping with the new layout
>>>> (symlinks instead of real devices)?
>>> SuSE's /sbin/getcfg for one uses libsysfs, which apparently doesn't
>>> follow symlinks (bounces off symlink and does nutty stuff instead). If
>>> any of the boxen you're having troubles with use libsysfs in their init
>>> stuff, that's likely the problem.
>> If that is what's happening, then the problem is breaking previously
>> working boxes by changing a userspace API. I don't know exactly which
>> patch broke it, but reverting all Greg's patches (except USB) from
>> -mm fixes the issue.
>
> Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
> all work just fine. Doesn't anyone read the Kconfig help entries for
> new kernel options?
1. This doesn't fix it.
2. Breaking things by default with an option to unbreak them is not
the finest of plans ;-)
M.
On Mon, 30 Oct 2006 23:03:51 -0800
Greg KH <[email protected]> wrote:
> On Mon, Oct 30, 2006 at 09:10:46PM -0800, Andrew Morton wrote:
> > On Mon, 30 Oct 2006 22:58:11 -0500
> > Andrew James Wade <[email protected]> wrote:
> >
> > > >
> > > > hm. Please send the .config
> > > >
> > > Sure.
> > >
> > > I've just found out that unsetting CONFIG_SYSFS_DEPRECATED makes the
> > > crash go away. I can hack around the resulting udev incompatibility.
> > >
> > > #
> > > # Automatically generated make config: don't edit
> > > # Linux kernel version: 2.6.19-rc3-mm1
> > > # Mon Oct 30 19:31:03 2006
> >
> > Well I tried to reproduce this, but I got such a psychedelic cornucopia of
> > oopses at various bisection points amongst those sysfs patches that I think
> > I'll just give up.
> >
> > Greg, Kay: it's quite ugly. I'll drop all those patches for now, and I
> > suggest you do so too. Have a play with the .config which Andrew sent..
>
> No, please don't drop them. We have tested these out on a lot of
> different boxes. So far everyone's problems have either been due to
> something else in -mm (acpi patches), or because they did not read the
> CONFIG_SYSFS_DEPRECATED Kconfig help text.
Does acpi cause the change_page_attr oopses?
What caused the several different oopses which I got with Andrew's config?
They were all inside the gregkh-driver-* series. (That test machine is
running FC1, which doesn't run udev at all. Its BIOS is acpi-free).
Here's one: http://userweb.kernel.org/~akpm/s5000364.jpg
I didn't grab the others.
> I have yet to see any real problems with these patches, except for your
> build issue with the bonding drivers, which I'm fixing up right now.
Tried Andrew's .config?
> So please leave them in, we did rework them a lot from the last round,
> _and_ these patches are shipping successfully in the OpenSuSE 10.2 alpha
> and beta release with no reported problems. So they are not as ugly as
> you imagine them to be :)
I can tell an enormous string of oopses when I see one ;)
I'm dropping acpi and gregkh-driver-* and am rushing rc4-mm1. Other
people's stuff needs to get tested.
On Mon, 2006-10-30 at 22:59 -0800, Greg KH wrote:
> On Mon, Oct 30, 2006 at 10:37:47PM -0800, Martin J. Bligh wrote:
> > Mike Galbraith wrote:
> > >On Mon, 2006-10-30 at 21:14 +0100, Cornelia Huck wrote:
> > >
> > >>Maybe the initscripts have problems coping with the new layout
> > >>(symlinks instead of real devices)?
> > >
> > >SuSE's /sbin/getcfg for one uses libsysfs, which apparently doesn't
> > >follow symlinks (bounces off symlink and does nutty stuff instead). If
> > >any of the boxen you're having troubles with use libsysfs in their init
> > >stuff, that's likely the problem.
> >
> > If that is what's happening, then the problem is breaking previously
> > working boxes by changing a userspace API. I don't know exactly which
> > patch broke it, but reverting all Greg's patches (except USB) from
> > -mm fixes the issue.
>
> Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
> all work just fine. Doesn't anyone read the Kconfig help entries for
> new kernel options?
There's another thread concerning that kaboom, and I think the culprit
is known?
-Mike
On Tue, 31 Oct 2006 08:29:28 +0100
"Rafael J. Wysocki" <[email protected]> wrote:
> [Resending due to a network problem on my side.]
>
> On Monday, 30 October 2006 21:57, Greg KH wrote:
> > On Mon, Oct 30, 2006 at 09:48:33PM +0100, Rafael J. Wysocki wrote:
> > > On Monday, 30 October 2006 21:22, Greg KH wrote:
> > > > On Mon, Oct 30, 2006 at 09:15:37PM +0100, Rafael J. Wysocki wrote:
> > > > > Sorry, I was wrong.
> > > > >
> > > > > The controller _is_ detected and handled properly, but udev is apparently
> > > > > unable to create the special device files for SATA drives/partitions even
> > > > > though CONFIG_SYSFS_DEPRECATED is set.
> > > >
> > > > This config option should not affect the block device sysfs files at all
> > > > at this point in time.
> > > >
> > > > What does 'tree /sys/block/' show?
> > >
> > > I can't run 'tree', but 'ls' works somehow (can't mount the root fs). The
> > > block device sysfs files seem to be present
> >
> > If they are there, then udev should work just fine.
> >
> > > > If the files show up there properly, udev should handle them just fine.
> > >
> > > It doesn't.
> > >
> > > Well, I can binary search for the offending patch if that helps.
> >
> > That would be very helpful, thanks.
>
> It's one of these:
>
> git-acpi.patch
> git-acpi-fixup.patch
> git-acpi-more-build-fixes.patch
>
You might need to resend the original report so the acpi guys can see it.
Meanwhile, I'll have to drop the acpi tree.
On Mon, 30 Oct 2006 23:34:32 -0800
Andrew Morton <[email protected]> wrote:
> (That test machine is
> running FC1, which doesn't run udev at all. Its BIOS is acpi-free).
Not that this is relevant - the machine went splat well before userspace
started up.
It has some krufty old audio card, but I don't think Andrew's .config even
selected it. Yet it oopsed in alsa code. Am not sure where the other oops
was.
vmm:/home/akpm> lspci
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:0f.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
00:10.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 05)
01:00.0 VGA compatible controller: nVidia Corporation NV18GL [Quadro4 NVS AGP 8x] (rev a2)
On Tuesday, 31 October 2006 08:40, Andrew Morton wrote:
> On Tue, 31 Oct 2006 08:29:28 +0100
> "Rafael J. Wysocki" <[email protected]> wrote:
>
> > [Resending due to a network problem on my side.]
> >
> > On Monday, 30 October 2006 21:57, Greg KH wrote:
> > > On Mon, Oct 30, 2006 at 09:48:33PM +0100, Rafael J. Wysocki wrote:
> > > > On Monday, 30 October 2006 21:22, Greg KH wrote:
> > > > > On Mon, Oct 30, 2006 at 09:15:37PM +0100, Rafael J. Wysocki wrote:
> > > > > > Sorry, I was wrong.
> > > > > >
> > > > > > The controller _is_ detected and handled properly, but udev is apparently
> > > > > > unable to create the special device files for SATA drives/partitions even
> > > > > > though CONFIG_SYSFS_DEPRECATED is set.
> > > > >
> > > > > This config option should not affect the block device sysfs files at all
> > > > > at this point in time.
> > > > >
> > > > > What does 'tree /sys/block/' show?
> > > >
> > > > I can't run 'tree', but 'ls' works somehow (can't mount the root fs). The
> > > > block device sysfs files seem to be present
> > >
> > > If they are there, then udev should work just fine.
> > >
> > > > > If the files show up there properly, udev should handle them just fine.
> > > >
> > > > It doesn't.
> > > >
> > > > Well, I can binary search for the offending patch if that helps.
> > >
> > > That would be very helpful, thanks.
> >
> > It's one of these:
> >
> > git-acpi.patch
> > git-acpi-fixup.patch
> > git-acpi-more-build-fixes.patch
> >
>
> You might need to resend the original report so the acpi guys can see it.
Okay, I will.
> Meanwhile, I'll have to drop the acpi tree.
Well, I'd prefer to find the offending commit within the tree, as the majority
of changes look pretty innocent. Are the commits available somewhere as
individual patches?
On Tue, 31 Oct 2006 08:48:01 +0100
"Rafael J. Wysocki" <[email protected]> wrote:
> > > It's one of these:
> > >
> > > git-acpi.patch
> > > git-acpi-fixup.patch
> > > git-acpi-more-build-fixes.patch
> > >
> >
> > You might need to resend the original report so the acpi guys can see it.
>
> Okay, I will.
Thanks.
> > Meanwhile, I'll have to drop the acpi tree.
>
> Well, I'd prefer to find the offending commit within the tree, as the majority
> of changes look pretty innocent. Are the commits available somewhere as
> individual patches?
git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git#test
I've not had much success persuading git to emit a series of applyable
patches.
On Mon, Oct 30, 2006 at 11:30:01PM -0800, Martin J. Bligh wrote:
> Greg KH wrote:
> >On Mon, Oct 30, 2006 at 10:37:47PM -0800, Martin J. Bligh wrote:
> >>Mike Galbraith wrote:
> >>>On Mon, 2006-10-30 at 21:14 +0100, Cornelia Huck wrote:
> >>>
> >>>>Maybe the initscripts have problems coping with the new layout
> >>>>(symlinks instead of real devices)?
> >>>SuSE's /sbin/getcfg for one uses libsysfs, which apparently doesn't
> >>>follow symlinks (bounces off symlink and does nutty stuff instead). If
> >>>any of the boxen you're having troubles with use libsysfs in their init
> >>>stuff, that's likely the problem.
> >>If that is what's happening, then the problem is breaking previously
> >>working boxes by changing a userspace API. I don't know exactly which
> >>patch broke it, but reverting all Greg's patches (except USB) from
> >>-mm fixes the issue.
> >
> >Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
> >all work just fine. Doesn't anyone read the Kconfig help entries for
> >new kernel options?
>
> 1. This doesn't fix it.
I think acpi is now being fingered here, right?
> 2. Breaking things by default with an option to unbreak them is not
> the finest of plans ;-)
Yes, I have now changed the default for that option to be on to help
guide people even better than before.
thanks,
greg k-h
On Mon, Oct 30, 2006 at 11:34:32PM -0800, Andrew Morton wrote:
> On Mon, 30 Oct 2006 23:03:51 -0800
> Greg KH <[email protected]> wrote:
>
> > On Mon, Oct 30, 2006 at 09:10:46PM -0800, Andrew Morton wrote:
> > > On Mon, 30 Oct 2006 22:58:11 -0500
> > > Andrew James Wade <[email protected]> wrote:
> > >
> > > > >
> > > > > hm. Please send the .config
> > > > >
> > > > Sure.
> > > >
> > > > I've just found out that unsetting CONFIG_SYSFS_DEPRECATED makes the
> > > > crash go away. I can hack around the resulting udev incompatibility.
> > > >
> > > > #
> > > > # Automatically generated make config: don't edit
> > > > # Linux kernel version: 2.6.19-rc3-mm1
> > > > # Mon Oct 30 19:31:03 2006
> > >
> > > Well I tried to reproduce this, but I got such a psychedelic cornucopia of
> > > oopses at various bisection points amongst those sysfs patches that I think
> > > I'll just give up.
> > >
> > > Greg, Kay: it's quite ugly. I'll drop all those patches for now, and I
> > > suggest you do so too. Have a play with the .config which Andrew sent..
> >
> > No, please don't drop them. We have tested these out on a lot of
> > different boxes. So far everyone's problems have either been due to
> > something else in -mm (acpi patches), or because they did not read the
> > CONFIG_SYSFS_DEPRECATED Kconfig help text.
>
> Does acpi cause the change_page_attr oopses?
>
> What caused the several different oopses which I got with Andrew's config?
> They were all inside the gregkh-driver-* series. (That test machine is
> running FC1, which doesn't run udev at all. Its BIOS is acpi-free).
>
> Here's one: http://userweb.kernel.org/~akpm/s5000364.jpg
That function (snd_register_device_for_dev), isn't even in 2.6.19-rc3,
so I don't see how any of my changes could have affected it :)
> I didn't grab the others.
>
> > I have yet to see any real problems with these patches, except for your
> > build issue with the bonding drivers, which I'm fixing up right now.
>
> Tried Andrew's .config?
I will do so in the morning...
time for sleep,
greg k-h
On Mon, 30 Oct 2006 21:14:32 +0100,
Cornelia Huck <[email protected]> wrote:
> With CONFIG_SYSFS_DEPRECATED set, you'll get errors for devices which
> have no parent set. The kobject's parent is set to the class
> subsystem's kobject, meaning there is a child with name bus_id (e.
> g. /sys/class/net/lo). Unfortunately, we also try to create a link
> named bus_id in /sys/class/<foo>, which will fail with -EEXIST... We
> should probably drop that link if we have no parent.
You can use the following as a band-aid (everything looks sane on my
system), although you will still have problems if your setup tools
can't cope with symlinks :/ (a link is still created for devices with
real parents).
Signed-off-by: Cornelia Huck <[email protected]>
---
drivers/base/core.c | 19 ++++++++++++++-----
1 files changed, 14 insertions(+), 5 deletions(-)
--- linux-2.6-CH.orig/drivers/base/core.c
+++ linux-2.6-CH/drivers/base/core.c
@@ -368,6 +368,12 @@ static void klist_children_put(struct kl
static int device_add_class_symlinks(struct device *dev)
{
int error;
+ int create_link =
+#ifdef CONFIG_SYSFS_DEPRECATED
+ dev->parent ? 1 : 0;
+#else
+ 1;
+#endif
if (!dev->class)
return 0;
@@ -375,10 +381,12 @@ static int device_add_class_symlinks(str
"subsystem");
if (error)
goto out;
- error = sysfs_create_link(&dev->class->subsys.kset.kobj, &dev->kobj,
- dev->bus_id);
- if (error)
- goto out_subsys;
+ if (create_link) {
+ error = sysfs_create_link(&dev->class->subsys.kset.kobj,
+ &dev->kobj, dev->bus_id);
+ if (error)
+ goto out_subsys;
+ }
#ifdef CONFIG_SYSFS_DEPRECATED
if (dev->parent) {
char *class_name;
@@ -407,7 +415,8 @@ out_device:
sysfs_remove_link(&dev->kobj, "device");
out_busid:
#endif
- sysfs_remove_link(&dev->class->subsys.kset.kobj, dev->bus_id);
+ if (create_link)
+ sysfs_remove_link(&dev->class->subsys.kset.kobj, dev->bus_id);
out_subsys:
sysfs_remove_link(&dev->kobj, "subsystem");
out:
On Tue, 2006-10-31 at 08:31 +0100, Mike Galbraith wrote:
> On Mon, 2006-10-30 at 23:21 -0800, Greg KH wrote:
>
> > Crap, the libsysfs hooks were more intrusive than I expected. 10.2
> > should not have this issue anymore. Until then, just enable that config
> > option and you should be fine.
>
> I just grabbed latest sysfsutils and configutils srpms, and will see if
> the problem has been fixed yet.
>
> (oh... [email protected]. i guess you're already sure:)
(i tested it anyway, and of course you're right, it's fixed)
On Tue, 31 Oct 2006 00:01:32 -0800
Greg KH <[email protected]> wrote:
> > Here's one: http://userweb.kernel.org/~akpm/s5000364.jpg
>
> That function (snd_register_device_for_dev), isn't even in 2.6.19-rc3,
> so I don't see how any of my changes could have affected it :)
It runs OK without gregkh-driver-* and oopses with them, so perhaps there's
some interaction there.
>>> Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
>>> all work just fine. Doesn't anyone read the Kconfig help entries for
>>> new kernel options?
>> 1. This doesn't fix it.
>
> I think acpi is now being fingered here, right?
Eh? How. Backing out all your patches from -mm fixes it.
The deprecated stuff does not fix it, it's the same as before.
Unless it's some strange interaction between driver-core/sysfs and ACPI,
I don't see how it can be ACPI's fault?
>> 2. Breaking things by default with an option to unbreak them is not
>> the finest of plans ;-)
>
> Yes, I have now changed the default for that option to be on to help
> guide people even better than before.
There's still some other problem there though. See:
http://test.kernel.org/abat/59232/debug/console.log
who's config is here:
http://test.kernel.org/abat/59232/build/dotconfig
A working log from that machine is here:
http://test.kernel.org/abat/59306/debug/console.log
M.
On Mon, 2006-10-30 at 23:22 -0800, Greg KH wrote:
> On Tue, Oct 31, 2006 at 08:09:54AM +0100, Mike Galbraith wrote:
> > > Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
> > > all work just fine. Doesn't anyone read the Kconfig help entries for
> > > new kernel options?
> >
> > That's terminal here atm: kernel BUG at arch/i386/mm/pageattr.c:165!
> >
> > I did have it set, but had to disable it to not panic.
>
> I think there are two different issues here. That kernel config option
> should not be causing an oops in mm code.
>
> Can you bisect the different patches to see which one causes the
> problem?
I'm not bisecting, but I'm making progress anyway. Definitely seems to
be one of the driver-core-* patches. I'm applying things to 2.6.19-rc3
virgin group wise, and as soon as I applied those, wham.
With only [1] *acpi*, gregkh-driver*, and gregkk-pci* and all was well
(except it didn't cure my eth0 woes).
Still poking at it.
-Mike
On Tue, 31 Oct 2006 07:52:17 -0800,
"Martin J. Bligh" <[email protected]> wrote:
> >>> Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
> >>> all work just fine. Doesn't anyone read the Kconfig help entries for
> >>> new kernel options?
> >> 1. This doesn't fix it.
> >
> > I think acpi is now being fingered here, right?
>
> Eh? How. Backing out all your patches from -mm fixes it.
> The deprecated stuff does not fix it, it's the same as before.
That's because /sys/class/net/<interface> is now a symlink instead of a
directory (and that hasn't anything to do with acpi, but rather with
the conversions in the driver tree). Seems the directory -> symlink
change shouldn't be done since it's impacting user space...
Cornelia Huck wrote:
> On Tue, 31 Oct 2006 07:52:17 -0800,
> "Martin J. Bligh" <[email protected]> wrote:
>
>>>>> Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
>>>>> all work just fine. Doesn't anyone read the Kconfig help entries for
>>>>> new kernel options?
>>>> 1. This doesn't fix it.
>>> I think acpi is now being fingered here, right?
>> Eh? How. Backing out all your patches from -mm fixes it.
>> The deprecated stuff does not fix it, it's the same as before.
>
> That's because /sys/class/net/<interface> is now a symlink instead of a
> directory (and that hasn't anything to do with acpi, but rather with
> the conversions in the driver tree). Seems the directory -> symlink
> change shouldn't be done since it's impacting user space...
You know which individual patch in -mm broke that? Can't see it easily.
Then we can just test across all the machines with just that one backed
out.
Thanks,
M.
On Tue, 31 Oct 2006 09:09:16 -0800,
"Martin J. Bligh" <[email protected]> wrote:
> Cornelia Huck wrote:
> > That's because /sys/class/net/<interface> is now a symlink instead of a
> > directory (and that hasn't anything to do with acpi, but rather with
> > the conversions in the driver tree). Seems the directory -> symlink
> > change shouldn't be done since it's impacting user space...
>
> You know which individual patch in -mm broke that? Can't see it easily.
> Then we can just test across all the machines with just that one backed
> out.
I'd try reverting gregkh-driver-network-device.patch for the network
device stuff.
Cornelia Huck wrote:
> On Tue, 31 Oct 2006 09:09:16 -0800,
> "Martin J. Bligh" <[email protected]> wrote:
>
>> Cornelia Huck wrote:
>>> That's because /sys/class/net/<interface> is now a symlink instead of a
>>> directory (and that hasn't anything to do with acpi, but rather with
>>> the conversions in the driver tree). Seems the directory -> symlink
>>> change shouldn't be done since it's impacting user space...
>> You know which individual patch in -mm broke that? Can't see it easily.
>> Then we can just test across all the machines with just that one backed
>> out.
>
> I'd try reverting gregkh-driver-network-device.patch for the network
> device stuff.
Ok, I've done a bisection which came back to:
gregkh-driver-mem-devices
But as it seems somewhat nonsensical I'll submit two tests one with that
backed out and one with the patch below backed out:
gregkh-driver-network-device
Results should be out on TKO in a few hours. Will report back tommorrow
in detail.
-apw
On Tue, 2006-10-31 at 17:28 +0100, Mike Galbraith wrote:
> On Mon, 2006-10-30 at 23:22 -0800, Greg KH wrote:
> > On Tue, Oct 31, 2006 at 08:09:54AM +0100, Mike Galbraith wrote:
>
> > > > Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
> > > > all work just fine. Doesn't anyone read the Kconfig help entries for
> > > > new kernel options?
> > >
> > > That's terminal here atm: kernel BUG at arch/i386/mm/pageattr.c:165!
> > >
> > > I did have it set, but had to disable it to not panic.
> >
> > I think there are two different issues here. That kernel config option
> > should not be causing an oops in mm code.
> >
> > Can you bisect the different patches to see which one causes the
> > problem?
>
> I'm not bisecting, but I'm making progress anyway. Definitely seems to
> be one of the driver-core-* patches. I'm applying things to 2.6.19-rc3
> virgin group wise, and as soon as I applied those, wham.
>
> With only [1] *acpi*, gregkh-driver*, and gregkk-pci* and all was well
> (except it didn't cure my eth0 woes).
>
> Still poking at it.
Seems it's driver-core-fixes-sysfs_create_link-retval-checks-in.patch
Tomorrow, I'll revert that alone from 2.6.19-rc3-mm1 to confirm... for
now, it's family time.
-Mike
On Tue, Oct 31, 2006 at 09:03:14AM +0100, Mike Galbraith wrote:
> On Tue, 2006-10-31 at 08:31 +0100, Mike Galbraith wrote:
> > On Mon, 2006-10-30 at 23:21 -0800, Greg KH wrote:
> >
> > > Crap, the libsysfs hooks were more intrusive than I expected. 10.2
> > > should not have this issue anymore. Until then, just enable that config
> > > option and you should be fine.
> >
> > I just grabbed latest sysfsutils and configutils srpms, and will see if
> > the problem has been fixed yet.
> >
> > (oh... [email protected]. i guess you're already sure:)
>
> (i tested it anyway, and of course you're right, it's fixed)
Thanks for verifying this, I appreciate it.
greg k-h
On Tue, Oct 31, 2006 at 05:46:39PM +0100, Cornelia Huck wrote:
> On Tue, 31 Oct 2006 07:52:17 -0800,
> "Martin J. Bligh" <[email protected]> wrote:
>
> > >>> Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
> > >>> all work just fine. Doesn't anyone read the Kconfig help entries for
> > >>> new kernel options?
> > >> 1. This doesn't fix it.
> > >
> > > I think acpi is now being fingered here, right?
> >
> > Eh? How. Backing out all your patches from -mm fixes it.
> > The deprecated stuff does not fix it, it's the same as before.
>
> That's because /sys/class/net/<interface> is now a symlink instead of a
> directory (and that hasn't anything to do with acpi, but rather with
> the conversions in the driver tree). Seems the directory -> symlink
> change shouldn't be done since it's impacting user space...
If you enable CONFIG_SYSFS_DEPRECATED, then there is no symlink and
there is no userspace change. sysfs should look identical to before.
Or did I miss something doing this work?
thanks,
greg k-h
Cornelia Huck wrote:
> On Tue, 31 Oct 2006 09:09:16 -0800,
> "Martin J. Bligh" <[email protected]> wrote:
>
>
>>Cornelia Huck wrote:
>>
>>>That's because /sys/class/net/<interface> is now a symlink instead of a
>>>directory (and that hasn't anything to do with acpi, but rather with
>>>the conversions in the driver tree). Seems the directory -> symlink
>>>change shouldn't be done since it's impacting user space...
>>
>>You know which individual patch in -mm broke that? Can't see it easily.
>>Then we can just test across all the machines with just that one backed
>>out.
>
>
> I'd try reverting gregkh-driver-network-device.patch for the network
> device stuff.
Reverting that patch does indeed appear to fix it.
Thanks,
M.
On Tue, Oct 31, 2006 at 05:39:10PM -0800, Martin Bligh wrote:
> Cornelia Huck wrote:
> >On Tue, 31 Oct 2006 09:09:16 -0800,
> >"Martin J. Bligh" <[email protected]> wrote:
> >
> >
> >>Cornelia Huck wrote:
> >>
> >>>That's because /sys/class/net/<interface> is now a symlink instead of a
> >>>directory (and that hasn't anything to do with acpi, but rather with
> >>>the conversions in the driver tree). Seems the directory -> symlink
> >>>change shouldn't be done since it's impacting user space...
> >>
> >>You know which individual patch in -mm broke that? Can't see it easily.
> >>Then we can just test across all the machines with just that one backed
> >>out.
> >
> >
> >I'd try reverting gregkh-driver-network-device.patch for the network
> >device stuff.
>
> Reverting that patch does indeed appear to fix it.
Even with CONFIG_SYSFS_DEPRECATED enabled? For some reason I'm guessing
that you missed that suggestion a while back...
thanks,
greg k-h
Greg KH wrote:
> On Tue, Oct 31, 2006 at 05:39:10PM -0800, Martin Bligh wrote:
>
>>Cornelia Huck wrote:
>>
>>>On Tue, 31 Oct 2006 09:09:16 -0800,
>>>"Martin J. Bligh" <[email protected]> wrote:
>>>
>>>
>>>
>>>>Cornelia Huck wrote:
>>>>
>>>>
>>>>>That's because /sys/class/net/<interface> is now a symlink instead of a
>>>>>directory (and that hasn't anything to do with acpi, but rather with
>>>>>the conversions in the driver tree). Seems the directory -> symlink
>>>>>change shouldn't be done since it's impacting user space...
>>>>
>>>>You know which individual patch in -mm broke that? Can't see it easily.
>>>>Then we can just test across all the machines with just that one backed
>>>>out.
>>>
>>>
>>>I'd try reverting gregkh-driver-network-device.patch for the network
>>>device stuff.
>>
>>Reverting that patch does indeed appear to fix it.
>
>
> Even with CONFIG_SYSFS_DEPRECATED enabled? For some reason I'm guessing
> that you missed that suggestion a while back...
Yes - Enabling CONFIG_SYSFS_DEPRECATED didn't help.
M.
On Tue, 2006-10-31 at 19:14 +0100, Mike Galbraith wrote:
> Seems it's driver-core-fixes-sysfs_create_link-retval-checks-in.patch
>
> Tomorrow, I'll revert that alone from 2.6.19-rc3-mm1 to confirm...
Confirmed. Boots fine with that patch reverted.
I'm getting a slew of....
BUG: atomic counter underflow at:
[<c0104282>] dump_trace+0x1b7/0x1e6
[<c01042cb>] show_trace_log_lvl+0x1a/0x30
[<c010495f>] show_trace+0x12/0x14
[<c01049e6>] dump_stack+0x16/0x18
[<c01b5262>] sysfs_d_iput+0x68/0x96
[<c01860de>] dentry_iput+0x5d/0xb1
[<c0186f25>] dput+0xd2/0x133
[<c01b4f45>] sysfs_remove_dir+0xd2/0x120
[<c02d59e4>] kobject_del+0xb/0x15
[<c03612f1>] device_del+0x199/0x1b0
[<c0361313>] device_unregister+0xb/0x15
[<c03613a2>] device_destroy+0x85/0x8e
[<c033e827>] vcs_remove_sysfs+0x1c/0x38
[<c034414d>] con_close+0x5e/0x6b
[<c0336bca>] release_dev+0x13d/0x65b
[<c03370fa>] tty_release+0x12/0x1c
[<c0176bad>] __fput+0xab/0x1d8
[<c0176dd8>] fput+0x22/0x3b
[<c0174314>] filp_close+0x41/0x67
[<c01753e8>] sys_close+0x6e/0xb6
[<c010317c>] syscall_call+0x7/0xb
[<0805cdc7>] 0x805cdc7
=======================
...with 2.6.19-rc3-mm1 with the patch reverted, which I did not get with
the patched up 2.6.19-rc3, but it does boot and run without exploding.
-Mike
On Tue, 2006-10-31 at 13:31 -0800, Greg KH wrote:
> On Tue, Oct 31, 2006 at 05:46:39PM +0100, Cornelia Huck wrote:
> > On Tue, 31 Oct 2006 07:52:17 -0800,
> > "Martin J. Bligh" <[email protected]> wrote:
> >
> > > >>> Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
> > > >>> all work just fine. Doesn't anyone read the Kconfig help entries for
> > > >>> new kernel options?
> > > >> 1. This doesn't fix it.
> > > >
> > > > I think acpi is now being fingered here, right?
> > >
> > > Eh? How. Backing out all your patches from -mm fixes it.
> > > The deprecated stuff does not fix it, it's the same as before.
> >
> > That's because /sys/class/net/<interface> is now a symlink instead of a
> > directory (and that hasn't anything to do with acpi, but rather with
> > the conversions in the driver tree). Seems the directory -> symlink
> > change shouldn't be done since it's impacting user space...
>
> If you enable CONFIG_SYSFS_DEPRECATED, then there is no symlink and
> there is no userspace change. sysfs should look identical to before.
>
> Or did I miss something doing this work?
Something is amiss, because it's still a symlink here.
With driver-core-fixes-sysfs_create_link-retval-checks-in.patch reverted
so I can boot, I get the below both in my patched up 2.6.19-rc3 and
2.6.19-rc3-mm1.
strace -vf /sbin/getcfg eth0
lstat64("/sys/class/net/eth0", {st_dev=makedev(0, 0), st_ino=4480, st_mode=S_IFLNK|0777, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2006/11/01-05:00:15, st_mtime=2006/11/01-05:59:54, st_ctime=2006/11/01-05:59:54}) = 0
file /sys/class/net/eth0
/sys/class/net/eth0: symbolic link to `../../devices/pci0000:00/0000:00:1e.0/0000:02:09.0/eth0'
grep DEPRECATED .config
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_PM_SYSFS_DEPRECATED is not set
On Wed, 01 Nov 2006 05:43:18 +0100
Mike Galbraith <[email protected]> wrote:
> On Tue, 2006-10-31 at 19:14 +0100, Mike Galbraith wrote:
>
> > Seems it's driver-core-fixes-sysfs_create_link-retval-checks-in.patch
> >
> > Tomorrow, I'll revert that alone from 2.6.19-rc3-mm1 to confirm...
>
> Confirmed. Boots fine with that patch reverted.
Could you test with something like this applied?
diff -puN drivers/base/core.c~driver-core-fixes-sysfs_create_link-retval-checks-in-debug drivers/base/core.c
--- a/drivers/base/core.c~driver-core-fixes-sysfs_create_link-retval-checks-in-debug
+++ a/drivers/base/core.c
@@ -24,6 +24,8 @@
#include "base.h"
#include "power/power.h"
+#define DB() printk(KERN_ERR "sysfs failure at %s:%d\n", __FILE__, __LINE__)
+
int (*platform_notify)(struct device * dev) = NULL;
int (*platform_notify_remove)(struct device * dev) = NULL;
@@ -373,30 +375,39 @@ static int device_add_class_symlinks(str
return 0;
error = sysfs_create_link(&dev->kobj, &dev->class->subsys.kset.kobj,
"subsystem");
- if (error)
+ if (error) {
+ DB();
goto out;
+ }
error = sysfs_create_link(&dev->class->subsys.kset.kobj, &dev->kobj,
dev->bus_id);
- if (error)
+ if (error) {
+ DB();
goto out_subsys;
+ }
#ifdef CONFIG_SYSFS_DEPRECATED
if (dev->parent) {
char *class_name;
error = sysfs_create_link(&dev->kobj, &dev->parent->kobj,
"device");
- if (error)
+ if (error) {
+ DB();
goto out_busid;
+ }
class_name = make_class_name(dev->class->name, &dev->kobj);
if (!class_name) {
+ DB();
error = -ENOMEM;
goto out_busid;
}
error = sysfs_create_link(&dev->parent->kobj, &dev->kobj,
class_name);
kfree(class_name);
- if (error)
+ if (error) {
+ DB();
goto out_device;
+ }
}
#endif
return 0;
@@ -574,8 +585,10 @@ int device_add(struct device *dev)
dev->devt_attr = attr;
}
- if ((error = device_add_class_symlinks(dev)))
+ if ((error = device_add_class_symlinks(dev))) {
+ DB();
goto SymlinkError;
+ }
if ((error = device_add_attrs(dev)))
goto AttrsError;
if ((error = device_add_groups(dev)))
@@ -941,6 +954,7 @@ int device_rename(struct device *dev, ch
error = kobject_rename(&dev->kobj, new_name);
if (error) {
+ DB();
strlcpy(dev->bus_id, old_device_name, BUS_ID_SIZE);
goto out;
}
@@ -951,8 +965,10 @@ int device_rename(struct device *dev, ch
if (new_class_name) {
error = sysfs_create_link(&dev->parent->kobj,
&dev->kobj, new_class_name);
- if (error)
+ if (error) {
+ DB();
goto out;
+ }
sysfs_remove_link(&dev->parent->kobj, old_class_name);
}
}
_
> I'm getting a slew of....
> BUG: atomic counter underflow at:
> [<c0104282>] dump_trace+0x1b7/0x1e6
> [<c01042cb>] show_trace_log_lvl+0x1a/0x30
> [<c010495f>] show_trace+0x12/0x14
> [<c01049e6>] dump_stack+0x16/0x18
> [<c01b5262>] sysfs_d_iput+0x68/0x96
> [<c01860de>] dentry_iput+0x5d/0xb1
> [<c0186f25>] dput+0xd2/0x133
> [<c01b4f45>] sysfs_remove_dir+0xd2/0x120
> [<c02d59e4>] kobject_del+0xb/0x15
> [<c03612f1>] device_del+0x199/0x1b0
> [<c0361313>] device_unregister+0xb/0x15
> [<c03613a2>] device_destroy+0x85/0x8e
> [<c033e827>] vcs_remove_sysfs+0x1c/0x38
> [<c034414d>] con_close+0x5e/0x6b
> [<c0336bca>] release_dev+0x13d/0x65b
> [<c03370fa>] tty_release+0x12/0x1c
> [<c0176bad>] __fput+0xab/0x1d8
> [<c0176dd8>] fput+0x22/0x3b
> [<c0174314>] filp_close+0x41/0x67
> [<c01753e8>] sys_close+0x6e/0xb6
> [<c010317c>] syscall_call+0x7/0xb
> [<0805cdc7>] 0x805cdc7
> =======================
> ...with 2.6.19-rc3-mm1 with the patch reverted, which I did not get with
> the patched up 2.6.19-rc3, but it does boot and run without exploding.
Hopefully that's due to the cherry-unpicking of this patch..
On Tue, 2006-10-31 at 21:25 -0800, Andrew Morton wrote:
> On Wed, 01 Nov 2006 05:43:18 +0100
> Mike Galbraith <[email protected]> wrote:
>
> > On Tue, 2006-10-31 at 19:14 +0100, Mike Galbraith wrote:
> >
> > > Seems it's driver-core-fixes-sysfs_create_link-retval-checks-in.patch
> > >
> > > Tomorrow, I'll revert that alone from 2.6.19-rc3-mm1 to confirm...
> >
> > Confirmed. Boots fine with that patch reverted.
>
> Could you test with something like this applied?
No output. I had already enabled debugging, but got nada there either.
Bugger. <scritch scritch>
-Mike
On Wed, 2006-11-01 at 07:12 +0100, Mike Galbraith wrote:
> On Tue, 2006-10-31 at 21:25 -0800, Andrew Morton wrote:
> > On Wed, 01 Nov 2006 05:43:18 +0100
> > Mike Galbraith <[email protected]> wrote:
> >
> > > On Tue, 2006-10-31 at 19:14 +0100, Mike Galbraith wrote:
> > >
> > > > Seems it's driver-core-fixes-sysfs_create_link-retval-checks-in.patch
> > > >
> > > > Tomorrow, I'll revert that alone from 2.6.19-rc3-mm1 to confirm...
> > >
> > > Confirmed. Boots fine with that patch reverted.
> >
> > Could you test with something like this applied?
>
> No output. I had already enabled debugging, but got nada there either.
> Bugger. <scritch scritch>
FIWI, the explosion is related to the fact that I have two graphics
cards configured in. One is on-board (Intel 865 Chipset), and the other
is an ATI X850 AGP (which I use, the other is there in case of failure).
If I disable all of the Intel 865 options, the box gets much further.
It then oopses while initializing sound, and eventually hangs. I poked
SysRq-T while it was hung, and was looking at the serial console output
when it took off again. It stalled again, and eventually, I gave up on
it. The complete log up through me poking SysRq-T is available for the
asking if anyone is interested.
The oops is below, but is probably irrelevant for this thread.
BUG: unable to handle kernel NULL pointer dereference at virtual address 0000010b
printing eip:
f8818377
*pde = 00000000
Oops: 0002 [#1]
PREEMPT SMP
last sysfs file: /class/input/input1/name
Modules linked in: snd_mpu401 snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore
CPU: 0
EIP: 0060:[<f8818377>] Not tainted VLI
EFLAGS: 00010282 (2.6.19-rc3-mm1-smp #21)
EIP is at snd_register_device_for_dev+0xff/0x116 [snd]
eax: ffffffef ebx: f79a2fa0 ecx: dffff4c0 edx: f7873e00
esi: 00000028 edi: 00000008 ebp: f7e4bd0c esp: f7e4bce4
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 2712, ti=f7e4a000 task=dfdb0a90 task.ti=f7e4a000)
Stack: f7c1a3c0 00000000 07400028 f881d69d f7e4bd24 00000000 f786e000 fffffff4
f7873e00 f7873e04 f7e4bd40 f882d951 f8832180 f7873e00 f7e4bd24 00000000
6964696d 30443143 ffffff00 f7c1a3c0 f79a2fe0 f786e140 00000000 f7e4bd50
Call Trace:
[<f882d951>] snd_rawmidi_dev_register+0xaa/0x322 [snd_rawmidi]
[<f881c9a8>] snd_device_register_all+0x30/0x4f [snd]
[<f8818bbe>] snd_card_register+0x55/0x311 [snd]
[<f88582d6>] snd_mpu401_pnp_probe+0x13a/0x1d3 [snd_mpu401]
[<c03316c7>] pnp_device_probe+0x47/0xa0
[<c036327b>] driver_probe_device+0xb6/0x18f
[<c036345c>] __driver_attach+0x84/0x86
[<c0362b83>] bus_for_each_dev+0x44/0x62
[<c0363097>] driver_attach+0x19/0x1b
[<c0362689>] bus_add_driver+0x85/0x1a8
[<c03636a9>] driver_register+0x54/0x84
[<c03314d1>] pnp_register_driver+0x17/0x19
[<f885c081>] alsa_card_mpu401_init+0x81/0xcd [snd_mpu401]
[<c0141f27>] sys_init_module+0x12f/0x1c9c
[<c010317c>] syscall_call+0x7/0xb
[<b7f01f5e>] 0xb7f01f5e
=======================
Code: a0 52 82 f8 c1 e0 14 09 f0 89 44 24 08 8b 45 14 89 44 24 04 a1 80 b4 83 f8 89 04 24 e8 36 96 b4 c7 89 43 14 85 c0 74 09 8b 55 0c <89> 90 1c 01 00 00 b8 2c 53 82 f8 e8 48 30 cd c7 31 f6 e9 62 ff
EIP: [<f8818377>] snd_register_device_for_dev+0xff/0x116 [snd] SS:ESP 0068:f7e4bce4
(gdb) list *snd_register_device_for_dev+0xff
0x377 is in snd_register_device_for_dev (include/linux/device.h:405).
400 }
401
402 static inline void
403 dev_set_drvdata (struct device *dev, void *data)
404 {
405 dev->driver_data = data;
406 }
407
408 static inline int device_is_registered(struct device *dev)
409 {
On Wed, 2006-11-01 at 07:12 +0100, Mike Galbraith wrote:
> On Tue, 2006-10-31 at 21:25 -0800, Andrew Morton wrote:
> > On Wed, 01 Nov 2006 05:43:18 +0100
> > Mike Galbraith <[email protected]> wrote:
> >
> > > On Tue, 2006-10-31 at 19:14 +0100, Mike Galbraith wrote:
> > >
> > > > Seems it's driver-core-fixes-sysfs_create_link-retval-checks-in.patch
> > > >
> > > > Tomorrow, I'll revert that alone from 2.6.19-rc3-mm1 to confirm...
> > >
> > > Confirmed. Boots fine with that patch reverted.
> >
> > Could you test with something like this applied?
>
> No output. I had already enabled debugging, but got nada there either.
> Bugger. <scritch scritch>
Duh! (what a maroon) I booted the wrong kernel due to a typo.
I enabled some other debug options (poke/hope), and it now boots past
the BUG at arch/i386/mm/pageattr.c:165 point, through the sound NULL
pointer dereference, and on to the eventual complete hang as NFS is
being initialized. The log shows 326 failures at lines 385 and 589.
-Mike
Greg KH wrote:
> On Tue, Oct 31, 2006 at 05:39:10PM -0800, Martin Bligh wrote:
>> Cornelia Huck wrote:
>>> On Tue, 31 Oct 2006 09:09:16 -0800,
>>> "Martin J. Bligh" <[email protected]> wrote:
>>>
>>>
>>>> Cornelia Huck wrote:
>>>>
>>>>> That's because /sys/class/net/<interface> is now a symlink instead of a
>>>>> directory (and that hasn't anything to do with acpi, but rather with
>>>>> the conversions in the driver tree). Seems the directory -> symlink
>>>>> change shouldn't be done since it's impacting user space...
>>>> You know which individual patch in -mm broke that? Can't see it easily.
>>>> Then we can just test across all the machines with just that one backed
>>>> out.
>>>
>>> I'd try reverting gregkh-driver-network-device.patch for the network
>>> device stuff.
>> Reverting that patch does indeed appear to fix it.
>
> Even with CONFIG_SYSFS_DEPRECATED enabled? For some reason I'm guessing
> that you missed that suggestion a while back...
Nope, that was tested across the board and was a failure. Check TKO,
there is a run with sysfs-deprecated-turn-this-on-by-default ...
I checked and this did result in configs with this option enabled.
-apw
On Tuesday 31 October 2006 00:09, Andrew James Wade wrote:
> On Monday 30 October 2006 23:20, Greg KH wrote:
> > On Mon, Oct 30, 2006 at 08:11:23PM -0800, Andrew Morton wrote:
> > > On Mon, 30 Oct 2006 22:58:11 -0500
> > > Andrew James Wade <[email protected]> wrote:
> > >
> > > > I've just found out that unsetting CONFIG_SYSFS_DEPRECATED makes the
> > > > crash go away.
> > >
> > > How bizarre. sysfs changes cause unexpected pte protection values?
>
> Perhaps one of the drivers is responding badly to device_create
> failing? (-EEXIST, if I'm not mistaken).
>
> >
> > That's just wrong. Something odd is happening here. Can you try to
> > bisect things to determine the patch that is causing the problem?
>
> Sure.
driver-core-fixes-sysfs_create_link-retval-checks-in.patch is where
this particular crash starts.
Andrew Wade
On Tue, Oct 31, 2006 at 06:11:13PM -0800, Martin Bligh wrote:
> Greg KH wrote:
> >On Tue, Oct 31, 2006 at 05:39:10PM -0800, Martin Bligh wrote:
> >
> >>Cornelia Huck wrote:
> >>
> >>>On Tue, 31 Oct 2006 09:09:16 -0800,
> >>>"Martin J. Bligh" <[email protected]> wrote:
> >>>
> >>>
> >>>
> >>>>Cornelia Huck wrote:
> >>>>
> >>>>
> >>>>>That's because /sys/class/net/<interface> is now a symlink instead of a
> >>>>>directory (and that hasn't anything to do with acpi, but rather with
> >>>>>the conversions in the driver tree). Seems the directory -> symlink
> >>>>>change shouldn't be done since it's impacting user space...
> >>>>
> >>>>You know which individual patch in -mm broke that? Can't see it easily.
> >>>>Then we can just test across all the machines with just that one backed
> >>>>out.
> >>>
> >>>
> >>>I'd try reverting gregkh-driver-network-device.patch for the network
> >>>device stuff.
> >>
> >>Reverting that patch does indeed appear to fix it.
> >
> >
> >Even with CONFIG_SYSFS_DEPRECATED enabled? For some reason I'm guessing
> >that you missed that suggestion a while back...
>
> Yes - Enabling CONFIG_SYSFS_DEPRECATED didn't help.
Ok, I'm testing this now and getting some very wierd results. Will
update everyone when I figure it out (oopses in vt code...)
thanks,
greg k-h
On Wed, 01 Nov 2006 10:26:24 +0100
Mike Galbraith <[email protected]> wrote:
> On Wed, 2006-11-01 at 07:12 +0100, Mike Galbraith wrote:
> > On Tue, 2006-10-31 at 21:25 -0800, Andrew Morton wrote:
> > > On Wed, 01 Nov 2006 05:43:18 +0100
> > > Mike Galbraith <[email protected]> wrote:
> > >
> > > > On Tue, 2006-10-31 at 19:14 +0100, Mike Galbraith wrote:
> > > >
> > > > > Seems it's driver-core-fixes-sysfs_create_link-retval-checks-in.patch
> > > > >
> > > > > Tomorrow, I'll revert that alone from 2.6.19-rc3-mm1 to confirm...
> > > >
> > > > Confirmed. Boots fine with that patch reverted.
> > >
> > > Could you test with something like this applied?
> >
> > No output. I had already enabled debugging, but got nada there either.
> > Bugger. <scritch scritch>
>
> Duh! (what a maroon) I booted the wrong kernel due to a typo.
>
> I enabled some other debug options (poke/hope), and it now boots past
> the BUG at arch/i386/mm/pageattr.c:165 point, through the sound NULL
> pointer dereference, and on to the eventual complete hang as NFS is
> being initialized. The log shows 326 failures at lines 385 and 589.
You mean 326 separate failures? erp.
So it's failing here:
static int device_add_class_symlinks(struct device *dev)
{
int error;
if (!dev->class)
return 0;
error = sysfs_create_link(&dev->kobj, &dev->class->subsys.kset.kobj,
"subsystem");
if (error) {
DB();
goto out;
}
error = sysfs_create_link(&dev->class->subsys.kset.kobj, &dev->kobj,
dev->bus_id);
if (error) {
-->> DB();
goto out_subsys;
}
Now, prior to driver-core-fixes-sysfs_create_link-retval-checks-in.patch we
were simply ignoring the return value of sysfs_create_link(). Now we're
not ignoring it and stuff is failing.
I'm suspecting that the second call to sysfs_create_link() in device_add():
if (dev->class) {
sysfs_create_link(&dev->kobj, &dev->class->subsys.kset.kobj,
"subsystem");
-->> sysfs_create_link(&dev->class->subsys.kset.kobj, &dev->kobj,
dev->bus_id);
is simply always failing, only we never knew about it.
It would be useful if you could tell us what `error' is in there. Usually
-EEXIST.
Greg, what is that call actually linking from and to?
On Wed, Nov 01, 2006 at 10:48:53AM -0800, Andrew Morton wrote:
> On Wed, 01 Nov 2006 10:26:24 +0100
> Mike Galbraith <[email protected]> wrote:
>
> > On Wed, 2006-11-01 at 07:12 +0100, Mike Galbraith wrote:
> > > On Tue, 2006-10-31 at 21:25 -0800, Andrew Morton wrote:
> > > > On Wed, 01 Nov 2006 05:43:18 +0100
> > > > Mike Galbraith <[email protected]> wrote:
> > > >
> > > > > On Tue, 2006-10-31 at 19:14 +0100, Mike Galbraith wrote:
> > > > >
> > > > > > Seems it's driver-core-fixes-sysfs_create_link-retval-checks-in.patch
> > > > > >
> > > > > > Tomorrow, I'll revert that alone from 2.6.19-rc3-mm1 to confirm...
> > > > >
> > > > > Confirmed. Boots fine with that patch reverted.
> > > >
> > > > Could you test with something like this applied?
> > >
> > > No output. I had already enabled debugging, but got nada there either.
> > > Bugger. <scritch scritch>
> >
> > Duh! (what a maroon) I booted the wrong kernel due to a typo.
> >
> > I enabled some other debug options (poke/hope), and it now boots past
> > the BUG at arch/i386/mm/pageattr.c:165 point, through the sound NULL
> > pointer dereference, and on to the eventual complete hang as NFS is
> > being initialized. The log shows 326 failures at lines 385 and 589.
>
> You mean 326 separate failures? erp.
>
> So it's failing here:
>
> static int device_add_class_symlinks(struct device *dev)
> {
> int error;
>
> if (!dev->class)
> return 0;
> error = sysfs_create_link(&dev->kobj, &dev->class->subsys.kset.kobj,
> "subsystem");
> if (error) {
> DB();
> goto out;
> }
> error = sysfs_create_link(&dev->class->subsys.kset.kobj, &dev->kobj,
> dev->bus_id);
> if (error) {
> -->> DB();
> goto out_subsys;
> }
>
>
> Now, prior to driver-core-fixes-sysfs_create_link-retval-checks-in.patch we
> were simply ignoring the return value of sysfs_create_link(). Now we're
> not ignoring it and stuff is failing.
>
> I'm suspecting that the second call to sysfs_create_link() in device_add():
>
>
> if (dev->class) {
> sysfs_create_link(&dev->kobj, &dev->class->subsys.kset.kobj,
> "subsystem");
> -->> sysfs_create_link(&dev->class->subsys.kset.kobj, &dev->kobj,
> dev->bus_id);
>
> is simply always failing, only we never knew about it.
>
> It would be useful if you could tell us what `error' is in there. Usually
> -EEXIST.
>
> Greg, what is that call actually linking from and to?
That is creating the symlink for the class device to show up properly in
/sys/class.
For example, the /sys/class/net/eth0 entry will be a symlink pointing to
the proper device.
Oh, DOH! That will fail if CONFIG_SYSFS_DEPRECATED is enabled because
that symlink can not be created because the device itself is already
called that and has been registered with sysfs in that location.
That might fix my other problem I am now seeing which happens when a
device is removed from the system at startup with that config option
enabled. Let me go rework this and see if it solves the issue...
thanks for the big hint, I was tracking it down through a different path
and hadn't gotten here yet.
greg k-h
On Wed, 2006-11-01 at 10:48 -0800, Andrew Morton wrote:
> So it's failing here:
>
> static int device_add_class_symlinks(struct device *dev)
> {
> int error;
>
> if (!dev->class)
> return 0;
> error = sysfs_create_link(&dev->kobj, &dev->class->subsys.kset.kobj,
> "subsystem");
> if (error) {
> DB();
> goto out;
> }
> error = sysfs_create_link(&dev->class->subsys.kset.kobj, &dev->kobj,
> dev->bus_id);
> if (error) {
> -->> DB();
> goto out_subsys;
> }
>
>
> Now, prior to driver-core-fixes-sysfs_create_link-retval-checks-in.patch we
> were simply ignoring the return value of sysfs_create_link(). Now we're
> not ignoring it and stuff is failing.
>
> I'm suspecting that the second call to sysfs_create_link() in device_add():
>
>
> if (dev->class) {
> sysfs_create_link(&dev->kobj, &dev->class->subsys.kset.kobj,
> "subsystem");
> -->> sysfs_create_link(&dev->class->subsys.kset.kobj, &dev->kobj,
> dev->bus_id);
>
> is simply always failing, only we never knew about it.
>
> It would be useful if you could tell us what `error' is in there. Usually
> -EEXIST.
Yeah, they're all -EEXIST.
-Mike
Andrew Morton wrote:
> On Tue, 31 Oct 2006 08:48:01 +0100
> "Rafael J. Wysocki" <[email protected]> wrote:
>
>>>> It's one of these:
>>>>
>>>> git-acpi.patch
>>>> git-acpi-fixup.patch
>>>> git-acpi-more-build-fixes.patch
>>>>
>>> You might need to resend the original report so the acpi guys can see it.
>> Okay, I will.
>
> Thanks.
>
>>> Meanwhile, I'll have to drop the acpi tree.
>> Well, I'd prefer to find the offending commit within the tree, as the majority
>> of changes look pretty innocent. Are the commits available somewhere as
>> individual patches?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git#test
>
> I've not had much success persuading git to emit a series of applyable
> patches.
git-format-patch can make a patch file for each commit in range, each
prefixed with a four digit patch number and named similarly to patches
in -mm:
git format-patch -o <dir> <from>..<to>
For example:
0009-DM-kill-bogus-uninit-warning.txt
0010-drivers-net-drivers-net-Silence-more-bogosities.txt
0011-debug-shared-irqs.txt
0012-debug-shared-irqs-kconfig-fix.txt
0013-make-frame_pointer-default-y.txt
It can also produce an mbox mailbox:
git format-patch --stdout <from>..<to>
I've used this second form in combination with a 'mailbomb' exploder to
extract the patches with a series file.
-apw
On Tue, Oct 31, 2006 at 06:11:13PM -0800, Martin Bligh wrote:
> Greg KH wrote:
> >On Tue, Oct 31, 2006 at 05:39:10PM -0800, Martin Bligh wrote:
> >
> >>Cornelia Huck wrote:
> >>
> >>>On Tue, 31 Oct 2006 09:09:16 -0800,
> >>>"Martin J. Bligh" <[email protected]> wrote:
> >>>
> >>>
> >>>
> >>>>Cornelia Huck wrote:
> >>>>
> >>>>
> >>>>>That's because /sys/class/net/<interface> is now a symlink instead of a
> >>>>>directory (and that hasn't anything to do with acpi, but rather with
> >>>>>the conversions in the driver tree). Seems the directory -> symlink
> >>>>>change shouldn't be done since it's impacting user space...
> >>>>
> >>>>You know which individual patch in -mm broke that? Can't see it easily.
> >>>>Then we can just test across all the machines with just that one backed
> >>>>out.
> >>>
> >>>
> >>>I'd try reverting gregkh-driver-network-device.patch for the network
> >>>device stuff.
> >>
> >>Reverting that patch does indeed appear to fix it.
> >
> >
> >Even with CONFIG_SYSFS_DEPRECATED enabled? For some reason I'm guessing
> >that you missed that suggestion a while back...
>
> Yes - Enabling CONFIG_SYSFS_DEPRECATED didn't help.
Ok, you are correct, for a stupid reason, this option didn't correctly
work for a range of device types (I can get into the gory details if
anyone really cares...)
I've now fixed this up, and a few other bugs that I kept tripping on
(which others also hit), and have refreshed my tree so that the next -mm
will be much better in this area.
If the problem persists (and I've built a zillion different kernels in
different configurations today testing to make sure it doesn't), please
let me know.
I can post updated patches here if people want them.
thanks for everyone's patience, I appreciated it.
greg k-h
>>> Even with CONFIG_SYSFS_DEPRECATED enabled? For some reason I'm guessing
>>> that you missed that suggestion a while back...
>> Yes - Enabling CONFIG_SYSFS_DEPRECATED didn't help.
>
> Ok, you are correct, for a stupid reason, this option didn't correctly
> work for a range of device types (I can get into the gory details if
> anyone really cares...)
>
> I've now fixed this up, and a few other bugs that I kept tripping on
> (which others also hit), and have refreshed my tree so that the next -mm
> will be much better in this area.
>
> If the problem persists (and I've built a zillion different kernels in
> different configurations today testing to make sure it doesn't), please
> let me know.
>
> I can post updated patches here if people want them.
>
> thanks for everyone's patience, I appreciated it.
Thanks for fixing this up. If you could post a diff somewhere against
either mainline or -mm, would make it easy to run through
test.kernel.org before you wake up tommorow ;-)
Thanks,
M.
On Wed, Nov 01, 2006 at 09:26:12PM -0800, Martin J. Bligh wrote:
>
> >>>Even with CONFIG_SYSFS_DEPRECATED enabled? For some reason I'm guessing
> >>>that you missed that suggestion a while back...
> >>Yes - Enabling CONFIG_SYSFS_DEPRECATED didn't help.
> >
> >Ok, you are correct, for a stupid reason, this option didn't correctly
> >work for a range of device types (I can get into the gory details if
> >anyone really cares...)
> >
> >I've now fixed this up, and a few other bugs that I kept tripping on
> >(which others also hit), and have refreshed my tree so that the next -mm
> >will be much better in this area.
> >
> >If the problem persists (and I've built a zillion different kernels in
> >different configurations today testing to make sure it doesn't), please
> >let me know.
> >
> >I can post updated patches here if people want them.
> >
> >thanks for everyone's patience, I appreciated it.
>
> Thanks for fixing this up. If you could post a diff somewhere against
> either mainline or -mm
These changes aren't in mainline, so I'll make up something against
-mm...
thanks,
greg k-h
On Wed, 2006-11-01 at 21:26 -0800, Martin J. Bligh wrote:
> > I can post updated patches here if people want them.
> >
> > thanks for everyone's patience, I appreciated it.
>
> Thanks for fixing this up. If you could post a diff somewhere against
> either mainline or -mm, would make it easy to run through
> test.kernel.org before you wake up tommorow ;-)
Ditto. I'll testdrive anything I can wiggle in.
-Mike
On Wed, Nov 01, 2006 at 09:26:12PM -0800, Martin J. Bligh wrote:
>
> >>>Even with CONFIG_SYSFS_DEPRECATED enabled? For some reason I'm guessing
> >>>that you missed that suggestion a while back...
> >>Yes - Enabling CONFIG_SYSFS_DEPRECATED didn't help.
> >
> >Ok, you are correct, for a stupid reason, this option didn't correctly
> >work for a range of device types (I can get into the gory details if
> >anyone really cares...)
> >
> >I've now fixed this up, and a few other bugs that I kept tripping on
> >(which others also hit), and have refreshed my tree so that the next -mm
> >will be much better in this area.
> >
> >If the problem persists (and I've built a zillion different kernels in
> >different configurations today testing to make sure it doesn't), please
> >let me know.
> >
> >I can post updated patches here if people want them.
> >
> >thanks for everyone's patience, I appreciated it.
>
> Thanks for fixing this up. If you could post a diff somewhere against
> either mainline or -mm, would make it easy to run through
> test.kernel.org before you wake up tommorow ;-)
Oops, the newest -mm just came out without any of the driver core
patches in it due to the problems. I'll wait until the next -mm release
then, and try to go catch up on my pending-patch-queue right now
instead...
thanks,
greg k-h
On Wed, 1 Nov 2006 22:02:25 -0800
Greg KH <[email protected]> wrote:
> > Thanks for fixing this up. If you could post a diff somewhere against
> > either mainline or -mm, would make it easy to run through
> > test.kernel.org before you wake up tommorow ;-)
>
> Oops, the newest -mm just came out without any of the driver core
> patches in it due to the problems. I'll wait until the next -mm release
> then, and try to go catch up on my pending-patch-queue right now
> instead...
Let me know when
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver/
is ready to go and I'll prepare a new rollup.
Greg KH wrote:
> On Wed, Nov 01, 2006 at 09:26:12PM -0800, Martin J. Bligh wrote:
>>>>> Even with CONFIG_SYSFS_DEPRECATED enabled? For some reason I'm guessing
>>>>> that you missed that suggestion a while back...
>>>> Yes - Enabling CONFIG_SYSFS_DEPRECATED didn't help.
>>> Ok, you are correct, for a stupid reason, this option didn't correctly
>>> work for a range of device types (I can get into the gory details if
>>> anyone really cares...)
>>>
>>> I've now fixed this up, and a few other bugs that I kept tripping on
>>> (which others also hit), and have refreshed my tree so that the next -mm
>>> will be much better in this area.
>>>
>>> If the problem persists (and I've built a zillion different kernels in
>>> different configurations today testing to make sure it doesn't), please
>>> let me know.
>>>
>>> I can post updated patches here if people want them.
>>>
>>> thanks for everyone's patience, I appreciated it.
>> Thanks for fixing this up. If you could post a diff somewhere against
>> either mainline or -mm, would make it easy to run through
>> test.kernel.org before you wake up tommorow ;-)
>
> Oops, the newest -mm just came out without any of the driver core
> patches in it due to the problems. I'll wait until the next -mm release
> then, and try to go catch up on my pending-patch-queue right now
> instead...
If we can test it out of sync, it'd save potentially messing up another
-mm cycle. The problem is that it blocks lots of other patches from
getting tested ...
M.
On Wed, Nov 01, 2006 at 10:07:01PM -0800, Andrew Morton wrote:
> On Wed, 1 Nov 2006 22:02:25 -0800
> Greg KH <[email protected]> wrote:
>
> > > Thanks for fixing this up. If you could post a diff somewhere against
> > > either mainline or -mm, would make it easy to run through
> > > test.kernel.org before you wake up tommorow ;-)
> >
> > Oops, the newest -mm just came out without any of the driver core
> > patches in it due to the problems. I'll wait until the next -mm release
> > then, and try to go catch up on my pending-patch-queue right now
> > instead...
>
> Let me know when
> http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver/
> is ready to go and I'll prepare a new rollup.
It should be ready to go right now. Fire away :)
thanks,
greg k-h
On Wed, 01 Nov 2006 22:32:23 -0800
"Martin J. Bligh" <[email protected]> wrote:
> > Oops, the newest -mm just came out without any of the driver core
> > patches in it due to the problems. I'll wait until the next -mm release
> > then, and try to go catch up on my pending-patch-queue right now
> > instead...
>
> If we can test it out of sync, it'd save potentially messing up another
> -mm cycle. The problem is that it blocks lots of other patches from
> getting tested ...
is OK - I wasn't doing anything useful anyway.
On Wed, 1 Nov 2006 22:42:27 -0800
Greg KH <[email protected]> wrote:
> On Wed, Nov 01, 2006 at 10:07:01PM -0800, Andrew Morton wrote:
> > On Wed, 1 Nov 2006 22:02:25 -0800
> > Greg KH <[email protected]> wrote:
> >
> > > > Thanks for fixing this up. If you could post a diff somewhere against
> > > > either mainline or -mm, would make it easy to run through
> > > > test.kernel.org before you wake up tommorow ;-)
> > >
> > > Oops, the newest -mm just came out without any of the driver core
> > > patches in it due to the problems. I'll wait until the next -mm release
> > > then, and try to go catch up on my pending-patch-queue right now
> > > instead...
> >
> > Let me know when
> > http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver/
> > is ready to go and I'll prepare a new rollup.
>
> It should be ready to go right now. Fire away :)
>
Poor Cornelia. All her patches broke again.
On Wed, Nov 01, 2006 at 10:49:15PM -0800, Andrew Morton wrote:
> On Wed, 1 Nov 2006 22:42:27 -0800
> Greg KH <[email protected]> wrote:
>
> > On Wed, Nov 01, 2006 at 10:07:01PM -0800, Andrew Morton wrote:
> > > On Wed, 1 Nov 2006 22:02:25 -0800
> > > Greg KH <[email protected]> wrote:
> > >
> > > > > Thanks for fixing this up. If you could post a diff somewhere against
> > > > > either mainline or -mm, would make it easy to run through
> > > > > test.kernel.org before you wake up tommorow ;-)
> > > >
> > > > Oops, the newest -mm just came out without any of the driver core
> > > > patches in it due to the problems. I'll wait until the next -mm release
> > > > then, and try to go catch up on my pending-patch-queue right now
> > > > instead...
> > >
> > > Let me know when
> > > http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver/
> > > is ready to go and I'll prepare a new rollup.
> >
> > It should be ready to go right now. Fire away :)
> >
>
> Poor Cornelia. All her patches broke again.
Yeah, I knew that would happen. I have them still in my queue, I'll
handle porting them to my tree now, I've forced her to handle my
mistakes too much already :)
So you can drop them now, I'll get to them tomorrow.
Let's verify that this all is fixed first :)
thanks,
greg k-h
Greg KH wrote:
> On Wed, Nov 01, 2006 at 10:49:15PM -0800, Andrew Morton wrote:
>> On Wed, 1 Nov 2006 22:42:27 -0800
>> Greg KH <[email protected]> wrote:
>>
>>> On Wed, Nov 01, 2006 at 10:07:01PM -0800, Andrew Morton wrote:
>>>> On Wed, 1 Nov 2006 22:02:25 -0800
>>>> Greg KH <[email protected]> wrote:
>>>>
>>>>>> Thanks for fixing this up. If you could post a diff somewhere against
>>>>>> either mainline or -mm, would make it easy to run through
>>>>>> test.kernel.org before you wake up tommorow ;-)
>>>>> Oops, the newest -mm just came out without any of the driver core
>>>>> patches in it due to the problems. I'll wait until the next -mm release
>>>>> then, and try to go catch up on my pending-patch-queue right now
>>>>> instead...
>>>> Let me know when
>>>> http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver/
>>>> is ready to go and I'll prepare a new rollup.
>>> It should be ready to go right now. Fire away :)
>>>
>> Poor Cornelia. All her patches broke again.
>
> Yeah, I knew that would happen. I have them still in my queue, I'll
> handle porting them to my tree now, I've forced her to handle my
> mistakes too much already :)
>
> So you can drop them now, I'll get to them tomorrow.
>
> Let's verify that this all is fixed first :)
If you can trivially produce a single patch against 2.6.19-rc3-mm1 or
2.6.19-rc4-mm1 (or any other tree :)) I can shove it through TKO and see
what comes out; and I'd say its worth it.
-apw
On Wed, 1 Nov 2006 22:56:09 -0800,
Greg KH <[email protected]> wrote:
> Yeah, I knew that would happen. I have them still in my queue, I'll
> handle porting them to my tree now, I've forced her to handle my
> mistakes too much already :)
Thanks for sorting that out :)
> Let's verify that this all is fixed first :)
Seems to work fine for me now.
--
Cornelia Huck
Linux for zSeries Developer
Tel.: +49-7031-16-4837, Mail: [email protected]
On Thu, Nov 02, 2006 at 11:26:03AM +0100, Cornelia Huck wrote:
> On Wed, 1 Nov 2006 22:56:09 -0800,
> Greg KH <[email protected]> wrote:
>
> > Yeah, I knew that would happen. I have them still in my queue, I'll
> > handle porting them to my tree now, I've forced her to handle my
> > mistakes too much already :)
>
> Thanks for sorting that out :)
>
> > Let's verify that this all is fixed first :)
>
> Seems to work fine for me now.
Thanks for testing this and letting me know.
greg k-h
