Public bug reported: For Haswell systems, Intel has created a new tool called 'intel_l3_parity'. They have requested that we use this so that we can make use of the l3 parity feature on these cards. Quote:
DPF (L3 Parity): Haswell has extra cache which can be dynamically (during run time) used to replace cachelines which are exhibiting faulty behavior. It follows that Haswell also has the ability to detect the errors. Kernel driver receives the error interrupts and reports them to userspace via udev. The event is a parity error. Userspace should be listening for the udev events, and handling them in whatever way they see fit. We expected OSVs to add such hooks to their distributions, and use the intel_l3_parity tool to be invoked by their udev rules as needed. The code for the binary can be found here, it looks like they're planning on adding it to the linux kernel tree but afact it's not in Linus' tree yet: http://article.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/10847/match=intel_l3_parity Also I haven't seen a udev script from them as yet. According to Intel the way it works is that udev has to catch the party check and then do the right thing by calling intel_l3_parity the right way. ** Affects: intel Importance: Low Assignee: Rodrigo-vivi (rodrigo-vivi) Status: Confirmed ** Affects: udev (Ubuntu) Importance: Undecided Status: New ** Description changed: For Haswell systems, Intel has created a new tool called 'intel_l3_parity'. They have requested that we use this so that we can make use of the l3 parity feature on these cards. Quote: + DPF (L3 Parity): Haswell has extra cache which can be dynamically (during run time) + used to replace cachelines which are exhibiting faulty behavior. - DPF (L3 Parity): Haswell has extra cache which can be dynamically (during run time) used to replace cachelines which are exhibiting faulty behavior. + It follows that Haswell also has the ability to detect the errors. - It follows that Haswell also has the ability to detect the errors. + Kernel driver receives the error interrupts and reports them to userspace via udev. + The event is a parity error. - Kernel driver receives the error interrupts and reports them to - userspace via udev. The event is a parity error. + Userspace should be listening for the udev events, and handling them in whatever way + they see fit. - - Userspace should be listening for the udev events, and handling them - in whatever way they see fit. - - We expected OSVs to add such hooks to their distributions, and use the - intel_l3_parity tool to be invoked by their udev rules as needed. + We expected OSVs to add such hooks to their distributions, and use the intel_l3_parity + tool to be invoked by their udev rules as needed. The code for the binary can be found here, it looks like they're planning on adding it to the linux kernel tree but afact it's not in Linus' tree yet: http://article.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/10847/match=intel_l3_parity Also I haven't seen a udev script from them as yet. According to Intel the way it works is that udev has to catch the party check and then do the right thing by calling intel_l3_parity the right way. ** Also affects: udev (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234260 Title: Package and use 'intel_l3_parity' binary To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1234260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
