* Re: 2.6.22-rc4-mm1
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-06 11:39 ` Gabriel C
2007-06-06 16:51 ` 2.6.22-rc4-mm1 Andrew Morton
2007-06-06 12:43 ` 2.6.22-rc4-mm1 Cedric Le Goater
` (14 subsequent siblings)
15 siblings, 1 reply; 120+ messages in thread
From: Gabriel C @ 2007-06-06 11:39 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
>
>
Compile error here :
...
LD .tmp_vmlinux1
drivers/built-in.o: In function `acpi_init':
bus.c:(.init.text+0x249a): undefined reference to `pci_mmcfg_late_init'
make: *** [.tmp_vmlinux1] Error 1
....
http://frugalware.org/~crazy/other/mm/2.6.22-rc4-mm1/config
Regards,
Gabriel
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1
2007-06-06 11:39 ` 2.6.22-rc4-mm1 Gabriel C
@ 2007-06-06 16:51 ` Andrew Morton
2007-06-07 0:01 ` 2.6.22-rc4-mm1 Robert Hancock
0 siblings, 1 reply; 120+ messages in thread
From: Andrew Morton @ 2007-06-06 16:51 UTC (permalink / raw)
To: Gabriel C; +Cc: linux-kernel, Robert Hancock
On Wed, 06 Jun 2007 13:39:18 +0200 Gabriel C <nix.or.die@googlemail.com> wrote:
> Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
> >
> >
>
>
> Compile error here :
>
> ...
>
> LD .tmp_vmlinux1
> drivers/built-in.o: In function `acpi_init':
> bus.c:(.init.text+0x249a): undefined reference to `pci_mmcfg_late_init'
> make: *** [.tmp_vmlinux1] Error 1
>
> ....
>
>
> http://frugalware.org/~crazy/other/mm/2.6.22-rc4-mm1/config
>
Yeah, this caused test.kernel.org to fail as well.
There are a couple of fixes in
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/hot-fixes/
which should get things going again.
Robert, I spent some time picking at
mmconfig-validate-against-acpi-motherboard-resources.patch then got bored
with fiddling with it and reverted it outright.
Please, we need to get those prototypes of pci_mmcfg_early_init() and
pci_mmcfg_late_init() into some sane place which works on all
architectures, not duplicate one of them in a C file and even see if we can
avoid the #ifdef CONFIG_PCI_MMCONFIG in arch/i386/pci/init.c
This code area is really messy, due partly to the x86_64 and i386 sharing.
Any changes in there need careful testing and checking.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 16:51 ` 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-07 0:01 ` Robert Hancock
0 siblings, 0 replies; 120+ messages in thread
From: Robert Hancock @ 2007-06-07 0:01 UTC (permalink / raw)
To: Andrew Morton; +Cc: Gabriel C, linux-kernel
Andrew Morton wrote:
> Yeah, this caused test.kernel.org to fail as well.
>
> There are a couple of fixes in
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/hot-fixes/
> which should get things going again.
>
> Robert, I spent some time picking at
> mmconfig-validate-against-acpi-motherboard-resources.patch then got bored
> with fiddling with it and reverted it outright.
The minimal fix would be to put #ifdef CONFIG_PCI_MMCONFIG around the
call to pci_mmcfg_late_init in drivers/acpi/bus.c.
>
> Please, we need to get those prototypes of pci_mmcfg_early_init() and
> pci_mmcfg_late_init() into some sane place which works on all
> architectures, not duplicate one of them in a C file and even see if we can
> avoid the #ifdef CONFIG_PCI_MMCONFIG in arch/i386/pci/init.c
>
> This code area is really messy, due partly to the x86_64 and i386 sharing.
> Any changes in there need careful testing and checking.
I'm not sure there's a point in making the prototypes for those
functions global to all architectures, since it's unlikely anything
non-X86 could make use of them with any similar semantics. We could
provide a no-op definition of those functions to avoid the need to ifdef
the calls, though.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
2007-06-06 11:39 ` 2.6.22-rc4-mm1 Gabriel C
@ 2007-06-06 12:43 ` Cedric Le Goater
2007-06-06 15:18 ` 2.6.22-rc4-mm1 Michal Piotrowski
2007-06-06 13:04 ` 2.6.22-rc4-mm1 Jiri Slaby
` (13 subsequent siblings)
15 siblings, 1 reply; 120+ messages in thread
From: Cedric Le Goater @ 2007-06-06 12:43 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Hi Andrew,
When CONFIG_DEBUG_VM=y, boot on i386 and s390 (the only one tested) ends
with the following.
C.
------------[ cut here ]------------
kernel BUG at mm/rmap.c:557!
invalid opcode: 0000 [#1]
CPU: 0
EIP: 0060:[<c013cbbd>] Not tainted VLI
EFLAGS: 00000206 (2.6.22-rc4-mm1 #1)
EIP is at __page_check_anon_rmap+0x21/0x28
eax: c15bd431 ebx: c1024700 ecx: 000bffa6 edx: c15bb6d0
esi: c1024700 edi: 01238045 ebp: c1423e9c esp: c1423e98
ds: 007b es: 007b fs: 0000 gs: 0033 ss: 0068
Process init (pid: 1, ti=c1422000 task=c14216b0 task.ti=c1422000)
Stack: c1024700 c1423ea8 c013d631 01238045 c1423ef8 c01392a6 c15bb6d0 c15afc40
c15afa40 c15aebfc c15c3bfc bffa7000 bffa6000 bffa7000 c15bae98 c15d5e98
00000000 c15afa90 c15afc90 00000000 00000002 c15d66f0 00000000 c15bb6d0
Call Trace:
[<c010282d>] show_trace_log_lvl+0x1a/0x2f
[<c01028dd>] show_stack_log_lvl+0x9b/0xa3
[<c0102a94>] show_registers+0x1af/0x280
[<c0102c4b>] die+0xe6/0x1e5
[<c0102dd3>] do_trap+0x89/0xa2
[<c010313e>] do_invalid_op+0x88/0x92
[<c024d142>] error_code+0x6a/0x70
[<c013d631>] page_dup_rmap+0x1b/0x21
[<c01392a6>] copy_page_range+0x22b/0x2d0
[<c01109bc>] copy_process+0x964/0xf54
[<c01110d1>] do_fork+0x98/0x1b8
[<c0100716>] sys_clone+0x33/0x39
[<c010226c>] syscall_call+0x7/0xb
=======================
Code: 2a c0 ff 05 30 67 2f c0 5d c3 55 89 e5 53 89 c3 8b 42 3c 40 39 43 10 74 04 0f 0b eb fe 2b 4a 04 c1 e9 0c 03 4a 44 39 4b 14 74 04 <0f> 0b eb fe 5b 5d c3 55 89 e5 53 89 c3 8b 42 3c 85 c0 75 04 0f
EIP: [<c013cbbd>] __page_check_anon_rmap+0x21/0x28 SS:ESP 0068:c1423e98
Kernel panic - not syncing: Attempted to kill init!
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1
2007-06-06 12:43 ` 2.6.22-rc4-mm1 Cedric Le Goater
@ 2007-06-06 15:18 ` Michal Piotrowski
2007-06-06 16:01 ` 2.6.22-rc4-mm1 Cedric Le Goater
0 siblings, 1 reply; 120+ messages in thread
From: Michal Piotrowski @ 2007-06-06 15:18 UTC (permalink / raw)
To: Cedric Le Goater; +Cc: Andrew Morton, linux-kernel, Nick Piggin
Cedric Le Goater pisze:
> Hi Andrew,
>
> When CONFIG_DEBUG_VM=y, boot on i386 and s390 (the only one tested) ends
> with the following.
>
> C.
>
> ------------[ cut here ]------------
> kernel BUG at mm/rmap.c:557!
> invalid opcode: 0000 [#1]
> CPU: 0
> EIP: 0060:[<c013cbbd>] Not tainted VLI
> EFLAGS: 00000206 (2.6.22-rc4-mm1 #1)
> EIP is at __page_check_anon_rmap+0x21/0x28
> eax: c15bd431 ebx: c1024700 ecx: 000bffa6 edx: c15bb6d0
> esi: c1024700 edi: 01238045 ebp: c1423e9c esp: c1423e98
> ds: 007b es: 007b fs: 0000 gs: 0033 ss: 0068
> Process init (pid: 1, ti=c1422000 task=c14216b0 task.ti=c1422000)
> Stack: c1024700 c1423ea8 c013d631 01238045 c1423ef8 c01392a6 c15bb6d0 c15afc40
> c15afa40 c15aebfc c15c3bfc bffa7000 bffa6000 bffa7000 c15bae98 c15d5e98
> 00000000 c15afa90 c15afc90 00000000 00000002 c15d66f0 00000000 c15bb6d0
> Call Trace:
> [<c010282d>] show_trace_log_lvl+0x1a/0x2f
> [<c01028dd>] show_stack_log_lvl+0x9b/0xa3
> [<c0102a94>] show_registers+0x1af/0x280
> [<c0102c4b>] die+0xe6/0x1e5
> [<c0102dd3>] do_trap+0x89/0xa2
> [<c010313e>] do_invalid_op+0x88/0x92
> [<c024d142>] error_code+0x6a/0x70
> [<c013d631>] page_dup_rmap+0x1b/0x21
> [<c01392a6>] copy_page_range+0x22b/0x2d0
> [<c01109bc>] copy_process+0x964/0xf54
> [<c01110d1>] do_fork+0x98/0x1b8
> [<c0100716>] sys_clone+0x33/0x39
> [<c010226c>] syscall_call+0x7/0xb
> =======================
> Code: 2a c0 ff 05 30 67 2f c0 5d c3 55 89 e5 53 89 c3 8b 42 3c 40 39 43 10 74 04 0f 0b eb fe 2b 4a 04 c1 e9 0c 03 4a 44 39 4b 14 74 04 <0f> 0b eb fe 5b 5d c3 55 89 e5 53 89 c3 8b 42 3c 85 c0 75 04 0f
> EIP: [<c013cbbd>] __page_check_anon_rmap+0x21/0x28 SS:ESP 0068:c1423e98
> Kernel panic - not syncing: Attempted to kill init!
> -
Same problem here
http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/console.log
http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/mm-config2
l *__page_check_anon_rmap+0x49
0xc1075ee5 is in __page_check_anon_rmap (mm/rmap.c:557).
552 * over the call to page_add_new_anon_rmap.
553 */
554 struct anon_vma *anon_vma = vma->anon_vma;
555 anon_vma = (void *) anon_vma + PAGE_MAPPING_ANON;
556 BUG_ON(page->mapping != (struct address_space *)anon_vma);
557 BUG_ON(page->index != linear_page_index(vma, address));
558 #endif
559 }
560
561 /**
I'll try to revert mm-merge-populate-and-nopage-into-fault-fixes-nonlinear.patch
Regards,
Michal
--
"Najbardziej brakowało mi twojego milczenia."
-- Andrzej Sapkowski "Coś więcej"
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 15:18 ` 2.6.22-rc4-mm1 Michal Piotrowski
@ 2007-06-06 16:01 ` Cedric Le Goater
2007-06-06 16:26 ` 2.6.22-rc4-mm1 Mel Gorman
0 siblings, 1 reply; 120+ messages in thread
From: Cedric Le Goater @ 2007-06-06 16:01 UTC (permalink / raw)
To: Michal Piotrowski; +Cc: Andrew Morton, linux-kernel, Nick Piggin
> Same problem here
>
> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/console.log
>
> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/mm-config2
>
>
> l *__page_check_anon_rmap+0x49
> 0xc1075ee5 is in __page_check_anon_rmap (mm/rmap.c:557).
> 552 * over the call to page_add_new_anon_rmap.
> 553 */
> 554 struct anon_vma *anon_vma = vma->anon_vma;
> 555 anon_vma = (void *) anon_vma + PAGE_MAPPING_ANON;
> 556 BUG_ON(page->mapping != (struct address_space *)anon_vma);
> 557 BUG_ON(page->index != linear_page_index(vma, address));
> 558 #endif
> 559 }
> 560
> 561 /**
>
> I'll try to revert
> mm-merge-populate-and-nopage-into-fault-fixes-nonlinear.patch
yes, i gave it a try that but it seems that this patch is heavily
interlaced with others. I assume Nick has a better understanding
of the issue.
C.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 16:01 ` 2.6.22-rc4-mm1 Cedric Le Goater
@ 2007-06-06 16:26 ` Mel Gorman
2007-06-06 16:35 ` 2.6.22-rc4-mm1 William Lee Irwin III
0 siblings, 1 reply; 120+ messages in thread
From: Mel Gorman @ 2007-06-06 16:26 UTC (permalink / raw)
To: Cedric Le Goater
Cc: Michal Piotrowski, Andrew Morton, linux-kernel, Nick Piggin, aaw,
a.p.zijlstra
On (06/06/07 18:01), Cedric Le Goater didst pronounce:
> > Same problem here
> >
> > http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/console.log
> >
> > http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/mm-config2
> >
> >
> > l *__page_check_anon_rmap+0x49
> > 0xc1075ee5 is in __page_check_anon_rmap (mm/rmap.c:557).
> > 552 * over the call to page_add_new_anon_rmap.
> > 553 */
> > 554 struct anon_vma *anon_vma = vma->anon_vma;
> > 555 anon_vma = (void *) anon_vma + PAGE_MAPPING_ANON;
> > 556 BUG_ON(page->mapping != (struct address_space *)anon_vma);
> > 557 BUG_ON(page->index != linear_page_index(vma, address));
> > 558 #endif
> > 559 }
> > 560
> > 561 /**
> >
> > I'll try to revert
> > mm-merge-populate-and-nopage-into-fault-fixes-nonlinear.patch
>
> yes, i gave it a try that but it seems that this patch is heavily
> interlaced with others. I assume Nick has a better understanding
> of the issue.
>
I do not believe this is Nick's problem. I encountered the same issue and
the bisect ended up here;
# BISECT HERE
mm-variable-length-argument-support.patch
mm-variable-length-argument-support-fix.patch
# BISECT BAD
Reverting those two patches boots ok on my standalone x86 laptop. Patch authors
cc'd. I have not read the patches yet to see what might be the problem.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 16:26 ` 2.6.22-rc4-mm1 Mel Gorman
@ 2007-06-06 16:35 ` William Lee Irwin III
2007-06-06 16:47 ` 2.6.22-rc4-mm1 Mel Gorman
2007-06-06 17:06 ` 2.6.22-rc4-mm1 Peter Zijlstra
0 siblings, 2 replies; 120+ messages in thread
From: William Lee Irwin III @ 2007-06-06 16:35 UTC (permalink / raw)
To: Mel Gorman
Cc: Cedric Le Goater, Michal Piotrowski, Andrew Morton, linux-kernel,
Nick Piggin, aaw, a.p.zijlstra
On Wed, Jun 06, 2007 at 05:26:49PM +0100, Mel Gorman wrote:
> I do not believe this is Nick's problem. I encountered the same issue and
> the bisect ended up here;
> # BISECT HERE
> mm-variable-length-argument-support.patch
> mm-variable-length-argument-support-fix.patch
> # BISECT BAD
> Reverting those two patches boots ok on my standalone x86 laptop.
> Patch authors cc'd. I have not read the patches yet to see what might
> be the problem.
I found this a while ago and peterz already has a tentative fix for it at
http://programming.kicks-ass.net/kernel-patches/max_arg_pages/move_anon_vma.patch
I'm sure he himself will chime in with more/better code when he returns.
-- wli
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 16:35 ` 2.6.22-rc4-mm1 William Lee Irwin III
@ 2007-06-06 16:47 ` Mel Gorman
2007-06-06 16:53 ` 2.6.22-rc4-mm1 Cedric Le Goater
2007-06-06 17:06 ` 2.6.22-rc4-mm1 Peter Zijlstra
1 sibling, 1 reply; 120+ messages in thread
From: Mel Gorman @ 2007-06-06 16:47 UTC (permalink / raw)
To: William Lee Irwin III
Cc: Cedric Le Goater, Michal Piotrowski, Andrew Morton, linux-kernel,
Nick Piggin, aaw, a.p.zijlstra
On (06/06/07 09:35), William Lee Irwin III didst pronounce:
> On Wed, Jun 06, 2007 at 05:26:49PM +0100, Mel Gorman wrote:
> > I do not believe this is Nick's problem. I encountered the same issue and
> > the bisect ended up here;
> > # BISECT HERE
> > mm-variable-length-argument-support.patch
> > mm-variable-length-argument-support-fix.patch
> > # BISECT BAD
> > Reverting those two patches boots ok on my standalone x86 laptop.
> > Patch authors cc'd. I have not read the patches yet to see what might
> > be the problem.
>
> I found this a while ago and peterz already has a tentative fix for it at
> http://programming.kicks-ass.net/kernel-patches/max_arg_pages/move_anon_vma.patch
> I'm sure he himself will chime in with more/better code when he returns.
>
This patch also boots successfully on the machine.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 16:47 ` 2.6.22-rc4-mm1 Mel Gorman
@ 2007-06-06 16:53 ` Cedric Le Goater
2007-06-06 17:20 ` 2.6.22-rc4-mm1 Andrew Morton
0 siblings, 1 reply; 120+ messages in thread
From: Cedric Le Goater @ 2007-06-06 16:53 UTC (permalink / raw)
To: Mel Gorman
Cc: William Lee Irwin III, Michal Piotrowski, Andrew Morton,
linux-kernel, Nick Piggin, aaw, a.p.zijlstra
Mel Gorman wrote:
> On (06/06/07 09:35), William Lee Irwin III didst pronounce:
>> On Wed, Jun 06, 2007 at 05:26:49PM +0100, Mel Gorman wrote:
>>> I do not believe this is Nick's problem. I encountered the same issue and
>>> the bisect ended up here;
>>> # BISECT HERE
>>> mm-variable-length-argument-support.patch
>>> mm-variable-length-argument-support-fix.patch
>>> # BISECT BAD
>>> Reverting those two patches boots ok on my standalone x86 laptop.
>>> Patch authors cc'd. I have not read the patches yet to see what might
>>> be the problem.
>> I found this a while ago and peterz already has a tentative fix for it at
>> http://programming.kicks-ass.net/kernel-patches/max_arg_pages/move_anon_vma.patch
>> I'm sure he himself will chime in with more/better code when he returns.
>>
>
> This patch also boots successfully on the machine.
Same for me.
thanks,
C.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 16:53 ` 2.6.22-rc4-mm1 Cedric Le Goater
@ 2007-06-06 17:20 ` Andrew Morton
0 siblings, 0 replies; 120+ messages in thread
From: Andrew Morton @ 2007-06-06 17:20 UTC (permalink / raw)
To: Cedric Le Goater
Cc: Mel Gorman, William Lee Irwin III, Michal Piotrowski,
linux-kernel, Nick Piggin, aaw, a.p.zijlstra
On Wed, 06 Jun 2007 18:53:12 +0200 Cedric Le Goater <clg@fr.ibm.com> wrote:
> Mel Gorman wrote:
> > On (06/06/07 09:35), William Lee Irwin III didst pronounce:
> >> On Wed, Jun 06, 2007 at 05:26:49PM +0100, Mel Gorman wrote:
> >>> I do not believe this is Nick's problem. I encountered the same issue and
> >>> the bisect ended up here;
> >>> # BISECT HERE
> >>> mm-variable-length-argument-support.patch
> >>> mm-variable-length-argument-support-fix.patch
> >>> # BISECT BAD
> >>> Reverting those two patches boots ok on my standalone x86 laptop.
> >>> Patch authors cc'd. I have not read the patches yet to see what might
> >>> be the problem.
> >> I found this a while ago and peterz already has a tentative fix for it at
> >> http://programming.kicks-ass.net/kernel-patches/max_arg_pages/move_anon_vma.patch
> >> I'm sure he himself will chime in with more/better code when he returns.
> >>
> >
> > This patch also boots successfully on the machine.
>
> Same for me.
>
blah. I dropped the whole lot. Am shedding patches like leaves in autumn
at present. Expect -mm2 RSN.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 16:35 ` 2.6.22-rc4-mm1 William Lee Irwin III
2007-06-06 16:47 ` 2.6.22-rc4-mm1 Mel Gorman
@ 2007-06-06 17:06 ` Peter Zijlstra
2007-06-06 19:27 ` 2.6.22-rc4-mm1 Peter Zijlstra
1 sibling, 1 reply; 120+ messages in thread
From: Peter Zijlstra @ 2007-06-06 17:06 UTC (permalink / raw)
To: William Lee Irwin III
Cc: Mel Gorman, Cedric Le Goater, Michal Piotrowski, Andrew Morton,
linux-kernel, Nick Piggin, aaw
On Wed, 2007-06-06 at 09:35 -0700, William Lee Irwin III wrote:
> On Wed, Jun 06, 2007 at 05:26:49PM +0100, Mel Gorman wrote:
> > I do not believe this is Nick's problem. I encountered the same issue and
> > the bisect ended up here;
> > # BISECT HERE
> > mm-variable-length-argument-support.patch
> > mm-variable-length-argument-support-fix.patch
> > # BISECT BAD
> > Reverting those two patches boots ok on my standalone x86 laptop.
> > Patch authors cc'd. I have not read the patches yet to see what might
> > be the problem.
>
> I found this a while ago and peterz already has a tentative fix for it at
> http://programming.kicks-ass.net/kernel-patches/max_arg_pages/move_anon_vma.patch
> I'm sure he himself will chime in with more/better code when he returns.
Ah, yes indeed. We were discussing wether it would be better to update
page->index (as this patch does) or not change vma->vm_pgoff. Bill
argued that the latter would be safe, it would just limit the merge
capabilities of the anon vma (and the stack rarely, if ever, merges
anyway).
I myself an not quite sure on the effects of ->vm_pgoff of anon vmas
yet.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 17:06 ` 2.6.22-rc4-mm1 Peter Zijlstra
@ 2007-06-06 19:27 ` Peter Zijlstra
0 siblings, 0 replies; 120+ messages in thread
From: Peter Zijlstra @ 2007-06-06 19:27 UTC (permalink / raw)
To: William Lee Irwin III
Cc: Mel Gorman, Cedric Le Goater, Michal Piotrowski, Andrew Morton,
linux-kernel, Nick Piggin, aaw
On Wed, 2007-06-06 at 19:06 +0200, Peter Zijlstra wrote:
> On Wed, 2007-06-06 at 09:35 -0700, William Lee Irwin III wrote:
> > On Wed, Jun 06, 2007 at 05:26:49PM +0100, Mel Gorman wrote:
> > > I do not believe this is Nick's problem. I encountered the same issue and
> > > the bisect ended up here;
> > > # BISECT HERE
> > > mm-variable-length-argument-support.patch
> > > mm-variable-length-argument-support-fix.patch
> > > # BISECT BAD
> > > Reverting those two patches boots ok on my standalone x86 laptop.
> > > Patch authors cc'd. I have not read the patches yet to see what might
> > > be the problem.
> >
> > I found this a while ago and peterz already has a tentative fix for it at
> > http://programming.kicks-ass.net/kernel-patches/max_arg_pages/move_anon_vma.patch
> > I'm sure he himself will chime in with more/better code when he returns.
>
> Ah, yes indeed. We were discussing wether it would be better to update
> page->index (as this patch does) or not change vma->vm_pgoff. Bill
> argued that the latter would be safe, it would just limit the merge
> capabilities of the anon vma (and the stack rarely, if ever, merges
> anyway).
>
> I myself an not quite sure on the effects of ->vm_pgoff of anon vmas
> yet.
Ok, from what I can make of it, nobody relies on the value of
vma->vm_pgoff for anon vmas as long as the following invariant is kept:
vaddr = vma->vm_start + (page->index - vma->vm_pgoff)*PAGE_SIZE
So the proper thing to do is not change vm_pgoff.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
2007-06-06 11:39 ` 2.6.22-rc4-mm1 Gabriel C
2007-06-06 12:43 ` 2.6.22-rc4-mm1 Cedric Le Goater
@ 2007-06-06 13:04 ` Jiri Slaby
2007-06-06 13:06 ` 2.6.22-rc4-mm1 Cedric Le Goater
` (12 subsequent siblings)
15 siblings, 0 replies; 120+ messages in thread
From: Jiri Slaby @ 2007-06-06 13:04 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, Mikael Pettersson, Tejun Heo
Andrew Morton napsal(a):
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
It freezes during bootup while searching for sata drives on sata_promise. There
were 2 issues with sata_promise in -rc4 IIRC, one was fixed, the latter remains
unresolved. Or, should be this solved too, Mikael, Tejun and is this yet
eanother problem? (In this case I'll post dmesg and co.)
thanks,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
` (2 preceding siblings ...)
2007-06-06 13:04 ` 2.6.22-rc4-mm1 Jiri Slaby
@ 2007-06-06 13:06 ` Cedric Le Goater
2007-06-06 13:48 ` 2.6.22-rc4-mm1 Andy Whitcroft
2007-06-06 13:49 ` 2.6.22-rc4-mm1 -- ia64 build failure Andy Whitcroft
` (11 subsequent siblings)
15 siblings, 1 reply; 120+ messages in thread
From: Cedric Le Goater @ 2007-06-06 13:06 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Andrew,
here's a minor fix for x86_64,
C.
when CONFIG_PM=y and CONFIG_SOFTWARE_SUSPEND=n,
CC arch/x86_64/kernel/e820.o
/home/legoater/linux/2.6.22-rc4-mm1/arch/x86_64/kernel/e820.c: In function `e820_mark_nosave_regions':
/home/legoater/linux/2.6.22-rc4-mm1/arch/x86_64/kernel/e820.c:248: warning: implicit declaration of function `register_nosave_region'
Signed-off-by: Cedric Le Goater <clg@fr.ibm.com>
---
include/linux/suspend.h | 8 ++++++++
1 file changed, 8 insertions(+)
Index: 2.6.22-rc4-mm1/include/linux/suspend.h
===================================================================
--- 2.6.22-rc4-mm1.orig/include/linux/suspend.h
+++ 2.6.22-rc4-mm1/include/linux/suspend.h
@@ -74,6 +74,14 @@
extern void hibernation_set_ops(struct hibernation_ops *ops);
extern int hibernate(void);
#else /* CONFIG_SOFTWARE_SUSPEND */
+static inline void register_nosave_region(unsigned long b, unsigned long e)
+{
+}
+
+static inline void register_nosave_region_late(unsigned long b, unsigned long e)
+{
+}
+
static inline int swsusp_page_is_forbidden(struct page *p) { return 0; }
static inline void swsusp_set_page_free(struct page *p) {}
static inline void swsusp_unset_page_free(struct page *p) {}
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1
2007-06-06 13:06 ` 2.6.22-rc4-mm1 Cedric Le Goater
@ 2007-06-06 13:48 ` Andy Whitcroft
2007-06-06 17:23 ` 2.6.22-rc4-mm1 Andrew Morton
0 siblings, 1 reply; 120+ messages in thread
From: Andy Whitcroft @ 2007-06-06 13:48 UTC (permalink / raw)
To: Cedric Le Goater; +Cc: Andrew Morton, linux-kernel
Cedric Le Goater wrote:
> Andrew,
>
> here's a minor fix for x86_64,
>
> C.
>
>
> when CONFIG_PM=y and CONFIG_SOFTWARE_SUSPEND=n,
>
> CC arch/x86_64/kernel/e820.o
> /home/legoater/linux/2.6.22-rc4-mm1/arch/x86_64/kernel/e820.c: In function `e820_mark_nosave_regions':
> /home/legoater/linux/2.6.22-rc4-mm1/arch/x86_64/kernel/e820.c:248: warning: implicit declaration of function `register_nosave_region'
>
> Signed-off-by: Cedric Le Goater <clg@fr.ibm.com>
> ---
> include/linux/suspend.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> Index: 2.6.22-rc4-mm1/include/linux/suspend.h
> ===================================================================
> --- 2.6.22-rc4-mm1.orig/include/linux/suspend.h
> +++ 2.6.22-rc4-mm1/include/linux/suspend.h
> @@ -74,6 +74,14 @@
> extern void hibernation_set_ops(struct hibernation_ops *ops);
> extern int hibernate(void);
> #else /* CONFIG_SOFTWARE_SUSPEND */
> +static inline void register_nosave_region(unsigned long b, unsigned long e)
> +{
> +}
> +
> +static inline void register_nosave_region_late(unsigned long b, unsigned long e)
> +{
> +}
> +
> static inline int swsusp_page_is_forbidden(struct page *p) { return 0; }
> static inline void swsusp_set_page_free(struct page *p) {}
> static inline void swsusp_unset_page_free(struct page *p) {}
> -
Looks like this is the cause of a bunch of compile failures across our
testing. Will shove this through tko.
-apw
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1
2007-06-06 13:48 ` 2.6.22-rc4-mm1 Andy Whitcroft
@ 2007-06-06 17:23 ` Andrew Morton
0 siblings, 0 replies; 120+ messages in thread
From: Andrew Morton @ 2007-06-06 17:23 UTC (permalink / raw)
To: Andy Whitcroft; +Cc: Cedric Le Goater, linux-kernel
On Wed, 06 Jun 2007 14:48:52 +0100 Andy Whitcroft <apw@shadowen.org> wrote:
> Cedric Le Goater wrote:
> > Andrew,
> >
> > here's a minor fix for x86_64,
> >
> > C.
> >
> >
> > when CONFIG_PM=y and CONFIG_SOFTWARE_SUSPEND=n,
> >
> > CC arch/x86_64/kernel/e820.o
> > /home/legoater/linux/2.6.22-rc4-mm1/arch/x86_64/kernel/e820.c: In function `e820_mark_nosave_regions':
> > /home/legoater/linux/2.6.22-rc4-mm1/arch/x86_64/kernel/e820.c:248: warning: implicit declaration of function `register_nosave_region'
> >
> > Signed-off-by: Cedric Le Goater <clg@fr.ibm.com>
> > ---
> > include/linux/suspend.h | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > Index: 2.6.22-rc4-mm1/include/linux/suspend.h
> > ===================================================================
> > --- 2.6.22-rc4-mm1.orig/include/linux/suspend.h
> > +++ 2.6.22-rc4-mm1/include/linux/suspend.h
> > @@ -74,6 +74,14 @@
> > extern void hibernation_set_ops(struct hibernation_ops *ops);
> > extern int hibernate(void);
> > #else /* CONFIG_SOFTWARE_SUSPEND */
> > +static inline void register_nosave_region(unsigned long b, unsigned long e)
> > +{
> > +}
> > +
> > +static inline void register_nosave_region_late(unsigned long b, unsigned long e)
> > +{
> > +}
> > +
> > static inline int swsusp_page_is_forbidden(struct page *p) { return 0; }
> > static inline void swsusp_set_page_free(struct page *p) {}
> > static inline void swsusp_unset_page_free(struct page *p) {}
> > -
>
>
> Looks like this is the cause of a bunch of compile failures across our
> testing. Will shove this through tko.
>
Yeah. I put a different fix into the hot-fixes directory, thanks.
The powerpc failure is nasty - probably a toolchain stupidity. I reverted
slub-use-ilog2-instead-of-series-of-constant-comparisons.patch which
_should_ fix it, but really the problem is triggered by ilog2().
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1 -- ia64 build failure
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
` (3 preceding siblings ...)
2007-06-06 13:06 ` 2.6.22-rc4-mm1 Cedric Le Goater
@ 2007-06-06 13:49 ` Andy Whitcroft
2007-06-06 17:43 ` Andrew Morton
2007-06-06 14:00 ` 2.6.22-rc4-mm1 -- x86_64 ACPI panic Andy Whitcroft
` (10 subsequent siblings)
15 siblings, 1 reply; 120+ messages in thread
From: Andy Whitcroft @ 2007-06-06 13:49 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Seeing this on an ia64:
drivers/built-in.o: In function `efi_setup_pcdp_console':
(.init.text+0x13be2): undefined reference to `early_serial_console_init'
drivers/built-in.o: In function `efi_setup_pcdp_console':
(.init.text+0x13de2): undefined reference to `early_serial_console_init'
make: *** [.tmp_vmlinux1] Error 1
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1 -- ia64 build failure
2007-06-06 13:49 ` 2.6.22-rc4-mm1 -- ia64 build failure Andy Whitcroft
@ 2007-06-06 17:43 ` Andrew Morton
2007-06-06 18:11 ` Yinghai Lu
0 siblings, 1 reply; 120+ messages in thread
From: Andrew Morton @ 2007-06-06 17:43 UTC (permalink / raw)
To: Andy Whitcroft; +Cc: linux-kernel, Yinghai Lu
On Wed, 06 Jun 2007 14:49:25 +0100 Andy Whitcroft <apw@shadowen.org> wrote:
> Seeing this on an ia64:
>
> drivers/built-in.o: In function `efi_setup_pcdp_console':
> (.init.text+0x13be2): undefined reference to `early_serial_console_init'
> drivers/built-in.o: In function `efi_setup_pcdp_console':
> (.init.text+0x13de2): undefined reference to `early_serial_console_init'
> make: *** [.tmp_vmlinux1] Error 1
We really exceeded ourselves this time. .config, please?
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1 -- ia64 build failure
2007-06-06 17:43 ` Andrew Morton
@ 2007-06-06 18:11 ` Yinghai Lu
0 siblings, 0 replies; 120+ messages in thread
From: Yinghai Lu @ 2007-06-06 18:11 UTC (permalink / raw)
To: Andrew Morton; +Cc: Andy Whitcroft, linux-kernel
Andrew Morton wrote:
> On Wed, 06 Jun 2007 14:49:25 +0100 Andy Whitcroft <apw@shadowen.org> wrote:
>
>> Seeing this on an ia64:
>>
>> drivers/built-in.o: In function `efi_setup_pcdp_console':
>> (.init.text+0x13be2): undefined reference to `early_serial_console_init'
>> drivers/built-in.o: In function `efi_setup_pcdp_console':
>> (.init.text+0x13de2): undefined reference to `early_serial_console_init'
>> make: *** [.tmp_vmlinux1] Error 1
>
> We really exceeded ourselves this time. .config, please?
Oh, i miss that file. will submit the patch.
YH
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
` (4 preceding siblings ...)
2007-06-06 13:49 ` 2.6.22-rc4-mm1 -- ia64 build failure Andy Whitcroft
@ 2007-06-06 14:00 ` Andy Whitcroft
2007-06-06 17:52 ` Andrew Morton
[not found] ` <6bffcb0e0706060356y3628e26m49fdce4d6fb8cac9@mail.gmail.com>
` (9 subsequent siblings)
15 siblings, 1 reply; 120+ messages in thread
From: Andy Whitcroft @ 2007-06-06 14:00 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Getting this on a bigger x86_64 (bl6-13):
Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
[<ffffffff8037898b>] acpi_processor_throttling_seq_show+0xa7/0xd6
PGD 2d77067 PUD 34c3067 PMD 0
Oops: 0000 [1] SMP
CPU 3
Modules linked in: video output button battery asus_acpi ac lp
parport_pc parport floppy nvram amd_rng rng_core i2c_amd756 i2c_core
Pid: 1634, comm: head Not tainted 2.6.22-rc4-mm1-autokern1 #1
RIP: 0010:[<ffffffff8037898b>] [<ffffffff8037898b>]
acpi_processor_throttling_seq_show+0xa7/0xd6
RSP: 0018:ffff810003c9de48 EFLAGS: 00010246
RAX: 0000000000000020 RBX: ffff8100029e7800 RCX: 0000000000000000
RDX: 000000000000002a RSI: ffffffff805993e4 RDI: ffff810002d714c0
RBP: ffff810002d714c0 R08: ffff810003f82051 R09: ffff810002d714c0
R10: ffffffffffffffff R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 00007fff64fd2b90
FS: 00002b3545aec6f0(0000) GS:ffff810001683a40(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 0000000003966000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process head (pid: 1634, threadinfo ffff810003c9c000, task ffff810001c8c810)
Stack: 00000000000000d0 ffff810002d714c0 0000000000000001 0000000000000001
0000000000002000 ffffffff802ab6eb ffff810003c9df50 ffff810002915d00
ffff810002d714f0 ffff810002fa2000 0000000000000000 fffffffffffffffb
Call Trace:
[<ffffffff802ab6eb>] seq_read+0x105/0x28e
[<ffffffff802ab5e6>] seq_read+0x0/0x28e
[<ffffffff802cd085>] proc_reg_read+0x80/0x9a
[<ffffffff802925a7>] vfs_read+0xcb/0x153
[<ffffffff80292943>] sys_read+0x45/0x6e
[<ffffffff8020bc5e>] system_call+0x7e/0x83
Code: 45 8b 44 0d 00 44 89 e1 0f 45 d0 31 c0 49 ff c4 49 83 c5 28
RIP [<ffffffff8037898b>] acpi_processor_throttling_seq_show+0xa7/0xd6
RSP <ffff810003c9de48>
CR2: 0000000000000000
FATAL: Error inserting acpi_cpufreq
(/lib/modules/2.6.22-rc4-mm1-autokern1/kernel/arch/x86_64/kernel/cpufreq/acpi-cpufreq.ko):
No such device
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
2007-06-06 14:00 ` 2.6.22-rc4-mm1 -- x86_64 ACPI panic Andy Whitcroft
@ 2007-06-06 17:52 ` Andrew Morton
2007-06-08 9:15 ` Luming Yu
0 siblings, 1 reply; 120+ messages in thread
From: Andrew Morton @ 2007-06-06 17:52 UTC (permalink / raw)
To: Andy Whitcroft
Cc: linux-kernel, Len Brown, Yu, Luming, Alexey Starikovskiy,
linux-acpi
On Wed, 06 Jun 2007 15:00:17 +0100 Andy Whitcroft <apw@shadowen.org> wrote:
> Getting this on a bigger x86_64 (bl6-13):
>
> Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
> [<ffffffff8037898b>] acpi_processor_throttling_seq_show+0xa7/0xd6
> PGD 2d77067 PUD 34c3067 PMD 0
> Oops: 0000 [1] SMP
> CPU 3
> Modules linked in: video output button battery asus_acpi ac lp
> parport_pc parport floppy nvram amd_rng rng_core i2c_amd756 i2c_core
> Pid: 1634, comm: head Not tainted 2.6.22-rc4-mm1-autokern1 #1
> RIP: 0010:[<ffffffff8037898b>] [<ffffffff8037898b>]
> acpi_processor_throttling_seq_show+0xa7/0xd6
> RSP: 0018:ffff810003c9de48 EFLAGS: 00010246
> RAX: 0000000000000020 RBX: ffff8100029e7800 RCX: 0000000000000000
> RDX: 000000000000002a RSI: ffffffff805993e4 RDI: ffff810002d714c0
> RBP: ffff810002d714c0 R08: ffff810003f82051 R09: ffff810002d714c0
> R10: ffffffffffffffff R11: 0000000000000000 R12: 0000000000000000
> R13: 0000000000000000 R14: 0000000000000000 R15: 00007fff64fd2b90
> FS: 00002b3545aec6f0(0000) GS:ffff810001683a40(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 0000000000000000 CR3: 0000000003966000 CR4: 00000000000006e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process head (pid: 1634, threadinfo ffff810003c9c000, task ffff810001c8c810)
> Stack: 00000000000000d0 ffff810002d714c0 0000000000000001 0000000000000001
> 0000000000002000 ffffffff802ab6eb ffff810003c9df50 ffff810002915d00
> ffff810002d714f0 ffff810002fa2000 0000000000000000 fffffffffffffffb
> Call Trace:
> [<ffffffff802ab6eb>] seq_read+0x105/0x28e
> [<ffffffff802ab5e6>] seq_read+0x0/0x28e
> [<ffffffff802cd085>] proc_reg_read+0x80/0x9a
> [<ffffffff802925a7>] vfs_read+0xcb/0x153
> [<ffffffff80292943>] sys_read+0x45/0x6e
> [<ffffffff8020bc5e>] system_call+0x7e/0x83
>
>
> Code: 45 8b 44 0d 00 44 89 e1 0f 45 d0 31 c0 49 ff c4 49 83 c5 28
> RIP [<ffffffff8037898b>] acpi_processor_throttling_seq_show+0xa7/0xd6
> RSP <ffff810003c9de48>
> CR2: 0000000000000000
> FATAL: Error inserting acpi_cpufreq
> (/lib/modules/2.6.22-rc4-mm1-autokern1/kernel/arch/x86_64/kernel/cpufreq/acpi-cpufreq.ko):
> No such device
Was the oops at modprobe time? If so, it seems weird that
acpi_processor_throttling_seq_show() would be getting run at that stage.
(The oops trace is supposed to show the oopsing process's
task_struct.comm[], but it isn't shown here?)
Anyway, there are extensive changes in there added by git-acpi.patch. I
suppose we can try to limp along with the below, but it'll probably just
oops later on.
--- a/drivers/acpi/processor_throttling.c~git-acpi-disable-acpi_processor_throttling_seq_show
+++ a/drivers/acpi/processor_throttling.c
@@ -648,6 +648,9 @@ static int acpi_processor_throttling_seq
goto end;
}
+ seq_puts(seq, "acpi_processor_throttling_seq_show() is busted\n");
+ goto end;
+
seq_printf(seq, "state count: %d\n"
"active state: T%d\n"
"state available: T%d to T%d\n",
_
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
2007-06-06 17:52 ` Andrew Morton
@ 2007-06-08 9:15 ` Luming Yu
2007-06-08 18:12 ` Andrew Morton
0 siblings, 1 reply; 120+ messages in thread
From: Luming Yu @ 2007-06-08 9:15 UTC (permalink / raw)
To: Andrew Morton
Cc: Andy Whitcroft, linux-kernel, Len Brown, Yu, Luming,
Alexey Starikovskiy, linux-acpi
The only problem known as to the acpi throttling changes in the mm tree
is a typo ,and the patch to fix it is available here. Please test and
get results back to me. BTW,the log shows that the acpi-cpufreq.ko has
problem. Would please also try not to load acpi-cpufreq.
http://www.ussg.iu.edu/hypermail/linux/kernel/0706.0/2509.html
On 6/7/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Wed, 06 Jun 2007 15:00:17 +0100 Andy Whitcroft <apw@shadowen.org> wrote:
>
> > Getting this on a bigger x86_64 (bl6-13):
> >
> > Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
> > [<ffffffff8037898b>] acpi_processor_throttling_seq_show+0xa7/0xd6
> > PGD 2d77067 PUD 34c3067 PMD 0
> > Oops: 0000 [1] SMP
> > CPU 3
> > Modules linked in: video output button battery asus_acpi ac lp
> > parport_pc parport floppy nvram amd_rng rng_core i2c_amd756 i2c_core
> > Pid: 1634, comm: head Not tainted 2.6.22-rc4-mm1-autokern1 #1
> > RIP: 0010:[<ffffffff8037898b>] [<ffffffff8037898b>]
> > acpi_processor_throttling_seq_show+0xa7/0xd6
> > RSP: 0018:ffff810003c9de48 EFLAGS: 00010246
> > RAX: 0000000000000020 RBX: ffff8100029e7800 RCX: 0000000000000000
> > RDX: 000000000000002a RSI: ffffffff805993e4 RDI: ffff810002d714c0
> > RBP: ffff810002d714c0 R08: ffff810003f82051 R09: ffff810002d714c0
> > R10: ffffffffffffffff R11: 0000000000000000 R12: 0000000000000000
> > R13: 0000000000000000 R14: 0000000000000000 R15: 00007fff64fd2b90
> > FS: 00002b3545aec6f0(0000) GS:ffff810001683a40(0000) knlGS:0000000000000000
> > CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> > CR2: 0000000000000000 CR3: 0000000003966000 CR4: 00000000000006e0
> > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> > Process head (pid: 1634, threadinfo ffff810003c9c000, task ffff810001c8c810)
> > Stack: 00000000000000d0 ffff810002d714c0 0000000000000001 0000000000000001
> > 0000000000002000 ffffffff802ab6eb ffff810003c9df50 ffff810002915d00
> > ffff810002d714f0 ffff810002fa2000 0000000000000000 fffffffffffffffb
> > Call Trace:
> > [<ffffffff802ab6eb>] seq_read+0x105/0x28e
> > [<ffffffff802ab5e6>] seq_read+0x0/0x28e
> > [<ffffffff802cd085>] proc_reg_read+0x80/0x9a
> > [<ffffffff802925a7>] vfs_read+0xcb/0x153
> > [<ffffffff80292943>] sys_read+0x45/0x6e
> > [<ffffffff8020bc5e>] system_call+0x7e/0x83
> >
> >
> > Code: 45 8b 44 0d 00 44 89 e1 0f 45 d0 31 c0 49 ff c4 49 83 c5 28
> > RIP [<ffffffff8037898b>] acpi_processor_throttling_seq_show+0xa7/0xd6
> > RSP <ffff810003c9de48>
> > CR2: 0000000000000000
> > FATAL: Error inserting acpi_cpufreq
> > (/lib/modules/2.6.22-rc4-mm1-autokern1/kernel/arch/x86_64/kernel/cpufreq/acpi-cpufreq.ko):
> > No such device
>
> Was the oops at modprobe time? If so, it seems weird that
> acpi_processor_throttling_seq_show() would be getting run at that stage.
>
> (The oops trace is supposed to show the oopsing process's
> task_struct.comm[], but it isn't shown here?)
>
> Anyway, there are extensive changes in there added by git-acpi.patch. I
> suppose we can try to limp along with the below, but it'll probably just
> oops later on.
>
> --- a/drivers/acpi/processor_throttling.c~git-acpi-disable-acpi_processor_throttling_seq_show
> +++ a/drivers/acpi/processor_throttling.c
> @@ -648,6 +648,9 @@ static int acpi_processor_throttling_seq
> goto end;
> }
>
> + seq_puts(seq, "acpi_processor_throttling_seq_show() is busted\n");
> + goto end;
> +
> seq_printf(seq, "state count: %d\n"
> "active state: T%d\n"
> "state available: T%d to T%d\n",
> _
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
2007-06-08 9:15 ` Luming Yu
@ 2007-06-08 18:12 ` Andrew Morton
2007-06-26 6:00 ` Len Brown
0 siblings, 1 reply; 120+ messages in thread
From: Andrew Morton @ 2007-06-08 18:12 UTC (permalink / raw)
To: Luming Yu
Cc: Andy Whitcroft, linux-kernel, Len Brown, Yu, Luming,
Alexey Starikovskiy, linux-acpi
On Fri, 8 Jun 2007 17:15:45 +0800
"Luming Yu" <luming.yu@gmail.com> wrote:
> The only problem known as to the acpi throttling changes in the mm tree
> is a typo ,and the patch to fix it is available here. Please test and
> get results back to me. BTW,the log shows that the acpi-cpufreq.ko has
> problem. Would please also try not to load acpi-cpufreq.
>
> http://www.ussg.iu.edu/hypermail/linux/kernel/0706.0/2509.html
Sigh. Is this some sort of contest to see how many things we can
do wrong in a single patch?
- Include a changelog
- Include Signed-off-by:
- Don't use attachments
- If you _must_ use attachments, use text/plain, not application/octet-stream
- Format code to remain within 80 columns.
- Don't do "if(". Do "if ("
Oh well. Good to hear that the oops got fixed, thanks.
From: "Luming Yu" <luming.yu@gmail.com>
Cc: Len Brown <lenb@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/acpi/processor_throttling.c | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff -puN drivers/acpi/processor_throttling.c~acpi-fix-oops-in-acpi_processor_throttling_seq_show drivers/acpi/processor_throttling.c
--- a/drivers/acpi/processor_throttling.c~acpi-fix-oops-in-acpi_processor_throttling_seq_show
+++ a/drivers/acpi/processor_throttling.c
@@ -656,18 +656,20 @@ static int acpi_processor_throttling_seq
pr->throttling.state_count - 1);
seq_puts(seq, "states:\n");
- if (acpi_processor_get_throttling == acpi_processor_get_throttling_fadt)
+ if (pr->throttling.acpi_processor_get_throttling ==
+ acpi_processor_get_throttling_fadt) {
for (i = 0; i < pr->throttling.state_count; i++)
seq_printf(seq, " %cT%d: %02d%%\n",
(i == pr->throttling.state ? '*' : ' '), i,
(pr->throttling.states[i].performance ? pr->
throttling.states[i].performance / 10 : 0));
- else
+ } else {
for (i = 0; i < pr->throttling.state_count; i++)
seq_printf(seq, " %cT%d: %02d%%\n",
(i == pr->throttling.state ? '*' : ' '), i,
(int)pr->throttling.states_tss[i].
freqpercentage);
+ }
end:
return 0;
_
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1 -- x86_64 ACPI panic
2007-06-08 18:12 ` Andrew Morton
@ 2007-06-26 6:00 ` Len Brown
0 siblings, 0 replies; 120+ messages in thread
From: Len Brown @ 2007-06-26 6:00 UTC (permalink / raw)
To: Andrew Morton
Cc: Luming Yu, Andy Whitcroft, linux-kernel, Yu, Luming,
Alexey Starikovskiy, linux-acpi
Applied.
thanks,
-Len
On Friday 08 June 2007 14:12, Andrew Morton wrote:
> On Fri, 8 Jun 2007 17:15:45 +0800
> "Luming Yu" <luming.yu@gmail.com> wrote:
>
> > The only problem known as to the acpi throttling changes in the mm tree
> > is a typo ,and the patch to fix it is available here. Please test and
> > get results back to me. BTW,the log shows that the acpi-cpufreq.ko has
> > problem. Would please also try not to load acpi-cpufreq.
> >
> > http://www.ussg.iu.edu/hypermail/linux/kernel/0706.0/2509.html
>
> Sigh. Is this some sort of contest to see how many things we can
> do wrong in a single patch?
>
> - Include a changelog
>
> - Include Signed-off-by:
>
> - Don't use attachments
>
> - If you _must_ use attachments, use text/plain, not application/octet-stream
>
> - Format code to remain within 80 columns.
>
> - Don't do "if(". Do "if ("
>
> Oh well. Good to hear that the oops got fixed, thanks.
>
>
> From: "Luming Yu" <luming.yu@gmail.com>
>
> Cc: Len Brown <lenb@kernel.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/acpi/processor_throttling.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff -puN drivers/acpi/processor_throttling.c~acpi-fix-oops-in-acpi_processor_throttling_seq_show drivers/acpi/processor_throttling.c
> --- a/drivers/acpi/processor_throttling.c~acpi-fix-oops-in-acpi_processor_throttling_seq_show
> +++ a/drivers/acpi/processor_throttling.c
> @@ -656,18 +656,20 @@ static int acpi_processor_throttling_seq
> pr->throttling.state_count - 1);
>
> seq_puts(seq, "states:\n");
> - if (acpi_processor_get_throttling == acpi_processor_get_throttling_fadt)
> + if (pr->throttling.acpi_processor_get_throttling ==
> + acpi_processor_get_throttling_fadt) {
> for (i = 0; i < pr->throttling.state_count; i++)
> seq_printf(seq, " %cT%d: %02d%%\n",
> (i == pr->throttling.state ? '*' : ' '), i,
> (pr->throttling.states[i].performance ? pr->
> throttling.states[i].performance / 10 : 0));
> - else
> + } else {
> for (i = 0; i < pr->throttling.state_count; i++)
> seq_printf(seq, " %cT%d: %02d%%\n",
> (i == pr->throttling.state ? '*' : ' '), i,
> (int)pr->throttling.states_tss[i].
> freqpercentage);
> + }
>
> end:
> return 0;
> _
>
> -
> 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] 120+ messages in thread
[parent not found: <6bffcb0e0706060356y3628e26m49fdce4d6fb8cac9@mail.gmail.com>]
* Re: 2.6.22-rc4-mm1
[not found] ` <6bffcb0e0706060356y3628e26m49fdce4d6fb8cac9@mail.gmail.com>
@ 2007-06-06 14:34 ` Michal Piotrowski
2007-06-06 17:14 ` 2.6.22-rc4-mm1 Andrew Morton
0 siblings, 1 reply; 120+ messages in thread
From: Michal Piotrowski @ 2007-06-06 14:34 UTC (permalink / raw)
To: Fenghua Yu; +Cc: Andrew Morton, linux-kernel
Michal Piotrowski pisze:
> On 06/06/07, Andrew Morton <akpm@linux-foundation.org> wrote:
>>
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
>>
>>
>
> It reboots immediately.
GOOD
#preserve-the-dirty-bit-in-init_page_buffers.patch
#rd-mark-ramdisk-buffer-heads-dirty-in-ramdisk_set_page_dirty.patch
#rd-mark-ramdisk-buffer-heads-dirty-in-ramdisk_set_page_dirty-fix.patch
#rd-simplify-by-using-the-same-helper-functions-in-libfs.patch
#rd-remove-ramdisk_set_page_dirty.patch
#rd-remove-ramdisk_set_page_dirty-fix.patch
mpu401-warning-fixes.patch
define-new-percpu-interface-for-shared-data.patch
use-the-new-percpu-interface-for-shared-data.patch
introduce-config_virt_to_bus.patch
BAD
Ok, these patches broke my P4 HT
define-new-percpu-interface-for-shared-data.patch
use-the-new-percpu-interface-for-shared-data.patch
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Pentium(R) 4 CPU 2.80GHz
stepping : 5
cpu MHz : 2798.721
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr
bogomips : 5599.63
clflush size : 64
processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Pentium(R) 4 CPU 2.80GHz
stepping : 5
cpu MHz : 2798.721
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr
bogomips : 5596.56
clflush size : 64
http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/mm-config
Regards,
Michal
--
"Najbardziej brakowało mi twojego milczenia."
-- Andrzej Sapkowski "Coś więcej"
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1 - 'lvm vgscan' busticated again...
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
` (6 preceding siblings ...)
[not found] ` <6bffcb0e0706060356y3628e26m49fdce4d6fb8cac9@mail.gmail.com>
@ 2007-06-06 16:08 ` Valdis.Kletnieks
2007-06-07 6:44 ` Tejun Heo
2007-06-06 16:19 ` 2.6.22-rc4-mm1 WANG Cong
` (7 subsequent siblings)
15 siblings, 1 reply; 120+ messages in thread
From: Valdis.Kletnieks @ 2007-06-06 16:08 UTC (permalink / raw)
To: Andrew Morton, Tejun Heo, Greg Kroah-Hartman; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
On Wed, 06 Jun 2007 02:07:37 PDT, Andrew Morton said:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
This one died a horrid death at boot time - console log indicates it found the
hard drive OK, found the 2 partitions on it. But when the initrd ran a
'lvm vgscan', it didn't find the LVM2 space on /dev/sda2, so it panic'ed when
it fell off the end of the initrd because the root= wasn't there.
My first guess for blame:
gregkh-driver-sysfs-allocate-inode-number-using-ida.patch
as that's awfully similar to gregkh-driver-sysfs-fix-i_ino-handling-in-sysfs.patch
that broke 'lvm vgscan' for me in the same way on 21-rc7-mm[12].
I'll hopefully get a chance to revert that one and test later today - a quick
'patch -p1 -R --dry-run' shows a number of conflicts that will need hand-fixing
at the very least.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1 - 'lvm vgscan' busticated again...
2007-06-06 16:08 ` 2.6.22-rc4-mm1 - 'lvm vgscan' busticated again Valdis.Kletnieks
@ 2007-06-07 6:44 ` Tejun Heo
2007-06-07 20:28 ` Valdis.Kletnieks
0 siblings, 1 reply; 120+ messages in thread
From: Tejun Heo @ 2007-06-07 6:44 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: Andrew Morton, Greg Kroah-Hartman, linux-kernel
Valdis.Kletnieks@vt.edu wrote:
> On Wed, 06 Jun 2007 02:07:37 PDT, Andrew Morton said:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
>
> This one died a horrid death at boot time - console log indicates it found the
> hard drive OK, found the 2 partitions on it. But when the initrd ran a
> 'lvm vgscan', it didn't find the LVM2 space on /dev/sda2, so it panic'ed when
> it fell off the end of the initrd because the root= wasn't there.
>
> My first guess for blame:
>
> gregkh-driver-sysfs-allocate-inode-number-using-ida.patch
>
> as that's awfully similar to gregkh-driver-sysfs-fix-i_ino-handling-in-sysfs.patch
> that broke 'lvm vgscan' for me in the same way on 21-rc7-mm[12].
>
> I'll hopefully get a chance to revert that one and test later today - a quick
> 'patch -p1 -R --dry-run' shows a number of conflicts that will need hand-fixing
> at the very least.
Did rc3-mm1 work? Can you find out the first broken -mm?
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1 - 'lvm vgscan' busticated again...
2007-06-07 6:44 ` Tejun Heo
@ 2007-06-07 20:28 ` Valdis.Kletnieks
2007-06-08 6:37 ` Tejun Heo
0 siblings, 1 reply; 120+ messages in thread
From: Valdis.Kletnieks @ 2007-06-07 20:28 UTC (permalink / raw)
To: Tejun Heo; +Cc: Andrew Morton, Greg Kroah-Hartman, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
On Thu, 07 Jun 2007 15:44:56 +0900, Tejun Heo said:
> Valdis.Kletnieks@vt.edu wrote:
> > On Wed, 06 Jun 2007 02:07:37 PDT, Andrew Morton said:
> >> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2
.6.22-rc4-mm1/
> >
> > This one died a horrid death at boot time - console log indicates it found
the
> > hard drive OK, found the 2 partitions on it. But when the initrd ran a
> > 'lvm vgscan', it didn't find the LVM2 space on /dev/sda2, so it panic'ed wh
en
> > it fell off the end of the initrd because the root= wasn't there.
> >
> > My first guess for blame:
> >
> > gregkh-driver-sysfs-allocate-inode-number-using-ida.patch
> >
> > as that's awfully similar to gregkh-driver-sysfs-fix-i_ino-handling-in-sysfs.patch
> > that broke 'lvm vgscan' for me in the same way on 21-rc7-mm[12].
> >
> > I'll hopefully get a chance to revert that one and test later today - a quick
> > 'patch -p1 -R --dry-run' shows a number of conflicts that will need hand-fixing
> > at the very least.
>
> Did rc3-mm1 work? Can you find out the first broken -mm?
21-rc5-mm2 worked, -rc6-mm* were busticated for other reasons on my laptop,
21-rc7-mm[12] were broken, 21-mm1 through 21-rc3-mm1 worked, -rc4-mm1 broke,
and -rc4-mm2 works. I could bisect through -rc4-mm1 if it's deemed useful,
Andrew just pushed -mm2 before I had a chance.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1 - 'lvm vgscan' busticated again...
2007-06-07 20:28 ` Valdis.Kletnieks
@ 2007-06-08 6:37 ` Tejun Heo
0 siblings, 0 replies; 120+ messages in thread
From: Tejun Heo @ 2007-06-08 6:37 UTC (permalink / raw)
To: Valdis.Kletnieks; +Cc: Andrew Morton, Greg Kroah-Hartman, linux-kernel
Valdis.Kletnieks@vt.edu wrote:
> On Thu, 07 Jun 2007 15:44:56 +0900, Tejun Heo said:
>> Valdis.Kletnieks@vt.edu wrote:
>>> On Wed, 06 Jun 2007 02:07:37 PDT, Andrew Morton said:
>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2
> .6.22-rc4-mm1/
>>> This one died a horrid death at boot time - console log indicates it found
> the
>>> hard drive OK, found the 2 partitions on it. But when the initrd ran a
>>> 'lvm vgscan', it didn't find the LVM2 space on /dev/sda2, so it panic'ed wh
> en
>>> it fell off the end of the initrd because the root= wasn't there.
>>>
>>> My first guess for blame:
>>>
>>> gregkh-driver-sysfs-allocate-inode-number-using-ida.patch
>>>
>>> as that's awfully similar to gregkh-driver-sysfs-fix-i_ino-handling-in-sysfs.patch
>>> that broke 'lvm vgscan' for me in the same way on 21-rc7-mm[12].
>>>
>>> I'll hopefully get a chance to revert that one and test later today - a quick
>>> 'patch -p1 -R --dry-run' shows a number of conflicts that will need hand-fixing
>>> at the very least.
>> Did rc3-mm1 work? Can you find out the first broken -mm?
>
> 21-rc5-mm2 worked, -rc6-mm* were busticated for other reasons on my laptop,
> 21-rc7-mm[12] were broken, 21-mm1 through 21-rc3-mm1 worked, -rc4-mm1 broke,
> and -rc4-mm2 works. I could bisect through -rc4-mm1 if it's deemed useful,
> Andrew just pushed -mm2 before I had a chance.
Thanks. The offending patch was
gregkh-driver-block-device
Which is pulled from -mm2. Jiri Slaby reports that turning on
SYSFS_DEPRECATED fixes the problem.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
` (7 preceding siblings ...)
2007-06-06 16:08 ` 2.6.22-rc4-mm1 - 'lvm vgscan' busticated again Valdis.Kletnieks
@ 2007-06-06 16:19 ` WANG Cong
2007-06-06 18:09 ` 2.6.22-rc4-mm1 Andrew Morton
2007-06-06 16:30 ` 2.6.22-rc4-mm1 William Lee Irwin III
` (6 subsequent siblings)
15 siblings, 1 reply; 120+ messages in thread
From: WANG Cong @ 2007-06-06 16:19 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Wed, Jun 06, 2007 at 02:07:37AM -0700, Andrew Morton wrote:
>
>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
>
>- Somebody broke it on my powerpc G5, but I didn't have time to do yet
> another bisection yet.
>
It seems strange that a new C source file (mlguest.c) appears in the top dir of the
kernel source. There are some problems with it.
First, I used `make mlguest.o` to compile that file, but I got tons of warnings and errors.
(Too many to put here.) What's wrong with it? Or I didn't compile/configure it correctly?
Second, mlguest.c #includes a head file named "../../include/linux/lguest_launcher.h".
Since mlguest.c is in the top dir, so where is ../../include/linux/lguest_launcher.h?
Regards!
WANG Cong
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1
2007-06-06 16:19 ` 2.6.22-rc4-mm1 WANG Cong
@ 2007-06-06 18:09 ` Andrew Morton
2007-06-07 2:26 ` 2.6.22-rc4-mm1 WANG Cong
0 siblings, 1 reply; 120+ messages in thread
From: Andrew Morton @ 2007-06-06 18:09 UTC (permalink / raw)
To: WANG Cong; +Cc: linux-kernel, Rusty Russell
On Thu, 7 Jun 2007 00:19:36 +0800 WANG Cong <xiyou.wangcong@gmail.com> wrote:
> On Wed, Jun 06, 2007 at 02:07:37AM -0700, Andrew Morton wrote:
> >
> >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
> >
> >- Somebody broke it on my powerpc G5, but I didn't have time to do yet
> > another bisection yet.
> >
>
> It seems strange that a new C source file (mlguest.c) appears in the top dir of the
> kernel source. There are some problems with it.
>
> First, I used `make mlguest.o` to compile that file, but I got tons of warnings and errors.
> (Too many to put here.) What's wrong with it? Or I didn't compile/configure it correctly?
>
> Second, mlguest.c #includes a head file named "../../include/linux/lguest_launcher.h".
> Since mlguest.c is in the top dir, so where is ../../include/linux/lguest_launcher.h?
>
Confused. I've grepped the entire universe here for "mlguest" and came up
with nothing.
I don't have a clue where that file came from on your system.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 18:09 ` 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-07 2:26 ` WANG Cong
2007-06-07 5:59 ` 2.6.22-rc4-mm1 Matt Mackall
0 siblings, 1 reply; 120+ messages in thread
From: WANG Cong @ 2007-06-07 2:26 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, Rusty Russell
On Wed, Jun 06, 2007 at 11:09:31AM -0700, Andrew Morton wrote:
>On Thu, 7 Jun 2007 00:19:36 +0800 WANG Cong <xiyou.wangcong@gmail.com> wrote:
>
>> On Wed, Jun 06, 2007 at 02:07:37AM -0700, Andrew Morton wrote:
>> >
>> >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
>> >
>> >- Somebody broke it on my powerpc G5, but I didn't have time to do yet
>> > another bisection yet.
>> >
>>
>> It seems strange that a new C source file (mlguest.c) appears in the top dir of the
>> kernel source. There are some problems with it.
>>
>> First, I used `make mlguest.o` to compile that file, but I got tons of warnings and errors.
>> (Too many to put here.) What's wrong with it? Or I didn't compile/configure it correctly?
>>
>> Second, mlguest.c #includes a head file named "../../include/linux/lguest_launcher.h".
>> Since mlguest.c is in the top dir, so where is ../../include/linux/lguest_launcher.h?
>>
>
>Confused. I've grepped the entire universe here for "mlguest" and came up
>with nothing.
>
>I don't have a clue where that file came from on your system.
I used 'ketchup' to update my kernel from -rc3 to -rc4-mm1. I got the follow:
[wangcong@localhost linux-2.6.22-rc4-mm1]$ ls
arch Documentation ipc Makefile README System.map
block drivers Kbuild mlguest.c REPORTING-BUGS usr
COPYING fs kernel mm scripts vmlinux
CREDITS include lib Module.symvers security
crypto init MAINTAINERS net sound
Maybe there's something wrong with ketchup. ;(
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 2:26 ` 2.6.22-rc4-mm1 WANG Cong
@ 2007-06-07 5:59 ` Matt Mackall
2007-06-07 6:51 ` 2.6.22-rc4-mm1 WANG Cong
0 siblings, 1 reply; 120+ messages in thread
From: Matt Mackall @ 2007-06-07 5:59 UTC (permalink / raw)
To: WANG Cong; +Cc: Andrew Morton, linux-kernel, Rusty Russell
On Thu, Jun 07, 2007 at 10:26:09AM +0800, WANG Cong wrote:
> On Wed, Jun 06, 2007 at 11:09:31AM -0700, Andrew Morton wrote:
> >On Thu, 7 Jun 2007 00:19:36 +0800 WANG Cong <xiyou.wangcong@gmail.com> wrote:
> >
> >> On Wed, Jun 06, 2007 at 02:07:37AM -0700, Andrew Morton wrote:
> >> >
> >> >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
> >> >
> >> >- Somebody broke it on my powerpc G5, but I didn't have time to do yet
> >> > another bisection yet.
> >> >
> >>
> >> It seems strange that a new C source file (mlguest.c) appears in the top dir of the
> >> kernel source. There are some problems with it.
> >>
> >> First, I used `make mlguest.o` to compile that file, but I got tons of warnings and errors.
> >> (Too many to put here.) What's wrong with it? Or I didn't compile/configure it correctly?
> >>
> >> Second, mlguest.c #includes a head file named "../../include/linux/lguest_launcher.h".
> >> Since mlguest.c is in the top dir, so where is ../../include/linux/lguest_launcher.h?
> >>
> >
> >Confused. I've grepped the entire universe here for "mlguest" and came up
> >with nothing.
> >
> >I don't have a clue where that file came from on your system.
>
>
> I used 'ketchup' to update my kernel from -rc3 to -rc4-mm1. I got the follow:
>
> [wangcong@localhost linux-2.6.22-rc4-mm1]$ ls
> arch Documentation ipc Makefile README System.map
> block drivers Kbuild mlguest.c REPORTING-BUGS usr
> COPYING fs kernel mm scripts vmlinux
> CREDITS include lib Module.symvers security
> crypto init MAINTAINERS net sound
>
> Maybe there's something wrong with ketchup. ;(
Can you do an 'lsdiff | grep lguest' on the patch in your ~/.ketchup directory?
Ketchup simply applies patches, it never touches filenames directly.
So for something to go wrong here and drop a file in the tree with a
damaged pathname, you've either got a damaged patch, a bug in patch
itself, or some form of filesystem corruption.
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 5:59 ` 2.6.22-rc4-mm1 Matt Mackall
@ 2007-06-07 6:51 ` WANG Cong
2007-06-07 14:04 ` 2.6.22-rc4-mm1 Matt Mackall
0 siblings, 1 reply; 120+ messages in thread
From: WANG Cong @ 2007-06-07 6:51 UTC (permalink / raw)
To: Matt Mackall; +Cc: Andrew Morton, linux-kernel, Rusty Russell
On Thu, Jun 07, 2007 at 12:59:13AM -0500, Matt Mackall wrote:
>On Thu, Jun 07, 2007 at 10:26:09AM +0800, WANG Cong wrote:
>> On Wed, Jun 06, 2007 at 11:09:31AM -0700, Andrew Morton wrote:
>> >On Thu, 7 Jun 2007 00:19:36 +0800 WANG Cong <xiyou.wangcong@gmail.com> wrote:
>> >
>> >> On Wed, Jun 06, 2007 at 02:07:37AM -0700, Andrew Morton wrote:
>> >> >
>> >> >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
>> >> >
>> >> >- Somebody broke it on my powerpc G5, but I didn't have time to do yet
>> >> > another bisection yet.
>> >> >
>> >>
>> >> It seems strange that a new C source file (mlguest.c) appears in the top dir of the
>> >> kernel source. There are some problems with it.
>> >>
>> >> First, I used `make mlguest.o` to compile that file, but I got tons of warnings and errors.
>> >> (Too many to put here.) What's wrong with it? Or I didn't compile/configure it correctly?
>> >>
>> >> Second, mlguest.c #includes a head file named "../../include/linux/lguest_launcher.h".
>> >> Since mlguest.c is in the top dir, so where is ../../include/linux/lguest_launcher.h?
>> >>
>> >
>> >Confused. I've grepped the entire universe here for "mlguest" and came up
>> >with nothing.
>> >
>> >I don't have a clue where that file came from on your system.
>>
>>
>> I used 'ketchup' to update my kernel from -rc3 to -rc4-mm1. I got the follow:
>>
>> [wangcong@localhost linux-2.6.22-rc4-mm1]$ ls
>> arch Documentation ipc Makefile README System.map
>> block drivers Kbuild mlguest.c REPORTING-BUGS usr
>> COPYING fs kernel mm scripts vmlinux
>> CREDITS include lib Module.symvers security
>> crypto init MAINTAINERS net sound
>>
>> Maybe there's something wrong with ketchup. ;(
>
>Can you do an 'lsdiff | grep lguest' on the patch in your ~/.ketchup directory?
>
>Ketchup simply applies patches, it never touches filenames directly.
>So for something to go wrong here and drop a file in the tree with a
>damaged pathname, you've either got a damaged patch, a bug in patch
>itself, or some form of filesystem corruption.
Thanks for your point.
It should be Documentation/lguest/lguest.c, maybe it was corrupted and ketchup
backuped it as mlguest.c.
Sorry for this.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 6:51 ` 2.6.22-rc4-mm1 WANG Cong
@ 2007-06-07 14:04 ` Matt Mackall
2007-06-07 15:40 ` 2.6.22-rc4-mm1 WANG Cong
0 siblings, 1 reply; 120+ messages in thread
From: Matt Mackall @ 2007-06-07 14:04 UTC (permalink / raw)
To: WANG Cong; +Cc: Andrew Morton, linux-kernel, Rusty Russell
On Thu, Jun 07, 2007 at 02:51:58PM +0800, WANG Cong wrote:
> >> Maybe there's something wrong with ketchup. ;(
> >
> >Can you do an 'lsdiff | grep lguest' on the patch in your ~/.ketchup directory?
> >
> >Ketchup simply applies patches, it never touches filenames directly.
> >So for something to go wrong here and drop a file in the tree with a
> >damaged pathname, you've either got a damaged patch, a bug in patch
> >itself, or some form of filesystem corruption.
>
> Thanks for your point.
>
> It should be Documentation/lguest/lguest.c, maybe it was corrupted and ketchup
> backuped it as mlguest.c.
It'd be interesting to figure out how that happened, still.
If your patch file is intact (are you using GPG's signature-checking
support?), the most likely explanation is an operating system or
filesystem bug.
Can you reproduce it?
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 14:04 ` 2.6.22-rc4-mm1 Matt Mackall
@ 2007-06-07 15:40 ` WANG Cong
2007-06-07 15:59 ` 2.6.22-rc4-mm1 Matt Mackall
0 siblings, 1 reply; 120+ messages in thread
From: WANG Cong @ 2007-06-07 15:40 UTC (permalink / raw)
To: Matt Mackall; +Cc: Andrew Morton, linux-kernel, Rusty Russell
On Thu, Jun 07, 2007 at 09:04:44AM -0500, Matt Mackall wrote:
>On Thu, Jun 07, 2007 at 02:51:58PM +0800, WANG Cong wrote:
>> >> Maybe there's something wrong with ketchup. ;(
>> >
>> >Can you do an 'lsdiff | grep lguest' on the patch in your ~/.ketchup directory?
>> >
>> >Ketchup simply applies patches, it never touches filenames directly.
>> >So for something to go wrong here and drop a file in the tree with a
>> >damaged pathname, you've either got a damaged patch, a bug in patch
>> >itself, or some form of filesystem corruption.
>>
>> Thanks for your point.
>>
>> It should be Documentation/lguest/lguest.c, maybe it was corrupted and ketchup
>> backuped it as mlguest.c.
>
>It'd be interesting to figure out how that happened, still.
>
>If your patch file is intact (are you using GPG's signature-checking
>support?), the most likely explanation is an operating system or
>filesystem bug.
Yes, I am using GPG's checking.
I think the most possible reason is that source file might be corrupted.
It's hardly the filesystem's fault, since I am using a stable kernel.
>
>Can you reproduce it?
May be very hard.;(
I deleted all the files of that version and download a new version to use.
Thanks!
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 15:40 ` 2.6.22-rc4-mm1 WANG Cong
@ 2007-06-07 15:59 ` Matt Mackall
2007-06-07 16:39 ` 2.6.22-rc4-mm1 WANG Cong
0 siblings, 1 reply; 120+ messages in thread
From: Matt Mackall @ 2007-06-07 15:59 UTC (permalink / raw)
To: WANG Cong; +Cc: Andrew Morton, linux-kernel, Rusty Russell
On Thu, Jun 07, 2007 at 11:40:08PM +0800, WANG Cong wrote:
> On Thu, Jun 07, 2007 at 09:04:44AM -0500, Matt Mackall wrote:
> >On Thu, Jun 07, 2007 at 02:51:58PM +0800, WANG Cong wrote:
> >> >> Maybe there's something wrong with ketchup. ;(
> >> >
> >> >Can you do an 'lsdiff | grep lguest' on the patch in your ~/.ketchup directory?
> >> >
> >> >Ketchup simply applies patches, it never touches filenames directly.
> >> >So for something to go wrong here and drop a file in the tree with a
> >> >damaged pathname, you've either got a damaged patch, a bug in patch
> >> >itself, or some form of filesystem corruption.
> >>
> >> Thanks for your point.
> >>
> >> It should be Documentation/lguest/lguest.c, maybe it was corrupted and ketchup
> >> backuped it as mlguest.c.
> >
> >It'd be interesting to figure out how that happened, still.
> >
> >If your patch file is intact (are you using GPG's signature-checking
> >support?), the most likely explanation is an operating system or
> >filesystem bug.
>
> Yes, I am using GPG's checking.
Well that gives a pretty solid assurance that the patch you downloaded
matches the one on kernel.org. And that one doesn't contain an
mlguest.c.
Ketchup doesn't even look inside patches, and patch doesn't invent
names, so something in the bzip2 -> patch(1) -> filesystem chain got
corrupted. Probably not bzip2, as it has CRCs.
Do you have ECC memory?
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 15:59 ` 2.6.22-rc4-mm1 Matt Mackall
@ 2007-06-07 16:39 ` WANG Cong
2007-06-07 16:59 ` 2.6.22-rc4-mm1 Matt Mackall
0 siblings, 1 reply; 120+ messages in thread
From: WANG Cong @ 2007-06-07 16:39 UTC (permalink / raw)
To: Matt Mackall; +Cc: Andrew Morton, linux-kernel, Rusty Russell
On Thu, Jun 07, 2007 at 10:59:14AM -0500, Matt Mackall wrote:
>On Thu, Jun 07, 2007 at 11:40:08PM +0800, WANG Cong wrote:
>> On Thu, Jun 07, 2007 at 09:04:44AM -0500, Matt Mackall wrote:
>> >On Thu, Jun 07, 2007 at 02:51:58PM +0800, WANG Cong wrote:
>> >> >> Maybe there's something wrong with ketchup. ;(
>> >> >
>> >> >Can you do an 'lsdiff | grep lguest' on the patch in your ~/.ketchup directory?
>> >> >
>> >> >Ketchup simply applies patches, it never touches filenames directly.
>> >> >So for something to go wrong here and drop a file in the tree with a
>> >> >damaged pathname, you've either got a damaged patch, a bug in patch
>> >> >itself, or some form of filesystem corruption.
>> >>
>> >> Thanks for your point.
>> >>
>> >> It should be Documentation/lguest/lguest.c, maybe it was corrupted and ketchup
>> >> backuped it as mlguest.c.
>> >
>> >It'd be interesting to figure out how that happened, still.
>> >
>> >If your patch file is intact (are you using GPG's signature-checking
>> >support?), the most likely explanation is an operating system or
>> >filesystem bug.
>>
>> Yes, I am using GPG's checking.
>
>Well that gives a pretty solid assurance that the patch you downloaded
>matches the one on kernel.org. And that one doesn't contain an
>mlguest.c.
>
I agree.
>Ketchup doesn't even look inside patches, and patch doesn't invent
>names, so something in the bzip2 -> patch(1) -> filesystem chain got
>corrupted. Probably not bzip2, as it has CRCs.
>
Do you mean ketchup doesn't do anything if a file is corrupted?
>Do you have ECC memory?
>
No. Do you mean it's an error of my RAM? I have never met such things before,
how often does such kind of things happen? May be less often than a bug in
a stable kernel?
Thanks!
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 16:39 ` 2.6.22-rc4-mm1 WANG Cong
@ 2007-06-07 16:59 ` Matt Mackall
2007-06-08 4:43 ` 2.6.22-rc4-mm1 WANG Cong
0 siblings, 1 reply; 120+ messages in thread
From: Matt Mackall @ 2007-06-07 16:59 UTC (permalink / raw)
To: WANG Cong; +Cc: Andrew Morton, linux-kernel, Rusty Russell
On Fri, Jun 08, 2007 at 12:39:30AM +0800, WANG Cong wrote:
> >Ketchup doesn't even look inside patches, and patch doesn't invent
> >names, so something in the bzip2 -> patch(1) -> filesystem chain got
> >corrupted. Probably not bzip2, as it has CRCs.
> >
>
> Do you mean ketchup doesn't do anything if a file is corrupted?
Ketchup never even sees the filenames. It just calls bzip2 | patch. So
it can't be responsible for damaging the filename.
> >Do you have ECC memory?
>
> No. Do you mean it's an error of my RAM? I have never met such things before,
> how often does such kind of things happen? May be less often than a bug in
> a stable kernel?
The best studies I've seen suggest so-called "soft errors" in DRAM
happen at a rate of once a week to once a day per gigabyte of RAM at
sea-level. It's unknown how many of these errors manifest by visibly
corrupting data, but it wouldn't be surprising if it were
significantly less than 10%. But ECC is definitely not just for the
paranoid!
So if I were to rank the reliability of everything, it'd look
something like this, highest to lowest:
bzip: simple, stable and heavily-used codebase, built-in safeguards like CRC
patch: simple, stable, heavily-used, limited detection of input errors
CPU: heavily used, very low non-catastrophic failure rate
disk: heavily used, CRC on cable, ECC on disk
kernel: complex, rapidly-changing, but heavily-used
Non-ECC DRAM: significant known transient failure rate
When the error rate for the kernel approaches that of DRAM, it gets
very hard to assign blame.
(And of course, there's the user, who tends to be near the bottom of
this range, but I'll let you judge that.)
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 16:59 ` 2.6.22-rc4-mm1 Matt Mackall
@ 2007-06-08 4:43 ` WANG Cong
0 siblings, 0 replies; 120+ messages in thread
From: WANG Cong @ 2007-06-08 4:43 UTC (permalink / raw)
To: Matt Mackall; +Cc: Andrew Morton, linux-kernel, Rusty Russell
On Thu, Jun 07, 2007 at 11:59:16AM -0500, Matt Mackall wrote:
>On Fri, Jun 08, 2007 at 12:39:30AM +0800, WANG Cong wrote:
>> >Ketchup doesn't even look inside patches, and patch doesn't invent
>> >names, so something in the bzip2 -> patch(1) -> filesystem chain got
>> >corrupted. Probably not bzip2, as it has CRCs.
>> >
>>
>> Do you mean ketchup doesn't do anything if a file is corrupted?
>
>Ketchup never even sees the filenames. It just calls bzip2 | patch. So
>it can't be responsible for damaging the filename.
>
>> >Do you have ECC memory?
>>
>> No. Do you mean it's an error of my RAM? I have never met such things before,
>> how often does such kind of things happen? May be less often than a bug in
>> a stable kernel?
>
>The best studies I've seen suggest so-called "soft errors" in DRAM
>happen at a rate of once a week to once a day per gigabyte of RAM at
>sea-level. It's unknown how many of these errors manifest by visibly
>corrupting data, but it wouldn't be surprising if it were
>significantly less than 10%. But ECC is definitely not just for the
>paranoid!
>
>So if I were to rank the reliability of everything, it'd look
>something like this, highest to lowest:
>
> bzip: simple, stable and heavily-used codebase, built-in safeguards like CRC
> patch: simple, stable, heavily-used, limited detection of input errors
> CPU: heavily used, very low non-catastrophic failure rate
> disk: heavily used, CRC on cable, ECC on disk
> kernel: complex, rapidly-changing, but heavily-used
> Non-ECC DRAM: significant known transient failure rate
>
>When the error rate for the kernel approaches that of DRAM, it gets
>very hard to assign blame.
>
>(And of course, there's the user, who tends to be near the bottom of
>this range, but I'll let you judge that.)
Good explanation! Thanks!
That the RAM error occurs so often really surprises me.
I think it might be RAM's fault, because, at least, it's less reproduceable than
a bug in a stable kernel.
Regards!
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
` (8 preceding siblings ...)
2007-06-06 16:19 ` 2.6.22-rc4-mm1 WANG Cong
@ 2007-06-06 16:30 ` William Lee Irwin III
2007-06-06 18:13 ` 2.6.22-rc4-mm1 Andrew Morton
2007-06-06 18:23 ` 2.6.22-rc4-mm1 Andy Whitcroft
2007-06-06 16:42 ` 2.6.22-rc4-mm1 Cedric Le Goater
` (5 subsequent siblings)
15 siblings, 2 replies; 120+ messages in thread
From: William Lee Irwin III @ 2007-06-06 16:30 UTC (permalink / raw)
To: Paul Menage; +Cc: Andrew Morton, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
On Wed, Jun 06, 2007 at 02:07:37AM -0700, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
> - Somebody broke it on my powerpc G5, but I didn't have time to do yet
> another bisection yet.
> - There's a lengthy patch series here from Nick which attempts to address
> the longstanding pagefault-vs-buffered-write deadlock.
> A great shower of filesystems were broken and have been disabled with
> CONFIG_BROKEN. This includes reiser4.
> - Complex patches which eliminate the kernel's fixed size limit on the
> command-line length. These break nommu builds.
Someone remind me what the pagefault vs. buffered write deadlock is.
Something brings down i386/qemu before even earlyprintk can handle.
Bisection has narrowed it down to patch 1140 after everything got
renumbered by peterz' fix for mm-variable-length-argument-support.patch,
namely containersv10-make-cpusets-a-client-of-containers.patch
-- wli
[-- Attachment #2: config-wli-2.6.22-rc4-mm1 --]
[-- Type: text/plain, Size: 44727 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.22-rc4-mm1
# Wed Jun 6 09:08:11 2007
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=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_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SWAP_PREFETCH=y
CONFIG_SYSVIPC=y
# CONFIG_IPC_NS is not set
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
# CONFIG_UTS_NS is not set
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=15
CONFIG_CONTAINERS=y
CONFIG_CPUSETS=y
CONFIG_SYSFS_DEPRECATED=y
CONFIG_CONTAINER_CPUACCT=y
CONFIG_PROC_PID_CPUSET=y
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_EMBEDDED=y
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=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_SLUB_DEBUG=y
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_PROC_SMAPS=y
CONFIG_PROC_CLEAR_REFS=y
CONFIG_PROC_PAGEMAP=y
CONFIG_PROC_KPAGEMAP=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 is not set
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_LBD=y
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_SMP=y
# CONFIG_X86_PC is not set
# 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=y
# CONFIG_X86_ES7000 is not set
# CONFIG_PARAVIRT is not set
CONFIG_X86_CYCLONE_TIMER=y
# 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_MCORE2 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_X86_GENERIC=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_XADD=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_MODEL=4
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_NR_CPUS=64
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_MCE is not set
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=y
CONFIG_X86_CPUID=y
#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_EFI_VARS is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_VMSPLIT_3G is not set
CONFIG_VMSPLIT_3G_OPT=y
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_2G_OPT is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xB0000000
CONFIG_ARCH_POPULATES_NODE_MAP=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 is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_NR_QUICK=1
CONFIG_VIRT_TO_BUS=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_EFI=y
CONFIG_IRQBALANCE=y
CONFIG_BOOT_IOREMAP=y
CONFIG_SECCOMP=y
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
# CONFIG_KEXEC is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
# CONFIG_HOTPLUG_CPU is not set
CONFIG_COMPAT_VDSO=y
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_LEGACY is not set
# CONFIG_PM_DEBUG is not set
# CONFIG_PM_SYSFS_DEPRECATED is not set
CONFIG_ACPI=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=y
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_ASUS=y
CONFIG_ACPI_TOSHIBA=y
CONFIG_ACPI_BLACKLIST_YEAR=2001
CONFIG_ACPI_DEBUG=y
# CONFIG_ACPI_DEBUG_FUNC_TRACE is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
# CONFIG_ACPI_SBS is not set
# CONFIG_APM is not set
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# CPU idle PM support
#
CONFIG_CPU_IDLE=y
#
# Governors
#
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCIEPORTBUS is not set
CONFIG_ARCH_SUPPORTS_MSI=y
# CONFIG_PCI_MSI is not set
# CONFIG_PCI_DEBUG is not set
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_K8_NB=y
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=y
#
# Networking
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
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_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
# CONFIG_IP_ROUTE_MULTIPATH_CACHED is not set
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# 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 is not set
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
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_IP_VS 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=y
# CONFIG_NETFILTER_DEBUG is not set
#
# Core Netfilter Configuration
#
# CONFIG_NETFILTER_NETLINK is not set
# CONFIG_NF_CONNTRACK_ENABLED is not set
# CONFIG_NF_CONNTRACK is not set
# CONFIG_NETFILTER_XTABLES is not set
#
# IP: Netfilter Configuration
#
# CONFIG_IP_NF_QUEUE is not set
# CONFIG_IP_NF_IPTABLES is not set
# CONFIG_IP_NF_ARPTABLES 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
#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_FIFO=y
#
# Queueing/Scheduling
#
# CONFIG_NET_SCH_CBQ is not set
# CONFIG_NET_SCH_HTB is not set
# CONFIG_NET_SCH_HFSC is not set
# CONFIG_NET_SCH_PRIO is not set
# CONFIG_NET_SCH_RED is not set
# CONFIG_NET_SCH_SFQ is not set
# CONFIG_NET_SCH_TEQL is not set
# CONFIG_NET_SCH_TBF is not set
# CONFIG_NET_SCH_GRED is not set
# CONFIG_NET_SCH_DSMARK is not set
# CONFIG_NET_SCH_NETEM is not set
# CONFIG_NET_SCH_INGRESS is not set
#
# Classification
#
# CONFIG_NET_CLS_BASIC is not set
# CONFIG_NET_CLS_TCINDEX is not set
# CONFIG_NET_CLS_ROUTE4 is not set
# CONFIG_NET_CLS_FW is not set
# CONFIG_NET_CLS_U32 is not set
# CONFIG_NET_CLS_RSVP is not set
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_EMATCH is not set
# CONFIG_NET_CLS_ACT is not set
CONFIG_NET_CLS_POLICE=y
CONFIG_NET_ESTIMATOR=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
CONFIG_FIB_RULES=y
#
# Wireless
#
# CONFIG_CFG80211 is not set
CONFIG_WIRELESS_EXT=y
# CONFIG_MAC80211 is not set
# CONFIG_IEEE80211 is not set
# CONFIG_RFKILL is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
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 is not set
# CONFIG_MTD is not set
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_AX88796 is not set
# CONFIG_PARPORT_1284 is not set
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set
#
# Protocols
#
CONFIG_ISAPNP=y
# CONFIG_PNPBIOS is not set
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE 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=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_MISC_DEVICES=y
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_MSI_LAPTOP is not set
# CONFIG_SONY_LAPTOP is not set
# CONFIG_THINKPAD_ACPI is not set
# CONFIG_BLINK is not set
# CONFIG_EEPROM_93CX6 is not set
CONFIG_IDE=y
CONFIG_IDE_MAX_HWIFS=4
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=y
# CONFIG_BLK_DEV_IDESCSI is not set
CONFIG_BLK_DEV_IDEACPI=y
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_PROC_FS=y
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPNP=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_IDEPCI_PCIBUS_ORDER=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_AEC62XX=y
CONFIG_BLK_DEV_ALI15X3=y
# CONFIG_WDC_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
CONFIG_BLK_DEV_ATIIXP=y
CONFIG_BLK_DEV_CMD64X=y
CONFIG_BLK_DEV_TRIFLEX=y
CONFIG_BLK_DEV_CY82C693=y
CONFIG_BLK_DEV_CS5520=y
CONFIG_BLK_DEV_CS5530=y
# CONFIG_BLK_DEV_CS5535 is not set
CONFIG_BLK_DEV_HPT34X=y
# CONFIG_HPT34X_AUTODMA is not set
CONFIG_BLK_DEV_HPT366=y
# CONFIG_BLK_DEV_JMICRON is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
CONFIG_BLK_DEV_IT8213=y
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
CONFIG_BLK_DEV_PDC202XX_OLD=y
# CONFIG_PDC202XX_BURST is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
CONFIG_BLK_DEV_SVWKS=y
CONFIG_BLK_DEV_SIIMAGE=y
CONFIG_BLK_DEV_SIS5513=y
CONFIG_BLK_DEV_SLC90E66=y
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_BLK_DEV_TC86C001 is not set
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_BLK_DEV_HD 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 is not set
#
# SCSI support type (disk, tape, CD-ROM)
#
# CONFIG_BLK_DEV_SD is not set
# 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 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 is not set
CONFIG_SCSI_FC_ATTRS=y
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS 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_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 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_IN2000 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_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS 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_SEAGATE is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
# CONFIG_ATA is not set
# CONFIG_CD_NO_IDESCSI is not set
# CONFIG_MD is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS 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_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 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_EL1 is not set
# CONFIG_EL2 is not set
# CONFIG_ELPLUS is not set
# CONFIG_EL16 is not set
# CONFIG_EL3 is not set
# CONFIG_3C515 is not set
# CONFIG_VORTEX is not set
# CONFIG_TYPHOON is not set
# CONFIG_LANCE is not set
CONFIG_NET_VENDOR_SMC=y
# CONFIG_WD80x3 is not set
# CONFIG_ULTRA is not set
# CONFIG_SMC9194 is not set
CONFIG_NET_VENDOR_RACAL=y
# CONFIG_NI52 is not set
# CONFIG_NI65 is not set
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
# CONFIG_TULIP is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_ULI526X is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
CONFIG_NET_ISA=y
# CONFIG_E2100 is not set
# CONFIG_EWRK3 is not set
# CONFIG_EEXPRESS is not set
# CONFIG_EEXPRESS_PRO is not set
# CONFIG_HPLAN_PLUS is not set
# CONFIG_HPLAN is not set
# CONFIG_LP486E is not set
# CONFIG_ETH16I is not set
# CONFIG_NE2000 is not set
# CONFIG_ZNET is not set
# CONFIG_SEEQ8005 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_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
CONFIG_NE2K_PCI=y
# CONFIG_8139CP is not set
CONFIG_8139TOO=y
CONFIG_8139TOO_PIO=y
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SC92031 is not set
# CONFIG_NET_POCKET is not set
CONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2 is not set
# 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_IXGB is not set
# CONFIG_S2IO is not set
# CONFIG_MYRI10GE is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_MLX4_CORE is not set
# CONFIG_TR is not set
#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
# CONFIG_RTL818X 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_MII is not set
# CONFIG_USB_USBNET is not set
# CONFIG_WAN is not set
CONFIG_FDDI=y
# CONFIG_DEFXX is not set
# CONFIG_SKFP is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=y
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_PPP_DEFLATE=y
CONFIG_PPP_BSDCOMP=y
# CONFIG_PPP_MPPE is not set
CONFIG_PPPOE=y
# CONFIG_SLIP is not set
CONFIG_SLHC=y
CONFIG_NET_FC=y
# CONFIG_SHAPER 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=y
#
# 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_TSDEV is not set
CONFIG_INPUT_EVDEV=y
# 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_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA is not set
CONFIG_INPUT_JOYSTICK=y
# CONFIG_JOYSTICK_ANALOG is not set
# CONFIG_JOYSTICK_A3D is not set
# CONFIG_JOYSTICK_ADI is not set
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
# CONFIG_JOYSTICK_SIDEWINDER is not set
# CONFIG_JOYSTICK_TMDC is not set
# CONFIG_JOYSTICK_IFORCE is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDJOY is not set
# CONFIG_JOYSTICK_DB9 is not set
# CONFIG_JOYSTICK_GAMECON is not set
# CONFIG_JOYSTICK_TURBOGRAFX is not set
# CONFIG_JOYSTICK_JOYDUMP is not set
# CONFIG_JOYSTICK_XPAD is not set
# CONFIG_INPUT_TABLET is not set
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_TOUCHSCREEN_ELO is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_UCB1400 is not set
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_PCSPKR is not set
# CONFIG_INPUT_WISTRON_BTNS is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
# 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
# CONFIG_INPUT_POLLDEV is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD 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_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_ESPSERIAL is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_MOXA_SMARTIO_NEW is not set
# CONFIG_ISI is not set
# CONFIG_SYNCLINK is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_SYNCLINK_GT is not set
# CONFIG_N_HDLC is not set
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
CONFIG_STALDRV=y
# 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_PNP=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
# CONFIG_SERIAL_8250_MANY_PORTS is not set
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 is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
# CONFIG_PRINTER is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
# CONFIG_IPMI_HANDLER is not set
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_ALIM1535_WDT is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_SC520_WDT is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_IBMASR is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_I6300ESB_WDT is not set
# CONFIG_ITCO_WDT is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_PC87413_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SBC8360_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_SMSC37B787_WDT is not set
# CONFIG_W83627HF_WDT is not set
# CONFIG_W83697HF_WDT is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_W83977F_WDT is not set
# CONFIG_MACHZ_WDT is not set
# CONFIG_SBC_EPX_C3_WATCHDOG is not set
#
# ISA-based Watchdog Cards
#
# CONFIG_PCWATCHDOG is not set
# CONFIG_MIXCOMWD is not set
# CONFIG_WDT is not set
#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set
#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
CONFIG_AGP=y
CONFIG_AGP_ALI=y
CONFIG_AGP_ATI=y
CONFIG_AGP_AMD=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=y
CONFIG_AGP_NVIDIA=y
CONFIG_AGP_SIS=y
CONFIG_AGP_SWORKS=y
CONFIG_AGP_VIA=y
CONFIG_AGP_EFFICEON=y
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_I915 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_GPIO is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
# CONFIG_I2C is not set
#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER 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_ABITUGURU is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_CORETEMP 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_W83627HF is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_SENSORS_APPLESMC is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Sonics Silicon Backplane
#
# 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
# CONFIG_USB_DABUSB is not set
#
# Graphics support
#
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_PROGEAR is not set
#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
# CONFIG_VGASTATE is not set
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
# CONFIG_FB_DDC is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_SYS_FOPS is not set
CONFIG_FB_DEFERRED_IO=y
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
# CONFIG_FB_IMAC is not set
# CONFIG_FB_HECUBA is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# 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_CYBLA is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_MDA_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 is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y
#
# Sound
#
CONFIG_SOUND=y
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_RAWMIDI=y
# CONFIG_SND_SEQUENCER is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_PCM_OSS_PLUGINS=y
# CONFIG_SND_RTCTIMER is not set
# CONFIG_SND_DYNAMIC_MINORS is not set
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_MTS64 is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
# CONFIG_SND_PORTMAN2X4 is not set
#
# ISA devices
#
# CONFIG_SND_ADLIB is not set
# CONFIG_SND_AD1816A is not set
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_ALS100 is not set
# CONFIG_SND_AZT2320 is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_DT019X is not set
# CONFIG_SND_ES968 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_MIRO is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set
# CONFIG_SND_WAVEFRONT is not set
#
# PCI devices
#
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_CS5535AUDIO is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
CONFIG_SND_ENS1370=y
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_HDA_INTEL is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
#
# USB devices
#
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set
# CONFIG_SND_USB_CAIAQ is not set
#
# System on Chip audio support
#
# CONFIG_SND_SOC is not set
#
# SoC Audio support for SuperH
#
#
# Open Sound System
#
# CONFIG_SOUND_PRIME 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=y
CONFIG_HID_PID=y
CONFIG_LOGITECH_FF=y
# CONFIG_PANTHERLORD_FF is not set
CONFIG_THRUSTMASTER_FF=y
# CONFIG_ZEROPLUS_FF is not set
CONFIG_USB_HIDDEV=y
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
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_PERSIST is not set
# CONFIG_USB_OTG is not set
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_EHCI_FSL is not set
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
# 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=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_KARMA 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=y
#
# USB port drivers
#
# CONFIG_USB_USS720 is not set
#
# USB Serial Converter support
#
# 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_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GOTEMP is not set
#
# USB DSL modem support
#
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
# CONFIG_MMC is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_INFINIBAND is not set
# CONFIG_EDAC is not set
#
# Real Time Clock
#
# CONFIG_RTC_CLASS is not set
#
# DMA Engine support
#
# CONFIG_DMA_ENGINE is not set
#
# DMA Clients
#
#
# DMA Devices
#
CONFIG_AUXDISPLAY=y
# CONFIG_KS0108 is not set
CONFIG_VIRTUALIZATION=y
# CONFIG_KVM is not set
#
# Userspace I/O
#
# CONFIG_UIO 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 is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# 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_OCFS2_FS is not set
CONFIG_ROMFS_FS=y
CONFIG_ROMFS_ON_BLOCK=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
# 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=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_RAMFS=y
# CONFIG_CONFIGFS_FS is not set
#
# Layered filesystems
#
# CONFIG_UNION_FS is not set
#
# Miscellaneous filesystems
#
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
#
# Network File Systems
#
CONFIG_NFS_FS=y
# CONFIG_NFS_V3 is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
# CONFIG_NFSD is not set
CONFIG_LOCKD=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_BIND34 is not set
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
# CONFIG_9P_FS is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
CONFIG_OSF_PARTITION=y
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not set
CONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not set
CONFIG_SUN_PARTITION=y
# CONFIG_KARMA_PARTITION is not set
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
# 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=y
# 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
#
# Distributed Lock Manager
#
# CONFIG_DLM is not set
CONFIG_INSTRUMENTATION=y
# CONFIG_PROFILING is not set
# CONFIG_KPROBES is not set
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
CONFIG_HEADERS_CHECK=y
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_SHIRQ=y
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_SCHEDSTATS=y
CONFIG_TIMER_STATS=y
# CONFIG_SLUB_DEBUG_ON is not set
CONFIG_DEBUG_PREEMPT=y
CONFIG_DEBUG_RT_MUTEXES=y
CONFIG_DEBUG_PI_LIST=y
# CONFIG_RT_MUTEX_TESTER is not set
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_LOCK_ALLOC=y
CONFIG_PROVE_LOCKING=y
CONFIG_LOCKDEP=y
# CONFIG_DEBUG_LOCKDEP is not set
CONFIG_TRACE_IRQFLAGS=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_DEBUG_LOCKING_API_SELFTESTS=y
CONFIG_STACKTRACE=y
CONFIG_DEBUG_KOBJECT=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_VM=y
CONFIG_DEBUG_LIST=y
CONFIG_FRAME_POINTER=y
CONFIG_UNWIND_INFO=y
CONFIG_STACK_UNWIND=y
CONFIG_FORCED_INLINING=y
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_EARLY_PRINTK=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_STACK_USAGE=y
CONFIG_DEBUG_RODATA=y
# CONFIG_4KSTACKS is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y
#
# 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_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 is not set
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
# 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=y
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_PCBC=y
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_CRYPTD is not set
# CONFIG_CRYPTO_DES is not set
# 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_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_HW=y
CONFIG_CRYPTO_DEV_PADLOCK=y
CONFIG_CRYPTO_DEV_PADLOCK_AES=y
CONFIG_CRYPTO_DEV_PADLOCK_SHA=y
CONFIG_CRYPTO_DEV_GEODE=y
#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=y
# CONFIG_CRC16 is not set
# 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_ZLIB_DEFLATE=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1
2007-06-06 16:30 ` 2.6.22-rc4-mm1 William Lee Irwin III
@ 2007-06-06 18:13 ` Andrew Morton
2007-06-06 19:43 ` 2.6.22-rc4-mm1 William Lee Irwin III
2007-06-06 18:23 ` 2.6.22-rc4-mm1 Andy Whitcroft
1 sibling, 1 reply; 120+ messages in thread
From: Andrew Morton @ 2007-06-06 18:13 UTC (permalink / raw)
To: William Lee Irwin III; +Cc: Paul Menage, linux-kernel
On Wed, 6 Jun 2007 09:30:53 -0700 William Lee Irwin III <wli@holomorphy.com> wrote:
> On Wed, Jun 06, 2007 at 02:07:37AM -0700, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
> > - Somebody broke it on my powerpc G5, but I didn't have time to do yet
> > another bisection yet.
> > - There's a lengthy patch series here from Nick which attempts to address
> > the longstanding pagefault-vs-buffered-write deadlock.
> > A great shower of filesystems were broken and have been disabled with
> > CONFIG_BROKEN. This includes reiser4.
> > - Complex patches which eliminate the kernel's fixed size limit on the
> > command-line length. These break nommu builds.
>
> Someone remind me what the pagefault vs. buffered write deadlock is.
generic_file_write() does lock_page(), then copies the user's data into
pagecache. If that copy_from_user() encounters a major fault and the page
is not uptodate, the pagefault handler does lock_page() and deadlocks.
It requires that the user be writ()ing from a mmap of the page back into
the same page, which is weird.
The kernel tries to prefault the page to avoid the copy_from_user() fault,
but there are ways in whcih that can be defeated (super memory pressure,
malicious fadvise() from a second thread, etc).
> Something brings down i386/qemu before even earlyprintk can handle.
>
> Bisection has narrowed it down to patch 1140 after everything got
> renumbered by peterz' fix for mm-variable-length-argument-support.patch,
> namely containersv10-make-cpusets-a-client-of-containers.patch
erk. A step-by-step how-to-make-this-happen might help if poss, please.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 18:13 ` 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-06 19:43 ` William Lee Irwin III
2007-06-07 0:32 ` 2.6.22-rc4-mm1 Paul Menage
0 siblings, 1 reply; 120+ messages in thread
From: William Lee Irwin III @ 2007-06-06 19:43 UTC (permalink / raw)
To: Andrew Morton; +Cc: Paul Menage, linux-kernel
On Wed, 6 Jun 2007 09:30:53 -0700 William Lee Irwin III <wli@holomorphy.com> wrote:
>> Something brings down i386/qemu before even earlyprintk can handle.
>> Bisection has narrowed it down to patch 1140 after everything got
>> renumbered by peterz' fix for mm-variable-length-argument-support.patch,
>> namely containersv10-make-cpusets-a-client-of-containers.patch
On Wed, Jun 06, 2007 at 11:13:15AM -0700, Andrew Morton wrote:
> erk. A step-by-step how-to-make-this-happen might help if poss, please.
(1) build for i386 with my .config
(2) attempt to boot in qemu's i386 system simulator
I'm not seeing the sort of nondeterminism Andy Whitcroft is. It breaks
every time when I try this.
-- wli
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 19:43 ` 2.6.22-rc4-mm1 William Lee Irwin III
@ 2007-06-07 0:32 ` Paul Menage
2007-06-07 1:09 ` 2.6.22-rc4-mm1 Andrew Morton
0 siblings, 1 reply; 120+ messages in thread
From: Paul Menage @ 2007-06-07 0:32 UTC (permalink / raw)
To: William Lee Irwin III; +Cc: Andrew Morton, linux-kernel
On 6/6/07, William Lee Irwin III <wli@holomorphy.com> wrote:
>
> (1) build for i386 with my .config
> (2) attempt to boot in qemu's i386 system simulator
>
> I'm not seeing the sort of nondeterminism Andy Whitcroft is. It breaks
> every time when I try this.
>
Looks to be lockdep related - it's reproducible for me when I turn on
CONFIG_LOCKDEP and the early crash goes away when I move the
container_init_early() call to after lockdep_init().
Paul
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 0:32 ` 2.6.22-rc4-mm1 Paul Menage
@ 2007-06-07 1:09 ` Andrew Morton
2007-06-07 6:13 ` 2.6.22-rc4-mm1 William Lee Irwin III
0 siblings, 1 reply; 120+ messages in thread
From: Andrew Morton @ 2007-06-07 1:09 UTC (permalink / raw)
To: Paul Menage; +Cc: William Lee Irwin III, linux-kernel
On Wed, 6 Jun 2007 17:32:33 -0700 "Paul Menage" <menage@google.com> wrote:
> On 6/6/07, William Lee Irwin III <wli@holomorphy.com> wrote:
> >
> > (1) build for i386 with my .config
> > (2) attempt to boot in qemu's i386 system simulator
> >
> > I'm not seeing the sort of nondeterminism Andy Whitcroft is. It breaks
> > every time when I try this.
> >
>
> Looks to be lockdep related - it's reproducible for me when I turn on
> CONFIG_LOCKDEP and the early crash goes away when I move the
> container_init_early() call to after lockdep_init().
>
ooh, yes, lockdep_init() really does want to be called before anything
else.
So do we take it that this code hasn't been tested with lockdep? Please
don't forget that step - lockdep finds some pretty nasty bugs sometimes.
This?
--- a/init/main.c~containersv10-basic-container-framework-fix-2
+++ a/init/main.c
@@ -503,7 +503,6 @@ asmlinkage void __init start_kernel(void
char * command_line;
extern struct kernel_param __start___param[], __stop___param[];
- container_init_early();
smp_setup_processor_id();
/*
@@ -512,6 +511,7 @@ asmlinkage void __init start_kernel(void
*/
unwind_init();
lockdep_init();
+ container_init_early();
local_irq_disable();
early_boot_irqs_off();
_
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 1:09 ` 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-07 6:13 ` William Lee Irwin III
0 siblings, 0 replies; 120+ messages in thread
From: William Lee Irwin III @ 2007-06-07 6:13 UTC (permalink / raw)
To: Andrew Morton; +Cc: Paul Menage, linux-kernel
On Wed, Jun 06, 2007 at 06:09:24PM -0700, Andrew Morton wrote:
> ooh, yes, lockdep_init() really does want to be called before anything
> else.
> So do we take it that this code hasn't been tested with lockdep? Please
> don't forget that step - lockdep finds some pretty nasty bugs sometimes.
> This?
I found this patch when I woke and it got things booting with the full
-mm stack. Now to fix the sparc32 build and see if it boots.
-- wli
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 16:30 ` 2.6.22-rc4-mm1 William Lee Irwin III
2007-06-06 18:13 ` 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-06 18:23 ` Andy Whitcroft
1 sibling, 0 replies; 120+ messages in thread
From: Andy Whitcroft @ 2007-06-06 18:23 UTC (permalink / raw)
To: William Lee Irwin III; +Cc: Paul Menage, Andrew Morton, linux-kernel
William Lee Irwin III wrote:
> On Wed, Jun 06, 2007 at 02:07:37AM -0700, Andrew Morton wrote:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
>> - Somebody broke it on my powerpc G5, but I didn't have time to do yet
>> another bisection yet.
>> - There's a lengthy patch series here from Nick which attempts to address
>> the longstanding pagefault-vs-buffered-write deadlock.
>> A great shower of filesystems were broken and have been disabled with
>> CONFIG_BROKEN. This includes reiser4.
>> - Complex patches which eliminate the kernel's fixed size limit on the
>> command-line length. These break nommu builds.
>
> Someone remind me what the pagefault vs. buffered write deadlock is.
>
> Something brings down i386/qemu before even earlyprintk can handle.
>
> Bisection has narrowed it down to patch 1140 after everything got
> renumbered by peterz' fix for mm-variable-length-argument-support.patch,
> namely containersv10-make-cpusets-a-client-of-containers.patch
Interestingly (and perhaps unrelatedly) on my _good_ boots the first
printk is no longer the kernel banner but the following which sounds
container related also:
Initializing container subsys cpuset
-apw
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
` (9 preceding siblings ...)
2007-06-06 16:30 ` 2.6.22-rc4-mm1 William Lee Irwin III
@ 2007-06-06 16:42 ` Cedric Le Goater
2007-06-06 18:48 ` 2.6.22-rc4-mm1 Michal Piotrowski
` (4 subsequent siblings)
15 siblings, 0 replies; 120+ messages in thread
From: Cedric Le Goater @ 2007-06-06 16:42 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, Arnd Bergmann, Nick Piggin
Here's a tentative fix for mm-merge-nopfn-into-fault.patch.
./arch/powerpc/platforms/cell/spufs/file.c: In function 'spufs_mem_mmap_fault':
./arch/powerpc/platforms/cell/spufs/file.c:122: error: 'address' undeclared (first use in this function)
./arch/powerpc/platforms/cell/spufs/file.c:122: error: (Each undeclared identifier is reported only once
./arch/powerpc/platforms/cell/spufs/file.c:122: error: for each function it appears in.)
./arch/powerpc/platforms/cell/spufs/file.c:141: error: expected ';' before 'if'
./arch/powerpc/platforms/cell/spufs/file.c:122: warning: unused variable 'addr0'
I'm not sure how useful is the addr0 variable.
Signed-off-by: Cedric Le Goater <clg@fr.ibm.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>
---
arch/powerpc/platforms/cell/spufs/file.c | 23 +++++------------------
1 file changed, 5 insertions(+), 18 deletions(-)
Index: 2.6.22-rc4-mm1/arch/powerpc/platforms/cell/spufs/file.c
===================================================================
--- 2.6.22-rc4-mm1.orig/arch/powerpc/platforms/cell/spufs/file.c
+++ 2.6.22-rc4-mm1/arch/powerpc/platforms/cell/spufs/file.c
@@ -53,19 +53,6 @@ spufs_mem_open(struct inode *inode, stru
return 0;
}
-static int
-spufs_mem_release(struct inode *inode, struct file *file)
-{
- struct spufs_inode_info *i = SPUFS_I(inode);
- struct spu_context *ctx = i->i_ctx;
-
- spin_lock(&ctx->mapping_lock);
- if (!--i->i_openers)
- ctx->local_store = NULL;
- spin_unlock(&ctx->mapping_lock);
- return 0;
-}
-
static ssize_t
__spufs_mem_read(struct spu_context *ctx, char __user *buffer,
size_t size, loff_t *pos)
@@ -119,13 +106,13 @@ static struct page *spufs_mem_mmap_fault
struct fault_data *fdata)
{
struct spu_context *ctx = vma->vm_file->private_data;
- unsigned long pfn, offset, addr0 = address;
+ unsigned long pfn, offset, addr0 = fdata->address;
#ifdef CONFIG_SPU_FS_64K_LS
struct spu_state *csa = &ctx->csa;
int psize;
/* Check what page size we are using */
- psize = get_slice_psize(vma->vm_mm, address);
+ psize = get_slice_psize(vma->vm_mm, fdata->address);
/* Some sanity checking */
BUG_ON(csa->use_big_pages != (psize == MMU_PAGE_64K));
@@ -133,18 +120,18 @@ static struct page *spufs_mem_mmap_fault
/* Wow, 64K, cool, we need to align the address though */
if (csa->use_big_pages) {
BUG_ON(vma->vm_start & 0xffff);
- address &= ~0xfffful;
+ fdata->address &= ~0xfffful;
}
#endif /* CONFIG_SPU_FS_64K_LS */
- offset = fdata->pgoff << PAGE_SHIFT
+ offset = fdata->pgoff << PAGE_SHIFT;
if (offset >= LS_SIZE) {
fdata->type = VM_FAULT_SIGBUS;
return NULL;
}
pr_debug("spufs_mem_mmap_nopfn address=0x%lx -> 0x%lx, offset=0x%lx\n",
- addr0, address, offset);
+ addr0, fdata->address, offset);
spu_acquire(ctx);
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
` (10 preceding siblings ...)
2007-06-06 16:42 ` 2.6.22-rc4-mm1 Cedric Le Goater
@ 2007-06-06 18:48 ` Michal Piotrowski
2007-06-06 20:16 ` 2.6.22-rc4-mm1 Andrew Morton
2007-06-06 22:14 ` 2.6.22-rc4-mm1 Kay Sievers
2007-06-06 19:32 ` 2.6.22-rc4-mm1 Mariusz Kozlowski
` (3 subsequent siblings)
15 siblings, 2 replies; 120+ messages in thread
From: Michal Piotrowski @ 2007-06-06 18:48 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, Kay Sievers, Greg Kroah-Hartman
Andrew Morton pisze:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
>
Kay, your patch gregkh-driver-block-device.patch breaks Fedora 7 initrd
http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/initrd.jpg
Please fix it ASAP, I can't test kernel...
Regards,
Michal
--
"Najbardziej brakowało mi twojego milczenia."
-- Andrzej Sapkowski "Coś więcej"
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1
2007-06-06 18:48 ` 2.6.22-rc4-mm1 Michal Piotrowski
@ 2007-06-06 20:16 ` Andrew Morton
2007-06-06 22:14 ` 2.6.22-rc4-mm1 Kay Sievers
1 sibling, 0 replies; 120+ messages in thread
From: Andrew Morton @ 2007-06-06 20:16 UTC (permalink / raw)
To: Michal Piotrowski; +Cc: linux-kernel, Kay Sievers, Greg Kroah-Hartman
On Wed, 06 Jun 2007 20:48:45 +0200 Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> Andrew Morton pisze:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
> >
>
> Kay, your patch gregkh-driver-block-device.patch breaks Fedora 7 initrd
> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/initrd.jpg
>
> Please fix it ASAP, I can't test kernel...
>
Yes, that looks just like what I was seeing on the yellowdog powerpc machine.
Is uses http://userweb.kernel.org/~akpm/config-g5.txt (plus `make oldconfig' of
course).
I'll revert it.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 18:48 ` 2.6.22-rc4-mm1 Michal Piotrowski
2007-06-06 20:16 ` 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-06 22:14 ` Kay Sievers
2007-06-07 8:40 ` 2.6.22-rc4-mm1 Michal Piotrowski
1 sibling, 1 reply; 120+ messages in thread
From: Kay Sievers @ 2007-06-06 22:14 UTC (permalink / raw)
To: Michal Piotrowski; +Cc: Andrew Morton, linux-kernel, Greg Kroah-Hartman
On Wed, 2007-06-06 at 20:48 +0200, Michal Piotrowski wrote:
> Andrew Morton pisze:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
> >
>
> Kay, your patch gregkh-driver-block-device.patch breaks Fedora 7 initrd
> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/initrd.jpg
>
> Please fix it ASAP, I can't test kernel...
Do you have CONFIG_SYSFS_DEPRECATED set or unset?
Kay
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 22:14 ` 2.6.22-rc4-mm1 Kay Sievers
@ 2007-06-07 8:40 ` Michal Piotrowski
2007-06-07 8:48 ` 2.6.22-rc4-mm1 Kay Sievers
0 siblings, 1 reply; 120+ messages in thread
From: Michal Piotrowski @ 2007-06-07 8:40 UTC (permalink / raw)
To: Kay Sievers
Cc: Michal Piotrowski, Andrew Morton, linux-kernel,
Greg Kroah-Hartman
Kay Sievers pisze:
> On Wed, 2007-06-06 at 20:48 +0200, Michal Piotrowski wrote:
>> Andrew Morton pisze:
>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
>>>
>> Kay, your patch gregkh-driver-block-device.patch breaks Fedora 7 initrd
>> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/initrd.jpg
>>
>> Please fix it ASAP, I can't test kernel...
>
> Do you have CONFIG_SYSFS_DEPRECATED set or unset?
>
> Kay
>
>
cat ../linux-mm-bo/.config | grep CONFIG_SYSFS_DEPRECATED
# CONFIG_SYSFS_DEPRECATED is not set
Regards,
Michal
--
"Najbardziej brakowało mi twojego milczenia."
-- Andrzej Sapkowski "Coś więcej"
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 8:40 ` 2.6.22-rc4-mm1 Michal Piotrowski
@ 2007-06-07 8:48 ` Kay Sievers
2007-06-07 9:41 ` 2.6.22-rc4-mm1 Michal Piotrowski
0 siblings, 1 reply; 120+ messages in thread
From: Kay Sievers @ 2007-06-07 8:48 UTC (permalink / raw)
To: Michal Piotrowski; +Cc: Andrew Morton, linux-kernel, Greg Kroah-Hartman
On Thu, 2007-06-07 at 10:40 +0200, Michal Piotrowski wrote:
> Kay Sievers pisze:
> > On Wed, 2007-06-06 at 20:48 +0200, Michal Piotrowski wrote:
> >> Andrew Morton pisze:
> >>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
> >>>
> >> Kay, your patch gregkh-driver-block-device.patch breaks Fedora 7 initrd
> >> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/initrd.jpg
> >>
> >> Please fix it ASAP, I can't test kernel...
> >
> > Do you have CONFIG_SYSFS_DEPRECATED set or unset?
> >
> > Kay
> >
> >
>
> cat ../linux-mm-bo/.config | grep CONFIG_SYSFS_DEPRECATED
> # CONFIG_SYSFS_DEPRECATED is not set
Oh, could you possibly try (with the block patch included) setting it to
yes and see if it works? That would help to find what's going wrong.
Thanks,
Kay
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 8:48 ` 2.6.22-rc4-mm1 Kay Sievers
@ 2007-06-07 9:41 ` Michal Piotrowski
2007-06-07 15:04 ` 2.6.22-rc4-mm1 Kay Sievers
0 siblings, 1 reply; 120+ messages in thread
From: Michal Piotrowski @ 2007-06-07 9:41 UTC (permalink / raw)
To: Kay Sievers
Cc: Michal Piotrowski, Andrew Morton, linux-kernel,
Greg Kroah-Hartman
Kay Sievers pisze:
> On Thu, 2007-06-07 at 10:40 +0200, Michal Piotrowski wrote:
>> Kay Sievers pisze:
>>> On Wed, 2007-06-06 at 20:48 +0200, Michal Piotrowski wrote:
>>>> Andrew Morton pisze:
>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
>>>>>
>>>> Kay, your patch gregkh-driver-block-device.patch breaks Fedora 7 initrd
>>>> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/initrd.jpg
>>>>
>>>> Please fix it ASAP, I can't test kernel...
>>> Do you have CONFIG_SYSFS_DEPRECATED set or unset?
>>>
>>> Kay
>>>
>>>
>> cat ../linux-mm-bo/.config | grep CONFIG_SYSFS_DEPRECATED
>> # CONFIG_SYSFS_DEPRECATED is not set
>
> Oh, could you possibly try (with the block patch included) setting it to
> yes and see if it works? That would help to find what's going wrong.
I enabled CONFIG_SYSFS_DEPRECATED and 2.6.22-rc4-mm2 boots fine.
Regards,
Michal
--
"Najbardziej brakowało mi twojego milczenia."
-- Andrzej Sapkowski "Coś więcej"
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 9:41 ` 2.6.22-rc4-mm1 Michal Piotrowski
@ 2007-06-07 15:04 ` Kay Sievers
2007-06-07 15:25 ` 2.6.22-rc4-mm1 Peter Jones
0 siblings, 1 reply; 120+ messages in thread
From: Kay Sievers @ 2007-06-07 15:04 UTC (permalink / raw)
To: Michal Piotrowski, Peter Jones
Cc: Andrew Morton, linux-kernel, Greg Kroah-Hartman
On Thu, 2007-06-07 at 11:41 +0200, Michal Piotrowski wrote:
> Kay Sievers pisze:
> > On Thu, 2007-06-07 at 10:40 +0200, Michal Piotrowski wrote:
> >> Kay Sievers pisze:
> >>> On Wed, 2007-06-06 at 20:48 +0200, Michal Piotrowski wrote:
> >>>> Andrew Morton pisze:
> >>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
> >>>>>
> >>>> Kay, your patch gregkh-driver-block-device.patch breaks Fedora 7 initrd
> >>>> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/initrd.jpg
> >>>>
> >>>> Please fix it ASAP, I can't test kernel...
> >>> Do you have CONFIG_SYSFS_DEPRECATED set or unset?
> >>>
> >>> Kay
> >>>
> >>>
> >> cat ../linux-mm-bo/.config | grep CONFIG_SYSFS_DEPRECATED
> >> # CONFIG_SYSFS_DEPRECATED is not set
> >
> > Oh, could you possibly try (with the block patch included) setting it to
> > yes and see if it works? That would help to find what's going wrong.
>
> I enabled CONFIG_SYSFS_DEPRECATED and 2.6.22-rc4-mm2 boots fine.
Michal, thanks a lot for the testing.
Peter, looking at your mkinitrd code, it works only with
CONFIG_SYSFS_DEPRECATED enabled when block devices are converted to
class devices.
Any chance to replace lstat() with stat() while looking for devices in
sysfs? Remember, _anything_ in sysfs can be symlink or a directory, you
can't assume one or the other. When things change internally in the
kernel, we can often provide symlinks for backwards compatibility, but
lstat() obviously can't works here.
Thanks,
Kay
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 15:04 ` 2.6.22-rc4-mm1 Kay Sievers
@ 2007-06-07 15:25 ` Peter Jones
2007-06-07 15:43 ` 2.6.22-rc4-mm1 Greg KH
0 siblings, 1 reply; 120+ messages in thread
From: Peter Jones @ 2007-06-07 15:25 UTC (permalink / raw)
To: Kay Sievers
Cc: Michal Piotrowski, Andrew Morton, linux-kernel,
Greg Kroah-Hartman
Kay Sievers wrote:
> On Thu, 2007-06-07 at 11:41 +0200, Michal Piotrowski wrote:
>> Kay Sievers pisze:
>>> On Thu, 2007-06-07 at 10:40 +0200, Michal Piotrowski wrote:
>>>> Kay Sievers pisze:
>>>>> On Wed, 2007-06-06 at 20:48 +0200, Michal Piotrowski wrote:
>>>>>> Andrew Morton pisze:
>>>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
>>>>>>>
>>>>>> Kay, your patch gregkh-driver-block-device.patch breaks Fedora 7 initrd
>>>>>> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/initrd.jpg
>>>>>>
>>>>>> Please fix it ASAP, I can't test kernel...
>>>>> Do you have CONFIG_SYSFS_DEPRECATED set or unset?
>>>>>
>>>>> Kay
>>>>>
>>>>>
>>>> cat ../linux-mm-bo/.config | grep CONFIG_SYSFS_DEPRECATED
>>>> # CONFIG_SYSFS_DEPRECATED is not set
>>> Oh, could you possibly try (with the block patch included) setting it to
>>> yes and see if it works? That would help to find what's going wrong.
>> I enabled CONFIG_SYSFS_DEPRECATED and 2.6.22-rc4-mm2 boots fine.
>
> Michal, thanks a lot for the testing.
>
> Peter, looking at your mkinitrd code, it works only with
> CONFIG_SYSFS_DEPRECATED enabled when block devices are converted to
> class devices.
> Any chance to replace lstat() with stat() while looking for devices in
> sysfs? Remember, _anything_ in sysfs can be symlink or a directory, you
> can't assume one or the other. When things change internally in the
> kernel, we can often provide symlinks for backwards compatibility, but
> lstat() obviously can't works here.
Fixed in mkinitrd-6.0.9-6 , which I'll build now and push to
updates-testing. Thanks for getting my attention here.
--
Peter
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 15:25 ` 2.6.22-rc4-mm1 Peter Jones
@ 2007-06-07 15:43 ` Greg KH
2007-06-07 15:52 ` 2.6.22-rc4-mm1 Andrew Morton
0 siblings, 1 reply; 120+ messages in thread
From: Greg KH @ 2007-06-07 15:43 UTC (permalink / raw)
To: Andrew Morton; +Cc: Peter Jones, Kay Sievers, Michal Piotrowski, linux-kernel
On Thu, Jun 07, 2007 at 11:25:57AM -0400, Peter Jones wrote:
> Kay Sievers wrote:
> > On Thu, 2007-06-07 at 11:41 +0200, Michal Piotrowski wrote:
> >> Kay Sievers pisze:
> >>> On Thu, 2007-06-07 at 10:40 +0200, Michal Piotrowski wrote:
> >>>> Kay Sievers pisze:
> >>>>> On Wed, 2007-06-06 at 20:48 +0200, Michal Piotrowski wrote:
> >>>>>> Andrew Morton pisze:
> >>>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
> >>>>>>>
> >>>>>> Kay, your patch gregkh-driver-block-device.patch breaks Fedora 7
> >>>>>> initrd
> >>>>>> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4-mm1/initrd.jpg
> >>>>>>
> >>>>>> Please fix it ASAP, I can't test kernel...
> >>>>> Do you have CONFIG_SYSFS_DEPRECATED set or unset?
> >>>>>
> >>>>> Kay
> >>>>>
> >>>>>
> >>>> cat ../linux-mm-bo/.config | grep CONFIG_SYSFS_DEPRECATED
> >>>> # CONFIG_SYSFS_DEPRECATED is not set
> >>> Oh, could you possibly try (with the block patch included) setting it to
> >>> yes and see if it works? That would help to find what's going wrong.
> >> I enabled CONFIG_SYSFS_DEPRECATED and 2.6.22-rc4-mm2 boots fine.
> > Michal, thanks a lot for the testing.
> > Peter, looking at your mkinitrd code, it works only with
> > CONFIG_SYSFS_DEPRECATED enabled when block devices are converted to
> > class devices.
> > Any chance to replace lstat() with stat() while looking for devices in
> > sysfs? Remember, _anything_ in sysfs can be symlink or a directory, you
> > can't assume one or the other. When things change internally in the
> > kernel, we can often provide symlinks for backwards compatibility, but
> > lstat() obviously can't works here.
>
> Fixed in mkinitrd-6.0.9-6 , which I'll build now and push to
> updates-testing. Thanks for getting my attention here.
Great, Andrew, can you please reenable the block-device patch that is in
my tree now that the problem has been solved?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 15:43 ` 2.6.22-rc4-mm1 Greg KH
@ 2007-06-07 15:52 ` Andrew Morton
2007-06-07 15:59 ` 2.6.22-rc4-mm1 Greg KH
0 siblings, 1 reply; 120+ messages in thread
From: Andrew Morton @ 2007-06-07 15:52 UTC (permalink / raw)
To: Greg KH; +Cc: Peter Jones, Kay Sievers, Michal Piotrowski, linux-kernel
On Thu, 7 Jun 2007 08:43:42 -0700 Greg KH <gregkh@suse.de> wrote:
> > Fixed in mkinitrd-6.0.9-6 , which I'll build now and push to
> > updates-testing. Thanks for getting my attention here.
>
> Great, Andrew, can you please reenable the block-device patch that is in
> my tree now that the problem has been solved?
I think we're screwed, aren't we? Everyone needs to upgrade mkinitrd to be
able to boot the kernel? Not viable :(
For example, what about my two-year-old yellowdog machine?
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 15:52 ` 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-07 15:59 ` Greg KH
2007-06-07 16:06 ` 2.6.22-rc4-mm1 Andrew Morton
0 siblings, 1 reply; 120+ messages in thread
From: Greg KH @ 2007-06-07 15:59 UTC (permalink / raw)
To: Andrew Morton; +Cc: Peter Jones, Kay Sievers, Michal Piotrowski, linux-kernel
On Thu, Jun 07, 2007 at 08:52:00AM -0700, Andrew Morton wrote:
> On Thu, 7 Jun 2007 08:43:42 -0700 Greg KH <gregkh@suse.de> wrote:
>
> > > Fixed in mkinitrd-6.0.9-6 , which I'll build now and push to
> > > updates-testing. Thanks for getting my attention here.
> >
> > Great, Andrew, can you please reenable the block-device patch that is in
> > my tree now that the problem has been solved?
>
> I think we're screwed, aren't we? Everyone needs to upgrade mkinitrd to be
> able to boot the kernel? Not viable :(
>
> For example, what about my two-year-old yellowdog machine?
Enable CONFIG_SYSFS_DEPRECATED and it should all work just fine. That's
what Michal said worked for him.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 15:59 ` 2.6.22-rc4-mm1 Greg KH
@ 2007-06-07 16:06 ` Andrew Morton
2007-06-07 16:15 ` 2.6.22-rc4-mm1 Greg KH
0 siblings, 1 reply; 120+ messages in thread
From: Andrew Morton @ 2007-06-07 16:06 UTC (permalink / raw)
To: Greg KH; +Cc: Peter Jones, Kay Sievers, Michal Piotrowski, linux-kernel
On Thu, 7 Jun 2007 08:59:53 -0700 Greg KH <gregkh@suse.de> wrote:
> On Thu, Jun 07, 2007 at 08:52:00AM -0700, Andrew Morton wrote:
> > On Thu, 7 Jun 2007 08:43:42 -0700 Greg KH <gregkh@suse.de> wrote:
> >
> > > > Fixed in mkinitrd-6.0.9-6 , which I'll build now and push to
> > > > updates-testing. Thanks for getting my attention here.
> > >
> > > Great, Andrew, can you please reenable the block-device patch that is in
> > > my tree now that the problem has been solved?
> >
> > I think we're screwed, aren't we? Everyone needs to upgrade mkinitrd to be
> > able to boot the kernel? Not viable :(
> >
> > For example, what about my two-year-old yellowdog machine?
>
> Enable CONFIG_SYSFS_DEPRECATED and it should all work just fine. That's
> what Michal said worked for him.
>
Actually, it _was_ enabled.
Ho hum, I'll have a poke at it this evening.
So... what's the story here? Should our position be that
CONFIG_SYSFS_DEPRECATED=n should only be used by distro kernel-builders,
who are concurrently shipping userspace which can handle it? And that
these distros should (probably) set CONFIG_SYSFS_DEPRECATED=y in their
update kernels for older distributions?
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 16:06 ` 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-07 16:15 ` Greg KH
2007-06-07 18:48 ` 2.6.22-rc4-mm1 Bill Nottingham
2007-06-08 7:31 ` 2.6.22-rc4-mm1 Andrew Morton
0 siblings, 2 replies; 120+ messages in thread
From: Greg KH @ 2007-06-07 16:15 UTC (permalink / raw)
To: Andrew Morton; +Cc: Peter Jones, Kay Sievers, Michal Piotrowski, linux-kernel
On Thu, Jun 07, 2007 at 09:06:32AM -0700, Andrew Morton wrote:
> On Thu, 7 Jun 2007 08:59:53 -0700 Greg KH <gregkh@suse.de> wrote:
>
> > On Thu, Jun 07, 2007 at 08:52:00AM -0700, Andrew Morton wrote:
> > > On Thu, 7 Jun 2007 08:43:42 -0700 Greg KH <gregkh@suse.de> wrote:
> > >
> > > > > Fixed in mkinitrd-6.0.9-6 , which I'll build now and push to
> > > > > updates-testing. Thanks for getting my attention here.
> > > >
> > > > Great, Andrew, can you please reenable the block-device patch that is in
> > > > my tree now that the problem has been solved?
> > >
> > > I think we're screwed, aren't we? Everyone needs to upgrade mkinitrd to be
> > > able to boot the kernel? Not viable :(
> > >
> > > For example, what about my two-year-old yellowdog machine?
> >
> > Enable CONFIG_SYSFS_DEPRECATED and it should all work just fine. That's
> > what Michal said worked for him.
> >
>
> Actually, it _was_ enabled.
>
> Ho hum, I'll have a poke at it this evening.
Yeah, that sounds odd, it should have worked.
> So... what's the story here? Should our position be that
> CONFIG_SYSFS_DEPRECATED=n should only be used by distro kernel-builders,
> who are concurrently shipping userspace which can handle it?
Yes.
There are a number of distros out there right now who can support that
option disabled. I'm pretty sure they are the following right now:
Gentoo unstable (actually stable works now for me, but I'm not
going to guarantee it just yet...)
Debian unstable (again stable might work, but I have not heard
any reports from testers.)
openSUSE FACTORY (the 10.3 alpha releases)
and now it sounds like Red Hat rawhide will also work properly.
> And that these distros should (probably) set CONFIG_SYSFS_DEPRECATED=y
> in their update kernels for older distributions?
Yes, unless they have tested things and it all works properly (all old
usages of libsysfs need to be removed and 'odd' initrd scripts need to
be updated as in the case of Red Hat.)
thanks,
greg k-h
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 16:15 ` 2.6.22-rc4-mm1 Greg KH
@ 2007-06-07 18:48 ` Bill Nottingham
2007-06-07 20:01 ` 2.6.22-rc4-mm1 Greg KH
2007-06-08 7:31 ` 2.6.22-rc4-mm1 Andrew Morton
1 sibling, 1 reply; 120+ messages in thread
From: Bill Nottingham @ 2007-06-07 18:48 UTC (permalink / raw)
To: Greg KH
Cc: Andrew Morton, Peter Jones, Kay Sievers, Michal Piotrowski,
linux-kernel
Greg KH (gregkh@suse.de) said:
> There are a number of distros out there right now who can support that
> option disabled. I'm pretty sure they are the following right now:
> Gentoo unstable (actually stable works now for me, but I'm not
> going to guarantee it just yet...)
> Debian unstable (again stable might work, but I have not heard
> any reports from testers.)
> openSUSE FACTORY (the 10.3 alpha releases)
>
> and now it sounds like Red Hat rawhide will also work properly.
I suspect while it will work for mkinitrd, the installer will not
work properly.
Bill
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 18:48 ` 2.6.22-rc4-mm1 Bill Nottingham
@ 2007-06-07 20:01 ` Greg KH
2007-06-07 21:00 ` 2.6.22-rc4-mm1 Peter Jones
2007-06-07 22:32 ` 2.6.22-rc4-mm1 Alan Cox
0 siblings, 2 replies; 120+ messages in thread
From: Greg KH @ 2007-06-07 20:01 UTC (permalink / raw)
To: Andrew Morton, Peter Jones, Kay Sievers, Michal Piotrowski,
linux-kernel
On Thu, Jun 07, 2007 at 02:48:05PM -0400, Bill Nottingham wrote:
> Greg KH (gregkh@suse.de) said:
> > There are a number of distros out there right now who can support that
> > option disabled. I'm pretty sure they are the following right now:
> > Gentoo unstable (actually stable works now for me, but I'm not
> > going to guarantee it just yet...)
> > Debian unstable (again stable might work, but I have not heard
> > any reports from testers.)
> > openSUSE FACTORY (the 10.3 alpha releases)
> >
> > and now it sounds like Red Hat rawhide will also work properly.
>
> I suspect while it will work for mkinitrd, the installer will not
> work properly.
Ah, but the installer doesn't matter until you do a Fedora 8 release,
right? This is just for people who want to run their own kernel on an
already-set-up Fedora machine.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 20:01 ` 2.6.22-rc4-mm1 Greg KH
@ 2007-06-07 21:00 ` Peter Jones
2007-06-07 23:09 ` 2.6.22-rc4-mm1 Greg KH
2007-06-07 22:32 ` 2.6.22-rc4-mm1 Alan Cox
1 sibling, 1 reply; 120+ messages in thread
From: Peter Jones @ 2007-06-07 21:00 UTC (permalink / raw)
To: Greg KH; +Cc: Andrew Morton, Kay Sievers, Michal Piotrowski, linux-kernel
Greg KH wrote:
> On Thu, Jun 07, 2007 at 02:48:05PM -0400, Bill Nottingham wrote:
>> Greg KH (gregkh@suse.de) said:
>>> There are a number of distros out there right now who can support that
>>> option disabled. I'm pretty sure they are the following right now:
>>> Gentoo unstable (actually stable works now for me, but I'm not
>>> going to guarantee it just yet...)
>>> Debian unstable (again stable might work, but I have not heard
>>> any reports from testers.)
>>> openSUSE FACTORY (the 10.3 alpha releases)
>>>
>>> and now it sounds like Red Hat rawhide will also work properly.
>> I suspect while it will work for mkinitrd, the installer will not
>> work properly.
>
> Ah, but the installer doesn't matter until you do a Fedora 8 release,
> right? This is just for people who want to run their own kernel on an
> already-set-up Fedora machine.
Eh, not so sure that's true. It's really kudzu rather than the
installer itself, and that's used by, for example, system-config-network.
--
Peter
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 21:00 ` 2.6.22-rc4-mm1 Peter Jones
@ 2007-06-07 23:09 ` Greg KH
0 siblings, 0 replies; 120+ messages in thread
From: Greg KH @ 2007-06-07 23:09 UTC (permalink / raw)
To: Peter Jones; +Cc: Andrew Morton, Kay Sievers, Michal Piotrowski, linux-kernel
On Thu, Jun 07, 2007 at 05:00:41PM -0400, Peter Jones wrote:
> Greg KH wrote:
> > On Thu, Jun 07, 2007 at 02:48:05PM -0400, Bill Nottingham wrote:
> >> Greg KH (gregkh@suse.de) said:
> >>> There are a number of distros out there right now who can support that
> >>> option disabled. I'm pretty sure they are the following right now:
> >>> Gentoo unstable (actually stable works now for me, but I'm not
> >>> going to guarantee it just yet...)
> >>> Debian unstable (again stable might work, but I have not heard
> >>> any reports from testers.)
> >>> openSUSE FACTORY (the 10.3 alpha releases)
> >>>
> >>> and now it sounds like Red Hat rawhide will also work properly.
> >> I suspect while it will work for mkinitrd, the installer will not
> >> work properly.
> > Ah, but the installer doesn't matter until you do a Fedora 8 release,
> > right? This is just for people who want to run their own kernel on an
> > already-set-up Fedora machine.
>
> Eh, not so sure that's true. It's really kudzu rather than the installer
> itself, and that's used by, for example, system-config-network.
Ok, then for Fedora 7 users, we should just recommend to keep
CONFIG_SYSFS_DEPRECATED enabled if you are using the -mm tree now, or
after 2.6.23 is out (which is the earliest I expect this block patch to
show up in mainline.)
thanks,
greg k-h
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 20:01 ` 2.6.22-rc4-mm1 Greg KH
2007-06-07 21:00 ` 2.6.22-rc4-mm1 Peter Jones
@ 2007-06-07 22:32 ` Alan Cox
2007-06-07 23:09 ` 2.6.22-rc4-mm1 Greg KH
1 sibling, 1 reply; 120+ messages in thread
From: Alan Cox @ 2007-06-07 22:32 UTC (permalink / raw)
To: Greg KH
Cc: Andrew Morton, Peter Jones, Kay Sievers, Michal Piotrowski,
linux-kernel
> Ah, but the installer doesn't matter until you do a Fedora 8 release,
> right? This is just for people who want to run their own kernel on an
> already-set-up Fedora machine.
People can and do roll updated install images because you get systems
that aren't supported by the released CD boot image. The installer/initrd
etc shouldn't keep getting broken by these kind of changes, its about
time that all the sysfs type breakage causing patches simply got
rejected, like such patches would in every other subsystem.
Yes it might cause a little pain, yes someone might have to tweak sysfs a
bit to keep compatibility and decouple the external and internal view a
bit - Matthew and others pointed out this problem several years ago and
predicted the current state of affairs, so its had a lot of time to get
fixed.
Alan
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 22:32 ` 2.6.22-rc4-mm1 Alan Cox
@ 2007-06-07 23:09 ` Greg KH
2007-06-08 15:33 ` 2.6.22-rc4-mm1 Valdis.Kletnieks
0 siblings, 1 reply; 120+ messages in thread
From: Greg KH @ 2007-06-07 23:09 UTC (permalink / raw)
To: Alan Cox
Cc: Andrew Morton, Peter Jones, Kay Sievers, Michal Piotrowski,
linux-kernel
On Thu, Jun 07, 2007 at 11:32:58PM +0100, Alan Cox wrote:
> > Ah, but the installer doesn't matter until you do a Fedora 8 release,
> > right? This is just for people who want to run their own kernel on an
> > already-set-up Fedora machine.
>
> People can and do roll updated install images because you get systems
> that aren't supported by the released CD boot image. The installer/initrd
> etc shouldn't keep getting broken by these kind of changes, its about
> time that all the sysfs type breakage causing patches simply got
> rejected, like such patches would in every other subsystem.
>
> Yes it might cause a little pain, yes someone might have to tweak sysfs a
> bit to keep compatibility and decouple the external and internal view a
> bit - Matthew and others pointed out this problem several years ago and
> predicted the current state of affairs, so its had a lot of time to get
> fixed.
If CONFIG_SYSFS_DEPRECATED everything should work just fine with all old
initrd scripts. It's only if you enable that option (which is enabled
by default) that you need to ensure that your distro has the latest
functionality so that everything works properly.
So, we should be fine here. The distros that are up to date, and the
users of them, can disable the option. All others need to keep it on.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 23:09 ` 2.6.22-rc4-mm1 Greg KH
@ 2007-06-08 15:33 ` Valdis.Kletnieks
2007-06-08 15:50 ` 2.6.22-rc4-mm1 Greg KH
2007-06-08 16:10 ` 2.6.22-rc4-mm1 Kay Sievers
0 siblings, 2 replies; 120+ messages in thread
From: Valdis.Kletnieks @ 2007-06-08 15:33 UTC (permalink / raw)
To: Greg KH
Cc: Alan Cox, Andrew Morton, Peter Jones, Kay Sievers,
Michal Piotrowski, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 434 bytes --]
On Thu, 07 Jun 2007 16:09:04 PDT, Greg KH said:
> If CONFIG_SYSFS_DEPRECATED everything should work just fine with all old
> initrd scripts. It's only if you enable that option (which is enabled
> by default) that you need to ensure that your distro has the latest
> functionality so that everything works properly.
Can somebody document what an initrd has to do differently? Some of us
run with initrd's not created by mkinitrd.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-08 15:33 ` 2.6.22-rc4-mm1 Valdis.Kletnieks
@ 2007-06-08 15:50 ` Greg KH
2007-06-08 16:11 ` 2.6.22-rc4-mm1 Greg KH
2007-06-08 16:10 ` 2.6.22-rc4-mm1 Kay Sievers
1 sibling, 1 reply; 120+ messages in thread
From: Greg KH @ 2007-06-08 15:50 UTC (permalink / raw)
To: Valdis.Kletnieks
Cc: Alan Cox, Andrew Morton, Alan Stern, Peter Jones, Kay Sievers,
Michal Piotrowski, linux-kernel
On Fri, Jun 08, 2007 at 11:33:38AM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 07 Jun 2007 16:09:04 PDT, Greg KH said:
> > If CONFIG_SYSFS_DEPRECATED everything should work just fine with all old
> > initrd scripts. It's only if you enable that option (which is enabled
> > by default) that you need to ensure that your distro has the latest
> > functionality so that everything works properly.
>
> Can somebody document what an initrd has to do differently? Some of us
> run with initrd's not created by mkinitrd.
So I'm guessing that you wrote your own initrd?
The main issue is that /sys/block/ is now full of symlinks, not real
directories, if CONFIG_SYSFS_DEPRECATED is not enabled. That means that
any program that was doing stat() should be doing lstat() for the block
directory to work on all instances (remember, whenever looking for a
directory or a file in sysfs, it could be either a real file/directory
or a symlink, you should not care either way.)
People have also reported that for some reason, removing the '--movedev'
argument to switchroot is also needed, but that might just be a Fedora 7
specific thing, I'm not quite sure.
See the post from Alan Stern on lkml with the subject:
Re: [RFC PATCH] /sys/block -> /sys/class/block (Fedora 3 & 4 testers wanted)
for more details on that.
Hope this helps,
greg k-h
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-08 15:50 ` 2.6.22-rc4-mm1 Greg KH
@ 2007-06-08 16:11 ` Greg KH
0 siblings, 0 replies; 120+ messages in thread
From: Greg KH @ 2007-06-08 16:11 UTC (permalink / raw)
To: Valdis.Kletnieks
Cc: Alan Cox, Andrew Morton, Alan Stern, Peter Jones, Kay Sievers,
Michal Piotrowski, linux-kernel
On Fri, Jun 08, 2007 at 08:50:27AM -0700, Greg KH wrote:
> On Fri, Jun 08, 2007 at 11:33:38AM -0400, Valdis.Kletnieks@vt.edu wrote:
> > On Thu, 07 Jun 2007 16:09:04 PDT, Greg KH said:
> > > If CONFIG_SYSFS_DEPRECATED everything should work just fine with all old
> > > initrd scripts. It's only if you enable that option (which is enabled
> > > by default) that you need to ensure that your distro has the latest
> > > functionality so that everything works properly.
> >
> > Can somebody document what an initrd has to do differently? Some of us
> > run with initrd's not created by mkinitrd.
>
> So I'm guessing that you wrote your own initrd?
>
> The main issue is that /sys/block/ is now full of symlinks, not real
> directories, if CONFIG_SYSFS_DEPRECATED is not enabled. That means that
> any program that was doing stat() should be doing lstat() for the block
> directory to work on all instances (remember, whenever looking for a
> directory or a file in sysfs, it could be either a real file/directory
> or a symlink, you should not care either way.)
Oops, sorry about that, it should be the other way around, stat(), not
lstat().
greg k-h
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-08 15:33 ` 2.6.22-rc4-mm1 Valdis.Kletnieks
2007-06-08 15:50 ` 2.6.22-rc4-mm1 Greg KH
@ 2007-06-08 16:10 ` Kay Sievers
1 sibling, 0 replies; 120+ messages in thread
From: Kay Sievers @ 2007-06-08 16:10 UTC (permalink / raw)
To: Valdis.Kletnieks
Cc: Greg KH, Alan Cox, Andrew Morton, Peter Jones, Michal Piotrowski,
linux-kernel
On Fri, 2007-06-08 at 11:33 -0400, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 07 Jun 2007 16:09:04 PDT, Greg KH said:
> > If CONFIG_SYSFS_DEPRECATED everything should work just fine with all old
> > initrd scripts. It's only if you enable that option (which is enabled
> > by default) that you need to ensure that your distro has the latest
> > functionality so that everything works properly.
>
> Can somebody document what an initrd has to do differently? Some of us
> run with initrd's not created by mkinitrd.
You should be fine if you don't explicitly distinguish between symlinks
and directories.
Or just look what almost everybody is doing in initramfs, Debian,
Gentoo, Ubuntu, SUSE, ..., all use uevent-driven udev bootup there, and
it just works without caring about anything in sysfs or weird timing
issues.
Kay
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 16:15 ` 2.6.22-rc4-mm1 Greg KH
2007-06-07 18:48 ` 2.6.22-rc4-mm1 Bill Nottingham
@ 2007-06-08 7:31 ` Andrew Morton
2007-06-08 15:51 ` 2.6.22-rc4-mm1 Greg KH
1 sibling, 1 reply; 120+ messages in thread
From: Andrew Morton @ 2007-06-08 7:31 UTC (permalink / raw)
To: Greg KH; +Cc: Peter Jones, Kay Sievers, Michal Piotrowski, linux-kernel
On Thu, 7 Jun 2007 09:15:25 -0700 Greg KH <gregkh@suse.de> wrote:
> On Thu, Jun 07, 2007 at 09:06:32AM -0700, Andrew Morton wrote:
> > On Thu, 7 Jun 2007 08:59:53 -0700 Greg KH <gregkh@suse.de> wrote:
> >
> > > On Thu, Jun 07, 2007 at 08:52:00AM -0700, Andrew Morton wrote:
> > > > On Thu, 7 Jun 2007 08:43:42 -0700 Greg KH <gregkh@suse.de> wrote:
> > > >
> > > > > > Fixed in mkinitrd-6.0.9-6 , which I'll build now and push to
> > > > > > updates-testing. Thanks for getting my attention here.
> > > > >
> > > > > Great, Andrew, can you please reenable the block-device patch that is in
> > > > > my tree now that the problem has been solved?
> > > >
> > > > I think we're screwed, aren't we? Everyone needs to upgrade mkinitrd to be
> > > > able to boot the kernel? Not viable :(
> > > >
> > > > For example, what about my two-year-old yellowdog machine?
> > >
> > > Enable CONFIG_SYSFS_DEPRECATED and it should all work just fine. That's
> > > what Michal said worked for him.
> > >
> >
> > Actually, it _was_ enabled.
> >
> > Ho hum, I'll have a poke at it this evening.
>
> Yeah, that sounds odd, it should have worked.
yup, yellowdog 4.1 on a mac g5:
gregkh-driver-block-device.patch applied, CONFIG_SYSFS_DEPRECATED=y:
http://userweb.kernel.org/~akpm/s5000552.jpg
gregkh-driver-block-device.patch applied, CONFIG_SYSFS_DEPRECATED=n:
Can't open /dev/sdb6 (root partition)
gregkh-driver-block-device.patch not applied, CONFIG_SYSFS_DEPRECATED=y:
Happy camper
gregkh-driver-block-device.patch not applied, CONFIG_SYSFS_DEPRECATED=n:
Still happy
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-08 7:31 ` 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-08 15:51 ` Greg KH
2007-06-08 16:36 ` 2.6.22-rc4-mm1 Kay Sievers
0 siblings, 1 reply; 120+ messages in thread
From: Greg KH @ 2007-06-08 15:51 UTC (permalink / raw)
To: Andrew Morton; +Cc: Peter Jones, Kay Sievers, Michal Piotrowski, linux-kernel
On Fri, Jun 08, 2007 at 12:31:18AM -0700, Andrew Morton wrote:
> On Thu, 7 Jun 2007 09:15:25 -0700 Greg KH <gregkh@suse.de> wrote:
>
> > On Thu, Jun 07, 2007 at 09:06:32AM -0700, Andrew Morton wrote:
> > > On Thu, 7 Jun 2007 08:59:53 -0700 Greg KH <gregkh@suse.de> wrote:
> > >
> > > > On Thu, Jun 07, 2007 at 08:52:00AM -0700, Andrew Morton wrote:
> > > > > On Thu, 7 Jun 2007 08:43:42 -0700 Greg KH <gregkh@suse.de> wrote:
> > > > >
> > > > > > > Fixed in mkinitrd-6.0.9-6 , which I'll build now and push to
> > > > > > > updates-testing. Thanks for getting my attention here.
> > > > > >
> > > > > > Great, Andrew, can you please reenable the block-device patch that is in
> > > > > > my tree now that the problem has been solved?
> > > > >
> > > > > I think we're screwed, aren't we? Everyone needs to upgrade mkinitrd to be
> > > > > able to boot the kernel? Not viable :(
> > > > >
> > > > > For example, what about my two-year-old yellowdog machine?
> > > >
> > > > Enable CONFIG_SYSFS_DEPRECATED and it should all work just fine. That's
> > > > what Michal said worked for him.
> > > >
> > >
> > > Actually, it _was_ enabled.
> > >
> > > Ho hum, I'll have a poke at it this evening.
> >
> > Yeah, that sounds odd, it should have worked.
>
> yup, yellowdog 4.1 on a mac g5:
>
> gregkh-driver-block-device.patch applied, CONFIG_SYSFS_DEPRECATED=y:
> http://userweb.kernel.org/~akpm/s5000552.jpg
Ugh.
Kay, any thoughts? Does switchroot need to have the --movedev option
removed for some reason?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-08 15:51 ` 2.6.22-rc4-mm1 Greg KH
@ 2007-06-08 16:36 ` Kay Sievers
2007-06-08 17:21 ` 2.6.22-rc4-mm1 Peter Jones
0 siblings, 1 reply; 120+ messages in thread
From: Kay Sievers @ 2007-06-08 16:36 UTC (permalink / raw)
To: Greg KH; +Cc: Andrew Morton, Peter Jones, Michal Piotrowski, linux-kernel
On Fri, 2007-06-08 at 08:51 -0700, Greg KH wrote:
> On Fri, Jun 08, 2007 at 12:31:18AM -0700, Andrew Morton wrote:
> > On Thu, 7 Jun 2007 09:15:25 -0700 Greg KH <gregkh@suse.de> wrote:
> >
> > > On Thu, Jun 07, 2007 at 09:06:32AM -0700, Andrew Morton wrote:
> > > > On Thu, 7 Jun 2007 08:59:53 -0700 Greg KH <gregkh@suse.de> wrote:
> > > >
> > > > > On Thu, Jun 07, 2007 at 08:52:00AM -0700, Andrew Morton wrote:
> > > > > > On Thu, 7 Jun 2007 08:43:42 -0700 Greg KH <gregkh@suse.de> wrote:
> > > > > >
> > > > > > > > Fixed in mkinitrd-6.0.9-6 , which I'll build now and push to
> > > > > > > > updates-testing. Thanks for getting my attention here.
> > > > > > >
> > > > > > > Great, Andrew, can you please reenable the block-device patch that is in
> > > > > > > my tree now that the problem has been solved?
> > > > > >
> > > > > > I think we're screwed, aren't we? Everyone needs to upgrade mkinitrd to be
> > > > > > able to boot the kernel? Not viable :(
> > > > > >
> > > > > > For example, what about my two-year-old yellowdog machine?
> > > > >
> > > > > Enable CONFIG_SYSFS_DEPRECATED and it should all work just fine. That's
> > > > > what Michal said worked for him.
> > > > >
> > > >
> > > > Actually, it _was_ enabled.
> > > >
> > > > Ho hum, I'll have a poke at it this evening.
> > >
> > > Yeah, that sounds odd, it should have worked.
> >
> > yup, yellowdog 4.1 on a mac g5:
> >
> > gregkh-driver-block-device.patch applied, CONFIG_SYSFS_DEPRECATED=y:
> > http://userweb.kernel.org/~akpm/s5000552.jpg
>
> Ugh.
>
> Kay, any thoughts? Does switchroot need to have the --movedev option
> removed for some reason?
Hmm, no idea, /sys/block should not have changed with
CONFIG_SYSFS_DEPRECATED=y. And it works fine for Michal and FC7.
Alan Stern mentioned the --movedev option with its customized initramfs,
or did other people report something similar?
Peter, any idea what it could be, that goes wrong on Andrew's box, or
how to look for what exactly is going wrong?
http://userweb.kernel.org/~akpm/s5000552.jpg
Seems that yellowdog uses RH's nash.
Thanks,
Kay
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-08 16:36 ` 2.6.22-rc4-mm1 Kay Sievers
@ 2007-06-08 17:21 ` Peter Jones
0 siblings, 0 replies; 120+ messages in thread
From: Peter Jones @ 2007-06-08 17:21 UTC (permalink / raw)
To: Andrew Morton
Cc: Kay Sievers, Greg KH, Michal Piotrowski,
Linux Kernel Mailing List
Kay Sievers wrote:
> Peter, any idea what it could be, that goes wrong on Andrew's box, or
> how to look for what exactly is going wrong?
> http://userweb.kernel.org/~akpm/s5000552.jpg
> Seems that yellowdog uses RH's nash.
Yeah, but a /really/ old version -- 4.2.11 is from May 2005 :/ . I feel
I should point out that that version IS using udev, but just like
mkinitrd and nash, the udev there is probably just as old. At the same
time, that does make it an excellent test case for this sort of situation.
Andrew, is there any chance you can put that initrd.img somewhere that I
can download it? That'd really help me to figure out what's going on,
as the minutia of our initrds from 2005 have faded a bit in my memory.
--
Peter
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
` (11 preceding siblings ...)
2007-06-06 18:48 ` 2.6.22-rc4-mm1 Michal Piotrowski
@ 2007-06-06 19:32 ` Mariusz Kozlowski
2007-06-06 20:24 ` 2.6.22-rc4-mm1 Andrew Morton
2007-06-06 20:58 ` 2.6.22-rc4-mm1 Grant Wilson
` (2 subsequent siblings)
15 siblings, 1 reply; 120+ messages in thread
From: Mariusz Kozlowski @ 2007-06-06 19:32 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
Hello,
This is from my P4 sony vaio laptop.
These warnings still there:
drivers/input/keyboard/Kconfig:170:warning: 'select' used by config symbol 'KEYBOARD_ATARI' refers to undefined symbol 'ATARI_KBD_CORE'
drivers/input/mouse/Kconfig:182:warning: 'select' used by config symbol 'MOUSE_ATARI' refers to undefined symbol 'ATARI_KBD_CORE'
sound/soc/sh/Kconfig:6:warning: 'select' used by config symbol 'SND_SOC_PCM_SH7760' refers to undefined symbol 'SH_DMABRG'
A hwmon related build error:
Building modules, stage 2.
MODPOST 187 modules
ERROR: "input_register_polled_device" [drivers/hwmon/hdaps.ko] undefined!
ERROR: "input_allocate_polled_device" [drivers/hwmon/hdaps.ko] undefined!
ERROR: "input_free_polled_device" [drivers/hwmon/hdaps.ko] undefined!
ERROR: "input_unregister_polled_device" [drivers/hwmon/hdaps.ko] undefined!
ERROR: "input_register_polled_device" [drivers/hwmon/applesmc.ko] undefined!
ERROR: "input_allocate_polled_device" [drivers/hwmon/applesmc.ko] undefined!
ERROR: "input_free_polled_device" [drivers/hwmon/applesmc.ko] undefined!
ERROR: "input_unregister_polled_device" [drivers/hwmon/applesmc.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
And for some reason the whole Cryptographic API is under the main level of menu
(please find .config and menu.png attached).
More tests soon.
Mariusz
[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 45319 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.22-rc4-mm1
# Wed Jun 6 20:45:44 2007
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=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_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
#
# General setup
#
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SWAP=y
CONFIG_SWAP_PREFETCH=y
CONFIG_SYSVIPC=y
# CONFIG_IPC_NS is not set
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
# CONFIG_TASKSTATS is not set
# CONFIG_UTS_NS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=18
# CONFIG_CONTAINER_DEBUG is not set
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_CONTAINER_CPUACCT is not set
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=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_PROC_SMAPS=y
CONFIG_PROC_CLEAR_REFS=y
CONFIG_PROC_PAGEMAP=y
CONFIG_PROC_KPAGEMAP=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=y
CONFIG_BLOCK=y
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_DEFAULT_AS=y
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="anticipatory"
#
# Processor type and features
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not set
# CONFIG_SMP is not set
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_PARAVIRT is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MCORE2 is not set
CONFIG_MPENTIUM4=y
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_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_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_XADD=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_CMPXCHG64=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_MODEL=4
# CONFIG_HPET_TIMER is not set
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=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
#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_NR_QUICK=1
CONFIG_VIRT_TO_BUS=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_SECCOMP=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_KEXEC is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_COMPAT_VDSO=y
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
# CONFIG_PM_SYSFS_DEPRECATED is not set
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION="/dev/hda2"
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_SLEEP_PROC_SLEEP is not set
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set
# CONFIG_ACPI_SBS is not set
# CONFIG_APM is not set
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# CPU idle PM support
#
# CONFIG_CPU_IDLE is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCIEPORTBUS is not set
# CONFIG_ARCH_SUPPORTS_MSI is not set
# CONFIG_PCI_DEBUG is not set
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_PCCARD=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=m
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_CARDBUS=y
#
# PC-card bridges
#
CONFIG_YENTA=m
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
CONFIG_PD6729=m
CONFIG_I82092=m
CONFIG_I82365=m
CONFIG_TCIC=m
CONFIG_PCMCIA_PROBE=y
CONFIG_PCCARD_NONSTATIC=m
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y
#
# 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_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 is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
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_IP_VS 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=y
# CONFIG_NETFILTER_DEBUG is not set
#
# Core Netfilter Configuration
#
# CONFIG_NETFILTER_NETLINK is not set
# CONFIG_NF_CONNTRACK_ENABLED is not set
# CONFIG_NF_CONNTRACK is not set
# CONFIG_NETFILTER_XTABLES is not set
#
# IP: Netfilter Configuration
#
# CONFIG_IP_NF_QUEUE is not set
# CONFIG_IP_NF_IPTABLES is not set
# CONFIG_IP_NF_ARPTABLES 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
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
#
# Wireless
#
# CONFIG_CFG80211 is not set
CONFIG_WIRELESS_EXT=y
# CONFIG_MAC80211 is not set
CONFIG_IEEE80211=y
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=m
CONFIG_IEEE80211_CRYPT_TKIP=m
CONFIG_IEEE80211_SOFTMAC=m
# CONFIG_IEEE80211_SOFTMAC_DEBUG is not set
# CONFIG_RFKILL is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
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=y
CONFIG_PARPORT_PC=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_PC_PCMCIA is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_AX88796 is not set
# CONFIG_PARPORT_1284 is not set
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set
#
# Protocols
#
# CONFIG_ISAPNP is not set
# CONFIG_PNPBIOS is not set
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_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=y
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_SONY_LAPTOP is not set
# CONFIG_THINKPAD_ACPI is not set
# CONFIG_BLINK is not set
# CONFIG_EEPROM_93CX6 is not set
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_BLK_DEV_IDECS is not set
# CONFIG_BLK_DEV_DELKIN is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_BLK_DEV_IDEACPI is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_PROC_FS=y
#
# IDE chipset support/bugfixes
#
# CONFIG_IDE_GENERIC is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_IDEPCI_PCIBUS_ORDER=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
CONFIG_BLK_DEV_ALI15X3=y
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_CS5535 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_JMICRON is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_IT8213 is not set
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_BLK_DEV_TC86C001 is not set
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_BLK_DEV_HD 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=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 is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS 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_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 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_IN2000 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_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS 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_SEAGATE is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
CONFIG_SCSI_LOWLEVEL_PCMCIA=y
# CONFIG_PCMCIA_AHA152X is not set
# CONFIG_PCMCIA_FDOMAIN is not set
# CONFIG_PCMCIA_NINJA_SCSI is not set
# CONFIG_PCMCIA_QLOGIC is not set
# CONFIG_PCMCIA_SYM53C500 is not set
# CONFIG_ATA is not set
# CONFIG_CD_NO_IDESCSI is not set
# CONFIG_MD is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
CONFIG_IEEE1394=y
#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
#
# Controllers
#
# CONFIG_IEEE1394_PCILYNX is not set
CONFIG_IEEE1394_OHCI1394=y
#
# Protocols
#
# CONFIG_IEEE1394_VIDEO1394 is not set
# CONFIG_IEEE1394_SBP2 is not set
# CONFIG_IEEE1394_ETH1394_ROM_ENTRY is not set
# CONFIG_IEEE1394_ETH1394 is not set
# CONFIG_IEEE1394_DV1394 is not set
CONFIG_IEEE1394_RAWIO=y
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 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 is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
CONFIG_8139TOO=m
CONFIG_8139TOO_PIO=y
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SC92031 is not set
# CONFIG_NET_POCKET is not set
CONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2 is not set
# 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_IXGB is not set
# CONFIG_S2IO is not set
# CONFIG_MYRI10GE is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_MLX4_CORE is not set
# CONFIG_TR is not set
#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
# CONFIG_RTL818X 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_MII is not set
# CONFIG_USB_USBNET is not set
# CONFIG_NET_PCMCIA is not set
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=m
# CONFIG_PPP_MULTILINK is not set
# CONFIG_PPP_FILTER is not set
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
# CONFIG_SLIP is not set
CONFIG_SLHC=m
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
CONFIG_NETCONSOLE=m
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS 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_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_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_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
CONFIG_INPUT_POLLDEV=m
#
# 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_PARKBD 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_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=m
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=m
CONFIG_SERIAL_8250_PNP=m
CONFIG_SERIAL_8250_CS=m
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=m
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_PRINTER=y
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=m
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
CONFIG_HW_RANDOM_GEODE=m
CONFIG_HW_RANDOM_VIA=m
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
CONFIG_SONYPI=m
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
CONFIG_AGP_ATI=y
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=y
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_CARDMAN_4000 is not set
# CONFIG_CARDMAN_4040 is not set
# CONFIG_IPWIRELESS_CS is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_GPIO is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=m
#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_ALGOPCA=m
#
# I2C Hardware Bus support
#
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI1563=m
CONFIG_I2C_ALI15X3=m
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD756_S4882=m
CONFIG_I2C_AMD8111=m
CONFIG_I2C_ELEKTOR=m
CONFIG_I2C_I801=m
CONFIG_I2C_I810=m
CONFIG_I2C_PIIX4=m
CONFIG_I2C_NFORCE2=m
CONFIG_I2C_OCORES=m
CONFIG_I2C_PARPORT=m
CONFIG_I2C_PARPORT_LIGHT=m
CONFIG_I2C_PROSAVAGE=m
CONFIG_I2C_SAVAGE4=m
CONFIG_I2C_SIMTEC=m
CONFIG_SCx200_ACB=m
CONFIG_I2C_SIS5595=m
CONFIG_I2C_SIS630=m
CONFIG_I2C_SIS96X=m
CONFIG_I2C_STUB=m
CONFIG_I2C_TINY_USB=m
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
CONFIG_I2C_VOODOO3=m
CONFIG_I2C_PCA_ISA=m
#
# Miscellaneous I2C Chip support
#
CONFIG_SENSORS_DS1337=m
CONFIG_SENSORS_DS1374=m
CONFIG_DS1682=m
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_PCF8574=m
CONFIG_SENSORS_PCA9539=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_MAX6875=m
CONFIG_SENSORS_TSL2550=m
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
#
# SPI support
#
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y
#
# SPI Master Controller Drivers
#
# CONFIG_SPI_BITBANG is not set
# CONFIG_SPI_BUTTERFLY is not set
# CONFIG_SPI_LM70_LLP is not set
#
# SPI Protocol Masters
#
# CONFIG_SPI_AT25 is not set
# CONFIG_SPI_SPIDEV is not set
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
CONFIG_SENSORS_ABITUGURU=m
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
CONFIG_SENSORS_K8TEMP=m
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS1621 is not set
CONFIG_SENSORS_F71805F=m
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_FSCPOS is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
CONFIG_SENSORS_CORETEMP=m
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM63 is not set
CONFIG_SENSORS_LM70=m
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX6650 is not set
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_SIS5595=m
# CONFIG_SENSORS_DME1737 is not set
CONFIG_SENSORS_SMSC47M1=m
# CONFIG_SENSORS_SMSC47M192 is not set
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83L785TS is not set
CONFIG_SENSORS_W83627HF=m
# CONFIG_SENSORS_W83627EHF is not set
CONFIG_SENSORS_HDAPS=m
CONFIG_SENSORS_APPLESMC=m
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Sonics Silicon Backplane
#
# 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
# CONFIG_USB_DABUSB is not set
#
# Graphics support
#
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
# CONFIG_VGASTATE is not set
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
# CONFIG_FB_DDC is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_SYS_FOPS is not set
CONFIG_FB_DEFERRED_IO=y
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
# CONFIG_FB_HECUBA is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# 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_CYBLA is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL 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=y
# CONFIG_MDA_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=y
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_RAWMIDI=y
CONFIG_SND_SEQUENCER=y
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_DYNAMIC_MINORS is not set
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
CONFIG_SND_MPU401_UART=y
CONFIG_SND_AC97_CODEC=y
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_MTS64 is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
# CONFIG_SND_PORTMAN2X4 is not set
#
# ISA devices
#
# CONFIG_SND_ADLIB is not set
# CONFIG_SND_AD1816A is not set
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_ALS100 is not set
# CONFIG_SND_AZT2320 is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_DT019X is not set
# CONFIG_SND_ES968 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_MIRO is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set
# CONFIG_SND_WAVEFRONT is not set
#
# PCI devices
#
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
CONFIG_SND_ALI5451=y
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_CS5535AUDIO is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_HDA_INTEL is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_AC97_POWER_SAVE is not set
#
# USB devices
#
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set
# CONFIG_SND_USB_CAIAQ is not set
#
# PCMCIA devices
#
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_PDAUDIOCF is not set
#
# System on Chip audio support
#
# CONFIG_SND_SOC is not set
#
# SoC Audio support for SuperH
#
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
CONFIG_AC97_BUS=y
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
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_DEVICE_CLASS=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_PERSIST is not set
# CONFIG_USB_OTG is not set
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_SPLIT_ISO=y
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
CONFIG_USB_EHCI_TT_NEWSCHED=y
# CONFIG_USB_EHCI_FSL is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=y
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#
#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_KARMA 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=y
#
# USB port drivers
#
# CONFIG_USB_USS720 is not set
#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
# CONFIG_USB_SERIAL_GENERIC is not set
CONFIG_USB_SERIAL_AIRCABLE=m
CONFIG_USB_SERIAL_AIRPRIME=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CP2101=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_FUNSOFT=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
# CONFIG_USB_SERIAL_KEYSPAN_MPR is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28XA is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28XB is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA18X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19W is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19QW is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19QI is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA49W is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA49WLC is not set
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_MOS7720=m
CONFIG_USB_SERIAL_MOS7840=m
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
# CONFIG_USB_SERIAL_OTI6858 is not set
CONFIG_USB_SERIAL_HP4X=m
CONFIG_USB_SERIAL_SAFE=m
# CONFIG_USB_SERIAL_SAFE_PADDED is not set
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_SERIAL_DEBUG=m
CONFIG_USB_EZUSB=y
#
# 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_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GOTEMP is not set
#
# USB DSL modem support
#
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
CONFIG_MMC=m
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set
# CONFIG_MMC_PASSWORDS is not set
#
# MMC/SD Card Drivers
#
CONFIG_MMC_BLOCK=m
CONFIG_MMC_BLOCK_BOUNCE=y
#
# MMC/SD Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
CONFIG_MMC_WBSD=m
# CONFIG_MMC_TIFM_SD is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=m
#
# LED drivers
#
#
# LED Triggers
#
# CONFIG_LEDS_TRIGGERS is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC=y
#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_MM_EDAC=y
# CONFIG_EDAC_AMD76X is not set
# CONFIG_EDAC_E7XXX is not set
# CONFIG_EDAC_E752X is not set
# CONFIG_EDAC_I82443BXGX is not set
# CONFIG_EDAC_I82875P is not set
# CONFIG_EDAC_I3000 is not set
# CONFIG_EDAC_I82860 is not set
# CONFIG_EDAC_R82600 is not set
# CONFIG_EDAC_I5000 is not set
#
# Real Time Clock
#
# CONFIG_RTC_CLASS is not set
#
# DMA Engine support
#
# CONFIG_DMA_ENGINE is not set
#
# DMA Clients
#
#
# DMA Devices
#
CONFIG_AUXDISPLAY=y
# CONFIG_KS0108 is not set
CONFIG_VIRTUALIZATION=y
# CONFIG_KVM is not set
#
# Userspace I/O
#
# 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=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
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 is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
# CONFIG_FUSE_FS is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=1250
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-2"
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
# CONFIG_CONFIGFS_FS is not set
#
# Layered filesystems
#
# CONFIG_UNION_FS is not set
#
# Miscellaneous filesystems
#
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
# 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_NFSD_TCP=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_BIND34 is not set
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=y
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp1250"
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
# CONFIG_9P_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-2"
CONFIG_NLS_CODEPAGE_437=m
# 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=y
# 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=m
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=y
# 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
#
# Distributed Lock Manager
#
# CONFIG_DLM is not set
CONFIG_INSTRUMENTATION=y
# CONFIG_PROFILING is not set
# CONFIG_KPROBES is not set
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_PAGE_OWNER is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_SHIRQ=y
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_LOCK_ALLOC=y
CONFIG_PROVE_LOCKING=y
CONFIG_LOCKDEP=y
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_LOCKDEP is not set
CONFIG_TRACE_IRQFLAGS=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_DEBUG_LOCKING_API_SELFTESTS=y
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
CONFIG_DEBUG_VM=y
# CONFIG_DEBUG_LIST is not set
CONFIG_FRAME_POINTER=y
CONFIG_UNWIND_INFO=y
CONFIG_STACK_UNWIND=y
# CONFIG_PROFILE_LIKELY is not set
CONFIG_FORCED_INLINING=y
# CONFIG_DEBUG_SYNCHRO_TEST is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
#
# Page alloc debug is incompatible with Software Suspend on i386
#
# CONFIG_DEBUG_RODATA is not set
# CONFIG_4KSTACKS is not set
CONFIG_DOUBLEFAULT=y
#
# 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=m
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_HASH=m
CONFIG_CRYPTO_MANAGER=m
CONFIG_CRYPTO_HMAC=m
CONFIG_CRYPTO_XCBC=m
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=m
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_GF128MUL=m
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_LRW=m
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_FCRYPT=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_TWOFISH_586=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_CAMELLIA=m
CONFIG_CRYPTO_TEST=m
CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO_DEV_PADLOCK=m
CONFIG_CRYPTO_DEV_PADLOCK_AES=m
CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
CONFIG_CRYPTO_DEV_GEODE=m
#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=m
# CONFIG_CRC16 is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_KTIME_SCALAR=y
[-- Attachment #3: menu.png --]
[-- Type: image/png, Size: 11332 bytes --]
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1
2007-06-06 19:32 ` 2.6.22-rc4-mm1 Mariusz Kozlowski
@ 2007-06-06 20:24 ` Andrew Morton
2007-06-06 20:52 ` 2.6.22-rc4-mm1 Fabio Comolli
2007-06-06 21:28 ` 2.6.22-rc4-mm1 Herbert Xu
0 siblings, 2 replies; 120+ messages in thread
From: Andrew Morton @ 2007-06-06 20:24 UTC (permalink / raw)
To: Mariusz Kozlowski; +Cc: linux-kernel, Herbert Xu
On Wed, 6 Jun 2007 21:32:36 +0200 Mariusz Kozlowski <m.kozlowski@tuxland.pl> wrote:
> Hello,
>
> This is from my P4 sony vaio laptop.
>
> These warnings still there:
>
> drivers/input/keyboard/Kconfig:170:warning: 'select' used by config symbol 'KEYBOARD_ATARI' refers to undefined symbol 'ATARI_KBD_CORE'
> drivers/input/mouse/Kconfig:182:warning: 'select' used by config symbol 'MOUSE_ATARI' refers to undefined symbol 'ATARI_KBD_CORE'
> sound/soc/sh/Kconfig:6:warning: 'select' used by config symbol 'SND_SOC_PCM_SH7760' refers to undefined symbol 'SH_DMABRG'
Yeah, people keep adding those and then never fixing them. I've given up
and I just ignore them.
> A hwmon related build error:
>
> Building modules, stage 2.
> MODPOST 187 modules
> ERROR: "input_register_polled_device" [drivers/hwmon/hdaps.ko] undefined!
> ERROR: "input_allocate_polled_device" [drivers/hwmon/hdaps.ko] undefined!
> ERROR: "input_free_polled_device" [drivers/hwmon/hdaps.ko] undefined!
> ERROR: "input_unregister_polled_device" [drivers/hwmon/hdaps.ko] undefined!
> ERROR: "input_register_polled_device" [drivers/hwmon/applesmc.ko] undefined!
> ERROR: "input_allocate_polled_device" [drivers/hwmon/applesmc.ko] undefined!
> ERROR: "input_free_polled_device" [drivers/hwmon/applesmc.ko] undefined!
> ERROR: "input_unregister_polled_device" [drivers/hwmon/applesmc.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
Yes, this is being argued on the lm-sensors list, of all places. For now
you'll need to manually set CONFIG_INPUT_POLLDEV, I assume.
> And for some reason the whole Cryptographic API is under the main level of menu
> (please find .config and menu.png attached).
err, yes. git-cryptodev.patch did that. Herbert is being immodest ;)
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 20:24 ` 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-06 20:52 ` Fabio Comolli
2007-06-06 21:28 ` 2.6.22-rc4-mm1 Herbert Xu
1 sibling, 0 replies; 120+ messages in thread
From: Fabio Comolli @ 2007-06-06 20:52 UTC (permalink / raw)
To: Andrew Morton; +Cc: Mariusz Kozlowski, linux-kernel, Herbert Xu
Hi
On 6/6/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Wed, 6 Jun 2007 21:32:36 +0200 Mariusz Kozlowski <m.kozlowski@tuxland.pl> wrote:
>
> > Hello,
> >
> > This is from my P4 sony vaio laptop.
> >
> > These warnings still there:
> >
> > drivers/input/keyboard/Kconfig:170:warning: 'select' used by config symbol 'KEYBOARD_ATARI' refers to undefined symbol 'ATARI_KBD_CORE'
> > drivers/input/mouse/Kconfig:182:warning: 'select' used by config symbol 'MOUSE_ATARI' refers to undefined symbol 'ATARI_KBD_CORE'
> > sound/soc/sh/Kconfig:6:warning: 'select' used by config symbol 'SND_SOC_PCM_SH7760' refers to undefined symbol 'SH_DMABRG'
>
> Yeah, people keep adding those and then never fixing them. I've given up
> and I just ignore them.
Maybe it is because ATARI_KBD_CORE is defined only in arch/m68k.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 20:24 ` 2.6.22-rc4-mm1 Andrew Morton
2007-06-06 20:52 ` 2.6.22-rc4-mm1 Fabio Comolli
@ 2007-06-06 21:28 ` Herbert Xu
2007-06-06 23:42 ` 2.6.22-rc4-mm1 Andrew Morton
1 sibling, 1 reply; 120+ messages in thread
From: Herbert Xu @ 2007-06-06 21:28 UTC (permalink / raw)
To: Andrew Morton; +Cc: Mariusz Kozlowski, linux-kernel, Jan Engelhardt
On Wed, Jun 06, 2007 at 01:24:39PM -0700, Andrew Morton wrote:
>
> > And for some reason the whole Cryptographic API is under the main level of menu
> > (please find .config and menu.png attached).
>
> err, yes. git-cryptodev.patch did that. Herbert is being immodest ;)
Is it this patch? If so then you sent to it me :)
Should I drop it?
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
commit a85e40c4a0d4fd87e3f9449faac98db0d7d6ac78
Author: Jan Engelhardt <jengelh@gmx.de>
Date: Fri May 18 15:11:01 2007 +1000
[CRYPTO] Kconfig: Use menuconfig objects
Use menuconfigs instead of menus, so the whole menu can be disabled at once
instead of going through all options.
Signed-off-by: Jan Engelhardt <jengelh@gmx.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
a85e40c4a0d4fd87e3f9449faac98db0d7d6ac78
diff --git a/crypto/Kconfig b/crypto/Kconfig
index 4ca0ab3..935301e 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
@@ -2,9 +2,7 @@
# Cryptographic API Configuration
#
-menu "Cryptographic options"
-
-config CRYPTO
+menuconfig CRYPTO
bool "Cryptographic API"
help
This option provides the core Cryptographic API.
@@ -463,5 +461,3 @@ config CRYPTO_TEST
source "drivers/crypto/Kconfig"
endif # if CRYPTO
-
-endmenu
^ permalink raw reply related [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1
2007-06-06 21:28 ` 2.6.22-rc4-mm1 Herbert Xu
@ 2007-06-06 23:42 ` Andrew Morton
2007-06-07 6:54 ` 2.6.22-rc4-mm1 Jan Engelhardt
0 siblings, 1 reply; 120+ messages in thread
From: Andrew Morton @ 2007-06-06 23:42 UTC (permalink / raw)
To: Herbert Xu; +Cc: Mariusz Kozlowski, linux-kernel, Jan Engelhardt
On Thu, 7 Jun 2007 07:28:31 +1000 Herbert Xu <herbert@gondor.apana.org.au> wrote:
> On Wed, Jun 06, 2007 at 01:24:39PM -0700, Andrew Morton wrote:
> >
> > > And for some reason the whole Cryptographic API is under the main level of menu
> > > (please find .config and menu.png attached).
> >
> > err, yes. git-cryptodev.patch did that. Herbert is being immodest ;)
>
> Is it this patch?
looks like it.
> If so then you sent to it me :)
You merged it ;)
> Should I drop it?
Sure, Jan will fix it up, I assume. I might have broken it while repairing
the reject storm which occurred when that durned HAS_IOMEM thing went in
all over the tree.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 23:42 ` 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-07 6:54 ` Jan Engelhardt
2007-06-07 7:01 ` 2.6.22-rc4-mm1 Herbert Xu
2007-06-07 19:27 ` 2.6.22-rc4-mm1 Adrian Bunk
0 siblings, 2 replies; 120+ messages in thread
From: Jan Engelhardt @ 2007-06-07 6:54 UTC (permalink / raw)
To: Andrew Morton; +Cc: Herbert Xu, Mariusz Kozlowski, linux-kernel
On Jun 6 2007 16:42, Andrew Morton wrote:
>> If so then you sent to it me :)
>
>You merged it ;)
>
>> Should I drop it?
>
>Sure, Jan will fix it up, I assume. I might have broken it while repairing
>the reject storm which occurred when that durned HAS_IOMEM thing went in
>all over the tree.
/me points at Herbert
Andrew would not add options between the "menuconfig CRYPTO" and
the "if CRYPTO" line... :)
Jan
===
Unbreak the crypto menu breakage.
Signed-off-by: Jan Engelhardt <jengelh@gmx.de>
---
crypto/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: linux-2.6.22-rc4/crypto/Kconfig
===================================================================
--- linux-2.6.22-rc4.orig/crypto/Kconfig
+++ linux-2.6.22-rc4/crypto/Kconfig
@@ -7,6 +7,8 @@ menuconfig CRYPTO
help
This option provides the core Cryptographic API.
+if CRYPTO
+
#
# Generic algorithms support
#
@@ -18,8 +20,6 @@ config XOR_BLOCKS
#
source "crypto/async_tx/Kconfig"
-if CRYPTO
-
config CRYPTO_ALGAPI
tristate
help
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 6:54 ` 2.6.22-rc4-mm1 Jan Engelhardt
@ 2007-06-07 7:01 ` Herbert Xu
2007-06-07 7:12 ` 2.6.22-rc4-mm1 Andrew Morton
2007-06-07 19:27 ` 2.6.22-rc4-mm1 Adrian Bunk
1 sibling, 1 reply; 120+ messages in thread
From: Herbert Xu @ 2007-06-07 7:01 UTC (permalink / raw)
To: Jan Engelhardt; +Cc: Andrew Morton, Mariusz Kozlowski, linux-kernel
On Thu, Jun 07, 2007 at 08:54:50AM +0200, Jan Engelhardt wrote:
>
> /me points at Herbert
> Andrew would not add options between the "menuconfig CRYPTO" and
> the "if CRYPTO" line... :)
Actually this patch is not even in my tree :)
> Index: linux-2.6.22-rc4/crypto/Kconfig
> ===================================================================
> --- linux-2.6.22-rc4.orig/crypto/Kconfig
> +++ linux-2.6.22-rc4/crypto/Kconfig
> @@ -7,6 +7,8 @@ menuconfig CRYPTO
> help
> This option provides the core Cryptographic API.
>
> +if CRYPTO
> +
> #
> # Generic algorithms support
> #
> @@ -18,8 +20,6 @@ config XOR_BLOCKS
> #
> source "crypto/async_tx/Kconfig"
Andrew, do you want me to pick the async_tx stuff up instead?
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1
2007-06-07 7:01 ` 2.6.22-rc4-mm1 Herbert Xu
@ 2007-06-07 7:12 ` Andrew Morton
2007-06-11 5:01 ` 2.6.22-rc4-mm1 Dan Williams
0 siblings, 1 reply; 120+ messages in thread
From: Andrew Morton @ 2007-06-07 7:12 UTC (permalink / raw)
To: Herbert Xu; +Cc: Jan Engelhardt, Mariusz Kozlowski, linux-kernel
On Thu, 7 Jun 2007 17:01:08 +1000 Herbert Xu <herbert@gondor.apana.org.au> wrote:
> On Thu, Jun 07, 2007 at 08:54:50AM +0200, Jan Engelhardt wrote:
> >
> > /me points at Herbert
> > Andrew would not add options between the "menuconfig CRYPTO" and
> > the "if CRYPTO" line... :)
>
> Actually this patch is not even in my tree :)
uh, OK, sorry.
> > Index: linux-2.6.22-rc4/crypto/Kconfig
> > ===================================================================
> > --- linux-2.6.22-rc4.orig/crypto/Kconfig
> > +++ linux-2.6.22-rc4/crypto/Kconfig
> > @@ -7,6 +7,8 @@ menuconfig CRYPTO
> > help
> > This option provides the core Cryptographic API.
> >
> > +if CRYPTO
> > +
> > #
> > # Generic algorithms support
> > #
> > @@ -18,8 +20,6 @@ config XOR_BLOCKS
> > #
> > source "crypto/async_tx/Kconfig"
>
> Andrew, do you want me to pick the async_tx stuff up instead?
>
I wouldn't recommend it. It's an ongoing source of bustage frankly, has a
habit of getting unpleasantly tangled with git-ioat.patch and afaik is
still awaiting a go-ahead from Neil.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 7:12 ` 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-11 5:01 ` Dan Williams
2007-06-11 6:26 ` 2.6.22-rc4-mm1 Andrew Morton
2007-06-11 6:51 ` 2.6.22-rc4-mm1 Paul Mundt
0 siblings, 2 replies; 120+ messages in thread
From: Dan Williams @ 2007-06-11 5:01 UTC (permalink / raw)
To: Andrew Morton
Cc: Herbert Xu, Jan Engelhardt, Mariusz Kozlowski, linux-kernel,
Neil Brown, Leech, Christopher, Jeff Garzik, davem, Wolfgang Denk
On 6/7/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Thu, 7 Jun 2007 17:01:08 +1000 Herbert Xu <herbert@gondor.apana.org.au> wrote:
>
> > On Thu, Jun 07, 2007 at 08:54:50AM +0200, Jan Engelhardt wrote:
> > >
> > > /me points at Herbert
> > > Andrew would not add options between the "menuconfig CRYPTO" and
> > > the "if CRYPTO" line... :)
> >
> > Actually this patch is not even in my tree :)
>
> uh, OK, sorry.
>
> > > Index: linux-2.6.22-rc4/crypto/Kconfig
> > > ===================================================================
> > > --- linux-2.6.22-rc4.orig/crypto/Kconfig
> > > +++ linux-2.6.22-rc4/crypto/Kconfig
> > > @@ -7,6 +7,8 @@ menuconfig CRYPTO
> > > help
> > > This option provides the core Cryptographic API.
> > >
> > > +if CRYPTO
> > > +
> > > #
> > > # Generic algorithms support
> > > #
> > > @@ -18,8 +20,6 @@ config XOR_BLOCKS
> > > #
> > > source "crypto/async_tx/Kconfig"
> >
> > Andrew, do you want me to pick the async_tx stuff up instead?
> >
>
It would be very helpful to have a clear merge path for dmaengine
changes and the async offload api. Neil has been extremely helpful
reviewing the raid specific changes, and I received his "Acked-by" for
the changes to MD[1]. However I have thus far been unable to attract
someone to 'ack/nak' the async_tx api and the changes to drivers/dma/
[2]. Jeff commented on an early revision...
I have recently gravitated to Herbert and the crypto directory since
async_tx and crypto have some structural similarities [3].
> I wouldn't recommend it. It's an ongoing source of bustage frankly, has a
> habit of getting unpleasantly tangled with git-ioat.patch and afaik is
> still awaiting a go-ahead from Neil.
>
Sorry, the crypto/Kconfig bustage was a goof on my part as I moved the
async_tx files from drivers/dma/, to the top-level directory, and
finally to crypto/. Hopefully these recent build breakages I have
caused in -mm have not put the series in too negative a light...
I was hoping the git-ioat.patch situation would be solved by me
rebasing my series on a version of mainline with Chris' changes
merged, but his attempts over the past two merge windows were ignored.
Should my series wait outside of -mm until git-ioat.patch makes
forward progress?
Overall, I feel that async_tx is perhaps justifiably receiving the
silent treatment because offload engines are not a mainstream
occurrence. Currently only people with an Xscale IOP or a PPC 440spe
[4] will notice that mainline lacks support for all the features of
their platform. I see async_tx as a nod to the embedded space where
offload engines act to make up for the absence of multi-Ghz CPUs with
streaming SIMD instructions.
Herbert's offer is greatly appreciated as it will give guidance to the
parts of the series outside of Neil's purview.
Regards,
Dan
[1]: The ack from Neil was in an offlist message for the MD specific
portion of the series
[2]: I asked DaveM and netdev to take a look at the two patches in the
series that change drivers/dma/ and net/core/dev.c since that was the
original merge path for I/OAT and dmaengine
[3]: async_tx is similar to crypto in that they both provide a library
of memory transforms that can in some cases be carried out by
hardware.
[4]: async_tx has attracted at least one other developer that I know
about to write a driver for their engines:
http://marc.info/?l=linux-raid&m=117400143317440&w=2
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-11 5:01 ` 2.6.22-rc4-mm1 Dan Williams
@ 2007-06-11 6:26 ` Andrew Morton
2007-06-11 6:51 ` 2.6.22-rc4-mm1 Paul Mundt
1 sibling, 0 replies; 120+ messages in thread
From: Andrew Morton @ 2007-06-11 6:26 UTC (permalink / raw)
To: Dan Williams
Cc: Herbert Xu, Jan Engelhardt, Mariusz Kozlowski, linux-kernel,
Neil Brown, Leech, Christopher, Jeff Garzik, davem, Wolfgang Denk
On Sun, 10 Jun 2007 22:01:34 -0700 "Dan Williams" <dan.j.williams@intel.com> wrote:
> It would be very helpful to have a clear merge path for dmaengine
> changes and the async offload api.
Yes, this needs some attention.
I'd suggest that you prepare a standalone tree for Linus to pull and we aim at
asking him to pull that for 2.6.23-rc1.
In the meanwhile I'd suggest that you get the core patch(es) out
onto the relevant lists again and cc'ed to the relevant maintainers.
Of course, good changelogging and commenting makes the review a) more
effective, b) more likely to happen and c) less work for reviewers. The
changelog you have for 7556477664edcbe1c9a2fdf60edddfd8455d198b is nice,
but it's awfully short for a 1/4MB patch. It tells us at a high level what
the code does, but it has nothing to say about how it does it: a high-level
design description, of you will.
Put yourself in the position of an experienced kernel developer who doesn't
know this code, and who doesn't know the hardware. What can you do to make
their review easier and more effective?
So. Please have a think about what you can do there, and also see what can
be done about the 312 warnings which
perl scripts/checkpatch.pl patches/git-md-accel.patch
emits. Then send 'em all out again (say, a week from now) and let's all just dig
in and make this thing happen?
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-11 5:01 ` 2.6.22-rc4-mm1 Dan Williams
2007-06-11 6:26 ` 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-11 6:51 ` Paul Mundt
1 sibling, 0 replies; 120+ messages in thread
From: Paul Mundt @ 2007-06-11 6:51 UTC (permalink / raw)
To: Dan Williams
Cc: Andrew Morton, Herbert Xu, Jan Engelhardt, Mariusz Kozlowski,
linux-kernel, Neil Brown, Leech, Christopher, Jeff Garzik, davem,
Wolfgang Denk
On Sun, Jun 10, 2007 at 10:01:34PM -0700, Dan Williams wrote:
> Overall, I feel that async_tx is perhaps justifiably receiving the
> silent treatment because offload engines are not a mainstream
> occurrence. Currently only people with an Xscale IOP or a PPC 440spe
> [4] will notice that mainline lacks support for all the features of
> their platform. I see async_tx as a nod to the embedded space where
> offload engines act to make up for the absence of multi-Ghz CPUs with
> streaming SIMD instructions.
>
For what it's worth, I'm planning on tying in the SH DMA stuff to
the dmaengine code, as the async_tx stuff certainly has quite a few bits
of interest. This is probably something I won't get around to for 2.6.23
though, due to time constraints.
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-07 6:54 ` 2.6.22-rc4-mm1 Jan Engelhardt
2007-06-07 7:01 ` 2.6.22-rc4-mm1 Herbert Xu
@ 2007-06-07 19:27 ` Adrian Bunk
1 sibling, 0 replies; 120+ messages in thread
From: Adrian Bunk @ 2007-06-07 19:27 UTC (permalink / raw)
To: Jan Engelhardt; +Cc: Andrew Morton, Herbert Xu, Mariusz Kozlowski, linux-kernel
On Thu, Jun 07, 2007 at 08:54:50AM +0200, Jan Engelhardt wrote:
>
> On Jun 6 2007 16:42, Andrew Morton wrote:
>
> >> If so then you sent to it me :)
> >
> >You merged it ;)
> >
> >> Should I drop it?
> >
> >Sure, Jan will fix it up, I assume. I might have broken it while repairing
> >the reject storm which occurred when that durned HAS_IOMEM thing went in
> >all over the tree.
>
> /me points at Herbert
> Andrew would not add options between the "menuconfig CRYPTO" and
> the "if CRYPTO" line... :)
>
>
> Jan
>
>
> ===
>
> Unbreak the crypto menu breakage.
>
> Signed-off-by: Jan Engelhardt <jengelh@gmx.de>
>
> ---
> crypto/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> Index: linux-2.6.22-rc4/crypto/Kconfig
> ===================================================================
> --- linux-2.6.22-rc4.orig/crypto/Kconfig
> +++ linux-2.6.22-rc4/crypto/Kconfig
> @@ -7,6 +7,8 @@ menuconfig CRYPTO
> help
> This option provides the core Cryptographic API.
>
> +if CRYPTO
> +
> #
> # Generic algorithms support
> #
> @@ -18,8 +20,6 @@ config XOR_BLOCKS
> #
> source "crypto/async_tx/Kconfig"
>
> -if CRYPTO
> -
> config CRYPTO_ALGAPI
> tristate
> help
This seems to be buggy since the options in crypto/async_tx/Kconfig do
not depend on the crypto subsystem (and they are not user visible
options that get select'ed).
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
` (12 preceding siblings ...)
2007-06-06 19:32 ` 2.6.22-rc4-mm1 Mariusz Kozlowski
@ 2007-06-06 20:58 ` Grant Wilson
2007-06-06 23:37 ` 2.6.22-rc4-mm1 Andrew Morton
2007-06-07 7:53 ` [2.6.22-rc4-mm1] ACPI Exception (processor_throttling) Maciej Rutecki
2007-06-07 12:47 ` 2.6.22-rc4-mm1 KAMEZAWA Hiroyuki
15 siblings, 1 reply; 120+ messages in thread
From: Grant Wilson @ 2007-06-06 20:58 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Wednesday 06 June 2007 10:07:37 Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
Patch 'usb-try-to-debug-bug-8561' triggers when I plug in a usb flash drive:
[10998.881000] usb 1-10: new high speed USB device using ehci_hcd and address 3
[10999.001000] usb 1-10: new device found, idVendor=13fe, idProduct=1a00
[10999.002000] usb 1-10: new device strings: Mfr=1, Product=2, SerialNumber=3
[10999.016000] usb 1-10: Product: USB DISK 2.0
[10999.025000] usb 1-10: Manufacturer:
[10999.033000] usb 1-10: SerialNumber: 07720947018D
[10999.034000] usb 1-10: configuration #1 chosen from 1 choice
[10999.047000] scsi8 : SCSI emulation for USB Mass Storage devices
[11004.055000] WARNING: at drivers/usb/core/urb.c:293 usb_submit_urb()
[11004.055000]
[11004.055000] Call Trace:
[11004.055000] [<ffffffff8020d30f>] dump_trace+0x43f/0x480
[11004.055000] [<ffffffff8020d393>] show_trace+0x43/0x70
[11004.055000] [<ffffffff8020d3d5>] dump_stack+0x15/0x20
[11004.055000] [<ffffffff804b4314>] usb_submit_urb+0x224/0x240
[11004.055000] [<ffffffff804b5ff5>] usb_sg_wait+0xd5/0x180
[11004.055000] [<ffffffff804cf464>] usb_stor_bulk_transfer_sg+0xc4/0x120
[11004.055000] [<ffffffff804cf611>] usb_stor_Bulk_transport+0x151/0x2e0
[11004.055000] [<ffffffff804cfb57>] usb_stor_invoke_transport+0x37/0x380
[11004.055000] [<ffffffff804ce9f9>] usb_stor_transparent_scsi_command+0x9/0x10
[11004.055000] [<ffffffff804d0aea>] usb_stor_control_thread+0x18a/0x230
[11004.055000] [<ffffffff8024927d>] kthread+0x4d/0x80
[11004.055000] [<ffffffff8020c868>] child_rip+0xa/0x12
Cheers,
Grant
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1
2007-06-06 20:58 ` 2.6.22-rc4-mm1 Grant Wilson
@ 2007-06-06 23:37 ` Andrew Morton
2007-06-07 14:53 ` 2.6.22-rc4-mm1 Alan Stern
0 siblings, 1 reply; 120+ messages in thread
From: Andrew Morton @ 2007-06-06 23:37 UTC (permalink / raw)
To: Grant Wilson; +Cc: linux-kernel, Alan Stern, linux-usb-devel
On Wed, 6 Jun 2007 21:58:38 +0100 Grant Wilson <gww@swandive.no-ip.com> wrote:
> On Wednesday 06 June 2007 10:07:37 Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
>
> Patch 'usb-try-to-debug-bug-8561' triggers when I plug in a usb flash drive:
Cool, thanks.
> [10998.881000] usb 1-10: new high speed USB device using ehci_hcd and address 3
> [10999.001000] usb 1-10: new device found, idVendor=13fe, idProduct=1a00
> [10999.002000] usb 1-10: new device strings: Mfr=1, Product=2, SerialNumber=3
> [10999.016000] usb 1-10: Product: USB DISK 2.0
> [10999.025000] usb 1-10: Manufacturer:
> [10999.033000] usb 1-10: SerialNumber: 07720947018D
> [10999.034000] usb 1-10: configuration #1 chosen from 1 choice
> [10999.047000] scsi8 : SCSI emulation for USB Mass Storage devices
> [11004.055000] WARNING: at drivers/usb/core/urb.c:293 usb_submit_urb()
> [11004.055000]
> [11004.055000] Call Trace:
> [11004.055000] [<ffffffff8020d30f>] dump_trace+0x43f/0x480
> [11004.055000] [<ffffffff8020d393>] show_trace+0x43/0x70
> [11004.055000] [<ffffffff8020d3d5>] dump_stack+0x15/0x20
> [11004.055000] [<ffffffff804b4314>] usb_submit_urb+0x224/0x240
> [11004.055000] [<ffffffff804b5ff5>] usb_sg_wait+0xd5/0x180
> [11004.055000] [<ffffffff804cf464>] usb_stor_bulk_transfer_sg+0xc4/0x120
> [11004.055000] [<ffffffff804cf611>] usb_stor_Bulk_transport+0x151/0x2e0
> [11004.055000] [<ffffffff804cfb57>] usb_stor_invoke_transport+0x37/0x380
> [11004.055000] [<ffffffff804ce9f9>] usb_stor_transparent_scsi_command+0x9/0x10
> [11004.055000] [<ffffffff804d0aea>] usb_stor_control_thread+0x18a/0x230
> [11004.055000] [<ffffffff8024927d>] kthread+0x4d/0x80
> [11004.055000] [<ffffffff8020c868>] child_rip+0xa/0x12
>
Alan, you got a bite - reel her in!
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 23:37 ` 2.6.22-rc4-mm1 Andrew Morton
@ 2007-06-07 14:53 ` Alan Stern
2007-06-08 4:23 ` [linux-usb-devel] 2.6.22-rc4-mm1 Greg KH
0 siblings, 1 reply; 120+ messages in thread
From: Alan Stern @ 2007-06-07 14:53 UTC (permalink / raw)
To: Grant Wilson, Andrew Morton; +Cc: Kernel development list, USB development list
On Wed, 6 Jun 2007, Andrew Morton wrote:
> On Wed, 6 Jun 2007 21:58:38 +0100 Grant Wilson <gww@swandive.no-ip.com> wrote:
>
> > On Wednesday 06 June 2007 10:07:37 Andrew Morton wrote:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
> >
> > Patch 'usb-try-to-debug-bug-8561' triggers when I plug in a usb flash drive:
>
> Cool, thanks.
>
> > [10998.881000] usb 1-10: new high speed USB device using ehci_hcd and address 3
> > [10999.001000] usb 1-10: new device found, idVendor=13fe, idProduct=1a00
> > [10999.002000] usb 1-10: new device strings: Mfr=1, Product=2, SerialNumber=3
> > [10999.016000] usb 1-10: Product: USB DISK 2.0
> > [10999.025000] usb 1-10: Manufacturer:
> > [10999.033000] usb 1-10: SerialNumber: 07720947018D
> > [10999.034000] usb 1-10: configuration #1 chosen from 1 choice
> > [10999.047000] scsi8 : SCSI emulation for USB Mass Storage devices
> > [11004.055000] WARNING: at drivers/usb/core/urb.c:293 usb_submit_urb()
> > [11004.055000]
> > [11004.055000] Call Trace:
> > [11004.055000] [<ffffffff8020d30f>] dump_trace+0x43f/0x480
> > [11004.055000] [<ffffffff8020d393>] show_trace+0x43/0x70
> > [11004.055000] [<ffffffff8020d3d5>] dump_stack+0x15/0x20
> > [11004.055000] [<ffffffff804b4314>] usb_submit_urb+0x224/0x240
> > [11004.055000] [<ffffffff804b5ff5>] usb_sg_wait+0xd5/0x180
> > [11004.055000] [<ffffffff804cf464>] usb_stor_bulk_transfer_sg+0xc4/0x120
> > [11004.055000] [<ffffffff804cf611>] usb_stor_Bulk_transport+0x151/0x2e0
> > [11004.055000] [<ffffffff804cfb57>] usb_stor_invoke_transport+0x37/0x380
> > [11004.055000] [<ffffffff804ce9f9>] usb_stor_transparent_scsi_command+0x9/0x10
> > [11004.055000] [<ffffffff804d0aea>] usb_stor_control_thread+0x18a/0x230
> > [11004.055000] [<ffffffff8024927d>] kthread+0x4d/0x80
> > [11004.055000] [<ffffffff8020c868>] child_rip+0xa/0x12
> >
>
> Alan, you got a bite - reel her in!
Thanks for forwarding the message. Unforunately it's a false alarm.
As mentioned in the original patch, the test it uses isn't precise.
To tell you the truth, I rather think there's not much point in keeping
usb-try-to-debug-bug-8561.patch around. Anything seriously wrong that
it could catch ought to have shown up long ago. And it is now clear
that bug 8561 has nothing to do with this; it is a programming error
common to many of the USB serial drivers. (Still waiting to hear back
from Paulo Pereira whether the fix to the USB Option driver works...)
My vote goes toward reverting usb-try-to-debug-bug-8561.patch.
However just to be thorough, for anyone wants to keep it here's an
untested patch to remove those false alarms.
Alan Stern
---------------------------------
Remove some false alarms generated by usb-try-to-debug-bug-8561.patch.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
---
Index: usb-2.6/drivers/usb/core/message.c
===================================================================
--- usb-2.6.orig/drivers/usb/core/message.c
+++ usb-2.6/drivers/usb/core/message.c
@@ -404,8 +404,6 @@ int usb_sg_init (
io->urbs [i]->complete = sg_complete;
io->urbs [i]->context = io;
- io->urbs [i]->status = -EINPROGRESS;
- io->urbs [i]->actual_length = 0;
/*
* Some systems need to revert to PIO when DMA is temporarily
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: [linux-usb-devel] 2.6.22-rc4-mm1
2007-06-07 14:53 ` 2.6.22-rc4-mm1 Alan Stern
@ 2007-06-08 4:23 ` Greg KH
2007-06-08 14:06 ` Alan Stern
0 siblings, 1 reply; 120+ messages in thread
From: Greg KH @ 2007-06-08 4:23 UTC (permalink / raw)
To: Alan Stern
Cc: Grant Wilson, Andrew Morton, Kernel development list,
USB development list
On Thu, Jun 07, 2007 at 10:53:29AM -0400, Alan Stern wrote:
> To tell you the truth, I rather think there's not much point in keeping
> usb-try-to-debug-bug-8561.patch around. Anything seriously wrong that
> it could catch ought to have shown up long ago. And it is now clear
> that bug 8561 has nothing to do with this; it is a programming error
> common to many of the USB serial drivers. (Still waiting to hear back
> from Paulo Pereira whether the fix to the USB Option driver works...)
What error in the usb-serial drivers are you speaking about?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: [linux-usb-devel] 2.6.22-rc4-mm1
2007-06-08 4:23 ` [linux-usb-devel] 2.6.22-rc4-mm1 Greg KH
@ 2007-06-08 14:06 ` Alan Stern
2007-06-08 18:47 ` Greg KH
0 siblings, 1 reply; 120+ messages in thread
From: Alan Stern @ 2007-06-08 14:06 UTC (permalink / raw)
To: Greg KH
Cc: Grant Wilson, Andrew Morton, Kernel development list,
USB development list
On Thu, 7 Jun 2007, Greg KH wrote:
> On Thu, Jun 07, 2007 at 10:53:29AM -0400, Alan Stern wrote:
> > To tell you the truth, I rather think there's not much point in keeping
> > usb-try-to-debug-bug-8561.patch around. Anything seriously wrong that
> > it could catch ought to have shown up long ago. And it is now clear
> > that bug 8561 has nothing to do with this; it is a programming error
> > common to many of the USB serial drivers. (Still waiting to hear back
> > from Paulo Pereira whether the fix to the USB Option driver works...)
>
> What error in the usb-serial drivers are you speaking about?
The one addressed by usb-option-fix-usage-of-urb-status-abuse.patch. I
thought it might be worthwhile to spend some time fixing all of these.
Here's a quick summary showing the extent of the problem (note that
not all the usages are in error):
$ grep EINPROGRESS drivers/usb/serial/*.c drivers/usb/misc/*.c
drivers/usb/serial/digi_acceleport.c:* return 256 when -EINPROGRESS is set, as the line discipline
drivers/usb/serial/digi_acceleport.c: while( oob_port->write_urb->status == -EINPROGRESS
drivers/usb/serial/digi_acceleport.c: while( (port->write_urb->status == -EINPROGRESS
drivers/usb/serial/digi_acceleport.c: while( oob_port->write_urb->status == -EINPROGRESS
drivers/usb/serial/digi_acceleport.c: if( port->write_urb->status == -EINPROGRESS
drivers/usb/serial/digi_acceleport.c: if( port->open_count && port->write_urb->status != -EINPROGRESS
drivers/usb/serial/digi_acceleport.c: if( port->write_urb->status == -EINPROGRESS
drivers/usb/serial/digi_acceleport.c: if( port->write_urb->status == -EINPROGRESS
drivers/usb/serial/empeg.c: if (write_urb_pool[i]->status != -EINPROGRESS) {
drivers/usb/serial/empeg.c: if (write_urb_pool[i]->status != -EINPROGRESS) {
drivers/usb/serial/empeg.c: if (write_urb_pool[i]->status == -EINPROGRESS) {
drivers/usb/serial/keyspan.c: if (this_urb->status == -EINPROGRESS) {
drivers/usb/serial/keyspan.c: } while (urb->status != -EINPROGRESS);
drivers/usb/serial/keyspan.c: if (this_urb->status != -EINPROGRESS)
drivers/usb/serial/keyspan.c: if (this_urb->status != -EINPROGRESS)
drivers/usb/serial/keyspan.c: if (urb && urb->status == -EINPROGRESS)
drivers/usb/serial/keyspan.c: /*while (p_priv->outcont_urb->status == -EINPROGRESS) {
drivers/usb/serial/keyspan.c: if (this_urb->status == -EINPROGRESS) {
drivers/usb/serial/keyspan.c: if (this_urb->status == -EINPROGRESS) {
drivers/usb/serial/keyspan.c: if (this_urb->status == -EINPROGRESS) {
drivers/usb/serial/keyspan.c: if (this_urb->status == -EINPROGRESS) {
drivers/usb/serial/keyspan.c: if (this_urb->status == -EINPROGRESS) {
drivers/usb/serial/keyspan_pda.c: * urb status is -EINPROGRESS, meaning it cannot write at the moment
drivers/usb/serial/keyspan_pda.c: again (the only sudden transition was the one from EINPROGRESS to
drivers/usb/serial/kl5kusb105.c: if (priv->write_urb_pool[i]->status != -EINPROGRESS) {
drivers/usb/serial/kl5kusb105.c: if (priv->write_urb_pool[i]->status == -EINPROGRESS) {
drivers/usb/serial/kl5kusb105.c: if (priv->write_urb_pool[i]->status != -EINPROGRESS) {
drivers/usb/serial/mos7720.c: if (port->read_urb->status != -EINPROGRESS) {
drivers/usb/serial/mos7720.c: if (mos7720_port->write_urb_pool[i] && mos7720_port->write_urb_pool[i]->status == -EINPROGRESS)
drivers/usb/serial/mos7720.c: if (mos7720_port->write_urb_pool[i] && mos7720_port->write_urb_pool[i]->status != -EINPROGRESS)
drivers/usb/serial/mos7720.c: if (mos7720_port->write_urb_pool[i] && mos7720_port->write_urb_pool[i]->status != -EINPROGRESS) {
drivers/usb/serial/mos7720.c: if (port->read_urb->status != -EINPROGRESS) {
drivers/usb/serial/mos7720.c: if(port->read_urb->status != -EINPROGRESS) {
drivers/usb/serial/mos7840.c: if (mos7840_port->read_urb->status != -EINPROGRESS) {
drivers/usb/serial/mos7840.c: if (mos7840_port->read_urb->status != -EINPROGRESS) {
drivers/usb/serial/sierra.c: if (this_urb->status == -EINPROGRESS) {
drivers/usb/serial/sierra.c: if (this_urb && this_urb->status != -EINPROGRESS)
drivers/usb/serial/sierra.c: if (this_urb && this_urb->status == -EINPROGRESS)
drivers/usb/misc/adutux.c: if (dev->interrupt_in_urb->status == -EINPROGRESS) {
drivers/usb/misc/adutux.c: if (should_submit && !dev->interrupt_in_urb->status==-EINPROGRESS) {
drivers/usb/misc/adutux.c: if (dev->interrupt_out_urb->status == -EINPROGRESS) {
drivers/usb/misc/auerswald.c: urb->status = -EINPROGRESS; /* usb_submit_urb does this, too */
drivers/usb/misc/auerswald.c: the result is 0 if the urb is cancelled, or -EINPROGRESS if
drivers/usb/misc/auerswald.c: if (urb->status != -EINPROGRESS) { /* No callback?!! */
drivers/usb/misc/auerswald.c:-EINPROGRESS during submission until end
drivers/usb/misc/usbtest.c: case -EINPROGRESS:
drivers/usb/misc/usbtest.c: if (!(retval == 0 || retval == -EINPROGRESS)) {
Alan Stern
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: [linux-usb-devel] 2.6.22-rc4-mm1
2007-06-08 14:06 ` Alan Stern
@ 2007-06-08 18:47 ` Greg KH
0 siblings, 0 replies; 120+ messages in thread
From: Greg KH @ 2007-06-08 18:47 UTC (permalink / raw)
To: Alan Stern
Cc: Grant Wilson, Andrew Morton, Kernel development list,
USB development list
On Fri, Jun 08, 2007 at 10:06:21AM -0400, Alan Stern wrote:
> On Thu, 7 Jun 2007, Greg KH wrote:
>
> > On Thu, Jun 07, 2007 at 10:53:29AM -0400, Alan Stern wrote:
> > > To tell you the truth, I rather think there's not much point in keeping
> > > usb-try-to-debug-bug-8561.patch around. Anything seriously wrong that
> > > it could catch ought to have shown up long ago. And it is now clear
> > > that bug 8561 has nothing to do with this; it is a programming error
> > > common to many of the USB serial drivers. (Still waiting to hear back
> > > from Paulo Pereira whether the fix to the USB Option driver works...)
> >
> > What error in the usb-serial drivers are you speaking about?
>
> The one addressed by usb-option-fix-usage-of-urb-status-abuse.patch. I
> thought it might be worthwhile to spend some time fixing all of these.
> Here's a quick summary showing the extent of the problem (note that
> not all the usages are in error):
Ah, yeah, I cleaned up a lot of them a while ago, but they keep creaping
back.
I _really_ think we need to just get rid of that field and pass the
status in the urb callback. That would fix this problem once and for
all.
But, from what I remember, the uhci host controller didn't make it easy
for me to acomplish this. Or it might have been another host
controller, can't remember anymore...
So, anyone looking to make up some patches that touch every USB driver
in the tree? I'd be glad to take them :)
thanks,
greg k-h
^ permalink raw reply [flat|nested] 120+ messages in thread
* [2.6.22-rc4-mm1] ACPI Exception (processor_throttling)
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
` (13 preceding siblings ...)
2007-06-06 20:58 ` 2.6.22-rc4-mm1 Grant Wilson
@ 2007-06-07 7:53 ` Maciej Rutecki
2007-06-07 8:51 ` Maciej Rutecki
2007-06-07 9:09 ` Luming Yu
2007-06-07 12:47 ` 2.6.22-rc4-mm1 KAMEZAWA Hiroyuki
15 siblings, 2 replies; 120+ messages in thread
From: Maciej Rutecki @ 2007-06-07 7:53 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-acpi, lenb
[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]
ACPI Exception (processor_throttling-0084): AE_NOT_FOUND, Evaluating
_PTC [20070126]
ACPI Exception (processor_throttling-0147): AE_NOT_FOUND, Evaluating
_TSS [20070126]
On 2.6.20.9 I don't have this exceptions.
Other problem:
2.6.22rc4-mm1:
rutek:/home/maciek# cat /proc/acpi/processor/CPU0/throttling
Naruszenie ochrony pamięci (segmentation fault)
compared to 2.6.20.9:
maciek@rutek:~$ cat /proc/acpi/processor/CPU0/throttling
state count: 8
active state: T0
states:
*T0: 00%
T1: 12%
T2: 25%
T3: 37%
T4: 50%
T5: 62%
T6: 75%
T7: 87%
Other info (2.6.22-rc4-mm1):
rutek:/home/maciek# ls /proc/acpi/processor/CPU0/
info limit power throttling
rutek:/home/maciek# cat /proc/acpi/processor/CPU0/info
processor id: 0
acpi id: 1
bus mastering control: yes
power management: yes
throttling control: yes
limit interface: yes
rutek:/home/maciek# cat /proc/acpi/processor/CPU0/limit
active limit: P0:T0
user limit: P0:T0
thermal limit: P0:T0
rutek:/home/maciek# cat /proc/acpi/processor/CPU0/power
active state: C0
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 8000 usec
states:
C1: type[C1] promotion[--] demotion[--]
latency[001] usage[00000000] duration[00000000000000000000]
C2: type[C2] promotion[--] demotion[--]
latency[001] usage[00000000] duration[00000000000000000000]
For CPU1 is similar.
config, dmesg, acpidump:
http://www.unixy.pl/maciek/download/kernel/2.6.22-rc4-mm1/
--
Maciej Rutecki
http://www.maciek.unixy.pl
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3265 bytes --]
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: [2.6.22-rc4-mm1] ACPI Exception (processor_throttling)
2007-06-07 7:53 ` [2.6.22-rc4-mm1] ACPI Exception (processor_throttling) Maciej Rutecki
@ 2007-06-07 8:51 ` Maciej Rutecki
2007-06-07 9:09 ` Luming Yu
1 sibling, 0 replies; 120+ messages in thread
From: Maciej Rutecki @ 2007-06-07 8:51 UTC (permalink / raw)
Cc: Andrew Morton, linux-kernel, linux-acpi, lenb
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
Maciej Rutecki pisze:
> ACPI Exception (processor_throttling-0084): AE_NOT_FOUND, Evaluating
> _PTC [20070126]
> ACPI Exception (processor_throttling-0147): AE_NOT_FOUND, Evaluating
> _TSS [20070126]
>
> On 2.6.20.9 I don't have this exceptions.
>
> Other problem:
>
> 2.6.22rc4-mm1:
> rutek:/home/maciek# cat /proc/acpi/processor/CPU0/throttling
> Naruszenie ochrony pamięci (segmentation fault)
Update (2.6.22-rc4-mm2):
rutek:/home/maciek# cat /proc/acpi/processor/CPU0/throttling
acpi_processor_throttling_seq_show() is busted
rutek:/home/maciek# cat /proc/acpi/processor/CPU1/throttling
acpi_processor_throttling_seq_show() is busted
--
Maciej Rutecki
http://www.maciek.unixy.pl
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3237 bytes --]
^ permalink raw reply [flat|nested] 120+ messages in thread
* Re: [2.6.22-rc4-mm1] ACPI Exception (processor_throttling)
2007-06-07 7:53 ` [2.6.22-rc4-mm1] ACPI Exception (processor_throttling) Maciej Rutecki
2007-06-07 8:51 ` Maciej Rutecki
@ 2007-06-07 9:09 ` Luming Yu
2007-06-07 10:30 ` Maciej Rutecki
1 sibling, 1 reply; 120+ messages in thread
From: Luming Yu @ 2007-06-07 9:09 UTC (permalink / raw)
To: Maciej Rutecki; +Cc: Andrew Morton, linux-kernel, linux-acpi, lenb
[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]
Please test the attached patch.
Thanks,
Luming
On 6/7/07, Maciej Rutecki <maciej.rutecki@gmail.com> wrote:
> ACPI Exception (processor_throttling-0084): AE_NOT_FOUND, Evaluating
> _PTC [20070126]
> ACPI Exception (processor_throttling-0147): AE_NOT_FOUND, Evaluating
> _TSS [20070126]
>
> On 2.6.20.9 I don't have this exceptions.
>
> Other problem:
>
> 2.6.22rc4-mm1:
> rutek:/home/maciek# cat /proc/acpi/processor/CPU0/throttling
> Naruszenie ochrony pamięci (segmentation fault)
>
> compared to 2.6.20.9:
> maciek@rutek:~$ cat /proc/acpi/processor/CPU0/throttling
> state count: 8
> active state: T0
> states:
> *T0: 00%
> T1: 12%
> T2: 25%
> T3: 37%
> T4: 50%
> T5: 62%
> T6: 75%
> T7: 87%
>
>
> Other info (2.6.22-rc4-mm1):
> rutek:/home/maciek# ls /proc/acpi/processor/CPU0/
> info limit power throttling
> rutek:/home/maciek# cat /proc/acpi/processor/CPU0/info
> processor id: 0
> acpi id: 1
> bus mastering control: yes
> power management: yes
> throttling control: yes
> limit interface: yes
> rutek:/home/maciek# cat /proc/acpi/processor/CPU0/limit
> active limit: P0:T0
> user limit: P0:T0
> thermal limit: P0:T0
> rutek:/home/maciek# cat /proc/acpi/processor/CPU0/power
> active state: C0
> max_cstate: C8
> bus master activity: 00000000
> maximum allowed latency: 8000 usec
> states:
> C1: type[C1] promotion[--] demotion[--]
> latency[001] usage[00000000] duration[00000000000000000000]
> C2: type[C2] promotion[--] demotion[--]
> latency[001] usage[00000000] duration[00000000000000000000]
>
> For CPU1 is similar.
>
> config, dmesg, acpidump:
> http://www.unixy.pl/maciek/download/kernel/2.6.22-rc4-mm1/
>
> --
> Maciej Rutecki
> http://www.maciek.unixy.pl
>
>
>
[-- Attachment #2: t.patch --]
[-- Type: application/octet-stream, Size: 654 bytes --]
diff --git a/drivers/acpi/processor_throttling.c b/drivers/acpi/processor_throttling.c
index 1bae2e4..1c9b697 100644
--- a/drivers/acpi/processor_throttling.c
+++ b/drivers/acpi/processor_throttling.c
@@ -645,7 +645,7 @@ static int acpi_processor_throttling_seq
pr->throttling.state_count-1);
seq_puts(seq, "states:\n");
- if(acpi_processor_get_throttling == acpi_processor_get_throttling_fadt)
+ if(pr->throttling.acpi_processor_get_throttling == acpi_processor_get_throttling_fadt)
for (i = 0; i < pr->throttling.state_count; i++)
seq_printf(seq, " %cT%d: %02d%%\n",
(i == pr->throttling.state ? '*' : ' '), i,
^ permalink raw reply related [flat|nested] 120+ messages in thread
* Re: 2.6.22-rc4-mm1
2007-06-06 9:07 2.6.22-rc4-mm1 Andrew Morton
` (14 preceding siblings ...)
2007-06-07 7:53 ` [2.6.22-rc4-mm1] ACPI Exception (processor_throttling) Maciej Rutecki
@ 2007-06-07 12:47 ` KAMEZAWA Hiroyuki
2007-06-07 15:34 ` 2.6.22-rc4-mm1 Andrew Morton
15 siblings, 1 reply; 120+ messages in thread
From: KAMEZAWA Hiroyuki @ 2007-06-07 12:47 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, clameter, linux-mm@kvack.org
Question.
While writing memory unplug, I noticed this code.
==
static int
fixup_anon_page(pte_t *pte, unsigned long start, unsigned long end, void *priv)
{
struct vm_area_struct *vma = priv;
struct page *page = vm_normal_page(vma, start, *pte);
if (page && PageAnon(page))
page->index = linear_page_index(vma, start);
return 0;
}
static int fixup_anon_pages(struct vm_area_struct *vma)
{
struct mm_walk walk = {
.pte_entry = fixup_anon_page,
};
return walk_page_range(vma->vm_mm,
vma->vm_start, vma->vm_end, &walk, vma);
}
==
I think that 'pte' passed to fixup_anon_page() by walk_page_range()
is not guaranteed to be 'Present'.
Then, vm_normal_page() will show print_bad_pte().
If this never occur now, I'll add my own check code for memory migration by kernel here.
(Sorry, I can't find who should be CCed.)
-Kame
^ permalink raw reply [flat|nested] 120+ messages in thread* Re: 2.6.22-rc4-mm1
2007-06-07 12:47 ` 2.6.22-rc4-mm1 KAMEZAWA Hiroyuki
@ 2007-06-07 15:34 ` Andrew Morton
2007-06-08 0:31 ` 2.6.22-rc4-mm1 KAMEZAWA Hiroyuki
0 siblings, 1 reply; 120+ messages in thread
From: Andrew Morton @ 2007-06-07 15:34 UTC (permalink / raw)
To: KAMEZAWA Hiroyuki
Cc: linux-kernel, clameter, linux-mm@kvack.org, Matt Mackall,
David Rientjes
On Thu, 7 Jun 2007 21:47:06 +0900 KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> Question.
>
> While writing memory unplug, I noticed this code.
> ==
> static int
> fixup_anon_page(pte_t *pte, unsigned long start, unsigned long end, void *priv)
> {
> struct vm_area_struct *vma = priv;
> struct page *page = vm_normal_page(vma, start, *pte);
>
> if (page && PageAnon(page))
> page->index = linear_page_index(vma, start);
>
> return 0;
> }
>
> static int fixup_anon_pages(struct vm_area_struct *vma)
> {
> struct mm_walk walk = {
> .pte_entry = fixup_anon_page,
> };
>
> return walk_page_range(vma->vm_mm,
> vma->vm_start, vma->vm_end, &walk, vma);
> }
I assume the above is your code - it's not in the tree?
>
> I think that 'pte' passed to fixup_anon_page() by walk_page_range()
> is not guaranteed to be 'Present'.
yup - the pagewalker only checks for !pte_none().
> Then, vm_normal_page() will show print_bad_pte().
> If this never occur now, I'll add my own check code for memory migration by kernel here.
Yes, you'll need to perform additional filtering where appropriate.
> (Sorry, I can't find who should be CCed.)
Matt and David did most of the work here.
^ permalink raw reply [flat|nested] 120+ messages in thread
![[-- Attachment #3: menu.png --] [-- Type: image/png, Size: 11332 bytes --]](../../200706062132.37430.m.kozlowski@tuxland.pl/3-menu.png){kind=link}