Messages in this thread | | | Date | Sat, 1 May 2004 18:31:02 +0800 (WST) | From | raven@themaw ... | Subject | Re: sparc64 2.6.6-rc2-mm2 build busted: usb/core/hub.c hubstatus |
| |
On Wed, 28 Apr 2004 raven@themaw.net wrote:
> On Wed, 28 Apr 2004, Dave Airlie wrote: > > > > > > > > > > > I'll investigate but I think that, either I need the fb device or > > > X -configure has it wrong. It thinks I have devices fb0 and fb1. > > > > leave in the "fb" device but don't enable direct rendering "ffb" device, > > not the extra f, if it still crashes with just the framebuffer and not the > > DRM then there is a framebuffer issue ... > > > > CONFIG_DRM_FFB should be n is probably the most straightforward way to > > check it isn't in there.. > > Did that and got simmilar oops. > > X -configure still insists I have BusID "SBUS:fb0" and "SBUS:fb1" devices. > If I configure BusID "sbus@1f,0/cgsix@0.0" and "sbus@1f,0/cgsix@2,0" as I > would in 2.4 X complains that it can't find the "SBUS:fbn" devices. >
Have tried to progress this.
As far as I can tell an oops occurs on this line
get_user(htransp, transp);
or on this line (if parameter kspc = 1)
htransp = transp ? *transp : 0xffff;
in fb_set_cmap.
It appears that transp (aka cmap->transp) is a bogus address.
Can someone who is familiar with this code give me a little insight into what I should expect to see here. Could there be some sort of reuse of a stale struct fbcmap here?
Ian
- 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/
| |