On Mon, 2008-05-26 at 18:15 +0200, Arkadiusz Miskiewicz wrote:
quoted text
> 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.

quoted text
> 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

quoted text
> complete log from boot:
(stripped)
quoted text
> 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