From: Arthur Marsh <arthur.marsh@internode.on.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Oleg Nesterov <oleg@redhat.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: lock-up with module: Optimize __module_address() using a latched RB-tree
Date: Mon, 06 Jul 2015 18:17:44 +0930 [thread overview]
Message-ID: <559A40B0.7080601@internode.on.net> (raw)
In-Reply-To: <20150706081210.GS18673@twins.programming.kicks-ass.net>
Peter Zijlstra wrote on 06/07/15 17:42:
> On Mon, Jul 06, 2015 at 09:19:11AM +0200, Peter Zijlstra wrote:
>> On Mon, Jul 06, 2015 at 04:03:45AM +0930, Arthur Marsh wrote:
>>> I am happy to supply further details and run further tests.
>>
>> A .config and gcc version might be a good start. I'll see if 32bit
>> userspace in KVM can reproduce.
>
> If you can, can you also provide your bzImage and initrd, that would get
> me closer to your setup. Feel free to provide those offlist if that's
> better for you.
>
> For the kernel that goes *Boom* obviously ;-)
>
I hope that these files are what are useful to you:
http://www.users.on.net/~arthur.marsh/config-4.1.0+
http://www.users.on.net/~arthur.marsh/initrd.img-4.1.0+
http://www.users.on.net/~arthur.marsh/vmlinuz-4.1.0+
This kernel does go boom, after it locks up I have to do a major power
down, pull out the graphics card, reboot, shutdown, replace graphics
card to get things working again properly.
Arthur.
next prev parent reply other threads:[~2015-07-06 8:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-05 18:33 Arthur Marsh
2015-07-06 7:19 ` Peter Zijlstra
2015-07-06 7:35 ` Arthur Marsh
2015-07-06 7:53 ` Arthur Marsh
2015-07-06 7:57 ` Peter Zijlstra
2015-07-06 8:12 ` Peter Zijlstra
2015-07-06 8:47 ` Arthur Marsh [this message]
2015-07-06 9:01 ` Peter Zijlstra
2015-07-06 10:04 ` Peter Zijlstra
2015-07-06 10:11 ` Arthur Marsh
2015-07-06 10:32 ` Peter Zijlstra
2015-07-06 11:26 ` Arthur Marsh
2015-07-07 5:29 ` Arthur Marsh
2015-07-07 7:29 ` Peter Zijlstra
2015-07-07 15:58 ` Arthur Marsh
2015-07-07 16:33 ` Mathieu Desnoyers
2015-07-07 20:15 ` Arthur Marsh
2015-07-07 21:56 ` Peter Zijlstra
2015-07-07 22:11 ` Peter Zijlstra
2015-07-08 0:55 ` Rusty Russell
2015-07-08 8:31 ` Arthur Marsh
2015-07-08 9:04 ` Peter Zijlstra
2015-07-08 11:43 ` Arthur Marsh
2015-07-08 12:32 ` Peter Zijlstra
2015-07-08 12:41 ` [PATCH] module: Fix load_module() error path Peter Zijlstra
2015-07-08 21:33 ` Rusty Russell
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=559A40B0.7080601@internode.on.net \
--to=arthur.marsh@internode.on.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
/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
Powered by JetHome