This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Fri Apr 19 02:37:06 2024 Delivery-date: Mon, 27 Mar 2006 17:25:17 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751085AbWC0PYr (ORCPT ); Mon, 27 Mar 2006 10:24:47 -0500 Received: from odyssey.analogic.com ([204.178.40.5]:49931 "EHLO odyssey.analogic.com") by vger.kernel.org with ESMTP id S1751084AbWC0PYr convert rfc822-to-8bit (ORCPT ); Mon, 27 Mar 2006 10:24:47 -0500 Received: from chaos.analogic.com ([10.112.50.11]) by phoenix.analogic.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 27 Mar 2006 10:24:43 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Received: from chaos.analogic.com (localhost [127.0.0.1]) by chaos.analogic.com (8.12.11/8.12.11) with ESMTP id k2RFOhed016403; Mon, 27 Mar 2006 10:24:43 -0500 Received: (from linux-os@localhost) by chaos.analogic.com (8.12.11/8.12.11/Submit) id k2RFOg10016402; Mon, 27 Mar 2006 10:24:42 -0500 In-Reply-To: <20060327145501.34766.qmail@web30606.mail.mud.yahoo.com> X-OriginalArrivalTime: 27 Mar 2006 15:24:43.0165 (UTC) FILETIME=[92911CD0:01C651B2] content-class: urn:content-classes:message Subject: Re: Detecting I/O error and Halting System Date: Mon, 27 Mar 2006 10:24:42 -0500 Message-Id: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Detecting I/O error and Halting System Thread-Index: AcZRspKaTdY6XUTqQn6zqUNXhaw0Yw== References: <20060327145501.34766.qmail@web30606.mail.mud.yahoo.com> From: "linux-os \(Dick Johnson\)" To: "zine el abidine Hamid" Cc: Reply-To: "linux-os \(Dick Johnson\)" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 27 Mar 2006, zine el abidine Hamid wrote: > Hi everybody, > > I have I/O error which occurs on servers based on a > VIA VT82C686 chipset and I have to prevent or stop the > error. I spent a lot time for searching solutions to > stop the error but I don't found anything, So I want > to write a module which will surveil the HDD and > stops the system after sending a mail. > > I read a lot of documents about kernel and writting > modules but I don't know how to start...? Help, > please. > > I'm not closed to others solutions (like smartd, or > writting classical programms) > > Best regards. > > Zine > > PS : this are errors du to VIA chipset; if anyone > knows wath appens...? > > > Feb 12 04:46:03 porte_de_clignancourt_nds_b kernel: > hda: timeout waiting for DMA > Feb 12 04:46:06 alesia_nds_b ucd-snmp[812]: Connection > from 104.25.3.11 > Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel: > ide_dmaproc: chipset supported ide_dma_timeout func > only: 14 > Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel: > hda: status timeout: status=3D0xd0 { Busy } adapter > disque annonce un status busy du DMA > Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel: > hda: drive not ready for command > Feb 12 04:46:23 porte_de_clignancourt_nds_b > ucd-snmp[813]: Connection from 104.1.3.11 > Feb 12 04:46:23 porte_de_clignancourt_nds_b > ucd-snmp[813]: Connection from 104.1.3.11 > Feb 12 04:46:23 porte_de_clignancourt_nds_b last > message repeated 3 times > Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel: > ide0: reset: success > Feb 12 10:22:38 porte_de_clignancourt_nds_b kernel: > hda: timeout waiting for DMA > Feb 12 10:24:46 porte_de_clignancourt_nds_b kernel: > ide_dmaproc: chipset supported ide_dma_timeout func > only: 14 > Feb 12 10:24:46 porte_de_clignancourt_nds_b kernel: > hda: status timeout: status=3D0xd0 { Busy } > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > hda: drive not ready for command > Feb 12 10:24:47 porte_de_clignancourt_nds_b > ucd-snmp[813]: Connection from 104.1.3.11 > Feb 12 10:24:47 porte_de_clignancourt_nds_b last > message repeated 4 times > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > ide0: reset timed-out, status=3D0x80 > le premier reser de ide0 est en =E9chec > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > hda: status timeout: status=3D0x80 { Busy } > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > hda: drive not ready for command > Feb 12 10:24:47 porte_de_clignancourt_nds_b > ucd-snmp[813]: Connection from 104.1.3.11 > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > ide0: reset: success > > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > hda: irq timeout: status=3D0xd0 { Busy } > > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > hda: DMA disabled > > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > ide0: reset timed-out, status=3D0x80 > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > hda: status timeout: status=3D0x80 { Busy } > nouvel =E9chec de reset > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > hda: drive not ready for command > Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel: > ide0: reset: success > > Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel: > ide0: reset timed-out, status=3D0x80 > Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel: > hda: status timeout: status=3D0x80 { Busy } > Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel: > hda: drive not ready for command > Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel: > ide0: reset timed-out, status=3D0x80 > Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel: > end_request: I/O error, dev 03:02 (hda), sector 102263 > Feb 12 13:45:38 porte_de_clignancourt_nds_b syslogd: > /var/log/maillog: Input/output error > Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel: > end_request: I/O error, dev 03:02 (hda), sector 110720 > Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel: > end_request: I/O error, dev 03:02 (hda), sector 110728 > > Maybe you should just fix the problem rather than attempting to work around it! The problem is that that you system has difficulty communicating with a hard disk. This is caused by either: (1) Bad hard disk. (2) Bad cable. (3) Improper configuration of one or more disks. Since a reset timed out, it is likely that one of the disks that share the same cable is defective, not necessarily /dev/hda if you have another drive on the same cable. If you have only one drive per cable (or only one drive), it is likely that /dev/hda is (or becomes defective). Note that the disk can fail if it gets too hot. Cheers, Dick Johnson Penguin : Linux version 2.6.15.4 on an i686 machine (5589.42 BogoMips). Warning : 98.36% of all statistics are fiction, book release in April. _ =1A=04 **************************************************************** The information transmitted in this message is confidential and may be = privileged. Any review, retransmission, dissemination, or other use of= this information by persons or entities other than the intended recipi= ent is prohibited. If you are not the intended recipient, please notif= y Analogic Corporation immediately - by replying to this message or by = sending an email to DeliveryErrors@analogic.com - and destroy all copie= s of this information, including any attachments, without reading or di= sclosing them. Thank you. - To unsubscribe from this list: send the line "unsubscribe linux-kernel"= in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/