10:05 a.m.
Hello,
In average, once a day my gnome session freezes. Only one option,
open a text session and try to kill the gnome-session!
Any idea how to debug this?
Thank.
--
======================================================================
Patrick DUPRÉ | | email: pdupre(a)kegtux.org
Laboratoire de Physico-Chimie de l'Atmosphère
Université du Littoral-Côte d'Opale
Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
======================================================================
9:35 a.m.
On 24 March 2013 10:42, Frank Murphy <frankly3d(a)gmail.com> wrote:
On Sun, 24 Mar 2013 10:36:21 +0000
Ian Malone <ibmalone(a)gmail.com> wrote:
> [15523.867808] ata3: EH in SWNCQ mode,QC:qc_active 0x7 sactive 0x7
> [15523.867822] ata3: SWNCQ:qc_active 0x1 defer_bits 0x6
> last_issue_tag 0x0 dhfis 0x1 dmafis 0x1 sdbfis 0x0
> [15523.867834] ata3: ATA_REG 0x40 ERR_REG 0x0
> [15523.867840] ata3: tag : dhfis dmafis sdbfis sactive
> [15523.867846] ata3: tag 0x0: 1 1 0 1
> [15523.867868] ata3.00: exception Emask 0x0 SAct 0x7 SErr 0x0
> action 0x6 frozen [15523.867876] ata3.00: failed command: WRITE
> FPDMA QUEUED [15523.867891] ata3.00: cmd
> 61/08:00:80:6b:c3/00:00:1d:00:00/40 tag 0 ncq 4096 out
> (before anyone asks, BZ #917826)
>
try the disk on another controller.
see if it's repeated.
Yes, finally getting around to doing that. Hadn't previously (though
had tried other things, changing cables etc.) as the previous disc on
that port had no problems and Windows on the same system is okay. Have
occassionally thought it was fixed, but very infrequent and can be a
long time between occurences.
--
imalone
http://ibmalone.blogspot.co.uk
5:42 a.m.
On Sun, 24 Mar 2013 10:36:21 +0000
Ian Malone <ibmalone(a)gmail.com> wrote:
[15523.867808] ata3: EH in SWNCQ mode,QC:qc_active 0x7 sactive 0x7
[15523.867822] ata3: SWNCQ:qc_active 0x1 defer_bits 0x6
last_issue_tag 0x0 dhfis 0x1 dmafis 0x1 sdbfis 0x0
[15523.867834] ata3: ATA_REG 0x40 ERR_REG 0x0
[15523.867840] ata3: tag : dhfis dmafis sdbfis sactive
[15523.867846] ata3: tag 0x0: 1 1 0 1
[15523.867868] ata3.00: exception Emask 0x0 SAct 0x7 SErr 0x0
action 0x6 frozen [15523.867876] ata3.00: failed command: WRITE
FPDMA QUEUED [15523.867891] ata3.00: cmd
61/08:00:80:6b:c3/00:00:1d:00:00/40 tag 0 ncq 4096 out
(before anyone asks, BZ #917826)
try the disk on another controller.
see if it's repeated.
--
Regards,
Frank
http//www.frankly3d.com
5:36 a.m.
On 24 March 2013 03:47, Richard Vickery <richard.vickeryrv(a)gmail.com> wrote:
On Fri, Mar 22, 2013 at 2:55 PM, Ian Malone
<ibmalone(a)gmail.com> wrote:
>
> On 22 March 2013 15:05, Patrick Dupre <pdupre(a)kegtux.org> wrote:
> > Hello,
> >
> > In average, once a day my gnome session freezes. Only one option,
> > open a text session and try to kill the gnome-session!
> >
> > Any idea how to debug this?
> >
>
> Run top and see what's going on. Should help answer the 'not enough
> resources' question. If gnome is using 100% CPU something is wrong. If
> something else is then it's probably an application run amok. See if
> dmesg shows anything unusual in recent events after a freeze.
How would I recognise a freeze and the events after such?
A freeze isn't a specific techinical problem. Currently my desktop
freezes very occassionally for a short time, and has nothing to do
with insufficient system resources. Afterwards I'll see something like
this in dmesg
[15523.867808] ata3: EH in SWNCQ mode,QC:qc_active 0x7 sactive 0x7
[15523.867822] ata3: SWNCQ:qc_active 0x1 defer_bits 0x6 last_issue_tag 0x0
dhfis 0x1 dmafis 0x1 sdbfis 0x0
[15523.867834] ata3: ATA_REG 0x40 ERR_REG 0x0
[15523.867840] ata3: tag : dhfis dmafis sdbfis sactive
[15523.867846] ata3: tag 0x0: 1 1 0 1
[15523.867868] ata3.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x6 frozen
[15523.867876] ata3.00: failed command: WRITE FPDMA QUEUED
[15523.867891] ata3.00: cmd 61/08:00:80:6b:c3/00:00:1d:00:00/40 tag 0
ncq 4096 out
(before anyone asks, BZ #917826)
dmesg reports things in chronological order and with a timestamp, so
if there's a recent event connected to the freeze it's fairly apparent
from the jump in timestamps after startup and login events. If the
problem is an application hogging resources then top will help find
it. If neither of these provide any useful information then
/var/log/messages contains a bit more information than dmesg and can
be worth checking. If none of those show anything suspicious, or at
least associated in timing, then the desktop itself is the top suspect
remaining.
--
imalone
http://ibmalone.blogspot.co.uk
10:47 p.m.
On Fri, Mar 22, 2013 at 2:55 PM, Ian Malone <ibmalone(a)gmail.com> wrote:
On 22 March 2013 15:05, Patrick Dupre <pdupre(a)kegtux.org>
wrote:
> Hello,
>
> In average, once a day my gnome session freezes. Only one option,
> open a text session and try to kill the gnome-session!
>
> Any idea how to debug this?
>
Run top and see what's going on. Should help answer the 'not enough
resources' question. If gnome is using 100% CPU something is wrong. If
something else is then it's probably an application run amok. See if
dmesg shows anything unusual in recent events after a freeze.
How would I recognise a freeze and the events after such?
4:55 p.m.
On 22 March 2013 15:05, Patrick Dupre <pdupre(a)kegtux.org> wrote:
Hello,
In average, once a day my gnome session freezes. Only one option,
open a text session and try to kill the gnome-session!
Any idea how to debug this?
Run top and see what's going on. Should help answer the 'not enough
resources' question. If gnome is using 100% CPU something is wrong. If
something else is then it's probably an application run amok. See if
dmesg shows anything unusual in recent events after a freeze.
--
imalone
http://ibmalone.blogspot.co.uk
12:48 p.m.
On Fri, Mar 22, 2013 at 11:27 AM, Patrick Dupre <pdupre(a)kegtux.org> wrote:
On 2013-03-22 17:15, Dale Dellutri wrote:
>
> On Fri, Mar 22, 2013 at 10:05 AM, Patrick Dupre <pdupre(a)kegtux.org> wrote:
>>
>> Hello,
>>
>> In average, once a day my gnome session freezes. Only one option,
>> open a text session and try to kill the gnome-session!
>>
>> Any idea how to debug this?
>
>
> If this is a limited resource problem, then you'll need to run
> something which
> logs resource usage. sysstat can do this and puts results in /var/log/sa.
ls -lS /var/log/sa
total 5628
-rw-r--r--. 1 root root 215628 Mar 22 17:20 sa22
-rw-r--r--. 1 root root 285923 Mar 21 23:53 sar21
-rw-r--r--. 1 root root 295548 Mar 21 23:50 sa21
-rw-r--r--. 1 root root 284591 Mar 20 23:53 sar20
But they are not ascii files.
The ones marked sa<nn> are data files, and the sar<nn> are ascii
report files. Try file on them.
Also see
man sar
and the info at
http://sebastien.godard.pagesperso-orange.fr/
You need to educate yourself about sysstat.
> If this is some kind of X error, look in /var/log/Xorg.0.log or
> /var/log/Xorg.0.log.old.
Nothing seems wrong in these files.
>>
>> Thank.
>>
>> --
>>
>> ======================================================================
>> Patrick DUPRÉ | | email: pdupre(a)kegtux.org
>> Laboratoire de Physico-Chimie de l'Atmosphère
>> Université du Littoral-Côte d'Opale
>> Fax: 03 28 65 82 44
>> 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
>>
>> ======================================================================
>> --
>> users mailing list
>> users(a)lists.fedoraproject.org
>> To unsubscribe or change subscription options:
>> https://admin.fedoraproject.org/mailman/listinfo/users
>> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>> Have a question? Ask away: http://ask.fedoraproject.org
>
>
>
>
> --
> Dale Dellutri
--
======================================================================
Patrick DUPRÉ | | email: pdupre(a)kegtux.org
Laboratoire de Physico-Chimie de l'Atmosphère
Université du Littoral-Côte d'Opale
Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
======================================================================
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
--
Dale Dellutri
11:27 a.m.
On 2013-03-22 17:15, Dale Dellutri wrote:
On Fri, Mar 22, 2013 at 10:05 AM, Patrick Dupre
<pdupre(a)kegtux.org>
wrote:
> Hello,
>
> In average, once a day my gnome session freezes. Only one option,
> open a text session and try to kill the gnome-session!
>
> Any idea how to debug this?
If this is a limited resource problem, then you'll need to run
something which
logs resource usage. sysstat can do this and puts results in
/var/log/sa.
ls -lS /var/log/sa
total 5628
-rw-r--r--. 1 root root 215628 Mar 22 17:20 sa22
-rw-r--r--. 1 root root 285923 Mar 21 23:53 sar21
-rw-r--r--. 1 root root 295548 Mar 21 23:50 sa21
-rw-r--r--. 1 root root 284591 Mar 20 23:53 sar20
But they are not ascii files.
If this is some kind of X error, look in /var/log/Xorg.0.log or
/var/log/Xorg.0.log.old.
Nothing seems wrong in these files.
>
> Thank.
>
> --
>
> ======================================================================
> Patrick DUPRÉ | | email: pdupre(a)kegtux.org
> Laboratoire de Physico-Chimie de l'Atmosphère
> Université du Littoral-Côte d'Opale
> Fax: 03 28 65 82 44
> 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
>
> ======================================================================
> --
> users mailing list
> users(a)lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
--
Dale Dellutri
--
======================================================================
Patrick DUPRÉ | | email: pdupre(a)kegtux.org
Laboratoire de Physico-Chimie de l'Atmosphère
Université du Littoral-Côte d'Opale
Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
======================================================================
11:15 a.m.
On Fri, Mar 22, 2013 at 10:05 AM, Patrick Dupre <pdupre(a)kegtux.org> wrote:
Hello,
In average, once a day my gnome session freezes. Only one option,
open a text session and try to kill the gnome-session!
Any idea how to debug this?
If this is a limited resource problem, then you'll need to run something which
logs resource usage. sysstat can do this and puts results in /var/log/sa.
If this is some kind of X error, look in /var/log/Xorg.0.log or
/var/log/Xorg.0.log.old.
Thank.
--
======================================================================
Patrick DUPRÉ | | email: pdupre(a)kegtux.org
Laboratoire de Physico-Chimie de l'Atmosphère
Université du Littoral-Côte d'Opale
Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
======================================================================
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
--
Dale Dellutri
11:06 a.m.
On Fri, 22 Mar 2013 16:56:06 +0100
Patrick Dupre wrote:
Frozen means, the mouse works but every thing else is frozen: all the
displays in the top panel,
no way to graphically interact.
Do way to move to another workspace. Fortunately Ctl F2 works.
It usually happens when I change of workspace.
It way be a graphics issue!
I have a freeze with different symptoms. For me switching to
a console also doesn't work, and the mouse is frozen as well.
But, if I wait a bit (somewhere between 3 minutes and 10 seconds)
it all comes back to life.
This only happens on my system at work, not at home
(both running up to date f18 64 bit). I tend to suspect
the radeon driver since my work system has a radeon card.
There is never any indication in any log files that
anything happened.
10:56 a.m.
On 2013-03-22 16:36, Richard Vickery wrote:
On Mar 22, 2013 8:06 AM, "Patrick Dupre"
<pdupre(a)kegtux.org [1]>
wrote:
>
> Hello,
>
> In average, once a day my gnome session freezes. Only one option,
> open a text session and try to kill the gnome-session!
>
> Any idea how to debug this?
>
> Thank.
>
> --
>
======================================================================
> Patrick DUPRÉ | | email:
pdupre(a)kegtux.org [2]
> Laboratoire de Physico-Chimie de lAtmosphère
> Université du Littoral-Côte dOpale
> Fax: 03 28 65 82 44
> 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
>
======================================================================
> --
> users mailing list
> users(a)lists.fedoraproject.org [3]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users [4]
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
[5]
> Have a question? Ask away: http://ask.fedoraproject.org [6]
What exactly do you mean by "debug"? A freeze means that the OS is
using too many resources. You could possibly go in and shut down some
programs, but the system may need these to keep running.
You could get a faster computer, or more RAM, else there is no fix
for
a freeze, as far as I am aware. Though I too experience freezes in
f18.
I have 4 processors at 3.2 GHz and 8Go of RAM, what else?
Frozen means, the mouse works but every thing else is frozen: all the
displays in the top panel,
no way to graphically interact.
Do way to move to another workspace. Fortunately Ctl F2 works.
It usually happens when I change of workspace.
It way be a graphics issue!
Links:
------
[1] mailto:pdupre@kegtux.org
[2] mailto:pdupre@kegtux.org
[3] mailto:users@lists.fedoraproject.org
[4] https://admin.fedoraproject.org/mailman/listinfo/users
[5] http://fedoraproject.org/wiki/Mailing_list_guidelines
[6] http://ask.fedoraproject.org
--
======================================================================
Patrick DUPRÉ | | email: pdupre(a)kegtux.org
Laboratoire de Physico-Chimie de l'Atmosphère
Université du Littoral-Côte d'Opale
Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
======================================================================
10:36 a.m.
On Mar 22, 2013 8:06 AM, "Patrick Dupre" <pdupre(a)kegtux.org> wrote:
Hello,
In average, once a day my gnome session freezes. Only one option,
open a text session and try to kill the gnome-session!
Any idea how to debug this?
Thank.
--
======================================================================
Patrick DUPRÉ | | email: pdupre(a)kegtux.org
Laboratoire de Physico-Chimie de l'Atmosphère
Université du Littoral-Côte d'Opale
Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
======================================================================
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
What exactly do you mean by "debug"? A freeze means that the OS is using
too many resources. You could possibly go in and shut down some programs,
but the system may need these to keep running.
You could get a faster computer, or more RAM, else there is no fix for a
freeze, as far as I am aware. Though I too experience freezes in f18.
4077
days inactive
4079
days old
11 comments
6 participants
participants (6)
-
Dale Dellutri -
Frank Murphy -
Ian Malone -
Patrick Dupre -
Richard Vickery -
Tom Horsley