Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
How to submit ACPI bugs to kernel.org?[SOLVED]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
muhlemmer
n00b
n00b


Joined: 26 Nov 2010
Posts: 24
Location: Middelburg, Netherlands

PostPosted: Tue Oct 10, 2017 12:02 pm    Post subject: How to submit ACPI bugs to kernel.org?[SOLVED] Reply with quote

Can someone help me out? I can't really find a clear resource on filing ACPI bug reports and how to do it. What etiquete, what debug info from the kernel has to be included etc? Maybe to recompile the kernel with some debug options enabled? I tried to ask on the kernel IRC channel a couple of times in the past, but no real guidance either. Basically, I just want to learn how to write a good ACPI bug report.

I have a laptop where battery info is missing and stand-by is not working. This laptop used to be a problem child since the beginning, but except for this items everything works now.
_________________
Ignorance is a bliss...


Last edited by muhlemmer on Fri Oct 20, 2017 12:38 pm; edited 1 time in total
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7071

PostPosted: Tue Oct 10, 2017 3:11 pm    Post subject: Reply with quote

you have to follow the rules from the bugzilla you are using, for kernel.org bugzilla, i don't know them except this one: only report against a vanilla kernel, if you are using a distro kernel (gentoo sources...), it's not for them.
for gentoo bugzilla: the minimum is to provide emerge --info, it would be good to provide info related to your problem, but if you don't know howto get these infos, the dev handling the bug report will ask you what he wants.

and in both case, submit one bug per problem, sure both might be ACPI, but let them work on one problem at a time, if you have battery and buttons problem, submit one bug for the battery and one for the buttons.
Back to top
View user's profile Send private message
muhlemmer
n00b
n00b


Joined: 26 Nov 2010
Posts: 24
Location: Middelburg, Netherlands

PostPosted: Fri Oct 20, 2017 12:34 pm    Post subject: Reply with quote

In the absence of a good guide, I started to read kernel.org bugzilla guide, bug reports reported fixed and bug reports reported invalid. Also based on the feedback I got on my own bug report, there are some tips to share here.

Config options
Double check your config and enable applicable debug options. Maybe it already gives you some clues. Also, you can try to use genkernel or other linux distributions. If the problem disappears with other kernel config, you know where to look and don't file a bug.

Update BIOS and EC firmware
First thing you are going to hear, did you update the firmware to the latest revision? Safe yourself the embarrassment and update them if you can. Mention in the bug report that the firmware is up-to-date.

Applicable kernel versions
So, you have an (ACPI) issue and you are running a gentoo kernel? Emerge a vanilla kernel with the same version, and 'make oldconfig' with the same config and see if the problem is there. If yes, upgrade to git-sources and try again. Maybe your issue was already fixed.

If not fixed in the latest git version, check if the issue is / was a regression. Maybe you already know that something just stopped working in a newer version. Or maybe you have a new PC and you are not sure. Anyway, try to compile earlier versions to check and pinpoint what was the latest kernel it worked (if it did).

Boot options
Poke around with the kernel boot options regarding ACPI, APIC, PCI etc. Maybe some behaviors change or even get better. This info might help the kernel dev to easier troubleshoot the problem. Look into 'acpi_os=' flag for instance.

dmesg
When you are posting your bug report, include the output of 'dmesg > dmesg.txt'. This should contain also the additional debug output you enabled in the kernel config. Also, do some investigations to the log itself and post the highlights of your findings in the bug report body. Try looking for 'dmesg | grep ACPI' or 'grep "ACPI Error". Maybe there are some PCI or interupt errors? All info helps.

acpidump
Use 'sys-power/iasl'. 'sys-power/pmtools' is horribly outdated. Attach the output of 'acpidump -c off > acpidump.txt'

Busybox
It might happen through troubleshooting, that you are not able to mount root with certain kernel versions of config (this happened to me). Of course, you kept a "healthy" kernel around to can reboot back into your system. But perhaps you want to investigate the dmesg log and prevent the kernel panic. Use the "initramfs" wiki article to setup a busybox initramfs. Instead, let not the script to setup and mount root. Just execute '/bin/busybox sh'. In the shell you will have access to commands like 'dmesg', 'grep' etc.

In any case I can recommend to have such a initramfs laying around in /boot in case you need it. In case shit hits the fan, just append the 'initrd=' flag in your bootloader.

Write the bug report
File it against the highest kernel version you tested with. In this case a RC version from GIT. This will give you the highest probability for support. Include all the above info. You cannot attach all you log files at once, so you will do this after creating the bug report. In the report you will mention your defect(s), highlights from dmesg and all the things you already did and tried. This will safe a lot of message round trips, which can take days if the dev is in opposite side of the world.

Patience and responsive
More and more devs are hired by companies to do kernel development. This means they will only work on your issues during their business hours and probably not in the weekends. They can be in complete opposite side of the world. When they request you for info, try to provide it as soon as possible. You will easily loose a day extra if you are replying when the dev is just going home.

And have some respect by letting them know when you found the problem or solved it with their patch. There are so many bug reports which just get closed, because the original bug poster disappeared. Yes, maybe you are a rookie and it was your own mistake. But let them know please. There are other rookies out there that still want to have the patience and the support from the devs. Don't spoil it!

Let your emotions at home. You didn't buy linux from them and they are not your therapist. This is technology and only facts matter.

Have fun!
_________________
Ignorance is a bliss...
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum