Bug 21022
| Summary: | Kernel 2.6.36 starts and works VERY slow, with long delays | ||
|---|---|---|---|
| Product: | Other | Reporter: | Ruslan (b7.10110111) |
| Component: | Other | Assignee: | other_other |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | akpm, alan |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.36 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Attachments: |
dmesg log for 2.6.36
Log from 2.6.34 Config file after make menuconfig |
||
Created attachment 34612 [details]
Log from 2.6.34
Created attachment 34622 [details]
Config file after make menuconfig
Your 2.6.36 build has + kmemcheck: Limiting number of CPUs to 1. + kmemcheck: Initialized + Brought up 1 CPUs + Total of 1 processors activated (3733.22 BogoMIPS). Can you try disabling kmemcheck? Without kmemcheck it works OK. Changing kmemcheck on boot state from "one-shot" to "disabled" removes the delays still preserving "Limiting number of CPUs to 1". So... is this normal for kmemcheck, so that this bug would be invalid, or is it still a real bug? |
Created attachment 34602 [details] dmesg log for 2.6.36 First what i noticed after upgrade from 2.6.34 to 2.6.36 is very long delays between some startup messages. I used the same .config file from 2.6.34, just made 'make menuconfig'; Esc-Esc, Enter to update the configuration. I attach the dmesg logs for 2.6.36 and 2.6.34 for comparison. Note the timestamps.