Bug 1026265
Summary: | systemd-readahead: Failed to read event: Value too large for defined data type | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Eduard Vopicka <eduard.vopicka> | ||||||
Component: | systemd | Assignee: | systemd-maint | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 19 | CC: | eduard.vopicka, johannbg, lnykryn, msekleta, plautrba, systemd-maint, vpavlin, zbyszek | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2013-12-13 02:01:47 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: | |||||||||
Attachments: |
|
Description
Eduard Vopicka
2013-11-04 09:55:34 UTC
On another boots, the pre-error boot messages are: Started Sendmail Mail Transport Client. Reached Target MultiUser System. Reached Target Graphical Interface. Maybe the problem is that lines are sometimes written one over the another when the problem occurs. Appears also to be less deterministic after trying ~15 boots. With WiFi enabled in nm-applet: - With HW Wifi Switch off, it never boots to GUI. - With HW WiFi Switch On, it sometimes boots to GUI. Created attachment 819675 [details]
Sample output of journalctl.
Created attachment 822340 [details]
Two sets of updates applied
It appears that the problem probably disappeared automa[tg]ically after two sets of updates have been applied. Please see the file attached for list of these updates. Unfortunately, I did not reboot between these two sets. *** This bug has been marked as a duplicate of bug 696821 *** |