regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
* Re: [PATCH] matroxfb: set maxvram of vbG200eW to the same as vbG200 to avoid black screen
       [not found] <20211218180035.200552-1-liuzx@knownsec.com>
@ 2021-12-19  5:09 ` Thorsten Leemhuis
  2022-01-18  5:27   ` [PATCH] matroxfb: set maxvram of vbG200eW to the same as vbG200 to avoid black screen #forregzbot Thorsten Leemhuis
  0 siblings, 1 reply; 3+ messages in thread
From: Thorsten Leemhuis @ 2021-12-19  5:09 UTC (permalink / raw)
  To: Z. Liu; +Cc: linux-fbdev, linux-kernel, regressions

On 18.12.21 19:00, Z. Liu wrote:
> Start from commit 11be60bd66d54 "matroxfb: add Matrox MGA-G200eW board
> support", when maxvram is 0x800000, monitor become black w/ error message
> said: "The current input timing is not supported by the monitor display.
> Please change your input timing to 1920x1080@60Hz ...".
> 
> Fixes: 1be60bd66d54 ("matroxfb: add Matrox MGA-G200eW board support")
> Cc: linux-fbdev@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Z. Liu <liuzx@knownsec.com>
> ---
>  drivers/video/fbdev/matrox/matroxfb_base.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/video/fbdev/matrox/matroxfb_base.c b/drivers/video/fbdev/matrox/matroxfb_base.c
> index 5c82611e93d9..236521b19daf 100644
> --- a/drivers/video/fbdev/matrox/matroxfb_base.c
> +++ b/drivers/video/fbdev/matrox/matroxfb_base.c
> @@ -1377,7 +1377,7 @@ static struct video_board vbG200 = {
>  	.lowlevel = &matrox_G100
>  };
>  static struct video_board vbG200eW = {
> -	.maxvram = 0x800000,
> +	.maxvram = 0x100000,
>  	.maxdisplayable = 0x800000,
>  	.accelID = FB_ACCEL_MATROX_MGAG200,
>  	.lowlevel = &matrox_G100

[TLDR: I'm adding this regression to regzbot, the Linux kernel
regression tracking bot; most text you find below is compiled from a few
templates paragraphs some of you might have seen already.]

Hi, this is your Linux kernel regression tracker speaking.

Thanks for the report.

Adding the regression mailing list to the list of recipients, as it
should be in the loop for all regressions, as explained here:
https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html

To be sure this issue doesn't fall through the cracks unnoticed, I'm
adding it to regzbot, my Linux kernel regression tracking bot:

#regzbot ^introduced 11be60bd66d54
#regzbot title fbdev: matroxfb: display black ans warns "the current
input timing is not supported by the monitor display"
#regzbot ignore-activity
#regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215355

Reminder: when fixing the issue, please add a 'Link:' tag with the URL
to the report (the parent of this mail) using the kernel.org redirector,
as explained in 'Documentation/process/submitting-patches.rst'. Regzbot
then will automatically mark the regression as resolved once the fix
lands in the appropriate tree. For more details about regzbot see footer.

Sending this to everyone that got the initial report, to make all aware
of the tracking. I also hope that messages like this motivate people to
directly get at least the regression mailing list and ideally even
regzbot involved when dealing with regressions, as messages like this
wouldn't be needed then.

Don't worry, I'll send further messages wrt to this regression just to
the lists (with a tag in the subject so people can filter them away), as
long as they are intended just for regzbot. With a bit of luck no such
messages will be needed anyway.

Ciao, Thorsten (wearing his 'Linux kernel regression tracker' hat).

P.S.: As a Linux kernel regression tracker I'm getting a lot of reports
on my table. I can only look briefly into most of them. Unfortunately
therefore I sometimes will get things wrong or miss something important.
I hope that's not the case here; if you think it is, don't hesitate to
tell me about it in a public reply. That's in everyone's interest, as
what I wrote above might be misleading to everyone reading this; any
suggestion I gave thus might sent someone reading this down the wrong
rabbit hole, which none of us wants.

BTW, I have no personal interest in this issue, which is tracked using
regzbot, my Linux kernel regression tracking bot
(https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting
this mail to get things rolling again and hence don't need to be CC on
all further activities wrt to this regression.

---
Additional information about regzbot:

If you want to know more about regzbot, check out its web-interface, the
getting start guide, and/or the references documentation:

https://linux-regtracking.leemhuis.info/regzbot/
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md

The last two documents will explain how you can interact with regzbot
yourself if your want to.

Hint for reporters: when reporting a regression it's in your interest to
tell #regzbot about it in the report, as that will ensure the regression
gets on the radar of regzbot and the regression tracker. That's in your
interest, as they will make sure the report won't fall through the
cracks unnoticed.

Hint for developers: you normally don't need to care about regzbot once
it's involved. Fix the issue as you normally would, just remember to
include a 'Link:' tag to the report in the commit message, as explained
in Documentation/process/submitting-patches.rst
That aspect was recently was made more explicit in commit 1f57bd42b77c:
https://git.kernel.org/linus/1f57bd42b77c


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] matroxfb: set maxvram of vbG200eW to the same as vbG200 to avoid black screen #forregzbot
  2021-12-19  5:09 ` [PATCH] matroxfb: set maxvram of vbG200eW to the same as vbG200 to avoid black screen Thorsten Leemhuis
@ 2022-01-18  5:27   ` Thorsten Leemhuis
  2022-02-18 14:41     ` Thorsten Leemhuis
  0 siblings, 1 reply; 3+ messages in thread
From: Thorsten Leemhuis @ 2022-01-18  5:27 UTC (permalink / raw)
  To: regressions

For the record:

Below issue is fixed by:

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=0c248dc26e9031841a0beb96e3f820c50d56e5b4

#regzbot fixed-by: 0c248dc26e90318

TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.

On 19.12.21 06:09, Thorsten Leemhuis wrote:
> On 18.12.21 19:00, Z. Liu wrote:
>> Start from commit 11be60bd66d54 "matroxfb: add Matrox MGA-G200eW board
>> support", when maxvram is 0x800000, monitor become black w/ error message
>> said: "The current input timing is not supported by the monitor display.
>> Please change your input timing to 1920x1080@60Hz ...".
>>
>> Fixes: 1be60bd66d54 ("matroxfb: add Matrox MGA-G200eW board support")
>> Cc: linux-fbdev@vger.kernel.org
>> Cc: linux-kernel@vger.kernel.org
>> Signed-off-by: Z. Liu <liuzx@knownsec.com>
>> ---
>>  drivers/video/fbdev/matrox/matroxfb_base.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/video/fbdev/matrox/matroxfb_base.c b/drivers/video/fbdev/matrox/matroxfb_base.c
>> index 5c82611e93d9..236521b19daf 100644
>> --- a/drivers/video/fbdev/matrox/matroxfb_base.c
>> +++ b/drivers/video/fbdev/matrox/matroxfb_base.c
>> @@ -1377,7 +1377,7 @@ static struct video_board vbG200 = {
>>  	.lowlevel = &matrox_G100
>>  };
>>  static struct video_board vbG200eW = {
>> -	.maxvram = 0x800000,
>> +	.maxvram = 0x100000,
>>  	.maxdisplayable = 0x800000,
>>  	.accelID = FB_ACCEL_MATROX_MGAG200,
>>  	.lowlevel = &matrox_G100
> 
> [TLDR: I'm adding this regression to regzbot, the Linux kernel
> regression tracking bot; most text you find below is compiled from a few
> templates paragraphs some of you might have seen already.]
> 
> Hi, this is your Linux kernel regression tracker speaking.
> 
> Thanks for the report.
> 
> Adding the regression mailing list to the list of recipients, as it
> should be in the loop for all regressions, as explained here:
> https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html
> 
> To be sure this issue doesn't fall through the cracks unnoticed, I'm
> adding it to regzbot, my Linux kernel regression tracking bot:
> 
> #regzbot ^introduced 11be60bd66d54
> #regzbot title fbdev: matroxfb: display black ans warns "the current
> input timing is not supported by the monitor display"
> #regzbot ignore-activity
> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215355
> 
> Reminder: when fixing the issue, please add a 'Link:' tag with the URL
> to the report (the parent of this mail) using the kernel.org redirector,
> as explained in 'Documentation/process/submitting-patches.rst'. Regzbot
> then will automatically mark the regression as resolved once the fix
> lands in the appropriate tree. For more details about regzbot see footer.
> 
> Sending this to everyone that got the initial report, to make all aware
> of the tracking. I also hope that messages like this motivate people to
> directly get at least the regression mailing list and ideally even
> regzbot involved when dealing with regressions, as messages like this
> wouldn't be needed then.
> 
> Don't worry, I'll send further messages wrt to this regression just to
> the lists (with a tag in the subject so people can filter them away), as
> long as they are intended just for regzbot. With a bit of luck no such
> messages will be needed anyway.
> 
> Ciao, Thorsten (wearing his 'Linux kernel regression tracker' hat).
> 
> P.S.: As a Linux kernel regression tracker I'm getting a lot of reports
> on my table. I can only look briefly into most of them. Unfortunately
> therefore I sometimes will get things wrong or miss something important.
> I hope that's not the case here; if you think it is, don't hesitate to
> tell me about it in a public reply. That's in everyone's interest, as
> what I wrote above might be misleading to everyone reading this; any
> suggestion I gave thus might sent someone reading this down the wrong
> rabbit hole, which none of us wants.
> 
> BTW, I have no personal interest in this issue, which is tracked using
> regzbot, my Linux kernel regression tracking bot
> (https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting
> this mail to get things rolling again and hence don't need to be CC on
> all further activities wrt to this regression.
> 
> ---
> Additional information about regzbot:
> 
> If you want to know more about regzbot, check out its web-interface, the
> getting start guide, and/or the references documentation:
> 
> https://linux-regtracking.leemhuis.info/regzbot/
> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md
> 
> The last two documents will explain how you can interact with regzbot
> yourself if your want to.
> 
> Hint for reporters: when reporting a regression it's in your interest to
> tell #regzbot about it in the report, as that will ensure the regression
> gets on the radar of regzbot and the regression tracker. That's in your
> interest, as they will make sure the report won't fall through the
> cracks unnoticed.
> 
> Hint for developers: you normally don't need to care about regzbot once
> it's involved. Fix the issue as you normally would, just remember to
> include a 'Link:' tag to the report in the commit message, as explained
> in Documentation/process/submitting-patches.rst
> That aspect was recently was made more explicit in commit 1f57bd42b77c:
> https://git.kernel.org/linus/1f57bd42b77c
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] matroxfb: set maxvram of vbG200eW to the same as vbG200 to avoid black screen #forregzbot
  2022-01-18  5:27   ` [PATCH] matroxfb: set maxvram of vbG200eW to the same as vbG200 to avoid black screen #forregzbot Thorsten Leemhuis
@ 2022-02-18 14:41     ` Thorsten Leemhuis
  0 siblings, 0 replies; 3+ messages in thread
From: Thorsten Leemhuis @ 2022-02-18 14:41 UTC (permalink / raw)
  To: regressions

TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.

Fix got rebased and afaics will wait till the next merge window

#regzbot fixed-by: 62d89a7d49afe46e6b
#regzbot backburner: looks like fix will wait till the next merge window
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I'm getting a lot of
reports on my table. I can only look briefly into most of them and lack
knowledge about most of the areas they concern. I thus unfortunately
will sometimes get things wrong or miss something important. I hope
that's not the case here; if you think it is, don't hesitate to tell me
in a public reply, it's in everyone's interest to set the public record
straight.

On 18.01.22 06:27, Thorsten Leemhuis wrote:
> For the record:
> 
> Below issue is fixed by:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=0c248dc26e9031841a0beb96e3f820c50d56e5b4
> 
> #regzbot fixed-by: 0c248dc26e90318
> 
> TWIMC: this mail is primarily send for documentation purposes and for
> regzbot, my Linux kernel regression tracking bot. These mails usually
> contain '#forregzbot' in the subject, to make them easy to spot and filter.
> 
> On 19.12.21 06:09, Thorsten Leemhuis wrote:
>> On 18.12.21 19:00, Z. Liu wrote:
>>> Start from commit 11be60bd66d54 "matroxfb: add Matrox MGA-G200eW board
>>> support", when maxvram is 0x800000, monitor become black w/ error message
>>> said: "The current input timing is not supported by the monitor display.
>>> Please change your input timing to 1920x1080@60Hz ...".
>>>
>>> Fixes: 1be60bd66d54 ("matroxfb: add Matrox MGA-G200eW board support")
>>> Cc: linux-fbdev@vger.kernel.org
>>> Cc: linux-kernel@vger.kernel.org
>>> Signed-off-by: Z. Liu <liuzx@knownsec.com>
>>> ---
>>>  drivers/video/fbdev/matrox/matroxfb_base.c | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/video/fbdev/matrox/matroxfb_base.c b/drivers/video/fbdev/matrox/matroxfb_base.c
>>> index 5c82611e93d9..236521b19daf 100644
>>> --- a/drivers/video/fbdev/matrox/matroxfb_base.c
>>> +++ b/drivers/video/fbdev/matrox/matroxfb_base.c
>>> @@ -1377,7 +1377,7 @@ static struct video_board vbG200 = {
>>>  	.lowlevel = &matrox_G100
>>>  };
>>>  static struct video_board vbG200eW = {
>>> -	.maxvram = 0x800000,
>>> +	.maxvram = 0x100000,
>>>  	.maxdisplayable = 0x800000,
>>>  	.accelID = FB_ACCEL_MATROX_MGAG200,
>>>  	.lowlevel = &matrox_G100
>>
>> [TLDR: I'm adding this regression to regzbot, the Linux kernel
>> regression tracking bot; most text you find below is compiled from a few
>> templates paragraphs some of you might have seen already.]
>>
>> Hi, this is your Linux kernel regression tracker speaking.
>>
>> Thanks for the report.
>>
>> Adding the regression mailing list to the list of recipients, as it
>> should be in the loop for all regressions, as explained here:
>> https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html
>>
>> To be sure this issue doesn't fall through the cracks unnoticed, I'm
>> adding it to regzbot, my Linux kernel regression tracking bot:
>>
>> #regzbot ^introduced 11be60bd66d54
>> #regzbot title fbdev: matroxfb: display black ans warns "the current
>> input timing is not supported by the monitor display"
>> #regzbot ignore-activity
>> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215355
>>
>> Reminder: when fixing the issue, please add a 'Link:' tag with the URL
>> to the report (the parent of this mail) using the kernel.org redirector,
>> as explained in 'Documentation/process/submitting-patches.rst'. Regzbot
>> then will automatically mark the regression as resolved once the fix
>> lands in the appropriate tree. For more details about regzbot see footer.
>>
>> Sending this to everyone that got the initial report, to make all aware
>> of the tracking. I also hope that messages like this motivate people to
>> directly get at least the regression mailing list and ideally even
>> regzbot involved when dealing with regressions, as messages like this
>> wouldn't be needed then.
>>
>> Don't worry, I'll send further messages wrt to this regression just to
>> the lists (with a tag in the subject so people can filter them away), as
>> long as they are intended just for regzbot. With a bit of luck no such
>> messages will be needed anyway.
>>
>> Ciao, Thorsten (wearing his 'Linux kernel regression tracker' hat).
>>
>> P.S.: As a Linux kernel regression tracker I'm getting a lot of reports
>> on my table. I can only look briefly into most of them. Unfortunately
>> therefore I sometimes will get things wrong or miss something important.
>> I hope that's not the case here; if you think it is, don't hesitate to
>> tell me about it in a public reply. That's in everyone's interest, as
>> what I wrote above might be misleading to everyone reading this; any
>> suggestion I gave thus might sent someone reading this down the wrong
>> rabbit hole, which none of us wants.
>>
>> BTW, I have no personal interest in this issue, which is tracked using
>> regzbot, my Linux kernel regression tracking bot
>> (https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting
>> this mail to get things rolling again and hence don't need to be CC on
>> all further activities wrt to this regression.
>>
>> ---
>> Additional information about regzbot:
>>
>> If you want to know more about regzbot, check out its web-interface, the
>> getting start guide, and/or the references documentation:
>>
>> https://linux-regtracking.leemhuis.info/regzbot/
>> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
>> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md
>>
>> The last two documents will explain how you can interact with regzbot
>> yourself if your want to.
>>
>> Hint for reporters: when reporting a regression it's in your interest to
>> tell #regzbot about it in the report, as that will ensure the regression
>> gets on the radar of regzbot and the regression tracker. That's in your
>> interest, as they will make sure the report won't fall through the
>> cracks unnoticed.
>>
>> Hint for developers: you normally don't need to care about regzbot once
>> it's involved. Fix the issue as you normally would, just remember to
>> include a 'Link:' tag to the report in the commit message, as explained
>> in Documentation/process/submitting-patches.rst
>> That aspect was recently was made more explicit in commit 1f57bd42b77c:
>> https://git.kernel.org/linus/1f57bd42b77c
>>
> 
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-02-18 14:41 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20211218180035.200552-1-liuzx@knownsec.com>
2021-12-19  5:09 ` [PATCH] matroxfb: set maxvram of vbG200eW to the same as vbG200 to avoid black screen Thorsten Leemhuis
2022-01-18  5:27   ` [PATCH] matroxfb: set maxvram of vbG200eW to the same as vbG200 to avoid black screen #forregzbot Thorsten Leemhuis
2022-02-18 14:41     ` Thorsten Leemhuis

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).