Bug#1067934: jameica: Jameica cannot load plugins | service "database" not found

2024-03-29 Thread Ferdinand Rau

The upstream author suggests that the issue may be related to the "H2 Database 
Engine" (Debian package: jameica-h2database) in a similar, but not identical case 
here:
https://homebanking-hilfe.de/forum/topic.php?p=170111#real170111

Upstream H2 is at version 2.2.224, whereas Debian is at 1.4.197-7, which is 
approx. six years old.

An update of jameica-h2database will likely fix this issue?



Bug#883935: linux-image-4.9.0-4-amd64: i915 GPU hang after every suspend or hibernate (Hang on render ring)

2017-12-27 Thread Ferdinand Rau
FYI, the bug is not resolved in the latest kernel package (update 12/23/2017):

> $ uname -a
> Linux N360-11 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23) x86_64 
> GNU/Linux

After hibernate/resume:
> $ dmesg | tail -n 9
> [ 1686.964009] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
> [ 1687.868696] [drm] GPU HANG: ecode 8:0:0x5fa3bf07, in Xorg [650], reason: 
> Hang on render ring, action: reset
> [ 1687.868704] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
> stack, including userspace.
> [ 1687.868708] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
> against DRI -> DRM/Intel
> [ 1687.868712] [drm] drm/i915 developers can then reassign to the right 
> component if it's not a kernel issue.
> [ 1687.868716] [drm] The gpu crash dump is required to analyze gpu hangs, so 
> please always attach it.
> [ 1687.868720] [drm] GPU crash dump saved to /sys/class/drm/card0/error
> [ 1687.868949] drm/i915: Resetting chip after gpu hang
> [ 1697.849509] drm/i915: Resetting chip after gpu hang



Bug#879857: xserver-xorg-video-intel: [i915] GPU hang after every suspend or hibernate on Debian 9 stretch

2017-12-10 Thread Ferdinand Rau
Dear Maintainer,

There are reports that this issue is resolved when using the same version of 
xserver-xorg-video-intel, but another kernel version. Therefore, I now assume 
that this issue is caused by a kernel bug, not a bug in your package.

I filed a new bug report against src:linux here:
https://bugs.debian.org/883935

I will post any updates or new information there. Feel free to close this bug 
any time.

Kind regards,
Ferdinand



Bug#879857: xserver-xorg-video-intel: [i915] GPU hang after every suspend or hibernate on Debian 9 stretch

2017-11-24 Thread Ferdinand Rau
This issue is not resolved.

Dear Maintainer:

Could you kindly confirm that this bug was reported correctly?

Could you please comment on the next steps? Even if it is not possible or not 
reasonable to work on this bug, I would love to know this.

Should I report another bug, e.g. against the kernel package or against the 
upstream xorg project?

Kind regards,
Ferdinand Rau



Bug#879857: xserver-xorg-video-intel: [i915] GPU hang after every suspend or hibernate on Debian 9 stretch

2017-10-26 Thread Ferdinand Rau
Package: xserver-xorg-video-intel
Version: 2:2.99.917+git20161206-1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

I am affected by this issue on a Wortmann/Terra Mobile N360-11 notebook 
computer with an Intel i915 graphics chipset.

Every time I use the suspend or hibernate sleep states, the system boots and 
resumes as expected (I can see the screen exactly the way before I pressed the 
hibernate button). After one or two seconds, however, the display manager is 
restarted and I am presented with a blac screen briefly, followed by the 
regular login screen. I use Xfce4 with lightdm, btw.
On the login screen, I can immediately log in as the same user that triggered 
the hibernation, and use the computer just fine.
After logging in, however, all applications are closed and all unsaved data is 
lost.
The consoles (TTY1, TTY2) are not affected.
The behaviour is reproducible every time I suspend or hibernate, also when 
hibernation is triggered automatically, e.g. by a low battery level.

After such a "failed" resume, I can find the following error message in the 
output of dmesg:
> [drm] GPU HANG: ecode 8:0:0x5fa3bf07, in Xorg [641], reason: Hang on render 
> ring, action: reset
> [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, 
> including userspace.
> [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> 
> DRM/Intel
> [drm] drm/i915 developers can then reassign to the right component if it's 
> not a kernel issue.
> [drm] The gpu crash dump is required to analyze gpu hangs, so please always 
> attach it.
> [drm] GPU crash dump saved to /sys/class/drm/card0/error
> drm/i915: Resetting chip after gpu hang
> drm/i915: Resetting chip after gpu hang

uname -a:
> Linux N360-11 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 
> GNU/Linux

Further information:
Note that I have a Debian testing live CD at hand, running kernel 4.11. The 
live CD is not affected by this issue.
I have read the description of bug #637511 and while this is an old bug, it is 
similar in the way that the system is not affected at all after a display 
manager restart.
Also, the error message reported here ist very similar to what I see: 
https://bugs.freedesktop.org/show_bug.cgi?id=93510

Please let me know what further information you require to investigate this 
issue, if any.

Best regards,
Ferdinand


-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation 
Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics 
Controller [8086:22b1] (rev 35)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.9.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.51-1 (2017-09-28)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 32263 Oct 22 02:55 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 38483 Oct 26 16:06 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[  1688.281] 
X.Org X Server 1.19.2
Release Date: 2017-03-02
[  1688.281] X Protocol Version 11, Revision 0
[  1688.281] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian
[  1688.281] Current Operating System: Linux N360-11 4.9.0-4-amd64 #1 SMP 
Debian 4.9.51-1 (2017-09-28) x86_64
[  1688.281] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 
root=/dev/sda2 ro quiet
[  1688.281] Build Date: 16 October 2017  08:19:45AM
[  1688.281] xorg-server 2:1.19.2-1+deb9u2 (https://www.debian.org/support) 
[  1688.281] Current version of pixman: 0.34.0
[  1688.281]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  1688.281] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1688.281] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 26 15:46:30 
2017
[  1688.281] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1688.282] (==) No Layout section.  Using the first Screen section.
[  1688.282] (==) No screen section available. Using defaults.
[  1688.282] (**) |-->Screen "Default Screen Section" (0)
[  1688.282] (**) |   |-->Monitor ""
[  1688.282] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[  1688.282] (==) Automatically adding devices
[  1688.282] (==) Automatically enabling devices
[  1688.282] (==) Automatically adding GPU devices
[  1688.282]