Gregory Haerr

> sys assumes the source fs is an image created by the build_hd_image.sh script Wow - I've never seen that script before. It is extremely outdated and should probably be...

> Back to the rm hang problem > This is repeatable only on one particular machine, so I'm going after it in that setting If this only repeats with the...

> Also, if those printks don't have arguments, just text, they have no effect. > So we have a stack pollution issue, a very elusive one: The printks can be...

Reviewing this issue a bit, I am now guessing that the kernel corruption, now more firmly evidenced by printk's not working (which occurred on the last similar issue), is ultimately...

Hello @Mellvik, I have reviewed the previous issues relating to the ELKS kernel crashing, or acting strangely, and haven't yet been able to correlate to this problem. In order to...

The actual issue itself seems to be evolving... we know there's a kernel problem where the system can appear to hang due to not enough buffers. This manifests itself by...

> The compaq actually hangs during boot because it's set up to mount 4 filesystems and stops in the 3rd Three mounts is a lot of activity - introduces variables...

Hello @Mellvik, Actually these two logs look remarkably similar - so much so that the block reads and buffer map/unmaps are identical, right until the moment where the system hangs...

Hi @Mellvik, I'm getting confused again on this issue, we might possibly be talking about different things - is the problem that `rm` hangs, or something else? My long response...

So basically, all of these issues (except mount) occur only on the SX/ALI system, right? If so, we need to consider BIOS or hardware issues (including possible I/O delays only...