On Sat, Feb 11, 2023 at 11:48 AM Abel Abraham Camarillo Ojeda <
acam...@verlet.org> wrote:

> anyone? maybe irq storm of somekind? (how to proceed?)
>
> Thanks
>
> On Sun, Feb 5, 2023 at 6:44 AM Abel Abraham Camarillo Ojeda <
> acam...@verlet.org> wrote:
>
>> >Synopsis:      screen brightness via F5/F6 buttons broken in X between
>> nov 17 and jan 05
>> >Category:      amd64
>> >Environment:
>>         System      : OpenBSD 7.2
>>         Details     : OpenBSD 7.2-current (GENERIC.MP) #1020: Sat Feb  4
>> 09:11:04 MST 2023
>>                          dera...@amd64.openbsd.org:
>> /usr/src/sys/arch/amd64/compile/GENERIC.MP
>>
>>         Architecture: OpenBSD.amd64
>>         Machine     : amd64
>> >Description:
>>         With OpenBSD 2022-11-17 I was able to use F5/F6 buttons on
>> thinkpad L470
>>         to decrease/increase brightness. Then I updated 2022-11-17 to
>> 2023-01-05
>>         (I didn't use the laptop without the dock station for a lot of
>> days so
>>         only noticed a few days ago that brightness wasn't working)
>>
>>         I updated to 2023-02-04 to see if it got fixed.
>>
>>         In console (without X): F5/F6 decrease/increase brightness as
>> expected
>>         In xenodm (or i3 wm): F5/F6 slug the system and I cannot move
>>         pointer/press any key on keyboard for some seconds (around 5
>> seconds)
>>
>>         I'm not sure how to bisect this being right now at 2023-02-04,
>> generally
>>         if only kernel if affected I would bisect and compile lots of
>> kernels
>>         for different dates. But since this seems to be Xorg related I'm
>> unsure
>>         how to test this in a isolated fashion without making a mess in
>>         machine...
>> >How-To-Repeat:
>>         press F5 or F6 in laptop keyboard
>> >Fix:
>>         Unknown
>>
>> full sendbug -P as root output attached (gmail issues)
>>
>
I've been able to reproduce this problem with the xbacklight command.
I can get the following ktraces when tracing xorg and doing `xbacklight
-set 50`:

fragment of ktrace -Rf ktrace-xorg.out, notice this:

  8144 Xorg     0.000013 CALL
 ioctl(11,DRM_IOCTL_MODE_GETCONNECTOR,0x7f7ffffc9050)
  8144 Xorg     1.640530 RET   ioctl 0

1.643s blocked in ioctl

more ktrace context:

  8144 Xorg     0.004444 CALL
 ioctl(11,DRM_IOCTL_MODE_GETCONNECTOR,0x7f7ffffc9050)
  8144 Xorg     0.000022 RET   ioctl 0
  8144 Xorg     0.000069 CALL
 ioctl(11,DRM_IOCTL_MODE_GETCONNECTOR,0x7f7ffffc9050)
  8144 Xorg     0.000019 RET   ioctl 0
  8144 Xorg     0.000011 CALL
 ioctl(11,DRM_IOCTL_MODE_GETCONNECTOR,0x7f7ffffc9050)
  8144 Xorg     0.000010 RET   ioctl 0
  8144 Xorg     0.000013 CALL
 ioctl(11,DRM_IOCTL_MODE_GETCONNECTOR,0x7f7ffffc9050)
  8144 Xorg     1.640530 RET   ioctl 0
  8144 Xorg     0.007344 CALL
 ioctl(11,DRM_IOCTL_MODE_GETCONNECTOR,0x7f7ffffc9050)
  8144 Xorg     0.000018 RET   ioctl 0
  8144 Xorg     0.000014 CALL
 ioctl(11,DRM_IOCTL_MODE_GETRESOURCES,0x7f7ffffc90c0)
  8144 Xorg     0.000004 RET   ioctl 0
  8144 Xorg     0.000003 CALL
 ioctl(11,DRM_IOCTL_MODE_GETRESOURCES,0x7f7ffffc90c0)
  8144 Xorg     0.000003 RET   ioctl 0
  8144 Xorg     0.000010 CALL
 ioctl(11,DRM_IOCTL_MODE_LIST_LESSEES,0x7f7ffffc90b0)
  8144 Xorg     0.000002 RET   ioctl -1 errno 22 Invalid argument
  8144 Xorg     0.000040 CALL
 ioctl(11,DRM_IOCTL_MODE_GETCONNECTOR,0x7f7ffffc8e50)
  8144 Xorg     0.000888 RET   ioctl 0
  8144 Xorg     0.000008 CALL
 ioctl(11,DRM_IOCTL_MODE_GETCONNECTOR,0x7f7ffffc8e50)
  8144 Xorg     0.000007 RET   ioctl 0
  8144 Xorg     0.000009 CALL
 ioctl(11,DRM_IOCTL_MODE_OBJ_SETPROPERTY,0x7f7ffffc8d30)
  8144 Xorg     0.002816 RET   ioctl 0
  8144 Xorg     0.000095 CALL
 ioctl(11,DRM_IOCTL_MODE_DESTROYPROPBLOB,0x7f7ffffc8d40)
  8144 Xorg     0.000004 RET   ioctl -1 errno 2 No such file or directory
  8144 Xorg     0.000008 CALL
 ioctl(11,DRM_IOCTL_MODE_GETPROPERTY,0x7f7ffffc8e40)
  8144 Xorg     0.000002 RET   ioctl 0
  8144 Xorg     0.000002 CALL
 ioctl(11,DRM_IOCTL_MODE_GETPROPERTY,0x7f7ffffc8e40)
  8144 Xorg     0.000001 RET   ioctl 0
  8144 Xorg     0.000005 CALL
 ioctl(11,DRM_IOCTL_MODE_GETPROPBLOB,0x7f7ffffc8e60)

Reply via email to