Bug 722546 - complete freeze with 2.6.38.8-35.fc15.x86_64 kernel
Summary: complete freeze with 2.6.38.8-35.fc15.x86_64 kernel
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-15 15:49 UTC by Gianluca Cecchi
Modified: 2012-06-06 16:09 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-06 16:09:27 UTC
Type: ---


Attachments (Terms of Use)
yum.log since begin of July (11.20 KB, text/plain)
2011-07-15 15:50 UTC, Gianluca Cecchi
no flags Details

Description Gianluca Cecchi 2011-07-15 15:49:47 UTC
Description of problem:
it happened two times after today updates that I have complete system freeze on my system.
first time after few minutes after boot. Another time after about 7 hours...
I'm going to attach latest today updates.
Both times I was using evolution:
- mouse scrolling through inbox folder items
- mouse click between sent items and inbox folder
I'm using evolution-mapi to connect to exchange 2007

I tipically have many applications open and I'm not always in evolution window,
So first attempt to bugzilla against evolution, but then I changed to kernel due to complete freeze...
After freeze I have no mouse pointer movement indication, no network reachability
let me know how to debug this, please... 

Version-Release number of selected component (if applicable):
2.6.38.8-35.fc15.x86_64

How reproducible:
random

Steps to Reproduce:
1. boot system
2. open some applications (eg evolution, firefox, virt-manager, gnome-terminal)
3. work in the system
  
Actual results:
after few minutes o few hours I get complete freeze

Expected results:
normal behaviour

Additional info:
I have been using F15 since RC3 on this system and didn't get any freeze like this...
It has begun happening right today.
I admit information is quite vague... and could also be related to something else (such as hw dying, ecc)

Some details about the system
Dell XPS M1330 laptop where default nouveau driver is installed
I got the first freeze at about 09:50 and this is the content of /var/log/messages:
Jul 15 09:49:51 ope46 dbus: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Jul 15 09:49:51 ope46 dbus: [system] Successfully activated service 'org.freedesktop.PackageKit'
Jul 15 09:53:19 ope46 kernel: imklog 5.8.2, log source = /proc/kmsg started.
Jul 15 09:53:19 ope46 rsyslogd: [origin software="rsyslogd" swVersion="5.8.2" x-pid="929" x-info="http://www.rsyslog.
com"] start


At the second freeze (at about 17:24):
Jul 15 16:58:58 ope46 dbus: [system] Successfully activated service 'org.freedesktop.PackageKit'
Jul 15 17:04:25 ope46 pulseaudio[1805]: ratelimit.c: 491 events suppressed
Jul 15 17:26:25 ope46 kernel: imklog 5.8.2, log source = /proc/kmsg started.
Jul 15 17:26:25 ope46 rsyslogd: [origin software="rsyslogd" swVersion="5.8.2" x-pid="904" x-info="http://www.rsyslog.com"] st
art
Jul 15 17:26:25 ope46 kernel: [    0.000000] Initializing cgroup subsys cpuset

Any way to use any debug, such as Ctrl+Alt+PrntScr to debug...?

Comment 1 Gianluca Cecchi 2011-07-15 15:50:53 UTC
Created attachment 513415 [details]
yum.log since begin of July

Comment 2 Michael Renz 2012-01-13 07:31:21 UTC
Hello ,

I', using fedora 16 
with Linux kernel 3.1.7-1.fc16.x86_64.

After a short time of working the gnome3 desktop freeze.

I could not find out why - it is reproduceable - 
i'm using nvidia-graphics driver

CTRL-ALT-BACKSPACKE is possible - and starts over again...

Comment 3 Josh Boyer 2012-06-06 16:04:30 UTC
2.6.38.8-35.fc15.x86_64 is fairly old at this point.  Are you still getting freezes with 2.6.43/3.3 in F15/F16?

Comment 4 Gianluca Cecchi 2012-06-06 16:07:11 UTC
In my case, I'm now on F17  and on anoher hardware (the XPS died ;-)
So for my problem the bugzilla could be closed.
I don't know for Michael Renz...

Comment 5 Josh Boyer 2012-06-06 16:09:27 UTC
(In reply to comment #4)
> In my case, I'm now on F17  and on anoher hardware (the XPS died ;-)
> So for my problem the bugzilla could be closed.
> I don't know for Michael Renz...

Thanks for letting us know.  Michael's problem sounded different, so we'll close this out.


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