fdae6bca88
- Update to version 194 (jsc#PED-4218): * client.c: fix build w/ musl libc * mcelog: New model number for Arrowlake * mcelog: Don't overwrite model number when lookup fails * mcelog: Add Graniterapids, Grandridge and Sierraforest * mcelog: New model number for Lunarlake * mcelog: Add Emerald Rapids * mcelog: Add decode support for Sapphire Rapids * Update PFA_test_howto * mcelog: Add support for Meteor Lake - Includes following SLE 15 SP5 jira features: * jsc#PED-671 mcelog: Update to latest release * jsc#PED-686 [CPU Features] Update mcelog support for ADL-N * jsc#PED-638 [CPU Features] Update mcelog support for MTL-P - Update to version 189: * mcelog: Add another Raptor Lake CPU model * Fix generation of cputype files * mcelog: Add missing model numbers for Broadwell and Raptorlake * mcelog: Makefile: Only touch cputype.h if needed to create it * Makefile: add install-nodoc target * Use env as the shebang target * Add missing dependencies for cputype include files * mcelog: Reverse sens of check to call resolveaddr() * mcelog: Reverse the sense of the check to set memory_error_support * mcelog: Drop CASE_INTEL define * mcelog: Generate cpu_choices[] from table * mcelog: Generate the cputype_name[] array from the table * mcelog: Add CPU model numbers to table and generate switch function * mcelog: Generate CPU_* enums from a table OBS-URL: https://build.opensuse.org/request/show/1093247 OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/mcelog?expand=0&rev=62 |
||
---|---|---|
_service | ||
_servicedata | ||
.gitattributes | ||
.gitignore | ||
add_new_amd_cpu_defines | ||
add-f10h-support.patch | ||
add-f11h-support.patch | ||
add-f12h-support.patch | ||
add-f14h-support.patch | ||
add-f15h-support.patch | ||
add-f16h-support.patch | ||
email.patch | ||
fix_setgroups_missing_call.patch | ||
mcelog_invert_prefill_db_warning.patch | ||
mcelog-194.obscpio | ||
mcelog-socket-path.patch | ||
mcelog.changes | ||
mcelog.obsinfo | ||
mcelog.spec | ||
mcelog.sysconfig | ||
mcelog.systemd | ||
mcelog.tmpfiles | ||
README.email_setup | ||
Start-consolidating-AMD-specific-stuff.patch |
MACHINE CHECK EXCPETION NOTIFICATION VIA EMAIL ============================================== (C)opyright by Thomas Renninger <trenn@suse.de> Novell Inc. 2010 The setup to send Machine Check Exceptions (MCEs) via email relies on a working smtp server listening on localhost on port 25. How this can easily be configured is can be read up here: http://en.opensuse.org/Mail_server_HOWTO in the "Outgoing" section. Test your setup by trying to send test mails via the "mail" shell command, included in the mailx package. Specify the email address where the MCEs should get mailed to here: /etc/sysconfig/mcelog You can filter MCE mails by matching against these mail headers. Either one of these headers are set: - X-Mcelog-Uncorrectable - X-Mcelog-Correctable and one of these are set: - X-Mcelog-Memory - X-Mcelog-CPU - X-Mcelog-Misc NOTE: If broken HW results in an MCE storm of dozens and hundreds of MCEs, mcelog will not sending them all to not overload the machine and network traffic. If in doubt, check the local mcelog log files. Autoyast -------- For people making use of autoyast to spread similar installations on multiple machines, here are some hints how to set up the email notification through autoyast. Please read the autoyast documentation first if you are not familiar with how to create an autoyast.xml file. This simply sets the email address, notifications should get send to: <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>MCELOG_ADMIN_EMAIL</sysconfig_key> <sysconfig_path>/etc/sysconfig/mcelog</sysconfig_path> <sysconfig_value>trenn@suse.de</sysconfig_value> </sysconfig_entry> </sysconfig> This is an example of how to set up postfix to listen on localhost and sending/forwarding all mails coming in there through the smtp server relay.suse.de. The alias at the beginning forwards local machine notifications sent to root, to trenn@suse.de. Like that mails interesting for the administrator can easily be collected and sent to one email address. But this is just one possible mail set up example. <mail> <aliases config:type="list"> <alias> <alias>root</alias> <destinations>trenn@suse.de</destinations> </alias> </aliases> <connection_type config:type="symbol">permanent</connection_type> <listen_remote config:type="boolean">false</listen_remote> <masquerade_other_domains config:type="list"> <domain>suse.de</domain> </masquerade_other_domains> <mta config:type="symbol">postfix</mta> <outgoing_mail_server>relay.suse.de</outgoing_mail_server> <postfix_mda config:type="symbol">local</postfix_mda> <use_amavis config:type="boolean">false</use_amavis> </mail>