-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPQ8074: Zyxel NBG7815: "kernel: backport nvmem v6.6 fixes and v6.7 changes" patch causing random MAC on each boot #13831
Comments
I've tried to start narrowing things down and I've just deleted 816-v6.7-0004-Revert-nvmem-add-new-config-option.patch. It is fixing the issue. But I don't know if and what sideeffects this could introduce. |
Nice work narrowing this down. Rafal will fix, but if you wanted to keep digging in the meantime, could you check if there are any message from the priv->mtd = of_get_mtd_device_by_node(np);
if (IS_ERR(priv->mtd)) {
dev_err_probe(dev, PTR_ERR(priv->mtd), "Failed to get %pOF MTD\n", np);
return PTR_ERR(priv->mtd);
} given we are modifying the openwrt/target/linux/generic/backport-6.1/816-v6.7-0004-Revert-nvmem-add-new-config-option.patch Lines 50 to 58 in b595670
If you cannot find anything in dmesg, would you be able to check the DT node --- drivers/nvmem/u-boot-env.c.orig 2023-10-31 06:44:36.186727737 +1000
+++ drivers/nvmem/u-boot-env.c 2023-10-31 06:47:18.392136608 +1000
@@ -211,6 +211,7 @@
struct u_boot_env *priv;
int err;
+ dev_warn(dev, "DT node: %pOF\n", np);
priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL);
if (!priv)
return -ENOMEM; Cheers |
I'll try to debug that tomorrow. I got some idea (posted comment actually) about |
I've checked. There is no such message. I've attached: dmesg (failed state), z-loader, u-boot and pre-boot log: dmesg.txt
I'll try it. But probably not until evening. EDIT: with full patch set
with deleted 816-v6.7-0004-Revert-nvmem-add-new-config-option.patch
So no change (beside the invalid MAC lines). |
Can you please compile and run firmware with my debugging patch "kernel: add nvmem u-boot-env debugging patch for 6.1"? I pushed branch with it to the https://git.openwrt.org/?p=openwrt/staging/rmilecki.git;a=shortlog;h=refs/heads/nvmem-u-boot-env-debugging I can't figure out this issue. NVMEM driver for U-Boot env works on my bcm4908 device. I can't understand how this change can break anything. |
Sure, I'm currently building and I will give feedback as soon as I can. It could be that it will be delayed after lunch. |
|
I cannot see anything suspicious. :/ EDIT: The u_boot_env lines are exactly the same if I remove the mentioned 816-patch on this debug build. But without the failed MAC lines (as before). |
Please give the latest |
Yep it is working again. Thank you for this fast fix. Kind regards. :) |
Fixes: b595670 ("kernel: backport nvmem v6.6 fixes and v6.7 changes") Fixes: openwrt#13831 Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Fixes: b595670 ("kernel: backport nvmem v6.6 fixes and v6.7 changes") Fixes: openwrt#13831 Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Fixes: b595670 ("kernel: backport nvmem v6.6 fixes and v6.7 changes") Fixes: openwrt#13831 Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Fixes: b595670 ("kernel: backport nvmem v6.6 fixes and v6.7 changes") Fixes: openwrt#13831 Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Fixes: 20736013e910 ("kernel: backport nvmem v6.6 fixes and v6.7 changes") Fixes: openwrt/openwrt#13831 Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit c997634c017294cb38cf6f9a0112860c7e736a53)
Describe the bug
After applying this commit:
b595670
kernel: backport nvmem v6.6 fixes and v6.7 changes
the MAC addresses are changing on every reboot on this device.
This kernel message is not present on earlier versions. I've tracked it down to this commit. If you need the whole dmesg just let me know.
OpenWrt version
r24256-1d6f9bdfc0
OpenWrt target/subtarget
qualcommax/ipq807x
Device
Zyxel NBG7815
Image kind
Self-built image
Steps to reproduce
No response
Actual behaviour
No response
Expected behaviour
MAC's should be stable on each boot.
Additional info
No response
Diffconfig
Terms
The text was updated successfully, but these errors were encountered: