* 2.6.17-rc1 did break XFS
@ 2006-04-13 5:21 Herbert Poetzl
2006-04-13 5:35 ` Nathan Scott
2006-04-13 7:23 ` notifier chain problem? (was Re: 2.6.17-rc1 did break XFS) David Chinner
0 siblings, 2 replies; 17+ messages in thread
From: Herbert Poetzl @ 2006-04-13 5:21 UTC (permalink / raw)
To: Linux Kernel ML, linux-xfs, xfs-masters
# grep XFS .config
CONFIG_XFS_FS=y
CONFIG_XFS_EXPORT=y
CONFIG_XFS_QUOTA=y
# CONFIG_XFS_SECURITY is not set
# CONFIG_XFS_POSIX_ACL is not set
# CONFIG_XFS_RT is not set
if you need more information, please let me know ...
best,
Herbert
[ 39.585041] BUG: unable to handle kernel paging request at virtual address 7856c380
[ 39.586688] printing eip:
[ 39.587040] 78129430
[ 39.587354] *pde = 005bf027
[ 39.587709] *pte = 0056c000
[ 39.588201] Oops: 0000 [#1]
[ 39.588536] SMP DEBUG_PAGEALLOC
[ 39.589057] Modules linked in:
[ 39.589639] CPU: 0
[ 39.589670] EIP: 0060:[<78129430>] Not tainted VLI
[ 39.589710] EFLAGS: 00000206 (2.6.17-rc1 #1)
[ 39.591291] EIP is at notifier_chain_register+0x20/0x50
[ 39.591890] eax: 7856c378 ebx: 878db3f8 ecx: 00000000 edx: 784bf9bc
[ 39.592601] esi: 878db3f8 edi: 878e7c00 ebp: 878db800 esp: 878cad5c
[ 39.593399] ds: 007b es: 007b ss: 0068
[ 39.593896] Process mount (pid: 50, threadinfo=878ca000 task=87f7e570)
[ 39.594530] Stack: <0>784bf9a0 781295f4 784bf9bc 878db3f8 878db000 878db000 78136997 784bf9a0
[ 39.595839] 878db3f8 782d43e6 878db3f8 00000404 878db000 87d1e6a0 878e7c00 782d1813
[ 39.597002] 878db000 00000001 782e5eaf 00000424 00000001 878e7c00 87d1e6a0 782f2150
[ 39.598164] Call Trace:
[ 39.598592] <781295f4> blocking_notifier_chain_register+0x54/0x90 <78136997> register_cpu_notifier+0x17/0x20
[ 39.600024] <782d43e6> xfs_icsb_init_counters+0x46/0xb0 <782d1813> xfs_mount_init+0x23/0x160
[ 39.601199] <782e5eaf> kmem_zalloc+0x1f/0x50 <782f2150> bhv_insert_all_vfsops+0x10/0x50
[ 39.602315] <782f1835> xfs_fs_fill_super+0x35/0x1f0 <78313607> snprintf+0x27/0x30
[ 39.603437] <781a2134> disk_name+0x64/0xc0 <78168fbf> sb_set_blocksize+0x1f/0x50
[ 39.604524] <78168909> get_sb_bdev+0x109/0x160 <781445ef> __alloc_pages+0x5f/0x370
[ 39.605612] <782f1a20> xfs_fs_get_sb+0x30/0x40 <782f1800> xfs_fs_fill_super+0x0/0x1f0
[ 39.606698] <78168bb0> do_kern_mount+0xa0/0x160 <78181467> do_new_mount+0x77/0xc0
[ 39.607764] <78181b2f> do_mount+0x1bf/0x220 <783f4178> iret_exc+0x3d4/0x6ab
[ 39.608790] <78181913> copy_mount_options+0x63/0xc0 <783f398f> lock_kernel+0x2f/0x50
[ 39.609867] <78181f2f> sys_mount+0x9f/0xe0 <78102b27> syscall_call+0x7/0xb
[ 39.610923] Code: 90 90 90 90 90 90 90 90 90 90 90 53 8b 54 24 08 8b 5c 24 0c 8b 02 85 c0 74 31 8b 4b 08 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 <3b> 48 08 7f 1b 8d 50 04 8b 40 04 85 c0 75 f1 31 c0 eb 0d 90 90
[ 39.615306] <3>BUG: sleeping function called from invalid context at include/linux/rwsem.h:43
[ 39.616413] in_atomic():0, irqs_disabled():1
[ 39.616918] <781189f4> __might_sleep+0xa4/0xb0 <7811de7a> exit_mm+0x3a/0x170
[ 39.617953] <7811e74c> do_exit+0xfc/0x420 <7811c217> printk+0x17/0x20
[ 39.618902] <78103ef7> die+0x1e7/0x1f0 <78112b34> do_page_fault+0x334/0x690
[ 39.619988] <7815c407> cache_grow+0x157/0x1a0 <78112800> do_page_fault+0x0/0x690
[ 39.621106] <78103627> error_code+0x4f/0x54 <78129430> notifier_chain_register+0x20/0x50
[ 39.622317] <781295f4> blocking_notifier_chain_register+0x54/0x90 <78136997> register_cpu_notifier+0x17/0x20
[ 39.623764] <782d43e6> xfs_icsb_init_counters+0x46/0xb0 <782d1813> xfs_mount_init+0x23/0x160
[ 39.625010] <782e5eaf> kmem_zalloc+0x1f/0x50 <782f2150> bhv_insert_all_vfsops+0x10/0x50
[ 39.626207] <782f1835> xfs_fs_fill_super+0x35/0x1f0 <78313607> snprintf+0x27/0x30
[ 39.627354] <781a2134> disk_name+0x64/0xc0 <78168fbf> sb_set_blocksize+0x1f/0x50
[ 39.628486] <78168909> get_sb_bdev+0x109/0x160 <781445ef> __alloc_pages+0x5f/0x370
[ 39.629634] <782f1a20> xfs_fs_get_sb+0x30/0x40 <782f1800> xfs_fs_fill_super+0x0/0x1f0
[ 39.630799] <78168bb0> do_kern_mount+0xa0/0x160 <78181467> do_new_mount+0x77/0xc0
[ 39.631939] <78181b2f> do_mount+0x1bf/0x220 <783f4178> iret_exc+0x3d4/0x6ab
[ 39.633023] <78181913> copy_mount_options+0x63/0xc0 <783f398f> lock_kernel+0x2f/0x50
[ 39.634154] <78181f2f> sys_mount+0x9f/0xe0 <78102b27> syscall_call+0x7/0xb
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: 2.6.17-rc1 did break XFS
2006-04-13 5:21 2.6.17-rc1 did break XFS Herbert Poetzl
@ 2006-04-13 5:35 ` Nathan Scott
2006-04-13 9:23 ` Keith Owens
2006-04-13 9:36 ` Keith Owens
2006-04-13 7:23 ` notifier chain problem? (was Re: 2.6.17-rc1 did break XFS) David Chinner
1 sibling, 2 replies; 17+ messages in thread
From: Nathan Scott @ 2006-04-13 5:35 UTC (permalink / raw)
To: dgc; +Cc: Linux Kernel ML, linux-xfs, xfs-masters
On Thu, Apr 13, 2006 at 07:21:45AM +0200, Herbert Poetzl wrote:
> [ 39.585041] BUG: unable to handle kernel paging request at virtual address 7856c380
> [ 39.586688] printing eip:
> [ 39.587040] 78129430
> [ 39.587354] *pde = 005bf027
> [ 39.587709] *pte = 0056c000
> [ 39.588201] Oops: 0000 [#1]
> [ 39.588536] SMP DEBUG_PAGEALLOC
> [ 39.589057] Modules linked in:
> [ 39.589639] CPU: 0
> [ 39.589670] EIP: 0060:[<78129430>] Not tainted VLI
> [ 39.589710] EFLAGS: 00000206 (2.6.17-rc1 #1)
> [ 39.591291] EIP is at notifier_chain_register+0x20/0x50
> [ 39.591890] eax: 7856c378 ebx: 878db3f8 ecx: 00000000 edx: 784bf9bc
> [ 39.592601] esi: 878db3f8 edi: 878e7c00 ebp: 878db800 esp: 878cad5c
> [ 39.593399] ds: 007b es: 007b ss: 0068
> [ 39.593896] Process mount (pid: 50, threadinfo=878ca000 task=87f7e570)
> [ 39.594530] Stack: <0>784bf9a0 781295f4 784bf9bc 878db3f8 878db000 878db000 78136997 784bf9a0
> [ 39.595839] 878db3f8 782d43e6 878db3f8 00000404 878db000 87d1e6a0 878e7c00 782d1813
> [ 39.597002] 878db000 00000001 782e5eaf 00000424 00000001 878e7c00 87d1e6a0 782f2150
> [ 39.598164] Call Trace:
> [ 39.598592] <781295f4> blocking_notifier_chain_register+0x54/0x90 <78136997> register_cpu_notifier+0x17/0x20
> [ 39.600024] <782d43e6> xfs_icsb_init_counters+0x46/0xb0 <782d1813> xfs_mount_init+0x23/0x160
> [ 39.601199] <782e5eaf> kmem_zalloc+0x1f/0x50 <782f2150> bhv_insert_all_vfsops+0x10/0x50
> [ 39.602315] <782f1835> xfs_fs_fill_super+0x35/0x1f0 <78313607> snprintf+0x27/0x30
> [ 39.603437] <781a2134> disk_name+0x64/0xc0 <78168fbf> sb_set_blocksize+0x1f/0x50
> [ 39.604524] <78168909> get_sb_bdev+0x109/0x160 <781445ef> __alloc_pages+0x5f/0x370
> [ 39.605612] <782f1a20> xfs_fs_get_sb+0x30/0x40 <782f1800> xfs_fs_fill_super+0x0/0x1f0
> [ 39.606698] <78168bb0> do_kern_mount+0xa0/0x160 <78181467> do_new_mount+0x77/0xc0
> [ 39.607764] <78181b2f> do_mount+0x1bf/0x220 <783f4178> iret_exc+0x3d4/0x6ab
> [ 39.608790] <78181913> copy_mount_options+0x63/0xc0 <783f398f> lock_kernel+0x2f/0x50
> [ 39.609867] <78181f2f> sys_mount+0x9f/0xe0 <78102b27> syscall_call+0x7/0xb
> [ 39.610923] Code: 90 90 90 90 90 90 90 90 90 90 90 53 8b 54 24 08 8b 5c 24 0c 8b 02 85 c0 74 31 8b 4b 08 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 <3b> 48 08 7f 1b 8d 50 04 8b 40 04 85 c0 75 f1 31 c0 eb 0d 90 90
> [ 39.615306] <3>BUG: sleeping function called from invalid context at include/linux/rwsem.h:43
> [ 39.616413] in_atomic():0, irqs_disabled():1
> [ 39.616918] <781189f4> __might_sleep+0xa4/0xb0 <7811de7a> exit_mm+0x3a/0x170
> [ 39.617953] <7811e74c> do_exit+0xfc/0x420 <7811c217> printk+0x17/0x20
> [ 39.618902] <78103ef7> die+0x1e7/0x1f0 <78112b34> do_page_fault+0x334/0x690
> [ 39.619988] <7815c407> cache_grow+0x157/0x1a0 <78112800> do_page_fault+0x0/0x690
> [ 39.621106] <78103627> error_code+0x4f/0x54 <78129430> notifier_chain_register+0x20/0x50
> [ 39.622317] <781295f4> blocking_notifier_chain_register+0x54/0x90 <78136997> register_cpu_notifier+0x17/0x20
> [ 39.623764] <782d43e6> xfs_icsb_init_counters+0x46/0xb0 <782d1813> xfs_mount_init+0x23/0x160
> [ 39.625010] <782e5eaf> kmem_zalloc+0x1f/0x50 <782f2150> bhv_insert_all_vfsops+0x10/0x50
> [ 39.626207] <782f1835> xfs_fs_fill_super+0x35/0x1f0 <78313607> snprintf+0x27/0x30
> [ 39.627354] <781a2134> disk_name+0x64/0xc0 <78168fbf> sb_set_blocksize+0x1f/0x50
> [ 39.628486] <78168909> get_sb_bdev+0x109/0x160 <781445ef> __alloc_pages+0x5f/0x370
> [ 39.629634] <782f1a20> xfs_fs_get_sb+0x30/0x40 <782f1800> xfs_fs_fill_super+0x0/0x1f0
> [ 39.630799] <78168bb0> do_kern_mount+0xa0/0x160 <78181467> do_new_mount+0x77/0xc0
> [ 39.631939] <78181b2f> do_mount+0x1bf/0x220 <783f4178> iret_exc+0x3d4/0x6ab
> [ 39.633023] <78181913> copy_mount_options+0x63/0xc0 <783f398f> lock_kernel+0x2f/0x50
> [ 39.634154] <78181f2f> sys_mount+0x9f/0xe0 <78102b27> syscall_call+0x7/0xb
Hmm, looks like your neck of the woods Dave? You can disable
HAVE_PERCPU_SB in xfs_linux.h to get a working setup again in
the meantime, Herbert.
cheers.
--
Nathan
^ permalink raw reply [flat|nested] 17+ messages in thread
* notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
2006-04-13 5:21 2.6.17-rc1 did break XFS Herbert Poetzl
2006-04-13 5:35 ` Nathan Scott
@ 2006-04-13 7:23 ` David Chinner
2006-04-13 8:40 ` Jes Sorensen
1 sibling, 1 reply; 17+ messages in thread
From: David Chinner @ 2006-04-13 7:23 UTC (permalink / raw)
To: Linux Kernel ML, linux-xfs, xfs-masters; +Cc: jes, stern, sekharan, akpm
On Thu, Apr 13, 2006 at 07:21:45AM +0200, Herbert Poetzl wrote:
>
> # grep XFS .config
> CONFIG_XFS_FS=y
> CONFIG_XFS_EXPORT=y
> CONFIG_XFS_QUOTA=y
> # CONFIG_XFS_SECURITY is not set
> # CONFIG_XFS_POSIX_ACL is not set
> # CONFIG_XFS_RT is not set
>
> if you need more information, please let me know ...
I don't think this is an XFS bug....
> [ 39.585041] BUG: unable to handle kernel paging request at virtual address 7856c380
> [ 39.586688] printing eip:
> [ 39.587040] 78129430
> [ 39.587354] *pde = 005bf027
> [ 39.587709] *pte = 0056c000
> [ 39.588201] Oops: 0000 [#1]
> [ 39.588536] SMP DEBUG_PAGEALLOC
> [ 39.589057] Modules linked in:
> [ 39.589639] CPU: 0
> [ 39.589670] EIP: 0060:[<78129430>] Not tainted VLI
> [ 39.589710] EFLAGS: 00000206 (2.6.17-rc1 #1)
> [ 39.591291] EIP is at notifier_chain_register+0x20/0x50
> [ 39.591890] eax: 7856c378 ebx: 878db3f8 ecx: 00000000 edx: 784bf9bc
> [ 39.592601] esi: 878db3f8 edi: 878e7c00 ebp: 878db800 esp: 878cad5c
> [ 39.593399] ds: 007b es: 007b ss: 0068
> [ 39.593896] Process mount (pid: 50, threadinfo=878ca000 task=87f7e570)
> [ 39.594530] Stack: <0>784bf9a0 781295f4 784bf9bc 878db3f8 878db000 878db000 78136997 784bf9a0
> [ 39.595839] 878db3f8 782d43e6 878db3f8 00000404 878db000 87d1e6a0 878e7c00 782d1813
> [ 39.597002] 878db000 00000001 782e5eaf 00000424 00000001 878e7c00 87d1e6a0 782f2150
> [ 39.598164] Call Trace:
> [ 39.598592] <781295f4> blocking_notifier_chain_register+0x54/0x90 <78136997> register_cpu_notifier+0x17/0x20
> [ 39.600024] <782d43e6> xfs_icsb_init_counters+0x46/0xb0 <782d1813> xfs_mount_init+0x23/0x160
It looks like we landed on top of a a notifier call chain
implementation change in -rc1. However, this should not matter to
XFS because the interface to register_cpu_notifier() did not change
and XFS is completely abstracted away from the notifier chain
implementation. We do:
mp->m_icsb_notifier.notifier_call = xfs_icsb_cpu_notify;
mp->m_icsb_notifier.priority = 0;
register_cpu_notifier(&mp->m_icsb_notifier);
and the mp structure is kzalloc()d almost immediately before this. The definition
of m_icsb_notifier in the struct xfs_mount (mp) is:
struct notifier_block m_icsb_notifier; /* hotplug cpu notifier */
I can't see anything wrong with this, but maybe others can see a problem with
this.
Hence I suspect this is a bug in the new notifier call chain code. Adding a few
ppl involved in the notifier chain work to the cc list.
Cheers,
Dave.
--
Dave Chinner
R&D Software Enginner
SGI Australian Software Group
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
2006-04-13 7:23 ` notifier chain problem? (was Re: 2.6.17-rc1 did break XFS) David Chinner
@ 2006-04-13 8:40 ` Jes Sorensen
2006-04-13 13:50 ` Herbert Poetzl
0 siblings, 1 reply; 17+ messages in thread
From: Jes Sorensen @ 2006-04-13 8:40 UTC (permalink / raw)
To: Herbert Poetzl
Cc: Linux Kernel ML, linux-xfs, xfs-masters, stern, sekharan, akpm,
David Chinner
>>>>> "David" == David Chinner <dgc@sgi.com> writes:
David> On Thu, Apr 13, 2006 at 07:21:45AM +0200, Herbert Poetzl wrote:
David> It looks like we landed on top of a a notifier call chain
David> implementation change in -rc1. However, this should not matter
David> to XFS because the interface to register_cpu_notifier() did not
David> change and XFS is completely abstracted away from the notifier
David> chain implementation. We do:
Dave,
Looks strange, the faulting address is in the same region as the
eip. I am not that strong on x86 layouts, so I am not sure whether
0x78xxxxxx is the kernel's mapping or it's module space. Almost looks
like something else had registered a notifier and then gone away
without unregistering it.
Herbert, any chance you can make the complete boot log up to the point
where it crashes, as well as a System.map and your .config available?
(probably not posted to all the lists :)
Cheers,
Jes
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: 2.6.17-rc1 did break XFS
2006-04-13 5:35 ` Nathan Scott
@ 2006-04-13 9:23 ` Keith Owens
2006-04-13 14:17 ` Jan Engelhardt
2006-04-13 9:36 ` Keith Owens
1 sibling, 1 reply; 17+ messages in thread
From: Keith Owens @ 2006-04-13 9:23 UTC (permalink / raw)
To: Nathan Scott
Cc: dgc, Linux Kernel ML, linux-xfs, xfs-masters, stern, sekharan
Nathan Scott (on Thu, 13 Apr 2006 15:35:33 +1000) wrote:
>On Thu, Apr 13, 2006 at 07:21:45AM +0200, Herbert Poetzl wrote:
>> [ 39.585041] BUG: unable to handle kernel paging request at virtual address 7856c380
>> [ 39.586688] printing eip:
>> [ 39.587040] 78129430
>> [ 39.587354] *pde = 005bf027
>> [ 39.587709] *pte = 0056c000
>> [ 39.588201] Oops: 0000 [#1]
>> [ 39.588536] SMP DEBUG_PAGEALLOC
>> [ 39.589057] Modules linked in:
>> [ 39.589639] CPU: 0
>> [ 39.589670] EIP: 0060:[<78129430>] Not tainted VLI
>> [ 39.589710] EFLAGS: 00000206 (2.6.17-rc1 #1)
>> [ 39.591291] EIP is at notifier_chain_register+0x20/0x50
>> [ 39.591890] eax: 7856c378 ebx: 878db3f8 ecx: 00000000 edx: 784bf9bc
>> [ 39.592601] esi: 878db3f8 edi: 878e7c00 ebp: 878db800 esp: 878cad5c
>> [ 39.593399] ds: 007b es: 007b ss: 0068
>> [ 39.593896] Process mount (pid: 50, threadinfo=878ca000 task=87f7e570)
>> [ 39.594530] Stack: <0>784bf9a0 781295f4 784bf9bc 878db3f8 878db000 878db000 78136997 784bf9a0
>> [ 39.595839] 878db3f8 782d43e6 878db3f8 00000404 878db000 87d1e6a0 878e7c00 782d1813
>> [ 39.597002] 878db000 00000001 782e5eaf 00000424 00000001 878e7c00 87d1e6a0 782f2150
>> [ 39.598164] Call Trace:
>> [ 39.598592] <781295f4> blocking_notifier_chain_register+0x54/0x90 <78136997> register_cpu_notifier+0x17/0x20
>> [ 39.600024] <782d43e6> xfs_icsb_init_counters+0x46/0xb0 <782d1813> xfs_mount_init+0x23/0x160
>> [ 39.601199] <782e5eaf> kmem_zalloc+0x1f/0x50 <782f2150> bhv_insert_all_vfsops+0x10/0x50
>> [ 39.602315] <782f1835> xfs_fs_fill_super+0x35/0x1f0 <78313607> snprintf+0x27/0x30
>> [ 39.603437] <781a2134> disk_name+0x64/0xc0 <78168fbf> sb_set_blocksize+0x1f/0x50
>> [ 39.604524] <78168909> get_sb_bdev+0x109/0x160 <781445ef> __alloc_pages+0x5f/0x370
>> [ 39.605612] <782f1a20> xfs_fs_get_sb+0x30/0x40 <782f1800> xfs_fs_fill_super+0x0/0x1f0
>> [ 39.606698] <78168bb0> do_kern_mount+0xa0/0x160 <78181467> do_new_mount+0x77/0xc0
>> [ 39.607764] <78181b2f> do_mount+0x1bf/0x220 <783f4178> iret_exc+0x3d4/0x6ab
>> [ 39.608790] <78181913> copy_mount_options+0x63/0xc0 <783f398f> lock_kernel+0x2f/0x50
>> [ 39.609867] <78181f2f> sys_mount+0x9f/0xe0 <78102b27> syscall_call+0x7/0xb
>> [ 39.610923] Code: 90 90 90 90 90 90 90 90 90 90 90 53 8b 54 24 08 8b 5c 24 0c 8b 02 85 c0 74 31 8b 4b 08 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 <3b> 48 08 7f 1b 8d 50 04 8b 40 04 85 c0 75 f1 31 c0 eb 0d 90 90
Ignoring the leading NOPs, that decodes to
0: 53 push %ebx
1: 8b 54 24 08 mov 0x8(%esp,1),%edx
5: 8b 5c 24 0c mov 0xc(%esp,1),%ebx
9: 8b 02 mov (%edx),%eax
b: 85 c0 test %eax,%eax
d: 74 31 je 0x40
f: 8b 4b 08 mov 0x8(%ebx),%ecx
12: 8d b4 26 00 00 00 00 lea 0x0(%esi,1),%esi
19: 8d bc 27 00 00 00 00 lea 0x0(%edi,1),%edi
20: 3b 48 08 cmp 0x8(%eax),%ecx <==== oops
23: 7f 1b jg 0x40
25: 8d 50 04 lea 0x4(%eax),%edx
28: 8b 40 04 mov 0x4(%eax),%eax
2b: 85 c0 test %eax,%eax
2d: 75 f1 jne 0x20
2f: 31 c0 xor %eax,%eax
31: eb 0d jmp 0x40
static int notifier_chain_register(struct notifier_block **nl,
struct notifier_block *n)
{
while ((*nl) != NULL) {
if (n->priority > (*nl)->priority) <=== oops
break;
nl = &((*nl)->next);
}
n->next = *nl;
rcu_assign_pointer(*nl, n);
return 0;
}
notifier_chain_register() is running the existing chain to find the
place where XFS needs to be inserted, and the existing chain is
corrupt. Probably not an XFS problem.
Any particular reason why this kernel is using VMSPLIT_2G?
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: 2.6.17-rc1 did break XFS
2006-04-13 5:35 ` Nathan Scott
2006-04-13 9:23 ` Keith Owens
@ 2006-04-13 9:36 ` Keith Owens
2006-04-13 15:12 ` Alan Stern
1 sibling, 1 reply; 17+ messages in thread
From: Keith Owens @ 2006-04-13 9:36 UTC (permalink / raw)
Cc: Nathan Scott, dgc, Linux Kernel ML, linux-xfs, xfs-masters, stern,
sekharan
Resend, previous mail was missing the person who reported the problem.
Nathan Scott (on Thu, 13 Apr 2006 15:35:33 +1000) wrote:
>On Thu, Apr 13, 2006 at 07:21:45AM +0200, Herbert Poetzl wrote:
>> [ 39.585041] BUG: unable to handle kernel paging request at virtual address 7856c380
>> [ 39.586688] printing eip:
>> [ 39.587040] 78129430
>> [ 39.587354] *pde = 005bf027
>> [ 39.587709] *pte = 0056c000
>> [ 39.588201] Oops: 0000 [#1]
>> [ 39.588536] SMP DEBUG_PAGEALLOC
>> [ 39.589057] Modules linked in:
>> [ 39.589639] CPU: 0
>> [ 39.589670] EIP: 0060:[<78129430>] Not tainted VLI
>> [ 39.589710] EFLAGS: 00000206 (2.6.17-rc1 #1)
>> [ 39.591291] EIP is at notifier_chain_register+0x20/0x50
>> [ 39.591890] eax: 7856c378 ebx: 878db3f8 ecx: 00000000 edx: 784bf9bc
>> [ 39.592601] esi: 878db3f8 edi: 878e7c00 ebp: 878db800 esp: 878cad5c
>> [ 39.593399] ds: 007b es: 007b ss: 0068
>> [ 39.593896] Process mount (pid: 50, threadinfo=878ca000 task=87f7e570)
>> [ 39.594530] Stack: <0>784bf9a0 781295f4 784bf9bc 878db3f8 878db000 878db000 78136997 784bf9a0
>> [ 39.595839] 878db3f8 782d43e6 878db3f8 00000404 878db000 87d1e6a0 878e7c00 782d1813
>> [ 39.597002] 878db000 00000001 782e5eaf 00000424 00000001 878e7c00 87d1e6a0 782f2150
>> [ 39.598164] Call Trace:
>> [ 39.598592] <781295f4> blocking_notifier_chain_register+0x54/0x90 <78136997> register_cpu_notifier+0x17/0x20
>> [ 39.600024] <782d43e6> xfs_icsb_init_counters+0x46/0xb0 <782d1813> xfs_mount_init+0x23/0x160
>> [ 39.601199] <782e5eaf> kmem_zalloc+0x1f/0x50 <782f2150> bhv_insert_all_vfsops+0x10/0x50
>> [ 39.602315] <782f1835> xfs_fs_fill_super+0x35/0x1f0 <78313607> snprintf+0x27/0x30
>> [ 39.603437] <781a2134> disk_name+0x64/0xc0 <78168fbf> sb_set_blocksize+0x1f/0x50
>> [ 39.604524] <78168909> get_sb_bdev+0x109/0x160 <781445ef> __alloc_pages+0x5f/0x370
>> [ 39.605612] <782f1a20> xfs_fs_get_sb+0x30/0x40 <782f1800> xfs_fs_fill_super+0x0/0x1f0
>> [ 39.606698] <78168bb0> do_kern_mount+0xa0/0x160 <78181467> do_new_mount+0x77/0xc0
>> [ 39.607764] <78181b2f> do_mount+0x1bf/0x220 <783f4178> iret_exc+0x3d4/0x6ab
>> [ 39.608790] <78181913> copy_mount_options+0x63/0xc0 <783f398f> lock_kernel+0x2f/0x50
>> [ 39.609867] <78181f2f> sys_mount+0x9f/0xe0 <78102b27> syscall_call+0x7/0xb
>> [ 39.610923] Code: 90 90 90 90 90 90 90 90 90 90 90 53 8b 54 24 08 8b 5c 24 0c 8b 02 85 c0 74 31 8b 4b 08 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 <3b> 48 08 7f 1b 8d 50 04 8b 40 04 85 c0 75 f1 31 c0 eb 0d 90 90
Ignoring the leading NOPs, that decodes to
0: 53 push %ebx
1: 8b 54 24 08 mov 0x8(%esp,1),%edx
5: 8b 5c 24 0c mov 0xc(%esp,1),%ebx
9: 8b 02 mov (%edx),%eax
b: 85 c0 test %eax,%eax
d: 74 31 je 0x40
f: 8b 4b 08 mov 0x8(%ebx),%ecx
12: 8d b4 26 00 00 00 00 lea 0x0(%esi,1),%esi
19: 8d bc 27 00 00 00 00 lea 0x0(%edi,1),%edi
20: 3b 48 08 cmp 0x8(%eax),%ecx <==== oops
23: 7f 1b jg 0x40
25: 8d 50 04 lea 0x4(%eax),%edx
28: 8b 40 04 mov 0x4(%eax),%eax
2b: 85 c0 test %eax,%eax
2d: 75 f1 jne 0x20
2f: 31 c0 xor %eax,%eax
31: eb 0d jmp 0x40
static int notifier_chain_register(struct notifier_block **nl,
struct notifier_block *n)
{
while ((*nl) != NULL) {
if (n->priority > (*nl)->priority) <=== oops
break;
nl = &((*nl)->next);
}
n->next = *nl;
rcu_assign_pointer(*nl, n);
return 0;
}
notifier_chain_register() is running the existing chain to find the
place where XFS needs to be inserted, and the existing chain is
corrupt. Probably not an XFS problem.
Any particular reason why this kernel is using VMSPLIT_2G?
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
2006-04-13 8:40 ` Jes Sorensen
@ 2006-04-13 13:50 ` Herbert Poetzl
2006-04-13 14:10 ` Jes Sorensen
2006-04-13 14:21 ` Jan Engelhardt
0 siblings, 2 replies; 17+ messages in thread
From: Herbert Poetzl @ 2006-04-13 13:50 UTC (permalink / raw)
To: Jes Sorensen
Cc: Linux Kernel ML, linux-xfs, xfs-masters, stern, sekharan, akpm,
David Chinner
On Thu, Apr 13, 2006 at 04:40:54AM -0400, Jes Sorensen wrote:
> >>>>> "David" == David Chinner <dgc@sgi.com> writes:
>
> David> On Thu, Apr 13, 2006 at 07:21:45AM +0200, Herbert Poetzl wrote:
> David> It looks like we landed on top of a a notifier call chain
> David> implementation change in -rc1. However, this should not matter
> David> to XFS because the interface to register_cpu_notifier() did not
> David> change and XFS is completely abstracted away from the notifier
> David> chain implementation. We do:
>
> Dave,
>
> Looks strange, the faulting address is in the same region as the
> eip. I am not that strong on x86 layouts, so I am not sure whether
> 0x78xxxxxx is the kernel's mapping or it's module space. Almost looks
> like something else had registered a notifier and then gone away
> without unregistering it.
sorry, the essential data I didn't provide here is
probably that I configured the 2G/2G split, which for
unknown reasons actually is a 2.125/1.875 split and
starts at 0x78000000 (instead of 0x80000000)
> Herbert, any chance you can make the complete boot log up to the point
> where it crashes, as well as a System.map and your .config available?
> (probably not posted to all the lists :)
sure, bootup is fine, as it boots on ext2/3 but once
it is up, and I mount the newly created xfs filesystem
the (virtual) machine (QEMU) panics ...
will provide all the data shortly via separated mail
best,
Herbert
> Cheers,
> Jes
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
2006-04-13 13:50 ` Herbert Poetzl
@ 2006-04-13 14:10 ` Jes Sorensen
2006-04-13 14:21 ` Jan Engelhardt
1 sibling, 0 replies; 17+ messages in thread
From: Jes Sorensen @ 2006-04-13 14:10 UTC (permalink / raw)
To: Jes Sorensen, Linux Kernel ML, linux-xfs, xfs-masters, stern,
sekharan, akpm, David Chinner
Herbert Poetzl wrote:
> sure, bootup is fine, as it boots on ext2/3 but once
> it is up, and I mount the newly created xfs filesystem
> the (virtual) machine (QEMU) panics ...
>
> will provide all the data shortly via separated mail
What happens if you run it on real hardware? Would be nice to eliminate
QEMU from the equation, in case it doesn't like the funny split.
Cheers,
Jes
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: 2.6.17-rc1 did break XFS
2006-04-13 9:23 ` Keith Owens
@ 2006-04-13 14:17 ` Jan Engelhardt
0 siblings, 0 replies; 17+ messages in thread
From: Jan Engelhardt @ 2006-04-13 14:17 UTC (permalink / raw)
To: Keith Owens
Cc: Nathan Scott, dgc, Linux Kernel ML, linux-xfs, xfs-masters, stern,
sekharan
>notifier_chain_register() is running the existing chain to find the
>place where XFS needs to be inserted, and the existing chain is
>corrupt. Probably not an XFS problem.
>
Aye. I booted 2.6.17-rc1 for some minutes to test CSCAN - root filesystem
is XFS - and did not have any such early oops. Since `updatedb` happened to
run automatically by cron just after I started that laptop, I also would
not say it being an XFS problem. I do use VMSPLIT_3G_OPT however.
Jan Engelhardt
--
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
2006-04-13 13:50 ` Herbert Poetzl
2006-04-13 14:10 ` Jes Sorensen
@ 2006-04-13 14:21 ` Jan Engelhardt
2006-04-13 14:32 ` Con Kolivas
2006-04-13 17:53 ` Herbert Poetzl
1 sibling, 2 replies; 17+ messages in thread
From: Jan Engelhardt @ 2006-04-13 14:21 UTC (permalink / raw)
To: Herbert Poetzl
Cc: Jes Sorensen, Con Kolivas, Linux Kernel ML, linux-xfs,
xfs-masters, stern, sekharan, akpm, David Chinner
>>
>> Looks strange, the faulting address is in the same region as the
>> eip. I am not that strong on x86 layouts, so I am not sure whether
>> 0x78xxxxxx is the kernel's mapping or it's module space. Almost looks
>> like something else had registered a notifier and then gone away
>> without unregistering it.
>
>sorry, the essential data I didn't provide here is
>probably that I configured the 2G/2G split, which for
>unknown reasons actually is a 2.125/1.875 split and
>starts at 0x78000000 (instead of 0x80000000)
That's how it is coded in arch/i386/Kconfig. It says 78 rather than 80.
Maybe Con has an idea?
Jan Engelhardt
--
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
2006-04-13 14:21 ` Jan Engelhardt
@ 2006-04-13 14:32 ` Con Kolivas
2006-04-13 17:53 ` Herbert Poetzl
1 sibling, 0 replies; 17+ messages in thread
From: Con Kolivas @ 2006-04-13 14:32 UTC (permalink / raw)
To: Jan Engelhardt
Cc: Herbert Poetzl, Jes Sorensen, Linux Kernel ML, linux-xfs,
xfs-masters, stern, sekharan, akpm, David Chinner
On Friday 14 April 2006 00:21, Jan Engelhardt wrote:
> >> Looks strange, the faulting address is in the same region as the
> >> eip. I am not that strong on x86 layouts, so I am not sure whether
> >> 0x78xxxxxx is the kernel's mapping or it's module space. Almost looks
> >> like something else had registered a notifier and then gone away
> >> without unregistering it.
> >
> >sorry, the essential data I didn't provide here is
> >probably that I configured the 2G/2G split, which for
> >unknown reasons actually is a 2.125/1.875 split and
> >starts at 0x78000000 (instead of 0x80000000)
>
> That's how it is coded in arch/i386/Kconfig. It says 78 rather than 80.
> Maybe Con has an idea?
Follow this thread backwards from this point:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113690295909937&w=2
--
-ck
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: 2.6.17-rc1 did break XFS
2006-04-13 9:36 ` Keith Owens
@ 2006-04-13 15:12 ` Alan Stern
0 siblings, 0 replies; 17+ messages in thread
From: Alan Stern @ 2006-04-13 15:12 UTC (permalink / raw)
To: Keith Owens
Cc: Nathan Scott, dgc, Linux Kernel ML, linux-xfs, xfs-masters,
sekharan
On Thu, 13 Apr 2006, Keith Owens wrote:
> Nathan Scott (on Thu, 13 Apr 2006 15:35:33 +1000) wrote:
> >On Thu, Apr 13, 2006 at 07:21:45AM +0200, Herbert Poetzl wrote:
> >> [ 39.585041] BUG: unable to handle kernel paging request at virtual address 7856c380
> >> [ 39.586688] printing eip:
> >> [ 39.587040] 78129430
> >> [ 39.587354] *pde = 005bf027
> >> [ 39.587709] *pte = 0056c000
> >> [ 39.588201] Oops: 0000 [#1]
> >> [ 39.588536] SMP DEBUG_PAGEALLOC
> >> [ 39.589057] Modules linked in:
> >> [ 39.589639] CPU: 0
> >> [ 39.589670] EIP: 0060:[<78129430>] Not tainted VLI
> >> [ 39.589710] EFLAGS: 00000206 (2.6.17-rc1 #1)
> >> [ 39.591291] EIP is at notifier_chain_register+0x20/0x50
> >> [ 39.591890] eax: 7856c378 ebx: 878db3f8 ecx: 00000000 edx: 784bf9bc
> >> [ 39.592601] esi: 878db3f8 edi: 878e7c00 ebp: 878db800 esp: 878cad5c
> >> [ 39.593399] ds: 007b es: 007b ss: 0068
> >> [ 39.593896] Process mount (pid: 50, threadinfo=878ca000 task=87f7e570)
> >> [ 39.594530] Stack: <0>784bf9a0 781295f4 784bf9bc 878db3f8 878db000 878db000 78136997 784bf9a0
> >> [ 39.595839] 878db3f8 782d43e6 878db3f8 00000404 878db000 87d1e6a0 878e7c00 782d1813
> >> [ 39.597002] 878db000 00000001 782e5eaf 00000424 00000001 878e7c00 87d1e6a0 782f2150
> >> [ 39.598164] Call Trace:
> >> [ 39.598592] <781295f4> blocking_notifier_chain_register+0x54/0x90 <78136997> register_cpu_notifier+0x17/0x20
> >> [ 39.600024] <782d43e6> xfs_icsb_init_counters+0x46/0xb0 <782d1813> xfs_mount_init+0x23/0x160
> >> [ 39.601199] <782e5eaf> kmem_zalloc+0x1f/0x50 <782f2150> bhv_insert_all_vfsops+0x10/0x50
> >> [ 39.602315] <782f1835> xfs_fs_fill_super+0x35/0x1f0 <78313607> snprintf+0x27/0x30
> >> [ 39.603437] <781a2134> disk_name+0x64/0xc0 <78168fbf> sb_set_blocksize+0x1f/0x50
> >> [ 39.604524] <78168909> get_sb_bdev+0x109/0x160 <781445ef> __alloc_pages+0x5f/0x370
> >> [ 39.605612] <782f1a20> xfs_fs_get_sb+0x30/0x40 <782f1800> xfs_fs_fill_super+0x0/0x1f0
> >> [ 39.606698] <78168bb0> do_kern_mount+0xa0/0x160 <78181467> do_new_mount+0x77/0xc0
> >> [ 39.607764] <78181b2f> do_mount+0x1bf/0x220 <783f4178> iret_exc+0x3d4/0x6ab
> >> [ 39.608790] <78181913> copy_mount_options+0x63/0xc0 <783f398f> lock_kernel+0x2f/0x50
> >> [ 39.609867] <78181f2f> sys_mount+0x9f/0xe0 <78102b27> syscall_call+0x7/0xb
> >> [ 39.610923] Code: 90 90 90 90 90 90 90 90 90 90 90 53 8b 54 24 08 8b 5c 24 0c 8b 02 85 c0 74 31 8b 4b 08 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 <3b> 48 08 7f 1b 8d 50 04 8b 40 04 85 c0 75 f1 31 c0 eb 0d 90 90
>
> Ignoring the leading NOPs, that decodes to
>
> 0: 53 push %ebx
> 1: 8b 54 24 08 mov 0x8(%esp,1),%edx
> 5: 8b 5c 24 0c mov 0xc(%esp,1),%ebx
> 9: 8b 02 mov (%edx),%eax
> b: 85 c0 test %eax,%eax
> d: 74 31 je 0x40
> f: 8b 4b 08 mov 0x8(%ebx),%ecx
> 12: 8d b4 26 00 00 00 00 lea 0x0(%esi,1),%esi
> 19: 8d bc 27 00 00 00 00 lea 0x0(%edi,1),%edi
> 20: 3b 48 08 cmp 0x8(%eax),%ecx <==== oops
> 23: 7f 1b jg 0x40
> 25: 8d 50 04 lea 0x4(%eax),%edx
> 28: 8b 40 04 mov 0x4(%eax),%eax
> 2b: 85 c0 test %eax,%eax
> 2d: 75 f1 jne 0x20
> 2f: 31 c0 xor %eax,%eax
> 31: eb 0d jmp 0x40
>
> static int notifier_chain_register(struct notifier_block **nl,
> struct notifier_block *n)
> {
> while ((*nl) != NULL) {
> if (n->priority > (*nl)->priority) <=== oops
> break;
> nl = &((*nl)->next);
> }
> n->next = *nl;
> rcu_assign_pointer(*nl, n);
> return 0;
> }
>
> notifier_chain_register() is running the existing chain to find the
> place where XFS needs to be inserted, and the existing chain is
> corrupt. Probably not an XFS problem.
I agree. It looks like some module registered a cpu notifier and then
forgot to unregister the notifier block when it was unloaded.
If you add some stack-dump debugging to register_cpu_notifier() and
unregister_cpu_notifier() it ought to be pretty easy to identify the
guilty party.
Alan Stern
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
2006-04-13 14:21 ` Jan Engelhardt
2006-04-13 14:32 ` Con Kolivas
@ 2006-04-13 17:53 ` Herbert Poetzl
2006-04-13 18:38 ` Chandra Seetharaman
2006-04-13 18:52 ` Jan Engelhardt
1 sibling, 2 replies; 17+ messages in thread
From: Herbert Poetzl @ 2006-04-13 17:53 UTC (permalink / raw)
To: Jan Engelhardt
Cc: Jes Sorensen, Con Kolivas, Linux Kernel ML, linux-xfs,
xfs-masters, stern, sekharan, akpm, David Chinner
On Thu, Apr 13, 2006 at 04:21:18PM +0200, Jan Engelhardt wrote:
> >>
> >> Looks strange, the faulting address is in the same region as the
> >> eip. I am not that strong on x86 layouts, so I am not sure whether
> >> 0x78xxxxxx is the kernel's mapping or it's module space. Almost looks
> >> like something else had registered a notifier and then gone away
> >> without unregistering it.
> >
> >sorry, the essential data I didn't provide here is
> >probably that I configured the 2G/2G split, which for
> >unknown reasons actually is a 2.125/1.875 split and
> >starts at 0x78000000 (instead of 0x80000000)
>
> That's how it is coded in arch/i386/Kconfig. It says 78 rather than 80.
> Maybe Con has an idea?
here is the same oops with 3/1 split and the bootup log
best,
Herbert
[42949372.960000] BIOS-provided physical RAM map:
[42949372.960000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[42949372.960000] BIOS-e820: 0000000000100000 - 0000000010000000 (usable)
[42949372.960000] 256MB LOWMEM available.
[42949372.960000] DMI not present or invalid.
[42949372.960000] Allocating PCI resources starting at 20000000 (gap: 10000000:f0000000)
[42949372.960000] Built 1 zonelists
[42949372.960000] Kernel command line: rw root=/dev/hda1
[42949372.960000] Local APIC disabled by BIOS -- you can enable it with "lapic"
[42949372.960000] Enabling fast FPU save and restore... done.
[42949372.960000] Enabling unmasked SIMD FPU exception support... done.
[42949372.960000] Initializing CPU#0
[42949372.960000] CPU 0 irqstacks, hard=c0585000 soft=c057d000
[42949372.960000] PID hash table entries: 2048 (order: 11, 8192 bytes)
[ 0.000000] Detected 936.901 MHz processor.
[ 2.311028] Using tsc for high-res timesource
[ 2.313007] Console: colour dummy device 80x25
[ 2.325933] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 2.330349] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 2.629401] Memory: 253808k/262144k available (3025k kernel code, 7948k reserved, 1312k data, 216k init, 0k highmem)
[ 2.630294] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[ 2.783776] Calibrating delay using timer specific routine.. 1892.22 BogoMIPS (lpj=9461109)
[ 2.787996] Security Framework v1.0.0 initialized
[ 2.789434] Capability LSM initialized
[ 2.791515] Mount-cache hash table entries: 512
[ 2.809314] CPU: L1 I cache: 8K
[ 2.809737] CPU: L2 cache: 128K
[ 2.811380] Checking 'hlt' instruction... OK.
[ 2.846019] SMP alternatives: switching to UP code
[ 2.849639] Freeing SMP alternatives: 16k freed
[ 2.855731] CPU0: Intel Pentium II (Klamath) stepping 03
[ 2.856731] SMP motherboard not detected.
[ 2.857175] Local APIC not detected. Using dummy APIC emulation.
[ 2.863283] Brought up 1 CPUs
[ 2.865224] migration_cost=0
[ 2.896344] NET: Registered protocol family 16
[ 2.901885] PCI: PCI BIOS revision 2.10 entry at 0xf9ce0, last bus=0
[ 2.916966] PCI: Probing PCI hardware
[ 2.930880] PCI: Using IRQ router PIIX/ICH [8086/7000] at 0000:00:01.0
[ 2.936121] Setting up standard PCI resources
[ 2.945954] PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
[ 2.977965] VFS: Disk quotas dquot_6.5.1
[ 2.979416] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 2.988151] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 2.996052] JFS: nTxBlock = 1983, nTxLock = 15864
[ 3.031832] SGI XFS with no debug enabled
[ 3.040916] SGI XFS Quota Management subsystem
[ 3.042382] Initializing Cryptographic API
[ 3.043276] io scheduler noop registered
[ 3.044655] io scheduler anticipatory registered
[ 3.045690] io scheduler deadline registered
[ 3.047093] io scheduler cfq registered (default)
[ 3.047950] PCI: PIIX3: Enabling Passive Release on 0000:00:01.0
[ 3.048668] Limiting direct PCI/PCI transfers.
[ 3.049154] Activating ISA DMA hang workarounds.
[ 3.088622] Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
[ 3.091746] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16450
[ 3.115241] FDC 0 is a S82078B
[ 3.117966] ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker
[ 3.118048] http://www.scyld.com/network/ne2k-pci.html
[ 3.119679] PCI: Found IRQ 11 for device 0000:00:03.0
[ 3.127097] eth0: RealTek RTL-8029 found at 0xc100, IRQ 11, 52:54:00:12:34:56.
[ 3.135008] tun: Universal TUN/TAP device driver, 1.6
[ 3.135605] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 3.136714] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[ 3.137446] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[ 3.583356] hda: QEMU HARDDISK, ATA DISK drive
[ 3.584654] hda: IRQ probe failed (0xfffffffa)
[ 4.202753] hdb: IRQ probe failed (0xfffffffa)
[ 4.522363] hdb: IRQ probe failed (0xfffffffa)
[ 5.021521] hdc: QEMU HARDDISK, ATA DISK drive
[ 5.022536] hdc: IRQ probe failed (0xfffffffa)
[ 5.641217] hdd: IRQ probe failed (0xfffffffa)
[ 5.961917] hdd: IRQ probe failed (0xfffffffa)
[ 6.021888] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[ 6.024569] ide1 at 0x170-0x177,0x376 on irq 15
[ 6.030061] hda: max request size: 128KiB
[ 6.031459] hda: 65537 sectors (33 MB) w/256KiB Cache, CHS=65/16/63
[ 6.036961] hda: hda1
[ 6.057314] hdc: max request size: 128KiB
[ 6.057862] hdc: 524289 sectors (268 MB) w/256KiB Cache, CHS=520/16/63
[ 6.061617] hdc: hdc1
[ 6.072677] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 6.073751] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 6.084567] input: AT Translated Set 2 keyboard as /class/input/input0
[ 6.089494] Netfilter messages via NETLINK v0.30.
[ 6.092791] NET: Registered protocol family 2
[ 6.183378] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 6.191725] TCP established hash table entries: 8192 (order: 5, 163840 bytes)
[ 6.195386] TCP bind hash table entries: 4096 (order: 4, 81920 bytes)
[ 6.197587] TCP: Hash tables configured (established 8192 bind 4096)
[ 6.198427] TCP reno registered
[ 6.201833] ip_conntrack version 2.4 (2048 buckets, 16384 max) - 172 bytes per conntrack
[ 6.294236] input: ImExPS/2 Generic Explorer Mouse as /class/input/input1
[ 6.441466] TCP bic registered
[ 6.442618] NET: Registered protocol family 1
[ 6.443427] NET: Registered protocol family 17
[ 6.447208] 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
[ 6.448011] All bugs added by David S. Miller <davem@redhat.com>
[ 6.449111] Using IPI Shortcut mode
[ 6.450683] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 6.503170] VFS: Mounted root (ext2 filesystem).
[ 6.550982] Freeing unused kernel memory: 216k freed
Linux (none) 2.6.17-rc1 #2 SMP Thu Apr 13 19:18:48 CEST 2006 i686 unknown
xid related tests ...
[ 66.670041] BUG: unable to handle kernel paging request at virtual address c056c380
[ 66.671683] printing eip:
[ 66.672036] c0129430
[ 66.672346] *pde = 005bf027
[ 66.672697] *pte = 0056c000
[ 66.673179] Oops: 0000 [#1]
[ 66.673496] SMP DEBUG_PAGEALLOC
[ 66.674011] Modules linked in:
[ 66.674591] CPU: 0
[ 66.674624] EIP: 0060:[<c0129430>] Not tainted VLI
[ 66.674664] EFLAGS: 00000286 (2.6.17-rc1 #2)
[ 66.676211] EIP is at notifier_chain_register+0x20/0x50
[ 66.676802] eax: c056c378 ebx: cf95f3f8 ecx: 00000000 edx: c04bf9bc
[ 66.677609] esi: cf95f3f8 edi: cf8eac00 ebp: cf95f800 esp: cf8ced5c
[ 66.678304] ds: 007b es: 007b ss: 0068
[ 66.678801] Process mount (pid: 50, threadinfo=cf8ce000 task=cff7e570)
[ 66.679442] Stack: <0>c04bf9a0 c01295f4 c04bf9bc cf95f3f8 cf95f000 cf95f000 c0136997 c04bf9a0
[ 66.680764] cf95f3f8 c02d43e6 cf95f3f8 00000404 cf95f000 cfd1e6a0 cf8eac00 c02d1813
[ 66.681929] cf95f000 00000001 c02e5eaf 00000424 00000001 cf8eac00 cfd1e6a0 c02f2150
[ 66.683090] Call Trace:
[ 66.683520] <c01295f4> blocking_notifier_chain_register+0x54/0x90 <c0136997> register_cpu_notifier+0x17/0x20
[ 66.684911] <c02d43e6> xfs_icsb_init_counters+0x46/0xb0 <c02d1813> xfs_mount_init+0x23/0x160
[ 66.686079] <c02e5eaf> kmem_zalloc+0x1f/0x50 <c02f2150> bhv_insert_all_vfsops+0x10/0x50
[ 66.687255] <c02f1835> xfs_fs_fill_super+0x35/0x1f0 <c0313607> snprintf+0x27/0x30
[ 66.688319] <c01a2134> disk_name+0x64/0xc0 <c0168fbf> sb_set_blocksize+0x1f/0x50
[ 66.689388] <c0168909> get_sb_bdev+0x109/0x160 <c01034f2> common_interrupt+0x1a/0x20
[ 66.690483] <c02f1a20> xfs_fs_get_sb+0x30/0x40 <c02f1800> xfs_fs_fill_super+0x0/0x1f0
[ 66.691552] <c0168bb0> do_kern_mount+0xa0/0x160 <c0181467> do_new_mount+0x77/0xc0
[ 66.692617] <c0181b2f> do_mount+0x1bf/0x220 <c03f4178> iret_exc+0x3d4/0x6ab
[ 66.693636] <c0181913> copy_mount_options+0x63/0xc0 <c03f398f> lock_kernel+0x2f/0x50
[ 66.694701] <c0181f2f> sys_mount+0x9f/0xe0 <c0102b27> syscall_call+0x7/0xb
[ 66.695739] Code: 90 90 90 90 90 90 90 90 90 90 90 53 8b 54 24 08 8b 5c 24 0c 8b 02 85 c0 74 31 8b 4b 08 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 <3b> 48 08 7f 1b 8d 50 04 8b 40 04 85 c0 75 f1 31 c0 eb 0d 90 90
[ 66.700163] <3>BUG: sleeping function called from invalid context at include/linux/rwsem.h:43
[ 66.701263] in_atomic():0, irqs_disabled():1
[ 66.701764] <c01189f4> __might_sleep+0xa4/0xb0 <c011de7a> exit_mm+0x3a/0x170
[ 66.702792] <c011e74c> do_exit+0xfc/0x420 <c011c217> printk+0x17/0x20
[ 66.703722] <c0103ef7> die+0x1e7/0x1f0 <c0112b34> do_page_fault+0x334/0x690
[ 66.704792] <c015c407> cache_grow+0x157/0x1a0 <c0112800> do_page_fault+0x0/0x690
[ 66.705897] <c0103627> error_code+0x4f/0x54 <c0129430> notifier_chain_register+0x20/0x50
[ 66.707153] <c01295f4> blocking_notifier_chain_register+0x54/0x90 <c0136997> register_cpu_notifier+0x17/0x20
[ 66.708536] <c02d43e6> xfs_icsb_init_counters+0x46/0xb0 <c02d1813> xfs_mount_init+0x23/0x160
[ 66.709778] <c02e5eaf> kmem_zalloc+0x1f/0x50 <c02f2150> bhv_insert_all_vfsops+0x10/0x50
[ 66.710964] <c02f1835> xfs_fs_fill_super+0x35/0x1f0 <c0313607> snprintf+0x27/0x30
[ 66.712097] <c01a2134> disk_name+0x64/0xc0 <c0168fbf> sb_set_blocksize+0x1f/0x50
[ 66.713219] <c0168909> get_sb_bdev+0x109/0x160 <c01034f2> common_interrupt+0x1a/0x20
[ 66.714372] <c02f1a20> xfs_fs_get_sb+0x30/0x40 <c02f1800> xfs_fs_fill_super+0x0/0x1f0
[ 66.715522] <c0168bb0> do_kern_mount+0xa0/0x160 <c0181467> do_new_mount+0x77/0xc0
[ 66.716658] <c0181b2f> do_mount+0x1bf/0x220 <c03f4178> iret_exc+0x3d4/0x6ab
[ 66.717790] <c0181913> copy_mount_options+0x63/0xc0 <c03f398f> lock_kernel+0x2f/0x50
[ 66.718945] <c0181f2f> sys_mount+0x9f/0xe0 <c0102b27> syscall_call+0x7/0xb
> Jan Engelhardt
> --
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
2006-04-13 17:53 ` Herbert Poetzl
@ 2006-04-13 18:38 ` Chandra Seetharaman
2006-04-14 1:39 ` Herbert Poetzl
2006-04-13 18:52 ` Jan Engelhardt
1 sibling, 1 reply; 17+ messages in thread
From: Chandra Seetharaman @ 2006-04-13 18:38 UTC (permalink / raw)
To: Herbert Poetzl
Cc: Jan Engelhardt, Jes Sorensen, Con Kolivas, Linux Kernel ML,
linux-xfs, xfs-masters, Alan Stern, akpm, David Chinner
On Thu, 2006-04-13 at 19:53 +0200, Herbert Poetzl wrote:
> On Thu, Apr 13, 2006 at 04:21:18PM +0200, Jan Engelhardt wrote:
> > >>
> > >> Looks strange, the faulting address is in the same region as the
> > >> eip. I am not that strong on x86 layouts, so I am not sure whether
> > >> 0x78xxxxxx is the kernel's mapping or it's module space. Almost looks
> > >> like something else had registered a notifier and then gone away
> > >> without unregistering it.
> > >
> > >sorry, the essential data I didn't provide here is
> > >probably that I configured the 2G/2G split, which for
> > >unknown reasons actually is a 2.125/1.875 split and
> > >starts at 0x78000000 (instead of 0x80000000)
> >
> > That's how it is coded in arch/i386/Kconfig. It says 78 rather than 80.
> > Maybe Con has an idea?
>
> here is the same oops with 3/1 split and the bootup log
>
Hi Herbert,
Looks to be the same stack as earlier, Is there any modules compiled in
that were removed before you tried to mount the XFS filesystem ?
Can you send me the .config file.
chandra
<snip>
--
----------------------------------------------------------------------
Chandra Seetharaman | Be careful what you choose....
- sekharan@us.ibm.com | .......you may get it.
----------------------------------------------------------------------
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
2006-04-13 17:53 ` Herbert Poetzl
2006-04-13 18:38 ` Chandra Seetharaman
@ 2006-04-13 18:52 ` Jan Engelhardt
2006-04-14 1:30 ` Herbert Poetzl
1 sibling, 1 reply; 17+ messages in thread
From: Jan Engelhardt @ 2006-04-13 18:52 UTC (permalink / raw)
To: Herbert Poetzl
Cc: Jes Sorensen, Con Kolivas, Linux Kernel ML, linux-xfs,
xfs-masters, stern, sekharan, akpm, David Chinner
>[ 3.583356] hda: QEMU HARDDISK, ATA DISK drive
>[ 5.021521] hdc: QEMU HARDDISK, ATA DISK drive
Maybe QEMU is involved in the Oops? What if used on a normal system?
Jan Engelhardt
--
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
2006-04-13 18:52 ` Jan Engelhardt
@ 2006-04-14 1:30 ` Herbert Poetzl
0 siblings, 0 replies; 17+ messages in thread
From: Herbert Poetzl @ 2006-04-14 1:30 UTC (permalink / raw)
To: Jan Engelhardt
Cc: Jes Sorensen, Con Kolivas, Linux Kernel ML, linux-xfs,
xfs-masters, stern, sekharan, akpm, David Chinner
On Thu, Apr 13, 2006 at 08:52:05PM +0200, Jan Engelhardt wrote:
>
> >[ 3.583356] hda: QEMU HARDDISK, ATA DISK drive
> >[ 5.021521] hdc: QEMU HARDDISK, ATA DISK drive
>
> Maybe QEMU is involved in the Oops? What if used on a normal system?
well, might be, but a) it works perfectly fine with
2.6.16 and many older kernels, and b) sorry, I don't
have a real system for xfs crash testing right now
find the config in my reply to the previous email
best,
Herbert
> Jan Engelhardt
> --
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
2006-04-13 18:38 ` Chandra Seetharaman
@ 2006-04-14 1:39 ` Herbert Poetzl
0 siblings, 0 replies; 17+ messages in thread
From: Herbert Poetzl @ 2006-04-14 1:39 UTC (permalink / raw)
To: Chandra Seetharaman
Cc: Jan Engelhardt, Jes Sorensen, Con Kolivas, Linux Kernel ML,
linux-xfs, xfs-masters, Alan Stern, akpm, David Chinner
[-- Attachment #1: Type: text/plain, Size: 2805 bytes --]
On Thu, Apr 13, 2006 at 11:38:11AM -0700, Chandra Seetharaman wrote:
> On Thu, 2006-04-13 at 19:53 +0200, Herbert Poetzl wrote:
> > On Thu, Apr 13, 2006 at 04:21:18PM +0200, Jan Engelhardt wrote:
> > > >>
> > > >> Looks strange, the faulting address is in the same region as the
> > > >> eip. I am not that strong on x86 layouts, so I am not sure whether
> > > >> 0x78xxxxxx is the kernel's mapping or it's module space. Almost looks
> > > >> like something else had registered a notifier and then gone away
> > > >> without unregistering it.
> > > >
> > > >sorry, the essential data I didn't provide here is
> > > >probably that I configured the 2G/2G split, which for
> > > >unknown reasons actually is a 2.125/1.875 split and
> > > >starts at 0x78000000 (instead of 0x80000000)
> > >
> > > That's how it is coded in arch/i386/Kconfig. It says 78 rather than 80.
> > > Maybe Con has an idea?
> >
> > here is the same oops with 3/1 split and the bootup log
> >
>
> Hi Herbert,
>
> Looks to be the same stack as earlier, Is there any modules compiled
> in that were removed before you tried to mount the XFS filesystem ?
no, the kernel is monolithic, no modules added or
removed after startup, just a busybox is running
and I did create the xfs filesystem before I mount
it ...
/ # mkfs.xfs -f /dev/hdc1
meta-data=/dev/hdc1 isize=256 agcount=8, agsize=8189 blks
data = bsize=4096 blocks=65512, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=0
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=1200
realtime =none extsz=65536 blocks=0, rtextents=0
/ # cat /proc/partitions
major minor #blocks name
3 0 32768 hda
3 1 32728 hda1
22 0 262144 hdc
22 1 262048 hdc1
/ # mount /dev/hdc1 /mnt/
[ 63.523239] BUG: unable to handle kernel paging request at virtual address c056c380
[ 63.524195] printing eip:
[ 63.524514] c0129430
[ 63.524797] *pde = 005bf027
[ 63.525182] *pte = 0056c000
[ 63.525667] Oops: 0000 [#1]
[ 63.525995] SMP DEBUG_PAGEALLOC
[ 63.526506] Modules linked in:
[ 63.527084] CPU: 0
[ 63.527118] EIP: 0060:[<c0129430>] Not tainted VLI
[ 63.527158] EFLAGS: 00000286 (2.6.17-rc1 #2)
[ 63.528675] EIP is at notifier_chain_register+0x20/0x50
...
> Can you send me the .config file.
find attached the kernel config
best,
Herbert
> chandra
>
> <snip>
>
> --
>
> ----------------------------------------------------------------------
> Chandra Seetharaman | Be careful what you choose....
> - sekharan@us.ibm.com | .......you may get it.
> ----------------------------------------------------------------------
>
[-- Attachment #2: xfs.config --]
[-- Type: text/plain, Size: 22377 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.17-rc1
# Thu Apr 13 18:59:33 2006
#
CONFIG_X86_32=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_CPUSETS=y
# CONFIG_RELAY is not set
CONFIG_INITRAMFS_SOURCE=""
CONFIG_UID16=y
CONFIG_VM86=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_EMBEDDED=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
# CONFIG_HOTPLUG is not set
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_SLAB=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
#
# Block layer
#
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
CONFIG_LSF=y
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
#
# 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=y
# 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 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_MGEODEGX1 is not set
# CONFIG_MGEODE_LX 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_PPRO_FENCE=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
# CONFIG_HPET_TIMER is not set
CONFIG_SMP=y
CONFIG_NR_CPUS=8
# CONFIG_SCHED_SMT is not set
CONFIG_SCHED_MC=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=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_X86_REBOOTFIXUPS is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_3G_OPT is not set
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_IRQBALANCE=y
# CONFIG_REGPARM is not set
# CONFIG_SECCOMP is not set
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
# CONFIG_KEXEC is not set
CONFIG_PHYSICAL_START=0x100000
CONFIG_DOUBLEFAULT=y
#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
# CONFIG_ACPI 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
CONFIG_PCI_DIRECT=y
# CONFIG_PCIEPORTBUS is not set
# CONFIG_PCI_MSI is not set
# CONFIG_PCI_DEBUG is not set
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set
#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set
#
# Networking
#
CONFIG_NET=y
#
# Networking options
#
# CONFIG_NETDEBUG is not set
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
# CONFIG_IP_ROUTE_FWMARK is not set
# CONFIG_IP_ROUTE_MULTIPATH is not set
# CONFIG_IP_ROUTE_VERBOSE is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
CONFIG_IP_MROUTE=y
# CONFIG_IP_PIMSM_V1 is not set
# CONFIG_IP_PIMSM_V2 is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_BIC=y
#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=y
# CONFIG_NETFILTER_NETLINK_QUEUE is not set
# CONFIG_NETFILTER_NETLINK_LOG is not set
# CONFIG_NETFILTER_XTABLES is not set
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=y
# CONFIG_IP_NF_CT_ACCT is not set
# CONFIG_IP_NF_CONNTRACK_MARK is not set
# CONFIG_IP_NF_CONNTRACK_EVENTS is not set
# CONFIG_IP_NF_CONNTRACK_NETLINK is not set
# CONFIG_IP_NF_CT_PROTO_SCTP is not set
# CONFIG_IP_NF_FTP is not set
# CONFIG_IP_NF_IRC is not set
# CONFIG_IP_NF_NETBIOS_NS is not set
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
# CONFIG_IP_NF_PPTP is not set
# CONFIG_IP_NF_H323 is not set
# CONFIG_IP_NF_QUEUE is not set
#
# DCCP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
#
# TIPC Configuration (EXPERIMENTAL)
#
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
CONFIG_VLAN_8021Q=y
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_IEEE80211 is not set
#
# 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
#
# Connector - unified userspace <-> kernelspace linker
#
# CONFIG_CONNECTOR is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
# CONFIG_PNP is not set
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# 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
# CONFIG_BLK_DEV_COW_COMMON is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_RAM is not set
CONFIG_BLK_DEV_INITRD=y
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_IDE_TASK_IOCTL is not set
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
# CONFIG_BLK_DEV_IDEDMA_PCI is not set
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
# CONFIG_BLK_DEV_IDEDMA is not set
# CONFIG_IDEDMA_AUTO is not set
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
# CONFIG_SCSI is not set
#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Network device support
#
CONFIG_NETDEVICES=y
CONFIG_DUMMY=y
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
#
# PHY device support
#
# CONFIG_PHYLIB is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_MII is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
CONFIG_NE2K_PCI=y
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_CHELSIO_T1 is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#
CONFIG_VT=y
# CONFIG_VT_CONSOLE is not set
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_NR_UARTS=2
CONFIG_SERIAL_8250_RUNTIME_UARTS=2
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_CS5535_GPIO is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set
#
# TPM devices
#
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
#
# I2C support
#
# CONFIG_I2C is not set
#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set
#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
#
# Hardware Monitoring support
#
CONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Misc devices
#
# CONFIG_IBM_ASM is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
# CONFIG_FB is not set
#
# Console display driver support
#
# CONFIG_VGA_CONSOLE is not set
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
#
# Sound
#
# CONFIG_SOUND is not set
#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
# CONFIG_USB is not set
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# MMC/SD Card support
#
# CONFIG_MMC is not set
#
# LED devices
#
CONFIG_NEW_LEDS=y
# CONFIG_LEDS_CLASS is not set
# CONFIG_LEDS_TRIGGERS is not set
#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set
#
# EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
#
# CONFIG_EDAC is not set
#
# Real Time Clock
#
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
#
# RTC drivers
#
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_TEST is not set
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
# CONFIG_EXT2_FS_POSIX_ACL is not set
# CONFIG_EXT2_FS_SECURITY is not set
CONFIG_EXT2_FS_XIP=y
CONFIG_FS_XIP=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
# CONFIG_REISERFS_FS_POSIX_ACL is not set
# CONFIG_REISERFS_FS_SECURITY is not set
CONFIG_JFS_FS=y
# CONFIG_JFS_POSIX_ACL is not set
# CONFIG_JFS_SECURITY is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=y
CONFIG_XFS_EXPORT=y
CONFIG_XFS_QUOTA=y
# CONFIG_XFS_SECURITY is not set
# CONFIG_XFS_POSIX_ACL is not set
# CONFIG_XFS_RT is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
CONFIG_QUOTA=y
CONFIG_QFMT_V1=y
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
# CONFIG_CONFIGFS_FS is not set
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=y
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
CONFIG_RPCSEC_GSS_SPKM3=y
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
# CONFIG_9P_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# Instrumentation Support
#
# CONFIG_PROFILING is not set
# CONFIG_KPROBES is not set
#
# Kernel hacking
#
CONFIG_PRINTK_TIME=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_KERNEL=y
CONFIG_LOG_BUF_SHIFT=15
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_DEBUG_KOBJECT=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_FS is not set
CONFIG_DEBUG_VM=y
# CONFIG_FRAME_POINTER is not set
CONFIG_UNWIND_INFO=y
CONFIG_FORCED_INLINING=y
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_EARLY_PRINTK=y
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_DEBUG_STACK_USAGE is not set
CONFIG_STACK_BACKTRACE_COLS=2
CONFIG_DEBUG_PAGEALLOC=y
# CONFIG_DEBUG_RODATA is not set
CONFIG_4KSTACKS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
#
# Security options
#
# CONFIG_KEYS is not set
CONFIG_SECURITY=y
# CONFIG_SECURITY_NETWORK is not set
CONFIG_SECURITY_CAPABILITIES=y
# CONFIG_SECURITY_SECLVL is not set
#
# Cryptographic options
#
CONFIG_CRYPTO=y
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_AES_586 is not set
CONFIG_CRYPTO_CAST5=y
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_TEST is not set
#
# Hardware crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set
#
# Library routines
#
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
CONFIG_CRC32=y
# CONFIG_LIBCRC32C is not set
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2006-04-14 1:39 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-04-13 5:21 2.6.17-rc1 did break XFS Herbert Poetzl
2006-04-13 5:35 ` Nathan Scott
2006-04-13 9:23 ` Keith Owens
2006-04-13 14:17 ` Jan Engelhardt
2006-04-13 9:36 ` Keith Owens
2006-04-13 15:12 ` Alan Stern
2006-04-13 7:23 ` notifier chain problem? (was Re: 2.6.17-rc1 did break XFS) David Chinner
2006-04-13 8:40 ` Jes Sorensen
2006-04-13 13:50 ` Herbert Poetzl
2006-04-13 14:10 ` Jes Sorensen
2006-04-13 14:21 ` Jan Engelhardt
2006-04-13 14:32 ` Con Kolivas
2006-04-13 17:53 ` Herbert Poetzl
2006-04-13 18:38 ` Chandra Seetharaman
2006-04-14 1:39 ` Herbert Poetzl
2006-04-13 18:52 ` Jan Engelhardt
2006-04-14 1:30 ` Herbert Poetzl
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox