Re: 2.6.5-mm4

• Previous message: Daniel Brahneborg: "block -> name ?"
• In reply to: Andrew Morton: "2.6.5-mm4"
• Next in thread: Andrew Morton: "Re: 2.6.5-mm4"
• Reply: Andrew Morton: "Re: 2.6.5-mm4"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date:	Mon, 12 Apr 2004 10:46:05 +0400
To: linux-kernel@vger.kernel.org

Replying to Andrew Morton:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.5/2.6.5-mm4/

I've got couple of these:
Apr 12 10:31:41 h1 Debug: sleeping function called from invalid
context at drivers/block/ll_rw_blk.c:1156
Apr 12 10:31:41 h1 in_atomic():1, irqs_disabled():1
Apr 12 10:31:41 h1 Call Trace:
Apr 12 10:31:41 h1 [<c011e396>] __might_sleep+0xb6/0xe0
Apr 12 10:31:41 h1 [<c02e4f05>] generic_unplug_device+0x15/0x80
Apr 12 10:31:41 h1 [<c03b8597>] unplug_slaves+0xa7/0xb0
Apr 12 10:31:41 h1 [<c02e76f4>] blk_backing_dev_unplug+0x14/0x16
Apr 12 10:31:41 h1 [<c016287a>] __wait_on_buffer+0xea/0xf0
Apr 12 10:31:41 h1 [<c011e980>] autoremove_wake_function+0x0/0x40
Apr 12 10:31:41 h1 [<c0166514>] submit_bh+0x94/0x1e0
Apr 12 10:31:41 h1 [<c011e980>] autoremove_wake_function+0x0/0x40
Apr 12 10:31:41 h1 [<c01a8298>] ext3_get_inode_loc+0x168/0x250
Apr 12 10:31:41 h1 [<c01a8409>] ext3_read_inode+0x29/0x2f0
Apr 12 10:31:41 h1 [<c017c7f5>] get_new_inode_fast+0x45/0x130
Apr 12 10:31:41 h1 [<c01aa2a4>] ext3_lookup+0x84/0xb0
Apr 12 10:31:41 h1 [<c016f98e>] real_lookup+0xce/0x100
Apr 12 10:31:41 h1 [<c016fc25>] do_lookup+0x75/0x80
Apr 12 10:31:41 h1 [<c016fd57>] link_path_walk+0x127/0xa20
Apr 12 10:31:41 h1 [<c02a0aa4>] set_cursor+0x64/0x80
Apr 12 10:31:41 h1 [<c0170934>] path_lookup+0xa4/0x1d0
Apr 12 10:31:41 h1 [<c01711c9>] open_namei+0x89/0x420
Apr 12 10:31:41 h1 [<c016043d>] filp_open+0x2d/0x50
Apr 12 10:31:41 h1 [<c01608ed>] sys_open+0x4d/0xa0
Apr 12 10:31:41 h1 [<c01003e9>] init+0xd9/0x180
Apr 12 10:31:41 h1 [<c0100310>] init+0x0/0x180
Apr 12 10:31:41 h1 [<c01042c5>] kernel_thread_helper+0x5/0x10

