Re: SuperMicro A2SDi-4C-HLN4F
Sat, 18 Aug 2018 12:28:17 + Rupert Gallagher > I am not complaining about obsd. > > I am complaining about your FUD on C3000 and your request for a > post-installation dmesg. No installation is possible for lack of disk > drivers. I do not develop/port drivers. The dmesgs I already posted > are all I can share. > > The only way to run obsd at this time is via qemu/proxmox or > vmware/esxi. Rupert, You would not have to complain if you hadn't spammed your puny pretences. The boards and processors have issues to be known, accompanying warnings. The dmesg you posted does not help anything. It looks like a poorly done commercial for other operating systems that "supposedly" work. Only, you have not been running anything past boot up. Accept it, you are a troll. Looks like you point out there are "drivers to be written", for your use. I call this helpless whining. I told you how you can help this process.. Get the boards in the hands of developers with OpenBSD who write drivers. And first kindly ask about it whether it is possible to fit in busy work. Kind regards, Anton Lazarov > On Sat, Aug 18, 2018 at 12:55, wrote: > > > Sat, 18 Aug 2018 08:29:33 + Rupert Gallagher > >> Orher architectures are explicitly known for being bugged, but this > >> did not stop the developers. > > > > Hi Rupert, > > > > Enough already, just post a full dmesg when you can. The hardware is not > > perfect, watch out for unfixed CPU bugs as these are soldered down chips. > > > > They also include a lot more than the CPU where most of the problems are. > > So keep an eye on these boards and be a bit more impartial and objective. > > > > It would be so nice if you could ship new boards like these to developers > > or donate some of your excess hardware costs so that they get the boards. > > > > That might be much more helpful than complaints over the installer dmesg. > > > > Kind regards, > > Anton Lazarov > > > >> On Fri, Aug 17, 2018 at 22:09, wrote: > >> > >> > Fri, 17 Aug 2018 16:48:52 + Rupert Gallagher > >> >> This is a really nice board at a really nice price, and you should > >> >> stop scaring people off. These Atoms are cleaner than both Cores and > >> >> Xeons, and AMDs have have their fair share of problems. Citin g > >> >> C2000 against the latest C3000 is FUD. You should come clean first, > >> >> and cite a comparable server board at a comparable cost and clear of > >> >> bugs. > >> > > >> > Rupert, > >> > > >> > The publication and processor specifications are about the C3000 CPU bug. > >> > Similar hardware flaws affect the new C3000 CPUs, same microarchitecture. > >> > These Atoms are also fully affected by Intel HW flaws Spectre & Meltdown. > >> > > >> > With NONE real hardware understanding, you have to rely upon vendor spec. > >> > With NONE single dmesg after installation, you can NOT advise this board. > >> > With NONE real OpenBSD experience, you better ask the developers instead. > >> > > >> > You are speculatively advertising yet unsupported boards as feature sets. > >> > Not interested reading anything that pops in your visibility on the list. > >> > It takes very little effort to have some opinion and I do NOT want yours. > >> > > >> > Kind regards, > >> > Anton Lazarov > >> > > >> >> On Fri, Aug 17, 2018 at 17:38, wrote: > >> >> > >> >> > Fri, 17 Aug 2018 11:15:32 + Rupert Gallagher > >> >> > > >> >> >> FUD > >> >> >> > >> >> >> Sent from total and utter ignorance. > >> >> > > >> >> > Rupert, > >> >> > > >> >> > Plus the dmesg you posted is by the RAM disk installation OpenBSD > >> >> > kernel. You Should complete an actual OpenBSD installation to get > >> >> > the full dmesg. > >> >> >> On Fri, Aug 17, 2018 at 12:24, wrote: > >> >> >> > >> >> >> > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher > >> >> >> > > >> >> >> >> Using the serial over lan console, the keyboard keeps working, > >> >> >> >> and it is possible to enter the shell. Using the standard > >> >> >> >> console, the keyboard does not work. There is plenty of drivers > >> >> >> >> that need to be written. No, I do not write/port drivers. > >> >> >> >> > >> >> >> >> By comparison, both freebsd and centos linux just work out of > >> >> >> >> the box. Both dmesgs are attached as reference. > >> >> >> >> > >> >> >> >> The board is really nice. > >> >> >> >> > >> >> >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher > >> >> >> >> wrote: > >> >> >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm > >> >> >> >> > > >> >> >> > > >> >> >> > Hi misc@, > >> >> >> > > >> >> >> > This one is much quieter, the vendors have reacted to the > >> >> >> > previous flaw. As nice as it can get.. before trusting > >> >> >> > non-technical reviews, be aware: > >> >> >> > > >> >> >> > https://en.wikipedia.org/wiki/Goldmont#Erratum > >> >> >> > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ > >> >> >> >
DUID changed?
So, today I was installing recent patches on my firewall box (a Dell R210-II) using openup/syspatch. After the reboot, it complained that it couldn't find [DUID].b for swap. After some panic, reboots, powercycles, etc. I realized that the DUID in fstab didn't match the DUID that was being used for /. I updated fstab to match, and everything is back to normal. Does anyone know how I might have done this, or how I can prevent it? BTW thanks for /bsd.booted. That made it easy to figure out the patch wasn't to blame. disklabel.sd0.backup: # /dev/rsd0c: type: SCSI disk: SCSI disk label: ST1000NM0011 duid: a0debfbdc4b3991a flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 121601 total sectors: 1953525168 boundstart: 64 boundend: 1953520065 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 2097152 64 4.2BSD 2048 16384 1 # / b: 17206720 2097216swap# none c: 19535251680 unused d: 8388608 19303936 4.2BSD 2048 16384 1 # /tmp e: 41753472 27692544 4.2BSD 2048 16384 1 # /var f: 4194304 69446016 4.2BSD 2048 16384 1 # /usr g: 2097152 73640320 4.2BSD 2048 16384 1 # /usr/X11R6 h: 20971520 75737472 4.2BSD 2048 16384 1 # /usr/local i: 4195264 96708992 4.2BSD 2048 16384 1 # /usr/src j: 41929632100904256 4.2BSD 2048 16384 1 # /home k: 41929664142833888 4.2BSD 2048 16384 1 # /usr/ports l: 4192960184763552 4.2BSD 2048 16384 1 # /usr/obj m:150994944188956512 4.2BSD 2048 16384 1 # /home/squidcache disklabel.sd0.current: # /dev/rsd0c: type: SCSI disk: SCSI disk label: ST1000NM0011 duid: 5b645952b882641e flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 121601 total sectors: 1953525168 boundstart: 64 boundend: 1953520065 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 2097152 64 4.2BSD 2048 16384 1 b: 17206720 2097216swap c: 19535251680 unused d: 8388608 19303936 4.2BSD 2048 16384 1 e: 41753472 27692544 4.2BSD 2048 16384 1 f: 4194304 69446016 4.2BSD 2048 16384 1 g: 2097152 73640320 4.2BSD 2048 16384 1 h: 20971520 75737472 4.2BSD 2048 16384 1 i: 4195264 96708992 4.2BSD 2048 16384 1 j: 41929632100904256 4.2BSD 2048 16384 1 k: 41929664142833888 4.2BSD 2048 16384 1 l: 4192960184763552 4.2BSD 2048 16384 1 m:150994944188956512 4.2BSD 2048 16384 1 (Where are the mount points? Does that matter?) dmesg: OpenBSD 6.3 (GENERIC.MP) #8: Sat Aug 4 16:56:56 CEST 2018 r...@syspatch-63-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8541405184 (8145MB) avail mem = 8275464192 (7892MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe6670 (57 entries) bios0: vendor Dell Inc. version "2.8.0" date 06/24/2014 bios0: Dell Inc. PowerEdge R210 II acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP SPMI DMAR ASF! HPET APIC MCFG WDAT BOOT SSDT ASPT SSDT SSDT HEST ERST BERT EINJ acpi0: wakeup devices P0P1(S4) GLAN(S0) EHC1(S4) EHC2(S4) XHC_(S4) PXSX(S4) RP01(S5) PXSX(S4) RP02(S5) PXSX(S4) RP03(S5) PXSX(S4) RP04(S5) PXSX(S4) RP05(S5) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E31260L @ 2.40GHz, 2394.92 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache acpihpet0: recalibrated TSC frequency 2394560655 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Xeon(R) CPU E31260L @ 2.40GHz, 2394.56 MHz cpu1:
Re: SuperMicro A2SDi-4C-HLN4F
I am not complaining about obsd. I am complaining about your FUD on C3000 and your request for a post-installation dmesg. No installation is possible for lack of disk drivers. I do not develop/port drivers. The dmesgs I already posted are all I can share. The only way to run obsd at this time is via qemu/proxmox or vmware/esxi. On Sat, Aug 18, 2018 at 12:55, wrote: > Sat, 18 Aug 2018 08:29:33 + Rupert Gallagher >> Orher architectures are explicitly known for being bugged, but this >> did not stop the developers. > > Hi Rupert, > > Enough already, just post a full dmesg when you can. The hardware is not > perfect, watch out for unfixed CPU bugs as these are soldered down chips. > > They also include a lot more than the CPU where most of the problems are. > So keep an eye on these boards and be a bit more impartial and objective. > > It would be so nice if you could ship new boards like these to developers > or donate some of your excess hardware costs so that they get the boards. > > That might be much more helpful than complaints over the installer dmesg. > > Kind regards, > Anton Lazarov > >> On Fri, Aug 17, 2018 at 22:09, wrote: >> >> > Fri, 17 Aug 2018 16:48:52 + Rupert Gallagher >> >> This is a really nice board at a really nice price, and you should >> >> stop scaring people off. These Atoms are cleaner than both Cores and >> >> Xeons, and AMDs have have their fair share of problems. Citin g >> >> C2000 against the latest C3000 is FUD. You should come clean first, >> >> and cite a comparable server board at a comparable cost and clear of >> >> bugs. >> > >> > Rupert, >> > >> > The publication and processor specifications are about the C3000 CPU bug. >> > Similar hardware flaws affect the new C3000 CPUs, same microarchitecture. >> > These Atoms are also fully affected by Intel HW flaws Spectre & Meltdown. >> > >> > With NONE real hardware understanding, you have to rely upon vendor spec. >> > With NONE single dmesg after installation, you can NOT advise this board. >> > With NONE real OpenBSD experience, you better ask the developers instead. >> > >> > You are speculatively advertising yet unsupported boards as feature sets. >> > Not interested reading anything that pops in your visibility on the list. >> > It takes very little effort to have some opinion and I do NOT want yours. >> > >> > Kind regards, >> > Anton Lazarov >> > >> >> On Fri, Aug 17, 2018 at 17:38, wrote: >> >> >> >> > Fri, 17 Aug 2018 11:15:32 + Rupert Gallagher >> >> > >> >> >> FUD >> >> >> >> >> >> Sent from total and utter ignorance. >> >> > >> >> > Rupert, >> >> > >> >> > Plus the dmesg you posted is by the RAM disk installation OpenBSD >> >> > kernel. You Should complete an actual OpenBSD installation to get >> >> > the full dmesg. >> >> >> On Fri, Aug 17, 2018 at 12:24, wrote: >> >> >> >> >> >> > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher >> >> >> > >> >> >> >> Using the serial over lan console, the keyboard keeps working, >> >> >> >> and it is possible to enter the shell. Using the standard >> >> >> >> console, the keyboard does not work. There is plenty of drivers >> >> >> >> that need to be written. No, I do not write/port drivers. >> >> >> >> >> >> >> >> By comparison, both freebsd and centos linux just work out of >> >> >> >> the box. Both dmesgs are attached as reference. >> >> >> >> >> >> >> >> The board is really nice. >> >> >> >> >> >> >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher >> >> >> >> wrote: >> >> >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm >> >> >> > >> >> >> > Hi misc@, >> >> >> > >> >> >> > This one is much quieter, the vendors have reacted to the >> >> >> > previous flaw. As nice as it can get.. before trusting >> >> >> > non-technical reviews, be aware: >> >> >> > >> >> >> > https://en.wikipedia.org/wiki/Goldmont#Erratum >> >> >> > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ >> >> >> > https://www.google.com/search?q=intel+c3000+bug >> >> >> > >> >> >> > Recurring issue - similar problems were discussed noisily >> >> >> > industry wide: >> >> >> > >> >> >> > https://en.wikipedia.org/wiki/Silvermont#Erratum >> >> >> > https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/ >> >> >> > https://www.servethehome.com/intel-atom-c2000-c0-stepping-fixing-the-avr54-bug/ >> >> >> > https://www.google.com/search?q=intel+c2000+bug >> >> >> > >> >> >> > As with the previous generation processors and main boards, >> >> >> > Intel FAILS. Wait for updated CPU revision boards, consult techs >> >> >> > and prepare for RMA. >> >> >> > >> >> >> > Kind regards, >> >> >> > Anton Lazarov >> >> > >> >> > "Similar to previous Silvermont generation design flaws were found >> >> > in processor circuitry resulting in cease of operation when >> >> > processors are actively used for several years. Errata named >> >> > >> >> > APL47 System May Experience Inability to Boot or May Cease Operation >> >> > >> >> > and
Re: SuperMicro A2SDi-4C-HLN4F
Sat, 18 Aug 2018 08:29:33 + Rupert Gallagher > Orher architectures are explicitly known for being bugged, but this > did not stop the developers. Hi Rupert, Enough already, just post a full dmesg when you can. The hardware is not perfect, watch out for unfixed CPU bugs as these are soldered down chips. They also include a lot more than the CPU where most of the problems are. So keep an eye on these boards and be a bit more impartial and objective. It would be so nice if you could ship new boards like these to developers or donate some of your excess hardware costs so that they get the boards. That might be much more helpful than complaints over the installer dmesg. Kind regards, Anton Lazarov > On Fri, Aug 17, 2018 at 22:09, wrote: > > > Fri, 17 Aug 2018 16:48:52 + Rupert Gallagher > >> This is a really nice board at a really nice price, and you should > >> stop scaring people off. These Atoms are cleaner than both Cores and > >> Xeons, and AMDs have have their fair share of problems. Citin g > >> C2000 against the latest C3000 is FUD. You should come clean first, > >> and cite a comparable server board at a comparable cost and clear of > >> bugs. > > > > Rupert, > > > > The publication and processor specifications are about the C3000 CPU bug. > > Similar hardware flaws affect the new C3000 CPUs, same microarchitecture. > > These Atoms are also fully affected by Intel HW flaws Spectre & Meltdown. > > > > With NONE real hardware understanding, you have to rely upon vendor spec. > > With NONE single dmesg after installation, you can NOT advise this board. > > With NONE real OpenBSD experience, you better ask the developers instead. > > > > You are speculatively advertising yet unsupported boards as feature sets. > > Not interested reading anything that pops in your visibility on the list. > > It takes very little effort to have some opinion and I do NOT want yours. > > > > Kind regards, > > Anton Lazarov > > > >> On Fri, Aug 17, 2018 at 17:38, wrote: > >> > >> > Fri, 17 Aug 2018 11:15:32 + Rupert Gallagher > >> > > >> >> FUD > >> >> > >> >> Sent from total and utter ignorance. > >> > > >> > Rupert, > >> > > >> > Plus the dmesg you posted is by the RAM disk installation OpenBSD > >> > kernel. You Should complete an actual OpenBSD installation to get > >> > the full dmesg. > >> >> On Fri, Aug 17, 2018 at 12:24, wrote: > >> >> > >> >> > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher > >> >> > > >> >> >> Using the serial over lan console, the keyboard keeps working, > >> >> >> and it is possible to enter the shell. Using the standard > >> >> >> console, the keyboard does not work. There is plenty of drivers > >> >> >> that need to be written. No, I do not write/port drivers. > >> >> >> > >> >> >> By comparison, both freebsd and centos linux just work out of > >> >> >> the box. Both dmesgs are attached as reference. > >> >> >> > >> >> >> The board is really nice. > >> >> >> > >> >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher > >> >> >> wrote: > >> >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm > >> >> >> > > >> >> > > >> >> > Hi misc@, > >> >> > > >> >> > This one is much quieter, the vendors have reacted to the > >> >> > previous flaw. As nice as it can get.. before trusting > >> >> > non-technical reviews, be aware: > >> >> > > >> >> > https://en.wikipedia.org/wiki/Goldmont#Erratum > >> >> > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ > >> >> > https://www.google.com/search?q=intel+c3000+bug > >> >> > > >> >> > Recurring issue - similar problems were discussed noisily > >> >> > industry wide: > >> >> > > >> >> > https://en.wikipedia.org/wiki/Silvermont#Erratum > >> >> > https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/ > >> >> > https://www.servethehome.com/intel-atom-c2000-c0-stepping-fixing-the-avr54-bug/ > >> >> > https://www.google.com/search?q=intel+c2000+bug > >> >> > > >> >> > As with the previous generation processors and main boards, > >> >> > Intel FAILS. Wait for updated CPU revision boards, consult techs > >> >> > and prepare for RMA. > >> >> > > >> >> > Kind regards, > >> >> > Anton Lazarov > >> > > >> > "Similar to previous Silvermont generation design flaws were found > >> > in processor circuitry resulting in cease of operation when > >> > processors are actively used for several years. Errata named > >> > > >> > APL47 System May Experience Inability to Boot or May Cease Operation > >> > > >> > and > >> > > >> > APL48 System May Experience Non-functioning GPIO Weak Pull-up > >> > Circuitry > >> > > >> > were added to documentation in June 2017 stating: > >> > > >> > The Low Pin Count (LPC), Real-Time Clock (RTC), Secure Digital (SD) > >> > card and General-Purpose Input/Output (GPIO) interfaces may stop > >> > functioning. > >> > > >> > The documents cited in the Wikipedia article, see for current > >> > versions.. that apply to the later CPU
Re: SuperMicro A2SDi-4C-HLN4F
I can pay you with your same currency. You have no experience installing openbsd on a new architecture: > Available disks are: none Your references are not specific to the C3000 architecture. Orher architectures are explicitly known for being bugged, but this did not stop the developers. On Fri, Aug 17, 2018 at 22:09, wrote: > Fri, 17 Aug 2018 16:48:52 + Rupert Gallagher >> This is a really nice board at a really nice price, and you should >> stop scaring people off. These Atoms are cleaner than both Cores and >> Xeons, and AMDs have have their fair share of problems. Citin g >> C2000 against the latest C3000 is FUD. You should come clean first, >> and cite a comparable server board at a comparable cost and clear of >> bugs. > > Rupert, > > The publication and processor specifications are about the C3000 CPU bug. > Similar hardware flaws affect the new C3000 CPUs, same microarchitecture. > These Atoms are also fully affected by Intel HW flaws Spectre & Meltdown. > > With NONE real hardware understanding, you have to rely upon vendor spec. > With NONE single dmesg after installation, you can NOT advise this board. > With NONE real OpenBSD experience, you better ask the developers instead. > > You are speculatively advertising yet unsupported boards as feature sets. > Not interested reading anything that pops in your visibility on the list. > It takes very little effort to have some opinion and I do NOT want yours. > > Kind regards, > Anton Lazarov > >> On Fri, Aug 17, 2018 at 17:38, wrote: >> >> > Fri, 17 Aug 2018 11:15:32 + Rupert Gallagher >> > >> >> FUD >> >> >> >> Sent from total and utter ignorance. >> > >> > Rupert, >> > >> > Plus the dmesg you posted is by the RAM disk installation OpenBSD >> > kernel. You Should complete an actual OpenBSD installation to get >> > the full dmesg. >> >> On Fri, Aug 17, 2018 at 12:24, wrote: >> >> >> >> > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher >> >> > >> >> >> Using the serial over lan console, the keyboard keeps working, >> >> >> and it is possible to enter the shell. Using the standard >> >> >> console, the keyboard does not work. There is plenty of drivers >> >> >> that need to be written. No, I do not write/port drivers. >> >> >> >> >> >> By comparison, both freebsd and centos linux just work out of >> >> >> the box. Both dmesgs are attached as reference. >> >> >> >> >> >> The board is really nice. >> >> >> >> >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher >> >> >> wrote: >> >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm >> >> > >> >> > Hi misc@, >> >> > >> >> > This one is much quieter, the vendors have reacted to the >> >> > previous flaw. As nice as it can get.. before trusting >> >> > non-technical reviews, be aware: >> >> > >> >> > https://en.wikipedia.org/wiki/Goldmont#Erratum >> >> > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ >> >> > https://www.google.com/search?q=intel+c3000+bug >> >> > >> >> > Recurring issue - similar problems were discussed noisily >> >> > industry wide: >> >> > >> >> > https://en.wikipedia.org/wiki/Silvermont#Erratum >> >> > https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/ >> >> > https://www.servethehome.com/intel-atom-c2000-c0-stepping-fixing-the-avr54-bug/ >> >> > https://www.google.com/search?q=intel+c2000+bug >> >> > >> >> > As with the previous generation processors and main boards, >> >> > Intel FAILS. Wait for updated CPU revision boards, consult techs >> >> > and prepare for RMA. >> >> > >> >> > Kind regards, >> >> > Anton Lazarov >> > >> > "Similar to previous Silvermont generation design flaws were found >> > in processor circuitry resulting in cease of operation when >> > processors are actively used for several years. Errata named >> > >> > APL47 System May Experience Inability to Boot or May Cease Operation >> > >> > and >> > >> > APL48 System May Experience Non-functioning GPIO Weak Pull-up >> > Circuitry >> > >> > were added to documentation in June 2017 stating: >> > >> > The Low Pin Count (LPC), Real-Time Clock (RTC), Secure Digital (SD) >> > card and General-Purpose Input/Output (GPIO) interfaces may stop >> > functioning. >> > >> > The documents cited in the Wikipedia article, see for current >> > versions.. that apply to the later CPU stepping models, if any, as >> > time progresses: >> > >> > https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/pentium-celeron-n-series-j-series-datasheet-spec-update.pdf >> > https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/atom-c3000-family-spec-update.pdf >> > >> > APL47 Problem: Under certain conditions LPC, SD card and RTC >> > circuitry may stop functioning in the outer years of use. >> > >> > APL48 Problem: When platform drives the GPIO pin low, GPIOs >> > programmed with weak pull-up circuitry may not maintain a value >> > above VIH when not actively driven in outer years of service."
