MacBook 2010 freezing after Idealing for X-amount of time

That’s all i know too. Little! Little of this …little of that … not enough of anything! :rofl:

Seem that both of us are cut out of the same cloth!

The LTS kernel seem to have resolve the freeze issue. Previously, by now, the MacBook would have frozen. Keeping my hopes up!

FYI: The LTS kernel seem to have resolve the freeze issue. Previously, by now, the MacBook would have frozen. Keeping my hopes up!

1 Like

Test it in both since you have made some mods after you are sure it’s working with the lts kernel.

Yes, it is still running while idling. If It stays in this condition, I will turn on some power features and I if I can duplicate the issue, I will info the community. THANKS to all for ideas, suggestions and in general, for the help.

1 Like

A big shout out to @RickLinux and @LizziAS for their assistance.

1 Like

Greeting all! An update to the MacBook7,1 1.0 (2010) freeze after x-amount of time. Well I have attempted all suggestions offered by @ricklinux and @LizziAS with a certain amount of progress, however the issue persist.

DETAILS: I am running an LTS and a swapfile of 6G. I could use the system for hours without issues. I have run the machine for upwards of 4 hours plus, but here is the weird behavior, once I am no longner active on the keyboard, the beast Freezes. The mouse can be moved, but every other activity is null.

I’ve done a couple of fresh installs (for the experience) and all power saving modes are off. My eyes see nothing in the journalctl log that may give me a heads-up. Weird behavior indeed! The journey for a resolution continues :100:

Do you continue to run it on nouveau?

Running the broadcom-wl-lts package

No i mean the nvidia graphics? Are you running open source nouveau? or the Nvidia 340xx drivers?

Correction: NVIDIA MCP89 Geforce 320M , alternative nouveau

Are you using TLP for power control?

NO!!! Regular that came with installation and all power saving modes off.

Here is more behavior. I been on the machine for a couple of hours and currently it is untouched for about an hour or so. And all seen fine at the moment.

If the mouse moves then the laptop has not frozen.

Can you switch to a TTY (e.g. CTRL+ALT+F2)?

Can you SSH in?

Is the system overheating? Can you check the system temperatures?

Can you follow the output of sudo journalctl -f and see what is happening at the point the screen freezes?

1 Like

NO. All is frozen, only the mouse is active.

Please read all of my post and consider each “can you” point as suggestions of things you should try (and feed back on individually).

Well here is some info:

Graphics: Device-1: NVIDIA MCP89 [GeForce 320M] vendor: Apple driver: N/A
alternate: nouveau, nvidia_drm, nvidia bus-ID: 02:00.0 chip-ID: 10de:08a0
class-ID: 0300
Device-2: Apple Built-in iSight type: USB driver: uvcvideo bus-ID: 1-6:2
chip-ID: 05ac:8507 class-ID: 0e02 serial: 8TD8S01YRDCJ6A00
Display: x11 server: X.org 1.20.11 driver: loaded: vesa unloaded: fbdev,modesetting
alternate: nouveau,nv resolution: <missing: xdpyinfo>
OpenGL: renderer: llvmpipe (LLVM 11.1.0 128 bits) v: 4.5 Mesa 21.0.3 compat-v: 3.1
direct render: Yes
[grl@grl-macbook71-eos ~]$ sudo journalctl -f
– Journal begins at Mon 2021-05-03 15:12:29 EDT. –
May 03 16:12:20 grl-macbook71-eos kernel: audit: type=1100 audit(1620072740.957:110): pid=3001 uid=1000 auid=1000 ses=2 msg=‘op=PAM:authentication grantors=? acct=“grl” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=failed’
May 03 16:12:31 grl-macbook71-eos audit[3001]: USER_AUTH pid=3001 uid=1000 auid=1000 ses=2 msg=‘op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct=“grl” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
May 03 16:12:31 grl-macbook71-eos audit[3001]: USER_ACCT pid=3001 uid=1000 auid=1000 ses=2 msg=‘op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct=“grl” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
May 03 16:12:31 grl-macbook71-eos sudo[3001]: grl : TTY=pts/0 ; PWD=/home/grl ; USER=root ; COMMAND=/usr/bin/journalctl -f
May 03 16:12:31 grl-macbook71-eos kernel: audit: type=1100 audit(1620072751.707:111): pid=3001 uid=1000 auid=1000 ses=2 msg=‘op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct=“grl” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
May 03 16:12:31 grl-macbook71-eos kernel: audit: type=1101 audit(1620072751.707:112): pid=3001 uid=1000 auid=1000 ses=2 msg=‘op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct=“grl” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
May 03 16:12:31 grl-macbook71-eos kernel: audit: type=1110 audit(1620072751.717:113): pid=3001 uid=1000 auid=1000 ses=2 msg=‘op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct=“root” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
May 03 16:12:31 grl-macbook71-eos audit[3001]: CRED_REFR pid=3001 uid=1000 auid=1000 ses=2 msg=‘op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct=“root” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
May 03 16:12:31 grl-macbook71-eos sudo[3001]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
May 03 16:12:31 grl-macbook71-eos audit[3001]: USER_START pid=3001 uid=1000 auid=1000 ses=2 msg=‘op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct=“root” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
May 03 16:12:31 grl-macbook71-eos kernel: audit: type=1105 audit(1620072751.717:114): pid=3001 uid=1000 auid=1000 ses=2 msg=‘op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct=“root” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’

Two quick tips for getting help via fora:

  1. Post terminal output within a “code fence”, e.g.
    ~~~
    Output
    ~~~
    and it will appear as:
    Output
    
  2. Make sure your posts provide useful additional information, ideally directly responding to questions asked by those people who are trying to remotely diagnose an issue.
  3. Remember you can go back and edit posts to correct them or add more information.