Re: ruby 2.6.0 oops+crash when accessing /dev/tty18

[Aivils S. <Aiv...@un...>]

Long holidays elapse so fast.

>On Mon, Dec 29, 2003 at 02:28:32PM +0200, Aivils Stoss wrote:
>>
>> >I have two framebuffers and fbcon, and ruby 2.6.0
>> >vc 1-16 on fb0 seems to work fine.
>>
>> cat /var/log/dmesg | grep Console
>> should show Your VT-VC configuration.
>> "Console ... matrox ... take over ... vc:1-16"
>> "Console ... matrox ... vc:17-32"
>> and similar
>> cat /var/log/dmesg | grep "keyboard\.c"
>>
>Thanks.
>
>This is what I have:
>Console: Colour VGA+ 80x25 vc:1-16
>Console: mono dummy device 80x25 vc:17-17

You must have more. fbcon initializing add some lines, actualy
"take over" , when takes over VGA console, take_over_console() vt.c
Secondary matrox_crt2 should come in dmesg to, fbcon_add() fbcon.c.

According Your dmesg, fbcon was not initialized.

>Is it possible to get 17 connected to the scond framebuffer
>instead of a dummy device?

Yes. But order is hardcoded first all DUMMY then all FB consoles,
seems this must be vice versa. dumbcon=0
1st fb take over VGA and so vc:1-16
2nd fb have vc:17-32
with hardcoded vgacon and fbcon.

>Seems there is no 18 then.  Trying to use 17
>is almost as bad though - letting an xserver use vt17
>goes into D-state as shown by "ps aux".
>So I keep running 2.6.0-test11+ruby, where vt17 works.
?

Aivils Stoss