Hi,

Sorry for the late reply I was away on Easter holidays.

I'm attaching both the dmesg output (dmesg.265-IBM305_2) and the
unpacked /proc/config.gz (config.gz.IBM_265_2)

However the last lines from dmesg:
---
> set_rtc_mmss: can't update from 52 to 0
> > set_rtc_mmss: can't update from 53 to 1
> > set_rtc_mmss: can't update from 54 to 2
> > set_rtc_mmss: can't update from 55 to 3
> > set_rtc_mmss: can't update from 56 to 4
> > set_rtc_mmss: can't update from 57 to 5
> > set_rtc_mmss: can't update from 58 to 6
> > Losing too many ticks!
> > TSC cannot be used as a timesource.  <4>Possible reasons for this are:
> >   You're running with Speedstep,
> >   You don't have DMA enabled for your hard disk (see hdparm),
> >   Incorrect TSC synchronization on an SMP system (see dmesg).
---

Were not synched to disk before I rebooted the system.


I've compiled a new kernel that seems to be working better although I
need to run some more tests to be sure.


Regards,

Niclas Gustafsson

 
fre 2004-04-09 klockan 00.58 skrev john stultz:
> On Thu, 2004-04-08 at 02:21, Niclas Gustafsson wrote:
> > Hi,
> > 
> > I'm running Linux 2.6.5  on a IBM xSeries 305 with a Intel P4 2.8Ghz.
> > 
> > And something is very very wrong, I'm getting the following last
> > messages in dmesg:
> > 
> > ------
> > set_rtc_mmss: can't update from 52 to 0
> > set_rtc_mmss: can't update from 53 to 1
> > set_rtc_mmss: can't update from 54 to 2
> > set_rtc_mmss: can't update from 55 to 3
> > set_rtc_mmss: can't update from 56 to 4
> > set_rtc_mmss: can't update from 57 to 5
> > set_rtc_mmss: can't update from 58 to 6
> > Losing too many ticks!
> > TSC cannot be used as a timesource.  <4>Possible reasons for this are:
> >   You're running with Speedstep,
> >   You don't have DMA enabled for your hard disk (see hdparm),
> >   Incorrect TSC synchronization on an SMP system (see dmesg).
> > ------
> > 
> > The problem seesm to be related to heavy loads.
> > I experienced a similar problem yesterday. The machine completly hung
> > after that and i had to cut the power to reboot it. Now however it is
> > responsive and I can log on to it through ssh.
> > 
> > Problem is that the clock stopped completly! - I've never seen anything
> > like this before. 
> > 
> > Local time is about 11 am here and a time gives me:
> > 
> > [root@s151 root]# date
> > Thu Apr  8 03:51:21 CEST 2004
> > 
> > ...10 s later, using my wristwatch, not sleep 10 ;)
> > 
> > [root@s151 root]# date
> > Thu Apr  8 03:51:21 CEST 2004
> > 
> > 
> > Any ideas anyone, I'd really like to know why it is behaving this way.
> 
> Huh. Very very odd.  
> 
> Does /proc/interrupts show timer ticks increasing? 
> Does setting the date change anything? 
> 
> Would you mind sending me your complete dmesg? 
> 
> I'll look into reproducing the error here if you can give me a better
> description of what triggers it and how frequently you see the problem.
> 
> thanks
> -john
> 
> 
>