Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 09 Feb 2009 01:00:36 -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:  <1234159237.23838.3.camel@ferret.2hip.net>
In-Reply-To: <498F901A.7000900@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>

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

--=-gOszhsnuOinBWQrHk+a9
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2009-02-09 at 02:08 +0000, Bruce M. Simpson wrote:
> Bruce M. Simpson wrote:
> > S.N.Grigoriev wrote:
> >> I thank you for your response. I've applied the patch to pci.c from
> >> kern/130957. Unfortunately there are no positive results. USB is still
> >> unreachable with X.
> >
> > Just following up to confirm that you are seeing exactly the same=20
> > symptoms with USB and Xorg 7.4 as I see on my amd64 desktop running=20
> > 7-STABLE from 00:00 UTC on this Wednesday.
>=20
> I still see the USB symptoms with xorg-server port as of today -- forced=20
> rebuild with libpciaccess also. So amd64 is still regressed -- USB is=20
> totally unusable there after X is started. My theory was that somehow=20
> Xorg was stomping on the USB controller registers on this machine. The=20
> USB controller on this box is ALi, card=3D0x81561043.

Is your usb sharing interrupts with the video card?

Does the issue occur if you aren't using a usb mouse?

robert.

> My i386 laptop (IBM/Lenovo T43) is not affected, and USB mice work just=20
> fine there.
>=20
> Obviously it's difficult to check what Xorg is actually doing to the=20
> registers on the box w/o a PCI bus analyzer, and of course due to normal=20
> decoding, those cycles probably won't be seen on the backplane itself as=20
> it sits behind a bridge; I haven't fully read what libpciaccess is doing.
>=20
> I skimmed patch-src-freebsd_pci.c. I wonder if this code may be stomping=20
> on the USB controller in some way (i.e. how it frobs the BARs).
>=20
> According to src/tools/tools/pciroms, the only PCI devices on this box=20
> with ROM BARs are mskc0 and vgapci0.
>=20
> (I also wonder if it's possible to guarantee that the window at 0xC0000=20
> is always going to be available, even in the amd64 case.)
>=20
> cheers
> BMS
--=20
Robert Noland <rnoland@FreeBSD.org>
FreeBSD

--=-gOszhsnuOinBWQrHk+a9
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)

iEYEABECAAYFAkmPxoQACgkQM4TrQ4qfROMuwgCeIaPqbNQ6akY11b6G1EeB3/Vv
M4oAn0S5j8Ls7rEkEQhYCpxta/k+dJYR
=Jf7L
-----END PGP SIGNATURE-----

--=-gOszhsnuOinBWQrHk+a9--




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