From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759326AbYHVJbd (ORCPT ); Fri, 22 Aug 2008 05:31:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753350AbYHVJbZ (ORCPT ); Fri, 22 Aug 2008 05:31:25 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:43039 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753149AbYHVJbW (ORCPT ); Fri, 22 Aug 2008 05:31:22 -0400 From: "Rafael J. Wysocki" To: "Vegard Nossum" Subject: Re: latest -git: suspend: unable to handle kernel paging request (was Re: no_console_suspend doesn't work?) Date: Fri, 22 Aug 2008 11:34:39 +0200 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) Cc: "Pekka Enberg" , "Linux Kernel Mailing List" , "Andrew Morton" , "Jens Axboe" , "Bartlomiej Zolnierkiewicz" References: <19f34abd0808211028w7889587fke523ff244339e7c5@mail.gmail.com> <200808220016.34494.rjw@sisk.pl> <19f34abd0808212145x6fbb481ex99829b22599439d9@mail.gmail.com> In-Reply-To: <19f34abd0808212145x6fbb481ex99829b22599439d9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200808221134.39983.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday, 22 of August 2008, Vegard Nossum wrote: > On Fri, Aug 22, 2008 at 12:16 AM, Rafael J. Wysocki wrote: > > On Thursday, 21 of August 2008, Pekka Enberg wrote: > >> > ============================================================================= > >> > BUG blkdev_ioc: Invalid object pointer 0xf5cdaca8 > >> > ----------------------------------------------------------------------------- > >> > >> Ok, here we have the block layer passing a bad pointer to SLUB this > >> time. And it's also from the suspend code (although it's the resume > >> path this time). As we never see an oops from the block layer first, > >> it's possible that someone else corrupted everything and it just shows > >> up in the block layer. Maybe something worth investigating, though. > >> > >> > INFO: Slab 0xf789e318 objects=14 used=14 fp=0x00000000 flags=0x2082083 > >> > Pid: 3597, comm: bash Tainted: G D 2.6.27-rc4-00003-ga798564-dirty #30 > >> > [] slab_err+0x46/0x50 > >> > [] ? check_slab+0xd6/0xf0 > >> > [] ? call_rcu+0x6f/0x80 > >> > [] ? trace_hardirqs_on+0xb/0x10 > >> > [] __slab_free+0x238/0x360 > >> > [] kmem_cache_free+0xa9/0x120 > >> > [] ? put_io_context+0x53/0x70 > >> > [] ? put_io_context+0x53/0x70 > >> > [] put_io_context+0x53/0x70 > >> > [] exit_io_context+0x6e/0x80 > >> > [] do_exit+0x84e/0x890 > >> > [] ? trace_hardirqs_on_thunk+0xc/0x10 > >> > [] ? printk+0x1b/0x20 > >> > [] ? print_oops_end_marker+0x2a/0x30 > >> > [] oops_end+0xb1/0xc0 > >> > [] die+0x50/0x70 > >> > [] do_trap+0x91/0xc0 > >> > [] ? do_invalid_op+0x0/0xa0 > >> > [] do_invalid_op+0x88/0xa0 > >> > [] ? page_remove_rmap+0x109/0x120 > >> > [] ? vprintk+0x151/0x3c0 > >> > [] ? vprintk+0x2db/0x3c0 > >> > [] ? print_lock_contention_bug+0x1a/0xe0 > >> > [] ? print_lock_contention_bug+0x1a/0xe0 > >> > [] error_code+0x72/0x78 > >> > [] ? sched_rt_period_timer+0x21b/0x270 > >> > [] ? page_remove_rmap+0x109/0x120 > >> > [] unmap_vmas+0x4b1/0x8b0 > >> > [] ? print_lock_contention_bug+0x1a/0xe0 > >> > [] exit_mmap+0x84/0x120 > >> > [] mmput+0x48/0xa0 > >> > [] exit_mm+0xe7/0x110 > >> > [] do_exit+0x184/0x890 > >> > [] ? printk+0x1b/0x20 > >> > [] ? print_oops_end_marker+0x2a/0x30 > >> > [] oops_end+0xb1/0xc0 > >> > [] die+0x50/0x70 > >> > [] do_page_fault+0x1ef/0xa20 > >> > [] ? native_sched_clock+0xb5/0x110 > >> > [] ? __lock_acquire+0x27a/0xa00 > >> > [] ? do_page_fault+0x0/0xa20 > >> > [] error_code+0x72/0x78 > >> > [] ? __list_add+0x15/0x90 > >> > [] ? _spin_lock+0x63/0x70 > >> > [] rmqueue_bulk+0x54/0x80 > >> > [] get_page_from_freelist+0x5a7/0x720 > >> > [] ? __lock_acquire+0x27a/0xa00 > >> > [] __alloc_pages_internal+0xa0/0x450 > >> > [] alloc_pages_current+0x7b/0xc0 > >> > [] new_slab+0x1bb/0x2d0 > >> > [] ? _spin_unlock+0x27/0x50 > >> > [] __slab_alloc+0x32a/0x4e0 > >> > [] ? native_sched_clock+0xb5/0x110 > >> > [] kmem_cache_alloc+0xb4/0xe0 > >> > [] ? mempool_alloc_slab+0xe/0x10 > >> > [] ? mempool_alloc_slab+0xe/0x10 > >> > [] mempool_alloc_slab+0xe/0x10 > >> > [] mempool_alloc+0x31/0xf0 > >> > [] ? trace_hardirqs_on_caller+0xd4/0x160 > >> > [] ? trace_hardirqs_on+0xb/0x10 > >> > [] get_request+0xae/0x2c0 > >> > [] get_request_wait+0x1c/0xd0 > >> > [] ? _spin_lock_irq+0x72/0x80 > >> > [] blk_get_request+0x32/0x70 > >> > [] generic_ide_resume+0x5c/0xf0 > > > > IDE again? > > > > Vegard, this is piix, isn't it? > > If this makes it so, then yes: > > calling piix_ide_init+0x0/0xb0 > initcall piix_ide_init+0x0/0xb0 returned 0 after 0 msecs > calling ide_scan_pcibus+0x0/0xf0 > piix 0000:00:1f.1: IDE controller (0x8086:0x27df rev 0x01) > piix 0000:00:1f.1: IDE port disabled > piix 0000:00:1f.1: not 100% native mode: will probe irqs later > ide0: BM-DMA at 0xffa0-0xffa7 > Probing IDE interface ide0... > hda: WDC WD1600BB-00DAA3, ATA DISK drive > hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 > hda: UDMA/100 mode selected > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > > It is also interesting that you mention that; this is from an earlier > run (before serial console was working properly): > > > In my last run, I managed to get a lot of ascii art on the screen, but > > also one line which gave me the EIP of the oops: > > > $ addr2line -e vmlinux -i c03724f3 > > block/cfq-iosched.c:1190 > > > /* > > * Must always be called with the rcu_read_lock() held > > */ > > static void > > __call_for_each_cic(struct io_context *ioc, > > void (*func)(struct io_context *, struct cfq_io_context *)) > > { > > struct cfq_io_context *cic; > > struct hlist_node *n; > > > > hlist_for_each_entry_rcu(cic, n, &ioc->cic_list, cic_list) <-- here > > func(ioc, cic); > > } Hmm. Would that be possible to switch temporarily to PATA/libata and see if the problem goes away? Then, we'd get a strong indication that it really is related to IDE. Thanks, Rafael