1. Forum
  2. Usenet
  3. COMP.SYS.MAC.PORTABLES

  • 2015 MBP freezes under 10.11.6

    From Robert Peirce@21:1/5 to Robert Peirce on Sat Nov 5 09:09:20 2016
    On 11/4/16 7:03 PM, Robert Peirce wrote:
    On problem MBP On Mini On my MBP
    AC3x.kext ACS6x.kext ACS6x.kext

    This is wrong. I just checked and it now says AC6x. I may have
    miss-typed it but now I don't know.

    All have the same name, except as noted. I didn't byte compare these
    but ACS3x.kext, whatever that is, is unique to the problem computer. The others have ACS6x.kext. I have no idea if that matters.

    I ran diff -r on all the directories between the problem MBP and my MBP.
    They are all the same.

    I'm not sure to what degree diff matches cmp. I suppose the bytes must
    be different for the line to be different. I used to have a directory
    compare utility that used cmp but I lost it years ago.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Robert Peirce@21:1/5 to Jolly Roger on Sat Nov 5 09:22:11 2016
    On 11/4/16 9:06 PM, Jolly Roger wrote:
    Are you actually using an HP printer with the problem MBP? Was
    this migrated over? You may want to try downloading an uninstaller from
    HP for that software package to remove all vestiges of it from the
    machine in case it's the cause of the problem.


    I have an HP Office Jet 6000 wireless printer that all my computers use
    in PA. In VA I have an USB Epson on my MBP that I share with the other MBP.

    However, hp_io_enabler_compound.kext is identical on both machines.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Robert Peirce@21:1/5 to Robert Peirce on Sat Nov 5 09:22:08 2016
    On 11/5/16 9:09 AM, Robert Peirce wrote:
    On 11/4/16 7:03 PM, Robert Peirce wrote:
    On problem MBP On Mini On my MBP
    AC3x.kext ACS6x.kext ACS6x.kext

    This is wrong. I just checked and it now says AC6x. I may have
    miss-typed it but now I don't know.


    Not being sure if that ACS3x was correct or not, I have allowed the
    problem MBP to go to sleep to see if it freezes. However, as an old
    friend used to say, "You can never prove the absence of a bug." It may
    wake up but still freeze later.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Robert Peirce@21:1/5 to Robert Peirce on Sat Nov 5 13:34:45 2016
    On 11/5/16 9:22 AM, Robert Peirce wrote:
    On 11/5/16 9:09 AM, Robert Peirce wrote:
    On 11/4/16 7:03 PM, Robert Peirce wrote:
    On problem MBP On Mini On my MBP
    AC3x.kext ACS6x.kext ACS6x.kext

    This is wrong. I just checked and it now says AC6x. I may have
    miss-typed it but now I don't know.


    Not being sure if that ACS3x was correct or not, I have allowed the
    problem MBP to go to sleep to see if it freezes. However, as an old
    friend used to say, "You can never prove the absence of a bug." It may
    wake up but still freeze later.

    I tried this several times and it still froze. Since all the kernel
    extensions match all three computers it must be something else.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Robert Peirce on Sat Nov 5 18:35:10 2016
    Robert Peirce <[email protected]> wrote:
    On 11/5/16 9:22 AM, Robert Peirce wrote:
    On 11/5/16 9:09 AM, Robert Peirce wrote:
    On 11/4/16 7:03 PM, Robert Peirce wrote:
    On problem MBP On Mini On my MBP
    AC3x.kext ACS6x.kext ACS6x.kext

    This is wrong. I just checked and it now says AC6x. I may have
    miss-typed it but now I don't know.


    Not being sure if that ACS3x was correct or not, I have allowed the
    problem MBP to go to sleep to see if it freezes. However, as an old
    friend used to say, "You can never prove the absence of a bug." It may
    wake up but still freeze later.

    I tried this several times and it still froze. Since all the kernel extensions match all three computers it must be something else.

    I forget: Have you made note of the time of the freeze, then looked at the system log for any error messages around that time?

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Robert Peirce@21:1/5 to Jolly Roger on Sun Nov 6 19:10:21 2016
    On 11/5/16 2:35 PM, Jolly Roger wrote:
    I forget: Have you made note of the time of the freeze, then looked at the system log for any error messages around that time?


    No, I have not. I have great difficulty working with logs. I can never
    figure out which one to examine and I really don't understand what I am
    looking at/for.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jolly Roger@21:1/5 to Robert Peirce on Mon Nov 7 01:50:45 2016
    Robert Peirce <[email protected]> wrote:
    On 11/5/16 2:35 PM, Jolly Roger wrote:
    I forget: Have you made note of the time of the freeze, then looked at the >> system log for any error messages around that time?

    No, I have not. I have great difficulty working with logs. I can never figure out which one to examine

    The system log is at /var/log/system.log.

    and I really don't understand what I am
    looking at/for.

    Messages with a time stamp at or near the time of the problem. See above.

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Robert Peirce@21:1/5 to All on Fri Nov 11 11:00:51 2016
    I updated the computer to Sierra and that seems to have solved the
    problem. Of course, one can never know that for sure but so far so good.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)