On Saturday 30 December 2006 18:06, James Courtier-Dutton wrote: > > I'd guess you have some kind of hardware problem. It could also be > > a kernel problem where the saved address was corrupted during an > > interrupt, but that's not likely. > > This looks rather strange. [snip]
> 2) Kernel modules compiled with different gcc than rest of kernel. Previously there was only one GCC version (4.1.1 totally replaced 3.4.3, and is the system wide GCC), now I have installed 3.4.6 into /opt/gcc-3.4.6 and it is only PATH'ed explicitly by me when I wish to compile a kernel using it: export PATH=/opt/gcc-3.4.6/bin:$PATH cp /boot/config-2.6.19-test .config make oldconfig make > 3) kernel headers do not match the kernel being used. The tree is a pristine 2.6.19. > One way to start tracking this down would be to run it with the fewest > amount of kernel modules loaded as one can, but still reproduce the > problem. Crippling the machine, though. Impractical for something that isn't immediately reproducible. -- Cheers, Alistair. Final year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/