Processing commands for cont...@bugs.debian.org:
> fixed 974646 5.10~rc4-1~exp1
Bug #974646 [src:linux] W: Possible missing firmware
/lib/firmware/i915/rkl_dmc_ver2_01.bin for module i915
Marked as fixed in versions linux/5.10~rc4-1~exp1.
> thanks
Stopping processing here.
Please contact me if
Processing commands for cont...@bugs.debian.org:
> reassign 977299 src:linux
Bug #977299 [linux-image-amd64] Add Support for Intel AX210 Wi-fi and Intel
Typhoon Peak Bluetooth
Bug reassigned from package 'linux-image-amd64' to 'src:linux'.
No longer marked as found in versions 5.10.0.
Ignoring
Hi Kernel Team,
Is there any ETA on Linux 5.10 version to land in buster-backports?.
Not the right time to ask this question as vactions are coming in. Since
one of our projects depend on Linux 5.10 and we do not want to build the
package in house just wanted to get a better picture.
Thanks
Processing commands for cont...@bugs.debian.org:
> tags 974646 + pending
Bug #974646 [src:linux] W: Possible missing firmware
/lib/firmware/i915/rkl_dmc_ver2_01.bin for module i915
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
974646:
Processing commands for cont...@bugs.debian.org:
> forwarded 975686 https://bugzilla.kernel.org/show_bug.cgi?id=210593
Bug #975686 [linux-image-amd64] EDAC amd64: Error:F0 not found, device 0x1650
(broken BIOS?)
Set Bug forwarded-to-address to
Hi
On Mon, Dec 14, 2020 at 05:26:33AM +, 张 宁 wrote:
> I find in master branch, CRYPTO_SM4/CRYPTO_SM3 are disabled without clean
> justification.
SM2, SM3 and SM4 have always been disabled, as everything that does not
show up is implicitely disabled. So those commits don't change
anything,
Processing commands for cont...@bugs.debian.org:
> close 975686 5.10~rc4-1~exp1
Bug #975686 [linux-image-amd64] EDAC amd64: Error:F0 not found, device 0x1650
(broken BIOS?)
Marked as fixed in versions linux-signed-amd64/5.10~rc4+1~exp1.
Bug #975686 [linux-image-amd64] EDAC amd64: Error:F0 not
Package: linux-image-cloud-amd64
Version: 5.9.0-4
Severity: wishlist
Dear Maintainer,
please enable e1000 module in the cloud images
the rationale here is that qemu, virtualbox and openstack
defaults to this device so it would ease the life...
thank you very much!
cs
-- System Information:
Package: sssd-krb5
Version: 1.16.3-3.2
Severity: important
Dear maintainers,
all Kerberos credential cache collections are unusable with sssd and the Debian
kernel in Buster.
Details:
1) KEYRING:persistent fails to work since CONFIG_PERSISTENT_KEYRINGS is not set
in the Kernel.
Processing commands for cont...@bugs.debian.org:
> found 972459 5.10~rc7-1~exp1
Bug #972459 [src:linux] linux: Reenable CONFIG_IMA
Marked as found in versions linux/5.10~rc7-1~exp1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
972459:
Package: src:linux
Version: 5.9.11-1
Followup-For: Bug #976788
X-Debbugs-Cc: damonswir...@gmail.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
Source: linux
Version: 5.9.11-1
Severity: wishlist
Dear Maintainer,
>From 5.10, Linux vc4 driver starts supporting Raspberry Pi GPU as
https://www.phoronix.com/scan.php?page=news_item=RPi4-Display-Linux-5.10-Coming
>From Ubuntu kernel experience, CONFIG_DRM_V3D seems necessary to
fully use its
Package: src:linux
Version: 5.9.11-1
Followup-For: Bug #976788
Hello,
I have the same problem as described the previous reportes.
The lock-up appears when using kwin-x11 display manager with compositing
enabled. It does not appear on previous kernel versions (<=5.8).
This is the relevant
Source: linux
Version: 5.9.11-1
Severity: wishlist
Dear Maintainer,
Could you consider to enable CONFIG_DRM_VC4_HDMI_CEC
for arm64 and possibly armhf?
It should enable cec-client command in Debian cec-util to
control some CEC-capable devices connected via HDMI.
Best regards, Ryutaroh Matsumoto
more info which might be important:
twice now in the past week when this bug has caused the x hang issue i have
been unable to log in afterwards. i believe that both times (certainly the
most recent) it was after i had ctrl+alt+f2 to a terminal and blindly
logged in and run some command. in the
Hi all,
we were experiencing this bug in a debian 10.4 docker container (FROM
php:apache)
it only happens with plain http not with https.
I can confirm that workaround from Stefan Fritsch by
turning EnableMMAP off is working for us!
Cheers,
Florian
i have done a bit more testing. here are some additional notes:
i have found a reliable way to trigger the issue. i am using firefox-esr.
to cause the x-freeze issue, i can play a youtube video. and as it is
playing, i repeatedly move the mouse over the video, and then off of it.
this causes the
Control: retitle -1 linux-image-rpi does not boot by qemu-system-arm -machine
raspi0 or raspi1ap
Booting a Debian armel kernel by grub-efi-arm:armel seems unnecessary
to everyone (?). So I changed the title.
If linux-image-rpi can boot on qemu-system-arm, then I can modify
autopkgtest-virt-qemu
Processing control commands:
> retitle -1 linux-image-rpi does not boot by qemu-system-arm -machine raspi0
> or raspi1ap
Bug #977126 [src:linux] linux: No armel kernel can be booted by
grub-efi-arm:armel
Changed Bug title to 'linux-image-rpi does not boot by qemu-system-arm -machine
raspi0 or
19 matches
Mail list logo