Chelsio driver bug in offload mode
hey I am using chelsio offload stack to tranfer data between two back to back connected systems. Now I using lighttpd server and http browser. After three-way handskahe successful completed, when it start transfering of data it gives me the following warning and then close the socket. cxgb3 :01:00.0 CIM SDRAM address out of range (0x2) cxgb3 :01:00.0 encountered fatal error. operation suspended. cxgb3 :01:00.0 FW status: 0x0,0x0,0x0,0x0 n then i don't get anything on the browser side. As i have tried to debug the problem i found that when skb is nonlinear and skb->len became more then mtu, it give me this bug. After that i have tried to linearize the skb and send but other side it shows me a really html crapped data. i am not able to clearly debug the problem. what i am doing wrong. thanks - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Chelsio driver bug in offload mode
hey I am using chelsio offload stack to tranfer data between two back to back connected systems. Now I using lighttpd server and http browser. After three-way handskahe successful completed, when it start transfering of data it gives me the following warning and then close the socket. cxgb3 :01:00.0 CIM SDRAM address out of range (0x2) cxgb3 :01:00.0 encountered fatal error. operation suspended. cxgb3 :01:00.0 FW status: 0x0,0x0,0x0,0x0 n then i don't get anything on the browser side. As i have tried to debug the problem i found that when skb is nonlinear and skb-len became more then mtu, it give me this bug. After that i have tried to linearize the skb and send but other side it shows me a really html crapped data. i am not able to clearly debug the problem. what i am doing wrong. thanks - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
strange interaction of struct sock between PF_INET and PF_UNIX stack
hello LKML I am testing a customized TCP/IP offloaded stack code. Its working fine with basic data transmission in between two peers. After 6-7 packet transmission it suddnely give me null pointer dereference bug. The null pointer bug comes at unix datagram sockets. I don't understand the interaction of TCP/IP sock object with the unix datagram socket. the bug details has been attached 1. this is the first bug <1>[ 637.540746] BUG: unable to handle kernel NULL pointer dereference at virtual address 0004 <1>[ 637.549320] printing eip: <4>[ 637.552047] c126cd6e <1>[ 637.552049] *pde = <0>[ 637.554869] Oops: 0002 [#1] <0>[ 637.557687] SMP DEBUG_PAGEALLOC <4>[ 637.560972] Modules linked in: dcxgb3 upcxgb3 locxgb3 uhci_hcd intel_agp agpgart <0>[ 637.568675] CPU:0 <4>[ 637.568676] EIP:0060:[]Not tainted VLI <4>[ 637.568677] EFLAGS: 00010006 (2.6.18-debug #3) <0>[ 637.581026] EIP is at skb_dequeue+0x2e/0x60 <0>[ 637.585228] eax: ebx: f7b1c734 ecx: c1fcf530 edx: 0286 [0]more> <0>[ 637.592042] esi: f595dd80 edi: f7b1c740 ebp: f6791d1c esp: f6791d10 <0>[ 637.598849] ds: 007b es: 007b ss: 0068 <0>[ 637.602974] Process syslogd (pid: 3710, ti=f679 task=c1fcf530 task.ti=f679) <0>[ 637.610479] Stack: 03fe f7b1c680 f6791dbc f6791d54 c127033c f7b1c734 f7b1c734 7fff <0>[ 637.619233] f7b1c8ac f6791f20 f6791dbc f6791d54 c12e9199 03fe f6791f20 <0>[ 637.627990]f6791dbc f6791da0 c12ca1ab f7b1c680 f6791d90 0001 <0>[ 637.636745] Call Trace: <4>[ 637.639447] [] show_stack_log_lvl+0xb1/0xe0 <4>[ 637.644655] [] show_registers+0x1b5/0x240 <4>[ 637.649682] [] die+0x13e/0x390 <4>[ 637.653755] [] do_page_fault+0x32c/0x670 <4>[ 637.658698] [] error_code+0x39/0x40 <4>[ 637.663205] [] skb_recv_datagram+0x13c/0x210 <4>[ 637.668490] [] unix_dgram_recvmsg+0x7b/0x240 <4>[ 637.673777] [] sock_recvmsg+0xe5/0x110 <4>[ 637.678543] [] sys_recvfrom+0x97/0x100 <4>[ 637.683311] [] sys_recv+0x36/0x40 <4>[ 637.687645] [] sys_socketcall+0x163/0x260 <4>[ 637.692673] [] syscall_call+0x7/0xb <0>[ 637.697180] Code: 83 ec 0c 89 1c 24 8b 5d 08 89 7c 24 08 89 74 24 04 8d 7b 0c 89 f8 e8 b2 dd 07 00 8b 33 39 f3 89 c2 7 <0>[ 637.718832] EIP: [] skb_dequeue+0x2e/0x60 SS:ESP 0068:f6791d10 <4>[ 637.725643] [0]kdb> dcxgb3: driver code upcxgb3 and locxgb3: TCP/IP stack code. 2. the second bug after a delay of 10-15 second a softlock up bug raises. <0>[ 637.718832] EIP: [] skb_dequeue+0x2e/0x60 SS:ESP 0068:f6791d10 <4>[ 637.725643] <0>BUG: spinlock lockup on CPU#1, klogd/3746, f7b1c740 <4>[ 899.151233] [] show_trace+0x1b/0x20 <4>[ 899.155936] [] dump_stack+0x26/0x30 <4>[ 899.160643] [] _raw_spin_lock+0x110/0x150 <4>[ 899.165872] [] _spin_lock_irqsave+0x50/0x60 <4>[ 899.171289] [] skb_queue_tail+0x21/0x50 <4>[ 899.176357] [] unix_dgram_sendmsg+0x42c/0x510 <4>[ 899.181938] [] do_sock_write+0xb4/0xc0 <4>[ 899.186920] [] sock_aio_write+0x67/0x70 <4>[ 899.191974] [] do_sync_write+0xb9/0xf0 <4>[ 899.196936] [] vfs_write+0x190/0x1a0 <4>[ 899.201731] [] sys_write+0x47/0x70 <4>[ 899.206367] [] syscall_call+0x7/0xb and i am sure these two bugs are inter-related.. System Details: Linux helvella 2.6.18-debug #3 SMP Fri Aug 10 14:08:20 IST 2007 i686 GNU/Linux any suggestion why this interaction is happening. or what i am doing wrong? thank you - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
strange interaction of struct sock between PF_INET and PF_UNIX stack
hello LKML I am testing a customized TCP/IP offloaded stack code. Its working fine with basic data transmission in between two peers. After 6-7 packet transmission it suddnely give me null pointer dereference bug. The null pointer bug comes at unix datagram sockets. I don't understand the interaction of TCP/IP sock object with the unix datagram socket. the bug details has been attached 1. this is the first bug 1[ 637.540746] BUG: unable to handle kernel NULL pointer dereference at virtual address 0004 1[ 637.549320] printing eip: 4[ 637.552047] c126cd6e 1[ 637.552049] *pde = 0[ 637.554869] Oops: 0002 [#1] 0[ 637.557687] SMP DEBUG_PAGEALLOC 4[ 637.560972] Modules linked in: dcxgb3 upcxgb3 locxgb3 uhci_hcd intel_agp agpgart 0[ 637.568675] CPU:0 4[ 637.568676] EIP:0060:[c126cd6e]Not tainted VLI 4[ 637.568677] EFLAGS: 00010006 (2.6.18-debug #3) 0[ 637.581026] EIP is at skb_dequeue+0x2e/0x60 0[ 637.585228] eax: ebx: f7b1c734 ecx: c1fcf530 edx: 0286 [0]more 0[ 637.592042] esi: f595dd80 edi: f7b1c740 ebp: f6791d1c esp: f6791d10 0[ 637.598849] ds: 007b es: 007b ss: 0068 0[ 637.602974] Process syslogd (pid: 3710, ti=f679 task=c1fcf530 task.ti=f679) 0[ 637.610479] Stack: 03fe f7b1c680 f6791dbc f6791d54 c127033c f7b1c734 f7b1c734 7fff 0[ 637.619233] f7b1c8ac f6791f20 f6791dbc f6791d54 c12e9199 03fe f6791f20 0[ 637.627990]f6791dbc f6791da0 c12ca1ab f7b1c680 f6791d90 0001 0[ 637.636745] Call Trace: 4[ 637.639447] [c1004831] show_stack_log_lvl+0xb1/0xe0 4[ 637.644655] [c1004a65] show_registers+0x1b5/0x240 4[ 637.649682] [c1004c2e] die+0x13e/0x390 4[ 637.653755] [c12ec0bc] do_page_fault+0x32c/0x670 4[ 637.658698] [c1004341] error_code+0x39/0x40 4[ 637.663205] [c127033c] skb_recv_datagram+0x13c/0x210 4[ 637.668490] [c12ca1ab] unix_dgram_recvmsg+0x7b/0x240 4[ 637.673777] [c1267485] sock_recvmsg+0xe5/0x110 4[ 637.678543] [c1268e97] sys_recvfrom+0x97/0x100 4[ 637.683311] [c1268f36] sys_recv+0x36/0x40 4[ 637.687645] [c1269373] sys_socketcall+0x163/0x260 4[ 637.692673] [c1003793] syscall_call+0x7/0xb 0[ 637.697180] Code: 83 ec 0c 89 1c 24 8b 5d 08 89 7c 24 08 89 74 24 04 8d 7b 0c 89 f8 e8 b2 dd 07 00 8b 33 39 f3 89 c2 7 0[ 637.718832] EIP: [c126cd6e] skb_dequeue+0x2e/0x60 SS:ESP 0068:f6791d10 4[ 637.725643] [0]kdb dcxgb3: driver code upcxgb3 and locxgb3: TCP/IP stack code. 2. the second bug after a delay of 10-15 second a softlock up bug raises. 0[ 637.718832] EIP: [c126cd6e] skb_dequeue+0x2e/0x60 SS:ESP 0068:f6791d10 4[ 637.725643] 0BUG: spinlock lockup on CPU#1, klogd/3746, f7b1c740 4[ 899.151233] [c10048ab] show_trace+0x1b/0x20 4[ 899.155936] [c1004ff6] dump_stack+0x26/0x30 4[ 899.160643] [c114b160] _raw_spin_lock+0x110/0x150 4[ 899.165872] [c12eab60] _spin_lock_irqsave+0x50/0x60 4[ 899.171289] [c126cc51] skb_queue_tail+0x21/0x50 4[ 899.176357] [c12c8f5c] unix_dgram_sendmsg+0x42c/0x510 4[ 899.181938] [c1267074] do_sock_write+0xb4/0xc0 4[ 899.186920] [c1267807] sock_aio_write+0x67/0x70 4[ 899.191974] [c1067ea9] do_sync_write+0xb9/0xf0 4[ 899.196936] [c10689c0] vfs_write+0x190/0x1a0 4[ 899.201731] [c1069107] sys_write+0x47/0x70 4[ 899.206367] [c1003793] syscall_call+0x7/0xb and i am sure these two bugs are inter-related.. System Details: Linux helvella 2.6.18-debug #3 SMP Fri Aug 10 14:08:20 IST 2007 i686 GNU/Linux any suggestion why this interaction is happening. or what i am doing wrong? thank you - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
inet_csk_listen_start: function defination
hi all i am bit confused with the function defination of inet_listen. How a listen socket can listen and return to application at a time. since a server stops at accpet not at listen then how listening port start. I was thinking that the listen call thread out at the tcp_v4_hash function time but it actaully does not use any thread fucntion and simple return so how does the listening socket start. thanks TEJ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
inet_csk_listen_start: function defination
hi all i am bit confused with the function defination of inet_listen. How a listen socket can listen and return to application at a time. since a server stops at accpet not at listen then how listening port start. I was thinking that the listen call thread out at the tcp_v4_hash function time but it actaully does not use any thread fucntion and simple return so how does the listening socket start. thanks TEJ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
reg: kprobe method
hi all
there is some problem in adding simple printk using kprobe method
i m posting the my code anybody can suggest how to make it work
#include
#include
#include
#include
#include
#include
MODULE_AUTHOR("TEJ");
MODULE_LICENSE("GPL");
//MODULE_PARM(int,val,I_IRUGO);
struct kprobe kp;
static int handler_pre(struct kprobe *p, struct pt_regs *regs)
{
printk("my name is tej parkash dhiman");
return 0;
}
void handler_post(struct kprobe *p, struct pt_regs *regs, unsigned long flags)
{
printk("mast hai na tej ash ker");
}
static int init_mod(void)
{
struct kprobe kp;
kp.post_handler=handler_post;
kp.pre_handler=handler_pre;
kp.addr = (kprobe_opcode_t *) 0xc0278e50; //add for __sock_create
if(kp.addr== NULL) {
printk("kallsyms_lookup_name could not find address
for the specified symbol name\n");
return 0;
}
register_kprobe();
printk("Module is inserted");
return 0;
}
void exit_mod(void)
{
unregister_kprobe();
printk("module is removed");
}
module_init(init_mod);
module_exit(exit_mod);
thanks
TEJ
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
reg: kprobe method
hi all
there is some problem in adding simple printk using kprobe method
i m posting the my code anybody can suggest how to make it work
#includelinux/kernel.h
#includelinux/version.h
#includelinux/module.h
#includelinux/init.h
#includelinux/kprobes.h
#includelinux/kallsyms.h
MODULE_AUTHOR(TEJ);
MODULE_LICENSE(GPL);
//MODULE_PARM(int,val,I_IRUGO);
struct kprobe kp;
static int handler_pre(struct kprobe *p, struct pt_regs *regs)
{
printk(my name is tej parkash dhiman);
return 0;
}
void handler_post(struct kprobe *p, struct pt_regs *regs, unsigned long flags)
{
printk(mast hai na tej ash ker);
}
static int init_mod(void)
{
struct kprobe kp;
kp.post_handler=handler_post;
kp.pre_handler=handler_pre;
kp.addr = (kprobe_opcode_t *) 0xc0278e50; //add for __sock_create
if(kp.addr== NULL) {
printk(kallsyms_lookup_name could not find address
for the specified symbol name\n);
return 0;
}
register_kprobe(kp);
printk(Module is inserted);
return 0;
}
void exit_mod(void)
{
unregister_kprobe(kp);
printk(module is removed);
}
module_init(init_mod);
module_exit(exit_mod);
thanks
TEJ
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-kernel-digest Digest, Vol 32, Issue 795
On 5/30/07, Sam Ravnborg <[EMAIL PROTECTED]> wrote: On Wed, May 30, 2007 at 08:07:53PM +0530, Tej Parkash wrote: > On 5/30/07, Tej Parkash <[EMAIL PROTECTED]> wrote: > >> > > > >> > > while building module i was getting following warning and it > >terminate > >> > > module building stage > >> > The below are only warnings and your build should succeed. > >> > > >> > It is obviously i386 - is it a clean allmodconfig or any changes? > >> > Is it latest -linus or some older version of the codebase? > >> Did an allmodconfig build of i386 - I see (almost) all warnings here. > >> So I will take a look based on this. > > yaa i got the warning but as i said building stage is also getting > terminated, without any error. > > >The MODPOST stage took a while but it proceeded with no hick-ups. > > MDOPSOT deals with ~2000 modules in my case and that consumes a bit > > of memory. Maybe you are hitting the limit with respect to available RAM > > / SWAP? > > > >Sam > > > > > I don't think so that RAM or SWAP space is a constraint, is it related > to kernel build option or some change in arch. config files > I am not aware of the required patches for the same. Can you please post relevant parts of a build with make V=2 That is the last couple of commands before the build suddenly stops. Also to error-code reported by make must be included. Ohh, and exact command-line + config you use. Sam make -C /lib/modules/2.6.21.3/build/ SUBDIR=/home/tej/Offload modules make[1]: Entering directory `/home/tej/linux_src/linux-2.6.21.3' CHK include/linux/version.h CHK include/linux/utsrelease.h Building modules, stage 2. MODPOST 1889 modules WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .text between 'is386' (at offset 0xc0101171) and 'check_x87' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xc0101458) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010adfb) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010ae11) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:sysenter_setup from .text between 'identify_cpu' (at offset 0xc010b46b) and 'display_cacheinfo' WARNING: vmlinux - Section mismatch: reference to .init.text:mtrr_bp_init from .text between 'identify_cpu' (at offset 0xc010b475) and 'display_cacheinfo' WARNING: vmlinux - Section mismatch: reference to .init.text:trap_init_f00f_bug from .text between 'init_intel' (at offset 0xc010d576) and 'cpuid4_cache_lookup' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f2c2e) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'set_up_list3s' (at offset 0xc0173aff) and 's_start' WARNING: vmlinux - Section mismatch: reference to .init.text:eisa_root_register from .text between 'virtual_eisa_root_init' (at offset 0xc026fecf) and 'cpufreq_unregister_driver' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f32c8) and '_etext' make[1]: Leaving directory `/home/tej/linux_src/linux-2.6.21.3' the actaul kernel where i am running this make is in /home/tej/linux_src/linux-2.6.21.3. thanks tej - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-kernel-digest Digest, Vol 32, Issue 795
On 5/30/07, Tej Parkash <[EMAIL PROTECTED]> wrote: > > > > > > while building module i was getting following warning and it terminate > > > module building stage > > The below are only warnings and your build should succeed. > > > > It is obviously i386 - is it a clean allmodconfig or any changes? > > Is it latest -linus or some older version of the codebase? > Did an allmodconfig build of i386 - I see (almost) all warnings here. > So I will take a look based on this. yaa i got the warning but as i said building stage is also getting terminated, without any error. The MODPOST stage took a while but it proceeded with no hick-ups. MDOPSOT deals with ~2000 modules in my case and that consumes a bit of memory. Maybe you are hitting the limit with respect to available RAM / SWAP? Sam I don't think so that RAM or SWAP space is a constraint, is it related to kernel build option or some change in arch. config files I am not aware of the required patches for the same. thanks TEJ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-kernel-digest Digest, Vol 32, Issue 795
On 5/30/07, Tej Parkash [EMAIL PROTECTED] wrote: while building module i was getting following warning and it terminate module building stage The below are only warnings and your build should succeed. It is obviously i386 - is it a clean allmodconfig or any changes? Is it latest -linus or some older version of the codebase? Did an allmodconfig build of i386 - I see (almost) all warnings here. So I will take a look based on this. yaa i got the warning but as i said building stage is also getting terminated, without any error. The MODPOST stage took a while but it proceeded with no hick-ups. MDOPSOT deals with ~2000 modules in my case and that consumes a bit of memory. Maybe you are hitting the limit with respect to available RAM / SWAP? Sam I don't think so that RAM or SWAP space is a constraint, is it related to kernel build option or some change in arch. config files I am not aware of the required patches for the same. thanks TEJ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-kernel-digest Digest, Vol 32, Issue 795
On 5/30/07, Sam Ravnborg [EMAIL PROTECTED] wrote: On Wed, May 30, 2007 at 08:07:53PM +0530, Tej Parkash wrote: On 5/30/07, Tej Parkash [EMAIL PROTECTED] wrote: while building module i was getting following warning and it terminate module building stage The below are only warnings and your build should succeed. It is obviously i386 - is it a clean allmodconfig or any changes? Is it latest -linus or some older version of the codebase? Did an allmodconfig build of i386 - I see (almost) all warnings here. So I will take a look based on this. yaa i got the warning but as i said building stage is also getting terminated, without any error. The MODPOST stage took a while but it proceeded with no hick-ups. MDOPSOT deals with ~2000 modules in my case and that consumes a bit of memory. Maybe you are hitting the limit with respect to available RAM / SWAP? Sam I don't think so that RAM or SWAP space is a constraint, is it related to kernel build option or some change in arch. config files I am not aware of the required patches for the same. Can you please post relevant parts of a build with make V=2 That is the last couple of commands before the build suddenly stops. Also to error-code reported by make must be included. Ohh, and exact command-line + config you use. Sam make -C /lib/modules/2.6.21.3/build/ SUBDIR=/home/tej/Offload modules make[1]: Entering directory `/home/tej/linux_src/linux-2.6.21.3' CHK include/linux/version.h CHK include/linux/utsrelease.h Building modules, stage 2. MODPOST 1889 modules WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .text between 'is386' (at offset 0xc0101171) and 'check_x87' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xc0101458) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010adfb) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010ae11) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:sysenter_setup from .text between 'identify_cpu' (at offset 0xc010b46b) and 'display_cacheinfo' WARNING: vmlinux - Section mismatch: reference to .init.text:mtrr_bp_init from .text between 'identify_cpu' (at offset 0xc010b475) and 'display_cacheinfo' WARNING: vmlinux - Section mismatch: reference to .init.text:trap_init_f00f_bug from .text between 'init_intel' (at offset 0xc010d576) and 'cpuid4_cache_lookup' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f2c2e) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'set_up_list3s' (at offset 0xc0173aff) and 's_start' WARNING: vmlinux - Section mismatch: reference to .init.text:eisa_root_register from .text between 'virtual_eisa_root_init' (at offset 0xc026fecf) and 'cpufreq_unregister_driver' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f32c8) and '_etext' make[1]: Leaving directory `/home/tej/linux_src/linux-2.6.21.3' the actaul kernel where i am running this make is in /home/tej/linux_src/linux-2.6.21.3. thanks tej - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
warning while building module.
hi all while building module i was getting following warning and it terminate module building stage MODPOST 1889 modules WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .text between 'is386' (at offset 0xc0101171) and 'check_x87' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xc0101458) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010adfb) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010ae11) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:sysenter_setup from .text between 'identify_cpu' (at offset 0xc010b46b) and 'display_cacheinfo' WARNING: vmlinux - Section mismatch: reference to .init.text:mtrr_bp_init from .text between 'identify_cpu' (at offset 0xc010b475) and 'display_cacheinfo' WARNING: vmlinux - Section mismatch: reference to .init.text:trap_init_f00f_bug from .text between 'init_intel' (at offset 0xc010d576) and 'cpuid4_cache_lookup' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f2c2e) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'set_up_list3s' (at offset 0xc0173aff) and 's_start' WARNING: vmlinux - Section mismatch: reference to .init.text:eisa_root_register from .text between 'virtual_eisa_root_init' (at offset 0xc026fecf) and 'cpufreq_unregister_driver' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f32c8) and '_etext' i was trying to fix with online available patches but does not help out. please cc to me thanks TEJ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
warning while building module.
hi all while building module i was getting following warning and it terminate module building stage MODPOST 1889 modules WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .text between 'is386' (at offset 0xc0101171) and 'check_x87' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xc0101458) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010adfb) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc010ae11) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:sysenter_setup from .text between 'identify_cpu' (at offset 0xc010b46b) and 'display_cacheinfo' WARNING: vmlinux - Section mismatch: reference to .init.text:mtrr_bp_init from .text between 'identify_cpu' (at offset 0xc010b475) and 'display_cacheinfo' WARNING: vmlinux - Section mismatch: reference to .init.text:trap_init_f00f_bug from .text between 'init_intel' (at offset 0xc010d576) and 'cpuid4_cache_lookup' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f2c2e) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'set_up_list3s' (at offset 0xc0173aff) and 's_start' WARNING: vmlinux - Section mismatch: reference to .init.text:eisa_root_register from .text between 'virtual_eisa_root_init' (at offset 0xc026fecf) and 'cpufreq_unregister_driver' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc02f32c8) and '_etext' i was trying to fix with online available patches but does not help out. please cc to me thanks TEJ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: reg: modules make in Ubuntu
On 5/26/07, Sam Ravnborg <[EMAIL PROTECTED]> wrote: On Sat, May 26, 2007 at 01:28:56AM -0400, Tej Parkash wrote: > make[1]: Entering directory `/usr/src/linux-headers-2.6.20-15-generic' > CHK include/linux/version.h > CHK include/linux/utsrelease.h > make[2]: *** No rule to make target `arch/i386/kernel/msr.c', needed > by `arch/i386/kernel/msr.o'. Stop. > make[1]: *** [arch/i386/kernel] Error 2 > make[1]: Leaving directory `/usr/src/linux-headers-2.6.20-15-generic' > make: *** [all] Error 2 > > what the hack is this. no kernel version is having this file in this > particular location as asked in error. then why this error is coming > in this kernel version. Looks like you are trying to build a kernel but have only headers judging from the directoryname. yaa u r correct but i am wondering like how those file can be missed from the required location. if they are so important to build the module.. even if it is missed is there any other procedure to build the module i am trying it on other kernel version. Could you please prove a bit more context if you need additional help. Like (but not limited to): -> Actual commandline -> Any own kbuild/Makefiles -> .config Sam thanks tej - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: reg: modules make in Ubuntu
On 5/26/07, Sam Ravnborg [EMAIL PROTECTED] wrote: On Sat, May 26, 2007 at 01:28:56AM -0400, Tej Parkash wrote: make[1]: Entering directory `/usr/src/linux-headers-2.6.20-15-generic' CHK include/linux/version.h CHK include/linux/utsrelease.h make[2]: *** No rule to make target `arch/i386/kernel/msr.c', needed by `arch/i386/kernel/msr.o'. Stop. make[1]: *** [arch/i386/kernel] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-2.6.20-15-generic' make: *** [all] Error 2 what the hack is this. no kernel version is having this file in this particular location as asked in error. then why this error is coming in this kernel version. Looks like you are trying to build a kernel but have only headers judging from the directoryname. yaa u r correct but i am wondering like how those file can be missed from the required location. if they are so important to build the module.. even if it is missed is there any other procedure to build the module i am trying it on other kernel version. Could you please prove a bit more context if you need additional help. Like (but not limited to): - Actual commandline - Any own kbuild/Makefiles - .config Sam thanks tej - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
reg: modules make in Ubuntu
make[1]: Entering directory `/usr/src/linux-headers-2.6.20-15-generic' CHK include/linux/version.h CHK include/linux/utsrelease.h make[2]: *** No rule to make target `arch/i386/kernel/msr.c', needed by `arch/i386/kernel/msr.o'. Stop. make[1]: *** [arch/i386/kernel] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-2.6.20-15-generic' make: *** [all] Error 2 what the hack is this. no kernel version is having this file in this particular location as asked in error. then why this error is coming in this kernel version. TEJ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Reg: redundancy in inet socket
list_for_each_rcu(p, [sock->type]) {
answer = list_entry(p, struct inet_protosw, list);
/* Check the non-wild match. */
if (protocol == answer->protocol) {
if (protocol != IPPROTO_IP)
break;
} else {
/* Check for the two wild cases. */
if (IPPROTO_IP == protocol) {
protocol = answer->protocol;
break;
}
if (IPPROTO_IP == answer->protocol)
break;
}
i think there is a problem in this code because if (protocol ==
answer->protocol) will be more like an assignment rather then
comparison
pl cc to me.
TEJ
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH - 1/1] Reg: __builtin_expect(!!(x), 0)
what is this hack and why it is required - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH - 1/1] Reg: __builtin_expect(!!(x), 0)
what is this hack and why it is required - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Reg: redundancy in inet socket
list_for_each_rcu(p, inetsw[sock-type]) {
answer = list_entry(p, struct inet_protosw, list);
/* Check the non-wild match. */
if (protocol == answer-protocol) {
if (protocol != IPPROTO_IP)
break;
} else {
/* Check for the two wild cases. */
if (IPPROTO_IP == protocol) {
protocol = answer-protocol;
break;
}
if (IPPROTO_IP == answer-protocol)
break;
}
i think there is a problem in this code because if (protocol ==
answer-protocol) will be more like an assignment rather then
comparison
pl cc to me.
TEJ
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
reg: modules make in Ubuntu
make[1]: Entering directory `/usr/src/linux-headers-2.6.20-15-generic' CHK include/linux/version.h CHK include/linux/utsrelease.h make[2]: *** No rule to make target `arch/i386/kernel/msr.c', needed by `arch/i386/kernel/msr.o'. Stop. make[1]: *** [arch/i386/kernel] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-2.6.20-15-generic' make: *** [all] Error 2 what the hack is this. no kernel version is having this file in this particular location as asked in error. then why this error is coming in this kernel version. TEJ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
