On Tue, Jun 18, 2013 at 1:25 AM, Khem Raj wrote:
>
> On Jun 17, 2013, at 9:58 PM, Bruce Ashfield
> wrote:
>
>> On 13-06-18 12:41 AM, Khem Raj wrote:
>>>
>>> On Jun 17, 2013, at 9:37 PM, Bruce Ashfield
>>> wrote:
>>>
On 13-06-17 11:30 PM, Khem Raj wrote:
> Hi Bruce and All
>
>
On Jun 17, 2013, at 9:58 PM, Bruce Ashfield
wrote:
> On 13-06-18 12:41 AM, Khem Raj wrote:
>>
>> On Jun 17, 2013, at 9:37 PM, Bruce Ashfield
>> wrote:
>>
>>> On 13-06-17 11:30 PM, Khem Raj wrote:
Hi Bruce and All
Finally after a long innings I have diagnosed the mystery behi
On 13-06-18 12:41 AM, Khem Raj wrote:
On Jun 17, 2013, at 9:37 PM, Bruce Ashfield
wrote:
On 13-06-17 11:30 PM, Khem Raj wrote:
Hi Bruce and All
Finally after a long innings I have diagnosed the mystery behind the below
segfault that we see on kernel 3.8 which compiled with gcc 4.8 but don
On Jun 17, 2013, at 9:37 PM, Bruce Ashfield
wrote:
> On 13-06-17 11:30 PM, Khem Raj wrote:
>> Hi Bruce and All
>>
>> Finally after a long innings I have diagnosed the mystery behind the below
>> segfault that we see on kernel 3.8 which compiled with gcc 4.8 but don't
>> show when compiled wi
On 13-06-17 11:30 PM, Khem Raj wrote:
Hi Bruce and All
Finally after a long innings I have diagnosed the mystery behind the below
segfault that we see on kernel 3.8 which compiled with gcc 4.8 but don't show
when compiled with gcc 4.7
There also seems to be a follow up patch:
commit 418df
On 13-06-17 11:30 PM, Khem Raj wrote:
Hi Bruce and All
Finally after a long innings I have diagnosed the mystery behind the below
segfault that we see on kernel 3.8 which compiled with gcc 4.8 but don't show
when compiled with gcc 4.7
Unable to handle kernel paging request at virtual address
Hi Bruce and All
Finally after a long innings I have diagnosed the mystery behind the below
segfault that we see on kernel 3.8 which compiled with gcc 4.8 but don't show
when compiled with gcc 4.7
Unable to handle kernel paging request at virtual address
pgd = c0004000
[] *pgd