Bug#657316: [Thinkpad X201] kernel randomly stops booting
Ok. Thank you. Due to the production system, I'm reluctant to install a kernel from unstable. As soon as the critical tasks are over, which will take me one or two weeks, I'll get the chance and report here once again. Greetings, Jaakov. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/897183194.1328697943.141454488.49...@mcgi-wr-12.rambler.ru
Bug#659111: linux-image-2.6.32-5-amd64: Files on NFS4 become unwritable, but OK after explicit stat
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 and :q' will trigger this. Explicitely doing a stat of the file fixes this. Doing the vim :q thing on machine A while it has been triggered on B works: A never shows this message, while B continues to show it until the file is stat'ed. The file server is a RHEL 6.2 machine. I can trigger this bug on RHEL 6 clients, Debian 6 clients, Debian 6 with the 3.2 backport, but NOT on CentOS 5 clients. I no longer have Lenny machines so I can't verify it there. This seems to have been discussed here: http://comments.gmane.org/gmane.linux.nfs/37230 According to that thread, vim tries to do a stat on the ~/.viminfo file and receives incorrect st_uid/st_gid information? If it gets the wrong information I assume this is a kernel bug. Why is the information incorrect? The easiest way to reproduce this is with vim, but I've seen similar strange behaviour when modifying my ~/.ssh/authorized_keys file and then trying to ssh to other machines. They say they are ignoring the file because the permissions are not OK. This looks like the same bug to me, but is harder to reproduce here. Regards, Rik -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-41) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Jan 16 16:22:28 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/vg00-root ro ipv6.disable=1 ** Not tainted ** Kernel log: [244111.447272] name_count maxed, losing inode data: dev=00:07, inode=8 [244111.447278] name_count maxed, losing inode data: dev=00:07, inode=20898841 [244111.466208] name_count maxed, losing inode data: dev=00:3b, inode=21757958 [257106.934243] IPMI message handler: BMC returned incorrect response, expected netfn 2d cmd 0, got netfn 2d cmd 35 [411592.612032] name_count maxed, losing inode data: dev=00:13, inode=724 [411592.612590] name_count maxed, losing inode data: dev=00:07, inode=8 [411592.612596] name_count maxed, losing inode data: dev=00:07, inode=36185654 [411592.612983] name_count maxed, losing inode data: dev=00:3d, inode=2 [430225.420674] snmpd invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0 [430225.420709] snmpd cpuset=/ mems_allowed=0 [430225.420735] Pid: 1967, comm: snmpd Not tainted 2.6.32-5-amd64 #1 [430225.420763] Call Trace: [430225.420792] [810b6418] ? oom_kill_process+0x7f/0x23f [430225.420821] [810b693c] ? __out_of_memory+0x12a/0x141 [430225.420849] [810b6a93] ? out_of_memory+0x140/0x172 [430225.420878] [810ba7f8] ? __alloc_pages_nodemask+0x4ec/0x5fc [430225.420910] [812fb9ea] ? io_schedule+0x93/0xb7 [430225.420939] [810bbd5d] ? __do_page_cache_readahead+0x9b/0x1b4 [430225.420970] [81065058] ? wake_bit_function+0x0/0x23 [430225.421005] [810bbe92] ? ra_submit+0x1c/0x20 [430225.421034] [810b4b65] ? filemap_fault+0x17d/0x2f6 [430225.421065] [810caada] ? __do_fault+0x54/0x3c3 [430225.421093] [810cce2e] ? handle_mm_fault+0x3b8/0x80f [430225.421123] [8106c59b] ? ktime_get_ts+0x68/0xb2 [430225.421151] [812ff166] ? do_page_fault+0x2e0/0x2fc [430225.421180] [812fd005] ? page_fault+0x25/0x30 [430225.421207] Mem-Info: [430225.421227] Node 0 DMA per-cpu: [430225.421252] CPU0: hi:0, btch: 1 usd: 0 [430225.421277] CPU1: hi:0, btch: 1 usd: 0 [430225.421303] CPU2: hi:0, btch: 1 usd: 0 [430225.421328] CPU3: hi:0, btch: 1 usd: 0 [430225.421353] Node 0 DMA32 per-cpu: [430225.421378] CPU0: hi: 186, btch: 31 usd: 0 [430225.421404] CPU1: hi: 186, btch: 31 usd: 0 [430225.421429] CPU2: hi: 186, btch: 31 usd: 0 [430225.421455] CPU3: hi: 186, btch: 31 usd: 0 [430225.421480] Node 0 Normal per-cpu: [430225.421504] CPU0: hi: 186, btch: 31 usd: 4 [430225.421530] CPU1: hi: 186, btch: 31 usd: 31 [430225.421556] CPU2: hi: 186, btch: 31 usd: 28 [430225.421581] CPU3: hi: 186, btch: 31 usd: 0 [430225.421610] active_anon:4620751 inactive_anon:456620 isolated_anon:0 [430225.421611] active_file:1426 inactive_file:1586 isolated_file:64 [430225.421612] unevictable:8 dirty:1493 writeback:202 unstable:0 [430225.421613] free:25435 slab_reclaimable:4029 slab_unreclaimable:4788 [430225.421614] mapped:1158 shmem:132 pagetables:15171 bounce:0 [430225.421745] Node 0 DMA free:15816kB min:12kB low:12kB high:16kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15288kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:16kB kernel_stack:0kB pagetables:0kB unstable:0kB
Bug#659111: List unaffected versions
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 subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f3285c3.1030...@esat.kuleuven.be
Processed: List unaffected versions
Processing commands for cont...@bugs.debian.org: notfound 659111 linux-2.6/2.6.26-27 Bug #659111 [linux-2.6] linux-image-2.6.32-5-amd64: Files on NFS4 become unwritable, but OK after explicit stat The source linux-2.6 and version 2.6.26-27 do not appear to match any binary packages Ignoring request to alter found versions of bug #659111 to the same values previously set notfound 659111 linux-2.6/2.6.29-5 Bug #659111 [linux-2.6] linux-image-2.6.32-5-amd64: Files on NFS4 become unwritable, but OK after explicit stat Ignoring request to alter found versions of bug #659111 to the same values previously set notfound 659111 linux-2.6/2.6.31-2 Bug #659111 [linux-2.6] linux-image-2.6.32-5-amd64: Files on NFS4 become unwritable, but OK after explicit stat Ignoring request to alter found versions of bug #659111 to the same values previously set found 659111 linux-2.6/2.6.32-8~bpo50+1 Bug #659111 [linux-2.6] linux-image-2.6.32-5-amd64: Files on NFS4 become unwritable, but OK after explicit stat The source linux-2.6 and version 2.6.32-8~bpo50+1 do not appear to match any binary packages Bug Marked as found in versions linux-2.6/2.6.32-8~bpo50+1. thanks Stopping processing here. Please contact me if you need assistance. -- 659111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132871239927618.transcr...@bugs.debian.org
Bug#656331: RTL8168b/8111b with ASUS M2A-VM (SB600): Network device stays down after resume
Dear Francois,
thank you for your fast reply.
Am Sonntag, den 05.02.2012, 18:57 +0100 schrieb Francois Romieu:
Paul Menzel pm.deb...@googlemail.com :
[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656331]
I experienced this problem (only) three times until now. If I remember
correctly the last time with 3.2.1. I still do not know how to reproduce
this.
(good PR, nice)
An 'ethtool -d' and a 'mii-tool -v' of the device after a successful resume
and a failed one could help if it's a driver thing.
The problem has not shown up again until now so I only send the output
from the successful resume. Currently Linux version 3.2.4 is installed.
The following outputs are identical after startup and (a successful)
resume.
$ sudo ethtool --version
ethtool version 3.1
$ sudo ethtool eth0 # The option `-d` does not exist.
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half
100baseT/Full
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x0033 (51)
drv probe ifdown ifup
Link detected: yes
$ sudo mii-tool --version
$Id: mii-tool.c,v 1.9 2006/09/27 20:59:18 ecki Exp $
(Author: David Hinds based on Donald Becker's mii-diag)
net-tools 1.60
$ sudo mii-tool -v
eth0: negotiated 100baseTx-FD flow-control, link ok
product info: vendor 00:07:32, model 17 rev 2
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD
10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
flow-control
link partner: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD
10baseT-FD 10baseT-HD flow-control
You may check if runtime power management is enabled or not, especially
after a failed resume. See the /sys/devices/pci:../:..:/power
directory and its control, runtime_enabled and runtime_status files
(control = on - runtime PM disabled, see Documentation/power/runtime_pm.txt)
The document is online at [1].
For some reason the ethernet controller is not listed under
`/sys/devices`.
$ lspci | grep RTL
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
$ lspci -n -s 02:00.0
02:00.0 0200: 10ec:8168 (rev 01)
$ ls /sys/devices/
breakpoint i2c-2 LNXSYSTM:00 pnp0 tracepoint
cpu i2c-3 pci:00 software virtual
i2c-1 i2c-4 platform system
I use `/sys/bus/pci/devices` instead.
$ more
/sys/bus/pci/devices/\:02\:00.0/power/{control,runtime_enabled,runtime_status}
::
/sys/bus/pci/devices/:02:00.0/power/control
::
on
--More--(Next file:
/sys/bus/pci/devices/:02:00.0/power/runtime_::
/sys/bus/pci/devices/:02:00.0/power/runtime_enabled
::
forbidden
--More--(Next file:
/sys/bus/pci/devices/:02:00.0/power/runtime_::
/sys/bus/pci/devices/:02:00.0/power/runtime_status
::
active
If it is enabled and the link does not come up fast enough (5 s), runtime
PM will suspend the device. It should not matter as long as the link is
still present because the device should (TM) soon generate a power management
event. The latter not happening or the PME being ignored could explain
the bug. If so, temporarily disabling runtime PM for your device after a
failed resume instead of removing the module or the cable may be enough
to recover the link. It's just a guess though.
So judging from the output above runtime
Bug#659130: variable RPCGSSDOPTS is used in /etc/init.d/nfs-common but never initialized p.ex in /etc/default/nfs-common
Package: nfs-common Version: 1:1.2.2-4squeeze2 Severity: normal -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120208154803.9362.16962.report...@tm.cs.uni-potsdam.de
Patch lockdep, bug: Exclude TAINT_OOT_MODULE from disabling lock debugging has been added to the 3.2-stable tree
This is a note to let you know that I've just added the patch titled
lockdep, bug: Exclude TAINT_OOT_MODULE from disabling lock debugging
to the 3.2-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
lockdep-bug-exclude-taint_oot_module-from-disabling-lock-debugging.patch
and it can be found in the queue-3.2 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let sta...@vger.kernel.org know about it.
From 9ec84acee1e221d99dc33237bff5e82839d10cc0 Mon Sep 17 00:00:00 2001
From: Ben Hutchings b...@decadent.org.uk
Date: Wed, 7 Dec 2011 14:30:58 +
Subject: lockdep, bug: Exclude TAINT_OOT_MODULE from disabling lock debugging
From: Ben Hutchings b...@decadent.org.uk
commit 9ec84acee1e221d99dc33237bff5e82839d10cc0 upstream.
We do want to allow lock debugging for GPL-compatible modules
that are not (yet) built in-tree. This was disabled as a
side-effect of commit 2449b8ba0745327c5fa49a8d9acffe03b2eded69
('module,bug: Add TAINT_OOT_MODULE flag for modules not built
in-tree'). Lock debug warnings now include taint flags, so
kernel developers should still be able to deflect warnings
caused by out-of-tree modules.
The TAINT_PROPRIETARY_MODULE flag for non-GPL-compatible modules
will still disable lock debugging.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
Cc: Nick Bowler nbow...@elliptictech.com
Cc: Dave Jones da...@redhat.com
Cc: Rusty Russell ru...@rustcorp.com.au
Cc: Randy Dunlap rdun...@xenotime.net
Cc: Debian kernel maintainers debian-kernel@lists.debian.org
Cc: Peter Zijlstra pet...@infradead.org
Cc: Alan Cox a...@linux.intel.com
Link: http://lkml.kernel.org/r/1323268258.18450.11.camel@deadeye
Signed-off-by: Ingo Molnar mi...@elte.hu
Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org
---
kernel/panic.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--- a/kernel/panic.c
+++ b/kernel/panic.c
@@ -237,11 +237,12 @@ void add_taint(unsigned flag)
* Can't trust the integrity of the kernel anymore.
* We don't call directly debug_locks_off() because the issue
* is not necessarily serious enough to set oops_in_progress to 1
-* Also we want to keep up lockdep for staging development and
-* post-warning case.
+* Also we want to keep up lockdep for staging/out-of-tree
+* development and post-warning case.
*/
switch (flag) {
case TAINT_CRAP:
+ case TAINT_OOT_MODULE:
case TAINT_WARN:
case TAINT_FIRMWARE_WORKAROUND:
break;
Patches currently in stable-queue which might be from b...@decadent.org.uk are
queue-3.2/lockdep-bug-exclude-taint_firmware_workaround-from-disabling-lockdep.patch
queue-3.2/lockdep-bug-exclude-taint_oot_module-from-disabling-lock-debugging.patch
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/13287191523...@kroah.org
Bug#659136: ideapad_laptop: Kernel Oops turning backlight back on using the function keys with Lenovo G555
reassign 659136 src:linux-2.6 3.1.8-2 forcemerge 659111 659136 quit Hi Paul, Paul Menzel wrote: Searching for existing reports on the WWW I only found a similar report in the RedHat Bugzilla claiming this bug to be fixed in 3.2 which I could not try yet. Please do. You can find 3.2.4-1 in sid; relative to the version you are currently using, in addition to adding the fix to this, it adds some fixes to important known security bugs. Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120208173015.GB6712@burratino
Processed (with 1 errors): Re: ideapad_laptop: Kernel Oops turning backlight back on using the function keys with Lenovo G555
Processing commands for cont...@bugs.debian.org: reassign 659136 src:linux-2.6 3.1.8-2 Bug #659136 [linux-2.6] ideapad_laptop: Kernel Oops turning backlight back on using the function keys with Lenovo G555 Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug No longer marked as found in versions 3.1.8-2. Bug #659136 [src:linux-2.6] ideapad_laptop: Kernel Oops turning backlight back on using the function keys with Lenovo G555 Bug Marked as found in versions linux-2.6/3.1.8-2. forcemerge 659111 659136 Bug#659111: linux-image-2.6.32-5-amd64: Files on NFS4 become unwritable, but OK after explicit stat Bug#659136: ideapad_laptop: Kernel Oops turning backlight back on using the function keys with Lenovo G555 Mismatch - only Bugs in the same package can be forcibly merged: Bug 659136 is not in the same package as 659111 quit Stopping processing here. Please contact me if you need assistance. -- 659136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13287515978.transcr...@bugs.debian.org
Processed: Re: ideapad_laptop: Kernel Oops turning backlight back on using the function keys with Lenovo G555
Processing commands for cont...@bugs.debian.org: # Debian Bug Tracking System wrote: # # forcemerge 659111 659136 # Bug#659111: linux-image-2.6.32-5-amd64: Files on NFS4 become unwritable, but OK after explicit stat # Bug#659136: ideapad_laptop: Kernel Oops turning backlight back on using the function keys with Lenovo G555 # Mismatch - only Bugs in the same package can be forcibly merged: # # Good catch, BTS! Sorry for the noise. forcemerge 655377 659136 Bug#655377: [ideapad_laptop] NULL pointer dereference turning off backlight with fn key Bug#659136: ideapad_laptop: Kernel Oops turning backlight back on using the function keys with Lenovo G555 Forcibly Merged 655377 659136. End of message, stopping processing here. Please contact me if you need assistance. -- 655377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655377 659136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132872323721400.transcr...@bugs.debian.org
Bug#659111: [2.6.31 - 2.6.32.y regression] Files on NFS4 become unwritable, but OK after explicit stat
# regression
severity 659111 important
quit
Hi Rik,
Rik Theys wrote:
I get E137: Viminfo file is not writable: /users/system/rtheys/.viminfo
Every invocation of 'vim and :q' will trigger this.
Explicitely doing a stat of the file fixes this.
[...]
This seems to have been discussed here:
http://comments.gmane.org/gmane.linux.nfs/37230
Thanks for a clear report.
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-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?
-- 8 --
From: Trond Myklebust trond.mykleb...@netapp.com
Date: Sat, 7 Jan 2012 13:22:46 -0500
Subject: NFSv4: Save the owner/group name string when doing open
commit 6926afd1925a54a13684ebe05987868890665e2b upstream.
...so that we can do the uid/gid mapping outside the asynchronous RPC
context.
This fixes a bug in the current NFSv4 atomic open code where the client
isn't able to determine what the true uid/gid fields of the file are,
(because the asynchronous nature of the OPEN call denies it the ability
to do an upcall) and so fills them with default values, marking the
inode as needing revalidation.
Unfortunately, in some cases, the VFS will do some additional sanity
checks on the file, and may override the server's decision to allow
the open because it sees the wrong owner/group fields.
Signed-off-by: Trond Myklebust trond.mykleb...@netapp.com
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
Hope that helps,
Jonathan
fs/nfs/idmap.c| 83 +++
fs/nfs/inode.c|2 +
fs/nfs/nfs4proc.c | 10
fs/nfs/nfs4xdr.c | 106 -
include/linux/nfs_idmap.h |8 +++
include/linux/nfs_xdr.h | 17 +--
6 files changed, 162 insertions(+), 64 deletions(-)
diff --git a/fs/nfs/idmap.c b/fs/nfs/idmap.c
index 47d1c6ff2d8e..2c05f1991e1e 100644
--- a/fs/nfs/idmap.c
+++ b/fs/nfs/idmap.c
@@ -38,6 +38,89 @@
#include linux/kernel.h
#include linux/slab.h
#include linux/nfs_idmap.h
+#include linux/nfs_fs.h
+
+/**
+ * nfs_fattr_init_names - initialise the nfs_fattr owner_name/group_name fields
+ * @fattr: fully initialised struct nfs_fattr
+ * @owner_name: owner name string cache
+ * @group_name: group name string cache
+ */
+void nfs_fattr_init_names(struct nfs_fattr *fattr,
+ struct nfs4_string *owner_name,
+ struct nfs4_string *group_name)
+{
+ fattr-owner_name = owner_name;
+ fattr-group_name = group_name;
+}
+
+static void nfs_fattr_free_owner_name(struct nfs_fattr *fattr)
+{
+ fattr-valid = ~NFS_ATTR_FATTR_OWNER_NAME;
+ kfree(fattr-owner_name-data);
+}
+
+static void nfs_fattr_free_group_name(struct nfs_fattr *fattr)
+{
+ fattr-valid = ~NFS_ATTR_FATTR_GROUP_NAME;
+ kfree(fattr-group_name-data);
+}
+
+static bool nfs_fattr_map_owner_name(struct nfs_server *server, struct
nfs_fattr *fattr)
+{
+ struct nfs4_string *owner = fattr-owner_name;
+ __u32 uid;
+
+ if (!(fattr-valid NFS_ATTR_FATTR_OWNER_NAME))
+ return false;
+ if (nfs_map_name_to_uid(server, owner-data, owner-len, uid) == 0) {
+ fattr-uid = uid;
+ fattr-valid |= NFS_ATTR_FATTR_OWNER;
+ }
+ return true;
+}
+
+static bool nfs_fattr_map_group_name(struct nfs_server *server, struct
nfs_fattr *fattr)
+{
+ struct nfs4_string *group = fattr-group_name;
+ __u32 gid;
+
+ if (!(fattr-valid NFS_ATTR_FATTR_GROUP_NAME))
+ return false;
+ if (nfs_map_group_to_gid(server, group-data, group-len, gid) == 0) {
+ fattr-gid = gid;
+ fattr-valid |= NFS_ATTR_FATTR_GROUP;
+ }
+ return true;
+}
+
+/**
+ * nfs_fattr_free_names - free up the NFSv4 owner and group strings
+ * @fattr: a fully initialised nfs_fattr structure
+ */
+void nfs_fattr_free_names(struct nfs_fattr *fattr)
+{
+ if (fattr-valid NFS_ATTR_FATTR_OWNER_NAME)
+ nfs_fattr_free_owner_name(fattr);
+ if (fattr-valid NFS_ATTR_FATTR_GROUP_NAME)
+ nfs_fattr_free_group_name(fattr);
+}
+
+/**
+ * nfs_fattr_map_and_free_names - map owner/group strings into uid/gid and free
+ * @server: pointer to the filesystem nfs_server structure
+ * @fattr: a fully initialised nfs_fattr structure
+ *
+ * This helper maps the cached NFSv4 owner/group strings in fattr into
+ * their numeric uid/gid equivalents, and then frees the cached strings.
+ */
+void nfs_fattr_map_and_free_names(struct nfs_server *server, struct nfs_fattr
*fattr)
+{
+ if (nfs_fattr_map_owner_name(server, fattr))
+ nfs_fattr_free_owner_name(fattr);
+ if (nfs_fattr_map_group_name(server, fattr))
+
Processed: Re: [2.6.31 - 2.6.32.y regression] Files on NFS4 become unwritable, but OK after explicit stat
Processing commands for cont...@bugs.debian.org: # regression severity 659111 important Bug #659111 [linux-2.6] linux-image-2.6.32-5-amd64: Files on NFS4 become unwritable, but OK after explicit stat Severity set to 'important' from 'normal' quit Stopping processing here. Please contact me if you need assistance. -- 659111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13287258733173.transcr...@bugs.debian.org
Bug#657316: [Thinkpad X201] kernel randomly stops booting
jaa...@ro.ru wrote: Thank you. Due to the production system, I'm reluctant to install a kernel from unstable. As soon as the critical tasks are over, which will take me one or two weeks, I'll get the chance and report here once again. No problem; we can wait. I guess it's probably worth mentioning that the kernel in sid fixes some important security bugs that are not fixed in 3.1.8-2. Now that it builds on all arches again, 3.2.4 should be migrating to testing soon. Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120208184553.GC7734@burratino
Bug#658662: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2
On Sat, Feb 04, 2012 at 06:31:13PM -0500, Peter Colberg wrote: Since upgrading to linux-image-3.2.0-1-amd64, an external display connected via DisplayPort to a Sandy Bridge onboard graphics card stopped working, and instead turns off reporting “DP no signal”. Ok, I have finished the bisect, compiling and testing 17 kernels. It seems the math in the i915 DisplayPort code got worse… ;-) Peter cd9dde44f47501394b9f0715b6a36a92aa74c0d0 is the first bad commit commit cd9dde44f47501394b9f0715b6a36a92aa74c0d0 Author: Adam Jackson a...@redhat.com Date: Fri Oct 14 12:43:49 2011 -0400 drm/i915/dp: Fix the math in intel_dp_link_required The previous code was confused about units, which is pretty reasonable given that the units themselves are confusing. Signed-off-by: Adam Jackson a...@redhat.com Signed-off-by: Keith Packard kei...@keithp.com :04 04 3c0a0f38fc6482a401340e03fa3fbd687d11eda4 294673b782b3ecc93540f46f7721d385bd30cfac M drivers # git bisect log # bad: [805a6af8dba5dfdd35ec35dc52ec0122400b2610] Linux 3.2 # good: [c3b92c8787367a8bb53d57d9789b558f1295cc96] Linux 3.1 git bisect start 'v3.2' 'v3.1' # bad: [68d99b2c8efcb6ed3807a55569300c53b5f88be5] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound git bisect bad 68d99b2c8efcb6ed3807a55569300c53b5f88be5 # good: [efb8d21b2c6db3497655cc6a033ae8a9883e4063] Merge branch 'tty-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty git bisect good efb8d21b2c6db3497655cc6a033ae8a9883e4063 # good: [8686a0e200419322654a75155e2e6f80346a1297] Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip git bisect good 8686a0e200419322654a75155e2e6f80346a1297 # bad: [f362f98e7c445643d27c610bb7a86b79727b592e] Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/hch/vfs-queue git bisect bad f362f98e7c445643d27c610bb7a86b79727b592e # good: [ca836a25435ef1b9914840ed0a310c9b6ac261d1] Merge branch 'x86-vdso-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip git bisect good ca836a25435ef1b9914840ed0a310c9b6ac261d1 # good: [c5c42360bc1cb14c7da3186683e9525b33b72656] vmwgfx: Don't pass unused arguments to do_dirty functions git bisect good c5c42360bc1cb14c7da3186683e9525b33b72656 # bad: [5619a693965b291315685bdfe01a0246ebd7e41e] Merge branch 'for-linus' of git://oss.sgi.com/xfs/xfs git bisect bad 5619a693965b291315685bdfe01a0246ebd7e41e # bad: [82d165557ef094d4b4dfc05871aee618ec7102b0] drm/i915/dp: Fix eDP on PCH DP on CPT/PPT git bisect bad 82d165557ef094d4b4dfc05871aee618ec7102b0 # good: [a9e2641dee52cae2db7688a749344365642a5e79] drm/i915: close PM interrupt masking races in the rps work func git bisect good a9e2641dee52cae2db7688a749344365642a5e79 # good: [75770564c90c45618003267f4cdde4bbc090f1bd] drm/i915: use transcoder select bits on VGA and HDMI on CPT git bisect good 75770564c90c45618003267f4cdde4bbc090f1bd # good: [a487928908226df493a3ce145ecf4bb39296714e] drm/i915: remove transcoder PLL mashing from mode_set per specs git bisect good a487928908226df493a3ce145ecf4bb39296714e # bad: [a2006cf5a7ad3463e7c1e9da2c4bc90499427558] drm/i915: read full receiver capability field during DP hot plug git bisect bad a2006cf5a7ad3463e7c1e9da2c4bc90499427558 # good: [f52c619a590fa75276c07dfcaf380dee53e4ea4c] drm/i915/panel: Always record the backlight level again (but cleverly) git bisect good f52c619a590fa75276c07dfcaf380dee53e4ea4c # bad: [dc22ee6fc18ce0f15424e753e8473c306ece95c1] drm/i915/dp: Remove eDP special cases from bandwidth checks git bisect bad dc22ee6fc18ce0f15424e753e8473c306ece95c1 # bad: [cd9dde44f47501394b9f0715b6a36a92aa74c0d0] drm/i915/dp: Fix the math in intel_dp_link_required git bisect bad cd9dde44f47501394b9f0715b6a36a92aa74c0d0 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120208185414.GA3816@alcyone
Processed: attached patch (Re: Files on NFS4 become unwritable, but OK after explicit stat)
Processing commands for cont...@bugs.debian.org: tags 659111 + patch moreinfo Bug #659111 [linux-2.6] linux-image-2.6.32-5-amd64: Files on NFS4 become unwritable, but OK after explicit stat Added tag(s) moreinfo and patch. End of message, stopping processing here. Please contact me if you need assistance. -- 659111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132872888618311.transcr...@bugs.debian.org
Bug#656331: RTL8168b/8111b with ASUS M2A-VM (SB600): Network device stays down after resume
Am Mittwoch, den 08.02.2012, 16:28 +0100 schrieb Paul Menzel: Am Sonntag, den 05.02.2012, 18:57 +0100 schrieb Francois Romieu: Paul Menzel pm.deb...@googlemail.com : [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656331] I experienced this problem (only) three times until now. If I remember correctly the last time with 3.2.1. I still do not know how to reproduce this. (good PR, nice) An 'ethtool -d' and a 'mii-tool -v' of the device after a successful resume and a failed one could help if it's a driver thing. The problem has not shown up again until now so I only send the output from the successful resume. Currently Linux version 3.2.4 is installed. Right on time a suspend cycle later the problem turned up again. The following outputs are identical after startup and (a successful) resume. $ sudo ethtool --version ethtool version 3.1 $ sudo ethtool eth0 # The option `-d` does not exist. Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x0033 (51) drv probe ifdown ifup Link detected: yes Now from a failed resume. $ sudo ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x0033 (51) drv probe ifdown ifup I could not spot a difference. $ sudo mii-tool --version $Id: mii-tool.c,v 1.9 2006/09/27 20:59:18 ecki Exp $ (Author: David Hinds based on Donald Becker's mii-diag) net-tools 1.60 $ sudo mii-tool -v eth0: negotiated 100baseTx-FD flow-control, link ok product info: vendor 00:07:32, model 17 rev 2 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control link partner: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control From a failed resume it looks like the following. $ sudo mii-tool -v eth0: negotiated 100baseTx-FD flow-control, link ok product info: vendor 00:07:32, model 17 rev 2 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
Bug#659169: [2.6.32] BUG: soft lockup - CPU#7 stuck for 17163091979s! [init:9709]
Source: linux-2.6 Version: 2.6.32-5 Severity: normal Hello, Today one of my servers stopped responding to some webs, ssh'ing into it was impossible. The ping worked and the ssh connection was starting but the shell didn't showed up after waiting a long time. Finally a hard-reset was needed in order to bring it back After the reboot I found this on kern.log # tail /var/log/kern.log Feb 1 09:41:00 server-i7_920 kernel: [17383037.287331] EXT4-fs (dm-29): mounted filesystem with ordered data mode Feb 5 09:38:15 server-i7_920 kernel: [17727613.769052] NOHZ: local_softirq_pending 100 Feb 7 05:56:07 server-i7_920 kernel: [17886689.887577] e1000e: eth0 NIC Link is Down Feb 7 05:59:05 server-i7_920 kernel: [17886867.166464] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 7 05:59:41 server-i7_920 kernel: [17886903.722727] e1000e: eth0 NIC Link is Down Feb 7 06:00:00 server-i7_920 kernel: [17886922.309159] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876326] BUG: soft lockup - CPU#7 stuck for 17163091979s! [init:9709] Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876371] Modules linked in: btrfs zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs ext4 jbd2 crc16 ext2 ipt_LOG sg xt_limit xt_tcpudp xt_state iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables dummy loop snd_pcm snd_timer snd soundcore snd_page_alloc ioatdma i2c_i801 i2c_core pcspkr dca psmouse evdev button serio_raw processor ext3 jbd mbcache dm_mod sd_mod crc_t10dif ahci libata uhci_hcd ehci_hcd scsi_mod usbcore nls_base e1000e thermal thermal_sys [last unloaded: scsi_wait_scan] Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876405] CPU 7: Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876406] Modules linked in: btrfs zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs ext4 jbd2 crc16 ext2 ipt_LOG sg xt_limit xt_tcpudp xt_state iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables dummy loop snd_pcm snd_timer snd soundcore snd_page_alloc ioatdma i2c_i801 i2c_core pcspkr dca psmouse evdev button serio_raw processor ext3 jbd mbcache dm_mod sd_mod crc_t10dif ahci libata uhci_hcd ehci_hcd scsi_mod usbcore nls_base e1000e thermal thermal_sys [last unloaded: scsi_wait_scan] Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876433] Pid: 9709, comm: init Not tainted 2.6.32-5-vserver-amd64 #1 X8STi Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876435] RIP: 0023:[f76c0430] [f76c0430] 0xf76c0430 Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876440] RSP: 002b:ffa6673c EFLAGS: 0296 Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876442] RAX: fff6 RBX: RCX: ffa6673c Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876443] RDX: f76c0430 RSI: 000f RDI: Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876445] RBP: 8101166e R08: R09: Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876447] R10: R11: R12: Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876448] R13: R14: R15: Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876451] FS: () GS:880016bc(0063) knlGS:f74a96c0 Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876453] CS: 0010 DS: 002b ES: 002b CR0: 8005003b Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876454] CR2: 7fa1566220a0 CR3: 000514e5d000 CR4: 06e0 Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876456] DR0: DR1: DR2: Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876458] DR3: DR6: 0ff0 DR7: 0400 Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876460] Call Trace: Feb 8 18:20:04 server-i7_920 kernel: [ 3003.130843] INFO: task cron:8748 blocked for more than 120 seconds. Feb 8 18:20:04 server-i7_920 kernel: [ 3003.130874] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Feb 8 18:20:04 server-i7_920 kernel: [ 3003.130919] cron D 0 8748 25441 0x0002 Feb 8 18:20:04 server-i7_920 kernel: [ 3003.130923] 88063ccf3250 0086 Feb 8 18:20:04 server-i7_920 kernel: [ 3003.130927] 88055c60c7e0 00d0 f9e0 88045d2bdfd8 Feb 8 18:20:04 server-i7_920 kernel: [ 3003.130931] 00015780 00015780 88055c60c7e0 88055c60cad8 Feb 8 18:20:04 server-i7_920 kernel: [ 3003.130934] Call Trace:
Processed: Re: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2
Processing commands for cont...@bugs.debian.org: forwarded 658662 https://bugs.freedesktop.org/show_bug.cgi?id=45801 Bug #658662 [linux-2.6] drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2 Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=45801'. End of message, stopping processing here. Please contact me if you need assistance. -- 658662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132873613922271.transcr...@bugs.debian.org
Bug#659169: marked as done ([2.6.32] BUG: soft lockup - CPU#7 stuck for 17163091979s! [init:9709])
Your message dated Wed, 8 Feb 2012 22:01:36 + with message-id 20120208220136.ge12...@decadent.org.uk and subject line Re: Bug#659169: [2.6.32] BUG: soft lockup - CPU#7 stuck for 17163091979s! [init:9709] has caused the Debian Bug report #659169, regarding [2.6.32] BUG: soft lockup - CPU#7 stuck for 17163091979s! [init:9709] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 659169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: linux-2.6 Version: 2.6.32-5 Severity: normal Hello, Today one of my servers stopped responding to some webs, ssh'ing into it was impossible. The ping worked and the ssh connection was starting but the shell didn't showed up after waiting a long time. Finally a hard-reset was needed in order to bring it back After the reboot I found this on kern.log # tail /var/log/kern.log Feb 1 09:41:00 server-i7_920 kernel: [17383037.287331] EXT4-fs (dm-29): mounted filesystem with ordered data mode Feb 5 09:38:15 server-i7_920 kernel: [17727613.769052] NOHZ: local_softirq_pending 100 Feb 7 05:56:07 server-i7_920 kernel: [17886689.887577] e1000e: eth0 NIC Link is Down Feb 7 05:59:05 server-i7_920 kernel: [17886867.166464] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 7 05:59:41 server-i7_920 kernel: [17886903.722727] e1000e: eth0 NIC Link is Down Feb 7 06:00:00 server-i7_920 kernel: [17886922.309159] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876326] BUG: soft lockup - CPU#7 stuck for 17163091979s! [init:9709] Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876371] Modules linked in: btrfs zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs ext4 jbd2 crc16 ext2 ipt_LOG sg xt_limit xt_tcpudp xt_state iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables dummy loop snd_pcm snd_timer snd soundcore snd_page_alloc ioatdma i2c_i801 i2c_core pcspkr dca psmouse evdev button serio_raw processor ext3 jbd mbcache dm_mod sd_mod crc_t10dif ahci libata uhci_hcd ehci_hcd scsi_mod usbcore nls_base e1000e thermal thermal_sys [last unloaded: scsi_wait_scan] Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876405] CPU 7: Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876406] Modules linked in: btrfs zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs ext4 jbd2 crc16 ext2 ipt_LOG sg xt_limit xt_tcpudp xt_state iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables dummy loop snd_pcm snd_timer snd soundcore snd_page_alloc ioatdma i2c_i801 i2c_core pcspkr dca psmouse evdev button serio_raw processor ext3 jbd mbcache dm_mod sd_mod crc_t10dif ahci libata uhci_hcd ehci_hcd scsi_mod usbcore nls_base e1000e thermal thermal_sys [last unloaded: scsi_wait_scan] Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876433] Pid: 9709, comm: init Not tainted 2.6.32-5-vserver-amd64 #1 X8STi Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876435] RIP: 0023:[f76c0430] [f76c0430] 0xf76c0430 Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876440] RSP: 002b:ffa6673c EFLAGS: 0296 Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876442] RAX: fff6 RBX: RCX: ffa6673c Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876443] RDX: f76c0430 RSI: 000f RDI: Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876445] RBP: 8101166e R08: R09: Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876447] R10: R11: R12: Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876448] R13: R14: R15: Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876451] FS: () GS:880016bc(0063) knlGS:f74a96c0 Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876453] CS: 0010 DS: 002b ES: 002b CR0: 8005003b Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876454] CR2: 7fa1566220a0 CR3: 000514e5d000 CR4: 06e0 Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876456] DR0: DR1: DR2: Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876458] DR3:
Bug#656331: RTL8168b/8111b with ASUS M2A-VM (SB600): Network device stays down after resume
Paul Menzel pm.deb...@googlemail.com :
[forget runtime PM]
[18764.958557] r8169 :02:00.0: PME# disabled
[18781.998004] r8169 :02:00.0: eth0: link down
^^
[18781.998024] r8169 :02:00.0: eth0: link down
^^
Two link events within 20 us. /me wonders...
The datasheet states [the PHYStatus] register is updated continuously at
maximum periods of 300us. but it is far from clear that the coherency
with the interrupt status register can be taken for granted. Hayes ?
Paul, can you try the hack below ?
diff --git a/drivers/net/ethernet/realtek/r8169.c
b/drivers/net/ethernet/realtek/r8169.c
index 7a0c800..6daca05 100644
--- a/drivers/net/ethernet/realtek/r8169.c
+++ b/drivers/net/ethernet/realtek/r8169.c
@@ -1278,6 +1278,7 @@ static void __rtl8169_check_link_status(struct net_device
*dev,
{
unsigned long flags;
+ udelay(500);
spin_lock_irqsave(tp-lock, flags);
if (tp-link_ok(ioaddr)) {
rtl_link_chg_patch(tp);
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20120208221644.ga25...@electric-eye.fr.zoreil.com
Bug#658662: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2
tags 658662 + upstream patch moreinfo
quit
Peter Colberg wrote:
cd9dde44f47501394b9f0715b6a36a92aa74c0d0 is the first bad commit
Yay, thanks much for this. :)
Please test the attached patch against the linux-3.2.y branch.
git remote add -f stable \
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
git checkout stable/linux-3.2.y
git am -3sc thepatch
make silentoldconfig; # reuse configuration
make deb-pkg; # optionally with -jnum
dpkg -i ../name of package
reboot
From: Keith Packard kei...@keithp.com
Date: Wed, 25 Jan 2012 08:16:25 -0800
Subject: drm/i915: Force explicit bpp selection for intel_dp_link_required
commit c898261c0dad617f0f1080bedc02d507a2fcfb92 upstream.
It is never correct to use intel_crtc-bpp in intel_dp_link_required,
so instead pass an explicit bpp in to this function. This patch
only supports 18bpp and 24bpp modes, which means that 10bpc modes will
be computed incorrectly. Fixing that will require more extensive
changes, and so must be addressed separately from this bugfix.
intel_dp_link_required is called from intel_dp_mode_valid and
intel_dp_mode_fixup.
* intel_dp_mode_valid is called to list supported modes; in this case,
the current crtc values cannot be relevant as the modes in question
may never be selected. Thus, using intel_crtc-bpp is never right.
* intel_dp_mode_fixup is called during mode setting, but it is run
well before ironlake_crtc_mode_set is called to set intel_crtc-bpp,
so using intel_crtc-bpp in this path can only ever get a stale
value.
Cc: Lubos Kolouch lubos.kolo...@gmail.com
Cc: Adam Jackson a...@redhat.com
Cc: sta...@vger.kernel.org
Reviewed-by: Daniel Vetter daniel.vet...@ffwll.ch
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=42263
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=44881
Tested-by: Dave Airlie airl...@redhat.com
Tested-by: cama...@picnicpark.org (Dell Latitude 6510)
Tested-by: Roland Dreier rol...@digitalvampire.org
Signed-off-by: Keith Packard kei...@keithp.com
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
drivers/gpu/drm/i915/intel_dp.c | 20 +---
1 files changed, 5 insertions(+), 15 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index 92b041b66e49..ac600910ffc6 100644
--- a/drivers/gpu/drm/i915/intel_dp.c
+++ b/drivers/gpu/drm/i915/intel_dp.c
@@ -208,17 +208,8 @@ intel_dp_link_clock(uint8_t link_bw)
*/
static int
-intel_dp_link_required(struct intel_dp *intel_dp, int pixel_clock, int
check_bpp)
+intel_dp_link_required(int pixel_clock, int bpp)
{
- struct drm_crtc *crtc = intel_dp-base.base.crtc;
- struct intel_crtc *intel_crtc = to_intel_crtc(crtc);
- int bpp = 24;
-
- if (check_bpp)
- bpp = check_bpp;
- else if (intel_crtc)
- bpp = intel_crtc-bpp;
-
return (pixel_clock * bpp + 9) / 10;
}
@@ -245,12 +236,11 @@ intel_dp_mode_valid(struct drm_connector *connector,
return MODE_PANEL;
}
- mode_rate = intel_dp_link_required(intel_dp, mode-clock, 0);
+ mode_rate = intel_dp_link_required(mode-clock, 24);
max_rate = intel_dp_max_data_rate(max_link_clock, max_lanes);
if (mode_rate max_rate) {
- mode_rate = intel_dp_link_required(intel_dp,
- mode-clock, 18);
+ mode_rate = intel_dp_link_required(mode-clock, 18);
if (mode_rate max_rate)
return MODE_CLOCK_HIGH;
else
@@ -683,7 +673,7 @@ intel_dp_mode_fixup(struct drm_encoder *encoder, struct
drm_display_mode *mode,
int lane_count, clock;
int max_lane_count = intel_dp_max_lane_count(intel_dp);
int max_clock = intel_dp_max_link_bw(intel_dp) == DP_LINK_BW_2_7 ? 1 :
0;
- int bpp = mode-private_flags INTEL_MODE_DP_FORCE_6BPC ? 18 : 0;
+ int bpp = mode-private_flags INTEL_MODE_DP_FORCE_6BPC ? 18 : 24;
static int bws[2] = { DP_LINK_BW_1_62, DP_LINK_BW_2_7 };
if (is_edp(intel_dp) intel_dp-panel_fixed_mode) {
@@ -701,7 +691,7 @@ intel_dp_mode_fixup(struct drm_encoder *encoder, struct
drm_display_mode *mode,
for (clock = 0; clock = max_clock; clock++) {
int link_avail =
intel_dp_max_data_rate(intel_dp_link_clock(bws[clock]), lane_count);
- if (intel_dp_link_required(intel_dp, mode-clock, bpp)
+ if (intel_dp_link_required(mode-clock, bpp)
= link_avail) {
intel_dp-link_bw = bws[clock];
intel_dp-lane_count = lane_count;
--
1.7.9
Processed: Re: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2
Processing commands for cont...@bugs.debian.org: tags 658662 + upstream patch moreinfo Bug #658662 [linux-2.6] drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2 Added tag(s) upstream, moreinfo, and patch. quit Stopping processing here. Please contact me if you need assistance. -- 658662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132874093922540.transcr...@bugs.debian.org
Re: Enabling CONFIG_KALLSYMS_ALL
Have you folks come to a decision on enabling CONFIG_KALLSYMS_ALL in wheezy? I can open a bug if that's better for your workflow, I just don't want this to be forgotten about. -Tim Abbott On 01/29/2012 04:13 PM, Tim Abbott wrote: On 01/29/2012 12:16 AM, Ben Hutchings wrote: On Thu, 2012-01-26 at 12:31 -0500, Tim Abbott wrote: Hello, Would it be possible to turn on CONFIG_KALLSYMS_ALL in the Debian kernel for Wheezy? It's a useful debugging option, and makes it easier to implement useful tools like Ksplice that inspect the code and data structures of the running kernel, in particular in relation to operating on modules (one can use System.map to look up addresses for data structures in the core kernel). Most other major Linux distributions have had CONFIG_KALLSYMS_ALL enabled in their kernels for some time now (RHEL, Fedora, Ubuntu, etc.). Isn't this redundant with the linux-image-*-dbg packages? Though those are much larger. Not entirely. You're right that those packages are huge, which makes them unwieldy. But there are other advantages of using kallsyms for symbol information: (1) kallsyms symbol information is available for out-of-tree modules, which don't always build/distribute the analogue of the linux-image-*-dbg packages. (2) With CONFIG_KALLSYMS_ALL, full symbol information is always available on the machine you're looking to debug. So you don't have to deal with tracking down the right version of the debug package (If you want to work with Debian systems that may have been up for a long time, you need a database of the mapping between `uname -a` and package version numbers in order to figure out which version of the linux-image-*-dbg package actually goes with the running kernel's vmlinux. And it's even harder to figure out which version of the linux-image-*-dbg package to use for an in-tree module, since it's possible that the linux-image-* package was upgraded on disk after boot, but before the kernel module of interest was loaded, and so the module isn't the one that goes with the vmlinux). (3) kallsyms provides a uniform interface across all the different Linux distributions for getting symbol information, that can be used directly by both kernel code and userspace code that's doing debugging, tracing, or patching. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f32f681.4080...@oracle.com
Bug#658662: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2
On Wed, Feb 08, 2012 at 04:42:01PM -0600, Jonathan Nieder wrote: tags 658662 + upstream patch moreinfo quit Peter Colberg wrote: cd9dde44f47501394b9f0715b6a36a92aa74c0d0 is the first bad commit Yay, thanks much for this. :) Please test the attached patch against the linux-3.2.y branch. git remote add -f stable \ git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git git checkout stable/linux-3.2.y git am -3sc thepatch make silentoldconfig; # reuse configuration make deb-pkg; # optionally with -jnum dpkg -i ../name of package reboot From: Keith Packard kei...@keithp.com Date: Wed, 25 Jan 2012 08:16:25 -0800 Subject: drm/i915: Force explicit bpp selection for intel_dp_link_required commit c898261c0dad617f0f1080bedc02d507a2fcfb92 upstream. Thanks, but I just tested this patch (again). It is included in drm-intel-fixes, and it does not fix the regression: https://bugs.freedesktop.org/show_bug.cgi?id=45801#c5 Given that the problem persists, at least my bisect was not in vain ;-). Peter -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120208225821.GA4814@alcyone
Processed: Re: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2
Processing commands for cont...@bugs.debian.org: tags 658662 - patch moreinfo Bug #658662 [linux-2.6] drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2 Removed tag(s) moreinfo and patch. quit Stopping processing here. Please contact me if you need assistance. -- 658662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132874192827262.transcr...@bugs.debian.org
Bug#605210: marked as done (linux-image-2.6.32-5-amd64: cdrom stops working)
Your message dated Wed, 8 Feb 2012 18:04:22 -0600
with message-id 20120209000422.GA12706@burratino
and subject line Re: linux-image-2.6.32-5-amd64: cdrom stops working
has caused the Debian Bug report #605210,
regarding linux-image-2.6.32-5-amd64: cdrom stops working
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
605210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-27
Severity: important
If a cdrom is inserted, things work for a short while. I can for instance read
one or two
files on the CD. But, invariably, it stops working and a number of error
messages are logged.
Typical messages are:
[ 329.673137] UDF-fs: Partition marked readonly; forcing readonly mount
[ 329.740260] UDF-fs INFO UDF: Mounting volume 'Antidote HD', timestamp
2010/06/30 16:20 (1000)
[ 446.568967] ata6: drained 32768 bytes to clear DRQ.
[ 446.575346] ata6.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 446.575352] sr 5:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 07 85 00 00 1f 00
[ 446.575368] ata6.01: cmd a0/01:00:00:00:f8/00:00:00:00:00/b0 tag 0 dma 63488
in
[ 446.575369] res 40/00:02:08:08:00/00:00:00:00:00/b0 Emask 0x4
(timeout)
[ 446.575373] ata6.01: status: { DRDY }
[ 446.575426] ata6: soft resetting link
[ 451.728152] ata6.01: qc timeout (cmd 0xa1)
[ 451.728172] ata6.01: failed to IDENTIFY (I/O error, err_mask=0x5)
[ 451.728175] ata6.01: revalidation failed (errno=-5)
[ 451.728225] ata6: soft resetting link
[ 461.884122] ata6.01: qc timeout (cmd 0xa1)
[ 461.884141] ata6.01: failed to IDENTIFY (I/O error, err_mask=0x5)
[ 461.884145] ata6.01: revalidation failed (errno=-5)
[ 461.884195] ata6: soft resetting link
[ 492.040124] ata6.01: qc timeout (cmd 0xa1)
[ 492.040144] ata6.01: failed to IDENTIFY (I/O error, err_mask=0x5)
[ 492.040147] ata6.01: revalidation failed (errno=-5)
[ 492.040151] ata6.01: disabled
[ 492.040265] ata6: soft resetting link
[ 492.196802] ata6: EH complete
[ 492.196832] sr 5:0:1:0: [sr0] Unhandled error code
[ 492.196835] sr 5:0:1:0: [sr0] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 492.196839] sr 5:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 07 85 00 00 1f 00
[ 492.196850] end_request: I/O error, dev sr0, sector 7700
[ 492.196856] Buffer I/O error on device sr0, logical block 1925
[ 492.196864] Buffer I/O error on device sr0, logical block 1926
[ 492.196867] Buffer I/O error on device sr0, logical block 1927
[ 492.196871] Buffer I/O error on device sr0, logical block 1928
[ 492.196874] Buffer I/O error on device sr0, logical block 1929
[ 492.196878] Buffer I/O error on device sr0, logical block 1930
[ 492.196881] Buffer I/O error on device sr0, logical block 1931
[ 492.196885] Buffer I/O error on device sr0, logical block 1932
[ 492.196888] Buffer I/O error on device sr0, logical block 1933
[ 492.196891] Buffer I/O error on device sr0, logical block 1934
[ 492.196927] sr 5:0:1:0: [sr0] Unhandled error code
[ 492.196929] sr 5:0:1:0: [sr0] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 492.196933] sr 5:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 07 85 00 00 01 00
[ 492.196943] end_request: I/O error, dev sr0, sector 7700
[ 492.197355] VFS: busy inodes on changed media or resized disk sr0
[ 492.197851] VFS: busy inodes on changed media or resized disk sr0
[ 492.200278] VFS: busy inodes on changed media or resized disk sr0
(Then quite a few more of these. They continue after the cd has been reomved.)
I have tried another drive and get the same errors, so I don't think the
problem is
related to the drive itself. A harddisk is attached to the same controller,
making
a controller error a little less likely.
The problem has been around for a while. Less than a year, but certainly for
several
kernel versions.
-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-27) (m...@debian.org) (gcc version
4.3.5 (Debian 4.3.5-4) ) #1 SMP Sat Oct 30 14:18:21 UTC 2010
** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64
root=UUID=4213b79c-6f32-4f5d-9690-825d96ebc45f ro quiet
** Not tainted
** Kernel log:
See above.
** Model information
sys_vendor:
product_name:
product_version:
chassis_vendor:
chassis_version:
bios_vendor: Award Software International, Inc.
bios_version: F2
board_vendor: Gigabyte Technology Co., Ltd.
board_name: 965GM-S2
board_version: x.x
** Loaded modules:
Module Size Used by
udf66628 1
binfmt_misc 6431 1
Bug#659169: Re: Bug#659169: [2.6.32] BUG: soft lockup - CPU#7 stuck for 17163091979s! [init:9709]
On -10/01/37 20:59, Ben Hutchings wrote: Version: 2.6.32-40 On Wed, Feb 08, 2012 at 10:13:50PM +0100, Carlos Alberto Lopez Perez wrote: Source: linux-2.6 Version: 2.6.32-5 Severity: normal Hello, Today one of my servers stopped responding to some webs, ssh'ing into it was impossible. The ping worked and the ssh connection was starting but the shell didn't showed up after waiting a long time. Finally a hard-reset was needed in order to bring it back After the reboot I found this on kern.log # tail /var/log/kern.log Feb 1 09:41:00 server-i7_920 kernel: [17383037.287331] EXT4-fs (dm-29): mounted filesystem with ordered data mode Feb 5 09:38:15 server-i7_920 kernel: [17727613.769052] NOHZ: local_softirq_pending 100 Feb 7 05:56:07 server-i7_920 kernel: [17886689.887577] e1000e: eth0 NIC Link is Down Feb 7 05:59:05 server-i7_920 kernel: [17886867.166464] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 7 05:59:41 server-i7_920 kernel: [17886903.722727] e1000e: eth0 NIC Link is Down Feb 7 06:00:00 server-i7_920 kernel: [17886922.309159] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Feb 8 17:28:57 server-i7_920 kernel: [18446744016.876326] BUG: soft lockup - CPU#7 stuck for 17163091979s! [init:9709] [...] This appears to be the bug fixed by 'sched, x86: Avoid unnecessary overflow in sched_clock', included in longterm update 2.6.32.50 and Debian package version 2.6.32-40. That bug would be triggered once the scheduler clock reached 18014398 seconds, which is a little after the last reasonable time seen in this log. Ben. Wow! Really amazing, thanks for the reply. I will be upgrading the kernel ASAP. Regards! -- ~~~ Carlos Alberto Lopez Perez http://neutrino.es Igalia - Free Software Engineeringhttp://www.igalia.com ~~~ signature.asc Description: OpenPGP digital signature
Bug#658759: [arm/kirkwood] compressed image does not boot
On Mon, 2012-02-06 at 15:30 -0600, purdyd tds.net wrote: Thanks, Ian. I understand. Do any of you know if there are any ready-rolled u-boot binaries for Dockstar available out there that incorporate this fix? No idea I'm afraid. Given that #658759 has been filed against u-boot in Debian I expect a new package will be along shortly. Ian. Perhaps tbm's u-boot upgrades here : ?? http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html thnx, Davy On Mon, Feb 6, 2012 at 3:08 PM, Ian Campbell i...@hellion.org.uk wrote: On Mon, 2012-02-06 at 11:42 -0600, Jonathan Nieder wrote: Ian Campbell wrote: I suspect this is due to the lack of this u-boot patch: http://lists.denx.de/pipermail/u-boot/2012-February/117020.html I found that without this my 3.2 dreamplug kernel would not boot (with the 2011.12-2 package from debian). It's related to CONFIG_ARM_PATCH_PHYS_VIRT. For the record, this proposed u-boot change has been filed as http://bugs.debian.org/658904. The inability to work with versions of u-boot without that change (workaround?) in the default configuration still would seem to be a regression in the kernel, so pointers toward solving it would be very welcome. I hacked my kernel (the Kconfig files) to allow me to turn off PATCH_PHYS_VIRT and it also worked. However AIUI PATCH_VIRT_PHYS is part of the infrastructure which allows a single kernel flavour to boot on multiple machines so turning it off is not a viable workaround. I think this is just a latent bug in u-boot which has been exposed by a recent kernel changes and should be treated as a bug to be fixed in u-boot. I personally wouldn't consider it a regression in the kernel (at least based on my understanding of what's going on). Ian. -- Ian Campbell It'll be a nice world if they ever get it finished. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1328769377.13189.79.ca...@dagon.hellion.org.uk
