Bug#695182: [PATCH] Subtract min_free_kbytes from dirtyable memory

2013-01-22 Thread paul . szabo
Dear Minchan, > So what's the effect for user? Sorry I have no idea. The kernel seems to work well without this patch; or in fact not so well, PAE crashing with spurious OOM. In my fruitless efforts of avoiding OOM by sensible choices of sysctl tunables, I noticed that maybe the treatment of min

Bug#695968: linux-image-3.2.0-4-amd64: ath.ko starts printing thousands of error messages several minutes after boot

2013-01-22 Thread Joel Diaz
On Sun, 2013-01-20 at 15:42 +, Ben Hutchings wrote: > I've looked for changes to the drive that seem related to power and > reset sequencing. Could you test whether applying the attached patches > to Debian's 3.2 kernel fixes the problem? See the instructions at >

Bug#695182: [PATCH] Subtract min_free_kbytes from dirtyable memory

2013-01-22 Thread Minchan Kim
On Mon, Jan 21, 2013 at 02:15:49PM +1100, paul.sz...@sydney.edu.au wrote: > When calculating amount of dirtyable memory, min_free_kbytes should be > subtracted because it is not intended for dirty pages. So what's the effect for user? It would be better to include that in description if possible.

Bug#695182: [PATCH] Negative (setpoint-dirty) in bdi_position_ratio()

2013-01-22 Thread Jan Kara
On Sun 20-01-13 11:02:10, paul.sz...@sydney.edu.au wrote: > In bdi_position_ratio(), get difference (setpoint-dirty) right even when > negative. Both setpoint and dirty are unsigned long, the difference was > zero-padded thus wrongly sign-extended to s64. This issue affects all > 32-bit architectur

Bug#695182: [PATCH] MAX_PAUSE to be at least 4

2013-01-22 Thread Andrew Morton
On Mon, 21 Jan 2013 14:07:34 +1100 paul.sz...@sydney.edu.au wrote: > Ensure MAX_PAUSE is 4 or larger, so limits in > return clamp_val(t, 4, MAX_PAUSE); > (the only use of it) are not back-to-front. MAX_PAUSE is not used in this fashion in current kernels. > (This patch does not solve the P

Bug#695182: [PATCH] MAX_PAUSE to be at least 4

2013-01-22 Thread Jan Kara
On Mon 21-01-13 14:07:34, paul.sz...@sydney.edu.au wrote: > Ensure MAX_PAUSE is 4 or larger, so limits in > return clamp_val(t, 4, MAX_PAUSE); > (the only use of it) are not back-to-front. > > (This patch does not solve the PAE OOM issue.) > > Paul Szabo p...@maths.usyd.edu.au http://ww

Bug#695182: [PATCH] Subtract min_free_kbytes from dirtyable memory

2013-01-22 Thread Andrew Morton
On Mon, 21 Jan 2013 14:15:49 +1100 paul.sz...@sydney.edu.au wrote: > When calculating amount of dirtyable memory, min_free_kbytes should be > subtracted because it is not intended for dirty pages. Makes sense. > Using an "extern int" because that is the only interface to some such > sysctl value

Processed: Re: USB 3.0 ext HDD drive doesnt work and hangs usb 3.0 hub

2013-01-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 697019 - moreinfo Bug #697019 [src:linux] linux-image-3.2.0-4-amd64: USB 3.0 ext HDD drive doesnt work and hangs usb 3.0 hub Removed tag(s) moreinfo. > fixed 697019 linux/3.7.3-1~experimental.1 Bug #697019 [src:linux] linux-image-3.2.0-4-amd

Bug#697357: bridging broken over bond interfaces

2013-01-22 Thread Bastian Blank
On Tue, Jan 22, 2013 at 09:25:35PM +0100, Ferenc Wagner wrote: > Bastian Blank writes: > > You want to use Open vSwitch for such setups. > Somewhat offtopic, but I left in the Cc-s to get it documented: why > should we prefer Open vSwitch over standard Linux bonding, bridge and > vlan interfaces i

Bug#697357: bridging broken over bond interfaces

2013-01-22 Thread Ferenc Wagner
Bastian Blank writes: > On Fri, Jan 04, 2013 at 12:17:12PM +0100, Peter Palfrader wrote: >> I tried to set up a new KVM host in the usual way: >> - have a bond0 interface over all physcial eth* interfaces >> - create a br0 over that bond0 and any vnet* interfaces for the >> guests. > > Yo

Bug#697357: bridging broken over bond interfaces

2013-01-22 Thread Ferenc Wagner
Ben Hutchings writes: > Forwarding this to netdev since the bug is still present in Linux 3.7.1. > For those joining us, this thread is archive at > . Please forgive me for eliding the previous discussion; I think I hit the same or a very similar problem in the sam

Bug#697019: linux-image-3.2.0-4-amd64: USB 3.0 ext HDD drive doesnt work and hangs usb 3.0 hub

2013-01-22 Thread Nikolay Kuzminykh
On 01/20/2013 08:09 PM, Ben Hutchings wrote: Control: tag -1 moreinfo Could you test whether Linux 3.7 (currently available in experimental ) still has this problem? Ben. There is no problem with my USB 3.0 hdd in kernel "3.7-trunk-amd64" (see attach

[BUG] 3w-9xxx BUG in Squeeze Installer

2013-01-22 Thread James Lamanna
Hi, I have a Quanta S45 motherboard that I'm trying to install Debian Squeeze on with a 3Ware 9650-4LPML RAID card. When the Debian installer inserts the 3w-9xxx module, I get the following kernel BUG. I've tried a different 9650 card and booting with acpi=off to no avail so far. Is this a MB issu

Processed: Re: Huge "Slab Unreclaimable" and continually growing

2013-01-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 519586 Bug #519586 {Done: maximilian attems } [linux-2.6] linux-image-2.6.26-1-xen-amd64: Huge "Slab Unreclaimable" and continually growing Unarchived Bug 519586 > reopen 519586 Bug #519586 {Done: maximilian attems } [linux-2.6] linux

Bug#697019: Message #20 (BugReport 697019)

2013-01-22 Thread Nick Y Kuzminyh
On 01/20/2013 08:09 PM, Ben Hutchings wrote: In step 3, I think you meant to say 'USB 3.0 port', right? Yes of course. In step 3, USB 3.0 is meant. Could you test whether Linux 3.7 (currently available in experimental ) still has this problem? Ben. I