Elektrostatische Entladung - memcantgetreserved
Bei einer elektrostatischen Entladung tritt schlagartig Ladung von einem geladenen Körper auf einen ungeladenen über. In Computern führt dies einerseits zu Beschädigungen, aber auch zu fehlerhaften Daten im RAM, da es dazu kommen kann, dass Speicherblöcke aktiviert werden, die eigentlich gar nicht aktiviert werden sollten. Es kann aber auch bei einer Überladung durch fehlerhafte Steuerungen (beispielsweise beim Übertakten) zu solchen ESD's kommen. Der Test fand draussen statt.
standard 14:58:46.215802 +0100 Adobe Desktop Service 0x7fa510d876c0 - PerformanceMonitor::measurePostBackgroundingCPUUsage: Process was using 0.2% CPU after becoming non visible.
//Spannung wird aufgebaut
standard 15:02:24.264660 +0100 dasd Attempting to suspend based on triggers: (
"com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange" )
standard 15:02:24.264845 +0100 dasd Ignoring trigger com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange because conditions are deteriorating
standard 15:02:34.159257 +0100 dasd Attempting to suspend based on triggers: ( "com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange" )
//CPU Auslastung steigt
standard 15:03:04.043543 +0100 dasd Attempting to suspend based on triggers: ( "com.apple.duetactivityscheduler.batterylevelpolicy.batterylevelchange", "com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange" )
standard 15:03:04.043808 +0100 dasd Ignoring trigger com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange because conditions are deteriorating
standard 15:03:14.163140 +0100 dasd Attempting to suspend based on triggers: ( "com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange" )
standard 15:03:20.115418 +0100 thermald Thermal pressure level: Moderate based on CPU thermal level 83
standard 15:03:26.679224 +0100 dasd Attempting to suspend based on triggers: ( "com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange" )
standard 15:03:26.679313 +0100 dasd Ignoring trigger com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange because conditions are deteriorating
standard 15:03:41.166035 +0100 Adobe Desktop Service 0x7fa510d876c0 - PerformanceMonitor::measureCPUUsageInActivityState: Process is using 0.4% CPU in state: NonVisible
standard 15:03:44.278263 +0100 dasd Attempting to suspend based on triggers: ( "com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange" )
standard 15:03:44.278366 +0100 dasd Ignoring trigger com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange because conditions are deteriorating
standard 15:03:48.028826 +0100 dasd 0:com.apple.icloud.findmydeviced.keep-alive-on-dirty:9933E5:[
{name: BatteryLevelPolicy, policyWeight: 1.000, response: {Decision: Can Proceed, Score: 0.51, Rationale: [{batteryLevel == 27}]}}
//Erste Freezes
{name: CPUUsagePolicy, policyWeight: 5.000, response: {Decision: Can Proceed, Score: 0.10, Rationale: [{cpuLevel == 90}]}}
{name: DeviceActivityPolicy, policyWeight: 2.000, response: {Decision: Can Proceed, Score: 0.40}}
{name: MemoryPressurePolicy, policyWeight: 5.000, response: {Decision: Can Proceed, Score: 0.50, Rationale: [{[memoryPressure]: Required:2.00, Observed:1.00},]}}
{name: ChargerPluggedInPolicy, policyWeight: 10.000, response: {Decision: Can Proceed, Score: 0.50, Rationale: }}
{name: ThermalPolicy, policyWeight: 5.000, response: {Decision: Can Proceed, Score: 0.20, Rationale: }}
] sumScores:17.823432, denominator:35.510000, FinalDecision: Can Proceed FinalScore: 0.501927}
standard 15:03:48.035918 +0100 dasd 501:com.apple.suggestd.persist-stats:683BBE:[
{name: CPUUsagePolicy, policyWeight: 5.000, response: {Decision: Must Not Proceed, Score: 0.00, Rationale: [{[Max allowed CPU Usage level]: Required:50.00, Observed:90.00},]}}
{name: ThermalPolicy, policyWeight: 5.000, response: {Decision: Absolutely Must Not Proceed, Score: 0.00, Rationale: [{thermalLevel >= 1}]}}
//Temperatur ist noch in Ordnung, es wird kein Programm beendet
], FinalDecision: Absolutely Must Not Proceed}
standard 15:03:48.036645 +0100 dasd 501:PDCardFileManager.RevocationCheck:74B8A1:[
{name: CPUUsagePolicy, policyWeight: 5.000, response: {Decision: Must Not Proceed, Score: 0.00, Rationale: [{[Max allowed CPU Usage level]: Required:50.00, Observed:90.00},]}}
{name: NetworkQualityPolicy, policyWeight: 11.400, response: {Decision: Absolutely Must Not Proceed, Score: 0.00, Rationale: [{[networkPathAvailability]: Required:1.00, Observed:0.00},]}}
{name: ThermalPolicy, policyWeight: 5.000, response: {Decision: Absolutely Must Not Proceed, Score: 0.00, Rationale: [{thermalLevel >= 1}]}}
], FinalDecision: Absolutely Must Not Proceed}
standard 15:03:48.037351 +0100 dasd 0:com.apple.applessdbgrefresh.activity:F2FD3B:[
{name: CPUUsagePolicy, policyWeight: 5.000, response: {Decision: Must Not Proceed, Score: 0.00, Rationale: [{[Max allowed CPU Usage level]: Required:50.00, Observed:90.00},]}}
{name: DeviceActivityPolicy, policyWeight: 20.000, response: {Decision: Must Not Proceed, Score: 0.00, Rationale: [{deviceActivity == 1}]}}
{name: ThermalPolicy, policyWeight: 5.000, response: {Decision: Absolutely Must Not Proceed, Score: 0.00, Rationale: [{thermalLevel >= 1}]}}
], FinalDecision: Absolutely Must Not Proceed}
standard 15:03:54.373760 +0100 dasd Attempting to suspend based on triggers: ( "com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange" )
standard 15:04:04.332448 +0100 dasd Attempting to suspend based on triggers: ( "com.apple.duetactivityscheduler.batterylevelpolicy.batterylevelchange", "com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange" )
standard 15:04:04.332831 +0100 dasd Ignoring trigger com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange because conditions are deteriorating
standard 15:04:23.554285 +0100 com.apple.WebKit.WebContent 0x7fcaf5d21a90 - PerformanceMonitor::measureCPUUsageInActivityState: Process is using 36.0% CPU in state: VisibleNonActive
standard 15:04:23.556635 +0100 com.apple.WebKit.WebContent 0x7fcaf5d21a90 - PerformanceMonitor::measureCPUUsageInActivityState: Process is using 75.4% CPU in state: NonVisible
standard 15:04:24.361447 +0100 dasd Attempting to suspend based on triggers: ( "com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange" )
standard 15:04:34.867549 +0100 thermald Thermal pressure level: Nominal based on CPU thermal level 49
standard 15:04:37.929922 +0100 com.apple.WebKit.WebContent 0x7fcaf5d21a90 - PerformanceMonitor::measureCPUUsageInActivityState: Process is using 0.5% CPU in state: VisibleAndActive
standard 15:04:38.129161 +0100 com.apple.WebKit.WebContent 0x7f9ecb717690 - PerformanceMonitor::measureCPUUsageInActivityState: Process is using 75.3% CPU in state: VisibleNonActive
standard 15:04:38.130240 +0100 com.apple.WebKit.WebContent 0x7f9ecb717690 - PerformanceMonitor::measureCPUUsageInActivityState: Process is using 111.0% CPU in state: NonVisible
standard 15:04:38.630105 +0100 com.apple.WebKit.WebContent 0x7fcaf5d21a90 - PerformanceMonitor::measurePostLoadCPUUsage: Process was using 0.2% CPU after the page load.
standard 15:04:38.750033 +0100 com.apple.WebKit.WebContent 0x7f9ecb717690 - PerformanceMonitor::measureCPUUsageInActivityState: Process is using 7.5% CPU in state: VisibleAndActive
standard 15:04:38.941918 +0100 com.apple.WebKit.WebContent 0x7f93aac2e690 - PerformanceMonitor::measureCPUUsageInActivityState: Process is using 78.7% CPU in state: VisibleNonActive
standard 15:04:38.944586 +0100 com.apple.WebKit.WebContent 0x7f93aac2e690 - PerformanceMonitor::measureCPUUsageInActivityState: Process is using 100.5% CPU in state: NonVisible
standard 15:04:39.827007 +0100 com.apple.WebKit.WebContent 0x7f93aac2e690 - PerformanceMonitor::measureCPUUsageInActivityState: Process is using 5.5% CPU in state: VisibleAndActive
standard 15:04:44.084915 +0100 thermald Thermal pressure level: Moderate based on CPU thermal level 52
standard 15:04:44.158698 +0100 dasd Attempting to suspend based on triggers: ( "com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange", "com.apple.duetactivityscheduler.thermalpolicypolicy.thermalpressurechange" )
standard 15:04:44.159170 +0100 dasd Ignoring trigger com.apple.duetactivityscheduler.cpuusagepolicy.cpuusagelevelchange because conditions are deteriorating
Da ich eine Ausbildung zum Programmierer absolviere, mache ich immer noch viele Fehler und so kam es, dass ich ein Motherboard mit geerdeter Watte gereinigt habe. Aufgrund von Hardwarefehlern hat die CPU jedoch etwas Spannung hinterlassen und die Wattierung aufgeladen, sodass die Wattierung eine elektrostatische Entladung (ESD) verursachte und der Arbeitsspeicher beschädigt wurde. Also funktionieren die Blöcke nicht mehr und sie können nicht reserviert werden. #memcantgetreserved
Sie können dies durcheinander bringen, wenn Sie zu viel RAM mit einem übertakteten Prozessor verwenden. Wie Sie auf dem Bild sehen können, gibt es Blöcke, die nicht neu geschrieben werden können, was das System dazu veranlasst hat, sie zu deaktivieren, was dazu führt, dass der Adresscontroller der CPU mehr aufgeteilte Daten verwalten musste. Diese chaotischen Daten können auch gefunden werden, wenn Sie Anwendungen in Xcode erstellen und testen, die viele unterschiedliche NS-Benutzervorgaben erstellen, die sich ändern und redundant verfügbar sind. So geschah es in einem Musik-Post-Stream.
Die Protokolle kamen nach meinem kleinen Unfall.
Diese Dinge können deinen Computer zerstören:
- Reinigen des Computerinneren mit einem Ballon (während dieses Ding zum Reinigen von Tastaturen geeignet ist)
- Achten Sie bei lauten Tönen darauf, dass Ihr Laufwerk sehr leise ist, indem Sie es bei langen Kopiervorgängen verlangsamen
- Deaktivieren des automatischen CPU-Lüfters
-Blockieren Sie die CPU mit Staub oder etwas anderem
-Ihr Gerät wird zerstört, wenn Sie ein Luftdrucksystem verwenden, das Luft enthält und kondensieren kann
- Starke Magnete können Festplatten zerstören
Processes: 367 total, 4 running, 1 stuck, 362 sleeping, 1460 threads 00:14:54
Load Avg: 2.63, 2.28, 1.83 CPU usage: 31.25% user, 7.93% sys, 60.81% idle
SharedLibs: 367M resident, 63M data, 46M linkedit.
MemRegions: 57387 total, 3060M resident, 153M private, 1334M shared.
PhysMem: 11G used (2441M wired), 5577M unused.
VM: 1813G vsize, 1293M framework vsize, 400119(0) swapins, 446718(0) swapouts.
Networks: packets: 1612146/1975M in, 971455/195M out.
Disks: 344123/7613M read, 409203/8809M written.
PID COMMAND %CPU TIME #TH #WQ #PORT MEM PURG CMPRS PGRP
10218 avguard.bin 97.5 00:01.25 1/1 0 15 107M+ 0B 0B 10218
10213 top 3.1 00:00.35 1/1 0 26 3200K+ 0B 0B 10213
10206 bash 0.0 00:00.01 1 0 21 764K 0B 0B 10206
10205 login 0.0 00:00.08 2 1 30 1068K 0B 0B 10205
10204 Terminal 14.8 00:01.20 9 4 273+ 46M+ 6700K- 0B 10204
10063 CVMCompiler 0.0 00:00.01 2 2 28 3260K 8192B 0B 10063
10060 VTDecoderXPC 0.0 00:00.40 2 1 53 4808K 0B 0B 10060
10028 Google Chrom 0.0 00:00.10 13 1 92 13M 4096B 0B 9965
10027 Google Chrom 4.3 00:21.00 17 2 126 52M 4096B 0B 9965
10026 Google Chrom 0.0 00:01.18 14 2 110 20M 4096B 0B 9965
10023 Google Chrom 0.0 00:01.35 13 1 118 27M 4096B 0B 9965
9995 Google Chrom 0.0 00:01.88 14 1 120 42M 4096B 0B 9965
9991 Google Chrom 3.2 00:55.79 18 1 153 276M 12K 0B 9965
9979 Google Chrom 0.0 00:05.64 14 2 109 108M 4096B 0B 9965
Nov 8 10:59:28 severin kernel: [ 0.000000] KERNEL supported cpus:
Nov 8 10:59:28 severin kernel: [ 0.000000] Intel GenuineIntel
Nov 8 10:59:28 severin kernel: [ 0.000000] AMD AuthenticAMD
Nov 8 10:59:28 severin kernel: [ 0.000000] Centaur CentaurHauls
Nov 8 10:59:28 severin kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Nov 8 10:59:28 severin kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Nov 8 10:59:28 severin kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Nov 8 10:59:28 severin kernel: [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Nov 8 10:59:28 severin kernel: [ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Nov 8 10:59:28 severin kernel: [ 0.000000] e820: BIOS-provided physical RAM map:
Nov 8 10:59:28 severin kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
Nov 8 10:59:28 severin kernel: [ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
Nov 8 10:59:28 severin kernel: [ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
Nov 8 10:59:28 severin kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000dffeffff] usable
Nov 8 10:59:28 severin systemd-modules-load[264]: Inserted module 'lp'
Nov 8 10:59:28 severin systemd-modules-load[264]: Inserted module 'ppdev'
Nov 8 10:59:28 severin systemd-modules-load[264]: Inserted module 'parport_pc'
Nov 8 10:59:28 severin systemd[1]: Starting Flush Journal to Persistent Storage...
Nov 8 10:59:28 severin systemd[1]: Starting udev Kernel Device Manager...
Nov 8 10:59:28 severin systemd[1]: Started Flush Journal to Persistent Storage.
Nov 8 10:59:28 severin loadkeys[263]: Lade /etc/console-setup/cached.kmap.gz.
Nov 8 10:59:28 severin systemd[1]: Started Set console keymap.
Nov 8 10:59:28 severin systemd[1]: Reached target Local File Systems (Pre).
Nov 8 10:59:28 severin systemd[1]: Reached target Local File Systems.
Nov 8 10:59:28 severin systemd[1]: Starting Enable support for additional executable binary formats...
Nov 8 10:59:28 severin systemd[1]: Starting Create Volatile Files and Directories...
Nov 8 10:59:28 severin systemd[1]: Starting Set console font and keymap...
Nov 8 10:59:28 severin systemd[1]: Starting LSB: AppArmor initialization...
Nov 8 10:59:28 severin systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Nov 8 10:59:28 severin systemd[1]: Starting Clean up any mess left by 0dns-up...
Nov 8 10:59:28 severin systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 298 (update-binfmts)
Nov 8 10:59:28 severin systemd-tmpfiles[299]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Nov 8 10:59:28 severin systemd[1]: Mounting Arbitrary Executable File Formats File System...
Nov 8 10:59:28 severin systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
Nov 8 10:59:28 severin systemd[1]: Mounted Arbitrary Executable File Formats File System.
Nov 8 10:59:28 severin systemd[1]: Started udev Coldplug all Devices.
Nov 8 10:59:28 severin systemd[1]: Started Enable support for additional executable binary formats.
Nov 8 10:59:28 severin systemd[1]: Started Clean up any mess left by 0dns-up.
Nov 8 10:59:28 severin systemd[1]: Starting Nameserver information manager...
Nov 8 10:59:28 severin systemd[1]: Started Nameserver information manager.
Nov 8 10:59:28 severin systemd[1]: Reached target Network (Pre).
Nov 8 10:59:28 severin systemd[1]: Started Create Volatile Files and Directories.
Nov 8 10:59:28 severin systemd[1]: Starting Network Time Synchronization...
Nov 8 10:59:28 severin kernel: [ 0.000000] BIOS-e820: [mem 0x00000000dfff0000-0x00000000dfffffff] ACPI data
Nov 8 10:59:28 severin kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Nov 8 10:59:28 severin kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Nov 8 10:59:28 severin kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
Nov 8 10:59:28 severin kernel: [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000002402fffff] usable
Nov 8 10:59:28 severin kernel: [ 0.000000] NX (Execute Disable) protection: active
Nov 8 10:59:28 severin kernel: [ 0.000000] SMBIOS 2.5 present.
Nov 8 10:59:28 severin kernel: [ 0.000000] DMI: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Nov 8 10:59:28 severin kernel: [ 0.000000] Hypervisor detected: KVM
Nov 8 10:59:28 severin kernel: [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov 8 10:59:28 severin kernel: [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov 8 10:59:28 severin kernel: [ 0.000000] e820: last_pfn = 0x240300 max_arch_pfn = 0x400000000
Nov 8 10:59:28 severin rsyslogd-2039: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ]
Nov 8 10:59:28 severin rsyslogd-2007: action 'action 10' suspended, next retry is Thu Nov 8 10:59:58 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Nov 8 10:59:28 severin kernel: [ 0.000000] MTRR default type: uncachable
Nov 8 10:59:28 severin kernel: [ 0.000000] MTRR variable ranges disabled:
Nov 8 10:59:28 severin kernel: [ 0.000000] MTRR: Disabled
Nov 8 10:59:28 severin kernel: [ 0.000000] x86/PAT: MTRRs disabled, skipping PAT initialization too.
Nov 8 10:59:28 severin kernel: [ 0.000000] CPU MTRRs all blank - virtualized system.
Nov 8 10:59:28 severin kernel: [ 0.000000] x86/PAT: Configuration [0-7]: WB WT UC- UC WB WT UC- UC
Nov 8 10:59:28 severin kernel: [ 0.000000] e820: last_pfn = 0xdfff0 max_arch_pfn = 0x400000000
Nov 8 10:59:28 severin kernel: [ 0.000000] found SMP MP-table at [mem 0x0009fff0-0x0009ffff] mapped at [ (ptrval)]
Nov 8 10:59:28 severin kernel: [ 0.000000] Scanning 1 areas for low memory corruption
Nov 8 10:59:28 severin kernel: [ 0.000000] Base memory trampoline at [ (ptrval)] 99000 size 24576
Nov 8 10:59:28 severin kernel: [ 0.000000] BRK [0x18cf3f000, 0x18cf3ffff] PGTABLE
Nov 8 10:59:28 severin kernel: [ 0.000000] BRK [0x18cf40000, 0x18cf40fff] PGTABLE
Nov 8 10:59:28 severin kernel: [ 0.000000] BRK [0x18cf41000, 0x18cf41fff] PGTABLE
Nov 8 10:59:28 severin kernel: [ 0.000000] BRK [0x18cf42000, 0x18cf42fff] PGTABLE
Nov 8 10:59:28 severin kernel: [ 0.000000] BRK [0x18cf43000, 0x18cf43fff] PGTABLE