system freezes while using Mozilla
am 12.09.2006 04:38:15 von Karthik Vishwanath
Hello,
I recently installed Fedora core 5 on an intel dual-core CPU box. The
machine froze up while running gnome2 while I was engaged in simple
browsing activity using firefox 1.5.01.
The "freezing" occurred twice one after the other and during both these
instances I was using firefox to browse the web (while having at least 2-4
firefox tabs open). The machine froze up in both instances and did not
respond to the keyboard/mouse or to a remote login/ping. I checked
/var/log/messages just before the "restart" line and did not find any
unusual entries (+/-5 lines around the restart lines from
/var/log/messages is included below).
I was wondering if:
(a) this matched any known issue with FC5 and intel hardware
(b) if there was any way that I could _recover_ control upon a system
freeze such as this?
All responses are appreciated.
Thanks,
-K
---------
lines from /var/log/messages:
....
Sep 11 15:23:19 dhcp-152-3-194-19 dhclient: DHCPREQUEST on eth0 to
152.3.17.193 port 67
Sep 11 15:23:19 dhcp-152-3-194-19 dhclient: DHCPACK from 152.3.17.193
Sep 11 15:23:19 dhcp-152-3-194-19 dhclient: bound to 152.3.194.19 --
renewal in 3162 seconds.
Sep 11 16:16:01 dhcp-152-3-194-19 dhclient: DHCPREQUEST on eth0 to
152.3.17.193 port 67
Sep 11 16:16:01 dhcp-152-3-194-19 dhclient: DHCPACK from 152.3.17.193
Sep 11 16:16:01 dhcp-152-3-194-19 dhclient: bound to 152.3.194.19 --
renewal in 3472 seconds.
Sep 11 16:32:19 dhcp-152-3-194-19 syslogd 1.4.1: restart.
Sep 11 16:32:20 dhcp-152-3-194-19 kernel: klogd 1.4.1, log source =
/proc/kmsg started.
Sep 11 16:32:20 dhcp-152-3-194-19 kernel: Linux version
2.6.15-1.2054_FC5smp (bhcompile@hs20-bc1-3.build.redhat.com) (gcc version
4.1.0 20060304 (Red Hat 4.1.0-3)) #1 SMP Tue Mar 14 16:05:46 EST 2006
Sep 11 16:32:20 dhcp-152-3-194-19 kernel: BIOS-provided physical RAM map:
Sep 11 16:32:20 dhcp-152-3-194-19 kernel: BIOS-e820: 0000000000000000 -
00000000000a0000 (usable)
....
Sep 11 16:34:30 dhcp-152-3-194-19 kernel: audit(1158006870.112:18): avc:
granted { execmem } for pid=2432 comm="nautilus"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Sep 11 16:34:51 dhcp-152-3-194-19 kernel: audit(1158006891.041:19): avc:
granted { execstack } for pid=2486 comm="xscreensaver-gl"
scontext=user_u:system_r:unconfined t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Sep 11 16:34:51 dhcp-152-3-194-19 kernel: audit(1158006891.041:20): avc:
granted { execmem } for pid=2486 comm="xscreensaver-gl"
scontext=user_u:system_r:unconfined_t:s0
tcontext=user_u:system_r:unconfined_t:s0 tclass=process
Sep 11 16:53:11 dhcp-152-3-194-19 syslogd 1.4.1: restart.
Sep 11 16:53:12 dhcp-152-3-194-19 kernel: klogd 1.4.1, log source =
/proc/kmsg started.
Sep 11 16:53:12 dhcp-152-3-194-19 kernel: Linux version
2.6.15-1.2054_FC5smp (bhcompile@hs20-bc1-3.build.redhat.com) (gcc version
4.1.0 20060304 (Red Hat 4.1.0-3)) #1 SMP Tue Mar 14 16:05:46 EST 2006
Sep 11 16:53:12 dhcp-152-3-194-19 kernel: BIOS-provided physical RAM map:
Sep 11 16:53:12 dhcp-152-3-194-19 kernel: BIOS-e820: 0000000000000000 -
00000000000a0000 (usable)
....
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Re: system freezes while using Mozilla
am 12.09.2006 06:55:06 von Ray Olszewski
This won't be of direct help to you, Karthik, but I've been seeing this
same problem running Firefox 1.5.0.6 (the current version for all
platforms, according to Firefox ... I assume you meant to write 1.5.0.1
so are a bit back) on my Windows 2000 workstation.
In my case, the additional details are that the mouse continues to work
for a bit, at least for moving the pointer, though I can't get anything
to respond to clicks. After a few clicks, the machine becomes totally
unresponsive at the UI (though I haven't checked response over the LAN)
and requires a power-cycle reset) ... I've surmised that the event queue
gets filled up because Firefox is not responding to mouse events.
I only mention it because of the possibility that we're both seeing a
Firefox problem, once that is platform independent but associated with
relatively recent versions of Firefox.
Karthik Vishwanath wrote:
> Hello,
>
> I recently installed Fedora core 5 on an intel dual-core CPU box. The
> machine froze up while running gnome2 while I was engaged in simple
> browsing activity using firefox 1.5.01.
>
> The "freezing" occurred twice one after the other and during both these
> instances I was using firefox to browse the web (while having at least 2-4
> firefox tabs open). The machine froze up in both instances and did not
> respond to the keyboard/mouse or to a remote login/ping. I checked
> /var/log/messages just before the "restart" line and did not find any
> unusual entries (+/-5 lines around the restart lines from
> /var/log/messages is included below).
>
> I was wondering if:
> (a) this matched any known issue with FC5 and intel hardware
> (b) if there was any way that I could _recover_ control upon a system
> freeze such as this?
>
> All responses are appreciated.
>
>
> Thanks,
>
> -K
>
> ---------
> lines from /var/log/messages:
>
> ...
> Sep 11 15:23:19 dhcp-152-3-194-19 dhclient: DHCPREQUEST on eth0 to
> 152.3.17.193 port 67
> Sep 11 15:23:19 dhcp-152-3-194-19 dhclient: DHCPACK from 152.3.17.193
> Sep 11 15:23:19 dhcp-152-3-194-19 dhclient: bound to 152.3.194.19 --
> renewal in 3162 seconds.
> Sep 11 16:16:01 dhcp-152-3-194-19 dhclient: DHCPREQUEST on eth0 to
> 152.3.17.193 port 67
> Sep 11 16:16:01 dhcp-152-3-194-19 dhclient: DHCPACK from 152.3.17.193
> Sep 11 16:16:01 dhcp-152-3-194-19 dhclient: bound to 152.3.194.19 --
> renewal in 3472 seconds.
> Sep 11 16:32:19 dhcp-152-3-194-19 syslogd 1.4.1: restart.
> Sep 11 16:32:20 dhcp-152-3-194-19 kernel: klogd 1.4.1, log source =
> /proc/kmsg started.
> Sep 11 16:32:20 dhcp-152-3-194-19 kernel: Linux version
> 2.6.15-1.2054_FC5smp (bhcompile@hs20-bc1-3.build.redhat.com) (gcc version
> 4.1.0 20060304 (Red Hat 4.1.0-3)) #1 SMP Tue Mar 14 16:05:46 EST 2006
> Sep 11 16:32:20 dhcp-152-3-194-19 kernel: BIOS-provided physical RAM map:
> Sep 11 16:32:20 dhcp-152-3-194-19 kernel: BIOS-e820: 0000000000000000 -
> 00000000000a0000 (usable)
>
> ...
>
> Sep 11 16:34:30 dhcp-152-3-194-19 kernel: audit(1158006870.112:18): avc:
> granted { execmem } for pid=2432 comm="nautilus"
> scontext=user_u:system_r:unconfined_t:s0
> tcontext=user_u:system_r:unconfined_t:s0 tclass=process
> Sep 11 16:34:51 dhcp-152-3-194-19 kernel: audit(1158006891.041:19): avc:
> granted { execstack } for pid=2486 comm="xscreensaver-gl"
> scontext=user_u:system_r:unconfined t:s0
> tcontext=user_u:system_r:unconfined_t:s0 tclass=process
> Sep 11 16:34:51 dhcp-152-3-194-19 kernel: audit(1158006891.041:20): avc:
> granted { execmem } for pid=2486 comm="xscreensaver-gl"
> scontext=user_u:system_r:unconfined_t:s0
> tcontext=user_u:system_r:unconfined_t:s0 tclass=process
> Sep 11 16:53:11 dhcp-152-3-194-19 syslogd 1.4.1: restart.
> Sep 11 16:53:12 dhcp-152-3-194-19 kernel: klogd 1.4.1, log source =
> /proc/kmsg started.
> Sep 11 16:53:12 dhcp-152-3-194-19 kernel: Linux version
> 2.6.15-1.2054_FC5smp (bhcompile@hs20-bc1-3.build.redhat.com) (gcc version
> 4.1.0 20060304 (Red Hat 4.1.0-3)) #1 SMP Tue Mar 14 16:05:46 EST 2006
> Sep 11 16:53:12 dhcp-152-3-194-19 kernel: BIOS-provided physical RAM map:
> Sep 11 16:53:12 dhcp-152-3-194-19 kernel: BIOS-e820: 0000000000000000 -
> 00000000000a0000 (usable)
> ...
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs