xorg issueshttps://gitlab.freedesktop.org/groups/xorg/-/issues2024-01-03T19:46:47Zhttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1057Fix 1bpp Xservers on "whitePixel=0, blackPixel=1" VRAMs2024-01-03T19:46:47ZIzumi TsutsuiFix 1bpp Xservers on "whitePixel=0, blackPixel=1" VRAMsI'm working on porting ancient X11R6/XFree86 based Xsun servers to build with recent Xorg 1.20 DIX APIs for old sun machines still supported by NetBSD. The Xsun server in the NetBSD local tree is now functional on 8bpp cgtwo on sun3, 8b...I'm working on porting ancient X11R6/XFree86 based Xsun servers to build with recent Xorg 1.20 DIX APIs for old sun machines still supported by NetBSD. The Xsun server in the NetBSD local tree is now functional on 8bpp cgtwo on sun3, 8bpp cgsix on SPARCstation, and 1bpp bwtwo on sun3.
- http://cvsweb.netbsd.org/bsdweb.cgi/xsrc/external/mit/xorg-server/dist/hw/sun/
- https://twitter.com/tsutsuii/status/1283063395248254976
- https://twitter.com/tsutsuii/status/1284605639587553280
To support sun3 bwtwo 1bpp framebuffer, I had to modify several DIX fb colormap code because its VRAM requires "whitePixel=0, blackPixel=1" settings (i.e. `-flipPixels` settings should be default). It would be great if my local changes will also be applied to upstream xorg tree.
There are two problem to support inverted b&w settings:
### (1) `fbSetupScreen()` in fb/fbscreen.c implicitly overwrites `blackPixel` and `whitePixel`
`fbSetupScreen()` has the following code:
https://gitlab.freedesktop.org/xorg/xserver/-/blob/0803918e64262482035f042e5e1f2a571d3dea1b/fb/fbscreen.c#L93
```c
/* let CreateDefColormap do whatever it wants for pixels */
pScreen->blackPixel = pScreen->whitePixel = (Pixel) 0;
```
However it doesn't seem `CreateDefColormap()` handles it in 1bpp case, so `fbSetupScreen()` should leave DDX settings.
### (2) `fbInitializeColormap()` doesn't check `blackPixel` and `whitePixel` on settings 1bpp colormap?
Even if `blackPixel` and `whitePixel` in `ScreenPtr` are set proplery (as `-flipPixels` is specified), it looks `fbInitializeColormap()` doesn't check `blackPixel` and `whitePixel` on settings 1bpp colormap.
Without this colormap settings, at least the following drawing operations don't reflect `blackPixel` and `whitePixel` values (they refer colormap directly even on 1bpp?)
- mouse cursor
- twm titlebar and window frames
- see pics in https://twitter.com/tsutsuii/status/1270362023080017921
To handle this, I had to take an old mfb function `mfbCreateColormap()` derived from X11R6 tree. It just calls `AllocColor()` for two colors per `whitePixel` value. I'm not sure if this should be implemented in the default `fbInitializeColormap()` function, but in NetBSD local tree I've just added an independent function (taken from old tree like https://gitlab.freedesktop.org/xorg/xserver/-/blob/0d7ec5c7d9b451066a079fe56bcc9722341a91ff/mfb/mfbcmap.c#L115 ) for 1bpp servers.
Note I have just noticed the `-flipPixels` option have been removed recently in this commit: https://gitlab.freedesktop.org/xorg/xserver/-/commit/d1c00c859c6676fbb540420c9055788bc19cb18f
but I would also like to denote "it just works with Xorg xf86-video-wsfb driver and this patch, at least Xorg 1.20.5 based NetBSD local tree."
https://twitter.com/tsutsuii/status/1283042381009498120
```diff
From 19c16dce27c220e1ae834e0c4eb10fab112c5b06 Mon Sep 17 00:00:00 2001
From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
Date: Sun, 9 Aug 2020 11:34:23 +0900
Subject: [PATCH] Fix 1bpp Xservers on "whitePixel=0, blackPixel=1" VRAMs.
---
fb/fb.h | 3 +++
fb/fbcmap_mi.c | 35 +++++++++++++++++++++++++++++++++++
fb/fbscreen.c | 12 +++++++++---
3 files changed, 47 insertions(+), 3 deletions(-)
diff --git a/fb/fb.h b/fb/fb.h
index 8ab050d0f..a113baf01 100644
--- a/fb/fb.h
+++ b/fb/fb.h
@@ -734,6 +734,9 @@ fbResolveColor(unsigned short *pred,
extern _X_EXPORT Bool
fbInitializeColormap(ColormapPtr pmap);
+extern _X_EXPORT Bool
+ mfbCreateColormap(ColormapPtr pmap);
+
extern _X_EXPORT int
fbExpandDirectColors(ColormapPtr pmap,
diff --git a/fb/fbcmap_mi.c b/fb/fbcmap_mi.c
index d9976ce9f..18acd2bf1 100644
--- a/fb/fbcmap_mi.c
+++ b/fb/fbcmap_mi.c
@@ -66,6 +66,41 @@ fbInitializeColormap(ColormapPtr pmap)
return miInitializeColormap(pmap);
}
+Bool
+mfbCreateColormap(ColormapPtr pmap)
+{
+ ScreenPtr pScreen;
+ unsigned short red0, green0, blue0;
+ unsigned short red1, green1, blue1;
+ Pixel pix;
+
+ pScreen = pmap->pScreen;
+ if (pScreen->whitePixel == 0)
+ {
+ red0 = green0 = blue0 = ~0;
+ red1 = green1 = blue1 = 0;
+ }
+ else
+ {
+ red0 = green0 = blue0 = 0;
+ red1 = green1 = blue1 = ~0;
+ }
+
+ /* this is a monochrome colormap, it only has two entries, just fill
+ * them in by hand. If it were a more complex static map, it would be
+ * worth writing a for loop or three to initialize it */
+
+ /* this will be pixel 0 */
+ pix = 0;
+ if (AllocColor(pmap, &red0, &green0, &blue0, &pix, 0) != Success)
+ return FALSE;
+
+ /* this will be pixel 1 */
+ if (AllocColor(pmap, &red1, &green1, &blue1, &pix, 0) != Success)
+ return FALSE;
+ return TRUE;
+}
+
int
fbExpandDirectColors(ColormapPtr pmap,
int ndef, xColorItem * indefs, xColorItem * outdefs)
diff --git a/fb/fbscreen.c b/fb/fbscreen.c
index 4ab807ab5..42efaa911 100644
--- a/fb/fbscreen.c
+++ b/fb/fbscreen.c
@@ -100,8 +100,10 @@ fbSetupScreen(ScreenPtr pScreen, void *pbits, /* pointer to screen bitmap */
if (!fbAllocatePrivates(pScreen))
return FALSE;
pScreen->defColormap = FakeClientID(0);
- /* let CreateDefColormap do whatever it wants for pixels */
- pScreen->blackPixel = pScreen->whitePixel = (Pixel) 0;
+ if (bpp > 1) {
+ /* let CreateDefColormap do whatever it wants for pixels */
+ pScreen->blackPixel = pScreen->whitePixel = (Pixel) 0;
+ }
pScreen->QueryBestSize = fbQueryBestSize;
/* SaveScreen */
pScreen->GetImage = fbGetImage;
@@ -118,7 +120,11 @@ fbSetupScreen(ScreenPtr pScreen, void *pbits, /* pointer to screen bitmap */
pScreen->RealizeFont = fbRealizeFont;
pScreen->UnrealizeFont = fbUnrealizeFont;
pScreen->CreateGC = fbCreateGC;
- pScreen->CreateColormap = fbInitializeColormap;
+ if (bpp == 1) {
+ pScreen->CreateColormap = mfbCreateColormap;
+ } else {
+ pScreen->CreateColormap = fbInitializeColormap;
+ }
pScreen->DestroyColormap = (void (*)(ColormapPtr)) NoopDDA;
pScreen->InstallColormap = fbInstallColormap;
pScreen->UninstallColormap = fbUninstallColormap;
--
2.25.3
```https://gitlab.freedesktop.org/xorg/xserver/-/issues/10561bpp server performance regression2023-04-19T15:42:12ZIzumi Tsutsui1bpp server performance regressionPlease consider the following change that causes serious performance regression on 1bpp (monochrome) servers on tiling small patterns.
commit e572bcc7f4236b7e0f23ab762f225b3bce37db59
> fb: Remove even/odd tile slow-pathing
>
> Again, ...Please consider the following change that causes serious performance regression on 1bpp (monochrome) servers on tiling small patterns.
commit e572bcc7f4236b7e0f23ab762f225b3bce37db59
> fb: Remove even/odd tile slow-pathing
>
> Again, clearly meant to be a fast path, but this turns out not to be the
> case.
Details
---
NetBSD still supports several monochrome framebuffers like Sun3 and Omron LUNA. After updates to Xorg 1.20.5 in the NetBSD tree I noticed extreme slowness on filling root_weave bitmap when screen saver was activated.
- Xorg 1.10 based Xsun server on Sun3/60 bwtwo:
https://twitter.com/tsutsuii/status/1289451828036300800
-> Drawing time is not measurable by eyes.
- Xorg 1.20 based Xsun server on Sun3/60 bwtwo:
https://twitter.com/tsutsuii/status/1289437204654075907
-> It takes >10 seconds to fill root window.
- Xorg 1.18 based Xsun server on Sun3/60 bwtwo:
https://twitter.com/tsutsuii/status/1291000288862560256
-> Same as 1.20.
- Xorg 1.20 server + xf86-video-wsfb driver on LUNA using single plane:
https://twitter.com/tsutsuii/status/1291772031525179392
-> Also >10 seconds even on the xf86-video-wsfb driver.
With several investigation, it turns out the above changes to fb/fbtile.c cause this regression:
https://gitlab.freedesktop.org/xorg/xserver/-/commit/e572bcc7f4236b7e0f23ab762f225b3bce37db59
I'm not sure how the *"not to be the case"* in the log was concluded, but the "fast path" of the removed `fbEvenTile()` function was only called if `FbEvenTile(tileWidth)` was true:
https://gitlab.freedesktop.org/xorg/xserver/-/blob/836bb27726441e048bb300664343a136bc596a5b/fb/fbtile.c#L145
```c
void
fbTile(FbBits * dst,
FbStride dstStride,
int dstX,
int width,
int height,
FbBits * tile,
FbStride tileStride,
int tileWidth,
int tileHeight, int alu, FbBits pm, int bpp, int xRot, int yRot)
{
if (FbEvenTile(tileWidth))
fbEvenTile(dst, dstStride, dstX, width, height,
tile, tileStride, tileHeight, alu, pm, xRot, yRot);
```
`FbEvenTile()` is defined in fb/fb.h:
https://gitlab.freedesktop.org/xorg/xserver/-/blob/e572bcc7f4236b7e0f23ab762f225b3bce37db59/fb/fb.h#L543
```c
/*
* Accelerated tiles are power of 2 width <= FB_UNIT
*/
#define FbEvenTile(w) ((w) <= FB_UNIT && FbPowerOfTwo(w))
```
`FB_UNIT` is 32 here, so the "fast path" is activiated only if `tileWidth` arg is 32 or smaller (i.e. 1, 2, 4, 8, or 16).
The main caller of `fbTile()` is `fbFill()` with `FillTiled` op in fb/fbfill.c:
https://gitlab.freedesktop.org/xorg/xserver/-/blob/7430fdb689678b98ac63f5a8dad13719bac777e0/fb/fbfill.c#L164
```c
fbTile(dst + (y + dstYoff) * dstStride,
dstStride,
(x + dstXoff) * dstBpp,
width * dstBpp, height,
tile,
tileStride,
tileWidth * tileBpp,
tileHeight,
pGC->alu,
pPriv->pm,
dstBpp,
(pGC->patOrg.x + pDrawable->x + dstXoff) * dstBpp,
pGC->patOrg.y + pDrawable->y - y);
```
The argument `tileWidth` of `fbTile()` includes bpp, so the "fast path" `fbEvenTile()` won't be called on 32bpp servers.
On the other hand, 1bpp server uses it for 32x32 or smaller bitmaps.
Reverting the above *"fb: Remove even/odd tile slow-pathing"* change significantly improves speed of filling the root_weave and other pattern of Xorg 1bpp server as before:
- Patched Xsun server on Sun3/60 bwtwo:
https://twitter.com/tsutsuii/status/1291061688762957826
- Patched Xorg + xf86-video-wsfb server on LUNA:
https://twitter.com/tsutsuii/status/1291773410964463617https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/545Stale texture data and flicker in small SDL2 program2022-01-23T00:50:22ZKevin CahalanStale texture data and flicker in small SDL2 programVideo of bug: https://youtu.be/O0__VNN9G_o
At 0:11 in the video you see old web browser data showing up in my program.
At 0:19 when I close a window in my program the texture for my piano key letters
flicker. By luck the texture for my...Video of bug: https://youtu.be/O0__VNN9G_o
At 0:11 in the video you see old web browser data showing up in my program.
At 0:19 when I close a window in my program the texture for my piano key letters
flicker. By luck the texture for my keys sometimes flickers to stuff previously
displayed on my desktop. This flickering is linked to my mouse movement/placement.
When I run my program with the proprietary 440 NVIDIA driver things work fine. It also works fine with the opensource Intel video driver on a different computer.
I am on Ubuntu budgie 20.04 using XFCE on X.org X11.
The SDL2 program source:
https://github.com/kevinacahalan/piano_waterfall
git hash 553bb6c8ca18b23494a6c92f4551baa1649f0374
[kernel_log.txt](/uploads/9b4057f74becbef5b17b6611ba36f62a/kernel_log.txt)https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/16The need to release Caps Lock should be removed.2022-09-29T23:45:27Znoone atallThe need to release Caps Lock should be removed.https://wiki.archlinux.org/index.php/Xorg/Keyboard_configuration#Switching_state_immediately_when_Caps_Lock_is_pressed
I'm one of those few people who type using only Caps Lock.
I press Caps Lock, it types upper case as expected then ve...https://wiki.archlinux.org/index.php/Xorg/Keyboard_configuration#Switching_state_immediately_when_Caps_Lock_is_pressed
I'm one of those few people who type using only Caps Lock.
I press Caps Lock, it types upper case as expected then very quickly I tap again however, at this point my right hand is already pressing the next button but Caps Lock requires me to release the button completely which results in 2 upper case letters instead of one.
Every time I install an OS this is something I have to fix. I don't think the current behaviour is of use to anybody.
I would like to also point out to the fact that other operating systems never implemented such behaviour.
I would very much appreciate if this was fixed. This is an old issue I think it's time.https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/18Shader crashes session2020-08-03T14:37:37ZGhost UserShader crashes sessionThe following shader on Shadertoy.com crashes session and needs to be killed before PC is usable again:
!!! IF YOU FOLLOW THIS LINK YOU SESSION MIGHT CRASH !!!
[https://www.shadertoy.com/view/ttf3Dj](https://www.shadertoy.com/view/ttf3D...The following shader on Shadertoy.com crashes session and needs to be killed before PC is usable again:
!!! IF YOU FOLLOW THIS LINK YOU SESSION MIGHT CRASH !!!
[https://www.shadertoy.com/view/ttf3Dj](https://www.shadertoy.com/view/ttf3Dj)
Mutter/Gnome, Kernel 5.7, Firefox 79.0https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/116Regression in 1.6.102020-08-03T12:30:41ZYichao YuRegression in 1.6.10Introduced by https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/388b303c62aa35a245f1704211a023440ad2c488 .
In particular, https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/388b303c62aa35a245f1704211a023440ad2c488#261ec56ec4e...Introduced by https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/388b303c62aa35a245f1704211a023440ad2c488 .
In particular, https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/388b303c62aa35a245f1704211a023440ad2c488#261ec56ec4e63167dfb89d70a34c54b7af676a80_264_268 and https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/388b303c62aa35a245f1704211a023440ad2c488#261ec56ec4e63167dfb89d70a34c54b7af676a80_371_381.
For both lines, `data_len` is the readable data length in bytes. However, the LHS uses the result data type (`XIMStyle` and `XIMHotKeyTrigger`) instead of the read data type (`CARD32` and 3x `CARD32`), i.e.
```patch
diff --git a/modules/im/ximcp/imRmAttr.c b/modules/im/ximcp/imRmAttr.c
index 2491908e..10be5619 100644
--- a/modules/im/ximcp/imRmAttr.c
+++ b/modules/im/ximcp/imRmAttr.c
@@ -265,7 +265,7 @@ _XimAttributeToValue(
if (num > (USHRT_MAX / sizeof(XIMStyle)))
return False;
- if ((sizeof(num) + (num * sizeof(XIMStyle))) > data_len)
+ if ((sizeof(num) + (num * sizeof(CARD32))) > data_len)
return False;
alloc_len = sizeof(XIMStyles) + sizeof(XIMStyle) * num;
if (alloc_len < sizeof(XIMStyles))
@@ -379,7 +379,7 @@ _XimAttributeToValue(
if (num > (UINT_MAX / sizeof(XIMHotKeyTrigger)))
return False;
- if ((sizeof(num) + (num * sizeof(XIMHotKeyTrigger))) > data_len)
+ if ((sizeof(num) + (num * 3 * sizeof(CARD32))) > data_len)
return False;
alloc_len = sizeof(XIMHotKeyTriggers)
+ sizeof(XIMHotKeyTrigger) * num;
```
------
As a side note, I believe the correct version for the `sizeof(num)` is `2 * sizeof(CARD16)` since this is the offset in `data` the array of data starts.https://gitlab.freedesktop.org/xorg/xserver/-/issues/1051Xwayland should not trigger screensavers per default2020-08-12T14:56:19ZMikael KnutssonXwayland should not trigger screensavers per defaultI use `xss-lock` on my Wayland setup to trigger a lock screen and realised a few things:
1. If no activity is detected within `Xwayland`, it will trigger the screensaver without any settings adjustments
2. `Xwayland` has no configuration...I use `xss-lock` on my Wayland setup to trigger a lock screen and realised a few things:
1. If no activity is detected within `Xwayland`, it will trigger the screensaver without any settings adjustments
2. `Xwayland` has no configuration file that it reads from, meaning if you want to turn off the default screensaver setting, you need to pass a command line parameter or after `Xwayland` has started, run `xset s off`
3. Not many WMs that use `Xwayland` actually allow you to change the command line paramters for `Xwayland` (sway and wlroots is my example)
Given how Xwayland is run (inside another WM) I would propose to change the default setting for triggering the screensaver event in Xwayland specifically (which I assume is inherited from Xserver) as if you're running Xwayland you probably have other tools to manage the idle time detection and you're most likely not in an Xwayland client all the time meaning that the triggering of the screensaver is unexpected behaviour?
Personally I do not use idle detection at all and rely on manually locking the screen which may be why I'm hitting this issue.
I'm also fine with if there's an upcoming change to introduce a configuration file for Xwayland however, as I realise that this is perhaps not "standard" or "intended" use.https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/5423d frame-packing mode not supported in X112022-01-23T00:48:31Zmax maier3d frame-packing mode not supported in X11Sorry, if its a foolish question - i'm not a Linux-pro...
I would like to give out a video stream in frame-packing mode to a 3d capable projector. But it seems impossible, because X11 can not handle this mode.
Thats at least what Kodi de...Sorry, if its a foolish question - i'm not a Linux-pro...
I would like to give out a video stream in frame-packing mode to a 3d capable projector. But it seems impossible, because X11 can not handle this mode.
Thats at least what Kodi devs told me, is the reason for the lack of 3d-possibilities in Linux.
So is there a reason for excluding this common 3d-protocol or was it somehow forgotten?
The frame-packing mode was introduced in the HDMI protocol more than 10 years ago.
And is there maybe a way to access the frame-packing mode which is hard to find?https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/540Unable to suspend TU116M (GF 1660 Ti) - regression in 5.7.6+ (nouveau 0000:01...2020-08-18T19:11:12ZMarcin ZajączkowskiUnable to suspend TU116M (GF 1660 Ti) - regression in 5.7.6+ (nouveau 0000:01:00.0: acr: init failed, -110)In kernel 5.7.6+ (tested up to 5.7.10 and 5.8.0-0.rc6.20200723gitd15be546031c - in 5.7.5 it worked fine) it is no longer possible to suspend Hyperbook NH5/Clevo NH55RCQ with GeForce GTX 1660 Mobile (TU116M):
```
kernel: Freezing remaini...In kernel 5.7.6+ (tested up to 5.7.10 and 5.8.0-0.rc6.20200723gitd15be546031c - in 5.7.5 it worked fine) it is no longer possible to suspend Hyperbook NH5/Clevo NH55RCQ with GeForce GTX 1660 Mobile (TU116M):
```
kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
kernel: printk: Suspending console(s) (use no_console_suspend to debug)
↓ related errrors ↓
kernel: xhci_hcd 0000:01:00.2: WARN: xHC CMD_RUN timeout
kernel: PM: suspend_common(): xhci_pci_suspend+0x0/0x100 returns -110
kernel: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110
kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -110
kernel: PM: Device 0000:01:00.2 failed to suspend async: error -110
↑ related errrors ↑
kernel: sd 4:0:0:0: [sda] Synchronizing SCSI cache
kernel: sd 4:0:0:0: [sda] Stopping disk
kernel: PM: Some devices failed to suspend, or early wake event detected
kernel: sd 4:0:0:0: [sda] Starting disk
kernel: PM: resume devices took 2.184 seconds
kernel: OOM killer enabled.
kernel: Restarting tasks ... done.
kernel: PM: suspend exit
...
systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Suspend.
systemd[1]: Dependency failed for Suspend.
systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
systemd[1]: Stopped target Sleep.
```
The suspend process is aborted and the system stays as is (still can be used, once the screen is unlocked).
`01:00.2` is the NVidia's USB host:
```
$ lspci | grep -i nvidia 15:38
01:00.0 VGA compatible controller: NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] (rev a1)
01:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1)
01:00.2 USB controller: NVIDIA Corporation TU116 USB 3.1 Host Controller (rev a1)
01:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU116 USB Type-C UCSI Controller (rev a1)
```
The change is most likely not in the nouveau driver itself, but definitely impacts it. During the system boot the following error and stack trace is visible in the system log (new in 5.7.6):
```
Jul 29 15:11:13 hszpak kernel: fb0: switching to inteldrmfb from EFI VGA
Jul 29 15:11:13 hszpak kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Jul 29 15:11:13 hszpak kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Jul 29 15:11:13 hszpak kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
Jul 29 15:11:13 hszpak kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
Jul 29 15:11:13 hszpak kernel: MXM: GUID detected in BIOS
Jul 29 15:11:13 hszpak kernel: ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20200326/nsarguments-59)
Jul 29 15:11:13 hszpak kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20200326/nsarguments-59)
Jul 29 15:11:13 hszpak kernel: pci 0000:01:00.0: optimus capabilities: enabled, status dynamic power, hda bios codec supported
Jul 29 15:11:13 hszpak kernel: VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.PEG0.PEGP handle
Jul 29 15:11:13 hszpak kernel: nouveau: detected PR support, will not use DSM
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: enabling device (0106 -> 0107)
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: NVIDIA TU116 (168000a1)
Jul 29 15:11:13 hszpak kernel: [drm] Initialized i915 1.6.0 20200313 for 0000:00:02.0 on minor 0
Jul 29 15:11:13 hszpak kernel: ACPI: Video Device [PEGP] (multi-head: no rom: yes post: no)
Jul 29 15:11:13 hszpak kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/input/input25
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: bios: version 90.16.26.00.11
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: fb: 6144 MiB GDDR6
Jul 29 15:11:13 hszpak kernel: input: Logitech Wireless Mouse PID:101f Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C52F.0002/0003:046D:101F.0006/input/input21
Jul 29 15:11:13 hszpak kernel: hid-generic 0003:046D:101F.0006: input,hidraw3: USB HID v1.11 Mouse [Logitech Wireless Mouse PID:101f] on usb-0000:00:14.0-1/input1:1
Jul 29 15:11:13 hszpak kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
Jul 29 15:11:13 hszpak kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input26
Jul 29 15:11:13 hszpak kernel: input: SYNA1202:00 06CB:CD65 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-SYNA1202:00/0018:06CB:CD65.0005/input/input27
Jul 29 15:11:13 hszpak kernel: input: SYNA1202:00 06CB:CD65 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-SYNA1202:00/0018:06CB:CD65.0005/input/input28
Jul 29 15:11:13 hszpak kernel: vga_switcheroo: enabled
Jul 29 15:11:13 hszpak kernel: [TTM] Zone kernel: Available graphics memory: 8046730 KiB
Jul 29 15:11:13 hszpak kernel: [TTM] Zone dma32: Available graphics memory: 2097152 KiB
Jul 29 15:11:13 hszpak kernel: [TTM] Initializing pool allocator
Jul 29 15:11:13 hszpak kernel: [TTM] Initializing DMA pool allocator
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: VRAM: 6144 MiB
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: GART: 536870912 MiB
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: BIT table 'A' not found
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: BIT table 'L' not found
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: TMDS table version 2.0
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: DCB version 4.1
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: DCB outp 00: 02002f52 00020010
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: DCB outp 01: 04814f76 04600010
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: DCB outp 02: 04814f72 00020010
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: DCB conn 02: 00010261
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: DCB conn 04: 01000446
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
Jul 29 15:11:13 hszpak kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes
Jul 29 15:11:13 hszpak kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: DRM: Disabling PCI power management to avoid bug
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes
Jul 29 15:11:13 hszpak kernel: nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes
Jul 29 15:11:13 hszpak kernel: hid-multitouch 0018:06CB:CD65.0005: input,hidraw3: I2C HID v1.00 Mouse [SYNA1202:00 06CB:CD65] on i2c-SYNA1202:00
Jul 29 15:11:13 hszpak kernel: psmouse serio2: synaptics: device claims to have extended capability 0x0c, but I'm not able to read it.
Jul 29 15:11:13 hszpak kernel: fbcon: i915drmfb (fb0) is primary device
Jul 29 15:11:13 hszpak kernel: fbcon: Deferring console take-over
Jul 29 15:11:13 hszpak kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device
Jul 29 15:11:13 hszpak kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device
Jul 29 15:11:13 hszpak kernel: psmouse serio2: synaptics: Unable to initialize device.
Jul 29 15:11:18 hszpak kernel: input: Logitech Wireless Mouse PID:101f as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:046D:C52F.0002/0003:046D:101F.0006/input/input30
Jul 29 15:11:18 hszpak kernel: logitech-hidpp-device 0003:046D:101F.0006: input,hidraw5: USB HID v1.11 Mouse [Logitech Wireless Mouse PID:101f] on usb-0000:00:14.0-1/input1:1
Jul 29 15:11:18 hszpak kernel: input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input14
Jul 29 15:11:19 hszpak kernel: psmouse serio2: Failed to enable mouse on isa0060/serio2
↓ new in 5.7.6 ↓
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: fifo: fault 09 [PHYS_WRITE] at 000000017fef0000 engine c0 [BAR2] client 08 [HUB/HOST_CPU_NB] reason 0d [REGION_VIOLATION] on channel -1 [0000000000 unknown]
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: fifo: fault 09 [PHYS_WRITE] at 000000017fef0000 engine c0 [BAR2] client 08 [HUB/HOST_CPU_NB] reason 0d [REGION_VIOLATION] on channel -1 [0000000000 unknown]
Jul 29 15:11:21 hszpak kernel: ------------[ cut here ]------------
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: timeout
Jul 29 15:11:21 hszpak kernel: WARNING: CPU: 4 PID: 428 at drivers/gpu/drm/nouveau/nvkm/falcon/v1.c:247 nvkm_falcon_v1_wait_for_halt+0x96/0xa0 [nouveau]
Jul 29 15:11:21 hszpak kernel: Modules linked in: hid_logitech_hidpp i915 nouveau hid_multitouch ttm cec rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper mmc_core mxm_wmi crct10dif_pclmul crc32_pclmul crc32c_intel nvme drm nvme_core ghash_clmu>
Jul 29 15:11:21 hszpak kernel: CPU: 4 PID: 428 Comm: plymouthd Not tainted 5.7.6-201.fc32.x86_64 #1
Jul 29 15:11:21 hszpak kernel: Hardware name: Blue Technology Sp. z o.o. NH5_NH7/NH5_NH7, BIOS 1.07.03TBT 11/16/2018
Jul 29 15:11:21 hszpak kernel: RIP: 0010:nvkm_falcon_v1_wait_for_halt+0x96/0xa0 [nouveau]
Jul 29 15:11:21 hszpak kernel: Code: 8b 40 10 48 8b 78 10 4c 8b 67 50 4d 85 e4 75 03 4c 8b 27 e8 1c aa 03 d6 4c 89 e2 48 c7 c7 8c d2 86 c0 48 89 c6 e8 31 56 a3 d5 <0f> 0b eb ba 66 0f 1f 44 00 00 0f 1f 44 00 00 41 54 be 80 96 98 00
Jul 29 15:11:21 hszpak kernel: RSP: 0018:ffffb44840707838 EFLAGS: 00010292
Jul 29 15:11:21 hszpak kernel: RAX: 000000000000001d RBX: ffffffffffffff92 RCX: 0000000000000007
Jul 29 15:11:21 hszpak kernel: RDX: 00000000fffffff8 RSI: 0000000000000092 RDI: ffff8f0b60519cc0
Jul 29 15:11:21 hszpak kernel: RBP: ffff8f0b518cb658 R08: 0000000000000385 R09: 0000000000000003
Jul 29 15:11:21 hszpak kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff8f0b5d738020
Jul 29 15:11:21 hszpak kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffff8f0b5441a000
Jul 29 15:11:21 hszpak kernel: FS: 00007ff013b2cf00(0000) GS:ffff8f0b60500000(0000) knlGS:0000000000000000
Jul 29 15:11:21 hszpak kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 29 15:11:21 hszpak kernel: CR2: 000055b4f79f9198 CR3: 000000045471c006 CR4: 00000000003606e0
Jul 29 15:11:21 hszpak kernel: Call Trace:
Jul 29 15:11:21 hszpak kernel: gm200_acr_hsfw_boot+0xc3/0x160 [nouveau]
Jul 29 15:11:21 hszpak kernel: ? mutex_lock+0xe/0x30
Jul 29 15:11:21 hszpak kernel: nvkm_acr_hsf_boot+0x85/0xe0 [nouveau]
Jul 29 15:11:21 hszpak kernel: tu102_acr_init+0x15/0x30 [nouveau]
Jul 29 15:11:21 hszpak kernel: nvkm_acr_load+0x2b/0xd0 [nouveau]
Jul 29 15:11:21 hszpak kernel: ? ktime_get+0x38/0x90
Jul 29 15:11:21 hszpak kernel: nvkm_subdev_init+0x92/0xd0 [nouveau]
Jul 29 15:11:21 hszpak kernel: ? ktime_get+0x38/0x90
Jul 29 15:11:21 hszpak kernel: nvkm_device_init+0x10b/0x190 [nouveau]
Jul 29 15:11:21 hszpak kernel: nvkm_udevice_init+0x41/0x60 [nouveau]
Jul 29 15:11:21 hszpak kernel: nvkm_object_init+0x3e/0x100 [nouveau]
Jul 29 15:11:21 hszpak kernel: nvkm_object_init+0x6f/0x100 [nouveau]
Jul 29 15:11:21 hszpak kernel: nvkm_object_init+0x6f/0x100 [nouveau]
Jul 29 15:11:21 hszpak kernel: nouveau_do_resume+0x2a/0xc0 [nouveau]
Jul 29 15:11:21 hszpak kernel: nouveau_pmops_runtime_resume+0x7a/0x170 [nouveau]
Jul 29 15:11:21 hszpak kernel: pci_pm_runtime_resume+0xaa/0xc0
Jul 29 15:11:21 hszpak kernel: ? pci_pm_freeze_noirq+0x110/0x110
Jul 29 15:11:21 hszpak kernel: __rpm_callback+0x81/0x140
Jul 29 15:11:21 hszpak kernel: ? pci_pm_freeze_noirq+0x110/0x110
Jul 29 15:11:21 hszpak kernel: rpm_callback+0x1f/0x70
Jul 29 15:11:21 hszpak kernel: ? pci_pm_freeze_noirq+0x110/0x110
Jul 29 15:11:21 hszpak kernel: rpm_resume+0x575/0x7c0
Jul 29 15:11:21 hszpak kernel: ? __mod_lruvec_state+0x44/0xf0
Jul 29 15:11:21 hszpak kernel: __pm_runtime_resume+0x4a/0x80
Jul 29 15:11:21 hszpak kernel: nouveau_drm_open+0x3b/0x1a0 [nouveau]
Jul 29 15:11:21 hszpak kernel: ? security_capable+0x36/0x50
Jul 29 15:11:21 hszpak kernel: drm_file_alloc+0x194/0x250 [drm]
Jul 29 15:11:21 hszpak kernel: drm_open+0xce/0x250 [drm]
Jul 29 15:11:21 hszpak kernel: drm_stub_open+0xad/0x140 [drm]
Jul 29 15:11:21 hszpak kernel: chrdev_open+0xdd/0x210
Jul 29 15:11:21 hszpak kernel: ? cdev_device_add+0xc0/0xc0
Jul 29 15:11:21 hszpak kernel: do_dentry_open+0x13a/0x380
Jul 29 15:11:21 hszpak kernel: path_openat+0xa9a/0xfe0
Jul 29 15:11:21 hszpak kernel: ? current_time+0x1b/0xd0
Jul 29 15:11:21 hszpak kernel: ? atime_needs_update+0x73/0xd0
Jul 29 15:11:21 hszpak kernel: do_filp_open+0x75/0x100
Jul 29 15:11:21 hszpak kernel: ? __check_object_size+0x12e/0x13c
Jul 29 15:11:21 hszpak kernel: ? __alloc_fd+0x44/0x150
Jul 29 15:11:21 hszpak kernel: do_sys_openat2+0x8a/0x130
Jul 29 15:11:21 hszpak kernel: __x64_sys_openat+0x46/0x70
Jul 29 15:11:21 hszpak kernel: do_syscall_64+0x5b/0xf0
Jul 29 15:11:21 hszpak kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jul 29 15:11:21 hszpak kernel: RIP: 0033:0x7ff013de414b
Jul 29 15:11:21 hszpak kernel: Code: 25 00 00 41 00 3d 00 00 41 00 74 4b 64 8b 04 25 18 00 00 00 85 c0 75 67 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 91 00 00 00 48 8b 4c 24 28 64 48 33 0c 25
Jul 29 15:11:21 hszpak kernel: RSP: 002b:00007ffd4536a520 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
Jul 29 15:11:21 hszpak kernel: RAX: ffffffffffffffda RBX: 00007ff013b2ce80 RCX: 00007ff013de414b
Jul 29 15:11:21 hszpak kernel: RDX: 0000000000000002 RSI: 000055b4f79e54c0 RDI: 00000000ffffff9c
Jul 29 15:11:21 hszpak kernel: RBP: 000055b4f79e54c0 R08: 000055b4f79e5400 R09: 00007ff013efc380
Jul 29 15:11:21 hszpak kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
Jul 29 15:11:21 hszpak kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Jul 29 15:11:21 hszpak kernel: ---[ end trace 71e1c4626a3ab07b ]---
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: acr: AHESASC binary failed
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: acr: init failed, -110
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: init failed with -110
Jul 29 15:11:21 hszpak kernel: nouveau: systemd-udevd[445]:00000000:00000080: init failed with -110
Jul 29 15:11:21 hszpak kernel: nouveau: DRM-master:00000000:00000000: init failed with -110
Jul 29 15:11:21 hszpak kernel: nouveau: DRM-master:00000000:00000000: init failed with -110
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: DRM: Client resume failed with error: -110
Jul 29 15:11:21 hszpak kernel: nouveau 0000:01:00.0: DRM: resume failed with: -110
↑ new in 5.7.6 ↑
```
As it was introduced between the minor kernel version, number of commits is smaller than between the major ones. Maybe someone with bigger nouveau/drm experience could suggest what could be the culprit to consult it with the commit author?
https://lwn.net/Articles/824499/
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.7.6
Btw, there was a similar in effects [regression in 5.3](https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/516#note_388553), but it was fixed in 5.5.0-rc2+.https://gitlab.freedesktop.org/xorg/driver/xf86-video-tseng/-/issues/2Broken struct2022-01-30T20:12:53ZRobert BrownBroken struct@see this commit - https://gitlab.freedesktop.org/xorg/xserver/-/commit/5a945f54e738f6e9c5a489febdd8b87cd8a41210
It remmoved maxHValue and maxVValue from struct _ScrnInfoRec in the xf86str.h include file. The primary driver file in this...@see this commit - https://gitlab.freedesktop.org/xorg/xserver/-/commit/5a945f54e738f6e9c5a489febdd8b87cd8a41210
It remmoved maxHValue and maxVValue from struct _ScrnInfoRec in the xf86str.h include file. The primary driver file in this repo, tseng_drivers.c, still references those values and fails to compile.
I created a simple patch to remove those values and instead use the already-set versions of them. That allows it to build.
[tseng.patch](/uploads/b62b698e2ab0d18af7b181f8f384feb8/tseng.patch)
I'm relatively clueless as to how this bit of code works or the implications but I'll test and report back. I intentionally did not submit a merge, a code review here would be needed given my rusty dev skills.https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/115Circular dependency observed2020-07-20T14:38:06ZBalaraman BCircular dependency observedHi Team,
* My target switch OS is, /home/user # uname -a Linux MARVELL_LINUX 3.10.70 #1 SMP Fri Jun 19 07:41:25 IST 2020 armv7l GNU/Linux
* I'm trying to cross compile tcl/tk libraries dependent for python2.7.12 and observed below ...Hi Team,
* My target switch OS is, /home/user # uname -a Linux MARVELL_LINUX 3.10.70 #1 SMP Fri Jun 19 07:41:25 IST 2020 armv7l GNU/Linux
* I'm trying to cross compile tcl/tk libraries dependent for python2.7.12 and observed below error.
/home/balaram/MOXA/le/armv7_latest/bin/../lib/gcc/arm-marvell-linux-gnueabi/4.6.4/../../../../arm-marvell-linux-gnueabi/bin/ld: cannot find -lX11
* Since it showed libX11 is a dependent library, downloaded libX11 source code and tried to cross compile.
./configure --build=x86_64-linux-gnu --host=arm-none-linux-gnueabi CC=arm-marvell-linux-gnueabi-gcc CXX=arm-marvell-linux-gnueabi-g++ AR=arm-marvell-linux-gnueabi-ar LD=arm-marvell-linux-gnueabi-ld CPP=arm-marvell-linux-gnueabi-cpp --disable-loadable-xc --disable-xthreads --disable-xcms --disable-xlocale --enable-xlocaledir --disable-xf86bigfont --disable-xkb --disable-
composecache --enable-malloc0returnsnull --prefix=/home/balaram/MOXA/libx11
```
root@sfsubuntu11:/home/balaram/MOXA/tk8.6.10/unix# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/projects/Marvell_Latest_Toolchain/aarch64v8-marvell-linux-gnu-5.2.1_x86_64_20160301/bin:/home/balaram/MOXA/le/armv7_latest/bin
```
* During make, observed below error, /home/balaram/MOXA/le/armv7_latest/bin/../lib/gcc/arm-marvell-linux-gnueabi/4.6.4/../../../../arm-marvell-linux-gnueabi/bin/ld: cannot find -lxcb
* Then downloaded libxcb-1.14.tar.gz and during compilation faced similar error, /home/balaram/MOXA/le/armv7_latest/bin/../lib/gcc/arm-marvell-linux-gnueabi/4.6.4/../../../../arm-marvell-linux-gnueabi/bin/ld: cannot find -lXau
* For xauth-master.tar.gz, below error observed:
```
configure: error: Package requirements (x11 xau xext xmuu xproto >= 7.0.17) were not met:
No package 'xmuu' found
```
* For libXmu,
```
make[2]: Entering directory '/home/balaram/MOXA/libXmu-master/src'
CCLD libXmu.la
/home/balaram/MOXA/le/armv7_latest/bin/../lib/gcc/arm-marvell-linux-gnueabi/4.6.4/../../../../arm-marvell-linux-
gnueabi/bin/ld: cannot find -lXt
/home/balaram/MOXA/le/armv7_latest/bin/../lib/gcc/arm-marvell-linux-gnueabi/4.6.4/../../../../arm-marvell-linux-
gnueabi/bin/ld: cannot find -lXext
/home/balaram/MOXA/le/armv7_latest/bin/../lib/gcc/arm-marvell-linux-gnueabi/4.6.4/../../../../arm-marvell-linux-
gnueabi/bin/ld: cannot find -lX11
collect2: ld returned 1 exit status
Makefile:509: recipe for target 'libXmu.la' failed
```
Now, X11 library is needed, but we are compiling these as dependent for libX11.
* Tried to compile libXext as well, same issue faced.
```
make\[2\]: Entering directory '/home/balaram/MOXA/libXext-master/src' CCLD libXext.la /home/balaram/MOXA/le/armv7_latest/bin/../lib/gcc/arm-marvell-linux-gnueabi/4.6.4/../../../../arm-marvell-linux- gnueabi/bin/ld: cannot find -lX11 collect2: ld returned 1 exit status Makefile:486: recipe for target 'libXext.la' failed
```
Now we are in circular depdendency.
libx11 -> libxcb -> libXauth -> libXmu -> libXext ->
|__________________________________________________|
Requesting you people to help us in resolving the issue.
Thanks & Regard,
Balaramhttps://gitlab.freedesktop.org/xorg/app/xinput/-/issues/12Feature request: xinput test for all devices by one command2022-01-16T21:22:11ZJarno SuniFeature request: xinput test for all devices by one command`xinput test`
gives error
```
usage: xinput test [-proximity] <device name>
```
If it would work, the output would be more suitable for some purposes than the output of
`xinput test-xi2 --root`
that has a limitation that only one com...`xinput test`
gives error
```
usage: xinput test [-proximity] <device name>
```
If it would work, the output would be more suitable for some purposes than the output of
`xinput test-xi2 --root`
that has a limitation that only one command can be run at a time in a session.https://gitlab.freedesktop.org/xorg/app/xinput/-/issues/11Feature request: disable/enable all pointer devices by one command2022-01-16T21:24:32ZJarno SuniFeature request: disable/enable all pointer devices by one commandhttps://gitlab.freedesktop.org/xorg/app/xauth/-/issues/4Circular dependency observed2020-07-20T14:38:06ZBalaraman BCircular dependency observedHi Team,
- My target switch OS is,
/home/user # uname -a
Linux MARVELL_LINUX 3.10.70 #1 SMP Fri Jun 19 07:41:25 IST 2020 armv7l GNU/Linux
- I'm trying to cross compile tcl/tk libraries dependent for python2.7.12 and observed below erro...Hi Team,
- My target switch OS is,
/home/user # uname -a
Linux MARVELL_LINUX 3.10.70 #1 SMP Fri Jun 19 07:41:25 IST 2020 armv7l GNU/Linux
- I'm trying to cross compile tcl/tk libraries dependent for python2.7.12 and observed below error.
/home/balaram/MOXA/le/armv7_latest/bin/../lib/gcc/arm-marvell-linux-gnueabi/4.6.4/../../../../arm-marvell-linux-gnueabi/bin/ld: cannot find -lX11
- Since it showed libX11 is a dependent library, downloaded libX11 source code and tried to cross compile.
./configure --build=x86_64-linux-gnu --host=arm-none-linux-gnueabi CC=arm-marvell-linux-gnueabi-gcc CXX=arm-marvell-linux-gnueabi-g++ AR=arm-marvell-linux-gnueabi-ar LD=arm-marvell-linux-gnueabi-ld CPP=arm-marvell-linux-gnueabi-cpp --disable-loadable-xc --disable-xthreads --disable-xcms --disable-xlocale --enable-xlocaledir --disable-xf86bigfont --disable-xkb --disable-composecache --enable-malloc0returnsnull --prefix=/home/balaram/MOXA/libx11
root@sfsubuntu11:/home/balaram/MOXA/tk8.6.10/unix# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/projects/Marvell_Latest_Toolchain/aarch64v8-marvell-linux-gnu-5.2.1_x86_64_20160301/bin:/home/balaram/MOXA/le/armv7_latest/bin
- During make, observed below error,
/home/balaram/MOXA/le/armv7_latest/bin/../lib/gcc/arm-marvell-linux-gnueabi/4.6.4/../../../../arm-marvell-linux-gnueabi/bin/ld: cannot find -lxcb
- Then downloaded libxcb-1.14.tar.gz and during compilation faced similar error,
/home/balaram/MOXA/le/armv7_latest/bin/../lib/gcc/arm-marvell-linux-gnueabi/4.6.4/../../../../arm-marvell-linux-gnueabi/bin/ld: cannot find -lXau
- For xauth-master.tar.gz, below error observed:
configure: error: Package requirements (x11 xau xext xmuu xproto >= 7.0.17) were not met:
No package 'xmuu' found
- For libXmu,
make[2]: Entering directory '/home/balaram/MOXA/libXmu-master/src'
CCLD libXmu.la
/home/balaram/MOXA/le/armv7_latest/bin/../lib/gcc/arm-marvell-linux-gnueabi/4.6.4/../../../../arm-marvell-linux-
gnueabi/bin/ld: cannot find -lXt
/home/balaram/MOXA/le/armv7_latest/bin/../lib/gcc/arm-marvell-linux-gnueabi/4.6.4/../../../../arm-marvell-linux-
gnueabi/bin/ld: cannot find -lXext
/home/balaram/MOXA/le/armv7_latest/bin/../lib/gcc/arm-marvell-linux-gnueabi/4.6.4/../../../../arm-marvell-linux-
gnueabi/bin/ld: cannot find -lX11
collect2: ld returned 1 exit status
Makefile:509: recipe for target 'libXmu.la' failed
Now, X11 library is needed, but we are compiling these as dependent for libX11.
- Tried to compile libXext as well, same issue faced.
make[2]: Entering directory '/home/balaram/MOXA/libXext-master/src'
CCLD libXext.la
/home/balaram/MOXA/le/armv7_latest/bin/../lib/gcc/arm-marvell-linux-gnueabi/4.6.4/../../../../arm-marvell-linux-
gnueabi/bin/ld: cannot find -lX11
collect2: ld returned 1 exit status
Makefile:486: recipe for target 'libXext.la' failed
Now we are in circular depdendency.
libx11 -> libxcb -> libXauth -> libXmu -> libXext ->
|__________________________________________________|
Requesting you people to help us in resolving the issue.
Thanks & Regard,
Balaramhttps://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/16WARNING at dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high()2020-07-01T16:03:42ZBugzilla Migration UserWARNING at dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high()## Submitted by Rafał Miłecki
Assigned to **Default DRI bug account**
**[Link to original bug (#109628)](https://bugs.freedesktop.org/show_bug.cgi?id=109628)**
## Description
I use HP EliteBook 745 G5 with Ryzen 5 PRO 2500U and ex...## Submitted by Rafał Miłecki
Assigned to **Default DRI bug account**
**[Link to original bug (#109628)](https://bugs.freedesktop.org/show_bug.cgi?id=109628)**
## Description
I use HP EliteBook 745 G5 with Ryzen 5 PRO 2500U and external monitor BenQ GW2260.<br>
<br>
Today after taking ~10 minutes break amdgpu had some problems with enabling my external monitor back (after putting it in sleep mode or something). It took it about half a minute I think.<br>
<br>
I checked dmesg immediately and found there a WARNING:<br>
[65984.999696] WARNING: CPU: 6 PID: 2081 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high+0x25/0x260 [amdgpu]<br>
<br>
I suspect it may be related to the issue I'm reporting.<br>
<br>
So far I was using kernels 4.19 and 4.20 (for the last 2 months) and never saw it. A day ago I've switched to the kernel 5.0.0-rc6. It may be either:<br>
1. A regression<br>
2. A very rare bughttps://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/15__gnu_cxx::recursive_init_error exception thrown by LLVM upon initialisation ...2020-06-29T14:28:48Zdatenwolf__gnu_cxx::recursive_init_error exception thrown by LLVM upon initialisation of OpenGL texture object= System information:
- GLX_MESA_query_renderer
* Device: AMD RAVEN (DRM 3.35.0, 5.4.48_1, LLVM 10.0.0) (0x15d8)
* Version: 20.1.1
- xf86-video-amdgpu-19.1.0
- Linux-5.4.48
= Problem description
Upon initialisation of an OpenGL ...= System information:
- GLX_MESA_query_renderer
* Device: AMD RAVEN (DRM 3.35.0, 5.4.48_1, LLVM 10.0.0) (0x15d8)
* Version: 20.1.1
- xf86-video-amdgpu-19.1.0
- Linux-5.4.48
= Problem description
Upon initialisation of an OpenGL texture (call to `glTexImage2D`) a `__gnu_cxx::recursive_init_error` exception is thrown from LLVM code that is called from `radeonsi_dri.so`
This issue might as well be an LLVM bug, however so far it only manifests in OpenGL programs on my system. As far as I can tell there is a race condition involved, since the exception is thrown on about 3 of 10 program launches, however the heavier the system is loaded, the more likely it is to appear.
= Relevant backtraces (backtraces of all threads attached as file)
Main thread:
```
Thread 1 (Thread 0x7ffff73fa740 (LWP 15213)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x00007ffff5bc4bf4 in ?? () from /usr/lib/xorg/modules/drivers/radeonsi_dri.so
>> #2 … #15 0x… in ?? () from /usr/lib/xorg/modules/drivers/radeonsi_dri.so
#16 0x00007ffff59ccb0e in ?? () from /usr/lib/xorg/modules/drivers/radeonsi_dri.so
#17 0x00000000004288c2 in ImGui_ImplOpenGL2_CreateFontsTexture () at ../3rd/imgui/examples/imgui_impl_opengl2.cpp:218
#18 0x000000000042895c in ImGui_ImplOpenGL2_CreateDeviceObjects () at ../3rd/imgui/examples/imgui_impl_opengl2.cpp:242
#19 0x00000000004281cd in ImGui_ImplOpenGL2_NewFrame () at ../3rd/imgui/examples/imgui_impl_opengl2.cpp:75
#20 0x000000000040265e in display () at ../src/alpha.cc:11
#21 0x00007ffff7ede57d in fghRedrawWindow () from /usr/lib/libglut.so.3
#22 0x00007ffff7edea42 in ?? () from /usr/lib/libglut.so.3
#23 0x00007ffff7edfa79 in fgEnumWindows () from /usr/lib/libglut.so.3
#24 0x00007ffff7edeb0d in glutMainLoopEvent () from /usr/lib/libglut.so.3
#25 0x00007ffff7edeba6 in glutMainLoop () from /usr/lib/libglut.so.3
#26 0x0000000000402817 in main (argc=1, argv=0x7fffffffd778) at ../src/alpha.cc:64
```
`../3rd/imgui/examples/imgui_impl_opengl2.cpp:218` is a call to `glTexImage2D`.
Crashing thread:
```
Thread 8 (Thread 0x7fffd7fff700 (LWP 15227)):
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x00007ffff794455b in __GI_abort () at abort.c:79
#2 0x00007ffff7ce26ce in ?? () from /usr/lib/libstdc++.so.6
#3 0x00007ffff7d115a6 in ?? () from /usr/lib/libstdc++.so.6
#4 0x00007ffff7d11611 in std::terminate() () from /usr/lib/libstdc++.so.6
#5 0x00007ffff7d11864 in __cxa_throw () from /usr/lib/libstdc++.so.6
#6 0x00007ffff7ce2340 in ?? () from /usr/lib/libstdc++.so.6
#7 0x00007ffff0d45f58 in std::enable_if<llvm::hashing::detail::is_hashable_data<unsigned int const>::value, llvm::hash_code>::type llvm::hashing::detail::hash_combine_range_impl<unsigned int const>(unsigned int const*, unsigned int const*) () from /usr/lib/libLLVM-10.so
#8 0x00007ffff0d46217 in llvm::FoldingSetNodeIDRef::ComputeHash() const () from /usr/lib/libLLVM-10.so
#9 0x00007ffff0d4624b in llvm::FoldingSetNodeID::ComputeHash() const () from /usr/lib/libLLVM-10.so
#10 0x00007ffff0d462aa in llvm::FoldingSetBase::FindNodeOrInsertPos(llvm::FoldingSetNodeID const&, void*&) () from /usr/lib/libLLVM-10.so
#11 0x00007ffff0f18c58 in llvm::PMTopLevelManager::findAnalysisUsage(llvm::Pass*) () from /usr/lib/libLLVM-10.so
#12 0x00007ffff0f1ef33 in llvm::PMTopLevelManager::schedulePass(llvm::Pass*) () from /usr/lib/libLLVM-10.so
#13 0x00007ffff60acb0f in ?? () from /usr/lib/xorg/modules/drivers/radeonsi_dri.so
#14 0x00007ffff5fee071 in ?? () from /usr/lib/xorg/modules/drivers/radeonsi_dri.so
#15 0x00007ffff601cdfb in ?? () from /usr/lib/xorg/modules/drivers/radeonsi_dri.so
#16 0x00007ffff5bc50e5 in ?? () from /usr/lib/xorg/modules/drivers/radeonsi_dri.so
#17 0x00007ffff5bc4c47 in ?? () from /usr/lib/xorg/modules/drivers/radeonsi_dri.so
#18 0x00007ffff6e9ef27 in start_thread (arg=<optimized out>) at pthread_create.c:479
#19 0x00007ffff7a1be0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
```
Full backtrace:
[gdb.txt](/uploads/26369161e730f60aa8f29de7055e7dc6/gdb.txt)https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/14Warning in kernel messages at write_i2c_retimer_setting() in dc_link.c2020-06-25T14:58:15ZAndrea D'AmoreWarning in kernel messages at write_i2c_retimer_setting() in dc_link.cI am seeing a warning message from amdgpu driver in dmesg output, along with a backtrace.
The message repeatedly appears in kernel messages, roughly after an interval of time in the `[600, 1200] s` span.
The system is fully functional, ...I am seeing a warning message from amdgpu driver in dmesg output, along with a backtrace.
The message repeatedly appears in kernel messages, roughly after an interval of time in the `[600, 1200] s` span.
The system is fully functional, as expected since the message is a warning, but I wonder what is the reason of the warning and if there is something that should changed or update for it to not be triggered.
My motherboard is an ASRock A300M-STX equipped with an AMD Ryzen 3200G APU, the graphic chipset is Vega 8.
Here is the relevant excerpt from dmesg output:
```
[ 4.333681] ------------[ cut here ]------------
[ 4.333733] WARNING: CPU: 3 PID: 511 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:1737 write_i2c_retimer_setting+0xc5/0x3e0 [amdgpu]
[ 4.333734] Modules linked in: uas usb_storage btrfs xor amdgpu amd_iommu_v2 gpu_sched raid6_pq hwmon libcrc32c i2c_algo_bit crc32c_generic ttm drm_kms_helper crct10dif_pclmul ahci libahci syscopyarea
crc32_pclmul crc32c_intel sysfillrect sysimgblt ghash_clmulni_intel aesni_intel fb_sys_fops crypto_simd libata drm cryptd glue_helper r8169 xhci_pci agpgart realtek xhci_hcd scsi_mod usbcore wmi video button dm_mirror dm_region_hash dm_log dm_mod
[ 4.333754] CPU: 3 PID: 511 Comm: kworker/3:3 Not tainted 5.4.48_1 #1
[ 4.333755] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./A300M-STX, BIOS P3.50 05/15/2019
[ 4.333760] Workqueue: events fbcon_register_existing_fbs
[ 4.333795] RIP: 0010:write_i2c_retimer_setting+0xc5/0x3e0 [amdgpu]
[ 4.333797] Code: b6 4c 24 16 44 89 e2 44 0f b6 44 24 17 44 0f b6 c8 48 c7 c6 f8 5f ab c0 bf 04 00 00 00 45 89 cd e8 80 2d c1 ff 45 84 ed 75 02 <0f> 0b 0f b6 44 5d 02 8d 50 f6 80 fa 02 77 88 3c 0a 0f 85 c5 00 00
[ 4.333798] RSP: 0018:ffffc1ad40b5f708 EFLAGS: 00010246
[ 4.333798] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000000000000a
[ 4.333799] RDX: 000000000000005d RSI: ffffffffc0ab5ff8 RDI: 0000000000000004
[ 4.333800] RBP: ffffc1ad40b5f77c R08: 0000000000000013 R09: 0000000000000000
[ 4.333800] R10: ffff9d5340bfc340 R11: 0000000000000001 R12: 000000000000005d
[ 4.333801] R13: 0000000000000000 R14: ffff9d5346cb01b8 R15: ffffc1ad40b5f71e
[ 4.333802] FS: 0000000000000000(0000) GS:ffff9d53504c0000(0000) knlGS:0000000000000000
[ 4.333803] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 4.333803] CR2: 00007ffd20bc5b28 CR3: 0000000384bf0000 CR4: 00000000003406e0
[ 4.333804] Call Trace:
[ 4.333843] core_link_enable_stream+0x865/0x8b0 [amdgpu]
[ 4.333876] ? generic_reg_update_ex+0x9c/0x130 [amdgpu]
[ 4.333911] ? dce110_apply_ctx_to_hw+0x55a/0x5a0 [amdgpu]
[ 4.333945] dce110_apply_ctx_to_hw+0x55a/0x5a0 [amdgpu]
[ 4.333980] dc_commit_state+0x26b/0x5a0 [amdgpu]
[ 4.334024] amdgpu_dm_atomic_commit_tail+0xd47/0x1dc0 [amdgpu]
[ 4.334029] ? deactivate_slab.isra.0+0x5bb/0x650
[ 4.334071] ? dcn_validate_bandwidth+0x1afe/0x1f00 [amdgpu]
[ 4.334073] ? init_object+0x6b/0x80
[ 4.334074] ? ___slab_alloc+0x56c/0x5e0
[ 4.334116] ? dm_plane_atomic_check+0x90/0x90 [amdgpu]
[ 4.334158] ? dm_plane_helper_prepare_fb+0x245/0x2c0 [amdgpu]
[ 4.334163] ? commit_tail+0x94/0x110 [drm_kms_helper]
[ 4.334166] commit_tail+0x94/0x110 [drm_kms_helper]
[ 4.334171] drm_atomic_helper_commit+0xb8/0x130 [drm_kms_helper]
[ 4.334178] drm_client_modeset_commit_atomic+0x179/0x1e0 [drm]
[ 4.334187] drm_client_modeset_commit_force+0x50/0x150 [drm]
[ 4.334190] drm_fb_helper_restore_fbdev_mode_unlocked+0x49/0xa0 [drm_kms_helper]
[ 4.334194] drm_fb_helper_set_par+0x2c/0x50 [drm_kms_helper]
[ 4.334196] fbcon_init+0x2a9/0x5e0
[ 4.334199] visual_init+0xce/0x130
[ 4.334201] do_bind_con_driver+0x1b9/0x2a0
[ 4.334203] do_take_over_console+0x115/0x180
[ 4.334204] do_fbcon_takeover+0x58/0xb0
[ 4.334206] fbcon_register_existing_fbs+0x1f/0x40
[ 4.334210] process_one_work+0x198/0x3c0
[ 4.334212] worker_thread+0x50/0x3a0
[ 4.334214] kthread+0xfb/0x130
[ 4.334216] ? process_one_work+0x3c0/0x3c0
[ 4.334217] ? kthread_park+0x90/0x90
[ 4.334220] ret_from_fork+0x22/0x40
[ 4.334223] ---[ end trace aacd787d303271ac ]---
[ 4.334431] ------------[ cut here ]------------
```https://gitlab.freedesktop.org/xorg/proto/xcbproto/-/issues/16Not all fields of errors are present2021-09-30T17:16:31ZUli SchlachterNot all fields of errors are presentIn xproto, all errors have `bad_value`, `minor_opcode` and `major_opcode` fields:
https://gitlab.freedesktop.org/xorg/proto/xcbproto/-/blob/7d58eed95f796fc764741d7549ee2214bbbcc64c/src/xproto.xml#L1109-1114
However, some extensions do n...In xproto, all errors have `bad_value`, `minor_opcode` and `major_opcode` fields:
https://gitlab.freedesktop.org/xorg/proto/xcbproto/-/blob/7d58eed95f796fc764741d7549ee2214bbbcc64c/src/xproto.xml#L1109-1114
However, some extensions do not, e.g.:
https://gitlab.freedesktop.org/xorg/proto/xcbproto/-/blob/7d58eed95f796fc764741d7549ee2214bbbcc64c/src/randr.xml#L44-47
I just followed the code in the X11 server and it seems like all errors always have these fields. Thus, the XML should be fixed accordingly. This is the relevant function that always adds these fields:
https://gitlab.freedesktop.org/xorg/xserver/-/blob/d6558477d7a264c2132bc977b51d80fc0277d1e0/dix/dispatch.c#L3740-3753
(This was originally found in https://github.com/psychon/x11rb/issues/503)https://gitlab.freedesktop.org/xorg/xserver/-/issues/1044/usr/lib/xorg/Xorg Segmentation fault at address 0x02021-06-23T11:33:20ZHNC/usr/lib/xorg/Xorg Segmentation fault at address 0x0I tried to install virtualGl and Turbovnc on my remote server A, to utilize the server's gpu to run glx application.Same approach work on another server B, but when I started **Xorg**, reported Segmentation fault at address 0x0.
Log fro...I tried to install virtualGl and Turbovnc on my remote server A, to utilize the server's gpu to run glx application.Same approach work on another server B, but when I started **Xorg**, reported Segmentation fault at address 0x0.
Log from /usr/lib/xorg/Xorg -verbose
```shell
[108004.504]
X.Org X Server 1.18.4
Release Date: 2016-07-19
[108004.504] X Protocol Version 11, Revision 0
[108004.504] Build Operating System: Linux 4.4.0-128-generic x86_64 Ubuntu
[108004.504] Current Operating System: Linux admin.cluster.local 4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019 x86_64
[108004.504] Kernel command line: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=UUID=33632c75-dcb4-4c37-a649-e9b72712476c ro quiet splash vt.handoff=7
[108004.504] Build Date: 10 August 2018 09:33:05AM
[108004.505] xorg-server 2:1.18.4-0ubuntu0.8 (For technical support please see http://www.ubuntu.com/support)
[108004.505] Current version of pixman: 0.33.6
[108004.505] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[108004.505] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[108004.505] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jun 21 16:50:11 2020
[108004.505] (==) Using config file: "/etc/X11/xorg.conf"
[108004.505] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[108004.505] (==) ServerLayout "Default Layout"
[108004.505] (**) |-->Screen "Default Screen" (0)
[108004.505] (**) | |-->Monitor "Configured Monitor"
[108004.505] (**) | |-->Device "Configured Video Device"
[108004.505] (**) |-->Input Device "Keyboard0"
[108004.505] (**) |-->Input Device "Mouse0"
[108004.505] (==) Automatically adding devices
[108004.505] (==) Automatically enabling devices
[108004.505] (==) Automatically adding GPU devices
[108004.506] (==) Max clients allowed: 256, resource mask: 0x1fffff
[108004.506] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/cyrillic,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[108004.506] (==) ModulePath set to "/usr/lib/x86_64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[108004.506] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[108004.506] (WW) Disabling Keyboard0
[108004.506] (WW) Disabling Mouse0
[108004.506] (II) Loader magic: 0x559170f9edc0
[108004.506] (II) Module ABI versions:
[108004.506] X.Org ANSI C Emulation: 0.4
[108004.506] X.Org Video Driver: 20.0
[108004.506] X.Org XInput driver : 22.1
[108004.506] X.Org Server Extension : 9.0
[108004.507] (--) using VT number 5
[108004.507] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[108004.509] (II) xfree86: Adding drm device (/dev/dri/card0)
[108004.509] (II) xfree86: Adding drm device (/dev/dri/card1)
[108004.509] (II) xfree86: Adding drm device (/dev/dri/card2)
[108004.510] (II) xfree86: Adding drm device (/dev/dri/card3)
[108004.510] (II) xfree86: Adding drm device (/dev/dri/card4)
[108004.510] (II) xfree86: Adding drm device (/dev/dri/card5)
[108004.510] (II) xfree86: Adding drm device (/dev/dri/card6)
[108004.510] (II) xfree86: Adding drm device (/dev/dri/card7)
[108004.510] (II) xfree86: Adding drm device (/dev/dri/card8)
[108004.521] (--) PCI:*(0:3:0:0) 1a03:2000:1a03:2000 rev 65, Mem @ 0x9c000000/16777216, 0x9d000000/131072, I/O @ 0x00002000/128, BIOS @ 0x????????/131072
[108004.521] (--) PCI: (0:26:0:0) 10de:1e04:1462:3712 rev 161, Mem @ 0xa9000000/16777216, 0x39ffe0000000/268435456, 0x39fff0000000/33554432, I/O @ 0x00005000/128, BIOS @ 0x????????/524288
[108004.521] (--) PCI: (0:27:0:0) 10de:1e04:1462:3712 rev 161, Mem @ 0xa7000000/16777216, 0x39ffc0000000/268435456, 0x39ffd0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
[108004.521] (--) PCI: (0:61:0:0) 10de:1e04:1462:3712 rev 161, Mem @ 0xb7000000/16777216, 0x3affe0000000/268435456, 0x3afff0000000/33554432, I/O @ 0x00007000/128, BIOS @ 0x????????/524288
[108004.521] (--) PCI: (0:62:0:0) 10de:1e04:1462:3712 rev 161, Mem @ 0xb5000000/16777216, 0x3affc0000000/268435456, 0x3affd0000000/33554432, I/O @ 0x00006000/128, BIOS @ 0x????????/524288
[108004.521] (--) PCI: (0:136:0:0) 10de:1e04:1462:3712 rev 161, Mem @ 0xdf000000/16777216, 0x3dffe0000000/268435456, 0x3dfff0000000/33554432, I/O @ 0x0000c000/128, BIOS @ 0x????????/524288
[108004.521] (--) PCI: (0:137:0:0) 10de:1e04:1462:3712 rev 161, Mem @ 0xdd000000/16777216, 0x3dffc0000000/268435456, 0x3dffd0000000/33554432, I/O @ 0x0000b000/128, BIOS @ 0x????????/524288
[108004.521] (--) PCI: (0:177:0:0) 10de:1e04:1462:3712 rev 161, Mem @ 0xed000000/16777216, 0x3effe0000000/268435456, 0x3efff0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[108004.521] (--) PCI: (0:178:0:0) 10de:1e04:1462:3712 rev 161, Mem @ 0xeb000000/16777216, 0x3effc0000000/268435456, 0x3effd0000000/33554432, I/O @ 0x0000d000/128, BIOS @ 0x????????/524288
[108004.521] (II) LoadModule: "glx"
[108004.522] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[108004.523] (II) Module glx: vendor="X.Org Foundation"
[108004.523] compiled for 1.18.4, module version = 1.0.0
[108004.523] ABI class: X.Org Server Extension, version 9.0
[108004.523] (==) AIGLX enabled
[108004.523] (II) LoadModule: "nvidia"
[108004.523] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[108004.523] (II) Module nvidia: vendor="NVIDIA Corporation"
[108004.523] compiled for 1.6.99.901, module version = 1.0.0
[108004.523] Module class: X.Org Video Driver
[108004.523] (II) NVIDIA dlloader X Driver 440.33.01 Tue Nov 12 23:50:12 UTC 2019
[108004.523] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[108004.533] (II) Loading sub module "fb"
[108004.533] (II) LoadModule: "fb"
[108004.533] (II) Loading /usr/lib/xorg/modules/libfb.so
[108004.534] (II) Module fb: vendor="X.Org Foundation"
[108004.534] compiled for 1.18.4, module version = 1.0.0
[108004.534] ABI class: X.Org ANSI C Emulation, version 0.4
[108004.534] (II) Loading sub module "wfb"
[108004.534] (II) LoadModule: "wfb"
[108004.534] (II) Loading /usr/lib/xorg/modules/libwfb.so
[108004.534] (II) Module wfb: vendor="X.Org Foundation"
[108004.534] compiled for 1.18.4, module version = 1.0.0
[108004.534] ABI class: X.Org ANSI C Emulation, version 0.4
[108004.534] (II) Loading sub module "ramdac"
[108004.534] (II) LoadModule: "ramdac"
[108004.534] (II) Module "ramdac" already built-in
[108004.534] (EE) No devices detected.
[108004.534] (II) Applying OutputClass "nvidia" to /dev/dri/card1
[108004.534] loading driver: nvidia
[108004.534] (II) Applying OutputClass "nvidia" to /dev/dri/card2
[108004.534] loading driver: nvidia
[108004.534] (II) Applying OutputClass "nvidia" to /dev/dri/card3
[108004.534] loading driver: nvidia
[108004.534] (II) Applying OutputClass "nvidia" to /dev/dri/card4
[108004.534] loading driver: nvidia
[108004.534] (II) Applying OutputClass "nvidia" to /dev/dri/card5
[108004.534] loading driver: nvidia
[108004.534] (II) Applying OutputClass "nvidia" to /dev/dri/card6
[108004.534] loading driver: nvidia
[108004.534] (II) Applying OutputClass "nvidia" to /dev/dri/card7
[108004.535] loading driver: nvidia
[108004.535] (==) Matched ast as autoconfigured driver 0
[108004.535] (==) Matched nvidia as autoconfigured driver 1
[108004.535] (==) Matched nvidia as autoconfigured driver 2
[108004.535] (==) Matched nouveau as autoconfigured driver 3
[108004.535] (==) Matched nvidia as autoconfigured driver 4
[108004.535] (==) Matched nvidia as autoconfigured driver 5
[108004.535] (==) Matched nouveau as autoconfigured driver 6
[108004.535] (==) Matched nvidia as autoconfigured driver 7
[108004.535] (==) Matched nvidia as autoconfigured driver 8
[108004.535] (==) Matched nouveau as autoconfigured driver 9
[108004.535] (==) Matched nvidia as autoconfigured driver 10
[108004.535] (==) Matched nvidia as autoconfigured driver 11
[108004.535] (==) Matched nouveau as autoconfigured driver 12
[108004.535] (==) Matched nvidia as autoconfigured driver 13
[108004.535] (==) Matched nvidia as autoconfigured driver 14
[108004.535] (==) Matched nouveau as autoconfigured driver 15
[108004.535] (==) Matched nvidia as autoconfigured driver 16
[108004.535] (==) Matched nvidia as autoconfigured driver 17
[108004.535] (==) Matched nouveau as autoconfigured driver 18
[108004.535] (==) Matched nvidia as autoconfigured driver 19
[108004.535] (==) Matched modesetting as autoconfigured driver 20
[108004.535] (EE)
[108004.535] (EE) Backtrace:
[108004.535] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x559170d126ce]
[108004.535] (EE) 1: /usr/lib/xorg/Xorg (0x559170b60000+0x1b6a69) [0x559170d16a69]
[108004.535] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f00d3fd6000+0x354b0) [0x7f00d400b4b0]
[108004.535] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (_IO_vfprintf+0x1b50) [0x7f00d4024cc0]
[108004.535] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (__vsnprintf_chk+0x96) [0x7f00d40ec896]
[108004.536] (EE) 5: /usr/lib/xorg/Xorg (Xvscnprintf+0x2e) [0x559170d1e91e]
[108004.536] (EE) 6: /usr/lib/xorg/Xorg (LogVMessageVerb+0x63) [0x559170d204d3]
[108004.536] (EE) 7: /usr/lib/xorg/Xorg (xf86Msg+0x9c) [0x559170c0051c]
[108004.536] (EE) 8: /usr/lib/xorg/Xorg (0x559170b60000+0xb5a94) [0x559170c15a94]
[108004.536] (EE) 9: /usr/lib/xorg/Xorg (InitOutput+0x9bd) [0x559170bf8aed]
[108004.536] (EE) 10: /usr/lib/xorg/Xorg (0x559170b60000+0x57c24) [0x559170bb7c24]
[108004.536] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f00d3ff6830]
[108004.536] (EE) 12: /usr/lib/xorg/Xorg (_start+0x29) [0x559170ba2069]
[108004.536] (EE)
[108004.536] (EE) Segmentation fault at address 0x0
[108004.536] (EE)
Fatal server error:
[108004.536] (EE) Caught signal 11 (Segmentation fault). Server aborting
[108004.536] (EE)
[108004.536] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[108004.536] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[108004.536] (EE)
```
Can you help me, plz.https://gitlab.freedesktop.org/xorg/lib/libxkbfile/-/issues/8in(marathi) segfaults xkbcomp2020-06-24T22:42:29ZPeter Huttererin(marathi) segfaults xkbcompcc @Niranjan
xkbcomp segfaults because of the name:
```
name[Group1]="मराठी इन्स्क्रिप्ट";
```
I don't know enough about sanskrit (?) to understand the symbols but bit of trial-and-error shows that just leaving the bits after ``...cc @Niranjan
xkbcomp segfaults because of the name:
```
name[Group1]="मराठी इन्स्क्रिप्ट";
```
I don't know enough about sanskrit (?) to understand the symbols but bit of trial-and-error shows that just leaving the bits after ``न्``part works, so the issue is in the first half of the name.
test case:
```
setxkbmap -layout in -variant marathi -print | xkbcomp -xkb - - > /dev/null
```
valgrind says:
```
==668064==
==668064== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==668064== Bad permissions for mapped region at address 0x49FD000
==668064== at 0x49EB1F0: XkbStringText (in /usr/lib64/libxkbfile.so.1.0.2)
==668064== by 0x49E56E0: XkbWriteXKBSymbols (in /usr/lib64/libxkbfile.so.1.0.2)
==668064== by 0x49E72A9: XkbWriteXKBKeymap (in /usr/lib64/libxkbfile.so.1.0.2)
==668064== by 0x10DF66: ??? (in /usr/bin/xkbcomp)
==668064== by 0x4A24041: (below main) (in /usr/lib64/libc-2.31.so)
```
So, the real bug is somewhere in xkbcomp or libX11 but I don't know yet where.