Re: 2.6.21.14 NFS related oops
Trond Myklebust pisze:
On Wed, 2007-06-13 at 14:00 +0200, Maciej Soltysiak wrote:
Hi,
If anyone is interested I got this OOPS while running a torrent
(btdownloadcurses)
application writing directly to a NAS mounted via nfs3.
The client machine is 2.6.21.14 and it is mounted with options:
wsize=8192,rsize=8192,hard,intr,tcp
Hmm. The Oops says '2.6.20.14-cks1'
Firstly, does that have any extra out-of-tree patches?
Secondly, is it reproducible with 2.6.21 or a more recent kernel?
Ah, yes, 2.6.20.14 not 2.6.21.14 and it does contain 2 extra things:
- Con Kolivas' -cks1 (server version)
- reiser4 code, one mounted filesystem.
After that, the application hung and i am unable to cd into the mounted
nfs directory
nor unmount it (busy), nor kill the app (kill -9 fails, process in D state)
Best regards,
Maciej
BUG: unable to handle kernel paging request at virtual address 5018f248
printing eip:
f0a93c94
*pde =
Oops: 0002 [#1]
Modules linked in: binfmt_misc sit nfs lockd nfs_acl sunrpc w83627ehf
i2c_isa i2c_viapro i2c_core via_agp agpgart rtc
CPU:0
EIP:0060:[]Not tainted VLI
EFLAGS: 00010206 (2.6.20.14-cks1 #15)
EIP is at rpcauth_checkverf+0x34/0x70 [sunrpc]
eax: d2f4447c ebx: c655d584 ecx: edx: f0aa9f60
esi: e91ea640 edi: d2f44474 ebp: ede2f228 esp: e64b5eec
ds: 007b es: 007b ss: 0068
Process rpciod/0 (pid: 1005, ti=e64b4000 task=efe95a90 task.ti=e64b4000)
Stack: 0286 ede2f8a0 ede2f8a0 0286 c655d584 121d0da3 0820
f0a8d7fd
f0a93d60 f08bae07 0286 c655d5cc 0286 0286 f08c0520
c655d584
c655d5ec f0a93260 f0a9306f efe95a90 ee2d5740 e092ffb0
c034e11c
Call Trace:
[] call_decode+0x27d/0x5e0 [sunrpc]
[] rpcauth_unbindcred+0x20/0x60 [sunrpc]
[] nfs_readpage_result_full+0xf7/0x120 [nfs]
[] nfs3_xdr_readres+0x0/0x160 [nfs]
[] rpc_async_schedule+0x0/0x10 [sunrpc]
[] __rpc_execute+0x5f/0x250 [sunrpc]
[] schedule+0x21c/0x450
[] run_workqueue+0x7a/0x110
[] worker_thread+0x137/0x160
[] default_wake_function+0x0/0x10
[] worker_thread+0x0/0x160
[] kthread+0xa9/0xe0
[] kthread+0x0/0xe0
[] kernel_thread_helper+0x7/0x10
===
Code: 10 89 5c 24 10 89 c3 89 7c 24 18 89 d7 89 74 24 14 8b 70 28 75 1a 8b
4e 08 89 fa 89 d8 ff 51 18 8b 5c 24 10 83 74 24 14 8b 7c 24 <18> 83 c4 1c c3
89 74 24 0c 8b 40 10 8b 40 24 8b 40 10 8b 40 08 EIP: []
rpcauth_checkverf+0x34/0x70 [sunrpc] SS:ESP 0068:e64b5eec
At a first guess, it looks as though something has scribbled over your
credential. Have you tried running this kernel with slab debugging
enabled?
No, i will turn it on, though. The server crashes on heavy NFS traffic
(eg. nightly rsync backup)
It crashed again today, but the oops did not get written to kern.log
Cheers
Trond
Thanks for your reply and best regards,
Maciej
-
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: 2.6.21.14 NFS related oops
Trond Myklebust pisze:
On Wed, 2007-06-13 at 14:00 +0200, Maciej Soltysiak wrote:
Hi,
If anyone is interested I got this OOPS while running a torrent
(btdownloadcurses)
application writing directly to a NAS mounted via nfs3.
The client machine is 2.6.21.14 and it is mounted with options:
wsize=8192,rsize=8192,hard,intr,tcp
Hmm. The Oops says '2.6.20.14-cks1'
Firstly, does that have any extra out-of-tree patches?
Secondly, is it reproducible with 2.6.21 or a more recent kernel?
Ah, yes, 2.6.20.14 not 2.6.21.14 and it does contain 2 extra things:
- Con Kolivas' -cks1 (server version)
- reiser4 code, one mounted filesystem.
After that, the application hung and i am unable to cd into the mounted
nfs directory
nor unmount it (busy), nor kill the app (kill -9 fails, process in D state)
Best regards,
Maciej
BUG: unable to handle kernel paging request at virtual address 5018f248
printing eip:
f0a93c94
*pde =
Oops: 0002 [#1]
Modules linked in: binfmt_misc sit nfs lockd nfs_acl sunrpc w83627ehf
i2c_isa i2c_viapro i2c_core via_agp agpgart rtc
CPU:0
EIP:0060:[f0a93c94]Not tainted VLI
EFLAGS: 00010206 (2.6.20.14-cks1 #15)
EIP is at rpcauth_checkverf+0x34/0x70 [sunrpc]
eax: d2f4447c ebx: c655d584 ecx: edx: f0aa9f60
esi: e91ea640 edi: d2f44474 ebp: ede2f228 esp: e64b5eec
ds: 007b es: 007b ss: 0068
Process rpciod/0 (pid: 1005, ti=e64b4000 task=efe95a90 task.ti=e64b4000)
Stack: 0286 ede2f8a0 ede2f8a0 0286 c655d584 121d0da3 0820
f0a8d7fd
f0a93d60 f08bae07 0286 c655d5cc 0286 0286 f08c0520
c655d584
c655d5ec f0a93260 f0a9306f efe95a90 ee2d5740 e092ffb0
c034e11c
Call Trace:
[f0a8d7fd] call_decode+0x27d/0x5e0 [sunrpc]
[f0a93d60] rpcauth_unbindcred+0x20/0x60 [sunrpc]
[f08bae07] nfs_readpage_result_full+0xf7/0x120 [nfs]
[f08c0520] nfs3_xdr_readres+0x0/0x160 [nfs]
[f0a93260] rpc_async_schedule+0x0/0x10 [sunrpc]
[f0a9306f] __rpc_execute+0x5f/0x250 [sunrpc]
[c034e11c] schedule+0x21c/0x450
[c01283aa] run_workqueue+0x7a/0x110
[c0128a07] worker_thread+0x137/0x160
[c01176b0] default_wake_function+0x0/0x10
[c01288d0] worker_thread+0x0/0x160
[c012b329] kthread+0xa9/0xe0
[c012b280] kthread+0x0/0xe0
[c0103a97] kernel_thread_helper+0x7/0x10
===
Code: 10 89 5c 24 10 89 c3 89 7c 24 18 89 d7 89 74 24 14 8b 70 28 75 1a 8b
4e 08 89 fa 89 d8 ff 51 18 8b 5c 24 10 83 74 24 14 8b 7c 24 18 83 c4 1c c3
89 74 24 0c 8b 40 10 8b 40 24 8b 40 10 8b 40 08 EIP: [f0a93c94]
rpcauth_checkverf+0x34/0x70 [sunrpc] SS:ESP 0068:e64b5eec
At a first guess, it looks as though something has scribbled over your
credential. Have you tried running this kernel with slab debugging
enabled?
No, i will turn it on, though. The server crashes on heavy NFS traffic
(eg. nightly rsync backup)
It crashed again today, but the oops did not get written to kern.log
Cheers
Trond
Thanks for your reply and best regards,
Maciej
-
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/
2.6.21.14 NFS related oops
Hi, If anyone is interested I got this OOPS while running a torrent (btdownloadcurses) application writing directly to a NAS mounted via nfs3. The client machine is 2.6.21.14 and it is mounted with options: wsize=8192,rsize=8192,hard,intr,tcp After that, the application hung and i am unable to cd into the mounted nfs directory nor unmount it (busy), nor kill the app (kill -9 fails, process in D state) Best regards, Maciej BUG: unable to handle kernel paging request at virtual address 5018f248 printing eip: f0a93c94 *pde = Oops: 0002 [#1] Modules linked in: binfmt_misc sit nfs lockd nfs_acl sunrpc w83627ehf i2c_isa i2c_viapro i2c_core via_agp agpgart rtc CPU:0 EIP:0060:[]Not tainted VLI EFLAGS: 00010206 (2.6.20.14-cks1 #15) EIP is at rpcauth_checkverf+0x34/0x70 [sunrpc] eax: d2f4447c ebx: c655d584 ecx: edx: f0aa9f60 esi: e91ea640 edi: d2f44474 ebp: ede2f228 esp: e64b5eec ds: 007b es: 007b ss: 0068 Process rpciod/0 (pid: 1005, ti=e64b4000 task=efe95a90 task.ti=e64b4000) Stack: 0286 ede2f8a0 ede2f8a0 0286 c655d584 121d0da3 0820 f0a8d7fd f0a93d60 f08bae07 0286 c655d5cc 0286 0286 f08c0520 c655d584 c655d5ec f0a93260 f0a9306f efe95a90 ee2d5740 e092ffb0 c034e11c Call Trace: [] call_decode+0x27d/0x5e0 [sunrpc] [] rpcauth_unbindcred+0x20/0x60 [sunrpc] [] nfs_readpage_result_full+0xf7/0x120 [nfs] [] nfs3_xdr_readres+0x0/0x160 [nfs] [] rpc_async_schedule+0x0/0x10 [sunrpc] [] __rpc_execute+0x5f/0x250 [sunrpc] [] schedule+0x21c/0x450 [] run_workqueue+0x7a/0x110 [] worker_thread+0x137/0x160 [] default_wake_function+0x0/0x10 [] worker_thread+0x0/0x160 [] kthread+0xa9/0xe0 [] kthread+0x0/0xe0 [] kernel_thread_helper+0x7/0x10 === Code: 10 89 5c 24 10 89 c3 89 7c 24 18 89 d7 89 74 24 14 8b 70 28 75 1a 8b 4e 08 89 fa 89 d8 ff 51 18 8b 5c 24 10 83 74 24 14 8b 7c 24 <18> 83 c4 1c c3 89 74 24 0c 8b 40 10 8b 40 24 8b 40 10 8b 40 08 EIP: [] rpcauth_checkverf+0x34/0x70 [sunrpc] SS:ESP 0068:e64b5eec - 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/
2.6.21.14 NFS related oops
Hi, If anyone is interested I got this OOPS while running a torrent (btdownloadcurses) application writing directly to a NAS mounted via nfs3. The client machine is 2.6.21.14 and it is mounted with options: wsize=8192,rsize=8192,hard,intr,tcp After that, the application hung and i am unable to cd into the mounted nfs directory nor unmount it (busy), nor kill the app (kill -9 fails, process in D state) Best regards, Maciej BUG: unable to handle kernel paging request at virtual address 5018f248 printing eip: f0a93c94 *pde = Oops: 0002 [#1] Modules linked in: binfmt_misc sit nfs lockd nfs_acl sunrpc w83627ehf i2c_isa i2c_viapro i2c_core via_agp agpgart rtc CPU:0 EIP:0060:[f0a93c94]Not tainted VLI EFLAGS: 00010206 (2.6.20.14-cks1 #15) EIP is at rpcauth_checkverf+0x34/0x70 [sunrpc] eax: d2f4447c ebx: c655d584 ecx: edx: f0aa9f60 esi: e91ea640 edi: d2f44474 ebp: ede2f228 esp: e64b5eec ds: 007b es: 007b ss: 0068 Process rpciod/0 (pid: 1005, ti=e64b4000 task=efe95a90 task.ti=e64b4000) Stack: 0286 ede2f8a0 ede2f8a0 0286 c655d584 121d0da3 0820 f0a8d7fd f0a93d60 f08bae07 0286 c655d5cc 0286 0286 f08c0520 c655d584 c655d5ec f0a93260 f0a9306f efe95a90 ee2d5740 e092ffb0 c034e11c Call Trace: [f0a8d7fd] call_decode+0x27d/0x5e0 [sunrpc] [f0a93d60] rpcauth_unbindcred+0x20/0x60 [sunrpc] [f08bae07] nfs_readpage_result_full+0xf7/0x120 [nfs] [f08c0520] nfs3_xdr_readres+0x0/0x160 [nfs] [f0a93260] rpc_async_schedule+0x0/0x10 [sunrpc] [f0a9306f] __rpc_execute+0x5f/0x250 [sunrpc] [c034e11c] schedule+0x21c/0x450 [c01283aa] run_workqueue+0x7a/0x110 [c0128a07] worker_thread+0x137/0x160 [c01176b0] default_wake_function+0x0/0x10 [c01288d0] worker_thread+0x0/0x160 [c012b329] kthread+0xa9/0xe0 [c012b280] kthread+0x0/0xe0 [c0103a97] kernel_thread_helper+0x7/0x10 === Code: 10 89 5c 24 10 89 c3 89 7c 24 18 89 d7 89 74 24 14 8b 70 28 75 1a 8b 4e 08 89 fa 89 d8 ff 51 18 8b 5c 24 10 83 74 24 14 8b 7c 24 18 83 c4 1c c3 89 74 24 0c 8b 40 10 8b 40 24 8b 40 10 8b 40 08 EIP: [f0a93c94] rpcauth_checkverf+0x34/0x70 [sunrpc] SS:ESP 0068:e64b5eec - 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/
2.6.20.4 crashes
Hi, here's more... BUG: unable to handle kernel NULL pointer dereference at virtual address printing eip: *pde = Oops: [#1] Modules linked in: binfmt_misc sit nfs lockd nfs_acl sunrpc ipt_ECN iptable_mangle w83627ehf i2c_isa i2c_viapro i2c_core via_agp agpgart rtc CPU:0 EIP:0060:[<>]Not tainted VLI EFLAGS: 00010016 (2.6.20.3-cks1 #4) EIP is at 0x0 eax: e94a5e6c ebx: e94a5e6c ecx: edx: 0001 esi: edi: e94a5e84 ebp: e94a5e6c esp: e94a5e4c ds: 007b es: 007b ss: 0068 Process grep (pid: 9156, ti=e94a4000 task=f4569a90 task.ti=e94a4000) Stack: c0116429 0001 0001 ec7da800 0286 e94a5e84 c0117802 ec7da800 ec7da800 ec7da85c c015c622 e9d02b40 e94a5f60 f77b6ac0 0400 c0313e6c 1000 Call Trace: [] __wake_up_common+0x39/0x70 [] __wake_up+0x22/0x30 [] pipe_write+0x222/0x4b0 [] do_sync_write+0xc7/0x110 [] autoremove_wake_function+0x0/0x50 [] vfs_write+0xa6/0x160 [] do_sync_write+0x0/0x110 [] sys_write+0x41/0x70 [] sysenter_past_esp+0x5f/0x85 [] ipv6_flowlabel_opt+0x193/0x730 === Code: Bad EIP value. EIP: [<>] 0x0 SS:ESP 0068:e94a5e4c <3>BUG: sleeping function called from invalid context at kernel/rwsem.c:20 in_atomic():0, irqs_disabled():1 [] down_read+0x12/0x20 [] acct_collect+0x38/0x120 [] do_exit+0xda/0x750 [] printk+0x1b/0x20 [] do_trap+0x0/0x100 [] do_page_fault+0x2da/0x630 [] do_page_fault+0x0/0x630 [] error_code+0x74/0x7c [] __wake_up_common+0x39/0x70 [] __wake_up+0x22/0x30 [] pipe_write+0x222/0x4b0 [] do_sync_write+0xc7/0x110 [] autoremove_wake_function+0x0/0x50 [] vfs_write+0xa6/0x160 [] do_sync_write+0x0/0x110 [] sys_write+0x41/0x70 [] sysenter_past_esp+0x5f/0x85 [] ipv6_flowlabel_opt+0x193/0x730 === BUG: unable to handle kernel NULL pointer dereference at virtual address printing eip: *pde = Oops: [#2] Modules linked in: binfmt_misc sit nfs lockd nfs_acl sunrpc ipt_ECN iptable_mangle w83627ehf i2c_isa i2c_viapro i2c_core via_agp agpgart rtc CPU:0 EIP:0060:[<>]Not tainted VLI EFLAGS: 00010087 (2.6.20.3-cks1 #4) EIP is at 0x0 eax: e94a5e6c ebx: e94a5e6c ecx: edx: 0001 esi: edi: e94a5e84 ebp: e94a5ccc esp: e94a5cac ds: 007b es: 007b ss: 0068 Process grep (pid: 9156, ti=e94a4000 task=f4569a90 task.ti=e94a4000) Stack: c0116429 0001 0001 ec7da800 0286 ec7da800 e94a5ce4 c0117802 0001 e9d02ad4 c015c069 e9d02b40 0008 e9d02ad4 f77b6ac0 c0157b20 Call Trace: [] __wake_up_common+0x39/0x70 [] __wake_up+0x22/0x30 [] pipe_release+0x59/0xb0 [] __fput+0xb0/0x180 [] filp_close+0x47/0x80 [] put_files_struct+0x9c/0xb0 [] do_exit+0x115/0x750 [] printk+0x1b/0x20 [] do_trap+0x0/0x100 [] do_page_fault+0x2da/0x630 [] do_page_fault+0x0/0x630 [] error_code+0x74/0x7c [] __wake_up_common+0x39/0x70 [] __wake_up+0x22/0x30 [] pipe_write+0x222/0x4b0 [] do_sync_write+0xc7/0x110 [] autoremove_wake_function+0x0/0x50 [] vfs_write+0xa6/0x160 [] do_sync_write+0x0/0x110 [] sys_write+0x41/0x70 [] sysenter_past_esp+0x5f/0x85 [] ipv6_flowlabel_opt+0x193/0x730 === Code: Bad EIP value. EIP: [<>] 0x0 SS:ESP 0068:e94a5cac <1>Fixing recursive fault but reboot is needed! - 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/
2.6.20.4 crashes
Hi, here's more... BUG: unable to handle kernel NULL pointer dereference at virtual address printing eip: *pde = Oops: [#1] Modules linked in: binfmt_misc sit nfs lockd nfs_acl sunrpc ipt_ECN iptable_mangle w83627ehf i2c_isa i2c_viapro i2c_core via_agp agpgart rtc CPU:0 EIP:0060:[]Not tainted VLI EFLAGS: 00010016 (2.6.20.3-cks1 #4) EIP is at 0x0 eax: e94a5e6c ebx: e94a5e6c ecx: edx: 0001 esi: edi: e94a5e84 ebp: e94a5e6c esp: e94a5e4c ds: 007b es: 007b ss: 0068 Process grep (pid: 9156, ti=e94a4000 task=f4569a90 task.ti=e94a4000) Stack: c0116429 0001 0001 ec7da800 0286 e94a5e84 c0117802 ec7da800 ec7da800 ec7da85c c015c622 e9d02b40 e94a5f60 f77b6ac0 0400 c0313e6c 1000 Call Trace: [c0116429] __wake_up_common+0x39/0x70 [c0117802] __wake_up+0x22/0x30 [c015c622] pipe_write+0x222/0x4b0 [c0156887] do_sync_write+0xc7/0x110 [c012b5c0] autoremove_wake_function+0x0/0x50 [c0157156] vfs_write+0xa6/0x160 [c01567c0] do_sync_write+0x0/0x110 [c0157781] sys_write+0x41/0x70 [c0102ed6] sysenter_past_esp+0x5f/0x85 [c0300033] ipv6_flowlabel_opt+0x193/0x730 === Code: Bad EIP value. EIP: [] 0x0 SS:ESP 0068:e94a5e4c 3BUG: sleeping function called from invalid context at kernel/rwsem.c:20 in_atomic():0, irqs_disabled():1 [c012e432] down_read+0x12/0x20 [c01367b8] acct_collect+0x38/0x120 [c011cc7a] do_exit+0xda/0x750 [c011ab1b] printk+0x1b/0x20 [c0104380] do_trap+0x0/0x100 [c011533a] do_page_fault+0x2da/0x630 [c0115060] do_page_fault+0x0/0x630 [c030e5a4] error_code+0x74/0x7c [c0116429] __wake_up_common+0x39/0x70 [c0117802] __wake_up+0x22/0x30 [c015c622] pipe_write+0x222/0x4b0 [c0156887] do_sync_write+0xc7/0x110 [c012b5c0] autoremove_wake_function+0x0/0x50 [c0157156] vfs_write+0xa6/0x160 [c01567c0] do_sync_write+0x0/0x110 [c0157781] sys_write+0x41/0x70 [c0102ed6] sysenter_past_esp+0x5f/0x85 [c0300033] ipv6_flowlabel_opt+0x193/0x730 === BUG: unable to handle kernel NULL pointer dereference at virtual address printing eip: *pde = Oops: [#2] Modules linked in: binfmt_misc sit nfs lockd nfs_acl sunrpc ipt_ECN iptable_mangle w83627ehf i2c_isa i2c_viapro i2c_core via_agp agpgart rtc CPU:0 EIP:0060:[]Not tainted VLI EFLAGS: 00010087 (2.6.20.3-cks1 #4) EIP is at 0x0 eax: e94a5e6c ebx: e94a5e6c ecx: edx: 0001 esi: edi: e94a5e84 ebp: e94a5ccc esp: e94a5cac ds: 007b es: 007b ss: 0068 Process grep (pid: 9156, ti=e94a4000 task=f4569a90 task.ti=e94a4000) Stack: c0116429 0001 0001 ec7da800 0286 ec7da800 e94a5ce4 c0117802 0001 e9d02ad4 c015c069 e9d02b40 0008 e9d02ad4 f77b6ac0 c0157b20 Call Trace: [c0116429] __wake_up_common+0x39/0x70 [c0117802] __wake_up+0x22/0x30 [c015c069] pipe_release+0x59/0xb0 [c0157b20] __fput+0xb0/0x180 [c0154ff7] filp_close+0x47/0x80 [c011bcbc] put_files_struct+0x9c/0xb0 [c011ccb5] do_exit+0x115/0x750 [c011ab1b] printk+0x1b/0x20 [c0104380] do_trap+0x0/0x100 [c011533a] do_page_fault+0x2da/0x630 [c0115060] do_page_fault+0x0/0x630 [c030e5a4] error_code+0x74/0x7c [c0116429] __wake_up_common+0x39/0x70 [c0117802] __wake_up+0x22/0x30 [c015c622] pipe_write+0x222/0x4b0 [c0156887] do_sync_write+0xc7/0x110 [c012b5c0] autoremove_wake_function+0x0/0x50 [c0157156] vfs_write+0xa6/0x160 [c01567c0] do_sync_write+0x0/0x110 [c0157781] sys_write+0x41/0x70 [c0102ed6] sysenter_past_esp+0x5f/0x85 [c0300033] ipv6_flowlabel_opt+0x193/0x730 === Code: Bad EIP value. EIP: [] 0x0 SS:ESP 0068:e94a5cac 1Fixing recursive fault but reboot is needed! - 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/
2.6.20.3-cks1 ext3 oops
Hi, I was doing large FTP transfers to an ext3 partition on a 2.6.20.3-cks1 machine and it spat on me. Here it is, hope you guys can read important stuff from it: BUG: at fs/buffer.c:1639 __block_write_full_page() [] __block_write_full_page+0x320/0x330 [] ext3_get_block+0x0/0x100 [] block_write_full_page+0xf6/0x100 [] ext3_get_block+0x0/0x100 [] ext3_journalled_writepage+0x14d/0x160 [] generic_writepages+0x1ee/0x320 [] ext3_journalled_writepage+0x0/0x160 [] do_writepages+0x49/0x50 [] __writeback_single_inode+0x8a/0x370 [] __writeback_single_inode+0xbe/0x370 [] schedule_timeout+0x52/0xd0 [] sync_sb_inodes+0x161/0x210 [] writeback_inodes+0x72/0x90 [] background_writeout+0x7c/0xa0 [] pdflush+0x0/0x180 [] pdflush+0xd5/0x180 [] background_writeout+0x0/0xa0 [] kthread+0xa9/0xe0 [] kthread+0x0/0xe0 [] kernel_thread_helper+0x7/0x10 === c0175556 Modules linked in: binfmt_misc sit nfs lockd nfs_acl sunrpc ipt_ECN iptable_mangle w83627ehf i2c_isa i2c_viapro i2c_core via_agp agpgart rtc <0>Assertion failure in journal_start() at fs/jbd/transaction.c:273: "handle->h_transaction->t_journal == journal" Modules linked in: binfmt_misc sit nfs lockd nfs_acl sunrpc ipt_ECN iptable_mangle w83627ehf i2c_isa i2c_viapro i2c_core via_agp agpgart rtc <1>Fixing recursive fault but reboot is needed! swapper: page allocation failure. order:0, mode:0x20 [] __alloc_pages+0x2f9/0x310 [] cache_alloc_refill+0x27d/0x490 [] __kmalloc+0x85/0x90 [] __alloc_skb+0x55/0x110 [] boomerang_rx+0x345/0x450 [] boomerang_interrupt+0x156/0x410 [] handle_IRQ_event+0x25/0x60 [] handle_fasteoi_irq+0x44/0x90 I don't think that the -ck patch i am using skews it in any way, it seems to be ext3/swap/memory related. I am not on the list, if you need anything from me, just use my email or cc. Best regards, Maciej Soltysiak - 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/
2.6.20.3-cks1 ext3 oops
Hi, I was doing large FTP transfers to an ext3 partition on a 2.6.20.3-cks1 machine and it spat on me. Here it is, hope you guys can read important stuff from it: BUG: at fs/buffer.c:1639 __block_write_full_page() [c01757b0] __block_write_full_page+0x320/0x330 [c01b9450] ext3_get_block+0x0/0x100 [c0175ab6] block_write_full_page+0xf6/0x100 [c01b9450] ext3_get_block+0x0/0x100 [c01bb15d] ext3_journalled_writepage+0x14d/0x160 [c013f33e] generic_writepages+0x1ee/0x320 [c01bb010] ext3_journalled_writepage+0x0/0x160 [c013f4b9] do_writepages+0x49/0x50 [c01704fa] __writeback_single_inode+0x8a/0x370 [c017052e] __writeback_single_inode+0xbe/0x370 [c030d642] schedule_timeout+0x52/0xd0 [c0170b41] sync_sb_inodes+0x161/0x210 [c0170f52] writeback_inodes+0x72/0x90 [c013f83c] background_writeout+0x7c/0xa0 [c013fcd0] pdflush+0x0/0x180 [c013fda5] pdflush+0xd5/0x180 [c013f7c0] background_writeout+0x0/0xa0 [c012b329] kthread+0xa9/0xe0 [c012b280] kthread+0x0/0xe0 [c0103a97] kernel_thread_helper+0x7/0x10 === c0175556 Modules linked in: binfmt_misc sit nfs lockd nfs_acl sunrpc ipt_ECN iptable_mangle w83627ehf i2c_isa i2c_viapro i2c_core via_agp agpgart rtc 0Assertion failure in journal_start() at fs/jbd/transaction.c:273: handle-h_transaction-t_journal == journal Modules linked in: binfmt_misc sit nfs lockd nfs_acl sunrpc ipt_ECN iptable_mangle w83627ehf i2c_isa i2c_viapro i2c_core via_agp agpgart rtc 1Fixing recursive fault but reboot is needed! swapper: page allocation failure. order:0, mode:0x20 [c013e8f9] __alloc_pages+0x2f9/0x310 [c0153bcd] cache_alloc_refill+0x27d/0x490 [c0153e65] __kmalloc+0x85/0x90 [c0286645] __alloc_skb+0x55/0x110 [c024a625] boomerang_rx+0x345/0x450 [c024b246] boomerang_interrupt+0x156/0x410 [c0136dd5] handle_IRQ_event+0x25/0x60 [c0137de4] handle_fasteoi_irq+0x44/0x90 I don't think that the -ck patch i am using skews it in any way, it seems to be ext3/swap/memory related. I am not on the list, if you need anything from me, just use my email or cc. Best regards, Maciej Soltysiak - 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/
agp_backend_initialize() failed on ServerWorks CNB20LE
Hello, On a server with ServerWorks CNB20LE and CONFIG_AGP_SWORKS enabled I get these upon bootup: Linux agpgart interface v0.101 (c) Dave Jones agpgart: unable to determine aperture size. agpgart: agp_backend_initialize() failed. agpgart-serverworks: probe of :00:00.0 failed with error -22 agpgart: unable to determine aperture size. agpgart: agp_backend_initialize() failed. agpgart-serverworks: probe of :00:00.1 failed with error -22 lspci -vvv shows (i skipped the IDE, ISA and NIC lines): 00:00.0 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
agp_backend_initialize() failed on ServerWorks CNB20LE
Hello, On a server with ServerWorks CNB20LE and CONFIG_AGP_SWORKS enabled I get these upon bootup: Linux agpgart interface v0.101 (c) Dave Jones agpgart: unable to determine aperture size. agpgart: agp_backend_initialize() failed. agpgart-serverworks: probe of :00:00.0 failed with error -22 agpgart: unable to determine aperture size. agpgart: agp_backend_initialize() failed. agpgart-serverworks: probe of :00:00.1 failed with error -22 lspci -vvv shows (i skipped the IDE, ISA and NIC lines): 00:00.0 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 64, cache line size 08 00:00.1 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64, cache line size 08 00:02.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC 215IIC [Mach64 GT IIC] (rev 7a) (prog-if 00 [VGA]) Subsystem: Intel Corporation: Unknown device 4756 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 66 (2000ns min), cache line size 08 Interrupt: pin A routed to IRQ 19 Region 0: Memory at fc00 (32-bit, prefetchable) [size=16M] Region 1: I/O ports at 5000 [size=256] Region 2: Memory at fb10 (32-bit, non-prefetchable) [size=4K] Expansion ROM at 5000 [disabled] [size=128K] Capabilities: [5c] Power Management version 1 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- The only problems I have that *may* be related to these messages is the fact that when I boot into X and try to switch to a text console, the screen gets garbled and freezes, the server works fine besides the screen throwing trash at me. It is not a big issue, but maybe anyone would like to know. Or enlighten me if it Regards, Maciej - 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: [OT] [KORG] BitTorrents?
Hello Sean, Monday, August 29, 2005, 6:13:21 AM, you wrote: > Is there any reason for not putting the kernel(and it's updates) up on a > tracker on kernel.org? I looked through the list and noted that there > has not been any discussion in regards to this topic. Maybe because HTTP and FTP is usually easier to get, the downloads are faster if you have a fast mirror and ibiblio.org is already posting the kernels on BitTorrent, eg. for 2.6 you have these: http://torrent.ibiblio.org/browse.php?docid=42 Also checkout other things they post, including video lectures: http://torrent.ibiblio.org > I personally don't have enough up-stream bandwidth(384K) to support a > tracker, but I have enough to contribute to a torrent... No problem, ibiblio.org has :-) -- Maciej - 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: [OT] [KORG] BitTorrents?
Hello Sean, Monday, August 29, 2005, 6:13:21 AM, you wrote: Is there any reason for not putting the kernel(and it's updates) up on a tracker on kernel.org? I looked through the list and noted that there has not been any discussion in regards to this topic. Maybe because HTTP and FTP is usually easier to get, the downloads are faster if you have a fast mirror and ibiblio.org is already posting the kernels on BitTorrent, eg. for 2.6 you have these: http://torrent.ibiblio.org/browse.php?docid=42 Also checkout other things they post, including video lectures: http://torrent.ibiblio.org I personally don't have enough up-stream bandwidth(384K) to support a tracker, but I have enough to contribute to a torrent... No problem, ibiblio.org has :-) -- Maciej - 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: 3com 3c59x stopped working with 2.6.13-rc[56]
Hello > I assume it worked OK in 2.6.12. Yes, sorry, forgot to mention that. >> 18:27:47: eth1: Setting full-duplex based on MII #24 link partner capability >> of 05e1. >> 18:32:02: NETDEV WATCHDOG: eth1: transmit timed out >> 18:32:02: eth1: transmit timed out, tx_status 00 status e601. >> 18:32:02: diagnostics: net 0cfa media 8880 dma 003a fifo 8800 >> 18:32:02: eth1: Interrupt posted but not delivered -- IRQ blocked by another >> device? > gargh, I have acpi feelings. Could you please It seems you had a good hunch. > a) Compare /proc/interrupts for 2.6.12 and 2.6.13-rc6 /proc/interrputs for 2.6.12: CPU0 0: 76133896 XT-PIC timer 1: 1170 XT-PIC i8042 2: 0 XT-PIC cascade 9: 0 XT-PIC acpi 11:2483056 XT-PIC eth1 14: 603767 XT-PIC ide0 15: 13 XT-PIC ide1 NMI: 0 ERR: 0 /proc/interrputs for 2.6.13: CPU0 0: 851172 XT-PIC timer 1:802 XT-PIC i8042 2: 0 XT-PIC cascade 5: 0 XT-PIC eth1 14: 30180 XT-PIC ide0 15: 13 XT-PIC ide1 NMI: 0 ERR: 0 What is missing is acpi on irq9 > b) Generate the boot-time dmesg output for 2.6.12 and 2.6.13-rc6 >(dmesg -s 100 > foo), then do > diff -u dmesg-2.6.12 dmesg-2.6.13-rc6 > foo >and send foo? Here is foo: --- dmesg-2.6.122005-08-23 12:53:43.0 +0200 +++ dmesg-2.6.132005-08-23 14:26:54.0 +0200 @@ -1,4 +1,4 @@ -Linux version 2.6.12 ([EMAIL PROTECTED]) (gcc version 4.0.1 (Debian 4.0.1-2)) #1 Mon Aug 22 14:49:40 CEST 2005 +Linux version 2.6.13-rc6-git13 ([EMAIL PROTECTED]) (gcc version 4.0.1 (Debian 4.0.1-2)) #2 Mon Aug 22 15:22:10 CEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 000a (usable) BIOS-e820: 000f - 0010 (reserved) @@ -13,25 +13,20 @@ Normal zone: 126956 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 DMI 2.3 present. -ACPI: RSDP (v000 ASUS ) @ 0x000f6c20 -ACPI: RSDT (v001 ASUS A7V266-C 0x30303031 MSFT 0x31313031) @ 0x1ffec000 -ACPI: FADT (v001 ASUS A7V266-C 0x30303031 MSFT 0x31313031) @ 0x1ffec080 -ACPI: BOOT (v001 ASUS A7V266-C 0x30303031 MSFT 0x31313031) @ 0x1ffec040 -ACPI: DSDT (v001 ASUS A7V266-C 0x1000 MSFT 0x010b) @ 0x Allocating PCI resources starting at 2000 (gap: 2000:dfff) Built 1 zonelists -Kernel command line: BOOT_IMAGE=Linux.old ro root=301 lapic pci=usepirqmask +Kernel command line: auto BOOT_IMAGE=Linux ro root=301 lapic pci=usepirqmask Initializing CPU#0 -CPU 0 irqstacks, hard=c0442000 soft=c0441000 +CPU 0 irqstacks, hard=c041b000 soft=c041a000 PID hash table entries: 2048 (order: 11, 32768 bytes) Detected 1210.984 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) -Memory: 515260k/524208k available (2114k kernel code, 8412k reserved, 801k data, 392k init, 0k highmem) +Memory: 515424k/524208k available (2010k kernel code, 8252k reserved, 753k data, 388k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. -Calibrating delay loop... 2383.87 BogoMIPS (lpj=1191936) +Calibrating delay using timer specific routine.. 2424.59 BogoMIPS (lpj=1212295) Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0383f9ff c1cbf9ff CPU: After vendor identify, caps: 0383f9ff c1cbf9ff @@ -40,65 +35,49 @@ CPU: After all inits, caps: 0383f9ff c1cbf9ff 0020 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. +mtrr: v2.0 (20020519) CPU: AMD Duron(TM)Processor stepping 01 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. -ACPI: setting ELCR to 0200 (from 0400) NET: Registered protocol family 16 PCI: PCI BIOS revision 2.10 entry at 0xf0f00, last bus=1 PCI: Using configuration type 1 -mtrr: v2.0 (20020519) -ACPI: Subsystem revision 20050309 -ACPI: Interpreter enabled -ACPI: Using PIC for interrupt routing -ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. -ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. -ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. -ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) -ACPI: PCI Root Bridge [PCI0] (:00) +PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) Boot video device is :01:00.0 -ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Re: 3com 3c59x stopped working with 2.6.13-rc[56]
Hello I assume it worked OK in 2.6.12. Yes, sorry, forgot to mention that. 18:27:47: eth1: Setting full-duplex based on MII #24 link partner capability of 05e1. 18:32:02: NETDEV WATCHDOG: eth1: transmit timed out 18:32:02: eth1: transmit timed out, tx_status 00 status e601. 18:32:02: diagnostics: net 0cfa media 8880 dma 003a fifo 8800 18:32:02: eth1: Interrupt posted but not delivered -- IRQ blocked by another device? gargh, I have acpi feelings. Could you please It seems you had a good hunch. a) Compare /proc/interrupts for 2.6.12 and 2.6.13-rc6 /proc/interrputs for 2.6.12: CPU0 0: 76133896 XT-PIC timer 1: 1170 XT-PIC i8042 2: 0 XT-PIC cascade 9: 0 XT-PIC acpi 11:2483056 XT-PIC eth1 14: 603767 XT-PIC ide0 15: 13 XT-PIC ide1 NMI: 0 ERR: 0 /proc/interrputs for 2.6.13: CPU0 0: 851172 XT-PIC timer 1:802 XT-PIC i8042 2: 0 XT-PIC cascade 5: 0 XT-PIC eth1 14: 30180 XT-PIC ide0 15: 13 XT-PIC ide1 NMI: 0 ERR: 0 What is missing is acpi on irq9 b) Generate the boot-time dmesg output for 2.6.12 and 2.6.13-rc6 (dmesg -s 100 foo), then do diff -u dmesg-2.6.12 dmesg-2.6.13-rc6 foo and send foo? Here is foo: --- dmesg-2.6.122005-08-23 12:53:43.0 +0200 +++ dmesg-2.6.132005-08-23 14:26:54.0 +0200 @@ -1,4 +1,4 @@ -Linux version 2.6.12 ([EMAIL PROTECTED]) (gcc version 4.0.1 (Debian 4.0.1-2)) #1 Mon Aug 22 14:49:40 CEST 2005 +Linux version 2.6.13-rc6-git13 ([EMAIL PROTECTED]) (gcc version 4.0.1 (Debian 4.0.1-2)) #2 Mon Aug 22 15:22:10 CEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 000a (usable) BIOS-e820: 000f - 0010 (reserved) @@ -13,25 +13,20 @@ Normal zone: 126956 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 DMI 2.3 present. -ACPI: RSDP (v000 ASUS ) @ 0x000f6c20 -ACPI: RSDT (v001 ASUS A7V266-C 0x30303031 MSFT 0x31313031) @ 0x1ffec000 -ACPI: FADT (v001 ASUS A7V266-C 0x30303031 MSFT 0x31313031) @ 0x1ffec080 -ACPI: BOOT (v001 ASUS A7V266-C 0x30303031 MSFT 0x31313031) @ 0x1ffec040 -ACPI: DSDT (v001 ASUS A7V266-C 0x1000 MSFT 0x010b) @ 0x Allocating PCI resources starting at 2000 (gap: 2000:dfff) Built 1 zonelists -Kernel command line: BOOT_IMAGE=Linux.old ro root=301 lapic pci=usepirqmask +Kernel command line: auto BOOT_IMAGE=Linux ro root=301 lapic pci=usepirqmask Initializing CPU#0 -CPU 0 irqstacks, hard=c0442000 soft=c0441000 +CPU 0 irqstacks, hard=c041b000 soft=c041a000 PID hash table entries: 2048 (order: 11, 32768 bytes) Detected 1210.984 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) -Memory: 515260k/524208k available (2114k kernel code, 8412k reserved, 801k data, 392k init, 0k highmem) +Memory: 515424k/524208k available (2010k kernel code, 8252k reserved, 753k data, 388k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. -Calibrating delay loop... 2383.87 BogoMIPS (lpj=1191936) +Calibrating delay using timer specific routine.. 2424.59 BogoMIPS (lpj=1212295) Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0383f9ff c1cbf9ff CPU: After vendor identify, caps: 0383f9ff c1cbf9ff @@ -40,65 +35,49 @@ CPU: After all inits, caps: 0383f9ff c1cbf9ff 0020 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. +mtrr: v2.0 (20020519) CPU: AMD Duron(TM)Processor stepping 01 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. -ACPI: setting ELCR to 0200 (from 0400) NET: Registered protocol family 16 PCI: PCI BIOS revision 2.10 entry at 0xf0f00, last bus=1 PCI: Using configuration type 1 -mtrr: v2.0 (20020519) -ACPI: Subsystem revision 20050309 -ACPI: Interpreter enabled -ACPI: Using PIC for interrupt routing -ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. -ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. -ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. -ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) -ACPI: PCI Root Bridge [PCI0] (:00) +PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) Boot video device is :01:00.0 -ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] -ACPI: PCI Interrupt
Re: sched_yield() makes OpenLDAP slow
Hello Con, Thursday, August 18, 2005, 2:47:25 AM, you wrote: > sched_yield behaviour changed in 2.5 series more than 3 years ago and > applications that use this as a locking primitive should be updated. I remember open office had a problem with excessive use of sched_yield() during 2.5. I guess they changed it but I have not checked. Does anyone know ? Back then oo was having serious latency problems on 2.5 Regards, Maciej - 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: sched_yield() makes OpenLDAP slow
Hello Con, Thursday, August 18, 2005, 2:47:25 AM, you wrote: sched_yield behaviour changed in 2.5 series more than 3 years ago and applications that use this as a locking primitive should be updated. I remember open office had a problem with excessive use of sched_yield() during 2.5. I guess they changed it but I have not checked. Does anyone know ? Back then oo was having serious latency problems on 2.5 Regards, Maciej - 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: function Name
Hello raja,
Friday, July 8, 2005, 8:12:21 AM, you wrote:
>I am writing a function that takes the return value of the another
> function and gives the status of the function.
> if
>error("functionName",arguments)
> here the function with Name "functionName " is to be executed with the
> corresponding argunents.But by knowing the function name how can i get
> the address if that function and how can i execute the function with the
> arguments.
A good place to ask C questions is IRC channel #c on IRCNET.
Lookup an IRCNET server in your vicinity and try there.
Really good and helpful people are hanging around.
--
Maciej
-
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: function Name
Hello raja, Friday, July 8, 2005, 8:12:21 AM, you wrote: I am writing a function that takes the return value of the another function and gives the status of the function. if error(functionName,arguments) here the function with Name functionName is to be executed with the corresponding argunents.But by knowing the function name how can i get the address if that function and how can i execute the function with the arguments. A good place to ask C questions is IRC channel #c on IRCNET. Lookup an IRCNET server in your vicinity and try there. Really good and helpful people are hanging around. -- Maciej - 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 incremental patch size [2.6.12-rc2 to 2.6.12-rc3]
Hi, These are the sizes of rc2 and rc3 patches # ls -la patch-2.6.12* -rw-r--r-- 1 root src 18011382 Apr 4 18:50 patch-2.6.12-rc2 -rw-r--r-- 1 root src 19979854 Apr 21 02:29 patch-2.6.12-rc3 Let us make an incremental patch from rc2 to rc3 # interdiff patch-2.6.12-rc2 patch-2.6.12-rc3 >x Let us see how big it is. # ls -ld x -rw-r--r-- 1 root src 37421924 Apr 21 12:28 x How come interdiff from rc2 (18MB) to rc3 (20MB) gave me 37MB worth of patch-code ? I would expect something about 2MB but 40MB ? The patching with the incremental patch took very long compared to other rc2-rc3-type patches, that is how I noticed it. Regards, Maciej - 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 incremental patch size [2.6.12-rc2 to 2.6.12-rc3]
Hi, These are the sizes of rc2 and rc3 patches # ls -la patch-2.6.12* -rw-r--r-- 1 root src 18011382 Apr 4 18:50 patch-2.6.12-rc2 -rw-r--r-- 1 root src 19979854 Apr 21 02:29 patch-2.6.12-rc3 Let us make an incremental patch from rc2 to rc3 # interdiff patch-2.6.12-rc2 patch-2.6.12-rc3 x Let us see how big it is. # ls -ld x -rw-r--r-- 1 root src 37421924 Apr 21 12:28 x How come interdiff from rc2 (18MB) to rc3 (20MB) gave me 37MB worth of patch-code ? I would expect something about 2MB but 40MB ? The patching with the incremental patch took very long compared to other rc2-rc3-type patches, that is how I noticed it. Regards, Maciej - 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/
where is current kernel ?
Hi, Is there currently a kernel tree that Linus is working ? I mean, now that we have 2.6.12-rc2 not being developed with BK, is that code getting fixes and other patches as we speak or the development will continue in a while someplace else ? Regards, Maciej - 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/
where is current kernel ?
Hi, Is there currently a kernel tree that Linus is working ? I mean, now that we have 2.6.12-rc2 not being developed with BK, is that code getting fixes and other patches as we speak or the development will continue in a while someplace else ? Regards, Maciej - 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/
[OT] Re[2]: bkbits.net is down
Hi Geert, you wrote on 13 Apr 2005: > I don't think so: both `c' and `t' are (different) ASCII-transcripts of the > actual non-ASCII character that should have been there. Yes, UTF-8 to US-ASCII > is lossy and imprecise ;-) There is now UTF there :-) Both Marcin and Martin are the same name, the difference is that Marcin is a Polish version - this is the correct spelling as far as Polish is concerned. It is like John and Johann I guess; or Paul and Pavel (Pavel is Czech here) There are issues with names sometimes. eg. I can say that I am Maciej or I can say I am Maciek. And it is perfectly fine. No spelling mistakes there. Regards, Maciej - 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/
[OT] Re[2]: bkbits.net is down
Hi Geert, you wrote on 13 Apr 2005: I don't think so: both `c' and `t' are (different) ASCII-transcripts of the actual non-ASCII character that should have been there. Yes, UTF-8 to US-ASCII is lossy and imprecise ;-) There is now UTF there :-) Both Marcin and Martin are the same name, the difference is that Marcin is a Polish version - this is the correct spelling as far as Polish is concerned. It is like John and Johann I guess; or Paul and Pavel (Pavel is Czech here) There are issues with names sometimes. eg. I can say that I am Maciej or I can say I am Maciek. And it is perfectly fine. No spelling mistakes there. Regards, Maciej - 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/
[2.6.12-rc1-mm4] swapped memset arguments
Hi, out of boredom I grepped 2.6.12-rc1-mm4 for swapped memset arguments. I found one: # grep -nr "memset.*\,\(\ \|\)0\(\ \|\));" * net/ieee80211/ieee80211_tx.c:226: memset(txb, sizeof(struct ieee80211_txb), 0); I found none in Linus' bk. Regards, Maciej - 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/
[2.6.12-rc1-mm4] swapped memset arguments
Hi, out of boredom I grepped 2.6.12-rc1-mm4 for swapped memset arguments. I found one: # grep -nr memset.*\,\(\ \|\)0\(\ \|\)); * net/ieee80211/ieee80211_tx.c:226: memset(txb, sizeof(struct ieee80211_txb), 0); I found none in Linus' bk. Regards, Maciej - 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[2]: eepro100 or e100
Hi, >> Are both drivers supported by their authors, etc. > eepro100 is unmaintained and going away. Well, good to know then, I am switching right now. Thanks. > Jeff Maciej - 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/
[2.6 current BK] Unnecesary code gets compiled in during build?
Hi, I am compiling 2.6.11-rc4-cset And I see during the compilation: LD drivers/media/common/built-in.o LD drivers/media/dvb/b2c2/built-in.o LD drivers/media/dvb/bt8xx/built-in.o LD drivers/media/dvb/cinergyT2/built-in.o LD drivers/media/dvb/dibusb/built-in.o LD drivers/media/dvb/dvb-core/built-in.o LD drivers/media/dvb/frontends/built-in.o LD drivers/media/dvb/ttpci/built-in.o LD drivers/media/dvb/ttusb-budget/built-in.o LD drivers/media/dvb/ttusb-dec/built-in.o LD drivers/media/dvb/built-in.o LD drivers/media/radio/built-in.o LD drivers/media/video/built-in.o Although I know I have not added dvb, nor radio. How come this shows up? I am attaching my .config, it does not have DVB set. Regards, Maciej # # Automatically generated make config: don't edit # Linux kernel version: 2.6.11-rc4 # Fri Feb 18 20:15:14 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_LOCK_KERNEL=y # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=15 # CONFIG_HOTPLUG is not set # CONFIG_KOBJECT_UEVENT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_EMBEDDED=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_EXTRA_PASS=y CONFIG_FUTEX=y CONFIG_EPOLL=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set # # Loadable module support # # CONFIG_MODULES is not set # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set CONFIG_MPENTIUMIII=y # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y # CONFIG_HPET_TIMER is not set CONFIG_SMP=y CONFIG_NR_CPUS=8 # CONFIG_SCHED_SMT is not set # CONFIG_PREEMPT is not set CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_TSC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_NONFATAL=y # CONFIG_X86_MCE_P4THERMAL is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set CONFIG_MICROCODE=y CONFIG_X86_MSR=y CONFIG_X86_CPUID=y # # Firmware Drivers # CONFIG_EDD=y # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_HIGHMEM=y CONFIG_HIGHPTE=y # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y CONFIG_IRQBALANCE=y CONFIG_HAVE_DEC_LOCK=y # CONFIG_REGPARM is not set # # Power management options (ACPI, APM) # # CONFIG_PM is not set # # ACPI (Advanced Configuration and Power Interface) Support # # CONFIG_ACPI is not set CONFIG_ACPI_BOOT=y # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y # CONFIG_PCIEPORTBUS is not set CONFIG_PCI_MSI=y CONFIG_PCI_LEGACY_PROC=y CONFIG_PCI_NAMES=y # CONFIG_ISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # # PCCARD (PCMCIA/CardBus) support # # CONFIG_PCCARD is not set # # PC-card bridges # # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_MISC=y # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_FW_LOADER is not set # CONFIG_DEBUG_DRIVER is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play support # # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set #
eepro100 or e100
Hello, Can anyone shed some light upon the state of development of these drivers? I mean: the set of supported both NIC and kernel features. Are both drivers supported by their authors, etc. Looking for answers that would lead to a conclusion which to use. Regards, Maciej - 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/
eepro100 or e100
Hello, Can anyone shed some light upon the state of development of these drivers? I mean: the set of supported both NIC and kernel features. Are both drivers supported by their authors, etc. Looking for answers that would lead to a conclusion which to use. Regards, Maciej - 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/
[2.6 current BK] Unnecesary code gets compiled in during build?
Hi, I am compiling 2.6.11-rc4-cset And I see during the compilation: LD drivers/media/common/built-in.o LD drivers/media/dvb/b2c2/built-in.o LD drivers/media/dvb/bt8xx/built-in.o LD drivers/media/dvb/cinergyT2/built-in.o LD drivers/media/dvb/dibusb/built-in.o LD drivers/media/dvb/dvb-core/built-in.o LD drivers/media/dvb/frontends/built-in.o LD drivers/media/dvb/ttpci/built-in.o LD drivers/media/dvb/ttusb-budget/built-in.o LD drivers/media/dvb/ttusb-dec/built-in.o LD drivers/media/dvb/built-in.o LD drivers/media/radio/built-in.o LD drivers/media/video/built-in.o Although I know I have not added dvb, nor radio. How come this shows up? I am attaching my .config, it does not have DVB set. Regards, Maciej # # Automatically generated make config: don't edit # Linux kernel version: 2.6.11-rc4 # Fri Feb 18 20:15:14 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_LOCK_KERNEL=y # # General setup # CONFIG_LOCALVERSION= CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=15 # CONFIG_HOTPLUG is not set # CONFIG_KOBJECT_UEVENT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_EMBEDDED=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_EXTRA_PASS=y CONFIG_FUTEX=y CONFIG_EPOLL=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set # # Loadable module support # # CONFIG_MODULES is not set # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set CONFIG_MPENTIUMIII=y # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y # CONFIG_HPET_TIMER is not set CONFIG_SMP=y CONFIG_NR_CPUS=8 # CONFIG_SCHED_SMT is not set # CONFIG_PREEMPT is not set CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_TSC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_NONFATAL=y # CONFIG_X86_MCE_P4THERMAL is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set CONFIG_MICROCODE=y CONFIG_X86_MSR=y CONFIG_X86_CPUID=y # # Firmware Drivers # CONFIG_EDD=y # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_HIGHMEM=y CONFIG_HIGHPTE=y # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y CONFIG_IRQBALANCE=y CONFIG_HAVE_DEC_LOCK=y # CONFIG_REGPARM is not set # # Power management options (ACPI, APM) # # CONFIG_PM is not set # # ACPI (Advanced Configuration and Power Interface) Support # # CONFIG_ACPI is not set CONFIG_ACPI_BOOT=y # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y # CONFIG_PCIEPORTBUS is not set CONFIG_PCI_MSI=y CONFIG_PCI_LEGACY_PROC=y CONFIG_PCI_NAMES=y # CONFIG_ISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # # PCCARD (PCMCIA/CardBus) support # # CONFIG_PCCARD is not set # # PC-card bridges # # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_MISC=y # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_FW_LOADER is not set # CONFIG_DEBUG_DRIVER is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play support # # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set #
Re[2]: eepro100 or e100
Hi, Are both drivers supported by their authors, etc. eepro100 is unmaintained and going away. Well, good to know then, I am switching right now. Thanks. Jeff Maciej - 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: possible leak in kernel 2.6.10-ac12
Hello Pedro, Thursday, February 17, 2005, 12:28:15 AM, you wrote: > boot. It came to a point that it started swapping and the swap usage too > started to grow linearly. I had the same with swap being eaten especially by perl apps like qmail-scanner I think this helps: --- a/mm/vmscan.c 2004-12-24 13:36:18 -08:00 +++ b/mm/vmscan.c 2004-12-24 13:36:18 -08:00 @@ -675,6 +674,7 @@ } pgscanned++; } +zone->pages_scanned += pgscanned; zone->nr_active -= pgmoved; spin_unlock_irq(>lru_lock); This patchlet is at: http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv2.6%2Fpatch-2.6.10.bz2;z=4918 This changeset contains other patches, you need only one. 2.6.11 will have it fixed. Regards, Maciej Soltysiak - 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: possible leak in kernel 2.6.10-ac12
Hello Pedro, Thursday, February 17, 2005, 12:28:15 AM, you wrote: boot. It came to a point that it started swapping and the swap usage too started to grow linearly. I had the same with swap being eaten especially by perl apps like qmail-scanner I think this helps: --- a/mm/vmscan.c 2004-12-24 13:36:18 -08:00 +++ b/mm/vmscan.c 2004-12-24 13:36:18 -08:00 @@ -675,6 +674,7 @@ } pgscanned++; } +zone-pages_scanned += pgscanned; zone-nr_active -= pgmoved; spin_unlock_irq(zone-lru_lock); This patchlet is at: http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv2.6%2Fpatch-2.6.10.bz2;z=4918 This changeset contains other patches, you need only one. 2.6.11 will have it fixed. Regards, Maciej Soltysiak - 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[2]: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup
Hello Hans,
Monday, February 7, 2005, 9:19:47 PM, you wrote:
> Maciej Soltysiak wrote:
>>)
>>
>>Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady
>>SeekComplete Error }
>>Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError
>>BadCRC }
>>
>>
> this means bad hard drive, or at least a bad sector on it.
Well, I have reiser4 on this drive with noncritical data which is rather
not used anyway.
But please note that, the process generating the oops (as long as I am
seeing this right) is something called swapper:
scheduling while atomic: swapper/0x00010001/0
My swap partition is not on hdc, it is on hda, which does not report
bad crc and any other dma related errors, or any for that matter.
The same machine runs on 2.6.10-ac10 + reiser-2.6.10 patch well or
at least it does not trigger these oopses.
Only some still not tracked down problems with terrible swap eating :-(
But that's a different story.
Regards,
Maciej
-
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[2]: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup
Hello Hans,
Monday, February 7, 2005, 9:19:47 PM, you wrote:
Maciej Soltysiak wrote:
)
Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError
BadCRC }
this means bad hard drive, or at least a bad sector on it.
Well, I have reiser4 on this drive with noncritical data which is rather
not used anyway.
But please note that, the process generating the oops (as long as I am
seeing this right) is something called swapper:
scheduling while atomic: swapper/0x00010001/0
My swap partition is not on hdc, it is on hda, which does not report
bad crc and any other dma related errors, or any for that matter.
The same machine runs on 2.6.10-ac10 + reiser-2.6.10 patch well or
at least it does not trigger these oopses.
Only some still not tracked down problems with terrible swap eating :-(
But that's a different story.
Regards,
Maciej
-
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/
2.6.11-rc3-mm1 bad scheduling while atomic + lockup
Hello,
I just want to report a lockup on my 2.6.11-rc3-mm1 machine.
I was working on it via ssh and suddenly the machine stopped
responding. When, the next day I came up to the console
it was printing over and over this oops.
In the logs I could find the oops. I am posting it inline here
along with some logs before that (maybe it is related)
Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC
}
Feb 6 17:07:47 dns kernel: ide: failed opcode was: unknown
Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC
}
Feb 6 17:07:47 dns kernel: ide: failed opcode was: unknown
Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC
}
Feb 6 17:07:47 dns kernel: ide: failed opcode was: unknown
Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC
}
Feb 6 17:07:47 dns kernel: ide: failed opcode was: unknown
Feb 6 17:07:47 dns kernel: scheduling while atomic: swapper/0x00010001/0
Feb 6 17:07:47 dns kernel: [schedule+1379/1392] schedule+0x563/0x570
Feb 6 17:07:47 dns kernel: [__call_console_drivers+87/96]
__call_console_drivers+0x57/0x60
Feb 6 17:07:47 dns kernel: [__mod_timer+350/480] __mod_timer+0x15e/0x1e0
Feb 6 17:07:47 dns kernel: [schedule_timeout+99/192]
schedule_timeout+0x63/0xc0
Feb 6 17:07:47 dns kernel: [process_timeout+0/16] process_timeout+0x0/0x10
Feb 6 17:07:47 dns kernel: [ide_pin_hwgroup+97/208] ide_pin_hwgroup+0x61/0xd0
Feb 6 17:07:47 dns kernel: [ide_set_xfer_rate+28/96]
ide_set_xfer_rate+0x1c/0x60
Feb 6 17:07:47 dns kernel: [check_dma_crc+72/112] check_dma_crc+0x48/0x70
Feb 6 17:07:47 dns kernel: [do_reset1+99/544] do_reset1+0x63/0x220
Feb 6 17:07:47 dns kernel: [ide_do_reset+23/32] ide_do_reset+0x17/0x20
Feb 6 17:07:47 dns kernel: [ide_error+143/160] ide_error+0x8f/0xa0
Feb 6 17:07:47 dns kernel: [ide_dma_intr+91/192] ide_dma_intr+0x5b/0xc0
Feb 6 17:07:47 dns kernel: [ide_dma_intr+0/192] ide_dma_intr+0x0/0xc0
Feb 6 17:07:47 dns kernel: [ide_intr+246/432] ide_intr+0xf6/0x1b0
Feb 6 17:07:47 dns kernel: [handle_IRQ_event+48/112]
handle_IRQ_event+0x30/0x70
Feb 6 17:07:47 dns kernel: [__do_IRQ+230/352] __do_IRQ+0xe6/0x160
Feb 6 17:07:47 dns kernel: [__do_softirq+120/144] __do_softirq+0x78/0x90
Feb 6 17:07:47 dns kernel: [do_IRQ+35/64] do_IRQ+0x23/0x40
Feb 6 17:07:47 dns kernel: [common_interrupt+26/32] common_interrupt+0x1a/0x20
Feb 6 17:07:47 dns kernel: [default_idle+35/48] default_idle+0x23/0x30
Feb 6 17:07:47 dns kernel: [cpu_idle+72/96] cpu_idle+0x48/0x60
Feb 6 17:07:47 dns kernel: [start_kernel+338/368] start_kernel+0x152/0x170
Feb 6 17:07:47 dns kernel: [unknown_bootoption+0/432]
unknown_bootoption+0x0/0x1b0
Best Regards
Maciej
This is my .config:
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.11-rc3-mm1
# Fri Feb 4 19:41:09 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
# CONFIG_HOTPLUG is not set
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_EMBEDDED=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_BASE_FULL=y
CONFIG_BASE_SMALL=0
CONFIG_FUTEX=y
CONFIG_EPOLL=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON
2.6.11-rc3-mm1 bad scheduling while atomic + lockup
Hello,
I just want to report a lockup on my 2.6.11-rc3-mm1 machine.
I was working on it via ssh and suddenly the machine stopped
responding. When, the next day I came up to the console
it was printing over and over this oops.
In the logs I could find the oops. I am posting it inline here
along with some logs before that (maybe it is related)
Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC
}
Feb 6 17:07:47 dns kernel: ide: failed opcode was: unknown
Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC
}
Feb 6 17:07:47 dns kernel: ide: failed opcode was: unknown
Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC
}
Feb 6 17:07:47 dns kernel: ide: failed opcode was: unknown
Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC
}
Feb 6 17:07:47 dns kernel: ide: failed opcode was: unknown
Feb 6 17:07:47 dns kernel: scheduling while atomic: swapper/0x00010001/0
Feb 6 17:07:47 dns kernel: [schedule+1379/1392] schedule+0x563/0x570
Feb 6 17:07:47 dns kernel: [__call_console_drivers+87/96]
__call_console_drivers+0x57/0x60
Feb 6 17:07:47 dns kernel: [__mod_timer+350/480] __mod_timer+0x15e/0x1e0
Feb 6 17:07:47 dns kernel: [schedule_timeout+99/192]
schedule_timeout+0x63/0xc0
Feb 6 17:07:47 dns kernel: [process_timeout+0/16] process_timeout+0x0/0x10
Feb 6 17:07:47 dns kernel: [ide_pin_hwgroup+97/208] ide_pin_hwgroup+0x61/0xd0
Feb 6 17:07:47 dns kernel: [ide_set_xfer_rate+28/96]
ide_set_xfer_rate+0x1c/0x60
Feb 6 17:07:47 dns kernel: [check_dma_crc+72/112] check_dma_crc+0x48/0x70
Feb 6 17:07:47 dns kernel: [do_reset1+99/544] do_reset1+0x63/0x220
Feb 6 17:07:47 dns kernel: [ide_do_reset+23/32] ide_do_reset+0x17/0x20
Feb 6 17:07:47 dns kernel: [ide_error+143/160] ide_error+0x8f/0xa0
Feb 6 17:07:47 dns kernel: [ide_dma_intr+91/192] ide_dma_intr+0x5b/0xc0
Feb 6 17:07:47 dns kernel: [ide_dma_intr+0/192] ide_dma_intr+0x0/0xc0
Feb 6 17:07:47 dns kernel: [ide_intr+246/432] ide_intr+0xf6/0x1b0
Feb 6 17:07:47 dns kernel: [handle_IRQ_event+48/112]
handle_IRQ_event+0x30/0x70
Feb 6 17:07:47 dns kernel: [__do_IRQ+230/352] __do_IRQ+0xe6/0x160
Feb 6 17:07:47 dns kernel: [__do_softirq+120/144] __do_softirq+0x78/0x90
Feb 6 17:07:47 dns kernel: [do_IRQ+35/64] do_IRQ+0x23/0x40
Feb 6 17:07:47 dns kernel: [common_interrupt+26/32] common_interrupt+0x1a/0x20
Feb 6 17:07:47 dns kernel: [default_idle+35/48] default_idle+0x23/0x30
Feb 6 17:07:47 dns kernel: [cpu_idle+72/96] cpu_idle+0x48/0x60
Feb 6 17:07:47 dns kernel: [start_kernel+338/368] start_kernel+0x152/0x170
Feb 6 17:07:47 dns kernel: [unknown_bootoption+0/432]
unknown_bootoption+0x0/0x1b0
Best Regards
Maciej
This is my .config:
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.11-rc3-mm1
# Fri Feb 4 19:41:09 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
#
# General setup
#
CONFIG_LOCALVERSION=
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
# CONFIG_HOTPLUG is not set
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_EMBEDDED=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_BASE_FULL=y
CONFIG_BASE_SMALL=0
CONFIG_FUTEX=y
CONFIG_EPOLL=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is
How do I find out who uses swap?
Hi, I have a problem for some time with that the amount of swap being used constantly increases up to the moment where the swap is used in 100% and the machine deadlocks. How do I find out which proceses use swap and in what amount? I tried using top and sorting by SWAP, it shows this: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ SWAP COMMAND 3390 ncg 15 0 72504 3380 1720 S 0.0 0.7 0:00.76 67m ncgserver 24718 mysql 15 0 68056 7364 2232 S 0.0 1.4 2:30.70 59m mysqld 582 fallen16 0 30396 568 480 S 0.0 0.1 0:02.40 29m sc_serv 624 vpopmail 16 0 31124 1736 1436 S 0.0 0.3 0:01.99 28m spamd 31765 solt 16 0 29916 1020 616 S 0.0 0.2 0:02.25 28m sc_serv 3348 bind 22 0 31604 3872 1472 S 0.0 0.8 0:48.84 27m named 24021 root 16 0 32976 10m 7228 S 0.0 2.1 0:01.99 21m apache 13066 www-data 16 0 33104 10m 7276 S 0.0 2.2 0:00.62 21m apache 13103 www-data 16 0 33104 10m 7276 S 0.0 2.2 0:00.61 21m apache 13104 www-data 16 0 33104 10m 7276 S 0.0 2.2 0:00.60 21m apache 13099 www-data 16 0 33104 10m 7276 S 0.3 2.2 0:00.63 21m apache 13142 www-data 16 0 33104 10m 7276 S 0.0 2.2 0:00.61 21m apache 29898 www-data 16 0 33108 11m 7580 S 0.0 2.2 0:00.01 21m apache 13061 www-data 16 0 34492 12m 7700 S 0.0 2.5 0:00.56 21m apache 13057 www-data 15 0 35076 13m 7696 S 0.0 2.6 0:00.78 21m apache 23259 www-data 16 0 36344 14m 7784 S 0.0 2.9 0:01.15 21m apache 13062 www-data 15 0 37812 15m 7868 S 0.0 3.2 0:01.03 20m apache Or should I look at VIRT or MEM ? I am confused. Regards, Maciej - 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/
How do I find out who uses swap?
Hi, I have a problem for some time with that the amount of swap being used constantly increases up to the moment where the swap is used in 100% and the machine deadlocks. How do I find out which proceses use swap and in what amount? I tried using top and sorting by SWAP, it shows this: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ SWAP COMMAND 3390 ncg 15 0 72504 3380 1720 S 0.0 0.7 0:00.76 67m ncgserver 24718 mysql 15 0 68056 7364 2232 S 0.0 1.4 2:30.70 59m mysqld 582 fallen16 0 30396 568 480 S 0.0 0.1 0:02.40 29m sc_serv 624 vpopmail 16 0 31124 1736 1436 S 0.0 0.3 0:01.99 28m spamd 31765 solt 16 0 29916 1020 616 S 0.0 0.2 0:02.25 28m sc_serv 3348 bind 22 0 31604 3872 1472 S 0.0 0.8 0:48.84 27m named 24021 root 16 0 32976 10m 7228 S 0.0 2.1 0:01.99 21m apache 13066 www-data 16 0 33104 10m 7276 S 0.0 2.2 0:00.62 21m apache 13103 www-data 16 0 33104 10m 7276 S 0.0 2.2 0:00.61 21m apache 13104 www-data 16 0 33104 10m 7276 S 0.0 2.2 0:00.60 21m apache 13099 www-data 16 0 33104 10m 7276 S 0.3 2.2 0:00.63 21m apache 13142 www-data 16 0 33104 10m 7276 S 0.0 2.2 0:00.61 21m apache 29898 www-data 16 0 33108 11m 7580 S 0.0 2.2 0:00.01 21m apache 13061 www-data 16 0 34492 12m 7700 S 0.0 2.5 0:00.56 21m apache 13057 www-data 15 0 35076 13m 7696 S 0.0 2.6 0:00.78 21m apache 23259 www-data 16 0 36344 14m 7784 S 0.0 2.9 0:01.15 21m apache 13062 www-data 15 0 37812 15m 7868 S 0.0 3.2 0:01.03 20m apache Or should I look at VIRT or MEM ? I am confused. Regards, Maciej - 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/
Support for Large Block Devices
Hi, I was wondering... Why is "Support for Large Block Devices" still an option? Shouldn't it be compiled in always? Or maybe there are some cons like incompatibility or something? Regards, Maciej - 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/
Support for Large Block Devices
Hi, I was wondering... Why is Support for Large Block Devices still an option? Shouldn't it be compiled in always? Or maybe there are some cons like incompatibility or something? Regards, Maciej - 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/
