i386/121115: [SATA] READ_DMA failure after 6.3 security upgrade

[Christophe Cap]

The following reply was made to PR i386/121115; it has been noted by GNATS.

From: "Christophe Cap" <christophe.cap at gmail.com>
To: FreeBSD-gnats-submit at freebsd.org, freebsd-i386 at 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 at freebsd.org <
 FreeBSD-gnats-submit at 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.<br><br>Apparantly something went wrong during the reboot after installing the new kernel and there were 2 bad blocks.<br><br>Seatools managerd to fix it, and after another run of fsck on that drive everything boots fine again.<br>
 <br>I guess the PR can be closed again.<br><br>Sorry for the trouble.<br><br>Best regards,<br><br>C.<br><br><div><span class="gmail_quote">On 2/26/08, <b class="gmail_sendername"><a href="mailto:FreeBSD-gnats-submit at freebsd.org">FreeBSD-gnats-submit at freebsd.org</a></b> &lt;<a href="mailto:FreeBSD-gnats-submit at freebsd.org">FreeBSD-gnats-submit at freebsd.org</a>&gt; wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border- left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
 Thank you very much for your problem report.<br> It has the internal identification `i386/121115&#39;.<br> The individual assigned to look at your<br> report is: freebsd-i386.<br><br> You can access the state of your problem report at any time<br>
  via this link:<br><br> <a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=121115">http://www.freebsd.org/cgi/query-pr.cgi?pr=121115</a><br><br> &gt;Category:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; i386<br> &gt;Responsible:&nbsp;&nbsp;&nbsp;&nbsp;freebsd-i386<br> &gt;Synopsis:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [SATA] READ_DMA failure after 6.3 security upgrade<br>
  &gt;Arrival-Date:&nbsp;&nbsp; Tue Feb 26 11:50:07 UTC 2008<br></blockquote></div><br><br clear="all"><br>-- <br>Christophe<br><br><br>---<br>Truly great madness cannot be achieved without significant intelligence.<br>--- 
 
 ------=_Part_13648_30076212.1204060184163--