All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Helge Deller <deller@gmx.de>
Cc: "Z. Liu" <liuzx@knownsec.com>,
	linux-fbdev@vger.kernel.org, it+linux-fbdev@molgen.mpg.de,
	regressions@lists.linux.dev, stable@vger.kernel.org
Subject: Re: matroxfb: cannot determine memory size
Date: Fri, 16 Dec 2022 12:58:44 +0100	[thread overview]
Message-ID: <dc0b1487-04f9-5a2f-e0f8-d157a74b6bcb@molgen.mpg.de> (raw)
In-Reply-To: <6ef71be5-def9-4578-3f73-c43c35d7e4a9@gmx.de>

[Cc: +regressions@, +stable@]

#regzbot ^introduced: 62d89a7d49afe46e6b9bbe9e23b004ad848dbde4


Dear Helge,


Thank you for your prompt reply.

Am 16.12.22 um 00:02 schrieb Helge Deller:
> On 12/15/22 17:39, Paul Menzel wrote:

>> Between Linux 5.10.103 and 5.10.110/5.15.77, matrixfb fails to load.
>>
>> ## Working:
>>
>>      [    0.000000] Linux version 5.10.103.mx64.429 (root@theinternet.molgen.mpg.de) (gcc (GCC) 7.5.0, GNU ld (GNU Binutils) 2.37) #1 SMP Mon Mar 7 16:41:58 CET 2022
>>      [    0.000000] Command line: BOOT_IMAGE=/boot/bzImage-5.10.103.mx64.429 root=LABEL=root ro crashkernel=64G-:256M console=ttyS0,115200n8 console=tty0 init=/bin/systemd audit=0 random.trust_cpu=on systemd.unified_cgroup_hierarchy
>>      […]
>>      [    0.000000] DMI: Dell Inc. PowerEdge R910/0KYD3D, BIOS 2.10.0 08/29/2013
>>      […]
>>      [   48.045530] matroxfb: Matrox MGA-G200eW (PCI) detected
>>      [   48.054675] matroxfb: 640x480x8bpp (virtual: 640x13107)
>>      [   48.059966] matroxfb: framebuffer at 0xC5000000, mapped to 0x00000000ca7238fa, size 8388608
>>
>> ## Non-working:
>>
>> ### 5.10.110
>>
>>      [    0.000000] Linux version 5.10.110.mx64.433 (root@theinternet.molgen.mpg.de) (gcc (GCC) 7.5.0, GNU ld (GNU 
>> Binutils) 2.37) #1 SMP Thu Apr 14 15:28:53 CEST 2022
>>      [    0.000000] Command line: root=LABEL=root ro crashkernel=64G-:256M console=ttyS0,115200n8 console=tty0 init=/bin/systemd audit=0 random.trust_cpu=on systemd.unified_cgroup_hierarchy
>>      […]
>>      [    0.000000] DMI: Dell Inc. PowerEdge R910/0KYD3D, BIOS 2.10.0 08/29/2013
>>      […]
>>      [   35.225987] matroxfb: Matrox MGA-G200eW (PCI) detected
>>      [   35.234088] matroxfb: cannot determine memory size
>>      [   35.238931] matroxfb: probe of 0000:09:03.0 failed with error -1
>>
>> ### 5.15.77
>>
>>      [    0.000000] Linux version 5.15.77.mx64.440 (root@theinternet.molgen.mpg.de) (gcc (GCC) 10.4.0, GNU ld (GNU Binutils) 2.37) #1 SMP Tue Nov 8 15:42:33 CET 2022
>>      [    0.000000] Command line: root=LABEL=root ro crashkernel=64G-:256M console=ttyS0,115200n8 console=tty0 init=/bin/systemd audit=0 random.trust_cpu=on systemd.unified_cgroup_hierarchy
>>      […]
>>      [    0.000000] DMI: Dell Inc. PowerEdge R715/0G2DP3, BIOS 1.5.2 04/19/2011
>>      […]
>>      [    9.436420] matroxfb: Matrox MGA-G200eW (PCI) detected
>>      [    9.444502] matroxfb: cannot determine memory size
>>      [    9.449316] matroxfb: probe of 0000:0a:03.0 failed with error -1
>>
>> We see it on several systems:
>>
>>      $ lspci -nn -s 0a:03.0 # Dell PowerEdge R715
>>      0a:03.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
>>
>>      $ lspci -nn -s 09:03.0 # Dell PowerEdge R910
>>      09:03.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a)
>>
>> I found some old log from April 2022, where I booted 5.10.109, and the 
>> error is not there, pointing toward the regression to be introduced 
>> between 5.10.109 and 5.10.110.
>>
>> ```
>> $ git log --oneline v5.10.109..v5.10.110 --grep fbdev

[…]

>> ```
>>
>> Is it worthwhile to test commit f8bf19f7f311 (video: fbdev: matroxfb: 
>> set maxvram of vbG200eW to the same as vbG200 to avoid black screen)?
> 
> Yes, it is.
> Please try and report back.
> It seems to be the only relevant patch, and it fits with the name of 
> your card.

I tested Linus’ master with commit 84e57d292203 (Merge tag 
'exfat-for-6.2-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/exfat) and the 
error is still there. Reverting commit fixes the issue.

Tested on:

     DMI: Dell Inc. PowerEdge R910/0KYD3D, BIOS 2.10.0 08/29/2013

Current master:

     [   36.221595] matroxfb 0000:09:03.0: vgaarb: deactivate vga console
     [   36.228355] Console: switching to colour dummy device 80x25
     [   36.234069] matroxfb: Matrox MGA-G200eW (PCI) detected
     [   36.239316] PInS memtype = 7
     [   36.242198] matroxfb: cannot determine memory size
     [   36.242209] matroxfb: probe of 0000:09:03.0 failed with error -1

After reverting 62d89a7d49af (video: fbdev: matroxfb: set maxvram of 
vbG200eW to the same as vbG200 to avoid black screen):

     [   38.140763] matroxfb 0000:09:03.0: vgaarb: deactivate vga console
     [   38.148057] Console: switching to colour dummy device 80x25
     [   38.153789] matroxfb: Matrox MGA-G200eW (PCI) detected
     [   38.159042] PInS memtype = 7
     [   38.161953] matroxfb: 640x480x8bpp (virtual: 640x13107)
2022-12-16T12:26:11.301999+01:00 invidia kernel: [   38.167175] 
matroxfb: framebuffer at 0xC5000000, mapped to 0x000000006f41c38c, size 
8388608

>> The master commit 62d89a7d49a was added to v5.18-rc1, and was also 
>> backported to the Linux 5.15 series in 5.15.33.


Kind regards,

Paul

  reply	other threads:[~2022-12-16 11:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 16:39 matroxfb: cannot determine memory size Paul Menzel
2022-12-15 23:02 ` Helge Deller
2022-12-16 11:58   ` Paul Menzel [this message]
2022-12-16 21:21     ` Helge Deller
2022-12-19 11:58       ` Paul Menzel
2022-12-19 12:19         ` Helge Deller
2023-02-16 12:50     ` Linux regression tracking #update (Thorsten Leemhuis)
2022-12-16 12:27 ` Thomas Zimmermann
2022-12-16 13:16   ` Why is mgag200 not used over matroxfb? (was: matroxfb: cannot determine memory size) Paul Menzel
2023-01-03 16:20     ` Why is mgag200 not used over matroxfb? Paul Menzel
2023-01-04  8:19       ` 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=dc0b1487-04f9-5a2f-e0f8-d157a74b6bcb@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=deller@gmx.de \
    --cc=it+linux-fbdev@molgen.mpg.de \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=liuzx@knownsec.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.