Created attachment 1486940 [details] Photo of kernel panic Description of problem: Kernel panic on Shuttle XS35GTv2 (see attached photo). Version-Release number of selected component (if applicable): kernel-4.18.9-200.fc28.x86_64 How reproducible: Not quite sure. Found this system panicked this morning Steps to Reproduce: 1. Run this kernel on it? Actual results: Kernel panic. Expected results: No panic. Additional info: See attached photo.
Given nothing else was happening at the time, I think this may have been one off corruption. We can keep this bug open to see if it happens again.
Created attachment 1517037 [details] Another panic, kernel 4.19.10
So, this is now an F29 bug too. Just FYI. BTW, I have no idea what the machine was doing at the time, to be honest. The only thing it really does around here is DHCP/DNS.
If it matters, this is an atom CPU machine, with all the recent meltdown and spectre mitigation off (i.e. there is no speculation, if I understand things at correctly).j
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora 29 has now been rebased to 4.20.5-200.fc29. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.