* Bisecting tip/auto-x86-next?
@ 2008-06-20 0:40 Kevin Winchester
2008-06-20 7:15 ` Sitsofe Wheeler
` (3 more replies)
0 siblings, 4 replies; 21+ messages in thread
From: Kevin Winchester @ 2008-06-20 0:40 UTC (permalink / raw)
To: Ingo Molnar, Thomas Gleixner, H. Peter Anvin; +Cc: Linux Kernel Mailing List
Hi,
I am trying to track down a problem I reported here:
http://lkml.org/lkml/2008/6/11/431
None or you were cc'd on the original report because I had no idea of
the source of the issue. However, I have now narrowed down the problem
to the auto-x86-next tree. Thus I did something like:
$ git bisect start
$ git bisect good linus/master
$ git bisect bad tip/auto-x86-next
which resulted in only about 170 or so revisions to test (sounds better
than the 3000 or so that -next wanted me to bisect through). However,
when I tried to compile the bisect-chosen commit, I get:
------------------
In file included from include/asm/thread_info.h:5,
from include/linux/thread_info.h:47,
from include/linux/preempt.h:9,
from include/linux/spinlock.h:49,
from include/linux/seqlock.h:29,
from include/linux/time.h:8,
from include/linux/stat.h:60,
from include/linux/module.h:10,
from crypto/sha1_generic.c:20:
include/asm/thread_info_64.h: In function ‘set_restore_sigmask’:
include/asm/thread_info_64.h:189: warning: passing argument 2 of
‘set_bit’ from incompatible pointer type
-----------------
Can I ignore these warnings and keep building the kernel anyway? Or is
there a way to work around this problem? Am I allowed to cherry pick a
particular commit to apply on top of the bisect-chosen commit, or will
that ruin the process? Can I manually choose a bisection point right
after this warning was fixed? Is it likely that the fix for this
warning will get rearranged in the tree before Linus pulls it so that
other don't run into this same bisection problem?
Is that enough questions?
Thanks,
--
Kevin Winchester
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: Bisecting tip/auto-x86-next? 2008-06-20 0:40 Bisecting tip/auto-x86-next? Kevin Winchester @ 2008-06-20 7:15 ` Sitsofe Wheeler 2008-06-20 10:04 ` Ingo Molnar ` (2 subsequent siblings) 3 siblings, 0 replies; 21+ messages in thread From: Sitsofe Wheeler @ 2008-06-20 7:15 UTC (permalink / raw) To: linux-kernel On Thu, 19 Jun 2008 21:40:59 -0300, Kevin Winchester wrote: > I am trying to track down a problem I reported here: > > http://lkml.org/lkml/2008/6/11/431 > [...] > > that ruin the process? Can I manually choose a bisection point right > after this warning was fixed? Is it likely that the fix for this You certainly can move the bisection point. If you look at man git-bisect it will mention the following: "Avoiding to test a commit If in a middle of bisect session, you know what the bisect suggested to try next is not a good one to test (e.g. the change the commit introduces is known not to work in your environment and you know it does not have anything to do with the bug you are chasing), you may want to find a near-by commit and try that instead. It goes something like this: $ git bisect good/bad # previous round was good/bad. Bisecting: 337 revisions left to test after this $ git bisect visualize # oops, that is uninteresting. $ git reset --hard HEAD~3 # try 3 revs before what # was suggested Then compile and test the one you chose to try. After that, tell bisect what the result was as usual." It can be helpful to use gitk on the point that git bisect chooses/git bisect visualise to see a graphical view of what's around it and then use git reset <commitrev> to move yourself to a particular commit. You can still use git bisect good/bad when you have moved to a particular commit so long as the bisection processes has started. -- Sitsofe | http://sucs.org/~sits/ ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-20 0:40 Bisecting tip/auto-x86-next? Kevin Winchester 2008-06-20 7:15 ` Sitsofe Wheeler @ 2008-06-20 10:04 ` Ingo Molnar 2008-06-20 22:23 ` Kevin Winchester 2008-06-20 10:07 ` Ingo Molnar 2008-06-20 10:17 ` Ingo Molnar 3 siblings, 1 reply; 21+ messages in thread From: Ingo Molnar @ 2008-06-20 10:04 UTC (permalink / raw) To: Kevin Winchester Cc: Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List * Kevin Winchester <kjwinchester@gmail.com> wrote: > > Hi, > > I am trying to track down a problem I reported here: > > http://lkml.org/lkml/2008/6/11/431 > > None or you were cc'd on the original report because I had no idea of > the source of the issue. However, I have now narrowed down the problem > to the auto-x86-next tree. Thus I did something like: > > $ git bisect start > $ git bisect good linus/master > $ git bisect bad tip/auto-x86-next > > which resulted in only about 170 or so revisions to test (sounds better > than the 3000 or so that -next wanted me to bisect through). However, > when I tried to compile the bisect-chosen commit, I get: > > ------------------ > > In file included from include/asm/thread_info.h:5, > from include/linux/thread_info.h:47, > from include/linux/preempt.h:9, > from include/linux/spinlock.h:49, > from include/linux/seqlock.h:29, > from include/linux/time.h:8, > from include/linux/stat.h:60, > from include/linux/module.h:10, > from crypto/sha1_generic.c:20: > include/asm/thread_info_64.h: In function ‘set_restore_sigmask’: > include/asm/thread_info_64.h:189: warning: passing argument 2 of > ‘set_bit’ from incompatible pointer type hm, could you send me the config that triggered this? Ingo ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-20 10:04 ` Ingo Molnar @ 2008-06-20 22:23 ` Kevin Winchester 0 siblings, 0 replies; 21+ messages in thread From: Kevin Winchester @ 2008-06-20 22:23 UTC (permalink / raw) To: Ingo Molnar Cc: Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List Ingo Molnar wrote: > * Kevin Winchester <kjwinchester@gmail.com> wrote: > >> Hi, >> >> I am trying to track down a problem I reported here: >> >> http://lkml.org/lkml/2008/6/11/431 >> >> None or you were cc'd on the original report because I had no idea of >> the source of the issue. However, I have now narrowed down the problem >> to the auto-x86-next tree. Thus I did something like: >> >> $ git bisect start >> $ git bisect good linus/master >> $ git bisect bad tip/auto-x86-next >> >> which resulted in only about 170 or so revisions to test (sounds better >> than the 3000 or so that -next wanted me to bisect through). However, >> when I tried to compile the bisect-chosen commit, I get: >> >> ------------------ >> >> In file included from include/asm/thread_info.h:5, >> from include/linux/thread_info.h:47, >> from include/linux/preempt.h:9, >> from include/linux/spinlock.h:49, >> from include/linux/seqlock.h:29, >> from include/linux/time.h:8, >> from include/linux/stat.h:60, >> from include/linux/module.h:10, >> from crypto/sha1_generic.c:20: >> include/asm/thread_info_64.h: In function ‘set_restore_sigmask’: >> include/asm/thread_info_64.h:189: warning: passing argument 2 of >> ‘set_bit’ from incompatible pointer type > > hm, could you send me the config that triggered this? > As promised: # # Automatically generated make config: don't edit # Linux kernel version: 2.6.26-rc4 # Thu Jun 19 21:24:04 2008 # CONFIG_64BIT=y # CONFIG_X86_32 is not set CONFIG_X86_64=y CONFIG_X86=y CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" # CONFIG_GENERIC_LOCKBREAK is not set CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_FAST_CMPXCHG_LOCAL=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_GENERIC_GPIO is not set CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_GENERIC_SPINLOCK=y # CONFIG_RWSEM_XCHGADD_ALGORITHM is not set # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y # CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ZONE_DMA32=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_AOUT=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_X86_TRAMPOLINE=y # CONFIG_KTIME_SCALAR is not set CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y # CONFIG_SYSVIPC is not set # CONFIG_POSIX_MQUEUE is not set # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=17 # CONFIG_CGROUPS is not set CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_GROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y # CONFIG_RT_GROUP_SCHED is not set CONFIG_USER_SCHED=y # CONFIG_CGROUP_SCHED is not set # CONFIG_SYSFS_DEPRECATED_V2 is not set # CONFIG_RELAY is not set CONFIG_NAMESPACES=y # CONFIG_UTS_NS is not set # CONFIG_USER_NS is not set # CONFIG_PID_NS is not set # CONFIG_BLK_DEV_INITRD is not set CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_SYSCTL_SYSCALL_CHECK=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y # CONFIG_COMPAT_BRK is not set CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set # CONFIG_PROFILING is not set CONFIG_MARKERS=y CONFIG_HAVE_OPROFILE=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y # CONFIG_HAVE_DMA_ATTRS is not set CONFIG_PROC_PAGE_MONITOR=y CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_MODULES is not set CONFIG_BLOCK=y # CONFIG_BLK_DEV_IO_TRACE is not set CONFIG_BLK_DEV_BSG=y CONFIG_BLOCK_COMPAT=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y # CONFIG_IOSCHED_AS is not set # CONFIG_IOSCHED_DEADLINE is not set 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" # CONFIG_CLASSIC_RCU is not set # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y # 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_X86_RDC321X is not set # CONFIG_X86_VSMP is not set # CONFIG_PARAVIRT_GUEST is not set CONFIG_MEMTEST=y # 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 is not set CONFIG_MK8=y # 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_MVIAC7 is not set # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_CPU=y CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_DEBUGCTLMSR=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_DMI=y CONFIG_GART_IOMMU=y # CONFIG_CALGARY_IOMMU is not set CONFIG_SWIOTLB=y CONFIG_IOMMU_HELPER=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_RCU=y # CONFIG_RCU_TRACE is not set CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_INTEL is not set CONFIG_X86_MCE_AMD=y # CONFIG_I8K is not set # CONFIG_MICROCODE is not set CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_SELECT_MEMORY_MODEL=y # CONFIG_FLATMEM_MANUAL is not set # CONFIG_DISCONTIGMEM_MANUAL is not set CONFIG_SPARSEMEM_MANUAL=y CONFIG_SPARSEMEM=y CONFIG_HAVE_MEMORY_PRESENT=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_VMEMMAP=y # CONFIG_MEMORY_HOTPLUG is not set CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_RESOURCES_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_MTRR=y CONFIG_X86_PAT=y # CONFIG_EFI is not set # CONFIG_SECCOMP is not set # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set CONFIG_HZ_1000=y CONFIG_HZ=1000 CONFIG_SCHED_HRTICK=y # CONFIG_KEXEC is not set # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x200000 # CONFIG_RELOCATABLE is not set CONFIG_PHYSICAL_ALIGN=0x200000 # CONFIG_COMPAT_VDSO is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y # # Power management options # CONFIG_PM=y # CONFIG_PM_DEBUG is not set CONFIG_PM_SLEEP=y CONFIG_SUSPEND=y CONFIG_SUSPEND_FREEZER=y # CONFIG_HIBERNATION is not set CONFIG_ACPI=y CONFIG_ACPI_SLEEP=y # CONFIG_ACPI_PROCFS is not set # CONFIG_ACPI_PROCFS_POWER is not set CONFIG_ACPI_SYSFS_POWER=y CONFIG_ACPI_PROC_EVENT=y # CONFIG_ACPI_AC is not set # CONFIG_ACPI_BATTERY is not set CONFIG_ACPI_BUTTON=y CONFIG_ACPI_FAN=y CONFIG_ACPI_DOCK=y # CONFIG_ACPI_BAY is not set CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_WMI is not set # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_TOSHIBA is not set # CONFIG_ACPI_CUSTOM_DSDT is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y # CONFIG_ACPI_CONTAINER is not set # CONFIG_ACPI_SBS is not set # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y # CONFIG_CPU_FREQ_DEBUG is not set CONFIG_CPU_FREQ_STAT=y # CONFIG_CPU_FREQ_STAT_DETAILS is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_ONDEMAND=y # CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set # # CPUFreq processor drivers # # CONFIG_X86_ACPI_CPUFREQ is not set CONFIG_X86_POWERNOW_K8=y CONFIG_X86_POWERNOW_K8_ACPI=y # CONFIG_X86_SPEEDSTEP_CENTRINO is not set # CONFIG_X86_P4_CLOCKMOD is not set # # shared options # # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set # CONFIG_X86_SPEEDSTEP_LIB is not set CONFIG_CPU_IDLE=y CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y # # Bus options (PCI etc.) # CONFIG_PCI=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y CONFIG_PCI_DOMAINS=y # CONFIG_PCIEPORTBUS is not set CONFIG_ARCH_SUPPORTS_MSI=y # CONFIG_PCI_MSI is not set # CONFIG_PCI_LEGACY is not set # CONFIG_PCI_DEBUG is not set CONFIG_HT_IRQ=y CONFIG_ISA_DMA_API=y CONFIG_K8_NB=y # CONFIG_PCCARD is not set # CONFIG_HOTPLUG_PCI is not set # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y CONFIG_COMPAT_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_IA32_EMULATION=y # CONFIG_IA32_AOUT is not set CONFIG_COMPAT=y CONFIG_COMPAT_FOR_U64_ALIGNMENT=y # # Networking # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y # CONFIG_NET_KEY is not set CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_FIB_HASH=y # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set CONFIG_NET_IPGRE=y # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_XFRM_TUNNEL is not set # CONFIG_INET_TUNNEL is not set # CONFIG_INET_XFRM_MODE_TRANSPORT is not set # CONFIG_INET_XFRM_MODE_TUNNEL is not set # CONFIG_INET_XFRM_MODE_BEET is not set CONFIG_INET_LRO=y # CONFIG_INET_DIAG is not set # CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_CUBIC=y CONFIG_DEFAULT_TCP_CONG="cubic" # CONFIG_TCP_MD5SIG is not set # CONFIG_IPV6 is not set # CONFIG_NETWORK_SECMARK is not set # CONFIG_NETFILTER is not set # CONFIG_IP_DCCP is not set # CONFIG_IP_SCTP is not set # 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 # CONFIG_NET_SCHED is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_CAN is not set # CONFIG_IRDA is not set # CONFIG_BT is not set # CONFIG_AF_RXRPC is not set # # Wireless # # CONFIG_CFG80211 is not set # CONFIG_WIRELESS_EXT is not set # CONFIG_MAC80211 is not set # CONFIG_IEEE80211 is not set # CONFIG_RFKILL is not set # CONFIG_NET_9P is not set # # Device Drivers # # # Generic Driver Options # CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug" CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_FW_LOADER is not set # CONFIG_DEBUG_DRIVER is not set # CONFIG_DEBUG_DEVRES is not set # CONFIG_SYS_HYPERVISOR is not set # CONFIG_CONNECTOR is not set # CONFIG_MTD is not set # CONFIG_PARPORT is not set CONFIG_PNP=y # CONFIG_PNP_DEBUG is not set # # Protocols # CONFIG_PNPACPI=y CONFIG_BLK_DEV=y # 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 is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set # CONFIG_BLK_DEV_UB is not set # CONFIG_BLK_DEV_RAM is not set CONFIG_CDROM_PKTCDVD=y CONFIG_CDROM_PKTCDVD_BUFFERS=8 # CONFIG_CDROM_PKTCDVD_WCACHE is not set # CONFIG_ATA_OVER_ETH is not set # CONFIG_MISC_DEVICES is not set CONFIG_HAVE_IDE=y # CONFIG_IDE is not set # # SCSI device support # # CONFIG_RAID_ATTRS is not set CONFIG_SCSI=y CONFIG_SCSI_DMA=y CONFIG_SCSI_TGT=y # CONFIG_SCSI_NETLINK is not set # CONFIG_SCSI_PROC_FS is not set # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set CONFIG_BLK_DEV_SR=y # CONFIG_BLK_DEV_SR_VENDOR is not set CONFIG_CHR_DEV_SG=y # CONFIG_CHR_DEV_SCH is not set # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_MULTI_LUN is not set # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set CONFIG_SCSI_SCAN_ASYNC=y # # 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 # CONFIG_SCSI_SRP_ATTRS is not set # CONFIG_SCSI_LOWLEVEL is not set CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set CONFIG_ATA_ACPI=y # CONFIG_SATA_PMP is not set # CONFIG_SATA_AHCI is not set # CONFIG_SATA_SIL24 is not set CONFIG_ATA_SFF=y # CONFIG_SATA_SVW is not set # CONFIG_ATA_PIIX is not set # CONFIG_SATA_MV is not set # CONFIG_SATA_NV is not set # CONFIG_PDC_ADMA is not set # CONFIG_SATA_QSTOR is not set # CONFIG_SATA_PROMISE is not set # CONFIG_SATA_SX4 is not set CONFIG_SATA_SIL=y # CONFIG_SATA_SIS is not set # CONFIG_SATA_ULI is not set CONFIG_SATA_VIA=y # CONFIG_SATA_VITESSE is not set # CONFIG_SATA_INIC162X is not set # CONFIG_PATA_ACPI is not set # CONFIG_PATA_ALI is not set # CONFIG_PATA_AMD is not set # CONFIG_PATA_ARTOP is not set # CONFIG_PATA_ATIIXP is not set # CONFIG_PATA_CMD640_PCI is not set # CONFIG_PATA_CMD64X is not set # CONFIG_PATA_CS5520 is not set # CONFIG_PATA_CS5530 is not set # CONFIG_PATA_CYPRESS is not set # CONFIG_PATA_EFAR is not set # CONFIG_ATA_GENERIC is not set # CONFIG_PATA_HPT366 is not set # CONFIG_PATA_HPT37X is not set # CONFIG_PATA_HPT3X2N is not set # CONFIG_PATA_HPT3X3 is not set # CONFIG_PATA_IT821X is not set # CONFIG_PATA_IT8213 is not set # CONFIG_PATA_JMICRON is not set # CONFIG_PATA_TRIFLEX is not set # CONFIG_PATA_MARVELL is not set # CONFIG_PATA_MPIIX is not set # CONFIG_PATA_OLDPIIX is not set # CONFIG_PATA_NETCELL is not set # CONFIG_PATA_NINJA32 is not set # CONFIG_PATA_NS87410 is not set # CONFIG_PATA_NS87415 is not set # CONFIG_PATA_OPTI is not set # CONFIG_PATA_OPTIDMA is not set # CONFIG_PATA_PDC_OLD is not set # CONFIG_PATA_RADISYS is not set # CONFIG_PATA_RZ1000 is not set # CONFIG_PATA_SC1200 is not set # CONFIG_PATA_SERVERWORKS is not set # CONFIG_PATA_PDC2027X is not set # CONFIG_PATA_SIL680 is not set # CONFIG_PATA_SIS is not set CONFIG_PATA_VIA=y # CONFIG_PATA_WINBOND is not set # CONFIG_PATA_SCH is not set # CONFIG_MD is not set # CONFIG_FUSION is not set # # IEEE 1394 (FireWire) support # CONFIG_FIREWIRE=y CONFIG_FIREWIRE_OHCI=y CONFIG_FIREWIRE_OHCI_DEBUG=y # CONFIG_FIREWIRE_SBP2 is not set # CONFIG_IEEE1394 is not set # CONFIG_I2O is not set # CONFIG_MACINTOSH_DRIVERS is not set CONFIG_NETDEVICES=y # CONFIG_NETDEVICES_MULTIQUEUE is not set # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_MACVLAN is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # CONFIG_VETH is not set # CONFIG_NET_SB1000 is not set # CONFIG_ARCNET is not set # CONFIG_PHYLIB is not set 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 # CONFIG_NET_TULIP is not set # CONFIG_HP100 is not set # CONFIG_IBM_NEW_EMAC_ZMII is not set # CONFIG_IBM_NEW_EMAC_RGMII is not set # CONFIG_IBM_NEW_EMAC_TAH is not set # CONFIG_IBM_NEW_EMAC_EMAC4 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_EEPRO100 is not set # CONFIG_E100 is not set # CONFIG_FEALNX is not set # CONFIG_NATSEMI is not set # CONFIG_NE2K_PCI is not set # CONFIG_8139CP is not set # CONFIG_8139TOO is not set # CONFIG_R6040 is not set # CONFIG_SIS900 is not set # CONFIG_EPIC100 is not set # CONFIG_SUNDANCE is not set CONFIG_VIA_RHINE=y CONFIG_VIA_RHINE_MMIO=y # CONFIG_VIA_RHINE_NAPI is not set # CONFIG_SC92031 is not set CONFIG_NETDEV_1000=y # CONFIG_ACENIC is not set # CONFIG_DL2K is not set # CONFIG_E1000 is not set # CONFIG_E1000E is not set # CONFIG_E1000E_ENABLED is not set # CONFIG_IP1000 is not set # CONFIG_IGB 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_VIA_VELOCITY=y # CONFIG_TIGON3 is not set # CONFIG_BNX2 is not set # CONFIG_QLA3XXX is not set # CONFIG_ATL1 is not set # CONFIG_NETDEV_10000 is not set # CONFIG_TR is not set # # Wireless LAN # # CONFIG_WLAN_PRE80211 is not set # CONFIG_WLAN_80211 is not set # CONFIG_IWLWIFI_LEDS 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_WAN is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set CONFIG_PPP=y # CONFIG_PPP_MULTILINK is not set CONFIG_PPP_FILTER=y CONFIG_PPP_ASYNC=y CONFIG_PPP_SYNC_TTY=y # CONFIG_PPP_DEFLATE is not set # CONFIG_PPP_BSDCOMP is not set CONFIG_PPP_MPPE=y # CONFIG_PPPOE is not set # CONFIG_PPPOL2TP is not set # CONFIG_SLIP is not set CONFIG_SLHC=y # CONFIG_NET_FC is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # CONFIG_ISDN is not set # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # CONFIG_INPUT_FF_MEMLESS is not set # CONFIG_INPUT_POLLDEV is not set # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 # CONFIG_INPUT_JOYDEV is not set CONFIG_INPUT_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_TABLET 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_DEVKMEM is not set # CONFIG_SERIAL_NONSTANDARD is not set # CONFIG_NOZOMI is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set CONFIG_FIX_EARLYCON_MEM=y # # Non-8250 serial port support # # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y # CONFIG_LEGACY_PTYS is not set # CONFIG_IPMI_HANDLER is not set CONFIG_HW_RANDOM=y # CONFIG_HW_RANDOM_INTEL is not set # CONFIG_HW_RANDOM_AMD is not set # CONFIG_NVRAM is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # CONFIG_MWAVE is not set # CONFIG_PC8736x_GPIO is not set # CONFIG_RAW_DRIVER is not set CONFIG_HPET=y # CONFIG_HPET_RTC_IRQ is not set CONFIG_HPET_MMAP=y CONFIG_HANGCHECK_TIMER=y # CONFIG_TCG_TPM is not set # CONFIG_TELCLOCK is not set CONFIG_DEVPORT=y CONFIG_I2C=y CONFIG_I2C_BOARDINFO=y CONFIG_I2C_CHARDEV=y # # 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_I2C_SIMTEC is not set # CONFIG_I2C_SIS5595 is not set # CONFIG_I2C_SIS630 is not set # CONFIG_I2C_SIS96X is not set # CONFIG_I2C_TAOS_EVM is not set # CONFIG_I2C_TINY_USB is not set # CONFIG_I2C_VIA is not set CONFIG_I2C_VIAPRO=y # CONFIG_I2C_VOODOO3 is not set # CONFIG_I2C_PCA_PLATFORM is not set # # Miscellaneous I2C Chip support # # CONFIG_DS1682 is not set CONFIG_SENSORS_EEPROM=y # CONFIG_SENSORS_PCF8574 is not set # CONFIG_PCF8575 is not set # CONFIG_SENSORS_PCF8591 is not set # CONFIG_SENSORS_MAX6875 is not set # CONFIG_SENSORS_TSL2550 is not set # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set # CONFIG_I2C_DEBUG_CHIP is not set # CONFIG_SPI is not set # CONFIG_W1 is not set CONFIG_POWER_SUPPLY=y # CONFIG_POWER_SUPPLY_DEBUG is not set # CONFIG_PDA_POWER is not set # CONFIG_BATTERY_DS2760 is not set CONFIG_HWMON=y CONFIG_HWMON_VID=y CONFIG_SENSORS_ABITUGURU=y # CONFIG_SENSORS_ABITUGURU3 is not set # CONFIG_SENSORS_AD7418 is not set # CONFIG_SENSORS_ADM1021 is not set # CONFIG_SENSORS_ADM1025 is not set # CONFIG_SENSORS_ADM1026 is not set # CONFIG_SENSORS_ADM1029 is not set # CONFIG_SENSORS_ADM1031 is not set # CONFIG_SENSORS_ADM9240 is not set # CONFIG_SENSORS_ADT7470 is not set # CONFIG_SENSORS_ADT7473 is not set CONFIG_SENSORS_K8TEMP=y # CONFIG_SENSORS_ASB100 is not set # CONFIG_SENSORS_ATXP1 is not set # CONFIG_SENSORS_DS1621 is not set # CONFIG_SENSORS_I5K_AMB is not set # CONFIG_SENSORS_F71805F is not set # CONFIG_SENSORS_F71882FG is not set # CONFIG_SENSORS_F75375S is not set # CONFIG_SENSORS_FSCHER is not set # CONFIG_SENSORS_FSCPOS is not set # CONFIG_SENSORS_FSCHMD is not set # CONFIG_SENSORS_GL518SM is not set # CONFIG_SENSORS_GL520SM is not set # CONFIG_SENSORS_CORETEMP 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_LM93 is not set # CONFIG_SENSORS_MAX1619 is not set # CONFIG_SENSORS_MAX6650 is not set # CONFIG_SENSORS_PC87360 is not set # CONFIG_SENSORS_PC87427 is not set # CONFIG_SENSORS_SIS5595 is not set # CONFIG_SENSORS_DME1737 is not set # CONFIG_SENSORS_SMSC47M1 is not set # CONFIG_SENSORS_SMSC47M192 is not set # CONFIG_SENSORS_SMSC47B397 is not set # CONFIG_SENSORS_ADS7828 is not set # CONFIG_SENSORS_THMC50 is not set # CONFIG_SENSORS_VIA686A is not set # CONFIG_SENSORS_VT1211 is not set # CONFIG_SENSORS_VT8231 is not set # CONFIG_SENSORS_W83781D is not set # CONFIG_SENSORS_W83791D is not set # CONFIG_SENSORS_W83792D is not set # CONFIG_SENSORS_W83793 is not set # CONFIG_SENSORS_W83L785TS is not set # CONFIG_SENSORS_W83L786NG is not set CONFIG_SENSORS_W83627HF=y # CONFIG_SENSORS_W83627EHF is not set # CONFIG_SENSORS_HDAPS is not set # CONFIG_SENSORS_APPLESMC is not set # CONFIG_HWMON_DEBUG_CHIP is not set CONFIG_THERMAL=y CONFIG_WATCHDOG=y # CONFIG_WATCHDOG_NOWAYOUT is not set # # Watchdog Device Drivers # # CONFIG_SOFT_WATCHDOG is not set # CONFIG_ACQUIRE_WDT is not set # CONFIG_ADVANTECH_WDT is not set # CONFIG_ALIM1535_WDT is not set # CONFIG_ALIM7101_WDT is not set # CONFIG_SC520_WDT is not set # CONFIG_EUROTECH_WDT is not set # CONFIG_IB700_WDT is not set # CONFIG_IBMASR is not set # CONFIG_WAFER_WDT is not set # CONFIG_I6300ESB_WDT is not set # CONFIG_ITCO_WDT is not set # CONFIG_IT8712F_WDT is not set # CONFIG_HP_WATCHDOG is not set # CONFIG_SC1200_WDT is not set # CONFIG_PC87413_WDT is not set # CONFIG_60XX_WDT is not set # CONFIG_SBC8360_WDT is not set # CONFIG_CPU5_WDT is not set # CONFIG_SMSC37B787_WDT is not set CONFIG_W83627HF_WDT=y # CONFIG_W83697HF_WDT is not set # CONFIG_W83877F_WDT is not set # CONFIG_W83977F_WDT is not set # CONFIG_MACHZ_WDT is not set # CONFIG_SBC_EPX_C3_WATCHDOG is not set # # PCI-based Watchdog Cards # # CONFIG_PCIPCWATCHDOG is not set # CONFIG_WDTPCI is not set # # USB-based Watchdog Cards # # CONFIG_USBPCWATCHDOG is not set # # Sonics Silicon Backplane # CONFIG_SSB_POSSIBLE=y # CONFIG_SSB is not set # # Multifunction device drivers # # CONFIG_MFD_SM501 is not set # CONFIG_HTC_PASIC3 is not set # # Multimedia devices # # # Multimedia core support # # CONFIG_VIDEO_DEV is not set # CONFIG_DVB_CORE is not set # CONFIG_VIDEO_MEDIA is not set # # Multimedia drivers # # CONFIG_DAB is not set # # Graphics support # CONFIG_AGP=y CONFIG_AGP_AMD64=y # CONFIG_AGP_INTEL is not set # CONFIG_AGP_SIS is not set # CONFIG_AGP_VIA is not set CONFIG_DRM=y # CONFIG_DRM_TDFX is not set # CONFIG_DRM_R128 is not set CONFIG_DRM_RADEON=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_VGASTATE is not set # CONFIG_VIDEO_OUTPUT_CONTROL is not set # CONFIG_FB is not set # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Display device support # # CONFIG_DISPLAY_SUPPORT 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 # # Sound # CONFIG_SOUND=y # # Advanced Linux Sound Architecture # CONFIG_SND=y CONFIG_SND_TIMER=y CONFIG_SND_PCM=y CONFIG_SND_RAWMIDI=y CONFIG_SND_SEQUENCER=y # CONFIG_SND_SEQ_DUMMY is not set CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=y CONFIG_SND_PCM_OSS=y CONFIG_SND_PCM_OSS_PLUGINS=y CONFIG_SND_SEQUENCER_OSS=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_PCSP is not set CONFIG_SND_MPU401_UART=y CONFIG_SND_AC97_CODEC=y # CONFIG_SND_DUMMY is not set # CONFIG_SND_VIRMIDI is not set # CONFIG_SND_MTPAV is not set # CONFIG_SND_SERIAL_U16550 is not set # CONFIG_SND_MPU401 is not set # # PCI devices # # CONFIG_SND_AD1889 is not set # CONFIG_SND_ALS300 is not set # CONFIG_SND_ALS4000 is not set # CONFIG_SND_ALI5451 is not set # CONFIG_SND_ATIIXP is not set # CONFIG_SND_ATIIXP_MODEM is not set # CONFIG_SND_AU8810 is not set # CONFIG_SND_AU8820 is not set # CONFIG_SND_AU8830 is not set # CONFIG_SND_AW2 is not set # CONFIG_SND_AZT3328 is not set # CONFIG_SND_BT87X is not set # CONFIG_SND_CA0106 is not set # CONFIG_SND_CMIPCI is not set # CONFIG_SND_OXYGEN is not set # CONFIG_SND_CS4281 is not set # CONFIG_SND_CS46XX is not set # CONFIG_SND_CS5530 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_HIFIER 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=y # CONFIG_SND_VIA82XX_MODEM is not set # CONFIG_SND_VIRTUOSO is not set # CONFIG_SND_VX222 is not set # CONFIG_SND_YMFPCI is not set CONFIG_SND_AC97_POWER_SAVE=y CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0 # # USB devices # # CONFIG_SND_USB_AUDIO is not set # CONFIG_SND_USB_USX2Y is not set # CONFIG_SND_USB_CAIAQ is not set # # System on Chip audio support # # CONFIG_SND_SOC is not set # # ALSA SoC audio for Freescale SOCs # # # SoC Audio for the Texas Instruments OMAP # # # Open Sound System # # CONFIG_SOUND_PRIME is not set CONFIG_AC97_BUS=y CONFIG_HID_SUPPORT=y CONFIG_HID=y # CONFIG_HID_DEBUG is not set # CONFIG_HIDRAW is not set # # USB Input Devices # CONFIG_USB_HID=y # CONFIG_USB_HIDINPUT_POWERBOOK is not set # CONFIG_HID_FF is not set # CONFIG_USB_HIDDEV is not set CONFIG_USB_SUPPORT=y 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 # CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y # CONFIG_USB_DEVICE_CLASS is not set # CONFIG_USB_DYNAMIC_MINORS is not set # CONFIG_USB_SUSPEND is not set # CONFIG_USB_OTG is not set # # USB Host Controller Drivers # # CONFIG_USB_C67X00_HCD is not set CONFIG_USB_EHCI_HCD=y CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_TT_NEWSCHED=y # CONFIG_USB_ISP116X_HCD is not set # CONFIG_USB_ISP1760_HCD is not set # CONFIG_USB_OHCI_HCD is not set CONFIG_USB_UHCI_HCD=y # CONFIG_USB_SL811_HCD is not set # CONFIG_USB_R8A66597_HCD is not set # # USB Device Class drivers # # CONFIG_USB_ACM is not set CONFIG_USB_PRINTER=y # CONFIG_USB_WDM is not set # # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' # # # may also be needed; see USB_STORAGE Help for more information # CONFIG_USB_STORAGE=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_ONETOUCH is not set # CONFIG_USB_STORAGE_KARMA is not set # CONFIG_USB_STORAGE_CYPRESS_ATACB is not set # CONFIG_USB_LIBUSUAL is not set # # USB Imaging devices # # CONFIG_USB_MDC800 is not set # CONFIG_USB_MICROTEK is not set # CONFIG_USB_MON is not set # # USB port drivers # # CONFIG_USB_SERIAL is not set # # USB Miscellaneous drivers # # CONFIG_USB_EMI62 is not set # CONFIG_USB_EMI26 is not set # CONFIG_USB_ADUTUX is not set # CONFIG_USB_AUERSWALD is not set # CONFIG_USB_RIO500 is not set # CONFIG_USB_LEGOTOWER is not set # CONFIG_USB_LCD is not set # CONFIG_USB_BERRY_CHARGE is not set # CONFIG_USB_LED is not set # CONFIG_USB_CYPRESS_CY7C63 is not set # CONFIG_USB_CYTHERM is not set # CONFIG_USB_PHIDGET is not set # CONFIG_USB_IDMOUSE is not set # CONFIG_USB_FTDI_ELAN is not set # CONFIG_USB_APPLEDISPLAY is not set # CONFIG_USB_SISUSBVGA is not set # CONFIG_USB_LD is not set # CONFIG_USB_TRANCEVIBRATOR is not set # CONFIG_USB_IOWARRIOR is not set # CONFIG_USB_TEST is not set # CONFIG_USB_ISIGHTFW is not set # CONFIG_USB_GADGET is not set # CONFIG_MMC is not set # CONFIG_MEMSTICK is not set # CONFIG_NEW_LEDS is not set # CONFIG_ACCESSIBILITY is not set # CONFIG_INFINIBAND is not set # CONFIG_EDAC is not set CONFIG_RTC_LIB=y CONFIG_RTC_CLASS=y CONFIG_RTC_HCTOSYS=y CONFIG_RTC_HCTOSYS_DEVICE="rtc0" # CONFIG_RTC_DEBUG is not set # # RTC interfaces # # CONFIG_RTC_INTF_SYSFS is not set # CONFIG_RTC_INTF_PROC is not set CONFIG_RTC_INTF_DEV=y CONFIG_RTC_INTF_DEV_UIE_EMUL=y # CONFIG_RTC_DRV_TEST is not set # # I2C RTC drivers # # CONFIG_RTC_DRV_DS1307 is not set # CONFIG_RTC_DRV_DS1374 is not set # CONFIG_RTC_DRV_DS1672 is not set # CONFIG_RTC_DRV_MAX6900 is not set # CONFIG_RTC_DRV_RS5C372 is not set # CONFIG_RTC_DRV_ISL1208 is not set # CONFIG_RTC_DRV_X1205 is not set # CONFIG_RTC_DRV_PCF8563 is not set # CONFIG_RTC_DRV_PCF8583 is not set # CONFIG_RTC_DRV_M41T80 is not set # CONFIG_RTC_DRV_S35390A is not set # # SPI RTC drivers # # # Platform RTC drivers # CONFIG_RTC_DRV_CMOS=y # CONFIG_RTC_DRV_DS1511 is not set # CONFIG_RTC_DRV_DS1553 is not set # CONFIG_RTC_DRV_DS1742 is not set # CONFIG_RTC_DRV_STK17TA8 is not set # CONFIG_RTC_DRV_M48T86 is not set # CONFIG_RTC_DRV_M48T59 is not set # CONFIG_RTC_DRV_V3020 is not set # # on-CPU RTC drivers # # CONFIG_DMADEVICES is not set # CONFIG_UIO is not set # # Firmware Drivers # # CONFIG_EDD is not set # CONFIG_DELL_RBU is not set # CONFIG_DCDBAS is not set # CONFIG_DMIID is not set # CONFIG_ISCSI_IBFT_FIND is not set # # File systems # CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y # CONFIG_EXT4DEV_FS is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set CONFIG_FS_POSIX_ACL=y # CONFIG_XFS_FS is not set # CONFIG_GFS2_FS is not set # CONFIG_OCFS2_FS is not set # CONFIG_DNOTIFY is not set CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y # CONFIG_QUOTA is not set # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # CONFIG_FUSE_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_UDF_FS=y CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=y # CONFIG_MSDOS_FS is not set 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 is not set # CONFIG_HUGETLB_PAGE is not set # 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_MINIX_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_ROMFS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # CONFIG_NETWORK_FILESYSTEMS is not set # # Partition Types # # CONFIG_PARTITION_ADVANCED is not set CONFIG_MSDOS_PARTITION=y 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 # CONFIG_DLM is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y CONFIG_PRINTK_TIME=y CONFIG_ENABLE_WARN_DEPRECATED=y # CONFIG_ENABLE_MUST_CHECK is not set CONFIG_FRAME_WARN=2048 CONFIG_MAGIC_SYSRQ=y # CONFIG_UNUSED_SYMBOLS is not set CONFIG_DEBUG_FS=y # CONFIG_HEADERS_CHECK is not set CONFIG_DEBUG_KERNEL=y CONFIG_DEBUG_SHIRQ=y CONFIG_DETECT_SOFTLOCKUP=y CONFIG_SCHED_DEBUG=y CONFIG_SCHEDSTATS=y # CONFIG_TIMER_STATS is not set CONFIG_DEBUG_OBJECTS=y CONFIG_DEBUG_OBJECTS_SELFTEST=y CONFIG_DEBUG_OBJECTS_FREE=y CONFIG_DEBUG_OBJECTS_TIMERS=y # CONFIG_SLUB_DEBUG_ON is not set # CONFIG_SLUB_STATS is not set CONFIG_DEBUG_PREEMPT=y 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_LOCK_ALLOC=y CONFIG_PROVE_LOCKING=y CONFIG_LOCKDEP=y # CONFIG_LOCK_STAT is not set CONFIG_DEBUG_LOCKDEP=y CONFIG_TRACE_IRQFLAGS=y CONFIG_DEBUG_SPINLOCK_SLEEP=y CONFIG_DEBUG_LOCKING_API_SELFTESTS=y CONFIG_STACKTRACE=y # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_INFO=y CONFIG_DEBUG_VM=y # CONFIG_DEBUG_WRITECOUNT is not set CONFIG_DEBUG_LIST=y CONFIG_DEBUG_SG=y CONFIG_FRAME_POINTER=y # CONFIG_BOOT_PRINTK_DELAY is not set # CONFIG_BACKTRACE_SELF_TEST is not set # CONFIG_FAULT_INJECTION is not set CONFIG_LATENCYTOP=y # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set # CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y # CONFIG_KGDB is not set CONFIG_NONPROMISC_DEVMEM=y CONFIG_EARLY_PRINTK=y CONFIG_DEBUG_STACKOVERFLOW=y # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PAGEALLOC is not set # CONFIG_X86_PTDUMP is not set CONFIG_DEBUG_RODATA=y CONFIG_DIRECT_GBPAGES=y CONFIG_DEBUG_RODATA_TEST=y CONFIG_X86_MPPARSE=y CONFIG_IOMMU_DEBUG=y CONFIG_IOMMU_LEAK=y CONFIG_IO_DELAY_TYPE_0X80=0 CONFIG_IO_DELAY_TYPE_0XED=1 CONFIG_IO_DELAY_TYPE_UDELAY=2 CONFIG_IO_DELAY_TYPE_NONE=3 # CONFIG_IO_DELAY_0X80 is not set # CONFIG_IO_DELAY_0XED is not set # CONFIG_IO_DELAY_UDELAY is not set CONFIG_IO_DELAY_NONE=y CONFIG_DEFAULT_IO_DELAY_TYPE=3 # CONFIG_DEBUG_BOOT_PARAMS is not set CONFIG_CPA_DEBUG=y # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # CONFIG_SECURITY_FILE_CAPABILITIES is not set CONFIG_CRYPTO=y # # Crypto core or helper # CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_MANAGER=y # CONFIG_CRYPTO_GF128MUL is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_CRYPTD is not set # CONFIG_CRYPTO_AUTHENC is not set # # Authenticated Encryption with Associated Data # # CONFIG_CRYPTO_CCM is not set # CONFIG_CRYPTO_GCM is not set # CONFIG_CRYPTO_SEQIV is not set # # Block modes # # CONFIG_CRYPTO_CBC is not set # CONFIG_CRYPTO_CTR is not set # CONFIG_CRYPTO_CTS is not set CONFIG_CRYPTO_ECB=y # CONFIG_CRYPTO_LRW is not set # CONFIG_CRYPTO_PCBC is not set # CONFIG_CRYPTO_XTS is not set # # Hash modes # CONFIG_CRYPTO_HMAC=y # CONFIG_CRYPTO_XCBC is not set # # Digest # # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=y # CONFIG_CRYPTO_MICHAEL_MIC is not set CONFIG_CRYPTO_SHA1=y CONFIG_CRYPTO_SHA256=y # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_TGR192 is not set # CONFIG_CRYPTO_WP512 is not set # # Ciphers # # CONFIG_CRYPTO_AES is not set # CONFIG_CRYPTO_AES_X86_64 is not set # CONFIG_CRYPTO_ANUBIS is not set CONFIG_CRYPTO_ARC4=y # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_CAMELLIA is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_DES is not set # CONFIG_CRYPTO_FCRYPT is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_SALSA20 is not set # CONFIG_CRYPTO_SALSA20_X86_64 is not set # CONFIG_CRYPTO_SEED is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_TWOFISH_X86_64 is not set # # Compression # # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_LZO is not set # CONFIG_CRYPTO_HW is not set CONFIG_HAVE_KVM=y # CONFIG_VIRTUALIZATION is not set # # Library routines # CONFIG_BITREVERSE=y CONFIG_GENERIC_FIND_FIRST_BIT=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_CRC_CCITT=y # CONFIG_CRC16 is not set CONFIG_CRC_ITU_T=y CONFIG_CRC32=y # CONFIG_CRC7 is not set # CONFIG_LIBCRC32C is not set CONFIG_ZLIB_INFLATE=y CONFIG_PLIST=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y -- Kevin Winchester ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-20 0:40 Bisecting tip/auto-x86-next? Kevin Winchester 2008-06-20 7:15 ` Sitsofe Wheeler 2008-06-20 10:04 ` Ingo Molnar @ 2008-06-20 10:07 ` Ingo Molnar 2008-06-20 10:17 ` Ingo Molnar 3 siblings, 0 replies; 21+ messages in thread From: Ingo Molnar @ 2008-06-20 10:07 UTC (permalink / raw) To: Kevin Winchester Cc: Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List * Kevin Winchester <kjwinchester@gmail.com> wrote: > include/asm/thread_info_64.h: In function ‘set_restore_sigmask’: > include/asm/thread_info_64.h:189: warning: passing argument 2 of > ‘set_bit’ from incompatible pointer type > > ----------------- > > Can I ignore these warnings and keep building the kernel anyway? [...] btw., you can probably ignore this one safely. Also please tell me at which commit ID you were at when you triggered this warning. Ingo ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-20 0:40 Bisecting tip/auto-x86-next? Kevin Winchester ` (2 preceding siblings ...) 2008-06-20 10:07 ` Ingo Molnar @ 2008-06-20 10:17 ` Ingo Molnar 2008-06-20 10:49 ` Pavel Machek ` (2 more replies) 3 siblings, 3 replies; 21+ messages in thread From: Ingo Molnar @ 2008-06-20 10:17 UTC (permalink / raw) To: Kevin Winchester Cc: Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Yinghai Lu, Rafael J. Wysocki, Pavel Machek * Kevin Winchester <kjwinchester@gmail.com> wrote: > Hi, > > I am trying to track down a problem I reported here: > > http://lkml.org/lkml/2008/6/11/431 [ GART related bootup crash. ] > None or you were cc'd on the original report because I had no idea of > the source of the issue. However, I have now narrowed down the > problem to the auto-x86-next tree. Thus I did something like: > > $ git bisect start > $ git bisect good linus/master > $ git bisect bad tip/auto-x86-next ok, in that case you can use tip's topical structure and probably bisect purely x86/gart, which has all x86 gart changes. I.e. do something like this: git-checkout tip/x86/gart build and boot that kernel, if it fails and mainline works then do: git-bisect reset git-bisect start git-bisect good linus/master git-bisect bad tip/x86/gart this should drastically reduce the number of bisection steps needed, to 3 or 4 iterations. Ingo ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-20 10:17 ` Ingo Molnar @ 2008-06-20 10:49 ` Pavel Machek 2008-06-20 11:40 ` Kevin Winchester 2008-06-20 10:51 ` Rafael J. Wysocki 2008-06-20 11:37 ` Kevin Winchester 2 siblings, 1 reply; 21+ messages in thread From: Pavel Machek @ 2008-06-20 10:49 UTC (permalink / raw) To: Ingo Molnar Cc: Kevin Winchester, Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Yinghai Lu, Rafael J. Wysocki Hi! > * Kevin Winchester <kjwinchester@gmail.com> wrote: > > Hi, > > > > I am trying to track down a problem I reported here: > > > > http://lkml.org/lkml/2008/6/11/431 Can you try iommu=memaper=2 ? Is it amd64 machine? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html pomozte zachranit klanovicky les: http://www.ujezdskystrom.info/ ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-20 10:49 ` Pavel Machek @ 2008-06-20 11:40 ` Kevin Winchester 0 siblings, 0 replies; 21+ messages in thread From: Kevin Winchester @ 2008-06-20 11:40 UTC (permalink / raw) To: Pavel Machek Cc: Ingo Molnar, Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Yinghai Lu, Rafael J. Wysocki On Fri, Jun 20, 2008 at 7:49 AM, Pavel Machek <pavel@suse.cz> wrote: > Hi! > >> * Kevin Winchester <kjwinchester@gmail.com> wrote: > >> > Hi, >> > >> > I am trying to track down a problem I reported here: >> > >> > http://lkml.org/lkml/2008/6/11/431 > > Can you try iommu=memaper=2 ? I should have mentioned that in the original post - I tried iommu=memaper=2, and got the identical result (including the message asking me to try iommu=memaper=2). Perhaps the message should not be printed if the user did actually provide that boot option. > > Is it amd64 machine? Yes it is, UP. Thanks, -- Kevin Winchester ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-20 10:17 ` Ingo Molnar 2008-06-20 10:49 ` Pavel Machek @ 2008-06-20 10:51 ` Rafael J. Wysocki 2008-06-20 11:37 ` Kevin Winchester 2 siblings, 0 replies; 21+ messages in thread From: Rafael J. Wysocki @ 2008-06-20 10:51 UTC (permalink / raw) To: Ingo Molnar Cc: Kevin Winchester, Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Yinghai Lu, Pavel Machek On Friday, 20 of June 2008, Ingo Molnar wrote: > > * Kevin Winchester <kjwinchester@gmail.com> wrote: > > > Hi, > > > > I am trying to track down a problem I reported here: > > > > http://lkml.org/lkml/2008/6/11/431 > > [ GART related bootup crash. ] Perhaps it's a good idea to bisect the GART branch of 'tip' alone, then. Not that I think my patch in there could affect bootup, as it only sets some variables during initialization. Still, the other patches in there could. Thanks, Rafael ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-20 10:17 ` Ingo Molnar 2008-06-20 10:49 ` Pavel Machek 2008-06-20 10:51 ` Rafael J. Wysocki @ 2008-06-20 11:37 ` Kevin Winchester 2008-06-20 15:36 ` Ingo Molnar 2 siblings, 1 reply; 21+ messages in thread From: Kevin Winchester @ 2008-06-20 11:37 UTC (permalink / raw) To: Ingo Molnar Cc: Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Yinghai Lu, Rafael J. Wysocki, Pavel Machek On Fri, Jun 20, 2008 at 7:17 AM, Ingo Molnar <mingo@elte.hu> wrote: > > * Kevin Winchester <kjwinchester@gmail.com> wrote: > >> Hi, >> >> I am trying to track down a problem I reported here: >> >> http://lkml.org/lkml/2008/6/11/431 > > [ GART related bootup crash. ] It isn't actually a crash - X comes up fine, just without direct rendering (which really kills KDE4 performance). > >> None or you were cc'd on the original report because I had no idea of >> the source of the issue. However, I have now narrowed down the >> problem to the auto-x86-next tree. Thus I did something like: >> >> $ git bisect start >> $ git bisect good linus/master >> $ git bisect bad tip/auto-x86-next > > ok, in that case you can use tip's topical structure and probably bisect > purely x86/gart, which has all x86 gart changes. > > I.e. do something like this: > > git-checkout tip/x86/gart > > build and boot that kernel, if it fails and mainline works then do: > > git-bisect reset > git-bisect start > git-bisect good linus/master > git-bisect bad tip/x86/gart > > this should drastically reduce the number of bisection steps needed, to > 3 or 4 iterations. > Thanks - I'll give this a try tonight. As to your other emails: > hm, could you send me the config that triggered this? I will do so tonight when I am home again. It is a UP AMD64 box with a VIA chipset, if that helps. > btw., you can probably ignore this one safely. Also please tell me at > which commit ID you were at when you triggered this warning. Good to know - I will get the commit ID tonight as well, although wouldn't following the same bisection sequence that I did give you the same bisection point? I guess that would assume that linus/master and auto-x86-next haven't changed much since last night, which might not be correct. Thanks, -- Kevin Winchester ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-20 11:37 ` Kevin Winchester @ 2008-06-20 15:36 ` Ingo Molnar 2008-06-21 0:00 ` Kevin Winchester 0 siblings, 1 reply; 21+ messages in thread From: Ingo Molnar @ 2008-06-20 15:36 UTC (permalink / raw) To: Kevin Winchester Cc: Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Yinghai Lu, Rafael J. Wysocki, Pavel Machek * Kevin Winchester <kjwinchester@gmail.com> wrote: > > hm, could you send me the config that triggered this? > > I will do so tonight when I am home again. It is a UP AMD64 box with > a VIA chipset, if that helps. > > > btw., you can probably ignore this one safely. Also please tell me > > at which commit ID you were at when you triggered this warning. > > Good to know - I will get the commit ID tonight as well, although > wouldn't following the same bisection sequence that I did give you the > same bisection point? I guess that would assume that linus/master and > auto-x86-next haven't changed much since last night, which might not > be correct. yeah, you'd probably not hit that warning with the x86/gart bisection sequence. (Assuming the bug is introduced in that branch - so you should first check whether pure x86/gart kernel triggers the problem too.) If you still have the commit ID around then please send it - if you dont, no problem, it's no big issue. I wanted to check how wide the bisection window is where the warning triggers. Ingo ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-20 15:36 ` Ingo Molnar @ 2008-06-21 0:00 ` Kevin Winchester 2008-06-21 0:14 ` Yinghai Lu 0 siblings, 1 reply; 21+ messages in thread From: Kevin Winchester @ 2008-06-21 0:00 UTC (permalink / raw) To: Ingo Molnar Cc: Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Yinghai Lu, Rafael J. Wysocki, Pavel Machek Ingo Molnar wrote: > * Kevin Winchester <kjwinchester@gmail.com> wrote: > >>> hm, could you send me the config that triggered this? >> I will do so tonight when I am home again. It is a UP AMD64 box with >> a VIA chipset, if that helps. >> >>> btw., you can probably ignore this one safely. Also please tell me >>> at which commit ID you were at when you triggered this warning. >> Good to know - I will get the commit ID tonight as well, although >> wouldn't following the same bisection sequence that I did give you the >> same bisection point? I guess that would assume that linus/master and >> auto-x86-next haven't changed much since last night, which might not >> be correct. > > yeah, you'd probably not hit that warning with the x86/gart bisection > sequence. (Assuming the bug is introduced in that branch - so you should > first check whether pure x86/gart kernel triggers the problem too.) > > If you still have the commit ID around then please send it - if you > dont, no problem, it's no big issue. I wanted to check how wide the > bisection window is where the warning triggers. > I'm sorry - I accidentally checkout out x86/gart to test it before grabbing the commit ID. I went ahead with the bisection and found: 8c9fd91a0dc503f085169d44f4360be025f75224 is first bad commit commit 8c9fd91a0dc503f085169d44f4360be025f75224 Author: Yinghai Lu <yhlu.kernel@gmail.com> Date: Sun Apr 13 18:42:31 2008 -0700 x86: checking aperture size order some systems are using 32M for gart and agp when memory is less than 4G. Kernel will reject and try to allcate another 64M that is not needed, and we will waste 64M of perfectly good RAM. this patch adds a workaround by checking aper_base/order between NB and agp bridge. If they are the same, and memory size is less than 4G, it will allow it. Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com> Signed-off-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> :040000 040000 848d6e4045a14d01fc0a794d4350d8a84f3ceff6 4a10a52b41309060cd5dc1bf0c322f6d43b2477b M arch :040000 040000 aa1cee87b1f5b1b30ed03ce6164ad7f404fef2a3 f9ce0aaa1f7d4fdc7bdc5a43285495db53a6f531 M drivers as the first bad commit. I do not have time to look at the patch right now, but in case anyone else does, I figured I would post it. Thanks, -- Kevin Winchester ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-21 0:00 ` Kevin Winchester @ 2008-06-21 0:14 ` Yinghai Lu 2008-06-21 10:00 ` Kevin Winchester 0 siblings, 1 reply; 21+ messages in thread From: Yinghai Lu @ 2008-06-21 0:14 UTC (permalink / raw) To: Kevin Winchester Cc: Ingo Molnar, Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Rafael J. Wysocki, Pavel Machek On Fri, Jun 20, 2008 at 5:00 PM, Kevin Winchester <kjwinchester@gmail.com> wrote: > Ingo Molnar wrote: >> >> * Kevin Winchester <kjwinchester@gmail.com> wrote: >> >>>> hm, could you send me the config that triggered this? >>> >>> I will do so tonight when I am home again. It is a UP AMD64 box with a >>> VIA chipset, if that helps. >>> >>>> btw., you can probably ignore this one safely. Also please tell me at >>>> which commit ID you were at when you triggered this warning. >>> >>> Good to know - I will get the commit ID tonight as well, although >>> wouldn't following the same bisection sequence that I did give you the same >>> bisection point? I guess that would assume that linus/master and >>> auto-x86-next haven't changed much since last night, which might not be >>> correct. >> >> yeah, you'd probably not hit that warning with the x86/gart bisection >> sequence. (Assuming the bug is introduced in that branch - so you should >> first check whether pure x86/gart kernel triggers the problem too.) >> >> If you still have the commit ID around then please send it - if you dont, >> no problem, it's no big issue. I wanted to check how wide the bisection >> window is where the warning triggers. >> > > I'm sorry - I accidentally checkout out x86/gart to test it before grabbing > the commit ID. > > I went ahead with the bisection and found: > > > > 8c9fd91a0dc503f085169d44f4360be025f75224 is first bad commit > commit 8c9fd91a0dc503f085169d44f4360be025f75224 > Author: Yinghai Lu <yhlu.kernel@gmail.com> > Date: Sun Apr 13 18:42:31 2008 -0700 > > x86: checking aperture size order > > some systems are using 32M for gart and agp when memory is less than 4G. > Kernel will reject and try to allcate another 64M that is not needed, > and we will waste 64M of perfectly good RAM. > > this patch adds a workaround by checking aper_base/order between NB and > agp bridge. If they are the same, and memory size is less than 4G, it > will allow it. > > Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com> > Signed-off-by: Ingo Molnar <mingo@elte.hu> > Signed-off-by: Thomas Gleixner <tglx@linutronix.de> > > :040000 040000 848d6e4045a14d01fc0a794d4350d8a84f3ceff6 > 4a10a52b41309060cd5dc1bf0c322f6d43b2477b M arch > :040000 040000 aa1cee87b1f5b1b30ed03ce6164ad7f404fef2a3 > f9ce0aaa1f7d4fdc7bdc5a43285495db53a6f531 M drivers > > > as the first bad commit. I do not have time to look at the patch right now, > but in case anyone else does, I figured I would post it. > please send out whole boot logs with "debug" in command line. YH ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-21 0:14 ` Yinghai Lu @ 2008-06-21 10:00 ` Kevin Winchester 2008-06-21 10:18 ` Yinghai Lu 0 siblings, 1 reply; 21+ messages in thread From: Kevin Winchester @ 2008-06-21 10:00 UTC (permalink / raw) To: Yinghai Lu Cc: Ingo Molnar, Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Rafael J. Wysocki, Pavel Machek Yinghai Lu wrote: > On Fri, Jun 20, 2008 at 5:00 PM, Kevin Winchester > <kjwinchester@gmail.com> wrote: >> Ingo Molnar wrote: >>> * Kevin Winchester <kjwinchester@gmail.com> wrote: >>> >>>>> hm, could you send me the config that triggered this? >>>> I will do so tonight when I am home again. It is a UP AMD64 box with a >>>> VIA chipset, if that helps. >>>> >>>>> btw., you can probably ignore this one safely. Also please tell me at >>>>> which commit ID you were at when you triggered this warning. >>>> Good to know - I will get the commit ID tonight as well, although >>>> wouldn't following the same bisection sequence that I did give you the same >>>> bisection point? I guess that would assume that linus/master and >>>> auto-x86-next haven't changed much since last night, which might not be >>>> correct. >>> yeah, you'd probably not hit that warning with the x86/gart bisection >>> sequence. (Assuming the bug is introduced in that branch - so you should >>> first check whether pure x86/gart kernel triggers the problem too.) >>> >>> If you still have the commit ID around then please send it - if you dont, >>> no problem, it's no big issue. I wanted to check how wide the bisection >>> window is where the warning triggers. >>> >> I'm sorry - I accidentally checkout out x86/gart to test it before grabbing >> the commit ID. >> >> I went ahead with the bisection and found: >> >> >> >> 8c9fd91a0dc503f085169d44f4360be025f75224 is first bad commit >> commit 8c9fd91a0dc503f085169d44f4360be025f75224 >> Author: Yinghai Lu <yhlu.kernel@gmail.com> >> Date: Sun Apr 13 18:42:31 2008 -0700 >> >> x86: checking aperture size order >> >> some systems are using 32M for gart and agp when memory is less than 4G. >> Kernel will reject and try to allcate another 64M that is not needed, >> and we will waste 64M of perfectly good RAM. >> >> this patch adds a workaround by checking aper_base/order between NB and >> agp bridge. If they are the same, and memory size is less than 4G, it >> will allow it. >> >> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com> >> Signed-off-by: Ingo Molnar <mingo@elte.hu> >> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> >> >> :040000 040000 848d6e4045a14d01fc0a794d4350d8a84f3ceff6 >> 4a10a52b41309060cd5dc1bf0c322f6d43b2477b M arch >> :040000 040000 aa1cee87b1f5b1b30ed03ce6164ad7f404fef2a3 >> f9ce0aaa1f7d4fdc7bdc5a43285495db53a6f531 M drivers >> >> >> as the first bad commit. I do not have time to look at the patch right now, >> but in case anyone else does, I figured I would post it. >> > > please send out whole boot logs with "debug" in command line. > "debug" in the command line doesn't seem to have any effect on the printout (is there some config option I need to use with it?), but here it is anyway: [ 0.000000] Linux version 2.6.26-rc2-00003-g8c9fd91 (kevin@alekhine) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #53 PREEMPT Sat Jun 21 06:53:46 ADT 2008 [ 0.000000] Command line: root=/dev/sda1 ro hpet=force debug [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable) [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) [ 0.000000] BIOS-e820: 0000000000100000 - 000000003fef0000 (usable) [ 0.000000] BIOS-e820: 000000003fef0000 - 000000003fef3000 (ACPI NVS) [ 0.000000] BIOS-e820: 000000003fef3000 - 000000003ff00000 (ACPI data) [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved) [ 0.000000] update e820 for GART [ 0.000000] modified physical RAM map: [ 0.000000] modified: 0000000000000000 - 000000000009f800 (usable) [ 0.000000] modified: 000000000009f800 - 00000000000a0000 (reserved) [ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved) [ 0.000000] modified: 0000000000100000 - 000000003fef0000 (usable) [ 0.000000] modified: 000000003fef0000 - 000000003fef3000 (ACPI NVS) [ 0.000000] modified: 000000003fef3000 - 000000003ff00000 (ACPI data) [ 0.000000] modified: 00000000e0000000 - 00000000e8000000 (reserved) [ 0.000000] modified: 00000000fec00000 - 0000000100000000 (reserved) [ 0.000000] Entering add_active_range(0, 0, 159) 0 entries of 256 used [ 0.000000] Entering add_active_range(0, 256, 261872) 1 entries of 256 used [ 0.000000] max_pfn_mapped = 1048576 [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [ 0.000000] init_memory_mapping [ 0.000000] DMI 2.3 present. [ 0.000000] ACPI: RSDP 000F77D0, 0014 (r0 VIAK8T) [ 0.000000] ACPI: RSDT 3FEF3040, 0034 (r1 VIAK8T AWRDACPI 42302E31 AWRD 0) [ 0.000000] ACPI: FACP 3FEF30C0, 0074 (r1 VIAK8T AWRDACPI 42302E31 AWRD 0) [ 0.000000] ACPI: DSDT 3FEF3180, 4F8A (r1 VIAK8T AWRDACPI 1000 MSFT 100000E) [ 0.000000] ACPI: FACS 3FEF0000, 0040 [ 0.000000] ACPI: BOOT 3FEF8180, 0028 (r1 VIAK8T AWRDACPI 42302E31 AWRD 0) [ 0.000000] ACPI: SSDT 3FEF82C0, 00B5 (r1 PTLTD POWERNOW 1 LTP 1) [ 0.000000] ACPI: APIC 3FEF8200, 0068 (r1 VIAK8T AWRDACPI 42302E31 AWRD 0) [ 0.000000] Entering add_active_range(0, 0, 159) 0 entries of 256 used [ 0.000000] Entering add_active_range(0, 256, 261872) 1 entries of 256 used [ 0.000000] early res: 0 [0-fff] BIOS data page [ 0.000000] early res: 1 [6000-7fff] TRAMPOLINE [ 0.000000] early res: 2 [200000-b0c907] TEXT DATA BSS [ 0.000000] early res: 3 [9f800-fffff] BIOS reserved [ 0.000000] early res: 4 [8000-afff] PGTABLE [ 0.000000] [ffffe20000000000-ffffe20000dfffff] PMD -> [ffff810001200000-ffff810001ffffff] on node 0 [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0 -> 4096 [ 0.000000] DMA32 4096 -> 1048576 [ 0.000000] Normal 1048576 -> 1048576 [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[2] active PFN ranges [ 0.000000] 0: 0 -> 159 [ 0.000000] 0: 256 -> 261872 [ 0.000000] On node 0 totalpages: 261775 [ 0.000000] DMA zone: 56 pages used for memmap [ 0.000000] DMA zone: 2420 pages reserved [ 0.000000] DMA zone: 1523 pages, LIFO batch:0 [ 0.000000] DMA32 zone: 3524 pages used for memmap [ 0.000000] DMA32 zone: 254252 pages, LIFO batch:31 [ 0.000000] Normal zone: 0 pages used for memmap [ 0.000000] Movable zone: 0 pages used for memmap [ 0.000000] Looks like a VIA chipset. Disabling IOMMU. Override with iommu=allowed [ 0.000000] ACPI: PM-Timer IO Port: 0x4008 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 2, version 0, address 0xfec00000, GSI 0-23 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) [ 0.000000] ACPI: IRQ0 used by override. [ 0.000000] ACPI: IRQ2 used by override. [ 0.000000] ACPI: IRQ9 used by override. [ 0.000000] Setting APIC routing to flat [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] Allocating PCI resources starting at 40000000 (gap: 3ff00000:a0100000) [4294014.506571] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 255775 [4294014.506571] Kernel command line: root=/dev/sda1 ro hpet=force debug [4294014.506571] Initializing CPU#0 [4294014.506571] Preemptible RCU implementation. [4294014.506571] PID hash table entries: 4096 (order: 12, 32768 bytes) [4294014.506571] TSC calibrated against PM_TIMER [4294014.506571] time.c: Detected 1804.093 MHz processor. [4294014.506571] Console: colour VGA+ 80x25 [4294014.506571] console [tty0] enabled [4294014.506571] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar [4294014.506571] ... MAX_LOCKDEP_SUBCLASSES: 8 [4294014.506571] ... MAX_LOCK_DEPTH: 48 [4294014.506571] ... MAX_LOCKDEP_KEYS: 2048 [4294014.506571] ... CLASSHASH_SIZE: 1024 [4294014.506571] ... MAX_LOCKDEP_ENTRIES: 8192 [4294014.506571] ... MAX_LOCKDEP_CHAINS: 16384 [4294014.506571] ... CHAINHASH_SIZE: 8192 [4294014.506571] memory used by lock dependency info: 1648 kB [4294014.506571] per task-struct memory footprint: 2688 bytes [4294014.506571] ------------------------ [4294014.506571] | Locking API testsuite: [4294014.506571] ---------------------------------------------------------------------------- [4294014.506571] | spin |wlock |rlock |mutex | wsem | rsem | [4294014.506571] -------------------------------------------------------------------------- [4294014.506571] A-A deadlock: ok | ok | ok | ok | ok | ok | [4294014.506571] A-B-B-A deadlock: ok | ok | ok | ok | ok | ok | [4294014.506571] A-B-B-C-C-A deadlock: ok | ok | ok | ok | ok | ok | [4294014.506571] A-B-C-A-B-C deadlock: ok | ok | ok | ok | ok | ok | [4294014.506571] A-B-B-C-C-D-D-A deadlock: ok | ok | ok | ok | ok | ok | [4294014.506571] A-B-C-D-B-D-D-A deadlock: ok | ok | ok | ok | ok | ok | [4294014.506571] A-B-C-D-B-C-D-A deadlock: ok | ok | ok | ok | ok | ok | [4294014.506571] double unlock: ok | ok | ok | ok | ok | ok | [4294014.506571] initialize held: ok | ok | ok | ok | ok | ok | [4294014.506571] bad unlock order: ok | ok | ok | ok | ok | ok | [4294014.506571] -------------------------------------------------------------------------- [4294014.506571] recursive read-lock: | ok | | ok | [4294014.506571] recursive read-lock #2: | ok | | ok | [4294014.506571] mixed read-write-lock: | ok | | ok | [4294014.506571] mixed write-read-lock: | ok | | ok | [4294014.506571] -------------------------------------------------------------------------- [4294014.506571] hard-irqs-on + irq-safe-A/12: ok | ok | ok | [4294014.506571] soft-irqs-on + irq-safe-A/12: ok | ok | ok | [4294014.506571] hard-irqs-on + irq-safe-A/21: ok | ok | ok | [4294014.506571] soft-irqs-on + irq-safe-A/21: ok | ok | ok | [4294014.506571] sirq-safe-A => hirqs-on/12: ok | ok | ok | [4294014.506571] sirq-safe-A => hirqs-on/21: ok | ok | ok | [4294014.506571] hard-safe-A + irqs-on/12: ok | ok | ok | [4294014.506571] soft-safe-A + irqs-on/12: ok | ok | ok | [4294014.506571] hard-safe-A + irqs-on/21: ok | ok | ok | [4294014.506571] soft-safe-A + irqs-on/21: ok | ok | ok | [4294014.506571] hard-safe-A + unsafe-B #1/123: ok | ok | ok | [4294014.506571] soft-safe-A + unsafe-B #1/123: ok | ok | ok | [4294014.506571] hard-safe-A + unsafe-B #1/132: ok | ok | ok | [4294014.506571] soft-safe-A + unsafe-B #1/132: ok | ok | ok | [4294014.506571] hard-safe-A + unsafe-B #1/213: ok | ok | ok | [4294014.506571] soft-safe-A + unsafe-B #1/213: ok | ok | ok | [4294014.506571] hard-safe-A + unsafe-B #1/231: ok | ok | ok | [4294014.506571] soft-safe-A + unsafe-B #1/231: ok | ok | ok | [4294014.506571] hard-safe-A + unsafe-B #1/312: ok | ok | ok | [4294014.506571] soft-safe-A + unsafe-B #1/312: ok | ok | ok | [4294014.506571] hard-safe-A + unsafe-B #1/321: ok | ok | ok | [4294014.506571] soft-safe-A + unsafe-B #1/321: ok | ok | ok | [4294014.506571] hard-safe-A + unsafe-B #2/123: ok | ok | ok | [4294014.506571] soft-safe-A + unsafe-B #2/123: ok | ok | ok | [4294014.506571] hard-safe-A + unsafe-B #2/132: ok | ok | ok | [4294014.506571] soft-safe-A + unsafe-B #2/132: ok | ok | ok | [4294014.506571] hard-safe-A + unsafe-B #2/213: ok | ok | ok | [4294014.506571] soft-safe-A + unsafe-B #2/213: ok | ok | ok | [4294014.506571] hard-safe-A + unsafe-B #2/231: ok | ok | ok | [4294014.506571] soft-safe-A + unsafe-B #2/231: ok | ok | ok | [4294014.506571] hard-safe-A + unsafe-B #2/312: ok | ok | ok | [4294014.506571] soft-safe-A + unsafe-B #2/312: ok | ok | ok | [4294014.506571] hard-safe-A + unsafe-B #2/321: ok | ok | ok | [4294014.506571] soft-safe-A + unsafe-B #2/321: ok | ok | ok | [4294014.506571] hard-irq lock-inversion/123: ok | ok | ok | [4294014.506571] soft-irq lock-inversion/123: ok | ok | ok | [4294014.506571] hard-irq lock-inversion/132: ok | ok | ok | [4294014.506571] soft-irq lock-inversion/132: ok | ok | ok | [4294014.506571] hard-irq lock-inversion/213: ok | ok | ok | [4294014.506571] soft-irq lock-inversion/213: ok | ok | ok | [4294014.506571] hard-irq lock-inversion/231: ok | ok | ok | [4294014.506571] soft-irq lock-inversion/231: ok | ok | ok | [4294014.506571] hard-irq lock-inversion/312: ok | ok | ok | [4294014.506571] soft-irq lock-inversion/312: ok | ok | ok | [4294014.506571] hard-irq lock-inversion/321: ok | ok | ok | [4294014.506571] soft-irq lock-inversion/321: ok | ok | ok | [4294014.506571] hard-irq read-recursion/123: ok | [4294014.506571] soft-irq read-recursion/123: ok | [4294014.506571] hard-irq read-recursion/132: ok | [4294014.506571] soft-irq read-recursion/132: ok | [4294014.506571] hard-irq read-recursion/213: ok | [4294014.506571] soft-irq read-recursion/213: ok | [4294014.506571] hard-irq read-recursion/231: ok | [4294014.506571] soft-irq read-recursion/231: ok | [4294014.506571] hard-irq read-recursion/312: ok | [4294014.506571] soft-irq read-recursion/312: ok | [4294014.506571] hard-irq read-recursion/321: ok | [4294014.506571] soft-irq read-recursion/321: ok | [4294014.506571] ------------------------------------------------------- [4294014.506571] Good, all 218 testcases passed! | [4294014.506571] --------------------------------- [4294014.506571] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) [4294014.506571] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) [4294014.506571] Memory: 1021212k/1047488k available (2715k kernel code, 25316k reserved, 1315k data, 204k init) [4294014.506571] CPA: page pool initialized 1 of 1 pages preallocated [4294014.506571] SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [4294014.566594] Calibrating delay using timer specific routine.. 3611.98 BogoMIPS (lpj=1805993) [4294014.566707] Mount-cache hash table entries: 256 [4294014.567359] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [4294014.567403] CPU: L2 Cache: 512K (64 bytes/line) [4294014.567445] CPU: AMD Athlon(tm) 64 Processor 3000+ stepping 00 [4294014.567512] ACPI: Core revision 20080321 [4294014.587546] Using local APIC timer interrupts. [4294014.589558] APIC timer calibration result 12528424 [4294014.589558] Detected 12.528 MHz APIC timer. [4294014.589558] net_namespace: 456 bytes [4294014.589558] NET: Registered protocol family 16 [4294014.590073] No dock devices found. [4294014.590309] node 0 link 0: io port [1000, fffff] [4294014.590338] TOM: 0000000040000000 aka 1024M [4294014.590365] node 0 link 0: mmio [a0000, bffff] [4294014.590401] node 0 link 0: mmio [40000000, ff70ffff] [4294014.590438] bus: [00,ff] on node 0 link 0 [4294014.590464] bus: 00 index 0 io port: [0, ffff] [4294014.590491] bus: 00 index 1 mmio: [a0000, bffff] [4294014.590517] bus: 00 index 2 mmio: [40000000, fcffffffff] [4294014.590558] ACPI: bus type pci registered [4294014.590603] PCI: Using configuration type 1 for base access [4294014.595977] ACPI: EC: Look up EC in DSDT [4294014.607934] ACPI: Interpreter enabled [4294014.607966] ACPI: (supports S0 S3 S5) [4294014.608061] ACPI: Using IOAPIC for interrupt routing [4294014.619360] ACPI: PCI Root Bridge [PCI0] (0000:00) [4294014.620741] pci 0000:00:11.0: Force enabled HPET at 0xfed00000 [4294014.621197] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [4294014.705272] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 10 11 12) *5 [4294014.705659] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 6 7 10 *11 12) [4294014.706025] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 *11 12) [4294014.706355] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 11 12) *0, disabled. [4294014.706716] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12) *0, disabled. [4294014.707099] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 10 11 12) *0, disabled. [4294014.707470] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 6 7 *10 11 12) [4294014.707819] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 6 7 *10 11 12) [4294014.708197] ACPI: PCI Interrupt Link [ALKA] (IRQs *20) [4294014.708506] ACPI: PCI Interrupt Link [ALKB] (IRQs *21) [4294014.708825] ACPI: PCI Interrupt Link [ALKC] (IRQs *22) [4294014.709186] ACPI: PCI Interrupt Link [ALKD] (IRQs *23), disabled. [4294014.709585] Linux Plug and Play Support v0.97 (c) Adam Belay [4294014.709683] pnp: PnP ACPI init [4294014.709733] ACPI: bus type pnp registered [4294014.715829] pnp: PnP ACPI: found 10 devices [4294014.715864] ACPI: ACPI bus type pnp unregistered [4294014.716251] SCSI subsystem initialized [4294014.716342] libata version 3.00 loaded. [4294014.716606] usbcore: registered new interface driver usbfs [4294014.716706] usbcore: registered new interface driver hub [4294014.716845] usbcore: registered new device driver usb [4294014.717558] PCI: Using ACPI for IRQ routing [4294014.717597] PCI: Cannot allocate resource region 0 of device 0000:00:00.0 [4294014.727717] agpgart: Detected AGP bridge 0 [4294014.727750] agpgart: Aperture conflicts with PCI mapping. [4294014.727785] agpgart: Aperture from AGP @ e0000000 size 128 MB [4294014.727816] agpgart: Aperture conflicts with PCI mapping. [4294014.727846] agpgart: No usable aperture found. [4294014.727874] agpgart: Consider rebooting with iommu=memaper=2 to get a good aperture. [4294014.728175] hpet clockevent registered [4294014.728205] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0 [4294014.728270] hpet0: 3 32-bit timers, 14318180 Hz [4294014.729438] ACPI: RTC can wake from S4 [4294014.739570] system 00:00: iomem range 0xcc000-0xcffff has been reserved [4294014.739602] system 00:00: iomem range 0xf0000-0xf7fff could not be reserved [4294014.739633] system 00:00: iomem range 0xf8000-0xfbfff could not be reserved [4294014.739664] system 00:00: iomem range 0xfc000-0xfffff could not be reserved [4294014.739695] system 00:00: iomem range 0x3ff00000-0x3fffffff has been reserved [4294014.739736] system 00:00: iomem range 0x3fef0000-0x3fefffff could not be reserved [4294014.739778] system 00:00: iomem range 0xffff0000-0xffffffff could not be reserved [4294014.739819] system 00:00: iomem range 0x0-0x9ffff could not be reserved [4294014.739850] system 00:00: iomem range 0x100000-0x3feeffff could not be reserved [4294014.739891] system 00:00: iomem range 0xfec00000-0xfec00fff could not be reserved [4294014.739933] system 00:00: iomem range 0xfee00000-0xfee00fff could not be reserved [4294014.739975] system 00:00: iomem range 0xfff80000-0xfffeffff could not be reserved [4294014.740027] system 00:02: ioport range 0x4000-0x407f has been reserved [4294014.740058] system 00:02: ioport range 0x5000-0x500f has been reserved [4294014.740098] system 00:03: ioport range 0xb78-0xb7b has been reserved [4294014.740128] system 00:03: ioport range 0xf78-0xf7b has been reserved [4294014.740158] system 00:03: ioport range 0xa78-0xa7b has been reserved [4294014.740188] system 00:03: ioport range 0xe78-0xe7b has been reserved [4294014.740218] system 00:03: ioport range 0xbbc-0xbbf has been reserved [4294014.740248] system 00:03: ioport range 0xfbc-0xfbf has been reserved [4294014.740278] system 00:03: ioport range 0x4d0-0x4d1 has been reserved [4294014.740308] system 00:03: ioport range 0x290-0x297 has been reserved [4294014.741461] PCI: Bridge: 0000:00:01.0 [4294014.741489] IO window: c000-cfff [4294014.741518] MEM window: 0xf8000000-0xf80fffff [4294014.741554] PREFETCH window: 0x00000000e8000000-0x00000000f7ffffff [4294014.741602] PCI: Setting latency timer of device 0000:00:01.0 to 64 [4294014.741648] NET: Registered protocol family 2 [4294014.775651] IP route cache hash table entries: 32768 (order: 6, 262144 bytes) [4294014.776315] TCP established hash table entries: 131072 (order: 9, 2097152 bytes) [4294014.777732] TCP bind hash table entries: 65536 (order: 9, 3670016 bytes) [4294014.783659] TCP: Hash tables configured (established 131072 bind 65536) [4294014.783721] TCP reno registered [4294014.795637] NET: Registered protocol family 1 [4294014.795940] Simple Boot Flag at 0x37 set to 0x1 [4294014.804867] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [4294014.804923] io scheduler noop registered [4294014.805073] io scheduler cfq registered (default) [4294014.805122] PCI: VIA PCI bridge detected.Disabling DAC. [4294014.805265] pci 0000:01:00.0: Boot video device [4294014.805580] input: Power Button (FF) as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 [4294014.805650] ACPI: Power Button (FF) [PWRF] [4294014.805840] input: Power Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1 [4294014.805884] ACPI: Power Button (CM) [PWRB] [4294014.806522] ACPI: ACPI0007:00 is registered as cooling_device0 [4294014.835953] Linux agpgart interface v0.103 [4294014.836063] [drm] Initialized drm 1.1.0 20060810 [4294014.837008] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 [4294014.837225] [drm] Initialized radeon 1.28.0 20060524 on minor 0 [4294014.838309] Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds). [4294014.838351] Hangcheck: Using get_cycles(). [4294014.838566] via-rhine: Broken BIOS detected, avoid_D3 enabled. [4294014.838747] VIA Networking Velocity Family Gigabit Ethernet Adapter Driver Ver. 1.14 [4294014.838789] Copyright (c) 2002, 2003 VIA Networking Technologies, Inc. [4294014.838818] Copyright (c) 2004 Red Hat Inc. [4294014.838858] ACPI: PCI Interrupt 0000:00:0e.0[A] -> GSI 22 (level, low) -> IRQ 22 [4294014.840052] eth0: VIA Networking Velocity Family Gigabit Ethernet Adapter [4294014.840084] eth0: Ethernet Address: 00:50:8D:D1:28:BB [4294014.850648] PPP generic driver version 2.4.2 [4294014.850942] PPP MPPE Compression module registered [4294014.851367] Driver 'sd' needs updating - please use bus_type methods [4294014.851464] Driver 'sr' needs updating - please use bus_type methods [4294014.851782] sata_via 0000:00:0f.0: version 2.3 [4294014.852160] ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20 [4294014.852198] ACPI: PCI Interrupt 0000:00:0f.0[B] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 20 [4294014.852334] sata_via 0000:00:0f.0: routed to hard irq line 11 [4294014.852463] scsi0 : sata_via [4294014.852829] scsi1 : sata_via [4294014.853039] ata1: SATA max UDMA/133 cmd 0xe900 ctl 0xea00 bmdma 0xe200 irq 20 [4294014.853080] ata2: SATA max UDMA/133 cmd 0xe000 ctl 0xe100 bmdma 0xe208 irq 20 [4294015.053537] ata1: SATA link down 1.5 Gbps (SStatus 0 SControl 300) [4294015.238139] Switched to high resolution mode on CPU 0 [4294015.275517] ata2: SATA link down 1.5 Gbps (SStatus 0 SControl 300) [4294015.278478] pata_via 0000:00:0f.1: version 0.3.3 [4294015.278525] ACPI: PCI Interrupt 0000:00:0f.1[A] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 20 [4294015.278575] scsi2 : pata_via [4294015.280804] scsi3 : pata_via [4294015.284094] ata3: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xe400 irq 14 [4294015.284125] ata4: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xe408 irq 15 [4294015.437925] ata3.00: ATAPI: COMPAQ DVD-ROM DRD-8120B, 1.10, max UDMA/33 [4294015.437971] ata3.01: ATAPI: HL-DT-ST GCE-8525B, 1.03, max UDMA/33 [4294015.443795] ata3.00: configured for UDMA/33 [4294015.449794] ata3.01: configured for UDMA/33 [4294015.615040] ata4.00: ATA-6: WDC WD800JB-00JJA0, 05.01C05, max UDMA/100 [4294015.615071] ata4.00: 156301488 sectors, multi 16: LBA [4294015.617901] ata4.00: configured for UDMA/100 [4294015.618035] isa bounce pool size: 16 pages [4294015.618589] scsi 2:0:0:0: CD-ROM COMPAQ DVD-ROM DRD8120B 1.10 PQ: 0 ANSI: 5 [4294015.621794] sr0: scsi3-mmc drive: 0x/40x cd/rw xa/form2 cdda tray [4294015.621824] Uniform CD-ROM driver Revision: 3.20 [4294015.622294] sr 2:0:0:0: Attached scsi CD-ROM sr0 [4294015.622599] sr 2:0:0:0: Attached scsi generic sg0 type 5 [4294015.623278] scsi 2:0:1:0: CD-ROM HL-DT-ST CD-RW GCE-8525B 1.03 PQ: 0 ANSI: 5 [4294015.626460] sr1: scsi3-mmc drive: 40x/52x writer cd/rw xa/form2 cdda tray [4294015.626750] sr 2:0:1:0: Attached scsi CD-ROM sr1 [4294015.626962] sr 2:0:1:0: Attached scsi generic sg1 type 5 [4294015.627224] scsi 3:0:0:0: Direct-Access ATA WDC WD800JB-00JJ 05.0 PQ: 0 ANSI: 5 [4294015.627726] sd 3:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB) [4294015.627794] sd 3:0:0:0: [sda] Write Protect is off [4294015.627822] sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4294015.627902] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4294015.628320] sd 3:0:0:0: [sda] 156301488 512-byte hardware sectors (80026 MB) [4294015.628391] sd 3:0:0:0: [sda] Write Protect is off [4294015.628421] sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4294015.628504] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4294015.628553] sda: sda1 sda2 < sda5 sda6 > [4294015.663111] sd 3:0:0:0: [sda] Attached SCSI disk [4294015.663325] sd 3:0:0:0: Attached scsi generic sg2 type 0 [4294015.663741] ACPI: PCI Interrupt 0000:00:07.0[A] -> GSI 23 (level, low) -> IRQ 23 [4294015.722583] firewire_ohci: Added fw-ohci device 0000:00:07.0, OHCI version 1.0 [4294015.722878] ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 21 (level, low) -> IRQ 21 [4294015.722937] ehci_hcd 0000:00:10.4: EHCI Host Controller [4294015.723544] ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 1 [4294015.723662] ehci_hcd 0000:00:10.4: irq 21, io mem 0xf8121000 [4294015.729587] ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 [4294015.730135] usb usb1: configuration #1 chosen from 1 choice [4294015.730303] hub 1-0:1.0: USB hub found [4294015.730366] hub 1-0:1.0: 8 ports detected [4294015.830956] USB Universal Host Controller Interface driver v3.0 [4294015.831061] ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI 21 (level, low) -> IRQ 21 [4294015.831122] uhci_hcd 0000:00:10.0: UHCI Host Controller [4294015.831253] uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2 [4294015.831317] uhci_hcd 0000:00:10.0: irq 21, io base 0x0000e500 [4294015.831664] usb usb2: configuration #1 chosen from 1 choice [4294015.831788] hub 2-0:1.0: USB hub found [4294015.831859] hub 2-0:1.0: 2 ports detected [4294015.932797] ACPI: PCI Interrupt 0000:00:10.1[A] -> GSI 21 (level, low) -> IRQ 21 [4294015.932853] uhci_hcd 0000:00:10.1: UHCI Host Controller [4294015.932979] uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3 [4294015.933040] uhci_hcd 0000:00:10.1: irq 21, io base 0x0000e600 [4294015.933392] usb usb3: configuration #1 chosen from 1 choice [4294015.933513] hub 3-0:1.0: USB hub found [4294015.933550] hub 3-0:1.0: 2 ports detected [4294015.985646] hub 1-0:1.0: unable to enumerate USB device on port 1 [4294016.034756] ACPI: PCI Interrupt 0000:00:10.2[B] -> GSI 21 (level, low) -> IRQ 21 [4294016.034813] uhci_hcd 0000:00:10.2: UHCI Host Controller [4294016.034940] uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4 [4294016.035001] uhci_hcd 0000:00:10.2: irq 21, io base 0x0000e700 [4294016.035336] usb usb4: configuration #1 chosen from 1 choice [4294016.035459] hub 4-0:1.0: USB hub found [4294016.035496] hub 4-0:1.0: 2 ports detected [4294016.135753] ACPI: PCI Interrupt 0000:00:10.3[B] -> GSI 21 (level, low) -> IRQ 21 [4294016.135809] uhci_hcd 0000:00:10.3: UHCI Host Controller [4294016.135935] uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 5 [4294016.135998] uhci_hcd 0000:00:10.3: irq 21, io base 0x0000e800 [4294016.136336] usb usb5: configuration #1 chosen from 1 choice [4294016.136455] hub 5-0:1.0: USB hub found [4294016.136492] hub 5-0:1.0: 2 ports detected [4294016.140603] hub 1-0:1.0: unable to enumerate USB device on port 2 [4294016.222985] firewire_core: created device fw0: GUID 00508d0000d028bb, S400 [4294016.346588] usb 2-1: new low speed USB device using uhci_hcd and address 2 [4294016.474582] usb 2-1: configuration #1 chosen from 1 choice [4294016.715588] usb 2-2: new low speed USB device using uhci_hcd and address 3 [4294016.847573] usb 2-2: configuration #1 chosen from 1 choice [4294016.889752] usbcore: registered new interface driver usblp [4294016.889783] Initializing USB Mass Storage driver... [4294017.097706] usbcore: registered new interface driver usb-storage [4294017.097737] USB Mass Storage support registered. [4294017.098077] PNP: No PS/2 controller found. Probing ports directly. [4294017.100530] serio: i8042 KBD port at 0x60,0x64 irq 1 [4294017.100575] serio: i8042 AUX port at 0x60,0x64 irq 12 [4294017.100964] mice: PS/2 mouse device common for all mice [4294017.122020] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0 [4294017.122081] rtc0: alarms up to one year, y3k [4294017.122177] i2c /dev entries driver [4294017.146603] w83627hf: Found W83627HF chip at 0x290 [4294017.286574] w83627hf w83627hf.656: Enabling temp2, readings might not make sense [4294017.286574] w83627hf w83627hf.656: Enabling temp3, readings might not make sense [4294017.512660] abituguru: testing bank1 sensor 0 [4294017.534773] abituguru: alarm not raised during volt sensor test [4294017.588582] abituguru: found temp sensor [4294017.590583] abituguru: testing bank1 sensor 1 [4294017.612024] abituguru: alarm not raised during volt sensor test [4294017.664582] abituguru: found temp sensor [4294017.666583] abituguru: testing bank1 sensor 3 [4294017.690582] abituguru: found volt sensor [4294017.692583] abituguru: testing bank1 sensor 4 [4294017.716582] abituguru: found volt sensor [4294017.718583] abituguru: testing bank1 sensor 10 [4294017.740486] abituguru: found volt sensor [4294017.742582] abituguru: testing bank1 sensor 8 [4294017.766582] abituguru: found volt sensor [4294017.768583] abituguru: testing bank1 sensor 14 [4294017.792582] abituguru: found volt sensor [4294017.794583] abituguru: testing bank1 sensor 2 [4294017.818582] abituguru: found volt sensor [4294017.820583] abituguru: testing bank1 sensor 9 [4294017.844732] abituguru: found volt sensor [4294017.846653] abituguru: testing bank1 sensor 6 [4294017.868473] abituguru: found volt sensor [4294017.870582] abituguru: testing bank1 sensor 5 [4294017.894582] abituguru: found volt sensor [4294017.896583] abituguru: testing bank1 sensor 11 [4294017.920582] abituguru: found volt sensor [4294017.922654] abituguru: testing bank1 sensor 15 [4294017.944764] abituguru: alarm not raised during volt sensor test [4294017.996451] abituguru: found temp sensor [4294017.998582] abituguru: testing bank1 sensor 13 [4294018.022582] abituguru: found volt sensor [4294018.024708] abituguru: testing bank1 sensor 7 [4294018.046758] abituguru: alarm not raised during volt sensor test [4294018.099582] abituguru: alarm not raised during temp sensor test [4294018.101583] abituguru: testing bank1 sensor 12 [4294018.124582] abituguru: alarm not raised during volt sensor test [4294018.176758] abituguru: alarm not raised during temp sensor test [4294018.177701] abituguru: detecting number of fan sensors [4294018.177729] abituguru: bank2 sensor 5 does not seem to be a fan sensor: the threshold (0) is below the minimum (5) [4294018.177774] abituguru: found: 5 fan sensors [4294018.177807] abituguru: detecting number of PWM outputs [4294018.177835] abituguru: pwm channel 3 does not seem to be a pwm channel: settings[0] = C9 [4294018.177876] abituguru: found: 3 PWM outputs [4294018.177907] abituguru: found Abit uGuru [4294018.178700] WDT driver for the Winbond(TM) W83627HF/THF/HG Super I/O chip initialising. [4294018.178845] w83627hf/thf/hg WDT: initialized. timeout=60 sec (nowayout=0) [4294018.178895] cpuidle: using governor ladder [4294018.178922] cpuidle: using governor menu [4294018.193574] input: Logitech USB Mouse as /devices/pci0000:00/0000:00:10.0/usb2/2-1/2-1:1.0/input/input2 [4294018.217664] input: USB HID v1.10 Mouse [Logitech USB Mouse] on usb-0000:00:10.0-1 [4294018.230585] input: Microsoft Microsoft� Digital Media Pro Keyboard as /devices/pci0000:00/0000:00:10.0/usb2/2-2/2-2:1.0/input/input3 [4294018.254662] input: USB HID v1.11 Keyboard [Microsoft Microsoft� Digital Media Pro Keyboard] on usb-0000:00:10.0-2 [4294018.273573] input: Microsoft Microsoft� Digital Media Pro Keyboard as /devices/pci0000:00/0000:00:10.0/usb2/2-2/2-2:1.1/input/input4 [4294018.305661] input: USB HID v1.11 Device [Microsoft Microsoft� Digital Media Pro Keyboard] on usb-0000:00:10.0-2 [4294018.305794] usbcore: registered new interface driver usbhid [4294018.305825] usbhid: v2.6:USB HID core driver [4294018.305977] Advanced Linux Sound Architecture Driver Version 1.0.16. [4294018.309575] ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 22 [4294018.309575] PCI: Setting latency timer of device 0000:00:11.5 to 64 [4294018.825716] ALSA device list: [4294018.825746] #0: VIA 8237 with ALC658D at 0xd800, irq 22 [4294018.826596] GRE over IPv4 tunneling driver [4294018.827292] TCP cubic registered [4294018.827320] NET: Registered protocol family 17 [4294018.827372] powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3000+ processors (1 cpu cores) (version 2.20.00) [4294018.827525] powernow-k8: 0 : fid 0xa (1800 MHz), vid 0x6 [4294018.827553] powernow-k8: 1 : fid 0x2 (1000 MHz), vid 0x12 [4294018.828513] rtc_cmos 00:05: setting system clock to 2008-06-21 09:56:22 UTC (1214042182) [4294018.847573] kjournald starting. Commit interval 5 seconds [4294018.847573] EXT3-fs: mounted filesystem with ordered data mode. [4294018.847573] VFS: Mounted root (ext3 filesystem) readonly. [4294018.847573] Freeing unused kernel memory: 204k freed [4294018.847573] Write protecting the kernel read-only data: 3696k [4294018.860730] Testing CPA: undo ffffffff804b3000-ffffffff805a5000 [4294018.860790] Testing CPA: again [4294019.010751] Marking TSC unstable due to cpufreq changes [4294019.227590] Clocksource tsc unstable (delta = -98945211 ns) [4294026.855875] Adding 1502036k swap on /dev/sda5. Priority:-1 extents:1 across:1502036k [4294027.202534] EXT3 FS on sda1, internal journal [4294027.967603] kjournald starting. Commit interval 5 seconds [4294027.967603] EXT3 FS on sda6, internal journal [4294027.967603] EXT3-fs: mounted filesystem with ordered data mode. [4294030.341591] warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use) [4294033.364577] Velocity is AUTO mode [4294035.043577] eth0: Link auto-negotiation speed 100M bps full duplex [4294044.796597] CPA self-test: [4294044.809748] 4k 2560 large 1019 gb 0 x 96[ffff8100000a0000-ffff8100000ff000] miss 524288 [4294044.832917] 4k 109056 large 811 gb 0 x 96[ffff8100000a0000-ffff8100000ff000] miss 524288 [4294044.853936] 4k 109056 large 811 gb 0 x 96[ffff8100000a0000-ffff8100000ff000] miss 524288 [4294044.856902] ok. -- Kevin Winchester ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-21 10:00 ` Kevin Winchester @ 2008-06-21 10:18 ` Yinghai Lu 2008-06-21 10:23 ` Kevin Winchester 0 siblings, 1 reply; 21+ messages in thread From: Yinghai Lu @ 2008-06-21 10:18 UTC (permalink / raw) To: Kevin Winchester Cc: Ingo Molnar, Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Rafael J. Wysocki, Pavel Machek On Sat, Jun 21, 2008 at 3:00 AM, Kevin Winchester <kjwinchester@gmail.com> wrote: > Yinghai Lu wrote: >> >> On Fri, Jun 20, 2008 at 5:00 PM, Kevin Winchester >> <kjwinchester@gmail.com> wrote: >>> >>> Ingo Molnar wrote: >>>> >>>> * Kevin Winchester <kjwinchester@gmail.com> wrote: >>>> >>>>>> hm, could you send me the config that triggered this? >>>>> >>>>> I will do so tonight when I am home again. It is a UP AMD64 box with a >>>>> VIA chipset, if that helps. >>>>> >>>>>> btw., you can probably ignore this one safely. Also please tell me at >>>>>> which commit ID you were at when you triggered this warning. >>>>> >>>>> Good to know - I will get the commit ID tonight as well, although >>>>> wouldn't following the same bisection sequence that I did give you the >>>>> same >>>>> bisection point? I guess that would assume that linus/master and >>>>> auto-x86-next haven't changed much since last night, which might not be >>>>> correct. >>>> >>>> yeah, you'd probably not hit that warning with the x86/gart bisection >>>> sequence. (Assuming the bug is introduced in that branch - so you should >>>> first check whether pure x86/gart kernel triggers the problem too.) >>>> >>>> If you still have the commit ID around then please send it - if you >>>> dont, >>>> no problem, it's no big issue. I wanted to check how wide the bisection >>>> window is where the warning triggers. >>>> >>> I'm sorry - I accidentally checkout out x86/gart to test it before >>> grabbing >>> the commit ID. >>> >>> I went ahead with the bisection and found: >>> >>> >>> >>> 8c9fd91a0dc503f085169d44f4360be025f75224 is first bad commit >>> commit 8c9fd91a0dc503f085169d44f4360be025f75224 >>> Author: Yinghai Lu <yhlu.kernel@gmail.com> >>> Date: Sun Apr 13 18:42:31 2008 -0700 >>> >>> x86: checking aperture size order >>> >>> some systems are using 32M for gart and agp when memory is less than >>> 4G. >>> Kernel will reject and try to allcate another 64M that is not needed, >>> and we will waste 64M of perfectly good RAM. >>> >>> this patch adds a workaround by checking aper_base/order between NB and >>> agp bridge. If they are the same, and memory size is less than 4G, it >>> will allow it. >>> >>> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com> >>> Signed-off-by: Ingo Molnar <mingo@elte.hu> >>> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> >>> >>> :040000 040000 848d6e4045a14d01fc0a794d4350d8a84f3ceff6 >>> 4a10a52b41309060cd5dc1bf0c322f6d43b2477b M arch >>> :040000 040000 aa1cee87b1f5b1b30ed03ce6164ad7f404fef2a3 >>> f9ce0aaa1f7d4fdc7bdc5a43285495db53a6f531 M drivers >>> >>> >>> as the first bad commit. I do not have time to look at the patch right >>> now, >>> but in case anyone else does, I figured I would post it. >>> >> >> please send out whole boot logs with "debug" in command line. >> > > "debug" in the command line doesn't seem to have any effect on the printout > (is there some config option I need to use with it?), but here it is anyway: are you using tip/master? http://people.redhat.com/mingo/sched-devel.git/README YH ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-21 10:18 ` Yinghai Lu @ 2008-06-21 10:23 ` Kevin Winchester 2008-06-21 10:30 ` Yinghai Lu 0 siblings, 1 reply; 21+ messages in thread From: Kevin Winchester @ 2008-06-21 10:23 UTC (permalink / raw) To: Yinghai Lu Cc: Ingo Molnar, Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Rafael J. Wysocki, Pavel Machek On Sat, Jun 21, 2008 at 7:18 AM, Yinghai Lu <yhlu.kernel@gmail.com> wrote: > On Sat, Jun 21, 2008 at 3:00 AM, Kevin Winchester > <kjwinchester@gmail.com> wrote: >> Yinghai Lu wrote: >>> >>> On Fri, Jun 20, 2008 at 5:00 PM, Kevin Winchester >>> <kjwinchester@gmail.com> wrote: >>>> >>>> Ingo Molnar wrote: >>>>> >>>>> * Kevin Winchester <kjwinchester@gmail.com> wrote: >>>>> >>>>>>> hm, could you send me the config that triggered this? >>>>>> >>>>>> I will do so tonight when I am home again. It is a UP AMD64 box with a >>>>>> VIA chipset, if that helps. >>>>>> >>>>>>> btw., you can probably ignore this one safely. Also please tell me at >>>>>>> which commit ID you were at when you triggered this warning. >>>>>> >>>>>> Good to know - I will get the commit ID tonight as well, although >>>>>> wouldn't following the same bisection sequence that I did give you the >>>>>> same >>>>>> bisection point? I guess that would assume that linus/master and >>>>>> auto-x86-next haven't changed much since last night, which might not be >>>>>> correct. >>>>> >>>>> yeah, you'd probably not hit that warning with the x86/gart bisection >>>>> sequence. (Assuming the bug is introduced in that branch - so you should >>>>> first check whether pure x86/gart kernel triggers the problem too.) >>>>> >>>>> If you still have the commit ID around then please send it - if you >>>>> dont, >>>>> no problem, it's no big issue. I wanted to check how wide the bisection >>>>> window is where the warning triggers. >>>>> >>>> I'm sorry - I accidentally checkout out x86/gart to test it before >>>> grabbing >>>> the commit ID. >>>> >>>> I went ahead with the bisection and found: >>>> >>>> >>>> >>>> 8c9fd91a0dc503f085169d44f4360be025f75224 is first bad commit >>>> commit 8c9fd91a0dc503f085169d44f4360be025f75224 >>>> Author: Yinghai Lu <yhlu.kernel@gmail.com> >>>> Date: Sun Apr 13 18:42:31 2008 -0700 >>>> >>>> x86: checking aperture size order >>>> >>>> some systems are using 32M for gart and agp when memory is less than >>>> 4G. >>>> Kernel will reject and try to allcate another 64M that is not needed, >>>> and we will waste 64M of perfectly good RAM. >>>> >>>> this patch adds a workaround by checking aper_base/order between NB and >>>> agp bridge. If they are the same, and memory size is less than 4G, it >>>> will allow it. >>>> >>>> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com> >>>> Signed-off-by: Ingo Molnar <mingo@elte.hu> >>>> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> >>>> >>>> :040000 040000 848d6e4045a14d01fc0a794d4350d8a84f3ceff6 >>>> 4a10a52b41309060cd5dc1bf0c322f6d43b2477b M arch >>>> :040000 040000 aa1cee87b1f5b1b30ed03ce6164ad7f404fef2a3 >>>> f9ce0aaa1f7d4fdc7bdc5a43285495db53a6f531 M drivers >>>> >>>> >>>> as the first bad commit. I do not have time to look at the patch right >>>> now, >>>> but in case anyone else does, I figured I would post it. >>>> >>> >>> please send out whole boot logs with "debug" in command line. >>> >> >> "debug" in the command line doesn't seem to have any effect on the printout >> (is there some config option I need to use with it?), but here it is anyway: > > are you using tip/master? > > http://people.redhat.com/mingo/sched-devel.git/README > That log is from tip/x86/gart, which is where the problem patch was bisected. Would you get better debugging info from tip/master (which includes tip/x86/gart, I believe, and thus would show the problem as well)? -- Kevin Winchester ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-21 10:23 ` Kevin Winchester @ 2008-06-21 10:30 ` Yinghai Lu 2008-06-21 10:39 ` Kevin Winchester 0 siblings, 1 reply; 21+ messages in thread From: Yinghai Lu @ 2008-06-21 10:30 UTC (permalink / raw) To: Kevin Winchester Cc: Ingo Molnar, Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Rafael J. Wysocki, Pavel Machek On Sat, Jun 21, 2008 at 3:23 AM, Kevin Winchester <kjwinchester@gmail.com> wrote: > On Sat, Jun 21, 2008 at 7:18 AM, Yinghai Lu <yhlu.kernel@gmail.com> wrote: >> On Sat, Jun 21, 2008 at 3:00 AM, Kevin Winchester >> <kjwinchester@gmail.com> wrote: >>> Yinghai Lu wrote: >>>> >>>> On Fri, Jun 20, 2008 at 5:00 PM, Kevin Winchester >>>> <kjwinchester@gmail.com> wrote: >>>>> >>>>> Ingo Molnar wrote: >>>>>> >>>>>> * Kevin Winchester <kjwinchester@gmail.com> wrote: >>>>>> >>>>>>>> hm, could you send me the config that triggered this? >>>>>>> >>>>>>> I will do so tonight when I am home again. It is a UP AMD64 box with a >>>>>>> VIA chipset, if that helps. >>>>>>> >>>>>>>> btw., you can probably ignore this one safely. Also please tell me at >>>>>>>> which commit ID you were at when you triggered this warning. >>>>>>> >>>>>>> Good to know - I will get the commit ID tonight as well, although >>>>>>> wouldn't following the same bisection sequence that I did give you the >>>>>>> same >>>>>>> bisection point? I guess that would assume that linus/master and >>>>>>> auto-x86-next haven't changed much since last night, which might not be >>>>>>> correct. >>>>>> >>>>>> yeah, you'd probably not hit that warning with the x86/gart bisection >>>>>> sequence. (Assuming the bug is introduced in that branch - so you should >>>>>> first check whether pure x86/gart kernel triggers the problem too.) >>>>>> >>>>>> If you still have the commit ID around then please send it - if you >>>>>> dont, >>>>>> no problem, it's no big issue. I wanted to check how wide the bisection >>>>>> window is where the warning triggers. >>>>>> >>>>> I'm sorry - I accidentally checkout out x86/gart to test it before >>>>> grabbing >>>>> the commit ID. >>>>> >>>>> I went ahead with the bisection and found: >>>>> >>>>> >>>>> >>>>> 8c9fd91a0dc503f085169d44f4360be025f75224 is first bad commit >>>>> commit 8c9fd91a0dc503f085169d44f4360be025f75224 >>>>> Author: Yinghai Lu <yhlu.kernel@gmail.com> >>>>> Date: Sun Apr 13 18:42:31 2008 -0700 >>>>> >>>>> x86: checking aperture size order >>>>> >>>>> some systems are using 32M for gart and agp when memory is less than >>>>> 4G. >>>>> Kernel will reject and try to allcate another 64M that is not needed, >>>>> and we will waste 64M of perfectly good RAM. >>>>> >>>>> this patch adds a workaround by checking aper_base/order between NB and >>>>> agp bridge. If they are the same, and memory size is less than 4G, it >>>>> will allow it. >>>>> >>>>> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com> >>>>> Signed-off-by: Ingo Molnar <mingo@elte.hu> >>>>> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> >>>>> >>>>> :040000 040000 848d6e4045a14d01fc0a794d4350d8a84f3ceff6 >>>>> 4a10a52b41309060cd5dc1bf0c322f6d43b2477b M arch >>>>> :040000 040000 aa1cee87b1f5b1b30ed03ce6164ad7f404fef2a3 >>>>> f9ce0aaa1f7d4fdc7bdc5a43285495db53a6f531 M drivers >>>>> >>>>> >>>>> as the first bad commit. I do not have time to look at the patch right >>>>> now, >>>>> but in case anyone else does, I figured I would post it. >>>>> >>>> >>>> please send out whole boot logs with "debug" in command line. >>>> >>> >>> "debug" in the command line doesn't seem to have any effect on the printout >>> (is there some config option I need to use with it?), but here it is anyway: >> >> are you using tip/master? >> >> http://people.redhat.com/mingo/sched-devel.git/README >> > > That log is from tip/x86/gart, which is where the problem patch was > bisected. Would you get better debugging info from tip/master (which > includes tip/x86/gart, I believe, and thus would show the problem as > well)? tip/master doesn't work? YH ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-21 10:30 ` Yinghai Lu @ 2008-06-21 10:39 ` Kevin Winchester 2008-06-21 10:50 ` Yinghai Lu 0 siblings, 1 reply; 21+ messages in thread From: Kevin Winchester @ 2008-06-21 10:39 UTC (permalink / raw) To: Yinghai Lu Cc: Ingo Molnar, Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Rafael J. Wysocki, Pavel Machek Yinghai Lu wrote: > On Sat, Jun 21, 2008 at 3:23 AM, Kevin Winchester > <kjwinchester@gmail.com> wrote: >> On Sat, Jun 21, 2008 at 7:18 AM, Yinghai Lu <yhlu.kernel@gmail.com> wrote: >>> On Sat, Jun 21, 2008 at 3:00 AM, Kevin Winchester >>> <kjwinchester@gmail.com> wrote: >>>> Yinghai Lu wrote: >>>>> On Fri, Jun 20, 2008 at 5:00 PM, Kevin Winchester >>>>> <kjwinchester@gmail.com> wrote: >>>>>> Ingo Molnar wrote: >>>>>>> * Kevin Winchester <kjwinchester@gmail.com> wrote: >>>>>>> >>>>>>>>> hm, could you send me the config that triggered this? >>>>>>>> I will do so tonight when I am home again. It is a UP AMD64 box with a >>>>>>>> VIA chipset, if that helps. >>>>>>>> >>>>>>>>> btw., you can probably ignore this one safely. Also please tell me at >>>>>>>>> which commit ID you were at when you triggered this warning. >>>>>>>> Good to know - I will get the commit ID tonight as well, although >>>>>>>> wouldn't following the same bisection sequence that I did give you the >>>>>>>> same >>>>>>>> bisection point? I guess that would assume that linus/master and >>>>>>>> auto-x86-next haven't changed much since last night, which might not be >>>>>>>> correct. >>>>>>> yeah, you'd probably not hit that warning with the x86/gart bisection >>>>>>> sequence. (Assuming the bug is introduced in that branch - so you should >>>>>>> first check whether pure x86/gart kernel triggers the problem too.) >>>>>>> >>>>>>> If you still have the commit ID around then please send it - if you >>>>>>> dont, >>>>>>> no problem, it's no big issue. I wanted to check how wide the bisection >>>>>>> window is where the warning triggers. >>>>>>> >>>>>> I'm sorry - I accidentally checkout out x86/gart to test it before >>>>>> grabbing >>>>>> the commit ID. >>>>>> >>>>>> I went ahead with the bisection and found: >>>>>> >>>>>> >>>>>> >>>>>> 8c9fd91a0dc503f085169d44f4360be025f75224 is first bad commit >>>>>> commit 8c9fd91a0dc503f085169d44f4360be025f75224 >>>>>> Author: Yinghai Lu <yhlu.kernel@gmail.com> >>>>>> Date: Sun Apr 13 18:42:31 2008 -0700 >>>>>> >>>>>> x86: checking aperture size order >>>>>> >>>>>> some systems are using 32M for gart and agp when memory is less than >>>>>> 4G. >>>>>> Kernel will reject and try to allcate another 64M that is not needed, >>>>>> and we will waste 64M of perfectly good RAM. >>>>>> >>>>>> this patch adds a workaround by checking aper_base/order between NB and >>>>>> agp bridge. If they are the same, and memory size is less than 4G, it >>>>>> will allow it. >>>>>> >>>>>> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com> >>>>>> Signed-off-by: Ingo Molnar <mingo@elte.hu> >>>>>> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> >>>>>> >>>>>> :040000 040000 848d6e4045a14d01fc0a794d4350d8a84f3ceff6 >>>>>> 4a10a52b41309060cd5dc1bf0c322f6d43b2477b M arch >>>>>> :040000 040000 aa1cee87b1f5b1b30ed03ce6164ad7f404fef2a3 >>>>>> f9ce0aaa1f7d4fdc7bdc5a43285495db53a6f531 M drivers >>>>>> >>>>>> >>>>>> as the first bad commit. I do not have time to look at the patch right >>>>>> now, >>>>>> but in case anyone else does, I figured I would post it. >>>>>> >>>>> please send out whole boot logs with "debug" in command line. >>>>> >>>> "debug" in the command line doesn't seem to have any effect on the printout >>>> (is there some config option I need to use with it?), but here it is anyway: >>> are you using tip/master? >>> >>> http://people.redhat.com/mingo/sched-devel.git/README >>> >> That log is from tip/x86/gart, which is where the problem patch was >> bisected. Would you get better debugging info from tip/master (which >> includes tip/x86/gart, I believe, and thus would show the problem as >> well)? > > tip/master doesn't work? > I will check tip/master now, but I believe it doesn't work. I will also correct myself, the log I sent you was from: 8c9fd91... x86: checking aperture size order -- Kevin Winchester ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-21 10:39 ` Kevin Winchester @ 2008-06-21 10:50 ` Yinghai Lu 2008-06-21 11:49 ` Kevin Winchester 0 siblings, 1 reply; 21+ messages in thread From: Yinghai Lu @ 2008-06-21 10:50 UTC (permalink / raw) To: Kevin Winchester Cc: Ingo Molnar, Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Rafael J. Wysocki, Pavel Machek [-- Attachment #1: Type: text/plain, Size: 4275 bytes --] On Sat, Jun 21, 2008 at 3:39 AM, Kevin Winchester <kjwinchester@gmail.com> wrote: > Yinghai Lu wrote: >> >> On Sat, Jun 21, 2008 at 3:23 AM, Kevin Winchester >> <kjwinchester@gmail.com> wrote: >>> >>> On Sat, Jun 21, 2008 at 7:18 AM, Yinghai Lu <yhlu.kernel@gmail.com> >>> wrote: >>>> >>>> On Sat, Jun 21, 2008 at 3:00 AM, Kevin Winchester >>>> <kjwinchester@gmail.com> wrote: >>>>> >>>>> Yinghai Lu wrote: >>>>>> >>>>>> On Fri, Jun 20, 2008 at 5:00 PM, Kevin Winchester >>>>>> <kjwinchester@gmail.com> wrote: >>>>>>> >>>>>>> Ingo Molnar wrote: >>>>>>>> >>>>>>>> * Kevin Winchester <kjwinchester@gmail.com> wrote: >>>>>>>> >>>>>>>>>> hm, could you send me the config that triggered this? >>>>>>>>> >>>>>>>>> I will do so tonight when I am home again. It is a UP AMD64 box >>>>>>>>> with a >>>>>>>>> VIA chipset, if that helps. >>>>>>>>> >>>>>>>>>> btw., you can probably ignore this one safely. Also please tell me >>>>>>>>>> at >>>>>>>>>> which commit ID you were at when you triggered this warning. >>>>>>>>> >>>>>>>>> Good to know - I will get the commit ID tonight as well, although >>>>>>>>> wouldn't following the same bisection sequence that I did give you >>>>>>>>> the >>>>>>>>> same >>>>>>>>> bisection point? I guess that would assume that linus/master and >>>>>>>>> auto-x86-next haven't changed much since last night, which might >>>>>>>>> not be >>>>>>>>> correct. >>>>>>>> >>>>>>>> yeah, you'd probably not hit that warning with the x86/gart >>>>>>>> bisection >>>>>>>> sequence. (Assuming the bug is introduced in that branch - so you >>>>>>>> should >>>>>>>> first check whether pure x86/gart kernel triggers the problem too.) >>>>>>>> >>>>>>>> If you still have the commit ID around then please send it - if you >>>>>>>> dont, >>>>>>>> no problem, it's no big issue. I wanted to check how wide the >>>>>>>> bisection >>>>>>>> window is where the warning triggers. >>>>>>>> >>>>>>> I'm sorry - I accidentally checkout out x86/gart to test it before >>>>>>> grabbing >>>>>>> the commit ID. >>>>>>> >>>>>>> I went ahead with the bisection and found: >>>>>>> >>>>>>> >>>>>>> >>>>>>> 8c9fd91a0dc503f085169d44f4360be025f75224 is first bad commit >>>>>>> commit 8c9fd91a0dc503f085169d44f4360be025f75224 >>>>>>> Author: Yinghai Lu <yhlu.kernel@gmail.com> >>>>>>> Date: Sun Apr 13 18:42:31 2008 -0700 >>>>>>> >>>>>>> x86: checking aperture size order >>>>>>> >>>>>>> some systems are using 32M for gart and agp when memory is less than >>>>>>> 4G. >>>>>>> Kernel will reject and try to allcate another 64M that is not >>>>>>> needed, >>>>>>> and we will waste 64M of perfectly good RAM. >>>>>>> >>>>>>> this patch adds a workaround by checking aper_base/order between NB >>>>>>> and >>>>>>> agp bridge. If they are the same, and memory size is less than 4G, >>>>>>> it >>>>>>> will allow it. >>>>>>> >>>>>>> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com> >>>>>>> Signed-off-by: Ingo Molnar <mingo@elte.hu> >>>>>>> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> >>>>>>> >>>>>>> :040000 040000 848d6e4045a14d01fc0a794d4350d8a84f3ceff6 >>>>>>> 4a10a52b41309060cd5dc1bf0c322f6d43b2477b M arch >>>>>>> :040000 040000 aa1cee87b1f5b1b30ed03ce6164ad7f404fef2a3 >>>>>>> f9ce0aaa1f7d4fdc7bdc5a43285495db53a6f531 M drivers >>>>>>> >>>>>>> >>>>>>> as the first bad commit. I do not have time to look at the patch >>>>>>> right >>>>>>> now, >>>>>>> but in case anyone else does, I figured I would post it. >>>>>>> >>>>>> please send out whole boot logs with "debug" in command line. >>>>>> >>>>> "debug" in the command line doesn't seem to have any effect on the >>>>> printout >>>>> (is there some config option I need to use with it?), but here it is >>>>> anyway: >>>> >>>> are you using tip/master? >>>> >>>> http://people.redhat.com/mingo/sched-devel.git/README >>>> >>> That log is from tip/x86/gart, which is where the problem patch was >>> bisected. Would you get better debugging info from tip/master (which >>> includes tip/x86/gart, I believe, and thus would show the problem as >>> well)? >> >> tip/master doesn't work? >> > > I will check tip/master now, but I believe it doesn't work. > > I will also correct myself, the log I sent you was from: > > 8c9fd91... x86: checking aperture size order > please try attached patch... YH [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #2: gart_any_mapped.patch --] [-- Type: text/x-patch; name=gart_any_mapped.patch, Size: 793 bytes --] [PATCH] x86: change back to any_mapped agp check is using request_mem_region. and could fail if e820 reserved... Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com> diff --git a/arch/x86/kernel/aperture_64.c b/arch/x86/kernel/aperture_64.c index e6deed1..600470d 100644 --- a/arch/x86/kernel/aperture_64.c +++ b/arch/x86/kernel/aperture_64.c @@ -324,8 +324,8 @@ void __init early_gart_iommu_check(void) fix = 1; if (gart_fix_e820 && !fix && aper_enabled) { - if (!e820_all_mapped(aper_base, aper_base + aper_size, - E820_RESERVED)) { + if (e820_any_mapped(aper_base, aper_base + aper_size, + E820_RAM)) { /* reserve it, so we can reuse it in second kernel */ printk(KERN_INFO "update e820 for GART\n"); e820_add_region(aper_base, aper_size, E820_RESERVED); ^ permalink raw reply related [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-21 10:50 ` Yinghai Lu @ 2008-06-21 11:49 ` Kevin Winchester 2008-06-23 11:12 ` Ingo Molnar 0 siblings, 1 reply; 21+ messages in thread From: Kevin Winchester @ 2008-06-21 11:49 UTC (permalink / raw) To: Yinghai Lu Cc: Ingo Molnar, Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Rafael J. Wysocki, Pavel Machek Yinghai Lu wrote: > On Sat, Jun 21, 2008 at 3:39 AM, Kevin Winchester > <kjwinchester@gmail.com> wrote: >> Yinghai Lu wrote: >>> On Sat, Jun 21, 2008 at 3:23 AM, Kevin Winchester >>> <kjwinchester@gmail.com> wrote: >>>> On Sat, Jun 21, 2008 at 7:18 AM, Yinghai Lu <yhlu.kernel@gmail.com> >>>> wrote: >>>>> On Sat, Jun 21, 2008 at 3:00 AM, Kevin Winchester >>>>> <kjwinchester@gmail.com> wrote: >>>>>> Yinghai Lu wrote: >>>>>>> On Fri, Jun 20, 2008 at 5:00 PM, Kevin Winchester >>>>>>> <kjwinchester@gmail.com> wrote: >>>>>>>> Ingo Molnar wrote: >>>>>>>>> * Kevin Winchester <kjwinchester@gmail.com> wrote: >>>>>>>>> >>>>>>>>>>> hm, could you send me the config that triggered this? >>>>>>>>>> I will do so tonight when I am home again. It is a UP AMD64 box >>>>>>>>>> with a >>>>>>>>>> VIA chipset, if that helps. >>>>>>>>>> >>>>>>>>>>> btw., you can probably ignore this one safely. Also please tell me >>>>>>>>>>> at >>>>>>>>>>> which commit ID you were at when you triggered this warning. >>>>>>>>>> Good to know - I will get the commit ID tonight as well, although >>>>>>>>>> wouldn't following the same bisection sequence that I did give you >>>>>>>>>> the >>>>>>>>>> same >>>>>>>>>> bisection point? I guess that would assume that linus/master and >>>>>>>>>> auto-x86-next haven't changed much since last night, which might >>>>>>>>>> not be >>>>>>>>>> correct. >>>>>>>>> yeah, you'd probably not hit that warning with the x86/gart >>>>>>>>> bisection >>>>>>>>> sequence. (Assuming the bug is introduced in that branch - so you >>>>>>>>> should >>>>>>>>> first check whether pure x86/gart kernel triggers the problem too.) >>>>>>>>> >>>>>>>>> If you still have the commit ID around then please send it - if you >>>>>>>>> dont, >>>>>>>>> no problem, it's no big issue. I wanted to check how wide the >>>>>>>>> bisection >>>>>>>>> window is where the warning triggers. >>>>>>>>> >>>>>>>> I'm sorry - I accidentally checkout out x86/gart to test it before >>>>>>>> grabbing >>>>>>>> the commit ID. >>>>>>>> >>>>>>>> I went ahead with the bisection and found: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> 8c9fd91a0dc503f085169d44f4360be025f75224 is first bad commit >>>>>>>> commit 8c9fd91a0dc503f085169d44f4360be025f75224 >>>>>>>> Author: Yinghai Lu <yhlu.kernel@gmail.com> >>>>>>>> Date: Sun Apr 13 18:42:31 2008 -0700 >>>>>>>> >>>>>>>> x86: checking aperture size order >>>>>>>> >>>>>>>> some systems are using 32M for gart and agp when memory is less than >>>>>>>> 4G. >>>>>>>> Kernel will reject and try to allcate another 64M that is not >>>>>>>> needed, >>>>>>>> and we will waste 64M of perfectly good RAM. >>>>>>>> >>>>>>>> this patch adds a workaround by checking aper_base/order between NB >>>>>>>> and >>>>>>>> agp bridge. If they are the same, and memory size is less than 4G, >>>>>>>> it >>>>>>>> will allow it. >>>>>>>> >>>>>>>> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com> >>>>>>>> Signed-off-by: Ingo Molnar <mingo@elte.hu> >>>>>>>> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> >>>>>>>> >>>>>>>> :040000 040000 848d6e4045a14d01fc0a794d4350d8a84f3ceff6 >>>>>>>> 4a10a52b41309060cd5dc1bf0c322f6d43b2477b M arch >>>>>>>> :040000 040000 aa1cee87b1f5b1b30ed03ce6164ad7f404fef2a3 >>>>>>>> f9ce0aaa1f7d4fdc7bdc5a43285495db53a6f531 M drivers >>>>>>>> >>>>>>>> >>>>>>>> as the first bad commit. I do not have time to look at the patch >>>>>>>> right >>>>>>>> now, >>>>>>>> but in case anyone else does, I figured I would post it. >>>>>>>> >>>>>>> please send out whole boot logs with "debug" in command line. >>>>>>> >>>>>> "debug" in the command line doesn't seem to have any effect on the >>>>>> printout >>>>>> (is there some config option I need to use with it?), but here it is >>>>>> anyway: >>>>> are you using tip/master? >>>>> >>>>> http://people.redhat.com/mingo/sched-devel.git/README >>>>> >>>> That log is from tip/x86/gart, which is where the problem patch was >>>> bisected. Would you get better debugging info from tip/master (which >>>> includes tip/x86/gart, I believe, and thus would show the problem as >>>> well)? >>> tip/master doesn't work? >>> >> I will check tip/master now, but I believe it doesn't work. >> >> I will also correct myself, the log I sent you was from: >> >> 8c9fd91... x86: checking aperture size order >> > > please try attached patch... > Thanks for the patch. it fixes the problem for me. tip/master was indeed showing the problem as well, but it does not once your patch is applied. So you can add a: Tested-by: Kevin Winchester <kjwinchester@gmail.com> to the patch if you want. Thanks again, -- Kevin Winchester ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: Bisecting tip/auto-x86-next? 2008-06-21 11:49 ` Kevin Winchester @ 2008-06-23 11:12 ` Ingo Molnar 0 siblings, 0 replies; 21+ messages in thread From: Ingo Molnar @ 2008-06-23 11:12 UTC (permalink / raw) To: Kevin Winchester Cc: Yinghai Lu, Ingo Molnar, Thomas Gleixner, H. Peter Anvin, Linux Kernel Mailing List, Rafael J. Wysocki, Pavel Machek * Kevin Winchester <kjwinchester@gmail.com> wrote: >> please try attached patch... > > Thanks for the patch. it fixes the problem for me. tip/master was > indeed showing the problem as well, but it does not once your patch is > applied. > > So you can add a: > > Tested-by: Kevin Winchester <kjwinchester@gmail.com> > > to the patch if you want. applied to tip/x86/gart - thanks a lot Kevin for bisecting this. I have attached the commit below. Ingo -----------------> commit 0754557d72c1fbfc5fcfd5235e7c23ae6f77248c Author: Yinghai Lu <yhlu.kernel@gmail.com> Date: Sat Jun 21 03:50:47 2008 -0700 x86: change early_gart_iommu_check() back to any_mapped Kevin Winchester reported a GART related direct rendering failure against linux-next-20080611, which shows up via these log entries: PCI: Using ACPI for IRQ routing PCI: Cannot allocate resource region 0 of device 0000:00:00.0 agpgart: Detected AGP bridge 0 agpgart: Aperture conflicts with PCI mapping. agpgart: Aperture from AGP @ e0000000 size 128 MB agpgart: Aperture conflicts with PCI mapping. agpgart: No usable aperture found. agpgart: Consider rebooting with iommu=memaper=2 to get a good aperture. instead of the expected: PCI: Using ACPI for IRQ routing agpgart: Detected AGP bridge 0 agpgart: Aperture from AGP @ e0000000 size 128 MB Kevin bisected it down to this change in tip/x86/gart: "x86: checking aperture size order". agp check is using request_mem_region(), and could fail if e820 is reserved... change it back to e820_any_mapped(). Reported-and-bisected-by: "Kevin Winchester" <kjwinchester@gmail.com> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com> Tested-by: Kevin Winchester <kjwinchester@gmail.com> Signed-off-by: Ingo Molnar <mingo@elte.hu> diff --git a/arch/x86/kernel/aperture_64.c b/arch/x86/kernel/aperture_64.c index 3409abb..e819362 100644 --- a/arch/x86/kernel/aperture_64.c +++ b/arch/x86/kernel/aperture_64.c @@ -324,8 +324,8 @@ void __init early_gart_iommu_check(void) fix = 1; if (gart_fix_e820 && !fix && aper_enabled) { - if (!e820_all_mapped(aper_base, aper_base + aper_size, - E820_RESERVED)) { + if (e820_any_mapped(aper_base, aper_base + aper_size, + E820_RAM)) { /* reserve it, so we can reuse it in second kernel */ printk(KERN_INFO "update e820 for GART\n"); add_memory_region(aper_base, aper_size, E820_RESERVED); ^ permalink raw reply related [flat|nested] 21+ messages in thread
end of thread, other threads:[~2008-06-23 11:13 UTC | newest] Thread overview: 21+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2008-06-20 0:40 Bisecting tip/auto-x86-next? Kevin Winchester 2008-06-20 7:15 ` Sitsofe Wheeler 2008-06-20 10:04 ` Ingo Molnar 2008-06-20 22:23 ` Kevin Winchester 2008-06-20 10:07 ` Ingo Molnar 2008-06-20 10:17 ` Ingo Molnar 2008-06-20 10:49 ` Pavel Machek 2008-06-20 11:40 ` Kevin Winchester 2008-06-20 10:51 ` Rafael J. Wysocki 2008-06-20 11:37 ` Kevin Winchester 2008-06-20 15:36 ` Ingo Molnar 2008-06-21 0:00 ` Kevin Winchester 2008-06-21 0:14 ` Yinghai Lu 2008-06-21 10:00 ` Kevin Winchester 2008-06-21 10:18 ` Yinghai Lu 2008-06-21 10:23 ` Kevin Winchester 2008-06-21 10:30 ` Yinghai Lu 2008-06-21 10:39 ` Kevin Winchester 2008-06-21 10:50 ` Yinghai Lu 2008-06-21 11:49 ` Kevin Winchester 2008-06-23 11:12 ` Ingo Molnar
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox