dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 5 Sep 2022 08:57:34 +0200	[thread overview]
Message-ID: <44b97fac-e879-e396-b8f2-f9459a5f913c@suse.de> (raw)
In-Reply-To: <20220902135242.2447.409509F4@e16-tech.com>


[-- Attachment #1.1: Type: text/plain, Size: 2282 bytes --]

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?

Best regards
Thomas

> 
> [root@T620 ~]# dmesg  |grep -i 'vga\|mga'
> [    0.588940] Console: colour VGA+ 80x25
> [    4.918214] pci 0000:0a:00.0: vgaarb: setting as boot VGA device
> [    4.919028] pci 0000:0a:00.0: vgaarb: bridge control possible
> [    4.919028] pci 0000:0a:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
> [    4.941058] vgaarb: loaded
> [    9.385485] mgag200 0000:0a:00.0: vgaarb: deactivate vga console
> [    9.510688] [drm] Initialized mgag200 1.0.0 20110418 for 0000:0a:00.0 on minor 0
> [    9.523145] fbcon: mgag200drmfb (fb0) is primary device
> [    9.641543] mgag200 0000:0a:00.0: [drm] fb0: mgag200drmfb frame buffer device
> 
> 
> more info:
> 1, This DELL/T620 works well with kernel 5.15.63,
>      so this is not a  hardware error.
> 
> 2, DELL/T640 works well with kernel 6.0-rc and 5.15.63.
>      both DELL/T620 and DELL/T640 use the driver 'mgag200'.
> 
> [root@T640 ~]#  dmesg  |grep -i 'vga\|mga'
> [   10.161500] pci 0000:03:00.0: vgaarb: setting as boot VGA device
> [   10.162463] pci 0000:03:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
> [   10.176527] pci 0000:03:00.0: vgaarb: bridge control possible
> [   10.182465] vgaarb: loaded
> [   11.832839] fb0: EFI VGA frame buffer device
> [   21.303826] mgag200 0000:03:00.0: vgaarb: deactivate vga console
> [   21.319498] [drm] Initialized mgag200 1.0.0 20110418 for 0000:03:00.0 on minor 0
> [   21.330223] fbcon: mgag200drmfb (fb0) is primary device
> [   21.332140] mgag200 0000:03:00.0: [drm] drm_plane_enable_fb_damage_clips() not called
> [   21.741629] mgag200 0000:03:00.0: [drm] fb0: mgag200drmfb frame buffer device
> 
> Best Regards
> Wang Yugui (wangyugui@e16-tech.com)
> 2022/09/02
> 

-- 
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 --]

       reply	other threads:[~2022-09-05  6:57 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 ` Thomas Zimmermann [this message]
2022-09-07  4:16   ` mgag200 broken on kernel-6.0-rc3 on DELL/T620 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
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=44b97fac-e879-e396-b8f2-f9459a5f913c@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).