linux-kernel - Re: AHCI exception, ext3 journal aborted on a VIA K8M890 / VT8251

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 5 Apr 2007 15:52:17 -0400
From:	"Stephen Evanchik" <evanchsa@...il.com>
To:	"Chuck Ebbert" <cebbert@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: AHCI exception, ext3 journal aborted on a VIA K8M890 / VT8251

n 4/2/07, Chuck Ebbert <cebbert@...hat.com> wrote:
> Stephen Evanchik wrote:
> > My hardware components are the following:
> >
> > Motherboard: A8V-VM Socket 939 VIA K8M890 / VT8251
> > CPU: Opteron 165 dual core
> > Harddisk: SATA 1.5Gbps WD 160GB drive
> >
> > Most relevant snippet from dmesg, (you can see a longer version below):
> >
> > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> > ata1.00: cmd ca/00:08:c5:b6:03/00:00:00:00:00/e0 tag 0 cdb 0x0 data 4096
> > out
> >        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> > ata1: soft resetting port
> > ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> > ata1.00: qc timeout (cmd 0xec)
> > ata1.00: failed to IDENTIFY (I/O error, err_mask=0x104)
> > ata1.00: revalidation failed (errno=-5)
> > ata1: failed to recover some devices, retrying in 5 secs
> > ata1: hard resetting port
> >

I have tested 2.6.20, 2.6.20.5, 2.6.21-rc5 and all exhibit the same behavior.

>
> We are testing fixes, but can only build test kernels for FC6. I think
> this may be fixed by patches I submitted for 2.6.20.5.
>

I still see the above problem from 2.6.19-rc1 to 2.6.21-rc5.


Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/