All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Lyude Paul <lyude@redhat.com>,
	Jocelyn Falempe <jfalempe@redhat.com>,
	dri-devel@lists.freedesktop.org
Cc: michel@daenzer.net
Subject: Re: [PATCH] mgag200 fix memmapsl configuration in GCTL6 register
Date: Wed, 19 Jan 2022 09:16:51 +0100	[thread overview]
Message-ID: <4dbe5421-73bb-e22d-3f8a-28578fffc55f@suse.de> (raw)
In-Reply-To: <8e2fed4af467f335def97232abbc22d86aff0617.camel@redhat.com>


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

Hi

Am 18.01.22 um 20:06 schrieb Lyude Paul:
> We should probably  Cc: stable@vger.kernel.org this as well, see:
> 
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html for
> more info. As well, some useful tools for adding the appropriate Fixes: tags:
> 
> https://drm.pages.freedesktop.org/maintainer-tools/dim.html
> 
> At least on my end this is:
> 
> Acked-by: Lyude Paul <lyude@redhat.com>
> 
> I'd very much like Thomas Zimmerman to verify that this patch is OK though
> with an R-b before we push anything upstream.

Yep, I'll give it a try on my test system. I'll also add a TODO comment 
that summarizes the situation.

A real fix would detect that the kdump kernel is running and not use the 
display then.

Best regards
Thomas

> 
> On Fri, 2022-01-14 at 10:47 +0100, Jocelyn Falempe wrote:
>> On some server with MGA G200e (rev 42), booting with Legacy BIOS,
>> The hardware hangs when using kdump and kexec into the kdump kernel.
>> This happens when the uncompress code tries to write "Decompressing Linux"
>> to the VGA Console.
>>
>> It can be reproduced by writing to the VGA console (0xB8000) after
>> booting to graphic mode, it generates the following error:
>>
>> kernel:NMI: PCI system error (SERR) for reason a0 on CPU 0.
>> kernel:Dazed and confused, but trying to continue
>>
>> The root cause is a bad configuration of the MGA GCTL6 register
>>
>> According to the GCTL6 register documentation:
>>
>> bit 0 is gcgrmode:
>>      0: Enables alpha mode, and the character generator addressing system is
>> activated.
>>      1: Enables graphics mode, and the character addressing system is not
>> used.
>>
>> bit 1 is chainodd even:
>>      0: The A0 signal of the memory address bus is used during system memory
>>      addressing.
>>      1: Allows A0 to be replaced by either the A16 signal of the system
>> address (if
>>      memmapsl is ‘00’), or by the hpgoddev (MISC<5>, odd/even page select)
>> field,
>>      described on page 3-294).
>>
>> bit 3-2 are memmapsl:
>>      Memory map select bits 1 and 0. VGA.
>>      These bits select where the video memory is mapped, as shown below:
>>          00 => A0000h - BFFFFh
>>          01 => A0000h - AFFFFh
>>          10 => B0000h - B7FFFh
>>          11 => B8000h - BFFFFh
>>
>> bit 7-4 are reserved.
>>
>> Current driver code set it to 0x05 => memmapsl to b01 => 0xA0000
>> but on x86, the VGA console is at 0xB8000
>> arch/x86/boot/compressed/misc.c define vidmem to 0xb8000 in extract_kernel()
>> so it's better to configure it to b11
>> Thus changing the value 0x05 to 0x0d
>>
>> Signed-off-by: Jocelyn Falempe <jfalempe@redhat.com>
>> ---
>>   drivers/gpu/drm/mgag200/mgag200_mode.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/mgag200/mgag200_mode.c
>> b/drivers/gpu/drm/mgag200/mgag200_mode.c
>> index b983541a4c53..c7f63610b278 100644
>> --- a/drivers/gpu/drm/mgag200/mgag200_mode.c
>> +++ b/drivers/gpu/drm/mgag200/mgag200_mode.c
>> @@ -529,7 +529,7 @@ static void mgag200_set_format_regs(struct mga_device
>> *mdev,
>>          WREG_GFX(3, 0x00);
>>          WREG_GFX(4, 0x00);
>>          WREG_GFX(5, 0x40);
>> -       WREG_GFX(6, 0x05);
>> +       WREG_GFX(6, 0x0d);
>>          WREG_GFX(7, 0x0f);
>>          WREG_GFX(8, 0x0f);
>>   
> 

-- 
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-01-19  8:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14  9:47 mgag200 fix memmapsl configuration in GCTL6 register Jocelyn Falempe
2022-01-14  9:47 ` [PATCH] " Jocelyn Falempe
2022-01-18 16:38   ` Javier Martinez Canillas
2022-01-18 16:52     ` Jocelyn Falempe
2022-01-18 17:17       ` Javier Martinez Canillas
2022-01-18 17:25         ` Jocelyn Falempe
2022-01-18 19:06   ` Lyude Paul
2022-01-19  8:16     ` Thomas Zimmermann [this message]
2022-01-19 10:29 ` [PATCH v2] " Jocelyn Falempe
2022-01-19 10:29   ` Jocelyn Falempe
2022-01-19 12:21   ` Thomas Zimmermann
2022-01-19 12:21     ` Thomas Zimmermann
2022-01-19 14:55     ` Thomas Zimmermann
2022-01-19 14:55       ` 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=4dbe5421-73bb-e22d-3f8a-28578fffc55f@suse.de \
    --to=tzimmermann@suse.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jfalempe@redhat.com \
    --cc=lyude@redhat.com \
    --cc=michel@daenzer.net \
    /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.