Re: Tux Kernel Bug

* Marek Habersack <[email protected]> wrote:

> Yes, the oops I posted for the first time was from the older tux, I've
> tested it with the newer patches since. It seems the issue got worse,
> although the outcome is precisely the same - the machine needs to be
> hard reset in order to make it operational again. The new oops isn't a
> result of a BUG() in inode.c but a null pointer dereference, and it's
> been the same in A4 and A5:

> CONFIG_TUX_DEBUG=y

the reason for the crash is that CONFIG_TUX_DEBUG doesnt work in -A5 (a
side-effects of the ->in_file cleanups). I have fixed it in my tree and
it should work in -A6.

	Ingo