I've now tested the patch on Ubuntu and it fixes the issue there, too.
@Kip, I didn't save the history, but the kernel rebuild was something like the following:
$ apt-get source linux && cd linux-*
$ patch -p1 < bug218916_fix_option_02.patch
# Rebuild the source package so the patch is included in the diff
# (Don't know if this is necessary, it's been ages since I've built a 1.0 package)
$ dpkg-source -b .
# Build kernel
# dpkg-buildpackage
I served the contents of the build result directory via python3 -m http.server, booted the guest, then downloaded and installed the image and module .debs from within.
It was necessary to place a hold on the packages, otherwise they would be "upgraded" to the original kernel when a test was run. See the gotcha mentioned earlier.
Can someone ping the mailing list again? I think this issue might have dropped off the radar.
I've now tested the patch on Ubuntu and it fixes the issue there, too.
@Kip, I didn't save the history, but the kernel rebuild was something like the following:
$ apt-get source linux && cd linux-* 02.patch
$ patch -p1 < bug218916_fix_option_
# Rebuild the source package so the patch is included in the diff
# (Don't know if this is necessary, it's been ages since I've built a 1.0 package)
$ dpkg-source -b .
# Build kernel
# dpkg-buildpackage
I served the contents of the build result directory via python3 -m http.server, booted the guest, then downloaded and installed the image and module .debs from within.
It was necessary to place a hold on the packages, otherwise they would be "upgraded" to the original kernel when a test was run. See the gotcha mentioned earlier.
Can someone ping the mailing list again? I think this issue might have dropped off the radar.