On Sun, 2003-01-12 at 16:58, Rob Wilkens wrote: > The hardware engineers, in my experience, will not refer to those issues > as bugs, but rather as misdocumented features... No? I mean if an > errata is enough to work around the problem, then the documentation was > clearly the problem, and not the hardware implementation. Intel seperate out things that are docmentation errors, clarifications and actual bugs. They publish regular errata documents listing these, and when they do decide to turn a flaw into a specification update they document that too. AMD likewise. Some vendors may not do this, but the x86 CPU vendors seem to do a good job. > As per the microcode updates, I noticed RedHat 8 was autoupdating > microcode on each boot IIRC. I've since switched to Debian and don't > know that it does this. Should I be concerned? It depends on your chip revisions. For example the O(1) scheduler will trigger very occasional random crashes or reboots with early PII Xeon microcode sets. I'm sure Debian has a package for this somewhere. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: Intel And Kenrel ProgrammingSamuli Suonpaa
- Re: Nvidia and its choice to read the GPL "differently"Chuck Wolber
- Intel And Kenrel Programming (was: Nvidia is a great company)Rob Wilkens
- Re: Intel And Kenrel Programming (was: Nvidia is a great company)Alan Cox
- Re: Intel And Kenrel Programming (was: Nvidia is a great company)Rob Wilkens
- Prev by Date: Re: Intel And Kenrel Programming (was: Nvidia is a great company)
- Next by Date: Re: any chance of 2.6.0-test*?
- Previous by thread: Re: Intel And Kenrel Programming (was: Nvidia is a great company)
- Next by thread: Re: Intel And Kenrel Programming
- Indexes:[Main][Thread]