Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 09 Feb 2009 02:08:26 +0000
From:      "Bruce M. Simpson" <bms@FreeBSD.org>
To:        freebsd-stable@freebsd.org
Cc:        "S.N.Grigoriev" <serguey-grigoriev@yandex.ru>, Markus Hitter <mah@jump-ing.de>, rnoland@FreeBSD.org
Subject:   Re: Unhappy Xorg upgrade
Message-ID:  <498F901A.7000900@FreeBSD.org>
In-Reply-To: <4983A3AE.90804@FreeBSD.org>
References:  <329181233306971@webmail57.yandex.ru>	<985A59F2-20CC-4779-A000-018E52B5BFA9@jump-ing.de>	<101781233319948@webmail36.yandex.ru> <4983A3AE.90804@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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 
> symptoms with USB and Xorg 7.4 as I see on my amd64 desktop running 
> 7-STABLE from 00:00 UTC on this Wednesday.

I still see the USB symptoms with xorg-server port as of today -- forced 
rebuild with libpciaccess also. So amd64 is still regressed -- USB is 
totally unusable there after X is started. My theory was that somehow 
Xorg was stomping on the USB controller registers on this machine. The 
USB controller on this box is ALi, card=0x81561043.

My i386 laptop (IBM/Lenovo T43) is not affected, and USB mice work just 
fine there.

Obviously it's difficult to check what Xorg is actually doing to the 
registers on the box w/o a PCI bus analyzer, and of course due to normal 
decoding, those cycles probably won't be seen on the backplane itself as 
it sits behind a bridge; I haven't fully read what libpciaccess is doing.

I skimmed patch-src-freebsd_pci.c. I wonder if this code may be stomping 
on the USB controller in some way (i.e. how it frobs the BARs).

According to src/tools/tools/pciroms, the only PCI devices on this box 
with ROM BARs are mskc0 and vgapci0.

(I also wonder if it's possible to guarantee that the window at 0xC0000 
is always going to be available, even in the amd64 case.)

cheers
BMS



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