* Re: 2.6.25-rc3-mm1
2008-03-04 9:19 2.6.25-rc3-mm1 Andrew Morton
@ 2008-03-04 11:59 ` Cornelia Huck
2008-03-04 19:35 ` 2.6.25-rc3-mm1 Greg KH
2008-03-04 13:12 ` [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc () Kamalesh Babulal
` (11 subsequent siblings)
12 siblings, 1 reply; 76+ messages in thread
From: Cornelia Huck @ 2008-03-04 11:59 UTC (permalink / raw)
To: Andrew Morton, Greg KH; +Cc: linux-kernel
On Tue, 4 Mar 2008 01:19:28 -0800,
Andrew Morton <akpm@linux-foundation.org> wrote:
> +driver-core-fix-cleanup-when-failing-device_add.patch
This should go into 2.6.25, as it fixes a panic (see
http://marc.info/?l=linux-kernel&m=120411157302447&w=2,
http://marc.info/?l=linux-kernel&m=120412001416810&w=2).
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: 2.6.25-rc3-mm1
2008-03-04 11:59 ` 2.6.25-rc3-mm1 Cornelia Huck
@ 2008-03-04 19:35 ` Greg KH
0 siblings, 0 replies; 76+ messages in thread
From: Greg KH @ 2008-03-04 19:35 UTC (permalink / raw)
To: Cornelia Huck; +Cc: Andrew Morton, linux-kernel
On Tue, Mar 04, 2008 at 12:59:39PM +0100, Cornelia Huck wrote:
> On Tue, 4 Mar 2008 01:19:28 -0800,
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > +driver-core-fix-cleanup-when-failing-device_add.patch
>
> This should go into 2.6.25, as it fixes a panic (see
> http://marc.info/?l=linux-kernel&m=120411157302447&w=2,
> http://marc.info/?l=linux-kernel&m=120412001416810&w=2).
Will add it to that queue to send to Linus in a bit, thanks for poking
me.
Hint, when sending patches, please at least change the Subject so that I
don't accidentally pass it by, it was burried in a longer thread that I
missed the first time through.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 76+ messages in thread
* [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc ()
2008-03-04 9:19 2.6.25-rc3-mm1 Andrew Morton
2008-03-04 11:59 ` 2.6.25-rc3-mm1 Cornelia Huck
@ 2008-03-04 13:12 ` Kamalesh Babulal
2008-03-04 14:40 ` Michael Neuling
` (2 more replies)
2008-03-04 16:35 ` 2.6.25-rc3-mm1 (IDE) Randy Dunlap
` (10 subsequent siblings)
12 siblings, 3 replies; 76+ messages in thread
From: Kamalesh Babulal @ 2008-03-04 13:12 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linuxppc-dev, Andy Whitcroft
Hi Andrew,
The 2.6.25-rc3-mm1 kernel panics while bootup on power box. The machine booted up
without the panic on the third attempt, but badness call trace were seen while running
tests
1) The kernel panic on first attempt
Unable to handle kernel paging request for data at address 0x00000000
Faulting instruction address: 0xc00000000000cb2c
Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=128 NUMA pSeries
Modules linked in:
NIP: c00000000000cb2c LR: c00000000000caf8 CTR: 0000000000000226
REGS: c00000000068f360 TRAP: 0300 Not tainted (2.6.25-rc3-mm1-autotest)
MSR: 8000000000001032 <ME,IR,DR> CR: 28000024 XER: 20000001
DAR: 0000000000000000, DSISR: 0000000040000000
TASK = c0000000005c8590[0] 'swapper' THREAD: c00000000068c000 CPU: 0
GPR00: c00000000068f5e0 c00000000068f5e0 c00000000068e690 0000000000000000
GPR04: 00000000000035e0 000000000087264e c000000008011280 c000000000594000
GPR08: c0000000005c9300 0000000000000000 c000000000591090 c00000000068c000
GPR12: 8000000000009032 c0000000005c9300 0000000000000000 0000000000000000
GPR16: 0000000000000000 0000000000000000 0000000000008000 0000000000000000
GPR20: 0000000000000000 0000000000000000 000000000000007f 0000000000018000
GPR24: 0000000000000001 0000000000000080 0000000000000018 0000000000000000
GPR28: 0000000000000c00 c000000000588988 c000000000639be8 c000000008001c00
NIP [c00000000000cb2c] .do_IRQ+0x74/0x1c4
LR [c00000000000caf8] .do_IRQ+0x40/0x1c4
Call Trace:
[c00000000068f5e0] [c00000000000caf8] .do_IRQ+0x40/0x1c4 (unreliable)
[c00000000068f680] [c000000000004790] hardware_interrupt_entry+0x18/0x1c
--- Exception: 501 at .memset+0x70/0xfc
LR = .__alloc_bootmem_core+0x39c/0x3dc
[c00000000068f970] [c00000000068fa10] init_thread_union+0x3a10/0x4000 (unreliable)
[c00000000068fa30] [c00000000057237c] .__alloc_bootmem_node+0x38/0x8c
[c00000000068fad0] [c0000000003c477c] .zone_wait_table_init+0x74/0x108
[c00000000068fb60] [c0000000003d9058] .init_currently_empty_zone+0x40/0x11c
[c00000000068fc00] [c0000000003d94c8] .free_area_init_node+0x394/0x3fc
[c00000000068fcf0] [c00000000057314c] .free_area_init_nodes+0x2d8/0x364
[c00000000068fd90] [c00000000056682c] .paging_init+0x40/0x58
[c00000000068fe40] [c00000000055ba34] .setup_arch+0x20c/0x240
[c00000000068fee0] [c000000000552690] .start_kernel+0xdc/0x414
[c00000000068ff90] [c000000000008594] .start_here_common+0x54/0xc0
Instruction dump:
7c200b78 780404a0 2ba408ff 41bd001c e87e80a8 3884ff00 48058d21 60000000
480054cd 60000000 e93e80b0 e92900b8 <e8090000> f8410028 e9690010 e8490008
2) The kernel panic on second attempt
Unable to handle kernel paging request for data at address 0x00000000
Faulting instruction address: 0xc00000000000cb2c
Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=128 NUMA pSeries
Modules linked in:
NIP: c00000000000cb2c LR: c00000000000caf8 CTR: 0000000000014a99
REGS: c00000000068f410 TRAP: 0300 Not tainted (2.6.25-rc3-mm1-autotest)
MSR: 8000000000001032 <ME,IR,DR> CR: 28000044 XER: 00000001
DAR: 0000000000000000, DSISR: 0000000040000000
TASK = c0000000005c8590[0] 'swapper' THREAD: c00000000068c000 CPU: 0
GPR00: c00000000068f690 c00000000068f690 c00000000068e690 0000000000000000
GPR04: 0000000000003690 0000000000537672 c000000001ad59c0 c000000000594000
GPR08: c0000000005c9300 0000000000000000 c000000000591090 c00000000068c000
GPR12: 8000000000009032 c0000000005c9300 0000000000000000 0000000000000000
GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR20: 0000000000230000 0000000000000000 0000000000ffffff 0000000001000000
GPR24: 0000000000001000 0000000001000000 0000000000001000 0000000000000000
GPR28: 0000000000000000 c0000000005889c8 c000000000639be8 c000000001000000
NIP [c00000000000cb2c] .do_IRQ+0x74/0x1c4
LR [c00000000000caf8] .do_IRQ+0x40/0x1c4
Call Trace:
[c00000000068f690] [c00000000000caf8] .do_IRQ+0x40/0x1c4 (unreliable)
[c00000000068f730] [c000000000004790] hardware_interrupt_entry+0x18/0x1c
--- Exception: 501 at .memset+0x80/0xfc
LR = .__alloc_bootmem_core+0x39c/0x3dc
[c00000000068fa20] [c000000000641a78] sysctl_pernet_ops+0x108e0/0x1d6e0 (unreliable)
[c00000000068fae0] [c00000000057237c] .__alloc_bootmem_node+0x38/0x8c
[c00000000068fb80] [c0000000003c48dc] .__earlyonly_bootmem_alloc+0x24/0x3c
[c00000000068fc00] [c0000000003d885c] .vmemmap_populate+0x7c/0xf4
[c00000000068fc90] [c0000000003d9b6c] .sparse_mem_map_populate+0x38/0x64
[c00000000068fd10] [c000000000573ec4] .sparse_early_mem_map_alloc+0x54/0x98
[c00000000068fda0] [c000000000573f70] .sparse_init+0x68/0x148
[c00000000068fe40] [c00000000055b9ec] .setup_arch+0x1c4/0x240
[c00000000068fee0] [c000000000552690] .start_kernel+0xdc/0x414
[c00000000068ff90] [c000000000008594] .start_here_common+0x54/0xc0
Instruction dump:
7c200b78 780404a0 2ba408ff 41bd001c e87e80a8 3884ff00 48058d21 60000000
480054cd 60000000 e93e80b0 e92900b8 <e8090000> f8410028 e9690010 e8490008
3) Third attempt kernel booted up but had the following call trace 264 times while running
test
Badness at include/linux/gfp.h:110
NIP: c0000000000b4ff0 LR: c0000000000b4fa0 CTR: c00000000019cdb4
REGS: c000000009edf250 TRAP: 0700 Not tainted (2.6.25-rc3-mm1-autotest)
MSR: 8000000000029032 <EE,ME,IR,DR> CR: 22024042 XER: 20000003
TASK = c000000009062140[548] 'kjournald' THREAD: c000000009edc000 CPU: 0
NIP [c0000000000b4ff0] .get_page_from_freelist+0x29c/0x898
LR [c0000000000b4fa0] .get_page_from_freelist+0x24c/0x898
Call Trace:
[c000000009edf5f0] [c0000000000b56e4] .__alloc_pages_internal+0xf8/0x470
[c000000009edf6e0] [c0000000000e0458] .kmem_getpages+0x8c/0x194
[c000000009edf770] [c0000000000e1050] .fallback_alloc+0x194/0x254
[c000000009edf820] [c0000000000e14b0] .kmem_cache_alloc+0xd8/0x144
[c000000009edf8c0] [c0000000001fe0f8] .radix_tree_preload+0x50/0xd4
[c000000009edf960] [c0000000000ad048] .add_to_page_cache+0x38/0x12c
[c000000009edfa00] [c0000000000ad158] .add_to_page_cache_lru+0x1c/0x4c
[c000000009edfa90] [c0000000000add58] .find_or_create_page+0x60/0xa8
[c000000009edfb30] [c00000000011e478] .__getblk+0x140/0x310
[c000000009edfc00] [c0000000001b78c4] .journal_get_descriptor_buffer+0x44/0xd8
[c000000009edfca0] [c0000000001b236c] .journal_commit_transaction+0x948/0x1590
[c000000009edfe00] [c0000000001b585c] .kjournald+0xf4/0x2ac
[c000000009edff00] [c00000000007ff4c] .kthread+0x84/0xd0
[c000000009edff90] [c000000000028900] .kernel_thread+0x4c/0x68
Instruction dump:
7dc57378 48009575 60000000 2fa30000 419e0490 56c902d8 3c000018 7dd907b4
7ad2c7e2 7f890000 7c000026 5400fffe <0b000000> e93e8128 3b000000 80090000
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc ()
2008-03-04 13:12 ` [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc () Kamalesh Babulal
@ 2008-03-04 14:40 ` Michael Neuling
2008-03-04 18:33 ` Andrew Morton
2008-03-04 18:36 ` Andrew Morton
2008-03-05 8:22 ` Benjamin Herrenschmidt
2 siblings, 1 reply; 76+ messages in thread
From: Michael Neuling @ 2008-03-04 14:40 UTC (permalink / raw)
To: Kamalesh Babulal; +Cc: Andrew Morton, linuxppc-dev, linux-kernel
In message <47CD4AB3.3080409@linux.vnet.ibm.com> you wrote:
> Hi Andrew,
>
> The 2.6.25-rc3-mm1 kernel panics while bootup on power box. The machine boote
d up
> without the panic on the third attempt, but badness call trace were seen whil
e running
> tests
>
> 1) The kernel panic on first attempt
>
> Unable to handle kernel paging request for data at address 0x00000000
> Faulting instruction address: 0xc00000000000cb2c
> Oops: Kernel access of bad area, sig: 11 [#1]
> SMP NR_CPUS=128 NUMA pSeries
> Modules linked in:
> NIP: c00000000000cb2c LR: c00000000000caf8 CTR: 0000000000000226
> REGS: c00000000068f360 TRAP: 0300 Not tainted (2.6.25-rc3-mm1-autotest)
> MSR: 8000000000001032 <ME,IR,DR> CR: 28000024 XER: 20000001
> DAR: 0000000000000000, DSISR: 0000000040000000
> TASK = c0000000005c8590[0] 'swapper' THREAD: c00000000068c000 CPU: 0
> GPR00: c00000000068f5e0 c00000000068f5e0 c00000000068e690 0000000000000000
> GPR04: 00000000000035e0 000000000087264e c000000008011280 c000000000594000
> GPR08: c0000000005c9300 0000000000000000 c000000000591090 c00000000068c000
> GPR12: 8000000000009032 c0000000005c9300 0000000000000000 0000000000000000
> GPR16: 0000000000000000 0000000000000000 0000000000008000 0000000000000000
> GPR20: 0000000000000000 0000000000000000 000000000000007f 0000000000018000
> GPR24: 0000000000000001 0000000000000080 0000000000000018 0000000000000000
> GPR28: 0000000000000c00 c000000000588988 c000000000639be8 c000000008001c00
> NIP [c00000000000cb2c] .do_IRQ+0x74/0x1c4
> LR [c00000000000caf8] .do_IRQ+0x40/0x1c4
> Call Trace:
> [c00000000068f5e0] [c00000000000caf8] .do_IRQ+0x40/0x1c4 (unreliable)
> [c00000000068f680] [c000000000004790] hardware_interrupt_entry+0x18/0x1c
> --- Exception: 501 at .memset+0x70/0xfc
> LR = .__alloc_bootmem_core+0x39c/0x3dc
> [c00000000068f970] [c00000000068fa10] init_thread_union+0x3a10/0x4000 (unreli
able)
> [c00000000068fa30] [c00000000057237c] .__alloc_bootmem_node+0x38/0x8c
> [c00000000068fad0] [c0000000003c477c] .zone_wait_table_init+0x74/0x108
> [c00000000068fb60] [c0000000003d9058] .init_currently_empty_zone+0x40/0x11c
> [c00000000068fc00] [c0000000003d94c8] .free_area_init_node+0x394/0x3fc
> [c00000000068fcf0] [c00000000057314c] .free_area_init_nodes+0x2d8/0x364
> [c00000000068fd90] [c00000000056682c] .paging_init+0x40/0x58
> [c00000000068fe40] [c00000000055ba34] .setup_arch+0x20c/0x240
> [c00000000068fee0] [c000000000552690] .start_kernel+0xdc/0x414
> [c00000000068ff90] [c000000000008594] .start_here_common+0x54/0xc0
> Instruction dump:
> 7c200b78 780404a0 2ba408ff 41bd001c e87e80a8 3884ff00 48058d21 60000000
> 480054cd 60000000 e93e80b0 e92900b8 <e8090000> f8410028 e9690010 e8490008
I'm not getting a crash but I am getting this:
start_kernel(): bug: interrupts were enabled *very* early, fixing it
...and you're getting a null pointer access here (in do_IRQ):
irq = ppc_md.get_irq();
Are we somehow enabling interrupts before we've setup ppc_md.get_irq?
Mikey
>
> 2) The kernel panic on second attempt
>
> Unable to handle kernel paging request for data at address 0x00000000
> Faulting instruction address: 0xc00000000000cb2c
> Oops: Kernel access of bad area, sig: 11 [#1]
> SMP NR_CPUS=128 NUMA pSeries
> Modules linked in:
> NIP: c00000000000cb2c LR: c00000000000caf8 CTR: 0000000000014a99
> REGS: c00000000068f410 TRAP: 0300 Not tainted (2.6.25-rc3-mm1-autotest)
> MSR: 8000000000001032 <ME,IR,DR> CR: 28000044 XER: 00000001
> DAR: 0000000000000000, DSISR: 0000000040000000
> TASK = c0000000005c8590[0] 'swapper' THREAD: c00000000068c000 CPU: 0
> GPR00: c00000000068f690 c00000000068f690 c00000000068e690 0000000000000000
> GPR04: 0000000000003690 0000000000537672 c000000001ad59c0 c000000000594000
> GPR08: c0000000005c9300 0000000000000000 c000000000591090 c00000000068c000
> GPR12: 8000000000009032 c0000000005c9300 0000000000000000 0000000000000000
> GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> GPR20: 0000000000230000 0000000000000000 0000000000ffffff 0000000001000000
> GPR24: 0000000000001000 0000000001000000 0000000000001000 0000000000000000
> GPR28: 0000000000000000 c0000000005889c8 c000000000639be8 c000000001000000
> NIP [c00000000000cb2c] .do_IRQ+0x74/0x1c4
> LR [c00000000000caf8] .do_IRQ+0x40/0x1c4
> Call Trace:
> [c00000000068f690] [c00000000000caf8] .do_IRQ+0x40/0x1c4 (unreliable)
> [c00000000068f730] [c000000000004790] hardware_interrupt_entry+0x18/0x1c
> --- Exception: 501 at .memset+0x80/0xfc
> LR = .__alloc_bootmem_core+0x39c/0x3dc
> [c00000000068fa20] [c000000000641a78] sysctl_pernet_ops+0x108e0/0x1d6e0 (unre
liable)
> [c00000000068fae0] [c00000000057237c] .__alloc_bootmem_node+0x38/0x8c
> [c00000000068fb80] [c0000000003c48dc] .__earlyonly_bootmem_alloc+0x24/0x3c
> [c00000000068fc00] [c0000000003d885c] .vmemmap_populate+0x7c/0xf4
> [c00000000068fc90] [c0000000003d9b6c] .sparse_mem_map_populate+0x38/0x64
> [c00000000068fd10] [c000000000573ec4] .sparse_early_mem_map_alloc+0x54/0x98
> [c00000000068fda0] [c000000000573f70] .sparse_init+0x68/0x148
> [c00000000068fe40] [c00000000055b9ec] .setup_arch+0x1c4/0x240
> [c00000000068fee0] [c000000000552690] .start_kernel+0xdc/0x414
> [c00000000068ff90] [c000000000008594] .start_here_common+0x54/0xc0
> Instruction dump:
> 7c200b78 780404a0 2ba408ff 41bd001c e87e80a8 3884ff00 48058d21 60000000
> 480054cd 60000000 e93e80b0 e92900b8 <e8090000> f8410028 e9690010 e8490008
>
> 3) Third attempt kernel booted up but had the following call trace 264 times
while running
> test
>
> Badness at include/linux/gfp.h:110
> NIP: c0000000000b4ff0 LR: c0000000000b4fa0 CTR: c00000000019cdb4
> REGS: c000000009edf250 TRAP: 0700 Not tainted (2.6.25-rc3-mm1-autotest)
> MSR: 8000000000029032 <EE,ME,IR,DR> CR: 22024042 XER: 20000003
> TASK = c000000009062140[548] 'kjournald' THREAD: c000000009edc000 CPU: 0
> NIP [c0000000000b4ff0] .get_page_from_freelist+0x29c/0x898
> LR [c0000000000b4fa0] .get_page_from_freelist+0x24c/0x898
> Call Trace:
> [c000000009edf5f0] [c0000000000b56e4] .__alloc_pages_internal+0xf8/0x470
> [c000000009edf6e0] [c0000000000e0458] .kmem_getpages+0x8c/0x194
> [c000000009edf770] [c0000000000e1050] .fallback_alloc+0x194/0x254
> [c000000009edf820] [c0000000000e14b0] .kmem_cache_alloc+0xd8/0x144
> [c000000009edf8c0] [c0000000001fe0f8] .radix_tree_preload+0x50/0xd4
> [c000000009edf960] [c0000000000ad048] .add_to_page_cache+0x38/0x12c
> [c000000009edfa00] [c0000000000ad158] .add_to_page_cache_lru+0x1c/0x4c
> [c000000009edfa90] [c0000000000add58] .find_or_create_page+0x60/0xa8
> [c000000009edfb30] [c00000000011e478] .__getblk+0x140/0x310
> [c000000009edfc00] [c0000000001b78c4] .journal_get_descriptor_buffer+0x44/0xd
8
> [c000000009edfca0] [c0000000001b236c] .journal_commit_transaction+0x948/0x159
0
> [c000000009edfe00] [c0000000001b585c] .kjournald+0xf4/0x2ac
> [c000000009edff00] [c00000000007ff4c] .kthread+0x84/0xd0
> [c000000009edff90] [c000000000028900] .kernel_thread+0x4c/0x68
> Instruction dump:
> 7dc57378 48009575 60000000 2fa30000 419e0490 56c902d8 3c000018 7dd907b4
> 7ad2c7e2 7f890000 7c000026 5400fffe <0b000000> e93e8128 3b000000 80090000
> --
> Thanks & Regards,
> Kamalesh Babulal,
> Linux Technology Center,
> IBM, ISTL.
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc ()
2008-03-04 14:40 ` Michael Neuling
@ 2008-03-04 18:33 ` Andrew Morton
2008-03-05 8:23 ` Benjamin Herrenschmidt
2008-03-06 0:03 ` Benjamin Herrenschmidt
0 siblings, 2 replies; 76+ messages in thread
From: Andrew Morton @ 2008-03-04 18:33 UTC (permalink / raw)
To: Michael Neuling
Cc: Kamalesh Babulal, linuxppc-dev, linux-kernel, Matthew Wilcox
On Tue, 04 Mar 2008 15:40:56 +0100 Michael Neuling <mikey@neuling.org> wrote:
> In message <47CD4AB3.3080409@linux.vnet.ibm.com> you wrote:
> > Hi Andrew,
> >
> > The 2.6.25-rc3-mm1 kernel panics while bootup on power box. The machine boote
> d up
> > without the panic on the third attempt, but badness call trace were seen whil
> e running
> > tests
> >
> > 1) The kernel panic on first attempt
> >
> > Unable to handle kernel paging request for data at address 0x00000000
> > Faulting instruction address: 0xc00000000000cb2c
> > Oops: Kernel access of bad area, sig: 11 [#1]
> > SMP NR_CPUS=128 NUMA pSeries
> > Modules linked in:
> > NIP: c00000000000cb2c LR: c00000000000caf8 CTR: 0000000000000226
> > REGS: c00000000068f360 TRAP: 0300 Not tainted (2.6.25-rc3-mm1-autotest)
> > MSR: 8000000000001032 <ME,IR,DR> CR: 28000024 XER: 20000001
> > DAR: 0000000000000000, DSISR: 0000000040000000
> > TASK = c0000000005c8590[0] 'swapper' THREAD: c00000000068c000 CPU: 0
> > GPR00: c00000000068f5e0 c00000000068f5e0 c00000000068e690 0000000000000000
> > GPR04: 00000000000035e0 000000000087264e c000000008011280 c000000000594000
> > GPR08: c0000000005c9300 0000000000000000 c000000000591090 c00000000068c000
> > GPR12: 8000000000009032 c0000000005c9300 0000000000000000 0000000000000000
> > GPR16: 0000000000000000 0000000000000000 0000000000008000 0000000000000000
> > GPR20: 0000000000000000 0000000000000000 000000000000007f 0000000000018000
> > GPR24: 0000000000000001 0000000000000080 0000000000000018 0000000000000000
> > GPR28: 0000000000000c00 c000000000588988 c000000000639be8 c000000008001c00
> > NIP [c00000000000cb2c] .do_IRQ+0x74/0x1c4
> > LR [c00000000000caf8] .do_IRQ+0x40/0x1c4
> > Call Trace:
> > [c00000000068f5e0] [c00000000000caf8] .do_IRQ+0x40/0x1c4 (unreliable)
> > [c00000000068f680] [c000000000004790] hardware_interrupt_entry+0x18/0x1c
> > --- Exception: 501 at .memset+0x70/0xfc
> > LR = .__alloc_bootmem_core+0x39c/0x3dc
> > [c00000000068f970] [c00000000068fa10] init_thread_union+0x3a10/0x4000 (unreli
> able)
> > [c00000000068fa30] [c00000000057237c] .__alloc_bootmem_node+0x38/0x8c
> > [c00000000068fad0] [c0000000003c477c] .zone_wait_table_init+0x74/0x108
> > [c00000000068fb60] [c0000000003d9058] .init_currently_empty_zone+0x40/0x11c
> > [c00000000068fc00] [c0000000003d94c8] .free_area_init_node+0x394/0x3fc
> > [c00000000068fcf0] [c00000000057314c] .free_area_init_nodes+0x2d8/0x364
> > [c00000000068fd90] [c00000000056682c] .paging_init+0x40/0x58
> > [c00000000068fe40] [c00000000055ba34] .setup_arch+0x20c/0x240
> > [c00000000068fee0] [c000000000552690] .start_kernel+0xdc/0x414
> > [c00000000068ff90] [c000000000008594] .start_here_common+0x54/0xc0
> > Instruction dump:
> > 7c200b78 780404a0 2ba408ff 41bd001c e87e80a8 3884ff00 48058d21 60000000
> > 480054cd 60000000 e93e80b0 e92900b8 <e8090000> f8410028 e9690010 e8490008
>
> I'm not getting a crash but I am getting this:
>
> start_kernel(): bug: interrupts were enabled *very* early, fixing it
>
> ...and you're getting a null pointer access here (in do_IRQ):
>
> irq = ppc_md.get_irq();
>
> Are we somehow enabling interrupts before we've setup ppc_md.get_irq?
>
Yes, we are - it's the semaphore rewrite which is doing this in
start_kernel(). It's being discussed.
Enabling interrupts too early on powerpc was discovered to be fatal on
powerpc years ago. It looks like that remains the case.
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc ()
2008-03-04 18:33 ` Andrew Morton
@ 2008-03-05 8:23 ` Benjamin Herrenschmidt
2008-03-06 0:03 ` Benjamin Herrenschmidt
1 sibling, 0 replies; 76+ messages in thread
From: Benjamin Herrenschmidt @ 2008-03-05 8:23 UTC (permalink / raw)
To: Andrew Morton
Cc: Michael Neuling, Matthew Wilcox, linuxppc-dev, linux-kernel,
Kamalesh Babulal
On Tue, 2008-03-04 at 10:33 -0800, Andrew Morton wrote:
> > Are we somehow enabling interrupts before we've setup
> ppc_md.get_irq?
> >
>
> Yes, we are - it's the semaphore rewrite which is doing this in
> start_kernel(). It's being discussed.
>
> Enabling interrupts too early on powerpc was discovered to be fatal on
> powerpc years ago. It looks like that remains the case.
Yes, it is and will probably always be. All that semaphore mucking
around that hard-enables interrupts is just asking for trouble (and on
more than just powerpc... heh, how do you do if your main interrupt
controller hasn't even been initialized yet ?)
Ben.
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc ()
2008-03-04 18:33 ` Andrew Morton
2008-03-05 8:23 ` Benjamin Herrenschmidt
@ 2008-03-06 0:03 ` Benjamin Herrenschmidt
2008-03-06 0:44 ` Andrew Morton
1 sibling, 1 reply; 76+ messages in thread
From: Benjamin Herrenschmidt @ 2008-03-06 0:03 UTC (permalink / raw)
To: Andrew Morton
Cc: Michael Neuling, Kamalesh Babulal, linuxppc-dev, linux-kernel,
Matthew Wilcox
> Yes, we are - it's the semaphore rewrite which is doing this in
> start_kernel(). It's being discussed.
>
> Enabling interrupts too early on powerpc was discovered to be fatal on
> powerpc years ago. It looks like that remains the case.
Regarding these issues. I could make it non fatal and just WARN_ON,
provided that I have a way to differentiate legal vs. illegal calls
to local_irq_enable(). We already have that function mostly out of
line in C code due to our lazy irq disabling scheme, so the overhead of
testing some global kernel state would be minimum here.
However, I don't see anything around init/main.c:start_kernel() that I
can use. What do you reckon here we should do ? Add some kind of global
we set before calling local_irq_enable() ? Or make early_boot_irqs_on()
do that generically
It's currently defined as an empty inline without CONFIG_TRACE_IRQFLAGS
but we could make it set a flag instead.
I'm pretty sure other archs have similar problems, especially in the
embedded world where you are booted with random junk firmwares that may
leave devices, interrupt controllers etc... in random state, and
enabling incoming IRQs before the arch code properly initializes the
main interrupt controller can be fatal. I know at least of an ARM board
I worked on a while ago that had a similar issues.
On ppc32, unfortunately, our local_irq_enable/restore are nice inlines
that whack the appropriate MSR bits directly, thus adding a test for a
global flag would add some bloat/overhead that I'd like to avoid, at
least until we decide to also do lazy disabling on those, if ever...
Cheers,
Ben.
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc ()
2008-03-06 0:03 ` Benjamin Herrenschmidt
@ 2008-03-06 0:44 ` Andrew Morton
2008-03-06 0:52 ` Benjamin Herrenschmidt
0 siblings, 1 reply; 76+ messages in thread
From: Andrew Morton @ 2008-03-06 0:44 UTC (permalink / raw)
To: benh; +Cc: mikey, kamalesh, linuxppc-dev, linux-kernel, willy
On Thu, 06 Mar 2008 11:03:31 +1100
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> > Yes, we are - it's the semaphore rewrite which is doing this in
> > start_kernel(). It's being discussed.
> >
> > Enabling interrupts too early on powerpc was discovered to be fatal on
> > powerpc years ago. It looks like that remains the case.
>
> Regarding these issues. I could make it non fatal and just WARN_ON,
> provided that I have a way to differentiate legal vs. illegal calls
> to local_irq_enable().
And local_irq_restore() and various other things.
> We already have that function mostly out of
> line in C code due to our lazy irq disabling scheme, so the overhead of
> testing some global kernel state would be minimum here.
>
> However, I don't see anything around init/main.c:start_kernel() that I
> can use. What do you reckon here we should do ? Add some kind of global
> we set before calling local_irq_enable() ? Or make early_boot_irqs_on()
> do that generically
>
> It's currently defined as an empty inline without CONFIG_TRACE_IRQFLAGS
> but we could make it set a flag instead.
>
> I'm pretty sure other archs have similar problems, especially in the
> embedded world where you are booted with random junk firmwares that may
> leave devices, interrupt controllers etc... in random state, and
> enabling incoming IRQs before the arch code properly initializes the
> main interrupt controller can be fatal. I know at least of an ARM board
> I worked on a while ago that had a similar issues.
>
> On ppc32, unfortunately, our local_irq_enable/restore are nice inlines
> that whack the appropriate MSR bits directly, thus adding a test for a
> global flag would add some bloat/overhead that I'd like to avoid, at
> least until we decide to also do lazy disabling on those, if ever...
I'd have thought that the way to do this would be to add it to lockdep -
lockdep already has all the infrastructure and code sites to do this.
Set some special flag saying its-ok-to-enable-interrupts-now and test that
in lockdep.
akpm:/usr/src/25> grep LOCKDEP arch/powerpc/Kconfig
akpm:/usr/src/25>
losers ;)
Still, doing it for
akpm:/usr/src/25> grep -l LOCKDEP arch/*/Kconfig
arch/arm/Kconfig
arch/avr32/Kconfig
arch/mips/Kconfig
arch/s390/Kconfig
arch/sh/Kconfig
arch/sparc64/Kconfig
arch/um/Kconfig
arch/x86/Kconfig
should give pretty good coverage.
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc ()
2008-03-06 0:44 ` Andrew Morton
@ 2008-03-06 0:52 ` Benjamin Herrenschmidt
0 siblings, 0 replies; 76+ messages in thread
From: Benjamin Herrenschmidt @ 2008-03-06 0:52 UTC (permalink / raw)
To: Andrew Morton; +Cc: mikey, kamalesh, linuxppc-dev, linux-kernel, willy
On Wed, 2008-03-05 at 16:44 -0800, Andrew Morton wrote:
> On Thu, 06 Mar 2008 11:03:31 +1100
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> >
> > > Yes, we are - it's the semaphore rewrite which is doing this in
> > > start_kernel(). It's being discussed.
> > >
> > > Enabling interrupts too early on powerpc was discovered to be fatal on
> > > powerpc years ago. It looks like that remains the case.
> >
> > Regarding these issues. I could make it non fatal and just WARN_ON,
> > provided that I have a way to differentiate legal vs. illegal calls
> > to local_irq_enable().
>
> And local_irq_restore() and various other things.
Yes, on powerpc 64 bits, they all go down to one C function that does
the lazy enable/disable, so it would be easy to deal with. 32 bits
doesn't have it that simple tho.
> I'd have thought that the way to do this would be to add it to lockdep -
> lockdep already has all the infrastructure and code sites to do this.
>
> Set some special flag saying its-ok-to-enable-interrupts-now and test that
> in lockdep.
Ok.
> akpm:/usr/src/25> grep LOCKDEP arch/powerpc/Kconfig
> akpm:/usr/src/25>
>
> losers ;)
I have lockdep patches for powerpc 32 and 64 bits. They aren't upstream
yet as they need a bit more beating up and there's at least one machine
that doesn't seem to like them, so I'm working on just that. That's a
good idea to add the test to lockdep tho, I'll see what I can do.
> Still, doing it for
>
> akpm:/usr/src/25> grep -l LOCKDEP arch/*/Kconfig
> arch/arm/Kconfig
> arch/avr32/Kconfig
> arch/mips/Kconfig
> arch/s390/Kconfig
> arch/sh/Kconfig
> arch/sparc64/Kconfig
> arch/um/Kconfig
> arch/x86/Kconfig
>
> should give pretty good coverage.
Ben.
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc ()
2008-03-04 13:12 ` [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc () Kamalesh Babulal
2008-03-04 14:40 ` Michael Neuling
@ 2008-03-04 18:36 ` Andrew Morton
2008-03-04 18:47 ` Pekka Enberg
2008-03-04 19:18 ` Pekka Enberg
2008-03-05 8:22 ` Benjamin Herrenschmidt
2 siblings, 2 replies; 76+ messages in thread
From: Andrew Morton @ 2008-03-04 18:36 UTC (permalink / raw)
To: Kamalesh Babulal
Cc: linux-kernel, linuxppc-dev, Andy Whitcroft, linux-mm,
Pekka Enberg, Mel Gorman
On Tue, 04 Mar 2008 18:42:19 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
> 3) Third attempt kernel booted up but had the following call trace 264 times while running
> test
>
> Badness at include/linux/gfp.h:110
> NIP: c0000000000b4ff0 LR: c0000000000b4fa0 CTR: c00000000019cdb4
> REGS: c000000009edf250 TRAP: 0700 Not tainted (2.6.25-rc3-mm1-autotest)
> MSR: 8000000000029032 <EE,ME,IR,DR> CR: 22024042 XER: 20000003
> TASK = c000000009062140[548] 'kjournald' THREAD: c000000009edc000 CPU: 0
> NIP [c0000000000b4ff0] .get_page_from_freelist+0x29c/0x898
> LR [c0000000000b4fa0] .get_page_from_freelist+0x24c/0x898
> Call Trace:
> [c000000009edf5f0] [c0000000000b56e4] .__alloc_pages_internal+0xf8/0x470
> [c000000009edf6e0] [c0000000000e0458] .kmem_getpages+0x8c/0x194
> [c000000009edf770] [c0000000000e1050] .fallback_alloc+0x194/0x254
> [c000000009edf820] [c0000000000e14b0] .kmem_cache_alloc+0xd8/0x144
> [c000000009edf8c0] [c0000000001fe0f8] .radix_tree_preload+0x50/0xd4
> [c000000009edf960] [c0000000000ad048] .add_to_page_cache+0x38/0x12c
> [c000000009edfa00] [c0000000000ad158] .add_to_page_cache_lru+0x1c/0x4c
> [c000000009edfa90] [c0000000000add58] .find_or_create_page+0x60/0xa8
> [c000000009edfb30] [c00000000011e478] .__getblk+0x140/0x310
> [c000000009edfc00] [c0000000001b78c4] .journal_get_descriptor_buffer+0x44/0xd8
> [c000000009edfca0] [c0000000001b236c] .journal_commit_transaction+0x948/0x1590
> [c000000009edfe00] [c0000000001b585c] .kjournald+0xf4/0x2ac
> [c000000009edff00] [c00000000007ff4c] .kthread+0x84/0xd0
> [c000000009edff90] [c000000000028900] .kernel_thread+0x4c/0x68
> Instruction dump:
> 7dc57378 48009575 60000000 2fa30000 419e0490 56c902d8 3c000018 7dd907b4
> 7ad2c7e2 7f890000 7c000026 5400fffe <0b000000> e93e8128 3b000000 80090000
/* Convert GFP flags to their corresponding migrate type */
static inline int allocflags_to_migratetype(gfp_t gfp_flags)
{
WARN_ON((gfp_flags & GFP_MOVABLE_MASK) == GFP_MOVABLE_MASK);
Mel, Pekka: would you have some head-scratching time for this one please?
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc ()
2008-03-04 18:36 ` Andrew Morton
@ 2008-03-04 18:47 ` Pekka Enberg
2008-03-04 19:18 ` Pekka Enberg
1 sibling, 0 replies; 76+ messages in thread
From: Pekka Enberg @ 2008-03-04 18:47 UTC (permalink / raw)
To: Andrew Morton
Cc: Kamalesh Babulal, linux-kernel, linuxppc-dev, Andy Whitcroft,
linux-mm, Mel Gorman
On Tue, 04 Mar 2008 18:42:19 +0530 Kamalesh Babulal
<kamalesh@linux.vnet.ibm.com> wrote:
> > 3) Third attempt kernel booted up but had the following call trace 264 times while running
> > test
> >
> > Badness at include/linux/gfp.h:110
> > NIP: c0000000000b4ff0 LR: c0000000000b4fa0 CTR: c00000000019cdb4
> > REGS: c000000009edf250 TRAP: 0700 Not tainted (2.6.25-rc3-mm1-autotest)
> > MSR: 8000000000029032 <EE,ME,IR,DR> CR: 22024042 XER: 20000003
> > TASK = c000000009062140[548] 'kjournald' THREAD: c000000009edc000 CPU: 0
> > NIP [c0000000000b4ff0] .get_page_from_freelist+0x29c/0x898
> > LR [c0000000000b4fa0] .get_page_from_freelist+0x24c/0x898
> > Call Trace:
> > [c000000009edf5f0] [c0000000000b56e4] .__alloc_pages_internal+0xf8/0x470
> > [c000000009edf6e0] [c0000000000e0458] .kmem_getpages+0x8c/0x194
> > [c000000009edf770] [c0000000000e1050] .fallback_alloc+0x194/0x254
> > [c000000009edf820] [c0000000000e14b0] .kmem_cache_alloc+0xd8/0x144
> > [c000000009edf8c0] [c0000000001fe0f8] .radix_tree_preload+0x50/0xd4
> > [c000000009edf960] [c0000000000ad048] .add_to_page_cache+0x38/0x12c
> > [c000000009edfa00] [c0000000000ad158] .add_to_page_cache_lru+0x1c/0x4c
> > [c000000009edfa90] [c0000000000add58] .find_or_create_page+0x60/0xa8
> > [c000000009edfb30] [c00000000011e478] .__getblk+0x140/0x310
> > [c000000009edfc00] [c0000000001b78c4] .journal_get_descriptor_buffer+0x44/0xd8
> > [c000000009edfca0] [c0000000001b236c] .journal_commit_transaction+0x948/0x1590
> > [c000000009edfe00] [c0000000001b585c] .kjournald+0xf4/0x2ac
> > [c000000009edff00] [c00000000007ff4c] .kthread+0x84/0xd0
> > [c000000009edff90] [c000000000028900] .kernel_thread+0x4c/0x68
> > Instruction dump:
> > 7dc57378 48009575 60000000 2fa30000 419e0490 56c902d8 3c000018 7dd907b4
> > 7ad2c7e2 7f890000 7c000026 5400fffe <0b000000> e93e8128 3b000000 80090000
On Tue, Mar 4, 2008 at 8:36 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> /* Convert GFP flags to their corresponding migrate type */
> static inline int allocflags_to_migratetype(gfp_t gfp_flags)
> {
> WARN_ON((gfp_flags & GFP_MOVABLE_MASK) == GFP_MOVABLE_MASK);
>
> Mel, Pekka: would you have some head-scratching time for this one please?
Sure. Just to double-check, this is with SLAB, right? Do you see this with SLUB?
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc ()
2008-03-04 18:36 ` Andrew Morton
2008-03-04 18:47 ` Pekka Enberg
@ 2008-03-04 19:18 ` Pekka Enberg
1 sibling, 0 replies; 76+ messages in thread
From: Pekka Enberg @ 2008-03-04 19:18 UTC (permalink / raw)
To: Andrew Morton
Cc: Kamalesh Babulal, linux-kernel, linuxppc-dev, Andy Whitcroft,
linux-mm, Mel Gorman
Andrew Morton wrote:
> > [c000000009edf5f0] [c0000000000b56e4] .__alloc_pages_internal+0xf8/0x470
> > [c000000009edf6e0] [c0000000000e0458] .kmem_getpages+0x8c/0x194
> > [c000000009edf770] [c0000000000e1050] .fallback_alloc+0x194/0x254
> > [c000000009edf820] [c0000000000e14b0] .kmem_cache_alloc+0xd8/0x144
> > [c000000009edf8c0] [c0000000001fe0f8] .radix_tree_preload+0x50/0xd4
> > [c000000009edf960] [c0000000000ad048] .add_to_page_cache+0x38/0x12c
> > [c000000009edfa00] [c0000000000ad158] .add_to_page_cache_lru+0x1c/0x4c
> > [c000000009edfa90] [c0000000000add58] .find_or_create_page+0x60/0xa8
> > [c000000009edfb30] [c00000000011e478] .__getblk+0x140/0x310
> > [c000000009edfc00] [c0000000001b78c4] .journal_get_descriptor_buffer+0x44/0xd8
> > [c000000009edfca0] [c0000000001b236c] .journal_commit_transaction+0x948/0x1590
> > [c000000009edfe00] [c0000000001b585c] .kjournald+0xf4/0x2ac
> > [c000000009edff00] [c00000000007ff4c] .kthread+0x84/0xd0
> > [c000000009edff90] [c000000000028900] .kernel_thread+0x4c/0x68
> > Instruction dump:
> > 7dc57378 48009575 60000000 2fa30000 419e0490 56c902d8 3c000018 7dd907b4
> > 7ad2c7e2 7f890000 7c000026 5400fffe <0b000000> e93e8128 3b000000 80090000
>
> /* Convert GFP flags to their corresponding migrate type */
> static inline int allocflags_to_migratetype(gfp_t gfp_flags)
> {
> WARN_ON((gfp_flags & GFP_MOVABLE_MASK) == GFP_MOVABLE_MASK);
>
> Mel, Pekka: would you have some head-scratching time for this one please?
What we have is __getblk() -> __getblk_slow() -> grow_buffers() ->
grow_dev_page() doing find_or_create_page() with __GFP_MOVABLE set. That
path then eventually does radix_tree_preload -> kmem_cache_alloc() to a
cache that has SLAB_RECLAIM_ACCOUNT set which implies __GFP_RECLAIMABLE
(for both SLAB and SLUB). So we oops there.
I suspect the WARN_ON() is bogus although I really don't know that part
of the code all too well. Mel?
Pekka
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc ()
2008-03-04 13:12 ` [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc () Kamalesh Babulal
2008-03-04 14:40 ` Michael Neuling
2008-03-04 18:36 ` Andrew Morton
@ 2008-03-05 8:22 ` Benjamin Herrenschmidt
2 siblings, 0 replies; 76+ messages in thread
From: Benjamin Herrenschmidt @ 2008-03-05 8:22 UTC (permalink / raw)
To: Kamalesh Babulal; +Cc: Andrew Morton, linuxppc-dev, linux-kernel
On Tue, 2008-03-04 at 18:42 +0530, Kamalesh Babulal wrote:
> Hi Andrew,
>
> The 2.6.25-rc3-mm1 kernel panics while bootup on power box. The machine booted up
> without the panic on the third attempt, but badness call trace were seen while running
> tests
We are taking a HW interrupt ... we aren't supposed to take HW
interrupts that early during boot afaik.
Is it yet another case of somebody hard-enabling interrupts with
local_irq_enable() ?
Ben.
> 1) The kernel panic on first attempt
>
> Unable to handle kernel paging request for data at address 0x00000000
> Faulting instruction address: 0xc00000000000cb2c
> Oops: Kernel access of bad area, sig: 11 [#1]
> SMP NR_CPUS=128 NUMA pSeries
> Modules linked in:
> NIP: c00000000000cb2c LR: c00000000000caf8 CTR: 0000000000000226
> REGS: c00000000068f360 TRAP: 0300 Not tainted (2.6.25-rc3-mm1-autotest)
> MSR: 8000000000001032 <ME,IR,DR> CR: 28000024 XER: 20000001
> DAR: 0000000000000000, DSISR: 0000000040000000
> TASK = c0000000005c8590[0] 'swapper' THREAD: c00000000068c000 CPU: 0
> GPR00: c00000000068f5e0 c00000000068f5e0 c00000000068e690 0000000000000000
> GPR04: 00000000000035e0 000000000087264e c000000008011280 c000000000594000
> GPR08: c0000000005c9300 0000000000000000 c000000000591090 c00000000068c000
> GPR12: 8000000000009032 c0000000005c9300 0000000000000000 0000000000000000
> GPR16: 0000000000000000 0000000000000000 0000000000008000 0000000000000000
> GPR20: 0000000000000000 0000000000000000 000000000000007f 0000000000018000
> GPR24: 0000000000000001 0000000000000080 0000000000000018 0000000000000000
> GPR28: 0000000000000c00 c000000000588988 c000000000639be8 c000000008001c00
> NIP [c00000000000cb2c] .do_IRQ+0x74/0x1c4
> LR [c00000000000caf8] .do_IRQ+0x40/0x1c4
> Call Trace:
> [c00000000068f5e0] [c00000000000caf8] .do_IRQ+0x40/0x1c4 (unreliable)
> [c00000000068f680] [c000000000004790] hardware_interrupt_entry+0x18/0x1c
> --- Exception: 501 at .memset+0x70/0xfc
> LR = .__alloc_bootmem_core+0x39c/0x3dc
> [c00000000068f970] [c00000000068fa10] init_thread_union+0x3a10/0x4000 (unreliable)
> [c00000000068fa30] [c00000000057237c] .__alloc_bootmem_node+0x38/0x8c
> [c00000000068fad0] [c0000000003c477c] .zone_wait_table_init+0x74/0x108
> [c00000000068fb60] [c0000000003d9058] .init_currently_empty_zone+0x40/0x11c
> [c00000000068fc00] [c0000000003d94c8] .free_area_init_node+0x394/0x3fc
> [c00000000068fcf0] [c00000000057314c] .free_area_init_nodes+0x2d8/0x364
> [c00000000068fd90] [c00000000056682c] .paging_init+0x40/0x58
> [c00000000068fe40] [c00000000055ba34] .setup_arch+0x20c/0x240
> [c00000000068fee0] [c000000000552690] .start_kernel+0xdc/0x414
> [c00000000068ff90] [c000000000008594] .start_here_common+0x54/0xc0
> Instruction dump:
> 7c200b78 780404a0 2ba408ff 41bd001c e87e80a8 3884ff00 48058d21 60000000
> 480054cd 60000000 e93e80b0 e92900b8 <e8090000> f8410028 e9690010 e8490008
>
> 2) The kernel panic on second attempt
>
> Unable to handle kernel paging request for data at address 0x00000000
> Faulting instruction address: 0xc00000000000cb2c
> Oops: Kernel access of bad area, sig: 11 [#1]
> SMP NR_CPUS=128 NUMA pSeries
> Modules linked in:
> NIP: c00000000000cb2c LR: c00000000000caf8 CTR: 0000000000014a99
> REGS: c00000000068f410 TRAP: 0300 Not tainted (2.6.25-rc3-mm1-autotest)
> MSR: 8000000000001032 <ME,IR,DR> CR: 28000044 XER: 00000001
> DAR: 0000000000000000, DSISR: 0000000040000000
> TASK = c0000000005c8590[0] 'swapper' THREAD: c00000000068c000 CPU: 0
> GPR00: c00000000068f690 c00000000068f690 c00000000068e690 0000000000000000
> GPR04: 0000000000003690 0000000000537672 c000000001ad59c0 c000000000594000
> GPR08: c0000000005c9300 0000000000000000 c000000000591090 c00000000068c000
> GPR12: 8000000000009032 c0000000005c9300 0000000000000000 0000000000000000
> GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> GPR20: 0000000000230000 0000000000000000 0000000000ffffff 0000000001000000
> GPR24: 0000000000001000 0000000001000000 0000000000001000 0000000000000000
> GPR28: 0000000000000000 c0000000005889c8 c000000000639be8 c000000001000000
> NIP [c00000000000cb2c] .do_IRQ+0x74/0x1c4
> LR [c00000000000caf8] .do_IRQ+0x40/0x1c4
> Call Trace:
> [c00000000068f690] [c00000000000caf8] .do_IRQ+0x40/0x1c4 (unreliable)
> [c00000000068f730] [c000000000004790] hardware_interrupt_entry+0x18/0x1c
> --- Exception: 501 at .memset+0x80/0xfc
> LR = .__alloc_bootmem_core+0x39c/0x3dc
> [c00000000068fa20] [c000000000641a78] sysctl_pernet_ops+0x108e0/0x1d6e0 (unreliable)
> [c00000000068fae0] [c00000000057237c] .__alloc_bootmem_node+0x38/0x8c
> [c00000000068fb80] [c0000000003c48dc] .__earlyonly_bootmem_alloc+0x24/0x3c
> [c00000000068fc00] [c0000000003d885c] .vmemmap_populate+0x7c/0xf4
> [c00000000068fc90] [c0000000003d9b6c] .sparse_mem_map_populate+0x38/0x64
> [c00000000068fd10] [c000000000573ec4] .sparse_early_mem_map_alloc+0x54/0x98
> [c00000000068fda0] [c000000000573f70] .sparse_init+0x68/0x148
> [c00000000068fe40] [c00000000055b9ec] .setup_arch+0x1c4/0x240
> [c00000000068fee0] [c000000000552690] .start_kernel+0xdc/0x414
> [c00000000068ff90] [c000000000008594] .start_here_common+0x54/0xc0
> Instruction dump:
> 7c200b78 780404a0 2ba408ff 41bd001c e87e80a8 3884ff00 48058d21 60000000
> 480054cd 60000000 e93e80b0 e92900b8 <e8090000> f8410028 e9690010 e8490008
>
> 3) Third attempt kernel booted up but had the following call trace 264 times while running
> test
>
> Badness at include/linux/gfp.h:110
> NIP: c0000000000b4ff0 LR: c0000000000b4fa0 CTR: c00000000019cdb4
> REGS: c000000009edf250 TRAP: 0700 Not tainted (2.6.25-rc3-mm1-autotest)
> MSR: 8000000000029032 <EE,ME,IR,DR> CR: 22024042 XER: 20000003
> TASK = c000000009062140[548] 'kjournald' THREAD: c000000009edc000 CPU: 0
> NIP [c0000000000b4ff0] .get_page_from_freelist+0x29c/0x898
> LR [c0000000000b4fa0] .get_page_from_freelist+0x24c/0x898
> Call Trace:
> [c000000009edf5f0] [c0000000000b56e4] .__alloc_pages_internal+0xf8/0x470
> [c000000009edf6e0] [c0000000000e0458] .kmem_getpages+0x8c/0x194
> [c000000009edf770] [c0000000000e1050] .fallback_alloc+0x194/0x254
> [c000000009edf820] [c0000000000e14b0] .kmem_cache_alloc+0xd8/0x144
> [c000000009edf8c0] [c0000000001fe0f8] .radix_tree_preload+0x50/0xd4
> [c000000009edf960] [c0000000000ad048] .add_to_page_cache+0x38/0x12c
> [c000000009edfa00] [c0000000000ad158] .add_to_page_cache_lru+0x1c/0x4c
> [c000000009edfa90] [c0000000000add58] .find_or_create_page+0x60/0xa8
> [c000000009edfb30] [c00000000011e478] .__getblk+0x140/0x310
> [c000000009edfc00] [c0000000001b78c4] .journal_get_descriptor_buffer+0x44/0xd8
> [c000000009edfca0] [c0000000001b236c] .journal_commit_transaction+0x948/0x1590
> [c000000009edfe00] [c0000000001b585c] .kjournald+0xf4/0x2ac
> [c000000009edff00] [c00000000007ff4c] .kthread+0x84/0xd0
> [c000000009edff90] [c000000000028900] .kernel_thread+0x4c/0x68
> Instruction dump:
> 7dc57378 48009575 60000000 2fa30000 419e0490 56c902d8 3c000018 7dd907b4
> 7ad2c7e2 7f890000 7c000026 5400fffe <0b000000> e93e8128 3b000000 80090000
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 (IDE)
2008-03-04 9:19 2.6.25-rc3-mm1 Andrew Morton
2008-03-04 11:59 ` 2.6.25-rc3-mm1 Cornelia Huck
2008-03-04 13:12 ` [BUG] 2.6.25-rc3-mm1 kernel panic while bootup on powerpc () Kamalesh Babulal
@ 2008-03-04 16:35 ` Randy Dunlap
2008-03-06 21:14 ` Bartlomiej Zolnierkiewicz
2008-03-04 16:45 ` 2.6.25-rc3-mm1 (CCISS) Randy Dunlap
` (9 subsequent siblings)
12 siblings, 1 reply; 76+ messages in thread
From: Randy Dunlap @ 2008-03-04 16:35 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, Bart
On Tue, 4 Mar 2008 01:19:28 -0800 Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
i386 allmodconfig gives me this:
ERROR: "probe_4drives" [drivers/ide/ide-core.ko] undefined!
---
~Randy
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: 2.6.25-rc3-mm1 (CCISS)
2008-03-04 9:19 2.6.25-rc3-mm1 Andrew Morton
` (2 preceding siblings ...)
2008-03-04 16:35 ` 2.6.25-rc3-mm1 (IDE) Randy Dunlap
@ 2008-03-04 16:45 ` Randy Dunlap
2008-03-04 17:02 ` Miller, Mike (OS Dev)
2008-03-04 19:12 ` [PATCH 2.6.25-rc3-mm1] fix ext2 borkage Hugh Dickins
` (8 subsequent siblings)
12 siblings, 1 reply; 76+ messages in thread
From: Randy Dunlap @ 2008-03-04 16:45 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, mike.miller, iss_storagedev
On Tue, 4 Mar 2008 01:19:28 -0800 Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
With
CONFIG_BLK_CPQ_DA=m
CONFIG_BLK_CPQ_CISS_DA=m
# CONFIG_CISS_SCSI_TAPE is not set
I'm getting
In file included from drivers/block/cciss.c:230:
drivers/block/cciss_scsi.c:1498:38: error: macro parameters must be comma-separated
drivers/block/cciss.c: In function 'cciss_seq_show_header':
drivers/block/cciss.c:271: error: implicit declaration of function 'cciss_seq_tape_report'
drivers/block/cciss.c: In function 'cciss_proc_write':
drivers/block/cciss.c:392: error: implicit declaration of function 'cciss_engage_scsi'
make[2]: *** [drivers/block/cciss.o] Error 1
make[1]: *** [drivers/block] Error 2
make[1]: *** Waiting for unfinished jobs....
---
~Randy
^ permalink raw reply [flat|nested] 76+ messages in thread* RE: 2.6.25-rc3-mm1 (CCISS)
2008-03-04 16:45 ` 2.6.25-rc3-mm1 (CCISS) Randy Dunlap
@ 2008-03-04 17:02 ` Miller, Mike (OS Dev)
2008-03-04 17:14 ` Randy Dunlap
0 siblings, 1 reply; 76+ messages in thread
From: Miller, Mike (OS Dev) @ 2008-03-04 17:02 UTC (permalink / raw)
To: Randy Dunlap, Andrew Morton; +Cc: linux-kernel@vger.kernel.org, ISS StorageDev
Randy wrote:
>
> On Tue, 4 Mar 2008 01:19:28 -0800 Andrew Morton wrote:
>
> >
> >
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-r
> > c3/2.6.25-rc3-mm1/
>
> With
> CONFIG_BLK_CPQ_DA=m
> CONFIG_BLK_CPQ_CISS_DA=m
> # CONFIG_CISS_SCSI_TAPE is not set
>
> I'm getting
> In file included from drivers/block/cciss.c:230:
> drivers/block/cciss_scsi.c:1498:38: error: macro parameters
> must be comma-separated
> drivers/block/cciss.c: In function 'cciss_seq_show_header':
> drivers/block/cciss.c:271: error: implicit declaration of
> function 'cciss_seq_tape_report'
> drivers/block/cciss.c: In function 'cciss_proc_write':
> drivers/block/cciss.c:392: error: implicit declaration of
> function 'cciss_engage_scsi'
> make[2]: *** [drivers/block/cciss.o] Error 1
> make[1]: *** [drivers/block] Error 2
> make[1]: *** Waiting for unfinished jobs....
>
> ---
Randy,
It looks like you have the original broken patch. I resubmitted and I think Jens picked up the fixed patch but I don't know where it is... :(
-- mikem
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 (CCISS)
2008-03-04 17:02 ` Miller, Mike (OS Dev)
@ 2008-03-04 17:14 ` Randy Dunlap
2008-03-04 18:14 ` Jens Axboe
0 siblings, 1 reply; 76+ messages in thread
From: Randy Dunlap @ 2008-03-04 17:14 UTC (permalink / raw)
To: Miller, Mike (OS Dev)
Cc: Andrew Morton, linux-kernel@vger.kernel.org, ISS StorageDev,
Jens Axboe
Miller, Mike (OS Dev) wrote:
> Randy wrote:
>> On Tue, 4 Mar 2008 01:19:28 -0800 Andrew Morton wrote:
>>
>>>
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-r
>>> c3/2.6.25-rc3-mm1/
>> With
>> CONFIG_BLK_CPQ_DA=m
>> CONFIG_BLK_CPQ_CISS_DA=m
>> # CONFIG_CISS_SCSI_TAPE is not set
>>
>> I'm getting
>> In file included from drivers/block/cciss.c:230:
>> drivers/block/cciss_scsi.c:1498:38: error: macro parameters
>> must be comma-separated
>> drivers/block/cciss.c: In function 'cciss_seq_show_header':
>> drivers/block/cciss.c:271: error: implicit declaration of
>> function 'cciss_seq_tape_report'
>> drivers/block/cciss.c: In function 'cciss_proc_write':
>> drivers/block/cciss.c:392: error: implicit declaration of
>> function 'cciss_engage_scsi'
>> make[2]: *** [drivers/block/cciss.o] Error 1
>> make[1]: *** [drivers/block] Error 2
>> make[1]: *** Waiting for unfinished jobs....
>>
>> ---
> Randy,
> It looks like you have the original broken patch. I resubmitted and I think Jens picked up the fixed patch but I don't know where it is... :(
s/you/latest -mm/
I thought that this had been fixed, but I can't find it either... :(
Jens, did you queue a patch for this?
--
~Randy
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 (CCISS)
2008-03-04 17:14 ` Randy Dunlap
@ 2008-03-04 18:14 ` Jens Axboe
0 siblings, 0 replies; 76+ messages in thread
From: Jens Axboe @ 2008-03-04 18:14 UTC (permalink / raw)
To: Randy Dunlap
Cc: Miller, Mike (OS Dev), Andrew Morton,
linux-kernel@vger.kernel.org, ISS StorageDev
On Tue, Mar 04 2008, Randy Dunlap wrote:
> Miller, Mike (OS Dev) wrote:
> >Randy wrote:
> >>On Tue, 4 Mar 2008 01:19:28 -0800 Andrew Morton wrote:
> >>
> >>>
> >>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-r
> >>>c3/2.6.25-rc3-mm1/
> >>With
> >>CONFIG_BLK_CPQ_DA=m
> >>CONFIG_BLK_CPQ_CISS_DA=m
> >># CONFIG_CISS_SCSI_TAPE is not set
> >>
> >>I'm getting
> >>In file included from drivers/block/cciss.c:230:
> >>drivers/block/cciss_scsi.c:1498:38: error: macro parameters
> >>must be comma-separated
> >>drivers/block/cciss.c: In function 'cciss_seq_show_header':
> >>drivers/block/cciss.c:271: error: implicit declaration of
> >>function 'cciss_seq_tape_report'
> >>drivers/block/cciss.c: In function 'cciss_proc_write':
> >>drivers/block/cciss.c:392: error: implicit declaration of
> >>function 'cciss_engage_scsi'
> >>make[2]: *** [drivers/block/cciss.o] Error 1
> >>make[1]: *** [drivers/block] Error 2
> >>make[1]: *** Waiting for unfinished jobs....
> >>
> >>---
> >Randy,
> >It looks like you have the original broken patch. I resubmitted and I
> >think Jens picked up the fixed patch but I don't know where it is... :(
>
> s/you/latest -mm/
>
> I thought that this had been fixed, but I can't find it either... :(
>
> Jens, did you queue a patch for this?
I did, here:
http://git.kernel.dk/?p=linux-2.6-block.git;a=commit;h=89b6e743788516491846724d7ef89bcac7ac9c99
--
Jens Axboe
^ permalink raw reply [flat|nested] 76+ messages in thread
* [PATCH 2.6.25-rc3-mm1] fix ext2 borkage
2008-03-04 9:19 2.6.25-rc3-mm1 Andrew Morton
` (3 preceding siblings ...)
2008-03-04 16:45 ` 2.6.25-rc3-mm1 (CCISS) Randy Dunlap
@ 2008-03-04 19:12 ` Hugh Dickins
2008-03-04 19:20 ` [BUG] 2.6.25-rc3-mm1 kernel bug while running libhugetlbfs Kamalesh Babulal
` (7 subsequent siblings)
12 siblings, 0 replies; 76+ messages in thread
From: Hugh Dickins @ 2008-03-04 19:12 UTC (permalink / raw)
To: Andrew Morton; +Cc: Christoph Lameter, linux-kernel
use-page_cache_xxx-in-ext2.patch gave me lots of EXT2-fs error (device
loop0): ext2_find_entry: dir 52629 size 5120 exceeds block count 2
so I stopped it quickly. Creating a directory entry was muddling up the
directory and the linked inode, writing directory page out to the latter.
Signed-off-by: Hugh Dickins <hugh@veritas.com>
---
fs/ext2/dir.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- 2.6.25-rc3-mm1/fs/ext2/dir.c 2008-03-04 11:37:47.000000000 +0000
+++ linux/fs/ext2/dir.c 2008-03-04 18:25:24.000000000 +0000
@@ -472,7 +472,7 @@ void ext2_set_link(struct inode *dir, st
int ext2_add_link (struct dentry *dentry, struct inode *inode)
{
struct inode *dir = dentry->d_parent->d_inode;
- struct address_space *mapping = inode->i_mapping;
+ struct address_space *mapping = dir->i_mapping;
const char *name = dentry->d_name.name;
int namelen = dentry->d_name.len;
unsigned chunk_size = ext2_chunk_size(dir);
^ permalink raw reply [flat|nested] 76+ messages in thread* [BUG] 2.6.25-rc3-mm1 kernel bug while running libhugetlbfs
2008-03-04 9:19 2.6.25-rc3-mm1 Andrew Morton
` (4 preceding siblings ...)
2008-03-04 19:12 ` [PATCH 2.6.25-rc3-mm1] fix ext2 borkage Hugh Dickins
@ 2008-03-04 19:20 ` Kamalesh Babulal
2008-03-04 19:51 ` Andrew Morton
2008-03-04 20:24 ` 2.6.25-rc3-mm1 (wakeup) Randy Dunlap
` (6 subsequent siblings)
12 siblings, 1 reply; 76+ messages in thread
From: Kamalesh Babulal @ 2008-03-04 19:20 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linuxppc-dev, Andy Whitcroft, Balbir Singh
Hi Andrew,
kernel bug is triggered while running libhugetlbfs test with 2.6.25-rc3-mm1 kernel
over the x86 and power machines.
------------[ cut here ]------------
kernel BUG at mm/hugetlb.c:295!
invalid opcode: 0000 [#1] SMP
last sysfs file: /sys/devices/system/node/possible
Modules linked in:
Pid: 5484, comm: counters Not tainted (2.6.25-rc3-mm1-autokern1 #1)
EIP: 0060:[<c10535cf>] EFLAGS: 00010202 CPU: 0
EIP is at alloc_buddy_huge_page+0x7a/0xb0
EAX: c13acd01 EBX: f7d3a000 ECX: 00000000 EDX: 00006363
ESI: 00000001 EDI: 00000000 EBP: 00000000 ESP: f5539ebc
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process counters (pid: 5484, ti=f5538000 task=f60afa20 task.ti=f5538000)
Stack: 00000001 c1053669 fffffff4 00000001 f5539ecc f5539ecc 00000001 fffffff4
f55d0e78 00000001 c105480c 00000001 00200000 c1054875 00000000 f54426c0
00200000 00000000 f54426c0 c10b0fb8 fffffff4 00200000 00000000 f55d0e78
Call Trace:
[<c1053669>] gather_surplus_pages+0x64/0x16d
[<c105480c>] hugetlb_acct_memory+0x1e/0x4a
[<c1054875>] hugetlb_reserve_pages+0x3d/0x6b
[<c10b0fb8>] hugetlbfs_file_mmap+0x9b/0xe1
[<c104bf9f>] mmap_region+0x1dc/0x3ae
[<c104bd42>] do_mmap_pgoff+0x27f/0x28e
[<c1005af2>] sys_mmap2+0x5a/0x78
[<c10029fa>] syscall_call+0x7/0xb
=======================
Code: c1 e8 ed 27 1c 00 85 db 74 41 83 7b 04 00 75 10 68 c0 93 27 c1 e8 02 92 fc ff 58 e8 c1 02 fb ff f0 ff 4b 04 0f 94 c0 84 c0 74 04 <0f> 0b eb fe c7 43 38 3e 33 05 c1 8b 03 c1 e8 1c ff 04 85 60 ce
EIP: [<c10535cf>] alloc_buddy_huge_page+0x7a/0xb0 SS:ESP 0068:f5539ebc
---[ end trace 5a47484f8fe93a33 ]---
------------[ cut here ]------------
cpu 0x3: Vector: 700 (Program Check) at [c0000000fb277740]
pc: c0000000000c6f54: .alloc_buddy_huge_page+0x120/0x1dc
lr: c0000000000c6f20: .alloc_buddy_huge_page+0xec/0x1dc
sp: c0000000fb2779c0
msr: 8000000000029032
current = 0xc0000000fc4cae90
paca = 0xc0000000004fae80
pid = 6828, comm = counters
kernel BUG at mm/hugetlb.c:295!
enter ? for help
[c0000000fb277a50] c0000000000c70e8 .hugetlb_acct_memory+0xd8/0x374
[c0000000fb277b10] c0000000000c769c .hugetlb_reserve_pages+0x184/0x2b0
[c0000000fb277bc0] c00000000018c950 .hugetlbfs_file_mmap+0xec/0x160
[c0000000fb277c70] c0000000000bc280 .mmap_region+0x254/0x4d4
[c0000000fb277d80] c00000000000b1b8 .sys_mmap+0xa4/0x104
[c0000000fb277e30] c00000000000872c syscall_exit+0x0/0x40
--- Exception: c01 (System Call) at 000004000019e528
SP (fffffcd4eb0) is in userspace
3:mon>
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: [BUG] 2.6.25-rc3-mm1 kernel bug while running libhugetlbfs
2008-03-04 19:20 ` [BUG] 2.6.25-rc3-mm1 kernel bug while running libhugetlbfs Kamalesh Babulal
@ 2008-03-04 19:51 ` Andrew Morton
2008-03-04 22:01 ` Adam Litke
0 siblings, 1 reply; 76+ messages in thread
From: Andrew Morton @ 2008-03-04 19:51 UTC (permalink / raw)
To: Kamalesh Babulal; +Cc: linux-kernel, linuxppc-dev, apw, balbir, Adam Litke
On Wed, 05 Mar 2008 00:50:17 +0530
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
> Hi Andrew,
>
> kernel bug is triggered while running libhugetlbfs test with 2.6.25-rc3-mm1 kernel
> over the x86 and power machines.
>
> ------------[ cut here ]------------
> kernel BUG at mm/hugetlb.c:295!
> invalid opcode: 0000 [#1] SMP
> last sysfs file: /sys/devices/system/node/possible
> Modules linked in:
>
> Pid: 5484, comm: counters Not tainted (2.6.25-rc3-mm1-autokern1 #1)
> EIP: 0060:[<c10535cf>] EFLAGS: 00010202 CPU: 0
> EIP is at alloc_buddy_huge_page+0x7a/0xb0
> EAX: c13acd01 EBX: f7d3a000 ECX: 00000000 EDX: 00006363
> ESI: 00000001 EDI: 00000000 EBP: 00000000 ESP: f5539ebc
> DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
> Process counters (pid: 5484, ti=f5538000 task=f60afa20 task.ti=f5538000)
> Stack: 00000001 c1053669 fffffff4 00000001 f5539ecc f5539ecc 00000001 fffffff4
> f55d0e78 00000001 c105480c 00000001 00200000 c1054875 00000000 f54426c0
> 00200000 00000000 f54426c0 c10b0fb8 fffffff4 00200000 00000000 f55d0e78
> Call Trace:
> [<c1053669>] gather_surplus_pages+0x64/0x16d
> [<c105480c>] hugetlb_acct_memory+0x1e/0x4a
> [<c1054875>] hugetlb_reserve_pages+0x3d/0x6b
> [<c10b0fb8>] hugetlbfs_file_mmap+0x9b/0xe1
> [<c104bf9f>] mmap_region+0x1dc/0x3ae
> [<c104bd42>] do_mmap_pgoff+0x27f/0x28e
> [<c1005af2>] sys_mmap2+0x5a/0x78
> [<c10029fa>] syscall_call+0x7/0xb
> =======================
> Code: c1 e8 ed 27 1c 00 85 db 74 41 83 7b 04 00 75 10 68 c0 93 27 c1 e8 02 92 fc ff 58 e8 c1 02 fb ff f0 ff 4b 04 0f 94 c0 84 c0 74 04 <0f> 0b eb fe c7 43 38 3e 33 05 c1 8b 03 c1 e8 1c ff 04 85 60 ce
> EIP: [<c10535cf>] alloc_buddy_huge_page+0x7a/0xb0 SS:ESP 0068:f5539ebc
> ---[ end trace 5a47484f8fe93a33 ]---
>
>
Please send Adam a copy of that libhugetlbfs test ;)
hugetlb-correct-page-count-for-surplus-huge-pages.patch adds:
if (page) {
/*
* This page is now managed by the hugetlb allocator and has
* no users -- drop the buddy allocator's reference.
*/
int page_count = put_page_testzero(page);
BUG_ON(page_count != 0);
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: [BUG] 2.6.25-rc3-mm1 kernel bug while running libhugetlbfs
2008-03-04 19:51 ` Andrew Morton
@ 2008-03-04 22:01 ` Adam Litke
2008-03-05 7:52 ` Kamalesh Babulal
0 siblings, 1 reply; 76+ messages in thread
From: Adam Litke @ 2008-03-04 22:01 UTC (permalink / raw)
To: Andrew Morton; +Cc: Kamalesh Babulal, linux-kernel, linuxppc-dev, apw, balbir
On Tue, 2008-03-04 at 11:51 -0800, Andrew Morton wrote:
> hugetlb-correct-page-count-for-surplus-huge-pages.patch adds:
>
> if (page) {
> /*
> * This page is now managed by the hugetlb allocator and has
> * no users -- drop the buddy allocator's reference.
> */
> int page_count = put_page_testzero(page);
> BUG_ON(page_count != 0);
>
>
Ugh I got bitten by put_page_testzero(). When it returns 1, the page
count is zero (not the page count).
My initial version had a BUG_ON() with side-effects. When a reviewer
pointed it out, I thought I could fix the patch up on its way out the
door. I have self-administered my punishment. This patch will fix it:
Signed-off-by: Adam Litke <agl@us.ibm.com>
--- mm/hugetlb.c.orig 2008-03-04 13:36:30.000000000 -0800
+++ mm/hugetlb.c 2008-03-04 13:39:30.000000000 -0800
@@ -291,8 +291,8 @@ static struct page *alloc_buddy_huge_pag
* This page is now managed by the hugetlb allocator and has
* no users -- drop the buddy allocator's reference.
*/
- int page_count = put_page_testzero(page);
- BUG_ON(page_count != 0);
+ put_page_testzero(page);
+ VM_BUG_ON(page_count(page));
nid = page_to_nid(page);
set_compound_page_dtor(page, free_huge_page);
/*
--
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: [BUG] 2.6.25-rc3-mm1 kernel bug while running libhugetlbfs
2008-03-04 22:01 ` Adam Litke
@ 2008-03-05 7:52 ` Kamalesh Babulal
0 siblings, 0 replies; 76+ messages in thread
From: Kamalesh Babulal @ 2008-03-05 7:52 UTC (permalink / raw)
To: Adam Litke; +Cc: Andrew Morton, linux-kernel, linuxppc-dev, apw, balbir
Adam Litke wrote:
> On Tue, 2008-03-04 at 11:51 -0800, Andrew Morton wrote:
>> hugetlb-correct-page-count-for-surplus-huge-pages.patch adds:
>>
>> if (page) {
>> /*
>> * This page is now managed by the hugetlb allocator and has
>> * no users -- drop the buddy allocator's reference.
>> */
>> int page_count = put_page_testzero(page);
>> BUG_ON(page_count != 0);
>>
>>
>
> Ugh I got bitten by put_page_testzero(). When it returns 1, the page
> count is zero (not the page count).
>
> My initial version had a BUG_ON() with side-effects. When a reviewer
> pointed it out, I thought I could fix the patch up on its way out the
> door. I have self-administered my punishment. This patch will fix it:
Hi Adam,
Thanks the patch fixes the kernel bug while running the libhugetlbfs test.
Tested-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
>
> Signed-off-by: Adam Litke <agl@us.ibm.com>
>
> --- mm/hugetlb.c.orig 2008-03-04 13:36:30.000000000 -0800
> +++ mm/hugetlb.c 2008-03-04 13:39:30.000000000 -0800
> @@ -291,8 +291,8 @@ static struct page *alloc_buddy_huge_pag
> * This page is now managed by the hugetlb allocator and has
> * no users -- drop the buddy allocator's reference.
> */
> - int page_count = put_page_testzero(page);
> - BUG_ON(page_count != 0);
> + put_page_testzero(page);
> + VM_BUG_ON(page_count(page));
> nid = page_to_nid(page);
> set_compound_page_dtor(page, free_huge_page);
> /*
>
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 (wakeup)
2008-03-04 9:19 2.6.25-rc3-mm1 Andrew Morton
` (5 preceding siblings ...)
2008-03-04 19:20 ` [BUG] 2.6.25-rc3-mm1 kernel bug while running libhugetlbfs Kamalesh Babulal
@ 2008-03-04 20:24 ` Randy Dunlap
2008-03-04 22:33 ` Rafael J. Wysocki
2008-03-04 21:26 ` 2.6.25-rc3-mm1 (9p docs) Randy Dunlap
` (5 subsequent siblings)
12 siblings, 1 reply; 76+ messages in thread
From: Randy Dunlap @ 2008-03-04 20:24 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, rjw
On Tue, 4 Mar 2008 01:19:28 -0800 Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
Both x86_64 and i386 builds throw these messages at me:
LD arch/x86/kernel/acpi/realmode/wakeup.elf
ld: warning: dot moved backwards before `.text'
ld: warning: dot moved backwards before `.text'
ld: warning: dot moved backwards before `.text'
OBJCOPY arch/x86/kernel/acpi/realmode/wakeup.bin
---
~Randy
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: 2.6.25-rc3-mm1 (wakeup)
2008-03-04 20:24 ` 2.6.25-rc3-mm1 (wakeup) Randy Dunlap
@ 2008-03-04 22:33 ` Rafael J. Wysocki
2008-03-05 7:40 ` Sam Ravnborg
0 siblings, 1 reply; 76+ messages in thread
From: Rafael J. Wysocki @ 2008-03-04 22:33 UTC (permalink / raw)
To: Randy Dunlap; +Cc: Andrew Morton, linux-kernel, H. Peter Anvin, Sam Ravnborg
On Tuesday, 4 of March 2008, Randy Dunlap wrote:
> On Tue, 4 Mar 2008 01:19:28 -0800 Andrew Morton wrote:
>
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
>
> Both x86_64 and i386 builds throw these messages at me:
>
> LD arch/x86/kernel/acpi/realmode/wakeup.elf
> ld: warning: dot moved backwards before `.text'
> ld: warning: dot moved backwards before `.text'
> ld: warning: dot moved backwards before `.text'
> OBJCOPY arch/x86/kernel/acpi/realmode/wakeup.bin
I think I saw something like this on a system with an "older" toolchain.
I'm not seeing it on openSUSE 10.3, though (using gcc 4.2.1).
Added CCs to the experts.
Thanks,
Rafael
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 (wakeup)
2008-03-04 22:33 ` Rafael J. Wysocki
@ 2008-03-05 7:40 ` Sam Ravnborg
0 siblings, 0 replies; 76+ messages in thread
From: Sam Ravnborg @ 2008-03-05 7:40 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Randy Dunlap, Andrew Morton, linux-kernel, H. Peter Anvin
On Tue, Mar 04, 2008 at 11:33:12PM +0100, Rafael J. Wysocki wrote:
> On Tuesday, 4 of March 2008, Randy Dunlap wrote:
> > On Tue, 4 Mar 2008 01:19:28 -0800 Andrew Morton wrote:
> >
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
> >
> > Both x86_64 and i386 builds throw these messages at me:
> >
> > LD arch/x86/kernel/acpi/realmode/wakeup.elf
> > ld: warning: dot moved backwards before `.text'
> > ld: warning: dot moved backwards before `.text'
> > ld: warning: dot moved backwards before `.text'
> > OBJCOPY arch/x86/kernel/acpi/realmode/wakeup.bin
>
> I think I saw something like this on a system with an "older" toolchain.
> I'm not seeing it on openSUSE 10.3, though (using gcc 4.2.1).
>
> Added CCs to the experts.
Google turned up this post:
http://sourceware.org/ml/binutils/2006-08/msg00235.html
I have no time to dig more into it the next days.
Sam
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 (9p docs)
2008-03-04 9:19 2.6.25-rc3-mm1 Andrew Morton
` (6 preceding siblings ...)
2008-03-04 20:24 ` 2.6.25-rc3-mm1 (wakeup) Randy Dunlap
@ 2008-03-04 21:26 ` Randy Dunlap
2008-03-04 21:43 ` Eric Van Hensbergen
2008-03-05 7:21 ` 2.6.25-rc3-mm1 - PROFILE_LIKELY redux Valdis.Kletnieks
` (4 subsequent siblings)
12 siblings, 1 reply; 76+ messages in thread
From: Randy Dunlap @ 2008-03-04 21:26 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, ericvh
On Tue, 4 Mar 2008 01:19:28 -0800 Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
"make htmldocs" gives me:
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
make[1]: *** No rule to make target `Documentation/DocBook/9p-overview.eps', needed by `Documentation/DocBook/9p.xml'. Stop.
make: *** [htmldocs] Error 2
Are we missing the .eps and .png files?
---
~Randy
^ permalink raw reply [flat|nested] 76+ messages in thread* 2.6.25-rc3-mm1 - PROFILE_LIKELY redux..
2008-03-04 9:19 2.6.25-rc3-mm1 Andrew Morton
` (7 preceding siblings ...)
2008-03-04 21:26 ` 2.6.25-rc3-mm1 (9p docs) Randy Dunlap
@ 2008-03-05 7:21 ` Valdis.Kletnieks
2008-03-05 17:45 ` Andi Kleen
2008-03-05 10:51 ` prctl(0x8) -> EINVAL [Was: 2.6.25-rc3-mm1] Jiri Slaby
` (3 subsequent siblings)
12 siblings, 1 reply; 76+ messages in thread
From: Valdis.Kletnieks @ 2008-03-05 7:21 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 2207 bytes --]
On Tue, 04 Mar 2008 01:19:28 PST, Andrew Morton said:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
x86_64, mostly 64-bit userspace, Dell Latitude D820, T7200 Core2 Duo...
So I gave CONFIG_PROFILE_LIKELY another try, and this time the thing actually
booted and got into userspace, but stuff started dying in rc.sysinit.
According to dmesg, they all died at the same place:
[ 4.841459] rename_device[686]: segfault at ffffffffff7009be ip ffffffffff7009be sp 7fff7ccfb958 error 14
[ 4.842384] rename_device[984]: segfault at ffffffffff7009be ip ffffffffff7009be sp 7fffb6fe9c68 error 14
[ 4.843298] rename_device[981]: segfault at ffffffffff7009be ip ffffffffff7009be sp 7fffc18504c8 error 14
[ 4.844184] rename_device[983]: segfault at ffffffffff7009be ip ffffffffff7009be sp 7fff512c8f48 error 14
[ 6.099486] rename_device[1513]: segfault at ffffffffff7009be ip ffffffffff7009be sp 7fff47e88ad8 error 14
[ 5.769289] rename_device[1516]: segfault at ffffffffff7009be ip ffffffffff7009be sp 7fffa317edd8 error 14
[ 7.457229] fsck.ext3[1576]: segfault at ffffffffff7009be ip ffffffffff7009be sp 7fff3be947f8 error 14
(Note that not everything died - some renames, an fsck, and maybe I missed
something - but a lot of other stuff worked (dmesg, grep, cat, uname that I
ran, and a lot of things that rc.sysinit invoked - so that may tell us
something...)
/proc/self/maps says that's near:
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
And my System.map says:
ffffffff80855a0c A __bss_stop
ffffffff80855a0c A _end
ffffffffff600000 T vgettimeofday
ffffffffff600100 t vread_tsc
ffffffffff600122 t vread_hpet
ffffffffff600140 D __vsyscall_gtod_data
ffffffffff600400 T vtime
ffffffffff600800 T vgetcpu
ffffffffff600870 D __vgetcpu_mode
ffffffffff600880 D __jiffies
ffffffffff600c00 T venosys_1
ffffffffff700000 A VDSO64_PRELINK
ffffffffff7005b0 A VDSO64_jiffies
ffffffffff7005b8 A VDSO64_vgetcpu_mode
ffffffffff7005c0 A VDSO64_vsyscall_gtod_data
<file ends there>
So we're in the same 4K as the VDSO64_* values, but some 0x4fe past the
gtod_data. Anybody got a hint as to what the heck it was doing?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: 2.6.25-rc3-mm1 - PROFILE_LIKELY redux..
2008-03-05 7:21 ` 2.6.25-rc3-mm1 - PROFILE_LIKELY redux Valdis.Kletnieks
@ 2008-03-05 17:45 ` Andi Kleen
2008-03-05 18:02 ` Andrew Morton
2008-03-05 19:59 ` Valdis.Kletnieks
0 siblings, 2 replies; 76+ messages in thread
From: Andi Kleen @ 2008-03-05 17:45 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: Andrew Morton, linux-kernel
Valdis.Kletnieks@vt.edu writes:
>
> So we're in the same 4K as the VDSO64_* values, but some 0x4fe past the
> gtod_data. Anybody got a hint as to what the heck it was doing?
Try this patch:
Remove unlikelies in vsyscall path
Remove unlikely in vsyscall path that conflict with unlikely profiling.
The unlikelies shouldn't be needed anyways because gcc predicts
condition leading to early return as unlikely by default and
for the loops it shouldn't make much difference
Signed-off-by: Andi Kleen <ak@suse.de>
Index: linux/arch/x86/kernel/vsyscall_64.c
===================================================================
--- linux.orig/arch/x86/kernel/vsyscall_64.c
+++ linux/arch/x86/kernel/vsyscall_64.c
@@ -128,7 +128,7 @@ static __always_inline void do_vgettimeo
seq = read_seqbegin(&__vsyscall_gtod_data.lock);
vread = __vsyscall_gtod_data.clock.vread;
- if (unlikely(!__vsyscall_gtod_data.sysctl_enabled || !vread)) {
+ if (!__vsyscall_gtod_data.sysctl_enabled || !vread) {
gettimeofday(tv,NULL);
return;
}
@@ -169,7 +169,7 @@ time_t __vsyscall(1) vtime(time_t *t)
{
struct timeval tv;
time_t result;
- if (unlikely(!__vsyscall_gtod_data.sysctl_enabled))
+ if (!__vsyscall_gtod_data.sysctl_enabled)
return time_syscall(t);
vgettimeofday(&tv, NULL);
Index: linux/arch/x86/vdso/vclock_gettime.c
===================================================================
--- linux.orig/arch/x86/vdso/vclock_gettime.c
+++ linux/arch/x86/vdso/vclock_gettime.c
@@ -48,7 +48,7 @@ static noinline int do_realtime(struct t
ts->tv_sec = gtod->wall_time_sec;
ts->tv_nsec = gtod->wall_time_nsec;
ns = vgetns();
- } while (unlikely(read_seqretry(>od->lock, seq)));
+ } while (read_seqretry(>od->lock, seq));
timespec_add_ns(ts, ns);
return 0;
}
@@ -77,7 +77,7 @@ static noinline int do_monotonic(struct
ns = gtod->wall_time_nsec + vgetns();
secs += gtod->wall_to_monotonic.tv_sec;
ns += gtod->wall_to_monotonic.tv_nsec;
- } while (unlikely(read_seqretry(>od->lock, seq)));
+ } while (read_seqretry(>od->lock, seq));
vset_normalized_timespec(ts, secs, ns);
return 0;
}
@@ -105,7 +105,7 @@ int __vdso_gettimeofday(struct timeval *
sizeof(*tv) != sizeof(struct timespec));
do_realtime((struct timespec *)tv);
tv->tv_usec /= 1000;
- if (unlikely(tz != NULL)) {
+ if (tz != NULL) {
/* This relies on gcc inlining the memcpy. We'll notice
if it ever fails to do so. */
memcpy(tz, >od->sys_tz, sizeof(struct timezone));
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: 2.6.25-rc3-mm1 - PROFILE_LIKELY redux..
2008-03-05 17:45 ` Andi Kleen
@ 2008-03-05 18:02 ` Andrew Morton
2008-03-05 18:22 ` Andi Kleen
2008-03-05 22:26 ` Valdis.Kletnieks
2008-03-05 19:59 ` Valdis.Kletnieks
1 sibling, 2 replies; 76+ messages in thread
From: Andrew Morton @ 2008-03-05 18:02 UTC (permalink / raw)
To: Andi Kleen; +Cc: Valdis.Kletnieks, linux-kernel
On Wed, 05 Mar 2008 18:45:13 +0100 Andi Kleen <andi@firstfloor.org> wrote:
> Valdis.Kletnieks@vt.edu writes:
> >
> > So we're in the same 4K as the VDSO64_* values, but some 0x4fe past the
> > gtod_data. Anybody got a hint as to what the heck it was doing?
>
> Try this patch:
>
> Remove unlikelies in vsyscall path
>
> Remove unlikely in vsyscall path that conflict with unlikely profiling.
> The unlikelies shouldn't be needed anyways because gcc predicts
> condition leading to early return as unlikely by default and
> for the loops it shouldn't make much difference
>
> --- linux.orig/arch/x86/kernel/vsyscall_64.c
> +++ linux/arch/x86/kernel/vsyscall_64.c
> ...
> --- linux.orig/arch/x86/vdso/vclock_gettime.c
> +++ linux/arch/x86/vdso/vclock_gettime.c
Yes, but both those files now have:
/*
* likely and unlikely explode when used in vdso in combination with
* profile-likely-unlikely-macros.patch
*/
#undef likely
#define likely(x) (x)
#undef unlikely
#define unlikely(x) (x)
at the top, so it'll be something else. Perhaps a `likely' snuck in via an
inline in a header file. It would be better to add a #define DONT_DO_THAT
at the top of arch/x86/kernel/vsyscall_64.c and
arch/x86/vdso/vclock_gettime.c, then use that to defeat likely-profiling.
arch/x86/kernel/vsyscall_64.c | 11 ++---------
arch/x86/vdso/vclock_gettime.c | 11 ++---------
include/linux/compiler.h | 3 ++-
3 files changed, 6 insertions(+), 19 deletions(-)
diff -puN arch/x86/kernel/vsyscall_64.c~profile-likely-unlikely-macros-fix arch/x86/kernel/vsyscall_64.c
--- a/arch/x86/kernel/vsyscall_64.c~profile-likely-unlikely-macros-fix
+++ a/arch/x86/kernel/vsyscall_64.c
@@ -17,6 +17,8 @@
* want per guest time just set the kernel.vsyscall64 sysctl to 0.
*/
+#define SUPPRESS_LIKELY_PROFILING
+
#include <linux/time.h>
#include <linux/init.h>
#include <linux/kernel.h>
@@ -46,15 +48,6 @@
#define __syscall_clobber "r11","cx","memory"
/*
- * likely and unlikely explode when used in vdso in combination with
- * profile-likely-unlikely-macros.patch
- */
-#undef likely
-#define likely(x) (x)
-#undef unlikely
-#define unlikely(x) (x)
-
-/*
* vsyscall_gtod_data contains data that is :
* - readonly from vsyscalls
* - written by timer interrupt or systcl (/proc/sys/kernel/vsyscall64)
diff -puN arch/x86/vdso/vclock_gettime.c~profile-likely-unlikely-macros-fix arch/x86/vdso/vclock_gettime.c
--- a/arch/x86/vdso/vclock_gettime.c~profile-likely-unlikely-macros-fix
+++ a/arch/x86/vdso/vclock_gettime.c
@@ -9,6 +9,8 @@
* Also alternative() doesn't work.
*/
+#define SUPPRESS_LIKELY_PROFILING
+
#include <linux/kernel.h>
#include <linux/posix-timers.h>
#include <linux/time.h>
@@ -23,15 +25,6 @@
#define gtod vdso_vsyscall_gtod_data
-/*
- * likely and unlikely explode when used in vdso in combination with
- * profile-likely-unlikely-macros.patch
- */
-#undef likely
-#define likely(x) (x)
-#undef unlikely
-#define unlikely(x) (x)
-
static long vdso_fallback_gettime(long clock, struct timespec *ts)
{
long ret;
diff -puN include/linux/compiler.h~profile-likely-unlikely-macros-fix include/linux/compiler.h
--- a/include/linux/compiler.h~profile-likely-unlikely-macros-fix
+++ a/include/linux/compiler.h
@@ -51,7 +51,8 @@ extern void __chk_io_ptr(const volatile
# include <linux/compiler-intel.h>
#endif
-#if defined(CONFIG_PROFILE_LIKELY) && !(defined(CONFIG_MODULE_UNLOAD) && defined(MODULE))
+#if defined(CONFIG_PROFILE_LIKELY) && !defined(SUPPRESS_LIKELY_PROFILING) && \
+ !(defined(CONFIG_MODULE_UNLOAD) && defined(MODULE))
struct likeliness {
const char *func;
char *file;
_
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: 2.6.25-rc3-mm1 - PROFILE_LIKELY redux..
2008-03-05 18:02 ` Andrew Morton
@ 2008-03-05 18:22 ` Andi Kleen
2008-03-05 22:26 ` Valdis.Kletnieks
1 sibling, 0 replies; 76+ messages in thread
From: Andi Kleen @ 2008-03-05 18:22 UTC (permalink / raw)
To: Andrew Morton; +Cc: Andi Kleen, Valdis.Kletnieks, linux-kernel, sam
> Yes, but both those files now have:
>
> /*
> * likely and unlikely explode when used in vdso in combination with
> * profile-likely-unlikely-macros.patch
> */
> #undef likely
> #define likely(x) (x)
> #undef unlikely
> #define unlikely(x) (x)
>
> at the top, so it'll be something else. Perhaps a `likely' snuck in via an
I see.
> inline in a header file. It would be better to add a #define DONT_DO_THAT
I think you need to do it differently. Not undef/define, but set
some symbol that is checked by the unlikely profiler and it won't
enable itself with that symbol set. Then header files would be covered too.
> at the top of arch/x86/kernel/vsyscall_64.c and
> arch/x86/vdso/vclock_gettime.c, then use that to defeat likely-profiling.
Possible. The problem is that there are now vsyscall functions in
other files too, especially hpet_64.c and tsc_64.c
Perhaps this is something that should be just checked in modpost instead.
Any external references from the vsyscall section to another section
should be flag'ed as error (cc'ed Sam in case he wants to look at that)
-Andi
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - PROFILE_LIKELY redux..
2008-03-05 18:02 ` Andrew Morton
2008-03-05 18:22 ` Andi Kleen
@ 2008-03-05 22:26 ` Valdis.Kletnieks
2008-03-05 23:49 ` Andrew Morton
1 sibling, 1 reply; 76+ messages in thread
From: Valdis.Kletnieks @ 2008-03-05 22:26 UTC (permalink / raw)
To: Andrew Morton; +Cc: Andi Kleen, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 5423 bytes --]
On Wed, 05 Mar 2008 10:02:21 PST, Andrew Morton said:
> at the top, so it'll be something else. Perhaps a `likely' snuck in via an
> inline in a header file. It would be better to add a #define DONT_DO_THAT
> at the top of arch/x86/kernel/vsyscall_64.c and
> arch/x86/vdso/vclock_gettime.c, then use that to defeat likely-profiling.
>
> arch/x86/kernel/vsyscall_64.c | 11 ++---------
> arch/x86/vdso/vclock_gettime.c | 11 ++---------
> include/linux/compiler.h | 3 ++-
> 3 files changed, 6 insertions(+), 19 deletions(-)
Confirming that this patch works and my system goes multi-user cleanly.
Actual numbers after about 10 minutes of uptime:
% wc -l /proc/likely_prof
2635 /proc/likely_prof
% grep '^[^ ]' /proc/likely_prof
Likely Profiling Results
[+- ] Type | # True | # False | Function:Filename@Line
+unlikely | 1| 0 in_dev_get()@:include/linux/inetdevice.h@185
+unlikely | 513| 0 dst_input()@:include/net/dst.h@254
-likely | 0| 148 ip6_mc_input()@:net/ipv6/ip6_input.c@271
-likely | 0| 1 sock_error()@:include/net/sock.h@1211
-likely | 851| 1219 tcp_transmit_skb()@:net/ipv4/tcp_output.c@493
+unlikely | 1| 0 signal_pending()@:include/linux/sched.h@1927
-likely | 0| 1172946 audit_syscall_entry()@:kernel/auditsc.c@1522
+unlikely | 1172716| 0 syscall_trace_enter()@:arch/x86/kernel/ptrace.c@1556
-likely | 0| 1173020 audit_syscall_exit()@:kernel/auditsc.c@1551
+unlikely | 1172831| 0 syscall_trace_leave()@:arch/x86/kernel/ptrace.c@1573
-likely | 0| 1272 audit_alloc()@:kernel/auditsc.c@841
+unlikely | 3| 0 icmp_unreach()@:net/ipv4/icmp.c@773
+unlikely | 2| 1 nf_ct_attach()@:net/netfilter/core.c@230
-likely | 0| 2 dst_gc_task()@:net/core/dst.c@82
+unlikely | 143| 61 fput_light()@:include/linux/file.h@77
+unlikely | 892| 424 _read_unlock_irqrestore()@:kernel/spinlock.c@375
+unlikely | 28| 0 sched_move_task()@:kernel/sched.c@7835
+unlikely | 28| 0 sched_move_task()@:kernel/sched.c@7828
+unlikely | 108| 0 verify_export_symbols()@:kernel/module.c@1401
+unlikely | 313| 0 verify_export_symbols()@:kernel/module.c@1393
+unlikely | 14| 0 ll_front_merge_fn()@:block/blk-merge.c@347
-likely | 17| 1150 audit_free()@:kernel/auditsc.c@1428
-likely | 17| 1174290 audit_get_context()@:kernel/auditsc.c@711
+unlikely | 33| 0 inotify_find_update_watch()@:fs/inotify.c@591
+unlikely | 4360| 775 kill_pid_info()@:kernel/signal.c@1065
+unlikely | 7239| 2767 next_pidmap()@:kernel/pid.c@194
+unlikely | 42009| 33683 copy_pte_range()@:mm/memory.c@510
-likely | 0| 1 qh_completions()@:drivers/usb/host/ehci-q.c@368
+unlikely | 19934| 0 ll_back_merge_fn()@:block/blk-merge.c@309
-likely | 927| 2323 load_elf_binary()@:fs/binfmt_elf.c@896
+unlikely | 2435| 875 pmd_alloc()@:include/linux/mm.h@862
+unlikely | 13| 12 psmouse_interrupt()@:drivers/input/mouse/psmouse-base.c@296
+unlikely | 70| 25 psmouse_interrupt()@:drivers/input/mouse/psmouse-base.c@292
-likely | 20| 80 qh_completions()@:drivers/usb/host/ehci-q.c@415
-likely | 0| 30 qh_completions()@:drivers/usb/host/ehci-q.c@319
-likely | 5| 14 submit_async()@:drivers/usb/host/ehci-q.c@975
+unlikely | 19| 2 qh_append_tds()@:drivers/usb/host/ehci-q.c@876
-likely | 6| 15 atapi_drain_needed()@:drivers/ata/libata-scsi.c@846
+unlikely | 27395| 18153 add_timer_randomness()@:drivers/char/random.c@628
+unlikely | 34665| 19948 bio_phys_segments()@:fs/bio.c@226
-likely | 347| 678 clocksource_adjust()@:kernel/time/timekeeping.c@418
-likely | 1| 4 __ata_qc_from_tag()@:include/linux/libata.h@1319
-likely | 0| 15 __cancel_work_timer()@:kernel/workqueue.c@490
+unlikely | 15638| 1127 queue_delayed_work_on()@:kernel/workqueue.c@233
+unlikely | 2| 0 srcu_notifier_chain_register()@:kernel/notifier.c@419
+unlikely | 6502| 2429 queue_work()@:kernel/workqueue.c@171
+unlikely | 9| 2 blocking_notifier_chain_register()@:kernel/notifier.c@212
+unlikely | 13631| 0 pre_schedule_rt()@:kernel/sched_rt.c@961
+unlikely | 591400| 443725 __update_curr()@:kernel/sched_fair.c@313
+unlikely | 233625| 205658 __switch_to()@:arch/x86/kernel/process_64.c@656
+unlikely | 313057| 126225 __switch_to()@:arch/x86/kernel/process_64.c@641
+unlikely | 313053| 126225 __switch_to()@:arch/x86/kernel/process_64.c@637
+unlikely | 467383| 0 sched_info_switch()@:kernel/sched_stats.h@230
+unlikely | 188448| 13628 pick_next_task_rt()@:kernel/sched_rt.c@522
+unlikely | 240619| 0 sched_info_queued()@:kernel/sched_stats.h@188
-likely | 61| 644 ifind()@:fs/inode.c@798
+unlikely | 258562| 61703 scheduler_tick()@:kernel/sched.c@3756
-likely | 61220| 241529 acct_update_integrals()@:kernel/tsacct.c@120
+unlikely | 1189922| 902477 kfree()@:mm/slab.c@3785
+unlikely | 23| 0 __rmqueue_fallback()@:mm/page_alloc.c@812
+unlikely | 14376| 9655 rt_policy()@:kernel/sched.c@140
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - PROFILE_LIKELY redux..
2008-03-05 22:26 ` Valdis.Kletnieks
@ 2008-03-05 23:49 ` Andrew Morton
0 siblings, 0 replies; 76+ messages in thread
From: Andrew Morton @ 2008-03-05 23:49 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: andi, linux-kernel
On Wed, 05 Mar 2008 17:26:25 -0500
Valdis.Kletnieks@vt.edu wrote:
> On Wed, 05 Mar 2008 10:02:21 PST, Andrew Morton said:
>
> > at the top, so it'll be something else. Perhaps a `likely' snuck in via an
> > inline in a header file. It would be better to add a #define DONT_DO_THAT
> > at the top of arch/x86/kernel/vsyscall_64.c and
> > arch/x86/vdso/vclock_gettime.c, then use that to defeat likely-profiling.
> >
> > arch/x86/kernel/vsyscall_64.c | 11 ++---------
> > arch/x86/vdso/vclock_gettime.c | 11 ++---------
> > include/linux/compiler.h | 3 ++-
> > 3 files changed, 6 insertions(+), 19 deletions(-)
>
> Confirming that this patch works and my system goes multi-user cleanly.
Thanks.
> Actual numbers after about 10 minutes of uptime:
>
> % wc -l /proc/likely_prof
> 2635 /proc/likely_prof
> % grep '^[^ ]' /proc/likely_prof
> Likely Profiling Results
> [+- ] Type | # True | # False | Function:Filename@Line
> +unlikely | 1| 0 in_dev_get()@:include/linux/inetdevice.h@185
> +unlikely | 513| 0 dst_input()@:include/net/dst.h@254
> -likely | 0| 148 ip6_mc_input()@:net/ipv6/ip6_input.c@271
> -likely | 0| 1 sock_error()@:include/net/sock.h@1211
> -likely | 851| 1219 tcp_transmit_skb()@:net/ipv4/tcp_output.c@493
> +unlikely | 1| 0 signal_pending()@:include/linux/sched.h@1927
> -likely | 0| 1172946 audit_syscall_entry()@:kernel/auditsc.c@1522
> +unlikely | 1172716| 0 syscall_trace_enter()@:arch/x86/kernel/ptrace.c@1556
> -likely | 0| 1173020 audit_syscall_exit()@:kernel/auditsc.c@1551
> +unlikely | 1172831| 0 syscall_trace_leave()@:arch/x86/kernel/ptrace.c@1573
> -likely | 0| 1272 audit_alloc()@:kernel/auditsc.c@841
> +unlikely | 3| 0 icmp_unreach()@:net/ipv4/icmp.c@773
> +unlikely | 2| 1 nf_ct_attach()@:net/netfilter/core.c@230
> -likely | 0| 2 dst_gc_task()@:net/core/dst.c@82
> +unlikely | 143| 61 fput_light()@:include/linux/file.h@77
> +unlikely | 892| 424 _read_unlock_irqrestore()@:kernel/spinlock.c@375
> +unlikely | 28| 0 sched_move_task()@:kernel/sched.c@7835
> +unlikely | 28| 0 sched_move_task()@:kernel/sched.c@7828
> +unlikely | 108| 0 verify_export_symbols()@:kernel/module.c@1401
> +unlikely | 313| 0 verify_export_symbols()@:kernel/module.c@1393
> +unlikely | 14| 0 ll_front_merge_fn()@:block/blk-merge.c@347
> -likely | 17| 1150 audit_free()@:kernel/auditsc.c@1428
> -likely | 17| 1174290 audit_get_context()@:kernel/auditsc.c@711
> +unlikely | 33| 0 inotify_find_update_watch()@:fs/inotify.c@591
> +unlikely | 4360| 775 kill_pid_info()@:kernel/signal.c@1065
> +unlikely | 7239| 2767 next_pidmap()@:kernel/pid.c@194
> +unlikely | 42009| 33683 copy_pte_range()@:mm/memory.c@510
> -likely | 0| 1 qh_completions()@:drivers/usb/host/ehci-q.c@368
> +unlikely | 19934| 0 ll_back_merge_fn()@:block/blk-merge.c@309
> -likely | 927| 2323 load_elf_binary()@:fs/binfmt_elf.c@896
> +unlikely | 2435| 875 pmd_alloc()@:include/linux/mm.h@862
> +unlikely | 13| 12 psmouse_interrupt()@:drivers/input/mouse/psmouse-base.c@296
> +unlikely | 70| 25 psmouse_interrupt()@:drivers/input/mouse/psmouse-base.c@292
> -likely | 20| 80 qh_completions()@:drivers/usb/host/ehci-q.c@415
> -likely | 0| 30 qh_completions()@:drivers/usb/host/ehci-q.c@319
> -likely | 5| 14 submit_async()@:drivers/usb/host/ehci-q.c@975
> +unlikely | 19| 2 qh_append_tds()@:drivers/usb/host/ehci-q.c@876
> -likely | 6| 15 atapi_drain_needed()@:drivers/ata/libata-scsi.c@846
> +unlikely | 27395| 18153 add_timer_randomness()@:drivers/char/random.c@628
> +unlikely | 34665| 19948 bio_phys_segments()@:fs/bio.c@226
> -likely | 347| 678 clocksource_adjust()@:kernel/time/timekeeping.c@418
> -likely | 1| 4 __ata_qc_from_tag()@:include/linux/libata.h@1319
> -likely | 0| 15 __cancel_work_timer()@:kernel/workqueue.c@490
> +unlikely | 15638| 1127 queue_delayed_work_on()@:kernel/workqueue.c@233
> +unlikely | 2| 0 srcu_notifier_chain_register()@:kernel/notifier.c@419
> +unlikely | 6502| 2429 queue_work()@:kernel/workqueue.c@171
> +unlikely | 9| 2 blocking_notifier_chain_register()@:kernel/notifier.c@212
> +unlikely | 13631| 0 pre_schedule_rt()@:kernel/sched_rt.c@961
> +unlikely | 591400| 443725 __update_curr()@:kernel/sched_fair.c@313
> +unlikely | 233625| 205658 __switch_to()@:arch/x86/kernel/process_64.c@656
> +unlikely | 313057| 126225 __switch_to()@:arch/x86/kernel/process_64.c@641
> +unlikely | 313053| 126225 __switch_to()@:arch/x86/kernel/process_64.c@637
> +unlikely | 467383| 0 sched_info_switch()@:kernel/sched_stats.h@230
> +unlikely | 188448| 13628 pick_next_task_rt()@:kernel/sched_rt.c@522
> +unlikely | 240619| 0 sched_info_queued()@:kernel/sched_stats.h@188
> -likely | 61| 644 ifind()@:fs/inode.c@798
> +unlikely | 258562| 61703 scheduler_tick()@:kernel/sched.c@3756
> -likely | 61220| 241529 acct_update_integrals()@:kernel/tsacct.c@120
> +unlikely | 1189922| 902477 kfree()@:mm/slab.c@3785
> +unlikely | 23| 0 __rmqueue_fallback()@:mm/page_alloc.c@812
> +unlikely | 14376| 9655 rt_policy()@:kernel/sched.c@140
These are all the ones which we got wrong on your setup, yes?
I wonder if assuming that current->audit_context is NULL is realistic
nowadays.
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - PROFILE_LIKELY redux..
2008-03-05 17:45 ` Andi Kleen
2008-03-05 18:02 ` Andrew Morton
@ 2008-03-05 19:59 ` Valdis.Kletnieks
2008-03-05 21:56 ` Andi Kleen
1 sibling, 1 reply; 76+ messages in thread
From: Valdis.Kletnieks @ 2008-03-05 19:59 UTC (permalink / raw)
To: Andi Kleen; +Cc: Andrew Morton, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
On Wed, 05 Mar 2008 18:45:13 +0100, Andi Kleen said:
> Valdis.Kletnieks@vt.edu writes:
> >
> > So we're in the same 4K as the VDSO64_* values, but some 0x4fe past the
> > gtod_data. Anybody got a hint as to what the heck it was doing?
>
> Try this patch:
>
> Remove unlikelies in vsyscall path
Nope, sorry... same behavior. Apparently it's a (un)likely someplace
else...
I'm trying to figure out what's at 0x9be into the vdso, but not having
a lot of luck.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - PROFILE_LIKELY redux..
2008-03-05 19:59 ` Valdis.Kletnieks
@ 2008-03-05 21:56 ` Andi Kleen
0 siblings, 0 replies; 76+ messages in thread
From: Andi Kleen @ 2008-03-05 21:56 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: Andi Kleen, Andrew Morton, linux-kernel
On Wed, Mar 05, 2008 at 02:59:57PM -0500, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 05 Mar 2008 18:45:13 +0100, Andi Kleen said:
> > Valdis.Kletnieks@vt.edu writes:
> > >
> > > So we're in the same 4K as the VDSO64_* values, but some 0x4fe past the
> > > gtod_data. Anybody got a hint as to what the heck it was doing?
> >
> > Try this patch:
> >
> > Remove unlikelies in vsyscall path
>
> Nope, sorry... same behavior. Apparently it's a (un)likely someplace
> else...
>
> I'm trying to figure out what's at 0x9be into the vdso, but not having
> a lot of luck.
You can do objdump -Sr on the vdso/vsyscall object files and see
if there are any external references to unlikely related functions. If yes
the problem is in that function
-Andi
^ permalink raw reply [flat|nested] 76+ messages in thread
* prctl(0x8) -> EINVAL [Was: 2.6.25-rc3-mm1]
2008-03-04 9:19 2.6.25-rc3-mm1 Andrew Morton
` (8 preceding siblings ...)
2008-03-05 7:21 ` 2.6.25-rc3-mm1 - PROFILE_LIKELY redux Valdis.Kletnieks
@ 2008-03-05 10:51 ` Jiri Slaby
2008-03-05 10:59 ` Jiri Slaby
2008-03-05 14:06 ` Serge E. Hallyn
2008-03-05 13:04 ` 2.6.25-rc3-mm1 Pavel Emelyanov
` (2 subsequent siblings)
12 siblings, 2 replies; 76+ messages in thread
From: Jiri Slaby @ 2008-03-05 10:51 UTC (permalink / raw)
To: Andrew Morton
Cc: linux-kernel, Andrew G. Morgan, Serge Hallyn, James Morris,
Stephen Smalley, Paul Moore
On 03/04/2008 10:19 AM, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
> +capabilities-implement-per-process-securebits.patch
This probably causes userspace damage:
dbus:
prctl(0x8, 0x1, 0, 0, 0) = -1 EINVAL (Invalid argument)
named:
named: -u with Linux threads not supported: requires kernel support for
prctl(PR_SET_KEEPCAPS)
prctl(0x8, 0x1, 0, 0, 0) = -1 EINVAL (Invalid argument)
ntpd:
prctl(0x8, 0x1, 0xffffffffffffffa8, 0x1, 0) = -1 EINVAL (Invalid argument)
prctl(0x8, 0x1, 0, 0, 0) = -1 EINVAL (Invalid argument)
$ grep CONFIG_SECURITY .config
# CONFIG_SECURITY is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: prctl(0x8) -> EINVAL [Was: 2.6.25-rc3-mm1]
2008-03-05 10:51 ` prctl(0x8) -> EINVAL [Was: 2.6.25-rc3-mm1] Jiri Slaby
@ 2008-03-05 10:59 ` Jiri Slaby
2008-03-05 14:06 ` Serge E. Hallyn
1 sibling, 0 replies; 76+ messages in thread
From: Jiri Slaby @ 2008-03-05 10:59 UTC (permalink / raw)
To: Jiri Slaby
Cc: Andrew Morton, linux-kernel, Andrew G. Morgan, Serge Hallyn,
James Morris, Stephen Smalley, Paul Moore
On 03/05/2008 11:51 AM, Jiri Slaby wrote:
> On 03/04/2008 10:19 AM, Andrew Morton wrote:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
>>
>> +capabilities-implement-per-process-securebits.patch
>
> This probably causes userspace damage:
sorry, s/probably//
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: prctl(0x8) -> EINVAL [Was: 2.6.25-rc3-mm1]
2008-03-05 10:51 ` prctl(0x8) -> EINVAL [Was: 2.6.25-rc3-mm1] Jiri Slaby
2008-03-05 10:59 ` Jiri Slaby
@ 2008-03-05 14:06 ` Serge E. Hallyn
2008-03-05 15:18 ` Jiri Slaby
2008-03-09 16:28 ` Andrew Morgan
1 sibling, 2 replies; 76+ messages in thread
From: Serge E. Hallyn @ 2008-03-05 14:06 UTC (permalink / raw)
To: Jiri Slaby
Cc: Andrew Morton, linux-kernel, Andrew G. Morgan, Serge Hallyn,
James Morris, Stephen Smalley, Paul Moore
Quoting Jiri Slaby (jirislaby@gmail.com):
> On 03/04/2008 10:19 AM, Andrew Morton wrote:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
>> +capabilities-implement-per-process-securebits.patch
>
> This probably causes userspace damage:
>
> dbus:
> prctl(0x8, 0x1, 0, 0, 0) = -1 EINVAL (Invalid argument)
>
> named:
> named: -u with Linux threads not supported: requires kernel support for
> prctl(PR_SET_KEEPCAPS)
> prctl(0x8, 0x1, 0, 0, 0) = -1 EINVAL (Invalid argument)
>
> ntpd:
> prctl(0x8, 0x1, 0xffffffffffffffa8, 0x1, 0) = -1 EINVAL (Invalid argument)
> prctl(0x8, 0x1, 0, 0, 0) = -1 EINVAL (Invalid argument)
>
> $ grep CONFIG_SECURITY .config
> # CONFIG_SECURITY is not set
> # CONFIG_SECURITY_FILE_CAPABILITIES is not set
Thanks, Jiri. Does the following patch work for you?
This patch address the !CONFIG_SECURITY case, but not the case of
using the dummy LSM. The default these days is to have capabilities
compiled in no matter what, but it is still possible to have
CONFIG_SECURITY=y and CONFIG_SECURITY_CAPABILITIES=n, in which
case prctl(0x8) will return -EINVAL. Do we want dummy to call
cap_prctl() as well, or are we ok with userspace getting -EINVAL
given that there are in fact no capabilities at that point and
the userspace code is clearly expecting them?
thanks,
-serge
>From 4a66f19580489a3ac84f0a145e4585c09e65c88e Mon Sep 17 00:00:00 2001
From: Serge E. Hallyn <serue@us.ibm.com>
Date: Wed, 5 Mar 2008 06:02:32 -0800
Subject: [PATCH 1/1] capabilities: use cap_task_prctl when !CONFIG_SECURITY
capabilities-implement-per-process-securebits.patch introduced
cap_task_prctl() and moved the handling of capability-related
prctl into it. So when !CONFIG_SECURITY, the default
security_task_prctl() needs to call cap_task_prctl() the way
other default hooks call capability helpers when they exist.
This fixes a slew of userspace breakages when
CONFIG_SECURITY=n.
Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
---
include/linux/security.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/security.h b/include/linux/security.h
index 83763b0..861d6da 100644
--- a/include/linux/security.h
+++ b/include/linux/security.h
@@ -2228,7 +2228,7 @@ static inline int security_task_prctl (int option, unsigned long arg2,
unsigned long arg4,
unsigned long arg5, long *rc_p)
{
- return 0;
+ return cap_task_prctl(option, arg2, arg3, arg3, arg5, rc_p);
}
static inline void security_task_reparent_to_init (struct task_struct *p)
--
1.5.1
^ permalink raw reply related [flat|nested] 76+ messages in thread* Re: prctl(0x8) -> EINVAL [Was: 2.6.25-rc3-mm1]
2008-03-05 14:06 ` Serge E. Hallyn
@ 2008-03-05 15:18 ` Jiri Slaby
2008-03-09 16:28 ` Andrew Morgan
1 sibling, 0 replies; 76+ messages in thread
From: Jiri Slaby @ 2008-03-05 15:18 UTC (permalink / raw)
To: Serge E. Hallyn
Cc: Andrew Morton, linux-kernel, Andrew G. Morgan, James Morris,
Stephen Smalley, Paul Moore
On 03/05/2008 03:06 PM, Serge E. Hallyn wrote:
> From 4a66f19580489a3ac84f0a145e4585c09e65c88e Mon Sep 17 00:00:00 2001
> From: Serge E. Hallyn <serue@us.ibm.com>
> Date: Wed, 5 Mar 2008 06:02:32 -0800
> Subject: [PATCH 1/1] capabilities: use cap_task_prctl when !CONFIG_SECURITY
>
> capabilities-implement-per-process-securebits.patch introduced
> cap_task_prctl() and moved the handling of capability-related
> prctl into it. So when !CONFIG_SECURITY, the default
> security_task_prctl() needs to call cap_task_prctl() the way
> other default hooks call capability helpers when they exist.
>
> This fixes a slew of userspace breakages when
> CONFIG_SECURITY=n.
>
> Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
Tested-by: Jiri Slaby <jirislaby@gmail.com>
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: prctl(0x8) -> EINVAL [Was: 2.6.25-rc3-mm1]
2008-03-05 14:06 ` Serge E. Hallyn
2008-03-05 15:18 ` Jiri Slaby
@ 2008-03-09 16:28 ` Andrew Morgan
1 sibling, 0 replies; 76+ messages in thread
From: Andrew Morgan @ 2008-03-09 16:28 UTC (permalink / raw)
To: Serge E. Hallyn
Cc: Jiri Slaby, Andrew Morton, linux-kernel, James Morris,
Stephen Smalley, Paul Moore
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Acked-by: Andrew G. Morgan <morgan@kernel.org>
Cheers
Andrew
Serge E. Hallyn wrote:
|
| This patch address the !CONFIG_SECURITY case, but not the case of
| using the dummy LSM. The default these days is to have capabilities
| compiled in no matter what, but it is still possible to have
| CONFIG_SECURITY=y and CONFIG_SECURITY_CAPABILITIES=n, in which
| case prctl(0x8) will return -EINVAL. Do we want dummy to call
| cap_prctl() as well, or are we ok with userspace getting -EINVAL
| given that there are in fact no capabilities at that point and
| the userspace code is clearly expecting them?
|
| thanks,
| -serge
|
|>From 4a66f19580489a3ac84f0a145e4585c09e65c88e Mon Sep 17 00:00:00 2001
| From: Serge E. Hallyn <serue@us.ibm.com>
| Date: Wed, 5 Mar 2008 06:02:32 -0800
| Subject: [PATCH 1/1] capabilities: use cap_task_prctl when
!CONFIG_SECURITY
|
| capabilities-implement-per-process-securebits.patch introduced
| cap_task_prctl() and moved the handling of capability-related
| prctl into it. So when !CONFIG_SECURITY, the default
| security_task_prctl() needs to call cap_task_prctl() the way
| other default hooks call capability helpers when they exist.
|
| This fixes a slew of userspace breakages when
| CONFIG_SECURITY=n.
|
| Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
| ---
| include/linux/security.h | 2 +-
| 1 files changed, 1 insertions(+), 1 deletions(-)
|
| diff --git a/include/linux/security.h b/include/linux/security.h
| index 83763b0..861d6da 100644
| --- a/include/linux/security.h
| +++ b/include/linux/security.h
| @@ -2228,7 +2228,7 @@ static inline int security_task_prctl (int
option, unsigned long arg2,
| unsigned long arg4,
| unsigned long arg5, long *rc_p)
| {
| - return 0;
| + return cap_task_prctl(option, arg2, arg3, arg3, arg5, rc_p);
| }
|
| static inline void security_task_reparent_to_init (struct task_struct *p)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH1BA/mwytjiwfWMwRAkQ3AJ4h7rKORHnRvoQrPh/l1psZEwsRJACePk1T
AooB76FrfRd63O2kOpPvqNU=
=rxzU
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1
2008-03-04 9:19 2.6.25-rc3-mm1 Andrew Morton
` (9 preceding siblings ...)
2008-03-05 10:51 ` prctl(0x8) -> EINVAL [Was: 2.6.25-rc3-mm1] Jiri Slaby
@ 2008-03-05 13:04 ` Pavel Emelyanov
2008-03-05 13:12 ` 2.6.25-rc3-mm1 (SYSFS=n breaks module engine) Pavel Emelyanov
` (2 more replies)
2008-03-05 21:34 ` 2.6.25-rc3-mm1 ppc64 boot hang Badari Pulavarty
2008-03-07 3:58 ` 2.6.25-rc3-mm1 - BUG at system shutdown time Valdis.Kletnieks
12 siblings, 3 replies; 76+ messages in thread
From: Pavel Emelyanov @ 2008-03-05 13:04 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, Greg KH, Kay Sievers
With CONFIG_SYSFS not set got this on boot:
kobject: '<NULL>' (f88774c8): is not initialized, yet kobject_put() is
------------[ cut here ]------------
WARNING: at lib/kobject.c:652 kobject_put+0x29/0x3c()
Modules linked in: sky2 e1000
Pid: 1303, comm: modprobe Not tainted 2.6.25-rc3-mm1 #79
[<c041855b>] warn_on_slowpath+0x40/0x66
[<c041c687>] irq_exit+0x50/0x67
[<c040cc70>] smp_apic_timer_interrupt+0x6e/0x7a
[<c0403380>] apic_timer_interrupt+0x28/0x30
[<c0418e36>] vprintk+0x2b0/0x2df
[<c04118e8>] __update_rq_clock+0x1d/0x110
[<c0565e43>] schedule_timeout+0x13/0x86
[<c05656c2>] wait_for_common+0xd1/0x123
[<c0418e79>] printk+0x14/0x18
[<c04b34bf>] kobject_put+0x29/0x3c
[<c0431e39>] free_module+0x2f/0x72
[<c04328dd>] sys_init_module+0xa61/0x15d2
[<c04ba863>] pci_bus_read_config_byte+0x0/0x58
[<c0454f87>] vfs_read+0x6c/0x8b
[<c0455323>] sys_read+0x3c/0x63
[<c04028b2>] sysenter_past_esp+0x5f/0x85
=======================
---[ end trace d50646e8e8e48682 ]---
BUG: atomic counter underflow at:
Pid: 1303, comm: modprobe Tainted: G W 2.6.25-rc3-mm1 #79
[<c04b4042>] kref_put+0x3a/0x55
[<c0431e39>] free_module+0x2f/0x72
[<c04328dd>] sys_init_module+0xa61/0x15d2
[<c04ba863>] pci_bus_read_config_byte+0x0/0x58
[<c0454f87>] vfs_read+0x6c/0x8b
[<c0455323>] sys_read+0x3c/0x63
[<c04028b2>] sysenter_past_esp+0x5f/0x85
=======================
And same on any (int this case sky2) module unload (load is OK)
sky2 eth1: disabling interface
kobject: '<NULL>' (f886cb48): is not initialized, yet kobject_put() is being called.
------------[ cut here ]------------
WARNING: at lib/kobject.c:652 kobject_put+0x29/0x3c()
Modules linked in: e1000 [last unloaded: sky2]
Pid: 3216, comm: rmmod Tainted: G W 2.6.25-rc3-mm1 #80
[<c041855b>] warn_on_slowpath+0x40/0x66
[<c041c687>] irq_exit+0x50/0x67
[<c040cc70>] smp_apic_timer_interrupt+0x6e/0x7a
[<c0403380>] apic_timer_interrupt+0x28/0x30
[<c0418e36>] vprintk+0x2b0/0x2df
[<c04118e8>] __update_rq_clock+0x1d/0x110
[<c0565da3>] schedule_timeout+0x13/0x86
[<c0565622>] wait_for_common+0xd1/0x123
[<c0418e79>] printk+0x14/0x18
[<c04b343b>] kobject_put+0x29/0x3c
[<c0431e39>] free_module+0x2f/0x72
[<c0433a09>] sys_delete_module+0x19a/0x1b1
[<c040f866>] do_page_fault+0x1f6/0x4cc
[<c04028b2>] sysenter_past_esp+0x5f/0x85
=======================
---[ end trace 75a3ddf88545c3d4 ]---
BUG: atomic counter underflow at:
Pid: 3216, comm: rmmod Tainted: G W 2.6.25-rc3-mm1 #80
[<c04b3fbe>] kref_put+0x3a/0x55
[<c0431e39>] free_module+0x2f/0x72
[<c0433a09>] sys_delete_module+0x19a/0x1b1
[<c040f866>] do_page_fault+0x1f6/0x4cc
[<c04028b2>] sysenter_past_esp+0x5f/0x85
=======================
Config file:
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.25-rc3-mm1
# Wed Mar 5 15:55:32 2008
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
# CONFIG_GENERIC_LOCKBREAK is not set
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_FAST_CMPXCHG_LOCAL=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_QUICKLIST=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
# CONFIG_GENERIC_GPIO is not set
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
# CONFIG_GENERIC_TIME_VSYSCALL is not set
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
# CONFIG_HAVE_SETUP_PER_CPU_AREA is not set
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
# CONFIG_ZONE_DMA32 is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set
CONFIG_ARCH_SUPPORTS_AOUT=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_32_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_TASKSTATS=y
# CONFIG_TASK_DELAY_ACCT is not set
# CONFIG_TASK_XACCT is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=17
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_CGROUP_NS is not set
# CONFIG_CPUSETS is not set
# CONFIG_GROUP_SCHED is not set
# CONFIG_CGROUP_CPUACCT is not set
CONFIG_RESOURCE_COUNTERS=y
# CONFIG_CGROUP_MEM_RES_CTLR is not set
# CONFIG_RELAY is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_EMBEDDED=y
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
# CONFIG_SYSCTL_SYSCALL_CHECK is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_COMPAT_BRK=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
# CONFIG_EPOLL is not set
# CONFIG_SIGNALFD is not set
# CONFIG_TIMERFD is not set
# CONFIG_EVENTFD is not set
CONFIG_SHMEM=y
# CONFIG_VM_EVENT_COUNTERS is not set
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
# CONFIG_PROFILING is not set
# CONFIG_MARKERS is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
# CONFIG_PROC_PAGE_MONITOR is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_LBD=y
CONFIG_LSF=y
# CONFIG_BLK_DEV_BSG is not set
#
# IO Schedulers
#
# CONFIG_IOSCHED_CFQ is not set
CONFIG_IOSCHED_AS=y
# CONFIG_IOSCHED_DEADLINE is not set
CONFIG_IOSCHED_NOOP=y
# CONFIG_DEFAULT_CFQ is not set
CONFIG_DEFAULT_AS=y
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="anticipatory"
CONFIG_CLASSIC_RCU=y
# CONFIG_PREEMPT_RCU is not set
#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
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_X86_RDC321X is not set
# CONFIG_X86_VSMP is not set
# CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER is not set
# CONFIG_PARAVIRT_GUEST 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_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_XADD=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_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=4
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
# CONFIG_IOMMU_HELPER is not set
CONFIG_NR_CPUS=255
# CONFIG_SCHED_SMT is not set
# CONFIG_SCHED_MC is not set
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
# CONFIG_RCU_TRACE is not set
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=y
CONFIG_VM86=y
# 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
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_3G_OPT is not set
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_2G_OPT is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
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_SPARSEMEM_VMEMMAP_ENABLE is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_NR_QUICK=1
CONFIG_VIRT_TO_BUS=y
CONFIG_HIGHPTE=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_IRQBALANCE is not set
# CONFIG_SECCOMP is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_SCHED_HRTICK=y
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x400000
# CONFIG_HOTPLUG_CPU is not set
# CONFIG_COMPAT_VDSO is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
#
# Power management options
#
# CONFIG_PM is not set
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
# CONFIG_CPU_IDLE is not set
#
# Bus options (PCI etc.)
#
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_PCI_DOMAINS=y
# CONFIG_PCIEPORTBUS is not set
CONFIG_ARCH_SUPPORTS_MSI=y
# CONFIG_PCI_MSI is not set
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_HT_IRQ is not set
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=y
#
# Networking
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_NET_NS=y
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
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 is not set
# CONFIG_IP_ROUTE_MULTIPATH is not set
# CONFIG_IP_ROUTE_VERBOSE is not set
CONFIG_IP_PNP=y
# CONFIG_IP_PNP_DHCP is not set
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
CONFIG_NET_IPIP=y
CONFIG_NET_IPGRE=y
# CONFIG_NET_IPGRE_BROADCAST 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=y
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
# CONFIG_INET_LRO is not set
# CONFIG_INET_DIAG is not set
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
# CONFIG_IPV6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# 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_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
#
# Wireless
#
# CONFIG_CFG80211 is not set
# CONFIG_WIRELESS_EXT is not set
# CONFIG_MAC80211 is not set
# CONFIG_IEEE80211 is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD 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=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_MISC_DEVICES is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
CONFIG_SCSI_ISCSI_ATTRS=m
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
# CONFIG_SATA_AHCI is not set
# CONFIG_SATA_SVW is not set
CONFIG_ATA_PIIX=y
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SX4 is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIL24 is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5535 is not set
# CONFIG_PATA_CS5536 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
# CONFIG_PATA_PLATFORM is not set
# CONFIG_MD is not set
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_NETDEVICES_MULTIQUEUE is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_ARCNET is not set
# CONFIG_NET_ETHERNET is not set
CONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=m
CONFIG_E1000_NAPI=y
# CONFIG_E1000_DISABLE_PACKET_SPLIT is not set
# CONFIG_E1000E is not set
# CONFIG_E1000E_ENABLED is not set
# CONFIG_IP1000 is not set
# CONFIG_IGB 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=m
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2 is not set
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set
#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# 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_NET_FC is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set
#
# Userland interfaces
#
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV 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_KEYBOARD_STOWAWAY is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET 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=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_DEVKMEM=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
CONFIG_SYNCLINK=m
CONFIG_SYNCLINKMP=m
CONFIG_SYNCLINK_GT=m
CONFIG_N_HDLC=m
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
# CONFIG_STALDRV is not set
# CONFIG_NOZOMI is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
CONFIG_HW_RANDOM_GEODE=m
CONFIG_HW_RANDOM_VIA=m
CONFIG_NVRAM=y
CONFIG_RTC=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
CONFIG_SONYPI=m
# CONFIG_MWAVE is not set
CONFIG_PC8736x_GPIO=m
CONFIG_NSC_GPIO=m
CONFIG_CS5535_GPIO=m
CONFIG_RAW_DRIVER=y
CONFIG_MAX_RAW_DEVS=8192
CONFIG_HANGCHECK_TIMER=m
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
# CONFIG_I2C is not set
# CONFIG_SPI is not set
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
# CONFIG_HWMON is not set
# CONFIG_THERMAL is not set
# CONFIG_WATCHDOG is not set
#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not set
#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_DAB is not set
#
# Graphics support
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
# CONFIG_VIDEO_SELECT is not set
CONFIG_DUMMY_CONSOLE=y
#
# Sound
#
# CONFIG_SOUND is not set
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set
# CONFIG_HIDRAW is not set
#
# USB Input Devices
#
CONFIG_USB_HID=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set
#
# Miscellaneous USB options
#
# CONFIG_USB_DEVICEFS is not set
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_EHCI_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
# CONFIG_USB_UHCI_HCD is not set
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#
#
# may also be needed; see USB_STORAGE Help for more information
#
# CONFIG_USB_STORAGE is not set
# CONFIG_USB_LIBUSUAL is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_MON is not set
#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_GOTEMP is not set
# CONFIG_USB_GADGET is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
# CONFIG_EDAC is not set
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
# CONFIG_UIO is not set
#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
# CONFIG_DMIID is not set
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT2_FS_XIP=y
CONFIG_FS_XIP=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
CONFIG_FS_MBCACHE=y
# CONFIG_REISER4_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_DNOTIFY is not set
# CONFIG_INOTIFY is not set
# CONFIG_QUOTA is not set
# 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_PROC_SYSCTL=y
# CONFIG_SYSFS is not set
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
#
# Layered filesystems
#
# CONFIG_UNION_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_MINIX_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_NETWORK_FILESYSTEMS is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=m
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
# 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=m
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
CONFIG_NLS_CODEPAGE_866=m
# 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=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
# 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=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_PAGE_OWNER is not set
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
# CONFIG_DETECT_SOFTLOCKUP is not set
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_WRITECOUNT is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_PROFILE_LIKELY is not set
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_DEBUG_SYNCHRO_TEST is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_SAMPLES is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_X86_PTDUMP is not set
# CONFIG_DEBUG_RODATA is not set
# CONFIG_DEBUG_NX_TEST is not set
# CONFIG_4KSTACKS is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
# CONFIG_CPA_DEBUG is not set
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=y
# CONFIG_CRYPTO_SEQIV is not set
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
# 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_GF128MUL is not set
# CONFIG_CRYPTO_ECB is not set
CONFIG_CRYPTO_CBC=y
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_XTS is not set
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_586 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 is not set
# 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_SEED is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_586 is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_TEST is not set
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_LZO is not set
# CONFIG_CRYPTO_HW is not set
CONFIG_HAVE_KVM=y
# CONFIG_VIRTUALIZATION is not set
#
# Library routines
#
CONFIG_BITREVERSE=y
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: 2.6.25-rc3-mm1 (SYSFS=n breaks module engine)
2008-03-05 13:04 ` 2.6.25-rc3-mm1 Pavel Emelyanov
@ 2008-03-05 13:12 ` Pavel Emelyanov
2008-03-05 13:31 ` 2.6.25-rc3-mm1 Kay Sievers
2008-03-05 16:40 ` 2.6.25-rc3-mm1 Greg KH
2 siblings, 0 replies; 76+ messages in thread
From: Pavel Emelyanov @ 2008-03-05 13:12 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, Greg KH, Kay Sievers
Sorry, I forgot to change the subject in the previous letter.
Better late than never.
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1
2008-03-05 13:04 ` 2.6.25-rc3-mm1 Pavel Emelyanov
2008-03-05 13:12 ` 2.6.25-rc3-mm1 (SYSFS=n breaks module engine) Pavel Emelyanov
@ 2008-03-05 13:31 ` Kay Sievers
2008-03-05 13:38 ` 2.6.25-rc3-mm1 Pavel Emelyanov
2008-03-05 16:40 ` 2.6.25-rc3-mm1 Greg KH
2 siblings, 1 reply; 76+ messages in thread
From: Kay Sievers @ 2008-03-05 13:31 UTC (permalink / raw)
To: Pavel Emelyanov; +Cc: Andrew Morton, linux-kernel, Greg KH
On Wed, 2008-03-05 at 16:04 +0300, Pavel Emelyanov wrote:
> With CONFIG_SYSFS not set got this on boot:
>
> kobject: '<NULL>' (f88774c8): is not initialized, yet kobject_put() is
> ------------[ cut here ]------------
> WARNING: at lib/kobject.c:652 kobject_put+0x29/0x3c()
> Modules linked in: sky2 e1000
> Pid: 1303, comm: modprobe Not tainted 2.6.25-rc3-mm1 #79
> [<c041855b>] warn_on_slowpath+0x40/0x66
> [<c041c687>] irq_exit+0x50/0x67
> [<c040cc70>] smp_apic_timer_interrupt+0x6e/0x7a
> [<c0403380>] apic_timer_interrupt+0x28/0x30
> [<c0418e36>] vprintk+0x2b0/0x2df
> [<c04118e8>] __update_rq_clock+0x1d/0x110
> [<c0565e43>] schedule_timeout+0x13/0x86
>
> [<c05656c2>] wait_for_common+0xd1/0x123
> [<c0418e79>] printk+0x14/0x18
> [<c04b34bf>] kobject_put+0x29/0x3c
> [<c0431e39>] free_module+0x2f/0x72
> [<c04328dd>] sys_init_module+0xa61/0x15d2
>
> [<c04ba863>] pci_bus_read_config_byte+0x0/0x58
> [<c0454f87>] vfs_read+0x6c/0x8b
> [<c0455323>] sys_read+0x3c/0x63
> [<c04028b2>] sysenter_past_esp+0x5f/0x85
>
> =======================
> ---[ end trace d50646e8e8e48682 ]---
Does this fix it?:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=120fc3d77acfd91f3521737a440d42839c475982
Thanks,
Kay
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1
2008-03-05 13:31 ` 2.6.25-rc3-mm1 Kay Sievers
@ 2008-03-05 13:38 ` Pavel Emelyanov
2008-03-05 13:54 ` 2.6.25-rc3-mm1 Kay Sievers
0 siblings, 1 reply; 76+ messages in thread
From: Pavel Emelyanov @ 2008-03-05 13:38 UTC (permalink / raw)
To: Kay Sievers; +Cc: Andrew Morton, linux-kernel, Greg KH
Kay Sievers wrote:
> On Wed, 2008-03-05 at 16:04 +0300, Pavel Emelyanov wrote:
>> With CONFIG_SYSFS not set got this on boot:
>>
>> kobject: '<NULL>' (f88774c8): is not initialized, yet kobject_put() is
>> ------------[ cut here ]------------
>> WARNING: at lib/kobject.c:652 kobject_put+0x29/0x3c()
>> Modules linked in: sky2 e1000
>> Pid: 1303, comm: modprobe Not tainted 2.6.25-rc3-mm1 #79
>> [<c041855b>] warn_on_slowpath+0x40/0x66
>> [<c041c687>] irq_exit+0x50/0x67
>> [<c040cc70>] smp_apic_timer_interrupt+0x6e/0x7a
>> [<c0403380>] apic_timer_interrupt+0x28/0x30
>> [<c0418e36>] vprintk+0x2b0/0x2df
>> [<c04118e8>] __update_rq_clock+0x1d/0x110
>> [<c0565e43>] schedule_timeout+0x13/0x86
>>
>> [<c05656c2>] wait_for_common+0xd1/0x123
>> [<c0418e79>] printk+0x14/0x18
>> [<c04b34bf>] kobject_put+0x29/0x3c
>> [<c0431e39>] free_module+0x2f/0x72
>> [<c04328dd>] sys_init_module+0xa61/0x15d2
>>
>> [<c04ba863>] pci_bus_read_config_byte+0x0/0x58
>> [<c0454f87>] vfs_read+0x6c/0x8b
>> [<c0455323>] sys_read+0x3c/0x63
>> [<c04028b2>] sysenter_past_esp+0x5f/0x85
>>
>> =======================
>> ---[ end trace d50646e8e8e48682 ]---
>
> Does this fix it?:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=120fc3d77acfd91f3521737a440d42839c475982
This is already in 2.6.25-rc3-mm1, so the answer is "no it does not" :)
> Thanks,
> Kay
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1
2008-03-05 13:38 ` 2.6.25-rc3-mm1 Pavel Emelyanov
@ 2008-03-05 13:54 ` Kay Sievers
2008-03-05 14:28 ` 2.6.25-rc3-mm1 Pavel Emelyanov
0 siblings, 1 reply; 76+ messages in thread
From: Kay Sievers @ 2008-03-05 13:54 UTC (permalink / raw)
To: Pavel Emelyanov; +Cc: Andrew Morton, linux-kernel, Greg KH
On Wed, 2008-03-05 at 16:38 +0300, Pavel Emelyanov wrote:
> Kay Sievers wrote:
> > On Wed, 2008-03-05 at 16:04 +0300, Pavel Emelyanov wrote:
> >> With CONFIG_SYSFS not set got this on boot:
> >>
> >> kobject: '<NULL>' (f88774c8): is not initialized, yet kobject_put() is
> >> ------------[ cut here ]------------
> >> WARNING: at lib/kobject.c:652 kobject_put+0x29/0x3c()
> >> Modules linked in: sky2 e1000
> >> Pid: 1303, comm: modprobe Not tainted 2.6.25-rc3-mm1 #79
> >> [<c041855b>] warn_on_slowpath+0x40/0x66
> >> [<c041c687>] irq_exit+0x50/0x67
> >> [<c040cc70>] smp_apic_timer_interrupt+0x6e/0x7a
> >> [<c0403380>] apic_timer_interrupt+0x28/0x30
> >> [<c0418e36>] vprintk+0x2b0/0x2df
> >> [<c04118e8>] __update_rq_clock+0x1d/0x110
> >> [<c0565e43>] schedule_timeout+0x13/0x86
> >>
> >> [<c05656c2>] wait_for_common+0xd1/0x123
> >> [<c0418e79>] printk+0x14/0x18
> >> [<c04b34bf>] kobject_put+0x29/0x3c
> >> [<c0431e39>] free_module+0x2f/0x72
> >> [<c04328dd>] sys_init_module+0xa61/0x15d2
> >>
> >> [<c04ba863>] pci_bus_read_config_byte+0x0/0x58
> >> [<c0454f87>] vfs_read+0x6c/0x8b
> >> [<c0455323>] sys_read+0x3c/0x63
> >> [<c04028b2>] sysenter_past_esp+0x5f/0x85
> >>
> >> =======================
> >> ---[ end trace d50646e8e8e48682 ]---
> >
> > Does this fix it?:
> >
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=120fc3d77acfd91f3521737a440d42839c475982
>
> This is already in 2.6.25-rc3-mm1, so the answer is "no it does not" :)
Ok. Care to enable CONFIG_DEBUG_KOBJECT, and post the part of the log
that happens right before the WARN()? We might get a hint where to look
for the stuff that goes wrong.
Thanks,
Kay
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1
2008-03-05 13:54 ` 2.6.25-rc3-mm1 Kay Sievers
@ 2008-03-05 14:28 ` Pavel Emelyanov
0 siblings, 0 replies; 76+ messages in thread
From: Pavel Emelyanov @ 2008-03-05 14:28 UTC (permalink / raw)
To: Kay Sievers; +Cc: Andrew Morton, linux-kernel, Greg KH
Kay Sievers wrote:
> On Wed, 2008-03-05 at 16:38 +0300, Pavel Emelyanov wrote:
>> Kay Sievers wrote:
>>> On Wed, 2008-03-05 at 16:04 +0300, Pavel Emelyanov wrote:
>>>> With CONFIG_SYSFS not set got this on boot:
>>>>
>>>> kobject: '<NULL>' (f88774c8): is not initialized, yet kobject_put() is
>>>> ------------[ cut here ]------------
>>>> WARNING: at lib/kobject.c:652 kobject_put+0x29/0x3c()
>>>> Modules linked in: sky2 e1000
>>>> Pid: 1303, comm: modprobe Not tainted 2.6.25-rc3-mm1 #79
>>>> [<c041855b>] warn_on_slowpath+0x40/0x66
>>>> [<c041c687>] irq_exit+0x50/0x67
>>>> [<c040cc70>] smp_apic_timer_interrupt+0x6e/0x7a
>>>> [<c0403380>] apic_timer_interrupt+0x28/0x30
>>>> [<c0418e36>] vprintk+0x2b0/0x2df
>>>> [<c04118e8>] __update_rq_clock+0x1d/0x110
>>>> [<c0565e43>] schedule_timeout+0x13/0x86
>>>>
>>>> [<c05656c2>] wait_for_common+0xd1/0x123
>>>> [<c0418e79>] printk+0x14/0x18
>>>> [<c04b34bf>] kobject_put+0x29/0x3c
>>>> [<c0431e39>] free_module+0x2f/0x72
>>>> [<c04328dd>] sys_init_module+0xa61/0x15d2
>>>>
>>>> [<c04ba863>] pci_bus_read_config_byte+0x0/0x58
>>>> [<c0454f87>] vfs_read+0x6c/0x8b
>>>> [<c0455323>] sys_read+0x3c/0x63
>>>> [<c04028b2>] sysenter_past_esp+0x5f/0x85
>>>>
>>>> =======================
>>>> ---[ end trace d50646e8e8e48682 ]---
>>> Does this fix it?:
>>>
>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=120fc3d77acfd91f3521737a440d42839c475982
>> This is already in 2.6.25-rc3-mm1, so the answer is "no it does not" :)
>
> Ok. Care to enable CONFIG_DEBUG_KOBJECT, and post the part of the log
> that happens right before the WARN()? We might get a hint where to look
> for the stuff that goes wrong.
Hm... Not sure how may lines are required, but here'are the ones
that are related to sky2 module, which is loaded and then removed:
kobject: 'sky2' (f74de280): kobject_add_internal: parent: 'drivers', set: 'drivers'
PCI: Setting latency timer of device 0000:02:00.0 to 64
sky2 0000:02:00.0: v1.21 addr 0xdeefc000 irq 16 Yukon-EC (0xb6) rev 2
kobject: 'net' (f7512200): kobject_add_internal: parent: '0000:02:00.0', set: '<NULL>'
kobject: 'eth1' (f74ccb64): kobject_add_internal: parent: 'net', set: 'devices'
kobject: 'eth1' (f74ccb64): kobject_uevent_env
kobject: 'eth1' (f74ccb64): fill_kobj_path: path = '/devices/pci0000:00/0000:00:03.0/0000:02:00.0/net/eth1'
sky2 eth1: addr 00:0e:0c:3b:d8:8a
kobject: 'sky2' (f74de280): kobject_uevent_env
kobject: 'sky2' (f74de280): fill_kobj_path: path = '/bus/pci/drivers/sky2'
sky2 eth1: enabling interface
sky2 eth1: disabling interface
kobject: 'eth1' (f74ccb64): kobject_uevent_env
kobject: 'eth1' (f74ccb64): fill_kobj_path: path = '/devices/pci0000:00/0000:00:03.0/0000:02:00.0/net/eth1'
kobject: 'net' (f7512200): kobject_cleanup
kobject: 'net' (f7512200): auto cleanup kobject_del
kobject: 'net' (f7512200): calling ktype release
kobject: (f7512200): dynamic_kobj_release
kobject: 'net': free name
kobject: 'eth1' (f74ccb64): kobject_cleanup
kobject: 'eth1' (f74ccb64): calling ktype release
kobject: 'eth1': free name
kobject: 'sky2' (f74de280): kobject_cleanup
kobject: 'sky2' (f74de280): auto cleanup 'remove' event
kobject: 'sky2' (f74de280): kobject_uevent_env
kobject: 'sky2' (f74de280): fill_kobj_path: path = '/bus/pci/drivers/sky2'
kobject: 'sky2' (f74de280): auto cleanup kobject_del
kobject: 'sky2' (f74de280): calling ktype release
kobject: 'sky2': free name
kobject: '<NULL>' (f886cb48): is not initialized, yet kobject_put() is being called.
------------[ cut here ]------------
WARNING: at lib/kobject.c:652 kobject_put+0x29/0x3c()
Modules linked in: e1000 [last unloaded: sky2]
Pid: 3188, comm: rmmod Tainted: G W 2.6.25-rc3-mm1 #88
[<c041855b>] warn_on_slowpath+0x40/0x66
[<c041c687>] irq_exit+0x50/0x67
[<c040cc70>] smp_apic_timer_interrupt+0x6e/0x7a
[<c0403380>] apic_timer_interrupt+0x28/0x30
[<c0418e36>] vprintk+0x2b0/0x2df
[<c04118e8>] __update_rq_clock+0x1d/0x110
[<c0565f43>] schedule_timeout+0x13/0x86
[<c05657c2>] wait_for_common+0xd1/0x123
[<c0418e79>] printk+0x14/0x18
[<c04b3474>] kobject_put+0x29/0x3c
[<c0431e39>] free_module+0x2f/0x72
[<c0433a09>] sys_delete_module+0x19a/0x1b1
[<c040f866>] do_page_fault+0x1f6/0x4cc
[<c04028b2>] sysenter_past_esp+0x5f/0x85
=======================
But this happens _after_ the very first warning and I can't figure
out which modules causes one :( Do you need a full dmesg for that?
> Thanks,
> Kay
>
>
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1
2008-03-05 13:04 ` 2.6.25-rc3-mm1 Pavel Emelyanov
2008-03-05 13:12 ` 2.6.25-rc3-mm1 (SYSFS=n breaks module engine) Pavel Emelyanov
2008-03-05 13:31 ` 2.6.25-rc3-mm1 Kay Sievers
@ 2008-03-05 16:40 ` Greg KH
2008-03-05 16:59 ` 2.6.25-rc3-mm1 Pavel Emelyanov
2 siblings, 1 reply; 76+ messages in thread
From: Greg KH @ 2008-03-05 16:40 UTC (permalink / raw)
To: Pavel Emelyanov; +Cc: Andrew Morton, linux-kernel, Kay Sievers
On Wed, Mar 05, 2008 at 04:04:43PM +0300, Pavel Emelyanov wrote:
> With CONFIG_SYSFS not set got this on boot:
>
> kobject: '<NULL>' (f88774c8): is not initialized, yet kobject_put() is
> ------------[ cut here ]------------
> WARNING: at lib/kobject.c:652 kobject_put+0x29/0x3c()
> Modules linked in: sky2 e1000
> Pid: 1303, comm: modprobe Not tainted 2.6.25-rc3-mm1 #79
> [<c041855b>] warn_on_slowpath+0x40/0x66
> [<c041c687>] irq_exit+0x50/0x67
> [<c040cc70>] smp_apic_timer_interrupt+0x6e/0x7a
> [<c0403380>] apic_timer_interrupt+0x28/0x30
> [<c0418e36>] vprintk+0x2b0/0x2df
> [<c04118e8>] __update_rq_clock+0x1d/0x110
> [<c0565e43>] schedule_timeout+0x13/0x86
>
> [<c05656c2>] wait_for_common+0xd1/0x123
> [<c0418e79>] printk+0x14/0x18
> [<c04b34bf>] kobject_put+0x29/0x3c
> [<c0431e39>] free_module+0x2f/0x72
> [<c04328dd>] sys_init_module+0xa61/0x15d2
>
> [<c04ba863>] pci_bus_read_config_byte+0x0/0x58
> [<c0454f87>] vfs_read+0x6c/0x8b
> [<c0455323>] sys_read+0x3c/0x63
> [<c04028b2>] sysenter_past_esp+0x5f/0x85
Hm, but with CONFIG_SYSFS set this does not show up?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1
2008-03-05 16:40 ` 2.6.25-rc3-mm1 Greg KH
@ 2008-03-05 16:59 ` Pavel Emelyanov
2008-03-05 17:07 ` 2.6.25-rc3-mm1 Greg KH
0 siblings, 1 reply; 76+ messages in thread
From: Pavel Emelyanov @ 2008-03-05 16:59 UTC (permalink / raw)
To: Greg KH; +Cc: Andrew Morton, linux-kernel, Kay Sievers
Greg KH wrote:
> On Wed, Mar 05, 2008 at 04:04:43PM +0300, Pavel Emelyanov wrote:
>> With CONFIG_SYSFS not set got this on boot:
>>
>> kobject: '<NULL>' (f88774c8): is not initialized, yet kobject_put() is
>> ------------[ cut here ]------------
>> WARNING: at lib/kobject.c:652 kobject_put+0x29/0x3c()
>> Modules linked in: sky2 e1000
>> Pid: 1303, comm: modprobe Not tainted 2.6.25-rc3-mm1 #79
>> [<c041855b>] warn_on_slowpath+0x40/0x66
>> [<c041c687>] irq_exit+0x50/0x67
>> [<c040cc70>] smp_apic_timer_interrupt+0x6e/0x7a
>> [<c0403380>] apic_timer_interrupt+0x28/0x30
>> [<c0418e36>] vprintk+0x2b0/0x2df
>> [<c04118e8>] __update_rq_clock+0x1d/0x110
>> [<c0565e43>] schedule_timeout+0x13/0x86
>>
>> [<c05656c2>] wait_for_common+0xd1/0x123
>> [<c0418e79>] printk+0x14/0x18
>> [<c04b34bf>] kobject_put+0x29/0x3c
>> [<c0431e39>] free_module+0x2f/0x72
>> [<c04328dd>] sys_init_module+0xa61/0x15d2
>>
>> [<c04ba863>] pci_bus_read_config_byte+0x0/0x58
>> [<c0454f87>] vfs_read+0x6c/0x8b
>> [<c0455323>] sys_read+0x3c/0x63
>> [<c04028b2>] sysenter_past_esp+0x5f/0x85
>
> Hm, but with CONFIG_SYSFS set this does not show up?
Yes, with CONFIG_SYSFS set everything is OK.
> thanks,
>
> greg k-h
>
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1
2008-03-05 16:59 ` 2.6.25-rc3-mm1 Pavel Emelyanov
@ 2008-03-05 17:07 ` Greg KH
0 siblings, 0 replies; 76+ messages in thread
From: Greg KH @ 2008-03-05 17:07 UTC (permalink / raw)
To: Pavel Emelyanov; +Cc: Andrew Morton, linux-kernel, Kay Sievers
On Wed, Mar 05, 2008 at 07:59:32PM +0300, Pavel Emelyanov wrote:
> Greg KH wrote:
> > On Wed, Mar 05, 2008 at 04:04:43PM +0300, Pavel Emelyanov wrote:
> >> With CONFIG_SYSFS not set got this on boot:
> >>
> >> kobject: '<NULL>' (f88774c8): is not initialized, yet kobject_put() is
> >> ------------[ cut here ]------------
> >> WARNING: at lib/kobject.c:652 kobject_put+0x29/0x3c()
> >> Modules linked in: sky2 e1000
> >> Pid: 1303, comm: modprobe Not tainted 2.6.25-rc3-mm1 #79
> >> [<c041855b>] warn_on_slowpath+0x40/0x66
> >> [<c041c687>] irq_exit+0x50/0x67
> >> [<c040cc70>] smp_apic_timer_interrupt+0x6e/0x7a
> >> [<c0403380>] apic_timer_interrupt+0x28/0x30
> >> [<c0418e36>] vprintk+0x2b0/0x2df
> >> [<c04118e8>] __update_rq_clock+0x1d/0x110
> >> [<c0565e43>] schedule_timeout+0x13/0x86
> >>
> >> [<c05656c2>] wait_for_common+0xd1/0x123
> >> [<c0418e79>] printk+0x14/0x18
> >> [<c04b34bf>] kobject_put+0x29/0x3c
> >> [<c0431e39>] free_module+0x2f/0x72
> >> [<c04328dd>] sys_init_module+0xa61/0x15d2
> >>
> >> [<c04ba863>] pci_bus_read_config_byte+0x0/0x58
> >> [<c0454f87>] vfs_read+0x6c/0x8b
> >> [<c0455323>] sys_read+0x3c/0x63
> >> [<c04028b2>] sysenter_past_esp+0x5f/0x85
> >
> > Hm, but with CONFIG_SYSFS set this does not show up?
>
> Yes, with CONFIG_SYSFS set everything is OK.
Thanks. Odds are we have some sysfs issue in the module core, that code
really needs to be refactored, I'll go work on it to see if we can try
to isolate all of that code into one file, which should help find these
kinds of things easier.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 76+ messages in thread
* 2.6.25-rc3-mm1 ppc64 boot hang
2008-03-04 9:19 2.6.25-rc3-mm1 Andrew Morton
` (10 preceding siblings ...)
2008-03-05 13:04 ` 2.6.25-rc3-mm1 Pavel Emelyanov
@ 2008-03-05 21:34 ` Badari Pulavarty
2008-03-05 21:54 ` Andrew Morton
2008-03-07 3:58 ` 2.6.25-rc3-mm1 - BUG at system shutdown time Valdis.Kletnieks
12 siblings, 1 reply; 76+ messages in thread
From: Badari Pulavarty @ 2008-03-05 21:34 UTC (permalink / raw)
To: Andrew Morton; +Cc: lkml, linuxppc-dev
On Tue, 2008-03-04 at 01:19 -0800, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
>
Hi Andrew,
Not able to boot 2.6.25-rc3-mm1 my ppc64 box.
2.6.25-rc2-mm1 and 2.6.25-rc3 boots fine.
I applied slab.c fix also.
Any other known issues ? My config file attached.
Here are the messages on the console.
Thanks,
Badari
Linux/PowerPC load: root=/dev/sda3 selinux=0 elevator=cfq numa=debug
kernelcore=1024M
Finalizing device tree... using OF tree (promptr=00c39a50)
OF stdout device is: /vdevice/vty@30000000
Hypertas detected, assuming LPAR !
command line: root=/dev/sda3 selinux=0 elevator=cfq numa=debug
kernelcore=1024M
memory layout at init:
alloc_bottom : 00000000023d0000
alloc_top : 0000000008000000
alloc_top_hi : 0000000072000000
rmo_top : 0000000008000000
ram_top : 0000000072000000
Looking for displays
instantiating rtas at 0x00000000077ca000 ... done
0000000000000000 : boot cpu 0000000000000000
0000000000000002 : starting cpu hw idx 0000000000000002... done
copying OF device tree ...
Building dt strings...
Building dt structure...
Device tree strings 0x00000000023d1000 -> 0x00000000023d21cf
Device tree struct 0x00000000023d3000 -> 0x00000000023e0000
Calling quiesce ...
returning from prom_init
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.25-rc3-mm1
# Wed Mar 5 10:34:39 2008
#
CONFIG_PPC64=y
#
# Processor support
#
# CONFIG_POWER4_ONLY is not set
CONFIG_POWER3=y
CONFIG_POWER4=y
# CONFIG_TUNE_CELL is not set
CONFIG_PPC_FPU=y
# CONFIG_ALTIVEC is not set
CONFIG_PPC_STD_MMU=y
CONFIG_PPC_MM_SLICES=y
CONFIG_VIRT_CPU_ACCOUNTING=y
CONFIG_SMP=y
CONFIG_NR_CPUS=32
CONFIG_64BIT=y
CONFIG_WORD_SIZE=64
CONFIG_PPC_MERGE=y
CONFIG_MMU=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_IRQ_PER_CPU=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_ILOG2_U32=y
CONFIG_ARCH_HAS_ILOG2_U64=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_ARCH_NO_VIRT_TO_BUS=y
CONFIG_PPC=y
CONFIG_EARLY_PRINTK=y
CONFIG_COMPAT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_PPC_OF=y
CONFIG_OF=y
CONFIG_PPC_UDBG_16550=y
CONFIG_GENERIC_TBSYNC=y
CONFIG_AUDIT_ARCH=y
CONFIG_GENERIC_BUG=y
# CONFIG_DEFAULT_UIMAGE is not set
CONFIG_HIBERNATE_64=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
# CONFIG_PPC_DCR_NATIVE is not set
# CONFIG_PPC_DCR_MMIO is not set
# CONFIG_PPC_OF_PLATFORM_PCI is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=15
CONFIG_CGROUPS=y
CONFIG_CGROUP_DEBUG=y
CONFIG_CGROUP_NS=y
# CONFIG_CPUSETS is not set
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_RT_GROUP_SCHED=y
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
CONFIG_CGROUP_CPUACCT=y
CONFIG_RESOURCE_COUNTERS=y
CONFIG_CGROUP_MEM_RES_CTLR=y
CONFIG_SYSFS_DEPRECATED=y
CONFIG_RELAY=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
CONFIG_PID_NS=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_SYSCTL_SYSCALL=y
CONFIG_SYSCTL_SYSCALL_CHECK=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_COMPAT_BRK=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_PROFILING=y
CONFIG_MARKERS=y
CONFIG_OPROFILE=y
CONFIG_HAVE_OPROFILE=y
CONFIG_KPROBES=y
CONFIG_KRETPROBES=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_KMOD is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_BLK_DEV_IO_TRACE=y
# CONFIG_BLK_DEV_BSG is not set
CONFIG_BLOCK_COMPAT=y
#
# IO Schedulers
#
CONFIG_IOSCHED_CFQ=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_NOOP=y
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_CLASSIC_RCU=y
# CONFIG_PREEMPT_RCU is not set
#
# Platform support
#
CONFIG_PPC_MULTIPLATFORM=y
# CONFIG_PPC_82xx is not set
# CONFIG_PPC_83xx is not set
# CONFIG_PPC_86xx is not set
CONFIG_PPC_PSERIES=y
# CONFIG_PPC_SPLPAR is not set
CONFIG_EEH=y
CONFIG_SCANLOG=y
# CONFIG_LPARCFG is not set
# CONFIG_PPC_ISERIES is not set
# CONFIG_PPC_MPC512x is not set
# CONFIG_PPC_MPC5121 is not set
CONFIG_PPC_PMAC=y
CONFIG_PPC_PMAC64=y
# CONFIG_PPC_MAPLE is not set
# CONFIG_PPC_PASEMI is not set
# CONFIG_PPC_CELLEB is not set
# CONFIG_PPC_PS3 is not set
# CONFIG_PPC_CELL is not set
# CONFIG_PPC_CELL_NATIVE is not set
# CONFIG_PPC_IBM_CELL_BLADE is not set
# CONFIG_PQ2ADS is not set
CONFIG_PPC_NATIVE=y
# CONFIG_UDBG_RTAS_CONSOLE is not set
CONFIG_XICS=y
# CONFIG_IPIC is not set
CONFIG_MPIC=y
# CONFIG_MPIC_WEIRD is not set
CONFIG_PPC_I8259=y
CONFIG_U3_DART=y
CONFIG_PPC_RTAS=y
CONFIG_RTAS_ERROR_LOGGING=y
CONFIG_RTAS_PROC=y
# CONFIG_RTAS_FLASH is not set
# CONFIG_MMIO_NVRAM is not set
CONFIG_MPIC_U3_HT_IRQS=y
CONFIG_IBMVIO=y
# CONFIG_IBMEBUS is not set
# CONFIG_PPC_MPC106 is not set
CONFIG_PPC_970_NAP=y
# CONFIG_PPC_INDIRECT_IO is not set
# CONFIG_GENERIC_IOMAP is not set
# CONFIG_CPU_FREQ is not set
# CONFIG_FSL_ULI1575 is not set
#
# Kernel options
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
# CONFIG_SCHED_HRTICK is not set
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_RCU_TRACE=y
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
CONFIG_FORCE_MAX_ZONEORDER=13
CONFIG_HUGETLB_PAGE_SIZE_VARIABLE=y
# CONFIG_IOMMU_VMERGE is not set
CONFIG_IOMMU_HELPER=y
CONFIG_HOTPLUG_CPU=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_ARCH_HAS_WALK_MEMORY=y
CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_IRQ_ALL_CPUS=y
CONFIG_NUMA=y
CONFIG_NODES_SHIFT=4
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
# CONFIG_DISCONTIGMEM_MANUAL is not set
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_NEED_MULTIPLE_NODES=y
CONFIG_HAVE_MEMORY_PRESENT=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_VMEMMAP=y
CONFIG_MEMORY_HOTPLUG=y
CONFIG_MEMORY_HOTPLUG_SPARSE=y
CONFIG_MEMORY_HOTREMOVE=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_MIGRATION=y
CONFIG_RESOURCES_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_ARCH_MEMORY_PROBE=y
CONFIG_NODES_SPAN_OTHER_NODES=y
# CONFIG_PPC_HAS_HASH_64K is not set
# CONFIG_PPC_64K_PAGES is not set
# CONFIG_SCHED_SMT is not set
CONFIG_PROC_DEVICETREE=y
# CONFIG_CMDLINE_BOOL is not set
# CONFIG_PM is not set
CONFIG_SECCOMP=y
CONFIG_ISA_DMA_API=y
#
# Bus options
#
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
# CONFIG_PPC_INDIRECT_PCI is not set
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCI_SYSCALL=y
# CONFIG_PCIEPORTBUS is not set
CONFIG_ARCH_SUPPORTS_MSI=y
# CONFIG_PCI_MSI is not set
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCCARD is not set
CONFIG_HOTPLUG_PCI=y
# CONFIG_HOTPLUG_PCI_FAKE is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set
CONFIG_HOTPLUG_PCI_RPA=y
CONFIG_HOTPLUG_PCI_RPA_DLPAR=y
CONFIG_KERNEL_START=0xc000000000000000
#
# Networking
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=y
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# 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=y
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
# CONFIG_INET_LRO is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# 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_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_TCPPROBE is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
#
# Wireless
#
# CONFIG_CFG80211 is not set
# CONFIG_WIRELESS_EXT is not set
# CONFIG_MAC80211 is not set
# CONFIG_IEEE80211 is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
# CONFIG_MTD is not set
CONFIG_OF_DEVICE=y
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=y
# 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=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
CONFIG_BLK_DEV_NBD=y
# CONFIG_BLK_DEV_SX8 is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_MISC_DEVICES=y
# CONFIG_PHANTOM is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ENCLOSURE_SERVICES is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SCSI_FC_ATTRS=m
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_IBMVSCSI is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_STEX is not set
CONFIG_SCSI_SYM53C8XX_2=y
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=0
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_MMIO=y
CONFIG_SCSI_IPR=y
CONFIG_SCSI_IPR_TRACE=y
CONFIG_SCSI_IPR_DUMP=y
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA_FC=m
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
# CONFIG_SATA_AHCI is not set
# CONFIG_SATA_SVW is not set
# CONFIG_ATA_PIIX is not set
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SX4 is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIL24 is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
# CONFIG_PATA_PLATFORM is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
# CONFIG_BLK_DEV_DM is not set
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
# CONFIG_I2O is not set
CONFIG_MACINTOSH_DRIVERS=y
# CONFIG_ADB_PMU is not set
# CONFIG_PMAC_SMU is not set
# CONFIG_MAC_EMUMOUSEBTN is not set
# CONFIG_WINDFARM is not set
# CONFIG_PMAC_RACKMETER is not set
CONFIG_NETDEVICES=y
# CONFIG_NETDEVICES_MULTIQUEUE is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_ARCNET is not set
# CONFIG_PHYLIB is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=y
# CONFIG_TYPHOON is not set
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
# CONFIG_IBMVETH is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
CONFIG_NET_PCI=y
CONFIG_PCNET32=y
# CONFIG_PCNET32_NAPI is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_EEPRO100 is not set
CONFIG_E100=y
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_R6040 is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SC92031 is not set
CONFIG_NETDEV_1000=y
CONFIG_ACENIC=y
CONFIG_ACENIC_OMIT_TIGON_I=y
# CONFIG_DL2K is not set
CONFIG_E1000=y
# CONFIG_E1000_NAPI is not set
# CONFIG_E1000_DISABLE_PACKET_SPLIT is not set
# CONFIG_E1000E is not set
# CONFIG_E1000E_ENABLED is not set
# CONFIG_IP1000 is not set
# CONFIG_IGB 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
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
CONFIG_NETDEV_10000=y
# CONFIG_CHELSIO_T1 is not set
# CONFIG_CHELSIO_T3 is not set
# CONFIG_IXGBE is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
# CONFIG_MYRI10GE is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_NIU is not set
# CONFIG_PASEMI_MAC is not set
# CONFIG_MLX4_CORE is not set
# CONFIG_TEHUTI is not set
# CONFIG_BNX2X is not set
# CONFIG_TR is not set
#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
# 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_NET_FC is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV 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_KEYBOARD_STOWAWAY is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_PS2_ELANTECH is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
# CONFIG_INPUT_ATI_REMOTE is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
# CONFIG_INPUT_UINPUT is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT 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=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
CONFIG_DEVKMEM=y
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_PMACZILOG is not set
# CONFIG_SERIAL_ICOM is not set
# CONFIG_SERIAL_JSM is not set
# CONFIG_SERIAL_OF_PLATFORM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_HVC_DRIVER=y
CONFIG_HVC_CONSOLE=y
# CONFIG_HVC_RTAS is not set
# CONFIG_HVCS is not set
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=m
# CONFIG_GEN_RTC is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
CONFIG_RAW_DRIVER=y
CONFIG_MAX_RAW_DEVS=256
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
CONFIG_DEVPORT=y
# CONFIG_I2C is not set
# CONFIG_SPI is not set
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
CONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
CONFIG_THERMAL=y
# CONFIG_WATCHDOG is not set
#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not set
#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
CONFIG_DAB=y
#
# Graphics support
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_VGASTATE is not set
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
# CONFIG_FB_DDC is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
CONFIG_FB_FOREIGN_ENDIAN=y
CONFIG_FB_BOTH_ENDIAN=y
# CONFIG_FB_BIG_ENDIAN is not set
# CONFIG_FB_LITTLE_ENDIAN is not set
# CONFIG_FB_SYS_FOPS is not set
CONFIG_FB_DEFERRED_IO=y
# CONFIG_FB_SVGALIB is not set
CONFIG_FB_MACMODES=y
# CONFIG_FB_BACKLIGHT is not set
# CONFIG_FB_MODE_HELPERS is not set
CONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
CONFIG_FB_OF=y
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
CONFIG_FB_MATROX=y
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
# CONFIG_FB_MATROX_G is not set
# CONFIG_FB_MATROX_I2C is not set
CONFIG_FB_MATROX_MULTIHEAD=y
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_IBM_GXT4500 is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
#
# Console display driver support
#
# CONFIG_VGA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
#
# Sound
#
# CONFIG_SOUND is not set
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set
# CONFIG_HIDRAW is not set
CONFIG_USB_SUPPORT=y
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'
#
# CONFIG_USB_GADGET is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
# CONFIG_EDAC is not set
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
# CONFIG_UIO is not set
#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_REISER4_FS is not set
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR 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 is not set
CONFIG_XFS_FS=y
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_SECURITY is not set
# CONFIG_XFS_POSIX_ACL is not set
# CONFIG_XFS_RT is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_AUTOFS_FS=y
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
# CONFIG_JOLIET is not set
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
# CONFIG_PROC_KCORE is not set
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
# CONFIG_TMPFS is not set
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
# CONFIG_CONFIGFS_FS is not set
#
# Layered filesystems
#
CONFIG_UNION_FS=y
CONFIG_UNION_FS_XATTR=y
# CONFIG_UNION_FS_DEBUG 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=y
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
# CONFIG_NFSD_V4 is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
# CONFIG_SUNRPC_BIND34 is not set
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
CONFIG_CIFS=y
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
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
# CONFIG_DLM is not set
#
# Library routines
#
CONFIG_BITREVERSE=y
# CONFIG_CRC_CCITT is not set
CONFIG_CRC16=m
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_HAVE_LMB=y
#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_PAGE_OWNER=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_SCHED_DEBUG=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_WRITECOUNT is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_PROFILE_LIKELY is not set
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_DEBUG_SYNCHRO_TEST is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_KPROBES_SANITY_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_LKDTM is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_SAMPLES is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_HCALL_STATS is not set
# CONFIG_DEBUGGER is not set
# CONFIG_IRQSTACKS is not set
# CONFIG_VIRQ_DEBUG is not set
# CONFIG_BOOTX_TEXT is not set
# CONFIG_PPC_EARLY_DEBUG is not set
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=y
# CONFIG_CRYPTO_SEQIV is not set
CONFIG_CRYPTO_MANAGER=y
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC 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_GF128MUL is not set
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_PCBC=m
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_XTS is not set
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
# 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_CAST5 is not set
# 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_SEED is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_TEST is not set
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_LZO is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_HIFN_795X is not set
# CONFIG_PPC_CLOCK is not set
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: 2.6.25-rc3-mm1 ppc64 boot hang
2008-03-05 21:34 ` 2.6.25-rc3-mm1 ppc64 boot hang Badari Pulavarty
@ 2008-03-05 21:54 ` Andrew Morton
2008-03-05 22:35 ` Badari Pulavarty
2008-03-05 23:17 ` Stephen Rothwell
0 siblings, 2 replies; 76+ messages in thread
From: Andrew Morton @ 2008-03-05 21:54 UTC (permalink / raw)
To: Badari Pulavarty; +Cc: linux-kernel, linuxppc-dev, Matthew Wilcox
On Wed, 05 Mar 2008 13:34:14 -0800
Badari Pulavarty <pbadari@gmail.com> wrote:
> On Tue, 2008-03-04 at 01:19 -0800, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
> >
>
> Hi Andrew,
>
> Not able to boot 2.6.25-rc3-mm1 my ppc64 box.
> 2.6.25-rc2-mm1 and 2.6.25-rc3 boots fine.
>
> I applied slab.c fix also.
>
> Any other known issues ? My config file attached.
> Here are the messages on the console.
The semaphore consolidation code enables interrupts early in boot, when it
shouldn't. This tends to make powerpc blow up. Could be that this is what
you're hitting.
Matthew, is this ging to be fixed soon?
Thanks.
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 ppc64 boot hang
2008-03-05 21:54 ` Andrew Morton
@ 2008-03-05 22:35 ` Badari Pulavarty
2008-03-05 23:17 ` Stephen Rothwell
1 sibling, 0 replies; 76+ messages in thread
From: Badari Pulavarty @ 2008-03-05 22:35 UTC (permalink / raw)
To: Andrew Morton; +Cc: lkml, linuxppc-dev, Matthew Wilcox
On Wed, 2008-03-05 at 13:54 -0800, Andrew Morton wrote:
> On Wed, 05 Mar 2008 13:34:14 -0800
> Badari Pulavarty <pbadari@gmail.com> wrote:
>
> > On Tue, 2008-03-04 at 01:19 -0800, Andrew Morton wrote:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
> > >
> >
> > Hi Andrew,
> >
> > Not able to boot 2.6.25-rc3-mm1 my ppc64 box.
> > 2.6.25-rc2-mm1 and 2.6.25-rc3 boots fine.
> >
> > I applied slab.c fix also.
> >
> > Any other known issues ? My config file attached.
> > Here are the messages on the console.
>
> The semaphore consolidation code enables interrupts early in boot, when it
> shouldn't. This tends to make powerpc blow up. Could be that this is what
> you're hitting.
>
> Matthew, is this ging to be fixed soon?
Yes. I just backed out git-semaphore.patch and machine booted fine.
Thanks,
Badari
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 ppc64 boot hang
2008-03-05 21:54 ` Andrew Morton
2008-03-05 22:35 ` Badari Pulavarty
@ 2008-03-05 23:17 ` Stephen Rothwell
1 sibling, 0 replies; 76+ messages in thread
From: Stephen Rothwell @ 2008-03-05 23:17 UTC (permalink / raw)
To: Andrew Morton
Cc: Badari Pulavarty, Matthew Wilcox, linuxppc-dev, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
Hi Andrew,
On Wed, 5 Mar 2008 13:54:25 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> The semaphore consolidation code enables interrupts early in boot, when it
> shouldn't. This tends to make powerpc blow up. Could be that this is what
> you're hitting.
>
> Matthew, is this ging to be fixed soon?
There is a new version of these patches in the current linux-next tree ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 76+ messages in thread
* 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-04 9:19 2.6.25-rc3-mm1 Andrew Morton
` (11 preceding siblings ...)
2008-03-05 21:34 ` 2.6.25-rc3-mm1 ppc64 boot hang Badari Pulavarty
@ 2008-03-07 3:58 ` Valdis.Kletnieks
2008-03-07 6:16 ` Andrew Morton
2008-03-12 7:32 ` Andrew Morton
12 siblings, 2 replies; 76+ messages in thread
From: Valdis.Kletnieks @ 2008-03-07 3:58 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 3705 bytes --]
On Tue, 04 Mar 2008 01:19:28 PST, Andrew Morton said:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
Dell Latitude D820, x86_64, Core2 Duo T7200
'shutdown -h' blows up at the very end. shutdown -r works OK. I caught this one
with netconsole. There's another, different, crash I've been seeing a bit
earlier in the shutdown -h as well, but I haven't been able to catch that one
yet...
[ 74.254402] CPU 1 is now offline
[ 74.255395] SMP alternatives: switching to UP code
[ 74.256373] BUG: unable to handle kernel paging request at ffffffff8020a023
[ 74.256373] IP: [<ffffffff80211872>] alternatives_smp_unlock+0x66/0x7b
[ 74.256373] PGD 203067 PUD 207063 PMD 7e4cc163 PTE 20a161
[ 74.256373] Oops: 0003 [1] PREEMPT SMP
[ 74.256373] last sysfs file: /sys/devices/virtual/block/dm-14/dev
[ 74.256373] CPU 0
[ 74.256373] Modules linked in: rtc sha256_generic aes_generic acpi_cpufreq tpm_tis arc4 ecb pcmcia iwl3945 iTCO_wdt ohci1394 firmware_class iTCO_vendor_support yenta_socket watchdog_core thermal rsrc_nonstatic mac80211 snd_hda_intel intel_agp watchdog_dev ieee1394 pcmcia_core processor button ac battery cfg80211
[ 74.256373] Pid: 1767, comm: halt Not tainted 2.6.25-rc3-mm1 #8
[ 74.256373] RIP: 0010:[<ffffffff80211872>] [<ffffffff80211872>] alternatives_smp_unlock+0x66/0x7b
[ 74.256373] RSP: 0018:ffff81007ac63d10 EFLAGS: 00010093
[ 74.256373] RAX: ffffffff80573190 RBX: ffff81007f83a8c0 RCX: ffffffff80563cec
[ 74.256373] RDX: ffffffff8020a023 RSI: ffffffff8078a0b8 RDI: ffffffff80783018
[ 74.256373] RBP: ffff81007ac63d28 R08: 0000000000000001 R09: ffffffff80563cec
[ 74.256373] R10: ffffffff80200000 R11: ffff81007ac63d1f R12: 0000000000000000
[ 74.256373] R13: 0000000000000001 R14: 0000000000000246 R15: ffff81007d156340
[ 74.256373] FS: 00007f2d0ab206f0(0000) GS:ffffffff8076e000(0000) knlGS:0000000000000000
[ 74.256373] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 74.256373] CR2: ffffffff8020a023 CR3: 000000007edf3000 CR4: 00000000000006e0
[ 74.256373] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 74.256373] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 74.256373] Process halt (pid: 1767, threadinfo ffff81007ac62000, task ffff81007db96300)
[ 74.256373] Stack: ffffffff8080df80 90ffffff8055ba3b ffff81007f83a8c0 ffff81007ac63d68
[ 74.256374] ffffffff80211a01 ffffffff807c6584 0000000000000001 ffffffff807c6584
[ 74.256374] 0000000000000001 0000000000000001 0000000000000001 ffff81007ac63d98
[ 74.256374] Call Trace:
[ 74.256374] [<ffffffff80211a01>] alternatives_smp_switch+0x17a/0x1b6
[ 74.256374] [<ffffffff80219dd3>] __cpu_die+0x58/0x87
[ 74.256374] [<ffffffff805498b2>] _cpu_down+0x1a4/0x28c
[ 74.256374] [<ffffffff80252e90>] disable_nonboot_cpus+0x60/0x108
[ 74.256374] [<ffffffff80241619>] kernel_power_off+0x21/0x3b
[ 74.256374] [<ffffffff80241863>] sys_reboot+0xf8/0x196
[ 74.256374] [<ffffffff8055b93f>] ? preempt_schedule+0x3c/0xaa
[ 74.256374] [<ffffffff8055b9a4>] ? preempt_schedule+0xa1/0xaa
[ 74.256374] [<ffffffff8023e7eb>] ? sys_kill+0xd8/0x1c1
[ 74.256374] [<ffffffff8055c112>] ? do_nanosleep+0x4b/0xd6
[ 74.256374] [<ffffffff8020c21b>] system_call_after_swapgs+0x7b/0x80
[ 74.256374]
[ 74.256374]
[ 74.256374] Code: 57 80 48 0f 42 d0 48 8b 42 08 4c 8d 5d f7 8a 00 41 b8 01 00 00 00 88 45 f7 eb 1b 48 8b 17 4c 39 d2 72 0f 4c 39 ca 77 0a 41 8a 03 <88> 02 44 89 c0 0f a2 48 83 c7 08 48 39 f7 72 e0 5a 59 5b c9 c3
[ 74.256374] RIP [<ffffffff80211872>] alternatives_smp_unlock+0x66/0x7b
[ 74.256374] RSP <ffff81007ac63d10>
[ 74.256374] CR2: ffffffff8020a023
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-07 3:58 ` 2.6.25-rc3-mm1 - BUG at system shutdown time Valdis.Kletnieks
@ 2008-03-07 6:16 ` Andrew Morton
2008-03-07 7:52 ` Valdis.Kletnieks
2008-03-12 7:32 ` Andrew Morton
1 sibling, 1 reply; 76+ messages in thread
From: Andrew Morton @ 2008-03-07 6:16 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: linux-kernel, Ingo Molnar, Thomas Gleixner
On Thu, 06 Mar 2008 22:58:45 -0500 Valdis.Kletnieks@vt.edu wrote:
> On Tue, 04 Mar 2008 01:19:28 PST, Andrew Morton said:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
>
> Dell Latitude D820, x86_64, Core2 Duo T7200
>
> 'shutdown -h' blows up at the very end. shutdown -r works OK. I caught this one
> with netconsole. There's another, different, crash I've been seeing a bit
> earlier in the shutdown -h as well, but I haven't been able to catch that one
> yet...
>
> [ 74.254402] CPU 1 is now offline
> [ 74.255395] SMP alternatives: switching to UP code
> [ 74.256373] BUG: unable to handle kernel paging request at ffffffff8020a023
> [ 74.256373] IP: [<ffffffff80211872>] alternatives_smp_unlock+0x66/0x7b
> [ 74.256373] PGD 203067 PUD 207063 PMD 7e4cc163 PTE 20a161
> [ 74.256373] Oops: 0003 [1] PREEMPT SMP
> [ 74.256373] last sysfs file: /sys/devices/virtual/block/dm-14/dev
> [ 74.256373] CPU 0
> [ 74.256373] Modules linked in: rtc sha256_generic aes_generic acpi_cpufreq tpm_tis arc4 ecb pcmcia iwl3945 iTCO_wdt ohci1394 firmware_class iTCO_vendor_support yenta_socket watchdog_core thermal rsrc_nonstatic mac80211 snd_hda_intel intel_agp watchdog_dev ieee1394 pcmcia_core processor button ac battery cfg80211
> [ 74.256373] Pid: 1767, comm: halt Not tainted 2.6.25-rc3-mm1 #8
> [ 74.256373] RIP: 0010:[<ffffffff80211872>] [<ffffffff80211872>] alternatives_smp_unlock+0x66/0x7b
> [ 74.256373] RSP: 0018:ffff81007ac63d10 EFLAGS: 00010093
> [ 74.256373] RAX: ffffffff80573190 RBX: ffff81007f83a8c0 RCX: ffffffff80563cec
> [ 74.256373] RDX: ffffffff8020a023 RSI: ffffffff8078a0b8 RDI: ffffffff80783018
> [ 74.256373] RBP: ffff81007ac63d28 R08: 0000000000000001 R09: ffffffff80563cec
> [ 74.256373] R10: ffffffff80200000 R11: ffff81007ac63d1f R12: 0000000000000000
> [ 74.256373] R13: 0000000000000001 R14: 0000000000000246 R15: ffff81007d156340
> [ 74.256373] FS: 00007f2d0ab206f0(0000) GS:ffffffff8076e000(0000) knlGS:0000000000000000
> [ 74.256373] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> [ 74.256373] CR2: ffffffff8020a023 CR3: 000000007edf3000 CR4: 00000000000006e0
> [ 74.256373] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ 74.256373] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [ 74.256373] Process halt (pid: 1767, threadinfo ffff81007ac62000, task ffff81007db96300)
> [ 74.256373] Stack: ffffffff8080df80 90ffffff8055ba3b ffff81007f83a8c0 ffff81007ac63d68
> [ 74.256374] ffffffff80211a01 ffffffff807c6584 0000000000000001 ffffffff807c6584
> [ 74.256374] 0000000000000001 0000000000000001 0000000000000001 ffff81007ac63d98
> [ 74.256374] Call Trace:
> [ 74.256374] [<ffffffff80211a01>] alternatives_smp_switch+0x17a/0x1b6
> [ 74.256374] [<ffffffff80219dd3>] __cpu_die+0x58/0x87
> [ 74.256374] [<ffffffff805498b2>] _cpu_down+0x1a4/0x28c
> [ 74.256374] [<ffffffff80252e90>] disable_nonboot_cpus+0x60/0x108
> [ 74.256374] [<ffffffff80241619>] kernel_power_off+0x21/0x3b
> [ 74.256374] [<ffffffff80241863>] sys_reboot+0xf8/0x196
> [ 74.256374] [<ffffffff8055b93f>] ? preempt_schedule+0x3c/0xaa
> [ 74.256374] [<ffffffff8055b9a4>] ? preempt_schedule+0xa1/0xaa
> [ 74.256374] [<ffffffff8023e7eb>] ? sys_kill+0xd8/0x1c1
> [ 74.256374] [<ffffffff8055c112>] ? do_nanosleep+0x4b/0xd6
> [ 74.256374] [<ffffffff8020c21b>] system_call_after_swapgs+0x7b/0x80
> [ 74.256374]
> [ 74.256374]
> [ 74.256374] Code: 57 80 48 0f 42 d0 48 8b 42 08 4c 8d 5d f7 8a 00 41 b8 01 00 00 00 88 45 f7 eb 1b 48 8b 17 4c 39 d2 72 0f 4c 39 ca 77 0a 41 8a 03 <88> 02 44 89 c0 0f a2 48 83 c7 08 48 39 f7 72 e0 5a 59 5b c9 c3
> [ 74.256374] RIP [<ffffffff80211872>] alternatives_smp_unlock+0x66/0x7b
> [ 74.256374] RSP <ffff81007ac63d10>
> [ 74.256374] CR2: ffffffff8020a023
Yes, I hit a similar one during halt on the t61p. But because of the
netconsole bustage I was only able to see (on the screen) oops #2 - oops #1
had scrolled off. oops #2 had a simlar trace and the EIP was in
text_poke().
I suppose one of us should bisect it.
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-07 6:16 ` Andrew Morton
@ 2008-03-07 7:52 ` Valdis.Kletnieks
2008-03-07 8:06 ` Thomas Gleixner
0 siblings, 1 reply; 76+ messages in thread
From: Valdis.Kletnieks @ 2008-03-07 7:52 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, Ingo Molnar, Thomas Gleixner
[-- Attachment #1: Type: text/plain, Size: 15434 bytes --]
On Thu, 06 Mar 2008 22:16:02 PST, Andrew Morton said:
> > [ 74.254402] CPU 1 is now offline
> > [ 74.255395] SMP alternatives: switching to UP code
> > [ 74.256373] BUG: unable to handle kernel paging request at ffffffff8020a023
> > [ 74.256373] IP: [<ffffffff80211872>] alternatives_smp_unlock+0x66/0x7b
> > [ 74.256373] PGD 203067 PUD 207063 PMD 7e4cc163 PTE 20a161
> > [ 74.256373] Oops: 0003 [1] PREEMPT SMP
> > [ 74.256373] last sysfs file: /sys/devices/virtual/block/dm-14/dev
> > [ 74.256373] CPU 0
> > [ 74.256373] Modules linked in: rtc sha256_generic aes_generic acpi_cpufreq tpm_tis arc4 ecb pcmcia iwl3945 iTCO_wdt ohci1394 firmware_class iTCO_vendor_support yenta_socket watchdog_core thermal rsrc_nonstatic mac80211 snd_hda_intel intel_agp watchdog_dev ieee1394 pcmcia_core processor button ac battery cfg80211
> > [ 74.256373] Pid: 1767, comm: halt Not tainted 2.6.25-rc3-mm1 #8
> > [ 74.256373] RIP: 0010:[<ffffffff80211872>] [<ffffffff80211872>] alternatives_smp_unlock+0x66/0x7b
> > [ 74.256373] RSP: 0018:ffff81007ac63d10 EFLAGS: 00010093
> > [ 74.256373] RAX: ffffffff80573190 RBX: ffff81007f83a8c0 RCX: ffffffff80563cec
> > [ 74.256373] RDX: ffffffff8020a023 RSI: ffffffff8078a0b8 RDI: ffffffff80783018
> > [ 74.256373] RBP: ffff81007ac63d28 R08: 0000000000000001 R09: ffffffff80563cec
> > [ 74.256373] R10: ffffffff80200000 R11: ffff81007ac63d1f R12: 0000000000000000
> > [ 74.256373] R13: 0000000000000001 R14: 0000000000000246 R15: ffff81007d156340
> > [ 74.256373] FS: 00007f2d0ab206f0(0000) GS:ffffffff8076e000(0000) knlGS:0000000000000000
> > [ 74.256373] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> > [ 74.256373] CR2: ffffffff8020a023 CR3: 000000007edf3000 CR4: 00000000000006e0
> > [ 74.256373] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > [ 74.256373] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> > [ 74.256373] Process halt (pid: 1767, threadinfo ffff81007ac62000, task ffff81007db96300)
> > [ 74.256373] Stack: ffffffff8080df80 90ffffff8055ba3b ffff81007f83a8c0 ffff81007ac63d68
> > [ 74.256374] ffffffff80211a01 ffffffff807c6584 0000000000000001 ffffffff807c6584
> > [ 74.256374] 0000000000000001 0000000000000001 0000000000000001 ffff81007ac63d98
> > [ 74.256374] Call Trace:
> > [ 74.256374] [<ffffffff80211a01>] alternatives_smp_switch+0x17a/0x1b6
> > [ 74.256374] [<ffffffff80219dd3>] __cpu_die+0x58/0x87
> > [ 74.256374] [<ffffffff805498b2>] _cpu_down+0x1a4/0x28c
> > [ 74.256374] [<ffffffff80252e90>] disable_nonboot_cpus+0x60/0x108
> > [ 74.256374] [<ffffffff80241619>] kernel_power_off+0x21/0x3b
> > [ 74.256374] [<ffffffff80241863>] sys_reboot+0xf8/0x196
> > [ 74.256374] [<ffffffff8055b93f>] ? preempt_schedule+0x3c/0xaa
> > [ 74.256374] [<ffffffff8055b9a4>] ? preempt_schedule+0xa1/0xaa
> > [ 74.256374] [<ffffffff8023e7eb>] ? sys_kill+0xd8/0x1c1
> > [ 74.256374] [<ffffffff8055c112>] ? do_nanosleep+0x4b/0xd6
> > [ 74.256374] [<ffffffff8020c21b>] system_call_after_swapgs+0x7b/0x80
> > [ 74.256374]
> > [ 74.256374]
> > [ 74.256374] Code: 57 80 48 0f 42 d0 48 8b 42 08 4c 8d 5d f7 8a 00 41 b8 01 00 00 00 88 45 f7 eb 1b 48 8b 17 4c 39 d2 72 0f 4c 39 ca 77 0a 41 8a 03 <88> 02 44 89 c0 0f a2 48 83 c7 08 48 39 f7 72 e0 5a 59 5b c9 c3
> > [ 74.256374] RIP [<ffffffff80211872>] alternatives_smp_unlock+0x66/0x7b
> > [ 74.256374] RSP <ffff81007ac63d10>
> > [ 74.256374] CR2: ffffffff8020a023
>
> Yes, I hit a similar one during halt on the t61p. But because of the
> netconsole bustage I was only able to see (on the screen) oops #2 - oops #1
> had scrolled off. oops #2 had a simlar trace and the EIP was in
> text_poke().
OK, I finally managed to catch the *other* failure I was seeing at shutdown,
and it appears to be a variant on the same theme, so readers may feel free to
ignore the rest of this note unless they care about the gory details...
Apparently, if I booted with 'ignore_loglevel' (which is my default when using
netconsole), I hit the above traceback and I'm dead in the water, no alt-sysrq,
need to hold down the power button for 5 seconds.
If I boot with 'quiet' instead, I get the below set of tracebacks, which caused
the original BUG to go scrolling off-screen and obfuscating that it's the same
failure. Adding to the confusion, if it failed in this mode, alt-sysrq still
worked just fine, so alt-sysrq-S-S-U-B got me a reboot.
Now that I know that at least *part* of the issue is the same, I can go
bisecting. Somebody *else* can ponder why ignore_loglevel/quiet causes the
big difference in behavior after the BUG, that part is beyond my ken...
[ 168.036824] BUG: unable to handle kernel paging request at ffffffff8020a023
[ 168.037300] IP: [<ffffffff80211872>] alternatives_smp_unlock+0x66/0x7b
[ 168.037745] PGD 203067 PUD 207063 PMD 7f989163 PTE 20a161
[ 168.037781] Oops: 0003 [1] PREEMPT SMP
[ 168.037781] last sysfs file: /sys/devices/platform/coretemp.1/temp1_input
[ 168.037781] CPU 0
[ 168.037781] Modules linked in: rtc irnet ppp_generic slhc irtty_sir sir_dev ircomm_tty ircomm irda crc_ccitt sha256_generic aes_generic acpi_cpufreq tpm_tis arc4 ecb iwl3945 pcmcia nvidia(P)(U) firmware_class mac80211 ohci1394 snd_hda_intel cfg80211 yenta_socket ieee1394 iTCO_wdt iTCO_vendor_support thermal rsrc_nonstatic ac processor watchdog_core battery watchdog_dev button pcmcia_core intel_agp [last unloaded: x_tables]
[ 168.037781] Pid: 3115, comm: halt Tainted: P 2.6.25-rc3-mm1 #8
[ 168.037781] RIP: 0010:[<ffffffff80211872>] [<ffffffff80211872>] alternatives_smp_unlock+0x66/0x7b
[ 168.037781] RSP: 0000:ffff81007dbebd10 EFLAGS: 00010093
[ 168.037781] RAX: ffffffff80573190 RBX: ffff81007f83a8c0 RCX: ffffffff80563cec
[ 168.037781] RDX: ffffffff8020a023 RSI: ffffffff8078a0b8 RDI: ffffffff80783018
[ 168.037781] RBP: ffff81007dbebd28 R08: 0000000000000001 R09: ffffffff80563cec
[ 168.037781] R10: ffffffff80200000 R11: ffff81007dbebd1f R12: 0000000000000000
[ 168.037781] R13: 0000000000000001 R14: 0000000000000246 R15: ffff810073200440
[ 168.037781] FS: 00007ffd6067a6f0(0000) GS:ffffffff8076e000(0000) knlGS:0000000000000000
[ 168.037781] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 168.037781] CR2: ffffffff8020a023 CR3: 000000007306e000 CR4: 00000000000006e0
[ 168.037781] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 168.037781] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 168.037781] Process halt (pid: 3115, threadinfo ffff81007dbea000, task ffff81007ef44440)
[ 168.037781] Stack: ffffffff8080df80 90ffffff8055ba3b ffff81007f83a8c0 ffff81007dbebd68
[ 168.037781] ffffffff80211a01 ffffffff807c6584 0000000000000001 ffffffff807c6584
[ 168.037781] 0000000000000001 0000000000000001 0000000000000001 ffff81007dbebd98
[ 168.037781] Call Trace:
[ 168.037781] [<ffffffff80211a01>] alternatives_smp_switch+0x17a/0x1b6
[ 168.037781] [<ffffffff80219dd3>] __cpu_die+0x58/0x87
[ 168.037781] [<ffffffff805498b2>] _cpu_down+0x1a4/0x28c
[ 168.037781] [<ffffffff80252e90>] disable_nonboot_cpus+0x60/0x108
[ 168.037781] [<ffffffff80241619>] kernel_power_off+0x21/0x3b
[ 168.037781] [<ffffffff80241863>] sys_reboot+0xf8/0x196
[ 168.037781] [<ffffffff80291233>] ? kfree+0x2b/0x1ac
[ 168.037781] [<ffffffff80265a44>] ? audit_syscall_entry+0x16e/0x1a2
[ 168.037781] [<ffffffff80213619>] ? syscall_trace_enter+0xa4/0xa9
[ 168.037781] [<ffffffff8020c32e>] ? tracesys+0x71/0xe1
[ 168.037781] [<ffffffff8020c399>] tracesys+0xdc/0xe1
[ 168.037781]
[ 168.037781]
[ 168.037781] Code: 57 80 48 0f 42 d0 48 8b 42 08 4c 8d 5d f7 8a 00 41 b8 01 00 00 00 88 45 f7 eb 1b 48 8b 17 4c 39 d2 72 0f 4c 39 ca 77 0a 41 8a 03 <88> 02 44 89 c0 0f a2 48 83 c7 08 48 39 f7 72 e0 5a 59 5b c9 c3
[ 168.037781] RIP [<ffffffff80211872>] alternatives_smp_unlock+0x66/0x7b
[ 168.037781] RSP <ffff81007dbebd10>
[ 168.037781] CR2: ffffffff8020a023
[ 168.037781] ---[ end trace 72339cb91f92973c ]---
[ 168.037781] note: halt[3115] exited with preempt_count 1
[ 168.038182] BUG: scheduling while atomic: halt/3115/0x00000002
[ 168.038789] Pid: 3115, comm: halt Tainted: P D 2.6.25-rc3-mm1 #8
[ 168.039791]
[ 168.039793] Call Trace:
[ 168.040795] [<ffffffff8055d761>] ? _spin_unlock_irqrestore+0x3a/0x45
[ 168.041796] [<ffffffff8022bc70>] __schedule_bug+0x5d/0x61
[ 168.042801] [<ffffffff8055ad42>] schedule+0x11a/0x9fd
[ 168.043801] [<ffffffff802e4dad>] ? release_sysfs_dirent+0x8c/0xac
[ 168.044797] [<ffffffff8055b9d5>] schedule_timeout+0x22/0xb4
[ 168.045797] [<ffffffff8037265e>] ? __list_add+0x62/0x9a
[ 168.046796] [<ffffffff8055ab53>] wait_for_common+0x109/0x152
[ 168.047816] [<ffffffff80228819>] ? default_wake_function+0x0/0xf
[ 168.048800] [<ffffffff8055ac26>] wait_for_completion+0x18/0x1a
[ 168.049798] [<ffffffff802428e2>] flush_cpu_workqueue+0x70/0x7c
[ 168.050793] [<ffffffff8024291c>] ? wq_barrier_func+0x0/0xf
[ 168.051794] [<ffffffff8024296e>] flush_workqueue+0x43/0x5d
[ 168.052794] [<ffffffff80242998>] flush_scheduled_work+0x10/0x12
[ 168.053795] [<ffffffff803bd0ce>] release_dev+0x529/0x6c6
[ 168.054799] [<ffffffff802894b5>] ? free_page_and_swap_cache+0x32/0x36
[ 168.055794] [<ffffffff80368bbe>] ? _atomic_dec_and_lock+0x5a/0x98
[ 168.056793] [<ffffffff80368bbe>] ? _atomic_dec_and_lock+0x5a/0x98
[ 168.057795] [<ffffffff803bd424>] tty_release+0x19/0x24
[ 168.058792] [<ffffffff8029630d>] __fput+0xc0/0x21d
[ 168.059793] [<ffffffff8029647e>] fput+0x14/0x16
[ 168.060796] [<ffffffff80292f7a>] filp_close+0x66/0x71
[ 168.061793] [<ffffffff802340a8>] put_files_struct+0x74/0xc3
[ 168.062793] [<ffffffff8023413e>] __exit_files+0x47/0x50
[ 168.063792] [<ffffffff80235c3b>] do_exit+0x39c/0x90b
[ 168.064792] [<ffffffff803ca25d>] ? do_unblank_screen+0x53/0x131
[ 168.065792] [<ffffffff8055e0ad>] oops_begin+0x0/0x90
[ 168.066791] [<ffffffff8020a023>] ? set_personality_64bit+0x14/0x32
[ 168.067794] [<ffffffff8055ff24>] do_page_fault+0x8b9/0x9ad
[ 168.068793] [<ffffffff8055d761>] ? _spin_unlock_irqrestore+0x3a/0x45
[ 168.069790] [<ffffffff80249e46>] ? up+0x42/0x47
[ 168.070790] [<ffffffff8055d761>] ? _spin_unlock_irqrestore+0x3a/0x45
[ 168.071790] [<ffffffff8023239e>] ? release_console_sem+0x1ae/0x1bb
[ 168.072792] [<ffffffff802329bb>] ? vprintk+0x377/0x3aa
[ 168.073791] [<ffffffff802329bb>] ? vprintk+0x377/0x3aa
[ 168.074792] [<ffffffff8055db19>] error_exit+0x0/0x51
[ 168.075795] [<ffffffff80563cec>] ? _etext+0x0/0x7b
[ 168.076790] [<ffffffff80563cec>] ? _etext+0x0/0x7b
[ 168.077787] [<ffffffff8020a023>] ? set_personality_64bit+0x14/0x32
[ 168.078790] [<ffffffff80211872>] ? alternatives_smp_unlock+0x66/0x7b
[ 168.079791] [<ffffffff80211a01>] ? alternatives_smp_switch+0x17a/0x1b6
[ 168.080791] [<ffffffff80219dd3>] ? __cpu_die+0x58/0x87
[ 168.082780] [<ffffffff805498b2>] ? _cpu_down+0x1a4/0x28c
[ 168.083792] [<ffffffff80252e90>] ? disable_nonboot_cpus+0x60/0x108
[ 168.084792] [<ffffffff80241619>] ? kernel_power_off+0x21/0x3b
[ 168.085787] [<ffffffff80241863>] ? sys_reboot+0xf8/0x196
[ 168.086789] [<ffffffff80291233>] ? kfree+0x2b/0x1ac
[ 168.087790] [<ffffffff80265a44>] ? audit_syscall_entry+0x16e/0x1a2
[ 168.088791] [<ffffffff80213619>] ? syscall_trace_enter+0xa4/0xa9
[ 168.089787] [<ffffffff8020c32e>] ? tracesys+0x71/0xe1
[ 168.090788] [<ffffffff8020c399>] ? tracesys+0xdc/0xe1
[ 168.091788]
[ 168.092814] BUG: scheduling while atomic: halt/3115/0x00000002
[ 168.093789] Pid: 3115, comm: halt Tainted: P D 2.6.25-rc3-mm1 #8
[ 168.094783]
[ 168.094785] Call Trace:
[ 168.095787] [<ffffffff8055d76a>] ? _spin_unlock_irqrestore+0x43/0x45
[ 168.096786] [<ffffffff80242721>] ? worker_thread+0xa9/0xee
[ 168.097786] [<ffffffff8022bc70>] __schedule_bug+0x5d/0x61
[ 168.098787] [<ffffffff8055ad42>] schedule+0x11a/0x9fd
[ 168.099790] [<ffffffff802e4dad>] ? release_sysfs_dirent+0x8c/0xac
[ 168.100792] [<ffffffff8055b9d5>] schedule_timeout+0x22/0xb4
[ 168.101787] [<ffffffff8037265e>] ? __list_add+0x62/0x9a
[ 168.102787] [<ffffffff8055ab53>] wait_for_common+0x109/0x152
[ 168.103786] [<ffffffff80228819>] ? default_wake_function+0x0/0xf
[ 168.104788] [<ffffffff8055ac26>] wait_for_completion+0x18/0x1a
[ 168.105784] [<ffffffff802428e2>] flush_cpu_workqueue+0x70/0x7c
[ 168.106785] [<ffffffff8024291c>] ? wq_barrier_func+0x0/0xf
[ 168.107786] [<ffffffff8024296e>] flush_workqueue+0x43/0x5d
[ 168.108785] [<ffffffff80242998>] flush_scheduled_work+0x10/0x12
[ 168.109788] [<ffffffff803bd0ce>] release_dev+0x529/0x6c6
[ 168.110787] [<ffffffff802894b5>] ? free_page_and_swap_cache+0x32/0x36
[ 168.111791] [<ffffffff80368bbe>] ? _atomic_dec_and_lock+0x5a/0x98
[ 168.112785] [<ffffffff80368bbe>] ? _atomic_dec_and_lock+0x5a/0x98
[ 168.113786] [<ffffffff803bd424>] tty_release+0x19/0x24
[ 168.114784] [<ffffffff8029630d>] __fput+0xc0/0x21d
[ 168.115784] [<ffffffff8029647e>] fput+0x14/0x16
[ 168.116783] [<ffffffff80292f7a>] filp_close+0x66/0x71
[ 168.117785] [<ffffffff802340a8>] put_files_struct+0x74/0xc3
[ 168.118788] [<ffffffff8023413e>] __exit_files+0x47/0x50
[ 168.119784] [<ffffffff80235c3b>] do_exit+0x39c/0x90b
[ 168.120783] [<ffffffff803ca25d>] ? do_unblank_screen+0x53/0x131
[ 168.121784] [<ffffffff8055e0ad>] oops_begin+0x0/0x90
[ 168.122782] [<ffffffff8020a023>] ? set_personality_64bit+0x14/0x32
[ 168.123782] [<ffffffff8055ff24>] do_page_fault+0x8b9/0x9ad
[ 168.124784] [<ffffffff8055d761>] ? _spin_unlock_irqrestore+0x3a/0x45
[ 168.126773] [<ffffffff80249e46>] ? up+0x42/0x47
[ 168.127781] [<ffffffff8055d761>] ? _spin_unlock_irqrestore+0x3a/0x45
[ 168.128785] [<ffffffff8023239e>] ? release_console_sem+0x1ae/0x1bb
[ 168.129783] [<ffffffff802329bb>] ? vprintk+0x377/0x3aa
[ 168.130783] [<ffffffff802329bb>] ? vprintk+0x377/0x3aa
[ 168.131783] [<ffffffff8055db19>] error_exit+0x0/0x51
[ 168.132818] [<ffffffff80563cec>] ? _etext+0x0/0x7b
[ 168.133810] [<ffffffff80563cec>] ? _etext+0x0/0x7b
[ 168.134813] [<ffffffff8020a023>] ? set_personality_64bit+0x14/0x32
[ 168.135807] [<ffffffff80211872>] ? alternatives_smp_unlock+0x66/0x7b
[ 168.136783] [<ffffffff80211a01>] ? alternatives_smp_switch+0x17a/0x1b6
[ 168.137785] [<ffffffff80219dd3>] ? __cpu_die+0x58/0x87
[ 168.138781] [<ffffffff805498b2>] ? _cpu_down+0x1a4/0x28c
[ 168.139784] [<ffffffff80252e90>] ? disable_nonboot_cpus+0x60/0x108
[ 168.140780] [<ffffffff80241619>] ? kernel_power_off+0x21/0x3b
[ 168.141779] [<ffffffff80241863>] ? sys_reboot+0xf8/0x196
[ 168.142781] [<ffffffff80291233>] ? kfree+0x2b/0x1ac
[ 168.143781] [<ffffffff80265a44>] ? audit_syscall_entry+0x16e/0x1a2
[ 168.144783] [<ffffffff80213619>] ? syscall_trace_enter+0xa4/0xa9
[ 168.145779] [<ffffffff8020c32e>] ? tracesys+0x71/0xe1
[ 168.146782] [<ffffffff8020c399>] ? tracesys+0xdc/0xe1
[ 168.147779]
[ 168.148798] halt used greatest stack depth: 3304 bytes left
[ 176.814710] SysRq : Emergency Sync
[ 176.815397] Emergency Sync complete
[ 177.804460] SysRq : Emergency Sync
[ 177.806194] Emergency Sync complete
[ 179.663923] SysRq : Emergency Remount R/O
[ 179.664927] Emergency Remount complete
[ 181.729629] SysRq : Emergency Sync
[ 181.730654] Emergency Sync complete
[ 184.781877] SysRq : Resetting
> I suppose one of us should bisect it.
I'll let you know what I find...
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-07 7:52 ` Valdis.Kletnieks
@ 2008-03-07 8:06 ` Thomas Gleixner
2008-03-07 8:23 ` Valdis.Kletnieks
0 siblings, 1 reply; 76+ messages in thread
From: Thomas Gleixner @ 2008-03-07 8:06 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: Andrew Morton, linux-kernel, Ingo Molnar
On Fri, 7 Mar 2008, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 06 Mar 2008 22:16:02 PST, Andrew Morton said:
> > > [ 74.254402] CPU 1 is now offline
> > > [ 74.255395] SMP alternatives: switching to UP code
> > > [ 74.256373] BUG: unable to handle kernel paging request at ffffffff8020a023
Can you decode ffffffff8020a023 via addr2line please ?
Thanks,
tglx
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-07 8:06 ` Thomas Gleixner
@ 2008-03-07 8:23 ` Valdis.Kletnieks
2008-03-07 8:34 ` Thomas Gleixner
0 siblings, 1 reply; 76+ messages in thread
From: Valdis.Kletnieks @ 2008-03-07 8:23 UTC (permalink / raw)
To: Thomas Gleixner; +Cc: Andrew Morton, linux-kernel, Ingo Molnar
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
On Fri, 07 Mar 2008 09:06:59 +0100, Thomas Gleixner said:
> On Fri, 7 Mar 2008, Valdis.Kletnieks@vt.edu wrote:
> > On Thu, 06 Mar 2008 22:16:02 PST, Andrew Morton said:
> > > > [ 74.254402] CPU 1 is now offline
> > > > [ 74.255395] SMP alternatives: switching to UP code
> > > > [ 74.256373] BUG: unable to handle kernel paging request at ffffffff8020a023
>
> Can you decode ffffffff8020a023 via addr2line please ?
It's been a long day, and I couldn't get addr2line to work, it kept saying '??:0'.
However, this is in my System.map:
ffffffff8020a000 t poll_idle
ffffffff8020a009 t do_nothing
ffffffff8020a00f T set_personality_64bit
ffffffff8020a041 T release_thread
ffffffff8020a07d T arch_randomize_brk
so set_personality_64bit+0x14 or so?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-07 8:23 ` Valdis.Kletnieks
@ 2008-03-07 8:34 ` Thomas Gleixner
2008-03-07 19:30 ` Valdis.Kletnieks
0 siblings, 1 reply; 76+ messages in thread
From: Thomas Gleixner @ 2008-03-07 8:34 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: Andrew Morton, linux-kernel, Ingo Molnar
On Fri, 7 Mar 2008, Valdis.Kletnieks@vt.edu wrote:
> On Fri, 07 Mar 2008 09:06:59 +0100, Thomas Gleixner said:
> > On Fri, 7 Mar 2008, Valdis.Kletnieks@vt.edu wrote:
> > > On Thu, 06 Mar 2008 22:16:02 PST, Andrew Morton said:
> > > > > [ 74.254402] CPU 1 is now offline
> > > > > [ 74.255395] SMP alternatives: switching to UP code
> > > > > [ 74.256373] BUG: unable to handle kernel paging request at ffffffff8020a023
> >
> > Can you decode ffffffff8020a023 via addr2line please ?
>
> It's been a long day, and I couldn't get addr2line to work, it kept saying '??:0'.
>
> However, this is in my System.map:
>
> ffffffff8020a000 t poll_idle
> ffffffff8020a009 t do_nothing
> ffffffff8020a00f T set_personality_64bit
> ffffffff8020a041 T release_thread
> ffffffff8020a07d T arch_randomize_brk
>
> so set_personality_64bit+0x14 or so?
Yeah. Sorry for making you do useless work. The meat is here:
> > [ 74.256373] PGD 203067 PUD 207063 PMD 7e4cc163 PTE 20a161
----------------------------------------------------------^^^^^^
The PTE has the RW bit cleared, so the fault is not a big surprise.
Thanks,
tglx
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-07 8:34 ` Thomas Gleixner
@ 2008-03-07 19:30 ` Valdis.Kletnieks
0 siblings, 0 replies; 76+ messages in thread
From: Valdis.Kletnieks @ 2008-03-07 19:30 UTC (permalink / raw)
To: Thomas Gleixner; +Cc: Andrew Morton, linux-kernel, Ingo Molnar
[-- Attachment #1: Type: text/plain, Size: 416 bytes --]
On Fri, 07 Mar 2008 09:34:01 +0100, Thomas Gleixner said:
> Yeah. Sorry for making you do useless work. The meat is here:
>
> > > [ 74.256373] PGD 203067 PUD 207063 PMD 7e4cc163 PTE 20a161
>
> ----------------------------------------------------------^^^^^^
>
> The PTE has the RW bit cleared, so the fault is not a big surprise.
Probably not surprisingly, the quilt bisect says the problem is git-x86,patch.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-07 3:58 ` 2.6.25-rc3-mm1 - BUG at system shutdown time Valdis.Kletnieks
2008-03-07 6:16 ` Andrew Morton
@ 2008-03-12 7:32 ` Andrew Morton
2008-03-13 2:19 ` Valdis.Kletnieks
1 sibling, 1 reply; 76+ messages in thread
From: Andrew Morton @ 2008-03-12 7:32 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: linux-kernel
On Thu, 06 Mar 2008 22:58:45 -0500 Valdis.Kletnieks@vt.edu wrote:
> On Tue, 04 Mar 2008 01:19:28 PST, Andrew Morton said:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
>
> Dell Latitude D820, x86_64, Core2 Duo T7200
>
> 'shutdown -h' blows up at the very end. shutdown -r works OK.
Did rc5-mm1 fix this?
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-12 7:32 ` Andrew Morton
@ 2008-03-13 2:19 ` Valdis.Kletnieks
2008-03-13 2:32 ` Andrew Morton
2008-03-21 13:41 ` Ingo Molnar
0 siblings, 2 replies; 76+ messages in thread
From: Valdis.Kletnieks @ 2008-03-13 2:19 UTC (permalink / raw)
To: Andrew Morton, Ingo Molnar; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]
On Wed, 12 Mar 2008 00:32:27 PDT, Andrew Morton said:
> On Thu, 06 Mar 2008 22:58:45 -0500 Valdis.Kletnieks@vt.edu wrote:
>
> > On Tue, 04 Mar 2008 01:19:28 PST, Andrew Morton said:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/
2.6.25-rc3-mm1/
> >
> > Dell Latitude D820, x86_64, Core2 Duo T7200
> >
> > 'shutdown -h' blows up at the very end. shutdown -r works OK.
>
> Did rc5-mm1 fix this?
Nope, still blows up with exactly the same traceback.
I may have to try again to figure out how to bisect the git-x86 tree - Ingo
send me a pointer to his git-x86 cheat sheet, I looked at it but I couldn't
figure out how to tell 'git bisect' that the starting good spot was "whatever
corresponded to the git-x86 patch in 24-rc8-mm1" and bad was "25-rc3-mm1". I
tried using the first commit ID listed in the patch, but that gave me this:
(looking at first few lines of the git-x86.patch in the 25-rc3-mm1 broken-out):
commit fa70e201463a7f3d86b995249e57a8e27b31b5f8
Author: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Date: Sun Feb 24 11:57:22 2008 +0100
but then:
% git bisect bad fa70e201463a7f3d86b995249e57a8e27b31b5f8
fatal: Needed a single revision
Bad rev input: fa70e201463a7f3d86b995249e57a8e27b31b5f8
And I didn't see any release tags in the x86 git tree that I could specify
either.
(Once I get the good and bad markers set, it "should be easy" - I've managed
to git-bisect through Linus's git tree before, but that was always easy
because "bad" was HEAD and "good" had a nice v2.6.2mumble-rcN tag to specify...
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-13 2:19 ` Valdis.Kletnieks
@ 2008-03-13 2:32 ` Andrew Morton
2008-03-13 3:57 ` Valdis.Kletnieks
2008-03-21 13:41 ` Ingo Molnar
1 sibling, 1 reply; 76+ messages in thread
From: Andrew Morton @ 2008-03-13 2:32 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: Ingo Molnar, linux-kernel
On Wed, 12 Mar 2008 22:19:11 -0400 Valdis.Kletnieks@vt.edu wrote:
> On Wed, 12 Mar 2008 00:32:27 PDT, Andrew Morton said:
> > On Thu, 06 Mar 2008 22:58:45 -0500 Valdis.Kletnieks@vt.edu wrote:
> >
> > > On Tue, 04 Mar 2008 01:19:28 PST, Andrew Morton said:
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/
> 2.6.25-rc3-mm1/
> > >
> > > Dell Latitude D820, x86_64, Core2 Duo T7200
> > >
> > > 'shutdown -h' blows up at the very end. shutdown -r works OK.
> >
> > Did rc5-mm1 fix this?
>
> Nope, still blows up with exactly the same traceback.
ah.
> I may have to try again to figure out how to bisect the git-x86 tree - Ingo
> send me a pointer to his git-x86 cheat sheet, I looked at it but I couldn't
> figure out how to tell 'git bisect' that the starting good spot was "whatever
> corresponded to the git-x86 patch in 24-rc8-mm1" and bad was "25-rc3-mm1". I
> tried using the first commit ID listed in the patch, but that gave me this:
>
> (looking at first few lines of the git-x86.patch in the 25-rc3-mm1 broken-out):
>
> commit fa70e201463a7f3d86b995249e57a8e27b31b5f8
> Author: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
> Date: Sun Feb 24 11:57:22 2008 +0100
>
> but then:
>
> % git bisect bad fa70e201463a7f3d86b995249e57a8e27b31b5f8
> fatal: Needed a single revision
> Bad rev input: fa70e201463a7f3d86b995249e57a8e27b31b5f8
>
> And I didn't see any release tags in the x86 git tree that I could specify
> either.
>
> (Once I get the good and bad markers set, it "should be easy" - I've managed
> to git-bisect through Linus's git tree before, but that was always easy
> because "bad" was HEAD and "good" had a nice v2.6.2mumble-rcN tag to specify...
Yes, it's all a bit mysterious. I just look in the changelog, which was
pull edout of the git diff via various means.
See how
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc5/2.6.25-rc5-mm1/broken-out
starts with 5813a19cba5735b629cdeb156863dab814759128 and ends with
816543f9bf2fb77ff52083216a4537eb4e3058ec. Use
5813a19cba5735b629cdeb156863dab814759128 as good and
816543f9bf2fb77ff52083216a4537eb4e3058ec as bad.
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-13 2:32 ` Andrew Morton
@ 2008-03-13 3:57 ` Valdis.Kletnieks
2008-03-13 4:27 ` Andrew Morton
0 siblings, 1 reply; 76+ messages in thread
From: Valdis.Kletnieks @ 2008-03-13 3:57 UTC (permalink / raw)
To: Andrew Morton; +Cc: Ingo Molnar, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 3579 bytes --]
On Wed, 12 Mar 2008 19:32:30 PDT, Andrew Morton said:
> Yes, it's all a bit mysterious. I just look in the changelog, which was
> pull edout of the git diff via various means.
>
> See how
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc5/2.6.25-rc5-mm1/broken-out
> starts with 5813a19cba5735b629cdeb156863dab814759128 and ends with
> 816543f9bf2fb77ff52083216a4537eb4e3058ec. Use
> 5813a19cba5735b629cdeb156863dab814759128 as good and
> 816543f9bf2fb77ff52083216a4537eb4e3058ec as bad.
I *hope* I'm mis-reading Ingo's directions when I cut-n-pasted them -
first I pulled down the two trees, tried to bisect, had it give me the
"need a single revision" error, then I checked out a tree - and got a
*different* funky opaque error message when I tried to bisect:
[/usr/src/valdis/x86.git] git-init-db
Initialized empty Git repository in .git/
[/usr/src/valdis/x86.git] git-remote add linus git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
[/usr/src/valdis/x86.git] git-remote add x86 git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git
[/usr/src/valdis/x86.git] git-remote update
Updating linus
warning: no common commits
(...)
Resolving deltas: 100% (598008/598008), done.
>From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
* [new branch] master -> linus/master
remote: Counting objects: 105, done.
(...)
>From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
* [new tag] v2.6.12 -> v2.6.12
* [new tag] v2.6.12-rc2 -> v2.6.12-rc2
(...)
* [new tag] v2.6.25-rc4 -> v2.6.25-rc4
* [new tag] v2.6.25-rc5 -> v2.6.25-rc5
Updating x86
remote: Counting objects: 2651, done.
(...)
Resolving deltas: 100% (1979/1979)
s: 100% (1979/1979), completed with 310 local objects.
>From git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86
* [new branch] base -> x86/base
* [new branch] for-akpm -> x86/for-akpm
* [new branch] for-linus -> x86/for-linus
* [new branch] latest -> x86/latest
* [new branch] master -> x86/master
* [new branch] origin -> x86/origin
* [new branch] testing -> x86/testing
[/usr/src/valdis/x86.git] git bisect start
[/usr/src/valdis/x86.git] git bisect good 5813a19cba5735b629cdeb156863dab814759128
fatal: Needed a single revision
Bad rev commit: ^{commit}
[/usr/src/valdis/x86.git] git branch list
fatal: Not a valid object name: 'master'.
[/usr/src/valdis/x86.git] git checkout -b x86-off x86/for-akpm
warning: You appear to be on a branch yet to be born.
warning: Forcing checkout of x86/for-akpm.
Checking out files: 25% (5948/23789)
Checking out files: 31% (7375/23789)
Checking out files: 37% (8809/23789)
Checking out files: 43% (10230/23789)
Checking out files: 48% (11466/23789)
Checking out files: 54% (12847/23789)
Checking out files: 58% (13811/23789)
Checking out files: 64% (15225/23789)
Checking out files: 69% (16415/23789)
Checking out files: 75% (17842/23789)
Checking out files: 81% (19032/23789)
Checking out files: 87% (20659/23789)
Checking out files: 92% (21886/23789)
Checking out files: 97% (23076/23789)
Checking out files: 100% (23789/23789), done.
Branch x86-off set up to track remote branch refs/remotes/x86/for-akpm.
Switched to a new branch "x86-off"
[/usr/src/valdis/x86.git] git bisect start
won't bisect on seeked tree
(Google tells me that last message is gone in git 1.5.4.4 - I'm still
on 1.5.4.3). Obviously I'm missing some important clue with working with
more than one remote tree....
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 76+ messages in thread* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-13 3:57 ` Valdis.Kletnieks
@ 2008-03-13 4:27 ` Andrew Morton
2008-03-14 18:50 ` Valdis.Kletnieks
0 siblings, 1 reply; 76+ messages in thread
From: Andrew Morton @ 2008-03-13 4:27 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: Ingo Molnar, linux-kernel
On Wed, 12 Mar 2008 23:57:12 -0400 Valdis.Kletnieks@vt.edu wrote:
> On Wed, 12 Mar 2008 19:32:30 PDT, Andrew Morton said:
>
> > Yes, it's all a bit mysterious. I just look in the changelog, which was
> > pull edout of the git diff via various means.
> >
> > See how
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc5/2.6.25-rc5-mm1/broken-out
> > starts with 5813a19cba5735b629cdeb156863dab814759128 and ends with
> > 816543f9bf2fb77ff52083216a4537eb4e3058ec. Use
> > 5813a19cba5735b629cdeb156863dab814759128 as good and
> > 816543f9bf2fb77ff52083216a4537eb4e3058ec as bad.
>
> I *hope* I'm mis-reading Ingo's directions when I cut-n-pasted them -
> first I pulled down the two trees, tried to bisect, had it give me the
> "need a single revision" error, then I checked out a tree - and got a
> *different* funky opaque error message when I tried to bisect:
Try this:
echo "git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git#for-akpm" > .git/branches/git-foo
git-fetch git-foo
git-checkout git-foo
git-bisect start
git-bisect good 968f7910e8d10e5273977248f3d89193b32e8c20
git-bisect bad c28550f4f68a894a3c05141762f388b5a14f33e3
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-13 4:27 ` Andrew Morton
@ 2008-03-14 18:50 ` Valdis.Kletnieks
0 siblings, 0 replies; 76+ messages in thread
From: Valdis.Kletnieks @ 2008-03-14 18:50 UTC (permalink / raw)
To: Andrew Morton; +Cc: Ingo Molnar, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 6647 bytes --]
On Wed, 12 Mar 2008 21:27:08 PDT, Andrew Morton said:
> Try this:
>
> echo "git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git#for-akpm" > .git/branches/git-foo
> git-fetch git-foo
> git-checkout git-foo
> git-bisect start
> git-bisect good 968f7910e8d10e5273977248f3d89193b32e8c20
> git-bisect bad c28550f4f68a894a3c05141762f388b5a14f33e3
Trying it against what I already pulled down:
[/usr/src/valdis/x86.git] echo "git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git#for-akpm" > .git/branches/git-foo
[/usr/src/valdis/x86.git] git-fetch git-foo
remote: Counting objects: 1642, done.
remote: Compressing objects: 100% (261/261), done.
remote: Total 1296 (delta 1090), reused 1238 (delta 1034)
Receiving objects: 100% (1296/1296), 197.24 KiB | 215 KiB/s, done.
Resolving deltas: 100% (1090/1090), completed with 218 local objects.
[/usr/src/valdis/x86.git] git-checkout git-foo
error: pathspec 'git-foo' did not match any file(s) known to git.
Did you forget to 'git add'?
[/usr/src/valdis/x86.git] git-bisect start
won't bisect on seeked tree
[/usr/src/valdis/x86.git] git-checkout -b git-foo git-foo
git checkout: updating paths is incompatible with switching branches/forcing
Did you intend to checkout 'git-foo' which can not be resolved as commit?
Trying again against a totally clean new directory:
[/usr/src/valdis] git --version
git version 1.5.4.3
[/usr/src/valdis] rm -rf x86.git
[/usr/src/valdis] mkdir x86.git
[/usr/src/valdis] cd x86.git
[/usr/src/valdis/x86.git] git-init-db
Initialized empty Git repository in .git/
[/usr/src/valdis/x86.git] git-remote add linus git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
[/usr/src/valdis/x86.git] git-remote update
Updating linus
warning: no common commits
remote: Counting objects: 721254, done.
remote: Compressing objects: 100% (130309/130309), done.
remote: Total 721254 (delta 598318), reused 711930 (delta 589976)
Receiving objects: 100% (721254/721254), 175.04 MiB | 3535 KiB/s, done.
Resolving deltas: 100% (598318/598318), done.
>From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
* [new branch] master -> linus/master
remote: Counting objects: 105, done.
remote: Compressing objects: 100% (105/105), done.
remote: Total 105 (delta 0), reused 102 (delta 0)
Receiving objects: 100% (105/105), 30.40 KiB, done.
>From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
* [new tag] v2.6.12 -> v2.6.12
* [new tag] v2.6.12-rc2 -> v2.6.12-rc2
(...)
* [new tag] v2.6.25-rc3 -> v2.6.25-rc3
* [new tag] v2.6.25-rc4 -> v2.6.25-rc4
* [new tag] v2.6.25-rc5 -> v2.6.25-rc5
[/usr/src/valdis/x86.git] echo "git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git#for-akpm" > .git/branches/git-foo
[/usr/src/valdis/x86.git] git-fetch git-foo
remote: Counting objects: 1035, done.
remote: Compressing objects: 100% (171/171), done.
remote: Total 909 (delta 777), reused 868 (delta 738)
Receiving objects: 100% (909/909), 138.30 KiB, done.
Resolving deltas: 100% (777/777), completed with 117 local objects.
[/usr/src/valdis/x86.git] git-checkout git-foo
error: pathspec 'git-foo' did not match any file(s) known to git.
Did you forget to 'git add'?
[/usr/src/valdis/x86.git] git-bisect start
[/usr/src/valdis/x86.git] git-bisect good 968f7910e8d10e5273977248f3d89193b32e8c20
fatal: Needed a single revision
Bad rev commit: ^{commit}
Try a third time, pulling down linus and x86 trees:
[/usr/src/valdis] rm -rf x86.git
[/usr/src/valdis] mkdir x86.git
[/usr/src/valdis] cd x86.git
[/usr/src/valdis/x86.git] git-remote add x86 git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git
fatal: Not a git repository at /usr/lib/perl5/vendor_perl/5.10.0/Git.pm line 197.
[/usr/src/valdis/x86.git] git-init-db
Initialized empty Git repository in .git/
[/usr/src/valdis/x86.git] git-remote add x86 git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git
[/usr/src/valdis/x86.git] git-remote add x86 git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git
remote x86 already exists.
[/usr/src/valdis/x86.git] git-remote add linus git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
[/usr/src/valdis/x86.git] git-remote update
Updating linus
warning: no common commits
remote: Counting objects: 721254, done.
remote: Compressing objects: 100% (130309/130309), done.
remote: Total 721254 (delta 598318), reused 711930 (delta 589976)
Receiving objects: 100% (721254/721254), 175.04 MiB | 10032 KiB/s, done.
Resolving deltas: 100% (598318/598318), done.
>From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
* [new branch] master -> linus/master
remote: Counting objects: 105, done.
remote: Compressing objects: 100% (105/105), done.
remote: Total 105 (delta 0), reused 102 (delta 0)
Receiving objects: 100% (105/105), 30.40 KiB, done.
>From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
* [new tag] v2.6.12 -> v2.6.12
* [new tag] v2.6.12-rc2 -> v2.6.12-rc2
* [new tag] v2.6.12-rc3 -> v2.6.12-rc3
(...}
* [new tag] v2.6.25-rc3 -> v2.6.25-rc3
* [new tag] v2.6.25-rc4 -> v2.6.25-rc4
* [new tag] v2.6.25-rc5 -> v2.6.25-rc5
Updating x86
remote: Counting objects: 2651, done.
remote: Compressing objects: 100% (340/340), done.
remote: Total 2320 (delta 1978), reused 2320 (delta 1978)
Receiving objects: 100% (2320/2320), 408.43 KiB | 588 KiB/s, done.
Resolving deltas: 100% (1978/1978), completed with 310 local objects.
>From git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86
* [new branch] base -> x86/base
* [new branch] for-akpm -> x86/for-akpm
* [new branch] for-linus -> x86/for-linus
* [new branch] latest -> x86/latest
* [new branch] master -> x86/master
* [new branch] origin -> x86/origin
* [new branch] testing -> x86/testing
[/usr/src/valdis/x86.git] echo "git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git#for-akpm" > .git/branches/git-foo
[/usr/src/valdis/x86.git] git-fetch git-foo
[/usr/src/valdis/x86.git] git-checkout git-foo
error: pathspec 'git-foo' did not match any file(s) known to git.
Did you forget to 'git add'?
[/usr/src/valdis/x86.git] git-bisect start
[/usr/src/valdis/x86.git] git-bisect good 968f7910e8d10e5273977248f3d89193b32e8c20
fatal: Needed a single revision
Bad rev commit: ^{commit}
Obviously, I'm either a *total* git-idiot, or malevolent spirits have taken
up residence in my laptop and are conspiring to prevent me from troubleshooting
this problem... ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-13 2:19 ` Valdis.Kletnieks
2008-03-13 2:32 ` Andrew Morton
@ 2008-03-21 13:41 ` Ingo Molnar
2008-03-21 19:38 ` Valdis.Kletnieks
1 sibling, 1 reply; 76+ messages in thread
From: Ingo Molnar @ 2008-03-21 13:41 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: Andrew Morton, linux-kernel
* Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> I may have to try again to figure out how to bisect the git-x86 tree -
> Ingo send me a pointer to his git-x86 cheat sheet, I looked at it but
> I couldn't figure out how to tell 'git bisect' that the starting good
> spot was "whatever corresponded to the git-x86 patch in 24-rc8-mm1"
> and bad was "25-rc3-mm1". I tried using the first commit ID listed in
> the patch, but that gave me this:
the best way to bisect the x86.git-only commits is to do:
git-bisect bad x86/latest
git-bisect good x86/base
the 'base' branch is the upstream tree that x86.git is based against.
This will minimize the number of bisection points as well, because
you'll only bisect x86.git patches.
[ and make sure you test x86/base first to establish that it's truly
'good' :-) ]
Ingo
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-21 13:41 ` Ingo Molnar
@ 2008-03-21 19:38 ` Valdis.Kletnieks
2008-03-21 19:58 ` Ingo Molnar
0 siblings, 1 reply; 76+ messages in thread
From: Valdis.Kletnieks @ 2008-03-21 19:38 UTC (permalink / raw)
To: Ingo Molnar; +Cc: Andrew Morton, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 2719 bytes --]
On Fri, 21 Mar 2008 14:41:28 BST, Ingo Molnar said:
>
> * Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
>
> > I may have to try again to figure out how to bisect the git-x86 tree -
> > Ingo send me a pointer to his git-x86 cheat sheet, I looked at it but
> > I couldn't figure out how to tell 'git bisect' that the starting good
> > spot was "whatever corresponded to the git-x86 patch in 24-rc8-mm1"
> > and bad was "25-rc3-mm1". I tried using the first commit ID listed in
> > the patch, but that gave me this:
>
> the best way to bisect the x86.git-only commits is to do:
>
> git-bisect bad x86/latest
> git-bisect good x86/base
OK, *that* got the bisect running. However, after a few bisections, things
are getting weird...
(Note - I haven't done a git pull or update for a week and a bit, so the tree is
as of 03/14 or so...)
'git bisect log' reports:
git-bisect start
# bad: [21a418440c44b6a2cdf38fea2533a5398d6fd939] Move mp_bus_id_to_node to numa.c
git-bisect bad 21a418440c44b6a2cdf38fea2533a5398d6fd939
# good: [dba92d3bc49c036056a48661d2d8fefe4c78375a] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband
git-bisect good dba92d3bc49c036056a48661d2d8fefe4c78375a
# good: [53f0f2bc547fd13a70a6adb86592301ec83b9fc7] x86 mmiotrace: comment about user space ABI
git-bisect good 53f0f2bc547fd13a70a6adb86592301ec83b9fc7
# good: [53f0f2bc547fd13a70a6adb86592301ec83b9fc7] x86 mmiotrace: comment about user space ABI
git-bisect good 53f0f2bc547fd13a70a6adb86592301ec83b9fc7
# good: [53f0f2bc547fd13a70a6adb86592301ec83b9fc7] x86 mmiotrace: comment about user space ABI
git-bisect good 53f0f2bc547fd13a70a6adb86592301ec83b9fc7
# good: [2702dd1be087ac7307b731d884ee48db6e1cdff6] x86: create smpcommon.c
git-bisect good 2702dd1be087ac7307b731d884ee48db6e1cdff6
# good: [ad42b55d36238ebb9fa4d7a538ef691a76397c46] x86: add KERN_INFO to show_unhandled_signals printout
git-bisect good ad42b55d36238ebb9fa4d7a538ef691a76397c46
# good: [56b412e63863ea82a5720315076c7dbd1d9888cd] x86: change x86 to use generic find_next_bit
git-bisect good 56b412e63863ea82a5720315076c7dbd1d9888cd
# good: [42de918f25dc9a49fb9688e22c2a3f2b156cc1bf] x86: prevent unconditional writes to DebugCtl MSR
git-bisect good 42de918f25dc9a49fb9688e22c2a3f2b156cc1bf
At this point, 'git bisect visualize' shows 9 commits left to bisect through,
and all are dated 03/10 or later. However, since 25-rc3-mm1 had the problem,
it had to be something in-tree as of 03/05.
Is it possible that the problem code was in the git-x86 tree when Andrew
pulled for -rc3-mm1 and -rc5-mm1, but had been reverted by the time I grabbed
the tree, so the /x86/base' was in fact *good* by that point?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-21 19:38 ` Valdis.Kletnieks
@ 2008-03-21 19:58 ` Ingo Molnar
2008-03-21 20:05 ` Valdis.Kletnieks
0 siblings, 1 reply; 76+ messages in thread
From: Ingo Molnar @ 2008-03-21 19:58 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: Andrew Morton, linux-kernel
* Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> git-bisect good ad42b55d36238ebb9fa4d7a538ef691a76397c46
> # good: [56b412e63863ea82a5720315076c7dbd1d9888cd] x86: change x86 to use generic find_next_bit
> git-bisect good 56b412e63863ea82a5720315076c7dbd1d9888cd
> # good: [42de918f25dc9a49fb9688e22c2a3f2b156cc1bf] x86: prevent unconditional writes to DebugCtl MSR
> git-bisect good 42de918f25dc9a49fb9688e22c2a3f2b156cc1bf
>
> At this point, 'git bisect visualize' shows 9 commits left to bisect
> through, and all are dated 03/10 or later. However, since 25-rc3-mm1
> had the problem, it had to be something in-tree as of 03/05.
>
> Is it possible that the problem code was in the git-x86 tree when
> Andrew pulled for -rc3-mm1 and -rc5-mm1, but had been reverted by the
> time I grabbed the tree, so the /x86/base' was in fact *good* by that
> point?
no, we frequently regenerate the x86.git tree so the dates have little
relevance. If for any particular pull, x86/base is good and x86/latest
is bad, then the bug is somewhere in those 200-300 patches inbetween.
They are lined up linearly so should be perfectly bisectable.
Ingo
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-21 19:58 ` Ingo Molnar
@ 2008-03-21 20:05 ` Valdis.Kletnieks
2008-03-21 20:12 ` Ingo Molnar
0 siblings, 1 reply; 76+ messages in thread
From: Valdis.Kletnieks @ 2008-03-21 20:05 UTC (permalink / raw)
To: Ingo Molnar; +Cc: Andrew Morton, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 388 bytes --]
On Fri, 21 Mar 2008 20:58:13 BST, Ingo Molnar said:
> no, we frequently regenerate the x86.git tree so the dates have little
> relevance. If for any particular pull, x86/base is good and x86/latest
> is bad, then the bug is somewhere in those 200-300 patches inbetween.
> They are lined up linearly so should be perfectly bisectable.
OK, off to go try the last few bisects then...
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-21 20:05 ` Valdis.Kletnieks
@ 2008-03-21 20:12 ` Ingo Molnar
2008-03-22 3:11 ` Hoo-fscking-ray - (was " Valdis.Kletnieks
0 siblings, 1 reply; 76+ messages in thread
From: Ingo Molnar @ 2008-03-21 20:12 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: Andrew Morton, linux-kernel
* Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> On Fri, 21 Mar 2008 20:58:13 BST, Ingo Molnar said:
>
> > no, we frequently regenerate the x86.git tree so the dates have little
> > relevance. If for any particular pull, x86/base is good and x86/latest
> > is bad, then the bug is somewhere in those 200-300 patches inbetween.
> > They are lined up linearly so should be perfectly bisectable.
>
> OK, off to go try the last few bisects then...
well ... your git bisection log does look suspiciously 'good', so
something is wrong thee i think :-(
the chance to get 8 'good' bisection points in a row is 1:256. OTOH, the
freshest x86 patches are always at the 'end' of the queue - which are
also the ones most likely to break anything.
Are you sure the x86/base point is indeed 'good'? You can check it via:
git-checkout -b tmp x86/base
and build+boot it.
Ingo
^ permalink raw reply [flat|nested] 76+ messages in thread
* Hoo-fscking-ray - (was Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-21 20:12 ` Ingo Molnar
@ 2008-03-22 3:11 ` Valdis.Kletnieks
2008-03-22 12:09 ` Ingo Molnar
0 siblings, 1 reply; 76+ messages in thread
From: Valdis.Kletnieks @ 2008-03-22 3:11 UTC (permalink / raw)
To: Ingo Molnar; +Cc: Andrew Morton, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 2121 bytes --]
On Fri, 21 Mar 2008 21:12:11 BST, Ingo Molnar said:
>
> * Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
>
> > On Fri, 21 Mar 2008 20:58:13 BST, Ingo Molnar said:
> >
> > > no, we frequently regenerate the x86.git tree so the dates have little
> > > relevance. If for any particular pull, x86/base is good and x86/latest
> > > is bad, then the bug is somewhere in those 200-300 patches inbetween.
> > > They are lined up linearly so should be perfectly bisectable.
> >
> > OK, off to go try the last few bisects then...
>
> well ... your git bisection log does look suspiciously 'good', so
> something is wrong thee i think :-(
>
> the chance to get 8 'good' bisection points in a row is 1:256. OTOH, the
> freshest x86 patches are always at the 'end' of the queue - which are
> also the ones most likely to break anything.
On the other hand, this was broken in 25-rc3-mm1, so it's not a "fresh"
patch...
> Are you sure the x86/base point is indeed 'good'? You can check it via:
>
> git-checkout -b tmp x86/base
>
> and build+boot it.
Did that, and it's good (as in 'shutdown -h now' powers off rather than BUG and
hanging).
"You're at Witt's End" -- Adventure, c. 1978
OK.. so far I've got:
25-rc3-mm1 is bad
25-rc5-mm1 is bad, and bisected down to git-x86.patch
x86/base as pulled last week is good
bisected to within the last 9 entries of x86/latest is good.
So I can't seem to replicate it using the git-x86 tree, but bisecting -mm
implicates it. How very strange.
I even went and pulled Andrew's mmotm pile as of this afternoon, and got that
to built after having to heave only a dozen patches over the side and one or
two hand-fixes of patches - and *that* one is good too.
So I'm thinking that it was some "bump in the night" that was broken in the
x86 tree when Andrew pulled it for 25-rc5-mm1, but was fixed by the time I
pulled it a few days later to start git-bisecting it.
Given that -mmotm isn't showing the problem, I'm having a hard time coming
up with enthusiasm to keep chasing it. If I see it happen again in a -mm
or Linus kernel, I'll restart the chase then....
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 76+ messages in thread
* Re: Hoo-fscking-ray - (was Re: 2.6.25-rc3-mm1 - BUG at system shutdown time
2008-03-22 3:11 ` Hoo-fscking-ray - (was " Valdis.Kletnieks
@ 2008-03-22 12:09 ` Ingo Molnar
0 siblings, 0 replies; 76+ messages in thread
From: Ingo Molnar @ 2008-03-22 12:09 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: Andrew Morton, linux-kernel
* Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> Given that -mmotm isn't showing the problem, I'm having a hard time
> coming up with enthusiasm to keep chasing it. If I see it happen
> again in a -mm or Linus kernel, I'll restart the chase then....
if it ever reappears then please check x86/latest first (without any
other -mm bits) and notify us.
Ingo
^ permalink raw reply [flat|nested] 76+ messages in thread