Re: [Vserver] kernel panic patch-2.6.19.1-vs2.1.1.7.diff
Hi, perfect, this provided the essential clue please verify that the following patch fixes the issue for you: http://vserver.13thfloor.at/Experimental/delta-proc-fix04.diff Test server didn't crashed so far. I checked this patch and also new patch-2.6.19.2-vs2.2.0-rc8.7. Thanks for help. Jarek ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] kernel panic patch-2.6.19.1-vs2.1.1.7.diff
On Wed, Jan 24, 2007 at 11:58:58AM +0100, Jarek Dylag wrote: Hi okay, I think we need some more information, especially the following would be of interest: # gcc --version gcc-3.4 (GCC) 3.4.4 20050314 (prerelease) (Debian 3.4.3-13) # as --version GNU assembler 2.15 and the result of this inisde your kernel build tree: (make sure that config and tools are the same as for the oops you reported!!) # make fs/proc/array.s simply provide the resulting fs/proc/array.s results are available at: http://195.149.230.90/array.s perfect, this provided the essential clue please verify that the following patch fixes the issue for you: http://vserver.13thfloor.at/Experimental/delta-proc-fix04.diff TIA, Herbert PS: does the issue go away if you do not compile with the CONFIG_CC_OPTIMIZE_FOR_SIZE=y (which probably doesn't make any sense on you arch, as it just slows down execution) No, issue still exists. Jarek Dylag ___ 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 panic patch-2.6.19.1-vs2.1.1.7.diff
Hi okay, I think we need some more information, especially the following would be of interest: # gcc --version gcc-3.4 (GCC) 3.4.4 20050314 (prerelease) (Debian 3.4.3-13) # as --version GNU assembler 2.15 and the result of this inisde your kernel build tree: (make sure that config and tools are the same as for the oops you reported!!) # make fs/proc/array.s simply provide the resulting fs/proc/array.s results are available at: http://195.149.230.90/array.s PS: does the issue go away if you do not compile with the CONFIG_CC_OPTIMIZE_FOR_SIZE=y (which probably doesn't make any sense on you arch, as it just slows down execution) No, issue still exists. Jarek Dylag ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] kernel panic patch-2.6.19.1-vs2.1.1.7.diff
On Wed, Jan 10, 2007 at 09:14:21AM +0100, Jarek Dylag wrote: Hi There is nothing new in kernel log after changes, oops in attachement. very strange ... you constantly omit the kernel lines from the oops traces, could you verify that you actually booted the modified kernel? I sended all information i can find in server logs (from netconsole). Yes, i'm sure it is modified kernel. could you also upload the vmlinux (not vmlinuz) file somewhere where I could access it? Vmlinux file, oops and my config file are available at: http://195.149.230.90/vmlinux http://195.149.230.90/vmlinux.bz2 http://195.149.230.90/.config http://195.149.230.90/oops.txt okay, I think we need some more information, especially the following would be of interest: # gcc --version # as --version and the result of this inisde your kernel build tree: (make sure that config and tools are the same as for the oops you reported!!) # make fs/proc/array.s simply provide the resulting fs/proc/array.s TIA, Herbert PS: does the issue go away if you do not compile with the CONFIG_CC_OPTIMIZE_FOR_SIZE=y (which probably doesn't make any sense on you arch, as it just slows down execution) Jarek Dylag ___ 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 panic patch-2.6.19.1-vs2.1.1.7.diff
Hi There is nothing new in kernel log after changes, oops in attachement. very strange ... you constantly omit the kernel lines from the oops traces, could you verify that you actually booted the modified kernel? I sended all information i can find in server logs (from netconsole). Yes, i'm sure it is modified kernel. could you also upload the vmlinux (not vmlinuz) file somewhere where I could access it? Vmlinux file, oops and my config file are available at: http://195.149.230.90/vmlinux http://195.149.230.90/vmlinux.bz2 http://195.149.230.90/.config http://195.149.230.90/oops.txt Jarek Dylag ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] kernel panic patch-2.6.19.1-vs2.1.1.7.diff
Hi, okay, as it seems, I cannot recreate this here please could you make the following changes to get_task_state() There is nothing new in kernel log after changes, oops in attachement. Jarek Dylag Jan 3 13:02:33 v2140 [10966.004095] BUG: unable to handle kernel NULL pointer dereference Jan 3 13:02:33 v2140 at virtual address Jan 3 13:02:33 v2140 [10966.004192] printing eip: Jan 3 13:02:33 v2140 [10966.004227] c01b2498 Jan 3 13:02:33 v2140 [10966.004260] *pde = Jan 3 13:02:33 v2140 [10966.004300] Oops: [#1] Jan 3 13:02:33 v2140 [10966.004341] Jan 3 13:02:33 v2140 SMP Jan 3 13:02:33 v2140 DEBUG_PAGEALLOC Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.004428] Modules linked in: Jan 3 13:02:33 v2140 ipt_LOG Jan 3 13:02:33 v2140 ipt_owner Jan 3 13:02:33 v2140 xt_state Jan 3 13:02:33 v2140 xt_tcpudp Jan 3 13:02:33 v2140 iptable_filter Jan 3 13:02:33 v2140 ipt_MASQUERADE Jan 3 13:02:33 v2140 iptable_nat Jan 3 13:02:33 v2140 ip_nat Jan 3 13:02:33 v2140 ip_tables Jan 3 13:02:33 v2140 x_tables Jan 3 13:02:33 v2140 ecb Jan 3 13:02:33 v2140 af_key Jan 3 13:02:33 v2140 tun Jan 3 13:02:33 v2140 netconsole Jan 3 13:02:33 v2140 e100 Jan 3 13:02:33 v2140 r8169 Jan 3 13:02:33 v2140 crc32 Jan 3 13:02:33 v2140 ip_conntrack_ftp Jan 3 13:02:33 v2140 ip_conntrack Jan 3 13:02:33 v2140 nfnetlink Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.005037] CPU:2 Jan 3 13:02:33 v2140 [10966.005040] EIP:0060:[c01b2498]Not tainted VLI Jan 3 13:02:33 v2140 [10966.005044] EFLAGS: 00010286 (2.6.19.1-vs2.2.0-rc5.p4smp.53 #1) Jan 3 13:02:33 v2140 [10966.005201] EIP is at do_task_stat+0xa5/0x766 Jan 3 13:02:33 v2140 [10966.005253] eax: ebx: d91ef000 ecx: c06ecbb4 edx: 0040 Jan 3 13:02:33 v2140 [10966.005311] esi: dbdf45a0 edi: dbdf45a0 ebp: cc0e9f14 esp: cc0e9dc0 Jan 3 13:02:33 v2140 [10966.005368] ds: 007b es: 007b ss: 0068 Jan 3 13:02:33 v2140 [10966.005418] Process pidof (pid: 23423[#2149], ti=cc0e8000 task=da4e45a0 task.ti=cc0e8000) Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.005473] Stack: Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 c01142ed Jan 3 13:02:33 v2140 cc0e9de8 Jan 3 13:02:33 v2140 c0141f03 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 c0588874 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.005788] Jan 3 13:02:33 v2140 cc0e9e00 Jan 3 13:02:33 v2140 c0140dd6 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 c0588874 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 c06e4a44 Jan 3 13:02:33 v2140 0296 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.006090] Jan 3 13:02:33 v2140 cc0e9e1c Jan 3 13:02:33 v2140 0296 Jan 3 13:02:33 v2140 c06e4a44 Jan 3 13:02:33 v2140 0001 Jan 3 13:02:33 v2140 c01142ed Jan 3 13:02:33 v2140 c151a4c0 Jan 3 13:02:33 v2140 0001 Jan 3 13:02:33 v2140 cc0e9e3c Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.006427] Call Trace: Jan 3 13:02:33 v2140 [10966.006510] [c0103dbd] Jan 3 13:02:33 v2140 show_trace_log_lvl+0x2f/0x45 Jan 3 13:02:33 v2140 [10966.006593] [c0103e9b] Jan 3 13:02:33 v2140 show_stack_log_lvl+0x9f/0xa7 Jan 3 13:02:33 v2140 [10966.006678] [c01040b2] Jan 3 13:02:33 v2140 show_registers+0x1b1/0x242 Jan 3 13:02:33 v2140 [10966.006755] [c0104345] Jan 3 13:02:33 v2140 die+0x151/0x246 Jan 3 13:02:33 v2140 [10966.006829] [c058a68e] Jan 3 13:02:33 v2140 do_page_fault+0x498/0x58a Jan 3 13:02:33 v2140 [10966.006919] [c0588c09] Jan 3 13:02:33 v2140 error_code+0x39/0x40 Jan 3 13:02:33 v2140 [10966.006998] [c01b2b9b] Jan 3 13:02:33 v2140 proc_tgid_stat+0x20/0x22 Jan 3 13:02:33 v2140 [10966.007080] [c01ad6dd] Jan 3 13:02:33 v2140 proc_info_read+0x12f/0x17e Jan 3 13:02:33 v2140 [10966.007166] [c01761f0] Jan 3 13:02:33 v2140 vfs_read+0xa3/0x177 Jan 3 13:02:33 v2140 [10966.007244] [c017658e] Jan 3 13:02:33 v2140 sys_read+0x47/0x6b Jan 3 13:02:33 v2140 [10966.040593] [c0102feb] Jan 3 13:02:33 v2140 syscall_call+0x7/0xb Jan 3 13:02:33 v2140 [10966.040650] === Jan 3 13:02:33 v2140 [10966.040685] Code: Jan 3 13:02:33 v2140 07 Jan 3 13:02:33 v2140 8b Jan 3 13:02:33 v2140 97 Jan 3 13:02:33 v2140 8c Jan 3 13:02:33 v2140 00 Jan 3 13:02:33 v2140 00 Jan 3 13:02:33 v2140 00 Jan 3 13:02:33 v2140 b9 Jan 3 13:02:33 v2140 98 Jan 3 13:02:33 v2140 cb Jan 3 13:02:33 v2140 6e Jan 3 13:02:33 v2140 c0 Jan 3 13:02:33 v2140 83 Jan 3 13:02:33 v2140 e0 Jan 3 13:02:33 v2140 1f Jan 3 13:02:33 v2140 83 Jan 3 13:02:33 v2140 e2 Jan 3 13:02:33 v2140 60 Jan 3 13:02:33 v2140 09 Jan 3 13:02:33 v2140 d0 Jan 3 13:02:33 v2140 74 Jan 3 13:02:33 v2140 13 Jan 3 13:02:33 v2140 83 Jan 3 13:02:33 v2140 c1 Jan 3 13:02:33 v2140 04 Jan 3 13:02:33 v2140 d1 Jan 3 13:02:33 v2140 e8 Jan
Re: [Vserver] kernel panic patch-2.6.19.1-vs2.1.1.7.diff
On Mon, Jan 08, 2007 at 11:29:46AM +0100, Jarek Dylag wrote: Hi, okay, as it seems, I cannot recreate this here please could you make the following changes to get_task_state() There is nothing new in kernel log after changes, oops in attachement. very strange ... you constantly omit the kernel lines from the oops traces, could you verify that you actually booted the modified kernel? could you also upload the vmlinux (not vmlinuz) file somewhere where I could access it? TIA, Herbert Jarek Dylag Jan 3 13:02:33 v2140 [10966.004095] BUG: unable to handle kernel NULL pointer dereference Jan 3 13:02:33 v2140 at virtual address Jan 3 13:02:33 v2140 [10966.004192] printing eip: Jan 3 13:02:33 v2140 [10966.004227] c01b2498 Jan 3 13:02:33 v2140 [10966.004260] *pde = Jan 3 13:02:33 v2140 [10966.004300] Oops: [#1] Jan 3 13:02:33 v2140 [10966.004341] Jan 3 13:02:33 v2140 SMP Jan 3 13:02:33 v2140 DEBUG_PAGEALLOC Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.004428] Modules linked in: Jan 3 13:02:33 v2140 ipt_LOG Jan 3 13:02:33 v2140 ipt_owner Jan 3 13:02:33 v2140 xt_state Jan 3 13:02:33 v2140 xt_tcpudp Jan 3 13:02:33 v2140 iptable_filter Jan 3 13:02:33 v2140 ipt_MASQUERADE Jan 3 13:02:33 v2140 iptable_nat Jan 3 13:02:33 v2140 ip_nat Jan 3 13:02:33 v2140 ip_tables Jan 3 13:02:33 v2140 x_tables Jan 3 13:02:33 v2140 ecb Jan 3 13:02:33 v2140 af_key Jan 3 13:02:33 v2140 tun Jan 3 13:02:33 v2140 netconsole Jan 3 13:02:33 v2140 e100 Jan 3 13:02:33 v2140 r8169 Jan 3 13:02:33 v2140 crc32 Jan 3 13:02:33 v2140 ip_conntrack_ftp Jan 3 13:02:33 v2140 ip_conntrack Jan 3 13:02:33 v2140 nfnetlink Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.005037] CPU:2 Jan 3 13:02:33 v2140 [10966.005040] EIP:0060:[c01b2498]Not tainted VLI Jan 3 13:02:33 v2140 [10966.005044] EFLAGS: 00010286 (2.6.19.1-vs2.2.0-rc5.p4smp.53 #1) Jan 3 13:02:33 v2140 [10966.005201] EIP is at do_task_stat+0xa5/0x766 Jan 3 13:02:33 v2140 [10966.005253] eax: ebx: d91ef000 ecx: c06ecbb4 edx: 0040 Jan 3 13:02:33 v2140 [10966.005311] esi: dbdf45a0 edi: dbdf45a0 ebp: cc0e9f14 esp: cc0e9dc0 Jan 3 13:02:33 v2140 [10966.005368] ds: 007b es: 007b ss: 0068 Jan 3 13:02:33 v2140 [10966.005418] Process pidof (pid: 23423[#2149], ti=cc0e8000 task=da4e45a0 task.ti=cc0e8000) Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.005473] Stack: Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 c01142ed Jan 3 13:02:33 v2140 cc0e9de8 Jan 3 13:02:33 v2140 c0141f03 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 c0588874 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.005788] Jan 3 13:02:33 v2140 cc0e9e00 Jan 3 13:02:33 v2140 c0140dd6 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 c0588874 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 c06e4a44 Jan 3 13:02:33 v2140 0296 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.006090] Jan 3 13:02:33 v2140 cc0e9e1c Jan 3 13:02:33 v2140 0296 Jan 3 13:02:33 v2140 c06e4a44 Jan 3 13:02:33 v2140 0001 Jan 3 13:02:33 v2140 c01142ed Jan 3 13:02:33 v2140 c151a4c0 Jan 3 13:02:33 v2140 0001 Jan 3 13:02:33 v2140 cc0e9e3c Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.006427] Call Trace: Jan 3 13:02:33 v2140 [10966.006510] [c0103dbd] Jan 3 13:02:33 v2140 show_trace_log_lvl+0x2f/0x45 Jan 3 13:02:33 v2140 [10966.006593] [c0103e9b] Jan 3 13:02:33 v2140 show_stack_log_lvl+0x9f/0xa7 Jan 3 13:02:33 v2140 [10966.006678] [c01040b2] Jan 3 13:02:33 v2140 show_registers+0x1b1/0x242 Jan 3 13:02:33 v2140 [10966.006755] [c0104345] Jan 3 13:02:33 v2140 die+0x151/0x246 Jan 3 13:02:33 v2140 [10966.006829] [c058a68e] Jan 3 13:02:33 v2140 do_page_fault+0x498/0x58a Jan 3 13:02:33 v2140 [10966.006919] [c0588c09] Jan 3 13:02:33 v2140 error_code+0x39/0x40 Jan 3 13:02:33 v2140 [10966.006998] [c01b2b9b] Jan 3 13:02:33 v2140 proc_tgid_stat+0x20/0x22 Jan 3 13:02:33 v2140 [10966.007080] [c01ad6dd] Jan 3 13:02:33 v2140 proc_info_read+0x12f/0x17e Jan 3 13:02:33 v2140 [10966.007166] [c01761f0] Jan 3 13:02:33 v2140 vfs_read+0xa3/0x177 Jan 3 13:02:33 v2140 [10966.007244] [c017658e] Jan 3 13:02:33 v2140 sys_read+0x47/0x6b Jan 3 13:02:33 v2140 [10966.040593] [c0102feb] Jan 3 13:02:33 v2140 syscall_call+0x7/0xb Jan 3 13:02:33 v2140 [10966.040650] === Jan 3 13:02:33 v2140 [10966.040685] Code: Jan 3 13:02:33 v2140 07 Jan 3 13:02:33 v2140 8b Jan 3 13:02:33 v2140 97 Jan 3 13:02:33 v2140 8c Jan 3 13:02:33 v2140 00 Jan 3 13:02:33 v2140 00 Jan 3 13:02:33 v2140 00 Jan 3 13:02:33 v2140 b9 Jan 3 13:02:33 v2140 98 Jan 3 13:02:33 v2140 cb Jan 3 13:02:33 v2140 6e
Re: [Vserver] kernel panic patch-2.6.19.1-vs2.1.1.7.diff
On Fri, Dec 29, 2006 at 07:25:02AM +0100, Jarek Dylag wrote:
On 22/12/06, Herbert Poetzl [EMAIL PROTECTED] wrote:
On Thu, Dec 21, 2006 at 03:45:45PM +0100, Jarek Dylag wrote:
Hi,
I've tested:
patch-2.6.19.1-vs2.1.1.7.diff
patch-2.6.19.1-vs2.2.0-rc5.diff
hmm, are you sure? it looks like a bug we
fixed in vs2.2.0-rc5, so please try to
confirm that version, and if so, please
yes, confirmed also with vs2.2.0-rc6
enable kernel debug info and frame pointers
so that we can get a meaningful backtrace
i turned on all kernel debug options, results in attachments.
okay, as it seems, I cannot recreate this here
please could you make the following changes to
get_task_state()
static inline const char * get_task_state(struct task_struct *tsk)
{
unsigned int state;
BUG_ON(!tsk);
state = (tsk-state (TASK_RUNNING |
TASK_INTERRUPTIBLE |
TASK_UNINTERRUPTIBLE |
TASK_STOPPED |
TASK_TRACED |
TASK_ONHOLD)) |
(tsk-exit_state (EXIT_ZOMBIE |
EXIT_DEAD));
const char **p = task_state_array[0];
while (state) {
p++;
state = 1;
}
BUG_ON(!p);
return *p;
}
TIA,
Herbert
Jarek Dylag
Dec 29 03:16:52 v2140 [ 7366.213758] BUG: unable to handle kernel NULL
pointer dereference
Dec 29 03:16:52 v2140 at virtual address
Dec 29 03:16:52 v2140 [ 7366.213881] printing eip:
Dec 29 03:16:52 v2140 [ 7366.213929] c01b2466
Dec 29 03:16:52 v2140 [ 7366.213989] *pde =
Dec 29 03:16:52 v2140 [ 7366.214045] Oops: [#1]
Dec 29 03:16:52 v2140 [ 7366.214089]
Dec 29 03:16:52 v2140 SMP
Dec 29 03:16:52 v2140 DEBUG_PAGEALLOC
Dec 29 03:16:52 v2140
Dec 29 03:16:52 v2140 [ 7366.214221] Modules linked in:
Dec 29 03:16:52 v2140 ipt_LOG
Dec 29 03:16:52 v2140 ipt_owner
Dec 29 03:16:52 v2140 xt_state
Dec 29 03:16:52 v2140 xt_tcpudp
Dec 29 03:16:52 v2140 iptable_filter
Dec 29 03:16:52 v2140 ipt_MASQUERADE
Dec 29 03:16:52 v2140 iptable_nat
Dec 29 03:16:52 v2140 ip_nat
Dec 29 03:16:52 v2140 ip_tables
Dec 29 03:16:52 v2140 x_tables
Dec 29 03:16:52 v2140 ecb
Dec 29 03:16:52 v2140 af_key
Dec 29 03:16:52 v2140 tun
Dec 29 03:16:52 v2140 netconsole
Dec 29 03:16:52 v2140 e100
Dec 29 03:16:52 v2140 r8169
Dec 29 03:16:52 v2140 crc32
Dec 29 03:16:52 v2140 ip_conntrack_ftp
Dec 29 03:16:52 v2140 ip_conntrack
Dec 29 03:16:52 v2140 nfnetlink
Dec 29 03:16:52 v2140
Dec 29 03:16:52 v2140 [ 7366.214679] CPU:2
Dec 29 03:16:52 v2140 [ 7366.214681] EIP:0060:[c01b2466]Not tainted
VLI
Dec 29 03:16:52 v2140 [ 7366.214683] EFLAGS: 00010247
(2.6.19.1-vs2.2.0-rc5.p4smp.52 #1)
Dec 29 03:16:52 v2140 [ 7366.214799] EIP is at do_task_stat+0x8d/0x74e
Dec 29 03:16:52 v2140 [ 7366.214839] eax: ebx: cae2f000 ecx:
c06ecbb4 edx: 0040
Dec 29 03:16:52 v2140 [ 7366.214880] esi: c9b5c5a0 edi: c9b5c5a0 ebp:
d8221f14 esp: d8221dc0
Dec 29 03:16:52 v2140 [ 7366.214923] ds: 007b es: 007b ss: 0068
Dec 29 03:16:52 v2140 [ 7366.214961] Process pidof (pid: 8231[#2030],
ti=d822 task=c5ea65a0 task.ti=d822)
Dec 29 03:16:52 v2140
Dec 29 03:16:52 v2140 [ 7366.215004] Stack:
Dec 29 03:16:52 v2140 c5ea65a0
Dec 29 03:16:52 v2140 c01142ed
Dec 29 03:16:52 v2140 d8221de8
Dec 29 03:16:52 v2140 c0141f03
Dec 29 03:16:52 v2140 c5ea65a0
Dec 29 03:16:52 v2140 c5ea65a0
Dec 29 03:16:52 v2140 c0588844
Dec 29 03:16:52 v2140
Dec 29 03:16:52 v2140
Dec 29 03:16:52 v2140 [ 7366.215228]
Dec 29 03:16:52 v2140 d8221e00
Dec 29 03:16:52 v2140 c0140dd6
Dec 29 03:16:52 v2140 c5ea65a0
Dec 29 03:16:52 v2140
Dec 29 03:16:52 v2140 c0588844
Dec 29 03:16:52 v2140 c5ea65a0
Dec 29 03:16:52 v2140 c06e4a44
Dec 29 03:16:52 v2140 0296
Dec 29 03:16:52 v2140
Dec 29 03:16:52 v2140 [ 7366.215409]
Dec 29 03:16:52 v2140 d8221e1c
Dec 29 03:16:52 v2140 0296
Dec 29 03:16:52 v2140 c06e4a44
Dec 29 03:16:52 v2140 0001
Dec 29 03:16:52 v2140 c01142ed
Dec 29 03:16:52 v2140 c12361c0
Dec 29 03:16:52 v2140 0001
Dec 29 03:16:52 v2140 d8221e3c
Dec 29 03:16:52 v2140
Dec 29 03:16:52 v2140 [ 7366.215579] Call Trace:
Dec 29 03:16:52 v2140 [ 7366.215641] [c0103dbd]
Dec 29 03:16:52 v2140 show_trace_log_lvl+0x2f/0x45
Dec 29 03:16:52 v2140 [ 7366.215704] [c0103e9b]
Dec 29 03:16:52 v2140 show_stack_log_lvl+0x9f/0xa7
Dec 29 03:16:52 v2140 [ 7366.215778] [c01040b2]
Dec 29 03:16:52 v2140 show_registers+0x1b1/0x242
Dec 29 03:16:52 v2140 [ 7366.215834] [c0104345]
Dec 29 03:16:52 v2140 die+0x151/0x246
Dec 29 03:16:52 v2140 [ 7366.234644] [c058a65e]
Dec 29 03:16:52 v2140 do_page_fault+0x498/0x58a
Dec 29 03:16:52 v2140 [ 7366.234711] [c0588bd9]
Dec 29 03:16:52 v2140 error_code+0x39/0x40
Dec 29 03:16:52 v2140 [ 7366.234767] [c01b2b69]
Dec 29 03:16:52 v2140
Re: [Vserver] kernel panic patch-2.6.19.1-vs2.1.1.7.diff
On 22/12/06, Herbert Poetzl [EMAIL PROTECTED] wrote: On Thu, Dec 21, 2006 at 03:45:45PM +0100, Jarek Dylag wrote: Hi, I've tested: patch-2.6.19.1-vs2.1.1.7.diff patch-2.6.19.1-vs2.2.0-rc5.diff hmm, are you sure? it looks like a bug we fixed in vs2.2.0-rc5, so please try to confirm that version, and if so, please yes, confirmed also with vs2.2.0-rc6 enable kernel debug info and frame pointers so that we can get a meaningful backtrace i turned on all kernel debug options, results in attachments. Jarek Dylag Dec 29 03:16:52 v2140 [ 7366.213758] BUG: unable to handle kernel NULL pointer dereference Dec 29 03:16:52 v2140 at virtual address Dec 29 03:16:52 v2140 [ 7366.213881] printing eip: Dec 29 03:16:52 v2140 [ 7366.213929] c01b2466 Dec 29 03:16:52 v2140 [ 7366.213989] *pde = Dec 29 03:16:52 v2140 [ 7366.214045] Oops: [#1] Dec 29 03:16:52 v2140 [ 7366.214089] Dec 29 03:16:52 v2140 SMP Dec 29 03:16:52 v2140 DEBUG_PAGEALLOC Dec 29 03:16:52 v2140 Dec 29 03:16:52 v2140 [ 7366.214221] Modules linked in: Dec 29 03:16:52 v2140 ipt_LOG Dec 29 03:16:52 v2140 ipt_owner Dec 29 03:16:52 v2140 xt_state Dec 29 03:16:52 v2140 xt_tcpudp Dec 29 03:16:52 v2140 iptable_filter Dec 29 03:16:52 v2140 ipt_MASQUERADE Dec 29 03:16:52 v2140 iptable_nat Dec 29 03:16:52 v2140 ip_nat Dec 29 03:16:52 v2140 ip_tables Dec 29 03:16:52 v2140 x_tables Dec 29 03:16:52 v2140 ecb Dec 29 03:16:52 v2140 af_key Dec 29 03:16:52 v2140 tun Dec 29 03:16:52 v2140 netconsole Dec 29 03:16:52 v2140 e100 Dec 29 03:16:52 v2140 r8169 Dec 29 03:16:52 v2140 crc32 Dec 29 03:16:52 v2140 ip_conntrack_ftp Dec 29 03:16:52 v2140 ip_conntrack Dec 29 03:16:52 v2140 nfnetlink Dec 29 03:16:52 v2140 Dec 29 03:16:52 v2140 [ 7366.214679] CPU:2 Dec 29 03:16:52 v2140 [ 7366.214681] EIP:0060:[c01b2466]Not tainted VLI Dec 29 03:16:52 v2140 [ 7366.214683] EFLAGS: 00010247 (2.6.19.1-vs2.2.0-rc5.p4smp.52 #1) Dec 29 03:16:52 v2140 [ 7366.214799] EIP is at do_task_stat+0x8d/0x74e Dec 29 03:16:52 v2140 [ 7366.214839] eax: ebx: cae2f000 ecx: c06ecbb4 edx: 0040 Dec 29 03:16:52 v2140 [ 7366.214880] esi: c9b5c5a0 edi: c9b5c5a0 ebp: d8221f14 esp: d8221dc0 Dec 29 03:16:52 v2140 [ 7366.214923] ds: 007b es: 007b ss: 0068 Dec 29 03:16:52 v2140 [ 7366.214961] Process pidof (pid: 8231[#2030], ti=d822 task=c5ea65a0 task.ti=d822) Dec 29 03:16:52 v2140 Dec 29 03:16:52 v2140 [ 7366.215004] Stack: Dec 29 03:16:52 v2140 c5ea65a0 Dec 29 03:16:52 v2140 c01142ed Dec 29 03:16:52 v2140 d8221de8 Dec 29 03:16:52 v2140 c0141f03 Dec 29 03:16:52 v2140 c5ea65a0 Dec 29 03:16:52 v2140 c5ea65a0 Dec 29 03:16:52 v2140 c0588844 Dec 29 03:16:52 v2140 Dec 29 03:16:52 v2140 Dec 29 03:16:52 v2140 [ 7366.215228] Dec 29 03:16:52 v2140 d8221e00 Dec 29 03:16:52 v2140 c0140dd6 Dec 29 03:16:52 v2140 c5ea65a0 Dec 29 03:16:52 v2140 Dec 29 03:16:52 v2140 c0588844 Dec 29 03:16:52 v2140 c5ea65a0 Dec 29 03:16:52 v2140 c06e4a44 Dec 29 03:16:52 v2140 0296 Dec 29 03:16:52 v2140 Dec 29 03:16:52 v2140 [ 7366.215409] Dec 29 03:16:52 v2140 d8221e1c Dec 29 03:16:52 v2140 0296 Dec 29 03:16:52 v2140 c06e4a44 Dec 29 03:16:52 v2140 0001 Dec 29 03:16:52 v2140 c01142ed Dec 29 03:16:52 v2140 c12361c0 Dec 29 03:16:52 v2140 0001 Dec 29 03:16:52 v2140 d8221e3c Dec 29 03:16:52 v2140 Dec 29 03:16:52 v2140 [ 7366.215579] Call Trace: Dec 29 03:16:52 v2140 [ 7366.215641] [c0103dbd] Dec 29 03:16:52 v2140 show_trace_log_lvl+0x2f/0x45 Dec 29 03:16:52 v2140 [ 7366.215704] [c0103e9b] Dec 29 03:16:52 v2140 show_stack_log_lvl+0x9f/0xa7 Dec 29 03:16:52 v2140 [ 7366.215778] [c01040b2] Dec 29 03:16:52 v2140 show_registers+0x1b1/0x242 Dec 29 03:16:52 v2140 [ 7366.215834] [c0104345] Dec 29 03:16:52 v2140 die+0x151/0x246 Dec 29 03:16:52 v2140 [ 7366.234644] [c058a65e] Dec 29 03:16:52 v2140 do_page_fault+0x498/0x58a Dec 29 03:16:52 v2140 [ 7366.234711] [c0588bd9] Dec 29 03:16:52 v2140 error_code+0x39/0x40 Dec 29 03:16:52 v2140 [ 7366.234767] [c01b2b69] Dec 29 03:16:52 v2140 proc_tgid_stat+0x20/0x22 Dec 29 03:16:52 v2140 [ 7366.234826] [c01ad6dd] Dec 29 03:16:52 v2140 proc_info_read+0x12f/0x17e Dec 29 03:16:52 v2140 [ 7366.234888] [c01761f0] Dec 29 03:16:52 v2140 vfs_read+0xa3/0x177 Dec 29 03:16:52 v2140 [ 7366.234948] [c017658e] Dec 29 03:16:52 v2140 sys_read+0x47/0x6b Dec 29 03:16:52 v2140 [ 7366.235004] [c0102feb] Dec 29 03:16:52 v2140 syscall_call+0x7/0xb Dec 29 03:16:52 v2140 [ 7366.235062] === Dec 29 03:16:52 v2140 [ 7366.235099] Code: Dec 29 03:16:52 v2140 45 Dec 29 03:16:52 v2140 84 Dec 29 03:16:52 v2140 00 Dec 29 03:16:52 v2140 00 Dec 29 03:16:52 v2140 00 Dec 29 03:16:52 v2140 00 Dec 29 03:16:52 v2140 c7 Dec 29 03:16:52 v2140 85 Dec 29 03:16:52 v2140 70 Dec 29 03:16:52 v2140 ff Dec 29 03:16:52 v2140 ff Dec 29 03:16:52 v2140 ff Dec 29 03:16:52 v2140 00 Dec 29 03:16:52 v2140 00 Dec 29 03:16:52
Re: [Vserver] kernel panic patch-2.6.19.1-vs2.1.1.7.diff
On Thu, Dec 21, 2006 at 03:45:45PM +0100, Jarek Dylag wrote: Hi, I've tested: patch-2.6.19.1-vs2.1.1.7.diff patch-2.6.19.1-vs2.2.0-rc5.diff hmm, are you sure? it looks like a bug we fixed in vs2.2.0-rc5, so please try to confirm that version, and if so, please enable kernel debug info and frame pointers so that we can get a meaningful backtrace TIA, Herbert With this kernels test servers crashed after 30 min - 2h. Opps from netconsole in attachment. Jarek Dylag Dec 21 11:55:48 v2140 [ 7949.406530] BUG: unable to handle kernel NULL pointer dereference Dec 21 11:55:48 v2140 at virtual address Dec 21 11:55:48 v2140 [ 7949.406644] printing eip: Dec 21 11:55:48 v2140 [ 7949.406674] c01ad192 Dec 21 11:55:48 v2140 [ 7949.406708] *pde = Dec 21 11:55:48 v2140 [ 7949.406751] Oops: [#1] Dec 21 11:55:48 v2140 [ 7949.406777] Dec 21 11:55:48 v2140 SMP Dec 21 11:55:48 v2140 Dec 21 11:55:48 v2140 [ 7949.406818] Modules linked in: Dec 21 11:55:48 v2140 ipt_LOG Dec 21 11:55:48 v2140 ipt_owner Dec 21 11:55:48 v2140 xt_state Dec 21 11:55:48 v2140 xt_tcpudp Dec 21 11:55:48 v2140 iptable_filter Dec 21 11:55:48 v2140 ipt_MASQUERADE Dec 21 11:55:48 v2140 iptable_nat Dec 21 11:55:48 v2140 ip_nat Dec 21 11:55:48 v2140 ip_tables Dec 21 11:55:48 v2140 x_tables Dec 21 11:55:48 v2140 ecb Dec 21 11:55:48 v2140 af_key Dec 21 11:55:48 v2140 tun Dec 21 11:55:48 v2140 netconsole Dec 21 11:55:48 v2140 e100 Dec 21 11:55:48 v2140 r8169 Dec 21 11:55:48 v2140 crc32 Dec 21 11:55:48 v2140 ip_conntrack_ftp Dec 21 11:55:48 v2140 ip_conntrack Dec 21 11:55:48 v2140 nfnetlink Dec 21 11:55:48 v2140 Dec 21 11:55:48 v2140 [ 7949.407089] CPU:0 Dec 21 11:55:48 v2140 [ 7949.407091] EIP:0060:[c01ad192]Not tainted VLI Dec 21 11:55:48 v2140 [ 7949.407094] EFLAGS: 00010247 (2.6.19.1.p4smp.49 #1) Dec 21 11:55:48 v2140 [ 7949.407182] EIP is at do_task_stat+0x8d/0x742 Dec 21 11:55:48 v2140 [ 7949.407217] eax: ebx: d6f19000 ecx: c062fc74 edx: 0040 Dec 21 11:55:48 v2140 [ 7949.407254] esi: deeb7aa0 edi: deeb7aa0 ebp: c4a57f14 esp: c4a57dc0 Dec 21 11:55:48 v2140 [ 7949.407296] ds: 007b es: 007b ss: 0068 Dec 21 11:55:48 v2140 [ 7949.407325] Process pidof (pid: 13338[#2149], ti=c4a56000 task=cf08b550 task.ti=c4a56000) Dec 21 11:55:48 v2140 Dec 21 11:55:48 v2140 [ 7949.407356] Stack: Dec 21 11:55:48 v2140 c0187635 Dec 21 11:55:48 v2140 d1371d68 Dec 21 11:55:48 v2140 c06e9880 Dec 21 11:55:48 v2140 c4a57f14 Dec 21 11:55:48 v2140 Dec 21 11:55:48 v2140 c4a57e44 Dec 21 11:55:48 v2140 c017902b Dec 21 11:55:48 v2140 d1371d40 Dec 21 11:55:48 v2140 Dec 21 11:55:48 v2140 [ 7949.407447] Dec 21 11:55:48 v2140 c4a57f14 Dec 21 11:55:48 v2140 0050 Dec 21 11:55:48 v2140 d1adc604 Dec 21 11:55:48 v2140 d1371d40 Dec 21 11:55:48 v2140 c7031740 Dec 21 11:55:48 v2140 0004 Dec 21 11:55:48 v2140 c4a57f30 Dec 21 11:55:48 v2140 0101 Dec 21 11:55:48 v2140 Dec 21 11:55:48 v2140 [ 7949.407632] Dec 21 11:55:48 v2140 0001 Dec 21 11:55:48 v2140 Dec 21 11:55:48 v2140 c01700fa Dec 21 11:55:48 v2140 c70316c0 Dec 21 11:55:48 v2140 0004 Dec 21 11:55:48 v2140 0004 Dec 21 11:55:48 v2140 bfe89140 Dec 21 11:55:48 v2140 1000 Dec 21 11:55:48 v2140 Dec 21 11:55:48 v2140 [ 7949.407716] Call Trace: Dec 21 11:55:48 v2140 [ 7949.407752] [c0103cd1] Dec 21 11:55:48 v2140 show_trace_log_lvl+0x2f/0x45 Dec 21 11:55:48 v2140 [ 7949.407789] [c0103daf] Dec 21 11:55:48 v2140 show_stack_log_lvl+0x9f/0xa7 Dec 21 11:55:48 v2140 [ 7949.407820] [c0103fc6] Dec 21 11:55:48 v2140 show_registers+0x1b1/0x242 Dec 21 11:55:48 v2140 [ 7949.407853] [c010424d] Dec 21 11:55:48 v2140 die+0x145/0x23a Dec 21 11:55:48 v2140 [ 7949.407884] [c057871f] Dec 21 11:55:48 v2140 do_page_fault+0x493/0x585 Dec 21 11:55:48 v2140 [ 7949.407921] [c0576cd9] Dec 21 11:55:48 v2140 error_code+0x39/0x40 Dec 21 11:55:48 v2140 [ 7949.407951] [c01ad889] Dec 21 11:55:48 v2140 proc_tgid_stat+0x20/0x22 Dec 21 11:55:48 v2140 [ 7949.407983] [c01a8101] Dec 21 11:55:48 v2140 proc_info_read+0x12f/0x17e Dec 21 11:55:48 v2140 [ 7949.408016] [c0170b6c] Dec 21 11:55:48 v2140 vfs_read+0xa3/0x177 Dec 21 11:55:48 v2140 [ 7949.408049] [c0170f0a] Dec 21 11:55:48 v2140 sys_read+0x47/0x6b Dec 21 11:55:48 v2140 [ 7949.408079] [c0102fbb] Dec 21 11:55:48 v2140 syscall_call+0x7/0xb Dec 21 11:55:48 v2140 [ 7949.408111] === Dec 21 11:55:48 v2140 [ 7949.408133] Code: Dec 21 11:55:48 v2140 45 Dec 21 11:55:48 v2140 84 Dec 21 11:55:48 v2140 00 Dec 21 11:55:48 v2140 00 Dec 21 11:55:48 v2140 00 Dec 21 11:55:48 v2140 00 Dec 21 11:55:48 v2140 c7 Dec 21 11:55:48 v2140 85 Dec 21 11:55:48 v2140 70 Dec 21 11:55:48 v2140 ff Dec 21 11:55:48 v2140 ff Dec 21 11:55:48 v2140 ff Dec 21 11:55:48 v2140 00 Dec 21 11:55:48 v2140 00
