Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 19 Jul 2019 00:23:17 +0200
Source: linux
Architecture: source
Version: 4.19.37-6
Distribution: unstable
Urgency: high
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Closes: 930554 930904
Your message dated Fri, 19 Jul 2019 04:55:49 +
with message-id
and subject line Bug#930554: fixed in linux 4.19.37-6
has caused the Debian Bug report #930554,
regarding Please add support for Huawei's TaiShan server platform
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 19 Jul 2019 04:55:49 +
with message-id
and subject line Bug#930904: fixed in linux 4.19.37-6
has caused the Debian Bug report #930904,
regarding linux-image-4.19.0-5-amd64: Latest kernel upgrades on unstable break
Steam (link to fix included)
to be marked as done.
linux_4.19.37-6_source.changes uploaded successfully to localhost
along with the files:
linux_4.19.37-6.dsc
linux_4.19.37-6.debian.tar.xz
linux_4.19.37-6_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
On Thu, 2019-07-18 at 21:36 +0100, Terry wrote:
> Package: src:linux
> Version: 4.19.37-5
> Severity: important
>
> Dear Maintainer,
>
> I performed an upgrade from stretch to buster today and the kernel
> paniced with a not syncing error.
>
> I've attempted to switch of acpi but adding the
Processing commands for cont...@bugs.debian.org:
> reassign 932368 src:nvidia-graphics-drivers
Bug #932368 [src:linux] linux-image-4.19.0-5-amd64: Blank a screen with setterm
(setterm -blank force) is not possible anymore.
Bug reassigned from package 'src:linux' to 'src:nvidia-graphics-drivers'.
Processing commands for cont...@bugs.debian.org:
> tags 932408 + moreinfo
Bug #932408 [src:linux] linux-image-4.19.0-5-amd64: kernel panic not syncing
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
932408:
Package: src:linux
Version: 4.19.37-5
Severity: important
Dear Maintainer,
I performed an upgrade from stretch to buster today and the kernel paniced with
a not syncing error.
I've attempted to switch of acpi but adding the options acpi=off pci=noacpi to
the boot line but this didn't have any
#
# bts-link upstream status pull for source package src:linux
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #931330
Your message dated Thu, 18 Jul 2019 21:15:27 +0200
with message-id <23856.50511.278325.41...@informatik.uni-koeln.de>
and subject line closing
has caused the Debian Bug report #686658,
regarding nfs-kernel-server: NFS Thread usage (th)
to be marked as done.
This means that you claim that the
On Thu, 18 Jul 2019, Dmitry Bogatov wrote:
> On my system, $x-display-manager is defined in /etc/insserv.conf.d/xdm;
> on headless box there is no display manager, hence warning. Situation
> with $portmap seems similar.
Indeed, I also ran into the $x-display-manager one after having
reported
Processing commands for cont...@bugs.debian.org:
> severity 874364 normal
Bug #874364 [gnome-control-center,systemd,initramfs-tools] Keyboard layout set
in GNOME or with localectl does not apply to initramfs LUKS prompt immediately
Severity set to 'normal' from 'important'
> thanks
Stopping
Forwarded Message
From: a a
To: Ben Hutchings
Subject: Re: Bug#932250: linux-image-amd64: random segfaults without
taking something down
Date: Thu, 18 Jul 2019 13:09:53 +0200
Message-Id:
It shouldnt be overheating, because i have custom setting on cpu heatsink
fan and the
It shouldnt be overheating, because i have custom setting on cpu heatsink
fan and the ram module has a own heatsink. Plus i have fan on case which
puls out the excees heat. The segfaults happend at low load, maybe it wasnt
above P2 power state. Also i have made sure that the cpu doenst exceed
Am 17.07.19 um 19:32 schrieb Vincent Tondellier:
>> It looks like (one of) the two `flow table` lines are at fault,
>> but I am not able to confirm this for sure, because the assertion
>> is not 100% reliably triggered.
>
> I can reproduce your crash quite reliably, maybe because I have kernel
On Wed, Jul 17, 2019 at 10:51 PM Miguel A. Vallejo wrote:
> But for me this problem is triggered by the Arduino IDE.
Interesting. The system bell only starts when I open my xfce session.
I'll continue digging in the audio direction.
Thanks
16 matches
Mail list logo
