------- Comment From hbath...@in.ibm.com 2017-07-31 14:14 EDT------- (In reply to comment #30) > I don't see any fundamental issue with providing a NET_WAIT_TIME variable > (probably should be namespaced to KDUMP_) in the kdump config file, but:
Right, KDUMP_NET_WAIT_TIME is better.. > > 1) this seems like a hack to work around slow hardware, right? > Yeah. On NICs that are slow to initialize. With my limited expertise in network related problems, I thought this can be a nice config option to have. A right fix might be somewhere in network related stuff.. > 2) it can't be automatically deduced, afaict. Or do you want to have 30s > delays (potentially) on all POWER machines? > No. I think this has more to do with the NIC than arch. What I have in mind is a 0s delay time by default but something that can be set to a non-zero value for NICs like this using KDUMP_NET_WAIT_TIME= > 3) I'm not 100% familiar with the 'upstream' of kdump-tools -- is this > something that we'd need to carry forever in the Debian/Ubuntu packaging? Probably, unless there is a fix in NIC (hardware/firmware) and/or network related code that makes this config option redundant.. Thanks Hari -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681909 Title: Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
