Push out 2.6.38-linode31 this afternoon - would be great if I could get some feedback before pointing "Latest" to it!

Thanks,
-Chris

I've added the availability of 2.6.38-x86_64-linode17 as well.

So far so good with our internal testing. If there no objections, Latest will point to these momentarily.

-Chris

Done!

http://www.linode.com/kernels/

http://www.linode.com/kernels/rss.xml

-Chris

Might want to hold up on the x64 version - I got immediate fail on boot:

blkfront: xvda: barriers enabled
 xvda: unknown partition table
blkfront: xvdb: barriers enabled
Kernel panic - not syncing: No available IRQ to bind to: increase nr_irqs!

Pid: 1, comm: swapper Not tainted 2.6.38-x86_64-linode17 #1
Call Trace:
 [<ffffffff8141cc67>] ? panic+0x8c/0x195
 [<ffffffff811f2cd2>] ? find_unbound_irq+0x94/0x9b
 [<ffffffff811f2f2c>] ? bind_evtchn_to_irq+0x2d/0xb3
 [<ffffffff811f381a>] ? HYPERVISOR_event_channel_op+0x15/0x46
 [<ffffffff811f3476>] ? bind_evtchn_to_irqhandler+0x20/0x5a
 [<ffffffff8123a05e>] ? blkif_interrupt+0x0/0x21a
 [<ffffffff81239ac5>] ? talk_to_blkback+0x118/0x284
 [<ffffffff8123aad0>] ? blkfront_probe+0x217/0x240
 [<ffffffff811f6112>] ? xenbus_dev_probe+0x7e/0x10d
 [<ffffffff812310c2>] ? driver_probe_device+0xa7/0x136
 [<ffffffff8123119b>] ? __driver_attach+0x4a/0x66
 [<ffffffff81231151>] ? __driver_attach+0x0/0x66
 [<ffffffff812306ed>] ? bus_for_each_dev+0x4e/0x83
 [<ffffffff81230f0d>] ? driver_attach+0x19/0x1b
 [<ffffffff81230b6f>] ? bus_add_driver+0xb1/0x1fe
 [<ffffffff81aaadec>] ? xlblk_init+0x0/0x7a
 [<ffffffff8123144c>] ? driver_register+0x98/0x109
 [<ffffffff81aaadec>] ? xlblk_init+0x0/0x7a
 [<ffffffff811f5fac>] ? xenbus_register_driver_common+0x24/0x26
 [<ffffffff811f6616>] ? __xenbus_register_frontend+0x29/0x42
 [<ffffffff81aaadec>] ? xlblk_init+0x0/0x7a
 [<ffffffff81aaae64>] ? xlblk_init+0x78/0x7a
 [<ffffffff81002080>] ? do_one_initcall+0x7a/0x134
 [<ffffffff81a86702>] ? kernel_init+0x15f/0x1e4
 [<ffffffff8100a764>] ? kernel_thread_helper+0x4/0x10
 [<ffffffff81009b73>] ? int_ret_from_sys_call+0x7/0x1b
 [<ffffffff8141ef21>] ? retint_restore_args+0x5/0x6
 [<ffffffff8100a760>] ? kernel_thread_helper+0x0/0x10

EDIT:
Always the same message, but the failure point seems a little random:

blkfront: xvda: barriers enabled
 xvda: unknown partition table
blkfront: xvdb: barriers enabled
 xvdb: unknown partition table
Setting capacity to 1482752
xvdb: detected capacity change from 0 to 759169024
blkfront: xvdc: barriers enabled
Kernel panic - not syncing: No available IRQ to bind to: increase nr_irqs!

brd: module loaded
loop: module loaded
blkfront: xvda: barriers enabled
Kernel panic - not syncing: No available IRQ to bind to: increase nr_irqs!

Why the rush to put this latest? Is there a bad kernel bug out there?

Interesting. I booted just fine on your very host - even with a couple extra disk images.

I've made a change - can you try once more?

-Chris

Yep - boots just fine now

Great! I guess CONFIG_SPARSE_IRQ is broken then. Thanks!

I've tried to reboot yesterday on the 2.6.38 kernel and the drbd device didn't show up as if it hasn't been compiled while it was there in the two latest revisions.
I rolled back to last revision (2.6.35) and everything worked again,
didn't tried since.
Have you removed it in your latest config?
Regards
Vincent

This post is vague to the point of uselessness, but a couple days ago someone popped in IRC saying something or other might be missing from 2.6.38. It was never 100% confirmed, and I don't remember what it was now, though...

_________________
Matt Nordhoff (aka Peng on IRC)

Probably related to this this post? viewtopic.php?t=6865&highlight=tun the 64 bit kernels don't have tun built in.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue