All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Ariel Elior <aelior@marvell.com>,
	Sudarsana Kalluru <skalluru@marvell.com>,
	Manish Chopra <manishc@marvell.com>
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: bnx2x: ppc64le: Unable to set message level greater than 0x7fff
Date: Tue, 15 Mar 2022 22:58:57 +0100	[thread overview]
Message-ID: <0497a560-8c7b-7cf8-84ee-bde1470ae360@molgen.mpg.de> (raw)

Dear Linux folks,


On the POWER8 server IBM S822LC (ppc64le), I am unable to set the 
message level for the network device to 0x0100000 but it fails.

     $ sudo ethtool -s enP1p1s0f2 msglvl 0x0100000
     netlink error: cannot modify bits past kernel bitset size (offset 56)
     netlink error: Invalid argument

Below is more information. 0x7fff is the largest value I am able to set.

```
$ sudo ethtool -i enP1p1s0f2
driver: bnx2x
version: 5.17.0-rc7+
firmware-version: bc 7.10.4
expansion-rom-version:
bus-info: 0001:01:00.2
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
$ sudo ethtool -s enP1p1s0f2 msglvl 0x7fff
$ sudo ethtool enP1p1s0f2
Settings for enP1p1s0f2:
         Supported ports: [ TP ]
         Supported link modes:   10baseT/Half 10baseT/Full
                                 100baseT/Half 100baseT/Full
                                 1000baseT/Full
         Supported pause frame use: Symmetric Receive-only
         Supports auto-negotiation: Yes
         Supported FEC modes: Not reported
         Advertised link modes:  10baseT/Half 10baseT/Full
                                 100baseT/Half 100baseT/Full
                                 1000baseT/Full
         Advertised pause frame use: Symmetric Receive-only
         Advertised auto-negotiation: Yes
         Advertised FEC modes: Not reported
         Speed: Unknown!
         Duplex: Unknown! (255)
         Auto-negotiation: on
         Port: Twisted Pair
         PHYAD: 17
         Transceiver: internal
         MDI-X: Unknown
         Supports Wake-on: g
         Wake-on: d
         Current message level: 0x00007fff (32767)
                                drv probe link timer ifdown ifup rx_err 
tx_err tx_queued intr tx_done rx_status pktdata hw wol
         Link detected: no
$ sudo ethtool -s enP1p1s0f2 msglvl 0x8000
netlink error: cannot modify bits past kernel bitset size (offset 56)
netlink error: Invalid argument
```


Kind regards,

Paul


PS: This is unrelated to the other problem.

             reply	other threads:[~2022-03-15 21:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 21:58 Paul Menzel [this message]
2022-03-16  1:35 ` bnx2x: ppc64le: Unable to set message level greater than 0x7fff Jakub Kicinski
2022-03-16  1:35   ` Jakub Kicinski
2022-03-16  5:16   ` Paul Menzel
2022-03-16  5:16     ` Paul Menzel
2022-03-16  5:33     ` Paul Menzel
2022-03-16  5:33       ` Paul Menzel
2022-03-16 11:49       ` [EXT] " Manish Chopra
2022-03-16 11:49         ` Manish Chopra
2022-03-16 18:17         ` Jakub Kicinski
2022-03-16 18:17           ` Jakub Kicinski
2022-03-16 18:52           ` Michal Kubecek
2022-03-16 18:52             ` Michal Kubecek
2022-03-16 19:18             ` Jakub Kicinski
2022-03-16 19:18               ` Jakub Kicinski

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=0497a560-8c7b-7cf8-84ee-bde1470ae360@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=aelior@marvell.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=manishc@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=skalluru@marvell.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.