[Nouveau] [INVALID_ARG] mthd 0414

[Nouveau] [INVALID_ARG] mthd 0414

[dmanye]

[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]

hello,

i have a problem and i think that it is in the nouveau driver. i hope 
you can help me...

i have 20 identical computers with debian bullseye (11) installed (only 
"official" debian packages). sometimes some of them boot but the screen 
is remains in black. if i connect remotely i can see that the X session 
starts as expected (i have set a lightdm autologin). restarting lightdm 
does not help, but rebooting the computer solves the problem but it 
reappears here and there (when i boot all the computers, between 0 and 2 
usually get the black screen).

i've noticed that this three lines appear always in dmesg when it fails:

[    4.090415] nouveau 0000:07:00.0: disp: chid 0 stat 00004414 reason 4 
[INVALID_ARG] mthd 0414 data 00000000 code 00000001
[    4.090430] nouveau 0000:07:00.0: disp: chid 0 stat 10004418 reason 4 
[INVALID_ARG] mthd 0418 data 00000000 code 00000001
[    4.090445] nouveau 0000:07:00.0: disp: chid 0 stat 10004424 reason 4 
[INVALID_ARG] mthd 0424 data 00000000 code 00000001

i can solve it without rebooting by unloading and loading again the 
nouveau driver

kernel version is 5.10.46-4

nouveau driver debian package is 1:1.0.17-1

i attach dmesg log in case it could help.

please don't hesitate to ask for more info if you need it.

thank you in advance.



[-- Attachment #2: dmesg.log.gz --]
[-- Type: application/gzip, Size: 18307 bytes --]

Re: [Nouveau] [INVALID_ARG] mthd 0414

[Karol Herbst]

On Thu, Nov 18, 2021 at 2:59 PM dmanye <dmanye@urv.cat> wrote:
>
> hello,
>
> i have a problem and i think that it is in the nouveau driver. i hope
> you can help me...
>
> i have 20 identical computers with debian bullseye (11) installed (only
> "official" debian packages). sometimes some of them boot but the screen
> is remains in black. if i connect remotely i can see that the X session
> starts as expected (i have set a lightdm autologin). restarting lightdm
> does not help, but rebooting the computer solves the problem but it
> reappears here and there (when i boot all the computers, between 0 and 2
> usually get the black screen).
>

What kind of connector are you using? I have a gk208B GPU here so I
could see if I hit this bug if I just reboot often enough on 5.10

> i've noticed that this three lines appear always in dmesg when it fails:
>
> [    4.090415] nouveau 0000:07:00.0: disp: chid 0 stat 00004414 reason 4
> [INVALID_ARG] mthd 0414 data 00000000 code 00000001
> [    4.090430] nouveau 0000:07:00.0: disp: chid 0 stat 10004418 reason 4
> [INVALID_ARG] mthd 0418 data 00000000 code 00000001
> [    4.090445] nouveau 0000:07:00.0: disp: chid 0 stat 10004424 reason 4
> [INVALID_ARG] mthd 0424 data 00000000 code 00000001
>
> i can solve it without rebooting by unloading and loading again the
> nouveau driver
>
> kernel version is 5.10.46-4
>
> nouveau driver debian package is 1:1.0.17-1
>
> i attach dmesg log in case it could help.
>
> please don't hesitate to ask for more info if you need it.
>
> thank you in advance.
>
>

Re: [Nouveau] [INVALID_ARG] mthd 0414

[dmanye]

On 18/11/21 16:13, Karol Herbst wrote:
> On Thu, Nov 18, 2021 at 2:59 PM dmanye <dmanye@urv.cat> wrote:
>> hello,
>>
>> i have a problem and i think that it is in the nouveau driver. i hope
>> you can help me...
>>
>> i have 20 identical computers with debian bullseye (11) installed (only
>> "official" debian packages). sometimes some of them boot but the screen
>> is remains in black. if i connect remotely i can see that the X session
>> starts as expected (i have set a lightdm autologin). restarting lightdm
>> does not help, but rebooting the computer solves the problem but it
>> reappears here and there (when i boot all the computers, between 0 and 2
>> usually get the black screen).
>>
> What kind of connector are you using? I have a gk208B GPU here so I
> could see if I hit this bug if I just reboot often enough on 5.10

i'm using vga cables. when the bug appears i can confirm with other 
computer that is not a cable/monitor problema. should i try other 
connector when the bug appears in case it chooses other output by 
mistake...?

thanks.

>
>> i've noticed that this three lines appear always in dmesg when it fails:
>>
>> [    4.090415] nouveau 0000:07:00.0: disp: chid 0 stat 00004414 reason 4
>> [INVALID_ARG] mthd 0414 data 00000000 code 00000001
>> [    4.090430] nouveau 0000:07:00.0: disp: chid 0 stat 10004418 reason 4
>> [INVALID_ARG] mthd 0418 data 00000000 code 00000001
>> [    4.090445] nouveau 0000:07:00.0: disp: chid 0 stat 10004424 reason 4
>> [INVALID_ARG] mthd 0424 data 00000000 code 00000001
>>
>> i can solve it without rebooting by unloading and loading again the
>> nouveau driver
>>
>> kernel version is 5.10.46-4
>>
>> nouveau driver debian package is 1:1.0.17-1
>>
>> i attach dmesg log in case it could help.
>>
>> please don't hesitate to ask for more info if you need it.
>>
>> thank you in advance.
>>
>>

Re: [Nouveau] [INVALID_ARG] mthd 0414

[Karol Herbst]

On Fri, Nov 19, 2021 at 9:10 AM dmanye <dmanye@urv.cat> wrote:
>
> On 18/11/21 16:13, Karol Herbst wrote:
> > On Thu, Nov 18, 2021 at 2:59 PM dmanye <dmanye@urv.cat> wrote:
> >> hello,
> >>
> >> i have a problem and i think that it is in the nouveau driver. i hope
> >> you can help me...
> >>
> >> i have 20 identical computers with debian bullseye (11) installed (only
> >> "official" debian packages). sometimes some of them boot but the screen
> >> is remains in black. if i connect remotely i can see that the X session
> >> starts as expected (i have set a lightdm autologin). restarting lightdm
> >> does not help, but rebooting the computer solves the problem but it
> >> reappears here and there (when i boot all the computers, between 0 and 2
> >> usually get the black screen).
> >>
> > What kind of connector are you using? I have a gk208B GPU here so I
> > could see if I hit this bug if I just reboot often enough on 5.10
>
> i'm using vga cables. when the bug appears i can confirm with other
> computer that is not a cable/monitor problema. should i try other
> connector when the bug appears in case it chooses other output by
> mistake...?
>
> thanks.
>

yeah.. not quite sure yet. I tried it out with my gk208b gpus, but
couldn't hit anything. Maybe using VGA makes the difference here. Or
something else is different. Might also already be fixed in 5.16...
too many unknowns still. I will do another round of testing with VGA
and see how that ends.

> >
> >> i've noticed that this three lines appear always in dmesg when it fails:
> >>
> >> [    4.090415] nouveau 0000:07:00.0: disp: chid 0 stat 00004414 reason 4
> >> [INVALID_ARG] mthd 0414 data 00000000 code 00000001
> >> [    4.090430] nouveau 0000:07:00.0: disp: chid 0 stat 10004418 reason 4
> >> [INVALID_ARG] mthd 0418 data 00000000 code 00000001
> >> [    4.090445] nouveau 0000:07:00.0: disp: chid 0 stat 10004424 reason 4
> >> [INVALID_ARG] mthd 0424 data 00000000 code 00000001
> >>
> >> i can solve it without rebooting by unloading and loading again the
> >> nouveau driver
> >>
> >> kernel version is 5.10.46-4
> >>
> >> nouveau driver debian package is 1:1.0.17-1
> >>
> >> i attach dmesg log in case it could help.
> >>
> >> please don't hesitate to ask for more info if you need it.
> >>
> >> thank you in advance.
> >>
> >>
>

Re: [Nouveau] [INVALID_ARG] mthd 0414

[dmanye]

On 19/11/21 13:31, Karol Herbst wrote:
> yeah.. not quite sure yet. I tried it out with my gk208b gpus, but
> couldn't hit anything. Maybe using VGA makes the difference here. Or
> something else is different. Might also already be fixed in 5.16...
> too many unknowns still. I will do another round of testing with VGA
> and see how that ends.

hello again,

thanks for your effort Karol. i've just found another time the bug and:

1) kept the vga cable in the same place.

2) connected a dvi cable between the same computer and the same monitor.

3) told xrandr to dup the signal through the dvi cable:

DISPLAY=:0.0 xrandr --output DVI-D-1 --mode "1920x1080" --same-as VGA-1

4) voilà! the monitor, all alone, switched to dvi input and there is my 
x session up and running.

5) if i force the monitor to change to vga input it refuses it and 
returns to dvi

so i think the driver does its job but without actually sending anything 
through the vga cable.


thanks.

Re: [Nouveau] [INVALID_ARG] mthd 0414

[Karol Herbst]

On Fri, Nov 19, 2021 at 2:00 PM dmanye <dmanye@urv.cat> wrote:
>
> On 19/11/21 13:31, Karol Herbst wrote:
> > yeah.. not quite sure yet. I tried it out with my gk208b gpus, but
> > couldn't hit anything. Maybe using VGA makes the difference here. Or
> > something else is different. Might also already be fixed in 5.16...
> > too many unknowns still. I will do another round of testing with VGA
> > and see how that ends.
>
> hello again,
>
> thanks for your effort Karol. i've just found another time the bug and:
>
> 1) kept the vga cable in the same place.
>
> 2) connected a dvi cable between the same computer and the same monitor.
>
> 3) told xrandr to dup the signal through the dvi cable:
>
> DISPLAY=:0.0 xrandr --output DVI-D-1 --mode "1920x1080" --same-as VGA-1
>
> 4) voilà! the monitor, all alone, switched to dvi input and there is my
> x session up and running.
>
> 5) if i force the monitor to change to vga input it refuses it and
> returns to dvi
>
> so i think the driver does its job but without actually sending anything
> through the vga cable.
>

yeah.. not quite sure yet what's going on here. Maybe the cable are
just a bit broken, or.... other signals interfering or whatever. Maybe
a driver bug. VGA being an analog signal and stuff makes it a bit
painful to tell what's wrong. If dmesg is clean, then no idea how to
dig into this even. I couldn't reproduce it with my Fedora system
running the latest 5.10 kernel either with VGA.

Could also be the displays being weird...

Anyway, if using DVI is an option for you I highly recommend using
that. But I'd also like to figure out what's wrong here.

What I think could help is to enable drm debugging once you hit the
error. For that you can write "0x1ff" into
/sys/module/drm/paramters/debug as root, restart X, change the
resolution via xrandr to force X to set a new mode on the connector
and pastebin the output of dmesg somewhere. Maybe that helps, maybe
not. Let's see what information that gives us.

>
> thanks.
>
>