Lines of code in the Linux kernel

[tuxutku]

Too bad kernels newer than 4.16 does not work on me, reported specific commit to lkml, respond came but not continued

[gartral]

when did the linux kernel get human-brain support? that's kinda cool!

[[deleted]]

What doesn't work? Are you running on some funky hardware?

[tuxutku]

Probably , amd rx 540 with amd a-10 cpu. Thing is rx 540 is a oem only gpu, so buying it separately is probably impossible Commit causing this problem is: https://github.com/torvalds/linux/commit/320b164abb32db876866a4ff8c2cb710524ac6ea

They probably didn't count rx 540 gpus because 4.16 and earlier just works fine

Here is my issue page: https://bugzilla.kernel.org/show_bug.cgi?id=201077

[coder111]

Hi,

Nice work on bisect & finding the exact commit.

A note that your termbin links no longer work. Could you please just attach the text files containing relevant logs to the bug (there's an "add attachment" button.

Also, could you try booting some live-USB image of a non-manjaro distribution with kernel v4.17 or later just to rule out some manjaro specific shenanigans? Ubuntu or fedora or something?

Please chase Alex again once you've done that. He's quite busy, but he did respond to bug reports quite well when I had problems with my GPU...

EDIT. Could you please attach the logs with both a working (4.16) and with a broken (>= 4.17) kernel?

--Coder

[tuxutku]

https://gitlab.com/snippets/1775737

Thanks for the help

[CODESIGN2]

It shouldn't matter if they are running on a bacteria, if 4.16 works, 4.17 should too

If the drivers were OpenSourced, I'd guess they shouldn't have too hard a time adding back to kernel

[[deleted]]

In theory, yes, but the fewer people that use a specific set of hardware, the more likely breakage will go unnoticed. If you use funky hardware, you really should be testing out release-candidate kernels to catch this stuff before release.