Bug#708995: iptables firewall is dropping GRO'd packets

Package: src:linux Version: 3.2.41-2+deb7u2 Severity: normal I attemped to update a Windows system yesterday, and after about a minute it failed with a generic error code which MS suggests usually indicates a firewall problem. I retried a few times, but with the same result. All my firewall rule

Bug#708994: perf script net_dropmonitor reports complete nonsense

Package: linux-tools-3.2 Version: 3.2.17-1 Severity: normal Tags: upstream The net_dropmonitor script for perf doesn't look up symbols correctly, e.g.: LOCATIONOFFSET COUNT __per_cpu_start 0

Bug#699667: Do new versions fix this?

I hit this same problem when I updated my DNS-323 (via apt-get dist-upgrade, a day or two after Wheezy went stable). Serial cable confirms the problem. I plan to try the sid kernel, once I can figure out how (here's hoping the netinst kernel/initrd can boot a rescue image). Before I waste my time,

Bug#708987: pacemaker cannot start nfs-kernel-server when /etc/exports is empty

Package: nfs-kernel-server Version: 1:1.2.6-3 I use ocf:heartbeat:exportfs and lsb:nfs-kernel-server to manage nfs exports and nfs service resources in a pacemaker and corosync based Linux HA. In this situation, all the nfs exports are managed by the ocf:heartbeat:exportfs resource agent and /etc/

Processed: Re: Bug#708757: linux-image-3.2.0-4-amd64: via-rhine network card fails to initialise correctly

Processing control commands: > tag -1 - moreinfo Bug #708757 [src:linux] linux-image-3.2.0-4-amd64: via-rhine network card fails to initialise correctly Removed tag(s) moreinfo. -- 708757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708757 Debian Bug Tracking System Contact ow...@bugs.debi

Bug#708757: linux-image-3.2.0-4-amd64: via-rhine network card fails to initialise correctly

Control: tag -1 - moreinfo On Sun, 2013-05-19 at 13:26 +1000, Mark Berndt wrote: > On Sun, 19 May 2013 12:14:21 AM Ben Hutchings wrote: > > Control: tag -1 moreinfo > > > > On Sat, 2013-05-18 at 21:39 +1000, marko wrote: > > > Package: src:linux > > > Version: 3.2.41-2+deb7u2 > > > Severity: norm

Bug#701189: marked as done (linux-image-3.7-trunk-amd64: 3.7.8 locks up occasionally)

Your message dated Sun, 19 May 2013 23:21:16 +0100 with message-id <1369002076.3469.105.ca...@deadeye.wl.decadent.org.uk> and subject line Re: Bug#701189: linux-image-3.7-trunk-amd64: 3.7.8 locks up occasionally has caused the Debian Bug report #701189, regarding linux-image-3.7-trunk-amd64: 3.7.8

Bug#708965: how to "reboot into new kernel"

On Sun, 2013-05-19 at 23:28 +0200, nobswolf wrote: > Hello Ben, > > I run a plain Dabian 6 system and run updates regularly. And the system > uses GRUB. Synaptic tells me, everything is up to date. > > Please tell me how tell the system to run the newest kernel. Normally, you would just reboot.

Bug#708965: how to "reboot into new kernel"

Hello Ben, I run a plain Dabian 6 system and run updates regularly. And the system uses GRUB. Synaptic tells me, everything is up to date. Please tell me how tell the system to run the newest kernel. Thanks for any help. Regards Emil -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.d

Bug#708965: marked as done (vfat: module vfat not loadable)

Your message dated Sun, 19 May 2013 21:12:02 +0100 with message-id <1368994322.3469.99.ca...@deadeye.wl.decadent.org.uk> and subject line Re: Bug#708965: vfat: module vfat not loadable has caused the Debian Bug report #708965, regarding vfat: module vfat not loadable to be marked as done. This mea

Bug#708965: vfat: module vfat not loadable

On Sun, 2013-05-19 at 22:05 +0200, nobswolf wrote: [...] > Linux version 2.6.32-5-amd64 (Debian 2.6.32-41) (b...@decadent.org.uk) (gcc > version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Jan 16 16:22:28 UTC 2012 In fact, you're running a really old version (2.6.32-41). [...] > Versions of packages lin

Bug#708965: vfat: module vfat not loadable

Package: linux-2.6 Version: 2.6.32-48squeeze3 Severity: important File: vfat root@okami:~# modprobe vfat FATAL: Error inserting vfat (/lib/modules/2.6.32-5-amd64/kernel/fs/fat/vfat.ko): Unknown symbol in module, or unknown parameter (see dmesg) root@okami:~# dmesg [40756.636280] vfat: Unknown sym

Processed: severity of 708849 is important

Processing commands for cont...@bugs.debian.org: > # hardware support is important > severity 708849 important Bug #708849 [linux-image-3.2.0-4-kirkwood] linux-image-3.2.0-4-kirkwood: Pogoplug Series 4 support Severity set to 'important' from 'wishlist' > thanks Stopping processing here. Please

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote: > Dear KVM maintainers, it appears that there is a gap in x86 emulation, > at least on a 32-bit host. Stefan found this when running GRML, a live > distribution which can be downloaded from: >

Bug#701189: linux-image-3.7-trunk-amd64: 3.7.8 locks up occasionally

On Wednesday, 20 March 2013 at 23:57, Ben Hutchings wrote: > That was the change that caused this memory leak. I doubt that it has > anything to do with the bug you reported. Well, I'll upload 3.8.4 soon > and you can find out whether it is really fixed. 3.8.5 ran for 33 days now without problem