-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rogue Wave Software Centos 7.3 image kernel breaking LIS integration #343
Comments
LIS 4.2.0 fixes this issue. The kABI change came in at the end of the 4.2.0 development cycle.
Thanks, --jrp
From: Johan Burati [mailto:notifications@github.com]
Sent: Thursday, May 18, 2017 00:17
To: LIS/lis-next <lis-next@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [LIS/lis-next] Rogue Wave Software Centos 7.3 image kernel breaking LIS integration (#343)
I tried to install LIS 4.1.3-2 on a VM build from the Centos 7.3 from Rogue Wave Software,
using kernel 3.10.0-514.16.1.el7.x86_64, and after reboot the VM hangs and fails to boot.
All LIS modules report unknown symbols at boot time, including storvsc, which fails to load. This leads to dracut-initqueue timeout messages.
A few sample boot messages for reference:
[ 3.294211] hv_storvsc: disagrees about version of symbol vmbus_driver_unregister
[ 3.294212] hv_storvsc: Unknown symbol vmbus_driver_unregister (err -22)
[ 3.294250] hv_storvsc: disagrees about version of symbol vmbus_sendpacket
[ 3.294251] hv_storvsc: Unknown symbol vmbus_sendpacket (err -22)
[ 3.294259] hv_storvsc: disagrees about version of symbol vmbus_close
[ 3.294260] hv_storvsc: Unknown symbol vmbus_close (err -22)
[ 3.294263] hv_storvsc: disagrees about version of symbol vmbus_recvpacket
[ 3.294263] hv_storvsc: Unknown symbol vmbus_recvpacket (err -22)
[ 3.294276] hv_storvsc: disagrees about version of symbol vmbus_open
[ 3.294277] hv_storvsc: Unknown symbol vmbus_open (err -22)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FLIS%2Flis-next%2Fissues%2F343&data=02%7C01%7Cjopoulso%40microsoft.com%7Cbd5d017640844fd07e6708d49dbde5a3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636306886306709141&sdata=M0zYnP8xBxDTL6h8w%2FzkororDRLixAQRuH00Sa7NYpM%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADpbJXzooLmNI6BNiCtyExDqHVCKAzR2ks5r6_BzgaJpZM4Ne0v1&data=02%7C01%7Cjopoulso%40microsoft.com%7Cbd5d017640844fd07e6708d49dbde5a3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636306886306709141&sdata=C4%2Bz7mbWUH7OO%2BWCae6%2FyZ7GvDpu0NIBxLxULkq9jnU%3D&reserved=0>.
|
Thank you Joshua ! Just tested it, I confirm it is working.
|
The next release, 4.2.3, adds compatibility for the 7.4 kernels. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried to install LIS 4.1.3-2 on a VM build from the Centos 7.3 from Rogue Wave Software,
using kernel 3.10.0-514.16.1.el7.x86_64, and after reboot the VM hangs and fails to boot.
All LIS modules report unknown symbols at boot time, including storvsc, which fails to load. This leads to dracut-initqueue timeout messages.
A few sample boot messages for reference:
[ 3.294211] hv_storvsc: disagrees about version of symbol vmbus_driver_unregister
[ 3.294212] hv_storvsc: Unknown symbol vmbus_driver_unregister (err -22)
[ 3.294250] hv_storvsc: disagrees about version of symbol vmbus_sendpacket
[ 3.294251] hv_storvsc: Unknown symbol vmbus_sendpacket (err -22)
[ 3.294259] hv_storvsc: disagrees about version of symbol vmbus_close
[ 3.294260] hv_storvsc: Unknown symbol vmbus_close (err -22)
[ 3.294263] hv_storvsc: disagrees about version of symbol vmbus_recvpacket
[ 3.294263] hv_storvsc: Unknown symbol vmbus_recvpacket (err -22)
[ 3.294276] hv_storvsc: disagrees about version of symbol vmbus_open
[ 3.294277] hv_storvsc: Unknown symbol vmbus_open (err -22)
The text was updated successfully, but these errors were encountered: