linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 32472] New: Mips ar71xx can't allocate I/O resource for mini-pci IDE storage.
Date: Fri, 1 Apr 2011 20:44:59 GMT	[thread overview]
Message-ID: <bug-32472-11633@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=32472

           Summary: Mips ar71xx can't allocate I/O resource for mini-pci
                    IDE storage.
           Product: IO/Storage
           Version: 2.5
    Kernel Version: Linux OpenWrt 2.6.32.25
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: IDE
        AssignedTo: io_ide@kernel-bugs.osdl.org
        ReportedBy: ciusss@gmail.com
        Regression: No


Hi, 
I have system composed by: router station pro ( architecture mips cpu ar7161 )
with openwrt backfire 10.03-rc4, i have installed only Axiomtek AX8931A Mini
PCI IDE Control Module in free slot.

>From dmesg command :
{{{
root@OpenWrt:~# dmesg | grep pci
pci 0000:00:00.0: reg 10 32bit mmio pref: [0x000000-0xfffffff]
pci 0000:00:00.0: reg 14 io port: [0x00-0xff]
pci 0000:00:00.0: supports D1 D2
pci 0000:00:00.0: PME# supported from D0 D1 D2 D3hot
pci 0000:00:00.0: PME# disabled
pci 0000:00:11.0: reg 10 io port: [0x1f0-0x1f7]
pci 0000:00:11.0: reg 14 io port: [0x3f4-0x3f7]
pci 0000:00:11.0: reg 18 io port: [0x170-0x177]
pci 0000:00:11.0: reg 1c io port: [0x374-0x377]
pci 0000:00:11.0: reg 20 io port: [0x6800-0x680f]
pci 0000:00:11.0: reg 24 32bit mmio: [0x000000-0x003fff]
pci 0000:00:11.0: reg 30 32bit mmio pref: [0x0dc000-0x0dffff]
pci 0000:00:11.0: supports D1
pci 0000:00:11.0: BAR 4: can't allocate I/O resource [0x00-0x00]
pci 0000:00:11.0: BAR 0: can't allocate I/O resource [0x00-0x00]
pci 0000:00:11.0: BAR 2: can't allocate I/O resource [0x00-0x00]
pci 0000:00:11.0: BAR 1: can't allocate I/O resource [0x00-0x00]
pci 0000:00:11.0: BAR 3: can't allocate I/O resource [0x00-0x00]
ath_pci: trunk
}}}
resource of id:
{{{
root@OpenWrt:~# cat /sys/bus/pci/devices/0000\:00\:11.0/resource  
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000010000000 0x0000000010003fff 0x0000000000020200
0x0000000010004000 0x0000000010007fff 0x0000000000027200
root@OpenWrt:~# 
}}}

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

             reply	other threads:[~2011-04-01 20:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01 20:44 bugzilla-daemon [this message]
2012-08-20 15:27 ` [Bug 32472] Mips ar71xx can't allocate I/O resource for mini-pci IDE storage bugzilla-daemon

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=bug-32472-11633@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).