[04:24] <Tim42> I think I found a bug in 2.6.31-xx-powerpc, but I want to make sure its a bug (and not my own stupidity).
[05:52] <holstein> hey guys.. if i have kernel 2.6.32-16-generic
[05:53] <holstein> and i want to test something with the mainline kernel
[05:53] <holstein> which one from...
[05:53] <holstein> http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=D;O=A
[05:53] <holstein> should i get?
[06:26] <crimsun> holstein: meaning which one most closely is the basis?
[06:26] <jjohansen> holstein: 2.6.32.9 would be the closest
[06:26] <holstein> http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html
[06:26] <holstein> yup
[06:26] <holstein> i should have said
[06:27] <holstein> i got linked the map over in #ubuntu+1
[06:27] <crimsun> my timing is spectacular :-)
[06:27] <holstein> hehe
[06:27] <jjohansen> but it would also be worth testing 2.6.33
[22:37] <dyek> Hi! I'm using Debian Squeeze's kernel to boot Ubuntu 9.10's DomU (cause that is the only kernel that works with Xen for me so far). If I were to use Debian Squeeze's initrd, I get this error: "No filesystem could mount root, tried:", "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)". I suspect that that was caused by Ext-4 FS used on Ubuntu 9.10. I'm now trying to use Ubuntu 9.10's initrd, but copy Debian Squeeze's
[22:37] <dyek>  initrd's lib/modules/2.6.32-trunk-686-bigmem directory into my Ubuntu-based custom initrd. I'm still getting the same error. Is there any tips if my approach can work and what other steps I need to carry out before it will work?
[23:24] <jjohansen> dyek: which 9.10 kernel specifically?
[23:25] <dyek> jjohansen: initrd.img-2.6.31-16-generic.
[23:27] <dyek> jjohansen: Debian Squeeze's vmlinuz-2.6.32-trunk-686-bigmem kernel, though, works with Xen (3.4.2 -- rather recent version.)
[23:27] <jjohansen> err modules in, lib/modules/2.6.32-trunk-686-bigmem won't work with a 2.6.31-16 kernel
[23:28] <jjohansen> ext4 should be builtin to the 2.6.31-16 kernel
[23:29] <dyek> jjohansen: OK. So, kernel module can never be moved to another minor version of kernel? Or with just a minor version difference, there is some chance that a kernel module will work with another kernel?
[23:29] <jjohansen> generally no, its based off of the abi
[23:30] <jjohansen> when building a kernel an abi "signature" is created and that has to match
[23:30] <jjohansen> so even just changing config options can result in a kernel that needs different modules
[23:31] <dyek> jjohansen: OK. So, the signature is the key! Thanks! ... I was told that "unknown-block(0,0)" means missing hdd-driver not FS.
[23:31] <jjohansen> dyek: right that is probably the hdd driver
[23:32] <jjohansen> but you mentioned 9.10 ext4 above
[23:32] <jjohansen> have you tried a lucid kernel?
[23:32] <jjohansen> its 2.6.32 based, and karmic will run ontop of the lucid kernel
[23:33] <dyek> jjohansen: Yeah...I could only guess as I don't understand enough. Lucid kernel? Any pointer to it?
[23:34] <dyek> https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kernel-decision
[23:35] <jjohansen> http://packages.ubuntu.com/lucid/admin/
[23:35] <jjohansen> look for linux-image
[23:35] <jjohansen> or you can grab the source from the git tree
[23:36] <dyek> Thanks!
[23:38] <dyek> http://lxr.linux.no/#linux+v2.6.33/Documentation/x86/boot.txt
[23:38] <dyek> Protocol 2.10: (Kernel 2.6.31) Added a protocol for relaxed alignment beyond the kernel_alignment added, new init_size and pref_address fields. Added extended boot loader IDs.
[23:39] <dyek> jjohansen:  Do you think if this change could be why I had problems booting 2.6.31 as Xen DomU? (And that maybe it is fixed in 2.6.32?)
[23:40] <jjohansen> dyek: unlikely
[23:41] <dyek> OK! Thanks!