Bug#701744: Xen netback regression
Am 04.07.2013 um 05:42 schrieb Ben Hutchings b...@decadent.org.uk: My understanding is that disabling scatter/gather on netfront in domU (ethtool -K eth0 sg off) will prevent it from triggering these bugs, but at a substantial performance impact. In practice, disabling TSO in domU (ethtool -K eth0 tso off) should also work and will have a smaller performance impact. However, a malicious domU would still be able to crash dom0. Thanks, Ben, for updating us on this issue! Crashing dom0 seems to happen on my Cisco C200 M2 server lately, maybe unrelated to this bug, maybe not. At least my server sometimes gets a restart command from the operating system. We see this in the CIMC (management console) logs and Cisco already confirmed that the reboot command is issued by the OS. On the other hand I see absolutely no hint or cause in the system log files, neither on dom0, nor domU nor the hypervisor logs, which makes it difficult to track down the reason for the random reboots of the whole machine. I'm using the ethtool workaround in some of my 8 running domUs, but not in all. No ethtool workaround in dom0 as well. As Ian requested, the netback fixes were included in Linux 3.2.47 and thus should appear in the wheezy-proposed-updates suite shortly. Aside from that, any regression that occurred as a result of a security update may also be fixed in a security update, and I hope we will be able to provide such updates for both Debian 6 (squeeze) and 7 (wheezy) in the next few weeks. Do you have a suggestion of in the next few weeks? The crashing server really gets annoying: sometimes it reboots several times per day, sometimes it runs for a week or so. We are close to open a TAC case with Cisco about the crashing server, but would like to be sure that it's not the kernel which is causing this, of course. ;) -- Ciao...// Fon: 0381-2744150 Ingo \X/ http://blog.windfluechter.net gpg pubkey: http://www.juergensmann.de/ij_public_key.asc -- 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/ebf914fa-8d50-4b64-b48c-57df00b65...@2013.bluespice.org
Bug#714729: linux-image-3.2.0-4-amd64: Kernel trace swapper: page allocation failure in combination with Intel ixgbe
Hi, many thanks for the fast reply! On 02.07.2013 15:16, Ben Hutchings wrote: Control: fixed -1 3.4.1-1~experimental.1 On Tue, 2013-07-02 at 10:42 +0200, Udo Lembke wrote: Package: src:linux Version: 3.2.46-1 Severity: important Tags: upstream Dear Maintainer, we running three nodes as ceph-cluster (0.61.3-1~bpo70+1) and sometimes (app. once or twice a day) we got an kernel trace which seems to be related to the Intel 10GB-NIC (ixgbe module). The same happens before update (from: SMP Debian 3.2.41-2+deb7u2 x86_64 GNU/Linux) and also occur with an actual self-compiled ixgbe-module (3.15.1). The page allocation failure are not only swapper related. Also ceph-osd and kswapd0 trigger this problem. To avoid the kernel-trace I use the sysctl-value vm.min_free_kbytes = 337920 but without luck. You could try increasing it further... ok, doubled vm.min_free_kbytes to 675840 on one node but happens again. We had also the issue (perhaps not related to this bug) that the whole host freezed and the NIC flood the 10-GB-Port so that the complete switch (and the compled network) are freezed. Please report only one issue in each bug report. Right, the information was only as backgroundinfo (if related to this bug). I believe the driver stopped making order-2 allocations in Linux 3.4, with this change: commit f800326dca7bc158f4c886aa92f222de37993c80 Author: Alexander Duyck alexander.h.du...@intel.com Date: Sat Mar 3 02:35:52 2012 + ixgbe: Replace standard receive path with a page based receive This should fix the allocation failures you're seeing. This might be backported to 3.2 if we have some other reason to update the ixgbe driver. Otherwise it will not be. Ben. On one node I installed linux-image-3.9-1-amd64 from testing and still now no traces occur. Best regards Udo Lembke -- 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/51d516d2.7020...@albertbauer.com
Bug#714571: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#714571: linux-image-3.10-rc7-686-pae: linux-kbuild-3.10 not available)
Oh, sorry, of course linux-image doesn't. Thank you for clarifying, so this is an expected situation; it still seems slightly odd for me, because drives the repository into an inconsistent state though. But OK if it's by intention.
Bug#691427: journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD
I just discovered that this bug seem to be reported to the kernel develoers as URL: https://bugzilla.kernel.org/show_bug.cgi?id=51861 . According to that report, the problem went away on its own. While according to URL: http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-520-180GB-issue/td-p/888083/page/2 , replacing the motherboard can help. Not quite sure what to believe. -- Happy hacking Petter Reinholdtsen -- 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/20130704081949.ge26...@diskless.uio.no
Bug#713929: linux-image-3.9-1-686-pae: Fan don't working on HP 550.
Package: src:linux Version: 3.9.6-1 Followup-For: Bug #713929 Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Upgrading kernel 3.2 of testing. * What exactly did you do (or not do) that was effective (or ineffective)? apt-get update apt-get dist-upgrade. Turn on the laptop. * What was the outcome of this action? Fan don't work. Overheating * What outcome did you expect instead? Fan must work. I also provides you the acpi -V. On Kernel 3.2, on an, It's write 1/1... but on 3.9, 0/1... Adapter 0: on-line Thermal 0: ok, 76.0 degrees C Thermal 0: trip point 0 switches to mode critical at temperature 108.0 degrees C Thermal 0: trip point 1 switches to mode passive at temperature 105.0 degrees C Thermal 1: active, 80.0 degrees C Thermal 1: trip point 0 switches to mode critical at temperature 256.0 degrees C Thermal 1: trip point 1 switches to mode active at temperature 80.0 degrees C Thermal 1: trip point 2 switches to mode active at temperature 72.0 degrees C Thermal 1: trip point 3 switches to mode active at temperature 60.0 degrees C Thermal 1: trip point 4 switches to mode active at temperature 45.0 degrees C Thermal 2: ok, 20.0 degrees C Thermal 2: trip point 0 switches to mode critical at temperature 110.0 degrees C Thermal 3: ok, 20.0 degrees C Thermal 3: trip point 0 switches to mode critical at temperature 108.0 degrees C Thermal 3: trip point 1 switches to mode passive at temperature 60.0 degrees C Thermal 4: ok, 64.0 degrees C Thermal 4: trip point 0 switches to mode critical at temperature 105.0 degrees C Thermal 4: trip point 1 switches to mode passive at temperature 95.0 degrees C Cooling 0: LCD 0 of 10 Cooling 1: Processor 0 of 7 Cooling 2: Fan 0 of 1 Cooling 3: Fan 0 of 1 Cooling 4: Fan 0 of 1 Cooling 5: Fan 0 of 1 Cooling 6: Fan 0 of 1 -- Package-specific info: ** Version: Linux version 3.9-1-686-pae (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-4) ) #1 SMP Debian 3.9.6-1 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.9-1-686-pae root=UUID=9905cccd-dd88-4114-8775-edb6a7cfcfa5 ro quiet ** Not tainted ** Kernel log: [6.021337] platform microcode: firmware: agent aborted loading intel-ucode/06-16-01 (not found?) [6.021828] microcode: Microcode Update Driver: v2.00 tig...@aivazian.fsnet.co.uk, Peter Oruba [6.242773] wmi: Mapper loaded [6.254760] ACPI Warning: 0x1028-0x102f SystemIO conflicts with Region \_SB_.C003.C004.C0D3 1 (20130117/utaddress-251) [6.254769] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [6.254774] ACPI Warning: 0x1130-0x113f SystemIO conflicts with Region \_SB_.C003.C004.C0E5 1 (20130117/utaddress-251) [6.254779] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [6.254781] ACPI Warning: 0x1100-0x112f SystemIO conflicts with Region \_SB_.C003.C004.C0E5 1 (20130117/utaddress-251) [6.254786] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [6.254788] lpc_ich: Resource conflict(s) found affecting gpio_ich [6.278900] ACPI: AC Adapter [C23A] (on-line) [6.279507] ACPI: Battery Slot [C23B] (battery absent) [6.297016] iTCO_vendor_support: vendor-support=0 [6.333290] input: PC Speaker as /devices/platform/pcspkr/input/input5 [6.363323] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10 [6.363362] iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x1060) [6.364651] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [6.419916] Monitor-Mwait will be used to enter C-1 state [6.420234] Monitor-Mwait will be used to enter C-2 state [6.420240] tsc: Marking TSC unstable due to TSC halts in idle [6.420248] ACPI: acpi_idle registered with cpuidle [6.426119] Switching to clocksource hpet [6.499626] input: HP WMI hotkeys as /devices/virtual/input/input6 [6.706447] cfg80211: Calling CRDA to update world regulatory domain [6.721622] snd_hda_intel :00:1b.0: irq 44 for MSI/MSI-X [6.784748] [drm] Initialized drm 1.1.0 20060810 [6.995737] b43-phy0: Broadcom 4312 WLAN found (core revision 15) [7.036066] b43-phy0: Found PHY: Analog 6, Type 5 (LP), Revision 1 [7.060237] Broadcom 43xx driver loaded [ Features: PMNLS ] [7.140516] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input7 [7.145648] [drm] Memory usable by graphics device = 512M [7.145659] i915 :00:02.0: setting latency timer to 64 [7.145897] i915 :00:02.0: irq 45 for MSI/MSI-X [7.145910] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [7.145912] [drm] Driver supports precise vblank timestamp query. [7.145971] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [7.212442] b43 ssb0:0: firmware: agent loaded
Bug#714959: linux-image-3.2.0-4-kirkwood mdraid array fails to assemble b/c drives are not yet ready (sata_mv)
Package: src:linux Version: 3.2.46-1 Severity: normal Tags: upstream patch Dear Maintainer, On my QNAP TS-412, after a clean install of Wheezy, the kernel fails to bring up all sata ports (using Marvell 88SX7042 via sata_mv driver) before md/raid tries to assemble the array. The same disks/array work in a different model (TS-410) and the drives/array from said TS-410 also fail in my TS-412. At the same time, using the original QNAP firmware, everything works as expected. The only discernable differences between the devices that I could find (they share the exact same SoC and SATA Model ID and revision), apart from the core clock speed, is that the TS-412 shows some sort of spin-up delay / staggering behaviour while the TS-410 does not. Now, having had a look at the most recent GPL code package from QNAP that I could find here: http://sourceforge.net/projects/qosgpl/ I found that they have a version 3.4.6 kernel tree. The file drivers/ata/sata_mv.c contains some changes regarding the delay while initializing the hardware. Using this as a blueprint, I patched the linux-image-3.2.0-4 source file accordingly. The resulting kernel works for me: The delay ensures that all drives are up and the raid array comes up. I discussed this with others on debian-...@lists.debian.org and while we agree that this kind of patch is a mere band-aid, we wanted to point out that there may be some issue concerning timing/delays with this kernel module. Maybe there is a more elegant / targeted approach to solving this? -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information Processor : Feroceon 88FR131 rev 1 (v5l) Hardware: QNAP TS-41x Revision: ** PCI devices: 00:00.0 Host bridge [0600]: Marvell Technology Group Ltd. 88F6281 [Kirkwood] ARM SoC [11ab:6281] (rev 03) Subsystem: Marvell Technology Group Ltd. Device [11ab:11ab] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 9 Region 0: Memory at ignored (64-bit, prefetchable) Capabilities: access denied 00:01.0 SCSI storage controller [0100]: Marvell Technology Group Ltd. 88SX7042 PCI-e 4-port SATA-II [11ab:7042] (rev 02) Subsystem: Marvell Technology Group Ltd. Device [11ab:11ab] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 9 Region 0: Memory at e000 (64-bit, non-prefetchable) [size=1M] Region 2: I/O ports at 1000 [size=256] Capabilities: access denied Kernel driver in use: sata_mv ** USB devices: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 3.2.46 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 linux-image-3.2.0-4-kirkwood depends on: ii debconf [debconf-2.0] 1.5.49 ii initramfs-tools [linux-initramfs-tool] 0.109.1 ii kmod9-3 ii linux-base 3.5 Versions of packages linux-image-3.2.0-4-kirkwood recommends: pn firmware-linux-free none pn uboot-mkimagenone Versions of packages linux-image-3.2.0-4-kirkwood suggests: pn debian-kernel-handbook none pn fdutils none pn linux-doc-3.2 none Versions of packages linux-image-3.2.0-4-kirkwood is related to: pn firmware-atherosnone pn firmware-bnx2 none pn firmware-bnx2x none pn firmware-brcm80211 none pn firmware-intelwimax none pn firmware-ipw2x00none pn firmware-ivtv none pn firmware-iwlwifinone pn firmware-libertas none pn firmware-linux none pn firmware-linux-nonfree none pn firmware-myricomnone pn firmware-netxen none pn firmware-qlogic none pn firmware-ralink none pn firmware-realteknone pn xen-hypervisor none -- debconf information: linux-image-3.2.0-4-kirkwood/postinst/missing-firmware-3.2.0-4-kirkwood: linux-image-3.2.0-4-kirkwood/prerm/removing-running-kernel-3.2.0-4-kirkwood: true linux-image-3.2.0-4-kirkwood/postinst/ignoring-ramdisk: linux-image-3.2.0-4-kirkwood/postinst/depmod-error-initrd-3.2.0-4-kirkwood: false [0.00] Initializing cgroup subsys cpuset [
Processed: Re: [Pkg-xfce-devel] Bug#714736: Bug#714736: thunar: GUI freeze while moving to trash a file from a NFS4+Kerberos mount
Processing control commands: reassign -1 nfs-common Bug #714736 [thunar] thunar: GUI freeze while moving to trash a file from a NFS4+Kerberos mount Bug reassigned from package 'thunar' to 'nfs-common'. No longer marked as found in versions thunar/1.2.3-4. Ignoring request to alter fixed versions of bug #714736 to the same values previously set -- 714736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714736 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.b714736.137297113728357.transcr...@bugs.debian.org
Processed: found 705635 in 3.2.46-1~bpo60+1
Processing commands for cont...@bugs.debian.org: found 705635 3.2.46-1~bpo60+1 Bug #705635 [linux-image-3.2.0-4-amd64] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung There is no source info for the package 'linux-image-3.2.0-4-amd64' at version '3.2.46-1~bpo60+1' with architecture '' Unable to make a source version for version '3.2.46-1~bpo60+1' Marked as found in versions 3.2.46-1~bpo60+1. thanks Stopping processing here. Please contact me if you need assistance. -- 705635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705635 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.137297464318248.transcr...@bugs.debian.org
Bug#705635: Found in 3.2.46-1~bpo60+1
I can confirm this problem on my Thinkpad E130 (Core i3, Sandybridge) with 3.2.46-1~bpo60+1 from squeeze-backports. For me the easiest way to trigger a complete freeze of the graphics is moving my mouse courser fast over the animated icons of avant-window-navigator a few times. signature.asc Description: This is a digitally signed message part
Bug#714974: nfs-kernel-server: Duplicate cookies reported - jfs partition, with samba
Package: nfs-kernel-server Version: 1:1.2.6-4 Severity: serious Justification: Effects usability of package This error is from the client machne - but I believe the error is caused by the server issuing duplicate cookies. Repeated multiple times - From syslog: Jul 4 18:45:17 singapore kernel: [280774.570555] NFS: directory //accounting contains a readdir loop.Please contact your server vendor. The file: .~lock.credit.rtf1.rtf# has duplicate cookie 199 The directory list shows files multiple times Closing the file makes things look normal. This machine is set up to share the directory in question via both nfs and samba. Samba settings for this directory: [accounting] comment = /home/accounting path = /home/accounting valid users = norma, karl, malaysia force group = accounting read only = No create mask = 0765 directory mask = 0775 inherit permissions = Yes oplocks = No level2 oplocks = No strict locking = Yes -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 56064 status 1000241 tcp 56734 status 132 tcp 2049 nfs 133 tcp 2049 nfs 134 tcp 2049 nfs 1002272 tcp 2049 1002273 tcp 2049 132 udp 2049 nfs 133 udp 2049 nfs 134 udp 2049 nfs 1002272 udp 2049 1002273 udp 2049 1000211 udp 38150 nlockmgr 1000213 udp 38150 nlockmgr 1000214 udp 38150 nlockmgr 1000211 tcp 49791 nlockmgr 1000213 tcp 49791 nlockmgr 1000214 tcp 49791 nlockmgr 151 udp 8 mountd 151 tcp 54775 mountd 152 udp 47557 mountd 152 tcp 58153 mountd 153 udp 36789 mountd 153 tcp 35984 mountd -- /etc/default/nfs-kernel-server -- RPCNFSDCOUNT=8 RPCNFSDPRIORITY=0 RPCMOUNTDOPTS=--manage-gids NEED_SVCGSSD= RPCSVCGSSDOPTS= -- /etc/exports -- /home/karl 192.168.1.0/24(rw,sync,no_all_squash,no_root_squash,no_subtree_check) /home/john 192.168.1.0/24(rw,sync,no_subtree_check) /home/norma 192.168.1.0/24(rw,sync,no_subtree_check) /home/installs 192.168.1.0/24(rw,sync,no_all_squash,no_root_squash,no_subtree_check) /home/content 192.168.1.0/22(rw,sync,no_all_squash,no_root_squash,no_subtree_check) /home/html 192.168.1.0/24(rw,sync,no_all_squash,no_root_squash,no_subtree_check) /home/accounting 192.168.1.0/24(rw,sync,no_all_squash,no_root_squash,no_subtree_check) /usr/src192.168.1.0/24(rw,sync,all_squash,no_subtree_check) /home/tftp 192.168.1.0/24(sync,rw,no_all_squash,no_root_squash,no_subtree_check) -- /proc/fs/nfs/exports -- # Version 1.1 # Path Client(Flags) # IPs /home/karl 192.168.1.0/22,192.168.1.0/24(rw,no_root_squash,sync,wdelay,no_subtree_check,uuid=511a1d4a:400e4bbb:bcba6a9a:5e00235f) /home 192.168.1.0/22,192.168.1.0/24(ro,root_squash,sync,no_wdelay,no_subtree_check,v4root,uuid=511a1d4a:400e4bbb:bcba6a9a:5e00235f) /home/html 192.168.1.0/22,192.168.1.0/24(rw,no_root_squash,sync,wdelay,no_subtree_check,uuid=511a1d4a:400e4bbb:bcba6a9a:5e00235f) /home/accounting 192.168.1.0/22,192.168.1.0/24(rw,no_root_squash,sync,wdelay,no_subtree_check,uuid=511a1d4a:400e4bbb:bcba6a9a:5e00235f) /home/content 192.168.1.0/22,192.168.1.0/24(rw,no_root_squash,sync,wdelay,no_subtree_check,uuid=511a1d4a:400e4bbb:bcba6a9a:5e00235f) /home/installs 192.168.1.0/22,192.168.1.0/24(rw,no_root_squash,sync,wdelay,no_subtree_check,uuid=511a1d4a:400e4bbb:bcba6a9a:5e00235f) -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 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-kernel-server depends on: ii libblkid1 2.20.1-5.3 ii libc6 2.13-38 ii libtirpc1 0.2.2-5 ii libwrap07.6.q-24 ii lsb-base4.1+Debian8+deb7u1 ii nfs-common 1:1.2.6-4 ii ucf 3.0025+nmu3 nfs-kernel-server recommends no packages. nfs-kernel-server suggests no packages. -- no debconf information -- 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/20130705002322.18476.83493.reportbug@malaysia.xtronics.network
Bug#714974: nfs-kernel-server: Duplicate cookies reported - jfs partition, with samba
Control: reassign -1 src:linux 3.2.46-1 Control: severity -1 important Control: tag -1 moreinfo On Thu, 2013-07-04 at 19:23 -0500, Karl Schmidt wrote: Package: nfs-kernel-server Version: 1:1.2.6-4 Severity: serious Justification: Effects usability of package nfs-kernel-server contains the scripts to set up the NFS kernel server; the server itself is part of the 'linux' package. This error is from the client machne - but I believe the error is caused by the server issuing duplicate cookies. Repeated multiple times - From syslog: Jul 4 18:45:17 singapore kernel: [280774.570555] NFS: directory //accounting contains a readdir loop.Please contact your server vendor. The file: .~lock.credit.rtf1.rtf# has duplicate cookie 199 The directory list shows files multiple times [...] You said here that this bug was fixed: http://bugs.debian.org/685407#152. Though I was sceptical, as we didn't change anything in jfs. So what has changed between then and now? Ben. -- Ben Hutchings Tomorrow will be cancelled due to lack of interest. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#714974: nfs-kernel-server: Duplicate cookies reported - jfs partition, with samba
Processing control commands: reassign -1 src:linux 3.2.46-1 Bug #714974 [nfs-kernel-server] nfs-kernel-server: Duplicate cookies reported - jfs partition, with samba Bug reassigned from package 'nfs-kernel-server' to 'src:linux'. No longer marked as found in versions nfs-utils/1:1.2.6-4. Ignoring request to alter fixed versions of bug #714974 to the same values previously set Bug #714974 [src:linux] nfs-kernel-server: Duplicate cookies reported - jfs partition, with samba Marked as found in versions linux/3.2.46-1. severity -1 important Bug #714974 [src:linux] nfs-kernel-server: Duplicate cookies reported - jfs partition, with samba Severity set to 'important' from 'serious' tag -1 moreinfo Bug #714974 [src:linux] nfs-kernel-server: Duplicate cookies reported - jfs partition, with samba Added tag(s) moreinfo. -- 714974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714974 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.b714974.13729970098825.transcr...@bugs.debian.org
