linux-kernel - Re: [kvm-devel] [BUG] Oops with KVM-27

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <466CFD6D.2080201@qumranet.com>
Date:	Mon, 11 Jun 2007 10:44:45 +0300
From:	Avi Kivity <avi@...ranet.com>
To:	Luca <kronos.it@...il.com>
CC:	kvm-devel@...ts.sf.net, linux-kernel@...r.kernel.org
Subject: Re: [kvm-devel] [BUG] Oops with KVM-27

Luca wrote:
>>
>> I've managed to reproduce this on kvm-21 (it takes many boots for this
>> to happen, but it does eventually).
>
> Hum, any clue on the cause? 

 From what I've seen, it's the new Linux clocksource code.

> Should I test older versions?

They're unlikely to be better.  Instead, it would be best to see what 
the guest is doing.

I suggest downloading the source rpm for the kernel, building it, and 
sprinkling printk()s until we know exactly what source the guest is 
executing at the time of the hang.

Use of the qemu -kernel, -append, and -serial can redirect the console 
to the command line so that it's easy to capture all debug output.

-- 
error compiling committee.c: too many arguments to function

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/