public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gavin Shan" <gshan@alcatel-lucent.com>
To: <linux-kernel@vger.kernel.org>
Subject: Bogus devices detected from Marvel MV64460
Date: Mon, 8 Sep 2008 20:18:00 +0800	[thread overview]
Message-ID: <001b01c911ac$f096edc0$0100a8c0@microsof291b50> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb2312", Size: 4022 bytes --]

Hello, My board is using MV64460 chip and lots of bogus devices were
detected at PCI bus probe time.Those bogus devices has vendor/device
id of 0x648511ab. I don't know why there has so much devices with
vendor/device id of 0x648511ab. Anybody has ideas?

pcibios_init:probe devices for hose 0xc0546800
I/O  0xd0000000-0xd0000fff
MEM0 0x80000000-0x87ffffff
MEM1 0xf2000000-0xf203ffff
MEM2 0xb0000000-0xb0003fff
pci_scan_child_bus: PCI: Scanning bus 0000:00
pci_scan_device: devfn=0, vendor_id=0x648511ab
pci_scan_device: devfn=8, vendor_id=0xffffffff
pci_scan_device: devfn=16, vendor_id=0xffffffff
pci_scan_device: devfn=24, vendor_id=0xffffffff
pci_scan_device: devfn=32, vendor_id=0xffffffff
pci_scan_device: devfn=40, vendor_id=0x648511ab
pci_scan_device: devfn=48, vendor_id=0x648511ab
pci_scan_device: devfn=56, vendor_id=0x648511ab
pci_scan_device: devfn=64, vendor_id=0xcafeb00b
plexus_fixup_mlba: set flags to IORESOURCE_MEM
plexus_fixup_mlba: start 0xb0000000, end=0xb0003fff
pci_scan_device: devfn=72, vendor_id=0x2222b00b
pci_scan_device: devfn=80, vendor_id=0xffffffff
pci_scan_device: devfn=88, vendor_id=0xffffffff
pci_scan_device: devfn=96, vendor_id=0xffffffff
pci_scan_device: devfn=104, vendor_id=0xffffffff
pci_scan_device: devfn=112, vendor_id=0xffffffff
pci_scan_device: devfn=120, vendor_id=0xffffffff
pci_scan_device: devfn=128, vendor_id=0xffffffff
pci_scan_device: devfn=136, vendor_id=0xffffffff
pci_scan_device: devfn=144, vendor_id=0xffffffff
pci_scan_device: devfn=152, vendor_id=0xffffffff
pci_scan_device: devfn=160, vendor_id=0xffffffff
pci_scan_device: devfn=168, vendor_id=0xffffffff
pci_scan_device: devfn=176, vendor_id=0xffffffff
pci_scan_device: devfn=184, vendor_id=0xffffffff
pci_scan_device: devfn=192, vendor_id=0xffffffff
pci_scan_device: devfn=200, vendor_id=0xffffffff
pci_scan_device: devfn=208, vendor_id=0xffffffff
pci_scan_device: devfn=216, vendor_id=0xffffffff
pci_scan_device: devfn=224, vendor_id=0xffffffff
pci_scan_device: devfn=232, vendor_id=0xffffffff
pci_scan_device: devfn=240, vendor_id=0xffffffff
pci_scan_device: devfn=248, vendor_id=0xffffffff
pcibios_init:probe devices for hose 0xc0548000
I/O  0xd1000000-0xd101ffff
MEM0 0x88000000-0x8fffffff
MEM1 0x00000000-0x00000000
MEM2 0x00000000-0x00000000
pci_scan_child_bus: PCI: Scanning bus 0001:00
pci_scan_device: devfn=0, vendor_id=0x648511ab
pci_scan_device: devfn=8, vendor_id=0xffffffff
pci_scan_device: devfn=16, vendor_id=0x06801095
pci_scan_device: devfn=24, vendor_id=0x06801095
pci_scan_device: devfn=32, vendor_id=0xffffffff
pci_scan_device: devfn=40, vendor_id=0xffffffff
pci_scan_device: devfn=48, vendor_id=0xffffffff
pci_scan_device: devfn=56, vendor_id=0xffffffff
pci_scan_device: devfn=64, vendor_id=0xffffffff
pci_scan_device: devfn=72, vendor_id=0xffffffff
pci_scan_device: devfn=80, vendor_id=0xffffffff
pci_scan_device: devfn=88, vendor_id=0x648511ab
pci_scan_device: devfn=96, vendor_id=0x648511ab
pci_scan_device: devfn=104, vendor_id=0x648511ab
pci_scan_device: devfn=112, vendor_id=0xffffffff
pci_scan_device: devfn=120, vendor_id=0xffffffff
pci_scan_device: devfn=128, vendor_id=0xffffffff
pci_scan_device: devfn=136, vendor_id=0xffffffff
pci_scan_device: devfn=144, vendor_id=0xffffffff
pci_scan_device: devfn=152, vendor_id=0xffffffff
pci_scan_device: devfn=160, vendor_id=0xffffffff
pci_scan_device: devfn=168, vendor_id=0xffffffff
pci_scan_device: devfn=176, vendor_id=0xffffffff
pci_scan_device: devfn=184, vendor_id=0xffffffff
pci_scan_device: devfn=192, vendor_id=0xffffffff
pci_scan_device: devfn=200, vendor_id=0xffffffff
pci_scan_device: devfn=208, vendor_id=0xffffffff
pci_scan_device: devfn=216, vendor_id=0xffffffff
pci_scan_device: devfn=224, vendor_id=0xffffffff
pci_scan_device: devfn=232, vendor_id=0xffffffff
pci_scan_device: devfn=240, vendor_id=0xffffffff
pci_scan_device: devfn=248, vendor_id=0xffffffffÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

                 reply	other threads:[~2008-09-08 12:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='001b01c911ac$f096edc0$0100a8c0@microsof291b50' \
    --to=gshan@alcatel-lucent.com \
    --cc=linux-kernel@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