[Vserver] stop vserver cause error/oops - with new debian 4.0 vserver kernel version
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 stop" I get the following error: --- Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ... hal9000 kernel: Oops: 0002 [5] SMP Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ... hal9000 kernel: CR2: 82180f7411a6 /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 "[EMAIL PROTECTED]" ${USE_VNAMESPACE:+$_VNAMESPACE --enter "$S_CONTEXT" -- } $_VCONTEXT $SILENT_OPT --migrate --chroot --xid "$S_CONTEXT" -- "[EMAIL PROTECTED]" internal error: 'vwait' exited with an unexpected status ''; I will try to continue but be prepared for unexpected events. Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ... hal9000 kernel: Oops: [6] SMP Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ... hal9000 kernel: CR2: 82180f74119e --- 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:[] [] add_wait_queue+0x29/0x43 Jan 8 10:55:37 hal9000 kernel: RSP: 0018:810016c71ee8 EFLAGS: 00010002 Jan 8 10:55:37 hal9000 kernel: RAX: 810016c71f20 RBX: 810016c71f08 RCX: 81000f741190 Jan 8 10:55:37 hal9000 kernel: RDX: 82180f74119e RSI: 0246 RDI: 81000f741188 Jan 8 10:55:37 hal9000 kernel: RBP: fffd R08: R09: Jan 8 10:55:37 hal9000 kernel: R10: 0040189a R11: 0202 R12: 81000f741188 Jan 8 10:55:37 hal9000 kernel: R13: 0033 R14: 001e R15: 0003 Jan 8 10:55:37 hal9000 kernel: FS: 2b6e32afc6d0() GS:8052f000() knlGS: Jan 8 10:55:37 hal9000 kernel: CS: 0010 DS: ES: CR0: 8005003b Jan 8 10:55:37 hal9000 kernel: CR2: 82180f7411a6 CR3: 1376d000 CR4: 06e0 Jan 8 10:55:37 hal9000 kernel: Process vwait (pid: 16787[#0], threadinfo 810016c7, task 81001169c880) Jan 8 10:55:37 hal9000 kernel: Stack: 810016c71f58 81000f74 7fffee1029e0 802996d4 Jan 8 10:55:37 hal9000 kernel: 81001169c880 8027fc81 Jan 8 10:55:37 hal9000 kernel: Jan 8 10:55:37 hal9000 kernel: Call Trace: Jan 8 10:55:37 hal9000 kernel: [] vc_wait_exit+0x5d/0x106 Jan 8 10:55:37 hal9000 kernel: [] default_wake_function+0x0/0xe Jan 8 10:55:37 hal9000 kernel: [] sys_vserver+0x4ab/0x59e Jan 8 10:55:37 hal9000 kernel: [] 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 Jan 8 10:55:37 hal9000 kernel: <1>Unable to handle kernel paging request at 82180f74119e 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:[] [] __wake_up_common+0x24/0x68 Jan 8 10:55:37 hal9000 kernel: RSP: 0018:810011515cc8 EFLAGS: 00010092 Jan 8 10:55:37 hal9000 kernel: RAX: 0292 RBX: 81000f741188 RCX: Jan 8 10:55:37 hal9000 kernel: RDX: 0001 RSI: 0001 RDI: 81000f741188 Jan 8 10:55:37 hal9000 kernel: RBP: 810011515cf8 R08: 82180f74119e R09: Jan 8 10:55:37 hal9000 kernel: R10: R11: 8100130ed268 R12: 0001 Jan 8 10:55:37 hal9000 kernel: R13: 0001 R14: 81000f741188 R15: Jan 8 10:55:37 hal9000 kernel: FS: 2b6e32afc6d0() GS:80
Re: [Vserver] stop vserver cause error/oops - with new debian 4.0 vserver kernel version
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 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 > --- > Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ... > hal9000 kernel: Oops: 0002 [5] SMP > > Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ... > hal9000 kernel: CR2: 82180f7411a6 > /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 > "[EMAIL PROTECTED]" ${USE_VNAMESPACE:+$_VNAMESPACE --enter "$S_CONTEXT" -- } > $_VCONTEXT $SILENT_OPT --migrate --chroot --xid "$S_CONTEXT" -- > "[EMAIL PROTECTED]" > internal error: 'vwait' exited with an unexpected status ''; I will > try to continue but be prepared for unexpected events. > > Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ... > hal9000 kernel: Oops: [6] SMP > > Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ... > hal9000 kernel: CR2: 82180f74119e > > --- > 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:[] > [] add_wait_queue+0x29/0x43 > Jan 8 10:55:37 hal9000 kernel: RSP: 0018:810016c71ee8 EFLAGS: 00010002 > Jan 8 10:55:37 hal9000 kernel: RAX: 810016c71f20 RBX: 810016c71f08 > RCX: > 81000f741190 > Jan 8 10:55:37 hal9000 kernel: RDX: 82180f74119e RSI: 0246 > RDI: > 81000f741188 > Jan 8 10:55:37 hal9000 kernel: RBP: fffd R08: > R09: > > Jan 8 10:55:37 hal9000 kernel: R10: 0040189a R11: 0202 > R12: > 81000f741188 > Jan 8 10:55:37 hal9000 kernel: R13: 0033 R14: 001e > R15: > 0003 > Jan 8 10:55:37 hal9000 kernel: FS: 2b6e32afc6d0() > GS:8052f000() knlGS: > Jan 8 10:55:37 hal9000 kernel: CS: 0010 DS: ES: CR0: > 8005003b > Jan 8 10:55:37 hal9000 kernel: CR2: 82180f7411a6 CR3: 1376d000 > CR4: > 06e0 > Jan 8 10:55:37 hal9000 kernel: Process vwait (pid: 16787[#0], threadinfo > 810016c7, task 81001169c880) > Jan 8 10:55:37 hal9000 kernel: Stack: 810016c71f58 81000f74 > 7fffee1029e0 802996d4 > Jan 8 10:55:37 hal9000 kernel: 81001169c880 > 8027fc81 > Jan 8 10:55:37 hal9000 kernel: > > Jan 8 10:55:37 hal9000 kernel: Call Trace: > Jan 8 10:55:37 hal9000 kernel: [] vc_wait_exit+0x5d/0x106 > Jan 8 10:55:37 hal9000 kernel: [] > default_wake_function+0x0/0xe > Jan 8 10:55:37 hal9000 kernel: [] sys_vserver+0x4ab/0x59e > Jan 8 10:55:37 hal9000 kernel: [] 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 > Jan 8 10:55:37 hal9000 kernel: <1>Unable to handle kernel paging request at > 82180f74119e 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:[] > [] __wake_up_common+0x24/0x68 > Jan 8 10:55:37 hal9000 kernel: RSP: 0018:810011515cc8 EFLAGS: 00010092 > Jan 8 10:55:37 hal9000 kernel: RAX:
Re: [Vserver] stop vserver cause error/oops - with new debian 4.0 vserver kernel version
> 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 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 [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ... >> hal9000 kernel: Oops: 0002 [5] SMP >> >> Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ... >> hal9000 kernel: CR2: 82180f7411a6 >> /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 >> "[EMAIL PROTECTED]" ${USE_VNAMESPACE:+$_VNAMESPACE --enter "$S_CONTEXT" -- >> } >> $_VCONTEXT $SILENT_OPT --migrate --chroot --xid "$S_CONTEXT" -- >> "[EMAIL PROTECTED]" >> internal error: 'vwait' exited with an unexpected status ''; I will >> try to continue but be prepared for unexpected events. >> >> Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ... >> hal9000 kernel: Oops: [6] SMP >> >> Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ... >> hal9000 kernel: CR2: 82180f74119e >> >> --- >> 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:[] >> [] add_wait_queue+0x29/0x43 >> Jan 8 10:55:37 hal9000 kernel: RSP: 0018:810016c71ee8 EFLAGS: >> 00010002 >> Jan 8 10:55:37 hal9000 kernel: RAX: 810016c71f20 RBX: >> 810016c71f08 RCX: >> 81000f741190 >> Jan 8 10:55:37 hal9000 kernel: RDX: 82180f74119e RSI: >> 0246 RDI: >> 81000f741188 >> Jan 8 10:55:37 hal9000 kernel: RBP: fffd R08: >> R09: >> >> Jan 8 10:55:37 hal9000 kernel: R10: 0040189a R11: >> 0202 R12: >> 81000f741188 >> Jan 8 10:55:37 hal9000 kernel: R13: 0033 R14: >> 001e R15: >> 0003 >> Jan 8 10:55:37 hal9000 kernel: FS: 2b6e32afc6d0() >> GS:8052f000() knlGS: >> Jan 8 10:55:37 hal9000 kernel: CS: 0010 DS: ES: CR0: >> 8005003b >> Jan 8 10:55:37 hal9000 kernel: CR2: 82180f7411a6 CR3: >> 1376d000 CR4: >> 06e0 >> Jan 8 10:55:37 hal9000 kernel: Process vwait (pid: 16787[#0], >> threadinfo >> 810016c7, task 81001169c880) >> Jan 8 10:55:37 hal9000 kernel: Stack: 810016c71f58 >> 81000f74 >> 7fffee1029e0 802996d4 >> Jan 8 10:55:37 hal9000 kernel: 81001169c880 >> 8027fc81 >> Jan 8 10:55:37 hal9000 kernel: >> >> Jan 8 10:55:37 hal9000 kernel: Call Trace: >> Jan 8 10:55:37 hal9000 kernel: [] >> vc_wait_exit+0x5d/0x106 >> Jan 8 10:55:37 hal9000 kernel: [] >> default_wake_function+0x0/0xe >> Jan 8 10:55:37 hal9000 kernel: [] >> sys_vserver+0x4ab/0x59e >> Jan 8 10:55:37 hal9000 kernel: [] >> 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 >> Jan 8 10:55:37 hal9000 kernel: <1>Unable to handle kernel paging >> request at >> 82180f74119e 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 eh
Re: [Vserver] stop vserver cause error/oops - with new debian 4.0 vserver kernel version
On Tue, Jan 09, 2007 at 06:11:10AM +0100, [EMAIL PROTECTED] wrote: > > On Mon, Jan 08, 2007 at 11:05:50AM +0100, Oliver Paulus wrote: > >> > >> 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 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. Debian Etch is now frozen, so every package update into Etch is processed through debian-release team ... some new linux-2.6 (kernel) is scheduled: http://lists.debian.org/debian-release/2007/01/msg00085.html -- 5o Peter.Mann at tuke.sk ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver