Bug 1263142
Summary: | `/bin/plymouth --details` stall | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Martin Cermak <mcermak> |
Component: | plymouth | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED WORKSFORME | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.7 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-09-21 17:29:48 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: |
Description
Martin Cermak
2015-09-15 08:19:08 UTC
I think the hang happens here in epoll_wait(): ======= (gdb) up #1 0x0000003727a0534b in ply_event_loop_process_pending_events (loop=0x608010) at ply-event-loop.c:1276 1276 number_of_received_events = epoll_wait (loop->epoll_fd, events, (gdb) l 1271 { 1272 timeout = (int) ((loop->wakeup_time - ply_get_timestamp ()) * 1000); 1273 timeout = MAX (timeout, 0); 1274 } 1275 1276 number_of_received_events = epoll_wait (loop->epoll_fd, events, 1277 sizeof (events), timeout); ======= Here, timeout is 0 and loop->epoll_fd points to: 6.7 S x86_64 # ls -l /proc/20862/fd/7 lrwx------ 1 root root 64 Sep 15 06:08 /proc/20862/fd/7 -> [eventpoll] is it looping ? a timeout of 0 to epoll_wait() should return immediately. plymouth --details is a command that is run when there is a failure. I wonder if this stall is the cause of your problem or just a side effect. Do you see anything strange in dmesg ? Unfortunately I don't have access to the reproducer box any more. Feel free to close this out if you consider it appropriate. I can possibly re-open. Got another box, but cannot reproduce. okay let's close this one out since we don't have a customer complaining and it's not clear we'll be able to debug the problem without a reproduction environment. |