Hi, Tried out 2.6.14.2 on my x86 server, and it died within 4 or 5 days. This is the last thing in the logs: <1>Unable to handle kernel paging request at virtual address bffeda2c c0143f58 Modules linked in: ipt_state ipt_MASQUERADE ppp_deflate zlib_deflate zlib_inflate bsd_comp ipt_LOG iptable_mangle sch_ingress cls_u32 sch_sfq sch_cbq iptable_nat ip_nat ipt_REJECT iptable_filter ip_tables ppp_async crc_ccitt ppp_generic slhc e1000 tulip ip_conntrack_irc i2c_dev via686a hwmon i2c_isa i2c_core hostap_pci hostap ieee80211_crypt CPU: 0 EIP: 0060:[page_check_address+56/96] Not tainted VLI EFLAGS: 00010202 (2.6.14-influx) EIP is at page_check_address+0x38/0x60 eax: bffeda2c ebx: c127cda0 ecx: 00000a2c edx: c017cbdd esi: c1000000 edi: c32c1ed8 ebp: d3d7db6c esp: d3d7db30 ds: 007b es: 007b ss: 0068 Process pdflush (pid: 81, threadinfo=d3d7c000 task=c13b3070) Stack: bfa8b000 d3e725f4 c0143fd8 c127cda0 c32c1ed8 bfa8b000 d3e725f4 d3e925e0 00000000 c127cda0 c0144082 c127cda0 d3e725f4 d3d7db6c 00000001 00000001 c127cda0 00000001 c033facc d3d7dbfc c01441f0 c127cda0 00000001 c127cda0 Call Trace: [page_referenced_one+88/192] page_referenced_one+0x58/0xc0 [page_referenced_anon+66/128] page_referenced_anon+0x42/0x80 [page_referenced+112/160] page_referenced+0x70/0xa0 [refill_inactive_zone+261/960] refill_inactive_zone+0x105/0x3c0 [shrink_zone+188/256] shrink_zone+0xbc/0x100 [shrink_caches+95/128] shrink_caches+0x5f/0x80 [try_to_free_pages+234/448] try_to_free_pages+0xea/0x1c0 [__alloc_pages+469/992] __alloc_pages+0x1d5/0x3e0 [netif_receive_skb+317/448] netif_receive_skb+0x13d/0x1c0 [kmem_getpages+42/160] kmem_getpages+0x2a/0xa0 [cache_grow+265/416] cache_grow+0x109/0x1a0 [cache_alloc_refill+528/576] cache_alloc_refill+0x210/0x240 [kmem_cache_alloc+48/64] kmem_cache_alloc+0x30/0x40 [journal_alloc_journal_head+13/96] journal_alloc_journal_head+0xd/0x60 [journal_add_journal_head+51/192] journal_add_journal_head+0x33/0xc0 [journal_dirty_data+43/320] journal_dirty_data+0x2b/0x140 [ext3_journal_dirty_data+18/64] ext3_journal_dirty_data+0x12/0x40 [walk_page_buffers+92/128] walk_page_buffers+0x5c/0x80 [ext3_ordered_writepage+308/352] ext3_ordered_writepage+0x134/0x160 [journal_dirty_data_fn+0/32] journal_dirty_data_fn+0x0/0x20 [mpage_writepages+481/992] mpage_writepages+0x1e1/0x3e0 [ext3_ordered_writepage+0/352] ext3_ordered_writepage+0x0/0x160 [do_writepages+44/64] do_writepages+0x2c/0x40 [__sync_single_inode+78/512] __sync_single_inode+0x4e/0x200 [__writeback_single_inode+37/256] __writeback_single_inode+0x25/0x100 [dm_table_any_congested+17/128] dm_table_any_congested+0x11/0x80 [sync_sb_inodes+410/640] sync_sb_inodes+0x19a/0x280 [writeback_inodes+63/160] writeback_inodes+0x3f/0xa0 [background_writeout+118/192] background_writeout+0x76/0xc0 [pdflush+0/64] pdflush+0x0/0x40 [__pdflush+162/320] __pdflush+0xa2/0x140 [pdflush+29/64] pdflush+0x1d/0x40 [background_writeout+0/192] background_writeout+0x0/0xc0 [kthread+142/160] kthread+0x8e/0xa0 [kthread+0/160] kthread+0x0/0xa0 [kernel_thread_helper+5/28] kernel_thread_helper+0x5/0x1c Code: 5c 24 0c 8b 52 20 c1 e8 16 8b 04 82 a8 01 74 22 c1 e9 0a 25 00 f0 ff ff 81 e1 fc 0f 00 00 8b 35 10 8a 3b c0 8d 84 08 00 00 00 c0 <8b> 10 f6 c2 81 75 08 b8 fe ff ff ff 5b 5e c3 29 f3 c1 fb 05 c1 Fortunately, the data appears to be safe, rebooted into 2.6.12 and things are relatively well. Any idea where this oops could come from? Also: While 2.6.14 was booted I also received this during every exceution of my 5-minute cronjob 'pidof pppd > /dev/null || pon dsl-provider': <1>Unable to handle kernel paging request at virtual address decfe5fe printing eip: c017c448 *pde = 00000000 Oops: 0000 [#2] Modules linked in: ipt_state ipt_MASQUERADE ppp_deflate zlib_deflate zlib_inflate bsd_comp ipt_LOG iptable_mangle sch_ingress cls_u32 sch_sfq sch_cbq iptable_nat ip_nat ipt_REJECT iptable_filter ip_tables ppp_async crc_ccitt ppp_generic slhc e1000 tulip ip_conntrack_irc i2c_dev via686a hwmon i2c_isa i2c_core hostap_pci hostap ieee80211_crypt CPU: 0 EIP: 0060:[proc_exe_link+40/160] Not tainted VLI EFLAGS: 00010282 (2.6.14-influx) EIP is at proc_exe_link+0x28/0xa0 eax: d3e6bdf0 ebx: d3e6bdc0 ecx: d3e6bdf0 edx: decfe5e9 esi: ce23bf1c edi: c203fc4c ebp: 00000000 esp: ce23be28 ds: 007b es: 007b ss: 0068 Process pidof (pid: 12274, threadinfo=ce23a000 task=c69c9ab0) Stack: c203fda0 ce23bf1c c017decf c203fda0 ce23bf1c ce23bf20 c2bfab30 ce23bf1c c015a94e c2bfab30 ce23bf1c ce23a000 ce23a000 ce23a000 ce23bf1c 00000001 ce23a000 00000001 c013fe4f c7f1a040 c2bfab30 0024c5a3 00000003 c93f8008 Call Trace: [proc_pid_follow_link+79/128] proc_pid_follow_link+0x4f/0x80 [__link_path_walk+2734/3360] __link_path_walk+0xaae/0xd20 [__handle_mm_fault+207/288] __handle_mm_fault+0xcf/0x120 [link_path_walk+73/256] link_path_walk+0x49/0x100 [remove_vm_struct+76/96] remove_vm_struct+0x4c/0x60 [path_lookup+113/288] path_lookup+0x71/0x120 [__user_walk+35/64] __user_walk+0x23/0x40 [vfs_stat+23/96] vfs_stat+0x17/0x60 [remove_vm_struct+76/96] remove_vm_struct+0x4c/0x60 [sys_stat64+16/64] sys_stat64+0x10/0x40 [do_munmap+186/256] do_munmap+0xba/0x100 [sys_munmap+49/96] sys_munmap+0x31/0x60 [syscall_call+7/11] syscall_call+0x7/0xb Code: 90 90 90 56 53 8b 44 24 0c ff 70 f0 e8 12 68 f9 ff 85 c0 89 c3 5a 74 77 8d 48 30 89 c8 ff 00 0f 88 72 07 00 00 8b 13 85 d2 74 14 42 15 10 74 07 8b 42 4c 85 c0 75 28 8b 52 0c 85 d2 75 ec be (It goes without saying that I disabled the cronjob.) Is 2.6.14 just .. broken for me? My config is attached (MIME). Thanks! Please CC me on replies. -- Joshua Kwan