linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: mikhail <mikhail.v.gavrilov@gmail.com>
Cc: mhocko@kernel.org, darrick.wong@oracle.com,
	linux-xfs@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Google Chrome cause locks held in system (kernel 4.15 rc2)
Date: Mon, 11 Dec 2017 12:48:28 +0900	[thread overview]
Message-ID: <201712110348.vBB3mSFZ068689@www262.sakura.ne.jp> (raw)
In-Reply-To: <1512963298.23718.15.camel@gmail.com>

mikhail wrote:
> > > netconsole works only within local network? destination ip may be from
> > > another network?
> > 
> > netconsole can work with another network.
> > 
> > (step 1) Verify that UDP packets are reachable. You can test with
> > 
> >          # echo test > /dev/udp/213.136.82.171/6666
> > 
> >          if you are using bash.
> 
> After this on remote machine was created folder with name of router
> external ip address.
> Inside this folder was places one file with name of current day. This
> file has size 0 of bytes and not contain "test" message inside.
> That is how it should be?

The message should be written to the log file. If not written, UDP packets
are dropped somewhere. You need to solve this problem first.

> 
> > 
> > (step 2) Verify that you specified gateway's MAC address rather than
> >          target host's MAC address. "ff:ff:ff:ff:ff:ff" suggests that
> >          netconsole is unable to resolve correct MAC address.
> > 
> 
> I am not was specified MAC address when launch netconsole. The address
> "ff:ff:ff:ff:ff:ff" was settled by default.
> Anyway does it matter for remote machine placed behind router?
> Ok, I also setted right MAC address for remote machine. But nothing is
> changed.

If remote machine is in a different network segment, you need to specify
gateway's MAC address rather than remote machine's MAC address. For more
information about netconsole, please see
https://www.kernel.org/doc/Documentation/networking/netconsole.txt .

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-12-11  3:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08  3:50 mikhail
2017-12-08  4:05 ` Darrick J. Wong
2017-12-08 10:18   ` Tetsuo Handa
2017-12-09 13:17     ` mikhail
2017-12-09 14:14       ` Tetsuo Handa
2017-12-10 21:49         ` mikhail
2017-12-11  0:14           ` Tetsuo Handa
2017-12-11  3:34             ` mikhail
2017-12-11  3:48               ` Tetsuo Handa [this message]
2018-01-06 14:17                 ` mikhail
2018-01-06 14:52                   ` Tetsuo Handa
2018-01-06 15:28                     ` mikhail
2018-01-06 15:48                       ` Tetsuo Handa
2018-01-06 17:24                         ` mikhail
2018-01-07  3:42                           ` Tetsuo Handa
2017-12-09 12:31   ` mikhail
  -- strict thread matches above, loose matches on Subject: below --
2017-12-08  3:48 mikhail

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=201712110348.vBB3mSFZ068689@www262.sakura.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --cc=darrick.wong@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --cc=mikhail.v.gavrilov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox