From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Anyone else see host machine lockups?
Date: Tue, 22 Apr 2014 07:44:40 -0700 [thread overview]
Message-ID: <53568058.9020009@candelatech.com> (raw)
In-Reply-To: <CA+BoTQmbdYXJy_VOmoRZrLd+nLpAB6LuHp6QGYmG=-rCJuecmg@mail.gmail.com>
On 04/21/2014 11:53 PM, Michal Kazior wrote:
> On 18 April 2014 22:09, Ben Greear <greearb@candelatech.com> wrote:
>> We can reliably lock up a host system (no splats, no mention of
>> firmware crashes, system just dies) when we bring up or down a
>> bunch of vifs in a system with 3 radios in a PC.
>>
>> Anyone else seeing similar?
>
>>From what I understand this seems to be faulty CUS hardware design.
> The problem occurs when trying to perform cold reset on target device
> which sometimes leads to voltage drops/spikes which in turn breaks
> PCI-E link. Some host controllers apparently can't deal with it and
> hang the whole machine (e.g. Thinkpad T430), while others just lose
> connectivity with the device and need re-plugging (e.g. Dell E6420) or
> display a splat and need to be restarted before given PCI-E slot can
> be used again (e.g. AP135's "Data bus error").
I see this on WLE900VX NICs as well, so it's not just a CUS issue.
And, I don't think it is just cold-reset, because I do not see any
console messages about attempting a cold reset.
Thanks,
Ben
>
>
> Michal
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-04-22 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 20:09 Anyone else see host machine lockups? Ben Greear
2014-04-19 14:41 ` Adrian Chadd
2014-04-19 15:03 ` Ben Greear
2014-04-22 6:53 ` Michal Kazior
2014-04-22 14:44 ` Ben Greear [this message]
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=53568058.9020009@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=michal.kazior@tieto.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.