Unexpected lock during "Calibrating delay loop" and failure to compile without "HighRes"

Unexpected lock during "Calibrating delay loop" and failure to compile without "HighRes"

Post by Isabelle, Francoi » Tue, 04 Feb 2003 18:10:07



Compilation with high-res turned off:

add #define do_gettimeoffset() do_slow_gettimeoffset()  at line 283 in
arch/i386/kernel/time.c

their was a
"static unsigned long (*do_gettimeoffset)(void) = do_slow_gettimeoffset;"
instead of the #define found for other configuration

at line 875

#ifndef do_gettimeoffset
                        do_gettimeoffset = do_fast_gettimeoffset;
#endif

would be compiled even when the CONFIG_X86_TSC is off.

> -----Original Message-----

> Sent: 3 fvrier, 2003 10:07
> To: Isabelle, Francois;


> Subject: RE: Errata : Unexpected lock during "Calibrating delay loop"
> and failure to co mpile without "HighRes"

> Please Read:
>  to build withOUT High-Res, the kernel won't build

> > -----Original Message-----

> > Sent: 3 fvrier, 2003 09:47


> > Subject: Unexpected lock during "Calibrating delay loop" and
> > failure to
> > co mpile without "HighRes"

> > Hi,
> >     I'm trying to integrate some tools on a 486-powered cpu
> > board, I don't
> > really need "High Resolution Timers", but one of the tools
> > would really make
> > good use of the POSIX API you implemented. I've patch kernel
> > 2.4.20 with the
> > latest 2.4.20-1.0 hrtimers.

> > Here comes the trouble.

> > - Trying to build with High-Res, the kernel won't build

> > time.c: In function `time_init':
> > time.c:873: `do_fast_gettimeoffset' undeclared (first use in
> > this function)
> > time.c:873: (Each undeclared identifier is reported only once
> > time.c:873: for each function it appears in.)
> > make[1]: *** [time.o] Error 1
> > make[1]: Leaving directory `/usr/src/linux-2.4.20/arch/i386/kernel'
> > make: *** [_dir_arch/i386/kernel] Error 2

> > seems like it should try to link "do_slow_gettimeoffset"
> > instead since 486
> > does not handle TSC, (I'll have to check that..)

> > - Trying to boot with "PIT-based" high-res support, the
> > kernel lock during
> > calibration "Calibrating delay loop".
> >       Same occurs with IOAPIC and TSC ...

> > If you have any hint, I'll be glad to hear it.

> > Thanks

> > Frank

> > -------------------------------------------------------
> > This SF.NET email is sponsored by:
> > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> > http://www.vasoftware.com
> > to unsubscribe:
> http://lists.sourceforge.net/lists/listinfo/high-res-timers-discourse
> High-res-timers-discourse mailing list

> https://lists.sourceforge.net/lists/listinfo/high-res-timers-discourse

> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> to unsubscribe:
> http://lists.sourceforge.net/lists/listinfo/high-res-timers-discourse
> High-res-timers-discourse mailing list

> https://lists.sourceforge.net/lists/listinfo/high-res-timers-discourse

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
 
 
 

Unexpected lock during "Calibrating delay loop" and failure to compile without "HighRes"

Post by george anzinge » Wed, 05 Feb 2003 00:40:06



> add #define do_gettimeoffset() do_slow_gettimeoffset()  at line 283 in
> arch/i386/kernel/time.c

No, I think not.  That messes up other logic.  This is what I think it
should be (note the below is the idea, a correct patch is attached):

                         *      and just enable this for the next intel chips ?
                         */
                        x86_udelay_tsc = 1;
-#ifndef do_gettimeoffset
+#if ! defined( do_gettimeoffset) && defined(CONFIG_X86_TSC)
                        do_gettimeoffset = do_fast_gettimeoffset;
  #endif
                          /*

Thanks for the bug report.

> their was a
> "static unsigned long (*do_gettimeoffset)(void) = do_slow_gettimeoffset;"
> instead of the #define found for other configuration

> at line 875

> #ifndef do_gettimeoffset
>                    do_gettimeoffset = do_fast_gettimeoffset;
> #endif

> would be compiled even when the CONFIG_X86_TSC is off.

>>-----Original Message-----

>>Sent: 3 fvrier, 2003 10:07
>>To: Isabelle, Francois;


>>Subject: RE: Errata : Unexpected lock during "Calibrating delay loop"
>>and failure to co mpile without "HighRes"

>>Please Read:
>> to build withOUT High-Res, the kernel won't build

>>>-----Original Message-----

>>>Sent: 3 fvrier, 2003 09:47


>>>Subject: Unexpected lock during "Calibrating delay loop" and
>>>failure to
>>>co mpile without "HighRes"

>>>Hi,
>>>    I'm trying to integrate some tools on a 486-powered cpu
>>>board, I don't
>>>really need "High Resolution Timers", but one of the tools
>>>would really make
>>>good use of the POSIX API you implemented. I've patch kernel
>>>2.4.20 with the
>>>latest 2.4.20-1.0 hrtimers.

>>>Here comes the trouble.

>>>- Trying to build with High-Res, the kernel won't build

>>>time.c: In function `time_init':
>>>time.c:873: `do_fast_gettimeoffset' undeclared (first use in
>>>this function)
>>>time.c:873: (Each undeclared identifier is reported only once
>>>time.c:873: for each function it appears in.)
>>>make[1]: *** [time.o] Error 1
>>>make[1]: Leaving directory `/usr/src/linux-2.4.20/arch/i386/kernel'
>>>make: *** [_dir_arch/i386/kernel] Error 2

