Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 09 Feb 2009 14:43:06 -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:  <1234208586.1524.17.camel@ferret.2hip.net>
In-Reply-To: <4990835A.3020303@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>

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

--=-35ABTMgOdLoeR8EGQwBO
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2009-02-09 at 19:26 +0000, Bruce M. Simpson wrote:
> Robert,
>=20
> First, thanks for all your dedicated work so far on the Xorg ports.
>=20
> I realize this upgrade has been somewhat fraught with unexpected issues.
>=20
> FWIW, things are not greener on the Linux side of the fence; many Ubuntu=20
> and Debian users have reported issues with the newer Xorg and in=20
> particular hald.
>=20
> Robert Noland wrote:
> > ...
> >> I still see the USB symptoms with xorg-server port as of today -- forc=
ed=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.
> >>    =20
> >
> > Is your usb sharing interrupts with the video card?
> >  =20
>=20
> Yes, it appears so. This is an ASUS Vintage AH-1, uniprocessor amd64 box=20
> w/ioapic enabled
>=20
> from devinfo -r (abbreviated):
> ohci0 17
> ohci1 18
> ohci2 19
> ehci0 23
>=20
> lspci -v jibes with devinfo -r -- the primary head got IRQ 18, the=20
> secondary IRQ 255.
>=20
> It appears msk0 is also sharing IRQ 18, though I haven't seen any=20
> problems with networking; mskc0, however, is then configured to use MSI=20
> (pseudo IRQ 256, 258), it is a PCI-e device.
>=20
> When the system starts, the drm module has not been loaded, so the=20
> Radeon (Sapphire X550) card hasn't been allocated its IRQ by FreeBSD.
>=20
> After X starts, glxinfo and glxgers work fine. kldstat reports drm.ko=20
> and radeon.ko got loaded by X as I would expect. I still see no IRQ=20
> allocated for the radeon, either in dmesg output or in devinfo -r,=20
> however, vmstat -i does show drm0 as sharing IRQ 18.

Ok, that is odd... Once drm is loaded and X opens it, the ddx driver
should request that the irq handler be installed.  At that point, dmesg
should show something resembling the following.

vgapci0: child drm0 requested pci_enable_busmaster
info: [drm] AGP at 0xc0000000 256MB
info: [drm] Initialized i915 1.6.0 20080730
drm0: [ITHREAD]

I have code to enable msi for drm, which has been at least minimally
tested on intel and ati.  FWIW, linux does not support msi on radeon
yet, so I got the jump on them there... The outstanding issue with that
code is that I still need to implement a blacklist for certain devices
that report msi capability, but don't (intel 945gm, is the only known
chip atm).

Does the issue still occur if drm is disabled?

robert.

> At this point, I rebooted and tried manually resetting the BIOS ESCD=20
> table, unfortunately the BIOS on this machine won't let me tie IRQs down=20
> to particular devices.
>=20
>=20
> > Does the issue occur if you aren't using a usb mouse?
> >  =20
>=20
> I see the USB problems regardless of the kind of USB devices plugged in,=20
> I continue to use a PS/2 mouse on the desktop as a workaround.
>=20
> I see the bump on devel/libpciaccess re typo of rombase, and forced a=20
> rebuild of xorg-server against the patched libpciaccess library=20
> (probably not needed, as the .so ABI didn't change).
>=20
> The USB problem is still present, unfortunately.
>=20
> thanks,
> BMS
>=20
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
--=20
Robert Noland <rnoland@FreeBSD.org>
FreeBSD

--=-35ABTMgOdLoeR8EGQwBO
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)

iEYEABECAAYFAkmQh0kACgkQM4TrQ4qfROO26QCfSCPARz0lb50RJHxAYgA0rTem
3igAnA1FqQSt7CQdNZ/jrekwa94BvMY1
=9cPB
-----END PGP SIGNATURE-----

--=-35ABTMgOdLoeR8EGQwBO--




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