I see many many section mismatches when compiling with gcc 4.1 and
binutils 2.17.50.20070426 They appear to be from .sdata to
.init.data.
This is with basic zx1_defconfig with a few mods.
The reason appears to be compiler weirdness..
WARNING: init/built-in.o(.sdata+0x30): Section mismatch:
I see many many section mismatches when compiling with gcc 4.1 and
binutils 2.17.50.20070426 They appear to be from .sdata to
.init.data.
This is with basic zx1_defconfig with a few mods.
The reason appears to be compiler weirdness..
WARNING: init/built-in.o(.sdata+0x30): Section mismatch:
> Tony, what system are you using to compile on, OS, etc?
$ cat /etc/redhat-release
Red Hat Enterprise Linux AS release 4 (Nahant Update 5 Beta)
-Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Luck, Tony wrote:
I used the sn2_defconfig in the tree :)
So there is something odd happening. Russ complained that he
was still seeing several errors from the sn2_defconfig build
too when I posted the "last fix" to Len. But I don't see them
when I build.
Adding Vivek.
I've
> I used the sn2_defconfig in the tree :)
So there is something odd happening. Russ complained that he
was still seeing several errors from the sn2_defconfig build
too when I posted the "last fix" to Len. But I don't see them
when I build.
-Tony
-
To unsubscribe from this list: send the line
On Thu, May 31, 2007 at 09:45:31PM -0700, Christoph Lameter wrote:
> On Fri, 1 Jun 2007, Sam Ravnborg wrote:
>
> > On Thu, May 31, 2007 at 09:05:54PM -0700, Christoph Lameter wrote:
> > > On Thu, 31 May 2007, Prarit Bhargava wrote:
> > >
> > > > I used the sn2_defconfig in the tree :)
> > >
> >
On Thu, May 31, 2007 at 09:45:31PM -0700, Christoph Lameter wrote:
On Fri, 1 Jun 2007, Sam Ravnborg wrote:
On Thu, May 31, 2007 at 09:05:54PM -0700, Christoph Lameter wrote:
On Thu, 31 May 2007, Prarit Bhargava wrote:
I used the sn2_defconfig in the tree :)
That is a static
Tony, what system are you using to compile on, OS, etc?
$ cat /etc/redhat-release
Red Hat Enterprise Linux AS release 4 (Nahant Update 5 Beta)
-Tony
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
I used the sn2_defconfig in the tree :)
So there is something odd happening. Russ complained that he
was still seeing several errors from the sn2_defconfig build
too when I posted the last fix to Len. But I don't see them
when I build.
-Tony
-
To unsubscribe from this list: send the line
Luck, Tony wrote:
I used the sn2_defconfig in the tree :)
So there is something odd happening. Russ complained that he
was still seeing several errors from the sn2_defconfig build
too when I posted the last fix to Len. But I don't see them
when I build.
Adding Vivek.
I've
On Fri, 1 Jun 2007, Sam Ravnborg wrote:
> On Thu, May 31, 2007 at 09:05:54PM -0700, Christoph Lameter wrote:
> > On Thu, 31 May 2007, Prarit Bhargava wrote:
> >
> > > I used the sn2_defconfig in the tree :)
> >
> > That is a static kernel build. Ideal for that kind of bug.
> Quite the opposite.
On Thu, May 31, 2007 at 09:05:54PM -0700, Christoph Lameter wrote:
> On Thu, 31 May 2007, Prarit Bhargava wrote:
>
> > I used the sn2_defconfig in the tree :)
>
> That is a static kernel build. Ideal for that kind of bug.
Quite the opposite.
If modpost cannot resolve symbols you are jsut told
On Thu, 31 May 2007, Prarit Bhargava wrote:
> I used the sn2_defconfig in the tree :)
That is a static kernel build. Ideal for that kind of bug.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Luck, Tony wrote:
Tony, the ia64 section mismatch "whack-a-mole" is far from over :(
Can you post the .config file that you are using when you see all those
warnings ... I'll start bopping them on their cute little heads.
Hi Tony,
I used the sn2_defconfig in the tree :)
P.
> Tony, the ia64 section mismatch "whack-a-mole" is far from over :(
Can you post the .config file that you are using when you see all those
warnings ... I'll start bopping them on their cute little heads.
-Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Thu, 31 May 2007, Prarit Bhargava wrote:
> Christoph, this is one less beer I owe you :) :) :)
Finally the compile works. Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Thu, May 31, 2007 at 11:20:27AM -0400, Prarit Bhargava wrote:
>
> Something is borken in modpost because I found a bug in the loopback
> code which is a _REAL_ bug.
Here is the result for an i386 allmodconfig build:
WARNING: arch/i386/kernel/built-in.o(.init.text+0x3966): Section mismatch:
On Thu, May 31, 2007 at 11:20:27AM -0400, Prarit Bhargava wrote:
>
>
> Christoph Lameter wrote:
> >On Wed, 30 May 2007, Luck, Tony wrote:
> >
> >
> >>>Ahh okay. cscope will do that too But all have __exit.
> >>>
> >>The trick is that one of them *shouldn't* have __exit. With cscope
Christoph Lameter wrote:
On Wed, 30 May 2007, Luck, Tony wrote:
Ahh okay. cscope will do that too But all have __exit.
The trick is that one of them *shouldn't* have __exit. With cscope
you'll have to use the "Find functions calling this function:"
mode to try and find the
On Wed, 30 May 2007 17:09:56 -0700 (PDT) Christoph Lameter wrote:
> On Wed, 30 May 2007, Randy Dunlap wrote:
>
> > OK. I would write the file to disk and view it with an editor.
> > Then at each occurrence of /exit.text/, see if it's inside an __init
> > function...
>
> Ahh okay. cscope will
On Wed, 30 May 2007 17:09:56 -0700 (PDT) Christoph Lameter wrote:
On Wed, 30 May 2007, Randy Dunlap wrote:
OK. I would write the file to disk and view it with an editor.
Then at each occurrence of /exit.text/, see if it's inside an __init
function...
Ahh okay. cscope will do that
Christoph Lameter wrote:
On Wed, 30 May 2007, Luck, Tony wrote:
Ahh okay. cscope will do that too But all have __exit.
The trick is that one of them *shouldn't* have __exit. With cscope
you'll have to use the Find functions calling this function:
mode to try and find the
On Thu, May 31, 2007 at 11:20:27AM -0400, Prarit Bhargava wrote:
Christoph Lameter wrote:
On Wed, 30 May 2007, Luck, Tony wrote:
Ahh okay. cscope will do that too But all have __exit.
The trick is that one of them *shouldn't* have __exit. With cscope
you'll have to use
On Thu, May 31, 2007 at 11:20:27AM -0400, Prarit Bhargava wrote:
Something is borken in modpost because I found a bug in the loopback
code which is a _REAL_ bug.
Here is the result for an i386 allmodconfig build:
WARNING: arch/i386/kernel/built-in.o(.init.text+0x3966): Section mismatch:
On Thu, 31 May 2007, Prarit Bhargava wrote:
Christoph, this is one less beer I owe you :) :) :)
Finally the compile works. Thanks.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Tony, the ia64 section mismatch whack-a-mole is far from over :(
Can you post the .config file that you are using when you see all those
warnings ... I'll start bopping them on their cute little heads.
-Tony
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of
Luck, Tony wrote:
Tony, the ia64 section mismatch whack-a-mole is far from over :(
Can you post the .config file that you are using when you see all those
warnings ... I'll start bopping them on their cute little heads.
Hi Tony,
I used the sn2_defconfig in the tree :)
P.
-Tony
On Thu, 31 May 2007, Prarit Bhargava wrote:
I used the sn2_defconfig in the tree :)
That is a static kernel build. Ideal for that kind of bug.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Thu, May 31, 2007 at 09:05:54PM -0700, Christoph Lameter wrote:
On Thu, 31 May 2007, Prarit Bhargava wrote:
I used the sn2_defconfig in the tree :)
That is a static kernel build. Ideal for that kind of bug.
Quite the opposite.
If modpost cannot resolve symbols you are jsut told what
On Fri, 1 Jun 2007, Sam Ravnborg wrote:
On Thu, May 31, 2007 at 09:05:54PM -0700, Christoph Lameter wrote:
On Thu, 31 May 2007, Prarit Bhargava wrote:
I used the sn2_defconfig in the tree :)
That is a static kernel build. Ideal for that kind of bug.
Quite the opposite.
I thought
On Wed, May 30, 2007 at 04:31:35PM -0700, Christoph Lameter wrote:
> On Wed, 30 May 2007, Luck, Tony wrote:
>
> >
> > > `.exit.text' referenced in section `.init.text' of drivers/built-in.o:
> > > defined in discarded section `.exit.text' of drivers/built-in.o
> >
> >
> > This one is a fatal
On Wed, 30 May 2007, Luck, Tony wrote:
> > Ahh okay. cscope will do that too But all have __exit.
>
> The trick is that one of them *shouldn't* have __exit. With cscope
> you'll have to use the "Find functions calling this function:"
> mode to try and find the __init function that is
> Ahh okay. cscope will do that too But all have __exit.
The trick is that one of them *shouldn't* have __exit. With cscope
you'll have to use the "Find functions calling this function:"
mode to try and find the __init function that is calling an
__exit function.
-Tony
-
To unsubscribe from
On Wed, May 30, 2007 at 01:11:17PM -0700, Luck, Tony wrote:
> > Hmmm - I wonder if my tree is screwed up in some weird way. I'm seeing link
> > warnings as well:
> >
> > WARNING: init/built-in.o - Section mismatch: reference to .init.data: from
> > .sdata after 'root_mountflags' (at offset 0x38)
On Wed, 30 May 2007, Randy Dunlap wrote:
> OK. I would write the file to disk and view it with an editor.
> Then at each occurrence of /exit.text/, see if it's inside an __init
> function...
Ahh okay. cscope will do that too But all have __exit.
-
To unsubscribe from this list: send the
> Saw this when running strace -f on a script on 2.6.21 on ia64
Run strace -f on 2.6.22-rc3 on Tiger4/Montecito. Couldn't reproduce
this issue. Kernel was built with both defconfig and tiger_defconfig.
Thanks.
-Fenghua
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Christoph Lameter wrote:
On Wed, 30 May 2007, Randy Dunlap wrote:
Right. I have no idea where to look. The function has no name? Or is the
segment .exit.text referenced by namne in .init.text?
Maybe 'objdump drivers/built-in.o and then grep that output (file)
for /exit.text/ ...
OK. I
On Wed, 30 May 2007, Randy Dunlap wrote:
> > Right. I have no idea where to look. The function has no name? Or is the
> > segment .exit.text referenced by namne in .init.text?
>
> Maybe 'objdump drivers/built-in.o and then grep that output (file)
> for /exit.text/ ...
[EMAIL
On Wed, 30 May 2007 16:31:35 -0700 (PDT) Christoph Lameter wrote:
> On Wed, 30 May 2007, Luck, Tony wrote:
>
> >
> > > `.exit.text' referenced in section `.init.text' of drivers/built-in.o:
> > > defined in discarded section `.exit.text' of drivers/built-in.o
> >
> >
> > This one is a fatal
On Wed, 30 May 2007, Luck, Tony wrote:
>
> > `.exit.text' referenced in section `.init.text' of drivers/built-in.o:
> > defined in discarded section `.exit.text' of drivers/built-in.o
>
>
> This one is a fatal error ... the code is trying to call a function
> that has been marked __exit in a
> `.exit.text' referenced in section `.init.text' of drivers/built-in.o:
> defined in discarded section `.exit.text' of drivers/built-in.o
This one is a fatal error ... the code is trying to call a function
that has been marked __exit in a driver that has been built-in, instead
of as a module.
On Wed, 30 May 2007, Luck, Tony wrote:
> > WARNING: init/built-in.o - Section mismatch: reference to .init.data: from
> > .sdata after 'root_mountflags' (at offset 0x38)
>
> I thought that I'd got the section mis-match warnings down to
> just one (and that was in ACPI code, so I sent a patch to
> Hmmm - I wonder if my tree is screwed up in some weird way. I'm seeing link
> warnings as well:
>
> WARNING: init/built-in.o - Section mismatch: reference to .init.data: from
> .sdata after 'root_mountflags' (at offset 0x38)
I thought that I'd got the section mis-match warnings down to
just
Hmmm - I wonder if my tree is screwed up in some weird way. I'm seeing link
warnings as well:
WARNING: init/built-in.o - Section mismatch: reference to .init.data: from
.sdata after 'root_mountflags' (at offset 0x38)
I thought that I'd got the section mis-match warnings down to
just one
On Wed, 30 May 2007, Luck, Tony wrote:
WARNING: init/built-in.o - Section mismatch: reference to .init.data: from
.sdata after 'root_mountflags' (at offset 0x38)
I thought that I'd got the section mis-match warnings down to
just one (and that was in ACPI code, so I sent a patch to Len
`.exit.text' referenced in section `.init.text' of drivers/built-in.o:
defined in discarded section `.exit.text' of drivers/built-in.o
This one is a fatal error ... the code is trying to call a function
that has been marked __exit in a driver that has been built-in, instead
of as a module.
On Wed, 30 May 2007, Luck, Tony wrote:
`.exit.text' referenced in section `.init.text' of drivers/built-in.o:
defined in discarded section `.exit.text' of drivers/built-in.o
This one is a fatal error ... the code is trying to call a function
that has been marked __exit in a driver
On Wed, 30 May 2007 16:31:35 -0700 (PDT) Christoph Lameter wrote:
On Wed, 30 May 2007, Luck, Tony wrote:
`.exit.text' referenced in section `.init.text' of drivers/built-in.o:
defined in discarded section `.exit.text' of drivers/built-in.o
This one is a fatal error ... the
On Wed, 30 May 2007, Randy Dunlap wrote:
Right. I have no idea where to look. The function has no name? Or is the
segment .exit.text referenced by namne in .init.text?
Maybe 'objdump drivers/built-in.o and then grep that output (file)
for /exit.text/ ...
[EMAIL
Christoph Lameter wrote:
On Wed, 30 May 2007, Randy Dunlap wrote:
Right. I have no idea where to look. The function has no name? Or is the
segment .exit.text referenced by namne in .init.text?
Maybe 'objdump drivers/built-in.o and then grep that output (file)
for /exit.text/ ...
OK. I
Saw this when running strace -f on a script on 2.6.21 on ia64
Run strace -f on 2.6.22-rc3 on Tiger4/Montecito. Couldn't reproduce
this issue. Kernel was built with both defconfig and tiger_defconfig.
Thanks.
-Fenghua
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
On Wed, 30 May 2007, Randy Dunlap wrote:
OK. I would write the file to disk and view it with an editor.
Then at each occurrence of /exit.text/, see if it's inside an __init
function...
Ahh okay. cscope will do that too But all have __exit.
-
To unsubscribe from this list: send the line
On Wed, May 30, 2007 at 01:11:17PM -0700, Luck, Tony wrote:
Hmmm - I wonder if my tree is screwed up in some weird way. I'm seeing link
warnings as well:
WARNING: init/built-in.o - Section mismatch: reference to .init.data: from
.sdata after 'root_mountflags' (at offset 0x38)
I
Ahh okay. cscope will do that too But all have __exit.
The trick is that one of them *shouldn't* have __exit. With cscope
you'll have to use the Find functions calling this function:
mode to try and find the __init function that is calling an
__exit function.
-Tony
-
To unsubscribe from
On Wed, 30 May 2007, Luck, Tony wrote:
Ahh okay. cscope will do that too But all have __exit.
The trick is that one of them *shouldn't* have __exit. With cscope
you'll have to use the Find functions calling this function:
mode to try and find the __init function that is calling an
On Wed, May 30, 2007 at 04:31:35PM -0700, Christoph Lameter wrote:
On Wed, 30 May 2007, Luck, Tony wrote:
`.exit.text' referenced in section `.init.text' of drivers/built-in.o:
defined in discarded section `.exit.text' of drivers/built-in.o
This one is a fatal error ... the
On Wed, May 30, 2007 at 01:30:41PM +1000, David Chinner wrote:
> On Wed, May 23, 2007 at 10:44:16AM -0700, Luck, Tony wrote:
> > > > Saw this when running strace -f on a script on 2.6.21 on ia64:
> > > >
> > > > BUG: sleeping function called from invalid context at kernel/fork.c:385
> > > >
On Wed, May 23, 2007 at 10:44:16AM -0700, Luck, Tony wrote:
> > > Saw this when running strace -f on a script on 2.6.21 on ia64:
> > >
> > > BUG: sleeping function called from invalid context at kernel/fork.c:385
> > > in_atomic():1, irqs_disabled():0
> ... snip ...
> > > I could reproduce it
On Wed, May 23, 2007 at 10:44:16AM -0700, Luck, Tony wrote:
Saw this when running strace -f on a script on 2.6.21 on ia64:
BUG: sleeping function called from invalid context at kernel/fork.c:385
in_atomic():1, irqs_disabled():0
... snip ...
I could reproduce it via 'strace -f
On Wed, May 30, 2007 at 01:30:41PM +1000, David Chinner wrote:
On Wed, May 23, 2007 at 10:44:16AM -0700, Luck, Tony wrote:
Saw this when running strace -f on a script on 2.6.21 on ia64:
BUG: sleeping function called from invalid context at kernel/fork.c:385
in_atomic():1,
> > Saw this when running strace -f on a script on 2.6.21 on ia64:
> >
> > BUG: sleeping function called from invalid context at kernel/fork.c:385
> > in_atomic():1, irqs_disabled():0
... snip ...
> > I could reproduce it via 'strace -f sleep 1'
> >
>
> I'd say this is specific to ia64.
On Wed, 23 May 2007 16:31:54 +1000 David Chinner <[EMAIL PROTECTED]> wrote:
> Saw this when running strace -f on a script on 2.6.21 on ia64:
>
> BUG: sleeping function called from invalid context at kernel/fork.c:385
> in_atomic():1, irqs_disabled():0
>
> Call Trace:
> [] show_stack+0x80/0xa0
On Wed, 23 May 2007 16:31:54 +1000 David Chinner [EMAIL PROTECTED] wrote:
Saw this when running strace -f on a script on 2.6.21 on ia64:
BUG: sleeping function called from invalid context at kernel/fork.c:385
in_atomic():1, irqs_disabled():0
Call Trace:
[a00100014700]
Saw this when running strace -f on a script on 2.6.21 on ia64:
BUG: sleeping function called from invalid context at kernel/fork.c:385
in_atomic():1, irqs_disabled():0
... snip ...
I could reproduce it via 'strace -f sleep 1'
I'd say this is specific to ia64. Someone would
64 matches
Mail list logo
