xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Andreas Olsowski <andreas.olsowski@leuphana.de>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: megasas stops I/O when running kernel as dom0 under xen4.1/4.2
Date: Fri, 19 Aug 2011 15:57:44 +0100	[thread overview]
Message-ID: <4E4E79E8.3020808@citrix.com> (raw)
In-Reply-To: <4E4E705E.3040505@leuphana.de>



On 19/08/11 15:17, Andreas Olsowski wrote:
> Am 19.08.2011 14:28, schrieb Andrew Cooper:
>> On 15/08/11 13:52, Andreas Olsowski wrote:
>>> On 08/15/2011 12:49 PM, Simon Rowe wrote:
>>>> I've found adding
>>>>
>>>>     options megaraid_sas poll_mode_io=1
>>>>
>>>> makes both of the systems we're seeing this on stable.
>>> ive been told to try that one and it works for me too (been running
>>> test
>>> io for roughly 5 minutes now).
>>>
>>> driver version
>>> megasas: 00.00.05.30 Tue. Jan. 4 17:00:00 PDT 2011
>>
>> Hello - I am now debugging.
>>
>> It seems that the megaraid_sas driver will try and use either MSI-X or
>> legacy PCI interrupts mode, but will never try to use MSI.  The box we
>> can reproduce the problem on has MSI support but not MSI-X support.
>>
>> As an experiment, I put a single call to pci_enable_msi() in the
>> megasas_probe_one() function, immediately after pci_set_master().  I now
>> cannot reproduce the problem.
>>
>> Do any of the boxes you have which reproduce the problem set up MSI-X
>> interrupts for the megasas driver, or are they all using legacy PCI
>> interrupts?
>>
>> (I am also emailing an LSI contact asking why they do not use MSI
>> interrupts)
>>
>> ~Andrew
>>
>
> No the affected systems DO NOT use MSI-X
>
> Below is output from 3 Servers, xenturio1 and tarballerina are
> affected (same old raid controller) whereas netcatarina is not (newer
> raid controller).
>
> May i add, the 1078 series raid controller isnt listed on the LSI
> homepage, the 9260 is.
>
> The affected servers are Dell PE2950 and R710.
> Unaffectes is are the R610s.
>
> Hope this helps, below is some output of the servers:
>
>
> root@xenturio1:~# cat /proc/interrupts  |grep mega
>   16:       2545          0          0          0          0         
> 0          0          0  xen-pirq-ioapic-level  megasas
> root@xenturio1:~# lspci |grep LSI
> 01:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS
> 1078 (rev 04)
>
>
> root@tarballerina:~# cat /proc/interrupts  |grep mega
>   33:      47264          0          0          0          0         
> 0          0          0  xen-pirq-ioapic-level  megasas
> root@tarballerina:~# lspci |grep LSI
> 03:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS
> 1078 (rev 04)
>
>
> root@netcatarina:~# cat /proc/interrupts  |grep mega
> 2237:      88684          0          0          0          0         
> 0          0          0  xen-pirq-msi-x     megasas
> root@netcatarina:~# lspci |grep LSI
> 03:00.0 RAID bus controller: LSI Logic / Symbios Logic LSI MegaSAS
> 9260 (rev 05)
>

This further confirms my findings.

Do you mind intserting a call to pci_enable_msi() in the probe function
and see if that sorts out your two problem cases?

-- 
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com

  reply	other threads:[~2011-08-19 14:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 13:59 megasas stops I/O when running kernel as dom0 under xen4.1/4.2 Andreas Olsowski
2011-08-11 16:27 ` Simon Rowe
2011-08-11 22:51   ` Konrad Rzeszutek Wilk
2011-08-12  6:31     ` xen.frontend flag for higher display resolution (vnc) for HVM domU domains Mark Schneider
2011-08-12  7:26       ` Marc - A. Dahlhaus
2011-08-12  7:42     ` megasas stops I/O when running kernel as dom0 under xen4.1/4.2 Simon Rowe
2011-08-12  9:11     ` Andreas Olsowski
2011-08-12  9:23       ` Simon Rowe
2011-08-15 10:49       ` Simon Rowe
2011-08-15 12:52         ` Andreas Olsowski
2011-08-19 12:28           ` Andrew Cooper
2011-08-19 14:17             ` Andreas Olsowski
2011-08-19 14:57               ` Andrew Cooper [this message]
2011-08-19 16:37                 ` Andreas Olsowski
2011-08-19 16:49                   ` Andrew Cooper
2011-08-19 18:10                     ` Andreas Olsowski
2011-08-22  9:05                       ` Andrew Cooper
2011-08-24 12:06                         ` Andrew Cooper
2011-08-24 16:57                           ` Andrew Cooper
2011-08-24 17:09                             ` Konrad Rzeszutek Wilk
2011-08-24 17:20                               ` Andrew Cooper
2011-08-26 18:16                                 ` Andrew Cooper
2011-08-26 18:32                                   ` Andrew Cooper
2011-08-30 12:02                                     ` Andreas Olsowski
2011-08-30 12:11                                       ` Andrew Cooper
2011-08-30 12:46                                         ` Keir Fraser
2011-08-12  9:02 ` Simon Rowe
2011-08-12 16:26   ` Pasi Kärkkäinen
2011-08-15  7:44     ` Simon Rowe
2011-08-12 16:25 ` Pasi Kärkkäinen

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=4E4E79E8.3020808@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=andreas.olsowski@leuphana.de \
    --cc=xen-devel@lists.xensource.com \
    /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;
as well as URLs for NNTP newsgroup(s).