regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: PGNet Dev <pgnet.dev@gmail.com>
To: stable@vger.kernel.org
Cc: regressions@lists.linux.dev
Subject: boot of J1900 (quad-core Celeron) mobo: kernel <= 5.12.15, OK; kernel >= 5.12.17, 5.13.4, slow boot (>> 660 secs) + hang/FAIL
Date: Thu, 22 Jul 2021 17:10:02 -0400	[thread overview]
Message-ID: <5b5d1b7f-7327-52a2-5221-de39206a07a3@gmail.com> (raw)

My servers run Fedora 34, with latest kernels.

Updating to any of minimally- or un- patched 5.12.17 or 5.13.4 hangs/fails, as follows.

On just one server , an old ASRockRack J1900D2Y (quad-core Celeron) motherboard build,

	hwinfo --bios
		01: None 00.0: 10105 BIOS
		  [Created at bios.186]
		  Unique ID: rdCR.lZF+r4EgHp4
		  Hardware Class: bios
		  BIOS Keyboard LED Status:
		    Scroll Lock: off
		    Num Lock: off
		    Caps Lock: off
		  Serial Port 0: 0x3f8
		  Base Memory: 626 kB
		  PnP BIOS: @@@0000
		  MP spec rev 1.4 info:
		    OEM id: "A M I"
		    Product id: "ALASKA"
		    4 CPUs (0 disabled)
		  SMBIOS Version: 2.8
		  BIOS Info: #0
		    Vendor: "American Megatrends Inc."
		    Version: "P1.10"
		    Date: "01/23/2015"
		    Start Address: 0xf0000
		    ROM Size: 8192 kB
		    Features: 0x0d03000000013f8b9880
		      PCI supported
		      BIOS flashable
		      BIOS shadowing allowed
		      CD boot supported
		      Selectable boot supported
		      BIOS ROM socketed
		      EDD spec supported
		      1.2MB Floppy supported
		      720kB Floppy supported
		      2.88MB Floppy supported
		      Print Screen supported
		      8042 Keyboard Services supported
		      Serial Services supported
		      Printer Services supported
		      ACPI supported
		      USB Legacy supported
		      BIOS Boot Spec supported
		  System Info: #1
		    Manufacturer: "To Be Filled By O.E.M."
		    Product: "To Be Filled By O.E.M."
		    Version: "To Be Filled By O.E.M."
		    Serial: "To Be Filled By O.E.M."
		    UUID: 03000200-0400-0500-0006-000700080009
		    Wake-up: 0x06 (Power Switch)
		  Board Info: #2
		    Manufacturer: "ASRock"
		    Product: "J1900D2Y"
		    Type: 0x0a (Motherboard)
		    Features: 0x09
		      Hosting Board
		      Replaceable
		    Chassis: #3
		...

with Fedora34 Kernel <=

	Fedora (5.12.15-300.fc34.x86_64) 34 (Thirty Four)

the box boots/runs OK,

	[    0.000000] microcode: microcode updated early to revision 0x838, date = 2019-04-22
	[    0.000000] Linux version 5.12.15-300.fc34.x86_64 (mockbuild@bkernel01.iad2.fedoraproject.org) (gcc (GCC) 11.1.1 20210531 (Red Hat 11.1.1-3), GNU ld version 2.35.1-41.fc34) #1 SMP Wed Jul 7 19:46:50 UTC 2021
	[    0.000000] Command line: BOOT_IMAGE=(mduuid/5687b25f8f25671a243a83cb661f7841)/vmlinuz-5.12.15-300.fc34.x86_64 root=/dev/mapper/VG0-LV_ROOT ro i915.modeset=1 vconsole.keymap=us vconsole.font=eurlatgr vconsole.font_map=trivial domdadm_
	[    0.000000] x86/fpu: x87 FPU will use FXSAVE
	[    0.000000] BIOS-provided physical RAM map:
	[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
	[    0.000000] BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
	[    0.000000] BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
	[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
	[    0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000200fffff] reserved
	[    0.000000] BIOS-e820: [mem 0x0000000020100000-0x000000006d66cfff] usable
	[    0.000000] BIOS-e820: [mem 0x000000006d66d000-0x000000006d69cfff] reserved
	[    0.000000] BIOS-e820: [mem 0x000000006d69d000-0x000000006d6acfff] ACPI data
	[    0.000000] BIOS-e820: [mem 0x000000006d6ad000-0x000000006d7f1fff] ACPI NVS
	[    0.000000] BIOS-e820: [mem 0x000000006d7f2000-0x000000006db80fff] reserved
	[    0.000000] BIOS-e820: [mem 0x000000006db81000-0x000000006db81fff] usable
	[    0.000000] BIOS-e820: [mem 0x000000006db82000-0x000000006dbc3fff] reserved
	[    0.000000] BIOS-e820: [mem 0x000000006dbc4000-0x000000006dd31fff] usable
	[    0.000000] BIOS-e820: [mem 0x000000006dd32000-0x000000006dff9fff] reserved
	[    0.000000] BIOS-e820: [mem 0x000000006dffa000-0x000000006dffffff] usable
	[    0.000000] BIOS-e820: [mem 0x00000000e00f8000-0x00000000e00f8fff] reserved
	[    0.000000] BIOS-e820: [mem 0x00000000fed01000-0x00000000fed01fff] reserved
	[    0.000000] BIOS-e820: [mem 0x00000000ffb00000-0x00000000ffffffff] reserved
	[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000047fffffff] usable
	[    0.000000] printk: console [earlyser0] enabled
	Memory KASLR using RDRAND RDTSC...
	Poking KASLR using RDRAND RDTSC...

	Welcome to Fedora 34 (Thirty Four) dracut-055-3.fc34 (Initramfs)!

	[  OK  ] Started Dispatch Password …ts to Console Directory Watch.
	[  OK  ] Reached target Local File Systems.
	[  OK  ] Reached target Path Units.
	...
	Fedora 34 (Thirty Four)
	Kernel 5.12.15-300.fc34.x86_64 on an x86_64 (ttyS0)

	srv01 login:
	...
	lsb_release -rd
		Description:    Fedora release 34 (Thirty Four)
		Release:        34
	uname -rm
		5.12.15-300.fc34.x86_64 x86_64

updating to any of minimally- or un- patched,

	Fedora (5.12.17-300.fc34.x86_64) 34 (Thirty Four)
		https://koji.fedoraproject.org/koji/buildinfo?buildID=1780670

	Fedora (5.13.4-200.fc34.x86_64) 34 (Thirty Four)
		https://koji.fedoraproject.org/koji/buildinfo?buildID=1782334

	Fedora (5.13.4-250.vanilla.1.fc34.x86_64) 34 (Thirty Four)
	    https://fedoraproject.org/wiki/Kernel_Vanilla_Repositories
	    https://repos.fedorapeople.org/repos/thl/kernel-vanilla-stable/fedora-34/x86_64/
		https://fedorapeople.org/cgit/thl/public_git/kernel.git/tree/?h=kernel-5.13.3-250.vanilla.1.fc34

and re-gen'ing initrd, system boot hangs early in each case,


	[    0.000000] microcode: microcode updated early to revision 0x838, date = 2019-04-22
	[    0.000000] Linux version 5.13.4-200.fc34.x86_64 (mockbuild@bkernel01.iad2.fedoraproject.org) (gcc (GCC) 11.1.1 20210531 (Red Hat 11.1.1-3), GNU ld version 2.35.1-41.fc34) #1 SMP Tue Jul 20 20:27:29 UTC 2021
	[    0.000000] Command line: BOOT_IMAGE=(mduuid/5687b25f8f25671a243a83cb661f7841)/vmlinuz-5.13.4-200.fc34.x86_64 root=/dev/mapper/VG0-LV_ROOT ro i915.modeset=1 vconsole.keymap=us vconsole.font=eurlatgr vconsole.font_map=trivial domdadm b
	[    0.000000] x86/fpu: x87 FPU will use FXSAVE
	[    0.000000] BIOS-provided physical RAM map:
	[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
	[    0.000000] BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
	[    0.000000] BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
	[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
	[    0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000200fffff] reserved
	[    0.000000] BIOS-e820: [mem 0x0000000020100000-0x000000006d66cfff] usable
	[    0.000000] BIOS-e820: [mem 0x000000006d66d000-0x000000006d69cfff] reserved
	[    0.000000] BIOS-e820: [mem 0x000000006d69d000-0x000000006d6acfff] ACPI data
	[    0.000000] BIOS-e820: [mem 0x000000006d6ad000-0x000000006d7f1fff] ACPI NVS
	[    0.000000] BIOS-e820: [mem 0x000000006d7f2000-0x000000006db80fff] reserved
	[    0.000000] BIOS-e820: [mem 0x000000006db81000-0x000000006db81fff] usable
	[    0.000000] BIOS-e820: [mem 0x000000006db82000-0x000000006dbc3fff] reserved
	[    0.000000] BIOS-e820: [mem 0x000000006dbc4000-0x000000006dd31fff] usable
	[    0.000000] BIOS-e820: [mem 0x000000006dd32000-0x000000006dff9fff] reserved
	[    0.000000] BIOS-e820: [mem 0x000000006dffa000-0x000000006dffffff] usable
	[    0.000000] BIOS-e820: [mem 0x00000000e00f8000-0x00000000e00f8fff] reserved
	[    0.000000] BIOS-e820: [mem 0x00000000fed01000-0x00000000fed01fff] reserved
	[    0.000000] BIOS-e820: [mem 0x00000000ffb00000-0x00000000ffffffff] reserved
	[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000047fffffff] usable
	[    0.000000] printk: console [earlyser0] enabled
	Memory KASLR using RDRAND RDTSC...
	Poking KASLR using RDRAND RDTSC...

, and proceeds no further.

drop-back to

	Fedora (5.12.15-300.fc34.x86_64) 34 (Thirty Four)

boots, again, with no issues.

for the

	Fedora (5.13.4-200.fc34.x86_64) 34 (Thirty Four)

case, with logging dialed up,

logs show a sloooooow boot process ( 700+ seconds and counting ), with eventual, complete hang @

	"Starting Apply Kernel Variables..."

--> https://pastebin.com/dP6Lm84J

So far, this occurs on this J1900 box only; other-hardware F34 installs with kernel >= 5.12.17 are booting fine.

AND, for _this_ J1900, all kernels <= 5.12.15 boot OK.



if there's specific, additional logging that'd be informative, I can attach.

             reply	other threads:[~2021-07-22 21:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22 21:10 PGNet Dev [this message]
2021-07-23  7:01 ` boot of J1900 (quad-core Celeron) mobo: kernel <= 5.12.15, OK; kernel >= 5.12.17, 5.13.4, slow boot (>> 660 secs) + hang/FAIL Greg KH
2021-07-23 13:22   ` PGNet Dev
2021-07-24 15:30     ` PGNet Dev

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=5b5d1b7f-7327-52a2-5221-de39206a07a3@gmail.com \
    --to=pgnet.dev@gmail.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 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).