From owner-freebsd-i386@FreeBSD.ORG Tue Feb 26 21:40:05 2008 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C90D3106575C for ; Tue, 26 Feb 2008 21:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6D90913C46B for ; Tue, 26 Feb 2008 21:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m1QLe4qg039028 for ; Tue, 26 Feb 2008 21:40:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m1QLe4Bi039027; Tue, 26 Feb 2008 21:40:04 GMT (envelope-from gnats) Date: Tue, 26 Feb 2008 21:40:04 GMT Message-Id: <200802262140.m1QLe4Bi039027@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: "Christophe Cap" Cc: Subject: Re: i386/121115: [SATA] READ_DMA failure after 6.3 security upgrade X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Christophe Cap List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2008 21:40:05 -0000 The following reply was made to PR i386/121115; it has been noted by GNATS. From: "Christophe Cap" To: FreeBSD-gnats-submit@freebsd.org, freebsd-i386@freebsd.org Cc: Subject: Re: i386/121115: [SATA] READ_DMA failure after 6.3 security upgrade Date: Tue, 26 Feb 2008 21:09:44 +0000 ------=_Part_13648_30076212.1204060184163 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Ok, in the meantime I dowloaded the Seagate Seatols software and did a full low-level check. Apparantly something went wrong during the reboot after installing the new kernel and there were 2 bad blocks. Seatools managerd to fix it, and after another run of fsck on that drive everything boots fine again. I guess the PR can be closed again. Sorry for the trouble. Best regards, C. On 2/26/08, FreeBSD-gnats-submit@freebsd.org < FreeBSD-gnats-submit@freebsd.org> wrote: > > Thank you very much for your problem report. > It has the internal identification `i386/121115'. > The individual assigned to look at your > report is: freebsd-i386. > > You can access the state of your problem report at any time > via this link: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=121115 > > >Category: i386 > >Responsible: freebsd-i386 > >Synopsis: [SATA] READ_DMA failure after 6.3 security upgrade > >Arrival-Date: Tue Feb 26 11:50:07 UTC 2008 > -- Christophe --- Truly great madness cannot be achieved without significant intelligence. --- ------=_Part_13648_30076212.1204060184163 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Ok, in the meantime I dowloaded the Seagate Seatols software and did a full low-level check.

Apparantly something went wrong during the reboot after installing the new kernel and there were 2 bad blocks.

Seatools managerd to fix it, and after another run of fsck on that drive everything boots fine again.

I guess the PR can be closed again.

Sorry for the trouble.

Best regards,

C.

On 2/26/08, FreeBSD-gnats-submit@freebsd.org <FreeBSD-gnats-submit@freebsd.org> wrote:
Thank you very much for your problem report.
It has the internal identification `i386/121115'.
The individual assigned to look at your
report is: freebsd-i386.

You can access the state of your problem report at any time
via this link:

http://www.freebsd.org/cgi/query-pr.cgi?pr=121115

>Category:       i386
>Responsible:    freebsd-i386
>Synopsis:       [SATA] READ_DMA failure after 6.3 security upgrade
>Arrival-Date:   Tue Feb 26 11:50:07 UTC 2008



--
Christophe


---
Truly great madness cannot be achieved without significant intelligence.
--- ------=_Part_13648_30076212.1204060184163--