Hi all,
are there any problems known with nested interrupts at a high interrupt
load? (QNX 6.2.0A, x86)
There are two interrupt sources which are producing ~5000 interrupts per
second. These two IRQs are handled with two seperate resource managers.
One of them locks up … no further interrupts and the main loop doesn’t
receive messages even if resmg_block() is receive blocked =:-/
Regards
Armin
Hi Armin,
Not that we will find anything wrong with your code, but it may help if you
could you post the snippet of code that handles interrupts in your resmgrs.
Kevin
“Armin Steinhoff” <a-steinhoff@web.de> wrote in message
news:bhtvhh$c6d$1@inn.qnx.com…
Hi all,
are there any problems known with nested interrupts at a high interrupt
load? (QNX 6.2.0A, x86)There are two interrupt sources which are producing ~5000 interrupts per
second. These two IRQs are handled with two seperate resource managers.
One of them locks up … no further interrupts and the main loop doesn’t
receive messages even if resmg_block() is receive blocked =:-/Regards
Armin
\
Armin Steinhoff <a-steinhoff@web.de> wrote:
AS > Hi Kevin,
AS > Kevin Stallard wrote:
Hi Armin,
Not that we will find anything wrong with your code,
AS > ??
but it may help if you
could you post the snippet of code that handles interrupts in your resmgrs.
AS > Would be waste of time … after working 12 years with QNX I know how to
AS > write and test interrupt handlers.
AS > BTW … each resmgr works properly with an interrupt load of 7000-10000
AS > interrupts /second.
AS > The problem appears if two of these resmgrs are actively handling
AS > different ISA interrupts (x86) at a high interrupt load.
ISA!
Can the ISA bus handle that?
AS > Both resmgs are working complete independent.
AS > Armin
Armin Steinhoff wrote:
but it may help if you
could you post the snippet of code that handles interrupts in your
resmgrs.
Would be waste of time … after working 12 years with QNX I know how to
I’m usually thrilled if someone volunteers to take a look at my code, and I’ve
been writing interrupt handlers for QNX for over 15 years. The only reason I
might not jump at the opportunity is if the code is too complex to be handled in
this forum (or would simply be too great a burden on the reviewer); but Kevin
asked for interrupt handlers, they couldn’t be complicated… could they ?
Kevin is simply asking for some code to give context in order to aid in
understanding what the issue might be.
As for the “Both resmgrs are working completely independently” comment, this
obviously is not true, since your complaint is that they are interacting in an
undesirable way. The goal should be to discover the mechanism by which they are
not “independent”. It may be O/S, hardware, or driver. Personally, I am
curious. I certainly want to be able to rely on QNX to provide sufficiently low
latencies and/or accurate scheduling, so that the interrupt load you are
discussing can be easily handled.
Hi Kevin,
Kevin Stallard wrote:
Hi Armin,
Not that we will find anything wrong with your code,
??
but it may help if you
could you post the snippet of code that handles interrupts in your resmgrs.
Would be waste of time … after working 12 years with QNX I know how to
write and test interrupt handlers.
BTW … each resmgr works properly with an interrupt load of 7000-10000
interrupts /second.
The problem appears if two of these resmgrs are actively handling
different ISA interrupts (x86) at a high interrupt load.
Both resmgs are working complete independent.
Armin
Kevin
“Armin Steinhoff” <> a-steinhoff@web.de> > wrote in message
news:bhtvhh$c6d$> 1@inn.qnx.com> …Hi all,
are there any problems known with nested interrupts at a high interrupt
load? (QNX 6.2.0A, x86)There are two interrupt sources which are producing ~5000 interrupts per
second. These two IRQs are handled with two seperate resource managers.
One of them locks up … no further interrupts and the main loop doesn’t
receive messages even if resmg_block() is receive blocked =:-/Regards
Armin
\
“Rennie Allen” <rgallen@attbi.com> wrote in message
news:bi1fco$72t$1@inn.qnx.com…
Armin Steinhoff wrote:
but it may help if you
could you post the snippet of code that handles interrupts in your
resmgrs.
Would be waste of time … after working 12 years with QNX I know how toI’m usually thrilled if someone volunteers to take a look at my code, and
I’ve
been writing interrupt handlers for QNX for over 15 years. The only
reason I
might not jump at the opportunity is if the code is too complex to be
handled in
this forum (or would simply be too great a burden on the reviewer); but
Kevin
asked for interrupt handlers, they couldn’t be complicated… could they ?Kevin is simply asking for some code to give context in order to aid in
understanding what the issue might be.As for the “Both resmgrs are working completely independently” comment,
this
obviously is not true, since your complaint is that they are interacting
in an
undesirable way. The goal should be to discover the mechanism by which
they are
not “independent”. It may be O/S, hardware, or driver. Personally, I am
curious. I certainly want to be able to rely on QNX to provide
sufficiently low
latencies and/or accurate scheduling, so that the interrupt load you are
discussing can be easily handled.
It would also help to put things into context if we knew what is clock
frequency, what are interrupt numbers assigned to those ISA devices, what
else is on the ISA/PCI buses, are those interrupts edge or level triggered,
etc.
Armin Steinhoff wrote:
BTW, is it an insult to say ‘I don’t need help in writing interrupt
handlers’??
It is if you brush off a reasonable request for more information, with the
implication that the person asking is inexperienced and or naive in comparison
with you.
btw: I don’t think Igors’ interpretation is strange, it is my interpretation
also; and I bet it is most peoples interpretation.
I asked simply:
“are there any problems known with nested interrupts
at a high interrupt load? (QNX 6.2.0A, x86)”
OK, I’ll buy that this was your original intent. How about next time someone
asks a question that implies that they want to help you, and you don’t really
want any help; instead of brushing them off rudely, you simply explain that you
just wanted to know if there were any known problems with the O/S ?
What would be really cool is if you added something like “thanks anyway”.
“Armin Steinhoff” <a-steinhoff@web.de> wrote in message
news:bi22d0$nam$1@inn.qnx.com…
Igor Kovalenko wrote:
“Rennie Allen” <> rgallen@attbi.com> > wrote in message
news:bi1fco$72t$> 1@inn.qnx.com> …[ clip … ]
It would also help to put things into context if we knew what is clock
frequency, what are interrupt numbers assigned to those ISA devices,
what
else is on the ISA/PCI buses, are those interrupts edge or level
triggered,
etc.It would help if there are some problems with the resmgr … but that’s
not the case.I also didn’t ask for help for this issue …
Right. Here’s a summary of what you’re saying:
“I have a program that I will NOT show you, that does not work because the
OS is broken. I just KNOW that OS is broken and I will NOT show any proof.
And I do not need help, so piss off with all your suggestions.”
(c) Armin, All rights reserved.
You’re a real prima donna here.
Armin Steinhoff <a-steinhoff@web.de> wrote:
Rennie Allen wrote:
Armin Steinhoff wrote:but it may help if you
could you post the snippet of code that handles interrupts in your
resmgrs.
Would be waste of time … after working 12 years with QNX I know how to
I’m usually thrilled if someone volunteers to take a look at my code,
and I’ve been writing interrupt handlers for QNX for over 15 years. The
only reason I might not jump at the opportunity is if the code is too
complex to be handled in this forum (or would simply be too great a
burden on the reviewer); but Kevin asked for interrupt handlers, they
couldn’t be complicated… could they ?Please read my initial message … I didn’t ask for help for writing
interrupt handlers.Kevin is simply asking for some code to give context in order to aid in
understanding what the issue might be.As for the “Both resmgrs are working completely independently”
comment, this obviously is not true, since your complaint is that they
are interacting in an undesirable way.No … they don’t interact. There seems to be a problem with the OS
if it has to handle both independent resmgr concurrently at a high
interrupt load or if both interrupts are raised up at the same time.BTW … there was a similar problem with the PPC version of QNX6.2.0A.
If two interrupts are raised up with a time difference in the range of
nanoseconds … QNX locked complete up.It’s working now with QNX 6.2.1 … and I haven’t changed a single line
of code.
If you’re referring to the issue with the MGT5100, that was a BSP specific
problem (as has already been pointed out in a previous thread) with an
interrupt callout, completely unrelated to OS version, kernel, etc.
The goal should be to discover
the mechanism by which they are not “independent”. It may be O/S,
hardware, or driver. Personally, I am curious. I certainly want to be
able to rely on QNX to provide sufficiently low latencies and/or
accurate scheduling, so that the interrupt load you are discussing can
be easily handled.I have different experiences … see above.
Armin
–
David Green (dgreen@qnx.com)
QNX Software Systems Ltd.
http://www.qnx.com
Igor Kovalenko wrote:
“Armin Steinhoff” <> a-steinhoff@web.de> > wrote in message
news:bi22d0$nam$> 1@inn.qnx.com> …Igor Kovalenko wrote:
[ clip …]
It would help if there are some problems with the resmgr … but that’s
not the case.I also didn’t ask for help for this issue …
Right. Here’s a summary of what you’re saying:
"I have a program that I will NOT show you, that does not work because the
OS is broken. I just KNOW that OS is broken
Sorry … but I didn’t say this!!
and I will NOT show any proof.
How would you SHOW such a PROOF in this NG??
BTW, is it forbidden to ask whether something is a KNOWN PROBLEM?
And I do not need help, so piss off with all your suggestions."
(c) Armin, All rights reserved.
That’s simply your very strange interpretation …
BTW, is it an insult to say ‘I don’t need help in writing interrupt
handlers’??
I asked simply:
“are there any problems known with nested interrupts
at a high interrupt load? (QNX 6.2.0A, x86)”
It’s really amazing for me how difficult it is to understand such a
short and simple question…
You’re a real prima donna here.
No … I don’t compete in this issue with you 
Armin
Dave Green wrote:
Armin Steinhoff <> a-steinhoff@web.de> > wrote:
Rennie Allen wrote:
Armin Steinhoff wrote:[…]
As for the “Both resmgrs are working completely independently”
comment, this obviously is not true, since your complaint is that they
are interacting in an undesirable way.No … they don’t interact. There seems to be a problem with the OS
if it has to handle both independent resmgr concurrently at a high
interrupt load or if both interrupts are raised up at the same time.BTW … there was a similar problem with the PPC version of QNX6.2.0A.
If two interrupts are raised up with a time difference in the range of
nanoseconds … QNX locked complete up.It’s working now with QNX 6.2.1 … and I haven’t changed a single line
of code.If you’re referring to the issue with the MGT5100, that was a BSP specific
problem (as has already been pointed out in a previous thread) with an
interrupt callout, completely unrelated to OS version, kernel, etc.
Dave, I don’t want to discuss your statement in public …
The new(?) interrupt problem we got reported form a customer (also a big
automotive!) is with a x86 / ISA / 6.2.0 system and … again, a two
channel CAN interface!
If you want to contact me directly, so please use my
as steinhoff-automation dot com address.
Armin
The goal should be to discover
the mechanism by which they are not “independent”. It may be O/S,
hardware, or driver. Personally, I am curious. I certainly want to be
able to rely on QNX to provide sufficiently low latencies and/or
accurate scheduling, so that the interrupt load you are discussing can
be easily handled.I have different experiences … see above.
Armin
–
David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com
Rennie Allen wrote:
Armin Steinhoff wrote:
but it may help if you
could you post the snippet of code that handles interrupts in your
resmgrs.
Would be waste of time … after working 12 years with QNX I know how to
I’m usually thrilled if someone volunteers to take a look at my code,
and I’ve been writing interrupt handlers for QNX for over 15 years. The
only reason I might not jump at the opportunity is if the code is too
complex to be handled in this forum (or would simply be too great a
burden on the reviewer); but Kevin asked for interrupt handlers, they
couldn’t be complicated… could they ?
Please read my initial message … I didn’t ask for help for writing
interrupt handlers.
Kevin is simply asking for some code to give context in order to aid in
understanding what the issue might be.As for the “Both resmgrs are working completely independently”
comment, this obviously is not true, since your complaint is that they
are interacting in an undesirable way.
No … they don’t interact. There seems to be a problem with the OS
if it has to handle both independent resmgr concurrently at a high
interrupt load or if both interrupts are raised up at the same time.
BTW … there was a similar problem with the PPC version of QNX6.2.0A.
If two interrupts are raised up with a time difference in the range of
nanoseconds … QNX locked complete up.
It’s working now with QNX 6.2.1 … and I haven’t changed a single line
of code.
The goal should be to discover
the mechanism by which they are not “independent”. It may be O/S,
hardware, or driver. Personally, I am curious. I certainly want to be
able to rely on QNX to provide sufficiently low latencies and/or
accurate scheduling, so that the interrupt load you are discussing can
be easily handled.
I have different experiences … see above.
Armin
Igor Kovalenko wrote:
“Rennie Allen” <> rgallen@attbi.com> > wrote in message
news:bi1fco$72t$> 1@inn.qnx.com> …
[ clip … ]
It would also help to put things into context if we knew what is clock
frequency, what are interrupt numbers assigned to those ISA devices, what
else is on the ISA/PCI buses, are those interrupts edge or level triggered,
etc.
It would help if there are some problems with the resmgr … but that’s
not the case.
I also didn’t ask for help for this issue …
Armin
Rennie Allen wrote:
Armin Steinhoff wrote:
BTW, is it an insult to say ‘I don’t need help in writing interrupt
handlers’??It is if you brush off a reasonable request for more information, with the
implication that the person asking is inexperienced and or naive in comparison
with you.
Regardless if a person is experienced, inexperienced, naive or whatever,
the person should be able at least to understand what the question was.
If a person never saw that problem, why to feel addressed with my
question?
Sorry Rennie, this is the OS NG and not the cafe NG …
I wanted a related answer, nothing else.
btw: I don’t think Igors’ interpretation is strange, it is my interpretation
also; and I bet it is most peoples interpretation.
Whatever you and others interpret, it’s up to you amd the others.
My impression is that here are some participants in the NGs who identify
themselves with QNX and feel attacked personally if the reason for a
problem could be QNX…
I asked simply:
“are there any problems known with nested interrupts
at a high interrupt load? (QNX 6.2.0A, x86)”OK, I’ll buy that this was your original intent. How about next time someone
asks a question that implies that they want to help you, and you don’t really
want any help; instead of brushing them off rudely, you simply explain that you
just wanted to know if there were any known problems with the O/S ?What would be really cool is if you added something like “thanks anyway”.
Rennie, the answer on my question was really annoying:
“Not that we will find anything wrong with your code, but it may
help if you could you post the snippet of code that handles
interrupts in your resmgrs.”
As you like to interpret, just my interpretation to that answer:
And now you expect that I say “thanks anyway”… you can’t expect that
everyone in these NGs has American behaviour, just because of the
language is English and QSSL is a Canadian company …
May be you feel that the answer on my question was polite, for me it
was impertinent… just my interpretation.
Armin
Armin Steinhoff wrote:
And now you expect that I say “thanks anyway”…
I didn’t expect that, I said it would be cool (going a little above and beyond
common courtesy).
you can’t expect that
everyone in these NGs has American behaviour, just because of the
language is English and QSSL is a Canadian company …
That’s a change; a European claiming that courtesy is an American trait; being
an American, I’ll take that as a compliment. Thank you
Rennie
Armin Steinhoff <a-steinhoff@web.de> wrote in message
news:3F45D9E5.A135827@web.de…
Whatever you and others interpret, it’s up to you amd the others.
My impression is that here are some participants in the NGs who identify
themselves with QNX and feel attacked personally if the reason for a
problem could be QNX…
I can only speak for myself, but I’d be first up to identify a problem if
there was one. There isn’t anything personal here (unless of course one
made it personal).
I asked simply:
“are there any problems known with nested interrupts
at a high interrupt load? (QNX 6.2.0A, x86)”
The answer is No.
Have you actually verified that the interrupt line associated with the
resource manager which does not respond is being asserted (edge/level)
properly, even if the manager doesn’t see it?
As you like to interpret, just my interpretation to that answer:
- he was not able to read and understand the question
Even I can’t understand some of the broken english that gets posted to the
newsgroups.
- examination of a snipped code can’t tell you if others saw the
same problem
No, but if you made a mistake we could help you (related to this issue or
not). You’re human, and regardless of how long you’ve coded ISRs, you’re
not excluded from making mistakes.
- the answer implies that I didn’t check my code before asking, and
that I’ve no experience with simple handling of interrupts…
That’s utter nonsense. Asking for code is just a fast way for others to
understand what you’re doing (we all speak the same langauge in that
regard), it has no bearing on experience, knowledge or ability.
And now you expect that I say “thanks anyway”… you can’t expect that
everyone in these NGs has American behaviour, just because of the
language is English and QSSL is a Canadian company …
Being polite has nothing to do with nationality, it has to do with working
with others. If you wish not to be polite, then so be it; you can hardly
get shocked if others don’t respond the way you want them to.
May be you feel that the answer on my question was polite, for me it
was impertinent… just my interpretation.
Rennie wasn’t rude at all - it is your incorrect interpretation.
Anyways, you have your answer, the rest is very OT in this newsgroup.
-Adam
Rennie, the answer on my question was really annoying:
“Not that we will find anything wrong with your code, but it may
help if you could you post the snippet of code that handles
interrupts in your resmgrs.”As you like to interpret, just my interpretation to that answer:
- he was not able to read and understand the question
- examination of a snipped code can’t tell you if others saw the
same problem- the answer implies that I didn’t check my code before asking, and
that I’ve no experience with simple handling of interrupts…
It’s too bad that your first inclination is to assume I didn’t understand
the question. A lot of assumptions have been made here and it is making
communication difficult. Lets see if we can make some sense of it before
any more bridges are destroyed.
\
a. Kevin is an idiot
b. Kevin’s light bulb is too dim to understand my question (I do
admit, sometimes it is dim…but this time it wasn’t, trust me).
c. Kevin thinks I’m an idiot and that I don’t know how to write
interrupt handlers, so I’m going to ignore it and respond in a curt and
arrogant way…that will teach hime to read and respect me!!!
d. Kevin is a very talented QNX software engineer who very quickly
examined his recent and not so recent experiences and concluded that there
was no known issue he was aware of and is seeking to engage me in a
conversation about my problem. Wow…what a nice and considerate fellow.
It looks like to me you choose a combination of b and c. That is
unfortunate. After a long and hard thread on QNX licenses, I was actually
hoping to redeem a little bit of a professional relationship by responding
to your post in what I thought was a helpful and unoffending way.
I had hoped that you would have chosen something along the lines of ‘d’. I
don’t require you to assume I’m a talented QNX software engineer, but at
least I can expect that your first assumption was that I do understand, that
the answer is ‘no’ and that I want to be of further assistance.
In summary for #1 the rule is: Don’t assume someone doesn’t understand
because they didn’t explicitly answer your question. Assume the answer is
in the negative ‘i.e. No’ but the writer wishes to expand on the subject so
that he may…even if in a small way…be of assistance in helping you find
a solution.
2. It was obvious that you didn’t understand my opening statement. Even in
English, sometimes we have to translate into English…
“Not that we will find anything wrong with your code…”
is the same as
“No, I don’t know of any issues with QNX and interrupts. And I know that
there are no errors in your code, but I would like to help and posting it or
some other details about what you are doing would help me (and others)
understand more about the problem. We would like to offer suggestions and
generally be as helpful as possible.”
As you can see…the first is much shorter, and therefore preferable. It
assumes the reader has sufficient understanding of the modifiers used in the
sentence…and that the reader is also inclined to believe that the writer
thinks the reader is competent (which I do btw…in fact I think you are
extremely competent).
Now…I have spent time with people from Germany…and they are a very
rugged, and individualistic people. This is a good thing. I understand
that offering assistance to a German citizen who is very able to take care
of the problem himself can be considered and insult and you will more than
likely get the cold shoulder. I have been the recipient of a German Cold
Shoulder on a number of occasions. This is a cultural difference and there
is nothing wrong with it. I’m not offended.
However, it is required here that you at least be polite about refusing
help. If you don’t wish to be polite, don’t say anything. Being easily
offened is not very charateritic of strength.
Keep in mind your native tongue is German and mine is English. There will
be differences, patience is key.
Regards,
Kevin
“Armin Steinhoff” <a-steinhoff@web.de> wrote in message
news:3F45D9E5.A135827@web.de…
[…]
Sorry Rennie, this is the OS NG and not the cafe NG …
I wanted a related answer, nothing else.
You wanted a related answer, huh? Have you forgotten Armin, this is not an
official support channel where you can demand an answer. This is community
place. When you post here, you are asking other people here for courtesy.
To give you an answer, related or not, they have to spend some of their time
for you. Do they deserve a little appreciation?
Now your question “is there a known problem” was simple, indeed. Simple for
someone working at QNX, but not for general public here. No matter how much
we “identify ourselves with QNX” (I am sure lot of people at QNX are
laughing) we just don’t know that answer. Yet being good willing humans
(sometimes anyway) some of us were trying to help anyway. Let’s go to my
question now - I asked some simple details about your hardware setup (not
even about your code!) - that may actually be relevant to the problem, even
if the OS is the problem here. Was it that hard to understand? Or answer?
Just out of courtesy?
I suppose when you walk into a store and a sales associate asks “can I help
you with something” you just tell him that you did not ask for his help.
btw: I don’t think Igors’ interpretation is strange, it is my
interpretation
also; and I bet it is most peoples interpretation.Whatever you and others interpret, it’s up to you amd the others.
My impression is that here are some participants in the NGs who identify
themselves with QNX and feel attacked personally if the reason for a
problem could be QNX…
LOL. Armin, have you forgotten already about “the worst attack on QNX ever”
attributed to me?
Hi Kevin…
I hope that all is well.
I would not waste my time too much. Just forget this and let it go as I
had to do some time ago. It is not worth any of your time. It may be
that a lot of this has nothing to do with technical issues, you know…
At the end, the fundamental issues may not even be a personal thing,
but something wholly related to nationalism and political standing, who
knows. Go figure…
Any way, I hope to see you in a few weeks in CA.
Regards…
Miguel.
Kevin Stallard wrote:
Rennie, the answer on my question was really annoying:
“Not that we will find anything wrong with your code, but it may
help if you could you post the snippet of code that handles
interrupts in your resmgrs.”As you like to interpret, just my interpretation to that answer:
- he was not able to read and understand the question
- examination of a snipped code can’t tell you if others saw the
same problem- the answer implies that I didn’t check my code before asking, and
that I’ve no experience with simple handling of interrupts…
It’s too bad that your first inclination is to assume I didn’t understand
the question. A lot of assumptions have been made here and it is making
communication difficult. Lets see if we can make some sense of it before
any more bridges are destroyed.
\- You noticed I didn’t answer your question directly. This is perfectly
acceptable in the English communication. It means the answer is ‘no’ but
the person responding doesn’t want you to think this is a dead end. Now
when you read this, you had a number of choices before you. You could have
concluded a number of thingsa. Kevin is an idiot
b. Kevin’s light bulb is too dim to understand my question (I do
admit, sometimes it is dim…but this time it wasn’t, trust me).c. Kevin thinks I’m an idiot and that I don’t know how to write
interrupt handlers, so I’m going to ignore it and respond in a curt and
arrogant way…that will teach hime to read and respect me!!!d. Kevin is a very talented QNX software engineer who very quickly
examined his recent and not so recent experiences and concluded that there
was no known issue he was aware of and is seeking to engage me in a
conversation about my problem. Wow…what a nice and considerate fellow.
It looks like to me you choose a combination of b and c. That is
unfortunate. After a long and hard thread on QNX licenses, I was actually
hoping to redeem a little bit of a professional relationship by responding
to your post in what I thought was a helpful and unoffending way.
I had hoped that you would have chosen something along the lines of ‘d’. I
don’t require you to assume I’m a talented QNX software engineer, but at
least I can expect that your first assumption was that I do understand, that
the answer is ‘no’ and that I want to be of further assistance.
In summary for #1 the rule is: Don’t assume someone doesn’t understand
because they didn’t explicitly answer your question. Assume the answer is
in the negative ‘i.e. No’ but the writer wishes to expand on the subject so
that he may…even if in a small way…be of assistance in helping you find
a solution.
2. It was obvious that you didn’t understand my opening statement. Even in
English, sometimes we have to translate into English…
“Not that we will find anything wrong with your code…”
is the same as
“No, I don’t know of any issues with QNX and interrupts. And I know that
there are no errors in your code, but I would like to help and posting it or
some other details about what you are doing would help me (and others)
understand more about the problem. We would like to offer suggestions and
generally be as helpful as possible.”
As you can see…the first is much shorter, and therefore preferable. It
assumes the reader has sufficient understanding of the modifiers used in the
sentence…and that the reader is also inclined to believe that the writer
thinks the reader is competent (which I do btw…in fact I think you are
extremely competent).
Now…I have spent time with people from Germany…and they are a very
rugged, and individualistic people. This is a good thing. I understand
that offering assistance to a German citizen who is very able to take care
of the problem himself can be considered and insult and you will more than
likely get the cold shoulder. I have been the recipient of a German Cold
Shoulder on a number of occasions. This is a cultural difference and there
is nothing wrong with it. I’m not offended.
However, it is required here that you at least be polite about refusing
help. If you don’t wish to be polite, don’t say anything. Being easily
offened is not very charateritic of strength.
Keep in mind your native tongue is German and mine is English. There will
be differences, patience is key.
Regards,
Kevin
\
moved to qdn.cafe
“Miguel Simon” <simon@ou.edu> wrote in message
news:3F46B5C0.2070508@ou.edu…
Hi Kevin…
I hope that all is well.
I would not waste my time too much. Just forget this and let it go as I
had to do some time ago. It is not worth any of your time. It may be
that a lot of this has nothing to do with technical issues, you know…
At the end, the fundamental issues may not even be a personal thing,
but something wholly related to nationalism and political standing, who
knows. Go figure…Any way, I hope to see you in a few weeks in CA.
Regards…
Miguel.
Kevin Stallard wrote:
Rennie, the answer on my question was really annoying:
“Not that we will find anything wrong with your code, but it may
help if you could you post the snippet of code that handles
interrupts in your resmgrs.”As you like to interpret, just my interpretation to that answer:
- he was not able to read and understand the question
- examination of a snipped code can’t tell you if others saw the
same problem- the answer implies that I didn’t check my code before asking, and
that I’ve no experience with simple handling of interrupts…
It’s too bad that your first inclination is to assume I didn’t
understand
the question. A lot of assumptions have been made here and it is making
communication difficult. Lets see if we can make some sense of it
before
any more bridges are destroyed.
\- You noticed I didn’t answer your question directly. This is
perfectly
acceptable in the English communication. It means the answer is ‘no’
but
the person responding doesn’t want you to think this is a dead end. Now
when you read this, you had a number of choices before you. You could
have
concluded a number of thingsa. Kevin is an idiot
b. Kevin’s light bulb is too dim to understand my question (I
do
admit, sometimes it is dim…but this time it wasn’t, trust me).c. Kevin thinks I’m an idiot and that I don’t know how to write
interrupt handlers, so I’m going to ignore it and respond in a curt and
arrogant way…that will teach hime to read and respect me!!!d. Kevin is a very talented QNX software engineer who very
quickly
examined his recent and not so recent experiences and concluded that
there
was no known issue he was aware of and is seeking to engage me in a
conversation about my problem. Wow…what a nice and considerate
fellow.
It looks like to me you choose a combination of b and c. That is
unfortunate. After a long and hard thread on QNX licenses, I was
actually
hoping to redeem a little bit of a professional relationship by
responding
to your post in what I thought was a helpful and unoffending way.
I had hoped that you would have chosen something along the lines of ‘d’.
I
don’t require you to assume I’m a talented QNX software engineer, but at
least I can expect that your first assumption was that I do understand,
that
the answer is ‘no’ and that I want to be of further assistance.
In summary for #1 the rule is: Don’t assume someone doesn’t understand
because they didn’t explicitly answer your question. Assume the answer
is
in the negative ‘i.e. No’ but the writer wishes to expand on the subject
so
that he may…even if in a small way…be of assistance in helping you
find
a solution.
2. It was obvious that you didn’t understand my opening statement.
Even in
English, sometimes we have to translate into English…
“Not that we will find anything wrong with your code…”
is the same as
“No, I don’t know of any issues with QNX and interrupts. And I know
that
there are no errors in your code, but I would like to help and posting
it or
some other details about what you are doing would help me (and others)
understand more about the problem. We would like to offer suggestions
and
generally be as helpful as possible.”
As you can see…the first is much shorter, and therefore preferable.
It
assumes the reader has sufficient understanding of the modifiers used in
the
sentence…and that the reader is also inclined to believe that the
writer
thinks the reader is competent (which I do btw…in fact I think you are
extremely competent).
Now…I have spent time with people from Germany…and they are a very
rugged, and individualistic people. This is a good thing. I understand
that offering assistance to a German citizen who is very able to take
care
of the problem himself can be considered and insult and you will more
than
likely get the cold shoulder. I have been the recipient of a German
Cold
Shoulder on a number of occasions. This is a cultural difference and
there
is nothing wrong with it. I’m not offended.
However, it is required here that you at least be polite about refusing
help. If you don’t wish to be polite, don’t say anything. Being easily
offened is not very charateritic of strength.
Keep in mind your native tongue is German and mine is English. There
will
be differences, patience is key.
Regards,
Kevin
\