public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: dann frazier <dannf@hp.com>
Cc: linux-scsi@vger.kernel.org, kadesai@lsi.com
Subject: Re: mptsas, msi and the dl585 g2
Date: Tue, 30 Jun 2009 11:35:45 -0700	[thread overview]
Message-ID: <4A4A5B01.9040200@kernel.org> (raw)
In-Reply-To: <20090630180300.GA9971@ldl.fc.hp.com>

dann frazier wrote:
> hey,
>  I'm finding problems when booting a dl585g2 w/ an LSISAS1068
> controller. In brief, this system system stopped booting once MSI
> became disabled by default in mptbase. Passing the parameter
> 'mpt_msi_enable_sas=1' to mptbase allows it to work again (tested w/
> 2.6.30).
> 
>  The symptom is that the system starts up, and we see the following:
> 
> ======== SNIP =========
> [    6.941489] hub 3-2:1.0: USB hub found
> [    6.943705] hub 3-2:1.0: 7 ports detected
> [    6.992639] Copyright (c) 1999-2008 LSI Corporation
> [    7.014262] Fusion MPT SAS Host driver 3.04.07
> [    7.021685] mptsas 0000:42:01.0: PCI INT A -> GSI 24 (level, low) -> IRQ 24
> [    7.026597] usb 1-6.3: new full speed USB device using ehci_hcd and address 3
> [    7.071143] mptbase: ioc0: Initiating bringup
> [    7.102198] usb 1-6.3: New USB device found, idVendor=0e34, idProduct=0204
> [    7.119107] usb 1-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [    7.128171] usb 1-6.3: Product: iPort/USB I2C Host Adapter
> [    7.160994] usb 1-6.3: Manufacturer: Silicon Labs
> [    7.171468] usb 1-6.3: SerialNumber: 0001248
> [    7.174931] usb 1-6.3: configuration #1 chosen from 1 choice
> [    7.360010] ioc0: LSISAS1068 B0: Capabilities={Initiator}
> [   40.581020] mptbase: ioc0: Initiating recovery
> [   71.190560] Clocksource tsc unstable (delta = 4398041105588 ns)
> [   81.190160] mptbase: ioc0: Initiating recovery
> ======== SNIP =========
> 
> These "Initiating recovery" messages are printed periodically, and the
> system never recovers.

Dann, that could be : ioapic routing in ACPI DSDT is not right somehow.

please try to move the card to other slot to get some luck.
or pci=routeirq could help too sometimes.


YH

  reply	other threads:[~2009-06-30 18:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 18:03 mptsas, msi and the dl585 g2 dann frazier
2009-06-30 18:35 ` Yinghai Lu [this message]
2009-07-03 22:57   ` dann frazier
2009-07-04 19:30     ` Yinghai Lu
2009-07-06 16:57       ` dann frazier
2009-07-09 18:59       ` dann frazier
2009-07-09 19:17         ` Yinghai Lu
2009-07-09 19:34           ` Yinghai Lu
2009-07-09 19:48             ` Yinghai Lu
2009-07-09 20:40               ` James Bottomley
2009-07-09 21:12                 ` Yinghai Lu
2009-07-09 21:41                 ` [PATCH} x86/pci: insert ioapic resource before assign unassigned resource for pci Yinghai Lu
2009-07-09 22:01                   ` dann frazier
2009-07-10 16:36                   ` [PATCH] x86/pci: insert ioapic resource before assign unassigned resource for pci -v2 Yinghai Lu
2009-07-10 20:03                     ` Jesse Barnes
2009-07-10 21:27                     ` Linus Torvalds

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=4A4A5B01.9040200@kernel.org \
    --to=yinghai@kernel.org \
    --cc=dannf@hp.com \
    --cc=kadesai@lsi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox