All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ing.Gianfranco Morandi" <gianfranco.morandi@euro-studio.it>
To: "Jean-Denis Boyer" <jdboyer@m5t.com>
Cc: "LinuxPPC" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: unhandled Intterrupt
Date: Fri, 17 Oct 2003 17:54:58 +0200	[thread overview]
Message-ID: <007601c394c7$b6bdca40$0700a8c0@eurostudio.local> (raw)
In-Reply-To: AB5AF73EAF23304EA1B932174137CED70E6EE1@m5tmail.m5t.com


Jean-Denis wrote:

>Please follow the following threads of discussion, and let us know if that
helps.
>http://lists.linuxppc.org/linuxppc-embedded/200204/msg00074.html
>http://lists.linuxppc.org/linuxppc-embedded/200205/msg00034.html

Dear Jean-Denis,

many thanks for your suggestions, they were really helpful.
First of all, we are working with the ELDK package, and as you know it uses
the 2.4.4 kernel.
By the way we didn't have any spurious Irqs prior to install our deamon and
for this we have
checked (and found!) the problem. As Dan were indicating we had a race
condition during
shutting down and re-starting the deamon.
In the past We have observed the indication of BAD Interrupts when we were
using the 2.4.18
kernel, but at the moment I do not have the possibilty to test it.
I'll keep You informed as well.

Regards

Gianfranco


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-10-17 15:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09 17:20 unhandled Intterrupt Jean-Denis Boyer
2003-10-17 15:54 ` Ing.Gianfranco Morandi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-23 15:33 Ing.Gianfranco Morandi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='007601c394c7$b6bdca40$0700a8c0@eurostudio.local' \
    --to=gianfranco.morandi@euro-studio.it \
    --cc=jdboyer@m5t.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.