public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer dereference
Date: Sat, 28 Feb 2015 17:57:01 -0500	[thread overview]
Message-ID: <006901d053a9$dcf5a950$96e0fbf0$@lucidpixels.com> (raw)
In-Reply-To: <005801d053a4$929e1540$b7da3fc0$@lucidpixels.com>



> -----Original Message-----
> From: Justin Piszcz [mailto:jpiszcz@lucidpixels.com]
> Sent: Saturday, February 28, 2015 5:19 PM
> To: linux-kernel@vger.kernel.org
> Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
> dereference
> 
> 
> 
> > -----Original Message-----
> > From: Justin Piszcz [mailto:jpiszcz@lucidpixels.com]
> > Sent: Friday, February 27, 2015 10:54 AM
> > To: linux-kernel@vger.kernel.org
> > Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
> > dereference
> >
> >
> >
> > > -----Original Message-----
> > > From: Justin Piszcz [mailto:jpiszcz@lucidpixels.com]
> > > Sent: Friday, February 27, 2015 9:54 AM
> > > To: linux-kernel@vger.kernel.org
> > > Subject: 3.19 kernel: BUG: unable to handle kernel NULL pointer
> > dereference
> > >
> > > Hello,
> > >
> > > With kernel 3.15, I do not recall having any issues, with 3.19, I am
> > getting
> > > a kernel crash when I copy files over NFS from machine A to B.
> > > Is this a known issue?
> > >
> > > I suspect it has to do something with this:
> > > Feb 27 09:31:20 remote-host [   15.745342] dmar: DRHD: handling fault
> > status
> > > reg 2
> > > Feb 27 09:31:20 remote-host [   15.745361] dmar: DMAR:[DMA Read]
> > Request
> > > device [04:00.0] fault addr 0 #012[   15.745361] DMAR:[fault reason
06]
> > PTE
> > > Read access is not set
> > >
> >
> > [ .. ]
> >
> > Here is another crash with debugging enabled:
> >
> 
> [ .. ]
> 

[ . ]

Sorry for the spam-- still occurs, will remove the NVIDIA card, looks like
it is still an issue for users--
https://bugs.freedesktop.org/show_bug.cgi?id=66696

Justin.




      reply	other threads:[~2015-02-28 22:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 14:53 3.19 kernel: BUG: unable to handle kernel NULL pointer dereference Justin Piszcz
2015-02-27 15:53 ` Justin Piszcz
2015-02-28 22:19   ` Justin Piszcz
2015-02-28 22:57     ` Justin Piszcz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='006901d053a9$dcf5a950$96e0fbf0$@lucidpixels.com' \
    --to=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox