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
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: 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:
Hi,
Does it help if you run 'exportfs -f'? (or wait about 15 minutes)
You can check the content of the various caches that nfsd uses in:
/proc/net/rpc
I've also recently discovered that /proc/net/rpc/auth.unix.ip/content
contains the cache used by nfsd. You can flush that cache with the above
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
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:
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
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
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,
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
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
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-kernel-requ...@lists.debian.org
with a
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
Hi,
I'm just an end-user but personally I would prefer to see Wheezy release
with a more recent kernel than 3.2. If Wheezy freezes in June linux 3.4
might already be released. When Wheezy releases there will be a 3.5 and
likely even a 3.6.
Having a more recent kernel (like 3.4) will result
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?
still log in on the system using SSH.
Regards,
Rik
On Fri, 30 Sep 2011, Jonathan Nieder wrote:
tags 568557 + moreinfo
quit
Hi,
Rik Theys wrote:
cteg wrote:
I hopefully found a workaround, this is working since hours,
keyboard and mouse seem stable now.
Its not enough just to rmmod
Package: linux-2.6
Version: 2.6.32-35
Severity: normal
Tags: patch
Hi,
On some of our servers, we periodically see name_count maxed, losing inode
data messages
in the kernel log.
From what I can tell from Google, they are probably harmless and caused by the
auditing subsystem.
The following
Hi,
On 04/15/2011 05:49 AM, Ben Hutchings wrote:
Please consider adding this patch to a ((old)stable) kernel update.
I don't think this is sufficiently critical for an oldstable update.
For stable, yes, we'll consider it once it's accepted upstream. Please
let us know when that happens.
It
Hi,
On 04/15/2011 05:49 AM, Ben Hutchings wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=683372
Please consider adding this patch to a ((old)stable) kernel update.
I don't think this is sufficiently critical for an oldstable update.
For stable, yes, we'll consider it once it's accepted
Hi,
Red Hat has debugged this problem and has provided a patch. I've tested
the patch on the RHEL6 kernel and it seems to fix the problem.
The patch is available in the Red Hat bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=683372
Please consider adding this patch to a
Package: linux-2.6
Version: 2.6.38-1
Severity: wishlist
Hi,
It seems transparent hugepages (a new feature in 2.6.38) is not enabled in the
Debian build.
Please consider enabling transparent hugepages in the Debian kernel.
The feature could default to being disabled by default, but can be
Hi,
As this appears to be an upstream problem, I filed a bug report in the
kernel bugzilla under File Systems/NFS.
The upstream bug number is 30862.
https://bugzilla.kernel.org/show_bug.cgi?id=30862
Regards,
Rik
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a
Package: linux-2.6
Version: 2.6.32-30
Severity: normal
Hi,
We initially experied this bug on a RHEL6 server and CentOS 5.5 clients.
See also my Red Hat bugzilla report:
https://bugzilla.redhat.com/show_bug.cgi?id=683372
I can reproduce this with:
- Debian Lenny clients against the RHEL6
Ian,
On 01/06/2011 10:09 AM, Ian Campbell wrote:
I can test some more options on this system for a few more days, but
then I have to reinstall it.
If you are able it would be useful to know if the tip of
xen-4.0-testing.hg (which is just about to become 4.0.2-rc1) works or
not. You would only
Iann
Now I think of it can you also collect a similar log with the dom0_mem
workaround in place, for comparisons sake.
Are you able to rebuild the kernel with
CONFIG_XEN_MAX_DOMAIN_MEMORY=128? If so then a log of that boot for
comparison would be very interesting.
If you don't know how
Hi,
On 12/22/2010 10:34 AM, Ian Campbell wrote:
I was wondering about clamping something in the kernel to correspond to
CONFIG_XEN_MAX_DOMAIN_MEMORY and avoid the issue but you say the crash
is after x VCPUS and before Scrubbing Free RAM so I'm surprised the
dom0 kernel has run at this point
Hi,
On 12/14/2010 02:41 PM, Ian Campbell wrote:
When adding dom0_mem=2G to the boot line, the system boots OK.
I expect it will work ok with everything up to and including
dom0_mem=32G?
It does.
It depends a bit on your usecase but it is often best recommended to use
dom0_mem= anyway,
On 12/20/2010 03:19 PM, Bastian Blank wrote:
On Mon, Dec 20, 2010 at 02:02:51PM +0100, Rik Theys wrote:
I get task blocked for 120s errors (see below).
Upgrade dpkg to something newer. 1.15.8.6 or 1.15.8.7.
Are any of those versions expected to enter squeeze?
Regards,
Rik
Ben,
On Tue, 14 Dec 2010, Ben Hutchings wrote:
mpt2sas was not using the correct test for whether DMA mapping
succeeded, so it tried to continue after the DMA mapping failure. This
has been fixed in a later version and I will apply the fix to Debian's
branch of 2.6.32.
Thanks!
However,
On Tue, 14 Dec 2010, Ben Hutchings wrote:
On Tue, 2010-12-14 at 13:24 +0100, Rik Theys wrote:
This system _has_
a RAID controller and the disk is in a RAID1. Why would the filesystem switch
to read-only mode? Is it because the RAID is too slow? If the RAID is too slow,
this should just give
On Tue, 14 Dec 2010, Rik Theys wrote:
On Tue, 14 Dec 2010, Ben Hutchings wrote:
On Tue, 2010-12-14 at 13:24 +0100, Rik Theys wrote:
This system _has_
a RAID controller and the disk is in a RAID1. Why would the filesystem
switch
to read-only mode? Is it because the RAID is too slow
Hi,
I'm seeing the same issue (hang at boot of -17 kernel) but the hang is
sometimes much earlier in the boot process on my system:
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 2.6.32-5-amd64 (Debian 2.6.32-17)
Hi,
Did you find the time to run tests to find the performance cost of
enabling the feature (disabled-by-default)?
Google [1] shows some low overhead patches for the memory controller,
but I don't know if they have been merged.
[1] http://lkml.org/lkml/2009/6/15/12
Regards,
Rik
--
Rik
Hi,
I had a similar issue on Fedora 12 (and now 13), with the keyboard and mouse
locking up but
the rest of the system OK.
The problem went away for me by adding the following kernel parameter to the
grub
configuration:
pcie_aspm=off
My motherboard is also an ASUS P7P55D-E.
Regards,
Rik
Hi,
It seems this was already filed in bug #534964, so this bug can be closed.
Regards,
Rik
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Package: linux-2.6
Version: 2.6.32-9
Severity: wishlist
Hi,
Please consider adding the memory cgroup feature to the kernel.
CONFIG_CGROUP_MEM_RES_CTLR=y
CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y
It uses a little bit of memory but can be disabled using a boot option.
It's also enabled in Fedora 12.
Package: linux-image-2.6.26-bpo.1-amd64
Version: 2.6.26-13~bpo40+1
Severity: normal
Hi,
I'm running the 2.6.26 kernel from backports on etch. The server in
question is an NFS file server. During periods we're getting a lot of
lockd: too many open connections, consider increasing the number of
to reproduce.
Regards,
Rik
--
Rik Theys
System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10
B-3001 LEUVEN - HEVERLEE
Tel.: +32(0)16/32.11.07
Any errors in spelling, tact or fact are transmission errors
Hi,
Can the patch be applied to the Debian kernel so lenny releases with a
kernel which works on common HP servers?
Regards,
Rik
--
Rik Theys
System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10
B-3001 LEUVEN - HEVERLEE
Tel.: +32(0)16/32.11.07
Hi,
The upstream bug report has been tagged as resolved and code_fix. I
assume this means it is scheduled for inclusion in 2.6.27.
Any chance of having this patch backported (the patch applies cleanly on
the Debian 2.6.26 kernel) to the 2.6.26 kernel targetted for Lenny?
Regards,
Rik
Hi,
The patch provided by David Brownell in the upstream bug report[1] seems
to fix this issue. I've applied the patch to the Debian 2.6.26-4 kernel
and it seems to work.
Please consider applying this patch to the Debian kernel targetted for
Lenny.
Regards,
Rik
[1]
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-5
Severity: important
When booting the latest Debian kernel (tried 2.6.26-4 and 2.6.26-5) on an HP
DL360 G5, no rtc device is
created in /dev and the system can not get the hardware clock time at boot and
save it at shutdown.
In the kernel
Hi,
I've tried some other kernels on the system:
2.6.18-6-amd64 from etch: OK
2.6.24-etchnhalf from etch: OK
2.6.25-1 from snapshot.debian.net: OK
2.6.26-1-amd64 (up to 2.6.26-6~snapshot.12236): NOT OK
2.6.27-rc6: NOT OK
Fedora kernel 2.6.26.3-29.fc9.x86_64: NOT OK
Maybe related to
Package: linux-2.6
Version: 2.6.26-3
Severity: normal
I'm running a kvm virtual machine (with CentOS 5.2 as the guest OS, but it
doesn't seem to
matter) on a Lenny host (using the 2.6.26 kernel and kvm from unstable). When I
try to
hot-add a cpu to the virtual machine, the host kernel oopses
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-1
Severity: normal
Hi,
When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains
during boot that it can not read the hardware clock using any known
methods.
When I look in /dev, the /dev/rtc* device is not there.
The device
Hi,
On Sunday 03 August 2008 16:08:18 Bastian Blank wrote:
On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote:
On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote:
When booting the 2.6.26 kernel from unstable on Lenny, hwclock
complains during boot that it can not read
On Sunday 03 August 2008 16:08:18 Bastian Blank wrote:
On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote:
On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote:
When booting the 2.6.26 kernel from unstable on Lenny, hwclock
complains during boot that it can not read
Hi,
On Sunday 03 August 2008 16:08:18 Bastian Blank wrote:
On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote:
On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote:
When booting the 2.6.26 kernel from unstable on Lenny, hwclock
complains during boot that it can not read
Bastian Blank wrote:
Setting it to 255 needs 2MiB of image size and unswappable memory.
|textdata bss dec hex filename
|1345623 3148364 417112 4911099 4aeffb x86_64-255/vmlinux
|1339887 380556 273880 1994323 1e6e53 x86_64-32/vmlinux
It adds 32 interrupt vectors
Subject: linux-2.6: Kernel supports only 32 cpu's
Package: linux-2.6
Severity: wishlist
Hi,
The current Debian kernel supports 32 cpu's according to the
/boot/config file. The
RHEL/CentOS 5 kernel has CONFIG_NR_CPUS set to 255. Any chance the
Debian kernel
parameter can be adjusted to be a
1 - 100 of 102 matches
Mail list logo
