From: Ben Greear <greearb@candelatech.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Anyone else see host machine lockups?
Date: Sat, 19 Apr 2014 08:03:45 -0700 [thread overview]
Message-ID: <53529051.2040702@candelatech.com> (raw)
In-Reply-To: <CAJ-Vmok6D88OHUPKhL0hXqX1RFDv42OkuChDBfEN7nB2JLM_sg@mail.gmail.com>
On 04/19/2014 07:41 AM, Adrian Chadd wrote:
> Heh, no, but back in the day this'd happen if the DMA engine wasn't
> shut down in the right order. The NIC would start DMAing crap all over
> random memory.
>
> I wonder if that's happening here.
Maybe, but I would hope that such a problem would at least often crash
the OS with some strange crashes as opposed to just silent host lockup?
Thanks,
Ben
>
>
>
> -a
>
>
> On 18 April 2014 13: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?
>>
>> Thanks,
>> Ben
>>
>> --
>> 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
--
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
next prev parent reply other threads:[~2014-04-19 15:04 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 [this message]
2014-04-22 6:53 ` Michal Kazior
2014-04-22 14:44 ` Ben Greear
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=53529051.2040702@candelatech.com \
--to=greearb@candelatech.com \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.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