Leslie Mann wrote:
> That works. Here is the last 100 lines from the strace capture. Letme know if
> there is anything else you need.
>
[...]
> 21:05:48.736568 clock_gettime(CLOCK_MONOTONIC, {1334, 970496230}) = 0
> <0.000010>
> 21:05:48.736618 sigreturn() = ? (mask now []) <0.000008>
> 21:05:48.736707 ioctl(10, 0xae80, 0) = 0 <0.000022>
> 21:05:48.736767 ioctl(10, 0xae80, 0) = 0 <0.000544>
> 21:05:48.744119 --- SIGIO (I/O possible) @ 0 (0) ---
> 21:05:48.744146 clock_gettime(CLOCK_MONOTONIC, {1334, 978076521}) = 0
> <0.000010>
> 21:05:48.744200 sigreturn() = ? (mask now [INT QUIT TRAP FPE KILL
> SEGV TSTP URG SYS RTMIN]) <0.000010>
> 21:05:48.744285 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
>
The SIGIO means some I/O has occured, but what exactly, we don't know.
Can you generate a core, attach it with gdb, and generate a backtrace?
Check the backtrace for signs of your password and delete them if
found. It shouldn't be there, but then it shouldn't crash either.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
kvm-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kvm-devel
