Re: [CentOS] boot issue with latest kernel

2019-03-21 Thread Keith Keller
On 2019-03-20, Young, Gregory wrote: > > Is this a VM running on top of Hyper-V by chance? It is not; as I mentioned in my original post, it's bare metal. --keith -- kkel...@wombat.san-francisco.ca.us ___ CentOS mailing list CentOS@centos.org

Re: [CentOS] boot issue with latest kernel

2019-03-20 Thread Jonathan Billings
On Mar 20, 2019, at 11:42 AM, mark wrote: > Haven't been following this, but if this is a server, rather than a > workstation, there is *zero* reason to have rhgb and quiet on a server. I > take it off ours. If I'm standing there during boot, I always want to see > what's happening. I agree

Re: [CentOS] boot issue with latest kernel

2019-03-20 Thread Johnny Hughes
On 3/20/19 10:42 AM, mark wrote: > Young, Gregory wrote: >> >> Is this a VM running on top of Hyper-V by chance? There seems to be an >> issue with the combination of: - Windows 10 1708 or newer. >> - Hyper-V config version 8.2 - 9.0. >> - Microsoft's Fix for Spectre and Meltdown. >> - Newer Intel

Re: [CentOS] boot issue with latest kernel

2019-03-20 Thread mark
Young, Gregory wrote: > > Is this a VM running on top of Hyper-V by chance? There seems to be an > issue with the combination of: - Windows 10 1708 or newer. > - Hyper-V config version 8.2 - 9.0. > - Microsoft's Fix for Spectre and Meltdown. > - Newer Intel Hardware (Sandy Lake/Kaby Lake, etc.) >

Re: [CentOS] boot issue with latest kernel

2019-03-20 Thread Young, Gregory
bject: [CentOS] boot issue with latest kernel Hi all, Has anyone seen this issue before? This afternoon, I tried updating a bare metal CentOS 6 box, and got some odd error messages on the console during booting kernel 2.6.32-754.11.1. (These aren't exact, I forgot to try to get a photo of the

[CentOS] boot issue with latest kernel

2019-03-13 Thread Keith Keller
Hi all, Has anyone seen this issue before? This afternoon, I tried updating a bare metal CentOS 6 box, and got some odd error messages on the console during booting kernel 2.6.32-754.11.1. (These aren't exact, I forgot to try to get a photo of the console.) sd 0:0:4:0 timed out resetting card