Bug 1076860 - i2c sendbytes NAK bailout, mei module, usb disconnect
Summary: i2c sendbytes NAK bailout, mei module, usb disconnect
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: LiveCD
Version: 20
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-15 20:35 UTC by Need Real Name
Modified: 2015-06-29 19:29 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 19:29:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
two attachments: dmesg file and Xorg log file (71.22 KB, text/x-log)
2014-03-15 20:35 UTC, Need Real Name
no flags Details
dmesg file (110.40 KB, text/plain)
2014-03-15 20:42 UTC, Need Real Name
no flags Details

Description Need Real Name 2014-03-15 20:35:46 UTC
Created attachment 874891 [details]
two attachments: dmesg file and Xorg log file

Description of problem:
Several failures during the live CD boot, possibly related

1. Early in boot 

i2c i2c-17: sendbytes: NAK bailout
and
i2c: i2c-29: sendbytes: NAK bailout

2. Later in boot

mei_me ... Device doesn't have valid ME interface
mei_me ... Intialization failed

3. 6 times after that:

USB disconnect, device number X
where X increments (this appears to be the USB keyboard/mouse)

4. One screen of two seems to go completely blank for a few seconds
roughly every 5 minutes or so (it comes back)

5. Xorg.log has many messages
"reporting 10 11 40 324"

Version-Release number of selected component (if applicable):
Fedora-Live-Desktop-x86_64-20-1

How reproducible:
Always

Steps to Reproduce:
1. Load DVD
2. Check media
3. i2c errors occur before media check stars

Actual results:
The USB disconnect occurs for as long as the system
is up.

Expected results:


Additional info:

Comment 1 Need Real Name 2014-03-15 20:42:07 UTC
Created attachment 874892 [details]
dmesg file

Comment 2 Fedora End Of Life 2015-05-29 11:15:57 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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'
of '20'.

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 20 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.

Comment 3 Fedora End Of Life 2015-06-29 19:29:58 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.