New install of "SimplyMEPIS-USB_8.5.03-rel1_64" is unstable

Those new to MEPIS or not very experienced can post their questions here.
Message
Author
k357k9
Forum Novice
Forum  Novice
Posts: 25
Joined: Sat Feb 12, 2011 9:16 am

Re: New install of "SimplyMEPIS-USB_8.5.03-rel1_64" is unsta

#11 Postby k357k9 » Sat Feb 11, 2012 6:40 pm

@m-pav
Is there some way to eliminate the old ISOs, or at least mark them old, and point people to the new ones?

User avatar
lucky9
Forum Veteran
Forum Veteran
Posts: 12274
Age: 70
Joined: Wed Jul 12, 2006 5:54 am

Re: New install of "SimplyMEPIS-USB_8.5.03-rel1_64" is unsta

#12 Postby lucky9 » Sat Feb 11, 2012 6:43 pm

It more a matter of the mirrors being behind and people not reading the mepis.org site. Or even reading stuff here.
Yes, even I am dishonest. Not in many ways, but in some. Forty-one, I think it is.
--Mark Twain

johnnyhop
Forum Novice
Forum  Novice
Posts: 22
Age: 64
Joined: Sun Jan 16, 2011 8:17 am

Re: New install of "SimplyMEPIS-USB_8.5.03-rel1_64" is unsta

#13 Postby johnnyhop » Sun Feb 12, 2012 1:08 am

Thank you for the grub boot line clarifications I'll experiment more with it tomorrow. Roadblock freezes at login 'enter.' Also will try another distro on the exixting partitions to prove/disprove HD issue.

User avatar
m_pav
Forum Guide
Forum Guide
Posts: 2507
Age: 49
Joined: Sun Aug 06, 2006 3:02 pm

Re: New install of "SimplyMEPIS-USB_8.5.03-rel1_64" is unsta

#14 Postby m_pav » Sun Feb 12, 2012 5:53 am

Oops, thanks for that.

Mike P
Mike P

Regd Linux User #472293
(Mine)Lenovo T550, i7-5600U, 16GB, 128GB SSD + 1.0TB HDD, MX15 64-bit
(Wifes) Asus M4A88TD-M, AMD Phenom II x4 955 CPU, nVidia GF610, 6Gb, 500GB+320GB, MX14 + KDE
(Kids) Intel NUC, J1900, 4GB, 64GB SSD, MX14 + KDE

johnnyhop
Forum Novice
Forum  Novice
Posts: 22
Age: 64
Joined: Sun Jan 16, 2011 8:17 am

Re: New install of "SimplyMEPIS-USB_8.5.03-rel1_64" is unsta

#15 Postby johnnyhop » Mon Feb 13, 2012 1:41 am

Installed SalineOS-1.6 in the partitions I'd tried installing Mepis 11-64. Saline installed glitch free. I'll look more carefully for the latest version of Mepis 11 .iso to download and give it another attempt.

johnnyhop
Forum Novice
Forum  Novice
Posts: 22
Age: 64
Joined: Sun Jan 16, 2011 8:17 am

Re: New install of "SimplyMEPIS-USB_8.5.03-rel1_64" is unsta

#16 Postby johnnyhop » Wed Feb 15, 2012 11:21 pm

Finally running Mepis. There must be something awry with hard drive sdd. Sucessfully installed and booted to a small 7.8gB (considering home is included on root) partition on sda. If Mepis can run without the annoying freezing up all too regularily, as is the case with Kubuntu and Fedora, then it'll move Mepis to more suitable partitions for regular use. This sdd4 partition is for testing. One very annoying thing is happening, this error message:

Code: Select all

Message from syslogd@mepis1 at Feb 15 19:49:00 ...
 kernel:[  760.688120] Transaction: snoop, Type: generic, Cache Level: L2

Message from syslogd@mepis1 at Feb 15 19:49:00 ...
 kernel:[  910.192039] MC0_STATUS: Corrected error, other errors lost: yes, CPU context corrupt: no, CECC Error

Message from syslogd@mepis1 at Feb 15 19:49:00 ...
 kernel:[  910.192055] Data Cache Error during L1 linefill from L2.

Message from syslogd@mepis1 at Feb 15 19:49:00 ...
 kernel:[  910.192063] Transaction: data read, Type: data, Cache Level: L2

Message from syslogd@mepis1 at Feb 15 19:49:00 ...
 kernel:[  910.192069] MC1_STATUS: Corrected error, other errors lost: yes, CPU context corrupt: no

Message from syslogd@mepis1 at Feb 15 19:49:00 ...
 kernel:[  910.192077] Instruction Cache Error: Parity error during data load.

Message from syslogd@mepis1 at Feb 15 19:49:00 ...
 kernel:[  910.192083] Transaction: inst fetch, Type: instruction, Cache Level: L1

Message from syslogd@mepis1 at Feb 15 19:49:00 ...
 kernel:[  910.192088] MC2_STATUS: Corrected error, other errors lost: yes, CPU context corrupt: no, CECC Error

Message from syslogd@mepis1 at Feb 15 19:49:00 ...
 kernel:[  910.192097] Bus Unit Error: evict error during data copyback.

Message from syslogd@mepis1 at Feb 15 19:53:59 ...
 kernel:[  910.192103] Transaction: evict, Type: generic, Cache Level: L2

Message from syslogd@mepis1 at Feb 15 19:53:59 ...
 kernel:[ 1209.200044] MC0_STATUS: Corrected error, other errors lost: yes, CPU context corrupt: no, CECC Error

Message from syslogd@mepis1 at Feb 15 19:53:59 ...
 kernel:[ 1209.200061] Data Cache Error during L1 linefill from L2.

Message from syslogd@mepis1 at Feb 15 19:53:59 ...
 kernel:[ 1209.200069] Transaction: data read, Type: data, Cache Level: L2

Message from syslogd@mepis1 at Feb 15 19:53:59 ...
 kernel:[ 1209.200075] MC1_STATUS: Corrected error, other errors lost: yes, CPU context corrupt: no

Message from syslogd@mepis1 at Feb 15 19:53:59 ...
 kernel:[ 1209.200083] Instruction Cache Error: Parity error during data load.

Message from syslogd@mepis1 at Feb 15 19:53:59 ...
 kernel:[ 1209.200090] Transaction: inst fetch, Type: instruction, Cache Level: L1

Message from syslogd@mepis1 at Feb 15 19:53:59 ...
 kernel:[ 1209.200095] MC2_STATUS: Corrected error, other errors lost: yes, CPU context corrupt: no, CECC Error

Message from syslogd@mepis1 at Feb 15 19:53:59 ...
 kernel:[ 1209.200104] Bus Unit Error: evict error during data copyback.

Message from syslogd@mepis1 at Feb 15 19:59:00 ...
 kernel:[ 1209.200110] Transaction: evict, Type: generic, Cache Level: L2

Message from syslogd@mepis1 at Feb 15 19:59:00 ...
 kernel:[ 1509.816057] MC0_STATUS: Corrected error, other errors lost: yes, CPU context corrupt: no, CECC Error

Message from syslogd@mepis1 at Feb 15 19:59:00 ...
 kernel:[ 1509.816073] Data Cache Error during L1 linefill from L2.

Message from syslogd@mepis1 at Feb 15 19:59:00 ...
 kernel:[ 1509.816080] Transaction: data read, Type: data, Cache Level: L2

Message from syslogd@mepis1 at Feb 15 19:59:00 ...
 kernel:[ 1509.816086] MC1_STATUS: Corrected error, other errors lost: yes, CPU context corrupt: no

Message from syslogd@mepis1 at Feb 15 19:59:00 ...
 kernel:[ 1509.816094] Instruction Cache Error: Parity error during data load.

Message from syslogd@mepis1 at Feb 15 19:59:00 ...
 kernel:[ 1509.816101] Transaction: inst fetch, Type: instruction, Cache Level: L1

Message from syslogd@mepis1 at Feb 15 19:59:00 ...
 kernel:[ 1509.816105] MC2_STATUS: Corrected error, other errors lost: no, CPU context corrupt: no, CECC Error

Message from syslogd@mepis1 at Feb 15 19:59:00 ...
 kernel:[ 1509.816114] Bus Unit Error: evict error during data copyback.


I'm not sure what it means, there doesn't appear to be an apparent problem with regard to functionality of the system. It pops up every few minutes and I'd like to find out how to turn it off.

User avatar
m_pav
Forum Guide
Forum Guide
Posts: 2507
Age: 49
Joined: Sun Aug 06, 2006 3:02 pm

Re: New install of "SimplyMEPIS-USB_8.5.03-rel1_64" is unsta

#17 Postby m_pav » Thu Feb 16, 2012 2:15 am

Googling portions of the error messages, they tend to point to;
1. RAM Memory errors, indicated by the CE status, with dire warnings that they will degenerate to full blown faults as the chips break down further.
2. Cache memory errors on some other hardware device if it's not the RAM chips.

Quoted from http://kernel.org/doc/Documentation/edac.txt
MEMORY

In the initial release, memory Correctable Errors (CE) and Uncorrectable
Errors (UE) are the primary errors being harvested. These types of errors
are harvested by the 'edac_mc' class of device.

Detecting CE events, then harvesting those events and reporting them,
CAN be a predictor of future UE events. With CE events, the system can
continue to operate, but with less safety. Preventive maintenance and
proactive part replacement of memory DIMMs exhibiting CEs can reduce
the likelihood of the dreaded UE events and system 'panics'.

NON-MEMORY

A new feature for EDAC, the edac_device class of device, was added in
the 2.6.23 version of the kernel.

This new device type allows for non-memory type of ECC hardware detectors
to have their states harvested and presented to userspace via the sysfs
interface.

Some architectures have ECC detectors for L1, L2 and L3 caches, along with DMA
engines, fabric switches, main data path switches, interconnections,
and various other hardware data paths. If the hardware reports it, then
a edac_device device probably can be constructed to harvest and present
that to userspace.


I guess that means any device that has onboard memory in active processes can can be responsible for the messages, and I would add, they might also be triggered by memory incompatibility or firmware bugs too.

You can disable the messages if you really want to, see the following thread
viewtopic.php?f=38&t=32593

Mike P
Mike P

Regd Linux User #472293
(Mine)Lenovo T550, i7-5600U, 16GB, 128GB SSD + 1.0TB HDD, MX15 64-bit
(Wifes) Asus M4A88TD-M, AMD Phenom II x4 955 CPU, nVidia GF610, 6Gb, 500GB+320GB, MX14 + KDE
(Kids) Intel NUC, J1900, 4GB, 64GB SSD, MX14 + KDE


Return to “Newbies”

Who is online

Users browsing this forum: cogprofessor and 1 guest