Fedora 13 Desktop freezes [Archive]

er_ashwini

28th May 2010, 06:59 AM

so far I solved the problem related to yum, and I updated the machine by login through clt+alt+f2 instead of login directly to gnome.

After updating, I figured out that when ever I scroll or browse the menu , the desktop get freezed and failed to respond not even the caps lock nor the clt+alt+fx. Everything works fine untill I click Application menu or System menu, in that also more precisely when ever I go to Applications > system tools or System menu, the problem occured.

What can be the cause for this and what can be the right solution?

System Config: acer aspire 4740, core i3 <How to find details about video cards ? >

Thanks and regards.
Ashwini

---------- Post added at 11:29 AM CDT ---------- Previous post was at 02:41 AM CDT ----------

When I installed gnome-shell I found that there is some problem with kernel, and when I saw the list I figured out crash in kernel occurs oftenly and that is why my desktop always get freeze. here is the crash report. What should I do now?

Package: kernel
Latest Crash: Fri 28 May 2010 10:23:01 PM
Command: not_applicable
Reason: ------------[ cut here ]------------
Comment: None
Bug Reports:
BackTrace
------------[ cut here ]------------
WARNING: at drivers/usb/serial/usb-serial.c:410 serial_unthrottle+0x54/0x71 [usbserial]()
Hardware name: Aspire 4740
Modules linked in: fuse ipt_MASQUERADE iptable_nat nf_nat bridge stp llc sunrpc cpufreq_ondemand acpi_cpufreq freq_table xt_physdev ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 kvm_intel kvm uinput arc4 snd_hda_codec_intelhdmi ecb snd_hda_codec_realtek ath9k ath9k_common mac80211 ath9k_hw snd_hda_intel ath uvcvideo snd_hda_codec cfg80211 videodev option v4l1_compat snd_hwdep v4l2_compat_ioctl32 iTCO_wdt snd_seq usb_wwan snd_seq_device snd_pcm snd_timer i2c_i801 snd iTCO_vendor_support usbserial rfkill soundcore snd_page_alloc broadcom tg3 joydev microcode wmi i915 drm_kms_helper drm i2c_algo_bit i2c_core video output [last unloaded: scsi_wait_scan]
Pid: 2699, comm: modem-manager Tainted: G W 2.6.33.3-85.fc13.x86_64 #1
Call Trace:
[<ffffffff8104b558>] warn_slowpath_common+0x77/0x8f
[<ffffffff8104b57f>] warn_slowpath_null+0xf/0x11
[<ffffffffa00e63c6>] serial_unthrottle+0x54/0x71 [usbserial]
[<ffffffff81284165>] tty_unthrottle+0x3a/0x47
[<ffffffff81282cd4>] reset_buffer_flags+0xdf/0xe4
[<ffffffff81282cee>] n_tty_flush_buffer+0x15/0x72
[<ffffffff81285447>] tty_ldisc_flush+0x28/0x3d
[<ffffffff81286577>] tty_port_close_start+0x14e/0x177
[<ffffffff812869c9>] tty_port_close+0x12/0x42
[<ffffffffa00e678b>] serial_close+0x58/0x61 [usbserial]
[<ffffffff812801c6>] tty_release+0x25c/0x5f0
[<ffffffff81102b9f>] __fput+0x125/0x1d7
[<ffffffff81102c66>] fput+0x15/0x17
[<ffffffff810ffe29>] filp_close+0x63/0x6d
[<ffffffff8104d58c>] put_files_struct+0x65/0xc7
[<ffffffff8104d62a>] exit_files+0x3c/0x41
[<ffffffff8104ee9b>] do_exit+0x25d/0x71a
[<ffffffff8105b068>] ? __dequeue_signal+0xe8/0x11d
[<ffffffff8104f3d4>] do_group_exit+0x7c/0xa6
[<ffffffff8105d002>] get_signal_to_deliver+0x3a1/0x3c3
[<ffffffff81008fe5>] do_signal+0x6d/0x6b3
[<ffffffff81428cb3>] ? printk+0x3c/0x41
[<ffffffff8102e6c6>] ? bad_area+0x42/0x49
[<ffffffff8100964e>] do_notify_resume+0x23/0x81
[<ffffffff8142b2dc>] retint_signal+0x48/0x8c

Thanks and Regards,
Ashwini

AdamW

28th May 2010, 10:07 PM

that's likely not the crash. that's a warn_slowpath_common, which seems to pop up quite a lot, and isn't a critical error, just a warning. I get 'em on this system but it doesn't hang.

neokun

30th May 2010, 10:54 PM

Hello ? Everyone.
My computer is also Freezing but my case, I am using "Fedora-13-i386".
It happened when

1) I try to type my password.
2) When I connected in internet and use firefox for 1 min (I mean after log in the computer)
3) F13 randomly system hang; It working only 2 to 3 min of log in)

I want to know how to diagnostic in F13.
Is F13 have any diagnostic tool or is there error report tool ?
If there are tool, can you teach us how to use them (Step by Step Guide) ?

From
neokun

AdamW

31st May 2010, 08:15 PM

there's an automated crash report tool, but it won't catch *every* crash. If it's working, when you log in - before it crashes again! - you should see a little red siren with an exclamation point on it in the system tray. That's abrt, the automated bug report tool, telling you it's caught something crashing. You can click on it to open up the report and submit it to Bugzilla - again, if you can make it in time before it crashes again :)

otherwise, you can look at the log file /var/log/messages to see if there's any information about the hangs there.

Amberson

3rd June 2010, 09:37 PM

Hello everyone.

- Please forgive me if I made mistakes, English is not my language -

I've quite the same problem. My desktop is also freezing and suddenly any input doesn't work at all (mouse& keyboard).
I have installed Fedora-13-i386, later as a test I installed the latest Ubuntu 10.04 but the same thing occur.
It happened randomly but within minutes after loggin in either using nouveau or nvidia drivers.
Not always but sometimes it is still possible a SSH connection but in /var/log/messages I can't find anything related to the problem.

I've had experienced similar problems with F12 after updating, and I can remember that as a fresh install
F12 was working properly. So I think there must be some kernel issue or something related with nvidia hardware.

My F13 kernel is 2.6.33.5-112

With Win7 that I have in dual boot no problem whatsoever (and that is really depressing!)

My config:
Intel i5-750
Asus P7P55D Pro
4 Gb ddr3 1333
Gainward Gtx 260

Any Help would be greatly appreciated!

