Bug#1026259: Status

2023-02-03 Thread RattusRattus
Dear team, - Did I submit to the correct location? - Is there anything additional information that you require? BR -- /RattusRattus Debian is not always the answer, however it is surprising how many times it is...

Did you see this article?

2023-02-03 Thread Julie Schumer
Hello Debian, Did my previous email get through?  We wrote a guide about how drugs affect children at all stages of development. The guide could fit on your website. Here's the link - https://www.toprehabs.com/drug-effects-on-children/ Let me know if your readers would gain something from the

Bug#1029684: disabling xhci prevents kernel warning

2023-02-03 Thread Peter Nagel
I found that the kernel warning disappears when I prevent the modules *xhci_pci* and *xhci_hcd* from being loaded during boot.

firmware-nonfree: XS-Autobuild whitelisting might need updating for non-free-firmware

2023-02-03 Thread Adrian Bunk
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#marking-non-free-packages-as-auto-buildable https://buildd.debian.org/status/logs.php?pkg=firmware-nonfree&arch=all https://buildd.debian.org/status/package.php?p=firmware-nonfree "Section: contrib/misc" at the latter URL looks very

Re: firmware-nonfree: XS-Autobuild whitelisting might need updating for non-free-firmware

2023-02-03 Thread Philipp Kern
On 03.02.23 16:50, Adrian Bunk wrote: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#marking-non-free-packages-as-auto-buildable https://buildd.debian.org/status/logs.php?pkg=firmware-nonfree&arch=all https://buildd.debian.org/status/package.php?p=firmware-nonfree "Section: co

Bug#1029968: Info received (Bug#1029968: Info received (Bug#1029968: Info received (Bug#1029968: Acknowledgement (bttv/v4l: WARNING: CPU: 6 PID: 6164 at mm/vmalloc.c:487 __vmap_pages_range_noflush+0x3

2023-02-03 Thread Dr. David Alan Gilbert
It's a bit messy... a) The patch I bisected to is not the root cause of the bug; it just triggers a ~9 year old bug in the v4l code - so this patch isn't going to get changed. b) The ~9 year old bug is in a particularly hairy piece of memory management code in v4l that I doubt anyone is going to