From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 203839] New: Kernel 5.2-rc3 fails to boot on a PowerMac G4 3, 6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument
Date: Fri, 07 Jun 2019 00:00:52 +0000 [thread overview]
Message-ID: <bug-203839-206035@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=203839
Bug ID: 203839
Summary: Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6:
systemd[1]: Failed to bump fs.file-max, ignoring:
invalid argument
Product: Platform Specific/Hardware
Version: 2.5
Kernel Version: 5.2-rc3
Hardware: PPC-32
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: PPC-32
Assignee: platform_ppc-32@kernel-bugs.osdl.org
Reporter: erhard_f@mailbox.org
Regression: No
Created attachment 283135
--> https://bugzilla.kernel.org/attachment.cgi?id=283135&action=edit
failed boot, screenshot 5.2-rc3
The system boots fine with kernel 5.1.7. Starting with 5.2-rc1 the G4 got
problems to correctly finish booting. With 5.2-rc3 basic boot process seems to
complete, but crashes when handing control over to systemd:
systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument
systemd[1]: segfault (11) at 0 nip 0 ir 0 code 1
systemd[1]: Bad NIP, not dumping instructions
[...]
For more details see the screenshot. Kernel 5.2-rc1 errors out even earlier
(see screenshot) with a different error. Also this problem maybe is 32bit
specific. Tried 5.2-rc3 on a PowerMac G5 which boots successfully without
problems.
root is ext4, boot is ext2, systemd is v241.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2019-06-07 0:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 0:00 bugzilla-daemon [this message]
2019-06-07 0:01 ` [Bug 203839] Kernel 5.2-rc3 fails to boot on a PowerMac G4 3,6: systemd[1]: Failed to bump fs.file-max, ignoring: invalid argument bugzilla-daemon
2019-06-07 0:03 ` bugzilla-daemon
2019-06-07 10:29 ` Christophe Leroy
2019-06-07 10:29 ` bugzilla-daemon
2019-06-08 13:45 ` bugzilla-daemon
2019-06-09 7:20 ` bugzilla-daemon
2019-06-11 0:32 ` bugzilla-daemon
2019-06-11 0:34 ` bugzilla-daemon
2019-06-11 7:25 ` bugzilla-daemon
2019-06-11 10:34 ` bugzilla-daemon
2019-07-06 0:51 ` bugzilla-daemon
2019-07-08 14:15 ` bugzilla-daemon
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=bug-203839-206035@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).