vserver development mailing list: Re: [Vserver] stop vserver cause error/oops - with new debian 4.0 vserver kernel version

From: <daniel_at_hozac.com>
Date: Tue 09 Jan 2007 - 05:11:10 GMT
Message-ID: <34251.192.168.101.6.1168319470.squirrel@intranet>

> On Mon, Jan 08, 2007 at 11:05:50AM +0100, Oliver Paulus wrote:
>> Hello,
>>
>> I have used Linux kernel 2.6.17.13 with VServer 2.0.2.1 before -
>> everything worked correctly. Now I have installed the Debian 4.0
>> (Etch) vserver kernel 2.6.18-3-vserver-amd64. If I stop a specific
>> vserver instance with "vserver <name> stop" I get the following error:
>
> please try with a mainstream kernel, preferable one of
> the 2.2.0-rc* kernels, and mainstream util-vserver (0.30.212)
> if the issue remains, please let us know, otherwise please
> contact the debian maintainers about those issues ...
>
> TIA,
> Herbert

The Debian maintainers are aware, and it's the bug fixed in 2.0.2.2-rc9
(off by one cacct). From what I gathered, the most recent Debian snapshot
kernel should work fine, but I didn't quite understand how or where to get
it.

>
>> ---
>> Message from syslogd@hal9000 at Mon Jan 8 10:55:37 2007 ...
>> hal9000 kernel: Oops: 0002 [5] SMP
>>
>> Message from syslogd@hal9000 at Mon Jan 8 10:55:37 2007 ...
>> hal9000 kernel: CR2: ffff82180f7411a6
>> /usr/lib/util-vserver/vserver.functions: line 895: 16787 Getötet
>> $_VWAIT --timeout "$VSHELPER_SYNC_TIMEOUT" --status-fd 3 "$2"
>> >>$_is_tmpdir/out
>> 2>$_is_tmpdir/err 3>$_is_tmpdir/fifo
>> /usr/lib/util-vserver/vserver.stop: line 85: 16794 Getötet
>> "${NICE_CMD[@]}" ${USE_VNAMESPACE:+$_VNAMESPACE --enter "$S_CONTEXT" --
>> }
>> $_VCONTEXT $SILENT_OPT --migrate --chroot --xid "$S_CONTEXT" --
>> "${INITCMD_STOP[@]}"
>> internal error: 'vwait' exited with an unexpected status ''; I will
>> try to continue but be prepared for unexpected events.
>>
>> Message from syslogd@hal9000 at Mon Jan 8 10:55:37 2007 ...
>> hal9000 kernel: Oops: 0000 [6] SMP
>>
>> Message from syslogd@hal9000 at Mon Jan 8 10:55:37 2007 ...
>> hal9000 kernel: CR2: ffff82180f74119e
>>
>> ---
>> here is the content of /var/log/messages:
>>
>> Jan 8 10:55:37 hal9000 kernel: PGD 0
>> Jan 8 10:55:37 hal9000 kernel: CPU 0
>> Jan 8 10:55:37 hal9000 kernel: Modules linked in: ipv6 dm_snapshot
>> dm_mirror
>> dm_mod loop snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore
>> snd_page_alloc pcspkr serio_raw psmouse shpchp pci_hotplug evdev ext3
>> jbd
>> mbcache raid1 md_mod ide_generic sd_mod ide_cd cdrom sata_sil libata
>> scsi_mod
>> via_rhine mii ehci_hcd uhci_hcd via82cxxx generic ide_core processor
>> Jan 8 10:55:37 hal9000 kernel: Pid: 16787, comm: vwait Not tainted
>> 2.6.18-3-vserver-amd64 #1
>> Jan 8 10:55:37 hal9000 kernel: RIP: 0010:[<ffffffff802474d2>]
>> [<ffffffff802474d2>] add_wait_queue+0x29/0x43
>> Jan 8 10:55:37 hal9000 kernel: RSP: 0018:ffff810016c71ee8 EFLAGS:
>> 00010002
>> Jan 8 10:55:37 hal9000 kernel: RAX: ffff810016c71f20 RBX:
>> ffff810016c71f08 RCX:
>> ffff81000f741190
>> Jan 8 10:55:37 hal9000 kernel: RDX: ffff82180f74119e RSI:
>> 0000000000000246 RDI:
>> ffff81000f741188
>> Jan 8 10:55:37 hal9000 kernel: RBP: 00000000fffffffd R08:
>> 0000000000000000 R09:
>> 0000000000000000
>> Jan 8 10:55:37 hal9000 kernel: R10: 000000000040189a R11:
>> 0000000000000202 R12:
>> ffff81000f741188
>> Jan 8 10:55:37 hal9000 kernel: R13: 0000000000000033 R14:
>> 000000000000001e R15:
>> 0000000000000003
>> Jan 8 10:55:37 hal9000 kernel: FS: 00002b6e32afc6d0(0000)
>> GS:ffffffff8052f000(0000) knlGS:0000000000000000
>> Jan 8 10:55:37 hal9000 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
>> 000000008005003b
>> Jan 8 10:55:37 hal9000 kernel: CR2: ffff82180f7411a6 CR3:
>> 000000001376d000 CR4:
>> 00000000000006e0
>> Jan 8 10:55:37 hal9000 kernel: Process vwait (pid: 16787[#0],
>> threadinfo
>> ffff810016c70000, task ffff81001169c880)
>> Jan 8 10:55:37 hal9000 kernel: Stack: ffff810016c71f58
>> ffff81000f740000
>> 00007fffee1029e0 ffffffff802996d4
>> Jan 8 10:55:37 hal9000 kernel: 0000000000000000 ffff81001169c880
>> ffffffff8027fc81 0000000000000000
>> Jan 8 10:55:37 hal9000 kernel: 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000
>> Jan 8 10:55:37 hal9000 kernel: Call Trace:
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff802996d4>]
>> vc_wait_exit+0x5d/0x106
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff8027fc81>]
>> default_wake_function+0x0/0xe
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff80295f87>]
>> sys_vserver+0x4ab/0x59e
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff8025ab0e>]
>> system_call+0x7e/0x83
>> Jan 8 10:55:37 hal9000 kernel:
>> Jan 8 10:55:37 hal9000 kernel:
>> Jan 8 10:55:37 hal9000 kernel: Code: 48 89 42 08 48 89 53 18 48 89 48
>> 08 49 89
>> 44 24 08 5b 5b 41
>> Jan 8 10:55:37 hal9000 kernel: RSP <ffff810016c71ee8>
>> Jan 8 10:55:37 hal9000 kernel: <1>Unable to handle kernel paging
>> request at
>> ffff82180f74119e RIP:
>> Jan 8 10:55:37 hal9000 kernel: PGD 0
>> Jan 8 10:55:37 hal9000 kernel: CPU 0
>> Jan 8 10:55:37 hal9000 kernel: Modules linked in: ipv6 dm_snapshot
>> dm_mirror
>> dm_mod loop snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore
>> snd_page_alloc pcspkr serio_raw psmouse shpchp pci_hotplug evdev ext3
>> jbd
>> mbcache raid1 md_mod ide_generic sd_mod ide_cd cdrom sata_sil libata
>> scsi_mod
>> via_rhine mii ehci_hcd uhci_hcd via82cxxx generic ide_core processor
>> Jan 8 10:55:37 hal9000 kernel: Pid: 28327, comm: apache2 Not tainted
>> 2.6.18-3-vserver-amd64 #1
>> Jan 8 10:55:37 hal9000 kernel: RIP: 0010:[<ffffffff8027e45e>]
>> [<ffffffff8027e45e>] __wake_up_common+0x24/0x68
>> Jan 8 10:55:37 hal9000 kernel: RSP: 0018:ffff810011515cc8 EFLAGS:
>> 00010092
>> Jan 8 10:55:37 hal9000 kernel: RAX: 0000000000000292 RBX:
>> ffff81000f741188 RCX:
>> 0000000000000000
>> Jan 8 10:55:37 hal9000 kernel: RDX: 0000000000000001 RSI:
>> 0000000000000001 RDI:
>> ffff81000f741188
>> Jan 8 10:55:37 hal9000 kernel: RBP: ffff810011515cf8 R08:
>> ffff82180f74119e R09:
>> 0000000000000000
>> Jan 8 10:55:37 hal9000 kernel: R10: 0000000000000000 R11:
>> ffff8100130ed268 R12:
>> 0000000000000001
>> Jan 8 10:55:37 hal9000 kernel: R13: 0000000000000001 R14:
>> ffff81000f741188 R15:
>> 0000000000000000
>> Jan 8 10:55:37 hal9000 kernel: FS: 00002b6e32afc6d0(0000)
>> GS:ffffffff8052f000(0000) knlGS:0000000000000000
>> Jan 8 10:55:37 hal9000 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
>> 000000008005003b
>> Jan 8 10:55:37 hal9000 kernel: CR2: ffff82180f74119e CR3:
>> 00000000077fc000 CR4:
>> 00000000000006e0
>> Jan 8 10:55:37 hal9000 kernel: Process apache2 (pid: 28327[#51],
>> threadinfo
>> ffff810011514000, task ffff8100130ed140)
>> Jan 8 10:55:37 hal9000 kernel: Stack: 0000000100000000
>> ffff81000f741188
>> 0000000000000000 0000000000000001
>> Jan 8 10:55:37 hal9000 kernel: 0000000000000292 0000000000000001
>> ffff810011515d38 ffffffff8022d038
>> Jan 8 10:55:37 hal9000 kernel: 0000000000000020 ffff810011515d58
>> 0000000000000020 ffff8100010f4780
>> Jan 8 10:55:37 hal9000 kernel: Call Trace:
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff8022d038>]
>> __wake_up+0x38/0x4f
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff80214181>]
>> do_exit+0x901/0x948
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff80246e14>]
>> cpuset_exit+0x0/0x6c
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff8022a295>]
>> get_signal_to_deliver+0x4b0/0x4df
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff80228cb6>]
>> do_signal+0x55/0x751
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff80232404>]
>> lock_sock+0xa2/0xad
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff8023f839>] d_rehash+0x6a/0x80
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff802610ba>]
>> _spin_lock_bh+0x9/0x14
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff8022fb95>]
>> release_sock+0x13/0xaa
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff803d18bb>]
>> inet_accept+0xab/0xb7
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff8039837d>]
>> sys_accept+0x1b8/0x1ea
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff80220b9b>]
>> __up_read+0x13/0x8a
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff8025ab97>]
>> sysret_signal+0x1c/0x27
>> Jan 8 10:55:37 hal9000 kernel: [<ffffffff8025ae1b>]
>> ptregscall_common+0x67/0xac
>> Jan 8 10:55:37 hal9000 kernel:
>> Jan 8 10:55:37 hal9000 kernel:
>> Jan 8 10:55:37 hal9000 kernel: Code: 49 8b 18 eb 2a 49 8d 78 e8 45 8b
>> 68 e8 4c
>> 89 f9 8b 55 d0 8b
>> Jan 8 10:55:37 hal9000 kernel: RSP <ffff810011515cc8>
>> Jan 8 10:55:37 hal9000 kernel: <1>Fixing recursive fault but reboot is
>> needed!
>>
>> ---
>> additional notes:
>> 1. other vserver instances can be stopped successfully.
>> 2. with the kernel 2.6.17.13-vs2.0.2.1 this failure does not appear.
>>
>> Regards
>> --
>> Oliver Paulus
>>
>> _______________________________________________
>> Vserver mailing list
>> Vserver@list.linux-vserver.org
>> http://list.linux-vserver.org/mailman/listinfo/vserver
> _______________________________________________
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
>

--
Daniel Hokka Zakrisson
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Received on Tue Jan 9 05:41:46 2007