From: stuart hayes <stuart.w.hayes@gmail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
Jacob Keller <jacob.e.keller@intel.com>,
Jocelyn Falempe <jfalempe@redhat.com>,
"airlied@redhat.com" <airlied@redhat.com>
Cc: dri-devel@lists.freedesktop.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pasi Vaananen <pvaanane@redhat.com>
Subject: Re: further issues with MGA G200 graphics chipset
Date: Tue, 28 Apr 2026 14:12:49 -0500 [thread overview]
Message-ID: <be1f1005-a7ed-4a5b-904b-35541b19658a@gmail.com> (raw)
In-Reply-To: <3def4337-4297-45fa-8825-4147abda49f4@suse.de>
On 4/27/2026 7:14 AM, Thomas Zimmermann wrote:
> Hi
>
> Am 25.04.26 um 01:29 schrieb Jacob Keller:
> [...]
>>>
>>> So I suggest to pick Manufacturer, Product, Version as key. I'd be
>>> surprised if we find more than a hand full of systems with the issue. If
>>> we see a trend or common pattern, we can generalize later on.
>>>
>> I think this is the best solution. Keep it focused for now. I believe
>> Intel has two major platforms that we care about with respect to this
>> issue. I'll see if I can dig up the data. The systems install the MGA
>> G200 for BMC use but don't seem to expose the VGA connection.
>>
>> For the specific system I have that was faulty, we have the following:
>>
>> $ for t in system-manufacturer system-product-name system-version ; \
>> do dmidecode -s ${t}; \
>> done
>> Dell Inc.
>> PowerEdge XR8720t
>> Not Specified
>>
>>
>>
>> I believe there was also some concern about HP systems which similarly
>> use this chipset, but I don't have the DMI data for that one off hand.
>> I've asked some colleagues to confirm the situation and obtain that
>> data. I'll get back early next week if we think there are any other
>> systems possibly affected.
>>
>> In the mean time, I'm happy to have our team test any patch to confirm
>> that it behaves as expected and resolves the service interruptions.
>
> For now, I've modified the two places that have BMC support in the
> driver. Could you please also tell me your system's exact Matrox chipset
> or its PCI id?
>
> The patch is attached for your testing. It would work against drm-tip or
> v7.1-rc1.
>
> I've also found the page at [1], which claims that there's a Mini-DP
> port at the front. If so, I'd assume that there's also an extra encoder
> chip to replace the VGA. If we ever get specs for that, we could
> implement real support in the driver.
>
> In the meantime, the current fix should work. In the worst case, that
> Mini-DP port would give a lower default resolution.
>
> [1] https://www.dell.com/en-us/shop/ipovw/poweredge-xr8720t?
> hve=shop+now#techspecs_section
>
> Best regards
> Thomas
>
>
So this patch disables DDC polling if the dmi_check_system() matches. If
this was to happen on systems that _do_ have a physical VGA connector,
will that port still be active, just with a resolution that may not be
compatible with the monitor that's plugged in?
I don't see anyone say that the DDC polling doesn't cause too much
latency for real time kernels on other systems that do have a VGA
connector... did I miss that, or is there a chance that a lot of other
systems that use this driver might also have issues with a real time kernel?
>
>
>>
>> Appreciate all the feedback on this thread.
>>
>> Thanks,
>> Jake
>
next prev parent reply other threads:[~2026-04-28 19:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 23:55 further issues with MGA G200 graphics chipset Jacob Keller
2026-04-23 0:05 ` David Airlie
2026-04-23 21:39 ` Jacob Keller
2026-04-23 7:44 ` Thomas Zimmermann
2026-04-23 16:35 ` Jacob Keller
2026-04-23 19:22 ` Jocelyn Falempe
2026-04-23 19:42 ` Jacob Keller
2026-04-23 21:02 ` David Airlie
2026-04-23 21:18 ` Jacob Keller
2026-04-24 6:16 ` Thomas Zimmermann
2026-04-24 6:20 ` Thomas Zimmermann
2026-04-24 7:36 ` Jocelyn Falempe
2026-04-24 7:47 ` Thomas Zimmermann
2026-04-24 23:29 ` Jacob Keller
2026-04-27 12:14 ` Thomas Zimmermann
2026-04-27 22:53 ` Jacob Keller
2026-04-27 23:32 ` Jacob Keller
2026-04-28 19:12 ` stuart hayes [this message]
2026-04-28 21:07 ` Jacob Keller
2026-04-29 6:40 ` Thomas Zimmermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=be1f1005-a7ed-4a5b-904b-35541b19658a@gmail.com \
--to=stuart.w.hayes@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacob.e.keller@intel.com \
--cc=jfalempe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pvaanane@redhat.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox