Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 18 Aug 2019 22:54:21 +0100
Source: linux
Architecture: source
Version: 5.2.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Ben Hutchings
Closes: 908712 925766 931707 933963
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id
and subject line Bug#934378: fixed in linux 5.2.9-1
has caused the Debian Bug report #934378,
regarding linux-image-5.2.0-2-amd64: linux-5.2.0-2 : Unable to mount CDROM
to be marked as done.
This means that you claim that the
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id
and subject line Bug#934309: fixed in linux 5.2.9-1
has caused the Debian Bug report #934309,
regarding linux-image-5.2.0-1-amd64-unsigned: suggesting INTEL_IOMMU_DEFAULT_ON
to be marked as done.
This means that you claim that
Your message dated Mon, 19 Aug 2019 05:32:13 +
with message-id
and subject line Bug#934848: fixed in linux 5.2.9-1
has caused the Debian Bug report #934848,
regarding linux-image-4.19.0-5-amd64: The Cavium PTP device driver is always
loaded
to be marked as done.
This means that you claim
Your message dated Mon, 19 Aug 2019 05:32:13 +
with message-id
and subject line Bug#934824: fixed in linux 5.2.9-1
has caused the Debian Bug report #934824,
regarding bug script doesn't grok missing /e/n/i
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id
and subject line Bug#934304: fixed in linux 5.2.9-1
has caused the Debian Bug report #934304,
regarding BUG: kernel NULL pointer dereference
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id
and subject line Bug#934304: fixed in linux 5.2.9-1
has caused the Debian Bug report #934304,
regarding powertop: Powertop gets terminated with SIGKILL
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id
and subject line Bug#934304: fixed in linux 5.2.9-1
has caused the Debian Bug report #934304,
regarding linux-image-5.2.0-1-amd64-unsigned: powertop -i 10 always causes
kernel NULL pointer dereference
to be marked as done.
This
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id
and subject line Bug#934091: fixed in linux 5.2.9-1
has caused the Debian Bug report #934091,
regarding Missing HID driver modules (Most are fairly new since 5.0 or so)
to be marked as done.
This means that you claim that the
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id
and subject line Bug#933963: fixed in linux 5.2.9-1
has caused the Debian Bug report #933963,
regarding New rtw88 driver missing from 5.2 and above
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id
and subject line Bug#934304: fixed in linux 5.2.9-1
has caused the Debian Bug report #934304,
regarding linux-image-5.2.0-2-amd64: powertop aborts on version 5.2
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id
and subject line Bug#931707: fixed in linux 5.2.9-1
has caused the Debian Bug report #931707,
regarding linux: HW_RANDOM_OMAP disabled for arm64 --> please enable
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id
and subject line Bug#934304: fixed in linux 5.2.9-1
has caused the Debian Bug report #934304,
regarding powertop: running powertop introduces "kernel NULL pointer
dereference"
to be marked as done.
This means that you claim that
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id
and subject line Bug#925766: fixed in linux 5.2.9-1
has caused the Debian Bug report #925766,
regarding linux: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
linux_5.2.9-1_source.changes uploaded successfully to localhost
along with the files:
linux_5.2.9-1.dsc
linux_5.2.9.orig.tar.xz
linux_5.2.9-1.debian.tar.xz
linux_5.2.9-1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Processing commands for cont...@bugs.debian.org:
> found 929557 5.0.1-1~exp1
Bug #929557 [src:linux] linux: restore __kernel_fpu needed for zfs for
AES-NI/AVX support [mainline not in debian yet]
Marked as found in versions linux/5.0.1-1~exp1.
> thanks
Stopping processing here.
Please contact
Processing control commands:
> forwarded 934331
> https://lore.kernel.org/stable/20190818155941.GA26766@eldamar.local/
Bug #934331 [linux] linux: backport "dm: disable DISCARD if the underlying
storage no longer supports it"?
Set Bug forwarded-to-address to
Control: forwarded 934331
https://lore.kernel.org/stable/20190818155941.GA26766@eldamar.local/
Hi Chris,
On Fri, Aug 09, 2019 at 11:12:36PM +0200, Chris Hofstaedtler wrote:
> Package: linux
> Version: 4.9.168-1+deb9u4
> Severity: normal
>
> Hi!
>
> Today I ran into an issue that matches the
Processing commands for cont...@bugs.debian.org:
> forwarded 934331
> https://lore.kernel.org/stable/20190818155941.GA26766@eldamar.local/
Bug #934331 [linux] linux: backport "dm: disable DISCARD if the underlying
storage no longer supports it"?
Ignoring request to change the
Processing commands for cont...@bugs.debian.org:
> fixed 921542 5.0.1-1~exp1
Bug #921542 {Done: Ben Hutchings } [src:linux] tc qdisc
kernel crash
Marked as fixed in versions linux/5.0.1-1~exp1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921542:
Processing commands for cont...@bugs.debian.org:
> fixed 921542 5.0
Bug #921542 {Done: Ben Hutchings } [src:linux] tc qdisc
kernel crash
The source 'linux' and version '5.0' do not appear to match any binary packages
Marked as fixed in versions linux/5.0.
> thanks
Stopping processing here.
Hi,
sorry for not replying to the thread. I am not on the mailing list but will fix
that after I send this message.
The issue you are reporting is a known issue with the 5.2 branch. If you use
the firmware-iwlwifi from Buster, your troubles should go away. Its a
compatibility issue with the
On Sun, 2019-08-18 at 10:26 -0400, thom...@fastmail.cn wrote:
> > I don't see any sign of CONFIG_HID_GT683R but have enabled the
> > others.
> I know all this is huge to maintain so I really appreciate all your
> help with this and you maintaining the Kernel. It is defined on line
> 383 of
Processing control commands:
> reassign -1 xserver-xorg-core
Bug #930631 [src:linux] linux-image-4.19.0-5-amd64: Fresh Buster install fails
to boot to desktop
Bug reassigned from package 'src:linux' to 'xserver-xorg-core'.
No longer marked as found in versions linux/4.19.37-3.
Ignoring request
Control: reassign -1 xserver-xorg-core
On Mon, 2019-08-05 at 22:44 +0100, Dai Trying wrote:
> This "bug" is actually with xserver-xorg-core package and is caused by the
> modesetting DDX driver, can this be changed here or do I need to file a new
> bug report?
I'm reassigning it, but you will
Processing control commands:
> tag -1 pending
Bug #934091 [src:linux] Missing HID driver modules (Most are fairly new since
5.0 or so)
Added tag(s) pending.
--
934091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
On Tue, 2019-08-06 at 17:54 -0400, thom...@fastmail.cn wrote:
> package: src:linux
> Keyboards, leds, remote controls etc.
> CONFIG_HID_BIGBEN_FF
> CONFIG_HID_GFRM
> CONFIG_HID_GT683R
I don't see any sign of CONFIG_HID_GT683R but have enabled the others.
Thanks,
Ben.
>
Processing commands for cont...@bugs.debian.org:
> forwarded 934828 https://bugzilla.kernel.org/show_bug.cgi?id=204141
Bug #934828 [src:linux] iwl_mvm_add_new_dqa_stream_wk BUG in lib/list_debug.c:56
Set Bug forwarded-to-address to
'https://bugzilla.kernel.org/show_bug.cgi?id=204141'.
> thanks
* Arnaud Patard [2019-08-02 10:58]:
> Sorry for the delay. I was waiting for some feedback before sending and
> then got busy with other stuff. I've now sent it:
> https://marc.info/?l=linux-netdev=156473570707976=2.
For the record, this has been accepted and queued for stable:
Source: linux
Severity: important
Dear Maintainer,
I often encouter GPU freezes using the buster kernel (4.19) and my AMD GPU
(Radeon 580) on 3D apps.
Here is a trace from dmesg:
[41030.750400] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=13431126, emitted
30 matches
Mail list logo
