public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrik Persson <nix@syndicalist.net>
To: "Mario 'BitKoenig' Holbe" <Mario.Holbe@RZ.TU-Ilmenau.DE>
Cc: Bruce Allen <ballen@gravity.phys.uwm.edu>, linux-kernel@vger.kernel.org
Subject: Re: Strange DMA-errors and system hang with Promise 20268
Date: Wed, 10 Mar 2004 16:00:52 +0100	[thread overview]
Message-ID: <1078930851.766.7.camel@vega> (raw)
In-Reply-To: <20040310123616.GA31893@darkside.22.kls.lan>

[-- Attachment #1: Type: text/plain, Size: 944 bytes --]

On Wed, 2004-03-10 at 13:36, Mario 'BitKoenig' Holbe wrote:
> On Wed, Mar 10, 2004 at 05:50:12AM -0600, Bruce Allen wrote:
> > Does the disk's SMART error log (smartctl -l error) show any entries
> > related to this problem?  If so, please print them with the latest version
> 
> No, none at all. This was the first I was looking at, because
> I just thought it was some disk problem.

Same here. Just one of the discs that has stopped during the last month
has any entries in the log at all. Those errors are attached.

The funny thing is that the machine stops responding after the
dma_timer_expiry.. Why doesn't just the kernel (or the controller for
that matter) disable DMA and then the problem would be solved, if the
problem is related to DMA, right? Sure, the speed (or lack of it) would
be painful but I wouldn't need to sit 60km from home and wondering why
my box just stopped responding. ;/

-- 
Henrik Persson <nix@syndicalist.net>

[-- Attachment #2: smarterrors --]
[-- Type: text/plain, Size: 3753 bytes --]

smartctl version 5.26 Copyright (C) 2002-3 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
ATA Error Count: 4
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Timestamp = decimal seconds since the previous disk power-on.
Note: timestamp "wraps" after 2^32 msec = 49.710 days.

Error 4 occurred at disk power-on lifetime: 6619 hours
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 00 00 00 00 e0  Error: ICRC, ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  c8 ff 01 00 00 00 e0 08     546.992  READ DMA
  ef 03 45 20 77 a5 e0 08     546.992  SET FEATURES [Set transfer mode]
  c6 ff 10 20 77 a5 e0 08     546.992  SET MULTIPLE MODE
  10 ff 50 20 77 a5 e0 08     546.992  RECALIBRATE [OBS-4]
  91 03 3f 20 77 a5 ef 08     546.992  INITIALIZE DEVICE PARAMETERS [OBS-6]

Error 3 occurred at disk power-on lifetime: 6619 hours
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 00 00 00 00 e0  Error: ICRC, ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  c8 ff 01 00 00 00 e0 08     516.560  READ DMA
  ef 03 45 c5 7b e3 e0 08     516.560  SET FEATURES [Set transfer mode]
  c6 ff 10 c5 7b e3 e0 08     516.560  SET MULTIPLE MODE
  10 ff 50 c5 7b e3 e0 08     516.544  RECALIBRATE [OBS-4]
  91 03 3f c5 7b e3 ef 08     516.544  INITIALIZE DEVICE PARAMETERS [OBS-6]

Error 2 occurred at disk power-on lifetime: 6619 hours
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 00 00 00 00 e0  Error: ICRC, ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  c8 ff 01 00 00 00 e0 08     501.328  READ DMA
  ef 03 45 18 bb 65 e0 08     501.328  SET FEATURES [Set transfer mode]
  c6 ff 10 18 bb 65 e0 08     501.328  SET MULTIPLE MODE
  10 ff 50 18 bb 65 e0 08     501.312  RECALIBRATE [OBS-4]
  91 03 3f 18 bb 65 ef 08     501.312  INITIALIZE DEVICE PARAMETERS [OBS-6]

Error 1 occurred at disk power-on lifetime: 6619 hours
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  84 51 00 00 00 00 e0  Error: ICRC, ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  c8 ff 01 00 00 00 e0 08     420.528  READ DMA
  ef 03 45 73 3d 65 e0 08     412.896  SET FEATURES [Set transfer mode]
  c6 ff 10 73 3d 65 e0 08     412.896  SET MULTIPLE MODE
  10 ff 50 73 3d 65 e0 08     412.896  RECALIBRATE [OBS-4]
  91 03 3f 73 3d 65 ef 08     412.896  INITIALIZE DEVICE PARAMETERS [OBS-6]


  reply	other threads:[~2004-03-10 15:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-06 19:47 Strange DMA-errors and system hang with Promise 20268 Henrik Persson
2004-03-06 19:55 ` Henrik Persson
2004-03-07  1:05 ` Mario 'BitKoenig' Holbe
2004-03-08 13:30   ` Henrik Persson
2004-03-10 11:50     ` Bruce Allen
2004-03-10 12:36       ` Mario 'BitKoenig' Holbe
2004-03-10 15:00         ` Henrik Persson [this message]
2004-03-11  9:36           ` Bruce Allen
2004-03-11 14:31             ` Henrik Persson
2004-03-10 15:41       ` Mario 'BitKoenig' Holbe
2004-03-11  9:25         ` Bruce Allen
2004-05-19 17:20   ` Sebastian
2004-05-19 17:28     ` Mario 'BitKoenig' Holbe
2004-05-19 18:12       ` Sebastian
     [not found]         ` <1648.128.150.143.219.1084992082.squirrel@webmail.seven4sky.com>
2004-05-19 20:12           ` Strange DMA-errors... (was: ...and system hang with Promise 20268) Sebastian
2004-05-19 23:47             ` Mario 'BitKoenig' Holbe
2004-05-20  9:23         ` Strange DMA-errors and system hang with Promise 20268 Bruce Allen
2004-05-20 10:35           ` Strange DMA-errors and system hang with SMART (was: ...and system hang with Promise 20268) Sebastian
2004-05-23 12:46             ` Bruce Allen
2004-06-02 19:00               ` Sebastian
2004-06-03 15:06                 ` Bruce Allen
2004-05-29 14:42   ` Strange DMA-errors and system hang with Promise 20268 Mario 'BitKoenig' Holbe
2004-05-29 22:51     ` Gene Heskett
2004-05-30 10:41     ` Henrik Persson
2004-06-04 20:09     ` Bruce Allen
     [not found] ` <200405052339.i45NdXsx003369@darkside.22.kls.lan>
     [not found]   ` <1083849053.6994.10.camel@vega>
2004-05-06 14:22     ` Mario 'BitKoenig' Holbe

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=1078930851.766.7.camel@vega \
    --to=nix@syndicalist.net \
    --cc=Mario.Holbe@RZ.TU-Ilmenau.DE \
    --cc=ballen@gravity.phys.uwm.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox