Processing commands for cont...@bugs.debian.org:
> severity 835940 serious
Bug #835940 [nvidia-cuda-toolkit] nvidia-cuda-toolkit: non-standard gcc/g++
used for build (gcc-5)
Severity set to 'serious' from 'important'
> severity 835941 serious
Bug #835941 [starpu-contrib] starpu-contrib: non-stand
On Mon, 12 Dec 2016 10:48:47 +0100
Stanislav Kozina wrote:
> A runtime check is still done, with per-module vermagic which distros
> can change when they bump the ABI version. Is it really necessary to
> have more than that (i.e., per-symbol versioning)?
> >>> From my point of
Processing commands for cont...@bugs.debian.org:
> found 847198 4.8.4-1~exp1
Bug #847198 [src:linux] src:linux: dmesg should be allowed to print the kernel
ring buffer for admins
Marked as found in versions linux/4.8.4-1~exp1.
> thanks
Stopping processing here.
Please contact me if you need assi
Package: mkvmlinuz
Version: 38
Severity: normal
Milan, the Vcs-* fields in mkvmlinuz point to the kernel team's old
Subversion repository but you never committed there. Please remove or
update these fields.
You seem to be the only maintainer for the package and are not using a
kernel team reposi
Hello,
That said, a dwarf based checker tool should be able to do as good a job
(maybe a bit better because report is very informative and it may pick up
compiler alignments or padding options).
So, Nicholas was kind enough to send me the two Linux Kernel binaries
that he built with the tiny li
Processing commands for cont...@bugs.debian.org:
> reassign 847991 udev 232-7
Bug #847991 [initramfs-tools] initramfs-tools: upgrade to stretch in kvm image
fails when trying to copy 70-persistent-net.rules
Bug reassigned from package 'initramfs-tools' to 'udev'.
No longer marked as found in vers
Package: initramfs-tools
Version: 0.120+deb8u2
Severity: important
Hi there,
I've tried upgrading a VM from jessie to stretch and I'm having an issue with
initramfs-tools.
The upgrade is from 0.120+deb8u2 to 0.125. The system is a KVM image of debian
jessie (vanilla debian install with only mysq
On Mon, Dec 12, 2016 at 08:11:12PM +, Dominic Hargreaves wrote:
> The kernel panics immediately after bootup with the following console
> output:
I forgot to mention that problem isn't seen with either 4.6.4-1
or 3.16.7-ckt25-2+deb8u3 which are also installed.
Thanks for any assistance.
Domi
Package: src:linux
Version: 4.8.11-1
Severity: important
The kernel panics immediately after bootup with the following console
output:
Loading Linux 4.8.0-2-amd64 ...
Loading initial ramdisk ...
/dev/vda1: clean, 832314/3932160 files, 10062334/15728128 blocks
[ 147.464089] general protection fau
On Mon, 2016-12-12 at 11:13 +0100, Salvatore Bonaccorso wrote:
> Hi,
>
> On Mon, Dec 12, 2016 at 10:23:49AM +0100, Ferenc Wágner wrote:
> > > > Daniel Pocock writes:
> >
> > > Could either of you comment on this bug? I saw your names in the
> > > nfs-utils changelog. I've seen various problems
Package: firmware-libertas
Version: 20161130-1
Severity: important
Hello,
I am new to the bug reporting on Debian and thus I apologize in advance for the
likely poor quality of this bug report. I will try to explain throughly the
issue although it is a little bit difficult to reproduce.
- Case
Ok, thanks, I will wait, it's not a big problem.
Regards
Marc
linux-headers-4.8.0-0.bpo.1-all_4.8.7-1~bpo8+1_amd64.deb: trying to install to
backports-new, but could not find source
binary:linux-headers-4.8.0-0.bpo.1-all is NEW.
binary:linux-perf-4.8 is NEW.
binary:linux-kbuild-4.8 is NEW.
binary:linux-headers-4.8.0-0.bpo.1-all-amd64 is NEW.
binary:linux-
linux_4.8.7-1~bpo8+1_amd64.changes uploaded successfully to localhost
along with the files:
linux-compiler-gcc-4.9-x86_4.8.7-1~bpo8+1_amd64.deb
linux-headers-4.8.0-0.bpo.1-amd64_4.8.7-1~bpo8+1_amd64.deb
linux-image-4.8.0-0.bpo.1-amd64-dbg_4.8.7-1~bpo8+1_amd64.deb
linux-image-4.8.0-0.bpo.1-a
Daniel Pocock writes:
> On 12/12/16 10:23, Ferenc Wágner wrote:
>
>> However, I also encountered serious problems deploying NFS (both client
>> and server side) under jessie, and I would agree to team up and help do
>> better for stretch.
>
> Can you tell us if all the problems you saw are alread
Hi,
On Mon, Dec 12, 2016 at 10:23:49AM +0100, Ferenc Wágner wrote:
> Daniel Pocock writes:
>
> > Could either of you comment on this bug? I saw your names in the
> > nfs-utils changelog. I've seen various problems with NFS under jessie
> > and I was hoping to help test if for stretch.
>
> Hi
A runtime check is still done, with per-module vermagic which distros
can change when they bump the ABI version. Is it really necessary to
have more than that (i.e., per-symbol versioning)?
From my point of view, it is. We need to allow changing ABI for some
modules while maintaining it for oth
On 12/12/16 10:23, Ferenc Wágner wrote:
> Daniel Pocock writes:
>
>> Could either of you comment on this bug? I saw your names in the
>> nfs-utils changelog. I've seen various problems with NFS under jessie
>> and I was hoping to help test if for stretch.
>
> Hi Daniel,
>
> I'm not involved
Daniel Pocock writes:
> Could either of you comment on this bug? I saw your names in the
> nfs-utils changelog. I've seen various problems with NFS under jessie
> and I was hoping to help test if for stretch.
Hi Daniel,
I'm not involved in the maintenance of nfs-utils, just reported a
trivial
On Sat, 2016-12-10 at 13:41 +0100, Greg Kroah-Hartman wrote:
> Now I don't work on a distro anymore, but I would think that something
> like this would be really useful, pointing out exactly what changed is
> very important for distro maintainers to determine what they want to do
The .symvers prod
Package:linux-image-3.16.0-4-amd64
Version:3.16.36-1+deb8u1
3.16.36-1+deb8u1 (debian stable package) kernel panic. see the page count:-1:
The information:
[4980739.576734] BUG: Bad page state in process parameter_serve pfn:1d485a4
[4980739.576772] page:ea00667d3be0 count:-1 mapcount:0 mappi
21 matches
Mail list logo
