All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Andersen <bryan@bogonomicon.net>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Manish Lachwani <manish@Zambeel.com>,
	Manish Lachwani <m_lachwani@yahoo.com>,
	linux-kernel@vger.kernel.org
Subject: Re: FW: PDC202XX DMA loss in 2.4.21-pre3-ac4
Date: Sun, 26 Jan 2003 05:24:10 -0600	[thread overview]
Message-ID: <3E33C55A.5050403@bogonomicon.net> (raw)
In-Reply-To: Pine.LNX.4.10.10301260125510.1744-100000@master.linux-ide.org



Andre Hedrick wrote:
> Yeah "smartctl" does not work, but reading the correct 48-bit logs does.
> 
> All I stated was you are using the wrong tool to extract the needed
> information.

So which tool(s) do I need for getting at the 48-bit log data?  If I 
need a spec doc to decode a binary block of data I can deal with that. 
Prefer not to, but...

I did a full surface read scan of the disk and it turned up no errors.

As for how I got the SMART data dump I enabled SMART on the drive then 
dumped the data a few minutes later.

- Bryan


  reply	other threads:[~2003-01-26 11:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <233C89823A37714D95B1A891DE3BCE5202AB1D12@xch-b.win.zambeel.com>
2003-01-26  9:42 ` FW: PDC202XX DMA loss in 2.4.21-pre3-ac4 Andre Hedrick
2003-01-26 11:24   ` Bryan Andersen [this message]
2003-01-26 21:27     ` Andre Hedrick
     [not found] <233C89823A37714D95B1A891DE3BCE5202AB1D07@xch-b.win.zambeel.com>
2003-01-25 20:34 ` Manish Lachwani
2003-01-26  6:51   ` Bryan Andersen
2003-01-26  7:15     ` Manish Lachwani
2003-01-26  8:13       ` Andre Hedrick
2003-01-26  8:27         ` Manish Lachwani
2003-01-26  8:48           ` Andre Hedrick
2003-01-26  9:10             ` Manish Lachwani
2003-01-26  9:14               ` Andre Hedrick

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=3E33C55A.5050403@bogonomicon.net \
    --to=bryan@bogonomicon.net \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m_lachwani@yahoo.com \
    --cc=manish@Zambeel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.