Dave Anderson wrote: >> See also https://bugs.launchpad.net/ubuntu/+source/crash/+bug/559219 >> >> -- >> Sergey Svishchev > > BTW, if you follow the advice in the ubuntu bug description, does > the crash session work normally? (It's my bug report :-) Yes, mostly. Date is wrong (DATE: Sun Oct 26 03:35:21 2594), 'bt' reports some errors but otherwise backtraces look sane. crash> bt PID: 0 TASK: ffffffff81796600 CPU: 0 COMMAND: "swapper" #0 [ffffffff8176fe58] schedule at ffffffff81525251 bt: invalid kernel virtual address: 41 type: "call byte" bt: invalid kernel virtual address: 1587b type: "call byte" bt: invalid kernel virtual address: 1587b type: "call byte" bt: invalid kernel virtual address: 1587b type: "call byte" bt: invalid kernel virtual address: 1587b type: "call byte" bt: invalid kernel virtual address: 1587b type: "call byte" bt: invalid kernel virtual address: 1587b type: "call byte" bt: invalid kernel virtual address: 1587b type: "call byte" bt: invalid kernel virtual address: 6db6db6db6db6db2 type: "call byte" bt: invalid kernel virtual address: 937fb type: "call byte" #1 [ffffffff8176ff00] cpu_idle at ffffffff81010e45 -- Sergey Svishchev

> By any chance do you have any insights re: the structure-related > changes associated with CPU_SAVE_VERSION?. This is an upstream bug > report, but I note that in qemu-kvm-0.11.0-rc1.fc12.i686, it's equal > to 10 in target-i386/cpu.h. It needs an update for newer qemus. I'll take a look, as probably we'd want this on RHEL6 too (or maybe not, I used crash/kvm on RHEL6 about a month ago). Paolo