Bug#886387: closed by Mehdi Dogguy <me...@debian.org> (Bug#886387: fixed in mstflint 4.8.0-2)
reopen 886387 found 886387 linux/4.14.7-1~bpo9+1 kthxbye On Fri, Jan 05, 2018 at 11:51:07AM +, Debian Bug Tracking System <ow...@bugs.debian.org> wrote: > mstflint (4.8.0-2) unstable; urgency=medium > . >* Make the build reproducible (Closes: #886387). Thanks to Chris Lamb > for the patch. > - add 0012-Reproducible-build.patch I made a typo in the changelog and closed the wrong bug. Sorry for that. I am opening it again. Regards, -- Mehdi Dogguy
Re: Kernel version for stretch
Hi, On 2016-02-02 08:34, Niels Thykier wrote: Based on the current 9 week upstream release cycle, the longterm branch for 2017 will presumably be based on Linux 4.10, released at the end of week 3 (22nd January 2017). That's well after the planned stretch freeze date so I don't see how it can be included. Indeed that is a bit unfortunate. With the freeze date already announced, I am very hesitant to move it. I wouldn't consider it a fail if we decided to shift the freeze date by two months [1], especially if this move helps project members to integrate better supported versions for their packages. Eventually, it would help us to have a better quality release and enhance its supportability over the years. Having that said, it would be nice to hear from Ben if it would be doable to go with 4.9 or with a 4.10rc for some time. [1] only a few persons seem to have noted those dates anyway (imho). -- Mehdi
Bug#774702: linux-image-3.16.0-4-amd64: Regression in topology for multi-NUMA-node Haswell Xeon CPUs
Just for the sake of completeness, this regression happens only when Cluster On Die is enabled. Sorry for not saying that in my initial report. Regards, -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150108145631.ga14...@dogguy.org
Bug#774702: linux-image-3.16.0-4-amd64: Regression in topology for multi-NUMA-node Haswell Xeon CPUs
Package: src:linux Version: 3.16.7-ckt2-1 Severity: normal Dear Maintainer, On a machine with 2 Intel Haswell Xeon E5-2697 v3 CPUs, we are observing a regression in how topology is detected. Using Wheezy, Linux detects 2 sockets and output the following text: === Jan 6 15:15:11 pocn001 kernel: [0.450629] Booting Node 0, Processors #1 Jan 6 15:15:11 pocn001 kernel: [0.455199] smpboot cpu 1: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [0.567069] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [0.573406] #2 Jan 6 15:15:11 pocn001 kernel: [0.575160] smpboot cpu 2: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [0.686818] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [0.693158] #3 Jan 6 15:15:11 pocn001 kernel: [0.694911] smpboot cpu 3: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [0.806473] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [0.812809] #4 Jan 6 15:15:11 pocn001 kernel: [0.814562] smpboot cpu 4: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [0.926220] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [0.932548] #5 Jan 6 15:15:11 pocn001 kernel: [0.934302] smpboot cpu 5: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [1.045959] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [1.052293] #6 Jan 6 15:15:11 pocn001 kernel: [1.054047] smpboot cpu 6: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [1.165709] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [1.172099] Ok. Jan 6 15:15:11 pocn001 kernel: [1.174143] Booting Node 1, Processors #7 Jan 6 15:15:11 pocn001 kernel: [1.178712] smpboot cpu 7: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [1.289472] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [1.295830] #8 Jan 6 15:15:11 pocn001 kernel: [1.297584] smpboot cpu 8: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [1.409242] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [1.415599] #9 Jan 6 15:15:11 pocn001 kernel: [1.417354] smpboot cpu 9: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [1.529010] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [1.535350] #10 Jan 6 15:15:11 pocn001 kernel: [1.537201] smpboot cpu 10: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [1.648655] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [1.654984] #11 Jan 6 15:15:11 pocn001 kernel: [1.656835] smpboot cpu 11: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [1.768484] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [1.774815] #12 Jan 6 15:15:11 pocn001 kernel: [1.776667] smpboot cpu 12: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [1.888219] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [1.894552] #13 Jan 6 15:15:11 pocn001 kernel: [1.896403] smpboot cpu 13: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [2.008055] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [2.014445] Ok. Jan 6 15:15:11 pocn001 kernel: [2.016491] Booting Node 2, Processors #14 Jan 6 15:15:11 pocn001 kernel: [2.021156] smpboot cpu 14: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [2.131722] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [2.138096] #15 Jan 6 15:15:11 pocn001 kernel: [2.139948] smpboot cpu 15: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [2.251343] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [2.257713] #16 Jan 6 15:15:11 pocn001 kernel: [2.259564] smpboot cpu 16: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [2.371119] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [2.377469] #17 Jan 6 15:15:11 pocn001 kernel: [2.379320] smpboot cpu 17: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [2.490874] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [2.497218] #18 Jan 6 15:15:11 pocn001 kernel: [2.499070] smpboot cpu 18: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [2.610525] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [2.616866] #19 Jan 6 15:15:11 pocn001 kernel: [2.618717] smpboot cpu 19: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel: [2.730272] NMI watchdog enabled, takes one hw-pmu counter. Jan 6 15:15:11 pocn001 kernel: [2.736616] #20 Jan 6 15:15:11 pocn001 kernel: [2.738468] smpboot cpu 20: start_ip = 89000 Jan 6 15:15:11 pocn001 kernel:
Bug#689336: initramfs-tools 0.108 cannot decrypt dm_crypt filesystems
On 05/10/2012 13:52, Raphael Hertzog wrote: Dropping the severity since most people will have console-setup installed. On Fri, 05 Oct 2012, Samuel Hym wrote: I was indeed missing the console-setup package, and with it works as expected. I believe that the update-initramfs keymap hook should display a warning about missing packages when KEYMAP=y and when some of the required executables are missing. But that's all that is needed to fix this bug. And as long as this not fixed, I'm not sure we should allow this package to migrate to testing. Even if most people might have console-setup installed, this new revision may break their setup without any notification. Thus, I don't think downgrading severity to normal is the right action. Regards. -- Mehdi -- 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/506ed475.3090...@debian.org
Bug#648207: Please add support for newest Dell touchpad
found 648207 3.1.6-1 found 648207 3.2~rc7-1~experimental.1 thanks On 0, Laurent Bigonville bi...@debian.org wrote: I own a Dell Latitude E6510 and unfortunately, the touchpad is not recognized properly, causing the vertical scrolling to not work. Same on Dell Latitude E6320 (and E6220). A series of patches that fix this issue has hit the linux-next branch, could you please apply them to the debian kernel. d4b347b29b4d14647c7394f7167bf6785dc98e50 fa629ef5222193214da9a2b3c94369f79353bec9 b46615fe9215214ac00e26d35fc54dbe1c510803 25bded7cd60fa460e520e9f819bd06f4c5cb53f0 01ce661fc83005947dc958a5739c153843af8a73 7cf801cfc0774b777aa6861cf4a43a90b112b1ed LKML discussion: https://lkml.org/lkml/2011/11/7/433 any news here? Regards, -- Mehdi Dogguy -- 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/20120106183355.ga2...@dogguy.org
Bug#648207: Please add support for newest Dell touchpad
On 06/01/12 23:14, Jonathan Nieder wrote: Results from testing[1] against a sid kernel would be welcome, though I'm not too worried (I suspect the patches just work). They work for me, fwiw. Regards, -- Mehdi -- 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/4f0772b8.3020...@dogguy.org
