Comment 53 for bug 1491566
Revision history for this message
| Alexandros Frantzis (afrantzis) wrote Re: Shell not responsive after an incoming SMS or call notification | #53 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> i succeeded in getting my device stuck in a frozen state. it seems alive, i can interact with the shell
How can you interact with the shell? Does it respond to input? Can you turn the screen on/off with the power button?
> so i grabbed a dump from lsof as well.
> here's the list of open files dump
Good call! unity8 has clearly reached its fd limit. It seems to be leaking fds (can't tell if it's unity8 itself leaking or another component inside unity8, e.g., mir):
...
unity8 2421 phablet 1017r CHR 13,70 0t0 1122358 /dev/input/event6 (deleted)
unity8 2421 phablet 1018r CHR 13,70 0t0 1117702 /dev/input/event6 (deleted)
unity8 2421 phablet 1019r CHR 13,70 0t0 1120899 /dev/input/event6 (deleted)
unity8 2421 phablet 1020r 0000 0,9 0 5513 anon_inode
unity8 2421 phablet 1021r 0000 0,9 0 5513 anon_inode
unity8 2421 phablet 1022r CHR 13,70 0t0 1120534 /dev/input/event6 (deleted)
unity8 2421 phablet 1023r CHR 13,70 0t0 1117848 /dev/input/event6 (deleted)
Unfortunately we didn't get a list of files for USC since it's running as root. If you still have the phone in that state could you rerun lsof with sudo?
> ok, i was able to attach gdb to usc, here's the bt
The backtrace seems normal. USC is just waiting for work to do, nothing suspicious in this case.
So, the question is if this is indeed an instance of the same bug we have been investigating or a different bug you have uncovered.
I will follow the fd leak lead and see if I can get more information.