From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: Kirkwood issues with 3.8-rc1 - Ooops and hang on reboot
Date: Fri, 28 Dec 2012 18:17:49 +0100 [thread overview]
Message-ID: <20121228171749.GA6152@lunn.ch> (raw)
Hi Josh
What compiler version are you using to get the opps?
I don't see this problem, when building with:
arm-linux-gnueabi-gcc -v
Using built-in specs.
Target: arm-linux-gnueabi
Configured with: ../src/configure -v --with-pkgversion='Debian 4.4.5-8' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.4 --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/arm-linux-gnueabi/include/c++/4.4.5 --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --disable-sjlj-exceptions --enable-checking=release --program-prefix=arm-linux-gnueabi- --includedir=/usr/arm-linux-gnueabi/include --build=i486-linux-gnu --host=i486-linux-gnu --target=arm-linux-gnueabi --with-headers=/usr/arm-linux-gnueabi/include --with-libs=/usr/arm-linux-gnueabi/lib
Thread model: posix
gcc version 4.4.5 (Debian 4.4.5-8)
The disassembly i get looks similar, but not identical.
BTW:
make drivers/clk/mvebu/clk-gating-ctrl.lst
is useful in situations like this.
Andrew
next reply other threads:[~2012-12-28 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 17:17 Andrew Lunn [this message]
2012-12-28 17:38 ` Kirkwood issues with 3.8-rc1 - Ooops and hang on reboot Russell King - ARM Linux
2012-12-29 23:31 ` Josh Coombs
2012-12-30 0:23 ` Russell King - ARM Linux
2013-01-03 4:50 ` Josh Coombs
2013-01-03 8:22 ` Andrew Lunn
2013-01-03 23:26 ` Josh Coombs
2013-01-04 7:38 ` Andrew Lunn
2012-12-28 18:19 ` Josh Coombs
-- strict thread matches above, loose matches on Subject: below --
2012-12-28 16:09 Josh Coombs
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=20121228171749.GA6152@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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).