No subject

Unknown Unknown
Thu Apr 7 11:52:33 PDT 2011

fA at>	<4D9B1466.5020604 at> <BANLkTim3Tpa9MQUNFn0BrxYsze1UKmNvKg at>
From: Max Herrgard <herrgard at>
Subject: Re: ACPI based interrupt routing and new ACPI code ready for testing
Date: Thu, 07 Apr 2011 20:49:08 +0200
List-Post: <mailto:users at>
List-Subscribe: <mailto:users-request at>
List-Unsubscribe: <mailto:users-request at>
List-Help: <mailto:users-request at>
List-Owner: <mailto:owner-users at>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
In-Reply-To: <BANLkTim3Tpa9MQUNFn0BrxYsze1UKmNvKg at>
Sender: users-errors at
Errors-To: users-errors at
Lines: 30
X-Trace: 1302202460 879
Xref: dragonfly.users:15642

Sepherosa Ziehau wrote:
> On Tue, Apr 5, 2011 at 9:08 PM, Max Herrgard<herrgard at>  wrote:
>> Sepherosa Ziehau wrote:
>>> On Mon, Apr 4, 2011 at 6:02 PM, Max Herrgard<herrgard at>    wrote:
>>>> Nope. Still the same, but they are now on different irqs. I noticed
>>>> however
>>>> that my drm0 doesn't get set up with acpi interrupt routing turned on.
>>> Hmm, looks like its irq setting up is hosed somewhere else.  drm
>>> device itself is attached.
>>> As far as I understand the drm code, bus_setup_intr is triggered by
>>> user space program like Xorg, but there are some precondition check
>>> before bus_setup_intr is called.  Please set hw.dri.debug=1 (sysctl)
>>> and give me the output of vmstat -iv and dmesg, after you started
>>> Xorg.
> Please retest master:
> 7e89a536e0a53aade79d6001b8477d03245f0be0
> I believe it is fixed.

Yes. Everything now works as it should :)


More information about the Users mailing list