Call trace in dmesg (need to specify later what this is)

[flip101]

Hello, I get a few call traces in my dmesg log which seems to indicate some problem. I'm trying to get my hardware better compatible with Ubuntu 18.10 therefor i report this bug. Actually i have no idea what this is about so i'll be happy to provide more information on request.

There are actually a few call traces so i will upload the entire output from dmesg together with information on my system. Possibly the issues should be separated into several bug reports.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: philippe 4375 F.... pulseaudio
 /dev/snd/controlC0: philippe 4375 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-05-14 (198 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=5ef6da7b-eb86-45bd-ad30-df7141164c79 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-11-generic N/A
 linux-backports-modules-4.18.0-11-generic N/A
 linux-firmware 1.175.1
Tags: cosmic
Uname: Linux 4.18.0-11-generic x86_64
UpgradeStatus: Upgraded to cosmic on 2018-11-16 (11 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/23/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.70
dmi.board.name: AB350 Gaming-ITX/ac
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd07/23/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1805433

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[flip101 (flip101)]

apport information

[flip101 (flip101)]

apport information

[flip101 (flip101)]

apport information

[flip101 (flip101)]

apport information

[flip101 (flip101)]

apport information

[flip101 (flip101)]

apport information

[flip101 (flip101)]

apport information

[flip101 (flip101)]

apport information

[flip101 (flip101)]

apport information

[flip101 (flip101)]

apport information

[flip101 (flip101)]

apport information

[flip101 (flip101)]

apport information

[flip101 (flip101)]

apport information

[flip101 (flip101)]

apport information

[flip101 (flip101)]

apport information

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc6

[flip101 (flip101)]

Hi jsalisbury i can not tell you about the situation before because it was the first time i checked dmesg. I did a dist upgrade from 18.04 to 18.10 though. But like i said i don't know if this was already happening in 18.04

[flip101 (flip101)]

The dmesg on 4.20 rc6 still contains a lot of call traces. I don't know if they are the same ones or of the same origin though. When comparing files i initially thought the 4.20rc6 has less call traces, but actually at the end of the diff there are more. So i would say both 4.18 and 4.20rc6 roughly have the same amount of call traces.

[Kai-Heng Feng (kaihengfeng)]

If you know how to build a kernel, please try this branch out:
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next

[flip101 (flip101)]

I can try to build a kernel. How can i download all the patches and apply them at the same time?

[flip101 (flip101)]

Well i was able to get the patches with

git clone https://git.kernel.org/ linux-13122018
cd linux-13122018
git remote add freedesktop git://people.freedesktop.org/~agd5f/linux
git fetch freedesktop amd-staging-drm-next
git checkout freedesktop/amd-staging-drm-next

Now i'm trying to follow this guide https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel#Modifying_the_configuration but i'm not sure if configuration changes are needed

[Kai-Heng Feng (kaihengfeng)]

$ yes '' | make localmodconfig
$ make -j`nproc` deb-pkg

Then the kernel should be built as Debian Package.

[flip101 (flip101)]

Ok i have the new kernel loaded now. The new dmesg output still has 9 call traces in it.