Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Feb 2009 13:57:26 -0500
From:      Robert Noland <rnoland@FreeBSD.org>
To:        "Bruce M. Simpson" <bms@FreeBSD.org>
Cc:        "S.N.Grigoriev" <serguey-grigoriev@yandex.ru>, Markus Hitter <mah@jump-ing.de>, freebsd-stable@freebsd.org
Subject:   Re: Unhappy Xorg upgrade
Message-ID:  <1234292252.1524.38.camel@ferret.2hip.net>
In-Reply-To: <4991C017.8080903@FreeBSD.org>
References:  <329181233306971@webmail57.yandex.ru> <985A59F2-20CC-4779-A000-018E52B5BFA9@jump-ing.de> <101781233319948@webmail36.yandex.ru> <4983A3AE.90804@FreeBSD.org> <498F901A.7000900@FreeBSD.org> <1234159237.23838.3.camel@ferret.2hip.net> <4990835A.3020303@FreeBSD.org> <1234208586.1524.17.camel@ferret.2hip.net> <4990BC99.1070108@FreeBSD.org> <1234246034.1524.27.camel@ferret.2hip.net> <4991C017.8080903@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-46oDHuVXdbKn3gLAcb1k
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

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.
> >  =20
>=20
> Well spotted. I saw this tool in "locate" output and was going to try it=20
> the other day, although I saw it didn't get installed, so assumed it was=20
> historical.
>=20
> Yes, This immediately triggered the issue without even running X on a=20
> 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.

--=20
Robert Noland <rnoland@FreeBSD.org>
FreeBSD

--=-46oDHuVXdbKn3gLAcb1k
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (FreeBSD)

iEUEABECAAYFAkmRzhYACgkQM4TrQ4qfROMBagCfTdI7UPNJuz+VnP6dvyghqXjW
N3EAmKzUWZ91q7dM62Qi+IVGOdW1cls=
=sBUa
-----END PGP SIGNATURE-----

--=-46oDHuVXdbKn3gLAcb1k--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1234292252.1524.38.camel>