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

[paul . szabo]

Dear Fengguang,

> There are 260MB reclaimable slab pages in the normal zone ...

Marked "all_unreclaimable? yes": is that wrong? Question asked also in:
http://marc.info/?l=linux-mm&m=135873981326767&w=2

> ... however we somehow failed to reclaim them. ...

I made a patch that would do a drop_caches at that point, please see:
http://bugs.debian.org/695182
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=101;filename=drop_caches.patch;att=1;bug=695182
http://marc.info/?l=linux-mm&m=135785511125549&w=2
and that successfully avoided OOM when writing files.
But, the drop_caches patch did not protect against the "sleep test".

> ... What's your filesystem and the content of /proc/slabinfo?

Filesystem is EXT3. See output of slabinfo in Debian bug above or in
http://marc.info/?l=linux-mm&m=135796154427544&w=2

Thanks, Paul

Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/201301250147.r0p1l00t001...@como.maths.usyd.edu.au

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

[Fengguang Wu]

On Fri, Jan 25, 2013 at 10:43:45AM +1100, paul.sz...@sydney.edu.au wrote:
> Dear Fengguang,
> 
> > Or more simple, you may show us the OOM dmesg which will contain the
> > number of dirty pages. ...
> 
> Do you mean kern.log lines like:

Yes.

> [  744.754199] bash invoked oom-killer: gfp_mask=0xd0, order=1, oom_adj=0, 
> oom_score_adj=0

It's an 2-page allocation in the Normal zone.

> [  744.754202] bash cpuset=/ mems_allowed=0
> [  744.754204] Pid: 3836, comm: bash Not tainted 3.2.0-4-686-pae #1 Debian 
> 3.2.32-1
> ...
> [  744.754354] active_anon:13497 inactive_anon:129 isolated_anon:0
> [  744.754354]  active_file:2664 inactive_file:4144756 isolated_file:0
> [  744.754355]  unevictable:0 dirty:510 writeback:0 unstable:0

Almost no dirty/writeback pages.

> [  744.754356]  free:11867217 slab_reclaimable:68289 slab_unreclaimable:7204
> [  744.754356]  mapped:8066 shmem:250 pagetables:519 bounce:0
> [  744.754361] DMA free:4260kB min:784kB low:980kB high:1176kB 
> active_anon:0kB inactive_anon:0kB active_file:4kB inactive_file:0kB 
> unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15784kB 
> mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB 
> slab_reclaimable:11628kB slab_unreclaimable:4kB kernel_stack:0kB 
> pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:499 
> all_unreclaimable? yes
> [  744.754364] lowmem_reserve[]: 0 867 62932 62932
> [  744.754369] Normal free:43788kB min:44112kB low:55140kB high:66168kB 
> active_anon:0kB inactive_anon:0kB active_file:912kB inactive_file:0kB 
> unevictable:0kB isolated(anon):0kB isolated(file):0kB present:887976kB 
> mlocked:0kB dirty:0kB writeback:0kB mapped:4kB shmem:0kB 
> slab_reclaimable:261528kB slab_unreclaimable:28812kB kernel_stack:3096kB 
> pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:16060 
> all_unreclaimable? yes

There are 260MB reclaimable slab pages in the normal zone, however we
somehow failed to reclaim them. What's your filesystem and the content
of /proc/slabinfo?

> [  744.754372] lowmem_reserve[]: 0 0 496525 496525
> [  744.754377] HighMem free:47420820kB min:512kB low:789888kB high:1579264kB 
> active_anon:53988kB inactive_anon:516kB active_file:9740kB 
> inactive_file:16579320kB unevictable:0kB isolated(anon):0kB 
> isolated(file):0kB present:63555300kB mlocked:0kB dirty:2040kB writeback:0kB 
> mapped:32260kB shmem:1000kB slab_reclaimable:0kB slab_unreclaimable:0kB 
> kernel_stack:0kB pagetables:2076kB unstable:0kB bounce:0kB writeback_tmp:0kB 
> pages_scanned:0 all_unreclaimable? no

There are plenty of free and inactive file pages in the HighMem zone.

Thanks,
Fengguang

> [  744.754380] lowmem_reserve[]: 0 0 0 0
> [  744.754381] DMA: 445*4kB 36*8kB 3*16kB 1*32kB 1*64kB 0*128kB 0*256kB 
> 0*512kB 0*1024kB 1*2048kB 0*4096kB = 4260kB
> [  744.754386] Normal: 1132*4kB 620*8kB 237*16kB 70*32kB 38*64kB 26*128kB 
> 20*256kB 14*512kB 4*1024kB 3*2048kB 0*4096kB = 43808kB
> [  744.754390] HighMem: 226*4kB 242*8kB 155*16kB 66*32kB 10*64kB 1*128kB 
> 1*256kB 0*512kB 1*1024kB 2*2048kB 11574*4096kB = 47420680kB
> [  744.754395] 4148173 total pagecache pages
> [  744.754396] 0 pages in swap cache
> [  744.754397] Swap cache stats: add 0, delete 0, find 0/0
> [  744.754397] Free swap  = 0kB
> [  744.754398] Total swap = 0kB
> [  744.900649] 16777200 pages RAM
> [  744.900650] 16549378 pages HighMem
> [  744.900651] 664304 pages reserved
> [  744.900652] 4162276 pages shared
> [  744.900653] 104263 pages non-shared
> 
> ? (The above and similar were reported to http://bugs.debian.org/695182 .)
> Do you want me to log and report something else?
> 
> I believe the above crash may be provoked simply by running:
>   n=0; while [ $n -lt 99 ]; do dd bs=1M count=1024 if=/dev/zero of=x$n; (( n 
> = $n + 1 )); done &
> on any PAE machine with over 32GB RAM. Oddly the problem does not seem
> to occur when using mem=32g or lower on the kernel boot line (or on
> machines with less than 32GB RAM).
> 
> Cheers, Paul
> 
> Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
> School of Mathematics and Statistics   University of SydneyAustralia


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130125005529.GA21668@localhost

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

[paul . szabo]

Dear Jan,

> I think he found the culprit of the problem being min_free_kbytes was not
> properly reflected in the dirty throttling. ... Paul please correct me
> if I'm wrong.

Sorry but have to correct you.

I noticed and patched/corrected two problems, one with (setpoint-dirty)
in bdi_position_ratio(), another with min_free_kbytes not subtracted
from dirtyable memory. Fixing those problems, singly or in combination,
did not help in avoiding OOM: running
  n=0; while [ $n -lt 99 ]; do dd bs=1M count=1024 if=/dev/zero of=x$n; 
((n=$n+1)); done
still produces an OOM after a few files written (on a PAE machine with
over 32GB RAM).

Also, a quite similar OOM may be produced on any PAE machine with
  n=0; while [ $n -lt 33000 ]; do sleep 600 & ((n=n+1)); done
This was tested on machines with as low as just 3GB RAM ... and
curiously the same machine with "plain" (not PAE but HIGHMEM4G)
kernel handles the same "sleep test" without any problems.

(Thus I now think that the remaining bug is not with writeback.)

Cheers, Paul

Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/201301250015.r0p0fr3t003...@como.maths.usyd.edu.au

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

[paul . szabo]

Dear Fengguang,

> Or more simple, you may show us the OOM dmesg which will contain the
> number of dirty pages. ...

Do you mean kern.log lines like:

[  744.754199] bash invoked oom-killer: gfp_mask=0xd0, order=1, oom_adj=0, 
oom_score_adj=0
[  744.754202] bash cpuset=/ mems_allowed=0
[  744.754204] Pid: 3836, comm: bash Not tainted 3.2.0-4-686-pae #1 Debian 
3.2.32-1
...
[  744.754354] active_anon:13497 inactive_anon:129 isolated_anon:0
[  744.754354]  active_file:2664 inactive_file:4144756 isolated_file:0
[  744.754355]  unevictable:0 dirty:510 writeback:0 unstable:0
[  744.754356]  free:11867217 slab_reclaimable:68289 slab_unreclaimable:7204
[  744.754356]  mapped:8066 shmem:250 pagetables:519 bounce:0
[  744.754361] DMA free:4260kB min:784kB low:980kB high:1176kB active_anon:0kB 
inactive_anon:0kB active_file:4kB inactive_file:0kB unevictable:0kB 
isolated(anon):0kB isolated(file):0kB present:15784kB mlocked:0kB dirty:0kB 
writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:11628kB 
slab_unreclaimable:4kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB 
writeback_tmp:0kB pages_scanned:499 all_unreclaimable? yes
[  744.754364] lowmem_reserve[]: 0 867 62932 62932
[  744.754369] Normal free:43788kB min:44112kB low:55140kB high:66168kB 
active_anon:0kB inactive_anon:0kB active_file:912kB inactive_file:0kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:887976kB 
mlocked:0kB dirty:0kB writeback:0kB mapped:4kB shmem:0kB 
slab_reclaimable:261528kB slab_unreclaimable:28812kB kernel_stack:3096kB 
pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:16060 
all_unreclaimable? yes
[  744.754372] lowmem_reserve[]: 0 0 496525 496525
[  744.754377] HighMem free:47420820kB min:512kB low:789888kB high:1579264kB 
active_anon:53988kB inactive_anon:516kB active_file:9740kB 
inactive_file:16579320kB unevictable:0kB isolated(anon):0kB isolated(file):0kB 
present:63555300kB mlocked:0kB dirty:2040kB writeback:0kB mapped:32260kB 
shmem:1000kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB 
pagetables:2076kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 
all_unreclaimable? no
[  744.754380] lowmem_reserve[]: 0 0 0 0
[  744.754381] DMA: 445*4kB 36*8kB 3*16kB 1*32kB 1*64kB 0*128kB 0*256kB 0*512kB 
0*1024kB 1*2048kB 0*4096kB = 4260kB
[  744.754386] Normal: 1132*4kB 620*8kB 237*16kB 70*32kB 38*64kB 26*128kB 
20*256kB 14*512kB 4*1024kB 3*2048kB 0*4096kB = 43808kB
[  744.754390] HighMem: 226*4kB 242*8kB 155*16kB 66*32kB 10*64kB 1*128kB 
1*256kB 0*512kB 1*1024kB 2*2048kB 11574*4096kB = 47420680kB
[  744.754395] 4148173 total pagecache pages
[  744.754396] 0 pages in swap cache
[  744.754397] Swap cache stats: add 0, delete 0, find 0/0
[  744.754397] Free swap  = 0kB
[  744.754398] Total swap = 0kB
[  744.900649] 16777200 pages RAM
[  744.900650] 16549378 pages HighMem
[  744.900651] 664304 pages reserved
[  744.900652] 4162276 pages shared
[  744.900653] 104263 pages non-shared

? (The above and similar were reported to http://bugs.debian.org/695182 .)
Do you want me to log and report something else?

I believe the above crash may be provoked simply by running:
  n=0; while [ $n -lt 99 ]; do dd bs=1M count=1024 if=/dev/zero of=x$n; (( n = 
$n + 1 )); done &
on any PAE machine with over 32GB RAM. Oddly the problem does not seem
to occur when using mem=32g or lower on the kernel boot line (or on
machines with less than 32GB RAM).

Cheers, Paul

Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/201301242343.r0onhjxr024...@como.maths.usyd.edu.au

Processed: bug 697029 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=59792

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 697029 https://bugs.freedesktop.org/show_bug.cgi?id=59792
Bug #697029 [src:linux] linux-image-3.2.0-4-amd64: i915_hangcheck_ring_idle 
error makes the computer lag using intel core i7-620 integrated gpu
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=59792'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
697029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.135904922724669.transcr...@bugs.debian.org

[bts-link] source package linux-2.6

[bts-link-upstream]

#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #627372 (http://bugs.debian.org/627372)
# Bug title: linux-image-2.6.38-2-686: Console turns black during boot
#  * https://bugs.freedesktop.org/show_bug.cgi?id=44156
#  * remote status changed: NEW -> RESOLVED
#  * remote resolution changed: (?) -> FIXED
#  * closed upstream
tags 627372 + fixed-upstream
usertags 627372 - status-NEW
usertags 627372 + status-RESOLVED resolution-FIXED

# remote status report for #627372 (http://bugs.debian.org/627372)
# Bug title: linux-image-2.6.38-2-686: Console turns black during boot
#  * https://bugs.freedesktop.org/show_bug.cgi?id=44156
#  * remote status changed: NEW -> RESOLVED
#  * remote resolution changed: (?) -> FIXED
#  * closed upstream
tags 627372 + fixed-upstream
usertags 627372 - status-NEW
usertags 627372 + status-RESOLVED resolution-FIXED

thanks


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130124164021.16111.56882.btsl...@sonntag.debian.org

[bts-link] source package src:linux

[bts-link-upstream]

#
# bts-link upstream status pull for source package src:linux
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #698376 (http://bugs.debian.org/698376)
# Bug title: linux-image-3.2.0-4-686-pae: fscache do not cache largefile (> 
2GB).
#  * http://bugzilla.kernel.org/show_bug.cgi?id=31182
#  * remote status changed: (?) -> RESOLVED
#  * remote resolution changed: (?) -> CODE-FIX
#  * closed upstream
tags 698376 + fixed-upstream
usertags 698376 + status-RESOLVED resolution-CODE-FIX

# remote status report for #680737 (http://bugs.debian.org/680737)
# Bug title: linux-image-3.2.0-2-amd64: Intel i915: black display after boot
#  * https://bugs.freedesktop.org/show_bug.cgi?id=59628
#  * remote status changed: (?) -> RESOLVED
#  * remote resolution changed: (?) -> FIXED
#  * closed upstream
tags 680737 + fixed-upstream
usertags 680737 + status-RESOLVED resolution-FIXED

# remote status report for #697741 (http://bugs.debian.org/697741)
# Bug title: i915: Black screen/no console with KMS
#  * https://bugs.freedesktop.org/show_bug.cgi?id=53926
#  * remote status changed: (?) -> ASSIGNED
usertags 697741 + status-ASSIGNED

thanks


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130124164021.16111.72735.btsl...@sonntag.debian.org

Processed: [bts-link] source package src:linux

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:linux
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #698376 (http://bugs.debian.org/698376)
> # Bug title: linux-image-3.2.0-4-686-pae: fscache do not cache largefile (> 
> 2GB).
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=31182
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> CODE-FIX
> #  * closed upstream
> tags 698376 + fixed-upstream
Bug #698376 [src:linux] linux-image-3.2.0-4-686-pae: fscache do not cache 
largefile (> 2GB).
Added tag(s) fixed-upstream.
> usertags 698376 + status-RESOLVED resolution-CODE-FIX
There were no usertags set.
Usertags are now: resolution-CODE-FIX status-RESOLVED.
> # remote status report for #680737 (http://bugs.debian.org/680737)
> # Bug title: linux-image-3.2.0-2-amd64: Intel i915: black display after boot
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=59628
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 680737 + fixed-upstream
Bug #680737 [src:linux] linux-image-3.2.0-2-amd64: Intel i915: black display 
after boot
Added tag(s) fixed-upstream.
> usertags 680737 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> # remote status report for #697741 (http://bugs.debian.org/697741)
> # Bug title: i915: Black screen/no console with KMS
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=53926
> #  * remote status changed: (?) -> ASSIGNED
> usertags 697741 + status-ASSIGNED
There were no usertags set.
Usertags are now: status-ASSIGNED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
680737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680737
697741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697741
698376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.135904563130917.transcr...@bugs.debian.org

Processed: [bts-link] source package linux-2.6

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package linux-2.6
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #627372 (http://bugs.debian.org/627372)
> # Bug title: linux-image-2.6.38-2-686: Console turns black during boot
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=44156
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 627372 + fixed-upstream
Bug #627372 [linux-2.6] linux-image-2.6.38-2-686: Console turns black during 
boot
Bug #625727 [linux-2.6] linux-image-2.6.38-2-amd64: Console turns black during 
boot, backlight turns off
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 627372 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 627372 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> # remote status report for #627372 (http://bugs.debian.org/627372)
> # Bug title: linux-image-2.6.38-2-686: Console turns black during boot
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=44156
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 627372 + fixed-upstream
Bug #627372 [linux-2.6] linux-image-2.6.38-2-686: Console turns black during 
boot
Bug #625727 [linux-2.6] linux-image-2.6.38-2-amd64: Console turns black during 
boot, backlight turns off
Ignoring request to alter tags of bug #627372 to the same tags previously set
Ignoring request to alter tags of bug #625727 to the same tags previously set
> usertags 627372 - status-NEW
Usertags were: status-RESOLVED resolution-FIXED.
Usertags are now: status-RESOLVED resolution-FIXED.
> usertags 627372 + status-RESOLVED resolution-FIXED
Usertags were: status-RESOLVED resolution-FIXED.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
625727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625727
627372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.135904563130886.transcr...@bugs.debian.org

Bug#697029: [squeeze -> wheezy regression] i915_hangcheck_ring_idle error makes the computer lag using intel core i7-620 integrated gpu

[Pierre AUSSAGUEL]

FUY, I filed a bug : n° 59792

https://bugs.freedesktop.org/show_bug.cgi?id=59792


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51015826.4070...@yahoo.fr

Bug#698854: linux-image-3.2.0-4-686-pae: p54 driver fails to reload firmware coming out of suspend to RAM

[Paul Bryan Roberts]

Package: src:linux
Version: 3.2.35-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Either:
 a) request Suspend at the XFCE desktop
 b) set Power Manager to suspend after a period of inactivty
Then:
 resume from suspend by touchpad or keyboard activity

   * What exactly did you do (or not do) that was effective ?

I did (or did not) as I always did (or did not) when running
Debian Squeeze: the Wheezy behaviour is regressive.

   * What was the outcome of this action?

No wireless network connection after resumse
(until the PCMCIA network card is ejcted and reinserted).

   * What outcome did you expect instead?

Wireless connection to be restablished automatically by
the desktop network manager (wicd in this instance).

-- Notes

dmesg below shows the end of failure to resume and then
the success after ejecting and reinserting the card.

The firmware image is 2.13.1.0.arm 
(md5sum 8ff41cff31c9323330d6170b54735477) taken from
http://daemonizer.de/prism54/prism54-fw/.

