[opensuse] Can anyone interpret this error message
I had this message frequently in 10.3/x6_64 and local opinion was a failing disk. Changed disk, build 11.0b3 and it reappeared so changed IDE cable and it stopped -- for two days and then came back after a reboot for the new kernel, about every 4 mins or so. I looked via Google and it seems that it occurs but I did not find an explanation. Currently running Linux xenakis 2.6.25.4-6-default #1 SMP 2008-05-23 14:08:04 +0200 x86_64 x86_64 x86_64 GNU/Linux with one ide disk and a pair or RAIDed sata disks. ==John ffitch ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 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 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata2.00: status: { DRDY } ata2: soft resetting link ata2.00: configured for PIO0 ata2.01: configured for PIO0 ata2: EH complete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, May 28, 2008 at 8:53 AM, jpff <jpff@codemist.co.uk> wrote:
I had this message frequently in 10.3/x6_64 and local opinion was a failing disk. Changed disk, build 11.0b3 and it reappeared so changed IDE cable and it stopped -- for two days and then came back after a reboot for the new kernel, about every 4 mins or so. I looked via Google and it seems that it occurs but I did not find an explanation. Currently running Linux xenakis 2.6.25.4-6-default #1 SMP 2008-05-23 14:08:04 +0200 x86_64 x86_64 x86_64 GNU/Linux with one ide disk and a pair or RAIDed sata disks. ==John ffitch
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 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 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata2.00: status: { DRDY } ata2: soft resetting link ata2.00: configured for PIO0 ata2.01: configured for PIO0 ata2: EH complete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
It seemes like a controller problem to me, rather than a disk problem. Why is is using PIO? Do you have the proper 80 pin cables? -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, May 28, 2008 at 3:38 PM, John Andersen <jsamyth@gmail.com> wrote:
On Wed, May 28, 2008 at 8:53 AM, jpff <jpff@codemist.co.uk> wrote:
I had this message frequently in 10.3/x6_64 and local opinion was a failing disk. Changed disk, build 11.0b3 and it reappeared so changed IDE cable and it stopped -- for two days and then came back after a reboot for the new kernel, about every 4 mins or so. I looked via Google and it seems that it occurs but I did not find an explanation. Currently running Linux xenakis 2.6.25.4-6-default #1 SMP 2008-05-23 14:08:04 +0200 x86_64 x86_64 x86_64 GNU/Linux with one ide disk and a pair or RAIDed sata disks. ==John ffitch
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 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 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata2.00: status: { DRDY } ata2: soft resetting link ata2.00: configured for PIO0 ata2.01: configured for PIO0 ata2: EH complete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
It seemes like a controller problem to me, rather than a disk problem. Why is is using PIO? Do you have the proper 80 pin cables?
I would open a bugzilla and try to assign it to Heo Tejun. He is Novell's sata driver expert. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Il Wednesday 28 May 2008 23:28:27 Greg Freemyer ha scritto:
On Wed, May 28, 2008 at 3:38 PM, John Andersen <jsamyth@gmail.com> wrote:
On Wed, May 28, 2008 at 8:53 AM, jpff <jpff@codemist.co.uk> wrote:
I had this message frequently in 10.3/x6_64 and local opinion was a failing disk. Changed disk, build 11.0b3 and it reappeared so changed IDE cable and it stopped -- for two days and then came back after a reboot for the new kernel, about every 4 mins or so. I looked via Google and it seems that it occurs but I did not find an explanation. Currently running Linux xenakis 2.6.25.4-6-default #1 SMP 2008-05-23 14:08:04 +0200 x86_64 x86_64 x86_64 GNU/Linux with one ide disk and a pair or RAIDed sata disks. ==John ffitch
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 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 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata2.00: status: { DRDY } ata2: soft resetting link ata2.00: configured for PIO0 ata2.01: configured for PIO0 ata2: EH complete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
It seemes like a controller problem to me, rather than a disk problem. Why is is using PIO? Do you have the proper 80 pin cables?
I would open a bugzilla and try to assign it to Heo Tejun. He is Novell's sata driver expert.
Greg
you can solve this problem (that made me definitively abandon Fedora for Suse) simply replacing your ata controller with its non-libata counterpart: e.g. I had to remove sata_via in favor of vt82cxxx. According to my readings this bug exhibits itself with controllers that have both sata and pata ports. It's been in the kernel for many months (maybe years) and I'm extremely surprised that it was never fixed (as far as I can tell). Fortunately Suse didn't make the idiot choice to remove non-libata based drivers that Fedora did. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Nico Sabbi escribió:
you can solve this problem (that made me definitively abandon Fedora for Suse) simply replacing your ata controller with its non-libata counterpart: e.g. I had to remove sata_via in favor of vt82cxxx.
That is no solution, drivers needs fixing/workaround instead.
e to remove non-libata based drivers that Fedora did.
They may be removed at some in the future though, but that's something kernel people decides. -- "Progress is possible only if we train ourselves to think about programs without thinking of them as pieces of executable code.” - Edsger W. Dijkstra Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
On Wed, May 28, 2008 at 6:26 PM, Cristian Rodríguez <crrodriguez@suse.de> wrote:
Nico Sabbi escribió:
you can solve this problem (that made me definitively abandon Fedora for Suse) simply replacing your ata controller with its non-libata counterpart: e.g. I had to remove sata_via in favor of vt82cxxx.
That is no solution, drivers needs fixing/workaround instead.
Historically the Linux 2.6 kernel has had some situations where they only supported the PATA connections of a controller or the SATA connections. I believe dual support has been to most by now, so I don't know if any drivers are still hobbled like that in 2.6.25 or not. Thus if a user had one of those, they either had to choose one half of their controller to use, or get a different controller. I believe one workaround was to run the controller in "legacy" mode and use the PATA driver.
e to remove non-libata based drivers that Fedora did.
They may be removed at some in the future though, but that's something kernel people decides.
The old drivers/ide subsystem is likely to be in vanilla kernels for a year or two longer (or more), but it can be disabled during kernel compile. I gather from Nico's comment that Fedora has quit building them into their kernels. A surprising situation, but certainly technically feasible. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Cristian Rodríguez -
Greg Freemyer -
John Andersen -
jpff -
Nico Sabbi