Messages in this thread | | | Subject | Re: [PATCH] Oops in framebuffer code. | Date | Fri, 13 Nov 1998 03:31:29 +0000 | From | David Woodhouse <> |
| |
dwmw2@devel2.axiom.internal said: > With vesafb in 2.1.127, there's no fb_pan_display routine set, but > fbmem.c tries to call it upon a FBIOPAN_DISPLAY ioctl without first > checking that it's present. Not good.
> Patch not compiled or tested, and it's probably in vger anyway, but > what the hell...
Patch not working. Arse.
Adding a printk() just before the offending line seemed to fix it, which is odd. Then it just oopsed in fb_mmap instead, which is annoying. I'm fairly sure I'm using the right System.map - after all, I only compiled the damn thing five minutes ago.
I'll take another look {in the morning,later,when I regain consciousness}.
3:30 am isn't the best time to be trying to work this stuff out.
---- ---- ---- David Woodhouse David.Woodhouse@mvhi.com Office: (+44) 1223 810302 Project Leader, Process Information Systems Mobile: (+44) 976 658355 Axiom (Cambridge) Ltd., Swaffham Bulbeck, Cambridge, CB5 0NA, UK. finger dwmw2@ferret.lmh.ox.ac.uk for PGP key.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |