From: Soeren Sonnenburg <sonne-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: Dmitry Torokhov
<dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>,
"Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>,
linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [SOLVED] kernel module loading does not work with binutils-gold (was Re: [Bug #14626] oops on boot starting udev)
Date: Sat, 21 Nov 2009 10:35:10 +0100 [thread overview]
Message-ID: <1258796110.6842.10.camel@no> (raw)
In-Reply-To: <1258793809.4814.4.camel@no>
On Sat, 2009-11-21 at 09:56 +0100, Soeren Sonnenburg wrote:
> On Wed, 2009-11-18 at 18:59 -0800, Dmitry Torokhov wrote:
> > On Tue, Nov 17, 2009 at 05:06:47AM +0100, Soeren Sonnenburg wrote:
> > > On Mon, 2009-11-16 at 20:01 -0800, Dmitry Torokhov wrote:
> > > > On Tue, Nov 17, 2009 at 03:59:03AM +0100, Soeren Sonnenburg wrote:
> > > > > On Mon, 2009-11-16 at 18:04 -0800, Dmitry Torokhov wrote:
> > > > > > On Mon, Nov 16, 2009 at 05:14:55PM -0800, Greg KH wrote:
> > > > > > > On Mon, Nov 16, 2009 at 11:37:48PM +0100, Rafael J. Wysocki wrote:
> > > > > > > > This message has been generated automatically as a part of a report
> > > > > > > > of recent regressions.
> > > > > > > >
> > > > > > > > The following bug entry is on the current list of known regressions
> > > > > > > > from 2.6.31. Please verify if it still should be listed and let me know
> > > > > > > > (either way).
> > > > > > > >
> > > > > > > >
> > > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14626
> > > > > > > > Subject : oops on boot starting udev
> > > > > > > > Submitter : Soeren Sonnenburg <sonne-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
> > > > > > > > Date : 2009-11-14 10:16 (3 days old)
> > > > > > > > References : http://marc.info/?l=linux-kernel&m=125819380206800&w=4
> > > > > > >
> > > > > > > This looks like an input core problem, as the evdev module was just
> > > > > > > loaded and died.
> > > > > > >
> > > > > > > Any input developers have any ideas?
> > > > > > >
> > > > > >
> > > > > >
> > > > > > Hmm, evdev does:
> > > > > >
> > > > > > dev_set_name(&evdev->dev, "event%d", minor);
> > > > > >
> > > > > > Not sure how it can go wrong...
> > > > >
> > > > > Anything I should/could do to narrow it down a bit (apart from
> > > > > bisecting?).
> > > > >
> > > >
> > > > Umm, I looked through the changes between -rc6 and 7 but nothing jumped
> > > > out at me... You don't happen to have any local changes in your tree?
> > >
> > > Well only the mouse button #1 emulation - though I don't see what could
> > > go wrong there.
> > >
> >
> > I have been looking through the changes and I really don't see anything
> > suspicious. I am also not hittign this oops on any of my boxes. Any
> > chance you could bisect?
> >
> > Thanks.
>
> Alright so I tried to do a bisect when I noticed that building a knwon
> to work -rc5 did no longer work either. Thought it might be a gcc
> problem (gcc-4.3 here) so upgraded to 4.4 - same thing.
> Then I recognized that it crashes on loading basically *any* module,
> tried tun and applesmc. Attaching the crashes...
>
> I am starting to run out of ideas...
OK, I've found the culprit: binutils-gold
I build all kernels upto and including -rc6 with the old binutils and
since then have upgraded to binutils gold 2.20-4 which - in contrast to
the old binutils - uses --no-add-needed per default.
So I suspect it triggers an error(?) in the way how the kernel links
modules: It is now required to provide all needed libraries to the
linker when building the modules. I guess this problem could be worked
around by adding --add-needed to the LDFLAGS_MODULE ...
Soeren
--
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
next prev parent reply other threads:[~2009-11-21 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <GUZt44bIwCE.A.vLF.pSdALB@chimera>
[not found] ` <xXQGFmujPl.A.fpF.zSdALB@chimera>
2009-11-17 1:14 ` [Bug #14626] oops on boot starting udev Greg KH
2009-11-17 2:04 ` Dmitry Torokhov
2009-11-17 2:59 ` Soeren Sonnenburg
2009-11-17 4:01 ` Dmitry Torokhov
[not found] ` <20091117040104.GA5792-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2009-11-17 4:06 ` Soeren Sonnenburg
2009-11-19 2:59 ` Dmitry Torokhov
2009-11-21 6:21 ` Soeren Sonnenburg
2009-11-21 8:56 ` Soeren Sonnenburg
2009-11-21 9:30 ` Justin P. Mattock
2009-11-21 9:35 ` Soeren Sonnenburg [this message]
2009-11-21 9:58 ` [SOLVED] kernel module loading does not work with binutils-gold (was Re: [Bug #14626] oops on boot starting udev) Justin P. Mattock
[not found] ` <4B07B9BA.2070607-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-11-21 10:08 ` Soeren Sonnenburg
2009-11-21 10:29 ` Justin P. Mattock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1258796110.6842.10.camel@no \
--to=sonne-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
--cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rjw-KKrjLPT3xs0@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).