Request for explanation of error message
Bret Busby
bret.busby at gmail.com
Mon Jul 29 19:03:36 UTC 2019
On 30/07/2019, Mike Marchywka <marchywka at hotmail.com> wrote:
> On Tue, Jul 30, 2019 at 12:33:14AM +0800, Bret Busby wrote:
>> On 29/07/2019, Oliver Grawert <ogra at ubuntu.com> wrote:
>> > hi,
>> > Am Montag, den 29.07.2019, 19:48 +0800 schrieb Bret Busby:
>> >>
>> >> >
>> >> The RAM was changed on 15 July, from a Kingston 8GB DDR 4 2400MHz
>> >> card, to
>> >> "
>> >> Corsair 32GB Kit (2x16GB) DDR4 Vengeance LPX
>> >> Ryzen Black C16 2400MHz (CMK32GX4M2Z2400C16)
>> >> "
>> >>
>> >> I am including that, here, on the off-chance that that may have
>> >> something to do with this.
>> >
>> > easy to test if you still have the old RAM around ... change it back
>> > and see if the errors vanish ;)
>> >
>> > seemingly this ram is "optimized for AMZ Ryzen CPUs" while it "can also
>> > run on Intel X99, 100 und 200 series mainboards"
>> >
>> > your system is an intel i3 (sadly the HW description doesnt tell what
>> > mainboard you have (sudo dmidecode should print that somewhere in its
>> > output though), but probably not an X99, 100 or 200 series one) ...
>> >
>>
>> "
>> Handle 0x0002, DMI type 2, 15 bytes
>> Base Board Information
>> Manufacturer: MEDION
>> Product Name: Z370H4-EM
>> Version: 1.0
>> Serial Number: ME5100G74501135
>> Asset Tag: Default string
>> Features:
>> Board is a hosting board
>> Board is replaceable
>> Location In Chassis: Default string
>> Chassis Handle: 0x0003
>> Type: Motherboard
>> Contained Object Handles: 0
>> "
>>
>> ?
>>
>> Sorry - I thought the information that I had posted, included the
>> motherboard model.
>>
>> From the above, and,, from
>> https://forums.whirlpool.net.au/archive/2702808
>>
>> "
>> It is an ECS oem mobo. Z370H4-EM
>> "
>>
>> > the date when you changed the ram matches the point in time when your
>> > logs started growing, so try if moving back to the old one helps .. if
>> > it does i'd assume your new ram is simply incompatible with that system
>> > ...
>> >
>> > ciao
>> > oli
>>
>>
>> I can't do anything much physically with the computer, and, I am not
>> confident to open it and do anything inside it - I am right-handed,
>> and, about half of my right hand has been numb for about two months,
>> now, and, I do not have much strength in my right hand.
>>
>> The new RAM was installed by my local computer shop for me, and, the
>> man booted it into BIOS, to determine that the BIOS could see the 32GB
>> of RAM, and, as other UbuntuMATE utilities can see the RAM, including
>> the System Monitor, I had taken for granted, that the 32GB RAM is
>> compatible.
>>
>> From the above command;
>>
>> "
>> Handle 0x003D, DMI type 16, 23 bytes
>> Physical Memory Array
>> Location: System Board Or Motherboard
>> Use: System Memory
>> Error Correction Type: None
>> Maximum Capacity: 32 GB
>> Error Information Handle: Not Provided
>> Number Of Devices: 2
>>
>> Handle 0x003E, DMI type 17, 40 bytes
>> Memory Device
>> Array Handle: 0x003D
>> Error Information Handle: Not Provided
>> Total Width: 64 bits
>> Data Width: 64 bits
>> Size: 16384 MB
>> Form Factor: DIMM
>> Set: None
>> Locator: ChannelA-DIMM0
>> Bank Locator: BANK 0
>> Type: DDR4
>> Type Detail: Synchronous Unbuffered (Unregistered)
>> Speed: 2400 MT/s
>> Manufacturer: 029E
>> Serial Number: 00000000
>> Asset Tag: 9876543210
>> Part Number: CMK32GX4M2Z2400C16
>> Rank: 2
>> Configured Clock Speed: 2400 MT/s
>> Minimum Voltage: 1.2 V
>> Maximum Voltage: 1.2 V
>> Configured Voltage: 1.2 V
>>
>> Handle 0x003F, DMI type 17, 40 bytes
>> Memory Device
>> Array Handle: 0x003D
>> Error Information Handle: Not Provided
>> Total Width: 64 bits
>> Data Width: 64 bits
>> Size: 16384 MB
>> Form Factor: DIMM
>> Set: None
>> Locator: ChannelB-DIMM0
>> Bank Locator: BANK 2
>> Type: DDR4
>> Type Detail: Synchronous Unbuffered (Unregistered)
>> Speed: 2400 MT/s
>> Manufacturer: 029E
>> Serial Number: 00000000
>> Asset Tag: 9876543210
>> Part Number: CMK32GX4M2Z2400C16
>> Rank: 2
>> Configured Clock Speed: 2400 MT/s
>> Minimum Voltage: 1.2 V
>> "
>>
>> I assume from that output, that the 32GB RAM is compatible?
>
> Does your bios have a memory test? You could just check that.
>
I assume that the shop performed a BIOS memory test, when the new RAM
was fitted - he booted the computer, went into BIOS, and, the screen
was blue, with white text, and, displayed only inmformation about the
memory, including the (about) 32GB being recognised. Outputs show
31xxxMB for the memory.
"
bret at bret-MD34045-2521:~$ free -h
total used free shared buff/cache available
Mem: 31G 5.0G 21G 1.1G 4.5G 24G
Swap: 30G 0B 30G
bret at bret-MD34045-2521:~$
"
After installing memtester, and trying to run
sudo memtester 32G 2
the end of the output is
"
got 16MB (16781312 bytes), trying mlock ...too many pages, reducing...
got 16MB (16777216 bytes), trying mlock ...locked.
Loop 1/2:
Stuck Address : ok
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok
8-bit Writes : ok
16-bit Writes : ok
Loop 2/2:
Stuck Address : ok
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok
8-bit Writes : ok
16-bit Writes : ok
Done.
"
after it working its way down to the 16MB, with thememory quantity
decreasing each line, until it got down to the 16MB.
memtester appears to cope with no more than 16MB of RAM.
> How often do you get the PCI errors? Do you check dmesg often?
>
The PCI errors appear to be ongoing and incessant.
If I go to a console (<CTRL><ALT><F1>), each time I type a string ( to
log in, and, then, each "word", or, string of characters without a
space), it keeps outputting the PCI error.
dmesg , unfortunately, does not show timestamps
I think a significant thing, is to determine what exactly is the "PCI
bridge" that is at the address,
"00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root
Port #9 (rev f0)
"
to which the error relates;
"
Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053210] pcieport
0000:00:1d.0: AER: Corrected error received: id=00e8
Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053216] pcieport
0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
id=00e8(Receiver ID)
Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053219] pcieport
0000:00:1d.0: device [8086:a298] error status/mask=00000001/00002000
Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053221] pcieport
0000:00:1d.0: [ 0] Receiver Error (First)
"
and, also, the Xorg error previously cited;
"
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
_XSERVTransSocketUNIXAccept: accept() failed
"
> I'd still try to boot into single user mode and try to trigger
> the PCI errors just by starting a few things manually
> like lightdm with debug flag that seems to be the immediate problem.
>
>
--
Bret Busby
Armadale
West Australia
..............
"So once you do know what the question actually is,
you'll know what the answer means."
- Deep Thought,
Chapter 28 of Book 1 of
"The Hitchhiker's Guide to the Galaxy:
A Trilogy In Four Parts",
written by Douglas Adams,
published by Pan Books, 1992
....................................................
More information about the ubuntu-users
mailing list