Re: Oops and Panics in 2.6.21.1, 2.6.20.6 and 2.6.19.2
On 06/29/2007 03:12 PM, Satyam Sharma wrote: > Hi Clemens, > > [ Cc:'ing Andrew, original thread at http://lkml.org/lkml/2007/5/15/354 ] > > On 6/29/07, Clemens Schwaighofer <[EMAIL PROTECTED]> wrote: >> On 05/16/2007 09:24 AM, Clemens Schwaighofer wrote: >> > Hi, >> >> I had my system running up for about one month without any issues, and >> then it happened again, same kernel oops, panic, end. >> >> So I have upgraded to 2.6.22-rc4-mm2 in hope it might fix it, but I just >> got another oops (uptime 4d) [see attached file] > > You "upgraded" from -stable series kernels (2.6.19.2 / 2.6.20.6 / > 2.6.21.1) to a -mm kernel, which is anything but :-) yeah, its sort of "last hope" > On the one hand, I really like that we're getting testers for -mm > kernels, but on the other hand, my good and honest side would > recommend you to install stable kernels (2.6.x.y versions) on > production systems, if you really care about uptimes. thats fine. its just my workstation here. I would never ever do that on any production box. I am too old to be that experimental :) >> my config hasn't changed in any way to the previous kernels. > > This doesn't look like the same oops you were getting persistently > with 2.6.21.1 ... you could try upgrading to 2.6.22-rc6 (without -mm) > too, if the oops in 2.6.21.1 was occurring too frequently in your setup; > possibly it has been resolved in the 22-rc series. I will try that. thanks a lot for the tip (I upgraded to rc6-mm1, and I will see if I get the oops again, or the other one ...) > Satyam > > [ Clemens' 2.6.22-rc4-mm2 oops below. ] > > > Jun 29 11:25:08 saturn kernel: [348308.690154] BUG: unable to handle > kernel NULL pointer dereference at virtual address 0001 > Jun 29 11:25:08 saturn kernel: [348308.690160] printing eip: > Jun 29 11:25:08 saturn kernel: [348308.690162] c108887c > Jun 29 11:25:08 saturn kernel: [348308.690163] *pde = > Jun 29 11:25:08 saturn kernel: [348308.690166] Oops: [#2] > Jun 29 11:25:08 saturn kernel: [348308.690167] PREEMPT > Jun 29 11:25:08 saturn kernel: [348308.690169] Modules linked in: > eeprom pcspkr i2c_viapro k8temp hwmon i2c_core > Jun 29 11:25:08 saturn kernel: [348308.690177] CPU:0 > Jun 29 11:25:08 saturn kernel: [348308.690177] EIP: > 0060:[__d_lookup+108/336]Not tainted VLI > Jun 29 11:25:08 saturn kernel: [348308.690179] EFLAGS: 00010202 > (2.6.22-rc4-mm2 #1) > Jun 29 11:25:08 saturn kernel: [348308.690185] EIP is at > __d_lookup+0x6c/0x150 > Jun 29 11:25:08 saturn kernel: [348308.690187] eax: 0001 ebx: > 0001 ecx: 0001 edx: 089c1579 > Jun 29 11:25:08 saturn kernel: [348308.690190] esi: c6840ee8 edi: > c301d734 ebp: f786f080 esp: c6840e84 > Jun 29 11:25:08 saturn kernel: [348308.690193] ds: 007b es: 007b > fs: gs: 0033 ss: 0068 > Jun 29 11:25:08 saturn kernel: [348308.690196] Process nfsd (pid: > 30536, ti=c684 task=c62bce90 task.ti=c684) > Jun 29 11:25:08 saturn kernel: [348308.690198] Stack: c301d734 > 089c1579 c6840edb 0002 c6840ee8 0005 c6840edb > Jun 29 11:25:08 saturn kernel: [348308.690205]f9ec > c6840ee8 c301d734 c471ba84 c1088976 c7bbb090 c7bbb090 > Jun 29 11:25:08 saturn kernel: [348308.690211]c10b49fc > c6840edb 000d c14914fb 7793 332bce90 31313630 c5469900 > Jun 29 11:25:08 saturn kernel: [348308.690217] Call Trace: > Jun 29 11:25:08 saturn kernel: [348308.690220] [d_lookup+22/64] > d_lookup+0x16/0x40 > Jun 29 11:25:08 saturn kernel: [348308.690224] > [proc_flush_task+76/496] proc_flush_task+0x4c/0x1f0 > Jun 29 11:25:08 saturn kernel: [348308.690229] [release_task+612/880] > release_task+0x264/0x370 > Jun 29 11:25:08 saturn kernel: [348308.690234] [do_wait+1850/3072] > do_wait+0x73a/0xc00 > Jun 29 11:25:08 saturn kernel: [348308.690239] > [_spin_unlock_irq+38/64] _spin_unlock_irq+0x26/0x40 > Jun 29 11:25:08 saturn kernel: [348308.690243] > [default_wake_function+0/16] default_wake_function+0x0/0x10 > Jun 29 11:25:08 saturn kernel: [348308.690247] [sys_wait4+49/64] > sys_wait4+0x31/0x40 > Jun 29 11:25:08 saturn kernel: [348308.690251] [sys_waitpid+39/48] > sys_waitpid+0x27/0x30 > Jun 29 11:25:08 saturn kernel: [348308.690255] [syscall_call+7/11] > syscall_call+0x7/0xb > Jun 29 11:25:08 saturn kernel: [348308.690259] === > Jun 29 11:25:08 saturn kernel: [348308.690260] INFO: lockdep is turned off. > Jun 29 11:25:08 saturn kernel: [348308.690262] Code: d3 e8 31 c3 23 1d > b4 d8 51 c1 b8 01 00 00 00 c1 e3 02 03 1d bc d8 51 c1 e8 e2 24 f9 ff > 8b 1b 85 db 75 08 eb 44 85 c0 89 c3 74 3e <8b> 03 0f 18 00 90 8d 6b d8 > 8b 54 24 04 3b 55 34 75 e8 8b 34 24 >
Re: Oops and Panics in 2.6.21.1, 2.6.20.6 and 2.6.19.2
On 06/29/2007 03:12 PM, Satyam Sharma wrote: Hi Clemens, [ Cc:'ing Andrew, original thread at http://lkml.org/lkml/2007/5/15/354 ] On 6/29/07, Clemens Schwaighofer [EMAIL PROTECTED] wrote: On 05/16/2007 09:24 AM, Clemens Schwaighofer wrote: Hi, I had my system running up for about one month without any issues, and then it happened again, same kernel oops, panic, end. So I have upgraded to 2.6.22-rc4-mm2 in hope it might fix it, but I just got another oops (uptime 4d) [see attached file] You upgraded from -stable series kernels (2.6.19.2 / 2.6.20.6 / 2.6.21.1) to a -mm kernel, which is anything but :-) yeah, its sort of last hope On the one hand, I really like that we're getting testers for -mm kernels, but on the other hand, my good and honest side would recommend you to install stable kernels (2.6.x.y versions) on production systems, if you really care about uptimes. thats fine. its just my workstation here. I would never ever do that on any production box. I am too old to be that experimental :) my config hasn't changed in any way to the previous kernels. This doesn't look like the same oops you were getting persistently with 2.6.21.1 ... you could try upgrading to 2.6.22-rc6 (without -mm) too, if the oops in 2.6.21.1 was occurring too frequently in your setup; possibly it has been resolved in the 22-rc series. I will try that. thanks a lot for the tip (I upgraded to rc6-mm1, and I will see if I get the oops again, or the other one ...) Satyam [ Clemens' 2.6.22-rc4-mm2 oops below. ] Jun 29 11:25:08 saturn kernel: [348308.690154] BUG: unable to handle kernel NULL pointer dereference at virtual address 0001 Jun 29 11:25:08 saturn kernel: [348308.690160] printing eip: Jun 29 11:25:08 saturn kernel: [348308.690162] c108887c Jun 29 11:25:08 saturn kernel: [348308.690163] *pde = Jun 29 11:25:08 saturn kernel: [348308.690166] Oops: [#2] Jun 29 11:25:08 saturn kernel: [348308.690167] PREEMPT Jun 29 11:25:08 saturn kernel: [348308.690169] Modules linked in: eeprom pcspkr i2c_viapro k8temp hwmon i2c_core Jun 29 11:25:08 saturn kernel: [348308.690177] CPU:0 Jun 29 11:25:08 saturn kernel: [348308.690177] EIP: 0060:[__d_lookup+108/336]Not tainted VLI Jun 29 11:25:08 saturn kernel: [348308.690179] EFLAGS: 00010202 (2.6.22-rc4-mm2 #1) Jun 29 11:25:08 saturn kernel: [348308.690185] EIP is at __d_lookup+0x6c/0x150 Jun 29 11:25:08 saturn kernel: [348308.690187] eax: 0001 ebx: 0001 ecx: 0001 edx: 089c1579 Jun 29 11:25:08 saturn kernel: [348308.690190] esi: c6840ee8 edi: c301d734 ebp: f786f080 esp: c6840e84 Jun 29 11:25:08 saturn kernel: [348308.690193] ds: 007b es: 007b fs: gs: 0033 ss: 0068 Jun 29 11:25:08 saturn kernel: [348308.690196] Process nfsd (pid: 30536, ti=c684 task=c62bce90 task.ti=c684) Jun 29 11:25:08 saturn kernel: [348308.690198] Stack: c301d734 089c1579 c6840edb 0002 c6840ee8 0005 c6840edb Jun 29 11:25:08 saturn kernel: [348308.690205]f9ec c6840ee8 c301d734 c471ba84 c1088976 c7bbb090 c7bbb090 Jun 29 11:25:08 saturn kernel: [348308.690211]c10b49fc c6840edb 000d c14914fb 7793 332bce90 31313630 c5469900 Jun 29 11:25:08 saturn kernel: [348308.690217] Call Trace: Jun 29 11:25:08 saturn kernel: [348308.690220] [d_lookup+22/64] d_lookup+0x16/0x40 Jun 29 11:25:08 saturn kernel: [348308.690224] [proc_flush_task+76/496] proc_flush_task+0x4c/0x1f0 Jun 29 11:25:08 saturn kernel: [348308.690229] [release_task+612/880] release_task+0x264/0x370 Jun 29 11:25:08 saturn kernel: [348308.690234] [do_wait+1850/3072] do_wait+0x73a/0xc00 Jun 29 11:25:08 saturn kernel: [348308.690239] [_spin_unlock_irq+38/64] _spin_unlock_irq+0x26/0x40 Jun 29 11:25:08 saturn kernel: [348308.690243] [default_wake_function+0/16] default_wake_function+0x0/0x10 Jun 29 11:25:08 saturn kernel: [348308.690247] [sys_wait4+49/64] sys_wait4+0x31/0x40 Jun 29 11:25:08 saturn kernel: [348308.690251] [sys_waitpid+39/48] sys_waitpid+0x27/0x30 Jun 29 11:25:08 saturn kernel: [348308.690255] [syscall_call+7/11] syscall_call+0x7/0xb Jun 29 11:25:08 saturn kernel: [348308.690259] === Jun 29 11:25:08 saturn kernel: [348308.690260] INFO: lockdep is turned off. Jun 29 11:25:08 saturn kernel: [348308.690262] Code: d3 e8 31 c3 23 1d b4 d8 51 c1 b8 01 00 00 00 c1 e3 02 03 1d bc d8 51 c1 e8 e2 24 f9 ff 8b 1b 85 db 75 08 eb 44 85 c0 89 c3 74 3e 8b 03 0f 18 00 90 8d 6b d8 8b 54 24 04 3b 55 34 75 e8 8b 34 24 Jun 29 11:25:08 saturn kernel: [348308.690289] EIP: [__d_lookup+108/336] __d_lookup+0x6c/0x150 SS:ESP 0068:c6840e84 Jun 29 11:25:08 saturn kernel: [348308.690296] note: nfsd[30536] exited with preempt_count 1 Jun 29 11:25:08 saturn kernel: [348308.690303] BUG: scheduling while atomic: nfsd/0x1002/30536 Jun 29 11:25:08 saturn kernel: [348308.690305] INFO: lockdep is turned off. Jun 29 11:25:08 saturn kernel
Re: Oops and Panics in 2.6.21.1, 2.6.20.6 and 2.6.19.2
On 05/16/2007 09:24 AM, Clemens Schwaighofer wrote: > Hi, I had my system running up for about one month without any issues, and then it happened again, same kernel oops, panic, end. So I have upgraded to 2.6.22-rc4-mm2 in hope it might fix it, but I just got another oops (uptime 4d) [see attached file] my config hasn't changed in any way to the previous kernels. -- [ Clemens Schwaighofer -=:~ ] [ TEQUILA\ Japan IT Group] [6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jp ] Jun 29 11:25:08 saturn kernel: [348308.690154] BUG: unable to handle kernel NULL pointer dereference at virtual address 0001 Jun 29 11:25:08 saturn kernel: [348308.690160] printing eip: Jun 29 11:25:08 saturn kernel: [348308.690162] c108887c Jun 29 11:25:08 saturn kernel: [348308.690163] *pde = Jun 29 11:25:08 saturn kernel: [348308.690166] Oops: [#2] Jun 29 11:25:08 saturn kernel: [348308.690167] PREEMPT Jun 29 11:25:08 saturn kernel: [348308.690169] Modules linked in: eeprom pcspkr i2c_viapro k8temp hwmon i2c_core Jun 29 11:25:08 saturn kernel: [348308.690177] CPU:0 Jun 29 11:25:08 saturn kernel: [348308.690177] EIP:0060:[__d_lookup+108/336]Not tainted VLI Jun 29 11:25:08 saturn kernel: [348308.690179] EFLAGS: 00010202 (2.6.22-rc4-mm2 #1) Jun 29 11:25:08 saturn kernel: [348308.690185] EIP is at __d_lookup+0x6c/0x150 Jun 29 11:25:08 saturn kernel: [348308.690187] eax: 0001 ebx: 0001 ecx: 0001 edx: 089c1579 Jun 29 11:25:08 saturn kernel: [348308.690190] esi: c6840ee8 edi: c301d734 ebp: f786f080 esp: c6840e84 Jun 29 11:25:08 saturn kernel: [348308.690193] ds: 007b es: 007b fs: gs: 0033 ss: 0068 Jun 29 11:25:08 saturn kernel: [348308.690196] Process nfsd (pid: 30536, ti=c684 task=c62bce90 task.ti=c684) Jun 29 11:25:08 saturn kernel: [348308.690198] Stack: c301d734 089c1579 c6840edb 0002 c6840ee8 0005 c6840edb Jun 29 11:25:08 saturn kernel: [348308.690205]f9ec c6840ee8 c301d734 c471ba84 c1088976 c7bbb090 c7bbb090 Jun 29 11:25:08 saturn kernel: [348308.690211]c10b49fc c6840edb 000d c14914fb 7793 332bce90 31313630 c5469900 Jun 29 11:25:08 saturn kernel: [348308.690217] Call Trace: Jun 29 11:25:08 saturn kernel: [348308.690220] [d_lookup+22/64] d_lookup+0x16/0x40 Jun 29 11:25:08 saturn kernel: [348308.690224] [proc_flush_task+76/496] proc_flush_task+0x4c/0x1f0 Jun 29 11:25:08 saturn kernel: [348308.690229] [release_task+612/880] release_task+0x264/0x370 Jun 29 11:25:08 saturn kernel: [348308.690234] [do_wait+1850/3072] do_wait+0x73a/0xc00 Jun 29 11:25:08 saturn kernel: [348308.690239] [_spin_unlock_irq+38/64] _spin_unlock_irq+0x26/0x40 Jun 29 11:25:08 saturn kernel: [348308.690243] [default_wake_function+0/16] default_wake_function+0x0/0x10 Jun 29 11:25:08 saturn kernel: [348308.690247] [sys_wait4+49/64] sys_wait4+0x31/0x40 Jun 29 11:25:08 saturn kernel: [348308.690251] [sys_waitpid+39/48] sys_waitpid+0x27/0x30 Jun 29 11:25:08 saturn kernel: [348308.690255] [syscall_call+7/11] syscall_call+0x7/0xb Jun 29 11:25:08 saturn kernel: [348308.690259] === Jun 29 11:25:08 saturn kernel: [348308.690260] INFO: lockdep is turned off. Jun 29 11:25:08 saturn kernel: [348308.690262] Code: d3 e8 31 c3 23 1d b4 d8 51 c1 b8 01 00 00 00 c1 e3 02 03 1d bc d8 51 c1 e8 e2 24 f9 ff 8b 1b 85 db 75 08 eb 44 85 c0 89 c3 74 3e <8b> 03 0f 18 00 90 8d 6b d8 8b 54 24 04 3b 55 34 75 e8 8b 34 24 Jun 29 11:25:08 saturn kernel: [348308.690289] EIP: [__d_lookup+108/336] __d_lookup+0x6c/0x150 SS:ESP 0068:c6840e84 Jun 29 11:25:08 saturn kernel: [348308.690296] note: nfsd[30536] exited with preempt_count 1 Jun 29 11:25:08 saturn kernel: [348308.690303] BUG: scheduling while atomic: nfsd/0x1002/30536 Jun 29 11:25:08 saturn kernel: [348308.690305] INFO: lockdep is turned off. Jun 29 11:25:08 saturn kernel: [348308.690307] [schedule+1490/1744] schedule+0x5d2/0x6d0 Jun 29 11:25:08 saturn kernel: [348308.690311] [vt_console_print+106/688] vt_console_print+0x6a/0x2b0 Jun 29 11:25:08 saturn kernel: [348308.690316] [__cond_resched+18/48] __cond_resched+0x12/0x30 Jun 29 11:25:08 saturn kernel: [348308.690319] [cond_resched+42/64] cond_resched+0x2a/0x40 Jun 29 11:25:08 saturn kernel: [348308.690322] [unmap_vmas+1116/1184] unmap_vmas+0x45c/0x4a0 Jun 29 11:25:08 saturn kernel: [348308.690327] [exit_mmap+105/256] exit_mmap+0x69/0x100 Jun 29 11:25:08 saturn kernel: [348308.690331] [mmput+68/256] mmput+0x44/0x100 Jun 29 11:25:08 saturn kernel: [348308.690335] [do_exit+301/2224] do_exit+0x12d/0x8b0 Jun 29 11:25:08 saturn kernel: [348308.690339] [__wake_up+56/80] __wake_up+0x38/0x50 Jun 29 11:25:08 saturn kernel: [348308.690342] [die+574/576] die+0x23e/0x240 Jun 29 11:25:08 saturn kernel: [3483
Re: Oops and Panics in 2.6.21.1, 2.6.20.6 and 2.6.19.2
On 05/16/2007 09:24 AM, Clemens Schwaighofer wrote: Hi, I had my system running up for about one month without any issues, and then it happened again, same kernel oops, panic, end. So I have upgraded to 2.6.22-rc4-mm2 in hope it might fix it, but I just got another oops (uptime 4d) [see attached file] my config hasn't changed in any way to the previous kernels. -- [ Clemens Schwaighofer -=:~ ] [ TEQUILA\ Japan IT Group] [6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jp ] Jun 29 11:25:08 saturn kernel: [348308.690154] BUG: unable to handle kernel NULL pointer dereference at virtual address 0001 Jun 29 11:25:08 saturn kernel: [348308.690160] printing eip: Jun 29 11:25:08 saturn kernel: [348308.690162] c108887c Jun 29 11:25:08 saturn kernel: [348308.690163] *pde = Jun 29 11:25:08 saturn kernel: [348308.690166] Oops: [#2] Jun 29 11:25:08 saturn kernel: [348308.690167] PREEMPT Jun 29 11:25:08 saturn kernel: [348308.690169] Modules linked in: eeprom pcspkr i2c_viapro k8temp hwmon i2c_core Jun 29 11:25:08 saturn kernel: [348308.690177] CPU:0 Jun 29 11:25:08 saturn kernel: [348308.690177] EIP:0060:[__d_lookup+108/336]Not tainted VLI Jun 29 11:25:08 saturn kernel: [348308.690179] EFLAGS: 00010202 (2.6.22-rc4-mm2 #1) Jun 29 11:25:08 saturn kernel: [348308.690185] EIP is at __d_lookup+0x6c/0x150 Jun 29 11:25:08 saturn kernel: [348308.690187] eax: 0001 ebx: 0001 ecx: 0001 edx: 089c1579 Jun 29 11:25:08 saturn kernel: [348308.690190] esi: c6840ee8 edi: c301d734 ebp: f786f080 esp: c6840e84 Jun 29 11:25:08 saturn kernel: [348308.690193] ds: 007b es: 007b fs: gs: 0033 ss: 0068 Jun 29 11:25:08 saturn kernel: [348308.690196] Process nfsd (pid: 30536, ti=c684 task=c62bce90 task.ti=c684) Jun 29 11:25:08 saturn kernel: [348308.690198] Stack: c301d734 089c1579 c6840edb 0002 c6840ee8 0005 c6840edb Jun 29 11:25:08 saturn kernel: [348308.690205]f9ec c6840ee8 c301d734 c471ba84 c1088976 c7bbb090 c7bbb090 Jun 29 11:25:08 saturn kernel: [348308.690211]c10b49fc c6840edb 000d c14914fb 7793 332bce90 31313630 c5469900 Jun 29 11:25:08 saturn kernel: [348308.690217] Call Trace: Jun 29 11:25:08 saturn kernel: [348308.690220] [d_lookup+22/64] d_lookup+0x16/0x40 Jun 29 11:25:08 saturn kernel: [348308.690224] [proc_flush_task+76/496] proc_flush_task+0x4c/0x1f0 Jun 29 11:25:08 saturn kernel: [348308.690229] [release_task+612/880] release_task+0x264/0x370 Jun 29 11:25:08 saturn kernel: [348308.690234] [do_wait+1850/3072] do_wait+0x73a/0xc00 Jun 29 11:25:08 saturn kernel: [348308.690239] [_spin_unlock_irq+38/64] _spin_unlock_irq+0x26/0x40 Jun 29 11:25:08 saturn kernel: [348308.690243] [default_wake_function+0/16] default_wake_function+0x0/0x10 Jun 29 11:25:08 saturn kernel: [348308.690247] [sys_wait4+49/64] sys_wait4+0x31/0x40 Jun 29 11:25:08 saturn kernel: [348308.690251] [sys_waitpid+39/48] sys_waitpid+0x27/0x30 Jun 29 11:25:08 saturn kernel: [348308.690255] [syscall_call+7/11] syscall_call+0x7/0xb Jun 29 11:25:08 saturn kernel: [348308.690259] === Jun 29 11:25:08 saturn kernel: [348308.690260] INFO: lockdep is turned off. Jun 29 11:25:08 saturn kernel: [348308.690262] Code: d3 e8 31 c3 23 1d b4 d8 51 c1 b8 01 00 00 00 c1 e3 02 03 1d bc d8 51 c1 e8 e2 24 f9 ff 8b 1b 85 db 75 08 eb 44 85 c0 89 c3 74 3e 8b 03 0f 18 00 90 8d 6b d8 8b 54 24 04 3b 55 34 75 e8 8b 34 24 Jun 29 11:25:08 saturn kernel: [348308.690289] EIP: [__d_lookup+108/336] __d_lookup+0x6c/0x150 SS:ESP 0068:c6840e84 Jun 29 11:25:08 saturn kernel: [348308.690296] note: nfsd[30536] exited with preempt_count 1 Jun 29 11:25:08 saturn kernel: [348308.690303] BUG: scheduling while atomic: nfsd/0x1002/30536 Jun 29 11:25:08 saturn kernel: [348308.690305] INFO: lockdep is turned off. Jun 29 11:25:08 saturn kernel: [348308.690307] [schedule+1490/1744] schedule+0x5d2/0x6d0 Jun 29 11:25:08 saturn kernel: [348308.690311] [vt_console_print+106/688] vt_console_print+0x6a/0x2b0 Jun 29 11:25:08 saturn kernel: [348308.690316] [__cond_resched+18/48] __cond_resched+0x12/0x30 Jun 29 11:25:08 saturn kernel: [348308.690319] [cond_resched+42/64] cond_resched+0x2a/0x40 Jun 29 11:25:08 saturn kernel: [348308.690322] [unmap_vmas+1116/1184] unmap_vmas+0x45c/0x4a0 Jun 29 11:25:08 saturn kernel: [348308.690327] [exit_mmap+105/256] exit_mmap+0x69/0x100 Jun 29 11:25:08 saturn kernel: [348308.690331] [mmput+68/256] mmput+0x44/0x100 Jun 29 11:25:08 saturn kernel: [348308.690335] [do_exit+301/2224] do_exit+0x12d/0x8b0 Jun 29 11:25:08 saturn kernel: [348308.690339] [__wake_up+56/80] __wake_up+0x38/0x50 Jun 29 11:25:08 saturn kernel: [348308.690342] [die+574/576] die+0x23e/0x240 Jun 29 11:25:08 saturn kernel: [348308.690346] [do_page_fault
Re: Oops and Panics in 2.6.21.1, 2.6.20.6 and 2.6.19.2
On 05/16/2007 10:53 AM, Andrew Morton wrote: > How frequently do you see these failures? If it's repeatable with any > reliability > then it'd be great if you could test a patchset for us. It's at: > > http://userweb.kernel.org/~akpm/cs.gz > > that's a single patch against 2.6.21-rc1, containing the following patches, > which > are from the forthcoming 2.6.21-rc1-mm1 lineup: (and those above are 2.6.22-rc1 of course) well, I tried to apply those patches and when I compile I get this error: CC net/ipv6/exthdrs.o net/ipv6/exthdrs.c: In function ‘ipv6_rthdr_rcv’: net/ipv6/exthdrs.c:390: error: ‘struct sk_buff’ has no member named ‘h’ net/ipv6/exthdrs.c:391: error: ‘struct sk_buff’ has no member named ‘h’ net/ipv6/exthdrs.c:391: error: ‘struct sk_buff’ has no member named ‘h’ net/ipv6/exthdrs.c:398: error: ‘struct sk_buff’ has no member named ‘h’ make[2]: *** [net/ipv6/exthdrs.o] Error 1 make[1]: *** [net/ipv6] Error 2 make: *** [net] Error 2 It's probably totally unrelated but sadly a showstopper for testing the new sysfs patches, -- [ Clemens Schwaighofer -=:~ ] [ TEQUILA\ Japan IT Group] [6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jp ] signature.asc Description: OpenPGP digital signature
Re: Oops and Panics in 2.6.21.1, 2.6.20.6 and 2.6.19.2
On 05/16/2007 10:53 AM, Andrew Morton wrote: > >> I think it started with 2.6.19.2, I cannot remember I had any of those >> problems before. The box can work fine for about a week or more, or it >> looks up several times a day. I run a memtest for 10 h, but I had no errors. > > shrink_dcache_memory->...sysfs_d_iput->BUG > > BUG_ON(sd->s_dentry != dentry); > > a number of people have hit that, on and off. > > We were close to having a fix, I think, but then we decided that great > chunks of sysfs needed rewriting and I believe that we believe that this > great rewrite will fix this bug. > > But alas, it's all too late for 2.6.22. Well, there is always hope for 2.6.23 :) > How frequently do you see these failures? If it's repeatable with any > reliability > then it'd be great if you could test a patchset for us. It's at: > > http://userweb.kernel.org/~akpm/cs.gz > > that's a single patch against 2.6.21-rc1, containing the following patches, > which > are from the forthcoming 2.6.21-rc1-mm1 lineup: I get this very frequently recently. I just got hit by another PANIC which was probably the same issue. I will get this patch and try it out and see if it helps for me. -- [ Clemens Schwaighofer -=:~ ] [ TEQUILA\ Japan IT Group] [6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jp ] signature.asc Description: OpenPGP digital signature
Re: Oops and Panics in 2.6.21.1, 2.6.20.6 and 2.6.19.2
On 05/16/2007 09:24 AM, Clemens Schwaighofer wrote: > The oops have the same error style like this Panic. I tried to capture > one, but right after copying it into vim, I got a Panic. So next time I > try to. I just got a oops and I could record it, the followed Kernel Panic didn't send out any Panic to my remote serial box. So I cannot give more information about that. -- [ Clemens Schwaighofer -=:~ ] [ TEQUILA\ Japan IT Group] [6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jp ] [ 5955.558356] BUG: unable to handle kernel paging request at virtual address 182b10f7 [ 5955.558362] printing eip: [ 5955.558363] 182b10f7 [ 5955.558365] *pde = [ 5955.558367] Oops: [#1] [ 5955.558369] PREEMPT [ 5955.558370] Modules linked in: eeprom i2c_viapro i2c_core pcspkr k8temp hwmon eth1394 [ 5955.558377] CPU:0 [ 5955.558378] EIP:0060:[<182b10f7>]Not tainted VLI [ 5955.558379] EFLAGS: 00010202 (2.6.21.1 #1) [ 5955.558382] EIP is at 0x182b10f7 [ 5955.558385] eax: 80c7dcc1 ebx: f786bc00 ecx: 182b10f7 edx: 0002 [ 5955.558388] esi: f7836200 edi: c2669f6c ebp: f780c88f esp: c2669f34 [ 5955.558390] ds: 007b es: 007b fs: 00d8 gs: ss: 0068 [ 5955.558393] Process pdflush (pid: 192, ti=c2669000 task=c268da90 task.ti=c2669000) [ 5955.558395] Stack: c108a454 f7836284 00158443 024a f7836200 f783623c c2669f6c c147774c [ 5955.558401]c108aa8b c2669fb8 00158925 bc01 c1053030 c1052c44 [ 5955.558406]c2669f94 01b6 024a 0025 [ 5955.558411] Call Trace: [ 5955.558413] [] sync_sb_inodes+0x74/0x280 [ 5955.558419] [] writeback_inodes+0xab/0x110 [ 5955.558423] [] pdflush+0x0/0x220 [ 5955.558426] [] wb_kupdate+0x74/0xe0 [ 5955.558430] [] pdflush+0x114/0x220 [ 5955.558433] [] wb_kupdate+0x0/0xe0 [ 5955.558436] [] kthread+0xa8/0xe0 [ 5955.558439] [] kthread+0x0/0xe0 [ 5955.558442] [] kernel_thread_helper+0x7/0x18 [ 5955.558446] === [ 5955.558447] Code: Bad EIP value. [ 5955.558449] EIP: [<182b10f7>] 0x182b10f7 SS:ESP 0068:c2669f34 [ 5955.558455] note: pdflush[192] exited with preempt_count 1 signature.asc Description: OpenPGP digital signature
Re: Oops and Panics in 2.6.21.1, 2.6.20.6 and 2.6.19.2
On 05/16/2007 09:24 AM, Clemens Schwaighofer wrote: The oops have the same error style like this Panic. I tried to capture one, but right after copying it into vim, I got a Panic. So next time I try to. I just got a oops and I could record it, the followed Kernel Panic didn't send out any Panic to my remote serial box. So I cannot give more information about that. -- [ Clemens Schwaighofer -=:~ ] [ TEQUILA\ Japan IT Group] [6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jp ] [ 5955.558356] BUG: unable to handle kernel paging request at virtual address 182b10f7 [ 5955.558362] printing eip: [ 5955.558363] 182b10f7 [ 5955.558365] *pde = [ 5955.558367] Oops: [#1] [ 5955.558369] PREEMPT [ 5955.558370] Modules linked in: eeprom i2c_viapro i2c_core pcspkr k8temp hwmon eth1394 [ 5955.558377] CPU:0 [ 5955.558378] EIP:0060:[182b10f7]Not tainted VLI [ 5955.558379] EFLAGS: 00010202 (2.6.21.1 #1) [ 5955.558382] EIP is at 0x182b10f7 [ 5955.558385] eax: 80c7dcc1 ebx: f786bc00 ecx: 182b10f7 edx: 0002 [ 5955.558388] esi: f7836200 edi: c2669f6c ebp: f780c88f esp: c2669f34 [ 5955.558390] ds: 007b es: 007b fs: 00d8 gs: ss: 0068 [ 5955.558393] Process pdflush (pid: 192, ti=c2669000 task=c268da90 task.ti=c2669000) [ 5955.558395] Stack: c108a454 f7836284 00158443 024a f7836200 f783623c c2669f6c c147774c [ 5955.558401]c108aa8b c2669fb8 00158925 bc01 c1053030 c1052c44 [ 5955.558406]c2669f94 01b6 024a 0025 [ 5955.558411] Call Trace: [ 5955.558413] [c108a454] sync_sb_inodes+0x74/0x280 [ 5955.558419] [c108aa8b] writeback_inodes+0xab/0x110 [ 5955.558423] [c1053030] pdflush+0x0/0x220 [ 5955.558426] [c1052c44] wb_kupdate+0x74/0xe0 [ 5955.558430] [c1053144] pdflush+0x114/0x220 [ 5955.558433] [c1052bd0] wb_kupdate+0x0/0xe0 [ 5955.558436] [c102fdd8] kthread+0xa8/0xe0 [ 5955.558439] [c102fd30] kthread+0x0/0xe0 [ 5955.558442] [c1004bff] kernel_thread_helper+0x7/0x18 [ 5955.558446] === [ 5955.558447] Code: Bad EIP value. [ 5955.558449] EIP: [182b10f7] 0x182b10f7 SS:ESP 0068:c2669f34 [ 5955.558455] note: pdflush[192] exited with preempt_count 1 signature.asc Description: OpenPGP digital signature
Re: Oops and Panics in 2.6.21.1, 2.6.20.6 and 2.6.19.2
On 05/16/2007 10:53 AM, Andrew Morton wrote: I think it started with 2.6.19.2, I cannot remember I had any of those problems before. The box can work fine for about a week or more, or it looks up several times a day. I run a memtest for 10 h, but I had no errors. shrink_dcache_memory-...sysfs_d_iput-BUG BUG_ON(sd-s_dentry != dentry); a number of people have hit that, on and off. We were close to having a fix, I think, but then we decided that great chunks of sysfs needed rewriting and I believe that we believe that this great rewrite will fix this bug. But alas, it's all too late for 2.6.22. Well, there is always hope for 2.6.23 :) How frequently do you see these failures? If it's repeatable with any reliability then it'd be great if you could test a patchset for us. It's at: http://userweb.kernel.org/~akpm/cs.gz that's a single patch against 2.6.21-rc1, containing the following patches, which are from the forthcoming 2.6.21-rc1-mm1 lineup: I get this very frequently recently. I just got hit by another PANIC which was probably the same issue. I will get this patch and try it out and see if it helps for me. -- [ Clemens Schwaighofer -=:~ ] [ TEQUILA\ Japan IT Group] [6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jp ] signature.asc Description: OpenPGP digital signature
Re: Oops and Panics in 2.6.21.1, 2.6.20.6 and 2.6.19.2
On 05/16/2007 10:53 AM, Andrew Morton wrote: How frequently do you see these failures? If it's repeatable with any reliability then it'd be great if you could test a patchset for us. It's at: http://userweb.kernel.org/~akpm/cs.gz that's a single patch against 2.6.21-rc1, containing the following patches, which are from the forthcoming 2.6.21-rc1-mm1 lineup: (and those above are 2.6.22-rc1 of course) well, I tried to apply those patches and when I compile I get this error: CC net/ipv6/exthdrs.o net/ipv6/exthdrs.c: In function ‘ipv6_rthdr_rcv’: net/ipv6/exthdrs.c:390: error: ‘struct sk_buff’ has no member named ‘h’ net/ipv6/exthdrs.c:391: error: ‘struct sk_buff’ has no member named ‘h’ net/ipv6/exthdrs.c:391: error: ‘struct sk_buff’ has no member named ‘h’ net/ipv6/exthdrs.c:398: error: ‘struct sk_buff’ has no member named ‘h’ make[2]: *** [net/ipv6/exthdrs.o] Error 1 make[1]: *** [net/ipv6] Error 2 make: *** [net] Error 2 It's probably totally unrelated but sadly a showstopper for testing the new sysfs patches, -- [ Clemens Schwaighofer -=:~ ] [ TEQUILA\ Japan IT Group] [6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jp ] signature.asc Description: OpenPGP digital signature
Re: Can't use SYSFS for "Proprietry" driver modules !!!.
On 31/3/2005, at 08:30, John Pearson wrote: E.g.: suppose there are 2 snack bars within 100 yards of a school; one is out of sight, across an intersection and down a side street, and one is clearly visible across an empty lot. For years the lot has been unfenced and, human nature being what it is, kids just walk across the open lot. The owner of the lot then decides to put up a high fence around it with a combination lock on the gate (now he's raising chinchillas, or peaches; he won't say) so all the kids start going to the other snackbar, except for a few that he trusts with the combination. It seems to me you're suggesting that the snackbar owner who's lost out would have an action for restraint of trade; I can't see it myself. Well in Austria there is a law: if you walk through an area that is not public and do this for a very long time years and suddenly the owner stops you from doing this, you could sue him for stopping you doing a usual thing. But real life issues and software laws are more than two kind of shoes. They are two kind of universes. Right and Code changes always happens, some approve i some not. And there will be always people not like it. Fact is the kernel is a GPL thing so logically the coders want to keep it GPL, lg, clemens PGP.sig Description: This is a digitally signed message part
Re: Can't use SYSFS for Proprietry driver modules !!!.
On 31/3/2005, at 08:30, John Pearson wrote: E.g.: suppose there are 2 snack bars within 100 yards of a school; one is out of sight, across an intersection and down a side street, and one is clearly visible across an empty lot. For years the lot has been unfenced and, human nature being what it is, kids just walk across the open lot. The owner of the lot then decides to put up a high fence around it with a combination lock on the gate (now he's raising chinchillas, or peaches; he won't say) so all the kids start going to the other snackbar, except for a few that he trusts with the combination. It seems to me you're suggesting that the snackbar owner who's lost out would have an action for restraint of trade; I can't see it myself. Well in Austria there is a law: if you walk through an area that is not public and do this for a very long time years and suddenly the owner stops you from doing this, you could sue him for stopping you doing a usual thing. But real life issues and software laws are more than two kind of shoes. They are two kind of universes. Right and Code changes always happens, some approve i some not. And there will be always people not like it. Fact is the kernel is a GPL thing so logically the coders want to keep it GPL, lg, clemens PGP.sig Description: This is a digitally signed message part
Re: Can't use SYSFS for "Proprietry" driver modules !!!.
The fact that Nvidia and ATI get away with it? The choose to take a risk based upon a specific interpretation of the boundary of a derivative work. Since the boundary is untested in law its not certain who is right. Plus the fact, that if somebody sues them, they just remove the drivers from their list. Linux is so small for them, that probably don't care (plus there is an open source nv & ati driver). [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] - 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: Can't use SYSFS for Proprietry driver modules !!!.
The fact that Nvidia and ATI get away with it? The choose to take a risk based upon a specific interpretation of the boundary of a derivative work. Since the boundary is untested in law its not certain who is right. Plus the fact, that if somebody sues them, they just remove the drivers from their list. Linux is so small for them, that probably don't care (plus there is an open source nv ati driver). [ Clemens Schwaighofer -=:~ ] [ TBWA\ TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] - 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 2.6.11-ac1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/08/2005 03:49 PM, Chris Wright wrote: > * Clemens Schwaighofer ([EMAIL PROTECTED]) wrote: > >>>2.6.11-ac1 >>>oFix jbd race in ext3(Stephen Tweedie) >> >>will that patch actually appear in 2.6.11.2? At least it looks like a >>candidate for me ... > > > Yes, we are intending to pick up bits from -ac (you might have missed > that in another thread). Probably. I am sorry :) I sort of got lost in the tons of RFD, etc threads :) - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCLUunjBz/yQjBxz8RArh2AJ4oMATN/P+9TPtFEDrGQhu2iox+MQCfZobG kc+hXDhfKyHhGK7UF6dKw2I= =CVCH -END PGP SIGNATURE- - 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 2.6.11-ac1
--On Monday, March 07, 2005 09:34:22 PM + Alan Cox <[EMAIL PROTECTED]> wrote: For a couple of reasons I've not yet merged Greg's 2.6.11.1 yet but this diff should actually apply to either right now. 2.6.11-ac1 o Fix jbd race in ext3(Stephen Tweedie) will that patch actually appear in 2.6.11.2? At least it looks like a candidate for me ... [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] pgpzmcmZz0gRq.pgp Description: PGP signature
Re: Linux 2.6.11-ac1
--On Monday, March 07, 2005 09:34:22 PM + Alan Cox [EMAIL PROTECTED] wrote: For a couple of reasons I've not yet merged Greg's 2.6.11.1 yet but this diff should actually apply to either right now. 2.6.11-ac1 o Fix jbd race in ext3(Stephen Tweedie) will that patch actually appear in 2.6.11.2? At least it looks like a candidate for me ... [ Clemens Schwaighofer -=:~ ] [ TBWA\ TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] pgpzmcmZz0gRq.pgp Description: PGP signature
Re: Linux 2.6.11-ac1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/08/2005 03:49 PM, Chris Wright wrote: * Clemens Schwaighofer ([EMAIL PROTECTED]) wrote: 2.6.11-ac1 oFix jbd race in ext3(Stephen Tweedie) will that patch actually appear in 2.6.11.2? At least it looks like a candidate for me ... Yes, we are intending to pick up bits from -ac (you might have missed that in another thread). Probably. I am sorry :) I sort of got lost in the tons of RFD, etc threads :) - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCLUunjBz/yQjBxz8RArh2AJ4oMATN/P+9TPtFEDrGQhu2iox+MQCfZobG kc+hXDhfKyHhGK7UF6dKw2I= =CVCH -END PGP SIGNATURE- - 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: RFD: Kernel release numbering
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2005 07:21 AM, Linus Torvalds wrote: > Comments? before you do this, we have to make -rc's real rc's. Seriously how can it be that there is a diff between the last rc and the "vanilla" release. Thats a no-goer in my opinion. Even if it is small things, there is a chance that it breaks. If there patches that have to be applied, because they are bugfixes, then make another rc before going live. And odd/even sub number won't help here anyway. People who get the kernel won't know it, there will be confusion, etc. I would stick with the current scheme, I see no big advantage in a special odd/even numbering. If there is a bugfix release, call it X.Y.Z.1 like for 2.6.8, rest of the bugfixing can be found in -ac/-as patchsets anyway. The time of using vanilla kernels is long over. Nowadays its more like, something, where you wait that a vendor gives you a kernel, or else you will shot your own foot off ... - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCJ+W4jBz/yQjBxz8RAgnoAKCKGVcIujulCLyk8p3ole80RhhcOwCgyHSM tD2sZv+sCz7oG5MfokKh05c= =lnqT -END PGP SIGNATURE- - 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: [BK] upgrade will be needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/18/2005 01:00 PM, Theodore Ts'o wrote: > On Thu, Feb 17, 2005 at 06:32:04PM -0500, Sean wrote: > >>No. It's about recognizing the needs of more people than just the few at >>the top. Besides, with a free tool at the Head, bk could continue to be >>used underneath by Linus and anyone else. > > > If you think that, you truly do not understand the value of BK, and > why Linus chose it. He choose it because it was the best tool to do the job at that time. It might still be the best job to do it. But for a normal user, who just wants to check out certain bk pulls, the new license is not bearable. I think we need a SVN mirror here soon, very soon. - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCFWkcjBz/yQjBxz8RAm5IAKDERXzaCeh1Qcuipp3sjZXxC7/DwgCgpl63 YgVM09sYczPMJsedObgKkLI= =8vFK -END PGP SIGNATURE- - 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: [BK] upgrade will be needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/2005 07:27 PM, Sean wrote: > On Thu, February 17, 2005 4:27 am, Roland Kuhn said: > > >>The difference comes after the merge. Suppose Andrew didn't push >>everything to Linus. Then new patches come in, both trees change. In >>this situation it is very time consuming with subversion to work out >>the changes which still have to go from Andrew's tree to Linus' tree. > > > Since Andrew does this all by hand now, subversion / arch / whatever could > only improve the situation. And the kicker is that using a free system > would mean the result could be dumped into BK for those that want to use > it. The reverse unfortunately isn't true; not because of technical > reasons, but because of license restrictions. well I think Andrew will have tonsof small helper scripts for that. I doubt he has time to try out various vcs ... (especially if they are so complicated to use like arch). - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCFTecjBz/yQjBxz8RAqx5AJ9TCxTpvXkfnUbGiPM67VQsa5RVlwCeMXPR 9RPlx/090x7ALlctuvSnWo4= =9Xst -END PGP SIGNATURE- - 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: [BK] upgrade will be needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/2005 01:57 PM, Theodore Ts'o wrote: > Compare the number of developers, the number of overlapping > simultaneous development trees, and the number of patches that touch > overlapping files, and you'll begin to start to appreciate the > difference between a system that can work for Linux, and a system that > can working for simpler projects. apache might be simpler, but I doubt that for gcc. But well lets see what the gcc guys will decide. - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCFTb7jBz/yQjBxz8RAqK+AJ9qyQaqg/zQz/xt6XKpLjlJIC5u9gCbBrPg D/3yjB5iv7HCSMtVOIZx6Xo= =Zfsd -END PGP SIGNATURE- - 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: [BK] upgrade will be needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/2005 04:55 PM, Roland Kuhn wrote: > That said, it would of course be possible to improve the internal > workflow of our emperor penguin if he used subversion, but the > collaboration with others could not benefit the way it does with a > changeset-based approach. Question is then, what about keeping a main trunk with the vanialle release, and each dev has its own branch. now at a certain point you have to merge them. Now where is the difference between a central rep and a de-central one. At day X, patches from Andrew's tree have to go to Linus tree and from his tree into the new vanialla kernel. right? Somehow I can't see the difference here. > Linux kernel development is hard _and_ sexy :-) at least something :D - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCFFEojBz/yQjBxz8RAs5rAKC1i4RuDxyi3hjnRDfcjCYyRTGbNQCgsRgc ErnefDIDGimPjjXa8cALBQc= =lWQ8 -END PGP SIGNATURE- - 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: [BK] upgrade will be needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/2005 04:55 PM, Roland Kuhn wrote: That said, it would of course be possible to improve the internal workflow of our emperor penguin if he used subversion, but the collaboration with others could not benefit the way it does with a changeset-based approach. Question is then, what about keeping a main trunk with the vanialle release, and each dev has its own branch. now at a certain point you have to merge them. Now where is the difference between a central rep and a de-central one. At day X, patches from Andrew's tree have to go to Linus tree and from his tree into the new vanialla kernel. right? Somehow I can't see the difference here. Linux kernel development is hard _and_ sexy :-) at least something :D - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCFFEojBz/yQjBxz8RAs5rAKC1i4RuDxyi3hjnRDfcjCYyRTGbNQCgsRgc ErnefDIDGimPjjXa8cALBQc= =lWQ8 -END PGP SIGNATURE- - 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: [BK] upgrade will be needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/2005 01:57 PM, Theodore Ts'o wrote: Compare the number of developers, the number of overlapping simultaneous development trees, and the number of patches that touch overlapping files, and you'll begin to start to appreciate the difference between a system that can work for Linux, and a system that can working for simpler projects. apache might be simpler, but I doubt that for gcc. But well lets see what the gcc guys will decide. - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCFTb7jBz/yQjBxz8RAqK+AJ9qyQaqg/zQz/xt6XKpLjlJIC5u9gCbBrPg D/3yjB5iv7HCSMtVOIZx6Xo= =Zfsd -END PGP SIGNATURE- - 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: [BK] upgrade will be needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/2005 07:27 PM, Sean wrote: On Thu, February 17, 2005 4:27 am, Roland Kuhn said: The difference comes after the merge. Suppose Andrew didn't push everything to Linus. Then new patches come in, both trees change. In this situation it is very time consuming with subversion to work out the changes which still have to go from Andrew's tree to Linus' tree. Since Andrew does this all by hand now, subversion / arch / whatever could only improve the situation. And the kicker is that using a free system would mean the result could be dumped into BK for those that want to use it. The reverse unfortunately isn't true; not because of technical reasons, but because of license restrictions. well I think Andrew will have tonsof small helper scripts for that. I doubt he has time to try out various vcs ... (especially if they are so complicated to use like arch). - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCFTecjBz/yQjBxz8RAqx5AJ9TCxTpvXkfnUbGiPM67VQsa5RVlwCeMXPR 9RPlx/090x7ALlctuvSnWo4= =9Xst -END PGP SIGNATURE- - 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: [BK] upgrade will be needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/18/2005 01:00 PM, Theodore Ts'o wrote: On Thu, Feb 17, 2005 at 06:32:04PM -0500, Sean wrote: No. It's about recognizing the needs of more people than just the few at the top. Besides, with a free tool at the Head, bk could continue to be used underneath by Linus and anyone else. If you think that, you truly do not understand the value of BK, and why Linus chose it. He choose it because it was the best tool to do the job at that time. It might still be the best job to do it. But for a normal user, who just wants to check out certain bk pulls, the new license is not bearable. I think we need a SVN mirror here soon, very soon. - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCFWkcjBz/yQjBxz8RAm5IAKDERXzaCeh1Qcuipp3sjZXxC7/DwgCgpl63 YgVM09sYczPMJsedObgKkLI= =8vFK -END PGP SIGNATURE- - 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: [BK] upgrade will be needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/2005 12:39 AM, d.c wrote: > El Wed, 16 Feb 2005 18:45:27 +0900, > Clemens Schwaighofer <[EMAIL PROTECTED]> escribió: > > >>than mature VCS. Apache group is switching to it, gcc people are >>strongly thinking about it, and those two are _huge_ projects with tons >>of developers, patches, trunks, etc. > > > and all of them work today with CVS, so any SCM will fit their purposes. so, your point it is, because linux used none before, none than bk fit? - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCE+HpjBz/yQjBxz8RAr8lAJ4w6TK0c7H1fjs178Y9Q0Mr4hdGBgCg32cT LUSf7DWy++w+cczaHpeEnIs= =zRM5 -END PGP SIGNATURE- - 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: [BK] upgrade will be needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/2005 12:43 AM, Olivier Galibert wrote: >>Perhaps its about time, that linux also switches. > > > Think what you want of Larry, but SVN is nowhere near BK is term of > capabilities (and neither is arch for he matter). It's only better > compared to cvs, and then not by that much. first. what kind of advantages does bk have over other svn? Seriously. If Apache can use it, and gcc might use it (again two very large projects), what makes linux so differetnt that it can't. And I don't want _anything_ from Larry. I am just pointing out, that this kind of legal clause is more ridicolous than understandable. Last, why can you compare cvs to bk? and not subversion, or arch? arch and subversion are way superiour to cvs ... > SCM is hard and not sexy, I'm afraid. yes its hard, so we have to use bk with a very strange license? better close the eyes and not change. What do you think is kernel coding? Walk in the park? Do you think all those developers say, nah I better use Windows or Mac OS X, because its hard and not sexy ... pah ... BS! - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCE+FAjBz/yQjBxz8RAjgHAKDf03ccZzlYDaFcZtNyG5Do3pba0QCfQk31 R7mSvvgMI7IQ9C4/ahc0Hak= =L8t2 -END PGP SIGNATURE- - 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: [BK] upgrade will be needed
-BEGIN PGP SIGNED MESSAGE- (BHash: SHA1 (B (BOn 02/15/2005 09:19 PM, kernel wrote: (B (B> Just catching up on this thread. I guess I'm ultimately surprised that (B> the developers here don't create a system *they* like with *their* (B> knowledge and skillsets. (B> (B> With all of the complaining about BK you'd think there'd be an equal (B> alternative. (B (Bthere is no need for that. There is already one. Subversion is a more (Bthan mature VCS. Apache group is switching to it, gcc people are (Bstrongly thinking about it, and those two are _huge_ projects with tons (Bof developers, patches, trunks, etc. (B (BPerhaps its about time, that linux also switches. (B (B- -- (B[ Clemens Schwaighofer -=:~ ] (B[ TBWA\ && TEQUILA\ Japan IT Group ] (B[6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] (B[ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] (B[ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] (B-BEGIN PGP SIGNATURE- (BVersion: GnuPG v1.2.6 (GNU/Linux) (BComment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org (B (BiD8DBQFCExY2jBz/yQjBxz8RAlHAAJ9TqcN1ry1PYkZOqc5NF4JiVjbivwCgi79W (B6W1JMuOsX5hGvKFI3vL+NGU= (B=NM1T (B-END PGP SIGNATURE- (B- (BTo unsubscribe from this list: send the line "unsubscribe linux-kernel" in (Bthe body of a message to [EMAIL PROTECTED] (BMore majordomo info at http://vger.kernel.org/majordomo-info.html (BPlease read the FAQ at http://www.tux.org/lkml/
Re: [BK] upgrade will be needed
-BEGIN PGP SIGNED MESSAGE- (BHash: SHA1 (B (BOn 02/15/2005 09:19 PM, kernel wrote: (B (B Just catching up on this thread. I guess I'm ultimately surprised that (B the developers here don't create a system *they* like with *their* (B knowledge and skillsets. (B (B With all of the complaining about BK you'd think there'd be an equal (B alternative. (B (Bthere is no need for that. There is already one. Subversion is a more (Bthan mature VCS. Apache group is switching to it, gcc people are (Bstrongly thinking about it, and those two are _huge_ projects with tons (Bof developers, patches, trunks, etc. (B (BPerhaps its about time, that linux also switches. (B (B- -- (B[ Clemens Schwaighofer -=:~ ] (B[ TBWA\ TEQUILA\ Japan IT Group ] (B[6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] (B[ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] (B[ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] (B-BEGIN PGP SIGNATURE- (BVersion: GnuPG v1.2.6 (GNU/Linux) (BComment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org (B (BiD8DBQFCExY2jBz/yQjBxz8RAlHAAJ9TqcN1ry1PYkZOqc5NF4JiVjbivwCgi79W (B6W1JMuOsX5hGvKFI3vL+NGU= (B=NM1T (B-END PGP SIGNATURE- (B- (BTo unsubscribe from this list: send the line "unsubscribe linux-kernel" in (Bthe body of a message to [EMAIL PROTECTED] (BMore majordomo info at http://vger.kernel.org/majordomo-info.html (BPlease read the FAQ at http://www.tux.org/lkml/
Re: [BK] upgrade will be needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/2005 12:43 AM, Olivier Galibert wrote: Perhaps its about time, that linux also switches. Think what you want of Larry, but SVN is nowhere near BK is term of capabilities (and neither is arch for he matter). It's only better compared to cvs, and then not by that much. first. what kind of advantages does bk have over other svn? Seriously. If Apache can use it, and gcc might use it (again two very large projects), what makes linux so differetnt that it can't. And I don't want _anything_ from Larry. I am just pointing out, that this kind of legal clause is more ridicolous than understandable. Last, why can you compare cvs to bk? and not subversion, or arch? arch and subversion are way superiour to cvs ... SCM is hard and not sexy, I'm afraid. yes its hard, so we have to use bk with a very strange license? better close the eyes and not change. What do you think is kernel coding? Walk in the park? Do you think all those developers say, nah I better use Windows or Mac OS X, because its hard and not sexy ... pah ... BS! - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCE+FAjBz/yQjBxz8RAjgHAKDf03ccZzlYDaFcZtNyG5Do3pba0QCfQk31 R7mSvvgMI7IQ9C4/ahc0Hak= =L8t2 -END PGP SIGNATURE- - 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: [BK] upgrade will be needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/2005 12:39 AM, d.c wrote: El Wed, 16 Feb 2005 18:45:27 +0900, Clemens Schwaighofer [EMAIL PROTECTED] escribió: than mature VCS. Apache group is switching to it, gcc people are strongly thinking about it, and those two are _huge_ projects with tons of developers, patches, trunks, etc. and all of them work today with CVS, so any SCM will fit their purposes. so, your point it is, because linux used none before, none than bk fit? - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCE+HpjBz/yQjBxz8RAr8lAJ4w6TK0c7H1fjs178Y9Q0Mr4hdGBgCg32cT LUSf7DWy++w+cczaHpeEnIs= =zRM5 -END PGP SIGNATURE- - 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.11-rc3-mm1: two oops on startup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/09/2005 03:09 PM, Andrew Morton wrote: > Clemens Schwaighofer <[EMAIL PROTECTED]> wrote: > >>during startup I get too oops on my Box > > > Yes, it is being worked on. You'll need to CONFIG_INOTIFY=n, thanks. okay, thanks. - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCCapCjBz/yQjBxz8RAmcKAJ4oYmg9aLy07R7bXfOVjRza+9N9FACgty/B LiRsNye+unxwpJXzc/PYyTw= =HP/o -END PGP SIGNATURE- - 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.11-rc3-mm1: two oops on startup
Hi, during startup I get too oops on my Box. It's a debian/unstable. dmesg from right after the start and the kernel config are attached. -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] # # Automatically generated make config: don't edit # Linux kernel version: 2.6.11-rc3-mm1 # Wed Feb 9 12:39:10 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=y CONFIG_SYSCTL=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_BASE_FULL=y CONFIG_BASE_SMALL=0 CONFIG_FUTEX=y CONFIG_EPOLL=y 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 is not set CONFIG_MODULE_SRCVERSION_ALL=y 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=y # 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=7 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=y CONFIG_HPET_EMULATE_RTC=y # CONFIG_SMP is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_TSC=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_NONFATAL is not set # 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 is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set CONFIG_MATH_EMULATION=y CONFIG_MTRR=y # CONFIG_EFI is not set CONFIG_HAVE_DEC_LOCK=y CONFIG_REGPARM=y # # Performance-monitoring counters support # CONFIG_PERFCTR=y CONFIG_PERFCTR_INIT_TESTS=y CONFIG_PERFCTR_VIRTUAL=y CONFIG_PERFCTR_INTERRUPT_SUPPORT=y CONFIG_PHYSICAL_START=0x10 # CONFIG_KEXEC is not set # # Power management options (ACPI, APM) # CONFIG_PM=y # CONFIG_PM_DEBUG is not set CONFIG_SOFTWARE_SUSPEND=y CONFIG_PM_STD_PARTITION="/dev/hda2" # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=y CONFIG_ACPI_FAN=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_IBM is not set # CONFIG_ACPI_TOSHIBA is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y # CONFIG_X86_PM_TIMER is not set # CONFIG_ACPI_CONTAINER is not set # # APM (Advanced Power Management) BIOS Support # CONFIG_APM=y # CONFIG_APM_IGNORE_USER_SUSPEND is not set # CONFIG_APM_DO_ENABLE is not set CONFIG_APM_CPU_IDLE=y # CONFIG_APM_DISPLAY_BLANK is not set CONFIG_APM_RTC_IS_GMT=y # CONFIG_APM_ALLOW_INTS is not set # CONFIG_APM_REAL_MODE_POWER_OFF is not set # # 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_P
again cifs oops in 2.6.8.1
pheral: Compaq Computer Corporation Integrated (BLights Out Processor (rev 01) (B:00:0f.0 ISA bridge: ServerWorks CSB5 South Bridge (rev 93) (B:00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 93) (B:00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (B(rev 05) (B:00:0f.3 Host bridge: ServerWorks CSB5 LPC bridge (B:00:10.0 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05) (B:00:10.2 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05) (B:00:11.0 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05) (B:00:11.2 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05) (B:01:03.0 RAID bus controller: Compaq Computer Corporation Smart (BArray 5i/532 (rev 01) (B:02:01.0 Ethernet controller: Broadcom Corporation NetXtreme (BBCM5703X Gigabit Ethernet (rev 02) (B:02:02.0 Ethernet controller: Broadcom Corporation NetXtreme (BBCM5703X Gigabit Ethernet (rev 02) (B:03:01.0 RAID bus controller: Compaq Computer Corporation Smart (BArray 64xx (rev 01) (B:06:02.0 SCSI storage controller: Adaptec ASC-29320LP U320 (rev 03) (B:06:1e.0 PCI Hot-plug controller: Compaq Computer Corporation PCI (BHotplug Controller (rev 14) (B (Bramen:~# gcc -v (BReading specs from /usr/lib/gcc-lib/i486-linux/3.3.5/specs (BConfigured with: ../src/configure -v (B- --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr (B- --mandir=/usr/share/man --infodir=/usr/share/info (B- --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared (B- --with-system-zlib --enable-nls --without-included-gettext (B- --enable-__cxa_atexit --enable-clocale=gnu --enable-debug (B- --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux (BThread model: posix (Bgcc version 3.3.5 (Debian 1:3.3.5-5) (B (BI have an external SW Raid5 with XFS shared as NFS, samba and appletalk, (Band internal HW RAID5 also XFS shared as NFS< samba and appletalk. (B (Bthere is one external FS mounted via NFS and one via CIFS. (B (Bthe CPU is a Xeon with HT enabled and SMP is compiled into the kernel (B(for HT) (B (B- -- (B[ Clemens Schwaighofer -=:~ ] (B[ TBWA\ && TEQUILA\ Japan IT Group ] (B[6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] (B[ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] (B[ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] (B-BEGIN PGP SIGNATURE- (BVersion: GnuPG v1.2.6 (GNU/Linux) (BComment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org (B (BiD8DBQFCCYF3jBz/yQjBxz8RAqraAKCMScAmtC4au14WAw2F7q46N0b7OwCeI40Z (BrZPO8ZArJ7E9pq4/HqlLBqY= (B=847T (B-END PGP SIGNATURE- (B- (BTo unsubscribe from this list: send the line "unsubscribe linux-kernel" in (Bthe body of a message to [EMAIL PROTECTED] (BMore majordomo info at http://vger.kernel.org/majordomo-info.html (BPlease read the FAQ at http://www.tux.org/lkml/
again cifs oops in 2.6.8.1
: Compaq Computer Corporation Integrated (BLights Out Processor (rev 01) (B:00:0f.0 ISA bridge: ServerWorks CSB5 South Bridge (rev 93) (B:00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 93) (B:00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (B(rev 05) (B:00:0f.3 Host bridge: ServerWorks CSB5 LPC bridge (B:00:10.0 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05) (B:00:10.2 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05) (B:00:11.0 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05) (B:00:11.2 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05) (B:01:03.0 RAID bus controller: Compaq Computer Corporation Smart (BArray 5i/532 (rev 01) (B:02:01.0 Ethernet controller: Broadcom Corporation NetXtreme (BBCM5703X Gigabit Ethernet (rev 02) (B:02:02.0 Ethernet controller: Broadcom Corporation NetXtreme (BBCM5703X Gigabit Ethernet (rev 02) (B:03:01.0 RAID bus controller: Compaq Computer Corporation Smart (BArray 64xx (rev 01) (B:06:02.0 SCSI storage controller: Adaptec ASC-29320LP U320 (rev 03) (B:06:1e.0 PCI Hot-plug controller: Compaq Computer Corporation PCI (BHotplug Controller (rev 14) (B (Bramen:~# gcc -v (BReading specs from /usr/lib/gcc-lib/i486-linux/3.3.5/specs (BConfigured with: ../src/configure -v (B- --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr (B- --mandir=/usr/share/man --infodir=/usr/share/info (B- --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared (B- --with-system-zlib --enable-nls --without-included-gettext (B- --enable-__cxa_atexit --enable-clocale=gnu --enable-debug (B- --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux (BThread model: posix (Bgcc version 3.3.5 (Debian 1:3.3.5-5) (B (BI have an external SW Raid5 with XFS shared as NFS, samba and appletalk, (Band internal HW RAID5 also XFS shared as NFS samba and appletalk. (B (Bthere is one external FS mounted via NFS and one via CIFS. (B (Bthe CPU is a Xeon with HT enabled and SMP is compiled into the kernel (B(for HT) (B (B- -- (B[ Clemens Schwaighofer -=:~ ] (B[ TBWA\ TEQUILA\ Japan IT Group ] (B[6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] (B[ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] (B[ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] (B-BEGIN PGP SIGNATURE- (BVersion: GnuPG v1.2.6 (GNU/Linux) (BComment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org (B (BiD8DBQFCCYF3jBz/yQjBxz8RAqraAKCMScAmtC4au14WAw2F7q46N0b7OwCeI40Z (BrZPO8ZArJ7E9pq4/HqlLBqY= (B=847T (B-END PGP SIGNATURE- (B- (BTo unsubscribe from this list: send the line "unsubscribe linux-kernel" in (Bthe body of a message to [EMAIL PROTECTED] (BMore majordomo info at http://vger.kernel.org/majordomo-info.html (BPlease read the FAQ at http://www.tux.org/lkml/
Re: 2.6.11-rc3-mm1: two oops on startup
Hi, during startup I get too oops on my Box. It's a debian/unstable. dmesg from right after the start and the kernel config are attached. -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] # # Automatically generated make config: don't edit # Linux kernel version: 2.6.11-rc3-mm1 # Wed Feb 9 12:39:10 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=y CONFIG_SYSCTL=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_BASE_FULL=y CONFIG_BASE_SMALL=0 CONFIG_FUTEX=y CONFIG_EPOLL=y 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 is not set CONFIG_MODULE_SRCVERSION_ALL=y 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=y # 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=7 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=y CONFIG_HPET_EMULATE_RTC=y # CONFIG_SMP is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_TSC=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_NONFATAL is not set # 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 is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set CONFIG_MATH_EMULATION=y CONFIG_MTRR=y # CONFIG_EFI is not set CONFIG_HAVE_DEC_LOCK=y CONFIG_REGPARM=y # # Performance-monitoring counters support # CONFIG_PERFCTR=y CONFIG_PERFCTR_INIT_TESTS=y CONFIG_PERFCTR_VIRTUAL=y CONFIG_PERFCTR_INTERRUPT_SUPPORT=y CONFIG_PHYSICAL_START=0x10 # CONFIG_KEXEC is not set # # Power management options (ACPI, APM) # CONFIG_PM=y # CONFIG_PM_DEBUG is not set CONFIG_SOFTWARE_SUSPEND=y CONFIG_PM_STD_PARTITION=/dev/hda2 # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=y CONFIG_ACPI_FAN=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_IBM is not set # CONFIG_ACPI_TOSHIBA is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y # CONFIG_X86_PM_TIMER is not set # CONFIG_ACPI_CONTAINER is not set # # APM (Advanced Power Management) BIOS Support # CONFIG_APM=y # CONFIG_APM_IGNORE_USER_SUSPEND is not set # CONFIG_APM_DO_ENABLE is not set CONFIG_APM_CPU_IDLE=y # CONFIG_APM_DISPLAY_BLANK is not set CONFIG_APM_RTC_IS_GMT=y # CONFIG_APM_ALLOW_INTS is not set # CONFIG_APM_REAL_MODE_POWER_OFF is not set # # 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
Re: 2.6.11-rc3-mm1: two oops on startup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/09/2005 03:09 PM, Andrew Morton wrote: Clemens Schwaighofer [EMAIL PROTECTED] wrote: during startup I get too oops on my Box Yes, it is being worked on. You'll need to CONFIG_INOTIFY=n, thanks. okay, thanks. - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCCapCjBz/yQjBxz8RAmcKAJ4oYmg9aLy07R7bXfOVjRza+9N9FACgty/B LiRsNye+unxwpJXzc/PYyTw= =HP/o -END PGP SIGNATURE- - 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: [PATCH] Re: msdos/vfat defaults are annoying
-BEGIN PGP SIGNED MESSAGE- (BHash: SHA1 (B (BOn 02/08/2005 09:23 AM, Horst von Brand wrote: (B> Clemens Schwaighofer <[EMAIL PROTECTED]> said: (B> (B> [...] (B>>but to be honest, most times I need vfat, and I actually haven't (B>>encountered a time when I need msdos. (B> (B> But writing MSDOS on a VFAT filesystem is a sure way to screw it up, and (B> AFAIU vice-versa. (B (Bwell it doesn't screw it up if you write MS DOS on a VFAT, you just (Bloose a lot of data. (B (BI was kinda surprised when I came home and plugged in my USB stick to (Bsee just A3.CB instead of a nice long filename :) (B (B- -- (B[ Clemens Schwaighofer -=:~ ] (B[ TBWA\ && TEQUILA\ Japan IT Group ] (B[6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] (B[ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] (B[ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] (B-BEGIN PGP SIGNATURE- (BVersion: GnuPG v1.2.6 (GNU/Linux) (BComment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org (B (BiD8DBQFCCCLljBz/yQjBxz8RAvgyAJ4zRyjszLLuBeZz5lBAyegCTbm1ygCfYf2E (BUJKEEU0HJuLRTAjec3aEQ3s= (B=g+L4 (B-END PGP SIGNATURE- (B- (BTo unsubscribe from this list: send the line "unsubscribe linux-kernel" in (Bthe body of a message to [EMAIL PROTECTED] (BMore majordomo info at http://vger.kernel.org/majordomo-info.html (BPlease read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Re: msdos/vfat defaults are annoying
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07.02.2005 20:29, Andries Brouwer wrote: > Making a symlink /etc/filesystems -> /proc/filesystems is > meaningless. well to be honest, I didn't even know Gentoo makes a symlink here, but I'll definitly will make bug entry for that. Perhaps its a default setting. eg Debian doesn't have a /etc/filesystems file by defauly anyway. > It is not true that vfat is universally better than msdos. > Some need one, some need the other. but to be honest, most times I need vfat, and I actually haven't encountered a time when I need msdos. lg, clemens -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD4DBQFCB3RpjBz/yQjBxz8RAlQBAJjj0IIhxCPWvWinMpi6J5UOJ9bBAJ9oQnI4 A6sIi+MzKiFbvpLIiQI1YQ== =rmlN -END PGP SIGNATURE- - 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: oops in 2.6.8.1
-BEGIN PGP SIGNED MESSAGE- (BHash: SHA1 (B (BOn 02/07/2005 06:50 PM, Clemens Schwaighofer wrote: (B> hi, (B> (B> today, just 30min ago I found this in my messages file: (B> (B> The box is a Debian/Testing with a self compiled 2.6.8.1 (B (BI forgot one thing: (B (Bthe CPU is a Xeon with HT enabled and SMP is compiled into the kernel (B(for HT). (B (B- -- (B[ Clemens Schwaighofer -=:~ ] (B[ TBWA\ && TEQUILA\ Japan IT Group ] (B[6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] (B[ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] (B[ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] (B-BEGIN PGP SIGNATURE- (BVersion: GnuPG v1.2.6 (GNU/Linux) (BComment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org (B (BiD8DBQFCBztxjBz/yQjBxz8RAuSzAKCZiKutel4PLBdRTxmls2EBw4j9yQCaAu8v (B54MXuqpugC5a4u6N9tk28jI= (B=zHY+ (B-END PGP SIGNATURE- (B- (BTo unsubscribe from this list: send the line "unsubscribe linux-kernel" in (Bthe body of a message to [EMAIL PROTECTED] (BMore majordomo info at http://vger.kernel.org/majordomo-info.html (BPlease read the FAQ at http://www.tux.org/lkml/
oops in 2.6.8.1
FS: Error unlocking previously locked range -5 during test of lock (B CIFS VFS: Error unlocking previously locked range -5 during test of lock (B (B (B- -- (B[ Clemens Schwaighofer -=:~ ] (B[ TBWA\ && TEQUILA\ Japan IT Group ] (B[6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] (B[ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] (B[ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] (B-BEGIN PGP SIGNATURE- (BVersion: GnuPG v1.2.6 (GNU/Linux) (BComment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org (B (BiD8DBQFCBznnjBz/yQjBxz8RAoGEAKCyuIrRwWib13rd2+Iv4GLqU/4WmACgqNct (BGuU5sGARIIyy23kFChrh7IE= (B=IOhj (B-END PGP SIGNATURE- (B- (BTo unsubscribe from this list: send the line "unsubscribe linux-kernel" in (Bthe body of a message to [EMAIL PROTECTED] (BMore majordomo info at http://vger.kernel.org/majordomo-info.html (BPlease read the FAQ at http://www.tux.org/lkml/
oops in 2.6.8.1
0xffec or on cifs_get_inode_info in lookup (B CIFS VFS: Error unlocking previously locked range -5 during test of lock (B CIFS VFS: Error unlocking previously locked range -5 during test of lock (B (B (B- -- (B[ Clemens Schwaighofer -=:~ ] (B[ TBWA\ TEQUILA\ Japan IT Group ] (B[6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] (B[ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] (B[ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] (B-BEGIN PGP SIGNATURE- (BVersion: GnuPG v1.2.6 (GNU/Linux) (BComment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org (B (BiD8DBQFCBznnjBz/yQjBxz8RAoGEAKCyuIrRwWib13rd2+Iv4GLqU/4WmACgqNct (BGuU5sGARIIyy23kFChrh7IE= (B=IOhj (B-END PGP SIGNATURE- (B- (BTo unsubscribe from this list: send the line "unsubscribe linux-kernel" in (Bthe body of a message to [EMAIL PROTECTED] (BMore majordomo info at http://vger.kernel.org/majordomo-info.html (BPlease read the FAQ at http://www.tux.org/lkml/
Re: oops in 2.6.8.1
-BEGIN PGP SIGNED MESSAGE- (BHash: SHA1 (B (BOn 02/07/2005 06:50 PM, Clemens Schwaighofer wrote: (B hi, (B (B today, just 30min ago I found this in my messages file: (B (B The box is a Debian/Testing with a self compiled 2.6.8.1 (B (BI forgot one thing: (B (Bthe CPU is a Xeon with HT enabled and SMP is compiled into the kernel (B(for HT). (B (B- -- (B[ Clemens Schwaighofer -=:~ ] (B[ TBWA\ TEQUILA\ Japan IT Group ] (B[6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] (B[ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] (B[ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] (B-BEGIN PGP SIGNATURE- (BVersion: GnuPG v1.2.6 (GNU/Linux) (BComment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org (B (BiD8DBQFCBztxjBz/yQjBxz8RAuSzAKCZiKutel4PLBdRTxmls2EBw4j9yQCaAu8v (B54MXuqpugC5a4u6N9tk28jI= (B=zHY+ (B-END PGP SIGNATURE- (B- (BTo unsubscribe from this list: send the line "unsubscribe linux-kernel" in (Bthe body of a message to [EMAIL PROTECTED] (BMore majordomo info at http://vger.kernel.org/majordomo-info.html (BPlease read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Re: msdos/vfat defaults are annoying
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07.02.2005 20:29, Andries Brouwer wrote: Making a symlink /etc/filesystems - /proc/filesystems is meaningless. well to be honest, I didn't even know Gentoo makes a symlink here, but I'll definitly will make bug entry for that. Perhaps its a default setting. eg Debian doesn't have a /etc/filesystems file by defauly anyway. It is not true that vfat is universally better than msdos. Some need one, some need the other. but to be honest, most times I need vfat, and I actually haven't encountered a time when I need msdos. lg, clemens -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD4DBQFCB3RpjBz/yQjBxz8RAlQBAJjj0IIhxCPWvWinMpi6J5UOJ9bBAJ9oQnI4 A6sIi+MzKiFbvpLIiQI1YQ== =rmlN -END PGP SIGNATURE- - 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: [PATCH] Re: msdos/vfat defaults are annoying
-BEGIN PGP SIGNED MESSAGE- (BHash: SHA1 (B (BOn 02/08/2005 09:23 AM, Horst von Brand wrote: (B Clemens Schwaighofer [EMAIL PROTECTED] said: (B (B [...] (Bbut to be honest, most times I need vfat, and I actually haven't (Bencountered a time when I need msdos. (B (B But writing MSDOS on a VFAT filesystem is a sure way to screw it up, and (B AFAIU vice-versa. (B (Bwell it doesn't screw it up if you write MS DOS on a VFAT, you just (Bloose a lot of data. (B (BI was kinda surprised when I came home and plugged in my USB stick to (Bsee just A3.CB instead of a nice long filename :) (B (B- -- (B[ Clemens Schwaighofer -=:~ ] (B[ TBWA\ TEQUILA\ Japan IT Group ] (B[6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] (B[ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] (B[ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] (B-BEGIN PGP SIGNATURE- (BVersion: GnuPG v1.2.6 (GNU/Linux) (BComment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org (B (BiD8DBQFCCCLljBz/yQjBxz8RAvgyAJ4zRyjszLLuBeZz5lBAyegCTbm1ygCfYf2E (BUJKEEU0HJuLRTAjec3aEQ3s= (B=g+L4 (B-END PGP SIGNATURE- (B- (BTo unsubscribe from this list: send the line "unsubscribe linux-kernel" in (Bthe body of a message to [EMAIL PROTECTED] (BMore majordomo info at http://vger.kernel.org/majordomo-info.html (BPlease read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Re: msdos/vfat defaults are annoying
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/07/2005 09:36 AM, Al Viro wrote: > On Mon, Feb 07, 2005 at 12:21:08AM +0100, Pozsar Balazs wrote: > >>On Sun, Feb 06, 2005 at 07:06:59AM +, Christoph Hellwig wrote: >> >>>On Sun, Feb 06, 2005 at 12:33:43AM -0500, John Richard Moser wrote: >>> >>>>I dunno. I can never understand the innards of the kernel devs' minds. >>> >>>filesystem detection isn't handled at the kerne level. >> >>Yeah, but the link order could be changed... Patch inlined. > > > And just what does the link order (or changes thereof) have to do with that? because some distributions (eg gentoo) make a symlink to /proc/filesystems jupiter root # ls -l /etc/filesystems lrwxrwxrwx 1 root root 19 Oct 25 11:18 /etc/filesystems -> ../proc/filesystems and then its impossible to change the order. (unless you make a "hand made" file of course). - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCBxBLjBz/yQjBxz8RAsCXAKCHwURn6UJjrtEOhjaXHa0min94NQCdFlBa EgBrVpGuASFNepZigjV1p5E= =ol2B -END PGP SIGNATURE- - 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: [PATCH] Re: msdos/vfat defaults are annoying
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/07/2005 09:36 AM, Al Viro wrote: On Mon, Feb 07, 2005 at 12:21:08AM +0100, Pozsar Balazs wrote: On Sun, Feb 06, 2005 at 07:06:59AM +, Christoph Hellwig wrote: On Sun, Feb 06, 2005 at 12:33:43AM -0500, John Richard Moser wrote: I dunno. I can never understand the innards of the kernel devs' minds. filesystem detection isn't handled at the kerne level. Yeah, but the link order could be changed... Patch inlined. And just what does the link order (or changes thereof) have to do with that? because some distributions (eg gentoo) make a symlink to /proc/filesystems jupiter root # ls -l /etc/filesystems lrwxrwxrwx 1 root root 19 Oct 25 11:18 /etc/filesystems - ../proc/filesystems and then its impossible to change the order. (unless you make a hand made file of course). - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCBxBLjBz/yQjBxz8RAsCXAKCHwURn6UJjrtEOhjaXHa0min94NQCdFlBa EgBrVpGuASFNepZigjV1p5E= =ol2B -END PGP SIGNATURE- - 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: kernel panic on a 2.6.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/31/2005 04:24 PM, Felipe Alfaro Solana wrote: > On 31 Jan 2005, at 02:51, Clemens Schwaighofer wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi, >> >> I have a RedHat 9.0 box with a self compiled 2.6.7 kernel. >> >> Today I had this error and a total lockup on the box. Before that (~6h >> before I had another lockup, but no output to anywhere). > > > Have you tried with a more recent kernel? 2.6.7 is a little bit ancient. well, I had a 2.6.9, but I had a lot of lock ups, only 2.6.7 ran more stable. But I might try 2.6.10, and see if I have ~1 month again a lock up - -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB/d3TjBz/yQjBxz8RAtyDAJsEPF4GyrX23oerx/X9M7TcVEbMhQCdFdtA tmTmgbIi0J9Yx/JisCdzKGA= =dREk -END PGP SIGNATURE- - 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/
kernel panic on a 2.6.7
kernel: [] kjournald+0x0/0x220 (BJan 31 10:30:25 soba kernel: [] kernel_thread_helper+0x5/0x10 (BJan 31 10:30:25 soba kernel: (BJan 31 10:30:25 soba kernel: Code: 0f a3 91 04 01 00 00 19 c0 85 c0 75 (B0a 0f ab 91 04 01 00 00 (B (Bgcc, library files are all still from redhat 9, but there are a lot of (Bextra things compiled by hand or from fedora core libraries. (B (B- -- (B[ Clemens Schwaighofer -=:~ ] (B[ TBWA\ && TEQUILA\ Japan IT Group ] (B[6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] (B[ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] (B[ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] (B-BEGIN PGP SIGNATURE- (BVersion: GnuPG v1.2.6 (GNU/Linux) (BComment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org (B (BiD8DBQFB/Y8IjBz/yQjBxz8RArO7AKDXpJ9FQ8VQFV1Bunz1rlqdsWa3yACfVVuA (BFNeuo+2A+5ZHdkD2KE1ly3Q= (B=rBmN (B-END PGP SIGNATURE- (B- (BTo unsubscribe from this list: send the line "unsubscribe linux-kernel" in (Bthe body of a message to [EMAIL PROTECTED] (BMore majordomo info at http://vger.kernel.org/majordomo-info.html (BPlease read the FAQ at http://www.tux.org/lkml/
