From: Bjorn Helgaas <bhelgaas@google.com>
To: Matteo <rootkit85@yahoo.it>
Cc: linux-pci@vger.kernel.org
Subject: Re: [Bug 84821] New: Compex WLE900VX-7A not recognized
Date: Fri, 19 Sep 2014 20:15:30 -0600 [thread overview]
Message-ID: <20140920021530.GA2275@google.com> (raw)
In-Reply-To: <bug-84821-41252@https.bugzilla.kernel.org/>
[+cc linux-pci to make this more searchable]
On Fri, Sep 19, 2014 at 04:08:40PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=84821
>
> Bug ID: 84821
> Summary: Compex WLE900VX-7A not recognized
> Product: Drivers
> Version: 2.5
> Kernel Version: 3.16
> Hardware: All
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: PCI
> Assignee: drivers_pci@kernel-bugs.osdl.org
> Reporter: rootkit85@yahoo.it
> Regression: No
>
> I have some mini PCI-express cards that fails to be recognized.
>
> The card is a Compex WLE900VX-7A
> http://www.compex.com.sg/productdetailinfo.asp?model=WLE900VX
>
> and it can't be enumerated as PCI device.
>
> On a Lenovo Thinkpad notebook it can't never be enumerated, on my Samsung
> NP350V5C-S09IT it appears in the devices list only after a reboot (ie. must
> boot, then reboot)
>
> I'm not sure it's a Linux bug, it could be an hardware bug, but maybe it's
> possible to bring the interface up with some quirk.
>
> I attach syslog and lspci output of the first and second boot
Based on subsequent testing, it doesn't work with Windows either. That
makes me think it might be some kind of defect in the card itself. But it
sounds like maybe it happens with multiple copies of the same card?
I really don't know what to say. Unless you have some way to attach a PCIe
analyzer and verify that the card is responding and the OS is doing
something wrong, I would probably just return it and get a different card.
Bjorn
parent reply other threads:[~2014-09-20 2:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-84821-41252@https.bugzilla.kernel.org/>]
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=20140920021530.GA2275@google.com \
--to=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=rootkit85@yahoo.it \
/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).