Fedora 13 Desktop freezes

[er_ashwini]

I just installed fedora 13 64 bit on core i3. When I login in to gnome, after few minutes, desktop get freezed and forced to restart the machine via power button. Same is happening in KDE also.

Whats wrong with this release, not able to figure it out.

Also, yum is giving error of failed to get the repo...
Also, wvdial is showing connection established but unable to browse the net.

This made me to get back to Ubuntu 10.04. I am still looking for the solution. any suggestions Please.

Thanks and Regards,
Ashwini

[sej7278]

I just installed fedora 13 64 bit on core i3. When I login in to gnome, after few minutes, desktop get freezed and forced to restart the machine via power button. Same is happening in KDE also.

i have that on f12 64-bit, it seems to be something to do with the intel 915 video drivers segfaulting.

what i noticed though is that its just xorg that's dead, you can still ssh into the machine. i can't seem to restart X from the console though, can't figure out what process to kill.

[AdamW]

telinit 3
telinit 5

but obviously, it shouldn't do that. the initial report is too vague to be of any use, though. we need _some_ kind of diagnostic...

[er_ashwini]

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]

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]

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]

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]

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]

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]

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]

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]

It looks like it is the kernel...

BUG: unable to handle kernel paging request at 00070001

[davidwillis]

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]

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!

[AdamW]

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