>Greetings all.
>
> This morning at 9:47am CST my machine (paranoia.dok.org) running linux
>2.2.1+arca_6 experienced 2 oopsen at the same time. Then at 12pm the machine
I seen, it's due a my bug in my inode patches. I'm afraid.
>experienced yet another oops which lead to a lockup (blank screen, still
>recoverable with the magic SysRQ key sequence u-s-b)
I know.
> I am not a kernel hacker and I do not know much about tracing oopsen,
>but I have followed the directions in
>
>/usr/src/linux/Documentation/oops-tracing.txt
> ^^^^ non kernel-hacker types take note!
>
>and I have attached the ksymoops output for all 3 oopsen along with some
>pertinent machine info.
Perfect report.
> ANDREA: if it turns out that the oopsen have nothing to do with your
>vm patches (which until now have been working beautifully) please let me know
I am happy to hear that my VM is working well for you ;)
>to whom I should forward a copy of this mail to, or feel free to forward it to
>the proper authorities. (I'd hate to bother Linus without good reason.)
Right you are, be careful, don't bother Linus with my bugs.
You can find the bug you reported just fixed if you apply:
ftp://ftp.kernel.org/pub/linux/testing/pre-patch-2.2.2-2.gz
on the top of 2.2.1.
Then you have to apply my arca-diff:
ftp://e-mind.com/pub/linux/arca-tree/2.2.2-pre2_arca-1.gz
on the top of 2.2.2-pre2.
Let me know if you'll have problems. 2.2.2-pre2_arca-1 should be rock
solid according to me.
Thanks for the report.
Andrea Arcangeli
-
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/