Summary: | systemd-journald[19270]: Failed to write entry, ignoring: Bad address | ||
---|---|---|---|
Product: | systemd | Reporter: | Oleksii Shevchuk <public.avatar> |
Component: | general | Assignee: | systemd-bugs |
Status: | RESOLVED FIXED | QA Contact: | systemd-bugs |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Oleksii Shevchuk
2012-09-09 05:13:04 UTC
Several minutes after it crashes with (gdb) bt #0 0xb77e49c3 in journal_file_find_data_object_with_hash (f=f@entry=0xb8c38fb8, data=data@entry=0xb8c3cb98, size=46, hash=12100562462439712934, ret=ret@entry=0xbf8d65b0, offset=0xbf8d65c0) at src/journal/journal-file.c:633 #1 0xb77e4ca0 in journal_file_append_data (f=f@entry=0xb8c38fb8, data=0xb8c3cb98, size=46, ret=ret@entry=0xbf8d66e0, offset=offset@entry=0xbf8d66f0) at src/journal/journal-file.c:725 #2 0xb77e6563 in journal_file_append_entry (f=0xb8c38fb8, ts=0xbf8d66fc, ts@entry=0x0, iovec=iovec@entry=0xbf8d6998, n_iovec=n_iovec@entry=8, seqnum=seqnum@entry=0xbf8d8ec4, ret=ret@entry=0x0, offset=offset@entry=0x0) at src/journal/journal-file.c:1073 #3 0xb77d59ad in write_to_journal (n=8, iovec=0xbf8d6998, uid=0, s=0xbf8d8ea0) at src/journal/journald.c:458 #4 dispatch_message_real (s=0xbf8d8ea0, iovec=0xbf8d6998, n=8, m=122, ucred=0x0, tv=0x0, label=0x0, label_len=0, unit_id=0x0) at src/journal/journald.c:662 #5 0xb77d6d92 in dev_kmsg_record (l=<optimized out>, p=0xbf8d6d8f "JBD: IO error -5 recovering block 4653 in log", s=0xbf8d8ea0) at src/journal/journald-kmsg.c:305 #6 server_read_dev_kmsg (s=s@entry=0xbf8d8ea0) at src/journal/journald-kmsg.c:347 #7 0xb77d31e2 in process_event (ev=0xbf8d8e10, s=0xbf8d8ea0) at src/journal/journald.c:997 #8 main (argc=1, argv=0xbf8d9194) at src/journal/journald.c:1537 Which version is this? 189 I am pretty sure this has been fixed these days. Closing hence. If it persists please open a new bug, in github. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.