On Sun, 2018-02-11 at 10:56 +0100, Bastian Blank wrote:
> Moin
>
> After almost four years and due to recent changes in the syscall path,
> I'd like to revisit our current handling of the x32 ABI.
>
> Currently we disable support for the x32 ABI on runtime, enabling it
> needs a kernel command
I updated to the stretch-proposed-updates version and am very happy thus
far. Sorry for the noise and thank you for the fix.
# uname -a
Linux lappy7 4.9.0-5-amd64 #1 SMP Debian 4.9.80-2 (2018-02-09) x86_64
GNU/Linux
# dmesg | grep 915
[ 15.124116] snd_hda_intel :00:03.0: bound :00:02.0
Yves-Alexis
Thank you. Would enabling that repo/branch and testing help at all with
this?
My confusion is that https://packages.debian.org/stretch/linux-image-amd64
and https://packages.debian.org/stretch/linux-image-4.9.0-5-amd64 did not
match up. I wonder if this is a mistake. I will go back
On Sun, 2018-02-11 at 13:33 -0600, Andrew Latham wrote:
> Related info in dmesg
> [0.00] Linux version 4.9.0-5-amd64 (debian-kernel@lists.debian.org)
> (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-
> 3+deb9u2 (2018-01-04)
> [ 273.787162] [drm:gen8_irq_handler
Thinkpad X1 Carbon Gen3 Intel HD Graphics 5500 Broadwell - WQHD (2560x1440)
Simple Debian Stretch install, updated, using KDE desktop
No bells or tweaks, standard install.
Reproduce
1. Open Google Chrome web browser
2. Open KDE Konsole app
3. Press enter or type a char
4. Screen scrolls
Package: linux-image-4.14.0-3-amd64
Version: 4.14.0-3
I have upgraded my laptop to unstable related.
I get the following errors during boot which disturbs me.
--- file attached ---
i use Debian GNU/Linux buster/sid related.
i do not get this error when i boot an older kernel which
is of 4.9
Hi,
after in total nine weeks of bisecting, broken filesystems, service
outages (thankfully on unportant systems), 4.15 seems to have fixed the
issue. After going to 4.15, the crashes never happened again.
They have, however, happened with each and every 4.14 release I tried,
which I stopped
Moin
After almost four years and due to recent changes in the syscall path,
I'd like to revisit our current handling of the x32 ABI.
Currently we disable support for the x32 ABI on runtime, enabling it
needs a kernel command line parameter. This Debian specific change was
done due to concerns
Package: nfs-kernel-server
Version: 1:1.3.4-2.1+b1
Severity: normal
I have recently changed my NFS setup so that one of the intermediate paths for
the
exported filesystem is a symlink. With this setup, trying to start the system
with
systemctl start nfs-server
fails, with `systemctl
9 matches
Mail list logo
