1 |
On Mon, 5 Oct 2015 17:56:53 -0700 |
2 |
walt <w41ter@×××××.com> wrote: |
3 |
|
4 |
> On Sun, 4 Oct 2015 20:59:01 -0400 |
5 |
> Alec Ten Harmsel <alec@××××××××××××××.com> wrote: |
6 |
> |
7 |
> > On Sun, Oct 04, 2015 at 05:47:37PM -0700, walt wrote: |
8 |
|
9 |
> > > I updated the kernel in my gentoo virtualbox guest machine to |
10 |
> > > 4.1.8 and got a kernel panic after rebooting the guest. |
11 |
> > > |
12 |
> > > Anyway, I rebooted the guest machine with vmlinuz.old (3.18.21) |
13 |
> > > and then updated the guest to vanilla-sources-4.2.3 with no |
14 |
> > > problems. |
15 |
> > > |
16 |
> > > (I omit several hours of confused |
17 |
> > > reconfiguring/recompiling/rebooting because you really don't want |
18 |
> > > to hear about them.) |
19 |
> > > |
20 |
> > > So, what is different or strange about kernel 4.1.8? Anyone have |
21 |
> > > any problems with it on real hardware, or in other virtual |
22 |
> > > environments like qemu, vmware, xen, etc? |
23 |
|
24 |
|
25 |
> > I am running 4.1.8 on all my machines without any problems. Without |
26 |
> > seeing the stack trace and/or other output from the kernel panic, I |
27 |
> > would have no idea how to figure out what the problem was. I am also |
28 |
> > not a kernel wizard, so I probably wouldn't be much help anyways. |
29 |
|
30 |
> Okay, thanks. Just by chance, Fedora (which I also run in vbox) |
31 |
> updated to kernel 4.1.8 today and I had no trouble with it, so I'll |
32 |
> use their kernel config file in my gentoo guest machine to compile |
33 |
> 4.1.8 and see if that fixes the panic. Experiments are fun :) |
34 |
|
35 |
Using the Fedora kernel config file to build vanilla-sources-4.1.8 on |
36 |
gentoo fixes the kernel panic. Apparently the upstream kernel devs |
37 |
changed the way 'make silentoldconfig' works so that it removes some |
38 |
important config options that virtualbox needs. Whatever they changed |
39 |
in the 4.2.x kernels fixed the problem. |