Kernel panic in 4.1.2-200.fc22.x86_64

Chris Murphy lists at colorremedies.com
Fri Jul 31 03:43:37 UTC 2015


On Thu, Jul 30, 2015 at 4:43 PM, Patrick O'Callaghan
<pocallaghan at gmail.com> 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.

mm/slub.c and kmmalloc are memory related functions, so if you regress
to a previously working kernel I'd say memory related. Maybe try live
media and see if it happens. And start a memtest over the weekend and
see if that triggers something.


-- 
Chris Murphy


More information about the users mailing list