Hi again, Am 02.09.2010 09:17, schrieb Wilhelm: > Hi, > > using 2.6.35.2 I get tons of the bug messages below: > > [ 1810.764109] BUG: scheduling while atomic: sh/11767/0x10000001 > [ 1810.765740] Modules linked in: ipt_MASQUERADE ipt_REDIRECT xt_owner > iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state > nf_conntrack xt_tcpudp iptable_filter ip_tables x_tables nfsd nfs lockd > nfs_acl auth_rpcgss sunrpc dummy aufs exportfs dm_crypt tpm_tis tpm > tpm_bios psmouse serio_raw pcspkr i2c_piix4 raid1 e1000 ahci libahci > [last unloaded: scsi_wait_scan] > [ 1810.782232] Pid: 11767, comm: sh Not tainted > 2.6.35.2-vs2.3.0.36.31-kmux--vs-aufs #1 > [ 1810.785920] Call Trace: > [ 1810.787243] [<c013305d>] __schedule_bug+0x5d/0x70 > [ 1810.789267] [<c04fcef2>] schedule+0x422/0x550 > [ 1810.790795] [<c04fd0fd>] _cond_resched+0x2d/0x50 > [ 1810.792373] [<c01c0819>] anon_vma_prepare+0x19/0x130 > [ 1810.794064] [<c01bc6c8>] expand_downwards+0x18/0x160 > [ 1810.795588] [<c012dea7>] ? kmap_atomic_prot+0x47/0xe0 > [ 1810.797191] [<c01b6d6d>] ? __pte_alloc+0x3d/0xb0 > [ 1810.798689] [<c01bc818>] expand_stack+0x8/0x10 > [ 1810.800178] [<c01ba709>] handle_mm_fault+0xb29/0xb80 > [ 1810.801693] [<c01b6a1e>] ? follow_page+0x5e/0x2e0 > [ 1810.803251] [<c01ba85e>] __get_user_pages+0xfe/0x3f0 > [ 1810.804802] [<c01babeb>] get_user_pages+0x4b/0x60 > [ 1810.806477] [<c01e070d>] get_arg_page+0x4d/0xa0 > [ 1810.807975] [<c0300de6>] ? strnlen_user+0x26/0x50 > [ 1810.810472] [<c01e0832>] copy_strings+0xd2/0x180 > [ 1810.812098] [<c01e0904>] copy_strings_kernel+0x24/0x40 > [ 1810.813643] [<c01e2d82>] do_execve+0x182/0x250 > [ 1810.815154] [<c0109882>] sys_execve+0x32/0x70 > [ 1810.816647] [<c0102fc2>] ptregs_execve+0x12/0x20 > [ 1810.818273] [<c04fee5c>] ? syscall_call+0x7/0xb > [ 1846.268122] BUG: scheduling while atomic: sh/11810/0x10000001 > > Is this a known issue? > > this bug should be fixed in stable version 2.6.35.4. When do we see the vserver-patches for this version? -- Wilhelm