Bug#561894: linux-image-2.6.32-trunk-686: ata reset during moderate load
On Mon, 21 Dec 2009, Ritesh Raj Sarraf wrote:
> Package: linux-2.6
> Version: 2.6.32-2
> Severity: normal
>
> The machine had an uptime of 5 days. Had been suspended (STR) and
> resumed many times. Today morning, I tried to preview a half-downloaded
> torrent file, which led in too much of disk I/O taking place.
> This led to the following ata reset followed by the RO remount of the
> ext4 file system.
>
>
> [476862.000125] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action
> 0x6 frozen
> [476862.000137] ata1.00: failed command: FLUSH CACHE EXT
> [476862.000154] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
> [476862.000158] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask
> 0x4 (timeout)
> [476862.000166] ata1.00: status: { DRDY }
> [476867.040082] ata1: link is slow to respond, please be patient
> (ready=0)
> [476872.024036] ata1: device not ready (errno=-16), forcing hardreset
> [476872.024050] ata1: soft resetting link
> [476877.220085] ata1: link is slow to respond, please be patient
> (ready=0)
> [476880.396601] ata1.00: configured for UDMA/100
> [476880.396612] ata1.00: device reported invalid CHS sector 0
> [476880.396625] end_request: I/O error, dev sda, sector 0
> [476880.396650] ata1: EH complete
> [476880.445232] Aborting journal on device dm-0-8.
> [476880.690442] EXT4-fs error (device dm-0): ext4_journal_start_sb:
> Detected aborted journal
> [476880.690451] EXT4-fs (dm-0): Remounting filesystem read-only
> [476881.064105] EXT4-fs error (device dm-0) in ext4_reserve_inode_write:
> Journal has aborted
> [476881.065448] journal commit I/O error
> [477058.373151] EXT4-fs error (device dm-0): ext4_remount: Abort forced
> by user
>
>
>
> Regards,
> Ritesh
can you reproduce that easily?
or was it a one time event, sid should have newer 2.6.32 by now
with lots of fixes.
if yes please report upstream on bugzilla.kernel.org
and let us know the bug nr, so that we can track it.
thanks
Reply to: