[Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!
I didn't think Trusty would even run baremetal on ppc64el? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715519 Title: bnx2x_attn_int_deasserted3:4323 MC assert! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!
Full test passes. No crash with proposed hwe-16.04 kernel and tso/gso enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715519 Title: bnx2x_attn_int_deasserted3:4323 MC assert! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!
After conferring with the IBM Novalink dev team, we found a way to exploit some undocumented preliminary artful support in the DKMS, to successfully install the hwe-16.04 kernel (4.13.0-38) from xenial- proposed. It boots and passes traffic. I hope to report back later today or possibly tomorrow with full test results. Please let me know if this is sufficient testing for applying the verification-done-artful tag. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715519 Title: bnx2x_attn_int_deasserted3:4323 MC assert! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!
These Linux LPARs are running Novalink, in a mode that allows them to serve in place of the traditional PowerVM AIX VIO server. So they're providing virtual I/O for other LPARs (this is how we ended up sending 64k packets into the bnx2x nics via open vswitch). The DKMS modules enable that function. It also serves to restrict what we can do with the OS in terms of trying other versions; the Novalink software is supported only on Xenial. Trying to rebuild a machine on artful without Novalink means none of the other LPARs on that machine will run, which will be very disruptive for us, even on a test machine. We could probably find a way to test artful on a VM, but then that would be using a virtual ethernet adapter and we wouldn't be testing the bnx2x code. I don't know if that would be valuable to you? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715519 Title: bnx2x_attn_int_deasserted3:4323 MC assert! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!
We're not set up to test the artful kernel, but I can envision a near- to-mid-term future where we will need this patch to be present in the artful kernel. What's the best way for me to help make sure that future obtains? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715519 Title: bnx2x_attn_int_deasserted3:4323 MC assert! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715519 Title: bnx2x_attn_int_deasserted3:4323 MC assert! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!
Our validation tests pass with tso/gso enabled and 4.4.0-117 (no crash). We'll do a couple more tests but it's looking good so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715519 Title: bnx2x_attn_int_deasserted3:4323 MC assert! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!
I was able to install the ppc64el 4.4.0-117 kernel from xenial-proposed. It boots and passes at least enough traffic to make an interactive ssh session function. I'm having some DKMS issues, however, which are preventing me from validating the patch prevents crash as expected (one of the modules we need has BUILD_EXCLUSIVE for 4.8 and 4.10 only). I am working with the IBM development team who publishes these modules to get that resolved ASAP (they were surprised by this, so we are waiting for answers from individual engineers, probably Monday). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715519 Title: bnx2x_attn_int_deasserted3:4323 MC assert! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!
Ok, that works. I should be able to provide basic validation much more easily. We are having trouble reproducing the crash with the unpatched kernel, as we've put many remediating workarounds in place and it's been an adventure to remember where they all are and how exactly they all interacted (and also there are some other bugs currently being worked on in our test environment that affect our ability to reproduce as well). We know it will crash though, and as soon as we get the test setup in place to reproduce the crash I'm confident we can repeat it every time and get a good validation that the patch is solving our problem as well. If we still can't reproduce the crash by COB Monday, I'll switch gears to provide just a basic boot/function validation and will make sure I get that to you by Tuesday at the latest. We only have the environment to test xenial ppc64el. We have xenial and trusty x86_64, but not with bnx2x. We don't have artful anywhere that I can test with. Based on that, I was only planning to provide a report for xenial ppc64el. Does the smoke testing make sense to perform without bnx2x hardware present? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715519 Title: bnx2x_attn_int_deasserted3:4323 MC assert! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!
I am the end user who originally reported this problem. We have been working with Canonical through IBM Support to get this problem resolved -- When I last spoke with IBM about this a few weeks ago, I got the impression we'd have a little extra time to perform verification (e.g. the test period would be between 18 and 31 March) and planned for our test resources accordingly. I now see that we'd need to perform verification by the 23rd, or possibly 26th? I will do what I can do increase urgency but even having a couple extra days would go a long way to help us get the verification done. Please let me know ASAP if this is or is not possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715519 Title: bnx2x_attn_int_deasserted3:4323 MC assert! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534179] Re: Feature Request: Include bash syslog package
This is what I do. I've successfully applied it to the bash source package from precise, trusty, and wily. It will create an extra package called 'logbash'. ** Patch added: "logbash-pkg.patch" https://bugs.launchpad.net/ubuntu/+source/bash/+bug/534179/+attachment/4566677/+files/logbash-pkg.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/534179 Title: Feature Request: Include bash syslog package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/534179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
