From: Jesse Brandeburg <jesse.brandeburg@gmail.com>
To: Ian Kumlien <ian.kumlien@gmail.com>
Cc: intel-wired-lan@lists.osuosl.org, anthony.l.nguyen@intel.com,
Piotr Skajewski <piotrx.skajewski@intel.com>,
jesse.brandeburg@intel.com
Subject: Re: [Intel-wired-lan] [ixgbe] regression: jumbo frames not working
Date: Sat, 6 May 2023 11:33:22 -0700 [thread overview]
Message-ID: <CAEuXFEzznsMofUJNLvRQKugDs+EpY1eEKkdykM5_O=9wkgBKPw@mail.gmail.com> (raw)
In-Reply-To: <CAA85sZsZMFMCLtL_70AMXvVsQ+jNze0C=sNmZfwNdwUhTp_kxw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 677 bytes --]
On Fri, May 5, 2023 at 1:28 PM Ian Kumlien <ian.kumlien@gmail.com> wrote:
> As a side note, I don't understand how the switch booted with jumbo
> frames off - the config stated that they should be on....
> So, some kind of failover... sorry for the noise..
>
> On Fri, May 5, 2023 at 7:50 PM Ian Kumlien <ian.kumlien@gmail.com> wrote:
> >
> > Sorry... It seems like my cisco switch booted with jumbo-frames
> > disabled after a power outage...
> > The conf says it should be enabled - but somehow it wasn't :/
Thanks for letting us know!
#regzbot resolve: not a regression. The reporter found the cause to be a
network config issue after a power outage.
[-- Attachment #1.2: Type: text/html, Size: 1181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 162 bytes --]
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-05-06 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 21:13 [Intel-wired-lan] [ixgbe] regression: jumbo frames not working Ian Kumlien
2023-04-30 16:29 ` Jesse Brandeburg
2023-04-30 17:01 ` Ian Kumlien
2023-05-05 14:21 ` Piotr Skajewski
2023-05-05 17:50 ` Ian Kumlien
2023-05-05 20:28 ` Ian Kumlien
2023-05-06 18:33 ` Jesse Brandeburg [this message]
2023-05-08 8:42 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-05-01 7:51 ` Linux regression tracking #adding (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='CAEuXFEzznsMofUJNLvRQKugDs+EpY1eEKkdykM5_O=9wkgBKPw@mail.gmail.com' \
--to=jesse.brandeburg@gmail.com \
--cc=anthony.l.nguyen@intel.com \
--cc=ian.kumlien@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=piotrx.skajewski@intel.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;
as well as URLs for NNTP newsgroup(s).