Unhappy Xorg upgrade
rnoland at FreeBSD.org
Tue Feb 10 10:57:41 PST 2009
On Tue, 2009-02-10 at 17:57 +0000, Bruce M. Simpson wrote:
> Robert Noland wrote:
> > ...
> > Ok, lets try another test... There is a scanpci util in the
> > libpciaccess port. We don't install it, but it does get built. Build
> > the port and run scanpci -v as root from the console. That should poke
> > all the pci devices on the box and tell you about them. See if that is
> > able to trigger the issue.
> Well spotted. I saw this tool in "locate" output and was going to try it
> the other day, although I saw it didn't get installed, so assumed it was
> Yes, This immediately triggered the issue without even running X on a
> fresh boot.
Ok, At least we know where the issue lies now. I'll try and look the
code over again, but I behaves almost identically to the kernel routines
I think. jhb@ wrote us a new ioctl to avoid doing most of this from
userland, but it will be a while before we can count on it's existence
and it doesn't support bios frobbing yet.
Can you verify that pciconf -lvbc does not trigger the issue?
Robert Noland <rnoland at FreeBSD.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090210/313ce89e/attachment.pgp
More information about the freebsd-stable