=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 07 April 2004 09:39, Ionel Mugurel Ciobica wrote: > Stie cineva de unde vine "i8253 count too high! resetting.."? > Google nu da decit niste intrebari similare, iar cele care au raspuns > sint de genul, raspunsul este la google... > > Kernelul este 2.4.25, distributia debian sid (testing) pe un sony vaio > FR415S cu uptime de citeva zile. > > Mersi de orice indicatie/directie etc. > > Mugurel > > P.S. Vreau sa stiu daca e ceva grav sau ceva care poate fi ignorat. > > --- > Detalii despre listele noastre de mail: http://www.lug.ro/
am patit si io asa ceva mai demult...am presupus ca e pb. hardware si am=20 inlocuit masina cu una similara si mesagiul a disparut.... iata ce zice un= =20 neamtz despre asta (sper sa se inteleaga...e o traducere) "Each system needs to know a rather accurate time around transmitting IO=20 kidneys. The system time normal is realized wise thereby that the hardware = in=20 certain distances releases an interrupt, that is interrupt 0. If you have u= n=20 ter X e.g. xosview openly, then sees you there also that the small lamp for= =20 IRQ 0 shines quasi continuously. The in such a way activated interrupt=20 routine takes over a counting of the time, the system time in Ticks is=20 measured since the start of the system and chert in the variable of jiffies= =20 gespei. That corresponds to IIRC 10 milli of second intervals on usual=20 systems. On the whole procedure now very much is based, because your system= =20 uses timers etc. and also the Scheduling needs an exact date. The message,= =20 which you received, comes finally from /arch/i386/kernel/time.c. It concern= s=20 the timer handling of the Kernels with the i386 architecture, the selection= =20 of the RTC with boats, timer interrupt, etc.. It has to do also with APIC.= =20 The Kernel discovered a problem (the variable COUNT became larger than a=20 vorgegebe ner value LATCH) and over the Kernel function printk a warning is= =20 spent. It seems to give thus on this system a problem with the time handlin= g,=20 what could have smaller and larger effects. It knows on the fact hindeu ten= =20 that there are problems with your BIOS (it can be to BIOS because of one=20 buggy), or also with APIC etc.. That is very difficult to say and you over it probably in the inter net non= e=20 all to exact and reliable data to find... Possibly an BIOS update, perhaps= =20 also an on of those helps Kernel or other APIC code etc.. Or other hard=20 commodity: -) It concerns with the board not coincidentally a Asus board?" =2D --=20 =A0 ing.Adrian Costescu =A0 Administrator Retea Infoplus, Ramnicu Valcea http://www.infoplus.com.ro PGP: http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xE4506831 =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAc7tGPynneORQaDERAlBrAJ47mtYKSvvD2Y6tQG82mNlN90ZZYgCbBEeV tjvd9UvVDEI4NRdbWCGmCpk=3D =3DciZA =2D----END PGP SIGNATURE----- --- Detalii despre listele noastre de mail: http://www.lug.ro/
