Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #187093

Re: Stretch and i3-7300T PROBLEM AGAIN

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

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" <
avbetev@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: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.
> >
> >
>
>

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Stretch and i3-7300T A_Man_Without_Clue <love.chaser@gmail.com> - 2017-09-17 16:40 +0200
  Re: Stretch and i3-7300T "Alexander V. Makartsev" <avbetev@gmail.com> - 2017-09-17 17:00 +0200
    Re: Stretch and i3-7300T A_Man_Without_Clue <love.chaser@gmail.com> - 2017-09-18 10:00 +0200
      Re: Stretch and i3-7300T Jimmy Johnson <field.engineer@gmail.com> - 2017-09-18 11:10 +0200
        Re: Stretch and i3-7300T A_Man_Without_Clue <love.chaser@gmail.com> - 2017-09-19 16:00 +0200
          Re: Stretch and i3-7300T PROBLEM AGAIN A_Man_Without_Clue <love.chaser@gmail.com> - 2017-09-22 08:30 +0200
            Re: Stretch and i3-7300T PROBLEM AGAIN "Alexander V. Makartsev" <avbetev@gmail.com> - 2017-09-22 15:50 +0200
              Re: Stretch and i3-7300T PROBLEM AGAIN Zoltán Herman <zoltanhbz@gmail.com> - 2017-09-22 16:10 +0200
                Re: Stretch and i3-7300T PROBLEM AGAIN A_Man_Without_Clue <love.chaser@gmail.com> - 2017-09-22 16:40 +0200
  Re: Stretch and i3-7300T James Montgomery <james@envcode.io> - 2017-09-17 17:00 +0200
    Re: Stretch and i3-7300T A_Man_Without_Clue <love.chaser@gmail.com> - 2017-09-18 09:50 +0200
  Re: Stretch and i3-7300T Jimmy Johnson <field.engineer@gmail.com> - 2017-09-18 07:20 +0200
    Re: Stretch and i3-7300T James Montgomery <james@envcode.io> - 2017-09-18 16:20 +0200
      Re: Stretch and i3-7300T Jimmy Johnson <field.engineer@gmail.com> - 2017-09-19 00:20 +0200
    Re: Stretch and i3-7300T solitone <solitone@mail.com> - 2017-09-19 08:00 +0200
      Re: Stretch and i3-7300T Greg Wooledge <wooledg@eeg.ccf.org> - 2017-09-19 14:20 +0200
        Re: firmware-linux-nonfree needed? (was Stretch and i3-7300T) solitone <solitone@mail.com> - 2017-09-19 19:10 +0200
          Re: intel-microcode (was Stretch and i3-7300T) solitone <solitone@mail.com> - 2017-09-19 20:50 +0200
          Re: firmware-linux-nonfree needed? (was Stretch and i3-7300T) deloptes <deloptes@gmail.com> - 2017-09-19 22:10 +0200
            Re: firmware-linux-nonfree needed? (was Stretch and i3-7300T) solitone <solitone@mail.com> - 2017-09-20 13:00 +0200
    Re: Fwd: Stretch and i3-7300T Jimmy Johnson <field.engineer@gmail.com> - 2017-09-23 19:30 +0200
      Re: Fwd: Stretch and i3-7300T Jimmy Johnson <field.engineer@gmail.com> - 2017-09-23 23:00 +0200

csiph-web