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: Tue, 24 Jul 2007 13:55:07 +0000 [thread overview]
Message-ID: <1185285307.3805.2.camel@athlon> (raw)
In-Reply-To: <1185239265.19353.6.camel@phobos>
On Tue, 2007-07-24 at 22:09 +0900, Yasuaki Ishimatsu wrote:
> Hi Doug,
>
> Yasuaki Ishimatsu wrote:
> > Hi Doug,
> >
> > Doug Chapman wrote:
> >> On Mon, 2007-07-23 at 13:42 -0700, Luck, Tony wrote:
> >>>>> Could be, but it sounds like there's something fishy in the current
> >>>>> tree - Doug Chapman is having problems as well, presumably on zx1 boxes.
> >>>> I am seeing the panic on HP zx1 and zx2 systems. Currently doing a git
> >>>> bisect to narrow it down.
> >>> 2.6.23-rc1 booted OK on my rx2620. On the zx2000 too (though X is currently
> >>> behaving weirdly, I think that might be some other issue though).
> >>>
> >>> -Tony
> >> Through the magic of git-bisect I have narrowed it down to this commit
> >> (although I don't know why):
> >>
> >> commit 4994be1b3fe9120c88022ff5c0c33f6312b17adb
> >> Author: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
> >> Date: Tue Jul 17 21:22:33 2007 +0900
> >>
> >> [IA64] Add support for vector domain
> >>
> >> Add fundamental support for multiple vector domain. There still exists
> >> only one vector domain even with this patch. IRQ migration across
> >> domain is not supported yet by this patch.
> >>
> >> Signed-off-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
> >> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
> >> Signed-off-by: Tony Luck <tony.luck@intel.com>
> >>
> >>
> >>
> >> As far as why I see this and so far others have not I have 2 guesses.
> >> It could be related to firmware version (I have all my systems with
> >> the latest available version) or, it could be the version of elilo
> >> (perhaps more of a longshot).
> >>
> >> Or, could be my .config file (ok, now that I think of it that may be
> >> more likely). Attaching my .config here. This is a custom config
> >> that started out as the fedora 7 .config but I have made some changes
> >> over time.
> >
> > Oops, I forgot to consider assign_irq_vector(AUTO_ASSIGN) case.
> > I'm writing bug fix patch now. Wait a moment.
>
> Unfortunately, I don't have any ski simulator environment. I attached
> the bug fix patch. Could you try this patch?
>
> Thanks,
> Yasuaki Ishimatsu
>
>
Yasuaki,
With this patch it still panics in the same way. I am building with
CONFIG_IA64_GENERIC and booting on an HP rx6600. I do not have the ski
simulator either.
- Doug
next prev parent reply other threads:[~2007-07-24 13:55 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 [this message]
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
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=1185285307.3805.2.camel@athlon \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox