public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.5.19] Oops during PCI scan on Alpha
Date: Mon, 3 Jun 2002 14:27:27 +1000	[thread overview]
Message-ID: <20020603042727.GE2355@krispykreme> (raw)
In-Reply-To: <20020602200646.GB20788@lug-owl.de>

 
> Trace; fffffc00003c9f04 <device_register+144/1c0>
> Trace; fffffc00003c4e18 <pci_scan_device+118/160>
> Trace; fffffc00003c4f0c <pci_scan_slot+ac/180>
> Trace; fffffc00003c5060 <pci_do_scan_bus+80/140>
> Trace; fffffc00003c53a0 <pci_scan_bus+40/80>
> Trace; fffffc00003100f8 <init+18/200>
> Trace; fffffc0000310748 <kernel_thread+28/90>
> Trace; fffffc0000324448 <printk+228/280>
> Trace; fffffc00003100a8 <rest_init+28/60>
> Trace; fffffc00003100e0 <init+0/200>
> Trace; fffffc0000310730 <kernel_thread+10/90>

On ppc64 I found that pcibios_init was being called before
pci_driver_init, maybe its happening on alpha too. I am using the
following hack for the moment, I'll leave it to Patrick to fix it properly.

Anton

===== drivers/pci/pci-driver.c 1.10 vs edited =====
--- 1.10/drivers/pci/pci-driver.c	Fri May 31 06:10:44 2002
+++ edited/drivers/pci/pci-driver.c	Sat Jun  1 09:46:37 2002
@@ -192,7 +192,7 @@
 	return bus_register(&pci_bus_type);
 }
 
-subsys_initcall(pci_driver_init);
+arch_initcall(pci_driver_init);
 
 EXPORT_SYMBOL(pci_match_device);
 EXPORT_SYMBOL(pci_register_driver);

  reply	other threads:[~2002-06-03  4:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-02 20:06 [2.5.19] Oops during PCI scan on Alpha Jan-Benedict Glaw
2002-06-03  4:27 ` Anton Blanchard [this message]
2002-06-03  3:39   ` David S. Miller
2002-06-04 15:50     ` Patrick Mochel
2002-06-04 17:07       ` Ivan Kokshaysky
2002-06-04 18:58         ` Patrick Mochel
2002-06-04 18:26           ` Benjamin Herrenschmidt
2002-06-05 14:20           ` Ivan Kokshaysky
2002-06-04 18:13       ` David S. Miller
2002-06-04 19:38         ` Patrick Mochel
2002-06-04 19:42           ` David S. Miller
2002-06-04 20:56             ` Tom Rini
2002-06-04 21:10             ` Patrick Mochel
2002-06-04 21:14               ` David S. Miller
2002-06-04 21:14                 ` Patrick Mochel
2002-06-04 21:23                   ` David S. Miller
2002-06-04 21:29                     ` Patrick Mochel
2002-06-04 21:34                       ` David S. Miller
2002-06-04 22:03                         ` Patrick Mochel
2002-06-04 22:06                           ` Patrick Mochel
2002-06-05 14:23                           ` Ivan Kokshaysky
2002-06-05 22:29                             ` David S. Miller
2002-06-06  0:01                             ` Patrick Mochel
2002-06-06 13:22                               ` Ivan Kokshaysky
2002-06-23 17:03       ` Jan-Benedict Glaw

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=20020603042727.GE2355@krispykreme \
    --to=anton@samba.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox