Re: Failing back to INSANE timesource :) Time stopped today.

[Niclas Gustafsson <niclas.gustafsson@codesense.com>]

Hi again,

I've now been running the system since last week, about 6 days now with
sometimes quite high load, both in regard to CPU usage and network
traffic.
And it seems to be running just fine with the patch from Maciej.

I've got a couple of questions, 

When was this bug introduced? Was it 2.6.1 ( or rather somewhere in
2.5)? Or was it already present in 2.4?

When will this patch be merged into the 2.6-tree?  I don't have to
stress the impact of this problem on IBM servers as they are rendered
quite useless.

Which other IBM models are affected? Can I run 2.6.5 on my 345:s or
335:s?  Do they use the same buggy SMM firmware?




Cheers,

Niclas 


tor 2004-04-15 klockan 18.57 skrev Niclas Gustafsson:
> Hello and thanks,
> 
> I've compiled and deployed a kernel with the patch below.
> I'm about to start some more tests on the machine - it's going to be
> interesting to see how it works out, I'll let you know.
> 
> 
> Cheers,
> 
> Niclas
>   
> 
> tor 2004-04-15 klockan 16.47 skrev Maciej W. Rozycki:
> > On Wed, 14 Apr 2004, Niclas Gustafsson wrote:
> > 
> > > Watching the /proc/interrupts with 10s apart after the "stop".
> > > 
> > > [root@s151 root]# more /proc/interrupts
> > >            CPU0
> > >   0:   66413955  local-APIC-edge  timer
> > [...]
> > > LOC:   67355837
> > > ERR:          0
> > > MIS:          0
> > > [root@s151 root]# more /proc/interrupts
> > >            CPU0
> > >   0:   66413955  local-APIC-edge  timer
> > [...]
> > > LOC:   67379568
> > > ERR:          0
> > > MIS:          0
> > 
> >  This may be because buggy SMM firmware messes with the 8259A (configured
> > for a transparent mode -- yes that rare "local-APIC-edge" mode is tricky
> > ;-) ) insanely.  You've written this is an IBM box previously -- this 
> > would be no surprise.  The following patch should help -- I think it's 
> > already included in the -mm series.