Package: src:linux
Version: 6.1.76-1
Severity: normal
X-Debbugs-Cc: da...@balch.co.uk
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I am trying to get WoWLAN working on an old DELL via a PCIe WiFi card (
Hello!
Could I please request bumping + optimally official backport to
bookworm? It would be very useful for our Mesa3D CI builds!
Thank you for your work!
David
--
David Heidelberg
Le 22/01/2024 à 13:49, Erwan David a écrit :
Le 23/12/2023 à 21:26, Erwan David a écrit :
Le 19/12/2023 à 19:34, Diederik de Haas a écrit :
On Tuesday, 19 December 2023 19:16:33 CET Erwan David wrote:
Same behaviour with 6.6.3-1 from experimental (that's what apt gave
me,
maybe tomoroow
Le 23/12/2023 à 21:26, Erwan David a écrit :
Le 19/12/2023 à 19:34, Diederik de Haas a écrit :
On Tuesday, 19 December 2023 19:16:33 CET Erwan David wrote:
Same behaviour with 6.6.3-1 from experimental (that's what apt gave me,
maybe tomoroow the 6.6.4).
Either your APT cache should be updated
Le 19/12/2023 à 19:34, Diederik de Haas a écrit :
On Tuesday, 19 December 2023 19:16:33 CET Erwan David wrote:
Same behaviour with 6.6.3-1 from experimental (that's what apt gave me,
maybe tomoroow the 6.6.4).
Either your APT cache should be updated or you're using a mirror which is
rather
them by generating work for many people and potentially
new upgrade problems for everyone – or if we declare them, existing or
not, a non-issue at least for the upgrade to trixie.
And on a sidenote: I would advise to reconsider interacting with dpkg
too casually – but luck is probably on your side in any case.
Best regards
David Kalnischkies
signature.asc
Description: PGP signature
exhibit the
required setup).
(I will write another mail in another subthread about the finer details
of what interacting with dpkg in an upgrade means and what might be
problematic if you aren't careful – in general, not just with aliasing)
Best regards
David Kalnischkies
signature.asc
Description: PGP signature
Le 19/12/2023 à 09:10, Salvatore Bonaccorso a écrit :
Control: tags -1 + moreinfo
On Tue, Dec 19, 2023 at 08:49:45AM +0100, Erwan David wrote:
Package: src:linux
Version: 6.5.13-1
Severity: important
On a Dell Latitude 7490, with 1 intergated e1000e nic, and an extrenal Dock
with Realtek8153
Package: src:linux
Version: 6.5.13-1
Severity: important
On a Dell Latitude 7490, with 1 intergated e1000e nic, and an extrenal Dock
with Realtek8153. If ethernet on one of those NICs is
connected at boot, it runs OK. However, if a NIC is connected to network while
the kernel runs (or when
Package: firmware-misc-nonfree
Version: 20230625-1
Severity: wishlist
Dear Maintainer,
would be lovely to have a firmware-misc-nonfree based on architecture.
Multiple of these firmwares are bound to arm64, x86_64 or other archs.
Installing them for example in the CI for x86_64 leads to needing
As well as the fixes in 6.6, we also need this patchup series here:
https://lore.kernel.org/linux-media/ZWibhE350L3BTRK8@gallifrey/T/#t
These seem to make it pretty nicely.
--
-Open up your eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running
--
-Open up your eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux | Happy \
\dave @ treblig.org | | In Hex /
\ _|_ http://www.treblig.org |___/
Le 07/10/2023 à 10:45, Diederik de Haas a écrit :
On Saturday, 7 October 2023 10:26:05 CEST Erwan David wrote:
Package: src:linux
Version: 6.5.3-1
Severity: important
After the computer went to sleep, I get no wifi, journalctl shows a crash of
iwlwifi with a NULL pointer dereference
Package: src:linux
Version: 6.5.3-1
Severity: important
After the computer went to sleep, I get no wifi, journalctl shows a crash of
iwlwifi with a NULL pointer dereference
here are the logs :
oct. 07 10:09:03 maine-ocean kernel: iwlwifi :00:14.3: Failed to load
firmware chunk!
oct. 07
fter reverting commit 8ee39ec479147e29af704639f8e55fce246ed2d9 and
building it again, booting went fine. Hope it helps.
Regards,
David
the laptop into this email.
Regards,
David
[0.00] microcode: microcode updated early to revision 0xf4, date =
2023-02-23
[0.00] Linux version 6.1.0-12-amd64 (debian-kernel@lists.debian.org)
(gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1
SMP PREEMPT_DYNA
Patch is included in recent stable release, available in unstable. Until
it gets into testing, this should help:
$ apt install -t unstable linux-image-amd64
I assume the bug can be closed.
David
On 18/08/2023 04:42, David wrote:
Version: 6.4.4-3
Hello,
1. the bug is still present
2
Package: linux-headers-6.4.0-3-amd64
Version: 6.4.11-1
Severity: normal
At install time I get following error, which prevents installation (and yes I
need virtualbox)
Setting up linux-headers-6.4.0-3-amd64 (6.4.11-1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation
Version: 6.4.4-3
Hello,
1. the bug is still present
2. Dell XPS 9310 is also affected.
It's still not included in stable series, but got merged into for-next
branch already [1].
Please apply.
Thank you
David
[1] https://www.spinics.net/lists/alsa-devel/msg163701.html
On Sat, 29 Jul
Package: linux-headers-amd64
Version: 6.1.38-2
Severity: important
X-Debbugs-Cc: d...@forkbox.net
Dear Maintainer,
It looks like linux-headers-amd64 6.1.38-3 depends on
linux-headers-6.1.0-11-amd64 (=6.1.38-3), which makes sense.
Unfortunately, the only version of linux-headers-6.1.0-11-amd64
ASAP ;)
Cheers,
--
David
On 4/3/23 9:24 AM, Stephen Hemminger wrote:
> ted
>>
>> This happens because iproute2 just assumes the tunnel is ipv4, but the
>> kernel "knows" it's actually ip6gre so when calling the SIOCGETTUNNEL
>> ioctl it writes back a struct ip6_tnl_parm2 into the struct
>> ip_tunnel_parm which is smaller,
:00.0: failed to init core: -110
[ 27.036908] ath11k_pci: probe of :04:00.0 failed with error -110
David
-Original Message-
From: Cyril Brulebois
Sent: Wednesday, March 1, 2023 3:23 AM
To: 1032...@bugs.debian.org
Cc: David Ober ; Steve McIntyre ;
debian-kernel@lists.debian.org
Subject
Test worked as you expected the network card driver looks to be enabled but
cannot load firmware. I can test if you want or you can wait until the next
formal build
David
-Original Message-
From: Cyril Brulebois
Sent: Tuesday, February 28, 2023 4:41 PM
To: David Ober ; 1032
Happy to test it
David
-Original Message-
From: Cyril Brulebois
Sent: Tuesday, February 28, 2023 12:52 PM
To: Steve McIntyre ; 1032...@bugs.debian.org
Cc: David Ober ; debian-kernel@lists.debian.org
Subject: [External] Re: Bug#1032140: Lenovo Z16 Install issue
Hi David,
and thanks
iommu
2) some v4l tools can use an mmap interface rather than the read(2)
interface; that seems to be OK.
Dave
--
-Open up your eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux | Happy \
\dave @ treblig.org
I sent this upstream report:
https://lore.kernel.org/linux-iommu/Y9qSwkLxeMpffZK%2F@gallifrey/T/#u
--
-Open up your eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux | Happy \
\dave @ treblig.org
Confirmed still happens on upstream 6.2.0-rc6
--
-Open up your eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux | Happy \
\dave @ treblig.org | | In Hex
open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux | Happy \
\dave @ treblig.org | | In Hex /
\ _|_ http://www.treblig.org |___/
050033
[ 78.988346] CR2: bd7fc110 CR3: 00022ce02000 CR4: 06e0
--
-Open up your eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux | Happy \
\dave @ treblig.org | |
U related
and device related.
--
-Open up your eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux | Happy \
\dave @ treblig.org | | In Hex /
\ _|_ http://www.treblig.org |___/
Upstream 5.17 works
Upstream 5.18 fails
(with intel_iommu=on)
Let the bisect begin.
--
-Open up your eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux | Happy \
\dave @ treblig.org
This is IOMMU related.
Upstream 6.1 and 5.18 *do* exhibit the bug, but only with intel_iommu=on
where as Debian seems to default it to on.
--
-Open up your eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux | Happy
I built upstream kernels 5.18.0 and 6.1.0 and both of them work for me.
Which makes life much more painful to find.
--
-Open up your eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux | Happy \
\dave @ treblig.org
t's changed from a BUG to a WARN but
back in 5.15 it just worked.
Dave
--
-Open up your eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux | Happy \
\dave @ treblig.org | | In
eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux | Happy \
\dave @ treblig.org | | In Hex /
\ _|_ http://www.treblig.org |___/
Package: src:linux
Version: 6.1.4-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
This was triggered when trying to capture video via a bt878 card using the
Buenas tardes: Tengo el siguiente problema: Mi Pc del programa JUANA
MANSO con software linux debian, no detecta redes wifi. He buscado
soluciones por internet pero solo funcionan temporalmente. Estoy
sospechando que sea la comunicación entre el router y la tarjeta wifi.
Algo parecido pasa con
kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath10k/core.c#n1227
[2]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath10k/core.c#n882
Best regards
David Kalnischkies
signature.asc
Description: PGP signature
Dear Maintainer,
It has been a while, Is there any update on this package? Please consider
packaging it in Debian, It will support more new hardware, Thanks!
Best Regards,
David Liu
发件人: David Liu<mailto:wbsdty...@outlook.com>
发送时间: 2022年5月22日 14:08
收件人: sub...@bugs.debian.org<m
Package: src:linux
Version: 5.10.113-1
Severity: normal
X-Debbugs-Cc: dpchr...@holgerdanske.com
Dear Maintainer,
Please see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001306
David
-- Package-specific info:
** Version:
Linux version 5.10.0-14-amd64 (debian-kernel@lists.debian.org
t's the
first call of virtqueue_add_outbuf() when virtio_balloon initializes.
Maybe something in generic virtio code changed?
--
Thanks,
David / dhildenb
Hello,
The Linux-firmware-nonfree (https://tracker.debian.org/pkg/firmware-nonfree)
has been no update about one year. Please update it.
I have submit a new bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011410.
Thanks!
Hi Diederik
Diederik de Haas schrieb am 07.06.22 um 15:11:
Is this still true with current kernels? At least with 5.10 from Stable, but
preferably with newer ones (evt from stable-backports).
Yes, the problem is still present (even in the latest backportss kernel)
as shown in the attachment.
and it was not recognized. I removed it, and
tried again -- no help. I rebooted. I then continued. When I
insert a USB flash drive into a USB 3.0 port, both ports on that
chipset stopped working.
I do not have sudo configured. I have pasted dmesg(1) output at the
end of this bug report.
David
-- Package
Package: firmware-amd-graphics
Version: 20210818-1
Severity: Normal
thanks
The RX6500XT was released in January. It requires the "beige-goby" line
of firmware files, which were added upstream September of last year [1].
A refresh of the package is needed.
[1]:
Hi!
Any chance we can get this into the bullseye kernel?
Best regards,
David
signature.asc
Description: This is a digitally signed message part
Package: linux-source-4.19
Version: 4.19.232-1
When attempting to build the kernel without enabling CONFIG_BPF_SYSCALL I
run into the following compilation error:
CC arch/x86/kernel/cpu/bugs.o
arch/x86/kernel/cpu/bugs.c: In function 'spectre_v2_select_mitigation':
Package: src:linux
Version: 5.10.92-1
Severity: important
File:
/lib/modules/5.10.0-11-amd64/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
X-Debbugs-Cc: alt.people.davidcal...@gmail.com
Dear Maintainer,
* What led up to the situation?
I upgraded to bullseye
* What exactly did you
ll kinds of non-naive situations. The best
practice for shell scripts is to actually handle errors where they
occur:
command || exit 1
This is not difficult, if that behaviour is desired.
It would be better if Debian policy was modified to be clearer about this.
Kind regards
David
[1] https:
Package: src:linux
Version: 5.10.70-1
Severity: normal
X-Debbugs-Cc: dpchr...@holgerdanske.com
Dear Maintainer,
Please see fowarded message, below.
David
Forwarded Message
Subject: Re: Bug#1001306: mount: exfat filesystem mtime's are wrong
Date: Wed, 8 Dec 2021 18:13:06
Apologies for the multiple messages. I coulda had that all in one:
Here's the commit adding the files to upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtl_bt?id=7118987b2f7aff733573121607bc9640a4880296
On Fri, 30 Jul 2021 at 10:47, David Schmitt
Reading through the docs a bit, I realize that this request should go
to the linux-firmware.git repo instead.
Package: firmware-realtek
Version: 20210315-3
To support the RTL8761B bluetooth chips from realtek, please add the
files as described in
https://www.raspberrypi.org/forums/viewtopic.php?t=294634 .
I can confirm that it enables the device for me.
Thanks in advance,
David
$ sha256sum /lib
ctions which is contained in
initramfs-tools-core.
I am therefore reassign this bug to them.
Best regards
David Kalnischkies
signature.asc
Description: PGP signature
Package: src:linux
Version: 4.19.181-1
Severity: important
Upgraded to latest packages and with Kernel 4.19.0-16 lirc stopped working. It
cannot find /sys/class/rc and fills every second syslog:
Mar 30 00:09:45 supply lircd[296]: lircd-0.10.1[296]: Error: No /sys/class/rc/
devices found
Mar 30
Guten Tag, ich bin David Pearl. Ich möchte etwas mit Ihnen besprechen.
Bitte kontaktieren Sie mich so schnell wie möglich.
I'm running into this bug also, and would love to know how to work around
it.
David Roundy
Package: src:linux
Version: 4.19.160-2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrade to linux-image-4.19.0-13-amd64 makes apcupsd unable to
contact UPS through USB
On Fri, 2020-11-13 at 14:56 +0100, Salvatore Bonaccorso wrote:
> If we are going to enable this for our builds, then we might need to
> check that https://bugzilla.redhat.com/show_bug.cgi?id=1897402 is not
> opened accordingly.
>
> This relates to
>
>
Source: linux
Severity: wishlist
X-Debbugs-Cc: david.schil...@gmx.at
Hi!
Could you please enable CONFIG_SENSORS_AMD_ENERGY as a module. This
provides RAPL energy monitoring on AMD Zen processors and has been
available since kernel 5.8.
Thanks in advance!
Dave
-- System Information:
Debian
> -- Forwarded message --
> From: David Awogbemila
> To: Debian Bug Tracking System
> Cc:
> Bcc:
> Date: Fri, 10 Jul 2020 18:21:14 +
> Subject: linux: Pulling Google Compute Engine Virtual Ethernet Driver into
> Debian
> Source: linux
> Severity
The bug is corrected in 5.7.0-2
On 2020-07-26 18:15, David wrote:
On Mon, 27 Jul 2020 at 09:47, David Christensen
wrote:
On 2020-03-30 02:58, deloptes wrote:
David Christensen wrote:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955329
I updated/ upgraded the system today and whatever broke LUKS when I
'apt-get
On Mon, 27 Jul 2020 at 09:47, David Christensen
wrote:
> On 2020-03-30 02:58, deloptes wrote:
> > David Christensen wrote:
> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955329
>
> I updated/ upgraded the system today and whatever broke LUKS when I
> 'apt-get
On 2020-03-30 02:58, deloptes wrote:
David Christensen wrote:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955329
I updated/ upgraded the system today and whatever broke LUKS when I
'apt-get dist-upgrade' and installed kernel 4.9.0-12-amd64 several
months ago now breaks LUKS when I
with kernel 4.9.0-11-amd64.
The work-around is to boot the only earlier kernel I have available,
4.9.0-9-amd64.
When whatever broke 4.9.0-12-amd64 and now 4.9.0-11-amd64 breaks
4.9.0-9-amd64, my system will be useless.
David
2020-07-26 15:44:55 root@po ~
# time apt-get
Package: src:linux
Version: 5.7.6-1
Severity: normal
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
ineffective)?
* What was the outcome of
Package: initramfs-tools
Version: 0.137
Severity: normal
Dear Maintainer,
update-initramfs fails:
Processing triggers for initramfs-tools (0.137) ...
update-initramfs: Generating /boot/initrd.img-5.2.17+
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed
Package: linux-image-rt-amd64
Version: 4.19+105+deb10u3
Severity: important
Dear Maintainer,
Using the rt kernel packages (4.19.0-8-rt-amd64 or 5.4.0-0.bpo.4-rt-amd64) no
access to
the EFI variables under /sys/firmware/efi/efivars is possible.
With the non-rt kernels, all is fine as shown
with the correct key.
My work-around is to boot the previous kernel. LUKS then works.
David
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
sys_vendor:
product_name:
product_version:
chassis_vendor:
chassis_version:
bios_vendor: Intel Corp.
bios_version
this Debian bug can now be closed as I guess things should be all
good once Linux 5.5 enters unstable.
Thanks,
David
--
David Purton
e: dcpur...@marshwiggle.net
m: 0413 626 862
signature.asc
Description: PGP signature
Package: src:linux
Version: 4.19.67-2+deb10u2
Severity: normal
Dear Maintainer,
The virtio-rng.ko is not present cloud image kernel package:
debian@dm-test1:~$ locate virtio
/usr/lib/modules/4.19.0-6-cloud-amd64/kernel/drivers/virtio
(pc10) 0.0%
I noticed this with the first version of Linux 5.3 to be included into
Testing.
I just upgrade the UEFI BIOS from 1.55 to 1.61 to see if that would make
any difference, but it didn't.
Thanks,
David
-- Package-specific info:
** Version:
Linux version 5.3.0-3-amd64 (debian-kernel
Package: linux
Version: 5.3.7-1
Severity: important
Owner: Salvatore Bonaccorso
Tags: patch
The kernel configuration change from Debian bug 940726 is invalid,
according to Intel: https://bugzilla.kernel.org/show_bug.cgi?id=204237#c15
The options for the SST and SOF drivers for
On 11/10/19 1:05 PM, David Ward wrote:
Unfortunately, this has caused a regression. The SST and SOF drivers
cannot both be enabled for the same Intel platform in the kernel
configuration, according to Intel.
https://bugzilla.kernel.org/show_bug.cgi?id=204237#c15
To clarify, the statement
: Nov 23 2019 00:34:14
I have tested 2 Apache 2.4.X containers, one from Azure, and one from
Bitnami, with the same behaviour.
Greetings, David.
Package: src:linux
Version: 4.19.67-2+deb10u2
Severity: important
Dear Maintainer,
Installing NVMe SSD on Asus UX430UA laptop (SSD is ADATA ZPG SX8200 Pro). Goal
was dual boot Windows 10 (already on drive) and Debian
10. Neither Debian 10 installer nor Deb 10.2 Live USB key
could detect NVMe
Unfortunately, this has caused a regression. The SST and SOF drivers
cannot both be enabled for the same Intel platform in the kernel
configuration, according to Intel.
https://bugzilla.kernel.org/show_bug.cgi?id=204237#c15
As described in the bug, this change causes a loss of sound on the
Package: linux-image-4.19.0-6-amd64
Version: 4.19.67-2+deb10u1
This issue looks like it might be related to #657689, or at least the
symptoms are similar.
Periodically, my network link goes down for ~35 seconds at a time. I
have not been able to determine what traffic pattern or set of other
I found the problem.
5.2.7-1 had
# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
5.2.9-1 had
CONFIG_INTEL_IOMMU_DEFAULT_ON=y
5.2.9-2 has
# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
CONFIG_INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF=y
Only 5.2.7-1 boots on my system.
I can successfully boot
(other
than a diff of /boot/config-5.2.0-2-amd64 and /boot/config-5.0.0-trunk-amd64).
--
David Purton
e: dcpur...@marshwiggle.net
m: 0413 626 862
Is this also happening with 20190502-1 from Sid?
Package: firmware-iwlwifi
Version: 20161130-5
Severity: important
Tags: upstream
After the most recent point release upgrade, performed on a stock Debian Stable
amd64 system with 'apt-get update ; apt-get dist-upgrade', in which the package
firmware-iwlwifi was upgraded to a newer version
Felix Hagemann writes:
> Package: src:linux
> Version: 4.17.17-1
> Followup-For: Bug #906189
>
> Dear Maintainer,
>
> I do see exactly the same behaviour on a Thinkpad X1 Carbon (Gen. 2).
>
I had the same problem on my dell e7270, but it was fixed by a BIOS
upgrade. Something to try?
d
es then we might have an opportunity to make Qt
> upstreams reconsider the issue.
>
> Cheers, Lisandro.
Interesting to note that on a system with sysvinit (and 4.17 kernel) there is
no noticeable delay in sddm startup.
David
I've had the same error happen ("generic_make_request: Trying to write
to read-only block-device "...) when running os-prober through grub on
my basically "wheezy" system. I removed os-prober, to stop having to do
a 12 hour resync of the raid5 array every time I updated the kernel.
Package: src:linux
Version: 4.9.88-1+deb9u1
Severity: normal
Dear Maintainer,
After updating to 4.9.0-6-amd64 nfs mounts fail with these messages:
[ 687.358529] NFS: nfs4_discover_server_trunking unhandled error -5.
Exiting with error EIO
[ 687.364094] gss_marshal: gss_get_mic FAILED (851968)
FWIW, I am also seeing this bug after a recent kernel upgrade. The
laptop is Asus UX303UA.
I enclose the kernel information from reportbug in the attachment.
Also I can confirm that the workaround given above works for me.
--
David Banks <amoe...@gmail.com>
reportbug-kernel-in
ed in code compiled
for no SMP machines (line 160); because of this the
"implicit-function-declaration" error.
Trying your sugestion, upstream 4.9.75 compile without problems: the
tlb.c there has no SMP special code (the header says something about:
"formerly SMP-only"...).
Cheers,
--
David
On Tue, 12 Dec 2017 01:57:48 + Ben Hutchings wrote:
> [This message is bcc'd to all bug reporters.]
>
> Apologies for this regression. Salvatore Bonaccorso has tracked down
> which change in 3.16-stable triggers the crash, and I identified some
> related upstream changes which appear to fix
0 ACCEPT tcp
-- * ens30.0.0.0/00.0.0.0/0tcp
spts:5:50500 ctstate RELATED,ESTABLISHED
[…]
As you can see, iptables is configured to let passive FTP connections
pass, on the same port range than the one configured on the FTP
service:
root@pern /h/david
Package: src:linux
Version: 4.11.6-1
Severity: important
File: nouveau
Dear Maintainer,
I performed a fresh installation from the 2017-07-04 daily d-i netinst on
amd64. After booting into the system, messages appeared on the console /
syslog about task kworker blocked for more than 120 seconds.
sid_nfs-utils_1.3.4-2.debdiff
Description: Binary data
state.
systemd[1]: nfs-mountd.service: Failed with result 'exit-code'.
Nowadays "nfs-mountd.service" uses "BindTo" directive to "nfs-server.service".
That, per se, doesn't guarantee ordering for NFS server to start rpcbind and for
nfs-mountd to depend on it.
https:
the PC
with it perhaps 60 times with no delay like this. However, I upgraded the
kernel to -pae perhaps a couple of weeks ago. There are now 2 HD's on my
PC, one SATA (ata30) and the other a slower PATA with a ribbon cable.
David Lawyer
I haven't received any further notifications on this bug. This has
remained an issue for me for all Linux versions higher than 4.5.
Happy Hacking,
David E. McMackins II
Associate Member, Free Software Foundation (#12889)
www.mcmackins.org www.delwink.com
www.gnu.org www.fsf.org
On 06/18/2016
Package: src:linux
Version: 4.6.2-1
Severity: important
Dear Maintainer,
All of the releases of Linux 4.6 in Debian Sid so far have failed to
mount my primary disk in read-write mode. I have not tested my other XFS
disks, because failure to correctly mount all my OS partitions causes
numerous
On 2/10/2016 11:10 AM, Ben Hutchings wrote:
> Which boot loader are you using?
Grub 2.
> diffoscope (https://try.diffoscope.org/) agrees with that.
>
> This works for me:
>
> kvm -m 1G -kernel /boot/vmlinuz-3.16.0-4-amd64 -initrd
> initrd.img-3.16.0-4-amd64.broken
Huh. This is only
Package: initramfs-tools
Version: 0.120
I have a rather odd case where update-initramfs sometimes generates good
initrds and sometimes it does not. I'm not sure if the bug lies here or
in the kernel, but after sinking hours into investigating this issues
I'm very confident there is a bug
1 - 100 of 820 matches
Mail list logo
