Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1282392
Summary: | systemd 227 gives non-bootable system | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Marcin Juszkiewicz <mjuszkie> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | johannbg, jsynacek, lnykryn, mjuszkie, msekleta, rjones, s, systemd-maint, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | aarch64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-19 14:01:49 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 922257 |
Description
Marcin Juszkiewicz
2015-11-16 09:57:02 UTC
226-3 works This is probably the unaligned access issue in systemd's siphash24 implementation. Upstream bug, https://github.com/systemd/systemd/pull/1911. Applied patches from that pull and crashed: [ OK ] Reached target Switch Root. Starting Switch Root... [ 11.020105] systemd-journald[184]: Received SIGTERM from PID 1 (systemd). [ 12.229563] systemd[1]: Successfully loaded SELinux policy in 444.093ms. [ 12.439438] systemd[1]: Relabelled /dev and /run in 82.324ms. [ 12.482944] systemd[1]: unhandled level 0 translation fault (11) at 0x6aa696d8a70, esr 0x92000004 [ 12.491792] pgd = fffffe03d6ef0000 [ 12.495183] [6aa696d8a70] *pgd=0000000000000000, *pud=0000000000000000, *pmd=0000000000000000 [ 12.503712] [ 12.505201] CPU: 0 PID: 1 Comm: systemd Tainted: G W 4.4.0-0.rc0.git5.1.fc24.aarch64 #1 [ 12.514292] Hardware name: AppliedMicro Mustang/Mustang, BIOS 1.1.0 Aug 3 2015 [ 12.521569] task: fffffe03dc0e0000 ti: fffffe03dc100000 task.ti: fffffe03dc100000 [ 12.529019] PC is at 0x2aaded13e58 [ 12.532408] LR is at 0x2aaded13e40 [ 12.535795] pc : [<000002aaded13e58>] lr : [<000002aaded13e40>] pstate: a0000000 [ 12.543157] sp : 000003ffdca61aa0 [ 12.546458] x29: 000003ffdca61ac0 x28: 000002aadee40440 [ 12.551773] x27: 000002aadee3f000 x26: 000003ffdca61fe8 [ 12.557087] x25: 000002aadee40000 x24: 0000000000000005 [ 12.562404] x23: 000002aafff89ea0 x22: 000003ffdca61c10 [ 12.567717] x21: 000002aadee41000 x20: 000002aadee40000 [ 12.573032] x19: 000002aafff89ea0 x18: 000002aadedcafa8 [ 12.578345] x17: 000003ff8a47db20 x16: 000002aadee3f4a0 [ 12.583658] x15: 000002aadedb34bb x14: 000002aadedd6b78 [ 12.588971] x13: 000002aadedcafa8 x12: 000002aadedb34bb [ 12.594285] x11: 000002aadedb34bb x10: 000002aadedb34bb [ 12.599601] x9 : 000003ffdca60600 x8 : 00000000000000d3 [ 12.604914] x7 : 7f7f7f7f7f7f7f7f x6 : fefefeff7dff284d [ 12.610232] x5 : 00000000000000b0 x4 : 0000000000000000 [ 12.615550] x3 : 0000000000000004 x2 : 0000000000000014 [ 12.620864] x1 : 000003ff8a899a70 x0 : 000002aadee3f000 [ 12.626177] Will check with systemd HEAD. Is this still a problem with systemd-228? [ 1595.357174] systemd[1]: unhandled level 0 translation fault (11) at 0x6aa83b68a70, esr 0x92000004 [ 1595.366021] pgd = fffffe03d4570000 [ 1595.369404] [6aa83b68a70] *pgd=0000000000000000, *pud=0000000000000000, *pmd=0000000000000000 [ 1595.377922] [ 1595.379406] CPU: 2 PID: 1 Comm: systemd Tainted: G W 4.3.0-1.fc24.aarch64 #1 [ 1595.387544] Hardware name: AppliedMicro Mustang/Mustang, BIOS 1.1.0 Oct 20 2015 [ 1595.394818] task: fffffe03dc090000 ti: fffffe03dc100000 task.ti: fffffe03dc100000 [ 1595.402266] PC is at 0x2aadfaf3380 [ 1595.405648] LR is at 0x2aadfaf3368 [ 1595.409030] pc : [<000002aadfaf3380>] lr : [<000002aadfaf3368>] pstate: a0000000 [ 1595.416389] sp : 000003ffceeab2e0 [ 1595.419684] x29: 000003ffceeab300 x28: 000002aadfc21000 [ 1595.424999] x27: 000002aadfc1f000 x26: 000524e332d19e8e [ 1595.430302] x25: 000002aadfc21000 x24: 0000000000000001 [ 1595.435608] x23: 000003ffceeab438 x22: 000002aadfc21000 [ 1595.440910] x21: 000002aadfc20000 x20: 000002aae5a59810 [ 1595.446216] x19: 000003ffceeab708 x18: 000002aadfb9f6f0 [ 1595.451522] x17: 000003ffa3b2db20 x16: 000002aadfc1f490 [ 1595.456824] x15: 000002aadfb969b3 x14: 000002aadfbbad08 [ 1595.462131] x13: 000002aadfb9f6f0 x12: 000002aadfb969b3 [ 1595.467432] x11: 000002aadfb969b3 x10: 000002aadfb969b3 [ 1595.472740] x9 : 000003ffceea9e40 x8 : 00000000000000d3 [ 1595.478041] x7 : 7f7f7f7f7f7f7f7f x6 : fefefeff7dff284d [ 1595.483347] x5 : 00000000000000b0 x4 : 0000000000000000 [ 1595.488649] x3 : 0000000000000004 x2 : 0000000000000014 [ 1595.493954] x1 : 000003ffa3f49a70 x0 : 000002aadfc1f000 [ 1595.499256] Got it while updated systemd 226 to 228. Start to suspect toolchain? [ 1595.357174] systemd[1]: unhandled level 0 translation fault (11) at 0x6aa83b68a70, esr 0x92000004 [ 1595.366021] pgd = fffffe03d4570000 [ 1595.369404] [6aa83b68a70] *pgd=0000000000000000, *pud=0000000000000000, *pmd=0000000000000000 [ 1595.377922] [ 1595.379406] CPU: 2 PID: 1 Comm: systemd Tainted: G W 4.3.0-1.fc24.aarch64 #1 [ 1595.387544] Hardware name: AppliedMicro Mustang/Mustang, BIOS 1.1.0 Oct 20 2015 [ 1595.394818] task: fffffe03dc090000 ti: fffffe03dc100000 task.ti: fffffe03dc100000 [ 1595.402266] PC is at 0x2aadfaf3380 [ 1595.405648] LR is at 0x2aadfaf3368 [ 1595.409030] pc : [<000002aadfaf3380>] lr : [<000002aadfaf3368>] pstate: a0000000 [ 1595.416389] sp : 000003ffceeab2e0 [ 1595.419684] x29: 000003ffceeab300 x28: 000002aadfc21000 [ 1595.424999] x27: 000002aadfc1f000 x26: 000524e332d19e8e [ 1595.430302] x25: 000002aadfc21000 x24: 0000000000000001 [ 1595.435608] x23: 000003ffceeab438 x22: 000002aadfc21000 [ 1595.440910] x21: 000002aadfc20000 x20: 000002aae5a59810 [ 1595.446216] x19: 000003ffceeab708 x18: 000002aadfb9f6f0 [ 1595.451522] x17: 000003ffa3b2db20 x16: 000002aadfc1f490 [ 1595.456824] x15: 000002aadfb969b3 x14: 000002aadfbbad08 [ 1595.462131] x13: 000002aadfb9f6f0 x12: 000002aadfb969b3 [ 1595.467432] x11: 000002aadfb969b3 x10: 000002aadfb969b3 [ 1595.472740] x9 : 000003ffceea9e40 x8 : 00000000000000d3 [ 1595.478041] x7 : 7f7f7f7f7f7f7f7f x6 : fefefeff7dff284d [ 1595.483347] x5 : 00000000000000b0 x4 : 0000000000000000 [ 1595.488649] x3 : 0000000000000004 x2 : 0000000000000014 [ 1595.493954] x1 : 000003ffa3f49a70 x0 : 000002aadfc1f000 [ 1595.499256] Got it while updated systemd 226 to 228. Start to suspect toolchain? Built 226-3 with current toolchain and it works. Installed 228-2 on top of it and systemd crashed in a way that even reboot is impossible without going back to 226-3 ;( (In reply to Marcin Juszkiewicz from comment #6) > Start to suspect toolchain? Definitely possible. See #1271387. *** This bug has been marked as a duplicate of bug 1271387 *** |