public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Simon Fowler <simon@himi.org>
Cc: jsimmons@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: 2.5.70-bk radeonfb oops on boot.
Date: Tue, 10 Jun 2003 20:16:41 -0700	[thread overview]
Message-ID: <20030610201641.220a4927.akpm@digeo.com> (raw)
In-Reply-To: <20030611021926.GA2241@himi.org>

Simon Fowler <simon@himi.org> wrote:
>
> On Tue, Jun 10, 2003 at 02:14:40PM -0700, Andrew Morton wrote:
> > Simon Fowler <simon@himi.org> wrote:
> > >
> > > On Tue, Jun 10, 2003 at 04:16:54PM +1000, Simon Fowler wrote:
> > > > I've started seeing a hard lockup on boot with my Fujitsu Lifebook
> > > > p2120 laptop, with a radeon mobility M6 LY, when using a Linus bk
> > > > kernel as of 2003-06-09 (possibly earlier - the last kernel I've
> > > > tested is bk as of 2003-06-04). lspci lists this hardware:
> > > > 
> > > I've narrowed the start of the problem down: 2.5.70-bk13 works,
> > > -bk14 oopses. 
> > 
> > That's funny.  bk13->bk14 was almost all arm stuff.  diffstat below.
> > 
> > It might be worth reverting this chunk, see if that fixes it:
> > 
> > --- b/drivers/char/mem.c        Thu Jun  5 23:36:40 2003
> > +++ b/drivers/char/mem.c        Sun Jun  8 05:02:24 2003
> > @@ -716 +716 @@
> > -__initcall(chr_dev_init);
> > +subsys_initcall(chr_dev_init);
> > 
> And we have a winner . . . Reverting this hunk fixes the oops.
> 

So it's another initcall problem in the PCI layer.

pci_enable_device_bars() is needing things which are not yet set up.  A lot
of the PCI initialisation is at subsys_initcall() as well, and you got
unlucky with link order.

I expect the below patch will fix this as well.  Could you please put the
above change back to normal and see if this one fixes it?


diff -puN arch/i386/pci/irq.c~pci-init-ordering-fix arch/i386/pci/irq.c
--- 25/arch/i386/pci/irq.c~pci-init-ordering-fix	Tue Jun 10 15:40:19 2003
+++ 25-akpm/arch/i386/pci/irq.c	Tue Jun 10 15:40:19 2003
@@ -791,7 +791,7 @@ static int __init pcibios_irq_init(void)
 	return 0;
 }
 
-subsys_initcall(pcibios_irq_init);
+arch_initcall(pcibios_irq_init);
 
 
 void pcibios_penalize_isa_irq(int irq)
diff -puN arch/i386/pci/legacy.c~pci-init-ordering-fix arch/i386/pci/legacy.c
--- 25/arch/i386/pci/legacy.c~pci-init-ordering-fix	Tue Jun 10 15:46:35 2003
+++ 25-akpm/arch/i386/pci/legacy.c	Tue Jun 10 15:46:47 2003
@@ -65,4 +65,4 @@ static int __init pci_legacy_init(void)
 	return 0;
 }
 
-subsys_initcall(pci_legacy_init);
+arch_initcall(pci_legacy_init);

_


  reply	other threads:[~2003-06-11  3:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-10  6:16 2.5.70-bk radeonfb oops on boot Simon Fowler
2003-06-10  6:36 ` Joshua Kwan
2003-06-10  6:48 ` Greg KH
2003-06-10  6:53   ` Simon Fowler
2003-06-10 13:02 ` Simon Fowler
2003-06-10 21:14   ` Andrew Morton
2003-06-11  2:19     ` Simon Fowler
2003-06-11  3:16       ` Andrew Morton [this message]
2003-06-11  3:55         ` Simon Fowler
2003-06-11  4:16           ` Andrew Morton
2003-06-11  5:05             ` Simon Fowler
2003-06-11  7:56               ` Helge Hafting
2003-06-10 13:24 ` Helge Hafting

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=20030610201641.220a4927.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simon@himi.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