It's more of a debugging issue for me. I like to see the stack of all the threads at the time of the oops to debug thread interaction bugs, but it's not critical. Is there a read-only live crash type facility available? I've tried enabling the pertinent kernel config options and using Gdb /boot/vmlinux /proc/kcore But I don't think that is working properly based on the data I'm seeing. Is there a better method for inspecting kernel data on live systems. Printk can be rather burdensome and can hide issues so I'll sometimes keep internal statistic structs, but I need a way of inspecting them on a live system.
Thanks. -----Original Message----- From: Arjan van de Ven [mailto:ar...@linux.intel.com] Sent: Wednesday, January 27, 2010 10:03 AM To: Gorby, RichardX R Cc: d...@lists.moblin.org Subject: Re: [Moblin Dev] crashdump config On 1/27/2010 10:00, Gorby, RichardX R wrote: > I have kexec-tools installed but it doesn't seem to create crashdumps when I > do > Echo c>/proc/sysrq-trigger > As I expected. Moblin does currently not support crash dumps, and there are no plans to add this, due to the limited value that these crash dumps provide, the poor reliability of such crash dumps and the complexity to implement these. Do you have a specific problem in mind where the standard "dump a set of oops information" is not sufficient,but you need a whole system dump instead? _______________________________________________ Moblin dev Mailing List dev@moblin.org To manage or unsubscribe from this mailing list visit: http://lists.moblin.org/listinfo/dev or your user account on http://moblin.org once logged in. For more information on the Moblin Developer Mailing lists visit: http://moblin.org/community/mailing-lists
