From: Philippe Gerum <rpm@xenomai.org>
To: Javier Herrero <jherrero@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] Problem with dm9000 and adeos-ipipe-2.6.34-blackfin-1.14-02.patch
Date: Thu, 07 Oct 2010 17:03:37 +0200 [thread overview]
Message-ID: <1286463817.13186.49.camel@domain.hid> (raw)
In-Reply-To: <4CADDF57.4070609@domain.hid>
On Thu, 2010-10-07 at 16:55 +0200, Javier Herrero wrote:
> Hi, Philippe,
>
> Thank you very much for your answer. I later found that the interrupt
> for the dm9000 was not defined OK in the platform data (it was somehow
> enabled both for rising edge and for high level). Surprisingly, this
> caused no problem without the adeos patch - this is the reason we did
> never caught that error before!
The pipeline magnifies bugs in this area, because IRQ delivery to the
regular kernel handler may be deferred to serve a high priority domain
first. So if the IRQ is actually level sensitive, but not masked
immediately when received before the decision is taken to defer the
handler, you usually get an IRQ storm.
>
> Once this was corrected, the system boots OK and the network works, but
> not OK - after a short while, two dm9000 driver messages 'status check
> fail: 70' appears. These messages indicate a problem in the reading of
> the dm9000 rx buffer. Once a status check of that kind appears, the
> driver disables automatically the dm9000 interrupts.
>
> Since now the system boots, I can easily check /proc/interrupt. I will
> also check with the patch that you suggest, and come back with any news :)
>
> Best regards,
>
> Javier
>
> El 07/10/2010 16:33, Philippe Gerum escribió:
> > On Sun, 2010-10-03 at 21:18 +0200, Javier Herrero wrote:
> >> Hello,
> >>
> >> I'm trying adeos on a Blackfin BF532 board with a DM9000 ethernet
> >> interface. If ethernet is down (cable disconnected) the system boots and
> >> works OK, but as soon as the ethernet cable is plugged, the system
> >> apparently hangs. After several seconds, a message dm9000 dm9000.0:
> >> status check fail: 226 appears.
> >>
> >> I've read a previous post about problems with dm9000 and an ARM
> >> processor,
> >> https://mail.gna.org/public/xenomai-help/2010-03/msg00147.html but it
> >> seems that there was not a response.
> >>
> >
> > dm9000 is probably not the important issue, what makes a difference is
> > which kind of IRQ is handled by this device. Knowing about the output
> > of /proc/interrupts when the pipeline is disabled would help.
> >
> > You may want to upgrade to this patch as well:
> > http://download.gna.org/adeos/patches/v2.6/blackfin/older/adeos-ipipe-2.6.34-blackfin-1.15-01.patch
> >
> >
> >> Thank you very much. Best regards,
> >>
> >> Javier
> >>
> >
>
--
Philippe.
prev parent reply other threads:[~2010-10-07 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 19:18 [Adeos-main] Problem with dm9000 and adeos-ipipe-2.6.34-blackfin-1.14-02.patch Javier Herrero
2010-10-07 14:33 ` Philippe Gerum
2010-10-07 14:55 ` Javier Herrero
2010-10-07 15:03 ` Philippe Gerum [this message]
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=1286463817.13186.49.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=adeos-main@gna.org \
--cc=jherrero@domain.hid \
/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.