From: "Nick Evgeniev" <nick@octet.com>
To: <linux-kernel@vger.kernel.org>
Subject: 2.4.19-pre8 ide bugs
Date: Fri, 24 May 2002 19:03:49 +0400 [thread overview]
Message-ID: <004101c20334$361b0b80$baefb0d4@nick> (raw)
Hi,
I've got the following problem with 2.4.19-pre8 &
ide-2.4.19-p7.all.convert.10.patch (w/o patch & I've more fatal problems
with sb & filesystem corruptions) kernel reports "kernel: bug: kernel timer
added twice at c01a7356." & panics.
Is it a known issue? What is the solution??? I remember that with 2.4.7 I
didn't have any ide errors... but it had reiserfs bugs...
Are there light at the end of ide nightmare?
Here is log:
>-------------------------------
May 24 12:19:48 vzhik kernel: hdg: drive_cmd: status=0xd0 { Busy }
May 24 12:19:48 vzhik kernel:
May 24 12:19:48 vzhik kernel: hdg: status timeout: status=0xd0 { Busy }
May 24 12:19:48 vzhik kernel:
May 24 12:19:49 vzhik kernel: hdg: DMA disabled
May 24 12:19:49 vzhik kernel: ide3: reset: success
May 24 12:19:49 vzhik kernel: PDC202XX: Secondary channel reset.
May 24 12:19:49 vzhik kernel: hdg: drive not ready for command
May 24 12:19:50 vzhik kernel: hde: timeout waiting for DMA
May 24 12:19:50 vzhik kernel: PDC202XX: Primary channel reset.
May 24 12:19:50 vzhik kernel: ide_dmaproc: chipset supported ide_dma_timeout
func only: 16
May 24 12:19:50 vzhik kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
May 24 12:19:50 vzhik kernel: hde: dma_intr: error=0x84 { DriveStatusError
BadCRC }
May 24 12:19:50 vzhik kernel: hde: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
May 24 12:19:50 vzhik kernel: hde: dma_intr: error=0x84 { DriveStatusError
BadCRC }
May 24 12:19:50 vzhik kernel: hde: timeout waiting for DMA
May 24 12:19:50 vzhik kernel: PDC202XX: Primary channel reset.
May 24 12:19:50 vzhik kernel: ide_dmaproc: chipset supported ide_dma_timeout
func only: 16
May 24 12:19:50 vzhik kernel: hde: status timeout: status=0xd1 { Busy }
May 24 12:19:50 vzhik kernel:
May 24 12:19:50 vzhik kernel: PDC202XX: Primary channel reset.
May 24 12:19:50 vzhik kernel: hde: drive not ready for command
May 24 12:19:50 vzhik kernel: ide2: reset: success
May 24 12:24:24 vzhik kernel: hdg: ide_set_handler: handler not null;
old=c01a5234, new=c01a5234
May 24 12:24:24 vzhik kernel: bug: kernel timer added twice at c01a7356.
next reply other threads:[~2002-05-24 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 15:03 Nick Evgeniev [this message]
2002-05-24 15:35 ` Alan Cox
2002-05-25 11:23 ` Nick Evgeniev
2002-05-25 5:00 ` Andre Hedrick
2002-05-25 23:22 ` Matthias Andree
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='004101c20334$361b0b80$baefb0d4@nick' \
--to=nick@octet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@octet.spb.ru \
/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®