[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3303fea7-9f10-d7f1-fb01-d2e9de26173b@osg.samsung.com>
Date: Tue, 21 Nov 2017 11:02:37 -0700
From: Shuah Khan <shuahkh@....samsung.com>
To: John Johansen <john.johansen@...onical.com>
Cc: torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
Shuah Khan <shuahkh@....samsung.com>
Subject: Re: Linux 4.14 - BUG: unable to handle kernel paging request at
ffffffff3bbbe160 IP: audit_signal_cb+0x75/0xf0
On 11/21/2017 10:44 AM, John Johansen wrote:
> On 11/21/2017 08:58 AM, Shuah Khan wrote:
>> Hi John,
>>
>> I am seeing the following on my laptop. Unfortunately this is my primary
>> system and my ability to bisect might be a bit limited. The system is
>> running
>>
>> 4.14.0+ #4 SMP Tue Nov 14 19:25:58 MST 2017 x86_64 x86_64 x86_64 GNU/Linux
>>
>> on Ubuntu 17.10 base.
>>
>> Is this a known issue? Please see the dmesg excerpts below:
>>
> Its not. I'll start looking into it today
>
> Do you have any other information that you can send to me?
>
> Any particular task/work load that triggers this?
> Can you tar up your /etc/apparmor.d/ and send that to me?
>
>
Yeah. I forgot mention that detail :)
I first noticed it when I tried starting "/usr/bin/evince"
evince doesn't start and runs into this error.
Happens every time evince is invoked. I tried evince again.
xournal works just fine. xournal doesn't have usr.bin.*file* for
it anyway, so that doesn't matter I would think.
Attached /etc/apparmor.d/usr.bin.evince
thanks,
-- Shuah
View attachment "usr.bin.evince" of type "text/plain" (5995 bytes)
Powered by blists - more mailing lists