> 
> Hello Vincent,
> 
> As it seems the 5s net gain is during the early phase of the 
> boot process, could you please post longer dmesgs, to let us 
> know where the gain occurs ?

Hi Paul,

Here is an sdiff between the two dmesg:
[    0.000000] Linux version 2.6.18.8-amd64-envcan-003 (root@ | [
0.000000] Linux version 2.6.18.8-rsdl-0.30-amd64-envcan
[    0.000000] time.c: Detected 2210.220 MHz processor.       | [
0.000000] time.c: Detected 2210.215 MHz processor.
[   37.396210] Console: colour dummy device 80x25             | [
32.320335] Console: colour dummy device 80x25
[   37.397484] Dentry cache hash table entries: 262144 (order | [
32.321611] Dentry cache hash table entries: 262144 (order
[   37.399120] Inode-cache hash table entries: 131072 (order: | [
32.323318] Inode-cache hash table entries: 131072 (order:
[   37.399633] Checking aperture...                           | [
32.323869] Checking aperture...
[   37.399641] CPU 0: aperture @ 8400000000 size 32 MB        | [
32.323877] CPU 0: aperture @ 8400000000 size 32 MB
[   37.399645] Aperture too small (32 MB)                     | [
32.323881] Aperture too small (32 MB)
[   37.404577] No AGP bridge found                            | [
32.328813] No AGP bridge found
[   37.421192] Memory: 2054704k/2096000k available (1934k ker | [
32.345833] Memory: 2054704k/2096000k available (1935k ker
[   37.498110] Calibrating delay using timer specific routine | [
32.422230] Calibrating delay using timer specific routine

Here is a bit more detailed info:

Vanilla Version:
[    0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
[    0.000000] Built 1 zonelists.  Total pages: 515848
[    0.000000] Kernel command line: root=LABEL=DebianEtch_64 ro
vga=0x305
[    0.000000] Initializing CPU#0
[    0.000000] PID hash table entries: 4096 (order: 12, 32768 bytes)
[    0.000000] Disabling vsyscall due to use of PM timer
[    0.000000] time.c: Using 3.579545 MHz WALL PM GTOD PM timer.
[    0.000000] time.c: Detected 2210.220 MHz processor.
[   37.396210] Console: colour dummy device 80x25
[   37.397484] Dentry cache hash table entries: 262144 (order: 9,
2097152 bytes)
[   37.399120] Inode-cache hash table entries: 131072 (order: 8, 1048576
bytes)
[   37.399633] Checking aperture...
[   37.399641] CPU 0: aperture @ 8400000000 size 32 MB
[   37.399645] Aperture too small (32 MB)
[   37.404577] No AGP bridge found
[   37.421192] Memory: 2054704k/2096000k available (1934k kernel code,
40908k reserved, 868k data, 188k init)


RSDL Version:
[    0.000000] Initializing CPU#0
[    0.000000] PID hash table entries: 4096 (order: 12, 32768 bytes)
[    0.000000] Disabling vsyscall due to use of PM timer
[    0.000000] time.c: Using 3.579545 MHz WALL PM GTOD PM timer.
[    0.000000] time.c: Detected 2210.215 MHz processor.
[   32.320335] Console: colour dummy device 80x25
[   32.321611] Dentry cache hash table entries: 262144 (order: 9,
2097152 bytes)
[   32.323318] Inode-cache hash table entries: 131072 (order: 8, 1048576
bytes)
[   32.323869] Checking aperture...
[   32.323877] CPU 0: aperture @ 8400000000 size 32 MB
[   32.323881] Aperture too small (32 MB)
[   32.328813] No AGP bridge found

There seems to be a some sort of lag happening adter the CPU
detection... It might simply be the call to vga=0x305 which takes less
or more time depending of the kernel?  I have attached a gzip full
dmesg.

> 
> Regards,
> Paul
> 

- vin 

Attachment: dmesg.2.6.18.8-rsdl-0.30-amd64-envcan.gz
Description: dmesg.2.6.18.8-rsdl-0.30-amd64-envcan.gz

Reply via email to