Bug#644550: indefinite soft lockup on rm
Attached. It makes no sense for me. And it doesn't seem to contain the _CST table, maybe because these being disabled in BIOS? Yep, I meant acpidump with c-states enabled. But don't worry about it. It's at http://joni.heaven-industries.com/~egon/tornado/acpidump-cst-enabled.txt (much bigger now with C-states enabled) Here's the best article on such trouble I can find from a quick search: [1]. Do you happen to know the name of the erratum, or an Intel document describing it? No. Nothing else an ordinary guy may find on web: http://www.intel.com/content/www/us/en/processors/xeon/xeon-e7-8800-4800-2800-families-specification-update.html ...there are quite a few mentioning C-states. I don't see any relevant fixes upstream recently, but please confirm the problem with a 3.2 release candidate from experimental, and then we should take this upstream (that means the linux...@vger.kernel.org list, cc-ing Len Brown l...@kernel.org, linux-ker...@vger.kernel.org, and either me or this bug log so we can track it). Actually, 3.2.0rc4 seems to run well! The big (and relevant) change since the squeeze kernel is that the new has the intel_idle driver (which kicks in instead of the acpi_idle): (2.6.32) root@tornado:/sys/devices/system/cpu/cpu0/cpuidle# grep . */* state0/desc:CPUIDLE CORE POLL IDLE state0/latency:0 state0/name:C0 state0/power:4294967295 state0/time:735633 state0/usage:85 state1/desc:ACPI FFH INTEL MWAIT 0x0 state1/latency:1 state1/name:C1 state1/power:1000 state1/time:457743320 state1/usage:49228 state2/desc:ACPI FFH INTEL MWAIT 0x10 state2/latency:64 state2/name:C2 state2/power:500 state2/time:86053513 state2/usage:47278 state3/desc:ACPI FFH INTEL MWAIT 0x20 state3/latency:96 state3/name:C3 state3/power:350 state3/time:1759785634 state3/usage:365191 (3.2.0rc4) root@tornado:/sys/devices/system/cpu/cpu0/cpuidle# grep . */* state0/desc:CPUIDLE CORE POLL IDLE state0/latency:0 state0/name:POLL state0/power:4294967295 state0/time:1985644 state0/usage:9221 state1/desc:MWAIT 0x00 state1/latency:3 state1/name:C1-NHM state1/power:4294967294 state1/time:411021632 state1/usage:9459157 state2/desc:MWAIT 0x10 state2/latency:20 state2/name:C3-NHM state2/power:4294967293 state2/time:1632399690 state2/usage:2649168 state3/desc:MWAIT 0x20 state3/latency:200 state3/name:C6-NHM state3/power:4294967292 state3/time:51728887664 state3/usage:8613936 ...and it possibly takes care somehow better, even when it (as it seems) allows the CPU to enter the deeper (and Nehalem/Westmere problematic?) states too. However, I am able to trigger the lockup just once a day, so it would need more testing. So far I only know that the experimental kernel survived once the same test case that crashes the squeeze kernel reliably (with no kernel cmdline tweaks regarding idle behavior). So regarding an eventual 2.6.32.x patch, I'm not sure what to think of about, an ACPI blacklist update perhaps? Now I'm switching back to stable kernel (as it's the one the company wants to run in the long term) and I will try to confirm the processor.max_cstate acpi_idle driver cmdline option workaround. I'll be back. Thanks, Egon -- 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/20111209092630.ga6...@heaven-industries.com
Bug#613321: linux-image-amd64: Please enable 'memtest' option for all linux kernels
Hello Dimitry, Since I am only responding to you and not to a list where others interested in the conversation that might not have read it are involved, I will top post as opposed to posting inline, this ensures brevity in my response as well as not requiring you to search out my response. OK. since memtest has traditionally always been a separate binary, not a part of the kernel. It would seem to me that if it is indeed now a part of the kernel, which I doubt, then it may well be an experimental feature requiring further testing before being released into the wild. there we have it. Robert G. Moonen On 12/1/11, Dmitry Smirnov only...@member.fsf.org wrote: I would like to reopen this discussion since there are some unanswered questions. Are we censoring certain Linux Kernel features because they are not good enough? If so, * How do we decide what experimental feature is OK? (For example we have btrfs along with many other things, long before they will become useful) * What's the decision criteria? It appears to me that particularly MEMTEST was refused purely because of prejudice rather than risk assessment. It is probably obvious to everyone that MEMTEST is harmless. Then why not enable it without painful discussions? What's our reason/excuse? (I think arguments like it is not good enough won't be qualified as reasonable answer due to availability of many other experimental features.) If just few requests for a feature is not enough to convince that we need it, how many people should ask, exactly, in order to make the change? (If I shall I start gathering signatures for petition, how many do I need? ;) Thank you. Regards, Dmitry. -- 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/CAOhUKb42iNZqmWTzhtVYW2uPEcr8=E_o=gkkeshmz_+jyif...@mail.gmail.com
Bug#590658: BUG in kmem_cache_alloc called by gss_create_cred
Le 11/27/2011 07:28 AM, Jonathan Nieder a écrit : tags 590658 + moreinfo quit Hi Victor, Victor Gomes Do Vale wrote: I have a desktop machine running debian lenny, with nfs4/kerberos for home directory accounting, which works great on my own machine. But on a specific machine, it kernel panics all nights, when the user come back the day, the machine is freezed, sometime I have logs of the kernel Oops, when i have an open ssh connection to the machine : [...] It seems to happened always on the same stack state (kmem_cache_alloc/gss... etc ...) I keep the machine up to date, but it does not correct the problem. If someone could correct that ... [...] Well, I tested the memory with memtest86, it gave me nothing (2 pass clear). I booted and set the X with vesa mode and nvidia unloaded yesterday, the machine was dead this morning. Thanks for reporting it. Basic questions: - Are you still using this machine? If so, how are you coping? --- what kernel do you use, did you find any workarounds, etc - If the slab corruption stopped happening at some point, do you remember when and whether anything interesting happened at the time? /var/log/dpkg.log* might have clues. - If the symptoms are still reproducible, please attach a log of the kernel's initialization (you can get it by capturing full dmesg output immediately after booting or by collecting from /var/log/dmesg*). - I assume this was not a regression, and that you always experienced these problems on this machine? - Any other clues or weird symptoms would be useful, too. Hope that helps, Jonathan Hi, Sorry for the late answer, well the only way i found to bypass this problem is one of those two options : - Move the machine to squeeze... - use the lenny-backports and change the kernel to 2.6.32-bpo ... No more logs other ways, i think it might be a kernel problem on the nfs4 kerberized implementation. for old machines i used lenny-backports on squeeze for newly installed machines, no more bug since then. Cannot be 100% sure of it, since it was a random bug, so far so good no problem since i applied this workarround. Thanks for asking. -- Victor -- 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/4ee1dc3d.3000...@cellectis.com
Processed: reassign 650425 to rpcbind
Processing commands for cont...@bugs.debian.org: reassign 650425 rpcbind Bug #650425 [nfs-common] Please add options to set the port range for nfs clients Bug reassigned from package 'nfs-common' to 'rpcbind'. thanks Stopping processing here. Please contact me if you need assistance. -- 650425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650425 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.132342779222989.transcr...@bugs.debian.org
Bug#633034: marked as done (nfs-utils: /run transition: Please switch to /run/sendsigs.omit.d)
Your message dated Fri, 09 Dec 2011 11:18:08 + with message-id e1ryysu-0002s4...@franck.debian.org and subject line Bug#633034: fixed in nfs-utils 1:1.2.5-3 has caused the Debian Bug report #633034, regarding nfs-utils: /run transition: Please switch to /run/sendsigs.omit.d 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.) -- 633034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: nfs-utils Version: 1:1.2.3-3 Severity: important Your package is currently using/lib/init/rw/sendsigs.omit.d which is now deprecated and pending removal. Please update your package to use /run/sendsigs.omit.d with a versioned dependency on initscripts, as detailed below. An overview of the /run transition and its current progress is available at http://wiki.debian.org/ReleaseGoals/RunDirectory Basically, it's now in both testing and unstable, and the next phase of the transition is to migrate all users of /lib/init/rw over to /run and then remove /lib/init/rw entirely for wheezy (as soon as this transition is complete). Your package is one of the users of sendsigs.omit.d listed here: http://wiki.debian.org/ReleaseGoals/RunDirectory#Packages_using_.2BAC8-lib.2BAC8-init.2BAC8-rw Recommendations for how to do the transition may be found here: http://wiki.debian.org/ReleaseGoals/RunDirectory#How_to_transition_from_.2BAC8-lib.2BAC8-init.2BAC8-rw_to_.2BAC8-run.3F For sendsigs.omit.d, we would recommend that you: * Depend on initscripts (= 2.88dsf-13.3) * Replace *all* usage of /lib/init/rw with /run * Move all files in /lib/init/rw to /run in the package postinst, for example: if [ -f /lib/init/rw/sendsigs.omit.d/foo ]; then mv /lib/init/rw/sendsigs.omit.d/foo /run/sendsigs.omit.d/foo fi Regards, Roger ---End Message--- ---BeginMessage--- Source: nfs-utils Source-Version: 1:1.2.5-3 We believe that the bug you reported is fixed in the latest version of nfs-utils, which is due to be installed in the Debian FTP archive: nfs-common_1.2.5-3_i386.deb to main/n/nfs-utils/nfs-common_1.2.5-3_i386.deb nfs-kernel-server_1.2.5-3_i386.deb to main/n/nfs-utils/nfs-kernel-server_1.2.5-3_i386.deb nfs-utils_1.2.5-3.debian.tar.bz2 to main/n/nfs-utils/nfs-utils_1.2.5-3.debian.tar.bz2 nfs-utils_1.2.5-3.dsc to main/n/nfs-utils/nfs-utils_1.2.5-3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 633...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luk Claes l...@debian.org (supplier of updated nfs-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 09 Dec 2011 11:55:31 +0100 Source: nfs-utils Binary: nfs-kernel-server nfs-common Architecture: source i386 Version: 1:1.2.5-3 Distribution: unstable Urgency: low Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: Luk Claes l...@debian.org Description: nfs-common - NFS support files common to client and server nfs-kernel-server - support for NFS kernel server Closes: 633034 644358 651354 Changes: nfs-utils (1:1.2.5-3) unstable; urgency=low . [ Roger Leigh ] * /run transition: nfs-common migrates /lib/init/rw/sendsigs.omit.d/statd to /run/sendsigs.omit.d on upgrade, and uses /run/sendsigs.omit.d. Depend on initscripts (= 2.88dsf-13.3) to guarantee the existence of /run/sendsigs.omit.d (Closes: #633034). . [ Luk Claes ] * Version libgssglue-dev build dependency (Closes: #651354). . [ Luca Capello ] * debian/control: + add mount.nfs to the long Description: (Closes: #644358). Checksums-Sha1: 6d86e12a5eaeeb4fa5d48e491f14d97e63a3d2c1 1590 nfs-utils_1.2.5-3.dsc 412f356387834bb8f44d689e373165d9de7c0c12 35596 nfs-utils_1.2.5-3.debian.tar.bz2 b3d65944054438735592ea1ba9f068ab280424f3 165218 nfs-kernel-server_1.2.5-3_i386.deb f71ead8cafb2ef7341b040d53d437ab595a0f886 277160 nfs-common_1.2.5-3_i386.deb Checksums-Sha256: cb4ad4cb29b4bdb759f16bb126b5b5994a588d096ecf8787e2507a3ac8ec9695 1590 nfs-utils_1.2.5-3.dsc 887bf26da7bc1cfcd67dc5d9537933407d9beeb75231fc9a6e1f4a38d86f4269 35596 nfs-utils_1.2.5-3.debian.tar.bz2 6822d06e2eab9a5498a956c87411a577ec4c3b11c501bd9210c86f3ef1371dfd 165218
Bug#644358: marked as done (nfs-common: please include mount.nfs in the long Description:)
Your message dated Fri, 09 Dec 2011 11:18:08 + with message-id e1ryysu-0002s7...@franck.debian.org and subject line Bug#644358: fixed in nfs-utils 1:1.2.5-3 has caused the Debian Bug report #644358, regarding nfs-common: please include mount.nfs in the long Description: 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.) -- 644358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-common Version: 1:1.2.5-2 Severity: wishlist Tags: patch Usertags: unige.ch-jmlab Hi there! The long Description: does not contain any reference to mount.nfs, which means that `apt-cache search mount.nfs` returns no results. While nfs-common shows up with `apt-cache search mount nfs`, showmount is not really a good candidate ;-) Here is a patch, please consider it. I can provide a real Git patch when this bug will get a number, if needed. --8---cut here---start-8--- diff --git a/debian/changelog b/debian/changelog index 3f823a9..34392f2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +nfs-utils (1:1.2.5-3) UNRELEASED; urgency=low + + [ Luca Capello ] + * debian/control: ++ add mount.nfs to the long Description: (Closes: #NNN). + + -- + nfs-utils (1:1.2.5-2) unstable; urgency=low * debian/patches/18-dont-use-PAGE_SIZE.patch diff --git a/debian/control b/debian/control index 9ee0ed0..f90cfa1 100644 --- a/debian/control +++ b/debian/control @@ -39,6 +39,6 @@ Conflicts: nfs-client Replaces: nfs-client, nfs-kernel-server ( 1:1.0.7-5), mount ( 2.13~) Description: NFS support files common to client and server Use this package on any machine that uses NFS, either as client or - server. Programs included: lockd, statd, showmount, nfsstat, gssd - and idmapd. + server. Programs included: lockd, statd, showmount, nfsstat, gssd, + idmapd and mount.nfs. Homepage: http://nfs.sourceforge.net/ --8---cut here---end---8--- Thx, bye, Gismo / Luca -- Package-specific info: -- rpcinfo -- program vers proto port 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 53970 status 1000241 tcp 35220 status -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD= NEED_GSSD= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-rc7-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.113 ii initscripts 2.88dsf-13.11 ii libc6 2.13-21 ii libcap2 1:2.22-1 ii libcomerr2 1.42~WIP-2011-09-25-1 ii libdevmapper1.02.1 2:1.02.65-1 ii libevent-1.4-2 1.4.14b-stable-1 ii libgssapi-krb5-21.9.1+dfsg-3 ii libgssglue1 0.3-3 ii libk5crypto31.9.1+dfsg-3 ii libkeyutils11.5.2-2 ii libkrb5-3 1.9.1+dfsg-3 ii libnfsidmap20.24-1 ii libtirpc1 0.2.2-5 ii libwrap07.6.q-21 ii lsb-base3.2-28 ii rpcbind 0.2.0-6 ii ucf 3.0025+nmu2 Versions of packages nfs-common recommends: ii python 2.7.2-7 nfs-common suggests no packages. -- no debconf information pgpRz3k5jLPeH.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: nfs-utils Source-Version: 1:1.2.5-3 We believe that the bug you reported is fixed in the latest version of nfs-utils, which is due to be installed in the Debian FTP archive: nfs-common_1.2.5-3_i386.deb to main/n/nfs-utils/nfs-common_1.2.5-3_i386.deb nfs-kernel-server_1.2.5-3_i386.deb to main/n/nfs-utils/nfs-kernel-server_1.2.5-3_i386.deb nfs-utils_1.2.5-3.debian.tar.bz2 to main/n/nfs-utils/nfs-utils_1.2.5-3.debian.tar.bz2 nfs-utils_1.2.5-3.dsc to main/n/nfs-utils/nfs-utils_1.2.5-3.dsc A summary of the changes
Bug#651354: marked as done (nfs-utils: needs build-dep on libgssglue-dev (= 0.3))
Your message dated Fri, 09 Dec 2011 11:18:08 + with message-id e1ryysu-0002sa...@franck.debian.org and subject line Bug#651354: fixed in nfs-utils 1:1.2.5-3 has caused the Debian Bug report #651354, regarding nfs-utils: needs build-dep on libgssglue-dev (= 0.3) 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.) -- 651354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-utils Version: 1.2.5-2 trying to build a backport of nfs-utils 1.2.5-2 on squeeze shows: checking for GSSGLUE... no configure: error: Package requirements (libgssglue = 0.3) were not met: Requested 'libgssglue = 0.3' but version of libgssglue is 0.1 Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables GSSGLUE_CFLAGS and GSSGLUE_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [build-stamp] Error 1 I believe this means that the Build-Depends: on libgssglue-dev needs to be versioned to (= 0.3). Regards, --dkg pgpnJXTA7pdQb.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: nfs-utils Source-Version: 1:1.2.5-3 We believe that the bug you reported is fixed in the latest version of nfs-utils, which is due to be installed in the Debian FTP archive: nfs-common_1.2.5-3_i386.deb to main/n/nfs-utils/nfs-common_1.2.5-3_i386.deb nfs-kernel-server_1.2.5-3_i386.deb to main/n/nfs-utils/nfs-kernel-server_1.2.5-3_i386.deb nfs-utils_1.2.5-3.debian.tar.bz2 to main/n/nfs-utils/nfs-utils_1.2.5-3.debian.tar.bz2 nfs-utils_1.2.5-3.dsc to main/n/nfs-utils/nfs-utils_1.2.5-3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 651...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luk Claes l...@debian.org (supplier of updated nfs-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 09 Dec 2011 11:55:31 +0100 Source: nfs-utils Binary: nfs-kernel-server nfs-common Architecture: source i386 Version: 1:1.2.5-3 Distribution: unstable Urgency: low Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: Luk Claes l...@debian.org Description: nfs-common - NFS support files common to client and server nfs-kernel-server - support for NFS kernel server Closes: 633034 644358 651354 Changes: nfs-utils (1:1.2.5-3) unstable; urgency=low . [ Roger Leigh ] * /run transition: nfs-common migrates /lib/init/rw/sendsigs.omit.d/statd to /run/sendsigs.omit.d on upgrade, and uses /run/sendsigs.omit.d. Depend on initscripts (= 2.88dsf-13.3) to guarantee the existence of /run/sendsigs.omit.d (Closes: #633034). . [ Luk Claes ] * Version libgssglue-dev build dependency (Closes: #651354). . [ Luca Capello ] * debian/control: + add mount.nfs to the long Description: (Closes: #644358). Checksums-Sha1: 6d86e12a5eaeeb4fa5d48e491f14d97e63a3d2c1 1590 nfs-utils_1.2.5-3.dsc 412f356387834bb8f44d689e373165d9de7c0c12 35596 nfs-utils_1.2.5-3.debian.tar.bz2 b3d65944054438735592ea1ba9f068ab280424f3 165218 nfs-kernel-server_1.2.5-3_i386.deb f71ead8cafb2ef7341b040d53d437ab595a0f886 277160 nfs-common_1.2.5-3_i386.deb Checksums-Sha256: cb4ad4cb29b4bdb759f16bb126b5b5994a588d096ecf8787e2507a3ac8ec9695 1590 nfs-utils_1.2.5-3.dsc 887bf26da7bc1cfcd67dc5d9537933407d9beeb75231fc9a6e1f4a38d86f4269 35596 nfs-utils_1.2.5-3.debian.tar.bz2 6822d06e2eab9a5498a956c87411a577ec4c3b11c501bd9210c86f3ef1371dfd 165218 nfs-kernel-server_1.2.5-3_i386.deb f0fd2b1f875622729c95377a5cd375078f6b06081b94ba2df94dd4a8b0bcf89b 277160 nfs-common_1.2.5-3_i386.deb Files: 669bc6f831b7a7cefc0d1751ea20a1db 1590 net standard nfs-utils_1.2.5-3.dsc 447eae050c7e822a94e4dd74cdf8736c 35596 net standard nfs-utils_1.2.5-3.debian.tar.bz2 17f73b015d09307a3474b7c2874c3e47 165218 net optional nfs-kernel-server_1.2.5-3_i386.deb c3ddc651c5fbe3c3e65c5907809a8e33 277160 net standard nfs-common_1.2.5-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk7h7OsACgkQ5UTeB5t8Mo2xiQCbBu2/velMR2S8XOaEMcWr5Dw8
Processing of nfs-utils_1.2.5-3_i386.changes
nfs-utils_1.2.5-3_i386.changes uploaded successfully to localhost along with the files: nfs-utils_1.2.5-3.dsc nfs-utils_1.2.5-3.debian.tar.bz2 nfs-kernel-server_1.2.5-3_i386.deb nfs-common_1.2.5-3_i386.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1ryyla-0001vo...@franck.debian.org
nfs-utils_1.2.5-3_i386.changes ACCEPTED into unstable
Accepted: nfs-common_1.2.5-3_i386.deb to main/n/nfs-utils/nfs-common_1.2.5-3_i386.deb nfs-kernel-server_1.2.5-3_i386.deb to main/n/nfs-utils/nfs-kernel-server_1.2.5-3_i386.deb nfs-utils_1.2.5-3.debian.tar.bz2 to main/n/nfs-utils/nfs-utils_1.2.5-3.debian.tar.bz2 nfs-utils_1.2.5-3.dsc to main/n/nfs-utils/nfs-utils_1.2.5-3.dsc Override entries for your package: nfs-common_1.2.5-3_i386.deb - standard net nfs-kernel-server_1.2.5-3_i386.deb - optional net nfs-utils_1.2.5-3.dsc - source net Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 633034 644358 651354 Thank you for your contribution to Debian. -- 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/e1ryysu-0002ry...@franck.debian.org
Processed: affects 645308
Processing commands for cont...@bugs.debian.org: affects 645308 + release.debian.org Bug #645308 [linux-2.6] tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer Added indication that 645308 affects release.debian.org thanks Stopping processing here. Please contact me if you need assistance. -- 645308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645308 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.132345992924655.transcr...@bugs.debian.org
Bug#651558: nfs-utils: NFSv4 sec=krb5 clients must install nfs-kernel-server to use rpc.svcgssd to receive delegations
Package: nfs-utils Version: 1.2.5-2 According to J. Bruce Fields on the linux-nfs mailing list [0], NFSv4 clients using any sec=krb5 variant will need to run rpc.svcgssd to receive delegations. On debian, this appears to mean that the clients will need to install nfs-kernel-server, even if they do not intend to act as a server. Should rpc.svcgssd get moved out to the nfs-common package (or, if the fragmentation isn't too much, to its own package)? It doesn't seem like encouraging clients to run nfsd when they have no intention of serving files is a good idea. Another alternative is to consider encouraging NFSv4.1 instead of NFSv4 (apparently the delegations in 4.1 happen over the client-initiated channels instead of establishing new connections back), but this was only been enabled in debian kernels since 3.1. If moving the daemon implementation between packages isn't the right idea, it would at least be good to document what's going on here and what the recommended configuration is for decently-performing cryptographically-secured NFS. I see no mention of the multi-daemon requirement for clients in /usr/share/doc/nfs-common/README.Debian.nfsv4, for example. If i wasn't stumbling my way through this setup myself, i'd offer to write improved documentation, but i'm not in deep enough to know best-practices or advise others at the moment. Thanks for maintaining nfs-utils in debian, --dkg [0] http://thread.gmane.org/gmane.linux.nfs/45498/focus=45502 pgpKXhjyq6KSa.pgp Description: PGP signature
Bug#651532: System crashes (kernel oops) when loading ATI firmware
reassign 651532 src:linux-2.6 3.1.1-1 quit Hi, Camaleón wrote: As soon as the firmware package is removed (which means no more 3D accelerated graphics capabilities) the system runs normally and no kernel oops presents. root@linux:~# lspci | grep VGA 01:00.0 VGA compatible controller: ATI Technologies Inc M56P [Radeon Mobility X1600] [...] radeon :01:00.0: GPU lockup CP stall for more than 10040msec [ cut here ] WARNING: at /build/buildd-linux-2.6_3.1.1-1-i386-6vi5gY/linux-2.6-3.1.1/debian/build/source_i386_none/drivers/gpu/drm/radeon/radeon_fence.c:267 radeon_fence_wait+0x22e/0x298 [radeon]() Hardware name: iMac5,1 GPU lockup (waiting for 0x5C23 last fence id 0x5C20) Thanks for reporting it. Can you reproduce this without the virtualbox and wl drivers? There have been some changes in this area recently upstream (e.g., v3.2-rc1~135^2~5 and v3.2-rc1~11^2~10). Please test with v3.2-rc4 or later from experimental, and if it still exhibits the problem, send a summary to https://bugs.freedesktop.org/, product DRI, component DRM/Radeon and let us know the bug number so we can track it. In your summary, be sure to include steps to reproduce the trouble, any visible symptoms, /var/log/Xorg.0.log, full dmesg output from booting and reproducing the bug, and a link to http://bugs.debian.org/651532 in case readers want the full story. 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/20111210004817.ga3...@elie.hsd1.il.comcast.net
Processed: tagging 651469
Processing commands for cont...@bugs.debian.org: tags 651469 + pending Bug #651469 [linux-2.6] linux-image-3.1.0-1-amd64: sky2 rx checksum failures on linux-image 3.1 with xen Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 651469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651469 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.132347799814201.transcr...@bugs.debian.org
Processed: tagging 651015
Processing commands for cont...@bugs.debian.org: tags 651015 + pending Bug #651015 [linux-2.6] linux-image-3.1.0-1-amd64: Turtle Beach USB Audio fails with Sandy Bridge USB 2.0 controller Ignoring request to alter tags of bug #651015 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 651015: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651015 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.132347800114226.transcr...@bugs.debian.org
Processed: tagging 586494
Processing commands for cont...@bugs.debian.org: tags 586494 + pending Bug #586494 [linux-2.6] linux-image-2.6.26-2-686: Dell PowerEdge 4200's don't work with 2.6.26 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 586494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586494 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.132347800514260.transcr...@bugs.debian.org
Processed: Re: System crashes (kernel oops) when loading ATI firmware
Processing commands for cont...@bugs.debian.org: reassign 651532 src:linux-2.6 3.1.1-1 Bug #651532 [linux-image-3.1.0-1-686-pae] System crashes (kernel oops) when loading ATI firmware Bug reassigned from package 'linux-image-3.1.0-1-686-pae' to 'src:linux-2.6'. Bug No longer marked as found in versions linux-2.6/3.1.4-1. Bug #651532 [src:linux-2.6] System crashes (kernel oops) when loading ATI firmware Bug Marked as found in versions linux-2.6/3.1.1-1. quit Stopping processing here. Please contact me if you need assistance. -- 651532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651532 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.132347811014958.transcr...@bugs.debian.org
Processed: tagging 586494
Processing commands for cont...@bugs.debian.org: tags 586494 + pending Bug #586494 [linux-2.6] linux-image-2.6.26-2-686: Dell PowerEdge 4200's don't work with 2.6.26 Ignoring request to alter tags of bug #586494 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 586494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586494 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.132348064831371.transcr...@bugs.debian.org
Processed: tagging 651367
Processing commands for cont...@bugs.debian.org: tags 651367 + pending Bug #651367 [src:linux-2.6] Changes from longterm release 2.6.32.50 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 651367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651367 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.132348064931383.transcr...@bugs.debian.org
Processed (with 1 errors): Re: BUG in kmem_cache_alloc called by gss_create_cred
Processing commands for cont...@bugs.debian.org: Version: 2.6.32-35 Unknown command or malformed arguments to command. tags 590658 - moreinfo Bug #590658 [linux-2.6] linux-image-2.6.26-2-686-bigmem: 2.6.26-2 bigmem nfs4 kerberos kernel panic Removed tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 590658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590658 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.132348335710919.transcr...@bugs.debian.org
Bug#590658: marked as done (linux-image-2.6.26-2-686-bigmem: 2.6.26-2 bigmem nfs4 kerberos kernel panic)
Your message dated Fri, 9 Dec 2011 20:15:47 -0600 with message-id 20111210021547.gb6...@elie.hsd1.il.comcast.net and subject line Re: BUG in kmem_cache_alloc called by gss_create_cred has caused the Debian Bug report #590658, regarding linux-image-2.6.26-2-686-bigmem: 2.6.26-2 bigmem nfs4 kerberos kernel panic 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.) -- 590658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.26-24 Severity: critical Justification: breaks the whole system I have a desktop machine running debian lenny, with nfs4/kerberos for home directory accounting, which works great on my own machine. But on a specific machine, it kernel panics all nights, when the user come back the day, the machine is freezed, sometime I have logs of the kernel Oops, when i have an open ssh connection to the machine : Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [ cut here ] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] invalid opcode: [#1] SMP Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] Process gdm (pid: 2854, ti=f3d54000 task=f797c280 task.ti=f3d54000) Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] Stack: 001e 80d0 f7401480 f744d200 0043 Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275]f7429e80 f017a790 0001 f8a2ec80 f7401480 0246 80d0 c017b969 Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275]f8a2ec80 f35be404 f363a474 f8a2b189 f8a2ec80 f30dfd0c Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] Call Trace: Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [c017b969] kmem_cache_alloc+0x47/0x87 Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [f8a2b189] gss_create_cred+0x32/0x94 [auth_rpcgss] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [fa22792b] rpcauth_lookup_credcache+0x92/0x177 [sunrpc] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [fa227fb6] generic_bind_cred+0x15/0x27 [sunrpc] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [fa227733] rpcauth_bindcred+0x17/0xaa [sunrpc] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [c015d7b2] find_get_pages_tag+0x2a/0x6e Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [fa226573] rpc_new_task+0xee/0x145 [sunrpc] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [fa221a3b] rpc_run_task+0x9/0x45 [sunrpc] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [fa2a032b] nfs_write_rpcsetup+0x202/0x218 [nfs] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [fa2a1749] nfs_flush_one+0x72/0xa0 [nfs] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [fa29d63e] nfs_pageio_doio+0x22/0x47 [nfs] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [fa2a0763] nfs_writepages+0x57/0x72 [nfs] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [fa2a16d7] nfs_flush_one+0x0/0xa0 [nfs] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [fa2a0ee3] __nfs_write_mapping+0xf/0x3b [nfs] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [fa2a0f43] nfs_write_mapping+0x34/0x52 [nfs] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [fa296c57] nfs_do_fsync+0x13/0x2d [nfs] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [fa296f26] nfs_file_write+0x13d/0x15f [nfs] Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [c017e3d2] do_sync_write+0xbf/0x100 Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [c013882c] autoremove_wake_function+0x0/0x2d Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [c01c4da9] security_file_permission+0xc/0xd Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [c017e313] do_sync_write+0x0/0x100 Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [c017eb44] vfs_write+0x83/0x120 Message from syslogd@lagune at Jul 28 02:36:02 ... kernel:[63659.784275] [c017f116] sys_write+0x3c/0x63 Message from
Bug#644550: marked as done (linux-image-2.6.32-5-amd64: indefinite soft lockup on rm)
Your message dated Fri, 9 Dec 2011 21:10:58 -0600 with message-id 20111210031058.gd6...@elie.hsd1.il.comcast.net and subject line Re: indefinite soft lockup on rm has caused the Debian Bug report #644550, regarding linux-image-2.6.32-5-amd64: indefinite soft lockup on rm 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.) -- 644550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-38 Severity: important Tags: upstream Hi, the lockup happened on unlinking a large file (several GB) on XFS on fibre channel storage (qla2xxx module). We experience very simiral trouble on this machine though, using other kernels (from stable, stable-backports and sid as well) and other fs/storage combinations (ext4 on local Dell PERC controller). This would normally suggest a HW problem, but this time it's unlikely IMO. The machine is new and survived many hours of memtest86-ing. Unfortunately we have no second identical machine to replicate it. The only HW issue I admit is the availability of newer BIOS, which will be flashed next week (sorry if you find this to be an obvious reason of the problem). As I said, the other kernels crash too showing similar backtraces. I think the (eventual) kernel bug may relate to relatively unusual configuration of this machine, which is a NUMA with 64GB RAM, getting probably not that much beating (I mean testing) as the more common desktop PCs. Could the unending find_get_pages indicate slab corruption perhaps? The full boot-time dmesg output may be found on http://joni.heaven-industries.com/~egon/tornado-dmesg.txt The bug is not too easy to trigger, so I hope there's another way to look for it than bisecting 5 years of kernel commits... On the other hand, I'm of course ready to spend a time on it if it helps to make the kernel better :). Thanks, Egon -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-38) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Oct 3 03:59:20 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=5b5632ae-3e39-4c83-baa6-cc1bb09996a4 ro quiet log_buf_len=512k video=matroxfb:vesa:0x1B8 ** Not tainted ** Kernel log: [26901.529927] BUG: soft lockup - CPU#2 stuck for 61s! [rm:4357] [26901.532682] Modules linked in: nls_utf8 cifs nfs lockd fscache nfs_acl auth_rpcgss sunrpc bonding ext4 jbd2 crc16 xfs exportfs dm_round_robin scsi_dh_emc dm_multipath scsi_dh uvesafb cn snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr psmouse evdev joydev power_meter dcdbas button processor serio_raw ext2 mbcache dm_mod sg sr_mod cdrom ata_generic usbhid hid sd_mod ses crc_t10dif enclosure uhci_hcd ata_piix qla2xxx scsi_transport_fc libata scsi_tgt ehci_hcd megaraid_sas usbcore thermal nls_base scsi_mod bnx2 thermal_sys [last unloaded: scsi_wait_scan] [26901.532720] CPU 2: [26901.532721] Modules linked in: nls_utf8 cifs nfs lockd fscache nfs_acl auth_rpcgss sunrpc bonding ext4 jbd2 crc16 xfs exportfs dm_round_robin scsi_dh_emc dm_multipath scsi_dh uvesafb cn snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr psmouse evdev joydev power_meter dcdbas button processor serio_raw ext2 mbcache dm_mod sg sr_mod cdrom ata_generic usbhid hid sd_mod ses crc_t10dif enclosure uhci_hcd ata_piix qla2xxx scsi_transport_fc libata scsi_tgt ehci_hcd megaraid_sas usbcore thermal nls_base scsi_mod bnx2 thermal_sys [last unloaded: scsi_wait_scan] [26901.532745] Pid: 4357, comm: rm Not tainted 2.6.32-5-amd64 #1 PowerEdge R810 [26901.532747] RIP: 0010:[810b4155] [810b4155] find_get_pages+0x5f/0xbb [26901.532758] RSP: 0018:88087a771d58 EFLAGS: 0297 [26901.532760] RAX: RBX: 88087a771df8 RCX: [26901.532761] RDX: 0059ed9a RSI: ea0004412fe8 RDI: ea0004412fe0 [26901.532763] RBP: 8101166e R08: ffc0 R09: 000d [26901.532764] R10: 0019 R11: 880ac952fb60 R12: 0292 [26901.532766] R13: 88088000 R14: 880880002d00 R15: 0002 [26901.532768] FS: 7f4c706fa700() GS:88001da2() knlGS: [26901.532770] CS: 0010 DS: ES: CR0: 8005003b [26901.532771] CR2: 7f4c70254060 CR3: 0005ac93b000 CR4: 06e0 [26901.532773] DR0: DR1: DR2: [26901.532774] DR3: DR6: 0ff0 DR7: 0400 [26901.532776] Call Trace:
Uploading linux-2.6 (3.1.5-1)
I intend to upload linux-2.6 version 3.1.5-1 to unstable this weekend. This is another upstream stable update. It also includes a fix for the FTBFS on mips/mipsel in 3.1.4-1. No ABI bump seems to be necessary. Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else. signature.asc Description: This is a digitally signed message part
Bug#598144: rt2500pci: very low transfers and link quality
tags 598144 = unreproducible quit David Sanchez Herrero wrote: Thanks for reply about this problem, but the laptop with rt2500 wireless card died 6 or 7 months ago (a graphic card crash), so I can't try the 3.1 kernel version. Alas. Hopefully some hero with the same hardware can come and save us by trying v2.6.39-rc1 or later. Marking accordingly. Finally, after analyzing my laptop's hard disk, I have remembered the final solution, that was using Ndiswrapper with rt2500 Windows drivers. It was the only way... That's useful --- it tells us that the hardware was ok. Regards, 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/20111210055945.gg6...@elie.hsd1.il.comcast.net
Processed: Re: rt2500pci: very low transfers and link quality
Processing commands for cont...@bugs.debian.org: tags 598144 = unreproducible Bug #598144 [linux-2.6] rt2500pci: very low transfers and link quality Added tag(s) unreproducible; removed tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 598144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598144 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.132349679630166.transcr...@bugs.debian.org
