Comment 36 for bug 1762844

------- Comment From <email address hidden> 2018-04-21 09:21 EDT-------
Should we go back to the stock Ubuntu kernel in an attempt to identify if bug 167104 is a result of the custom kernel or the newest PNOR?

------- Comment From <email address hidden> 2018-04-21 13:17 EDT-------
(In reply to comment #106)
> Should we go back to the stock Ubuntu kernel in an attempt to identify if
> bug 167104 is a result of the custom kernel or the newest PNOR?

I am looking at all these plethora of bugs on the host and guest, seems like a constantly shifting problem. I don't think that this particular instance was because of the custom kernel (reverting some Qlogic patches). In my opinion memory corruption seems to be gaining currency.

Are systems without the Qlogic adapters seeing any of the problems reported here?

How do we debug with constantly moving pieces? Can we get a stable base to start with? By that I mean we go back to a kernel and pnor that worked in the past. Then using the same kernel advance the pnor and validate how it works. We might need to limit the testing to "cater" to the various bugs.

Once we have isolated the pnor, then we repeat with the kernels. Not sure how long these activities will take, but we might need to consider running a parallel exercise.

------- Comment From <email address hidden> 2018-04-21 14:17 EDT-------
boslcp3 seems to have gone off the rails again ... the console is spitting out a
lot of messages like:

[ ***] (2 of 2) A start job is running for?urnal Service

and it is not pingable....