proxmox5 kernel config

[efeu]

You mentioned here that PINCTRL_AMD will be disabled, but it's not. Neither in 4.10.1-2-pve nor in 4.10.5-1-pve, so I alwas have to compile the kernel by my own, but this kinda sucks. Could you please change this parameter in your kernel config?

 

[fabian]

You mentioned here that PINCTRL_AMD will be disabled, but it's not. Neither in 4.10.1-2-pve nor in 4.10.5-1-pve, so I alwas have to compile the kernel by my own, but this kinda sucks. Could you please change this parameter in your kernel config?

I am afraid disabling that might have unintended side effects on other main boards, depending on how stuff is wired up. I'd rather wait for that specific broken mainboard to be blacklisted or a BIOS update that fixes the issue.

Maybe building the kernel with pinctrl-amd as module instead of compiled in would be an option?

 

[liebero3]

Hi efeu,

could you please help me compiling the kernel without pinctrl-amd, or do you have it uploaded anywhere? I'm stuck with the same problem (owning a gigabyte gaming5).

Cheers,
Till

@fabian: I read, that compiling it as module would be sufficiant to solve the problem. I would appreciate that

 

[fabian]

Hi efeu,

could you please help me compiling the kernel without pinctrl-amd, or do you have it uploaded anywhere? I'm stuck with the same problem (owning a gigabyte gaming5).

Cheers,
Till

@fabian: I read, that compiling it as module would be sufficiant to solve the problem. I would appreciate that

could you file a bug report for easier tracking? thanks.

 

[liebero3]

Hi Fabian, a bug report for what?

Me failing in compiling the proxmox kernel? That one doesn't exist, I'm novice and just succeeded in compiling the ubuntu kernel and the debian kernel, did not even start to compile the proxmox kernel because of lack of knowledge

Or do you mean a bugreport for my issue with pinctrl-amd? That happens, if I try to install proxmox 5 and it just throws an infinit amount of vector 07 faults. I think it's the exact same issue efeu has, since disabling pinctrl-amd is the suggested workaround for the gigabyte boards.

Cheers,
Till

EDIT: typos...

 

[fabian]

a bug report/enhancement request for moving that module from compiled in to modular

 

[liebero3]

Thanks for your explanation. I think/hope, I accomplished the task

Cheers,
Till

 

[efeu]

As of what I read here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
the bug was fixed in Linux kernel version 4.10.0-25 (and before we could just insert it as a module). Are these changes included in latest proxmox5 kernels?

 

[fabian]

the patches from 1671360 has been included in pve-kernel for some time.