From: "Bjørn Forbord" <bforbord@broadpark.no>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Clemens Ladisch <clemens@ladisch.de>,
Joel bourrigaud <joel@bourrigaud.info>,
linux1394-devel@lists.sf.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: ohci: do not bind to Pinnacle or Fujitsu HCI, prevent panic
Date: Mon, 11 Jul 2011 01:30:47 +0200 [thread overview]
Message-ID: <4E1A3627.9020606@broadpark.no> (raw)
In-Reply-To: <20110711012422.1e585783@stein>
I saw these mails just now and it's late. I will check my machine and
answer tomorrow
Best regards
Bjørn
Den 11. juli 2011 01:24, skrev Stefan Richter:
> When firewire-ohci is bound to a Pinnacle MovieBoard, eventually a
> "Register access failure" is logged and an interrupt storm or a kernel
> panic happens. https://bugzilla.kernel.org/show_bug.cgi?id=36622
>
> Until this is sorted out (if that is going to succeed at all), let's
> just prevent firewire-ohci from touching these devices.
>
> This device with link layer PCI IDs 11bd:0015 and 1394 PHY IDs
> 00000e:086613 is apparently a Fujitsu MB86613 --- hence the PHY IDs.
> Therefore, blacklist the MB86613 too (PCI IDs 10cf:200c). We only check
> the vendor ID because there is no other Fujitsu OHCI-1394 PCI device
> known besides this one.
>
> Signed-off-by: Stefan Richter<stefanr@s5r6.in-berlin.de>
> Cc:<stable@kernel.org>
> ---
> Supersedes patch "firewire: ohci: do not bind to Pinnacle cards, prevent panic"
>
> drivers/firewire/ohci.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> Index: b/drivers/firewire/ohci.c
> ===================================================================
> --- a/drivers/firewire/ohci.c
> +++ b/drivers/firewire/ohci.c
> @@ -260,6 +260,8 @@ static inline struct fw_ohci *fw_ohci(st
>
> static char ohci_driver_name[] = KBUILD_MODNAME;
>
> +#define PCI_VENDOR_ID_FUJITSU 0x10cf
> +#define PCI_VENDOR_ID_PINNACLE_SYSTEMS 0x11bd
> #define PCI_DEVICE_ID_AGERE_FW643 0x5901
> #define PCI_DEVICE_ID_JMICRON_JMB38X_FW 0x2380
> #define PCI_DEVICE_ID_TI_TSB12LV22 0x8009
> @@ -3202,6 +3204,12 @@ static int __devinit pci_probe(struct pc
> int i, err;
> size_t size;
>
> + if (dev->vendor == PCI_VENDOR_ID_FUJITSU ||
> + dev->vendor == PCI_VENDOR_ID_PINNACLE_SYSTEMS) {
> + dev_err(&dev->dev, "Controller type is not yet supported\n");
> + return -ENOSYS;
> + }
> +
> ohci = kzalloc(sizeof(*ohci), GFP_KERNEL);
> if (ohci == NULL) {
> err = -ENOMEM;
>
>
next prev parent reply other threads:[~2011-07-11 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110604002938.78c85881@stein>
[not found] ` <20110604010625.1a37638e@stein>
[not found] ` <4DEA697A.1090104@bourrigaud.info>
[not found] ` <20110612145303.2099aa81@stein>
[not found] ` <4DF4FF4F.4020607@bourrigaud.info>
[not found] ` <20110612210111.3e979131@stein>
[not found] ` <4DF528CF.50407@bourrigaud.info>
[not found] ` <20110709235410.08004e5d@stein>
2011-07-09 22:23 ` [PATCH] firewire: ohci: do not bind to Pinnacle cards, prevent panic Stefan Richter
[not found] ` <4E1A161D.1050304@ladisch.de>
2011-07-10 23:24 ` [PATCH] firewire: ohci: do not bind to Pinnacle or Fujitsu HCI, " Stefan Richter
2011-07-10 23:30 ` Bjørn Forbord [this message]
2011-07-10 23:50 ` Stefan Richter
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=4E1A3627.9020606@broadpark.no \
--to=bforbord@broadpark.no \
--cc=clemens@ladisch.de \
--cc=joel@bourrigaud.info \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sf.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox