Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
08-03-2019, 10:30 PM
|
#1
|
Member
Registered: Jun 2004
Distribution: puppy linux, suse 10.0, opensuse 11.3, 12.1, mythdora, opensuse 13.1, opensuse tumbleweed
Posts: 606
Rep:
|
mc1 error: copy back parity/victim error
Hello,
I have been getting this error several times today. Not sure, but could this be bad ram? Never had this problem before. Depending on what I am doing, the box can freeze or I get the local system message service informing me:
kernel:[300.704016] [hardware error]: mc1 error: copy back parity/victim error.
kernel:[300.704026] [hardware error]: error status: corrected error, not action required.
amd 3200 64bit
4 gig ram
asus a8v-e se motherboard
I built this box and it ran without errors for years.
|
|
|
08-04-2019, 09:29 PM
|
#2
|
Member
Registered: Jun 2004
Distribution: puppy linux, suse 10.0, opensuse 11.3, 12.1, mythdora, opensuse 13.1, opensuse tumbleweed
Posts: 606
Original Poster
Rep:
|
I ordered a cpu. It is an amd athlon 3000+. The error code appears to refer to the L1 cache which is on the cpu. The error code can also be a thermal problem associated with dust. I blew out all the dust, but still received the hardware error code.
|
|
|
08-11-2019, 06:47 PM
|
#3
|
Member
Registered: Jun 2004
Distribution: puppy linux, suse 10.0, opensuse 11.3, 12.1, mythdora, opensuse 13.1, opensuse tumbleweed
Posts: 606
Original Poster
Rep:
|
I installed a new identical cpu. The hardware error is gone, the bios can be accessed and changed, however, I have a new error: kernel panic - not syncing: fatal exception in interrupt. The error happens after the splash screen of opensuse on the hard disk or any live disk that I try, always after the splash screen. The hardware is the same. The motherboard detected the cpu change. I have gone through every menu entry in the bios and can not figure it out. I also removed the cmos battery with the box unplugged to clear the memory. On start up, cmos reported: cmos check sum error. Defaults loaded. The box still stops after the splash screen. The box can run memtest with no problems. Also tried removing and reinstalling the ram modules.
|
|
|
08-13-2019, 08:55 PM
|
#4
|
Member
Registered: Jun 2004
Distribution: puppy linux, suse 10.0, opensuse 11.3, 12.1, mythdora, opensuse 13.1, opensuse tumbleweed
Posts: 606
Original Poster
Rep:
|
The problem is now a kernel panic. The following has been changed:
1. Replaced cpu - that fixed the l1 cache error
2. Tried booting other types of medium - live dvd - get same kernel panic after splash screen
3. Replaced all the ram with ram from a known good pc - kernel panic
error is: kernel panic - not syncing: fatal exception in interrupt
I can page through the bios screens no problem. Box boots with ok beep from motherboard. I am running out of possible causes. Only have motherboard and video card to troubleshoot, however, since I have video output and the motherboard beeps ok, what are the other possibilities? Maybe remove cmos battery overnight to make sure setting are flushed from memory and boot up?
|
|
|
08-13-2019, 08:56 PM
|
#5
|
Member
Registered: Jun 2004
Distribution: puppy linux, suse 10.0, opensuse 11.3, 12.1, mythdora, opensuse 13.1, opensuse tumbleweed
Posts: 606
Original Poster
Rep:
|
I will post a photo I took of the last kernel panic screen.
|
|
|
08-14-2019, 05:52 PM
|
#6
|
Member
Registered: Jun 2004
Distribution: puppy linux, suse 10.0, opensuse 11.3, 12.1, mythdora, opensuse 13.1, opensuse tumbleweed
Posts: 606
Original Poster
Rep:
|
kernel panic
Attached are two screen shots:
|
|
|
08-18-2019, 04:23 PM
|
#7
|
Member
Registered: Jun 2004
Distribution: puppy linux, suse 10.0, opensuse 11.3, 12.1, mythdora, opensuse 13.1, opensuse tumbleweed
Posts: 606
Original Poster
Rep:
|
The pc runs no problem with freeDos, but I have a kernel panic with every other os. Other error reports are:
unable to handle kernel paging request
vfs: unable to mount root fs on unknown-block (0,0)
I believe the second error points to the bios. With the updated bios file, I plan to flash the cmos chip. If that fails, then I feel that the board is bad.
|
|
|
08-21-2019, 07:35 PM
|
#8
|
Member
Registered: Jun 2004
Distribution: puppy linux, suse 10.0, opensuse 11.3, 12.1, mythdora, opensuse 13.1, opensuse tumbleweed
Posts: 606
Original Poster
Rep:
|
The bios was successfully flashed, however, it still reports a kernel panic. At this point I feel that the motherboard has failed, but I am not 100% certain because it can boot dos and run dos based utilities. Can anyone suggest a dos based diagnostic program to test the motherboard?
|
|
|
09-21-2019, 08:00 PM
|
#9
|
Member
Registered: Jun 2004
Distribution: puppy linux, suse 10.0, opensuse 11.3, 12.1, mythdora, opensuse 13.1, opensuse tumbleweed
Posts: 606
Original Poster
Rep:
|
A new motherboard solved the problem. After dissecting the error codes, it appeared that the irq handler would crash as the os was loading and when irq 21 was assigned, it crashed causing a kernel panic. That would explain why the board ran dos ok. The board never had to assign many interrupts.
|
|
|
All times are GMT -5. The time now is 05:53 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|