The ubuntu/debian build of 2.6.36-rc1 from [1] doesn't boot on my macbook v.2.1. It's most likely not an EXT4 bug but I have no idea where to put it and cc people that probably know better. I am linking to a crappy cellphone shot of the oops, please see [2]. Unfortunately, due to the kernel-package in ubuntu being broken once again, I can't build myself, hence no bisecting. All I can say is that 2.6.35-rc2 from the same ppa works. Let me know if additional info is needed. Regards, Tobias [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.36-rc1-maverick/ [2] http://img841.imageshack.us/img841/6654/imag0030l.jpg
Not an ext4 or even filesystem bug; looks like it was going down an apparmor path (aa_alloc_task_context) when it oopsed. Unfortunately I don't know how to move a bug off the filesystem component.
Apologies, I obviously can't read a trace. I guess I could move this to another category, but have no idea where to.
Tobias, can you try booting with the kernel parameter of apparmor=0 If apparmor is causing the problem then, this wil disable apparmor and cause the kernel to fall back to just DAC.
Both rc1 and rc2 seem to oops regardless of apparmor being enabled or not. Please see [1] for a boot attempt of rc1 with apparmor disabled and [2] for a failed rc2 boot. I am actually not sure if apparmor was disabled on this rc2 boot, I tried several times and can only say that this is not the only trace that scrolls by, just the last one that stays on screen. Sorry for the horrible pics btw. [1]http://img819.imageshack.us/img819/221/imag0033qx.jpg [2]http://img842.imageshack.us/img842/4300/imag0037ij.jpg
Tobias, thanks for testing. It looks like apparmor is disabled in both. Can you provide some more detail about your setup?
Tobias, Can you clarify how the kernel packaging in ubuntu is broken, so we can look into fixing it.
Created attachment 28011 [details] lspci
John, wrt #5: This is a Macbook 2.1, I replaced RAM and HDD a while back. lscpi output attached. I have an OSX install on it that it never used, and Ubuntu 10.04. Ubuntu install consists of an unencrypted /boot partition and an encrypted partition where LVM provides / and /home. fdisk -l shows: /dev/sda1 1 26 204819+ ee GPT /dev/sda2 * 26 5248 41943040 af HFS / HFS+ /dev/sda3 5248 5308 487424 83 Linux /dev/sda4 5308 60802 445750272 ef EFI (FAT-12/16/32) mount: /dev/mapper/vg-root on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) none on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) none on /dev type devtmpfs (rw,mode=0755) none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) none on /dev/shm type tmpfs (rw,nosuid,nodev) none on /var/run type tmpfs (rw,nosuid,mode=0755) none on /var/lock type tmpfs (rw,noexec,nosuid,nodev) none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) /dev/mapper/vg-home on /home type ext4 (rw) /dev/sda3 on /boot type ext3 (rw) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) gvfs-fuse-daemon on /home/tobias/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=tobias) That said this is a stock setup. wrt #6: I think I am running into the same issue as described in [1]. People are saying it is fixed in maverick, so I am hoping for an upgrade or backport to lucid. What puzzles me is that the exact issue (trying to build a -git kernel) was reported to lkml from a maverick user [2], and the thread suggests that there are kernel patches available to fix this. Now I am unsure where if kernel-package or source itself are broken. Please let me know if there are things I can do to be of help (things that break my setup are no option unfortunately). [1] https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/58307 [2] http://marc.info/?t=128247993200002&r=1&w=2
FWIW, -rc3 does not oops during boot, so I guess this has been fixed. I am still getting ioctl errors related to dm, and screen resolution min gnome is wrong, but those are different issues as far as I understand.