I am apparently having an out-of-memory event. I wouldn't think I'd be susceptible to that, but I don't think I can blame it on the kernel in any case.

However: the OOM killer has blown up. The system is totally unresponsive and the console is repeating this over and over forever:

Mem-info:
Normal per-cpu:
CPU    0: Hot: hi:  186, btch:  31 usd:  12   Cold: hi:   62, btch:  15 usd:  51
Active:84829 inactive:41008 dirty:0 writeback:0 unstable:0
 free:655 slab:3389 mapped:3 pagetables:1201 bounce:0
Normal free:2620kB min:2960kB low:3700kB high:4440kB active:339316kB inactive:164032kB present:548640kB pages_scanned:228230182 all_unreclaimable? yes
lowmem_reserve[]: 0 0
Normal: 1*4kB 1*8kB 17*16kB 11*32kB 1*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 0*2048kB 0*4096kB = 2620kB
Swap cache: add 1158766, delete 1158766, find 2060666/2215923, race 5+107
Free swap  = 0kB
Total swap = 263160kB
Free swap:            0kB
138240 pages of RAM
0 pages of HIGHMEM
3950 reserved pages
573 pages shared
0 pages swap cached
printk: 27627 messages suppressed.
cron invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
1e297cb0:  [<080693f2>] dump_stack+0x22/0x30
1e297cc8:  [<080b3cd9>] out_of_memory+0x109/0x140
1e297cf4:  [<080b51c5>] __alloc_pages+0x355/0x380
1e297d48:  [<080b7688>] __do_page_cache_readahead+0x128/0x1a0
1e297d84:  [<080b77f1>] do_page_cache_readahead+0x51/0x70
1e297da4:  [<080b1615>] filemap_fault+0x1f5/0x310
1e297de8:  [<080bed75>] __do_fault+0x55/0x3d0
1e297e2c:  [<080bf13e>] do_linear_fault+0x4e/0x50
1e297e50:  [<080bf39c>] handle_mm_fault+0xbc/0x2a0
1e297e84:  [<0806a52c>] handle_page_fault+0x13c/0x230
1e297eb8:  [<0806a887>] segv+0x177/0x2f0
1e297f6c:  [<0807e046>] handle_segv+0x56/0x60
1e297f90:  [<0807e856>] userspace+0x216/0x260
1e297fe4:  [<0806b434>] fork_handler+0x74/0x90
1e297ffc:  [<4000b080>] 0x4000b080

My bad. This happened on another of my Linodes which is actually still on UML. Nothing to do with the new Xen kernel which is still working fine on the Linode I have it on.

I've just switched to this new kernel on my Ubuntu 8.04. The only problem was that Apache failed to start on boot. After restarting the daemon everything was fine!

Performance-wise I didn't see much difference. Both RAM and CPU usage are still the same.

Booted into this kernel on my 360 earlier and noticed that it reports my memory incorrectly. If it helps, I'm on dallas111.

free -m -t

and

htop

reports 349MB of available memory while using the stable kernel, both reports 360MB of memory (as it should).

It was nice though, reporting that I'm only using 35MB/349MB versus 60MB/360MB which was the usual usage on the stable kernel.

Unfortunately, I can't tell if that was just a misreport or actually savings...

[root@ ~]# uname -a
Linux x.y.com 2.6.27.4-x86_64-linode3

when running

# /sbin/iptables -t mangle -A MANGLE_OUTPUT -p tcp --dport 80 -j TOS --set-tos Maximize-Throughput

the output is

iptables: Unknown error 18446744073709551615

i use this ruleset on other hosts (containing this rule), and haven't had this problem before.

Thanks,