public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Xavier Bru  <Xavier.Bru@bull.net>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] null pointer in iosapic_pci_fixup()
Date: Mon, 26 Nov 2001 16:17:26 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805543@msgid-missing> (raw)

When a device is found behind a pci/pci bridge and this device has no
IRQ decribed in the ACPI table, Linux prints a warning  message: 
" PCI: Couldn't map irq for (...)"
unfortunately there is a null "bridge" pointer at that point. This makes the
system hang in release 2.4.9 and have a wrong print of bus , device
and irq in kernel 2.4.13.

A posssible patch could be:

--- linux-2.4.13-ori/arch/ia64/kernel/iosapic.c	Mon Nov 26 17:09:49 2001
+++ linux-2.4.13-new/arch/ia64/kernel/iosapic.c	Mon Nov 26 16:42:40 2001
@@ -615,8 +615,8 @@
 					       pin, vector);
 				else
 					printk(KERN_WARNING
-					       "PCI: Couldn't map irq for (B%d,I%d,P%d)o\n",
-					       bridge->bus->number, PCI_SLOT(bridge->devfn),
+					       "PCI: Couldn't map irq for (B%d,I%d,P%d)\n",
+					       dev->bus->number, PCI_SLOT(dev->devfn),
 					       pin);
 			}
 			if (vector >= 0) {

-- 

 Sincères salutations.
_____________________________________________________________________
 
Xavier BRU                 BULL ISD/R&D/INTEL office:     FREC B1-422
tel : +33 (0)4 76 29 77 45                    http://www-frec.bull.fr
fax : +33 (0)4 76 29 77 70                 mailto:Xavier.Bru@bull.net
addr: BULL, 1 rue de Provence, BP 208, 38432 Echirolles Cedex, FRANCE
_____________________________________________________________________


             reply	other threads:[~2001-11-26 16:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26 16:17 Xavier Bru [this message]
2001-11-27  0:25 ` [Linux-ia64] null pointer in iosapic_pci_fixup() David Mosberger

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=marc-linux-ia64-105590698805543@msgid-missing \
    --to=xavier.bru@bull.net \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox