From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: "joram.agten@pandora.be" <joram.agten@pandora.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel 2.4 pdc202xx and kernel 2.6 pdc202xx_old Broken
Date: Sun, 10 Apr 2005 14:39:26 +0200 [thread overview]
Message-ID: <58cb370e0504100539274f5df7@mail.gmail.com> (raw)
In-Reply-To: <000701c53dc6$8246e3b0$0505a8c0@cheopsturbo>
Hi,
On Apr 10, 2005 2:12 PM, joram.agten@pandora.be <joram.agten@pandora.be> wrote:
> Hello
>
> please put me in CC
>
> I'm using a pdc20262 promise utra66 controller to manage 4 HD's, all 30GB
> and I put them in a software /dev/md/0 raid5 configuration
>
> recently I upgraded my kernel to linux-2.6.11-gentoo-r4 and also
> linux-2.6.11-gentoo-r5
> and the raid array would go offline with dma timeouts when putting load to
> it
>
> Apr 9 23:30:15 vennen hde: DMA timeout error
> Apr 9 23:30:15 vennen hde: dma timeout error: status=0x58 { DriveReady
> SeekComplete DataRequest }
> Apr 9 23:30:15 vennen
> Apr 9 23:30:15 vennen ide: failed opcode was: unknown
> Apr 9 23:30:15 vennen hdh: dma_timer_expiry: dma status == 0x62
> Apr 9 23:30:15 vennen hdh: DMA timeout error
> Apr 9 23:30:15 vennen hdh: dma timeout error: status=0x58 { DriveReady
> SeekComplete DataRequest }
> Apr 9 23:30:15 vennen
> Apr 9 23:30:15 vennen ide: failed opcode was: unknown
> Apr 9 23:30:15 vennen hdg: status timeout: status=0xd0 { Busy }
> Apr 9 23:30:15 vennen
> Apr 9 23:30:15 vennen ide: failed opcode was: unknown
> Apr 9 23:30:15 vennen hdg: DMA disabled
> Apr 9 23:30:15 vennen PDC202XX: Secondary channel reset.
> Apr 9 23:30:15 vennen PDC202XX: Primary channel reset.
This is a buggy expiry handler but it gets triggered as a result of
earlier OOPS:
Apr 9 23:30:01 vennen Call Trace:
Apr 9 23:30:01 vennen [] _spin_lock+0x16/0x90
Apr 9 23:30:01 vennen [] _spin_unlock+0xd/0x30
Apr 9 23:30:01 vennen [] do_truncate+0x4a/0x70
Apr 9 23:30:01 vennen [] _spin_unlock_irqrestore+0xf/0x30
Apr 9 23:30:01 vennen [] do_coredump+0x1fd/0x216
Apr 9 23:30:01 vennen [] __dequeue_signal+0xf5/0x1b0
Apr 9 23:30:01 vennen [] dequeue_signal+0x35/0xd0
Apr 9 23:30:01 vennen [] get_signal_to_deliver+0x229/0x320
Apr 9 23:30:01 vennen [] do_signal+0x9b/0x130
Apr 9 23:30:01 vennen [] sys_rt_sigaction+0xaa/0xc0
Apr 9 23:30:01 vennen [] do_page_fault+0x0/0x5d5
Apr 9 23:30:01 vennen [] do_notify_resume+0x37/0x3c
Apr 9 23:30:01 vennen [] work_notifysig+0x13/0x15
which doesn't seem to be related to IDE in any way.
It would be useful if you pinpoint issue further to a specific kernel version.
Bartlomiej
prev parent reply other threads:[~2005-04-10 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 12:12 PROBLEM: kernel 2.4 pdc202xx and kernel 2.6 pdc202xx_old Broken joram.agten
2005-04-10 12:39 ` Bartlomiej Zolnierkiewicz [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=58cb370e0504100539274f5df7@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=joram.agten@pandora.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.