On Thu, 08 Aug 2019 09:47:46 -0600
"Theo de Raadt" wrote:
> The mechanism underlying unveil(2) is a vnode cache.
>
> After unveil is activated, pathname-accessing functions (except
> for unveil(2) itself) require at a vnode in that cache to be
> "traversed".
>
> I believe your first openat()
>Synopsis: ADB (Android debug Bridge) lead sometimes to a kernel crash in
>xhci with bsd.mp
>Category: amd64 kernel
>Environment:
System : OpenBSD 6.5
Details : OpenBSD 6.5-current (GENERIC.MP) #172: Mon Aug
5 21:27:09 MDT 2019
The mechanism underlying unveil(2) is a vnode cache.
After unveil is activated, pathname-accessing functions (except
for unveil(2) itself) require at a vnode in that cache to be
"traversed".
I believe your first openat() references "." which is in the
unveil vnode cache, so it wins.
That gives
On Thu, Aug 08, 2019 at 10:23:15AM +0200, Sebastien Marie wrote:
>
> I will try to compare i386 and amd64 in r600_read_disabled_bios().
I didn't found any major difference between i386 and amd64. the values
below are the same for i386 and amd64.
- radeon_get_bios()
-
On Thu, Aug 08, 2019 at 06:57:57AM +0200, Sebastien Marie wrote:
> On Wed, Aug 07, 2019 at 11:12:57PM +0200, Mark Kettenis wrote:
> > > > Can you try to figure out where exactly reading the BIOS from the card
> > > > goes wrong?
> > >
> > > radeon_read_bios (called by r600_read_disabled_bios)
On Thu, Aug 08, 2019 at 09:42:49AM +0200, Sebastien Marie wrote:
> On Wed, Aug 07, 2019 at 07:47:43PM +0200, Matthieu Herrb wrote:
> > On Wed, Aug 07, 2019 at 11:32:09AM +0200, Matthieu Herrb wrote:
> > >
> > > I will also have a look on why did the extra built-in modes disapear.
> > > But I
On Wed, Aug 07, 2019 at 07:47:43PM +0200, Matthieu Herrb wrote:
> On Wed, Aug 07, 2019 at 11:32:09AM +0200, Matthieu Herrb wrote:
> >
> > I will also have a look on why did the extra built-in modes disapear.
> > But I think that if you can run a better driver than xf86-video-vesa,
> > it is
