Bug 204175

Summary: kernel trace during suspend on disk
Product: [Fedora] Fedora Reporter: Patrice Dumas <pertusus>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-30 11:29:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg output
none
xorg.log none

Description Patrice Dumas 2006-08-26 12:32:15 UTC 
Description of problem:

A suspend on disk seems to resume well, but mouse cursor has 
disappeared (from gdm or fluxbox). It happens with the 
touchpad, and also with an external usb mouse.

Computer is a Dell Latitude D505. System is rawhide up-to-date.
kernel 2.6.17-1.2586.fc6.

There is a trace of something going wrong appearing in dmesg. 
I attach it. Nothing seems wrong in Xorg log. I attach it also.

On the mingetty console the mouse cursor is still there.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Patrice Dumas 2006-08-26 12:32:15 UTC 
Created attachment 134976 [details]
dmesg output
Comment 2 Patrice Dumas 2006-08-26 12:33:32 UTC 
Created attachment 134977 [details]
xorg.log
Comment 3 Patrice Dumas 2006-08-30 11:08:00 UTC 
I can reproduce the mouse cursor disappearing when I switch
to a mingetty console (with ctrl-alt-F1). There is no trace in that 
case. Therefore I think the trace is unrelated to the mouse cursor
disappearing. I change the summary accordingly. I have entered 
Bug #204599 for the mouse cursor disappearing.

The trace seems to be harmless, but I guess it is still worth 
reporting it.

The trace is the same with
2.6.17-1.2597.fc6
Comment 4 Patrice Dumas 2006-08-30 11:29:33 UTC 
Found that it is a duplicate of Bug #184027, closing.

*** This bug has been marked as a duplicate of 184027 ***