All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steven A. Falco" <sfalco@domain.hid>
To: "Steven A. Falco" <sfalco@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Oops with ifconfig on Sequioa AMCC 440EPX board
Date: Tue, 30 Sep 2008 10:45:44 -0400	[thread overview]
Message-ID: <48E23B98.3000403@domain.hid> (raw)
In-Reply-To: <48E22F37.2000903@domain.hid>

Steven A. Falco wrote:
> Philippe Gerum wrote:
>> Wolfgang Grandegger wrote:
>>> Hello,
>>>
>>> I get the following Oops with a Xenomai patch kernel when configuring
>>> the EEPRO100 on the PCI slot:
> ...
>>> Any idea where the problem could be?
>>>
>> As you pointed out, there was an issue with cascaded UICs. The following patch
>> should fix it (will be merged in the upcoming 2.2-05):
> 
> Thanks!  The patch does indeed fix it.  One comment, though.  I had
> turned on spinlock debugging as well as adding your patch.  That
> combination produces the bugs below.  Once I turn off spinlock
> debugging (with the patch still included), then things work properly.
> 
> So, I don't know if this bug is totally unrelated to Ipipe.  I'll
> investigate and post again with the results.
> 
> 	Steve
> 
> 

Turns out the spinlock bug is totally unrelated to Ipipe, as per the following:

http://kerneltrap.org/mailarchive/linux-netdev/2008/8/13/2926664/thread

So, I believe your patch completely fixes the issue I initially reported.

	Thanks,
	Steve





      reply	other threads:[~2008-09-30 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05 10:09 [Xenomai-help] Oops with ifconfig on Sequioa AMCC 440EPX board Wolfgang Grandegger
2008-09-06 14:16 ` Wolfgang Grandegger
2008-09-06 14:34   ` Gilles Chanteperdrix
2008-09-30 10:41 ` Philippe Gerum
2008-09-30 13:52   ` Steven A. Falco
2008-09-30 14:45     ` Steven A. Falco [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=48E23B98.3000403@domain.hid \
    --to=sfalco@domain.hid \
    --cc=xenomai@xenomai.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.