Sometimes it is a bit longer
Apr 12 10:31:41 h1 Debug: sleeping function called from invalid
context at drivers/block/ll_rw_blk.c:1156
Apr 12 10:31:41 h1 in_atomic():1, irqs_disabled():1
Apr 12 10:31:41 h1 Call Trace:
Apr 12 10:31:41 h1 [<c011e396>] __might_sleep+0xb6/0xe0
Apr 12 10:31:41 h1 [<c02e4f05>] generic_unplug_device+0x15/0x80
Apr 12 10:31:41 h1 [<c03b8597>] unplug_slaves+0xa7/0xb0
Apr 12 10:31:41 h1 [<c02e76f4>] blk_backing_dev_unplug+0x14/0x16
Apr 12 10:31:41 h1 [<c016287a>] __wait_on_buffer+0xea/0xf0
Apr 12 10:31:41 h1 [<c011e980>] autoremove_wake_function+0x0/0x40
Apr 12 10:31:41 h1 [<c0166514>] submit_bh+0x94/0x1e0
Apr 12 10:31:41 h1 [<c011e980>] autoremove_wake_function+0x0/0x40
Apr 12 10:31:41 h1 [<c0164255>] __bread_slow+0x45/0xa0
Apr 12 10:31:41 h1 [<c016454c>] __bread+0x2c/0x30
Apr 12 10:31:41 h1 [<c01a5832>] ext3_get_branch+0x72/0xf0
Apr 12 10:31:41 h1 [<c01a5e5b>] ext3_get_block_handle+0x8b/0x300
Apr 12 10:31:41 h1 [<c02e685c>] submit_bio+0x6c/0x120
Apr 12 10:31:41 h1 [<c01a612a>] ext3_get_block+0x5a/0xb0
Apr 12 10:31:41 h1 [<c018483a>] do_mpage_readpage+0x1aa/0x4c0
Apr 12 10:31:41 h1 [<c0144bff>] buffered_rmqueue+0x11f/0x250
Apr 12 10:31:41 h1 [<c0257b98>] radix_tree_insert+0xe8/0x110
Apr 12 10:31:41 h1 [<c013f921>] add_to_page_cache+0x61/0x180
Apr 12 10:31:41 h1 [<c0184cdc>] mpage_readpages+0x18c/0x1d0
Apr 12 10:31:41 h1 [<c01a60d0>] ext3_get_block+0x0/0xb0
Apr 12 10:31:41 h1 [<c01a6ed0>] ext3_readpages+0x0/0x20
Apr 12 10:31:41 h1 [<c014763d>] read_pages+0x19d/0x1b0
Apr 12 10:31:41 h1 [<c01a60d0>] ext3_get_block+0x0/0xb0
Apr 12 10:31:41 h1 [<c0144ffa>] __alloc_pages+0x2ca/0x320
Apr 12 10:31:41 h1 [<c01161b6>] smp_apic_timer_interrupt+0xe6/0x150
Apr 12 10:31:41 h1 [<c0106c16>] apic_timer_interrupt+0x1a/0x20
Apr 12 10:31:41 h1 [<c0147974>] do_page_cache_readahead+0x124/0x1c0
Apr 12 10:31:41 h1 [<c0147b16>] page_cache_readahead+0x106/0x210
Apr 12 10:31:41 h1 [<c014044a>] do_generic_mapping_read+0xba/0x500
Apr 12 10:31:41 h1 [<c0140890>] file_read_actor+0x0/0xd0
Apr 12 10:31:41 h1 [<c0140b30>] __generic_file_aio_read+0x1d0/0x200
Apr 12 10:31:41 h1 [<c0140890>] file_read_actor+0x0/0xd0
Apr 12 10:31:41 h1 [<c01a5e5b>] ext3_get_block_handle+0x8b/0x300
Apr 12 10:31:41 h1 [<c0140ba2>] generic_file_aio_read+0x42/0x60
Apr 12 10:31:41 h1 [<c0161264>] do_sync_read+0x74/0xb0
Apr 12 10:31:41 h1 [<c011eb5c>] mm_init+0xcc/0x110
Apr 12 10:31:41 h1 [<c0161342>] vfs_read+0xa2/0x100
Apr 12 10:31:41 h1 [<c016cb2c>] kernel_read+0x3c/0x50
Apr 12 10:31:41 h1 [<c016d85f>] prepare_binprm+0xaf/0xc0
Apr 12 10:31:41 h1 [<c016dc28>] do_execve+0xf8/0x1c0
Apr 12 10:31:41 h1 [<c016f53b>] getname+0xab/0xf0
Apr 12 10:31:41 h1 [<c0104be2>] sys_execve+0x32/0x80
Apr 12 10:31:41 h1 [<c010615d>] sysenter_past_esp+0x52/0x71

.config attached
Actually, it is not -mm4 itself but Joe Thornber's -udm2 ont top
of it and evms patches.

-- 
Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key
 This message represents the official view of the voices in my head

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

• text/plain attachment: .config

• Previous message: Daniel Brahneborg: "block -> name ?"
• In reply to: Andrew Morton: "2.6.5-mm4"
• Next in thread: Andrew Morton: "Re: 2.6.5-mm4"
• Reply: Andrew Morton: "Re: 2.6.5-mm4"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]