by Ulrich Windl[permalink] [raw]
Reading the article in the German computer magazine c't that Linux 2-4
is scheduled for release in December, and that Linux complained people
do not want to test the new kernel, I decided to test it.
The Hardware was: Spacewalker/Shuttle AV11 (VIA Apollo Pro chipset),
Intel Celeron-500 ("boxed"), 128MB PC133 SD-ROM (Infineon, no crap),
EIDE IBM hardisk (4GB, supporting UDMA 33).
[If you need more detail, I can provide them]
First the lesser important issues:
During config I noticed that documentation is missing for CONFIG_INPUT
(which is later required for USB), CONFIG_NLS_UTF8 (which is probably
even less clear as 88591 or CP850).
Some source files produced an assembler warning about an Indirect lcall
When booting, the kernel said
"Unknow bridge resource 0; assuming transparent". I don't know what
When typing "cat /proc/kmsg" I noticed that the process is not
Loading the keymap failed, but it seems SuSE Linux 7.0 is not quite 3.4-
ready (util-linux, modutils, e2fsprogs too old).
I also got "EXT2 check option not supported", "can't locate module
"vfat", probably because of old modutils however).
During some heavy disk I/O I got the impression that buffer writes are
delayed significantly, and that reading can be delayed by several
seconds when there is "writing back dirty buffers".
Finally I got a "gzip -t" CRC error on the kernel tar archive that was
without error when tried with 2.2.17. This is the possible show
stopper. The syslog messages did not report any problem (harddisk
operating in UDMA 33 mode, using a proper cable).
Documentation/sysctl/kernel.txt still is 2.2.10!
After hacking the kernel I got a conflict between <linux/spinlock.h>
and <asm/spinlock.h>, but it was too late to investigate. (I had done
over 4 hours merging rejected diffs, and I was tired from pressing C-d
C-d C-n in Emacs ;-))