This is not the most recent image but it is the most
recent that the network card will boot.

Repeat, resume from suspend to RAM worked perfectly
well under Debian Squeeze with this firmware image.

The machine also fails to recover the wireless network
connnection after hibernation.


-- Package-specific info:
** Version:
Linux version 3.2.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version 
4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.35-2

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae 
root=UUID=1d6f9e11-20cb-4aa9-945b-ca7961131bea ro quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[ 2667.981805]  [] ? __driver_attach+0x5b/0x5b
[ 2667.981816]  [] ? bus_probe_device+0x1f/0x74
[ 2667.981847]  [] ? device_add+0x388/0x4e7
[ 2667.981864]  [] ? pci_bus_read_config_byte+0x51/0x5a
[ 2667.981878]  [] ? pci_bus_add_device+0xc/0x2c
[ 2667.981888]  [] ? pci_bus_add_devices+0x1d/0xaf
[ 2667.981912]  [] ? cb_alloc+0x97/0xf84 [pcmcia_core]
[ 2667.981929]  [] ? socket_late_resume+0x78/0x93 [pcmcia_core]
[ 2667.981945]  [] ? pcmcia_socket_dev_resume+0x19/0x27 [pcmcia_core]
[ 2667.981956]  [] ? pm_op+0x84/0x108
[ 2667.981967]  [] ? device_resume+0x78/0xc1
[ 2667.981977]  [] ? dpm_resume+0xbe/0x151
[ 2667.981988]  [] ? dpm_resume_end+0x8/0x10
[ 2667.982006]  [] ? suspend_devices_and_enter+0x1a3/0x1db
[ 2667.982016]  [] ? enter_state+0x111/0x14d
[ 2667.982027]  [] ? state_store+0x93/0xcd
[ 2667.982037]  [] ? pm_async_store+0x2d/0x2d
[ 2667.982060]  [] ? kobj_attr_store+0x18/0x1c
[ 2667.982082]  [] ? sysfs_write_file+0xb6/0xe3
[ 2667.982093]  [] ? sysfs_poll+0x60/0x60
[ 2667.982123]  [] ? vfs_write+0x83/0xd4
[ 2667.982134]  [] ? sys_write+0x3d/0x61
[ 2667.982150]  [] ? sysenter_do_call+0x12/0x28
[ 2667.982159] ---[ end trace d6af62e7099b8a09 ]---
[ 2667.982170] p54pci :02:00.0: firmware: isl3886pci will not be loaded
[ 2667.982181] [ cut here ]
[ 2667.982193] WARNING: at 
/build/buildd-linux_3.2.35-2-i386-pOtnxQ/linux-3.2.35/drivers/base/firmware_class.c:547
 _request_firmware+0xbe/0x334()
