> Can you confirm that the Wily kernel (4.2.0-36.41)
> currently in -proposed fixes this bug? Thanks!
All looks good when installing the three packages from wily-proposed:
linux-headers-4.2.0-36-generic linux-image-4.2.0-36-generic
linux-image-extra-4.2.0-36-generic. The kernel did not deference the
NULL pointer, and the particular OpenSSL self test passed:
make test
../test/recipes/25-test_x509.t ............. ok
../test/recipes/30-test_afalg.t ............ ok
../test/recipes/30-test_engine.t ........... ok
A small nit, which is probably due to my misunderstanding of the way
dependencies are handled when using Selective Upgrades
(http://wiki.ubuntu.com/Testing/EnableProposed#Selective_upgrading_from_-proposed).
When I performed only 'apt-get install
linux-image-4.2.0-36-generic/wily-proposed', the machine did not boot,
and it was stuck at the initramfs prompt. I needed to install
linux-image-extra-4.2.0-36-generic manually.
> Can you confirm that the Wily kernel (4.2.0-36.41)
> currently in -proposed fixes this bug? Thanks!
All looks good when installing the three packages from wily-proposed: 4.2.0-36- generic linux-image- 4.2.0-36- generic extra-4. 2.0-36- generic. The kernel did not deference the
linux-headers-
linux-image-
NULL pointer, and the particular OpenSSL self test passed:
make test test/recipes/ 25-test_ x509.t ............. ok test/recipes/ 30-test_ afalg.t ............ ok test/recipes/ 30-test_ engine. t ........... ok
../
../
../
And the only thing I see under dmesg:
$ dmesg
...
[ 913.294639] NET: Registered protocol family 38
$
A small nit, which is probably due to my misunderstanding of the way wiki.ubuntu. com/Testing/ EnableProposed# Selective_ upgrading_ from_-proposed). 4.2.0-36- generic/ wily-proposed' , the machine did not boot, extra-4. 2.0-36- generic manually.
dependencies are handled when using Selective Upgrades
(http://
When I performed only 'apt-get install
linux-image-
and it was stuck at the initramfs prompt. I needed to install
linux-image-