From: Baoquan He <bhe@redhat.com>
To: airlied@redhat.com
Cc: dyoung@redhat.com, x86@kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: mgag200 fails kdump kernel booting
Date: Wed, 26 Jun 2019 16:29:07 +0800 [thread overview]
Message-ID: <20190626082907.GY24419@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20190626081522.GX24419@MiWiFi-R3L-srv>
On 06/26/19 at 04:15pm, Baoquan He wrote:
> Hi Dave,
>
> We met an kdump kernel boot failure on a lenovo system. Kdump kernel
> failed to boot, but just reset to firmware to reboot system. And nothing
> is printed out.
>
> The machine is a big server, with 6T memory and many cpu, its graphic
> driver module is mgag200.
>
> When added 'earlyprintk=ttyS0' into kernel command line, it printed
> out only one line to console during kdump kernel booting:
> KASLR disabled: 'nokaslr' on cmdline.
>
> Then reset to firmware to reboot system.
>
> By further code debugging, the failure happened in
> arch/x86/boot/compressed/misc.c, during kernel decompressing stage. It's
> triggered by the vga printing. As you can see, in __putstr() of
> arch/x86/boot/compressed/misc.c, the code checks if earlyprintk= is
> specified, and print out to the target. And no matter if earlyprintk= is
> added or not, it will print to VGA. And printing to VGA caused it to
> reset to firmware. That's why we see nothing when didn't specify
> earlyprintk=, but see only one line of printing about the 'KASLR
> disabled'.
Here I mean:
That's why we see nothing when didn't specify earlyprintk=, but see only
one line of printing about the 'KASLR disabled' message when
earlyprintk=ttyS0 added.
>
> To confirm it's caused by VGA printing, I blacklist the mgag200 by
> writting it into /etc/modprobe.d/blacklist.conf. The kdump kernel can
> boot up successfully. And add 'nomodeset' can also make it work. So it's
> for sure mgag driver or related code have something wrong when booting
> code tries to re-init it.
>
> This is the only case we ever see, tend to pursuit fix in mgag200 driver
> side. Any idea or suggestion? We have two machines to be able to
> reproduce it stablly.
>
> Thanks
> Baoquan
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: airlied@redhat.com
Cc: kexec@lists.infradead.org, x86@kernel.org,
linux-kernel@vger.kernel.org, dyoung@redhat.com
Subject: Re: mgag200 fails kdump kernel booting
Date: Wed, 26 Jun 2019 16:29:07 +0800 [thread overview]
Message-ID: <20190626082907.GY24419@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20190626081522.GX24419@MiWiFi-R3L-srv>
On 06/26/19 at 04:15pm, Baoquan He wrote:
> Hi Dave,
>
> We met an kdump kernel boot failure on a lenovo system. Kdump kernel
> failed to boot, but just reset to firmware to reboot system. And nothing
> is printed out.
>
> The machine is a big server, with 6T memory and many cpu, its graphic
> driver module is mgag200.
>
> When added 'earlyprintk=ttyS0' into kernel command line, it printed
> out only one line to console during kdump kernel booting:
> KASLR disabled: 'nokaslr' on cmdline.
>
> Then reset to firmware to reboot system.
>
> By further code debugging, the failure happened in
> arch/x86/boot/compressed/misc.c, during kernel decompressing stage. It's
> triggered by the vga printing. As you can see, in __putstr() of
> arch/x86/boot/compressed/misc.c, the code checks if earlyprintk= is
> specified, and print out to the target. And no matter if earlyprintk= is
> added or not, it will print to VGA. And printing to VGA caused it to
> reset to firmware. That's why we see nothing when didn't specify
> earlyprintk=, but see only one line of printing about the 'KASLR
> disabled'.
Here I mean:
That's why we see nothing when didn't specify earlyprintk=, but see only
one line of printing about the 'KASLR disabled' message when
earlyprintk=ttyS0 added.
>
> To confirm it's caused by VGA printing, I blacklist the mgag200 by
> writting it into /etc/modprobe.d/blacklist.conf. The kdump kernel can
> boot up successfully. And add 'nomodeset' can also make it work. So it's
> for sure mgag driver or related code have something wrong when booting
> code tries to re-init it.
>
> This is the only case we ever see, tend to pursuit fix in mgag200 driver
> side. Any idea or suggestion? We have two machines to be able to
> reproduce it stablly.
>
> Thanks
> Baoquan
next prev parent reply other threads:[~2019-06-26 8:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 8:15 mgag200 fails kdump kernel booting Baoquan He
2019-06-26 8:15 ` Baoquan He
2019-06-26 8:29 ` Baoquan He [this message]
2019-06-26 8:29 ` Baoquan He
2019-07-01 20:51 ` David Airlie
2019-07-01 20:51 ` David Airlie
2019-07-02 1:41 ` Baoquan He
2019-07-02 1:41 ` Baoquan He
2019-07-02 3:17 ` Dave Young
2019-07-02 3:17 ` Dave Young
2019-07-02 5:34 ` Baoquan He
2019-07-02 5:34 ` Baoquan He
2019-07-02 7:42 ` Dave Young
2019-07-02 7:42 ` Dave Young
2020-02-05 7:31 ` Baoquan He
2019-07-02 2:21 ` Dave Young
2019-07-02 2:21 ` Dave Young
2019-07-02 2:47 ` Baoquan He
2019-07-02 2:47 ` Baoquan He
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=20190626082907.GY24419@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=airlied@redhat.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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.