Processed: Re: linux-image-3.10-3-amd64: Network adapter (Intel 82579V) hangs during TX, causing reset and undetected data corruption at the other side

Processing control commands: > severity -1 important Bug #727149 [src:linux] linux-image-3.10-3-amd64: Network adapter (Intel 82579V) hangs during TX, causing reset and undetected data corruption at the other side Ignoring request to change severity of Bug 727149 to the same value. -- 727149:

Bug#727149: linux-image-3.10-3-amd64: Network adapter (Intel 82579V) hangs during TX, causing reset and undetected data corruption at the other side

control: severity -1 important thanks So in terms of deep-freeze bug triage and cleanup, what do we want to do with this? It's been over a year, and there aren't any "me-too" here, even though there are reports of a similar problem at suse and ubuntu. Regardless, it doesn't seem to be a wide-s

Processed: Re: linux-image-3.10-3-amd64: Network adapter (Intel 82579V) hangs during TX, causing reset and undetected data corruption at the other side

Processing control commands: > severity -1 important Bug #727149 [src:linux] linux-image-3.10-3-amd64: Network adapter (Intel 82579V) hangs during TX, causing reset and undetected data corruption at the other side Severity set to 'important' from 'critical' -- 727149: http://bugs.debian.org/cg

Processed: Re: Bug#772983: kirkwood kernel image is too big

Processing control commands: > severity -1 important Bug #772983 [src:linux] kirkwood kernel image is too big Severity set to 'important' from 'serious' > retitle -1 armel kernel images are close to size limits Bug #772983 [src:linux] kirkwood kernel image is too big Changed Bug title to 'armel ke

Bug#772983: kirkwood kernel image is too big

Control: severity -1 important Control: retitle -1 armel kernel images are close to size limits On Fri, 2014-12-12 at 19:36 +, Ian Campbell wrote: > On Fri, 2014-12-12 at 18:12 +, Ben Hutchings wrote: > > Package: src:linux > > Version: 3.16.7-2 > > Severity: serious > > > > The kirkwood

Bug#772983: kirkwood kernel image is too big

On Fri, 2014-12-12 at 18:12 +, Ben Hutchings wrote: > Package: src:linux > Version: 3.16.7-2 > Severity: serious > > The kirkwood and orion5x kernel images generally have to be installed > in flash partitions with a fixed size. Currently we check at build > time that vmlinuz is small enough t

Bug#772983: kirkwood kernel image is too big

Package: src:linux Version: 3.16.7-2 Severity: serious The kirkwood and orion5x kernel images generally have to be installed in flash partitions with a fixed size. Currently we check at build time that vmlinuz is small enough to fit. However, these platforms now require Device Tree blobs, and th

Bug#772953: Enable several Kconfigs to support OMAP5432 uEVM devboard

Source: linux Version: 3.16.7-2 Severity: important Tags: patch I have been trying debian kernel on my OMAP5432 uEVM devboard these days and now manage to boot it by adding some extra configs in the kernel and use the lateset initramfs-tools from git to include some .ko of regulator drivers in the

Bug#772951: linux-image-3.16.0-4-amd64: Soekris net6501 clocksource refined-jiffies unstable - force enable HPET

Package: src:linux Version: 3.16.7-2 Severity: normal Dear Maintainer, upgrading Debian Wheezy (3.2) to Jessie (3.16) renders internal clocksource unstable. ntpd cannot keep up. Jitter is high. As soon as HPET is enabled and intel_idle.max_cstate=1 is passed the clocksource stays with tsc and r

Processed: https://bugzilla.kernel.org/show_bug.cgi?id=89621

Processing commands for cont...@bugs.debian.org: > forwarded 772848 https://bugzilla.kernel.org/show_bug.cgi?id=89621 Bug #772848 [src:linux] linux-image-3.16-0.bpo.2-amd64: ext3 fs gets ext4_mb_release_inode_pa error, remounted read-only Set Bug forwarded-to-address to 'https://bugzilla.kernel.

Bug#772848: ext3 fs gets ext4_mb_release_inode_pa error, remounted read-only

Here's what the fsck looked like. No serious damage. root@olympic:~# fsck -y /dev/olympic/olympic-imap fsck from util-linux 2.20.1 e2fsck 1.42.5 (29-Jul-2012) olympic-imap: recovering journal olympic-imap contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and size

Bug#772848: ext3 fs gets ext4_mb_release_inode_pa error, remounted read-only)

It turns out that this is not the first time I've seen this bug, it happened on another VM (on another physical machine). The storage stack is similar: On the host (3.16-0.bpo.2-amd64): mdadm raid (2 SATA disks) LVM On the guest (3.16-0.bpo.2-amd64) LVM2, ext3 filesystem. Dec 10 22:33:24 cedri

Processed: reassign 763431 to src:linux

Processing commands for cont...@bugs.debian.org: > reassign 763431 src:linux Bug #763431 [linux-image-3.16-2-amd64] linux-image-3.16-2-amd64: Doesn't finish booting Warning: Unknown package 'linux-image-3.16-2-amd64' Bug reassigned from package 'linux-image-3.16-2-amd64' to 'src:linux'. No longer

linux_3.18-1~exp1_multi.changes ACCEPTED into experimental, experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 11 Dec 2014 00:43:21 + Source: linux Binary: linux-source-3.18 linux-doc-3.18 linux-manual-3.18 linux-support-3.18.0-trunk linux-libc-dev linux-headers-3.18.0-trunk-all linux-headers-3.18.0-trunk-all-alpha li

linux_3.2.63-2+deb7u2_multi.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Dec 2014 03:42:14 + Source: linux Binary: linux-source-3.2 linux-doc-3.2 linux-manual-3.2 linux-support-3.2.0-4 linux-libc-dev linux-headers-3.2.0-4-all linux-headers-3.2.0-4-all-alpha linux-headers-3.2.0-