LinuxCNC Support Forum :: Topic: can't open after fixing smi issues (6/7)

component fault "designed specifically to break LinuxCNC";
license "GPL";
author "Andy Pugh";
option extra_setup yes;
pin out unsigned dummy = 666;
function _;

;;
FUNCTION(_){
//It will never even get this far
}

EXTRA_SETUP(){
*(int*)0 = 0;
}

then:
halrun
loadrt fault.comp
exit

Then try to recover the system so that halrun can be invoked again without a reboot.
I hope you can find a way, it will save me hours.
(currently I am struggling with a slightly more subtle issue of passing fixed-length strings between modules, which may or may not be initialised but the effect is the same)

MESSAGE FOR THE OP:
Don't worry about this, it is not relevant to the typical user experience.

The administrator has disabled public write access.

Re:can't open after fixing smi issues 25 Mag 2012 18:38 #20404

pfred1
OFFLINE
Senior Boarder
Posts: 57
Karma: 6

It is your experiment Andy so you try it,

sudo init 1

login as root

init 2

Because quite frankly I don't know the first thing you're on about with any of this. I still give fair odds that'd work. Technically it isn't rebooting either. Although I'll admit it looks an awful lot like rebooting. There may be less invasive fixes though. But I feel like I'm getting a bit of the mushroom treatment now. You know kept in the dark, and fed ....

So that is the best I can come up with for now. Well, maybe not, but it's the best I'm going to come up with considering what I have to work with.

The administrator has disabled public write access.

Re:can't open after fixing smi issues 25 Mag 2012 18:49 #20406

andypugh
OFFLINE
Moderator
Posts: 4245
Thank you received: 152
Karma: 130

pfred1 wrote:

It is your experiment Andy so you try it,

I did, I had to reboot. In fact dmesg said:
[ 4057.142301] RTAPI: Task 1[eed35800]: Fault with vec=14, signo=11 ip=fb598d71.
[ 4057.142305] RTAPI: This fault may not be recoverable without rebooting.

sudo init 1
login as root
init 2

I can try it, I am open to suggestions.

Because quite frankly I don't know the first thing you're on about with any of this. I still give fair odds that'd work. Technically it isn't rebooting either. Although I'll admit it looks an awful lot like rebooting. There may be less invasive fixes though. But I feel like I'm getting a bit of the mushroom treatment now. You know kept in the dark, and fed

You have me puzzled now. I thought you were saying that there were simpler ways to untangle a mess of kernel modules other than rebooting. I was rather hoping you were right.
I just provided a minimal realtime module that puts the system in the state I was describing.

I really do know next-to-nothing about Linux. It might seem odd that someone like me would mess about with Kernel modules, but it's true. I like my hobbies to be beyond my capabilities.

Last Edit: 25 Mag 2012 18:49 by andypugh.

The administrator has disabled public write access.

Re:can't open after fixing smi issues 25 Mag 2012 19:32 #20407

Banana Jack OFFLINE Fresh Boarder Posts: 10 Karma: 0	MESSAGE FOR THE OP: Don't worry about this, it is not relevant to the typical user experience. yeah i realized that... real fast. on a side note... YOU GUYS ARE AWESOME. what a beautiful, beautiful sight...it's been much too long...
	The administrator has disabled public write access.

Re:can't open after fixing smi issues 25 Mag 2012 19:34 #20408

andypugh OFFLINE Moderator Posts: 4245 Thank you received: 152 Karma: 130	Banana Jack wrote: what a beautiful, beautiful sight...it's been much too long... It's not that beautiful, you still have the "Realtime Delay" message
	The administrator has disabled public write access.

Re:can't open after fixing smi issues 25 Mag 2012 20:35 #20409

pfred1
OFFLINE
Senior Boarder
Posts: 57
Karma: 6

Things are rarely fun if they're not challenging.

[ 4057.142305] RTAPI: This fault may not be recoverable without rebooting.

In any event reading your dmesg error I think you might have better luck in June, and that isn't so far off now. May is a silly month!

Next thing you know you'll be singing jigs!

Don't ever learn anything about Linux, because as soon as you do some clown will just end up changing it all on you anyways. I just learned termcap no longer exists! I can't make heads or tails out of terminfo either. How am I supposed to pick colors for my terminals now?

I did learn about this bizarre little program called grc though. It doesn't do much for me with dmesg, but it sure can make syslog pretty.