Description of problem: kernel: platform goldfish_pdev_bus: failed to claim resource 0 Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. clean x86_64 network install, non-free and tainted media enabled 2. journalctl -b | grep goldfish
I don't know how many kernel goldfishes there are, but if this goldfish is related to https://android.googlesource.com/platform/external/qemu.git/+/master/docs/GOLDFISH-VIRTUAL-HARDWARE.TXT, then it probably shouldn't claim any resources on your system. @tmb What is this goldfish about?
CC: (none) => marja11Assignee: bugsquad => tmb
(In reply to Marja van Waes from comment #1) > I don't know how many kernel goldfishes there are, but if this goldfish is > related to > https://android.googlesource.com/platform/external/qemu.git/+/master/docs/ > GOLDFISH-VIRTUAL-HARDWARE.TXT, then it probably shouldn't claim any > resources on your system. I spent a few years as a maintenance programmer and experience has taught me to heed any messages other than information and I have found fixing code for those messages resolved other problems. I have no idea when any *_bus error is causing other problems. In my opinion the qemu hooks should be pulled in via dkms if qemu is installed like VirtualBox.
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.
Assignee: tmb => kernel
no longer seeing message in journal
Status: NEW => RESOLVEDResolution: (none) => FIXED