linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Lee <nj.lee@plumtree.co.nz>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: Crashing with Abit KT7, 2.2.19+ide patches
Date: Tue, 28 Aug 2001 14:16:34 +1200	[thread overview]
Message-ID: <20010828141633.C14714@cone.kiwa.co.nz> (raw)
In-Reply-To: <20010827200106.A26175@cone.kiwa.co.nz> <3B8AD463.C196B9B6@bigfoot.com>
In-Reply-To: <3B8AD463.C196B9B6@bigfoot.com>; from timothymoore@bigfoot.com on Mon, Aug 27, 2001 at 04:14:43PM -0700



I managed to catch one of these crash the system messages:

Aug 28 14:07:51 hoppa kernel: hda: timeout waiting for DMA
Aug 28 14:07:51 hoppa kernel: hda: ide_dma_timeout: Lets do it again!stat = 0xd0, dma_stat = 0x20
Aug 28 14:07:51 hoppa kernel: hda: DMA disabled
Aug 28 14:07:51 hoppa kernel: hda: irq timeout: status=0x80 { Busy }
Aug 28 14:07:51 hoppa kernel: hda: DMA disabled
Aug 28 14:07:51 hoppa kernel: hda: ide_set_handler: handler not null; old=c018f67c, new=c018f67c
Aug 28 14:07:51 hoppa kernel: bug: kernel timer added twice at c018f526.
Aug 28 14:07:53 hoppa kernel: ide0: reset: success


Note the second the last line: "bug: kernel timer added twice at
c018f526"


This occured 4 mintues after a system reboot and some rsync activity. 
It occured this time when I was in the shell doing a cd [tab].

Other times the HDD might have just crashed again.


Note: this box is also acting as a router between three interfaces at
the same time with IPSec on one of these interfaces.   


Is this likely to make the situation worse?


Nicholas

  parent reply	other threads:[~2001-08-28  2:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-27  8:01 Crashing with Abit KT7, 2.2.19+ide patches Nicholas Lee
2001-08-27 23:14 ` Tim Moore
2001-08-27 23:48   ` Nicholas Lee
2001-08-28  0:15   ` Nicholas Lee
2001-08-28  2:16   ` Nicholas Lee [this message]
2001-08-28 16:56     ` Tim Moore

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=20010828141633.C14714@cone.kiwa.co.nz \
    --to=nj.lee@plumtree.co.nz \
    --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;
as well as URLs for NNTP newsgroup(s).