Re: [Vserver] kernel bug
On Wednesday 06 December 2006 21:50, Herbert Poetzl wrote: > On Wed, Dec 06, 2006 at 12:11:44PM +0100, Andreas Baetz wrote: > > > On Tuesday 28 November 2006 15:54, Herbert Poetzl wrote: > > > > On Tue, Nov 28, 2006 at 08:11:35AM +0100, Andreas Baetz wrote: > > > > > On Sunday 26 November 2006 23:22, Herbert Poetzl wrote: > > > > > > On Fri, Nov 24, 2006 at 08:11:39AM +0100, Andreas Baetz wrote: > > > > > > > On Thursday 23 November 2006 18:49, Herbert Poetzl wrote: > > > > > > > > On Thu, Nov 23, 2006 at 02:43:13AM +0100, Herbert Poetzl wrote: > > > > > > > > > > > > > > > > > > thanks, should be fixed in the next release > > > > > > > > > > > > > > > > vs2.0.2.2-rc8 is out ... > > > > > > > > > > > > > > I tried vs2.0.2.2-rc8 with 2.6.18.3, the vserver starts ok, no > > > > > > > errors, but when I stopped it, the whole system freezed. > > > > > > > Right after "Deconfiguring network interfaces...done." > > > > > > > > > > > > okay, maybe you get around, the stack trace of > > > > > > all processes would probably tell us more ... > > > > > I wrote down some of the trace output by hand: > > > > > > > > hmm, the numbers of those dumps would be interesting, > > > > especially if you have an unstripped kernel (vmlinux) > > > > available, so we can figure _where_ this happens > > > > > > > > so a serial console or some other means of recording > > > > them would be very helpful, if not available, try > > > > with a photo camera ... > > > > > > > > some more info: > > I copied the / of a working vserver and used it as / of deb4. > > "vserver deb4 stop" now works. > > It seems that something inside the / of the old deb4 is causing > > the system to crash when no more processes are running with that xid. > > > So if a user of a certain vserver manages to create that condition in > > a vserver, then ending all processes in that vserver, the user could > > manage to crash the host. > > yes, please try if you can reproduce that with > > http://vserver.13thfloor.at/Experimental/patch-2.6.18.5-vs2.1.1.3.diff > > if yes, we should have the necessary debugging > harnish to track that down, if it can't be > recreated there, consider it already fixed in > the next stable release ... > > TIA, > Herbert > With 2.6.18.5 and patch-2.6.18.5-vs2.1.1.3.diff the bug is gone. Also, hard CPU scheduling works again. Great work, many thanks !!! Andreas ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. ** ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] kernel bug
On Wed, Dec 06, 2006 at 12:11:44PM +0100, Andreas Baetz wrote: > > On Tuesday 28 November 2006 15:54, Herbert Poetzl wrote: > > > On Tue, Nov 28, 2006 at 08:11:35AM +0100, Andreas Baetz wrote: > > > > On Sunday 26 November 2006 23:22, Herbert Poetzl wrote: > > > > > On Fri, Nov 24, 2006 at 08:11:39AM +0100, Andreas Baetz wrote: > > > > > > On Thursday 23 November 2006 18:49, Herbert Poetzl wrote: > > > > > > > On Thu, Nov 23, 2006 at 02:43:13AM +0100, Herbert Poetzl wrote: > > > > > > > > > > > > > > > > thanks, should be fixed in the next release > > > > > > > > > > > > > > vs2.0.2.2-rc8 is out ... > > > > > > > > > > > > I tried vs2.0.2.2-rc8 with 2.6.18.3, the vserver starts ok, no > > > > > > errors, but when I stopped it, the whole system freezed. > > > > > > Right after "Deconfiguring network interfaces...done." > > > > > > > > > > okay, maybe you get around, the stack trace of > > > > > all processes would probably tell us more ... > > > > I wrote down some of the trace output by hand: > > > > > > hmm, the numbers of those dumps would be interesting, > > > especially if you have an unstripped kernel (vmlinux) > > > available, so we can figure _where_ this happens > > > > > > so a serial console or some other means of recording > > > them would be very helpful, if not available, try > > > with a photo camera ... > > > > > > > I did some more tests: > > At console 1: > > host:~# vserver deb4 enter > > deb4:/# > > > > .. Then I stopped all services in deb4 .. > > > > deb4:/# ps ax > > PID TTY STAT TIME COMMAND > > 1 ?Ss 0:00 init [2] > > 4999 ?S+ 0:00 login > > 5023 pts/0Ss 0:00 /bin/bash -login > > 5043 pts/0R+ 0:00 ps ax > > > > At console 2: > > host:~# vps ax|grep 8004 > > 4999 8004 deb4 tty3 S+ 0:00 login > > > > 5023 8004 deb4 pts/0Ss+0:00 /bin/bash -login > > 5049 0 MAIN tty2 S+ 0:00 grep 8004 > > > > At console 1: > > deb4:/# > > > > EIP: [] 0xe2fd8894 SS:ESP 0068:e4711f20 > > <1>Fixing recursive fault but reboot is needed! > > host kernel: Oops: 0002 [#1] > > host kernel: PREEMPT > > host kernel: CPU:0 > > host kernel: EIP is at 0xe2fd8894 > > host kernel: eax: e2fd ebx: e2fd8930 ecx: 0001 edx: 0001 > > host kernel: esi: edi: e2fd8890 ebp: e4711f48 esp: e4711f20 > > host kernel: ds: 007b es: 007b ss: 0068 > > host kernel: Process vcontext (pid: 4638[#8004], ti=e471 task=e4334ab0 > > task.ti=e471) > > host kernel: Stack: c01195e3 e2fd 0001 0001 > > 0001 > > host kernel: 0001 0286 e4711f6c c011b1af > > 0001 e2fd8890 > > host kernel: e4711f9c e4334ab0 0010 c17efa90 c01224b9 > > c011ac30 > > host kernel: Call Trace: > > host kernel: Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 94 88 fd e2 > > <30> 89 fd e2 02 00 00 00 00 00 00 00 2f 65 74 63 2f 76 73 65 72 > > host kernel: EIP: [] 0xe2fd8894 SS:ESP 0068:e4711f20 > > some more info: > I copied the / of a working vserver and used it as / of deb4. > "vserver deb4 stop" now works. > It seems that something inside the / of the old deb4 is causing > the system to crash when no more processes are running with that xid. > So if a user of a certain vserver manages to create that condition in > a vserver, then ending all processes in that vserver, the user could > manage to crash the host. yes, please try if you can reproduce that with http://vserver.13thfloor.at/Experimental/patch-2.6.18.5-vs2.1.1.3.diff if yes, we should have the necessary debugging harnish to track that down, if it can't be recreated there, consider it already fixed in the next stable release ... TIA, Herbert > Andreas > > > ** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > ** > > ___ > 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
Re: [Vserver] kernel bug
Andreas Baetz wrote: On Tuesday 28 November 2006 15:54, Herbert Poetzl wrote: On Tue, Nov 28, 2006 at 08:11:35AM +0100, Andreas Baetz wrote: On Sunday 26 November 2006 23:22, Herbert Poetzl wrote: On Fri, Nov 24, 2006 at 08:11:39AM +0100, Andreas Baetz wrote: On Thursday 23 November 2006 18:49, Herbert Poetzl wrote: On Thu, Nov 23, 2006 at 02:43:13AM +0100, Herbert Poetzl wrote: thanks, should be fixed in the next release vs2.0.2.2-rc8 is out ... I tried vs2.0.2.2-rc8 with 2.6.18.3, the vserver starts ok, no errors, but when I stopped it, the whole system freezed. Right after "Deconfiguring network interfaces...done." okay, maybe you get around, the stack trace of all processes would probably tell us more ... I wrote down some of the trace output by hand: hmm, the numbers of those dumps would be interesting, especially if you have an unstripped kernel (vmlinux) available, so we can figure _where_ this happens so a serial console or some other means of recording them would be very helpful, if not available, try with a photo camera ... I did some more tests: At console 1: host:~# vserver deb4 enter deb4:/# .. Then I stopped all services in deb4 .. deb4:/# ps ax PID TTY STAT TIME COMMAND 1 ?Ss 0:00 init [2] 4999 ?S+ 0:00 login 5023 pts/0Ss 0:00 /bin/bash -login 5043 pts/0R+ 0:00 ps ax At console 2: host:~# vps ax|grep 8004 4999 8004 deb4 tty3 S+ 0:00 login 5023 8004 deb4 pts/0Ss+0:00 /bin/bash -login 5049 0 MAIN tty2 S+ 0:00 grep 8004 At console 1: deb4:/# EIP: [] 0xe2fd8894 SS:ESP 0068:e4711f20 <1>Fixing recursive fault but reboot is needed! host kernel: Oops: 0002 [#1] host kernel: PREEMPT host kernel: CPU:0 host kernel: EIP is at 0xe2fd8894 host kernel: eax: e2fd ebx: e2fd8930 ecx: 0001 edx: 0001 host kernel: esi: edi: e2fd8890 ebp: e4711f48 esp: e4711f20 host kernel: ds: 007b es: 007b ss: 0068 host kernel: Process vcontext (pid: 4638[#8004], ti=e471 task=e4334ab0 task.ti=e471) host kernel: Stack: c01195e3 e2fd 0001 0001 0001 host kernel: 0001 0286 e4711f6c c011b1af 0001 e2fd8890 host kernel: e4711f9c e4334ab0 0010 c17efa90 c01224b9 c011ac30 host kernel: Call Trace: host kernel: Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 94 88 fd e2 <30> 89 fd e2 02 00 00 00 00 00 00 00 2f 65 74 63 2f 76 73 65 72 host kernel: EIP: [] 0xe2fd8894 SS:ESP 0068:e4711f20 some more info: I copied the / of a working vserver and used it as / of deb4. "vserver deb4 stop" now works. It seems that something inside the / of the old deb4 is causing the system to crash when no more processes are running with that xid. So if a user of a certain vserver manages to create that condition in a vserver, then ending all processes in that vserver, the user could manage to crash the host. And what condition is that, exactly? Without a complete trace or at least a way to reproduce this, it's going to be pretty much impossible to fix it. Would it be possible for you to tar up the whole guest and upload it somewhere? Or setup a serial console so catch the previous Oops (which would hopefully have a usable stack trace)? -- Daniel Hokka Zakrisson GPG id: 06723412 GPG fingerprint: A455 4DF3 990A 431F FECA 7947 6136 DDA2 0672 3412 ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] kernel bug
> On Tuesday 28 November 2006 15:54, Herbert Poetzl wrote: > > On Tue, Nov 28, 2006 at 08:11:35AM +0100, Andreas Baetz wrote: > > > On Sunday 26 November 2006 23:22, Herbert Poetzl wrote: > > > > On Fri, Nov 24, 2006 at 08:11:39AM +0100, Andreas Baetz wrote: > > > > > On Thursday 23 November 2006 18:49, Herbert Poetzl wrote: > > > > > > On Thu, Nov 23, 2006 at 02:43:13AM +0100, Herbert Poetzl wrote: > > > > > > > > > > > > > > thanks, should be fixed in the next release > > > > > > > > > > > > vs2.0.2.2-rc8 is out ... > > > > > > > > > > I tried vs2.0.2.2-rc8 with 2.6.18.3, the vserver starts ok, no > > > > > errors, but when I stopped it, the whole system freezed. > > > > > Right after "Deconfiguring network interfaces...done." > > > > > > > > okay, maybe you get around, the stack trace of > > > > all processes would probably tell us more ... > > > I wrote down some of the trace output by hand: > > > > hmm, the numbers of those dumps would be interesting, > > especially if you have an unstripped kernel (vmlinux) > > available, so we can figure _where_ this happens > > > > so a serial console or some other means of recording > > them would be very helpful, if not available, try > > with a photo camera ... > > > > I did some more tests: > At console 1: > host:~# vserver deb4 enter > deb4:/# > > .. Then I stopped all services in deb4 .. > > deb4:/# ps ax > PID TTY STAT TIME COMMAND > 1 ?Ss 0:00 init [2] > 4999 ?S+ 0:00 login > 5023 pts/0Ss 0:00 /bin/bash -login > 5043 pts/0R+ 0:00 ps ax > > At console 2: > host:~# vps ax|grep 8004 > 4999 8004 deb4 tty3 S+ 0:00 login > > 5023 8004 deb4 pts/0Ss+0:00 /bin/bash -login > 5049 0 MAIN tty2 S+ 0:00 grep 8004 > > At console 1: > deb4:/# > > EIP: [] 0xe2fd8894 SS:ESP 0068:e4711f20 > <1>Fixing recursive fault but reboot is needed! > host kernel: Oops: 0002 [#1] > host kernel: PREEMPT > host kernel: CPU:0 > host kernel: EIP is at 0xe2fd8894 > host kernel: eax: e2fd ebx: e2fd8930 ecx: 0001 edx: 0001 > host kernel: esi: edi: e2fd8890 ebp: e4711f48 esp: e4711f20 > host kernel: ds: 007b es: 007b ss: 0068 > host kernel: Process vcontext (pid: 4638[#8004], ti=e471 task=e4334ab0 > task.ti=e471) > host kernel: Stack: c01195e3 e2fd 0001 0001 > 0001 > host kernel: 0001 0286 e4711f6c c011b1af 0001 > e2fd8890 > host kernel: e4711f9c e4334ab0 0010 c17efa90 c01224b9 > c011ac30 > host kernel: Call Trace: > host kernel: Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 94 88 fd e2 <30> > 89 fd e2 02 00 00 00 00 00 00 00 2f 65 74 63 2f 76 73 65 72 > host kernel: EIP: [] 0xe2fd8894 SS:ESP 0068:e4711f20 some more info: I copied the / of a working vserver and used it as / of deb4. "vserver deb4 stop" now works. It seems that something inside the / of the old deb4 is causing the system to crash when no more processes are running with that xid. So if a user of a certain vserver manages to create that condition in a vserver, then ending all processes in that vserver, the user could manage to crash the host. Andreas ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. ** ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] kernel bug
On Tuesday 28 November 2006 15:54, Herbert Poetzl wrote: > On Tue, Nov 28, 2006 at 08:11:35AM +0100, Andreas Baetz wrote: > > On Sunday 26 November 2006 23:22, Herbert Poetzl wrote: > > > On Fri, Nov 24, 2006 at 08:11:39AM +0100, Andreas Baetz wrote: > > > > On Thursday 23 November 2006 18:49, Herbert Poetzl wrote: > > > > > On Thu, Nov 23, 2006 at 02:43:13AM +0100, Herbert Poetzl wrote: > > > > > > > > > > > > thanks, should be fixed in the next release > > > > > > > > > > vs2.0.2.2-rc8 is out ... > > > > > > > > I tried vs2.0.2.2-rc8 with 2.6.18.3, the vserver starts ok, no > > > > errors, but when I stopped it, the whole system freezed. > > > > Right after "Deconfiguring network interfaces...done." > > > > > > okay, maybe you get around, the stack trace of > > > all processes would probably tell us more ... > > I wrote down some of the trace output by hand: > > hmm, the numbers of those dumps would be interesting, > especially if you have an unstripped kernel (vmlinux) > available, so we can figure _where_ this happens > > so a serial console or some other means of recording > them would be very helpful, if not available, try > with a photo camera ... > I did some more tests: At console 1: host:~# vserver deb4 enter deb4:/# .. Then I stopped all services in deb4 .. deb4:/# ps ax PID TTY STAT TIME COMMAND 1 ?Ss 0:00 init [2] 4999 ?S+ 0:00 login 5023 pts/0Ss 0:00 /bin/bash -login 5043 pts/0R+ 0:00 ps ax At console 2: host:~# vps ax|grep 8004 4999 8004 deb4 tty3 S+ 0:00 login 5023 8004 deb4 pts/0Ss+0:00 /bin/bash -login 5049 0 MAIN tty2 S+ 0:00 grep 8004 At console 1: deb4:/# EIP: [] 0xe2fd8894 SS:ESP 0068:e4711f20 <1>Fixing recursive fault but reboot is needed! host kernel: Oops: 0002 [#1] host kernel: PREEMPT host kernel: CPU:0 host kernel: EIP is at 0xe2fd8894 host kernel: eax: e2fd ebx: e2fd8930 ecx: 0001 edx: 0001 host kernel: esi: edi: e2fd8890 ebp: e4711f48 esp: e4711f20 host kernel: ds: 007b es: 007b ss: 0068 host kernel: Process vcontext (pid: 4638[#8004], ti=e471 task=e4334ab0 task.ti=e471) host kernel: Stack: c01195e3 e2fd 0001 0001 0001 host kernel: 0001 0286 e4711f6c c011b1af 0001 e2fd8890 host kernel: e4711f9c e4334ab0 0010 c17efa90 c01224b9 c011ac30 host kernel: Call Trace: host kernel: Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 94 88 fd e2 <30> 89 fd e2 02 00 00 00 00 00 00 00 2f 65 74 63 2f 76 73 65 72 host kernel: EIP: [] 0xe2fd8894 SS:ESP 0068:e4711f20 The same doesn't work with another vserver (deb3). With deb3, I can stop all services, then after CTRL-D there is no deb3 anymore in vserver-stat (I think that is how it is supposed to work) > > BUG: unable to handle kernel NULL pointer dereference at virtual > > address 0005 > > printing eip: > > c0104118 > > one of those addresses is listed above, you might > be able to get thre required info with: > > addr2line -e vmlinux c0104118 > > another option to identify the location is the code > sequence dumped at the end (2 digit block) > > TIA, > Herbert Andreas ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. ** ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] kernel bug
On Tue, Nov 28, 2006 at 08:11:35AM +0100, Andreas Baetz wrote: > On Sunday 26 November 2006 23:22, Herbert Poetzl wrote: > > On Fri, Nov 24, 2006 at 08:11:39AM +0100, Andreas Baetz wrote: > > > On Thursday 23 November 2006 18:49, Herbert Poetzl wrote: > > > > On Thu, Nov 23, 2006 at 02:43:13AM +0100, Herbert Poetzl wrote: > > > > > > > > > > thanks, should be fixed in the next release > > > > > > > > vs2.0.2.2-rc8 is out ... > > > > > > I tried vs2.0.2.2-rc8 with 2.6.18.3, the vserver starts ok, no > > > errors, but when I stopped it, the whole system freezed. > > > Right after "Deconfiguring network interfaces...done." > > > > okay, maybe you get around, the stack trace of > > all processes would probably tell us more ... > I wrote down some of the trace output by hand: hmm, the numbers of those dumps would be interesting, especially if you have an unstripped kernel (vmlinux) available, so we can figure _where_ this happens so a serial console or some other means of recording them would be very helpful, if not available, try with a photo camera ... > BUG: unable to handle kernel NULL pointer dereference at virtual > address 0005 > printing eip: > c0104118 one of those addresses is listed above, you might be able to get thre required info with: addr2line -e vmlinux c0104118 another option to identify the location is the code sequence dumped at the end (2 digit block) TIA, Herbert PS: would be interesting to see if you encounter the same issues with 2.1.1.2.3 (if you find the time to test) > *pde = > Kernel panic - not syncing: Fatal exception in interrupt > > after pressing sysrq-T: > > rb_insert_color > do_nanosleep > hrtimer_nanosleep > __fput > hrtimer_wakeup > sys_nanosleep > sysenter_past_esp > vserver S C01218db 0 23266 23227 23267 23269 23240 (NOTLB) > .. > Call Trace: > do_wait > __alloc_pages > kernel_fpu_begin > eligible_child > do_wait > do_sigaction > default_wake_function > sys_wait4 > sys_waitpid > syscall_call > vwait R running 0 23267 23266 (NOTLB) > rc R running 0 23269 23227 23266 (L-TLB) > > > > > TIA, > > Herbert > > > > Andreas > > > ** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > ** > > ___ > 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
Re: [Vserver] kernel bug
On Sunday 26 November 2006 23:22, Herbert Poetzl wrote: > On Fri, Nov 24, 2006 at 08:11:39AM +0100, Andreas Baetz wrote: > > On Thursday 23 November 2006 18:49, Herbert Poetzl wrote: > > > On Thu, Nov 23, 2006 at 02:43:13AM +0100, Herbert Poetzl wrote: > > > > > > > > thanks, should be fixed in the next release > > > > > > vs2.0.2.2-rc8 is out ... > > > > I tried vs2.0.2.2-rc8 with 2.6.18.3, the vserver starts ok, no > > errors, but when I stopped it, the whole system freezed. > > Right after "Deconfiguring network interfaces...done." > > okay, maybe you get around, the stack trace of > all processes would probably tell us more ... I wrote down some of the trace output by hand: BUG: unable to handle kernel NULL pointer dereference at virtual address 0005 printing eip: c0104118 *pde = Kernel panic - not syncing: Fatal exception in interrupt after pressing sysrq-T: rb_insert_color do_nanosleep hrtimer_nanosleep __fput hrtimer_wakeup sys_nanosleep sysenter_past_esp vserver S C01218db 0 23266 23227 23267 23269 23240 (NOTLB) .. Call Trace: do_wait __alloc_pages kernel_fpu_begin eligible_child do_wait do_sigaction default_wake_function sys_wait4 sys_waitpid syscall_call vwait R running 0 23267 23266 (NOTLB) rc R running 0 23269 23227 23266 (L-TLB) > > TIA, > Herbert > Andreas ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. ** ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] kernel bug
On Sunday 26 November 2006 23:22, Herbert Poetzl wrote: > On Fri, Nov 24, 2006 at 08:11:39AM +0100, Andreas Baetz wrote: > > On Thursday 23 November 2006 18:49, Herbert Poetzl wrote: > > > On Thu, Nov 23, 2006 at 02:43:13AM +0100, Herbert Poetzl wrote: > > > > > > > > thanks, should be fixed in the next release > > > > > > vs2.0.2.2-rc8 is out ... > > > > I tried vs2.0.2.2-rc8 with 2.6.18.3, the vserver starts ok, no > > errors, but when I stopped it, the whole system freezed. > > Right after "Deconfiguring network interfaces...done." > > hmm, on the guest or host? > if on the guest, what does the 'Deconfiguring' do? It's on the guest, a debian installation. /etc/init.d/networking: .. log_action_begin_msg "Deconfiguring network interfaces" if ifdown -a --exclude=lo; then log_action_end_msg $? else log_action_end_msg $? fi ;; .. In the meantime I found out that some other scripts are executed after the above, so this should be not the problem. I noticed something interesting, though: 1) I did put some delays (sleep) into some of the scripts in ../rc0.d to find out which is the source of the problem, and I think that the bug shows after a certain time and not after a certain command. 2) I have a vserver (deb3) that doesn't crash the machine when I do "vserver deb3 stop". The config files on the host for both vservers are identical. 3) Both vservers are running ok, the crash only occurs when trying to stop deb4, i.e. when deb4's rc0.d scripts are executed via /usr/lib/util-vserver/vserver.stop. > > > Nothing worked besides magic sysreq-boot. > > well, that is at least something ... > > would have been interesting to get a process dump > (which should work with SYSRQ-T) In the meantime I produced some of these crashes, and the kernel always reports something which has to do with interrupt handling, the reported process was always the one that was executed in the vserver's rc0.d script, for example "sleep" while testing with the delays mentioned above. > > > Nothing in the syslog. > > Didn't try a second time due o lack of time. > > okay, maybe you get around, the stack trace of > all processes would probably tell us more ... > > TIA, > Herbert > Andreas ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. ** ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] kernel bug
On Fri, Nov 24, 2006 at 08:11:39AM +0100, Andreas Baetz wrote: > On Thursday 23 November 2006 18:49, Herbert Poetzl wrote: > > On Thu, Nov 23, 2006 at 02:43:13AM +0100, Herbert Poetzl wrote: > > > On Wed, Nov 22, 2006 at 01:28:42PM +0100, Andreas Baetz wrote: > > > > Because of the CPU scheduling problems I have with 2.6.18.2 and vserver > > > > vs2.0.2.2-rc6 I tried > > > > 2.6.18.3 and vs2.0.2.2-rc7. > > > > The patch applied cleanly to a vanilla kernel. > > > > The kernel compiled ok. > > > > After booting I tried "vserver deb4 start", that failed and I got > > > > > > > > kernel BUG at kernel/vserver/network.c:147! > > > > host kernel: invalid opcode: [#2] > > > > host kernel: PREEMPT > > > > host kernel: CPU:0 > > > > host kernel: EIP is at unhash_nx_info+0x6e/0x90 > > > > host kernel: eax: 0100 ebx: f6c7eee0 ecx: 0001 edx: > > > > e8326000 > > > > host kernel: esi: e824ba90 edi: 0010 ebp: c17efa90 esp: > > > > e8327f64 > > > > host kernel: ds: 007b es: 007b ss: 0068 > > > > host kernel: Process chbind (pid: 4168[#0], ti=e8326000 task=e824ba90 > > > > task.ti=e8326000) > > > > host kernel: Stack: f6c7eee0 0004 e8327f9c c012296e f6c7eee0 > > > > ff00 e8f1da40 > > > > host kernel: e8327f9c e824bb48 e824bb80 ff00 e8f1da40 e824bb48 > > > > e8327f9c e8327f9c > > > > host kernel: 00ff 0401a8c0 e8326000 c0122a4d c01031e1 > > > > 00ff 0804c81b > > > > host kernel: Call Trace: > > > > host kernel: Code: 04 c7 03 00 01 10 00 c7 43 04 00 02 20 00 b8 01 00 > > > > 00 00 e8 e5 ed fd ff 89 e0 25 00 e0 ff ff 8b 40 08 a8 08 75 0f 83 c4 08 > > > > 5b c3 <0f> 0b 93 00 1f 5a 43 c0 eb b8 83 c4 08 5b e9 5f 54 2c 00 eb 0d > > > > host kernel: EIP: [] unhash_nx_info+0x6e/0x90 SS:ESP > > > > 0068:e8327f64 > > > > > > > > I'm back to 2.6.18.2 now. > > > > > > thanks, should be fixed in the next release > > > > vs2.0.2.2-rc8 is out ... > > I tried vs2.0.2.2-rc8 with 2.6.18.3, the vserver starts ok, no > errors, but when I stopped it, the whole system freezed. > Right after "Deconfiguring network interfaces...done." hmm, on the guest or host? if on the guest, what does the 'Deconfiguring' do? > Nothing worked besides magic sysreq-boot. well, that is at least something ... would have been interesting to get a process dump (which should work with SYSRQ-T) > Nothing in the syslog. > Didn't try a second time due o lack of time. okay, maybe you get around, the stack trace of all processes would probably tell us more ... TIA, Herbert > Andreas > > > ** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > ** > > ___ > 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
Re: [Vserver] kernel bug
On Thursday 23 November 2006 18:49, Herbert Poetzl wrote: > On Thu, Nov 23, 2006 at 02:43:13AM +0100, Herbert Poetzl wrote: > > On Wed, Nov 22, 2006 at 01:28:42PM +0100, Andreas Baetz wrote: > > > Because of the CPU scheduling problems I have with 2.6.18.2 and vserver > > > vs2.0.2.2-rc6 I tried > > > 2.6.18.3 and vs2.0.2.2-rc7. > > > The patch applied cleanly to a vanilla kernel. > > > The kernel compiled ok. > > > After booting I tried "vserver deb4 start", that failed and I got > > > > > > kernel BUG at kernel/vserver/network.c:147! > > > host kernel: invalid opcode: [#2] > > > host kernel: PREEMPT > > > host kernel: CPU:0 > > > host kernel: EIP is at unhash_nx_info+0x6e/0x90 > > > host kernel: eax: 0100 ebx: f6c7eee0 ecx: 0001 edx: > > > e8326000 > > > host kernel: esi: e824ba90 edi: 0010 ebp: c17efa90 esp: > > > e8327f64 > > > host kernel: ds: 007b es: 007b ss: 0068 > > > host kernel: Process chbind (pid: 4168[#0], ti=e8326000 task=e824ba90 > > > task.ti=e8326000) > > > host kernel: Stack: f6c7eee0 0004 e8327f9c c012296e f6c7eee0 > > > ff00 e8f1da40 > > > host kernel: e8327f9c e824bb48 e824bb80 ff00 e8f1da40 e824bb48 > > > e8327f9c e8327f9c > > > host kernel: 00ff 0401a8c0 e8326000 c0122a4d c01031e1 > > > 00ff 0804c81b > > > host kernel: Call Trace: > > > host kernel: Code: 04 c7 03 00 01 10 00 c7 43 04 00 02 20 00 b8 01 00 00 > > > 00 e8 e5 ed fd ff 89 e0 25 00 e0 ff ff 8b 40 08 a8 08 75 0f 83 c4 08 5b > > > c3 <0f> 0b 93 00 1f 5a 43 c0 eb b8 83 c4 08 5b e9 5f 54 2c 00 eb 0d > > > host kernel: EIP: [] unhash_nx_info+0x6e/0x90 SS:ESP > > > 0068:e8327f64 > > > > > > I'm back to 2.6.18.2 now. > > > > thanks, should be fixed in the next release > > vs2.0.2.2-rc8 is out ... I tried vs2.0.2.2-rc8 with 2.6.18.3, the vserver starts ok, no errors, but when I stopped it, the whole system freezed. Right after "Deconfiguring network interfaces...done." Nothing worked besides magic sysreq-boot. Nothing in the syslog. Didn't try a second time due to lack of time. Andreas ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. ** ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] kernel bug
On Thu, Nov 23, 2006 at 02:43:13AM +0100, Herbert Poetzl wrote: > On Wed, Nov 22, 2006 at 01:28:42PM +0100, Andreas Baetz wrote: > > Because of the CPU scheduling problems I have with 2.6.18.2 and vserver > > vs2.0.2.2-rc6 I tried > > 2.6.18.3 and vs2.0.2.2-rc7. > > The patch applied cleanly to a vanilla kernel. > > The kernel compiled ok. > > After booting I tried "vserver deb4 start", that failed and I got > > > > kernel BUG at kernel/vserver/network.c:147! > > host kernel: invalid opcode: [#2] > > host kernel: PREEMPT > > host kernel: CPU:0 > > host kernel: EIP is at unhash_nx_info+0x6e/0x90 > > host kernel: eax: 0100 ebx: f6c7eee0 ecx: 0001 edx: e8326000 > > host kernel: esi: e824ba90 edi: 0010 ebp: c17efa90 esp: e8327f64 > > host kernel: ds: 007b es: 007b ss: 0068 > > host kernel: Process chbind (pid: 4168[#0], ti=e8326000 task=e824ba90 > > task.ti=e8326000) > > host kernel: Stack: f6c7eee0 0004 e8327f9c c012296e f6c7eee0 ff00 > > e8f1da40 > > host kernel: e8327f9c e824bb48 e824bb80 ff00 e8f1da40 e824bb48 > > e8327f9c e8327f9c > > host kernel: 00ff 0401a8c0 e8326000 c0122a4d c01031e1 > > 00ff 0804c81b > > host kernel: Call Trace: > > host kernel: Code: 04 c7 03 00 01 10 00 c7 43 04 00 02 20 00 b8 01 00 00 > > 00 e8 e5 ed fd ff 89 e0 25 00 e0 ff ff 8b 40 08 a8 08 75 0f 83 c4 08 5b c3 > > <0f> 0b 93 00 1f 5a 43 c0 eb b8 83 c4 08 5b e9 5f 54 2c 00 eb 0d > > host kernel: EIP: [] unhash_nx_info+0x6e/0x90 SS:ESP > > 0068:e8327f64 > > > > I'm back to 2.6.18.2 now. > > thanks, should be fixed in the next release vs2.0.2.2-rc8 is out ... > best, > Herbert > > > Andreas > > > > > > ** > > This email and any files transmitted with it are confidential and > > intended solely for the use of the individual or entity to whom they > > are addressed. If you have received this email in error please notify > > the system manager. > > ** > > > > ___ > > 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 ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] kernel bug
On Wed, Nov 22, 2006 at 01:28:42PM +0100, Andreas Baetz wrote: > Because of the CPU scheduling problems I have with 2.6.18.2 and vserver > vs2.0.2.2-rc6 I tried > 2.6.18.3 and vs2.0.2.2-rc7. > The patch applied cleanly to a vanilla kernel. > The kernel compiled ok. > After booting I tried "vserver deb4 start", that failed and I got > > kernel BUG at kernel/vserver/network.c:147! > host kernel: invalid opcode: [#2] > host kernel: PREEMPT > host kernel: CPU:0 > host kernel: EIP is at unhash_nx_info+0x6e/0x90 > host kernel: eax: 0100 ebx: f6c7eee0 ecx: 0001 edx: e8326000 > host kernel: esi: e824ba90 edi: 0010 ebp: c17efa90 esp: e8327f64 > host kernel: ds: 007b es: 007b ss: 0068 > host kernel: Process chbind (pid: 4168[#0], ti=e8326000 task=e824ba90 > task.ti=e8326000) > host kernel: Stack: f6c7eee0 0004 e8327f9c c012296e f6c7eee0 ff00 > e8f1da40 > host kernel: e8327f9c e824bb48 e824bb80 ff00 e8f1da40 e824bb48 e8327f9c > e8327f9c > host kernel: 00ff 0401a8c0 e8326000 c0122a4d c01031e1 00ff > 0804c81b > host kernel: Call Trace: > host kernel: Code: 04 c7 03 00 01 10 00 c7 43 04 00 02 20 00 b8 01 00 00 00 > e8 e5 ed fd ff 89 e0 25 00 e0 ff ff 8b 40 08 a8 08 75 0f 83 c4 08 5b c3 <0f> > 0b 93 00 1f 5a 43 c0 eb b8 83 c4 08 5b e9 5f 54 2c 00 eb 0d > host kernel: EIP: [] unhash_nx_info+0x6e/0x90 SS:ESP 0068:e8327f64 > > I'm back to 2.6.18.2 now. thanks, should be fixed in the next release best, Herbert > Andreas > > > ** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > ** > > ___ > 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
[Vserver] kernel bug
Because of the CPU scheduling problems I have with 2.6.18.2 and vserver vs2.0.2.2-rc6 I tried 2.6.18.3 and vs2.0.2.2-rc7. The patch applied cleanly to a vanilla kernel. The kernel compiled ok. After booting I tried "vserver deb4 start", that failed and I got kernel BUG at kernel/vserver/network.c:147! host kernel: invalid opcode: [#2] host kernel: PREEMPT host kernel: CPU:0 host kernel: EIP is at unhash_nx_info+0x6e/0x90 host kernel: eax: 0100 ebx: f6c7eee0 ecx: 0001 edx: e8326000 host kernel: esi: e824ba90 edi: 0010 ebp: c17efa90 esp: e8327f64 host kernel: ds: 007b es: 007b ss: 0068 host kernel: Process chbind (pid: 4168[#0], ti=e8326000 task=e824ba90 task.ti=e8326000) host kernel: Stack: f6c7eee0 0004 e8327f9c c012296e f6c7eee0 ff00 e8f1da40 host kernel: e8327f9c e824bb48 e824bb80 ff00 e8f1da40 e824bb48 e8327f9c e8327f9c host kernel: 00ff 0401a8c0 e8326000 c0122a4d c01031e1 00ff 0804c81b host kernel: Call Trace: host kernel: Code: 04 c7 03 00 01 10 00 c7 43 04 00 02 20 00 b8 01 00 00 00 e8 e5 ed fd ff 89 e0 25 00 e0 ff ff 8b 40 08 a8 08 75 0f 83 c4 08 5b c3 <0f> 0b 93 00 1f 5a 43 c0 eb b8 83 c4 08 5b e9 5f 54 2c 00 eb 0d host kernel: EIP: [] unhash_nx_info+0x6e/0x90 SS:ESP 0068:e8327f64 I'm back to 2.6.18.2 now. Andreas ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. ** ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Kernel BUG at kernel/exit.c:676
On Mon, May 01, 2006 at 01:03:47AM +0200, Jan Rekorajski wrote:
> Hi,
> I have serious problem with vserver 2.1.1-rc on SMP systems.
> I don't have UP system to check if it's an SMP-only.
> Kernel is 2.6.16.11, vserver patch 2.1.1-rc17,
>
> I can't run gdb. The following test case will give results as shown
> below:
yep, I can confirm this, it's basically a bad assumption
the following patch makes it a warning until we fix
it in rc19 (by checking for the reaper result)
(only affects init-less guests with debug enabled)
http://vserver.13thfloor.at/Experimental/BAGGINS/delta-reaper-fix01.diff
best,
Herbert
> gdb /bin/ls
> r
>
> and then you will see this:
>
> From the x86-64 machine (4xDC Opteron):
>
> Kernel BUG at kernel/exit.c:676
> invalid opcode: [1] SMP
> CPU 4
> Modules linked in: vroot nfsd lockd nfs_acl sunrpc ipv6 tg3 ext3 jbd
> mbcache dm_mod 8021q
> Pid: 21617[#100], comm: gdb Not tainted 2.6.16.11 #1
> RIP: 0010:[] {forget_original_parent+437}
> RSP: 0018:8105fa8c5eb8 EFLAGS: 00010002
> RAX: RBX: 8105cf1a50e8 RCX: 0078
> RDX: RSI: 8105fa8c5ef8 RDI: 8105cf1a5770
> RBP: 81020708d040 R08: R09: 8105fa8c5ea8
> R10: 0001 R11: 0246 R12: 8105cf1a5040
> R13: 8105cf1a50e8 R14: 0001 R15: 8105cf1a5160
> FS: 2b03caddebe0() GS:81040709dcc0() knlGS:f7d656c0
> CS: 0010 DS: 002b ES: 002b CR0: 8005003b
> CR2: 0829b574 CR3: 00101000 CR4: 06e0
> Process gdb (pid: 21617[#100], threadinfo 8105fa8c4000, task
> 8105cf1a5040)
> Stack: 8105fa8c5ef8 8101ffad2b80 8105cf1a5040 8105fa8c5ef8
> 0001 80132e06
>8105fa8c5ef8 8105fa8c5ef8
> Call Trace: {exit_notify+246}
> {do_exit+1023}
>{do_group_exit+220}
> {cstar_do_call+27}
>
> Code: 0f 0b 68 91 58 36 80 c2 a4 02 90 48 39 ef 74 0a 48 83 bd e0
> RIP {forget_original_parent+437} RSP
> <1>Fixing recursive fault but reboot is needed!
>
> From the 2xPentiumMMX:
>
> kernel BUG at kernel/exit.c:676!
> invalid opcode: [#1]
> SMP
> CPU:0
> EIP is at forget_original_parent+0x121/0x200
> eax: ebx: ca8a8b20 ecx: edx: ca8a8ab0
> esi: ca8a8098 edi: c12b9ab0 ebp: ca8a8098 esp: c5465f48
> ds: 007b es: 007b ss: 0068
> Process gdb (pid: 6053[#100], threadinfo=c5464000 task=ca8a8030)
> Stack: <0>ca8a80dc c5465f6c ca8a8030 ca8a8030 c5465f6c c0121c62
> ca8a8030
> c5465f6c c5465f6c c5465f6c ca8a8030 c9d1c4c0 c9d1c4c0 c012215e
> ca8a8030 ca8a8030 0001 cbb8fe60 c5464000 c5464000 c012237d
> Call Trace:
> [] exit_notify+0x32/0x2e0
> [] do_exit+0x24e/0x400
> [] do_group_exit+0x2d/0x90
> [] syscall_call+0x7/0xb
> Code: 00 89 eb 6a 01 8b 44 24 20 50 52 e8
> 5a fd ff ff 8b 6d 00 83 c4 0c 39 f3 75 c3 59 5b 5b 5e 5f 5d c3 0f 0b 27
> 02 08 3c 2f c0 eb d0 <0f> 0b a4 02 08 3c 2f c0 eb b9 83 be 84 00 00 00
> 10 75 83 83 be
>
> Jan
> --
> Jan R?korajski| ALL SUSPECTS ARE GUILTY. PERIOD!
> bagginsmimuw.edu.pl | OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY?
> BOFH, MANIAC | -- TROOPS by Kevin Rubio
> ___
> 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
[Vserver] Kernel BUG at kernel/exit.c:676
Hi,
I have serious problem with vserver 2.1.1-rc on SMP systems.
I don't have UP system to check if it's an SMP-only.
Kernel is 2.6.16.11, vserver patch 2.1.1-rc17,
I can't run gdb. The following test case will give results as shown
below:
gdb /bin/ls
r
and then you will see this:
From the x86-64 machine (4xDC Opteron):
Kernel BUG at kernel/exit.c:676
invalid opcode: [1] SMP
CPU 4
Modules linked in: vroot nfsd lockd nfs_acl sunrpc ipv6 tg3 ext3 jbd
mbcache dm_mod 8021q
Pid: 21617[#100], comm: gdb Not tainted 2.6.16.11 #1
RIP: 0010:[] {forget_original_parent+437}
RSP: 0018:8105fa8c5eb8 EFLAGS: 00010002
RAX: RBX: 8105cf1a50e8 RCX: 0078
RDX: RSI: 8105fa8c5ef8 RDI: 8105cf1a5770
RBP: 81020708d040 R08: R09: 8105fa8c5ea8
R10: 0001 R11: 0246 R12: 8105cf1a5040
R13: 8105cf1a50e8 R14: 0001 R15: 8105cf1a5160
FS: 2b03caddebe0() GS:81040709dcc0() knlGS:f7d656c0
CS: 0010 DS: 002b ES: 002b CR0: 8005003b
CR2: 0829b574 CR3: 00101000 CR4: 06e0
Process gdb (pid: 21617[#100], threadinfo 8105fa8c4000, task
8105cf1a5040)
Stack: 8105fa8c5ef8 8101ffad2b80 8105cf1a5040 8105fa8c5ef8
0001 80132e06
8105fa8c5ef8 8105fa8c5ef8
Call Trace: {exit_notify+246} {do_exit+1023}
{do_group_exit+220}
{cstar_do_call+27}
Code: 0f 0b 68 91 58 36 80 c2 a4 02 90 48 39 ef 74 0a 48 83 bd e0
RIP {forget_original_parent+437} RSP
<1>Fixing recursive fault but reboot is needed!
From the 2xPentiumMMX:
kernel BUG at kernel/exit.c:676!
invalid opcode: [#1]
SMP
CPU:0
EIP is at forget_original_parent+0x121/0x200
eax: ebx: ca8a8b20 ecx: edx: ca8a8ab0
esi: ca8a8098 edi: c12b9ab0 ebp: ca8a8098 esp: c5465f48
ds: 007b es: 007b ss: 0068
Process gdb (pid: 6053[#100], threadinfo=c5464000 task=ca8a8030)
Stack: <0>ca8a80dc c5465f6c ca8a8030 ca8a8030 c5465f6c c0121c62
ca8a8030
c5465f6c c5465f6c c5465f6c ca8a8030 c9d1c4c0 c9d1c4c0 c012215e
ca8a8030 ca8a8030 0001 cbb8fe60 c5464000 c5464000 c012237d
Call Trace:
[] exit_notify+0x32/0x2e0
[] do_exit+0x24e/0x400
[] do_group_exit+0x2d/0x90
[] syscall_call+0x7/0xb
Code: 00 89 eb 6a 01 8b 44 24 20 50 52 e8
5a fd ff ff 8b 6d 00 83 c4 0c 39 f3 75 c3 59 5b 5b 5e 5f 5d c3 0f 0b 27
02 08 3c 2f c0 eb d0 <0f> 0b a4 02 08 3c 2f c0 eb b9 83 be 84 00 00 00
10 75 83 83 be
Jan
--
Jan Rękorajski| ALL SUSPECTS ARE GUILTY. PERIOD!
bagginsmimuw.edu.pl | OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY?
BOFH, MANIAC | -- TROOPS by Kevin Rubio
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Kernel BUG at "kernel/vserver/context.c":144
Hi,
I got 2 BUG() messages for the same place when trying to restart a vserver.
System: Dell 1425SC, Dual Xenon with AMD64 Kernel
Kernel: 2.6.13.4
Vserver: 2.6.13.1-vs2.1.0-rc2
Regards
Andreas
*** First Opps:
ksymoops 2.4.9 on x86_64 2.6.13+vserver. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.6.13+vserver/ (default)
-m /boot/System.map-2.6.13+vserver (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Error (regular_file): read_ksyms stat /proc/ksyms failed
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Sep 26 13:00:03 cspweb01 kernel: Kernel BUG at "kernel/vserver/context.c":144
Sep 26 13:00:03 cspweb01 kernel: invalid operand: [1] SMP
Sep 26 13:00:03 cspweb01 kernel: CPU 2
Sep 26 13:00:03 cspweb01 kernel: Pid: 10252, comm: mount Not tainted 2.6.13+vserver
Sep 26 13:00:03 cspweb01 kernel: RIP: 0010:[free_vx_info+28/152] {free_vx_info+28}
Using defaults from ksymoops -t elf64-x86-64 -a i386:x86-64
Sep 26 13:00:03 cspweb01 kernel: RSP: 0018:81006ca1bcc0 EFLAGS: 00010246
Sep 26 13:00:03 cspweb01 kernel: RAX: RBX: 8100585090f0 RCX: 8100023279e8
Sep 26 13:00:03 cspweb01 kernel: RDX: 0001 RSI: 0292 RDI: 810054ce
Sep 26 13:00:03 cspweb01 kernel: RBP: 810067b4f320 R08: 810067b4f320 R09: 810077c4b548
Sep 26 13:00:03 cspweb01 kernel: R10: 81005551ed20 R11: 80198a56 R12: 8100702f79f8
Sep 26 13:00:03 cspweb01 kernel: R13: 81007ff9fa00 R14: 8100702f7918 R15:
Sep 26 13:00:03 cspweb01 kernel: FS: 2b00c6d0() GS:8042c900() knlGS:
Sep 26 13:00:03 cspweb01 kernel: CS: 0010 DS: ES: CR0: 8005003b
Sep 26 13:00:03 cspweb01 kernel: CR2: 00516000 CR3: 35129000 CR4: 06e0
Sep 26 13:00:03 cspweb01 kernel: Stack: 8012ff1a 810067b4f300 801b1824 810067b4fa70
Sep 26 13:00:03 cspweb01 kernel:810067b4f320 801b17fe 80198b53 810067b4f320
Sep 26 13:00:03 cspweb01 kernel:8100702f79f0 810067b4f320
Sep 26 13:00:03 cspweb01 kernel: Call Trace:{free_task+48} {proc_delete_inode+38}
Sep 26 13:00:03 cspweb01 kernel:{proc_delete_inode+0} {generic_delete_inode+253}
Sep 26 13:00:03 cspweb01 kernel:{dput+439} {shrink_dcache_sb+496}
Sep 26 13:00:03 cspweb01 kernel:{do_remount_sb+75} {do_mount+671}
Sep 26 13:00:03 cspweb01 kernel:{do_no_page+1399} {buffered_rmqueue+509}
Sep 26 13:00:03 cspweb01 kernel:{__alloc_pages+259} {sys_mount+138}
Sep 26 13:00:03 cspweb01 kernel:{system_call+126}
Sep 26 13:00:03 cspweb01 kernel: Code: 0f 0b a3 a0 5e 2e 80 ff ff ff ff c2 90 00 8b 47 14 85 c0 74
>>RIP; 8014abb1<=
>>RBX; 8100585090f0
>>RCX; 8100023279e8
>>RDI; 810054ce
>>RBP; 810067b4f320
>>R08; 810067b4f320
>>R09; 810077c4b548
>>R10; 81005551ed20
>>R11; 80198a56
>>R12; 8100702f79f8
>>R13; 81007ff9fa00
>>R14; 8100702f7918
Trace; 8012ff1a
Trace; 801b17fe
Trace; 8019649d
Trace; 80184410
Trace; 8016f3a3
Trace; 801647bf <__alloc_pages+103/448>
Trace; 8010d9ea
Code; 8014abb1
<_RIP>:
Code; 8014abb1<=
0: 0f 0b ud2a <=
Code; 8014abb3
2: a3 a0 5e 2e 80 ff ff mov%eax,0x802e5ea0
Code; 8014abba
9: ff ff
Code; 8014abbc
b: c2 90 00 retq $0x90
Code; 8014abbf
e: 8b 47 14 mov0x14(%rdi),%eax
Code; 8014abc2
11: 85 c0 test %eax,%eax
Code; 8014abc4
13: 74 00 je 15 <_RIP+0x15>
1 warning and 1 error issued. Results may not be reliable.
*** Second Opps:
ksymoops 2.4.9 on x86_64 2.6.13+vserver. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.6.13+vserver/ (default)
-m /boot/System.map-2.6.13+vserver (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops
