February 2010 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] pvops kernel repos for Opensuse 11.2 available?
by 0bo0 02 Feb '10

02 Feb '10

Are any of the Kernel repos, available for Opensuse 11.2, pvops kernels? these, http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.2 although quite recent -- atm kernel-xen-2.6.33-rc5.5.1.x86_64 -- appear to be forward-port patched Xen kernels ... thanks. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 2

[opensuse-kernel] Kernel:HEAD v2.6.33-rc6.6.1builds failing since 1/30
by 0bo0 02 Feb '10

02 Feb '10

> in case of problems that last longer than 24 hours, please report them to Jan Blunck <jblunck(a)suse.de> @ https://build.opensuse.org/project/monitor?project=Kernel%3AHEAD novell-kmp & kernel-xen packages have been failing to build for a number of days, leaving them out of sync ... e.g., kernel-xen-2.6.33-rc5.5.1.x86_64.rpm 30-Jan-2010 09:34 33M Mirrors Metalink kernel-default-2.6.33-rc6.6.1.x86_64.rpm 31-Jan-2010 09:38 34M Mirrors Metalink hth. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] aufs crash in nfs3_proc_setattr with 2.6.27.39-0.2.1
by Hans-Peter Jansen 02 Feb '10

02 Feb '10

Dear Jeff, because of the need to use current hardware, I try to adapt a new kernel from 11.1 to an old (SuSE 9.3), but otherwise rock solid diskless setup. The basics are pretty simple. Mount two NFS3 filesystems, one with the distribution (ro), another node specific (rw) in initrd. Stable setup: kernel 2.6.11.4 with aufs 20070327 New setup: kernel 2.6.27.39 with aufs-cvs20081020-1.32.14 and aufs-20090126. While building the new kernel and initrd in the old environment went fine, it crashes consistently on mounting /proc early on boot (boot.localfs): + mount -fv -t proc proc /proc BUG: unable to handle kernel NULL pointer dereference at 00000021 IP: [<f9123ab9>] :nfs:nfs3_proc_setattr+0x89/0xf1 *pdpt = 0000000034527001 *pde = 0000000000000000 Oops: 0000 [#1] SMP last sysfs file: Modules linked in: nfs lockd nfs_acl af_packet sunrpc aufs(N) 3c59x r8169 forcedeth via_rhine 8139too mii e1000 Supported: No Pid: 539, comm: mount Tainted: G (2.6.27.39-0.2.1.aufs1-pae #1) EIP: 0060:[<f9123ab9>] EFLAGS: 00010202 CPU: 2 EIP is at nfs3_proc_setattr+0x89/0xf1 [nfs] EAX: 00000015 EBX: f444dd50 ECX: 00000000 EDX: 00000000 ESI: f444dd0c EDI: f444dd08 EBP: f444df64 ESP: f444dcf4 DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Process mount (pid: 539, ti=f444c000 task=f444b250 task.ti=f444c000) Stack: f4d7c8d0 f9159e48 f444dd18 f444dd50 00000000 00000000 00000001 00000000 7fffffff f4d7c7b0 f444df64 00000000 00000000 00000000 00000030 00000000 00000000 f9136760 f444df64 f4d7c8d0 f444dd50 f91181ab f4d7863c f444ddb8 Call Trace: [<f91181ab>] nfs_setattr+0xeb/0x107 [nfs] [<c01a3da2>] fnotify_change+0x1aa/0x302 [<f9481c3d>] call_notify_change+0xcd/0x140 [aufs] [<f9481d0f>] vfsub_fnotify_change+0x4f/0xc0 [aufs] [<f9481f2f>] vfsub_notify_change+0xf/0x20 [aufs] [<f949fa4a>] aufs_do_setattr+0x2ca/0x4d0 [aufs] [<c01a3d7a>] fnotify_change+0x182/0x302 [<c0191566>] sys_fchmod+0xa2/0xc7 [<c01048e2>] syscall_call+0x7/0xb [<b785dad1>] 0xb785dad1 ======================= Code: 15 f9 89 44 24 08 89 5c 24 0c 74 0b 68 a1 9d 13 f9 e8 fd 7b 00 c7 58 f6 45 01 20 74 19 8b 45 30 85 c0 74 0c 8b 40 70 85 c0 74 05 <8b> 40 0c eb 02 31 c0 89 44 24 10 66 c7 03 00 00 31 c9 a1 00 4b EIP: [<f9123ab9>] nfs3_proc_setattr+0x89/0xf1 [nfs] SS:ESP 0068:f444dcf4 ---[ end trace b4052108726180bb ]--- Since it crashes in an area, that you worked on with your aufs-fsetattr patch, I kindly ask you for advise. Any idea, why an innocent mount of /proc in an staggered nfs root filesystem could crash the kernel? Thanks in advance, Pete -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 3