public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shane Shrybman <shrybman@aei.ca>
To: mingo@elte.hu, linux-kernel <linux-kernel@vger.kernel.org>
Cc: svetljo@gmx.de, alan@lxorguk.ukuu.org.uk
Subject: VP and Promise dma_timer_expiry: dma status == 0x24 error
Date: Thu, 07 Oct 2004 11:44:11 -0400	[thread overview]
Message-ID: <1097163851.5796.65.camel@mars> (raw)

Hi Ingo, Alan, Svetoslav,

I have finally made a bit of progress in narrowing down the source of
the Promise ide controller dma_timer_expiry errors in recent -mm/VP
kernels.

I have copied Svetoslav Slavtchev because he was also experiencing the
problem, (What is your current status re this issue Svetoslav?). And
Alan because he was responding to other folks regarding this error
message.

hdg: dma_timer_expiry: dma status == 0x24
PDC202XX: Secondary channel reset.
hdg: DMA interrupt recovery
hdg: lost interrupt
[..many repeats..never recovers..]

I got side tracked when recent -mm started spontaneously rebooting
during bootup. I resolved that by switching from gcc 2.95 to 3.2.3.

Now, 2.6.9-rc3mm2T1 with acpi=off (with the ivtv driver) has been
running OK for 24 hours.

<wild guess>
kernel: ** PCI interrupts are no longer routed automatically.  If this
kernel: ** causes a device to stop working, it is probably because the
kernel: ** driver failed to call pci_enable_device().  As a temporary
kernel: ** workaround, the "pci=routeirq" argument restores the old
kernel: ** behavior.  If this argument makes the device work again,
kernel: ** please email the output of "lspci" to bjorn.helgaas@hp.com
kernel: ** so I can fix the driver.

I see the above in the logs and a quick grep of pdc202xx_new.c shows no
call to pci_enable_device. Could this possibly be the source of the
problem?

Regards,

Shane





                 reply	other threads:[~2004-10-07 15:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1097163851.5796.65.camel@mars \
    --to=shrybman@aei.ca \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=svetljo@gmx.de \
    /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