From: Grant Grundler <grundler@parisc-linux.org>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Grant Grundler <grundler@parisc-linux.org>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
greg@kroah.com
Subject: Re: 2.6.20 PCI Cannot allocate resource region 2
Date: Tue, 6 Feb 2007 00:04:56 -0700 [thread overview]
Message-ID: <20070206070456.GA20752@colo.lackof.org> (raw)
In-Reply-To: <1a297b360702052228r2b3eb84bpa2d3d836f5777456@mail.gmail.com>
On Tue, Feb 06, 2007 at 10:28:56AM +0400, Manu Abraham wrote:
> On 2/6/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> >On Mon, 5 Feb 2007 22:03:31 -0700 Grant Grundler
> ><grundler@parisc-linux.org> wrote:
> >
> >> On Mon, Feb 05, 2007 at 09:55:28PM -0700, Grant Grundler wrote:
> >> ...
> >> > > Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
> >ParErr- Stepping- SERR- FastB2B-
> >> > > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> ><TAbort- <MAbort- >SERR+ <PERR+
> >> > > Latency: 0, Cache Line Size 0c
> >> > > BIST is running
> >> >
> >> > BIST is required to complete in 2 seconds. Either with success or
> >failure.
> >> > I expect BIOS to have complained before launching grub/lilo.
> >>
> >> Gregkh,
> >> I just realized linux-pci bus scan should ignore devices (print a
> >warning)
> >> which have BIST set. Want a patch for this?
> >>
> >> Slight risk some previously "working" device which violates the
> >> spec might get ignored...but I hope there aren't too many of those.
> >
> >Should we wait two seconds before declaring the device dead? To see
> >whether
> >it will come back?
> >
>
>
> Wonders !
>
> I was about to give the card it's last rites. I thought well let me
> try under the other OS
Could you be more specific? Which OS? FreeBSD? :)
> I didn't have any drivers for the same, since the demodulator driver
> doesn't exist in the other OS also, but the bridge device does have
> the driver.
>
> I plugged the card in, the OS searched for drivers, since i didn't
> have any didn't load any..
> So it went under a question mark.
>
> Looking under Resources,
>
> It showed the PCI information string like this ..
>
> PCI\VEN_1822&DEV_4E35&SUBSYS_00311822&REV_01\4&2E98101C&0&10F0
>
> then i thought try with the driver eventhough support for the
> demodulator doesn't exist ..
>
> Downloaded and installed drivers ..
>
> Lo ..!
>
> Memory Range: F87FF000 - F87FFFFF
> IRQ : 17
>
> it got assigned a memory region indeed.
Excellent.
> So, to wrap it up, the device is not dead .. We have something wrong
> in the PCI subsystem probably.
Hrm maybe but not likely. I'm more inclined to believe PCI subsystem
is missing hacks needed for that device and/or BIOS.
grant
next prev parent reply other threads:[~2007-02-06 7:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 1:09 Manu Abraham
2007-02-05 3:04 ` Luming Yu
2007-02-05 4:16 ` H. Peter Anvin
2007-02-05 17:20 ` Manu Abraham
2007-02-06 4:55 ` Grant Grundler
2007-02-06 5:03 ` Grant Grundler
2007-02-06 5:33 ` Andrew Morton
2007-02-06 6:28 ` Manu Abraham
2007-02-06 7:04 ` Grant Grundler [this message]
2007-02-06 7:13 ` Manu Abraham
2007-02-06 8:46 ` Grant Grundler
2007-02-06 9:06 ` Manu Abraham
2007-02-06 9:29 ` Manu Abraham
2007-02-06 12:21 ` Luming Yu
2007-02-06 12:24 ` Manu Abraham
2007-02-06 12:56 ` Manu Abraham
2007-02-06 12:56 ` Manu Abraham
2007-02-07 4:19 ` Luming Yu
2007-02-07 5:25 ` Manu Abraham
2007-02-06 11:13 ` Manu Abraham
2007-02-06 11:52 ` Manu Abraham
2007-02-07 6:58 ` Grant Grundler
2007-02-08 5:26 ` Manu Abraham
2007-02-08 5:46 ` Manu Abraham
2007-02-06 6:24 ` Greg KH
2007-02-06 5:20 ` Manu Abraham
2007-02-06 8:25 ` Grant Grundler
2007-02-06 8:48 ` Manu Abraham
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=20070206070456.GA20752@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=abraham.manu@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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
Powered by JetHome