All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Chapman <doug.chapman@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: panic from vector domain patch (was RE: Linus' tree broken?)
Date: Wed, 25 Jul 2007 05:09:45 +0000	[thread overview]
Message-ID: <1185340185.14444.16.camel@phobos> (raw)
In-Reply-To: <1185239265.19353.6.camel@phobos>

Yasuaki,

I added a bunch of printk's to try to better understand this.
ia64_mv.setup does get initialized properly but then gets overwritten.
It appears that it gets overwritten in __bind_irq_vector but I have not
narrowed down exactly where.  I put a printk at the top and bottom of
this function to show what ia64_mv.setup is and I am finding that on the
3rd call to this function it causes ia64_mv.setup to get set to -1.

It is getting way too late for me (1AM here).  I will try to dig into
this more tomorrow but at least I have narrowed it down to a bit of code
that actually is touched by the commit that causes the panic.

- Doug



  parent reply	other threads:[~2007-07-25  5:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24  1:07 panic from vector domain patch (was RE: Linus' tree broken?) Doug Chapman
2007-07-24  2:06 ` Doug Chapman
2007-07-24  2:26 ` Yasuaki Ishimatsu
2007-07-24 13:09 ` Yasuaki Ishimatsu
2007-07-24 13:55 ` Doug Chapman
2007-07-24 14:28 ` Kenji Kaneshige
2007-07-25  0:19 ` Yasuaki Ishimatsu
2007-07-25  1:12 ` Doug Chapman
2007-07-25  2:55 ` Doug Chapman
2007-07-25  5:09 ` Doug Chapman [this message]
2007-07-25  8:59 ` Kenji Kaneshige
2007-07-25 13:03 ` Doug Chapman
2007-07-25 13:37 ` Horms
2007-07-25 15:26 ` Doug Chapman
2007-07-26  1:31 ` Horms
2007-07-26  2:55 ` Horms
2007-07-30  9:56 ` Jes Sorensen
2007-07-30 13:42 ` Doug Chapman
2007-07-30 13:53 ` Jes Sorensen
2007-07-31 14:34 ` Jes Sorensen

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=1185340185.14444.16.camel@phobos \
    --to=doug.chapman@hp.com \
    --cc=linux-ia64@vger.kernel.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.