Trouble on kernel

Trouble on kernel

[Martin Kaffanke]

Hi there,

Sometimes my computer crashes since i use now ubuntu 13.10 with 
unity/compiz.

dmesg tells me:

[  686.209019] nouveau E[    PBUS][0000:00:0d.0] MMIO write of 
0x00000000 FAULT at 0x00b020

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

So I don't really know where to start for debugging,
if you could help me that would be great.

Full dmesg output on http://ubuntuone.com/3AVhp6HT2jU26HdfguAbdV

thanks,
Martin

Re: Trouble on kernel

[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.

>
> 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?)

>
> 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

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.

>
> So I don't really know where to start for debugging,
> if you could help me that would be great.
>
> Full dmesg output on http://ubuntuone.com/3AVhp6HT2jU26HdfguAbdV
>
> thanks,
> Martin
> _______________________________________________
> Nouveau mailing list
> Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
> http://lists.freedesktop.org/mailman/listinfo/nouveau

Re: Trouble on kernel

[Martin Kaffanke]

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

Re: Trouble on kernel

[Ilia Mirkin]

On Mon, Oct 28, 2013 at 12:31 PM, Martin Kaffanke
<martin.kaffanke-RbZlAiThDcE@public.gmane.org> wrote:
> 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)

OK, good.

>
>
>>> 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?

Meh. Like I said, don't worry about it. On closer inspection, it's
most likely the nv31_mpeg_tile_prog function. Although why it's
getting addresses of 0... I don't know. (And also why it's getting
run, I don't know either. Something must be starting up either xvmc or
vdpau, the latter of which won't work for your card.)

>
>
>>> 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?

envytools. rnn/lookup. But you don't need to run it, I was just using
it to decode that error message to figure out what command triggered
the bad argument error.

>
>
>> 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?

Well, if compiz/something else *crashes* (i.e.
segfault/sigbus/whatever), it's likely there's a log of it. Perhaps
look in .xsession-errors, or run it inside gdb? Or are you saying that
you get a hard hang? Can you ssh into the machine when that happens?

  -ilia

Re: Trouble on kernel

[Martin Kaffanke]

Am 2013-10-28 17:55, schrieb Ilia Mirkin:
> On Mon, Oct 28, 2013 at 12:31 PM, Martin Kaffanke
> <martin.kaffanke-RbZlAiThDcE@public.gmane.org> wrote:
>> Am 2013-10-28 15:42, schrieb Ilia Mirkin:
>>>> 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?
>
> Meh. Like I said, don't worry about it. On closer inspection, it's
> most likely the nv31_mpeg_tile_prog function. Although why it's
> getting addresses of 0... I don't know. (And also why it's getting
> run, I don't know either. Something must be starting up either xvmc or
> vdpau, the latter of which won't work for your card.)

Ok, if that is not my problem, so that doesn't matter.

>
> Well, if compiz/something else *crashes* (i.e.
> segfault/sigbus/whatever), it's likely there's a log of it. Perhaps
> look in .xsession-errors, or run it inside gdb? Or are you saying that
> you get a hard hang? Can you ssh into the machine when that happens?

Hm.  I don't really know, i installed the ssh server not so i can test this.

but the last 'crash', the xserver was not possible to work on it any more,
just seeing horizontal stripes instead of a picture, let me go back to the
console and dmesg gives now additional:

[29361.912198] nouveau E[   PFIFO][0000:00:0d.0] CACHE_ERROR - ch 1 
[Xorg[1029]] subc 4 mthd 0x0188 data 0x80000003
[29361.912206] nouveau E[  PGRAPH][0000:00:0d.0]  ERROR nsource: 
ILLEGAL_MTHD nstatus: INVALID_STATE BAD_ARGUMENT PROTECTION_FAULT

see the full dmesg:
http://ubuntuone.com/5rZQABeUirzvxUSIDhWTcY

After that i made a reboot, because a 'sudo service lightdm restart' 
does something strange:  I have an additional LightDM User there, which 
is not there after reboot....  - but thats another problem. :)

Martin

Re: Trouble on kernel

[Martin Kaffanke]

Am 2013-10-28 17:55, schrieb Ilia Mirkin:

> Well, if compiz/something else *crashes* (i.e.
> segfault/sigbus/whatever), it's likely there's a log of it. Perhaps
> look in .xsession-errors, or run it inside gdb? Or are you saying that
> you get a hard hang? Can you ssh into the machine when that happens?

Ok, now I can tell you, it is not reachable via ssh when i see the stripes
on the monitor, but it is before. :(

Thanks for your help,
Martin