[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <559A40B0.7080601@internode.on.net>
Date: Mon, 06 Jul 2015 18:17:44 +0930
From: Arthur Marsh <arthur.marsh@...ernode.on.net>
To: Peter Zijlstra <peterz@...radead.org>
CC: linux-kernel@...r.kernel.org,
Rusty Russell <rusty@...tcorp.com.au>,
Steven Rostedt <rostedt@...dmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Oleg Nesterov <oleg@...hat.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: lock-up with module: Optimize __module_address() using a latched
RB-tree
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists