From: Jeff Garzik <jeff@garzik.org>
To: Heikki Orsila <shdl@zakalwe.fi>
Cc: Max Krasnyansky <maxk@qualcomm.com>, linux-kernel@vger.kernel.org
Subject: Re: Strange freezes (seems like SATA related)
Date: Thu, 01 Nov 2007 23:34:35 -0400 [thread overview]
Message-ID: <472A9ACB.6040107@garzik.org> (raw)
In-Reply-To: <20071101235348.GC3441@zakalwe.fi>
Heikki Orsila wrote:
> On Mon, Oct 29, 2007 at 09:54:27AM -0700, Max Krasnyansky wrote:
>> A couple of HP xw9300 machines (dual Opterons) started freezing up.
>> We're running on 2.6.22.1 on them. Freezes a somewhere weird.
>> VGA console is alive
>> (I can switch vts, etc) but everything else is dead (network, etc).
>
> I'm thinking this is not a coincidence. I was running 2.6.22.5, and
> looking at your problems, I just had a similar experience on tuesday..
> The network was still fine after kernel errors so that I was able to
> login with SSH. See:
>
> http://lkml.org/lkml/2007/10/30/193
>
>> ata1: EH in ADMA mode, notifier 0x1 notifier_error 0x0 gen_ctl 0x1581000 status 0x1540 next cpb count 0x0 next cpb idx 0x0
>> ata1: CPB 0: ctl_flags 0xd, resp_flags 0x1
>> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
>> ata1.00: cmd ca/00:08:57:00:80/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)
>> Descriptor sense data with sense descriptors (in hex):
>> end_request: I/O error, dev sda, sector 8388695
>> Buffer I/O error on device sda1, logical block 1048579
>> lost page write due to I/O error on sda1
>> sd 0:0:0:0: [sda] Write Protect is off
>
> With ata_piix Intel SATA I got these errors:
>
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata1.00: cmd ca/00:68:6f:3a:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 53248 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata1: port is slow to respond, please be patient (Status 0xd0)
> ata1: device not ready (errno=-16), forcing hardreset
> ata1: soft resetting port
> ata1.00: revalidation failed (errno=-2)
> ata1: failed to recover some devices, retrying in 5 secs
> ata1: soft resetting port
> ata1.00: configured for UDMA/133
> ata1: EH complete
> sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
These are two 100% different issues.... The only thing they have in
common is that they spit out an error.
Jeff
next prev parent reply other threads:[~2007-11-02 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 16:54 Strange freezes (seems like SATA related) Max Krasnyansky
2007-11-01 23:40 ` Andrew Morton
2007-11-06 21:42 ` Max Krasnyansky
2007-11-01 23:53 ` Heikki Orsila
2007-11-02 3:34 ` Jeff Garzik [this message]
[not found] <fa.geuG6UTKiSgc409K9/yA9HzMTUs@ifi.uio.no>
2007-10-30 0:03 ` Robert Hancock
2007-11-06 21:36 ` Max Krasnyansky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=472A9ACB.6040107@garzik.org \
--to=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=shdl@zakalwe.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox