Bug#908161: Please enable building a riscv64 kernel image

Hi! On 06/09/2018 21:06, Karsten Merker wrote: > Unfortunately, with the patch applied the kernel itself builds > successfully, but the package build process then fails with > > -8<--8<--8<--8<--8<- > > make[3]: Leaving directory >

Bug#891520: linux-libc-dev: headers from 4.15 cause "redefinition of 'struct in6_addr'" in libreswan

Package: linux-libc-dev Version: 4.15.4-1 Severity: important Tags: fixed-upstream Control: affects -1 src:libreswan X-Debbugs-CC: libres...@packages.debian.org Hi, I noticed libreswan FTBFS in unstable with this error: > In file included from > /<>/programs/pluto/linux-copy/linux/xfrm.h:4:0, >

Bug#883735: Re: Bug#883735: initramfs-tools: automatic resume doesn't work for lvm swap partitions

Hi, On 07/12/17 01:30, Ben Hutchings wrote: > Control: reopen -1 > Control: tag -1 patch moreinfo > > On Thu, 2017-12-07 at 00:22 +, James Cowgill wrote: >> Hi, >> >> On 07/12/17 00:06, Ben Hutchings wrote: >>> On Wed, 2017-12-06 at 23:48 +, James

Bug#883735: Re: Bug#883735: initramfs-tools: automatic resume doesn't work for lvm swap partitions

Hi, On 07/12/17 00:06, Ben Hutchings wrote: > On Wed, 2017-12-06 at 23:48 +0000, James Cowgill wrote: >> Package: initramfs-tools >> Version: 0.130 >> Severity: normal >> >> Hi, >> >> I had noticed this bug for quite a while now, but since I rarely tur

Bug#883735: initramfs-tools: automatic resume doesn't work for lvm swap partitions

Package: initramfs-tools Version: 0.130 Severity: normal Hi, I had noticed this bug for quite a while now, but since I rarely turn my machine off I left investigating what the problem was until now. Every time I boot my laptop, it prints a lot of messages like this, before eventually giving up:

Bug#881830: linux: cherry-pick "security/keys: add CONFIG_KEYS_COMPAT to Kconfig" to stretch kernel

Hi, On 16/11/17 19:04, Ben Hutchings wrote: > On Wed, 2017-11-15 at 16:50 +0000, James Cowgill wrote: >> Since I was a little puzzled as to why keyutils built previously on >> mips, I found this commit to 4.8 which caused the need for KEYS_COMPA

Bug#881830: linux: cherry-pick "security/keys: add CONFIG_KEYS_COMPAT to Kconfig" to stretch kernel

Since I was a little puzzled as to why keyutils built previously on mips, I found this commit to 4.8 which caused the need for KEYS_COMPAT: commit 20f06ed9f61a185c6dabd662c310bed6189470df Author: David Howells Date: Wed Jul 27 11:43:37 2016 +0100 KEYS: 64-bit MIPS

Bug#881830: linux: cherry-pick "security/keys: add CONFIG_KEYS_COMPAT to Kconfig" to stretch kernel

Source: linux Version: 4.9.51-1 Severity: wishlist Control: fixed -1 4.12.2-1~exp1 Hi, Is it possible to cherry-pick the following upstream commit into the stable kernel so it is available on the buildds? commit 47b2c3fff4932e6fc17ce13d51a43c6969714e20 Author: Bilal Amarni

Bug#877779: linux: modpost uses wrong sizes for mips-octeon kernel

Source: linux Version: 4.12.13-1 Severity: normal Hi, I recently attempted to install an out-of-tree module (an old version of the octeon mmc driver) on an octeon machine running big endian 32-bit mips. In this configuration, the kernel is 64-bit, but userspace is 32-bit. The module build

Bug#867358: mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address

m/davecgh/go-spew/spew: /usr/bin/mips-linux-gnu-gccgo-7: >>>> waitid: bad address >>>> FAIL github.com/pelletier/go-toml [build failed] >>>> ? github.com/pelletier/go-toml/cmd[no test files] >>>> ... >>> >>> James

Lemote-3a-itx-a1101 kernel/PMON bug (Was: Bug#858405: xmlto: intermittent Segmentation fault when building manpages for libreswan on mips64el)

Hi, [drop some CCs since this is not directly related to the xmlto bug] On 24/03/17 09:36, YunQiang Su wrote: > On Fri, Mar 24, 2017 at 1:06 AM, James Cowgill <jcowg...@debian.org> wrote: >> I believe any of the following will fix this (but have not all been tested): >> - R

Re: Bug#858405: xmlto: intermittent Segmentation fault when building manpages for libreswan on mips64el

reassign 858405 xsltproc forcemerge 750593 858405 retitle 750593 xsltproc: bus error on some arches with linux < 4.1 thanks Hi, On 22/03/17 21:01, Daniel Kahn Gillmor wrote: > On Wed 2017-03-22 06:22:41 -0400, James Cowgill wrote: >> On 22/03/17 01:29, Daniel Kahn Gillmor wrote: &g

Bug#851963: linux: enable SENSORS_ADM1031

On 21/01/17 10:29, Roger Shimizu wrote: > On Sat, Jan 21, 2017 at 6:05 PM, James Cowgill <jcowg...@debian.org> wrote: >> Hi, >> >> On 21/01/17 08:05, Roger Shimizu wrote: >>> Control: tag -1 +moreinfo >>> >>> On Fri, Jan 20, 2017 at 9:17 PM,

Bug#851963: linux: enable SENSORS_ADM1031

Hi, On 21/01/17 08:05, Roger Shimizu wrote: > Control: tag -1 +moreinfo > > On Fri, Jan 20, 2017 at 9:17 PM, James Cowgill <jcowg...@debian.org> wrote: >> Source: linux >> Version: 4.9.2-2 >> Severity: wishlist >> >> Hi, >> >> Please c

Bug#851963: linux: enable SENSORS_ADM1031

Source: linux Version: 4.9.2-2 Severity: wishlist Hi, Please can you enable CONFIG_SENSORS_ADM1031 as a module. I have a Cavium Octeon board which needs this driver to be able to read the CPU temperature / fan sensors. Thanks, James signature.asc Description: OpenPGP digital signature

Bug#781892: (Hardware?) problem with denormal values on mipsel

On Wed, 2015-05-27 at 20:46 +0200, Ole Streicher wrote: Hi all, Am 27.05.2015 um 15:45 schrieb James Cowgill: There's probably still a hardware bug in here somewhere, but before 3.16 the kernel was fixing it with the math emulator. Without understanding the discussion in detail, I'd

Re: (Hardware?) problem with denormal values on mipsel

Cowgill wrote: On Sun, 2015-05-24 at 22:32 +0300, Aaro Koskinen wrote: On Fri, May 22, 2015 at 11:00:18PM +0100, James Cowgill wrote: On Sat, 2015-05-23 at 00:04 +0300, Aaro Koskinen wrote: On Fri, May 22, 2015 at 05:27:14PM +0100, James Cowgill wrote: Yep it's a hardware problem

Bug#781892: (Hardware?) problem with denormal values on mipsel

On Wed, 2015-05-27 at 18:13 +0100, Maciej W. Rozycki wrote: On Wed, 27 May 2015, James Cowgill wrote: Thanks! The kernel was the important part which was different to my setup. There's probably still a hardware bug in here somewhere, but before 3.16 the kernel was fixing