linux-kernel - continues problems with libata; kernel 2.6.21.1

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

Message-ID: <46385818.8000209@astro.uni-bonn.de>
Date:	Wed, 02 May 2007 11:21:28 +0200
From:	Manuel Metz <mmetz@...ro.uni-bonn.de>
To:	linux-kernel@...r.kernel.org
CC:	jeff@...zik.org, htejun@...il.com,
	Manuel Metz <mmetz@...ro.uni-bonn.de>
Subject: continues problems with libata; kernel 2.6.21.1

Hi,
unfortunately I have continues problems with libata on my box. The
mainboard is an  ASUS A8V-X.
(see also in a previous thread http://lkml.org/lkml/2007/2/14/47)

I worked now for several weeks with the new libata drivers. The system
boots, but only with a couple of warnings while booting. After that it
appears to be working, but ...

... basically every time I have to reboot my system (which only happens
rarely, maybe once every second week or so) I get file system errors on
the hard-drives attached to the PATA controller. I did not recognize
this behaviour when I was using the old ATA driver, but this only
occurred since I am using the new libata. So I suspect that it has
something to do with libata, but I'm not absolutely sure.

Any idea? Might this only be a behaviour of the asus board?

Manuel

attached:
- output of lspci
- my latest .config
- dmesg output after reboot

View attachment "lspci.txt" of type "text/plain" (2132 bytes)

View attachment ".config" of type "text/plain" (45244 bytes)

View attachment "dmesg.2.6.21.1.sataproblem.txt" of type "text/plain" (30804 bytes)