Avi Kivity a écrit :
> Aurelien Jarno wrote:
>> Well the IDE code hasn't changed a lot recently, so I checked the CVS
>> history and easily (first test) found the commit that causes the problem:
>>
>> Last AIO patch, by Vladimir N. Oleynik.
>>
>> http://cvs.savannah.nongnu.org/viewvc/qemu/hw/ide.c?
Aurelien Jarno wrote:
> Well the IDE code hasn't changed a lot recently, so I checked the CVS
> history and easily (first test) found the commit that causes the problem:
>
> Last AIO patch, by Vladimir N. Oleynik.
>
> http://cvs.savannah.nongnu.org/viewvc/qemu/hw/ide.c?root=qemu&r1=1.64&r2=1.65
>
>
On Tue, Oct 02, 2007 at 02:38:19PM +0200, Avi Kivity wrote:
> Aurelien Jarno wrote:
> > Avi Kivity a écrit :
> >
> >> Aurelien Jarno wrote:
> >>
> >>> Hi all,
> >>>
> >>> That's not something new, but I never seen the problem mentioned here.
> >>> FreeBSD does not work on KVM, approximately
Avi Kivity a écrit :
> Aurelien Jarno wrote:
>> Avi Kivity a écrit :
>>
>>> Aurelien Jarno wrote:
>>>
>> I also confirm that using -no-acpi fixes the problem. However, I have
>> seen strange data corruption, even on Intel.
>>
>> Basically, booting a recently installed FreeBS
Aurelien Jarno wrote:
> Avi Kivity a écrit :
>
>> Aurelien Jarno wrote:
>>
> I also confirm that using -no-acpi fixes the problem. However, I have
> seen strange data corruption, even on Intel.
>
> Basically, booting a recently installed FreeBSD leads to the following
>
Avi Kivity a écrit :
> Aurelien Jarno wrote:
I also confirm that using -no-acpi fixes the problem. However, I have
seen strange data corruption, even on Intel.
Basically, booting a recently installed FreeBSD leads to the following
message from the bootloader: "No kernel fou
Aurelien Jarno wrote:
> Avi Kivity a écrit :
>
>> Aurelien Jarno wrote:
>>
> I also confirm that using -no-acpi fixes the problem. However, I have
> seen strange data corruption, even on Intel.
>
> Basically, booting a recently installed FreeBSD leads to the following
>
Avi Kivity a écrit :
> Aurelien Jarno wrote:
I also confirm that using -no-acpi fixes the problem. However, I have
seen strange data corruption, even on Intel.
Basically, booting a recently installed FreeBSD leads to the following
message from the bootloader: "No kernel fou
Aurelien Jarno wrote:
>>> I also confirm that using -no-acpi fixes the problem. However, I have
>>> seen strange data corruption, even on Intel.
>>>
>>> Basically, booting a recently installed FreeBSD leads to the following
>>> message from the bootloader: "No kernel found". And the next time, I ge
Laurent Vivier wrote:
> Avi Kivity wrote:
>
>> Laurent Vivier wrote:
>>
>>> Avi Kivity wrote:
>>>
>>>
Aurelien Jarno wrote:
> It's actually described page 200 of the specifications (page 216 in
> ACPIspec30.pdf):
>
> Note: This descri
Avi Kivity wrote:
> Laurent Vivier wrote:
>> Avi Kivity wrote:
>>
>>> Aurelien Jarno wrote:
>>>
It's actually described page 200 of the specifications (page 216 in
ACPIspec30.pdf):
Note: This descriptor is meant for describing interrupts that are
connected to PIC-
Laurent Vivier wrote:
> Avi Kivity wrote:
>
>> Aurelien Jarno wrote:
>>
>>> It's actually described page 200 of the specifications (page 216 in
>>> ACPIspec30.pdf):
>>>
>>> Note: This descriptor is meant for describing interrupts that are
>>> connected to PIC-compatible
>>> interrupt co
Avi Kivity wrote:
> Aurelien Jarno wrote:
>>
>> It's actually described page 200 of the specifications (page 216 in
>> ACPIspec30.pdf):
>>
>> Note: This descriptor is meant for describing interrupts that are
>> connected to PIC-compatible
>> interrupt controllers, which can only be programmed f
Aurelien Jarno wrote:
It's actually described page 200 of the specifications (page 216 in
ACPIspec30.pdf):
Note: This descriptor is meant for describing interrupts that are connected
to PIC-compatible
interrupt controllers, which can only be programmed for
Active-High-Edge-Triggered or
Laurent Vivier wrote:
>>
>> Edge-triggered means we can't share interrupt lines. Since we have only
>> two or three that limits the number of devices we can have.
>>
>> So I'd like to try moving to active low pci interrupts, and implementing
>> polarity in the qemu ioapic. It's probably closer
Avi Kivity wrote:
> Aurelien Jarno wrote:
>> On Fri, Oct 05, 2007 at 03:25:05PM +0200, Laurent Vivier wrote:
>>
>>> Digging in the FreeBSD sources I found the origin of the problem:
>>>
>>> I added some ACPI traces:
>>>
>>>rsirq-0234 [13] RsIrqResource : Invalid interrupt
>>> polari
Avi Kivity wrote:
> Aurelien Jarno wrote:
>
>> On Fri, Oct 05, 2007 at 03:25:05PM +0200, Laurent Vivier wrote:
>>
>>
>>> Digging in the FreeBSD sources I found the origin of the problem:
>>>
>>> I added some ACPI traces:
>>>
>>>rsirq-0234 [13] RsIrqResource : Invalid interrup
Aurelien Jarno wrote:
> On Fri, Oct 05, 2007 at 03:25:05PM +0200, Laurent Vivier wrote:
>
>> Digging in the FreeBSD sources I found the origin of the problem:
>>
>> I added some ACPI traces:
>>
>>rsirq-0234 [13] RsIrqResource : Invalid interrupt
>> polarity/trigger in
>> resource l
Aurelien Jarno wrote:
> On Fri, Oct 05, 2007 at 03:25:05PM +0200, Laurent Vivier wrote:
[snip]
> It looks like the solution is either to describe the IRQ with an
> "Extended Interrupt Descriptor" or to change this value to one of the
> two allowed values. In the later case we have to make sure it
On Fri, Oct 05, 2007 at 03:25:05PM +0200, Laurent Vivier wrote:
> Digging in the FreeBSD sources I found the origin of the problem:
>
> I added some ACPI traces:
>
>rsirq-0234 [13] RsIrqResource : Invalid interrupt polarity/trigger
> in
> resource list, 10
>
> Which is in /sys/cont
Aurelien Jarno wrote:
> Hi all,
>
> That's not something new, but I never seen the problem mentioned here.
> FreeBSD does not work on KVM, approximately since the lapic merge.
>
> However, that does not seem related to lapic, as using -no-kvm-irqchip
> does not help. With -no-kvm I get a page fau
Avi Kivity wrote:
> Aurelien Jarno wrote:
>> Avi Kivity a écrit :
>>
>>> Aurelien Jarno wrote:
>>>
Hi all,
That's not something new, but I never seen the problem mentioned here.
FreeBSD does not work on KVM, approximately since the lapic merge.
However, that do
Aurelien Jarno a écrit :
> Aurelien Jarno a écrit :
>> Avi Kivity a écrit :
>>> Aurelien Jarno wrote:
Avi Kivity a écrit :
> Aurelien Jarno wrote:
>
>> Hi all,
>>
>> That's not something new, but I never seen the problem mentioned here.
>> FreeBSD does not
Aurelien Jarno a écrit :
> Avi Kivity a écrit :
>> Aurelien Jarno wrote:
>>> Avi Kivity a écrit :
>>>
Aurelien Jarno wrote:
> Hi all,
>
> That's not something new, but I never seen the problem mentioned here.
> FreeBSD does not work on KVM, approximately since the
Avi Kivity a écrit :
> Aurelien Jarno wrote:
>> Avi Kivity a écrit :
>>
>>> Aurelien Jarno wrote:
>>>
Hi all,
That's not something new, but I never seen the problem mentioned here.
FreeBSD does not work on KVM, approximately since the lapic merge.
However, that
Aurelien Jarno wrote:
> Avi Kivity a écrit :
>
>> Aurelien Jarno wrote:
>>
>>> Hi all,
>>>
>>> That's not something new, but I never seen the problem mentioned here.
>>> FreeBSD does not work on KVM, approximately since the lapic merge.
>>>
>>> However, that does not seem related to lapic,
Laurent Vivier a écrit :
> Avi Kivity wrote:
>> Aurelien Jarno wrote:
>>> Hi all,
>>>
>>> That's not something new, but I never seen the problem mentioned here.
>>> FreeBSD does not work on KVM, approximately since the lapic merge.
>>>
>>> However, that does not seem related to lapic, as using -no-
Aurelien Jarno wrote:
> Avi Kivity a écrit :
>
>> Aurelien Jarno wrote:
>>
>>> Hi all,
>>>
>>> That's not something new, but I never seen the problem mentioned here.
>>> FreeBSD does not work on KVM, approximately since the lapic merge.
>>>
>>> However, that does not seem related to lapic,
Avi Kivity wrote:
> Aurelien Jarno wrote:
>> Hi all,
>>
>> That's not something new, but I never seen the problem mentioned here.
>> FreeBSD does not work on KVM, approximately since the lapic merge.
>>
>> However, that does not seem related to lapic, as using -no-kvm-irqchip
>> does not help. With
Avi Kivity a écrit :
> Aurelien Jarno wrote:
>> Hi all,
>>
>> That's not something new, but I never seen the problem mentioned here.
>> FreeBSD does not work on KVM, approximately since the lapic merge.
>>
>> However, that does not seem related to lapic, as using -no-kvm-irqchip
>> does not help. W
Laurent Vivier a écrit :
> Hi Aurélien,
>
> did you try kvm-45 ?
>
Yes the test is done with kvm-45.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' [EMAIL PROTECTED] | [EMAIL PROTECTED]
`-people.deb
Aurelien Jarno wrote:
> Hi all,
>
> That's not something new, but I never seen the problem mentioned here.
> FreeBSD does not work on KVM, approximately since the lapic merge.
>
> However, that does not seem related to lapic, as using -no-kvm-irqchip
> does not help. With -no-kvm I get a page fault
Hi Aurélien,
did you try kvm-45 ?
Laurent
Aurelien Jarno wrote:
> Hi all,
>
> That's not something new, but I never seen the problem mentioned here.
> FreeBSD does not work on KVM, approximately since the lapic merge.
>
> However, that does not seem related to lapic, as using -no-kvm-irqchip
>
Hi all,
That's not something new, but I never seen the problem mentioned here.
FreeBSD does not work on KVM, approximately since the lapic merge.
However, that does not seem related to lapic, as using -no-kvm-irqchip
does not help. With -no-kvm I get a page fault in kernel mode, while the
normal
34 matches
Mail list logo
