Bug 215170

I got a similar error even running on console mode, before the freeze, the 
message "bus error" appear and the system freeze. my system is also affected 
for the anaconda bug https://bugzilla.redhat.com/bugzilla/
show_bug.cgi?id=211941, with fedora5 there is no problem.

Pentium4 3Ghz
GeForce4 MX 4000
Biostar P4M80-M4(3 PCI, 1 AGP, 1 CNR, 2 DDR DIMM, Audio, Video, LAN)

     

Created attachment 140980 [details]
hardware info

track the error to my sata drive, 
Barracuda 7200.9 SATA ST3160812AS  (160 GB, 7200 RPM, SATA-II) before the system
freeze 

syslog report:
 
kernel ata1.00:	execption Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
kernel ata1.00:	(BMDMA stat 0x24)
kernel ata1.00:	tag 0 cmd 0xca Emask 0x4 stat 0x40 err 0x0 (timeout)
kernel ata1: 	SATA link up 1.5Gbps (SStatus 113 Scontrol 300)
kernel ata1: 	soft resetting port
kernel ata1.00:	qc timeout(cmd 0xec)
kernel ata1.00:	failed to IDENTIFY (I/0 error, err_maks= 0x4)
kernel ata1.00:	revalidation failed (errno =.5)
kernel ata1:	failed to recover some devices, retriying in 5 secs
kernel ata1: 	SATA link up 1.5Gbps (SStatus 113 Scontrol 300)
kernel ata1: 	soft resetting port
kernel ata1.00:	disable
kernel ata1	EH complete
sd 0:0:0:0 SCSI error: return code = 0x00040000

Created attachment 141153 [details]
My Xorg.0.log

Created attachment 141154 [details]
My messages

Created attachment 141155 [details]
My secure

Created attachment 141156 [details]
My dmesg

I attached some logs in case they are of any use... I'm really a beginner with
Linux.  I don't want to give up on it but this bug is making things very
difficult for me so any help or suggestions are greatly appreciated!

Have you tried to replug the cables from the hard-disk and the motherboard
(power and as well the SATA ones)? 

Nikki's bug isn't the sata thing.  The seems like a problem in the Rt61 wireless
driver.  It seems to be open source but I think it's an out of tree module from
Ralink.

Aah!  T(In reply to comment #10)
> Nikki's bug isn't the sata thing.  The seems like a problem in the Rt61 wireless
> driver.  It seems to be open source but I think it's an out of tree module from
> Ralink.

Ooh... that would make sense.  It seems to happen when I'm using things that
access the Internet and I've been noticing it a lot when running the software
updater.  I used the RT61 thingy from RT2X00.serialmonkey.com because I couldn't
get the driver I downloaded directly from Ralink to work.

(In reply to comment #9)
> Have you tried to replug the cables from the hard-disk and the motherboard
> (power and as well the SATA ones)? 

yes i did, the problem is not resolved, i looks like a bug in the sata driver, 
fedora core 5 never freeze and was installed on the same drive before i changed
to fedora 6 with a fresh install   

Nikki, the bad news is that ralink is going to have to fix the bug instead of
Fedora.  If you showed them your /var/log/messages they _should_ be able to fix
it pretty easily.

(In reply to comment #13)
> Nikki, the bad news is that ralink is going to have to fix the bug instead of
> Fedora.  If you showed them your /var/log/messages they _should_ be able to fix
> it pretty easily.

Well, it's a point in the right direction.  Thanks!  I will get in touch with
them.  :)

i search in google about problem and appears the system freeze with certain sata
hardrive model barracuda Seagate the kernel send this messages 

kernel: ATA: abnormal status 0x7F on port 0xB407
kernel:   Vendor: ATA       Model: ST3160812AS       Rev: 3.AA

message post by someone with similar problem
http://groups.google.com.ni/group/lucky.linux.kernel/browse_thread/thread/d533b878a25a2557/85af5d3780e95c35?lnk=st&q=+kernel%3A+ATA%3A+abnormal+status+0x7F+on+port+0xB407&rnum=3&hl=es#85af5d3780e95c35

(This is a mass-update to all current FC6 kernel bugs in NEW state)

Hello,

I'm reviewing this bug list as part of the kernel bug triage project, an attempt
to isolate current bugs in the Fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug, however this version of Fedora is no longer
maintained.

Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.

Thanks for using Fedora!

Per the previous comment in this bug, I am closing it as INSUFFICIENT_DATA,
since no information has been lodged for over 30 days.

Please re-open this bug or file a new one if you can provide the requested data,
and thanks for filing the original report!