[ 2667.982202] Hardware name: Versa Premium
[ 2667.982206] Modules linked in: sis sisfb drm ppdev lp bnep rfcomm bluetooth 
autofs4 uinput nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop arc4 
p54pci p54common mac80211 cfg80211 joydev rfkill snd_trident snd_ac97_codec 
snd_util_mem snd_mpu401_uart snd_seq_midi snd_seq_midi_event snd_rawmidi pcmcia 
snd_pcm snd_page_alloc snd_seq snd_seq_device snd_timer psmouse snd 
yenta_socket shpchp serio_raw pcmcia_rsrc evdev pcmcia_core pcspkr soundcore 
ac97_bus gameport i2c_sis630 i2c_core button battery irda parport_pc parport 
crc_ccitt processor ac power_supply thermal_sys ext4 crc16 jbd2 mbcache sg 
sr_mod sd_mod cdrom crc_t10dif ohci_hcd ehci_hcd usbcore ata_generic usb_common 
pata_sis libata floppy scsi_mod [last unloaded: scsi_wait_scan]
[ 2667.982336] Pid: 4996, comm: pm-suspend Tainted: GW
3.2.0-4-686-pae #1 Debian 3.2.35-2
[ 2667.982343] Call Trace:
[ 2667.982355]  [] ? warn_slowpath_common+0x68/0x79
[ 2667.982366]  [] ? _request_firmware+0xbe/0x334
[ 2667.982378]  [] ? warn_slowpath_null+0xd/0x10
[ 2667.982389]  [] ? _request_firmware+0xbe/0x334
[ 2667.982402]  [] ? request_firmware+0x9/0xc
[ 2667.982416]  [] ? p54p_probe+0x29a/0x32e [p54pci]
[ 2667.982432]  [] ? dma_set_mask+0x35/0x35
[ 2667.982444]  [] ? pci_device_probe+0x53/0x9a
[ 2667.982457]  [] ? driver_probe_device+0x8c/0x10c
[ 2667.982467]  [] ? bus_for_each_drv+0x37/0x60
[ 2667.982478]  [] ? device_attach+0x58/0x74
[ 2667.982488]  [] ? __driver_attach+0x5b/0x5b
[ 2667.982498]  [] ? bus_probe_device+0x1f/0x74
[ 2667.982511]  [] ? device_add+0x388/0x4e7
[ 2667.982521]  [] ? pci_bus_read_config_byte+0x51/0x5a
[ 2667.982533]  [] ? pci_bus_add_device+0xc/0x2c
[ 2667.982543]  [] ? pci_bus_add_devices+0x1d/0xaf
[ 2667.982564]  [] ? cb_alloc+0x97/0xf84 [pcmcia_core]
[ 2667.982581]  [] ? socket_late_resume+0x78/0x93 [pcmcia_core]
[ 2667.982596]  [] ? pcmcia_socket_dev_

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

[Jan Kara]

On Thu 24-01-13 22:57:07, Wu Fengguang wrote:
> Hi Paul,
> 
> > (This patch does not solve the PAE OOM issue.)
> 
> You may try the below debug patch. The only way the writeback patches
> should trigger OOM, I think, is for the number of dirty/writeback
> pages going out of control.
> 
> Or more simple, you may show us the OOM dmesg which will contain the
> number of dirty pages. Or run this in a continuous loop during your
> tests, and see how the dirty numbers change before OOM:
  I think he found the culprit of the problem being min_free_kbytes was not
properly reflected in the dirty throttling. But the patch has been already
picked up by Andrew so I didn't forward it to you. Paul please correct me
if I'm wrong.

Honza

