Public bug reported:
SRU Justification:
[Impact]
The BlueSphere like boards have a feature where the BMC
can trigger a BlueField ARM reset via ipmitool. The ipmitool
command simply toggles the signal on a BMC GPIO pin which
propagates to HOST GPIO 7. HOST GPIO 7 is setup as an
interrupt for SW r
Public bug reported:
SRU Justification:
[Impact]
There could be stack overflow in mlxbf_i2c_smbus_start_transaction().
memcpy() is called in a loop while 'operation->length' upper bound is not
checked and 'data_idx' also increments.
More details:
The operation length is verified by the caller f
Public bug reported:
SRU Justification:
[Impact]
The mlxbf-gige driver has just been upstreamed so linux-bluefield needs
to be synced up with what we have upstreamed.
[Fix]
* Cleaned up the gige driver as instructed by maintainers
* removed dependency between the mlxbf-gige driver and gpio-mlx
** Description changed:
SRU Justification:
[Impact]
- The mlxbf-gige driver has just been upstreamed so linux-bluefield needs
- to be synced up with what we have upstreamed.
+ The mlxbf-gige driver has just been upstreamed so linux-bluefield needs to be
synced up with what we have upstr
** Description changed:
SRU Justification:
[Impact]
The mlxbf-gige driver has just been upstreamed so linux-bluefield needs to be
synced up with what we have upstreamed.
- IMPORTANT: during testing phase, make sure the latest UEFI (bootloader) is
loaded on top of these changes.
+ IMP
Public bug reported:
SRU Justification:
[Impact]
* This will fix a broken i2c-mlxbf.c driver for BlueField-2.
[Fix]
* Restore previous version of the driver which was tested extensively.
This current version is what was upstreamed but was not tested on the
new BlueField-2 boards with BMC on th
: linux-bluefield (Ubuntu)
Importance: Undecided
Assignee: Asmaa Mnebhi (asmaam)
Status: In Progress
** Changed in: linux-bluefield (Ubuntu)
Assignee: (unassigned) => Asmaa Mnebhi (asmaam)
** Changed in: linux-bluefield (Ubuntu)
Status: New => In Progress
--
You re
Public bug reported:
SRU Justification:
[Impact]
* Sync up the current i2c-mlx.c driver with the upstreamed version. The name of
the i2c-mlx.c driver changed to i2c-mlxbf2.c.
* Support multi slave functionality
* And fix a bug in the core frequency
[Fix]
* Sync up the current i2c-mlx.c driver
Public bug reported:
SRU Justification:
[Impact]
* The previous ipmb_host patch broke the customer tests. They requested to make
the ipmb_host response time as long as before. In the case where the I2C bus is
made very busy, the ipmb_host driver just drops slow/delayed responses. This
fix elo
Public bug reported:
SRU Justification:
[Impact]
During the reboot test, QA found an intermittent issue where the OOB link is
down.
The link is down because the KSZ9031 PHY fails to complete autonegotiation.
Even under "normal" circumstances where autonegotiation completes,
it takes an abnorma
Public bug reported:
SRU Justification:
[Impact]
During the QA reboot test, the BF3 Vitesse PHY gets stuck in a bad
state, resulting in no ip provisioning. The only way to recover is to
toggle the PHY hard reset pin via GPIO17 (or powercycle cycle since it
achieves just that). We might have foun
** Description changed:
SRU Justification:
[Impact]
- During the QA reboot test, the BF3 Vitesse PHY gets stuck in a bad
- state, resulting in no ip provisioning. The only way to recover is to
- toggle the PHY hard reset pin via GPIO17 (or powercycle cycle since it
- achieves just that).
This SW WA didnt work so the HW team will have to review it.
** Changed in: linux-bluefield (Ubuntu)
Status: New => Invalid
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
SRU Justification:
[Impact]
This is reproducible on systems which already have heavy background
traffic. On top of that, the user issues one of the 2 docker pulls below:
docker pull nvcr.io/ea-doca-hbn/hbn/hbn:latest
OR
docker pull gitlab-master.nvidia.com:5005/dl/dgx/triton
Public bug reported:
SRU Justification:
[Impact]
Although the gpio-mlxbf2.c driver has already been upstreamed, it did not
include gpio interrupt handling. We recently upstreamed the latter and as
requested by maintainers, moved all gpio interrupt code from the mlxbf-gige
driver to the gpio-m
Public bug reported:
SRU Justification:
[Impact]
At the moment, the mlxbf-gige is broken in the ubuntu image because it is out
of date. This change in the gpio-mlxbf2.c driver broke it:
https://code.launchpad.net/~asmaam/ubuntu/+source/linux-bluefield/+git/version-seeds/+merge/417771
https://b
Public bug reported:
SRU Justification:
[Impact]
OCP3.0 project was discontinued and canceled so all stale code related to
that was removed.
The HID MLNXBF29 is used now for triggering a graceful shutdown for the Bobcat
board. On the bobcat board, the main board cpld issues the shutdown request
Public bug reported:
SRU Justification:
[Impact]
Bobcat is a new board which doesn't have an external PHY connected to
the OOB. There are no MDIO busses involved and no PHY involved. The OOB
is directly connected to the switch (MAC to MAC). SO we need to use the
linux fixed phy to be able to emu
** Summary changed:
- mlxbf-gige: support bobcat
+ mlxbf-gige: support fixed phy for Bobcat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054845
Title:
mlxbf-gige: support fixed phy for Bobcat
To
Reopening this bug since we found a software workaround for it.
** Changed in: linux-bluefield (Ubuntu)
Status: Invalid => In Progress
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: Invalid => In Progress
** Description changed:
SRU Justification:
[Impact]
Durin
Public bug reported:
SRU Justification:
[Impact]
The ipmb driver failing to load is just the result of i2c-mlxbf
not receiving interrupts.
In fact, any driver dependent on the i2c-mlxbf driver will not work.
How to reproduce this issue?
- modprobe gpio-mlxbf3
-
Public bug reported:
SRU Justification:
[Impact]
Once the BF3 MDIO clock is enabled by software it is expected and intended
for it to keep toggling. BF3 has a hardware GPIO bug where constant
toggling at "high frequencies" will lead to GPIO degradation.
[Fix]
* A workaround is to lower down th
Public bug reported:
SRU Justification:
[Impact]
Fix return value check for devm_platform_ioremap_resource() in
mlxbf3_pinctrl_probe().
[Fix]
* Fix return value check for devm_platform_ioremap_resource() in
mlxbf3_pinctrl_probe().
[Test Case]
* Check that pinctrl driver is loaded without err
** Description changed:
+ SRU Justification:
+
[Impact]
Fix return value check for devm_platform_ioremap_resource() in
mlxbf3_pinctrl_probe().
[Fix]
* Fix return value check for devm_platform_ioremap_resource() in
mlxbf3_pinctrl_probe().
[Test Case]
* Check that pin
Public bug reported:
SRU Justification:
[Impact]
Cherry pick pwr-mlxbf patches from linux-next.
[Fix]
* Revert existing pwr-mlxbf driver changes
* Cherry-pick all the following commits from linux-next:
a4c0094fcf7628f31bf82a7b25e7f51ee5a22324
a5a3d94fc4edecb894bc79810aea511ff9261c09
a578
Public bug reported:
[Fix]
* Support the ipmb_host.c driver on the Noble branch.
[Test Case]
* check that ipmb_host.c driver is loaded at boot time with no errors
(lsmod/modinfo)
* check that the /dev/ipmi0 device file is created successfully
* Please note that this driver (like other host IPM
26 matches
Mail list logo
