From: Andre Hedrick <andre@linux-ide.org>
To: ULISSES FURQUIM FREIRE DA SILVA <ra993482@ic.unicamp.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hardware, IDE or ext3 problem?
Date: Sun, 19 May 2002 15:01:57 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10205182044290.8582-100000@master.linux-ide.org> (raw)
In-Reply-To: <Pine.GSO.4.10.10205182031540.14231-100000@tigre.dcc.unicamp.br>
Hi Ulisses,
I guess I need to put in a special monster printk to explain the error
events. You drive, hardware, and data are secure because of a feature I
created, but chose not to patent (nice guy erm sucker et al.). However
you do have issues that cause the driver to invoke the transfer rate
reduction feature set. You can simply try put the drive back in the
faster mode and if it likes it fine, otherwise it will down grade again to
stablize throughput.
The choice is to have it continue with multiple retries w/ the higher
transfer rate, or reduce the io rate but have success on a consistant
bases.
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Sat, 18 May 2002, ULISSES FURQUIM FREIRE DA SILVA wrote:
>
> Hi,
>
> I installed Red Hat 7.3 and the 2.4.18-3 kernel shows some IDE
> errors on boot like:
>
> VFS: Mounted root (ext2 filesystem).
> Journalled Block Device driver loaded
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> ide0: reset: success
> kjournald starting. Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
>
> I also tried the 2.4.18-4 kernel, but the errors continue. It's
> weird cause this happen only on boot and in spite of it the system runs
> fine.
> I have a SiS 5513 chipset with a QUANTUM FIREBALLlct15 20 IDE
> drive.
> I'm not sure if I have a true hardware problem or if there is a
> bug in the kernel. Any ideas?
> (please CC the answers to me)
>
> Thanks,
>
> -- Ulisses
>
> -
> 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/
>
prev parent reply other threads:[~2002-05-19 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-19 0:08 ULISSES FURQUIM FREIRE DA SILVA
2002-05-19 18:13 ` Lionel Bouton
2002-05-19 19:03 ` ULISSES FURQUIM FREIRE DA SILVA
2002-05-19 20:11 ` Lionel Bouton
2002-05-19 21:45 ` ULISSES FURQUIM FREIRE DA SILVA
2002-05-19 22:01 ` Andre Hedrick [this message]
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=Pine.LNX.4.10.10205182044290.8582-100000@master.linux-ide.org \
--to=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ra993482@ic.unicamp.br \
/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
all inboxes | Powered by JetHome®