Bug#741406: (linux-image-3.13-1-amd64: tcp traffic fails after approx 1/2hour boot time 'TCP: out of memory -- consider tuning tcp_mem')
On Sun, Apr 20, 2014 at 02:33:00PM +1200, Jason Alavaliant wrote: > I believe that linux-image-3.13-1-amd64 3.13.10-1 fixes this problem. I've > been testing all package updates since > 3.13.5-1 and this is the first version of 3.13 where I've been able to run > it for 12 hours+ without tcp dropping out.I only have the computer > effected by this bug on during the day so can't test longer than 12hours, > but given in the past the longest it stayed up was sub 2hours I'm fairly > confident the problem is gone. Easily reproduced on 3.14.5-1. -- WBR, wRAR signature.asc Description: Digital signature
Bug#741406: (linux-image-3.13-1-amd64: tcp traffic fails after approx 1/2hour boot time 'TCP: out of memory -- consider tuning tcp_mem')
On Wed, Jun 18, 2014 at 05:11:41PM +0100, Ben Hutchings wrote: > > > I believe that linux-image-3.13-1-amd64 3.13.10-1 fixes this problem. > > > I've > > > been testing all package updates since > > > 3.13.5-1 and this is the first version of 3.13 where I've been able to run > > > it for 12 hours+ without tcp dropping out.I only have the computer > > > effected by this bug on during the day so can't test longer than 12hours, > > > but given in the past the longest it stayed up was sub 2hours I'm fairly > > > confident the problem is gone. > > Easily reproduced on 3.14.5-1. > It may be easy for you, yet other users don't seem to have this problem. Sure. > Do you also see a similar WARNING message in the kernel log? (Like: > "WARNING: CPU: . PID: ... at /build/.../net/core/stream.c:201 > inet_csk_destroy_sock+...") Yes, see https://bugzilla.kernel.org/show_bug.cgi?id=78121 > Which network driver(s) are you using? r8169 > Have you applied any router/firewall/bridge/qdisc configuration? Any > protocols other than TCP/UDP/ICMP over IP? I have a bridge with one interface in it (and there are bridge.ko functions in the WARNING stack). Otherwise nothing special. Note that I couldn't reproduce this on a custom-built vanilla 3.15. -- WBR, wRAR signature.asc Description: Digital signature
Bug#699140: Linux as of 3.8-rc5 doesn't support NCT6779D hw sensor
Package: src:linux-2.6 Severity: normal Tags: upstream patch Some newer desktop motherboards, including my ASUS P8Z77-V LE and at least some other ASUS Z77-based ones, contain a NCT6779D sensor which isn't supported by the w83627ehf driver or any other kernel driver. There is a working driver at https://github.com/groeck/nct6775 (last time submitted for reviewing at http://lists.lm-sensors.org/pipermail/lm- sensors/2012-December/037817.html ). It "will replace the w83627ehf driver for NCT6775F and NCT6776F, and provides support for NCT6779D". Here is its output on my system: nct6779-isa-0290 Adapter: ISA adapter in0:+0.94 V (min = +0.00 V, max = +1.74 V) in1:+1.01 V (min = +0.00 V, max = +0.00 V) ALARM in2:+3.41 V (min = +0.00 V, max = +0.00 V) ALARM in3:+3.41 V (min = +0.00 V, max = +0.00 V) ALARM in4:+1.02 V (min = +0.00 V, max = +0.00 V) ALARM in5:+2.04 V (min = +0.00 V, max = +0.00 V) ALARM in6:+0.29 V (min = +0.00 V, max = +0.00 V) ALARM in7:+3.42 V (min = +0.00 V, max = +0.00 V) ALARM in8:+3.38 V (min = +0.00 V, max = +0.00 V) ALARM in9:+1.06 V (min = +0.00 V, max = +0.00 V) ALARM in10: +0.22 V (min = +0.00 V, max = +0.00 V) ALARM in11: +0.18 V (min = +0.00 V, max = +0.00 V) ALARM in12: +0.18 V (min = +0.00 V, max = +0.00 V) ALARM in13: +0.18 V (min = +0.00 V, max = +0.00 V) ALARM in14: +0.18 V (min = +0.00 V, max = +0.00 V) ALARM fan1: 873 RPM (min =0 RPM) fan2: 581 RPM (min =0 RPM) fan3: 0 RPM (min =0 RPM) fan4: 0 RPM (min =0 RPM) fan5: 0 RPM (min =0 RPM) SYSTIN: +32.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor CPUTIN: +36.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor AUXTIN0: +102.0°Csensor = thermistor AUXTIN1: +102.0°Csensor = thermistor AUXTIN2: +102.0°Csensor = thermistor AUXTIN3: +8.0°Csensor = thermal diode PCH_CHIP_CPU_MAX_TEMP: +0.0°C PCH_CHIP_TEMP: +0.0°C PCH_CPU_TEMP:+0.0°C PCH_MCH_TEMP:+0.0°C cpu0_vid: +0.000 V intrusion0:ALARM intrusion1:ALARM See also e.g. http://lists.lm-sensors.org/pipermail/lm- sensors/2012-May/036187.html and http://lists.lm-sensors.org/pipermail/lm- sensors/2012-June/036285.html -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.0-rc3-wrar-1+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20130128013725.8159.77153.report...@belkar.wrar.name
Re: Question regarding patching in 4.9 kernel
On Thu, Sep 27, 2018 at 02:28:35AM +, Harish Venkatraman wrote: > Hi Ben, > > I am trying to manually back port to Linux 4.9 since in the link I don’t see > a patch provided for 4.9 version. The last version that has this patch is > 4.11, wanted to know if back port of this patch is supported on Linux 4.9 or > this patch is supported only from 4.11? This is a wrong place to ask though, as this question is not related to Debian. -- WBR, wRAR signature.asc Description: PGP signature
Bug#848115: Fails to configure: "Failed to try-restart nfs-server.service: Unit proc-fs-nfsd.mount is masked."
Package: nfs-kernel-server Version: 1:1.3.4-1 Severity: serious I've upgraded nfs-kernel-server from 1:1.2.8-9.2 to 1:1.3.4-1. It failed to configure: Setting up nfs-kernel-server (1:1.3.4-1) ... Failed to try-restart nfs-server.service: Unit proc-fs-nfsd.mount is masked. insserv: warning: current start runlevel(s) (empty) of script `nfs-kernel- server' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `nfs- kernel-server' overrides LSB defaults (0 1 6). Failed to restart nfs-kernel-server.service: Unit proc-fs-nfsd.mount is masked. invoke-rc.d: initscript nfs-kernel-server, action "restart" failed. * nfs-server.service - NFS server and services Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled) Active: active (exited) since Sun 2016-12-11 01:42:06 +05; 3 days ago Main PID: 984 (code=exited, status=0/SUCCESS) CGroup: /system.slice/nfs-server.service Dec 11 01:42:05 belkar systemd[1]: Starting NFS server and services... Dec 11 01:42:06 belkar systemd[1]: Started NFS server and services. dpkg: error processing package nfs-kernel-server (--configure): subprocess installed post-installation script returned error exit status 1 -- 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 151 udp 58998 mountd 151 tcp 43577 mountd 152 udp 47808 mountd 152 tcp 37305 mountd 153 udp 59423 mountd 153 tcp 59211 mountd 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 54161 nlockmgr 1000213 udp 54161 nlockmgr 1000214 udp 54161 nlockmgr 1000211 tcp 45795 nlockmgr 1000213 tcp 45795 nlockmgr 1000214 tcp 45795 nlockmgr -- /etc/default/nfs-kernel-server -- RPCNFSDCOUNT=8 RPCNFSDPRIORITY=0 RPCMOUNTDOPTS="--manage-gids" NEED_SVCGSSD="" RPCSVCGSSDOPTS="" -- /etc/exports -- / *(ro,async,insecure,fsid=0,crossmnt,subtree_check) -- /proc/fs/nfs/exports -- # Version 1.1 # Path Client(Flags) # IPs -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages nfs-kernel-server depends on: ii init-system-helpers 1.46 ii keyutils 1.5.9-9 ii libblkid12.29-1 ii libc62.24-8 ii libcap2 1:2.25-1 ii libsqlite3-0 3.15.2-1 ii libtirpc10.2.5-1 ii libwrap0 7.6.q-25 ii lsb-base 9.20161125 ii netbase 5.3 ii nfs-common 1:1.3.4-1 ii ucf 3.0036 nfs-kernel-server recommends no packages. nfs-kernel-server suggests no packages. -- debconf-show failed
