Re: Lost Ticks

[Scott Lampert <scott@lampert.org>]

I have the exact same problem on a ASUS A8N-SLI Premium board and 
Athlon64 4800+ X2 with every BIOS up to 1008-01.  Running with notsc is 
the only way to get it to work.

As an aside BIOS version 1008-003 is available for this board however 
this one seems to be WAY worse as the board won't even boot.  It gets 
panics before the boot messages unless you boot with noapic and after 
that it gets checksum errors on the RSDP.  I'm afraid to see what the 
next official BIOS version does. :/
   -Scott

Frank van Maarseveen wrote:

> On Sun, Sep 18, 2005 at 09:23:40PM -0700, Marc Perkel wrote:
>  
>
> > Got a dual core Athlon 64 X2 on an Asus board using NVidia chipset and 
> > getting lost ticks. The software clock of course is totally messed up. 
> > I've scanned google for a solution and see others complaining about bad 
> > code in the SMM BIOS. I have the latest bios and whatever they need to 
> > fix - isn't.
> >
> > So - what do I do to make it work?
> >    
>
> See http://bugzilla.kernel.org/show_bug.cgi?id=5105
>
> On the kernel command-line:
>
> x86_64:	try "notsc"
> i386:	try "clock=pit"
>
> "nosmp" works but isn't fun.
>
>  
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/