William Lee Irwin III wrote:
>> This sounds like a real problem. What happens if you move VMALLOC_START
>> to where it was in 2.4.x?
On Sat, Jan 15, 2005 at 10:24:42PM -0600, Bob Breuer wrote:
> Yes, changing it back fixes my problem for now.
> The bitkeeper comments say it was changed 4 months ag
William Lee Irwin III wrote:
Bob Breuer wrote:
At this point, I am guessing that some pte's allocated for the
framebuffer are being wrongly re-used when loading the module.
On Sat, Jan 15, 2005 at 08:25:35PM -0600, Bob Breuer wrote:
The cg14 driver is not remapping the framebuffer, and is using t
Bob Breuer wrote:
>> At this point, I am guessing that some pte's allocated for the
>> framebuffer are being wrongly re-used when loading the module.
On Sat, Jan 15, 2005 at 08:25:35PM -0600, Bob Breuer wrote:
> The cg14 driver is not remapping the framebuffer, and is using the mappings
> that w
Bob Breuer wrote:
At this point, I am guessing that some pte's allocated for the
framebuffer are being wrongly re-used when loading the module.
The cg14 driver is not remapping the framebuffer, and is using the mappings
that were setup by the prom and recreated in linux from
srmmu_inherit_prom_
Badness in map_area_pte at mm/vmalloc.c:126
[f0062a8c : map_area_pud+0x50/0xac ] [f0062c20 : map_vm_area+0x94/0xd0 ]
[f00631bc : __vmalloc+0xe0/0x134 ] [f0048124 : load_module+0x38/0x9dc ]
[f0048b3c : sys_init_module+0x74/0x2dc ] [f0010cdc :
syscall_is_too_hard+0x34/0x40 ] [00020df8 : 0x20df8 ]
