Re: calcru went backwards on 7 stable
Thanks in 2008/7/24 Dimitar Vasilev <[EMAIL PROTECTED]> > > > 2008/7/24 Kris Kennaway <[EMAIL PROTECTED]>: > > Dimitar Vasilev wrote: >> >>> The "calcru went backwards" message can have two causes: 1) Your time counter really went backwards and is too broken to use. 2) Something caused clock interrupts to be delayed for extremely long periods of time. This happens if you break to DDB for example. It can also happen if there are kernel bugs, maybe in a driver etc. Try to enable additional debugging (WITNESS, INVARIANTS, etc; see the developers handbook) and see where it gets you. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to " [EMAIL PROTECTED]" Thanks Kris, >>> >>> Last time I tried to set the date there was a problem with the year - I >>> could not set the date beyond 2007 >>> >> >> That doesn't sound like a FreeBSD bug. >> > Hello, I did kgdb print_cpu ticks today. It says (kgdb) print cpu_ticks $1 = (cpu_tick_f *) 0x8077d340 This means that kernel is using tsc discipline actually imho. Could someone confirm this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: calcru went backwards on 7 stable
Dimitar Vasilev wrote: The "calcru went backwards" message can have two causes: 1) Your time counter really went backwards and is too broken to use. 2) Something caused clock interrupts to be delayed for extremely long periods of time. This happens if you break to DDB for example. It can also happen if there are kernel bugs, maybe in a driver etc. Try to enable additional debugging (WITNESS, INVARIANTS, etc; see the developers handbook) and see where it gets you. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to " [EMAIL PROTECTED]" Thanks Kris, Last time I tried to set the date there was a problem with the year - I could not set the date beyond 2007 That doesn't sound like a FreeBSD bug. Also HZ were 2000 instead of 1000, but at that time machine was a uniprocessor one. HZ=1000 by default, so are you saying you set it to 2000? Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: calcru went backwards on 7 stable
2008/7/24 Kris Kennaway <[EMAIL PROTECTED]>: > Dimitar Vasilev wrote: > >> The "calcru went backwards" message can have two causes: >>> >>> 1) Your time counter really went backwards and is too broken to use. >>> >>> 2) Something caused clock interrupts to be delayed for extremely long >>> periods of time. This happens if you break to DDB for example. It can >>> also >>> happen if there are kernel bugs, maybe in a driver etc. Try to enable >>> additional debugging (WITNESS, INVARIANTS, etc; see the developers >>> handbook) >>> and see where it gets you. >>> >>> Kris >>> >>> ___ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to " >>> [EMAIL PROTECTED]" >>> >>> Thanks Kris, >> >> Last time I tried to set the date there was a problem with the year - I >> could not set the date beyond 2007 >> > > That doesn't sound like a FreeBSD bug. > > Also HZ were 2000 instead of 1000, but at that time machine was a >> uniprocessor one. >> > > HZ=1000 by default, so are you saying you set it to 2000? > > Kris > Thanks Kris, I appreciate your help. I'm aware that bios bugs are not related to FreeBSD. Machine we're speaking about is one of the official mirrors for FreeBSD in Bulgaria. System was running fine with HZ=2000 from 2005 to 2007 with a single CPU and 5-stable series. After I moved back to Sofia we moved it to 7-stable, 1000 HZ by default and added a second CPU. I'm trying to isolate the problem with the help of all subscribers - I don't have frequent access to the server room which leads to delayed troubleshooting. Will change CMOS battery and update bios as a start. Thanks for helping. Best regards, Dimitar Vassilev ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: calcru went backwards on 7 stable
> > The "calcru went backwards" message can have two causes: > > 1) Your time counter really went backwards and is too broken to use. > > 2) Something caused clock interrupts to be delayed for extremely long > periods of time. This happens if you break to DDB for example. It can also > happen if there are kernel bugs, maybe in a driver etc. Try to enable > additional debugging (WITNESS, INVARIANTS, etc; see the developers handbook) > and see where it gets you. > > Kris > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > [EMAIL PROTECTED]" > Thanks Kris, Last time I tried to set the date there was a problem with the year - I could not set the date beyond 2007 Also HZ were 2000 instead of 1000, but at that time machine was a uniprocessor one. Best regards, Dimitar Vassilev ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: calcru went backwards on 7 stable
Michael Powell wrote: Dimitar Vasilev wrote: Hi, I'm having calcru went backwards issues on a machine with the following config: MB: MSI K8D Master-F 2xOpteron 242 2.2Ghz BIOS - от 2005-та 7-stable areca 1120 8 disks HDD temperature 28-29 for 1st five, 38-39 for the last 3. bios is as of 2005 - ami bios or something like this. Initial time counter acpi-fast. changed it to i8245, but without success. Problem is that I get 10-15 messages, after which machine freezes - and it's not possible to log in via ssh. then after some time it looses ping also and it has to be reset. smart says disks are ok. Could someone help on this? Thanks in advance!. Only two things I can think of are to try the TSC timer as well, but sort of doubt that will change anything. The other is if there is any CPU frequency speed reduction when idle (PowerNow!) settings in the BIOS try disabling that functionality. IIRC some of these had the ability for different cores/cpus to run at slightly different frequencies to reduce power consumption and this can really confuse the OS. The "calcru went backwards" message can have two causes: 1) Your time counter really went backwards and is too broken to use. 2) Something caused clock interrupts to be delayed for extremely long periods of time. This happens if you break to DDB for example. It can also happen if there are kernel bugs, maybe in a driver etc. Try to enable additional debugging (WITNESS, INVARIANTS, etc; see the developers handbook) and see where it gets you. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: calcru went backwards on 7 stable
Dimitar Vasilev wrote: > Hi, > I'm having calcru went backwards issues on a machine with the following > config: > > MB: MSI K8D Master-F > 2xOpteron 242 2.2Ghz > BIOS - от 2005-та > 7-stable > areca 1120 > 8 disks > HDD temperature 28-29 for 1st five, 38-39 for the last 3. > > bios is as of 2005 - ami bios or something like this. > > Initial time counter acpi-fast. changed it to i8245, but without success. > Problem is that I get 10-15 messages, after which machine freezes - and > it's not possible to log in via ssh. > then after some time it looses ping also and it has to be reset. > > smart says disks are ok. > > Could someone help on this? > > Thanks in advance!. Only two things I can think of are to try the TSC timer as well, but sort of doubt that will change anything. The other is if there is any CPU frequency speed reduction when idle (PowerNow!) settings in the BIOS try disabling that functionality. IIRC some of these had the ability for different cores/cpus to run at slightly different frequencies to reduce power consumption and this can really confuse the OS. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
calcru went backwards on 7 stable
Hi, I'm having calcru went backwards issues on a machine with the following config: MB: MSI K8D Master-F 2xOpteron 242 2.2Ghz BIOS - от 2005-та 7-stable areca 1120 8 disks HDD temperature 28-29 for 1st five, 38-39 for the last 3. bios is as of 2005 - ami bios or something like this. Initial time counter acpi-fast. changed it to i8245, but without success. Problem is that I get 10-15 messages, after which machine freezes - and it's not possible to log in via ssh. then after some time it looses ping also and it has to be reset. smart says disks are ok. Could someone help on this? Thanks in advance!. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
