Bug#834791: Add NEWS/README.Debian entry to recommend people not to enable KSM
Source: linux Version: 3.16.7-ckt7-1 Severity: wishlist On Wed, Aug 17, 2016 at 11:51:14PM +0200, Moritz Mühlenhoff wrote: > Aurelien Jarno schrieb: > > On 2016-08-14 16:00, Salvatore Bonaccorso wrote: > >> Package: release.debian.org > >> Severity: normal > >> Tags: jessie > >> User: release.debian@packages.debian.org > >> Usertags: pu > >> > >> Dear SRM > >> > >> I would like to propose the following hardening to src:gnupg2 which was > >> found during the analysis of a vulnerability report to the security team > >> and related to > >> https://www.usenix.org/system/files/conference/usenixsecurity16/sec16_paper_razavi.pdf > >> and developed by NIIBE Yutaka. The underlying problem in hardware cannot > >> be solved in software (and thus we don't want to issue a DSA for it, and > >> give possibly this false impression), and as pointed out by Florian > > > > I wonder if it would be a good idea to release an announcement without > > any software change recommending people to not enable KSM on their > > hosts? > > I think a NEWS file for the kernel would be best? Okay. Let's open a Bug for src:linux for this. Regards, Salvatore
Bug#834505: arm64 boot failure with large physical memory range
> > On Tue, Aug 16, 2016 at 01:13:28PM +0100, Leif Lindholm wrote:
> > >
> > > Package: linux
> > > Version: 4.6.4-1
> > > > > > > > > X-Debbugs-CC: st...@einval.com, woo...@wookware.org,
> > > > > > > > > zheng...@linaro.org
> > >
> > > Upstream commit 211102d85 ("arm64: defconfig: enable 48-bit virtual
> > > addresses") changed the default configuration for arm64 to be 48-bit
> > > VA (CONFIG_ARM64_VA_BITS_48). This is required in order to be able to
> > > access the full amount of RAM available on some current arm64 systems
> > > (currently with large memory holes, but could apply to any system with
> > > >
> > > > 512GB of RAM). Without this, on these systems, the kernel will fail
> > > to access the initrd, which will have been located near top of RAM by
> > > GRUB. Error message given is:
> > > ---
> > > initrd not fully accessible via the linear mapping -- please check
> > > your bootloader ...
> > > ---
> > >
> > > So please enable CONFIG_ARM64_VA_BITS_48 for arm64 kernels.
> > >
> > > Note: this change _will_ cause breakage in certain userland software
> > > making non-portable assumptions about available of top address bits
> > > for pointer tagging - including luajit and mozilla-js (and hence
> > > everything using mozilla-js).
[...]
Could we possibly work around that by reducing
CONFIG_ARCH_MMAP_RND_BITS_MAX? (That's not directly configurable; it
requires patching arch/arm64/Kconfig.)
Ben.
--
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.
signature.asc
Description: This is a digitally signed message part
Bug#834764: linux: Please update aufs4-patches to latest version
Source: linux Version: 4.7_rc7-1_exp1 Severity: wishlist Hey, I'm packaging aufs4 for Debian at the moment. It would be very nice if you could update the aufs4 kernel-patches applied by Debian to the latest version (seems to be "4.6-20160815" and "4.7-20160815" at the moment). Thank you, Jan
Re: machine checks on Dell R815 under jessie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, 2016-08-10 at 10:20 -0400, Jeffrey Mark Siskind wrote: > From: Ritesh Raj Sarraf > > I (still) have MCE errors on my new laptop [1]. But so far, hasn't created > any problem. > > It causes my servers to halt. > > Jeff (http://engineering.purdue.edu/~qobi) Were you able to progress on this issue? You mentioned initially that, with older kernel, this issue was not seen. Is that still the case ? The manpage says that uncorrected machine check errors will lead to a kernel panic. - -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXtfRuAAoJEKY6WKPy4XVpC84P/13lr7xhifobSxwBDLgDEbFB Z7eeQN4ibvxz1g/NddUyAhxjkK7ISlMaUJ4MwVQdcmPMRnmtCi1e+it3j0pVTAxb /NjNQNRtxaPJz5eEbCE32R0Aj076Q88VMOVcbKVb7k3KZJmIvPmL/5plErPnC/Az cOrS78B7B2l+8EfDaQUglta8dWDf8mloD4lkzcFQAsDY8bBIQ4bkL0I7vHDxR4Z4 cn/QOsOdN2KYgIFlIIJbiovgei/sOVcNcGXopVjEMu46Vw6zqLhUtz2z9xpe+35Y uDTfUHdyALymOBXDswa8OOHRn60GhdC4Ai7f3dupjJwV8UHeeH+jd3wl0ZdFhzxo NVZFiaCSzm8M6qpF46Eh9DLjbluvjBrW7OsZ3uxDyRzQ9xwWnJpSAr0DqVkilUCX fx5DUddY5WPkRfAiiZCqqIU00OJzvQtoE4NHDSiiLBs4cpvH5FYFKcwvp/QU4Ah2 oVt8na9ZIm9njEV6aLkRsRtdk5d+Wj/wnr0HhNnVX7MkzzS1aBcZWsPzxttTIfT3 Emqf2umL0kKAtxUZCDKxyqkjS3CE6GMVdKrszAFWMYn2KmjdTHfw7tFDi4hdH+PL yO00uAVVmX0M0bsj5b9P/nxCAKEcRaFzr0Pmf2ypzgb7Teg2oh/MUgPoNxzvtb7g fPqt9FP27v2Dv4eiEv9T =8zBL -END PGP SIGNATURE-
Re: machine checks on Dell R815 under jessie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, 2016-08-18 at 23:16 +0530, Ritesh Raj Sarraf wrote: > On Wed, 2016-08-10 at 10:20 -0400, Jeffrey Mark Siskind wrote: > > From: Ritesh Raj Sarraf > > > > I (still) have MCE errors on my new laptop [1]. But so far, hasn't > created > > any problem. > > > > It causes my servers to halt. > > > > Jeff (http://engineering.purdue.edu/~qobi) > > Were you able to progress on this issue? > You mentioned initially that, with older kernel, this issue was not seen. Is > that still the case ? > > The manpage says that uncorrected machine check errors will lead to a kernel > panic. I just extracted the logs for my machine. Contrary to what the manpage says, I get Uncorrected errors, but no kernel panic. Hardware event. This is not a software error. MCE 0 CPU 0 BANK 6 MISC 38a086 ADDR fef81780 TIME 1471502624 Thu Aug 18 12:13:44 2016 MCG status: MCi status: Uncorrected error MCi_MISC register valid MCi_ADDR register valid Processor context corrupt MCA: corrected filtering (some unreported errors in same region) Generic CACHE Level-2 Generic Error STATUS ae40110a MCGSTATUS 0 MCGCAP c07 APICID 0 SOCKETID 0 CPUID Vendor Intel Family 6 Model 69 Hardware event. This is not a software error. MCE 0 CPU 0 BANK 6 MISC 38a086 ADDR fef81780 TIME 1471506843 Thu Aug 18 13:24:03 2016 MCG status: MCi status: Uncorrected error MCi_MISC register valid MCi_ADDR register valid Processor context corrupt MCA: corrected filtering (some unreported errors in same region) Generic CACHE Level-2 Generic Error STATUS ae40110a MCGSTATUS 0 MCGCAP c07 APICID 0 SOCKETID 0 CPUID Vendor Intel Family 6 Model 69 Hardware event. This is not a software error. MCE 0 CPU 0 BANK 6 MISC 38a086 ADDR fef81780 TIME 1471511695 Thu Aug 18 14:44:55 2016 MCG status: MCi status: Uncorrected error MCi_MISC register valid MCi_ADDR register valid Processor context corrupt MCA: corrected filtering (some unreported errors in same region) Generic CACHE Level-2 Generic Error STATUS ae40110a MCGSTATUS 0 MCGCAP c07 APICID 0 SOCKETID 0 CPUID Vendor Intel Family 6 Model 69 Hardware event. This is not a software error. MCE 0 CPU 0 BANK 6 MISC 38a086 ADDR fef81780 TIME 1471520827 Thu Aug 18 17:17:07 2016 MCG status: MCi status: Uncorrected error MCi_MISC register valid MCi_ADDR register valid Processor context corrupt MCA: corrected filtering (some unreported errors in same region) Generic CACHE Level-2 Generic Error STATUS ae40110a MCGSTATUS 0 MCGCAP c07 APICID 0 SOCKETID 0 CPUID Vendor Intel Family 6 Model 69 Hardware event. This is not a software error. MCE 0 CPU 0 BANK 6 MISC 38a086 ADDR fef81780 TIME 1471531931 Thu Aug 18 20:22:11 2016 MCG status: MCi status: Uncorrected error MCi_MISC register valid MCi_ADDR register valid Processor context corrupt MCA: corrected filtering (some unreported errors in same region) Generic CACHE Level-2 Generic Error STATUS ae40110a MCGSTATUS 0 MCGCAP c07 APICID 0 SOCKETID 0 CPUID Vendor Intel Family 6 Model 69 Hardware event. This is not a software error. MCE 0 CPU 0 BANK 6 MISC 38a086 ADDR fef81780 TIME 1471534964 Thu Aug 18 21:12:44 2016 MCG status: MCi status: Uncorrected error MCi_MISC register valid MCi_ADDR register valid Processor context corrupt MCA: corrected filtering (some unreported errors in same region) Generic CACHE Level-2 Generic Error STATUS ae40110a MCGSTATUS 0 MCGCAP c07 APICID 0 SOCKETID 0 CPUID Vendor Intel Family 6 Model 69 Hardware event. This is not a software error. MCE 0 CPU 0 BANK 6 MISC 78a086 ADDR fef87300 TIME 1471539248 Thu Aug 18 22:24:08 2016 MCG status: MCi status: Uncorrected error MCi_MISC register valid MCi_ADDR register valid Processor context corrupt MCA: corrected filtering (some unreported errors in same region) Generic CACHE Level-2 Generic Error STATUS ae40110a MCGSTATUS 0 MCGCAP c07 APICID 0 SOCKETID 0 CPUID Vendor Intel Family 6 Model 69 - -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXtfuXAAoJEKY6WKPy4XVpeIQP/0eozS3oWSPZ0elxoAaVZtOi mgcxtpvRl1LPUqNfE+mhH8HzgqMzJjSK3pUJLJtXlHFMzXlTt4oRv5gwidOGrWp7 ZKzEs/6HK9CmhQnm9eqbj8CMJ1BuEzL0hxauHn79BumIteRVRNfgMst0U1wxXU2l v1iGGRAdyqiNbF7pl0NH3CNYm1oaTA1ZnqaSpL1EFFsgmMTaKIAWJLN1q4gIwqz4 7g4yEL4YqPkd9AcQR5jxOCbsMDXFZxXUcICMhTM1WA/XvPt6SIJaSdd3RKWZPJre nrs6v6rl8+Gsfhtq3U8iQlelzLr4Vg6uZcEm+TNg7w+twSCwwe0n0HiJHRdFaKR8 UPYaO3mzRCPLy/hK9BYC7LwiHj2DJYD0xm8JLP0WPfjEpLfzwNhvXZoKOXuFGr4X 9wHNGaaS/r08LkabQ8PmT9qWchoNI8opxuomD4Dhg1k5bE1R2yF1BNHyfsHfSE7f y39u0taQVcrYu8F6T0QHrCiLtWoFj84b/6DaVUx5pQOicH+OshaYUTc427ccKmjB 4Nnj9RcBTLmkMyPKU+EbpbQAwpVC3lZPtmFnxx6whJVstYw55DEt4T10pFbPoxOD ETKeREZFHZvJhZqEFxm4kh6gf6/HF5DVKDMeRtejufTmr+DaVO3pGZ9z/NdQr4Ls HlPODP4gmSfdXuSL08bQ =Ay8k -END PGP SIGNATURE-
Re: Bug#684265: testing report [Re: Bug#686471: cdimage.debian.org:Please made DVD-1 image small enough to fit on a 4GB USB stick]
Hello can u please email me back lost pass word and info to gain access to content Sent from my iPhone
Bug#834513: Correction to the bug description
Hello, I have to correct my description of bug #834513. I said, we had made available another lun to both linux servers. This is not correct. I should have said, that we made available another storage device to both systems (WWN zoning). But on this storage device there was no lun configured to be used by these systems. So probably the systems froze because they saw a new storage device and kept scanning for available luns on this device. When we realized, that we lost connection to our systems, we disabled the new zoning rules. So while restarting the maschines the old (working) san configuration was active again and the reboot went right. Thanks! smime.p7s Description: S/MIME Cryptographic Signature
Bug#834505: arm64 boot failure with large physical memory range
On Tue, Aug 16, 2016 at 04:39:15PM +0200, Hector Oron wrote:
> On Tue, Aug 16, 2016 at 01:13:28PM +0100, Leif Lindholm wrote:
> > Package: linux
> > Version: 4.6.4-1
> > X-Debbugs-CC: st...@einval.com, woo...@wookware.org, zheng...@linaro.org
> >
> > Upstream commit 211102d85 ("arm64: defconfig: enable 48-bit virtual
> > addresses") changed the default configuration for arm64 to be 48-bit
> > VA (CONFIG_ARM64_VA_BITS_48). This is required in order to be able to
> > access the full amount of RAM available on some current arm64 systems
> > (currently with large memory holes, but could apply to any system with
> > >512GB of RAM). Without this, on these systems, the kernel will fail
> > to access the initrd, which will have been located near top of RAM by
> > GRUB. Error message given is:
> > ---
> > initrd not fully accessible via the linear mapping -- please check
> > your bootloader ...
> > ---
> >
> > So please enable CONFIG_ARM64_VA_BITS_48 for arm64 kernels.
> >
> > Note: this change _will_ cause breakage in certain userland software
> > making non-portable assumptions about available of top address bits
> > for pointer tagging - including luajit and mozilla-js (and hence
> > everything using mozilla-js).
>
> FTR, this is an issue DSA is having booting arm64 machine donated by
> Gigabyte MR30-AR1. I am currently building a kernel, to get a d-i image
> and test this proposed fix.
>
> I'll follow up with the results.
Ok, that worked fine, in addition to:
CONFIG_ARM64_VA_BITS_48=y
we also need to set on arm64
CONFIG_ACPI=y
As we are using ACPI for booting MR30-AR1 device.
Regards,
--
Hector Oron
signature.asc
Description: PGP signature
