From: Thomas Zimmermann <tzimmermann@suse.de>
To: Wang Yugui <wangyugui@e16-tech.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: mgag200 broken on kernel-6.0-rc3 on DELL/T620
Date: Wed, 7 Sep 2022 11:18:01 +0200 [thread overview]
Message-ID: <149574f2-6dcf-f1bb-c7dc-3d6edaf52ef0@suse.de> (raw)
In-Reply-To: <20220907164723.CD41.409509F4@e16-tech.com>
[-- Attachment #1.1: Type: text/plain, Size: 1925 bytes --]
Hi
Am 07.09.22 um 10:47 schrieb Wang Yugui:
> Hi,
>
>> Am 07.09.22 um 09:38 schrieb Wang Yugui:
>>> Hi,
>>>
>>>
>>>> Hi
>>>>
>>>> Am 07.09.22 um 06:16 schrieb Wang Yugui:
>>>>> Hi,
>>>>>
>>>>>> Am 02.09.22 um 07:52 schrieb Wang Yugui:
>>>>>>> Hi,
>>>>>>>
>>>>>>> mgag200 broken on kernel-6.0-rc3 on DELL/T620.
>>>>>>>
>>>>>>> See the attachementment file for the graph output.
>>>>>>
>>>>>> Thanks for reporting the bug. We recently refactored some code of the driver. Can you bisect to the change that introduced the problem?
>>>>>
>>>>> 5.19.3 works well on this DELL/T620.
>>>>>
>>>>> so this problem should be a regression of 6.0.
>>>>>
>>>>> other bisect seem difficult for me.
>>>>
>>>> OK, thank you. Can you provide the dmesg log of the broken machine and the output of 'sudo lspci -vn' please?
>>>
>>> please see the attachment file for the output of 'lspci -vn'.
>>
>> 0a:00.0 0300: 102b:0534 (prog-if 00 [VGA controller])
>>
>> It's the G200ER. I'll try to find related code that we recently changed. I might get back to you for testing a patch. Thanks so far.
>
> the patch based on kernel 6.0(rc4) will be easy to build and test here.
>
> By the way, this problem happen on DELL/T630 too.
> but it does not happen on DELL/T640.
>
> please see the attachment file for the output of 'lspci -vn' on
> DELL/T630 and DELL/T640.
Thanks a lot, again. According to these files, the T630 also has a
G200ER, but the T640 has a G200EW3. As I said, we recently refactored
the driver. The G200ER is somehow different now. I'll get back to you as
soon as I find something.
Best regards
Thomas
>
> Best Regards
> Wang Yugui (wangyugui@e16-tech.com)
> 2022/09/07
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-09-07 9:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220902135242.2447.409509F4@e16-tech.com>
2022-09-05 6:57 ` mgag200 broken on kernel-6.0-rc3 on DELL/T620 Thomas Zimmermann
2022-09-07 4:16 ` Wang Yugui
2022-09-07 6:47 ` Thomas Zimmermann
2022-09-07 7:38 ` Wang Yugui
2022-09-07 7:55 ` Thomas Zimmermann
2022-09-07 8:47 ` Wang Yugui
2022-09-07 9:18 ` Thomas Zimmermann [this message]
2022-09-13 8:34 ` Thomas Zimmermann
2022-09-13 14:25 ` Wang Yugui
2022-09-13 14:44 ` Thomas Zimmermann
2022-09-13 15:15 ` Wang Yugui
2022-09-14 7:59 ` Thomas Zimmermann
2022-09-14 8:29 ` Wang Yugui
2022-09-14 14:36 ` Thomas Zimmermann
2022-09-14 14:58 ` Wang Yugui
2022-09-14 15:41 ` Thomas Zimmermann
2022-09-14 16:25 ` Wang Yugui
2022-09-15 12:54 ` Thomas Zimmermann
2022-09-15 14:41 ` Wang Yugui
2022-09-20 7:57 ` Thomas Zimmermann
2022-09-20 9:02 ` Wang Yugui
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=149574f2-6dcf-f1bb-c7dc-3d6edaf52ef0@suse.de \
--to=tzimmermann@suse.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=wangyugui@e16-tech.com \
/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;
as well as URLs for NNTP newsgroup(s).