From: Greg KH <greg@kroah.com>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
Cc: "Grundler, Grant G" <grant.grundler@hp.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: Problems with MSI-X on ia64
Date: Fri, 27 Jan 2006 04:37:34 +0000 [thread overview]
Message-ID: <20060127043734.GA32009@kroah.com> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF10B8481F1@cceexc23.americas.cpqcorp.net>
On Thu, Jan 26, 2006 at 02:37:14PM -0600, Miller, Mike (OS Dev) wrote:
> > -----Original Message-----
> > From: Grundler, Grant G
> > > We're using a 2.6.9 variant and a cciss driver with
> > MSI/MSI-X support.
> > > The kernel has MSI enabled. On ia64 the MSI-X table is all zeroes.
> >
> > Could you post the debug output you've collected so far?
>
> There are 2 MSI-X capable controllers in the system. On IPF this is what
> the tables look like:
>
> cciss: offset = 0xfe000 table offset = 0xfe000 BIR = 0x0
> cciss: 0: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: 1: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: 2: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: 3: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: using DAC cycles
> ACPI: PCI interrupt 0000:88:00.0[A] -> GSI 71 (level, low) -> IRQ 61
> cciss: MSI-X enabled
> cciss: offset = 0xfe000 table offset = 0xfe000 BIR = 0x0
> cciss: 0: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: 1: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: 2: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: 3: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: using DAC cycles
> blocks= 143305920 block_size= 512
> heads= 255, sectors= 32, cylinders= 17562
>
> blocks= 142130880 block_size= 512
> heads= 255, sectors= 32, cylinders= 17418
>
> cciss/c2d0:
>
> And this is where we hang, when enabling interrupts in the driver.
Can you try 2.6.15, or possibly 2.6.16-rc1-mm3?
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
Cc: "Grundler, Grant G" <grant.grundler@hp.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: Problems with MSI-X on ia64
Date: Thu, 26 Jan 2006 20:37:34 -0800 [thread overview]
Message-ID: <20060127043734.GA32009@kroah.com> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF10B8481F1@cceexc23.americas.cpqcorp.net>
On Thu, Jan 26, 2006 at 02:37:14PM -0600, Miller, Mike (OS Dev) wrote:
> > -----Original Message-----
> > From: Grundler, Grant G
> > > We're using a 2.6.9 variant and a cciss driver with
> > MSI/MSI-X support.
> > > The kernel has MSI enabled. On ia64 the MSI-X table is all zeroes.
> >
> > Could you post the debug output you've collected so far?
>
> There are 2 MSI-X capable controllers in the system. On IPF this is what
> the tables look like:
>
> cciss: offset = 0xfe000 table offset = 0xfe000 BIR = 0x0
> cciss: 0: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: 1: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: 2: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: 3: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: using DAC cycles
> ACPI: PCI interrupt 0000:88:00.0[A] -> GSI 71 (level, low) -> IRQ 61
> cciss: MSI-X enabled
> cciss: offset = 0xfe000 table offset = 0xfe000 BIR = 0x0
> cciss: 0: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: 1: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: 2: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: 3: vector = 0,msg data = 0, msg upper addr = 0,msg addr = 0
> cciss: using DAC cycles
> blocks= 143305920 block_size= 512
> heads= 255, sectors= 32, cylinders= 17562
>
> blocks= 142130880 block_size= 512
> heads= 255, sectors= 32, cylinders= 17418
>
> cciss/c2d0:
>
> And this is where we hang, when enabling interrupts in the driver.
Can you try 2.6.15, or possibly 2.6.16-rc1-mm3?
thanks,
greg k-h
next prev parent reply other threads:[~2006-01-27 4:37 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 17:14 Problems with MSI-X on ia64 Miller, Mike (OS Dev)
2006-01-26 17:14 ` Miller, Mike (OS Dev)
2006-01-26 17:14 ` Miller, Mike (OS Dev)
2006-01-26 17:24 ` Mark Maule
2006-01-26 17:24 ` Mark Maule
2006-01-26 20:24 ` Grant Grundler
2006-01-26 20:24 ` Grant Grundler
2006-01-26 20:37 ` Miller, Mike (OS Dev)
2006-01-26 20:37 ` Miller, Mike (OS Dev)
2006-01-26 20:37 ` Miller, Mike (OS Dev)
2006-01-27 4:37 ` Greg KH [this message]
2006-01-27 4:37 ` Greg KH
2006-01-27 15:34 ` Miller, Mike (OS Dev)
2006-01-27 15:34 ` Miller, Mike (OS Dev)
2006-01-27 15:34 ` Miller, Mike (OS Dev)
2006-02-17 7:58 ` Grant Grundler
2006-02-17 7:58 ` Grant Grundler
2006-02-17 8:46 ` Chris Wedgwood
2006-02-17 8:46 ` Chris Wedgwood
2006-02-17 14:11 ` Matthew Wilcox
2006-02-17 14:11 ` Matthew Wilcox
2006-02-17 16:36 ` Grant Grundler
2006-02-17 16:36 ` Grant Grundler
2006-02-17 19:10 ` Chris Wedgwood
2006-02-17 19:10 ` Chris Wedgwood
2006-06-01 6:35 ` Grant Grundler
2006-06-01 6:35 ` Grant Grundler
2006-02-17 19:52 ` Luck, Tony
2006-02-17 19:52 ` Luck, Tony
2006-02-17 19:52 ` Luck, Tony
2006-02-17 20:04 ` Grant Grundler
2006-02-17 20:04 ` Grant Grundler
2006-02-17 20:21 ` Roland Dreier
2006-02-17 20:21 ` Roland Dreier
2006-02-21 20:21 ` Miller, Mike (OS Dev)
2006-02-21 20:21 ` Miller, Mike (OS Dev)
2006-02-21 20:21 ` Miller, Mike (OS Dev)
2006-02-25 16:23 ` Grant Grundler
2006-02-25 16:23 ` Grant Grundler
2006-02-27 18:36 ` Miller, Mike (OS Dev)
2006-02-27 18:36 ` Miller, Mike (OS Dev)
2006-02-27 18:36 ` Miller, Mike (OS Dev)
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=20060127043734.GA32009@kroah.com \
--to=greg@kroah.com \
--cc=Mike.Miller@hp.com \
--cc=grant.grundler@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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.