Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

On Tuesday, 27 June 2017 4:19:56 AM AEST Michael Biebl wrote: > > Now what can we do about /dev and /sys/fs/cgroup neither of which needs to > > be 24G in size on a system with 48G of RAM? Should I open a new bug > > report about this? > > What exactly would that solve? > Neither of those are

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

Am 27.06.2017 um 04:03 schrieb Russell Coker: > Now what can we do about /dev and /sys/fs/cgroup neither of which needs to be > 24G in size on a system with 48G of RAM? Should I open a new bug report > about > this? What exactly would that solve? Neither of those are writable by the user.

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

For /run specifying the number of inodes is also a good idea. For a system with 160M of RAM it will default to 20480 inodes which may be more than you want on a system with less than the recommended amount of RAM. tmpfs /run tmpfs nosuid,noexec,size=20M,nr_inodes=4096 0 0 The above might be

Processed: severity of 866055 is important

Processing commands for cont...@bugs.debian.org: > severity 866055 important Bug #866055 [src:linux] linux-image-4.9.0-3-amd64: Broadwell laptop hangs during light usage since upgrading to stretch Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

Am 27.06.2017 um 02:08 schrieb Michael Biebl: > You can add a entry to /etc/fstab which specifies the desired amount of > RAM for /run. > systemd will remount /run with the size you set very early during boot. > I don't think a separate config option is necessary. Something like this in

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

On Sun, 07 May 2017 13:38:11 +0100 J M Cerqueira Esteves wrote: > Package: initramfs-tools-core > Version: 0.130 > Severity: important > > In a virtual machine with 160 MiB RAM, running a freshly installed Debian > stretch system (i686), Since wheezy, the minimum

Bug#866055: linux-image-4.9.0-3-amd64: Broadwell laptop hangs during light usage since upgrading to stretch

Package: src:linux Version: 4.9.30-2+deb9u1 Severity: critical Justification: breaks the whole system Dear Maintainer, Since upgrading to Debian stretch (from jessie), my Broadwell based Lenovo X1 Carbon has been locking up regularly, seemingly around 24 hours of uptime. My system is not under

Bug#865984: linux-image-4.9.0-3-amd64: hairpin NAT doesn't work across bridges

On Tue, 2017-06-27 at 07:54 +1000, Russell Stuart wrote: > On Mon, 2017-06-26 at 16:57 +0100, Ben Hutchings wrote: > > Control: tag -1 upstream wontfix > > I'll file it upstream.  I'm never quite sure whether the maintainer is > supposed to do that or the bug submitter - it seems to vary by

Bug#865984: linux-image-4.9.0-3-amd64: hairpin NAT doesn't work across bridges

On Mon, 2017-06-26 at 16:57 +0100, Ben Hutchings wrote: > Control: tag -1 upstream wontfix I'll file it upstream. I'm never quite sure whether the maintainer is supposed to do that or the bug submitter - it seems to vary by package. Should I link the bug report here? > You should put the WAN

Bug#859639:

Update: I can confirm that the solution (or workaround) provided by Uwe is working also on my ProBook 6450b. First some hardware info: 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])     Subsystem:

Processed: Re: Bug#865984: linux-image-4.9.0-3-amd64: hairpin NAT doesn't work across bridges

Processing control commands: > tag -1 upstream wontfix Bug #865984 [src:linux] linux-image-4.9.0-3-amd64: hairpin NAT doesn't work across bridges Added tag(s) upstream and wontfix. -- 865984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865984 Debian Bug Tracking System Contact

Bug#865984: linux-image-4.9.0-3-amd64: hairpin NAT doesn't work across bridges

Control: tag -1 upstream wontfix This doesn't look like a sane network configuration to me. You should put the WAN and LAN traffic on separate VLANs and set the router's switch port to trunked mode. Ben. -- Ben Hutchings Never put off till tomorrow what you can avoid all together.

Processed: severity of 865303 is serious

Processing commands for cont...@bugs.debian.org: > severity 865303 serious Bug #865303 [src:linux] libreoffice: Libreoffice Java features crash with Linux 3.16.43-2+deb8u1 Bug #865311 [src:linux] security update for CVE-2017-1000364 breaks UniFi Controller Bug #865343 [src:linux]

Processed: tagging 865416, forcibly merging 865303 865416, tagging 865303

Processing commands for cont...@bugs.debian.org: > tags 865416 - moreinfo Bug #865416 [src:linux] cargo: segfaults some of the time on ppc64el, can't reproduce in gdb Bug #865549 [src:linux] linux: stack-guard fix for CVE-2017-1000364 incorrect Removed tag(s) moreinfo. Removed tag(s) moreinfo. >

Bug#865311:

C programs which start a jvm using jni also segfault. This smells like fundamentally the same issue. I added a "me too" to debian bug 865746 (collectd), with links to info about the issue at Ubuntu - including a test program to reproduce. See

Bug#865984: linux-image-4.9.0-3-amd64: hairpin NAT doesn't work across bridges

Package: src:linux Version: 4.9.30-2+deb9u1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Configuration: A box running 4.9.0-3-amd64 is acting as a NAT'ing router. It has a single Ethernet NIC and a wireless NIC servicing the local LAN. These devices are bridged. Since

Bug#865303: Bug#865343: SIGSEGV in jsvc / LibreOffice after kernel update

I have tested both 3.16.43-2+deb8u2 and 4.9.30-2+deb9u2 and everything works. Thanks! Sasa On Thu, Jun 22, 2017 at 2:03 PM Ben Hutchings wrote: > I have candidate fixes for this regression which are available at: >

Bug#865928: linux-image-4.9.0-3-m68k: fails to boot on ARAnyM due to NMI watchdog / soft stuck

Control: reassign -1 src:aranym Control: retitle -1 'aranym: Older versions of Aranym crash in atari_scsi with newer kernels' On Mon, Jun 26, 2017 at 03:03:04PM +1000, Finn Thain wrote: > > Hm, true. Unfortunately, I cannot upgrade ARAnyM until I get a newer > > kernel provided to Zigo’s domU

Processed: Re: Bug#865928: linux-image-4.9.0-3-m68k: fails to boot on ARAnyM due to NMI watchdog / soft stuck

Processing control commands: > reassign -1 src:aranym Bug #865928 [src:linux] linux-image-4.9.0-3-m68k: fails to boot on ARAnyM due to NMI watchdog / soft stuck Bug reassigned from package 'src:linux' to 'src:aranym'. No longer marked as found in versions linux/4.9.30-2. Ignoring request to