Author
Topic: LMCE keeps hard locking.... (Read 3565 times)

Occasionally (sometimes once per day, other times it can go for several days) my core locks up completely, keyboard LEDs flashing. Have to reset the box completely...

I have noticed in dmesg some errors which are obviously related. They tend to happen some time before the lock up and obviously the kernel eventually falls over. But I have noticed the last few all seem to be complaining about Photo Screen Saver particularly.. Can anybody shed any light on what might be causing this?

fsck just happens to have run yesterday, no issues. Haven't run any memory check yet, but I think it is indicative that it only seems to happen for the one process.. PSS... I guess that could either be a bug in the code generally, or perhaps a particular photo is triggering an arcane bug? esp. given the rescaling function that was recently added...

Will have a think about using vesa - but I'm concerned it will be unusably slow (how slow is it, hari?)

Its not compatibility, the same hardware has been running very successfully for over a year. I have checked heat before, and it runs well below the critical temperatures, but I will take another look to make sure something hasn't changed - but again, I point out that it is the same process failing each time. Although PSS runs most of the time, and that statistically increases the likelihood of a "random" hardware issue effecting that process repeatedly, there are dozens of other processes that run all the time as well... wish I could find a clear explanation of that the error message means generally. If its just memory management getting pages mixed up/page tables corrupted then it is extremely unlikely to be hardware, but if it is the hardware memory mapping CAM or such like, then very likely to be hardware... hmmm

It could even be "bit-rot" on the HD (granted, not very likely) maybe try reinstalling the pluto-photo-screen-saver package and see if that makes any difference: sudo apt-get --reinstall pluto-photo-screen-saver (from memory).

Will have a think about using vesa - but I'm concerned it will be unusably slow (how slow is it, hari?)

Its not compatibility, the same hardware has been running very successfully for over a year. I have checked heat before, and it runs well below the critical temperatures, but I will take another look to make sure something hasn't changed - but again, I point out that it is the same process failing each time. Although PSS runs most of the time, and that statistically increases the likelihood of a "random" hardware issue effecting that process repeatedly, there are dozens of other processes that run all the time as well... wish I could find a clear explanation of that the error message means generally. If its just memory management getting pages mixed up/page tables corrupted then it is extremely unlikely to be hardware, but if it is the hardware memory mapping CAM or such like, then very likely to be hardware... hmmm

I think the suggestion of using vesa mode was purely to allow a test of your hardware... not intended for permanent use etc.

All - before I can use apt-get install for either the smartmontools or to reinstall PSS I have to resolve a dependency issue.

I recently got a SqueezeBox Boom, and as a result of it being incompatible with the existing streamer, I had to go through a process of upgrading to SqueezeCentre. This has left my dependencies a bit screwed up. So now if I try to issue any apt-get install commands it comes back with:

The following packages have unmet dependencies: pluto-slim-server-streamer: PreDepends: slimserver but it is not going to be installedE: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).linuxmce@dcerouter:/etc/pluto$ man apt-get

The dependencies indicate that is it still using slimserver when in fact it is really using squeezecenter (Zaerc did squeezecenter make it into the alpha1?)

I would like just to be able to override this check/failure for now and go ahead with the install/reinstall I want to do - how can I do this? I really don't want to 1) mess around with the dependencies or 2) accidentally install/uninstall a component at this stage because I can't remember how I got squeezecenter hooked into the system in the first place! So just getting it to ignore this problem temporarily would be great!