> 
> while :
> do
> grep -E '(Dirty|Writeback)' /proc/meminfo
> sleep 1
> done
> 
> Thanks,
> Fengguang
> 
> diff --git a/mm/page-writeback.c b/mm/page-writeback.c
> index 50f0824..cf1165a 100644
> --- a/mm/page-writeback.c
> +++ b/mm/page-writeback.c
> @@ -1147,6 +1147,16 @@ pause:
>   if (task_ratelimit)
>   break;
>  
> + if (nr_dirty > dirty_thresh + dirty_thresh / 2) {
> + if (printk_ratelimit())
> + printk(KERN_WARNING "nr_dirty=%lu 
> dirty_thresh=%lu task_ratelimit=%lu dirty_ratelimit=%lu pos_ratio=%lu\n",
> +nr_dirty,
> +dirty_thresh,
> +task_ratelimit,
> +dirty_ratelimit,
> +pos_ratio);
> + }
> +
>   /*
>* In the case of an unresponding NFS server and the NFS dirty
>* pages exceeds dirty_thresh, give the other good bdi's a pipe
-- 
Jan Kara 
SUSE Labs, CR


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130124151603.gd21...@quack.suse.cz

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

[Fengguang Wu]

Hi Paul,

> (This patch does not solve the PAE OOM issue.)

You may try the below debug patch. The only way the writeback patches
should trigger OOM, I think, is for the number of dirty/writeback
pages going out of control.

Or more simple, you may show us the OOM dmesg which will contain the
number of dirty pages. Or run this in a continuous loop during your
tests, and see how the dirty numbers change before OOM:

while :
do
grep -E '(Dirty|Writeback)' /proc/meminfo
sleep 1
done

Thanks,
Fengguang

diff --git a/mm/page-writeback.c b/mm/page-writeback.c
index 50f0824..cf1165a 100644
--- a/mm/page-writeback.c
+++ b/mm/page-writeback.c
@@ -1147,6 +1147,16 @@ pause:
if (task_ratelimit)
break;
 
+   if (nr_dirty > dirty_thresh + dirty_thresh / 2) {
+   if (printk_ratelimit())
+   printk(KERN_WARNING "nr_dirty=%lu 
dirty_thresh=%lu task_ratelimit=%lu dirty_ratelimit=%lu pos_ratio=%lu\n",
+  nr_dirty,
+  dirty_thresh,
+  task_ratelimit,
+  dirty_ratelimit,
+  pos_ratio);
+   }
+
/*
 * In the case of an unresponding NFS server and the NFS dirty
 * pages exceeds dirty_thresh, give the other good bdi's a pipe


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130124145707.GB12745@localhost

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

[Fengguang Wu]

On Wed, Jan 23, 2013 at 12:54:38AM +0100, Jan Kara wrote:
> 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 architectures, does not affect 64-bit architectures where long
> > and s64 are equivalent.
> > 
> > In this function, dirty is between freerun and limit, the pseudo-float x
> > is between [-1,1], expected to be negative about half the time. With
> > zero-padding, instead of a small negative x we obtained a large positive
> > one so bdi_position_ratio() returned garbage.
> > 
> > Casting the difference to s64 also prevents overflow with left-shift;
> > though normally these numbers are small and I never observed a 32-bit
> > overflow there.
> > 
> > (This patch does not solve the PAE OOM issue.)
> > 
> > Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
> > School of Mathematics and Statistics   University of SydneyAustralia
> > 
> > Reported-by: Paul Szabo 
> > Reference: http://bugs.debian.org/695182
> > Signed-off-by: Paul Szabo 
>   Ah, good catch. Thanks for the patch. You can add:
> Reviewed-by: Jan Kara 
> 
>   I've also added CC to writeback maintainer.

Applied. Thanks! It's a good fix.

Thanks,
Fengguang


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130124141441.GA12745@localhost

Bug#697029: [squeeze -> wheezy regression] i915_hangcheck_ring_idle error makes the computer lag using intel core i7-620 integrated gpu

[Pierre AUSSAGUEL]

Le 23/01/2013 18:35, Jonathan Nieder a écrit :

Pierre AUSSAGUEL wrote:


I installed again linux-image-3.7-trunk-amd64 to be able to report the bug,
but the problem seem to have gone by now !
Maybe the version has changed (I am currently using 3.7.3-1~experimental.1
x86_64) since my previous try, a few weeks ago.

[...]

What can I do to help to track it down ?


That's good news.  If you have time to find the newest broken and
oldest fixed kernel among the pre-compiled kernels at
, that would help in
narrowing down the range of patches to sift through.

Thanks much,
Jonathan


Unfortunately, it seems that the problem is not really fixed.
This morning my system is very slow with the 3.7.3-1 kernel, and the 
glxgears score is close to 2 instead of 1400 yesterday !

Yesterday the system was fully usable... In don't understand.

I will report the bug in the experimental kernel and keep you informed here.


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5100efe7.7010...@yahoo.fr