Contribute
Register

Slow Boot time with Samsung 960 Evo NVME?

Status
Not open for further replies.
Hi everyone and to the attention of RehabMan.

With High Sierra, if I enable Trim support, I have:

1) slow start issues (40'')
after row
- (apfs) apfs_mount_update:17785: er: mount check: ro->rw update: no encryption rolling in progress, bailing.
before rows:
- (apfs) er_state_obj_get_for_recovery: 3682: No ER object - rolling is not happening, nothing to recover.
- (apfs) handle_mount: 254: vol-uuid: 42581E64-0633-4338-A556-AFBEFF7E020F block size: 4096 block count: 58556556 (unencrypted; flags: 0x1; features: 1.0.2)
- (apfs) apfs_vfsop_mount: 1331: mounted volume: VM .

2) ACPI errors [SANV] and [_DSM] and "ACPI: Can not translate ACPI object 14" in System Bootlog.

3) Frequent "Wake reason: PEGP" if I ask Stop.

I really understand that it is very boring for you, but would you be so kind to help me solve something?

Sorry for my bad english and very thanks in advance.
Giuseppe

Read FAQ, "Problem Reporting"
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
 

With High Sierra, if I enable Trim support, I have:

1) slow start issues (40'')
before rows:
- (apfs) er_state_obj_get_for_recovery: 3682: No ER object - rolling is not happening, nothing to recover.
- (apfs) handle_mount: 254: vol-uuid: 42581E64-0633-4338-A556-AFBEFF7E020F block size: 4096 block count: 58556556 (unencrypted; flags: 0x1; features: 1.0.2)
- (apfs) apfs_vfsop_mount: 1331: mounted volume: VM .

2) ACPI errors [SANV] and [_DSM] and "ACPI: Can not translate ACPI object 14" in System Bootlog.

3) Frequent "Wake reason: PEGP" if I ask Stop.

Sorry for bothering and many thanks.
Giuseppe
 

Attachments

  • data.zip
    2.5 MB · Views: 90
With High Sierra, if I enable Trim support, I have:

1) slow start issues (40'')
before rows:
- (apfs) er_state_obj_get_for_recovery: 3682: No ER object - rolling is not happening, nothing to recover.
- (apfs) handle_mount: 254: vol-uuid: 42581E64-0633-4338-A556-AFBEFF7E020F block size: 4096 block count: 58556556 (unencrypted; flags: 0x1; features: 1.0.2)
- (apfs) apfs_vfsop_mount: 1331: mounted volume: VM .

2) ACPI errors [SANV] and [_DSM] and "ACPI: Can not translate ACPI object 14" in System Bootlog.

3) Frequent "Wake reason: PEGP" if I ask Stop.

Sorry for bothering and many thanks.
Giuseppe

Problems:
- you forgot to press F4 (no files in ACPI/origin)
- you forgot to press F2 (misc/preboot.log is missing)
- your config.plist is corrupt
Code:
SPEEDY-NUC:patched rehabman$ plutil -lint /Users/rehabman/Downloads/data/EFI\:CLOVER/config.plist
/Users/rehabman/Downloads/data/EFI:CLOVER/config.plist: Encountered unexpected character d on line 282 while looking for close tag
- after fixing your config.plist, it is obvious your ACPI configuration is wrong
- patched SSDTs in ACPI/patched without DropOem=true
- likely incomplete SSDTs in ACPI/patched
- poor naming practice (SSDT-x where 'x' is a number should be reserved for patched SSDTs, eg. those that came from ACPI/origin). add-on SSDTs should be named with meaningful names (eg. not numbered).
- power management implemented wrongly. You should not drop the CPU SSDTs. And config.plist/ACPI/SSDT/Generate should be false.
- your Clover/kexts is wrong (you are injecting duplicates from Other and 10.12/10.13)
- config.plist/SystemParameters/InjectKexts should be set "Detect". You have it set true.

Yeah,... it is quite a mess.
 
Problems:
- you forgot to press F4 (no files in ACPI/origin)
- you forgot to press F2 (misc/preboot.log is missing)
- your config.plist is corrupt
Code:
SPEEDY-NUC:patched rehabman$ plutil -lint /Users/rehabman/Downloads/data/EFI\:CLOVER/config.plist
/Users/rehabman/Downloads/data/EFI:CLOVER/config.plist: Encountered unexpected character d on line 282 while looking for close tag
- after fixing your config.plist, it is obvious your ACPI configuration is wrong
- patched SSDTs in ACPI/patched without DropOem=true
- likely incomplete SSDTs in ACPI/patched
- poor naming practice (SSDT-x where 'x' is a number should be reserved for patched SSDTs, eg. those that came from ACPI/origin). add-on SSDTs should be named with meaningful names (eg. not numbered).
- power management implemented wrongly. You should not drop the CPU SSDTs. And config.plist/ACPI/SSDT/Generate should be false.
- your Clover/kexts is wrong (you are injecting duplicates from Other and 10.12/10.13)
- config.plist/SystemParameters/InjectKexts should be set "Detect". You have it set true.

Yeah,... it is quite a mess.

I'm just embarrassed by the naivety that I presented to you. Sorry for the time you've lost for me.
I'm trying to fix something.
In the future, can I ask you something?

Hi and thank you very much.
Giuseppe
 
ACPI/patched is out of sync with native.
Note different SystemMemory addresses:
Code:
SPEEDY-NUC:origin rehabman$ diff ../origin/ ../patched/ |grep SystemMemory
<     OperationRegion (GNVS, SystemMemory, 0x8A860000, 0x06B3)
>     OperationRegion (GNVS, SystemMemory, 0x8A899000, 0x06B3)
<                 OperationRegion (CPSB, SystemMemory, 0x89FDFF98, 0x10)
>                 OperationRegion (CPSB, SystemMemory, 0x8A018F98, 0x10)
<                 OperationRegion (XMIO, SystemMemory, Local0, 0x9000)

I have the same problem, I takes almost two minutes to boot, however I'm not applying any ACPI patches at all. The slowdown started after converting the disk to APFS. I neither have any other binary patches like the TRIM enabler. Do you have any idea of what other things could be happening?
 

Attachments

  • CLOVER.zip
    1.9 MB · Views: 99
  • ioreg.plist.zip
    744.1 KB · Views: 92
  • kextcache.txt.zip
    601 bytes · Views: 67
  • kextstat.txt.zip
    793 bytes · Views: 88
  • patchmatic.zip
    49.7 KB · Views: 66
Here they are, thanks in advance and sorry for not attaching the debug info beforehand.

Problems:
- FixUSB_1000 not needed. remove.
- CPU PM not implemented
- native support for SATA 8086:a282 is missing (add SATA-200-series-unsupported.kext)
- kexts not installed correctly (all kexts should be installed to the system volume)
- USB not implemented correctly (see my USBInjectAll guide)
- VirtualBox tends to interfere with USB. remove.
- you have a bunch of things hooking your USB (Google Chrome, Plex Tuner Service)
- check boot logs for other things that may cause delays
 
Hi everyone and to the attention of RehabMan.
I abuse your patience, I know and apologize.
My computer, sometimes and not always, wakes up immediately after going to stop and then back to stop and stay there.
After doing this a first time, this does not repeat to subsequent stops.
The log says in these cases: 'Wake reason:?' or 'Wake reason: PEGP'.
In addition, computer's start-up, shutdown and especially restart are very slow.
You can correct me something, please?
I would be grateful if you tell me what I can fix in the DSDT or SSDT patches.
Ciao.
 

Attachments

  • data.zip
    7 MB · Views: 132
Hi everyone and to the attention of RehabMan.
I abuse your patience, I know and apologize.
My computer, sometimes and not always, wakes up immediately after going to stop and then back to stop and stay there.
After doing this a first time, this does not repeat to subsequent stops.
The log says in these cases: 'Wake reason:?' or 'Wake reason: PEGP'.
In addition, computer's start-up, shutdown and especially restart are very slow.
You can correct me something, please?
I would be grateful if you tell me what I can fix in the DSDT or SSDT patches.
Ciao.

Your ACPI/patched is out of sync with native.
Look at the different SystemMemory region addresses:
Code:
SPEEDY-NUC:patched rehabman$ diff ../origin/ ../patched/ |grep SystemMemory
<     OperationRegion (GNVS, SystemMemory, 0xCDED6A98, 0x034D)
>     OperationRegion (GNVS, SystemMemory, 0xB8ED6A98, 0x034D)
<         OperationRegion (CPSB, SystemMemory, 0xCDC97E98, 0x10)
>         OperationRegion (CPSB, SystemMemory, 0xB8C97E98, 0x10)
<         OperationRegion (PNVS, SystemMemory, 0xCDED8F98, 0x0053)
>     OperationRegion (SANV, SystemMemory, 0xCDED6E18, 0x0186)
>         OperationRegion (RPCS, SystemMemory, \XBAS, 0x00018040)
>                 OperationRegion (RPCY, SystemMemory, BBAR, 0x25)
>             OperationRegion (CCDC, SystemMemory, ADDR, 0x04)
>                     OperationRegion (IPCV, SystemMemory, BBAR, 0x70)
>                 OperationRegion (IPCV, SystemMemory, BBAR, 0xBF)
>                 OperationRegion (IPCV, SystemMemory, BBAR, 0x70)
>                 OperationRegion (IPCV, SystemMemory, BBAR, 0x1020)
>         OperationRegion (IGDM, SystemMemory, ASLB, 0x2000)
>             OperationRegion (PCI0, SystemMemory, Local7, One)
>             OperationRegion (PCI0, SystemMemory, Local7, One)
>             OperationRegion (PCI0, SystemMemory, Local7, 0x02)
>             OperationRegion (PCI0, SystemMemory, Local7, 0x02)
>             OperationRegion (PCI0, SystemMemory, Local7, 0x04)
>             OperationRegion (PCI0, SystemMemory, Local7, 0x04)
>             OperationRegion (PCI0, SystemMemory, Local7, 0x04)
<                     OperationRegion (CST0, SystemMemory, DerefOf (Index (SSDT, 0x07)), DerefOf (Index (SSDT, 0x08)))
>             OperationRegion (PCI0, SystemMemory, Local7, 0x04)
>             OperationRegion (PCI0, SystemMemory, Local7, 0x04)
>             OperationRegion (PCI0, SystemMemory, Local7, 0x04)
>             OperationRegion (PCI0, SystemMemory, Local7, 0x02)
>             OperationRegion (PCI0, SystemMemory, Local7, 0x04)
>             OperationRegion (PCI0, SystemMemory, Local7, 0x08)
<                 OperationRegion (CST1, SystemMemory, DerefOf (Index (SSDT, 0x0A)), DerefOf (Index (SSDT, 0x0B)))
>             OperationRegion (PCI0, SystemMemory, Local7, 0x04)
<                 OperationRegion (IST1, SystemMemory, DerefOf (Index (SSDT, 0x04)), DerefOf (Index (SSDT, 0x05)))
 
Status
Not open for further replies.
Back
Top