early ioremap not working with 2.4.19-pre1-aa1 ?

early ioremap not working with 2.4.19-pre1-aa1 ?

Post by Martin J. Blig » Sun, 03 Mar 2002 08:50:09



I have code for the NUMA-Q systems that does an ioremap
as the first thing in smp_boot_cpus (ia32 tree). This seems to
work fine until I install the aa patches ... then it hangs in the
ioremap.

Has anyone got any idea why this might be? I'd really like to
test out the -aa vm patches on this box ... I can debug it some
more - just looking for an easy answer ;-)

Thanks,

Martin.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

early ioremap not working with 2.4.19-pre1-aa1 ?

Post by Andrea Arcangel » Sun, 03 Mar 2002 11:50:11



> I have code for the NUMA-Q systems that does an ioremap
> as the first thing in smp_boot_cpus (ia32 tree). This seems to
> work fine until I install the aa patches ... then it hangs in the
> ioremap.

this sounds like the same problem of the MXT patch. In short pte_alloc
and in turn ioremap was usable only after the initcalls.

Does this incremental patch fix it?  (untested)

--- 2.4.19pre1aa1/include/linux/highmem.h.~1~   Fri Mar  1 20:19:05 2002

 /* declarations for linux/mm/highmem.c */
 unsigned int nr_free_highpages(void);
+extern void init_kmap(void);

 extern struct buffer_head *create_bounce(int rw, struct buffer_head * bh_orig);

 #else /* CONFIG_HIGHMEM */

 static inline unsigned int nr_free_highpages(void) { return 0; }
+#define init_kmap() do { } while(0)

 static inline void *kmap(struct page *page) { return page_address(page); }

--- 2.4.19pre1aa1/init/main.c.~1~       Wed Feb 27 12:46:19 2002

        mem_init();
        kmem_cache_sizes_init();
        pgtable_cache_init();
+       init_kmap();

 #ifdef CONFIG_PERFMON
        perfmon_init();
--- 2.4.19pre1aa1/mm/highmem.c.~1~      Wed Feb 27 12:46:13 2002

 static wait_queue_head_t pkmap_map_wait[KM_NR_SERIES];

-static __init int init_kmap(void)
+void __init init_kmap(void)
 {
        int i;

 #endif
        return 0;
 }
-__initcall(init_kmap);

 static void flush_all_zero_pkmaps(void)
 {

Quote:

> Has anyone got any idea why this might be? I'd really like to
> test out the -aa vm patches on this box ... I can debug it some
> more - just looking for an easy answer ;-)

> Thanks,

> Martin.

Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

early ioremap not working with 2.4.19-pre1-aa1 ?

Post by Mikael Pettersso » Sun, 03 Mar 2002 22:20:06



>I have code for the NUMA-Q systems that does an ioremap
>as the first thing in smp_boot_cpus (ia32 tree). This seems to
>work fine until I install the aa patches ... then it hangs in the
>ioremap.

You may want to use the new boot-time ioremap, which is based
on the fixmap mechanism. It's included in 2.5.6-pre1; a separate
patch for 2.4.18 is available at
<http://www.csd.uu.se/~mikpe/linux/patches/2.4/>.

/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

early ioremap not working with 2.4.19-pre1-aa1 ?

Post by Martin J. Blig » Fri, 08 Mar 2002 11:00:17


Quote:>> I have code for the NUMA-Q systems that does an ioremap
>> as the first thing in smp_boot_cpus (ia32 tree). This seems to
>> work fine until I install the aa patches ... then it hangs in the
>> ioremap.

> this sounds like the same problem of the MXT patch. In short pte_alloc
> and in turn ioremap was usable only after the initcalls.

> Does this incremental patch fix it?  (untested)

Sorry for the slow test cycle - this works just great ... will
this make it back to your main tree?

Thanks very much for the patch,

Martin.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. 2.4.19-pre1-aa1 problems

 >
 > Mar  3 20:39:17 localhost kernel: Unable to handle kernel paging request at virtual address 04740010
 > Mar  3 20:39:17 localhost kernel: c01a078a
 > Mar  3 20:39:17 localhost kernel: *pde = 00000000
 > Mar  3 20:39:17 localhost kernel: Oops: 0000
 > Mar  3 20:39:17 localhost kernel: CPU:    0
 > Mar  3 20:39:17 localhost kernel: EIP:    0010:[sock_poll+30/40]    Tainted: P

 Which modules do you have loaded ?

--
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. domainname on Red Hat 7.2

3. 2.4.19-rc3-aa1 and FB Console

4. sum command

5. Severe problems with 2.4.19-rc2-aa1 on k6-II

6. magstripe card reader/writer under Linux ?

7. Kernel patching 2.4.19pre1 -> 2.4.19pre2

8. paperwhite monitor

9. 2.4.19-rc2 -> 2.4.19-rc3 : no more eth (fwd)

10. 3Ware ok 2.4.19, dies 2.4.19-ac4

11. Promise 20267 hangs with 2.4.19-pre3 and 2.4.19-pre3-ac3

12. 2.4.19-pre6aa1 (possible all kernel after 2.4.19-pre2) athlon PCI workaround

13. Kernel panic 2.4.19-pre6 AND 2.4.19-pre5-ac3 - More info - ksymoops