public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null'
@ 2010-01-21 19:16 Toralf Förster
  2010-01-21 20:35 ` Alexey Dobriyan
  2010-01-28  4:51 ` Américo Wang
  0 siblings, 2 replies; 8+ messages in thread
From: Toralf Förster @ 2010-01-21 19:16 UTC (permalink / raw)
  To: linux-kernel

I was inspired by http://article.gmane.org/gmane.linux.kernel/941115 .

Running the command (se subject) as a normal user at a 2.6.32.4 kernel
gives this in /var/log/messages:

2010-01-21T20:11:39.171+01:00 n22 kernel: head: page allocation failure. order:9, mode:0xd0                                  
2010-01-21T20:11:39.171+01:00 n22 kernel: Pid: 2324, comm: head Not tainted 2.6.32.4 #1                                      
2010-01-21T20:11:39.171+01:00 n22 kernel: Call Trace:                                                                        
2010-01-21T20:11:39.171+01:00 n22 kernel: [<c106e2cc>] ? __alloc_pages_nodemask+0x4bc/0x5a0                                  
2010-01-21T20:11:39.171+01:00 n22 kernel: [<c108cf5a>] ? cache_alloc_refill+0x2ba/0x510                                      
2010-01-21T20:11:39.171+01:00 n22 kernel: [<c108d299>] ? __kmalloc+0xe9/0xf0                                                 
2010-01-21T20:11:39.171+01:00 n22 kernel: [<c10aa755>] ? seq_read+0x195/0x370                                                
2010-01-21T20:11:39.171+01:00 n22 kernel: [<c10aa5c0>] ? seq_read+0x0/0x370                                                  
2010-01-21T20:11:39.171+01:00 n22 kernel: [<c10cbb6f>] ? proc_reg_read+0x5f/0x90                                             
2010-01-21T20:11:39.171+01:00 n22 kernel: [<c10cbb10>] ? proc_reg_read+0x0/0x90                                              
2010-01-21T20:11:39.171+01:00 n22 kernel: [<c10927c5>] ? vfs_read+0xa5/0x190                                                 
2010-01-21T20:11:39.171+01:00 n22 kernel: [<c1092981>] ? sys_read+0x41/0x80                                                  
2010-01-21T20:11:39.171+01:00 n22 kernel: [<c100300f>] ? sysenter_do_call+0x12/0x26                                          
2010-01-21T20:11:39.171+01:00 n22 kernel: Mem-Info:                                                                          
2010-01-21T20:11:39.171+01:00 n22 kernel: DMA per-cpu:                                                                       
2010-01-21T20:11:39.172+01:00 n22 kernel: CPU    0: hi:    0, btch:   1 usd:   0                                             
2010-01-21T20:11:39.172+01:00 n22 kernel: CPU    1: hi:    0, btch:   1 usd:   0                                             
2010-01-21T20:11:39.172+01:00 n22 kernel: Normal per-cpu:                                                                    
2010-01-21T20:11:39.172+01:00 n22 kernel: CPU    0: hi:  186, btch:  31 usd:   0                                             
2010-01-21T20:11:39.172+01:00 n22 kernel: CPU    1: hi:  186, btch:  31 usd:   0                                             
2010-01-21T20:11:39.172+01:00 n22 kernel: HighMem per-cpu:                                                                   
2010-01-21T20:11:39.172+01:00 n22 kernel: CPU    0: hi:  186, btch:  31 usd:   0                                             
2010-01-21T20:11:39.172+01:00 n22 kernel: CPU    1: hi:  186, btch:  31 usd:   0                                             
2010-01-21T20:11:39.172+01:00 n22 kernel: active_anon:77374 inactive_anon:26716 isolated_anon:0                              
2010-01-21T20:11:39.172+01:00 n22 kernel: active_file:154367 inactive_file:77664 isolated_file:0                             
2010-01-21T20:11:39.172+01:00 n22 kernel: unevictable:0 dirty:74 writeback:432 unstable:0                                    
2010-01-21T20:11:39.172+01:00 n22 kernel: free:107209 slab_reclaimable:41314 slab_unreclaimable:3995                         
2010-01-21T20:11:39.172+01:00 n22 kernel: mapped:23759 shmem:19312 pagetables:882 bounce:0                                   
2010-01-21T20:11:39.172+01:00 n22 kernel: DMA free:12296kB min:64kB low:80kB high:96kB active_anon:0kB inactive_anon:0kB active_file:772kB inactive_file:372kB unevictable:0kB 
isolated(anon):0kB isolated(file):0kB present:15864kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:2520kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB 
unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
2010-01-21T20:11:39.172+01:00 n22 kernel: lowmem_reserve[]: 0 865 1911 1911
2010-01-21T20:11:39.172+01:00 n22 kernel: Normal free:282076kB min:3728kB low:4660kB high:5592kB active_anon:8kB inactive_anon:3320kB active_file:279600kB inactive_file:121612kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:885944kB mlocked:0kB dirty:140kB writeback:0kB mapped:276kB shmem:16kB slab_reclaimable:162736kB slab_unreclaimable:15980kB 
kernel_stack:900kB pagetables:3528kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
2010-01-21T20:11:39.172+01:00 n22 kernel: lowmem_reserve[]: 0 0 8369 8369
2010-01-21T20:11:39.172+01:00 n22 kernel: HighMem free:134464kB min:512kB low:1636kB high:2764kB active_anon:309488kB inactive_anon:103544kB active_file:337096kB 
inactive_file:188672kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1071256kB mlocked:0kB dirty:156kB writeback:1728kB mapped:94760kB shmem:77232kB slab_reclaimable:0kB 
slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
2010-01-21T20:11:39.172+01:00 n22 kernel: lowmem_reserve[]: 0 0 0 0
2010-01-21T20:11:39.172+01:00 n22 kernel: DMA: 288*4kB 121*8kB 80*16kB 62*32kB 48*64kB 22*128kB 4*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 12296kB
2010-01-21T20:11:39.172+01:00 n22 kernel: Normal: 19101*4kB 8755*8kB 3545*16kB 1846*32kB 186*64kB 34*128kB 2*256kB 2*512kB 0*1024kB 1*2048kB 0*4096kB = 282076kB
2010-01-21T20:11:39.172+01:00 n22 kernel: HighMem: 304*4kB 260*8kB 1594*16kB 1644*32kB 571*64kB 89*128kB 18*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 134464kB
2010-01-21T20:11:39.172+01:00 n22 kernel: 251864 total pagecache pages
2010-01-21T20:11:39.172+01:00 n22 kernel: 505 pages in swap cache
2010-01-21T20:11:39.172+01:00 n22 kernel: Swap cache stats: add 587, delete 82, find 189/195
2010-01-21T20:11:39.172+01:00 n22 kernel: Free swap  = 2001148kB
2010-01-21T20:11:39.172+01:00 n22 kernel: Total swap = 2003360kB
2010-01-21T20:11:39.172+01:00 n22 kernel: 498176 pages RAM
2010-01-21T20:11:39.172+01:00 n22 kernel: 270850 pages HighMem
2010-01-21T20:11:39.172+01:00 n22 kernel: 5979 pages reserved
2010-01-21T20:11:39.172+01:00 n22 kernel: 251238 pages shared
2010-01-21T20:11:39.172+01:00 n22 kernel: 209073 pages non-shared
2010-01-21T20:11:39.480+01:00 n22 kernel: ACPI: Please implement acpi_video_bus_ROM_seq_show


-- 
MfG/Sincerely
Toralf Förster

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null'
  2010-01-21 19:16 kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null' Toralf Förster
@ 2010-01-21 20:35 ` Alexey Dobriyan
  2010-01-21 21:19   ` Toralf Förster
  2010-01-28  4:51 ` Américo Wang
  1 sibling, 1 reply; 8+ messages in thread
From: Alexey Dobriyan @ 2010-01-21 20:35 UTC (permalink / raw)
  To: Toralf Förster; +Cc: linux-kernel

On Thu, Jan 21, 2010 at 08:16:59PM +0100, Toralf Förster wrote:
> I was inspired by http://article.gmane.org/gmane.linux.kernel/941115 .
> 
> Running the command (se subject) as a normal user at a 2.6.32.4 kernel
> gives this in /var/log/messages:
> 
> head: page allocation failure. order:9, mode:0xd0                                  
> Pid: 2324, comm: head Not tainted 2.6.32.4 #1                                      
> Call Trace:                                                                        
> [<c106e2cc>] ? __alloc_pages_nodemask+0x4bc/0x5a0                                  
> [<c108cf5a>] ? cache_alloc_refill+0x2ba/0x510                                      
> [<c108d299>] ? __kmalloc+0xe9/0xf0                                                 
> [<c10aa755>] ? seq_read+0x195/0x370                                                

Please, find out which file is causing this, if it's reproducible.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null'
  2010-01-21 20:35 ` Alexey Dobriyan
@ 2010-01-21 21:19   ` Toralf Förster
  2010-01-26 13:17     ` Jiri Kosina
  0 siblings, 1 reply; 8+ messages in thread
From: Toralf Förster @ 2010-01-21 21:19 UTC (permalink / raw)
  To: Alexey Dobriyan; +Cc: linux-kernel


Alexey Dobriyan wrote at 21:35:35
> On Thu, Jan 21, 2010 at 08:16:59PM +0100, Toralf Förster wrote:
> > I was inspired by http://article.gmane.org/gmane.linux.kernel/941115 .
> >
> > Running the command (se subject) as a normal user at a 2.6.32.4 kernel
> > gives this in /var/log/messages:
> >
> > head: page allocation failure. order:9, mode:0xd0
> > Pid: 2324, comm: head Not tainted 2.6.32.4 #1
> > Call Trace:
> > [<c106e2cc>] ? __alloc_pages_nodemask+0x4bc/0x5a0
> > [<c108cf5a>] ? cache_alloc_refill+0x2ba/0x510
> > [<c108d299>] ? __kmalloc+0xe9/0xf0
> > [<c10aa755>] ? seq_read+0x195/0x370
> 
> Please, find out which file is causing this, if it's reproducible.
> 
I reproduced the msg :
"ACPI: Please implement acpi_video_bus_ROM_seq_show" by :
by
$> head -c 10 /proc/acpi/video/VID/info

After suspend to disk and wakeup however the file /proc/acpi/video/VID/ROM was 
the culprit.

The trace however I can't reproduce until now.


-- 
MfG/Sincerely
Toralf Förster

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null'
  2010-01-21 21:19   ` Toralf Förster
@ 2010-01-26 13:17     ` Jiri Kosina
  2010-01-28  1:39       ` Zhang Rui
  2010-01-29 13:45       ` Al Viro
  0 siblings, 2 replies; 8+ messages in thread
From: Jiri Kosina @ 2010-01-26 13:17 UTC (permalink / raw)
  To: Toralf Förster; +Cc: Alexey Dobriyan, linux-kernel, linux-acpi, Zhang Rui


[ adding relevant CCs ]

On Thu, 21 Jan 2010, Toralf Förster wrote:

> Alexey Dobriyan wrote at 21:35:35
> > On Thu, Jan 21, 2010 at 08:16:59PM +0100, Toralf Förster wrote:
> > > I was inspired by http://article.gmane.org/gmane.linux.kernel/941115 .
> > >
> > > Running the command (se subject) as a normal user at a 2.6.32.4 kernel
> > > gives this in /var/log/messages:
> > >
> > > head: page allocation failure. order:9, mode:0xd0
> > > Pid: 2324, comm: head Not tainted 2.6.32.4 #1
> > > Call Trace:
> > > [<c106e2cc>] ? __alloc_pages_nodemask+0x4bc/0x5a0
> > > [<c108cf5a>] ? cache_alloc_refill+0x2ba/0x510
> > > [<c108d299>] ? __kmalloc+0xe9/0xf0
> > > [<c10aa755>] ? seq_read+0x195/0x370
> > 
> > Please, find out which file is causing this, if it's reproducible.
> > 
> I reproduced the msg :
> "ACPI: Please implement acpi_video_bus_ROM_seq_show" by :
> by
> $> head -c 10 /proc/acpi/video/VID/info
> 
> After suspend to disk and wakeup however the file /proc/acpi/video/VID/ROM was 
> the culprit.
> 
> The trace however I can't reproduce until now.
> 
> 
> 

-- 
Jiri Kosina
SUSE Labs, Novell Inc.


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null'
  2010-01-26 13:17     ` Jiri Kosina
@ 2010-01-28  1:39       ` Zhang Rui
  2010-01-29 13:45       ` Al Viro
  1 sibling, 0 replies; 8+ messages in thread
From: Zhang Rui @ 2010-01-28  1:39 UTC (permalink / raw)
  To: Jiri Kosina
  Cc: Toralf Förster, Alexey Dobriyan,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org

On Tue, 2010-01-26 at 21:17 +0800, Jiri Kosina wrote:
> [ adding relevant CCs ]
> 
> On Thu, 21 Jan 2010, Toralf Förster wrote:
> 
> > Alexey Dobriyan wrote at 21:35:35
> > > On Thu, Jan 21, 2010 at 08:16:59PM +0100, Toralf Förster wrote:
> > > > I was inspired by http://article.gmane.org/gmane.linux.kernel/941115 .
> > > >
> > > > Running the command (se subject) as a normal user at a 2.6.32.4 kernel
> > > > gives this in /var/log/messages:
> > > >
> > > > head: page allocation failure. order:9, mode:0xd0
> > > > Pid: 2324, comm: head Not tainted 2.6.32.4 #1
> > > > Call Trace:
> > > > [<c106e2cc>] ? __alloc_pages_nodemask+0x4bc/0x5a0
> > > > [<c108cf5a>] ? cache_alloc_refill+0x2ba/0x510
> > > > [<c108d299>] ? __kmalloc+0xe9/0xf0
> > > > [<c10aa755>] ? seq_read+0x195/0x370
> > > 
> > > Please, find out which file is causing this, if it's reproducible.
> > > 
> > I reproduced the msg :
> > "ACPI: Please implement acpi_video_bus_ROM_seq_show" by :
> > by
> > $> head -c 10 /proc/acpi/video/VID/info
> > 
this is just a KERN_INFO message that suggests the
acpi_video_bus_ROM_seq_show method is not actually implemented right
now.

I don't think it has anything to do with the trace. :)

thanks,
rui

> > After suspend to disk and wakeup however the file /proc/acpi/video/VID/ROM was 
> > the culprit.
> > 
> > The trace however I can't reproduce until now.
> > 
> > 
> > 
> 



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10  >/dev/null'
  2010-01-21 19:16 kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null' Toralf Förster
  2010-01-21 20:35 ` Alexey Dobriyan
@ 2010-01-28  4:51 ` Américo Wang
  2010-01-29 13:38   ` Al Viro
  1 sibling, 1 reply; 8+ messages in thread
From: Américo Wang @ 2010-01-28  4:51 UTC (permalink / raw)
  To: Toralf Förster; +Cc: linux-kernel, linux-mm, linux-fsdevel

2010/1/22 Toralf Förster <toralf.foerster@gmx.de>:
> I was inspired by http://article.gmane.org/gmane.linux.kernel/941115 .
>
> Running the command (se subject) as a normal user at a 2.6.32.4 kernel
> gives this in /var/log/messages:
>
> 2010-01-21T20:11:39.171+01:00 n22 kernel: head: page allocation failure. order:9, mode:0xd0


Hmm, it is suspecious that we need 2^9 pages for seq_file...


> 2010-01-21T20:11:39.171+01:00 n22 kernel: Pid: 2324, comm: head Not tainted 2.6.32.4 #1
> 2010-01-21T20:11:39.171+01:00 n22 kernel: Call Trace:
> 2010-01-21T20:11:39.171+01:00 n22 kernel: [<c106e2cc>] ? __alloc_pages_nodemask+0x4bc/0x5a0
> 2010-01-21T20:11:39.171+01:00 n22 kernel: [<c108cf5a>] ? cache_alloc_refill+0x2ba/0x510
> 2010-01-21T20:11:39.171+01:00 n22 kernel: [<c108d299>] ? __kmalloc+0xe9/0xf0
> 2010-01-21T20:11:39.171+01:00 n22 kernel: [<c10aa755>] ? seq_read+0x195/0x370
> 2010-01-21T20:11:39.171+01:00 n22 kernel: [<c10aa5c0>] ? seq_read+0x0/0x370
> 2010-01-21T20:11:39.171+01:00 n22 kernel: [<c10cbb6f>] ? proc_reg_read+0x5f/0x90
> 2010-01-21T20:11:39.171+01:00 n22 kernel: [<c10cbb10>] ? proc_reg_read+0x0/0x90
> 2010-01-21T20:11:39.171+01:00 n22 kernel: [<c10927c5>] ? vfs_read+0xa5/0x190
> 2010-01-21T20:11:39.171+01:00 n22 kernel: [<c1092981>] ? sys_read+0x41/0x80
> 2010-01-21T20:11:39.171+01:00 n22 kernel: [<c100300f>] ? sysenter_do_call+0x12/0x26
> 2010-01-21T20:11:39.171+01:00 n22 kernel: Mem-Info:
> 2010-01-21T20:11:39.171+01:00 n22 kernel: DMA per-cpu:
> 2010-01-21T20:11:39.172+01:00 n22 kernel: CPU    0: hi:    0, btch:   1 usd:   0
> 2010-01-21T20:11:39.172+01:00 n22 kernel: CPU    1: hi:    0, btch:   1 usd:   0
> 2010-01-21T20:11:39.172+01:00 n22 kernel: Normal per-cpu:
> 2010-01-21T20:11:39.172+01:00 n22 kernel: CPU    0: hi:  186, btch:  31 usd:   0
> 2010-01-21T20:11:39.172+01:00 n22 kernel: CPU    1: hi:  186, btch:  31 usd:   0
> 2010-01-21T20:11:39.172+01:00 n22 kernel: HighMem per-cpu:
> 2010-01-21T20:11:39.172+01:00 n22 kernel: CPU    0: hi:  186, btch:  31 usd:   0
> 2010-01-21T20:11:39.172+01:00 n22 kernel: CPU    1: hi:  186, btch:  31 usd:   0
> 2010-01-21T20:11:39.172+01:00 n22 kernel: active_anon:77374 inactive_anon:26716 isolated_anon:0
> 2010-01-21T20:11:39.172+01:00 n22 kernel: active_file:154367 inactive_file:77664 isolated_file:0
> 2010-01-21T20:11:39.172+01:00 n22 kernel: unevictable:0 dirty:74 writeback:432 unstable:0
> 2010-01-21T20:11:39.172+01:00 n22 kernel: free:107209 slab_reclaimable:41314 slab_unreclaimable:3995
> 2010-01-21T20:11:39.172+01:00 n22 kernel: mapped:23759 shmem:19312 pagetables:882 bounce:0
> 2010-01-21T20:11:39.172+01:00 n22 kernel: DMA free:12296kB min:64kB low:80kB high:96kB active_anon:0kB inactive_anon:0kB active_file:772kB inactive_file:372kB unevictable:0kB
> isolated(anon):0kB isolated(file):0kB present:15864kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:2520kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB
> unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
> 2010-01-21T20:11:39.172+01:00 n22 kernel: lowmem_reserve[]: 0 865 1911 1911
> 2010-01-21T20:11:39.172+01:00 n22 kernel: Normal free:282076kB min:3728kB low:4660kB high:5592kB active_anon:8kB inactive_anon:3320kB active_file:279600kB inactive_file:121612kB
> unevictable:0kB isolated(anon):0kB isolated(file):0kB present:885944kB mlocked:0kB dirty:140kB writeback:0kB mapped:276kB shmem:16kB slab_reclaimable:162736kB slab_unreclaimable:15980kB
> kernel_stack:900kB pagetables:3528kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
> 2010-01-21T20:11:39.172+01:00 n22 kernel: lowmem_reserve[]: 0 0 8369 8369
> 2010-01-21T20:11:39.172+01:00 n22 kernel: HighMem free:134464kB min:512kB low:1636kB high:2764kB active_anon:309488kB inactive_anon:103544kB active_file:337096kB
> inactive_file:188672kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1071256kB mlocked:0kB dirty:156kB writeback:1728kB mapped:94760kB shmem:77232kB slab_reclaimable:0kB
> slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
> 2010-01-21T20:11:39.172+01:00 n22 kernel: lowmem_reserve[]: 0 0 0 0
> 2010-01-21T20:11:39.172+01:00 n22 kernel: DMA: 288*4kB 121*8kB 80*16kB 62*32kB 48*64kB 22*128kB 4*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 12296kB
> 2010-01-21T20:11:39.172+01:00 n22 kernel: Normal: 19101*4kB 8755*8kB 3545*16kB 1846*32kB 186*64kB 34*128kB 2*256kB 2*512kB 0*1024kB 1*2048kB 0*4096kB = 282076kB

Obviously you have one 2^9-page chuck here, but page allocator doesn't
give this.


> 2010-01-21T20:11:39.172+01:00 n22 kernel: HighMem: 304*4kB 260*8kB 1594*16kB 1644*32kB 571*64kB 89*128kB 18*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 134464kB
> 2010-01-21T20:11:39.172+01:00 n22 kernel: 251864 total pagecache pages
> 2010-01-21T20:11:39.172+01:00 n22 kernel: 505 pages in swap cache
> 2010-01-21T20:11:39.172+01:00 n22 kernel: Swap cache stats: add 587, delete 82, find 189/195
> 2010-01-21T20:11:39.172+01:00 n22 kernel: Free swap  = 2001148kB
> 2010-01-21T20:11:39.172+01:00 n22 kernel: Total swap = 2003360kB
> 2010-01-21T20:11:39.172+01:00 n22 kernel: 498176 pages RAM
> 2010-01-21T20:11:39.172+01:00 n22 kernel: 270850 pages HighMem
> 2010-01-21T20:11:39.172+01:00 n22 kernel: 5979 pages reserved
> 2010-01-21T20:11:39.172+01:00 n22 kernel: 251238 pages shared
> 2010-01-21T20:11:39.172+01:00 n22 kernel: 209073 pages non-shared
> 2010-01-21T20:11:39.480+01:00 n22 kernel: ACPI: Please implement acpi_video_bus_ROM_seq_show
>

For me, this seems to be either a problem of mm page allocator or a problem
of seq_file, the former seems to be more likely since we already got some other
page allocation failure report...

Adding linux-mm and linux-fs-devel into Cc...

Thanks for your report.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null'
  2010-01-28  4:51 ` Américo Wang
@ 2010-01-29 13:38   ` Al Viro
  0 siblings, 0 replies; 8+ messages in thread
From: Al Viro @ 2010-01-29 13:38 UTC (permalink / raw)
  To: Am??rico Wang; +Cc: Toralf F??rster, linux-kernel, linux-mm, linux-fsdevel

On Thu, Jan 28, 2010 at 12:51:02PM +0800, Am??rico Wang wrote:
> 2010/1/22 Toralf F??rster <toralf.foerster@gmx.de>:
> > I was inspired by http://article.gmane.org/gmane.linux.kernel/941115 .
> >
> > Running the command (se subject) as a normal user at a 2.6.32.4 kernel
> > gives this in /var/log/messages:
> >
> > 2010-01-21T20:11:39.171+01:00 n22 kernel: head: page allocation failure. order:9, mode:0xd0
> 
> 
> Hmm, it is suspecious that we need 2^9 pages for seq_file...

Something's using single_open() and obscene amounts of output; should
switch to real iterator...  Which file it is?

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null'
  2010-01-26 13:17     ` Jiri Kosina
  2010-01-28  1:39       ` Zhang Rui
@ 2010-01-29 13:45       ` Al Viro
  1 sibling, 0 replies; 8+ messages in thread
From: Al Viro @ 2010-01-29 13:45 UTC (permalink / raw)
  To: Jiri Kosina
  Cc: Toralf F?rster, Alexey Dobriyan, linux-kernel, linux-acpi,
	Zhang Rui

On Tue, Jan 26, 2010 at 02:17:32PM +0100, Jiri Kosina wrote:
> > > Please, find out which file is causing this, if it's reproducible.
> > > 
> > I reproduced the msg :
> > "ACPI: Please implement acpi_video_bus_ROM_seq_show" by :
> > by
> > $> head -c 10 /proc/acpi/video/VID/info
> > 
> > After suspend to disk and wakeup however the file /proc/acpi/video/VID/ROM was 
> > the culprit.
> > 
> > The trace however I can't reproduce until now.

*snort*
The message is caused by
        printk(KERN_INFO PREFIX "Please implement %s\n", __func__);
        seq_printf(seq, "<TODO>\n");
in acpi_video_bus_ROM_seq_show(), so it's not surprising.  Shouldn't spew
to syslog, but other than that it's a non-issue.  Stack trace, OTOH, is
something very different; something is trying to generate 2Mb of contents
in a single ->show().  Which is definitely not that one - "<TODO>\n" is
not going to eat that much ;-)

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2010-01-29 13:45 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-01-21 19:16 kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null' Toralf Förster
2010-01-21 20:35 ` Alexey Dobriyan
2010-01-21 21:19   ` Toralf Förster
2010-01-26 13:17     ` Jiri Kosina
2010-01-28  1:39       ` Zhang Rui
2010-01-29 13:45       ` Al Viro
2010-01-28  4:51 ` Américo Wang
2010-01-29 13:38   ` Al Viro

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox