public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Isaacson <adi@hexapodia.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Chris Wright <chrisw@sous-sol.org>,
	Matthew Wilcox <willy@linux.intel.com>,
	Yinghai Lu <yinghai@kernel.org>
Subject: Re: [2.6.34-rc1 REGRESSION] ahci 0000:00:1f.2: controller reset failed (0xffffffff)
Date: Tue, 6 Apr 2010 21:13:33 -0700	[thread overview]
Message-ID: <20100407041333.GF29192@hexapodia.org> (raw)
In-Reply-To: <1270612783.8518.15.camel@dc7800.home>

On Tue, Apr 06, 2010 at 09:59:43PM -0600, Bjorn Helgaas wrote:
> > I suspect it's due to:
> > 
> > [    3.094038] pci 0000:00:1f.2: no compatible bridge window for [mem 0xff970000-0xff9707ff]
> > [    3.103001] pci 0000:00:1f.2: can't reserve [mem 0xff970000-0xff9707ff]
> 
> Thanks a lot for reporting this!
> 
> No need to bisect it.  I'm pretty sure 2.6.34-rc1 will boot fine if you
> use "pci=use_crs" (obviously that's only a temporary workaround until we
> fix the real problem).

pci=nocrs worked on 2.6.34-rc3-00299-g0fdf867.  I won't be back in front
of the machine to try use_crs until Thursday.

> put AHCI device, so we moved the AHCI device.  Unfortunately, we put it
> at [mem 0x000a0000-0x000a07ff], which wasn't a very good choice because
> that's probably already used by a VGA device.

The machine has one VGA controller exposed currently; there may be
another integrated Intel video controller on the motherboard and
disabled by the BIOS.

01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 290 (rev a1) (prog-if 00 [VGA controller])
        Subsystem: nVidia Corporation Device 0492
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at fc000000 (32-bit, non-prefetchable) [size=16M]
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
        I/O ports at dc80 [size=128]
        Expansion ROM at fde00000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: nouveau

(this is from the pci=nocrs boot.)

> If you happen to have Windows on this box, I'd love to know whether *it*
> moves the AHCI device, too, or whether Windows interprets the BIOS
> information differently than we do.  If you have Windows and can collect
> screenshots of the Device Manager resources for the PCI bus and the AHCI
> controller, that would be a good start.

The machine only has Linux installed, but I may have access to another
T3400 that can dual-boot.  Any preference for XP versus Win7?

> Would you mind trying the patch below and the patch and kernel args
> here:
>   https://bugzilla.kernel.org/show_bug.cgi?id=15533#c5
> 
> This will (1) reserve the VGA area, so we should put the AHCI device
> elsewhere, and (2) collect a few more details about exactly what the
> BIOS is reporting.

I'll try that on Thursday.

-andy

  reply	other threads:[~2010-04-07  4:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 22:54 [2.6.34-rc1 REGRESSION] ahci 0000:00:1f.2: controller reset failed (0xffffffff) Andy Isaacson
2010-04-07  1:08 ` Yinghai
2010-04-07  1:28   ` Andy Isaacson
2010-04-07  2:19     ` Yinghai Lu
2010-04-07  3:59 ` Bjorn Helgaas
2010-04-07  4:13   ` Andy Isaacson [this message]
2010-04-07  4:21     ` Bjorn Helgaas
2010-04-07 17:16       ` Andy Isaacson
2010-04-07 18:08         ` Bjorn Helgaas
2010-04-07 18:42           ` Andy Isaacson
2010-04-12 17:56   ` Bjorn Helgaas
2010-04-12 19:33     ` Andy Isaacson
2010-04-12 21:56     ` Matthew Wilcox
2010-04-13  2:14       ` H. Peter Anvin
2010-04-13  1:51     ` H. Peter Anvin
2010-04-09 19:10 ` Maciej Rutecki

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=20100407041333.GF29192@hexapodia.org \
    --to=adi@hexapodia.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=chrisw@sous-sol.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@linux.intel.com \
    --cc=yinghai@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