Your message dated Thu, 20 Feb 2014 16:21:40 +0600
with message-id <[email protected]>
and subject line Re: Bug#739595: mcelog 100-1 does not recognize AMD CPUs 
properly
has caused the Debian Bug report #739595,
regarding mcelog 100-1 does not recognize AMD CPUs properly
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
739595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739595
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mcelog
Version: 100-1
Architecture: i386
Severity: important

I think this is what caused #738927 to be noticed, but this is a separate issue.

# strace -efile,read,ioctl,exit_group mcelog         
execve("/usr/sbin/mcelog", ["mcelog"], [/* 15 vars */]) = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/i386-linux-gnu/i686/cmov/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300\213^B4\0\0\0"..., 
512) = 512
open("/etc/mcelog/mcelog.conf", O_RDONLY) = 3
read(3, "#\n# Example config file for mcel"..., 4096) = 4096
read(3, "the hardware does not report DIM"..., 4096) = 1966
read(3, "", 4096)                       = 0
open("/proc/cpuinfo", O_RDONLY)         = 3
read(3, "processor\t: 0\nvendor_id\t: Authen"..., 1024) = 1024
mcelog: AMD Processor family 16: Please load edac_mce_amd module.
: Success
CPU is unsupported
exit_group(1)                           = ?

The error message appears to be bogus for three separate reasons:
1) The module is named amd64_edac_mod.ko
2) I have CONFIG_EDAC_AMD64=y, so don't need the module
3) It prints the error before doing anything that could theoretically
   detect the presence of such a module in the kernel, so loading
   the module wouldn't helo.

For comparison, specifying the CPU results in normal operation:
# strace -efile,read,ioctl,exit_group mcelog --cpu k8
execve("/usr/sbin/mcelog", ["mcelog", "--cpu", "k8"], [/* 15 vars */]) = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/i386-linux-gnu/i686/cmov/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300\213^B4\0\0\0"..., 
512) = 512
open("/etc/mcelog/mcelog.conf", O_RDONLY) = 3
read(3, "#\n# Example config file for mcel"..., 4096) = 4096
read(3, "the hardware does not report DIM"..., 4096) = 1966
read(3, "", 4096)                       = 0
open("/dev/mem", O_RDONLY)              = 3
open("/sys/firmware/efi/systab", O_RDONLY) = -1 ENOENT (No such file or 
directory)
open("/proc/efi/systab", O_RDONLY)      = -1 ENOENT (No such file or directory)
access("/etc/mcelog", R_OK|X_OK)        = 0
access("/etc/mcelog/cache-error-trigger", R_OK|X_OK) = 0
open("/dev/mcelog", O_RDONLY)           = 3
ioctl(3, MCE_GET_RECORD_LEN or MTRRIOC_SET_ENTRY, 0xfff90ca8) = 0
ioctl(3, MCE_GET_LOG_LEN or MTRRIOC_DEL_ENTRY, 0xfff90ca4) = 0
read(3, "", 2816)                       = 0
exit_group(0)                           = ?

FWIW, here's 1/4 of my /proc/cpuinfo:

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 16
model           : 2
model name      : AMD Phenom(tm) 9850 Quad-Core Processor
stepping        : 3
microcode       : 0x1000083
cpu MHz         : 2500.164
cache size      : 512 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 4
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 5
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni 
monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs hw_pstate npt lbrv svm_lock
bogomips        : 5002.67
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

--- End Message ---
--- Begin Message ---
On Tue, Feb 18, 2014 at 10:24:22PM -0500, [email protected] 
wrote:
> mcelog: AMD Processor family 16: Please load edac_mce_amd module.
> : Success
> CPU is unsupported
> exit_group(1)                           = ?
> 
> The error message appears to be bogus for three separate reasons:
> 1) The module is named amd64_edac_mod.ko
> 2) I have CONFIG_EDAC_AMD64=y, so don't need the module
> 3) It prints the error before doing anything that could theoretically
>    detect the presence of such a module in the kernel, so loading
>    the module wouldn't helo.
Please direct these suggestions to the upstream at
http://www.mcelog.org/contact.html

-- 
WBR, wRAR

--- End Message ---

Reply via email to