>>>seems like it should try to link "do_slow_gettimeoffset"
>>>instead since 486
>>>does not handle TSC, (I'll have to check that..)

>>>- Trying to boot with "PIT-based" high-res support, the
>>>kernel lock during
>>>calibration "Calibrating delay loop".
>>>    Same occurs with IOAPIC and TSC ...

>>>If you have any hint, I'll be glad to hear it.

>>>Thanks

>>>Frank

>>>-------------------------------------------------------
>>>This SF.NET email is sponsored by:
>>>SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
>>>http://www.vasoftware.com
>>>to unsubscribe:

>>http://lists.sourceforge.net/lists/listinfo/high-res-timers-discourse
>>High-res-timers-discourse mailing list

>>https://lists.sourceforge.net/lists/listinfo/high-res-timers-discourse

>>-------------------------------------------------------
>>This SF.NET email is sponsored by:
>>SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
>>http://www.vasoftware.com
>>to unsubscribe:
>>http://lists.sourceforge.net/lists/listinfo/high-res-timers-discourse
>>High-res-timers-discourse mailing list

>>https://lists.sourceforge.net/lists/listinfo/high-res-timers-discourse

> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld http://www.vasoftware.com
> to unsubscribe: http://lists.sourceforge.net/lists/listinfo/high-res-timers-discourse
> High-res-timers-discourse mailing list

> https://lists.sourceforge.net/lists/listinfo/high-res-timers-discourse

--

High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml

[ hrtimers-2.4.20-fix2.patch < 1K ]
--- linux-2.4.20-hrt/arch/i386/kernel/time.c~   2003-01-08 22:51:06.000000000 -0800

                         *      and just enable this for the next intel chips ?
                         */
                        x86_udelay_tsc = 1;
-#ifndef do_gettimeoffset
+#if ! defined( do_gettimeoffset) && defined(CONFIG_X86_TSC)
                        do_gettimeoffset = do_fast_gettimeoffset;
 #endif
                         /*

 
 
 

1. High-Res-Timers: Unexpected "lock" during "Calibrating delay loop "

Hi,
        we are having an unexpected problem with the HR patch( regardless of
the patch you sent which compiled just fine ). The board uses a 486DX cpu,
so there is no support for TSC nor ACPI, the only thing we have is the PIT.

Without highres, the kernel boots properly, with highres enabled, the kernel
passes "time_init()" put it hangs in "calibrate_loop() , ( I though it hung
for real, but it get passed the loop after a while) "

Seems like the tick is VERY SLOW..

The PIT has been tested on this board, and without HR, the kernel boots fine
... if you have any hints, they would be welcome.

The keyboard detection routine timeouts so the system is quiet unuseable and
I can't get the calibration results yet.

Frank

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. argument list too long

3. Errata : Unexpected lock during "Calibrating delay loop" and failure to co mpile without "HighRes"

4. /var/lib

5. Unexpected lock during "Calibrating delay loop" and failure to co mpile without "HighRes"

6. help with smtp and imap explaination

7. GETSERVBYNAME()????????????????????"""""""""""""

8. Internet Connection Sharing question

9. Hangs/freezes during "Calibrating Delay Loop...."

10. """"""""My SoundBlast 16 pnp isn't up yet""""""""""""

11. 1.1.62 + IDE-2.01: long delay on reboot before "Calibrating delay loop"

12. "umsdos" vs "vfat" vs "looped ext2"

13. Using "if" in "ksh" to change "for loop" values....