[opensuse] ata3.00:,exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Hi All Motherboard: ASUS P5VD2-MX SE (BIOS 0602) DVD: TSSTCorp SH-S128D Hard drive: 320GB SATA1 Maxtor STM33320820AS Pentium(R) D CPU 3.20GHz, Cores: 2 Linux 2.6.22.13-0.3-default x86_64 System: openSUSE 10.3 (x86_64) KDE: 3.5.7 "release 72.2" Model: GeForce 7300 GS I've recently upgraded to 10.3 with a full/new install from a previously fully functional 10.2 (no hardware changed during the upgrade). I'm now getting a significant run of "ata3.00:exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen" error messages. The effect is such that, for example, if I don't start VirtualBox immediately, after booting the system, it just hangs ... The relevant part of dmesg are (with multiple occurrences of): " ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata3.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x1a data 255 in res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata3: soft resetting link ata3.00: configured for PIO0 ata3: EH complete " plus, the occasional: " sr0: CDROM (ioctl) error, command: Test Unit Ready 00 00 00 00 00 00 sr: Sense Key : Aborted Command [current] [descriptor] sr: Add. Sense: No additional sense information " The configuration for the drive starts with "UDMA/33" and slowly deteriorates to "PIO0". Following one prompt, in dmesg, I tried editing /etc/smartd.conf to uncomment "/dev/sda -a -d sat". But no luck ... the "frozen" message continues ... I've done a major Google around this topic and can find no obvious consistency with the potential cause or solution; it appears independent of hardware/software/Linux version/drivers/... I initially though the problem was with EXT3 journalling (as the impact appears to increases over time - but I cannot fathom how to force a check of EXT3 at boot). If I try to run "Repair Installed System", from the original installation DVD, it just reboots ... I'm lost for a solution ... Further information: "/sbin/lspci | grep IDE" gives: " 00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07) " Has anybody solved this for OpenSUSE Linux 2.6.22, or can help me investigate it further ... Cheers B -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Brian Green (NET) wrote:
Hi All
[snip]
I've recently upgraded to 10.3 with a full/new install from a previously fully functional 10.2 (no hardware changed during the upgrade). I'm now getting a significant run of "ata3.00:exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen" error messages.
[snip] ... I initially though the
problem was with EXT3 journalling (as the impact appears to increases over time - but I cannot fathom how to force a check of EXT3 at boot). If I try to run "Repair Installed System", from the original installation DVD, it just reboots ...
I'm lost for a solution ...
[snip]
Has anybody solved this for OpenSUSE Linux 2.6.22, or can help me investigate it further ...
Cheers
B
It was the EXT3 journal for my root partition /dev/sda1: init 1 umount /dev/sda1 fsck.ext3 /dev/sda1 and then a reboot ... The "ata3.00: ... frozen" error message has stopped and I can run VirtualBox again ... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-12-07 at 23:15 -0000, Brian Green (NET) wrote:
over time - but I cannot fathom how to force a check of EXT3 at boot).
touch /forcefsck - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHXogytTMYHG2NR9URAtHxAKCHQVDp68LIrWykqdOFSiYnzaSyswCgkFDf d9W5ge7JfnP5Q83qFsDf2MQ= =H1sW -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Brian Green (NET) escribió:
Has anybody solved this for OpenSUSE Linux 2.6.22, or can help me investigate it further ...
https://bugzilla.novell.com/show_bug.cgi?id=340126 it is a libata issue. -- "The only thing that interferes with my learning is my education." - Albert Einstein Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Cristian Rodríguez wrote:
Brian Green (NET) escribió:
Has anybody solved this for OpenSUSE Linux 2.6.22, or can help me investigate it further ...
https://bugzilla.novell.com/show_bug.cgi?id=340126
it is a libata issue.
Hi Cristian Yeah! I added to your bugzilla notes after I raised it here. However, my occurrence of the "ata1.00: exception ... frozen" error message has completely stopped after I fsck.ext3 my EXT3 journal for my root partition: /dev/sda1 (see my earlier contribution to this thread). However, I'm not aware of what I did to corrupt the journal in the first instance - a fresh installation with a full set of updates, but no crashes. Nor have I identified why the journal wasn't flagged as being corrupted and the cause for the error message ... was my occurrence a libata issue also? B. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Brian Green (NET) wrote:
Hi All
[snip]
I've recently upgraded to 10.3 with a full/new install from a previously fully functional 10.2 (no hardware changed during the upgrade). I'm now getting a significant run of "ata3.00:exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen" error messages.
[snip]
The relevant part of dmesg are (with **MANY** occurrences of):
" ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata3.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x1a data 255 in res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata3: soft resetting link ata3.00: configured for PIO0 ata3: EH complete "
plus, the occasional:
" sr0: CDROM (ioctl) error, command: Test Unit Ready 00 00 00 00 00 00 sr: Sense Key : Aborted Command [current] [descriptor] sr: Add. Sense: No additional sense information "
The configuration for the drive starts with "UDMA/33" and slowly deteriorates to "PIO0".
Following one prompt, in dmesg, I tried editing /etc/smartd.conf to uncomment "/dev/sda -a -d sat". But no luck ... the "frozen" message continues ...
[snip]
I'm lost for a solution ...
I thought it was resolved (after "fsch.ext3" on my root partition - I was without the error message for a very long time). Then I did an update and the "ata3.00: exception Emask ... frozen" messages have returned. In an attempt to resolve it I've: 1) in the BIOS, disabled the SMART monitoring of the hard drive 2) fsch.ext3 all the partitions (as init 1 - the're all "clean") 3) checked all the partitions for badblocks (there's none) 4) even tried leaving a CD in my DVD drive ... So, am I suffering from the "libata: constant ata1.00: exception Emask 0x2 SAct 0x3f00f SErr 0x0 action 0x2 frozen" - bug (https://bugzilla.novell.com/show_bug.cgi?id=340126)? Cristian says that bug has been fixed in 2.6.22.15 - so I do wait for that (I'm currently on 2.6.22.13). Or, have I go some other bug/intolerance ... Can somebody give me a starter/some pointers?
Cheers
Brian
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 17 December 2007 14:30:06 Brian Green (NET) wrote:
Brian Green (NET) wrote:
Hi All
[snip]
I've recently upgraded to 10.3 with a full/new install from a previously fully functional 10.2 (no hardware changed during the upgrade). I'm now getting a significant run of "ata3.00:exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen" error messages.
[snip]
The relevant part of dmesg are (with **MANY** occurrences of):
" ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata3.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x1a data 255 in res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata3: soft resetting link ata3.00: configured for PIO0 ata3: EH complete "
plus, the occasional:
" sr0: CDROM (ioctl) error, command: Test Unit Ready 00 00 00 00 00 00 sr: Sense Key : Aborted Command [current] [descriptor] sr: Add. Sense: No additional sense information "
The configuration for the drive starts with "UDMA/33" and slowly deteriorates to "PIO0".
Following one prompt, in dmesg, I tried editing /etc/smartd.conf to uncomment "/dev/sda -a -d sat". But no luck ... the "frozen" message continues ...
[snip]
I'm lost for a solution ...
I thought it was resolved (after "fsch.ext3" on my root partition - I was without the error message for a very long time). Then I did an update and the "ata3.00: exception Emask ... frozen" messages have returned.
In an attempt to resolve it I've:
1) in the BIOS, disabled the SMART monitoring of the hard drive 2) fsch.ext3 all the partitions (as init 1 - the're all "clean") 3) checked all the partitions for badblocks (there's none) 4) even tried leaving a CD in my DVD drive ...
So, am I suffering from the "libata: constant ata1.00: exception Emask 0x2 SAct 0x3f00f SErr 0x0 action 0x2 frozen" - bug (https://bugzilla.novell.com/show_bug.cgi?id=340126)? Cristian says that bug has been fixed in 2.6.22.15 - so I do wait for that (I'm currently on 2.6.22.13). Or, have I go some other bug/intolerance ...
Can somebody give me a starter/some pointers?
Cheers
Brian
Dear Brian, I have noticed that in my system the messages only appear when I introduce a CD or DVD. I am using opensuse 10.3 with a P5W DH motherboard. Best regards, Rafael -- Dr. Rafael R. Pappalardo Dept. Physical Chemistry, Univ. de Sevilla (Spain) e-mail: rafapa@us.es -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rafael R. Pappalardo wrote:
On Monday 17 December 2007 14:30:06 Brian Green (NET) wrote:
Brian Green (NET) wrote:
Hi All [snip]
[snip]
In an attempt to resolve it I've:
1) in the BIOS, disabled the SMART monitoring of the hard drive 2) fsch.ext3 all the partitions (as init 1 - the're all "clean") 3) checked all the partitions for badblocks (there's none) 4) even tried leaving a CD in my DVD drive ...
So, am I suffering from the "libata: constant ata1.00: exception Emask 0x2 SAct 0x3f00f SErr 0x0 action 0x2 frozen" - bug (https://bugzilla.novell.com/show_bug.cgi?id=340126)? Cristian says that bug has been fixed in 2.6.22.15 - so I do wait for that (I'm currently on 2.6.22.13). Or, have I go some other bug/intolerance ...
Can somebody give me a starter/some pointers?
Cheers
Brian
Dear Brian, I have noticed that in my system the messages only appear when I introduce a CD or DVD. I am using opensuse 10.3 with a P5W DH motherboard.
Best regards,
Rafael
Hi Rafael Other than: " sr0: CDROM not ready. Make sure there is a disc in the drive. " in the log file at boot-up, I've *completely* stopped the message by: a) Adding "irqpoll" to the command line b) Disabling smartd in system services Not, yet had time to see if irqpoll alone will staunch the error message (obviously disabling smartd would ...) I'll try unpacking these fixes when I've installed 2.6.22.15 ... Brian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Brian Green (NET) -
Carlos E. R. -
Cristian Rodríguez -
Rafael R. Pappalardo