linux-kernel - Re: [2.6.28-rc] Sata soft reset filling log

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>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 29 Dec 2008 15:23:09 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Justin Madru <jdm64@...ab.com>
CC:	lkml <linux-kernel@...r.kernel.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-ide@...r.kernel.org, "Rafael J. Wysocki" <rjw@...k.pl>,
	Jeff Garzik <jeff@...zik.org>
Subject: Re: [2.6.28-rc] Sata soft reset filling log

Hello,

Justin Madru wrote:
> I applied the patch and get the following:
> 
> ata2: XXX status=50 after 100 tries
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata2.00: ST_FIRST: !(DRQ|ERR|DF)
> 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 50/00:01:00:00:00/00:00:00:00:00/a0 Emask 0x2 (HSM violation)
> ata2.00: status: { DRDY }
> ata2: soft resetting link
> ata2.00: configured for UDMA/33
> ata2: EH complete

This is so strange.  :-(

> I tried to git bisect the problem. First time I thought the error
> was between rc2 and rc3, but the bisect gave inconclusive results
> because I couldn't tell for sure a good commit from a bad.  I tried
> again with .27 to .28-rc3, but I was unable to bisect because of
> compile errors (in pre-rc1), and doing git bisect skip, again landed
> on a commit with compile errors.

Thanks for trying.  I can't think of any relevant change which can
cause this and I doubt it's something affecting many machines given
that you're currently the only one reporting this problem.

Any chance it's a hardware fluke?  Can you please make sure it doesn't
happen with 2.6.27?

> Unless you can think of anything else, I'm just going to wait and see if
> a commit in .29 will fix the problem.

Eh... I doubt that will happen.  No scheduled change for SFF HSM
implementation.

Thanks.

-- 
tejun
--
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/