mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andree Leidenfrost <andree.leidenfrost@harmsconsulting.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel Panic: 2.4.20pre7-ac3 and earlier with PDC20276
Date: Mon, 23 Sep 2002 07:50:18 +1000	[thread overview]
Message-ID: <3D8E3B1A.5050800@harmsconsulting.com> (raw)

I am experiencing kernel errors when accessing disks attached to the 
PDC20276. Executing command 'badblocks -svw /dev/hde' starts fine:

sv-sap001:/home/andree# badblocks -svw /dev/hde
Checking for bad blocks in read-write mode
 From block 0 to 39082680
Writing pattern 0xaaaaaaaa:   1266090/ 39082680

After a while I start getting messages like the stuff below on the 
console (this manually copied from the console).

This happens on both drives and on both channels. Cables were replaced, 
so were the harddisks. I returned the machine to my dealer who tested 
things under WinXP and says that everything works fine. I have tried 
this with 2.4.19 and pretty much all 2.4.20preX and 2.4.20preX-acY 
version over the past three weeks without success. When I switch off DMA 
('hdparm -d0 /dev/hde') things are of course terribly slow but they work 
fine.

I am trying hdaprm -d1 -X15 at the moment. It has been running for 40 
hours now and gotten as far as 27047040/39082680. So far it looks like I 
only get 'eepro100: wait_for_cmd_done timeout!' but no IDE errors.

Sometimes I am getting a kernel Aiiii followed by a kernel panic saying 
something like 'Trying to kill interrupt handler'. I just haven't been 
albe to reproduce it for this mail.

I am happy to do other testing if  someone tells me what to do. Just 
bear in mind that though being an experienced Linux administrator I am 
nothing close to a kernel developer. ;-)

Best regards
Andree

 

Console output snippet:

hde: dma_rtimer_expiry: dma status == 0x21
hde: timeout waiting for DMA
PDC202XX: Primary channel reset.
hde: timeout waiting for DMA
hde: (__ide_dma_test_irq) called while not waiting
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }

hde: drive not ready for command
hde: status timeout: status=0xd0 { Busy }

PDC202XX: Primary channel reset.
hde: drive not ready for command
ide2: reset: success

eepro100: wait_for_cmd_done timeout!
(repeated many times)

hda: timeout waiting for DMA
hda: timeout waiting for DMA
hda: (__ide_dma_test_irq) called while not waiting
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }

hda: drive not ready for command
hda: status timeout: status=0xd0 { Busy }

hda: no DRQ after issueing write
ide0: reset: success


 


Motherboard: Gigabyte GA-7DPXW+
Chipset: AMD-760MPX
RAID: PDC20276
CPU: 2 x AthlonMP 1800+


             reply	other threads:[~2002-09-22 21:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-22 21:50 Andree Leidenfrost [this message]
2002-09-24 21:40 Andree Leidenfrost

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=3D8E3B1A.5050800@harmsconsulting.com \
    --to=andree.leidenfrost@harmsconsulting.com \
    --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

all inboxes | Powered by JetHome®