Bug#944420: Fixed in 5.5

2020-02-25 Thread Philipp Klaus Krause
The green screen lockup issue is fixed in 5.5.

I've tried 5.5rc5 from experimental. While it crashes a lot and shows
graphical corruption in XFCE, I don't not get the green screen lockup.

I've also compiled 5.5.6 myself. With that kernel, crashes are a lot
less common (though they still happen in games sometimes) and the
graphical corruption is gone too.



Bug#944420: Can't reproduce when using 5.1.21 from Ubuntu packages

2019-11-21 Thread Philipp Klaus Krause
Today, I've also installed a 5.1.21 kernel from Ubuntu on my Debian
GNU/Linux testing system, and logged into XFCE thrice. I did not see the
green screen crash with that kernel, though once I got a crash (system
frozen, only mouse pointer still moveable) a few minutes after logging in.



Bug#944420: Upstream bug report

2019-11-20 Thread Philipp Klaus Krause
Upstream bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=205589



Bug#944420: Two more confirmations

2019-11-20 Thread Philipp Klaus Krause
Two more Manjaro users with of the green screen hang on XFCE start using
3400G with a 5.x kernel: One in the thread mentined above, the other in
https://forum.manjaro.org/t/kernel-question-amd-ryzen-5-2400g-with-radeon-vega-graphics/106683



Bug#944420: Bug confirmed with 5.x kernel on Manjaroo, too

2019-11-14 Thread Philipp Klaus Krause
Apparently someone has the same problem (AMD 3400G APU, mainboard with
B450 chipset, 5.x linux kernel, green screen crash just after login)
using a RC of linux 5.4 on Manjaro:

https://forum.manjaro.org/t/manjaro-with-ryzen-3-3200g-vega-8-any-experience/110497/18



Bug#944420: Also tried 5.2.0

2019-11-09 Thread Philipp Klaus Krause
I also tried an older 5.2.0 kernel:

linux-image-5.2.0-3-amd64 5.2.17-1

The problem there is the same, but it seems I have a somewhat higher
chance to make it to XFCE (in which I still see graphical corruption)
than just getting a green screen (which I there see bit less than half
of the time).



Bug#944420: Wrong info

2019-11-09 Thread Philipp Klaus Krause
I see reportbug added a lot of information from the system on which I
submitted the bug report. Please disregard that; sorry for the noise.

Do you need any further information from the system on which I see the
bug that I should provide?



Bug#944420: linux-image-5.3.0-1-amd64: green screen in X

2019-11-09 Thread Philipp Klaus Krause
Package: src:linux
Version: 5.3.7-1
Severity: important

A few days ago, I installed Debian on a new Ryzen 3400G system (not the system
on which I write this report, hope reportbug doesn't add any invalid
information from the system on which I type this).

I see graphical problems in X. I am not sure if the bug is in the kernel or
elsewhere, but the kernel seemed the most likely candidate for the bug report
to me.

I have installed XFCE. After boot, I see the graphical login screen. After
login, most of the time, the screen turns a dark green (so I don't get to see
XFCE). Sometimes I do get to XFCE, but then there is graphical corruption.

Despite the screen going green (which seems permanent - switching to a console
won't help), I can still switch to a console and type blindly. That way I
obtained the dmesg output I put at http://www.colecovision.eu/stuff/dmesg-log

I have also tried with kernel options ioomu=off and iommu=pt init=nomwait, but
neither one helped. The same system seems stable on Windows 10, so I guess it
is not a hardware issue.

Some installed packages:

linux-image-amd64 5.3.7-1
firmware-amd-graphics 20190717-2
xserver-xorg-vieo-amdgpu 19.1.0-1



-- Package-specific info:
** Version:
Linux version 5.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 
20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19)

** Command line:
BOOT_IMAGE=/vmlinuz-5.3.0-1-amd64 root=/dev/mapper/universum-root ro quiet

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Notebook
product_name: N24_25BU
product_version: Not Applicable  
chassis_vendor: Notebook
chassis_version: N/A 
bios_vendor: American Megatrends Inc.
bios_version: 5.12
board_vendor: Notebook
board_name: N24_25BU
board_version: Not Applicable  

** Loaded modules:
loop
udf
crc_itu_t
nls_utf8
isofs
fuse
ufs
qnx4
hfsplus
hfs
minix
msdos
jfs
xfs
ti_usb_3410_5052
sr_mod
cdrom
uas
usb_storage
ctr
ccm
cmac
bnep
binfmt_misc
btusb
btrtl
btbcm
btintel
pl2303
usbserial
bluetooth
nls_ascii
nls_cp437
uvcvideo
videobuf2_vmalloc
videobuf2_memops
videobuf2_v4l2
videobuf2_common
videodev
vfat
fat
mc
drbg
ansi_cprng
ext4
ecdh_generic
ecc
crc16
iwlmvm
mbcache
snd_soc_skl
intel_rapl_msr
jbd2
snd_soc_hdac_hda
intel_rapl_common
mac80211
snd_hda_ext_core
snd_soc_skl_ipc
snd_soc_sst_ipc
snd_soc_sst_dsp
snd_soc_acpi_intel_match
snd_hda_codec_realtek
x86_pkg_temp_thermal
intel_powerclamp
snd_hda_codec_generic
snd_soc_acpi
libarc4
coretemp
snd_soc_core
ledtrig_audio
snd_compress
kvm_intel
snd_hda_intel
iwlwifi
snd_hda_codec
snd_hda_core
kvm
snd_hwdep
cfg80211
irqbypass
snd_pcm
intel_cstate
efi_pstore
intel_uncore
snd_timer
joydev
iTCO_wdt
intel_rapl_perf
iTCO_vendor_support
serio_raw
pcspkr
mei_me
snd
rtsx_pci_ms
efivars
watchdog
soundcore
sg
memstick
tpm_crb
mei
rfkill
intel_pch_thermal
battery
tpm_tis
tpm_tis_core
tpm
evdev
acpi_pad
rng_core
ac
parport_pc
ppdev
lp
sunrpc
parport
efivarfs
ip_tables
x_tables
autofs4
btrfs
zstd_decompress
zstd_compress
dm_crypt
dm_mod
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
hid_generic
usbhid
hid
raid6_pq
libcrc32c
crc32c_generic
raid1
raid0
multipath
linear
md_mod
sd_mod
crct10dif_pclmul
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
i915
nvme
rtsx_pci_sdmmc
mmc_core
ahci
i2c_algo_bit
aesni_intel
drm_kms_helper
libahci
xhci_pci
aes_x86_64
psmouse
crypto_simd
cryptd
glue_helper
nvme_core
xhci_hcd
drm
i2c_i801
rtsx_pci
libata
mfd_core
r8169
realtek
libphy
scsi_mod
usbcore
usb_common
wmi
video
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: CLEVO/KAPOK Computer Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers [1558:2410]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: CLEVO/KAPOK Computer HD Graphics 620 [1558:2410]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / 
E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911]
Subsystem: CLEVO/KAPOK Computer Xeon E3-1200 v5/v6 / E3-1500 v5 / 
6th/7th Gen Core Processor Gaussian Mixture Model [1558:2410]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VG

Bug#844604: [src:linux] Crash when resuming after suspend-to-disk

2016-11-17 Thread Philipp Klaus Krause
Package: src:linux
Severity: important

--- Please enter the report below this line. ---

Whenever I try to resume from supend-to-disk, I get a crash with message:

BUG: Unable to handle kernel paging request at a1c15685f000
[…]

The problem happens no matter if I use "s2disk" or "systemcl hibernate".
Suspend-to-disk used to work up to a few months ago, but the problem
already was there with Linux 4.7 and I'm not sure which was the last
working version.
On the other hand, suspend-to-ram still works fine.
My memory hardware should be ok, as Memtest86+ does not find any errors.

I see this problem on a Schenker S403 Ultrabook with an Intel Core
i7-4500U processor and 16 GB of RAM.

--- System information. ---
Architecture: Kernel:   Linux 4.8.0-1-amd64

Debian Release: stretch/sid
  500 unstableftp.de.debian.org   500 testing
ftp.de.debian.org 1 experimentalftp.de.debian.org
--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.



Bug#641622: Resolution

2011-09-16 Thread Philipp Klaus Krause
I observe the bug using 1280x800 and 800x600 resolution. I cannot
reproduce the bug in 1024x768 resolution.

Philipp



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e737ddb@spth.de



Bug#641622: System configuration

2011-09-16 Thread Philipp Klaus Krause
Here's some further information on my current system configuration (not
the one were I originally observed the bug, but it still is there),
which might be useful to reproduce the bug:

/proc/version: Linux version 3.1.0-rc4 (root@notebook3) (gcc version
4.6.1 (Debian 4.6.1-8) ) #1 SMP Mon Aug 29 21:01:35 CEST 2011

Package versions:
simutrans: 110.0.1-3
libdrm2: 2.4.26-1
libgl1-mesa-dri: 7.11-5
xserver-xorg-video-intel: 2:2.15.0-3
xserver-xorg-core: 2:1.10.4-1
libsdl1.2debian: 1.2.14-6.4

I use gnome2, and start simutrans using "simutrans -fullscreen" from a
gnome terminal.

Philipp



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e73710a.5080...@spth.de



Bug#641622: Screen corruption regression

2011-09-14 Thread Philipp Klaus Krause
Package: linux-image-3.1.0-rc4-amd64
Version: 3.1.0~rc4-1~experimental.1
Severity: Important

There is a screen corruption regression for intel graphics. It sometimes
appears spuriously and has been observed by multiple people. However
there are ways way to reproduce it:

In the free game simutrans, in fullscreen mode (install it from teh
Debian package, start using "simutrans -fullscreen") I see the following
problem:
The lower about 2 cm of the screen don't update. They are black or carry
the image from the game startup screen. They flicker once in a while,
but otherwise the image stays the same.
This makes the game practically unplayable in fullscreen mode.

lspci output:
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (primary) (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (secondary) (rev 0c)

glxinfo:
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) 965GM
OpenGL version string: 2.1 Mesa 7.11

I have bisected this issue to the following commit:

d74362c9e45689d8d7e3d4bcf6681c4358ef4f2e is the first bad commit
commit d74362c9e45689d8d7e3d4bcf6681c4358ef4f2e
Author: Keith Packard 
Date:   Thu Jul 28 14:47:14 2011 -0700

drm/i915: Flush other plane register writes

Writes to the plane control register are buffered in the chip until a
write to the DSPADDR (pre-965) or DSPSURF (post-965) register occurs.

This patch adds flushes in:

intel_enable_plane
gen6_init_clock_gating
ivybridge_init_clock_gating

Signed-off-by: Keith Packard 

:04 04 68666ff438ff2b9890a72914905b4aadf53e23ef
101e78df34814a3661c87e9e44d10761d0676d7a M  drivers

Switching to the console and back or taking a screen shot is a temporary
(few seconds) workaround.
Using kernel command line i915.i915_enable_fbc=0 is a permanent workaround.

There were some messages on the Intel-gfx list about this (titled
"Screen corruption regression from 3.0 to 3.1rc4").

Philipp



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e70e39a.4090...@spth.de