From: Simon Fowler <simon@himi.org>
To: Andrew Morton <akpm@digeo.com>
Cc: jsimmons@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: 2.5.70-bk radeonfb oops on boot.
Date: Wed, 11 Jun 2003 15:05:40 +1000 [thread overview]
Message-ID: <20030611050540.GD2852@himi.org> (raw)
In-Reply-To: <20030610211607.2bb55b41.akpm@digeo.com>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
On Tue, Jun 10, 2003 at 09:16:07PM -0700, Andrew Morton wrote:
> Simon Fowler <simon@himi.org> wrote:
> >
> > > > >
> > > > > 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.
> > > >
<snippage>
> Thanks for testing.
>
> All the initcall ordering of chardevs versus pci, pci versus pci and who
> knows what else is all bollixed up.
>
> Unfortunately I do not have the bandwidth to work on this.
Since this seems to be a showstopper for people using radeonfb,
getting the 'fix' above in might be a good idea . . .
Simon
--
PGP public key Id 0x144A991C, or http://himi.org/stuff/himi.asc
(crappy) Homepage: http://himi.org
doe #237 (see http://www.lemuria.org/DeCSS)
My DeCSS mirror: ftp://himi.org/pub/mirrors/css/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-11 4:52 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
2003-06-11 3:55 ` Simon Fowler
2003-06-11 4:16 ` Andrew Morton
2003-06-11 5:05 ` Simon Fowler [this message]
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=20030611050540.GD2852@himi.org \
--to=simon@himi.org \
--cc=akpm@digeo.com \
--cc=jsimmons@infradead.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 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.