> On Mon, 26 Apr 1999, George Bonser wrote:
>
> >I just build your andrea3 on a low memory machine, it will not work well.
>
> I know. As first due an e2fs bug. There's also some other performance
> issue in some not normal condition (i.e. cp /dev/zero /tmp/zero) due
> too heavy try_to_free_buffers() writeahead loop (probably this is present
> in 2.2.6_andrea2 as well though).
>
> >Launched Netscape, clicked a link that opened up a second browser window,
> >segfault, kernel oops.
>
> This made me to think that you did something wrong. Here is definitely
> stable from an Oops point of view. You can show me your .config though.
>
Config sent in earlier mail ... THIS one is very stable so far. I suspect
that the chain of events in the earlier patch was that it caused some
filesystem corruption and that caused the kernel oops. I had one block of
a binary file turn up in lost+found after the cleanup of the andrea3
wreckage. Any idea how I might find out which file this belonged to? I
now have a binary file that lived in my root filesystem that is short a
block.
Andrea4 seems to be working well and "feels" faster ... will try some test
tomorrow to measure it. Wonder if the time of tonites news expire might be
any indication.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/