* Re: 2.6.16-rc4-mm1
2006-02-20 12:26 2.6.16-rc4-mm1 Andrew Morton
@ 2006-02-20 12:38 ` Al Viro
2006-02-20 12:54 ` 2.6.16-rc4-mm1 Francesco Biscani
2006-02-20 12:40 ` 2.6.16-rc4-mm1 Reuben Farrelly
` (9 subsequent siblings)
10 siblings, 1 reply; 62+ messages in thread
From: Al Viro @ 2006-02-20 12:38 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Mon, Feb 20, 2006 at 04:26:15AM -0800, Andrew Morton wrote:
> - Added Al Viro's `bird' tree (what does that mean, anyway?)
Mostly that aforementioned Al Viro is rather fond of bebop...
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc4-mm1
2006-02-20 12:26 2.6.16-rc4-mm1 Andrew Morton
2006-02-20 12:38 ` 2.6.16-rc4-mm1 Al Viro
@ 2006-02-20 12:40 ` Reuben Farrelly
2006-02-20 19:36 ` [PATCH] remove ccache from top level Makefile and make configurable Andy Whitcroft
2006-02-20 20:15 ` 2.6.16-rc4-mm1 Al Viro
2006-02-20 13:02 ` 2.6.16-rc4-mm1 Reuben Farrelly
` (8 subsequent siblings)
10 siblings, 2 replies; 62+ messages in thread
From: Reuben Farrelly @ 2006-02-20 12:40 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On 21/02/2006 1:26 a.m., Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc4/2.6.16-rc4-mm1/
>
> - git-jfs.patch has been dropped due to its ongoing git problems.
>
> - Added Al Viro's `bird' tree (what does that mean, anyway?) as
> git-viro-bird.patch.
>
> This tree had a lot of things dropped when it is merged into -mm, partly
> because some of it appears to have been merged into other git trees.
>
> - This kernel won't compile on ia64 (and possibly other architectures)
> because the kbuild tree is using Elf_Rela in scripts/mod/modpost.c. Is OK
> on x86, x86_64 and powerpc. Sam might send a hotfix?
>
> - Many warnings are emitted at the link stage due to section mismatches and
> duplicated symbol exports. Please don't report these. Patches are welcome,
> but do them carefully - it's easy to make mistakes with these things.
Time for the brown paper bag............ ;)
[root@tornado linux-2.6-mm]# make
/usr/src/linux/linux-2.6-mm/scripts/gcc-version.sh: line 11: ccache: command not
found
/usr/src/linux/linux-2.6-mm/scripts/gcc-version.sh: line 12: ccache: command not
found
make: ccache: Command not found
CHK include/linux/version.h
CC arch/i386/kernel/asm-offsets.s
/bin/sh: ccache: command not found
make[1]: *** [arch/i386/kernel/asm-offsets.s] Error 127
make: *** [prepare0] Error 2
[root@tornado linux-2.6-mm]#
Removing 'ccache' from the CC line in Makefile fixed this.
reuben
^ permalink raw reply [flat|nested] 62+ messages in thread* [PATCH] remove ccache from top level Makefile and make configurable
2006-02-20 12:40 ` 2.6.16-rc4-mm1 Reuben Farrelly
@ 2006-02-20 19:36 ` Andy Whitcroft
2006-02-20 21:39 ` Christopher Friesen
2006-02-20 20:15 ` 2.6.16-rc4-mm1 Al Viro
1 sibling, 1 reply; 62+ messages in thread
From: Andy Whitcroft @ 2006-02-20 19:36 UTC (permalink / raw)
To: Reuben Farrelly; +Cc: Andrew Morton, linux-kernel
remove ccache from top level Makefile and make configurable
[Here is the patch I used to fix this for out nightly testing.
It seems that if it were something we could configure from outside
the source we'd avoid this occuring again.]
Remove errant ccache from top-level makefile and make it configurable on
the kernel build line.
Signed-off-by: Andy Whitcroft <apw@shadowen.org>
---
Makefile | 4 +++-
1 files changed, 3 insertions(+), 1 deletion(-)
diff -upN reference/Makefile current/Makefile
--- reference/Makefile
+++ current/Makefile
@@ -171,9 +171,11 @@ SUBARCH := $(shell uname -m | sed -e s/i
# Alternatively CROSS_COMPILE can be set in the environment.
# Default value for CROSS_COMPILE is not to prefix executables
# Note: Some architectures assign CROSS_COMPILE in their arch/*/Makefile
+# CCACHE specifies the name of a ccache binary to use with gcc.
ARCH ?= $(SUBARCH)
CROSS_COMPILE ?=
+CCACHE ?=
# Architecture as present in compile.h
UTS_MACHINE := $(ARCH)
@@ -274,7 +276,7 @@ include $(srctree)/scripts/Kbuild.inclu
AS = $(CROSS_COMPILE)as
LD = $(CROSS_COMPILE)ld
-CC = ccache $(CROSS_COMPILE)gcc
+CC = $(CCACHE) $(CROSS_COMPILE)gcc
CPP = $(CC) -E
AR = $(CROSS_COMPILE)ar
NM = $(CROSS_COMPILE)nm
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: [PATCH] remove ccache from top level Makefile and make configurable
2006-02-20 19:36 ` [PATCH] remove ccache from top level Makefile and make configurable Andy Whitcroft
@ 2006-02-20 21:39 ` Christopher Friesen
2006-02-21 18:39 ` Andy Whitcroft
0 siblings, 1 reply; 62+ messages in thread
From: Christopher Friesen @ 2006-02-20 21:39 UTC (permalink / raw)
To: Andy Whitcroft; +Cc: Reuben Farrelly, Andrew Morton, linux-kernel
Andy Whitcroft wrote:
> remove ccache from top level Makefile and make configurable
Isn't it already configurable?
> diff -upN reference/Makefile current/Makefile
> --- reference/Makefile
> +++ current/Makefile
> @@ -171,9 +171,11 @@ SUBARCH := $(shell uname -m | sed -e s/i
> # Alternatively CROSS_COMPILE can be set in the environment.
> # Default value for CROSS_COMPILE is not to prefix executables
> # Note: Some architectures assign CROSS_COMPILE in their arch/*/Makefile
> +# CCACHE specifies the name of a ccache binary to use with gcc.
>
> ARCH ?= $(SUBARCH)
> CROSS_COMPILE ?=
> +CCACHE ?=
This sets it to nothing if it isn't already set--seems like you should
be able to set it on the commandline or else it has no effect.
Chris
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: [PATCH] remove ccache from top level Makefile and make configurable
2006-02-20 21:39 ` Christopher Friesen
@ 2006-02-21 18:39 ` Andy Whitcroft
0 siblings, 0 replies; 62+ messages in thread
From: Andy Whitcroft @ 2006-02-21 18:39 UTC (permalink / raw)
To: Christopher Friesen; +Cc: Reuben Farrelly, Andrew Morton, linux-kernel
Christopher Friesen wrote:
> Andy Whitcroft wrote:
>
>> remove ccache from top level Makefile and make configurable
>
> Isn't it already configurable?
Yes and no. You can specify CC, but you need to know the form of that
line. Ok, we do now but will be in the future. If it changes then the
semantics to use CCACHE would change. This seem like something to avoid.
>> diff -upN reference/Makefile current/Makefile
>> --- reference/Makefile
>> +++ current/Makefile
>> @@ -171,9 +171,11 @@ SUBARCH := $(shell uname -m | sed -e s/i
>> # Alternatively CROSS_COMPILE can be set in the environment.
>> # Default value for CROSS_COMPILE is not to prefix executables
>> # Note: Some architectures assign CROSS_COMPILE in their arch/*/Makefile
>> +# CCACHE specifies the name of a ccache binary to use with gcc.
>>
>> ARCH ?= $(SUBARCH)
>> CROSS_COMPILE ?=
>> +CCACHE ?=
>
>
> This sets it to nothing if it isn't already set--seems like you should
> be able to set it on the commandline or else it has no effect.
Yes this would really allow a subarch to set it if it wanted to, which
isn't likely to. It can probabally be killed.
-apw
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-20 12:40 ` 2.6.16-rc4-mm1 Reuben Farrelly
2006-02-20 19:36 ` [PATCH] remove ccache from top level Makefile and make configurable Andy Whitcroft
@ 2006-02-20 20:15 ` Al Viro
2006-02-21 0:53 ` 2.6.16-rc4-mm1 Andrew Morton
1 sibling, 1 reply; 62+ messages in thread
From: Al Viro @ 2006-02-20 20:15 UTC (permalink / raw)
To: Reuben Farrelly; +Cc: Andrew Morton, linux-kernel
It really would be more useful to pick individual branches
fixes.b8
m32r.b0
m68k.b8
xfs.b8
uml.b1
net.b6
frv.b8
misc.b8
upf.b5
volatile.b0
endian.b8
net-endian.b3
are relevant;
infrastructure.b0
not-for-merge.b1
are not. The latter is obvious, the former is infrastructure needed to
support cross-build setup.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-20 20:15 ` 2.6.16-rc4-mm1 Al Viro
@ 2006-02-21 0:53 ` Andrew Morton
2006-02-21 4:40 ` 2.6.16-rc4-mm1 Al Viro
2006-02-21 7:59 ` 2.6.16-rc4-mm1 Arjan van de Ven
0 siblings, 2 replies; 62+ messages in thread
From: Andrew Morton @ 2006-02-21 0:53 UTC (permalink / raw)
To: Al Viro; +Cc: reuben-lkml, linux-kernel
Al Viro <viro@ftp.linux.org.uk> wrote:
>
> It really would be more useful to pick individual branches
> fixes.b8
> m32r.b0
> m68k.b8
> xfs.b8
> uml.b1
> net.b6
> frv.b8
> misc.b8
> upf.b5
> volatile.b0
> endian.b8
> net-endian.b3
OK... But it looks like these are liable to be removed, renamed or added
to at the drop of a hat. I don't know how to keep up with that.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-21 0:53 ` 2.6.16-rc4-mm1 Andrew Morton
@ 2006-02-21 4:40 ` Al Viro
2006-02-21 7:59 ` 2.6.16-rc4-mm1 Arjan van de Ven
1 sibling, 0 replies; 62+ messages in thread
From: Al Viro @ 2006-02-21 4:40 UTC (permalink / raw)
To: Andrew Morton; +Cc: reuben-lkml, linux-kernel
On Mon, Feb 20, 2006 at 04:53:27PM -0800, Andrew Morton wrote:
> Al Viro <viro@ftp.linux.org.uk> wrote:
> >
> > It really would be more useful to pick individual branches
> > fixes.b8
> > m32r.b0
> > m68k.b8
> > xfs.b8
> > uml.b1
> > net.b6
> > frv.b8
> > misc.b8
> > upf.b5
> > volatile.b0
> > endian.b8
> > net-endian.b3
>
> OK... But it looks like these are liable to be removed, renamed or added
> to at the drop of a hat. I don't know how to keep up with that.
No renaming... FWIW, the workflow looks that way:
* origin follows mainline; no merges, no commits, only fetching from Linus
* everything else is branched off origin; branches starting at Nth branch
point have .b<N> as suffix.
* all topic branches (everything except bird) _never_ get merges; only
commits, 100% linear history.
* composite branch (bird), OTOH, gets only merges - from origin and from
topic branches.
* whenever a conflict would happen:
* new bird.b<N> is spawned;
* all affected branches are respawned (off the same point on mainline)
and cherry-picked from their previous versions.
* the latest versions of all topic branches are merged into composite
one.
That's it for master repository. Work repositories are cloned from it;
there I have a transient branch (work) starting at the tip of bird.b<latest>.
All changes go there; to get them back into master I cherry-pick from work
to appropriate topic branches and fetch them into master. Then (in master)
I merge them into composite branch and push the result to work repos.
At that point I again have all of them in sync and just reset work branch
to tip of composite one.
It works surprisingly well; nice properties:
* latest versions of all topic branches merge clean and have linear
history. IOW, git-format-patch on any of them gives a set of patches that
will apply to the tip of mainline and won't conflict each other.
* at all times composite branch is equal to merge of topic ones and
latest mainline.
* all build boxen are kept in sync easily
* I never have to trust build boxen with anything about master or each
other.
* Adding new build boxen is trivial; so's redistributing work between
those.
* Branches in master are never renamed, removed or reset.
The last one is a big win compared to davem's "rebase everything all the
time" and this setup does, AFAICS, behave no worse wrt giving clean
patchset.
As for the "what to pick" - I've just put that into
ftp.kernel.org/pub/linux/kernel/people/viro/bird-branches (and will put
composite patch there) and I can send mail whenever that changes...
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-21 0:53 ` 2.6.16-rc4-mm1 Andrew Morton
2006-02-21 4:40 ` 2.6.16-rc4-mm1 Al Viro
@ 2006-02-21 7:59 ` Arjan van de Ven
1 sibling, 0 replies; 62+ messages in thread
From: Arjan van de Ven @ 2006-02-21 7:59 UTC (permalink / raw)
To: Andrew Morton; +Cc: Al Viro, reuben-lkml, linux-kernel
On Mon, 2006-02-20 at 16:53 -0800, Andrew Morton wrote:
> Al Viro <viro@ftp.linux.org.uk> wrote:
> >
> > It really would be more useful to pick individual branches
> > fixes.b8
> > m32r.b0
> > m68k.b8
> > xfs.b8
> > uml.b1
> > net.b6
> > frv.b8
> > misc.b8
> > upf.b5
> > volatile.b0
> > endian.b8
> > net-endian.b3
>
> OK... But it looks like these are liable to be removed, renamed or added
> to at the drop of a hat. I don't know how to keep up with that.
maybe a for-akpm branch can be made?
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-20 12:26 2.6.16-rc4-mm1 Andrew Morton
2006-02-20 12:38 ` 2.6.16-rc4-mm1 Al Viro
2006-02-20 12:40 ` 2.6.16-rc4-mm1 Reuben Farrelly
@ 2006-02-20 13:02 ` Reuben Farrelly
2006-02-20 14:11 ` 2.6.16-rc4-mm1 Patrick McHardy
2006-02-20 14:37 ` 2.6.16-rc4-mm1: usbfs2 multiply defined symbols Adrian Bunk
` (7 subsequent siblings)
10 siblings, 1 reply; 62+ messages in thread
From: Reuben Farrelly @ 2006-02-20 13:02 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On 21/02/2006 1:26 a.m., Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc4/2.6.16-rc4-mm1/
>
> - git-jfs.patch has been dropped due to its ongoing git problems.
>
> - Added Al Viro's `bird' tree (what does that mean, anyway?) as
> git-viro-bird.patch.
>
> This tree had a lot of things dropped when it is merged into -mm, partly
> because some of it appears to have been merged into other git trees.
>
> - This kernel won't compile on ia64 (and possibly other architectures)
> because the kbuild tree is using Elf_Rela in scripts/mod/modpost.c. Is OK
> on x86, x86_64 and powerpc. Sam might send a hotfix?
>
> - Many warnings are emitted at the link stage due to section mismatches and
> duplicated symbol exports. Please don't report these. Patches are welcome,
> but do them carefully - it's easy to make mistakes with these things.
Minor dependency issue:
My compile failed with this..
CC [M] net/netfilter/xt_dccp.o
In file included from net/netfilter/xt_dccp.c:15:
include/linux/dccp.h:341:2: error: #error "At least one CCID must be built as
the default"
make[2]: *** [net/netfilter/xt_dccp.o] Error 1
make[1]: *** [net/netfilter] Error 2
make: *** [net] Error 2
[root@tornado linux-2.6-mm]#
[I have no idea what a CCID is]
But it was caused by this:
CONFIG_NETFILTER_XT_MATCH_DCCP=m
and maybe this below had an impact:
#
# DCCP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP is not set
After unsetting the option to build the DCCP Netfilter module, I was able to
compile through to completion.
Reuben
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc4-mm1
2006-02-20 13:02 ` 2.6.16-rc4-mm1 Reuben Farrelly
@ 2006-02-20 14:11 ` Patrick McHardy
2006-02-20 14:20 ` 2.6.16-rc4-mm1 Arnaldo Carvalho de Melo
` (2 more replies)
0 siblings, 3 replies; 62+ messages in thread
From: Patrick McHardy @ 2006-02-20 14:11 UTC (permalink / raw)
To: Reuben Farrelly
Cc: Andrew Morton, linux-kernel, Netfilter Development Mailinglist,
dccp
Reuben Farrelly wrote:
> Minor dependency issue:
>
> My compile failed with this..
>
> CC [M] net/netfilter/xt_dccp.o
> In file included from net/netfilter/xt_dccp.c:15:
> include/linux/dccp.h:341:2: error: #error "At least one CCID must be
> built as the default"
> make[2]: *** [net/netfilter/xt_dccp.o] Error 1
> make[1]: *** [net/netfilter] Error 2
> make: *** [net] Error 2
> [root@tornado linux-2.6-mm]#
>
> [I have no idea what a CCID is]
>
> But it was caused by this:
>
> CONFIG_NETFILTER_XT_MATCH_DCCP=m
>
> and maybe this below had an impact:
>
> #
> # DCCP Configuration (EXPERIMENTAL)
> #
> # CONFIG_IP_DCCP is not set
>
> After unsetting the option to build the DCCP Netfilter module, I was
> able to compile through to completion.
Ideally this dependency should be enforced by Kconfig. I'm not sure
if it is possible to express something like "IP_DCCP_CCID2 and
IP_DCCP_CCID3 depend on DCCP, DCCP requires at least one of both
to be enabled". Can someone more familiar with Kconfig than me
comment on this? Otherwise the #error should be moved to
net/dccp/options.c to keep dccp.h usable without dccp enabled.
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc4-mm1
2006-02-20 14:11 ` 2.6.16-rc4-mm1 Patrick McHardy
@ 2006-02-20 14:20 ` Arnaldo Carvalho de Melo
2006-02-20 20:04 ` 2.6.16-rc4-mm1 Carl-Daniel Hailfinger
2006-02-20 20:44 ` 2.6.16-rc4-mm1 Adrian Bunk
2 siblings, 0 replies; 62+ messages in thread
From: Arnaldo Carvalho de Melo @ 2006-02-20 14:20 UTC (permalink / raw)
To: Patrick McHardy
Cc: Reuben Farrelly, Andrew Morton, linux-kernel,
Netfilter Development Mailinglist, dccp
On 2/20/06, Patrick McHardy <kaber@trash.net> wrote:
> Reuben Farrelly wrote:
> > Minor dependency issue:
> >
> > My compile failed with this..
> >
> > CC [M] net/netfilter/xt_dccp.o
> > In file included from net/netfilter/xt_dccp.c:15:
> > include/linux/dccp.h:341:2: error: #error "At least one CCID must be
> > built as the default"
> > make[2]: *** [net/netfilter/xt_dccp.o] Error 1
> > make[1]: *** [net/netfilter] Error 2
> > make: *** [net] Error 2
> > [root@tornado linux-2.6-mm]#
> >
> > [I have no idea what a CCID is]
> >
> > But it was caused by this:
> >
> > CONFIG_NETFILTER_XT_MATCH_DCCP=m
> >
> > and maybe this below had an impact:
> >
> > #
> > # DCCP Configuration (EXPERIMENTAL)
> > #
> > # CONFIG_IP_DCCP is not set
> >
> > After unsetting the option to build the DCCP Netfilter module, I was
> > able to compile through to completion.
>
> Ideally this dependency should be enforced by Kconfig. I'm not sure
> if it is possible to express something like "IP_DCCP_CCID2 and
> IP_DCCP_CCID3 depend on DCCP, DCCP requires at least one of both
> to be enabled". Can someone more familiar with Kconfig than me
> comment on this? Otherwise the #error should be moved to
> net/dccp/options.c to keep dccp.h usable without dccp enabled.
oops, I think I'll move the #error to options.c, thanks for forwarding
this report
to dccp@vger.kernel.org.
- Arnaldo
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-20 14:11 ` 2.6.16-rc4-mm1 Patrick McHardy
2006-02-20 14:20 ` 2.6.16-rc4-mm1 Arnaldo Carvalho de Melo
@ 2006-02-20 20:04 ` Carl-Daniel Hailfinger
2006-02-20 20:56 ` 2.6.16-rc4-mm1 Arnaldo Carvalho de Melo
2006-02-20 20:44 ` 2.6.16-rc4-mm1 Adrian Bunk
2 siblings, 1 reply; 62+ messages in thread
From: Carl-Daniel Hailfinger @ 2006-02-20 20:04 UTC (permalink / raw)
To: Patrick McHardy
Cc: Reuben Farrelly, Andrew Morton, Netfilter Development Mailinglist,
linux-kernel, dccp
Patrick McHardy schrieb:
> Reuben Farrelly wrote:
>
>>Minor dependency issue:
>>
>>My compile failed with this..
>>
>> CC [M] net/netfilter/xt_dccp.o
>>In file included from net/netfilter/xt_dccp.c:15:
>>include/linux/dccp.h:341:2: error: #error "At least one CCID must be
>>built as the default"
>>make[2]: *** [net/netfilter/xt_dccp.o] Error 1
>>make[1]: *** [net/netfilter] Error 2
>>make: *** [net] Error 2
>>[root@tornado linux-2.6-mm]#
>>
>>[I have no idea what a CCID is]
>>
>>But it was caused by this:
>>
>>CONFIG_NETFILTER_XT_MATCH_DCCP=m
>>
>>and maybe this below had an impact:
>>
>>#
>># DCCP Configuration (EXPERIMENTAL)
>>#
>># CONFIG_IP_DCCP is not set
>>
>>After unsetting the option to build the DCCP Netfilter module, I was
>>able to compile through to completion.
>
>
> Ideally this dependency should be enforced by Kconfig. I'm not sure
> if it is possible to express something like "IP_DCCP_CCID2 and
> IP_DCCP_CCID3 depend on DCCP, DCCP requires at least one of both
> to be enabled". Can someone more familiar with Kconfig than me
> comment on this? Otherwise the #error should be moved to
> net/dccp/options.c to keep dccp.h usable without dccp enabled.
Suggestion (not tested):
config IP_DCCP_CCID2
tristate "blah"
select DCCP
help
Foo
config IP_DCCP_CCID3
tristate "blah"
select DCCP
help
Foo
config DCCP
bool "blah"
depends on IP_DCCP_CCID2 || IP_DCCP_CCID3
help
Foo
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc4-mm1
2006-02-20 20:04 ` 2.6.16-rc4-mm1 Carl-Daniel Hailfinger
@ 2006-02-20 20:56 ` Arnaldo Carvalho de Melo
2006-02-20 21:09 ` 2.6.16-rc4-mm1 Adrian Bunk
0 siblings, 1 reply; 62+ messages in thread
From: Arnaldo Carvalho de Melo @ 2006-02-20 20:56 UTC (permalink / raw)
To: Carl-Daniel Hailfinger
Cc: Patrick McHardy, Reuben Farrelly, Andrew Morton,
Netfilter Development Mailinglist, linux-kernel, dccp
On 2/20/06, Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> wrote:
> Patrick McHardy schrieb:
> > Reuben Farrelly wrote:
> >
> >>Minor dependency issue:
> >>
> >>My compile failed with this..
> >>
> >> CC [M] net/netfilter/xt_dccp.o
> >>In file included from net/netfilter/xt_dccp.c:15:
> >>include/linux/dccp.h:341:2: error: #error "At least one CCID must be
> >>built as the default"
> >>make[2]: *** [net/netfilter/xt_dccp.o] Error 1
> >>make[1]: *** [net/netfilter] Error 2
> >>make: *** [net] Error 2
> >>[root@tornado linux-2.6-mm]#
> >>
> >>[I have no idea what a CCID is]
> >>
> >>But it was caused by this:
> >>
> >>CONFIG_NETFILTER_XT_MATCH_DCCP=m
> >>
> >>and maybe this below had an impact:
> >>
> >>#
> >># DCCP Configuration (EXPERIMENTAL)
> >>#
> >># CONFIG_IP_DCCP is not set
> >>
> >>After unsetting the option to build the DCCP Netfilter module, I was
> >>able to compile through to completion.
> >
> >
> > Ideally this dependency should be enforced by Kconfig. I'm not sure
> > if it is possible to express something like "IP_DCCP_CCID2 and
> > IP_DCCP_CCID3 depend on DCCP, DCCP requires at least one of both
> > to be enabled". Can someone more familiar with Kconfig than me
> > comment on this? Otherwise the #error should be moved to
> > net/dccp/options.c to keep dccp.h usable without dccp enabled.
>
> Suggestion (not tested):
>
> config IP_DCCP_CCID2
> tristate "blah"
> select DCCP
> help
> Foo
> config IP_DCCP_CCID3
> tristate "blah"
> select DCCP
> help
> Foo
> config DCCP
> bool "blah"
> depends on IP_DCCP_CCID2 || IP_DCCP_CCID3
> help
> Foo
NAK, its more clear to be exposed to DCCP specific stuff such as CCIDs only
if the user selected DCCP.
So perhaps something like what is done for the io schedulers, will study this...
- Arnaldo
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-20 20:56 ` 2.6.16-rc4-mm1 Arnaldo Carvalho de Melo
@ 2006-02-20 21:09 ` Adrian Bunk
0 siblings, 0 replies; 62+ messages in thread
From: Adrian Bunk @ 2006-02-20 21:09 UTC (permalink / raw)
To: Arnaldo Carvalho de Melo
Cc: Carl-Daniel Hailfinger, Patrick McHardy, Reuben Farrelly,
Andrew Morton, Netfilter Development Mailinglist, linux-kernel,
dccp
On Mon, Feb 20, 2006 at 05:56:47PM -0300, Arnaldo Carvalho de Melo wrote:
>...
> So perhaps something like what is done for the io schedulers, will study this...
The io schedulers solve this through "always build the noop scheduler"...
> - Arnaldo
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] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-20 14:11 ` 2.6.16-rc4-mm1 Patrick McHardy
2006-02-20 14:20 ` 2.6.16-rc4-mm1 Arnaldo Carvalho de Melo
2006-02-20 20:04 ` 2.6.16-rc4-mm1 Carl-Daniel Hailfinger
@ 2006-02-20 20:44 ` Adrian Bunk
2006-02-21 1:17 ` 2.6.16-rc4-mm1 Patrick McHardy
2 siblings, 1 reply; 62+ messages in thread
From: Adrian Bunk @ 2006-02-20 20:44 UTC (permalink / raw)
To: Patrick McHardy, acme
Cc: Reuben Farrelly, Andrew Morton, linux-kernel,
Netfilter Development Mailinglist, dccp
On Mon, Feb 20, 2006 at 03:11:36PM +0100, Patrick McHardy wrote:
> Reuben Farrelly wrote:
> > Minor dependency issue:
> >
> > My compile failed with this..
> >
> > CC [M] net/netfilter/xt_dccp.o
> > In file included from net/netfilter/xt_dccp.c:15:
> > include/linux/dccp.h:341:2: error: #error "At least one CCID must be
> > built as the default"
> > make[2]: *** [net/netfilter/xt_dccp.o] Error 1
> > make[1]: *** [net/netfilter] Error 2
> > make: *** [net] Error 2
> > [root@tornado linux-2.6-mm]#
> >
> > [I have no idea what a CCID is]
> >
> > But it was caused by this:
> >
> > CONFIG_NETFILTER_XT_MATCH_DCCP=m
> >
> > and maybe this below had an impact:
> >
> > #
> > # DCCP Configuration (EXPERIMENTAL)
> > #
> > # CONFIG_IP_DCCP is not set
> >
> > After unsetting the option to build the DCCP Netfilter module, I was
> > able to compile through to completion.
>
> Ideally this dependency should be enforced by Kconfig. I'm not sure
> if it is possible to express something like "IP_DCCP_CCID2 and
> IP_DCCP_CCID3 depend on DCCP, DCCP requires at least one of both
> to be enabled". Can someone more familiar with Kconfig than me
> comment on this? Otherwise the #error should be moved to
> net/dccp/options.c to keep dccp.h usable without dccp enabled.
I can try to do it, but I need the exact semantics.
Should all of the following stay allowed configurations?
CONFIG_IP_DCCP=y
CONFIG_IP_DCCP_CCID2=m
CONFIG_IP_DCCP_CCID3=n
CONFIG_IP_DCCP=y
CONFIG_IP_DCCP_CCID2=y
CONFIG_IP_DCCP_CCID3=m
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] 62+ messages in thread* Re: 2.6.16-rc4-mm1
2006-02-20 20:44 ` 2.6.16-rc4-mm1 Adrian Bunk
@ 2006-02-21 1:17 ` Patrick McHardy
2006-02-21 2:00 ` 2.6.16-rc4-mm1 Adrian Bunk
0 siblings, 1 reply; 62+ messages in thread
From: Patrick McHardy @ 2006-02-21 1:17 UTC (permalink / raw)
To: Adrian Bunk; +Cc: linux-kernel, Netfilter Development Mailinglist
Adrian Bunk wrote:
> On Mon, Feb 20, 2006 at 03:11:36PM +0100, Patrick McHardy wrote:
>
>>Ideally this dependency should be enforced by Kconfig. I'm not sure
>>if it is possible to express something like "IP_DCCP_CCID2 and
>>IP_DCCP_CCID3 depend on DCCP, DCCP requires at least one of both
>>to be enabled". Can someone more familiar with Kconfig than me
>>comment on this? Otherwise the #error should be moved to
>>net/dccp/options.c to keep dccp.h usable without dccp enabled.
>
>
> I can try to do it, but I need the exact semantics.
>
> Should all of the following stay allowed configurations?
>
> CONFIG_IP_DCCP=y
> CONFIG_IP_DCCP_CCID2=m
> CONFIG_IP_DCCP_CCID3=n
>
> CONFIG_IP_DCCP=y
> CONFIG_IP_DCCP_CCID2=y
> CONFIG_IP_DCCP_CCID3=m
Arnaldo apparently wants to fix it differently, but maybe you could help
us with conntrack :) CONFIG_IP_NF_CONNTRACK and CONFIG_NF_CONNTRACK
should be mutually exclusive. Specifying
CONFIG_IP_NF_CONNTRACK
depends on CONFIG_NF_CONNTRACK=n
CONFIG_NF_CONNTRACK
depends on CONFIG_IP_NF_CONNTRACK=n
will avoid asking for NF_CONNTRACK when IP_NF_CONNTRACK is set, but not
the other way around.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-21 1:17 ` 2.6.16-rc4-mm1 Patrick McHardy
@ 2006-02-21 2:00 ` Adrian Bunk
0 siblings, 0 replies; 62+ messages in thread
From: Adrian Bunk @ 2006-02-21 2:00 UTC (permalink / raw)
To: Patrick McHardy; +Cc: linux-kernel, Netfilter Development Mailinglist
On Tue, Feb 21, 2006 at 02:17:32AM +0100, Patrick McHardy wrote:
>
> Arnaldo apparently wants to fix it differently, but maybe you could help
> us with conntrack :) CONFIG_IP_NF_CONNTRACK and CONFIG_NF_CONNTRACK
> should be mutually exclusive. Specifying
>
> CONFIG_IP_NF_CONNTRACK
> depends on CONFIG_NF_CONNTRACK=n
>
> CONFIG_NF_CONNTRACK
> depends on CONFIG_IP_NF_CONNTRACK=n
>
> will avoid asking for NF_CONNTRACK when IP_NF_CONNTRACK is set, but not
> the other way around.
Even worse, kconfig will complain about a circular dependency.
CONFIG_IP_NF_CONNTRACK
CONFIG_NF_CONNTRACK
depends on CONFIG_IP_NF_CONNTRACK=n
CONFIG_IP_NF_CONNTRACK will be visible if CONFIG_NF_CONNTRACK is set,
but as soon as CONFIG_IP_NF_CONNTRACK is set, CONFIG_NF_CONNTRACK is
automatically set to n.
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] 62+ messages in thread
* 2.6.16-rc4-mm1: usbfs2 multiply defined symbols
2006-02-20 12:26 2.6.16-rc4-mm1 Andrew Morton
` (2 preceding siblings ...)
2006-02-20 13:02 ` 2.6.16-rc4-mm1 Reuben Farrelly
@ 2006-02-20 14:37 ` Adrian Bunk
2006-02-20 17:33 ` [linux-usb-devel] " Greg KH
2006-02-20 15:07 ` 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble? Helge Hafting
` (6 subsequent siblings)
10 siblings, 1 reply; 62+ messages in thread
From: Adrian Bunk @ 2006-02-20 14:37 UTC (permalink / raw)
To: Andrew Morton, Greg Kroah-Hartman; +Cc: linux-kernel, linux-usb-devel
On Mon, Feb 20, 2006 at 04:26:15AM -0800, Andrew Morton wrote:
>...
> +gregkh-usb-usbfs2.patch
>
> USB tree updates
>...
This patch causes the following compile error:
<-- snip -->
...
LD .tmp_vmlinux1
drivers/built-in.o: In function `securityfs_create_dir': multiple definition of `securityfs_create_dir'
security/built-in.o: first defined here
drivers/built-in.o: In function `securityfs_remove': multiple definition of `securityfs_remove'
security/built-in.o: first defined here
drivers/built-in.o: In function `securityfs_create_file': multiple definition of `securityfs_create_file'
security/built-in.o: first defined here
ld: Warning: size of symbol `securityfs_create_file' changed from 331 in security/built-in.o to 332 in drivers/built-in.o
make: *** [.tmp_vmlinux1] Error 1
<-- snip -->
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] 62+ messages in thread* Re: [linux-usb-devel] 2.6.16-rc4-mm1: usbfs2 multiply defined symbols
2006-02-20 14:37 ` 2.6.16-rc4-mm1: usbfs2 multiply defined symbols Adrian Bunk
@ 2006-02-20 17:33 ` Greg KH
0 siblings, 0 replies; 62+ messages in thread
From: Greg KH @ 2006-02-20 17:33 UTC (permalink / raw)
To: Adrian Bunk
Cc: Andrew Morton, Greg Kroah-Hartman, linux-kernel, linux-usb-devel
On Mon, Feb 20, 2006 at 03:37:13PM +0100, Adrian Bunk wrote:
> On Mon, Feb 20, 2006 at 04:26:15AM -0800, Andrew Morton wrote:
> >...
> > +gregkh-usb-usbfs2.patch
> >
> > USB tree updates
> >...
>
> This patch causes the following compile error:
Known issue, don't build in usbfs2 directly in the kernel just yet.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble?
2006-02-20 12:26 2.6.16-rc4-mm1 Andrew Morton
` (3 preceding siblings ...)
2006-02-20 14:37 ` 2.6.16-rc4-mm1: usbfs2 multiply defined symbols Adrian Bunk
@ 2006-02-20 15:07 ` Helge Hafting
2006-02-20 15:25 ` MIke Galbraith
[not found] ` <6bffcb0e0602200533p1a3da98ew@mail.gmail.com>
` (5 subsequent siblings)
10 siblings, 1 reply; 62+ messages in thread
From: Helge Hafting @ 2006-02-20 15:07 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
pentium IV single processor, gcc (GCC) 4.0.3 20060128
During boot, I normally get:
parport0: irq 7 detected
lp0: using parport0 (polling).
Instead, I got this, written by hand:
parport0:irq 7 detected
BUG unable to handle kernel NULL pointer dereference at 000000c8
eip c0234785
*pde=0
Oops: 0000[#1]
last sysfs file:
cpu 0
Eip: 0060:[<c0234785>] not tainted VLI
EFLAGS: 000010282 (2.6.16-rc4-mm1 #3)
EIP is at kref_get+0x6/0x3e
eax 000000c8 ebx 000000c8 ecx 00000000 edx affea000
esi c04d1df1 edi dff59927 ebp dff68394 esp dff59927
ds 0007b es 0007b ss 00068
process swapper
call trace
kobject_get sysfs_create_link
sysfs_add_file class_device_add
kobject_juif class_device_create
lp_register lp_attach
attach_driver_chain parport_announce_port
parport_pc_probe_port parport_pc_init
init init
kernel_thread_helper
kernel panic - not syncing attempted to kill init!
reboot in 300 seconds. (Now, if sysrq+B would work
while waiting for this...)
This oops is simplified. I can get the exact text if
that really matters. It is much more to write down and
I don't usually have my camera at work.
Helge Hafting
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble?
2006-02-20 15:07 ` 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble? Helge Hafting
@ 2006-02-20 15:25 ` MIke Galbraith
2006-02-20 20:41 ` Andrew Morton
2006-02-20 22:58 ` Rafael J. Wysocki
0 siblings, 2 replies; 62+ messages in thread
From: MIke Galbraith @ 2006-02-20 15:25 UTC (permalink / raw)
To: Helge Hafting; +Cc: Andrew Morton, linux-kernel
On Mon, 2006-02-20 at 16:07 +0100, Helge Hafting wrote:
> pentium IV single processor, gcc (GCC) 4.0.3 20060128
>
> During boot, I normally get:
> parport0: irq 7 detected
> lp0: using parport0 (polling).
>
> Instead, I got this, written by hand:
........
> This oops is simplified. I can get the exact text if
> that really matters. It is much more to write down and
> I don't usually have my camera at work.
I get the same, and already have the serial console hooked up.
BUG: unable to handle kernel NULL pointer dereference at virtual address 000000e8
printing eip:
c0295414
*pde = 00000000
Oops: 0000 1]
PREEMPT SMP
last sysfs file:
Modules linked in:
CPU: 1
EIP: 0060:[<c0295414>] Not tainted VLI
EFLAGS: 00010282 (2.6.16-rc4-mm17)
EIP is at kref_get+0x9/0x43
eax: 000000e8 ebx: 000000e8 ecx: c1923a00 edx: 000000d0
esi: c04d87ab edi: dfccfce7 ebp: c1910d68 esp: c1910d54
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, threadinfo=c1910000 task=c190faa0)
Stack: <0>dfcdf5c8 00008124 dfccfd40 00000286 000000d0 c1910d74 c0294964 dfccfd00
c1910da0 c019e308 dfcdf5c0 dfccfd40 000000d0 dfce04d0 fffffff4 dfcd2d74
00000048 dfcdf5c0 00000000 c1910dd8 c031f953 dfcdf5c8 c04dd2e1 dfcdf640
Call Trace:
<c0103e8c> show_stack_log_lvl+0xb7/0xfd <c0104064> show_registers+0x192/0x228
<c0104347> die+0x119/0x24a <c011387f> do_page_fault+0x2ff/0x57a
<c0103837> error_code+0x4f/0x54 <c0294964> kobject_get+0x12/0x17
<c019e308> sysfs_create_link+0x91/0x103 <c031f953> class_device_add+0x13c/0x2b1
<c031fada> class_device_register+0x12/0x15 <c031fb59> class_device_create+0x7c/0x9e
<c0306e20> lp_register+0xa8/0xef <c0306e93> lp_attach+0x2c/0x73
<c0314c4f> attach_driver_chain+0x14/0x2d <c0314d1e> parport_announce_port+0x89/0xb9
<c031b94e> parport_pc_probe_port+0x6d9/0xeb2 <c031c1d9> parport_pc_pnp_probe+0xb2/0x108
<c02ef096> pnp_device_probe+0x47/0x93 <c031eae2> driver_probe_device+0x3e/0xb6
<c031ec29> __driver_attach+0x68/0x6a <c031e198> bus_for_each_dev+0x40/0x5e
<c031e9cd> driver_attach+0x19/0x1b <c031e474> bus_add_driver+0x6c/0x119
<c031efa2> driver_register+0x76/0xaa <c02eeecd> pnp_register_driver+0x1d/0x47
<c062bc92> parport_pc_init+0x26b/0x295 <c0100427> init+0x124/0x365
<c0100e25> kernel_thread_helper+0x5/0xb
Code: dc 12 00 e9 79 fe ff ff 0f 0b 33 03 03 28 4b c0 e9 54 fe ff ff 90 90 55 89 e5 c7 00 01 00 00 00 5d c3 55 89 e5 53 83 ec 10 89 c3 <8b> 00 85 c0 74 09 f0 ff 03 83 c4 10 5b 5d c3 c7 44 24 0c 88 d3
<0>Kernel panic - not syncing: Attempted to kill init!
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble?
2006-02-20 15:25 ` MIke Galbraith
@ 2006-02-20 20:41 ` Andrew Morton
2006-02-20 23:36 ` Rafael J. Wysocki
2006-02-20 22:58 ` Rafael J. Wysocki
1 sibling, 1 reply; 62+ messages in thread
From: Andrew Morton @ 2006-02-20 20:41 UTC (permalink / raw)
To: MIke Galbraith; +Cc: helge.hafting, linux-kernel
MIke Galbraith <efault@gmx.de> wrote:
>
> On Mon, 2006-02-20 at 16:07 +0100, Helge Hafting wrote:
> > pentium IV single processor, gcc (GCC) 4.0.3 20060128
> >
> > During boot, I normally get:
> > parport0: irq 7 detected
> > lp0: using parport0 (polling).
> >
> > Instead, I got this, written by hand:
>
> ........
>
> > This oops is simplified. I can get the exact text if
> > that really matters. It is much more to write down and
> > I don't usually have my camera at work.
>
> I get the same, and already have the serial console hooked up.
>
> BUG: unable to handle kernel NULL pointer dereference at virtual address 000000e8
Thanks. Could someone try reverting
register-sysfs-device-for-lp-devices.patch?
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble?
2006-02-20 20:41 ` Andrew Morton
@ 2006-02-20 23:36 ` Rafael J. Wysocki
2006-02-20 23:40 ` Andrew Morton
0 siblings, 1 reply; 62+ messages in thread
From: Rafael J. Wysocki @ 2006-02-20 23:36 UTC (permalink / raw)
To: Andrew Morton; +Cc: MIke Galbraith, helge.hafting, linux-kernel
On Monday 20 February 2006 21:41, Andrew Morton wrote:
> MIke Galbraith <efault@gmx.de> wrote:
> >
> > On Mon, 2006-02-20 at 16:07 +0100, Helge Hafting wrote:
> > > pentium IV single processor, gcc (GCC) 4.0.3 20060128
> > >
> > > During boot, I normally get:
> > > parport0: irq 7 detected
> > > lp0: using parport0 (polling).
> > >
> > > Instead, I got this, written by hand:
> >
> > ........
> >
> > > This oops is simplified. I can get the exact text if
> > > that really matters. It is much more to write down and
> > > I don't usually have my camera at work.
> >
> > I get the same, and already have the serial console hooked up.
> >
> > BUG: unable to handle kernel NULL pointer dereference at virtual address 000000e8
>
> Thanks. Could someone try reverting
> register-sysfs-device-for-lp-devices.patch?
That helps on my system.
An unrelated problem is that USB host drivers (ohci-hcd, ehci-hcd) refuse to
suspend. [Investigating ...]
Rafael
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble?
2006-02-20 23:36 ` Rafael J. Wysocki
@ 2006-02-20 23:40 ` Andrew Morton
2006-02-21 0:02 ` Rafael J. Wysocki
0 siblings, 1 reply; 62+ messages in thread
From: Andrew Morton @ 2006-02-20 23:40 UTC (permalink / raw)
To: Rafael J. Wysocki; +Cc: efault, helge.hafting, linux-kernel, Bernhard R. Link
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
> On Monday 20 February 2006 21:41, Andrew Morton wrote:
> > MIke Galbraith <efault@gmx.de> wrote:
> > >
> > > On Mon, 2006-02-20 at 16:07 +0100, Helge Hafting wrote:
> > > > pentium IV single processor, gcc (GCC) 4.0.3 20060128
> > > >
> > > > During boot, I normally get:
> > > > parport0: irq 7 detected
> > > > lp0: using parport0 (polling).
> > > >
> > > > Instead, I got this, written by hand:
> > >
> > > ........
> > >
> > > > This oops is simplified. I can get the exact text if
> > > > that really matters. It is much more to write down and
> > > > I don't usually have my camera at work.
> > >
> > > I get the same, and already have the serial console hooked up.
> > >
> > > BUG: unable to handle kernel NULL pointer dereference at virtual address 000000e8
> >
> > Thanks. Could someone try reverting
> > register-sysfs-device-for-lp-devices.patch?
>
> That helps on my system.
OK, thanks. I'll drop it.
> An unrelated problem is that USB host drivers (ohci-hcd, ehci-hcd) refuse to
> suspend. [Investigating ...]
Me too.
Try reverting reset-pci-device-state-to-unknown-after-disabled.patch. It
seems that my machine likes the bug which that fixes. Something's most
mucked up in PM land.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble?
2006-02-20 23:40 ` Andrew Morton
@ 2006-02-21 0:02 ` Rafael J. Wysocki
2006-02-21 0:09 ` Andrew Morton
2006-02-22 11:44 ` Rafael J. Wysocki
0 siblings, 2 replies; 62+ messages in thread
From: Rafael J. Wysocki @ 2006-02-21 0:02 UTC (permalink / raw)
To: Andrew Morton; +Cc: efault, helge.hafting, linux-kernel, Bernhard R. Link
On Tuesday 21 February 2006 00:40, Andrew Morton wrote:
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> >
> > On Monday 20 February 2006 21:41, Andrew Morton wrote:
> > > MIke Galbraith <efault@gmx.de> wrote:
> > > >
> > > > On Mon, 2006-02-20 at 16:07 +0100, Helge Hafting wrote:
> > > > > pentium IV single processor, gcc (GCC) 4.0.3 20060128
> > > > >
> > > > > During boot, I normally get:
> > > > > parport0: irq 7 detected
> > > > > lp0: using parport0 (polling).
> > > > >
> > > > > Instead, I got this, written by hand:
> > > >
> > > > ........
> > > >
> > > > > This oops is simplified. I can get the exact text if
> > > > > that really matters. It is much more to write down and
> > > > > I don't usually have my camera at work.
> > > >
> > > > I get the same, and already have the serial console hooked up.
> > > >
> > > > BUG: unable to handle kernel NULL pointer dereference at virtual address 000000e8
> > >
> > > Thanks. Could someone try reverting
> > > register-sysfs-device-for-lp-devices.patch?
> >
> > That helps on my system.
>
> OK, thanks. I'll drop it.
>
> > An unrelated problem is that USB host drivers (ohci-hcd, ehci-hcd) refuse to
> > suspend. [Investigating ...]
>
> Me too.
>
> Try reverting reset-pci-device-state-to-unknown-after-disabled.patch.
Heh, that actually helps. :-) Still I have no idea why is that so ...
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble?
2006-02-21 0:02 ` Rafael J. Wysocki
@ 2006-02-21 0:09 ` Andrew Morton
2006-02-21 0:20 ` Rafael J. Wysocki
2006-02-22 11:44 ` Rafael J. Wysocki
1 sibling, 1 reply; 62+ messages in thread
From: Andrew Morton @ 2006-02-21 0:09 UTC (permalink / raw)
To: Rafael J. Wysocki; +Cc: efault, helge.hafting, linux-kernel, brlink
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
> > > An unrelated problem is that USB host drivers (ohci-hcd, ehci-hcd) refuse to
> > > suspend. [Investigating ...]
> >
> > Me too.
> >
> > Try reverting reset-pci-device-state-to-unknown-after-disabled.patch.
>
> Heh, that actually helps. :-) Still I have no idea why is that so ...
Because some PCI drivers do pci_disable_device() before
pci_set_power_state(). pci_set_power_state() sees PCI_UNKNOWN and runs
away in terror.
Whether those drivers _should_ be setting the power state of a disabled
device is an open question...
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble?
2006-02-21 0:09 ` Andrew Morton
@ 2006-02-21 0:20 ` Rafael J. Wysocki
0 siblings, 0 replies; 62+ messages in thread
From: Rafael J. Wysocki @ 2006-02-21 0:20 UTC (permalink / raw)
To: Andrew Morton; +Cc: efault, helge.hafting, linux-kernel, brlink
On Tuesday 21 February 2006 01:09, Andrew Morton wrote:
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> >
> > > > An unrelated problem is that USB host drivers (ohci-hcd, ehci-hcd) refuse to
> > > > suspend. [Investigating ...]
> > >
> > > Me too.
> > >
> > > Try reverting reset-pci-device-state-to-unknown-after-disabled.patch.
> >
> > Heh, that actually helps. :-) Still I have no idea why is that so ...
>
> Because some PCI drivers do pci_disable_device() before
> pci_set_power_state(). pci_set_power_state() sees PCI_UNKNOWN and runs
> away in terror.
Now I see that. Thanks!
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble?
2006-02-21 0:02 ` Rafael J. Wysocki
2006-02-21 0:09 ` Andrew Morton
@ 2006-02-22 11:44 ` Rafael J. Wysocki
2006-02-22 11:56 ` Andrew Morton
1 sibling, 1 reply; 62+ messages in thread
From: Rafael J. Wysocki @ 2006-02-22 11:44 UTC (permalink / raw)
To: Andrew Morton; +Cc: efault, helge.hafting, linux-kernel, Bernhard R. Link
On Tuesday 21 February 2006 01:02, Rafael J. Wysocki wrote:
> On Tuesday 21 February 2006 00:40, Andrew Morton wrote:
> > "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> > >
> > > On Monday 20 February 2006 21:41, Andrew Morton wrote:
> > > > MIke Galbraith <efault@gmx.de> wrote:
> > > > >
> > > > > On Mon, 2006-02-20 at 16:07 +0100, Helge Hafting wrote:
> > > > > > pentium IV single processor, gcc (GCC) 4.0.3 20060128
> > > > > >
> > > > > > During boot, I normally get:
> > > > > > parport0: irq 7 detected
> > > > > > lp0: using parport0 (polling).
> > > > > >
> > > > > > Instead, I got this, written by hand:
> > > > >
> > > > > ........
> > > > >
> > > > > > This oops is simplified. I can get the exact text if
> > > > > > that really matters. It is much more to write down and
> > > > > > I don't usually have my camera at work.
> > > > >
> > > > > I get the same, and already have the serial console hooked up.
> > > > >
> > > > > BUG: unable to handle kernel NULL pointer dereference at virtual address 000000e8
> > > >
> > > > Thanks. Could someone try reverting
> > > > register-sysfs-device-for-lp-devices.patch?
> > >
> > > That helps on my system.
> >
> > OK, thanks. I'll drop it.
> >
> > > An unrelated problem is that USB host drivers (ohci-hcd, ehci-hcd) refuse to
> > > suspend. [Investigating ...]
> >
> > Me too.
> >
> > Try reverting reset-pci-device-state-to-unknown-after-disabled.patch.
>
> Heh, that actually helps. :-)
Well, after reverting the reset-pci-device-state-to-unknown-after-disabled.patch
my usb controllers actually suspend, but they don't seem to resume properly
(eg. the USB mouse I am addicted to doesn't work after resume).
Greetings,
Rafael
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble?
2006-02-22 11:44 ` Rafael J. Wysocki
@ 2006-02-22 11:56 ` Andrew Morton
2006-02-22 18:19 ` Rafael J. Wysocki
0 siblings, 1 reply; 62+ messages in thread
From: Andrew Morton @ 2006-02-22 11:56 UTC (permalink / raw)
To: Rafael J. Wysocki; +Cc: efault, helge.hafting, linux-kernel, brlink
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
> > > Try reverting reset-pci-device-state-to-unknown-after-disabled.patch.
> >
> > Heh, that actually helps. :-)
>
> Well, after reverting the reset-pci-device-state-to-unknown-after-disabled.patch
> my usb controllers actually suspend, but they don't seem to resume properly
> (eg. the USB mouse I am addicted to doesn't work after resume).
Ho hum. Revert
pm-add-state-field-to-pm_message_t-to-hold-actual.patch
pm-respect-the-actual-device-power-states-in-sysfs.patch
pm-minor-updates-to-core-suspend-resume-functions.patch
pm-make-pci_choose_state-use-the-real-device.patch
Eventually we'll end up at 2.6.16-rc4 ;)
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble?
2006-02-22 11:56 ` Andrew Morton
@ 2006-02-22 18:19 ` Rafael J. Wysocki
0 siblings, 0 replies; 62+ messages in thread
From: Rafael J. Wysocki @ 2006-02-22 18:19 UTC (permalink / raw)
To: Andrew Morton; +Cc: efault, helge.hafting, linux-kernel, brlink
On Wednesday 22 February 2006 12:56, Andrew Morton wrote:
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> >
> > > > Try reverting reset-pci-device-state-to-unknown-after-disabled.patch.
> > >
> > > Heh, that actually helps. :-)
> >
> > Well, after reverting the reset-pci-device-state-to-unknown-after-disabled.patch
> > my usb controllers actually suspend, but they don't seem to resume properly
> > (eg. the USB mouse I am addicted to doesn't work after resume).
>
> Ho hum. Revert
>
> pm-add-state-field-to-pm_message_t-to-hold-actual.patch
> pm-respect-the-actual-device-power-states-in-sysfs.patch
> pm-minor-updates-to-core-suspend-resume-functions.patch
> pm-make-pci_choose_state-use-the-real-device.patch
Thanks, that helped. Everything seems to be OK now. :-)
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble?
2006-02-20 15:25 ` MIke Galbraith
2006-02-20 20:41 ` Andrew Morton
@ 2006-02-20 22:58 ` Rafael J. Wysocki
1 sibling, 0 replies; 62+ messages in thread
From: Rafael J. Wysocki @ 2006-02-20 22:58 UTC (permalink / raw)
To: Andrew Morton; +Cc: MIke Galbraith, Helge Hafting, linux-kernel
On Monday 20 February 2006 16:25, MIke Galbraith wrote:
> On Mon, 2006-02-20 at 16:07 +0100, Helge Hafting wrote:
> > pentium IV single processor, gcc (GCC) 4.0.3 20060128
> >
> > During boot, I normally get:
> > parport0: irq 7 detected
> > lp0: using parport0 (polling).
> >
> > Instead, I got this, written by hand:
>
> ........
>
> > This oops is simplified. I can get the exact text if
> > that really matters. It is much more to write down and
> > I don't usually have my camera at work.
>
> I get the same, and already have the serial console hooked up.
Similar thing on x86-64 (Asus L5D), but less drastic. I can boot, but get:
Unable to handle kernel NULL pointer dereference at 00000000000001bc RIP:
<ffffffff8024f7dc>{kref_get+12}
PGD 2c788067 PUD 2c796067 PMD 0
Oops: 0000 [1] PREEMPT
last sysfs file: /block/hdc/range
CPU 0
Modules linked in: parport_pc lp parport dm_mod
Pid: 1452, comm: modprobe Not tainted 2.6.16-rc4-mm1 #56
RIP: 0010:[<ffffffff8024f7dc>] <ffffffff8024f7dc>{kref_get+12}
RSP: 0018:ffff81002c7bbca8 EFLAGS: 00010292
RAX: ffff81002acd8970 RBX: 00000000000001bc RCX: ffff81002acd8000
RDX: ffff81002acd8977 RSI: ffffffff803af6a6 RDI: 00000000000001bc
RBP: ffff81002c7bbcb8 R08: 0000000000000000 R09: ffff81002acd8970
R10: 0000000000000001 R11: 2222222222222222 R12: ffffffff803af69f
R13: ffff81002c7641f0 R14: 00000000fffffff4 R15: ffff81002a574160
FS: 00002b1185fabb00(0000) GS:ffffffff8058a000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00000000000001bc CR3: 000000002de28000 CR4: 00000000000006e0
Process modprobe (pid: 1452, threadinfo ffff81002c7ba000, task ffff81002fecf830)
Stack: ffff81002c7bbcd8 00000000000001a0 ffff81002c7bbcd8 ffffffff8024eb4a
ffff81002c7641f0 ffff81002acd89a8 ffff81002c7bbd18 ffffffff801c442d
00000000000001a0 ffff81002e76c5b0
Call Trace: <ffffffff8024eb4a>{kobject_get+26} <ffffffff801c442d>{sysfs_create_link+173}
<ffffffff802b6b76>{class_device_add+550} <ffffffff802b6cb9>{class_device_register+25}
<ffffffff802b6dc2>{class_device_create+258} <ffffffff88016ce2>{:parport:parport_device_proc_register+242}
<ffffffff88014207>{:parport:parport_register_device+663}
<ffffffff88021040>{:lp:lp_preempt+0} <ffffffff88013abc>{:parport:parport_register_driver+44}
<ffffffff8802174e>{:lp:lp_register+158} <ffffffff880217db>{:lp:lp_attach+75}
<ffffffff88013adf>{:parport:parport_register_driver+79}
<ffffffff880262a3>{:lp:lp_init_module+675} <ffffffff8014b9a4>{sys_init_module+212}
<ffffffff80109cca>{system_call+126}
Code: 8b 07 85 c0 75 24 48 c7 c1 50 f3 37 80 ba 20 00 00 00 48 c7
RIP <ffffffff8024f7dc>{kref_get+12} RSP <ffff81002c7bbca8>
CR2: 00000000000001bc
BUG: modprobe/1452, lock held at task exit time!
[ffffffff8801eb20] {registration_lock}
.. held by: modprobe: 1452 [ffff81002fecf830, 116]
... acquired at: parport_register_driver+0x2c/0x90 [parport]
and the thing called /sbin/udevstart ends up in the D state because of this.
Greetings,
Rafael
^ permalink raw reply [flat|nested] 62+ messages in thread
[parent not found: <6bffcb0e0602200533p1a3da98ew@mail.gmail.com>]
* Re: 2.6.16-rc4-mm1
[not found] ` <6bffcb0e0602200533p1a3da98ew@mail.gmail.com>
@ 2006-02-20 16:33 ` Greg KH
0 siblings, 0 replies; 62+ messages in thread
From: Greg KH @ 2006-02-20 16:33 UTC (permalink / raw)
To: Michal Piotrowski; +Cc: Andrew Morton, linux-kernel
On Mon, Feb 20, 2006 at 02:33:44PM +0100, Michal Piotrowski wrote:
> Hi,
>
> On 20/02/06, Andrew Morton <akpm@osdl.org> wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc4/2.6.16-rc4-mm1/
> >
> [snip]
> > +gregkh-usb-usb-initdata-fixes.patch
> > +gregkh-usb-usbfs2.patch
> >
> > USB tree updates
>
> I have noticed this:
>
> drivers/built-in.o: In function
> `securityfs_create_dir':/usr/src/linux-mm/drivers/usb/usbfs2/usbfs2.c:271:
> multiple definition of `securityfs_create_dir'
Yeah, usbfs2 was a copy of securityfs, and can't be built into the
kernel just yet. You can safely disable usbfs2 for now, as it's still a
work in progress and doesn't really work at all.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-20 12:26 2.6.16-rc4-mm1 Andrew Morton
` (5 preceding siblings ...)
[not found] ` <6bffcb0e0602200533p1a3da98ew@mail.gmail.com>
@ 2006-02-20 17:54 ` Bernhard Rosenkraenzer
2006-02-20 19:25 ` [PATCH -mm HOT-FIX] fix build on ia64 (modpost.c) Sam Ravnborg
` (3 subsequent siblings)
10 siblings, 0 replies; 62+ messages in thread
From: Bernhard Rosenkraenzer @ 2006-02-20 17:54 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Monday, 20. February 2006 13:26, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc4/2.
>6.16-rc4-mm1/
Doesn't compile on boxes without ccache -- patch below:
Don't depend on ccache, but use it if it's there
Signed-off-by: Bernhard Rosenkraenzer <bero@arklinux.org>
--- linux-2.6.15/Makefile.ark 2006-02-20 18:09:54.000000000 +0100
+++ linux-2.6.15/Makefile 2006-02-20 18:15:37.000000000 +0100
@@ -274,7 +274,7 @@
AS = $(CROSS_COMPILE)as
LD = $(CROSS_COMPILE)ld
-CC = ccache $(CROSS_COMPILE)gcc
+CC = $(shell ccache --version &>/dev/null && echo ccache)
$(CROSS_COMPILE)gcc
CPP = $(CC) -E
AR = $(CROSS_COMPILE)ar
NM = $(CROSS_COMPILE)nm
^ permalink raw reply [flat|nested] 62+ messages in thread* [PATCH -mm HOT-FIX] fix build on ia64 (modpost.c)
2006-02-20 12:26 2.6.16-rc4-mm1 Andrew Morton
` (6 preceding siblings ...)
2006-02-20 17:54 ` 2.6.16-rc4-mm1 Bernhard Rosenkraenzer
@ 2006-02-20 19:25 ` Sam Ravnborg
2006-02-20 21:37 ` Andrew Morton
2006-02-21 8:14 ` 2.6.16-rc4-mm1 Laurent Riffard
` (2 subsequent siblings)
10 siblings, 1 reply; 62+ messages in thread
From: Sam Ravnborg @ 2006-02-20 19:25 UTC (permalink / raw)
To: Andrew Morton, LKML, linux-ia64; +Cc: linux-kernel
>
> - This kernel won't compile on ia64 (and possibly other architectures)
> because the kbuild tree is using Elf_Rela in scripts/mod/modpost.c. Is OK
> on x86, x86_64 and powerpc. Sam might send a hotfix?
Attached is a real hot-fix. It disables the new check entirely.
I like to learn:
1) Why IA64 is missing Elf64_Rela. Can someone drop me a copy of elf.h -
and include gcc + binutils version in the mail - thanks.
2) I also like to know if other architectures broke - so I can figure
out how to fix this.
I have tested this on X86_64/amd64 (gentoo based) only.
Sam
diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
index 844f84b..b87070a 100644
--- a/scripts/mod/modpost.c
+++ b/scripts/mod/modpost.c
@@ -451,6 +451,7 @@ static char *get_modinfo(void *modinfo,
return NULL;
}
+#if 0
/**
* Find symbol based on relocation record info.
* In some cases the symbol supplied is a valid symbol so
@@ -616,7 +617,12 @@ static void check_sec_ref(struct module
}
}
}
-
+#endif
+static void check_sec_ref(struct module *mod, const char *modname,
+ struct elf_info *elf,
+ int section(const char*),
+ int section_ref_ok(const char *))
+{}
/**
* Functions used only during module init is marked __init and is stored in
* a .init.text section. Likewise data is marked __initdata and stored in
^ permalink raw reply related [flat|nested] 62+ messages in thread* Re: [PATCH -mm HOT-FIX] fix build on ia64 (modpost.c)
2006-02-20 19:25 ` [PATCH -mm HOT-FIX] fix build on ia64 (modpost.c) Sam Ravnborg
@ 2006-02-20 21:37 ` Andrew Morton
0 siblings, 0 replies; 62+ messages in thread
From: Andrew Morton @ 2006-02-20 21:37 UTC (permalink / raw)
To: Sam Ravnborg; +Cc: linux-kernel, linux-ia64, Ingo Molnar
Sam Ravnborg <sam@ravnborg.org> wrote:
>
> >
> > - This kernel won't compile on ia64 (and possibly other architectures)
> > because the kbuild tree is using Elf_Rela in scripts/mod/modpost.c. Is OK
> > on x86, x86_64 and powerpc. Sam might send a hotfix?
>
> Attached is a real hot-fix. It disables the new check entirely.
Well that bit compiles.
> I like to learn:
> 1) Why IA64 is missing Elf64_Rela. Can someone drop me a copy of elf.h -
> and include gcc + binutils version in the mail - thanks.
This thing's running RHAS2.1 which I think dates from before the invention
of the transistor. Running home-made gcc-3.3.2 and binutils-2.14.90.0.6-1.
I'll send along the three elf.h's under /usr/include.
> 2) I also like to know if other architectures broke - so I can figure
> out how to fix this.
Dunno yet - I didn't do the normal batch of cross-compiles due to spending
six hours chasing down new bugs.
> I have tested this on X86_64/amd64 (gentoo based) only.
That fixes the modpost.c compile, but the new futex stuff fails because
ia64 doesn't implement ptr_to_compat(). In fact only three architectures
appear to do so.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-20 12:26 2.6.16-rc4-mm1 Andrew Morton
` (7 preceding siblings ...)
2006-02-20 19:25 ` [PATCH -mm HOT-FIX] fix build on ia64 (modpost.c) Sam Ravnborg
@ 2006-02-21 8:14 ` Laurent Riffard
2006-02-21 8:16 ` 2.6.16-rc4-mm1 Andrew Morton
2006-02-21 19:00 ` 2.6.16-rc4-mm1 console (radeonfb) not resumed after s2ram Mattia Dongili
2006-02-22 13:47 ` 2.6.16-rc4-mm1 Alexander E. Patrakov
10 siblings, 1 reply; 62+ messages in thread
From: Laurent Riffard @ 2006-02-21 8:14 UTC (permalink / raw)
To: Kernel development list, Al Viro; +Cc: Andrew Morton
[-- Attachment #1: Type: text/plain, Size: 3637 bytes --]
Le 20.02.2006 13:26, Andrew Morton a écrit :
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc4/2.6.16-rc4-mm1/
>
[snip]
> git-viro-bird.patch
[snip]
This one seems to break ne2k-pci for me. Kernel gets an
oops when the module is inserted. Reverting git-viro-bird*
solves the problem.
ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker
http://www.scyld.com/network/ne2k-pci.html
ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5
BUG: unable to handle kernel paging request at virtual address 0000a000
printing eip:
e0f285dd
*pde = 00000000
Oops: 0002 [#1]
last sysfs file: /block/fd0/removable
Modules linked in: ne2k_pci 8390 af_packet floppy ide_cd cdrom loop aes dm_crypt nls_iso8859_1 nls_cp850 vfat fat reiser4 reiserfs raid1 md_mod via_agp agpgart video joydev usbhid ohci1394 ieee1394 uhci_hcd usbcore dm_mirror dm_mod
CPU: 0
EIP: 0060:[pg0+548873693/1069843456] Not tainted VLI
EIP: 0060:[<e0f285dd>] Not tainted VLI
EFLAGS: 00210213 (2.6.16-rc4-mm1 #102)
EIP is at __NS8390_init+0x33/0x101 [8390]
eax: 00000049 ebx: 00000049 ecx: 0000a000 edx: db0cca60
esi: db0cc800 edi: 0000a000 ebp: dac5dd2c esp: dac5dd0c
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 1574, threadinfo=dac5d000 task=dfe49a70)
Feb 20 20:57:51 antares acpid: Démarrage de acpid succeeded
Stack: <0>00000000 dac5dd2c c0229724 e0f28487 000000a0 dfe12048 db0cc800 0000a000
dac5dd34 e0f286b3 dac5dd98 e0f2b796 dfe12000 00000005 00000000 00000040
dff578a0 40000202 2d6e4695 00000000 97220501 40005757 2d6e4695 00000000
Call Trace:
[show_stack_log_lvl+160/171] show_stack_log_lvl+0xa0/0xab
[<c0103a11>] show_stack_log_lvl+0xa0/0xab
[show_registers+291/393] show_registers+0x123/0x189
[<c0103b3f>] show_registers+0x123/0x189
[die+309/441] die+0x135/0x1b9
[<c0103e05>] die+0x135/0x1b9
[do_page_fault+959/1279] do_page_fault+0x3bf/0x4ff
[<c01114b3>] do_page_fault+0x3bf/0x4ff
[error_code+79/84] error_code+0x4f/0x54
[<c01034c3>] error_code+0x4f/0x54
[pg0+548873907/1069843456] NS8390_init+0x8/0xa [8390]
[<e0f286b3>] NS8390_init+0x8/0xa [8390]
[pg0+548886422/1069843456] ne2k_pci_init_one+0x26d/0x358 [ne2k_pci]
[<e0f2b796>] ne2k_pci_init_one+0x26d/0x358 [ne2k_pci]
[pci_device_probe+57/89] pci_device_probe+0x39/0x59
[<c01a98ca>] pci_device_probe+0x39/0x59
[driver_probe_device+69/152] driver_probe_device+0x45/0x98
[<c020335f>] driver_probe_device+0x45/0x98
[__driver_attach+99/137] __driver_attach+0x63/0x89
[<c020348b>] __driver_attach+0x63/0x89
[bus_for_each_dev+55/92] bus_for_each_dev+0x37/0x5c
[<c0202aab>] bus_for_each_dev+0x37/0x5c
[driver_attach+20/23] driver_attach+0x14/0x17
[<c0203254>] driver_attach+0x14/0x17
[bus_add_driver+99/234] bus_add_driver+0x63/0xea
[<c0202d3a>] bus_add_driver+0x63/0xea
[driver_register+118/123] driver_register+0x76/0x7b
[<c0203839>] driver_register+0x76/0x7b
[__pci_register_driver+92/122] __pci_register_driver+0x5c/0x7a
[<c01a9575>] __pci_register_driver+0x5c/0x7a
[pg0+548900892/1069843456] ne2k_pci_init+0x1c/0x1e [ne2k_pci]
[<e0f2f01c>] ne2k_pci_init+0x1c/0x1e [ne2k_pci]
[sys_init_module+5409/5617] sys_init_module+0x1521/0x15f1
[<c012a1a0>] sys_init_module+0x1521/0x15f1
[sysenter_past_esp+84/117] sysenter_past_esp+0x54/0x75
[<c01029af>] sysenter_past_esp+0x54/0x75
Code: bb 48 00 00 00 83 ec 14 89 55 e0 8d 90 60 02 00 00 8b 48 20 8a 42 28 a8 02 74 0d 83 e0 04 3c 01 19 db 83 e3 fe 83 c3 4b 0f b6 c3 <c6> 01 21 8d 59 0d 88 41 0e 8d 41 0c c6 41 0a 00 c6 41 0b 00 8d
<7>parport_pc: VIA 686A/8231 detected
parport_pc: probing current configuration
~~
laurent
[-- Attachment #2: config-2.6.16-rc4-mm1 --]
[-- Type: text/plain, Size: 41966 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.16-rc4-mm1
# Tue Feb 21 08:42:08 2006
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
CONFIG_INITRAMFS_SOURCE=""
CONFIG_UID16=y
CONFIG_VM86=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_EMBEDDED=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
CONFIG_SLAB=y
CONFIG_SERIAL_PCI=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
#
# Block layer
#
# CONFIG_LBD is not set
# CONFIG_LSF is not set
# CONFIG_BLK_DEV_IO_TRACE 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_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
CONFIG_X86_TSC=y
CONFIG_HPET_TIMER=y
# CONFIG_SMP is not set
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=m
CONFIG_X86_MCE_P4THERMAL=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_X86_REBOOTFIXUPS=y
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=m
# CONFIG_X86_CPUID is not set
#
# Firmware Drivers
#
CONFIG_EDD=y
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_3G_OPT is not set
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_REGPARM=y
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_KEXEC=y
CONFIG_PHYSICAL_START=0x100000
CONFIG_DOUBLEFAULT=y
#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
# CONFIG_PM_DEBUG is not set
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION="/dev/hdb6"
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_SLEEP_PROC_SLEEP is not set
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_HOTKEY=m
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_SONY is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_ACPI_DEBUG=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_CONTAINER is not set
#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCIEPORTBUS is not set
# CONFIG_PCI_MSI is not set
# CONFIG_PCI_LEGACY_PROC is not set
# CONFIG_PCI_DEBUG is not set
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set
#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_MISC=m
#
# Networking
#
CONFIG_NET=y
#
# Networking options
#
# CONFIG_NETDEBUG is not set
CONFIG_PACKET=m
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_MULTIPLE_TABLES is not set
# CONFIG_IP_ROUTE_MULTIPATH is not set
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_BIC=y
#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
#
# Core Netfilter Configuration
#
# CONFIG_NETFILTER_NETLINK is not set
# CONFIG_NETFILTER_XTABLES is not set
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
# CONFIG_IP_NF_CT_ACCT is not set
# CONFIG_IP_NF_CONNTRACK_MARK is not set
# CONFIG_IP_NF_CONNTRACK_EVENTS is not set
# CONFIG_IP_NF_CT_PROTO_SCTP is not set
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
# CONFIG_IP_NF_NETBIOS_NS is not set
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_AMANDA=m
# CONFIG_IP_NF_PPTP is not set
CONFIG_IP_NF_QUEUE=m
#
# DCCP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
#
# TIPC Configuration (EXPERIMENTAL)
#
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q 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_NET_DIVERT 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_CLK_JIFFIES=y
# CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set
# CONFIG_NET_SCH_CLK_CPU is not set
#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
# CONFIG_NET_SCH_NETEM is not set
CONFIG_NET_SCH_INGRESS=m
#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
# 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_CLS_IND is not set
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_IEEE80211 is not set
CONFIG_WIRELESS_EXT=y
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
# CONFIG_DEBUG_DRIVER is not set
#
# Connector - unified userspace <-> kernelspace linker
#
# CONFIG_CONNECTOR is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
# 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_1284=y
#
# Plug and Play support
#
# CONFIG_PNP is not set
#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# 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=m
# 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=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
# CONFIG_ATA_OVER_ETH is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=m
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=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_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_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_SC1200 is not set
# CONFIG_BLK_DEV_PIIX 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=y
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
# CONFIG_CHR_DEV_SCH is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set
#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SAS_CLASS is not set
#
# SCSI low-level drivers
#
# 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_DPT_I2O 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_SATA 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_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR 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_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_LPFC 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
#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_RAID6 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
CONFIG_BLK_DEV_DM=m
CONFIG_DM_CRYPT=m
# CONFIG_DM_SNAPSHOT is not set
CONFIG_DM_MIRROR=m
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH 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_IEEE1394=m
#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
CONFIG_IEEE1394_OUI_DB=y
# CONFIG_IEEE1394_EXTRA_CONFIG_ROMS is not set
# CONFIG_IEEE1394_EXPORT_FULL_API is not set
#
# Device Drivers
#
# CONFIG_IEEE1394_PCILYNX is not set
CONFIG_IEEE1394_OHCI1394=m
#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
# CONFIG_IEEE1394_SBP2 is not set
# CONFIG_IEEE1394_ETH1394 is not set
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Network device support
#
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
#
# PHY device support
#
# CONFIG_PHYLIB is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
CONFIG_NE2K_PCI=m
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_NET_POCKET is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_CHELSIO_T1 is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
#
# Wireless LAN (non-hamradio)
#
CONFIG_NET_RADIO=y
#
# Obsolete Wireless cards support (pre-802.11)
#
# CONFIG_STRIP is not set
# CONFIG_ARLAN is not set
# CONFIG_WAVELAN is not set
#
# Wireless 802.11b ISA/PCI cards support
#
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not set
# CONFIG_AIRO is not set
# CONFIG_HERMES is not set
# CONFIG_ATMEL is not set
#
# Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support
#
CONFIG_PRISM54=m
# CONFIG_HOSTAP is not set
# CONFIG_ACX is not set
CONFIG_NET_WIRELESS=y
#
# Wan interfaces
#
# 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=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
# CONFIG_PPP_MPPE is not set
CONFIG_PPPOE=m
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
CONFIG_NETCONSOLE=m
# CONFIG_KGDBOE is not set
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_RX is not set
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA is not set
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
# 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_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_WISTRON_BTNS is not set
# CONFIG_INPUT_UINPUT is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_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=m
# CONFIG_GAMEPORT_NS558 is not set
# CONFIG_GAMEPORT_L4 is not set
# CONFIG_GAMEPORT_EMU10K1 is not set
# CONFIG_GAMEPORT_FM801 is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=m
# CONFIG_SERIAL_8250_ACPI is not set
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 is not set
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=m
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# 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=m
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON 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_CS5535_GPIO is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set
#
# TPM devices
#
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
#
# I2C support
#
CONFIG_I2C=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 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_ELEKTOR is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_PIIX4 is not set
CONFIG_I2C_ISA=m
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_STUB is not set
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set
#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_RTC8564 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_RTC_X1205_I2C is not set
# 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 is not set
# CONFIG_SPI_MASTER is not set
#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
#
# Hardware Monitoring support
#
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_F71805F is not set
# 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_IT87 is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
CONFIG_SENSORS_LM80=m
# 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_PC87360 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
CONFIG_SENSORS_VIA686A=m
# CONFIG_SENSORS_VT8231 is not set
CONFIG_SENSORS_W83781D=m
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Misc devices
#
# CONFIG_IBM_ASM is not set
#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
#
# Video For Linux
#
#
# Video Adapters
#
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_PMS is not set
# CONFIG_VIDEO_BWQCAM is not set
# CONFIG_VIDEO_CQCAM is not set
# CONFIG_VIDEO_W9966 is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set
# CONFIG_VIDEO_EM28XX is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
# CONFIG_VIDEO_AUDIO_DECODER is not set
# CONFIG_VIDEO_DECODER is not set
#
# Radio Adapters
#
# CONFIG_RADIO_CADET is not set
# CONFIG_RADIO_RTRACK is not set
# CONFIG_RADIO_RTRACK2 is not set
# CONFIG_RADIO_AZTECH is not set
# CONFIG_RADIO_GEMTEK is not set
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set
# CONFIG_RADIO_SF16FMI is not set
# CONFIG_RADIO_SF16FMR2 is not set
# CONFIG_RADIO_TERRATEC is not set
# CONFIG_RADIO_TRUST is not set
# CONFIG_RADIO_TYPHOON is not set
# CONFIG_RADIO_ZOLTRIX is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_MACMODES is not set
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
# 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_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
CONFIG_FB_NVIDIA=m
CONFIG_FB_NVIDIA_I2C=y
CONFIG_FB_RIVA=m
CONFIG_FB_RIVA_I2C=y
# CONFIG_FB_RIVA_DEBUG is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY 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_CYBLA is not set
# CONFIG_FB_TRIDENT 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_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
#
# Sound
#
CONFIG_SOUND=m
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
# CONFIG_SND_MIXER_OSS is not set
# CONFIG_SND_PCM_OSS is not set
# CONFIG_SND_SEQUENCER_OSS is not set
# CONFIG_SND_RTCTIMER is not set
# CONFIG_SND_DYNAMIC_MINORS is not set
# CONFIG_SND_SUPPORT_OLD_API is not set
# CONFIG_SND_VERBOSE_PROCFS is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_AC97_BUS=m
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
#
# ISA devices
#
# CONFIG_SND_AD1848 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_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_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_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_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_CS5535AUDIO is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
CONFIG_SND_ENS1371=m
# 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_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
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
CONFIG_USB_DYNAMIC_MINORS=y
CONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not set
CONFIG_USB_USBFS2=m
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
# CONFIG_USB_EHCI_SPLIT_ISO is not set
CONFIG_USB_EHCI_ROOT_HUB_TT=y
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=m
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_IP is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#
#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# 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_LIBUSUAL is not set
#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_ACECAD is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_ITMTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_YEALINK is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set
# CONFIG_USB_ATI_REMOTE2 is not set
# CONFIG_USB_KEYSPAN_REMOTE is not set
# CONFIG_USB_APPLETOUCH is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_ET61X251 is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_ZC0301 is not set
# CONFIG_USB_PWC is not set
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_ZD1201 is not set
# CONFIG_USB_MON is not set
#
# 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_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_GOTEMP is not set
# CONFIG_USB_PHIDGETKIT is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TEST is not set
#
# USB DSL modem support
#
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# MMC/SD Card support
#
# CONFIG_MMC is not set
#
# LED devices
#
# CONFIG_NEW_LEDS is not set
#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set
#
# SN Devices
#
#
# EDAC - error detection and reporting (RAS)
#
CONFIG_EDAC=m
#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_MM_EDAC=m
CONFIG_EDAC_AMD76X=m
CONFIG_EDAC_E7XXX=m
# CONFIG_EDAC_E752X is not set
CONFIG_EDAC_I82875P=m
# CONFIG_EDAC_I82860 is not set
CONFIG_EDAC_R82600=m
CONFIG_EDAC_POLL=y
#
# Distributed Lock Manager
#
# CONFIG_DLM is not set
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
# CONFIG_EXT2_FS_POSIX_ACL is not set
# CONFIG_EXT2_FS_SECURITY is not set
CONFIG_EXT2_FS_XIP=y
CONFIG_FS_XIP=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISER4_FS=m
CONFIG_REISER4_DEBUG=y
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=m
# CONFIG_FUSE_FS is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=850
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
# CONFIG_RELAYFS_FS is not set
CONFIG_CONFIGFS_FS=m
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ASFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_RPCSEC_GSS_KRB5=m
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
CONFIG_CIFS=m
CONFIG_CIFS_STATS=y
# CONFIG_CIFS_STATS2 is not set
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_EXPERIMENTAL 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 is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
# CONFIG_NLS_CODEPAGE_852 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=m
CONFIG_NLS_ISO8859_1=m
# 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=m
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# Instrumentation Support
#
# CONFIG_PROFILING is not set
# CONFIG_KPROBES is not set
#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_SHIRQ=y
CONFIG_DEBUG_KERNEL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_MUTEXES=y
# CONFIG_DEBUG_SPINLOCK is not set
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_PAGE_OWNER is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_DEBUG_VM is not set
CONFIG_FRAME_POINTER=y
CONFIG_UNWIND_INFO=y
CONFIG_FORCED_INLINING=y
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_DEBUG_SYNCHRO_TEST is not set
CONFIG_EARLY_PRINTK=y
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_DEBUG_STACK_USAGE is not set
CONFIG_STACK_BACKTRACE_COLS=1
#
# Page alloc debug is incompatible with Software Suspend on i386
#
CONFIG_DEBUG_RODATA=y
# CONFIG_DEBUG_INITDATA is not set
CONFIG_4KSTACKS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
# CONFIG_KGDB is not set
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=m
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
CONFIG_CRYPTO_ARC4=m
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
# CONFIG_CRYPTO_TEST is not set
#
# Hardware crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set
#
# Library routines
#
CONFIG_CRC_CCITT=m
# CONFIG_CRC16 is not set
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_KTIME_SCALAR=y
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc4-mm1 console (radeonfb) not resumed after s2ram
2006-02-20 12:26 2.6.16-rc4-mm1 Andrew Morton
` (8 preceding siblings ...)
2006-02-21 8:14 ` 2.6.16-rc4-mm1 Laurent Riffard
@ 2006-02-21 19:00 ` Mattia Dongili
2006-02-21 21:43 ` Andrew Morton
2006-02-22 13:47 ` 2.6.16-rc4-mm1 Alexander E. Patrakov
10 siblings, 1 reply; 62+ messages in thread
From: Mattia Dongili @ 2006-02-21 19:00 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Mon, Feb 20, 2006 at 04:26:15AM -0800, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc4/2.6.16-rc4-mm1/
After suspend the system is fully working except it doesn't resume the
console (I'm using radeonfb). If suspending from X the thing comes back,
X working ok, but switching to vt1 I see the console completely garbled.
Reverting radeonfb-resume-support-for-samsung-p35-laptops.patch (_wild_
guess) does not help.
Any good candidate?
My videocard:
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY (prog-if 00 [VGA])
Subsystem: Sony Corporation VAIO PCG-GR214EP/GR214MP/GR215MP/GR314MP/GR315MP
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 66 (2000ns min), Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 9
Region 0: Memory at d8000000 (32-bit, prefetchable) [size=128M]
Region 1: I/O ports at 3000 [size=256]
Region 2: Memory at d0100000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at d0120000 [disabled] [size=128K]
Capabilities: [58] AGP version 2.0
Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none>
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
--
mattia
:wq!
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc4-mm1 console (radeonfb) not resumed after s2ram
2006-02-21 19:00 ` 2.6.16-rc4-mm1 console (radeonfb) not resumed after s2ram Mattia Dongili
@ 2006-02-21 21:43 ` Andrew Morton
2006-02-22 14:24 ` Mattia Dongili
0 siblings, 1 reply; 62+ messages in thread
From: Andrew Morton @ 2006-02-21 21:43 UTC (permalink / raw)
To: Mattia Dongili; +Cc: linux-kernel
Mattia Dongili <malattia@linux.it> wrote:
>
> On Mon, Feb 20, 2006 at 04:26:15AM -0800, Andrew Morton wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc4/2.6.16-rc4-mm1/
>
> After suspend the system is fully working except it doesn't resume the
> console (I'm using radeonfb). If suspending from X the thing comes back,
> X working ok, but switching to vt1 I see the console completely garbled.
> Reverting radeonfb-resume-support-for-samsung-p35-laptops.patch (_wild_
> guess) does not help.
> Any good candidate?
>
Did you apply the patches in the hot-fixes directory?
revert-reset-pci-device-state-to-unknown-after-disabled.patch might help.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1 console (radeonfb) not resumed after s2ram
2006-02-21 21:43 ` Andrew Morton
@ 2006-02-22 14:24 ` Mattia Dongili
2006-02-22 19:39 ` Mattia Dongili
0 siblings, 1 reply; 62+ messages in thread
From: Mattia Dongili @ 2006-02-22 14:24 UTC (permalink / raw)
To: Andrew Morton; +Cc: Mattia Dongili, linux-kernel
On Tue, February 21, 2006 10:43 pm, Andrew Morton said:
> Mattia Dongili <malattia@linux.it> wrote:
>>
>> On Mon, Feb 20, 2006 at 04:26:15AM -0800, Andrew Morton wrote:
>> >
>> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc4/2.6.16-rc4-mm1/
>>
>> After suspend the system is fully working except it doesn't resume the
>> console (I'm using radeonfb). If suspending from X the thing comes back,
>> X working ok, but switching to vt1 I see the console completely garbled.
>> Reverting radeonfb-resume-support-for-samsung-p35-laptops.patch (_wild_
>> guess) does not help.
>> Any good candidate?
>
> Did you apply the patches in the hot-fixes directory?
> revert-reset-pci-device-state-to-unknown-after-disabled.patch might help.
Sorry, this didn't help either. I'll try to revert some suspend related
patches then go bisecting if still unsuccessful.
--
mattia
:wq!
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1 console (radeonfb) not resumed after s2ram
2006-02-22 14:24 ` Mattia Dongili
@ 2006-02-22 19:39 ` Mattia Dongili
2006-02-22 20:40 ` Andrew Morton
0 siblings, 1 reply; 62+ messages in thread
From: Mattia Dongili @ 2006-02-22 19:39 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Wed, Feb 22, 2006 at 03:24:38PM +0100, Mattia Dongili wrote:
> On Tue, February 21, 2006 10:43 pm, Andrew Morton said:
> > Mattia Dongili <malattia@linux.it> wrote:
> >>
> >> On Mon, Feb 20, 2006 at 04:26:15AM -0800, Andrew Morton wrote:
> >> >
> >> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc4/2.6.16-rc4-mm1/
> >>
> >> After suspend the system is fully working except it doesn't resume the
> >> console (I'm using radeonfb). If suspending from X the thing comes back,
> >> X working ok, but switching to vt1 I see the console completely garbled.
> >> Reverting radeonfb-resume-support-for-samsung-p35-laptops.patch (_wild_
> >> guess) does not help.
> >> Any good candidate?
> >
> > Did you apply the patches in the hot-fixes directory?
> > revert-reset-pci-device-state-to-unknown-after-disabled.patch might help.
>
> Sorry, this didn't help either. I'll try to revert some suspend related
> patches then go bisecting if still unsuccessful.
Ok, reverting the same 4 patches as suggested to Rafael J. Wysocki
restores the correct behaviour:
pm-add-state-field-to-pm_message_t-to-hold-actual.patch
pm-respect-the-actual-device-power-states-in-sysfs.patch
pm-minor-updates-to-core-suspend-resume-functions.patch
pm-make-pci_choose_state-use-the-real-device.patch
Are they indipendent? Would you want me to track the exact one
introducing the bug?
--
mattia
:wq!
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1 console (radeonfb) not resumed after s2ram
2006-02-22 19:39 ` Mattia Dongili
@ 2006-02-22 20:40 ` Andrew Morton
0 siblings, 0 replies; 62+ messages in thread
From: Andrew Morton @ 2006-02-22 20:40 UTC (permalink / raw)
To: Mattia Dongili; +Cc: linux-kernel
Mattia Dongili <malattia@linux.it> wrote:
>
> On Wed, Feb 22, 2006 at 03:24:38PM +0100, Mattia Dongili wrote:
> > On Tue, February 21, 2006 10:43 pm, Andrew Morton said:
> > > Mattia Dongili <malattia@linux.it> wrote:
> > >>
> > >> On Mon, Feb 20, 2006 at 04:26:15AM -0800, Andrew Morton wrote:
> > >> >
> > >> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc4/2.6.16-rc4-mm1/
> > >>
> > >> After suspend the system is fully working except it doesn't resume the
> > >> console (I'm using radeonfb). If suspending from X the thing comes back,
> > >> X working ok, but switching to vt1 I see the console completely garbled.
> > >> Reverting radeonfb-resume-support-for-samsung-p35-laptops.patch (_wild_
> > >> guess) does not help.
> > >> Any good candidate?
> > >
> > > Did you apply the patches in the hot-fixes directory?
> > > revert-reset-pci-device-state-to-unknown-after-disabled.patch might help.
> >
> > Sorry, this didn't help either. I'll try to revert some suspend related
> > patches then go bisecting if still unsuccessful.
>
> Ok, reverting the same 4 patches as suggested to Rafael J. Wysocki
> restores the correct behaviour:
>
> pm-add-state-field-to-pm_message_t-to-hold-actual.patch
> pm-respect-the-actual-device-power-states-in-sysfs.patch
> pm-minor-updates-to-core-suspend-resume-functions.patch
> pm-make-pci_choose_state-use-the-real-device.patch
>
> Are they indipendent? Would you want me to track the exact one
> introducing the bug?
>
Is OK, thanks - I have already passed that info on to Pat and I dropped all
four.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-20 12:26 2.6.16-rc4-mm1 Andrew Morton
` (9 preceding siblings ...)
2006-02-21 19:00 ` 2.6.16-rc4-mm1 console (radeonfb) not resumed after s2ram Mattia Dongili
@ 2006-02-22 13:47 ` Alexander E. Patrakov
2006-02-22 15:26 ` 2.6.16-rc4-mm1 Alexander E. Patrakov
` (2 more replies)
10 siblings, 3 replies; 62+ messages in thread
From: Alexander E. Patrakov @ 2006-02-22 13:47 UTC (permalink / raw)
To: Andrew Morton, LKML
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc4/2.6.16-rc4-mm1/
plus hotfixes
Unfortunately, I lost my .config from the old kernel, so I attempted the
following:
cd scripts
make binoffset
cd ..
scripts/extract-ikconfig /boot/vmlinuz-2.6.16-rc3-mm1-home >.config
This results in:
zcat: stdin: decompression OK, trailing garbage ignored
Note: I have not compiled this kernel yet, so there will be probably
another report of real issues.
--
Alexander E. Patrakov
^ permalink raw reply [flat|nested] 62+ messages in thread* Re: 2.6.16-rc4-mm1
2006-02-22 13:47 ` 2.6.16-rc4-mm1 Alexander E. Patrakov
@ 2006-02-22 15:26 ` Alexander E. Patrakov
2006-02-23 12:10 ` 2.6.16-rc4-mm1 Alan Cox
2006-02-22 15:36 ` 2.6.16-rc4-mm1 Randy.Dunlap
2006-02-23 6:53 ` 2.6.16-rc4-mm1 Randy.Dunlap
2 siblings, 1 reply; 62+ messages in thread
From: Alexander E. Patrakov @ 2006-02-22 15:26 UTC (permalink / raw)
To: Alexander E. Patrakov, LKML, Andrew Morton
I wrote:
> there will be probably another report of real issues.
It boots and doesn't oops. I have played with libata a bit (booted off
ext3 on LVM2 on via pata, played some CD audio tracks, and a DVD intro -
btw this also counts as snd-fm801 test). It is still slow because of
improper MWDMA2 setting (libata still doesn't know that master and slave
can use different DMA speeds on via pata).
ppracer works, so this counts as r200 DRM test.
I also hit the already-known psmouse resync issue:
psmouse.c: resync failed, issuing reconnect request
input: ImExPS/2 Logitech Wheel Mouse as /class/input/input2
And, because you can read this, the 8250 serial driver and the PPP
protocol work.
Of course the above doesn't form good testing, so I will just use this
kernel and report if I find more.
--
Alexander E. Patrakov
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-22 15:26 ` 2.6.16-rc4-mm1 Alexander E. Patrakov
@ 2006-02-23 12:10 ` Alan Cox
2006-02-23 13:02 ` 2.6.16-rc4-mm1 Thierry Vignaud
0 siblings, 1 reply; 62+ messages in thread
From: Alan Cox @ 2006-02-23 12:10 UTC (permalink / raw)
To: Alexander E. Patrakov; +Cc: LKML, Andrew Morton
On Mer, 2006-02-22 at 20:26 +0500, Alexander E. Patrakov wrote:
> btw this also counts as snd-fm801 test). It is still slow because of
> improper MWDMA2 setting (libata still doesn't know that master and slave
> can use different DMA speeds on via pata).
The libata and pata_via in -mm are a bit out of date. The current libata
patch and driver for 2.6.16-rc4 knows how to do per device modes.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-23 12:10 ` 2.6.16-rc4-mm1 Alan Cox
@ 2006-02-23 13:02 ` Thierry Vignaud
2006-02-23 15:19 ` 2.6.16-rc4-mm1 Alan Cox
0 siblings, 1 reply; 62+ messages in thread
From: Thierry Vignaud @ 2006-02-23 13:02 UTC (permalink / raw)
To: Alan Cox; +Cc: Alexander E. Patrakov, LKML, Andrew Morton
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> The libata and pata_via in -mm are a bit out of date. The current
> libata patch and driver for 2.6.16-rc4 knows how to do per device
> modes.
does this include the other pata_* drivers?
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-23 13:02 ` 2.6.16-rc4-mm1 Thierry Vignaud
@ 2006-02-23 15:19 ` Alan Cox
0 siblings, 0 replies; 62+ messages in thread
From: Alan Cox @ 2006-02-23 15:19 UTC (permalink / raw)
To: Thierry Vignaud; +Cc: Alexander E. Patrakov, LKML, Andrew Morton
On Iau, 2006-02-23 at 14:02 +0100, Thierry Vignaud wrote:
> Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>
> > The libata and pata_via in -mm are a bit out of date. The current
> > libata patch and driver for 2.6.16-rc4 knows how to do per device
> > modes.
>
> does this include the other pata_* drivers?
All the PATA in -mm is a bit out of date right now. I'm getting so much
more third party testing by releasing patches versus base not -mm that
it seems best to ge the patches knocked into a decent shape and then
feed them through Jeff into -mm and base.
The patch deals with
- 40pin cables (generically)
- DMA mode filtering by card rules
- Per device timing
and some drivers use the command issue wrapping in the core code to
switch mode programming to support multiple DMA timings on hardware that
doesn't do it at hardware level.
Alan
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-22 13:47 ` 2.6.16-rc4-mm1 Alexander E. Patrakov
2006-02-22 15:26 ` 2.6.16-rc4-mm1 Alexander E. Patrakov
@ 2006-02-22 15:36 ` Randy.Dunlap
2006-02-23 6:53 ` 2.6.16-rc4-mm1 Randy.Dunlap
2 siblings, 0 replies; 62+ messages in thread
From: Randy.Dunlap @ 2006-02-22 15:36 UTC (permalink / raw)
To: Alexander E. Patrakov; +Cc: Andrew Morton, LKML
On Wed, 22 Feb 2006, Alexander E. Patrakov wrote:
> Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc4/2.6.16-rc4-mm1/
> plus hotfixes
>
> Unfortunately, I lost my .config from the old kernel, so I attempted the
> following:
>
> cd scripts
> make binoffset
> cd ..
> scripts/extract-ikconfig /boot/vmlinuz-2.6.16-rc3-mm1-home >.config
>
> This results in:
>
> zcat: stdin: decompression OK, trailing garbage ignored
>
> Note: I have not compiled this kernel yet, so there will be probably
> another report of real issues.
argh. That used to work. I'll look into it later today.
Could be that some changes in -mm broke it, or maybe not.
You could try reverting some or all of these to see if
scripts/extract-ikconfig will work for you.
extract-ikconfig-use-mktemp1.patch
extract-ikconfig: use mktemp(1)
extract-ikconfig-be-sure-binoffset-exists-before-extracting.patch
extract-ikconfig: be sure binoffset exists before extracting
extract-ikconfig-dont-use-long-options.patch
extract-ikconfig: don't use --long-options
--
~Randy
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-22 13:47 ` 2.6.16-rc4-mm1 Alexander E. Patrakov
2006-02-22 15:26 ` 2.6.16-rc4-mm1 Alexander E. Patrakov
2006-02-22 15:36 ` 2.6.16-rc4-mm1 Randy.Dunlap
@ 2006-02-23 6:53 ` Randy.Dunlap
2006-02-23 9:11 ` 2.6.16-rc4-mm1 Alexander E. Patrakov
2006-02-23 18:21 ` zcat: stdin: decompression OK (was: Re: 2.6.16-rc4-mm1) Alexey Dobriyan
2 siblings, 2 replies; 62+ messages in thread
From: Randy.Dunlap @ 2006-02-23 6:53 UTC (permalink / raw)
To: Alexander E. Patrakov; +Cc: akpm, linux-kernel
On Wed, 22 Feb 2006 18:47:59 +0500 Alexander E. Patrakov wrote:
> Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc4/2.6.16-rc4-mm1/
> plus hotfixes
>
> Unfortunately, I lost my .config from the old kernel, so I attempted the
> following:
>
> cd scripts
> make binoffset
> cd ..
> scripts/extract-ikconfig /boot/vmlinuz-2.6.16-rc3-mm1-home >.config
>
> This results in:
>
> zcat: stdin: decompression OK, trailing garbage ignored
No other output? what $ARCH?
What did the .config file contain? was it correct?
so is the only problem the zcat warning message?
I tested extract-ikconfig several times without errors (on 2.6.16-rc4-mm1).
---
~Randy
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-23 6:53 ` 2.6.16-rc4-mm1 Randy.Dunlap
@ 2006-02-23 9:11 ` Alexander E. Patrakov
2006-02-23 15:27 ` 2.6.16-rc4-mm1 Randy.Dunlap
2006-02-23 18:21 ` zcat: stdin: decompression OK (was: Re: 2.6.16-rc4-mm1) Alexey Dobriyan
1 sibling, 1 reply; 62+ messages in thread
From: Alexander E. Patrakov @ 2006-02-23 9:11 UTC (permalink / raw)
To: Randy.Dunlap; +Cc: akpm, linux-kernel
Randy.Dunlap wrote:
> On Wed, 22 Feb 2006 18:47:59 +0500 Alexander E. Patrakov wrote:
>> zcat: stdin: decompression OK, trailing garbage ignored
>
> No other output? what $ARCH?
No other output, the arch is i386, userspace is Debian Sarge.
> What did the .config file contain? was it correct?
The end result was correct. The problematic kernel image (with the
config in it) can be accessed at:
http://ums.usu.ru/~patrakov/vmlinuz-2.6.16-rc3-mm1-home
(please notify when I can erase it)
> so is the only problem the zcat warning message?
Yes.
> I tested extract-ikconfig several times without errors (on 2.6.16-rc4-mm1).
I will dig more into the problem today. Reverting extract-ikconfig-*
patches didn't help.
--
Alexander E. Patrakov
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: 2.6.16-rc4-mm1
2006-02-23 9:11 ` 2.6.16-rc4-mm1 Alexander E. Patrakov
@ 2006-02-23 15:27 ` Randy.Dunlap
0 siblings, 0 replies; 62+ messages in thread
From: Randy.Dunlap @ 2006-02-23 15:27 UTC (permalink / raw)
To: Alexander E. Patrakov; +Cc: Randy.Dunlap, akpm, linux-kernel
On Thu, 23 Feb 2006, Alexander E. Patrakov wrote:
> Randy.Dunlap wrote:
> > On Wed, 22 Feb 2006 18:47:59 +0500 Alexander E. Patrakov wrote:
> >> zcat: stdin: decompression OK, trailing garbage ignored
> >
> > No other output? what $ARCH?
>
> No other output, the arch is i386, userspace is Debian Sarge.
>
> > What did the .config file contain? was it correct?
>
> The end result was correct. The problematic kernel image (with the
> config in it) can be accessed at:
>
> http://ums.usu.ru/~patrakov/vmlinuz-2.6.16-rc3-mm1-home
>
> (please notify when I can erase it)
I have it, so you can erase it...
> > so is the only problem the zcat warning message?
>
> Yes.
>
> > I tested extract-ikconfig several times without errors (on 2.6.16-rc4-mm1).
>
> I will dig more into the problem today. Reverting extract-ikconfig-*
> patches didn't help.
Thanks.
--
~Randy
^ permalink raw reply [flat|nested] 62+ messages in thread
* zcat: stdin: decompression OK (was: Re: 2.6.16-rc4-mm1)
2006-02-23 6:53 ` 2.6.16-rc4-mm1 Randy.Dunlap
2006-02-23 9:11 ` 2.6.16-rc4-mm1 Alexander E. Patrakov
@ 2006-02-23 18:21 ` Alexey Dobriyan
2006-02-24 4:18 ` Randy.Dunlap
2006-02-24 4:51 ` zcat: stdin: decompression OK Alexander E. Patrakov
1 sibling, 2 replies; 62+ messages in thread
From: Alexey Dobriyan @ 2006-02-23 18:21 UTC (permalink / raw)
To: Randy.Dunlap; +Cc: Alexander E. Patrakov, akpm, linux-kernel
On Wed, Feb 22, 2006 at 10:53:25PM -0800, Randy.Dunlap wrote:
> On Wed, 22 Feb 2006 18:47:59 +0500 Alexander E. Patrakov wrote:
> > Unfortunately, I lost my .config from the old kernel, so I attempted the
> > following:
> >
> > cd scripts
> > make binoffset
> > cd ..
> > scripts/extract-ikconfig /boot/vmlinuz-2.6.16-rc3-mm1-home >.config
> >
> > This results in:
> >
> > zcat: stdin: decompression OK, trailing garbage ignored
>
> No other output? what $ARCH?
> What did the .config file contain? was it correct?
> so is the only problem the zcat warning message?
>
> I tested extract-ikconfig several times without errors (on 2.6.16-rc4-mm1).
Since I can reproduce it, Randy, what version do you use? 1.3.5-r8 here
from Gentoo.
At least, we can trivially shut it up.
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: zcat: stdin: decompression OK (was: Re: 2.6.16-rc4-mm1)
2006-02-23 18:21 ` zcat: stdin: decompression OK (was: Re: 2.6.16-rc4-mm1) Alexey Dobriyan
@ 2006-02-24 4:18 ` Randy.Dunlap
2006-02-24 4:51 ` zcat: stdin: decompression OK Alexander E. Patrakov
1 sibling, 0 replies; 62+ messages in thread
From: Randy.Dunlap @ 2006-02-24 4:18 UTC (permalink / raw)
To: Alexey Dobriyan; +Cc: patrakov, akpm, linux-kernel
On Thu, 23 Feb 2006 21:21:07 +0300 Alexey Dobriyan wrote:
> On Wed, Feb 22, 2006 at 10:53:25PM -0800, Randy.Dunlap wrote:
> > On Wed, 22 Feb 2006 18:47:59 +0500 Alexander E. Patrakov wrote:
> > > Unfortunately, I lost my .config from the old kernel, so I attempted the
> > > following:
> > >
> > > cd scripts
> > > make binoffset
> > > cd ..
> > > scripts/extract-ikconfig /boot/vmlinuz-2.6.16-rc3-mm1-home >.config
> > >
> > > This results in:
> > >
> > > zcat: stdin: decompression OK, trailing garbage ignored
> >
> > No other output? what $ARCH?
> > What did the .config file contain? was it correct?
> > so is the only problem the zcat warning message?
> >
> > I tested extract-ikconfig several times without errors (on 2.6.16-rc4-mm1).
>
> Since I can reproduce it, Randy, what version do you use? 1.3.5-r8 here
> from Gentoo.
>
> At least, we can trivially shut it up.
Hi Alexey-
zcat 1.3.5
(2002-09-30)
---
~Randy
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: zcat: stdin: decompression OK
2006-02-23 18:21 ` zcat: stdin: decompression OK (was: Re: 2.6.16-rc4-mm1) Alexey Dobriyan
2006-02-24 4:18 ` Randy.Dunlap
@ 2006-02-24 4:51 ` Alexander E. Patrakov
2006-02-27 1:59 ` Randy.Dunlap
1 sibling, 1 reply; 62+ messages in thread
From: Alexander E. Patrakov @ 2006-02-24 4:51 UTC (permalink / raw)
To: Alexey Dobriyan; +Cc: Randy.Dunlap, akpm, linux-kernel
Alexey Dobriyan wrote:
> On Wed, Feb 22, 2006 at 10:53:25PM -0800, Randy.Dunlap wrote:
>> On Wed, 22 Feb 2006 18:47:59 +0500 Alexander E. Patrakov wrote:
>>> Unfortunately, I lost my .config from the old kernel, so I attempted the
>>> following:
>>>
>>> cd scripts
>>> make binoffset
>>> cd ..
>>> scripts/extract-ikconfig /boot/vmlinuz-2.6.16-rc3-mm1-home >.config
>>>
>>> This results in:
>>>
>>> zcat: stdin: decompression OK, trailing garbage ignored
>> No other output? what $ARCH?
>> What did the .config file contain? was it correct?
>> so is the only problem the zcat warning message?
>>
>> I tested extract-ikconfig several times without errors (on 2.6.16-rc4-mm1).
>
> Since I can reproduce it, Randy, what version do you use? 1.3.5-r8 here
> from Gentoo.
>
> At least, we can trivially shut it up.
I think this would be wrong, because I am able to extract the config
without warnings from 2.6.15-mm2 or even vanilla 2.6.16-rc4, but not
vmlinuz-2.6.16-rc3-mm1. So something changed in -mm between 2.6.15-mm2
and 2.6.16-rc3-mm1 in the way how bzImages are produced.
--
Alexander E. Patrakov
^ permalink raw reply [flat|nested] 62+ messages in thread
* Re: zcat: stdin: decompression OK
2006-02-24 4:51 ` zcat: stdin: decompression OK Alexander E. Patrakov
@ 2006-02-27 1:59 ` Randy.Dunlap
0 siblings, 0 replies; 62+ messages in thread
From: Randy.Dunlap @ 2006-02-27 1:59 UTC (permalink / raw)
To: Alexander E. Patrakov; +Cc: adobriyan, akpm, linux-kernel
On Fri, 24 Feb 2006 09:51:34 +0500 Alexander E. Patrakov wrote:
> Alexey Dobriyan wrote:
> > On Wed, Feb 22, 2006 at 10:53:25PM -0800, Randy.Dunlap wrote:
> >> On Wed, 22 Feb 2006 18:47:59 +0500 Alexander E. Patrakov wrote:
> >>> Unfortunately, I lost my .config from the old kernel, so I attempted the
> >>> following:
> >>>
> >>> cd scripts
> >>> make binoffset
> >>> cd ..
> >>> scripts/extract-ikconfig /boot/vmlinuz-2.6.16-rc3-mm1-home >.config
> >>>
> >>> This results in:
> >>>
> >>> zcat: stdin: decompression OK, trailing garbage ignored
> >> No other output? what $ARCH?
> >> What did the .config file contain? was it correct?
> >> so is the only problem the zcat warning message?
> >>
> >> I tested extract-ikconfig several times without errors (on 2.6.16-rc4-mm1).
> >
> > Since I can reproduce it, Randy, what version do you use? 1.3.5-r8 here
> > from Gentoo.
> >
> > At least, we can trivially shut it up.
>
> I think this would be wrong, because I am able to extract the config
> without warnings from 2.6.15-mm2 or even vanilla 2.6.16-rc4, but not
> vmlinuz-2.6.16-rc3-mm1. So something changed in -mm between 2.6.15-mm2
> and 2.6.16-rc3-mm1 in the way how bzImages are produced.
Alexey,
It's the final zcat that is complaining -- last one in the script:
(dd ibs="$off" skip=1 count=0 && dd bs=512k) <"$image" 2>/dev/null | \
zcat >"$TMPFILE"
The 'dd' command begins at the gzip header of the kernel image file,
but it doesn't know where the end of the gzip area is, it just feeds
everything from $off to zcat, and zcat finds more data than it needs/wants.
still looking.
---
~Randy
^ permalink raw reply [flat|nested] 62+ messages in thread