From: Peter Zijlstra <peterz@infradead.org>
To: Arthur Marsh <arthur.marsh@internode.on.net>
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, 6 Jul 2015 12:32:46 +0200 [thread overview]
Message-ID: <20150706103246.GY3644@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <559A545A.80508@internode.on.net>
On Mon, Jul 06, 2015 at 07:41:38PM +0930, Arthur Marsh wrote:
> No, it's the standard kernel radeon driver.
>
> If it's of any use I can reboot the machine with the kernel that goes boom
> and the video card removed.
You're saying the same kernel boots without issue if you remove the
Radeon?
Most peculiar...
next prev parent reply other threads:[~2015-07-06 10:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-05 18:33 lock-up with module: Optimize __module_address() using a latched RB-tree 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
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 [this message]
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=20150706103246.GY3644@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.