From: Tejun Heo <htejun@gmail.com>
To: Lieven Marchand <mal@wyrd.be>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org,
Robert Hancock <hancockr@shaw.ca>
Subject: Re: regression problem with Maxtor disk
Date: Tue, 14 Aug 2007 18:50:24 +0900 [thread overview]
Message-ID: <46C17AE0.5090601@gmail.com> (raw)
In-Reply-To: <87tzr4zvpt.fsf@wyrd.be>
[cc'ing Robert Hancock and quoting the whole message for him]
Lieven Marchand wrote:
> Hi,
>
> the following drive
>
> Aug 12 12:26:15 black kernel: Vendor: ATA Model: Maxtor 7H500F0 Rev:
> HA43
> Aug 12 12:26:15 black kernel: Type: Direct-Access ANSI
> SCSI revision: 05
>
> works fine under 2.6.18 and crashes the boot procedure under
> 2.6.22. Occasionally the boot continues but most of the times the
> kernel crashes with an error message of a corrupt cpu context.
>
> I've added the logs of a succesful boot here. When such a boot
> succeeds, the system is noticeably slower than under 2.6.18.
>
> Aug 11 10:27:51 black kernel: scsi 4:0:0:0: Direct-Access ATA Maxtor 7H
> 500F0 HA43 PQ: 0 ANSI: 5
> Aug 11 10:27:51 black kernel: ata2: bounce limit 0xFFFFFFFFFFFFFFFF, segment bou
> ndary 0xFFFFFFFF, hw segs 61
> Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x440
> Aug 11 10:27:51 black kernel: res 51/04:00:00:00:00/04:00:00:00:00/40 E
> mask 0x1 (device error)
> Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133
> Aug 11 10:27:51 black kernel: ata2: EH complete
>
> Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x440
> Aug 11 10:27:51 black kernel: res 51/04:00:00:00:00/04:00:00:00:00/40 E
> mask 0x1 (device error)
> Aug 11 10:27:51 black last message repeated 2 times
> Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133
> Aug 11 10:27:51 black kernel: ata2: EH complete
> Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY clear and ID
> LE, stat=0x440
> Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x400
> Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY, stat=0x400
> Aug 11 10:27:51 black kernel: res 40/00:00:00:00:00/04:00:00:00:00/40 E
> mask 0x4 (timeout)
> Aug 11 10:27:51 black last message repeated 2 times
> Aug 11 10:27:51 black kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 E
> mask 0x4 (timeout)
> Aug 11 10:27:51 black kernel: ata2: soft resetting port
> Aug 11 10:27:51 black kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl
> 300)
> Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133
> Aug 11 10:27:51 black kernel: ata2: EH complete
> Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY clear and ID
> LE, stat=0x400
> Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x400
> Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY, stat=0x400
> Aug 11 10:27:51 black kernel: ata2.00: NCQ disabled due to excessive errors
> Aug 11 10:27:51 black kernel: res 40/00:00:00:00:00/04:00:00:00:00/40 E
> mask 0x4 (timeout)
> Aug 11 10:27:51 black last message repeated 2 times
> Aug 11 10:27:51 black kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 E
> mask 0x4 (timeout)
> Aug 11 10:27:51 black kernel: ata2: soft resetting port
> Aug 11 10:27:51 black kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl
> 300)
> Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133
> Aug 11 10:27:51 black kernel: ata2: EH complete
> Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY clear and ID
> LE, stat=0x400
> Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA IDLE, stat=0x400
> Aug 11 10:27:51 black kernel: ata2: timeout waiting for ADMA LEGACY, stat=0x400
> Aug 11 10:27:51 black kernel: res 40/00:00:00:00:00/04:00:00:00:00/40 E
> mask 0x4 (timeout)
> Aug 11 10:27:51 black kernel: ata2: soft resetting port
> Aug 11 10:27:51 black kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl
> 300)
> Aug 11 10:27:51 black kernel: ata2.00: configured for UDMA/133
> Aug 11 10:27:51 black kernel: ata2: EH complete
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
tejun
next prev parent reply other threads:[~2007-08-14 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 14:14 regression problem with Maxtor disk Lieven Marchand
2007-08-14 9:50 ` Tejun Heo [this message]
2007-08-14 23:14 ` Robert Hancock
2007-08-15 7:34 ` Lieven Marchand
2007-08-15 7:53 ` Tejun Heo
2007-08-15 21:22 ` Lieven Marchand
2007-08-15 23:31 ` Robert Hancock
-- strict thread matches above, loose matches on Subject: below --
2007-08-12 23:36 babl
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=46C17AE0.5090601@gmail.com \
--to=htejun@gmail.com \
--cc=hancockr@shaw.ca \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=mal@wyrd.be \
/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;
as well as URLs for NNTP newsgroup(s).