All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Krystian Pradzynski <krystian.pradzynski@linux.intel.com>,
	hq.dev+kernel@msdfc.xyz,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Networking <netdev@vger.kernel.org>,
	Oded Gabbay <ogabbay@kernel.org>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Linux DRI Development <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
	Eric Dumazet <edumazet@google.com>,
	"Linux regression tracking \(Thorsten Leemhuis\)"
	<regressions@leemhuis.info>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
	Linux Intel Ethernet Drivers <intel-wired-lan@lists.osuosl.org>,
	Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] Unexplainable packet drop starting at v6.4
Date: Tue, 25 Jul 2023 17:47:12 -0700	[thread overview]
Message-ID: <20230725174712.66a809c4@kernel.org> (raw)
In-Reply-To: <ZMBf3Cu+MgXjOpvF@debian.me>

On Wed, 26 Jul 2023 06:50:52 +0700 Bagas Sanjaya wrote:
> This time, the bisection points out to v6.4 networking pull, so:
> 
> #regzbot introduced: 6e98b09da931a0

Ask the reporter to test 9b78d919632b, i.e. the tip of net-next before
the merge. It seems quite unlikely that the merge itself is the problem.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>,
	Krystian Pradzynski <krystian.pradzynski@linux.intel.com>,
	Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
	Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
	Oded Gabbay <ogabbay@kernel.org>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	"Linux regression tracking (Thorsten Leemhuis)"
	<regressions@leemhuis.info>,
	hq.dev+kernel@msdfc.xyz,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux DRI Development <dri-devel@lists.freedesktop.org>,
	Linux Networking <netdev@vger.kernel.org>,
	Linux Intel Ethernet Drivers <intel-wired-lan@lists.osuosl.org>
Subject: Re: Unexplainable packet drop starting at v6.4
Date: Tue, 25 Jul 2023 17:47:12 -0700	[thread overview]
Message-ID: <20230725174712.66a809c4@kernel.org> (raw)
In-Reply-To: <ZMBf3Cu+MgXjOpvF@debian.me>

On Wed, 26 Jul 2023 06:50:52 +0700 Bagas Sanjaya wrote:
> This time, the bisection points out to v6.4 networking pull, so:
> 
> #regzbot introduced: 6e98b09da931a0

Ask the reporter to test 9b78d919632b, i.e. the tip of net-next before
the merge. It seems quite unlikely that the merge itself is the problem.

WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Krystian Pradzynski <krystian.pradzynski@linux.intel.com>,
	hq.dev+kernel@msdfc.xyz,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Networking <netdev@vger.kernel.org>,
	Oded Gabbay <ogabbay@kernel.org>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Linux DRI Development <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
	Eric Dumazet <edumazet@google.com>,
	"Linux regression tracking \(Thorsten Leemhuis\)"
	<regressions@leemhuis.info>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
	Linux Intel Ethernet Drivers <intel-wired-lan@lists.osuosl.org>,
	Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: Unexplainable packet drop starting at v6.4
Date: Tue, 25 Jul 2023 17:47:12 -0700	[thread overview]
Message-ID: <20230725174712.66a809c4@kernel.org> (raw)
In-Reply-To: <ZMBf3Cu+MgXjOpvF@debian.me>

On Wed, 26 Jul 2023 06:50:52 +0700 Bagas Sanjaya wrote:
> This time, the bisection points out to v6.4 networking pull, so:
> 
> #regzbot introduced: 6e98b09da931a0

Ask the reporter to test 9b78d919632b, i.e. the tip of net-next before
the merge. It seems quite unlikely that the merge itself is the problem.

  reply	other threads:[~2023-07-26  0:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18  0:51 [Intel-wired-lan] Fwd: Unexplainable packet drop starting at v6.4 Bagas Sanjaya
2023-07-18  0:51 ` Bagas Sanjaya
2023-07-18  0:51 ` Bagas Sanjaya
2023-07-19 11:49 ` [Intel-wired-lan] " Thorsten Leemhuis
2023-07-19 11:49   ` Thorsten Leemhuis
2023-07-19 11:49   ` Thorsten Leemhuis
2023-07-19 12:30   ` [Intel-wired-lan] " Bagas Sanjaya
2023-07-19 12:30     ` Bagas Sanjaya
2023-07-19 12:30     ` Bagas Sanjaya
2023-07-19 13:00     ` [Intel-wired-lan] " Thorsten Leemhuis
2023-07-19 13:00       ` Thorsten Leemhuis
2023-07-19 13:00       ` Thorsten Leemhuis
2023-07-25 23:50 ` [Intel-wired-lan] " Bagas Sanjaya
2023-07-25 23:50   ` Bagas Sanjaya
2023-07-25 23:50   ` Bagas Sanjaya
2023-07-26  0:47   ` Jakub Kicinski [this message]
2023-07-26  0:47     ` Jakub Kicinski
2023-07-26  0:47     ` Jakub Kicinski
2023-08-30 10:07 ` [Intel-wired-lan] Fwd: " Linux regression tracking (Thorsten Leemhuis)
2023-08-30 10:07   ` Linux regression tracking (Thorsten Leemhuis)
2023-09-11 14:03   ` [Intel-wired-lan] " Thorsten Leemhuis
2023-09-11 14:03     ` Thorsten Leemhuis

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=20230725174712.66a809c4@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrzej.kacprowski@linux.intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=bagasdotme@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=edumazet@google.com \
    --cc=hq.dev+kernel@msdfc.xyz \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jacek.lawrynowicz@linux.intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=krystian.pradzynski@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ogabbay@kernel.org \
    --cc=pabeni@redhat.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=stanislaw.gruszka@linux.intel.com \
    --cc=torvalds@linux-foundation.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 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.