Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #75545 > unrolled thread

Bug#1000481: encountered this bug on a POS system (Toshiba Surepos 500) running the same graphic chip

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1000481: encountered this bug on a POS system (Toshiba Surepos 500) running the same graphic chip Bogdan Veringioiu <bogdan.veringioiu@amano.eu> - 2022-06-10 08:10 +0200
    Bug#1000481: Bullseye kernel hangs while initialising i915 gpu driver on old intel graphic chip Diederik de Haas <didi.debian@cknow.org> - 2022-06-10 12:40 +0200
      Bug#1000481: Bullseye kernel hangs while initialising i915 gpu driver on old intel graphic chip Bogdan Veringioiu <bogdan.veringioiu@amano.eu> - 2022-10-28 15:10 +0200
        Bug#1000481: Bullseye kernel hangs while initialising i915 gpu driver on old intel graphic chip Diederik de Haas <didi.debian@cknow.org> - 2022-10-28 15:40 +0200
          Bug#1000481: Bullseye kernel hangs while initialising i915 gpu driver on old intel graphic chip Ben Mueller <letterbox@internix.de> - 2022-10-28 20:10 +0200

#75545 — Bug#1000481: encountered this bug on a POS system (Toshiba Surepos 500) running the same graphic chip

Hello,

the bug is still exists in kernel version 5.10.106 (32 bit).

Also tried a newer kernel linux-image-5.16.0-0.bpo.4 from 
bullseye-backports, with the same result.


Symptoms:

The monitor  gets blank when the i915 changes resolution on boot.

The PC remains accessible (ssh).

xrandr shows no monitor connected. Somehow the i915 driver is not 
detecting the built-in monitor when resolution is changing on boot.

$ xrandr
Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767
VGA1 disconnected primary (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Connecting an external VGA monitor works without issues.

The intel_iommu=off does not work.


Some details about the system below:

lspci

..

00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express 
Integrated Graphics Controller (rev 02)


$ dmesg | grep 915

[    8.816308] i915 0000:00:02.0: vgaarb: deactivate vga console
[    8.846333] i915 0000:00:02.0: [drm] Failed to find VBIOS tables (VBT)
[    8.846882] i915 0000:00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    9.116269] i915 0000:00:02.0: [drm] Initialized overlay support.
[    9.118527] [drm] Initialized i915 1.6.0 20200917 for 0000:00:02.0 on 
minor 0
[    9.163178] fbcon: i915drmfb (fb0) is primary device
[    9.203620] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device


Thank you

Bogdan

[toc] | [next] | [standalone]

#75547 — Bug#1000481: Bullseye kernel hangs while initialising i915 gpu driver on old intel graphic chip

[Multipart message — attachments visible in raw view] — view raw

Control: found -1 linux/5.10.106-1
Control: found -1 linux/5.16.12-1~bpo11+1

On Friday, 10 June 2022 07:57:12 CEST Bogdan Veringioiu wrote:
> the bug is still exists in kernel version 5.10.106 (32 bit).
> 
> Also tried a newer kernel linux-image-5.16.0-0.bpo.4 from
> bullseye-backports, with the same result.

Thanks for that. Metadata updated accordingly.

> Symptoms:
> The monitor  gets blank when the i915 changes resolution on boot.
> The PC remains accessible (ssh).

That seems different from what Ben reported, which may be useful info.
@Ben: can you tell whether you can ssh into your device or not?

> The intel_iommu=off does not work.
> 
> Some details about the system below:
> 
> $ dmesg | grep 915
> 
> [    8.816308] i915 0000:00:02.0: vgaarb: deactivate vga console
> [    8.846333] i915 0000:00:02.0: [drm] Failed to find VBIOS tables (VBT)

When putting "i915 [drm] Failed to find VBIOS tables (VBT)" into a search 
engine, most results were about GPU passthrough (VMs).
I don't see a (direct) connection with this bug, but thought I'd share this 
observation in case it might give a clue to others.

> [    8.846882] i915 0000:00:02.0: vgaarb: changed VGA decodes:
> olddecodes=io+mem,decodes=io+mem:owns=io+mem
> [    9.116269] i915 0000:00:02.0: [drm] Initialized overlay support.
> [    9.118527] [drm] Initialized i915 1.6.0 20200917 for 0000:00:02.0 on
> minor 0
> [    9.163178] fbcon: i915drmfb (fb0) is primary device
> [    9.203620] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device

Request to both Bogdan and Ben:
Can you share the full dmesg output of the 'failing' system and in case of a 
working workaround (like "intel_iommu=off"), also the dmesg output of that?

The full dmesg output may contain clues as to why this issue occurs.

[toc] | [prev] | [next] | [standalone]

#76746 — Bug#1000481: Bullseye kernel hangs while initialising i915 gpu driver on old intel graphic chip

Hi

this issue affecting the LVDS connector was reported here:

https://gitlab.freedesktop.org/drm/intel/-/issues/7301

and fixed.

Any chance it will be backported in 5.10?

Thanks

