View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001286 | channel: elrepo/el8 | kmod-sky2 | public | 2022-11-15 17:49 | 2023-01-14 17:55 |
| Reporter | furicle | Assigned To | pperry | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Summary | 0001286: kmod-sky2 kernel crashes on alma8.7 | ||||
| Description | Trying to use the kmod-sky2 drivers on a Lenovo 0809-5u system running Alma 8.7 fully updated. I get screen fulls of kernel lock up material a few minutes after link up. I would be happy to share if someone can explain how to capture or retrieve the info properly. There's a picture at https://files.mastodon.social/media_attachments/files/109/350/248/120/244/053/small/13047f943228ba9e.jpg | ||||
| Tags | No tags attached. | ||||
|
|
How about dmesg? Do you see any hints there? Or /var/log/messages is another place to look in. |
|
|
Hi, Thank for the report. I confirm I can see there is an issue which we will need to fix. I'll try to get that sorted for you by tomorrow and will report back here once we have an updated package for you to test. |
|
|
Once it starts, the system is unusable. dmesg looks ok I think, as does journalctl [ 1.591806] sky2: loading out-of-tree module taints kernel. [ 1.591981] sky2: module verification failed: signature and/or required key missing - tainting kernel [ 1.594577] sky2: driver version 1.30 [ 1.594767] sky2 0000:02:00.0: Yukon-2 UL 2 chip revision 0 [ 1.596323] sky2 0000:02:00.0 eth0: addr 44:87:fc:fc:9b:4d [ 1.722919] sky2 0000:02:00.0 ens33: renamed from eth0 [ 21.850240] sky2 0000:02:00.0 ens33: enabling interface Nov 15 18:02:29 hostname.example.com kernel: sky2: loading out-of-tree module taints kernel. Nov 15 18:02:29 hostname.example.com kernel: sky2: module verification failed: signature and/or required key missing - tainting kernel Nov 15 18:02:29 hostname.example.com kernel: sky2: driver version 1.30 Nov 15 18:02:29 hostname.example.com kernel: sky2 0000:02:00.0: Yukon-2 UL 2 chip revision 0 Nov 15 18:02:29 hostname.example.com kernel: sky2 0000:02:00.0 eth0: addr 44:87:fc:fc:9b:4d Nov 15 18:02:29 hostname.example.com kernel: sky2 0000:02:00.0 ens33: renamed from eth0 Nov 15 23:02:49 hostname.example.com kernel: sky2 0000:02:00.0 ens33: enabling interface |
|
|
Note I've rebooted a couple times and duplicated this. System is fine, use it a bit with a USB eth card, its fine... link up the card, do ip a and whammo |
|
|
Updated packages for el8.7 have been built and released to the main elrepo repository, and should be available on our mirror sites shortly: kmod-sky2-1.30-7.el8_7.elrepo.x86_64.rpm These updated packages should fix this issue. Please test and we'd appreciate feedback if this package fixes the issues for you. Please note this package is intended for use with el8.7 kernel(s) only and is unlikely to be backward compatible with el8.6 kernels. Many thanks |
|
|
After a quick test, that's looking like it's working correctly. Thank you! Do I understand correctly that there is a manual procedure the people at this repo have to complete after each point release to keep this driver working? So to avoid future issues I'd have to prevent kernel upgrades until ? or ? Do point releases always come with new kernels? (I guess I don't know what actually triggers the version number to increment) |
|
|
Firstly, thank you for the feedback - pleased to hear it's working for you! Red Hat generally release a "point release" update every 6 months. E.g, RHEL 8.5 -> RHEL 8.6 -> RHEL 8.7 Each point release comes with an updated kernel, and as a result of that update, our kmod packages will often stop working. We won't know if a kmod package is affected until after Red Hat release the update and we can test. Even then, we will miss some, as was the case here, as we can only run simplistic tests as we don't have access to physical hardware to perform full testing of every kmod driver package we ship. So history tells us you can assume that the kmod package will break for each point release update - if it doesn't break, then that's a bonus. The further down the road we get in the lifecycle of RHEL, the less chance of breakage happening. Going from X.0 to X.1 has a very high chance of breakage whereas going from X.7 to X.8 the likelihood reduces significantly. Generally, we will try our very best to fix and rebuild all affected packages (and that's sometimes all of them!) within 24 hours of release, so hopefully we should have our packages available about the same time Alma release their updates (I note Alma released both 8.7 and 9.1 recently within about 24h of Red Hat - an amazing turnaround). If you can, try to aim to coordinate updating any kmod packages at the same time you update the distro if possible. Worst case scenario, you update and discover your kmod driver is no longer working, and you reboot back to your previous kernel and all is good. File a bug with us, and we will do our best to turn that around for you very quickly - as we did here in around 12h. Yum/dnf will not normally allow you to update to a newer kmod package if the corresponding newer kernel it is intended for is not available yet. Hope that helps explain. |
|
|
Thanks for the detailed note, and all your work! That does help explain. Unfortunately "worst case" for these devices is messy as they are scattered geographically, without backup connectivity or out of band management. I guess to continue with Alma I will have to somehow hold back kernel updates until testing locally confirms things will work. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-11-15 17:49 | furicle | New Issue | |
| 2022-11-15 17:49 | furicle | Status | new => assigned |
| 2022-11-15 17:49 | furicle | Assigned To | => pperry |
| 2022-11-15 17:56 | toracat | Note Added: 0008739 | |
| 2022-11-15 18:12 | pperry | Note Added: 0008740 | |
| 2022-11-15 18:13 | furicle | Note Added: 0008741 | |
| 2022-11-15 18:14 | furicle | Note Added: 0008742 | |
| 2022-11-16 05:46 | pperry | Note Added: 0008745 | |
| 2022-11-16 05:46 | pperry | Status | assigned => feedback |
| 2022-11-17 09:42 | furicle | Note Added: 0008753 | |
| 2022-11-17 09:42 | furicle | Status | feedback => assigned |
| 2022-11-17 16:34 | pperry | Note Added: 0008755 | |
| 2022-11-18 09:57 | furicle | Note Added: 0008756 | |
| 2023-01-14 17:55 | pperry | Status | assigned => resolved |
| 2023-01-14 17:55 | pperry | Resolution | open => fixed |
