Kernel panic in 4.1.2-200.fc22.x86_64

[joev.8450]

hmm.  I don't know if I'm in the same experience or not.  I'm running
fedora 21 and upgraded to kernel 4.0.8 from 4.0.7 on 7/19.  I didn't
have any issues until about the 26th.  But then my system started to
lock up.  It wasn't just GNOME but direct access was locked -- ie no
response via keyboard, no signal to monitor.  The system responded to
ping and allowed nfs shares that were in place but was not accepting ssh
connect.  So I powered down and selected kernel 4.0.6 on the reboot on
7/29.  I haven't had any issues since.  However, I am not seeing any
kernel bug events logged in the journal.  I suspected the seagate USB
drive or driver for a minute but before I dropped the kernel back I
unplugged the external drive.  Still locked up.  I am seeing some
references to nVidia in the logs.

regards,

Joe Verreau
Durand, MI

On 07/30/2015 06:43 PM, Patrick O'Callaghan wrote:
> On Thu, 2015-07-30 at 13:21 -0500, Ranjan Maitra wrote:
>> On Thu, 30 Jul 2015 18:54:02 +0100 "Patrick O'Callaghan" <
>> pocallaghan at gmail.com> wrote:
>>
>>> This is happening every few minutes since I updated today:
>>>
>>> Jul 30 18:26:21 Bree kernel: BUG: unable to handle kernel NULL 
>>> pointer dereference at 0000000000000288
>>> Jul 30 18:26:21 Bree kernel: IP: [<ffffffff8120f034>] 
>>> __kmalloc_node_track_caller+0x1c4/0x320
>>>
>>> Going to try booting the previous kernel.
>>
>> This is likely a bug. Please file on BZ so that developers may know 
>> about it.
> 
> It's wierd. I rebooted with 4.0.8 (which had previously been working
> with no issues) and got a different bug:
> 
> Jul 30 18:54:49 Bree kernel: kernel BUG at mm/slub.c:3413!
> Jul 30 18:54:50 Bree kernel: invalid opcode: 0000 [#1] SMP
> 
> I rebooted again with 4.0.6 and so far it seems to be working (several
> hours without crashing).
> 
> I'll try updating again tomorrow before I report anything.
> 
> poc
>