All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: ohci1394 unhandled interrupts bug in 2.6.14-rc2
Date: Sat, 15 Oct 2005 14:59:12 -0700	[thread overview]
Message-ID: <20051015215912.GA11321@virtuousgeek.org> (raw)
In-Reply-To: <43516E78.6040502@s5r6.in-berlin.de>

On Sat, Oct 15, 2005 at 11:02:48PM +0200, Stefan Richter wrote:
> What about the PCI_CACHE_LINE_SIZE read/write?
> 
> Jody McIntyre wrote on 2005-02-09:
> | Can you try the fix without
> | pci_write_config_word(dev,PCI_CACHE_LINE_SIZE,toshiba_pcls);
> | or pci_read_config_word(dev,PCI_CACHE_LINE_SIZE,&toshiba_pcls);
> | and report if it still works?
> |
> | If it doesn't work, try leaving those lines out but adding
> | pci_clear_mwi(dev);
> | after the mdelay(), on the off chance that the device thinks mwi is on.
> |
> | The correct fix for this, if possible, is actually a pci quirk instead
> | of the dmi-based approach, but if reading PCI_CACHE_LINE_SIZE before
> | pci_enable_device() really is necessary, this will be rather difficult.
> [ http://marc.theaimsgroup.com/?l=linux1394-devel&m=110797909807519 ]

It looks like it is.

I removed the PCI_CACHE_LINE_SIZE read and write, and that didn't work.
I added in a pci_clear_mwi(dev) and that didn't work either.  It looks
like the whole patch that I posted earlier is required.

Thanks,
Jesse

  reply	other threads:[~2005-10-15 22:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 18:55 ohci1394 unhandled interrupts bug in 2.6.14-rc2 jbarnes
2005-10-15 19:39 ` Stefan Richter
2005-10-15 20:29   ` Jesse Barnes
2005-10-15 20:40     ` new PCI quirk for Toshiba Satellite? Jesse Barnes
2005-10-20  0:06       ` Greg KH
2005-10-20 18:32         ` Stefan Richter
2005-10-21 18:38           ` Jesse Barnes
2005-10-21 20:13             ` Stefan Richter
2005-10-24 17:45               ` Jesse Barnes
2005-10-24 18:07                 ` Jesse Barnes
2005-10-24 18:21                 ` Stefan Richter
2005-10-24 21:09                   ` Ivan Kokshaysky
2005-10-15 21:02     ` ohci1394 unhandled interrupts bug in 2.6.14-rc2 Stefan Richter
2005-10-15 21:59       ` Jesse Barnes [this message]
2005-10-17  7:55     ` Andrew Morton
2005-10-17  9:35       ` Stefan Richter
2005-10-17  9:42         ` Andrew Morton
2005-10-17 10:03           ` Stefan Richter
2005-10-17 16:30             ` Jesse Barnes
2005-10-17 18:50               ` Stefan Richter
2005-10-19 17:54                 ` Jesse Barnes
2005-10-17 12:48           ` rob
2005-10-17 15:58             ` Stefan Richter
2005-10-18  5:32               ` rob

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=20051015215912.GA11321@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.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 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.