Hi... On Fri, Jul 23, 2010 at 00:43, Zax Zax <[email protected]> wrote: > no stack trace is available. Even when I run it through the GDB. In GDB I > get PC not save and that's it.
It's also likely because it's not compiled with -g or using -fomit-frame-pointer >I'm compiling with -O2 gcc option. When I > compile with -O0 or -O1 the Problem disappears. Now this is weird.... but I think the problem it's not on the -O option itself, but "clash of the options"...-O enables something..and that other options negates it or render the final result "awkward". >Is it possible to be some > kind of unaligned data access? Could be..... x86 (32 and 64 bit) is ok with unaligned access...however, it should end up with trap IIRC... not "close". The error message itself, honestly IMO, is confusing.... > P.S. > I cannot find the "kernel:Close" in the kernel source and I don't have any > clue... I've forget to mention that I am using kernel 2.6.23.17. Either it's in your kernel message....or...ok wait, thinking another possibility, it's in your initramfs or initrd image..or something else that can be considered initializing your system at very same degree of your core kernel.....now this is a challenging exercise.... -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ
