| 1 |
On 02/01/18 14:42, Mick wrote: |
| 2 |
> On Tuesday, 2 January 2018 12:03:24 GMT Alexander Kapshuk wrote: |
| 3 |
>> On Tue, Jan 2, 2018 at 1:54 PM, Kruglov Sergey <kr_serge@×××××××.com> wrote: |
| 4 |
>>> [...] |
| 5 |
>>> Now I have gentoo-sources-4.14.8-r1 installed. |
| 6 |
>>> |
| 7 |
>>> After "emerge --ask --update --deep --with-bdeps=y --newuse @world" |
| 8 |
>>> command emerge installs old kernel in NS (after first update 4.12.12, |
| 9 |
>>> after second update 4.9.49-r1). |
| 10 |
>>> How can I fix it? |
| 11 |
>>> [...] |
| 12 |
>> |
| 13 |
>> There was a discussion about this on the gentoo-dev mailing list. See |
| 14 |
>> the link below for details: |
| 15 |
>> https://archives.gentoo.org/gentoo-dev/message/1d2f3f98c2485fa53ed602bc82850 |
| 16 |
>> 54c |
| 17 |
> |
| 18 |
> [...] |
| 19 |
> That said, I've been running gentoo-sources-4.14.8-r1 here too, on 3 different |
| 20 |
> boxen and thought it was doing fine, thanks. Then I discovered KVM images |
| 21 |
> failed to boot with this error: |
| 22 |
> |
| 23 |
> kernel: kvm [5499]: vcpu0, guest rIP: 0xffffffffbbe67be4 disabled perfctr |
| 24 |
> wrmsr: 0xc2 data 0xffff |
| 25 |
|
| 26 |
The core issue seems to have been finally fixed in 4.14.10-r1. |
Archives