Comment # 50
on bug 105425
from iive@yahoo.com
If this `messages` file is from the failed apitrace crash recording, then maybe you should try again. In the previous file I could see that SysRq has been used. Since the first command you use also kills all programs, including the logging, there are no more logs from the session. I do not see anything SysRq in the new `messages` file. So one possibility is that you forgot to enable sysrq and it just hang. Another possibility is that you need to do things with certain timing. Here is how "transactions" work in linux. The program (apitrace) can make many writes and they all could be cached in ram, without been send to disk. Even if they are written on disk, they might not be committed to the file, until `flush()` or `close()` is called on the file. That is, "in theory", the file should remain unchanged until it is flushed, even when old content is overwritten. SysRq+r takes over the keyboard, so keep pressing that first. SysRq+e would send TERM signal to all programs. It is very likely that apitrace could handle that signal and close all files, thus committing them to disk. Give it a few seconds to finish. Count to 5 or wait until hdd stops working. SysRq+i sends KILL signal to all programs. This is forcibly termination and might eliminate programs that are still handling the TERM. In your case I would ask you not to use that. SysRq+s sync all kernel buffered reads to disk. Wait for hdd to stop before pressing next key combination. SysRq+u unmount all filesystems. Same as before, wait for the hdd to stop before pressing the next key. SysRq+b reboot. So basically, watch the HDD LED on the PC box and wait for it to stop, before pressing the next key. Have in mind, when you kill all programs, systemd remains as it is running as init#1, and it would try to restart everything again. So disabling some services you don't need might be good idea. I think I saw apache web server in the previous log. Good Luck and try again.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
