|
Bugzilla – Full Text Bug Listing |
| Summary: | systemd crashed: Assertion failed at src/hashmap.c | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Richard Weinberger <richard> |
| Component: | Basesystem | Assignee: | Frederic Crozat <fcrozat> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 12.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | systemd crash | ||
which version of systemd are you running ? Does it happen everytime ? If you can reproduce, could you test with package from http://download.opensuse.org/repositories/home:/fcrozat:/systemd/openSUSE_12.1/ ? Please mail me privately the backtrace from the core dump (I don't think it will contain any sensitive information). I'm using systemd-37-3.6.1.x86_64. So far it happened only once. :-( Sent you an email! hmm, I can't decypher your core, I don't have the exact same libraries than you have. please try to enable debug repositories for 12.1 and updates and install systemd-debuginfo and glibc-debuginfo (and maybe additional packages) then, run : gdb -c your_core /bin/systemd and then type "bt" and attach the output. There you go:
#0 0x00007ff816c93d95 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x000000000040be1c in crash (sig=6) at src/main.c:123
#2 <signal handler called>
#3 0x00007ff816c93d95 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#4 0x00007ff816c952ab in __GI_abort () at abort.c:93
#5 0x0000000000466e69 in log_assert (file=0x4afc8c "src/hashmap.c", line=246,
func=<optimized out>, format=<optimized out>) at src/log.c:506
#6 0x000000000046407b in unlink_entry (h=<optimized out>, e=<optimized out>,
hash=<optimized out>) at src/hashmap.c:246
#7 0x00000000004643ca in remove_entry (h=0x7ff818224fe0, e=0x6e1910) at src/hashmap.c:258
#8 0x0000000000464798 in hashmap_clear (h=0x7ff818224fe0) at src/hashmap.c:293
#9 0x00000000004647be in hashmap_free (h=0x7ff818224fe0) at src/hashmap.c:271
#10 0x0000000000475507 in bidi_set_free (s=0x7ff818224fe0, u=0x6fdb40) at src/unit.c:333
#11 unit_free (u=0x6fdb40) at src/unit.c:356
#12 0x000000000040c848 in manager_clear_jobs_and_units (m=0x6dc1e0) at src/manager.c:433
#13 0x0000000000412b3b in manager_free (m=0x6dc1e0) at src/manager.c:454
#14 0x000000000040910a in main (argc=<optimized out>, argv=<optimized out>)
at src/main.c:1509
You can close this bug as INVALID. I was hit by another issue which most likely caused this systemd crash: https://lkml.org/lkml/2012/2/16/130 closing as invalid then |
Created attachment 475753 [details] systemd crash User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 While shutting down systemd crashed. See attached picture. The affected system is using encrypted disks and stuff. I don't know what kind of confidential information the core dump contains. In case you need the core dump please contact me in private. Reproducible: Didn't try Steps to Reproduce: 1. 2. 3.