mfernandezbl

4th June 2010, 07:31 PM

Hello every body,

I've just the same problem, after login on KDE Desktop, my desktop freezes randomly after some time!! I upgraded from Fedora 12 to Fedora 13, this is my configuration:

kernel version: 2.6.33.5-112.fc13.x86_64
CPU: Intel i5-750
Motherboard: Asus P7P55D
RAM: 4 Gb ddr 1333
Graphic Card: ASUS EAH4550 DD3 512Mb (ATI based)

The last entries in /var/log/mesages when desktop freezes was:

Jun 4 19:50:48 localhost rtkit-daemon[1769]: Sucessfully made thread 2068 of process 2067 (/usr/bin/pulseaudio) owned by '500' RT at priority 5.
Jun 4 19:50:49 localhost rtkit-daemon[1769]: Sucessfully made thread 2070 of process 2067 (/usr/bin/pulseaudio) owned by '500' RT at priority 5.
Jun 4 19:50:49 localhost rtkit-daemon[1769]: Sucessfully made thread 2071 of process 2067 (/usr/bin/pulseaudio) owned by '500' RT at priority 5.
Jun 4 19:50:53 localhost rtkit-daemon[1769]: Sucessfully made thread 2103 of process 2103 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 4 19:50:53 localhost pulseaudio[2103]: pid.c: Daemon already running.
Jun 4 19:50:54 localhost rtkit-daemon[1769]: Sucessfully made thread 2116 of process 2116 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 4 19:50:54 localhost kernel: fuse init (API version 7.13)
Jun 4 19:50:54 localhost pulseaudio[2116]: pid.c: Daemon already running.
Jun 4 19:51:50 localhost kernel: TCP lp registered
Jun 4 19:53:40 localhost ntpd[1455]: 0.0.0.0 c61c 0c clock_step +1.924452 s
Jun 4 19:53:42 localhost ntpd[1455]: 0.0.0.0 c614 04 freq_mode
Jun 4 19:53:43 localhost ntpd[1455]: 0.0.0.0 c618 08 no_sys_peer

Any Help would be greatly appreciated!

Thanks!!

Amberson

6th June 2010, 02:08 PM

Hi

After a long period of efforts I think there's no way for me to resolve this problem.
I really think is something related to the kernel.

I reinstalled F12 and with kernel 2.6.31.5-127.fc12.i686.PAE everything works just fine, as soon I try an update with newer kernels freezing comes in play again.

So I'm staying with my F12 configuration and with nvidia driver installed.

Hope others will solve their problems.

davidwillis

10th June 2010, 12:59 AM

I have the same problem, and it seems random.

I installed f13 with the experimental d3 drivers for nvidia cards. I love the driver because it actually plays movies while I use compiz. With any other nvidia driver I can only watch a small window of a move or it will shut down the player.

So I tried F13, and it works great, except it does randomly freeze. It will run for days, then just freeze. This is not acceptable for the work I do on my computer. I just figured it was the experimental 3d driver (can't blame fedora for that, since it is experimental). But after reading this, maybe it is something else.

I dual boot with ubuntu 10.04. So I will boot back into fedora and see if I can see a bug report. It would be great if this could be fixed... but I am no expert at finding what the problem is. So if someone wants to give me some instructions that will help, I will do it.

Thanks
David

davidwillis

10th June 2010, 11:36 PM

It looks like it is the kernel...

BUG: unable to handle kernel paging request at 00070001

davidwillis

11th June 2010, 07:30 PM

I did an update-reboot just before my last post, and have been running fedora since with no freezes. It has lasted longer before, but this is a good sign. I will keep running it and see how long it lasts.

---------- Post added at 10:30 AM CDT ---------- Previous post was at 09:20 AM CDT ----------

I spoke too soon.... It just froze up. I guess I am on ubuntu until this gets fixed.

TalalPRO

14th June 2010, 03:40 PM

I found 1 clue!!!

When you install fedora 13 BETA , you will find that there is no freezing but Bugs... (strange menu color)

But after that someone report thut is problem and Fedora fix it the wrong way ... But even though, It fixed the problem...

But then it's freeazing!:mad:

AdamW

14th June 2010, 11:28 PM

david: were you able to submit that to the oops tracker?

davidwillis

15th June 2010, 12:52 AM

ok, so any ideas on how to fix this besides installing the beta?

---------- Post added at 03:52 PM CDT ---------- Previous post was at 03:51 PM CDT ----------

david: were you able to submit that to the oops tracker?

yes, I did.

AdamW

15th June 2010, 10:49 PM

Hum, in your screenshot, I see vboxdrv. does uninstalling VirtualBox do anything?

davidwillis

15th June 2010, 11:05 PM

I am not sure, but I do need virtualbox, or some other way to run windowsxp. If I remember correctly it did freeze before I installed virtualbox, but again I am not sure on that. Maybe we can get some comments to see if everyone with the problem is running virtualbox.

I can uninstall virtualbox this weekend and see if it works, but I need my computer running virtualbox by sunday night, so it won't be a real long test, and if it does not freeze it will not really prove anything.

Unless I install vmware and run that with winxp, then I could keep it running until it freezes.

GrayFox

16th June 2010, 09:03 PM

I have an i7 based HP laptop. From day one the X server would go crazy in a random fashion and
Go to 99% CPU. The keyboard becomes nonfunctional and I have to ssh in and reboot.

I have filed a bug and the problem has lessened a bit but Xorg still occasionally gets hung in a loop....

AdamW

16th June 2010, 10:21 PM

davidwillis

18th June 2010, 03:43 PM

davidwillis: Understood. Have you looked at Fedora's virt stack? It's pretty easy to use, and I think can actually load VirtualBox images directly. Just install the Virtualization package group, then run virt-manager . You do need a CPU with VT support and to have it turned on in your BIOS, though.

I have not looked at that, but will... for now I have just un-installed virtualbox, and am updating. It looks like there is a new kernel 2.6.33.5.124.

I will re-boot after the update without virtualbox, and see if it can keep running all weekend.

my cpu is a core2 duo.... I will check in the bios to see if I can tun on vt support.

---------- Post added at 06:24 AM CDT ---------- Previous post was at 06:05 AM CDT ----------

I don't see any thing with vt in the bios. my processor is the core2 4400, I am thinking it may not support it.

Anyway, I am booted up, and will see if it can run without freezing for the weekend. If it does, I will install vbox back and see if it works with that...

---------- Post added at 06:27 AM CDT ---------- Previous post was at 06:24 AM CDT ----------

Looking at the intel website, my processor does not support VT....

---------- Post added at 06:43 AM CDT ---------- Previous post was at 06:27 AM CDT ----------

I have an i7 based HP laptop. From day one the X server would go crazy in a random fashion and
Go to 99% CPU. The keyboard becomes nonfunctional and I have to ssh in and reboot.

I have filed a bug and the problem has lessened a bit but Xorg still occasionally gets hung in a loop....

How do you ssh in and reboot? I have to just hit the power switch, but I don't like that. With me the mouse and keyboard becomes non-functional.

mfernandezbl

18th June 2010, 08:02 PM

Hi,

I've updated all packages installed on my computer, but the desktop is still freezing.

Kernel version: 2.6.33.5-124.fc13.x86_64

I'm suspecting that It's some kind of problem with Radeon drivers and Xorg, but I don't know what's the exactly problem! There aren't logs about it!

Any suggestions???

AdamW

18th June 2010, 08:04 PM

davidwillis: ssh in means he connects to the misbehaving machine from another system via ssh and then reboots it. Obviously you need another machine handy, and ssh server running on the misbehaving system.

Are you sure your CPU doesn't have VT support? I'd be very surprised. I was fairly sure all Core 2 CPUs have it. I run a fairly old Core 2 Quad in this system (Q6600) and it certainly has VT support. What's your CPU model exactly?

davidwillis

18th June 2010, 08:39 PM

I think this is mine, the 4400 one. Most do have support, but this is one of the first core2 duo's. I found the info here (http://www.intel.com/products/processor/core2duo/specifications.htm)

I think that is my processor, but I cant see how to tell exactly what mine is.

cat /proc/cpuinfo gives:

model intel (R) Core(TM)2 CPU 4400 @2.00GHZ

davidwillis

19th June 2010, 01:01 AM

well it froze up again, so I guess it was not virtualbox. And the strange thing, is that I did not get a but report this time, but it did freeze, and it froze just when I was switching desktops (and I had one window on one monitor showing on all desktops, so the one screen stayed on, but my other screen was blank. But the freezes seem random, this time it was when I changed desktops, one time it froze just after I had just got back to my computer and I moved the mouse to bring the monitors back on (it froze just after they cam on). One time it froze when I was just moving my mouse across the screen to another window. Another time it froze when I clicked on an option in compiz.... But it also froze before I had compiz running, so that is not the problem.

So I don't know, I was hoping the new kernel would fix it, or even taking virtialbox off.....

AdamW

22nd June 2010, 08:04 PM

yeah, sounds like it's not vbox then, you may as well turn it back on :/ I'm afraid I really can't figure out the problem here, I'd recommend filing a bug report but I can't honestly guarantee it'll be looked at super-fast or anything :/

Danielisawesome

22nd June 2010, 08:08 PM

Some more suggestions available here:

https://fedoraproject.org/wiki/Common_F13_bugs#misc-gfx

mfernandezbl

23rd June 2010, 07:47 PM

I tried these suggestions without success!!

davidwillis

24th June 2010, 02:49 PM

I looked at them, but they don't seem to apply to my problem.

Thanks for the suggestion though.... I do appreciate the help given here, even if it hasn't fixed the problem.

mecin

28th June 2010, 07:53 PM

Hello, I'm from Poland, sorry for my language :).
I have the randomly freezes on F13, i looking all of google etc... i doesn't finde resolve.

But yesterday i install on my laptop new SIDUX KDE with new kernel 2.6.34 .... and works nice :). So i decide to install once again fedora with 'nomodeset' option, download the 2.6.34 kernel from f14, and next add 'radeon.modeset=1' to kernel line. I don't have freeze :) when i running on fedora 13 kernel, after boot about 1-2 minutes system freeze.

Now I testing fedora 13 with kernel-2.6.34-18.fc14 and it works fine. I have radeon card, and its working nice with radeon.modeset=1.(never working with modeset=1, but on 2.6.34 seems to be worked!)

I don't try flashplayer, when i use fedora with 'nomdeset' and hard youtube videos i have freeze. When my system will be up to date i test this.

Try the new kernel from here http://koji.fedoraproject.org/koji/buildinfo?buildID=176027 and enjoy fedora :)

davidwillis

1st July 2010, 02:30 PM

How hard is it to try that kernel out? I have an nvidia video card, but it is worth a try.

mecin

1st July 2010, 11:23 PM

How hard is it to try that kernel out? I have an nvidia video card, but it is worth a try.

Just download the rpm packed for you and install it from console (yum localinstall <name_of_rpm>) or install with graphical packed installer.

If you have any problems just remove the packed using yum remove, but i think it will be work great.

davidwillis

3rd July 2010, 06:25 AM

OK, I have the new kernel installed, but I can't get virtual box to work. It has to re-compile the kernel, and can't find the source. I downloaded the src rpm, but it will not install, it gives me "could not do simulate: Backend will not install a src rpm file.

---------- Post added at 09:25 PM CDT ---------- Previous post was at 05:06 PM CDT ----------

Never mind... I downloaded the devel version and installed it, and it is now working... I hope that fixed the freezing problems...

silverback011

3rd July 2010, 04:39 PM

I am having the same issues. The GUI will randomly freeze on me. I am not able to switch to a virtual terminal. The mouse will still keep moving though. I have to do a shutdown via the power button. I have not tried ssh since I don't have another machine for this.

I tried Ubuntu for awhile and experienced the same problems.

This machine is a laptop Sony Vaio F116FX with an i7 processor and a GT216 GeForce GT330m (rev 2) graphics card.

The log files reveal nothing that I could see that was useful or more importantly gave me a clue as to where to start looking.

I have noticed that if I add acpi=off to the grub boot loader it has not frozen. This gives me a screen resolution of 800x600 I believe. That is what led me to this thread. I was looking for a way to get a decent screen resolution with the acpi=off setting. Right now I am thinking it is related to the acpi issue.

I will continue to look around for what may be the issue. Anyone else who has any ideas, I would greatly appreciate.

For the record, I was really impressed I was able to install linux at all on this machine. I thought I was relegated to working with a virtual machine under Win 7.

TalalPRO

3rd July 2010, 07:50 PM

I just found it !!!!!

Take a look at these configuration that i just configured:

Using (dri) configuration:See The Atachment:

Just download the DRI from the package manager and follow the pictures...

(it also enables 3D effects in VMware player using Intel video cards...)

It's not ACPI problem!

davidwillis

3rd July 2010, 09:30 PM

The new kernel seems to have fixed it for me.... If I run into more problems I will look into that. I run an nvidia card though, and I think my freezing was a kernel problem... So far it has been about 1 day without a freeze.....:)

siabost

8th July 2010, 12:50 PM

Dell Dimension 2350/2Ghz P4/1.5GB memory (updated BIOS).

Fedora 13 freezes regularly on me too on the above machine. Mandriva 2010, Ubuntu & Xubuntu 10.04 do similar (although the screen dies with Ubuntu and I get a strange bar pattern flashing on the screen.

Mepis 8.5 on the other hand is fine as were Ubuntu 9.10 & Mandriva 2009 - but presumably these will be on an older kernel.

I would agree with most here that it's a kernel issue probably affecting older machines. My 1-year old AMD powered desktop works perfectly with Ubuntu 10.04 for instance - don't think I've ever had a freeze up on that one.

Incidentally, on loading F13 from the Live CD the Dell 2350 froze with the progress bar about 70% done. Nevertheless F13 booted up from the HD including a few Kernel Crash notices which disappeared almost immediately. These Kernel Crash notices appear during some sessions & not others - this seems to have no bearing on whether the system freezes, which it does regularly.

Does anyone know if the bug has been identified? Moving to an F14 kernel causes problems in F13 program compatibility - and I assume the same would apply to Ubuntu.

Hope it gets sorted soon cos it's a bit of a pain - I thought initially it was a hardware problem (memory or HD) but from all the posts on the different distro forums this does not seem to be the case.

Ta

davidwillis

8th July 2010, 03:08 PM

Dell Dimension 2350/2Ghz P4/1.5GB memory (updated BIOS).

Does anyone know if the bug has been identified? Moving to an F14 kernel causes problems in F13 program compatibility - and I assume the same would apply to Ubuntu.

Hope it gets sorted soon cos it's a bit of a pain - I thought initially it was a hardware problem (memory or HD) but from all the posts on the different distro forums this does not seem to be the case.

Ta

I noticed I had other problems with the F14 kernel (missing sound when playing movies, but it is fixed with a reboot for a while. Also movie player would not open one time), but no more crashes. Also, Fedora 13 is the only distro that I have had this issue with.

siabost

8th July 2010, 03:23 PM

Also, Fedora 13 is the only distro that I have had this issue with.

Hmmm. Did you have the freezing during the initial installation that I noted in previous post? The two installs of F13 I've tried have frozen late on in the installation yet they still booted - this was using a live CD made from an iso downloaded from the Fedora site.

There seems to be little common ground between the machines that are affected - different graphics cards (mine is an onboard Intel chip) & PC/Laptop brands.

I think I'll try another fresh install using a different disk... just in case...

jdgiotta

8th July 2010, 05:05 PM

I experience seemingly random freezing as well. GUI freezes, but cursor will still move.
Manf/Model: HP EliteBook 8540w
Kernel: 2.6.33.5-124.fc13.x86_64

davidwillis

9th July 2010, 12:45 AM

Hmmm. Did you have the freezing during the initial installation that I noted in previous post? The two installs of F13 I've tried have frozen late on in the installation yet they still booted - this was using a live CD made from an iso downloaded from the Fedora site.

There seems to be little common ground between the machines that are affected - different graphics cards (mine is an onboard Intel chip) & PC/Laptop brands.

I think I'll try another fresh install using a different disk... just in case...

I didn't notice any freezing until after it was installed. And then it was not very often, maybe once a day on average.

kevmif

9th July 2010, 01:09 AM

I also have freezes - acer laptop 5741G I believe.

X crashes, can move the mouse but can't click anything. Can't swap terminals either. Have to hold down the power button :(

I have searched dmesg and x logs but I can't find anything.

AdamW

9th July 2010, 01:29 AM

karljs

9th July 2010, 02:46 AM

I hope folks realize I for one am mostly ignoring this thread because it's far too vague. It's quite likely that many of you are suffering from quite different bugs. Just because you all experience something that can be quantified as 'random freezes' doesn't mean you all have the same bug. I've seen dozens of separate bugs with that symptom in the past. It's quite hard to do anything meaningful to help a thread full of people who may well be suffering from quite different bugs =)

unless you all can identify something that clearly links your cases, it'd likely be best for you to file separate threads / bug reports.

I have a hunch that the problem is the same as mentioned in this thread:
http://forums.fedoraforum.org/showthread.php?t=245923

That error in the X log file is not very helpful as it can appear for any number of reasons but it has mysteriously occurred randomly for a large number of people lately. Unfortunately it is all I am able to provide and this a definite showstopper for me.

Edit: I should mention also that it isn't JUST a random freeze as (for me at least) the mouse cursor can still be moved but Xorg refuses to take input mouse clicks or keyboard input.

Edit 2: This bug also occurs in the RC of OpenSUSE and some helpful info may be available in this bug report: https://bugzilla.novell.com/show_bug.cgi?id=597078

AdamW

9th July 2010, 03:22 AM

karljs: so you don't even actually have the same symptoms as several others in the thread. 'X fell over' is a completely different bug to 'the system froze'.

As you say, that error message is, on its own, useless; it doesn't indicate the source of the problem at all, and can be caused by many different problems.

karljs

9th July 2010, 03:30 AM

karljs: so you don't even actually have the same symptoms as several others in the thread. 'X fell over' is a completely different bug to 'the system froze'.

I agree with you completely that they are different but I think that the majority of people posting in this thread are having the same problem as me but are not describing it with enough detail.

chayman

9th July 2010, 05:55 AM

I also have random desktop freeze:

My history start with ubuntu 10.04, same random freeze without any valuable information in /var/log/*. This make me install fedora (about 3 years without using it) but with the same results.

So this time, I decided to install kernel crash utilities (from http://fedoraproject.org/wiki/Kernel/kdump), and strangely this seems to solve the kernel freeze. Since the installation I'm getting Xorg crashes. Some of the crashes shutdown X, some of them just freeze X (but I can do ssh from my centos machine, avoiding the reset button).

Not all the crashes are managed by abrt, but I'm posting today abrt catch crashes:

./ccpp-1278593614-2856/ (08:53)
component: bash
cmdline: /bin/sh /usr/lib/ConsoleKit/scripts/ck-system-restart
reason: SIGSEGV

./ccpp-1278594061-3218/ (09:01)
component: bash
cmdline: /bin/bash /usr/bin/run-parts /etc/cron.hourly
reason: SIGSEGV

./ccpp-1278642103-1322/ (22:21)
component: xorg-x11-server
cmdline: /usr/bin/Xorg :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm-kxcUdy/database -nolisten tcp vt1
reason: SIGABRT

The last one was a X server shutdown (while I'm working is annoying). All of them seems to be just symptoms of something else.
I've installed debug info for X, and gdb says:

(gdb) where
#0 0x000000330cc329a5 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x000000330cc34185 in abort () at abort.c:92
#2 0x0000000000460c1e in OsAbort () at utils.c:1335
#3 0x000000000046919d in AbortServer () at log.c:425
#4 0x00000000004699f0 in FatalError (f=0x574028 "Caught signal %d (%s). Server aborting\n") at log.c:553
#5 0x000000000046041e in OsSigHandler (signo=11, sip=<value optimized out>, unused=<value optimized out>) at osinit.c:156
#6 <signal handler called>
#7 0x00000000004312fc in CompareISOLatin1Lowered (s1=0xff000001004b20 <Address 0xff000001004b20 out of bounds>, s1len=<value optimized out>, s2=0x583aa8 "nearest", s2len=<value optimized out>) at dixutils.c:177
#8 0x00000000004c54a2 in PictureGetFilterId (filter=0x583aa8 "nearest", len=7, makeit=1) at filter.c:59
#9 0x00000000004c77f0 in SetPictureToDefaults (pPicture=0x3479db0) at picture.c:735
#10 0x00000000004c7e15 in CreatePicture (pid=70382862, pDrawable=0x34ab030, pFormat=0x1004e48, vmask=256, vlist=0x3495e6c, client=0x2c80a70, error=0x7fff6f1b4bbc) at picture.c:786
#11 0x00000000004ce9ba in ProcRenderCreatePicture (client=0x2c80a70) at render.c:612
#12 0x000000000042c28c in Dispatch () at dispatch.c:439
#13 0x000000000042190a in main (argc=<value optimized out>, argv=0x7fff6f1b4dc8, envp=<value optimized out>) at main.c:286

(but I don't know why the signal was thrown).

I'm attaching my full HW specs (generated via lshw), but in summary I have:
AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
2GB Ram
GeForce 8600 GT (with nouveau, without mesa-dri-drivers-experimental)
Hitachi HD 320GB

The system is fully updated, with the add of rpmfusion repo (for video/audio extra support).

The services currently running are:

abrtd atd cpuspeed crond
cups gpm ip6tables iptables
irqbalance kdump messagebus netfs
NetworkManager ntpd portreserve rsyslog
sendmail smolt sshd udev-post

And SELinux is disabled.
My fedora installation comes from the gamers spin off.

Well that's all, best regards!

chayman

9th July 2010, 07:17 AM

Update:

Today, after 2 days, I've got the system complete freeze:
no X, no console, no network access, no crash dump (/var/crash is empty).
So, my hypothesis about installing & setting kdump to avoid kernel freeze was wrong.
As usual, I can't find nothing usable in /var/log/* and abrt didn't work.

siabost

9th July 2010, 08:23 AM

Hi AdamW,

Dell Dimension 2350/2Ghz P4/1.5GB memory (updated BIOS).
Desktop freezes; cursor still moves with mouse.

Those suffering the same symptoms in this thread, that I can see:
myself (siabost)
karljs
kevmif
jdgiotta
silverback011
esok
- any more?

Yesterday I reinstalled F13 from a different disk - one supplied with a recent Linux Format magazine (LXFDVD134) - and this time the install did not freeze on me.
So far I have not had a "mouse still moves freeze" since the new install & I have been working it quite heavily trying to get WinXP installed via Virtualbox (but that's a story for a different thread). One kernel crash warning but that seemed to pass off with no effect
This new install (after updates) gives me a kernel of 2.6.33.3-85.fc13.i686 - this seems to be different from the majority in this thread.

To clarify, the problems I had U/Xbuntu 10.04 previously on the same machine seem to have been X collapses.

I will post as much info as I can later.

;)

esok

9th July 2010, 02:24 PM

I appear to be having the same trouble as many of you. I am running Fedora 13 x86_64, kernel 2.6.33.5-124.fc13.x86_64. I can get the machine to freeze reliably by running gimp and opening a file, or by running Xsane. I still have cursor control after the freeze but the screen doesn't update. I haven't yet tried to ssh into the machine after the freeze. Trying to switch virtual terminals doesn't work.

Update: The machine is not completely dead, because I can ssh into it from another machine. Xorg just locked up hard. I installed Fedora 13 xfce spin on the same machine (it has a slightly different kernel version) and the same problems do not manifest. I even upgraded to (I think) kernel 2.6.33.6-something and it still works well.

TSmurf

9th July 2010, 08:35 PM

I've been lurking and figure now is the time to jump in...

I've been having similar problems with a brand new Dell Precision M4500, with an Intel i7-820.

Like others have said, I'm not sure all these go together or not. Just thought I'd throw my info into the mix to help move towards a solution.

It literally locks up at totally random times and I have not been able nail down a set of actions that guarantees a lock up. Sometimes the mouse moves, other times it doesn't. I can ssh in, and start killing off processes but it does not change what appears on the screen. As soon as I kill X, the whole thing locks tight and I lose my ssh connection.

There is nothing suspicion in my Xorg log. However, after every lock up the last line of /var/log/messages is:

kernel: dell-wmi: Received unknown WMI event (0x11)

This is a new machine that I'm moving to, so I have flexibility to fight it for a few days. I'm going to see if I get similar results with any other distros, and also a fresh Fedora 13 install.

siabost

9th July 2010, 10:48 PM

Anyone know what kernel we should be on in F13 stable (32b & 64b) i.e. non-testing?

Folks posting here seem to be on a variety.

Ta

thesun

9th July 2010, 11:00 PM

Sorry if I'm jumping into the wrong thread, but I have a problem at boot (as of an update to the newest kernel from a Kpackagekit update yesterday...). In my case, the keyboard works for entering the password for the full disk encryption, but is hung at the point where the user is selected and he enters his password. I have mouse use, but no keyboard. Nor does the virtual keyboard work. So I am stuck because I cannot enter my password.

If this is NOT the same problem, I'm sorry...but it started right this morning after a reboot when I updated the kernel. Anyone having similar issues?

TSmurf

10th July 2010, 02:56 AM

I'm on kernel version 2.6.33.5-124.fc13.x86_64

I just tried Ubuntu and LinuxMint (same line I know, but it was worth a shot), and both froze shortly after the very 1st GRUB screen, even if I chose the option to go to compatibility mode (VESA driver). So I don't fit in with the group who can run Ubuntu without freezes.

I'm going to start a separate thread about my issue under a similar title.

AdamW

12th July 2010, 08:43 PM

tsmurf: try creating a file /etc/modprobe.d/blacklist-dell.conf with this content:

blacklist dell-wmi

and see if that fixes your problem. (It'll likely stop the extended keys on your laptop's keyboard from working, note). If it does, then your particular issue is a bug in the dell-wmi kernel module.

Note to everyone else: don't bother trying this unless you also have suspicious lines from the dell-wmi module in your logs.

TSmurf

12th July 2010, 09:02 PM

I played with Xorg and didn't have any success...if I force a manual config it only creates problems.

Just tried the blacklist-dell.conf and will see what happens.

Fortunately the only extended keys are a rocker for volume control and one for mute/unmute.

Let the waiting begin to see if it freezes...

Thanks.

TSmurf

13th July 2010, 08:49 PM

No luck with the dell-wmi thing.

It went about 25 hours and then froze. I'm going to comb over the latest logs to see if there is any even remote clue.

Thanks.

rmbrady

15th July 2010, 06:20 PM

Hi
Just to add my method of locking up the Desktop.
Start either Openoffice, or Dia and lock the Desktop. The mouse still moves,
but the keyboard is frozen, with no access to the F2-F6 terminals

ssh access to the machine still works, however I can't stop X by dropping
to runlevel 3, as telinit 3 appears to do nothing :-(

The only way I can get the system back is a 5 second hold on the power button.
I never get any abrt crash messages.

siabost

15th July 2010, 10:17 PM

Hi all,

Well, while I was on kernel 2.6.33.3-85.fc13.i686 I didn't suffer a desktop freeze (mouse still moving). Trouble was Virtualbox was not allowing me to start the guest machine.

I downloaded the latest Virtualbox version from the Virtualbox website and followed the instructions given including running "yum update".

This has now left me on kernel 2.6.33.6-147.fc13.i686 and the freezing (mouse still moving) is back. There are no error messages in var/log/dmesg that I can see (although I can post the whole thing if it's useful) and their was no crash alert before the freeze but copied below is the Bug Reporter backtrace - it marked it up as a kernel crash.

WARNING: at mm/highmem.c:453 debug_kmap_atomic+0xad/0x12a()
Hardware name: Dimension 2350
Modules linked in: aes_i586 aes_generic fuse vboxnetadp vboxnetflt vboxdrv p4_clockmod ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 uinput arc4 ecb rt61pci crc_itu_t snd_intel8x0 rt2x00pci rt2x00lib snd_ac97_codec ac97_bus mac80211 snd_seq snd_seq_device b44 cfg80211 iTCO_wdt ssb iTCO_vendor_support rfkill mmc_core ppdev snd_pcm i2c_i801 mii eeprom_93cx6 snd_timer snd parport_pc soundcore parport snd_page_alloc dcdbas microcode i915 drm_kms_helper drm i2c_algo_bit i2c_core video output [last unloaded: scsi_wait_scan]
Pid: 2211, comm: VirtualBox Tainted: G W 2.6.33.6-147.fc13.i686 #1
Call Trace:
[<c0436e31>] warn_slowpath_common+0x65/0x7c
[<c04aa561>] ? debug_kmap_atomic+0xad/0x12a
[<c0436e55>] warn_slowpath_null+0xd/0x10
[<c04aa561>] debug_kmap_atomic+0xad/0x12a
[<c04240ec>] kmap_atomic_prot+0x51/0xd2
[<f7da5f5d>] ? i915_error_object_create+0x5d/0xfa [i915]
[<c042417b>] kmap_atomic+0xe/0x10
[<f7da5f9f>] i915_error_object_create+0x9f/0xfa [i915]
[<f7da632a>] i915_handle_error+0x330/0x813 [i915]
[<f7da68ac>] i915_hangcheck_elapsed+0x9f/0xdf [i915]
[<c0441a35>] run_timer_softirq+0x163/0x1e6
[<f7da680d>] ? i915_hangcheck_elapsed+0x0/0xdf [i915]
[<c043c20d>] __do_softirq+0xac/0x152
[<c043c2e4>] do_softirq+0x31/0x3c
[<c043c3f8>] irq_exit+0x29/0x5c
[<c0417fb7>] smp_apic_timer_interrupt+0x6f/0x7d
[<c07714c5>] apic_timer_interrupt+0x31/0x38
[<c077007b>] ? __mutex_lock_common+0xde/0x15f

The only plus is that Virtualbox now works if only between freezes.

It does seem to be a kernel thing,:confused: no?

TSmurf

18th July 2010, 04:13 PM

Still freezing on my end. Tried switching to XFCE from Gnome and it still froze.

Here's my /var/log/messages from the last two freezes.

Jul 17 09:44:04 JeffPrecision abrt[5294]: saved core dump of pid 1881 (/usr/bin/Xorg) to /var/cache/abrt/ccpp-1279377843-1881.new/coredump
(41861120 bytes)
Jul 17 09:44:04 JeffPrecision abrtd: Directory 'ccpp-1279377843-1881' creation detected
Jul 17 09:44:04 JeffPrecision abrtd: Registered Database plugin 'SQLite3'
Jul 17 09:44:12 JeffPrecision kernel: [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 2
Jul 17 09:44:12 JeffPrecision kernel: [drm] nouveau 0000:01:00.0: Failed to idle channel 2.
Jul 17 09:44:12 JeffPrecision kernel: [drm] nouveau 0000:01:00.0: PGRAPH idle timed out with status 0x00b00003
Jul 17 09:44:12 JeffPrecision kernel: [drm] nouveau 0000:01:00.0: PGRAPH idle timed out with status 0x00b00003
Jul 17 09:44:12 JeffPrecision kernel: [drm] nouveau 0000:01:00.0: PGRAPH idle timed out with status 0x00b00103
Jul 17 09:44:12 JeffPrecision gnome-keyring-daemon[2142]: dbus failure unregistering from session: Connection is closed
Jul 17 09:44:12 JeffPrecision gnome-keyring-daemon[2142]: dbus failure unregistering from session: Connection is closed
Jul 17 09:44:12 JeffPrecision NetworkManager[1548]: <info> (eth1): device state change: 8 -> 3 (reason 38)
Jul 17 09:44:12 JeffPrecision NetworkManager[1548]: <info> (eth1): deactivating device (reason: 38).
Jul 17 09:44:12 JeffPrecision NetworkManager[1548]: <info> (eth1): canceled DHCP transaction, DHCP client pid 5214
Jul 17 09:44:12 JeffPrecision NetworkManager[1548]: <error> [1279377852.937919] [nm-system.c:1229] check_one_route(): (eth1): error -34 ret
urned from rtnl_route_del(): Sucess#012
Jul 17 09:44:12 JeffPrecision avahi-daemon[1559]: Withdrawing address record for 192.168.1.5 on eth1.
Jul 17 09:44:12 JeffPrecision avahi-daemon[1559]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.1.5.
Jul 17 09:44:12 JeffPrecision avahi-daemon[1559]: Interface eth1.IPv4 no longer relevant for mDNS.
Jul 17 09:44:13 JeffPrecision console-kit-daemon[1901]: WARNING: Couldn't read /proc/2079/environ: Failed to open file '/proc/2079/environ'
: No such file or directory
Jul 17 09:44:13 JeffPrecision abrtd: New crash /var/cache/abrt/ccpp-1279377843-1881, processing
Jul 17 09:44:13 JeffPrecision abrtd: Registered Action plugin 'RunApp'
Jul 17 09:44:13 JeffPrecision abrtd: RunApp('/var/cache/abrt/ccpp-1279377843-1881','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
Jul 17 09:44:13 JeffPrecision kernel: [drm] nouveau 0000:01:00.0: GPU lockup - switching to software fbcon
Jul 17 09:44:14 JeffPrecision ntpd[1781]: Deleting interface #11 eth1, 192.168.1.5#123, interface stats: received=9, sent=10, dropped=0, active_time=623 secs
Jul 17 09:44:14 JeffPrecision ntpd[1781]: 72.18.205.156 interface 192.168.1.5 -> (null)
Jul 17 09:44:14 JeffPrecision ntpd[1781]: 208.77.19.5 interface 192.168.1.5 -> (null)
Jul 17 09:44:14 JeffPrecision ntpd[1781]: 206.210.192.99 interface 192.168.1.5 -> (null)
Jul 17 09:44:14 JeffPrecision kernel: [drm] nouveau 0000:01:00.0: Allocating FIFO number 2
Jul 17 09:44:14 JeffPrecision kernel: [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 2
Jul 17 09:45:42 JeffPrecision kernel: imklog 4.4.2, log source = /proc/kmsg started.

Freeze 2:
Jul 18 07:16:34 JeffPrecision kernel: dell-wmi: Received unknown WMI event (0x11)
Jul 18 07:46:37 JeffPrecision kernel: dell-wmi: Received unknown WMI event (0x11)
Jul 18 08:43:28 JeffPrecision kernel: dell-wmi: Received unknown WMI event (0x11)
Jul 18 08:47:09 JeffPrecision kernel: npviewer.bin[4057]: segfault at 418 ip 00000000026dda56 sp 00000000ff8c1b18 error 6 in libflashplayer.so[248f000+b04000]
Jul 18 08:47:09 JeffPrecision abrt[6565]: saved core dump of pid 4057 (/usr/lib/nspluginwrapper/npviewer.bin (deleted)) to /var/cache/abrt/ccpp-1279460829-4057.new/coredump (116715520 bytes)
Jul 18 08:47:09 JeffPrecision abrtd: Directory 'ccpp-1279460829-4057' creation detected
Jul 18 08:47:09 JeffPrecision abrtd: Executable '/usr/lib/nspluginwrapper/npviewer.bin (deleted)' doesn't belong to any package
Jul 18 08:47:09 JeffPrecision abrtd: Corrupted or bad crash /var/cache/abrt/ccpp-1279460829-4057 (res:4), deleting
Jul 18 08:54:59 JeffPrecision kernel: imklog 4.4.2, log source = /proc/kmsg started.

ragatron

19th July 2010, 07:42 AM

I don't know if it the same problem, but I seem to be having a similar issues with F13 freezing suddenly. It happens whenever I try and do a yum update, or when surfing the internet. It only freezes whenever I have my ethernet cable plugged in, and after a few seconds of being idle. If I move the mouse cursor around constantly fedora will continue working until I stop moving it for more than 10 seconds. When it freezes I am forced to reboot the machine by hitting the power button.

I have turned off the screen saver, and set on my power settings to do nothing when idle. The problem still occurs.

Here are my hardware specs:
Toshiba NB305 mini netbook
Intel® Atom™ Processor N450
Intel® Graphics Media Accelerator 3150

A-Zed

19th July 2010, 11:57 AM

I am getting all the same symptoms. Random freeze. I updated the kernel to .147 and get the freezes.

I have a Gigabyte MoBo, Intel core duo (2 years old), 4 GB RAM and am prepared to state that F13 is *****.

rmbrady

20th July 2010, 08:48 PM

I just tried to use the GIMP to edit a screenshot, and the desktop locked up, with the mouse moving,
but nothing else ( No F2-F6 terminals either).
I think I will start a Howto Guide for Desktop Lockup, as if I start Openoffice, or now the GIMP, I am
locked up and need the power button to get the machine back.

Is there a guru out there who can give some tips on diagnostics, as I can ssh into the locked machine, but I
cannot see anything obvious.

shimoda

21st July 2010, 02:41 PM

I think that here are mix of different symptoms but others are the same!

I suffer exact the same problem, for example opening a file in gimp... Keyboard freeze -> had to reset machine

I'm in Fedora 13 64bit, recently installed...
I've a Nvidia card... I'll try installing proprietary drivers (i'm using nouveau) and report here the results...

In my case not are random freezes... For example in Gimp, is every time I try to load and image...

---------- Post added at 05:41 AM CDT ---------- Previous post was at 12:29 AM CDT ----------

Sorry for double posting,

but confirmed!!!!

in my case, enabling Nvidia proprietary drivers solves the problem!!

tempest766

21st July 2010, 06:00 PM

I believe that there is a known problem in X that make the machine appear to be dead. The X server locks up and the user cannot use the keyboard to restart or exit X. The pointer may or may not be dead at this point. The backtrace usually puts the point of failure at a symbol (mieqEnenqueue+????). And further up the foodchain it gets there from evdev and whatever video driver you happen to be using.

Based on information in bugzilla it seems that developers are aware of it, that it is a bug of at least two years old, and that they don't know how to fix it so will generally blame it on something else, or say "lack of detail---ticket closed". I'd say "you get what you pay for" in support circles, but "pay for support" linux channels usually aren't much better.

If you see this error then try using a different video driver and/or different screen resolutions. Moving things around in memory seems to make it less frequent or go away altogether.

rmbrady

22nd July 2010, 08:35 PM

Loaded the Nvidia driver, using http://forums.fedoraforum.org/showthread.php?t=204752 instructions
and now Openoffice and the Gimp run fine.
Bye Bye Lockups :-)

xwolfi

23rd July 2010, 05:25 PM

Loaded the Nvidia driver, using http://forums.fedoraforum.org/showthread.php?t=204752 instructions
and now Openoffice and the Gimp run fine.
Bye Bye Lockups :-)

Hi! Exact same problem, exact same solution!

To further explain what I had and did:

I am intensively web developping with my computer, and installed fedora on a computer with an nvidia card. From time to time, when using firefox (not sure it is the cause, but each time I had the freeze I was using it), the whole computer suddently blocks, I can move the mouse and nothing else. Pretty boring when working.

So I tried to use the nvidia proprietary drivers, and never faced another freeze again! And it's been one week, so I think the main problem comes from the nouveau drivers :)

Boricua

24th July 2010, 01:28 PM

I had the same issues (Fedora 13 64bit). Some random and unexplained freezes happening as soon as the screensaver started. However, I updated several xorg packages available in the updates-testing repo and the issue seems to be solved, at least so far.

cvbrowne

26th July 2010, 05:31 PM

I'm having the same issue. see thread http://forums.fedoraforum.org/showthread.php?t=247980

I do have a work around. However, I would like to fix this permanently.

Marcuccio

10th August 2010, 06:11 PM

I'm also having this issue. My hardware is : Asus P6TD Deluxe, core i7 920, Asus nvidia gt220.
Symptoms are:

1) Gui completely frozen and unresponsive
2) mouse still working
3) keyboard frozen (block num not working, no ctrl+alt+backspace, no ctrl+alt+F1...F12)
4)rarely , while everything is frozen, i can still remotely connect through ssh

With fedora 12 the problem comes up only after 20-30 minutes of interactive use of the X environment (quite sure the problem is the same... http://forums.fedoraforum.org/showthread.php?t=238512&page=1)

With fedora 13 the problem comes up aftre 18 - 24 hour of uptime, usually while you are interactively using some X application

Now i have installed nvidia proprietary driver and blacklisted nouveau module and the system has been up for 48 hour without error...
I think the problem is unrelated to hw because some people have had it with non nvidia cards. Probably the installation of nvidia proprietary drive has disabled something somewhere...(in the hypothesis that the nvida proprietary driver solve the problem, but i'm still not sure of it!)

This is a really hard to discover bug, opening a bug to bugzilla is also very difficult because of the way the problem comes up (no log, no way to deterministically repeat the issue...).

Marco

Pollete

10th September 2010, 08:25 AM

I'm with the same problem, in a Fedora13, it works perfectly even i let the computer alone. Then, frozes and i need to reboot manualy.

kailashkumar

16th September 2010, 05:12 AM

For me, the culprit turned out to be compiz.
Uninstalled compiz and compiz-gnome packages. Enabled metacity compisiting manager using gconftool.

gconftool-2 -s --type bool /apps/metacity/general/compositing_manager true

The performance and looks are not that good as with compiz but decent enough for me.

I am using Intel Graphics card
VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller

Escher

18th September 2010, 01:50 AM

I konw that is the video driver that is freezing the system. When i disable it, the system goes ok. ( nVidia )

Here the message log when it freezes:

Aug 9 20:42:32 localhost kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Aug 9 20:42:32 localhost kernel: ata3.00: failed command: WRITE DMA EXT
Aug 9 20:42:32 localhost kernel: ata3.00: cmd 35/00:00:80:29:f7/00:04:07:00:00/e0 tag 0 dma 524288 out
Aug 9 20:42:32 localhost kernel: res 40/00:08:b0:41:97/84:00:0b:00:00/e6 Emask 0x4 (timeout)
Aug 9 20:42:32 localhost kernel: ata3.00: status: { DRDY }
Aug 9 20:42:37 localhost kernel: ata3: link is slow to respond, please be patient (ready=0)
Aug 9 20:42:42 localhost kernel: ata3: device not ready (errno=-16), forcing hardreset
Aug 9 20:42:42 localhost kernel: ata3: soft resetting link
Aug 9 20:42:43 localhost kernel: ata3.00: configured for UDMA/33
Aug 9 20:42:43 localhost kernel: ata3: EH complete

Edit: Problem resolved.
I changed the SATA II HD for a old ATA disk.

wjlink

25th September 2010, 11:02 PM

I've experienced the same problem described by others on this forum,
Fedora 13 running on a PC with an Intel Core i3 processor fails to
respond to keyboard or mouse input. The problem occurred at random
and could only be cleared by a system reboot. While trying to deal
with the problem I discovered that I could plug a USB mouse into my
PC and it would work properly while, my PS/2 mouse and keyboard both
remained unusable. Eight days ago I switched to using a USB connected
mouse and keyboard on my PC. I haven't experienced an input freeze
problem since I made this change.

gerarcm

29th September 2010, 12:18 AM

Hello.

Greetings from Mexico, running on a Dell Studio 15, Intel video.

System locks up at random. It will even (although not as often) lock up when in run level 3. This sort of tells me it's not an X thing. It took me about 3 days, on and off, to complete my initial yum update, since it kept locking up at different stages. I thought that would have fixed the problem.

Since it was locking up, and fearing it a problem with X, I changed my default runlevel to 3. It allowed me to complete the updates, so it did run for about 5 hours straight before it locked up again.

Besides that, It is the same symptoms that others have reported. Total system freeze (Have not tried to ssh in, I had that service disabled) No info on logs or ABRT. only recourse is to hard-reset the laptop.

Run level 5 experiences lockups still. Run level 3 does, but far less frequently. I have not tried running X within rl3, but I might try that next.

I hope this is even remotely related, so we can start to pinpoint a cause.

[EDIT]

Sorry, forgot to mention
Running f13-64.
kernel is 2.6.34.7-56 (latest as of today's updates)