seth vidal wrote:
On Mon, 2008-10-27 at 15:56 +0200, shmuel siegel wrote:
> seth vidal wrote:
>
>> On Mon, 2008-10-27 at 13:28 +0200, shmuel siegel wrote:
>>
>>
>>> As Red Skeleton was known to say, "I just do them, I don't explain
>>> them". I have noticed more than once that x freezes if I am playing
>>> freecell while running "sudo yum update" from a gnome terminal. I
have
>>> not had X freeze in any other scenario. The symptoms of the freeze are:
>>>
>>> 1. yum is downloading at the time
>>> 2. It happens while I am dragging a card - the motion freezesa
>>> 3. The mouse still moves but none of the rollovers do anything and
>>> clicking doesn't have any effect
>>> 4. The keyboard doesn't have any effect. Not even ctrl-alt-del,
>>> ctrl-alt-f2, or ctrl-alt-backspace
>>> 5. The gnome monitor panel applet freezes
>>> 6. ssh works. I can log in from another machine
>>> 7. /sbin/init 3 doesn't do anything
>>>
>>> I am running F10 rawhide on a Dell Latitude D620 - integrated Intel
>>> graphics chip.
>>>
>>>
>> How much memory do you have in the system?
>>
>> -sv
>>
>>
> One Gig of ram and at least 6 gig free on vars partition. If it happens
> again I check how ram is used.
>
and type 'dmesg' and look for OOM or Out-of-Memory in the output.
-sv
Sorry I took so long, but the problem had to occur again before I could
post anything. It should be noted that the system is still running and
the disk drive is accessible.
No out of memory messages but I do have the following entries, probably
relevant.
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: status: { DRDY ERR }
ata2.00: qc timeout (cmd 0xa0)
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
ata2.00: status: { DRDY ERR }
ata2: link is slow to respond, please be patient (ready=0)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting link
ata2.00: configured for UDMA/25
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: status: { DRDY ERR }
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
res 51/04:01:01:60:00/00:00:00:00:00/a0 Emask 0x1 (device error)
ata2.00: status: { DRDY ERR }
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
res 58/00:02:00:12:00/00:00:00:00:00/a0 Emask 0x2 (HSM violation)
ata2.00: status: { DRDY DRQ }
ata2: soft resetting link
ata2.00: configured for UDMA/25
ata2: EH complete