Processed: severity of 983357 is important, tagging 983357

2021-08-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 983357 important Bug #983357 [linux] udevadm trigger fails for Xen Virtual Keyboard driver Severity set to 'important' from 'normal' > tags 983357 + upstream patch Bug #983357 [linux] udevadm trigger fails for Xen Virtual Keyboard driver

Processed: tagging 992121

2021-08-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 992121 + bullseye Bug #992121 {Done: Salvatore Bonaccorso } [src:linux] linux-image-5.10.0-8-amd64: kernel oops and subsequent hard crash in bluetooth bt_sock_poll, regression, upstream patch Added tag(s) bullseye. > thanks Stopping

Bug#983357: Bug#988776: Bug#983357: Netinst crashes xen domU when loading kernel

2021-08-26 Thread Chuck Zmudzinski
On 8/26/2021 8:01 AM, Chuck Zmudzinski wrote: On 8/24/2021 7:12 PM, Ben Hutchings wrote: The current limit on the environment of a uevent appears to be 2 KB (UEVENT_BUFFER_SIZE defined in ).� That seems like it *might* be easier to change, so long as user-space doesn't have a similar limit.

Bug#949973: closed by maximilian attems (Re: firmware-realtek: kernel error caught)

2021-08-26 Thread pior...@gmail.com
Hi, My apologies, I forgot about this bug completely and didn't noticed your follow up. Now I use different laptop, but it works perfectly with Debian 11. Thanks for your work!

Bug#983357: Bug#988776: Bug#983357: Netinst crashes xen domU when loading kernel

2021-08-26 Thread Chuck Zmudzinski
On 8/24/2021 7:12 PM, Ben Hutchings wrote: The current limit on the environment of a uevent appears to be 2 KB (UEVENT_BUFFER_SIZE defined in ). That seems like it *might* be easier to change, so long as user-space doesn't have a similar limit. I looked into systemd/udev, and it seems to use

Bug#949973: marked as done (firmware-realtek: kernel error caught)

2021-08-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Aug 2021 15:40:36 +0200 with message-id and subject line Re: firmware-realtek: kernel error caught has caused the Debian Bug report #949973, regarding firmware-realtek: kernel error caught to be marked as done. This means that you claim that the problem has been dealt

Bug#992555: probably same on Dell Inspiron 3580

2021-08-26 Thread Piotr A. Dybczyński
Hi, both: after upgrade from Buster and after clean install laptop does not wake up when opening lid. Simply freezes, only power off helps. When I boot Bullseye with 4.19 kernel it works. Regards, Piotr A. Dybczyński --

Bug#990127: mt76x0 crashes repeatedly

2021-08-26 Thread maximilian attems
reassign 990127 linux 4.19.181-1 tags 990127 moreinfo stop > Package: firmware-misc-nonfree > Version: 20190114-2 > kernel module: mt76x0 The firmware did not change for ages, hence reassigning to linux. > Following an update recently, this driver stopped working correctly. I can > now only

Processed: Re: Bug#990127: mt76x0 crashes repeatedly

2021-08-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 990127 linux 4.19.181-1 Bug #990127 [firmware-misc-nonfree] mt76x0 crashes repeatedly Bug reassigned from package 'firmware-misc-nonfree' to 'linux'. No longer marked as found in versions firmware-nonfree/20190114-2. Ignoring request to

Re: Bug#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners

2021-08-26 Thread Bjørn Mork
Martin-Éric Racine writes: >> [1] https://wiki.debian.org/DeviceDatabase/USB YUCK! That is fundamentally flawed. It is so misleading that it is harmful. Could someone with Wiki access pleaase delete that page? Bjørn

Bug#913711: marked as done (firmware-brcm80211: firmware failed to load: NULL pointer dereference with brcmfmac4356)

2021-08-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Aug 2021 08:51:28 +0200 with message-id and subject line Re: firmware-brcm80211: firmware failed to load: NULL pointer dereference with brcmfmac4356 has caused the Debian Bug report #913711, regarding firmware-brcm80211: firmware failed to load: NULL pointer

Bug#993000: linux: please enable CONFIG_VFIO_FSL_MC on arm64

2021-08-26 Thread russm
Source: linux Severity: normal X-Debbugs-Cc: russm-debian-b...@slofith.org Dear Maintainer, Please enable CONFIG_VFIO_FSL_MC=m on arm64 to allow passthrough of fsl-mc network devices to VMs. Thanks -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500,

Bug#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners

2021-08-26 Thread Martin-Éric Racine
$ lsusb Bus 002 Device 019: ID 8564:4000 Transcend Information, Inc. microSD/SD/CF UHS-II Card Reader [RDF8, RDF9] Bus 002 Device 018: ID 076b:1021 OmniKey AG CardMan 1021 Bus 002 Device 017: ID 05e3:0605 Genesys Logic, Inc. Hub Bus 002 Device 020: ID 04a9:2220 Canon, Inc. CanoScan LIDE 25 Bus 002

Bug#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners

2021-08-26 Thread Martin-Éric Racine
They are supported by the kernel. They work just fine as WiFi dongles. They simply are NOT scanning devices. SANE makes the wrong assumption. This has NOTHING to do with the kernel. to 26. elok. 2021 klo 8.58 Jörg Frings-Fürst (debian@jff.email) kirjoitti: > > reassign 983332 linux-signed-amd64

Processed: Re: Bug#983332: sane-utils: incorrectly identifies Wifi USB dongles as scanners

2021-08-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 983332 linux-signed-amd64 Bug #983332 [sane-utils] sane-utils: incorrectly identifies Wifi USB dongles as scanners Bug reassigned from package 'sane-utils' to 'linux-signed-amd64'. No longer marked as found in versions