Bug 865844 - kernel BUG when disconnecting AC power
Summary: kernel BUG when disconnecting AC power
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-12 15:44 UTC by Jiri Pospisil
Modified: 2013-07-04 08:13 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-23 17:27:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Photo of the kernel BUG (1.30 MB, image/jpeg)
2012-10-12 15:44 UTC, Jiri Pospisil
no flags Details

Description Jiri Pospisil 2012-10-12 15:44:59 UTC
Created attachment 626073 [details]
Photo of the kernel BUG

Description of problem:
After diconnecting AC adapter I encountered "kernel BUG". See photo attached. As this happenned to a live-USB system, I have no logs. I was not successful reproducing this bug afterwards.

Additional info:
Using pm-testday provided live USB drive. Machine profile: http://www.smolts.org/client/show/pub_29d45dd7-df6b-4468-8b0c-f26537abea6b

Comment 1 Fedora End Of Life 2013-04-03 15:41:33 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 2 Justin M. Forbes 2013-04-05 19:14:36 UTC
Is this still an issue with the 3.9 kernels in F19?

Comment 3 Justin M. Forbes 2013-04-23 17:27:29 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a
response in 2 weeks.  If you are still experiencing this issue,
please reopen and attach the relevant data from the latest kernel you are
running and any data that might have been requested previously.


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