On 10.06.22 15:01, Bogdan Veringioiu wrote:
> Hi Diederik,
>
> thanks for answering.
>
> I am attaching dmesg, Xorg, xrandr output as well as a listing of 
> /sys/class/drm directory of:
>
> - a buster install running kernel 4.19.98 which is working fine
>
> - a bullseye install running kernel 5.10.106 which is not working
>
> As mentioned intel_iommu parameter does not help me.
>
> After more tests, I understood what is happening under bullseye with 
> 5.10 kernel. The built-in monitor of the POS PC is connected via LVDS. 
> This LVDS connection is not detected/listed at all by the i915 driver 
> upon initialization on boot and the screen goes blank. See the Xorg + 
> xrand outputs. Under buster + kernel 4.19 it works perfectly.
>
> Additionaly (bullseye): If I hook an external VGA monitor using the 
> VGA connector in the back of the POS PC, that monitor is detected and 
> it is working fine, Xorg is using it as the main display. The built-in 
> LVDS monitor remains blank, the LVDS connection is not listed.
>
> Regards
>
> Bogdan
>
>
> On 10.06.22 12:35, Diederik de Haas wrote:
>> Control: found -1 linux/5.10.106-1
>> Control: found -1 linux/5.16.12-1~bpo11+1
>>
>> On Friday, 10 June 2022 07:57:12 CEST Bogdan Veringioiu wrote:
>>> the bug is still exists in kernel version 5.10.106 (32 bit).
>>>
>>> Also tried a newer kernel linux-image-5.16.0-0.bpo.4 from
>>> bullseye-backports, with the same result.
>> Thanks for that. Metadata updated accordingly.
>>
>>> Symptoms:
>>> The monitor  gets blank when the i915 changes resolution on boot.
>>> The PC remains accessible (ssh).
>> That seems different from what Ben reported, which may be useful info.
>> @Ben: can you tell whether you can ssh into your device or not?
>>
>>> The intel_iommu=off does not work.
>>>
>>> Some details about the system below:
>>>
>>> $ dmesg | grep 915
>>>
>>> [    8.816308] i915 0000:00:02.0: vgaarb: deactivate vga console
>>> [    8.846333] i915 0000:00:02.0: [drm] Failed to find VBIOS tables 
>>> (VBT)
>> When putting "i915 [drm] Failed to find VBIOS tables (VBT)" into a 
>> search
>> engine, most results were about GPU passthrough (VMs).
>> I don't see a (direct) connection with this bug, but thought I'd 
>> share this
>> observation in case it might give a clue to others.
>>
>>> [    8.846882] i915 0000:00:02.0: vgaarb: changed VGA decodes:
>>> olddecodes=io+mem,decodes=io+mem:owns=io+mem
>>> [    9.116269] i915 0000:00:02.0: [drm] Initialized overlay support.
>>> [    9.118527] [drm] Initialized i915 1.6.0 20200917 for 
>>> 0000:00:02.0 on
>>> minor 0
>>> [    9.163178] fbcon: i915drmfb (fb0) is primary device
>>> [    9.203620] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer 
>>> device
>> Request to both Bogdan and Ben:
>> Can you share the full dmesg output of the 'failing' system and in 
>> case of a
>> working workaround (like "intel_iommu=off"), also the dmesg output of 
>> that?
>>
>> The full dmesg output may contain clues as to why this issue occurs.
>

[toc] | [prev] | [next] | [standalone]

#76747 — Bug#1000481: Bullseye kernel hangs while initialising i915 gpu driver on old intel graphic chip

[Multipart message — attachments visible in raw view] — view raw

On Friday, 28 October 2022 14:57:12 CEST Bogdan Veringioiu wrote:
> this issue affecting the LVDS connector was reported here:
> 
> https://gitlab.freedesktop.org/drm/intel/-/issues/7301
> 
> and fixed.
> 
> Any chance it will be backported in 5.10?

https://lore.kernel.org/all/20221026101134.20865-1-ville.syrjala@linux.intel.com/
is where the changes have been submitted upstream.
When that gets accepted by the upstream maintainer, then a request for a
backport to the _upstream_ 5.10 kernel can be made and when done and accepted
then it should land in Debian's 5.10 kernel too.

Ben: it would be really great and interesting to know whether the patches would
solve your issue too. Are you able to test that?

[toc] | [prev] | [next] | [standalone]

#76750 — Bug#1000481: Bullseye kernel hangs while initialising i915 gpu driver on old intel graphic chip

On 10/28/22 15:27, Diederik de Haas wrote:
> On Friday, 28 October 2022 14:57:12 CEST Bogdan Veringioiu wrote:
>> this issue affecting the LVDS connector was reported here:
>>
>> https://gitlab.freedesktop.org/drm/intel/-/issues/7301
>>
>> and fixed.
>>
>> Any chance it will be backported in 5.10?
> 
> https://lore.kernel.org/all/20221026101134.20865-1-ville.syrjala@linux.intel.com/
> is where the changes have been submitted upstream.
> When that gets accepted by the upstream maintainer, then a request for a
> backport to the _upstream_ 5.10 kernel can be made and when done and accepted
> then it should land in Debian's 5.10 kernel too.
> 
> Ben: it would be really great and interesting to know whether the patches would
> solve your issue too. Are you able to test that?

Unfortunately I don't use this hardware anymore. But I could power it up 
once again, when the patches made it into the Debian kernel.

   Ben

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web