Package: curl
Version: 7.88.1-10+deb12u3
Severity: normal
Tags: ipv6
X-Debbugs-Cc: t...@security.debian.org
We use curl as a health check in our keepalived setup. We basically run the
following curl command:
curl 'ldap://[2a02:2c40:0:a412::389:389]'
This works fine in 7.88.1-10+deb12u1, but
Source: pcs
Version: 0.11.5-1
Severity: important
Tags: upstream patch
Hi,
I've set up a pacemaker cluster using pcs on Debian 12. When trying to
move a resource from one node to the next, this fails with a python
error:
Traceback (most recent call last):
File "/usr/sbin/pcs",
Package: iputils-ping
Version: 3:20221126-1
Severity: normal
Hi,
After upgrading our monitoring host from bullseye to bookworm, our
check_ping plugin suddenly reports that hosts that have been down for
months are up again for a few minutes.
I've looked into this and it seems we are running so
Package: autofs
Version: 5.1.8-2
Severity: minor
Dear Maintainer,
When running "automount -m" to debug the maps used by autofs, I noticed that
this triggers segfaults as can be seen in 'dmesg':
[Wed Jun 14 08:05:38 2023] automount[9026]: segfault at 8 ip 7f5d6f3d4d19
sp 7ffd202ac5d8
Swap: 758060 kB
SwapPss: 758060 kB
Locked: 0 kB
VmFlags: rd wr mr mw me ac sd
Any ideas on how to further debug this are very welcome.
Regards,
Rik
--
Rik Theys
System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10 bus 2440 - B-3001
Hi,
It seems the newer upstream releases 2.2.11 and 2.2.12 fix memory issues:
https://github.com/apple/cups/releases/tag/v2.2.11
https://github.com/apple/cups/releases/tag/v2.2.12
Would it be possible to backport those fixes to the Debian package?
Regards,
Rik
--
Rik Theys
System Engineer
Package: cups
Version: 2.2.10-6+deb10u1
Severity: important
Hi,
After upgrading our print server from Debian 9 to 10, we frequently get
notified by our monitoring system that the server is running out of
memory.
It seems there's a memory leak in cupsd. The memory usage starts at
about 3.8% and
Package: dnsmasq
Version: 2.76-5
Followup-For: Bug #863896
This issue seems to be caused by the recent upgrade of the dns-root-data
package. The root.ds file in this new package contains two records where
the previous version (2015052300+h+1) only had one record.
The old version was also
Package: davical
Version: 1.1.5-1
Severity: important
Dear Maintainer,
When the configuration contains an LDAP mapping for the modified field
to modifyTimestamp,
davical fails to create a new user as there's an error in the code that
does the mapping.
The outcome is that the user is not created
Package: obnam
Version: 1.19.1-1
Severity: minor
Hi,
Running 'obnam list-errors' produces a list of error messages and then crashes
with the following python traceback:
`EncryptionError` (`RD88CFX`)
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/cliapp/app.py",
Hi,
Looking at the samba changelog this bug should be fixed in the 4.1.18
release.
Would it be possible to backport this fix into the jessie package?
Regards,
Rik
--
Rik Theys
System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10 bus 2440 - B-3001 Leuven-Heverlee
Package: samba
Version: 2:4.1.17+dfsg-2+deb8u2
Severity: important
Tags: patch
Hi,
After upgrading our print server from Wheezy to Jessie, windows clients
can no longer connect to some of our printers. These printers have
drivers available on the print server.
The following error is logged for
Hi,
On 01/18/2016 11:46 PM, Martin Michlmayr wrote:
> * Rik Theys <rik.th...@esat.kuleuven.be> [2016-01-18 20:15]:
>> When a preseed file is used to enable SSH access to the installer, the
>> local user can still interfere with the installation process by using
Package: debian-installer
Severity: wishlist
Hi,
When a preseed file is used to enable SSH access to the installer, the
local user can still interfere with the installation process by using
the local console.
It would be nice to have an option to disable local interaction with
the installer, so
likely.)
In our environment we have systems managed centrally and systems managed
by research groups but they share the same dns domain. I don't think
they would appreciate it if their systems suddenly started to contact
our puppet server :-).
Regards,
Rik
--
Rik Theys
System Engineer
KU
Hi,
I've had a similar issue with Fedora's 3.17 kernel and indeed it was
fixed after an upgrade to 3.18.
If Jessie has the same bug, I agree it should best be fixed prior to its
release.
As a workaround on the 3.17 kernel I started the RPC idmapd service.
This service is normally no
Hi,
On Sat, 21 Feb 2015, Stig Sandbeck Mathisen wrote:
Rik Theys rik.th...@esat.kuleuven.be writes:
During an upgrade from wheezy to jessie, puppet was upgraded to 3.7.2
and systemd became the default init system.
When jessie is released, an upgrade should keep the current init system.
I
Package: puppet
Version: 3.7.2-2
Severity: grave
Tags: patch security
Justification: user security hole
Hi,
During an upgrade from wheezy to jessie, puppet was upgraded to 3.7.2 and
systemd
became the default init system.
In our environment, our puppet master is not called puppet and we
Package: linux-tools-3.16
Version: 3.16-3
Severity: wishlist
Hi,
Would it be possible to include the x86_energy_perf_policy and turbostat tool
on x86 builds of linux-tools?
It allows you to set the x86 performance policy of the CPU, and a tool to
monitor the CPU states of recent intel
Package: src:linux
Version: 3.16.7-ckt4-3
Severity: normal
Hi,
I was playing with the x86_energy_perf_policy tool to change the energy
performance policy of the CPU.
When the system boots, it indicates it has switched the CPU to the 'normal'
perf_policy (from 'performance').
[0.011281]
found 777165 3.18.5-1~exp1
forwarded 777165 https://bugzilla.kernel.org/show_bug.cgi?id=92871
stop
This bug is also present in the 3.18 kernel from experimental. I've also
tested this on 3.19-rc7 and it also has this bug.
I filed an upstream bug at
Hi,
On Fri, Feb 6, 2015 at 6:57 AM, Jérôme Deuchnord debian-li...@deuchnord.tk
wrote:
I have the same problem, and wrote a bug, but nobody answered me:
https://lists.debian.org/20150131113439.1239.79224.reportbug@JeromeTanghe-Debian
The screen on the photo doesn't say the same thing, but
Hi,
This bug looks like a similar bug in the RHEL bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=1086058
Regards,
Rik
Package: src:linux
Version: 3.16.7-ckt4-3
Severity: normal
Hi,
I enabled nested virtualisation on the kvm_intel module and
created a virtual machine (using virt-manager). The VM had the host cpu flags
copied so it also had the vmx cpu flag.
Inside this VM I configured another virtual machine
Package: general
Severity: normal
Hi,
I was thus far unable to pinpoint which component causes this behaviour as I can
not find anything in my logs (and/or journal). I have therefore assigned it
to general. Feel free to change to a more appropriate package.
I'm using KDE on Jessie with gdm3 as
Package: src:linux
Version: 3.14.12-1
Severity: wishlist
Hi,
If the 3.14 kernel will be the kernel for Jessie, please consider backporting
support for the Dell PowerEdge VRTX storage.
Support for this was first introduced with the 3.15 kernel in the following
commit:
Package: libmount1
Version: 2.20.1-5.5
Severity: normal
Dear Maintainer,
I use systemd as init. Sometimes during boot-up systemd spawns the emergency
shell because it failed to mount my /home (which is on LVM on MD raid).
According to the log file this is because the file system was already
Hi,
I've created a bug report in the freedesktop.org bug tracker:
https://bugs.freedesktop.org/show_bug.cgi?id=72282
Regards,
Rik
On Thu, Nov 28, 2013 at 10:54 AM, Rik Theys rik.th...@gmail.com wrote:
Hi,
Thanks for investigating this!
Please forward the bug upstream.
Regards,
Rik
Hi,
Thanks for investigating this!
Please forward the bug upstream.
Regards,
Rik
On Wed, Nov 27, 2013 at 9:41 PM, Michael Stapelberg
stapelb...@debian.orgwrote:
control: tags -1 + upstream
Hi Rik,
Rik Theys rik.th...@gmail.com writes:
The complete command line is:
$ cat /proc
reopen 729805
thanks
Hi Michael,
On Sun, Nov 17, 2013 at 8:43 PM, Michael Biebl bi...@debian.org wrote:
Am 17.11.2013 16:34, schrieb Rik Theys:
To show the systemd startup messages (OK Starting/started/...), I added
systemd.show_status=1 to /etc/default/grub and updated the grub config
Hi,
The complete command line is:
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.11-2-amd64 root=/dev/mapper/vg_earth-root ro
elevator=deadline init=/bin/systemd systemd.show_status=1
acpi_backlight=vendor acpi_osi=Linux quiet
On Fedora:
$ cat /proc/cmdline
Package: src:linux
Version: 3.11.6-2
Severity: normal
Hi,
I received the following WARNING in my kernel messages:
[ 846.633954] WARNING: CPU: 0 PID: 553 at
/build/linux-iRt5Ta/linux-3.11.6/net/ipv4/tcp_input.c:2711
tcp_fastretrans_alert+0xb72/0xba0()
[ 846.633955] Modules linked in:
Hi,
I've experienced similar behaviour since the 3.9 kernels on my Dell Latitude
6530
Adding the following kernel parameter to the grub boot line has
dramatically reduced the latency for me:
acpi_backlight=vendor
It might also make a difference for you.
Regards,
Rik
--
To UNSUBSCRIBE,
Hi Marc,
I'm experiencing similar behaviour on my Dell Latitude E6530: updating
the brightness blocks (mouse) input and is very slow.
Adding 'acpi_backlight=vendor' to the kernel parameters has helped a lot
on my system to make the brightness updates less slow. It's still slower
than it used to
a way of (reliably) triggering this bug?
Regards,
Rik
--
Rik Theys
System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10 bus 2440 - B-3001 Leuven-Heverlee
+32(0)16/32.11.07
Any errors in spelling, tact
Package: intel-microcode
Version: 1.20120606.v2.2
Severity: important
Hi,
After upgrading one of our servers from Squeeze to Wheezy, we noticed the cpu
microcode
was no longer being upgraded. The kernel messages indicated the needed
microcode file
was not found:
57360.773761] platform
Hi,
We had another system triggering this same BUG which did not come out of
resume/hibernate, so the hibernation/suspend does not seem relevant.
Although the issue seems to be a lot easier to hit when using
hibernate/suspend.
Regards,
Rik
--
To UNSUBSCRIBE, email to
Package: src:linux
Version: 3.2.35-2~bpo60+1
Severity: normal
Hi,
When our NFSv4 client is resumed from hibernate, it logs the following message:
NFS: nfs4_reclaim_open_state: Lock reclaim failed!
After a while (15 min up to 2 hours) the following BUG is triggered:
Jan 22 09:13:47 bax kernel:
which was filed against the bind9 package:
#697681: bind9: DNSSEC validating resolver spams log file after
upgrade to 9.8.4
It has been closed by LaMont Jones lam...@debian.org.
--
Rik Theys
System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10 bus 2440 - B-3001
Hi,
Sorry, disregards this message. I missed your upload to unstable.
Thanks for fixing this!
Regards,
Rik
On 01/10/2013 08:48 AM, Rik Theys wrote:
Hi,
Thanks for fixing this. Would it be possible to also fix this bug in a
9.8.4 upload directed for Wheezy? Maybe using testing-proposed
:
This is an automatic notification regarding your Bug report
which was filed against the bind9 package:
#697681: bind9: DNSSEC validating resolver spams log file after upgrade to 9.8.4
It has been closed by LaMont Jones lam...@debian.org.
--
Rik Theys
System Engineer
KU Leuven - Dept. Elektrotechniek
Package: bind9
Version: 1:9.8.4.dfsg.P1-1
Severity: important
Hi,
After upgrading bind to 9.8.4 (now in testing) on our DNSSEC validating
resolvers, our log files are being spammed with the following messages:
Jan 8 12:06:06 sulphur named[26473]: RSA_verify failed
Jan 8 12:06:06 sulphur
Hi,
On 12/07/2012 09:48 AM, Rik Theys wrote:
Hi,
On 12/06/2012 02:51 PM, Ben Hutchings wrote:
On Thu, 2012-12-06 at 13:58 +0100, Rik Theys wrote:
On 12/06/2012 01:29 PM, Ben Hutchings wrote:
It is not too difficult to fix up the conflicts. But this is a
fairly
big change, so I think
Hi,
On 12/06/2012 02:51 PM, Ben Hutchings wrote:
On Thu, 2012-12-06 at 13:58 +0100, Rik Theys wrote:
On 12/06/2012 01:29 PM, Ben Hutchings wrote:
It is not too difficult to fix up the conflicts. But this is a fairly
big change, so I think this bug should now be 'wontfix' for wheezy.
Sorry we
Hi,
On 12/01/2012 11:10 PM, Ben Hutchings wrote:
On Fri, 2012-11-30 at 11:10 +0100, Rik Theys wrote:
[...]
I cherry picked commits 5ef30ee53b187786e64bdc1f8109e39d17f2ce58 and
5195d8e217a78697152d64fc09a16e063a022465 and tried to compile the
result, but it failed with the following error
running, so extra names aren't cheap.
What would you consider the upper limit to which we could increase the
number? Just so I know at which limit I can stop building test kernels.
Regards,
Rik
--
Rik Theys
System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10 bus
Hi,
On 11/30/2012 08:18 AM, Rik Theys wrote:
On 11/29/2012 01:10 PM, Rik Theys wrote:
On 11/25/2012 01:12 AM, Jonathan Nieder wrote:
On some of our servers, we periodically see name_count maxed,
losing inode data messages in the kernel log.
As you mentioned, this is said to be fixed
this as this is a production system and I did
not plan on rebooting the system before the end of January. I'll see if
I can squeeze in a reboot somewhere.
Regards,
Rik
--
Rik Theys
System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10 bus 2440 - B-3001 Leuven-Heverlee
+32(0)16
On 11/29/2012 01:10 PM, Rik Theys wrote:
On 11/25/2012 01:12 AM, Jonathan Nieder wrote:
On some of our servers, we periodically see name_count maxed,
losing inode data messages in the kernel log.
As you mentioned, this is said to be fixed by
commit 5195d8e217a7
Author: Eric Paris epa
Package: mount
Version: 2.20.1-5.2
Severity: normal
Hi,
When bind mounts are configured in /etc/fstab, they don't show up as bind
mounts in the
output of 'mount'.
From my /etc/fstab:
/dev/mapper/vg_sulphur-root / ext4errors=remount-ro 0 1
/dev/mapper/vg_sulphur-bind
Hi Seth,
On Tue, Jul 10, 2012 at 6:57 AM, Seth Forshee
seth.fors...@canonical.com wrote:
On Tue, Jul 10, 2012 at 12:16:27PM +0800, littlebat wrote:
3, If you are interest in this and have time and it is helpful, I can
provide a root password for this laptop to you and run ssh service for
you
Hi,
On Fri, Jul 6, 2012 at 12:19 AM, Vincent Lefevre vinc...@vinc17.net wrote:
On 2012-07-04 20:55:56 +0200, Rik Theys wrote:
Vincent Lefevre wrote:
When I want to restart (reboot) my Dell Latitude E6400 laptop, the
machine sometimes remain on without restarting. The last message
Hi,
I believe this is the same bug as launchpad bug 606238:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606238
The bug discusses various Dell laptops with ALPS touchpad that don't
work. They now work in the ubuntu 12.04 kernel (and I believe upstream
as well), but some (such as the one
Hi,
Vincent Lefevre wrote:
When I want to restart (reboot) my Dell Latitude E6400 laptop, the
machine sometimes remain on without restarting. The last message
on the console is: Restarting system.
Can you try adding the following parameter to your kernel boot line?
Add it to the
On 06/29/2012 10:31 PM, micah anderson wrote:
After getting the go ahead from the maintainers, I uploaded
dovecot-antispam and dovecot2 to BPO yesterday. Because dovecot-antispam
is already in BPO, it was accepted right away, the dovecot2 packages are
waiting in NEW.
The dovecot-antispam
: [2572005.811051] freeradius[31179]: segfault
at c ip b735e328 sp bfdf4d10 error 4 in rlm_eap-2.1.10.so[b735a000+6000]
Jun 14 15:21:49 vm075144 kernel: [2572570.522135] freeradius[8368]: segfault at
c ip b7311328 sp bfe97bd0 error 4 in rlm_eap-2.1.10.so[b730d000+6000]
El 05/06/12 10:20, Rik Theys escribió
Hi,
On 06/07/2012 11:22 PM, Ben Hutchings wrote:
On Tue, Jun 05, 2012 at 09:05:42AM +0200, Rik Theys wrote:
I have seen similar crashes with the 6.0.x kernel on some of our
systems. Unfortunately the systems are in a remote location and I
was unable to capture any crash screens
reassign 675621 linux-2.6
thanks
Hi,
I have seen similar crashes with the 6.0.x kernel on some of our
systems. Unfortunately the systems are in a remote location and I was
unable to capture any crash screens.
I installed the 3.2 kernel from squeeze-backports on those systems and
that fixed
Hi,
I manually created a patch for this commit (see attach). I also applied
the patch to the latest Debian package. You can find a build for amd64
at http://homes.esat.kuleuven.be/~rtheys/freeradius.
I have not tested the resulting package, but the patch applied cleanly
and there were no
Hi,
With the freeze in a few weeks, I'm wondering if you would still
consider applying the following patches to the Wheezy kernel:
NFSv4: Further reduce the footprint of the idmapper
commit 685f50f9188ac1e8244d0340a9d6ea36b6136cec
NFSv4: Reduce the footprint of the idmapper
commit
Hi,
On 05/12/2012 11:32 PM, Ben Hutchings wrote:
On Sat, 2012-05-12 at 16:25 -0500, Jonathan Nieder wrote:
Ben Hutchings wrote:
Which shows that the segfault is always at the same code address:
[ 56.663596] lvm[540]: segfault at ff600400 ip ff600400 sp
7fff25461ec8
Hi,
On 05/14/2012 10:52 AM, Ben Hutchings wrote:
On Mon, 2012-05-14 at 08:48 +0200, Rik Theys wrote:
Hi,
On 05/12/2012 11:32 PM, Ben Hutchings wrote:
On Sat, 2012-05-12 at 16:25 -0500, Jonathan Nieder wrote:
Ben Hutchings wrote:
Which shows that the segfault is always at the same code
Hi,
On 05/10/2012 02:56 PM, Rik Theys wrote:
So, the Save owner/group name string is the most efficient way of
ensuring that the open works as expected, and it should be a fairly
self-contained patch.
There is an alternative solution, which is much shorter (and therefore
appropriate for stable
Hi,
On 05/10/2012 05:08 PM, Jonathan Nieder wrote:
I looked at the 2.6.32-44 kernel source to see if the simple fix
Trond suggested can be applied there as well, but I fail to find the
context where the extra line could be needed.
Here's a patch to try against 2.6.32.y.
Hope that helps,
Hi,
On 05/09/2012 04:34 PM, Myklebust, Trond wrote:
Can you please comment on wether additional fixes and/or
dependencies are needed to backport the patch below to the Debian
3.2 kernel?
So, the Save owner/group name string is the most efficient way of
ensuring that the open works as
Hutchings wrote:
On Tue, 2012-04-24 at 22:04 +0200, Rik Theys wrote:
Hi,
I'm experiencing the bug described in the Debian[1] and Red Hat[2] bug tracker.
This bug seems to have been fixed in the 3.3 kernel with your commit
6926afd1925a54a13684ebe05987868890665e2b:
From: Trond
Hi,
On Tue, 8 May 2012, Jonathan Nieder wrote:
Hi Trond,
Can you please comment on wether additional fixes and/or
dependencies are needed to backport the patch below to the Debian
3.2 kernel?
The Debian kernel maintainers would prefer some feedback before
applying the fix to their 3.2 kernel.
Package: linux-2.6
Version: 3.2.15-1~bpo60+1
Severity: important
Hi,
It seems stable update 3.2.14 or 3.2.15 introduced a regression regarding NFS4
delegations.
It seems to be the same issue as reported here[1] against the 3.3 kernel. It
was also intruduced
there between 3.3.0 and 3.3.1.
[1]
Hi Jonathan,
On Thu, 26 Apr 2012, Jonathan Nieder wrote:
Rik Theys wrote:
It seems stable update 3.2.14 or 3.2.15 introduced a regression regarding NFS4
delegations.
It seems to be the same issue as reported here[1] against the 3.3 kernel. It
was also intruduced
there between 3.3.0
or not these get applied in the stable tree (which would be
nice if it can be justified), I think we definitely want them in
Debian, so cloning the bug to track that.
I agree! (but I'm biased).
Regards,
Rik
--
Rik Theys
Senior System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark
Hi,
On 04/24/2012 11:16 PM, Jeff Layton wrote:
On Tue, 24 Apr 2012 13:35:13 -0700
Greg KHgre...@linuxfoundation.org wrote:
On Tue, Apr 24, 2012 at 10:22:50PM +0200, Rik Theys wrote:
Hi,
I'm experiencing the following Red Hat bug[1] on RHEL and also on
Debian.
I've noticed Fedora has
Hi,
On 04/25/2012 03:14 AM, Ben Hutchings wrote:
On Tue, 2012-04-24 at 22:04 +0200, Rik Theys wrote:
Hi,
I'm experiencing the bug described in the Debian[1] and Red Hat[2] bug tracker.
This bug seems to have been fixed in the 3.3 kernel with your commit
the patch be part of a stable update to consider it.
Regards,
Rik
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659111
[2] https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=789298
--
Rik Theys
Senior System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10
B
these patches in a stable 3.2 update (and/or 3.0.x) so they
will become part of the upcoming Debian 7.0 kernel (which is based
on 3.2).
Have these patches made it into the 3.3 and/or 3.4-rc kernels?
Regards,
Rik
--
Rik Theys
Senior System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark
Package: bind9
Severity: wishlist
Hi,
Please consider packaging the new upstream 9.9 release for sid/wheezy.
It has some new features that make rolling out DNSSEC easier (such as
inline signing).
Regards,
Rik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
Hi,
On 03/21/2012 06:39 PM, Jonathan Nieder wrote:
Rik Theys wrote:
Can this commit be backported to the 3.2 kernel in sid?
It applies and I have tested it in the past against the 3.2.4 kernel.
Just for the record: we are talking about
v3.3-rc1~116^2~1 NFSv4: Save the owner/group name
Hi Jonathan,
On 03/22/2012 04:16 PM, Jonathan Nieder wrote:
It seems it's not only lvm that segfaults, but also ls etc in the
initramfs.
Thanks. Are symptoms tied to the version of initramfs-tools or one of
its dependencies, or to the kernel version? E.g., if you install
another kernel or
Hi,
On 03/21/2012 05:27 PM, Jonathan Nieder wrote:
When booting with the quiet option off, I see that the lvm command in the initrd
segfaults.
Can you get a backtrace, for example by saving a core file to some
other (virtual) disk and analyzing it afterward with gdb?
See
Hi,
On 03/22/2012 01:12 PM, Rik Theys wrote:
Would unpacking the initramfs on a sid box with the 3.3 kernel and
chrooting into it be able to provide any additional info? I believe the
initramfs uses another C library than glibc, or is that no longer the case?
I did this, but when I chroot
Package: linux-2.6
Version: 3.3~rc6-1~experimental.1
Severity: important
Hi,
I installed the 3.3.0-rc6-amd64 kernel from experimental on a squeeze VM. The
system fails to boot this kernel as it can no longer find the root file system.
When booting with the quiet option off, I see that the lvm
fixed-upstream 659111
fixed 659111 linux-2.6/3.3~rc6-1~experimental.1
quit
Hi,
The commit that fixes this bug is now part of the upstream 3.3 kernel. I
verified it on the 3.3-rc6 kernel from experimental.
Can this commit be backported to the 3.2 kernel in sid?
It applies and I have tested it
Hi,
The Fedora 16 kernel 3.2.10-3.fc16 has patches that should reduce the
memory requirements of the old id mapper. The relevant changelog entry is:
* Wed Mar 14 2012 Steve Dickson ste...@redhat.com
- Reduce the foot print of the NFSv4 idmapping coda (bz 593035)
I have attached the patches
Hi,
On Wed, 21 Mar 2012, Jonathan Nieder wrote:
Rik Theys wrote:
Can this commit be backported to the 3.2 kernel in sid?
It applies and I have tested it in the past against the 3.2.4 kernel.
I would also be very much interested to hear how well the following
series against 2.6.32.y does
Ben,
On Wed, 21 Mar 2012, Ben Hutchings wrote:
It's probably also worth testing 3.3 when it shows up (currently in NEW
but likely to be available within 24 hours).
I compiled 3.3 from kernel.org and it has the same problem.
I'll try to configure a netconsole and/or serial console tomorrow.
testing any other NFS
functionality now.
How do you determine which other patches are required to backport a
specific patch (in general)? Is there some magic git command for that?
Regards,
Rik
--
Rik Theys
Senior System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10
B
] or the corresponding file in the
debian-kernel-handbook package.
[1]
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-kernel-org-package
Which 3.2.y kernel did you test?
I will upgrade the lenny test system to sid and try building a kernel
with this patch.
Regards,
Rik
--
Rik
Hi Ben,
On Tue, Jan 24, 2012 at 3:54 PM, Ben Hutchings b...@decadent.org.uk wrote:
On Tue, 2012-01-24 at 08:01 +0100, Rik Theys wrote:
The allocation failure has already been reported as #636306. I
proposed a fix for that in http://bugs.debian.org/636306#35.
The patch in #636306 has
Hi,
On 02/09/2012 10:09 AM, Rik Theys wrote:
On 02/08/2012 07:31 PM, Jonathan Nieder wrote:
Please try v3.3-rc1 or newer from upstream, or try the following patch
against stable/linux-3.2.y. Instructions for building a custom
kernel can be found at [1] or the corresponding file in the
debian
Hi,
On 02/09/2012 12:04 PM, Rik Theys wrote:
On 02/08/2012 07:31 PM, Jonathan Nieder wrote:
Please try v3.3-rc1 or newer from upstream, or try the following patch
against stable/linux-3.2.y. Instructions for building a custom
kernel can be found at [1] or the corresponding file in the
debian
Package: linux-2.6
Version: 2.6.32-41
Severity: normal
Hi,
Our home directories here are mounted over NFS4. When I log in to machine A and
run
vim
:q
and then log into machine B and do:
vim
:q
I get E137: Viminfo file is not writable: /users/system/rtheys/.viminfo
Every invocation of 'vim
notfound 659111 linux-2.6/2.6.26-27
notfound 659111 linux-2.6/2.6.29-5
notfound 659111 linux-2.6/2.6.31-2
found 659111 linux-2.6/2.6.32-8~bpo50+1
thanks
Hi,
It seems Lenny is not affected by this bug.
Regards,
Rik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
[forgot to cc the bug report]
-- Forwarded message --
Hi,
On Mon, Jan 23, 2012 at 1:24 PM, Michael Tokarev m...@tls.msk.ru wrote:
On 22.01.2012 22:42, Rik Theys wrote:
The updates installed linux kernel 3.2, which I assume is triggering this.
Recently there was a security
Package: linux-2.6
Version: 3.2.1-1
Severity: wishlist
Hi,
Please consider enabling the new NFS ID mapper functionality in the kernel:
CONFIG_NFS_USE_NEW_IDMAPPER
This will also need support in nfs-utils.
Enabling this feature should prevent page allocation failure errors we
frequently
get
Hi Ben,
On Mon, Jan 23, 2012 at 11:28 PM, Ben Hutchings b...@decadent.org.uk wrote:
On Mon, Jan 23, 2012 at 10:43:18PM +0100, Rik Theys wrote:
Please consider enabling the new NFS ID mapper functionality in the kernel:
CONFIG_NFS_USE_NEW_IDMAPPER
Enabling this feature should prevent page
Package: mdadm
Version: 3.2.3-2
Severity: normal
Dear Maintainer,
After upgrading my system to the latest sid packages I'm seeing the following
errors
in the kernel log:
[4.334881] mdadm: sending ioctl 800c0910 to a partition!
[4.334886] mdadm: sending ioctl 800c0910 to a partition!
[
Hi,
On Sun, Jan 8, 2012 at 7:36 PM, Ben Hutchings b...@decadent.org.uk wrote:
Jan 8 17:12:52 saturn kernel: [ 1623.655341] [ cut here
]
Jan 8 17:12:52 saturn kernel: [ 1623.655363] kernel BUG at
[Reformatted as plain-text so it will get accepted by the vger.kernel.org list]
On Mon, Jan 9, 2012 at 1:14 PM, Rik Theys rik.th...@gmail.com wrote:
Hi,
On Sun, Jan 8, 2012 at 7:36 PM, Ben Hutchings b...@decadent.org.uk wrote:
Jan 8 17:12:52 saturn kernel: [ 1623.655341] [ cut
Package: linux-2.6
Version: 2.6.32-39
Severity: normal
Hi,
We have a virtual machine now running as a KVM virtual machine. Before, this
virtual
machine was running as a Xen domU.
The VM has been given the same amount of memory and number of cpu's as it had
with Xen.
We configured the
Hi Jonathan,
On Fri, 2 Dec 2011, Jonathan Nieder wrote:
Thanks, Rik! It would also be useful to know the newest kernel you've
experienced this problem on, so we can rule out it having silently
gone away (though I don't think that's likely).
cteg, Rik, what kernel are you using these days?
Hi,
This can be fixed (worked around) by letting the start/stop script
create/remove a symlink to the pid file in /lib/init/rw/sendsigs.omit.d
(for squeeze) that points to the PID file.
Sendsigs will no longer send TERM and KILL signals to the daemon then.
For testing the sendsigs.omit.d is
1 - 100 of 197 matches
Mail list logo
