public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sebastian Piecha" <spi@gmxpro.de>
To: "Eric Bickle" <ebickle@healthspace.ca>, <linux-kernel@vger.kernel.org>
Subject: Re: Problem: IDE data corruption with VIA chipsets on 2.4.20-19.8+others
Date: Thu, 11 Sep 2003 10:28:25 +0200	[thread overview]
Message-ID: <3F604E49.14444.F8BCBBB@localhost> (raw)
In-Reply-To: <003601c37826$26d8d220$5d74ad8e@hyperwolf>

On 10 Sep 2003 at 22:32, Eric Bickle wrote:

> The core issue:
> ----------------
> Random crashes, general operating system instability with a RedHat 8 Linux
> install running a moderately heavy-use database server (IBM Lotus Domino 5
> or 6). All current indications point to a data
> corruption/ide-incompatibility between the linux IDE driver and various VIA
> chipsets. The problem only occurs during heavy database server load.
> ...
I reported a problem to the lkml (see "PROBLEM: Powerquest Drive 
Image let the kernel panic" and "PROBLEM: kernel panic when accessing 
data via samba") describing a kernel panic when accessing a huge 
amount of data via samba. Unfortunately I didn't get any response 
yet.

I'm using a SuSE 8.2 distribution with kernel 2.4.20.

> 
> We also get various IDE errors in the /var/log files, such as: (also another
> weird IRQ error - except we're running a stock config! (ie/ no PCI devices
> other than one NIC... No idea if they're related to the IDE thing <sigh>.
> The IRQ thing appears to be USB related)
> == during server runtime ==
> kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> kernel: hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=150637065,
> sector=150636992
> kernel: end_request: I/O error, dev 16:01 (hdc), sector 150636992
> kernel: hdc: dma_intr: status=0x53 { DriveReady SeekComplete Index Error }
> kernel: hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=150630007,
> sector=150629920
> kernel: end_request: I/O error, dev 16:01 (hdc), sector 150629920
> == during server boot ==
> kernel: usb.c: new USB bus registered, assigned bus number 3
> kernel: hub.c: USB hub found
> kernel: hub.c: 2 ports detected
> kernel: PCI: Found IRQ 3 for device 00:10.2
> kernel: IRQ routing conflict for 00:10.0, have irq 9, want irq 3
> kernel: IRQ routing conflict for 00:10.1, have irq 9, want irq 3
> kernel: IRQ routing conflict for 00:10.2, have irq 9, want irq 3
> kernel: IRQ routing conflict for 00:10.3, have irq 9, want irq 3
> kernel: usb-uhci.c: USB UHCI at I/O 0x9400, IRQ 9
> ...

I'm getting similar errors:
kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
kernel: hdc: drive_cmd: error=0x04Aborted Command 

I don't get any IRQ routing conflicts.

But in my configuration hdc is a cd-rom attached to the onboard IDE. 

> ...
> We tried various motherboards, including the following chipsets:
> VIA KT333
> VIA KT400
> SiS 745
> 
> ...
My onboard IDE is an Intel 82371AB/EB/MB PIIX4 IDE. My two harddisks 
(each 120GB of size) are attached to a Promise Ultra 133TX2 
controller.

Mit freundlichen Gruessen/Best regards,
Sebastian Piecha

EMail: spi@gmxpro.de


  reply	other threads:[~2003-09-11  8:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11  5:32 Problem: IDE data corruption with VIA chipsets on 2.4.20-19.8+others Eric Bickle
2003-09-11  8:28 ` Sebastian Piecha [this message]
2003-09-11 11:26 ` Andre Tomt
2003-09-11 14:32 ` Alan Cox
2003-09-11 14:34 ` Alan Cox
2003-09-11 20:24 ` Francois Romieu
2003-09-11 23:58 ` Resident Boxholder

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=3F604E49.14444.F8BCBBB@localhost \
    --to=spi@gmxpro.de \
    --cc=ebickle@healthspace.ca \
    --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