Regressions in the last kernels
During preparation and own testing for my distro; installation on computers for neighbours, by reclamations by users, I learned about the following problems of 2.6.26-rcX :
1) When compiling for i486, one cannot select/configurate more memory than 4 GB, menuconfig don't show items with higher values. My own computer/server has 8 GB, but when I compile the kernel with 4 GB and i486 then 'free' shows only 3.2 GB (no shared grafics, the grafic card has its own memory) ...
2) On some laptops, especially IBM/Centrinho laptops, 2.6.26-rcX dont find the CD devices, nor that from what was booted. This problem is independend on the edd problem. It wasn't present at the 2.6.25-rc9 kernel or earliers (i didn't test it on 2.6.25 defin.), but it's present at 2.6.26-rc4 and -rc5 (-rc6 i didnt test). Just because of this problem it wasnt possible to install something on this kind laptop, and I had yesterday to make a new Install .iso with an older kernel as alternative: ftp://ftp.uni-siegen.de/pub/sys-linux/SYS_Linux-0.23-rc3.iso
Exactly happens the following: BIOS finds correctly the CD drive for booting and boots, but later Linux dont find it (only older kernels), on some laptops. I insert in the drive the Install DVD: It boots, loads the kernel and the initrd correctly. This is the small install / rescue system. However, although everything present in /dev, inclusive the device nodes /dev/hdb etc (but empty), Linux don't find /dev/hdb f.ex. for mount it or calling with hdparm or anyhow else. Thus, also the system installation fails, because the packages or lzma-zipped system cannot be readed from the same CD what was used for boot and what BIOS found/managed ... With exactly the same system/initrd, configuration etc everything the same but just change to an older kernel, everything works normally; thus this is a kernel regression
*** At this point, I want to suggest, that Linux should have a special devide node /dev/<anyname> on what one can mount ANYWAY and ANYHOW that boot device what BIOS used and understood to boot from, even when the hardware detection of Linux fails completely. When bios managed it to read that device and to load the kernel and the initrd , then Linux should manage it too, to read from the same CD other files. This is necessary in order to perform the installation anyway, even when Linux dont find hardware or the boot CD. ***
Werner Landgraf
werner#guyane.dyn-o-saur.com
[email protected]
Linux SYS
0.23-rc3
Quoted 8 lines · werner
During preparation and own testing for my distro; installation on computers for neighbours, by reclamations by users, I learned about the following problems of 2.6.26-rcX :
1) When compiling for i486, one cannot select/configurate more memory than 4 GB, menuconfig don't show items with higher values. My own computer/server has 8 GB, but when I compile the kernel with 4 GB and i486 then 'free' shows only 3.2 GB (no shared grafics, the grafic card has its own memory) ...
I've just created the Bugzilla entry at:
http://bugzilla.kernel.org/show_bug.cgi?id=10912
for this problem. Please add yourself to the CC list in there and please file a separate bug for the CD issue.
Quoted 9 lines
2) On some laptops, especially IBM/Centrinho laptops, 2.6.26-rcX dont find
the CD devices, nor that from what was booted. This problem is independend
on the edd problem. It wasn't present at the 2.6.25-rc9 kernel or earliers (i didn't test it on 2.6.25 defin.), but it's present at 2.6.26-rc4 and -rc5 (-rc6 i didnt test). Just because of this problem it wasnt possible to install something on this kind laptop, and I had yesterday to make a new Install .iso with an older kernel as alternative:
ftp://ftp.uni-siegen.de/pub/sys-linux/SYS_Linux-0.23-rc3.iso
Quoted 12 lines
Exactly happens the following: BIOS finds correctly the CD drive for
booting and boots, but later Linux dont find it (only older kernels), on some
laptops. I insert in the drive the Install DVD: It boots, loads
the kernel and the initrd correctly. This is the small install / rescue
system. However, although everything present in /dev, inclusive the device nodes/dev/hdbetc (but empty), Linux don't find/dev/hdbf.ex. for mount it or calling with hdparm or anyhow else. Thus, also the system installation fails, because the packages or lzma-zipped system cannot be readed from the
same CD what was used for boot and what BIOS found/managed ... With
exactly the same system/initrd, configuration etc everything the same but just change to an older kernel, everything works normally; thus this is a kernel regression
This looks like it might have been fixed already. Which -rc kernels have you tried so far?
Quoted 7 lines
*** At this point, I want to suggest, that Linux should have a special devide node /dev/<anyname> on what one can mount ANYWAY and ANYHOW that boot device what BIOS used and understood to boot from, even when the hardware detection
of Linux fails completely. When bios managed it to read that device and to
load the kernel and the initrd , then Linux should manage it too, to read from the same CD other files. This is necessary in order to perform the installation anyway, even when Linux dont find hardware or the boot CD. ***
You can use the /dev/disk/by-id/* things for that I think.
Thanks,
Rafael
Quoted 9 lines · On Sat, 14 Jun 2008 15:26:09 -0300 (GFT) "werner" <[email protected]>…
During preparation and own testing for my distro; installation on computers for neighbours, by reclamations by users, I learned about the following problems of 2.6.26-rcX :
1) When compiling for i486, one cannot select/configurate more memory than 4 GB, menuconfig don't show items with higher values. My own computer/server has 8 GB, but when I compile the kernel with 4 GB and i486 then 'free' shows only 3.2 GB (no shared grafics, the grafic card has its own memory) ...
interesting problem... 486's didn't have PAE so are limited to 4Gb of memory... makes this a policy question more than a bug... (in fact, if you configure for > 4Gb a 486 CPU will not boot... so arguably the new behavior is correct!!!)
Signature · 3 lines
If you want to reach me at my work email, use [email protected] For development, discussion and tips for power savings, visit http://www.lesswatts.org
Quoted 10 lines · Arjan van de Ven
Quoted 5 lines · On Sat, 14 Jun 2008 15:26:09 -0300 (GFT) "werner" <[email protected]>…
1) When compiling for i486, one cannot select/configurate more memory than 4 GB, menuconfig don't show items with higher values. My own computer/server has 8 GB, but when I compile the kernel with 4 GB and i486 then 'free' shows only 3.2 GB (no shared grafics, the grafic card has its own memory) ...
Quoted 4 lines
interesting problem... 486's didn't have PAE so are limited to 4Gb of memory... makes this a policy question more than a bug... (in fact, if you configure for > 4Gb a 486 CPU will not boot... so arguably the new behavior is correct!!!)
What's arguable about it?
Rene.
Quoted 4 lines · werner
During preparation and own testing for my distro; installation on computers for neighbours, by reclamations by users, I learned about the following problems of 2.6.26-rcX :
1) When compiling for i486, one cannot select/configurate more memory than 4 GB, menuconfig don't show items with higher values.
Is not the i486 limited to a 4GB address space?
Quoted 10 lines · David Newall
Quoted 7 lines · werner
During preparation and own testing for my distro; installation on computers for neighbours, by reclamations by users, I learned about the following problems of 2.6.26-rcX :
1) When compiling for i486, one cannot select/configurate more memory than 4 GB, menuconfig don't show items with higher values.
Is not the i486 limited to a 4GB address space?
The point, if I understand it correctly, is that if you compile the kernel for i486 and then run it on something that does support PAE, it will only see 4 GB of RAM.
Thanks,
Rafael
Quoted 12 lines · Rafael J. Wysocki
Quoted 10 lines · David Newall
Quoted 8 lines · werner
During preparation and own testing for my distro; installation on computers for neighbours, by reclamations by users, I learned about the following problems of 2.6.26-rcX :
1) When compiling for i486, one cannot select/configurate more memory than 4 GB, menuconfig don't show items with higher values.
Quoted 6 lines
Quoted 2 lines
Is not the i486 limited to a 4GB address space?
The point, if I understand it correctly, is that if you compile the kernel for i486 and then run it on something that does support PAE, it will only see 4 GB of RAM.
Rather like compiling it for i486 and running it on ia64: you ask for an i486, you don't get to use features beyond that CPU.
Quoted 16 lines · David Newall
Quoted 15 lines · Rafael J. Wysocki
Quoted 12 lines · David Newall
Quoted 8 lines · werner
During preparation and own testing for my distro; installation on computers for neighbours, by reclamations by users, I learned about the following problems of 2.6.26-rcX :
1) When compiling for i486, one cannot select/configurate more memory than 4 GB, menuconfig don't show items with higher values.
Is not the i486 limited to a 4GB address space?
Quoted 6 lines
Quoted 3 lines
The point, if I understand it correctly, is that if you compile the kernel for i486 and then run it on something that does support PAE, it will only see 4 GB of RAM.
Rather like compiling it for i486 and running it on ia64: you ask for an i486, you don't get to use features beyond that CPU.
Sure, that's reasonable.
Thanks,
Rafael