[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PCI arbiter crash on last qemu image
From: |
Damien Zammit |
Subject: |
Re: PCI arbiter crash on last qemu image |
Date: |
Mon, 7 Sep 2020 11:16:13 +1000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 |
On 6/9/20 11:17 pm, Samuel Thibault wrote:
>> I have uploaded libpciaccess_0.16-1+hurd.5 with the latest upstream
>> version.
Thanks!
> One issue remains, however: Xorg's vesa driver produces
>
> [1669282.478] (II) VESA(0): initializing int10
> [1669282.478] (EE) VESA(0): Cannot read int vect
>
> which comes from hw/xfree86/int10/generic.c xf86ExtendedInitInt10:
>
> if (!sysMem)
> pci_device_map_legacy(pInt->dev, V_BIOS, BIOS_SIZE + SYS_BIOS -
> V_BIOS,
> PCI_DEV_MAP_FLAG_WRITABLE, &sysMem);
It appears that it's trying to map more than BIOS_SIZE, which probably fails
under the current scheme.
Perhaps we need to make overreads return zeroes instead of failure?
Purely guessing here...
Damien
- Re: PCI arbiter crash on last qemu image, Samuel Thibault, 2020/09/06
- Re: PCI arbiter crash on last qemu image, Samuel Thibault, 2020/09/06
- Re: PCI arbiter crash on last qemu image, Samuel Thibault, 2020/09/06
- Re: PCI arbiter crash on last qemu image,
Damien Zammit <=
- Re: PCI arbiter crash on last qemu image, Samuel Thibault, 2020/09/09
- Re: PCI arbiter crash on last qemu image, Samuel Thibault, 2020/09/09
- Re: PCI arbiter crash on last qemu image, Joan Lledó, 2020/09/13
- Re: PCI arbiter crash on last qemu image, Samuel Thibault, 2020/09/13
- Re: PCI arbiter crash on last qemu image, Joan Lledó, 2020/09/13