Message ID | 03e799c6-a0f3-eccf-882d-78205e9335ad@redhat.com (mailing list archive) |
---|---|
State | Not Applicable, archived |
Headers | show |
On Mon, Feb 12, 2018 at 10:18:06AM -0500, Prarit Bhargava wrote: > > But when I specify "earlyprintk=serial,ttyS0,115200" this SPCR crud will > > not interfere? > > > > I tested "earlyprintk=serial,ttyS0,115200" on a system which is known to have a > functional console with "console=ttyS0,1152008N1" both with and without > CONFIG_ACPI_SPCR_TABLE enabled. OK, but my point was that SPCR will never override explicit earlyprintk stuff. There is absolutely nothing worse than breaking working setups.
On 02/12/2018 10:44 AM, Peter Zijlstra wrote: > On Mon, Feb 12, 2018 at 10:18:06AM -0500, Prarit Bhargava wrote: >>> But when I specify "earlyprintk=serial,ttyS0,115200" this SPCR crud will >>> not interfere? >>> >> >> I tested "earlyprintk=serial,ttyS0,115200" on a system which is known to have a >> functional console with "console=ttyS0,1152008N1" both with and without >> CONFIG_ACPI_SPCR_TABLE enabled. > > OK, but my point was that SPCR will never override explicit earlyprintk > stuff. There is absolutely nothing worse than breaking working setups. > Oh, I see. SPCR will not override earlyprintk config. P.
diff of boot logs: --- earlyprintk_no_spcr_enable 2018-02-12 10:11:00.477288423 -0500 +++ earlyprintk_spcr_enable 2018-02-12 10:16:02.282574797 -0500 @@ -1,5 +1,5 @@ microcode: microcode updated early to revision 0x2000035, date = 2017-10-17 -Linux version 4.15.0+ (root@intel-purley-lr-02.khw.lab.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC)) #5 SMP Mon Feb 12 10:06:08 EST 2018 +Linux version 4.15.0+ (root@intel-purley-lr-02.khw.lab.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC)) #6 SMP Mon Feb 12 10:11:42 EST 2018 Command line: BOOT_IMAGE=/vmlinuz-4.15.0+