Red Hat Bugzilla – Bug 1462368
inicialization problem kernel
Last modified: 2017-12-12 05:36:50 EST
Created attachment 1288472 [details]
Description of problem:
17:29:32 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
17:29:08 kernel: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
17:28:53 kernel: Bluetooth: hci0 command 0x2010 tx timeout
17:28:51 kernel: Bluetooth: hci0 command 0x200f tx timeout
17:28:49 kernel: Bluetooth: hci0 command 0x2007 tx timeout
17:28:47 kernel: Bluetooth: hci0 command 0x2001 tx timeout
17:28:39 kernel: usb 1-1.1: device descriptor read/64, error -110
17:28:38 avahi-daemon: chroot.c: open() failed: No such file or directory
14:28:19 kernel: ACPI Error: Method parse/execution failed [\_PR.CPU0._PDC] (Node ffff976e66504af0), AE_AML_OPERAND_TYPE (20170119/psparse-543)
14:28:19 kernel: ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20170119/dswexec-461)
14:28:19 kernel: ACPI Error: Needed type [Reference], found [Integer] ffff976e652817e0 (20170119/exresop-103)
Version-Release number of selected component (if applicable):
Start your computer
Steps to Reproduce:
1.Start your computer
2.Open System Log
Ending the bugs
Running 'journalctl -b -p 3 | less' returns the following on Fedora 26 Workstation:
Sep 29 11:13:34 vanoy.fedora kernel: Bluetooth: hci0 hardware error 0x37
Sep 29 11:13:59 vanoy.fedora libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: No such file or directory
Sep 29 11:14:21 vanoy.fedora spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Sep 29 11:20:13 vanoy.fedora spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Running 'uname -r' returns the following:
Steps to Reporduce:
1. Computer boots up
2. Open system log
no error message
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.