RE: PROBLEM: Oops when doing disk heavy disk I/O

[Sergio Monteiro Basto]

On Wed, 2006-10-25 at 10:21 +1000, Michael wrote:
>  
> > -----Original Message-----
> > From: Sergio Monteiro Basto [mailto:sergio@xxxxxxxxxxxxxxxxxx] 
> > Sent: Wednesday, 25 October 2006 3:27 AM
> > 
> > Hi, 
> > please boot with "report_lost_ticks" like
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=115545986619977&w=2
> > and see if you have 
> > time.c: Lost n timer tick(s)!
> > 
> > and 
> > cat /sys/devices/system/clocksource/clocksource0/
> > 
> > cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> > 
> > 
> 
> Hi,
> 
> Yep, seems to be losing some ticks -- I'm not sure what that means, but is
> it bad? :-)
> 

well I don't know for sure , but after this initials Lost Timer tick ,
it appears more after a few time of uptime ? 


> [ root @ barbossa : ~ ] # dmesg | grep tick
> Command line: root=/dev/md1 ro report_lost_ticks
> Kernel command line: root=/dev/md1 ro report_lost_ticks
> time.c: Lost 1 timer tick(s)! rip release_console_sem+0x196/0x20c)
> time.c: Lost 12 timer tick(s)! rip setup_boot_APIC_clock+0x11f/0x121)
> time.c: Lost 2 timer tick(s)! rip __do_softirq+0x4a/0xc4)
> 

> 
> Also, for the clocksource:
> [ root @ barbossa : ~ ] # cat
> /sys/devices/system/clocksource/clocksource0/available_clocksource
> jiffies
> 
> [ root @ barbossa : ~ ] # cat
> /sys/devices/system/clocksource/clocksource0/current_clocksource
> jiffies
> 
> 
> Thanks for your help.
> 
> Cheers,
> Michael
> 

-- 
Sérgio M.B.

Attachment: smime.p7s
Description: S/MIME cryptographic signature