cpufreq limits avilable frequencies to 800MHz on git kernel

public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed

* cpufreq limits avilable frequencies to 800MHz on git kernel
@ 2008-05-23 17:44 Arkadiusz Miskiewicz
  2008-05-24  1:25 ` Andrew Morton
  0 siblings, 1 reply; 13+ messages in thread
From: Arkadiusz Miskiewicz @ 2008-05-23 17:44 UTC (permalink / raw)
  To: linux-kernel, cpufreq

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


thinkpad z60m, Intel(R) Pentium(R) M processor 2.00GHz. kernel from git from 
1-2 days ago. 

Unfortunately it seems that suspend to ram/resume causes frequency
to be limited to 800MHz only. I can't set it to 2GHz again :-/

scaling_max_freq is then 800000 and cannot be changed.

reboot and the problem disappears until new suspend/resume cycle.

cpufreq stuff is driven by acpi-cpufreq

$ cpufreq-info
cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to linux@brodo.de, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 800 MHz - 2.00 GHz
  available frequency steps: 2.00 GHz, 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
  available cpufreq governors: powersave, userspace, ondemand, performance
  current policy: frequency should be within 800 MHz and 800 MHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz.

/sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:800000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:2000000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:800000
/sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:2000000 
1600000 1333000 1066000 800000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:powersave 
userspace ondemand performance
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:800000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufreq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:performance
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:800000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:800000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:<unsupported>

-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 70346 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.26-rc3
# Fri May 23 19:25:09 2008
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_DEFCONFIG_LIST="arch/x86/configs/i386_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 is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# 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 is not set
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
# CONFIG_HAVE_SETUP_PER_CPU_AREA is not set
# CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
# CONFIG_ZONE_DMA32 is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set
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_KTIME_SCALAR=y

#
# 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 is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_TREE=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_CGROUPS is not set
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_RT_GROUP_SCHED=y
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
CONFIG_RELAY=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_SYSCTL_SYSCALL_CHECK=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_EXTRA_PASS=y
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=y
# CONFIG_MARKERS is not set
CONFIG_OPROFILE=m
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
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=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_BLOCK=y
CONFIG_LBD=y
CONFIG_BLK_DEV_IO_TRACE=y
CONFIG_LSF=y
CONFIG_BLK_DEV_BSG=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_CLASSIC_RCU=y

#
# 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_SCHED_NO_NO_OMIT_FRAME_POINTER=y
# CONFIG_PARAVIRT_GUEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
CONFIG_MPENTIUMM=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CPU=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=4
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
# CONFIG_IOMMU_HELPER is not set
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
# CONFIG_PREEMPT_RCU is not set
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
# CONFIG_X86_MCE_P4THERMAL is not set
CONFIG_VM86=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_X86_REBOOTFIXUPS=y
CONFIG_MICROCODE=m
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
# CONFIG_SPARSEMEM_VMEMMAP_ENABLE is not set
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_X86_PAT=y
# CONFIG_EFI is not set
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_SCHED_HRTICK=y
CONFIG_KEXEC=y
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
# 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=y
CONFIG_PM_STD_PARTITION=""
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_DOCK=m
CONFIG_ACPI_BAY=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_WMI=m
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_CUSTOM_DSDT_FILE=""
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=m
CONFIG_ACPI_SBS=m
CONFIG_X86_APM_BOOT=y
CONFIG_APM=m
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
CONFIG_APM_CPU_IDLE=y
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF 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=m
CONFIG_CPU_FREQ_STAT_DETAILS=y
# 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=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_X86_POWERNOW_K6=m
CONFIG_X86_POWERNOW_K7=m
CONFIG_X86_POWERNOW_K7_ACPI=y
CONFIG_X86_POWERNOW_K8=m
CONFIG_X86_POWERNOW_K8_ACPI=y
CONFIG_X86_GX_SUSPMOD=m
CONFIG_X86_SPEEDSTEP_CENTRINO=m
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y
CONFIG_X86_SPEEDSTEP_ICH=m
CONFIG_X86_SPEEDSTEP_SMI=m
CONFIG_X86_P4_CLOCKMOD=m
CONFIG_X86_CPUFREQ_NFORCE2=m
CONFIG_X86_LONGRUN=m
# CONFIG_X86_LONGHAUL is not set
# CONFIG_X86_E_POWERSAVER is not set

#
# shared options
#
CONFIG_X86_ACPI_CPUFREQ_PROC_INTF=y
CONFIG_X86_SPEEDSTEP_LIB=m
CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK=y
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_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
# CONFIG_PCI_GOOLPC is not set
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
CONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
# CONFIG_PCI_LEGACY is not set
# CONFIG_PCI_DEBUG is not set
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_OLPC is not set
CONFIG_PCCARD=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=m
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y

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

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_MISC=m

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
# CONFIG_XFRM_SUB_POLICY is not set
CONFIG_XFRM_MIGRATE=y
CONFIG_XFRM_STATISTICS=y
CONFIG_NET_KEY=m
CONFIG_NET_KEY_MIGRATE=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_LRO=m
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
CONFIG_IP_VS=m
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12

#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y

#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m

#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
CONFIG_IPV6_OPTIMISTIC_DAD=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_IPV6_MIP6=m
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_INET6_XFRM_MODE_BEET=m
CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m
CONFIG_IPV6_SIT=m
CONFIG_IPV6_NDISC_NODETYPE=y
CONFIG_IPV6_TUNNEL=m
CONFIG_IPV6_MULTIPLE_TABLES=y
CONFIG_IPV6_SUBTREES=y
CONFIG_IPV6_MROUTE=y
CONFIG_IPV6_PIMSM_V2=y
CONFIG_NETLABEL=y
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
# CONFIG_NF_CONNTRACK is not set
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
# CONFIG_NETFILTER_XT_TARGET_NFQUEUE is not set
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_RATEEST=m
# CONFIG_NETFILTER_XT_TARGET_TRACE is not set
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_IPRANGE=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_OWNER=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_RATEEST=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_TIME=m
# CONFIG_NETFILTER_XT_MATCH_U32 is not set
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m

#
# IP: Netfilter Configuration
#
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m

#
# IPv6: Netfilter Configuration
#
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_MH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_RAW=m

#
# DECnet: Netfilter Configuration
#
# CONFIG_DECNET_NF_GRABULATOR is not set

#
# Bridge: Netfilter Configuration
#
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_ULOG=m
CONFIG_BRIDGE_EBT_NFLOG=m
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
CONFIG_IP_DCCP_ACKVEC=y

#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP_CCID2=m
# CONFIG_IP_DCCP_CCID2_DEBUG is not set
CONFIG_IP_DCCP_CCID3=m
# CONFIG_IP_DCCP_CCID3_DEBUG is not set
CONFIG_IP_DCCP_CCID3_RTO=100
CONFIG_IP_DCCP_TFRC_LIB=m

#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y
CONFIG_TIPC=m
CONFIG_TIPC_ADVANCED=y
CONFIG_TIPC_ZONES=3
CONFIG_TIPC_CLUSTERS=1
CONFIG_TIPC_NODES=255
CONFIG_TIPC_SLAVE_NODES=0
CONFIG_TIPC_PORTS=8191
CONFIG_TIPC_LOG=0
# CONFIG_TIPC_DEBUG is not set
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
CONFIG_ATM_CLIP_NO_ICMP=y
CONFIG_ATM_LANE=m
CONFIG_ATM_MPOA=m
CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set
CONFIG_BRIDGE=m
CONFIG_VLAN_8021Q=m
CONFIG_DECNET=m
# CONFIG_DECNET_ROUTER is not set
CONFIG_LLC=m
CONFIG_LLC2=m
CONFIG_IPX=m
# CONFIG_IPX_INTERN is not set
CONFIG_ATALK=m
CONFIG_DEV_APPLETALK=m
CONFIG_IPDDP=m
# CONFIG_IPDDP_ENCAP is not set
# CONFIG_IPDDP_DECAP is not set
CONFIG_X25=m
CONFIG_LAPB=m
CONFIG_ECONET=m
CONFIG_ECONET_AUNUDP=y
# CONFIG_ECONET_NATIVE is not set
CONFIG_WAN_ROUTER=m
CONFIG_NET_SCHED=y

#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_ATM=m
CONFIG_NET_SCH_PRIO=m
# CONFIG_NET_SCH_RR is not set
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_INGRESS=m

#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_CLS_FLOW=m
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
# CONFIG_GACT_PROB is not set
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_IPT=m
CONFIG_NET_ACT_NAT=m
CONFIG_NET_ACT_PEDIT=m
# CONFIG_NET_ACT_SIMP is not set
CONFIG_NET_CLS_IND=y
CONFIG_NET_SCH_FIFO=y

#
# Network testing
#
CONFIG_NET_PKTGEN=m
CONFIG_HAMRADIO=y

#
# Packet Radio protocols
#
CONFIG_AX25=m
# CONFIG_AX25_DAMA_SLAVE is not set
CONFIG_NETROM=m
CONFIG_ROSE=m

#
# AX.25 network device drivers
#
CONFIG_MKISS=m
CONFIG_6PACK=m
CONFIG_BPQETHER=m
CONFIG_BAYCOM_SER_FDX=m
CONFIG_BAYCOM_SER_HDX=m
CONFIG_YAM=m
CONFIG_CAN=m
CONFIG_CAN_RAW=m
CONFIG_CAN_BCM=m

#
# CAN Device Drivers
#
CONFIG_CAN_VCAN=m
# CONFIG_CAN_DEBUG_DEVICES is not set
CONFIG_IRDA=m

#
# IrDA protocols
#
CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
CONFIG_IRDA_ULTRA=y

#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
# CONFIG_IRDA_DEBUG is not set

#
# Infrared-port device drivers
#

#
# SIR device drivers
#
CONFIG_IRTTY_SIR=m

#
# Dongle support
#
CONFIG_DONGLE=y
CONFIG_ESI_DONGLE=m
CONFIG_ACTISYS_DONGLE=m
CONFIG_TEKRAM_DONGLE=m
# CONFIG_TOIM3232_DONGLE is not set
CONFIG_LITELINK_DONGLE=m
CONFIG_MA600_DONGLE=m
CONFIG_GIRBIL_DONGLE=m
CONFIG_MCP2120_DONGLE=m
CONFIG_OLD_BELKIN_DONGLE=m
CONFIG_ACT200L_DONGLE=m
# CONFIG_KINGSUN_DONGLE is not set
# CONFIG_KSDAZZLE_DONGLE is not set
# CONFIG_KS959_DONGLE is not set

#
# FIR device drivers
#
CONFIG_USB_IRDA=m
CONFIG_SIGMATEL_FIR=m
CONFIG_NSC_FIR=m
CONFIG_WINBOND_FIR=m
CONFIG_TOSHIBA_FIR=m
CONFIG_SMC_IRCC_FIR=m
CONFIG_ALI_FIR=m
CONFIG_VLSI_FIR=m
CONFIG_VIA_FIR=m
# CONFIG_MCS_FIR is not set
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=m

#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
CONFIG_BT_HCIUSB_SCO=y
CONFIG_BT_HCIBTSDIO=m
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_LL=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m
CONFIG_AF_RXRPC=m
# CONFIG_AF_RXRPC_DEBUG is not set
# CONFIG_RXKAD is not set
CONFIG_FIB_RULES=y

#
# Wireless
#
CONFIG_CFG80211=m
CONFIG_NL80211=y
CONFIG_WIRELESS_EXT=y
CONFIG_MAC80211=m

#
# Rate control algorithm selection
#
CONFIG_MAC80211_RC_DEFAULT_PID=y
# CONFIG_MAC80211_RC_DEFAULT_NONE is not set

#
# Selecting 'y' for an algorithm will
#

#
# build the algorithm into mac80211.
#
CONFIG_MAC80211_RC_DEFAULT="pid"
CONFIG_MAC80211_RC_PID=y
CONFIG_MAC80211_MESH=y
CONFIG_MAC80211_LEDS=y
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_DEBUG_PACKET_ALIGNMENT is not set
# CONFIG_MAC80211_DEBUG is not set
CONFIG_IEEE80211=m
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=m
CONFIG_IEEE80211_CRYPT_TKIP=m
CONFIG_RFKILL=m
CONFIG_RFKILL_INPUT=m
CONFIG_RFKILL_LEDS=y
# CONFIG_NET_9P is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
# CONFIG_STANDALONE is not set
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=m
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_CONCAT=m
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_REDBOOT_PARTS=m
CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1
CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED=y
CONFIG_MTD_REDBOOT_PARTS_READONLY=y
# CONFIG_MTD_AR7_PARTS is not set

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=m
CONFIG_MTD_BLKDEVS=m
CONFIG_MTD_BLOCK=m
CONFIG_MTD_BLOCK_RO=m
CONFIG_FTL=m
CONFIG_NFTL=m
CONFIG_NFTL_RW=y
CONFIG_INFTL=m
# CONFIG_RFD_FTL is not set
CONFIG_SSFDC=m
CONFIG_MTD_OOPS=m

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=m
CONFIG_MTD_JEDECPROBE=m
CONFIG_MTD_GEN_PROBE=m
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
CONFIG_MTD_CFI_INTELEXT=m
CONFIG_MTD_CFI_AMDSTD=m
CONFIG_MTD_CFI_STAA=m
CONFIG_MTD_CFI_UTIL=m
CONFIG_MTD_RAM=m
CONFIG_MTD_ROM=m
CONFIG_MTD_ABSENT=m

#
# Mapping drivers for chip access
#
CONFIG_MTD_COMPLEX_MAPPINGS=y
CONFIG_MTD_PHYSMAP=m
CONFIG_MTD_PHYSMAP_START=0x8000000
CONFIG_MTD_PHYSMAP_LEN=0x4000000
CONFIG_MTD_PHYSMAP_BANKWIDTH=2
CONFIG_MTD_SC520CDP=m
CONFIG_MTD_NETSC520=m
CONFIG_MTD_TS5500=m
CONFIG_MTD_SBC_GXX=m
CONFIG_MTD_AMD76XROM=m
CONFIG_MTD_ICHXROM=m
CONFIG_MTD_ESB2ROM=m
CONFIG_MTD_CK804XROM=m
CONFIG_MTD_SCB2_FLASH=m
CONFIG_MTD_NETtel=m
CONFIG_MTD_DILNETPC=m
CONFIG_MTD_DILNETPC_BOOTSIZE=0x80000
CONFIG_MTD_L440GX=m
CONFIG_MTD_PCI=m
# CONFIG_MTD_INTEL_VR_NOR is not set
CONFIG_MTD_PLATRAM=m

#
# Self-contained MTD device drivers
#
CONFIG_MTD_PMC551=m
CONFIG_MTD_PMC551_BUGFIX=y
# CONFIG_MTD_PMC551_DEBUG is not set
CONFIG_MTD_SLRAM=m
CONFIG_MTD_PHRAM=m
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
CONFIG_MTD_BLOCK2MTD=m

#
# Disk-On-Chip Device Drivers
#
CONFIG_MTD_DOC2000=m
CONFIG_MTD_DOC2001=m
CONFIG_MTD_DOC2001PLUS=m
CONFIG_MTD_DOCPROBE=m
CONFIG_MTD_DOCECC=m
# CONFIG_MTD_DOCPROBE_ADVANCED is not set
CONFIG_MTD_DOCPROBE_ADDRESS=0
CONFIG_MTD_NAND=m
CONFIG_MTD_NAND_VERIFY_WRITE=y
# CONFIG_MTD_NAND_ECC_SMC is not set
# CONFIG_MTD_NAND_MUSEUM_IDS is not set
CONFIG_MTD_NAND_IDS=m
CONFIG_MTD_NAND_DISKONCHIP=m
# CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set
CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0
CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE=y
CONFIG_MTD_NAND_CAFE=m
# CONFIG_MTD_NAND_CS553X is not set
# CONFIG_MTD_NAND_NANDSIM is not set
# CONFIG_MTD_NAND_PLATFORM is not set
CONFIG_MTD_ALAUDA=m
# CONFIG_MTD_ONENAND is not set

#
# UBI - Unsorted block images
#
# CONFIG_MTD_UBI 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=m
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_XIP is not set
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
CONFIG_CDROM_PKTCDVD_WCACHE=y
CONFIG_ATA_OVER_ETH=m
CONFIG_VIRTIO_BLK=m
CONFIG_MISC_DEVICES=y
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ACER_WMI is not set
# CONFIG_ASUS_LAPTOP is not set
# CONFIG_FUJITSU_LAPTOP is not set
# CONFIG_TC1100_WMI is not set
# CONFIG_MSI_LAPTOP is not set
# CONFIG_SONY_LAPTOP is not set
CONFIG_THINKPAD_ACPI=m
# CONFIG_THINKPAD_ACPI_DEBUG is not set
CONFIG_THINKPAD_ACPI_BAY=y
CONFIG_THINKPAD_ACPI_VIDEO=y
CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y
CONFIG_INTEL_MENLOW=m
# CONFIG_EEEPC_LAPTOP is not set
CONFIG_ENCLOSURE_SERVICES=m
CONFIG_HAVE_IDE=y
CONFIG_IDE=m
CONFIG_BLK_DEV_IDE=m

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

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=m
CONFIG_BLK_DEV_PLATFORM=m
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPNP=m
CONFIG_BLK_DEV_IDEDMA_SFF=y

#
# PCI IDE chipsets support
#
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=m
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_CS5535 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_JMICRON is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=m
# CONFIG_BLK_DEV_IT8213 is not set
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_BLK_DEV_TC86C001 is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_BLK_DEV_HD_ONLY is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=m
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=m
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y

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

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

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_FC_TGT_ATTRS=y
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_SCSI_SAS_LIBSAS=m
# CONFIG_SCSI_SAS_ATA is not set
CONFIG_SCSI_SAS_HOST_SMP=y
CONFIG_SCSI_SAS_LIBSAS_DEBUG=y
CONFIG_SCSI_SRP_ATTRS=m
CONFIG_SCSI_SRP_TGT_ATTRS=y
CONFIG_SCSI_LOWLEVEL=y
CONFIG_ISCSI_TCP=m
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
# CONFIG_SCSI_LOWLEVEL_PCMCIA is not set
CONFIG_ATA=m
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
CONFIG_SATA_AHCI=m
# CONFIG_SATA_SIL24 is not set
CONFIG_ATA_SFF=y
# CONFIG_SATA_SVW is not set
CONFIG_ATA_PIIX=m
# 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 is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
CONFIG_PATA_ACPI=m
# 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_CS5535 is not set
# CONFIG_PATA_CS5536 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
CONFIG_ATA_GENERIC=m
# 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=m
# 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_PCMCIA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
# CONFIG_PATA_SCH is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
# CONFIG_MD_RAID5_RESHAPE is not set
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=m
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m
CONFIG_DM_MULTIPATH_EMC=m
# CONFIG_DM_MULTIPATH_RDAC is not set
# CONFIG_DM_MULTIPATH_HP is not set
# CONFIG_DM_DELAY is not set
# CONFIG_DM_UEVENT is not set
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
CONFIG_IEEE1394=m

#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set

#
# Controllers
#
CONFIG_IEEE1394_PCILYNX=m
CONFIG_IEEE1394_OHCI1394=m

#
# Protocols
#
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
CONFIG_IEEE1394_ETH1394_ROM_ENTRY=y
CONFIG_IEEE1394_ETH1394=m
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_I2O=m
CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y
# CONFIG_I2O_EXT_ADAPTEC is not set
CONFIG_I2O_CONFIG=m
CONFIG_I2O_CONFIG_OLD_IOCTL=y
CONFIG_I2O_BUS=m
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_NETDEVICES_MULTIQUEUE is not set
CONFIG_IFB=m
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_MACVLAN=m
CONFIG_EQUALIZER=m
CONFIG_TUN=m
CONFIG_VETH=m
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
# CONFIG_NET_ETHERNET is not set
CONFIG_MII=m
CONFIG_NETDEV_1000=y
CONFIG_ACENIC=m
# CONFIG_ACENIC_OMIT_TIGON_I 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 is not set
CONFIG_TIGON3=m
CONFIG_BNX2=m
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
CONFIG_NETDEV_10000=y
# CONFIG_CHELSIO_T1 is not set
# CONFIG_CHELSIO_T3 is not set
# CONFIG_IXGBE is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
# CONFIG_MYRI10GE is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_NIU is not set
# CONFIG_MLX4_CORE is not set
# CONFIG_TEHUTI is not set
# CONFIG_BNX2X is not set
# CONFIG_SFC is not set
# CONFIG_TR is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
CONFIG_WLAN_80211=y
# CONFIG_PCMCIA_RAYCS is not set
CONFIG_IPW2100=m
CONFIG_IPW2100_MONITOR=y
# CONFIG_IPW2100_DEBUG is not set
CONFIG_IPW2200=m
CONFIG_IPW2200_MONITOR=y
CONFIG_IPW2200_RADIOTAP=y
CONFIG_IPW2200_PROMISCUOUS=y
CONFIG_IPW2200_QOS=y
# CONFIG_IPW2200_DEBUG is not set
# CONFIG_LIBERTAS is not set
# CONFIG_AIRO is not set
# CONFIG_HERMES is not set
# CONFIG_ATMEL is not set
# CONFIG_AIRO_CS is not set
# CONFIG_PCMCIA_WL3501 is not set
# CONFIG_PRISM54 is not set
# CONFIG_USB_ZD1201 is not set
CONFIG_USB_NET_RNDIS_WLAN=m
# CONFIG_RTL8180 is not set
# CONFIG_RTL8187 is not set
# CONFIG_ADM8211 is not set
# CONFIG_P54_COMMON is not set
CONFIG_ATH5K=m
# CONFIG_ATH5K_DEBUG is not set
CONFIG_IWLWIFI=m
CONFIG_IWLCORE=m
# CONFIG_IWLWIFI_LEDS is not set
CONFIG_IWLWIFI_RFKILL=y
# CONFIG_IWL4965 is not set
# CONFIG_IWL3945 is not set
# CONFIG_HOSTAP is not set
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not set
CONFIG_ZD1211RW=m
# CONFIG_ZD1211RW_DEBUG is not set
# CONFIG_RT2X00 is not set

#
# USB Network Adapters
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
# CONFIG_USB_NET_DM9601 is not set
CONFIG_USB_NET_GL620A=m
CONFIG_USB_NET_NET1080=m
CONFIG_USB_NET_PLUSB=m
# CONFIG_USB_NET_MCS7830 is not set
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
# CONFIG_USB_EPSON2888 is not set
# CONFIG_USB_KC2190 is not set
CONFIG_USB_NET_ZAURUS=m
CONFIG_NET_PCMCIA=y
CONFIG_PCMCIA_3C589=m
CONFIG_PCMCIA_3C574=m
CONFIG_PCMCIA_FMVJ18X=m
CONFIG_PCMCIA_PCNET=m
CONFIG_PCMCIA_NMCLAN=m
CONFIG_PCMCIA_SMC91C92=m
CONFIG_PCMCIA_XIRC2PS=m
CONFIG_PCMCIA_AXNET=m
# CONFIG_WAN is not set
CONFIG_ATM_DRIVERS=y
CONFIG_ATM_DUMMY=m
CONFIG_ATM_TCP=m
CONFIG_ATM_LANAI=m
CONFIG_ATM_ENI=m
# CONFIG_ATM_ENI_DEBUG is not set
# CONFIG_ATM_ENI_TUNE_BURST is not set
# CONFIG_ATM_FIRESTREAM is not set
# CONFIG_ATM_ZATM is not set
# CONFIG_ATM_NICSTAR is not set
# CONFIG_ATM_IDT77252 is not set
# CONFIG_ATM_AMBASSADOR is not set
# CONFIG_ATM_HORIZON is not set
# CONFIG_ATM_IA is not set
# CONFIG_ATM_FORE200E_MAYBE is not set
# CONFIG_ATM_HE is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
CONFIG_PPPOATM=m
# CONFIG_PPPOL2TP is not set
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLHC=m
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y
CONFIG_NET_FC=y
CONFIG_NETCONSOLE=m
# CONFIG_NETCONSOLE_DYNAMIC is not set
CONFIG_NETPOLL=y
CONFIG_NETPOLL_TRAP=y
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_VIRTIO_NET=m
# CONFIG_ISDN is not set
CONFIG_PHONE=m
CONFIG_PHONE_IXJ=m
CONFIG_PHONE_IXJ_PCMCIA=m

#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=m
CONFIG_INPUT_POLLDEV=m

#
# 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=m
CONFIG_INPUT_EVDEV=m
# 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=m
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_SERIAL=m
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_VSXXXAA is not set
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
CONFIG_JOYSTICK_A3D=m
CONFIG_JOYSTICK_ADI=m
CONFIG_JOYSTICK_COBRA=m
CONFIG_JOYSTICK_GF2K=m
CONFIG_JOYSTICK_GRIP=m
CONFIG_JOYSTICK_GRIP_MP=m
CONFIG_JOYSTICK_GUILLEMOT=m
CONFIG_JOYSTICK_INTERACT=m
CONFIG_JOYSTICK_SIDEWINDER=m
CONFIG_JOYSTICK_TMDC=m
CONFIG_JOYSTICK_IFORCE=m
CONFIG_JOYSTICK_IFORCE_USB=y
CONFIG_JOYSTICK_IFORCE_232=y
CONFIG_JOYSTICK_WARRIOR=m
CONFIG_JOYSTICK_MAGELLAN=m
CONFIG_JOYSTICK_SPACEORB=m
CONFIG_JOYSTICK_SPACEBALL=m
CONFIG_JOYSTICK_STINGER=m
CONFIG_JOYSTICK_TWIDJOY=m
# CONFIG_JOYSTICK_ZHENHUA is not set
CONFIG_JOYSTICK_JOYDUMP=m
# CONFIG_JOYSTICK_XPAD is not set
# CONFIG_INPUT_TABLET is not set
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_FUJITSU is not set
CONFIG_TOUCHSCREEN_GUNZE=m
CONFIG_TOUCHSCREEN_ELO=m
CONFIG_TOUCHSCREEN_MTOUCH=m
CONFIG_TOUCHSCREEN_MK712=m
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_UCB1400 is not set
# CONFIG_TOUCHSCREEN_WM97XX is not set
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_APANEL is not set
# CONFIG_INPUT_WISTRON_BTNS is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
# CONFIG_INPUT_ATI_REMOTE is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
CONFIG_INPUT_UINPUT=m

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

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

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=8
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=y
CONFIG_HW_RANDOM_GEODE=y
CONFIG_HW_RANDOM_VIA=y
CONFIG_NVRAM=m
# CONFIG_R3964 is not set
CONFIG_APPLICOM=m
# CONFIG_SONYPI is not set

#
# PCMCIA character devices
#
CONFIG_SYNCLINK_CS=m
# CONFIG_CARDMAN_4000 is not set
# CONFIG_CARDMAN_4040 is not set
CONFIG_IPWIRELESS=m
CONFIG_MWAVE=m
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_GPIO is not set
CONFIG_RAW_DRIVER=m
CONFIG_MAX_RAW_DEVS=1024
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
CONFIG_HANGCHECK_TIMER=m
CONFIG_TCG_TPM=m
CONFIG_TCG_TIS=m
CONFIG_TCG_NSC=m
CONFIG_TCG_ATMEL=m
CONFIG_TCG_INFINEON=m
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=m
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=m
CONFIG_I2C_ALGOBIT=m

#
# I2C Hardware Bus support
#
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI1563=m
CONFIG_I2C_ALI15X3=m
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD756_S4882=m
CONFIG_I2C_AMD8111=m
CONFIG_I2C_I801=m
CONFIG_I2C_I810=m
CONFIG_I2C_PIIX4=m
CONFIG_I2C_NFORCE2=m
# CONFIG_I2C_OCORES is not set
CONFIG_I2C_PARPORT_LIGHT=m
CONFIG_I2C_PROSAVAGE=m
CONFIG_I2C_SAVAGE4=m
# CONFIG_I2C_SIMTEC is not set
CONFIG_SCx200_ACB=m
CONFIG_I2C_SIS5595=m
CONFIG_I2C_SIS630=m
CONFIG_I2C_SIS96X=m
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_TINY_USB is not set
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
CONFIG_I2C_VOODOO3=m
# CONFIG_I2C_PCA_PLATFORM is not set

#
# Miscellaneous I2C Chip support
#
# CONFIG_DS1682 is not set
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_PCF8574=m
CONFIG_PCF8575=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_MAX6875=m
# 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=m
CONFIG_W1_CON=y

#
# 1-wire Bus Masters
#
# CONFIG_W1_MASTER_MATROX is not set
# CONFIG_W1_MASTER_DS2490 is not set
# CONFIG_W1_MASTER_DS2482 is not set

#
# 1-wire Slaves
#
CONFIG_W1_SLAVE_THERM=m
# CONFIG_W1_SLAVE_SMEM is not set
# CONFIG_W1_SLAVE_DS2433 is not set
# CONFIG_W1_SLAVE_DS2760 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
CONFIG_PDA_POWER=m
# CONFIG_BATTERY_DS2760 is not set
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7418 is not set
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7473 is not set
# CONFIG_SENSORS_K8TEMP is not set
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS1621=m
# 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=m
CONFIG_SENSORS_FSCPOS=m
# CONFIG_SENSORS_FSCHMD is not set
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
# CONFIG_SENSORS_CORETEMP is not set
# CONFIG_SENSORS_IBMPEX is not set
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
# CONFIG_SENSORS_LM93 is not set
CONFIG_SENSORS_MAX1619=m
# CONFIG_SENSORS_MAX6650 is not set
CONFIG_SENSORS_PC87360=m
# CONFIG_SENSORS_PC87427 is not set
CONFIG_SENSORS_SIS5595=m
# CONFIG_SENSORS_DME1737 is not set
CONFIG_SENSORS_SMSC47M1=m
# CONFIG_SENSORS_SMSC47M192 is not set
CONFIG_SENSORS_SMSC47B397=m
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_THMC50 is not set
CONFIG_SENSORS_VIA686A=m
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
CONFIG_SENSORS_W83781D=m
# CONFIG_SENSORS_W83791D is not set
CONFIG_SENSORS_W83792D=m
# CONFIG_SENSORS_W83793 is not set
CONFIG_SENSORS_W83L785TS=m
# CONFIG_SENSORS_W83L786NG is not set
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
CONFIG_SENSORS_HDAPS=m
# 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=m
# 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=m
CONFIG_ITCO_WDT=m
CONFIG_ITCO_VENDOR_SUPPORT=y
# 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_SBC7240_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_SMSC37B787_WDT is not set
# CONFIG_W83627HF_WDT is not set
# CONFIG_W83697HF_WDT is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_W83977F_WDT is not set
# CONFIG_MACHZ_WDT is not set
# CONFIG_SBC_EPX_C3_WATCHDOG is not set

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

#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set

#
# 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=m
CONFIG_VIDEO_V4L2_COMMON=m
CONFIG_VIDEO_ALLOW_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
# CONFIG_DVB_CORE is not set
CONFIG_VIDEO_MEDIA=m

#
# Multimedia drivers
#
CONFIG_MEDIA_ATTACH=y
CONFIG_MEDIA_TUNER=m
# CONFIG_MEDIA_TUNER_CUSTOMIZE is not set
CONFIG_MEDIA_TUNER_SIMPLE=m
CONFIG_MEDIA_TUNER_TDA8290=m
CONFIG_MEDIA_TUNER_TDA9887=m
CONFIG_MEDIA_TUNER_TEA5761=m
CONFIG_MEDIA_TUNER_TEA5767=m
CONFIG_MEDIA_TUNER_MT20XX=m
CONFIG_MEDIA_TUNER_XC2028=m
CONFIG_MEDIA_TUNER_XC5000=m
CONFIG_VIDEO_V4L2=m
CONFIG_VIDEO_V4L1=m
CONFIG_VIDEOBUF_GEN=m
CONFIG_VIDEOBUF_VMALLOC=m
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
CONFIG_VIDEO_VIVI=m
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set
# CONFIG_VIDEO_IVTV is not set
# CONFIG_VIDEO_CAFE_CCIC is not set
CONFIG_V4L_USB_DRIVERS=y
# CONFIG_VIDEO_PVRUSB2 is not set
# CONFIG_VIDEO_EM28XX is not set
# CONFIG_VIDEO_USBVISION is not set
CONFIG_VIDEO_USBVIDEO=m
# CONFIG_USB_VICAM is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
CONFIG_USB_QUICKCAM_MESSENGER=m
# CONFIG_USB_ET61X251 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
# CONFIG_USB_W9968CF is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set
CONFIG_USB_ZC0301=m
CONFIG_USB_PWC=m
# CONFIG_USB_PWC_DEBUG is not set
# CONFIG_USB_ZR364XX is not set
# CONFIG_USB_STKWEBCAM is not set
# CONFIG_SOC_CAMERA is not set
CONFIG_RADIO_ADAPTERS=y
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_SI470X is not set
CONFIG_DAB=y
CONFIG_USB_DABUSB=m

#
# Graphics support
#
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=m
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_I915 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_VGASTATE is not set
CONFIG_VIDEO_OUTPUT_CONTROL=m
# CONFIG_FB is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_LCD_CLASS_DEVICE=m
CONFIG_BACKLIGHT_CLASS_DEVICE=m
# CONFIG_BACKLIGHT_CORGI is not set
# CONFIG_BACKLIGHT_PROGEAR is not set

#
# Display device support
#
CONFIG_DISPLAY_SUPPORT=m

#
# Display hardware drivers
#

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_VIDEO_SELECT=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FONT_8x16=y

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
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=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_VMASTER=y

#
# Generic devices
#
CONFIG_SND_PCSP=m
CONFIG_SND_MPU401_UART=m
CONFIG_SND_AC97_CODEC=m
# CONFIG_SND_DUMMY is not set
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
CONFIG_SND_SERIAL_U16550=m
CONFIG_SND_MPU401=m

#
# PCI devices
#
CONFIG_SND_AD1889=m
# 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_CS5535AUDIO is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
CONFIG_SND_HDA_INTEL=m
CONFIG_SND_HDA_HWDEP=y
CONFIG_SND_HDA_CODEC_REALTEK=y
CONFIG_SND_HDA_CODEC_ANALOG=y
CONFIG_SND_HDA_CODEC_SIGMATEL=y
CONFIG_SND_HDA_CODEC_VIA=y
CONFIG_SND_HDA_CODEC_ATIHDMI=y
CONFIG_SND_HDA_CODEC_CONEXANT=y
CONFIG_SND_HDA_CODEC_CMEDIA=y
CONFIG_SND_HDA_CODEC_SI3054=y
CONFIG_SND_HDA_GENERIC=y
# CONFIG_SND_HDA_POWER_SAVE 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=m
CONFIG_SND_INTEL8X0M=m
# 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_SIS7019 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_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

#
# PCMCIA devices
#
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_PDAUDIOCF 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=m
CONFIG_HID_SUPPORT=y
CONFIG_HID=m
# CONFIG_HID_DEBUG is not set
CONFIG_HIDRAW=y

#
# USB Input Devices
#
CONFIG_USB_HID=m
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
CONFIG_HID_FF=y
CONFIG_HID_PID=y
CONFIG_LOGITECH_FF=y
# CONFIG_LOGIRUMBLEPAD2_FF is not set
# CONFIG_PANTHERLORD_FF is not set
CONFIG_THRUSTMASTER_FF=y
# CONFIG_ZEROPLUS_FF is not set
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y

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

#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_ROOT_HUB_TT=y
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
CONFIG_USB_ISP116X_HCD=m
# CONFIG_USB_ISP1760_HCD is not set
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_SL811_HCD=m
CONFIG_USB_SL811_CS=m
# CONFIG_USB_R8A66597_HCD is not set

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

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

#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
# 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=y

#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m
CONFIG_USB_MON=y

#
# USB port drivers
#
CONFIG_USB_SERIAL=m
CONFIG_USB_EZUSB=y
CONFIG_USB_SERIAL_GENERIC=y
# CONFIG_USB_SERIAL_AIRCABLE is not set
CONFIG_USB_SERIAL_AIRPRIME=m
# CONFIG_USB_SERIAL_ARK3116 is not set
CONFIG_USB_SERIAL_BELKIN=m
# CONFIG_USB_SERIAL_CH341 is not set
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CP2101=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
# CONFIG_USB_SERIAL_FUNSOFT is not set
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
# CONFIG_USB_SERIAL_IUU is not set
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KEYSPAN_MPR=y
CONFIG_USB_SERIAL_KEYSPAN_USA28=y
CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
CONFIG_USB_SERIAL_KEYSPAN_USA19=y
CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
# CONFIG_USB_SERIAL_MOS7720 is not set
# CONFIG_USB_SERIAL_MOS7840 is not set
CONFIG_USB_SERIAL_MOTOROLA=m
# CONFIG_USB_SERIAL_NAVMAN is not set
CONFIG_USB_SERIAL_PL2303=m
# CONFIG_USB_SERIAL_OTI6858 is not set
# CONFIG_USB_SERIAL_SPCP8X5 is not set
CONFIG_USB_SERIAL_HP4X=m
CONFIG_USB_SERIAL_SAFE=m
CONFIG_USB_SERIAL_SAFE_PADDED=y
# CONFIG_USB_SERIAL_SIERRAWIRELESS is not set
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
# CONFIG_USB_SERIAL_DEBUG is not set

#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
# CONFIG_USB_ADUTUX is not set
CONFIG_USB_AUERSWALD=m
CONFIG_USB_RIO500=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
# CONFIG_USB_BERRY_CHARGE is not set
CONFIG_USB_LED=m
# CONFIG_USB_CYPRESS_CY7C63 is not set
CONFIG_USB_CYTHERM=m
# CONFIG_USB_PHIDGET is not set
CONFIG_USB_IDMOUSE=m
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
CONFIG_USB_SISUSBVGA=m
CONFIG_USB_SISUSBVGA_CON=y
CONFIG_USB_LD=m
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
CONFIG_USB_TEST=m
CONFIG_USB_ATM=m
CONFIG_USB_SPEEDTOUCH=m
CONFIG_USB_CXACRU=m
CONFIG_USB_UEAGLEATM=m
CONFIG_USB_XUSBATM=m
CONFIG_USB_GADGET=m
# CONFIG_USB_GADGET_DEBUG is not set
# CONFIG_USB_GADGET_DEBUG_FILES is not set
# CONFIG_USB_GADGET_DEBUG_FS is not set
CONFIG_USB_GADGET_SELECTED=y
CONFIG_USB_GADGET_AMD5536UDC=y
CONFIG_USB_AMD5536UDC=m
# CONFIG_USB_GADGET_ATMEL_USBA is not set
# CONFIG_USB_GADGET_FSL_USB2 is not set
# CONFIG_USB_GADGET_NET2280 is not set
# CONFIG_USB_GADGET_PXA2XX is not set
# CONFIG_USB_GADGET_M66592 is not set
# CONFIG_USB_GADGET_PXA27X is not set
# CONFIG_USB_GADGET_GOKU is not set
# CONFIG_USB_GADGET_LH7A40X is not set
# CONFIG_USB_GADGET_OMAP is not set
# CONFIG_USB_GADGET_S3C2410 is not set
# CONFIG_USB_GADGET_AT91 is not set
# CONFIG_USB_GADGET_DUMMY_HCD is not set
CONFIG_USB_GADGET_DUALSPEED=y
CONFIG_USB_ZERO=m
CONFIG_USB_ETH=m
CONFIG_USB_ETH_RNDIS=y
CONFIG_USB_GADGETFS=m
CONFIG_USB_FILE_STORAGE=m
# CONFIG_USB_FILE_STORAGE_TEST is not set
CONFIG_USB_G_SERIAL=m
# CONFIG_USB_MIDI_GADGET is not set
CONFIG_USB_G_PRINTER=m
CONFIG_MMC=m
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set

#
# MMC/SD Card Drivers
#
CONFIG_MMC_BLOCK=m
CONFIG_MMC_BLOCK_BOUNCE=y
CONFIG_SDIO_UART=m
# CONFIG_MMC_TEST is not set

#
# MMC/SD Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
CONFIG_MMC_RICOH_MMC=m
CONFIG_MMC_WBSD=m
# CONFIG_MMC_TIFM_SD is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=m

#
# LED drivers
#
# CONFIG_LEDS_CLEVO_MAIL is not set

#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_IDE_DISK=y
CONFIG_LEDS_TRIGGER_HEARTBEAT=m
CONFIG_LEDS_TRIGGER_DEFAULT_ON=m
CONFIG_ACCESSIBILITY=y
# CONFIG_A11Y_BRAILLE_CONSOLE is not set
# CONFIG_INFINIBAND is not set
# CONFIG_EDAC is not set
CONFIG_RTC_LIB=m
CONFIG_RTC_CLASS=m

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# 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=m
# 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=y

#
# DMA Devices
#
CONFIG_INTEL_IOATDMA=m
CONFIG_DMA_ENGINE=y

#
# DMA Clients
#
CONFIG_NET_DMA=y
CONFIG_DCA=m
CONFIG_UIO=m
# CONFIG_UIO_CIF is not set
# CONFIG_UIO_SMX is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
CONFIG_DMIID=y
CONFIG_ISCSI_IBFT_FIND=y
CONFIG_ISCSI_IBFT=m

#
# File systems
#
CONFIG_EXT2_FS=m
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=m
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4DEV_FS=m
CONFIG_EXT4DEV_FS_XATTR=y
CONFIG_EXT4DEV_FS_POSIX_ACL=y
CONFIG_EXT4DEV_FS_SECURITY=y
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=m
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=m
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
# CONFIG_XFS_RT is not set
# CONFIG_XFS_DEBUG is not set
CONFIG_GFS2_FS=m
CONFIG_GFS2_FS_LOCKING_NOLOCK=m
CONFIG_GFS2_FS_LOCKING_DLM=m
CONFIG_OCFS2_FS=m
CONFIG_OCFS2_FS_O2CB=m
CONFIG_OCFS2_FS_USERSPACE_CLUSTER=m
CONFIG_OCFS2_DEBUG_MASKLOG=y
# CONFIG_OCFS2_DEBUG_FS is not set
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
CONFIG_PRINT_QUOTA_WARNING=y
CONFIG_QFMT_V1=m
CONFIG_QFMT_V2=m
CONFIG_QUOTACTL=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=m
CONFIG_GENERIC_ACL=y

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

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

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
# CONFIG_PROC_KCORE is not set
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_CONFIGFS_FS=m

#
# Miscellaneous filesystems
#
CONFIG_ADFS_FS=m
CONFIG_ADFS_FS_RW=y
CONFIG_AFFS_FS=m
CONFIG_ECRYPT_FS=m
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
CONFIG_BEFS_FS=m
# CONFIG_BEFS_DEBUG is not set
CONFIG_BFS_FS=m
CONFIG_EFS_FS=m
CONFIG_JFFS2_FS=m
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
# CONFIG_JFFS2_FS_WBUF_VERIFY is not set
# CONFIG_JFFS2_SUMMARY is not set
CONFIG_JFFS2_FS_XATTR=y
CONFIG_JFFS2_FS_POSIX_ACL=y
CONFIG_JFFS2_FS_SECURITY=y
CONFIG_JFFS2_COMPRESSION_OPTIONS=y
CONFIG_JFFS2_ZLIB=y
CONFIG_JFFS2_LZO=y
CONFIG_JFFS2_RTIME=y
CONFIG_JFFS2_RUBIN=y
# CONFIG_JFFS2_CMODE_NONE is not set
CONFIG_JFFS2_CMODE_PRIORITY=y
# CONFIG_JFFS2_CMODE_SIZE is not set
# CONFIG_JFFS2_CMODE_FAVOURLZO is not set
CONFIG_CRAMFS=m
CONFIG_VXFS_FS=m
CONFIG_MINIX_FS=m
CONFIG_HPFS_FS=m
CONFIG_QNX4FS_FS=m
CONFIG_ROMFS_FS=y
CONFIG_SYSV_FS=m
CONFIG_UFS_FS=m
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_UFS_DEBUG is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
# CONFIG_SUNRPC_BIND34 is not set
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_RPCSEC_GSS_SPKM3=m
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="iso8859-2"
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
CONFIG_CIFS_EXPERIMENTAL=y
# CONFIG_CIFS_UPCALL is not set
CONFIG_CIFS_DFS_UPCALL=y
CONFIG_NCP_FS=m
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
CONFIG_NCPFS_SMALLDOS=y
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
CONFIG_CODA_FS=m
# CONFIG_CODA_FS_OLD_API is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
CONFIG_ACORN_PARTITION=y
CONFIG_ACORN_PARTITION_CUMANA=y
CONFIG_ACORN_PARTITION_EESOX=y
CONFIG_ACORN_PARTITION_ICS=y
CONFIG_ACORN_PARTITION_ADFS=y
CONFIG_ACORN_PARTITION_POWERTEC=y
CONFIG_ACORN_PARTITION_RISCIX=y
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
CONFIG_ATARI_PARTITION=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
CONFIG_SGI_PARTITION=y
CONFIG_ULTRIX_PARTITION=y
CONFIG_SUN_PARTITION=y
# CONFIG_KARMA_PARTITION is not set
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m
CONFIG_DLM=m
# CONFIG_DLM_DEBUG 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=1024
CONFIG_MAGIC_SYSRQ=y
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
# CONFIG_DETECT_SOFTLOCKUP is not set
CONFIG_SCHED_DEBUG=y
CONFIG_SCHEDSTATS=y
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_WRITECOUNT is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
CONFIG_FRAME_POINTER=y
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST 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_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
# CONFIG_NONPROMISC_DEVMEM is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_X86_PTDUMP is not set
# CONFIG_DEBUG_RODATA is not set
# CONFIG_DEBUG_NX_TEST is not set
# CONFIG_4KSTACKS is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=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=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not set

#
# Security options
#
CONFIG_KEYS=y
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_NETWORK_XFRM=y
CONFIG_SECURITY_CAPABILITIES=y
CONFIG_SECURITY_FILE_CAPABILITIES=y
CONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR=0
# CONFIG_SECURITY_SELINUX is not set
# CONFIG_SECURITY_SMACK is not set
CONFIG_XOR_BLOCKS=m
CONFIG_ASYNC_CORE=m
CONFIG_ASYNC_MEMCPY=m
CONFIG_ASYNC_XOR=m
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_GF128MUL=m
CONFIG_CRYPTO_NULL=m
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=m
# CONFIG_CRYPTO_TEST is not set

#
# Authenticated Encryption with Associated Data
#
CONFIG_CRYPTO_CCM=m
CONFIG_CRYPTO_GCM=m
CONFIG_CRYPTO_SEQIV=m

#
# Block modes
#
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_CTR=m
CONFIG_CRYPTO_CTS=m
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_LRW=m
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_XTS=m

#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=m

#
# Digest
#
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_WP512=m

#
# Ciphers
#
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_CAMELLIA=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_FCRYPT=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_SALSA20=m
CONFIG_CRYPTO_SALSA20_586=m
CONFIG_CRYPTO_SEED=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_TWOFISH_586=m

#
# Compression
#
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_LZO=m
CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO_DEV_PADLOCK=m
CONFIG_CRYPTO_DEV_PADLOCK_AES=m
CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
CONFIG_CRYPTO_DEV_GEODE=m
# CONFIG_CRYPTO_DEV_HIFN_795X is not set
CONFIG_HAVE_KVM=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=m
CONFIG_KVM_INTEL=m
CONFIG_KVM_AMD=m
# CONFIG_LGUEST is not set
CONFIG_VIRTIO=m
CONFIG_VIRTIO_RING=m
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIO_BALLOON=m

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
CONFIG_CRC7=m
CONFIG_LIBCRC32C=m
CONFIG_AUDIT_GENERIC=y
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_LZO_COMPRESS=m
CONFIG_LZO_DECOMPRESS=m
CONFIG_REED_SOLOMON=m
CONFIG_REED_SOLOMON_DEC16=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: cpufreq limits avilable frequencies to 800MHz on git kernel
  2008-05-23 17:44 cpufreq limits avilable frequencies to 800MHz on git kernel Arkadiusz Miskiewicz
@ 2008-05-24  1:25 ` Andrew Morton
  2008-05-25  9:36   ` Arkadiusz Miskiewicz
  0 siblings, 1 reply; 13+ messages in thread
From: Andrew Morton @ 2008-05-24  1:25 UTC (permalink / raw)
  To: Arkadiusz Miskiewicz; +Cc: linux-kernel, cpufreq

On Fri, 23 May 2008 19:44:57 +0200 Arkadiusz Miskiewicz <arekm@maven.pl> wrote:

> thinkpad z60m, Intel(R) Pentium(R) M processor 2.00GHz. kernel from git from 
> 1-2 days ago. 
> 
> Unfortunately it seems that suspend to ram/resume causes frequency
> to be limited to 800MHz only. I can't set it to 2GHz again :-/
> 
> scaling_max_freq is then 800000 and cannot be changed.
> 
> reboot and the problem disappears until new suspend/resume cycle.
> 
> cpufreq stuff is driven by acpi-cpufreq
> 
> $ cpufreq-info
> cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
> Report errors and bugs to linux@brodo.de, please.
> analyzing CPU 0:
>   driver: acpi-cpufreq
>   CPUs which need to switch frequency at the same time: 0
>   hardware limits: 800 MHz - 2.00 GHz
>   available frequency steps: 2.00 GHz, 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
>   available cpufreq governors: powersave, userspace, ondemand, performance
>   current policy: frequency should be within 800 MHz and 800 MHz.
>                   The governor "performance" may decide which speed to use
>                   within this range.
>   current CPU frequency is 800 MHz.
> 
> /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:800000
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:2000000
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:800000
> /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:2000000 
> 1600000 1333000 1066000 800000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:powersave 
> userspace ondemand performance
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:800000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufreq
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:performance
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:800000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:800000
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:<unsupported>

Thanks.  Is this a newly-occurring bug or did earlier kernels do this also?

If it was newly added, do you know in which kernel version we might
have added it?


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: cpufreq limits avilable frequencies to 800MHz on git kernel
  2008-05-24  1:25 ` Andrew Morton
@ 2008-05-25  9:36   ` Arkadiusz Miskiewicz
  2008-05-25 15:03     ` Thomas Renninger
  0 siblings, 1 reply; 13+ messages in thread
From: Arkadiusz Miskiewicz @ 2008-05-25  9:36 UTC (permalink / raw)
  To: linux-kernel; +Cc: Andrew Morton, cpufreq

On Saturday 24 May 2008, Andrew Morton wrote:
> On Fri, 23 May 2008 19:44:57 +0200 Arkadiusz Miskiewicz <arekm@maven.pl> 
wrote:
> > thinkpad z60m, Intel(R) Pentium(R) M processor 2.00GHz. kernel from git
> > from 1-2 days ago.
> >
> > Unfortunately it seems that suspend to ram/resume causes frequency
> > to be limited to 800MHz only. I can't set it to 2GHz again :-/
> >
> > scaling_max_freq is then 800000 and cannot be changed.
> >
> > reboot and the problem disappears until new suspend/resume cycle.
> >
> > cpufreq stuff is driven by acpi-cpufreq
> >
> > $ cpufreq-info
> > cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
> > Report errors and bugs to linux@brodo.de, please.
> > analyzing CPU 0:
> >   driver: acpi-cpufreq
> >   CPUs which need to switch frequency at the same time: 0
> >   hardware limits: 800 MHz - 2.00 GHz
> >   available frequency steps: 2.00 GHz, 1.60 GHz, 1.33 GHz, 1.07 GHz, 800
> > MHz available cpufreq governors: powersave, userspace, ondemand,
> > performance current policy: frequency should be within 800 MHz and 800
> > MHz. The governor "performance" may decide which speed to use within this
> > range.
> >   current CPU frequency is 800 MHz.
> >
> > /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
> > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:800000
> > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:2000000
> > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:800000
> > /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:200000
> >0 1600000 1333000 1066000 800000
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:powersav
> >e userspace ondemand performance
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:800000
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufreq
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:performance
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:800000
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:800000
> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:<unsupported>
>
> Thanks.  Is this a newly-occurring bug or did earlier kernels do this also?
>
> If it was newly added, do you know in which kernel version we might
> have added it?

I wasn't able to reproduce the problem on final 2.6.24 but was able to 
reproduce on final 2.6.25. Problem introduced somewhere between it seems.

Note that 2-3 suspend to ram/resume cycles is needed to get into the problem.

-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: cpufreq limits avilable frequencies to 800MHz on git kernel
  2008-05-25  9:36   ` Arkadiusz Miskiewicz
@ 2008-05-25 15:03     ` Thomas Renninger
  2008-05-26  7:07       ` Arkadiusz Miskiewicz
  0 siblings, 1 reply; 13+ messages in thread
From: Thomas Renninger @ 2008-05-25 15:03 UTC (permalink / raw)
  To: Arkadiusz Miskiewicz
  Cc: linux-kernel, cpufreq, Andrew Morton, gnorton, miguel

On Sun, 2008-05-25 at 11:36 +0200, Arkadiusz Miskiewicz wrote:
> On Saturday 24 May 2008, Andrew Morton wrote:
> > On Fri, 23 May 2008 19:44:57 +0200 Arkadiusz Miskiewicz <arekm@maven.pl> 
> wrote:
> > > thinkpad z60m, Intel(R) Pentium(R) M processor 2.00GHz. kernel from git
> > > from 1-2 days ago.
> > >
> > > Unfortunately it seems that suspend to ram/resume causes frequency
> > > to be limited to 800MHz only. I can't set it to 2GHz again :-/
> > >
> > > scaling_max_freq is then 800000 and cannot be changed.
> > >
> > > reboot and the problem disappears until new suspend/resume cycle.
> > >
> > > cpufreq stuff is driven by acpi-cpufreq
> > >
> > > $ cpufreq-info
> > > cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
> > > Report errors and bugs to linux@brodo.de, please.
> > > analyzing CPU 0:
> > >   driver: acpi-cpufreq
> > >   CPUs which need to switch frequency at the same time: 0
> > >   hardware limits: 800 MHz - 2.00 GHz
> > >   available frequency steps: 2.00 GHz, 1.60 GHz, 1.33 GHz, 1.07 GHz, 800
> > > MHz available cpufreq governors: powersave, userspace, ondemand,
> > > performance current policy: frequency should be within 800 MHz and 800
> > > MHz. The governor "performance" may decide which speed to use within this
> > > range.
> > >   current CPU frequency is 800 MHz.
> > >
> > > /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
> > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:800000
> > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:2000000
> > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:800000
> > > /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0
> > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:200000
> > >0 1600000 1333000 1066000 800000
> > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:powersav
> > >e userspace ondemand performance
> > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:800000
> > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufreq
> > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:performance
> > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:800000
> > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:800000
> > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:<unsupported>
> >
> > Thanks.  Is this a newly-occurring bug or did earlier kernels do this also?
> >
> > If it was newly added, do you know in which kernel version we might
> > have added it?
> 
> I wasn't able to reproduce the problem on final 2.6.24 but was able to 
> reproduce on final 2.6.25. Problem introduced somewhere between it seems.
> 
> Note that 2-3 suspend to ram/resume cycles is needed to get into the problem.

Sounds related to:
[Bug 374099] T61p speedstep problems (ondemand scheduler)
https://bugzilla.novell.com/show_bug.cgi?id=374099

Miguel speaks from "good boots" and "bad boots".

Could you check whether the OS thinks it is too hot.
I described some basics how to monitor temperature and cpufreq (if
passive cooling kicks in) here:
https://bugzilla.novell.com/show_bug.cgi?id=387702#c13

Hmm, it may just have been fixed by this one:
commit e56a727b023d40d1adf660168883f30f2e6abe0a
Author: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Date:   Mon Apr 28 15:13:43 2008 -0400

Miguel, Geoff: This is already in 11.0 for some time and in 10.3 for
some days.

       Thomas


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: cpufreq limits avilable frequencies to 800MHz on git kernel
  2008-05-25 15:03     ` Thomas Renninger
@ 2008-05-26  7:07       ` Arkadiusz Miskiewicz
  2008-05-26 11:37         ` Thomas Renninger
  2008-05-26 12:28         ` Thomas Renninger
  0 siblings, 2 replies; 13+ messages in thread
From: Arkadiusz Miskiewicz @ 2008-05-26  7:07 UTC (permalink / raw)
  To: linux-kernel, trenn; +Cc: cpufreq, Andrew Morton, gnorton, miguel

On Sunday 25 May 2008, Thomas Renninger wrote:
> On Sun, 2008-05-25 at 11:36 +0200, Arkadiusz Miskiewicz wrote:
> > On Saturday 24 May 2008, Andrew Morton wrote:
> > > On Fri, 23 May 2008 19:44:57 +0200 Arkadiusz Miskiewicz
> > > <arekm@maven.pl>
> >
> > wrote:
> > > > thinkpad z60m, Intel(R) Pentium(R) M processor 2.00GHz. kernel from
> > > > git from 1-2 days ago.
> > > >
> > > > Unfortunately it seems that suspend to ram/resume causes frequency
> > > > to be limited to 800MHz only. I can't set it to 2GHz again :-/
> > > >
> > > > scaling_max_freq is then 800000 and cannot be changed.
> > > >
> > > > reboot and the problem disappears until new suspend/resume cycle.
> > > >
> > > > cpufreq stuff is driven by acpi-cpufreq
> > > >
> > > > $ cpufreq-info
> > > > cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
> > > > Report errors and bugs to linux@brodo.de, please.
> > > > analyzing CPU 0:
> > > >   driver: acpi-cpufreq
> > > >   CPUs which need to switch frequency at the same time: 0
> > > >   hardware limits: 800 MHz - 2.00 GHz
> > > >   available frequency steps: 2.00 GHz, 1.60 GHz, 1.33 GHz, 1.07 GHz,
> > > > 800 MHz available cpufreq governors: powersave, userspace, ondemand,
> > > > performance current policy: frequency should be within 800 MHz and
> > > > 800 MHz. The governor "performance" may decide which speed to use
> > > > within this range.
> > > >   current CPU frequency is 800 MHz.
> > > >
> > > > /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
> > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:800000
> > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:2000000
> > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:800000
> > > > /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0
> > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:20
> > > >0000 0 1600000 1333000 1066000 800000
> > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:powe
> > > >rsav e userspace ondemand performance
> > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:800000
> > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufreq
> > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:performance
> > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:800000
> > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:800000
> > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:<unsupported>
> > >
> > > Thanks.  Is this a newly-occurring bug or did earlier kernels do this
> > > also?
> > >
> > > If it was newly added, do you know in which kernel version we might
> > > have added it?
> >
> > I wasn't able to reproduce the problem on final 2.6.24 but was able to
> > reproduce on final 2.6.25. Problem introduced somewhere between it seems.
> >
> > Note that 2-3 suspend to ram/resume cycles is needed to get into the
> > problem.
>
> Sounds related to:
> [Bug 374099] T61p speedstep problems (ondemand scheduler)
> https://bugzilla.novell.com/show_bug.cgi?id=374099

login/pass protected

>
> Miguel speaks from "good boots" and "bad boots".

Actually I also got "bad boot" (so no suspend/resume was needed).

>
> Could you check whether the OS thinks it is too hot.
> I described some basics how to monitor temperature and cpufreq (if
> passive cooling kicks in) here:
> https://bugzilla.novell.com/show_bug.cgi?id=387702#c13

Doesn't seem to be overheated

[arekm@tarm ~]$ cat /proc/acpi/thermal_zone/*/{temperature,trip_points,state}; cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_{cur_freq,max_freq}
temperature:             45 C
critical (S5):           99 C
passive:                 95 C: tc1=5 tc2=4 tsp=600 devices= CPU
state:                   ok
800000
800000

but still limited to 800MHz.

>
> Hmm, it may just have been fixed by this one:
> commit e56a727b023d40d1adf660168883f30f2e6abe0a
> Author: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> Date:   Mon Apr 28 15:13:43 2008 -0400
>
> Miguel, Geoff: This is already in 11.0 for some time and in 10.3 for
> some days.

Unfortunately it doesn't fix the problem. The patch is in Linus tree for long
time (so I guess I had it when initially reporting the problem) + I upgraded
today to current git - the problem is still there.

>        Thomas

-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: cpufreq limits avilable frequencies to 800MHz on git kernel
  2008-05-26  7:07       ` Arkadiusz Miskiewicz
@ 2008-05-26 11:37         ` Thomas Renninger
  2008-05-26 16:15           ` Arkadiusz Miskiewicz
  2008-05-26 12:28         ` Thomas Renninger
  1 sibling, 1 reply; 13+ messages in thread
From: Thomas Renninger @ 2008-05-26 11:37 UTC (permalink / raw)
  To: Arkadiusz Miskiewicz
  Cc: linux-kernel, cpufreq, Andrew Morton, gnorton, miguel, linux-acpi

On Mon, 2008-05-26 at 09:07 +0200, Arkadiusz Miskiewicz wrote:
> On Sunday 25 May 2008, Thomas Renninger wrote:
> > On Sun, 2008-05-25 at 11:36 +0200, Arkadiusz Miskiewicz wrote:
> > > On Saturday 24 May 2008, Andrew Morton wrote:
> > > > On Fri, 23 May 2008 19:44:57 +0200 Arkadiusz Miskiewicz
> > > > <arekm@maven.pl>
> > >
> > > wrote:
> > > > > thinkpad z60m, Intel(R) Pentium(R) M processor 2.00GHz. kernel from
> > > > > git from 1-2 days ago.
> > > > >
> > > > > Unfortunately it seems that suspend to ram/resume causes frequency
> > > > > to be limited to 800MHz only. I can't set it to 2GHz again :-/
> > > > >
> > > > > scaling_max_freq is then 800000 and cannot be changed.
> > > > >
> > > > > reboot and the problem disappears until new suspend/resume cycle.
> > > > >
> > > > > cpufreq stuff is driven by acpi-cpufreq
> > > > >
> > > > > $ cpufreq-info
> > > > > cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
> > > > > Report errors and bugs to linux@brodo.de, please.
> > > > > analyzing CPU 0:
> > > > >   driver: acpi-cpufreq
> > > > >   CPUs which need to switch frequency at the same time: 0
> > > > >   hardware limits: 800 MHz - 2.00 GHz
> > > > >   available frequency steps: 2.00 GHz, 1.60 GHz, 1.33 GHz, 1.07 GHz,
> > > > > 800 MHz available cpufreq governors: powersave, userspace, ondemand,
> > > > > performance current policy: frequency should be within 800 MHz and
> > > > > 800 MHz. The governor "performance" may decide which speed to use
> > > > > within this range.
> > > > >   current CPU frequency is 800 MHz.
> > > > >
> > > > > /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
> > > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:800000
> > > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:2000000
> > > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:800000
> > > > > /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0
> > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:20
> > > > >0000 0 1600000 1333000 1066000 800000
> > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:powe
> > > > >rsav e userspace ondemand performance
> > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:800000
> > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufreq
> > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:performance
> > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:800000
> > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:800000
> > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:<unsupported>
> > > >
> > > > Thanks.  Is this a newly-occurring bug or did earlier kernels do this
> > > > also?
> > > >
> > > > If it was newly added, do you know in which kernel version we might
> > > > have added it?
> > >
> > > I wasn't able to reproduce the problem on final 2.6.24 but was able to
> > > reproduce on final 2.6.25. Problem introduced somewhere between it seems.
> > >
> > > Note that 2-3 suspend to ram/resume cycles is needed to get into the
> > > problem.
> >
> > Sounds related to:
> > [Bug 374099] T61p speedstep problems (ondemand scheduler)
> > https://bugzilla.novell.com/show_bug.cgi?id=374099
> 
> login/pass protected
> 
> >
> > Miguel speaks from "good boots" and "bad boots".
> 
> Actually I also got "bad boot" (so no suspend/resume was needed).
> 
> >
> > Could you check whether the OS thinks it is too hot.
> > I described some basics how to monitor temperature and cpufreq (if
> > passive cooling kicks in) here:
> > https://bugzilla.novell.com/show_bug.cgi?id=387702#c13
> 
> Doesn't seem to be overheated
> 
> [arekm@tarm ~]$ cat /proc/acpi/thermal_zone/*/{temperature,trip_points,state}; cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_{cur_freq,max_freq}
> temperature:             45 C
> critical (S5):           99 C
> passive:                 95 C: tc1=5 tc2=4 tsp=600 devices= CPU
> state:                   ok
> 800000
> 800000
> 
> but still limited to 800MHz.
> 
> >
> > Hmm, it may just have been fixed by this one:
> > commit e56a727b023d40d1adf660168883f30f2e6abe0a
> > Author: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> > Date:   Mon Apr 28 15:13:43 2008 -0400
> >
> > Miguel, Geoff: This is already in 11.0 for some time and in 10.3 for
> > some days.
> 
> Unfortunately it doesn't fix the problem. The patch is in Linus tree for long
> time (so I guess I had it when initially reporting the problem) + I upgraded
> today to current git - the problem is still there.

Yep, Dells and some HP should be fixed, it would have been strange if
ThinkPads are now also affected, but thanks for double checking, it
shows the same symptoms.

Then it might be _PPC.
If you compile in CPUFREQ_DEBUG and add the boot param:
cpufreq.debug=7
you should see a message in dmesg (if you do not see one, then
everything is fine you have a "good boot" and freq should be at max?):
cpufreq_printk("CPU %d: _PPC is %d - frequency %s limited\n", pr->id,
                       (int)ppc, ppc ? "" : "not");

If PPC is zero all frequencies are allowed, if it is one max_freq will
be set to the second highest freq, etc.

If it's that you can workaround that (temporarily, pls help evaluating
this further) you can use:
processor.ignore_ppc=1

I remember Ingo Molnar sent a patch to not always evaluate _PPC at
boot/initialization time, but only on processor notification events.
AFAIK this was a recent ThinkPad, so this might be it what you are
seeing. But nobody knew why some ThinkPads had a wrong _PPC value at
initialization time.

If this is PPC related, this is more an ACPI than a cpufreq issue ->
adding linux-acpi list.

   Thomas


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: cpufreq limits avilable frequencies to 800MHz on git kernel
  2008-05-26  7:07       ` Arkadiusz Miskiewicz
  2008-05-26 11:37         ` Thomas Renninger
@ 2008-05-26 12:28         ` Thomas Renninger
  1 sibling, 0 replies; 13+ messages in thread
From: Thomas Renninger @ 2008-05-26 12:28 UTC (permalink / raw)
  To: Arkadiusz Miskiewicz
  Cc: linux-kernel, cpufreq, Andrew Morton, gnorton, miguel

...
> > Sounds related to:
> > [Bug 374099] T61p speedstep problems (ondemand scheduler)
> > https://bugzilla.novell.com/show_bug.cgi?id=374099
> 
> login/pass protected
Sorry, OpenSUSE bugs should by default be public, no idea why this one
was not.
Should be public now.
Readable for the public, you can post if you get an bugzilla.novell.com
account.

Thanks,

    Thomas


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: cpufreq limits avilable frequencies to 800MHz on git kernel
  2008-05-26 11:37         ` Thomas Renninger
@ 2008-05-26 16:15           ` Arkadiusz Miskiewicz
  2008-05-26 16:23             ` Arkadiusz Miskiewicz
  2008-05-27  9:35             ` Thomas Renninger
  0 siblings, 2 replies; 13+ messages in thread
From: Arkadiusz Miskiewicz @ 2008-05-26 16:15 UTC (permalink / raw)
  To: linux-kernel, trenn; +Cc: cpufreq, Andrew Morton, gnorton, miguel, linux-acpi

On Monday 26 May 2008, Thomas Renninger wrote:
> On Mon, 2008-05-26 at 09:07 +0200, Arkadiusz Miskiewicz wrote:
> > On Sunday 25 May 2008, Thomas Renninger wrote:
> > > On Sun, 2008-05-25 at 11:36 +0200, Arkadiusz Miskiewicz wrote:
> > > > On Saturday 24 May 2008, Andrew Morton wrote:
> > > > > On Fri, 23 May 2008 19:44:57 +0200 Arkadiusz Miskiewicz
> > > > > <arekm@maven.pl>
> > > >
> > > > wrote:
> > > > > > thinkpad z60m, Intel(R) Pentium(R) M processor 2.00GHz. kernel
> > > > > > from git from 1-2 days ago.
> > > > > >
> > > > > > Unfortunately it seems that suspend to ram/resume causes
> > > > > > frequency to be limited to 800MHz only. I can't set it to 2GHz
> > > > > > again :-/
> > > > > >
> > > > > > scaling_max_freq is then 800000 and cannot be changed.
> > > > > >
> > > > > > reboot and the problem disappears until new suspend/resume cycle.
> > > > > >
> > > > > > cpufreq stuff is driven by acpi-cpufreq
> > > > > >
> > > > > > $ cpufreq-info
> > > > > > cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
> > > > > > Report errors and bugs to linux@brodo.de, please.
> > > > > > analyzing CPU 0:
> > > > > >   driver: acpi-cpufreq
> > > > > >   CPUs which need to switch frequency at the same time: 0
> > > > > >   hardware limits: 800 MHz - 2.00 GHz
> > > > > >   available frequency steps: 2.00 GHz, 1.60 GHz, 1.33 GHz, 1.07
> > > > > > GHz, 800 MHz available cpufreq governors: powersave, userspace,
> > > > > > ondemand, performance current policy: frequency should be within
> > > > > > 800 MHz and 800 MHz. The governor "performance" may decide which
> > > > > > speed to use within this range.
> > > > > >   current CPU frequency is 800 MHz.
> > > > > >
> > > > > > /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
> > > > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:800000
> > > > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:2000000
> > > > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:800000
> > > > > > /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0
> > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencie
> > > > > >s:20 0000 0 1600000 1333000 1066000 800000
> > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:
> > > > > >powe rsav e userspace ondemand performance
> > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:800000
> > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufreq
> > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:performance
> > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:800000
> > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:800000
> > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:<unsupporte
> > > > > >d>
> > > > >
> > > > > Thanks.  Is this a newly-occurring bug or did earlier kernels do
> > > > > this also?
> > > > >
> > > > > If it was newly added, do you know in which kernel version we might
> > > > > have added it?
> > > >
> > > > I wasn't able to reproduce the problem on final 2.6.24 but was able
> > > > to reproduce on final 2.6.25. Problem introduced somewhere between it
> > > > seems.
> > > >
> > > > Note that 2-3 suspend to ram/resume cycles is needed to get into the
> > > > problem.
> > >
> > > Sounds related to:
> > > [Bug 374099] T61p speedstep problems (ondemand scheduler)
> > > https://bugzilla.novell.com/show_bug.cgi?id=374099
> >
> > login/pass protected
> >
> > > Miguel speaks from "good boots" and "bad boots".
> >
> > Actually I also got "bad boot" (so no suspend/resume was needed).
> >
> > > Could you check whether the OS thinks it is too hot.
> > > I described some basics how to monitor temperature and cpufreq (if
> > > passive cooling kicks in) here:
> > > https://bugzilla.novell.com/show_bug.cgi?id=387702#c13
> >
> > Doesn't seem to be overheated
> >
> > [arekm@tarm ~]$ cat
> > /proc/acpi/thermal_zone/*/{temperature,trip_points,state}; cat
> > /sys/devices/system/cpu/cpu*/cpufreq/scaling_{cur_freq,max_freq}
> > temperature:             45 C
> > critical (S5):           99 C
> > passive:                 95 C: tc1=5 tc2=4 tsp=600 devices= CPU
> > state:                   ok
> > 800000
> > 800000
> >
> > but still limited to 800MHz.
> >
> > > Hmm, it may just have been fixed by this one:
> > > commit e56a727b023d40d1adf660168883f30f2e6abe0a
> > > Author: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> > > Date:   Mon Apr 28 15:13:43 2008 -0400
> > >
> > > Miguel, Geoff: This is already in 11.0 for some time and in 10.3 for
> > > some days.
> >
> > Unfortunately it doesn't fix the problem. The patch is in Linus tree for
> > long time (so I guess I had it when initially reporting the problem) + I
> > upgraded today to current git - the problem is still there.
>
> Yep, Dells and some HP should be fixed, it would have been strange if
> ThinkPads are now also affected, but thanks for double checking, it
> shows the same symptoms.
>
> Then it might be _PPC.
> If you compile in CPUFREQ_DEBUG and add the boot param:
> cpufreq.debug=7
> you should see a message in dmesg (if you do not see one, then
> everything is fine you have a "good boot" and freq should be at max?):
> cpufreq_printk("CPU %d: _PPC is %d - frequency %s limited\n", pr->id,
>                        (int)ppc, ppc ? "" : "not");
>
> If PPC is zero all frequencies are allowed, if it is one max_freq will
> be set to the second highest freq, etc.
>
> If it's that you can workaround that (temporarily, pls help evaluating
> this further) you can use:
> processor.ignore_ppc=1
>
> I remember Ingo Molnar sent a patch to not always evaluate _PPC at
> boot/initialization time, but only on processor notification events.
> AFAIK this was a recent ThinkPad, so this might be it what you are
> seeing. But nobody knew why some ThinkPads had a wrong _PPC value at
> initialization time.
>
> If this is PPC related, this is more an ACPI than a cpufreq issue ->
> adding linux-acpi list.

Ok, there is something, see:

[ 4093.625227] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
[ 4095.755272] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
[ 4095.755508] acpi-cpufreq: acpi_cpufreq_verify
[ 4095.755642] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
[ 4095.755780] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
[ 4095.755916] acpi-cpufreq: acpi_cpufreq_verify
[ 4095.756042] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
[ 4095.756179] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
[ 4095.756314] cpufreq-core: new min and max freqs are 800000 - 800000 kHz

PPC related messages are:

$ dmesg|grep PPC
[ 3597.291342] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
[ 3721.943484] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
[ 3881.874373] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
[ 4216.175414] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited


complete log from boot:

May 26 19:02:28 tarm kernel: [    6.125186] input: Video Bus as /class/input/input5
May 26 19:02:28 tarm kernel: [    6.145244] usbcore: registered new interface driver usbfs
May 26 19:02:28 tarm kernel: [    6.145273] usbcore: registered new interface driver hub
May 26 19:02:28 tarm kernel: [    6.145305] usbcore: registered new device driver usb
May 26 19:02:28 tarm kernel: [    6.153013] ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
May 26 19:02:28 tarm kernel: [    6.153349] input: Video Bus as /class/input/input6
May 26 19:02:28 tarm kernel: [    6.177267] USB Universal Host Controller Interface driver v3.0
May 26 19:02:28 tarm kernel: [    6.177320] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 19:02:28 tarm kernel: [    6.177330] PCI: Setting latency timer of device 0000:00:1d.0 to 64
May 26 19:02:28 tarm kernel: [    6.177334] uhci_hcd 0000:00:1d.0: UHCI Host Controller
May 26 19:02:28 tarm kernel: [    6.177561] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
May 26 19:02:28 tarm kernel: [    6.177595] uhci_hcd 0000:00:1d.0: irq 16, io base 0x00001800
May 26 19:02:28 tarm kernel: [    6.177715] usb usb1: configuration #1 chosen from 1 choice
May 26 19:02:28 tarm kernel: [    6.177742] hub 1-0:1.0: USB hub found
May 26 19:02:28 tarm kernel: [    6.177748] hub 1-0:1.0: 2 ports detected
May 26 19:02:28 tarm kernel: [    6.178737] iTCO_vendor_support: vendor-support=0
May 26 19:02:28 tarm kernel: [    6.184998] ACPI: Video Device [VID1] (multi-head: yes  rom: no  post: no)
May 26 19:02:28 tarm kernel: [    6.195516] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.03 (30-Apr-2008)
May 26 19:02:28 tarm kernel: [    6.195591] iTCO_wdt: Found a ICH6-M TCO device (Version=2, TCOBASE=0x1060)
May 26 19:02:28 tarm kernel: [    6.195619] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
May 26 19:02:28 tarm kernel: [    6.235056] intel_rng: FWH not detected
May 26 19:02:28 tarm kernel: [    6.281041] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
May 26 19:02:28 tarm kernel: [    6.281045] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 19:02:28 tarm kernel: [    6.281048] usb usb1: Product: UHCI Host Controller
May 26 19:02:28 tarm kernel: [    6.281050] usb usb1: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 19:02:28 tarm kernel: [    6.281052] usb usb1: SerialNumber: 0000:00:1d.0
May 26 19:02:28 tarm kernel: [    6.281661] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 19
May 26 19:02:28 tarm kernel: [    6.281678] PCI: Setting latency timer of device 0000:00:1d.7 to 64
May 26 19:02:28 tarm kernel: [    6.281682] ehci_hcd 0000:00:1d.7: EHCI Host Controller
May 26 19:02:29 tarm kernel: [    6.281707] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
May 26 19:02:29 tarm kernel: [    6.285625] ehci_hcd 0000:00:1d.7: debug port 1
May 26 19:02:29 tarm kernel: [    6.285631] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
May 26 19:02:29 tarm kernel: [    6.285645] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xb0004000
May 26 19:02:29 tarm kernel: [    6.292413] sd 0:0:0:0: Attached scsi generic sg0 type 0
May 26 19:02:29 tarm kernel: [    6.292434] sr 1:0:0:0: Attached scsi generic sg1 type 5
May 26 19:02:29 tarm kernel: [    6.300973] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
May 26 19:02:29 tarm kernel: [    6.301079] usb usb2: configuration #1 chosen from 1 choice
May 26 19:02:29 tarm kernel: [    6.301111] hub 2-0:1.0: USB hub found
May 26 19:02:29 tarm kernel: [    6.301118] hub 2-0:1.0: 8 ports detected
May 26 19:02:29 tarm kernel: [    6.405649] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
May 26 19:02:29 tarm kernel: [    6.405653] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 19:02:29 tarm kernel: [    6.405656] usb usb2: Product: EHCI Host Controller
May 26 19:02:29 tarm kernel: [    6.405658] usb usb2: Manufacturer: Linux 2.6.26-rc3 ehci_hcd
May 26 19:02:29 tarm kernel: [    6.405660] usb usb2: SerialNumber: 0000:00:1d.7
May 26 19:02:29 tarm kernel: [    6.405688] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 17
May 26 19:02:29 tarm kernel: [    6.405698] PCI: Setting latency timer of device 0000:00:1d.1 to 64
May 26 19:02:29 tarm kernel: [    6.405702] uhci_hcd 0000:00:1d.1: UHCI Host Controller
May 26 19:02:29 tarm kernel: [    6.405724] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
May 26 19:02:29 tarm kernel: [    6.405759] uhci_hcd 0000:00:1d.1: irq 17, io base 0x00001820
May 26 19:02:29 tarm kernel: [    6.405862] usb usb3: configuration #1 chosen from 1 choice
May 26 19:02:29 tarm kernel: [    6.405887] hub 3-0:1.0: USB hub found
May 26 19:02:29 tarm kernel: [    6.405895] hub 3-0:1.0: 2 ports detected
May 26 19:02:29 tarm kernel: [    6.509042] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
May 26 19:02:29 tarm kernel: [    6.509047] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 19:02:29 tarm kernel: [    6.509049] usb usb3: Product: UHCI Host Controller
May 26 19:02:29 tarm kernel: [    6.509052] usb usb3: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 19:02:29 tarm kernel: [    6.509054] usb usb3: SerialNumber: 0000:00:1d.1
May 26 19:02:29 tarm kernel: [    6.509104] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 19:02:29 tarm kernel: [    6.509115] PCI: Setting latency timer of device 0000:00:1d.2 to 64
May 26 19:02:29 tarm kernel: [    6.509118] uhci_hcd 0000:00:1d.2: UHCI Host Controller
May 26 19:02:29 tarm kernel: [    6.509141] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
May 26 19:02:29 tarm kernel: [    6.509173] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001840
May 26 19:02:29 tarm kernel: [    6.509274] usb usb4: configuration #1 chosen from 1 choice
May 26 19:02:29 tarm kernel: [    6.509301] hub 4-0:1.0: USB hub found
May 26 19:02:29 tarm kernel: [    6.509308] hub 4-0:1.0: 2 ports detected
May 26 19:02:29 tarm kernel: [    6.588120] ieee80211_crypt: registered algorithm 'NULL'
May 26 19:02:29 tarm kernel: [    6.591780] hub 2-0:1.0: unable to enumerate USB device on port 3
May 26 19:02:29 tarm kernel: [    6.601591] ieee80211: 802.11 data/management/control stack, git-1.1.13
May 26 19:02:29 tarm kernel: [    6.601594] ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
May 26 19:02:29 tarm kernel: [    6.613037] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
May 26 19:02:29 tarm kernel: [    6.613041] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 19:02:29 tarm kernel: [    6.613044] usb usb4: Product: UHCI Host Controller
May 26 19:02:29 tarm kernel: [    6.613046] usb usb4: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 19:02:29 tarm kernel: [    6.613048] usb usb4: SerialNumber: 0000:00:1d.2
May 26 19:02:29 tarm kernel: [    6.613095] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 19
May 26 19:02:29 tarm kernel: [    6.613106] PCI: Setting latency timer of device 0000:00:1d.3 to 64
May 26 19:02:29 tarm kernel: [    6.613109] uhci_hcd 0000:00:1d.3: UHCI Host Controller
May 26 19:02:29 tarm kernel: [    6.613132] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
May 26 19:02:29 tarm kernel: [    6.613158] uhci_hcd 0000:00:1d.3: irq 19, io base 0x00001860
May 26 19:02:29 tarm kernel: [    6.613261] usb usb5: configuration #1 chosen from 1 choice
May 26 19:02:29 tarm kernel: [    6.613287] hub 5-0:1.0: USB hub found
May 26 19:02:29 tarm kernel: [    6.613292] hub 5-0:1.0: 2 ports detected
May 26 19:02:29 tarm kernel: [    6.641371] sdhci: Secure Digital Host Controller Interface driver
May 26 19:02:29 tarm kernel: [    6.641375] sdhci: Copyright(c) Pierre Ossman
May 26 19:02:29 tarm kernel: [    6.686967] input: PC Speaker as /class/input/input7
May 26 19:02:29 tarm kernel: [    6.717153] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
May 26 19:02:29 tarm kernel: [    6.717156] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 19:02:29 tarm kernel: [    6.717159] usb usb5: Product: UHCI Host Controller
May 26 19:02:29 tarm kernel: [    6.717161] usb usb5: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 19:02:29 tarm kernel: [    6.717163] usb usb5: SerialNumber: 0000:00:1d.3
May 26 19:02:29 tarm kernel: [    6.717637] Yenta: CardBus bridge found at 0000:14:00.0 [1014:056c]
May 26 19:02:29 tarm kernel: [    6.727391] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 19:02:29 tarm kernel: [    6.727398] hda_intel: probe_mask set to 0x1 for device 1014:05b7
May 26 19:02:29 tarm kernel: [    6.727416] PCI: Setting latency timer of device 0000:00:1b.0 to 64
May 26 19:02:29 tarm kernel: [    6.828993] hub 2-0:1.0: unable to enumerate USB device on port 5
May 26 19:02:29 tarm kernel: [    6.843641] NET: Registered protocol family 23
May 26 19:02:29 tarm kernel: [    6.845789] Yenta: ISA IRQ mask 0x0cb8, PCI irq 16
May 26 19:02:29 tarm kernel: [    6.845794] Socket status: 30000006
May 26 19:02:29 tarm kernel: [    6.845797] pcmcia: parent PCI bridge I/O window: 0x9000 - 0xcfff
May 26 19:02:29 tarm kernel: [    6.845801] pcmcia: parent PCI bridge Memory window: 0xb8000000 - 0xc00fffff
May 26 19:02:29 tarm kernel: [    6.845803] pcmcia: parent PCI bridge Memory window: 0xd8000000 - 0xdfffffff
May 26 19:02:29 tarm kernel: [    6.847886] ACPI: PCI Interrupt 0000:14:00.1[B] -> GSI 17 (level, low) -> IRQ 17
May 26 19:02:29 tarm kernel: [    6.903799] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17]  MMIO=[c0001000-c00017ff]  Max Packet=[2048]  IR/IT contexts=[4/4]
May 26 19:02:29 tarm kernel: [    6.912962] sdhci: SDHCI controller found at 0000:14:00.2 [1180:0822] (rev 17)
May 26 19:02:29 tarm kernel: [    6.912962] ACPI: PCI Interrupt 0000:14:00.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 19:02:29 tarm kernel: [    6.913507] mmc0: Will use DMA mode even though HW doesn't fully claim to support it.
May 26 19:02:29 tarm kernel: [    6.915539] mmc0: SDHCI at 0xc0001800 irq 18 DMA
May 26 19:02:29 tarm kernel: [    6.972114] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
May 26 19:02:29 tarm kernel: [    6.972118] ipw2200: Copyright(c) 2003-2006 Intel Corporation
May 26 19:02:29 tarm kernel: [    6.972191] ACPI: PCI Interrupt 0000:14:02.0[A] -> GSI 21 (level, low) -> IRQ 21
May 26 19:02:29 tarm kernel: [    6.972331] ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection
May 26 19:02:29 tarm kernel: [    6.972369] firmware: requesting ipw2200-bss.fw
May 26 19:02:29 tarm kernel: [    7.033926] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
May 26 19:02:29 tarm kernel: [    7.033950] rtc0: alarms up to one month, y3k
May 26 19:02:29 tarm kernel: [    7.068998] hub 2-0:1.0: unable to enumerate USB device on port 6
May 26 19:02:29 tarm kernel: [    7.156205] Marking TSC unstable due to: TSC halts in idle.
May 26 19:02:29 tarm kernel: [    7.300154] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x81a0b1, caps: 0xa04793/0x300000
May 26 19:02:29 tarm kernel: [    7.300154] serio: Synaptics pass-through port at isa0060/serio1/input0
May 26 19:02:29 tarm kernel: [    7.308981] usb 3-1: new low speed USB device using uhci_hcd and address 2
May 26 19:02:29 tarm kernel: [    7.349544] input: SynPS/2 Synaptics TouchPad as /class/input/input8
May 26 19:02:29 tarm kernel: [    7.375433] nsc-ircc 00:09: activated
May 26 19:02:29 tarm kernel: [    7.375433] nsc-ircc, chip->init
May 26 19:02:29 tarm kernel: [    7.375433] nsc-ircc, Found chip at base=0x164e
May 26 19:02:29 tarm kernel: [    7.375433] nsc-ircc, driver loaded (Dag Brattli)
May 26 19:02:29 tarm kernel: [    7.482233] usb 3-1: configuration #1 chosen from 1 choice
May 26 19:02:29 tarm kernel: [    7.485325] usb 3-1: New USB device found, idVendor=046d, idProduct=c404
May 26 19:02:29 tarm kernel: [    7.485328] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 19:02:29 tarm kernel: [    7.485331] usb 3-1: Product: Trackball
May 26 19:02:29 tarm kernel: [    7.485333] usb 3-1: Manufacturer: Logitech
May 26 19:02:29 tarm kernel: [    7.729656] usb 4-1: new full speed USB device using uhci_hcd and address 2
May 26 19:02:29 tarm kernel: [    7.807997] IrDA: Registered device irda0
May 26 19:02:29 tarm kernel: [    7.808001] nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500
May 26 19:02:29 tarm kernel: [    7.808876] ipw2200: Detected geography ZZE (13 802.11bg channels, 19 802.11a channels)
May 26 19:02:29 tarm kernel: [    7.808903] ACPI: PCI Interrupt 0000:00:1f.3[A] -> GSI 23 (level, low) -> IRQ 23
May 26 19:02:29 tarm kernel: [    7.904151] usb 4-1: configuration #1 chosen from 1 choice
May 26 19:02:29 tarm kernel: [    7.906821] usb 4-1: New USB device found, idVendor=0a5c, idProduct=2110
May 26 19:02:29 tarm kernel: [    7.906825] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 19:02:29 tarm kernel: [    7.906828] usb 4-1: Product: BCM2045B
May 26 19:02:29 tarm kernel: [    7.906830] usb 4-1: Manufacturer: Broadcom Corp
May 26 19:02:29 tarm kernel: [    8.004787] Bluetooth: Core ver 2.11
May 26 19:02:29 tarm kernel: [    8.005609] NET: Registered protocol family 31
May 26 19:02:29 tarm kernel: [    8.005612] Bluetooth: HCI device and connection manager initialized
May 26 19:02:29 tarm kernel: [    8.005615] Bluetooth: HCI socket layer initialized
May 26 19:02:29 tarm kernel: [    8.134262] Bluetooth: HCI USB driver ver 2.9
May 26 19:02:29 tarm kernel: [    8.147365] usb 4-2: new full speed USB device using uhci_hcd and address 3
May 26 19:02:29 tarm kernel: [    8.181089] ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00061b002020c273]
May 26 19:02:29 tarm kernel: [    8.319993] usb 4-2: configuration #1 chosen from 1 choice
May 26 19:02:29 tarm kernel: [    8.326293] usb 4-2: New USB device found, idVendor=0483, idProduct=2016
May 26 19:02:29 tarm kernel: [    8.326296] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 19:02:29 tarm kernel: [    8.326299] usb 4-2: Product: Biometric Coprocessor
May 26 19:02:29 tarm kernel: [    8.326301] usb 4-2: Manufacturer: STMicroelectronics
May 26 19:02:29 tarm kernel: [    8.326339] usbcore: registered new interface driver hiddev
May 26 19:02:29 tarm kernel: [    8.328311] usbcore: registered new interface driver hci_usb
May 26 19:02:29 tarm kernel: [    8.346436] input: Logitech Trackball as /class/input/input9
May 26 19:02:29 tarm kernel: [    8.373046] input,hidraw0: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:1d.1-1
May 26 19:02:29 tarm kernel: [    8.373071] usbcore: registered new interface driver usbhid
May 26 19:02:29 tarm kernel: [    8.373074] usbhid: v2.6:USB HID core driver
May 26 19:02:29 tarm kernel: [    8.951994] Bluetooth: L2CAP ver 2.9
May 26 19:02:29 tarm kernel: [    8.951994] Bluetooth: L2CAP socket layer initialized
May 26 19:02:29 tarm kernel: [    8.985031] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
May 26 19:02:29 tarm kernel: [    9.063318] Bluetooth: RFCOMM socket layer initialized
May 26 19:02:29 tarm kernel: [    9.063327] Bluetooth: RFCOMM TTY layer initialized
May 26 19:02:29 tarm kernel: [    9.063329] Bluetooth: RFCOMM ver 1.8
May 26 19:02:29 tarm kernel: [   13.393047] IBM TrackPoint firmware: 0x0e, buttons: 3/3
May 26 19:02:29 tarm kernel: [   13.652587] input: TPPS/2 IBM TrackPoint as /class/input/input10
May 26 19:02:29 tarm kernel: [   39.175406] tun: Universal TUN/TAP device driver, 1.6
May 26 19:02:29 tarm kernel: [   39.175406] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
May 26 19:02:29 tarm kernel: [   39.338274] hdaps: IBM ThinkPad Z60m detected.
May 26 19:02:29 tarm kernel: [   39.338274] hdaps: initial latch check good (0x01).
May 26 19:02:29 tarm kernel: [   39.541424] hdaps: device successfully initialized.
May 26 19:02:29 tarm kernel: [   39.541912] input: hdaps as /class/input/input11
May 26 19:02:29 tarm kernel: [   39.569007] hdaps: driver successfully loaded.
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq: acpi_cpufreq_init
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq: acpi_cpufreq_early_init
May 26 19:02:29 tarm kernel: [   39.682552] cpufreq-core: trying to register driver acpi-cpufreq
May 26 19:02:29 tarm kernel: [   39.682552] cpufreq-core: adding CPU 0
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq: acpi_cpufreq_cpu_init
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq: HARDWARE addr space
May 26 19:02:29 tarm kernel: [   39.682552] freq-table: table entry 0: 2000000 kHz, 0 index
May 26 19:02:29 tarm kernel: [   39.682552] freq-table: table entry 1: 1600000 kHz, 1 index
May 26 19:02:29 tarm kernel: [   39.682552] freq-table: table entry 2: 1333000 kHz, 2 index
May 26 19:02:29 tarm kernel: [   39.682552] freq-table: table entry 3: 1066000 kHz, 3 index
May 26 19:02:29 tarm kernel: [   39.682552] freq-table: table entry 4: 800000 kHz, 4 index
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq: get_cur_freq_on_cpu (0)
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq: get_cur_val = 100667177
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq: cur freq = 2000000
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq: CPU0 - ACPI performance management activated.
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq:      *P0: 2000 MHz, 27000 mW, 500 uS
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq:       P1: 1600 MHz, 22600 mW, 500 uS
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq:       P2: 1333 MHz, 19666 mW, 500 uS
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq:       P3: 1066 MHz, 16733 mW, 500 uS
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq:       P4: 800 MHz, 13800 mW, 500 uS
May 26 19:02:29 tarm kernel: [   39.682552] freq-table: setting show_table for cpu 0 to f7bb1440
May 26 19:02:29 tarm kernel: [   39.682552] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq: acpi_cpufreq_verify
May 26 19:02:29 tarm kernel: [   39.682552] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 19:02:29 tarm kernel: [   39.682552] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 19:02:29 tarm kernel: [   39.682552] acpi-cpufreq: acpi_cpufreq_verify
May 26 19:02:29 tarm kernel: [   39.682552] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 19:02:29 tarm kernel: [   39.682552] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 19:02:29 tarm kernel: [   39.682552] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 19:02:29 tarm kernel: [   39.682552] cpufreq-core: governor switch
May 26 19:02:29 tarm kernel: [   39.682552] cpufreq-core: __cpufreq_governor for CPU 0, event 1
May 26 19:02:29 tarm kernel: [   39.682552] cpufreq-core: governor: change or update limits
May 26 19:02:29 tarm kernel: [   39.682552] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 19:02:29 tarm kernel: [   39.682552] cpufreq-core: initialization complete
May 26 19:02:29 tarm kernel: [   39.682552] cpufreq-core: driver acpi-cpufreq up and running
May 26 19:02:29 tarm kernel: [   39.722541] cpufreq-core: updating policy for CPU 0
May 26 19:02:29 tarm kernel: [   39.722541] acpi-cpufreq: get_cur_freq_on_cpu (0)
May 26 19:02:29 tarm kernel: [   39.722541] acpi-cpufreq: get_cur_val = 100667177
May 26 19:02:29 tarm kernel: [   39.722541] acpi-cpufreq: cur freq = 2000000
May 26 19:02:29 tarm kernel: [   39.722541] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 19:02:29 tarm kernel: [   39.722541] acpi-cpufreq: acpi_cpufreq_verify
May 26 19:02:29 tarm kernel: [   39.722541] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 19:02:29 tarm kernel: [   39.722541] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 19:02:29 tarm kernel: [   39.722541] acpi-cpufreq: acpi_cpufreq_verify
May 26 19:02:29 tarm kernel: [   39.722541] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 19:02:29 tarm kernel: [   39.722541] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 19:02:29 tarm kernel: [   39.722541] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 19:02:29 tarm kernel: [   39.722541] cpufreq-core: governor: change or update limits
May 26 19:02:29 tarm kernel: [   39.722541] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 19:02:29 tarm kernel: [   39.794929] IrCOMM protocol (Dag Brattli)
May 26 19:02:29 tarm kernel: [   39.961001] cpufreq-core: target for CPU 0: 857142 kHz, relation 0
May 26 19:02:29 tarm kernel: [   39.961005] acpi-cpufreq: acpi_cpufreq_target 857142 (0)
May 26 19:02:29 tarm kernel: [   39.961008] freq-table: request for target 857142 kHz (relation: 0) for cpu 0
May 26 19:02:29 tarm kernel: [   39.961011] freq-table: target is 3 (1066000 kHz, 3)
May 26 19:02:29 tarm kernel: [   39.961014] cpufreq-core: notification 0 of frequency transition to 1066000 kHz
May 26 19:02:29 tarm kernel: [   40.090458] fuse init (API version 7.9)
May 26 19:02:29 tarm kernel: [   40.340980] Clocksource tsc unstable (delta = -177391143 ns)
May 26 19:02:29 tarm kernel: [   50.829229] ieee80211_crypt: registered algorithm 'CCMP'
May 26 19:02:29 tarm kernel: [   50.980350] padlock: VIA PadLock not detected.
May 26 19:02:29 tarm kernel: [   51.063393] ieee80211_crypt: registered algorithm 'TKIP'
May 26 19:02:29 tarm kernel: [   56.612204] warning: `named' uses 32-bit capabilities (legacy support in use)
May 26 19:02:29 tarm kernel: [   56.811286] NET: Registered protocol family 10
May 26 19:02:29 tarm kernel: [   56.812249] lo: Disabled Privacy Extensions
May 26 19:02:29 tarm kernel: [   56.813322] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 26 19:02:29 tarm kernel: [   57.135357] tun0: Disabled Privacy Extensions
May 26 19:02:29 tarm kernel: [   58.209229] Bluetooth: BNEP (Ethernet Emulation) ver 1.2
May 26 19:02:29 tarm kernel: [   58.209236] Bluetooth: BNEP filters: protocol multicast
May 26 19:02:29 tarm kernel: [   58.293509] Bridge firewalling registered
May 26 19:02:29 tarm kernel: [   58.293678] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 19:02:29 tarm kernel: [   58.295410] pan1: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 19:02:32 tarm kernel: [   61.577355] NET: Registered protocol family 15
May 26 19:02:32 tarm kernel: [   61.906798] padlock: VIA PadLock Hash Engine not detected.
May 26 19:02:33 tarm kernel: [   62.940989] __ratelimit: 10 messages suppressed
May 26 19:02:33 tarm kernel: [   62.941202] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 19:02:33 tarm kernel: [   62.941368] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 19:02:33 tarm kernel: [   62.941503] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 19:02:33 tarm kernel: [   62.941642] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:02:37 tarm kernel: [   67.236982] eth1: no IPv6 routers present
May 26 17:02:47 tarm kernel: [   77.110282] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:02:47 tarm kernel: [   77.110296] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:02:47 tarm kernel: [   77.110303] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:02:47 tarm kernel: [   77.110312] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:02:47 tarm kernel: [   77.110321] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:02:47 tarm kernel: [   77.110328] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:02:47 tarm kernel: [   77.110337] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:02:47 tarm kernel: [   77.110345] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 17:02:47 tarm kernel: [   77.110351] cpufreq-core: governor: change or update limits
May 26 17:02:47 tarm kernel: [   77.110358] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:02:49 tarm kernel: [   79.270059] [drm] Initialized drm 1.1.0 20060810
May 26 17:02:50 tarm kernel: [   79.290995] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:02:50 tarm kernel: [   79.292438] PCI: Setting latency timer of device 0000:01:00.0 to 64
May 26 17:02:50 tarm kernel: [   79.292722] [drm] Initialized radeon 1.28.0 20060524 on minor 0
May 26 17:02:50 tarm kernel: [   79.440996] __ratelimit: 17 messages suppressed
May 26 17:02:50 tarm kernel: [   79.441203] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:02:50 tarm kernel: [   79.441372] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:02:50 tarm kernel: [   79.441510] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:02:50 tarm kernel: [   79.940982] __ratelimit: 4 messages suppressed
May 26 17:02:50 tarm kernel: [   79.941048] cpufreq-core: target for CPU 0: 114285 kHz, relation 0
May 26 17:02:53 tarm kernel: [   82.345837] [drm] Setting GART location based on new memory map
May 26 17:02:53 tarm kernel: [   82.346717] [drm] Loading R300 Microcode
May 26 17:02:53 tarm kernel: [   82.346768] [drm] writeback test succeeded in 1 usecs
May 26 17:02:59 tarm kernel: [   88.441019] __ratelimit: 6 messages suppressed
May 26 17:02:59 tarm kernel: [   88.441285] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:03:09 tarm kernel: [   98.441553] __ratelimit: 20 messages suppressed
May 26 17:03:09 tarm kernel: [   98.441782] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:03:09 tarm kernel: [   98.441929] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:03:15 tarm kernel: [  104.940997] __ratelimit: 12 messages suppressed
May 26 17:03:15 tarm kernel: [  104.941215] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:03:15 tarm kernel: [  104.941385] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:03:20 tarm kernel: [  109.940992] __ratelimit: 33 messages suppressed
May 26 17:03:20 tarm kernel: [  109.941174] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:03:25 tarm kernel: [  114.940988] __ratelimit: 41 messages suppressed
May 26 17:03:25 tarm kernel: [  114.941124] cpufreq-core: target for CPU 0: 857142 kHz, relation 0
May 26 17:03:30 tarm kernel: [  119.941018] __ratelimit: 58 messages suppressed
May 26 17:03:30 tarm kernel: [  119.941213] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:03:35 tarm kernel: [  124.941049] __ratelimit: 39 messages suppressed
May 26 17:03:35 tarm kernel: [  124.941263] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:04:05 tarm kernel: [  154.941067] __ratelimit: 20 messages suppressed
May 26 17:04:05 tarm kernel: [  154.941286] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:04:05 tarm kernel: [  154.941433] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:04:05 tarm kernel: [  154.941573] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:04:05 tarm kernel: [  154.941718] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:04:05 tarm kernel: [  154.941854] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:04:05 tarm kernel: [  154.941997] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:04:13 tarm kernel: [  162.941008] __ratelimit: 8 messages suppressed
May 26 17:04:13 tarm kernel: [  162.941232] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:04:20 tarm kernel: [  169.441016] __ratelimit: 20 messages suppressed
May 26 17:04:20 tarm kernel: [  169.441253] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:04:21 tarm kernel: [  170.440990] __ratelimit: 6 messages suppressed
May 26 17:04:21 tarm kernel: [  170.441136] cpufreq-core: target for CPU 0: 800000 kHz, relation 0
May 26 17:04:26 tarm kernel: [  175.442070] __ratelimit: 20 messages suppressed
May 26 17:04:26 tarm kernel: [  175.442307] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:04:30 tarm kernel: [  179.941024] __ratelimit: 32 messages suppressed
May 26 17:04:30 tarm kernel: [  179.941267] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:04:36 tarm kernel: [  185.440989] __ratelimit: 20 messages suppressed
May 26 17:04:36 tarm kernel: [  185.441143] cpufreq-core: target for CPU 0: 1371428 kHz, relation 0
May 26 17:04:41 tarm kernel: [  190.441011] __ratelimit: 39 messages suppressed
May 26 17:04:41 tarm kernel: [  190.441250] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:04:48 tarm kernel: [  197.441033] __ratelimit: 34 messages suppressed
May 26 17:04:48 tarm kernel: [  197.441267] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:04:50 tarm kernel: [  199.940991] __ratelimit: 30 messages suppressed
May 26 17:04:50 tarm kernel: [  199.941150] cpufreq-core: target for CPU 0: 800000 kHz, relation 0
May 26 17:04:57 tarm kernel: [  206.940999] __ratelimit: 32 messages suppressed
May 26 17:04:57 tarm kernel: [  206.941225] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:05:11 tarm kernel: [  220.941020] __ratelimit: 13 messages suppressed
May 26 17:05:11 tarm kernel: [  220.941288] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:05:11 tarm kernel: [  220.941440] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:05:11 tarm kernel: [  220.941581] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:05:17 tarm kernel: [  227.139266] ehci_hcd 0000:00:1d.7: remove, state 4
May 26 17:05:17 tarm kernel: [  227.139483] usb usb2: USB disconnect, address 1
May 26 17:05:17 tarm kernel: [  227.143880] ehci_hcd 0000:00:1d.7: USB bus 2 deregistered
May 26 17:05:17 tarm kernel: [  227.148968] ACPI: PCI interrupt for device 0000:00:1d.7 disabled
May 26 17:05:17 tarm kernel: [  227.148968] uhci_hcd 0000:00:1d.3: remove, state 4
May 26 17:05:17 tarm kernel: [  227.148968] usb usb5: USB disconnect, address 1
May 26 17:05:17 tarm kernel: [  227.149375] uhci_hcd 0000:00:1d.3: USB bus 5 deregistered
May 26 17:05:17 tarm kernel: [  227.149431] ACPI: PCI interrupt for device 0000:00:1d.3 disabled
May 26 17:05:17 tarm kernel: [  227.149448] uhci_hcd 0000:00:1d.2: remove, state 1
May 26 17:05:17 tarm kernel: [  227.149459] usb usb4: USB disconnect, address 1
May 26 17:05:17 tarm kernel: [  227.149464] usb 4-1: USB disconnect, address 2
May 26 17:05:18 tarm kernel: [  227.407102] usb 4-2: USB disconnect, address 3
May 26 17:05:18 tarm kernel: [  227.411886] uhci_hcd 0000:00:1d.2: USB bus 4 deregistered
May 26 17:05:18 tarm kernel: [  227.411955] ACPI: PCI interrupt for device 0000:00:1d.2 disabled
May 26 17:05:18 tarm kernel: [  227.411974] uhci_hcd 0000:00:1d.1: remove, state 1
May 26 17:05:18 tarm kernel: [  227.411986] usb usb3: USB disconnect, address 1
May 26 17:05:18 tarm kernel: [  227.411991] usb 3-1: USB disconnect, address 2
May 26 17:05:18 tarm kernel: [  227.437810] uhci_hcd 0000:00:1d.1: USB bus 3 deregistered
May 26 17:05:18 tarm kernel: [  227.438150] ACPI: PCI interrupt for device 0000:00:1d.1 disabled
May 26 17:05:18 tarm kernel: [  227.438174] uhci_hcd 0000:00:1d.0: remove, state 4
May 26 17:05:18 tarm kernel: [  227.438186] usb usb1: USB disconnect, address 1
May 26 17:05:18 tarm kernel: [  227.438537] uhci_hcd 0000:00:1d.0: USB bus 1 deregistered
May 26 17:05:18 tarm kernel: [  227.438593] ACPI: PCI interrupt for device 0000:00:1d.0 disabled
May 26 17:05:19 tarm kernel: [  228.941023] __ratelimit: 32 messages suppressed
May 26 17:05:19 tarm kernel: [  228.941063] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:05:20 tarm kernel: [  229.941023] __ratelimit: 13 messages suppressed
May 26 17:05:20 tarm kernel: [  229.941251] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:05:22 tarm kernel: [  231.076114] PM: Syncing filesystems ... done.
May 26 17:05:36 tarm kernel: [  231.371787] Freezing user space processes ... (elapsed 0.00 seconds) done.
May 26 17:05:36 tarm kernel: [  231.380672] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
May 26 17:05:36 tarm kernel: [  231.380822] Suspending console(s)
May 26 17:05:36 tarm kernel: [  231.588170] sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 26 17:05:36 tarm kernel: [  231.597293] sd 0:0:0:0: [sda] Stopping disk
May 26 17:05:36 tarm kernel: [  233.021763] nsc-ircc 00:09: disabled
May 26 17:05:36 tarm kernel: [  233.021953] eth1: Going into suspend...
May 26 17:05:36 tarm kernel: [  233.025023] ACPI: PCI interrupt for device 0000:14:02.0 disabled
May 26 17:05:36 tarm kernel: [  233.025034] ACPI handle has no context!
May 26 17:05:36 tarm kernel: [  233.042094] ACPI handle has no context!
May 26 17:05:36 tarm kernel: [  233.042124] ACPI: PCI interrupt for device 0000:14:00.2 disabled
May 26 17:05:36 tarm kernel: [  233.042134] ACPI handle has no context!
May 26 17:05:36 tarm kernel: [  233.062075] ACPI handle has no context!
May 26 17:05:36 tarm kernel: [  233.218607] ACPI handle has no context!
May 26 17:05:36 tarm kernel: [  233.437051] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
May 26 17:05:36 tarm kernel: [  233.456153] ACPI: Preparing to enter system sleep state S3
May 26 17:05:36 tarm kernel: [  233.469518] Extended CMOS year: 2000
May 26 17:05:36 tarm kernel: [  233.469518] Intel machine check architecture supported.
May 26 17:05:36 tarm kernel: [  233.469534] Intel machine check reporting enabled on CPU#0.
May 26 17:05:36 tarm kernel: [  233.469634] Back to C!
May 26 17:05:36 tarm kernel: [  233.469930] Extended CMOS year: 2000
May 26 17:05:36 tarm kernel: [  233.469935] Force enabled HPET at resume
May 26 17:05:36 tarm kernel: [  233.470111] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:05:36 tarm kernel: [  233.470113] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:05:36 tarm kernel: [  233.470116] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:05:36 tarm kernel: [  233.470119] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:05:36 tarm kernel: [  233.470123] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:05:36 tarm kernel: [  233.470125] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:05:36 tarm kernel: [  233.470128] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:05:36 tarm kernel: [  233.470131] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 17:05:36 tarm kernel: [  233.470133] cpufreq-core: governor: change or update limits
May 26 17:05:36 tarm kernel: [  233.470136] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:05:36 tarm kernel: [  233.534939] PM: Writing back config space on device 0000:00:01.0 at offset 7 (was 20002020, writing 2020)
May 26 17:05:36 tarm kernel: [  233.534945] PM: Writing back config space on device 0000:00:01.0 at offset 1 (was 100107, writing 100507)
May 26 17:05:36 tarm kernel: [  233.534962] PCI: Setting latency timer of device 0000:00:01.0 to 64
May 26 17:05:36 tarm kernel: [  233.549015] PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100002)
May 26 17:05:36 tarm kernel: [  233.549038] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:05:36 tarm kernel: [  233.549045] PCI: Setting latency timer of device 0000:00:1b.0 to 64
May 26 17:05:36 tarm kernel: [  233.605163] PM: Writing back config space on device 0000:00:1c.0 at offset 7 (was f0, writing 200000f0)
May 26 17:05:36 tarm kernel: [  233.605184] PM: Writing back config space on device 0000:00:1c.0 at offset 1 (was 100107, writing 100507)
May 26 17:05:36 tarm kernel: [  233.605249] PCI: Setting latency timer of device 0000:00:1c.0 to 64
May 26 17:05:36 tarm kernel: [  233.605310] PM: Writing back config space on device 0000:00:1c.1 at offset 1 (was 100107, writing 100507)
May 26 17:05:36 tarm kernel: [  233.605373] PCI: Setting latency timer of device 0000:00:1c.1 to 64
May 26 17:05:36 tarm kernel: [  233.605433] PM: Writing back config space on device 0000:00:1c.2 at offset 1 (was 100107, writing 100507)
May 26 17:05:36 tarm kernel: [  233.605496] PCI: Setting latency timer of device 0000:00:1c.2 to 64
May 26 17:05:36 tarm kernel: [  233.605557] PM: Writing back config space on device 0000:00:1c.3 at offset 1 (was 100107, writing 100507)
May 26 17:05:36 tarm kernel: [  233.605620] PCI: Setting latency timer of device 0000:00:1c.3 to 64
May 26 17:05:36 tarm kernel: [  233.605627] PM: Writing back config space on device 0000:00:1d.0 at offset f (was 100, writing 10b)
May 26 17:05:36 tarm kernel: [  233.605681] PM: Writing back config space on device 0000:00:1d.1 at offset f (was 200, writing 20b)
May 26 17:05:36 tarm kernel: [  233.605728] PM: Writing back config space on device 0000:00:1d.2 at offset f (was 300, writing 30b)
May 26 17:05:36 tarm kernel: [  233.605773] PM: Writing back config space on device 0000:00:1d.3 at offset f (was 400, writing 40b)
May 26 17:05:36 tarm kernel: [  233.605834] PM: Writing back config space on device 0000:00:1d.7 at offset f (was 400, writing 40b)
May 26 17:05:36 tarm kernel: [  233.605871] PM: Writing back config space on device 0000:00:1d.7 at offset 4 (was 0, writing b0004000)
May 26 17:05:36 tarm kernel: [  233.605879] PM: Writing back config space on device 0000:00:1d.7 at offset 1 (was 2900000, writing 2900102)
May 26 17:05:36 tarm kernel: [  233.605978] PCI: Setting latency timer of device 0000:00:1e.0 to 64
May 26 17:05:36 tarm kernel: [  233.621044] PM: Writing back config space on device 0000:00:1f.2 at offset 1 (was 2b00005, writing 2b80005)
May 26 17:05:36 tarm kernel: [  233.621063] PCI: Setting latency timer of device 0000:00:1f.2 to 64
May 26 17:05:36 tarm kernel: [  233.623314] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:05:36 tarm kernel: [  233.623320] PCI: Setting latency timer of device 0000:01:00.0 to 64
May 26 17:05:36 tarm kernel: [  233.623357] PM: Writing back config space on device 0000:02:00.0 at offset c (was 0, writing f4f70000)
May 26 17:05:36 tarm kernel: [  233.623383] PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 100106)
May 26 17:05:36 tarm kernel: [  233.961256] PM: Writing back config space on device 0000:14:00.1 at offset 4 (was 0, writing c0001000)
May 26 17:05:36 tarm kernel: [  233.961263] PM: Writing back config space on device 0000:14:00.1 at offset 3 (was 800000, writing 804000)
May 26 17:05:36 tarm kernel: [  233.961271] PM: Writing back config space on device 0000:14:00.1 at offset 1 (was 2100000, writing 2100106)
May 26 17:05:36 tarm kernel: [  233.973825] ata2.00: ACPI cmd ef/03:42:00:00:00:a0 filtered out
May 26 17:05:36 tarm kernel: [  233.973827] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
May 26 17:05:36 tarm kernel: [  233.981830] ata2.00: ACPI cmd e3/00:10:00:00:00:a0 succeeded
May 26 17:05:36 tarm kernel: [  233.989833] ata2.00: ACPI cmd e3/00:03:00:00:00:a0 succeeded
May 26 17:05:36 tarm kernel: [  234.014161] ata2.00: configured for UDMA/33
May 26 17:05:36 tarm kernel: [  234.016178] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17]  MMIO=[c0001000-c00017ff]  Max Packet=[2048]  IR/IT contexts=[4/4]
May 26 17:05:36 tarm kernel: [  234.041185] PM: Writing back config space on device 0000:14:00.2 at offset 4 (was 0, writing c0001800)
May 26 17:05:36 tarm kernel: [  234.041190] PM: Writing back config space on device 0000:14:00.2 at offset 3 (was 800000, writing 804000)
May 26 17:05:36 tarm kernel: [  234.041197] PM: Writing back config space on device 0000:14:00.2 at offset 1 (was 2100000, writing 2100106)
May 26 17:05:36 tarm kernel: [  234.041217] ACPI: PCI Interrupt 0000:14:00.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 17:05:36 tarm kernel: [  234.042261] eth1: Coming out of suspend...
May 26 17:05:36 tarm kernel: [  234.064110] ACPI: PCI Interrupt 0000:14:02.0[A] -> GSI 21 (level, low) -> IRQ 21
May 26 17:05:36 tarm kernel: [  234.064849] nsc-ircc 00:09: activated
May 26 17:05:36 tarm kernel: [  234.941019] __ratelimit: 37 messages suppressed
May 26 17:05:36 tarm kernel: [  234.941022] cpufreq-core: target for CPU 0: 800000 kHz, relation 0
May 26 17:05:36 tarm kernel: [  235.000506] sd 0:0:0:0: [sda] Starting disk
May 26 17:05:36 tarm kernel: [  235.401717] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 succeeded
May 26 17:05:36 tarm kernel: [  235.401725] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
May 26 17:05:36 tarm kernel: [  235.401731] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 filtered out
May 26 17:05:36 tarm kernel: [  235.401738] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
May 26 17:05:36 tarm kernel: [  235.402138] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 succeeded
May 26 17:05:36 tarm kernel: [  235.425653] ata1.00: configured for UDMA/100
May 26 17:05:36 tarm kernel: [  235.449674] ata1.00: configured for UDMA/100
May 26 17:05:36 tarm kernel: [  235.449681] ata1: EH complete
May 26 17:05:36 tarm kernel: [  235.449773] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
May 26 17:05:36 tarm kernel: [  235.449816] sd 0:0:0:0: [sda] Write Protect is off
May 26 17:05:36 tarm kernel: [  235.449822] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 26 17:05:36 tarm kernel: [  235.449895] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 26 17:05:36 tarm kernel: [  235.449967] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
May 26 17:05:36 tarm kernel: [  235.450006] sd 0:0:0:0: [sda] Write Protect is off
May 26 17:05:36 tarm kernel: [  235.450012] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 26 17:05:36 tarm kernel: [  235.450083] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 26 17:05:36 tarm kernel: [  238.171920] hdaps: initial latch check good (0x01).
May 26 17:05:36 tarm kernel: [  238.377549] Restarting tasks ... done.
May 26 17:05:36 tarm kernel: [  238.545699] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 19
May 26 17:05:36 tarm kernel: [  238.545980] PCI: Setting latency timer of device 0000:00:1d.7 to 64
May 26 17:05:36 tarm kernel: [  238.546130] ehci_hcd 0000:00:1d.7: EHCI Host Controller
May 26 17:05:36 tarm kernel: [  238.607604] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
May 26 17:05:36 tarm kernel: [  238.614007] ehci_hcd 0000:00:1d.7: debug port 1
May 26 17:05:36 tarm kernel: [  238.614139] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
May 26 17:05:36 tarm kernel: [  238.614296] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xb0004000
May 26 17:05:36 tarm kernel: [  238.630093] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
May 26 17:05:36 tarm kernel: [  238.630554] usb usb1: configuration #1 chosen from 1 choice
May 26 17:05:36 tarm kernel: [  238.630625] hub 1-0:1.0: USB hub found
May 26 17:05:36 tarm kernel: [  238.630641] hub 1-0:1.0: 8 ports detected
May 26 17:05:36 tarm kernel: [  238.733155] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
May 26 17:05:36 tarm kernel: [  238.733167] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:05:36 tarm kernel: [  238.733174] usb usb1: Product: EHCI Host Controller
May 26 17:05:36 tarm kernel: [  238.733180] usb usb1: Manufacturer: Linux 2.6.26-rc3 ehci_hcd
May 26 17:05:36 tarm kernel: [  238.733185] usb usb1: SerialNumber: 0000:00:1d.7
May 26 17:05:36 tarm kernel: [  238.754490] USB Universal Host Controller Interface driver v3.0
May 26 17:05:36 tarm kernel: [  238.754576] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:05:36 tarm kernel: [  238.754597] PCI: Setting latency timer of device 0000:00:1d.0 to 64
May 26 17:05:36 tarm kernel: [  238.754605] uhci_hcd 0000:00:1d.0: UHCI Host Controller
May 26 17:05:36 tarm kernel: [  238.754668] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
May 26 17:05:36 tarm kernel: [  238.754706] uhci_hcd 0000:00:1d.0: irq 16, io base 0x00001800
May 26 17:05:36 tarm kernel: [  238.754943] usb usb2: configuration #1 chosen from 1 choice
May 26 17:05:36 tarm kernel: [  238.755010] hub 2-0:1.0: USB hub found
May 26 17:05:36 tarm kernel: [  238.755025] hub 2-0:1.0: 2 ports detected
May 26 17:05:36 tarm kernel: [  238.857152] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:05:36 tarm kernel: [  238.857394] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:05:36 tarm kernel: [  238.857526] usb usb2: Product: UHCI Host Controller
May 26 17:05:36 tarm kernel: [  238.857646] usb usb2: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:05:36 tarm kernel: [  238.857766] usb usb2: SerialNumber: 0000:00:1d.0
May 26 17:05:36 tarm kernel: [  238.857922] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 17
May 26 17:05:36 tarm kernel: [  238.858108] PCI: Setting latency timer of device 0000:00:1d.1 to 64
May 26 17:05:36 tarm kernel: [  238.858254] uhci_hcd 0000:00:1d.1: UHCI Host Controller
May 26 17:05:36 tarm kernel: [  238.858424] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
May 26 17:05:36 tarm kernel: [  238.858584] uhci_hcd 0000:00:1d.1: irq 17, io base 0x00001820
May 26 17:05:36 tarm kernel: [  238.858923] usb usb3: configuration #1 chosen from 1 choice
May 26 17:05:36 tarm kernel: [  238.859114] hub 3-0:1.0: USB hub found
May 26 17:05:36 tarm kernel: [  238.859244] hub 3-0:1.0: 2 ports detected
May 26 17:05:36 tarm kernel: [  238.951941] hub 1-0:1.0: unable to enumerate USB device on port 3
May 26 17:05:36 tarm kernel: [  238.961069] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:05:36 tarm kernel: [  238.961075] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:05:36 tarm kernel: [  238.961078] usb usb3: Product: UHCI Host Controller
May 26 17:05:36 tarm kernel: [  238.961080] usb usb3: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:05:36 tarm kernel: [  238.961083] usb usb3: SerialNumber: 0000:00:1d.1
May 26 17:05:36 tarm kernel: [  238.961115] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 17:05:36 tarm kernel: [  238.961126] PCI: Setting latency timer of device 0000:00:1d.2 to 64
May 26 17:05:36 tarm kernel: [  238.961130] uhci_hcd 0000:00:1d.2: UHCI Host Controller
May 26 17:05:36 tarm kernel: [  238.961155] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
May 26 17:05:36 tarm kernel: [  238.961181] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001840
May 26 17:05:36 tarm kernel: [  238.961283] usb usb4: configuration #1 chosen from 1 choice
May 26 17:05:36 tarm kernel: [  238.961311] hub 4-0:1.0: USB hub found
May 26 17:05:36 tarm kernel: [  238.961317] hub 4-0:1.0: 2 ports detected
May 26 17:05:36 tarm kernel: [  239.065077] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:05:36 tarm kernel: [  239.065084] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:05:36 tarm kernel: [  239.065087] usb usb4: Product: UHCI Host Controller
May 26 17:05:36 tarm kernel: [  239.065089] usb usb4: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:05:36 tarm kernel: [  239.065091] usb usb4: SerialNumber: 0000:00:1d.2
May 26 17:05:36 tarm kernel: [  239.065124] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 19
May 26 17:05:36 tarm kernel: [  239.065137] PCI: Setting latency timer of device 0000:00:1d.3 to 64
May 26 17:05:36 tarm kernel: [  239.065141] uhci_hcd 0000:00:1d.3: UHCI Host Controller
May 26 17:05:36 tarm kernel: [  239.065165] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
May 26 17:05:36 tarm kernel: [  239.065192] uhci_hcd 0000:00:1d.3: irq 19, io base 0x00001860
May 26 17:05:36 tarm kernel: [  239.065300] usb usb5: configuration #1 chosen from 1 choice
May 26 17:05:36 tarm kernel: [  239.065328] hub 5-0:1.0: USB hub found
May 26 17:05:36 tarm kernel: [  239.065335] hub 5-0:1.0: 2 ports detected
May 26 17:05:36 tarm kernel: [  239.172508] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:05:36 tarm kernel: [  239.172653] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:05:36 tarm kernel: [  239.172711] usb usb5: Product: UHCI Host Controller
May 26 17:05:36 tarm kernel: [  239.172764] usb usb5: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:05:36 tarm kernel: [  239.172817] usb usb5: SerialNumber: 0000:00:1d.3
May 26 17:05:36 tarm kernel: [  239.189150] hub 1-0:1.0: unable to enumerate USB device on port 5
May 26 17:05:36 tarm kernel: [  239.223775] [drm] Loading R300 Microcode
May 26 17:05:37 tarm kernel: [  239.429247] hub 1-0:1.0: unable to enumerate USB device on port 6
May 26 17:05:37 tarm kernel: [  239.669302] usb 3-1: new low speed USB device using uhci_hcd and address 2
May 26 17:05:37 tarm kernel: [  239.849560] usb 3-1: configuration #1 chosen from 1 choice
May 26 17:05:37 tarm kernel: [  239.876525] input: Logitech Trackball as /class/input/input12
May 26 17:05:37 tarm kernel: [  239.903251] input,hidraw0: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:1d.1-1
May 26 17:05:37 tarm kernel: [  239.903507] usb 3-1: New USB device found, idVendor=046d, idProduct=c404
May 26 17:05:37 tarm kernel: [  239.903561] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:05:37 tarm kernel: [  239.903611] usb 3-1: Product: Trackball
May 26 17:05:37 tarm kernel: [  239.903657] usb 3-1: Manufacturer: Logitech
May 26 17:05:38 tarm kernel: [  240.140989] usb 4-1: new full speed USB device using uhci_hcd and address 2
May 26 17:05:38 tarm kernel: [  240.316315] usb 4-1: configuration #1 chosen from 1 choice
May 26 17:05:38 tarm kernel: [  240.326782] usb 4-1: New USB device found, idVendor=0a5c, idProduct=2110
May 26 17:05:38 tarm kernel: [  240.326943] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:05:38 tarm kernel: [  240.327302] usb 4-1: Product: BCM2045B
May 26 17:05:38 tarm kernel: [  240.327356] usb 4-1: Manufacturer: Broadcom Corp
May 26 17:05:38 tarm kernel: [  240.569038] usb 4-2: new full speed USB device using uhci_hcd and address 3
May 26 17:05:38 tarm kernel: [  240.584721] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 17:05:38 tarm kernel: [  240.592342] pan1: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 17:05:38 tarm kernel: [  240.738539] usb 4-2: configuration #1 chosen from 1 choice
May 26 17:05:38 tarm kernel: [  240.745401] usb 4-2: New USB device found, idVendor=0483, idProduct=2016
May 26 17:05:38 tarm kernel: [  240.745493] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:05:38 tarm kernel: [  240.745548] usb 4-2: Product: Biometric Coprocessor
May 26 17:05:38 tarm kernel: [  240.745598] usb 4-2: Manufacturer: STMicroelectronics
May 26 17:05:40 tarm kernel: [  241.940987] __ratelimit: 13 messages suppressed
May 26 17:05:40 tarm kernel: [  241.941181] cpufreq-core: target for CPU 0: 228571 kHz, relation 0
May 26 17:05:41 tarm kernel: [  243.097399] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 26 17:05:43 tarm kernel: [  244.941023] __ratelimit: 27 messages suppressed
May 26 17:05:43 tarm kernel: [  244.941244] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:05:46 tarm kernel: [  248.929927] ADDRCONF(NETDEV_UP): eth1: link is not ready
May 26 17:05:47 tarm kernel: [  249.562683] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
May 26 17:05:48 tarm kernel: [  249.940991] __ratelimit: 34 messages suppressed
May 26 17:05:48 tarm kernel: [  249.940997] cpufreq-core: target for CPU 0: 171428 kHz, relation 0
May 26 17:05:50 tarm kernel: [  251.961251] tun0: Disabled Privacy Extensions
May 26 17:05:58 tarm kernel: [  260.364983] eth1: no IPv6 routers present
May 26 17:06:09 tarm kernel: [  270.941020] __ratelimit: 34 messages suppressed
May 26 17:06:09 tarm kernel: [  270.941039] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:06:09 tarm kernel: [  270.941048] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:06:09 tarm kernel: [  270.941056] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:06:09 tarm kernel: [  270.941064] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:06:09 tarm kernel: [  271.365829] ehci_hcd 0000:00:1d.7: remove, state 4
May 26 17:06:09 tarm kernel: [  271.365843] usb usb1: USB disconnect, address 1
May 26 17:06:09 tarm kernel: [  271.384968] ehci_hcd 0000:00:1d.7: USB bus 1 deregistered
May 26 17:06:09 tarm kernel: [  271.384968] ACPI: PCI interrupt for device 0000:00:1d.7 disabled
May 26 17:06:09 tarm kernel: [  271.385508] uhci_hcd 0000:00:1d.3: remove, state 4
May 26 17:06:09 tarm kernel: [  271.385519] usb usb5: USB disconnect, address 1
May 26 17:06:09 tarm kernel: [  271.385711] uhci_hcd 0000:00:1d.3: USB bus 5 deregistered
May 26 17:06:09 tarm kernel: [  271.385739] ACPI: PCI interrupt for device 0000:00:1d.3 disabled
May 26 17:06:09 tarm kernel: [  271.385749] uhci_hcd 0000:00:1d.2: remove, state 1
May 26 17:06:09 tarm kernel: [  271.385756] usb usb4: USB disconnect, address 1
May 26 17:06:09 tarm kernel: [  271.385758] usb 4-1: USB disconnect, address 2
May 26 17:06:09 tarm kernel: [  271.646074] usb 4-2: USB disconnect, address 3
May 26 17:06:09 tarm kernel: [  271.648464] uhci_hcd 0000:00:1d.2: USB bus 4 deregistered
May 26 17:06:09 tarm kernel: [  271.648500] ACPI: PCI interrupt for device 0000:00:1d.2 disabled
May 26 17:06:09 tarm kernel: [  271.648511] uhci_hcd 0000:00:1d.1: remove, state 1
May 26 17:06:09 tarm kernel: [  271.648517] usb usb3: USB disconnect, address 1
May 26 17:06:09 tarm kernel: [  271.648519] usb 3-1: USB disconnect, address 2
May 26 17:06:09 tarm kernel: [  271.673669] uhci_hcd 0000:00:1d.1: USB bus 3 deregistered
May 26 17:06:09 tarm kernel: [  271.673858] ACPI: PCI interrupt for device 0000:00:1d.1 disabled
May 26 17:06:09 tarm kernel: [  271.673871] uhci_hcd 0000:00:1d.0: remove, state 4
May 26 17:06:09 tarm kernel: [  271.673878] usb usb2: USB disconnect, address 1
May 26 17:06:09 tarm kernel: [  271.674048] uhci_hcd 0000:00:1d.0: USB bus 2 deregistered
May 26 17:06:09 tarm kernel: [  271.674075] ACPI: PCI interrupt for device 0000:00:1d.0 disabled
May 26 17:06:11 tarm kernel: [  273.462926] PM: Syncing filesystems ... done.
May 26 17:06:23 tarm kernel: [  273.690876] Freezing user space processes ... (elapsed 0.00 seconds) done.
May 26 17:06:23 tarm kernel: [  273.692274] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
May 26 17:06:23 tarm kernel: [  273.692353] Suspending console(s)
May 26 17:06:23 tarm kernel: [  273.905802] sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 26 17:06:23 tarm kernel: [  273.914797] sd 0:0:0:0: [sda] Stopping disk
May 26 17:06:23 tarm kernel: [  275.349748] nsc-ircc 00:09: disabled
May 26 17:06:23 tarm kernel: [  275.349937] eth1: Going into suspend...
May 26 17:06:23 tarm kernel: [  275.354784] ACPI: PCI interrupt for device 0000:14:02.0 disabled
May 26 17:06:23 tarm kernel: [  275.354795] ACPI handle has no context!
May 26 17:06:23 tarm kernel: [  275.370131] ACPI handle has no context!
May 26 17:06:23 tarm kernel: [  275.370160] ACPI: PCI interrupt for device 0000:14:00.2 disabled
May 26 17:06:23 tarm kernel: [  275.370170] ACPI handle has no context!
May 26 17:06:23 tarm kernel: [  275.390076] ACPI handle has no context!
May 26 17:06:23 tarm kernel: [  275.546630] ACPI handle has no context!
May 26 17:06:23 tarm kernel: [  275.765051] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
May 26 17:06:23 tarm kernel: [  275.784291] ACPI: Preparing to enter system sleep state S3
May 26 17:06:23 tarm kernel: [  275.796812] Extended CMOS year: 2000
May 26 17:06:23 tarm kernel: [  275.796904] __ratelimit: 24 messages suppressed
May 26 17:06:23 tarm kernel: [  275.796909] cpufreq-core: suspending cpu 0
May 26 17:06:23 tarm kernel: [  275.796909] Intel machine check architecture supported.
May 26 17:06:23 tarm kernel: [  275.796925] Intel machine check reporting enabled on CPU#0.
May 26 17:06:23 tarm kernel: [  275.796967] Back to C!
May 26 17:06:23 tarm kernel: [  275.796967] Extended CMOS year: 2000
May 26 17:06:23 tarm kernel: [  275.796967] Force enabled HPET at resume
May 26 17:06:23 tarm kernel: [  275.796967] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:06:23 tarm kernel: [  275.796967] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:06:23 tarm kernel: [  275.796967] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:06:23 tarm kernel: [  275.796967] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:06:23 tarm kernel: [  275.796983] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:06:23 tarm kernel: [  275.796986] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:06:23 tarm kernel: [  275.796989] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:06:23 tarm kernel: [  275.796992] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 17:06:23 tarm kernel: [  275.796994] cpufreq-core: governor: change or update limits
May 26 17:06:23 tarm kernel: [  275.796996] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:06:23 tarm kernel: [  275.857830] PM: Writing back config space on device 0000:00:01.0 at offset 1 (was 100107, writing 100507)
May 26 17:06:23 tarm kernel: [  275.857830] PCI: Setting latency timer of device 0000:00:01.0 to 64
May 26 17:06:23 tarm kernel: [  275.877052] PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100002)
May 26 17:06:23 tarm kernel: [  275.877076] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:06:23 tarm kernel: [  275.877082] PCI: Setting latency timer of device 0000:00:1b.0 to 64
May 26 17:06:23 tarm kernel: [  275.933171] PM: Writing back config space on device 0000:00:1c.0 at offset 1 (was 100107, writing 100507)
May 26 17:06:23 tarm kernel: [  275.933245] PCI: Setting latency timer of device 0000:00:1c.0 to 64
May 26 17:06:23 tarm kernel: [  275.933296] PM: Writing back config space on device 0000:00:1c.1 at offset 1 (was 100107, writing 100507)
May 26 17:06:23 tarm kernel: [  275.933368] PCI: Setting latency timer of device 0000:00:1c.1 to 64
May 26 17:06:23 tarm kernel: [  275.933420] PM: Writing back config space on device 0000:00:1c.2 at offset 1 (was 100107, writing 100507)
May 26 17:06:23 tarm kernel: [  275.933483] PCI: Setting latency timer of device 0000:00:1c.2 to 64
May 26 17:06:23 tarm kernel: [  275.933544] PM: Writing back config space on device 0000:00:1c.3 at offset 1 (was 100107, writing 100507)
May 26 17:06:23 tarm kernel: [  275.933607] PCI: Setting latency timer of device 0000:00:1c.3 to 64
May 26 17:06:23 tarm kernel: [  275.933623] PM: Writing back config space on device 0000:00:1d.0 at offset f (was 100, writing 10b)
May 26 17:06:23 tarm kernel: [  275.933669] PM: Writing back config space on device 0000:00:1d.1 at offset f (was 200, writing 20b)
May 26 17:06:23 tarm kernel: [  275.933723] PM: Writing back config space on device 0000:00:1d.2 at offset f (was 300, writing 30b)
May 26 17:06:23 tarm kernel: [  275.933769] PM: Writing back config space on device 0000:00:1d.3 at offset f (was 400, writing 40b)
May 26 17:06:23 tarm kernel: [  275.933830] PM: Writing back config space on device 0000:00:1d.7 at offset f (was 400, writing 40b)
May 26 17:06:23 tarm kernel: [  275.933858] PM: Writing back config space on device 0000:00:1d.7 at offset 4 (was 0, writing b0004000)
May 26 17:06:23 tarm kernel: [  275.933875] PM: Writing back config space on device 0000:00:1d.7 at offset 1 (was 2900000, writing 2900102)
May 26 17:06:23 tarm kernel: [  275.933976] PCI: Setting latency timer of device 0000:00:1e.0 to 64
May 26 17:06:23 tarm kernel: [  275.949064] PM: Writing back config space on device 0000:00:1f.2 at offset 1 (was 2b00005, writing 2b80005)
May 26 17:06:23 tarm kernel: [  275.949089] PCI: Setting latency timer of device 0000:00:1f.2 to 64
May 26 17:06:23 tarm kernel: [  275.952615] PM: Writing back config space on device 0000:01:00.0 at offset 1 (was 100103, writing 100107)
May 26 17:06:23 tarm kernel: [  275.952725] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:06:23 tarm kernel: [  275.952732] PCI: Setting latency timer of device 0000:01:00.0 to 64
May 26 17:06:23 tarm kernel: [  275.952775] PM: Writing back config space on device 0000:02:00.0 at offset c (was 0, writing fcf70000)
May 26 17:06:23 tarm kernel: [  275.952805] PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 100106)
May 26 17:06:23 tarm kernel: [  276.289270] PM: Writing back config space on device 0000:14:00.1 at offset 4 (was 0, writing c0001000)
May 26 17:06:23 tarm kernel: [  276.289280] PM: Writing back config space on device 0000:14:00.1 at offset 3 (was 800000, writing 804000)
May 26 17:06:23 tarm kernel: [  276.289291] PM: Writing back config space on device 0000:14:00.1 at offset 1 (was 2100000, writing 2100106)
May 26 17:06:23 tarm kernel: [  276.301847] ata2.00: ACPI cmd ef/03:42:00:00:00:a0 filtered out
May 26 17:06:23 tarm kernel: [  276.301852] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
May 26 17:06:23 tarm kernel: [  276.309858] ata2.00: ACPI cmd e3/00:10:00:00:00:a0 succeeded
May 26 17:06:23 tarm kernel: [  276.317863] ata2.00: ACPI cmd e3/00:03:00:00:00:a0 succeeded
May 26 17:06:23 tarm kernel: [  276.342258] ata2.00: configured for UDMA/33
May 26 17:06:23 tarm kernel: [  276.344286] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17]  MMIO=[c0001000-c00017ff]  Max Packet=[2048]  IR/IT contexts=[4/4]
May 26 17:06:23 tarm kernel: [  276.369295] PM: Writing back config space on device 0000:14:00.2 at offset 4 (was 0, writing c0001800)
May 26 17:06:23 tarm kernel: [  276.369303] PM: Writing back config space on device 0000:14:00.2 at offset 3 (was 800000, writing 804000)
May 26 17:06:23 tarm kernel: [  276.369313] PM: Writing back config space on device 0000:14:00.2 at offset 1 (was 2100000, writing 2100106)
May 26 17:06:23 tarm kernel: [  276.369337] ACPI: PCI Interrupt 0000:14:00.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 17:06:23 tarm kernel: [  276.370387] eth1: Coming out of suspend...
May 26 17:06:23 tarm kernel: [  276.392223] ACPI: PCI Interrupt 0000:14:02.0[A] -> GSI 21 (level, low) -> IRQ 21
May 26 17:06:23 tarm kernel: [  276.394194] nsc-ircc 00:09: activated
May 26 17:06:23 tarm kernel: [  277.338077] sd 0:0:0:0: [sda] Starting disk
May 26 17:06:23 tarm kernel: [  277.385689] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 succeeded
May 26 17:06:23 tarm kernel: [  277.385692] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
May 26 17:06:23 tarm kernel: [  277.385696] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 filtered out
May 26 17:06:23 tarm kernel: [  277.385699] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
May 26 17:06:23 tarm kernel: [  277.386116] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 succeeded
May 26 17:06:23 tarm kernel: [  277.409617] ata1.00: configured for UDMA/100
May 26 17:06:23 tarm kernel: [  277.433629] ata1.00: configured for UDMA/100
May 26 17:06:23 tarm kernel: [  277.433633] ata1: EH complete
May 26 17:06:23 tarm kernel: [  277.433692] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
May 26 17:06:23 tarm kernel: [  277.433716] sd 0:0:0:0: [sda] Write Protect is off
May 26 17:06:23 tarm kernel: [  277.433719] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 26 17:06:23 tarm kernel: [  277.433761] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 26 17:06:23 tarm kernel: [  277.433802] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
May 26 17:06:23 tarm kernel: [  277.433825] sd 0:0:0:0: [sda] Write Protect is off
May 26 17:06:23 tarm kernel: [  277.433827] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 26 17:06:23 tarm kernel: [  277.433868] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 26 17:06:23 tarm kernel: [  280.139770] hdaps: initial latch check good (0x01).
May 26 17:06:23 tarm kernel: [  280.549499] Restarting tasks ... done.
May 26 17:06:23 tarm kernel: [  280.658346] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 19
May 26 17:06:23 tarm kernel: [  280.658607] PCI: Setting latency timer of device 0000:00:1d.7 to 64
May 26 17:06:23 tarm kernel: [  280.658749] ehci_hcd 0000:00:1d.7: EHCI Host Controller
May 26 17:06:23 tarm kernel: [  280.704830] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
May 26 17:06:23 tarm kernel: [  280.708957] ehci_hcd 0000:00:1d.7: debug port 1
May 26 17:06:23 tarm kernel: [  280.709163] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
May 26 17:06:23 tarm kernel: [  280.709320] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xb0004000
May 26 17:06:23 tarm kernel: [  280.725037] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
May 26 17:06:23 tarm kernel: [  280.725461] usb usb1: configuration #1 chosen from 1 choice
May 26 17:06:23 tarm kernel: [  280.726082] hub 1-0:1.0: USB hub found
May 26 17:06:23 tarm kernel: [  280.726103] hub 1-0:1.0: 8 ports detected
May 26 17:06:23 tarm kernel: [  280.829127] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
May 26 17:06:23 tarm kernel: [  280.829140] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:06:23 tarm kernel: [  280.829147] usb usb1: Product: EHCI Host Controller
May 26 17:06:23 tarm kernel: [  280.829152] usb usb1: Manufacturer: Linux 2.6.26-rc3 ehci_hcd
May 26 17:06:23 tarm kernel: [  280.829158] usb usb1: SerialNumber: 0000:00:1d.7
May 26 17:06:23 tarm kernel: [  280.843749] USB Universal Host Controller Interface driver v3.0
May 26 17:06:23 tarm kernel: [  280.843843] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:06:23 tarm kernel: [  280.843864] PCI: Setting latency timer of device 0000:00:1d.0 to 64
May 26 17:06:23 tarm kernel: [  280.843872] uhci_hcd 0000:00:1d.0: UHCI Host Controller
May 26 17:06:23 tarm kernel: [  280.843935] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
May 26 17:06:23 tarm kernel: [  280.843972] uhci_hcd 0000:00:1d.0: irq 16, io base 0x00001800
May 26 17:06:23 tarm kernel: [  280.844210] usb usb2: configuration #1 chosen from 1 choice
May 26 17:06:23 tarm kernel: [  280.844276] hub 2-0:1.0: USB hub found
May 26 17:06:23 tarm kernel: [  280.844290] hub 2-0:1.0: 2 ports detected
May 26 17:06:24 tarm kernel: [  280.941077] __ratelimit: 45 messages suppressed
May 26 17:06:24 tarm kernel: [  280.941274] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:06:24 tarm kernel: [  280.945074] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:06:24 tarm kernel: [  280.945079] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:06:24 tarm kernel: [  280.945082] usb usb2: Product: UHCI Host Controller
May 26 17:06:24 tarm kernel: [  280.945084] usb usb2: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:06:24 tarm kernel: [  280.945086] usb usb2: SerialNumber: 0000:00:1d.0
May 26 17:06:24 tarm kernel: [  280.945116] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 17
May 26 17:06:24 tarm kernel: [  280.945128] PCI: Setting latency timer of device 0000:00:1d.1 to 64
May 26 17:06:24 tarm kernel: [  280.945132] uhci_hcd 0000:00:1d.1: UHCI Host Controller
May 26 17:06:24 tarm kernel: [  280.945157] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
May 26 17:06:24 tarm kernel: [  280.945183] uhci_hcd 0000:00:1d.1: irq 17, io base 0x00001820
May 26 17:06:24 tarm kernel: [  280.945289] usb usb3: configuration #1 chosen from 1 choice
May 26 17:06:24 tarm kernel: [  280.945319] hub 3-0:1.0: USB hub found
May 26 17:06:24 tarm kernel: [  280.945325] hub 3-0:1.0: 2 ports detected
May 26 17:06:24 tarm kernel: [  281.030288] hub 1-0:1.0: unable to enumerate USB device on port 3
May 26 17:06:24 tarm kernel: [  281.049081] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:06:24 tarm kernel: [  281.050181] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:06:24 tarm kernel: [  281.050261] usb usb3: Product: UHCI Host Controller
May 26 17:06:24 tarm kernel: [  281.050314] usb usb3: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:06:24 tarm kernel: [  281.050366] usb usb3: SerialNumber: 0000:00:1d.1
May 26 17:06:24 tarm kernel: [  281.050448] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 17:06:24 tarm kernel: [  281.050533] PCI: Setting latency timer of device 0000:00:1d.2 to 64
May 26 17:06:24 tarm kernel: [  281.050598] uhci_hcd 0000:00:1d.2: UHCI Host Controller
May 26 17:06:24 tarm kernel: [  281.050677] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
May 26 17:06:24 tarm kernel: [  281.050756] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001840
May 26 17:06:24 tarm kernel: [  281.050917] usb usb4: configuration #1 chosen from 1 choice
May 26 17:06:24 tarm kernel: [  281.051000] hub 4-0:1.0: USB hub found
May 26 17:06:24 tarm kernel: [  281.051057] hub 4-0:1.0: 2 ports detected
May 26 17:06:24 tarm kernel: [  281.153093] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:06:24 tarm kernel: [  281.154270] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:06:24 tarm kernel: [  281.154351] usb usb4: Product: UHCI Host Controller
May 26 17:06:24 tarm kernel: [  281.154404] usb usb4: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:06:24 tarm kernel: [  281.154456] usb usb4: SerialNumber: 0000:00:1d.2
May 26 17:06:24 tarm kernel: [  281.154541] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 19
May 26 17:06:24 tarm kernel: [  281.154626] PCI: Setting latency timer of device 0000:00:1d.3 to 64
May 26 17:06:24 tarm kernel: [  281.154690] uhci_hcd 0000:00:1d.3: UHCI Host Controller
May 26 17:06:24 tarm kernel: [  281.154772] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
May 26 17:06:24 tarm kernel: [  281.154851] uhci_hcd 0000:00:1d.3: irq 19, io base 0x00001860
May 26 17:06:24 tarm kernel: [  281.155013] usb usb5: configuration #1 chosen from 1 choice
May 26 17:06:24 tarm kernel: [  281.155096] hub 5-0:1.0: USB hub found
May 26 17:06:24 tarm kernel: [  281.155153] hub 5-0:1.0: 2 ports detected
May 26 17:06:24 tarm kernel: [  281.257066] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:06:24 tarm kernel: [  281.258029] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:06:24 tarm kernel: [  281.258106] usb usb5: Product: UHCI Host Controller
May 26 17:06:24 tarm kernel: [  281.258159] usb usb5: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:06:24 tarm kernel: [  281.258210] usb usb5: SerialNumber: 0000:00:1d.3
May 26 17:06:24 tarm kernel: [  281.273474] hub 1-0:1.0: unable to enumerate USB device on port 5
May 26 17:06:24 tarm kernel: [  281.379226] [drm] Loading R300 Microcode
May 26 17:06:24 tarm kernel: [  281.513044] hub 1-0:1.0: unable to enumerate USB device on port 6
May 26 17:06:24 tarm kernel: [  281.757204] usb 3-1: new low speed USB device using uhci_hcd and address 2
May 26 17:06:24 tarm kernel: [  281.936966] usb 3-1: configuration #1 chosen from 1 choice
May 26 17:06:24 tarm kernel: [  281.965684] input: Logitech Trackball as /class/input/input13
May 26 17:06:24 tarm kernel: [  281.993174] input,hidraw0: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:1d.1-1
May 26 17:06:24 tarm kernel: [  281.993454] usb 3-1: New USB device found, idVendor=046d, idProduct=c404
May 26 17:06:24 tarm kernel: [  281.993531] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:06:24 tarm kernel: [  281.993602] usb 3-1: Product: Trackball
May 26 17:06:24 tarm kernel: [  281.993668] usb 3-1: Manufacturer: Logitech
May 26 17:06:24 tarm kernel: [  282.237073] usb 4-1: new full speed USB device using uhci_hcd and address 2
May 26 17:06:24 tarm kernel: [  282.417060] usb 4-1: configuration #1 chosen from 1 choice
May 26 17:06:24 tarm kernel: [  282.423275] usb 4-1: New USB device found, idVendor=0a5c, idProduct=2110
May 26 17:06:24 tarm kernel: [  282.423361] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:06:24 tarm kernel: [  282.423430] usb 4-1: Product: BCM2045B
May 26 17:06:24 tarm kernel: [  282.423494] usb 4-1: Manufacturer: Broadcom Corp
May 26 17:06:25 tarm kernel: [  282.759606] usb 4-2: new full speed USB device using uhci_hcd and address 3
May 26 17:06:25 tarm kernel: [  282.953187] usb 4-2: configuration #1 chosen from 1 choice
May 26 17:06:25 tarm kernel: [  282.958536] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 17:06:25 tarm kernel: [  282.959408] pan1: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 17:06:25 tarm kernel: [  282.966418] usb 4-2: New USB device found, idVendor=0483, idProduct=2016
May 26 17:06:25 tarm kernel: [  282.966516] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:06:25 tarm kernel: [  282.966571] usb 4-2: Product: Biometric Coprocessor
May 26 17:06:25 tarm kernel: [  282.966622] usb 4-2: Manufacturer: STMicroelectronics
May 26 17:06:26 tarm kernel: [  284.497105] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 26 17:06:27 tarm kernel: [  284.940986] __ratelimit: 41 messages suppressed
May 26 17:06:27 tarm kernel: [  284.941058] cpufreq-core: target for CPU 0: 114285 kHz, relation 0
May 26 17:06:32 tarm kernel: [  290.334663] ADDRCONF(NETDEV_UP): eth1: link is not ready
May 26 17:06:32 tarm kernel: [  290.441110] __ratelimit: 6 messages suppressed
May 26 17:06:32 tarm kernel: [  290.441265] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:06:33 tarm kernel: [  291.281839] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
May 26 17:06:36 tarm kernel: [  293.870899] tun0: Disabled Privacy Extensions
May 26 17:06:37 tarm kernel: [  294.940986] __ratelimit: 20 messages suppressed
May 26 17:06:37 tarm kernel: [  294.941101] cpufreq-core: target for CPU 0: 0 kHz, relation 0
May 26 17:06:44 tarm kernel: [  301.552982] eth1: no IPv6 routers present
May 26 17:07:01 tarm kernel: [  318.625003] __ratelimit: 20 messages suppressed
May 26 17:07:01 tarm kernel: [  318.625022] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:07:01 tarm kernel: [  318.625030] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:07:01 tarm kernel: [  318.625038] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:07:01 tarm kernel: [  318.625046] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:07:01 tarm kernel: [  319.047860] ehci_hcd 0000:00:1d.7: remove, state 4
May 26 17:07:01 tarm kernel: [  319.047874] usb usb1: USB disconnect, address 1
May 26 17:07:01 tarm kernel: [  319.079601] ehci_hcd 0000:00:1d.7: USB bus 1 deregistered
May 26 17:07:01 tarm kernel: [  319.079660] ACPI: PCI interrupt for device 0000:00:1d.7 disabled
May 26 17:07:01 tarm kernel: [  319.080377] uhci_hcd 0000:00:1d.3: remove, state 4
May 26 17:07:01 tarm kernel: [  319.080387] usb usb5: USB disconnect, address 1
May 26 17:07:01 tarm kernel: [  319.080579] uhci_hcd 0000:00:1d.3: USB bus 5 deregistered
May 26 17:07:01 tarm kernel: [  319.080608] ACPI: PCI interrupt for device 0000:00:1d.3 disabled
May 26 17:07:01 tarm kernel: [  319.080617] uhci_hcd 0000:00:1d.2: remove, state 1
May 26 17:07:01 tarm kernel: [  319.080624] usb usb4: USB disconnect, address 1
May 26 17:07:01 tarm kernel: [  319.080626] usb 4-1: USB disconnect, address 2
May 26 17:07:01 tarm kernel: [  319.338078] usb 4-2: USB disconnect, address 3
May 26 17:07:01 tarm kernel: [  319.340537] uhci_hcd 0000:00:1d.2: USB bus 4 deregistered
May 26 17:07:01 tarm kernel: [  319.340575] ACPI: PCI interrupt for device 0000:00:1d.2 disabled
May 26 17:07:01 tarm kernel: [  319.340586] uhci_hcd 0000:00:1d.1: remove, state 1
May 26 17:07:01 tarm kernel: [  319.340593] usb usb3: USB disconnect, address 1
May 26 17:07:01 tarm kernel: [  319.340595] usb 3-1: USB disconnect, address 2
May 26 17:07:01 tarm kernel: [  319.361423] uhci_hcd 0000:00:1d.1: USB bus 3 deregistered
May 26 17:07:01 tarm kernel: [  319.361611] ACPI: PCI interrupt for device 0000:00:1d.1 disabled
May 26 17:07:01 tarm kernel: [  319.361697] uhci_hcd 0000:00:1d.0: remove, state 4
May 26 17:07:01 tarm kernel: [  319.361706] usb usb2: USB disconnect, address 1
May 26 17:07:01 tarm kernel: [  319.361878] uhci_hcd 0000:00:1d.0: USB bus 2 deregistered
May 26 17:07:01 tarm kernel: [  319.361906] ACPI: PCI interrupt for device 0000:00:1d.0 disabled
May 26 17:07:02 tarm kernel: [  320.125024] __ratelimit: 3 messages suppressed
May 26 17:07:02 tarm kernel: [  320.125149] cpufreq-core: target for CPU 0: 57142 kHz, relation 0
May 26 17:07:03 tarm kernel: [  321.072150] PM: Syncing filesystems ... done.
May 26 17:07:19 tarm kernel: [  321.137914] Freezing user space processes ... (elapsed 0.00 seconds) done.
May 26 17:07:19 tarm kernel: [  321.139290] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
May 26 17:07:19 tarm kernel: [  321.139371] Suspending console(s)
May 26 17:07:19 tarm kernel: [  321.356723] sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 26 17:07:19 tarm kernel: [  321.365852] sd 0:0:0:0: [sda] Stopping disk
May 26 17:07:19 tarm kernel: [  322.821787] nsc-ircc 00:09: disabled
May 26 17:07:19 tarm kernel: [  322.821976] eth1: Going into suspend...
May 26 17:07:19 tarm kernel: [  322.826659] ACPI: PCI interrupt for device 0000:14:02.0 disabled
May 26 17:07:19 tarm kernel: [  322.826671] ACPI handle has no context!
May 26 17:07:19 tarm kernel: [  322.842141] ACPI handle has no context!
May 26 17:07:19 tarm kernel: [  322.842170] ACPI: PCI interrupt for device 0000:14:00.2 disabled
May 26 17:07:19 tarm kernel: [  322.842181] ACPI handle has no context!
May 26 17:07:19 tarm kernel: [  322.862080] ACPI handle has no context!
May 26 17:07:19 tarm kernel: [  323.018603] ACPI handle has no context!
May 26 17:07:19 tarm kernel: [  323.237051] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
May 26 17:07:19 tarm kernel: [  323.256304] ACPI: Preparing to enter system sleep state S3
May 26 17:07:19 tarm kernel: [  323.268938] Extended CMOS year: 2000
May 26 17:07:19 tarm kernel: [  323.268938] Intel machine check architecture supported.
May 26 17:07:19 tarm kernel: [  323.268953] Intel machine check reporting enabled on CPU#0.
May 26 17:07:19 tarm kernel: [  323.268967] Back to C!
May 26 17:07:19 tarm kernel: [  323.268967] Extended CMOS year: 2000
May 26 17:07:19 tarm kernel: [  323.268967] Force enabled HPET at resume
May 26 17:07:19 tarm kernel: [  323.269152] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:07:19 tarm kernel: [  323.269154] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:07:19 tarm kernel: [  323.269157] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:07:19 tarm kernel: [  323.269160] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:07:19 tarm kernel: [  323.269164] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:07:19 tarm kernel: [  323.269166] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:07:19 tarm kernel: [  323.269169] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:07:19 tarm kernel: [  323.269172] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 17:07:19 tarm kernel: [  323.269175] cpufreq-core: governor: change or update limits
May 26 17:07:19 tarm kernel: [  323.269177] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:07:19 tarm kernel: [  323.326536] PM: Writing back config space on device 0000:00:01.0 at offset 1 (was 100107, writing 100507)
May 26 17:07:19 tarm kernel: [  323.326536] PCI: Setting latency timer of device 0000:00:01.0 to 64
May 26 17:07:19 tarm kernel: [  323.345052] PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100002)
May 26 17:07:19 tarm kernel: [  323.345076] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:07:19 tarm kernel: [  323.345082] PCI: Setting latency timer of device 0000:00:1b.0 to 64
May 26 17:07:19 tarm kernel: [  323.401171] PM: Writing back config space on device 0000:00:1c.0 at offset 1 (was 100107, writing 100507)
May 26 17:07:19 tarm kernel: [  323.401243] PCI: Setting latency timer of device 0000:00:1c.0 to 64
May 26 17:07:19 tarm kernel: [  323.401295] PM: Writing back config space on device 0000:00:1c.1 at offset 1 (was 100107, writing 100507)
May 26 17:07:19 tarm kernel: [  323.401358] PCI: Setting latency timer of device 0000:00:1c.1 to 64
May 26 17:07:19 tarm kernel: [  323.401419] PM: Writing back config space on device 0000:00:1c.2 at offset 1 (was 100107, writing 100507)
May 26 17:07:19 tarm kernel: [  323.401482] PCI: Setting latency timer of device 0000:00:1c.2 to 64
May 26 17:07:19 tarm kernel: [  323.401543] PM: Writing back config space on device 0000:00:1c.3 at offset 1 (was 100107, writing 100507)
May 26 17:07:19 tarm kernel: [  323.401606] PCI: Setting latency timer of device 0000:00:1c.3 to 64
May 26 17:07:19 tarm kernel: [  323.401622] PM: Writing back config space on device 0000:00:1d.0 at offset f (was 100, writing 10b)
May 26 17:07:19 tarm kernel: [  323.401669] PM: Writing back config space on device 0000:00:1d.1 at offset f (was 200, writing 20b)
May 26 17:07:19 tarm kernel: [  323.401723] PM: Writing back config space on device 0000:00:1d.2 at offset f (was 300, writing 30b)
May 26 17:07:19 tarm kernel: [  323.401769] PM: Writing back config space on device 0000:00:1d.3 at offset f (was 400, writing 40b)
May 26 17:07:19 tarm kernel: [  323.401832] PM: Writing back config space on device 0000:00:1d.7 at offset f (was 400, writing 40b)
May 26 17:07:19 tarm kernel: [  323.401859] PM: Writing back config space on device 0000:00:1d.7 at offset 4 (was 0, writing b0004000)
May 26 17:07:19 tarm kernel: [  323.401876] PM: Writing back config space on device 0000:00:1d.7 at offset 1 (was 2900000, writing 2900102)
May 26 17:07:19 tarm kernel: [  323.401976] PCI: Setting latency timer of device 0000:00:1e.0 to 64
May 26 17:07:19 tarm kernel: [  323.417044] PM: Writing back config space on device 0000:00:1f.2 at offset 1 (was 2b00005, writing 2b80005)
May 26 17:07:19 tarm kernel: [  323.417064] PCI: Setting latency timer of device 0000:00:1f.2 to 64
May 26 17:07:19 tarm kernel: [  323.419257] PM: Writing back config space on device 0000:01:00.0 at offset 1 (was 100103, writing 100107)
May 26 17:07:19 tarm kernel: [  323.419321] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:07:19 tarm kernel: [  323.419326] PCI: Setting latency timer of device 0000:01:00.0 to 64
May 26 17:07:19 tarm kernel: [  323.419363] PM: Writing back config space on device 0000:02:00.0 at offset c (was 0, writing d4ff0000)
May 26 17:07:19 tarm kernel: [  323.419389] PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 100106)
May 26 17:07:19 tarm kernel: [  323.757256] PM: Writing back config space on device 0000:14:00.1 at offset 4 (was 0, writing c0001000)
May 26 17:07:19 tarm kernel: [  323.757262] PM: Writing back config space on device 0000:14:00.1 at offset 3 (was 800000, writing 804000)
May 26 17:07:19 tarm kernel: [  323.757270] PM: Writing back config space on device 0000:14:00.1 at offset 1 (was 2100000, writing 2100106)
May 26 17:07:19 tarm kernel: [  323.769823] ata2.00: ACPI cmd ef/03:42:00:00:00:a0 filtered out
May 26 17:07:19 tarm kernel: [  323.769825] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
May 26 17:07:19 tarm kernel: [  323.777829] ata2.00: ACPI cmd e3/00:10:00:00:00:a0 succeeded
May 26 17:07:19 tarm kernel: [  323.785831] ata2.00: ACPI cmd e3/00:03:00:00:00:a0 succeeded
May 26 17:07:19 tarm kernel: [  323.810167] ata2.00: configured for UDMA/33
May 26 17:07:19 tarm kernel: [  323.812184] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17]  MMIO=[c0001000-c00017ff]  Max Packet=[2048]  IR/IT contexts=[4/4]
May 26 17:07:19 tarm kernel: [  323.837197] PM: Writing back config space on device 0000:14:00.2 at offset 4 (was 0, writing c0001800)
May 26 17:07:19 tarm kernel: [  323.837202] PM: Writing back config space on device 0000:14:00.2 at offset 3 (was 800000, writing 804000)
May 26 17:07:19 tarm kernel: [  323.837209] PM: Writing back config space on device 0000:14:00.2 at offset 1 (was 2100000, writing 2100106)
May 26 17:07:19 tarm kernel: [  323.837229] ACPI: PCI Interrupt 0000:14:00.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 17:07:19 tarm kernel: [  323.838273] eth1: Coming out of suspend...
May 26 17:07:19 tarm kernel: [  323.860123] ACPI: PCI Interrupt 0000:14:02.0[A] -> GSI 21 (level, low) -> IRQ 21
May 26 17:07:19 tarm kernel: [  323.860864] nsc-ircc 00:09: activated
May 26 17:07:19 tarm kernel: [  324.789657] sd 0:0:0:0: [sda] Starting disk
May 26 17:07:19 tarm kernel: [  325.125335] __ratelimit: 52 messages suppressed
May 26 17:07:19 tarm kernel: [  325.125339] cpufreq-core: target for CPU 0: 38085 kHz, relation 0
May 26 17:07:19 tarm kernel: [  325.125688] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 succeeded
May 26 17:07:19 tarm kernel: [  325.125695] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
May 26 17:07:19 tarm kernel: [  325.125701] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 filtered out
May 26 17:07:19 tarm kernel: [  325.125708] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
May 26 17:07:19 tarm kernel: [  325.126119] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 succeeded
May 26 17:07:19 tarm kernel: [  325.149648] ata1.00: configured for UDMA/100
May 26 17:07:19 tarm kernel: [  325.173676] ata1.00: configured for UDMA/100
May 26 17:07:19 tarm kernel: [  325.173682] ata1: EH complete
May 26 17:07:19 tarm kernel: [  325.173775] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
May 26 17:07:19 tarm kernel: [  325.173817] sd 0:0:0:0: [sda] Write Protect is off
May 26 17:07:19 tarm kernel: [  325.173823] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 26 17:07:19 tarm kernel: [  325.173896] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 26 17:07:19 tarm kernel: [  325.173968] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
May 26 17:07:19 tarm kernel: [  325.174008] sd 0:0:0:0: [sda] Write Protect is off
May 26 17:07:19 tarm kernel: [  325.174013] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 26 17:07:19 tarm kernel: [  325.174084] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 26 17:07:19 tarm kernel: [  327.870104] hdaps: initial latch check good (0x01).
May 26 17:07:19 tarm kernel: [  328.077513] Restarting tasks ... done.
May 26 17:07:19 tarm kernel: [  328.172324] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 19
May 26 17:07:19 tarm kernel: [  328.172586] PCI: Setting latency timer of device 0000:00:1d.7 to 64
May 26 17:07:19 tarm kernel: [  328.172726] ehci_hcd 0000:00:1d.7: EHCI Host Controller
May 26 17:07:19 tarm kernel: [  328.213571] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
May 26 17:07:19 tarm kernel: [  328.221618] ehci_hcd 0000:00:1d.7: debug port 1
May 26 17:07:19 tarm kernel: [  328.221789] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
May 26 17:07:19 tarm kernel: [  328.221944] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xb0004000
May 26 17:07:19 tarm kernel: [  328.237572] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
May 26 17:07:19 tarm kernel: [  328.238055] usb usb1: configuration #1 chosen from 1 choice
May 26 17:07:19 tarm kernel: [  328.238247] hub 1-0:1.0: USB hub found
May 26 17:07:19 tarm kernel: [  328.238372] hub 1-0:1.0: 8 ports detected
May 26 17:07:19 tarm kernel: [  328.341642] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
May 26 17:07:19 tarm kernel: [  328.341880] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:07:19 tarm kernel: [  328.342007] usb usb1: Product: EHCI Host Controller
May 26 17:07:19 tarm kernel: [  328.342120] usb usb1: Manufacturer: Linux 2.6.26-rc3 ehci_hcd
May 26 17:07:19 tarm kernel: [  328.342235] usb usb1: SerialNumber: 0000:00:1d.7
May 26 17:07:19 tarm kernel: [  328.353090] USB Universal Host Controller Interface driver v3.0
May 26 17:07:19 tarm kernel: [  328.353174] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:07:19 tarm kernel: [  328.353194] PCI: Setting latency timer of device 0000:00:1d.0 to 64
May 26 17:07:19 tarm kernel: [  328.353202] uhci_hcd 0000:00:1d.0: UHCI Host Controller
May 26 17:07:19 tarm kernel: [  328.353261] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
May 26 17:07:19 tarm kernel: [  328.353298] uhci_hcd 0000:00:1d.0: irq 16, io base 0x00001800
May 26 17:07:19 tarm kernel: [  328.353532] usb usb2: configuration #1 chosen from 1 choice
May 26 17:07:19 tarm kernel: [  328.353598] hub 2-0:1.0: USB hub found
May 26 17:07:19 tarm kernel: [  328.353613] hub 2-0:1.0: 2 ports detected
May 26 17:07:19 tarm kernel: [  328.457151] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:07:19 tarm kernel: [  328.457377] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:07:19 tarm kernel: [  328.457501] usb usb2: Product: UHCI Host Controller
May 26 17:07:19 tarm kernel: [  328.457613] usb usb2: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:07:19 tarm kernel: [  328.457724] usb usb2: SerialNumber: 0000:00:1d.0
May 26 17:07:19 tarm kernel: [  328.457868] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 17
May 26 17:07:19 tarm kernel: [  328.458033] PCI: Setting latency timer of device 0000:00:1d.1 to 64
May 26 17:07:19 tarm kernel: [  328.458169] uhci_hcd 0000:00:1d.1: UHCI Host Controller
May 26 17:07:19 tarm kernel: [  328.458330] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
May 26 17:07:19 tarm kernel: [  328.458479] uhci_hcd 0000:00:1d.1: irq 17, io base 0x00001820
May 26 17:07:19 tarm kernel: [  328.458816] usb usb3: configuration #1 chosen from 1 choice
May 26 17:07:19 tarm kernel: [  328.458999] hub 3-0:1.0: USB hub found
May 26 17:07:19 tarm kernel: [  328.459121] hub 3-0:1.0: 2 ports detected
May 26 17:07:19 tarm kernel: [  328.533056] hub 1-0:1.0: unable to enumerate USB device on port 3
May 26 17:07:20 tarm kernel: [  328.565084] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:07:20 tarm kernel: [  328.565097] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:07:20 tarm kernel: [  328.565104] usb usb3: Product: UHCI Host Controller
May 26 17:07:20 tarm kernel: [  328.565109] usb usb3: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:07:20 tarm kernel: [  328.565115] usb usb3: SerialNumber: 0000:00:1d.1
May 26 17:07:20 tarm kernel: [  328.565159] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 17:07:20 tarm kernel: [  328.565178] PCI: Setting latency timer of device 0000:00:1d.2 to 64
May 26 17:07:20 tarm kernel: [  328.565186] uhci_hcd 0000:00:1d.2: UHCI Host Controller
May 26 17:07:20 tarm kernel: [  328.565240] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
May 26 17:07:20 tarm kernel: [  328.565276] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001840
May 26 17:07:20 tarm kernel: [  328.565511] usb usb4: configuration #1 chosen from 1 choice
May 26 17:07:20 tarm kernel: [  328.565579] hub 4-0:1.0: USB hub found
May 26 17:07:20 tarm kernel: [  328.565593] hub 4-0:1.0: 2 ports detected
May 26 17:07:20 tarm kernel: [  328.669053] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:07:20 tarm kernel: [  328.669060] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:07:20 tarm kernel: [  328.669063] usb usb4: Product: UHCI Host Controller
May 26 17:07:20 tarm kernel: [  328.669065] usb usb4: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:07:20 tarm kernel: [  328.669067] usb usb4: SerialNumber: 0000:00:1d.2
May 26 17:07:20 tarm kernel: [  328.669098] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 19
May 26 17:07:20 tarm kernel: [  328.669110] PCI: Setting latency timer of device 0000:00:1d.3 to 64
May 26 17:07:20 tarm kernel: [  328.669114] uhci_hcd 0000:00:1d.3: UHCI Host Controller
May 26 17:07:20 tarm kernel: [  328.669139] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
May 26 17:07:20 tarm kernel: [  328.669165] uhci_hcd 0000:00:1d.3: irq 19, io base 0x00001860
May 26 17:07:20 tarm kernel: [  328.669274] usb usb5: configuration #1 chosen from 1 choice
May 26 17:07:20 tarm kernel: [  328.669303] hub 5-0:1.0: USB hub found
May 26 17:07:20 tarm kernel: [  328.669310] hub 5-0:1.0: 2 ports detected
May 26 17:07:20 tarm kernel: [  328.776648] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:07:20 tarm kernel: [  328.776780] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:07:20 tarm kernel: [  328.776834] usb usb5: Product: UHCI Host Controller
May 26 17:07:20 tarm kernel: [  328.776885] usb usb5: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:07:20 tarm kernel: [  328.776936] usb usb5: SerialNumber: 0000:00:1d.3
May 26 17:07:20 tarm kernel: [  328.779921] hub 1-0:1.0: unable to enumerate USB device on port 5
May 26 17:07:20 tarm kernel: [  328.892529] [drm] Loading R300 Microcode
May 26 17:07:20 tarm kernel: [  329.017160] hub 1-0:1.0: unable to enumerate USB device on port 6
May 26 17:07:20 tarm kernel: [  329.257301] usb 3-1: new low speed USB device using uhci_hcd and address 2
May 26 17:07:20 tarm kernel: [  329.437971] usb 3-1: configuration #1 chosen from 1 choice
May 26 17:07:20 tarm kernel: [  329.465534] input: Logitech Trackball as /class/input/input14
May 26 17:07:20 tarm kernel: [  329.497198] input,hidraw0: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:1d.1-1
May 26 17:07:20 tarm kernel: [  329.497501] usb 3-1: New USB device found, idVendor=046d, idProduct=c404
May 26 17:07:20 tarm kernel: [  329.497557] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:07:20 tarm kernel: [  329.497609] usb 3-1: Product: Trackball
May 26 17:07:20 tarm kernel: [  329.497659] usb 3-1: Manufacturer: Logitech
May 26 17:07:21 tarm kernel: [  329.737045] usb 4-1: new full speed USB device using uhci_hcd and address 2
May 26 17:07:21 tarm kernel: [  329.913487] usb 4-1: configuration #1 chosen from 1 choice
May 26 17:07:21 tarm kernel: [  329.923683] usb 4-1: New USB device found, idVendor=0a5c, idProduct=2110
May 26 17:07:21 tarm kernel: [  329.923973] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:07:21 tarm kernel: [  329.924025] usb 4-1: Product: BCM2045B
May 26 17:07:21 tarm kernel: [  329.924072] usb 4-1: Manufacturer: Broadcom Corp
May 26 17:07:21 tarm kernel: [  330.172998] usb 4-2: new full speed USB device using uhci_hcd and address 3
May 26 17:07:21 tarm kernel: [  330.181692] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 17:07:21 tarm kernel: [  330.190476] pan1: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 17:07:21 tarm kernel: [  330.342681] usb 4-2: configuration #1 chosen from 1 choice
May 26 17:07:21 tarm kernel: [  330.349671] usb 4-2: New USB device found, idVendor=0483, idProduct=2016
May 26 17:07:21 tarm kernel: [  330.349780] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:07:21 tarm kernel: [  330.349835] usb 4-2: Product: Biometric Coprocessor
May 26 17:07:21 tarm kernel: [  330.349886] usb 4-2: Manufacturer: STMicroelectronics
May 26 17:07:21 tarm kernel: [  330.625099] __ratelimit: 20 messages suppressed
May 26 17:07:21 tarm kernel: [  330.625238] cpufreq-core: target for CPU 0: 1942857 kHz, relation 0
May 26 17:07:23 tarm kernel: [  332.637273] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 26 17:07:29 tarm kernel: [  338.506662] ADDRCONF(NETDEV_UP): eth1: link is not ready
May 26 17:07:29 tarm kernel: [  338.625094] __ratelimit: 30 messages suppressed
May 26 17:07:29 tarm kernel: [  338.625267] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:07:30 tarm kernel: [  339.434521] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
May 26 17:07:33 tarm kernel: [  342.049414] tun0: Disabled Privacy Extensions
May 26 17:07:33 tarm kernel: [  342.625029] __ratelimit: 13 messages suppressed
May 26 17:07:33 tarm kernel: [  342.625186] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:07:39 tarm kernel: [  348.625008] __ratelimit: 27 messages suppressed
May 26 17:07:39 tarm kernel: [  348.625222] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:07:41 tarm kernel: [  350.124978] eth1: no IPv6 routers present
May 26 17:07:41 tarm kernel: [  350.625131] __ratelimit: 6 messages suppressed
May 26 17:07:41 tarm kernel: [  350.625143] cpufreq-core: target for CPU 0: 1485714 kHz, relation 0
May 26 17:07:46 tarm kernel: [  355.125008] __ratelimit: 25 messages suppressed
May 26 17:07:46 tarm kernel: [  355.125252] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:07:51 tarm kernel: [  360.124988] __ratelimit: 27 messages suppressed
May 26 17:07:51 tarm kernel: [  360.125128] cpufreq-core: target for CPU 0: 1314285 kHz, relation 0
May 26 17:08:02 tarm kernel: [  371.125078] __ratelimit: 39 messages suppressed
May 26 17:08:02 tarm kernel: [  371.125322] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:08:02 tarm kernel: [  371.125467] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:08:16 tarm kernel: [  385.625001] __ratelimit: 47 messages suppressed
May 26 17:08:16 tarm kernel: [  385.625020] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:08:16 tarm kernel: [  385.625028] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:08:16 tarm kernel: [  385.625036] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:08:17 tarm kernel: [  386.157723] ehci_hcd 0000:00:1d.7: remove, state 4
May 26 17:08:17 tarm kernel: [  386.157853] usb usb1: USB disconnect, address 1
May 26 17:08:17 tarm kernel: [  386.181821] ehci_hcd 0000:00:1d.7: USB bus 1 deregistered
May 26 17:08:17 tarm kernel: [  386.182020] ACPI: PCI interrupt for device 0000:00:1d.7 disabled
May 26 17:08:17 tarm kernel: [  386.182887] uhci_hcd 0000:00:1d.3: remove, state 4
May 26 17:08:17 tarm kernel: [  386.182899] usb usb5: USB disconnect, address 1
May 26 17:08:17 tarm kernel: [  386.183094] uhci_hcd 0000:00:1d.3: USB bus 5 deregistered
May 26 17:08:17 tarm kernel: [  386.183123] ACPI: PCI interrupt for device 0000:00:1d.3 disabled
May 26 17:08:17 tarm kernel: [  386.183132] uhci_hcd 0000:00:1d.2: remove, state 1
May 26 17:08:17 tarm kernel: [  386.183139] usb usb4: USB disconnect, address 1
May 26 17:08:17 tarm kernel: [  386.183141] usb 4-1: USB disconnect, address 2
May 26 17:08:17 tarm kernel: [  386.438098] usb 4-2: USB disconnect, address 3
May 26 17:08:17 tarm kernel: [  386.440480] uhci_hcd 0000:00:1d.2: USB bus 4 deregistered
May 26 17:08:17 tarm kernel: [  386.440624] ACPI: PCI interrupt for device 0000:00:1d.2 disabled
May 26 17:08:17 tarm kernel: [  386.440690] uhci_hcd 0000:00:1d.1: remove, state 1
May 26 17:08:17 tarm kernel: [  386.440749] usb usb3: USB disconnect, address 1
May 26 17:08:17 tarm kernel: [  386.440802] usb 3-1: USB disconnect, address 2
May 26 17:08:17 tarm kernel: [  386.465468] uhci_hcd 0000:00:1d.1: USB bus 3 deregistered
May 26 17:08:17 tarm kernel: [  386.465640] ACPI: PCI interrupt for device 0000:00:1d.1 disabled
May 26 17:08:17 tarm kernel: [  386.465709] uhci_hcd 0000:00:1d.0: remove, state 4
May 26 17:08:17 tarm kernel: [  386.465785] usb usb2: USB disconnect, address 1
May 26 17:08:17 tarm kernel: [  386.466014] uhci_hcd 0000:00:1d.0: USB bus 2 deregistered
May 26 17:08:17 tarm kernel: [  386.466101] ACPI: PCI interrupt for device 0000:00:1d.0 disabled
May 26 17:08:19 tarm kernel: [  388.361475] PM: Syncing filesystems ... done.
May 26 17:08:32 tarm kernel: [  388.430003] Freezing user space processes ... (elapsed 0.00 seconds) done.
May 26 17:08:32 tarm kernel: [  388.431517] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
May 26 17:08:32 tarm kernel: [  388.431599] Suspending console(s)
May 26 17:08:32 tarm kernel: [  388.643461] sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 26 17:08:32 tarm kernel: [  388.643572] sd 0:0:0:0: [sda] Stopping disk
May 26 17:08:32 tarm kernel: [  390.058000] nsc-ircc 00:09: disabled
May 26 17:08:32 tarm kernel: [  390.058190] eth1: Going into suspend...
May 26 17:08:32 tarm kernel: [  390.063072] ACPI: PCI interrupt for device 0000:14:02.0 disabled
May 26 17:08:32 tarm kernel: [  390.063083] ACPI handle has no context!
May 26 17:08:32 tarm kernel: [  390.078142] ACPI handle has no context!
May 26 17:08:32 tarm kernel: [  390.078171] ACPI: PCI interrupt for device 0000:14:00.2 disabled
May 26 17:08:32 tarm kernel: [  390.078181] ACPI handle has no context!
May 26 17:08:32 tarm kernel: [  390.098077] ACPI handle has no context!
May 26 17:08:32 tarm kernel: [  390.254616] ACPI handle has no context!
May 26 17:08:32 tarm kernel: [  390.473051] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
May 26 17:08:32 tarm kernel: [  390.492624] ACPI: Preparing to enter system sleep state S3
May 26 17:08:32 tarm kernel: [  390.505459] Extended CMOS year: 2000
May 26 17:08:32 tarm kernel: [  390.505550] __ratelimit: 30 messages suppressed
May 26 17:08:32 tarm kernel: [  390.505555] cpufreq-core: suspending cpu 0
May 26 17:08:32 tarm kernel: [  390.505555] Intel machine check architecture supported.
May 26 17:08:32 tarm kernel: [  390.505571] Intel machine check reporting enabled on CPU#0.
May 26 17:08:32 tarm kernel: [  390.505672] Back to C!
May 26 17:08:32 tarm kernel: [  390.505970] Extended CMOS year: 2000
May 26 17:08:32 tarm kernel: [  390.505976] Force enabled HPET at resume
May 26 17:08:32 tarm kernel: [  390.506151] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:08:32 tarm kernel: [  390.506153] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:08:32 tarm kernel: [  390.506156] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:08:32 tarm kernel: [  390.506159] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:08:32 tarm kernel: [  390.506163] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:08:32 tarm kernel: [  390.506165] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:08:32 tarm kernel: [  390.506168] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:08:32 tarm kernel: [  390.506171] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 17:08:32 tarm kernel: [  390.506173] cpufreq-core: governor: change or update limits
May 26 17:08:32 tarm kernel: [  390.506176] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:08:32 tarm kernel: [  390.558306] PM: Writing back config space on device 0000:00:01.0 at offset 1 (was 100107, writing 100507)
May 26 17:08:32 tarm kernel: [  390.558306] PCI: Setting latency timer of device 0000:00:01.0 to 64
May 26 17:08:32 tarm kernel: [  390.581103] PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100002)
May 26 17:08:32 tarm kernel: [  390.581126] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:08:32 tarm kernel: [  390.581133] PCI: Setting latency timer of device 0000:00:1b.0 to 64
May 26 17:08:32 tarm kernel: [  390.637242] PM: Writing back config space on device 0000:00:1c.0 at offset 1 (was 100107, writing 100507)
May 26 17:08:32 tarm kernel: [  390.637328] PCI: Setting latency timer of device 0000:00:1c.0 to 64
May 26 17:08:32 tarm kernel: [  390.637410] PM: Writing back config space on device 0000:00:1c.1 at offset 1 (was 100107, writing 100507)
May 26 17:08:32 tarm kernel: [  390.637505] PCI: Setting latency timer of device 0000:00:1c.1 to 64
May 26 17:08:32 tarm kernel: [  390.637577] PM: Writing back config space on device 0000:00:1c.2 at offset 1 (was 100107, writing 100507)
May 26 17:08:32 tarm kernel: [  390.637674] PCI: Setting latency timer of device 0000:00:1c.2 to 64
May 26 17:08:32 tarm kernel: [  390.637755] PM: Writing back config space on device 0000:00:1c.3 at offset 1 (was 100107, writing 100507)
May 26 17:08:32 tarm kernel: [  390.637840] PCI: Setting latency timer of device 0000:00:1c.3 to 64
May 26 17:08:32 tarm kernel: [  390.637862] PM: Writing back config space on device 0000:00:1d.0 at offset f (was 100, writing 10b)
May 26 17:08:32 tarm kernel: [  390.637928] PM: Writing back config space on device 0000:00:1d.1 at offset f (was 200, writing 20b)
May 26 17:08:32 tarm kernel: [  390.637994] PM: Writing back config space on device 0000:00:1d.2 at offset f (was 300, writing 30b)
May 26 17:08:32 tarm kernel: [  390.638070] PM: Writing back config space on device 0000:00:1d.3 at offset f (was 400, writing 40b)
May 26 17:08:32 tarm kernel: [  390.638153] PM: Writing back config space on device 0000:00:1d.7 at offset f (was 400, writing 40b)
May 26 17:08:32 tarm kernel: [  390.638197] PM: Writing back config space on device 0000:00:1d.7 at offset 4 (was 0, writing b0004000)
May 26 17:08:32 tarm kernel: [  390.638210] PM: Writing back config space on device 0000:00:1d.7 at offset 1 (was 2900000, writing 2900102)
May 26 17:08:32 tarm kernel: [  390.638278] PCI: Setting latency timer of device 0000:00:1e.0 to 64
May 26 17:08:32 tarm kernel: [  390.653060] PM: Writing back config space on device 0000:00:1f.2 at offset 1 (was 2b00005, writing 2b80005)
May 26 17:08:32 tarm kernel: [  390.653088] PCI: Setting latency timer of device 0000:00:1f.2 to 64
May 26 17:08:32 tarm kernel: [  390.657638] PM: Writing back config space on device 0000:01:00.0 at offset 1 (was 100103, writing 100107)
May 26 17:08:32 tarm kernel: [  390.657780] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:08:32 tarm kernel: [  390.657790] PCI: Setting latency timer of device 0000:01:00.0 to 64
May 26 17:08:32 tarm kernel: [  390.657836] PM: Writing back config space on device 0000:02:00.0 at offset c (was 0, writing f4ff0000)
May 26 17:08:32 tarm kernel: [  390.657869] PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 100106)
May 26 17:08:32 tarm kernel: [  390.993061] PM: Writing back config space on device 0000:14:00.1 at offset 4 (was 0, writing c0001000)
May 26 17:08:32 tarm kernel: [  390.993073] PM: Writing back config space on device 0000:14:00.1 at offset 3 (was 800000, writing 804000)
May 26 17:08:32 tarm kernel: [  390.993086] PM: Writing back config space on device 0000:14:00.1 at offset 1 (was 2100000, writing 2100106)
May 26 17:08:32 tarm kernel: [  391.009856] ata2.00: ACPI cmd ef/03:42:00:00:00:a0 filtered out
May 26 17:08:32 tarm kernel: [  391.009864] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
May 26 17:08:32 tarm kernel: [  391.017888] ata2.00: ACPI cmd e3/00:10:00:00:00:a0 succeeded
May 26 17:08:32 tarm kernel: [  391.025904] ata2.00: ACPI cmd e3/00:03:00:00:00:a0 succeeded
May 26 17:08:32 tarm kernel: [  391.047869] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17]  MMIO=[c0001000-c00017ff]  Max Packet=[2048]  IR/IT contexts=[4/4]
May 26 17:08:32 tarm kernel: [  391.050421] ata2.00: configured for UDMA/33
May 26 17:08:32 tarm kernel: [  391.073461] PM: Writing back config space on device 0000:14:00.2 at offset 4 (was 0, writing c0001800)
May 26 17:08:32 tarm kernel: [  391.073472] PM: Writing back config space on device 0000:14:00.2 at offset 3 (was 800000, writing 804000)
May 26 17:08:32 tarm kernel: [  391.073484] PM: Writing back config space on device 0000:14:00.2 at offset 1 (was 2100000, writing 2100106)
May 26 17:08:32 tarm kernel: [  391.073512] ACPI: PCI Interrupt 0000:14:00.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 17:08:32 tarm kernel: [  391.074571] eth1: Coming out of suspend...
May 26 17:08:32 tarm kernel: [  391.096419] ACPI: PCI Interrupt 0000:14:02.0[A] -> GSI 21 (level, low) -> IRQ 21
May 26 17:08:32 tarm kernel: [  391.098552] nsc-ircc 00:09: activated
May 26 17:08:32 tarm kernel: [  392.015855] sd 0:0:0:0: [sda] Starting disk
May 26 17:08:32 tarm kernel: [  392.325719] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 succeeded
May 26 17:08:32 tarm kernel: [  392.325726] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
May 26 17:08:32 tarm kernel: [  392.325733] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 filtered out
May 26 17:08:32 tarm kernel: [  392.325739] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
May 26 17:08:32 tarm kernel: [  392.326166] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 succeeded
May 26 17:08:32 tarm kernel: [  392.349666] ata1.00: configured for UDMA/100
May 26 17:08:32 tarm kernel: [  392.373671] ata1.00: configured for UDMA/100
May 26 17:08:32 tarm kernel: [  392.373677] ata1: EH complete
May 26 17:08:32 tarm kernel: [  392.373769] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
May 26 17:08:32 tarm kernel: [  392.373812] sd 0:0:0:0: [sda] Write Protect is off
May 26 17:08:32 tarm kernel: [  392.373818] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 26 17:08:32 tarm kernel: [  392.373891] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 26 17:08:32 tarm kernel: [  392.373963] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
May 26 17:08:32 tarm kernel: [  392.374002] sd 0:0:0:0: [sda] Write Protect is off
May 26 17:08:32 tarm kernel: [  392.374007] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 26 17:08:32 tarm kernel: [  392.374079] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 26 17:08:32 tarm kernel: [  395.076118] hdaps: initial latch check good (0x01).
May 26 17:08:32 tarm kernel: [  395.281513] Restarting tasks ... done.
May 26 17:08:32 tarm kernel: [  395.386376] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 19
May 26 17:08:32 tarm kernel: [  395.386665] PCI: Setting latency timer of device 0000:00:1d.7 to 64
May 26 17:08:32 tarm kernel: [  395.386808] ehci_hcd 0000:00:1d.7: EHCI Host Controller
May 26 17:08:32 tarm kernel: [  395.431301] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
May 26 17:08:32 tarm kernel: [  395.436500] ehci_hcd 0000:00:1d.7: debug port 1
May 26 17:08:32 tarm kernel: [  395.436653] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
May 26 17:08:32 tarm kernel: [  395.436811] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xb0004000
May 26 17:08:32 tarm kernel: [  395.449033] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
May 26 17:08:32 tarm kernel: [  395.449494] usb usb1: configuration #1 chosen from 1 choice
May 26 17:08:32 tarm kernel: [  395.450112] hub 1-0:1.0: USB hub found
May 26 17:08:32 tarm kernel: [  395.453020] hub 1-0:1.0: 8 ports detected
May 26 17:08:32 tarm kernel: [  395.557146] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
May 26 17:08:32 tarm kernel: [  395.557389] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:08:32 tarm kernel: [  395.557517] usb usb1: Product: EHCI Host Controller
May 26 17:08:32 tarm kernel: [  395.557635] usb usb1: Manufacturer: Linux 2.6.26-rc3 ehci_hcd
May 26 17:08:32 tarm kernel: [  395.557751] usb usb1: SerialNumber: 0000:00:1d.7
May 26 17:08:32 tarm kernel: [  395.568587] USB Universal Host Controller Interface driver v3.0
May 26 17:08:32 tarm kernel: [  395.568671] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:08:32 tarm kernel: [  395.568691] PCI: Setting latency timer of device 0000:00:1d.0 to 64
May 26 17:08:32 tarm kernel: [  395.568699] uhci_hcd 0000:00:1d.0: UHCI Host Controller
May 26 17:08:32 tarm kernel: [  395.568757] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
May 26 17:08:32 tarm kernel: [  395.568794] uhci_hcd 0000:00:1d.0: irq 16, io base 0x00001800
May 26 17:08:32 tarm kernel: [  395.569035] usb usb2: configuration #1 chosen from 1 choice
May 26 17:08:32 tarm kernel: [  395.569099] hub 2-0:1.0: USB hub found
May 26 17:08:32 tarm kernel: [  395.569114] hub 2-0:1.0: 2 ports detected
May 26 17:08:32 tarm kernel: [  395.627759] __ratelimit: 46 messages suppressed
May 26 17:08:32 tarm kernel: [  395.627959] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:08:32 tarm kernel: [  395.674509] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:08:32 tarm kernel: [  395.674516] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:08:32 tarm kernel: [  395.674519] usb usb2: Product: UHCI Host Controller
May 26 17:08:32 tarm kernel: [  395.674521] usb usb2: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:08:32 tarm kernel: [  395.674523] usb usb2: SerialNumber: 0000:00:1d.0
May 26 17:08:32 tarm kernel: [  395.674552] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 17
May 26 17:08:32 tarm kernel: [  395.674564] PCI: Setting latency timer of device 0000:00:1d.1 to 64
May 26 17:08:32 tarm kernel: [  395.674568] uhci_hcd 0000:00:1d.1: UHCI Host Controller
May 26 17:08:32 tarm kernel: [  395.674592] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
May 26 17:08:32 tarm kernel: [  395.674619] uhci_hcd 0000:00:1d.1: irq 17, io base 0x00001820
May 26 17:08:32 tarm kernel: [  395.674724] usb usb3: configuration #1 chosen from 1 choice
May 26 17:08:32 tarm kernel: [  395.674753] hub 3-0:1.0: USB hub found
May 26 17:08:32 tarm kernel: [  395.674759] hub 3-0:1.0: 2 ports detected
May 26 17:08:32 tarm kernel: [  395.749009] hub 1-0:1.0: unable to enumerate USB device on port 3
May 26 17:08:32 tarm kernel: [  395.777062] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:08:32 tarm kernel: [  395.777941] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:08:32 tarm kernel: [  395.778017] usb usb3: Product: UHCI Host Controller
May 26 17:08:32 tarm kernel: [  395.778070] usb usb3: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:08:32 tarm kernel: [  395.778121] usb usb3: SerialNumber: 0000:00:1d.1
May 26 17:08:32 tarm kernel: [  395.778204] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 17:08:32 tarm kernel: [  395.778287] PCI: Setting latency timer of device 0000:00:1d.2 to 64
May 26 17:08:32 tarm kernel: [  395.778580] uhci_hcd 0000:00:1d.2: UHCI Host Controller
May 26 17:08:32 tarm kernel: [  395.778659] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
May 26 17:08:32 tarm kernel: [  395.778738] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001840
May 26 17:08:32 tarm kernel: [  395.778895] usb usb4: configuration #1 chosen from 1 choice
May 26 17:08:32 tarm kernel: [  395.778978] hub 4-0:1.0: USB hub found
May 26 17:08:32 tarm kernel: [  395.779034] hub 4-0:1.0: 2 ports detected
May 26 17:08:33 tarm kernel: [  395.881086] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:08:33 tarm kernel: [  395.882354] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:08:33 tarm kernel: [  395.882435] usb usb4: Product: UHCI Host Controller
May 26 17:08:33 tarm kernel: [  395.882488] usb usb4: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:08:33 tarm kernel: [  395.882539] usb usb4: SerialNumber: 0000:00:1d.2
May 26 17:08:33 tarm kernel: [  395.882621] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 19
May 26 17:08:33 tarm kernel: [  395.882705] PCI: Setting latency timer of device 0000:00:1d.3 to 64
May 26 17:08:33 tarm kernel: [  395.882769] uhci_hcd 0000:00:1d.3: UHCI Host Controller
May 26 17:08:33 tarm kernel: [  395.882850] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
May 26 17:08:33 tarm kernel: [  395.882929] uhci_hcd 0000:00:1d.3: irq 19, io base 0x00001860
May 26 17:08:33 tarm kernel: [  395.883100] usb usb5: configuration #1 chosen from 1 choice
May 26 17:08:33 tarm kernel: [  395.883184] hub 5-0:1.0: USB hub found
May 26 17:08:33 tarm kernel: [  395.883241] hub 5-0:1.0: 2 ports detected
May 26 17:08:33 tarm kernel: [  395.985064] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:08:33 tarm kernel: [  395.986151] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:08:33 tarm kernel: [  395.986229] usb usb5: Product: UHCI Host Controller
May 26 17:08:33 tarm kernel: [  395.986281] usb usb5: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:08:33 tarm kernel: [  395.986333] usb usb5: SerialNumber: 0000:00:1d.3
May 26 17:08:33 tarm kernel: [  395.989846] hub 1-0:1.0: unable to enumerate USB device on port 5
May 26 17:08:33 tarm kernel: [  396.108565] [drm] Loading R300 Microcode
May 26 17:08:33 tarm kernel: [  396.229007] hub 1-0:1.0: unable to enumerate USB device on port 6
May 26 17:08:33 tarm kernel: [  396.469536] usb 3-1: new low speed USB device using uhci_hcd and address 2
May 26 17:08:34 tarm kernel: [  396.650560] usb 3-1: configuration #1 chosen from 1 choice
May 26 17:08:34 tarm kernel: [  396.680441] input: Logitech Trackball as /class/input/input15
May 26 17:08:34 tarm kernel: [  396.717720] input,hidraw0: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:1d.1-1
May 26 17:08:34 tarm kernel: [  396.718015] usb 3-1: New USB device found, idVendor=046d, idProduct=c404
May 26 17:08:34 tarm kernel: [  396.718082] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:08:34 tarm kernel: [  396.718144] usb 3-1: Product: Trackball
May 26 17:08:34 tarm kernel: [  396.718201] usb 3-1: Manufacturer: Logitech
May 26 17:08:34 tarm kernel: [  396.956990] usb 4-1: new full speed USB device using uhci_hcd and address 2
May 26 17:08:34 tarm kernel: [  397.135654] usb 4-1: configuration #1 chosen from 1 choice
May 26 17:08:34 tarm kernel: [  397.140242] usb 4-1: New USB device found, idVendor=0a5c, idProduct=2110
May 26 17:08:34 tarm kernel: [  397.140318] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:08:34 tarm kernel: [  397.140379] usb 4-1: Product: BCM2045B
May 26 17:08:34 tarm kernel: [  397.140435] usb 4-1: Manufacturer: Broadcom Corp
May 26 17:08:34 tarm kernel: [  397.385029] usb 4-2: new full speed USB device using uhci_hcd and address 3
May 26 17:08:34 tarm kernel: [  397.457527] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 17:08:34 tarm kernel: [  397.465569] pan1: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 17:08:35 tarm kernel: [  397.763494] usb 4-2: configuration #1 chosen from 1 choice
May 26 17:08:35 tarm kernel: [  397.768596] usb 4-2: New USB device found, idVendor=0483, idProduct=2016
May 26 17:08:35 tarm kernel: [  397.769080] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:08:35 tarm kernel: [  397.769150] usb 4-2: Product: Biometric Coprocessor
May 26 17:08:35 tarm kernel: [  397.769199] usb 4-2: Manufacturer: STMicroelectronics
May 26 17:08:36 tarm kernel: [  399.389868] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 26 17:08:37 tarm kernel: [  400.124987] __ratelimit: 44 messages suppressed
May 26 17:08:37 tarm kernel: [  400.125122] cpufreq-core: target for CPU 0: 571428 kHz, relation 0
May 26 17:08:42 tarm kernel: [  405.234652] ADDRCONF(NETDEV_UP): eth1: link is not ready
May 26 17:08:43 tarm kernel: [  405.625001] __ratelimit: 20 messages suppressed
May 26 17:08:43 tarm kernel: [  405.625197] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:08:43 tarm kernel: [  406.155271] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
May 26 17:08:49 tarm kernel: [  411.836137] tun0: Disabled Privacy Extensions
May 26 17:08:49 tarm kernel: [  412.125004] __ratelimit: 13 messages suppressed
May 26 17:08:49 tarm kernel: [  412.125234] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:08:53 tarm kernel: [  416.156982] eth1: no IPv6 routers present
May 26 17:08:58 tarm kernel: [  420.625017] __ratelimit: 20 messages suppressed
May 26 17:08:58 tarm kernel: [  420.625261] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:08:58 tarm kernel: [  420.625405] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:09:09 tarm kernel: [  431.625006] __ratelimit: 12 messages suppressed
May 26 17:09:09 tarm kernel: [  431.625024] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:09:09 tarm kernel: [  431.625033] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:09:09 tarm kernel: [  432.106648] ehci_hcd 0000:00:1d.7: remove, state 4
May 26 17:09:09 tarm kernel: [  432.106662] usb usb1: USB disconnect, address 1
May 26 17:09:09 tarm kernel: [  432.129147] ehci_hcd 0000:00:1d.7: USB bus 1 deregistered
May 26 17:09:09 tarm kernel: [  432.129358] ACPI: PCI interrupt for device 0000:00:1d.7 disabled
May 26 17:09:09 tarm kernel: [  432.130197] uhci_hcd 0000:00:1d.3: remove, state 4
May 26 17:09:09 tarm kernel: [  432.130209] usb usb5: USB disconnect, address 1
May 26 17:09:09 tarm kernel: [  432.130403] uhci_hcd 0000:00:1d.3: USB bus 5 deregistered
May 26 17:09:09 tarm kernel: [  432.130431] ACPI: PCI interrupt for device 0000:00:1d.3 disabled
May 26 17:09:09 tarm kernel: [  432.130441] uhci_hcd 0000:00:1d.2: remove, state 1
May 26 17:09:09 tarm kernel: [  432.130448] usb usb4: USB disconnect, address 1
May 26 17:09:09 tarm kernel: [  432.130450] usb 4-1: USB disconnect, address 2
May 26 17:09:09 tarm kernel: [  432.390092] usb 4-2: USB disconnect, address 3
May 26 17:09:09 tarm kernel: [  432.392457] uhci_hcd 0000:00:1d.2: USB bus 4 deregistered
May 26 17:09:09 tarm kernel: [  432.392601] ACPI: PCI interrupt for device 0000:00:1d.2 disabled
May 26 17:09:09 tarm kernel: [  432.392669] uhci_hcd 0000:00:1d.1: remove, state 1
May 26 17:09:09 tarm kernel: [  432.392728] usb usb3: USB disconnect, address 1
May 26 17:09:09 tarm kernel: [  432.392779] usb 3-1: USB disconnect, address 2
May 26 17:09:09 tarm kernel: [  432.413423] uhci_hcd 0000:00:1d.1: USB bus 3 deregistered
May 26 17:09:09 tarm kernel: [  432.413615] ACPI: PCI interrupt for device 0000:00:1d.1 disabled
May 26 17:09:09 tarm kernel: [  432.413700] uhci_hcd 0000:00:1d.0: remove, state 4
May 26 17:09:09 tarm kernel: [  432.413710] usb usb2: USB disconnect, address 1
May 26 17:09:09 tarm kernel: [  432.413883] uhci_hcd 0000:00:1d.0: USB bus 2 deregistered
May 26 17:09:09 tarm kernel: [  432.413911] ACPI: PCI interrupt for device 0000:00:1d.0 disabled
May 26 17:09:11 tarm kernel: [  434.070883] PM: Syncing filesystems ... done.
May 26 17:09:29 tarm kernel: [  434.175318] Freezing user space processes ... (elapsed 0.00 seconds) done.
May 26 17:09:29 tarm kernel: [  434.176725] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
May 26 17:09:29 tarm kernel: [  434.176924] Suspending console(s)
May 26 17:09:29 tarm kernel: [  434.388778] sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 26 17:09:29 tarm kernel: [  434.388828] sd 0:0:0:0: [sda] Stopping disk
May 26 17:09:29 tarm kernel: [  434.836986] __ratelimit: 19 messages suppressed
May 26 17:09:29 tarm kernel: [  434.836988] cpufreq-core: target for CPU 0: 285714 kHz, relation 0
May 26 17:09:29 tarm kernel: [  435.841790] nsc-ircc 00:09: disabled
May 26 17:09:29 tarm kernel: [  435.841980] eth1: Going into suspend...
May 26 17:09:29 tarm kernel: [  435.847145] ACPI: PCI interrupt for device 0000:14:02.0 disabled
May 26 17:09:29 tarm kernel: [  435.847156] ACPI handle has no context!
May 26 17:09:29 tarm kernel: [  435.862140] ACPI handle has no context!
May 26 17:09:29 tarm kernel: [  435.862169] ACPI: PCI interrupt for device 0000:14:00.2 disabled
May 26 17:09:29 tarm kernel: [  435.862179] ACPI handle has no context!
May 26 17:09:29 tarm kernel: [  435.882079] ACPI handle has no context!
May 26 17:09:29 tarm kernel: [  436.038608] ACPI handle has no context!
May 26 17:09:29 tarm kernel: [  436.257053] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
May 26 17:09:29 tarm kernel: [  436.276712] ACPI: Preparing to enter system sleep state S3
May 26 17:09:29 tarm kernel: [  436.289286] Extended CMOS year: 2000
May 26 17:09:29 tarm kernel: [  436.289286] Intel machine check architecture supported.
May 26 17:09:29 tarm kernel: [  436.289302] Intel machine check reporting enabled on CPU#0.
May 26 17:09:29 tarm kernel: [  436.289403] Back to C!
May 26 17:09:29 tarm kernel: [  436.289697] Extended CMOS year: 2000
May 26 17:09:29 tarm kernel: [  436.289703] Force enabled HPET at resume
May 26 17:09:29 tarm kernel: [  436.289878] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:09:29 tarm kernel: [  436.289880] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:09:29 tarm kernel: [  436.289883] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:09:29 tarm kernel: [  436.289886] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:09:29 tarm kernel: [  436.289890] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:09:29 tarm kernel: [  436.289893] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:09:29 tarm kernel: [  436.289895] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:09:29 tarm kernel: [  436.289898] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 17:09:29 tarm kernel: [  436.289900] cpufreq-core: governor: change or update limits
May 26 17:09:29 tarm kernel: [  436.289903] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:09:29 tarm kernel: [  436.349423] PM: Writing back config space on device 0000:00:01.0 at offset 1 (was 100107, writing 100507)
May 26 17:09:29 tarm kernel: [  436.349423] PCI: Setting latency timer of device 0000:00:01.0 to 64
May 26 17:09:29 tarm kernel: [  436.365016] PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100002)
May 26 17:09:29 tarm kernel: [  436.365040] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:09:29 tarm kernel: [  436.365046] PCI: Setting latency timer of device 0000:00:1b.0 to 64
May 26 17:09:29 tarm kernel: [  436.421172] PM: Writing back config space on device 0000:00:1c.0 at offset 1 (was 100107, writing 100507)
May 26 17:09:29 tarm kernel: [  436.421245] PCI: Setting latency timer of device 0000:00:1c.0 to 64
May 26 17:09:29 tarm kernel: [  436.421296] PM: Writing back config space on device 0000:00:1c.1 at offset 1 (was 100107, writing 100507)
May 26 17:09:29 tarm kernel: [  436.421369] PCI: Setting latency timer of device 0000:00:1c.1 to 64
May 26 17:09:29 tarm kernel: [  436.421420] PM: Writing back config space on device 0000:00:1c.2 at offset 1 (was 100107, writing 100507)
May 26 17:09:29 tarm kernel: [  436.421483] PCI: Setting latency timer of device 0000:00:1c.2 to 64
May 26 17:09:29 tarm kernel: [  436.421544] PM: Writing back config space on device 0000:00:1c.3 at offset 1 (was 100107, writing 100507)
May 26 17:09:29 tarm kernel: [  436.421607] PCI: Setting latency timer of device 0000:00:1c.3 to 64
May 26 17:09:29 tarm kernel: [  436.421623] PM: Writing back config space on device 0000:00:1d.0 at offset f (was 100, writing 10b)
May 26 17:09:29 tarm kernel: [  436.421669] PM: Writing back config space on device 0000:00:1d.1 at offset f (was 200, writing 20b)
May 26 17:09:29 tarm kernel: [  436.421724] PM: Writing back config space on device 0000:00:1d.2 at offset f (was 300, writing 30b)
May 26 17:09:29 tarm kernel: [  436.421770] PM: Writing back config space on device 0000:00:1d.3 at offset f (was 400, writing 40b)
May 26 17:09:29 tarm kernel: [  436.421832] PM: Writing back config space on device 0000:00:1d.7 at offset f (was 400, writing 40b)
May 26 17:09:29 tarm kernel: [  436.421859] PM: Writing back config space on device 0000:00:1d.7 at offset 4 (was 0, writing b0004000)
May 26 17:09:29 tarm kernel: [  436.421876] PM: Writing back config space on device 0000:00:1d.7 at offset 1 (was 2900000, writing 2900102)
May 26 17:09:29 tarm kernel: [  436.421976] PCI: Setting latency timer of device 0000:00:1e.0 to 64
May 26 17:09:29 tarm kernel: [  436.437045] PM: Writing back config space on device 0000:00:1f.2 at offset 1 (was 2b00005, writing 2b80005)
May 26 17:09:29 tarm kernel: [  436.437064] PCI: Setting latency timer of device 0000:00:1f.2 to 64
May 26 17:09:29 tarm kernel: [  436.439261] PM: Writing back config space on device 0000:01:00.0 at offset 1 (was 100103, writing 100107)
May 26 17:09:29 tarm kernel: [  436.439325] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:09:29 tarm kernel: [  436.439330] PCI: Setting latency timer of device 0000:01:00.0 to 64
May 26 17:09:29 tarm kernel: [  436.439367] PM: Writing back config space on device 0000:02:00.0 at offset c (was 0, writing fcff0000)
May 26 17:09:29 tarm kernel: [  436.439393] PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 100106)
May 26 17:09:29 tarm kernel: [  436.777257] PM: Writing back config space on device 0000:14:00.1 at offset 4 (was 0, writing c0001000)
May 26 17:09:29 tarm kernel: [  436.777264] PM: Writing back config space on device 0000:14:00.1 at offset 3 (was 800000, writing 804000)
May 26 17:09:29 tarm kernel: [  436.777272] PM: Writing back config space on device 0000:14:00.1 at offset 1 (was 2100000, writing 2100106)
May 26 17:09:29 tarm kernel: [  436.789823] ata2.00: ACPI cmd ef/03:42:00:00:00:a0 filtered out
May 26 17:09:29 tarm kernel: [  436.789826] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
May 26 17:09:29 tarm kernel: [  436.797829] ata2.00: ACPI cmd e3/00:10:00:00:00:a0 succeeded
May 26 17:09:29 tarm kernel: [  436.805832] ata2.00: ACPI cmd e3/00:03:00:00:00:a0 succeeded
May 26 17:09:29 tarm kernel: [  436.830164] ata2.00: configured for UDMA/33
May 26 17:09:29 tarm kernel: [  436.832182] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17]  MMIO=[c0001000-c00017ff]  Max Packet=[2048]  IR/IT contexts=[4/4]
May 26 17:09:29 tarm kernel: [  436.857195] PM: Writing back config space on device 0000:14:00.2 at offset 4 (was 0, writing c0001800)
May 26 17:09:29 tarm kernel: [  436.857201] PM: Writing back config space on device 0000:14:00.2 at offset 3 (was 800000, writing 804000)
May 26 17:09:29 tarm kernel: [  436.857208] PM: Writing back config space on device 0000:14:00.2 at offset 1 (was 2100000, writing 2100106)
May 26 17:09:29 tarm kernel: [  436.857228] ACPI: PCI Interrupt 0000:14:00.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 17:09:29 tarm kernel: [  436.858272] eth1: Coming out of suspend...
May 26 17:09:29 tarm kernel: [  436.880121] ACPI: PCI Interrupt 0000:14:02.0[A] -> GSI 21 (level, low) -> IRQ 21
May 26 17:09:29 tarm kernel: [  436.880863] nsc-ircc 00:09: activated
May 26 17:09:29 tarm kernel: [  437.816800] sd 0:0:0:0: [sda] Starting disk
May 26 17:09:29 tarm kernel: [  438.273716] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 succeeded
May 26 17:09:29 tarm kernel: [  438.273723] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
May 26 17:09:29 tarm kernel: [  438.273730] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 filtered out
May 26 17:09:29 tarm kernel: [  438.273736] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
May 26 17:09:29 tarm kernel: [  438.274160] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 succeeded
May 26 17:09:29 tarm kernel: [  438.297669] ata1.00: configured for UDMA/100
May 26 17:09:29 tarm kernel: [  438.321673] ata1.00: configured for UDMA/100
May 26 17:09:29 tarm kernel: [  438.321680] ata1: EH complete
May 26 17:09:29 tarm kernel: [  438.321772] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
May 26 17:09:29 tarm kernel: [  438.321814] sd 0:0:0:0: [sda] Write Protect is off
May 26 17:09:29 tarm kernel: [  438.321820] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 26 17:09:29 tarm kernel: [  438.321892] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 26 17:09:29 tarm kernel: [  438.321963] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
May 26 17:09:29 tarm kernel: [  438.322002] sd 0:0:0:0: [sda] Write Protect is off
May 26 17:09:29 tarm kernel: [  438.322008] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 26 17:09:29 tarm kernel: [  438.322078] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 26 17:09:29 tarm kernel: [  441.032641] hdaps: initial latch check good (0x01).
May 26 17:09:29 tarm kernel: [  443.277512] Restarting tasks ... done.
May 26 17:09:29 tarm kernel: [  443.381823] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 19
May 26 17:09:29 tarm kernel: [  443.382092] PCI: Setting latency timer of device 0000:00:1d.7 to 64
May 26 17:09:29 tarm kernel: [  443.382235] ehci_hcd 0000:00:1d.7: EHCI Host Controller
May 26 17:09:29 tarm kernel: [  443.432880] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
May 26 17:09:29 tarm kernel: [  443.439143] ehci_hcd 0000:00:1d.7: debug port 1
May 26 17:09:29 tarm kernel: [  443.439288] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
May 26 17:09:29 tarm kernel: [  443.439445] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xb0004000
May 26 17:09:29 tarm kernel: [  443.453032] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
May 26 17:09:29 tarm kernel: [  443.453463] usb usb1: configuration #1 chosen from 1 choice
May 26 17:09:29 tarm kernel: [  443.459343] hub 1-0:1.0: USB hub found
May 26 17:09:29 tarm kernel: [  443.459486] hub 1-0:1.0: 8 ports detected
May 26 17:09:30 tarm kernel: [  443.574958] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
May 26 17:09:30 tarm kernel: [  443.574970] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:09:30 tarm kernel: [  443.574977] usb usb1: Product: EHCI Host Controller
May 26 17:09:30 tarm kernel: [  443.574983] usb usb1: Manufacturer: Linux 2.6.26-rc3 ehci_hcd
May 26 17:09:30 tarm kernel: [  443.574989] usb usb1: SerialNumber: 0000:00:1d.7
May 26 17:09:30 tarm kernel: [  443.590571] USB Universal Host Controller Interface driver v3.0
May 26 17:09:30 tarm kernel: [  443.590651] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:09:30 tarm kernel: [  443.590672] PCI: Setting latency timer of device 0000:00:1d.0 to 64
May 26 17:09:30 tarm kernel: [  443.590680] uhci_hcd 0000:00:1d.0: UHCI Host Controller
May 26 17:09:30 tarm kernel: [  443.590741] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
May 26 17:09:30 tarm kernel: [  443.590778] uhci_hcd 0000:00:1d.0: irq 16, io base 0x00001800
May 26 17:09:30 tarm kernel: [  443.591005] usb usb2: configuration #1 chosen from 1 choice
May 26 17:09:30 tarm kernel: [  443.591070] hub 2-0:1.0: USB hub found
May 26 17:09:30 tarm kernel: [  443.591084] hub 2-0:1.0: 2 ports detected
May 26 17:09:30 tarm kernel: [  443.625067] __ratelimit: 45 messages suppressed
May 26 17:09:30 tarm kernel: [  443.625263] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:09:30 tarm kernel: [  443.693056] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:09:30 tarm kernel: [  443.694024] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:09:30 tarm kernel: [  443.694113] usb usb2: Product: UHCI Host Controller
May 26 17:09:30 tarm kernel: [  443.694166] usb usb2: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:09:30 tarm kernel: [  443.694217] usb usb2: SerialNumber: 0000:00:1d.0
May 26 17:09:30 tarm kernel: [  443.694298] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 17
May 26 17:09:30 tarm kernel: [  443.694381] PCI: Setting latency timer of device 0000:00:1d.1 to 64
May 26 17:09:30 tarm kernel: [  443.694444] uhci_hcd 0000:00:1d.1: UHCI Host Controller
May 26 17:09:30 tarm kernel: [  443.694523] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
May 26 17:09:30 tarm kernel: [  443.694603] uhci_hcd 0000:00:1d.1: irq 17, io base 0x00001820
May 26 17:09:30 tarm kernel: [  443.694759] usb usb3: configuration #1 chosen from 1 choice
May 26 17:09:30 tarm kernel: [  443.694841] hub 3-0:1.0: USB hub found
May 26 17:09:30 tarm kernel: [  443.694897] hub 3-0:1.0: 2 ports detected
May 26 17:09:30 tarm kernel: [  443.773483] hub 1-0:1.0: unable to enumerate USB device on port 3
May 26 17:09:30 tarm kernel: [  443.797077] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:09:30 tarm kernel: [  443.797969] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:09:30 tarm kernel: [  443.798042] usb usb3: Product: UHCI Host Controller
May 26 17:09:30 tarm kernel: [  443.798094] usb usb3: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:09:30 tarm kernel: [  443.798144] usb usb3: SerialNumber: 0000:00:1d.1
May 26 17:09:30 tarm kernel: [  443.798225] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 17:09:30 tarm kernel: [  443.798307] PCI: Setting latency timer of device 0000:00:1d.2 to 64
May 26 17:09:30 tarm kernel: [  443.798371] uhci_hcd 0000:00:1d.2: UHCI Host Controller
May 26 17:09:30 tarm kernel: [  443.798449] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
May 26 17:09:30 tarm kernel: [  443.798528] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001840
May 26 17:09:30 tarm kernel: [  443.798683] usb usb4: configuration #1 chosen from 1 choice
May 26 17:09:30 tarm kernel: [  443.798766] hub 4-0:1.0: USB hub found
May 26 17:09:30 tarm kernel: [  443.798821] hub 4-0:1.0: 2 ports detected
May 26 17:09:30 tarm kernel: [  443.901079] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:09:30 tarm kernel: [  443.902034] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:09:30 tarm kernel: [  443.902109] usb usb4: Product: UHCI Host Controller
May 26 17:09:30 tarm kernel: [  443.902161] usb usb4: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:09:30 tarm kernel: [  443.902212] usb usb4: SerialNumber: 0000:00:1d.2
May 26 17:09:30 tarm kernel: [  443.902293] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 19
May 26 17:09:30 tarm kernel: [  443.902376] PCI: Setting latency timer of device 0000:00:1d.3 to 64
May 26 17:09:30 tarm kernel: [  443.902440] uhci_hcd 0000:00:1d.3: UHCI Host Controller
May 26 17:09:30 tarm kernel: [  443.902520] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
May 26 17:09:30 tarm kernel: [  443.902599] uhci_hcd 0000:00:1d.3: irq 19, io base 0x00001860
May 26 17:09:30 tarm kernel: [  443.902757] usb usb5: configuration #1 chosen from 1 choice
May 26 17:09:30 tarm kernel: [  443.902839] hub 5-0:1.0: USB hub found
May 26 17:09:30 tarm kernel: [  443.902895] hub 5-0:1.0: 2 ports detected
May 26 17:09:30 tarm kernel: [  444.006372] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:09:30 tarm kernel: [  444.006498] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:09:30 tarm kernel: [  444.006553] usb usb5: Product: UHCI Host Controller
May 26 17:09:30 tarm kernel: [  444.006604] usb usb5: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:09:30 tarm kernel: [  444.006654] usb usb5: SerialNumber: 0000:00:1d.3
May 26 17:09:30 tarm kernel: [  444.021071] hub 1-0:1.0: unable to enumerate USB device on port 5
May 26 17:09:30 tarm kernel: [  444.109142] [drm] Loading R300 Microcode
May 26 17:09:30 tarm kernel: [  444.261006] hub 1-0:1.0: unable to enumerate USB device on port 6
May 26 17:09:31 tarm kernel: [  444.500994] usb 3-1: new low speed USB device using uhci_hcd and address 2
May 26 17:09:31 tarm kernel: [  444.684966] usb 3-1: configuration #1 chosen from 1 choice
May 26 17:09:31 tarm kernel: [  444.711667] input: Logitech Trackball as /class/input/input16
May 26 17:09:31 tarm kernel: [  444.737121] input,hidraw0: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:1d.1-1
May 26 17:09:31 tarm kernel: [  444.737514] usb 3-1: New USB device found, idVendor=046d, idProduct=c404
May 26 17:09:31 tarm kernel: [  444.737592] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:09:31 tarm kernel: [  444.737663] usb 3-1: Product: Trackball
May 26 17:09:31 tarm kernel: [  444.737729] usb 3-1: Manufacturer: Logitech
May 26 17:09:31 tarm kernel: [  444.977628] usb 4-1: new full speed USB device using uhci_hcd and address 2
May 26 17:09:31 tarm kernel: [  445.159634] usb 4-1: configuration #1 chosen from 1 choice
May 26 17:09:31 tarm kernel: [  445.174640] usb 4-1: New USB device found, idVendor=0a5c, idProduct=2110
May 26 17:09:31 tarm kernel: [  445.175417] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:09:31 tarm kernel: [  445.175499] usb 4-1: Product: BCM2045B
May 26 17:09:31 tarm kernel: [  445.175565] usb 4-1: Manufacturer: Broadcom Corp
May 26 17:09:32 tarm kernel: [  445.413073] usb 4-2: new full speed USB device using uhci_hcd and address 3
May 26 17:09:32 tarm kernel: [  445.625078] __ratelimit: 13 messages suppressed
May 26 17:09:32 tarm kernel: [  445.625225] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:09:32 tarm kernel: [  445.708905] usb 4-2: configuration #1 chosen from 1 choice
May 26 17:09:32 tarm kernel: [  445.711683] usb 4-2: New USB device found, idVendor=0483, idProduct=2016
May 26 17:09:32 tarm kernel: [  445.711746] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:09:32 tarm kernel: [  445.711798] usb 4-2: Product: Biometric Coprocessor
May 26 17:09:32 tarm kernel: [  445.711847] usb 4-2: Manufacturer: STMicroelectronics
May 26 17:09:32 tarm kernel: [  445.782302] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 17:09:32 tarm kernel: [  445.783182] pan1: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 17:09:33 tarm kernel: [  447.252710] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 26 17:09:39 tarm kernel: [  453.122676] ADDRCONF(NETDEV_UP): eth1: link is not ready
May 26 17:09:40 tarm kernel: [  453.625166] __ratelimit: 27 messages suppressed
May 26 17:09:40 tarm kernel: [  453.625375] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:09:40 tarm kernel: [  453.634525] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
May 26 17:09:41 tarm kernel: [  455.124997] __ratelimit: 13 messages suppressed
May 26 17:09:41 tarm kernel: [  455.125216] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:09:45 tarm kernel: [  459.186581] tun0: Disabled Privacy Extensions
May 26 17:09:46 tarm kernel: [  460.124986] __ratelimit: 20 messages suppressed
May 26 17:09:46 tarm kernel: [  460.125130] cpufreq-core: target for CPU 0: 628571 kHz, relation 0
May 26 17:09:50 tarm kernel: [  464.168981] eth1: no IPv6 routers present
May 26 17:09:53 tarm kernel: [  467.124998] __ratelimit: 6 messages suppressed
May 26 17:09:53 tarm kernel: [  467.125213] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:10:10 tarm kernel: [  483.625021] __ratelimit: 27 messages suppressed
May 26 17:10:10 tarm kernel: [  483.625257] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:10:10 tarm kernel: [  483.625402] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:10:10 tarm kernel: [  483.625537] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:10:10 tarm kernel: [  484.110265] ehci_hcd 0000:00:1d.7: remove, state 4
May 26 17:10:10 tarm kernel: [  484.110393] usb usb1: USB disconnect, address 1
May 26 17:10:10 tarm kernel: [  484.124969] ehci_hcd 0000:00:1d.7: USB bus 1 deregistered
May 26 17:10:10 tarm kernel: [  484.125225] ACPI: PCI interrupt for device 0000:00:1d.7 disabled
May 26 17:10:10 tarm kernel: [  484.126042] uhci_hcd 0000:00:1d.3: remove, state 4
May 26 17:10:10 tarm kernel: [  484.126122] usb usb5: USB disconnect, address 1
May 26 17:10:10 tarm kernel: [  484.126371] uhci_hcd 0000:00:1d.3: USB bus 5 deregistered
May 26 17:10:10 tarm kernel: [  484.126458] ACPI: PCI interrupt for device 0000:00:1d.3 disabled
May 26 17:10:10 tarm kernel: [  484.126525] uhci_hcd 0000:00:1d.2: remove, state 1
May 26 17:10:10 tarm kernel: [  484.126676] usb usb4: USB disconnect, address 1
May 26 17:10:10 tarm kernel: [  484.126877] usb 4-1: USB disconnect, address 2
May 26 17:10:11 tarm kernel: [  484.394116] usb 4-2: USB disconnect, address 3
May 26 17:10:11 tarm kernel: [  484.396494] uhci_hcd 0000:00:1d.2: USB bus 4 deregistered
May 26 17:10:11 tarm kernel: [  484.396532] ACPI: PCI interrupt for device 0000:00:1d.2 disabled
May 26 17:10:11 tarm kernel: [  484.396544] uhci_hcd 0000:00:1d.1: remove, state 1
May 26 17:10:11 tarm kernel: [  484.396552] usb usb3: USB disconnect, address 1
May 26 17:10:11 tarm kernel: [  484.396554] usb 3-1: USB disconnect, address 2
May 26 17:10:11 tarm kernel: [  484.417428] uhci_hcd 0000:00:1d.1: USB bus 3 deregistered
May 26 17:10:11 tarm kernel: [  484.417622] ACPI: PCI interrupt for device 0000:00:1d.1 disabled
May 26 17:10:11 tarm kernel: [  484.417707] uhci_hcd 0000:00:1d.0: remove, state 4
May 26 17:10:11 tarm kernel: [  484.417716] usb usb2: USB disconnect, address 1
May 26 17:10:11 tarm kernel: [  484.417891] uhci_hcd 0000:00:1d.0: USB bus 2 deregistered
May 26 17:10:11 tarm kernel: [  484.417918] ACPI: PCI interrupt for device 0000:00:1d.0 disabled
May 26 17:10:11 tarm kernel: [  485.125025] __ratelimit: 11 messages suppressed
May 26 17:10:11 tarm kernel: [  485.125162] cpufreq-core: target for CPU 0: 457142 kHz, relation 0
May 26 17:10:13 tarm kernel: [  486.847805] PM: Syncing filesystems ... done.
May 26 17:10:27 tarm kernel: [  487.204289] Freezing user space processes ... (elapsed 0.04 seconds) done.
May 26 17:10:27 tarm kernel: [  487.251387] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
May 26 17:10:27 tarm kernel: [  487.251464] Suspending console(s)
May 26 17:10:27 tarm kernel: [  487.463985] sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 26 17:10:27 tarm kernel: [  487.464051] sd 0:0:0:0: [sda] Stopping disk
May 26 17:10:27 tarm kernel: [  488.897745] nsc-ircc 00:09: disabled
May 26 17:10:27 tarm kernel: [  488.897934] eth1: Going into suspend...
May 26 17:10:27 tarm kernel: [  488.903804] ACPI: PCI interrupt for device 0000:14:02.0 disabled
May 26 17:10:27 tarm kernel: [  488.903816] ACPI handle has no context!
May 26 17:10:27 tarm kernel: [  488.918131] ACPI handle has no context!
May 26 17:10:27 tarm kernel: [  488.918160] ACPI: PCI interrupt for device 0000:14:00.2 disabled
May 26 17:10:27 tarm kernel: [  488.918170] ACPI handle has no context!
May 26 17:10:27 tarm kernel: [  488.938076] ACPI handle has no context!
May 26 17:10:27 tarm kernel: [  489.094601] ACPI handle has no context!
May 26 17:10:27 tarm kernel: [  489.313053] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
May 26 17:10:27 tarm kernel: [  489.332268] ACPI: Preparing to enter system sleep state S3
May 26 17:10:27 tarm kernel: [  489.344888] Extended CMOS year: 2000
May 26 17:10:27 tarm kernel: [  489.344888] Intel machine check architecture supported.
May 26 17:10:27 tarm kernel: [  489.344904] Intel machine check reporting enabled on CPU#0.
May 26 17:10:27 tarm kernel: [  489.344967] Back to C!
May 26 17:10:27 tarm kernel: [  489.344967] Extended CMOS year: 2000
May 26 17:10:27 tarm kernel: [  489.344967] Force enabled HPET at resume
May 26 17:10:27 tarm kernel: [  489.345152] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:10:27 tarm kernel: [  489.345155] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:10:27 tarm kernel: [  489.345157] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:10:27 tarm kernel: [  489.345160] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:10:27 tarm kernel: [  489.345164] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:10:27 tarm kernel: [  489.345167] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:10:27 tarm kernel: [  489.345170] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:10:27 tarm kernel: [  489.345173] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 17:10:27 tarm kernel: [  489.345175] cpufreq-core: governor: change or update limits
May 26 17:10:27 tarm kernel: [  489.345177] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:10:27 tarm kernel: [  489.408463] PM: Writing back config space on device 0000:00:01.0 at offset 1 (was 100107, writing 100507)
May 26 17:10:27 tarm kernel: [  489.408463] PCI: Setting latency timer of device 0000:00:01.0 to 64
May 26 17:10:27 tarm kernel: [  489.425016] PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100002)
May 26 17:10:27 tarm kernel: [  489.425040] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:10:27 tarm kernel: [  489.425047] PCI: Setting latency timer of device 0000:00:1b.0 to 64
May 26 17:10:27 tarm kernel: [  489.481172] PM: Writing back config space on device 0000:00:1c.0 at offset 1 (was 100107, writing 100507)
May 26 17:10:27 tarm kernel: [  489.481244] PCI: Setting latency timer of device 0000:00:1c.0 to 64
May 26 17:10:27 tarm kernel: [  489.481296] PM: Writing back config space on device 0000:00:1c.1 at offset 1 (was 100107, writing 100507)
May 26 17:10:27 tarm kernel: [  489.481369] PCI: Setting latency timer of device 0000:00:1c.1 to 64
May 26 17:10:27 tarm kernel: [  489.481421] PM: Writing back config space on device 0000:00:1c.2 at offset 1 (was 100107, writing 100507)
May 26 17:10:27 tarm kernel: [  489.481484] PCI: Setting latency timer of device 0000:00:1c.2 to 64
May 26 17:10:27 tarm kernel: [  489.481544] PM: Writing back config space on device 0000:00:1c.3 at offset 1 (was 100107, writing 100507)
May 26 17:10:27 tarm kernel: [  489.481607] PCI: Setting latency timer of device 0000:00:1c.3 to 64
May 26 17:10:27 tarm kernel: [  489.481623] PM: Writing back config space on device 0000:00:1d.0 at offset f (was 100, writing 10b)
May 26 17:10:27 tarm kernel: [  489.481669] PM: Writing back config space on device 0000:00:1d.1 at offset f (was 200, writing 20b)
May 26 17:10:27 tarm kernel: [  489.481724] PM: Writing back config space on device 0000:00:1d.2 at offset f (was 300, writing 30b)
May 26 17:10:27 tarm kernel: [  489.481770] PM: Writing back config space on device 0000:00:1d.3 at offset f (was 400, writing 40b)
May 26 17:10:27 tarm kernel: [  489.481832] PM: Writing back config space on device 0000:00:1d.7 at offset f (was 400, writing 40b)
May 26 17:10:27 tarm kernel: [  489.481859] PM: Writing back config space on device 0000:00:1d.7 at offset 4 (was 0, writing b0004000)
May 26 17:10:27 tarm kernel: [  489.481876] PM: Writing back config space on device 0000:00:1d.7 at offset 1 (was 2900000, writing 2900102)
May 26 17:10:27 tarm kernel: [  489.481976] PCI: Setting latency timer of device 0000:00:1e.0 to 64
May 26 17:10:27 tarm kernel: [  489.497044] PM: Writing back config space on device 0000:00:1f.2 at offset 1 (was 2b00005, writing 2b80005)
May 26 17:10:27 tarm kernel: [  489.497064] PCI: Setting latency timer of device 0000:00:1f.2 to 64
May 26 17:10:27 tarm kernel: [  489.499260] PM: Writing back config space on device 0000:01:00.0 at offset 1 (was 100103, writing 100107)
May 26 17:10:27 tarm kernel: [  489.499324] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:10:27 tarm kernel: [  489.499328] PCI: Setting latency timer of device 0000:01:00.0 to 64
May 26 17:10:27 tarm kernel: [  489.499365] PM: Writing back config space on device 0000:02:00.0 at offset c (was 0, writing fcf70000)
May 26 17:10:27 tarm kernel: [  489.499391] PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 100106)
May 26 17:10:27 tarm kernel: [  489.837265] PM: Writing back config space on device 0000:14:00.1 at offset 4 (was 0, writing c0001000)
May 26 17:10:27 tarm kernel: [  489.837271] PM: Writing back config space on device 0000:14:00.1 at offset 3 (was 800000, writing 804000)
May 26 17:10:27 tarm kernel: [  489.837279] PM: Writing back config space on device 0000:14:00.1 at offset 1 (was 2100000, writing 2100106)
May 26 17:10:27 tarm kernel: [  489.845830] ata2.00: ACPI cmd ef/03:42:00:00:00:a0 filtered out
May 26 17:10:27 tarm kernel: [  489.845833] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
May 26 17:10:27 tarm kernel: [  489.849870] ata2.00: ACPI cmd e3/00:10:00:00:00:a0 succeeded
May 26 17:10:27 tarm kernel: [  489.857873] ata2.00: ACPI cmd e3/00:03:00:00:00:a0 succeeded
May 26 17:10:27 tarm kernel: [  489.882210] ata2.00: configured for UDMA/33
May 26 17:10:27 tarm kernel: [  489.892168] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17]  MMIO=[c0001000-c00017ff]  Max Packet=[2048]  IR/IT contexts=[4/4]
May 26 17:10:27 tarm kernel: [  489.917174] PM: Writing back config space on device 0000:14:00.2 at offset 4 (was 0, writing c0001800)
May 26 17:10:27 tarm kernel: [  489.917179] PM: Writing back config space on device 0000:14:00.2 at offset 3 (was 800000, writing 804000)
May 26 17:10:27 tarm kernel: [  489.917186] PM: Writing back config space on device 0000:14:00.2 at offset 1 (was 2100000, writing 2100106)
May 26 17:10:27 tarm kernel: [  489.917205] ACPI: PCI Interrupt 0000:14:00.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 17:10:27 tarm kernel: [  489.918248] eth1: Coming out of suspend...
May 26 17:10:27 tarm kernel: [  489.940100] ACPI: PCI Interrupt 0000:14:02.0[A] -> GSI 21 (level, low) -> IRQ 21
May 26 17:10:27 tarm kernel: [  489.940842] nsc-ircc 00:09: activated
May 26 17:10:27 tarm kernel: [  490.149682] __ratelimit: 37 messages suppressed
May 26 17:10:27 tarm kernel: [  490.149684] cpufreq-core: target for CPU 0: 1600000 kHz, relation 0
May 26 17:10:27 tarm kernel: [  490.892523] sd 0:0:0:0: [sda] Starting disk
May 26 17:10:27 tarm kernel: [  491.269696] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 succeeded
May 26 17:10:27 tarm kernel: [  491.269703] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
May 26 17:10:27 tarm kernel: [  491.269710] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 filtered out
May 26 17:10:27 tarm kernel: [  491.269716] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
May 26 17:10:27 tarm kernel: [  491.270140] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 succeeded
May 26 17:10:27 tarm kernel: [  491.293674] ata1.00: configured for UDMA/100
May 26 17:10:27 tarm kernel: [  491.317651] ata1.00: configured for UDMA/100
May 26 17:10:27 tarm kernel: [  491.317658] ata1: EH complete
May 26 17:10:27 tarm kernel: [  491.317751] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
May 26 17:10:27 tarm kernel: [  491.317794] sd 0:0:0:0: [sda] Write Protect is off
May 26 17:10:27 tarm kernel: [  491.317799] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 26 17:10:27 tarm kernel: [  491.317872] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 26 17:10:27 tarm kernel: [  491.317943] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
May 26 17:10:27 tarm kernel: [  491.317983] sd 0:0:0:0: [sda] Write Protect is off
May 26 17:10:27 tarm kernel: [  491.317988] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 26 17:10:27 tarm kernel: [  491.318059] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 26 17:10:27 tarm kernel: [  494.045815] hdaps: initial latch check good (0x01).
May 26 17:10:27 tarm kernel: [  494.249506] Restarting tasks ... done.
May 26 17:10:28 tarm kernel: [  494.345881] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 19
May 26 17:10:28 tarm kernel: [  494.346144] PCI: Setting latency timer of device 0000:00:1d.7 to 64
May 26 17:10:28 tarm kernel: [  494.346286] ehci_hcd 0000:00:1d.7: EHCI Host Controller
May 26 17:10:28 tarm kernel: [  494.390051] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
May 26 17:10:28 tarm kernel: [  494.394635] ehci_hcd 0000:00:1d.7: debug port 1
May 26 17:10:28 tarm kernel: [  494.394772] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
May 26 17:10:28 tarm kernel: [  494.394926] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xb0004000
May 26 17:10:28 tarm kernel: [  494.409018] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
May 26 17:10:28 tarm kernel: [  494.409522] usb usb1: configuration #1 chosen from 1 choice
May 26 17:10:28 tarm kernel: [  494.409896] hub 1-0:1.0: USB hub found
May 26 17:10:28 tarm kernel: [  494.410027] hub 1-0:1.0: 8 ports detected
May 26 17:10:28 tarm kernel: [  494.513151] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
May 26 17:10:28 tarm kernel: [  494.513392] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:10:28 tarm kernel: [  494.513735] usb usb1: Product: EHCI Host Controller
May 26 17:10:28 tarm kernel: [  494.513858] usb usb1: Manufacturer: Linux 2.6.26-rc3 ehci_hcd
May 26 17:10:28 tarm kernel: [  494.513973] usb usb1: SerialNumber: 0000:00:1d.7
May 26 17:10:28 tarm kernel: [  494.524824] USB Universal Host Controller Interface driver v3.0
May 26 17:10:28 tarm kernel: [  494.524907] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:10:28 tarm kernel: [  494.524927] PCI: Setting latency timer of device 0000:00:1d.0 to 64
May 26 17:10:28 tarm kernel: [  494.524935] uhci_hcd 0000:00:1d.0: UHCI Host Controller
May 26 17:10:28 tarm kernel: [  494.525357] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
May 26 17:10:28 tarm kernel: [  494.525398] uhci_hcd 0000:00:1d.0: irq 16, io base 0x00001800
May 26 17:10:28 tarm kernel: [  494.525629] usb usb2: configuration #1 chosen from 1 choice
May 26 17:10:28 tarm kernel: [  494.525695] hub 2-0:1.0: USB hub found
May 26 17:10:28 tarm kernel: [  494.525709] hub 2-0:1.0: 2 ports detected
May 26 17:10:28 tarm kernel: [  494.629076] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:10:28 tarm kernel: [  494.629218] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:10:28 tarm kernel: [  494.629277] usb usb2: Product: UHCI Host Controller
May 26 17:10:28 tarm kernel: [  494.629330] usb usb2: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:10:28 tarm kernel: [  494.629394] usb usb2: SerialNumber: 0000:00:1d.0
May 26 17:10:28 tarm kernel: [  494.629476] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 17
May 26 17:10:28 tarm kernel: [  494.629564] PCI: Setting latency timer of device 0000:00:1d.1 to 64
May 26 17:10:28 tarm kernel: [  494.629629] uhci_hcd 0000:00:1d.1: UHCI Host Controller
May 26 17:10:28 tarm kernel: [  494.629704] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
May 26 17:10:28 tarm kernel: [  494.629783] uhci_hcd 0000:00:1d.1: irq 17, io base 0x00001820
May 26 17:10:28 tarm kernel: [  494.629939] usb usb3: configuration #1 chosen from 1 choice
May 26 17:10:28 tarm kernel: [  494.630022] hub 3-0:1.0: USB hub found
May 26 17:10:28 tarm kernel: [  494.630079] hub 3-0:1.0: 2 ports detected
May 26 17:10:28 tarm kernel: [  494.719563] hub 1-0:1.0: unable to enumerate USB device on port 3
May 26 17:10:28 tarm kernel: [  494.733117] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:10:28 tarm kernel: [  494.734030] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:10:28 tarm kernel: [  494.734104] usb usb3: Product: UHCI Host Controller
May 26 17:10:28 tarm kernel: [  494.734156] usb usb3: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:10:28 tarm kernel: [  494.734208] usb usb3: SerialNumber: 0000:00:1d.1
May 26 17:10:28 tarm kernel: [  494.734290] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 17:10:28 tarm kernel: [  494.734373] PCI: Setting latency timer of device 0000:00:1d.2 to 64
May 26 17:10:28 tarm kernel: [  494.734437] uhci_hcd 0000:00:1d.2: UHCI Host Controller
May 26 17:10:28 tarm kernel: [  494.734517] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
May 26 17:10:28 tarm kernel: [  494.734718] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001840
May 26 17:10:28 tarm kernel: [  494.734878] usb usb4: configuration #1 chosen from 1 choice
May 26 17:10:28 tarm kernel: [  494.734962] hub 4-0:1.0: USB hub found
May 26 17:10:28 tarm kernel: [  494.735018] hub 4-0:1.0: 2 ports detected
May 26 17:10:28 tarm kernel: [  494.837089] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:10:28 tarm kernel: [  494.837223] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:10:28 tarm kernel: [  494.837283] usb usb4: Product: UHCI Host Controller
May 26 17:10:28 tarm kernel: [  494.837338] usb usb4: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:10:28 tarm kernel: [  494.837402] usb usb4: SerialNumber: 0000:00:1d.2
May 26 17:10:28 tarm kernel: [  494.837485] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 19
May 26 17:10:28 tarm kernel: [  494.837578] PCI: Setting latency timer of device 0000:00:1d.3 to 64
May 26 17:10:28 tarm kernel: [  494.837645] uhci_hcd 0000:00:1d.3: UHCI Host Controller
May 26 17:10:28 tarm kernel: [  494.837727] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
May 26 17:10:28 tarm kernel: [  494.837811] uhci_hcd 0000:00:1d.3: irq 19, io base 0x00001860
May 26 17:10:28 tarm kernel: [  494.837975] usb usb5: configuration #1 chosen from 1 choice
May 26 17:10:28 tarm kernel: [  494.838064] hub 5-0:1.0: USB hub found
May 26 17:10:28 tarm kernel: [  494.838125] hub 5-0:1.0: 2 ports detected
May 26 17:10:28 tarm kernel: [  494.941187] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:10:28 tarm kernel: [  494.942471] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:10:28 tarm kernel: [  494.942549] usb usb5: Product: UHCI Host Controller
May 26 17:10:28 tarm kernel: [  494.942603] usb usb5: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:10:28 tarm kernel: [  494.942655] usb usb5: SerialNumber: 0000:00:1d.3
May 26 17:10:28 tarm kernel: [  494.957200] hub 1-0:1.0: unable to enumerate USB device on port 5
May 26 17:10:28 tarm kernel: [  495.067809] [drm] Loading R300 Microcode
May 26 17:10:28 tarm kernel: [  495.197029] hub 1-0:1.0: unable to enumerate USB device on port 6
May 26 17:10:29 tarm kernel: [  495.437104] usb 3-1: new low speed USB device using uhci_hcd and address 2
May 26 17:10:29 tarm kernel: [  495.617733] usb 3-1: configuration #1 chosen from 1 choice
May 26 17:10:29 tarm kernel: [  495.624999] __ratelimit: 28 messages suppressed
May 26 17:10:29 tarm kernel: [  495.625107] cpufreq-core: target for CPU 0: 914285 kHz, relation 0
May 26 17:10:29 tarm kernel: [  495.641054] input: Logitech Trackball as /class/input/input17
May 26 17:10:29 tarm kernel: [  495.669040] input,hidraw0: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:1d.1-1
May 26 17:10:29 tarm kernel: [  495.669349] usb 3-1: New USB device found, idVendor=046d, idProduct=c404
May 26 17:10:29 tarm kernel: [  495.669442] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:10:29 tarm kernel: [  495.669526] usb 3-1: Product: Trackball
May 26 17:10:29 tarm kernel: [  495.669605] usb 3-1: Manufacturer: Logitech
May 26 17:10:29 tarm kernel: [  495.921022] usb 4-1: new full speed USB device using uhci_hcd and address 2
May 26 17:10:30 tarm kernel: [  496.106111] usb 4-1: configuration #1 chosen from 1 choice
May 26 17:10:30 tarm kernel: [  496.113535] usb 4-1: New USB device found, idVendor=0a5c, idProduct=2110
May 26 17:10:30 tarm kernel: [  496.113741] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:10:30 tarm kernel: [  496.113833] usb 4-1: Product: BCM2045B
May 26 17:10:30 tarm kernel: [  496.113913] usb 4-1: Manufacturer: Broadcom Corp
May 26 17:10:30 tarm kernel: [  496.353025] usb 4-2: new full speed USB device using uhci_hcd and address 3
May 26 17:10:30 tarm kernel: [  496.391231] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 17:10:30 tarm kernel: [  496.398832] pan1: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 17:10:30 tarm kernel: [  496.528100] usb 4-2: configuration #1 chosen from 1 choice
May 26 17:10:30 tarm kernel: [  496.535144] usb 4-2: New USB device found, idVendor=0483, idProduct=2016
May 26 17:10:30 tarm kernel: [  496.535317] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:10:30 tarm kernel: [  496.535371] usb 4-2: Product: Biometric Coprocessor
May 26 17:10:30 tarm kernel: [  496.535420] usb 4-2: Manufacturer: STMicroelectronics
May 26 17:10:32 tarm kernel: [  498.837639] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 26 17:10:37 tarm kernel: [  503.625008] __ratelimit: 41 messages suppressed
May 26 17:10:37 tarm kernel: [  503.625255] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:10:38 tarm kernel: [  504.706644] ADDRCONF(NETDEV_UP): eth1: link is not ready
May 26 17:10:39 tarm kernel: [  505.125057] __ratelimit: 13 messages suppressed
May 26 17:10:39 tarm kernel: [  505.125282] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:10:39 tarm kernel: [  505.624109] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
May 26 17:10:42 tarm kernel: [  508.300698] tun0: Disabled Privacy Extensions
May 26 17:10:49 tarm kernel: [  515.125001] __ratelimit: 55 messages suppressed
May 26 17:10:49 tarm kernel: [  515.125216] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:10:49 tarm kernel: [  515.125382] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:10:50 tarm kernel: [  516.492981] eth1: no IPv6 routers present
May 26 17:10:54 tarm kernel: [  520.625015] __ratelimit: 33 messages suppressed
May 26 17:10:54 tarm kernel: [  520.625253] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:11:01 tarm kernel: [  527.625011] __ratelimit: 13 messages suppressed
May 26 17:11:01 tarm kernel: [  527.625247] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:11:07 tarm kernel: [  533.125129] __ratelimit: 13 messages suppressed
May 26 17:11:07 tarm kernel: [  533.125349] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:11:18 tarm kernel: [  544.125011] __ratelimit: 13 messages suppressed
May 26 17:11:18 tarm kernel: [  544.125242] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:11:18 tarm kernel: [  544.125383] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:11:19 tarm kernel: [  545.124987] __ratelimit: 5 messages suppressed
May 26 17:11:19 tarm kernel: [  545.125125] cpufreq-core: target for CPU 0: 57142 kHz, relation 0
May 26 17:11:42 tarm kernel: [  568.125009] __ratelimit: 6 messages suppressed
May 26 17:11:42 tarm kernel: [  568.125255] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:11:42 tarm kernel: [  568.125398] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:11:42 tarm kernel: [  568.125530] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:11:42 tarm kernel: [  568.125667] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:12:02 tarm kernel: [  588.125047] __ratelimit: 10 messages suppressed
May 26 17:12:02 tarm kernel: [  588.125294] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:12:02 tarm kernel: [  588.125438] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:12:02 tarm kernel: [  588.125571] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:12:02 tarm kernel: [  588.125708] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:12:07 tarm kernel: [  593.625003] __ratelimit: 17 messages suppressed
May 26 17:12:07 tarm kernel: [  593.625231] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:12:09 tarm kernel: [  595.624986] __ratelimit: 20 messages suppressed
May 26 17:12:09 tarm kernel: [  595.625140] cpufreq-core: target for CPU 0: 1600000 kHz, relation 0
May 26 17:12:14 tarm kernel: [  600.124987] __ratelimit: 25 messages suppressed
May 26 17:12:14 tarm kernel: [  600.125128] cpufreq-core: target for CPU 0: 342857 kHz, relation 0
May 26 17:12:21 tarm kernel: [  607.129339] __ratelimit: 41 messages suppressed
May 26 17:12:21 tarm kernel: [  607.129571] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:12:24 tarm kernel: [  610.125052] __ratelimit: 13 messages suppressed
May 26 17:12:24 tarm kernel: [  610.125367] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:12:30 tarm kernel: [  616.125014] __ratelimit: 13 messages suppressed
May 26 17:12:30 tarm kernel: [  616.125266] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:12:42 tarm kernel: [  628.625019] __ratelimit: 18 messages suppressed
May 26 17:12:42 tarm kernel: [  628.625243] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:12:42 tarm kernel: [  628.625382] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:12:54 tarm kernel: [  640.625537] __ratelimit: 12 messages suppressed
May 26 17:12:54 tarm kernel: [  640.625756] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:12:54 tarm kernel: [  640.625900] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:12:54 tarm kernel: [  640.626068] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:13:01 tarm kernel: [  647.125036] __ratelimit: 25 messages suppressed
May 26 17:13:01 tarm kernel: [  647.125255] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:13:28 tarm kernel: [  674.625023] __ratelimit: 20 messages suppressed
May 26 17:13:28 tarm kernel: [  674.625347] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:13:28 tarm kernel: [  674.625495] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:13:28 tarm kernel: [  674.625652] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:13:28 tarm kernel: [  674.625796] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:13:28 tarm kernel: [  674.625930] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:13:29 tarm kernel: [  675.124987] __ratelimit: 2 messages suppressed
May 26 17:13:29 tarm kernel: [  675.125127] cpufreq-core: target for CPU 0: 628571 kHz, relation 0
May 26 17:13:33 tarm kernel: [  679.037672] ehci_hcd 0000:00:1d.7: remove, state 4
May 26 17:13:33 tarm kernel: [  679.037687] usb usb1: USB disconnect, address 1
May 26 17:13:33 tarm kernel: [  679.066194] ehci_hcd 0000:00:1d.7: USB bus 1 deregistered
May 26 17:13:33 tarm kernel: [  679.066253] ACPI: PCI interrupt for device 0000:00:1d.7 disabled
May 26 17:13:33 tarm kernel: [  679.067034] uhci_hcd 0000:00:1d.3: remove, state 4
May 26 17:13:33 tarm kernel: [  679.067044] usb usb5: USB disconnect, address 1
May 26 17:13:33 tarm kernel: [  679.067236] uhci_hcd 0000:00:1d.3: USB bus 5 deregistered
May 26 17:13:33 tarm kernel: [  679.067265] ACPI: PCI interrupt for device 0000:00:1d.3 disabled
May 26 17:13:33 tarm kernel: [  679.067275] uhci_hcd 0000:00:1d.2: remove, state 1
May 26 17:13:33 tarm kernel: [  679.067283] usb usb4: USB disconnect, address 1
May 26 17:13:33 tarm kernel: [  679.067285] usb 4-1: USB disconnect, address 2
May 26 17:13:33 tarm kernel: [  679.326093] usb 4-2: USB disconnect, address 3
May 26 17:13:33 tarm kernel: [  679.328506] uhci_hcd 0000:00:1d.2: USB bus 4 deregistered
May 26 17:13:33 tarm kernel: [  679.328544] ACPI: PCI interrupt for device 0000:00:1d.2 disabled
May 26 17:13:33 tarm kernel: [  679.328554] uhci_hcd 0000:00:1d.1: remove, state 1
May 26 17:13:33 tarm kernel: [  679.328562] usb usb3: USB disconnect, address 1
May 26 17:13:33 tarm kernel: [  679.328564] usb 3-1: USB disconnect, address 2
May 26 17:13:33 tarm kernel: [  679.349431] uhci_hcd 0000:00:1d.1: USB bus 3 deregistered
May 26 17:13:33 tarm kernel: [  679.349619] ACPI: PCI interrupt for device 0000:00:1d.1 disabled
May 26 17:13:33 tarm kernel: [  679.349704] uhci_hcd 0000:00:1d.0: remove, state 4
May 26 17:13:33 tarm kernel: [  679.349714] usb usb2: USB disconnect, address 1
May 26 17:13:33 tarm kernel: [  679.349889] uhci_hcd 0000:00:1d.0: USB bus 2 deregistered
May 26 17:13:33 tarm kernel: [  679.349916] ACPI: PCI interrupt for device 0000:00:1d.0 disabled
May 26 17:13:34 tarm kernel: [  680.125052] __ratelimit: 18 messages suppressed
May 26 17:13:34 tarm kernel: [  680.125198] cpufreq-core: target for CPU 0: 1828571 kHz, relation 0
May 26 17:13:35 tarm kernel: [  681.499633] PM: Syncing filesystems ... done.
May 26 17:13:47 tarm kernel: [  681.613159] Freezing user space processes ... (elapsed 0.00 seconds) done.
May 26 17:13:47 tarm kernel: [  681.614674] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
May 26 17:13:47 tarm kernel: [  681.614758] Suspending console(s)
May 26 17:13:47 tarm kernel: [  681.835093] sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 26 17:13:47 tarm kernel: [  681.844214] sd 0:0:0:0: [sda] Stopping disk
May 26 17:13:47 tarm kernel: [  683.265808] nsc-ircc 00:09: disabled
May 26 17:13:47 tarm kernel: [  683.265997] eth1: Going into suspend...
May 26 17:13:47 tarm kernel: [  683.270843] ACPI: PCI interrupt for device 0000:14:02.0 disabled
May 26 17:13:47 tarm kernel: [  683.270855] ACPI handle has no context!
May 26 17:13:47 tarm kernel: [  683.286131] ACPI handle has no context!
May 26 17:13:47 tarm kernel: [  683.286160] ACPI: PCI interrupt for device 0000:14:00.2 disabled
May 26 17:13:47 tarm kernel: [  683.286170] ACPI handle has no context!
May 26 17:13:47 tarm kernel: [  683.306077] ACPI handle has no context!
May 26 17:13:47 tarm kernel: [  683.462597] ACPI handle has no context!
May 26 17:13:47 tarm kernel: [  683.681053] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
May 26 17:13:47 tarm kernel: [  683.700321] ACPI: Preparing to enter system sleep state S3
May 26 17:13:47 tarm kernel: [  683.712644] Extended CMOS year: 2000
May 26 17:13:47 tarm kernel: [  683.712644] Intel machine check architecture supported.
May 26 17:13:47 tarm kernel: [  683.712660] Intel machine check reporting enabled on CPU#0.
May 26 17:13:47 tarm kernel: [  683.712761] Back to C!
May 26 17:13:47 tarm kernel: [  683.712967] Extended CMOS year: 2000
May 26 17:13:47 tarm kernel: [  683.712967] Force enabled HPET at resume
May 26 17:13:47 tarm kernel: [  683.712967] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:13:47 tarm kernel: [  683.712967] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:13:47 tarm kernel: [  683.712967] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:13:47 tarm kernel: [  683.712967] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:13:47 tarm kernel: [  683.712967] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:13:47 tarm kernel: [  683.712967] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:13:47 tarm kernel: [  683.712967] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:13:47 tarm kernel: [  683.712967] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 17:13:47 tarm kernel: [  683.712967] cpufreq-core: governor: change or update limits
May 26 17:13:47 tarm kernel: [  683.712967] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:13:47 tarm kernel: [  683.762614] PM: Writing back config space on device 0000:00:01.0 at offset 1 (was 100107, writing 100507)
May 26 17:13:47 tarm kernel: [  683.762614] PCI: Setting latency timer of device 0000:00:01.0 to 64
May 26 17:13:47 tarm kernel: [  683.789051] PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100002)
May 26 17:13:47 tarm kernel: [  683.789074] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:13:47 tarm kernel: [  683.789081] PCI: Setting latency timer of device 0000:00:1b.0 to 64
May 26 17:13:47 tarm kernel: [  683.845176] PM: Writing back config space on device 0000:00:1c.0 at offset 1 (was 100107, writing 100507)
May 26 17:13:47 tarm kernel: [  683.845248] PCI: Setting latency timer of device 0000:00:1c.0 to 64
May 26 17:13:47 tarm kernel: [  683.845299] PM: Writing back config space on device 0000:00:1c.1 at offset 1 (was 100107, writing 100507)
May 26 17:13:47 tarm kernel: [  683.845363] PCI: Setting latency timer of device 0000:00:1c.1 to 64
May 26 17:13:47 tarm kernel: [  683.845423] PM: Writing back config space on device 0000:00:1c.2 at offset 1 (was 100107, writing 100507)
May 26 17:13:47 tarm kernel: [  683.845487] PCI: Setting latency timer of device 0000:00:1c.2 to 64
May 26 17:13:47 tarm kernel: [  683.845548] PM: Writing back config space on device 0000:00:1c.3 at offset 1 (was 100107, writing 100507)
May 26 17:13:47 tarm kernel: [  683.845611] PCI: Setting latency timer of device 0000:00:1c.3 to 64
May 26 17:13:47 tarm kernel: [  683.845627] PM: Writing back config space on device 0000:00:1d.0 at offset f (was 100, writing 10b)
May 26 17:13:47 tarm kernel: [  683.845673] PM: Writing back config space on device 0000:00:1d.1 at offset f (was 200, writing 20b)
May 26 17:13:47 tarm kernel: [  683.845728] PM: Writing back config space on device 0000:00:1d.2 at offset f (was 300, writing 30b)
May 26 17:13:47 tarm kernel: [  683.845774] PM: Writing back config space on device 0000:00:1d.3 at offset f (was 400, writing 40b)
May 26 17:13:47 tarm kernel: [  683.845836] PM: Writing back config space on device 0000:00:1d.7 at offset f (was 400, writing 40b)
May 26 17:13:47 tarm kernel: [  683.845873] PM: Writing back config space on device 0000:00:1d.7 at offset 4 (was 0, writing b0004000)
May 26 17:13:47 tarm kernel: [  683.845881] PM: Writing back config space on device 0000:00:1d.7 at offset 1 (was 2900000, writing 2900102)
May 26 17:13:47 tarm kernel: [  683.845980] PCI: Setting latency timer of device 0000:00:1e.0 to 64
May 26 17:13:47 tarm kernel: [  683.861043] PM: Writing back config space on device 0000:00:1f.2 at offset 1 (was 2b00005, writing 2b80005)
May 26 17:13:47 tarm kernel: [  683.861062] PCI: Setting latency timer of device 0000:00:1f.2 to 64
May 26 17:13:47 tarm kernel: [  683.863259] PM: Writing back config space on device 0000:01:00.0 at offset 1 (was 100103, writing 100107)
May 26 17:13:47 tarm kernel: [  683.863323] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:13:47 tarm kernel: [  683.863327] PCI: Setting latency timer of device 0000:01:00.0 to 64
May 26 17:13:47 tarm kernel: [  683.863365] PM: Writing back config space on device 0000:02:00.0 at offset c (was 0, writing fcff0000)
May 26 17:13:47 tarm kernel: [  683.863391] PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 100106)
May 26 17:13:47 tarm kernel: [  684.201259] PM: Writing back config space on device 0000:14:00.1 at offset 4 (was 0, writing c0001000)
May 26 17:13:47 tarm kernel: [  684.201265] PM: Writing back config space on device 0000:14:00.1 at offset 3 (was 800000, writing 804000)
May 26 17:13:47 tarm kernel: [  684.201273] PM: Writing back config space on device 0000:14:00.1 at offset 1 (was 2100000, writing 2100106)
May 26 17:13:47 tarm kernel: [  684.213807] ata2.00: ACPI cmd ef/03:42:00:00:00:a0 filtered out
May 26 17:13:47 tarm kernel: [  684.213809] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
May 26 17:13:47 tarm kernel: [  684.221813] ata2.00: ACPI cmd e3/00:10:00:00:00:a0 succeeded
May 26 17:13:47 tarm kernel: [  684.229816] ata2.00: ACPI cmd e3/00:03:00:00:00:a0 succeeded
May 26 17:13:47 tarm kernel: [  684.254164] ata2.00: configured for UDMA/33
May 26 17:13:47 tarm kernel: [  684.256181] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17]  MMIO=[c0001000-c00017ff]  Max Packet=[2048]  IR/IT contexts=[4/4]
May 26 17:13:47 tarm kernel: [  684.281188] PM: Writing back config space on device 0000:14:00.2 at offset 4 (was 0, writing c0001800)
May 26 17:13:47 tarm kernel: [  684.281193] PM: Writing back config space on device 0000:14:00.2 at offset 3 (was 800000, writing 804000)
May 26 17:13:47 tarm kernel: [  684.281200] PM: Writing back config space on device 0000:14:00.2 at offset 1 (was 2100000, writing 2100106)
May 26 17:13:47 tarm kernel: [  684.281219] ACPI: PCI Interrupt 0000:14:00.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 17:13:47 tarm kernel: [  684.282264] eth1: Coming out of suspend...
May 26 17:13:47 tarm kernel: [  684.304115] ACPI: PCI Interrupt 0000:14:02.0[A] -> GSI 21 (level, low) -> IRQ 21
May 26 17:13:47 tarm kernel: [  684.304856] nsc-ircc 00:09: activated
May 26 17:13:47 tarm kernel: [  685.125021] __ratelimit: 36 messages suppressed
May 26 17:13:47 tarm kernel: [  685.125024] cpufreq-core: target for CPU 0: 1005714 kHz, relation 0
May 26 17:13:47 tarm kernel: [  685.240365] sd 0:0:0:0: [sda] Starting disk
May 26 17:13:47 tarm kernel: [  685.361681] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 succeeded
May 26 17:13:47 tarm kernel: [  685.361686] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
May 26 17:13:47 tarm kernel: [  685.361691] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 filtered out
May 26 17:13:47 tarm kernel: [  685.361696] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
May 26 17:13:47 tarm kernel: [  685.362115] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 succeeded
May 26 17:13:47 tarm kernel: [  685.385653] ata1.00: configured for UDMA/100
May 26 17:13:47 tarm kernel: [  685.409640] ata1.00: configured for UDMA/100
May 26 17:13:47 tarm kernel: [  685.409645] ata1: EH complete
May 26 17:13:47 tarm kernel: [  685.409720] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
May 26 17:13:47 tarm kernel: [  685.409754] sd 0:0:0:0: [sda] Write Protect is off
May 26 17:13:47 tarm kernel: [  685.409759] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 26 17:13:47 tarm kernel: [  685.409816] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 26 17:13:47 tarm kernel: [  685.409873] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
May 26 17:13:47 tarm kernel: [  685.409904] sd 0:0:0:0: [sda] Write Protect is off
May 26 17:13:47 tarm kernel: [  685.409908] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 26 17:13:47 tarm kernel: [  685.409964] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 26 17:13:47 tarm kernel: [  688.101026] hdaps: initial latch check good (0x01).
May 26 17:13:47 tarm kernel: [  688.509522] Restarting tasks ... done.
May 26 17:13:47 tarm kernel: [  688.613227] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 19
May 26 17:13:47 tarm kernel: [  688.613491] PCI: Setting latency timer of device 0000:00:1d.7 to 64
May 26 17:13:47 tarm kernel: [  688.613633] ehci_hcd 0000:00:1d.7: EHCI Host Controller
May 26 17:13:47 tarm kernel: [  688.662871] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
May 26 17:13:47 tarm kernel: [  688.667009] ehci_hcd 0000:00:1d.7: debug port 1
May 26 17:13:47 tarm kernel: [  688.669045] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
May 26 17:13:47 tarm kernel: [  688.669225] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xb0004000
May 26 17:13:47 tarm kernel: [  688.685034] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
May 26 17:13:47 tarm kernel: [  688.685481] usb usb1: configuration #1 chosen from 1 choice
May 26 17:13:47 tarm kernel: [  688.691355] hub 1-0:1.0: USB hub found
May 26 17:13:47 tarm kernel: [  688.691495] hub 1-0:1.0: 8 ports detected
May 26 17:13:47 tarm kernel: [  688.805182] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
May 26 17:13:47 tarm kernel: [  688.805194] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:13:47 tarm kernel: [  688.805201] usb usb1: Product: EHCI Host Controller
May 26 17:13:47 tarm kernel: [  688.805207] usb usb1: Manufacturer: Linux 2.6.26-rc3 ehci_hcd
May 26 17:13:47 tarm kernel: [  688.805213] usb usb1: SerialNumber: 0000:00:1d.7
May 26 17:13:47 tarm kernel: [  688.816077] USB Universal Host Controller Interface driver v3.0
May 26 17:13:47 tarm kernel: [  688.816157] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
May 26 17:13:47 tarm kernel: [  688.816177] PCI: Setting latency timer of device 0000:00:1d.0 to 64
May 26 17:13:47 tarm kernel: [  688.816185] uhci_hcd 0000:00:1d.0: UHCI Host Controller
May 26 17:13:47 tarm kernel: [  688.816252] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
May 26 17:13:47 tarm kernel: [  688.816288] uhci_hcd 0000:00:1d.0: irq 16, io base 0x00001800
May 26 17:13:47 tarm kernel: [  688.816514] usb usb2: configuration #1 chosen from 1 choice
May 26 17:13:47 tarm kernel: [  688.816578] hub 2-0:1.0: USB hub found
May 26 17:13:47 tarm kernel: [  688.816592] hub 2-0:1.0: 2 ports detected
May 26 17:13:47 tarm kernel: [  688.917139] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:13:47 tarm kernel: [  688.917780] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:13:47 tarm kernel: [  688.917792] usb usb2: Product: UHCI Host Controller
May 26 17:13:47 tarm kernel: [  688.917798] usb usb2: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:13:47 tarm kernel: [  688.917803] usb usb2: SerialNumber: 0000:00:1d.0
May 26 17:13:47 tarm kernel: [  688.917849] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 17
May 26 17:13:47 tarm kernel: [  688.917868] PCI: Setting latency timer of device 0000:00:1d.1 to 64
May 26 17:13:47 tarm kernel: [  688.917876] uhci_hcd 0000:00:1d.1: UHCI Host Controller
May 26 17:13:47 tarm kernel: [  688.917936] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
May 26 17:13:47 tarm kernel: [  688.917972] uhci_hcd 0000:00:1d.1: irq 17, io base 0x00001820
May 26 17:13:47 tarm kernel: [  688.918197] usb usb3: configuration #1 chosen from 1 choice
May 26 17:13:47 tarm kernel: [  688.918263] hub 3-0:1.0: USB hub found
May 26 17:13:47 tarm kernel: [  688.918277] hub 3-0:1.0: 2 ports detected
May 26 17:13:48 tarm kernel: [  689.001814] hub 1-0:1.0: unable to enumerate USB device on port 3
May 26 17:13:48 tarm kernel: [  689.021284] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:13:48 tarm kernel: [  689.021491] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:13:48 tarm kernel: [  689.021502] usb usb3: Product: UHCI Host Controller
May 26 17:13:48 tarm kernel: [  689.021507] usb usb3: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:13:48 tarm kernel: [  689.021513] usb usb3: SerialNumber: 0000:00:1d.1
May 26 17:13:48 tarm kernel: [  689.021559] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
May 26 17:13:48 tarm kernel: [  689.021578] PCI: Setting latency timer of device 0000:00:1d.2 to 64
May 26 17:13:48 tarm kernel: [  689.021586] uhci_hcd 0000:00:1d.2: UHCI Host Controller
May 26 17:13:48 tarm kernel: [  689.021641] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
May 26 17:13:48 tarm kernel: [  689.021675] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001840
May 26 17:13:48 tarm kernel: [  689.021905] usb usb4: configuration #1 chosen from 1 choice
May 26 17:13:48 tarm kernel: [  689.021971] hub 4-0:1.0: USB hub found
May 26 17:13:48 tarm kernel: [  689.021984] hub 4-0:1.0: 2 ports detected
May 26 17:13:48 tarm kernel: [  689.125223] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:13:48 tarm kernel: [  689.125235] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:13:48 tarm kernel: [  689.125242] usb usb4: Product: UHCI Host Controller
May 26 17:13:48 tarm kernel: [  689.125248] usb usb4: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:13:48 tarm kernel: [  689.125254] usb usb4: SerialNumber: 0000:00:1d.2
May 26 17:13:48 tarm kernel: [  689.125297] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 19
May 26 17:13:48 tarm kernel: [  689.125317] PCI: Setting latency timer of device 0000:00:1d.3 to 64
May 26 17:13:48 tarm kernel: [  689.125324] uhci_hcd 0000:00:1d.3: UHCI Host Controller
May 26 17:13:48 tarm kernel: [  689.125377] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
May 26 17:13:48 tarm kernel: [  689.125412] uhci_hcd 0000:00:1d.3: irq 19, io base 0x00001860
May 26 17:13:48 tarm kernel: [  689.125642] usb usb5: configuration #1 chosen from 1 choice
May 26 17:13:48 tarm kernel: [  689.125708] hub 5-0:1.0: USB hub found
May 26 17:13:48 tarm kernel: [  689.125722] hub 5-0:1.0: 2 ports detected
May 26 17:13:48 tarm kernel: [  689.229073] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
May 26 17:13:48 tarm kernel: [  689.229218] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May 26 17:13:48 tarm kernel: [  689.229275] usb usb5: Product: UHCI Host Controller
May 26 17:13:48 tarm kernel: [  689.229328] usb usb5: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
May 26 17:13:48 tarm kernel: [  689.229380] usb usb5: SerialNumber: 0000:00:1d.3
May 26 17:13:48 tarm kernel: [  689.241062] hub 1-0:1.0: unable to enumerate USB device on port 5
May 26 17:13:48 tarm kernel: [  689.335824] [drm] Loading R300 Microcode
May 26 17:13:48 tarm kernel: [  689.481010] hub 1-0:1.0: unable to enumerate USB device on port 6
May 26 17:13:48 tarm kernel: [  689.721001] usb 3-1: new low speed USB device using uhci_hcd and address 2
May 26 17:13:48 tarm kernel: [  689.900933] usb 3-1: configuration #1 chosen from 1 choice
May 26 17:13:48 tarm kernel: [  689.929009] input: Logitech Trackball as /class/input/input18
May 26 17:13:48 tarm kernel: [  689.957156] input,hidraw0: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:1d.1-1
May 26 17:13:48 tarm kernel: [  689.957408] usb 3-1: New USB device found, idVendor=046d, idProduct=c404
May 26 17:13:48 tarm kernel: [  689.957465] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:13:48 tarm kernel: [  689.957517] usb 3-1: Product: Trackball
May 26 17:13:48 tarm kernel: [  689.957566] usb 3-1: Manufacturer: Logitech
May 26 17:13:49 tarm kernel: [  690.197096] usb 4-1: new full speed USB device using uhci_hcd and address 2
May 26 17:13:49 tarm kernel: [  690.374479] usb 4-1: configuration #1 chosen from 1 choice
May 26 17:13:49 tarm kernel: [  690.380777] usb 4-1: New USB device found, idVendor=0a5c, idProduct=2110
May 26 17:13:49 tarm kernel: [  690.381156] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:13:49 tarm kernel: [  690.381228] usb 4-1: Product: BCM2045B
May 26 17:13:49 tarm kernel: [  690.381279] usb 4-1: Manufacturer: Broadcom Corp
May 26 17:13:49 tarm kernel: [  690.621038] usb 4-2: new full speed USB device using uhci_hcd and address 3
May 26 17:13:49 tarm kernel: [  690.642216] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 17:13:49 tarm kernel: [  690.649778] pan1: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
May 26 17:13:49 tarm kernel: [  690.791941] usb 4-2: configuration #1 chosen from 1 choice
May 26 17:13:49 tarm kernel: [  690.799042] usb 4-2: New USB device found, idVendor=0483, idProduct=2016
May 26 17:13:49 tarm kernel: [  690.799147] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
May 26 17:13:49 tarm kernel: [  690.799217] usb 4-2: Product: Biometric Coprocessor
May 26 17:13:49 tarm kernel: [  690.799267] usb 4-2: Manufacturer: STMicroelectronics
May 26 17:13:51 tarm kernel: [  692.125168] __ratelimit: 20 messages suppressed
May 26 17:13:51 tarm kernel: [  692.125309] cpufreq-core: target for CPU 0: 400000 kHz, relation 0
May 26 17:13:51 tarm kernel: [  692.821450] ADDRCONF(NETDEV_UP): eth0: link is not ready
May 26 17:13:54 tarm kernel: [  695.124991] __ratelimit: 13 messages suppressed
May 26 17:13:54 tarm kernel: [  695.125126] cpufreq-core: target for CPU 0: 1714285 kHz, relation 0
May 26 17:13:57 tarm kernel: [  698.726701] ADDRCONF(NETDEV_UP): eth1: link is not ready
May 26 17:13:58 tarm kernel: [  699.619284] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
May 26 17:14:00 tarm kernel: [  701.625013] __ratelimit: 27 messages suppressed
May 26 17:14:00 tarm kernel: [  701.625238] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:14:01 tarm kernel: [  702.285362] tun0: Disabled Privacy Extensions
May 26 17:14:08 tarm kernel: [  709.912981] eth1: no IPv6 routers present
May 26 17:14:10 tarm kernel: [  711.125019] __ratelimit: 27 messages suppressed
May 26 17:14:10 tarm kernel: [  711.125255] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:14:10 tarm kernel: [  711.125430] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:14:51 tarm kernel: [  752.125025] __ratelimit: 12 messages suppressed
May 26 17:14:51 tarm kernel: [  752.125268] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:14:51 tarm kernel: [  752.125414] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:14:51 tarm kernel: [  752.125551] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:14:51 tarm kernel: [  752.125691] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:14:51 tarm kernel: [  752.125820] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:14:51 tarm kernel: [  752.125978] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:14:51 tarm kernel: [  752.126035] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:14:51 tarm kernel: [  752.624990] cpufreq-core: target for CPU 0: 685714 kHz, relation 0
May 26 17:14:54 tarm kernel: [  755.125030] __ratelimit: 20 messages suppressed
May 26 17:14:54 tarm kernel: [  755.125175] cpufreq-core: target for CPU 0: 137142 kHz, relation 0
May 26 17:15:05 tarm kernel: [  766.626964] __ratelimit: 39 messages suppressed
May 26 17:15:05 tarm kernel: [  766.627173] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:15:05 tarm kernel: [  766.627318] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:15:09 tarm kernel: [  770.625018] __ratelimit: 19 messages suppressed
May 26 17:15:09 tarm kernel: [  770.625466] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:15:18 tarm kernel: [  779.625026] __ratelimit: 13 messages suppressed
May 26 17:15:18 tarm kernel: [  779.625254] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:15:19 tarm kernel: [  780.124986] __ratelimit: 6 messages suppressed
May 26 17:15:19 tarm kernel: [  780.125126] cpufreq-core: target for CPU 0: 171428 kHz, relation 0
May 26 17:15:53 tarm kernel: [  814.624997] __ratelimit: 20 messages suppressed
May 26 17:15:53 tarm kernel: [  814.625215] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:15:53 tarm kernel: [  814.625381] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:15:53 tarm kernel: [  814.625513] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:15:53 tarm kernel: [  814.625650] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:15:53 tarm kernel: [  814.625779] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:15:53 tarm kernel: [  814.625913] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:15:54 tarm kernel: [  815.124988] __ratelimit: 1 messages suppressed
May 26 17:15:54 tarm kernel: [  815.125128] cpufreq-core: target for CPU 0: 0 kHz, relation 0
May 26 17:16:53 tarm kernel: [  874.624998] __ratelimit: 6 messages suppressed
May 26 17:16:53 tarm kernel: [  874.625222] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:16:53 tarm kernel: [  874.625388] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:16:53 tarm kernel: [  874.625522] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:16:53 tarm kernel: [  874.625658] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:16:53 tarm kernel: [  874.625786] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:16:53 tarm kernel: [  874.625920] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:16:53 tarm kernel: [  874.625975] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:16:54 tarm kernel: [  875.124986] cpufreq-core: target for CPU 0: 0 kHz, relation 0
May 26 17:16:54 tarm kernel: [  875.125137] acpi-cpufreq: acpi_cpufreq_target 0 (0)
May 26 17:16:54 tarm kernel: [  875.125211] freq-table: request for target 0 kHz (relation: 0) for cpu 0
May 26 17:17:53 tarm kernel: [  934.625012] __ratelimit: 18 messages suppressed
May 26 17:17:53 tarm kernel: [  934.625248] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:17:53 tarm kernel: [  934.625413] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:17:53 tarm kernel: [  934.625549] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:17:53 tarm kernel: [  934.625685] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:17:53 tarm kernel: [  934.625815] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:17:53 tarm kernel: [  934.625949] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:17:53 tarm kernel: [  934.626004] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:17:54 tarm kernel: [  935.124990] cpufreq-core: target for CPU 0: 171428 kHz, relation 0
May 26 17:17:54 tarm kernel: [  935.125159] acpi-cpufreq: acpi_cpufreq_target 171428 (0)
May 26 17:17:54 tarm kernel: [  935.125249] freq-table: request for target 171428 kHz (relation: 0) for cpu 0
May 26 17:18:04 tarm kernel: [  945.125001] __ratelimit: 4 messages suppressed
May 26 17:18:04 tarm kernel: [  945.125228] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:18:04 tarm kernel: [  945.125397] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:18:53 tarm kernel: [  994.625059] __ratelimit: 12 messages suppressed
May 26 17:18:53 tarm kernel: [  994.625297] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:18:53 tarm kernel: [  994.625440] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:18:53 tarm kernel: [  994.625575] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:18:53 tarm kernel: [  994.625715] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:18:53 tarm kernel: [  994.625847] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:18:53 tarm kernel: [  994.625983] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:18:53 tarm kernel: [  994.626037] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:18:54 tarm kernel: [  995.624989] cpufreq-core: target for CPU 0: 57142 kHz, relation 0
May 26 17:18:54 tarm kernel: [  995.625149] acpi-cpufreq: acpi_cpufreq_target 57142 (0)
May 26 17:18:54 tarm kernel: [  995.625223] freq-table: request for target 57142 kHz (relation: 0) for cpu 0
May 26 17:19:14 tarm kernel: [ 1015.125008] __ratelimit: 4 messages suppressed
May 26 17:19:14 tarm kernel: [ 1015.125233] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:19:14 tarm kernel: [ 1015.125399] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:19:14 tarm kernel: [ 1015.125533] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:19:14 tarm kernel: [ 1015.125670] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:19:54 tarm kernel: [ 1055.125008] __ratelimit: 17 messages suppressed
May 26 17:19:54 tarm kernel: [ 1055.125243] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:19:54 tarm kernel: [ 1055.125382] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:19:54 tarm kernel: [ 1055.125513] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:19:54 tarm kernel: [ 1055.125649] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:19:54 tarm kernel: [ 1055.125777] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:19:54 tarm kernel: [ 1055.125911] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:19:54 tarm kernel: [ 1055.125965] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:19:54 tarm kernel: [ 1055.625012] cpufreq-core: target for CPU 0: 57142 kHz, relation 0
May 26 17:20:14 tarm kernel: [ 1075.125008] __ratelimit: 6 messages suppressed
May 26 17:20:14 tarm kernel: [ 1075.125237] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:20:14 tarm kernel: [ 1075.125381] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:20:14 tarm kernel: [ 1075.125515] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:20:14 tarm kernel: [ 1075.125653] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:20:26 tarm kernel: [ 1087.124998] __ratelimit: 10 messages suppressed
May 26 17:20:26 tarm kernel: [ 1087.125221] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:20:26 tarm kernel: [ 1087.125384] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:20:54 tarm kernel: [ 1115.124997] __ratelimit: 12 messages suppressed
May 26 17:20:54 tarm kernel: [ 1115.125222] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:20:54 tarm kernel: [ 1115.125388] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:20:54 tarm kernel: [ 1115.125523] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:20:54 tarm kernel: [ 1115.125659] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:20:54 tarm kernel: [ 1115.125788] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:20:54 tarm kernel: [ 1115.125947] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:21:15 tarm kernel: [ 1136.125011] __ratelimit: 8 messages suppressed
May 26 17:21:15 tarm kernel: [ 1136.125243] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:21:15 tarm kernel: [ 1136.125382] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:21:15 tarm kernel: [ 1136.125527] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:21:15 tarm kernel: [ 1136.125689] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:21:54 tarm kernel: [ 1175.125018] __ratelimit: 10 messages suppressed
May 26 17:21:54 tarm kernel: [ 1175.125245] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:21:54 tarm kernel: [ 1175.125387] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:21:54 tarm kernel: [ 1175.125520] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:21:54 tarm kernel: [ 1175.125658] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:21:54 tarm kernel: [ 1175.125790] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:21:54 tarm kernel: [ 1175.125925] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:21:54 tarm kernel: [ 1175.125979] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:21:54 tarm kernel: [ 1175.624992] cpufreq-core: target for CPU 0: 1771428 kHz, relation 0
May 26 17:22:16 tarm kernel: [ 1197.625810] __ratelimit: 11 messages suppressed
May 26 17:22:16 tarm kernel: [ 1197.626031] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:22:16 tarm kernel: [ 1197.626176] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:22:16 tarm kernel: [ 1197.626457] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:22:16 tarm kernel: [ 1197.626603] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:22:29 tarm kernel: [ 1210.125024] __ratelimit: 10 messages suppressed
May 26 17:22:29 tarm kernel: [ 1210.125247] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:22:29 tarm kernel: [ 1210.125393] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:22:29 tarm kernel: [ 1210.125528] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:22:54 tarm kernel: [ 1235.625018] __ratelimit: 11 messages suppressed
May 26 17:22:54 tarm kernel: [ 1235.625239] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:22:54 tarm kernel: [ 1235.625403] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:22:54 tarm kernel: [ 1235.625538] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:22:54 tarm kernel: [ 1235.625674] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:22:54 tarm kernel: [ 1235.625803] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:23:16 tarm kernel: [ 1257.125017] __ratelimit: 9 messages suppressed
May 26 17:23:16 tarm kernel: [ 1257.125262] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:23:16 tarm kernel: [ 1257.125404] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:23:16 tarm kernel: [ 1257.125536] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:23:16 tarm kernel: [ 1257.125673] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:23:54 tarm kernel: [ 1295.625025] __ratelimit: 10 messages suppressed
May 26 17:23:54 tarm kernel: [ 1295.625295] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:23:54 tarm kernel: [ 1295.625453] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:23:54 tarm kernel: [ 1295.625591] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:23:54 tarm kernel: [ 1295.625732] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:23:54 tarm kernel: [ 1295.625866] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:23:54 tarm kernel: [ 1295.626006] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:23:54 tarm kernel: [ 1295.626069] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:23:55 tarm kernel: [ 1296.124988] cpufreq-core: target for CPU 0: 342857 kHz, relation 0
May 26 17:24:22 tarm kernel: [ 1323.125013] __ratelimit: 6 messages suppressed
May 26 17:24:22 tarm kernel: [ 1323.125256] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:24:22 tarm kernel: [ 1323.125399] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:24:22 tarm kernel: [ 1323.125532] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:24:22 tarm kernel: [ 1323.125670] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:24:22 tarm kernel: [ 1323.125798] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:24:25 tarm kernel: [ 1326.125101] __ratelimit: 9 messages suppressed
May 26 17:24:25 tarm kernel: [ 1326.125315] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:24:28 tarm kernel: [ 1329.625024] __ratelimit: 46 messages suppressed
May 26 17:24:28 tarm kernel: [ 1329.625208] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:24:33 tarm kernel: [ 1334.624994] __ratelimit: 53 messages suppressed
May 26 17:24:33 tarm kernel: [ 1334.625181] cpufreq-core: target for CPU 0: 121828 kHz, relation 0
May 26 17:24:44 tarm kernel: [ 1345.125022] __ratelimit: 6 messages suppressed
May 26 17:24:44 tarm kernel: [ 1345.125262] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:24:44 tarm kernel: [ 1345.125404] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:24:49 tarm kernel: [ 1350.125010] __ratelimit: 12 messages suppressed
May 26 17:24:49 tarm kernel: [ 1350.125260] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:24:54 tarm kernel: [ 1355.625050] __ratelimit: 34 messages suppressed
May 26 17:24:54 tarm kernel: [ 1355.625262] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:25:01 tarm kernel: [ 1362.124998] __ratelimit: 34 messages suppressed
May 26 17:25:01 tarm kernel: [ 1362.125214] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:25:03 tarm kernel: [ 1364.625011] __ratelimit: 13 messages suppressed
May 26 17:25:03 tarm kernel: [ 1364.625239] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:25:09 tarm kernel: [ 1370.625010] __ratelimit: 27 messages suppressed
May 26 17:25:09 tarm kernel: [ 1370.625247] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:25:24 tarm kernel: [ 1385.625023] __ratelimit: 13 messages suppressed
May 26 17:25:24 tarm kernel: [ 1385.625231] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:25:24 tarm kernel: [ 1385.625374] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:25:24 tarm kernel: [ 1385.625510] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:25:29 tarm kernel: [ 1390.125013] __ratelimit: 25 messages suppressed
May 26 17:25:29 tarm kernel: [ 1390.125240] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:25:36 tarm kernel: [ 1397.125009] __ratelimit: 20 messages suppressed
May 26 17:25:36 tarm kernel: [ 1397.125254] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:25:38 tarm kernel: [ 1399.625042] __ratelimit: 20 messages suppressed
May 26 17:25:38 tarm kernel: [ 1399.625259] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:25:54 tarm kernel: [ 1415.625005] __ratelimit: 41 messages suppressed
May 26 17:25:54 tarm kernel: [ 1415.625225] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:25:54 tarm kernel: [ 1415.625370] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:25:54 tarm kernel: [ 1415.625506] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:26:27 tarm kernel: [ 1448.625114] __ratelimit: 11 messages suppressed
May 26 17:26:27 tarm kernel: [ 1448.625339] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:26:27 tarm kernel: [ 1448.625508] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:26:27 tarm kernel: [ 1448.625693] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:26:27 tarm kernel: [ 1448.625829] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:26:27 tarm kernel: [ 1448.625957] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:26:27 tarm kernel: [ 1448.626090] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:26:54 tarm kernel: [ 1476.125842] __ratelimit: 8 messages suppressed
May 26 17:26:54 tarm kernel: [ 1476.126064] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:26:54 tarm kernel: [ 1476.126209] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:26:54 tarm kernel: [ 1476.126346] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:26:54 tarm kernel: [ 1476.126485] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:26:54 tarm kernel: [ 1476.126616] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:26:54 tarm kernel: [ 1476.126753] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:27:07 tarm kernel: [ 1488.625025] __ratelimit: 8 messages suppressed
May 26 17:27:07 tarm kernel: [ 1488.625264] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:27:07 tarm kernel: [ 1488.625406] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:27:09 tarm kernel: [ 1491.128646] __ratelimit: 12 messages suppressed
May 26 17:27:09 tarm kernel: [ 1491.128868] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:27:14 tarm kernel: [ 1496.125016] __ratelimit: 27 messages suppressed
May 26 17:27:14 tarm kernel: [ 1496.125257] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:27:21 tarm kernel: [ 1502.625087] __ratelimit: 34 messages suppressed
May 26 17:27:21 tarm kernel: [ 1502.625320] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:27:26 tarm kernel: [ 1507.625104] __ratelimit: 13 messages suppressed
May 26 17:27:26 tarm kernel: [ 1507.625321] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:27:54 tarm kernel: [ 1536.125010] __ratelimit: 18 messages suppressed
May 26 17:27:54 tarm kernel: [ 1536.125254] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:27:54 tarm kernel: [ 1536.125395] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:27:54 tarm kernel: [ 1536.125529] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:27:54 tarm kernel: [ 1536.125666] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:27:54 tarm kernel: [ 1536.125794] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:27:54 tarm kernel: [ 1536.125928] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:28:35 tarm kernel: [ 1577.125012] __ratelimit: 15 messages suppressed
May 26 17:28:35 tarm kernel: [ 1577.125259] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:28:35 tarm kernel: [ 1577.125429] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:28:35 tarm kernel: [ 1577.125565] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:28:35 tarm kernel: [ 1577.125702] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:28:35 tarm kernel: [ 1577.125831] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:28:35 tarm kernel: [ 1577.125965] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:28:35 tarm kernel: [ 1577.126019] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:28:36 tarm kernel: [ 1577.625003] cpufreq-core: target for CPU 0: 914285 kHz, relation 0
May 26 17:28:55 tarm kernel: [ 1596.625005] __ratelimit: 13 messages suppressed
May 26 17:28:55 tarm kernel: [ 1596.625226] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:28:55 tarm kernel: [ 1596.625396] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:28:55 tarm kernel: [ 1596.625533] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:28:55 tarm kernel: [ 1596.625686] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:29:04 tarm kernel: [ 1605.626418] __ratelimit: 10 messages suppressed
May 26 17:29:04 tarm kernel: [ 1605.626630] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:29:04 tarm kernel: [ 1605.626772] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:29:24 tarm kernel: [ 1625.625002] __ratelimit: 40 messages suppressed
May 26 17:29:24 tarm kernel: [ 1625.625218] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:29:24 tarm kernel: [ 1625.625363] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:29:24 tarm kernel: [ 1625.625501] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:29:24 tarm kernel: [ 1625.625643] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:29:39 tarm kernel: [ 1641.125020] __ratelimit: 31 messages suppressed
May 26 17:29:39 tarm kernel: [ 1641.125248] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:29:39 tarm kernel: [ 1641.125387] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:29:39 tarm kernel: [ 1641.125519] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:29:43 tarm kernel: [ 1644.624994] __ratelimit: 16 messages suppressed
May 26 17:29:43 tarm kernel: [ 1644.625160] cpufreq-core: target for CPU 0: 152342 kHz, relation 0
May 26 17:30:05 tarm kernel: [ 1666.625410] __ratelimit: 6 messages suppressed
May 26 17:30:05 tarm kernel: [ 1666.625629] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:30:05 tarm kernel: [ 1666.625774] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:30:05 tarm kernel: [ 1666.625912] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:30:05 tarm kernel: [ 1666.626054] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:30:12 tarm kernel: [ 1674.125189] __ratelimit: 17 messages suppressed
May 26 17:30:12 tarm kernel: [ 1674.125425] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:30:13 tarm kernel: [ 1674.624988] __ratelimit: 6 messages suppressed
May 26 17:30:13 tarm kernel: [ 1674.625130] cpufreq-core: target for CPU 0: 0 kHz, relation 0
May 26 17:30:18 tarm kernel: [ 1680.124993] __ratelimit: 13 messages suppressed
May 26 17:30:18 tarm kernel: [ 1680.125137] cpufreq-core: target for CPU 0: 57142 kHz, relation 0
May 26 17:30:23 tarm kernel: [ 1684.625011] __ratelimit: 41 messages suppressed
May 26 17:30:23 tarm kernel: [ 1684.625238] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:30:25 tarm kernel: [ 1687.103612] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:30:25 tarm kernel: [ 1687.103851] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:30:25 tarm kernel: [ 1687.103983] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:30:25 tarm kernel: [ 1687.104121] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:30:25 tarm kernel: [ 1687.104257] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:30:25 tarm kernel: [ 1687.104385] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
May 26 17:30:25 tarm kernel: [ 1687.104521] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
May 26 17:30:25 tarm kernel: [ 1687.104656] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
May 26 17:30:25 tarm kernel: [ 1687.104788] cpufreq-core: governor: change or update limits
May 26 17:30:25 tarm kernel: [ 1687.105041] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:30:33 tarm kernel: [ 1695.412124] __ratelimit: 25 messages suppressed
May 26 17:30:33 tarm kernel: [ 1695.412329] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
May 26 17:30:33 tarm kernel: [ 1695.412490] cpufreq-core: updating policy for CPU 0
May 26 17:30:33 tarm kernel: [ 1695.412623] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:30:33 tarm kernel: [ 1695.412757] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:30:33 tarm kernel: [ 1695.413087] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:30:33 tarm kernel: [ 1695.413265] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:30:33 tarm kernel: [ 1695.413402] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:30:33 tarm kernel: [ 1695.413529] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:30:33 tarm kernel: [ 1695.413664] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:30:33 tarm kernel: [ 1695.413798] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 17:30:33 tarm kernel: [ 1695.413929] cpufreq-core: governor: change or update limits
May 26 17:30:33 tarm kernel: [ 1695.414056] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:30:51 tarm kernel: [ 1712.625338] __ratelimit: 3 messages suppressed
May 26 17:30:51 tarm kernel: [ 1712.625566] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:30:51 tarm kernel: [ 1712.625711] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:30:51 tarm kernel: [ 1712.625863] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:30:55 tarm kernel: [ 1716.625004] __ratelimit: 11 messages suppressed
May 26 17:30:55 tarm kernel: [ 1716.625234] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:30:58 tarm kernel: [ 1719.625020] __ratelimit: 20 messages suppressed
May 26 17:30:58 tarm kernel: [ 1719.625245] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:31:08 tarm kernel: [ 1729.625013] __ratelimit: 20 messages suppressed
May 26 17:31:08 tarm kernel: [ 1729.625257] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:31:08 tarm kernel: [ 1729.625405] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:31:55 tarm kernel: [ 1777.125078] __ratelimit: 33 messages suppressed
May 26 17:31:55 tarm kernel: [ 1777.125305] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:31:55 tarm kernel: [ 1777.125462] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:31:55 tarm kernel: [ 1777.125596] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:31:55 tarm kernel: [ 1777.125733] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:31:55 tarm kernel: [ 1777.125862] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:31:55 tarm kernel: [ 1777.126989] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:31:55 tarm kernel: [ 1777.127043] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:31:56 tarm kernel: [ 1777.625029] cpufreq-core: target for CPU 0: 1257142 kHz, relation 0
May 26 17:31:56 tarm kernel: [ 1777.625190] acpi-cpufreq: acpi_cpufreq_target 1257142 (0)
May 26 17:32:08 tarm kernel: [ 1789.625048] __ratelimit: 12 messages suppressed
May 26 17:32:08 tarm kernel: [ 1789.625277] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:32:08 tarm kernel: [ 1789.625420] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:32:08 tarm kernel: [ 1789.625554] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:32:27 tarm kernel: [ 1808.625076] __ratelimit: 23 messages suppressed
May 26 17:32:27 tarm kernel: [ 1808.625314] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:32:27 tarm kernel: [ 1808.625477] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:32:27 tarm kernel: [ 1808.625611] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:32:28 tarm kernel: [ 1809.625036] __ratelimit: 11 messages suppressed
May 26 17:32:28 tarm kernel: [ 1809.625204] cpufreq-core: target for CPU 0: 594285 kHz, relation 0
May 26 17:32:55 tarm kernel: [ 1837.125529] __ratelimit: 6 messages suppressed
May 26 17:32:55 tarm kernel: [ 1837.125771] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:32:55 tarm kernel: [ 1837.125927] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:32:55 tarm kernel: [ 1837.126060] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:32:55 tarm kernel: [ 1837.126220] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:32:55 tarm kernel: [ 1837.126384] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:33:08 tarm kernel: [ 1850.124998] __ratelimit: 9 messages suppressed
May 26 17:33:08 tarm kernel: [ 1850.125223] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:33:08 tarm kernel: [ 1850.125389] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:33:08 tarm kernel: [ 1850.125546] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:33:15 tarm kernel: [ 1856.625076] __ratelimit: 11 messages suppressed
May 26 17:33:15 tarm kernel: [ 1856.625322] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:33:22 tarm kernel: [ 1864.124999] __ratelimit: 13 messages suppressed
May 26 17:33:22 tarm kernel: [ 1864.125220] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:33:23 tarm kernel: [ 1864.624994] __ratelimit: 6 messages suppressed
May 26 17:33:23 tarm kernel: [ 1864.625132] cpufreq-core: target for CPU 0: 0 kHz, relation 0
May 26 17:33:37 tarm kernel: [ 1878.625014] __ratelimit: 60 messages suppressed
May 26 17:33:37 tarm kernel: [ 1878.625252] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:33:37 tarm kernel: [ 1878.625420] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:33:38 tarm kernel: [ 1879.624989] __ratelimit: 10 messages suppressed
May 26 17:33:38 tarm kernel: [ 1879.625128] cpufreq-core: target for CPU 0: 228571 kHz, relation 0
May 26 17:33:43 tarm kernel: [ 1884.626773] __ratelimit: 20 messages suppressed
May 26 17:33:43 tarm kernel: [ 1884.626985] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:33:49 tarm kernel: [ 1891.128517] __ratelimit: 34 messages suppressed
May 26 17:33:49 tarm kernel: [ 1891.128729] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:33:53 tarm kernel: [ 1894.624989] __ratelimit: 27 messages suppressed
May 26 17:33:53 tarm kernel: [ 1894.625138] cpufreq-core: target for CPU 0: 914285 kHz, relation 0
May 26 17:34:10 tarm kernel: [ 1911.625009] __ratelimit: 27 messages suppressed
May 26 17:34:10 tarm kernel: [ 1911.625242] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:34:10 tarm kernel: [ 1911.625381] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:34:10 tarm kernel: [ 1911.625513] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:34:57 tarm kernel: [ 1959.125001] __ratelimit: 25 messages suppressed
May 26 17:34:57 tarm kernel: [ 1959.125227] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:34:57 tarm kernel: [ 1959.125397] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:34:57 tarm kernel: [ 1959.125532] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:34:57 tarm kernel: [ 1959.125670] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:34:57 tarm kernel: [ 1959.125798] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:34:57 tarm kernel: [ 1959.125931] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:34:57 tarm kernel: [ 1959.125986] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:34:58 tarm kernel: [ 1959.624990] cpufreq-core: target for CPU 0: 1257142 kHz, relation 0
May 26 17:34:58 tarm kernel: [ 1959.625142] acpi-cpufreq: acpi_cpufreq_target 1257142 (0)
May 26 17:34:58 tarm kernel: [ 1959.625221] freq-table: request for target 1257142 kHz (relation: 0) for cpu 0
May 26 17:35:03 tarm kernel: [ 1964.624997] __ratelimit: 39 messages suppressed
May 26 17:35:03 tarm kernel: [ 1964.625162] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:35:09 tarm kernel: [ 1970.625110] __ratelimit: 34 messages suppressed
May 26 17:35:09 tarm kernel: [ 1970.625347] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:35:13 tarm kernel: [ 1974.625010] __ratelimit: 39 messages suppressed
May 26 17:35:13 tarm kernel: [ 1974.625164] cpufreq-core: target for CPU 0: 914285 kHz, relation 0
May 26 17:35:18 tarm kernel: [ 1979.624990] __ratelimit: 27 messages suppressed
May 26 17:35:18 tarm kernel: [ 1979.625150] cpufreq-core: target for CPU 0: 137142 kHz, relation 0
May 26 17:35:23 tarm kernel: [ 1984.625099] __ratelimit: 13 messages suppressed
May 26 17:35:23 tarm kernel: [ 1984.625242] cpufreq-core: target for CPU 0: 228571 kHz, relation 0
May 26 17:35:28 tarm kernel: [ 1989.625013] __ratelimit: 20 messages suppressed
May 26 17:35:28 tarm kernel: [ 1989.625247] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:35:53 tarm kernel: [ 2014.625029] __ratelimit: 13 messages suppressed
May 26 17:35:53 tarm kernel: [ 2014.625260] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:35:53 tarm kernel: [ 2014.625408] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:35:53 tarm kernel: [ 2014.625545] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:35:53 tarm kernel: [ 2014.625688] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:35:53 tarm kernel: [ 2014.625830] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:35:58 tarm kernel: [ 2020.124991] __ratelimit: 49 messages suppressed
May 26 17:35:58 tarm kernel: [ 2020.125144] cpufreq-core: target for CPU 0: 960000 kHz, relation 0
May 26 17:36:04 tarm kernel: [ 2025.625733] __ratelimit: 27 messages suppressed
May 26 17:36:04 tarm kernel: [ 2025.625970] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:36:08 tarm kernel: [ 2030.124999] __ratelimit: 27 messages suppressed
May 26 17:36:08 tarm kernel: [ 2030.125208] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:36:45 tarm kernel: [ 2066.624998] __ratelimit: 13 messages suppressed
May 26 17:36:45 tarm kernel: [ 2066.625471] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:36:45 tarm kernel: [ 2066.625649] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:36:45 tarm kernel: [ 2066.625789] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:36:45 tarm kernel: [ 2066.625927] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:36:45 tarm kernel: [ 2066.626087] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:36:45 tarm kernel: [ 2066.626225] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:36:45 tarm kernel: [ 2066.626279] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:36:56 tarm kernel: [ 2077.625025] __ratelimit: 21 messages suppressed
May 26 17:36:56 tarm kernel: [ 2077.625259] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:36:56 tarm kernel: [ 2077.625402] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:37:32 tarm kernel: [ 2114.125331] __ratelimit: 12 messages suppressed
May 26 17:37:32 tarm kernel: [ 2114.125558] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:37:32 tarm kernel: [ 2114.125703] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:37:32 tarm kernel: [ 2114.125839] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:37:32 tarm kernel: [ 2114.125978] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:37:32 tarm kernel: [ 2114.126110] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:37:32 tarm kernel: [ 2114.126249] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:37:32 tarm kernel: [ 2114.126305] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:37:33 tarm kernel: [ 2114.624991] cpufreq-core: target for CPU 0: 1771428 kHz, relation 0
May 26 17:37:38 tarm kernel: [ 2120.125076] __ratelimit: 11 messages suppressed
May 26 17:37:38 tarm kernel: [ 2120.125306] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:37:43 tarm kernel: [ 2124.625018] __ratelimit: 27 messages suppressed
May 26 17:37:43 tarm kernel: [ 2124.625164] cpufreq-core: target for CPU 0: 514285 kHz, relation 0
May 26 17:37:51 tarm kernel: [ 2133.125018] __ratelimit: 6 messages suppressed
May 26 17:37:51 tarm kernel: [ 2133.125274] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:37:53 tarm kernel: [ 2135.124987] __ratelimit: 20 messages suppressed
May 26 17:37:53 tarm kernel: [ 2135.125133] cpufreq-core: target for CPU 0: 400000 kHz, relation 0
May 26 17:38:08 tarm kernel: [ 2150.125024] __ratelimit: 20 messages suppressed
May 26 17:38:08 tarm kernel: [ 2150.125263] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:38:08 tarm kernel: [ 2150.125406] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:38:08 tarm kernel: [ 2150.125541] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:38:44 tarm kernel: [ 2186.125030] __ratelimit: 39 messages suppressed
May 26 17:38:44 tarm kernel: [ 2186.125274] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:38:44 tarm kernel: [ 2186.125419] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:38:44 tarm kernel: [ 2186.125554] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:38:44 tarm kernel: [ 2186.125692] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:38:44 tarm kernel: [ 2186.125950] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:38:44 tarm kernel: [ 2186.126086] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:38:44 tarm kernel: [ 2186.126140] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:39:42 tarm kernel: [ 2244.125003] __ratelimit: 7 messages suppressed
May 26 17:39:42 tarm kernel: [ 2244.125386] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:39:42 tarm kernel: [ 2244.125533] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:39:42 tarm kernel: [ 2244.125668] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:39:42 tarm kernel: [ 2244.125805] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:39:42 tarm kernel: [ 2244.125933] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:39:42 tarm kernel: [ 2244.126067] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:39:42 tarm kernel: [ 2244.126122] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:39:43 tarm kernel: [ 2244.624993] cpufreq-core: target for CPU 0: 1142857 kHz, relation 0
May 26 17:39:43 tarm kernel: [ 2244.625151] acpi-cpufreq: acpi_cpufreq_target 1142857 (0)
May 26 17:39:43 tarm kernel: [ 2244.625231] freq-table: request for target 1142857 kHz (relation: 0) for cpu 0
May 26 17:39:47 tarm kernel: [ 2249.124999] __ratelimit: 11 messages suppressed
May 26 17:39:47 tarm kernel: [ 2249.125216] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:39:55 tarm kernel: [ 2257.125017] __ratelimit: 27 messages suppressed
May 26 17:39:55 tarm kernel: [ 2257.125257] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:39:57 tarm kernel: [ 2259.124988] __ratelimit: 20 messages suppressed
May 26 17:39:57 tarm kernel: [ 2259.125137] cpufreq-core: target for CPU 0: 342857 kHz, relation 0
May 26 17:40:03 tarm kernel: [ 2264.625779] __ratelimit: 6 messages suppressed
May 26 17:40:03 tarm kernel: [ 2264.626008] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:40:08 tarm kernel: [ 2269.625005] __ratelimit: 13 messages suppressed
May 26 17:40:08 tarm kernel: [ 2269.625224] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:40:16 tarm kernel: [ 2277.625001] __ratelimit: 13 messages suppressed
May 26 17:40:16 tarm kernel: [ 2277.625225] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:40:57 tarm kernel: [ 2318.625170] __ratelimit: 13 messages suppressed
May 26 17:40:57 tarm kernel: [ 2318.625402] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:40:57 tarm kernel: [ 2318.625545] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:40:57 tarm kernel: [ 2318.625680] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:40:57 tarm kernel: [ 2318.625833] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:40:57 tarm kernel: [ 2318.625962] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:40:57 tarm kernel: [ 2318.626095] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:40:57 tarm kernel: [ 2318.626149] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:40:57 tarm kernel: [ 2319.124990] cpufreq-core: target for CPU 0: 400000 kHz, relation 0
May 26 17:40:57 tarm kernel: [ 2319.125141] acpi-cpufreq: acpi_cpufreq_target 400000 (0)
May 26 17:41:07 tarm kernel: [ 2329.125011] __ratelimit: 5 messages suppressed
May 26 17:41:07 tarm kernel: [ 2329.125242] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:41:07 tarm kernel: [ 2329.125381] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:41:13 tarm kernel: [ 2334.625002] __ratelimit: 33 messages suppressed
May 26 17:41:13 tarm kernel: [ 2334.625220] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:41:19 tarm kernel: [ 2340.625925] __ratelimit: 27 messages suppressed
May 26 17:41:19 tarm kernel: [ 2340.626164] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:41:22 tarm kernel: [ 2344.125010] __ratelimit: 27 messages suppressed
May 26 17:41:22 tarm kernel: [ 2344.125242] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:42:05 tarm kernel: [ 2386.625014] __ratelimit: 41 messages suppressed
May 26 17:42:05 tarm kernel: [ 2386.625238] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:42:05 tarm kernel: [ 2386.625411] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:42:05 tarm kernel: [ 2386.625548] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:42:05 tarm kernel: [ 2386.625689] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:42:05 tarm kernel: [ 2386.625818] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:42:05 tarm kernel: [ 2386.626082] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:42:05 tarm kernel: [ 2386.626137] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:42:05 tarm kernel: [ 2387.124995] cpufreq-core: target for CPU 0: 114285 kHz, relation 0
May 26 17:42:23 tarm kernel: [ 2405.126157] __ratelimit: 6 messages suppressed
May 26 17:42:23 tarm kernel: [ 2405.126390] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:42:23 tarm kernel: [ 2405.126536] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:42:23 tarm kernel: [ 2405.126671] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:42:23 tarm kernel: [ 2405.126810] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:42:27 tarm kernel: [ 2409.124997] __ratelimit: 31 messages suppressed
May 26 17:42:27 tarm kernel: [ 2409.125156] cpufreq-core: target for CPU 0: 960000 kHz, relation 0
May 26 17:42:57 tarm kernel: [ 2439.125015] __ratelimit: 13 messages suppressed
May 26 17:42:57 tarm kernel: [ 2439.125247] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:42:57 tarm kernel: [ 2439.125392] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:42:57 tarm kernel: [ 2439.125526] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:42:57 tarm kernel: [ 2439.125664] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:42:57 tarm kernel: [ 2439.125792] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:42:57 tarm kernel: [ 2439.125926] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:44:08 tarm kernel: [ 2509.627811] __ratelimit: 15 messages suppressed
May 26 17:44:08 tarm kernel: [ 2509.628028] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:44:08 tarm kernel: [ 2509.628172] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:44:08 tarm kernel: [ 2509.628479] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:44:08 tarm kernel: [ 2509.628623] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:44:08 tarm kernel: [ 2509.628782] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:44:08 tarm kernel: [ 2509.628934] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:44:08 tarm kernel: [ 2509.629114] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:44:08 tarm kernel: [ 2510.128990] cpufreq-core: target for CPU 0: 1200000 kHz, relation 0
May 26 17:44:08 tarm kernel: [ 2510.129147] acpi-cpufreq: acpi_cpufreq_target 1200000 (0)
May 26 17:44:08 tarm kernel: [ 2510.129225] freq-table: request for target 1200000 kHz (relation: 0) for cpu 0
May 26 17:45:53 tarm kernel: [ 2614.625003] __ratelimit: 11 messages suppressed
May 26 17:45:53 tarm kernel: [ 2614.625214] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:45:53 tarm kernel: [ 2614.625359] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:45:53 tarm kernel: [ 2614.625497] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:45:53 tarm kernel: [ 2614.625638] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:45:53 tarm kernel: [ 2614.625773] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:45:53 tarm kernel: [ 2614.625914] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:45:53 tarm kernel: [ 2614.625971] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:45:53 tarm kernel: [ 2615.124994] cpufreq-core: target for CPU 0: 0 kHz, relation 0
May 26 17:45:53 tarm kernel: [ 2615.125153] acpi-cpufreq: acpi_cpufreq_target 0 (0)
May 26 17:45:53 tarm kernel: [ 2615.125213] freq-table: request for target 0 kHz (relation: 0) for cpu 0
May 26 17:45:58 tarm kernel: [ 2620.125038] __ratelimit: 4 messages suppressed
May 26 17:45:58 tarm kernel: [ 2620.125262] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:46:30 tarm kernel: [ 2652.125063] __ratelimit: 13 messages suppressed
May 26 17:46:30 tarm kernel: [ 2652.125294] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:46:30 tarm kernel: [ 2652.125434] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:46:30 tarm kernel: [ 2652.125566] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:46:30 tarm kernel: [ 2652.125702] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:46:30 tarm kernel: [ 2652.125831] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:46:30 tarm kernel: [ 2652.125965] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:47:03 tarm kernel: [ 2684.630045] __ratelimit: 8 messages suppressed
May 26 17:47:03 tarm kernel: [ 2684.630290] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:47:03 tarm kernel: [ 2684.630432] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:47:03 tarm kernel: [ 2684.630565] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:47:03 tarm kernel: [ 2684.630702] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:47:03 tarm kernel: [ 2684.630832] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:47:03 tarm kernel: [ 2684.630968] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:47:03 tarm kernel: [ 2684.631023] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:47:24 tarm kernel: [ 2706.124999] __ratelimit: 7 messages suppressed
May 26 17:47:24 tarm kernel: [ 2706.125221] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:47:24 tarm kernel: [ 2706.125385] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:47:24 tarm kernel: [ 2706.125520] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:47:24 tarm kernel: [ 2706.125658] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:47:58 tarm kernel: [ 2740.124998] __ratelimit: 10 messages suppressed
May 26 17:47:58 tarm kernel: [ 2740.125220] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:47:58 tarm kernel: [ 2740.125409] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:47:58 tarm kernel: [ 2740.125545] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:47:58 tarm kernel: [ 2740.125683] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:47:58 tarm kernel: [ 2740.125811] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:47:58 tarm kernel: [ 2740.125946] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:47:58 tarm kernel: [ 2740.126000] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:48:09 tarm kernel: [ 2751.125047] __ratelimit: 21 messages suppressed
May 26 17:48:09 tarm kernel: [ 2751.125269] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:48:09 tarm kernel: [ 2751.125434] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:48:58 tarm kernel: [ 2800.125099] __ratelimit: 33 messages suppressed
May 26 17:48:58 tarm kernel: [ 2800.125338] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:48:58 tarm kernel: [ 2800.125482] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:48:58 tarm kernel: [ 2800.125617] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:48:58 tarm kernel: [ 2800.125756] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:48:58 tarm kernel: [ 2800.125886] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:48:58 tarm kernel: [ 2800.126021] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:48:58 tarm kernel: [ 2800.126075] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:48:59 tarm kernel: [ 2801.124990] cpufreq-core: target for CPU 0: 285714 kHz, relation 0
May 26 17:48:59 tarm kernel: [ 2801.125146] acpi-cpufreq: acpi_cpufreq_target 285714 (0)
May 26 17:48:59 tarm kernel: [ 2801.125221] freq-table: request for target 285714 kHz (relation: 0) for cpu 0
May 26 17:49:05 tarm kernel: [ 2806.625051] __ratelimit: 4 messages suppressed
May 26 17:49:05 tarm kernel: [ 2806.625274] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:49:36 tarm kernel: [ 2837.625751] __ratelimit: 13 messages suppressed
May 26 17:49:36 tarm kernel: [ 2837.625989] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:49:36 tarm kernel: [ 2837.626134] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:49:36 tarm kernel: [ 2837.626432] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:49:36 tarm kernel: [ 2837.626578] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:49:36 tarm kernel: [ 2837.626711] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:49:36 tarm kernel: [ 2837.626849] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:49:48 tarm kernel: [ 2850.125068] __ratelimit: 8 messages suppressed
May 26 17:49:48 tarm kernel: [ 2850.125309] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:49:48 tarm kernel: [ 2850.125449] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:49:48 tarm kernel: [ 2850.125581] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:50:37 tarm kernel: [ 2898.625001] __ratelimit: 11 messages suppressed
May 26 17:50:37 tarm kernel: [ 2898.625247] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:50:37 tarm kernel: [ 2898.625393] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:50:37 tarm kernel: [ 2898.625543] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:50:37 tarm kernel: [ 2898.625682] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:50:37 tarm kernel: [ 2898.625811] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:50:37 tarm kernel: [ 2898.625945] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:50:37 tarm kernel: [ 2898.625999] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:50:37 tarm kernel: [ 2899.124989] cpufreq-core: target for CPU 0: 0 kHz, relation 0
May 26 17:50:37 tarm kernel: [ 2899.125144] acpi-cpufreq: acpi_cpufreq_target 0 (0)
May 26 17:51:20 tarm kernel: [ 2941.625016] __ratelimit: 5 messages suppressed
May 26 17:51:20 tarm kernel: [ 2941.625237] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:51:20 tarm kernel: [ 2941.625406] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:51:20 tarm kernel: [ 2941.625546] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:51:20 tarm kernel: [ 2941.625689] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:51:20 tarm kernel: [ 2941.625824] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:51:20 tarm kernel: [ 2941.626027] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:51:20 tarm kernel: [ 2941.626285] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:51:20 tarm kernel: [ 2942.124990] cpufreq-core: target for CPU 0: 1085714 kHz, relation 0
May 26 17:51:20 tarm kernel: [ 2942.125146] acpi-cpufreq: acpi_cpufreq_target 1085714 (0)
May 26 17:51:23 tarm kernel: [ 2945.124994] __ratelimit: 31 messages suppressed
May 26 17:51:23 tarm kernel: [ 2945.125180] cpufreq-core: target for CPU 0: 944171 kHz, relation 0
May 26 17:51:28 tarm kernel: [ 2950.124996] __ratelimit: 37 messages suppressed
May 26 17:51:28 tarm kernel: [ 2950.125182] cpufreq-core: target for CPU 0: 852800 kHz, relation 0
May 26 17:51:55 tarm kernel: [ 2977.125010] __ratelimit: 26 messages suppressed
May 26 17:51:55 tarm kernel: [ 2977.125244] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:51:55 tarm kernel: [ 2977.125384] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:51:55 tarm kernel: [ 2977.125516] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:51:55 tarm kernel: [ 2977.125652] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:51:55 tarm kernel: [ 2977.125806] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:51:58 tarm kernel: [ 2980.125002] __ratelimit: 30 messages suppressed
May 26 17:51:58 tarm kernel: [ 2980.125197] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:52:03 tarm kernel: [ 2984.753859] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:52:03 tarm kernel: [ 2984.754110] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:52:03 tarm kernel: [ 2984.754246] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:52:03 tarm kernel: [ 2984.754387] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:52:03 tarm kernel: [ 2984.754526] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:52:03 tarm kernel: [ 2984.754657] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
May 26 17:52:03 tarm kernel: [ 2984.754935] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
May 26 17:52:03 tarm kernel: [ 2984.755073] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
May 26 17:52:03 tarm kernel: [ 2984.755208] cpufreq-core: governor: change or update limits
May 26 17:52:03 tarm kernel: [ 2984.755339] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:52:15 tarm kernel: [ 2997.184583] __ratelimit: 39 messages suppressed
May 26 17:52:15 tarm kernel: [ 2997.184789] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
May 26 17:52:15 tarm kernel: [ 2997.185072] cpufreq-core: updating policy for CPU 0
May 26 17:52:15 tarm kernel: [ 2997.185310] acpi-cpufreq: get_cur_freq_on_cpu (0)
May 26 17:52:15 tarm kernel: [ 2997.185448] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:52:15 tarm kernel: [ 2997.185583] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:52:15 tarm kernel: [ 2997.185710] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:52:15 tarm kernel: [ 2997.185846] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:52:15 tarm kernel: [ 2997.186002] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:52:15 tarm kernel: [ 2997.186153] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:52:15 tarm kernel: [ 2997.186289] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:52:15 tarm kernel: [ 2997.186423] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 17:52:15 tarm kernel: [ 2997.186555] cpufreq-core: governor: change or update limits
May 26 17:52:15 tarm kernel: [ 2997.186682] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:53:50 tarm kernel: [ 3091.625021] __ratelimit: 2 messages suppressed
May 26 17:53:50 tarm kernel: [ 3091.625236] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:53:50 tarm kernel: [ 3091.625380] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:53:50 tarm kernel: [ 3091.625514] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:53:50 tarm kernel: [ 3091.625653] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:53:50 tarm kernel: [ 3091.625785] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:53:50 tarm kernel: [ 3091.626086] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:53:50 tarm kernel: [ 3091.626142] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:53:50 tarm kernel: [ 3092.124989] cpufreq-core: target for CPU 0: 171428 kHz, relation 0
May 26 17:53:50 tarm kernel: [ 3092.125141] acpi-cpufreq: acpi_cpufreq_target 171428 (0)
May 26 17:53:50 tarm kernel: [ 3092.125227] freq-table: request for target 171428 kHz (relation: 0) for cpu 0
May 26 17:54:23 tarm kernel: [ 3125.125835] __ratelimit: 4 messages suppressed
May 26 17:54:23 tarm kernel: [ 3125.126073] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:54:23 tarm kernel: [ 3125.126214] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:54:23 tarm kernel: [ 3125.126374] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:54:23 tarm kernel: [ 3125.126511] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:54:23 tarm kernel: [ 3125.126639] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:54:23 tarm kernel: [ 3125.126772] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:54:25 tarm kernel: [ 3126.625001] __ratelimit: 15 messages suppressed
May 26 17:54:25 tarm kernel: [ 3126.625156] cpufreq-core: target for CPU 0: 1600000 kHz, relation 0
May 26 17:54:59 tarm kernel: [ 3161.125068] __ratelimit: 13 messages suppressed
May 26 17:54:59 tarm kernel: [ 3161.125422] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:54:59 tarm kernel: [ 3161.125563] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:54:59 tarm kernel: [ 3161.125695] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:54:59 tarm kernel: [ 3161.125831] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:54:59 tarm kernel: [ 3161.125960] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:54:59 tarm kernel: [ 3161.126189] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:55:00 tarm kernel: [ 3161.624989] __ratelimit: 1 messages suppressed
May 26 17:55:00 tarm kernel: [ 3161.625138] cpufreq-core: target for CPU 0: 628571 kHz, relation 0
May 26 17:57:59 tarm kernel: [ 3341.125000] __ratelimit: 20 messages suppressed
May 26 17:57:59 tarm kernel: [ 3341.125237] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:57:59 tarm kernel: [ 3341.125407] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:57:59 tarm kernel: [ 3341.125542] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:57:59 tarm kernel: [ 3341.125680] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:57:59 tarm kernel: [ 3341.125808] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:57:59 tarm kernel: [ 3341.125941] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 17:57:59 tarm kernel: [ 3341.126003] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 17:58:00 tarm kernel: [ 3342.124989] cpufreq-core: target for CPU 0: 0 kHz, relation 0
May 26 17:58:00 tarm kernel: [ 3342.125176] acpi-cpufreq: acpi_cpufreq_target 0 (0)
May 26 17:58:00 tarm kernel: [ 3342.125238] freq-table: request for target 0 kHz (relation: 0) for cpu 0
May 26 17:58:09 tarm kernel: [ 3350.625020] __ratelimit: 4 messages suppressed
May 26 17:58:09 tarm kernel: [ 3350.625222] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:58:11 tarm kernel: [ 3353.124988] __ratelimit: 6 messages suppressed
May 26 17:58:11 tarm kernel: [ 3353.125210] cpufreq-core: target for CPU 0: 1600000 kHz, relation 0
May 26 17:58:16 tarm kernel: [ 3357.625011] __ratelimit: 13 messages suppressed
May 26 17:58:16 tarm kernel: [ 3357.625238] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:58:20 tarm kernel: [ 3361.625052] __ratelimit: 39 messages suppressed
May 26 17:58:20 tarm kernel: [ 3361.625267] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:58:24 tarm kernel: [ 3366.125013] __ratelimit: 48 messages suppressed
May 26 17:58:24 tarm kernel: [ 3366.125240] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:58:27 tarm kernel: [ 3368.864167] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:58:27 tarm kernel: [ 3368.864411] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:58:27 tarm kernel: [ 3368.864544] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:58:27 tarm kernel: [ 3368.864681] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:58:27 tarm kernel: [ 3368.864816] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:58:27 tarm kernel: [ 3368.864944] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
May 26 17:58:27 tarm kernel: [ 3368.865130] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
May 26 17:58:27 tarm kernel: [ 3368.865297] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
May 26 17:58:27 tarm kernel: [ 3368.865433] cpufreq-core: governor: change or update limits
May 26 17:58:27 tarm kernel: [ 3368.865564] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:58:43 tarm kernel: [ 3385.479447] __ratelimit: 30 messages suppressed
May 26 17:58:43 tarm kernel: [ 3385.479651] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
May 26 17:58:43 tarm kernel: [ 3385.479810] cpufreq-core: updating policy for CPU 0
May 26 17:58:43 tarm kernel: [ 3385.479938] acpi-cpufreq: get_cur_freq_on_cpu (0)
May 26 17:58:43 tarm kernel: [ 3385.480067] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:58:43 tarm kernel: [ 3385.480199] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:58:43 tarm kernel: [ 3385.480325] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:58:43 tarm kernel: [ 3385.480459] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:58:43 tarm kernel: [ 3385.480591] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:58:43 tarm kernel: [ 3385.480716] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:58:43 tarm kernel: [ 3385.480850] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:58:43 tarm kernel: [ 3385.481074] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 17:58:43 tarm kernel: [ 3385.481231] cpufreq-core: governor: change or update limits
May 26 17:58:43 tarm kernel: [ 3385.481361] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:59:07 tarm kernel: [ 3408.625001] __ratelimit: 2 messages suppressed
May 26 17:59:07 tarm kernel: [ 3408.625221] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:59:07 tarm kernel: [ 3408.625385] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:59:07 tarm kernel: [ 3408.625519] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:59:07 tarm kernel: [ 3408.625677] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:59:07 tarm kernel: [ 3408.625803] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:59:10 tarm kernel: [ 3411.625026] __ratelimit: 9 messages suppressed
May 26 17:59:10 tarm kernel: [ 3411.625265] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:59:36 tarm kernel: [ 3438.125078] __ratelimit: 13 messages suppressed
May 26 17:59:36 tarm kernel: [ 3438.125317] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:59:36 tarm kernel: [ 3438.125536] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 17:59:36 tarm kernel: [ 3438.125667] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 17:59:36 tarm kernel: [ 3438.125799] freq-table: target is 0 (2000000 kHz, 0)
May 26 17:59:36 tarm kernel: [ 3438.127191] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 17:59:39 tarm kernel: [ 3441.125011] __ratelimit: 16 messages suppressed
May 26 17:59:39 tarm kernel: [ 3441.125163] cpufreq-core: target for CPU 0: 571428 kHz, relation 0
May 26 17:59:44 tarm kernel: [ 3446.129064] __ratelimit: 51 messages suppressed
May 26 17:59:44 tarm kernel: [ 3446.129319] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 17:59:50 tarm kernel: [ 3451.625003] __ratelimit: 39 messages suppressed
May 26 17:59:50 tarm kernel: [ 3451.625174] cpufreq-core: target for CPU 0: 1142857 kHz, relation 0
May 26 17:59:54 tarm kernel: [ 3456.079363] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 17:59:54 tarm kernel: [ 3456.079519] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:59:54 tarm kernel: [ 3456.079577] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 17:59:54 tarm kernel: [ 3456.079647] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 17:59:54 tarm kernel: [ 3456.079707] acpi-cpufreq: acpi_cpufreq_verify
May 26 17:59:54 tarm kernel: [ 3456.079762] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
May 26 17:59:54 tarm kernel: [ 3456.079821] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
May 26 17:59:54 tarm kernel: [ 3456.079879] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
May 26 17:59:54 tarm kernel: [ 3456.079936] cpufreq-core: governor: change or update limits
May 26 17:59:54 tarm kernel: [ 3456.079992] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 17:59:54 tarm kernel: [ 3456.080058] cpufreq-core: target for CPU 0: 800000 kHz, relation 1
May 26 17:59:54 tarm kernel: [ 3456.080114] acpi-cpufreq: acpi_cpufreq_target 800000 (0)
May 26 17:59:54 tarm kernel: [ 3456.080196] freq-table: request for target 800000 kHz (relation: 1) for cpu 0
May 26 17:59:54 tarm kernel: [ 3456.080254] freq-table: target is 4 (800000 kHz, 4)
May 26 17:59:54 tarm kernel: [ 3456.080310] cpufreq-core: notification 0 of frequency transition to 800000 kHz
May 26 17:59:54 tarm kernel: [ 3456.080385] cpufreq-core: notification 1 of frequency transition to 800000 kHz
May 26 17:59:54 tarm kernel: [ 3456.080439] cpufreq-core: scaling loops_per_jiffy to 3195449 for frequency 800000 kHz
May 26 18:02:15 tarm kernel: [ 3597.291132] __ratelimit: 39 messages suppressed
May 26 18:02:15 tarm kernel: [ 3597.291342] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
May 26 18:02:15 tarm kernel: [ 3597.291480] cpufreq-core: updating policy for CPU 0
May 26 18:02:15 tarm kernel: [ 3597.291608] acpi-cpufreq: get_cur_freq_on_cpu (0)
May 26 18:02:15 tarm kernel: [ 3597.291734] acpi-cpufreq: get_cur_val = 100664850
May 26 18:02:15 tarm kernel: [ 3597.291859] acpi-cpufreq: cur freq = 800000
May 26 18:02:15 tarm kernel: [ 3597.291984] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 18:02:15 tarm kernel: [ 3597.292116] acpi-cpufreq: acpi_cpufreq_verify
May 26 18:02:15 tarm kernel: [ 3597.292241] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 18:02:15 tarm kernel: [ 3597.292377] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 18:02:15 tarm kernel: [ 3597.292546] acpi-cpufreq: acpi_cpufreq_verify
May 26 18:02:15 tarm kernel: [ 3597.292675] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 18:02:15 tarm kernel: [ 3597.292812] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 18:02:15 tarm kernel: [ 3597.293470] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 18:02:15 tarm kernel: [ 3597.293635] cpufreq-core: governor: change or update limits
May 26 18:02:15 tarm kernel: [ 3597.293768] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 18:02:17 tarm kernel: [ 3598.625022] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:02:17 tarm kernel: [ 3598.625266] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 18:02:17 tarm kernel: [ 3598.625404] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 18:02:17 tarm kernel: [ 3598.625541] freq-table: target is 0 (2000000 kHz, 0)
May 26 18:02:17 tarm kernel: [ 3598.625671] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 18:02:21 tarm kernel: [ 3602.625004] __ratelimit: 28 messages suppressed
May 26 18:02:21 tarm kernel: [ 3602.625238] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:02:26 tarm kernel: [ 3607.627568] __ratelimit: 39 messages suppressed
May 26 18:02:26 tarm kernel: [ 3607.627787] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:02:28 tarm kernel: [ 3609.767385] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 18:02:28 tarm kernel: [ 3609.767625] acpi-cpufreq: acpi_cpufreq_verify
May 26 18:02:28 tarm kernel: [ 3609.767757] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 18:02:28 tarm kernel: [ 3609.767895] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 18:02:28 tarm kernel: [ 3609.768031] acpi-cpufreq: acpi_cpufreq_verify
May 26 18:02:28 tarm kernel: [ 3609.768158] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
May 26 18:02:28 tarm kernel: [ 3609.768294] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
May 26 18:02:28 tarm kernel: [ 3609.768429] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
May 26 18:02:28 tarm kernel: [ 3609.768561] cpufreq-core: governor: change or update limits
May 26 18:02:28 tarm kernel: [ 3609.768689] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 18:04:20 tarm kernel: [ 3721.943273] __ratelimit: 18 messages suppressed
May 26 18:04:20 tarm kernel: [ 3721.943484] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
May 26 18:04:20 tarm kernel: [ 3721.943624] cpufreq-core: updating policy for CPU 0
May 26 18:04:20 tarm kernel: [ 3721.943754] acpi-cpufreq: get_cur_freq_on_cpu (0)
May 26 18:04:20 tarm kernel: [ 3721.943883] acpi-cpufreq: get_cur_val = 100664850
May 26 18:04:20 tarm kernel: [ 3721.944010] acpi-cpufreq: cur freq = 800000
May 26 18:04:20 tarm kernel: [ 3721.944137] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 18:04:20 tarm kernel: [ 3721.944271] acpi-cpufreq: acpi_cpufreq_verify
May 26 18:04:20 tarm kernel: [ 3721.944418] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 18:04:20 tarm kernel: [ 3721.944556] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 18:04:20 tarm kernel: [ 3721.944691] acpi-cpufreq: acpi_cpufreq_verify
May 26 18:04:20 tarm kernel: [ 3721.944818] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 18:04:20 tarm kernel: [ 3721.945412] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 18:04:20 tarm kernel: [ 3721.945579] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 18:04:20 tarm kernel: [ 3721.945714] cpufreq-core: governor: change or update limits
May 26 18:04:20 tarm kernel: [ 3721.945845] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 18:04:29 tarm kernel: [ 3730.625003] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:04:29 tarm kernel: [ 3730.625247] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 18:04:29 tarm kernel: [ 3730.625405] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 18:04:29 tarm kernel: [ 3730.625545] freq-table: target is 0 (2000000 kHz, 0)
May 26 18:04:29 tarm kernel: [ 3730.625674] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 18:04:29 tarm kernel: [ 3730.625808] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 18:04:30 tarm kernel: [ 3732.125001] __ratelimit: 8 messages suppressed
May 26 18:04:30 tarm kernel: [ 3732.125223] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:05:01 tarm kernel: [ 3762.625004] __ratelimit: 27 messages suppressed
May 26 18:05:01 tarm kernel: [ 3762.625230] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:05:01 tarm kernel: [ 3762.625371] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 18:05:01 tarm kernel: [ 3762.625503] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 18:05:01 tarm kernel: [ 3762.625639] freq-table: target is 0 (2000000 kHz, 0)
May 26 18:05:01 tarm kernel: [ 3762.625767] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 18:05:01 tarm kernel: [ 3762.625996] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 18:05:05 tarm kernel: [ 3767.125001] __ratelimit: 34 messages suppressed
May 26 18:05:05 tarm kernel: [ 3767.125153] cpufreq-core: target for CPU 0: 457142 kHz, relation 0
May 26 18:05:11 tarm kernel: [ 3772.625012] __ratelimit: 53 messages suppressed
May 26 18:05:11 tarm kernel: [ 3772.625165] cpufreq-core: target for CPU 0: 685714 kHz, relation 0
May 26 18:05:14 tarm kernel: [ 3775.942575] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 18:05:14 tarm kernel: [ 3775.942722] acpi-cpufreq: acpi_cpufreq_verify
May 26 18:05:14 tarm kernel: [ 3775.942782] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 18:05:14 tarm kernel: [ 3775.942844] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 18:05:14 tarm kernel: [ 3775.942905] acpi-cpufreq: acpi_cpufreq_verify
May 26 18:05:14 tarm kernel: [ 3775.942961] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
May 26 18:05:14 tarm kernel: [ 3775.943022] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
May 26 18:05:14 tarm kernel: [ 3775.943082] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
May 26 18:05:14 tarm kernel: [ 3775.943140] cpufreq-core: governor: change or update limits
May 26 18:05:14 tarm kernel: [ 3775.943197] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 18:05:14 tarm kernel: [ 3775.943255] cpufreq-core: target for CPU 0: 800000 kHz, relation 1
May 26 18:05:14 tarm kernel: [ 3775.943311] acpi-cpufreq: acpi_cpufreq_target 800000 (0)
May 26 18:05:14 tarm kernel: [ 3775.943369] freq-table: request for target 800000 kHz (relation: 1) for cpu 0
May 26 18:05:14 tarm kernel: [ 3775.943428] freq-table: target is 4 (800000 kHz, 4)
May 26 18:05:14 tarm kernel: [ 3775.943485] cpufreq-core: notification 0 of frequency transition to 800000 kHz
May 26 18:05:14 tarm kernel: [ 3775.943546] cpufreq-core: notification 1 of frequency transition to 800000 kHz
May 26 18:05:14 tarm kernel: [ 3775.943599] cpufreq-core: scaling loops_per_jiffy to 3195449 for frequency 800000 kHz
May 26 18:07:00 tarm kernel: [ 3881.874163] __ratelimit: 44 messages suppressed
May 26 18:07:00 tarm kernel: [ 3881.874373] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
May 26 18:07:00 tarm kernel: [ 3881.874512] cpufreq-core: updating policy for CPU 0
May 26 18:07:00 tarm kernel: [ 3881.874642] acpi-cpufreq: get_cur_freq_on_cpu (0)
May 26 18:07:00 tarm kernel: [ 3881.874770] acpi-cpufreq: get_cur_val = 100664850
May 26 18:07:00 tarm kernel: [ 3881.874896] acpi-cpufreq: cur freq = 800000
May 26 18:07:00 tarm kernel: [ 3881.875047] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 18:07:00 tarm kernel: [ 3881.875182] acpi-cpufreq: acpi_cpufreq_verify
May 26 18:07:00 tarm kernel: [ 3881.875310] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 18:07:00 tarm kernel: [ 3881.875447] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 18:07:00 tarm kernel: [ 3881.875583] acpi-cpufreq: acpi_cpufreq_verify
May 26 18:07:00 tarm kernel: [ 3881.875710] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 18:07:00 tarm kernel: [ 3881.875847] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 18:07:00 tarm kernel: [ 3881.875982] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 18:07:00 tarm kernel: [ 3881.876115] cpufreq-core: governor: change or update limits
May 26 18:07:00 tarm kernel: [ 3881.876243] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 18:07:01 tarm kernel: [ 3882.625011] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:07:01 tarm kernel: [ 3882.625258] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 18:07:01 tarm kernel: [ 3882.625399] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 18:07:01 tarm kernel: [ 3882.625541] freq-table: target is 0 (2000000 kHz, 0)
May 26 18:07:01 tarm kernel: [ 3882.625675] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 18:07:18 tarm kernel: [ 3899.625001] __ratelimit: 16 messages suppressed
May 26 18:07:18 tarm kernel: [ 3899.625229] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:07:18 tarm kernel: [ 3899.625400] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 18:07:18 tarm kernel: [ 3899.625536] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 18:09:01 tarm kernel: [ 4003.125000] __ratelimit: 11 messages suppressed
May 26 18:09:01 tarm kernel: [ 4003.125219] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:09:01 tarm kernel: [ 4003.125383] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 18:09:01 tarm kernel: [ 4003.125518] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 18:09:01 tarm kernel: [ 4003.125655] freq-table: target is 0 (2000000 kHz, 0)
May 26 18:09:01 tarm kernel: [ 4003.125785] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 18:09:01 tarm kernel: [ 4003.125920] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 18:09:01 tarm kernel: [ 4003.125974] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 18:09:02 tarm kernel: [ 4003.624990] cpufreq-core: target for CPU 0: 457142 kHz, relation 0
May 26 18:09:02 tarm kernel: [ 4003.625144] acpi-cpufreq: acpi_cpufreq_target 457142 (0)
May 26 18:09:02 tarm kernel: [ 4003.625219] freq-table: request for target 457142 kHz (relation: 0) for cpu 0
May 26 18:09:13 tarm kernel: [ 4014.625002] __ratelimit: 4 messages suppressed
May 26 18:09:13 tarm kernel: [ 4014.625228] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:09:13 tarm kernel: [ 4014.625394] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 18:09:47 tarm kernel: [ 4048.625002] __ratelimit: 19 messages suppressed
May 26 18:09:47 tarm kernel: [ 4048.625223] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:09:47 tarm kernel: [ 4048.625389] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 18:09:47 tarm kernel: [ 4048.625524] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 18:09:47 tarm kernel: [ 4048.625661] freq-table: target is 0 (2000000 kHz, 0)
May 26 18:09:47 tarm kernel: [ 4048.625791] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 18:09:47 tarm kernel: [ 4048.625926] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 18:09:47 tarm kernel: [ 4048.625990] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 18:09:52 tarm kernel: [ 4053.626605] __ratelimit: 33 messages suppressed
May 26 18:09:52 tarm kernel: [ 4053.626791] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:09:58 tarm kernel: [ 4060.133318] __ratelimit: 20 messages suppressed
May 26 18:09:58 tarm kernel: [ 4060.133559] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:10:01 tarm kernel: [ 4063.125021] __ratelimit: 13 messages suppressed
May 26 18:10:01 tarm kernel: [ 4063.125262] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:10:06 tarm kernel: [ 4068.125460] __ratelimit: 13 messages suppressed
May 26 18:10:06 tarm kernel: [ 4068.125699] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:10:12 tarm kernel: [ 4074.125037] __ratelimit: 20 messages suppressed
May 26 18:10:12 tarm kernel: [ 4074.125255] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:10:18 tarm kernel: [ 4079.626878] __ratelimit: 13 messages suppressed
May 26 18:10:18 tarm kernel: [ 4079.627098] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:10:24 tarm kernel: [ 4086.133059] __ratelimit: 20 messages suppressed
May 26 18:10:24 tarm kernel: [ 4086.133274] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:10:27 tarm kernel: [ 4088.624999] __ratelimit: 11 messages suppressed
May 26 18:10:27 tarm kernel: [ 4088.625151] cpufreq-core: target for CPU 0: 1142857 kHz, relation 0
May 26 18:10:32 tarm kernel: [ 4093.625002] __ratelimit: 27 messages suppressed
May 26 18:10:32 tarm kernel: [ 4093.625227] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:10:34 tarm kernel: [ 4095.755272] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 18:10:34 tarm kernel: [ 4095.755508] acpi-cpufreq: acpi_cpufreq_verify
May 26 18:10:34 tarm kernel: [ 4095.755642] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 18:10:34 tarm kernel: [ 4095.755780] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 18:10:34 tarm kernel: [ 4095.755916] acpi-cpufreq: acpi_cpufreq_verify
May 26 18:10:34 tarm kernel: [ 4095.756042] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
May 26 18:10:34 tarm kernel: [ 4095.756179] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
May 26 18:10:34 tarm kernel: [ 4095.756314] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
May 26 18:10:34 tarm kernel: [ 4095.756447] cpufreq-core: governor: change or update limits
May 26 18:10:34 tarm kernel: [ 4095.756575] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 18:12:34 tarm kernel: [ 4216.175207] __ratelimit: 39 messages suppressed
May 26 18:12:34 tarm kernel: [ 4216.175414] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
May 26 18:12:34 tarm kernel: [ 4216.175553] cpufreq-core: updating policy for CPU 0
May 26 18:12:34 tarm kernel: [ 4216.175682] acpi-cpufreq: get_cur_freq_on_cpu (0)
May 26 18:12:34 tarm kernel: [ 4216.175809] acpi-cpufreq: get_cur_val = 100664850
May 26 18:12:34 tarm kernel: [ 4216.175936] acpi-cpufreq: cur freq = 800000
May 26 18:12:34 tarm kernel: [ 4216.176061] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
May 26 18:12:34 tarm kernel: [ 4216.176194] acpi-cpufreq: acpi_cpufreq_verify
May 26 18:12:34 tarm kernel: [ 4216.176322] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 18:12:34 tarm kernel: [ 4216.176458] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 18:12:34 tarm kernel: [ 4216.176592] acpi-cpufreq: acpi_cpufreq_verify
May 26 18:12:34 tarm kernel: [ 4216.176719] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
May 26 18:12:34 tarm kernel: [ 4216.176856] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
May 26 18:12:34 tarm kernel: [ 4216.177405] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
May 26 18:12:34 tarm kernel: [ 4216.177565] cpufreq-core: governor: change or update limits
May 26 18:12:34 tarm kernel: [ 4216.177696] cpufreq-core: __cpufreq_governor for CPU 0, event 3
May 26 18:12:49 tarm kernel: [ 4230.625012] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:12:49 tarm kernel: [ 4230.625277] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 18:12:49 tarm kernel: [ 4230.625421] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 18:12:49 tarm kernel: [ 4230.625563] freq-table: target is 0 (2000000 kHz, 0)
May 26 18:12:49 tarm kernel: [ 4230.625698] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
May 26 18:12:49 tarm kernel: [ 4230.625838] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
May 26 18:12:49 tarm kernel: [ 4230.625904] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
May 26 18:13:00 tarm kernel: [ 4241.624998] __ratelimit: 7 messages suppressed
May 26 18:13:00 tarm kernel: [ 4241.625219] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:13:00 tarm kernel: [ 4241.625384] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
May 26 18:13:00 tarm kernel: [ 4241.625519] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
May 26 18:13:14 tarm kernel: [ 4255.624998] __ratelimit: 37 messages suppressed
May 26 18:13:14 tarm kernel: [ 4255.625224] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
May 26 18:13:14 tarm kernel: [ 4255.625391] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)


>
>    Thomas
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: cpufreq limits avilable frequencies to 800MHz on git kernel
  2008-05-26 16:15           ` Arkadiusz Miskiewicz
@ 2008-05-26 16:23             ` Arkadiusz Miskiewicz
  2008-07-17 13:48               ` [PATCH] " Thomas Renninger
  2008-05-27  9:35             ` Thomas Renninger
  1 sibling, 1 reply; 13+ messages in thread
From: Arkadiusz Miskiewicz @ 2008-05-26 16:23 UTC (permalink / raw)
  To: linux-kernel; +Cc: trenn, cpufreq, Andrew Morton, gnorton, miguel, linux-acpi

On Monday 26 May 2008, Arkadiusz Miskiewicz wrote:
> On Monday 26 May 2008, Thomas Renninger wrote:
> > On Mon, 2008-05-26 at 09:07 +0200, Arkadiusz Miskiewicz wrote:
> > > On Sunday 25 May 2008, Thomas Renninger wrote:
> > > > On Sun, 2008-05-25 at 11:36 +0200, Arkadiusz Miskiewicz wrote:
> > > > > On Saturday 24 May 2008, Andrew Morton wrote:
> > > > > > On Fri, 23 May 2008 19:44:57 +0200 Arkadiusz Miskiewicz
> > > > > > <arekm@maven.pl>
> > > > >
> > > > > wrote:
> > > > > > > thinkpad z60m, Intel(R) Pentium(R) M processor 2.00GHz. kernel
> > > > > > > from git from 1-2 days ago.
> > > > > > >
> > > > > > > Unfortunately it seems that suspend to ram/resume causes
> > > > > > > frequency to be limited to 800MHz only. I can't set it to 2GHz
> > > > > > > again :-/
> > > > > > >
> > > > > > > scaling_max_freq is then 800000 and cannot be changed.
> > > > > > >
> > > > > > > reboot and the problem disappears until new suspend/resume
> > > > > > > cycle.
> > > > > > >
> > > > > > > cpufreq stuff is driven by acpi-cpufreq
> > > > > > >
> > > > > > > $ cpufreq-info
> > > > > > > cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
> > > > > > > Report errors and bugs to linux@brodo.de, please.
> > > > > > > analyzing CPU 0:
> > > > > > >   driver: acpi-cpufreq
> > > > > > >   CPUs which need to switch frequency at the same time: 0
> > > > > > >   hardware limits: 800 MHz - 2.00 GHz
> > > > > > >   available frequency steps: 2.00 GHz, 1.60 GHz, 1.33 GHz, 1.07
> > > > > > > GHz, 800 MHz available cpufreq governors: powersave, userspace,
> > > > > > > ondemand, performance current policy: frequency should be
> > > > > > > within 800 MHz and 800 MHz. The governor "performance" may
> > > > > > > decide which speed to use within this range.
> > > > > > >   current CPU frequency is 800 MHz.
> > > > > > >
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:800000
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:2000000
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:800000
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequenc
> > > > > > >ie s:20 0000 0 1600000 1333000 1066000 800000
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governor
> > > > > > >s: powe rsav e userspace ondemand performance
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:800000
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufre
> > > > > > >q
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:performan
> > > > > > >ce /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:800000
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:800000
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:<unsuppor
> > > > > > >te d>
> > > > > >
> > > > > > Thanks.  Is this a newly-occurring bug or did earlier kernels do
> > > > > > this also?
> > > > > >
> > > > > > If it was newly added, do you know in which kernel version we
> > > > > > might have added it?
> > > > >
> > > > > I wasn't able to reproduce the problem on final 2.6.24 but was able
> > > > > to reproduce on final 2.6.25. Problem introduced somewhere between
> > > > > it seems.
> > > > >
> > > > > Note that 2-3 suspend to ram/resume cycles is needed to get into
> > > > > the problem.
> > > >
> > > > Sounds related to:
> > > > [Bug 374099] T61p speedstep problems (ondemand scheduler)
> > > > https://bugzilla.novell.com/show_bug.cgi?id=374099
> > >
> > > login/pass protected
> > >
> > > > Miguel speaks from "good boots" and "bad boots".
> > >
> > > Actually I also got "bad boot" (so no suspend/resume was needed).
> > >
> > > > Could you check whether the OS thinks it is too hot.
> > > > I described some basics how to monitor temperature and cpufreq (if
> > > > passive cooling kicks in) here:
> > > > https://bugzilla.novell.com/show_bug.cgi?id=387702#c13
> > >
> > > Doesn't seem to be overheated
> > >
> > > [arekm@tarm ~]$ cat
> > > /proc/acpi/thermal_zone/*/{temperature,trip_points,state}; cat
> > > /sys/devices/system/cpu/cpu*/cpufreq/scaling_{cur_freq,max_freq}
> > > temperature:             45 C
> > > critical (S5):           99 C
> > > passive:                 95 C: tc1=5 tc2=4 tsp=600 devices= CPU
> > > state:                   ok
> > > 800000
> > > 800000
> > >
> > > but still limited to 800MHz.
> > >
> > > > Hmm, it may just have been fixed by this one:
> > > > commit e56a727b023d40d1adf660168883f30f2e6abe0a
> > > > Author: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> > > > Date:   Mon Apr 28 15:13:43 2008 -0400
> > > >
> > > > Miguel, Geoff: This is already in 11.0 for some time and in 10.3 for
> > > > some days.
> > >
> > > Unfortunately it doesn't fix the problem. The patch is in Linus tree
> > > for long time (so I guess I had it when initially reporting the
> > > problem) + I upgraded today to current git - the problem is still
> > > there.
> >
> > Yep, Dells and some HP should be fixed, it would have been strange if
> > ThinkPads are now also affected, but thanks for double checking, it
> > shows the same symptoms.
> >
> > Then it might be _PPC.
> > If you compile in CPUFREQ_DEBUG and add the boot param:
> > cpufreq.debug=7
> > you should see a message in dmesg (if you do not see one, then
> > everything is fine you have a "good boot" and freq should be at max?):
> > cpufreq_printk("CPU %d: _PPC is %d - frequency %s limited\n", pr->id,
> >                        (int)ppc, ppc ? "" : "not");
> >
> > If PPC is zero all frequencies are allowed, if it is one max_freq will
> > be set to the second highest freq, etc.
> >
> > If it's that you can workaround that (temporarily, pls help evaluating
> > this further) you can use:
> > processor.ignore_ppc=1
> >
> > I remember Ingo Molnar sent a patch to not always evaluate _PPC at
> > boot/initialization time, but only on processor notification events.
> > AFAIK this was a recent ThinkPad, so this might be it what you are
> > seeing. But nobody knew why some ThinkPads had a wrong _PPC value at
> > initialization time.
> >
> > If this is PPC related, this is more an ACPI than a cpufreq issue ->
> > adding linux-acpi list.
>
> Ok, there is something, see:
>
> [ 4093.625227] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> [ 4095.755272] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000
> kHz [ 4095.755508] acpi-cpufreq: acpi_cpufreq_verify
> [ 4095.755642] freq-table: request for verification of policy (800000 -
> 2000000 kHz) for cpu 0 [ 4095.755780] freq-table: verification lead to
> (800000 - 2000000 kHz) for cpu 0 [ 4095.755916] acpi-cpufreq:
> acpi_cpufreq_verify
> [ 4095.756042] freq-table: request for verification of policy (800000 -
> 800000 kHz) for cpu 0 [ 4095.756179] freq-table: verification lead to
> (800000 - 800000 kHz) for cpu 0 [ 4095.756314] cpufreq-core: new min and
> max freqs are 800000 - 800000 kHz

and later back to 2GHz



[ 4095.756042] freq-table: request for verification of policy (800000 - 800000 
kHz) for cpu 0
[ 4095.756179] freq-table: verification lead to (800000 - 800000 kHz) for cpu 
0
[ 4095.756314] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
[ 4095.756447] cpufreq-core: governor: change or update limits
[ 4095.756575] cpufreq-core: __cpufreq_governor for CPU 0, event 3
[ 4216.175207] __ratelimit: 39 messages suppressed
[ 4216.175414] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
[ 4216.175553] cpufreq-core: updating policy for CPU 0
[ 4216.175682] acpi-cpufreq: get_cur_freq_on_cpu (0)
[ 4216.175809] acpi-cpufreq: get_cur_val = 100664850
[ 4216.175936] acpi-cpufreq: cur freq = 800000
[ 4216.176061] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 
kHz
[ 4216.176194] acpi-cpufreq: acpi_cpufreq_verify
[ 4216.176322] freq-table: request for verification of policy (800000 - 
2000000 kHz) for cpu 0
[ 4216.176458] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 
0
[ 4216.176592] acpi-cpufreq: acpi_cpufreq_verify
[ 4216.176719] freq-table: request for verification of policy (800000 - 
2000000 kHz) for cpu 0
[ 4216.176856] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 
0
[ 4216.177405] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
[ 4216.177565] cpufreq-core: governor: change or update limits
[ 4216.177696] cpufreq-core: __cpufreq_governor for CPU 0, event 3
[ 4230.625012] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
[ 4230.625277] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
[ 4230.625421] freq-table: request for target 2000000 kHz (relation: 1) for 
cpu 0
[ 4230.625563] freq-table: target is 0 (2000000 kHz, 0)
[ 4230.625698] cpufreq-core: notification 0 of frequency transition to 2000000 
kHz
[ 4230.625838] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 
2000000 kHz
[ 4230.625904] cpufreq-core: notification 1 of frequency transition to 2000000 
kHz
[ 4241.624998] __ratelimit: 7 messages suppressed


then back again to 800MHz and back to 2GHz

[ 4313.125215] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
[ 4315.821316] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 
kHz
[ 4315.821465] acpi-cpufreq: acpi_cpufreq_verify
[ 4315.821525] freq-table: request for verification of policy (800000 - 
2000000 kHz) for cpu 0
[ 4315.821587] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 
0
[ 4315.821648] acpi-cpufreq: acpi_cpufreq_verify
[ 4315.821705] freq-table: request for verification of policy (800000 - 800000 
kHz) for cpu 0
[ 4315.821765] freq-table: verification lead to (800000 - 800000 kHz) for cpu 
0
[ 4315.821826] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
[ 4315.821885] cpufreq-core: governor: change or update limits
[ 4315.821942] cpufreq-core: __cpufreq_governor for CPU 0, event 3
[ 4315.822000] cpufreq-core: target for CPU 0: 800000 kHz, relation 1
[ 4315.822080] acpi-cpufreq: acpi_cpufreq_target 800000 (0)
[ 4315.822138] freq-table: request for target 800000 kHz (relation: 1) for cpu 
0
[ 4315.822197] freq-table: target is 4 (800000 kHz, 4)
[ 4315.822255] cpufreq-core: notification 0 of frequency transition to 800000 
kHz
[ 4315.822316] cpufreq-core: notification 1 of frequency transition to 800000 
kHz
[ 4315.822370] cpufreq-core: scaling loops_per_jiffy to 3195449 for frequency 
800000 kHz
[ 4459.098165] __ratelimit: 44 messages suppressed
[ 4459.098394] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
[ 4459.098534] cpufreq-core: updating policy for CPU 0
[ 4459.098663] acpi-cpufreq: get_cur_freq_on_cpu (0)
[ 4459.098791] acpi-cpufreq: get_cur_val = 100664850
[ 4459.098918] acpi-cpufreq: cur freq = 800000
[ 4459.099044] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 
kHz
[ 4459.099177] acpi-cpufreq: acpi_cpufreq_verify
[ 4459.099321] freq-table: request for verification of policy (800000 - 
2000000 kHz) for cpu 0
[ 4459.099458] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 
0


-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: cpufreq limits avilable frequencies to 800MHz on git kernel
  2008-05-26 16:15           ` Arkadiusz Miskiewicz
  2008-05-26 16:23             ` Arkadiusz Miskiewicz
@ 2008-05-27  9:35             ` Thomas Renninger
  1 sibling, 0 replies; 13+ messages in thread
From: Thomas Renninger @ 2008-05-27  9:35 UTC (permalink / raw)
  To: Arkadiusz Miskiewicz
  Cc: linux-kernel, cpufreq, Andrew Morton, gnorton, miguel, linux-acpi,
	Pallipadi, Venkatesh

On Mon, 2008-05-26 at 18:15 +0200, Arkadiusz Miskiewicz wrote:
> On Monday 26 May 2008, Thomas Renninger wrote:
> > On Mon, 2008-05-26 at 09:07 +0200, Arkadiusz Miskiewicz wrote:
> > > On Sunday 25 May 2008, Thomas Renninger wrote:
> > > > On Sun, 2008-05-25 at 11:36 +0200, Arkadiusz Miskiewicz wrote:
> > > > > On Saturday 24 May 2008, Andrew Morton wrote:
> > > > > > On Fri, 23 May 2008 19:44:57 +0200 Arkadiusz Miskiewicz
> > > > > > <arekm@maven.pl>
> > > > >
> > > > > wrote:
> > > > > > > thinkpad z60m, Intel(R) Pentium(R) M processor 2.00GHz. kernel
> > > > > > > from git from 1-2 days ago.
> > > > > > >
> > > > > > > Unfortunately it seems that suspend to ram/resume causes
> > > > > > > frequency to be limited to 800MHz only. I can't set it to 2GHz
> > > > > > > again :-/
> > > > > > >
> > > > > > > scaling_max_freq is then 800000 and cannot be changed.
> > > > > > >
> > > > > > > reboot and the problem disappears until new suspend/resume cycle.
> > > > > > >
> > > > > > > cpufreq stuff is driven by acpi-cpufreq
> > > > > > >
> > > > > > > $ cpufreq-info
> > > > > > > cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
> > > > > > > Report errors and bugs to linux@brodo.de, please.
> > > > > > > analyzing CPU 0:
> > > > > > >   driver: acpi-cpufreq
> > > > > > >   CPUs which need to switch frequency at the same time: 0
> > > > > > >   hardware limits: 800 MHz - 2.00 GHz
> > > > > > >   available frequency steps: 2.00 GHz, 1.60 GHz, 1.33 GHz, 1.07
> > > > > > > GHz, 800 MHz available cpufreq governors: powersave, userspace,
> > > > > > > ondemand, performance current policy: frequency should be within
> > > > > > > 800 MHz and 800 MHz. The governor "performance" may decide which
> > > > > > > speed to use within this range.
> > > > > > >   current CPU frequency is 800 MHz.
> > > > > > >
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:800000
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:2000000
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:800000
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencie
> > > > > > >s:20 0000 0 1600000 1333000 1066000 800000
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:
> > > > > > >powe rsav e userspace ondemand performance
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:800000
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufreq
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:performance
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:800000
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:800000
> > > > > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:<unsupporte
> > > > > > >d>
> > > > > >
> > > > > > Thanks.  Is this a newly-occurring bug or did earlier kernels do
> > > > > > this also?
> > > > > >
> > > > > > If it was newly added, do you know in which kernel version we might
> > > > > > have added it?
> > > > >
> > > > > I wasn't able to reproduce the problem on final 2.6.24 but was able
> > > > > to reproduce on final 2.6.25. Problem introduced somewhere between it
> > > > > seems.
> > > > >
> > > > > Note that 2-3 suspend to ram/resume cycles is needed to get into the
> > > > > problem.
> > > >
> > > > Sounds related to:
> > > > [Bug 374099] T61p speedstep problems (ondemand scheduler)
> > > > https://bugzilla.novell.com/show_bug.cgi?id=374099
> > >
> > > login/pass protected
> > >
> > > > Miguel speaks from "good boots" and "bad boots".
> > >
> > > Actually I also got "bad boot" (so no suspend/resume was needed).
> > >
> > > > Could you check whether the OS thinks it is too hot.
> > > > I described some basics how to monitor temperature and cpufreq (if
> > > > passive cooling kicks in) here:
> > > > https://bugzilla.novell.com/show_bug.cgi?id=387702#c13
> > >
> > > Doesn't seem to be overheated
> > >
> > > [arekm@tarm ~]$ cat
> > > /proc/acpi/thermal_zone/*/{temperature,trip_points,state}; cat
> > > /sys/devices/system/cpu/cpu*/cpufreq/scaling_{cur_freq,max_freq}
> > > temperature:             45 C
> > > critical (S5):           99 C
> > > passive:                 95 C: tc1=5 tc2=4 tsp=600 devices= CPU
> > > state:                   ok
> > > 800000
> > > 800000
> > >
> > > but still limited to 800MHz.
> > >
> > > > Hmm, it may just have been fixed by this one:
> > > > commit e56a727b023d40d1adf660168883f30f2e6abe0a
> > > > Author: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> > > > Date:   Mon Apr 28 15:13:43 2008 -0400
> > > >
> > > > Miguel, Geoff: This is already in 11.0 for some time and in 10.3 for
> > > > some days.
> > >
> > > Unfortunately it doesn't fix the problem. The patch is in Linus tree for
> > > long time (so I guess I had it when initially reporting the problem) + I
> > > upgraded today to current git - the problem is still there.
> >
> > Yep, Dells and some HP should be fixed, it would have been strange if
> > ThinkPads are now also affected, but thanks for double checking, it
> > shows the same symptoms.
> >
> > Then it might be _PPC.
> > If you compile in CPUFREQ_DEBUG and add the boot param:
> > cpufreq.debug=7
> > you should see a message in dmesg (if you do not see one, then
> > everything is fine you have a "good boot" and freq should be at max?):
> > cpufreq_printk("CPU %d: _PPC is %d - frequency %s limited\n", pr->id,
> >                        (int)ppc, ppc ? "" : "not");
> >
> > If PPC is zero all frequencies are allowed, if it is one max_freq will
> > be set to the second highest freq, etc.
> >
> > If it's that you can workaround that (temporarily, pls help evaluating
> > this further) you can use:
> > processor.ignore_ppc=1
> >
> > I remember Ingo Molnar sent a patch to not always evaluate _PPC at
> > boot/initialization time, but only on processor notification events.
> > AFAIK this was a recent ThinkPad, so this might be it what you are
> > seeing. But nobody knew why some ThinkPads had a wrong _PPC value at
> > initialization time.
> >
> > If this is PPC related, this is more an ACPI than a cpufreq issue ->
> > adding linux-acpi list.
> 
> Ok, there is something, see:
> 
> [ 4093.625227] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> [ 4095.755272] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> [ 4095.755508] acpi-cpufreq: acpi_cpufreq_verify
> [ 4095.755642] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> [ 4095.755780] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> [ 4095.755916] acpi-cpufreq: acpi_cpufreq_verify
> [ 4095.756042] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
> [ 4095.756179] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
> [ 4095.756314] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
> 
> PPC related messages are:
> 
> $ dmesg|grep PPC
> [ 3597.291342] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
> [ 3721.943484] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
> [ 3881.874373] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
> [ 4216.175414] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
> 
This looks ok...
I'd expected:
[ 4216.175414] cpufreq-core: CPU 0: _PPC is 4 - frequency limited
Then it should be limited and get unlimited with e.g.:
[ 4216.175414] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited

AFAIK, max_freq should only get limited via passive cooling or explicit
BIOS limitation via _PPC.

> May 26 19:02:28 tarm kernel: [    6.184998] ACPI: Video Device [VID1]
The video driver is rather broken, especially on ThinkPads arbitrary HW
might get accessed, better blacklist video in modprobe.conf for now.
Probably unrelated, just to be sure...

Some strange frequency targets, min freq is 800.000 Khz, I wonder where
these values are coming from:
May 26 17:40:57 tarm kernel: [ 2319.124990] cpufreq-core: target for CPU
0: 400000 kHz, relation 0
May 26 17:40:57 tarm kernel: [ 2319.125141] acpi-cpufreq:
acpi_cpufreq_target 400000 (0)
May 26 17:59:39 tarm kernel: [ 3441.125163] cpufreq-core: target for CPU
0: 571428 kHz, relation 0
May 26 17:39:57 tarm kernel: [ 2259.125137] cpufreq-core: target for CPU 0: 342857 kHz, relation 0


The bad seems to happen at the end at 17:59 (the rest of the logs should
be rather uninteresting). There the frequency gets limited to 800. Then
every about 2-3 (18:02, 18:04)  mins something odd is happening:
The limitation falls away (2000 is allowed again) and ten seconds later
the frequency is limited again.

It already starts before...:
17:59:54 limited to 800
18:02:15 unlimited, max_freq 2000
18:02:28 limited to 800
18:04:20 unlimited, max_freq 2000
18:05:14 limited to 800
18:07:00 unlimited, max_freq 2000
18:10:34 limited to 800


Sorry, but I currently do not have time to look deeper at this.
I try to look at it the next days, if I haven't answered until Sa, I
won't be able to for the next 2 weeks.

   Thomas

> complete log from boot:
(stripped)
> May 26 17:13:47 tarm kernel: [  681.613159] Freezing user space processes ... (elapsed 0.00 seconds) done.
> May 26 17:13:47 tarm kernel: [  681.614674] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
> May 26 17:13:47 tarm kernel: [  681.614758] Suspending console(s)
> May 26 17:13:47 tarm kernel: [  681.835093] sd 0:0:0:0: [sda] Synchronizing SCSI cache
> May 26 17:13:47 tarm kernel: [  681.844214] sd 0:0:0:0: [sda] Stopping disk
> May 26 17:13:47 tarm kernel: [  683.265808] nsc-ircc 00:09: disabled
> May 26 17:13:47 tarm kernel: [  683.265997] eth1: Going into suspend...
> May 26 17:13:47 tarm kernel: [  683.270843] ACPI: PCI interrupt for device 0000:14:02.0 disabled
> May 26 17:13:47 tarm kernel: [  683.270855] ACPI handle has no context!
> May 26 17:13:47 tarm kernel: [  683.286131] ACPI handle has no context!
> May 26 17:13:47 tarm kernel: [  683.286160] ACPI: PCI interrupt for device 0000:14:00.2 disabled
> May 26 17:13:47 tarm kernel: [  683.286170] ACPI handle has no context!
> May 26 17:13:47 tarm kernel: [  683.306077] ACPI handle has no context!
> May 26 17:13:47 tarm kernel: [  683.462597] ACPI handle has no context!
> May 26 17:13:47 tarm kernel: [  683.681053] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> May 26 17:13:47 tarm kernel: [  683.700321] ACPI: Preparing to enter system sleep state S3
> May 26 17:13:47 tarm kernel: [  683.712644] Extended CMOS year: 2000
> May 26 17:13:47 tarm kernel: [  683.712644] Intel machine check architecture supported.
> May 26 17:13:47 tarm kernel: [  683.712660] Intel machine check reporting enabled on CPU#0.
> May 26 17:13:47 tarm kernel: [  683.712761] Back to C!
> May 26 17:13:47 tarm kernel: [  683.712967] Extended CMOS year: 2000
> May 26 17:13:47 tarm kernel: [  683.712967] Force enabled HPET at resume
> May 26 17:13:47 tarm kernel: [  683.712967] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 17:13:47 tarm kernel: [  683.712967] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:13:47 tarm kernel: [  683.712967] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 17:13:47 tarm kernel: [  683.712967] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 17:13:47 tarm kernel: [  683.712967] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:13:47 tarm kernel: [  683.712967] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 17:13:47 tarm kernel: [  683.712967] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 17:13:47 tarm kernel: [  683.712967] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
> May 26 17:13:47 tarm kernel: [  683.712967] cpufreq-core: governor: change or update limits
> May 26 17:13:47 tarm kernel: [  683.712967] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 17:13:47 tarm kernel: [  683.762614] PM: Writing back config space on device 0000:00:01.0 at offset 1 (was 100107, writing 100507)
> May 26 17:13:47 tarm kernel: [  683.762614] PCI: Setting latency timer of device 0000:00:01.0 to 64
> May 26 17:13:47 tarm kernel: [  683.789051] PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100002)
> May 26 17:13:47 tarm kernel: [  683.789074] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
> May 26 17:13:47 tarm kernel: [  683.789081] PCI: Setting latency timer of device 0000:00:1b.0 to 64
> May 26 17:13:47 tarm kernel: [  683.845176] PM: Writing back config space on device 0000:00:1c.0 at offset 1 (was 100107, writing 100507)
> May 26 17:13:47 tarm kernel: [  683.845248] PCI: Setting latency timer of device 0000:00:1c.0 to 64
> May 26 17:13:47 tarm kernel: [  683.845299] PM: Writing back config space on device 0000:00:1c.1 at offset 1 (was 100107, writing 100507)
> May 26 17:13:47 tarm kernel: [  683.845363] PCI: Setting latency timer of device 0000:00:1c.1 to 64
> May 26 17:13:47 tarm kernel: [  683.845423] PM: Writing back config space on device 0000:00:1c.2 at offset 1 (was 100107, writing 100507)
> May 26 17:13:47 tarm kernel: [  683.845487] PCI: Setting latency timer of device 0000:00:1c.2 to 64
> May 26 17:13:47 tarm kernel: [  683.845548] PM: Writing back config space on device 0000:00:1c.3 at offset 1 (was 100107, writing 100507)
> May 26 17:13:47 tarm kernel: [  683.845611] PCI: Setting latency timer of device 0000:00:1c.3 to 64
> May 26 17:13:47 tarm kernel: [  683.845627] PM: Writing back config space on device 0000:00:1d.0 at offset f (was 100, writing 10b)
> May 26 17:13:47 tarm kernel: [  683.845673] PM: Writing back config space on device 0000:00:1d.1 at offset f (was 200, writing 20b)
> May 26 17:13:47 tarm kernel: [  683.845728] PM: Writing back config space on device 0000:00:1d.2 at offset f (was 300, writing 30b)
> May 26 17:13:47 tarm kernel: [  683.845774] PM: Writing back config space on device 0000:00:1d.3 at offset f (was 400, writing 40b)
> May 26 17:13:47 tarm kernel: [  683.845836] PM: Writing back config space on device 0000:00:1d.7 at offset f (was 400, writing 40b)
> May 26 17:13:47 tarm kernel: [  683.845873] PM: Writing back config space on device 0000:00:1d.7 at offset 4 (was 0, writing b0004000)
> May 26 17:13:47 tarm kernel: [  683.845881] PM: Writing back config space on device 0000:00:1d.7 at offset 1 (was 2900000, writing 2900102)
> May 26 17:13:47 tarm kernel: [  683.845980] PCI: Setting latency timer of device 0000:00:1e.0 to 64
> May 26 17:13:47 tarm kernel: [  683.861043] PM: Writing back config space on device 0000:00:1f.2 at offset 1 (was 2b00005, writing 2b80005)
> May 26 17:13:47 tarm kernel: [  683.861062] PCI: Setting latency timer of device 0000:00:1f.2 to 64
> May 26 17:13:47 tarm kernel: [  683.863259] PM: Writing back config space on device 0000:01:00.0 at offset 1 (was 100103, writing 100107)
> May 26 17:13:47 tarm kernel: [  683.863323] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
> May 26 17:13:47 tarm kernel: [  683.863327] PCI: Setting latency timer of device 0000:01:00.0 to 64
> May 26 17:13:47 tarm kernel: [  683.863365] PM: Writing back config space on device 0000:02:00.0 at offset c (was 0, writing fcff0000)
> May 26 17:13:47 tarm kernel: [  683.863391] PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 100106)
> May 26 17:13:47 tarm kernel: [  684.201259] PM: Writing back config space on device 0000:14:00.1 at offset 4 (was 0, writing c0001000)
> May 26 17:13:47 tarm kernel: [  684.201265] PM: Writing back config space on device 0000:14:00.1 at offset 3 (was 800000, writing 804000)
> May 26 17:13:47 tarm kernel: [  684.201273] PM: Writing back config space on device 0000:14:00.1 at offset 1 (was 2100000, writing 2100106)
> May 26 17:13:47 tarm kernel: [  684.213807] ata2.00: ACPI cmd ef/03:42:00:00:00:a0 filtered out
> May 26 17:13:47 tarm kernel: [  684.213809] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
> May 26 17:13:47 tarm kernel: [  684.221813] ata2.00: ACPI cmd e3/00:10:00:00:00:a0 succeeded
> May 26 17:13:47 tarm kernel: [  684.229816] ata2.00: ACPI cmd e3/00:03:00:00:00:a0 succeeded
> May 26 17:13:47 tarm kernel: [  684.254164] ata2.00: configured for UDMA/33
> May 26 17:13:47 tarm kernel: [  684.256181] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17]  MMIO=[c0001000-c00017ff]  Max Packet=[2048]  IR/IT contexts=[4/4]
> May 26 17:13:47 tarm kernel: [  684.281188] PM: Writing back config space on device 0000:14:00.2 at offset 4 (was 0, writing c0001800)
> May 26 17:13:47 tarm kernel: [  684.281193] PM: Writing back config space on device 0000:14:00.2 at offset 3 (was 800000, writing 804000)
> May 26 17:13:47 tarm kernel: [  684.281200] PM: Writing back config space on device 0000:14:00.2 at offset 1 (was 2100000, writing 2100106)
> May 26 17:13:47 tarm kernel: [  684.281219] ACPI: PCI Interrupt 0000:14:00.2[C] -> GSI 18 (level, low) -> IRQ 18
> May 26 17:13:47 tarm kernel: [  684.282264] eth1: Coming out of suspend...
> May 26 17:13:47 tarm kernel: [  684.304115] ACPI: PCI Interrupt 0000:14:02.0[A] -> GSI 21 (level, low) -> IRQ 21
> May 26 17:13:47 tarm kernel: [  684.304856] nsc-ircc 00:09: activated
> May 26 17:13:47 tarm kernel: [  685.125021] __ratelimit: 36 messages suppressed
> May 26 17:13:47 tarm kernel: [  685.125024] cpufreq-core: target for CPU 0: 1005714 kHz, relation 0
> May 26 17:13:47 tarm kernel: [  685.240365] sd 0:0:0:0: [sda] Starting disk
> May 26 17:13:47 tarm kernel: [  685.361681] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 succeeded
> May 26 17:13:47 tarm kernel: [  685.361686] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
> May 26 17:13:47 tarm kernel: [  685.361691] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 filtered out
> May 26 17:13:47 tarm kernel: [  685.361696] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
> May 26 17:13:47 tarm kernel: [  685.362115] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 succeeded
> May 26 17:13:47 tarm kernel: [  685.385653] ata1.00: configured for UDMA/100
> May 26 17:13:47 tarm kernel: [  685.409640] ata1.00: configured for UDMA/100
> May 26 17:13:47 tarm kernel: [  685.409645] ata1: EH complete
> May 26 17:13:47 tarm kernel: [  685.409720] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
> May 26 17:13:47 tarm kernel: [  685.409754] sd 0:0:0:0: [sda] Write Protect is off
> May 26 17:13:47 tarm kernel: [  685.409759] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> May 26 17:13:47 tarm kernel: [  685.409816] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> May 26 17:13:47 tarm kernel: [  685.409873] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
> May 26 17:13:47 tarm kernel: [  685.409904] sd 0:0:0:0: [sda] Write Protect is off
> May 26 17:13:47 tarm kernel: [  685.409908] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> May 26 17:13:47 tarm kernel: [  685.409964] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> May 26 17:13:47 tarm kernel: [  688.101026] hdaps: initial latch check good (0x01).
> May 26 17:13:47 tarm kernel: [  688.509522] Restarting tasks ... done.
> May 26 17:13:47 tarm kernel: [  688.613227] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 19
> May 26 17:13:47 tarm kernel: [  688.613491] PCI: Setting latency timer of device 0000:00:1d.7 to 64
> May 26 17:13:47 tarm kernel: [  688.613633] ehci_hcd 0000:00:1d.7: EHCI Host Controller
> May 26 17:13:47 tarm kernel: [  688.662871] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
> May 26 17:13:47 tarm kernel: [  688.667009] ehci_hcd 0000:00:1d.7: debug port 1
> May 26 17:13:47 tarm kernel: [  688.669045] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
> May 26 17:13:47 tarm kernel: [  688.669225] ehci_hcd 0000:00:1d.7: irq 19, io mem 0xb0004000
> May 26 17:13:47 tarm kernel: [  688.685034] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
> May 26 17:13:47 tarm kernel: [  688.685481] usb usb1: configuration #1 chosen from 1 choice
> May 26 17:13:47 tarm kernel: [  688.691355] hub 1-0:1.0: USB hub found
> May 26 17:13:47 tarm kernel: [  688.691495] hub 1-0:1.0: 8 ports detected
> May 26 17:13:47 tarm kernel: [  688.805182] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
> May 26 17:13:47 tarm kernel: [  688.805194] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> May 26 17:13:47 tarm kernel: [  688.805201] usb usb1: Product: EHCI Host Controller
> May 26 17:13:47 tarm kernel: [  688.805207] usb usb1: Manufacturer: Linux 2.6.26-rc3 ehci_hcd
> May 26 17:13:47 tarm kernel: [  688.805213] usb usb1: SerialNumber: 0000:00:1d.7
> May 26 17:13:47 tarm kernel: [  688.816077] USB Universal Host Controller Interface driver v3.0
> May 26 17:13:47 tarm kernel: [  688.816157] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
> May 26 17:13:47 tarm kernel: [  688.816177] PCI: Setting latency timer of device 0000:00:1d.0 to 64
> May 26 17:13:47 tarm kernel: [  688.816185] uhci_hcd 0000:00:1d.0: UHCI Host Controller
> May 26 17:13:47 tarm kernel: [  688.816252] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
> May 26 17:13:47 tarm kernel: [  688.816288] uhci_hcd 0000:00:1d.0: irq 16, io base 0x00001800
> May 26 17:13:47 tarm kernel: [  688.816514] usb usb2: configuration #1 chosen from 1 choice
> May 26 17:13:47 tarm kernel: [  688.816578] hub 2-0:1.0: USB hub found
> May 26 17:13:47 tarm kernel: [  688.816592] hub 2-0:1.0: 2 ports detected
> May 26 17:13:47 tarm kernel: [  688.917139] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
> May 26 17:13:47 tarm kernel: [  688.917780] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> May 26 17:13:47 tarm kernel: [  688.917792] usb usb2: Product: UHCI Host Controller
> May 26 17:13:47 tarm kernel: [  688.917798] usb usb2: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
> May 26 17:13:47 tarm kernel: [  688.917803] usb usb2: SerialNumber: 0000:00:1d.0
> May 26 17:13:47 tarm kernel: [  688.917849] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 17
> May 26 17:13:47 tarm kernel: [  688.917868] PCI: Setting latency timer of device 0000:00:1d.1 to 64
> May 26 17:13:47 tarm kernel: [  688.917876] uhci_hcd 0000:00:1d.1: UHCI Host Controller
> May 26 17:13:47 tarm kernel: [  688.917936] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
> May 26 17:13:47 tarm kernel: [  688.917972] uhci_hcd 0000:00:1d.1: irq 17, io base 0x00001820
> May 26 17:13:47 tarm kernel: [  688.918197] usb usb3: configuration #1 chosen from 1 choice
> May 26 17:13:47 tarm kernel: [  688.918263] hub 3-0:1.0: USB hub found
> May 26 17:13:47 tarm kernel: [  688.918277] hub 3-0:1.0: 2 ports detected
> May 26 17:13:48 tarm kernel: [  689.001814] hub 1-0:1.0: unable to enumerate USB device on port 3
> May 26 17:13:48 tarm kernel: [  689.021284] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
> May 26 17:13:48 tarm kernel: [  689.021491] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> May 26 17:13:48 tarm kernel: [  689.021502] usb usb3: Product: UHCI Host Controller
> May 26 17:13:48 tarm kernel: [  689.021507] usb usb3: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
> May 26 17:13:48 tarm kernel: [  689.021513] usb usb3: SerialNumber: 0000:00:1d.1
> May 26 17:13:48 tarm kernel: [  689.021559] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
> May 26 17:13:48 tarm kernel: [  689.021578] PCI: Setting latency timer of device 0000:00:1d.2 to 64
> May 26 17:13:48 tarm kernel: [  689.021586] uhci_hcd 0000:00:1d.2: UHCI Host Controller
> May 26 17:13:48 tarm kernel: [  689.021641] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
> May 26 17:13:48 tarm kernel: [  689.021675] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001840
> May 26 17:13:48 tarm kernel: [  689.021905] usb usb4: configuration #1 chosen from 1 choice
> May 26 17:13:48 tarm kernel: [  689.021971] hub 4-0:1.0: USB hub found
> May 26 17:13:48 tarm kernel: [  689.021984] hub 4-0:1.0: 2 ports detected
> May 26 17:13:48 tarm kernel: [  689.125223] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
> May 26 17:13:48 tarm kernel: [  689.125235] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> May 26 17:13:48 tarm kernel: [  689.125242] usb usb4: Product: UHCI Host Controller
> May 26 17:13:48 tarm kernel: [  689.125248] usb usb4: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
> May 26 17:13:48 tarm kernel: [  689.125254] usb usb4: SerialNumber: 0000:00:1d.2
> May 26 17:13:48 tarm kernel: [  689.125297] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 19
> May 26 17:13:48 tarm kernel: [  689.125317] PCI: Setting latency timer of device 0000:00:1d.3 to 64
> May 26 17:13:48 tarm kernel: [  689.125324] uhci_hcd 0000:00:1d.3: UHCI Host Controller
> May 26 17:13:48 tarm kernel: [  689.125377] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
> May 26 17:13:48 tarm kernel: [  689.125412] uhci_hcd 0000:00:1d.3: irq 19, io base 0x00001860
> May 26 17:13:48 tarm kernel: [  689.125642] usb usb5: configuration #1 chosen from 1 choice
> May 26 17:13:48 tarm kernel: [  689.125708] hub 5-0:1.0: USB hub found
> May 26 17:13:48 tarm kernel: [  689.125722] hub 5-0:1.0: 2 ports detected
> May 26 17:13:48 tarm kernel: [  689.229073] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
> May 26 17:13:48 tarm kernel: [  689.229218] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> May 26 17:13:48 tarm kernel: [  689.229275] usb usb5: Product: UHCI Host Controller
> May 26 17:13:48 tarm kernel: [  689.229328] usb usb5: Manufacturer: Linux 2.6.26-rc3 uhci_hcd
> May 26 17:13:48 tarm kernel: [  689.229380] usb usb5: SerialNumber: 0000:00:1d.3
> May 26 17:13:48 tarm kernel: [  689.241062] hub 1-0:1.0: unable to enumerate USB device on port 5
> May 26 17:13:48 tarm kernel: [  689.335824] [drm] Loading R300 Microcode
> May 26 17:13:48 tarm kernel: [  689.481010] hub 1-0:1.0: unable to enumerate USB device on port 6
> May 26 17:13:48 tarm kernel: [  689.721001] usb 3-1: new low speed USB device using uhci_hcd and address 2
> May 26 17:13:48 tarm kernel: [  689.900933] usb 3-1: configuration #1 chosen from 1 choice
> May 26 17:13:48 tarm kernel: [  689.929009] input: Logitech Trackball as /class/input/input18
> May 26 17:13:48 tarm kernel: [  689.957156] input,hidraw0: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:1d.1-1
> May 26 17:13:48 tarm kernel: [  689.957408] usb 3-1: New USB device found, idVendor=046d, idProduct=c404
> May 26 17:13:48 tarm kernel: [  689.957465] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> May 26 17:13:48 tarm kernel: [  689.957517] usb 3-1: Product: Trackball
> May 26 17:13:48 tarm kernel: [  689.957566] usb 3-1: Manufacturer: Logitech
> May 26 17:13:49 tarm kernel: [  690.197096] usb 4-1: new full speed USB device using uhci_hcd and address 2
> May 26 17:13:49 tarm kernel: [  690.374479] usb 4-1: configuration #1 chosen from 1 choice
> May 26 17:13:49 tarm kernel: [  690.380777] usb 4-1: New USB device found, idVendor=0a5c, idProduct=2110
> May 26 17:13:49 tarm kernel: [  690.381156] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> May 26 17:13:49 tarm kernel: [  690.381228] usb 4-1: Product: BCM2045B
> May 26 17:13:49 tarm kernel: [  690.381279] usb 4-1: Manufacturer: Broadcom Corp
> May 26 17:13:49 tarm kernel: [  690.621038] usb 4-2: new full speed USB device using uhci_hcd and address 3
> May 26 17:13:49 tarm kernel: [  690.642216] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
> May 26 17:13:49 tarm kernel: [  690.649778] pan1: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
> May 26 17:13:49 tarm kernel: [  690.791941] usb 4-2: configuration #1 chosen from 1 choice
> May 26 17:13:49 tarm kernel: [  690.799042] usb 4-2: New USB device found, idVendor=0483, idProduct=2016
> May 26 17:13:49 tarm kernel: [  690.799147] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> May 26 17:13:49 tarm kernel: [  690.799217] usb 4-2: Product: Biometric Coprocessor
> May 26 17:13:49 tarm kernel: [  690.799267] usb 4-2: Manufacturer: STMicroelectronics
> May 26 17:13:51 tarm kernel: [  692.125168] __ratelimit: 20 messages suppressed
> May 26 17:13:51 tarm kernel: [  692.125309] cpufreq-core: target for CPU 0: 400000 kHz, relation 0
> May 26 17:13:51 tarm kernel: [  692.821450] ADDRCONF(NETDEV_UP): eth0: link is not ready
> May 26 17:13:54 tarm kernel: [  695.124991] __ratelimit: 13 messages suppressed
> May 26 17:13:54 tarm kernel: [  695.125126] cpufreq-core: target for CPU 0: 1714285 kHz, relation 0
> May 26 17:13:57 tarm kernel: [  698.726701] ADDRCONF(NETDEV_UP): eth1: link is not ready
> May 26 17:13:58 tarm kernel: [  699.619284] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
> May 26 17:14:00 tarm kernel: [  701.625013] __ratelimit: 27 messages suppressed
> May 26 17:14:00 tarm kernel: [  701.625238] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:14:01 tarm kernel: [  702.285362] tun0: Disabled Privacy Extensions
> May 26 17:14:08 tarm kernel: [  709.912981] eth1: no IPv6 routers present
> May 26 17:14:10 tarm kernel: [  711.125019] __ratelimit: 27 messages suppressed
> May 26 17:14:10 tarm kernel: [  711.125255] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:14:10 tarm kernel: [  711.125430] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:14:51 tarm kernel: [  752.125025] __ratelimit: 12 messages suppressed
> May 26 17:14:51 tarm kernel: [  752.125268] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:14:51 tarm kernel: [  752.125414] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:14:51 tarm kernel: [  752.125551] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:14:51 tarm kernel: [  752.125691] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:14:51 tarm kernel: [  752.125820] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:14:51 tarm kernel: [  752.125978] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:14:51 tarm kernel: [  752.126035] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:14:51 tarm kernel: [  752.624990] cpufreq-core: target for CPU 0: 685714 kHz, relation 0
> May 26 17:14:54 tarm kernel: [  755.125030] __ratelimit: 20 messages suppressed
> May 26 17:14:54 tarm kernel: [  755.125175] cpufreq-core: target for CPU 0: 137142 kHz, relation 0
> May 26 17:15:05 tarm kernel: [  766.626964] __ratelimit: 39 messages suppressed
> May 26 17:15:05 tarm kernel: [  766.627173] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:15:05 tarm kernel: [  766.627318] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:15:09 tarm kernel: [  770.625018] __ratelimit: 19 messages suppressed
> May 26 17:15:09 tarm kernel: [  770.625466] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:15:18 tarm kernel: [  779.625026] __ratelimit: 13 messages suppressed
> May 26 17:15:18 tarm kernel: [  779.625254] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:15:19 tarm kernel: [  780.124986] __ratelimit: 6 messages suppressed
> May 26 17:15:19 tarm kernel: [  780.125126] cpufreq-core: target for CPU 0: 171428 kHz, relation 0
> May 26 17:15:53 tarm kernel: [  814.624997] __ratelimit: 20 messages suppressed
> May 26 17:15:53 tarm kernel: [  814.625215] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:15:53 tarm kernel: [  814.625381] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:15:53 tarm kernel: [  814.625513] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:15:53 tarm kernel: [  814.625650] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:15:53 tarm kernel: [  814.625779] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:15:53 tarm kernel: [  814.625913] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:15:54 tarm kernel: [  815.124988] __ratelimit: 1 messages suppressed
> May 26 17:15:54 tarm kernel: [  815.125128] cpufreq-core: target for CPU 0: 0 kHz, relation 0
> May 26 17:16:53 tarm kernel: [  874.624998] __ratelimit: 6 messages suppressed
> May 26 17:16:53 tarm kernel: [  874.625222] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:16:53 tarm kernel: [  874.625388] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:16:53 tarm kernel: [  874.625522] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:16:53 tarm kernel: [  874.625658] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:16:53 tarm kernel: [  874.625786] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:16:53 tarm kernel: [  874.625920] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:16:53 tarm kernel: [  874.625975] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:16:54 tarm kernel: [  875.124986] cpufreq-core: target for CPU 0: 0 kHz, relation 0
> May 26 17:16:54 tarm kernel: [  875.125137] acpi-cpufreq: acpi_cpufreq_target 0 (0)
> May 26 17:16:54 tarm kernel: [  875.125211] freq-table: request for target 0 kHz (relation: 0) for cpu 0
> May 26 17:17:53 tarm kernel: [  934.625012] __ratelimit: 18 messages suppressed
> May 26 17:17:53 tarm kernel: [  934.625248] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:17:53 tarm kernel: [  934.625413] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:17:53 tarm kernel: [  934.625549] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:17:53 tarm kernel: [  934.625685] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:17:53 tarm kernel: [  934.625815] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:17:53 tarm kernel: [  934.625949] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:17:53 tarm kernel: [  934.626004] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:17:54 tarm kernel: [  935.124990] cpufreq-core: target for CPU 0: 171428 kHz, relation 0
> May 26 17:17:54 tarm kernel: [  935.125159] acpi-cpufreq: acpi_cpufreq_target 171428 (0)
> May 26 17:17:54 tarm kernel: [  935.125249] freq-table: request for target 171428 kHz (relation: 0) for cpu 0
> May 26 17:18:04 tarm kernel: [  945.125001] __ratelimit: 4 messages suppressed
> May 26 17:18:04 tarm kernel: [  945.125228] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:18:04 tarm kernel: [  945.125397] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:18:53 tarm kernel: [  994.625059] __ratelimit: 12 messages suppressed
> May 26 17:18:53 tarm kernel: [  994.625297] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:18:53 tarm kernel: [  994.625440] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:18:53 tarm kernel: [  994.625575] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:18:53 tarm kernel: [  994.625715] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:18:53 tarm kernel: [  994.625847] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:18:53 tarm kernel: [  994.625983] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:18:53 tarm kernel: [  994.626037] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:18:54 tarm kernel: [  995.624989] cpufreq-core: target for CPU 0: 57142 kHz, relation 0
> May 26 17:18:54 tarm kernel: [  995.625149] acpi-cpufreq: acpi_cpufreq_target 57142 (0)
> May 26 17:18:54 tarm kernel: [  995.625223] freq-table: request for target 57142 kHz (relation: 0) for cpu 0
> May 26 17:19:14 tarm kernel: [ 1015.125008] __ratelimit: 4 messages suppressed
> May 26 17:19:14 tarm kernel: [ 1015.125233] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:19:14 tarm kernel: [ 1015.125399] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:19:14 tarm kernel: [ 1015.125533] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:19:14 tarm kernel: [ 1015.125670] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:19:54 tarm kernel: [ 1055.125008] __ratelimit: 17 messages suppressed
> May 26 17:19:54 tarm kernel: [ 1055.125243] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:19:54 tarm kernel: [ 1055.125382] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:19:54 tarm kernel: [ 1055.125513] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:19:54 tarm kernel: [ 1055.125649] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:19:54 tarm kernel: [ 1055.125777] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:19:54 tarm kernel: [ 1055.125911] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:19:54 tarm kernel: [ 1055.125965] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:19:54 tarm kernel: [ 1055.625012] cpufreq-core: target for CPU 0: 57142 kHz, relation 0
> May 26 17:20:14 tarm kernel: [ 1075.125008] __ratelimit: 6 messages suppressed
> May 26 17:20:14 tarm kernel: [ 1075.125237] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:20:14 tarm kernel: [ 1075.125381] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:20:14 tarm kernel: [ 1075.125515] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:20:14 tarm kernel: [ 1075.125653] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:20:26 tarm kernel: [ 1087.124998] __ratelimit: 10 messages suppressed
> May 26 17:20:26 tarm kernel: [ 1087.125221] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:20:26 tarm kernel: [ 1087.125384] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:20:54 tarm kernel: [ 1115.124997] __ratelimit: 12 messages suppressed
> May 26 17:20:54 tarm kernel: [ 1115.125222] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:20:54 tarm kernel: [ 1115.125388] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:20:54 tarm kernel: [ 1115.125523] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:20:54 tarm kernel: [ 1115.125659] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:20:54 tarm kernel: [ 1115.125788] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:20:54 tarm kernel: [ 1115.125947] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:21:15 tarm kernel: [ 1136.125011] __ratelimit: 8 messages suppressed
> May 26 17:21:15 tarm kernel: [ 1136.125243] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:21:15 tarm kernel: [ 1136.125382] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:21:15 tarm kernel: [ 1136.125527] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:21:15 tarm kernel: [ 1136.125689] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:21:54 tarm kernel: [ 1175.125018] __ratelimit: 10 messages suppressed
> May 26 17:21:54 tarm kernel: [ 1175.125245] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:21:54 tarm kernel: [ 1175.125387] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:21:54 tarm kernel: [ 1175.125520] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:21:54 tarm kernel: [ 1175.125658] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:21:54 tarm kernel: [ 1175.125790] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:21:54 tarm kernel: [ 1175.125925] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:21:54 tarm kernel: [ 1175.125979] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:21:54 tarm kernel: [ 1175.624992] cpufreq-core: target for CPU 0: 1771428 kHz, relation 0
> May 26 17:22:16 tarm kernel: [ 1197.625810] __ratelimit: 11 messages suppressed
> May 26 17:22:16 tarm kernel: [ 1197.626031] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:22:16 tarm kernel: [ 1197.626176] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:22:16 tarm kernel: [ 1197.626457] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:22:16 tarm kernel: [ 1197.626603] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:22:29 tarm kernel: [ 1210.125024] __ratelimit: 10 messages suppressed
> May 26 17:22:29 tarm kernel: [ 1210.125247] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:22:29 tarm kernel: [ 1210.125393] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:22:29 tarm kernel: [ 1210.125528] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:22:54 tarm kernel: [ 1235.625018] __ratelimit: 11 messages suppressed
> May 26 17:22:54 tarm kernel: [ 1235.625239] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:22:54 tarm kernel: [ 1235.625403] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:22:54 tarm kernel: [ 1235.625538] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:22:54 tarm kernel: [ 1235.625674] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:22:54 tarm kernel: [ 1235.625803] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:23:16 tarm kernel: [ 1257.125017] __ratelimit: 9 messages suppressed
> May 26 17:23:16 tarm kernel: [ 1257.125262] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:23:16 tarm kernel: [ 1257.125404] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:23:16 tarm kernel: [ 1257.125536] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:23:16 tarm kernel: [ 1257.125673] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:23:54 tarm kernel: [ 1295.625025] __ratelimit: 10 messages suppressed
> May 26 17:23:54 tarm kernel: [ 1295.625295] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:23:54 tarm kernel: [ 1295.625453] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:23:54 tarm kernel: [ 1295.625591] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:23:54 tarm kernel: [ 1295.625732] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:23:54 tarm kernel: [ 1295.625866] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:23:54 tarm kernel: [ 1295.626006] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:23:54 tarm kernel: [ 1295.626069] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:23:55 tarm kernel: [ 1296.124988] cpufreq-core: target for CPU 0: 342857 kHz, relation 0
> May 26 17:24:22 tarm kernel: [ 1323.125013] __ratelimit: 6 messages suppressed
> May 26 17:24:22 tarm kernel: [ 1323.125256] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:24:22 tarm kernel: [ 1323.125399] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:24:22 tarm kernel: [ 1323.125532] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:24:22 tarm kernel: [ 1323.125670] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:24:22 tarm kernel: [ 1323.125798] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:24:25 tarm kernel: [ 1326.125101] __ratelimit: 9 messages suppressed
> May 26 17:24:25 tarm kernel: [ 1326.125315] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:24:28 tarm kernel: [ 1329.625024] __ratelimit: 46 messages suppressed
> May 26 17:24:28 tarm kernel: [ 1329.625208] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:24:33 tarm kernel: [ 1334.624994] __ratelimit: 53 messages suppressed
> May 26 17:24:33 tarm kernel: [ 1334.625181] cpufreq-core: target for CPU 0: 121828 kHz, relation 0
> May 26 17:24:44 tarm kernel: [ 1345.125022] __ratelimit: 6 messages suppressed
> May 26 17:24:44 tarm kernel: [ 1345.125262] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:24:44 tarm kernel: [ 1345.125404] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:24:49 tarm kernel: [ 1350.125010] __ratelimit: 12 messages suppressed
> May 26 17:24:49 tarm kernel: [ 1350.125260] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:24:54 tarm kernel: [ 1355.625050] __ratelimit: 34 messages suppressed
> May 26 17:24:54 tarm kernel: [ 1355.625262] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:25:01 tarm kernel: [ 1362.124998] __ratelimit: 34 messages suppressed
> May 26 17:25:01 tarm kernel: [ 1362.125214] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:25:03 tarm kernel: [ 1364.625011] __ratelimit: 13 messages suppressed
> May 26 17:25:03 tarm kernel: [ 1364.625239] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:25:09 tarm kernel: [ 1370.625010] __ratelimit: 27 messages suppressed
> May 26 17:25:09 tarm kernel: [ 1370.625247] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:25:24 tarm kernel: [ 1385.625023] __ratelimit: 13 messages suppressed
> May 26 17:25:24 tarm kernel: [ 1385.625231] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:25:24 tarm kernel: [ 1385.625374] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:25:24 tarm kernel: [ 1385.625510] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:25:29 tarm kernel: [ 1390.125013] __ratelimit: 25 messages suppressed
> May 26 17:25:29 tarm kernel: [ 1390.125240] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:25:36 tarm kernel: [ 1397.125009] __ratelimit: 20 messages suppressed
> May 26 17:25:36 tarm kernel: [ 1397.125254] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:25:38 tarm kernel: [ 1399.625042] __ratelimit: 20 messages suppressed
> May 26 17:25:38 tarm kernel: [ 1399.625259] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:25:54 tarm kernel: [ 1415.625005] __ratelimit: 41 messages suppressed
> May 26 17:25:54 tarm kernel: [ 1415.625225] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:25:54 tarm kernel: [ 1415.625370] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:25:54 tarm kernel: [ 1415.625506] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:26:27 tarm kernel: [ 1448.625114] __ratelimit: 11 messages suppressed
> May 26 17:26:27 tarm kernel: [ 1448.625339] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:26:27 tarm kernel: [ 1448.625508] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:26:27 tarm kernel: [ 1448.625693] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:26:27 tarm kernel: [ 1448.625829] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:26:27 tarm kernel: [ 1448.625957] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:26:27 tarm kernel: [ 1448.626090] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:26:54 tarm kernel: [ 1476.125842] __ratelimit: 8 messages suppressed
> May 26 17:26:54 tarm kernel: [ 1476.126064] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:26:54 tarm kernel: [ 1476.126209] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:26:54 tarm kernel: [ 1476.126346] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:26:54 tarm kernel: [ 1476.126485] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:26:54 tarm kernel: [ 1476.126616] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:26:54 tarm kernel: [ 1476.126753] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:27:07 tarm kernel: [ 1488.625025] __ratelimit: 8 messages suppressed
> May 26 17:27:07 tarm kernel: [ 1488.625264] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:27:07 tarm kernel: [ 1488.625406] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:27:09 tarm kernel: [ 1491.128646] __ratelimit: 12 messages suppressed
> May 26 17:27:09 tarm kernel: [ 1491.128868] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:27:14 tarm kernel: [ 1496.125016] __ratelimit: 27 messages suppressed
> May 26 17:27:14 tarm kernel: [ 1496.125257] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:27:21 tarm kernel: [ 1502.625087] __ratelimit: 34 messages suppressed
> May 26 17:27:21 tarm kernel: [ 1502.625320] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:27:26 tarm kernel: [ 1507.625104] __ratelimit: 13 messages suppressed
> May 26 17:27:26 tarm kernel: [ 1507.625321] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:27:54 tarm kernel: [ 1536.125010] __ratelimit: 18 messages suppressed
> May 26 17:27:54 tarm kernel: [ 1536.125254] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:27:54 tarm kernel: [ 1536.125395] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:27:54 tarm kernel: [ 1536.125529] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:27:54 tarm kernel: [ 1536.125666] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:27:54 tarm kernel: [ 1536.125794] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:27:54 tarm kernel: [ 1536.125928] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:28:35 tarm kernel: [ 1577.125012] __ratelimit: 15 messages suppressed
> May 26 17:28:35 tarm kernel: [ 1577.125259] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:28:35 tarm kernel: [ 1577.125429] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:28:35 tarm kernel: [ 1577.125565] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:28:35 tarm kernel: [ 1577.125702] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:28:35 tarm kernel: [ 1577.125831] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:28:35 tarm kernel: [ 1577.125965] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:28:35 tarm kernel: [ 1577.126019] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:28:36 tarm kernel: [ 1577.625003] cpufreq-core: target for CPU 0: 914285 kHz, relation 0
> May 26 17:28:55 tarm kernel: [ 1596.625005] __ratelimit: 13 messages suppressed
> May 26 17:28:55 tarm kernel: [ 1596.625226] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:28:55 tarm kernel: [ 1596.625396] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:28:55 tarm kernel: [ 1596.625533] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:28:55 tarm kernel: [ 1596.625686] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:29:04 tarm kernel: [ 1605.626418] __ratelimit: 10 messages suppressed
> May 26 17:29:04 tarm kernel: [ 1605.626630] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:29:04 tarm kernel: [ 1605.626772] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:29:24 tarm kernel: [ 1625.625002] __ratelimit: 40 messages suppressed
> May 26 17:29:24 tarm kernel: [ 1625.625218] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:29:24 tarm kernel: [ 1625.625363] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:29:24 tarm kernel: [ 1625.625501] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:29:24 tarm kernel: [ 1625.625643] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:29:39 tarm kernel: [ 1641.125020] __ratelimit: 31 messages suppressed
> May 26 17:29:39 tarm kernel: [ 1641.125248] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:29:39 tarm kernel: [ 1641.125387] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:29:39 tarm kernel: [ 1641.125519] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:29:43 tarm kernel: [ 1644.624994] __ratelimit: 16 messages suppressed
> May 26 17:29:43 tarm kernel: [ 1644.625160] cpufreq-core: target for CPU 0: 152342 kHz, relation 0
> May 26 17:30:05 tarm kernel: [ 1666.625410] __ratelimit: 6 messages suppressed
> May 26 17:30:05 tarm kernel: [ 1666.625629] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:30:05 tarm kernel: [ 1666.625774] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:30:05 tarm kernel: [ 1666.625912] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:30:05 tarm kernel: [ 1666.626054] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:30:12 tarm kernel: [ 1674.125189] __ratelimit: 17 messages suppressed
> May 26 17:30:12 tarm kernel: [ 1674.125425] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:30:13 tarm kernel: [ 1674.624988] __ratelimit: 6 messages suppressed
> May 26 17:30:13 tarm kernel: [ 1674.625130] cpufreq-core: target for CPU 0: 0 kHz, relation 0
> May 26 17:30:18 tarm kernel: [ 1680.124993] __ratelimit: 13 messages suppressed
> May 26 17:30:18 tarm kernel: [ 1680.125137] cpufreq-core: target for CPU 0: 57142 kHz, relation 0
> May 26 17:30:23 tarm kernel: [ 1684.625011] __ratelimit: 41 messages suppressed
> May 26 17:30:23 tarm kernel: [ 1684.625238] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:30:25 tarm kernel: [ 1687.103612] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 17:30:25 tarm kernel: [ 1687.103851] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:30:25 tarm kernel: [ 1687.103983] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 17:30:25 tarm kernel: [ 1687.104121] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 17:30:25 tarm kernel: [ 1687.104257] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:30:25 tarm kernel: [ 1687.104385] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
> May 26 17:30:25 tarm kernel: [ 1687.104521] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
> May 26 17:30:25 tarm kernel: [ 1687.104656] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
> May 26 17:30:25 tarm kernel: [ 1687.104788] cpufreq-core: governor: change or update limits
> May 26 17:30:25 tarm kernel: [ 1687.105041] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 17:30:33 tarm kernel: [ 1695.412124] __ratelimit: 25 messages suppressed
> May 26 17:30:33 tarm kernel: [ 1695.412329] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
> May 26 17:30:33 tarm kernel: [ 1695.412490] cpufreq-core: updating policy for CPU 0
> May 26 17:30:33 tarm kernel: [ 1695.412623] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 17:30:33 tarm kernel: [ 1695.412757] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:30:33 tarm kernel: [ 1695.413087] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 17:30:33 tarm kernel: [ 1695.413265] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 17:30:33 tarm kernel: [ 1695.413402] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:30:33 tarm kernel: [ 1695.413529] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 17:30:33 tarm kernel: [ 1695.413664] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 17:30:33 tarm kernel: [ 1695.413798] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
> May 26 17:30:33 tarm kernel: [ 1695.413929] cpufreq-core: governor: change or update limits
> May 26 17:30:33 tarm kernel: [ 1695.414056] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 17:30:51 tarm kernel: [ 1712.625338] __ratelimit: 3 messages suppressed
> May 26 17:30:51 tarm kernel: [ 1712.625566] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:30:51 tarm kernel: [ 1712.625711] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:30:51 tarm kernel: [ 1712.625863] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:30:55 tarm kernel: [ 1716.625004] __ratelimit: 11 messages suppressed
> May 26 17:30:55 tarm kernel: [ 1716.625234] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:30:58 tarm kernel: [ 1719.625020] __ratelimit: 20 messages suppressed
> May 26 17:30:58 tarm kernel: [ 1719.625245] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:31:08 tarm kernel: [ 1729.625013] __ratelimit: 20 messages suppressed
> May 26 17:31:08 tarm kernel: [ 1729.625257] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:31:08 tarm kernel: [ 1729.625405] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:31:55 tarm kernel: [ 1777.125078] __ratelimit: 33 messages suppressed
> May 26 17:31:55 tarm kernel: [ 1777.125305] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:31:55 tarm kernel: [ 1777.125462] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:31:55 tarm kernel: [ 1777.125596] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:31:55 tarm kernel: [ 1777.125733] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:31:55 tarm kernel: [ 1777.125862] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:31:55 tarm kernel: [ 1777.126989] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:31:55 tarm kernel: [ 1777.127043] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:31:56 tarm kernel: [ 1777.625029] cpufreq-core: target for CPU 0: 1257142 kHz, relation 0
> May 26 17:31:56 tarm kernel: [ 1777.625190] acpi-cpufreq: acpi_cpufreq_target 1257142 (0)
> May 26 17:32:08 tarm kernel: [ 1789.625048] __ratelimit: 12 messages suppressed
> May 26 17:32:08 tarm kernel: [ 1789.625277] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:32:08 tarm kernel: [ 1789.625420] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:32:08 tarm kernel: [ 1789.625554] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:32:27 tarm kernel: [ 1808.625076] __ratelimit: 23 messages suppressed
> May 26 17:32:27 tarm kernel: [ 1808.625314] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:32:27 tarm kernel: [ 1808.625477] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:32:27 tarm kernel: [ 1808.625611] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:32:28 tarm kernel: [ 1809.625036] __ratelimit: 11 messages suppressed
> May 26 17:32:28 tarm kernel: [ 1809.625204] cpufreq-core: target for CPU 0: 594285 kHz, relation 0
> May 26 17:32:55 tarm kernel: [ 1837.125529] __ratelimit: 6 messages suppressed
> May 26 17:32:55 tarm kernel: [ 1837.125771] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:32:55 tarm kernel: [ 1837.125927] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:32:55 tarm kernel: [ 1837.126060] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:32:55 tarm kernel: [ 1837.126220] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:32:55 tarm kernel: [ 1837.126384] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:33:08 tarm kernel: [ 1850.124998] __ratelimit: 9 messages suppressed
> May 26 17:33:08 tarm kernel: [ 1850.125223] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:33:08 tarm kernel: [ 1850.125389] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:33:08 tarm kernel: [ 1850.125546] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:33:15 tarm kernel: [ 1856.625076] __ratelimit: 11 messages suppressed
> May 26 17:33:15 tarm kernel: [ 1856.625322] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:33:22 tarm kernel: [ 1864.124999] __ratelimit: 13 messages suppressed
> May 26 17:33:22 tarm kernel: [ 1864.125220] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:33:23 tarm kernel: [ 1864.624994] __ratelimit: 6 messages suppressed
> May 26 17:33:23 tarm kernel: [ 1864.625132] cpufreq-core: target for CPU 0: 0 kHz, relation 0
> May 26 17:33:37 tarm kernel: [ 1878.625014] __ratelimit: 60 messages suppressed
> May 26 17:33:37 tarm kernel: [ 1878.625252] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:33:37 tarm kernel: [ 1878.625420] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:33:38 tarm kernel: [ 1879.624989] __ratelimit: 10 messages suppressed
> May 26 17:33:38 tarm kernel: [ 1879.625128] cpufreq-core: target for CPU 0: 228571 kHz, relation 0
> May 26 17:33:43 tarm kernel: [ 1884.626773] __ratelimit: 20 messages suppressed
> May 26 17:33:43 tarm kernel: [ 1884.626985] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:33:49 tarm kernel: [ 1891.128517] __ratelimit: 34 messages suppressed
> May 26 17:33:49 tarm kernel: [ 1891.128729] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:33:53 tarm kernel: [ 1894.624989] __ratelimit: 27 messages suppressed
> May 26 17:33:53 tarm kernel: [ 1894.625138] cpufreq-core: target for CPU 0: 914285 kHz, relation 0
> May 26 17:34:10 tarm kernel: [ 1911.625009] __ratelimit: 27 messages suppressed
> May 26 17:34:10 tarm kernel: [ 1911.625242] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:34:10 tarm kernel: [ 1911.625381] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:34:10 tarm kernel: [ 1911.625513] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:34:57 tarm kernel: [ 1959.125001] __ratelimit: 25 messages suppressed
> May 26 17:34:57 tarm kernel: [ 1959.125227] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:34:57 tarm kernel: [ 1959.125397] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:34:57 tarm kernel: [ 1959.125532] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:34:57 tarm kernel: [ 1959.125670] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:34:57 tarm kernel: [ 1959.125798] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:34:57 tarm kernel: [ 1959.125931] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:34:57 tarm kernel: [ 1959.125986] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:34:58 tarm kernel: [ 1959.624990] cpufreq-core: target for CPU 0: 1257142 kHz, relation 0
> May 26 17:34:58 tarm kernel: [ 1959.625142] acpi-cpufreq: acpi_cpufreq_target 1257142 (0)
> May 26 17:34:58 tarm kernel: [ 1959.625221] freq-table: request for target 1257142 kHz (relation: 0) for cpu 0
> May 26 17:35:03 tarm kernel: [ 1964.624997] __ratelimit: 39 messages suppressed
> May 26 17:35:03 tarm kernel: [ 1964.625162] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:35:09 tarm kernel: [ 1970.625110] __ratelimit: 34 messages suppressed
> May 26 17:35:09 tarm kernel: [ 1970.625347] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:35:13 tarm kernel: [ 1974.625010] __ratelimit: 39 messages suppressed
> May 26 17:35:13 tarm kernel: [ 1974.625164] cpufreq-core: target for CPU 0: 914285 kHz, relation 0
> May 26 17:35:18 tarm kernel: [ 1979.624990] __ratelimit: 27 messages suppressed
> May 26 17:35:18 tarm kernel: [ 1979.625150] cpufreq-core: target for CPU 0: 137142 kHz, relation 0
> May 26 17:35:23 tarm kernel: [ 1984.625099] __ratelimit: 13 messages suppressed
> May 26 17:35:23 tarm kernel: [ 1984.625242] cpufreq-core: target for CPU 0: 228571 kHz, relation 0
> May 26 17:35:28 tarm kernel: [ 1989.625013] __ratelimit: 20 messages suppressed
> May 26 17:35:28 tarm kernel: [ 1989.625247] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:35:53 tarm kernel: [ 2014.625029] __ratelimit: 13 messages suppressed
> May 26 17:35:53 tarm kernel: [ 2014.625260] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:35:53 tarm kernel: [ 2014.625408] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:35:53 tarm kernel: [ 2014.625545] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:35:53 tarm kernel: [ 2014.625688] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:35:53 tarm kernel: [ 2014.625830] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:35:58 tarm kernel: [ 2020.124991] __ratelimit: 49 messages suppressed
> May 26 17:35:58 tarm kernel: [ 2020.125144] cpufreq-core: target for CPU 0: 960000 kHz, relation 0
> May 26 17:36:04 tarm kernel: [ 2025.625733] __ratelimit: 27 messages suppressed
> May 26 17:36:04 tarm kernel: [ 2025.625970] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:36:08 tarm kernel: [ 2030.124999] __ratelimit: 27 messages suppressed
> May 26 17:36:08 tarm kernel: [ 2030.125208] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:36:45 tarm kernel: [ 2066.624998] __ratelimit: 13 messages suppressed
> May 26 17:36:45 tarm kernel: [ 2066.625471] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:36:45 tarm kernel: [ 2066.625649] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:36:45 tarm kernel: [ 2066.625789] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:36:45 tarm kernel: [ 2066.625927] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:36:45 tarm kernel: [ 2066.626087] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:36:45 tarm kernel: [ 2066.626225] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:36:45 tarm kernel: [ 2066.626279] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:36:56 tarm kernel: [ 2077.625025] __ratelimit: 21 messages suppressed
> May 26 17:36:56 tarm kernel: [ 2077.625259] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:36:56 tarm kernel: [ 2077.625402] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:37:32 tarm kernel: [ 2114.125331] __ratelimit: 12 messages suppressed
> May 26 17:37:32 tarm kernel: [ 2114.125558] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:37:32 tarm kernel: [ 2114.125703] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:37:32 tarm kernel: [ 2114.125839] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:37:32 tarm kernel: [ 2114.125978] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:37:32 tarm kernel: [ 2114.126110] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:37:32 tarm kernel: [ 2114.126249] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:37:32 tarm kernel: [ 2114.126305] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:37:33 tarm kernel: [ 2114.624991] cpufreq-core: target for CPU 0: 1771428 kHz, relation 0
> May 26 17:37:38 tarm kernel: [ 2120.125076] __ratelimit: 11 messages suppressed
> May 26 17:37:38 tarm kernel: [ 2120.125306] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:37:43 tarm kernel: [ 2124.625018] __ratelimit: 27 messages suppressed
> May 26 17:37:43 tarm kernel: [ 2124.625164] cpufreq-core: target for CPU 0: 514285 kHz, relation 0
> May 26 17:37:51 tarm kernel: [ 2133.125018] __ratelimit: 6 messages suppressed
> May 26 17:37:51 tarm kernel: [ 2133.125274] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:37:53 tarm kernel: [ 2135.124987] __ratelimit: 20 messages suppressed
> May 26 17:37:53 tarm kernel: [ 2135.125133] cpufreq-core: target for CPU 0: 400000 kHz, relation 0
> May 26 17:38:08 tarm kernel: [ 2150.125024] __ratelimit: 20 messages suppressed
> May 26 17:38:08 tarm kernel: [ 2150.125263] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:38:08 tarm kernel: [ 2150.125406] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:38:08 tarm kernel: [ 2150.125541] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:38:44 tarm kernel: [ 2186.125030] __ratelimit: 39 messages suppressed
> May 26 17:38:44 tarm kernel: [ 2186.125274] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:38:44 tarm kernel: [ 2186.125419] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:38:44 tarm kernel: [ 2186.125554] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:38:44 tarm kernel: [ 2186.125692] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:38:44 tarm kernel: [ 2186.125950] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:38:44 tarm kernel: [ 2186.126086] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:38:44 tarm kernel: [ 2186.126140] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:39:42 tarm kernel: [ 2244.125003] __ratelimit: 7 messages suppressed
> May 26 17:39:42 tarm kernel: [ 2244.125386] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:39:42 tarm kernel: [ 2244.125533] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:39:42 tarm kernel: [ 2244.125668] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:39:42 tarm kernel: [ 2244.125805] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:39:42 tarm kernel: [ 2244.125933] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:39:42 tarm kernel: [ 2244.126067] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:39:42 tarm kernel: [ 2244.126122] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:39:43 tarm kernel: [ 2244.624993] cpufreq-core: target for CPU 0: 1142857 kHz, relation 0
> May 26 17:39:43 tarm kernel: [ 2244.625151] acpi-cpufreq: acpi_cpufreq_target 1142857 (0)
> May 26 17:39:43 tarm kernel: [ 2244.625231] freq-table: request for target 1142857 kHz (relation: 0) for cpu 0
> May 26 17:39:47 tarm kernel: [ 2249.124999] __ratelimit: 11 messages suppressed
> May 26 17:39:47 tarm kernel: [ 2249.125216] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:39:55 tarm kernel: [ 2257.125017] __ratelimit: 27 messages suppressed
> May 26 17:39:55 tarm kernel: [ 2257.125257] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:39:57 tarm kernel: [ 2259.124988] __ratelimit: 20 messages suppressed
> May 26 17:39:57 tarm kernel: [ 2259.125137] cpufreq-core: target for CPU 0: 342857 kHz, relation 0
> May 26 17:40:03 tarm kernel: [ 2264.625779] __ratelimit: 6 messages suppressed
> May 26 17:40:03 tarm kernel: [ 2264.626008] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:40:08 tarm kernel: [ 2269.625005] __ratelimit: 13 messages suppressed
> May 26 17:40:08 tarm kernel: [ 2269.625224] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:40:16 tarm kernel: [ 2277.625001] __ratelimit: 13 messages suppressed
> May 26 17:40:16 tarm kernel: [ 2277.625225] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:40:57 tarm kernel: [ 2318.625170] __ratelimit: 13 messages suppressed
> May 26 17:40:57 tarm kernel: [ 2318.625402] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:40:57 tarm kernel: [ 2318.625545] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:40:57 tarm kernel: [ 2318.625680] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:40:57 tarm kernel: [ 2318.625833] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:40:57 tarm kernel: [ 2318.625962] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:40:57 tarm kernel: [ 2318.626095] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:40:57 tarm kernel: [ 2318.626149] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:40:57 tarm kernel: [ 2319.124990] cpufreq-core: target for CPU 0: 400000 kHz, relation 0
> May 26 17:40:57 tarm kernel: [ 2319.125141] acpi-cpufreq: acpi_cpufreq_target 400000 (0)
> May 26 17:41:07 tarm kernel: [ 2329.125011] __ratelimit: 5 messages suppressed
> May 26 17:41:07 tarm kernel: [ 2329.125242] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:41:07 tarm kernel: [ 2329.125381] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:41:13 tarm kernel: [ 2334.625002] __ratelimit: 33 messages suppressed
> May 26 17:41:13 tarm kernel: [ 2334.625220] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:41:19 tarm kernel: [ 2340.625925] __ratelimit: 27 messages suppressed
> May 26 17:41:19 tarm kernel: [ 2340.626164] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:41:22 tarm kernel: [ 2344.125010] __ratelimit: 27 messages suppressed
> May 26 17:41:22 tarm kernel: [ 2344.125242] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:42:05 tarm kernel: [ 2386.625014] __ratelimit: 41 messages suppressed
> May 26 17:42:05 tarm kernel: [ 2386.625238] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:42:05 tarm kernel: [ 2386.625411] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:42:05 tarm kernel: [ 2386.625548] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:42:05 tarm kernel: [ 2386.625689] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:42:05 tarm kernel: [ 2386.625818] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:42:05 tarm kernel: [ 2386.626082] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:42:05 tarm kernel: [ 2386.626137] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:42:05 tarm kernel: [ 2387.124995] cpufreq-core: target for CPU 0: 114285 kHz, relation 0
> May 26 17:42:23 tarm kernel: [ 2405.126157] __ratelimit: 6 messages suppressed
> May 26 17:42:23 tarm kernel: [ 2405.126390] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:42:23 tarm kernel: [ 2405.126536] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:42:23 tarm kernel: [ 2405.126671] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:42:23 tarm kernel: [ 2405.126810] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:42:27 tarm kernel: [ 2409.124997] __ratelimit: 31 messages suppressed
> May 26 17:42:27 tarm kernel: [ 2409.125156] cpufreq-core: target for CPU 0: 960000 kHz, relation 0
> May 26 17:42:57 tarm kernel: [ 2439.125015] __ratelimit: 13 messages suppressed
> May 26 17:42:57 tarm kernel: [ 2439.125247] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:42:57 tarm kernel: [ 2439.125392] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:42:57 tarm kernel: [ 2439.125526] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:42:57 tarm kernel: [ 2439.125664] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:42:57 tarm kernel: [ 2439.125792] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:42:57 tarm kernel: [ 2439.125926] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:44:08 tarm kernel: [ 2509.627811] __ratelimit: 15 messages suppressed
> May 26 17:44:08 tarm kernel: [ 2509.628028] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:44:08 tarm kernel: [ 2509.628172] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:44:08 tarm kernel: [ 2509.628479] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:44:08 tarm kernel: [ 2509.628623] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:44:08 tarm kernel: [ 2509.628782] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:44:08 tarm kernel: [ 2509.628934] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:44:08 tarm kernel: [ 2509.629114] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:44:08 tarm kernel: [ 2510.128990] cpufreq-core: target for CPU 0: 1200000 kHz, relation 0
> May 26 17:44:08 tarm kernel: [ 2510.129147] acpi-cpufreq: acpi_cpufreq_target 1200000 (0)
> May 26 17:44:08 tarm kernel: [ 2510.129225] freq-table: request for target 1200000 kHz (relation: 0) for cpu 0
> May 26 17:45:53 tarm kernel: [ 2614.625003] __ratelimit: 11 messages suppressed
> May 26 17:45:53 tarm kernel: [ 2614.625214] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:45:53 tarm kernel: [ 2614.625359] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:45:53 tarm kernel: [ 2614.625497] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:45:53 tarm kernel: [ 2614.625638] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:45:53 tarm kernel: [ 2614.625773] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:45:53 tarm kernel: [ 2614.625914] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:45:53 tarm kernel: [ 2614.625971] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:45:53 tarm kernel: [ 2615.124994] cpufreq-core: target for CPU 0: 0 kHz, relation 0
> May 26 17:45:53 tarm kernel: [ 2615.125153] acpi-cpufreq: acpi_cpufreq_target 0 (0)
> May 26 17:45:53 tarm kernel: [ 2615.125213] freq-table: request for target 0 kHz (relation: 0) for cpu 0
> May 26 17:45:58 tarm kernel: [ 2620.125038] __ratelimit: 4 messages suppressed
> May 26 17:45:58 tarm kernel: [ 2620.125262] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:46:30 tarm kernel: [ 2652.125063] __ratelimit: 13 messages suppressed
> May 26 17:46:30 tarm kernel: [ 2652.125294] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:46:30 tarm kernel: [ 2652.125434] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:46:30 tarm kernel: [ 2652.125566] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:46:30 tarm kernel: [ 2652.125702] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:46:30 tarm kernel: [ 2652.125831] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:46:30 tarm kernel: [ 2652.125965] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:47:03 tarm kernel: [ 2684.630045] __ratelimit: 8 messages suppressed
> May 26 17:47:03 tarm kernel: [ 2684.630290] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:47:03 tarm kernel: [ 2684.630432] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:47:03 tarm kernel: [ 2684.630565] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:47:03 tarm kernel: [ 2684.630702] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:47:03 tarm kernel: [ 2684.630832] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:47:03 tarm kernel: [ 2684.630968] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:47:03 tarm kernel: [ 2684.631023] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:47:24 tarm kernel: [ 2706.124999] __ratelimit: 7 messages suppressed
> May 26 17:47:24 tarm kernel: [ 2706.125221] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:47:24 tarm kernel: [ 2706.125385] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:47:24 tarm kernel: [ 2706.125520] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:47:24 tarm kernel: [ 2706.125658] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:47:58 tarm kernel: [ 2740.124998] __ratelimit: 10 messages suppressed
> May 26 17:47:58 tarm kernel: [ 2740.125220] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:47:58 tarm kernel: [ 2740.125409] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:47:58 tarm kernel: [ 2740.125545] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:47:58 tarm kernel: [ 2740.125683] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:47:58 tarm kernel: [ 2740.125811] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:47:58 tarm kernel: [ 2740.125946] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:47:58 tarm kernel: [ 2740.126000] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:48:09 tarm kernel: [ 2751.125047] __ratelimit: 21 messages suppressed
> May 26 17:48:09 tarm kernel: [ 2751.125269] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:48:09 tarm kernel: [ 2751.125434] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:48:58 tarm kernel: [ 2800.125099] __ratelimit: 33 messages suppressed
> May 26 17:48:58 tarm kernel: [ 2800.125338] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:48:58 tarm kernel: [ 2800.125482] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:48:58 tarm kernel: [ 2800.125617] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:48:58 tarm kernel: [ 2800.125756] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:48:58 tarm kernel: [ 2800.125886] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:48:58 tarm kernel: [ 2800.126021] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:48:58 tarm kernel: [ 2800.126075] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:48:59 tarm kernel: [ 2801.124990] cpufreq-core: target for CPU 0: 285714 kHz, relation 0
> May 26 17:48:59 tarm kernel: [ 2801.125146] acpi-cpufreq: acpi_cpufreq_target 285714 (0)
> May 26 17:48:59 tarm kernel: [ 2801.125221] freq-table: request for target 285714 kHz (relation: 0) for cpu 0
> May 26 17:49:05 tarm kernel: [ 2806.625051] __ratelimit: 4 messages suppressed
> May 26 17:49:05 tarm kernel: [ 2806.625274] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:49:36 tarm kernel: [ 2837.625751] __ratelimit: 13 messages suppressed
> May 26 17:49:36 tarm kernel: [ 2837.625989] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:49:36 tarm kernel: [ 2837.626134] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:49:36 tarm kernel: [ 2837.626432] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:49:36 tarm kernel: [ 2837.626578] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:49:36 tarm kernel: [ 2837.626711] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:49:36 tarm kernel: [ 2837.626849] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:49:48 tarm kernel: [ 2850.125068] __ratelimit: 8 messages suppressed
> May 26 17:49:48 tarm kernel: [ 2850.125309] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:49:48 tarm kernel: [ 2850.125449] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:49:48 tarm kernel: [ 2850.125581] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:50:37 tarm kernel: [ 2898.625001] __ratelimit: 11 messages suppressed
> May 26 17:50:37 tarm kernel: [ 2898.625247] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:50:37 tarm kernel: [ 2898.625393] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:50:37 tarm kernel: [ 2898.625543] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:50:37 tarm kernel: [ 2898.625682] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:50:37 tarm kernel: [ 2898.625811] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:50:37 tarm kernel: [ 2898.625945] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:50:37 tarm kernel: [ 2898.625999] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:50:37 tarm kernel: [ 2899.124989] cpufreq-core: target for CPU 0: 0 kHz, relation 0
> May 26 17:50:37 tarm kernel: [ 2899.125144] acpi-cpufreq: acpi_cpufreq_target 0 (0)
> May 26 17:51:20 tarm kernel: [ 2941.625016] __ratelimit: 5 messages suppressed
> May 26 17:51:20 tarm kernel: [ 2941.625237] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:51:20 tarm kernel: [ 2941.625406] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:51:20 tarm kernel: [ 2941.625546] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:51:20 tarm kernel: [ 2941.625689] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:51:20 tarm kernel: [ 2941.625824] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:51:20 tarm kernel: [ 2941.626027] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:51:20 tarm kernel: [ 2941.626285] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:51:20 tarm kernel: [ 2942.124990] cpufreq-core: target for CPU 0: 1085714 kHz, relation 0
> May 26 17:51:20 tarm kernel: [ 2942.125146] acpi-cpufreq: acpi_cpufreq_target 1085714 (0)
> May 26 17:51:23 tarm kernel: [ 2945.124994] __ratelimit: 31 messages suppressed
> May 26 17:51:23 tarm kernel: [ 2945.125180] cpufreq-core: target for CPU 0: 944171 kHz, relation 0
> May 26 17:51:28 tarm kernel: [ 2950.124996] __ratelimit: 37 messages suppressed
> May 26 17:51:28 tarm kernel: [ 2950.125182] cpufreq-core: target for CPU 0: 852800 kHz, relation 0
> May 26 17:51:55 tarm kernel: [ 2977.125010] __ratelimit: 26 messages suppressed
> May 26 17:51:55 tarm kernel: [ 2977.125244] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:51:55 tarm kernel: [ 2977.125384] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:51:55 tarm kernel: [ 2977.125516] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:51:55 tarm kernel: [ 2977.125652] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:51:55 tarm kernel: [ 2977.125806] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:51:58 tarm kernel: [ 2980.125002] __ratelimit: 30 messages suppressed
> May 26 17:51:58 tarm kernel: [ 2980.125197] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:52:03 tarm kernel: [ 2984.753859] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 17:52:03 tarm kernel: [ 2984.754110] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:52:03 tarm kernel: [ 2984.754246] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 17:52:03 tarm kernel: [ 2984.754387] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 17:52:03 tarm kernel: [ 2984.754526] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:52:03 tarm kernel: [ 2984.754657] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
> May 26 17:52:03 tarm kernel: [ 2984.754935] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
> May 26 17:52:03 tarm kernel: [ 2984.755073] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
> May 26 17:52:03 tarm kernel: [ 2984.755208] cpufreq-core: governor: change or update limits
> May 26 17:52:03 tarm kernel: [ 2984.755339] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 17:52:15 tarm kernel: [ 2997.184583] __ratelimit: 39 messages suppressed
> May 26 17:52:15 tarm kernel: [ 2997.184789] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
> May 26 17:52:15 tarm kernel: [ 2997.185072] cpufreq-core: updating policy for CPU 0
> May 26 17:52:15 tarm kernel: [ 2997.185310] acpi-cpufreq: get_cur_freq_on_cpu (0)
> May 26 17:52:15 tarm kernel: [ 2997.185448] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 17:52:15 tarm kernel: [ 2997.185583] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:52:15 tarm kernel: [ 2997.185710] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 17:52:15 tarm kernel: [ 2997.185846] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 17:52:15 tarm kernel: [ 2997.186002] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:52:15 tarm kernel: [ 2997.186153] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 17:52:15 tarm kernel: [ 2997.186289] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 17:52:15 tarm kernel: [ 2997.186423] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
> May 26 17:52:15 tarm kernel: [ 2997.186555] cpufreq-core: governor: change or update limits
> May 26 17:52:15 tarm kernel: [ 2997.186682] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 17:53:50 tarm kernel: [ 3091.625021] __ratelimit: 2 messages suppressed
> May 26 17:53:50 tarm kernel: [ 3091.625236] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:53:50 tarm kernel: [ 3091.625380] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:53:50 tarm kernel: [ 3091.625514] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:53:50 tarm kernel: [ 3091.625653] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:53:50 tarm kernel: [ 3091.625785] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:53:50 tarm kernel: [ 3091.626086] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:53:50 tarm kernel: [ 3091.626142] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:53:50 tarm kernel: [ 3092.124989] cpufreq-core: target for CPU 0: 171428 kHz, relation 0
> May 26 17:53:50 tarm kernel: [ 3092.125141] acpi-cpufreq: acpi_cpufreq_target 171428 (0)
> May 26 17:53:50 tarm kernel: [ 3092.125227] freq-table: request for target 171428 kHz (relation: 0) for cpu 0
> May 26 17:54:23 tarm kernel: [ 3125.125835] __ratelimit: 4 messages suppressed
> May 26 17:54:23 tarm kernel: [ 3125.126073] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:54:23 tarm kernel: [ 3125.126214] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:54:23 tarm kernel: [ 3125.126374] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:54:23 tarm kernel: [ 3125.126511] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:54:23 tarm kernel: [ 3125.126639] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:54:23 tarm kernel: [ 3125.126772] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:54:25 tarm kernel: [ 3126.625001] __ratelimit: 15 messages suppressed
> May 26 17:54:25 tarm kernel: [ 3126.625156] cpufreq-core: target for CPU 0: 1600000 kHz, relation 0
> May 26 17:54:59 tarm kernel: [ 3161.125068] __ratelimit: 13 messages suppressed
> May 26 17:54:59 tarm kernel: [ 3161.125422] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:54:59 tarm kernel: [ 3161.125563] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:54:59 tarm kernel: [ 3161.125695] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:54:59 tarm kernel: [ 3161.125831] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:54:59 tarm kernel: [ 3161.125960] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:54:59 tarm kernel: [ 3161.126189] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:55:00 tarm kernel: [ 3161.624989] __ratelimit: 1 messages suppressed
> May 26 17:55:00 tarm kernel: [ 3161.625138] cpufreq-core: target for CPU 0: 628571 kHz, relation 0
> May 26 17:57:59 tarm kernel: [ 3341.125000] __ratelimit: 20 messages suppressed
> May 26 17:57:59 tarm kernel: [ 3341.125237] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:57:59 tarm kernel: [ 3341.125407] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:57:59 tarm kernel: [ 3341.125542] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:57:59 tarm kernel: [ 3341.125680] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:57:59 tarm kernel: [ 3341.125808] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:57:59 tarm kernel: [ 3341.125941] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 17:57:59 tarm kernel: [ 3341.126003] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 17:58:00 tarm kernel: [ 3342.124989] cpufreq-core: target for CPU 0: 0 kHz, relation 0
> May 26 17:58:00 tarm kernel: [ 3342.125176] acpi-cpufreq: acpi_cpufreq_target 0 (0)
> May 26 17:58:00 tarm kernel: [ 3342.125238] freq-table: request for target 0 kHz (relation: 0) for cpu 0
> May 26 17:58:09 tarm kernel: [ 3350.625020] __ratelimit: 4 messages suppressed
> May 26 17:58:09 tarm kernel: [ 3350.625222] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:58:11 tarm kernel: [ 3353.124988] __ratelimit: 6 messages suppressed
> May 26 17:58:11 tarm kernel: [ 3353.125210] cpufreq-core: target for CPU 0: 1600000 kHz, relation 0
> May 26 17:58:16 tarm kernel: [ 3357.625011] __ratelimit: 13 messages suppressed
> May 26 17:58:16 tarm kernel: [ 3357.625238] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:58:20 tarm kernel: [ 3361.625052] __ratelimit: 39 messages suppressed
> May 26 17:58:20 tarm kernel: [ 3361.625267] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:58:24 tarm kernel: [ 3366.125013] __ratelimit: 48 messages suppressed
> May 26 17:58:24 tarm kernel: [ 3366.125240] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:58:27 tarm kernel: [ 3368.864167] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 17:58:27 tarm kernel: [ 3368.864411] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:58:27 tarm kernel: [ 3368.864544] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 17:58:27 tarm kernel: [ 3368.864681] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 17:58:27 tarm kernel: [ 3368.864816] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:58:27 tarm kernel: [ 3368.864944] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
> May 26 17:58:27 tarm kernel: [ 3368.865130] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
> May 26 17:58:27 tarm kernel: [ 3368.865297] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
> May 26 17:58:27 tarm kernel: [ 3368.865433] cpufreq-core: governor: change or update limits
> May 26 17:58:27 tarm kernel: [ 3368.865564] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 17:58:43 tarm kernel: [ 3385.479447] __ratelimit: 30 messages suppressed
> May 26 17:58:43 tarm kernel: [ 3385.479651] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
> May 26 17:58:43 tarm kernel: [ 3385.479810] cpufreq-core: updating policy for CPU 0
> May 26 17:58:43 tarm kernel: [ 3385.479938] acpi-cpufreq: get_cur_freq_on_cpu (0)
> May 26 17:58:43 tarm kernel: [ 3385.480067] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 17:58:43 tarm kernel: [ 3385.480199] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:58:43 tarm kernel: [ 3385.480325] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 17:58:43 tarm kernel: [ 3385.480459] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 17:58:43 tarm kernel: [ 3385.480591] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:58:43 tarm kernel: [ 3385.480716] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 17:58:43 tarm kernel: [ 3385.480850] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 17:58:43 tarm kernel: [ 3385.481074] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
> May 26 17:58:43 tarm kernel: [ 3385.481231] cpufreq-core: governor: change or update limits
> May 26 17:58:43 tarm kernel: [ 3385.481361] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 17:59:07 tarm kernel: [ 3408.625001] __ratelimit: 2 messages suppressed
> May 26 17:59:07 tarm kernel: [ 3408.625221] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:59:07 tarm kernel: [ 3408.625385] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:59:07 tarm kernel: [ 3408.625519] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:59:07 tarm kernel: [ 3408.625677] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:59:07 tarm kernel: [ 3408.625803] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:59:10 tarm kernel: [ 3411.625026] __ratelimit: 9 messages suppressed
> May 26 17:59:10 tarm kernel: [ 3411.625265] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:59:36 tarm kernel: [ 3438.125078] __ratelimit: 13 messages suppressed
> May 26 17:59:36 tarm kernel: [ 3438.125317] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:59:36 tarm kernel: [ 3438.125536] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 17:59:36 tarm kernel: [ 3438.125667] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 17:59:36 tarm kernel: [ 3438.125799] freq-table: target is 0 (2000000 kHz, 0)
> May 26 17:59:36 tarm kernel: [ 3438.127191] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 17:59:39 tarm kernel: [ 3441.125011] __ratelimit: 16 messages suppressed
> May 26 17:59:39 tarm kernel: [ 3441.125163] cpufreq-core: target for CPU 0: 571428 kHz, relation 0
> May 26 17:59:44 tarm kernel: [ 3446.129064] __ratelimit: 51 messages suppressed
> May 26 17:59:44 tarm kernel: [ 3446.129319] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 17:59:50 tarm kernel: [ 3451.625003] __ratelimit: 39 messages suppressed
> May 26 17:59:50 tarm kernel: [ 3451.625174] cpufreq-core: target for CPU 0: 1142857 kHz, relation 0
> May 26 17:59:54 tarm kernel: [ 3456.079363] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 17:59:54 tarm kernel: [ 3456.079519] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:59:54 tarm kernel: [ 3456.079577] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 17:59:54 tarm kernel: [ 3456.079647] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 17:59:54 tarm kernel: [ 3456.079707] acpi-cpufreq: acpi_cpufreq_verify
> May 26 17:59:54 tarm kernel: [ 3456.079762] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
> May 26 17:59:54 tarm kernel: [ 3456.079821] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
> May 26 17:59:54 tarm kernel: [ 3456.079879] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
> May 26 17:59:54 tarm kernel: [ 3456.079936] cpufreq-core: governor: change or update limits
> May 26 17:59:54 tarm kernel: [ 3456.079992] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 17:59:54 tarm kernel: [ 3456.080058] cpufreq-core: target for CPU 0: 800000 kHz, relation 1
> May 26 17:59:54 tarm kernel: [ 3456.080114] acpi-cpufreq: acpi_cpufreq_target 800000 (0)
> May 26 17:59:54 tarm kernel: [ 3456.080196] freq-table: request for target 800000 kHz (relation: 1) for cpu 0
> May 26 17:59:54 tarm kernel: [ 3456.080254] freq-table: target is 4 (800000 kHz, 4)
> May 26 17:59:54 tarm kernel: [ 3456.080310] cpufreq-core: notification 0 of frequency transition to 800000 kHz
> May 26 17:59:54 tarm kernel: [ 3456.080385] cpufreq-core: notification 1 of frequency transition to 800000 kHz
> May 26 17:59:54 tarm kernel: [ 3456.080439] cpufreq-core: scaling loops_per_jiffy to 3195449 for frequency 800000 kHz
> May 26 18:02:15 tarm kernel: [ 3597.291132] __ratelimit: 39 messages suppressed
> May 26 18:02:15 tarm kernel: [ 3597.291342] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
> May 26 18:02:15 tarm kernel: [ 3597.291480] cpufreq-core: updating policy for CPU 0
> May 26 18:02:15 tarm kernel: [ 3597.291608] acpi-cpufreq: get_cur_freq_on_cpu (0)
> May 26 18:02:15 tarm kernel: [ 3597.291734] acpi-cpufreq: get_cur_val = 100664850
> May 26 18:02:15 tarm kernel: [ 3597.291859] acpi-cpufreq: cur freq = 800000
> May 26 18:02:15 tarm kernel: [ 3597.291984] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 18:02:15 tarm kernel: [ 3597.292116] acpi-cpufreq: acpi_cpufreq_verify
> May 26 18:02:15 tarm kernel: [ 3597.292241] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 18:02:15 tarm kernel: [ 3597.292377] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 18:02:15 tarm kernel: [ 3597.292546] acpi-cpufreq: acpi_cpufreq_verify
> May 26 18:02:15 tarm kernel: [ 3597.292675] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 18:02:15 tarm kernel: [ 3597.292812] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 18:02:15 tarm kernel: [ 3597.293470] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
> May 26 18:02:15 tarm kernel: [ 3597.293635] cpufreq-core: governor: change or update limits
> May 26 18:02:15 tarm kernel: [ 3597.293768] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 18:02:17 tarm kernel: [ 3598.625022] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:02:17 tarm kernel: [ 3598.625266] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 18:02:17 tarm kernel: [ 3598.625404] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 18:02:17 tarm kernel: [ 3598.625541] freq-table: target is 0 (2000000 kHz, 0)
> May 26 18:02:17 tarm kernel: [ 3598.625671] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 18:02:21 tarm kernel: [ 3602.625004] __ratelimit: 28 messages suppressed
> May 26 18:02:21 tarm kernel: [ 3602.625238] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:02:26 tarm kernel: [ 3607.627568] __ratelimit: 39 messages suppressed
> May 26 18:02:26 tarm kernel: [ 3607.627787] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:02:28 tarm kernel: [ 3609.767385] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 18:02:28 tarm kernel: [ 3609.767625] acpi-cpufreq: acpi_cpufreq_verify
> May 26 18:02:28 tarm kernel: [ 3609.767757] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 18:02:28 tarm kernel: [ 3609.767895] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 18:02:28 tarm kernel: [ 3609.768031] acpi-cpufreq: acpi_cpufreq_verify
> May 26 18:02:28 tarm kernel: [ 3609.768158] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
> May 26 18:02:28 tarm kernel: [ 3609.768294] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
> May 26 18:02:28 tarm kernel: [ 3609.768429] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
> May 26 18:02:28 tarm kernel: [ 3609.768561] cpufreq-core: governor: change or update limits
> May 26 18:02:28 tarm kernel: [ 3609.768689] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 18:04:20 tarm kernel: [ 3721.943273] __ratelimit: 18 messages suppressed
> May 26 18:04:20 tarm kernel: [ 3721.943484] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
> May 26 18:04:20 tarm kernel: [ 3721.943624] cpufreq-core: updating policy for CPU 0
> May 26 18:04:20 tarm kernel: [ 3721.943754] acpi-cpufreq: get_cur_freq_on_cpu (0)
> May 26 18:04:20 tarm kernel: [ 3721.943883] acpi-cpufreq: get_cur_val = 100664850
> May 26 18:04:20 tarm kernel: [ 3721.944010] acpi-cpufreq: cur freq = 800000
> May 26 18:04:20 tarm kernel: [ 3721.944137] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 18:04:20 tarm kernel: [ 3721.944271] acpi-cpufreq: acpi_cpufreq_verify
> May 26 18:04:20 tarm kernel: [ 3721.944418] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 18:04:20 tarm kernel: [ 3721.944556] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 18:04:20 tarm kernel: [ 3721.944691] acpi-cpufreq: acpi_cpufreq_verify
> May 26 18:04:20 tarm kernel: [ 3721.944818] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 18:04:20 tarm kernel: [ 3721.945412] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 18:04:20 tarm kernel: [ 3721.945579] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
> May 26 18:04:20 tarm kernel: [ 3721.945714] cpufreq-core: governor: change or update limits
> May 26 18:04:20 tarm kernel: [ 3721.945845] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 18:04:29 tarm kernel: [ 3730.625003] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:04:29 tarm kernel: [ 3730.625247] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 18:04:29 tarm kernel: [ 3730.625405] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 18:04:29 tarm kernel: [ 3730.625545] freq-table: target is 0 (2000000 kHz, 0)
> May 26 18:04:29 tarm kernel: [ 3730.625674] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 18:04:29 tarm kernel: [ 3730.625808] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 18:04:30 tarm kernel: [ 3732.125001] __ratelimit: 8 messages suppressed
> May 26 18:04:30 tarm kernel: [ 3732.125223] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:05:01 tarm kernel: [ 3762.625004] __ratelimit: 27 messages suppressed
> May 26 18:05:01 tarm kernel: [ 3762.625230] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:05:01 tarm kernel: [ 3762.625371] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 18:05:01 tarm kernel: [ 3762.625503] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 18:05:01 tarm kernel: [ 3762.625639] freq-table: target is 0 (2000000 kHz, 0)
> May 26 18:05:01 tarm kernel: [ 3762.625767] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 18:05:01 tarm kernel: [ 3762.625996] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 18:05:05 tarm kernel: [ 3767.125001] __ratelimit: 34 messages suppressed
> May 26 18:05:05 tarm kernel: [ 3767.125153] cpufreq-core: target for CPU 0: 457142 kHz, relation 0
> May 26 18:05:11 tarm kernel: [ 3772.625012] __ratelimit: 53 messages suppressed
> May 26 18:05:11 tarm kernel: [ 3772.625165] cpufreq-core: target for CPU 0: 685714 kHz, relation 0
> May 26 18:05:14 tarm kernel: [ 3775.942575] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 18:05:14 tarm kernel: [ 3775.942722] acpi-cpufreq: acpi_cpufreq_verify
> May 26 18:05:14 tarm kernel: [ 3775.942782] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 18:05:14 tarm kernel: [ 3775.942844] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 18:05:14 tarm kernel: [ 3775.942905] acpi-cpufreq: acpi_cpufreq_verify
> May 26 18:05:14 tarm kernel: [ 3775.942961] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
> May 26 18:05:14 tarm kernel: [ 3775.943022] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
> May 26 18:05:14 tarm kernel: [ 3775.943082] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
> May 26 18:05:14 tarm kernel: [ 3775.943140] cpufreq-core: governor: change or update limits
> May 26 18:05:14 tarm kernel: [ 3775.943197] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 18:05:14 tarm kernel: [ 3775.943255] cpufreq-core: target for CPU 0: 800000 kHz, relation 1
> May 26 18:05:14 tarm kernel: [ 3775.943311] acpi-cpufreq: acpi_cpufreq_target 800000 (0)
> May 26 18:05:14 tarm kernel: [ 3775.943369] freq-table: request for target 800000 kHz (relation: 1) for cpu 0
> May 26 18:05:14 tarm kernel: [ 3775.943428] freq-table: target is 4 (800000 kHz, 4)
> May 26 18:05:14 tarm kernel: [ 3775.943485] cpufreq-core: notification 0 of frequency transition to 800000 kHz
> May 26 18:05:14 tarm kernel: [ 3775.943546] cpufreq-core: notification 1 of frequency transition to 800000 kHz
> May 26 18:05:14 tarm kernel: [ 3775.943599] cpufreq-core: scaling loops_per_jiffy to 3195449 for frequency 800000 kHz
> May 26 18:07:00 tarm kernel: [ 3881.874163] __ratelimit: 44 messages suppressed
> May 26 18:07:00 tarm kernel: [ 3881.874373] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
> May 26 18:07:00 tarm kernel: [ 3881.874512] cpufreq-core: updating policy for CPU 0
> May 26 18:07:00 tarm kernel: [ 3881.874642] acpi-cpufreq: get_cur_freq_on_cpu (0)
> May 26 18:07:00 tarm kernel: [ 3881.874770] acpi-cpufreq: get_cur_val = 100664850
> May 26 18:07:00 tarm kernel: [ 3881.874896] acpi-cpufreq: cur freq = 800000
> May 26 18:07:00 tarm kernel: [ 3881.875047] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 18:07:00 tarm kernel: [ 3881.875182] acpi-cpufreq: acpi_cpufreq_verify
> May 26 18:07:00 tarm kernel: [ 3881.875310] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 18:07:00 tarm kernel: [ 3881.875447] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 18:07:00 tarm kernel: [ 3881.875583] acpi-cpufreq: acpi_cpufreq_verify
> May 26 18:07:00 tarm kernel: [ 3881.875710] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 18:07:00 tarm kernel: [ 3881.875847] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 18:07:00 tarm kernel: [ 3881.875982] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
> May 26 18:07:00 tarm kernel: [ 3881.876115] cpufreq-core: governor: change or update limits
> May 26 18:07:00 tarm kernel: [ 3881.876243] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 18:07:01 tarm kernel: [ 3882.625011] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:07:01 tarm kernel: [ 3882.625258] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 18:07:01 tarm kernel: [ 3882.625399] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 18:07:01 tarm kernel: [ 3882.625541] freq-table: target is 0 (2000000 kHz, 0)
> May 26 18:07:01 tarm kernel: [ 3882.625675] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 18:07:18 tarm kernel: [ 3899.625001] __ratelimit: 16 messages suppressed
> May 26 18:07:18 tarm kernel: [ 3899.625229] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:07:18 tarm kernel: [ 3899.625400] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 18:07:18 tarm kernel: [ 3899.625536] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 18:09:01 tarm kernel: [ 4003.125000] __ratelimit: 11 messages suppressed
> May 26 18:09:01 tarm kernel: [ 4003.125219] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:09:01 tarm kernel: [ 4003.125383] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 18:09:01 tarm kernel: [ 4003.125518] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 18:09:01 tarm kernel: [ 4003.125655] freq-table: target is 0 (2000000 kHz, 0)
> May 26 18:09:01 tarm kernel: [ 4003.125785] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 18:09:01 tarm kernel: [ 4003.125920] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 18:09:01 tarm kernel: [ 4003.125974] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 18:09:02 tarm kernel: [ 4003.624990] cpufreq-core: target for CPU 0: 457142 kHz, relation 0
> May 26 18:09:02 tarm kernel: [ 4003.625144] acpi-cpufreq: acpi_cpufreq_target 457142 (0)
> May 26 18:09:02 tarm kernel: [ 4003.625219] freq-table: request for target 457142 kHz (relation: 0) for cpu 0
> May 26 18:09:13 tarm kernel: [ 4014.625002] __ratelimit: 4 messages suppressed
> May 26 18:09:13 tarm kernel: [ 4014.625228] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:09:13 tarm kernel: [ 4014.625394] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 18:09:47 tarm kernel: [ 4048.625002] __ratelimit: 19 messages suppressed
> May 26 18:09:47 tarm kernel: [ 4048.625223] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:09:47 tarm kernel: [ 4048.625389] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 18:09:47 tarm kernel: [ 4048.625524] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 18:09:47 tarm kernel: [ 4048.625661] freq-table: target is 0 (2000000 kHz, 0)
> May 26 18:09:47 tarm kernel: [ 4048.625791] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 18:09:47 tarm kernel: [ 4048.625926] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 18:09:47 tarm kernel: [ 4048.625990] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 18:09:52 tarm kernel: [ 4053.626605] __ratelimit: 33 messages suppressed
> May 26 18:09:52 tarm kernel: [ 4053.626791] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:09:58 tarm kernel: [ 4060.133318] __ratelimit: 20 messages suppressed
> May 26 18:09:58 tarm kernel: [ 4060.133559] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:10:01 tarm kernel: [ 4063.125021] __ratelimit: 13 messages suppressed
> May 26 18:10:01 tarm kernel: [ 4063.125262] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:10:06 tarm kernel: [ 4068.125460] __ratelimit: 13 messages suppressed
> May 26 18:10:06 tarm kernel: [ 4068.125699] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:10:12 tarm kernel: [ 4074.125037] __ratelimit: 20 messages suppressed
> May 26 18:10:12 tarm kernel: [ 4074.125255] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:10:18 tarm kernel: [ 4079.626878] __ratelimit: 13 messages suppressed
> May 26 18:10:18 tarm kernel: [ 4079.627098] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:10:24 tarm kernel: [ 4086.133059] __ratelimit: 20 messages suppressed
> May 26 18:10:24 tarm kernel: [ 4086.133274] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:10:27 tarm kernel: [ 4088.624999] __ratelimit: 11 messages suppressed
> May 26 18:10:27 tarm kernel: [ 4088.625151] cpufreq-core: target for CPU 0: 1142857 kHz, relation 0
> May 26 18:10:32 tarm kernel: [ 4093.625002] __ratelimit: 27 messages suppressed
> May 26 18:10:32 tarm kernel: [ 4093.625227] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:10:34 tarm kernel: [ 4095.755272] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 18:10:34 tarm kernel: [ 4095.755508] acpi-cpufreq: acpi_cpufreq_verify
> May 26 18:10:34 tarm kernel: [ 4095.755642] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 18:10:34 tarm kernel: [ 4095.755780] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 18:10:34 tarm kernel: [ 4095.755916] acpi-cpufreq: acpi_cpufreq_verify
> May 26 18:10:34 tarm kernel: [ 4095.756042] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
> May 26 18:10:34 tarm kernel: [ 4095.756179] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
> May 26 18:10:34 tarm kernel: [ 4095.756314] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
> May 26 18:10:34 tarm kernel: [ 4095.756447] cpufreq-core: governor: change or update limits
> May 26 18:10:34 tarm kernel: [ 4095.756575] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 18:12:34 tarm kernel: [ 4216.175207] __ratelimit: 39 messages suppressed
> May 26 18:12:34 tarm kernel: [ 4216.175414] cpufreq-core: CPU 0: _PPC is 0 - frequency not limited
> May 26 18:12:34 tarm kernel: [ 4216.175553] cpufreq-core: updating policy for CPU 0
> May 26 18:12:34 tarm kernel: [ 4216.175682] acpi-cpufreq: get_cur_freq_on_cpu (0)
> May 26 18:12:34 tarm kernel: [ 4216.175809] acpi-cpufreq: get_cur_val = 100664850
> May 26 18:12:34 tarm kernel: [ 4216.175936] acpi-cpufreq: cur freq = 800000
> May 26 18:12:34 tarm kernel: [ 4216.176061] cpufreq-core: setting new policy for CPU 0: 800000 - 2000000 kHz
> May 26 18:12:34 tarm kernel: [ 4216.176194] acpi-cpufreq: acpi_cpufreq_verify
> May 26 18:12:34 tarm kernel: [ 4216.176322] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 18:12:34 tarm kernel: [ 4216.176458] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 18:12:34 tarm kernel: [ 4216.176592] acpi-cpufreq: acpi_cpufreq_verify
> May 26 18:12:34 tarm kernel: [ 4216.176719] freq-table: request for verification of policy (800000 - 2000000 kHz) for cpu 0
> May 26 18:12:34 tarm kernel: [ 4216.176856] freq-table: verification lead to (800000 - 2000000 kHz) for cpu 0
> May 26 18:12:34 tarm kernel: [ 4216.177405] cpufreq-core: new min and max freqs are 800000 - 2000000 kHz
> May 26 18:12:34 tarm kernel: [ 4216.177565] cpufreq-core: governor: change or update limits
> May 26 18:12:34 tarm kernel: [ 4216.177696] cpufreq-core: __cpufreq_governor for CPU 0, event 3
> May 26 18:12:49 tarm kernel: [ 4230.625012] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:12:49 tarm kernel: [ 4230.625277] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 18:12:49 tarm kernel: [ 4230.625421] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 18:12:49 tarm kernel: [ 4230.625563] freq-table: target is 0 (2000000 kHz, 0)
> May 26 18:12:49 tarm kernel: [ 4230.625698] cpufreq-core: notification 0 of frequency transition to 2000000 kHz
> May 26 18:12:49 tarm kernel: [ 4230.625838] cpufreq-core: scaling loops_per_jiffy to 7988623 for frequency 2000000 kHz
> May 26 18:12:49 tarm kernel: [ 4230.625904] cpufreq-core: notification 1 of frequency transition to 2000000 kHz
> May 26 18:13:00 tarm kernel: [ 4241.624998] __ratelimit: 7 messages suppressed
> May 26 18:13:00 tarm kernel: [ 4241.625219] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:13:00 tarm kernel: [ 4241.625384] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> May 26 18:13:00 tarm kernel: [ 4241.625519] freq-table: request for target 2000000 kHz (relation: 1) for cpu 0
> May 26 18:13:14 tarm kernel: [ 4255.624998] __ratelimit: 37 messages suppressed
> May 26 18:13:14 tarm kernel: [ 4255.625224] cpufreq-core: target for CPU 0: 2000000 kHz, relation 1
> May 26 18:13:14 tarm kernel: [ 4255.625391] acpi-cpufreq: acpi_cpufreq_target 2000000 (0)
> 


^ permalink raw reply	[flat|nested] 13+ messages in thread

* [PATCH] Re: cpufreq limits avilable frequencies to 800MHz on git kernel
  2008-05-26 16:23             ` Arkadiusz Miskiewicz
@ 2008-07-17 13:48               ` Thomas Renninger
  2008-07-17 21:40                 ` Andrew Morton
  0 siblings, 1 reply; 13+ messages in thread
From: Thomas Renninger @ 2008-07-17 13:48 UTC (permalink / raw)
  To: Arkadiusz Miskiewicz
  Cc: linux-kernel, cpufreq, Andrew Morton, gnorton, miguel, linux-acpi,
	Dave Jones

Hi,

maybe I found something..., can someone review/test this.

Thanks,

         Thomas

------------
CPUFREQ ACPI: Only call _PPC after cpufreq ACPI init funcs got called already

Ingo Molnar provided a fix to not call _PPC at processor driver initialization 
time.
Git commit #e4233dec749a3519069d9390561b5636a75c7579

But it can still happen that _PPC is called at  processor driver 
initialization time.

This patch should make sure that this is not possible anymore.

Signed-off-by: Thomas Renninger <trenn@suse.de>
---
 arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c |    6 ++++++
 drivers/acpi/processor_perflib.c              |   13 ++++++++++++-
 drivers/cpufreq/cpufreq.c                     |    3 +++
 include/linux/cpufreq.h                       |    1 +
 4 files changed, 22 insertions(+), 1 deletions(-)

diff --git a/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c 
b/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c
index 69288f6..3233fe8 100644
--- a/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c
+++ b/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c
@@ -96,6 +96,12 @@ static int pmi_notifier(struct notifier_block *nb,
 	struct cpufreq_frequency_table *cbe_freqs;
 	u8 node;
 
+	/* Should this really be called for CPUFREQ_ADJUST, CPUFREQ_INCOMPATIBLE
+	 * and CPUFREQ_NOTIFY policy events?)
+	 */
+	if (event == CPUFREQ_START)
+		return 0;
+
 	cbe_freqs = cpufreq_frequency_get_table(policy->cpu);
 	node = cbe_cpu_to_node(policy->cpu);
 
diff --git a/drivers/acpi/processor_perflib.c 
b/drivers/acpi/processor_perflib.c
index b474996..63ccf80 100644
--- a/drivers/acpi/processor_perflib.c
+++ b/drivers/acpi/processor_perflib.c
@@ -72,7 +72,13 @@ MODULE_PARM_DESC(ignore_ppc, "If the frequency of your 
machine gets wrongly" \
 #define PPC_REGISTERED   1
 #define PPC_IN_USE       2
 
-static int acpi_processor_ppc_status = 0;
+/* ignore_ppc:
+ * -1 -> cpufreq low level drivers not initialized -> _PSS, etc. not called 
yet
+ *       ignore _PPC
+ *  0 -> cpufreq low level drivers initialized -> consider _PPC values
+ *  1 -> ignore _PPC totally -> forced by user through boot param
+ */
+static int acpi_processor_ppc_status = -1;
 
 static int acpi_processor_ppc_notifier(struct notifier_block *nb,
 				       unsigned long event, void *data)
@@ -81,6 +87,11 @@ static int acpi_processor_ppc_notifier(struct 
notifier_block *nb,
 	struct acpi_processor *pr;
 	unsigned int ppc = 0;
 
+	if (event == CPUFREQ_START && ignore_ppc <= 0) {
+		ignore_ppc = 0;
+		return 0;
+	}
+
 	if (ignore_ppc)
 		return 0;
 
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 1d41496..0471ef5 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -825,6 +825,9 @@ static int cpufreq_add_dev(struct sys_device *sys_dev)
 	policy->user_policy.min = policy->cpuinfo.min_freq;
 	policy->user_policy.max = policy->cpuinfo.max_freq;
 
+	blocking_notifier_call_chain(&cpufreq_policy_notifier_list,
+				     CPUFREQ_START, policy);
+
 #ifdef CONFIG_SMP
 
 #ifdef CONFIG_HOTPLUG_CPU
diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
index e7e91db..07cb761 100644
--- a/include/linux/cpufreq.h
+++ b/include/linux/cpufreq.h
@@ -109,6 +109,7 @@ struct cpufreq_policy {
 #define CPUFREQ_ADJUST		(0)
 #define CPUFREQ_INCOMPATIBLE	(1)
 #define CPUFREQ_NOTIFY		(2)
+#define CPUFREQ_START		(3)
 
 #define CPUFREQ_SHARED_TYPE_NONE (0) /* None */
 #define CPUFREQ_SHARED_TYPE_HW	 (1) /* HW does needed coordination */
-- 
1.5.4.5


^ permalink raw reply related	[flat|nested] 13+ messages in thread

* Re: [PATCH] Re: cpufreq limits avilable frequencies to 800MHz on git kernel
  2008-07-17 13:48               ` [PATCH] " Thomas Renninger
@ 2008-07-17 21:40                 ` Andrew Morton
  2008-07-18  2:46                   ` Thomas Renninger
  0 siblings, 1 reply; 13+ messages in thread
From: Andrew Morton @ 2008-07-17 21:40 UTC (permalink / raw)
  To: Thomas Renninger
  Cc: arekm, linux-kernel, cpufreq, gnorton, miguel, linux-acpi, davej,
	stable

On Thu, 17 Jul 2008 15:48:02 +0200
Thomas Renninger <trenn@suse.de> wrote:

> Hi,
> 
> maybe I found something..., can someone review/test this.
> 
> Thanks,
> 
>          Thomas
> 
> ------------
> CPUFREQ ACPI: Only call _PPC after cpufreq ACPI init funcs got called already
> 
> Ingo Molnar provided a fix to not call _PPC at processor driver initialization 
> time.
> Git commit #e4233dec749a3519069d9390561b5636a75c7579
> 
> But it can still happen that _PPC is called at  processor driver 
> initialization time.
> 
> This patch should make sure that this is not possible anymore.

There is no actual description of what this fixes, is there?  Do
machines go oops, or what?

How do we proceed from here with this patch?  Who should review it, who
should test it, who should ack it and who should merge it?

e4233dec749a3519069d9390561b5636a75c7579 was in January so this patch
is applicable to 2.6.25.x and to 2.6.26.x.  But is it needed there? 
Insufficient info.

Ho hum.  I queued it, tagged as needed-in-2.6.25.x and 2.6.26.x.  But I
am unsure about that.

Please help to clarify these things.

> Signed-off-by: Thomas Renninger <trenn@suse.de>
> ---
>  arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c |    6 ++++++
>  drivers/acpi/processor_perflib.c              |   13 ++++++++++++-
>  drivers/cpufreq/cpufreq.c                     |    3 +++
>  include/linux/cpufreq.h                       |    1 +
>  4 files changed, 22 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c 
> b/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c
> index 69288f6..3233fe8 100644
> --- a/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c
> +++ b/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c
> @@ -96,6 +96,12 @@ static int pmi_notifier(struct notifier_block *nb,
>  	struct cpufreq_frequency_table *cbe_freqs;
>  	u8 node;
>  
> +	/* Should this really be called for CPUFREQ_ADJUST, CPUFREQ_INCOMPATIBLE
> +	 * and CPUFREQ_NOTIFY policy events?)
> +	 */
> +	if (event == CPUFREQ_START)
> +		return 0;
> +
>  	cbe_freqs = cpufreq_frequency_get_table(policy->cpu);
>  	node = cbe_cpu_to_node(policy->cpu);
>  
> diff --git a/drivers/acpi/processor_perflib.c 
> b/drivers/acpi/processor_perflib.c
> index b474996..63ccf80 100644
> --- a/drivers/acpi/processor_perflib.c
> +++ b/drivers/acpi/processor_perflib.c
> @@ -72,7 +72,13 @@ MODULE_PARM_DESC(ignore_ppc, "If the frequency of your 
> machine gets wrongly" \
>  #define PPC_REGISTERED   1
>  #define PPC_IN_USE       2
>  
> -static int acpi_processor_ppc_status = 0;
> +/* ignore_ppc:
> + * -1 -> cpufreq low level drivers not initialized -> _PSS, etc. not called 
> yet

I am going to start hanging around in dark alleys in the hope of
meeting the person who invented wordwrapping.


Here it is again, fixed:


From: Thomas Renninger <trenn@suse.de>

Ingo Molnar provided a fix to not call _PPC at processor driver
initialization time.  Git commit #e4233dec749a3519069d9390561b5636a75c7579

But it can still happen that _PPC is called at processor driver
initialization time.

This patch should make sure that this is not possible anymore.

Signed-off-by: Thomas Renninger <trenn@suse.de>
Cc: Dave Jones <davej@redhat.com>
Cc: Len Brown <len.brown@intel.com>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Cc: Chandra Seetharaman <sekharan@us.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Arkadiusz Miskiewicz <arekm@maven.pl>
Cc: <gnorton@novell.com>
Cc: <miguel@novell.com>
Cc: <stable@kernel.org>		[2.6.25.x, 2.6.26.x]
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c |    6 ++++++
 drivers/acpi/processor_perflib.c              |   13 ++++++++++++-
 drivers/cpufreq/cpufreq.c                     |    3 +++
 include/linux/cpufreq.h                       |    1 +
 4 files changed, 22 insertions(+), 1 deletion(-)

diff -puN arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c~cpufreq-acpi-only-call-_ppc-after-cpufreq-acpi-init-funcs-got-called-already arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c
--- a/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c~cpufreq-acpi-only-call-_ppc-after-cpufreq-acpi-init-funcs-got-called-already
+++ a/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c
@@ -96,6 +96,12 @@ static int pmi_notifier(struct notifier_
 	struct cpufreq_frequency_table *cbe_freqs;
 	u8 node;
 
+	/* Should this really be called for CPUFREQ_ADJUST, CPUFREQ_INCOMPATIBLE
+	 * and CPUFREQ_NOTIFY policy events?)
+	 */
+	if (event == CPUFREQ_START)
+		return 0;
+
 	cbe_freqs = cpufreq_frequency_get_table(policy->cpu);
 	node = cbe_cpu_to_node(policy->cpu);
 
diff -puN drivers/acpi/processor_perflib.c~cpufreq-acpi-only-call-_ppc-after-cpufreq-acpi-init-funcs-got-called-already drivers/acpi/processor_perflib.c
--- a/drivers/acpi/processor_perflib.c~cpufreq-acpi-only-call-_ppc-after-cpufreq-acpi-init-funcs-got-called-already
+++ a/drivers/acpi/processor_perflib.c
@@ -72,7 +72,13 @@ MODULE_PARM_DESC(ignore_ppc, "If the fre
 #define PPC_REGISTERED   1
 #define PPC_IN_USE       2
 
-static int acpi_processor_ppc_status = 0;
+/* ignore_ppc:
+ * -1 -> cpufreq low level drivers not initialized -> _PSS, etc. not called yet
+ *       ignore _PPC
+ *  0 -> cpufreq low level drivers initialized -> consider _PPC values
+ *  1 -> ignore _PPC totally -> forced by user through boot param
+ */
+static int acpi_processor_ppc_status = -1;
 
 static int acpi_processor_ppc_notifier(struct notifier_block *nb,
 				       unsigned long event, void *data)
@@ -81,6 +87,11 @@ static int acpi_processor_ppc_notifier(s
 	struct acpi_processor *pr;
 	unsigned int ppc = 0;
 
+	if (event == CPUFREQ_START && ignore_ppc <= 0) {
+		ignore_ppc = 0;
+		return 0;
+	}
+
 	if (ignore_ppc)
 		return 0;
 
diff -puN drivers/cpufreq/cpufreq.c~cpufreq-acpi-only-call-_ppc-after-cpufreq-acpi-init-funcs-got-called-already drivers/cpufreq/cpufreq.c
--- a/drivers/cpufreq/cpufreq.c~cpufreq-acpi-only-call-_ppc-after-cpufreq-acpi-init-funcs-got-called-already
+++ a/drivers/cpufreq/cpufreq.c
@@ -825,6 +825,9 @@ static int cpufreq_add_dev(struct sys_de
 	policy->user_policy.min = policy->cpuinfo.min_freq;
 	policy->user_policy.max = policy->cpuinfo.max_freq;
 
+	blocking_notifier_call_chain(&cpufreq_policy_notifier_list,
+				     CPUFREQ_START, policy);
+
 #ifdef CONFIG_SMP
 
 #ifdef CONFIG_HOTPLUG_CPU
diff -puN include/linux/cpufreq.h~cpufreq-acpi-only-call-_ppc-after-cpufreq-acpi-init-funcs-got-called-already include/linux/cpufreq.h
--- a/include/linux/cpufreq.h~cpufreq-acpi-only-call-_ppc-after-cpufreq-acpi-init-funcs-got-called-already
+++ a/include/linux/cpufreq.h
@@ -106,6 +106,7 @@ struct cpufreq_policy {
 #define CPUFREQ_ADJUST		(0)
 #define CPUFREQ_INCOMPATIBLE	(1)
 #define CPUFREQ_NOTIFY		(2)
+#define CPUFREQ_START		(3)
 
 #define CPUFREQ_SHARED_TYPE_NONE (0) /* None */
 #define CPUFREQ_SHARED_TYPE_HW	 (1) /* HW does needed coordination */
_


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [PATCH] Re: cpufreq limits avilable frequencies to 800MHz on git kernel
  2008-07-17 21:40                 ` Andrew Morton
@ 2008-07-18  2:46                   ` Thomas Renninger
  0 siblings, 0 replies; 13+ messages in thread
From: Thomas Renninger @ 2008-07-18  2:46 UTC (permalink / raw)
  To: Andrew Morton
  Cc: arekm, linux-kernel, cpufreq, gnorton, miguel, linux-acpi, davej,
	stable

On Thursday 17 July 2008 11:40:00 pm Andrew Morton wrote:
> On Thu, 17 Jul 2008 15:48:02 +0200
>
> Thomas Renninger <trenn@suse.de> wrote:
> > Hi,
> >
> > maybe I found something..., can someone review/test this.
> >
> > Thanks,
> >
> >          Thomas
> >
> > ------------
> > CPUFREQ ACPI: Only call _PPC after cpufreq ACPI init funcs got called
> > already
> >
> > Ingo Molnar provided a fix to not call _PPC at processor driver
> > initialization time.
> > Git commit #e4233dec749a3519069d9390561b5636a75c7579
> >
> > But it can still happen that _PPC is called at  processor driver
> > initialization time.
> >
> > This patch should make sure that this is not possible anymore.
>
> There is no actual description of what this fixes, is there?  Do
> machines go oops, or what?
ThinkPads get stuck at lowest frequency.
A very nasty bug, reported several times recently.
This seem to show up rarely, not 100% reproducable (after every X boot...).
I do not know whether this one really fixes it. I saw an interesting debug
output on the cpufreq list recently pointing in this direction.
Even if it's not this, only calling _PPC after other initial cpufreq ACPI 
functions like _PDC or _PSS have been called (means cpufreq is really active) 
is a good idea. _PPC functions often have a complex logic. They might depend
on variables initialized in e.g. in _PDC or _PSS...
>
> How do we proceed from here with this patch?  Who should review it, who
> should test it, who should ack it and who should merge it?
I hope that Dave or someone on cpufreq list is having a look at it.
Dave should take it if it's fine.
People seeing this are in CC. After a quick review (patches are short..), I 
can provide an rpm for SUSE people (there is a SUSE and a kernel bug open)
https://bugzilla.novell.com/show_bug.cgi?id=374099

>
> e4233dec749a3519069d9390561b5636a75c7579 was in January so this patch
> is applicable to 2.6.25.x and to 2.6.26.x.  But is it needed there?
Probably should go in through .27 after review/testing.

> Insufficient info.
>
> Ho hum.  I queued it, tagged as needed-in-2.6.25.x and 2.6.26.x.  But I
> am unsure about that.
>
> Please help to clarify these things.
>
> > Signed-off-by: Thomas Renninger <trenn@suse.de>
> > ---
> >  arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c |    6 ++++++
> >  drivers/acpi/processor_perflib.c              |   13 ++++++++++++-
> >  drivers/cpufreq/cpufreq.c                     |    3 +++
> >  include/linux/cpufreq.h                       |    1 +
> >  4 files changed, 22 insertions(+), 1 deletions(-)
> >
> > diff --git a/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c
> > b/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c
> > index 69288f6..3233fe8 100644
> > --- a/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c
> > +++ b/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c
> > @@ -96,6 +96,12 @@ static int pmi_notifier(struct notifier_block *nb,
> >  	struct cpufreq_frequency_table *cbe_freqs;
> >  	u8 node;
> >
> > +	/* Should this really be called for CPUFREQ_ADJUST,
> > CPUFREQ_INCOMPATIBLE +	 * and CPUFREQ_NOTIFY policy events?)
> > +	 */
> > +	if (event == CPUFREQ_START)
> > +		return 0;
> > +
> >  	cbe_freqs = cpufreq_frequency_get_table(policy->cpu);
> >  	node = cbe_cpu_to_node(policy->cpu);
> >
> > diff --git a/drivers/acpi/processor_perflib.c
> > b/drivers/acpi/processor_perflib.c
> > index b474996..63ccf80 100644
> > --- a/drivers/acpi/processor_perflib.c
> > +++ b/drivers/acpi/processor_perflib.c
> > @@ -72,7 +72,13 @@ MODULE_PARM_DESC(ignore_ppc, "If the frequency of your
> > machine gets wrongly" \
> >  #define PPC_REGISTERED   1
> >  #define PPC_IN_USE       2
> >
> > -static int acpi_processor_ppc_status = 0;
> > +/* ignore_ppc:
> > + * -1 -> cpufreq low level drivers not initialized -> _PSS, etc. not
> > called yet
>
> I am going to start hanging around in dark alleys in the hope of
> meeting the person who invented wordwrapping.
Sorry about that, I moved to kmail recently, still do not know how this could 
happen...

         Thomas
>
>
> Here it is again, fixed:
>
>
> From: Thomas Renninger <trenn@suse.de>
>
> Ingo Molnar provided a fix to not call _PPC at processor driver
> initialization time.  Git commit #e4233dec749a3519069d9390561b5636a75c7579
>
> But it can still happen that _PPC is called at processor driver
> initialization time.
>
> This patch should make sure that this is not possible anymore.
>
> Signed-off-by: Thomas Renninger <trenn@suse.de>
> Cc: Dave Jones <davej@redhat.com>
> Cc: Len Brown <len.brown@intel.com>
> Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> Cc: Chandra Seetharaman <sekharan@us.ibm.com>
> Cc: Ingo Molnar <mingo@elte.hu>
> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Cc: Arkadiusz Miskiewicz <arekm@maven.pl>
> Cc: <gnorton@novell.com>
> Cc: <miguel@novell.com>
> Cc: <stable@kernel.org>		[2.6.25.x, 2.6.26.x]
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
>  arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c |    6 ++++++
>  drivers/acpi/processor_perflib.c              |   13 ++++++++++++-
>  drivers/cpufreq/cpufreq.c                     |    3 +++
>  include/linux/cpufreq.h                       |    1 +
>  4 files changed, 22 insertions(+), 1 deletion(-)
>
> diff -puN
> arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c~cpufreq-acpi-only-call-_ppc-a
>fter-cpufreq-acpi-init-funcs-got-called-already
> arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c ---
> a/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c~cpufreq-acpi-only-call-_ppc
>-after-cpufreq-acpi-init-funcs-got-called-already +++
> a/arch/powerpc/platforms/cell/cbe_cpufreq_pmi.c
> @@ -96,6 +96,12 @@ static int pmi_notifier(struct notifier_
>  	struct cpufreq_frequency_table *cbe_freqs;
>  	u8 node;
>
> +	/* Should this really be called for CPUFREQ_ADJUST, CPUFREQ_INCOMPATIBLE
> +	 * and CPUFREQ_NOTIFY policy events?)
> +	 */
> +	if (event == CPUFREQ_START)
> +		return 0;
> +
>  	cbe_freqs = cpufreq_frequency_get_table(policy->cpu);
>  	node = cbe_cpu_to_node(policy->cpu);
>
> diff -puN
> drivers/acpi/processor_perflib.c~cpufreq-acpi-only-call-_ppc-after-cpufreq-
>acpi-init-funcs-got-called-already drivers/acpi/processor_perflib.c ---
> a/drivers/acpi/processor_perflib.c~cpufreq-acpi-only-call-_ppc-after-cpufre
>q-acpi-init-funcs-got-called-already +++ a/drivers/acpi/processor_perflib.c
> @@ -72,7 +72,13 @@ MODULE_PARM_DESC(ignore_ppc, "If the fre
>  #define PPC_REGISTERED   1
>  #define PPC_IN_USE       2
>
> -static int acpi_processor_ppc_status = 0;
> +/* ignore_ppc:
> + * -1 -> cpufreq low level drivers not initialized -> _PSS, etc. not
> called yet + *       ignore _PPC
> + *  0 -> cpufreq low level drivers initialized -> consider _PPC values
> + *  1 -> ignore _PPC totally -> forced by user through boot param
> + */
> +static int acpi_processor_ppc_status = -1;
>
>  static int acpi_processor_ppc_notifier(struct notifier_block *nb,
>  				       unsigned long event, void *data)
> @@ -81,6 +87,11 @@ static int acpi_processor_ppc_notifier(s
>  	struct acpi_processor *pr;
>  	unsigned int ppc = 0;
>
> +	if (event == CPUFREQ_START && ignore_ppc <= 0) {
> +		ignore_ppc = 0;
> +		return 0;
> +	}
> +
>  	if (ignore_ppc)
>  		return 0;
>
> diff -puN
> drivers/cpufreq/cpufreq.c~cpufreq-acpi-only-call-_ppc-after-cpufreq-acpi-in
>it-funcs-got-called-already drivers/cpufreq/cpufreq.c ---
> a/drivers/cpufreq/cpufreq.c~cpufreq-acpi-only-call-_ppc-after-cpufreq-acpi-
>init-funcs-got-called-already +++ a/drivers/cpufreq/cpufreq.c
> @@ -825,6 +825,9 @@ static int cpufreq_add_dev(struct sys_de
>  	policy->user_policy.min = policy->cpuinfo.min_freq;
>  	policy->user_policy.max = policy->cpuinfo.max_freq;
>
> +	blocking_notifier_call_chain(&cpufreq_policy_notifier_list,
> +				     CPUFREQ_START, policy);
> +
>  #ifdef CONFIG_SMP
>
>  #ifdef CONFIG_HOTPLUG_CPU
> diff -puN
> include/linux/cpufreq.h~cpufreq-acpi-only-call-_ppc-after-cpufreq-acpi-init
>-funcs-got-called-already include/linux/cpufreq.h ---
> a/include/linux/cpufreq.h~cpufreq-acpi-only-call-_ppc-after-cpufreq-acpi-in
>it-funcs-got-called-already +++ a/include/linux/cpufreq.h
> @@ -106,6 +106,7 @@ struct cpufreq_policy {
>  #define CPUFREQ_ADJUST		(0)
>  #define CPUFREQ_INCOMPATIBLE	(1)
>  #define CPUFREQ_NOTIFY		(2)
> +#define CPUFREQ_START		(3)
>
>  #define CPUFREQ_SHARED_TYPE_NONE (0) /* None */
>  #define CPUFREQ_SHARED_TYPE_HW	 (1) /* HW does needed coordination */
> _



^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2008-07-18  3:20 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-05-23 17:44 cpufreq limits avilable frequencies to 800MHz on git kernel Arkadiusz Miskiewicz
2008-05-24  1:25 ` Andrew Morton
2008-05-25  9:36   ` Arkadiusz Miskiewicz
2008-05-25 15:03     ` Thomas Renninger
2008-05-26  7:07       ` Arkadiusz Miskiewicz
2008-05-26 11:37         ` Thomas Renninger
2008-05-26 16:15           ` Arkadiusz Miskiewicz
2008-05-26 16:23             ` Arkadiusz Miskiewicz
2008-07-17 13:48               ` [PATCH] " Thomas Renninger
2008-07-17 21:40                 ` Andrew Morton
2008-07-18  2:46                   ` Thomas Renninger
2008-05-27  9:35             ` Thomas Renninger
2008-05-26 12:28         ` Thomas Renninger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox