All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Kaffanke <martin.kaffanke-RbZlAiThDcE@public.gmane.org>
To: Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
Cc: "nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: Trouble on kernel
Date: Mon, 28 Oct 2013 17:31:23 +0100	[thread overview]
Message-ID: <526E915B.6070509@gmx.at> (raw)
In-Reply-To: <CAKb7UvgaEqjAS7JDnQYio6DynTNk+yaDekwWPQpeEDdDDPmhpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Am 2013-10-28 15:42, schrieb Ilia Mirkin:
> On Mon, Oct 28, 2013 at 3:45 AM, Martin Kaffanke <martin.kaffanke-RbZlAiThDcE@public.gmane.org> wrote:
>> Hi there,
>>
>> Sometimes my computer crashes since i use now ubuntu 13.10 with
>> unity/compiz.
>
> You're on NV4C. Do you have mesa 9.2.1 or later (or pre-9.2)? If you
> have 9.2.0, there are known issues with shader compilation.

it is 9.2.1 as far as i can see in the package names containing mesa 
(glx and dri)

>> dmesg tells me:
>>
>> [  686.209019] nouveau E[    PBUS][0000:00:0d.0] MMIO write of 0x00000000
>> FAULT at 0x00b020
>
> Odd. That's VPE. You should have one... maybe not. Nothing to worry
> about though. (Especially odd that it's showing up multiple times --
> are you trying to use xvmc?)

At the moment I'm trying nothing, its the default installation, i didn't
change something.

Where do I have to look to find it out?

>> and later:
>>
>> [ 1425.565441] nouveau E[  PGRAPH][0000:00:0d.0]  ERROR nsource: DATA_ERROR
>> nstatus: BAD_ARGUMENT
>> [ 1425.565462] nouveau E[  PGRAPH][0000:00:0d.0] ch 3 [0x00056000
>> compiz[1970]] subc 2 class 0x0039 mthd 0x0314 data 0x031dc000
>
> A bit more concerning:
>
> $ lookup -a 4c -d NV01_SUBCHAN -- -v obj-class NV03_M2MF 0x0314 0x031dc000
> PITCH_IN => 52281344

lookup seems not to work, the package 'lookup' seems to be a different 
tool, right?

> I'm sure that's above some limit. A pitch of 50MB... I wonder how
> that's happening... If you feel like debugging, the place to look is
> nv30_transfer.c (in mesa). Although I would think this would merely
> cause misrendering, not crashes.

I'm not going to do that, because I really not that competent for that, even
if i know about c programming.

I also think that this can cause missrendering, and not crashes, but it 
also seems
that there aren't stored any messages on the crash, maybe it crashes 
before it can
write something to the harddisk?

But thank you for your help.

Martin

  parent reply	other threads:[~2013-10-28 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28  7:45 Trouble on kernel Martin Kaffanke
     [not found] ` <526E1619.9060402-RbZlAiThDcE@public.gmane.org>
2013-10-28 14:42   ` Ilia Mirkin
     [not found]     ` <CAKb7UvgaEqjAS7JDnQYio6DynTNk+yaDekwWPQpeEDdDDPmhpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-28 16:31       ` Martin Kaffanke [this message]
     [not found]         ` <526E915B.6070509-RbZlAiThDcE@public.gmane.org>
2013-10-28 16:55           ` Ilia Mirkin
     [not found]             ` <CAKb7UvjctRR3KMaTGroeSY7=N4SQgnGvZERo+X8fMh2uJahphA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-28 17:23               ` Martin Kaffanke
2013-10-28 21:29               ` Martin Kaffanke

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=526E915B.6070509@gmx.at \
    --to=martin.kaffanke-rbzlaithdce@public.gmane.org \
    --cc=imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.