2.4.1 not fully sane on Alpha - file systems

[Michal Jaegermann]

I just tried to boot 2.4.1 kernel on Alpha UP1100.  This machine
happens to have two SCSI disks on sym53c875 controller and two IDE
drives hooked to a builtin "Acer Laboratories Inc. [ALi] M5229 IDE".
It boots and in the first moment makes even a pretty good impression
of beeing healthy.  But an attempt to compile something causes the
whole setup to start behaving weird, with a compiler obviously unable
to find both itself and the right sources, and the whole thing ends in
a silent lockup.

On the second boot I tried to copy kernel sources from a SCSI to an
IDE drive.  This time I got something in my logs and the same stuff
was printed on my screen before everything lockded up really tight
again (no sysrq).  Here it is:

 kernel: attempt to access beyond end of device
 kernel: 08:05: rw=0, want=198500353, limit=5779456
 kernel: attempt to access beyond end of device
 kernel: 08:05: rw=0, want=4294934529, limit=5779456
 kernel: attempt to access beyond end of device
 kernel: 08:05: rw=0, want=198500353, limit=5779456
 kernel: EXT2-fs error (device sd(8,5)): ext2_readdir: bad entry in
 directory #250255: directory entry across blocks - offset=0,
 inode=198505472, rec_len=32768, name_len=255

(and the machine dies at this point).

There is nothing wrong with this device and a file system on it.
Copying the same way, or compiling the same sources, but when booted
with 2.2.18 does not present a whiff of trouble and e2fsck, luckily
enough, finds my file systems still in place.  One should be grateful
for small favours.

Anybody have seen something similar?

  Michal
  [e-mail]

p.s. I find a bit humorous the fact that the code required to
recognize that one has _some_ partition table (I happen to have two
kinds at the moment) is billed in a config file as ADVANCED.
It did the job anyway. :-)