From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752919AbXCFFae (ORCPT ); Tue, 6 Mar 2007 00:30:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752924AbXCFFae (ORCPT ); Tue, 6 Mar 2007 00:30:34 -0500 Received: from srv5.dvmed.net ([207.36.208.214]:50604 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752918AbXCFFad (ORCPT ); Tue, 6 Mar 2007 00:30:33 -0500 Message-ID: <45ECFC5F.7000102@garzik.org> Date: Tue, 06 Mar 2007 00:30:07 -0500 From: Jeff Garzik User-Agent: Thunderbird 1.5.0.9 (X11/20070212) MIME-Version: 1.0 To: Ingo Molnar CC: "Michael S. Tsirkin" , Pavel Machek , Jens Axboe , Adrian Bunk , Linus Torvalds , Andrew Morton , Linux Kernel Mailing List , Thomas Gleixner , linux-pm@lists.osdl.org, Michal Piotrowski , Auke Kok Subject: Re: SATA resume slowness, e1000 MSI warning References: <20070225175559.GC12392@stusta.de> <20070227100202.GV3822@kernel.dk> <20070227102109.GG6745@elf.ucw.cz> <20070227103021.GA2250@kernel.dk> <20070227103407.GA17819@elte.hu> <20070227105922.GD2250@kernel.dk> <20070227111515.GA4271@kernel.dk> <20070301093450.GA8508@elte.hu> <20070302100704.GB2293@elf.ucw.cz> <20070305084257.GA4464@mellanox.co.il> <20070305101120.GA23032@elte.hu> In-Reply-To: <20070305101120.GA23032@elte.hu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.3 (----) X-Spam-Report: SpamAssassin version 3.1.8 on srv5.dvmed.net summary: Content analysis details: (-4.3 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Ingo Molnar wrote: > i'm also getting this WARN_ON() from e1000: > > BUG: at drivers/pci/msi.c:611 pci_enable_msi() > [] show_trace_log_lvl+0x19/0x2e > [] show_trace+0x12/0x14 > [] dump_stack+0x14/0x16 > [] pci_enable_msi+0x6d/0x203 > [] e1000_request_irq+0x2e/0xe2 > [] e1000_resume+0x7f/0xef > [] pci_device_resume+0x1a/0x44 > [] resume_device+0xf7/0x16f > [] dpm_resume+0x77/0xcb > [] device_resume+0x3a/0x51 > [] enter_state+0x193/0x1bb > [] state_store+0x81/0x97 > [] subsys_attr_store+0x20/0x25 > [] sysfs_write_file+0xce/0xf6 > [] vfs_write+0xb1/0x13a > [] sys_write+0x3d/0x61 > [] syscall_call+0x7/0xb > > seems harmless because it seems to work fine. I would poke Eric Biederman(sp?) about this one. Maybe its even solved by the MSI-enable-related patch he posted in the past 24-48 hours. Jeff