All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Masashi Honma <masashi.honma@gmail.com>,
	linux-wireless@vger.kernel.org, Cedric.Izoard@ceva-dsp.com
Subject: Re: [REGRESSION, bisect] mesh: SAE connection causes kernel crash
Date: Wed, 11 Jan 2017 12:01:59 +0100	[thread overview]
Message-ID: <1484132519.23671.12.camel@sipsolutions.net> (raw)
In-Reply-To: <670a7439-50b9-4f07-1d7d-cb915547562e@gmail.com> (sfid-20170111_113614_374251_1EB7EC8D)

On Wed, 2017-01-11 at 19:36 +0900, Masashi Honma wrote:
> On 2017年01月11日 19:00, Johannes Berg wrote:
> > Nevertheless, I don't have hardware to try to reproduce it, and I
> > can't
> > see any such issues (even with real forwarding, I even just wrote a
> > wpa_s test for that) in hwsim.
> > 
> > Even a photo of the crash on the VT would help. Or maybe you can
> > set up
> > netconsole on the wired interface?
> 
> Thanks but SSH console via wired interface and laptop display does
> not show any log...

Sure, ssh won't - I was thinking of netconsole:
https://www.kernel.org/doc/Documentation/networking/netconsole.txt

johannes

  reply	other threads:[~2017-01-11 11:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 23:35 [REGRESSION, bisect] mesh: SAE connection causes kernel crash Masashi Honma
2017-01-11  8:02 ` Johannes Berg
2017-01-11  8:50   ` Masashi Honma
2017-01-11  9:00     ` Johannes Berg
2017-01-11  9:38       ` Masashi Honma
2017-01-11 10:00         ` Johannes Berg
2017-01-11 10:36           ` Masashi Honma
2017-01-11 11:01             ` Johannes Berg [this message]
2017-01-11 11:10               ` Masashi Honma
2017-01-11 11:35                 ` Cedric Izoard
2017-01-11 12:05                   ` Johannes Berg
2017-01-11 13:22                     ` Cedric Izoard
2017-01-11 13:34                       ` Johannes Berg
2017-01-11 13:41                         ` Cedric Izoard

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=1484132519.23671.12.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=Cedric.Izoard@ceva-dsp.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=masashi.honma@gmail.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.