On Thu, Aug 02, 2012 at 01:26:55PM +0200, Ortwin Gl?ck wrote:
> I have managed to turn the crash into a WARN_ON, by adding this to the
> begin of nouveau_software_vblank():
>
> if (!psw) {
> WARN_ON(1);
> return;
> }
Yes, I know about it, but t
I have managed to turn the crash into a WARN_ON, by adding this to the
begin of nouveau_software_vblank():
if (!psw) {
WARN_ON(1);
return;
}
And I have also managed to load the module manually instead by udev. So
I am happy to attach a full lo
On Thu, Aug 02, 2012 at 01:26:55PM +0200, Ortwin Glück wrote:
> I have managed to turn the crash into a WARN_ON, by adding this to the
> begin of nouveau_software_vblank():
>
> if (!psw) {
> WARN_ON(1);
> return;
> }
Yes, I know about it, but t
On 30.07.2012 19:16, Marcin Slusarz wrote:
> Are you sure you boot the correct kernel? I'm asking because your panic says
> its
> version is "3.5.0 #3" - exactly the same as in previous crash log.
I am using the correct kernel, don't worry. (.version may not be
incremented on each build necessar
Yes, as far as I can tell. I didn't do anything different this time. The date
on the kernel file looks ok. Just did a fresh make && make install again, and
got the same behaviour. When is that number after the hash sign upped?
Marcin Slusarz wrote:
>Are you sure you boot the correct kernel? I
Yes, as far as I can tell. I didn't do anything different this time. The date
on the kernel file looks ok. Just did a fresh make && make install again, and
got the same behaviour. When is that number after the hash sign upped?
Marcin Slusarz wrote:
>Are you sure you boot the correct kernel? I
On 29.07.2012 22:15, Marcin Slusarz wrote:
No, the real problem is: with "noaccel" we don't register "software engine",
but vblank ISR relies on its existance and happily derefences NULL pointer.
Now, this patch should fix it for real...
Unfortunately I am still seeing the crash. Without "noac
On Mon, Jul 30, 2012 at 01:16:37PM +0200, Ortwin Gl?ck wrote:
> On 29.07.2012 22:15, Marcin Slusarz wrote:
> > No, the real problem is: with "noaccel" we don't register "software engine",
> > but vblank ISR relies on its existance and happily derefences NULL pointer.
> >
> > Now, this patch should
On 29.07.2012 22:15, Marcin Slusarz wrote:
> No, the real problem is: with "noaccel" we don't register "software engine",
> but vblank ISR relies on its existance and happily derefences NULL pointer.
>
> Now, this patch should fix it for real...
Unfortunately I am still seeing the crash. Without "
Hey,
Op 29-07-12 22:15, Marcin Slusarz schreef:
> On Thu, Jul 26, 2012 at 02:56:22PM +0200, Ortwin Gl?ck wrote:
>> On 25.07.2012 20:42, Marcin Slusarz wrote:
>>> Good, below patch should fix this panic.
>>>
>>> Note that you can hit an oops in drm_handle_vblank because patch from
>>> http://lists.
On Mon, Jul 30, 2012 at 01:16:37PM +0200, Ortwin Glück wrote:
> On 29.07.2012 22:15, Marcin Slusarz wrote:
> > No, the real problem is: with "noaccel" we don't register "software engine",
> > but vblank ISR relies on its existance and happily derefences NULL pointer.
> >
> > Now, this patch should
Hey,
Op 29-07-12 22:15, Marcin Slusarz schreef:
> On Thu, Jul 26, 2012 at 02:56:22PM +0200, Ortwin Glück wrote:
>> On 25.07.2012 20:42, Marcin Slusarz wrote:
>>> Good, below patch should fix this panic.
>>>
>>> Note that you can hit an oops in drm_handle_vblank because patch from
>>> http://lists.
On Thu, Jul 26, 2012 at 02:56:22PM +0200, Ortwin Gl?ck wrote:
> On 25.07.2012 20:42, Marcin Slusarz wrote:
> > Good, below patch should fix this panic.
> >
> > Note that you can hit an oops in drm_handle_vblank because patch from
> > http://lists.freedesktop.org/archives/dri-devel/2012-May/023498.h
On 25.07.2012 20:42, Marcin Slusarz wrote:
Good, below patch should fix this panic.
Note that you can hit an oops in drm_handle_vblank because patch from
http://lists.freedesktop.org/archives/dri-devel/2012-May/023498.html
has not been applied (yet?).
After applying your patch, it still crashe
On Thu, Jul 26, 2012 at 02:56:22PM +0200, Ortwin Glück wrote:
> On 25.07.2012 20:42, Marcin Slusarz wrote:
> > Good, below patch should fix this panic.
> >
> > Note that you can hit an oops in drm_handle_vblank because patch from
> > http://lists.freedesktop.org/archives/dri-devel/2012-May/023498.h
On Thu, Jul 26, 2012 at 02:56:22PM +0200, Ortwin Gl?ck wrote:
> On 25.07.2012 20:42, Marcin Slusarz wrote:
> > Good, below patch should fix this panic.
> >
> > Note that you can hit an oops in drm_handle_vblank because patch from
> > http://lists.freedesktop.org/archives/dri-devel/2012-May/023498.h
On 25.07.2012 20:42, Marcin Slusarz wrote:
> Good, below patch should fix this panic.
>
> Note that you can hit an oops in drm_handle_vblank because patch from
> http://lists.freedesktop.org/archives/dri-devel/2012-May/023498.html
> has not been applied (yet?).
After applying your patch, it still
On Thu, Jul 26, 2012 at 02:56:22PM +0200, Ortwin Glück wrote:
> On 25.07.2012 20:42, Marcin Slusarz wrote:
> > Good, below patch should fix this panic.
> >
> > Note that you can hit an oops in drm_handle_vblank because patch from
> > http://lists.freedesktop.org/archives/dri-devel/2012-May/023498.h
Does it work if you boot without X and modprobe nouveau manually? If it does,
can you disable page flipping in xorg.conf (Option "PageFlip" "0" in nouveau
device section) and recheck with X?
It happens long before X, when the nouveau module is loaded.
Does it work if you disable acceleration (
On 24.07.2012 19:00, Marcin Slusarz wrote:
Please post the crash log.
Sorry, I was not precise: it boots until drm performs modesetting (so it
seems). The screen goes black and the machine is dead. So there is
nothing I could post here, unfortunately.
This is a video of 3.5 booting:
http://
On Wed, Jul 25, 2012 at 10:46:49AM +0200, Ortwin Gl?ck wrote:
> > Does it work if you boot without X and modprobe nouveau manually? If it
> > does,
> > can you disable page flipping in xorg.conf (Option "PageFlip" "0" in nouveau
> > device section) and recheck with X?
>
> It happens long before X
On Wed, Jul 25, 2012 at 10:46:49AM +0200, Ortwin Glück wrote:
> > Does it work if you boot without X and modprobe nouveau manually? If it
> > does,
> > can you disable page flipping in xorg.conf (Option "PageFlip" "0" in nouveau
> > device section) and recheck with X?
>
> It happens long before X
> Does it work if you boot without X and modprobe nouveau manually? If it does,
> can you disable page flipping in xorg.conf (Option "PageFlip" "0" in nouveau
> device section) and recheck with X?
It happens long before X, when the nouveau module is loaded.
> Does it work if you disable accelerat
On Tue, Jul 24, 2012 at 07:22:52PM +0200, Ortwin Gl?ck wrote:
> On 24.07.2012 19:00, Marcin Slusarz wrote:
> > Please post the crash log.
>
> Sorry, I was not precise: it boots until drm performs modesetting (so it
> seems). The screen goes black and the machine is dead. So there is
> nothing I
On 24.07.2012 19:00, Marcin Slusarz wrote:
> Please post the crash log.
Sorry, I was not precise: it boots until drm performs modesetting (so it
seems). The screen goes black and the machine is dead. So there is
nothing I could post here, unfortunately.
This is a video of 3.5 booting:
http://ww
On Mon, Jul 23, 2012 at 08:01:14PM +0200, Ortwin Gl?ck wrote:
> Hi,
>
> My HP Elitebook 8540w now crashes on boot with 3.5. All works fine with
> 3.4. Bisected to the following commit:
>
> 20abd1634a6e2eedb84ca977adea56b8aa06cc3e is the first bad commit
> commit 20abd1634a6e2eedb84ca977adea56b8a
On Tue, Jul 24, 2012 at 07:22:52PM +0200, Ortwin Glück wrote:
> On 24.07.2012 19:00, Marcin Slusarz wrote:
> > Please post the crash log.
>
> Sorry, I was not precise: it boots until drm performs modesetting (so it
> seems). The screen goes black and the machine is dead. So there is
> nothing I
On Mon, Jul 23, 2012 at 08:01:14PM +0200, Ortwin Glück wrote:
> Hi,
>
> My HP Elitebook 8540w now crashes on boot with 3.5. All works fine with
> 3.4. Bisected to the following commit:
>
> 20abd1634a6e2eedb84ca977adea56b8aa06cc3e is the first bad commit
> commit 20abd1634a6e2eedb84ca977adea56b8a
Hi,
My HP Elitebook 8540w now crashes on boot with 3.5. All works fine with
3.4. Bisected to the following commit:
20abd1634a6e2eedb84ca977adea56b8aa06cc3e is the first bad commit
commit 20abd1634a6e2eedb84ca977adea56b8aa06cc3e
Author: Ben Skeggs
Date: Mon Apr 30 11:33:43 2012 -0500
dr
Hi,
My HP Elitebook 8540w now crashes on boot with 3.5. All works fine with
3.4. Bisected to the following commit:
20abd1634a6e2eedb84ca977adea56b8aa06cc3e is the first bad commit
commit 20abd1634a6e2eedb84ca977adea56b8aa06cc3e
Author: Ben Skeggs
Date: Mon Apr 30 11:33:43 2012 -0500
drm
30 matches
Mail list logo
