On Sun, 27 Oct 2024 08:37:32 +0100, Salvatore Bonaccorso wrote:
>I uploaded 6.11.5-1 now to unstable. As we were not identifying the
>upstream change fixing the issue, I have manually marked the bug as
>fixed with 6.11.5-1, so once ftp-master accepts it through NEW and
>packages build you should b
Control: tags -1 - moreinfo
I still don't know any examples of an unpaired bluetooth device triggering
dmesg entries at boot time. (If this ever happens with any such device, I
would be interested in knowing how and why.)
But since you asked, I tried it anyway. The device enters pairing mode as
On Wed, 23 Oct 2024 15:46:26 +0200, Salvatore Bonaccorso wrote:
>Do you maybe can share dmesg information from booting with the old
>kernel with the controller available?
Given that we're talking about a wireless controller that is never connected
at boot time, do you expect dmesg to show anythin
Package: src:linux
Version: 6.11.4-1
Severity: normal
X-Debbugs-Cc: fores...@nom.one
Dear Maintainer,
After upgrading from linux-image-6.11.2-amd64 to
linux-image-6.11.4-amd64, my Sony DualShock 4 v2 game controller no
longer connects over bluetooth.
I don't see any messages in dmesg or syslog w
Upstream 6.10.9 does indeed seem to fix it.
Half a dozen runs of my reproducers yielded nothing but correct behavior.
On Sat, 7 Sep 2024 09:54:48 +0200, Salvatore Bonaccorso wrote:
>AFIU, this should be fixed with c26096ee0278 ("mm: Fix
>filemap_invalidate_inode() to use invalidate_inode_pages2_range()")
>upstream, correct?
That patch alone didn't fix the problems reported here, but when combined
with several pr
Reported on the lists:
https://lore.kernel.org/linux-cifs/pv2lcjhveti4sfua95o0u6r4i73r39s...@sonic.net/T/#u
Tracked by regzbot:
https://linux-regtracking.leemhuis.info/regzbot/regression/lore/pv2lcjhveti4sfua95o0u6r4i73r39s...@sonic.net/
Related: a bug in recent 6.11 release candidates that pr
After further testing today, that commit also seems to be (intermittently)
causing ffmpeg and mkvmerge to write corrupt files to cifs mounts.
On Fri, 23 Aug 2024 22:13:07 +0200, Salvatore Bonaccorso wrote:
>Since you identified this as upstream regression including the
>breaking commit, can you
Control: found -1 6.10.4-1
Control: found -1 6.10.3-1
Package: src:linux
Version: 6.10.6-1
Severity: important
X-Debbugs-Cc: fores...@nom.one
Dear Maintainer,
After upgrading from kernel 6.9.12 to 6.10.4, flatpak and ostree are now
writing corrupt gpg signatures when exporting signed packages or signing
their repository metadata/summary files, when
Control: fixed -1 6.8.9-1
On Fri, 17 May 2024 12:15:55 +0200, Diederik de Haas wrote:
>Kernel 6.8.9 has recently been uploaded to Unstable which has that commit.
>Can you verify that it indeed fixes this bug?
Indeed, it seems to be fixed there. It usually takes only one or two boots
to show up,
A git bisect reveals it to be fixed by this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f7a59018953910032231c0a019208c4b0a4a8bc3
> maple_tree: make mas_erase() more robust
>
> mas_erase() may not deal correctly with all maple states. Make the
> function m
Control: fixed -1 linux/6.7.12-1
fixed -1 linux/6.7.12-1
Control: found -1 6.7.12-1
Package: src:linux
Version: 6.7.12-1
Severity: normal
X-Debbugs-Cc: fores...@nom.one
Dear Maintainer,
After upgrading from kernel 6.7.9 to 6.7.12, my DualShock 4 game
controller no longer shows as connected in KDE Plasma.
Contrary to what the GUI says, the device's onboard light seems to
indicat
Note that this is a headless system, so there is no other way to display a
prompt or enter the passphrase.
Just in case this was merely a display problem, I tried entering the
passphrase at the serial console despite the missing prompt. It didn't work.
Package: src:linux
Version: 6.6.15-2
Severity: normal
X-Debbugs-Cc: fores...@nom.one
Dear Maintainer,
When booting with an encrypted root filesystem, the LUKS unlock
passphrase prompt normally appears on the serial console shortly after
the first device-mapper messages. It looks like this:
Ple
Control: found -1 6.6.15-2
On Tue, 16 Apr 2024 10:34:45 +0200, Diederik de Haas wrote:
>Can you try the Debian Testing kernel, which is at version 6.6.15?
6.6.15-2 also has the bug.
Control: retitle es8316 driver causes kernel oops / panic on rockpro64
Blacklisting the snd_soc_es8316 module in /etc/modprobe.d seems to restore
kernel stability, as far as I have seen from half a dozen reboots.
Package: src:linux
Version: 6.7.9-2
Severity: important
X-Debbugs-Cc: fores...@sonic.net
Dear Maintainer,
The current debian unstable kernel causes a variety of failures that are not
present in the bookworm kernel, on the RockPro64 single board computer. (This
is an arm64 machine built upon the R
On Sun, 31 Jul 2022 12:30:42 +0200, Diederik de Haas wrote:
>From the partial logs you shared it appeared that your network also went down
>after (quite) some time,
If you're referring to my 5.14.0-1 kernel log, I can't offer any insight, as
I only tried that kernel briefly, nearly a year ago.
Control: found -1 5.10.127-2
Control: notfound -1 5.18.14-1
Control: tags -1 - moreinfo
On Sat, 30 Jul 2022 00:19:25 +0200, Diederik de Haas wrote:
>Is this problem still present with a recent 5.10 or (better yet) the 5.18.14
>kernel from Unstable?
It is still present in recent 5.10 kernels.
5
Control: tags -1 - moreinfo
>Could you try with the current kernel in unstable?
>We are at 5.14.6-2, which had some rk3399 related changes.
Did any of those changes arrive after 5.14.0-1? If so, I suppose I would
have to wait for a newer debian kernel to appear before I could test it.
With 5.1
ehci_platform
ehci_hcd
ptp
sdhci_of_arasan
usbcore
sdhci_pltfm
phy_rockchip_emmc
cqhci
phy_rockchip_pcie
phy_rockchip_typec
phy_rockchip_inno_usb2
sdhci
pps_core
dw_mmc_rockchip
dw_mmc_pltfm
spi_rockchip
i2c_rk3x
usb_common
dw_mmc
** Network interface configuration:
*** /etc/network/interfaces:
# This
Thanks, Guilhem.
Is anything more needed from me to get this fixed?
Problem also exists on my QNAP TS-119P+ running Debian 8.2 (jessie).
I would check my Wake on LAN and Energy-using Products settings if I knew
how. /usr/sbin/qcontrol doesn't seem to have an option for reporting the
current settings.
27 matches
Mail list logo
