On Tue, Nov 20, 2007 at 03:02:29AM +0100, SPKills wrote:
I just (re)installed debian etch on my machine, at the first reboot i
got some errors on my harddisk and i don't really know what it's
about... But i'm pretty sure it's good at all and i probably have to
worry about...
I tried to do
On Tue, Nov 20, 2007 at 03:02:29AM +0100, SPKills wrote:
> I just (re)installed debian etch on my machine, at the first reboot i
> got some errors on my harddisk and i don't really know what it's
> about... But i'm pretty sure it's good at all and i probably have to
> worry about...
> I tried to
is a part of 'dmesg' command :
debian:~# dmesg
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdb: DMA disabled
ide0: reset: success
I used to get these messages several months back. I s
mplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekCo
On Tuesday 07 December 2004 04:45, Adomelf wrote:
> Hi,
> I meet some errors occasionally ,such as
> dma_intr: status=0x51 { DriveReady SeekComplete Error }
> dma_intr: error=0x84 { DriveStatusError BadCRC }
You don't say what version of Linux you are running. I had this p
Hi,
I meet some errors occasionally ,such as
dma_intr: status=0x51 { DriveReady SeekComplete Error }
dma_intr: error=0x84 { DriveStatusError BadCRC }
eth0: Oversized Ethernet frame spanned multiple buffers, entry 0x6
length 0 status 0600!
in the same time.
The frequence of these errors
lete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> I am running kernel 2.4.14-2.4.22 and they have all seen this problem.
>
> Things that I've done so far:
> replaced the IDE cable, no affect.
> replaced the hard drive, no affect.
> replaced both hard
I need some help.
I have a FIC SD-11 motherboard and a hard drive that keeps dumping out the
above error whenever dma is enabled.
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
I am running kernel 2.4.14-2.4.22 and they have
At 15:18 Uhr -0500 19.8.2001, Phil Brutsche wrote:
with UMDA66 you should see results somewhere in the vicinity of
25-30 MB/sec.
I get 23 MB/sec. (On the 2year old mac it's 12MB/sec) (Hmm I would
have thought that with a bus clock of 66Mhz and 16 bit bus width one
would get transfer rates of
A long time ago, in a galaxy far, far way, someone said...
> >What kernel is this? If you're using 2.4.x or 2.2.x with Andre Hedrick's
> >IDE patches this is done automatically.
>
> It's 2.4.7 (from kernel.org)
>
> >hdparm /dev/hda
>
> /dev/hda:
> multcount= 0 (off)
> I/O support = 1 (
At 22:36 Uhr -0500 18.8.2001, Phil Brutsche wrote:
You may want to consider replacing the IDE cable.
Thanks, I'll look for another one.
What kernel is this? If you're using 2.4.x or 2.2.x with Andre Hedrick's
IDE patches this is done automatically.
It's 2.4.7 (from kernel.org)
hdparm /de
A long time ago, in a galaxy far, far way, someone said...
> There are lots of reasons why a 2 year old G3 Mac has a 1 meg cache and
> the Athlon has a 256k cache, all of which are irrelevent given the
> difference between the CPU architectures.
Um, that shoudl read:
There are lots of reasons wh
A long time ago, in a galaxy far, far way, someone said...
> Hello
>
> I've seen some messages in the system log and am wondering what to do
> with them:
You may want to consider replacing the IDE cable. The CRC errors make me
suspicious that it may be bad. The "sector not found" errors may be
Thanks for your reply.
I've built the kernel with apm as a module. I've modprobe'd the apm
module now (/proc/apm reports -1% battery charge :-) ) and installed
apmd - i'll see if that changes anything.
christian
At 20:13 Uhr -0500 18.8.2001, Brian McGroarty wrote:
With a previous machine, I
dmaproc: chipset supported
> ide_dma_timeout func only: 14
> Aug 14 06:25:53 pflanze kernel: hda: irq timeout: status=0x59 {
> DriveReady SeekComplete DataRequest Error }
> Aug 14 06:25:53 pflanze kernel: hda: irq timeout: error=0x84 {
> DriveStatusError BadCRC }
With a previous machi
meout: status=0x59 {
DriveReady SeekComplete DataRequest Error }
Aug 14 06:25:53 pflanze kernel: hda: irq timeout: error=0x84 {
DriveStatusError BadCRC }
Doing a zgrep hda on the old messages logs I get:
messages.0:Aug 6 06:25:47 pflanze kernel: hda: timeout waiting for DMA
messages.0:Aug 6 06:
16 matches
Mail list logo
