On 09/22/2017 11:08 PM, Zoltán Herman wrote: > Or you use netinst cd and start rescue mode... and execute shell on hdd... > > 2017. szept. 22. 3:44 du. ezt írta ("Alexander V. Makartsev" > <avbe...@gmail.com <mailto:avbe...@gmail.com>>): > > At this point it is highly unlikely this "freeze" problem is CPU > related. There could be hardware problems like over-heating, bad memory, > power issues, etc. This list could extend forever. > To debug this problem you need to read syslog\journal to find what was > last thing your system did before\after "freezing". > You can do this by asking journald a whole log from previous boot: > $ sudo journalctl -b -1 > If you don't remember when that "freeze" happened, you can walk back > through previous logs to find the one with "freeze" problem by changing > -1 to -2, -3, etc > $ sudo journalctl -b -2 > > > > On 22.09.2017 11 <tel:22.09.2017%2011>:20, A_Man_Without_Clue wrote: > > > > Oh no, I still got problem. > > > > I have installed Stretch with non-free enabled and was able to install > > then upgraded the kernel. I got some problems first seemed like > > something to do with power supply so I got new power supply installed > > today but the problem is that the system freezes at some point. I > > haven't been able to pin point what is the cause of the problem > whether > > it's hardware or software... > > I will follow up but in the mean timen I wonder if there's anybody who > > is encountering problem with Kaby Lake processor with Stretch. > > > > >
Well, I don't know journalctl doesn't give me anything... It once again happened while ago. I was transferring the files from the back up HDD to main HDDs, I was also running the Firefox though I wasn't browsing actively. Firefox crashed and then thing went froze.I think it's something to do with PcManFM though... I was able to switch to other console, tty2 and tried to kill the process but did not help anything. I was also monitoring the system usage, CPU and memory usage were pretty low. Maybe I should try using another file manager instead.