From: john stultz <johnstul@us.ibm.com>
To: Christian Hoffmann <email@christianhoffmann.info>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Long timeout when booting >= 2.6.38
Date: Tue, 03 May 2011 18:38:54 -0700 [thread overview]
Message-ID: <1304473134.3037.14.camel@work-vm> (raw)
In-Reply-To: <4DC04E15.2030308@christianhoffmann.info>
On Tue, 2011-05-03 at 20:48 +0200, Christian Hoffmann wrote:
> Hi,
>
> > Could you send me the full dmesg output both with and without the
> > 08ec0c58fb8a05d3191d5cb6f5d6f81adb419798 commit applied?
>
> broken.dmesg is kernel at 08ec0c58fb8a05d3191d5cb6f5d6f81adb419798
> working.dmesg is 08ec0c58fb8a05d3191d5cb6f5d6f81adb419798 - 1
>
> >
> > Also, does the same issue crop up if you compile the kernel with
> > CONFIG_PCI_MSI disabled?
> >
>
> I can't really disable this, can I? This gets set by other presets. I
> tried to use pci=nomsi, but i see same issue (but I also see the MSI
> quirks in dmesg, so not sure if this is working).
>
> I didn't cc the linux-kernel, as I don't know if I am supposed to post
> dmesg/attachements.
Can you send dmesg on a broken kernel with the following patch added?
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 5129ed6..6718e7f 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -2791,6 +2791,7 @@ static void pci_do_fixups(struct pci_dev *dev, struct pci_fixup *f,
if ((f->vendor == dev->vendor || f->vendor == (u16) PCI_ANY_ID) &&
(f->device == dev->device || f->device == (u16) PCI_ANY_ID)) {
dev_dbg(&dev->dev, "calling %pF\n", f->hook);
+ printk("Calling fixup hook: %pF\n", f->hook);
f->hook(dev);
}
f++;
next prev parent reply other threads:[~2011-05-04 1:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 18:49 Long timeout when booting >= 2.6.38 Christian Hoffmann
2011-05-02 19:09 ` john stultz
2011-05-02 20:42 ` Christian Hoffmann
2011-05-02 21:10 ` Christian Hoffmann
2011-05-02 22:12 ` john stultz
2011-05-02 21:49 ` john stultz
2011-05-02 22:27 ` Christian Hoffmann
2011-05-03 0:31 ` john stultz
2011-05-03 19:33 ` Christian Hoffmann
[not found] ` <4DC04E15.2030308@christianhoffmann.info>
2011-05-04 1:38 ` john stultz [this message]
2011-05-04 7:12 ` Christian Hoffmann
2011-05-04 17:04 ` Christian Hoffmann
2011-05-04 1:00 ` john stultz
2011-05-04 7:31 ` Christian Hoffmann
2011-05-04 8:37 ` Thomas Gleixner
2011-05-04 16:47 ` Christian Hoffmann
2011-05-04 17:49 ` Thomas Gleixner
2011-05-04 19:40 ` Christian Hoffmann
2011-05-04 20:53 ` Thomas Gleixner
2011-05-05 17:28 ` Christian Hoffmann
2011-05-09 8:22 ` Thomas Gleixner
2011-05-15 20:11 ` Christian Hoffmann
2011-05-16 9:07 ` Thomas Gleixner
2011-05-16 19:34 ` Christian Hoffmann
2011-05-05 1:16 ` john stultz
2011-05-05 8:25 ` Thomas Gleixner
2011-05-05 17:47 ` Christian Hoffmann
2011-05-05 18:41 ` Thomas Gleixner
2011-05-03 18:12 ` David
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1304473134.3037.14.camel@work-vm \
--to=johnstul@us.ibm.com \
--cc=email@christianhoffmann.info \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox