Bug 5636
| Summary: | Totally bogus BogoMips when calibrate_delay_direct fails; results in sluggish system | ||
|---|---|---|---|
| Product: | Other | Reporter: | mjacek (jmisiure) |
| Component: | Other | Assignee: | other_other |
| Status: | CLOSED PATCH_ALREADY_AVAILABLE | ||
| Severity: | low | CC: | bunk, john.stultz |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.14.2 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
Interesting, but with 2.6.14.3 kernel the calibrate_delay() routine does not fail. Perhaps the main bug was somewhere else, BEFORE the calibration..... Has this issue been seen w/ 2.6.15 or newer kernels? I've never seen it again after move to newer kernels. (today I use 2.6.14.4) Haven't tried 2.6.15 yet. Please reopen this bug if you'll observe it with kernel 2.6.17. |
Most recent kernel where this bug did not occur: (last tried: 2.6.12) Distribution: PLD Linux Hardware Environment: Asus M2400E laptop Software Environment: kernel initialization, (kernel/calibrate.c) Problem Description: calibrate_delay_direct fails ("failed to get a good estimate for loops_per_jiffy"), then the BogoMIPS number goes ten times larger than should be. I wish I had a laptop with 27000 BogoMIPS...... The lpj=xxxx kernel parameter setting works OK, but: 1. Doesnt it mean some hidden problem in the new routine? 2. It would be much better to fall to the old routine after the failure. 3. There should be the possibility to switch off the new routine in config. Steps to reproduce: Probably by running the new kernel on a platforms with "long platform interrupts"