Hi,
Ever since I went to the new 2.6.25-rcX, I encountered lots of random
system freezes after about 2 or 3 hours of uptime... but until now,
I couldn't _catch_ them, since the system
(AMD Athlon 4200+ X2 (Manchester) / nforce 4 SLI / x86_64) went
straight into oblivion (nothing on the serial console or anywhere else,
heck I couldn't even hit reset, It didn't POST anymore)
So. take a look at stuck_task... that's best backtrace I could get...
(I have other logs too. (Task-list / Lockdep / ... ) but it's too much
and I hope the _logs_ are already enough.
BTW: I noticed that the clock seems to jump forward and backwards.
Is this because the CPU-Cores aren't syncronized? (And why are they
out of sync?)
(And yes, 2.6.24.4 is fine... even hpet works there without any
rtc: lost 14 interrupts)
cat /proc/interrupts
CPU0 CPU1
0: 51 0 XT-PIC-XT timer
1: 43 22170 IO-APIC-edge i8042
4: 0 1 IO-APIC-edge
6: 0 5 IO-APIC-edge floppy
7: 1 0 IO-APIC-edge parport0
8: 0 199 IO-APIC-edge rtc
9: 0 0 IO-APIC-fasteoi acpi
14: 0 0 IO-APIC-edge pata_amd
15: 0 0 IO-APIC-edge pata_amd
16: 82 51311 IO-APIC-fasteoi firewire_ohci, EMU10K1
17: 0 50 IO-APIC-fasteoi firewire_ohci, eth1
18: 12 4862 IO-APIC-fasteoi nvidia
20: 421 304857 IO-APIC-fasteoi eth0
21: 57 33025 IO-APIC-fasteoi ohci_hcd:usb1
22: 185 12275 IO-APIC-fasteoi sata_nv
23: 276 83270 IO-APIC-fasteoi sata_nv, ehci_hcd:usb2
NMI: 0 0 Non-maskable interrupts
LOC: 339847 307599 Local timer interrupts
RES: 126709 38837 Rescheduling interrupts
CAL: 605 1054 function call interrupts
TLB: 1513 3813 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
SPU: 0 0 Spurious interrupts
ERR: 1
[Added some CCs]
On Sunday, 30 of March 2008, Chr wrote:
> Hi,
>
> Ever since I went to the new 2.6.25-rcX, I encountered lots of random
> system freezes after about 2 or 3 hours of uptime... but until now,
> I couldn't _catch_ them, since the system
> (AMD Athlon 4200+ X2 (Manchester) / nforce 4 SLI / x86_64) went
> straight into oblivion (nothing on the serial console or anywhere else,
> heck I couldn't even hit reset, It didn't POST anymore)
>
> So. take a look at stuck_task... that's best backtrace I could get...
> (I have other logs too. (Task-list / Lockdep / ... ) but it's too much
> and I hope the _logs_ are already enough.
>
> BTW: I noticed that the clock seems to jump forward and backwards.
> Is this because the CPU-Cores aren't syncronized? (And why are they
> out of sync?)
>
> (And yes, 2.6.24.4 is fine... even hpet works there without any
> rtc: lost 14 interrupts)
>
> cat /proc/interrupts
> CPU0 CPU1
> 0: 51 0 XT-PIC-XT timer
> 1: 43 22170 IO-APIC-edge i8042
> 4: 0 1 IO-APIC-edge
> 6: 0 5 IO-APIC-edge floppy
> 7: 1 0 IO-APIC-edge parport0
> 8: 0 199 IO-APIC-edge rtc
> 9: 0 0 IO-APIC-fasteoi acpi
> 14: 0 0 IO-APIC-edge pata_amd
> 15: 0 0 IO-APIC-edge pata_amd
> 16: 82 51311 IO-APIC-fasteoi firewire_ohci, EMU10K1
> 17: 0 50 IO-APIC-fasteoi firewire_ohci, eth1
> 18: 12 4862 IO-APIC-fasteoi nvidia
> 20: 421 304857 IO-APIC-fasteoi eth0
> 21: 57 33025 IO-APIC-fasteoi ohci_hcd:usb1
> 22: 185 12275 IO-APIC-fasteoi sata_nv
> 23: 276 83270 IO-APIC-fasteoi sata_nv, ehci_hcd:usb2
> NMI: 0 0 Non-maskable interrupts
> LOC: 339847 307599 Local timer interrupts
> RES: 126709 38837 Rescheduling interrupts
> CAL: 605 1054 function call interrupts
> TLB: 1513 3813 TLB shootdowns
> TRM: 0 0 Thermal event interrupts
> THR: 0 0 Threshold APIC interrupts
> SPU: 0 0 Spurious interrupts
> ERR: 1
>
On Sun, 30 Mar 2008, Rafael J. Wysocki wrote:
> > So. take a look at stuck_task... that's best backtrace I could get...
> > (I have other logs too. (Task-list / Lockdep / ... ) but it's too much
> > and I hope the _logs_ are already enough.
> >
> > BTW: I noticed that the clock seems to jump forward and backwards.
> > Is this because the CPU-Cores aren't syncronized? (And why are they
> > out of sync?)
The cores of those AMD beasts are never in sync. That's a chip feature :)
Can you please provide the output of:
/sys/devices/system/clocksource/clocksource0/current_clocksource
for both 2.6.24 and 2.6.25-rc7
Thanks,
tglx
On Sunday 30 March 2008 21:59:51 Thomas Gleixner wrote:
> On Sun, 30 Mar 2008, Rafael J. Wysocki wrote:
> > > So. take a look at stuck_task... that's best backtrace I could get...
> > > (I have other logs too. (Task-list / Lockdep / ... ) but it's too much
> > > and I hope the _logs_ are already enough.
> > >
> > > BTW: I noticed that the clock seems to jump forward and backwards.
> > > Is this because the CPU-Cores aren't syncronized? (And why are they
> > > out of sync?)
>
> The cores of those AMD beasts are never in sync. That's a chip feature :)
>
> Can you please provide the output of:
> /sys/devices/system/clocksource/clocksource0/current_clocksource
>
> for both 2.6.24 and 2.6.25-rc7
it's "hpet" (in both cases...)
Regards,
Chr
On Sun, 30 Mar 2008, Chr wrote:
> On Sunday 30 March 2008 21:59:51 Thomas Gleixner wrote:
> > On Sun, 30 Mar 2008, Rafael J. Wysocki wrote:
> > > > So. take a look at stuck_task... that's best backtrace I could get...
> > > > (I have other logs too. (Task-list / Lockdep / ... ) but it's too much
> > > > and I hope the _logs_ are already enough.
> > > >
> > > > BTW: I noticed that the clock seems to jump forward and backwards.
> > > > Is this because the CPU-Cores aren't syncronized? (And why are they
> > > > out of sync?)
> >
> > The cores of those AMD beasts are never in sync. That's a chip feature :)
> >
> > Can you please provide the output of:
> > /sys/devices/system/clocksource/clocksource0/current_clocksource
> >
> > for both 2.6.24 and 2.6.25-rc7
> it's "hpet" (in both cases...)
Hmm. That should be stable. Which clock is jumping back and forth ?
The one in the logs or the system clock ?
Thanks,
tglx
On Sunday 30 March 2008 22:37:29 Thomas Gleixner wrote:
> On Sun, 30 Mar 2008, Chr wrote:
> > On Sunday 30 March 2008 21:59:51 Thomas Gleixner wrote:
> > > On Sun, 30 Mar 2008, Rafael J. Wysocki wrote:
> > > > > So. take a look at stuck_task... that's best backtrace I could
> > > > > get... (I have other logs too. (Task-list / Lockdep / ... ) but
> > > > > it's too much and I hope the _logs_ are already enough.
> > >
> > > The cores of those AMD beasts are never in sync. That's a chip feature
> > > :)
> > >
> > > Can you please provide the output of:
> > > /sys/devices/system/clocksource/clocksource0/current_clocksource
> > >
> > > for both 2.6.24 and 2.6.25-rc7
> >
> > it's "hpet" (in both cases...)
>
> Hmm. That should be stable. Which clock is jumping back and forth ?
> The one in the logs or the system clock ?
The one in the logs... (but it's because of the TSC, right?)
Regards,
Chr
On Sun, 30 Mar 2008, Chr wrote:
> > > it's "hpet" (in both cases...)
> >
> > Hmm. That should be stable. Which clock is jumping back and forth ?
> > The one in the logs or the system clock ?
> The one in the logs... (but it's because of the TSC, right?)
Yes. I thought this was fixed already in Linus tree, but I might be
wrong as usual.
Anyway, that's not the real problem; I read your original post in
meantime :)
> Ever since I went to the new 2.6.25-rcX ...
Did this problem start with 25-rc1 ? What is the latest version you
tried ?
> [ 5215.101875] [<ffffffff80217d8f>] __smp_call_function_mask+0x90/0xc5
> [ 5215.108493] [<ffffffff8029b433>] invalidate_bh_lru+0x0/0x42
> [ 5215.114422] [<ffffffff8029b433>] invalidate_bh_lru+0x0/0x42
> [ 5215.120348] [<ffffffff8029b433>] invalidate_bh_lru+0x0/0x42
> [ 5215.126276] [<ffffffff80217e0d>] smp_call_function_mask+0x49/0x61
> [ 5215.132723] [<ffffffff8029b433>] invalidate_bh_lru+0x0/0x42
> [ 5215.138649] [<ffffffff802339a3>] on_each_cpu+0x10/0x2c
> [ 5215.144135] [<ffffffff8029fb4b>] kill_bdev+0x1e/0x33
> [ 5215.149456] [<ffffffff802a01da>] __blkdev_put+0x4f/0x128
> [ 5215.155124] [<ffffffff8027dd93>] __fput+0xa1/0x164
> [ 5215.160272] [<ffffffff8027b67d>] filp_close+0x5d/0x65
> [ 5215.165679] [<ffffffff80231072>] put_files_struct+0x66/0xc4
> [ 5215.171607] [<ffffffff802323ea>] do_exit+0x245/0x64c
> [ 5215.176925] [<ffffffff80238b94>] __dequeue_signal+0xff/0x159
> [ 5215.182941] [<ffffffff80232867>] do_group_exit+0x76/0x93
> [ 5215.188606] [<ffffffff8023a0fd>] get_signal_to_deliver+0x2b9/0x2e5
> [ 5215.195141] [<ffffffff8020a466>] do_notify_resume+0xaf/0x7e0
> [ 5215.201155] [<ffffffff80291414>] mntput_no_expire+0x1f/0x86
> [ 5215.201155] [<ffffffff80291414>] mntput_no_expire+0x1f/0x86
You mentioned that you have tons of other logs. Can you please
upload those to some place? If you don't have a possiblity, please
contact me private and I'll provide you one.
Thanks,
tglx
On Sunday 30 March 2008 23:36:40 Thomas Gleixner wrote:
> On Sun, 30 Mar 2008, Chr wrote:
> > > > it's "hpet" (in both cases...)
> > >
> > > Hmm. That should be stable. Which clock is jumping back and forth ?
> > > The one in the logs or the system clock ?
> >
> > The one in the logs... (but it's because of the TSC, right?)
>
> Yes. I thought this was fixed already in Linus tree, but I might be
> wrong as usual.
>
> Anyway, that's not the real problem; I read your original post in
> meantime :)
>
> > Ever since I went to the new 2.6.25-rcX ...
>
> Did this problem start with 25-rc1 ? What is the latest version you
> tried ?
I had other problems with 25-rc1 as well.. but this one is now gone with
the dm-crypto update. I'll try rc1 tomorrow...
>
> > [ 5215.101875] [<ffffffff80217d8f>] __smp_call_function_mask+0x90/0xc5
> > [ 5215.108493] [<ffffffff8029b433>] invalidate_bh_lru+0x0/0x42
> > [ 5215.114422] [<ffffffff8029b433>] invalidate_bh_lru+0x0/0x42
> > [ 5215.120348] [<ffffffff8029b433>] invalidate_bh_lru+0x0/0x42
> > [ 5215.126276] [<ffffffff80217e0d>] smp_call_function_mask+0x49/0x61
> > [ 5215.132723] [<ffffffff8029b433>] invalidate_bh_lru+0x0/0x42
> > [ 5215.138649] [<ffffffff802339a3>] on_each_cpu+0x10/0x2c
> > [ 5215.144135] [<ffffffff8029fb4b>] kill_bdev+0x1e/0x33
> > [ 5215.149456] [<ffffffff802a01da>] __blkdev_put+0x4f/0x128
> > [ 5215.155124] [<ffffffff8027dd93>] __fput+0xa1/0x164
> > [ 5215.160272] [<ffffffff8027b67d>] filp_close+0x5d/0x65
> > [ 5215.165679] [<ffffffff80231072>] put_files_struct+0x66/0xc4
> > [ 5215.171607] [<ffffffff802323ea>] do_exit+0x245/0x64c
> > [ 5215.176925] [<ffffffff80238b94>] __dequeue_signal+0xff/0x159
> > [ 5215.182941] [<ffffffff80232867>] do_group_exit+0x76/0x93
> > [ 5215.188606] [<ffffffff8023a0fd>] get_signal_to_deliver+0x2b9/0x2e5
> > [ 5215.195141] [<ffffffff8020a466>] do_notify_resume+0xaf/0x7e0
> > [ 5215.201155] [<ffffffff80291414>] mntput_no_expire+0x1f/0x86
> > [ 5215.201155] [<ffffffff80291414>] mntput_no_expire+0x1f/0x86
>
> You mentioned that you have tons of other logs. Can you please
> upload those to some place? If you don't have a possiblity, please
> contact me private and I'll provide you one.
>
http://www.file-upload.net/download-758265/logs.tar.bz2.html
and hit Download. ;-)
(BTW, the you can ignore some logs like freeze7, ... I tried
nolapic, but that doesn't play well with SATA?!)
Regards,
Chr
Chr <[email protected]> writes:
> Ever since I went to the new 2.6.25-rcX, I encountered lots of random
> system freezes after about 2 or 3 hours of uptime... but until now,
> I couldn't _catch_ them, since the system
> (AMD Athlon 4200+ X2 (Manchester) / nforce 4 SLI / x86_64) went
> straight into oblivion (nothing on the serial console or anywhere else,
> heck I couldn't even hit reset, It didn't POST anymore)
Not POSTing would point to some kind of hardware problem. Normally
the kernel shouldn't be able to cause that.
I would recommend you double check if the problem is really not
there with an older kernel by going back there and testing.
-Andi
On Monday 31 March 2008 09:10:34 Andi Kleen wrote:
> Chr <[email protected]> writes:
> > Ever since I went to the new 2.6.25-rcX, I encountered lots of random
> > system freezes after about 2 or 3 hours of uptime... but until now,
> > I couldn't _catch_ them, since the system
> > (AMD Athlon 4200+ X2 (Manchester) / nforce 4 SLI / x86_64) went
> > straight into oblivion (nothing on the serial console or anywhere else,
> > heck I couldn't even hit reset, It didn't POST anymore)
>
> Not POSTing would point to some kind of hardware problem. Normally
> the kernel shouldn't be able to cause that.
Normally yes.. but this is the first time that this ever happend!
(And my system has been stable so far (more than a year now, in fact more like
2 years)... even with nvidia & madwifi drivers!).
>
> I would recommend you double check if the problem is really not
> there with an older kernel by going back there and testing.
Well... older kernels won't freeze that way..
I can hit reset whenever I want and it still POSTs.
But, I'll try... maybe I get another change.
(BTW, if it happends again, is there anything special, that
could help to find the real bugs?)
>
> -Andi
Regards,
Chr.
On Sun, Mar 30, 2008 at 11:36:40PM +0200, Thomas Gleixner wrote:
> On Sun, 30 Mar 2008, Chr wrote:
>...
> You mentioned that you have tons of other logs. Can you please
> upload those to some place? If you don't have a possiblity, please
> contact me private and I'll provide you one.
The logical place would be
http://bugzilla.kernel.org/show_bug.cgi?id=10369
And linux-kernel has a size limit of 400 kB, so everything that is
smaller (at least when compressed) could simply be sent by email.
> Thanks,
>
> tglx
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
On Monday 31 March 2008 14:56:53 Adrian Bunk wrote:
> On Sun, Mar 30, 2008 at 11:36:40PM +0200, Thomas Gleixner wrote:
> > On Sun, 30 Mar 2008, Chr wrote:
> >...
> > You mentioned that you have tons of other logs. Can you please
> > upload those to some place? If you don't have a possiblity, please
> > contact me private and I'll provide you one.
>
> The logical place would be
> http://bugzilla.kernel.org/show_bug.cgi?id=10369
Done! The log is about 200KBs (~ 2MBs untarbz2ed)
Regards
Chr
On Sunday 30 March 2008 23:36:40 Thomas Gleixner wrote:
> On Sun, 30 Mar 2008, Chr wrote:
>
> You mentioned that you have tons of other logs. Can you please
> upload those to some place? If you don't have a possiblity, please
> contact me private and I'll provide you one.
>
Ahhm it happend again (well, actually it's the fifth time today, but this time
I _hopefully_ found something)
I made a new log: (check out bugzilla)
http://bugzilla.kernel.org/show_bug.cgi?id=10369
(direct link)
http://bugzilla.kernel.org/attachment.cgi?id=15542
so, this log was made from a _working_ machine over the serial
console... I put some _real_ "date" marks here and there...
to explain a bit, how the time STALLS... (well, it seems like
it goes a bit backward and forward and backwards again... it loops?!
whatever..!??!?!!)
just take a look at the jiffies (grep for them... it takes "minutes"
until jiffies+1 comes)
Maybe there's a "signed" problem somewhere in the timekeeping
code? Or does 2.6.25-rcX have a general problem with NTP-daemons
like chrony?
Regards,
Chr.
On Tuesday, 1 of April 2008, Chr wrote:
> On Sunday 30 March 2008 23:36:40 Thomas Gleixner wrote:
> > On Sun, 30 Mar 2008, Chr wrote:
> >
> > You mentioned that you have tons of other logs. Can you please
> > upload those to some place? If you don't have a possiblity, please
> > contact me private and I'll provide you one.
> >
> Ahhm it happend again (well, actually it's the fifth time today, but this time
> I _hopefully_ found something)
>
> I made a new log: (check out bugzilla)
> http://bugzilla.kernel.org/show_bug.cgi?id=10369
>
> (direct link)
> http://bugzilla.kernel.org/attachment.cgi?id=15542
>
> so, this log was made from a _working_ machine over the serial
> console... I put some _real_ "date" marks here and there...
> to explain a bit, how the time STALLS... (well, it seems like
> it goes a bit backward and forward and backwards again... it loops?!
> whatever..!??!?!!)
>
> just take a look at the jiffies (grep for them... it takes "minutes"
> until jiffies+1 comes)
>
> Maybe there's a "signed" problem somewhere in the timekeeping
> code? Or does 2.6.25-rcX have a general problem with NTP-daemons
> like chrony?
Have you posted the .config already?
Rafael
On Tuesday 01 April 2008 01:14:24 Rafael J. Wysocki wrote:
> On Tuesday, 1 of April 2008, Chr wrote:
>
> Have you posted the .config already?
Done!
BTW:
[ 5074.308547] .jiffies : 4296102117
[ 5074.308547] .jiffies : 4296102117
[ 5105.659185] .idle_jiffies : 4296102113
[ 5105.659185] .last_jiffies : 4296102117
[ 5105.659185] .next_jiffies : 4296102118
[ 5105.659185] jiffies: 4296102117
[ 5105.659185] .idle_jiffies : 4296102114
[ 5105.659185] .last_jiffies : 4296102113
[ 5105.659185] .next_jiffies : 4296102116
[ 5105.659185] jiffies: 4296102117
[ 5044.543918] .jiffies : 4296102117
[ 5044.640998] .jiffies : 4296102117
[ 4979.215327] .idle_jiffies : 4296102113
[ 4979.229471] .last_jiffies : 4296102117
[ 4979.231334] .next_jiffies : 4296102118
[ 4979.235415] jiffies: 4296102117
[ 4979.298216] .idle_jiffies : 4296102114
[ 4979.312360] .last_jiffies : 4296102113
[ 4979.314223] .next_jiffies : 4296102116
[ 4979.318303] jiffies: 4296102117
[ 5040.749212] .idle_jiffies : 4296102113
[ 5040.763356] .last_jiffies : 4296102117
[ 5040.765219] .next_jiffies : 4296102118
[ 5040.769299] jiffies: 4296102117
[ 5040.832119] .idle_jiffies : 4296102114
[ 5040.846264] .last_jiffies : 4296102113
[ 5040.848127] .next_jiffies : 4296102116
[ 5040.852206] jiffies: 4296102117
-OUCH - going backwards?
[ 4956.514210] .idle_jiffies : 4296102113
[ 4956.528354] .last_jiffies : 4296102117
[ 4956.530217] .next_jiffies : 4296102118
[ 4956.534298] jiffies: 4296102117
[ 4956.597024] .idle_jiffies : 4296102114
[ 4956.611168] .last_jiffies : 4296102113
[ 4956.613031] .next_jiffies : 4296102116
[ 4956.617111] jiffies: 4296102117
[ 5063.325509] .idle_jiffies : 4296102113
[ 5063.339653] .last_jiffies : 4296102117
[ 5063.341517] .next_jiffies : 4296102118
[ 5063.345597] jiffies: 4296102117
[ 5063.408519] .idle_jiffies : 4296102114
[ 5063.422664] .last_jiffies : 4296102113
[ 5063.424526] .next_jiffies : 4296102116
[ 5063.428607] jiffies: 4296102117
[ 5116.186763] .idle_jiffies : 4296102113
[ 5116.186764] .last_jiffies : 4296102117
[ 5116.186764] .next_jiffies : 4296102118
[ 5116.186764] jiffies: 4296102117
[ 5116.186764] .idle_jiffies : 4296102114
[ 5116.186764] .last_jiffies : 4296102113
[ 5116.186764] .next_jiffies : 4296102116
[ 5116.186764] jiffies: 4296102117
[ 5012.429020] .idle_jiffies : 4296102113
[ 5012.443164] .last_jiffies : 4296102117
[ 5012.445027] .next_jiffies : 4296102118
[ 5012.449107] jiffies: 4296102117
[ 5012.511908] .idle_jiffies : 4296102114
[ 5012.526052] .last_jiffies : 4296102113
[ 5012.527915] .next_jiffies : 4296102116
[ 5012.531995] jiffies: 4296102117
[ 5048.890792] .idle_jiffies : 4296102113
[ 5048.904936] .last_jiffies : 4296102117
[ 5048.906800] .next_jiffies : 4296102118
[ 5048.910880] jiffies: 4296102117
[ 5048.973842] .idle_jiffies : 4296102114
[ 5048.987987] .last_jiffies : 4296102113
[ 5048.989850] .next_jiffies : 4296102116
[ 5048.993930] jiffies: 4296102117
[ 5069.025049] .idle_jiffies : 4296102113
[ 5069.039194] .last_jiffies : 4296102117
[ 5069.041056] .next_jiffies : 4296102118
[ 5069.045136] jiffies: 4296102117
[ 5069.107874] .idle_jiffies : 4296102114
[ 5069.122019] .last_jiffies : 4296102113
[ 5069.123881] .next_jiffies : 4296102116
[ 5069.127962] jiffies: 4296102117
[ 5095.978692] .idle_jiffies : 4296102113
[ 5095.992836] .last_jiffies : 4296102117
[ 5095.994699] .next_jiffies : 4296102118
[ 5095.998780] jiffies: 4296102117
[ 5096.061623] .idle_jiffies : 4296102114
[ 5096.075768] .last_jiffies : 4296102113
[ 5096.077631] .next_jiffies : 4296102116
[ 5096.081711] jiffies: 4296102117
[ 5108.211902] .idle_jiffies : 4296102113
[ 5108.211902] .last_jiffies : 4296102117
[ 5108.211902] .next_jiffies : 4296102118
[ 5108.211902] jiffies: 4296102117
[ 5108.211903] .idle_jiffies : 4296102114
[ 5108.211903] .last_jiffies : 4296102113
[ 5108.211903] .next_jiffies : 4296102116
[ 5108.211903] jiffies: 4296102117
[ 5108.211903] .idle_jiffies : 4296102113
[ 5108.211903] .last_jiffies : 4296102117
[ 5108.211903] .next_jiffies : 4296102118
[ 5108.211903] jiffies: 4296102117
[ 5108.211903] .idle_jiffies : 4296102114
[ 5108.211903] .last_jiffies : 4296102113
[ 5108.211903] .next_jiffies : 4296102116
[ 5108.211903] jiffies: 4296102117
[ 5108.211903] .idle_jiffies : 4296102113
[ 5108.211903] .last_jiffies : 4296102117
[ 5108.211903] .next_jiffies : 4296102118
[ 5108.211903] jiffies: 4296102117
[ 5108.211903] .idle_jiffies : 4296102114
[ 5108.211903] .last_jiffies : 4296102113
[ 5108.211903] .next_jiffies : 4296102116
[ 5108.211903] jiffies: 4296102117
[ 5108.211904] .idle_jiffies : 4296102113
[ 5108.211904] .last_jiffies : 4296102117
[ 5108.211904] .next_jiffies : 4296102118
[ 5108.211904] jiffies: 4296102117
[ 5108.211904] .idle_jiffies : 4296102114
[ 5108.211904] .last_jiffies : 4296102113
[ 5108.211904] .next_jiffies : 4296102116
[ 5108.211904] jiffies: 4296102117
[ 5108.211904] .idle_jiffies : 4296102113
[ 5108.211904] .last_jiffies : 4296102117
[ 5108.211904] .next_jiffies : 4296102118
[ 5108.211904] jiffies: 4296102117
[ 5108.211904] .idle_jiffies : 4296102114
[ 5108.211904] .last_jiffies : 4296102113
[ 5108.211904] .next_jiffies : 4296102116
[ 5108.211904] jiffies: 4296102117
[ 5108.211905] .idle_jiffies : 4296102113
[ 5108.211905] .last_jiffies : 4296102117
[ 5108.211905] .next_jiffies : 4296102118
[ 5108.211905] jiffies: 4296102117
[ 5108.211905] .idle_jiffies : 4296102114
[ 5108.211905] .last_jiffies : 4296102113
[ 5108.211905] .next_jiffies : 4296102116
[ 5108.211905] jiffies: 4296102117
[ 5108.211905] .idle_jiffies : 4296102113
[ 5108.211905] .last_jiffies : 4296102117
[ 5108.211905] .next_jiffies : 4296102118
[ 5108.211905] jiffies: 4296102117
[ 5108.211905] .idle_jiffies : 4296102114
[ 5108.211905] .last_jiffies : 4296102113
[ 5108.211905] .next_jiffies : 4296102116
[ 5108.211905] jiffies: 4296102117
[ 5108.211905] .idle_jiffies : 4296102113
[ 5108.211905] .last_jiffies : 4296102117
[ 5108.211905] .next_jiffies : 4296102118
[ 5108.211905] jiffies: 4296102117
[ 5108.211906] .idle_jiffies : 4296102114
[ 5108.211906] .last_jiffies : 4296102113
[ 5108.211906] .next_jiffies : 4296102116
[ 5108.211906] jiffies: 4296102117
[ 5108.211906] .idle_jiffies : 4296102113
[ 5108.211906] .last_jiffies : 4296102117
[ 5108.211906] .next_jiffies : 4296102118
[ 5108.211906] jiffies: 4296102117
[ 5108.211906] .idle_jiffies : 4296102114
[ 5108.211906] .last_jiffies : 4296102113
[ 5108.211906] .next_jiffies : 4296102116
[ 5108.211906] jiffies: 4296102117
[ 5108.211906] .idle_jiffies : 4296102113
[ 5108.211906] .last_jiffies : 4296102117
[ 5108.211906] .next_jiffies : 4296102118
[ 5108.211906] jiffies: 4296102117
[ 5108.211906] .idle_jiffies : 4296102114
[ 5108.211906] .last_jiffies : 4296102113
[ 5108.211906] .next_jiffies : 4296102116
[ 5108.211906] jiffies: 4296102117
[ 5108.211924] .jiffies : 4296102117
[ 5108.211925] .jiffies : 4296102117
Regards,
Chr