Messages in this thread | | | Date | Wed, 11 Jun 2003 09:56:38 +0200 | From | Helge Hafting <> | Subject | Re: 2.5.70-bk radeonfb oops on boot. |
| |
Simon Fowler wrote: > 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 . . .
It isn't merely radeonfb. A machine with matroxfb dies the same death, pci_enable_device_bars() oopses before the framebuffer even comes up with 2.5.70-mm7.
Helge Hafting
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |