Summary: | portage freeze during emerge portage | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Burak Sezer <bburaksezer> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Burak Sezer
2009-04-20 13:39:35 UTC
Could you show 'dmesg | tail -n 20' and 'strace -p pid' for saw what take place when portage freezes ? (In reply to comment #1) > Could you show 'dmesg | tail -n 20' and 'strace -p pid' for saw what take place > when portage freezes ? > unfortunately, I have been rebooted system because emerge was eating my CPU. This issue appears sometimes. I hope, it appears in the near future. Next time that it happens, trigger the python debugger by sending the emerge process a SIGUSR1 singal: killall -s SIGUSR1 emerge At the debugger prompt, type these two lines to get a backtrace: s bt The 's' command is necessary in order to step out of the signal handler, and 'bt' displays the backtrace. Please post the backtrace. I'll do that as soon as the problem appears next. However as described that might take a week or so... Interestingly, after I delete, the manifest, the digest works. The Manifest hasn't changed, though. I also tried to change the timestamp of the Manifest to an older time using touch but that did not have an effect, either. Could it be that portage caches the ebuilds somewhere and the problem is in the cached ebuild? please ignore my last two posts, I posted them in the wrong bug. Sorry!!! Some time has passed. Please comment on this bug and reopen it if it happens again; when you do so, can you provide the instructions from Comment #3? If you can't reopen, as you are perhaps a new user; feel free to start a new bug. |