Package: linux-base
Version: 4.6
Severity: normal
Tags: patch
Hi,
The perf wrapper script in Debian requires the perf binary of the running
kernel. However, there's not really a good reason for this; perf has a stable
ABI, and even though it's distributed and built with the kernel, you can
Processing commands for cont...@bugs.debian.org:
> found 983818 5.10.40-1
Bug #983818 [src:linux] linux-image-5.10.0-3-arm64: often fails to bring up
eth0 / dwmac_rk module
Marked as found in versions linux/5.10.40-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Thanks!
I installed linux-image-5.9.0-0.bpo.5-amd64 and instantly reproduced the issue.
For reference: the amplifier is a Denon AVR-X500. I just purchased a Denon
AVR-X1000 as replacement, I will confirm whether the issue is fixed as soon as
I receive it.
At this point I'm 99% sure it's the
Control: reassign -1 iptables-netflow-dkms
Control: found -1 2.3-5
Control: notfound -1 2.5.1-2
Hi Salvatore,
Salvatore Bonaccorso wrote:
> On Mon, Jun 21, 2021 at 01:33:01PM +0200, Axel Beckert wrote:
> > Since kernel packages linux-{image,headers}-4.19.0-17-*, at least with
> > -amd64 and
Processing control commands:
> reassign -1 iptables-netflow-dkms
Bug #990123
[iptables-netflow-dkms,linux-headers-4.19.0-17-amd64,linux-headers-4.19.0-17-i686-pae]
[buster regression] iptables-netflow-dkms: No more compiles since
linux-*-4.19.0-17-*: "implicit declaration of function
Processing commands for cont...@bugs.debian.org:
> reassign 990162 src:linux 5.10.28-1
Bug #990162 [linux-image-5.10.0-6-amd64] power consumption regression
Warning: Unknown package 'linux-image-5.10.0-6-amd64'
Bug reassigned from package 'linux-image-5.10.0-6-amd64' to 'src:linux'.
No longer
Control: affects -1 + release.debian.org
Hi Axel,
On Mon, Jun 21, 2021 at 01:33:01PM +0200, Axel Beckert wrote:
> Package:
> iptables-netflow-dkms,linux-headers-4.19.0-17-amd64,linux-headers-4.19.0-17-i686-pae
> Severity: serious
> Version: iptables-netflow/2.3-5
> Version:
Processing control commands:
> affects -1 + release.debian.org
Bug #990123
[iptables-netflow-dkms,linux-headers-4.19.0-17-amd64,linux-headers-4.19.0-17-i686-pae]
[buster regression] iptables-netflow-dkms: No more compiles since
linux-*-4.19.0-17-*: "implicit declaration of function
Hi Paul,
thanks for your immediate response.
Your assumption is right, booting into kernel 4.19.0-16 causes
lxc-attach to behave as expected, no more apparmor related errors.
Cheers Bernd
Am 21.06.21 um 19:06 schrieb Paul Gevers:
Hi Bernd,
Thanks for your report.
On 21-06-2021 18:04,
Processing commands for cont...@bugs.debian.org:
> # try two
> forcemerge 990072 990140
Bug #990072 {Done: Salvatore Bonaccorso } [src:linux]
lxc-attach fails after debian 10.10 update
Bug #990075 {Done: Salvatore Bonaccorso } [src:linux]
lxc-attach fails after debian 10.10 update
Bug #990089
Processing commands for cont...@bugs.debian.org:
> reassign 990140 src:linux
Bug #990140 [upgrade-reports] upgrade-reports: lxc-attach does not start with
apparmor problem after ugrade to 10.10
Bug reassigned from package 'upgrade-reports' to 'src:linux'.
Ignoring request to alter found versions
Hi Bernd,
Thanks for your report.
On 21-06-2021 18:04, Bernd Breuer wrote:
> after the recent upgrade to Buster 10.10 (including a kernel upgrade) the
> command 'lxc-attach' (out of the Linux Container (lxc) set of commands),
> typed in like
>
> "sudo lxc-attach "
>
> stopped working with
Good morning,
[I have searched the list archives and the debian bugzilla, but not got any
hits on this being discussed already. If it has, apologies, I missed it.]
I make extensive use of Debian on single board computers, and have a use
case to run them diskless over a VLAN using nbd-server &
Processing commands for cont...@bugs.debian.org:
> # Version tracking seems to not have worked properly in the initial bug
> submission
> found 990123 iptables-netflow/2.3-5
Bug #990123
[iptables-netflow-dkms,linux-headers-4.19.0-17-amd64,linux-headers-4.19.0-17-i686-pae]
[buster regression]
Package: firmware-misc-nonfree
Version: 20190114-2
kernel module: mt76x0
Severity: serious
Following an update recently, this driver stopped working correctly. I
can now only get a working WiFi connection for a few seconds after
reboot, or after waiting several minutes, making anything that
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 21 Jun 2021 10:46:20 +0200
Source: linux
Architecture: source
Version: 4.19.194-2
Distribution: buster
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Closes: 990072
Changes:
Your message dated Mon, 21 Jun 2021 12:02:07 +
with message-id
and subject line Bug#990072: fixed in linux 4.19.194-2
has caused the Debian Bug report #990072,
regarding linux-image-4.19.0-17-amd64: lxc-attach Operation not permitted -
Failed to set AppArmor label
to be marked as done.
This
Your message dated Mon, 21 Jun 2021 12:02:07 +
with message-id
and subject line Bug#990072: fixed in linux 4.19.194-2
has caused the Debian Bug report #990072,
regarding linux-image-4.19.0-17-amd64: lxc-attach fails with Failed to set
AppArmor label unconfined
to be marked as done.
This
Your message dated Mon, 21 Jun 2021 12:02:07 +
with message-id
and subject line Bug#990072: fixed in linux 4.19.194-2
has caused the Debian Bug report #990072,
regarding lxc-attach fails after debian 10.10 update
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 21 Jun 2021 12:02:07 +
with message-id
and subject line Bug#990072: fixed in linux 4.19.194-2
has caused the Debian Bug report #990072,
regarding lxc-attach fails after debian 10.10 update
to be marked as done.
This means that you claim that the problem has been dealt
> Pushed a fix to git:
>
> https://salsa.debian.org/kernel-team/linux/-/commit/f952b94621847732b3ed96a74babb89b6a1862f6
Wow! Thanks! At least I now know I'm not crazy... Any idea how long it will
be before the fix is in something I can download and install with?
Enjoy!
Rick
On maandag 21 juni 2021 13:20:46 CEST Drew Parsons wrote:
> I was surprised to see python2 pulled in on a new bullseye
> installation using nfs.
>
> It's a trivial patch of course to update the hashbangs for mountstats
> and nfsiostat in nfs-common 1:1.3.4-5 to python3.
Package:
iptables-netflow-dkms,linux-headers-4.19.0-17-amd64,linux-headers-4.19.0-17-i686-pae
Severity: serious
Version: iptables-netflow/2.3-5
Version: iptables-netflow/2.5.1-2
Version: linux/4.19.194-1
Tags: buster
Forwarded: https://github.com/aabc/ipt-netflow/issues/177
Since kernel packages
Package: nfs-common
Followup-For: Bug #883194
X-Debbugs-Cc: debian-rele...@lists.debian.org
I was surprised to see python2 pulled in on a new bullseye
installation using nfs.
It's a trivial patch of course to update the hashbangs for mountstats
and nfsiostat in nfs-common 1:1.3.4-5 to python3.
Hi,
On Mon, Jun 21, 2021 at 10:24:31AM +0100, Gmail wrote:
> Salvatore,
>
> On Sun, 2021-06-20 at 20:39 +0200, Salvatore Bonaccorso wrote:
> > Hi Mark,
> >
> > On Sun, Jun 20, 2021 at 10:44:29AM +0100, Mark Grant wrote:
> > > Package: src:linux
> > > Version: 4.19.194-1
> > > Severity: normal
>
problem resolved, i think.
new sof firmware update came out, not sure its arrival was more than a
coincidence
1 - disabling all intel vitrualisation options in the helix bios was enough
to allow the fw to load thus pavucontrol was now seeing input bars moving
but no sound output.
2 - ran
Salvatore,
On Sun, 2021-06-20 at 20:39 +0200, Salvatore Bonaccorso wrote:
> Hi Mark,
>
> On Sun, Jun 20, 2021 at 10:44:29AM +0100, Mark Grant wrote:
> > Package: src:linux
> > Version: 4.19.194-1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > After upgrading from
Mapping buster to stable.
Mapping stable to proposed-updates.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 21 Jun 2021 10:46:20 +0200
Source: linux
Architecture: source
Version: 4.19.194-2
Distribution: buster
Urgency: medium
Maintainer: Debian Kernel Team
linux_4.19.194-2_source.changes uploaded successfully to localhost
along with the files:
linux_4.19.194-2.dsc
linux_4.19.194-2.debian.tar.xz
linux_4.19.194-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
On maandag 21 juni 2021 03:14:47 CEST Davide Beatrici wrote:
> I reproduced the problem on 5.10.0-6 as well
> I believe the relay in the amplifier is going bad
It maybe useful to try a 5.9.x kernel as well, to properly rule out the kernel
as the source of the issues. Difference between -6 and -7
Hi Matthew,
On Sun, Jun 20, 2021 at 11:14:57PM -0400, Matthew Darwin wrote:
> kernel 4.19.194-1a~test resolved the issue
>
> Applied
> https://lore.kernel.org/stable/20210614102643.875096...@linuxfoundation.org/
> using the process described at
>
Processing commands for cont...@bugs.debian.org:
> forwarded 990008 https://bugzilla.kernel.org/show_bug.cgi?id=213481
Bug #990008 [src:linux] linux-image-5.10.0-7-amd64: e1000e driver fails to load
after upgrade to bullseye from buster
Set Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> forwarded 990008 https://bugzilla.kernel.org/show_bug.cgi?id=213481
Bug #990008 [src:linux] linux-image-5.10.0-7-amd64: e1000e driver fails to load
after upgrade to bullseye from buster
Ignoring request to change the forwarded-to-address of
Hi all, starting from Debian Buster (on older kernels it works, on
newer kernels it fails), I have a problem with the Wi-Fi connection of
my PC:
When I connect a Huawei P Smart smartphone to the same wireless
network my PC is on,
my Wi-Fi card hangs indefinitely, thus causing a disconnection, and
34 matches
Mail list logo
