linux-kernel - Re: [2.6.34-rc1 REGRESSION] ahci 0000:00:1f.2: controller reset failed (0xffffffff)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1270614080.8518.26.camel@dc7800.home>
Date:	Tue, 06 Apr 2010 22:21:20 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Andy Isaacson <adi@...apodia.org>
Cc:	linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Chris Wright <chrisw@...s-sol.org>,
	Matthew Wilcox <willy@...ux.intel.com>,
	Yinghai Lu <yinghai@...nel.org>
Subject: Re: [2.6.34-rc1 REGRESSION] ahci 0000:00:1f.2: controller reset
	failed (0xffffffff)

On Tue, 2010-04-06 at 21:13 -0700, Andy Isaacson wrote:
> 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.

Oops, sorry, I meant it would probably work with "pci=nocrs", as you
already confirmed.  Don't bother trying "pci=use_crs"; that's turned on
automatically on your system already.

> > 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?

Nope, whatever's more convenient for you should be fine.

> > 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.

Great, thanks!  Oh, and I forgot to ask: what BIOS version are you
running?  Google found several reports of USB issues in Windows on this
box, e.g., http://tim.cexx.org/?p=529 .

I think we still have a Linux bug in that we should be reserving the
legacy VGA area, but if the BIOS is reporting an incorrect host bridge
window, that will cause us to move the AHCI controller and tickle this
bug when we wouldn't otherwise.

Bjorn


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/